Add, modify, or delete a node | |||
GO |
This topic describes the steps to add, modify, or delete a node on the Lucent CM system.
Nodes can have the following processes:
Load balancer (up to 2)
Lucent CM application
Database
In the Lucent CM Explorer, a node is represented in both the Nodes folder and in the System Servers folder. The Nodes folder entries are used for configuration. The System Servers entries can be used to start and stop the servers and view status information.
Updates to most node parameters require reconfiguration of the Lucent CM node. Reconfiguration results in complex changes to the node and must comply with strict rules. Reconfiguration procedures are described in a separate chapter.
Only Max Call Logs can be updated without reconfiguration.
Node names cannot be changed after a node is added. If the node name must be changed, the node must be removed and added with a new name.
The following procedures require reconfiguration:
Change node name
Change role of a node
Only one node reconfiguration action can occur on a Lucent CM system at any given time. This includes reconfiguration from different administration accounts.
Node Info parameters are:
Parameter |
Description |
Node Name |
Alphanumerical name for the node. Must be unique for the system. |
External Hostname |
Alphanumerical external name for the node. Must be unique for the system network. |
Internal Hostname |
Alphanumerical internal name for the node. Must be unique for the system network. |
New SSH Passphrase 1 |
Password for establishing SSH connection |
Verify SSH Passphrase 1 |
Password for establishing SSH connection |
Load Balancer 2 |
Checkmark box to define whether the node acts as a load balancer node. |
Lucent CM Application |
Checkmark box to define whether the node acts as an application node . |
Web Portal Identity |
URL to identify the web portal that is related to this Lucent CM node. The web portal can be a customer web portal that provides service management functionality to Lucent CM users. |
Database |
Checkmark box to define whether the node acts as a database node. |
Peer Node 3 |
Peer node for the database |
Max Call Logs |
The maximum number of call log services that can be defined on this node. |
Call Logs Assigned |
The number of call log services that are currently defined on this node. |
OMC-P Connection Status |
The status of the connection between the Lucent CM server and the OMC-P Server that manages the Lucent CM system. |
Details |
Button to display OMC-P Server connection details. |
1 | |
2 | Maximum of 2. Can only be selected on the first two application nodes. |
3 |
A database can be configured with a peer node. When adding the first node, the peer node field cannot be changed directly. You must add the second node, and select the first node that you added as peer node.
The checkboxes define the type of node that is equipped.
To define the type of nodes, mark the appropriate checkboxes:
Type of node |
Mark checkbox |
U-node |
Lucent CM Application Load Balancer Database |
A-node |
Lucent CM Application Load Balancer (only for the first two nodes) |
D-node |
Database |
For more information on nodes and node types, refer to Lucent CM nodes.
Before you add a node, ensure the following:
Server hardware and cabling is installed
Red Hat Linux is installed
Timezone RPM is installed
NTP client is installed
Refer to chapter Configuration management - Lucent CM system installation.
Important! Perform a backup of the Lucent CM system before you add a new database segment.
A database segment cannot be removed once it is created. To remove the new database segment, restore the Lucent CM system using a backup that does not have the new database segment.
Perform the following steps:
1 |
At the Lucent CM Explorer tree view, select Lucent CM System → Nodes. Result: The Nodes list displays, listing the nodes. | ||||||||
2 |
Important! Do not use this procedure when you want to change a parameter that requires reconfiguration.
| ||||||||
3 |
Configure the Node info parameters. | ||||||||
4 |
Click Add or Update to save the changes. | ||||||||
5 |
Enter the “root” user account password and SSH passphrase to confirm the action. Result: The changes are applied and the Node panel remains open. Applying the change can take several minutes. When you select the Nodes folder in the Lucent CM Explorer tree view, the changes display in the Nodes List. End of steps |
GO | |||
© Lucent Technologies |