Users Guide

Fabric OS Administrator’s Guide 107
53-1002920-02
Audit log configuration
3
Example output from a switch
The following example displays what is typically seen from a Brocade switch, but the quantity and
types vary by platform.
switch:admin> switchstatuspolicyshow
To change the overall switch status policy parameters
The current overall switch status policy parameters:
Down Marginal
-----------------------------------
PowerSupplies 2 1
Temperatures 2 1
Fans 2 1
Flash 0 1
MarginalPorts 25.00%[12] 10.00%[5]
FaultyPorts 25.00%[12] 10.00%[5]
MissingSFPs 0.00%[0] 0.00%[0]
ErrorPorts 0.00%[0] 0.00%[0]
Number of ports: 48
Note that the value, 0, for a parameter, means that it is
NOT used in the calculation.
** In addition, if the range of settable values in the prompt is (0..0),
** the policy parameter is NOT applicable to the switch.
** Simply hit the Return key.
The minimum number of
Bad PowerSupplies contributing to DOWN status: (0..2) [2]
Bad PowerSupplies contributing to MARGINAL status: (0..2) [1]
Bad Temperatures contributing to DOWN status: (0..4) [2]1
Bad Temperatures contributing to MARGINAL status: (0..4) [1]2
Bad Fans contributing to DOWN status: (0..2) [2]
Bad Fans contributing to MARGINAL status: (0..2) [1]
(output truncated)
NOTE
On the Brocade Backbones, the command output includes parameters related to CP blades.
Audit log configuration
When managing SANs, you may want to audit certain classes of events to ensure that you can view
and generate an audit log for what is happening on a switch, particularly for security-related event
changes. These events include login failures, zone configuration changes, firmware downloads,
and other configuration changes; in other words, critical changes that have a serious effect on the
operation and security of the switch.
Important information related to event classes is also tracked and made available. For example,
you can track changes from an external source by the user name, IP address, or type of
management interface used to access the switch.