Tech Tip: How are changes propagated to Fault Tolerant SpectroSERVERs when Event changes are made on the Primary?
CA Spectrum Tech Tip by Bill Wolforth, Senior Support Engineer for September 13, 2016
How are changes propagated to Fault Tolerant SpectroSERVERs when Event changes are made on the Primary?
Description: After event changes have been made on a primary SpectroSERVER what causes those changes to be rolled out to the secondary SpectroSERVER?
The EMSUpdateTime attribute is updated when an Event change occurs that affects the AlertMap or EventDisp files. 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.
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.
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:
show attributes attr=0x12be0 mh=0x100000
0x12be0 EMSUpdateTime 1444411317
This is the value of the attribute after saving event changes in the Event Configuration UI
0x12be0 EMSUpdateTime 1456839348
UNIX time converts to: 3/1/2016, 8:35:48 AM GMT-5:00
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 file.
> ls -al
drwxr-xr-x 2 Administrator None 0 Mar 1 08:36 .
drwxr-xr-x 5 Administrator None 0 Feb 25 10:38 ..
-rw-r--r-- 1 Administrator None 17630 Mar 1 08:36 EventDisp
For more information about working with Events in Spectrum please see:
Will initiating the update action from the VNM or CLI propagate the changes out by any chance?