The SPID Updates For iConectiv Spid Migration are Updated on LSMS only but not Pushed to ELAP and Eagle

Asset ID:	1-71-2369960.1
Update Date:	2018-03-09
Keywords:

Solution Type Technical Instruction Sure

Solution 2369960.1 : The SPID Updates For iConectiv Spid Migration are Updated on LSMS only but not Pushed to ELAP and Eagle

Applies to:

Oracle Communications EAGLE (Software) - Version LSMS 13.3 and later
Information in this document applies to any platform.

Goal

Performing spid migration with iConectiv. We stopped npaagent, eagle agent and sup, ran the massupdate with the SMURF file generated by iConnectiv.

massupdate -n Region SMURF_file

rw-r----- 1 lsmsadm root 42 Feb 26 15:11 SIC-SMURF-LRN.T220.T830.25-02-2018060201
-rw-r----- 1 lsmsadm root 34 Feb 26 15:11 SIC-SMURF-NPANXX.T220.T830.25-02-2018060201
-rw-r----- 1 lsmsadm root 36 Feb 26 15:11 SIC-SMURF-NPANXXX.T220.T830.25-02-2018060201

After runing the massupdate, and starting npacagents, eagle agents and sup, the data (TN, LRN, ect ) in LSMS changed with the new SPID which is what we expected, but ELAP and STP still show the old SPID.

How can this update ELAP and STP.

Solution

The SPID doesn't get audited, but other values are.

Per Chapter 5 in the guide below. Need to load servdi/bulkload to update ELAP and Eagle with the new SPID (but not necessary) as the information you need for routing are correct.

LNP Database Synchronization User's Guide

Attachments

This solution has no attachment