For those mid-level technicians and engineers in your network who are more comfortable with using the CLI to monitor continuous system operation, JUNOS offers tools in addition to syslog and SNMP for obtaining the information necessary to ensure continuous system operation and high availability. The primary tool for these technicians is event policies, which make it possible to define a list of commands to be run when a trigger event occurs. The output from these commands can be sent to an external source for root-cause failure analysis, for network monitoring, and to develop a network baseline. You configure event policies in the standard configuration file of the network equipment, and they are visible when you display the contents of the configuration.
Just as with syslog and SNMP, you must determine up front exactly what information to retrieve during periodic checks or in the case of an expected or unexpected event. Without proper and thorough planning, the amount of information available from your network equipment can be overwhelming. While you cannot fully customize information gathered from event policies, CLI pipes and other tricks are available to help filter command output. Table 10-1 is an example of an event policy plan.
Table 10-1. Event policy planning