Configuring Bfd For Ipv6 Bgp - HP MSR2000 series Configuration Manual

Routing policy configured:
No routing policy is configured
Received: Total 0 messages, Update messages 0
Sent: Total 0 messages, Update messages 0
Maximum allowed prefix number: 4294967295
Threshold: 75%
Minimum time between advertisement runs is 30 seconds
Optional capabilities:
Route refresh capability has been enabled
ORF advertise capability based on prefix (type 64):
Local: both
Negotiated: send
Peer Preferred Value: 0
IPsec policy name: policy002, SPI :54321
Routing policy configured:
No routing policy is configured
The output shows that both IBGP and EBGP neighbor relationships have been established and all
protocol packets are protected by IPsec.

Configuring BFD for IPv6 BGP

Network requirements
As shown in
Configure OSPFv3 as the IGP in AS 200.
•
Establish two IBGP connections between Switch A and Switch C. When both links are working,
•
Switch C adopts the link Switch A<—>Switch B<—>Switch C to exchange packets with network
1200::0/64. Configure BFD over the link. Then if the link fails, BFD can quickly detect the failure
and notify it to IPv6 BGP. Then the link Switch A<—>Switch D<—>Switch C takes effect
immediately.
BGP Peer is 3::2,
Type: EBGP link
BGP version 4, remote router ID 3.3.3.3
BGP current state: Established, Up for 00h01m51s
BGP current event: RecvKeepalive
BGP last state: OpenConfirm
Port: Local – 1029
Configured: Active
Received : Active
Negotiated: Active
Peer optional capabilities:
Peer support bgp multi-protocol extended
Peer support bgp route refresh capability
Address family IPv4 Unicast: advertised and received
Figure 1 19,
remote AS 65009,
Remote - 179
Hold Time: 180 sec
Hold Time: 180 sec
Hold Time: 180 sec
353
Keepalive Time: 60 sec