INE Live Webinar MPLS Basics

Name: INE Live Webinar MPLS Basics
Uploaded: 2020-02-25T20:57:13.000Z
Duration: 3 h 10 min 14 s

Webinar on Configuring and Troubleshooting Basic MPLS

Introduction to the Webinar

The webinar is hosted by Rohit, a full-time instructor with multiple CCIE certifications in various domains including routing, security, voice, collaboration, and service provider.

Overview of MPLS Configuration

The session will cover a pre-configured topology involving customer routers and provider edge (PE) routers. Router 1 acts as the customer router with a default route towards Router 2 (ISP).

Routers XR1 and XR2 serve as PE routers. The infrastructure between these routers operates under MPLS.

Importance of MPLS

Without MPLS, running BGP between customers and ISPs would require extensive configurations that are not scalable or cost-effective.

Traditional routing methods would necessitate BGP on all routers for connectivity; however, this approach is impractical due to complexity.

Functionality of MPLS

MPLS encapsulates packet data with labels instead of IP addresses, allowing for efficient routing without exposing source/destination IP information.

This labeling system enables routers to perform lookups based on labels rather than traditional IP address lookups.

Pre-Configured Setup Details

The webinar will demonstrate basic MPLS configuration using pre-configured routers. Router 1 has a default route towards Router 2 while XR2 connects to XR1.

Both PE routers run BGP VPNv4 neighbor relationships but have not yet configured internal MPLS within the ISP infrastructure.

Routing Protocol Insights

OSPF runs internally within the ISP infrastructure; however, it does not extend to customer connections.

Understanding how MPLS functions is crucial for both CCIE Service Provider exams and general networking knowledge.

Configuration Demonstration

Rohit plans to show the current router configurations before building out the MPLS setup. He highlights existing routes in Router 1's table pointing towards the ISP.

A review of OSPF interfaces reveals that it only operates within the ISP network without extending to customer networks.

Connectivity Challenges

Despite having basic connectivity established through loopbacks among various routers, direct communication between customers remains unfeasible without proper routing configurations.

Understanding MPLS and BGP Interactions

Overview of BGP and MPLS Configuration

The discussion begins with examining the command show bgp evpn v4 unicast all, focusing on how routes are distributed in BGP, particularly through pre-configured loopbacks.

A traceroute example is presented, illustrating how packets are routed from one IP to another, emphasizing the recursive lookup process in the global routing table to reach a specific BGP neighbor.

Packet Forwarding and Routing Lookups

It is noted that without MPLS configured, Radha 1 sends an IP packet which gets forwarded but ultimately dropped by Radha 4 due to missing routes for destination 20.

The absence of BGP redistribution into OSPF leads to incomplete routing tables, resulting in packet drops when routers cannot find valid paths.

Control Plane vs Data Plane Dynamics

An analogy is drawn between OSPF and MPLS regarding route advertisement; both require establishing adjacency before exchanging information.

In OSPF, routes are shared directly after forming neighbor relationships; however, in MPLS, labels representing routes are exchanged instead.

Label Distribution Protocol (LDP)

The key difference in MPLS is that it uses label advertisements rather than direct route advertisements. Neighbor relationships must be established using protocols like LDP or NDP.

Emphasis is placed on the necessity for both routers to run the same protocol (e.g., LDP or NDP) to form adjacencies effectively.

Establishing Adjacency and Troubleshooting

Communication for forming adjacency in LDP relies on TCP port 646 and requires reachable router IDs—unlike OSPF where any unique ID suffices.

When troubleshooting MPLS configurations, verifying LDP neighbor relationships should be prioritized as a first step.

Activating MPLS on Interfaces

There are two methods for activating MPLS: directly on interfaces or automatically via IGP protocols like OSPF.

MPLS Configuration and Troubleshooting

Initial MPLS Setup Steps

The activation of MPLS is initiated by accessing the interface (Gig 1.24) and issuing the command mpls ip, which activates LDP (Label Distribution Protocol) instead of TDP (Tag Distribution Protocol).

Performing specific commands before activating MPLS simplifies troubleshooting, especially in lab environments where identifying label origins can be crucial.

Ensure that Safe Enablement (SEF) is activated; it is typically enabled by default but should be verified to avoid issues during configuration.

