12/4/2017 Tidbit: IOS-XR BGP Allocate Label + Some Inter-AS VPNv4 | Come Route With Me!

Come Route With Me!

Let's route, let's route away

Home About

Search

Tidbit: IOS-XR BGP

Recent Posts

Allocate Label + Some NFD16 Gigamon and Splunk

(with a Dash of Phantom)
Guest Post! WTF Are all those

Inter-AS VPNv4 Checkboxes? (ACI L3 Outs)

Part 2 of ???
ACI Power Deployment Tool
Posted on April 3, 2014 by carlniger
Update!
State of the Union of ACI
I ran into a problem while doing an INE mock lab this Have we reached peak ACI?
morning. it basically kicked my ass, so I figured Id post WTF Are all those
Checkboxes? (ACI L3 Outs)
about it!
Part 1 of ???

The overall scenario is that there are two BGP domains, AS

1000 and AS 2000. Within each AS, there is some standard Tags
IGP routing, and IPv4 BGP including eBGP between the
two domains. There is also some route reflection and some 1000v ACI ADM

other fun stuff, but thats mostly irrelevant for the purposes of Automation BGP
this post. Below is the INE topology drawing.
CCIE SP Design
DMVPN Gigamon Illumio IOS-

XR Lab Meraki Microseg

MPLS Multicast

Musings
Nexus OSX PowerCLI

https://comeroutewithme.com/2014/04/03/tidbit-ios-xr-bgp-allocate-label-some-inter-as-vpnv4/ 1/5
12/4/2017 Tidbit: IOS-XR BGP Allocate Label + Some Inter-AS VPNv4 | Come Route With Me!

Python SDN Security

Segment Routing Splunk

VMware VxLAN

Categories

Hardware
Musings
Shenanigans
Soapbox
Tidbit

Archives

September 2017
July 2017
February 2017
September 2016
After the tasks that setup the basics, the lab rolls into some August 2016
inter-AS VPN. Essentially, the routers in AS 1000 and 2000 July 2016
June 2016
also have loopbacks that are in the same VRF that AS 3000
May 2016
lives in. The initial VPNv4 task basically is asking to
April 2016
configure the domains so that loopbacks in this VRF are March 2016
reachable from both of the domains. February 2016
January 2016
December 2015
So the first thing to consider is that BGP labels will need to
September 2015
be sent between the domains. Thats pretty simple, just send- June 2015
label in IOS or labeled-unicast in IOS-XR. In addition to that, May 2015
April 2015
IOS will require the mpls bgp forwarding command on the
February 2015
interfaces between the domains in order to send the labels. January 2015
For IOS-XR, since the neighbor is on a physical interface, November 2014
October 2014
and its not a /32 (obviously), a static host route to the
August 2014
neighbor pointing out the connected interface is required. July 2014
This is because IOS-XR will not install any labels into the June 2014
forwarding table that have a next hop of something other May 2014
April 2014
than a /32.
March 2014
February 2014
After this, we need to ensure that each domain has January 2014
reachability to the PE routers loopbacks. This is to ensure December 2013
November 2013
that we have a label switched path the whole way through to

https://comeroutewithme.com/2014/04/03/tidbit-ios-xr-bgp-allocate-label-some-inter-as-vpnv4/ 2/5
12/4/2017 Tidbit: IOS-XR BGP Allocate Label + Some Inter-AS VPNv4 | Come Route With Me!

the end. We also need to make sure that however we learn

about the PE (which is basically every router since they all The Twitters

have a loopback in the customer VRF) loopbacks, and that

we get some labels for those. There is an important piece
Tweets by @carl_niger
here that basically says that however we learn about that Carl Niger
prefix (/32 for the PE), we must also get a label from the @carl_niger
Replying to @carl_niger
same mechanism. IF we were to learn about those /32s via
nvm.. apparently wildcards on
BGP, we would need a BGP label. If we learn the PE the shared folder permissions
loopbacks via IGP, we need to have a label for that via doesn't work in QNAP :/

