We've started to implement MPLS-TP for testing purposes in our lab and I've been reading a lot of material to better understand this technology, but there are still quite a few questions which arise when dealing with it. As a basis, I understand MPLS-TP is supposed to allow providers which maintain a transport network to interconnect that network to their IP/MPLS core, but:
1. Why would they need MPLS at the transport network at all? Why wouldn't it simply be a L2 or a basic IP network throughout that network?
2. Why can't they use existing MPLS? As I understnad, they major difference between the two is the lack of dynamic label allocation (which is done by LDP) in the MPLS-TP design. Why was that omitted? Isn't that rather a setback in the progress of the technology?
3. Which technologies will "suffer" from a dynamic allocation of labels and why?
Crosswork Cloud - Crosswork Traffic Analysis - FAQ
Crosswork Cloud - Crosswork Traffic Analysis is a Cloud-hosted Software as a Service platform that provides Netflow based Traffic Analytics. The Crosswork Traffic Analysis platform Traffic Analysis, Peeri...
Cisco Champion Radio · S8|E9 Innovations to Achieve a Trustworthy Infrastructure
How do you know for certain that a router in your network has not been altered with since you deployed it? Wouldn’t it be great if you can cryptographically challenge your r...
IOS upgrade on asr9xx mandates rommon upgrades sometimes while they can be optional at other times. You may land up in unwanted situation if proper procedure is not followed during upgrades.
This article will include complete details about rommon ...
In some situation NCS560 RP become unresponsive after reload or powercycle.
In many NCS560 deployments are in remote location, deployment might be large and human intervention should be kept at minimum
Engineering team have been working on a str...
In simple terms, 'Route Churn' is defined as the 'rate of change of prefixes'. Different XR versions across 4.x to 7.x have differing behavior & support for the BGP churn handling and some enhancements made from 6.5.3 onwards (listed in appendix) mak...