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-7028) Static NAT does not work after the fail-ove
Date Tue, 01 Jul 2014 09:50:24 GMT

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

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

Commit e336796cd5eae39bf7755d981426160a15bc6e9f in cloudstack's branch refs/heads/4.4-forward
from Jayapal
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e336796 ]

CLOUDSTACK-7028: Fixed adding route for additional public nic on fail over


>  Static NAT does not work after the fail-ove
> --------------------------------------------
>
>                 Key: CLOUDSTACK-7028
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7028
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.0.0
>            Reporter: Jayapal Reddy
>            Assignee: Jayapal Reddy
>             Fix For: 4.4.0
>
>
> On fail over, in master router route got missed.
> Reproducing steps:
> 1. Create RVR network and acquire additional public ip range (ex: 47 vlan and 10.147.47.x
subnet)
> 2. create a static nat rue on additional range public ip and add firewall rule for port
22-22
> 3. ssh to public ip, it get connected to vm
> 4. Now make master VR down, backup wil become master.
> 5. On master router on eth3 there default route got missed, which is causing the ingress
traffic is coming to eth3 is going out via eth2.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message