You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Koushik Das (JIRA)" <ji...@apache.org> on 2013/05/09 15:29:16 UTC

[jira] [Commented] (CLOUDSTACK-2035) Fix source NAT configuration with Cisco VNMC/ASA

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652953#comment-13652953 ] 

Koushik Das commented on CLOUDSTACK-2035:
-----------------------------------------

There is a limitation in Cisco VNMC where in the source NAT ip for isolated guest network cannot be used as the outside interface IP of the ASA appliance. Doing this results in config failure in VNMC appliance.
In order to work around this limitation, when the network gets implemented an additional public ip (from same subnet as source nat ip) will be acquired and assigned to outside interface of ASA.

This public ip will be similar to an explicitly acquired public ip.
                
> Fix source NAT configuration with Cisco VNMC/ASA
> ------------------------------------------------
>
>                 Key: CLOUDSTACK-2035
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2035
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Devices
>    Affects Versions: 4.2.0
>            Reporter: Koushik Das
>            Assignee: Koushik Das
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Fix source NAT configuration with Cisco VNMC/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