I suspect network offering isolation guarantees (dedicated/shared) for load
balancer did not match up with the NetScaler resources provisioned in the
deployment. Please refer to
http://wiki.cloudstack.org/pages/viewpage.action?pageId=1344581 for the device
allocation logic
You can try out cr
I put it on the Community page
http://goo.gl/4V94A
On 4/26/12 11:57 AM, "Marlon Davids" wrote:
>Brilliant, thanks Chiradeep,
>
>
>
>Unfortunately I don't see the attachment?
>
>
>
>>There's a few approaches to the "monitoring VMs" question.
>
>A. Install agents on the VMs and get the agents to
Brilliant, thanks Chiradeep,
Unfortunately I don't see the attachment?
>There's a few approaches to the "monitoring VMs" question.
A. Install agents on the VMs and get the agents to phone back to your
monitoring server.
B. Add a dedicated monitoring VLAN per tenant and get the tenant VMs t
I was just about to see if anybody wanted to work on a nagios plugin, but
googled first - https://github.com/jasonhancock/nagios-cloudstack looks
interesting, for any other Opsview/Nagios peeps out there.
MIght be good to have a wiki page pointing to plugins for the various
monitoring solutions
Is monitoring VM's through hypervisor APIs an option as well?
-David
On 4/26/12 10:19 AM, "Chiradeep Vittal"
wrote:
>There's a few approaches to the "monitoring VMs" question.
>A. Install agents on the VMs and get the agents to phone back to your
>monitoring server.
>B. Add a dedicated monitor
There's a few approaches to the "monitoring VMs" question.
A. Install agents on the VMs and get the agents to phone back to your
monitoring server.
B. Add a dedicated monitoring VLAN per tenant and get the tenant VMs to be
dual homed on the original isolated VLAN and the monitoring VLAN
C. Like B,
It is known that VMware complains about MAC address assigned from CloudStack.
as long As you don't mix VMs from CloudStack and VMs from vCenter itself into a
common network, other than this annoying message from vCenter, this will not
affect CloudStack from functioning.
Kelven
-Original Me
Anyone know if there is a known issue with CS 3.0.1 using ESXi 4.1 that causes
VMware to complain about the SSVM and Console VM NIC MACs to be assigned
outside of the allowed range?
Error seen is
"Change virtual NIC MAC Address
The MAC Address entered is not in the valid range. Valid values ar
Just one note, the mascot will not stick forever :), means that we can
change it later if the community wants, this happens oftenly when podlings
are preparing for graduation
On Wed, Apr 25, 2012 at 7:03 PM, Peder Ulander wrote:
> Matt, Mohammad and David - great suggestions. 30 days seems more
Agree, that 3 symptoms describe 3 level of 7-layer OSI model.
no routing to host - Layer 3 (IP layer)
connection refused - Layer 4 (transport - TCP/UDP)
connection reset - Layer 5 (session layer) or higher
> 1. Sounds like a routing issue. Packet flow cant reach the destination.
> 2. So
10 matches
Mail list logo
