Extreme Networks Ridgeline Guide Manual page 305

See "Administering Ridgeline" in the Ridgeline Reference Guide for information on Ridgeline
Administration.
Problem: Telnet polling messages can fill up a device's syslog file.
The Ridgeline server uses Telnet polling to retrieve certain switch information such as Netlogins, FDB
data (if FDB polling is enabled) and power supply information. By default, Ridgeline does status polls
every five minutes and detailed polls once every 90 minutes. Each telnet login and logout message is
logged to the switch's log file, and will eventually fill up the log.
In addition, in some cases Ridgeline needs to disable CLI paging so the poller can retrieve the full
results of some CLI commands. An entry is created in the switch log for each disable clipaging
command, which can also contribute to filling up the log.
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.
Disable device Telnet polling by clearing the Poll Devices Using Telnet property in the Devices list
●
on the Server Properties page of Ridgeline Administration. However, if you do this, Ridgeline 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 Ridgeline polling by changing the value of the SNMP Poll
●
Interval property in the SNMP list on the Server Properties page of Ridgeline Administration. Note
that this will change the interval for all SNMP polling as well as Telnet polling.
See the Ridgeline 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 and higher you can set up filters to suppress the log entries generated by
Ridgeline 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 Ridgeline is installed, and from the account Ridgeline uses to
login to the device.
To set up this filter you would use the following four commands, where
name used by Ridgeline to login to the switch, and
where the Ridgeline 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 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 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:
Ridgeline Concepts and Solutions Guide
clear log
<EPIC_account>
is the IP address of the system
<EPIC_ip_addr>
command. Telnet login
is the account
303