If you are not registered:

Register Now


Please do not hesitate to contact us if you have any queries, or visit our website:

Visit our Website

Email our helpdesk

Call us
General enquiries: 0845 123 2222
Support: 0845 123 2229
Fax: 0845 123 2221


Node4 status page detailing information about incidents and planned maintenance:


NetApp OnCommand System Manager & Java 8: Error 500 (Connection Refused)
Posted by Matthew Geck on 11 October 2017 05:51 PM

When upgrading Java to version 8 or higher, you may find that NetApp OnCommand System Manager client fails to authenticate against any controllers and throws an "Error 500 (Connection Refused)" error.


To resolve this, you'll need to take the following steps:

N.B. all commands shown below are to be used whilst connected to the controller(s) via SSH.


1) Update your NetApp OnCommand System Manager client to the latest release client available from NetApp (http://support.netapp.com).


2) Enable TLS on all controllers you plan to manage via OCSM using one of the methods below.

7-Mode: options tls.enable on

CDOT: system services web modify –tlsv1-enabled true


3) Regenerate the SSL certificate on each controller, setting the key length to 2048. This is required as Java 8 will not communicate with any device/site covered by an SSL with a key length of less than 1024-bits.

7-Mode: secureadmin setup ssl (when running through this wizard the default values are shown in square brackets.)

CDOT: security certificate create -vserver <vserver> -common-name <clustername.domain> -size 2048 -country US -state California -locality San Jose -organization NetApp -unit Storage -email-addr support@netapp.com -expire-days 3650 -hash-function SHA256


Once complete, you should find that you can manage the controller via OnCommand System Manager without encountering any further errors.




(17 vote(s))
Not helpful

Comments (0)
Post a new comment
Full Name: