When a primary SpectroServer is stopped and the secondary takes over, there are no more alarms from CA PM to spectrum. Even when the primary SpectroServer is back up and running, there are still no alarms with the following errors appearing repeatedly in the tomcat log:
This can happen after upgrade to PM 3.6 and spectrum 10.3.
This can also be seen in systems where a network problem causes the OC and SS systems to lose connection.
In a standalone situation, when the SpectroServer (SS) goes down, neither sync to CAPC nor event polling are able to run.
When the SS comes back up (without a tomcat restart), it should be marked as synchronized, and start event polling. During the next sync, it should sync anything changed since the SpectroServer went down. OneClick will ask for events back to when the SS went down.
When SpectroServer is configured with Fault Tolerance (FT), it should operate as above, however, this was not happening. No synchronization or sending events should occur while the system is in a failover state and running on the (secondary) SpectroServer.
One Fault Tolerant pair (1 primary and 1 secondary SpectroServer)
Issue was replicated and fixed, verified in both standalone and DSS setups. After applying this fix, event polling will start automatically when the SS returns to active state without a OneClick server restart.
This fix is available in the Spectrum 10.3.2 release:
For Spectrum 10.3.0, a PTF was created - "Spectrum_10.03.00.PTF_10.3.021":