![Cisco BTS 10200 Softswitch Скачать руководство пользователя страница 508](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550508.webp)
10-140
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Troubleshooting Signaling Alarms
Insufficient Heap Memory—Signaling (81)
The Insufficient Heap Memory alarm (critical) indicates that there is insufficient heap memory. The
primary cause of the alarm is that the H323 signaling adapter was unable to allocate memory from the
system. To correct the primary cause of the alarm, contact Cisco TAC for assistance.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
for
detailed instructions on contacting Cisco TAC and opening a service request.
Insufficient Shared Memory Pools—Signaling (82)
The Insufficient Shared Memory Pools alarm (critical) indicates that there is insufficient shared memory
pools. The primary cause of the alarm is that the H323 signaling adapter was unable to allocate storage.
To correct the primary cause of the alarm, contact Cisco TAC for corrective action.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
for
detailed instructions on contacting Cisco TAC and opening a service request.
Error While Binding to Socket—Signaling (83)
The Error While Binding to Socket alarm (critical) indicates that an error occurred while binding to the
socket. To correct the primary cause of the alarm, contact Cisco TAC for corrective action.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
for
detailed instructions on contacting Cisco TAC and opening a service request.
Reached Maximum Socket Limit—Signaling (84)
The Reached Maximum Socket Limit alarm (critical) indicates that the BTS 10200 system has reached
the maximum socket limit. The primary cause of the alarm is that the configuration setting of an H3A
parameter in the platform.cfg file is wrong. To correct the primary cause of the alarm, reconfigure the
platform.cfg file and restart the H3A process.
Initialization Failure—Signaling (85)
The Initialization Failure alarm (critical) indicates that the BTS 10200 system failed to initialize. The
primary cause of the alarm that a process initialization failure has occurred. To correct the primary cause
of the alarm, check “Reason” dataword for the failure cause and take action accordingly.