PEGASUS-SDH-MIB: View SNMP OID List / Download MIB

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).

A table containing stm1 card specific information.

Row and index definition for stm1 card table.

Slot number for stm1 card.

Name of the PEGASUS device.

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.

Version number and build date of the firmware running on the line card. The format is 'major.minor YYYYMMDD hh:mm'.

Manufacturer of the STM-1 card.

Serial number of the line card. Also called HM-number, as it always starts with 'HM'. Example: HMVSS014810294.

Selects the SDH multiplexing mode. Either it is STM1-AU3-VC3 or STM1-AU4-VC4.

If trace monitoring is disable no alarm is propagated to PEM and also no RDI/AIS is inserted.

If trace monitoring is disable no alarm is propagated to PEM and also no RDI/AIS is inserted.

If trace monitoring is disable no alarm is propagated to PEM and also no RDI/AIS is inserted.

Size of the Regenerator Section Trace Message.

Configurable Regenerator Section (RS) Trace Message.

Regenerator Section (RS) Trace Message that should be received.

Regenerator Section (RS) Trace Message that is be received.

Configuration of the 'Automatic Laser Shutdown' feature.

Actual state of the laser.

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.

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.

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.

Determines, whether the PRBS Generator should be used on the optical or on the E1 links.

Determines, whether the PRBS Analyzer should be used on the optical or on the E1 links.

Determines the PRBS Pattern to be used.

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)

A table containing stm1 card specific clock information.

Row and index definition for stm1 card clock table.

Displays which clock sourceis active and used as sync source.

Sync status is OK if RX or Reference clock is valid and used as active sync source.

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.

If enabled the RX line clock can be used as sync source.

This value has always the opposite value of Reference Clock Priority.

This is the clock quality of the incoming SDH signal.

Clock status is valid if a good clock can be found on input (clock checker).

If enabled the Reference clock (V5 card input) can be used as sync source.

This value has always the opposite value of Rx Clock Priority.

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.

Clock status is valid if a good clock can be found on input (clock checker).

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).

Row and index definition for the ethernetIfTable.

Configuration of the Link Capacity Adjustment Scheme.

This attribute shows the used Ethernet encapsulation protocol.

Only relevant, if SDH Multiplexing Mode (see STM-1 card propertied) is set to VC3.

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

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.

Row and index definition for the vcConfigTable.

Type of Virtual Container (VC). In Pegasus VC-4, VC-3 or VC-12.

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)

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)

Represents the index of the interface within the ifTable (IF-MIB) that transmits to this VC.

The value of the outgoing J1 Byte VC Path Trace byte message.

The value of the expected J1 Byte VC Path Trace byte message.

The value of the incoming J1 Byte VC Path Trace byte message.

The outgoing C2 VC Signal Label (0x02 = TUG structure).

The expected C2 VC Signal Label (0x02 = TUG structure).

The incoming C2 VC Signal Label (0x02 = TUG structure).

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

This table contains information concerning Tributary Unit Groups. If AU-3 structure is used, this table is empty.

Row and index definition for the tugConfigTable.

Number of the TUG. Range 1..3

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.

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 $