Per the object's own description this indicates whether an FRR backup tunnel needs to be created for this dynamic encap tunnel, applying here to a co-routed bidirectional circuit rather than a unidirectional one. An admin enabling this on a co-routed tunnel expects a local-repair backup covering both directions of the circuit to be pre-signaled, so a downstream failure triggers a fast switch for the whole bidirectional path rather than waiting on full end-to-end re-signaling. For example, this set to on(1) on a co-routed voice trunk should produce sub-100ms recovery in both directions if a link along the shared path fails, versus a multi-second gap without FRR.