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

Step 2: Verify That Node-Link Protection Is Up

After you configure node-link protection, you must check that bypass paths are up. You can also check the number of LSPs protected by the bypass paths. In the network shown in Figure 7, two bypass paths should be up: one next-hop bypass path protecting the link between R1 and R2 (or next-hop 10.0.12.14), and a next-next-hop bypass path avoiding R2.

Action

To verify node-link protection (many-to-one backup), enter the following JUNOS CLI operational mode commands on the ingress router. You can also issue the commands on transit routers and other routers used in the bypass path for slightly different information.

show mpls lsp (See Sample Output)
show mpls lsp extensive (See Sample Output)
show rsvp interface (See Sample Output)
show rsvp interface extensive (See Sample Output)
show rsvp session detail (See Sample Output)

Sample Output

user@R1> show mpls lsp

Ingress LSP: 1 sessions

To              From            State Rt ActivePath       P     LSPname

192.168.5.1     192.168.1.1     Up     0 via-r2           *     lsp2-r1-to-r5

Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions

To              From            State   Rt Style Labelin Labelout LSPname

192.168.1.1     192.168.5.1     Up       0  1 FF       3        - r5-to-r1

Total 1 displayed, Up 1, Down 0

Transit LSP: 2 sessions

To              From            State   Rt Style Labelin Labelout LSPname

192.168.0.1     192.168.6.1     Up       0  1 FF 100464   101952 lsp1-r6-to-r0

192.168.6.1     192.168.0.1     Up       0  1 FF  100448        3 r0-to-t6

Total 2 displayed, Up 2, Down 0

What It Means

Sample output from R1 for the show mpls lsp command shows a brief description of the state of configured and active LSPs for which R1 is the ingress, transit, and egress router. All LSPs are up. R1 is the ingress router for lsp2-r1-to-r5, and the egress router for return LSP r5-to-r1. Two LSPs transit R1, lsp1-r6-to-r0 and the return LSP r0-to-t6. For more detailed information about the LSP, include the extensive option when you issue the show mpls lsp command.

Sample Output

user@R1> show mpls lsp extensive

Ingress LSP: 1 sessions

192.168.5.1

  From: 192.168.1.1, State: Up, ActiveRoute: 0, LSPname: lsp2-r1-to-r5

  ActivePath: via-r2 (primary)

  Node/Link protection desired

  LoadBalance: Random

  Encoding type: Packet, Switching type: Packet, GPID: IPv4

 *Primary   via-r2           State: Up

    SmartOptimizeTimer: 180

    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 3)

 10.0.12.14 S 10.0.24.2 S 10.0.45.2 S

    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 
10=SoftPreempt):

          10.0.12.14(Label=101872) 10.0.24.2(Label=101360) 10.0.45.2(Label=3)

   11 Jul 11 14:30:58 Link-protection Up

   10 Jul 11 14:28:28 Selected as active path

    [...Output truncated...]

  Created: Tue Jul 11 14:22:58 2006

Total 1 displayed, Up 1, Down 0

Egress LSP: 1 sessions

192.168.1.1

  From: 192.168.5.1, LSPstate: Up, ActiveRoute: 0

  LSPname: r5-to-r1, LSPpath: Primary

  Suggested label received: -, Suggested label sent: -

  Recovery label received: -, Recovery label sent: -

  Resv style: 1 FF, Label in: 3, Label out: -

  Time left:  146, Since: Tue Jul 11 14:28:36 2006

  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500

  Port number: sender 1 receiver 29228 protocol 0

  PATH rcvfrom: 10.0.12.14 (fe-0/1/0.0) 362 pkts

  Adspec: received MTU 1500

  PATH sentto: localclient

  RESV rcvfrom: localclient

  Record route: 10.0.45.2 10.0.24.2 10.0.12.14 <self>

Total 1 displayed, Up 1, Down 0

Transit LSP: 2 sessions

