I was wondering how to keep a “reload in” command to act as a fail-safe when working with remote equipment. There can be only a single reload \u00a0Someone recommended using scheduled tasks or Embedded Event Manager (EEM),<\/p>\n
In the EEM, it is possible to schedule a task, at the desired time\/trigger, execute the task or restart the router. \u00a0There\u00a0are other monitoring actions the EEM can do, like send an email when a certain trigger has occurred. \u00a0 EEM available on most routers and 3xxx series of switches.<\/p>\n
The EEM process is based on core event publishers (event detectors), and the event subscribers (policies). \u00a0Obviously, the policy is based on what the detectors can detect\/trigger. \u00a0Listed below are the detectors available. \u00a0Not all are available for the IOS version.<\/p>\n
Application-Specific
\nCLI
\nCounter
\nCustom CLI
\nEnhanced Object Tracking
\nEnvironmental
\nGeneric Online Diagnostic (GOLD)
\nIdentity
\nInterface Counter
\nIPSLA
\nMac-Address-Table
\nNeighbor Discovery
\nNetFlow (NF)
\nNone
\nOIR
\nResource
\nRedundancy Framework (RF)
\nRouting
\nRPC
\nSNMP
\nSNMP Proxy
\nSNMP Notification
\nSNMP Object
\nSyslog
\nSystem Manager
\nTimer
\nIOSWDSysMon (Cisco IOS watchdog)
\nWDSysMon (Cisco IOS Software Modularity watchdog)<\/p><\/blockquote>\n<\/p>\n