This post is more than 5 years old
99 Posts
0
820
Discovery failed in ECC for NAS celerra NS80
Hi There,
I tried discovering the NS80 from Control center 6.0 and I got this error.
Can anybody please let me know what this error means.
SESSION_ACTION: Discover [2] MO Type = NasContainer
Container_IP=xxx.xx.xxx.xxx | Container_Port=8000 | Container_Username=XXXXXXX | Container_Password=XXXXXX| Container_Type=Celerra
command status = finished, errors
objects found = 0 agents responding = 1
completed in 15 seconds
action begins at:XXXXXX
action ends at:XXXXXXX
Reported agent errors:
[1] ADAResult:
ADAErrorSet:9, Celerra@xxx.xx.xxx.xxx : Telnet::SendTelnetCmds - connect failed - WSAGetLastError: 10061
Responding agent persistent Id: 18176
Responding agents:
[1] {ID=18176} NAS Agent @ xxxxx.net
Thanks,
Bannu.
I tried discovering the NS80 from Control center 6.0 and I got this error.
Can anybody please let me know what this error means.
SESSION_ACTION: Discover [2] MO Type = NasContainer
Container_IP=xxx.xx.xxx.xxx | Container_Port=8000 | Container_Username=XXXXXXX | Container_Password=XXXXXX| Container_Type=Celerra
command status = finished, errors
objects found = 0 agents responding = 1
completed in 15 seconds
action begins at:XXXXXX
action ends at:XXXXXXX
Reported agent errors:
[1] ADAResult:
ADAErrorSet:9, Celerra@xxx.xx.xxx.xxx : Telnet::SendTelnetCmds - connect failed - WSAGetLastError: 10061
Responding agent persistent Id: 18176
Responding agents:
[1] {ID=18176} NAS Agent @ xxxxx.net
Thanks,
Bannu.
seamuscoffey
472 Posts
0
February 24th, 2009 14:00
This is some kind of connectivity issue between the NAS agent host and the Celerra Control Station.
Please check the following:
1) Celerra should be accessible via Telnet from the host running the NAS agent.
Make sure that you could telnet using the IP Address or hostname of the Celerra.
If not, enable telnet on the Celerra box using the following command.
"chkconfig telnet on"
2) Telnet to the control station and try executing the "nas_version" command.
This command or the telnet connection to the control station should not hang.
3) XHMP server should be running on the Control Station.
To check whether JServer is running, telnet to the control station and
do "ps -ef|grep jserv"
If you're still having issues, then please open a SR as Support will probably need to test connectivity via a debug XHMP tool.
Regards,
Séamus
Nathan_N_Anthon
17 Posts
1
March 17th, 2009 11:00