HM2-L2REDUNDANCY-MIB: View SNMP OID List / Download MIB

Hirschmann Layer 2 Redundancy MIB. Copyright (C) 2011. All Rights Reserved.

This notification is sent if the MRP ring has switched over.

This notification is sent if the SRM ring has switched over.

The Ring Coupling mechanism has switched over

The RCP Redundancy mechanism has switched over.

Every entry in this table contains information about a Media Redundancy Protocol (MRP) domain, defined by IEC 62439-2.

An entry in the hm2MrpTable.

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

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

Unique index to identify the slot number of the ringport 1 in the MRP domain.

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 frames 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. notConnected(4) indicates that the port has no link. Enumeration: 'disabled': 1, 'notConnected': 4, 'forwarding': 3, 'blocked': 2.

Unique index to identify the slot number of the ringport 2 in the MRP domain.

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 frames 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. notConnected(4) indicates that the port has no link. Enumeration: 'disabled': 1, 'notConnected': 4, 'forwarding': 3, 'blocked': 2.

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.

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. Enumeration: 'manager': 2, 'client': 1, 'undefined': 3.

The MRM defines with its parameter set the maximum recovery delay of the 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. delay30(3) specifies the parameter set for the maximum recovery delay of 30ms in the MRP domain. delay10(4) specifies the parameter set for the maximum recovery delay of 10ms in the MRP domain. Enumeration: 'delay500': 1, 'delay30': 3, 'delay200': 2, 'delay10': 4.

The 10ms and 30ms recovery time put additional restrictions on the cable length and on the reaction time of each client in the MRP ring, so these recovery times may not be supported by a MRP entity. supportedAll(1) indicates that all recovery times in hm2MrpRecoveryDelay are supported by the MRP entity. supported200500(2) indicates that only the recovery times 500ms and 200ms are supported by the MRP entity. Enumeration: 'supportedAll': 1, 'supported200500': 2.

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

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

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.

Counter will be incremented when the ring state changes to ring open.

The local time at which the ring state last changed to ring open. Measured in seconds since 00:00:00, January 1, 1970.

The max. Round-Trip-Delay (in microseconds) which was measured by the MRM since startup or reset. A device which supports only the recovery delays 200ms and 500ms doesn't support the measuring of round-trip-delay.

The min. Round-Trip-Delay (in microseconds) which was measured by the MRM since startup or reset. A device which supports only the recovery delays 200ms and 500ms doesn't support the measuring of round-trip-delay.

A write request with reset(1) will reset the values of hm2MrpMRMRoundTripDelayMax and hm2MrpMRMRoundTripDelayMin to zero at the same time. Enumeration: 'reset': 1.

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

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.

Actual ring state of the MRP redundancy domain. The ring state can only be detected by the MRM. open(1) indicates that the ring is open. closed(2) indicates that the ring is closed. undefined(3) indicates an undefined ring state or is read if hm2MrpRoleOperState indicates the value client. Enumeration: 'open': 1, 'undefined': 3, 'closed': 2.

Operational state of ring redundancy in the MRP domain. available(1) indicates that ring redundancy exists in the MRP domain. notAvailable(2) indicates that ring redundancy does not exist in the MRP domain. Enumeration: 'available': 1, 'notAvailable': 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. multipleMRM(3) indicates multiple active MRM in the ring. singleSideReceive(4) indicates that the MRM has seen it's test frames, but only on one ring port. Enumeration: 'noError': 1, 'multipleMRM': 3, 'ringportLinkError': 2, 'singleSideReceive': 4.

Supports creation, deletion and activation of rows. A row must not be active(1) in order to be modified. A row can be taken out of service by writing the value notInService(2).

If value is set to enable(1) the ringport 2 at the MRM will always be the backup port. Setting is only relevant if hm2MrpRoleAdminState is set to manager(2).

Basic implementation requirements for MRP support. The agent shall support the monitoring and control of MRP redundancy domains.

Parameters which are necessary to monitor and control the status of MRP domains.

Additional parameters which are necessary to monitor and control the status of a MRM.

Parameters which are optional to monitor and control the diagnostic status of MRP domains.

Notifications indicate changes in the MRP ring.

Fast MRP means that MRP supports also maximum recovery times of 30ms or 10ms as defined in IEC 62439-2. supported(1) indicates that the device is able to support fast recovery times for MRP like 30ms or 10ms. notSupported(2) indicates that only the MRP recovery times 500ms and 200ms are supported by the device. Enumeration: 'notSupported': 2, 'supported': 1.

