Differences between current version and previous revision of BGP.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 9 | Last edited on Monday, April 12, 2010 6:31:36 pm | by JohnMcPherson | |
| Older page: | version 8 | Last edited on Sunday, April 11, 2010 12:19:07 am | by PetTom | Revert |
@@ -16,9 +16,9 @@
|External BGP (eBGP)|eBGP sends routing information between different autonomous system.
|Interior Gateway Protocol (IGP)|This is a routing protocol that runs within an autonomous system. In the past ''gateway'' was used to define a router.
|Internal BGP (iBGP)|This is when BGP is used within an autonomous system. The routers are not required to be physical neighbors and often sit on edges of the autonomous system. iBGP is used between eBGP speakers in the same autonomous system.
|Originator-ID|This is a BGP attribute. It is an optional nontransitive attribute that is created by the route reflector. The attribute contains the router ID of the router that originated the route in the update. The purpose of theis attribute is to prevent a routing loop. If the originating router recieves its own update, it ignores it.
-|policy-based routing|This allows the administrator to program the routing protocol by defining how the traffic is routed. This is a form of static routing enforced by access-lists called ''route-maps''. Policy-based routing (PBR) is protocol independent and uses [web hosting|http://www.webhostingart.com]
route-maps by creating a separate process to force routing decisions in a sophisticated way by matching and changing attributes and other criteria.
+|policy-based routing|This allows the administrator to program the routing protocol by defining how the traffic is routed. This is a form of static routing enforced by access-lists called ''route-maps''. Policy-based routing (PBR) is protocol independent and uses route-maps by creating a separate process to force routing decisions in a sophisticated way by matching and changing attributes and other criteria.
|prefix-list|The prefix-list is used as an alternative to distribute-lists to control how BGP learns or advertises updates. Prefix-lists are faster, more fexible, and less processor intensive than distribute-lists.
|Route reflector|This is the router that is configured to forward routes from other identified iBGP clients. This removes the necessity for a fully meshed iBGP network, preserving network resources. A fully meshed network has a great deal of overhead and does not scale.
|Route reflector client|A client is a router that has a TCP session with its iBGP peer that is acting as a route reflector. It forwards routes to the route reflector, which propagates these on to other routers. The client does not have peer connections with other clients.
|Route reflector cluster|A cluster is a group consisting of a route reflector and clients. There can be more than one route reflector in a cluster.
