Article Number
000033143
Applies To
RSA Product Set: Security Analytics
RSA Product/Service Type: SA Security Analytics Server
RSA Version/Condition: 10.6.0.0
RSA Product/Service Type: SA Security Analytics Server
RSA Version/Condition: 10.6.0.0
Issue
After upgrading to 10.6.0.0, some appliances display the incorrect current version details as reflected below.
Image description
Image descriptionCause
The incorrect version is displayed since the MongoDB wasn't updated properly during the upgrade process. This can happen when systems are upgraded through the command line rather than through the WebUI.
Use the following steps to verify and correct the MongoDB.
1. Logon to the target appliance via ssh and note the Node_id of the appliance which has incorrect version details in Hosts page:
cat /var/lib/puppet/node_id command.
2. Login to the Security Analytics server via ssh and run the following commands.
mongo puppet
db.nodes.find({node: '<Node_id>'})
Note: <Node_id> must be replaced with the node_id value from step1.
Sample output from the db.nodes.find() command:
Image description
Use the following steps to verify and correct the MongoDB.
1. Logon to the target appliance via ssh and note the Node_id of the appliance which has incorrect version details in Hosts page:
cat /var/lib/puppet/node_id command.
2. Login to the Security Analytics server via ssh and run the following commands.
mongo puppet
db.nodes.find({node: '<Node_id>'})
Note: <Node_id> must be replaced with the node_id value from step1.
Sample output from the db.nodes.find() command:
Image descriptionResolution
Please follow these steps to update MongoDB with correct Current Version details.
1. Logon to the target appliance via ssh and note the Node_id of the appliance which has incorrect version details in Hosts page:
cat /var/lib/puppet/node_id command.
2. Login to the Security Analytics server via ssh and run the following commands.
mongo puppet
db.nodes.update({node: '<node_id>'}, {$set: {currentVersion: {version: {major: '10', minor: '6', servicePack: '0'}}}})
exit
Note: <Node_id> must be replaced with the node_id value from step1.
3.The following browser URL refreshes the Hosts page with the new data. By forcing it to reload the info from the mongo db.
4. Check the WebUI to verify the current version details have been updated.
1. Logon to the target appliance via ssh and note the Node_id of the appliance which has incorrect version details in Hosts page:
cat /var/lib/puppet/node_id command.
2. Login to the Security Analytics server via ssh and run the following commands.
mongo puppet
db.nodes.update({node: '<node_id>'}, {$set: {currentVersion: {version: {major: '10', minor: '6', servicePack: '0'}}}})
exit
Note: <Node_id> must be replaced with the node_id value from step1.
3.The following browser URL refreshes the Hosts page with the new data. By forcing it to reload the info from the mongo db.
https://<SA-server-hostname>/ajax/appliances/reload
4. Check the WebUI to verify the current version details have been updated.
In this article
