2016-02-28 07:02 PM - last edited on 2016-03-04 07:38 AM by alissa
As the title says, we cannot log in to the management system and we receive a 500 refused message. Sometimes we are able to log in to one controller but never two any more. No changes have been made to the configuration. The issues began when I upgraded my oncommand app. to 3.1.2. Rolling back did not help. I assumed it was a local PC issue with java or my browser and so I built a fresh VM install of Windows 7 but no matter what I try in terms of java version or oncommand version I still cannot log in, even with a vanilla Windows 7 install.
As I'm a bit stuck, does the community have any pointers which I could try? The FAS's are coming up to 3 years old now, and they've not had any software upgraded either. I'm not sure if this is the cause.
Solved! SEE THE SOLUTION
2016-02-28 07:24 PM
Refer KB https://kb.netapp.com/support/index?page=content&actp=LIST&id=2021507 (requires login)
2016-02-28 07:41 PM
Thank you, thank you!
Can you please tell me one last thing, after running those commands at the CLI - do I need to "save" the configuration? If so, then please let me know how?
2016-02-28 08:13 PM
Once you run the commands, those settings will be saved automatically.
1. Solution hyperlink is dead.
2. 500 connection refused brings up tons of hits on NetApp website
3. Clicking on these so called solutions just has links to other docs which have further links.
4. Finally I end up on a doc that has a supposed solution. The solution reads:
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
POOR NetApp. VERY POOR!