Step 3: Verify Interfaces

Action

To determine that the relevant interfaces are up and configured correctly, enter the following commands from the ingress, transit, and egress routers:

user@host> show interfaces terse

user@host> show configuration interfaces type-fpc/pic/port

Sample Output

user@R1> show interfaces so* 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  <<< family mpls is missing

so-0/0/3                up    down

user@R1> show configuration interfaces so-0/0/2 

unit 0 {

    family inet {

        address 10.1.13.1/30;

    }

    family iso; <<< family mpls is missing

}

What It Means

The sample output shows that interface so-0/0/2.0 on the ingress router does not have the family mpls statement configured at the [edit interfaces type-fpc/pic/port] hierarchy level, indicating that the interface is incorrectly configured to support the LSP. The LSP is configured correctly at the [edit protocols mpls] hierarchy level.

The output from the transit and egress routers (not shown) shows that the interfaces on those routers are configured correctly.