Extreme Networks Policy Manager, Руководство пользователя, Страница: 77 / 82

Extreme Networks Policy Manager (EPM) 1.2 User Guide
77
B Troubleshooting
Introduction
This appendix includes suggestions for dealing with problems that may occur when running the
Extreme Networks Policy Manager (EPM). They are categorized as follows:
●
Connectivity Problems on page 77
●
EXOS Compatibility Problems on page 77
●
Local Client Runtime Problems on page 78
●
Rule and Policy Version Problems on page 78
●
SSH Problems on page 78
Connectivity Problems
When there is failure opening or saving policy file on a switch, check the following:
●
Check the network connection to the switch by pinging the switch
●
Check that the local IP address is correct.
●
Check that the NAT address is set if the client is on the outside of a NAT.
●
Check that the TFTP server is running on the client and listing on port 69.
●
Check that the file staging directory is set to the TFTP server’s root directory.
●
Check that the user running the EPM has read/write permission to the TFTP server’s root directory.
●
Check the client firewalls
●
Check that the SSH image is loaded and that it has been enabled.
●
Check the user name and password. They are case-sensitive.
●
Check the default routes on the switch and client.
EXOS Compatibility Problems
When the policy file loads with an exception or with rules that are disabled, check the following:
●
If there is an exception, attempt to reload the policy file.
●
Look at connectivity problems
●
In the case of a disabled rule, check to see if the rule contains rule pneumonics that might not be
supported by the EPM until an upgrade of EPM is produced. The customer can save the policy;
however, the rules will be commented out.