Hi, Cristian
All of my operation are in vRouter.
Now, inside vRouter I can ping 192.168.85.202(vRouter's public ipaddress,
eth2) successfully after added firewall rules in UI. But ping public gateway
192.168.85.2 still failed.
Frank
frankpers...@gmail.com
From: Cristian Cio
Hi Frank,
My question is:
1. Did you used Basic Network for deploy ?
2. Can you please type the following command on VR : "ip a" and provide
the output.
Regards,
Cristian
On 29.01.2016 10:20:36, frankpers...@gmail.com wrote:
Hi, Cristian
All of my operation are in vRouter.
Thank you Lucian, I will try it and let you know if worked for me.
El vie., 29 ene. 2016 a las 2:25, Nux! () escribió:
> Hello Sebastian,
>
> Cloudstack creates a new bridge because it's standard behaviour if you
> mention a VLAN number when you add the public network details.
>
> I believe you
Hi, Cristian
1. Advanced Network
2. type "ip a" on VR, I get following:
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 02:00:22:2e:00:0
Hi, I'm new to Linux and CloudStack and would appreciate any support here
CS 4.7 Ubuntu 14.04
PC A - management server
PC B - host
PC C - host
The management server managed to connect to PC B, making it a host.
But I'm getting an 'Authentication Error' when adding PC C. The
username/passwd shou
Hello,
Can you test manually if that agent machine can access the management one on
that port?
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Syafiq Rokman wrote:
> Hi, I'm new to Linux and CloudStack and would appreciate any support here
>
> CS 4.7 Ubuntu 14.
Hello,
If you want your gateway to be reachable you can configure this IP :
192.168.85.2 on a virtual NIC/Private NIC depends of your configuration.
My default gateway is configured on Cloudstack management server as private
IP ( in my case i have to interfaces on management server public
Dear Glenn
Thank you very much.
I checked your suggestion.
>Check that the vhd-util is the correct version from cloudstack
>Run a md5sum on the vhd-util
It is the correct version.
>Also check that the master and slave can access the secondary storage properly
It is no probrem.
the master and s
It worked for me!
Oh my God, I spent lot of time trying to solve it.. Thank a lot!
El vie., 29 ene. 2016 a las 9:44, Sebastian Gomez ()
escribió:
> Thank you Lucian, I will try it and let you know if worked for me.
>
>
>
> El vie., 29 ene. 2016 a las 2:25, Nux! () escribió:
>
>> Hello Sebast
Hi All,
Getting same issue (http://picpaste.com/pics/VPC-rhH48Qao.1454066282.PNG) with
below stable/latest builds of System VM Template.
http://jenkins.buildacloud.org/job/build-systemvm64-master/lastStableBuild/artifact/tools/appliance/dist/systemvm64template-master-4.6.0-xen.vhd.bz2
http://
Hi Suneel,
If you want to upgrade, use 4.7.1 instead of 4.6.x as many bugs have been
fixed. In another thread we discussed a timeout setting you can bump to make it
work, too.
Regards,
Remi
On 29/01/16 12:17, "mvs babu" wrote:
>Hi All,
>
>Getting same issue (http://picpaste.com/pics/VPC-r
Hi Remi,
Thanks for suggestion, sure we will test with 4.7. But, there is no System VM
Template available for 4.7.
Thank you,
Suneel Mallela
AxiomIO.
From: Remi Bergsma
Sent: Friday, January 29, 2016 5:45 PM
To: users@cloudstack.apache.org
Cc: d...@cloudstack.apache.org
Hi
You can use the 4.6 version in 4.6, 4.7 and 4.8.
On 29/01/16 13:24, "mvs babu" wrote:
>Hi Remi,
>
>Thanks for suggestion, sure we will test with 4.7. But, there is no System VM
>Template available for 4.7.
>
>
>Thank you,
>Suneel Mallela
>
>AxiomIO.
>
>
>
>From: Remi Bergsma
>Sent: Friday,
Suneel,
The 4.6.x virtual routers work with 4.7+ now. The new method of pushing
features into the virtual routers is to utilize the mounted ISO for deployment.
Not having to upgrade the routers with every release saves a huge amount of
time and also simplifies deployment of new releases.
- Si
Hi, Cristian
Thank you very much, I will try and to fix it.
frankpers...@gmail.com
From: Cristian Ciobanu
Date: 2016-01-29 17:53
To: users@cloudstack.apache.org
Subject: Re: Re: vRouter ping it's public ipaddress failed
Hello,
If you want your gateway to be reachable you can configure
Sure, I will test with 4.7.1 and get back with status.
Simon, I din not get you on below, can you please elaborate it.
“The new method of pushing features into the virtual routers is to utilize the
mounted ISO for deployment”
Thank you,
Suneel Mallela
AxiomIO
From: Simon Weller
Sent: Fr
Hi,
This applies to CloudStack 4.6.
The scenario: have one zone installed, and you want to delete the zone.
Doing this requires deletion of everything under the host. When the system
VMs are destroyed, their volumes go into Destroy state. The storage cleanup
thread is constantly trying to expunge
No problem. Which solution did you go for?
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Sebastian Gomez"
> To: users@cloudstack.apache.org
> Sent: Friday, 29 January, 2016 10:43:07
> Subject: Re: cloudstack-agent 4.5 problem with c
Hello,
I have the same issue again, vCenter stop to be reachable from SSVM, when I
try to create a template or VM deploy from template, everything is ok when i
create deploy from ISO, in this case i think the issue was not related to IP
class.
Also i'm able to ping vCenter from SSVM afte
Hi All,
Sorry didn't particpate discussion. Got pretty big issue with the cloud
yesterday. Very intersting one.
I have 2 networks with 2 dedicated VR (not VPC). One of the netowork with
default gateway, the second one just for internal interconnect between VMs.
Both network are IsolatedWithNoSNA
Mohd,
I dont agree with you. Thats a very generalized statement.
We put a lot of effort to make sure upgrades are working as expected and
you can move forward from any version to any version.
With that said, if you have specific problem - you need to file a bug
and reach out to dev list.
Rui,
21 matches
Mail list logo
