Logmanager documentation
Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage

Extreme Network XOS

The way to process logs on devices with Extreme Networks XOS is very similar to the work with Rsyslog or Syslog-NG in Unix. There are more event sources (e.g. verification components, management of dynamic routing processes, ports state etc.), where every component informs about different events. Those are sorted by importance to the levels Emergency - Debug. Filters may be specified in settings to selected events and importance level, which has to be send to Logmanager.

First it is appropriate to create a copy of default events filter, which can be then easily edited without affecting other logs:

create log filter logmanager copy "DefaultFilter"

When using synchronization of time via NTP, this informational message appears regularly, but it may be ignored by command:

configure log filter "logmanager" add exclude events DM.Notice match string "Setting hwclock time to system time, and broadcasting time"

Sample configuration assumes, that you selected facility local0 for sending messages (local0 - local7 may be used).

Forwarding messages to Logmanager server settings:

configure syslog add <Logmanager_IP_address> vr <Virtual router> local0
configure log target syslog <Logmanager_IP_address> vr <Virtual router> local0 filter "logmanager" severity info
configure log target syslog <Logmanager_IP_address> vr <Virtual router> local0 format timestamp seconds date Mmm-dd event-name condition severity priority tag-name host-name
enable log target syslog <Logmanager_IP_address> vr <Virtual router> local0
Logmanager_IP_address is the IP address of your Logmanager server.
Item Virtual router has to be replaced by virtuarl router,which should be used for communication with Logmanager. Usualy VR-Mgmt is used in case of out-of-band management using Mgmt port or VR-Default when using in-band management.