HMRING-MGMT-SNMP-MIB: View SNMP OID List / Download MIB

The Hirschmann Private Ring Redundancy MIB definitions for Platform devices.

The events of hmAgent.

The Ring Redundancy mechanism has switched over

The Ring Coupling mechanism has switched over

The configuration of the Ring Redundancy has changed.

The Media Redundancy Protocol mechanism has switched over. This trap is only sent if hmMrpMRMCheckMediaRedundancy is enabled.

The Ring Redundancy mechanism has switched over.

The Ring Redundancy mechanism has switched over.

This table contains variables to define an entry in the ring redundancy database.

The entry of the hmRingRedTable.

Unique index to identify the slot number of the primary link port. This value is never greater than hmSysGroupCapacity. Note that row creation is done only by writing to hmRingRedMode

Interface index of the primary link. Note that row creation is only done by writing to hmRingRedMode

operational state of the primary interface. Enumeration: 'not-available': 1, 'active': 2, 'inactive': 3.

Unique index to identify the slot number of the redundant link port. This value is never greater than hmSysGroupCapacity.

Interface index of the redundant link.

operational state of the redundant interface. Enumeration: 'not-available': 1, 'active': 2, 'inactive': 3.

operational state of an entry. If a new entry is created by setting hmRingRedMode to create(1), the operState returns a value of underCreation(1). rmActive(2) indicates that redundancy-manager is configured and a ring failure has occured. rmInactive(3) indicates that redundancy-manager is configured and ring is ok. The value rs(4) is returend when hmRingRedMode is set to rs(4). Enumeration: 'underCreation': 1, 'rmActive': 2, 'disable': 5, 'rmInactive': 3, 'rs': 4.

Desired mode of operation. To create, modify or deactivate an entry the value create(1) have to be set. delete(2) removes the entry. rm(3) and rs(4) activate the redundancy. Enumeration: 'rm': 3, 'create': 1, 'rs': 4, 'disable': 5, 'delete': 2.

Operational state of the ring configuration. rmConfigError(2) indicates that the ring is not connected with both ringports of the redundancy manager, one of the ring cables is connected to another port of the redundancy manager. ringConfigError(3) is returned when somewhere in the ring a ring connection fails. anotherRM(4) indicates that another redundancy manager was detected in the same ring. In this case the redundant ring ports of these redundancy managers are blocked until only one redundancy manager remains in the ring. Notice: rmConfigError(2) and ringConfigError(3) can only be detected by the redundancy manager if the redundancy manager is inactive. Enumeration: 'ringConfigError': 3, 'noError': 1, 'rmConfigError': 2, 'anotherRM': 4.

The hmRingRedRecoveryDelay with its parameter set defines the maximum recovery delay of ring recovery in the HIPER Ring. delay500(1) specifies the parameter set for the maximum recovery delay of 500ms in the HIPER Ring. delay300(2) specifies the parameter set for the maximum recovery delay of 300ms in the HIPER Ring. Enumeration: 'delay500': 1, 'delay300': 2.

This table contains variables to define an entry in the ring coupling database.

The entry of the hmRingCouplingTable.

Unique index to identify the slot number of the coupling link port. This value is never greater than hmSysGroupCapacity. Note that row creation is done only by writing to hmRingCplRowStatus.

Interface index of the coupling link. Note that only those ports can be chosen which do not belong to another L2 redundancy mechanism like ring redundancy or dual homing and that row creation is only done by writing to hmRingCplRowStatus.

Operational state of the coupling interface. active(2) indicates that the port is switching. standby(3) indicates that the port is in standby mode. On the slave active(2) indicates that a ring coupling failure has occured and the port is switching. On the slave standby(3) indicates that the ring coupling is ok and the slave is in standby mode. Enumeration: 'active': 2, 'standby': 3, 'not-connected': 1.

Unique index to identify the slot number of the control link port in case of outband-control. This value is never greater than hmSysGroupCapacity.

Interface index of the control link in case of outband-control. Note that only those ports can be chosen which do not belong to another L2 redundancy mechanism like ring redundancy or dual homing and that row creation is only done by writing to hmRingCplRowStatus.

Operational state of the control interface in case of outband-control. Enumeration: 'active': 2, 'standby': 3, 'not-connected': 1.

Control mode of the ring coupling which can only be chosen by the slave, the master just reports his current control mode. unknown(3) cannot be set. In outband(1) mode an additional line must connect the control interfaces between the two partners in the ring coupling. In inband(2) mode only the coupling link port is needed. In local(4) mode the coupling link port and the partner port are located on the same switch. disable(5) deactivates the ring coupling functionality. Enumeration: 'unknown': 3, 'disable': 5, 'local': 4, 'inband': 2, 'outband': 1.

IP Address of the partner in the ring coupling.

Index identifies the slot number of the coupling link port of the partner in the ring coupling. This variable can only be set if the hmRingCplControlMode is local(4).

Interface index identifies the coupling link of the partner in the ring coupling. This variable can only be set if the hmRingCplControlMode is local(4).

Operational state of the coupling interface of the partner in the ring coupling. active(2) indicates that the partner port is switching. standby(3) indicates that the partner port is in standby mode. Enumeration: 'active': 2, 'standby': 3, 'not-connected': 1.

Operational state of an entry. If a new entry is created by setting hmRingCplRowStatus to create(1), the operState returns a value of underCreation(1). slave(2) indicates that switch is configured to be the slave of the ring coupling, that means the switch is in standby mode. master(3) indicates that a switch is configured to be the master of the ring coupling. local(4) indicates that the switch is configured to control a ring coupling where the coupling port and the partner port are located on the same switch. disable(5) indicates that the ring coupling functionality is switched off. Enumeration: 'underCreation': 1, 'master': 3, 'disable': 5, 'slave': 2, 'local': 4.

Desired mode of operation. slaveOn(2) activates the slave. slaveOff(1) deactivates the slave, the ring coupling is disabled and the switch acts from now in normal rs mode. Note that this mode can only be set if the slave is not activated or deactivated by a DIP-switch. disable(3) indicates that the ring coupling functionality is switched off. Enumeration: 'slaveOff': 1, 'disable': 3, 'slaveOn': 2.

Defines the status of a ring coupling database entry.

Operational state of the ring coupling configuration. slaveCouplingLinkError(2) indicates that the coupling link is not connected with the coupling port of the slave but with another port of the slave. In case of outband control additional failures can be detected: slaveControlLinkError(3) indicates that the control port of the slave has either no link or the link fails. masterControlLinkError(4) indicates that the control link is not connected with the control port of the master but with another port of the master. twoSlaves(5) is returned when two slaves are connected by the control line. localPartnerLinkError(6) indicates that the partner coupling link is not connected with the partner port of the slave but with another port of the slave in local control mode. localInvalidCouplingPort(7) indicates that in local mode the coupling line is connected to another switch and not on the same switch like the partner line. couplingPortNotAvailable(8), controlPortNotAvailable(9) and partnerPortNotAvailable(10) indicate that this port is not available because the module related to this port is not available or the port does not exist on this module. Enumeration: 'masterControlLinkError': 4, 'partnerPortNotAvailable': 10, 'slaveCouplingLinkError': 2, 'couplingPortNotAvailable': 8, 'twoSlaves': 5, 'noError': 1, 'slaveControlLinkError': 3, 'controlPortNotAvailable': 9, 'localPartnerLinkError': 6, 'localInvalidCouplingPort': 7.

Maximum coupling links between two coupled rings in case of a failure in one of the coupled rings. If there is no connection starting from the switch in slave or local operational state over the route of the coupled rings or nets to oneself the slave or the local mode want to set the coupling port in forwarding after a timeout period. basicRedundancy(1) prevents the slave or the local mode from setting its coupling port into forwarding in case of the described failure. In this case the segment which is connected to this coupling port is unreachable until the failure is eliminated. In extendedRedundancy(2) the coupling port and the partner coupling port are allowed to be in forwarding. Enumeration: 'extendedRedundancy': 2, 'basicRedundancy': 1.

Additional operational states detected by the slave or in local mode. basicRedundancyInactive(2) indicates that the coupling port has been prevented from setting into forwarding (please see description of hmRingCplCouplingLinks). Enumeration: 'noError': 1, 'basicRedundancyInactive': 2.

Specifies the kind of the coupled net segment. If two HIPER Rings are coupled ringCoupling(1) must be used. In netCoupling(2) the coupled segment is no HIPER Ring topology and the switches in the coupled net segment may be connected with other ports than their ringports. Notice: if the ring coupling mechanism switches over, in ringCoupling(1) only the address tables of the switches in the two coupled HIPER Rings will be erased, in netCoupling(2) the address tables of all switches in the coupled net will be erased. Enumeration: 'netCoupling': 2, 'ringCoupling': 1.

