Hi Vivek,
Thank you for your reply. We recovered the VR no problem, and fortunately only
test VMs where running of this VR.
I’m more concerned about the failure to notify the alarm.
-Antoine
Antoine Boucher
antoi...@haltondc.com
[o] +1-226-505-9734
www.haltondc.com
“Data security made simple and affordable”
Confidentiality Warning: This message and any attachments are intended only for
the use of the intended recipient(s), are confidential, and may be privileged.
If you are not the intended recipient, you are hereby notified that any review,
retransmission, conversion to hard copy, copying, circulation or other use of
this message and any attachments is strictly prohibited. If you are not the
intended recipient, please notify the sender immediately by return e-mail, and
delete this message and any attachments from your system.
> On May 2, 2022, at 4:37 AM, Vivek Kumar
> wrote:
>
> Try restart the VPC with cleanup options if you are using VPC, or simply
> destroy the VR and re-create the VR.
>
>
> Regards,
> Vivek Kumar
>
>
>> On 01-May-2022, at 9:12 PM, Antoine Boucher wrote:
>>
>> Hello,
>>
>> We use ACS 4.16.1 with multiple clusters and zones using Xen and KVM hosts.
>>
>> We could not deploy a new VM on a specific cluster after one of our KVM
>> hosts went down. Our investigation discovered that the VR of the network we
>> were trying to use was on the failed host. We confirmed that the VR is dead;
>> however, We see no alarm indication as the VR is showing as running and up.
>>
>> We have not uncovered why the system is not reporting the issue and
>> re-spawning the VR on another host.
>>
>> Has anyone seen this issue? What could be the most likely reasons?
>> Everything else seems to be working fine.
>>
>> Regards,
>> Antoine
>>
>>
>
>
> --
> This message is intended only for the use of the individual or entity to
> which it is addressed and may contain confidential and/or privileged
> information. If you are not the intended recipient, please delete the
> original message and any copy of it from your computer system. You are
> hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited unless proper authorization has been
> obtained for such action. If you have received this communication in error,
> please notify the sender immediately. Although IndiQus attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that both are
> virus-free and accepts no liability for any damage sustained as a result of
> viruses.
