257
Task Command
Clear dampened BGP IPv6 unicast
routing information and release
suppressed routes.
reset bgp dampening ipv6
[
unicast
] [
vpn-instance
vpn-instance-name ] [ network-address prefix-length ]
Clear BGP IPv6 unicast route flap
information.
reset bgp flap-info ipv6
[
unicast
] [
vpn-instance
vpn-instance-name ] [ 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 63, all switches run BGP. Run EBGP between Switch A and Switch B, and run
IBGP between Switch B and Switch C to allow Switch C to access network 8.1.1.0/24 connected to
Switch A.
Figure 63 Network diagram
Requirements analysis
To prevent route flapping caused by port state changes, this example uses loopback interfaces to
establish IBGP connections. Because loopback interfaces are virtual interfaces, 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 Switch B can
communicate with Switch C through loopback interfaces.
The EBGP peers, Switch A and Switch B (usually belong to different carriers), are located in different
ASs. Typically, their loopback interfaces are not reachable to each other, so directly connected
interfaces are used for establishing EBGP sessions. To enable Switch C to access the network
8.1.1.0/24 connected directly to Switch A, inject network 8.1.1.0/24 to the BGP routing table of
Switch A.
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure IBGP:
# Configure Switch B.
<SwitchB> system-view
[SwitchB] bgp 65009
[SwitchB-bgp] router-id 2.2.2.2
[SwitchB-bgp] peer 3.3.3.3 as-number 65009
[SwitchB-bgp] peer 3.3.3.3 connect-interface loopback 0
[SwitchB-bgp] address-family ipv4 unicast
[SwitchB-bgp-ipv4] peer 3.3.3.3 enable
To Next Page
Loading...
Need help?
General