Extreme Networks EPICenter 5.0, Manual

Page: 174 / 208

174 EPICenter Concepts and Solutions Guide
Troubleshooting
Problem: A program specified as an action for an alarm (in the Run Program field) does not get
executed. It includes output to the desktop among its functions.
If you are running the EPICenter server as a service, you must specifically tell it to allow output to the
desktop. To do this you must stop and restart the EPICenter server, as follows:
1 In the Services properties window, select EPICenter 5.0 Server and click Stop . (To find the Services
window, from the Start menu select Settings, then Control Panel, the double-click the Services icon).
2 When the EPICenter 5.0 Server service has be stopped, select it again and click Startup... . This displays
a pop-up window where you can specify start-up options.
3 In the lower part of the window, in the Log On As: area, click the box labeled Allow Service to Interact
with Desktop . Then click OK .
After the EPICenter server restarts, the program you have specified as an alarm action should execute
correctly.
To specify a batch file that does output to the desktop, you must specify the “.bat” file within a DOS “cmd”
command, as follows:
cmd /c start <file.bat>
where <
file.bat
> is the batch file you want to run.
Problem: Email alarm actions generate too much text for a text pager.
You can use the “Short email to:” option to send an abbreviated message appropriate for a text pager or
cell phone. The short email provides only very basic alarm information. See Chapter 9 for more details on
using the email options as an alarm action.
Problem: Alarm action that executes a script does not run to completion.
Check to determine if a command in the script has failed. If one command in the script fails, the rest of the
script will not be executed. This is expected behavior.
If you want to execute multiple script commands regardless of individual command failure, you must
catch the exception thrown in each command. For example, a script action:
catch {do Command1}
catch {do Command2}
will execute Command2 even if command1 fails. For detailed information on how to use the Tcl script,
consult the Tcl man pages or Help file at
http://www.tcl.tk
.
ESRP Monitor
Problem: None of the member VLANs of an ESRP group are appearing in the ESRP Manager applet.
Make sure that all members of the ESRP group use the same election algorithm. If there is an election
algorithm mismatch between any of the ESRP-enabled switches in any of the ESRP-enabled VLANs in the
ESRP group, this causes a misconfiguration scenario, and ESRP will not function. As a result, none of the
members of the ESRP group will appear in the ESRP Manager applet.