Browse Community
Help
Log In
Unsolved
This post is more than 5 years old
freeneet
33 Posts
0
1726
September 7th, 2012 01:00
Hi,
NetWorker 7.6.4.1.Build.1049, Windows 2008 R2, VMware vSphere 501 - please look at picture, autodiscovery failed?
thank you
freenet
1 Attachment
auto.jpg
Responses(7)
vishwanathkrish
75 Posts
September 7th, 2012 06:00
Make sure that the /nsr/res/servers file on the Virtual Center Server has an entry for the NetWorker server.
Thanks,
Vishwanath k
Panwar
79 Posts
September 10th, 2012 06:00
Hi
Make sure that networker services are running fine on the vcenter server. Try restart the Networker services .
Regards
there is FQDN and short name, any other ideas?
thanks,
pn1lDbv3G612259
105 Posts
September 14th, 2012 02:00
Are you running the Virtual Center server on windows 32 bit or 64 bit machine?
I was going through some old issues which relates to the sceeen shot which provided, Hence I would like to confirm the above details.
Also, I would suggest you to go though the discussion and let us know if that helps for you
https://community.emc.com/message/357593#357593
Thank you
ShivaKiran
restart.. still the same error
September 17th, 2012 01:00
Have you gone through the link and were you be able to solve the issue with Autodiscovery problem.
September 17th, 2012 05:00
thank you, problem solved
from nsrtask.raw:
78825 1347880093 2 0 0 3236 2604 0 ba.xxx.xx nsrtask 24 [%s] Launching: %s on %s 3 42 14 vc501.xxx.xx 0 37 nsrvim -s puxxx -D 0 vc501.xxx.xx 12 14 vc501.xxx.xx
78827 1347880093 2 0 0 3236 2604 0 ba.xxx.xx nsrtask 23 [%s] Monitoring job: %d 2 42 14 vc501.xxx.xx 1 7 1248820
78831 1347880100 2 0 0 3236 2604 0 ba.xxx.xx nsrtask 7 [%s] %s 2 42 14 vc501.xxx.xx 0 49 nsrvim starting on vc501.xxx.xx (process 7916).
78831 1347880100 2 0 0 3236 2604 0 ba.xxx.xx nsrtask 7 [%s] %s 2 42 14 vc501.xxx.xx 0 37 Connecting to NetWorker on 'puxxx'.
78832 1347880104 2 0 0 3236 2604 0 ba.xxx.xx nsrtask 20 [%s] Task result: %s 2 42 14 vc501.xxx.xx 0 6 Failed
there is wrong servername "puxxx" because Networker server renamed.
Dell Support Resources
View More
View All
Top
vishwanathkrish
75 Posts
0
September 7th, 2012 06:00
Hi,
Make sure that the /nsr/res/servers file on the Virtual Center Server has an entry for the NetWorker server.
Thanks,
Vishwanath k
Panwar
79 Posts
0
September 10th, 2012 06:00
Hi
Make sure that networker services are running fine on the vcenter server. Try restart the Networker services .
Regards
Panwar
freeneet
33 Posts
0
September 10th, 2012 06:00
there is FQDN and short name, any other ideas?
thanks,
freenet
pn1lDbv3G612259
105 Posts
0
September 14th, 2012 02:00
Hi,
Are you running the Virtual Center server on windows 32 bit or 64 bit machine?
I was going through some old issues which relates to the sceeen shot which provided, Hence I would like to confirm the above details.
Also, I would suggest you to go though the discussion and let us know if that helps for you
https://community.emc.com/message/357593#357593
Thank you
ShivaKiran
freeneet
33 Posts
0
September 14th, 2012 02:00
restart.. still the same error
pn1lDbv3G612259
105 Posts
0
September 17th, 2012 01:00
Hi,
Have you gone through the link and were you be able to solve the issue with Autodiscovery problem.
Thank you
ShivaKiran
freeneet
33 Posts
0
September 17th, 2012 05:00
thank you, problem solved
from nsrtask.raw:
78825 1347880093 2 0 0 3236 2604 0 ba.xxx.xx nsrtask 24 [%s] Launching: %s on %s 3 42 14 vc501.xxx.xx 0 37 nsrvim -s puxxx -D 0 vc501.xxx.xx 12 14 vc501.xxx.xx
78827 1347880093 2 0 0 3236 2604 0 ba.xxx.xx nsrtask 23 [%s] Monitoring job: %d 2 42 14 vc501.xxx.xx 1 7 1248820
78831 1347880100 2 0 0 3236 2604 0 ba.xxx.xx nsrtask 7 [%s] %s 2 42 14 vc501.xxx.xx 0 49 nsrvim starting on vc501.xxx.xx (process 7916).
78831 1347880100 2 0 0 3236 2604 0 ba.xxx.xx nsrtask 7 [%s] %s 2 42 14 vc501.xxx.xx 0 37 Connecting to NetWorker on 'puxxx'.
78832 1347880104 2 0 0 3236 2604 0 ba.xxx.xx nsrtask 20 [%s] Task result: %s 2 42 14 vc501.xxx.xx 0 6 Failed
there is wrong servername "puxxx" because Networker server renamed.
Thank you
freenet