Cisco MCS-7825-H3-IPC1 Service Manual page 191

Chapter 5 Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts
Table 5-34 Cisco SIP Normalization (continued)
Display Name
DeviceResetManually
ErrorExecution
ErrorInit
ErrorInternal
OL-22523-01
Description
This counter indicates the number of times that the device (SIP trunk) is reset
manually in Cisco Unified Communications Manager Administration or by other
methods, such as AXL. When the device associated with a script is reset due to
configuration changes, the counter value increments.
The counter restarts when:
• The SIP trunk is deleted.
• The script on the trunk gets changed or deleted.
Cisco Unified Communications Manager restarts.
•
This counter represents the number of execution errors that occurred while the
script executed. Execution errors can occur while a message handler executes.
Execution errors can be caused by resource errors, an argument mismatch in a
function call, and so on.
When an execution error occurs, Cisco Unified CM performs the following actions:
• Automatically restores the message to the original content before applying
additional error handling actions.
Increments the value of the counter.
•
• Takes appropriate action based on the configuration of the Script Execution
Error Recovery Action and System Resource Error Recovery Action fields in
Cisco Unified Communications Manager Administration.
Check the SIPNormalizationScriptError alarm for details, including the line number
in the script that failed. Correct the script problem, upload the corrected script as
needed, and reset the trunk. This counter increments every time an execution error
occurs. This counter provides a count from the most recent trunk reset that involved
a script configuration change. (A device reset alone does not restart the count; the
script configuration must also change before the reset occurs.)
If the counter continues to increment after you fix the script problem, examine the
script again.
This counter represents the number of times a script error occurred after the script
successfully loaded into memory, but failed to initialize in Cisco Unified CM. A
script can fail to initialize due to resource errors, an argument mismatch in a
function call, the expected table was not returned, and so on.
Check the SIPNormalizationScriptError alarm for details, including the line number
in the script that failed. Correct the script problem, upload the corrected script as
needed, and reset the trunk. This counter increments every time an initialization
error occurs. This counter provides a count from the most recent trunk reset that was
accompanied by a script configuration change. (A device reset alone does not restart
the count; the script configuration must also change before the reset occurs.) If the
counter continues to increment after you fix the script problem, examine the script
again. When the error occurs during initialization, Cisco Unified CM automatically
disables the script.
This counter indicates the number of internal errors that occurred while the script
executed. Internal errors are very rare. If the value in this counter is higher than
zero, a defect exists in the system that is not related to the script content or
execution. Collect SDI traces and contact the Technical Assistance Center (TAC).
Cisco Unified Communications Manager Managed Services Guide
Performance Monitoring in RTMT
5-37