How does bgp peering work




















If Device A installs the route, a loop is formed within the AS. The routing devices are not able to detect the loop because the AS path attribute is not modified during these advertisements.

For route reachability, the IBGP peers are fully meshed. A recursive route lookup resolves the loopback peering address to an IP forwarding next hop. No special configuration beyond device initialization is required before you configure this example. The loopback interface lo0 is used to establish connections between IBGP peers. If there is a route to the loopback address, the IBGP peer session stays up. If a physical interface address is used instead and that interface goes up and down, the IBGP peer session also goes up and down.

Thus, if the device has link redundancy, the loopback interface provides fault tolerance in case the physical interface or one of the links goes down. The local-address statement enables you to specify the source information in BGP update messages. When this happens, the peer session is not established because a mismatch exists between the expected source address the egress interface of the peer and the actual source the loopback interface of the peer. To make sure that the expected source address matches the actual source address, specify the loopback interface address in the local-address statement.

A recursive route lookup resolves the loopback peer address to an IP forwarding next hop. In this example, this service is provided by OSPF. Although interior gateway protocol IGP neighbors do not need to be directly connected, they do need to be fully meshed. In the sample network, the devices in AS 17 are fully meshed in the group internal-peers.

The devices have loopback addresses Figure 5 shows a typical network with internal peer sessions. Other useful options for this scenario might be to accept routes learned through OSPF or local routes. From configuration mode, confirm your configuration by entering the show interfaces , show policy-options , show protocols , and show routing-options commands.

The following example requires that you navigate various levels in the configuration hierarchy. From operational mode, enter the show bgp neighbor command. From operational mode, enter the show bgp group command. From operational mode, enter the show bgp summary command. Verify that the export policy configuration is causing the BGP routes to be installed in the routing tables of the peers.

From operational mode, enter the show route protocol bgp command. Figure 6 shows a typical network with internal peer sessions. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it. From the operational mode, enter the show bgp neighbor command. From the operational mode, enter the show bgp group command.

From the operational mode, enter the show bgp summary command. From the operational mode, enter the show route protocol bgp command. In complex networks such as Data Center or Cloud, link-local addresses are widely used due to the high number of links and nodes.

EBGP peers are normally directly connected over a single hop across a single link , with no intervening routers, and therefore require no additional underlying routing information.

There are mechanisms for connecting eBGP peers across multiple hops; these are covered in more detail in Multipath section of Chapter 7. Converting an understanding of BGP into practical, running configurations, isn't always as easy at it seems, so we will often provide sample configurations for networks used as examples.

For the network in Figure , the following configurations, along with some explanation of the various parts of the configuration, are provided. With these configurations in place, router D should learn the Throughout the duration of a BGP session between two BGP speakers it's possible that one of the two peers will send some data in error, or send malformed data, or data the other speaker doesn't understand. The easiest remedy in any of these situations is to simply shut the BGP session down, but a simple session shutdown doesn't provide any diagnostic information to the speaker that transmitted the information that triggered the peering session to shut down, and therefore no corrective action can be taken.

To provide the information needed to take corrective action, BGP includes Notifications, which should be sent by the BGP speaker closing the session. The subcode provides more information about the error.

For instance, where in the Open message the error was. The BGP speaker transmitting the Notification can fill in the data field with information such as the actual part of the Open message causing the error. While the data field is variable in length, there is no length field in the Notification code format. This is because the length of the data field is implied by the length of the complete message.

Message header errors generally indicate problems in the packet format. Since TCP is a reliable transport service, message header errors should be very rare, although it is possible for an implementation of BGP to malform a packet, causing this type of error. Three subcodes are defined in the base BGP specification:.

Notifications transmitted while two BGP peers are opening a session are generally the result of misconfiguration, rather than packet level errors or problems in a BGP implementation. Bad peer autonomous system; the peer has claimed an autonomous system number which isn't valid. Unsupported optional parameter; the peer has indicated it wants to use some optional parameter the receiver doesn't support. Authentication failure; the peer is sending packets which are encrypted or authenticated in some way, but the authentication check is failing.

As BGP peers exchange updates, a number of errors can occur which make it impossible for one speaker to process an update transmitted by the other speaker.

These include:. Malformed attribute list; the list of attributes included in the update packet has some error which makes it unreadable by the receiver. Unrecognized well-known attribute; the sender is including an attribute the receiver must be able to process, but does not recognize. Attribute flags error; the flags included with an attribute are not formed correctly generally flags carry various options which apply to the attribute. The Cease code indicates to the receiver that the peer for some reason has chosen to close the BGP connection.

The Cease Notification is not sent if a fatal error occurs, but rather, provides a graceful mechanism to shutdown a BGP connection. When first initiating a session, a BGP speaker sends an Open message describing various parameters, including a set of capability codes, one for each optional capability it supports.

Capability codes are defined for things such as:. The applicability and value of these and other BGP capabilities and extensions with be discussed in later sections. If a BGP speaker receives a capability code it does not support when enabling a peering with another BGP speaker, it will send a Notification message to its peer, which shuts the session down, with a notification subcode indicating that the peer requested a capability the local BGP speaker doesn't support. The receiving peer can either break off communications altogether on receipt of a notification code indicating an unsupported capability, or it can attempt to peer again without that capability enabled.

There are a lot of elements to the BGP peering process; when a BGP speaker begins a session with a new peer, it must determine if it is peering with an external neighbor or an internal neighbor, it must negotiate capabilities, and do a number of other things. The BGP session state machine in Figure illustrates the process in an attempt to bring all these different actions together in one place.

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time. So the next time you check out this blog , remember that BGP is what helped you get here. Ziv Leyes. What is BGP? So what is BGP? BGP for History Buffs Once upon a time, when the Internet was just a tiny cloud, there were only a few networks connected to each other. Tree-like vs.

In a full mesh topology, nodes have many paths to reach each other. The Emergence of Autonomous System Architecture As the Internet continued to expand, it became increasingly difficult to keep track of all the routes from one network to another. Try Imperva for Free Protect your business for 30 days on Imperva. Start Now. Data Security Application Delivery. Within the BGP advertisement system is the path information that includes the next destination and which destinations are reachable.

An administrator can design and implement policies by programming them into the BGP system. This can be used, for example, to choose between routes that exist within the autonomous system and those that exist outside it.

TCP makes sure data packets get sent and delivered across networks. The conservation of network bandwidth allows an organization to get the most out of its network, and because BGP supports this, it can be used to facilitate efficient network transmissions.

While BGP does not have any security features inherent to it, it supports the existing security tools and protocols that various networks use. This enables administrators to secure their networks and use BGP simultaneously.

BGP allows the right peer to be identified, authenticated, and connected to, making the network run more efficiently. BGP sends information regarding whether or not a peer is reachable. This saves time by eliminating errant connections. Once a connection happens, BGP is able to verify the health of the communication. In this way, BGP facilitates more consistent, reliable connections. With route storage, individual BGPs keep information regarding how to connect with networks within a set of databases.

Databases are also used to store routing information that can be accessed by BGP. BGP delivers update messages to advertise pertinent routing information.

These are stored in a routing table that becomes available after the system has started up.



0コメント

  • 1000 / 1000