Scenario#36 – RTMT Alert LSIESG_AlertIndication 500605B00177F4C0 BBU disabled

Posted: March 2, 2012 in Call Manager - CUCM, Real World Scenarios
Tags: , , ,

I was looking at some alerts for a customer when I found this in RTMT:

At Thu Mar 01 04:42:41 CET 2012 on node 10.254.33.20, the following HardwareFailure events generated:
hwStringMatch : Mar  1 04:42:10 AKDEUC00 daemon 4 Director Agent: LSIESG_AlertIndication 500605B0024A5360 BBU disabled; changing WB virtual disks to WT Sev: 3.
AppID : Cisco Syslog Agent
ClusterID :
NodeID : AKDEUC00
TimeStamp : Thu Mar 01 04:42:10 CET 2012

If you are concerned about this error then don’t be. This is a cosmetic error and documented in Bug id CSCti17353 .

 Bug Details

“IBM Servers battery learn cycle negatively impacts CCM performance”

Symptom:

CCM Tracing stops for a period of time (over 4 seconds observed) leading dropped or reordered calls.
IO wait utilization of the CPU increases unexpectedly.  System Event Logs (messages) contains the following logs shortly after the unexpected IO event.

Aug 2 15:48:08 lg-sub-1 daemon 5 Director Agent: LSIESG_AlertIndication 500605B00177F4C0 Battery relearn started Sev: 2.
Aug 2 15:48:13 lg-sub-1 daemon 4 Director Agent: LSIESG_AlertIndication 500605B00177F4C0 BBU disabled; changing WB virtual disks to WT Sev: 3.

Conditions:

On MCS-78X5-I3 platforms with LSI Raid controllers the system will run a Battery Backup Unit learning cycle every 60 days. The system can experience sudden IO
performance drop at the beginning of this cycle and this could impact Callmanager’s call processing performance. During this cycle the Raid Controller’s Caching policy is changed from WriteBack to Write Through.

Workaround:

None to avoid the BBU learning cycle.

After this ddts is applied…

The event reported above is an informational (sev 4) event: daemon 4

Director Agent:
LSIESG_AlertIndication 500605B0027DA6E0 BBU disabled; changing WB virtual disks

The event will occur once a month (at 4:42am) during the battery recharging cycle. That cycle is a scheduled event to recharge the raid battery. During that time, raid cache write-back is disabled as part of normal course to ensure proper IO. This is not an issue.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s