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-1963887.1
Update Date:2017-12-21
Keywords:

Solution Type  Problem Resolution Sure

Solution  1963887.1 :   Synchronizing IMF in NSP CCM Generates this Error: "Unable To Update The Link As Card Number/Port Number has been changed"  


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
Symptoms
Cause
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: This procedure requires cfguser/root access to the servers and access to NSP oracle database
Created from <SR 3-10154847331>

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 6.6.3 to 7.1.2 [Release 6.0 to 7.0]
Information in this document applies to any platform.

Symptoms

When the customer uses the "Synchronize" action in NSP CCM for an IMF subsystem it generates following error:

Error : Unable to update the link as Card Number/Port number has been changed. Please first remove the link and then try to resynchronize. Link Name: stpnum1-msc999-1 , Linkset Name: stpnum1-msc999 , slc: 1

As a result of this error, the link called stpnum1-msc999-1 is not added to the CCM and will not be monitored by the IMF.

Please refer to <document 1910228.1> and apply the procedure described before following to the next steps.

Cause

This error can be generated when an object with the same OID already exists in the NSP oracle database. This object is outdated but has not been erased during the previous synchronize action.

As this obsolete object is still present in the NSP oracle database, the NSP CCM will not be able to add a new link with the same OID. 

Solution

To fix the issue the first step is to identify the old link preventing the new link from being synchronized.

To do this first log onto the master IMF of the subsystem as cfguser and search the Link causing the synchronize error in CcmLink IDB table:

IMF-LAF-1A:/export/home/cfguser igrep -p stpnum1-msc999-1 CcmLink
link_id link_name discovered discovered_name eagle_name short_name description link_oid port_id channel_number number_of_channels status modified_at
1123 stpnum1-1234-1 Yes stpnum1-1234-1 stpnum1-msc999-1 st999999 Discovered by Eagle Provisioner at 01/01/15 01:01:07 .1.3.6.1.4.1.4404.2.1.6.1.1.50332198.50332158.1 1240 0 1 1 01/22/2015 09:24:07

The MO_OID of link stpnum1-msc999-1 is .1.3.6.1.4.1.4404.2.1.6.1.1.50332198.50332158.1.

Log on to NSP Oracle database with sqlplus and search the managed object linked to this MO_OID:

SQL> select MO_ID,MO_CLASS_ID,NAME,MO_OID from cor_managed_object where MO_OID='.1.3.6.1.4.1.4404.2.1.6.1.1.50332198.50332158.1';
  MO_ID MO_CLASS_ID
---------- -----------
NAME
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
MO_OID
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  12345 3
stpnum1-1304-24
.1.3.6.1.4.1.4404.2.1.6.1.1.50332198.50332158.1

On the IMF verify if this link still exists:

IMF-LAF-1A:/export/home/cfguser igrep -p stpnum1-1304-24 CcmLink
link_id link_name discovered discovered_name eagle_name short_name description link_oid port_id channel_number number_of_channels status modified_at
IMF-LAF-1A:/export/home/cfguser

As it is not found on the IMF, it means it's no longer part of the eagle configuration and has to be deleted manually from NSP CCM before the new link can be synchronized.

Log on to NSP GUI navigate the CCM/Network Element and search the link called stpnum1-1304-24, delete it and apply configuration on the IMF.

Synchronize the IMF, the result should now be error free.


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