Solved

vShield manager can't talk to one ESX host - "Host not reachable"

Posted on 2013-05-27
1
2,130 Views
Last Modified: 2013-11-22
We use Deep Security 9. A ESXi 5.1 host was taken down in maintenance mode for a period of more then one week while we were waiting for an additional vRanger license for the host. After the license was received and everything taken care of in that matter, the host was taken out of maintenance mode. Soon it was obvious that the DSVA on the host was no longer functioning. After some troubleshooting it was deleted and we attempted to deploy a new DSVA on the host. This did not succeed. The error message stated that the DSVA could not register with the vShield Manager. vShield manager states that the host is not reachable. I can ping from the host to the vCenter and vShield Admin, I can ping from vShield admin and vCenter to the host. The host also looks fine in vCenter. I have restored the host in Deep Security Admin and booted it. I have rebootet the vShield Manager. I have re-synhronized vShield manager with the vCenter server. vShield admin stills shows the same state for the esx host, "Host not reachable."
27.05.png
0
Comment
Question by:itnifl
1 Comment
 
LVL 2

Accepted Solution

by:
itnifl earned 0 total points
ID: 39203751
There was some problem with network communication to the host. I am not sure what fixed it, but it is OK now.
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Last article we focus in how to VMware: How to create and use VMs TAGs – Part 1 so before follow this article and perform the next tasks, you should read the first article how to create the TAG before using them in Veeam Backup Jobs.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …

820 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question