Smarts SAM: Manually Adding 8.1.x Domain to a 9.1 or 9.2.x Broker the Domain will report Dead on the 9.x Broker

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


When you manually add a Smarts SAM 8.1.x domain to a Smarts SAM 9.1 or 9.2 broker, the 9.1/9.2 broker will not be able to talk to the 8.1.x domain

This will impact upgrades when you move your Smarts SAM 8.x domain and broker to 9.x, and do not want to restart any of your existing domains, but instead to use the new 9.x broker for the new SAM 8.x domain to connect to the other domains.


When manually adding a Smarts SAM 8.1.x domain to a 9.1 or 9.2 broker with the brcontrol add_dm test domain, the domain will show Dead when running a brcontrol command. 

However, the domain is running and if the domain is still registered with the 8.1.x broker it will appear to be Running as well.

Errors like the following will appear in the domain log file:

CI-BSAFE-error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number: ; in file "s3_pkt.c" at line 553
brstart[844]: CI-TLSPE-TLS protocol error


[April 19, 2016 2:56:35 PM EDT +558ms] t@5040 InCharge Framework
SVIF-W-ESERVERCONNECT-While attempting to (re)connect to the remote server 'SBD_SAM'
 SM-BROKER-Broker location: tow-p-smtsm02.americas.swk.pri:426/dmbroker
 SM-ENOTREGISTERED-Domain Manager is not registered with the DM Broker
 

 

Environment

VMware Smart Assurance - SMARTS

Cause

This issue occurs because the Smarts SAM 8.1.x domain was added as a TLS-capable domain using brcontrol add_dm test-sam.  Smarts SAM 8.1.x domains do not use TLS, but instead use keepalives. There is currently no way in Smarts SAM to specify that this is a legacy domain that does not use TLS.

Resolution

To address this issue, the "usingTLS" attribute for the Smarts SAM 8.x domain must be set to false as follows:

1. Attach to the Smarts SAM 9.x broker.
2. Run the following commands:

./dmctl -s localhost:426/dmbroker

put DomainManager::test-sam::usingTLS FALSE