How to protect MPLS TE sub-pool from other traffic
Hi MPLS expert,
I would like to know how we can make sure that traffic that goes into a tunnel configured with the subpool x kbs option is not affected by other type of traffic that are not part of the tunnel in a case of congestion of the low latency queue.
It is my understanding that TE works at control plane only and does not provide any kind of priority for the TE tunnel. If I am not mistaken, it is not possible to assign any kind of policing or shaping to a tunnel interface.
I would like to understand how we can make sure that TE traffic using the subpool option will not be affected by other traffic that also goes into the LLQ in a congestion situation.
Is the only way to prioritize TE traffic is to police all other source of traffic that can go in the LLQ?
If this is true that we cannot applied QOS policy to a tunnel, how can we make sure that all the traffic going into the tunnel is mark with the same EXP bits?
The Cisco EPN system incorporates a network architecture designed to consolidate multiples services on a single Multiprotocol Label Switching (MPLS) transport network. This network is designed primarily based on Application Engineered...
Internet security is important with the increasing attacks that are happening every day. Many internet and browsing security solutions exist, but some are not very easy to use or maybe the question is how can I enable them?
Cisco Software Manager Server
This document describes the programmatic interfaces, RESTful APIs, which are supported by Cisco Software Manager Server (CSM Server).
CSM Server supports a set of finite RESTful APIs. The fir...