Strange behavior with scheduled SANM policies

Products

• CA Spectrum

Issue/Introduction

Customer has for his alarm notifier the following two SANM policies: ..OfficeHours and ...OutofOfficeHours

The OfficeHours is enabled from Mon thru Fri at 8 AM
The OutofOfficeHours is enabled from Mon thru Fri at 6 PM 
So on Friday at 6:00 PM SANM should start to use the OutofOfficeHours policy, till Monday at 8:00 AM  when the policy  OfficeHours should be enabled again. 

Now it looks like that after the Spectrum upgrade to 21.2.4 only on Sunday, Spectrum switches to use the OfficeHours policy.

Environment

Release : 21.2

Component : Spectrum Applications

Resolution

Customer created a new SANM Policy to cover the weekend (Saturday and Sunday) which worked fine.

Additional Information

To check which SANM policy is currently associated to the alarm notifier, you can run a CLI show associations command. Here is a sample of script 

------------

#!/bin/bash
timestamp=`date "+%H%M%d/%m/%Y"`
 
# Connect to the VNM shell
./connect
CLIMNAMEWIDTH=64   
export CLIMNAMEWIDTH

connection
echo "Press CTRL+C to exit"
echo " " > ./outfile

while :

       do

echo "Current running SANM policy run `date` " >> ./outfile

                ./show associations mh=0x5004a55 | grep -i Is_Associated_With >> ./outfile

              sleep 1800
        done
  
# Disconnect from the VNM shell
./disconnect

------------------

where mh= is the model_handle of your  alarmnotifier application. The script every 30 mins (sleep 1800) will write in the output file the current running SANM policy.