Recommended Commands Before Activation

Always start with enabling SEF and then configure the MPLS label protocol using mpls label protocol ldp.

Assign a unique router ID that must be reachable via TCP connection on port 646; this ensures proper communication between routers.

Label Range Configuration

It’s advisable to define a unique MPLS label range for each router to prevent conflicts when labels are advertised across different routers.

Labels need to be unique per router for different prefixes but do not require uniqueness across routers, making it essential to manage ranges effectively.

Practical Label Range Suggestions

Allocate sufficient label ranges based on the number of routes within your ISP infrastructure; a range from 2002 to 9999 provides ample space for labeling.

In lab exams, expect no more than 1000 routes, so configuring a range like 2002 to 3000 suffices.

Activating MPLS

Activate MPLS using the command mpls ip, which will initiate LDP packet exchanges over TCP port 646 with neighboring routers.

Alternative Activation Methods

An alternative method involves using routing protocols such as OSPF or IS-IS for automatic activation of MPLS across interfaces without manual configuration on each one.

By executing mpls ldp autoconfig under OSPF, all interfaces running OSPF will automatically have MPLS enabled.

Loopback Interface Considerations

Note that while you cannot activate MPLS directly on loopback interfaces, they can still advertise labels if they meet certain conditions: being part of an IGP and having a /32 address.

MPLS Configuration and Neighbor Relationships

Understanding MPLS Activation on Loopbacks

MPLS must be activated for LDP (Label Distribution Protocol), but it is not necessary to activate it on loopback interfaces. Loopbacks can still advertise labels if they have OSPF or any IGP configured, as they are treated as /32 addresses.

Neighbor Formation Requirements

If MPLS is not activated on both ends of a connection, neighbors will not form. This mirrors the behavior of OSPF where both routers need to have the protocol running to establish adjacency.

Configuring MPLS Between Routers

To enable MPLS between routers, activation must occur on all relevant interfaces. The command mpls label protocol ldp should be issued along with defining a unique label range for proper operation.

Scalability in Large Networks

Activating MPLS under the OSPF process can save time and effort when dealing with numerous routers and interfaces, making configuration more scalable compared to activating it individually on each interface.

Verifying MPLS Neighbors

After configuring MPLS between two routers, using commands like show mpls ldp neighbor helps verify that neighbors are established correctly. The output shows important details such as router IDs and TCP connections used for communication.

Troubleshooting Neighbor Issues

Understanding MPLS and VPN Label Exchange

Overview of MPLS Labels

The discussion begins with the explanation of transport labels, specifically the MPLS label and VPN label used in a VRF context. BGP is utilized for exchanging VPN labels between routers R2 and X.

It is noted that while one label is exchanged through BGP, another is exchanged via LDP (Label Distribution Protocol), highlighting the dual nature of label exchange mechanisms.

Packet Flow and Encapsulation

When Router 1 sends an IP packet to the ISP, it does not utilize TLS due to its absence between routers. Instead, it encapsulates packets with both a VPN label (1914) and an MPLS transport label (4004).

The process continues as Router 5 removes the transport label before forwarding a packet to the ISP, demonstrating how packets are processed through multiple routers.

Troubleshooting LDP Neighbor Issues

A brief overview indicates that despite lacking PDB within the infrastructure, pings between customers succeed due to proper encapsulation by MPLS.

To identify LDP neighbor issues quickly, verifying if MPLS is enabled on interfaces can be an effective first step.

Identifying Broken LDP Neighbors

An example scenario illustrates breaking LDP neighbor relationships by modifying OSPF configurations on specific loopbacks without affecting overall OSPF functionality.

The speaker explains how establishing LDP neighbor relationships relies heavily on router IDs being reachable; broken links can hinder this process significantly.

Efficient Troubleshooting Techniques

In large networks with numerous routers, manually checking each router for LDP status can be inefficient. A more efficient method involves using ping commands directed at remote PE loopbacks to diagnose issues quickly.

By performing an MPLS ping command from Router 2 to Router X's loopback address, users can determine where problems lie based on output indicating unlabeled interfaces.

Resolving TCP Connection Issues

If there are no established neighbors despite confirming interface settings are correct, potential solutions include changing router IDs or advertising loopbacks in OSPF.

MPLS and LDP Neighbor Issues

