search cancel

How are changes propagated to the Fault-Tolerant SpectroSERVERs when Event changes are made on the Primary?


Article ID: 39383


Updated On:


CA Spectrum DX NetOps


After making changes to the EventDisp and/or AlertMap files on a Primary SpectroSERVER that are defined in the <$SPECROOT>/custom/Events directory, how are the changes propagated to Fault-Tolerant servers?




The EMSUpdateTime attribute is updated when an event change occurs that affects the AlertMap or EventDisp files.

The Secondary SpectroSERVER monitors the Primary SpectroSERVER for status changes. During this time the EMSUpdateTime attribute is evaluated. If the timestamp has a newer value than the timestamp when the AlertMap and/or EventDisp file was last updated, the appropriate file will be updated on the Secondary SpectroSERVER.

NOTE: This update can only be made via the Event Configuration Editor. Manual changes to the AlertMap or EventDisp or changes made via MibTools will not update the EMSUpdateTime attribute.

For example:

On the Primary SpectroSERVER
The EMSUpdateTime attribute is on the VNM model.

This is the value of EMSUpdateTime before changes are made to the EventDisp file:

0x12be0     EMSUpdateTime     1444411317

This is the value of the attribute after saving event changes in the Event Configuration UI

0x12be0     EMSUpdateTime     1456839348


On the Secondary SpectroSERVER
During the next status update, the Secondary will query the EMSUpdateTime attribute on the VNM of the Primary SpectroSERVER and notice the timestamp has been updated. This will cause the Secondary SpectroSERVER to request the updated EventDisp and/or AlertMap file.

Additional Information

Please reference the "Event Configuration" section of the documentation for more information.