An client I’m doing some alarm reduction work for has started putting more and more network connections and devices into “In Maintenance” in SMARTS.
This would be of no concern if they were running off a single set of SAMs and APMs. But being the owners of a large global enterprise network and in the banking sector one isn’t enough and rightly so. They have two independent systems both doing live polling and alerting, backing each other up.
We’ve had a tool in place for a while, ensuring that any log entries, ownership and acknowledgement are replicated from one system to the other.
Today I finished the first cut of a Perl script that replicates In Maintenance setting between the systems via the SMARTS API. Just a bit of change control and everything will be in place.
If for whatever reason the Network Operations Centre have to switch from one system to the other all of the maintenance settings will then be in place allowing them to continue as if nothing had happened.