esxcli swiscsi nic add -n vmk# -d vmhba##

You’ll need to SSH into the server to do that, and su – (change to roots home as that is the only place you can issue that command)

The reason they are on separate subnets is because that is simply the way the MD’s handle multipathing. no more, no less.

Also, dynamic discovery does what is called a iSCSI send request. You technically only need to put in one IP – your long boot times could be attributed to this. The storage array will report back all available iSCSI ports. Put in one from each controller on separate NICs (or subnets if you have one nic for iSCSI)

Just an opinion – using broadcoms as HBA’s is horrible. Lots of problems. Use the software iSCSI init.

For you equallogic guys that need to change the network binding order so you have unused nics, you should also change the lowest vmk# port to be a storage heartbeat and have access to both nics. Then create another “real” VMK for iSCSI… storage heartbeat has to be the lowest numbered vmk.

The 2nd problem you found is not clear in the Update 1 release notes, that it has fixed it ONLY the “unused adapter problem”.

Can anybody clarify this, as we have some strange problems with Active/Standby on the vmotion/ management network?

Bob

I have not seen a software package that will emulate an internal IDE or SATA drive as a USB. However, I have seen IDE-to-USB and SATA-to-USB converters. Many mother boards have internal USB pin-outs. I’m sure you could get an adapter installed internally for users who need this on their desktop to support these drives.

My next question is, is there any software out there that will emulate a USB cd drive and redirect that to the physical drive?

Regards Robert

It seems to be fixed by removing the 2 vmotion, restart management and recreate vmotion.

I couldn’t find any KB around this at vmware.com

Equallogic is configured as a single subnet because you cluster shelf’s together not typical of an iSCSI SAN.

The lower end Dell PowerVault is configured to have each port on a different subnet.

after a few tests, the problem does not accure anymore if i left the Gateway for the new configured vmkernel port (vmotion) blank (so it has the GW from the management network) . this is like the configuration in ESX(i) 4

br
Stefan

Thanks for the article

1.) Add new PP/VE to your VUM Update Repository (Update Manager –> Patch Repository –> Import Patches (top right).
2.) Remove old PP/VE from update baseline, and then add new PP/VE to same baseline, – or – create a new baseline just for PP/VE. Works either way – just a matter of preference for your environment.
3.) Manually remove old PP/VE from hosts. Syntax is like this:

# vihostupdate –remove –bulletin EMC-PP5.4.0.00.00- –server

4.) Reboot host.
5.) Scan for updates in VUM, apply new baseline with PP/VE extension.
6.) Reboot host again.
7.) Re-apply license (re-host first on Powerlink if you did a host re-install and are using unserved licenses)

Good luck and let us know how it goes. If you need additional help, I’ve got a great team in the DC area that can support you.

Any thought on what would need to be done if you wanted to upgrade PP/VE 5.4 SP2 to the next version using VUM? Would that be a separate baseline or what? Can you uninstall PP/VE via VUM?

For people that deployed PP/VE 5.4 SP1 using VUM. Have you tried upgrading to PP/VE 5.4 SP2 via VUM?