SDC Fault Isolation

Secure Domain Connector (SDC) is used for managing devices. When SDC gets down, all the devices managed by SDC become unreachable. Previously, such devices would start generating individual alarms. Now, this behavior has changed in the 10.4.1 release. In this release, when SDC goes down, all devices modeled under SDC are suppressed and show the root cause as
SDC down
. Therefore, all related individual alarms are suppressed and users see only one alarm with the root cause as
SDC down
. It also helps users to efficiently manage devices and alarms.
The following information describes the behavior when SDC goes down.
  1. When SDC goes down, the SDC-modeled devices are suppressed. The following screenshot shows the required information:
    Suppress devices when SDC is down
    In the SDC LOST alarm impact list, you can find a list of SDC-modeled devices that show the root cause as SDC down. The following screenshot shows the impact list:
    Impact list when SDC is down
    The following screenshot shows the root cause:
    Root cause when SDC is down
  2. If chassis down alarms are available on an SDC-managed device and SDC goes down, then those alarms on that device are also suppressed. However, when SDC comes up, SpectroSERVER again generates those alarms if the device is down.
  • If SDC-managed devices are in the maintenance mode and SDC goes down, then such devices are suppressed and are not shown in the impact list. And, if the device is removed from the maintenance mode, then it is shown in the impact list.
  • If a suppressed device is put in the maintenance mode and SDC goes down, then this device is not shown in the impact list.
  • Trap based alarms are not suppressed.
  • Alarms generated on System Resources (RFC 2790) on monitored processes and file systems are not suppressed.
  • It is not recommended to put virtual entities like Fanout and WA segment in maintenance mode.