BGP/1/hwBgpRouteLoopDetected_active: The local device has detected a BGP routing loop. (BGP instance name=[InstanceName], Vpn-instance=[Vpn-instance], Afi=[AddrFamilyAfi], Safi=[AddrFamilySafi])
| Parameter Name | Parameter Meaning |
|---|---|
|
InstanceName |
BGP instance name. "-" indicates the default BGP instance, and other values indicate multiple instances. |
|
Vpn-instance |
Name of a VPN instance |
|
AddrFamilyAfi |
Address family. |
|
AddrFamilySafi |
Sub-address family. |
Improper configurations exist on some devices on the network. For example, the number of times for allowable local AS number repetition is set (using the peer allow-as-loop command) and the route preference is changed in a routing policy; alternatively, the AS number and route preference are changed in a routing policy. As a result, a device receives the routes that it has advertised from its BGP peers again, and the preference of the received routes is higher than that of the routes advertised by the device.
After detecting a BGP route loop, the device automatically adjusts the route selection rule to eliminate the impact of route flapping caused by the loop on services.
Loops still exist between devices. In addition, the route selection rules adjusted by the system during automatic loop breaking may cause the traffic path to be different from the expected one. After the system reports an alarm, you can check the routing information about the loop based on the diagnosis log and rectify the improper configuration that causes the loop. In this way, the risk source of the loop is eliminated.
After the risk source is eliminated, run the clear route loop-detect bgp alarm command in the system view of the device generating the alarm to manually clear the alarm.