cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2812) Static NAT rules are created with same name and Destination IP Pool for each Public IP with which only one instance is reachable with both Static NATed IP's
Date Wed, 05 Jun 2013 10:13:19 GMT

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

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

Commit 9f18f1cb1cb4c11b61b687e745ef126775526b60 in branch refs/heads/master from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9f18f1c ]

CLOUDSTACK-2812: Static NAT rules are created with same name and Destination IP Pool for each
Public IP with which only one instance is reachable with both Static NATed IP's
For static NAT rule an IP pool gets created in VNMC. In order to make the pool name unique
the rule id is appended. Since static NAT rules are not stored in CS db. like PF/FW rules,
the id was always set to 0.
As a result the pool was always getting overridden everytime a static NAT rule is created.
Fixed it by appending the public IP address id along with a character indicating that the
pool is used for static NAT rule to the pool name.

                
> Static NAT rules are created with same name and Destination IP Pool for each Public IP
with which only one instance is reachable with both Static NATed IP's 
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2812
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2812
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller, Network Devices
>    Affects Versions: 4.2.0
>            Reporter: Sailaja Mada
>            Assignee: Koushik Das
>            Priority: Critical
>         Attachments: vnmc1.png, vnmc2.png, vnmc3.png, vnmc4.png
>
>
> Steps:
> 1. Configure Advanced Networking zone with VMWARE Nexus enabled cluster 
> 2. Add Cisco VNMC,ASA firewall devices 
> 3. Create Network offering with Cisco VNMC provider as (Source NAT, PF,Firewall,Static
NAT )
> 4. Deploy two Instances using this network 
> 5. Acquire 2 new public IP's and configure Static NAT Rule with Public IP1 -> VM1
&  Public IP2 -> VM2
> 6. Add Firewall rules to allow from all 
> 7. Try to Access Instance 1 , It is accessible thru Public IP1 & Public IP2.  Instance
2 is never accessible .
> Observation:
> Static NAT rules are created with same name and Destination IP Pool for each Public IP
with which only one instance is reachable with both Static NATed IP's  
> (Attached all the snaps')

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

Mime
View raw message