60
Fabric OS Administrator’s Guide
53-1001763-02
Audit log configuration
3
Auditable event classes
Before configuring an audit log, you must select the event classes you want audited. The audit log
includes:
•
SEC-3001 through SEC-3017
•
SEC-3024 through SEC-3029
•
ZONE-3001 through ZONE-3012
Table 7
identifies auditable event classes and the auditCfg command operands used to enable
auditing of a specific class.
NOTE
Only the active CP can generate audit messages because event classes being audited occur only on
the active CP. Audit messages cannot originate from other blades in an enterprise-class platform.
Audit events have the following message format:
AUDIT, <Timestamp>, [<Event ID>], <Severity>, <Event Class>, <User
ID>/<Role>/<IP address>/<Interface>,<Admin Domain>/<Switch name>,/<FID>,
<Reserved>,<Event-specific information>
Switch names are logged for switch components and enterprise-class platform names for
enterprise-class platform components. For example, an enterprise-class platform name may be
FWDL or RAS and a switch component name may be zone, name server, or SNMP.
Pushed messages contain the administrative domain of the entity that generated the event. Refer
to the
Fabric OS Message Reference
for details on message formats. For more information on
setting up the system error log daemon, refer to the
Fabric OS Troubleshooting and Diagnostics
Guide
.
Verifying host syslog prior to configuring the audit log
Audit logging assumes that your syslog is operational and running. Before configuring an audit log,
you must perform the following steps to ensure that the host syslog is operational.
TABLE 7
AuditCfg event class operands
Operand
Event class
Description
1
Zone
Audit zone event configuration changes, but not the actual values that were
changed. For example, a message may state, “Zone configuration has
changed,” but the syslog does not display the actual values that were changed.
2
Security
Audit any user-initiated security events for all management interfaces. For
events that have an impact on an entire fabric, an audit is generated only for
the switch from which the event was initiated.
3
Configuration
Audit configuration downloads of existing SNMP configuration parameters.
Configuration uploads are not audited.
4
Firmware
Audit firmware download start, firmware complete, and any other errors
encountered during a firmware download.
5
Fabric
Audit administrative domain-related changes.
Summary of Contents for 53-1001763-02
Page 1: ...53 1001763 02 13 September 2010 Fabric OS Administrator s Guide Supporting Fabric OS v6 4 0 ...
Page 4: ...iv Fabric OS Administrator s Guide 53 1001763 02 ...
Page 24: ...xxiv Fabric OS Administrator s Guide 53 1001763 02 ...
Page 28: ...xxviii Fabric OS Administrator s Guide 53 1001763 02 ...
Page 32: ...xxxii Fabric OS Administrator s Guide 53 1001763 02 ...
Page 40: ...xl Fabric OS Administrator s Guide 53 1001763 02 ...
Page 42: ...2 Fabric OS Administrator s Guide 53 1001763 02 ...
Page 54: ...14 Fabric OS Administrator s Guide 53 1001763 02 High availability of daemon processes 1 ...
Page 74: ...34 Fabric OS Administrator s Guide 53 1001763 02 Basic connections 2 ...
Page 102: ...62 Fabric OS Administrator s Guide 53 1001763 02 Audit log configuration 3 ...
Page 214: ...174 Fabric OS Administrator s Guide 53 1001763 02 Management interface security 7 ...
Page 228: ...188 Fabric OS Administrator s Guide 53 1001763 02 Brocade configuration form 8 ...
Page 276: ...236 Fabric OS Administrator s Guide 53 1001763 02 Creating a logical fabric using XISLs 10 ...
Page 404: ...364 Fabric OS Administrator s Guide 53 1001763 02 ...
Page 440: ...400 Fabric OS Administrator s Guide 53 1001763 02 Performance data collection 17 ...
Page 480: ...440 Fabric OS Administrator s Guide 53 1001763 02 F_Port masterless trunking 19 ...
Page 494: ...454 Fabric OS Administrator s Guide 53 1001763 02 Buffer credit recovery 20 ...
Page 574: ...534 Fabric OS Administrator s Guide 53 1001763 02 Hexadecimal overview E ...