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-71-2365607.1
Update Date:2018-02-27
Keywords:

Solution Type  Technical Instruction Sure

Solution  2365607.1 :   HLR Router (HLRR) : All Connections Down from MP's  


Related Items
  • Tekelec HLR Router
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
  •  




In this Document
Goal
Solution


Created from <SR 3-16173898784>

Applies to:

Tekelec HLR Router - Version HLRR 4.0 to HLRR 4.0 [Release HLRR 4.0]
Tekelec

Goal

 All Connections down from MP's of HLR Router (HLRR)

Solution

On investigation it was found that for the XSI interfaces i.e. eth02 and eth04, IP's were not there from MP's, It was also verified from NOAM GUI : Main Menu :Configuration =>Network=>Devices : Under this for MP's , it was observed eth02 and eth04 were in DEPLOYED state..

There are various scenario when devices are configured differently :
1. When the Devices are configured from NOAM GUI they appear as "Configured".
2. When the Devices are configured manually on the MP server (through netAdm) they appear as "Discovered".
3. When the Device information is present in the server (i.e. NOAM) and the device is also manually configured in the Server (i.e. MP) it appear as "Deployed".

In this case the devices were manually configured using netAdm commands that is why they appear as Discovered as configuration information was not in the DB. Since there was no Network(XSI) associated with these devices so System has considered the IP addresses as DHCP assigned IP. So, When "Take Ownership" was done, then IP addressed were lost as they were considered to be DHCP assigned.

Following action can be done to restore this:

1) The audits on the MP's were stopped (the soap server was halted on the MP's) using " pm.set off apwSoapServer " command .
2) The network information was manually recreated (using the platcfg tools) for eth02 and eth04.
3) Added the route back towards the destinations using platcfg tools.
4) Performed the EXHR process restart on each MP's once configuration completed using platcfg tool.
5) At this point of time, we had restored the situation but the eth02 and eth04 were still in deployed state.
6) We connected to the MP CLI and manually removed the existing entries from ResourceAudit.0 table for eth02 and eth04.
7) We went to Active NOAM CLI and removed the entries for related MP's interface eth02 and eth04 from NetworkDevice and NetworkDeviceOption table.
8) At the end we started the audits on the MP using "pm.set off apwSoapServer" command and this audit took the eth02 and eth04 as discovered device into NOAM GUI.

Note : It is recommended to inform Oracle TAC when such issue triggered and let Oracle TAC to execute the recovery procedure.

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