Error Message

1) [root@XYZ vom_agent]# /var/tmp/vom_agent/vom_agent_managed_host_@#$%
Checking if MH version [7.2.0.100] is same or greater than as that of least supported MH version [5.0.0.0]

InfoScale Operations Manager Managed Host Deployment
Initializing
Attempting to configure host using hostname XYZ.ABC.123.com.
Verifying if it is reachable from the CMS DEF.ABC.123.com...
Extracting credential
Configuring managed host

Managed host failed to communicate with Central Server
Failed to configure managed host
Please refer to the log file /var/opt/VRTSsfmh/logs/mhrun.log

2) mhrun logs entry shows,

2018-09-12 09:24:52 [warning] 4604 create_sfm_conf: get_hosts_with_hname: Failed to check if host [XYZ.ABC.123.com] exists in DB. Out: []. Err: []
2018-09-12 09:24:52 [error] 4604 create_sfm_conf: Could not communicate with CMS to check if another host with same name is already configured: {
"XPRTLD_VERSION" :  "7.2.0.100",
"LOCAL_NAME" : "localhost.localdomain",
"LOCAL_ADDR" : "127.0.0.1",
"PEER_NAME" : "localhost.localdomain",
"PEER_ADDR" : "127.0.0.1",
"LOCAL_TIME" : "1536744292",
"LOCALE" : "C",
"DOMAIN_MODE" : "FALSE",
"QUIESCE_MODE" : "RUNNING",
"OSNAME" : "Linux",
"OSRELEASE" : "3.10.0-327.el7.x86_64",
"CPUTYPE" : "x86_64",
"OSUUID" : "{00010050-5683-55f5-0000-000000000000}",
"DOMAINS" : {
    "sfm://ABC.is.123.com:5634/" : {
        "primary_broker" : "vxss://ABC.is.123.com:14545/sfm_agent/sfm_domain/vx"
        }
    }
}
 
2018-09-12 09:24:52 [debug] 4604 create_sfm_conf: json = {"JOB":{"ERROR":"CONFIGURE_MH_CS_COMM_FAILED","ISHIDDEN":0,"RETURNCODE":100,"NAME":"create_sfm_conf","OUTPUT":"{\n\"XPRTLD_VERSION\" :  \"7.2.0.100\",\n\"LOCAL_NAME\" : \"localhost.localdomain\",\n\"LOCAL_ADDR\" : \"127.0.0.1\",\n\"PEER_NAME\" : \"localhost.localdomain\",\n\"PEER_ADDR\" : \"127.0.0.1\",\n\"LOCAL_TIME\" : \"1536744292\",\n\"LOCALE\" : \"C\",\n\"DOMAIN_MODE\" : \"FALSE\",\n\"QUIESCE_MODE\" : \"RUNNING\",\n\"OSNAME\" : \"Linux\",\n\"OSRELEASE\" : \"3.10.0-327.el7.x86_64\",\n\"CPUTYPE\" : \"x86_64\",\n\"OSUUID\" : \"{00010050-5683-55f5-0000-000000000000}\",\n\"DOMAINS\" : {\n    \"sfm://ABC.is.123.com:5634/\" : {\n        \"primary_broker\" : \"vxss://ABC.is.123.com:14545/sfm_agent/sfm_domain/vx\"\n        }\n    }\n}\n","STATE":"FAILED","PROGRESS":40}}
2018-09-12 09:24:52 [debug] 4604 check_duplicate_vmid: json =

3) V-383-50513-5778 Communication failure with managed host
Excerpt from /var/opt/VRTSsfmh/logs/mhrun.log:
2017-06-05 17:33:03 [debug] 23890 refresh_host: Set HOST_CONFIG_MAPPING.State = [4], host_id [{0001b4b5-2f66-f150-0000-000000000000}], type [AGENT]
2017-06-05 17:33:03 [debug] 23890 refresh_host: json = {"JOB":{"ERROR":"Communication failure with managed host.","ISHIDDEN":0,"RETURNCODE":4,"NAME":"refresh_host","OUTPUT":"HTTP/1.1 401 Unauthorized\r\nWWW-Authenticate: Basic realm=\"cwxticm5\"\r\n\r\n

Authorization Required

This server could not verify that you are authorized to access the document requested.  Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.

4) V-383-50513-57759: Managed host failed to communicate with Management Server 
Log file: 
/var/opt/VRTSsfmh/logs/add_host.log or configuration log link in GUI 

[11/08/2015 22:59:51] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME": "add_host","OUTPUT":"ADD_HOST_INIT_DISCOVERY", "STATE":"SUCCESS","PROGRESS":80}}
[11/08/2015 22:59:51]  fancy_die
[11/08/2015 22:59:51] CONFIGURE_MH_CS_COMM_FAILED
[11/08/2015 22:59:51] {"JOB":"RETURNCODE":-1,"ERROR": "CONFIGURE_MH_CS_COMM_FAILED","NAME": "job_add_host","OUTPUT":"","STATE":"FAILED","PROGRESS": 100}}{"RESULT": {"RETURNCODE":-1,"UMI":"V-383-50513-5759","ERROR": "CONFIGURE_MH_CS_COMM_FAILED","NAME":"add_host","TASKID":"{yJTaTamZo9tMMQjY}"}}
[11/08/2015 22:59:51] fancy_dead

