cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Join Customer Connection to register!
786
Views
0
Helpful
3
Replies
r.heitmann
Beginner

catalyst 6500 - outlost counter

Hi,

i'm experiencing performance problems on two ports - both are incrementing the "qos3outlost" counter. (see last row in the attachment)

Unfortunately this counter is not documented in the manual.

Any idea?

Regards,

//Ronald

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

* Catalyst 6513

* Sup 720

* WS-X6548-GE-TX 10/100/1000mb

* IOS 12.2(17d)SXB4

* QoS globally disabled

switch #show counters interface gigabitEthernet 2/1

32 bit counters:

0. rxCRCAlignErrors = 0

1. rxUndersizedPkts = 0

2. rxOversizedPkts = 0

3. rxFragmentPkts = 0

4. rxJabbers = 0

5. txCollisions = 0

6. ifInErrors = 0

7. ifOutErrors = 0

8. ifInDiscards = 0

9. ifInUnknownProtos = 0

10. ifOutDiscards = 0

11. txDelayExceededDiscards = 0

12. txCRC = 0

13. linkChange = 1

14. wrongEncapFrames = 0

All Port Counters

1. InPackets = 2579030

2. InOctets = 707154029

3. InUcastPkts = 2575722

4. InMcastPkts = 1

5. InBcastPkts = 3307

6. OutPackets = 576701235

7. OutOctets = 650700777573

8. OutUcastPkts = 553275452

9. OutMcastPkts = 19468528

10. OutBcastPkts = 3957255

11. AlignErr = 0

12. FCSErr = 0

13. XmitErr = 0

14. RcvErr = 0

15. UnderSize = 0

16. SingleCol = 0

17. MultiCol = 0

18. LateCol = 0

19. ExcessiveCol = 0

20. CarrierSense = 0

21. Runts = 0

22. Giants = 0

23. InDiscards = 0

24. OutDiscards = 0

25. InErrors = 0

26. OutErrors = 0

27. TrunkFramesTx = 0

28. TrunkFramesRx = 0

29. WrongEncap = 0

30. Broadcast_suppression_discards = 0

31. Multicast_suppression_discards = 0

32. Unicast_suppression_discards = 0

33. rxTxHCPkts64Octets = 36464454

34. rxTxHCPkts65to127Octets = 55925886

35. rxTxHCPkts128to255Octets = 29765888

36. rxTxHCPkts256to511Octets = 22958237

37. rxTxHCpkts512to1023Octets = 28902202

38. rxTxHCpkts1024to1518Octets = 405263638

39. DropEvents = 0

40. CRCAlignErrors = 0

41. UndersizedPkts = 0

42. OversizedPkts = 0

43. FragmentPkts = 0

44. Jabbers = 0

45. Collisions = 0

46. DelayExceededDiscards = 0

47. bpduOutlost = 0

48. qos0Outlost = 0

49. qos1Outlost = 0

50. qos2Outlost = 0

51. qos3Outlost = 699437194

...

3 REPLIES 3
answanso
Cisco Employee

Do you have any monitor sessions that are the destination to any gig2/x interfaces? Can I see the output from a "show run"? This can happen if you have a large span session overwelm a portasic that controls multiple ports.

Anthony

Hallo Ronald,

Out−Lost Excessive output rate of traffic. Increments in this counter are more likely to occur when connected to low speed devices. The first step in

troubleshooting Out−Lost increments is to verify

the link partner is running 100 Mbps full−duplex

from www.cisco119.com/down/pds/Troubleshooting_ Cisco_Catalyst_Switches_to_NIC_Compatibility_Issues-46.pdf

"qos3outlost" could be qos queue 3 overrun by traffic.

Liebe Gruesse aus Hamburg!

Martin

jarathbu
Beginner

Hello,

The "qos3Outlost" counter is typically associated with oversubscription. Are the 2 ports your having difficulties with supported by the same ASIC(s) - same group of 4 or group of 8? Both links are running at full duplex? As previously mentioned, no span sessions configured for either of the ports as a destination port?

Hope this helps.

Regards,

James

Content for Community-Ad