So it seems that perhaps not the FW update, but the placement of the rules changed the behavior.
I’m unable to place the rule below the PepVPN route section as originally had been. The rule previously automatically populated itself as above. However, this is the new behavior and the message given when I try to move it below the PepVPN section…
However, it seems that it works…I’ve decreased the failure detection to its default to minimize traffic across the links. All that’s going now are two pings in either direction at ~1400 bytes…
Is your suggestion that the policy should be below the PepVPN section? If so, that would seem to be not the case. Additionally, as suggested, the FW upgrade did not change the behavior of the status of the additional tunnels. As you can see, they still show as inactive. This is the same on both sides.