Nexus5k New service policy for queuing in input direction

[dganta]

I am looking to define a  new  service policy that is different than the system policy on the vpc port-channel in Nexus for queuing. This VPC is connected to Cisco UCS, my question is what happens when I apply the new service policy for queuing in the input direction when I add it on one switch and later add it on vpc peer switch, as this will take a 2 seconds will there be any disruption in vpc port-channel as the Queuing service policy will be applied on primary vpc switch and then on secondary vpc switch. Please clarify

[mlund]

Hi

From this link

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_vpc_ops.html

The show vpc consistency-parameters global command lists all global consistency check parameters. Beginning with Cisco NX-OS Release 5.0(2)N1(1), QoS parameters have been downgraded from Type 1 to Type 2.

This example shows how to display all global consistency check parameters:

switch# show vpc consistency-parameters global

Legend:

Type 1 : vPC will be suspended in case of mismatch

Name Type Local Value Peer Value

------------- ---- ---------------------- -----------------------

QoS 2 ([], [3], [], [], [], ([], [3], [], [], [],

[]) [])

Network QoS (MTU) 2 (1538, 2240, 0, 0, 0, (1538, 2240, 0, 0, 0,

0) 0)

Network Qos (Pause) 2 (T, F, F, F, F, F) (T, F, F, F, F, F)

Input Queuing (Bandwidth) 2 (50, 50, 0, 0, 0, 0) (50, 50, 0, 0, 0, 0)

Input Queuing (Absolute 2 (F, F, F, F, F, F) (F, F, F, F, F, F)

Priority)

Type 2 mismatch should only generate a warning, so You can do this without disruption.

disclaimer, if the configuration itself introduce same traffic disruption when programming the asic.

/Mikael