Step 6: Verify the MPLS Configuration

Purpose

After you have checked the transit and ingress routers, used the traceroute command to verify the BGP next hop, and used the ping command to verify the active path, you can check for problems with the MPLS configuration at the [edit protocols mpls] and [edit interfaces] hierarchy levels.

Action

To verify the MPLS configuration, enter the following commands from the ingress, transit, and egress routers:

user@host> show configuration protocols mpls

user@host> show configuration interfaces

Sample Output 1

user@R1> show configuration protocols mpls

label-switched-path R1-to-R6 {

    to 10.0.0.6;

}

inactive: interface so-0/0/0.0;

inactive: interface so-0/0/1.0;

interface so-0/0/2.0;

interface fxp0.0 {

    disable;

}

user@R3> show configuration protocols mpls

interface fxp0.0 {

    disable;

}

inactive: interface so-0/0/0.0;

inactive: interface so-0/0/1.0;

interface so-0/0/2.0;

interface so-0/0/3.0;

user@R6> show configuration protocols mpls 

label-switched-path R6-to-R1 {

    to 10.0.0.1;

}

inactive: interface so-0/0/0.0;

inactive: interface so-0/0/1.0;

inactive: interface so-0/0/2.0;

inactive: interface so-0/0/3.0;                                    <<< Incorrectly configured

Sample Output 2

user@R6> show configuration interfaces

so-0/0/0 {

    unit 0 {

        family inet {

            address 10.1.56.2/30;

        }

        family iso;

        family mpls;

    }

}

so-0/0/1 {

    unit 0 {

        family inet {

            address 10.1.46.2/30;

        }

        family iso;

        family mpls;

    }

}

so-0/0/2 {

    unit 0 {

        family inet {

            address 10.1.26.2/30;

        }

        family iso;

        family mpls;

    }

}

so-0/0/3 {

    unit 0 {

        family inet {

            address 10.1.36.2/30;

        }

        family iso;

        family mpls;

    }

}

fxp0 {

    unit 0 {

        family inet {

            address 192.168.70.148/21;

        }

    }

}

lo0 {

    unit 0 {

        family inet {

            address 10.0.0.6/32;

            address 127.0.0.1/32;

        }

        family iso {

            address 49.0003.1000.0000.0006.00;

        }

    }

}

What It Means

Sample Output 1 from the ingress, transit, and egress routers shows that the configuration of interfaces on egress router R6 is incorrect. Interface so-0/0/3.0 is included as inactive at the [edit protocols mpls] hierarchy level, when it should be active because it is the interface through which the LSP travels.

Sample Output 2 shows that interfaces are correctly configured for MPLS on egress router R6. The interfaces are also correctly configured on the ingress and transit routers (not shown).