Jason:
I think you've confused the C2 with the A2 which will never support this feature:
https://community.extremenetworks.com/extreme/topics/c2_b2_a4_a2_series_has_ssh_session_error_nonexi...
The C2 within its own release notes says that in version 5.02.16.0008
they believe the issue was resolved, though it doesn't seem to be. Note below our revision number: (connected using Netsight)
![41065662dc3541daaa93b03abf186e5f_RackMultipart20140923-20036-1b5vwoa-sshcapture_inline.jpg 41065662dc3541daaa93b03abf186e5f_RackMultipart20140923-20036-1b5vwoa-sshcapture_inline.jpg](/t5/image/serverpage/image-id/5568i8505C11C072CAD54/image-size/large?v=v2&px=999)
And now the error by connecting from Putty rather than Netsight:
![41065662dc3541daaa93b03abf186e5f_RackMultipart20140923-26444-10qvz75-sshcapture2_inline.jpg 41065662dc3541daaa93b03abf186e5f_RackMultipart20140923-26444-10qvz75-sshcapture2_inline.jpg](/t5/image/serverpage/image-id/5617iF5A5C2CF4A5B3585/image-size/large?v=v2&px=999)
I've figured out why launching SSH via Netsight works, apparently they've built in version 0.60 of Putty into Netsight which didn't suffer from this issue.
![41065662dc3541daaa93b03abf186e5f_RackMultipart20140923-21021-16ilx7s-netsightcapture_inline.jpg 41065662dc3541daaa93b03abf186e5f_RackMultipart20140923-21021-16ilx7s-netsightcapture_inline.jpg](/t5/image/serverpage/image-id/464i2CAE69FA969EF0EE/image-size/large?v=v2&px=999)
![41065662dc3541daaa93b03abf186e5f_RackMultipart20140923-20036-ufo5n5-puttycapture_inline.jpg 41065662dc3541daaa93b03abf186e5f_RackMultipart20140923-20036-ufo5n5-puttycapture_inline.jpg](/t5/image/serverpage/image-id/3086iA1B925EB7EA75C08/image-size/large?v=v2&px=999)
![41065662dc3541daaa93b03abf186e5f_RackMultipart20140923-29568-zubd6o-puttycapture2_inline.jpg 41065662dc3541daaa93b03abf186e5f_RackMultipart20140923-29568-zubd6o-puttycapture2_inline.jpg](/t5/image/serverpage/image-id/719i8880A50C4D9E0D33/image-size/large?v=v2&px=999)
So I think in short, the rather annoying workaround is to launch SSH via Netsight for the C2s. This way you can continue to use the latest and greatest for Putty for unaffected hosts and keep the benefit of SHA-256 instead of being forced down to SHA1 at best no matter your host's capabilities.