CISCO BGP PDF
IP Routing: BGP Configuration Guide, Cisco IOS Release 15M&T -Cisco BGP Overview. This document contains five Border Gateway Protocol (BGP) case studies. Example: Configuring a BGP Process and Customizing Peers Examples: Example: Resetting BGP Peers Using 4-Byte Autonomous System Numbers
|Language:||English, Spanish, Hindi|
|Genre:||Health & Fitness|
|ePub File Size:||20.40 MB|
|PDF File Size:||14.38 MB|
|Distribution:||Free* [*Regsitration Required]|
EGP (Exterior Gateway Protocol) - BGP = Routing protocol used to exchange .. Cisco routers maintain a separate routing table to hold BGP routes: show ip bgp. BGP is a standardized exterior gateway protocol (EGP), as opposed to RIP,. OSPF, and A Cisco router running BGP can belong to only one AS. The IOS will. Introduction. Prerequisites. Requirements. Components Used. Conventions. BGP Case Studies 1. How Does BGP Work? eBGP and iBGP.
Hares, Ed. Please refer to the current edition of the "Internet Official Protocol Standards" STD 1 for the standardization state and status of this protocol. Distribution of this memo is unlimited. This network reachability information includes information on the list of Autonomous Systems ASes that reachability information traverses.
This information is sufficient for constructing a graph of AS connectivity for this reachability from which routing loops may be pruned, and, at the AS level, some policy decisions may be enforced. These mechanisms include support for advertising a set of destinations as an IP prefix, and eliminating the concept of network "class" within BGP. BGP-4 also introduces mechanisms that allow aggregation of routes, including aggregation of AS paths.
Cisco Systems' Solution for Multicast in BGP/MPLS IP VPNs
This document obsoletes RFC Rekhter, et al. Finite State Machine Decision Process Phase 1: Calculation of Degree of Preference Phase 2: Route Selection Route Resolvability Condition Breaking Ties Phase Phase 3: Route Dissemination Overlapping Routes Update-Send Process Controlling Routing Traffic Overhead Frequency of Route Advertisement Frequency of Route Origination Efficient Organization of Routing Information Information Reduction Aggregating Routing Information Route Selection Criteria Originating BGP routes BGP Timers Comparison with RFC Implementation Recommendations Multiple Networks Per Message Reducing Route Flapping Path Attribute Ordering Control Over Version Negotiation This information is sufficient for constructing a graph of AS connectivity for this reachability, from which routing loops may be pruned and, at the AS level, some policy decisions may be enforced.
These mechanisms include support for advertising a set of destinations as an IP prefix and eliminating the concept of network "class" within BGP. Routing information exchanged via BGP supports only the destination- based forwarding paradigm, which assumes that a router forwards a packet based solely on the destination address carried in the IP header of the packet.
This, in turn, reflects the set of policy decisions that can and cannot be enforced using BGP. BGP can support only those policies conforming to the destination-based forwarding paradigm.
Definition of Commonly Used Terms This section provides definitions for terms that have a specific meaning to the BGP protocol and that are used throughout the text. Autonomous System AS The classic definition of an Autonomous System is a set of routers under a single technical administration, using an interior gateway protocol IGP and common metrics to determine how to route packets within the AS, and using an inter-AS routing protocol to determine how to route packets to other ASes.
Since this classic definition was developed, it has become common for a single AS to Rekhter, et al. The use of the term Autonomous System stresses the fact that, even when multiple IGPs and metrics are used, the administration of an AS appears to other ASes to have a single coherent interior routing plan, and presents a consistent picture of the destinations that are reachable through it.
External peer Peer that is in a different Autonomous System than the local system. Feasible route An advertised route that is available for use by the recipient. Internal peer Peer that is in the same Autonomous System as the local system. IGP Interior Gateway Protocol - a routing protocol used to exchange routing information among routers within a single Autonomous System.
Route A unit of information that pairs a set of destinations with the attributes of a path to those destinations. The set of Rekhter, et al. Unfeasible route A previously advertised feasible route that is no longer available for use. Honig for their contributions to the earlier version BGP-1 of this document. We would like to specially acknowledge numerous contributions by Dennis Ferguson to the earlier version of this document.
We would like to explicitly thank Bob Braden for the review of the earlier version BGP-2 of this document, and for his constructive and valuable comments. Johns, and Paul Tsuchiya, acted with a strong combination of toughness, professionalism, and courtesy.
File Extensions and File Formats
We would like to specially acknowledge Andrew Lange for his help in preparing the final version of this document. Finally, we would like to thank all the members of the IDR Working Group for their ideas and the support they have given to this document.
This information is sufficient for constructing a graph of AS connectivity, from which routing loops may be pruned, and, at the AS level, some policy decisions may be enforced. In the context of this document, we assume that a BGP speaker advertises to its peers only those routes that it uses itself in this context, a BGP speaker is said to "use" a BGP route if it is the most preferred BGP route and is used in forwarding.
All other cases are outside the scope of this document. Note that some policies cannot be supported by the destination-based forwarding paradigm, and thus require techniques such as source routing aka explicit routing to be enforced. Such policies cannot be enforced using BGP either. Standards Track [Page 7] RFC BGP-4 January traffic to a neighboring AS for forwarding to some destination reachable through but beyond that neighboring AS, intending that the traffic take a different route to that taken by the traffic originating in the neighboring AS for that same destination.
On the other hand, BGP can support any policy conforming to the destination-based forwarding paradigm. These mechanisms include support for advertising a set of destinations as an IP prefix and eliminating the concept of a network "class" within BGP.
642-691 PDF Free Samples
The classic definition of an Autonomous System is a set of routers under a single technical administration, using an interior gateway protocol IGP and common metrics to determine how to route packets within the AS, and using an inter-AS routing protocol to determine how to route packets to other ASes. Since this classic definition was developed, it has become common for a single AS to use several IGPs and, sometimes, several sets of metrics within an AS.
The use of the term Autonomous System stresses the fact that, even when multiple IGPs and metrics are used, the administration of an AS appears to other ASes to have a single coherent interior routing plan and presents a consistent picture of the destinations that are reachable through it. This eliminates the need to implement explicit update fragmentation, retransmission, acknowledgement, and sequencing. A TCP connection is formed between two systems.
They exchange messages to open and confirm the connection parameters. The initial data flow is the portion of the BGP routing table that is allowed by the export policy, called the Adj-Ribs-Out see 3.
Incremental updates are sent as the routing tables change. BGP does not require a periodic refresh of the routing table. A peer in a different AS is referred to as an external peer, while a peer in the same AS is referred to as an internal peer. If a particular AS has multiple BGP speakers and is providing transit service for other ASes, then care must be taken to ensure a consistent view of routing within the AS. This document specifies the base behavior of the BGP protocol.
This behavior can be, and is, modified by extension specifications. When the protocol is extended, the new behavior is fully documented in the extension specifications. Routes: Advertisement and Storage For the purpose of this protocol, a route is defined as a unit of information that pairs a set of destinations with the attributes of a path to those destinations.
If a BGP speaker chooses to advertise a previously received route, it MAY add to, or modify, the path attributes of the route before advertising it to a peer. Changing the attribute s of a route is accomplished by advertising a replacement route. The replacement route carries new changed attributes and has the same address prefix as the original route. Their contents represent routes that are available as input to the Decision Process.
These are the routes that will be used by the local BGP speaker. The choice of implementation for example, 3 copies of the information vs 1 copy with pointers is not constrained by the protocol.
Routing information that the BGP speaker uses to forward packets or to construct the forwarding table used for packet forwarding is maintained in the Routing Table. The Routing Table accumulates routes to directly connected networks, static routes, routes learned from the IGP protocols, and routes learned from BGP.
Whether a specific BGP route should be installed in the Routing Table, and whether a BGP route should override a route to the same destination installed by another source, is a local policy decision, and is not specified in this document. In addition to actual packet forwarding, the Routing Table is used for resolution of the next-hop addresses specified in BGP updates see Section 5.
A message is processed only after it is entirely received. The maximum message size is octets. All implementations are required to support this maximum message size.
The smallest message that may be sent consists of a BGP header without a data portion 19 octets. All multi-octet fields are in network byte order. Message Header Format Each message has a fixed-size header.
There may or may not be a data portion following the header, depending on the message type. BGP prefers stability within the network, because a link flap could result in route computation for thousands of routes.
Two blocks of private ASNs are available for any organization to use as long as they are never exchanged publicly on the Internet. IANA requires the following items when requesting a public ASN: Proof of a publicly allocated network range Proof that Internet connectivity is provided through multiple connections Need for a unique route policy from your providers In the event that an organization does not meet those guidelines, it should use the ASN provided by its service provider.
Well-known mandatory attributes must be included with every prefix advertisement, whereas well-known discretionary attributes may or may not be included with the prefix advertisement. Optional attributes do not have to be recognized by all BGP implementations. Optional attributes can be set so that they are transitive and stay with the route advertisement from AS to AS. Loop Prevention BGP is a path vector routing protocol and does not contain a complete topology of the network-like link state routing protocols.
BGP behaves similar to distance vector protocols to ensure a path is loop free. An address-family correlates to a specific network protocol, such as IPv4, IPv6, and the like, and additional granularity through a subsequent address-family identifier SAFI , such as unicast and multicast. These attributes are carried inside BGP update messages and are used to carry network reachability information for different address families.For example, kindness, Dumps such as guilty Su Zhe intended to say that his hands on the shoulders of the Ni day d.
It defines whether the Attribute Length is one octet if set to 0 or two octets if set to 1.
Autonomous System AS The classic definition of an Autonomous System is a set of routers under a single technical administration, using an interior gateway protocol IGP and common metrics to determine how to route packets within the AS, and using an inter-AS routing protocol to determine how to route packets to other ASes. Routes: Advertisement and Storage For the purpose of this protocol, a route is defined as a unit of information that pairs a set of destinations with the attributes of a path to those destinations.
Update-Send Process With BGP we can see all the different networks, to which autonomous system they belong and which autonomous systems we have to cross to get there. Am I doing something at all possible? In the upcoming articles I will be writing about BGP attributes, this will show you how BGP will choose a certain path and how we can influence routing decisions.