Wired Intelligent Edge

 View Only
last person joined: 20 hours ago 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Expand all | Collapse all

Procurve 5412zl - HTTPS web admin no longer working after update to K.16.01.004

This thread has been viewed 0 times
  • 1.  Procurve 5412zl - HTTPS web admin no longer working after update to K.16.01.004

    Posted Feb 08, 2016 02:27 PM

    After updating to firmware K.16.01.0004, our 5412zl's https web admin is no longer accessible. Using all of the major browsers, I receive a TLS error. I have recreated the self-signed certificate but that did not help.

    An example of the error I get is "The server rejected the handshake because the client downgraded to a lower TLS version than the server supports."

    Any help would be appreciated.


    #ProCurve
    #5412zl


  • 2.  RE: Procurve 5412zl - HTTPS web admin no longer working after update to K.16.01.004

    EMPLOYEE
    Posted Feb 09, 2016 01:14 PM

    Hello.  Any current browser should support TLS 1.2 and that should get chosen.  We tested all the major browsers with newly generated self-signed certs and did not see any issues.  Can you reply with the browser/versions/certifcate you used?

    There is a newer config command: "tls application web-ssl lowest-version" where you could try setting the lowest version to 1.0 and see if that works.  Wouldn't recommend using 1.0 as a long term solution but it may help identify what the problem is.

     



  • 3.  RE: Procurve 5412zl - HTTPS web admin no longer working after update to K.16.01.004

    Posted Feb 10, 2016 11:38 AM

    We are using Firefox 45, Safari 9.03 and Chrome 48.



  • 4.  RE: Procurve 5412zl - HTTPS web admin no longer working after update to K.16.01.004

    Posted Feb 10, 2016 11:43 AM

    Issue was in "crypto suiteB-MinLoS 128 tls". We had it set to strict and that caused problems. Once we removed the stict, everything started working at TLS 1.2