Enabling trap, Enabling logging of peer state changes, Configuring bfd for bgp – H3C Technologies H3C SecPath F1000-E User Manual

Page 497

Advertising
background image

472

Step Command

Remarks

5.

Enter system view.

system-view

N/A

6.

Enter BGP view.

bgp as-number

N/A

7.

Enable compatibility with

routers not compliant with RFC
3065 in the confederation.

confederation nonstandard

Optional
Not enabled by default

Enabling Trap

After Trap is enabled for BGP, BGP generates Level-4 traps to report important events. The generated
traps are sent to the information center of the device. The output rules of the traps (whether to output the

traps and the output direction) are determined according to the information center configuration. (For

information center configuration, see System Management and Maintenance Configuration Guide.)
To enable Trap:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enable Trap for BGP.

snmp-agent trap enable bgp

Optional.
Enabled by default.

Enabling logging of peer state changes

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter BGP view.

bgp as-number N/A

3.

Enable the logging of peer state
changes globally.

log-peer-change

Optional.
Enabled by default.

4.

Enable the logging of peer state
changes for a peer or peer

group.

peer { group-name | ip-address }
log-change

Optional.
Enabled by default.

Configuring BFD for BGP

BGP maintains neighbor relationships based on the keepalive timer and holdtime timer, which are set in

seconds. BGP defines that the holdtime interval must be at least three times the keepalive interval. This

mechanism makes link failure detection rather slow; once a failure occurs on a high-speed link, a large

quantity of packets will be dropped. BFD is introduced to solve this problem. It detects links between
neighbors quickly to reduce convergence time upon link failures.
To enable BFD for a BGP peer:

Advertising