Have this Gig interface directly connected to a 10Mb link to the ISP.
GigabitEthernet0/0 is up, line protocol is up
Hardware is MV96340 Ethernet, address is 0025.45f2.09a0 (bia 0025.45f2.09a0)
Internet address is x.x.x.x/30
MTU 1500 bytes, BW 10000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 75/255, rxload 61/255
There's QoS configured outbound for a TCP application to provide 30% of interface bandwidth.
service-policy output ARCUS-QOS
Which values do I have to see on the txload/rxload in the interface to have QoS kick in?
Class-map: TRANSACTIONAL (match-all)
23896 packets, 4597078 bytes
5 minute offered rate 12000 bps, drop rate 0 bps
Match: access-group 160
Priority: 30% (3000 kbps), burst bytes 75000, b/w exceed drops: 0
When is the interface considered congested?
No, tx-ring is a software pointer, which points to where the packets physically store in the memory. You can consider it is a FIFO queue. When packet leaves interface, it will be placed on the tx-ring first waiting be sent out. If the number of packets on the tx-ring exceeds the tx-ring-limit, the coming packets will be put in software queue to process.That's why when traffic is bursty, even the txload is very low on the interface, it still can cause interface congestion.