Scribd
Upload
124 views2 pages

Configure BGP

This document discusses techniques for advertising EBGP routes to IBGP peers, including using the neighbor next-hop-self command to override the default behavior and force the router to advertise itself as the next hop. It also explains how route reflectors allow IBGP peers to receive routes without requiring a full mesh by acting as a central point that passes updates between clients.

Uploaded by

Đỗ Thái
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
124 views2 pages

Configure BGP

This document discusses techniques for advertising EBGP routes to IBGP peers, including using the neighbor next-hop-self command to override the default behavior and force the router to advertise itself as the next hop. It also explains how route reflectors allow IBGP peers to receive routes without requiring a full mesh by acting as a central point that passes updates between clients.

Uploaded by

Đỗ Thái
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Advertising EBGP Routes to IBGP Peers

When an EBGP router receives an update from an EBGP neighbor and forwards the update to its IBGP peers, the source IP address will still be the EBGP routers. IBGP neighbors will have to be configured to reach that external IP address. Another solution is to override a routers default behavior and force it to advertise itself as the next-hop address for and force it to advertise itself as the next-hop address for routes sent to a neighbor. To do so, use the neighbor next-hop-self router configuration command Next Hop Self Example

BGP Without Peer Group Example

BGP With Peer Group Example

BGP Route Reflectors By default, a router that receives an EBGP route will advertise it to its IBGP peers. However, if it receives it through IBGP, it will not advertise it to its IBGP peers. This is a loop prevention mechanism. However, because of this behavior, the only way for all IBGP routers to receive a route once it is originated into the AS is to have a full mesh of IBGP peers. This can get messy with a large number of peers. To get around this limitation of IBGP, we can use a route reflector. A route reflector allows a topology to get around the IBGP limitation of having to have a full mesh. To do this, a route reflector specifies its neighbors as route reflector clients. When a route reflector receives an update from a route reflector client, it can pass it on to its other clients. This greatly simplifies configuration because only the route reflector needs to know all the other peers. The clients dont even know that they are clients. To them, it is just a normal IBGP peering relationship. You can even set up multiple route reflectors in a more advanced configuration for redundancy

You might also like