I feel keepalive is not configured under the tunnel interface which is very much required to detect the physical link failures and bring the tunnel to down state.
do remember to key in keepalive on both the sides of the tunnel interface and check.
hope you have the static routes configured like this ..
ip route x.x.x.x 255.255.255.255 ethernet0
ip route y.y.y.0 255.255.255.0 tunnel 0
ip route y.y.y.0 255.255.255.0 bri 10
where x.x.x.x is the tunnel destination ip addrss which is required to be routed through the ethernet interface and y.y.y.0/24 the remote local lan network which you need to be reached via the tunnel interface built over the primary wireless link connected on ur ethernet port.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...