Even with P2P link, MTU comes into picture. When there is a need for label imposition, each label will consume 4 bytes. Depending on what MPLS application you are running, number of labels may vary. For example, plain MPLS will need 1 label to be imposed while L3VPN needs 2 labels.
MPLS MTU applies only to MPLS packet, so only packets with tags
IP MTU applies to IP paquets only.
You could configure 2 values at interface level for IP and MPLS packets.
Also you may have some Penultimate hop popping in your scenario, meaning the downstream edge router might receive just an IP packet in case of a basic MPLS backbone, or a packet with 1 label only in case of L3VPN ( because of implicit null label advertisement.).
You might also add some labels in case of traffic engineering, meaning one or more label in your core network (with FRR for example).
As it is 4 bytes per label, make sure you count them all in worst case scenario
This will be the complete setup, Layer 2 EoMPLS vlan based. Also there are no P routers, all PE in a sense.
I already set the mpls mtu to 1546, but for the interface mtu still 1500. From R1 when i ping R2 no problem with mtu, for R1 ping R3 i can only use 1530, so therefore 16 bytes is used? Also what do i expect when i put my cpe and use EoMplS vlan based, another 4 bytes will be added?
With XR 4.2.0 the ASR9000 is releasing a new line of hardware models. This amongst others is the RSP440, the next generation RSP with faster switch fabric along with Typhoon based Linecards, the next generation network processor.
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...
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?