Persistent alarms re-generated at SpectroSEVER restart.

book

Article ID: 211869

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

On a non Fault Tolerance SpectroSERVER environment, all existing alarms (even if they are persistent) are re-generated at SpectroSERVER restart.

To verify the issue, add the following debug options in $SPECROOT/SS/.vnmrc file:

ftasv_debug=TRUE
debug=TRUE
persistent_alarms_active=TRUE

Restart the SpectroSERVER process and check for the following in the $SPECROOT/SS/VNM.OUT file:

Mar 11 10:47:39 : Please wait. SpectroSERVER
     is loading landscape 0x700000 at precedence 10...

Mar 11 10:47:39 ERROR TRACE at CsPstAlServ.cc(614): IH REF Attr has no value... cannot restore alarm
Mar 11 10:47:39 ERROR TRACE at CsPstAlServ.cc(614): IH REF Attr has no value... cannot restore alarm
Mar 11 10:47:39 ERROR TRACE at CsPstAlServ.cc(614): IH REF Attr has no value... cannot restore alarm
Mar 11 10:47:39 ERROR TRACE at CsPstAlServ.cc(614): IH REF Attr has no value... cannot restore alarm

Environment

Release : 20.2.7 (10.4.3) 20.2.10 (10.4.3.1)

Component : Spectrum Core / SpectroSERVER

Resolution

This issue is addressed in the patch 10.04.03.D130 for 20.2.7 (10.4.3) and the 10.04.03.01.D172 patch for 20.2.10 (10.4.3.1)

After installing the patch and before starting the SpectroSERVER, add the following to the .vnmrc file:

restore_persistent_alarms=TRUE