We have been having issues with our CSM 4.24 deployments to a specific 55xx ASA context, where all recent policy deployments are failing with the error "Unable to Communicate with Device" / "No response to connection attempts to this device". Another context on this same ASA is receiving policy deployments with no issue, no errors.
The thing is... The policy deployments to the "bad" context, other than this error, seem to be going through fine. The CLI transcript in the deployment info has nothing but "SUCCESS" and "OK". We can see in this transcript where the CSM server is changing from the admin context to the specific context in question, and it looks like everything is going perfectly okay. I confirmed through SSHing to the CLI that expected changes were made.
Note: A Powershell TCP Connection test from CSM server to the admin context of the ASA in question (x.x.x.x) via 443, is successful -
PS C:\WINDOWS\system32> New-Object System.Net.Sockets.TcpClient x.x.x.x,443
Client : System.Net.Sockets.Socket
Available : 0
Connected : True <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
ExclusiveAddressUse : False
ReceiveBufferSize : 131072
SendBufferSize : 131072
ReceiveTimeout : 0
SendTimeout : 0
LingerState : System.Net.Sockets.LingerOption
NoDelay : False
PS C:\WINDOWS\system32>
I did some searching online, and cannot find a similar situation. Anybody got any ideas? Another tech needs to look at this before we start a TAC case, so just wanted to run this by the discussion community first.
