I am also seeing this issue https://issues.apache.org/jira/browse/CLOUDSTACK-8823. This is a blocker for regular isolated network as VR is not coming to 'up' state due to ssh failure.
-----Original Message----- From: Bharat Kumar [mailto:bharat.ku...@citrix.com] Sent: Thursday, 3 September 2015 15:44 To: dev@cloudstack.apache.org Subject: Re: [Blocker/Critical] VR related Issues Hi, found few more issues related to rvr in isolated networks. There seems to be a problem with the keepalived config and setting up of default routes when rvr changes states. created bugs for these issues. CLOUDSTACK-8798<https://issues.apache.org/jira/browse/CLOUDSTACK-8798> CLOUDSTACK-8799<https://issues.apache.org/jira/browse/CLOUDSTACK-8799> Thanks, Bharat. On 12-Aug-2015, at 10:52 am, Bharat Kumar <bharat.ku...@citrix.com<mailto:bharat.ku...@citrix.com>> wrote: Hi, looks like there is one more issue. Conntrackd fails to start in case of rvr enabled isolated networks. created a bug to track this. https://issues.apache.org/jira/browse/CLOUDSTACK-8725 Thanks, Bharat. On 11-Aug-2015, at 3:03 pm, Kishan Kavala <kishan.kav...@citrix.com<mailto:kishan.kav...@citrix.com>> wrote: Below VR related issues currently open. Most of these issues did not exist in 4.5.x and are related to VR refactor (persistent VR). Blocker https://issues.apache.org/jira/browse/CLOUDSTACK-8690 - Remote Access VPN not working Critical https://issues.apache.org/jira/browse/CLOUDSTACK-8688 - Default policy for INPUT and FORWARD chain is ACCEPT in VR filter table (Wilder is working on this) https://issues.apache.org/jira/browse/CLOUDSTACK-8681 - CS does not honor the default deny egress policy in isolated network https://issues.apache.org/jira/browse/CLOUDSTACK-8710 - site2site vpn iptables rules are not configured on VR https://issues.apache.org/jira/browse/CLOUDSTACK-8685 - Default route is not configured on VPC VR https://issues.apache.org/jira/browse/CLOUDSTACK-8694 - Monitor service cron job not visible
