Matrix ETERNITY NE System Manual 1119
System Fault Log
SARVAM UCS maintains a log of all the system faults. The System Fault Log has a buffer capacity of 500 records.
The Fault Log stores records using the FIFO method.
The System Fault Log can be printed on a local printer or downloaded on a computer in the form of a report. The
report can be printed or downloaded by the System Administrator in two modes:
• Online: The fault report is printed/downloaded as and when a fault occurs.
• Report (Offline): The faulty report is printed/downloaded whenever desired.
The System Administrator can print or download System Activity Log, online or offline.
SARVAM UCS supports Syslog Client for System Fault Logs. The Syslog Client enables the system to send fault
logs in syslog format to the remote Syslog Server. You can view the logs on the remote server.
You can also send notifications for the faults that occur in the system to the concerned person via SMS and/or
Email. For more details, refer to “System Log Notification”.
How it works
• A destination port for sending the report must be selected to which the system can send the log.
• If the System Administrator extension is a Extended IP Phone, a DSS Key can be assigned for System
Fault Log.
• Whenever a fault is detected, the LED of the Fault Log DSS key, if assigned, is turned ON.
• If more than one Extended IP extension is assigned Fault Log DSS Key, the LED of all keys will be turned
ON.
• The System Administrator must acknowledge the Fault indication by pressing the Fault Log key or by
dialing the Fault Log access code. The LED of the Fault Log key is turned OFF.
The following table summarizes the different activities that are logged into system fault log.
Event
Index
Event Description
04 SLT Standby-Open: nnnnnn, Slot=xx, Port=yy When the SLT reaches Open state from the
Stand-by mode, where nnnnnn = max. 6
digit flexible number assinged to SLT, xx =
Slot number and yy = Port number
09 RTC Failure Reserved for future use
10 VoPP Program Download Fail, Slot=xx
Internal failure, DSP fails to load/start for a
particular VoIP module, where xx=slot
number
To Next Page
Loading...
