rui-slave inbound without-forwarding

Usage Scenario

In hot backup scenarios, when a switch sends a broadcast packet, the packet is copied to the slave device. If the slave device is not required to forward the packet, you can run the rui-slave inbound without-forwarding command to disable the slave device from forwarding the packet.

Configuration Impact

After this command is configured in hot backup scenarios, traffic is lost during a master/slave switchover. The switchover time is about 50 ms, and the switchback time is at the second level.

The bitmap corresponding to the VRRP table of the main interface is set to 0 if the following conditions are met: Two VRRP backup groups with the same VRID are configured on different sub-interfaces of a main interface (For example, a VRRP backup group has been configured on the interface 1/0/0.1 and its status is backup, but a VRRP backup group with the same VRID has been configured on the interface 1/0/0.6 and its status is Master); The RBP is bound to the interface 1/0/0.3, and a backup VRRP backup group is configured in the RBP view; The rui-slave inbound without-forwarding command is configured in the RBP view. However, since sub-interface 1/0/0.6 of this main interface is using the VRRP table, the VRRP table of the corresponding interface cannot be set invalid and backup without forwarding will be affected.

Precautions

In VS mode, this command is supported only by the admin VS.

• The peer-backup virtual command is configured in the view of the RBP because the slave device in a backup group still needs to forward backup packets. When the rui-slave inbound without-forwarding command is run after the peer-backup virtual command has been configured in the RBP view, a message is displayed, indicating that the rui-slave inbound without-forwarding command cannot be run in virtual backup scenarios. In hot backup scenarios, when the peer-backup virtual command is run after the rui-slave inbound without-forwarding command has been configured in the RBP view, a message is displayed, indicating that the peer-backup virtual command cannot be run. To run the peer-backup virtual command, you must delete the rui-slave inbound without-forwarding command configuration.
• The rui-slave inbound without-forwarding command must be configured on both the master and slave devices. When a master/slave switchover is performed, the rui-slave inbound without-forwarding command configured on the master device takes effect.
• In a dual-device hot backup scenario, if multiple RBPs are bound to the same VRRP backup group, all slave devices of the RBPs are allowed to forward packets even if packet forwarding is enabled only for some RBPs.