[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

Verifying the MPLS Configuration

After configuring MPLS on your network, you must verify the correct configuration of both the MPLS and RSVP protocols. Incorrect configuration of either protocol prevents successful LSP creation.

Figure 5 illustrates the network with the example configurations used in this topic. For more details about the router configurations in this network, see .

Figure 5: MPLS Network Topology

Image g015527.gif

To verify the MPLS configuration, follow these steps:

  1. Verify MPLS Interfaces
  2. Verify the RSVP Protocol
  3. Verify RSVP Interfaces
  4. Verify Protocol Families

Verify MPLS Interfaces

Purpose

If the MPLS protocol is not configured correctly on the routers in your network, the interfaces are not able to perform MPLS switching.

Action

To verify MPLS interfaces, enter the following JUNOS command-line interface (CLI) operational mode command:

user@host> show mpls interface

Sample Output 1

The following sample output is for all routers in the network shown in Figure 5. 

user@R1> show mpls interface 
Interface        State       Administrative groups
so-0/0/0.0       Up         <none>
so-0/0/1.0       Up         <none>
so-0/0/2.0       Up         <none>

user@R2> show mpls interface 
Interface        State       Administrative groups
so-0/0/0.0       Up         <none>
so-0/0/1.0       Up         <none>
so-0/0/2.0       Up         <none>
so-0/0/3.0       Up         <none>

user@R3> show mpls interface  
Interface        State       Administrative groups
so-0/0/0.0       Up         <none>
so-0/0/1.0       Up         <none>
so-0/0/2.0       Up         <none>
so-0/0/3.0       Up         <none>

user@R4> show mpls interface  
Interface        State       Administrative groups
so-0/0/0.0       Up         <none>
so-0/0/1.0       Up         <none>
so-0/0/2.0       Up         <none>
so-0/0/3.0       Up         <none>

user@R5> show mpls interface  
Interface        State       Administrative groups
so-0/0/0.0       Up         <none>
so-0/0/1.0       Up         <none>
so-0/0/2.0       Up         <none>

user@R6> show mpls interface 
Interface        State       Administrative groups
so-0/0/0.0       Up         <none>
so-0/0/1.0       Up         <none>
so-0/0/2.0       Up         <none>
so-0/0/3.0       Up         <none>

Sample Output 2

user@R6>  show mpls interface
Interface        State       Administrative groups
so-0/0/0.0       Up         <none>
so-0/0/1.0       Up         <none>
so-0/0/3.0       Up         <none>       # so-0/0/2.0 is missing

Sample Output 3

 
user@host> show mpls interface
MPLS not configured

Meaning

Sample Output 1 shows that all MPLS interfaces on all routers in the network are enabled (Up) and can perform MPLS switching. If you fail to configure the correct interface at the [edit protocols mpls] hierarchy level or include the family mpls statement at the [edit interfaces type-fpc/pic/port unit number ] hierarchy level, the interface cannot perform MPLS switching, and does not appear in the output for the show mpls interface command.

Administrative groups are not configured on any of the interfaces shown in the example network in Figure 5. However, if they were, the output would indicate which affinity class bits are enabled on the router.

Sample Output 2 shows that interface so-0/0/2.0 is missing and therefore might be incorrectly configured. For example, the interface might not be included at the [edit protocols mpls] hierarchy level, or the family mpls statement might not be included at the [edit interfaces type-fpc/pic/port unit number] hierarchy level. If the interface is configured correctly, RSVP might not have signaled over this interface yet. For more information on determining which interface is incorrectly configured, see Verify Protocol Families.

Sample Output 3 shows that the MPLS protocol is not configured at the [edit protocols mpls] hierarchy level.

For more information on configuring MPLS on routers in your network, see Configuring MPLS on Your Network


Verify the RSVP Protocol

Purpose

If the RSVP protocol is not enabled on the routers in your network, the interface cannot signal LSPs.

Action

To verify that the RSVP protocol is enabled, enter the following JUNOS CLI command:

user@host> show rsvp version

Sample Output

user@R1> show rsvp version 
Resource ReSerVation Protocol, version 1. rfc2205 
   RSVP protocol           =  Enabled
   R(refresh timer)        = 30 seconds
   K(keep multiplier)      = 3
   Preemption              = Normal
   Soft-preemption cleanup = 30 seconds
   Graceful restart        = Disabled
   Restart helper mode     = Enabled
   Restart time            = 0 msec

Meaning

The sample output shows that the RSVP protocol is enabled on R1. The supported RSVP protocol is version 1, as defined in RFC 2205.

The RSVP refresh timer is set to 30 seconds, indicating that every 30 seconds, plus or minus 50 percent, the router will refresh the RSVP state with its directly connected neighbors by sending either a Path or a Resv message. The variable refresh time helps prevent harmonic oscillations in network traffic caused by periodic protocol updates.

The keepalive multiplier, K(keep multiplier), is input to a formula that helps determine the lifetime of an RSVP session. The session lifetime is reset each time the state is updated. The lifetime represents the duration of an RSVP session that does not receive any state updates (Path or Resv messages). The formula is:

RSVP session lifetime = (keep-multiplier + 0.5) * 1.5 * refresh-time

The RSVP preemption state is currently configured for normal preemption, indicating that only an LSP with a stronger priority can preempt an existing session; that is, the setup value of the new LSP is lower than the hold value of the existing LSP. Other options include aggressive preemption, which always preempts when there is insufficient bandwidth, and disabled, which prevents any preemption, regardless of LSP priority values.

Graceful restart is currently disabled and Restart helper mode is enabled. There are four combinations for Graceful restart and restart helper mode:

  1. Both Graceful restart and Restart helper mode are enabled.
  2. Graceful restart is enabled but Restart helper mode is disabled. An LSR with this configuration can restart gracefully but cannot help a neighbor with its restart and recovery procedures.
  3. Graceful restart is disabled but Restart helper mode is enabled. An LSR with this configuration can only help a restarting neighbor. It cannot restart gracefully itself.
  4. Graceful restart and Restart helper mode are both disabled. This configuration completely disables RSVP graceful restart (including restart and recovery procedures and helper mode). It is the same as an LSR that is not supported by RSVP graceful restart.

Restart time is the estimated time (in milliseconds) for an LSR to restart the RSVP traffic engineering component. In the example output, the restart time is 0 milliseconds, indicating that it is disabled.

The output is identical for all routers in the network shown in Figure 5.


Verify RSVP Interfaces

Purpose

If the RSVP protocol is not configured correctly on the routers in your network, the interfaces cannot signal LSPs.

Action

To verify RSVP interfaces, enter the following JUNOS CLI operational mode command:

user@host> show rsvp interface

Sample Output 1

user@R1> show rsvp interface 
RSVP interface: 4 active
                  Active Subscr- Static      Available   Reserved    Highwater
Interface   State resv   iption  BW          BW          BW          mark
so-0/0/0.0  Up         2   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/1.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/2.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       

user@R2> show rsvp interface 
RSVP interface: 5 active
                  Active Subscr- Static      Available   Reserved    Highwater
Interface   State resv   iption  BW          BW          BW          mark
so-0/0/0.0  Up         1   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/1.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/2.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/3.0  Up         1   100%  155.52Mbps  155.52Mbps  0bps        0bps       

user@R3> show rsvp interface 
RSVP interface: 5 active
                  Active Subscr- Static      Available   Reserved    Highwater
Interface   State resv   iption  BW          BW          BW          mark
so-0/0/0.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/1.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/2.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/3.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps 

user@R4> show rsvp interface 
RSVP interface: 5 active
                  Active Subscr- Static      Available   Reserved    Highwater
Interface   State resv   iption  BW          BW          BW          mark
so-0/0/0.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/1.0  Up         1   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/2.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/3.0  Up         1   100%  155.52Mbps  155.52Mbps  0bps        0bps 

user@R5> show rsvp interface 
RSVP interface: 4 active
                  Active Subscr- Static      Available   Reserved    Highwater
Interface   State resv   iption  BW          BW          BW          mark
so-0/0/0.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/1.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/2.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps 

user@R6> show rsvp interface 
RSVP interface: 5 active
                  Active Subscr- Static      Available   Reserved    Highwater
Interface   State resv   iption  BW          BW          BW          mark
so-0/0/0.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/1.0  Up         1    100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/2.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/3.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps

Sample Output 2

user@R6> show rsvp interface 
RSVP interface: 3 active
                  Active Subscr- Static      Available   Reserved    Highwater
Interface   State resv   iption  BW          BW          BW          mark
so-0/0/0.0  Up         1   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/1.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps       
so-0/0/2.0  Up         0   100%  155.52Mbps  155.52Mbps  0bps        0bps  #so-0/0/3.0 is missing

Sample Output 3

user@host# show rsvp interface
RSVP not configured

Meaning

Sample Output 1 shows that all interfaces on all routers in the network are enabled with RSVP, including the management interface (fxp0). The output for all routers in the network includes similar information, so we will examine R6 in detail.

R6 has five interfaces enabled with RSVP (Up). Interface so-0/1/1.0 has a single active RSVP reservation (Active resv) that did not change the default subscription percentage of 100 percent (Subscription). Interface so-0/1/1.0 did not assign a static bandwidth (Static BW) to the logical unit and therefore inherited 100 percent of the physical interface rate as the bandwidth available (Available BW) for RSVP sessions. Interface so-0/1/1.0 has no bandwidth assigned (Reserved BW), and no RSVP bandwidth allocation at any single instant in time (Highwater mark).

Sample Output 2 shows that interface so-0/0/3.0 is missing. If you do not configure the correct interface at the [edit protocols rsvp] hierarchy level, the interface cannot signal LSPs, and does not appear in the output for the show rsvp interface command. For more information on configuring MPLS on routers in your network, see Configuring MPLS on Your Network.

Sample Output 3 shows that the RSVP protocol is not configured at the [edit protocols rsvp] hierarchy level.


Verify Protocol Families

Purpose

If a logical interface does not have MPLS enabled, it cannot perform MPLS switching. This step allows you to quickly determine which interfaces are configured with MPLS and other protocol families.

Action

To verify the protocol families configured on the routers in your network, enter the following JUNOS CLI operational mode command:

user@host> show interfaces terse

Sample Output 1

user@R1> show interfaces terse
Interface               Admin Link Proto Local                 Remote
so-0/0/0                up    up  
so-0/0/0.0              up    up   inet  10.1.12.1/30    
                                    iso  
                                    mpls 
so-0/0/1                up    up  
so-0/0/1.0              up    up   inet  10.1.15.1/30    
                                   iso  
                                   mpls 
so-0/0/2                up    up  
so-0/0/2.0              up    up   inet  10.1.13.1/30    
                                   iso  
                                   mpls 
so-0/0/3                up    down

user@R2> show interfaces terse
Interface               Admin Link Proto Local                 Remote
so-0/0/0                up    up  
so-0/0/0.0              up    up   inet  10.1.12.2/30    
                                   iso  
                                   mpls 
so-0/0/1                up    up  
so-0/0/1.0              up    up   inet  10.1.23.1/30    
                                   iso  
                                   mpls 
so-0/0/2                up    up  
so-0/0/2.0              up    up   inet  10.1.26.1/30    
                                   iso  
                                   mpls 
so-0/0/3                up    up  
so-0/0/3.0              up    up   inet  10.1.24.1/30    
                                   iso  
                                   mpls 

user@R3> show interfaces terse
Interface               Admin Link Proto Local                 Remote
so-0/0/0                up    up  
so-0/0/0.0              up    up   inet  10.1.34.1/30    
                                   iso  
                                   mpls 
so-0/0/1                up    up  
so-0/0/1.0              up    up   inet  10.1.23.2/30    
                                   iso  
                                   mpls 
so-0/0/2                up    up  
so-0/0/2.0              up    up   inet  10.1.13.2/30    
                                   iso  
                                   mpls 
so-0/0/3                up    up  
so-0/0/3.0              up    up   inet  10.1.36.1/30    
                                   iso  
                                   mpls 

user@R4> show interfaces terse
Interface               Admin Link Proto Local                 Remote
so-0/0/0                up    up  
so-0/0/0.0              up    up   inet  10.1.34.2/30    
                                   iso  
                                   mpls 
so-0/0/1                up    up  
so-0/0/1.0              up    up   inet  10.1.46.1/30    
                                   iso  
                                   mpls 
so-0/0/2                up    up  
so-0/0/2.0              up    up   inet  10.1.45.1/30    
                                   iso  
                                   mpls 
so-0/0/3                up    up  
so-0/0/3.0              up    up   inet  10.1.24.2/30    
                                   iso  
                                   mpls 

user@R5> show interfaces terse
Interface               Admin Link Proto Local                 Remote
so-0/0/0                up    up  
so-0/0/0.0              up    up   inet  10.1.56.1/30    
                                   iso  
                                   mpls 
so-0/0/1                up    up  
so-0/0/1.0              up    up   inet  10.1.15.2/30    
                                   iso  
                                   mpls 
so-0/0/2                up    up  
so-0/0/2.0              up    up   inet  10.1.45.2/30    
                                   iso  
                                   mpls 
so-0/0/3                up    down

user@R6>  show interfaces terse
Interface               Admin Link Proto Local                 Remote
so-0/0/0                up    up  
so-0/0/0.0              up    up   inet  10.1.56.2/30    
                                   iso  
                                   mpls 
so-0/0/1                up    up  
so-0/0/1.0              up    up   inet  10.1.46.2/30    
                                   iso  
                                   mpls 
so-0/0/2                up    up  
so-0/0/2.0              up    up   inet  10.1.26.2/30    
                                   iso  
                                   mpls 
so-0/0/3                up    up  
so-0/0/3.0              up    up   inet  10.1.36.2/30    
                                   iso  
                                   mpls

Sample Output 2

user@R6> show interfaces terse
Interface               Admin Link Proto Local                 Remote
so-0/0/0                up    up  
so-0/0/0.0              up    up   inet  10.1.56.2/30    
                                   iso  
                                   mpls 
so-0/0/1                up    up  
so-0/0/1.0              up    up   inet  10.1.46.2/30    
                                   iso  
                                   mpls 
so-0/0/2                up    up  
so-0/0/2.0              up    up   inet  10.1.26.2/30    
                                   iso  #The mpls statement is missing.
so-0/0/3                up    up  
so-0/0/3.0              up    up   inet  10.1.36.2/30    
                                   iso  
                                   mpls

Meaning

Sample Output 1 shows the interface, the administrative status of the link (Admin), the data link layer status of the link (Link), the protocol families configured on the interface (Proto), and the local and remote addresses on the interface.

All interfaces on all routes in the network shown in Figure 5 are administratively enabled and functioning at the data link layer with MPLS and IS-IS, and have an inet address. All are configured with an IPv4 protocol family (inet), and have the IS-IS (iso) and MPLS (mpls) protocol families configured at the [edit interfaces type-fpc/pic/port unit number] hierarchy level.

Sample Output 2 shows that interface so-0/0/2.0 on R6 does not have the mpls statement included at the [edit interfaces type-fpc/pic/port unit number] hierarchy level. For information on how to configure MPLS on an interface, see Configuring MPLS on Your Network.

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]