A backup link that stays quiet until needed
BR-02 (site 102) has one internet link. A cellular modem gives it a second way out for the day the cable breaks, but the data plan is metered and the radio link is slower than the wired one. Making the cellular transport a normal tunnel interface would bring its tunnels up next to the main one: BFD probes and control traffic would flow all the time, and traffic could be sent over it whenever a policy or a path comparison allowed. A last-resort circuit avoids that. The interface is up and ready, but it does not carry tunnels while another transport is working.
What the router does, in order
- Normal state: the internet tunnel interface is up and carries the tunnels and the control connection. The cellular interface, marked as a last-resort circuit, has no tunnels.
- The internet link fails. BFD sessions on it stop receiving replies and are declared down.
- With no other tunnel interface left, the router brings up tunnels on the last-resort circuit, and the control connection to the SD-WAN Controller (formerly vSmart) and Manager moves with it if it was lost.
- The remote sites learn of the new TLOC through OMP and BFD comes up on the new tunnels.
- Traffic flows over the cellular link.
- The internet link returns. The router sees the normal transport is healthy again and the last-resort tunnels are torn down. Traffic returns to the main link.
The exact conditions that trigger and release the circuit, and how the router decides that the other transports are gone, can differ by release. Check your release's guide before relying on a particular trigger.
On small screens, swipe sideways or focus the diagram and use the arrow keys.
What the switchover costs
On small screens, swipe sideways or focus the diagram and use the arrow keys.
Together this is typically seconds to tens of seconds. It is not a promise. It depends on the BFD timers, the radio conditions and the carrier, so measure it in your own lab and keep the result. A design that needs a sub-second failover needs a second wired transport, not a last-resort circuit.
Cautions before relying on it
- All traffic moves at once. When the circuit activates, the whole site's traffic goes onto the cellular link. A 20 Mbit/s radio link carrying a branch that normally uses 200 Mbit/s will be saturated. Size for it, or limit what may use it. The single-application scenario looks at that.
- The far side must be reachable. The hubs and Controllers must be reachable from the cellular carrier's network, and the hubs need a transport that the cellular tunnels can connect to, on a matching colour where the design requires one.
- The link must be monitored. A backup that is down when needed is found out too late. An idle circuit still needs a check for signal, SIM state and plan.
- Fail-back needs a test. Do not assume the tunnels return to the main link cleanly. Test what happens to open sessions when they do.
The configuration idea
On IOS XE SD-WAN the circuit is an option on the tunnel interface. The fragment below shows the idea for a cellular interface in colour lte. Confirm the exact syntax in your release's configuration guide. In practice it is set in the SD-WAN Manager template, not typed by hand.
sdwan
interface Cellular0/2/0
tunnel-interface
encapsulation ipsec
color lte
last-resort-circuit
no allow-service all
exit
exit
exitFragment written for this lesson; confirm the syntax in your release's guide. The interface name is an example. The sdwan interface block makes the cellular port part of the overlay. tunnel-interface turns it into a transport. encapsulation ipsec sets the tunnel type. color lte names the transport, and the colour is an example. last-resort-circuit is what keeps the tunnels down while another interface works. The allow-service line closes management services on the radio link; it is a design choice, not a requirement of the feature.
A switchover test for a lab or maintenance window
Run it in a lab or a planned window, with a person at the site or a way to restore the link remotely. Keep a continuous ping from BR-02 to an application address in the data centre, for example in 10.20.1.0/24, from the beginning.
- Record the baseline: control connections, BFD sessions and OMP routes on BR-02, showing tunnels on the main transport only.
- Disconnect the main internet link (shut the interface or pull the cable). Note the time.
- Note when the ping stops and when it resumes. The gap is the measured switchover time.
- Record the same outputs on the cellular link: tunnels on lte, control connection state, and the throughput that the link gives.
- Restore the main link. Note when the cellular tunnels go away and whether the ping drops again.
- Record the carrier data used during the test, so the cost of a real event can be estimated.
What to record: the three times (failure, resume, fail-back), the throughput on the cellular link, the data used, the software release, and any session that broke. Repeat the test when the release, the carrier plan or the BFD timers change.
Test yourself on last-resort circuits
BR-02 has a wired internet link and a cellular link set as a last-resort circuit. Both are physically up and the wired link is healthy. Where do the tunnels run?
A branch needs a failover that is almost unnoticeable for voice. Is a last-resort cellular circuit enough?
During a test, the cellular circuit activates but the application is slow and a monitoring tool shows the link at 100% utilisation. What was most likely missed in the design?
After the wired link is restored, the cellular tunnels are still up an hour later. What should you check?