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

ASF subversion and git services commented on CLOUDSTACK-3115:
-------------------------------------------------------------

Commit 75c3facb43659a7e01c072309244e077e81dfa59 in branch refs/heads/master 
from [~radhikap]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=75c3fac ]

CLOUDSTACK-3115 vnmc limitations

                
> [DOC] Cisco VNMC provider known issues to document 
> ---------------------------------------------------
>
>                 Key: CLOUDSTACK-3115
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3115
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Doc
>    Affects Versions: 4.2.0
>            Reporter: Sailaja Mada
>            Assignee: Radhika Nair
>             Fix For: 4.2.0
>
>
> Please find the list of known issues with CISCO VNMC provider (ASA 1000v 
> firewall) to document:
> 1. Public IP address range should be from single subnet. Its not allowed to 
> add from different Subnet
> 2. One ASA instance per VLAN - Cannot trunk multiple vlans to asa ports
> 3. Auto Spin of ASA instance is not supported
> 4. When guest network with CISCO VNMC is provider, By default an additional 
> public IP gets acquired along with Source NAT which is used for ASA outside 
> IP. This should not be released. This is required as there is a config issue 
> in ASA if source NAT ip is used as ASA outside ip
> 5. No Side by side support for LB , Only inline
> 6. CISCO ASA firewall is not Supported in VPC
> 7. CISCO ASA is only supported with isolated guest networks in advanced zone
> 8. Load Balancing is not certified with Cisco ASA firewall
> 9.In ASA the firewall rule is not tied to the specific public ip. i.e the 
> destination filter ip is ‘Any IP’

--
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

Reply via email to