search cancel

DA failed to sync after overinstall of Data Agregator (DA)


Article ID: 239755


Updated On:


CA Performance Management - Usage and Administration


After doing an over-install of the Data Aggregator, the DA data source fails to test.

Also seeing errors in the karaf.log on the Data Aggregator showing that the DA cannot contact theEvent Manager on the Netops Portal.

at Source) [?:?]
aused by: org.apache.cxf.transport.http.HTTPException: HTTP response '401: Unauthorized' when communicating with http://rms-pm-pc-1:8281/EventManager/EventManaerWS.asmx


When doing a 21.2.8 over-install of the DA we do not change the SsoEncryptionAlgorithm from AES to DES in case the user has changed to DES.


Release : 21.2

Component : PM Data Aggregator


To remedy:

1) Use SsoConfig on the Netops Portal to verify the following under 4. Single Sign-On

Encryption Decryption Key: <VALUE>
Encryption Algorithm:<AES/DES>

2) Compare these to the following values from the Data Aggregator from http://<DA>:<port>/rest/dataaagegator

<SsoEncryptionAlgorithm>(AES or DES)</SsoEncryptionAlgorithm>

Also note the <ID>(NUMBER)</ID>

If you did an over-install of the DA what you will likely see is the SsoEncryptionDecryptionKey matches, but the SsoEncryptionAlgorithm does not.

To correct this, make the SsoEncryptionAlgorithm on the DA match the Netops Portal via REST:

URL: http://<DA>:<port>/rest/dataaagegator/ID
Method: PUT

<DataAggregatorInfo version="1.0.0"><SsoEncryptionAlgorithm>(AES or DES)</SsoEncryptionAlgorithm></DataAggregatorInfo>

Where ID is the ID of the Data Aggregator as noted previously, and (AES or DES) would be th value in use by the Neetop Portal as noted previously.

Example using curl, where the DA id was 70 and the SsoEncryptionAlgorithm needs to be changed to AES, run from the DA itself:

curl -kv -u admin:admin  -X PUT -H "Content-Type: application/xml" -d'<DataAggregatorInfo version="1.0.0"><SsoEncryptionAlgorithm>AES</SsoEncryptionAlgorithm></DataAggregatorInfo>'