The BGP Attribute NEXT_HOP

SEnuke: Ready for action

When you're learning for the BSCI exam on the method to gaining your CCNP accreditation, you've got to learn the usage of BGP attributes. These attributes permit you to manipulate the road or paths that BGP use to achieve certain destination when multiple paths to that destination exist.

In this free BGP article, we are going to take a peek at-the NEXT_HOP characteristic. To check up additional info, please consider peeping at: indexification. You might be thinking \hey, how complicated can this attribute be?\ It's not very difficult at all, but this being Cisco, there's got to be at least one unusual aspect about it, right?

The NEXT_HOP attribute is straightforward enough - this attribute indicates the next-hop IP that should be taken to achieve a destination. Within the following example, R1 is a link switch and R3 and R2 are spokes. Get new resources about linklicious service by visiting our commanding article. All three routers are in BGP AS 100, with R1 having a connection with both R3 and R2. There is no BGP peering between R3 and R2.

R3 is advertising the network 33.3.0.0 /24 via BGP, and the importance of the next-hop attribute on R1 is the IP on R3 that's utilized in the peer relationship, 172.12.123.3.

The issue with the next-hop credit is available in once the route is advertised to BGP peers. To check up additional information, consider checking out: linklicious case study. If R3 were in a separate 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 route to iBGP peers that was initially learned from an eBGP fellow, the next-hop value is stored. For other ways to look at it, consider taking a look at: linklicious price.

Here, all three routers come in AS 100. What will the next-hop attribute be established to when R1 advertises the route to its iBGP friend R2?

R2#show ip bgp

< no result ">

There will be no attribute for the route on R2, since the route will not look on R2. Automatically, a BGP speaker won't promote a to iBGP neighbors if the route was initially learned from another iBGP friend.

Fortuitously for us, there are numerous ways around this principle. The most common is using route reflectors, and we'll look at RRs in another free BGP tutorial..