04-10-2015 03:21 AM - edited 03-07-2019 11:29 PM
The interface drop rate count arises and the traffic throughput gets down to 15% of the nominal data rate of the 1Gb interface when a server with a 10Gb interface send data to a client connected at 1Gb FEX interface.
How must I configure the interface to achieve nearly 100% of 1Gb?
Client to Server: 100% of 1Gb; Sever to Client 15% of 1Gb
Server ---(10Gb)--- Nexus7010-- (10Gb)--- C6880-X----(10Gb)---FEX----(1Gb)Client
04-10-2015 06:04 AM
6880-X <> FEX ?
Did you mean
6880-X <> IA?
04-13-2015 12:35 AM
Sorry, yes of course:
Server ---(10Gb)--- Nexus7010-- (10Gb)--- C6880-X----(10Gb)---6800-IA----(1Gb)---Client
06-04-2015 12:04 AM
Hi,
TAC Observation:-
The temporary workaround is to create any lan-queuing policy-map, apply it on the FEX interface and then remove it.
class-map type lan-queuing match-all cs1
match dscp cs1
class-map type lan-queuing match-all cs2
match dscp cs2
policy-map type lan-queuing policy1
class type lan-queuing cs1
priority
class type lan-queuing cs2
bandwidth remaining percent 10
And apply this policy on host port on FEX and remove it,
Router(config)#int gigabitEthernet 103/1/0/19
Router(config-if)#service-policy type lan-queuing output policy1
Propagating [attach] lan queueing policy "policy1" to Gi103/1/0/1 Gi103/1/0/2 Gi103/1/0/3 Gi103/1/0/4 Gi103/1/0/5 Gi103/1/0/6 Gi103/1/0/7 Gi103/1/0/8 Gi103/1/0/9 Gi103/1/0/10 Gi103/1/0/11 Gi103/1/0/12 Gi103/1/0/13 Gi103/1/0/14 Gi103/1/0/15 Gi103/1/0/16 Gi103/1/0/17 Gi103/1/0/18 Gi103/1/0/20 Gi103/1/0/21 Gi103/1/0/22 Gi103/1/0/23 Gi103/1/0/24 Gi103/1/0/25 Gi103/1/0/26 Gi103/1/0/27 Gi103/1/0/28 Gi103/1/0/29 Gi103/1/0/30 Gi103/1/0/31 Gi103/1/0/32 Gi103/1/0/33 Gi103/1/0/34 Gi103/1/0/35 Gi103/1/0/36 Gi103/1/0/37 Gi103/1/0/38 Gi103/1/0/39 Gi103/1/0/40 Gi103/1/0/41 Gi103/1/0/42 Gi103/1/0/43 Gi103/1/0/44 Gi103/1/0/45 Gi103/1/0/46 Gi103/1/0/47 Gi103/1/0/48
Router(config-if)#
Router(config-if)#no service-policy type lan-queuing output policy1
Propagating [remove] lan queueing policy "policy1" to Gi103/1/0/1 Gi103/1/0/2 Gi103/1/0/3 Gi103/1/0/4 Gi103/1/0/5 Gi103/1/0/6 Gi103/1/0/7 Gi103/1/0/8 Gi103/1/0/9 Gi103/1/0/10 Gi103/1/0/11 Gi103/1/0/12 Gi103/1/0/13 Gi103/1/0/14 Gi103/1/0/15 Gi103/1/0/16 Gi103/1/0/17 Gi103/1/0/18 Gi103/1/0/20 Gi103/1/0/21 Gi103/1/0/22 Gi103/1/0/23 Gi103/1/0/24 Gi103/1/0/25 Gi103/1/0/26 Gi103/1/0/27 Gi103/1/0/28 Gi103/1/0/29 Gi103/1/0/30 Gi103/1/0/31 Gi103/1/0/32 Gi103/1/0/33 Gi103/1/0/34 Gi103/1/0/35 Gi103/1/0/36 Gi103/1/0/37 Gi103/1/0/38 Gi103/1/0/39 Gi103/1/0/40 Gi103/1/0/41 Gi103/1/0/42 Gi103/1/0/43 Gi103/1/0/44 Gi103/1/0/45 Gi103/1/0/46 Gi103/1/0/47 Gi103/1/0/48
Router(config-if)#
Then you will see the changes in the priority queue.
Router(config-if)# do remote command fex 103 show mls qos interface gig 1/0/19 queueing
GigabitEthernet1/0/19
Egress Priority Queue : enabled
Shaped queue weights (absolute) : 0 0 0 0
Shared queue weights : 0 84 84 84<<<<<<<<<<<
The port bandwidth limit : 100 (Operational Bandwidth:100.0)
The port is mapped to qset : 1
Now please try to send file from server to client. And let me know if you see any drops.
This issue is due to the defect # CSCuu30115 / CSCuu52415 , and the fix for this defect is available in 15.2(1)SY2
Resolution :-
Workaround has been provided and we need to wait for final release of SY2 which is expected to be available on CC October’15 tentatively. I have added your CCO id on bugtoolkit.
Whenever any update related to this bug you will be notified via email. It was nice working with you and thanks for choosing Cisco. If you want to share any feedback related to handling of this Service Request to our management team, please do not hesitate in contacting my Manager - Mahesh Dawar. Email :mdawar@cisco.com
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