Control Packet Management VLANs

[novo_rafael]

Hi,

I have 2 questions regarding these VLANs:

Question 1. I have a ESX with 6 NICs:

- 2 for Service Console

- 2 for VMs traffic

- 2 for VMotion.

Only the 2 NICs used for VM traffic wil configured as Uplinks in Nexus 1000v (the other 4 NICs will remain in the standard vSwitch)

By my understanding I should configure

- Management VLAN for the 2 NICs used in Service Console

- Packet / Control VLANs for ths 2 NICs used as uplinks

Is this correct?

Question 2. Cisco used to recommend three separate VLANs, but now it seems to have changed for a single VLAN recomendation.

What is the implications of have multiple or single VLAN for Nexus 1000v?

Regards,

Rafa

[lwatta]

Rafa,

The Management interface (nic2 in the VSM VM) just needs to be on a subnet that can talk to vCenter and the rest of the world for SSH/telnet access. If you want to put this on an existing VLAN thats fine. You don't need to create a new VLAN for Management if you don't need it.

Control and Packet will need to be on the Uplinks you add to the Nexus 1000V. These can be combined to into one vlan or seperate vlans.  The reasoning was that at first there was concern about allowing control traffic on the same vlan as data. We've since eased up on the requirement and simply recommend that control be on a network where there is adequate bandwidth and low latency.

louis