Viewing Information About RSVP-Signaled LSPs in the Routing Tables
Problem
You want to check the routing tables to verify that an RSVP-signaled LSP has been established and is being used.
Solution
On the ingress router, look in the inet.3 routing table to view the RSVP routes:
aviva@R1> show route table inet.3 inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.0.0.6/32 *[RSVP/7] 00:17:28, metric 2 > via so-0/0/2.0, label-switched-path R1-to-R6
On the transit router, look in the mpls.0 table to see the routers label information:
aviva@R3> show route table mpls.0 mpls.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 0 *[MPLS/0] 06:28:10, metric 1 Receive 1 *[MPLS/0] 06:28:10, metric 1 Receive 2 *[MPLS/0] 06:28:10, metric 1 Receive 100048 *[RSVP/7] 05:55:24, metric 1 > via so-0/0/2.0, label-switched-path R6-to-R1 100048(S=0) *[RSVP/7] 05:55:24, metric 1 > via so-0/0/2.0, label-switched-path R6-to-R1 100064 *[RSVP/7] 00:18:59, metric 1 > via so-0/0/3.0, label-switched-path R1-to-R6 100064(S=0) *[RSVP/7] 00:18:59, metric 1 > via so-0/0/3.0, label-switched-path R1-to-R6
Discussion
MPLS and RSVP store their routing and forwarding information in two routing tables, inet.3 and mpls.0. The inet.3 table contains the routers learned from the signaling protocol, RSVP (and also LDP), which MPLS uses to make forwarding decisions. The show route table inet.3 command lists the routes to RSVP-signaled LSP. You can also use the show route protocol rsvp command to display the same information:
aviva@R1> show route protocol rsvp inet.0: 14 destinations, 18 routes (14 active, 0 holddown, 0 hidden) inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.0.0.6/32 *[RSVP/7] 00:32:04, metric 2 > via so-0/0/2.0, label-switched-path R1-to-R6
The inet.0 unicast routing table doesn contain any routes learned from RSVP, and the inet.3 table has one route, to 10.0.0.6, the LSPs egress router. The second line of the routing entry shows that the path to the egress router goes out the so-0/0/2 interface and travels along LSP R1-to-R6. The detail version of both show route commands gives more information about the route and LSP:
aviva@R1> show route table inet.3 detail inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) 10.0.0.6/32 (1 entry, 1 announced) State:* RSVP Preference: 7 Next-hop reference count: 7 Next hop: via so-0/0/2.0 weight 0x1, selected Label-switched-path R1-to-R6 Label operation: Push 100064 State: <Active Int> Local AS: 65432 Age: 23:52 Metric: 2 Task: RSVP Announcement bits (2): 2-Resolve tree 1 3-Resolve tree 2 AS path: I
The first highlighted line shows the name of the LSP, while the Label operation line shows the label operation performed by this route, here a push operation, and the label value that is placed into the MPLS header.
The inet.3 routing table is only on the ingress router because this is the only router that can place traffic into the LSP. This is important to remember when troubleshooting RSVP-signaled LSPs, so you don become confused when looking for routes on different routers. Checking the transit router confirms that the inet.3 table is not present:
aviva@R3> show route table inet.3 aviva@R3>
The second routing table used by RSVP is mpls.0, which stores the label bindings for the LSPs:
aviva@R3> show route table mpls.0 mpls.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 0 *[MPLS/0] 06:50:42, metric 1 Receive 1 *[MPLS/0] 06:50:42, metric 1 Receive 2 *[MPLS/0] 06:50:42, metric 1 Receive 100048 *[RSVP/7] 06:17:56, metric 1 > via so-0/0/2.0, label-switched-path R6-to-R1 100048(S=0) *[RSVP/7] 06:17:56, metric 1 > via so-0/0/2.0, label-switched-path R6-to-R1 100064 *[RSVP/7] 00:41:31, metric 1 > via so-0/0/3.0, label-switched-path R1-to-R6 100064(S=0) *[RSVP/7] 00:41:31, metric 1 > via so-0/0/3.0, label-switched-path R1-to-R6
Recipe 14.3 explains how to interpret the entries in the mpls.0 table.
The JUNOS software maintains the mpls.0 table on all routers along the LSP, but only the table on the transit router contains information about the labels being used for LSP signaling. On the egress and egress routers, the mpls.0 table lists only the reserved labels:
aviva@R1> show route table mpls.0 mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 0 *[MPLS/0] 07:01:51, metric 1 Receive 1 *[MPLS/0] 07:01:51, metric 1 Receive 2 *[MPLS/0] 07:01:51, metric 1 Receive
Again, this is important to remember when monitoring and troubleshooting LSPs.
Because BGP is also configured on the MPLS routers, when the BGP next hop is the same as the LSP egress address, the JUNOS default behavior uses the LSP for the BGP traffic. You see this in the routing-table entry:
aviva@R1> show route protocol bgp inet.0: 14 destinations, 18 routes (14 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 100.100.6.0/24 *[BGP/170] 4w6d 02:45:37, localpref 100, from 10.0.0.6 AS path: I > via so-0/0/2.0, label-switched-path R1-to-R6
Here, the route to 100.100.6.0, learned by BGP, is the route over the R1-to-R6 LSP.
The JUNOS software installs the active routes from the inet.3 and mpls.0 table into the Routing Engines forwarding table. On the ingress router, the IPv4 forwarding table includes the following routes:
aviva@R1> show route forwarding-table family inet Routing table: inet Internet: Destination Type RtRef Next hop Type Index NhRef Netif 10.0.0.3/32 user 1 ucst 330 6 so-0/0/2.0 10.0.0.6/32 user 1 ucst 330 6 so-0/0/2.0 100.100.6.0/24 user 0 indr 262142 2 Push 100064 so-0/0/2.0
The destinations to the transit and egress routers, 10.0.0.3 and 10.0.0.6, show up simply as unicast routes. The destination 100.100.6.0, learned from BGP and by using the LSP, shows as type indr (indirect) and you see the label (100064) and label operation (Push).
On the transit router, the MPLS forwarding table lists the labels used to forward the MPLS packets:
aviva@R3> show route forwarding-table family mpls Routing table: mpls MPLS: Destination Type RtRef Next hop Type Index NhRef Netif default perm 0 dscd 28 1 0 user 0 recv 27 3 1 user 0 recv 27 3 2 user 0 recv 27 3 100048 user 0 Pop so-0/0/2.0 100048(S=0) user 0 Pop so-0/0/2.0 100064 user 0 Pop so-0/0/3.0 100064(S=0) user 0 Pop so-0/0/3.0
These labels match what you see in the show route mpls.0 output on the transit router. These labels are installed into the Packet Forwarding Engines forwarding table:
aviva@R3> show pfe route mpls MPLS Route Table 0, MPLS.0, 0x0: Destination Type ID NhRef ----------------------- -------- ----- ----- default Discard 28 1 0 Receive 27 3 1 Receive 27 3 2 Receive 27 3 100048 Unicast 336 1 so-0/0/2.0 100048(S=0) Unicast 337 1 so-0/0/2.0 100064 Unicast 334 1 so-0/0/3.0 100064(S=0) Unicast 335 1 so-0/0/3.0
On the ingress and egress routers, the output of the show route forwarding-table family mpls and show pfe route mpls commands on the ingress and egress route lists only the reserved labels.
See Also
Recipes 8.1 and 14.3
Router Configuration and File Management
- Introduction
- Configuring the Router for the First Time
- Configuring the Router from the CLI
- Getting Exclusive Access to Configure the Router
- Displaying the Commands to Recreate a Configuration
- Including Comments in the Configuration
- Checking the Syntax of the Configuration
- Activating the Router Configuration
- Debugging a Failed Commit
- Exiting Configuration Mode
- Keeping a Record of Configuration Changes
- Determining What Changes You Have Made to the Configuration
- Configuring the Router by Copying a File from a Server
- Configuring the Router by Copying Text from a Terminal Window
- Backing Up the Routers Configuration
- Scheduling the Activation of a Configuration
- Provisionally Activating a Configuration
- Loading a Previous Router Configuration
- Creating an Emergency Rescue Configuration
- Backing Up Filesystems on M-Series and T-Series Routers
- Backing Up Filesystems on J-Series Routers
- Restoring a Backed-Up Filesystem
- Installing a Different Software Release on M-Series and T-Series Routers
- Installing a Different Software Release on J-Series Routers
- Creating an Emergency Boot Disk
- Gathering Software Version Information
- Gathering Hardware Inventory Information
- Finding Out How Long the Router Has Been Up
- Gathering Information Before Contacting Support
- Managing Routers with Similar Configurations
- Managing Redundant Routing Engines
- Using the Second Routing Engine to Upgrade to a New Software Version
Basic Router Security and Access Control
- Basic Router Security and Access Control
- Introduction
- Allowing Access to the Router
- Controlling Root Authentication
- Logging In to the Routers Console
- Setting the Login Authentication Methods
- Setting Up Login Accounts on the Router
- Changing the Format of Plain-Text Passwords
- Changing the Plain-Text Password Encryption Method
- Creating a Login Account for Remote Authentication
- Creating a Group Login Account
- Customizing Account Privileges
- Creating a Privilege Class that Hides Encrypted Passwords
- Setting Up RADIUS User Authentication
- Setting Up TACACS+ User Authentication
- Restricting Inbound SSH and Telnet Access
- Setting the Source Address for Telnet Connections
- Creating a Login Banner
- Finding Out Who Is Logged In to the Router
- Logging Out of the Router
- Forcibly Logging a User Out
IPSec
- IPSec
- Introduction
- Configuring IPSec
- Configuring IPSec Dynamic SAs
- Creating IPSec Dynamic SAs on J-Series Routers or Routers with AS PICs
- Using Digital Certificates to Create Dynamic IPSec SAs
SNMP
- SNMP
- Introduction
- Configuring SNMP
- Setting Router Information for the MIB-II System Group
- Setting Up SNMP Traps
- Controlling SNMP Access to the Router
- Using a Firewall Filter to Protect SNMP Access
- Controlling Access to Router MIBs
- Extracting Software Inventory Information with SNMP
- Extracting Hardware Inventory Information with SNMP
- Collecting Router Operational Information with SNMP
- Logging SNMP Access to the Router
- Logging Enterprise-Specific Traps
- Using RMON Traps to Monitor the Routers Temperature
- Configuring SNMPv3
- Tracking Router Configuration Changes
- Setting Up SNMPv3 Traps
Logging
- Logging
- Introduction
- Turning On Logging
- Limiting the Messages Collected
- Including the Facility and Severity in Messages
- Changing the Size of a Logging File
- Clearing the Routers Logfiles
- Sending Log Messages to Your Screen
- Sending Logging Messages to a Log Server
- Saving Logging Messages to the Other Routing Engine
- Turning Off Logging
- Turning On Basic Tracing
- Monitoring Interface Traffic
NTP
- NTP
- Introduction
- Setting the Date and Time on the Router Manually
- Setting the Time Zone
- Synchronizing Time When the Router Boots
- Synchronizing Time Periodically
- Authenticating NTP
- Checking NTP Status
Router Interfaces
- Router Interfaces
- Introduction
- Viewing Interface Status
- Viewing Traffic Statistics on an Interface
- Setting an IP Address for the Router
- Setting the Routers Source Address
- Configuring an IPv4 Address on an Interface
- Configuring an IPv6 Address on an Interface
- Configuring an ISO Address on an Interface
- Creating an MPLS Protocol Family on a Logical Interface
- Configuring an Interface Description
- Choosing Primary and Preferred Interface Addresses
- Using the Management Interface
- Finding Out What IP Addresses Are Used on the Router
- Configuring Ethernet Interfaces
- Using VRRP on Ethernet Interfaces
- Connecting to an Ethernet Switch
- Configuring T1 Interfaces
- Performing a Loopback Test on a T1 Interface
- Setting Up a BERT Test on a T1 Interface
- Configuring Frame Relay on a T1 Interface
- Configuring a SONET Interface
- Using APS to Protect Against SONET Circuit Failures
- Configuring an ATM Interface
- Dealing with Nonconfigurable Interfaces
- Configuring Interfaces Before the PICs Are Installed
IP Routing
- IP Routing
- Introduction
- Viewing the Routes in the Routing Table
- Viewing Routes to a Particular Prefix
- Viewing Routes Learned from a Specific Protocol
- Displaying the Routes in the Forwarding Table
- Creating Static Routes
- Blackholing Routes
- Filtering Traffic Using Unicast Reverse-Path Forwarding
- Aggregating Routes
- Load-Balancing Traffic Flows
- Adding Martian Addresses
- Changing Route Preferences to Migrate to Another IGP
- Configuring Routing Protocols to Restart Without Losing Adjacencies
Routing Policy and Firewall Filters
- Routing Policy and Firewall Filters
- Introduction
- Creating a Simple Routing Policy
- Changing a Routes Routing Information
- Filtering Routes by IP Address
- Filtering Long Prefixes
- Filtering Unallocated Prefix Blocks
- Creating a Chain of Routing Policies
- Making Sure a Routing Policy Is Functioning Properly
- Creating a Simple Firewall Filter that Matches Packet Contents
- Creating a Firewall Filter that Negates a Match
- Reordering Firewall Terms
- Filtering Traffic Transiting the Router
- Using a Firewall Filter to Count Traffic on an Interface
- Logging the Traffic on an Interface
- Limiting Traffic on an Interface
- Protecting the Local Routing Engine
- Rate-Limiting Traffic Flow to the Routing Engine
- Using Counters to Determine Whether a Router Is Under Attack
RIP
- RIP
- Introduction
- Configuring RIP
- Having RIP Advertise Its Routes
- Configuring RIP for IPv6
- Enabling RIP Authentication
- Routing RIP Traffic over Faster Interfaces
- Sending Version 1 Update Messages
- Tracing RIP Protocol Traffic
IS-IS
- IS-IS
- Introduction
- Configuring IS-IS
- Viewing the IS-IS Link-State Database
- Viewing Routes Learned by IS-IS
- Configuring IS-IS for IPv6
- Configuring a Level 1Only Router
- Controlling DIS Election
- Enabling IS-IS Authentication
- Redistributing Static Routes into IS-IS
- Leaking IS-IS Level 2 Routes into Level 1
- Adjusting IS-IS Link Costs
- Improving IS-IS Convergence Times
- Moving IS-IS Traffic off a Router
- Disabling IS-IS on an Interface
- Tracing IS-IS Protocol Traffic
OSPF
- Introduction
- Configuring OSPF
- Viewing Routes Learned by OSPF
- Viewing the OSPF Link-State Database
- Configuring OSPF for IPv6
- Configuring a Multiarea OSPF Network
- Setting Up Stub Areas
- Creating a Not-So-Stubby Area
- Summarizing Routes in OSPF
- Enabling OSPF Authentication
- Redistributing Static Routes into OSPF
- Adjusting OSPF Link Costs
- Improving OSPF Convergence Times
- Moving OSPF Traffic off a Router
- Disabling OSPF on an Interface
- Tracing OSPF Protocol Traffic
BGP
- Introduction
- Configuring a BGP Session Between Routers in Two ASs
- Configuring BGP on Routers Within an AS
- Diagnosing TCP Session Problems
- Adjusting the Next-Hop Attribute
- Adjusting Local Preference Values
- Removing Private AS Numbers from the AS Path
- Prepending AS Numbers to the AS Path
- Filtering BGP Routes Based on AS Paths
- Restricting the Number of Routes Advertised to a BGP Peer
- Authenticating BGP Peers
- Setting Up Route Reflectors
- Mitigating Route Instabilities with Route Flap Damping
- Adding a BGP Community to Routes
- Load-Balancing BGP Traffic
- Tracing BGP Protocol Traffic
MPLS
- Introduction
- Configuring LSPs Using LDP as the Signaling Protocol
- Viewing Information and LDP-Signaled LSPs in the Routing Tables
- Verifying that an LDP-Signaled LSP Is Carrying Traffic
- Enabling LDP Authentication
- Tracing LDP Operations
- Setting Up RSVP-Signaled LSPs
- Viewing Information About RSVP-Signaled LSPs in the Routing Tables
- Verifying Packet Labels
- Verifying that the RSVP-Signaled LSP Is Carrying Traffic
- Configuring RSVP Authentication
- Protecting an LSPs Path
- Using Fast Reroute to Reduce Packet Loss Following a Link Failure
- Automatically Allocating Bandwidth
- Prioritizing LSPs
- Allowing IGP Traffic to Use an LSP
- Installing LSPs into the Unicast Routing Table
- Tracing RSVP Operations
VPNs
- Introduction
- Setting Up a Simple Layer 3 VPN
- Viewing the VPN Routing Tables
- Adding a VPN for a Second Customer
IP Multicast
- Introduction
- Configuring PIM-SM
- Manually Establishing a PIM-SM RP
- Using Auto-RP to Dynamically Map RPs
- Setting Up a PIM-SM Bootstrap Router
- Filtering PIM-SM Bootstrap Messages
- Configuring Multiple RPs in a PIM-SM Domain with Anycast RP
- Configuring Multiple RPs in a PIM-SM Domain Anycast PIM
- Limiting the Group Ranges an RP Services
- Viewing Multicast Routes
- Checking the Groups for Which a PIM-SM Router Maintains Join State
- Manually Configuring IGMP
- Using SSM
- Connecting PIM-SM Domains Using MSDP and MBGP
- Configuring PIM-DM
- Tracing PIM Packets
EAN: 2147483647
Pages: 290
