[j-nsp] RSVP Fast Reroute Node Protection
Judah Scott
judah.scott.iam at gmail.com
Thu Jul 30 20:46:10 EDT 2009
Thanks all for your help, however still only link protection is being
created instead of the desired node protection. I am going to use a transit
lsp case for my example. The ted database shows links which if you take
time to map it out visually could/should be used to provide node protection
however only link protection bypass is created. I've included
(transitlsp.txt) much output and a map of what the links look like. It's
best viewed with a monospace font.
Maybe there is something else that is required which I am missing for node
protection to work.
Thanks,
J Scott
On Thu, Jul 30, 2009 at 3:52 PM, Harry Reynolds <harry at juniper.net> wrote:
> Thanks Kari, you appear correct. I was looking at a config that did not
> match the topo in my head. Sorry for the mis-info.
>
> Regards
>
>
>
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net [mailto:
> juniper-nsp-bounces at puck.nether.net] On Behalf Of Kari Asheim
> Sent: Thursday, July 30, 2009 3:10 PM
> To: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] RSVP Fast Reroute Node Protection
>
> On Thu, Jul 30, 2009 at 02:15:04PM -0700, Harry Reynolds wrote:
>
> > I think that you only need to configure the rsvp interface
> > <interface-name> link-protection statement on the lsp's protection
> > paths. That is to say, if the primary path exits a transit node on
> > fe-0/1/1, and you want that node to provide link or link-node
> > protection for that LSP, you would add the link-protection statement
> > to some other rsvp/mpls enabled interface that is not Fast
> > Ethernet-0/1/1. Adding the statement to the lsp's primary path
> > interfaces should have no ill effect, but obviously no gain as the
> > primary and link protection interfaces now share the same fate.
>
> I think you need to configure rsvp interface <> link-protection on the
> links of the primary path. A very simple example, link-protecting a one-hop
> LSP:
>
> ka at m320-1# run show mpls lsp ingress detail
> Ingress LSP: 1 sessions
>
> 10.0.0.5
> From: 10.0.0.4, State: Up, ActiveRoute: 0, LSPname: to-m320-2
> ActivePath: (primary)
> Link protection desired
> LoadBalance: Random
> Encoding type: Packet, Switching type: Packet, GPID: IPv4
> *Primary State: Up
> Priorities: 7 0
> SmartOptimizeTimer: 180
> Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 1)
> 10.0.1.2 S
> Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node
> 10=SoftPreempt):
> 10.0.1.2(Label=3)
> Total 1 displayed, Up 1, Down 0
>
>
> ka at m320-1# run show mpls lsp bypass ingress detail
> Ingress LSP: 2 sessions
>
> 10.0.0.5
> From: 10.0.0.4, LSPstate: Up, ActiveRoute: 0
> LSPname: Bypass->10.0.1.2
> Suggested label received: -, Suggested label sent: -
> Recovery label received: -, Recovery label sent: 299872
> Resv style: 1 SE, Label in: -, Label out: 299872
> Time left: -, Since: Thu Jul 30 23:54:23 2009
> Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
> Port number: sender 1 receiver 22134 protocol 0
> Type: Bypass LSP
> Number of data route tunnel through: 1
> Number of RSVP session tunnel through: 0
> PATH rcvfrom: localclient
> Adspec: sent MTU 1500
> Path MTU: received 1500
> PATH sentto: 10.0.2.2 (ge-1/0/9.0) 18 pkts
> RESV rcvfrom: 10.0.2.2 (ge-1/0/9.0) 18 pkts
> Explct route: 10.0.2.2 10.0.3.1
> Record route: <self> 10.0.2.2 10.0.3.1 Total 1 displayed, Up 1, Down 0
>
>
> ka at m320-1# run show route 10.0.0.5
>
> inet.0: 21 destinations, 21 routes (20 active, 0 holddown, 1 hidden)
> + = Active Route, - = Last Active, * = Both
>
> 10.0.0.5/32 *[OSPF/10] 00:07:39, metric 1
> > to 10.0.1.2 via ge-1/1/0.1 ...
>
>
> ka at m320-1# show protocols rsvp
> interface ge-1/1/0.1 {
> link-protection;
> }
> interface ge-1/0/9.0;
>
>
> Kari
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
-------------- next part --------------
(cspf) PRIMARY LSP: M320 -> 1 -> 2 -> ...
(desired) NODE BYPASS: M320 -> 3 -> 4 -> 2
(unwanted) LINK BYPASS: M320 -> 3 -> 1
1.1.1.1 100.0.0.1 100.0.1.1
-----+ 10.0.1.1 +---+ 101.0.0.1 +---+
M320 |----------------| 1 |----------------| 2 |-----....
-----+ 10.0.1.2 +---+ 101.0.0.2 +---+
| | |
| | 101.0.0.100 | 101.0.1.100
| | |
| | 101.0.0.200 | 101.0.1.200
| | |
| 10.0.2.1 +---+ 101.0.0.10 +---+
+-------------------| 3 |----------------| 4 |-----.....
10.0.2.2 +---+ 101.0.0.20 +---+
102.0.0.1 102.0.0.1
--------------------------------------------------------
admin at re-0> show mpls lsp transit detail
Transit LSP: 2 sessions
100.0.5.1
From: 10.0.0.2, LSPstate: Up, ActiveRoute: 1
LSPname: lspPool_1
Suggested label received: -, Suggested label sent: -
Recovery label received: -, Recovery label sent: 16
Resv style: 1 SE, Label in: 301936, Label out: 16
Time left: 150, Since: Thu Jul 30 22:30:58 2009
Tspec: rate 100kbps size 8kbps peak 100kbps m 0 M 0
Port number: sender 1 receiver 1 protocol 0
Node/Link protection desired
Type: Link protected LSP
PATH rcvfrom: 10.0.0.2 (ge-5/0/0.0) 44 pkts
Adspec: received MTU -1 sent MTU -1
PATH sentto: 10.0.1.2 (ge-5/0/1.0) 32 pkts
RESV rcvfrom: 10.0.1.2 (ge-5/0/1.0) 41 pkts
100.0.5.1
From: 10.0.0.2, LSPstate: Up, ActiveRoute: 1
LSPname: lspPool_1
Suggested label received: -, Suggested label sent: -
Recovery label received: -, Recovery label sent: 17
Resv style: 1 SE, Label in: 301952, Label out: 17
Time left: 146, Since: Thu Jul 30 22:30:58 2009
Tspec: rate 100kbps size 8kbps peak 100kbps m 0 M 0
Port number: sender 1 receiver 2 protocol 0
Node/Link protection desired
Type: Link protected LSP
PATH rcvfrom: 10.0.0.2 (ge-5/0/0.0) 43 pkts
Adspec: received MTU -1 sent MTU -1
PATH sentto: 10.0.1.2 (ge-5/0/1.0) 32 pkts
RESV rcvfrom: 10.0.1.2 (ge-5/0/1.0) 42 pkts
Total 2 displayed, Up 2, Down 0
admin at re-0> show mpls lsp bypass detail
Ingress LSP: 1 sessions
100.0.0.1
From: 1.1.1.1, LSPstate: Up, ActiveRoute: 0
LSPname: Bypass->10.0.1.2
Suggested label received: -, Suggested label sent: -
Recovery label received: -, Recovery label sent: 16
Resv style: 1 SE, Label in: -, Label out: 16
Time left: -, Since: Thu Jul 30 22:30:59 2009
Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
Port number: sender 1 receiver 32486 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.2.2 (ge-5/0/2.0) 36 pkts
RESV rcvfrom: 10.0.2.2 (ge-5/0/2.0) 51 pkts
Explct route: 10.0.2.2 101.0.0.100
Record route: <self> ...incomplete
Total 1 displayed, Up 1, Down 0
Egress LSP: 0 sessions
Total 0 displayed, Up 0, Down 0
Transit LSP: 2 sessions
Total 0 displayed, Up 0, Down 0
--------------------------------------------------------
------------------------------------------------------------------------
admin at re-0> show ted database brief
TED database: 0 ISIS nodes 17 INET nodes
ID Type Age(s) LnkIn LnkOut Protocol
10.0.0.1-1 Net 1779 2 2 OSPF(0.0.0.0)
To: 1.1.1.1, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.0.0.2, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
100.0.0.1 Rtr 1778 3 3 OSPF(0.0.0.0)
To: 10.0.1.1-1, Local: 10.0.1.2, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 100.0.1.1, Local: 101.0.0.1, Remote: 101.0.0.2
Local interface index: 0, Remote interface index: 0
To: 102.0.0.1, Local: 101.0.0.100, Remote: 101.0.0.200
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
102.0.0.1 Rtr 1773 3 3 OSPF(0.0.0.0)
To: 100.0.0.1, Local: 101.0.0.200, Remote: 101.0.0.100
Local interface index: 0, Remote interface index: 0
To: 102.0.1.1, Local: 101.0.0.10, Remote: 101.0.0.20
Local interface index: 0, Remote interface index: 0
To: 10.0.2.1-1, Local: 10.0.2.2, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
10.0.1.1-1 Net 1775 2 2 OSPF(0.0.0.0)
To: 1.1.1.1, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 100.0.0.1, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
100.0.1.1 Rtr 1778 3 3 OSPF(0.0.0.0)
To: 100.0.2.1, Local: 101.0.1.1, Remote: 101.0.1.2
Local interface index: 0, Remote interface index: 0
To: 100.0.0.1, Local: 101.0.0.2, Remote: 101.0.0.1
Local interface index: 0, Remote interface index: 0
To: 102.0.1.1, Local: 101.0.1.100, Remote: 101.0.1.200
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
102.0.1.1 Rtr 1773 3 3 OSPF(0.0.0.0)
To: 102.0.2.1, Local: 101.0.1.10, Remote: 101.0.1.20
Local interface index: 0, Remote interface index: 0
To: 100.0.1.1, Local: 101.0.1.200, Remote: 101.0.1.100
Local interface index: 0, Remote interface index: 0
To: 102.0.0.1, Local: 101.0.0.20, Remote: 101.0.0.10
Local interface index: 0, Remote interface index: 0
...................
------------------------------------------------------------------------
-------------------------------------------
admin at re-0# show protocols mpls
interface lo0.0;
interface ge-5/0/0.0;
interface ge-5/0/1.0;
interface ge-5/0/2.0;
admin at re-0# show protocols rsvp
interface lo0.0;
interface ge-5/0/0.0 {
aggregate;
link-protection;
}
interface ge-5/0/1.0 {
aggregate;
link-protection;
}
interface ge-5/0/2.0 {
aggregate;
link-protection;
}
---------------------------------------------
More information about the juniper-nsp
mailing list