joeflint
Enthusiast
Enthusiast

Cisco Nexus Configuration

Jump to solution

Hi, questions on the Cisco Nexus 100v Configuration.

Firstly, the VSM will have three vNICs used for:

1. Control Interface - NIC1               

2. Management Interface - NIC2     

3. Packet Interface - NIC3

Does the Managament interface belong on the same VLAN as VMconsole (or service console) because it is used to communicate with vCenter and ESX hosts for management traffic?

Do IP addresses need to be assigned for the Control and Packet Interfaces?

Thanks

0 Kudos
1 Solution

Accepted Solutions
lwatta
Hot Shot
Hot Shot

When you use L3 control we encapsulate control and packet traffic onto the mgmt interface by default. The only IP you need is the IP you've assinged to the mgmt 0 interface. Control and packet interfaces never get used and never need an IP.

louis

View solution in original post

0 Kudos
3 Replies
LFC
Enthusiast
Enthusiast

In our configuration, we use a Virtual vCenter, which resides on VLAN 175, our ESXi hosts Management Port is on 176.

We have configured our Nexus 1000V in L3 mode (L2 mode in not advised anymore). Our 1000V VSM's have 3 NICs' which are all in VALN176 and communicate with the VEMs (on the hosts) using a L3 routed connection.

This was the "Best practice" solution provided by our Cisco partner company, and is what we have adopted as our standard for all Nexus 1000v installations, except in very high security environments, where Control and Packet are moved to non-routable L2 VLANs

Hope this helps

joeflint
Enthusiast
Enthusiast

Thanks LFC, regards to contorl & packet Nics - do these require IP addresses to be assigned also?

0 Kudos
lwatta
Hot Shot
Hot Shot

When you use L3 control we encapsulate control and packet traffic onto the mgmt interface by default. The only IP you need is the IP you've assinged to the mgmt 0 interface. Control and packet interfaces never get used and never need an IP.

louis

View solution in original post

0 Kudos