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

hardware queue-limit

satyamkhurana
Level 1
Level 1

Hi ,


I want to change the Queue Limit Tx of the port which is on FEX .

#show queuing int e103/1/15
Ethernet103/1/15 queuing information:
Input buffer allocation:
Qos-group: 0
frh: 2
drop-type: drop
cos: 0 1 2 3 4 5 6
xon xoff buffer-size
---------+---------+-----------
0 0 65536

Queueing:
queue qos-group cos priority bandwidth mtu
--------+------------+--------------+---------+---------+----
2 0 0 1 2 3 4 5 6 WRR 100 2048

Queue Limit Tx: 4194304 bytes <<<<<<<<<<<<<<<<<<<<<<< Here the port’s transmit queue-limit is 4mb
Queue Limit Rx: 1048576 bytes

Queue Statistics:
---+----------------+-----------+------------+----------+-----------+
Que|Received / |Tail Drop |No Buffer |MAC Error |Multicast |
No |Transmitted | | | |Tail Drop |
---+----------------+-----------+------------+----------+-----------+
2rx| 122107707577| 0| 1| - |
2tx| 172794118333| 806343868| 0| 0| 0|
---+----------------+-----------+------------+----------+-----------+

Priority-flow-control enabled: no
Flow-control status:
cos qos-group rx pause tx pause masked rx pause
-------+-----------+---------+---------+---------------
0 0 xon xon xon
1 0 xon xon xon
2 0 xon xon xon
3 0 xon xon xon
4 0 xon xon xon
5 0 xon xon xon
6 0 xon xon xon
7 n/a xon xon xon

I want to modify the default configuration to allow a specific port, to pull more buffers to remediate the drops.

1) Increase the queue-limit for a specific port seeing drops
2) Increase the queue-limit for all ports on the FEX


Either of these options is fine to perform, the choice is more aligned to what level of change you’d like to have. Since the buffer is shared, by increasing it for all ports there’s a higher possibility of having other ports use up the buffer and cause output drops but we still have some protection with a queue-limit in place. By allowing a single port increased buffer limits, only this port is susceptible to utilizing the larger buffers. If the queue-limit is removed entirely via option 3 there is no protection for the shared buffer and a single port could utilize a large chunk of it, starving out other ports.

Here is syntax for option 1, to change the queue-limit for a specific port:
switch(config)# interface ethernet 100/1/1
switch(config-if)# hardware N2248TP-E queue-limit 4000000 tx

Here is the syntax for option 2, to change the queue-limit for an entire FEX:
switch(config)# fex <FEX ID>
switch(config-fex)# hardware N2248TP-E queue-limit 4000000 tx


I have a limitation to perform this change on live network. I was able to make a change using Option 1 on standalone interfaces successfully.


But in the interfaces which are clubbed with port-channel it is causing problem and there is no command coming available for such interfaces.


(config)#int Ethernet101/1/1
(config-if)# hardware N2248TP-E queue-limit 5000000 tx
^
% Invalid command at '^' marker.

interface Ethernet101/1/2
description --to hw-hpd380-1108
switchport mode trunk
switchport trunk allowed vlan 262,269
flowcontrol receive on
channel-group 32 mode active
!
interface Ethernet102/1/2
description --to hw-hpd380-1108
switchport mode trunk
switchport trunk allowed vlan 262,269
flowcontrol receive on
channel-group 32 mode active
!
interface port-channel32
switchport mode trunk
switchport trunk allowed vlan 262,269
spanning-tree guard root
flowcontrol receive on


(config)# interface port-channel32
(config-if)# hardware N2248TP-E queue-limit 5000000 tx
^
% Invalid command at '^' marker.
(config-if)# interface Ethernet102/1/2
(config-if)# hardware N2248TP-E queue-limit 5000000 tx
^
% Invalid command at '^' marker.
(config-if)# interface Ethernet101/1/2
(config-if)# hardware N2248TP-E queue-limit 5000000 tx
^
% Invalid command at '^' marker.

================================================

I have to limitation with system that I cannot take downtime and change it entirely on fex plus I am also not allowed to remove any port from port-channel to
configure queue-limit on it. Is there any solution considering a thin line I am giving for solution.

I am on following IOS
cisco Nexus 56128P Chassis ("Nexus 56128P Supervisor")

kickstart image file is: bootflash:///n6000-uk9-kickstart.7.0.8.N1.1.bin
kickstart compile time: 2/20/2016 21:00:00 [02/21/2016 09:06:20]
system image file is: bootflash:///n6000-uk9.7.0.8.N1.1.bin
system compile time: 2/20/2016 21:00:00 [02/21/2016 09:07:39]

 

0 Replies 0