EXOS – DefaultFilter / Debuging

30th December 2015 by Martin Flammia

Filed under Extreme Networks EXOS

Last modified 4th January 2016

The best way to debug is with the use of the filter, please refer the logging section for more detail on how to set this up.

To get started the ‘DefaultFilter’ has a bunch of events that are enabled by default, these are identified as a ‘Y’ under the column ‘In’, and can be listed with the following command:

If you want to know exactly what all the events are and what they do and all the other events you can add, you can download the ‘EMS Events Catalogue’ from the Extreme Networks website from http://documentation.extremenetworks.com/ems_catalog/

The syntax for the show log command is as follows, which each example will be shown in the proceeding post:

There are a few ways to attack the problem from a logging point of view. The first would be to target those logs that are relevant to the problem and the would be to see if events are occurring. We will start with the latter and view events that are occurring:

You can clear the counters, then re-run the command to see which events are increasing and possibly an indication to the problem:

The events occurred will look something like the following:

Once you know what events to target you can add them to your ‘DefaultFilter’ or create a new filter specifically for that event and then say, just add them to syslogs.

In order to view messages from Severity level Debug-Data, Debug-Summary and Debug-Verbose you have to enable debug mode:

WARNING: This must be enabled with precaution though as this will have a performance issue on the switch.

To view what’s included and excluded in a filter use the following command:

This next command gives you a lot of information, of which each is explained further:

The elements of interest are:

• Severity – this will give you the severity at which that particular event occurs.
• Occurred – this will give you the count of every time that particular event has happened.
• In – this gives you whether the event is included in the filter.
• Notified – this gives you how many times an event has been sent.

For example you will observe from the output that an ‘In’, condition ‘localAuthen’ has been set to ‘N’, yet it has ‘Occurred’ 54 times, but due to not being part of the filter there have been non ‘Notified’.

There may be a situation where you are getting logs that you do not want to be notified about, such as the following:

This can be excluded by adding the following command:

A common set of excludes include the following:

The example given below shows how to add events to the “DefaultFilter”, of which the below gives the best events to add if trying to diagnose OSPF related issues:

or for spanning tree:

Leave a Comment