MUI?

[jared1]

New install 3.0.1 with AX-150 FC SAN. AX documentation for ESX calls for configuring the HBAs as dedicated or shared.

It gives two options:

vmkpcidivy -i[/b] (recommended) will not run - I get "[i]vmkpcidivy is deprecated, it is only provided for compatibility with vmkpcidivy - q vmhba_devs[/i]."[/b]

Use the VMware Management Interface. I connect to the internal ip I get the VMware ESX 3 Welcome page and I click Log in to Web Access (192.168.x.x/ui) I get [b]"page cannot be displayed."[/b][/i]

How should I configure this option? Why aren't these features working?

Thanks in advance for your help.

Jared

[esiebert7625]

Make sure you are using https:///ui instead of http

I've seen a weird bug that will sometimes cause the page to not display.

Alternately you can load the VI client on a workstation and connect to it from that

[jared1]

Ok, so I thought the https: was going to do it, however after the certificate warning, it still says page cannot be displayed.

I haven't found the option in the VI client.

Will I ever need to have the MUI or can everything now be done through the VI client?

[Dave_Mishchenko]

It might help to add the URL to the local intranet security group in IE.

For the VI client, you can do everything you need in it (the web interface just provides basic management). You can get the VI client bygoing to http://ip_address/ and you'll see a link to download the virtual infrastructure client.

[esiebert7625]

Check out this post, you might try logging into the Service Console and restarting the web service.

http://www.vmware.com/community/thread.jspa?messageID=528517&#528517

[jared1]

I have restarted the web service with no change.

Where can I make the changes for the HBAs in the VI client?

[Dave_Mishchenko]

Go to the configuration tab \ storage adapters.

[jared1]

I'm sorry for being ignorant here, but under Configuration \ Storage Adapters my only options are rescan, manage paths and hide luns - no where to specify dedicated or shared on the HBAs.

What do I need to choose, highlight, etc?

[esiebert7625]

I don't think you can set that there. You'll probably have to do it from the Service Console....

The division of hardware with vmkpcidivy is no longer needed. All hardware is handled by the VMkernel.

Vmkpcicheck is no longer needed for the same reason.

Vmkbootcfg has been replaced by esxcfg-boot. Basically configures boot option for ESX.

Vmkchdev has been replaced by esxcfg-init.

“Vmware-cmd –l” listed every registered VM on the box. With ESX3, if a VM isn’t running on the box it is not listed with this command.

Old Command New Command Notes

vmkpcidivy esxcfg-boot -p esxcfg-boot always requires at least one argument.

vmkpcidivy -i esxcfg-boot -p \[-s] Only the installer should use -s. To deal with new devices, only pass -p.

vmkpcidivy -d <root-device> esxcfg-boot -d <root-device>

vmkpcidivy -b <boot-loader> No longer needed- only GRUB is supported.

vmkpcidivy -convertnetscripts ethN/vswifN conversions handled automatically on reboot now.

vmkpcidivy -k esxcfg-dumppart -s <vmhbaN:N:N:N>

vmkpcidivy -q vmkdump_part esxcfg-dumppart -l

vmkpcidivy -q vmkdump_dev esxcfg-dumppart -f

vmkpcidivy -q vmkdump_prev esxcfg-dumppart -t/-c

vmkpcidivy -q vmfs_part vmkfstools -P, I think. See vmkfstools usage for exact option.

vmkpcidivy -q vmkmod esxcfg-boot -q vmkmod

vmkpcidivy -q vmhba_devs esxcfg-vmhbadevs

Other vmkpcidivy Obsolete or no longer needed from a supported tool. Internal use only: vsish may have what you need.

vmkbootcfg esxcfg-boot -b esxcfg-boot always requires at least one argument.

vmkbootcfg -q esxcfg-boot -q boot

vmkbootcfg -g esxcfg-boot -g

[Dave_Mishchenko · Accepted solution]

The dedicated / shared setup is no longer part of the setup for ESX. If you want to add some SAN storage and the LUN has been created and zoned properly, you'll simply click on the HBA and do a rescan. Once you've done that do to Configuration \ storage and click on add storage.