Enables or disables the global SRM admin mode.

Maximum number of supported SRM instances in the hm2SrmTable.

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

Information about a Sub-Ring Manager (SRM) domain.

Identifier of the sub-ring in the SRM domain.

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. If the value is set to redundantManager(2) the entity will be in the role of the Sub-Ring Manager 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 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 hm2SrmTable are needed to build a single-manager where both instances must have singleManager(3) selected. Note: The sub-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. redundantManager(2) indicates that the entity is in the role of the Sub-Ring Manager 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.

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

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.

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

Name of the sub-ring in the SRM domain.

Interface index of sub-ring port in the SRM domain.

Operational state of sub-ring port. 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.

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.

Enables or disables the global (HIPER)Ring Redundancy admin mode.

The mode (HIPER)Ring Redundancy is configured. Enumeration: 'ring-switch': 1.

Interface index of the primary interface.

Operational state of the primary ring port. The port states are as follows, active - port is logically up and active. inactive - port is logically down. not-available - no Hiper Ring instance is running, check prerequisites. Enumeration: 'not-available': 1, 'active': 2, 'inactive': 3.

Interface index of the secondary interface.

Operational state of the secondary ring port. The port states are as follows, active - port is logically up and active. inactive - port is logically down. not-available - no Hiper Ring instance is running, check prerequisites. Enumeration: 'not-available': 1, 'active': 2, 'inactive': 3.

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

The entry of the hm2RingCouplingTable.

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

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.

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

Operational state of the control interface in case of outband-control.

Interface index identifies the coupling link of the partner in the ring coupling. This variable can only be set if the hm2RingCplControlMode 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.

Partner IP Address type.

IP Address of the partner in the ring coupling.

Ring-coupling operating mode . In single(1) mode both coupling ports are local to the switch, switch performs master and slave functions. In dual-master-inband(2) mode second coupling port is on a remote switch, local switch is master, communication over network. In dual-master-outband(3) mode second coupling port is on a remote switch, local switch is master, communication over dedicated control port. In dual-slave-inband(4) mode second coupling port is on a remote switch, local switch is slave, communication over network. In dual-slave-outband(5) mode second coupling port is on a remote switch, local switch is slave, communication over dedicated control port. unknown(6) cannot be set,it's returned when no mode is configured. Enumeration: 'dual-master-outband': 3, 'unknown': 6, 'dual-slave-outband': 5, 'single': 1, 'dual-slave-inband': 4, 'dual-master-inband': 2.

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. Enumeration: 'unknown': 3, 'local': 4, 'inband': 2, 'outband': 1.

Mode of operation . slaveOn(2) slave is activated. slaveOff(1) slave is deactivated, the ring coupling is disabled and the switch acts from now in normal rs mode. Enumeration: 'slaveOff': 1, 'slaveOn': 2.

Operational state of an entry. If a new entry is created by setting hm2RingCplRowStatus 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. Enumeration: 'underCreation': 1, 'master': 3, 'slave': 2, 'local': 4.

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

Operational state of the Ring/Net coupling redundancy. redGuaranteed(1) indicates that redundancy is guaranteed in the ring coupling. redNotGuaranteed(2) indicates that redundancy is not guaranteed in the ring coupling. Enumeration: 'redGuaranteed': 1, 'redNotGuaranteed': 2.

Defines the status of a ring coupling database entry.

Enables or disables the global RCP admin state.

The inner coupling port of the primary ring.

The outer coupling port of the primary ring.

The inner coupling port of the secondary ring

The outer coupling port of the secondary ring

Configurable role of the RCP coupler. Enumeration: 'slave': 2, 'master': 1, 'auto': 4.

Current role of the RCP coupler. Enumeration: 'disabled': 5, 'slave': 2, 'master': 1, 'listening': 3, 'error': 4.

RCP coupler timeout in milliseconds.

MAC address of the coupling partner.

Port of the coupling partner in the primary ring.

Port of the coupling partner in the secondary ring.

current forwarding state of the RCP coupler. Enumeration: 'forwarding': 1, 'blocking': 2.

Indicates if coupling redundancy is available. Enumeration: 'redNotAvailable': 2, 'redAvailable': 1.

Partner IP Address type.

IP address of the coupling partner.

Could not enable Ring/Net Coupling configuration. In {0} control mode the {1} should be selected, different from the coupling port and in the valid range.

Could not enable RCP. The required ports are not configured.