Option A L3NNI
Load russo.pl.course.inter-as.init.cfg
#IOS-XE
config replace flash:russo.pl.course.inter-as.init.cfg
#IOS-XR
configure
load bootflash:russo.pl.course.inter-as.init.cfg
commit replace
yConfigure inter-AS option A using the following guidelines:
Globomantics is AS65001 and Wired Brain is AS65002
XR11 must set LP to 50 for the following prefixes received from CSR3:
2001:DB8:3::102/128, 2001:DB8:3::103/128
192.0.2.2, 192.0.2.3
XR11 must prepend the customer’s AS path three times towards CSR3 for prefixes originated from CSR1’s AS65101
VRF L3B and L3C on R8/R10 are currently importing/exporting different RTs. On R3, routes from both VRFs must be imported/exported as if they are in one single VRF.
Use outer-VLAN 3888 inner-VLAN 311 for the XR11-R3 link
Use 10.3.11.0/24 and fc00:10:3:11::/64
Use outer-VLAN 3777 inner-VLAN 23 for the R2-R3 link
Use 10.2.3.0/24 and fc00:10:2:3::/64
All IGP/BGP peerings are already setup (except for the ASBR-ASBR peerings for option A).
Answer
Explanation
Inter-AS option A is the simplest option, in which the ASBRs treat each other as CEs. The simplest design is a basic PE-CE setup with no policies. For example, the config for R2:
By looking at the config above, you cannot tell whether R2 is connecting to a true CE or an ASBR. There is no difference.
There is some slight complexity within the Wired Brain (AS65002) network. The L3B and L3C VRFs use different RTs for import and export. This means that R8 and R10 do not import routes learned from the other PE:
This task requires us to create a VRF on R3 that imports all routes from both VRFs. This is simply done by reversing the RT policy:
Next, we have two ASBR-ASBR links (XR11-R3 and R2-R3). This task asks us to configure policies on XR11 so that this link is only used if the R2-R3 link fails.
First we setup an outbound policy which matches routes originated from 65101 and prepends the customer’s AS three time. Since this is address-familiy independent, this same RPL can be used for both IPv4 and IPv6 outbound routes.
On R3 we can confirm that the routes are prepended from XR11:
To influence AS65001 to prefer the R2-R3 link, XR11 sets local preference low for prefixes received from R3:
We can confirm that LP is set to 50 for these prefixes.
Notice that XR11 hides this alternative path because only the best path is sent to its iBGP peers. For example, if we look at the RR, we only see one path for 192.0.2.2/32. This can prevent fast convergence and load sharing.
Even if XR11 uses a unique RD, this would not solve the issue. In addition, XR11 would have to use a technique such as advertise-best-external.
Moving on, when we trace from R1’s L3A to L3B or L3C, we see that traffic takes the R2-R3 link. Notice that the traceroute has an unlabeled hop in the middle at the L3 NNI. This is a characteristic of inter-AS option A.
Last updated