hrp standby sync fast-forwarding table enable

Only the USG6510E/6510E-POE/6530E does not support this command.

In versions earlier than V600R007C20SPC200, USG6680E and USG6712E/6716E support this command. For V600R007C20SPC200 and later versions, device batches are distinguished by BomID Version (which can be checked using the display version command). Only the USG6680E and USG6712E/6716E whose BomID Version is earlier than 003 and whose device BOM numbers does not contain "-001" support this command.

By default, the standby device does not automatically deliver the fast forwarding table.

In hot standby deployment in active/standby mode, if the active device properly operates, the standby device does not receive service packets. Therefore, the delivery of the fast forwarding table is not triggered. After active/standby switchover, the new active device needs to re-implement the fast forwarding table delivery process, which may occupy additional CPU resources.

Therefore, in this scenario, if hardware fast forwarding is enabled, you need to run the hrp standby sync fast-forwarding table enable [ asym-next-hop ] command in active device to enable the standby device to automatically deliver the fast forwarding table.

In a hot standby (active/standby) scenario, if the FWs work at Layer 3 and the next hops of the routes on the active and standby FWs are different, the asym-next-hop parameter must be configured. The outbound interfaces and next-hop addresses of entries recorded in the hardware fast forwarding table backed up will replace the outbound interfaces and next-hop addresses of the routes (excluding PBR routes) on the standby device. If FWs work at Layer 2, the asym-next-hop parameter does not need to be configured.

In load balancing scenario, the function of automatically delivering hardware fast forwarding table is not recommended on the standby device.