Announcement Banner
UNSOLVED

AllBlack

updated

16 years ago

A

AllBlack

1 Rookie

•

74 Posts

0

5172

August 13th, 2009 17:00

Virtual Edition Client auto-discovery issue

Hi,

I have been asked to have a look at the VEC. First of all, I have no knowledge of Networker so someone will help me out there. I need to look at how to install the client on the vmware side of things.

I seem to have some problems with the auto-discovery.
I installed client on my virtual center and now I am trying to configure the auto-discovery but it fails.

My web services are running on VC as I can connect to web client in my browser. I don't get any indication as to why it fails.

Starting Auto Discovery Process for vcenter1
Monitoring Auto Discovery for vcenter1
Auto Discovery for vcenter1 failed Failed
Monitoring Auto Discovery Completed

Any ideas
Cheers

Message was edited by:
AllBlack
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1404

    0

    Posted September 4th, 2009 02:00

    Is there more in log of NW or VC for that session?
  • sbrooks15

    10 Posts

    1404

    0

    Posted November 6th, 2009 08:00

    Having the same issue. On the Advanced tab, it is looking for http://servername/sdk

    If I go to that page in a web browser, I get "The webpage cannot be found". Do we need a software development kit from Networker for to auto discover? Do the ESX hosts need to have the Virtual Client installed first?
  • sbrooks15

    10 Posts

    1404

    0

    Posted December 22nd, 2009 13:00

    So this is what I have learned since my first post.  If your Virtual Center is on a 64 bit operating system the "nsrvim" script will not install because it is only for 32 bit machines.  And Networker Engineers seemed to be under the impression no one would be using a 64 bit operating system ever!  7.6 does not have it either, so I guess maybe 7.7 will have it

  • jrinehart1

    28 Posts

    1404

    0

    Posted December 22nd, 2009 13:00

    I too am having the same issue. I am using NW 7.5 SP1 and after re-reading the admin guide, it states that the auto-discovery process calls a program called "nsrvim" from the virtual client server with Networker installed. However, the 7.5 SP1 client does not contain "nsrvim". The last version to contain this program was 7.4 SP2 that I have used.

    So, I tried to go back to 7.4 SP2 on my virtual client server and when "nsrvim" runs I get an error that "liblocal.dll" cannot be found. It is contained in the same directory as "nsrvim" but apparently that is not the location in which "nsrvim" is looking. This was working before we updated to vSphere 4 and NW 7.5.

    I'm confused as to the documentation still stating that the only command at this time that is used for auto-discovery but it is not included in the client or server installation.

    Am I missing something? I haven't called support yet and that'll be my next course of action unless the community as found the solution.

  • jrinehart1

    28 Posts

    1404

    0

    Posted December 22nd, 2009 14:00

    Yep. I did some more digging and came to the same conclusion.

    Very frustrating indeed.

  • jrinehart1

    28 Posts

    1402

    0

    Posted December 23rd, 2009 10:00

    Just so I understand, this could be any normal client running 32bit NW? It doesn't need anything special?

    In the auto-discovery config, I would list this client in the "command host" section and it should work? You mention that it works with NW 7.6, what about previous versions of NW?

  • sbrooks15

    10 Posts

    1060

    0

    Posted December 28th, 2009 06:00

    Thank you, samadm!!

    It works, I just pointed the command host only to a 32 bit server and it all comes up with no issue.

  • 832

    0

    Posted May 7th, 2010 14:00

    That's great! . . . unless you don't have any 32-bit OSs around anymore :-( It's not like you can still install the NW 32-bit client on Windows x64 to get around all of this.

    So I'm trying to dig around and find the Networker documentation that says "This is a really cool VMware backup feature - but is only available on old 32-bit Windows". Haven't found it yet . . .

  • 832

    0

    Posted May 7th, 2010 15:00

    What do you know. Finally found it on pg 527 in the 7.6 Admin Guide:

    A binary, nsrvim, is used to facilitate communication between the NetWorker

    software and the VMware VirtualCenter. The nsrvim binary can communicate with

    the Web Services server on the VMware VirtualCenter using the secure HTTPS

    protocol. The nsrvim binary is available only on Windows x86 platforms and is

    included in the NetWorker for Windows 32-bit installation. All NetWorker servers

    regardless of platform must contact a NetWorker client running in a Windows

    environment for auto-discovery. By default, the NetWorker server contacts the

    NetWorker client running on the VMware VirtualCenter.

  • azakaban

    8 Posts

    490

    0

    Posted August 24th, 2010 01:00

    Many thanks for this post. Just moved vCentre to a Windows 2008 R2 host and got this problem. Worked a treat.