shakeking's Posts

I upgraded one of our ESX 2.5.2 servers to 3.01 after VMotioning all the servers to the other 2 2.5.x servers. I have been creating new VMFS3 LUN's on our EMC CX300 and copying the .vmdk files on... See more...
I upgraded one of our ESX 2.5.2 servers to 3.01 after VMotioning all the servers to the other 2 2.5.x servers. I have been creating new VMFS3 LUN's on our EMC CX300 and copying the .vmdk files one at a time over to the new LUNs and upgrading the VM Hardware and Tools. However, whenever I add another LUN to the ESX storage group, it always shows up as LUN9 when I click add Storage in the VMI client. Then, the ESX 3.x box can no longer see the previous LUN I created. This is the same process for each new LUN I try to allocate, it seems to conflict with the previous one so I can add more than 1 LUN to the ESX 3.x server. Anyone run into this before? Jonathan
We are planning an upgrade from 2.5.2 to 3.01. We ran the preupgrade perl script amd get the following errors on our SAN volumes where we have running VM's, any suggestions? \[root@esx3 script... See more...
We are planning an upgrade from 2.5.2 to 3.01. We ran the preupgrade perl script amd get the following errors on our SAN volumes where we have running VM's, any suggestions? \[root@esx3 scripts]# perl ./preupgrade.pl Checking existing VMs... Checking VM versions... Checking for repeatable resume... Checking Service Console disk space... Checking VMFS disk space... ERROR: The following VMFS volumes require at least 1200 MB ERROR: of free disk space to upgrade: ERROR: * vmhba1:0:0:1 ERROR: * vmhba1:0:10:1 ERROR: * vmhba1:0:11:1 ERROR: * vmhba1:0:12:1 ERROR: * vmhba1:0:13:1 ERROR: * vmhba1:0:14:1 ERROR: * vmhba1:0:15:1 ERROR: * vmhba1:0:16:1 ERROR: * vmhba1:0:18:1 ERROR: * vmhba1:0:19:1 ERROR: * vmhba1:0:1:1 ERROR: * vmhba1:0:3:1 ERROR: * vmhba1:0:4:1 ERROR: * vmhba1:0:5:1 ERROR: * vmhba1:0:6:1 ERROR: * vmhba1:0:7:1 ERROR: * vmhba1:0:8:1 ERROR: * vmhba1:0:9:1 ERROR: * vmhba1:1:12:1 ERROR: * vmhba1:1:13:1 ERROR: * vmhba1:1:14:1 ERROR: * vmhba1:1:14:2 ERROR: * vmhba1:1:15:1 ERROR: * vmhba1:1:16:1 ERROR: * vmhba1:1:18:1 ERROR: * vmhba1:1:21:1 ERROR: * vmhba1:1:23:1 ERROR: * vmhba1:1:23:2 ERROR: * vmhba1:1:23:3 ERROR: * vmhba1:1:23:4 ERROR: * vmhba1:1:24:1 ERROR: * vmhba1:1:26:1 ERROR: * vmhba1:1:27:1 ERROR: * vmhba1:1:28:1 ERROR: * vmhba1:1:2:1 ERROR: * vmhba1:1:33:1 ERROR: * vmhba1:1:34:1 ERROR: * vmhba1:1:35:1 ERROR: * vmhba1:1:4:1 ERROR: * vmhba1:1:5:1 ERROR: * vmhba1:1:5:2 ERROR: * vmhba1:1:5:3 ERROR: * vmhba1:1:5:4 ERROR: * vmhba1:1:6:1 ERROR: * vmhba1:1:6:2 ERROR: * vmhba1:1:6:3 ERROR: * vmhba1:1:6:4 ERROR: * vmhba1:1:7:1 ERROR: * vmhba1:1:8:1 ERROR: * vmhba1:1:9:1 ERROR: * vmhba1:1:9:2 ERROR: * vmhba1:1:9:3 ERROR: * vmhba1:1:9:4 ERROR: * vmhba1:3:36:3 ERROR: * vmhba1:3:36:5 ERROR: * vmhba1:3:36:6 ERROR: * vmhba1:3:36:7 ERROR: * vmhba1:3:36:8 ERROR: * vmhba2:0:17:1 ERROR: * vmhba2:0:29:1 ERROR: * vmhba2:0:30:1 ERROR: * vmhba2:0:32:1 ERROR: * vmhba2:2:17:1 ERROR: * vmhba2:2:20:1 ERROR: * vmhba2:2:21:1 ERROR: * vmhba2:2:22:1 ERROR: * vmhba2:2:23:1 ERROR: * vmhba2:2:24:1 Checking VMFS version compatibility... Checking device names...
We have 2 ESX 2.5.2 servers, 1 production & 1 developement, and one the developement server we have serveral MS clustered VM's on the same physical box. I've read that clustering between ESX serv... See more...
We have 2 ESX 2.5.2 servers, 1 production & 1 developement, and one the developement server we have serveral MS clustered VM's on the same physical box. I've read that clustering between ESX servers won't carry over when you do an upgrade to VI3, but will VM's MS clustered on the same physical ESX box have issues as well? The shared disks are on an EMC CX300 SAN that is formatted in VMFS with the ESX server in a storage group using RAID-5 disks. The SCSI controller is set to virtual and the disks are in persistent mode. They are all .vmdk disks, no raw luns. Any insight would be appreciated, Jonathan
Yes, we just didn't want the upgrade of the Dev server to mess up the Luns on the Production side since it can see them. Jonathan
We have 2 ESX 2.5.2 servers and 2 EMC CX300 SANS, 1 production & 1 developement. The ESX developement server can see LUNS on both the Prod SAN and the Dev SAN. The production ESX can only see LUN... See more...
We have 2 ESX 2.5.2 servers and 2 EMC CX300 SANS, 1 production & 1 developement. The ESX developement server can see LUNS on both the Prod SAN and the Dev SAN. The production ESX can only see LUNS on the Prod SAN. The shared disks are on an EMC CX300 SAN that is formatted in VMFS with the ESX server in a storage group using RAID-5 disks. Do I need to configure the Dev ESX server not be able to see the Prod SAN if I don't won't to affect the Prod side when I upgrade the Dev server to VI3 and upgrade the VMFS? Thanks, Jonathan
They are all .vmdk disks, no raw luns.
The shared disks are on an EMC CX300 SAN that is formatted in VMFS with the ESX server in a storage group using RAID-5 disks. The SCSI controller is set to virtual and the disks are in persistent... See more...
The shared disks are on an EMC CX300 SAN that is formatted in VMFS with the ESX server in a storage group using RAID-5 disks. The SCSI controller is set to virtual and the disks are in persistent mode. Let me know if you need any other information I haven't provided. Thanks! Jonathan
We have 2 ESX 2.5.2 servers, 1 production & 1 developement, and one the developement server we have serveral MS clustered VM's on the same physical box. I've read that clustering between ESX serv... See more...
We have 2 ESX 2.5.2 servers, 1 production & 1 developement, and one the developement server we have serveral MS clustered VM's on the same physical box. I've read that clustering between ESX servers won't carry over when you do an upgrade to VI3, but will VM's MS clustered on the same box have issues as well? Thanks, Jonathan