Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Article Number: 000170139


Avamar: How to use remote MCCLI server to manage multiple Avamars which are using signed MCSSL cert

Summary: Avamar: How to use remote MCCLI server to manage multiple Avamars which are using signed MCSSL cert

Article Content


Symptoms

Signed certificate was installed using AUI which changed MCSSL cert to signed cert. 

Note: This KB article is applicable for Avamar 19.2.x and 18.2.x only. This article should not be applied to previous Avamar versions.

If MCSSL certificate is changed to a signed certificate, (see KB article 540434: Avamar 19.2: How to install CA Signed certificate using AUI), remote MCCLI server stopped working with below error:   
 
1,23996,CLI failed to connect to MCS.
Attribute Value
--------- -------------------------------------------------------------------------------------------------------------------------------------------------
reason    FIPS 140-2 mode is not supported on Java 7.  Please install supported version of Java on the client machine, or turn off this mode on the server.
option    non-JRMP server at remote endpoint

Cause

Remote MCCLI server does not contain correct chain certs (root and intermediate cert) for Avamar server.

Resolution

  1. Log in to remote MCCLI server and switch to MCCLI install directory. For example:   
cd /usr/local/avamar/19.2.0-155/lib  
  1. Take backup copy of existing rmi_ssl_keystore:    
cp -p rmi_ssl_keystore rmi_ssl_keystore-orig
  1. Import Chain certs which contain root and intermediate certs for CA (assuming you have received ca.crt from CA):   
keytool -importcert -file ca.crt -alias rootcert -keystore /usr/local/avamar/19.2.0-155/lib/rmi_ssl_keystore -storepass changeme
  1. Try MCCLI command from remote MCCLI server to test. It should work now. 

Additional Information

This content is translated in 17 languages: 
https://downloads.dell.com/TranslatedPDF/CS_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/DA_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/DE_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/ES-XL_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/FI_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/FR_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/IT_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/JA_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/KO_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/NL_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/NO-NO_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/PL_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/PT-BR_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/RU_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/SV_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/TR_KB540989.pdf
https://downloads.dell.com/TranslatedPDF/ZH-CN_KB540989.pdf

Article Properties


Affected Product

Avamar

Product

Avamar

Last Published Date

17 Dec 2020

Version

3

Article Type

Solution