[cisco-voip] Tac poop pooped Unity Connection Hardware failure
Chris Clouse
Chris.Clouse at cdw.com
Tue Jul 17 13:30:47 EDT 2012
I also have been receiving these only it has been a bit more frequent (weekly or so). I'd be interested in what the solution is.
At Tue Jul 17 10:35:02 UTC 2012 on node X.X.X.X, the following HardwareFailure events generated:
hwStringMatch : Jul 17 10:34:41 bebrpcmt01 daemon 4 Director Agent: LSIESG_AlertIndication 500605B00249A0D0 BBU disabled; changing WB virtual disks to WT Sev: 3.
AppID : Cisco Syslog Agent
ClusterID :
NodeID : bebrpcmt01
TimeStamp : Tue Jul 17 10:34:41 UTC 2012
~Chris
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Scott Voll
Sent: Tuesday, July 17, 2012 10:30 AM
To: Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Tac poop pooped Unity Connection Hardware failure
nothing on either side of it for at least 2 hours. and those are just the periodic task checks
Scott
On Tue, Jul 17, 2012 at 7:45 AM, Ryan Ratliff <rratliff at cisco.com<mailto:rratliff at cisco.com>> wrote:
The 4:42AM alarm is a monthly self-test that includes a full battery discharge, thus the alarm. I don't recall seeing a battery failure that recovered itself, typically once they go they are dead. Are there any other messages around this alarm in the syslog that give a clue as to what is going on?
-Ryan
On Jul 17, 2012, at 10:28 AM, Scott Voll wrote:
OK, I understand that the below message is typically a bug and shows up at 4:42am the first of each month. Have seen it for years now.
At Mon Jul 16 17:54:44 PDT 2012 on node UnityConnection, the following HardwareFailure events generated:
hwStringMatch : Jul 16 17:54:30 UnityConnection daemon 4 Director Agent: LSIESG_AlertIndication 500605B001AAECE0 BBU disabled; changing WB virtual disks to WT Sev: 3.
AppID : Cisco Syslog Agent
ClusterID :
NodeID : UnityConnection
TimeStamp : Mon Jul 16 17:54:30 PDT 2012
But I'm not getting it multiple times a month at times other than 4:42am.
opened a TAC case and they just say it's the bug. I'm thinking that the Battery is going out. am I incorrect in my thinking?
TIA
Scott
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto: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/20120717/6af85d61/attachment.html>
More information about the cisco-voip
mailing list