Howto filter “No VR found on VLAN xxx with VR Id xxx” on Extreme XOS switches | Robert Penz Blog

Howto filter “No VR found on VLAN xxx with VR Id xxx” on Extreme XOS switches

May 25, 2014

If your Extreme Networks switches are using VRRP and other devices are using it also in the same VLAN, the Exterme XOS switches will complain loudly about that … one log line per broadcast. In my case it were two per second and as the switch stores only 1000 log lines .. the log soon contained only these entries:

05/22/2014 17:29:41.11 Slot-1: No VR found on VLAN xxx with VR Id xxx 05/22/2014 17:29:40.48 Slot-2: No VR found on VLAN xxx with VR Id xxx 05/22/2014 17:29:40.11 Slot-1: No VR found on VLAN xxx with VR Id xxx 05/22/2014 17:29:39.48 Slot-2: No VR found on VLAN xxx with VR Id xxx 05/22/2014 17:29:39.11 Slot-1: No VR found on VLAN xxx with VR Id xxx

The one pitfall with using the exclude match string variable is that the VRIDs must not be treated as string variable. This does not work because Extreme XOS does not treat the VRID as a string variable, but rather as a integer. To determine the valid variables available for the specific event you’ll need to type following:

Slot-1 xxxxxxx.1 # show log events "VRRP.UnkVR" details Component SubComponent Condition Severity Parameters ----------- ------------ ----------------------- ------------- ---------- VRRP UnkVR Warning 2 Total 0 - string 1 - number (32-bit unsigned int) No VR found on VLAN %0% with VR Id %1%

This tells us that to filter on the VRRP.UnkVR messages, there is a string variable (%0%) equal to the VLAN name, and a integer (%1%) equal to the VRID itself. Because Extreme XOS interprets the VRID itself as a number and not a string, doing an exclude match string will not work. You must use the number variable as follows:

configure log filter "DefaultFilter" add exclude events "VRRP.UnkVR" match number xxx

From the Concept Guide:

The filter can be associated with one or more targets using the command to control the messages sent to those targets. The system has one built-in filter named DefaultFilter, which itself may be customized. Therefore, the if a filter other than DefaultFilter is desired. As its name implies, DefaultFilter initially contains the default level of logging in which every Extreme XOS component and subcomponent has a pre-assigned severity level.

PS: You can use this solution to filter out any other event, just check with show log events "xxxx" details

In HowTo, Networking | No Comments

No Comments yet »

RSS feed for comments on this post. TrackBack URI

Leave a comment

Powered by WordPress
Entries and comments feeds. Valid XHTML and CSS. 34 queries. 0.040 seconds.