How to Change the AMS ID on an AMS Node

Each AMS (Active Message Store) node within the NewNet cluster is assigned a unique AMS ID.  If two or more AMS nodes have the same AMS ID, this can cause replication or communication failures between nodes (e.g., AMS showing as “NOT AVAILABLE” in tp_qcli).

If two nodes have the same AMS ID, you may see an error like this in /var/log/messages:

Jan 17 07:17:58 Node_05 tp_ams: Duplicate AMS Id (1) detected. Two nodes have the same id!

Duplicate AMS IDs can occur if restarting multiple nodes at the same time, or after a rebuild.

This article explains how to verify and reassign a correct AMS ID to an affected node.

Process

Notes: 

• Perform the following steps as the textpass user on the affected node (e.g., AMS07).
• This process involves temporarily shutting down the affected AMS process.
• In this example, AMS07 should have ams_id=6, but was assigned ams_id=1 after rebuilding.  The below show how this was corrected.

1. Verify Current AMS ID

   grep "ams_id from database" /var/log/messages | tail -5

   • Confirms the AMS ID currently registered in the database.

   • Example output:

     /var/log/messages:Jan 12 07:17:53 AMS07 tp_ams: AMS read 1 as ams_id from database for AMS identifier

2. Check Process Status

   tp_status

   • Confirms the current operational state of AMS and related components.

3. Stop the AMS Process

   tp_stop --tp_ams

   • Gracefully stops the AMS service on the node.

4. Assign the Correct AMS ID

   tp_ams --amsid=<new_id> --makemyday=yes

   • Replace <new_id> with the correct unique AMS ID for this node (e.g., 6 for RTR07).

   • Example:

     tp_ams --amsid=6 --makemyday=yes

5. Restart the AMS Process

   tp_start --tp_ams

   • Restarts AMS with the updated identifier.

6. Wait 30 Seconds and Validate Initialization

   tp_status tp_ams operating 0 days, 0:00:14.51

7. Confirm AMS ID Update

   grep "ams_id from database" /var/log/messages | tail -5

   • Verify that the AMS now reports the new ID:

     /var/log/messages:Jan 13 02:10:28 AMS07 tp_ams: AMS read 6 as ams_id from database for AMS identifier

8. Verify AMS Availability

   tp_qcli -s -n

   • Confirm that the node now appears as available with the new AMS ID:

     [textpass@AMS07 ~]$ tp_qcli -s -n
     List of available AMS nodes
     AMS status host_id sub_id port adresses
     --------------------------------------------------------------
     0 available ab12cd34 0001a2b3 11168 192.168.10.11
     1 available 9f45de67 0000b4c2 11168 192.168.10.12
     2 available 8a23ef90 0001d3e4 11168 192.168.10.13
     3 available bc56f123 00004321 11168 192.168.10.14
     4 available da78b912 0000754a 11168 192.168.10.15
     5 available ef90ac45 0001ce89 11168 192.168.10.16
     6 available c123d456 0001f234 11168 192.168.10.17