Symptom: How does an NE40E redirect traffic to different interfaces while at the same time supporting BFD association?.
1. The NE40E has two outbound interfaces connecting to Supplier1 and Supplier2, respectively.
2. The NE40E is interconnected to Supplier1 and Supplier2 over transport devices. There is a possibility that the transmission is interrupted but the physical interface is still up.
Requirement: The NE40E needs to redirect traffic based on the internal network address so that traffic is preferentially forwarded through Supplier1 and then through Supplier2
1. The NE40E can be configured to redirect traffic to multiple hops but cannot be associated with BFD. Therefore, if the transmission to Supplier1 is interrupted and the physical interface is not down, traffic switching is not performed.
You are advised to perform the following configurations:
Step1 Configure a basic traffic policy to redirect traffic to 126.96.36.199.
traffic classifier test1
traffic behavior test1
redirect ip-nexthop 188.8.131.52
traffic policy test1
classifier test1 behavior test1
Step2 Configure a one-arm BFD echo session.
bfd test1 bind peer-ip 10.1.1.2 interface GigabitEthernet 0/1/7 source-ip 10.1.1.1 one-arm-echo
Step 3 Configure two routes with the next hop IP address of 184.108.40.206.
Traffic is preferentially forwarded to Supplier1 by default, but is associated with
the BFD session.
ip route-static 220.127.116.11 32 10.1.1.2 track bfd-session test1 //Traffic forwarded to Supplier1 is associated with BFD.
ip route-static 18.104.22.168 32 10.1.2.2 preference 100 //The priority of the traffic forwarded over Supplier2 is changed to 100, lower than the default value (60).
This solution allows both redirection to multiple hops and BFD association.