What is the diference between tx-lmit command and hold queue command?
Actually I have two routers connected through a FR cloud. I make a ping to ROUTER_B's serial interface from ROUTER_A and I have icmp request timout during the day. I noticed from several commands outputs (find them attached) that I have many drop packets and delayed packets.
"What is the diference between tx-lmit command and hold queue command?"
Tx-ring-limit controls the size/depth of the FIFO queue on the controller. Hold queue controls the size/depth of the software (FIFO) queue. (The latter only obtains packets when the former overflows.)
Congested links usually drop packets. Frame-relay can also drop packets in the cloud (especially if you exceed your CIR).
Generally two things to try, first insure if one side's FR cloud connection is larger than the other, or there are multiple PVCs, regulate it (them) so as to not to overrun FR egress. Second, try to implement fair-queue instead of FIFO. The former tends to provide all flows more more consistent performance and bandwidth hog flow packets tend to be dropped first.
I had WFQ configured on the interfaces but I had the same symptom, about 2500 dropped packets for every 20000 output packets. After configuring the serial interface with hold queue 900 (I tried several values before this) and now I have about 50 dropped packets every 60000 output packets.
The serial link to FR Cloud is never overloaded during the day. The CIR is the same on both sides 512. from the command outputs I have posted what does the "pkts delayed" field actually mean?
The hold queue command affect only CPU switched packets or all the packets? The number in the tx-ring-limit & hold queue commands what are representing packets or bytes? Is there any specific value for tx-ring that I can use for testing.
Sorry, for the long, long delay. Misplaced your response questions.
Unclear how the FR cloud isn't overloaded but you're seeing all these drops. You shouldn't see drops unless the interface is congested.
Hold queue applies to software queued packets. Hold queue, I believe, always count packets, tx-ring-limit I believe usually counts packets but on some platforms I recall it counts particles. (Neither should be in bytes.)
For a tx-ring-limit, I either allow the router to default the value unless I'm supporting voice where I'll set it to 2 or 3. (Believe I've read the very latest IOSs are much "smarter" about setting the default tx-ring-limit.)
Don't know what "pkts delayed" specically means unless it indicates packets delayed by the shaper.
The CIR is 512 but's what the physical link speed? If the physical link is faster, wonder whether the shaper is holding your bandwidth to 512. If so, and if these links are in North America, you could likely run them at full port speed.
Actually the interface access-rate is 768Kbps and the CIR is 512Kbps. I configured the software pvc hold queue for a value 90 packets and now router does not drop packets at all. However I think that we must proceed with a new CIR contract with our ISP.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...