SD-WAN

In the Service Policy, there are 4 settings under Session Resiliency:

• none
• failover
• revertible-failover
• packet-duplication

What does each setting do?

The Session-Resiliency setting applies when there are multiple paths available between a pair of 128T peers (two routers peering using the 128T secure vector routing technique). The setting refers to how established flows behave in terms of utilizing available paths.

The "none" setting means that each session will utilize one, and only one, path during its lifetime. If the path becomes impaired, any established sessions with the "none" setting will not be failed over to another path. Even if the path experiences a hard down, those sessions will be terminated and removed.

The "failover" option will ensure that sessions are seamlessly migrated to the next best available path, per the various policies configured, if the current path experiences a hard down, or its QoS measurements no longer meet the session's SLA requirements configured in its associated service policy.

The "revertible-failover" option will act as the previous option, with the exception that if the original impaired path comes back in service, the migrated session will be moved back to that original path. This sometimes has the potential of session flapping back and forth between paths, so may not always be appropriate.

Finally, "packet-duplication" sends all of the session's packets over multiple available path, and duplicate copies of those packets are discarded at the receiving end. Packet-duplication is obviously more taxing on the total available bandwidth between a pair of peers, but can substantially improve QoS/MOS measurements compared to utilizing just one path .

In the Service Policy, there are 4 settings under Session Resiliency:

• none
• failover
• revertible-failover
• packet-duplication

What does each setting do?

The Session-Resiliency setting applies when there are multiple paths available between a pair of 128T peers (two routers peering using the 128T secure vector routing technique). The setting refers to how established flows behave in terms of utilizing available paths.

The "none" setting means that each session will utilize one, and only one, path during its lifetime. If the path becomes impaired, any established sessions with the "none" setting will not be failed over to another path. Even if the path experiences a hard down, those sessions will be terminated and removed.

The "failover" option will ensure that sessions are seamlessly migrated to the next best available path, per the various policies configured, if the current path experiences a hard down, or its QoS measurements no longer meet the session's SLA requirements configured in its associated service policy.

The "revertible-failover" option will act as the previous option, with the exception that if the original impaired path comes back in service, the migrated session will be moved back to that original path. This sometimes has the potential of session flapping back and forth between paths, so may not always be appropriate.

Finally, "packet-duplication" sends all of the session's packets over multiple available path, and duplicate copies of those packets are discarded at the receiving end. Packet-duplication is obviously more taxing on the total available bandwidth between a pair of peers, but can substantially improve QoS/MOS measurements compared to utilizing just one path .

In the Service Policy, there are 4 settings under Session Resiliency:

• none
• failover
• revertible-failover
• packet-duplication

What does each setting do?

The Session-Resiliency setting applies when there are multiple paths available between a pair of 128T peers (two routers peering using the 128T secure vector routing technique). The setting refers to how established flows behave in terms of utilizing available paths.

The "none" setting means that each session will utilize one, and only one, path during its lifetime. If the path becomes impaired, any established sessions with the "none" setting will not be failed over to another path. Even if the path experiences a hard down, those sessions will be terminated and removed.

The "failover" option will ensure that sessions are seamlessly migrated to the next best available path, per the various policies configured, if the current path experiences a hard down, or its QoS measurements no longer meet the session's SLA requirements configured in its associated service policy.

The "revertible-failover" option will act as the previous option, with the exception that if the original impaired path comes back in service, the migrated session will be moved back to that original path. This sometimes has the potential of session flapping back and forth between paths, so may not always be appropriate.

Finally, "packet-duplication" sends all of the session's packets over multiple available path, and duplicate copies of those packets are discarded at the receiving end. Packet-duplication is obviously more taxing on the total available bandwidth between a pair of peers, but can substantially improve QoS/MOS measurements compared to utilizing just one path .

In the Service Policy, there are 4 settings under Session Resiliency:

• none
• failover
• revertible-failover
• packet-duplication

What does each setting do?

The Session-Resiliency setting applies when there are multiple paths available between a pair of 128T peers (two routers peering using the 128T secure vector routing technique). The setting refers to how established flows behave in terms of utilizing available paths.

The "none" setting means that each session will utilize one, and only one, path during its lifetime. If the path becomes impaired, any established sessions with the "none" setting will not be failed over to another path. Even if the path experiences a hard down, those sessions will be terminated and removed.

The "failover" option will ensure that sessions are seamlessly migrated to the next best available path, per the various policies configured, if the current path experiences a hard down, or its QoS measurements no longer meet the session's SLA requirements configured in its associated service policy.

The "revertible-failover" option will act as the previous option, with the exception that if the original impaired path comes back in service, the migrated session will be moved back to that original path. This sometimes has the potential of session flapping back and forth between paths, so may not always be appropriate.

Finally, "packet-duplication" sends all of the session's packets over multiple available path, and duplicate copies of those packets are discarded at the receiving end. Packet-duplication is obviously more taxing on the total available bandwidth between a pair of peers, but can substantially improve QoS/MOS measurements compared to utilizing just one path .

In the Service Policy, there are 4 settings under Session Resiliency:

• none
• failover
• revertible-failover
• packet-duplication

What does each setting do?