1. Make the CMS the same, or higher, version (pre-VOM 7.0)

Note: Versions 6, and above, are supported at the time of this writing.

• Older versions of the CMS installer can be downloaded as follows:
• Browse to: https://downloads.infoscale.com/infoscale-operations-manager-and-license-management-service/REL689151

2. Make the version of each MH the same as the CS (7.0)

• These packages can be downloaded as follows:
• Browse to: https://downloads.infoscale.com/infoscale-operations-manager-and-license-management-service/REL689151
• Download the "Managed Host 7.0 Bundle" ("Description" Optional)
• Use the desired method to add the MH to the domain

NOTE for Unix: 
If the file /etc/default/sfm_resolv.conf is not present, empty or contains "[domains]"  (and nothing else) then the older version of the Operation System (OS) package may be removed using typical OS commands, then the 7.x version of the package may be installed. 

The commands to install these packages can be found in the  InfoScale Operations Manager 7.0 Installation and Configuration Guide,  

 

There could be multiple issue relating to this problem,
1) MH to MS communication issue
2) Ports 5634 or required ports are not open bidirectional and Firewall is blocking the ports
3) xprtld is not running on MH or MS
4) Different VRTS file versions (V-383-50513-5778 Communication failure with managed host/V-383-50513-57759: Managed host failed to communicate with Management Server )
 

1) Ensure there is a proper communication happening between MH and MS and if required add etc\hosts entries for MS from MH

2) Ports 5634 and/or required ports should be open bidirectional, telnet to see if port 5634 is listening on both nodes and firewall is not blocking the port,
[root@server101 VRTSexplorer]# firewall-cmd --list-port
443/tcp 80/tcp 443/udp 80/udp
[root@server101 VRTSexplorer]# firewall-cmd --permanent --add-port=5634/tcp
success
[root@server101 VRTSexplorer]# firewall-cmd --reload
success
[root@server101 VRTSexplorer]# firewall-cmd --list-port 5634/tcp 443/tcp 80/tcp 443/udp 80/udp

3) Ensure xprtld is running on both the node MH or MS.

4) Ensure following VRTS packages are of same version on both the nodes,
on MS: VRTSsfmcs & VRTSsfmh
on MH: VRTSsfcpi & VRTSsfmh
a) Sometimes the error encounters "V-383-50513-5778 Communication failure with managed host" appears when trying to refresh a Managed Host. This occurs if the version of the Managed Host (package VRTSsfmh) is earlier than the CS, and this issue ONLY applies to a newly-installed 7.2 CS, not one that has been upgraded from a previous version and has 7.0 MHs already added. The issue can be verified by the VRTSsfmh log from the MH, as shown above. 

Upgrade the MH (package VRTSsfmh) to 7.2 and re-add the host to the CS. 
If this is not possible, as a workaround, set up a manual trust:

• On a Linux managed host, enter the following commands:
  export EAT_HOME_DIR=/opt/VRTSsfmh
  export EAT_DATA_DIR=/var/opt/VRTSsfmh/sec
  /opt/VRTSsfmh/bin/vssatbin setuptrust -b CS_FQDN:14545 -s high
• On a Windows managed host, enter the following commands:
  set EAT_HOME_DIR=C:\Program Files\Veritas\VRTSsfmh
  set EAT_DATA_DIR=C:\ProgramData\veritas\VRTSsfmh\sec
  vssatbin setuptrust -b CS_FQDN:14545 -s high

b) Sometimes the error encounters "V-383-50513-57759 Managed host failed to communicate with Management Server" encountered when adding a MH (managed host) to a new installation of 7.0 CMS (Central management Server) A new installation of a 7.x, and higher, CMS uses 2048 bit certificates while version 6.x, and lower, use1024 bit certificates. An in-place upgrade of CMS to 7.0 will continue to communicate to MH versions 6.1, and below. 

There are two things that can be done to resolve this issue. 

1. Make the CMS the same, or higher, version (pre-VOM 7.0) 
2. Make the version of each MH the same as the CMS (7.0) 
The solutions to these options are below: 

When trying to add the new MH from the terminal session to the Infoscale Operations Manager (VIOM) domain, the error is encountered: Managed host failed to communicate with Central Server failed to configure managed host.