Error Message

V-338-1-2039:"CS not reachable from Managed Host"

There could be several causes, but if the MH or CMS was on a DHCP designated IP it is likely the firewall is controlled by IP and that the port 5634 was not open in the firewall from the Managed Host to the Control Server or vice versa.

The time difference between the MH and CMS could be too great to coordinate connections. It should be verified to be within the parameters listed in the Administrator's Guide for the version installed.

The communication channel can be confirmed by verifying the connection between the CMS and MH.

1) Verify the output of getvitals from CMS to MH and vice-versa

From the managed host:
C:\Program Files\Veritas\VRTSsfmh\bin\xprtlc -u nobody -l https://:5634/world/getvitals

From the central management server:
C:\Program Files\Veritas\VRTSsfmh\bin\xprtlc.exe" -u nobody -l https://:5634/world/getvitals

From the managed host:
/opt/VRTSsfmh/bin/xprtlc -u nobody -l https://:5634/world/getvitals

From the central management server:
/opt/VRTSsfmh/bin//xprtlc.exe" -u nobody -l https://:5634/world/getvitals

 

2) Firewalls must allow port 5634 bi-directional access between subnets hosting CMS and MHs.

3) Ensure the CMS is up -

            o On Windows: Check in the Service control manager or task manager for the xprtld process actively running.

            o On Unix: Check if xprild and vxdclid are running using 
                                ps -ef | grep xprtld

                                ps -ef | grep vxdclid

4) verify host management installation on UNIX by making sure that the VRTSsfmh package is installed, and the required processes are started.

            o On Windows: Check in C:\Program Files\VERITAS\VRTSsfmh directory, if exists

            o On Unix: use the command: rpm -q VRTSsfmh

            o On AIX: Use the command: lslpp -l VRTSsfmh

            o On HP-UX: Use the command: swlist VRTSsfmh

            o On Solaris: Use the command: pkginfo -l VRTSsfmh

 

 

 

On the Veritas Operations Manager (VOM) Central Management Server (CMS) the Managed Host (MH) can show up in a faulty state indicating there is no current heartbeat or contact from the MH. The MH when reviewed could have an active xprtld daemon waiting to contact the CMS and report the current status. Neither cycling the MH processes or refreshing the host from the CMS Console will bring the MH into communication to clear the reported fault.