Secondary backup server generate duplicate event/alarms with precedence 10

book

Article ID: 145292

calendar_today

Updated On:

Products

CA Spectrum CA eHealth

Issue/Introduction

We are testing having our Cisco controller send traps to both Primary and Secondary servers, for Fault Tolerance. We expect that if Primary is active, any traps sent to Secondary would not be processed. Instead, when sending traps to the Secondary server, we are seeing Precedence 10 events being generated. This also creates duplicate alarms. Why does this happen? 
 

Cause

In a Fault Tolerant server configuration, its possible there may be an issue with the Landscape Map causing traps sent to Secondary to be processed as Precedence 10 when the Primary is active. 

Environment

Release : 10.3

Component : Spectrum Core / SpectroSERVER

Resolution

Force the Secondary server to startup as "Secondary" which should force precedence 20 events. Precedence 20 events should only process if the Secondary server is active (Failover) . 

- Add the following line to the Secondary server .vnmrc config file: 

is_secondary=true

- save the file, and restart the server for this setting to take place

- perform this step for any/all Secondary servers in the Landscape

Additional Information

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/spectrum/10-4-1/administrating/distributed-spectroserver-administration/how-to-monitor-the-secondary-spectroserver-status.html