2014-10-20 06:41 AM - edited 2014-10-20 07:04 AM
Good day, i am running OnCommand System Manager ver 3.1.1 on Windows.
Today, for the very first time, i have seen this issue: i can connect to my 3210 running DataONTAP 8.0.3P2 7-mode, but when i try to reach my new 2240 running DataONTAP 8.1.3P3 7-mode i recieve an error 500 "connection refused".
I have found this workaround: on the 2240s i have issued the command >options httpd.admin.enable on ;
after this the OnCommand System Manager probably still tries a secure connection, on the console i see errors like
[hostname: HTTPPool03:warning]: HTTP XML Authentication failed from MyClientIP .
But now i guess OnCommand System Manager falls back to a non secure connection, i see the question "do you want to set up a secure connection or continue without...", i answer "continue without" and i'm able to manage my filers again.
What's happened? Maybe something java updates related? Thanks in advance.
2014-12-29 12:43 AM
Good Morning everyone!
Im struggling with the same issue.
Is there a workaround or a fix to this problem?
My java-client version is 7.45 due to the fact, that we need this exact version for some other applications here.
But if the only way to get the OnCommandSystemmanager working again is to update java, surely i will do the update.
Thanks in advance!
2014-12-29 12:54 AM
I just updated Java to the latest version and this issue is solved.
It seems to be java related.
This is working for OnCommandSystemmanager version 3.1.1 and 3.1.2
2015-01-01 10:11 AM
I have written 2 KB's related to this issue:
KB ID: 2021850
OnCommand System Manager is unable to authenticate clustered Data ONTAP using secure protocols when Java 8u25 is installed on the host
KB ID: 2021507
OnCommand System Manager 3.1 and 3.1.1 do not function when using Java 8.x
2015-01-22 04:48 AM
I am using OCSM 3.1.1RC1 as well and got upgraded to Java 8 update 31 and am having the same issues with SSL. I also change the .exe with the .jar version and still have the same issues. I uninstalled Java 8 and reverted back to Java 7u75 but that didn't seem to work either. I'm stumped.
2015-01-22 10:32 AM
Exact same thing here...Removed all traces of Java 8, installed 7u75, got the System Manager to install but cannot connect to anything. Just error 500. Another user here is able to connect without any problems.
2015-01-22 10:59 AM - last edited on 2015-02-04 06:37 AM by alissa
I ended up installing Java 8 U 31. Reinstalled OnCommand System Manager 3.1.1RC1 which kept all my filers. But when I try to run the Network Config Checker I get the enclosed errors. When I try to login to the filer themselves I get the other enclosed screenshot. The only thing that changed was the Java upgrade.
I can't seem to find anyone else with this exact type of issue though.
2015-01-23 05:20 AM
I have had the same issue. If you are experiencing error 500 and are using Windows 7 Enterprise x64 try uninstalling all versions of Java and then install J7 U45 x86 and then J7 U71 x64 then install OCSM 3.1.1.
I had later versions of Java (x86/x64) and OCSM wouldn't launch.
2015-01-26 04:22 AM
I experienced similar issues when I inadvertently updated my to a Java 8 version.
As previously suggested I did the following to resolve the issue.
- uninstalled OCSM
- uninstalled all Java versions
- reinstalled Java 7 u51
- reinstalled OCSM
It seems to be the case that later versions of Java 7 and especially version 8 are incompatible.