Having some trouble with the setup of a Local Director 417 using http probes to test the functionality of an underlying database.
The symptoms are as follows:
2 real servers and 1 virtual. Http-probes sent with a 20 second interval. If one real server is taken down - the LD keeps probing the server every 20 seconds and brings it up if/when the probe succeeds.
However - if BOTH the real servers are taken down - in a few seconds the virtual server is also marked as down (naturally). But here is the problem - as the virtual server is marked as down the LD stops sending HTTP probes onto the real servers, thereby making automatic recovery impossible....
In this state I can of course just bring one of the real servers up with the "in-service" command. The virtual server then comes up and it starts sending probes to BOTH servers again.
So to summarize my problem: How can I accomplish automatic recovery when both my real servers are taken down (lets say for backup) using HTTP probes?
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...