cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4321
Views
0
Helpful
1
Replies

Need some clarification as to the physical uplinks

cougar694u
Level 1
Level 1

I'm unclear as to the actual configuration needed for a Nexus 1kv.

Taken from another post on here:

You need to have at least one nics configured for each VEM module.  This is how each VEM communicates with the VSM.  Without an uplink the VEM module can never get programmed by the VSM.

On one of my ESX hosts, I have two physical NICs (it's a blade).  When setting up the VSM, we created the packet, control, and mgmt port groups on the standard local vswitch.  After getting everything installed and setup, we were able to see the VEM and the secondary VSM.

We then migrated the vmk0 to the VSM on a port-profile we created and we still had connectivity.  After, we migrated all vmnics over to the nexus DVS and set the packet and control NICs to use port-profiles we set up on the nexus.

When we did, we no longer had connectivity to the VEM (if we did a show mod).  Once we moved the control and packet back to the local vswitch and assigned a vmnic to it, it all came back.

Are we required to use the local vswitch for the packet and control ifs from the nexus, and dedicate a single physical NIC for this purpose?

1 Reply 1

Robert Burns
Cisco Employee
Cisco Employee

No you're not required to use the vSwitch at all.  Sounds like you just haven't configured a Port Channel on your System Uplink port profile.

Assuming your upstream switch supports CDP add the following line your System uplink.

"channel-group auto mode on sub-group cdp"

**If you upstream switch does NOT support CDP (ie. Flex-10), then still add the command above, you're need to manually set the sub-group IDs

Ex.

If you have VEM 3, and VEM 4 here's how you would assign a sub-group to the Ethernet interfaces

n1000v-1(config)# int eth3/1
n1000v-1(config-if)# sub-group-id 0

n1000v-1(config)# int eth3/2
n1000v-1(config-if)# sub-group-id 1

n1000v-1(config)# int eth4/1
n1000v-1(config-if)# sub-group-id 0

n1000v-1(config)# int eth4/2
n1000v-1(config-if)# sub-group-id 1

If this doesn't fix your issue please post your VSM config.

Thanks,

Robert

Review Cisco Networking for a $25 gift card