IGP/LDP. Nov 29, 2017

Carl Niger
This leads us to the point of the post! In the course of the lab,
@carl_niger
I was advertising the loopback of each of the PE devices into Any lovely twitter people have
BGP on each router individually i.e. on R5 I advertised QNAP NFS mounted
successfully in vCenter? Mine
10.0.0.5/32 (loopback0) into BGP locally, and advertised R2s mounts but shows up as
loopback locally, etc. This totally worked R5 and XR1 16MB and no files on it

both had these prefixes in BGP and while things were Nov 29, 2017

configured for normal IPv4 unicast (not labeled) they were

Embed View on Twitter
advertised across to AS 2000.

Things got a little dicey for me though when I moved the

Recent Comments
eBGP to labeled unicast. R5 was sending prefixes and labels
configrouter on Spanning-tree
across to AS 2000, but when shutting down that peering
is hard! (for Nexus 93128s)
session to test that the inter-AS VPNv4 setup was working qamar on ACI Network vs
across XR1/R3 as well, I was met with crushing defeat!! Application
Centric Deployments
FirstLeila on Nexus 9000
Thankfully somebody on the IEOC forums (INEs forum) had VXLAN EVPN, vPC, and
this same problem, and Mr. Brian McGahan was there to VXLAN Routing
NFD16 Gigamon and Splunk
save the day heres what he said:
(with a Dash of Phantom) -
Tech Field Day on NFD16

Only the originator of the BGP route can allocate the

label. This means that whoever you have the
Gigamon and Splunk (with a
Dash of Phantom)
Mads Adrian on Python + OSX
network statement or the redistribute statement on OpenSSL Issue

you need to do the allocation there. In your case if

you dont originate the network on XR1 youd have
to go to R5 and then send-label to XR1, and on XR1 Meta

send label back to R5. Thats why in most designs Register

Log in
you just have your edge routers originate the BGP
Entries RSS
networks on behalf of the IGP network, because then Comments RSS
https://comeroutewithme.com/2014/04/03/tidbit-ios-xr-bgp-allocate-label-some-inter-as-vpnv4/ 3/5
12/4/2017 Tidbit: IOS-XR BGP Allocate Label + Some Inter-AS VPNv4 | Come Route With Me!

you have a single point of control for them. You can WordPress.com

do it either way but its good to know that the

problem exists in the first place.

So basically IOS-XR, which was configured for allocate-label

all in order to send BGP labels across to AS 2000, was NOT
actually sending any labels!! This was due to the way I was
getting the loopback prefixes piped into BGP. Killing the
advertisements on the other routers, and then advertising
them into BGP on XR1 instead allowed XR1 to send the
labels across.

So lesson learned! Im pretty glad that I messed up and was

able to come across this because I could totally see Cisco
doing something like this on the lab guess Ill find out in a
few weeks when I sit my first attempt!!

Advertisements

Share this:

https://comeroutewithme.com/2014/04/03/tidbit-ios-xr-bgp-allocate-label-some-inter-as-vpnv4/ 4/5
12/4/2017 Tidbit: IOS-XR BGP Allocate Label + Some Inter-AS VPNv4 | Come Route With Me!

Twitter Facebook Google

Like
Be the first to like this.

Related

Nexus 9000 VXLAN My CCIE SP Lab DMVPN/MPLS/PfR

- EVPN, vPC, and Experience Part 2: Finally...
VXLAN Routing In "Shenanigans" Some Routing!
In "Shenanigans" In "Shenanigans"

This entry was posted in Shenanigans and tagged CCIE SP, IOS-XR, Lab,
MPLS. Bookmark the permalink.

IOS-XR Route-Policy My CCIE SP Lab Experience

Leave a Reply

Enter your comment here...

Blog at WordPress.com.

https://comeroutewithme.com/2014/04/03/tidbit-ios-xr-bgp-allocate-label-some-inter-as-vpnv4/ 5/5