An SDConnector is modeled in Spectrum as a SDConnectorProcess. When the SDConnector experiences an outage, all devices connected to the SDConnector alarm.
Release: Spectrum version up to 10.4.0
Component:
There is no fault isolation intelligence built into the SDConnector modeltype in versions prior to 10.4.1. In version 10.4.1, SDC enhancement is made to only show DEVICE STOPPED RESPONDING alarm on SDC, and downstream devices are suppressed:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/spectrum/10-4-1/managing-network/secure-domain-manager-sdm/installing-and-configuring-secure-domain-manager-processes/SDC-Fault-Isolation.html
If an SDC goes down, all the devices managed by that SDC should turn grey [suppressed].
SDConnector Modeling and SPECTRUM Fault Isolation:
When you model SDConnectors you can choose one of the following model types:
- SDConnectorProcess
- Host_Device
- Pingable
Spectrum Support recommends that you model the SDConnector host as a Host_Device or Pingable model type to allow SPECTRUM's fault isolation to work correctly in the event that a remote SDConnector process goes down or the connection to it is lost. This enables SPECTRUM to fully isolate the cause of an outage to the SDConnector host model, virtually eliminating unresolved fault alarms.
Although the SDConnector host is most likely connected to a switch on the "edge" of a region's network, logically it is the bridge between the public domain and secure domain regions and it must be modeled accordingly. Therefore you should place the SDConnector host model between the two models for the devices that are routing traffic between the public domain and secure
domain regions.