HMRING-MGMT-SNMP-MIB :: hmSrmConfigOperState

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › HMRING-MGMT-SNMP-MIB › hmSrmConfigOperState

hmSrmConfigOperState

Module: HMRING-MGMT-SNMP-MIB

OID (symbolic): HMRING-MGMT-SNMP-MIB::hmSrmConfigOperState

OID (numeric): 1.3.6.1.4.1.248.14.5.5.5.1.12

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Operational state of the configuration in the SRM domain. noError(1) indicates that no configuration error was detected. ringportLinkError(2) indicates that the ring port has no link or one of the sub-ring lines is not connected with one of the ring ports of the entity but to another port of the entity. multipleSRM(3) indicates that the Sub-Ring Manager receives frames from more than one Sub-Ring Managers in the sub-ring. noPartnerManager(4) indicates that the Sub-Ring Manager receives his own frames. concurrentVLAN(5) indicates that the VLAN of the SRM domain is used by MRP in the basis ring. concurrentPort(6) indicates that the ringport of the SRM domain is used by another redundancy protocol. concurrentRedundancy(7) indicates the SRM domain is not active because of another active redundancy protocol. trunkMember(8) indicates that the ringport of the SRM domain is member of a trunk. sharedVLAN(9) indicates the SRM domain cannot be active because Shared VLAN is active and MRP is used in the basis ring too.

What is hmSrmConfigOperState?

Flags a range of sub-ring configuration conflicts: ringportLinkError(2) for a miswired or down ring port, multipleSRM(3) or noPartnerManager(4) for sub-ring manager pairing problems, concurrentVLAN(5)/concurrentPort(6)/concurrentRedundancy(7) for the sub-ring's VLAN or port already being claimed by MRP or another redundancy protocol on the basis ring, trunkMember(8) for a ring port that's part of a trunk (unsupported), and sharedVLAN(9) for a conflict with Shared VLAN plus MRP. An admin checks this value first whenever a newly configured sub-ring won't come up, since it names the specific conflict.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.248.14.5.5.5.1.12
snmpwalk -v2c -c public <target> HMRING-MGMT-SNMP-MIB::hmSrmConfigOperState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.248.14.5.5.5.1.12.1
snmpget -v2c -c public <target> HMRING-MGMT-SNMP-MIB::hmSrmConfigOperState.1

Start monitoring Hirschmann industrial Ethernet switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HMRING-MGMT-SNMP-MIB::hmSrmConfigOperState OID value, configure state conditions and alerts, and monitor any Hirschmann industrial Ethernet switches 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.248hirschmannHIRSCHMANN-GENERIC-ERROR-MIB
1.3.6.1.4.1.248.14hmConfigurationHMPRIV-MGMT-SNMP-MIB
Numeric OIDNameModule
1.3.6.1.4.1.248.14.5hmRingRedundancyHMRING-MGMT-SNMP-MIB
1.3.6.1.4.1.248.14.5.5hmMultiHiperRingHMRING-MGMT-SNMP-MIB
1.3.6.1.4.1.248.14.5.5.5hmSrmTableHMRING-MGMT-SNMP-MIB
1.3.6.1.4.1.248.14.5.5.5.1hmSrmEntryHMRING-MGMT-SNMP-MIB
1.3.6.1.4.1.248.14.5.5.5.1.12hmSrmConfigOperStateHMRING-MGMT-SNMP-MIB