Best Practice: Virtual Connect config in OneView?

[MattGG]

When deploying 2 VC modules in c7000 using Virtual Connect (for VMware blades) we would create explicit VLAN networks for the A and B side and then associate them with their respective and A and B VC module.   Is this the recommended way to do it in OneView or can I just create a single SUS that contains all uplinks from the A/B modules and create a single network for each VLAN (no A/B VLAN)?

The vSphere vSwitches will be configured to use the default Port Based ID load balancing.

Thanks,

-MattGG

[ChrisLynch · Accepted solution]

The short answer is yes. I would encourage you to review the HP OneView Deployment and Management Guide found on the Enterprise Information Library (http:\\hp.com\go\oneview\docs), as it covers that and many other topics.