Reply to Message

View discussion in a popup

Replying to:
admin
Immortal
Immortal

Passing this along from one of our Engineers:

In a perfect world you'd want  to do both of those things.

You want to isolate vMotion  traffic in it's own broadcast domain - i.e. dedicated non-routable VLAN  or a dedicated physical switch. And ideally, you'd want at least one  dedicated physical network adapter for vMotion as it can be quite  'bursty' and may increase latency to other network services during  migrations.

This may  not always be possible - especially with blades where NIC counts are  typically on the low side. Having vMotion isolated into it's own VLAN is  the more important of the two considerations if you can't do both.

It  sounds like you've done all of the reasonable remediation required to  limit this problem though - with network resource pools, load based  teaming etc.