Hello Experts,
I am trying to set up basic Inter-AS MVPN using P2MP-TE tunnels in my VIRL environment, however I am struggling to signal even the basic P2P tunnel between my MVPN PE's located in different AS's.
I have 2 PE's in my setup (10.0.0.1 and 10.0.0.4) which are XRv boxes and ASBR (10.0.0.11) is XRv as well. As far as I understood so far from the research XR doesn't support MPLS-TE passive interfaces as XE does, hence in order to establish P2P TE tunnel I need to use 'verbatim' option on the head-end to avoid checking MPLS TE topology database and rely only on regular RIB while signaling the tunnel. However, with current configuration my TE tunnel persist to be down:
!!!Configuration on a Head-end:
interface tunnel-te14
description PE1-TO-PE4
ipv4 unnumbered Loopback0
destination 10.0.0.4
path-option 10 explicit name PE1-PE4 verbatim
!
RP/0/0/CPU0:PE-1#show run explicit-path
Sun Feb 12 19:31:17.859 UTC
explicit-path name PE1-PE4
index 1 next-address strict ipv4 unicast 10.1.10.10 //interface of the core LSR
index 2 next-address strict ipv4 unicast 10.10.11.11 //core-facing link of ASBR
index 3 next-address loose ipv4 unicast 194.11.44.44 //inter-as link between ASBR's
index 4 next-address loose ipv4 unicast 10.0.0.4 //address of the tail-end
!
Name: tunnel-te14 Destination: 10.0.0.4 Ifhandle:0xf0
Signalled-Name: PE-1_t14
Status:
Admin: up Oper: down Path: valid Signalling: RSVP signaling proceeding
path option 10, (verbatim) type explicit PE1-PE4
Last PCALC Error: Sun Feb 12 17:28:15 2017
Info: Path-option is skipped because it is held down
Last Signalled Error : Sun Feb 12 18:24:29 2017
Info: [114] PathErr(24,5)-(routing, no route to dest) at 10.10.11.11
G-PID: 0x0800 (derived from egress interface properties)
Bandwidth Requested: 0 kbps CT0
Creation Time: Sun Feb 12 17:28:14 2017 (02:11:22 ago)
Config Parameters:
Bandwidth: 0 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Metric Type: TE (global)
Path Selection:
Tiebreaker: Min-fill (default)
Hop-limit: disabled
Cost-limit: disabled
Path-invalidation timeout: 10000 msec (default), Action: Tear (default)
AutoRoute: disabled LockDown: disabled Policy class: not set
Forward class: 0 (default)
Forwarding-Adjacency: disabled
Autoroute Destinations: 0
Loadshare: 0 equal loadshares
Auto-bw: disabled
Fast Reroute: Disabled, Protection Desired: None
Path Protection: Not Enabled
BFD Fast Detection: Disabled
Reoptimization after affinity failure: Enabled
Soft Preemption: Disabled
History:
Current LSP:
Setup Time: 92 seconds
Prior LSP:
ID: 134 Path Option: 10
Removal Trigger: setup timed out
Path info (No IGP):
Hop0: 10.1.10.10
Hop1: 10.10.11.11
Hop2: 194.11.44.44
Hop3: 10.0.0.4
Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 0) tails
Displayed 0 up, 1 down, 0 recovering, 0 recovered heads
After some basic troubleshooting/debugs some lookup problem revealed on ASBR-1:
RP/0/0/CPU0:ASBR-1#RP/0/0/CPU0:Feb 12 19:11:33.192 : te_control[1050]: ERR-LM[1]: te_optical_link_get_link_by_lcl_te_link_id:1164: OLM-API: Unable to look up TE link record: link LCL TE link ID: 194.11.44.44, Error: 'olm_api' detected the 'fatal' condition 'client not registered'
RP/0/0/CPU0:Feb 12 19:11:33.192 : te_control[1050]: DBG-PATH-LOOKUP[1]: te_s2l_compute_outgoing_ero:1806 (T:14,L:129,P:2147483647,E:10.0.0.1,SI:0,SO:0.0.0.0,S:10.0.0.1,D:10.0.0.4,CT:7,V:1610612736): Could not extract a TE valid loose hop to expand
RP/0/0/CPU0:Feb 12 19:11:33.192 : te_control[1050]: DBG-PATH-LOOKUP[1]: te_s2l_expand_ero_h:1303 (T:14,L:129,P:2147483647,E:10.0.0.1,SI:0,SO:0.0.0.0,S:10.0.0.1,D:10.0.0.4,CT:7,V:1610612736): Failed to expand path to 0.0.0.0, attempting IP RIB lookup
RP/0/0/CPU0:Feb 12 19:11:33.192 : te_control[1050]: ERR-DB-S2L[1]: te_s2l_set_local_hop:5886 (T:14,L:129,P:2147483647,E:10.0.0.1,SI:0,SO:0.0.0.0,S:10.0.0.1,D:10.0.0.4,CT:7,V:1610612736): Attempt to change local hop from 10.10.11.11 to 194.11.44.11 prevented
From the output above I cannot really get why ASBR-1 complains about the lookup problem for directly connected IP address of inter-as link (194.11.44.44):
RP/0/0/CPU0:ASBR-1#sh route 194.11.44.44
Sun Feb 12 19:46:07.869 UTC
Routing entry for 194.11.44.44/32
Known via "static", distance 1, metric 0 (connected)
Installed Feb 11 19:55:36.029 for 23:50:31
Routing Descriptor Blocks
directly connected, via GigabitEthernet0/0/0/3
Route metric is 0, Wt is 1
No advertising protos.
Per my understanding if 'verbatim' option is used the ASBR should completely omit any TE topology checks and send PATH message further on inter-as link(based on RIB) towards the neighbor ASBR where it expands the ERO with loosely defined 10.0.0.4 PE4 address and forwards it respectively.
Am I missing something here or my understanding of this feature is wrong? Or are there any other suggestions how to implement Inter-AS P2MP-TE with XR-based ASBR?
Thanks,
Taras