Understanding Router ID and Connection Types

The router ID is identified as loopback one, while the PCP connection operates on a physical interface. This indicates that TCP is not utilizing the router ID at this moment.

Common Lab Exam Challenges

In lab exams, issues may arise from using interfaces that do not run IGP, potentially causing LDP neighbor ship failures. Such problems can also occur in production environments.

Quick Troubleshooting Techniques

A successful ping to MPLS indicates proper connectivity. It's emphasized that checking every router for LDP neighbor status is inefficient during time-sensitive lab exams.

MPLS Forwarding Table Insights

After establishing MPLS connectivity, it's crucial to examine the MPLS flooding table and understand how labels are advertised. Two label stacks exist: a VPN label atop an IP packet followed by a transport label.

Label Advertisement Process

When OSPF adjacency is established between routers, labels representing routes are exchanged to build the MPLS forwarding table. This process mirrors traditional routing protocols like OSPF.

Label Distribution and Implicit Null

Advertising Labels in MPLS

The discussion includes how labels are advertised when customers are not within a VRF (Virtual Routing and Forwarding). If customers reside in global tables, only transport labels will be present.

Local Perspective of Label Advertisement

The focus shifts to R2 advertising its loopback label to R4. Each interface within the IGP infrastructure follows this labeling process for efficient data plane operations.

Special Case of Implicit Null Label

R2 advertises an implicit null label (label number 3), which signifies that it’s directly connected to itself. This special case does not appear locally but is recognized by neighboring routers like R4.

Handling Non-direct Connections

When R4 receives an implicit null advertisement from R2 for its loopback, it must handle this differently since it’s not directly connected; thus, it cannot send implicit null back but must generate a unique label instead.

MPLS Forwarding Table Construction and Packet Flow

Label Distribution and Interface Connections

The router receives a label (4000) on interface gig 1.34 from neighbor 20.3.4.4, indicating the start of label distribution.

Router 6 receives label 3000 from gig 1.36 (20.3.6.36) and advertises a new label range (6000) to Router 5 via gig 1.56 (20.5).

XR1 generates an irrelevant local label (19000), as there are no neighbors behind it; this is for potential future connections.

Building the MPLS Forwarding Table

The MPLS forwarding table is constructed by advertising labels to neighbors and recording received labels in respective columns.

Similar to OSPF's route building, MPLS uses neighbor relationships to exchange labels, forming the basis for packet routing.

Packet Transmission Process

When a ping is initiated from one router to another, it sends an IP packet based on its routing table.

XR1 checks its global routing table for routes to destination IP (1.1.1.1), confirming connectivity through BGP.

Encapsulation and Label Swapping

Upon finding that MPLS is enabled on the outgoing interface, XR1 encapsulates the IP packet with a corresponding MPLS label (5000).

Router 5 receives an MPLS-labeled packet; it performs an MPLS lookup using the received label (5000), swapping it with its own assigned label (6000).

Final Delivery of Packets

Each subsequent router continues this process of swapping labels until reaching Router R2, which pops the topmost layer off when receiving implicit null.

This process reduces processing load on routers by allowing penultimate hop routers to handle some operations—known as Penultimate Hop Popping (PHP).

Implications of Routing Tables and Labels

If R2 had advertised a specific non-null label instead of implicit null, additional processing would be required at each hop, complicating packet delivery efficiency.

This structured summary captures key concepts related to MPLS forwarding tables and their operational mechanics within network infrastructure while providing direct references for further exploration of each topic discussed in the transcript.

Understanding MPLS and VPN Labeling

Overview of Router Operations

The process begins with R2 forwarding packets to R1, highlighting the heavy load on PE routers due to BGP, VPNv4, and MPLS operations.

R2 instructs R4 to remove the topmost layer of the packet, simplifying processing by eliminating the need for R2 to strip off the MPLS label.

VPN vs. Non-VPN Packet Processing

When dealing with a customer inside a VRF (Virtual Routing and Forwarding), R2 uses BGP to advertise a VPN label instead of relying solely on MPLS labels.

A specific example is given where a VPN label (e.g., 2099) is advertised through BGP rather than appearing in an MPLS routing table.

Traffic Flow and Encapsulation

