Extreme Networks Ridgeline Guide Manual page 306

Book Title
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 Ridgeline 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 Ridgeline server limits its processing of traps in order to be able to reliably handle trap storms from
a single or multiple devices. Ridgeline 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 file.
epicenter_server.log
Exceeding the first limit (>20 traps in 28 seconds) is rare, and should be considered abnormal behavior
in the managed device. If you are managing a large number of devices, you may reach the total (275)
limit in normal circumstances. If you are managing more than 1000 devices, it is recommended that you
increase the total number of traps to 500.
The trap processing limits can be changed through server properties in Ridgeline Administration. See
the Ridgeline Reference Guide for more information on setting Ridgeline server properties.
Problem: Under Solaris, an error occurs when attempting to enable the Ridgeline Syslog server
function.
By default, Solaris runs its own Syslog server. This may cause an error "Syslog Server unable to start:
Address already in use" when you attempt to enable the Ridgeline syslog server. You must first stop the
Solaris syslog server in order to have Ridgeline act as a Syslog receiver. To stop the Solaris Syslog
server, use the command:
/etc/init.d/syslog stop
Problem: Ridgeline is not receiving traps.
If the IP address of an Ridgeline host is changed via DHCP while Ridgeline is running, the system will
not receive traps. To fix the problem, you can do a manual sync on all devices, or restart the Ridgeline
server.
Problem: On a Windows system with multiple NICs, Ridgeline may not receive traps or be able to
upload or download configuration files or images.
In Windows, in a multiple NIC cards environment, the IP address that Ridgeline gets as the primary IP
address is determined by the order in which the network connection is listed in the 'Adapters and
Bindings' tab in Advanced Settings, and may not be the NIC that is actually connected to the
management network. There is no guarantee that the primary IP address that gets registered as a trap
receiver on a switch is the IP address of the NIC that Ridgeline actually uses to communicate.
You may be able to work around this by changing the order of the IP addresses in the Adapters and
Bindings tab in the select the primary IP address for Ridgeline to use:
1 From the Start menu select Settings, then select Network and Dial-up Connections. You can also
open the Network and Dial-up Connections window from the control Panel.
2 From the Advanced menu, select Advanced Settings...
3 Select the Adapters and Bindings tab, which shows the connections listed in order.
Ridgeline Concepts and Solutions Guide
304