OID reference

aluRS232ControlLeadsState

1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.23

Description

aluRS232ControlLeadsState is an array of byte values used to indicate the current states of the input and output control leads. These state values are historically known as scan and drive values, respectively. These state values are the ones that get transported over the network (provided there is a means, such as HCM…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1 (aluRS232Entry)
Node code
23
Node name
aluRS232ControlLeadsState
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.23
URN notation
urn:oid:1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.23
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6527 6 1 2 2 2 4 5 1 23}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) timetra(6527) tmnxBasedProducts(6) aluServiceAggrRouters(1) aluSARMIB(2) aluSARObjs(2) aluHwObjs(2) aluPortObjs(4) aluRS232Table(5) aluRS232Entry(1) aluRS232ControlLeadsState(23)}
OID-IRI notation
  • /1/3/6/1/4/1/6527/6/1/2/2/2/4/5/1/23
  • /ISO/Identified-Organization/6/1/4/1/6527/6/1/2/2/2/4/5/1/23
  • /ISO/3/6/1/4/1/6527/6/1/2/2/2/4/5/1/23
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/identified-organization/dod/internet/private/enterprises/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/identified-organization/dod/internet/private/vendor-objects/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/org/dod/internet/private/enterprise/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/org/dod/internet/private/enterprises/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/org/dod/internet/private/ldap-enterprise/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/org/dod/internet/private/vendor-objects/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/iso-identified-organization/dod/internet/private/enterprise/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/iso-identified-organization/dod/internet/private/enterprises/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/iso-organization/dod/internet/private/enterprise/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/iso-organization/dod/internet/private/enterprises/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState
  • /iso/iso-organization/dod/internet/private/vendor-objects/timetra/tmnxBasedProducts/aluServiceAggrRouters/aluSARMIB/aluSARObjs/aluHwObjs/aluPortObjs/aluRS232Table/aluRS232Entry/aluRS232ControlLeadsState

SNMP properties

Value type
OCTET STRING
Maximum access defined by MIB
read-only
Status in MIB
current
Allowed size (octets)
8

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: tmnxChassisIndex, tmnxPortPortID.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.23

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

