13-16
Cisco ONS 15454 SDH Reference Manual, R5.0
April 2008
Chapter13 Alarm Monitoring and Management
13.9 Audit Trail
–
Virtual wire entities—You can provision an alarm that is input to a virtual wire to trigger an
external control output.
13.9 Audit Trail
The ONS 15454 SDH maintains an audit trail log that resides on the TCC2/TCC2P. This record shows
who has accessed the system and what operations were performed during a given time period. The log
includes authorized Cisco logins and logouts using the operating system command line interface, Cisco
Transport Controller (CTC), and TL1; the log also includes FTP actions, circuit creation/de letion, and
user/system generated actions.
Event monitoring is also recorded in the audit log. An event is defined as the change in status of an
element within the network. External events, internal events, attribute changes, and software
upload/download activities are recorded in the audit trail.
Audit trails are useful for maintaining security, recovering lost transactions and enforcing accountability.
Accountability is the ability to trace user activities by associating a process or action with a specific user.
To view the audit trail log, refer to the Cisco ONS 15454 SDH Procedure Guide. to view the audit trail
record. Any management interface (CTC, CTM, TL1) can access the audit trail logs.
The audit trail is stored in persistent memory and is not corrupted by processor switches, resets or
upgrades. However, if the TCC2/TCC2Ps are removed, the audit trail log is lost.

13.9.1 Audit Trail Log Entries

Audit trail records capture the following activities:
•User—Name of the user performing the action
•Host—Host from where the activity is logged
•Device ID—IP address of the device involved in the activity
•Application—Name of the application involved in the activity
•Task—Name of the task involved in the activity (View a dialog, apply configuration and so on)
•Connection Mode—Telnet, Console, SNMP
•Category—Type of change; Hardware, Software, Configuration
•Status—Status of the user action (Read, Initial, Successful, Timeout, Failed)
•Time—Time of change
•Message Type—Denotes if the event is Success/Failure type
•Message Details—A description of the change

13.9.2 Audit Trail Capacities

The system is able to store 640 log entries.When this limit is reached, the oldest entries are overwritten
with new events.
When the log server is 80 percent full, an AUD-LOG-LOW condition is raised and logged (by way of
CORBA/CTC).