This post is more than 5 years old
2 Intern
•
306 Posts
0
1960
September 25th, 2008 06:00
Adding Celerra into Storage Scope and ECC
Need to get a new Celerra added into ECC and Storage scope. Went through the assisted discovery and received this message.
SESSION_ACTION: Discover [4] MO Type = NasContainer
Container_IP=172.22.117.118 | Container_Port=8000 | Container_Username=nasadmin | Container_Password=****** | Container_Type=Celerra
command status = finished, errors
objects found = 0 agents responding = 1
completed in 5 seconds
action begins at: Thu Sep 25 09:42:15 EDT 2008
action ends at: Thu Sep 25 09:42:20 EDT 2008
Reported agent errors:
[1] ADAResult:
ADAErrorSet:9, Celerra@172.22.117.118 : Telnet::SendTelnetCmds - connect failed - WSAGetLastError: 10061
Responding agent persistent Id: 107842647
Responding agents:
[1] {ID=107842647} NAS Agent @ mastor05.prod.ishealth.net
SESSION_ACTION: Discover [4] MO Type = NasContainer
Container_IP=172.22.117.118 | Container_Port=8000 | Container_Username=nasadmin | Container_Password=****** | Container_Type=Celerra
command status = finished, errors
objects found = 0 agents responding = 1
completed in 5 seconds
action begins at: Thu Sep 25 09:42:15 EDT 2008
action ends at: Thu Sep 25 09:42:20 EDT 2008
Reported agent errors:
[1] ADAResult:
ADAErrorSet:9, Celerra@172.22.117.118 : Telnet::SendTelnetCmds - connect failed - WSAGetLastError: 10061
Responding agent persistent Id: 107842647
Responding agents:
[1] {ID=107842647} NAS Agent @ mastor05.prod.ishealth.net
No Events found!
seamuscoffey
472 Posts
0
September 25th, 2008 07:00
Just wondering what version of ControlCenter you are running and what is the Storage Agent for NAS patch level?
I have seen a similar issue previously - you will almost certainly need to open a SR as there are more than likely exceptions/constraints being logged by the Store at the time of discovery. There may also be issues on the NAS Control Station with the Jserver.
Technical Support and/or Engineering may need to provide you with a debug XHMP discovery tool in order to further investigate the issue.
Regards,
Séamus Coffey
EMC Global Services
seamuscoffey
472 Posts
0
September 25th, 2008 08:00
It's the IP address of the Celerra Control Station.
Java version 6.0.0.0.357 is a little low (latest is 6.0.0.0.529) but shouldn't affect the NAS discovery; the latest Storage Agent for NAS is 6.0.0.0.105 and it does include a fix for Celerra NSX discovery failures.
Regards,
Séamus Coffey
EMC Global Services
DHoffman2
2 Intern
•
306 Posts
0
September 25th, 2008 08:00
DHoffman2
2 Intern
•
306 Posts
0
September 25th, 2008 08:00
seamuscoffey
472 Posts
0
October 6th, 2008 06:00
Has this issue been resolved?
Thanks,
Séamus Coffey
EMC Global Services
DHoffman2
2 Intern
•
306 Posts
0
October 14th, 2008 05:00
cincystorage
2 Intern
•
467 Posts
0
October 14th, 2008 06:00
From the ECC server open up a command prompt and cd to c:\ecc\exec\CNN600
then run:
emcplink.exe -ssh -l nasadmin -pw PASSWORD 10.10.20.30 -interactive
using your password and IP address. If that connects you, then in the console go to assisted discovery, NAS Container, and change the port to 443. Fill everything out and discover..
If that doesnt work let me know, and we can make sure jserv is working correctly...
Problem: telnet disabled using ssh
Fix: Change default port from 8000 to 443/22 and Celerra should be fully discovered