I have a question regarding queueing on an ATM interface. Platforms are 7206VXR & 7606s, with either PA-A3 -T3 or PA-A3-OC3SM cards.
What is the functional difference between queueing on the whole ATM interface and per-vc queueing? What would the queue size be for a DS-3 or an OC-3 without per-vc, and with per-vc? What types of symptoms would we see on our PVCs without per-vc queueing?
Also, our "legacy" way of configuring ATM pvcs was to use the old command format:
atm pvc 55 3 55 aal5snap 36864 36864 100
Some on our team have been configuring them with the "new way" as follows:
pvc 35 2/35
vbr-nrt 64 64 1
Other than the ability to name PVCs, what is the benefit of one way vs. the other?
The physical aspects are essentially the same, it's more an issue of how the process handles the administration of multiple VCs and the resulting traffic.
Without per-vc queuing, the behavior more like a fifo queue, with per-vc queuing, it's more like fair-weighting.
According to articles found on a Cisco-site search: "Per-VC queuing is to ensure that one congested VC does not consume all the memory resources and starve other VCs." In other words, if you have one pool of memory resources for several VCs, and one VC is using most of the pool, then performance of the other VCs will suffer.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.