Networker

[Networker] Networker and 64 Bit vCenter Server Woes

2009-11-18 15:16:23
Subject: [Networker] Networker and 64 Bit vCenter Server Woes
From: Chester Martin <cmartin AT SPP DOT ORG>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 18 Nov 2009 14:12:29 -0600
Hope this helps someone else who has run into the same issue.

 

After upgrading to vCenter on a 64 bit server, networker no longer can
use "auto-discovery" to find the vm clients.  If you look in the
nsrtask.raw file after attempting an autodiscover you will see "Could
not run nsrvim: The system cannot find the file specified".  If you look
on the vCenter server, sure enough nsrvim.exe does not exist in the
........\bin directory.  This is because networker doesn't support a 64
bit version of the nsrvim.exe binary.  I've seen several posts on the
net on others who have run into the same issue.

 

Emc support had me try something that allowed "auto-discovery" to work.
Since we still have our old infrastructure client server online (it's
not 64 bit).  He had me point the "command host" in the "enable
auto-discovery" setup to the old infrastructure client, and leave the
"hostname" as the new vCenter server.  Autodiscovery worked for us after
doing this. 

 

Of course this is just a workaround, but it allows auto-discovery to
work until the 64 bit version supports nsrvim.exe.

 

 


To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>