Technical data

Network OS Message Reference 11

53-1002489-01

Reading the system messages

2. Configure the event classes you want to audit. For example, to audit the CONFIGURATON class,

execute the following command.

switch# logging auditlog class

Possible completions:

CONFIGURATION FIRMWARE SECURITY

switch# logging auditlog class CONFIGURATION

3. Execute the show running-config logging auditlog command to verify the configuration.

switch# show running-config logging auditlog

logging auditlog class CONFIGURATION

Reading the system messages

This section provides information about reading the system messages.

RAS system messages

The following example shows the format of the RAS system error message.

<Timestamp>, [<Event ID>], <Sequence Number>, <Flags>,<Severity>,<Switch name>,

<Event-specific information>

The following example shows the sample messages from the error log.

2011/08/23-22:58:10, [IPAD-1000], 2,, INFO, VDX6720-24, SW/0 Ether/0 IPv4 DHCP

10.24.95.252/20 DHCP On.

2011/08/26-12:39:02, [HAM-1007], 2, FFDC, CRITICAL, VDX6720-24, Need to reboot the

system for recovery, reason: raslog-test-string0123456-raslog.

2011/08/26-12:40:01, [VCS-1003], 7013/3454, VCS, INFO, VDX6720-60, Event: VCS

node add, Coordinator IP: 10.17.10.31, VCS ID: 1, Status: rBridge ID 1

(10.17.10.32) added to VCS cluster., VcsFabAddRejoin, line: 1450, comp:dcmd,

ltime:2011/06/27-02:47:04:555942.

The fields in the error message are described in Table 4.

TABLE 4 System message field description

Variable name Description

Timestamp The system time (UTC) when the message was generated on the switch. The RASLog

subsystem supports an internationalized time stamp format base on the “LOCAL” setting.

Event ID The Event ID is the message module and number. These values uniquely identify each

message in the Network OS and reference the cause and actions recommended in this

manual. Note that not all message numbers are used; there can be gaps in the numeric

message sequence.

Sequence Number The error message position in the log. When a new message is added to the log, this number

is incremented by 1.

The message sequence number starts at 1 after a firmware download and increases up to a

value of 2,147,483,647 (0x7ffffff).

The sequence number continues to increase after the message log wraps around, i.e. the

oldest message in the log is deleted when a new message is added. The sequence number

can be reset to 1 using the clear logging raslog command. The sequence number is

persistent across power cycles and switch reboots.