271
Task Command
Clear dampening information for BGP IPv4
multicast routes and release suppressed
BGP IPv4 multicast routes.
reset bgp dampening ipv4 multicast
[
network-address
[
mask
|
mask-length
] ]
Clear flap information for BGP IPv4
multicast routes.
reset bgp flap-info ipv4 multicast
[
network-address
[
mask
|
mask-length
] |
as-path-acl
as-path-acl-number
|
peer
ipv4-address
]
Clear dampening information for BGP IPv6
multicast routes and release suppressed
BGP IPv6 multicast routes.
reset bgp dampening ipv6 multicast
[
network-address
prefix-length
]
Clear flap information for BGP IPv6
multicast routes.
reset bgp flap-info ipv6 multicast
[
network-address prefix-length
|
as-path-acl
as-path-acl-number
|
peer
ipv6-address
]
IPv4 BGP configuration examples
Basic BGP configuration example
Network requirements
As shown in
Figure 62
, run EBGP between Router A and Router B, and run IBGP between Router B and
Router C so that Router C can access the network 8.1.1.0/24 connected to Router A.
Figure 62
Network diagram
Configuration considerations
To prevent route flapping caused by port state changes, this example uses loopback interfaces to
establish IBGP connections. Because loopback interfaces are virtual interfaces, you need to use the
peer
connect-interface
command to specify the loopback interface as the source interface for establishing
BGP connections. Enable OSPF in AS 65009 to make sure that Router B can communicate with Router
C through loopback interfaces.
The EBGP peers, Router A and Router B (usually in different ISPs), are located in different ASs. Typically,
their loopback interfaces are not reachable to each other, so directly connected interfaces are used for
establishing BGP sessions. To enable Router C to access the network 8.1.1.0/24 connected directly to
Router A, inject network 8.1.1.0/24 to the BGP routing table of Router A.
Configuration procedure
1.
Configure IP addresses for interfaces. (Details not shown.)
2.
Configure IBGP:
# Configure Router B.