Reconnecting Network Elements Procedures

Perform the following procedure:

At the source LSMS, log in as lsmsadm on the active server.

Enter the following command to display the status of all eagleagent processes: eagle status

Scan the output for the names of all active EAGLE agents, similar to the values shown in bold in the following example:

CLLI        Pid   State       Resync        Conn A  Conn B  DCM     EBDA    Debug Queue  
Memory  CPU  Timestamp 1190801
     13622 A_ACTIVE    COMPLETE      ACTIVE  STANDBY NONE    IDLE     OFF    0 %   71
M  0.1 % 13:00:40

At the source LSMS, for each EAGLE agent process that is running, enter the following command to stop the EAGLE agent processes (<CLLI> is the Common Language Location Identifier for the EAGLE node):
$LSMS_DIR/eagle stop <CLLI>
For the example shown in step 2, you would enter the following commands:

$LSMS_DIR/eagle stop 1190801
At the destination LSMS, for each network element serviced by the LSMS, do one of the following:
- In an inactive shadow configuration, create the EMS for the given network element (refer to the Configuration Guide, “Creating an EMS Configuration Component”). When you finish creating the EMS, sentryd process automatically starts the Eagle agent.
- In an active shadow configuration, modify the EMS for the given network element (refer to the Configuration Guide, “Modifying an EMS Configuration Component”). Next, stop and restart the Eagle agent for the given CLLI using the following commands, then go to “Automatic Resyncronization after Reconnect”.
  $LSMS_DIR/eagle stop <CLLI>
  
  $LSMS_DIR/eagle start <CLLI>
Next, the LSMS and the network elements will automatically resynchronize as described in “Automatic Resyncronization after Reconnect”.

Automatic Resyncronization after Reconnect

When the LSMS and MPS are reconnected, the LSMS automatically starts an automatic resynchronization of the databases. For more information, see “Automatic Resynchronization Process” in the LNP Database Synchronization User's Guide. If the LSMS cannot complete automatic resynchronization, it posts a notification to the LSMS GUI. For more information, refer to “Notifications that Database Maintenance Is Required” in the LNP Database Synchronization User's Guide.

If the Surveillance feature is active, the following Surveillance notification is also posted, where <Host Name> is the hostname and <CLLI> is the 11-character CLLI code of the network element:

LSMS8001|14:58 Jul 22, 1997|<Host Name>|Notify:Sys Admin - NE CLLI=<CLLI>