cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sheng Yang (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-687) s2s VPN error
Date Tue, 08 Jan 2013 20:36:12 GMT


Sheng Yang commented on CLOUDSTACK-687:

I've checked the code, for error message: The selected VPC does not have a VPN gateway. Please
create a VPN gateway for the VPC first.

Found it's not in API level(so not in the mgmt server log), it's in UI part. Seems UI failed
to get VPN gateway for current VPC.

Did you see the VPN gateway in the site-to-site VPN page? I mean, not from db, but from UI.
It should show one entry in the UI, including the IP of the VPN gateway(and you need that
IP to config the remote peer I think).
> s2s VPN error 
> --------------
>                 Key: CLOUDSTACK-687
>                 URL:
>             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.0.0, 4.0.1
>         Environment: сurrent CloudStack 4.0.1 build 11 from jenkins
> previous Cloudstack 4.0 build 1234  from jenkins
> CentOS 6.3 x86_64 (KVM)
> Advance Zoning
>            Reporter: Richard Shevel
>         Attachments: 1.png, 2.png, 3.png, catalina.out, management-server.rar
> The problem with s2s VPN
> At the remote site Cisco
> Follow all the instructions:
> 1. Create a VPC - done (Default - System Offering For Software Router)
> 1a. Create Tier (
> 2. Create a customer VPN gateway. - Done
> IKE policy 3des-sha1; modp1024
> IKE policy 3des-sha1; modp1024
> ESP policy 3des-sha1
> IKE lifetime (second) 86 400
> ESP Lifetime (second) 28 800
> Dead Peer Detection Yes
> 3. Create a VPN gateway for the VPC. - Fail
> see screenshot
> I rebooted the management server multiple times, delete and create new VPN, but the problem

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:

View raw message