Hello, just wondering about the following situation and if this is or isn't in SOI's ability to work with Spectrum?
In Spectrum we can have the following layout situation:
Router1 > Device1
Spectrum has the ability to determine that if Device1 goes down, it will produce an alert on Device1. SOI Sees this alert and displays on the SOI Console.
Spectrum then tries to ping all neighbor devices relative to Device1. If it find that the neighbors are up then it leaves the alert until it is resolved.
If it finds the the neighbors of Device1 are also down, then it tests the upstream device Router1. If Router1 is down then what Spectrum does is then create 1 alert on Router1 and then "Supresses" all the devices downstream from Router1. All Device1, and Deive2 alarms are then removed from the Spectrum console. This is the part where SOI is lacking. SOI keeps these alarms on it's console for all the device# alerts that got generated. It doesn't clear or hide them form the console.
This is really bad since if we have auto-ticketing turned on for a service/site, and all the downstream devices throw an alert in SOI, all alerts get tickets cut.
We could be talking 100+ tickets when really there should be 1 ticket cut b/c the Router connecting all those devices is down. Spectrum behaves correctly but on the SOI side those alerts should be suppressed or removed when Spectrum does this. We would have a delay of about 2 minutes set in our AEP policy that would wait before the ticket is cut. That would give enough time for Spectrum to make the determination if the issue lies upstream or if the actual device is down. If the Device is down alerts are not removed from the SOI console then tickets get cut. This is an issue.