[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-tabpanelfocusedCommentId=13654377#comment-13654377 ] ASF subversion and git services commented on CLOUDSTACK-2035: - Commit c704c90b1163d0f3386370e75fc5903dd76498c5 in branch refs/heads/master from [~koushikd] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c704c90 ] CLOUDSTACK-2035: Fix source NAT configuration with Cisco VNMC/ASA Due to VNMC limitation source nat ip cannot be assigned to ASA 1000v outside interface. Working around this issue by acquiring additional public ip during network implement and assigning that to outside interface of ASA. Also made changes to ensure that source nat policy comes after pf and static nat policies in terms of evaluation by assigning a high 'order' value for it. 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
[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-tabpanelfocusedCommentId=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
[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-tabpanelfocusedCommentId=13644636#comment-13644636 ] Koushik Das commented on CLOUDSTACK-2035: - Out of office till 5/3. 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
