[
https://issues.apache.org/jira/browse/CLOUDSTACK-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658337#comment-13658337
]
Koushik Das commented on CLOUDSTACK-2169:
-----------------------------------------
Since this is a limitation of the ASA appliance there is no need to change the
code to handle this. In future once these issues are addressed by Cisco there
won't be any need to reset ASA appliances explicitly. Also in order to enable
executing these comands from code, SSH needs to enabled on the ASA appliances
and the credentials needs to be stored in Cloudstack database.
For now the steps to reset ASA to factory settings needs to be documented and
if there is an issue while reusing the ASA appliance in a new isolated guest
network only then should this workaroud be applied. Since not doing any code
changes marking it as a doc issue.
> Reset ASA 1000v appliance to factory setting as part of guest network cleanup
> -----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2169
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2169
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc, Network Devices
> Affects Versions: 4.2.0
> Reporter: Koushik Das
> Assignee: Koushik Das
> Fix For: 4.2.0
>
>
> Expected behavior is that ASA 1000v should get cleaned up properly when
> logical edge firewall is cleaned up in VNMC. But due to some issue with the
> VNMC sometimes the cleanup doesn't happen. If the cleanup doesn't happen then
> the ASA 1000v cannot be reused in a new guest network.
> So the ASA 1000v needs to be cleaned up explicitly using some CLI commands.
> As part of this SSH needs to be enabled on the ASA by the admin outside of CS
> and store the SSH credentials with CS while registering ASA.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira