I am attempting to ensure that all of my devices are getting their configs archived. Yesterday, I noticed that many of the devices listed in the "failed" category are devices that are currently not connected to the network. I placed these devices in a suspended state to prevent RME from trying to pull configurations from these devices. However, these devices are still showing up under "failed" devices in the configuration archival summary.
Is this a bug or am I just missing the point of "suspending" a device?
RME is working as designed. If a device is in a suspended or pre-deployed state, the pre-fetch checks will fail (i.e. the device will not actually be contacted). Since RME is only aware of Success and Failure from a device point of view, this is treated as a Failure. Admittedly, this is confusing, but the overall job should still be reported as a Success (provided there were no real failures).
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...