HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual page 52

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 a Director.
Audit events have the following message format:
AUDIT, <Timestamp>, [<Event ID>], <Severity>, <Event Class>, <User ID>/<Role>/<IP
address>/<Interface>,<Admin Domain>/<Switch name>,<Reserved>,<Event-specific
information>
Switch names are logged for switch components and Director names for Director components. For
example, a Director name may be FWDL or RAS and a switch component name may be zone, name
server, or SNMP.
Pushed messages contain the administration domain of the entity that generated the event. See the Fabric
OS Message Reference for details on message formats. See
page 285 for details on setting up the system error log daemon.
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.
To verify host syslog prior to configuring the audit log:
1. Set up an external host machine with a system message log daemon running to receive the audit events
that will be generated.
2. On the switch where the audit configuration is enabled, enter the syslogdipaddrAdd command to
add the IP address of the host machine so that it can receive the audit events.
You can use IPv4, IPv6, or DNS names for the syslogdipaddrAdd command.
3. Ensure the network is configured with a network connection between the switch and the remote host.
4. Check the host SYSLOG configuration. If all error levels are not configured, you may not see some of
the audit messages.
To configure an audit log for specific event classes:
1. Connect to the switch from which you wish to generate an audit log and log in using an account
assigned to the admin role.
2. Enter the auditCfg
switch:admin> auditcfg --class 2,4
Audit filter is configured.
The auditCfg event class operands are identified in
3. Enter the auditCfg
configured in
switch:admin> auditcfg --enable
Audit filter is enabled.
To disable an audit event configuration, enter the auditCfg
4. Enter the auditCfg
event classes are being audited, and the correct filter state appears (enabled or disabled).
switch:admin> auditcfg --show
Audit filter is enabled.
2-SECURITY
4-FIRMWARE
5. To verify the audit event log setup, make a change affecting an enabled event class, and confirm that
the remote host machine receives the audit event messages.
The following example shows the SYSLOG (system message log) output for audit logging.
Jun 2 08:33:04 [10.32.220.7.2.2] raslogd: AUDIT, 2006/06/02-15:25:53, [SULB-1003],
INFO, FIRMWARE, root/root/NONE/console/CLI, ad_0/ras007_chassis, , Firmwarecommit has
started.
Jun 5 06:45:33 [10.32.220.70.2.2] raslogd: AUDIT, 2006/06/05-13:38:17, [CONF-1010],
INFO, CONFIGURATION, root/root/NONE/
console/CLI, ad_0/ras070, , configDownload failed
52 Standard features
class command, which defines the specific event classes to be filtered.
--
enable command, which enables audit event logging based on the classes
--
step 2.
show command to view the filter configuration and confirm that the correct
--
"Working with Diagnostic
Table 5.
disable command.
--
Features" on