[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anshul Gangwar resolved CLOUDSTACK-1853.
----------------------------------------

    Resolution: Not A Problem

Alert is not generated for router VM as we don't send alert for HA VMs. SSVM 
and CPVM's HA is handled differently. So this is by design.

If we need to made design change, what should be the expected behaviour?
send alert for all HA VMs?
make exception for router VMs only?
 stop sending alert for SSVM and CPVM also?

sending alert for HA VMs can be false alarm as they are started automatically.

> Alerts-SNMP:No alerts generated for router vm when VM stopped unexpectedly 
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1853
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1853
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: sadhu suresh
>            Assignee: Anshul Gangwar
>             Fix For: Future
>
>         Attachments: management-server.rar
>
>
> No alerts generated for router vm when VM stopped unexpectedly 
> Steps:
> 1.setup advance zone with xen
> 2.deploy few guest VM,configure the SNMP
> 3.from xencenter ,perform force shutdown
> 4 check for Alerts and SNMP alerts
> Actual results:
> In case router vms no alerts generated  but where as for ssvm and cpvm CS 
> generated alerts  properly
> router vm: shutdown event --No Alerts generated
> ssvm,cpvm-Shutdown event -Alerts generated
> CPVM
> ---------
> 2013-03-29 11:39:08 rhel631.cs1cloud.internal [UDP: 
> [10.147.59.110]:46391->[10.147.59.110]]:
> SNMPv2-MIB::snmpTrapOID.0 = OID: CS-ROOT-MIB::consoleProxyVmState       
> CS-ROOT-MIB::dataCenterId = Gauge32: 1  CS-ROOT-MIB::podId = Gauge32: 1 
> CS-ROOT-MIB::message = STRING: VM (name: v-2-VM, id: 2) stopped unexpectedly 
> on host id:1, availability zone id:1, pod id:1  CS-ROOT-MIB::generationTime = 
> STRING: Fri Mar 29 11:39:08 EDT 2013
> VM (name: v-2-VM, id: 2) stopped unexpectedly on host id:1, availability zone 
> id:1, pod id:1  29 Mar 2013 15:39:08     
> VM (name: s-1-VM, id: 1) stopped unexpectedly on host id:1, availability zone 
> id:1, pod id:1



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to