Database change events, Log events, Inventory events – Nortel Networks OPTera Metro 3500 User Manual
Page 212
2-174 Operation, administration, and maintenance (OAM) features
OPTera Metro 3500 Multiservice Platform NTRN10AN Rel 12.1 Standard Iss 1 Apr 2004
Database change events
Database change events (DBCHG events) result only in the case of
successfully completed commands. DBCHG events include the following
information:
•
User ID of the person who entered the command (alphanumeric string up
to 20 characters in length)
•
Command identifier (for example, ENT-CRS-VT1)
•
AID(s) that were acted upon (if applicable)
•
CTAG
•
Position defined parameters from the command
•
Keyword defined parameters from the command
•
Primary and secondary states from the command
Log events
Log events result after either of the following occurs:
•
a TL1 command is unsuccessful (TL1 return code is not COMPLD)
•
a TL1 command is attempted, regardless of success or failure, with an
account of UPC 4 or higher
Note: Retrieval command (RTRV) from a UPC account of 3 or lower does
not result in a log event
Log events include the following information:
•
User ID of the person who entered the command (alphanumeric string up
to 20 characters in length)
•
Priority
•
Status of the command
•
Command identifier (for example, ENT-CRS-VT1)
•
AID(s) that were acted upon (if applicable)
•
CTAG
•
Position defined parameters from the command
•
Keyword defined parameters from the command
•
Primary and secondary state parameters from the command
•
Failure string
Inventory events
Inventory events are generated and displayed when inventory changes (for
example, pulling or inserting circuit packs) occur.