Static Routing-Track-Bfd Collaboration Configuration Example - HP 5130 EI Series Configuration Manual

Static routing-Track-BFD collaboration configuration example

Network requirements
As shown in
Switch A is the default gateway of the hosts in subnet 20.1.1.0/24.
•
Switch B is the default gateway of the hosts in subnet 30.1.1.0/24.
•
• Hosts in the two subnets communicate with each other through static routes.
To ensure network availability, configure route backup and static routing-Track-BFD collaboration on
Switch A and Switch B as follows:
• On Switch A, assign a higher priority to the static route to 30.1.1.0/24 with Switch B as the next hop.
This route is the master route. The static route to 30.1.1.0/24 with Switch C as the next hop acts as
the backup route. When the master route is unavailable, BFD can quickly detect the route failure to
make the backup route take effect.
On Switch B, assign a higher priority to the static route to 20.1.1.0/24 with Switch A as the next hop.
•
This route is the master route. The static route to 20.1.1.0/24 with Switch C as the next hop acts as
the backup route. When the master route is unavailable, BFD can quickly detect the route failure to
make the backup route take effect.
Figure 31 Network diagram
Configuration procedure
1. Create VLANs and assign ports to them. Configure the IP address of each VLAN interface as
shown in
2. Configure Switch A:
# Configure a static route to 30.1.1.0/24 with the next hop 10.2.1.2 and the default priority 60,
and associate this static route with track entry 1.
<SwitchA> system-view
[SwitchA] ip route-static 30.1.1.0 24 10.2.1.2 track 1
# Configure a static route to 30.1.1.0/24 with the next hop 10.3.1.3 and the priority 80.
[SwitchA] ip route-static 30.1.1.0 24 10.3.1.3 preference 80
# Configure the source address of BFD echo packets as 10.10.10.10.
[SwitchA] bfd echo-source-ip 10.10.10.10
# Configure track entry 1, and associate it with the BFD session to verify the connectivity between
Switch A and Switch B.
[SwitchA] track 1 bfd echo interface vlan-interface 2 remote ip 10.2.1.2 local ip
10.2.1.1
Figure 31:
Figure 31. (Details not shown.)
141