[cisco-voip] CallManager 7.1(3) on MCS7835I3-K9-CMC2

[Ryan Ratliff]

I'd have expected that Critical alert to generate a Syslog Severity alert in RTMT.

-Ryan

On Jun 2, 2010, at 9:14 AM, Jason Aarons (US) wrote:

> Cool. Syslog from RTMT had the details. Surprised this was in the Alert Central section of RTMT! -jason
>  
> Can IBM Director poll/manage MCS-7835I3 ? If customer wants to monitor hardware/raid/temps, etc? I’m asking are the IBM snmp/mibs on the RedHat platform appliance in 7.1(3).
>  
> Jun 1 19:18:44, USAvp4221IRVG01, Critical,  Director Agent, : IBMPSG_TemperatureEvent USAvp4221IRVG01 Temperature  Sensor 2 exceeded the manufacturer defined threshold of 45 Celsius. The current value is 41 Celsius. Sev: 6., 33285
> Jun 1 19:18:49, USAvp4221IRVG01, Notice,  messagebus, : messagebus -TERM succeeded, 33286
> Jun 1 19:18:49, USAvp4221IRVG01, Notice,  cimlistenerd, : Shutting down Pegasus CIM Listener , 33287
> Jun 1 19:18:49, USAvp4221IRVG01, Notice,  cimlistenerd, :  succeeded, 33288
> Jun 1 19:18:49, USAvp4221IRVG01, Notice,  cimlistenerd, : [60G, 33289
> Jun 1 19:18:49, USAvp4221IRVG01, Notice,  rc, : Stopping cimlistenerd:  succeeded, 33290
> Jun 1 19:18:50, USAvp4221IRVG01, Warning,  cimserver[6243], : /opt/ibm/icc/cimom/lib, 33291
> Jun 1 19:18:54, USAvp4221IRVG01, Info,  cimserver[2289], : PGS10031: CIM server CIM Server stopped., 33292
> Jun 1 19:18:56, USAvp4221IRVG01, Notice,  cimserverd, :  succeeded, 33293
> Jun 1 19:18:56, USAvp4221IRVG01, Notice,  icesnmp, : stopdirsnmpd startup succeeded, 33294
> Jun 1 19:19:21, USAvp4221IRVG01, Notice,  twgend, : Requesting service to end., 33295
> Jun 1 19:19:21, USAvp4221IRVG01, Notice,  twgend, : Waiting for service to end., 33296
> Jun 1 19:20:01, USAvp4221IRVG01, Notice,  twgend, : getnameinfo failed, 33297
> Jun 1 19:20:01, USAvp4221IRVG01, Notice,  twgend, : Service ended., 33298
> Jun 1 19:20:01, USAvp4221IRVG01, Notice,  twgagent, : twgend startup succeeded, 33299
> Jun 1 19:20:02, USAvp4221IRVG01, Notice,  servm, : servM shutdown failed, 33300
> Jun 1 19:20:02, USAvp4221IRVG01, Notice,  sshd, : sshd shutdown succeeded, 33301
> Jun 1 19:20:02, USAvp4221IRVG01, Info,  snmpd[3589], : Received TERM or STOP signal...  shutting down... , 33302
>  
> From: Jason Aarons (US) 
> Sent: Wednesday, June 02, 2010 7:26 AM
> To: cisco-voip at puck.nether.net
> Subject: CallManager 7.1(3) on MCS7835I3-K9-CMC2
>  
> Customer Data Center lost power, then lost AC so it go hot in there!
>  
> I suspect that CallManager 7.1(3) on MCS7835I3-K9-CMC2 got hot enough to where the BIOS protected the machine by shutting it down.  Since it wasn’t a power outage I don’t think the BIOS would re-start the hardware but rather keep it  shut down and wait for a manual restart. If your engine is overheating you wouldn’t want it to keep restarting, you want to protect it right?
>  
> Customer tested that during a power down/up scenario the MCS7835I3-K9-CMC2 would reboot and stay running, but I don’t want to “test” a high heat situation.  Is there any way to confirm what the expected behavior is when a IBM server (is the MCS-7835I3 actually a IBM x3650-M2) overheats? What is the temp threshold the hardware shuts down, etc.
> 
> 
> Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100602/2c814a8e/attachment.html>