Table of Contents
Advertisement
Troubleshooting
Local Client Runtime Problems
When the EPM becomes unresponsive or does not launch, check the following:
Verify that the client has at least 1 GB of memory. The EPM requires up to 512 MB of available
●
memory but functions better with 1 GB.
Terminate any other applications that may be consuming memory and restart the EPM. Verify that it
●
executes correctly.
Verify that the CPU is not "swamped" with other intensive processing tasks. Reduce the other tasks
●
and restart the EPM. Verify that the EPM executes correctly.
Rule and Policy Version Problems
When the policy does not support CLEAR-Flow, check the following:
Verify that the user specified version 3 when opening an external policy file. If not, reopen the policy
●
with the correct version.
Verify that the policy file looks like a reasonable Extreme policy file.
●
SSH Problems
When the EPM has connection problems, use the following procedure.
To display the status of SSH process:
1 telnet/ssh to the switch
2
show process exsshd
To start SSH process on the switch
1 telnet/ssh to the switch
2
start process exsshd
To terminate SSH process on the switch
1 telnet/ssh to the switch
2
terminate process exsshd graceful
To terminate and restart SSH process during a software upgrade on the switch
1 telnet/ssh to the switch
2
restart process exsshd
78
Extreme Networks Policy Manager (EPM) 1.2 User Guide
Advertisement
Table of Contents
