|Applies To||RSA Product Set: RSA Data Protection Manager|
RSA Product/Service Type: DPM Appliance / DPM Appliance (Virtual)
RSA Version/Condition: 184.108.40.206.1 / 220.127.116.11 / 18.104.22.168 / 22.214.171.124
|Issue||After upgrading a cluster using tokenization and a setting of Node ID for replication collision avoidance to any version from 126.96.36.199.1 through 188.8.131.52, the node ID value in new tokens will always be 1 instead of the node ID of each individual cluster member. This value is appended to the end of all token values on each node. This will give the appearance of all tokens being generated from the same node and can make it difficult to track down which node is generating a given token.|
Sample token from node 2 before this issue:
Sample token from node 2 after this issue:
Note that the node ID value appended to the end of the token value no longer reflects the accurate node ID.
|Cause||When performing an upgrade, the cluster.order.number value in keyManagerServer.properties is reset to a value of 1. This is what drives the node ID setting for replication collision avoidance.|
|Resolution||This issue is resolved for appliances in the 184.108.40.206 hotfix.|
To resolve this issue on DPM Server, you need to manually set the cluster.order.number value to equal the node ID value after the upgrade is complete.
|Notes||We do not support or recommend changing cluster.order.number to any value other than the nodeID. For more information, see "RSA Data Protection Manager Appliance 220.127.116.11 Administrators Guide" and refer to Chapter 2 "Deployment Types", Section "Cluster Deployment", subsection "Avoid Token Collision in a Cluster".|