EAGLE5 STP - How To Handle UAM-0285 LNP Ported NPAs Approaching Feat. Cap

Asset ID:	1-72-2381832.1
Update Date:	2018-04-03
Keywords:

Solution Type Problem Resolution Sure

Solution 2381832.1 : EAGLE5 STP - How To Handle UAM-0285 LNP Ported NPAs Approaching Feat. Cap

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 46.0 and later
Tekelec

Symptoms

Eagle STP starts reporting UAM-285- LNP Ported NPAs Approaching Feat. Cap. after system upgrade

8012.0285 ** LNP SYSTEM LNP Ported NPAs approaching Feat. Cap.
****18-03-02 09:41:29****
8011.0426 LNP SYSTEM LNP Subsystem is available
****18-03-02 09:41:29****
8010.0285 ** LNP SYSTEM LNP Ported NPAs approaching Feat. Cap.
****18-03-02 09:41:28****
8008.0426 LNP SYSTEM LNP Subsystem is available"

Changes

Customer upgraded the Eagle from R44.0.4 to R46.0.3

Cause

The alarm is triggered when the number of LNP ported NPANXXs is greater than the capacity this feature supports.
This UAM appears when the DSMVSCCP cards are cold-restarted after the ELAPRTDBs were pre-populated offline with NPANXX totals that exceed the NPANXX Quantity Feature keys capacities that are currently configured for the EAGLE 5.

Verify the system’s status by comparing the provisioned table quantity with the number of NPANXXs specified by the feature.

1. Enter the following command to verify the quantity of NPANXXs specified for this system: rtrv-ctrl-feat
EagleSTP 18-03-01 10:42:45 EST EAGLE5 46.0.3-65.26.29
The following features have been permanently enabled:

Feature Name Partnum Status Quantity
LNP ported NPANXXs 893009403 on 350000

2. Enter the following command in order to generate a report of the local number portability (LNP) status information: rept-stat-lnp

PROVISIONED TABLE QTY:
TN: 355910837 of 384000000 ( 92%)
NPA: 316080 of 350000 ( 90%)
LRN: 36807 of 200000 ( 18%)

By comparing the provisioned NPA quantity with the capacity the feature supports we validate the alarm and confirm if it is correctly triggered.

Solution

In the example above the number of LNP ported NPAs reached 90.31% of the capacity. This correctly triggers UAM 0285. The only way to solve the alarm is by increasing the capacity or by reducing the number of NPANXXs.

In the unlikely case that the alarm reporting is not confirmed by the rept-stat-lnp output, the alarm could be fake. Only in this case consider an MDAL and MASP reset:

Remove the USBs from both MASP cards, if they are inserted. Make sure no USBs are inserted in any of the MASP cards in the system.
Remove MDAL card on location 1117 from the system.
Wait 3 minutes to insert back MDAL card. Verify E5-MDAL card status using rept-stat-card:loc=1117 command confirming E5-MDAL card is in IS-NR state.
Verify status for both MASP cards by using rept-stat-card:appl=oam command. Make sure no GPL Alarms are present on the E5-MASP Cards.
To switchover the MASP card identify active MASP Card location from step-4
Execute init-card:loc=xxxx command for MASP switchover; xxxx is the active masp card location.
Wait for 5 to 10 min. to get both the MASP in IS-NR state. This can be verified by using rept-stat-card:appl=oam command.
Once the Eagle is in duplex mode check if the alarm 0285 "LNP Ported NPAs approaching Feat. Cap." is cleared using: rept-stat-trbl:display=timestamp.
To activate the initial MASP, execute init-card:loc=xxxx on the active MASP the second time
Check the alarm status at the end

NOTE: during the MASP switchover the current users will be logged out momentarily.

Attachments

This solution has no attachment