Extreme Networks ExtremeWare XOS Command Reference Manual page 468

Commands for Status Monitoring and Statistics
To configure a scoped IPv6 address with any VLAN, use the following command:
configure log filter myFilter add events all match ipaddress 3ffe::/16%*
To configure any scoped IPv6 address with a specific VLAN, use the following command:
configure log filter myFilter add events all match ipaddress ::/0%Default
NOTE
In the previous example, if you specify the VLAN name, it must be a full match; wild cards are not allowed.
The
<value>
port number, a source MAC address, and a destination MAC address. To allow only those incidents
with a specific source MAC address, use the following in the command:
configure log filter myFilter add events aaa.radius.requestInit secerity notice match
source mac-address 00:01:30:23:C1:00
configure log filter myFilter add events bridge severity notice match source mac-
address 00:01:30:23:C1:00
The string type is used to match a specific string value of an event parameter, such as a user name. A
string can be specified as a simple regular expression.
Match Versus Strict-Match. The
incidents whose event definition does not contain all the parameters specified in a
filter events match
XYZ component, named XYZ.event5, contains a physical port number, a source MAC address, but no
destination MAC address. If you configure a filter to match a source MAC address and a destination
MAC address, XYZ.event5 will match the filter when the source MAC address matches regardless of the
destination MAC address, since the event contains no destination MAC address. If you specify the
strict-match
destination MAC address.
In other words, if the
values in the incident match those in the match criteria, but all parameter types in the match criteria
need not be present in the event definition.
More Information. See the command
To get a listing of the components present in the system, use the following command:
show log components
To get a listing of event condition definitions, use the following command:
show log events
To see the current configuration of a filter, use the following command:
show log configuration filter {<filter name>}
468
depends on the parameter type specified. As an example, an event may contain a physical
match
command. This is best explained with an example. Suppose an event in the
keyword, then the filter will never match, since XYZ.event5 does not contain the
keyword is specified, an incident will pass a filter so long as all parameter
match
show log
and keywords control the filter behavior for
strict-match
on page 532 for more information about severity levels.
configure log
ExtremeWare XOS 11.3 Command Reference