Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2090015.1
Update Date:2017-02-23
Keywords:

Solution Type  Problem Resolution Sure

Solution  2090015.1 :   Eagle Release 44 :: DSM Card Is Not Coming Up RTDB Reload Required  


Related Items
  • Oracle Communications EAGLE (Hardware)
  •  
  • Oracle Communications EAGLE (Hardware)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec Eagle 5
  •  




In this Document
Symptoms
Cause
Solution


Created from <SR 3-11831416066>

Applies to:

Oracle Communications EAGLE (Hardware) - Version EAGLE 3x.x to EAGLE 44.x [Release EAGLE 3x.0 to EAGLE 44.0]
Oracle Communications EAGLE (Hardware) - Version EPAP 14.0 to EPAP 14.0 [Release EPAP 14.0]
Tekelec

Symptoms

On : EAGLE 44.0.4-64.34.24 version, Eagle 5 - STP (Hardware)

DSM Card is not coming up

ERROR
-----------------------
Rept-stat-mps shows RTDB reload required for all the DSM cards:
ALARM STATUS = ** 0451 RTDB reload is required

Also;
Rept-stat-sccp shows that the the DSM cards have:
SST=DB_DIFF


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. EAGLE Release 44 or below
2. EPAP Release 15 with feature: "EIR_BLK_EXPANSION_100K"
3. This EPAP feature works with Eagle Release 45 or above. As customer's Eagle release is 44; the feature did not work and once the EIR size increased above 50,000; it caused issues in RTDB which could not be loaded to the DSM

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, new MNP/EIR information cannot be updated to DSM cards.
If this condition remains for an extended period of time; DSM cards will have old RTDB information which will mean that subscribers with newly changed statuses will be unable to make successful calls.

Cause

The issue is caused by the following setup:
• EAGLE 44.0.4-64.34.24 version
• Prior to upgrading the EPAPs to R 15.0, customer was optimizing the IMEI block provisioning to keep IMEI blocks below 50K mark.
• After upgrading to R 15.0 , "EIR_BLK_EXPANSION_100K" feature was enabled. At this point customer stopped optimizing the provisioning of IMEI block keeping in mind that the feature is turned ON.
• The IMEI block level needs to be maintained below 50K till EAGLE sites are upgraded to R 45.0 or above.
 
Reference to Oracle Communications EAGLE Application Processor Feature Notice Release 15.0
Table 1: Compatibility Matrix EPAP 15.0 on E5-APP-B cards:
EAGLE 5 44.0 is Partially Compatible (PC*/**)

** Partially Compatible: EIR Expansion of IMEI Block from 50K to 100k will not be available until the EAGLE 5 is upgraded to Release 45.0 or higher.
 

Solution

Provisioning has to be stopped before the start of the activity.

  1. Check the DB levels in both active PDBA and standby PDBA servers and make sure the IMEI blocks count is below 50K. ( Do not proceed further if the IMEI blocks count has reached 50K )
  2. STOP the EPAP software in Active PDBA server.
  3. STOP the PDBA software in Active PDBA server.
  4. Reload RTDB from PDBA in standby PDBA server ( EPAP A)
  5. Take RTDB backup in standby PDBA server ( EPAP A)
  6. Transfer the RTDB backup file to free directory (/var/TKLC/appl/free) of EPAP A.
  7. Restore the RTDB of EPAP A from the transferred backup file.
  8. Reload the RTDB of EPAP B from EPAP A
  9. Reboot DSM cards of STP one after the other.
  10. Make sure the standby PDBA server is not in forced standby state. ( This is because the server will be put to forced standby state when RTDB reload from PDBA is attempted)
  11. START the PDBA software in active PDBA server
  12. START the EPAP software in active PDBA server
  13. Customer can start the provisioning
  14. Verify the provisioning updates in EPAP RTDBs and DSM cards.

Note:-
1) Customer should be very careful and make sure the IMEI blocks stays below 50K until other sites are upgraded to Release 45.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback