SBC SCOM Health Monitors
SCOM classes define Health as a tri-state attribute: Error, Warning, and Healthy. A device is in Error state when it's not working correctly and requires attention, it's in Warning state when it appears to be working but a condition is detected that should be attended to, and it's Healthy otherwise.
SBC SCOM Monitors
A SCOM Monitor is a periodic poll that runs in order to determine health state. The SBC SCOM Management Pack will define monitors that poll the SBC for the following information:
- Highest Alarm State (not currently returned through SNMP)
- Operational Status for ports, DSPs, and power supplies.
- Administrative State for Ports
The results of this poll will be used to set the Health state of SBC classes as follows:
Health States Associated with SBC SCOM Object Classes
SBC SCOM Class
Highest Alarm Severity is either Critical or Major. Where SLAs are present, these severities require immediate attention.
Highest Alarm Severity is Minor
Highest Alarm Severity is Warning or None
SBCSeries is an abstract class, these criteria apply to all inherited classes
The card has configured ports and is either not present or is operationally down.
The card either has no configured ports, or is operationally up.
SBCLineCard is an abstract class representing pluggable cards (e.g.: SBC2000 DS1), these criteria apply to all inherited classes. When administrative state support is provided for cards the error criteria will include the card being administratively up.
This state always applies
SBCModule is an abstract class representing non-pluggable feature modules (e.g.: SBC1000 DS1). No service status information is supported for these modules.
The port is administratively up and operationally down
The port is either administratively down, or operationally up.
The DSP card is out of service
The DSP card is in service
DSP Service Status is added via SNMP in the Flute release.
The power supply is out of service
NOTE: Warning can be indicated based upon temp or voltage-out being out-of-spec.
The power supply is in service
Only applicable to SBC2000 with dual power supplies, otherwise the node will simply become SNMP-unreachable.
This is a recovery port , it is not mandatory to keep the cable plugged-in always in this port. Un-plugging the cable will make the port status down . This is a typical state in the customer location. So instead of showing the port down and alarming the operator , keep the port status healthy alway
Object Model Overview
Within SCOM object classes represent entities whose health state is monitored by SCOM and presented to the user. SBC SCOM object classes are defined for persistent objects in the system.
Supported Object Relationships
SCOM supports the following relationships:
- Inheritance: An inheritance relationship has the common object-oriented meaning.
- Hosting: A hosting relationship is one where an instance of the hosted class cannot exist without it's host, and where removing the host from the system causes the hosted objects to be removed.
- Containment: A containment relationship allows instances of the two classes to exist independently, but provides for health state roll-up.
- Reference: A reference relationship has the common object-oriented meaning. The only relationships that exist between SBC SCOM classes are Inheritance and Hosting.
SBC SCOM Object Classes
- SBCSeries: This will be an abstract object class for all "SBC" network devices.
- SBC2000: This inherits from SBCSeries and represents a SBC2000 node. This is the "chassis" object for the SBC2000.
- SBC1000: This inherits from SBCSeries and represents a SBC1000 node. This is the "chassis" object for the SBC1000.
- SBCShelf: This object class is hosted by SBCSeries. There will be one instance for each SBC2000 and 1000, the 5000 will have multiple instances.
- SBCCard: This will be an abstract object class for cards and modules. It will be Hosted by SBCShelf.
- SBCLineCard: This will be an abstract object class for all user-pluggable SBC Cards. It will inherit from SBCCard.
- SBCModule: This will be an abstract object class for all non-pluggable SBC Cards. It will inherit from SBCCard.
- SBC1000MainBoard: This class represents a SBC1000 'main board', and inherits from SBCCard. It provides a container for all ports on the SBC1000.
- SBC2000MainBoard: This class represents a SBC2000 'main board', and inherits from SBCCard. It provides a container for non-SPI SBC2000 Ethernet Ports.
- SBCTelcoDS1Card: This inherits from SBCLineCard and represents a Telco DS1 line card.
- SBCTelcoDS1Module: This inherits from SBCModule and represents a Telco DS1 Module.
- SBCFXSAnalogModule: This inherits from SBCModule and represents a FXS Analog Module.
- SBCFXOAnalogModule: This inherits from SBCModule and represents a FXO Analog Module.
- SBCBRIModule: This inherits from SBCModule and represents a BRI Module.
- SBCPort: This is an abstract class and represents a SBC Series Port.
- SBCTelcoDS1Port: This class inherits from SBCPort and represents a Telco DS1 Port. It will be Hosted by SBCTelcoDS1Card and SBCTelcoDS1Module.
- SBCEthernetPort: This class inherits from SBCPort and represents an Ethernet port. It will be Hosted by SBC1000MainBoard and SBC2000MainBoard.
- SBCFXSAnalogPort: This class inherits from SBCPort and represents an FXS analog port. It will be hosted by SBCFXSAnalogModule.
- SBCFXOAnalogPort: This class inherits from SBCPort and represents an FXO Analog Port. It will be hosted by SBCFXOAnalogModule.
- SBCBRIPort: This class inherits from SBCPort and represents a BRI port. It will be hosted by SBCBRIModule.
- SBCPowerSupply: This class represents a pluggable SBC Power Supply. It will be Hosted by SBCShelf. The SBC1000 does not have a SBCPowerSupply object because it's not pluggable.
- SBCDSPCard: This class represents a DSP. It will be Hosted by SBC1000MainBoard and SBC2000MainBoard.
- SBCAdminPort: This class represents the SBC2000 Admin port which is hosted by SBC2000MainBoard.
SCOM Object Class Diagram