Returns the Source by which the feature is controlled. Enumeration: 'dipSwitch': 1, 'management': 2.

Every entry in this table contains information about a Media Redundancy Protocol (MRP) domain.

An entry in the hmMrpTable.

Universally unique identifier belongs to the MRP domain which represents a ring.

Unique index to identify the slot number of the ringport 1 in the MRP domain. This value is never greater than hmSysGroupCapacity.

Interface index of the ringport 1 in the MRP domain.

Operational state of ringport 1. disabled(1) indicates that all frames are dropped. blocked(2) indicates that all frame are dropped except - MRP topology change frames and MRP test frames from a MRM, - MRP link change frames from a MRC, - frames from other protocols that also define to pass blocked(2) ports. forwarding(3) indicates that all frames are passed through according to the forwarding behavior of IEEE 802.1D. not-connected(4) indicates that the port has no link. Enumeration: 'disabled': 1, 'forwarding': 3, 'not-connected': 4, 'blocked': 2.

Unique index to identify the slot number of the ringport 2 in the MRP domain. This value is never greater than hmSysGroupCapacity.

Interface index of the ringport 2 in the MRP domain.

Operational state of ringport 2. disabled(1) indicates that all frames are dropped. blocked(2) indicates that all frame are dropped except - MRP topology change frames and MRP test frames from a MRM, - MRP link change frames from a MRC, - frames from other protocols that also define to pass blocked(2) ports. forwarding(3) indicates that all frames are passed through according to the forwarding behavior of IEEE 802.1D. not-connected(4) indicates that the port has no link. Enumeration: 'disabled': 1, 'forwarding': 3, 'not-connected': 4, 'blocked': 2.

VLAN identifier of the MRP domain.

Control the role of the MRP entity in the MRP domain. If the value is set to client(1) the entity will be in the role of a Media Redundancy Client (MRC). If the value is set to manager(2) the entity will be in the role of a Media Redundancy Manager (MRM). Enumeration: 'manager': 2, 'client': 1.

Interval for sending link down MRP link change frames on ringports.

Interval for sending link up MRP link change frames on ringports.

MRP link change frame count which controls repeated transmission of MRP link change frames.

Ability of the MRC to receive and forward MRP test frames, MRP link change frames and MRP topology change frames at a ringport whose port state is blocked. enabled(1) indicates that the MRC is able to receive and forward these MRP frames at a ringport whose port state is blocked. disabled(2) indicates that the MRC is not able to receive and forward these MRP frames at a ringport whose port state is blocked. Enumeration: 'disabled': 2, 'enabled': 1.

Priority of the MRM. A lower value indicates a higher priority.

Interval for sending MRP topology change frames on ringports.

Interval count which controls repeated transmission of MRP topology change frames.

Short interval for sending MRP test frames on ringports after link changes in the ring.

Default interval for sending MRP test frames on ringports.

Interval count for monitoring the reception of MRP test frames.

Ability of the MRM to support MRC in the ring which have hmMrpMRCBlockedSupported set disabled. enabled(1) indicates that the MRM is able to support MRC in the ring which have hmMrpMRCBlockedSupported set disabled. disabled(2) indicates that the MRM is not able to support MRC in the ring which have hmMrpMRCBlockedSupported set disabled. Enumeration: 'disabled': 2, 'enabled': 1.

Extended interval count for monitoring the reception of MRP test frames. This value is used by the MRP if hmMrpMRMNonBlockingMRCSupported is is set enabled.

Specifies whether the MRM reacts on all MRP link change frames or not. enabled(1) indicates that the MRM reacts on all MRP link change frames. disabled(2) indicates that the MRM does not react on link down MRP link change frames. Enumeration: 'disabled': 2, 'enabled': 1.

Specifies whether monitoring of MRM state is enabled or disabled in the redundancy domain. enabled(1) indicates that the MRM monitors its state. disabled(2) indicates that the MRM does not monitor its state. Enumeration: 'disabled': 2, 'enabled': 1.

Operational role of the MRP entity in the MRP domain. client(1) indicates that the MRP entity is in a MRC role. manager(2) indicates that the MRP entity is the manager MRM of this MRP domain. undefined(3) indicates that the MRP entity doesn't work. This value can only be read if hmMrpMRMCheckMediaRedundancy is set enabled. Enumeration: 'manager': 2, 'client': 1, 'undefined': 3.

