Hi all,
#ccc2016mtl is off to great start! We had a productive round table
discussion this afternoon. You can find the notes from the discussion here
[1] and the recording of the session will be posted soon.
Tomorrow's talks will be live streamed and recorded. You can watch them
here: http://ca
Thanks for the logs Cristian,
You just forgot to include the : /var/log/cloud.log available on the
VR... ;)
Also, quite Interesting to see that your VM can communicate with ACS
correctly...
Can you try to reproduce it again but this time with the default VM (
ie: CentOS 5.6... ) Just want
Hi Marcus,
I just reproduced this error, by removing an old VM (with and IP from
previous class ) also exported the last part from log :
VR LOG : hxxp://pastebin.com/TH8CcEL6
Very interesting is what I saw on VM :
VM LOG : hxxp://pastebin.com/dn6Du4ci ( in order to grab
when your condition happen, is there any errors in the
/var/log/cloud.log of your VR ?
Marcus
On 2016-06-01 12:21 PM, Cristian Ciobanu wrote:
Hi Marcus,
Ok, please see, i also attached screenshots.
1. Yes, i'm using CloudStack 4.5.2 with Vmware 5.5 update3
2. vC
Hi Marcus,
Ok, please see, i also attached screenshots.
1. Yes, i'm using CloudStack 4.5.2 with Vmware 5.5 update3
2. vCenter version : hxxp://imgur.com/tcjY4kS
3. Host version : hxxp://imgur.com/ZIDKqWe
4. 2X NIC/hypervisor : hxxp://imgur.com/UefelGO
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). Yo
Hey !
Ok, At this point, I will need a bit more info then... so far, looks
like the public core router can see correctly both public ip range and
route them correctly...
You mention that you're using Cloustack 4.5.2 wuth Vmware 5.5
- vmware : which latest fix / patch level installed ?
- app
Hello
I have been hitting problems with Network ACL rules in VPCs with 4.7 (
looked at the code for 4.8 and it looks similar). It seems that the rule
ordering is actually inverted on the VR. So the rules with higher rule
numbers are getting checked before the lower ones. As an example, this can
be
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: Ven
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.
thank you my friend
Best regards,
On Thu, May 26, 2016 at 11:04 AM, Mohd Zainal Abidin Rabani <
zai...@nocser.net> wrote:
> Hi,
>
>
>
> On primary storage I have set NFS. The question is how to set use NFS when
> creating disk size under Disk Offering under Service Offerings?
>
>
>
> Thanks.
>
>
11 matches
Mail list logo
