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-1911509.1
Update Date:2015-08-20
Keywords:

Solution Type  Technical Instruction Sure

Solution  1911509.1 :   Understand and Mitigate "TKPIC26086: NSP Host Configuration" Alarms ?  


Related Items
  • Oracle Communications Performance Intelligence Center (PIC) Software
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
  •  




In this Document
Goal
Solution


Created from <SR 3-9172882584>

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 9.0.3 and later
Information in this document applies to any platform.

Goal

How to determine the origin of 'TKPIC26086: NSP Host Configuration' alarms and mitigate them ?

Solution

Alarms with specific problem 'TKPIC26086: NSP Host Configuration' are alarms received by the NSP with a managed Object ID unknown to the NSP configuration.

To find the origin of the alarms, events attached to the alarm must be reviewed with ProAlarm Viewer and SysAlarm.

These events can originate from different equipments/elements. To differentiate them "Additional text" field can be used: It usually contains the name of the element or its OID and will allow you to analyse why this source is generating an alarm and then you can investigate why the alarm is not recognized by NSP.

The most common cause is a new network element configured on Eagle STP (Link, LinkSet, Signaling Point...) that was not discovered in CCM.

In this case, the first action will be to make sure the IMFs have been properly synchronized in CCM after the eagle STP configuration was changed.
 


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