hmm... If they are following their best practice, as network engineers/consultants/specialists etc... we should probably be helping them achieve that. But I do understand where you are coming from. Bandwidth is money!
What tests have you guys done to prove that the VMotion nic sits at 0-1% - have you guys actually monitored what happens when you perform VMotion? My experience is you need the bandwidth available to have the best performance. Any slowness can be catastrophic! (to the end user/application or process)
So in the environment I work in, we actually have 2Gb portchannel dedicated link for VMotion to each ESX host!
Remember, Solarwinds Orion polls at certain times e.g. every 1min or every 5min - its not actively monitoring as such, its not garunteed to capture the spike or burst if there is one, hence you wouldn't see it.
Lets look at it this way too....
There is an application I am using, which connects to the VM - lets take Exchange 2010 as an example. If for some reason there was a failure or not enough resources on the ESX host itself and made a decision to VMotion, it VMotions to a different ESX host. But that time, my PC and Outlook disconnected and got effected or crashed? why? because it took a bit more time to VMotion - bandwidth wasn't there to help transition 'fast enough'
It may not necessarily be the case when I have enough B/W / dedicated links for a VMotion to take place quicker. Probably wont notice any difference, or perhaps a reconnect?
The more B/W, the more quicker a VMotion process will be, the less impact it will have on services.
PS - 1% seems quite low - unless your traffic profile is low and you dont have much running on your network or very few VM's on the ESX host. Check the reference B/W in Orion to see if it matches the real interface bandwidth
Please rate useful posts & remember to mark any solved questions as answered. Thank you.
Please rate useful posts & remember to mark any solved questions as answered. Thank you.
