I just thought about something. When you transmit MPLS Labels over L2 technology (ATM/FR/Eth) L2 header identifies that encapsulated traffic is Label and it's done via EtherType or SNAP headers.
I assume that when LDP gets enabled on the interface, it allows the interface to transmit and receive labeled packet which otherwise would have been dropped.
In case of IPv4+Label in either CsC or Inter-AS VPN scenarios, LDP is not enabled on the interface, so how do PE routers know to accept labeled packets and not drop them?
Maybe if there was a way to enable labeled packets processing without configuring LDP on the interface, cause with IPv4+Label feature you still want to process labeled packets, but you're not interested in activating LDP on the interface and exachanging labels this way.
I think that on the data forwarding plane, you still have to make sure that labeled packets are accepted and it's not done by default. Activating LDP on the interface takes care of that and I assume that IOS code treats interfaces through which the IPv4+Label advertisemets were received also as interfaces enabled for label packet forwarding.
I guess we would need an "internal" Cisco info to confirm if that's so :-)
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...