(Cloud) Cisco ASA failing over to different data center instead of another data pod
Last Updated May 13, 2017
The Cisco ASA is failing over to another data center instead of failing over to another data pod within a data center
This issue can be caused by the following command in the ASA's configuration:
set connection-type originate-only
Per Cisco documentation, this command "...specifies that this peer [the ASA] initiates the first proprietary exchange in order to determine the appropriate peer to which to connect." In other words, if the remote peer tries to initiate the connection, the ASA will not honor the request.
Blue Coat recommends removing the originate-only portion of the command. The command defaults to bidirectional.
Imported Document ID: 000008579
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe
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.