If I use CBWFQ and use the bandwidth percent in each class, and if I apply the policy to an ATM sub-interface which has a vbr-nrt vc with 294Kbps as the SCR, the calculated bandwidth is based on the SCR instead of the bandwidth statement of the sub-interface (the bandwidth statement is 256Kbps). The difference between the 294 and 256 is the atm cell overhead.
So far so good. However, why would the bandwidth percent base its calculation on the configured SCR as opposed to interface bandwidth ? The document at the following location mentions CBWFQ does not take the ATM cell header overhead into account for its calculations. Yet, the bandwidth percent seems to base its calculation on the SCR which includes cell overhead...Anybody encounteredthis problem ? That seems like it may be hard to use bandwidth percent because of this...
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 ...