topic Re: Host Package on external client in Active IQ Unified Manager Discussions

Host Package on external client

connoisseur — Thu, 05 Jun 2025 06:40:07 GMT

Hi!

Sorry if this is a noob question, but I´ve read through the documents and couldn´t quit find the answer.

I have a customer with vSphere 4.

They want to connect to our filer now but after some initial tests the VMware admin thought that the NetApp applications used a lot of memory on the client.

So they want to install the hostpackage on an external client instead.

And I have two questions.

1. What ports should be opened in what direction? There should be both to the ESX/vSphere klient and to our Management server?

2. Is both the Host Package and VSC to be installed on the external klient or shoudl the VSC still be isntalled on te ESX/vSphere klient?

Sorry if this is a noob question, but I´m new to this?

Thanks in advance..

Re: Host Package on external client

chott — Thu, 19 Apr 2012 08:21:58 GMT

just tp bring some ativity into this community:

regarding your second question:

- VSC and Host Package are completely independent products so you can install them on different servers

- however if you do so you are loosing the ability to configure a local shared "lock" folder, preventing a deadlock situation between VSC and Host Package:

- you might be able to setup a shared lock directory on a network share though

Installation Guide: (page 51)

If you plan to install OnCommand Host Package on the same system as Virtual Storage Console

2.1.1, a best practice is to setup a shared lock directory. A shared lock directory is used for products

that share resources through the vSphere client. This ensures that mutually exclusive functions do not

happen in parallel. For example, cloning of a virtual machine through Virtual Storage Console at

same time that OnCommand Host Package is attempting to restore the same virtual machine.

hope that helps partially...

cheers chris

Re: Host Package on external client

connoisseur — Thu, 19 Apr 2012 08:25:16 GMT

Thanks Chris.

I sort of forgott this topic 🙂

Re: Host Package on external client

mark_schuren — Fri, 22 Feb 2013 12:37:58 GMT

Is the same recommendation (to use a shares lock dir between VSC and Host Package) still there for VSC 4.0 / 4.1 and Host Package 1.2?

Because the HS setup guide explicitly states VSC version 2.1.1.

Any ideas?

Re: Host Package on external client

chott — Fri, 22 Feb 2013 12:53:28 GMT

Hi Mark,

couldn't think of a reason why it should not be required any more, so yes.

The documentation has probably just not been updated.

cheers chris

Re: Host Package on external client

mark_schuren — Fri, 22 Feb 2013 15:29:38 GMT

Thanks for confirmation, Chris. Always did it but was not sure if still required.

Mark

Re: Host Package on external client

adaikkap — Sat, 23 Feb 2013 03:58:08 GMT

Hi Mark,

Yes, because they are still competing actions that are possible by VSC and HP. I am filing a bug for the same to get it updated.

Regards

adai

Re: Host Package on external client

mark_schuren — Fri, 01 Mar 2013 08:28:14 GMT

Great, thanks.

Von: Adaikkappan Arumugam

Gesendet: Samstag, 23. Februar 2013 04:59

An: Mark Schuren

Betreff: - Re: Host Package on external client

<https://communities.netapp.com/index.jspa>

Re: Host Package on external client

created by Adaikkappan Arumugam<https://communities.netapp.com/people/adaikkap> in OnCommand Management Software - View the full discussion<https://communities.netapp.com/message/101130#101130>

Hi Mark,

Yes, because they are still competing actions that are possible by VSC and HP. I am filing a bug for the same to get it updated.

Regards

adai

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/101130#101130>

Start a new discussion in OnCommand Management Software by email<mailto:discussions-community-products_and_solutions-storage_management_software@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=2026>