N1K allows for pin preferencing in the vethernet port profiile. As of version 1.4a and later you can now set the "order" of failover sub groups.
Ex. Let's say you want to do some traffic engineering and keep your Service Console/Management traffic & Vmotion traffic pinned to separate uplinks. We know we can use sticky pinning to force these virtual interfaces to separate sub group uplink interface, but what happens when there is a failure with one of these links? Previously, when a sub group member failed with pinned interfaces it would be dynamically re-pinned in a round-robin fashion to the remaining operational members. New functionality was added to force the order of which backup sub groups will be utilized.
To specify multiple sub-groups for failover you can use the following pinning command in either the vEth interface or Port profile level.
1000v(config-if) pinning id backup
So let's say we had four uplink vmnics 0 through 3. We'd like to keep our management and vmotion traffic separated if possilbe.
vmnic0 = subgroup ID 0 (primary for management)
vmnic1 = subgroup ID 1 (secondary for mangement, tertiary for vmotion)
vmnic2 = subgroup ID 2 (secondary for vmotion, tertiary for management)
vmnic3 = subgroup ID 3 (primary for vmotion)
Our port profiles might look like this.
port-profile type ethernet system-uplink
vmware port-group
switchport trunk allowed vlan 1-3967,4048-4093
switchport mode trunk
channel-group auto mode on mac-pinning
no shutdown
system vlan 10, 3001-3002
state enabled
port-profile type vethernet management
vmware port-group
no shutdown
switchport mode access
switchport access vlan 10
system vlan 10
state enabled
pinning id 0 backup 1 2
port-profile type vethernet vmotion
vmware port-group
no shutdown
switchport mode access
switchport access vlan 99
state enabled
pinning id 3 backup 2 1
Thank You,
Dan Laden
Cisco PDI Data Center
Want to know more about how PDI can assist you?
http://www.youtube.com/watch?v=4BebSCuxcQU&list=PL88EB353557455BD7
http://www.cisco.com/go/pdihelpdesk