192.168.0.1

  From: 192.168.6.1, LSPstate: Up, ActiveRoute: 0

  LSPname: lsp1-r6-to-r0, LSPpath: Primary

  Suggested label received: -, Suggested label sent: -

  Recovery label received: -, Recovery label sent: 101952

  Resv style: 1 SE, Label in: 100464, Label out: 101952

  Time left:  157, Since: Tue Jul 11 14:31:38 2006

  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500

  Port number: sender 1 receiver 11131 protocol 0

  Node/Link protection desired

  Type: Node/Link protected LSP, using Bypass->10.0.12.14->10.0.24.2

      1 Jul 11 14:31:38 Node protection up, using Bypass->10.0.12.14->10.0.24.2

  PATH rcvfrom: 10.0.16.2 (so-0/0/3.0) 509 pkts

  Adspec: received MTU 1500 sent MTU 1500

  PATH sentto: 10.0.12.14 (fe-0/1/0.0) 356 pkts

  RESV rcvfrom: 10.0.12.14 (fe-0/1/0.0) 358 pkts

  Explct route: 10.0.12.14 10.0.24.2 10.0.45.2 10.0.50.2

  Record route: 10.0.16.2 <self> 10.0.12.14 10.0.24.2 10.0.45.2 10.0.50.2

192.168.6.1

  From: 192.168.0.1, LSPstate: Up, ActiveRoute: 0

  LSPname: r0-to-t6, LSPpath: Primary

  Suggested label received: -, Suggested label sent: -

  Recovery label received: -, Recovery label sent: 3

  Resv style: 1 FF, Label in: 100448, Label out: 3

  Time left:  147, Since: Tue Jul 11 14:31:36 2006

  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500

  Port number: sender 1 receiver 23481 protocol 0

  PATH rcvfrom: 10.0.12.14 (fe-0/1/0.0) 358 pkts

  Adspec: received MTU 1500 sent MTU 1500

  PATH sentto: 10.0.16.2 (so-0/0/3.0) 350 pkts

  RESV rcvfrom: 10.0.16.2 (so-0/0/3.0) 323 pkts

  Explct route: 10.0.16.2

  Record route: 10.0.50.2 10.0.45.2 10.0.24.2 10.0.12.14 <self> 10.0.16.2

Total 2 displayed, Up 2, Down 0

What It Means

Sample output from R1 for the show mpls lsp extensive command shows detailed information about all LSPs for which R1 is the ingress, egress, or transit router, including all past state history and the reason why an LSP failed. All LSPs are up. The main two LSPs lsp2-r1-to-r5 and lsp1-r6-to-r0 have node-link protection as indicated by the Node/Link protection desired field in the ingress and transit sections of the output. In the ingress section of the output, the Link-protection Up field shows that lsp2-r1-to-r5 has link protection up. In the transit section of the output, the Type: Node/Link protected LSP field shows that lsp1-r6-to-r0 has node-link protection up, and in case of failure will use the bypass LSP Bypass->10.0.12.14->10.0.24.2.

Sample Output

user@R1> show rsvp interface

RSVP interface: 4 active

                  Active Subscr- Static      Available   Reserved    Highwater

Interface   State resv   iption  BW          BW          BW          mark

fe-0/1/0.0  Up         2   100%  100Mbps     100Mbps     0bps        0bps

fe-0/1/1.0  Up         1   100%  100Mbps     100Mbps     0bps        0bps

fe-0/1/2.0  Up         0   100%  100Mbps     100Mbps     0bps        0bps

so-0/0/3.0  Up         1   100%  155.52Mbps  155.52Mbps  0bps        0bps

What It Means

Sample output from R1 for the show rsvp interface command shows four interfaces enabled with RSVP (Up). Interface fe-0/1/0.0 has two active RSVP reservations (Active resv) that might indicate sessions for the two main LSPs, lsp1-r6-to-r0 and lsp2-r1-to-r5. Interface fe-0/1/0.0 is the connecting interface between R1 and R2, and both LSPs are configured with a strict path through fe-0/1/0.0. For more detailed information about what is happening on interface fe-0/1/0.0, issue the show rsvp interface extensive command.

Sample Output

user@R1> show rsvp interface extensive

