| 1 | Introduction |
| 1.1 | Alarm Description |
| 1.2 | Prerequisites |
2 | Procedure |
| 2.1 | Analyzing the Alarm |
| 2.2 | Actions for Checking ENUM Logs |
| 2.3 | Actions for Checking ERH and SS7 Stack |
1 Introduction
This instruction concerns alarm handling.
1.1 Alarm Description
This alarm is issued when the percentage of failed NP queries with respect to the total number of NP queries exceeds a configurable threshold.
The possible alarm causes and the corresponding fault reasons, fault locations, and impacts are described in Table 1.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
Solution |
|---|---|---|---|---|---|
|
ERH module load error |
Initialization of ERH module failed when ENUM server is started. |
ERH module is initialized incorrectly. |
ENUM server |
See Section 2.2 | |
|
SS7 stack configuration error or LDAP database connection error. |
SS7 stack is in wrong status or LDAP database has problem or stopped. |
See Section 2.3 |
- Note:
- An alarm can appear as a result of the maintenance activity.
The following is the consequence for the node if the alarm is not solved:
- If the percentage of failed NP queries continuously increase, ENUM server might not provide ERH service properly.
The alarm attributes are listed and explained in Table 2.
|
Attribute Name |
Attribute Value |
|---|---|
|
Major Type |
193 |
|
Minor Type |
856098 |
|
Managed Object Class |
IpworksErhPm |
|
Source |
ManagedElement=<Node Name>,SystemFunctions=1,Pm=1,PmJob=<PM job name, the default job is ERHTPSDefaultJob>,MeasurementReader=<name>:<hostname> |
|
Specific Problem |
|
|
Event Type |
qualityOfServiceAlarm(11) |
|
Probable Cause |
x733ThresholdCrossed(351) |
|
Additional Text |
This alarm is generated when the percentage of failed NP queries with respect to the total number of NP queries exceeds a configurable threshold.;uuid:<Product_UUID>(1) |
|
Perceived Severity |
Warning |
(1) <Product_UUID> is the universally unique
identifier (UUID) of machine that generates the alarm. The value can
be fetched from /sys/devices/virtual/dmi/id/product_uuid on the PL node.
1.2 Prerequisites
This section provides information on the documents, tools, and conditions that apply to the procedure.
1.2.1 Documents
This instruction references the following document:
1.2.2 Tools
Before starting this procedure, ensure that the following tool is available:
1.2.3 Conditions
No conditions.
2 Procedure
This section describes the procedure to follow when this alarm is received.
2.1 Analyzing the Alarm
Do the following at the maintenance center:
2.2 Actions for Checking ENUM Logs
Do the following:
- Log on to an SC or PL.
- Open ENUM log to check if the ERH module initialization
is successful. A successful log resembles the following:
../ProtocolServer.cpp:991 InitialAINHandle. NP(AIN) Info Data is Initializing ... ../NPHandler.cpp:448 initTimerModule. Init the Timer Module now. ../NPHandler.cpp:550 CreateMultiWorkingThread. Init the MultiWorking Thread to receive the ERH Data now. ../ProtocolServer.cpp:1001 InitialAINHandle. NP(AIN) Info Data Initialization is finished ... ../ProtocolServer.cpp:1006 InitialMAPHandle. NP(MAP) Info Data is Initializing ... ../NPHandler.cpp:448 initTimerModule. Init the Timer Module now. ../NPHandler.cpp:550 CreateMultiWorkingThread. Init the MultiWorking Thread to receive the ERH Data now. ../ProtocolServer.cpp:1015 InitialMAPHandle. NP(MAP) Info Data Initialization is finished ... ../ProtocolServer.cpp:1020 InitialINAPHandle. NP(INAP) Info Data is Initializing ... ../NPHandler.cpp:448 initTimerModule. Init the Timer Module now. ../NPHandler.cpp:550 CreateMultiWorkingThread. Init the MultiWorking Thread to receive the ERH Data now. ../ProtocolServer.cpp:1030 InitialINAPHandle. NP(INAP) Info Data Initialization is finished ...
- If the actual output is not like the above example, consult the next level of maintenance support.
2.3 Actions for Checking ERH and SS7 Stack
Do the following:
- In IPWorks CLI, check the fields LocalSSN and LocalSPC of the AINNode, MAPNode, and INAPNode objects.
- Note:
- The value of fields LocalSSN and LocalSPC must be consistent with the configuration of SS7 stack.
- If the configuration is inconsistent, correct the configuration
of the objects.
- Note:
- The operator can either change the configuration of the objects
in IPWorks CLI or change the configuration of SS7 stack in Signaling
Manager to keep the configuration consistent.
For information on how to configuration SS7 stack, refer to Configure SS7 for ENUM Number Portability.
- Set the NPSwitch field of AINNode, MAPNode, and INAPNode to 0, and wait for ENUM to unload the ERH module.
- Set the NPSwitch field of AINNode, MAPNode, and INAPNode to 1, then try the query again.
- Check the status of SS7 stack.
For information on how to check SS7 stack, refer to the section Verifying Stack Configuration in Configure SS7 for ENUM Number Portability.
- Check whether the LDAP feature is enabled, if not, enable
it in ECLI.
For example:
>ManagedElement=<Node Name>,IpworksFunction=1,IpworksDnsRoot=1,IpworksEnumRoot=1,EnumServer=2,Erh=1
(Erh=1)>show -v
Erh=1 discardErhFailure=false <default> erhId="1" ldap=false <default> nxdomainForNonPortedNumber=true <default> rcseInterConnect=false <default> teTimer=30 <default> ErhLdap=1 ErhSs7=1
(Erh=1)>configure
(config-Erh=1)>ldap=true
(config-Erh=1)>commit
- If the query is not sent to the NPDB by the LDAP protocol,
check the configuration of EnumDnRange in
IPWorks CLI.
For example:
IPWorks> list enumdnrange
[EnumDNRange 50 8652] enumZoneId: 50 viewId: 0 enumDnRange: 8652 scope: destNode: ldap updateLevel: 0 Working on 1 object(s).
The expected result is that the value of destNode must be ldap when the EnumDnRange is configured for the NP by the LDAP protocol.
- Confirm that the alarm has ceased. If the alarm remains, consult the next level of maintenance support. Further actions are outside the scope of this instruction.

Contents