Enabling Trap; Displaying And Maintaining Bfd - H3C LS-3100-52P-OVS-H3 Operation Manual

If route flaps occur, enabling BFD may worsen the route flaps. Therefore, enable BFD with care in
such cases.
The source address of echo packets must be configured if the BFD session operates in the echo
mode.
If you configure BFD for a static route, you need to specify the outbound interface and next hop IP
address for the route.
BFD cannot be used for a static route with the outbound interface having the spoofing attribute.
BFD can be used for static routes with direct nexthops rather than non-direct nexthops.
In the draft, the BFD echo function is revised to specify that a BFD session is established at only
one end when the echo mode is used.
For static route configuration, refer to Static Routing Configuration in the IP Routing Volume.

Enabling Trap

When the trap function is enabled on the BFD module, the module will generate trap messages at the
notifications level to report the important events of the module. The generated trap messages are sent
to the device's information center, which determines the output rules for the trap messages, namely,
whether to output the trap messages and the output destinations). For the information center
configuration, refer to Information Center Configuration in the System Volume.
Follow these steps to enable BFD trap:
To do...
Enter system view
Enable BFD trap
For the description of the snmp-agent trap enable isdn command, refer to the snmp-agent trap
enable command in SNMP Commands in the System Volume.

Displaying and Maintaining BFD

Display information about
BFD-enabled interfaces
Display information about enabled
BFD debugging
Display PAF configuration information
Use the command...
system-view
snmp-agent trap enable bfd
To do... Use the command...
display bfd interface [ verbose ]
display bfd debugging-switches
display bfd paf
1-12
Remarks
—
Optional
Enabled by default
Remarks
Available in any
view
Available in any
view
Available in any
view