shared control, packet and management vlan

[christoph.brunner]

hey there...

i'm about to upgrade our virtualisation environment to 4.0(4)SV1(3a). now, i've seen that there are recommondation to share the control, packet and management vlan of nexus1000v. finally this i possible and i'm lucky about that.

the problem is that we have different nexus1000v installations as like the productive and the engineering site. so the data site of the vm's is seperated. the nexus communication is running on the out-of-band site. now, there is my question. does anybody know if i can share this vlan for different nexus installation or do i need one vlan per nexus installation.

it was a bad idea to use the same vlan's (control/packet) with the first release, but know it may have changed.

kind regards

chris

[abbharga]

Hi Chris,

You can use a common vlan for control and packet data beween the different N1K installs. All you need to make sure is the svs domain ID is different for each N1K install, if you have the same domain ID you can run into some major issues. To seprate N1K setup with same domain ID different vlans have to be used.

Hope this answers your query.

./Abhinav