VMM Domain for which networks?

[KVS7]

Currently, I have created VMM domains to push port groups create by the APIC and pushed down to the vDS on vCenter (aka VMM) for everything except management. However, I'm building a new site with new protocols like NFS and iSCSI boot which will require a new vDS due to new uplinks and I feel like creating two more VMM domains for each new vDS in vCenter is kind of a pain.

My question is if these should also be controlled by the APIC or if there's no real caveats to storage protocols being controlled by the APIC or if it's better to leave these on the vDS (non VMM).

Thanks

[wajidhassan · Accepted solution]

Hi @KVS7 ,

For storage networks like NFS and iSCSI, it’s generally better to keep them on a traditional vDS, outside of the APIC-managed VMM domain.

APIC and VMM integration is ideal for VM networks (user traffic, app tiers, etc.), but for storage protocols, direct control from APIC doesn't add much benefit and can introduce unnecessary complexity. These types of traffic often have specific requirements around QoS, flow control, and failover that are better handled directly in vCenter or through traditional methods.

So unless you have a strong reason to manage storage traffic via APIC, keeping it on a non-VMM vDS is a clean and reliable approach.

Hope this helps!

[KVS7]

Good points. Thanks. I will keep them separate.