I wouldn't have though this setting would be in the SQL DB...
Because if you moved an ESX host from one datacenter to another - you would potentially loose a lot of configuration information...
That said - for all i know it could well be in the DB!
We wouldn't have this grief if there was a switch on the esx-vmknic command!!! (hint, hint) 
Regards
Mike
I discussed the COS commands with VMWare support
several times with several different issues during
and after the beta period.
There is a disconnect somewhere between what VIC
shows and what COS shows. The commands are there in
COS, but VMWare support told me not to use them
because VIC does more behind the scenes.
I can use the commands and make things work, but the
VIC doesn't always show the updates.
My last message to them was referring to a situation
where I no longer had network access from VIC to ESX
and had to use the console commands. If that
happens, my only option is COS from KVM. There has
been no response on that message as of yet.
that's interesting post on two counts. I do feel we are being discouraged from using the command-line... it bugs me when command's don't have man pages... grrrr....
I've did some inplace upgrades with ISO's & tarballs - in Beta/RC1 and found my COS networking was "shafted" (that's a technical terms) so spent sometime getting to grips with the esxcfg commands to correct this...
I used stuff like this (without an ilo I was using a KVM to get to the "shafted" machine)
esxcfg-vswitch -a vSwitch0
esxcfg-vswitch -p "Service Console" vSwitch0
esxcfg-vswitch –L vmnic0 vSwitch0
esxcfg-vswif –a vswif0 -p "Service Console" i 192.168.2.102 –n 255.255.255.0
then editing /etc/sysconfig/network to set the default gateway and device used...
If your interested im in the process of writing a cmd-line guide...
Regards
Mike
that would be very useful...
2b honest - I've never monkied around with kickstart - because i hardly ever have to mass deployments - just resets of my various boxes when I screw them up...
(that's sounds reassuring doesn't it)
Mike Laverick
98% of what I have learned is from screw-ups... this does mean I screw about 98% of the time...\!!!
that's interesting post on two counts. I do feel we
are being discouraged from using the command-line...
it bugs me when command's don't have man pages...
grrrr....
I've did some inplace upgrades with ISO's & tarballs
- in Beta/RC1 and found my COS networking was
"shafted" (that's a technical terms) so spent
sometime getting to grips with the esxcfg commands to
correct this...
I used stuff like this (without an ilo I was using a
KVM to get to the "shafted" machine)
esxcfg-vswitch -a vSwitch0
esxcfg-vswitch -p "Service Console" vSwitch0
esxcfg-vswitch –L vmnic0 vSwitch0
esxcfg-vswif –a vswif0 -p "Service Console" i
192.168.2.102 –n 255.255.255.0
then editing /etc/sysconfig/network to set the
default gateway and device used...
If your interested im in the process of writing a
cmd-line guide...
Regards
Mike
We are definitely being discouraged from using the command line. They don't want us to, but there are times when it is not only convenient, but absolutely mandatory (loss of network connectivity).
esxcfg-route is the routing command for VMKernel.
In order to get the COS routing to work, I simply used route
route add default gw X.X.X.X
If you look at vSwitch definitions (esxcfg-vswitch -l) in the COS, they will list 32 ports. There are supposedly 8 "reserved" ports that aren't shown in the VIC. If you look at the same switch in the VIC, it shows only 24 ports. The GUI is supposed to be "correct" according to VMWare. I'm not sure why they would want them to be different. It only causes more confustion.
Also, if you change the COS IP/NM/Routing from the command line, it will restore network connectivity, but the VIC still shows the old information. The COS command do not update the GUI. This was the source of my SR with VMWare. That's when they told me that the GUI does more than the console commands do (not that they would tell me what that actually is).
See my message above about enabling advanced options. There is still no guarentee that this will work however
At the COS level (esxcfg-*) there is no knowledge of VMotion, it can however flip the same bit that VC flipped, but whether that is the whole story on enabling VMotion, I don't know.