Dear CS contributors
We use CS 4.5.1 on a 3 Clusters with XenServer 6.5.
One Host in a cluster (and another in another cluster as well) got and
stayed in status "Disconnected".
We tried to unmanage/remanage the cluster to force a reconnection, we
also destroyed all System VM's (virtual cons
> We use CS 4.5.1 on a 3 Clusters with XenServer 6.5.
>
> One Host in a cluster (and another in another cluster as well) got
> and
> stayed in status "Disconnected".
use
xe host-list
to determine your disconnected hosts-uuid, and try to enable it via
xe host-enable uuid=NN
If the host is e
Dear CS contributors
We could fix the issue without having to restart the disconnected Xen Hosts.
We suspect that the root cause was a interrupted agent transfer, during
a restart of a Managment Server (CSMAN).
We have 3 CSMAN's running in cluster: man01, man02 and man03.
The disconnected vh0
Hi Francois,
As pointed out by Stephan the problem is probably with your Xen cluster rather
than your CloudStack management. On the disconnected host you may want to carry
out a xe-toolstack-restart - this will restart Xapi without affecting running
Vms. After that check your cluster with ‘xe h
Hi CloudStack Users and Developers,
we’re currently implementing a new CloudStack environment based on 4.8.0.1
(System VM Template is 4.6) with XenServer 6.5 SP1 and all the latest
updates.
So far everything works as expected we only have an issue regarding the
stability of Site-to-Site VPNs with
Dear Stephan and Dag,
we also thought about it and checked it but the host was already enabled on xen.
Best Regards
Francois
EveryWare AG
François Scheurer
Senior Systems Engineer
-Original Message-
From: Dag Sonstebo [mailto:[email protected]]
Sent: Thursday, July 21, 2016
Hey Francois,
here is some suggestion...
Did you have any load balancer in front of your 3 CSMAN servers? if so,
is there any persistence defined in your configuration ? Can you try to
set it to SourceIP and fix the timeout to something like 60 or 120 min ?
Also validate these points:
under
So far, I got something stable with this kind of setup :
RHEL 6.7 // Tomcat 6.0.24-94.el6_7 // java version "1.8.0_73"
...continuing to test...
Marcus
On 2016-06-10 4:10 PM, Yiping Zhang wrote:
RHEL 6.7 / java-1.7.0-openjdk-1.7.0.85-2.6.1.3 / tomcat6-6.0.24-90
On 6/10/16, 12:49 PM, "Marc-Andr
Hey guys,
I cannot find documentation on this topic. I have a zone created with
two public ip ranges. When I create a new network it always routes
through the first listed ip range. Is there a way in the UI to specify
the second ip range be used for a given network?
If not, do you know recor
Matthew,
When you add a public range, you have the ability to assign it to a domain and
account under that domain. That ip space will then be used for allocated for
that domain (or optionally a specific account under that domain).
- Si
From: Matthew Smart
Se
Ahh, got it.
Thanks!
Matthew Smart
President
Smart Software Solutions Inc.
108 S Pierre St.
Pierre, SD 57501
Phone: (605) 280-0383
Skype: msmart13
Email: [email protected]
On 07/21/2016 02:58 PM, Simon Weller wrote:
cated f
Hi, you could add the iptables command in rc.local or other startup script.
However, even though the workaround helps, that bug isn't completely correct.
The VR uses dnsmasq for DHCP, not isc-dhcp, so updating isc-dhcp on the VR
wouldn’t help.
This is more of an issue with the DHCP client.
12 matches
Mail list logo
