Solved!
Go to SolutionNS20 - Control Station connection state "Inaccessible"
Within the last week, the control station has had the disconnected icon in Navisphere (CS is currently running Unisphere). I have manually restarted both SPA and SPB, which removed the disconnected status, but I am still unable to access Unisphere on the host IP. The status in Navisphere is "Host Agent not reachable" and showing "Inaccessible" as the connection state. I've also connected to the NS20 via serial to verify settings and it appears that the config is fine, including the NTP settings.
I'm kind of stuck at this point.
853
0
Posted November 19th, 2013 08:00
Can you tell me how you are trying to access the Unisphere and also where exactly you are getting 'inaccessible' message ?
Please put a snap if possible.
Are the shares/exports accessible ? I believe your data movers are having connectivity issue.
853
0
Posted November 19th, 2013 08:00
Hi Vipin, I'm trying to access via both the IP and FQDN in IE 9 (https). We can access our NFS/CIFS fine and the replications are still replicating on our DR site (NS120).
This is the logon screen after Java loads:
Navisphere:
853
1
Posted November 19th, 2013 11:00
Use
server_date server_2 timesvc
to see your confiugration, you should have some hosts set. If you don't, use a command such as
server_date server_2 timesvc start ntp interval 04:00 (hours:minutes interval) < >
and that will schedule your ntp polling interval. Of course make sure your NTP source is configured correctly as well.
853
0
Posted November 19th, 2013 11:00
Are you able to connect to the CS by ssh?
853
0
Posted November 19th, 2013 11:00
Yes, SSH works to the CS.
Though, as I look at the image, I see the year and date are incorrect.. Hmm.
853
0
Posted November 19th, 2013 12:00
Thank you, I was see that the CS and SPs were off by an hour. I just changed the time on the CS and restarted the management servers and the CS now. Same issue though. Otherwise, NTP configuration is correct and CS now has the correct date and time
jdugas1
5 Posts
853
0
Posted November 27th, 2013 11:00
The issue was as simple as an expired certificate. Generated a new one and it solved the problem.