request-mvpn-hrs-force-revert

Syntax

Description

Force MVPN flows to switch back to actual primary and backup path on the egress PE. Use this command to reverse the no-revert behavior introduced in Junos OS Release 22.4R3-S1.

All flows or a specific single flow can be reverted. You cannot revert a subset of flows. Use the options instance, group address and source address to filter for a specific flow.

CAUTION:

Execute this command only when the system is in a stable state.

The force reversion command can be executed outside the maintenance window as the state of the primary path would be UP. In which case the PFE forwarding path changes from backup to primary.

During force reversion, if the primary path state is not UP for a particular S, G then the PFE will not force revert the relevant S, G.

Note that PFE will revert based on primary path status and that may lead to loss in certain scenarios. For example, if we have an IPMSI tunnel with traffic above the hot-root-standby min-rate but if some flows within this tunnel are not carrying traffic on the primary path, the PFE will still revert as the primary path state is UP, and those individual flows will experience traffic loss.

Convergence during execution of forced reversion to primary path can be expected to be of same order as hot-root-standby min-rate convergence.

Options

instance `instance-name`	(Optional) Name of the instance that you want to revert.
group `group-address`	Group address of the flow.
source `source-address`	Source address of the flow.

Required Privilege Level

view

Output Fields

When you enter this command, you are provided no feedback on the status of your request if successful. You can enter the show multicast route command to verify the operation.

Upon failure, the following status messages are displayed with error code 501.

Sample Output

request mvpn hrs-force-revert
request mvpn hrs-force-revert instance vrf1 group 233.252.0.1 source 10.1.1.1
request mvpn hrs-force-revert instance vrf2 group 233.25.0.2 source 10.1.1.2