BGP4+
In this section:
- BGP4+ overviewThe implementation of IPv6 supports multiprotocol BGP (MBGP) extensions that allow Border Gateway Protocol version 4 plus (BGP4+) to distribute routing information. BGP4+ supports all of the same features and functionality as IPv4 BGP (BGP4).
- BGP global mode Configurations that are not specific to address family configuration are available in the BGP global configuration mode.
- IPv6 unicast address familyThe IPv6 unicast address family configuration level provides access to commands that allow you to configure BGP4+ unicast routes. The commands that you enter at this level apply only to the IPv6 unicast address family.
- BGP4+ neighborsBGP4+ neighbors can be configured using link-local addresses or global addresses.
- BGP4+ Peer Groups
- Importing routes into BGP4+Routes can be explicitly specified for advertisement by BGP.
- Advertising the default BGP4+ routeA BGP device can be configured to advertise the default IPv6 route to all BGP4+ neighbors and to install that route in the local BGP4+ route table.
- Advertising the default BGP4+ route to a specific neighborA BGP device can be configured to advertise the default IPv6 route to a specific neighbor.
- Using the IPv6 Default Route as a Valid Next
Hop for a BGP4+ RouteIn certain cases, such as when a device is acting as an edge device, it can be configured to use the default route as a valid next hop.
- BGP4+ next hop recursionA device can find the IGP route to the next-hop gateway for a BGP4+ route.
- BGP4+ NLRIs and next hop attributesBGP4+ introduces new attributes to handle multiprotocol extensions for BGP.
- BGP4+ route reflection
- BGP4+ route aggregationA device can be configured to aggregate routes in a range of networks into a single IPv6 prefix.
- BGP4+ multipathThe BGP4+ multipath feature can be used to enable load-balancing across different paths.
- Route mapsRoute maps must be applied to IPv6 unicast address prefixes in IPv6 address family configuration mode.
- Redistributing prefixes into BGP4+Various routes can be redistributed into BGP.
- Redistributing routes into BGP4+Various routes can be redistributed into BGP. This task redistributes connected routes into BGP.
- Specifying the weight added to BGP4+ received routesThe weight that the device adds to received routes can be specified. The following task changes the weight from the default for routes that are received from a specified BGP4+ neighbor.
- BGP4+ outbound route filteringThe BGP4+ Outbound Route Filtering Capability (ORF) feature is used to minimize the number of BGP updates sent between BGP peers.
- BGP4+ confederationsA large autonomous system (AS) can be divided into multiple subautonomous systems and grouped into a single BGP4+ confederation.
- BGP4+ extended communityThe BGP4+ extended community feature filters routes based on a regular expression specified when a route has multiple community values in it.
- BGP4+ graceful restartBGP4+ graceful restart (GR) allows for restarts where BGP neighboring devices participate in the restart, helping to ensure that no route and topology changes occur in the network for the duration of the restart.
- Generalized TTL Security Mechanism supportGeneralized TTL Security Mechanism (GTSM) is a lightweight security mechanism that protects external Border Gateway Protocol (eBGP) peering sessions from CPU utilization-based attacks using forged IP packets. GTSM prevents attempts to hijack the eBGP peering session by a host on a network segment that is not part of either BGP network, or by a host on a network segment that is not between the eBGP peers.
- Disabling the BGP AS_PATH Check
FunctionA device can be configured so that the AS_PATH check function for routes learned from a specific location is disabled, and routes that contain the recipient BGP speaker's AS number are not rejected.
- Displaying BGP4+ statistics
- Displaying BGP4+ Neighbor Statistics