aluRS232ControlLeadsState OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE(8))
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "aluRS232ControlLeadsState is an array of byte values used to indicate
         the current states of the input and output control leads. These state
         values are historically known as scan and drive values, respectively.
         These state values are the ones that get transported over the network
         (provided there is a means, such as HCM). As such, they are sometimes
         referred to as NETWORK-side values.
         For line-side values, see aluRS232ControlLeadsSignal.

         Each byte in the array represents the state of an individual control
         lead. The byte order is as follows:

             -- DtrDsr (LSB or byte0)
             -- RtsDcdC
             -- AlbCts
             -- RdlRi
             -- DsrDtr
             -- DcdRtsI
             -- CtsAlb
             -- RiRdl (MSB or byte7)
        
         A byte value of 1 represents on (or high as per AluRS232ControlLead).
         A byte value of 2 represents off (or low as per AluRS232ControlLead).
         All other byte values are undefined.

         A particular byte is undefined if its config counterpart is undefined.
         For example, given an X.21 interface, aluRS232ControlLeadDsrDtr is
         undefined thus, aluRS232ControlLeadsState byte 'DtrDsr' is also
         undefined.

         Some bytes can represent something else depending on the interface
         type. For example, given an RS-530, RdlRi represents LlTm.
         See the respective object for details (eg. aluRS232ControlLeadRdlRi).
         "
    ::= { aluRS232Entry 23 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

aluRS232ControlLeadsState is an array of byte values used to indicate the current states of the input and output control leads. These state values are historically known as scan and drive values, respectively. These state values are the ones that get transported over the network (provided there is a means, such as HCM). As such, they are sometimes referred to as NETWORK-side values. For line-side values, see aluRS232ControlLeadsSignal. Each byte in the array represents the state of an individual control lead. The byte order is as follows: -- DtrDsr (LSB or byte0) -- RtsDcdC -- AlbCts -- RdlRi -- DsrDtr -- DcdRtsI -- CtsAlb -- RiRdl (MSB or byte7) A byte value of 1 represents on (or high as per AluRS232ControlLead). A byte value of 2 represents off (or low as per AluRS232ControlLead). All other byte values are undefined. A particular byte is undefined if its config counterpart is undefined. For example, given an X.21 interface, aluRS232ControlLeadDsrDtr is undefined thus, aluRS232ControlLeadsState byte 'DtrDsr' is also undefined. Some bytes can represent something else depending on the interface type. For example, given an RS-530, RdlRi represents LlTm. See the respective object for details (eg. aluRS232ControlLeadRdlRi).

Sources for this description

Nokia networking MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Nokia networking MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

aluRS232ControlLeadsState · currentNokia networking MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: aluRS232ControlLeadsState

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "aluRS232ControlLeadsState",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "(",
    "SIZE",
    "(",
    "8",
    ")",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"aluRS232ControlLeadsState is an array of byte values used to indicate the current states of the input and output control leads. These state values are historically known as scan and drive values, respectively. These state values are the ones that get transported over the network (provided there is a means, such as HCM). As such, they are sometimes referred to as NETWORK-side values. For line-side values, see aluRS232ControlLeadsSignal. Each byte in the array represents the state of an individual control lead. The byte order is as follows: -- DtrDsr (LSB or byte0) -- RtsDcdC -- AlbCts -- RdlRi -- DsrDtr -- DcdRtsI -- CtsAlb -- RiRdl (MSB or byte7) A byte value of 1 represents on (or high as per AluRS232ControlLead). A byte value of 2 represents off (or low as per AluRS232ControlLead). All other byte values are undefined. A particular byte is undefined if its config counterpart is undefined. For example, given an X.21 interface, aluRS232ControlLeadDsrDtr is undefined thus, aluRS232ControlLeadsState byte 'DtrDsr' is also undefined. Some bytes can represent something else depending on the interface type. For example, given an RS-530, RdlRi represents LlTm. See the respective object for details (eg. aluRS232ControlLeadRdlRi). \"",
    "::=",
    "{",
    "aluRS232Entry",
    "23",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING",
      [
        "octetStringSubType",
        [
          [
            8
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "aluRS232ControlLeadsState is an array of byte values used to indicate the current states of the input and output control leads. These state values are historically known as scan and drive values, respectively. These state values are the ones that get transported over the network (provided there is a means, such as HCM). As such, they are sometimes referred to as NETWORK-side values. For line-side values, see aluRS232ControlLeadsSignal. Each byte in the array represents the state of an individual control lead. The byte order is as follows: -- DtrDsr (LSB or byte0) -- RtsDcdC -- AlbCts -- RdlRi -- DsrDtr -- DcdRtsI -- CtsAlb -- RiRdl (MSB or byte7) A byte value of 1 represents on (or high as per AluRS232ControlLead). A byte value of 2 represents off (or low as per AluRS232ControlLead). All other byte values are undefined. A particular byte is undefined if its config counterpart is undefined. For example, given an X.21 interface, aluRS232ControlLeadDsrDtr is undefined thus, aluRS232ControlLeadsState byte 'DtrDsr' is also undefined. Some bytes can represent something else depending on the interface type. For example, given an RS-530, RdlRi represents LlTm. See the respective object for details (eg. aluRS232ControlLeadRdlRi)."
    ],
    null,
    null,
    null,
    null
  ]
}
  • Nokia networking MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive. Nokia support.

    Module: ALU-PORT-MIB

    See published definition above

    Module imports
    {'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TimeStamp', 'TruthValue', 'RowStatus', 'DateAndTime', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Counter64', 'Unsigned32', 'Integer32', 'Counter32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'TIMETRA-TC-MIB': ['TNamedItemOrEmpty', 'TmnxActionType', 'TItemLongDescription', 'TQueueId', 'TmnxPortID', 'TmnxEnabledDisabled'], 'ALU-CHASSIS-MIB': ['aluHwObjs', 'aluHwConformance', 'aluHwNotification'], 'IEEE8021-PAE-MIB': ['dot1xPaePortNumber'], 'TIMETRA-PORT-MIB': ['tmnxDS1PortEntry', 'tmnxPortPortID', 'tmnxPortEtherEntry', 'tmnxDS0ChanGroupEntry', 'tmnxPortNotifyPortId', 'tmnxDS1Entry', 'TmnxDs0ChannelList', 'TmnxDSXIdleFillType', 'TmnxDSXIdleCycleFlags', 'TmnxDSXClockSource', 'tmnxPortCemStatsEntry', 'tmnxFrIntfEntry', 'tmnxPortEntry'], 'ALU-SAR-GLOBAL-MIB': ['aluSARMIBModules'], 'POWER-ETHERNET-MIB': ['pethPsePortEntry', 'pethPsePortPowerClassifications', 'pethPsePortDetectionStatus'], 'FRAME-RELAY-DTE-MIB': ['frCircuitEntry'], 'TIMETRA-CHASSIS-MIB': ['tmnxChassisIndex']}
    · Download ALU-PORT-MIB

    Related source files and packages:

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6527)

Marcelo Mourier

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.6527)

Jason Sterne

Siblings (39)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.1 aluRS232RowStatus00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.2 aluRS232LastChangeTime00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.3 aluRS232Type00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.4 aluRS232DeviceMode00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.5 aluRS232DeviceGender00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.6 aluRS232Duplex00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.7 aluRS232Speed00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.8 aluRS232ClockSource00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.9 aluRS232Loopback00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.10 aluRS232CharacterLength00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.11 aluRS232Parity00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.12 aluRS232StopBits00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.13 aluRS232ReportAlarm00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.14 aluRS232ReportAlarmStatus00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.15 aluRS232ControlLeadDtrDsr00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.16 aluRS232ControlLeadRtsDcdC00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.17 aluRS232ControlLeadAlbCts00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.18 aluRS232ControlLeadRdlRi00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.19 aluRS232ControlLeadDsrDtr00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.20 aluRS232ControlLeadDcdRtsI00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.21 aluRS232ControlLeadCtsAlb00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.22 aluRS232ControlLeadRiRdl00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.24 aluRS232MultiDrop00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.25 aluRS232SBitSignaling00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.26 aluRS232DataPosition00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.27 aluRS232HoldTimeUp00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.28 aluRS232HoldTimeDown00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.29 aluRS232ControlLeadsSignal00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.30 aluRS232ControlLeadMonDtrDsr00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.31 aluRS232ControlLeadMonRtsDcdC00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.32 aluRS232ControlLeadMonAlbCts00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.33 aluRS232ControlLeadMonRdlRi00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.34 aluRS232ClockSyncState00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.35 aluRS232ClockMasterPortId00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.36 aluRS232InvertClock00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.37 aluRS232MonClockDeviationRaise00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.38 aluRS232MonClockDeviationClear00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.39 aluRS232MonDataInactivityRaise00
1.3.6.1.4.1.6527.6.1.2.2.2.4.5.1.40 aluRS232MonDataInactivityClear00