LSP prefix mapping
Hi,
I was configuring the prefix-mapping for two different LSPs as in chapter two of the JNCIE book.
LSPs are between r7 and r3, called r7-r3 and r7-r3-prime.
R3 sends 130.130/16 routes into the AS via BGP. Idea is to map different prefix lengths to different LSPs.
So far, so good.
When I configure r3, r4 and r5 as RR, the solution as such does not work any more, as the policy matches on BGP neighbor. So r6 and r7 are clients to r5.
So below my take on it, where I was matching on neighbor. Unfortunately it does not work. Which field must I match in the policy to get the routes that originally came from r3?
TIA
I was configuring the prefix-mapping for two different LSPs as in chapter two of the JNCIE book.
LSPs are between r7 and r3, called r7-r3 and r7-r3-prime.
R3 sends 130.130/16 routes into the AS via BGP. Idea is to map different prefix lengths to different LSPs.
So far, so good.
When I configure r3, r4 and r5 as RR, the solution as such does not work any more, as the policy matches on BGP neighbor. So r6 and r7 are clients to r5.
So below my take on it, where I was matching on neighbor. Unfortunately it does not work. Which field must I match in the policy to get the routes that originally came from r3?
TIA
lab@lab-1# show policy-options policy-statement lsp-map
term 10 {
from {
protocol bgp;
next-hop 10.0.3.3;
route-filter 0.0.0.0/0 prefix-length-range /0-/19;
}
then {
install-nexthop lsp r7-r3;
accept;
}
}
term 20 {
from {
protocol bgp;
next-hop 10.0.3.3;
route-filter 0.0.0.0/0 prefix-length-range /20-/32;
}
then {
install-nexthop lsp r7-r3-prime;
accept;
}
}
[edit logical-systems r7]
lab@lab-1# show protocols mpls
label-switched-path r7-r1 {
to 10.0.6.1;
ldp-tunneling;
install 10.0.5.10/32;
no-cspf;
}
label-switched-path r7-r3 {
to 10.0.3.3;
}
label-switched-path r7-r3-prime {
to 10.0.3.3;
}
interface all;
interface fxp0.0 {
disable;
}
[edit logical-systems r7]
lab@lab-1# show routing-options
aggregate {
route 10.0.0.0/16 discard;
}
autonomous-system 65412;
forwarding-table {
export lsp-map;
}
[edit logical-systems r7]
lab@lab-1# run show route logical-system r7 next-hop 10.0.3.3
inet.0: 62 destinations, 67 routes (62 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
3.0.0.0/8 *[BGP/170] 00:09:32, localpref 100, from 10.0.3.5
AS path: 65222 I
> to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3
to 10.0.8.9 via fe-0/0/4.0, label-switched-path r7-r3-prime
10.0.0.0/16 [BGP/170] 00:09:32, localpref 100, from 10.0.3.5
AS path: I
> to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3
to 10.0.8.9 via fe-0/0/4.0, label-switched-path r7-r3-prime
130.130.0.0/24 *[BGP/170] 00:09:32, localpref 100, from 10.0.3.5
AS path: 65222 I
> to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3
to 10.0.8.9 via fe-0/0/4.0, label-switched-path r7-r3-prime
130.130.1.0/24 *[BGP/170] 00:09:32, localpref 100, from 10.0.3.5
AS path: 65222 I
> to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3
to 10.0.8.9 via fe-0/0/4.0, label-switched-path r7-r3-prime
130.130.2.0/24 *[BGP/170] 00:09:32, localpref 100, from 10.0.3.5
AS path: 65222 I
> to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3
to 10.0.8.9 via fe-0/0/4.0, label-switched-path r7-r3-prime
130.130.3.0/24 *[BGP/170] 00:09:32, localpref 100, from 10.0.3.5
AS path: 65222 I
> to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3
to 10.0.8.9 via fe-0/0/4.0, label-switched-path r7-r3-prime
130.130.4.0/24 *[BGP/170] 00:09:32, localpref 100, from 10.0.3.5
AS path: 65222 I
> to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3
to 10.0.8.9 via fe-0/0/4.0, label-switched-path r7-r3-prime
130.130.5.0/24 *[BGP/170] 00:09:32, localpref 100, from 10.0.3.5
AS path: 65222 I
> to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3
to 10.0.8.9 via fe-0/0/4.0, label-switched-path r7-r3-prime
130.130.6.0/24 *[BGP/170] 00:09:32, localpref 100, from 10.0.3.5
AS path: 65222 I
> to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3
to 10.0.8.9 via fe-0/0/4.0, label-switched-path r7-r3-prime
130.130.7.0/24 *[BGP/170] 00:09:32, localpref 100, from 10.0.3.5
AS path: 65222 I
> to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3
to 10.0.8.9 via fe-0/0/4.0, label-switched-path r7-r3-prime
inet.3: 7 destinations, 8 routes (3 active, 0 holddown, 5 hidden)
mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
[edit logical-systems r7]
lab@lab-1# run show route logical-system r7 next-hop 10.0.3.3 3/8
inet.0: 62 destinations, 67 routes (62 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
3.0.0.0/8 *[BGP/170] 00:09:38, localpref 100, from 10.0.3.5
AS path: 65222 I
> to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3
to 10.0.8.9 via fe-0/0/4.0, label-switched-path r7-r3-prime
[edit logical-systems r7]
lab@lab-1# run show route logical-system r7 next-hop 10.0.3.3 3/8 detail
inet.0: 62 destinations, 67 routes (62 active, 0 holddown, 0 hidden)
3.0.0.0/8 (1 entry, 1 announced)
*BGP Preference: 170/-101
Next hop type: Indirect
Next-hop reference count: 28
Source: 10.0.3.5
Next hop type: Router, Next hop index: 262153
Next hop: 10.0.2.18 via fe-0/0/9.0 weight 0x1, selected
Label-switched-path r7-r3
Label operation: Push 299872
Next hop: 10.0.8.9 via fe-0/0/4.0 weight 0x1
Label-switched-path r7-r3-prime
Label operation: Push 100048
Protocol next hop: 10.0.3.3
Indirect next hop: 8d2b140 262147
State: <Active Int Ext>
Local AS: 65412 Peer AS: 65412
Age: 9:41 Metric2: 2
Task: BGP_65412.10.0.3.5+4602
Announcement bits (2): 3-KRT 6-Resolve tree 1
AS path: 65222 I (Originator) Cluster list: 10.0.3.5
AS path: Originator ID: 10.0.3.3
Communities: 65412:100
Accepted
Localpref: 100
Router ID: 10.0.3.5
[edit logical-systems r7]
lab@lab-1#
Comments
-
ccie15672
Member Posts: 92 ■■■□□□□□□□
You are matching on next-hop. The RR should not be changing the next-hop. Unless you have a next-hop-self policy configured....Derick Winkworth
CCIE #15672 (R&S, SP), JNCIE-M #721
Chasing: CCIE Sec, CCSA (Checkpoint) -
hoogen82
Member Posts: 272
Can you post from R7 these following commands
show route 130.130.1.0 detail
show route 3.0.0.0 detail
show configuration routing-options
show route table inet.3
show mpls lsp ingress detailIS-IS Sleeps.
BGP peers are quiet.
Something must be wrong. -
pepper
Member Posts: 4 ■□□□□□□□□□
Can you post from R7 these following commands
show route 130.130.1.0 detail
show route 3.0.0.0 detail
show configuration routing-options
show route table inet.3
show mpls lsp ingress detailshow route before: show route logical-system r7 next-hop 10.0.3.3 inet.0: 52 destinations, 52 routes (52 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 3.0.0.0/8 *[BGP/170] 01:28:47, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.0.0/24 *[BGP/170] 01:28:47, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.1.0/24 *[BGP/170] 01:28:47, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.2.0/24 *[BGP/170] 01:28:47, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.3.0/24 *[BGP/170] 01:28:47, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.4.0/24 *[BGP/170] 01:28:47, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.5.0/24 *[BGP/170] 01:28:47, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.6.0/24 *[BGP/170] 01:28:47, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.7.0/24 *[BGP/170] 01:28:47, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime show route logical-system r7 130.130.0.0 detail inet.0: 52 destinations, 52 routes (52 active, 0 holddown, 0 hidden) 130.130.0.0/24 (1 entry, 1 announced) *BGP Preference: 170/-101 Next hop type: Indirect Next-hop reference count: 27 Source: 10.0.3.5 Next hop type: Router, Next hop index: 262147 Next hop: 10.0.2.18 via fe-0/0/9.0 weight 0x1, selected Label-switched-path r7-r3 Label operation: Push 301328 Next hop: 10.0.8.21 via fe-0/0/1.0 weight 0x1 Label-switched-path r7-r3-prime Label operation: Push 100528 Protocol next hop: 10.0.3.3 Indirect next hop: 8d700a0 262145 State: <Active Int Ext> Local AS: 65412 Peer AS: 65412 Age: 1:33:57 Metric2: 20 Task: BGP_65412.10.0.3.5+179 Announcement bits (2): 0-KRT 5-Resolve tree 4 AS path: 65222 I (Originator) Cluster list: 10.0.3.5 AS path: Originator ID: 10.0.3.3 Accepted Localpref: 100 Router ID: 10.0.3.5 [edit logical-systems r7] lab@JTB_m20# run show route logical-system r7 3/8 detail inet.0: 52 destinations, 52 routes (52 active, 0 holddown, 0 hidden) 3.0.0.0/8 (1 entry, 1 announced) *BGP Preference: 170/-101 Next hop type: Indirect Next-hop reference count: 27 Source: 10.0.3.5 Next hop type: Router, Next hop index: 262147 Next hop: 10.0.2.18 via fe-0/0/9.0 weight 0x1, selected Label-switched-path r7-r3 Label operation: Push 301328 Next hop: 10.0.8.21 via fe-0/0/1.0 weight 0x1 Label-switched-path r7-r3-prime Label operation: Push 100528 Protocol next hop: 10.0.3.3 Indirect next hop: 8d700a0 262145 State: <Active Int Ext> Local AS: 65412 Peer AS: 65412 Age: 1:34:03 Metric2: 20 Task: BGP_65412.10.0.3.5+179 Announcement bits (2): 0-KRT 5-Resolve tree 4 AS path: 65222 I (Originator) Cluster list: 10.0.3.5 AS path: Originator ID: 10.0.3.3 Accepted Localpref: 100 Router ID: 10.0.3.5 show routing-options autonomous-system 65412; forwarding-table { export lsp-map; } show mpls lsp extensive logical-system r7 ingress Ingress LSP: 3 sessions 10.0.3.3 From: 10.0.9.7, State: Up, ActiveRoute: 9, LSPname: r7-r3 ActivePath: (primary) 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: 20) 10.0.2.18 S 10.0.2.5 S Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID): 10.0.2.18 10.0.2.5 5 May 17 16:16:41.818 Selected as active path 4 May 17 16:16:41.817 Record Route: 10.0.2.18 10.0.2.5 3 May 17 16:16:41.814 Up 2 May 17 16:16:41.773 Originate Call 1 May 17 16:16:41.773 CSPF: computation result accepted 10.0.2.18 10.0.2.5 Created: Mon May 17 16:16:41 2010 10.0.3.3 From: 10.0.9.7, State: Up, ActiveRoute: 0, LSPname: r7-r3-prime ActivePath: (primary) 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: 20) 10.0.8.21 S 10.0.2.14 S Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID): 10.0.8.21 10.0.2.14 5 May 17 16:16:41.895 Selected as active path 4 May 17 16:16:41.894 Record Route: 10.0.8.21 10.0.2.14 3 May 17 16:16:41.894 Up 2 May 17 16:16:41.785 Originate Call 1 May 17 16:16:41.785 CSPF: computation result accepted 10.0.8.21 10.0.2.14 Created: Mon May 17 16:16:41 2010 show route logical-system r7 table inet.3 inet.3: 5 destinations, 6 routes (3 active, 0 holddown, 3 hidden) + = Active Route, - = Last Active, * = Both 10.0.3.3/32 *[RSVP/7] 00:09:28, metric 20 > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 10.0.5.10/32 *[RSVP/7] 00:20:34, metric 11 > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r1 10.0.6.1/32 *[RSVP/7] 00:20:34, metric 11 > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r1 after LSP map is applied: show route logical-system r7 next-hop 10.0.3.3 inet.0: 52 destinations, 52 routes (52 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 3.0.0.0/8 *[BGP/170] 01:36:58, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.0.0/24 *[BGP/170] 01:36:58, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.1.0/24 *[BGP/170] 01:36:58, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.2.0/24 *[BGP/170] 01:36:58, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.3.0/24 *[BGP/170] 01:36:58, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.4.0/24 *[BGP/170] 01:36:58, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.5.0/24 *[BGP/170] 01:36:58, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.6.0/24 *[BGP/170] 01:36:58, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime 130.130.7.0/24 *[BGP/170] 01:36:58, localpref 100, from 10.0.3.5 AS path: 65222 I > to 10.0.2.18 via fe-0/0/9.0, label-switched-path r7-r3 to 10.0.8.21 via fe-0/0/1.0, label-switched-path r7-r3-prime -
ccie15672
Member Posts: 92 ■■■□□□□□□□
I'm sorry.. what is the difference you are seeing before and after? I'm not seeing it...Derick Winkworth
CCIE #15672 (R&S, SP), JNCIE-M #721
Chasing: CCIE Sec, CCSA (Checkpoint) -
Aldur
Member Posts: 1,460
I'm sorry.. what is the difference you are seeing before and after? I'm not seeing it...
I think the problem is that there is no difference between the before and after. Which means that the lsp mapping isn't working as the OP is thinking it should.
But I think I see the problem.
I believe that the 'next-hop' that is specified in the from clause of the policy isn't actually talking about 'protocol next-hop' and is referring to either 'source' field or the 'next-hop' field located in the detail output for the 3/8 route. I think it's actually the 'source' field but I don't have something setup to test right now.lab@lab-1# run show route logical-system r7 next-hop 10.0.3.3 3/8 detail inet.0: 62 destinations, 67 routes (62 active, 0 holddown, 0 hidden) 3.0.0.0/8 (1 entry, 1 announced) *BGP Preference: 170/-101 Next hop type: Indirect Next-hop reference count: 28 [B] Source: 10.0.3.5 <------[/B] Next hop type: Router, Next hop index: 262153 Next hop: 10.0.2.18 via fe-0/0/9.0 weight 0x1, selected Label-switched-path r7-r3 Label operation: Push 299872 [B]Next hop: 10.0.8.9[/B] via fe-0/0/4.0 weight 0x1 <------ Label-switched-path r7-r3-prime Label operation: Push 100048 Protocol next hop: 10.0.3.3 Indirect next hop: 8d2b140 262147 State: <Active Int Ext> Local AS: 65412 Peer AS: 65412 Age: 9:41 Metric2: 2 Task: BGP_65412.10.0.3.5+4602 Announcement bits (2): 3-KRT 6-Resolve tree 1 AS path: 65222 I (Originator) Cluster list: 10.0.3.5 AS path: Originator ID: 10.0.3.3 Communities: 65412:100 Accepted Localpref: 100 Router ID: 10.0.3.5
Since the route reflector is involved it is changing the 'source' field to be it's loopback address and thus breaking the lsp mapping that worked before hand.
Try changing the policy to what I have highlighted below.lab@lab-1# show policy-options policy-statement lsp-map term 10 { from { protocol bgp; [B]next-hop 10.0.3.5; <------[/B] route-filter 0.0.0.0/0 prefix-length-range /0-/19; } then { install-nexthop lsp r7-r3; accept; } } term 20 { from { protocol bgp; [B]next-hop 10.0.3.5; <------[/B] route-filter 0.0.0.0/0 prefix-length-range /20-/32; } then { install-nexthop lsp r7-r3-prime; accept; } }
Let us know how it turns out."Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."
-Bender -
hoogen82
Member Posts: 272
But isn't the purpose of the solution to affect routes received from R3's external neighbor...I am not sure what I am mis reading here...I do not seem to see any issues with your configuration... But can you instead of neighbor/next-hop ... you could also do as-path regex to match all routes... For example I believe R3 is connected to T1.. which is in AS 65222...
You could have your policy look like this...
policy-statement lsp-map {
term 1 {
from as-path t1-origin;
route-filter 0.0.0.0/0 prefix-length-range /0-/19;
then {
install-nexthop lsp r7-r3;
accept;
}
}
term 2 {
from as-path t1-origin;
route-filter 0.0.0.0/0 prefix-length-range /20-/32;
then {
install-nexthop lsp r7-r3-prime;
}
}
}
as-path t2-origin ".* 65222 .*";IS-IS Sleeps.
BGP peers are quiet.
Something must be wrong. -
Aldur
Member Posts: 1,460
But isn't the purpose of the solution to affect routes received from R3's external neighbor...I am not sure what I am mis reading here...I do not seem to see any issues with your configuration... But can you instead of neighbor/next-hop ... you could also do as-path regex to match all routes... For example I believe R3 is connected to T1.. which is in AS 65222...
You could have your policy look like this...
policy-statement lsp-map {
term 1 {
from as-path t1-origin;
route-filter 0.0.0.0/0 prefix-length-range /0-/19;
then {
install-nexthop lsp r7-r3;
accept;
}
}
term 2 {
from as-path t1-origin;
route-filter 0.0.0.0/0 prefix-length-range /20-/32;
then {
install-nexthop lsp r7-r3-prime;
}
}
}
as-path t2-origin ".* 65222 .*";
Yea I was actually thinking about this last night as well. It would be best to mark the route with the community or something to do the load balancing on. The AS path matching works well since you won't have to do anything with the routes other then match off their AS. Marking the routes with communities might be helpful when you just want to load balance on just a subset of routes and not everything received from that particular AS."Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."
-Bender -
pepper
Member Posts: 4 ■□□□□□□□□□
I think the problem is that there is no difference between the before and after. Which means that the lsp mapping isn't working as the OP is thinking it should.
Yes, sounds like I was a bit too stressed to be clear
But I think I see the problem.
I believe that the 'next-hop' that is specified in the from clause of the policy isn't actually talking about 'protocol next-hop' and is referring to either 'source' field or the 'next-hop' field located in the detail output for the 3/8 route. I think it's actually the 'source' field but I don't have something setup to test right now.
From the documentation the from next-hop in BGP should exactly match what I wanted to use it for, from the documentation:next-hop address: Next-hop address or addresses specified in the routing information for a particular route. For BGP routes, matches are performed against each protocol next hop.
[code]
I fixed the "rpoblem" by specifying the routes specifically and then mapping to the LSP worked as expected.
Well, so much for elegance.
Thanks for looking at this. -
Aldur
Member Posts: 1,460
Hmm yea, I suppose it does refer to the protocol next-hop. But I've seen this before on older code, 7.x, to where the loopback of the RR needed to be specified to get this to work. What code are you running here? Somewhat sounds like a bug to me then
"Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."
-Bender -
pepper
Member Posts: 4 ■□□□□□□□□□
Hmm yea, I suppose it does refer to the protocol next-hop. But I've seen this before on older code, 7.x, to where the loopback of the RR needed to be specified to get this to work. What code are you running here? Somewhat sounds like a bug to me then
The lab is running 9.4R1.8 (not a good choice, but well...)
