Configuring The Audit Log - HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual

Hp storageworks fabric os 6.1.1 administrator guide (5697-0235, december 2009)
Hide thumbs Also See for A7533A - Brocade 4Gb SAN Switch Base:
Table of Contents

Advertisement

HP StorageWorks 4/8 SAN Switch and 4/16 SAN Switch, 8/8 SAN Switch, 8/24 SAN Switch, 8/40
SAN Switch, 8/80 SAN Switch, Brocade 4Gb SAN Switch for HP p-Class BladeSystem, Brocade 4Gb
SAN Switch for HP c-Class BladeSystem, SAN Switch 4/32, 4/64 SAN Switch, SAN Switch 4/32B, 400
Multi-protocol Router:
switch:admin> switchstatuspolicyset
To change the overall switch status policy parameters
The current overall switch status policy parameters:
----------------------------------
PowerSupplies
Temperatures
MarginalPorts
FaultyPorts
MissingSFPs
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.
Bad PowerSupplies contributing to DOWN status: (0..2) [2] 0
Bad PowerSupplies contributing to MARGINAL status: (0..2) [1] 0
Bad Temperatures contributing to DOWN status: (0..6) [2] 0
Bad Temperatures contributing to MARGINAL status: (0..6) [1] 0
Bad Fans contributing to DOWN status: (0..3) [2] 0
Bad Fans contributing to MARGINAL status: (0..3) [1] 0
Out of range Flash contributing to DOWN status: (0..1) [0] 0
Out of range Flash contributing to MARGINAL status: (0..1) [1] 0
MarginalPorts contributing to DOWN status: (0..32) [2] 0
MarginalPorts contributing to MARGINAL status: (0..32) [1] 0
FaultyPorts contributing to DOWN status: (0..32) [2] 0
FaultyPorts contributing to MARGINAL status: (0..32) [1] 0
MissingSFPs contributing to DOWN status: (0..32) [0] 0
MissingSFPs contributing to MARGINAL status: (0..32) [0] 0
Policy parameter set has been changed
rint12:admin>
4/256 SAN Director and DC SAN Backbone Director (short name, DC Director): Command output includes
parameters related to CP blades.

Configuring the audit log

When managing SANs, you may want to filter, or 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 if you are running a Fabric OS version earlier than 6.x. 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.
Auditable events are generated by the switch and streamed to an external host through a configured
system message log daemon (syslog). You specify a filter on the output to select the event classes that are
sent through the system message log. The filtered events are streamed chronologically and sent to the
Down
Marginal
2
2
Fans
2
Flash
0
2
2
0
1
1
1
1
1
1
0
Fabric OS 6.1.1 administrator guide
51

Advertisement

Table of Contents
loading

Table of Contents