vPC between Nexus 3172TQ and Nexus 31108TC-V

[leptonius]

Hi guys!

I am trying to configure vPC between Nexus 3172TQ and Nexus 31108TC-V. The "show vpc" output from the Nexus 3172TQ displays that there are some "weird" vPC consistency issues:

Nexus-A# sh vpc
Legend:
(*) - local vPC is down, forwarding via vPC peer-link

vPC domain id : 101
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : failed
Type-2 inconsistency reason : QoSMgr Network QoS configuration incompatible
vPC role : secondary
Number of vPCs configured : 1
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Enabled, timer is off.(timeout = 240s)
Delay-restore status : Timer is off.(timeout = 30s)
Delay-restore SVI status : Timer is off.(timeout = 10s)
Operational Layer3 Peer-router : Disabled

vPC Peer-link status
---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ -------------------------------------------------
1 Po101 up 1,490,495

vPC status
----------------------------------------------------------------------------
Id Port Status Consistency Reason Active vlans
-- ------------ ------ ----------- ------ ---------------
103 Po103 down* failed Local card type does -
not match with peer's

Please check "show vpc consistency-parameters vpc <vpc-num>" for the
consistency reason of down vpc and for type-2 consistency reasons for
any vpc.

Nexus-A# show vpc consistency-parameters vpc 103

Legend:
Type 1 : vPC will be suspended in case of mismatch

Name Type Local Value Peer Value
------------- ---- ---------------------- -----------------------
STP Port Guard 1 Default Default
STP Port Type 1 Default Default
STP MST Simulate PVST 1 Default Default
Allow-Multi-Tag 1 Disabled Disabled
Vlan xlt mapping 1 Disabled Disabled
vPC card type 1 N3K N9K TOR
Allowed VLANs - 1-4094 1-4094
Local suspended VLANs - - -

Nexus-A# show port-channel summary
Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
b - BFD Session Wait
S - Switched R - Routed
U - Up (port-channel)
p - Up in delay-lacp mode (member)
M - Not in use. Min-links not met
--------------------------------------------------------------------------------
Group Port- Type Protocol Member Ports
Channel
--------------------------------------------------------------------------------
101 Po101(SU) Eth LACP Eth1/53(P) Eth1/54(P)
103 Po103(SD) Eth LACP Eth1/47(D)

The above vPC config works fine between Nexus 3172TQ boxes without any vPC consistency issues.

My question: 
Is vPC compatible between Nexus 3172TQ and Nexus 31108TC-V? If so, do I actually miss some "magic" steps to fire up the vPC between those boxes?

[Reza Sharifi]

Hi,

Usually, there is no issue with using vPC between different platforms. In your case, there is some QOS difference between the 2 platforms that is causing the inconsistency problem.

HTH

[leptonius]

Hi,

Yes, you are right. By default, there are some Network QoS configuration inconsistency between Nexus 3172TQ and Nexus 31108TC-V regarding vPC:

Nexus-A (Nexus 31108TC-V)

Nexus-B (Nexus 3172TQ)

Nexus-B# sh vpc consistency-parameters global

Legend:
Type 1 : vPC will be suspended in case of mismatch

Name Type Local Value Peer Value
------------- ---- ---------------------- -----------------------
STP MST Simulate PVST 1 Enabled Enabled
STP Port Type, Edge 1 Normal, Disabled, Normal, Disabled,
BPDUFilter, Edge BPDUGuard Disabled Disabled
STP MST Region Name 1 "" ""
STP Disabled 1 None None
STP Mode 1 Rapid-PVST Rapid-PVST
STP Bridge Assurance 1 Enabled Enabled
STP Loopguard 1 Disabled Disabled
STP MST Region Instance to 1
VLAN Mapping
STP MST Region Revision 1 0 0
Interface-vlan admin up 2 490,495 490,495
Interface-vlan routing 2 1,490,495 1,490,495
capability
QoS (Cos) 2 ([0-7], [], [], [], ([0-7], [], [], [],
[], []) [], [])
Network QoS (MTU) 2 (1500, 1500, 1500, (1500, 1500, 1500,
1500, 1500, 1500) 1500, 0, 0)
Network Qos (Pause: 2 (F, F, F, F, F, F) (F, F, F, F, F, F)
T->Enabled, F->Disabled)
Input Queuing (Bandwidth) 2 (100, 0, 0, 0, 0, 0) (0, 0, 0, 0, 0, 0)
Input Queuing (Absolute 2 (F, F, F, F, F, F) (F, F, F, F, F, F)
Priority: T->Enabled,
F->Disabled)
Output Queuing (Bandwidth 2 (100, 0, 0, 0, 0, 0) (100, 0, 0, 0, 0, 0)
Remaining)
Output Queuing (Absolute 2 (F, F, F, F, F, F) (F, F, F, T, F, F)
Priority: T->Enabled,
F->Disabled)

Here are default System QoS policies for the Nexus-A and Nexus-B respectively:

Nexus-A# sh policy-map system type network-qos

Type network-qos policy-maps
============================
policy-map type network-qos default-nq-policy
class type network-qos c-nq3
match qos-group 3
mtu 1500
class type network-qos c-nq2
match qos-group 2
mtu 1500
class type network-qos c-nq1
match qos-group 1
mtu 1500
class type network-qos c-nq-default
match qos-group 0
mtu 1500

Nexus-A# sh policy-map system type qos

Nexus-A# sh policy-map system type queuing

Service-policy (queuing) output: default-out-policy
policy statistics status: disabled (current status: disabled)

Class-map (queuing): c-out-q3 (match-any)
priority level 1

Class-map (queuing): c-out-q2 (match-any)
bandwidth remaining percent 0

Class-map (queuing): c-out-q1 (match-any)
bandwidth remaining percent 0

Class-map (queuing): c-out-q-default (match-any)
bandwidth remaining percent 100

Nexus-B# sh policy-map system type network-qos

Type network-qos policy-maps
============================
policy-map type network-qos default-nq-policy
  class type network-qos class-default
     match qos-group 0
     mtu 1500

Nexus-B# sh policy-map system type qos

Service-policy (qos) input: default-in-policy

Class-map (qos): class-default (match-any)
Match: any
set qos-group 0

Nexus-B# sh policy-map system type queuing

Service-policy (queuing) input: default-in-policy
policy statistics status: disabled (current status: disabled)

Class-map (queuing): class-default (match-any)
bandwidth percent 100

Service-policy (queuing) output: default-out-policy
policy statistics status: disabled (current status: disabled)

Class-map (queuing): class-default (match-any)
bandwidth percent 100

I tried to tailor Network-QoS policy on the Nexus 31108TC-V to somehow match default Network-QoS policy of the Nexus 3172TQ:

policy-map type network-qos my-nq-policy

  class type network-qos c-nq-default
      mtu 1500
system qos
  service-policy type network-qos my-nq-policy

After applying above config, the vPC type-2 inconsistency (QoSMgr Network QoS configuration incompatible) still remains.

Are there any ideas how to resolve vPC Network QoS inconsistency between boxes?