silverlance
Contributor
Contributor

vShield Zone 4.1 installation problem.. :(

Hi,

I'm encountering this problem when installing vShield Zone 4.1.

"Previous installation of host services encountered error"

And upon checking the recent task bar, I've noticed that the OVF template for vShield FW always shows in-progress but does not managed to start

"waiting for host (1/) port data update task to complete"....

Anyone has encountered this problem before and managed to solve this?

Thanks...

0 Kudos
4 Replies
admin
Immortal
Immortal

This can happen if

-vSM not configured with DNS

-VSM not able to resolve the esx hostname

Please check your DNS and esx hostname resolution.

Ravi

0 Kudos
Cacciari
Contributor
Contributor

I am suffering with this also.

About DNS. I put all entries in hosts file. This is not a problem since vCenter is working fine so far until now and there are several requirements based on DNS during vCenter setup.

I also did followed this:

Knowledge Base 1028003:

Symptoms

  • vShield App Installation fails
  • You see the error:

    Previous installation of host services encountered an error

Resolution

This issue can occur due to a previous incomplete installation or due to problems during uninstallation.
To resolve this issue:
  1. Verify if required modules are loaded in ESX host before installing vShield App.

    1. Log in to the ESX host using an SSH client and run the command:

      esx01# esxcfg-module -l | grep -i dvf
      dvfilter 2 72
      vmkapiv1_0_0_0_dvfilter_shim0 8


      OR

    2. Check the vShield Manager logs:

      Info Sep 16, 2010 03:42:15 PM *** *** 41: VMware ESX: esx 4.1.0 (HostAgent 4.1)
      Error Sep 16, 2010 03:42:17 PM *** *** 52: dvfilter module not loaded for host host-373
      Error Sep 16, 2010 03:42:17 PM InstallProcess doInstall 52:
      java.lang.Exception: Dvfilter module not up for host 10.112.97.33

  2. If modules are not loaded, load the modules with the commands:

    #esxcfg-module –e /usr/lib/vmware/vmkmod/dvfilter
    #esxcfg-module -v –e /usr/lib/vmware/vmkmod/vmkapiv1_0_0_0_dvfilter_shim

  3. Reboot the host and then retry the vShield App installation.
  4. If you still see error during installation: 
    1. Manually clean the ESX host before re-installation. Remove  vmservice-vswitch virtual switch under ESX host configuration and remove  the vShield packages with the commands:

      #esxupdate query | grep -i vShield
      #esxupdate remove -b <Package name from previous output>

    2. Delete the vShield-FW-<IP> virtual machine from vCenter Server Inventory.

  5. In the ESX host, navigate to Configuration > Software and click Advanced Settings.
  6. Remove the IP address from /Net/Net.DVFilterBindIpAddress.

Did all steps above and nothing.

I also see the "Operation timed out" error. According to this discussion there are several people that discussed moving of storage arrays from one side to another, reconfiguring RAID levels and recreating arrays. Nothing of that worked also. Even modifying SCSI timeouts didn't worked.

So, I made a brand-new installation of vCenter Server locally. Unregistered everything from the old vCenter server to the new one, installed vShield plugins again but the same installation error occurs:

Yellow sign "Previous installation of host services encountered error"

Recent Tasks "Deploy OVF Template" reaches status "Operation Timed Out" after a while (let's say 10-15 minutes)

The deployed OVF appears whortly in inventory but it disappears after a vSphere Client restart or after sometime.

This is a show-stopper for our project because we conceived it totally with vShield Edge and vShield Zones.

So if some if you got that working, please reply here because this question is still not answered for me or for opther people with same problems that I've googled so far.

0 Kudos
carlosVSZ
VMware Employee
VMware Employee

The fact that it  gets to the 'Deploy OVF Template' step and then fails still points to one of two possible things:

1. DNS

2. Storage

1. DNS - When you say you put entries in hosts files it tells me you are looking at the DNS on the VC or ESX hosts. What you need to check is the DNS on the vShield Manager. DNS servers need to be configured on the vShield Manager, also a good way to test is to log in to the CLI of the vShield Manager and from there ping by hostname the VC and the ESX servers.

2. Storage - make sure there is enough space on the datastore where you are deploying the vShield Zones firewall and make sure there are no latency/slowness when writing to the disk. A quick test is to install the vShield Zones firewall on local disk, just to rule out the shared storage being the issue. Of course, this is not the recommended installation location and I would strongly suggest to uninstall and then re-install on shared storage once the issue is fixed (Assuming there are issues with shared storage).

ne more thing I noticed from the screenshot is that you have not applied the license keys for vShield App and vShield Edge. I mention this because you say your test plan requires Edge and most likely vShield App (not the free version: Zones). You will need to apply the license keys in order to be able to deploy Edge.

Please check DNS/Storage and let me know.

Carlos

0 Kudos
Cacciari
Contributor
Contributor

carlosVSZ wrote:

... one of two possible things:

1. DNS

1. DNS - When you say you put entries in hosts files it tells me you are looking at the DNS on the VC or ESX hosts. What you need to check is the DNS on the vShield Manager. DNS servers need to be configured on the vShield Manager, also a good way to test is to log in to the CLI of the vShield Manager and from there ping by hostname the VC and the ESX servers.


Please check DNS/Storage and let me know.

Carlos

It worked so well it looked like cheating.

Thank you very much for your advice. Thumbs up to you!

0 Kudos