Avaya 9608 Desk Phones - Alarms - WARNING IN - Constantly

[Bondojordo]

Howdy,

Running CM 5.2 with 9608 desk phones.
For the last couple of weeks i've been getting a lot of WARNING IN alarms from random phones throughout our building.
They go away pretty quickly, but then later on i'm contacted by the user who states they are having voice issues or the display on the phone is messed up, phone's not ringing, etc.

A quick phone reboot solves the issue, but,
Would anyone have any thoughts and ideas on what would be causing these mass WARNING IN alarms?

I would say this is the first time this has ever happened where its so consistent throughout the day, after hours, everyday.

Any help would be greatly appreciated,
Thanks!

 

[kyle555]

network problem... got 4600's working fine in the same subnets?
WARNING IN means the phone went in service, as in it was recently out of service, as in, packets ain't getting from the phone to the core and vice versa.

gotta firewall between the phones and the core?

 

[Bondojordo]

yeah, i figured its network related. It usually is.
Thank you for that.

Im sure we do.
Notified my network people.
Waiting on a response...

 

[Bondojordo]

@kyle555

Found this under SYSTEM LOGS in system platform.
Anything to worry about:



Apr 23 06:29:14 Warning [6188]: WARN: common_apply_stickiness: Forcing dom0-drbd-Domain00 away from voipla1 after 1000000 failures (max=1)
Apr 23 06:29:13 Warning [6188]: WARN: unpack_rsc_op: Processing failed op dom0-drbd-Domain00_start_0 on voipla1: unknown error (1)
Apr 23 06:14:14 Warning [6188]: WARN: common_apply_stickiness: Forcing dom0-drbd-Domain00 away from voipla1 after 1000000 failures (max=1)
Apr 23 06:14:13 Warning [6188]: WARN: unpack_rsc_op: Processing failed op dom0-drbd-Domain00_start_0 on voipla1: unknown error (1)
Apr 23 05:59:14 Warning [6188]: WARN: common_apply_stickiness: Forcing dom0-drbd-Domain00 away from voipla1 after 1000000 failures (max=1)

 

[kyle555]

drbd = distributed replication of block devices.

It does exactly what its name implies. In System Platform, that purpose was do distribute the replication of disks - or, block devices! - across 2 servers for System Platform HA

So, if you had System Platform HA running a Midsize Enterprise or any other System Platform template, that was the thing to ensure what was on disk for each VM on server 1 was sync'd on server 2.

System Platform HA required shutting down the VMs on one box before firing them up on the other, so it's likely that has nothing to do with your problem otherwise your CM would have been down for a good 10 minutes each time VSP HA flipped around. CM runs in RAM for the most part anyway. If something like that drbd stuff was causing your 9608s problems, you'd probably be seeing sparks fly elsewhere too.