Heartbeat woes

[TBLuk]

We use the heartbeat (ALHBI) function as a keep alive for alarm checks across our network.

We have it setup to output a heartbeat every 12 hours using.

Every now and again, and this happens on all BC9 sites I've checked, the heartbeat stops working.

You do an ALDIP and predictably the heartbeat is displayed.
You try and remove it and it says NOT ACCEPTED - HEART BEAT NOT INITIATED, even though it is.
You try and program a new heartbeat and it tells you that it's already initiated.

Normally to overcome this, you erase all ALAPI information, then program up a heartbeat on a seperate IODEV, then remove it. This has the effect of removing the 'stuck' heartbeat as well.

However, I've now come upon a scenario where someone has setup two 'stuck' heartbeats. You MD110 only allows two heartbeats so I can't initiate a third to resolve the problem.

Is there any way I can somehow force this out? I've already tried removing and reprogramming the two IODEVs affected, and I've given ALH1 and 2 a kick to no avail.

Help appreciated!

 

[LME]

Hi
Try restarting ALM &ALR

 

[TBLuk]

Thanks for the suggestion LME, but I did not expect that to work, and unfortunately it didn't :-(

Does anyone else have any suggestions?

 

[LME]

Hi
Try rfpui:lim=1,unit=alh1&alh2&alm&alr;

 

[TBLuk]

I'd already tried ALH1 and ALH2, LME.

This seems more a corruption issue that'll need poked out.

 

[TBLuk]

Can anyone else assist in this matter? Please!

 

[spamfree]

I have found that the alapi command does not always output alarms (some CLASS 4) in BC9. All alarm classes are set for output. Yet when you print allip the alarm is there. alhbi & alapi are not commands that many people use so it doesn't surprise me that these faults have gone unnoticed for so long.