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

Step 2: Check the Administrative Group Configuration

Action

To check the administrative group configuration, enter the following JUNOS CLI operational mode commands, or issue the show command at the [edit protocols mpls] hierarchy level, as shown in the example below:

user@host> show configuration protocols mpls

user@host> show mpls interface        

user@host> show ted database extensive nodeID

Sample Output 1

[edit protocols mpls]

user@R1# show 

traceoptions {

    file cspf;

    flag cspf;

    flag cspf-node;

    flag cspf-link;

}

admin-groups {

    blue 4;

    red 8;

}

label-switched-path R1-to-R6 {

    to 10.0.0.6;

    metric 100;

    admin-group {

        include red;

        exclude blue;

    }

}

interface so-0/0/0.0;

interface so-0/0/1.0 {

    admin-group red;

}

interface so-0/0/2.0 {

    admin-group blue;

}

interface fxp0.0 {

    disable;

}



[edit protocols mpls]

user@R3# show 

admin-groups {

    blue 4;

}

interface fxp0.0 {

    disable;

}

interface so-0/0/0.0;

interface so-0/0/1.0;

interface so-0/0/2.0 {

interface so-0/0/3.0 {

    admin-group blue;

}



[edit protocols mpls]

user@R5# show 

admin-groups {

    red 8;

}

interface fxp0.0 {

    disable;

}

interface so-0/0/0.0 {

    admin-group red;

}

interface so-0/0/1.0;

interface so-0/0/2.0;



[edit protocols mpls]

user@R6# show 

admin-groups {

    blue 4;

    red 8;

}

label-switched-path R6-to-R1 {

    to 10.0.0.1;

}

interface so-0/0/0.0 {

    admin-group red;

}

interface so-0/0/1.0;

interface so-0/0/2.0;

interface so-0/0/3.0 {

    admin-group blue;

}

Sample Output 2

useruser@R1> show mpls interface        

Interface        State       Administrative groups

so-0/0/0.0       Up         <none>

so-0/0/1.0       Up          red

so-0/0/2.0       Up          blue



user@R1> show mpls interface        

Interface        State       Administrative groups

so-0/0/0.0       Up         <none>

so-0/0/1.0       Up          red

so-0/0/2.0       Up          blue



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          blue



user@R5> show mpls interface 

Interface        State       Administrative groups

so-0/0/0.0       Up          red

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          red

so-0/0/1.0       Up         <none>

so-0/0/2.0       Up         <none>

so-0/0/3.0       Up          blue

Sample Output 3

user@R1> show ted database extensive R1

TED database: 6 ISIS nodes 6 INET nodes

NodeID: R1.00(10.0.0.1)

  Type: Rtr, Age: 665 secs, LinkIn: 3, LinkOut: 3

  Protocol: IS-IS(2)

    To: R2.00(10.0.0.2), Local: 10.1.12.1, Remote: 10.1.12.2

      Color: 0 <none>

      Metric: 10

      Static BW: 155.52Mbps

      Reservable BW: 155.52Mbps

      Available BW [priority] bps:

          [0] 155.52Mbps   [1] 155.52Mbps  [2] 155.52Mbps  [3] 155.52Mbps  

          [4] 155.52Mbps   [5] 155.52Mbps  [6] 155.52Mbps  [7] 155.52Mbps  

      Interface Switching Capability Descriptor(1):

        Switching type: Packet

        Encoding type: Packet

        Maximum LSP BW [priority] bps:

          [0] 155.52Mbps   [1] 155.52Mbps  [2] 155.52Mbps  [3] 155.52Mbps  

          [4] 155.52Mbps   [5] 155.52Mbps  [6] 155.52Mbps  [7] 155.52Mbps  

    To: R5.00(10.0.0.5), Local: 10.1.15.1, Remote: 10.1.15.2

      Color: 0x100 red

      Metric: 10

      Static BW: 155.52Mbps

      Reservable BW: 155.52Mbps

      Available BW [priority] bps:

          [0] 155.52Mbps   [1] 155.52Mbps  [2] 155.52Mbps  [3] 155.52Mbps  

          [4] 155.52Mbps   [5] 155.52Mbps  [6] 155.52Mbps  [7] 155.52Mbps  

      Interface Switching Capability Descriptor(1):

        Switching type: Packet

        Encoding type: Packet

        Maximum LSP BW [priority] bps:

          [0] 155.52Mbps   [1] 155.52Mbps  [2] 155.52Mbps  [3] 155.52Mbps  

          [4] 155.52Mbps   [5] 155.52Mbps  [6] 155.52Mbps  [7] 155.52Mbps  

    To: R3.00(10.0.0.3), Local: 10.1.13.1, Remote: 10.1.13.2

      Color: 0x10 blue

      Metric: 10

      Static BW: 155.52Mbps

      Reservable BW: 155.52Mbps

      Available BW [priority] bps:

          [0] 155.52Mbps   [1] 155.52Mbps  [2] 155.52Mbps  [3] 155.52Mbps  

          [4] 155.52Mbps   [5] 155.52Mbps  [6] 155.52Mbps  [7] 155.52Mbps  

      Interface Switching Capability Descriptor(1):

        Switching type: Packet

        Encoding type: Packet

        Maximum LSP BW [priority] bps:

          [0] 155.52Mbps   [1] 155.52Mbps  [2] 155.52Mbps  [3] 155.52Mbps  

          [4] 155.52Mbps   [5] 155.52Mbps  [6] 155.52Mbps  [7] 155.52Mbps

What It Means

Sample Output 1 shows that administrative group coloring is correctly configured on all relevant routers. Administrative groups red and blue are configured at the [edit protocols mpls] hierarchy level, and relevant interfaces are associated with each administrative group correctly.

R3 is configured with blue coloring and the include and exclude statements are included in the configuration of R1 to ensure that LSP R1-to-R6 always transits R5. The inclusion of red coloring is not strictly necessary. To force the LSP to transit R5, you could color the links on R2 and R3 blue and then exclude the blue links. Red coloring is included in this example to demonstrate the fact that the CSPF algorithm excludes links that do not have a color configured, when the include statement is configured at the [edit protocols mpls] hierarchy level.

In addition, ingress router R1 has CSPF tracing configured in preparation for gathering information when the CSPF algorithm fails later in this example.

Sample Output 2 shows that the correct interfaces are associated with the red and blue administration groups on R1, R3, R5, and R6.

Sample Output 3 confirms that link coloring is correctly reported in the traffic engineering database for R1. Not shown is the traffic engineering database output for the remaining routers, which is similar to the R1 output, and correct.

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