Status Monitoring and Statistics
ExtremeWare XOS 11.1 Concepts Guide
140
incidents, of severity
notice
and above, with a specific source MAC address, use the following
command:
configure log filter myFilter add events aaa.radius.requestInit 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
match
and
strict-match
keywords control the filter behavior for
those incidents with event definition that does not contain all the parameters specified in a
configure
log filter events match
command.
This is best explained with an example. Suppose an event in the
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
because the event contains no destination MAC address. If you specify the
strict-match
keyword,
then the filter will never match event
XYZ.event5
because this event does not contain the destination
MAC address.
In other words, if the
match
keyword is specified, an incident will pass a filter so long as all parameter
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.
Formatting Event Messages
Event messages are made up of a number of items. The individual items can be formatted; however,
EMS does not allow you to vary the
order
of the items. To format the messages for a particular target,
use the following command:
configure log target [console | memory-buffer | nvram | session | syslog [all |
<ipaddress> | <ipPort>] {vr <vr_name>} {local0 ... local7}]] format [timestamp
[seconds | hundredths | none] | date [dd-mm-yyyy | dd-Mmm-yyyy | mm-dd-yyyy | Mmm-dd |
yyyy-mm-dd | none] | severity
| event-name [component | condition | none |
subcomponent] | host-name | priority | process-name | process-slot | source-line
Using the default format for the session target, an example log message might appear as:
06/25/2004 22:49:10.63 <Info:dm.Info> MSM-A: PowerSupply:4 Powered On
If you set the current session format using the following command:
configure log target session format timestamp seconds date mm-dd-yyyy event-name
component
The same example would appear as:
06/25/2004 22:49:10 <dm> PowerSupply:4 Powered On
To provide some detailed information to technical support, set the current session format using the
following command:
configure log target session format timestamp hundredths date mmm-dd event-name
condition process-name source-line
Содержание ExtremeWare XOS 11.1
Страница 16: ...Contents ExtremeWare XOS 11 1 Concepts Guide 16...
Страница 20: ...Preface ExtremeWare XOS 11 1 Concepts Guide 20...
Страница 21: ...1 Using ExtremeWare XOS...
Страница 22: ......
Страница 78: ...Managing the ExtremeWare XOS Software ExtremeWare XOS 11 1 Concepts Guide 78...
Страница 168: ...Virtual LANs ExtremeWare XOS 11 1 Concepts Guide 168...
Страница 200: ...Policies and ACLs ExtremeWare XOS 11 1 Concepts Guide 200...
Страница 252: ...Security ExtremeWare XOS 11 1 Concepts Guide 252...
Страница 265: ...2 Using Switching and Routing Protocols...
Страница 266: ......
Страница 294: ...Ethernet Automatic Protection Switching ExtremeWare XOS 11 1 Concepts Guide 294...
Страница 354: ...Extreme Standby Router Protocol ExtremeWare XOS 11 1 Concepts Guide 354...
Страница 416: ...IP Multicast Routing ExtremeWare XOS 11 1 Concepts Guide 416...
Страница 417: ...3 Appendixes...
Страница 418: ......
Страница 432: ...Software Upgrade and Boot Options ExtremeWare XOS 11 1 Concepts Guide 432...