Saving Configurations MPLS Tag Switching Commands

How to Configure MPLS LDP

Interfaces:

POS2/0 (ldp): xmit/recv

LDP Id: 172.31.255.255:0

Tunnel1 (ldp): Targeted -> 192.168.255.255

Targeted Hellos:

172.16.0.0-> 192.168.255.255 (ldp): active, xmit/recv

LDP Id: 192.168.255.255:0

172.16.0.0-> 192.168.0.0 (tdp): passive, xmit/recv

TDP Id: 192.168.0.0:0

This command output indicates that:

•The local LSR (172.16.0.0) sent LDP link Hello messages on interface POS2/0 and discovered neighbor 172.31.255.255.

•The local LSR sent LDP targeted Hello messages associated with interface Tunnel1 to target 192.168.255.255. The LSR was configured to use LDP.

•The local LSR is active for targeted discovery activity with 192.168.255.255; this means that the targeted Hello messages it sends to 192.168.255.255 carry a response request. The local LSR was configured to have an LDP session with the nondirectly connected LSR 192.168.255.255.

•The local LSR is not passive from the discovery activity with 192.168.255.255 for one of the following reasons:

◦The targeted Hello messages it receives from 192.168.255.255 do not carry a response request.

◦The local LSR has not been configured to respond to such requests.

•The local LSR sent TDP directed Hello messages to the target LSR 192.168.0.0. This LSR uses TDP because the Hello messages received from the target LSR 192.168.0.0 were TDP directed Hello messages.

•The local LSR is passive in discovery activity with LSR 192.168.0.0. This means that the directed Hello messages it receives from LSR 192.168.0.0 carry a response request and that the local LSR has been configured with the mpls ldp discovery targeted-hello accept command to respond to such requests from LSR 192.168.0.0.

•The local LSR is not active in discovery activity with LSR 192.168.0.0, because no application that requires an LDP session with LSR 192.168.0.0 has been configured on the local LSR.

For examples of configuring LDP targeted sessions, see the Establishing Nondirectly Connected MPLS LDP Sessions Example, page 23.

Saving Configurations MPLS Tag Switching Commands

In releases of Cisco IOS software prior to 12.4(2)T, some MPLS commands had both a tag-switching version and an MPLS version. For example, the two commands tag-switching ip and mpls ip were the same. To support backward compatibility, the tag-switching form of the command was written to the saved configuration.

Starting in Cisco IOS Release 12.4(2)T, the MPLS form of the command is written to the saved configuration.

For example, if an ATM interface is configured using the following commands, which have both a tag- switching form and an MPLS form:

Router(config)# interface ATM3/0 Router(config-if)#ip unnumbered Loopback0 router(config-if)#tag-switching ip Router(config-if)#mpls label protocol ldp

After you enter these commands and save this configuration or display the running configuration with the show runningcommand, the commands saved or displayed appear as follows:

interface ATM3/0

MPLS LDP Configuration Guide, Cisco IOS Release 12.4

11

Page 16 Page 18
Page 17
Image 17
Cisco Systems 12.4 manual Saving Configurations Mpls Tag Switching Commands
Page 16 Page 18

12.4 specifications

Cisco Systems has consistently been at the forefront of networking technology, and one of its notable software releases is IOS version 12.4. This version introduced significant enhancements and features that continue to influence networking practices. IOS 12.4 was specifically designed to accommodate the growing demands of network reliability, scalability, and advanced functionalities.

One of the primary characteristics of IOS 12.4 is its enhanced security features. The version integrates advanced security protocols, including improvements in IPsec, which allows for secure communication across potentially insecure networks. Additionally, it supports firewall technologies and access control lists (ACLs), ensuring that organizations can implement stringent security measures tailored to their traffic requirements.

Another defining feature of IOS 12.4 is its support for IPv6. As the internet continued to grow, the need for expanded address space became critical. With IOS 12.4, Cisco provided robust capabilities for transitioning from IPv4 to IPv6, ensuring that network managers could adopt the newer standard without sacrificing performance or reliability. This included support for routing protocols and other networking functions that were essential in an IPv6 environment.

Performance improvements were also a key aspect of IOS 12.4. The release optimized routing protocols, including Enhanced Interior Gateway Routing Protocol (EIGRP) and Open Shortest Path First (OSPF), to enhance convergence times and reduce latency. This effectively contributed to improved network efficiency and uptime.

Cisco also included advanced Quality of Service (QoS) capabilities in IOS 12.4, allowing organizations to prioritize critical traffic. Features such as class-based weighted fair queuing and low-latency queuing became invaluable for organizations requiring seamless voice and video communications over IP networks. This focus on QoS demonstrated Cisco's understanding of the growing importance of multimedia applications in modern business environments.

With a set of stable and scalable routing features, IOS 12.4 supports a variety of platforms, enabling businesses to deploy it across different networking hardware to suit their needs. The modularity of this IOS version makes it flexible for various applications, from small business networks to large enterprise systems.

In summary, Cisco Systems' IOS 12.4 brought forth a wealth of features aimed at enhancing security, performance, and flexibility. Through improved routing capabilities, strong IPv6 support, and advanced QoS features, this version laid the foundation for many of the networking principles that organizations still utilize today.
Top Page Image Contents