RSVP interface: 3 active

fe-0/1/0.0 Index 67, State Ena/Up

  NoAuthentication, NoAggregate, NoReliable, LinkProtection

  HelloInterval 9(second)

  Address 10.0.12.13

  ActiveResv 2, PreemptionCnt 0, Update threshold 10%

  Subscription 100%,

  bc0 = ct0, StaticBW 100Mbps

  ct0: StaticBW 100Mbps, AvailableBW 100Mbps

    MaxAvailableBW 100Mbps = (bc0*subscription)

    ReservedBW [0] 0bps[1] 0bps[2] 0bps[3] 0bps[4] 0bps[5] 0bps[6] 0bps[7] 0bps

  Protection: On, Bypass: 2, LSP: 2, Protected LSP: 2, Unprotected LSP: 0

      2 Jul 14 14:49:40 New bypass Bypass->10.0.12.14

      1 Jul 14 14:49:34 New bypass Bypass->10.0.12.14->10.0.24.2

    Bypass: Bypass->10.0.12.14, State: Up, Type: LP, LSP: 0, Backup: 0

      3 Jul 14 14:49:42 Record Route:  10.0.17.14 10.0.27.1

      2 Jul 14 14:49:42 Up

      1 Jul 14 14:49:42 CSPF: computation result accepted

    Bypass: Bypass->10.0.12.14->10.0.24.2, State: Up, Type: NP, LSP: 2, Backup:0

      4 Jul 14 14:50:04 Record Route:  10.0.17.14 10.0.79.2 10.0.59.1 10.0.45.1

      3 Jul 14 14:50:04 Up

      2 Jul 14 14:50:04 CSPF: computation result accepted

      1 Jul 14 14:49:34 CSPF failed: no route toward 10.0.24.2

[...Output truncated...]

What It Means

Sample output from R1 for the show rsvp interface extensive command shows more detailed information about the activity on all RSVP interfaces (3). However, only output for fe-0/1/0.0 is shown. Protection is enabled (Protection: On), with two bypass paths (Bypass: 2) protecting two LSPs (Protected LSP: 2). All LSPs are protected, as indicated by the Unprotected LSP: 0 field. The first bypass Bypass->10.0.12.14 is a link protection bypass path (Type: LP), protecting the link between R1 and R2, fe-0/1/0.0. The second bypass path 10.0.12.14->10.0.24.2 is a node-link protected LSP, avoiding R2 in case of node failure.

Sample Output

user@R1> show rsvp session detail

Ingress RSVP: 2 sessions

192.168.4.1

  From: 192.168.1.1, LSPstate: Up, ActiveRoute: 0

  LSPname: Bypass->10.0.12.14->10.0.24.2

  Suggested label received: -, Suggested label sent: -

  Recovery label received: -, Recovery label sent: 102000

  Resv style: 1 SE, Label in: -, Label out: 102000

  Time left:    -, Since: Tue Jul 11 14:30:53 2006

  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500

  Port number: sender 1 receiver 60120 protocol 0

  Type: Bypass LSP

    Number of data route tunnel through: 2

    Number of RSVP session tunnel through: 0

  PATH rcvfrom: localclient

  Adspec: sent MTU 1500

  Path MTU: received 1500

  PATH sentto: 10.0.17.14 (fe-0/1/1.0) 336 pkts

  RESV rcvfrom: 10.0.17.14 (fe-0/1/1.0) 310 pkts

  Explct route: 10.0.17.14 10.0.79.2 10.0.59.1 10.0.45.1

  Record route: <self> 10.0.17.14 10.0.79.2 10.0.59.1 10.0.45.1

