I'm hung up on a few items, even after trying multiple suggestions in these forums. Having tried on my own, I'm now throwing myself to your collective mercy...
I'm trying to do the following, using the templates available in the UDA.
1. Check off the "Enable VMotion" box to enable vmotion. I've tried the vimsh -e -n 'blah blah portgroup2' but it didn't work. I also tried sleeps before and after, as well as restarting mgmt-vmware. Any ideas?
2. Set the default gateway for vmotion. It comes up blank. As a side question, this should just be set the same as the vmotion IP (or any other IP on the same segment), right? It's my understanding that vmotion uses broadcast, so it doesn't really matter what the GW is, as long as they're the same on all participating ESX boxes, right?
3. Script the rolling failover setting on the nic teaming page. I tried one command that I found on here somewhere, but it didn't work. Not much scripting info on this one...
4. This one is more out of curiosity... I added 2nd/3rd nameservers to resolv.conf in the script (which does work) but they don't show up in the VI3 client when looking at "DNS and Routing." However, when I click "Edit" I do see that they're in there. The main DNS and Routing pages just show dashes for each one.
BTW, I second the motion from one of the posts that we get a dedicated section for scripted installs! This is some powerful stuff, but it's sometimes difficult to find what you're looking for in the main forum.
Thanks, all!
Wow, no replies to a thread that has points to assign? ![]()
I figured I'd give this a little bump to see if I can get any love...
1. The method you used should work but be careful about one thing, vimsh only "works" when ESX "webservices" are working, so usually after restarting service mgmt-vmware, that starts it in background and says it's "ok" but it still loading in background so usually everyone uses a sleep of about 20s the time it launches.
esxcfg-vswitch -A VMotion vSwitchX
esxcfg-vmknic -a VMotion -i <vmotion_ip> -n <vmotion_netmask>
esxcfg-route <vmotion_gateway>
service mgmt-vmware restart
sleep 20
vimsh -n -e "/hostsvc/vmotion/vnic_set portgroupX" => get this from esxcfg-vswitch -l
2. Answered with 1 ![]()
3. the rolling failover setting can be configured through vimsh too.
vimsh -n -e "hostsvc/net/vswitch_setpolicy --nicteaming-rollingorder=<bool>"
4. Probably only shows the first nameserver, just a "cosmetic issue"
Hope it helps,
1. I think I probably had a brain fart on this one. I'm testing this in an isolated environment with no available VC server, so that's probably why the "Enable VMotion" box is not being checked. Without a VC/LM server, it's not licensed! You did show me the esxcfg-route command though, so you still helped on this one.
2. So, do you agree that this can be pretty much any ip address, as long as it's on the same segment and is used by all participating ESX boxes?
3. I still can't get this to work, and I tried a variety of different variations of the command you suggested. If you're using this command in a script, would you ming cutting and pasting it here?
4. I guess so. As long as it works. ![]()
another tip => all changes done by vimsh will be seen on the vi client ui only if you do a : vimsh force refresh.
vimsh -n -e "hostsvc/net/refresh" ![]()
Then you would see appearing "immediately" the changes into vi client ![]()
Nope, still no love on the rollingorder setting. Can you cut & paste a sample from your script? Maybe include the lines leading up to it as well?
I'm at home so tested it on a esx into vmware workstation works fine. (2x intel e1000 nics)
vimsh -n -e "hostsvc/net/vswitch_setpolicy --nicteaming-rollingorder=true vSwitch0"
vimsh -n -e "hostsvc/net/refresh"
After that you will find Rolling failover set to "Yes" into your vSwitch configuration tab.
The damn thing still isn't working, so I think I'm going to shelve this for a little while. I appreciate your assistance!
what's your issue exactely ?
No error, but the rolling failover remains "No."
