PEGASUS-SDH-MIB :: stm1CardMgmtCommState

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › PEGASUS-SDH-MIB › stm1CardMgmtCommState

stm1CardMgmtCommState

Module: PEGASUS-SDH-MIB

OID (symbolic): PEGASUS-SDH-MIB::stm1CardMgmtCommState

OID (numeric): 1.3.6.1.4.1.6368.2.8.1.1.19

Node type: OBJECT-TYPE

Type: CommStateEnum

Access: read-only

Description: 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.

What is stm1CardMgmtCommState?

This shows the state of the management connection between the PEM Server and this STM-1 card, progressing through states like init, identification, check hardware, check config version, status synch, and finally active once fully established. Admins use this to diagnose why a card isn't showing up as manageable, e.g. a card stuck at 'check hardware' suggests a configured-vs-actual hardware mismatch.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6368.2.8.1.1.19
snmpwalk -v2c -c public <target> PEGASUS-SDH-MIB::stm1CardMgmtCommState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6368.2.8.1.1.19.1
snmpget -v2c -c public <target> PEGASUS-SDH-MIB::stm1CardMgmtCommState.1

Start monitoring Schmid Telecom Pegasus STM-1 microwave/SDSL transport cards (SDH/clock status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the PEGASUS-SDH-MIB::stm1CardMgmtCommState OID value, configure state conditions and alerts, and monitor any Schmid Telecom Pegasus STM-1 microwave/SDSL transport cards (SDH/clock status) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.6368schmidtelecomPEGASUS-MIB
1.3.6.1.4.1.6368.2pegasusMibModulePEGASUS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6368.2.8pegasusSdhMibModulePEGASUS-SDH-MIB
1.3.6.1.4.1.6368.2.8.1stm1CardTablePEGASUS-SDH-MIB
1.3.6.1.4.1.6368.2.8.1.1stm1CardEntryPEGASUS-SDH-MIB
1.3.6.1.4.1.6368.2.8.1.1.19stm1CardMgmtCommStatePEGASUS-SDH-MIB