192.168.5.1

  From: 192.168.1.1, LSPstate: Up, ActiveRoute: 0

  LSPname: lsp2-r1-to-r5, LSPpath: Primary

  Suggested label received: -, Suggested label sent: -

  Recovery label received: -, Recovery label sent: 101872

  Resv style: 1 SE, Label in: -, Label out: 101872

  Time left:    -, Since: Tue Jul 11 14:28:28 2006

  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500

  Port number: sender 2 receiver 60118 protocol 0

  Node/Link protection desired

  Type: Node/Link protected LSP

  PATH rcvfrom: localclient

  Adspec: sent MTU 1500

  Path MTU: received 1500

  PATH sentto: 10.0.12.14 (fe-0/1/0.0) 344 pkts

  RESV rcvfrom: 10.0.12.14 (fe-0/1/0.0) 349 pkts

  Explct route: 10.0.12.14 10.0.24.2 10.0.45.2

  Record route: <self> 10.0.12.14 10.0.24.2 10.0.45.2

Total 2 displayed, Up 2, Down 0

Egress RSVP: 1 sessions

192.168.1.1

  From: 192.168.5.1, LSPstate: Up, ActiveRoute: 0

  LSPname: r5-to-r1, LSPpath: Primary

  Suggested label received: -, Suggested label sent: -

  Recovery label received: -, Recovery label sent: -

  Resv style: 1 FF, Label in: 3, Label out: -

  Time left:  147, Since: Tue Jul 11 14:28:36 2006

  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500

  Port number: sender 1 receiver 29228 protocol 0

  PATH rcvfrom: 10.0.12.14 (fe-0/1/0.0) 348 pkts

  Adspec: received MTU 1500

  PATH sentto: localclient

  RESV rcvfrom: localclient

  Record route: 10.0.45.2 10.0.24.2 10.0.12.14 <self>

Total 1 displayed, Up 1, Down 0

Transit RSVP: 2 sessions

192.168.0.1

  From: 192.168.6.1, LSPstate: Up, ActiveRoute: 0

  LSPname: lsp1-r6-to-r0, LSPpath: Primary

  Suggested label received: -, Suggested label sent: -

  Recovery label received: -, Recovery label sent: 101952

  Resv style: 1 SE, Label in: 100464, Label out: 101952

  Time left:  134, Since: Tue Jul 11 14:31:38 2006

  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500

  Port number: sender 1 receiver 11131 protocol 0

  Node/Link protection desired

  Type: Node/Link protected LSP

  PATH rcvfrom: 10.0.16.2 (so-0/0/3.0) 488 pkts

  Adspec: received MTU 1500 sent MTU 1500

  PATH sentto: 10.0.12.14 (fe-0/1/0.0) 339 pkts

  RESV rcvfrom: 10.0.12.14 (fe-0/1/0.0) 343 pkts

  Explct route: 10.0.12.14 10.0.24.2 10.0.45.2 10.0.50.2

  Record route: 10.0.16.2 <self> 10.0.12.14 10.0.24.2 10.0.45.2 10.0.50.2

192.168.6.1

  From: 192.168.0.1, LSPstate: Up, ActiveRoute: 0

  LSPname: r0-to-t6, LSPpath: Primary

  Suggested label received: -, Suggested label sent: -

  Recovery label received: -, Recovery label sent: 3

  Resv style: 1 FF, Label in: 100448, Label out: 3

  Time left:  158, Since: Tue Jul 11 14:31:36 2006

  Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500

  Port number: sender 1 receiver 23481 protocol 0

  PATH rcvfrom: 10.0.12.14 (fe-0/1/0.0) 344 pkts

  Adspec: received MTU 1500 sent MTU 1500

  PATH sentto: 10.0.16.2 (so-0/0/3.0) 337 pkts

  RESV rcvfrom: 10.0.16.2 (so-0/0/3.0) 310 pkts

  Explct route: 10.0.16.2

  Record route: 10.0.50.2 10.0.45.2 10.0.24.2 10.0.12.14 <self> 10.0.16.2

Total 2 displayed, Up 2, Down 0

What It Means

Sample output from R1 shows detailed information about the RSVP sessions active on R1. All sessions are up, with two ingress sessions, one egress session, and two transit sessions.

Within the ingress section, the first session is a bypass path, as indicated by the Type: Bypass LSP field; and the second session is a protected LSP (lsp2-r1-to-r5) originating on R1, as indicated by the Type: Node/Link protected LSP field.

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