Customer discovered that after upgrading from Management Center (MC) 1.9.1.x to 184.108.40.206 they where no longer able to add certain ProxySGs to MC.
ProxySG SGOS 220.127.116.11
GUI returns the error message
"The operation has timed out"
when trying to test the connection to the ProxySG.
The sg.log (when set to debug level) shows
[2018-07-09 15:24:04.176] WARN TimeoutFactory-watchdog-00 com.bluecoat.cm.device.sgos6x.command.SshjSshSession SG SSH connection timed out. Closing client. Expect a subsequent trace.
[2018-07-09 15:24:05.201] DEBUG eviceJobExecutor-worker-0133 com.bluecoat.cm.device.sgos6x.command.SshSessionFactory ssh://192.168.1.2:22 - Creating session
[2018-07-09 15:24:09.467] WARN https-jsse-nio-8082-exec-5 com.bluecoat.cm.device.sgos6x.command.SshSessionFactory Error while checking if session ssh://192.168.1.3:22 was released in enable mode. Abandoning session. java.util.concurrent.TimeoutException: Timed out while waiting for one of ["#"]
The customer had set up a banner page for ssh logins which included reserved characters
"########## You are connected to ProxyA! ###########"
As of MC 1.11 the hashes (#) in the banner (or the ProxySG name) will prevent MC from completing the logging process to the ProxySG
Remove the banner login or remove the hashes from the message
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
Subscribed to the Article.
Unable to subscribe
Thanks for your additional feedback !!!
Enterprise Support Virtual Agent
Rate Me :
Tell us more:
Welcome! My name is Sami, the Enterprise Support Virtual Agent answering technical support questions.