Tripp Lite B0930042E4U Owners Manual for B093- B097- and B098-Series Console S - Page 236

15. Advanced Configuration This code shows there are two alternative scripts that can be run instead of the default script. This code first checks whether a file "/etc/config/scripts/pattern-alert.${ALERT_PORTNAME}" exists. The variable ${ALERT_PORTNAME} must be replaced with "port01" or "port13", or whichever port the alert should run. If this file cannot be found, the script checks whether the file "/etc/config/scripts/portmanager-pattern-alert" exists. If either of these files exist, the script calls the exec command on the first file that it finds and runs that custom file/script instead. For example, you can copy the /etc/scripts/portmanager-pattern-alert script file to /etc/config/scripts/portmanagerpattern-alert: # cd / # mkdir /etc/config/scripts (if the directory does not already exist) # cp /etc/scripts/portmanager-pattern-alert /etc/config/scripts/portmanager-pattern-alert The next step is to edit the new script file. Open the file /etc/config/scripts/portmanager-pattern-alert using vi (or any other editor), and remove the lines that check for a custom script (the code from above). This will prevent the new custom script from repeatedly calling itself. After these lines have been removed, edit the file or add any additional scripting to the file. 15.1.3 Sample Script - Power Cycling on Pattern Match For example, if an RPC (PDU) is connected to port 1 on a console server and some telecommunications device connected to port 2, which is powered by the RPC outlet 3. Assuming the telecom device transmits a character stream "EMERGENCY" out on its serial console port every time that it encounters some specific error, the only way to fix this error is to power cycle the telecom device. The first step is to set up a pattern-match alert on port 2 to check for the pattern "EMERGENCY". Next, we need to create a custom script for this alert: # cd / # mkdir /etc/config/scripts (if the directory does not already exist) # cp /etc/scripts/portmanager-pattern-alert /etc/config/scripts/portmanager-pattern-alert Note: To prevent an infinite loop, make sure to remove the if statement (which checks for a custom script) from the new script. The pmpower utility is used to send power commands to an RPC device in order to power cycle the telecom device: # pmpower -l port01 -o 3 cycle (The RPC is on serial port 1. The telecom device is powered by RPC outlet 3) Now append this command to our custom script. This will guarantee the telecom device will be power cycled every time the console reads the "EMERGENCY" character stream on port 2. 15.1.4 Sample Script - Multiple Email Notifications on Each Alert If you desire to send more than one email when an alert triggers, you have to create a replacement script using the method described above and add the appropriate lines to your new script. Currently, there is a script /etc/scripts/alert-email that runs from within all the alert scripts (e.g., portmanager-user-alert or environmental-alert). The alert-email script is responsible for sending the email. The line that invokes the email script appears as follows: /bin/sh /etc/scripts/alert-email $suffix & If you wish to send another email to a single address or the same email to many recipients, edit the custom script appropriately. You can follow the examples in any of the seven alert scripts listed above. In particular, consider the portmanager-user-alert script. If you need to send the same alert email to more than one email address, find the lines in the script responsible for invoking the alert-email script, then add the following lines below the existing lines: export TOADDR="[email protected]" /bin/sh /etc/scripts/alert-email $suffix & These two lines assign a new email address to TOADDR and invoke the alert-email script in the background. 236