Alcatel-Lucent 6850-48 ネットワークガイド
Configuring BFD
Configuring BFD
page 30-24
OmniSwitch AOS Release 6 Network Configuration Guide
September 2009
Configuring BFD Support for Static Routes
This section provides information about how to configure and verify BFD support for static routing.
To enable BFD support for a particular static route, use the
command, as
shown below:
-> ip static-route 10.1.1.1 255.0.0.0 gateway 10.1.1.25 bfd-std status enable
Note. BFD for a static route is disabled by default. Also, Static Routes support BFD in the echo-only oper-
ational mode.
ational mode.
The above command enables BFD support for a static route with destination ip address as 10.1.1.1, desti-
nation network mask as 255.0.0.0, and gateway address as 10.1.1.25.
nation network mask as 255.0.0.0, and gateway address as 10.1.1.25.
In order to create a BFD session for a static route, the gateway address should not match with any local
interface address of the switch, and BFD should be enabled on the interface on which the gateway address
exists. If multiple routes are configured with the same gateway address, only one BFD session will run.
You can verify the BFD session list which shows the gateway address using the
interface address of the switch, and BFD should be enabled on the interface on which the gateway address
exists. If multiple routes are configured with the same gateway address, only one BFD session will run.
You can verify the BFD session list which shows the gateway address using the
command.
To enable BFD support for all static routes, use the
command, as shown below:
-> ip static-route all bfd-std enable
You can display the static routes on which BFD is enabled by using the
show ip route
command. For
example:
-> show ip route
Once BFD determines that the next hop is unreachable, it informs IPRM that the neighbor is down. On
receiving this message, IPRM moves the routes corresponding to this gateway to inactive routing database
if BFD status is enabled. If BFD determines that the gateway is reachable, IPRM moves the routes corre-
sponding to the gateway to the forwarding database.
receiving this message, IPRM moves the routes corresponding to this gateway to inactive routing database
if BFD status is enabled. If BFD determines that the gateway is reachable, IPRM moves the routes corre-
sponding to the gateway to the forwarding database.
If a BFD-enabled static route is deleted, and other BFD-enabled routes with the same gateway are avail-
able, the BFD session will continue to run; if no routes are available, the router sends NBRDEL message
to BFD-CMM.
able, the BFD session will continue to run; if no routes are available, the router sends NBRDEL message
to BFD-CMM.
+ = Equal cost multipath routes
* = BFD Enabled
Total 12 routes
Dest Address Subnet Mask Gateway Addr Age Protocol
------------------+-----------------+-----------------+---------+-----------
20.20.20.0 255.255.255.0 20.20.20.10 01:56:01 LOCAL
32.32.32.0 255.255.255.0 *20.20.20.152 00:00:01 NETMGMT
60.60.60.0 255.255.255.0 *20.20.20.152
* = BFD Enabled
Total 12 routes
Dest Address Subnet Mask Gateway Addr Age Protocol
------------------+-----------------+-----------------+---------+-----------
20.20.20.0 255.255.255.0 20.20.20.10 01:56:01 LOCAL
32.32.32.0 255.255.255.0 *20.20.20.152 00:00:01 NETMGMT
60.60.60.0 255.255.255.0 *20.20.20.152
00:01:22 NETMGMT
70.70.70.0 255.255.255.0 70.70.70.151 00:01:22 LOCAL
71.71.71.0 255.255.255.0 71.71.71.151 00:01:22 LOCAL
78.78.78.0 255.255.255.0 *80.80.80.142 00:01:22 NETMGMT
79.79.79.0 255.255.255.0 79.79.79.151 00:01:23 LOCAL
127.0.0.1 255.255.255.255 127.0.0.1 01:57:15 LOCAL
71.71.71.0 255.255.255.0 71.71.71.151 00:01:22 LOCAL
78.78.78.0 255.255.255.0 *80.80.80.142 00:01:22 NETMGMT
79.79.79.0 255.255.255.0 79.79.79.151 00:01:23 LOCAL
127.0.0.1 255.255.255.255 127.0.0.1 01:57:15 LOCAL