Extreme Networks EPICenter Guide Manual page 185

There are several things you can do to alleviate this problem:
Periodically clear the switch's log file using the ExtremeWare CLI
●
and logout messages are Informational level messages. You can create a Telnet macro to do this.
Disable device Telnet polling by clearing the Poll Devices Using Telnet property in the Devices list
●
on the Server Properties page of the Administration applet. However, if you do this, EPICenter will
not be able to do edge port polling through the MAC Address Poller, and will not be able to get
Netlogin information, or Alpine power supply IDs.
Increase the polling interval for all EPICenter polling by changing the value of the SNMP Poll
●
Interval property in the SNMP list on the Server Properties page of the Administration applet. Note
that this will change the interval for all SNMP polling as well as Telnet polling.
See the EPICenter Reference Guide for more information about setting server properties.
You can set up event filtering to exclude login/logout events or clipaging enable/disable events
●
from the log. See the following discussion for more details.
With ExtremeXOS 11.2 you can set up filters to suppress the log entries generated by EPICenter login
and logout of the switch. Use of these filters is based on the assumption that one can trust a login from
the system on which EPICenter is installed, and from the account EPICenter uses to login to the device.
To set up this filter you would use the following four commands, where
name used by EPICenter to login to the switch, and
where the EPICenter server is installed:
configure log filter DefaultFilter add exclude event aaa.authPass strict-match string "<EPIC_account>"
configure log filter DefaultFilter add exclude event aaa.authPass strict-match string "<EPIC_ip_addr>"
configure log filter DefaultFilter add exclude event aaa.logout strict-match string "<EPIC_account>"
configure log filter DefaultFilter add exclude event aaa.logout strict-match string "<EPIC_ip_addr>"
For example, to set up the filter for an EPICenter server with IP address 10.255.48.40, and using account
name "admin" to login to the switch, you would enter the following:
configure log filter DefaultFilter add exclude event aaa.authPass strict-match string "admin"
configure log filter DefaultFilter add exclude event aaa.authPass strict-match string "10.255.48.40"
configure log filter DefaultFilter add exclude event aaa.logout strict-match string "admin"
configure log filter DefaultFilter add exclude event aaa.logout strict-match string "10.255.48.40"
You can also create a filter to exclude the clipaging commands from the log. An example of such a
command in ExtremeWare 7.3.3 or ExtremeWare 7.5 is the following:
configure log filter DefaultFilter add exclude events All match string "<EPIC_ip_addr> <EPIC_account>:
disable clipaging session"
For example, to set up the filter for an EPICenter server with IP address 10.255.48.40, and using account
name "admin" to login to the switch, you would enter the following:
configure log filter DefaultFilter add exclude events All match string "10.255.48.40 admin: disable
clipaging session"
Problem: Traps may be dropped during a trap "storm."
The EPICenter server limits its processing of traps in order to be able to reliably handle trap storms
from a single or multiple devices. EPICenter limits its trap processing to 20 traps every 28 seconds from
an individual device, and a total of 275 traps every 55 seconds system-wide. Any traps that occur
beyond these limits will be discarded, but will be noted in the
EPICenter Concepts and Solutions Guide
clear log
<EPIC_account>
is the IP address of the system
<EPIC_ip_addr>
epicenter_server.log
EPICenter Server Issues
command. Telnet login
is the account
file.
185