The traffic flow involves XR1 receiving an IP packet without an MPLS label; it checks its VRF routing table for routes via BGP.

XR1 encapsulates the IP packet with both a VPN label (2099) and a transport label (5000), preparing it for further forwarding.

Layer Removal Process

As packets traverse through various routers, each router performs layer removal: R4 removes the topmost layer while maintaining necessary labels for proper routing.

The distinction between "pop" (removing one layer) versus "no label" (removing all layers) is emphasized during this process.

Route Tracing and Label Learning

A trace route from Radha 1 to XR1 illustrates how packets are received as IP packets before being encapsulated with appropriate labels by XR1.

Labels are learned via BGP rather than appearing in standard MPLS tables; this highlights how dynamic routing influences packet handling across networks.

Final Forwarding Steps

Upon reaching XR1, additional encapsulation occurs based on interface capabilities; if MPLS is enabled, further transport labels are added before forwarding.

MPLS Configuration and Troubleshooting

Understanding MPLS Labeling and Packet Forwarding

The process of MPLS involves a VP labeled swap, where the router (R4) performs a pop operation to remove the topmost label from a packet before forwarding it as an IP packet to the customer.

When activating MPLS, it's crucial to ensure that the router ID is reachable; otherwise, configuration issues may arise.

Use traceroute or ping commands specifically for MPLS to identify transport and VPN labels effectively.

The BGP table reveals that XR1 instructs R2 on encapsulating packets with specific VPN labels for customer communication.

PE routers must establish BGP neighbor relationships over loopback interfaces rather than physical ones to avoid premature penultimate hop popping.

Implications of Incorrect Interface Configuration

If BGP neighbor relationships are formed on physical interfaces instead of loopbacks, it can lead to incorrect label popping behavior in packet forwarding.

An example illustrates how improper configurations can cause packets to be dropped due to missing VPN labels when they reach routers not running BGP.

R4 drops packets because it lacks the necessary VPN label after premature penultimate hop popping occurs, emphasizing the importance of correct adjacency setups.

Alternatives and Best Practices in MPLS Setup

Configuring explicit null instead of implicit null can help manage label advertisement but may complicate end-to-end processes by removing PHP functionality.

Ensure safe configurations are enabled, verify router IDs are reachable, and maintain unique label ranges for easier troubleshooting within LDP neighbor issues.

Router Types in MPLS Networks

PE routers typically include high-capacity models like iOS XR or SR routers capable of handling extensive routing tables (over 600,000 routes).

P routers do not require BGP; they primarily run OSPF and MPLS protocols without needing heavy processing capabilities found in PE routers.

While PE routers should be robust (e.g., ESR 900 series), P routers can be less powerful models such as CSR or lower series like 2900/3900.

Addressing Questions on BGP Cost Relationships

Understanding IP Address Usage in MPLS Networks

Internal vs. Public IP Addresses

It is common to use internal IP addresses within an ISP's MPLS network, as the internal infrastructure is not advertised publicly.

Typically, a router (R2) would have a public-facing IP address, while connections between routers may utilize private IP addresses unless they are directly connected.

Routing and BGP Peering

The next hop always refers to the global routing table, regardless of whether VRFs (Virtual Routing and Forwarding) are used.

R1 acts as a customer and does not run BGP with XR1; instead, BGP is only established between R2 and XR1.

Label Management in MPLS

Label Assignment Strategies

Assigning unique label ranges per client router can be beneficial for organization but may not be scalable compared to assigning labels based on routes.

Optimization of MPLS configurations is essential; unnecessary transport labels should be minimized for efficiency.

Adjacency Establishment

Distant routers cannot establish adjacency without direct connection unless using tunnels; LDP (Label Distribution Protocol) operates within the same interface.

Label Processing and Configuration

Label Allocation Across Platforms

The process of allocating labels is similar across IOS and XR platforms; however, certain features like SAFI (Subsequent Address Family Identifier) are enabled by default in XR.

Maximum Labels Overhead

The number of labels that can be added over an IP packet varies based on configuration; multiple VPN or transport labels can coexist depending on setup.

Route Distinguishers and Targets in MPLS

Identifying Customer Routes

Route distinguishers and import/export policies help identify which customer's routing table a packet belongs to when multiple customers share the same PE (Provider Edge).

Importance of Route Separation