PEGASUS-SDH-MIB

All MIBs › PEGASUS-SDH-MIB

Organization: Schmid Telecom, Zurich

Last Updated: 2004-03-18

Category: Optical Networking

Description: Manages SDH multiplex section, regenerator section, and higher-order path performance on Schmid Telecom Pegasus microwave equipment.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is PEGASUS-SDH-MIB?

PEGASUS-SDH-MIB is a Schmid Telecom vendor MIB modeled after the PEM management model that manages SDH multiplex-section, regenerator-section, and higher-order path performance on the Pegasus SDSL/STM-1 microwave and access product manufactured by Schmid Telecom. It defines five tables: stm1CardTable and stm1CardClockTable (per-STM-1-card configuration and clock source/quality, using ClockSourceEnum, ClockSyncStateEnum, and ClockQualityEnum), ethernetIfTable (per-card Ethernet interface state and alarm status), vcTable (per Virtual Container VC-3/4/12), and tugConfigTable (per Tributary Unit Group TUG-3), with alarm visibility surfaced through stm1CardAlarmStatus, ethernetIfAlarmStatus, and vcAlarmStatus objects using the shared AvailabilityStatusElem convention. This makes the MIB useful for monitoring SDH transport-layer health and clock synchronization state on the Pegasus platform in addition to the Ethernet-over-SDH mapping it carries. It represents an extension to the standard DS1-MIB and SONET-MIB (reusing ifIndex from IF-MIB for its extension tables) and is deployed on Schmid Telecom Pegasus STM-1 microwave transport cards; field technicians can download the PEGASUS-SDH-MIB to interpret the SDH/VC alarm and clock objects on these cards.

IPNetwork Monitor allows you to monitor SNMP objects defined in PEGASUS-SDH-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Schmid Telecom Pegasus STM-1 microwave/SDSL transport cards

Monitoring Examples

An operator polls stm1CardTable's clock objects to confirm ClockSyncStateEnum reads syncOk and checks vcTable's vcAlarmStatus per Virtual Container; a VC-4 entry reporting an active alarm in vcAlarmStatus alongside a syncNotOk clock state on the carrying STM-1 card would point to a section-layer synchronization problem propagating into the mapped VC path.

What Can Be Monitored

STM-1 card configuration and clock source/quality
clock synchronization state
Ethernet-over-SDH interface status and alarms
Virtual Container (VC-3/4/12) alarm status
Tributary Unit Group (TUG-3) configuration

Imported Objects

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero
ifIndex	OBJECT-TYPE

From PEGASUS-MIB

AvailabilityStatusElem
CommStateEnum
OperStateEnum
pegasusMibModule	MODULE-IDENTITY

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using stm1CardAlarmStatus OID:

Select a Schmid Telecom Pegasus STM-1 microwave/SDSL transport card (SDH/clock status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type stm1CardAlarmStatus into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. This variable indicates the status of STM-1 card, regenerator section and multiplex section. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
pegasusSdhMibModule	1.3.6.1.4.1.6368.2.8			This MIB applies to the PEGASUS SDSL product manufactured by Schmid Telecom Zurich. The MIB is modelled after the PEM management model, so object hierarchy and individual variables agree with the PEM client. This MIB represents an extension to the DS1-MIB and the SONET-MIB. These three MIB files are used to manage the PEGASUS STM-1 card. The PEGASUS-SDH-MIB contains five tables: - stm1CardTable one entry for each STM-1 card configured. - stm1CardClockTable one entry for each STM-1 card configured. - ethernetIfTable one entry for each Ethernet interface of a configured STM-1 card. - vcTable one entry for each Virtual Container (VC-3/4/12). - tugConfigTable one entry for each Tributary Unit Group (TUG-3). Note - The tables that represent extensions to the DS1-/SINET-MIB use the ifIndex from IF-MIB (ifTable).
stm1CardTable	1.3.6.1.4.1.6368.2.8.1		not-accessible	A table containing stm1 card specific information.
stm1CardEntry	1.3.6.1.4.1.6368.2.8.1.1		not-accessible	Row and index definition for stm1 card table.
STM stm1CardSlotNumber	1.3.6.1.4.1.6368.2.8.1.1.1	STM1SlotNumber	not-accessible	Slot number for stm1 card.
STR stm1CardName	1.3.6.1.4.1.6368.2.8.1.1.2	DisplayString	read-only	Name of the PEGASUS device.
STR stm1CardHardwareVersion	1.3.6.1.4.1.6368.2.8.1.1.3	DisplayString	read-only	Hardware version of the STM-1 card. This is also called CHM-number (it always starts with the letters 'CHM'). The number '404' after 'CHM' identifies the card as a STM-1 card.
STR stm1CardFirmwareVersion	1.3.6.1.4.1.6368.2.8.1.1.4	DisplayString	read-only	Version number and build date of the firmware running on the line card. The format is 'major.minor YYYYMMDD hh:mm'.
STR stm1CardManufacturer	1.3.6.1.4.1.6368.2.8.1.1.5	DisplayString	read-only	Manufacturer of the STM-1 card.
STR stm1CardSerialNumber	1.3.6.1.4.1.6368.2.8.1.1.6	DisplayString	read-only	Serial number of the line card. Also called HM-number, as it always starts with 'HM'. Example: HMVSS014810294.
MUL stm1CardMultiplexingMode	1.3.6.1.4.1.6368.2.8.1.1.7	MultiplexingModeEnum	read-write	Selects the SDH multiplexing mode. Either it is STM1-AU3-VC3 or STM1-AU4-VC4.
OPE stm1CardJ0TraceMonitoring	1.3.6.1.4.1.6368.2.8.1.1.8	OperStateEnum	read-write	If trace monitoring is disable no alarm is propagated to PEM and also no RDI/AIS is inserted.
OPE stm1CardJ1TraceMonitoring	1.3.6.1.4.1.6368.2.8.1.1.9	OperStateEnum	read-write	If trace monitoring is disable no alarm is propagated to PEM and also no RDI/AIS is inserted.
OPE stm1CardJ2TraceMonitoring	1.3.6.1.4.1.6368.2.8.1.1.10	OperStateEnum	read-write	If trace monitoring is disable no alarm is propagated to PEM and also no RDI/AIS is inserted.
TRA stm1CardJ0PathTraceSize	1.3.6.1.4.1.6368.2.8.1.1.11	TraceSizeEnum	read-write	Size of the Regenerator Section Trace Message.
STR stm1CardJ0PathTraceSend	1.3.6.1.4.1.6368.2.8.1.1.12	DisplayString	read-write	Configurable Regenerator Section (RS) Trace Message.
STR stm1CardJ0PathTraceExpected	1.3.6.1.4.1.6368.2.8.1.1.13	DisplayString	read-write	Regenerator Section (RS) Trace Message that should be received.
STR stm1CardJ0PathTraceReceive	1.3.6.1.4.1.6368.2.8.1.1.14	DisplayString	read-only	Regenerator Section (RS) Trace Message that is be received.
LAS stm1CardLaserOperationMode	1.3.6.1.4.1.6368.2.8.1.1.15	LaserOperationModeEnum	read-write	Configuration of the 'Automatic Laser Shutdown' feature.
LAS stm1CardLaserState	1.3.6.1.4.1.6368.2.8.1.1.16	LaserStateEnum	read-only	Actual state of the laser.
OPE stm1CardOperState	1.3.6.1.4.1.6368.2.8.1.1.17	OperStateEnum	read-only	The operational state is a status property indicating whether or not a device is physically installed and working. enabled The device is partially or fully operable and available for use. disabled The device is totally inoperable and unavailable to provide service.
AVA stm1CardAvailabilityState	1.3.6.1.4.1.6368.2.8.1.1.18	AvailabilityStatusElem	read-only	The availability status gives more detailed information about failures within a device. An empty status set means that no error exists. Possible status are: in test The device is under test. failed The device has an internal fault that prevents it from operating. power off The device requires power to be applied and is not powered on. off line The device requires a routine operation to be performed to place it online and make it available for use. off duty The device has been made inactive by an internal control process in accordance with a predetermined time schedule. dependency The device can not operate because some other resource on which it depends is unavailable. degraded The device is partially defective but still operable. not installed The device is not present, or incomplete. log full The log is full.
COM stm1CardMgmtCommState	1.3.6.1.4.1.6368.2.8.1.1.19	CommStateEnum	read-only	The Management Comm State indicates the state of the management connection between the PEM Server and the STM-1 card. disconnected No connection has been established. init A connection has freshly been established on the underlying protocol, but no management information has been transmitted so far. identification The connected device is being identified. check hardware The connected hardware is compared to the one stored in the configuration. hardware adaptation If the configured and the existing device do not match, an adoption is made. The behaviour in this case can be configured with the 'HW Adaptation Policy' option. check program version The program version of the connected hardware is compared to the one stored in the configuration. check config version The configuration version of the connected hardware is compared to the one stored in the configuration. download config If a configuration version mismatch has been detected and the 'Config Priority' of 'PEGASUS system' is set to 'Device', the configuration is downloaded from the device to the PEM Server. upload config If a configuration version mismatch has been detected and the 'Config Priority' of 'PEGASUS system' is set to 'Server', the configuration is uploaded from the PEM Server to the device. status synch The values of the status properties are being synchronised. resetting The device is resetting. inactive The device is connected, but it is inactive, that is not operational. This may be due to a hardware mismatch. active The management connection between the device and the PEM Server is fully established and the device is active.
NUM stm1CardPRBSGeneratorSink	1.3.6.1.4.1.6368.2.8.1.1.20	SdhInterfaceEnum	read-write	Determines, whether the PRBS Generator should be used on the optical or on the E1 links.
NUM stm1CardPRBSAnalyzerSource	1.3.6.1.4.1.6368.2.8.1.1.21	SdhInterfaceEnum	read-write	Determines, whether the PRBS Analyzer should be used on the optical or on the E1 links.
PRB stm1CardPRBSPattern	1.3.6.1.4.1.6368.2.8.1.1.22	PRBSPatternEnum	read-write	Determines the PRBS Pattern to be used.
I32 stm1CardAlarmStatusEx	1.3.6.1.4.1.6368.2.8.1.1.23	Integer32	read-only	This variable indicates the status of STM-1 card, regenerator section and multiplex section. It's a bitmap represented as a sum. Therefore multiple alarms can be displayed simultaneously. The value noAlarm is only set if there isn't any alarm active. The various bit positions are: 1 No alarm present -- STM-1 card -- 2 Initialization failure 4 Firmware Version Mismatch 8 Maintenance -- regenerator section RS -- 16 Loss of Signal (LOS) 32 Loss of Frame (LOF) 64 Trace ID Mismatch (RS-TIM) -- multiplex section MS -- 128 Alarm Indication Signal (MS-AIS) 256 Remote Defect Indication (MS-RDI, former FERF)
stm1CardClockTable	1.3.6.1.4.1.6368.2.8.2		not-accessible	A table containing stm1 card specific clock information.
stm1CardClockEntry	1.3.6.1.4.1.6368.2.8.2.1		not-accessible	Row and index definition for stm1 card clock table.
CLO stm1CardActiveClockSource	1.3.6.1.4.1.6368.2.8.2.1.1	ClockSourceEnum	read-only	Displays which clock sourceis active and used as sync source.
CLO stm1CardClockSyncState	1.3.6.1.4.1.6368.2.8.2.1.2	ClockSyncStateEnum	read-only	Sync status is OK if RX or Reference clock is valid and used as active sync source.
CLO stm1CardTxLineClockQuality	1.3.6.1.4.1.6368.2.8.2.1.3	ClockQualityEnum	read-write	This is the clock quality of the outgoing SDH signal. The default sets the outgoing quality to the incoming quality. Sometime it may be useful to set a fix outgoing quality.
CLO stm1CardRxClockMode	1.3.6.1.4.1.6368.2.8.2.1.4	ClockModeEnum	read-write	If enabled the RX line clock can be used as sync source.
CLO stm1CardRxClockPriority	1.3.6.1.4.1.6368.2.8.2.1.5	ClockPriorityEnum	read-write	This value has always the opposite value of Reference Clock Priority.
CLO stm1CardRxClockQuality	1.3.6.1.4.1.6368.2.8.2.1.6	ClockQualityEnum	read-only	This is the clock quality of the incoming SDH signal.
CLO stm1CardRxClockState	1.3.6.1.4.1.6368.2.8.2.1.7	ClockStateEnum	read-only	Clock status is valid if a good clock can be found on input (clock checker).
CLO stm1CardReferenceClockMode	1.3.6.1.4.1.6368.2.8.2.1.8	ClockModeEnum	read-write	If enabled the Reference clock (V5 card input) can be used as sync source.
CLO stm1CardReferenceClockPriority	1.3.6.1.4.1.6368.2.8.2.1.9	ClockPriorityEnum	read-write	This value has always the opposite value of Rx Clock Priority.
CLO stm1CardReferenceClockQuality	1.3.6.1.4.1.6368.2.8.2.1.10	ClockQualityEnum	read-write	Defines the quality of the reference clock input. This value will be transmitted in SDH-TX if reference clock is used as active sync source.
CLO stm1CardReferenceClockState	1.3.6.1.4.1.6368.2.8.2.1.11	ClockStateEnum	read-only	Clock status is valid if a good clock can be found on input (clock checker).
ethernetIfTable	1.3.6.1.4.1.6368.2.8.3		not-accessible	This table contains additional information concerning the ethernet interfaces of a STM-1 card. It represents an extension of the if(X)Table (see IF-MIB).
ethernetIfEntry	1.3.6.1.4.1.6368.2.8.3.1		not-accessible	Row and index definition for the ethernetIfTable.
CON etherIfConcatenationOption	1.3.6.1.4.1.6368.2.8.3.1.1	ConcatenationTypeEnum	read-write	Configuration of the Link Capacity Adjustment Scheme.
ETH etherIfEncapsulation	1.3.6.1.4.1.6368.2.8.3.1.2	EthernetIfEncapsulationEnum	read-only	This attribute shows the used Ethernet encapsulation protocol.
ORD etherIfOrderLevel	1.3.6.1.4.1.6368.2.8.3.1.3	OrderLevelEnum	read-only	Only relevant, if SDH Multiplexing Mode (see STM-1 card propertied) is set to VC3.
I32 etherIfAlarmStatus	1.3.6.1.4.1.6368.2.8.3.1.4	Integer32	read-only	This variable indicates the status of an Ethernet Interface. It's a bitmap represented as a sum. Therefore multiple defects can be displayed simultaneously. The value noAlarm is only set if there isn't any alarm. The various bit positions are (LO = LowOrder, HO = HighOrder): 1 No alarm 2 LO LCAS group identifier mismatch (Rx) 4 HO LCAS group identifier mismatch (Rx) 8 LO VCG exceeds max. differential delay (Rx) 16 HO VCG exceeds max. differential delay (Rx) 32 LO VCG exceeds max. differential delay, calculated over all containers (Rx) 64 HO VCG exceeds max. differential delay, calculated over all containers (Rx) 128 Transmit FIFO overflow (Tx) 256 Rx head-of-line blocking FIFO overflow
vcTable	1.3.6.1.4.1.6368.2.8.4		not-accessible	This table contains additional information for VC concerning the multiplexing configuration. It's an extension of the ifTable (IF-MIB) and the tables of the SONET/SDH-MIB.
vcEntry	1.3.6.1.4.1.6368.2.8.4.1		not-accessible	Row and index definition for the vcConfigTable.
VIR vcType	1.3.6.1.4.1.6368.2.8.4.1.1	VirtualContainerTypeEnum	read-only	Type of Virtual Container (VC). In Pegasus VC-4, VC-3 or VC-12.
TUG vcRelatedTUG	1.3.6.1.4.1.6368.2.8.4.1.2	TUGIndexOrZero	read-only	Represents the index of the Tributary Unit Group within the tugConfigTable to which this VC is assigned to. The value depends also on the multiplexing mode. If the value is 0, there doesn't exist the relation VC-x to TUG-3. Possible values: 1) multiplexing mode = AU-4: VC-4: vcRelatedTUG = 0 VC-3/12: vcRelatedTUG = 1..3 2) multiplexing mode = AU-3: vcRelatedTUG = 0 (no dependency on VC type)
NUM vcRelatedVC	1.3.6.1.4.1.6368.2.8.4.1.3	InterfaceIndexOrZero	read-only	Represents the index of the Virtual Container within the ifTable to which this VC is assigned to. The value depends also on the multiplexing mode. If the value is 0, there doesn't exist the relation VC-x to VC-x. Possible values: 1) multiplexing mode = AU-4: vcRelatedVC = 0 (no dependency on VC type) 2) multiplexing mode = AU-3: VC-3: vcRelatedVC = 0 VC-12: vcRelatedVC = 2031..2033 (example for slot 2)
NUM vcAssignedIfIndex	1.3.6.1.4.1.6368.2.8.4.1.4	InterfaceIndexOrZero	read-write	Represents the index of the interface within the ifTable (IF-MIB) that transmits to this VC.
STR vcPathTraceSend	1.3.6.1.4.1.6368.2.8.4.1.5	DisplayString	read-write	The value of the outgoing J1 Byte VC Path Trace byte message.
STR vcPathTraceExpected	1.3.6.1.4.1.6368.2.8.4.1.6	DisplayString	read-write	The value of the expected J1 Byte VC Path Trace byte message.
STR vcPathTraceReceive	1.3.6.1.4.1.6368.2.8.4.1.7	DisplayString	read-only	The value of the incoming J1 Byte VC Path Trace byte message.
SIG vcSignalLabelSend	1.3.6.1.4.1.6368.2.8.4.1.8	SignalLabel	read-write	The outgoing C2 VC Signal Label (0x02 = TUG structure).
SIG vcSignalLabelExpected	1.3.6.1.4.1.6368.2.8.4.1.9	SignalLabel	read-write	The expected C2 VC Signal Label (0x02 = TUG structure).
SIG vcSignalLabelReceive	1.3.6.1.4.1.6368.2.8.4.1.10	SignalLabel	read-only	The incoming C2 VC Signal Label (0x02 = TUG structure).
I32 vcAlarmStatus	1.3.6.1.4.1.6368.2.8.4.1.11	Integer32	read-only	This variable indicates the status of the VC. It's a bitmap represented as a sum. Therefore multiple defects can be displayed simultaneously. The value noDefect should only be set if there is no other defect. Some alarms can't occur actually. The various bit positions are: 1 vcNoDefect 2 vcAlarmAIS 4 vcAlarmLOP 8 vcAlarmRDI 16 vcAlarmUnequipped 32 vcAlarmPLM 64 vcAlarmTIM 128 vcAlarmLOM 256 vcAlarmRFI 512 vcgTxAddTimeout -- not used (deprecated) 1024 vcgTxAdd -- not used (deprecated) 2048 vcgTxRemove -- not used (deprecated) 4096 vcgTxDnu -- not used (deprecated) 8192 vcgDnuOk -- not used (deprecated) 16384 vcgRxAdd -- not used (deprecated) 32768 vcgRxRemove -- not used (deprecated) 65536 vcgRxFail -- not used (deprecated) 131072 vcgLcasCrcError 262144 vcgNonLcasSeqError
tugConfigTable	1.3.6.1.4.1.6368.2.8.5		not-accessible	This table contains information concerning Tributary Unit Groups. If AU-3 structure is used, this table is empty.
tugConfigEntry	1.3.6.1.4.1.6368.2.8.5.1		not-accessible	Row and index definition for the tugConfigTable.
TUG tugIndex	1.3.6.1.4.1.6368.2.8.5.1.1	TUGIndex	not-accessible	Number of the TUG. Range 1..3
NUM tugRelatedVC4	1.3.6.1.4.1.6368.2.8.5.1.2	InterfaceIndex	read-only
ORD tugOrderLevel	1.3.6.1.4.1.6368.2.8.5.1.3	OrderLevelEnum	read-write	Individual Order Level of this TUG. If high order is used, the TUG has exactly one VC-3 and no VC-12s. If low order is used, the TUG has exactly 21 VC-12 and no VC-3.
STR sdhMibRevision	1.3.6.1.4.1.6368.2.8.6	DisplayString	read-only	The version number assigned by the version control system. You can query this from the agent, to find out with which version of the MIB was built into the agent. The value is also present in copies of the MIB to feed into SNMP managers. Comparing the version numbers from both sources can help to detect mismatches. The revision string for this version is: $Workfile: PEGASUS-SDH-MIB.txt $ $Revision: 14 $ $Date: 3/18/04 6:40p $

RFC description

SDH/STM-1 management module for Schmid Telecom PEGASUS SDSL products. Manages STM-1 cards, virtual containers, Ethernet interfaces, and tributary unit groups.

Start monitoring Schmid Telecom Pegasus STM-1 microwave/SDSL transport cards (SDH/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download PEGASUS-SDH-MIB