| Troubleshoot reconfiguration and upgrade problems | |||
|
| GO | |
|
This topic provides:
Information on the causes of reconfiguration and upgrade problems on the Lucent CM system
The steps to clear a Reconfig in Progress state on the Lucent CM system.
Reconfiguration problems can occur when adding or removing Lucent CM nodes or servers.
Examples of causes of reconfiguration problems are:
Internal network of existing Lucent CM server does not reside on the same network of the internal interface of the new Lucent CM server
External network of existing Lucent CM server does not reside on the same network of the external interface of the new Lucent CM server
Root password for new node is not known, or incorrect
SSH passphrase for the master node is not known, or incorrect
Internal and external DNS host names for new node are not resolvable
DNS host names are not exactly the same as the DNS host names that are configured on the new nodes
IP address of the Internal interface of the new Lucent CM node is unreachable
IP address of the External interface of the new Lucent CM node is unreachable
Invalid IP address or port address of the database.
No DNS to resolve the IP of call server.
Make sure you comply with all the requirements when adding nodes or servers.
Upgrade problems can occur when something interrupts an upgrade or reconfiguration process, and the process times out.
Examples are:
DNS outage
Network outage
A process timeout can cause in the Lucent CM system to remain in a Reconfig in Progress state.
When the Lucent CM system is in a Reconfig in Progress state, no upgrades can be performed on the Lucent CM system. If the Lucent CM system remains stuck in this state, the state must be cleared before proceeding.
Perform the following steps to clear a Reconfig in Progress state:
1 |
Verify if a reconfiguration is in progress. At the Lucent CM explorer, go to Lucent CM system and check the "Reconfiguration Status" |
2 |
Login to any local CM node as “root” user. |
3 |
Execute the script. Enter the command: sudo -u lps /opt/lps/current/bin/endReconfig.sh Result: The Reconfig in Progress state is reset and returns to the Reconfig not in Progress state. End of steps |
|
|
GO | |
|
| © Lucent Technologies | |||