This was triggered by an error that both @ayounsi and I experienced attempting to connect to https://scs-oe11-esams.mgmt.esams.wmnet/

On FF and Chrome, it gives the error:

Secure Connection Failed

An error occurred during a connection to scs-oe11-esams.mgmt.esams.wmnet. Cannot communicate securely with peer: no common encryption algorithm(s). Error code: SSL_ERROR_NO_CYPHER_OVERLAP

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

It gives an option to try again, but nothign to override. Safari doesn't have the issue.

Mentioned in SAL (#wikimedia-operations) [2017-09-11T18:10:24Z] <robh> scs-ulsfo has successfully updated firmware T174475

Mentioned in SAL (#wikimedia-operations) [2017-09-11T18:29:40Z] <robh> firmware update on scs-a1-codfw and scs-c1-codfw has been started, awaiting completion T174475

Mentioned in SAL (#wikimedia-operations) [2017-09-11T18:33:30Z] <robh> firmware update on scs-a1-codfw and scs-c1-codfw has been complete and tested good T174475

I've created a sub-task to troubleshoot scs-c1-eqiad. I'm not sure of the status of the two additional scs consoles in esams.

@mark: I've updated the firmware and tested it as functioning on scs-oe11-esams. I cannot see any dns or setup for scs-oe10-esams or scs-oe16-esams. I'm guessing these are old scs that are now defunct, but I'm not sure and wanted to see if you knew?

Mentioned in SAL (#wikimedia-operations) [2020-03-03T18:11:07Z] <robh> updating firmware on scs-oe16-esams via T174475