Actual ring state of the redundancy domain. open(1) indicates that the ring is opened. closed(2) indicates that the ring is closed. undefined(3) indicates an undefined ring state or can be read if hmMrpMRMRealRoleState contains the value client. This value can only be read if hmMrpMRMCheckMediaRedundancy is set enabled. Enumeration: 'open': 1, 'undefined': 3, 'closed': 2.

Defines the status of the MRP database entry.

Operational state of ring redundancy in the MRP domain. redGuaranteed(1) indicates that ring redundancy is guaranteed in the MRP domain. redNotGuaranteed(2) indicates that ring redundancy is not guaranteed in the MRP domain. Enumeration: 'redGuaranteed': 1, 'redNotGuaranteed': 2.

Operational state of the configuration in the MRP domain. noError(1) indicates that no configuration error was detected. ringportLinkError(2) indicates that one of the ring lines is not connected with one of the ring ports in the MRP domain. Enumeration: 'noError': 1, 'ringportLinkError': 2.

A logical name for the MRP domain to ease the management of MRP domains.

The MRM defines with its parameter set the maximum recovery delay of ring recovery in the MRP domain. delay500(1) specifies the parameter set for the maximum recovery delay of 500ms in the MRP domain. delay200(2) specifies the parameter set for the maximum recovery delay of 200ms in the MRP domain. Enumeration: 'delay500': 1, 'delay200': 2.

Every entry in this table contains information about a Ring Protocol Control (RPC) domain.

An entry in the hmRpcTable.

Desired version of the ring protocol in the RPC domain. If the value is set to FastHiperRing(3) the entity will run the Fast Hiper Ring protocol. Note: Not all entities may support all ring protocols. If an entity does not support the desired protocol a row in this table cannot be created for this protocol. Enumeration: 'fastHiperRing': 3.

Identifier of the ring in the RPC domain.

Name of the ring in RPC domain.

Unique index to identify the slot number of ringport 1 in the RPC domain. This value is never greater than hmSysGroupCapacity.

Interface index of ringport 1 in the RPC domain.

Operational state of ringport 1. disabled(1) indicates that all frames are dropped. blocked(2) indicates that all frames are dropped except - frames used by the selected ring protocol selected which are defined to pass blocked(2) ports, - frames from other protocols which are defined to pass blocked(2) ports. forwarding(3) indicates that all frames are passed through according to the forwarding behavior of IEEE 802.1D. not-connected(4) indicates that the port has no link. Enumeration: 'disabled': 1, 'forwarding': 3, 'not-connected': 4, 'blocked': 2.

Unique index to identify the slot number of ringport 2 in the RPC domain. This value is never greater than hmSysGroupCapacity.

Interface index of ringport 2 in the RPC domain.

Operational state of ringport 2. disabled(1) indicates that all frames are dropped. blocked(2) indicates that all frames are dropped except - frames used by the selected ring protocol selected which are defined to pass blocked(2) ports, - frames from other protocols which are defined to pass blocked(2) ports. forwarding(3) indicates that all frames are passed through according to the forwarding behavior of IEEE 802.1D. not-connected(4) indicates that the port has no link. Enumeration: 'disabled': 1, 'forwarding': 3, 'not-connected': 4, 'blocked': 2.

VLAN identifier of the RPC domain. If value is set to 0 no VLAN is assigned.

Admin state of the entity in the RPC domain. If the value is set to client(1) the entity will be in the role of a redundancy client. If the value is set to manager(2) the entity will be in the role of a redundancy manager. Enumeration: 'manager': 2, 'client': 1.

Operational state of the entity in the RPC domain. client(1) indicates that the entity is in the role of a redundancy client. manager(2) indicates that the entity is in the role of a redundancy manager. disabled(3) indicates that the protocol does not work on the entity. Enumeration: 'disabled': 3, 'manager': 2, 'client': 1.

Operational state of the ring in the RPC domain. undefined(1) indicates either an undefined ring state or the entity may have the role of a redundancy client. open(1) indicates that the ring is opened. closed(2) indicates that the ring is closed. Enumeration: 'open': 2, 'undefined': 1, 'closed': 3.

Operational state of the ring redundancy in the RPC domain. redGuaranteed(1) indicates that ring redundancy is guaranteed in the RPC domain. redNotGuaranteed(2) indicates that ring redundancy is not guaranteed in the RPC domain. Enumeration: 'redGuaranteed': 1, 'redNotGuaranteed': 2.

