Hi Venkat,

You can also check on your VPC if there's any IPSEC negociation errors there...

log on your VPC and check in :
/var/log/cloud.log
/var/log/daemon.log

Marcus
On 2016-06-01 9:45 AM, Timothy Lothering wrote:
Hi Venkat,

IPSEC VPN is established with the VPC (in your case the /16). Your Tier
(/24) is in this supernet, so you should be able to route to it once the
tunnel is up.

Make sure to specify the supernet (/16) on the remote VPN appliance as the
destination.



-----Original Message-----
From: Venkat Boggarapu [mailto:[email protected]]
Sent: Wednesday, 01 June 2016 2:50 PM
To: [email protected]
Subject: SITE TO SITE VPN ERROR IN OUR ENVIRONMENT with CLOUDSTACK-4.3.1 AND
XENSERVER 6.2

Hi Team,

In our environment we are using cloudstack-4.3.1 and xenserver 6.2

We have created  VPC router with  SUPER-CIDR value as X.X.X.X/16.

After creating VPC router, created a new TIER with X.X.X.X/24 with the same
network, gateway.

Finally we are unable to configure the IPSEC with the X.X.X.X/24, but we
have successful configured IPSEC with X.X.X.X/16.

Please help me guys, I was wonder why it's working with SUPER-CDIR
(X.X.X.X/16) with IPSEC.

Thanks,
Venkat Boggarapu



Reply via email to