I may be wrong, but VCB might have a problem if a VM has virtual disks on 2 different LUNs. Can any one verify that? If that is the case, can you move all of the virtual disks to one director...
See more...
I may be wrong, but VCB might have a problem if a VM has virtual disks on 2 different LUNs. Can any one verify that? If that is the case, can you move all of the virtual disks to one directory (also rename them inthe process)
Turn up logging (use -L 6) and see which host it is trying to reach. I have a situation where VCB is trying to contact the wrong host for the VM that is being VCB'd.
Hey guys, Please correct me, but I thought IP hash was only applicable when using etherchannel trunks on Cisco switches, and that this was not possible to do across multiple switches. Mayur
James: On the portfast option, be sure that your network guys use the option of Spanningtree portfast trunk[/b]. Without the trunk option, cisco switches will not enable portfast on a trunk'd...
See more...
James: On the portfast option, be sure that your network guys use the option of Spanningtree portfast trunk[/b]. Without the trunk option, cisco switches will not enable portfast on a trunk'd port. With this option enabled, your recovery time should be only 2 or 3 seconds. Mayur
Jeff: I stand corrected. You are correct. It seems to send the copy instructions to the ESX Hosts and then the copy happens between the 2 ESX hosts. Mayur
Wouldn't using FastSCP to copy between ESX hosts take longer?? I mean Fast SCP has to pull the data over the network to your PC, then send it to the target Host. Anyway, I like to use scp. A...
See more...
Wouldn't using FastSCP to copy between ESX hosts take longer?? I mean Fast SCP has to pull the data over the network to your PC, then send it to the target Host. Anyway, I like to use scp. Although you can export the vmdk files to smaller chunks, from what I understand, the scp client in ESX has been modified to handle large files. I beleive the FTP lient has also. Mayur
I have a customer that is using it. It seems to work well, reliability was good, but it did seem a little slow. But their network was not configured ideally, so I'm sure that added to the perfo...
See more...
I have a customer that is using it. It seems to work well, reliability was good, but it did seem a little slow. But their network was not configured ideally, so I'm sure that added to the performance (or lack there of.) The one thing that I had problems with was that with 4 hosts connected to it, and each host being presented all of the LUNs, every time we wanted to work on the Promise (like adding disks, creating new LUns,etc..), it seemed that if we didn't stop the hosts from accessing the disks, the Promise would lock up.-- Only a cold restart would fix this.. Good Luck Mayur Patel
Earlier today, we had a situation where our storage guys were pulling cables and though they did one cable at a time, we lost access to the Datastores. We looked in the vmkernel & vmkwarning lo...
See more...
Earlier today, we had a situation where our storage guys were pulling cables and though they did one cable at a time, we lost access to the Datastores. We looked in the vmkernel & vmkwarning logs and see where the links were lost, but I don't see where the kernel tried to fail over. Does anyone know how the attempt to fail over would be logged & to which file? Mayur
According to the configurations maximums doc (http://www.vmware.com/pdf/vi3_301_201_config_max.pdf), you need to have an 8mb block size to have a max file size of 2TB. Mayur
SO, you could leave it this way, but is is not recommended to do so. This is basically saying that when this LUN was formatted and a signature written on it, it was presented as LUN X, now th...
See more...
SO, you could leave it this way, but is is not recommended to do so. This is basically saying that when this LUN was formatted and a signature written on it, it was presented as LUN X, now this LUN is appearing as LUN Y. I don't know about the MSA 1000, but in the EVA (HP SANs) in the management GUI, when I present a LUN to a HOSt, I can choose which LUN I would like it to be presented as to that host. I alway make sure that all of the hosts that I present this LUN to have the same LUN. Anyone know how to do this for the MSA 1000??
THe "..resignaturing.. & .. snapshot LUN.." message, makes me think that there is a LUN # mismatch. To test this, go to the Configuration Tab in the Infrastructure Client, go to Advanced Settin...
See more...
THe "..resignaturing.. & .. snapshot LUN.." message, makes me think that there is a LUN # mismatch. To test this, go to the Configuration Tab in the Infrastructure Client, go to Advanced Settings, click on LVM, and change LVM.DisallowSnapshotLun from 1 to 0. If after changing to 0, you can see the LUN, then there's a definite mismatch in LUN number from when the LUN was first created to now. If possible, I would unpresent the LUN from both Hosts (through the SAN management interface) and re-present the LUN making sure to use the same LUN for both of the hosts. Mayur
SO, you will have to either put a physical nic on the 4.x subnet or set up the port at the physical switch as a trunk for the vlans for both the 5.x & 4.x subnets. If you go the trunk route, y...
See more...
SO, you will have to either put a physical nic on the 4.x subnet or set up the port at the physical switch as a trunk for the vlans for both the 5.x & 4.x subnets. If you go the trunk route, you have to create additional port groups in your virtual switch for each vlan. Mayur
No, I don't believe there is anything like that. As far as I know, it's basically honor system once you get the license keys from VMware (or license files for VI 3) Mayur
That's the ideal congiuration. Although, you can put vmotion nics on a network shared with other traffic, but it's better to isolate the network traffic, you'll get a better ratio of success. ...
See more...
That's the ideal congiuration. Although, you can put vmotion nics on a network shared with other traffic, but it's better to isolate the network traffic, you'll get a better ratio of success. In ESX 3.x, some guys even put the console nic and vmotion on the same vswitch, with 2 uplinks(pNICS) connected and separate the traffic via VLAN tags. I prefer to separate the networks personally.
Guys, I did have a case open with VMware, but I couldn't wait for them to try to solve it. I ended up doing cold migrations so that I could keep my project moving. If anyone finds out w...
See more...
Guys, I did have a case open with VMware, but I couldn't wait for them to try to solve it. I ended up doing cold migrations so that I could keep my project moving. If anyone finds out what might be causing this, please keep this thread updated. Mayur
for vmotion: On the SAN - your ESX hosts have to be able to see the same LUNS, so that when the running process of a VM is transferred from one to another, there's no need to copy the vmdk fil...
See more...
for vmotion: On the SAN - your ESX hosts have to be able to see the same LUNS, so that when the running process of a VM is transferred from one to another, there's no need to copy the vmdk files. On the LAN - you should dedicate a Gig NIC on each host for this purpose. I deally they would be connected in a private network so that there's no "unnecessary" traffic on that segment. Virtual Center doesn't need to be on the VMotion network, nor does it need to be on the SAN. I t only needs to be able to communicate to the ESX Host through port 902 (that's the port for the Virtual Center Agent that get's installed on the ESX host when you add it to VC.) Hope this helps!! Mayur