Saturday, October 20, 2018

Cisco CCNP / BSCI Tutorial: The BGP Attribute NEXT_HOP

When you are studying for the BSCI examination on the way to earning your CCNP accreditation, you've surely got to learn the usage of BGP attributes. These capabilities permit you to manipulate the road or paths that BGP uses to attain a given destination when multiple paths to that destination occur. Get supplementary info on this related website - Browse this web site: senukex xindexer.

Within this free BGP tutorial, we are planning to take a look at-the NEXT_HOP attribute. You may be considering "hey, how difficult can this capability be?" It's not to difficult at all, but this being Cisco, there's got to be at least one unusual detail about it, right?

The NEXT_HOP attribute is simple enough - this attribute indicates the next-hop IP that needs to be taken to reach a destination. Within the following instance, R1 is a link router and R3 and R2 are spokes. All three routers come in BGP AS 100, with R1 having a relationship with both R3 and R2. Learn supplementary resources on backlinks indexer by visiting our great site. There is no BGP peering between R2 and R3.

R3 is advertising the community 33.3.0.0 /24 via BGP, and the value of the attribute on R1 is the IP on R3 that is utilized in the peer relationship, 172.12.123.3.

The problem using the attribute will come in once the route is advertised to BGP peers. Better Than Linklicious contains additional info about when to acknowledge it. If R3 were in another AS from R1 and R2, the route would be then advertised by R1 to R2 using the attribute set to 172.12.123.3. When a BGP speaker advertises a path to iBGP friends that was originally learned from an eBGP peer, the next-hop value is stored.

Here, all three routers are in AS 100. What will the next-hop feature be set to when R1 advertises the path to its iBGP neighbor R2?

R2#show ip address bgp

< no result >

There will be no credit for the route on R2, because the route won't look on R2. Automagically, a BGP speaker will not promote a to iBGP neighbors if the route was learned from another iBGP neighbor.

Luckily for us, there are lots of ways around this concept. My boss discovered linklicious service by browsing Yahoo. The most common is using route reflectors, and we'll look at RRs in a future free BGP training..