Operational state of the configuration in the RPC domain. noError(1) indicates that no configuration error was detected. ringportLinkError(2) indicates that the ring port has no link or one of the ring lines is not connected with one of the ring ports of the entity but to another port of the entity (this may be available only if the entity has the role of a redundancy manager). singleSideReceive(3) indicates that the redundancy manager receives test frames only on one ringport (only available if the entity has the role of a redundancy manager). multipleRM(4) indicates that the redundancy manager receives frames from another redundancy manager (only available if the entity has the role of a redundancy manager). Enumeration: 'noError': 1, 'singleSideReceive': 3, 'ringportLinkError': 2, 'multipleRM': 4.

Defines the status of the RPC database entry.

Manager only: number of nodes in the RPC ring.

Manager only: maximum Round-Trip-Delay (in microseconds) which was measured since the RowStatus of the RPC domain has been set active.

Maximum number of supported SRM instances in the hmSrmTable.

Every entry in this table contains information about a Sub-Ring Manager (SRM) domain in the Multi HIPER Ring.

An entry in the hmSrmTable.

Identifier of the sub-ring in the SRM domain.

If the value is set to standardMRP(4) the entity will run the MRP protocol. Note: If using standardMRP(4) all clients in the sub-ring segment must run MRP according to IEC 62439. Enumeration: 'standardMRP': 4.

Name of the sub-ring in SRM domain.

Unique index to identify the slot number of ringport 1 in the SRM domain. This value is never greater than hmSysGroupCapacity.

Interface index of ringport 1 in the SRM domain.

Operational state of ringport 1. disabled(1) indicates that all frames are dropped. blocked(2) indicates that all frames are dropped except - frames used by the selected ring protocol which are defined to pass blocked(2) ports, - frames from other protocols which are defined to pass blocked(2) ports. forwarding(3) indicates that all frames are passed through according to the forwarding behavior of IEEE 802.1D. not-connected(4) indicates that the port has no link. Enumeration: 'disabled': 1, 'forwarding': 3, 'not-connected': 4, 'blocked': 2.

VLAN identifier of the SRM domain. If value is set to 0 no VLAN is assigned.

Admin state of the entity in the SRM domain. If the value is set to manager(1) the entity will be in the role of a Sub-Ring Manager in the Multi HIPER Ring. If the value is set to redundantManager(2) the entity will be in the role of the Sub-Ring Manager in the Multi HIPER Ring which will block its ringport if the sub-ring is closed. If the value is set to singleManager(3) the entity will be in the role of the single-manager in the Multi HIPER Ring which has both ends of a sub-ring connected and will block one of these ends if the sub-ring is closed. Note: Two instances in the hmSrmTable are needed to build a single-manager where both instances must have singleManager(3) selected. Note: The sub-ring in the Multi HIPER Ring has two managers at the same time. The redundant manager can be designated. Enumeration: 'singleManager': 3, 'manager': 1, 'redundantManager': 2.

Operational state of the entity in the SRM domain. manager(1) indicates that the entity is in the role of a Sub-Ring Manager in the Multi HIPER Ring. redundantManager(3) indicates that the entity is in the role of the Sub-Ring Manager in the Multi HIPER Ring which will block its ringport if the sub-ring is closed. singleManager(3) indicates that the entity is in the role of the single manager. disabled(4) indicates that the protocol does not work on the entity. Enumeration: 'disabled': 4, 'singleManager': 3, 'manager': 1, 'redundantManager': 2.

Operational state of the sub-ring in the SRM domain. undefined(1) indicates an undefined sub-ring state. open(2) indicates that the sub-ring is opened. closed(3) indicates that the sub-ring is closed. Enumeration: 'open': 2, 'undefined': 1, 'closed': 3.

Operational state of the ring redundancy in the SRM domain. redGuaranteed(1) indicates that ring redundancy is guaranteed in the SRM domain. redNotGuaranteed(2) indicates that ring redundancy is not guaranteed in the SRM domain. Enumeration: 'redGuaranteed': 1, 'redNotGuaranteed': 2.

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. Enumeration: 'concurrentRedundancy': 7, 'multipleSRM': 3, 'noPartnerManager': 4, 'noError': 1, 'concurrentVLAN': 5, 'sharedVLAN': 9, 'concurrentPort': 6, 'trunkMember': 8, 'ringportLinkError': 2.

Defines the status of the SRM database entry.

Number of nodes in the sub-ring. Note: Will get neccessary if the SRM runs on a fpga.

Only for MRP: Universally unique identifier belongs to the MRP domain which represents a sub-ring.

The MAC address of the partner Sub-Ring Manager in the same sub-ring domain.