I solved the problem by removing the no-cspf statement from
label-switched-path configuration:
mumulox@mx5t> show route table inet.3 logical-system PE1 extensive
inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
192.168.1.2/32 (1 entry, 1 announced)
State: <FlashAll CalcForwarding>
*RSVP Preference: 7/1
Next hop type: Router, Next hop index: 1299
Address: 0x2b5a578
Next-hop reference count: 13
Next hop: 172.22.211.2 via ge-1/1/7.104
weight0x8001,selected
Label-switched-path Bypass->172.22.210.2->172.22.201.2
Label operation: Push 301744, Push 301584(top)
Label TTL action: prop-ttl, prop-ttl(top)
State: <Active ForwardingOnly Int>
Local AS: 65512
Age: 3:36:49 Metric: 4
Task: RSVP
Announcement bits (1): 1-Resolve tree 1
mumulox@mx5t> show rsvp session logical-system PE1 bypass extensive
Ingress RSVP: 6 sessions
192.168.5.2
From: 192.168.1.1, LSPstate: BackupActive, ActiveRoute: 0
LSPname: Bypass->172.22.210.2->172.22.201.2
LSPtype: Static Configured
Suggested label received: -, Suggested label sent: -
Recovery label received: -, Recovery label sent: 301584
Resv style: 1 SE, Label in: -, Label out: 301584
Time left: -, Since: Fri Aug 10 16:06:15 2012
Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500
Port number: sender 1 receiver 52704 protocol 0
Type: Bypass LSP
Number of data route tunnel through: 2
Number of RSVP session tunnel through: 1
PATH rcvfrom: localclient
Adspec: sent MTU 1500
Path MTU: received 1500
PATH sentto: 172.22.211.2 (ge-1/1/7.104) 331 pkts
RESV rcvfrom: 172.22.211.2 (ge-1/1/7.104) 331 pkts
Explct route: 172.22.211.2 172.22.203.2 172.22.205.1
Record route: <self> 172.22.211.2 172.22.203.2 172.22.205.1
On 08/10/2012 06:28 PM, Wayne Tucker wrote:
I've never tried to use node-protection in conjunction with a strict
path - but I suspect the two features are incompatible since the
protection path would disregard the strict path.
Try changing the path from strict to loose. That allows some
flexibility (though I believe every node in the path must be used, so
it will fail if the node goes down).
If you don't need to use that path, remove the primary statement on
the lsp configuration.
If you do need to use the strict path, configure an alternate strict
path and add it as a secondary under the lsp. If you don't want it to
fail back automatically then list both as secondary paths.
:w
On Fri, Aug 10, 2012 at 2:02 AM, Mihai Gabriel<mihaigabr...@gmail.com> wrote:
This is the topology:
http://img52.imageshack.us/img52/5512/avpn.png
Sorry
On Fri, Aug 10, 2012 at 11:57 AM, Mihai Gabriel<mihaigabr...@gmail.com>wrote:
Hello,
I am trying to test the node-protection feature in a lab using an MX5
router with logical-systems and I can't find the reason why is not
working.The topology I use is here:
http://imageshack.us/photo/my-images/849/avpn.png/
All routers are configured for mls,rsvp,ospf,link-protection, but when I
disable the interface between P1 and PE1, the LSP between PE1 and PE2 goes
down and stay that way:
Before disabling the interface:
mumulox@mx5t> show mpls lsp logical-system PE1 extensive
Ingress LSP: 1 sessions
192.168.1.2
From: 192.168.1.1, State: Up, ActiveRoute: 0, LSPname: pe1-to-pe2
ActivePath: strict-path (primary)
Node/Link protection desired
LSPtype: Static Configured
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
Revert timer: 1
*Primary strict-path State: Up
Priorities: 7 0
OptimizeTimer: 1
SmartOptimizeTimer: 2
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node
10=SoftPreempt 20=Node-ID):
192.168.5.1(flag=0x29) 172.22.210.2(flag=9 Label=301600)
192.168.5.2(flag=0x29) 172.22.201.2(flag=9 Label=301472)
192.168.5.3(flag=0x21) 172.22.206.2(flag=1 Label=301200)
192.168.1.2(flag=0x20) 172.22.212.1(Label=3)
mumulox@mx5t> show mpls path strict-path logical-system PE1
Path name Address strict/loose if-id
strict-path 172.22.210.2 strict<empty>
mumulox@mx5t> show rsvp session logical-system PE1
Ingress RSVP: 2 sessions
To From State Rt Style Labelin Labelout LSPname
192.168.1.2 192.168.1.1 Up 0 1 SE - 301600
pe1-to-pe2
192.168.5.2 192.168.1.1 Up 0 1 SE - 301296
Bypass->172.22.210.2->172.22.201.2
Total 2 displayed, Up 2, Down 0
mumulox@mx5t> show route table inet.3 logical-system PE1 192.168.1.2
extensive
inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
192.168.1.2/32 (1 entry, 1 announced)
State:<FlashAll>
*RSVP Preference: 7/1
Next hop type: Router, Next hop index: 1048577
Address: 0x2c74010
Next-hop reference count: 7
Next hop: 172.22.210.2 via ge-1/1/7.100 weight 0x1,
selected
Label-switched-path pe1-to-pe2
Label operation: Push 301600
Label TTL action: prop-ttl
Next hop: 172.22.211.2 via ge-1/1/7.104 weight 0x8001
Label-switched-path Bypass->172.22.210.2->172.22.201.2
Label operation: Push 301472, Push 301296(top)
Label TTL action: prop-ttl, prop-ttl(top)
State:<Active Int>
Local AS: 65512
Age: 4:33 Metric: 4
Task: RSVP
Announcement bits (1): 1-Resolve tree 1
AS path: I
After disabling the interface:
mumulox@mx5t> show mpls lsp extensive logical-system PE1
Ingress LSP: 1 sessions
192.168.1.2
From: 192.168.1.1, State: Dn, ActiveRoute: 0, LSPname: pe1-to-pe2
ActivePath: (none)
Node/Link protection desired
LSPtype: Static Configured
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
Revert timer: 1
Primary strict-path State: Dn
Priorities: 7 0
OptimizeTimer: 1
SmartOptimizeTimer: 2
199 Aug 10 12:04:44.607 Deselected as active
198 Aug 10 12:04:44.607 172.22.205.1: Non-RSVP capable router detected
197 Aug 10 12:04:44.607 Link-protection Down
196 Aug 10 12:04:44.606 Session preempted
195 Aug 10 12:04:44.504 172.22.210.1: Tunnel local repaired
194 Aug 10 12:04:44.504 172.22.210.1: Down
"198 Aug 10 12:04:44.607 172.22.205.1: Non-RSVP capable router detected"
seems to be very clear,but it is not, because all routers are rsvp enabled
mumulox@mx5t> show rsvp neighbor logical-system P2
RSVP neighbor: 3 learned
Address Idle Up/Dn LastChange HelloInt HelloTx/Rx MsgRcvd
172.22.201.1 0 13/12 23:49 1 84288/84248 2908
172.22.206.2 0 1/0 2d 20:02:20 1 92707/92707 4944
172.22.205.2 0 1/0 2d 18:30:33 1 92114/92114 6789
Any advice?
Thanks
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
