07-23-2015 02:28 AM
In Nexus1000v, the ethernet X/Y and Port-Channel A/B are created automatically when migrating the vmnic to vDS in vcenter,
Several questions:
1. Why Port-Channel is created??
2. What's the different between Port-Channel and Ethernet in Nexus1000v??
3. Can I associate vem directly to Ethernet??
4. I'm using B200M3, I can create many vmnic for different purposes. In that sense, Can I allocate vmnic into different port-channel groups per vem??
5. Can I change to MTU size?? Where should I change it??
==============================================
port-profile type ethernet UP-LINK
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 1-3967,4048-4093
switchport trunk native vlan 1
channel-group auto mode on mac-pinning
no shutdown
system vlan 1,40
state enabled
interface port-channel3
inherit port-profile UP-LINK
vem 4
interface port-channel4
inherit port-profile UP-LINK
vem 3
interface mgmt0
ip address 192.168.40.10/24
interface Vethernet1
inherit port-profile system-uplink
description VMware VMkernel, vmk0
vmware dvport 609 dvswitch uuid "35 a7 11 50 68 d8 d3 df-14 ba d6 0c 50 27 9e 46"
vmware vm mac 0025.B500.0008
interface Vethernet2
inherit port-profile vlan1
description VMware VMkernel, vmk0
vmware dvport 672 dvswitch uuid "35 a7 11 50 68 d8 d3 df-14 ba d6 0c 50 27 9e 46"
vmware vm mac CCEF.48B4.A49C
interface Ethernet3/1
inherit port-profile UP-LINK
interface Ethernet3/2
inherit port-profile UP-LINK
interface Ethernet4/4
inherit port-profile UP-LINK
N1000v# module vem 3 execute vemcmd show port
LTL VSM Port Admin Link State Cause PC-LTL SGID Vem Port Type
17 Eth3/1 UP UP FWD - 561 0 vmnic0
18 Eth3/2 UP UP FWD - 561 1 vmnic1
49 Veth1 UP UP FWD - 0 1 vmk0
561 Po4 UP UP FWD - 0
* F/B: Port is BLOCKED on some of the vlans.
One or more vlans are either not created or
not in the list of allowed vlans for this port.
Please run "vemcmd show port vlans" to see the details.
08-03-2015 09:02 PM
1- You are using the command "channel-group auto mode on mac-pinning"
2-Can you show me what two parts of the configuration you are talking about? That will help me give you a more accurate answer
3-You can create a port-profile type "ethernet" which basically means that the port-profile will be use on an physical port and then go to the VEM and choose that port-profile (hope I am making my point here, otherwise, let me know)
4-You can create sub-groups and then assign the vmnics to those subgroups. More info here: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_3/port_profile/configuration/guide/n1000v_port_profile/n1000v_portprof_5channel.html#wp1119128
5-If desired, the MTU can be changed on uplink por-profiles (type ethernet, not vethernet)
I hope that helps... If I am mistaken somewhere and anyone else feels like it should be corrected, feel free to do it.
-Kenny
08-20-2015 07:21 AM
The channel-group auto mode on mac-pinning command turns on vPC MAC pinning. VEM has multiple external connections (host's physical NIC aka vmnic) on each host. These are the EthernetX/Y ports in the config (X is the VEM number just like a module number in a modular switch). If these pNICs are connected to multiple non-vPC-capable switches we need redundancy but we cannot load-balance with traditional port-channels. vPC MAC pinning creates a pseudo port-channel, it shares the traffic between the physical links without requiring a cross-chassis port channel on the upstream physical switches. You can see one port channel per VEM (i. e. per host) in the config.
See the MAC Pinning chapter in the config guide.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide