Author Topic: An alarm has been raised with major severity  (Read 2629 times)

Offline akuhn

  • Sr. Member
  • ****
  • Posts: 339
  • Karma: +1/-0
    • View Profile
An alarm has been raised with major severity
« on: June 11, 2012, 08:45:01 AM »
or critical or major.  I've been seeing more of these lately.  I can't seem to figure out the root cause.  They are typically at 12:03 or 12:11 in the morning.  I have a ticket in with Mitel.  Examples are:


Application   : ucserver
Event Type   : wdOutOfService
Value      : lnm
Severity   : major
Description   : Health check failed for module: DB_CHECK

or


Application   : ucserver
Event Type   : wdShutdown
Value      : lnm
Severity   : major
Description   : Module DB_CHECK pid 8917 is shutting down - if system shutdown not in progress, contact Mitel Technical support.

or


Application   : ucserver
Event Type   : genServerCongestionLevel
Value      : lnm
Severity   : critical
Description   : Current server congestion level 1, description CONG_YELLOW, DebugLevel: 1, BlockProvisioning: 0, BlockSIPRegistration: 0,PercentInboundDrops: 0, PercentOutboundDrops: 0, reason cpu

Mas 3.  UCA 4.1.22 all as a VM

Checked with my VMWare Admins and they so no events during that time.  Wouldn't an alarm about congestion at midnight seem odd?  No one is on the system at that time as far as I know.

Thanks for your feedback.

Adam in DC





Offline akuhn

  • Sr. Member
  • ****
  • Posts: 339
  • Karma: +1/-0
    • View Profile
Re: An alarm has been raised with major severity
« Reply #1 on: July 03, 2012, 08:17:09 AM »
Tech support is recommending upgrading from UCA 4 to 5, MAS 3 to 4 and upgrading virtual RAM of the vm from 4 to 6.

Not a whole lot of reasoning to it.  The RAM is a pre-determined amount from the VM template. 


 

Sitemap 1 2 3 4 5 6 7 8 9 10