You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Abhinandan Prateek (JIRA)" <ji...@apache.org> on 2014/09/01 07:25:22 UTC
[jira] [Updated] (CLOUDSTACK-7028) [RVR] Static NAT does not work
after the fail-over in additional public range
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhinandan Prateek updated CLOUDSTACK-7028:
-------------------------------------------
Labels: AUTOMATION_REQ DEVREV (was: AUTOMATION_REQ DEV_REVIEWED)
> [RVR] Static NAT does not work after the fail-over in additional public range
> -----------------------------------------------------------------------------
>
> 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
> Labels: AUTOMATION_REQ, DEVREV
> 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.3.4#6332)