Guys…sorry for the essay…but I do appreciate your time if and when you may have time to spare and read my reply…?
Troy – Licensing shouldn’t be an issue, this host is one of 9 hosts running our Virtual Server Infrastructure.
All others are running fine and setup in the same manner…to use the same license server...although the problem box it is not picking up any add-ins that it should like our other servers I just assumed these missing add-ins are because the box is not connecting to the VC…i.e….vCenter agent for ESX Server, VMotion, VMware Consolidated Backup are not showing up under the licensing config tab?
Disk space also seems fine…
[root@vh1 root]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/cciss/c0d0p2 4.9G 1.5G 3.2G 32% /
/dev/cciss/c0d0p1 99M 26M 68M 28% /boot
none 391M 0 391M 0% /dev/shm
/dev/cciss/c0d0p6 2.0G 1006M 856M 55% /var/log
This feels more and more like a network issue to me?
Bulletprooffo – yes I tried connecting the box into VC by IP and hostname…all I get is that totally unhelpful “general system error” error message!
On your second suggestion…ALL our ESX hosts in our VM server cluster are in the same subnet. Only this particular box is playing up! She is an old girl (ProLiant DL 585 - G1) but we have 4 other identical “physically identical” G1 boxes in this cluster working fine?
I have noticed that the VC server address is NOT in this problem box’s host file. Infact because we have never used HA or VMotion none of our hosts have anything other than their own address set in their host files…strange that it is not affecting any other boxes but I am going to add the VC IP and FQDN to the problem box’s host file and see what happens…?
On the storage point…hmm…I’m afraid this is a headache for us at present!
We have an EVA which is being difficult in that not even HP themselves can figure out why our ESX hosts auto configure their paths to overwhelmingly route through only one of the two Fibre channel controllers on the EVA. To make matters worse they set their preferred path all on the same port of the 4 ports on each FC controller which means when something like McAfee tries to push out an update our EVA grinds to a halt with maxed out I\O…!!!
Disk presentation does however seem fine on this box…despite the same port and controller prefered path issue!
Disk vmhba1:0:14 /dev/sdb (460800MB) has 8 paths and policy of Fixed
FC 3:7.0 10000000c96459bd<->50001fe1500d4c9a vmhba1:0:14 On active preferred
FC 3:7.0 10000000c96459bd<->50001fe1500d4c98 vmhba1:1:14 On
FC 3:7.0 10000000c96459bd<->50001fe1500d4c9e vmhba1:2:14 On
FC 3:7.0 10000000c96459bd<->50001fe1500d4c9c vmhba1:3:14 On
FC 3:8.0 10000000c9673ed6<->50001fe1500d4c9b vmhba2:0:14 On
FC 3:8.0 10000000c9673ed6<->50001fe1500d4c99 vmhba2:1:14 On
FC 3:8.0 10000000c9673ed6<->50001fe1500d4c9f vmhba2:2:14 On
FC 3:8.0 10000000c9673ed6<->50001fe1500d4c9d vmhba2:3:14 On
Disk vmhba1:0:10 /dev/sda (512000MB) has 8 paths and policy of Fixed
FC 3:7.0 10000000c96459bd<->50001fe1500d4c9a vmhba1:0:10 On active preferred
FC 3:7.0 10000000c96459bd<->50001fe1500d4c98 vmhba1:1:10 On
FC 3:7.0 10000000c96459bd<->50001fe1500d4c9e vmhba1:2:10 On
FC 3:7.0 10000000c96459bd<->50001fe1500d4c9c vmhba1:3:10 On
FC 3:8.0 10000000c9673ed6<->50001fe1500d4c9b vmhba2:0:10 On
FC 3:8.0 10000000c9673ed6<->50001fe1500d4c99 vmhba2:1:10 On
FC 3:8.0 10000000c9673ed6<->50001fe1500d4c9f vmhba2:2:10 On
FC 3:8.0 10000000c9673ed6<->50001fe1500d4c9d vmhba2:3:10 On
Disk vmhba3:0:0 /dev/cciss/c0d0 (140006MB) has 1 paths and policy of Fixed
Local 6:4.0 vmhba3:0:0 On active preferred
RAID Controller (SCSI-3) vmhba1:1:0 (0MB) has 8 paths and policy of Fixed
FC 3:7.0 10000000c96459bd<->50001fe1500d4c98 vmhba1:1:0 On active preferred
FC 3:7.0 10000000c96459bd<->50001fe1500d4c9e vmhba1:2:0 On
FC 3:7.0 10000000c96459bd<->50001fe1500d4c9c vmhba1:3:0 On
FC 3:7.0 10000000c96459bd<->50001fe1500d4c9a vmhba1:0:0 On
FC 3:8.0 10000000c9673ed6<->50001fe1500d4c9b vmhba2:0:0 On
FC 3:8.0 10000000c9673ed6<->50001fe1500d4c99 vmhba2:1:0 On
FC 3:8.0 10000000c9673ed6<->50001fe1500d4c9f vmhba2:2:0 On
FC 3:8.0 10000000c9673ed6<->50001fe1500d4c9d vmhba2:3:0 On
This looks more and more like an ESX box reboot...although I hate doing this because it doesn't teach me anything or halp us find out possible problems with the system!
