OID reference

lldpRemTable

1.3.6.1.4.1.3320.127.1.4.1

Description

This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one lldpRemEntry is present for each local port, or it may choose to maintain multiple lldpRemEntries for the same local port. The following procedure may be used to retrieve remote systems …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.3320.127.1.4 (lldpRemoteSystemsData, lldpExtens)
Node code
1
Node name
lldpRemTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.3320.127.1.4.1
URN notation
urn:oid:1.3.6.1.4.1.3320.127.1.4.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 3320 127 1 4 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bdcom(3320) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bdcom(3320) nmslldpMIB(127) lldpObjects(1) lldpExtens(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(3320) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(3320) nmslldpMIB(127) lldpObjects(1) lldpExtens(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bdcom(3320) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bdcom(3320) nmslldpMIB(127) lldpObjects(1) lldpExtens(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nms(3320) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nms(3320) nmslldpMIB(127) lldpObjects(1) lldpExtens(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bdcom(3320) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bdcom(3320) nmslldpMIB(127) lldpObjects(1) lldpExtens(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nms(3320) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nms(3320) nmslldpMIB(127) lldpObjects(1) lldpExtens(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bdcom(3320) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bdcom(3320) nmslldpMIB(127) lldpObjects(1) lldpExtens(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nms(3320) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nms(3320) nmslldpMIB(127) lldpObjects(1) lldpExtens(4) lldpRemTable(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/3320/127/1/4/1
  • /ISO/Identified-Organization/6/1/4/1/3320/127/1/4/1
  • /ISO/3/6/1/4/1/3320/127/1/4/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/bdcom/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
  • /iso/identified-organization/dod/internet/private/enterprise/bdcom/nmslldpMIB/lldpObjects/lldpExtens/lldpRemTable
  • /iso/identified-organization/dod/internet/private/enterprise/nms/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
  • /iso/identified-organization/dod/internet/private/enterprise/nms/nmslldpMIB/lldpObjects/lldpExtens/lldpRemTable
  • /iso/identified-organization/dod/internet/private/enterprises/bdcom/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
  • /iso/identified-organization/dod/internet/private/enterprises/bdcom/nmslldpMIB/lldpObjects/lldpExtens/lldpRemTable
  • /iso/identified-organization/dod/internet/private/enterprises/nms/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
  • /iso/identified-organization/dod/internet/private/enterprises/nms/nmslldpMIB/lldpObjects/lldpExtens/lldpRemTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/bdcom/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/bdcom/nmslldpMIB/lldpObjects/lldpExtens/lldpRemTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nms/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nms/nmslldpMIB/lldpObjects/lldpExtens/lldpRemTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/bdcom/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/bdcom/nmslldpMIB/lldpObjects/lldpExtens/lldpRemTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/nms/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/nms/nmslldpMIB/lldpObjects/lldpExtens/lldpRemTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF LldpRemEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

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

Product context

Documented MIB packages

The FS.COM catalogue lists MIB packages containing this definition for these models:

IES3100-16TM, IES3100-8T4F-P, IES3100-8TF, IES3100-8TF-P, S3150-8T2FP, S3400-24T4FP, S3400-24T4SP, S3400-48T4SP, S3400-48T6SP, S5500-48T6SP-R.

A definition in a model's MIB package does not establish that the device implements it or permits access.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

lldpRemTable · current

lldpRemTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF LldpRemEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            "This table contains one or more rows per physical network
            connection known to this agent.  The agent may wish to ensure
            that only one lldpRemEntry is present for each local port,
            or it may choose to maintain multiple lldpRemEntries for
            the same local port.

            The following procedure may be used to retrieve remote
            systems information updates from an LLDP agent:

               1. NMS polls all tables associated with remote systems
                  and keeps a local copy of the information retrieved.
                  NMS polls periodically the values of the following
                  objects:
                     a. lldpStatsRemTablesInserts
                     b. lldpStatsRemTablesDeletes
                     c. lldpStatsRemTablesDrops
                     d. lldpStatsRemTablesAgeouts
                     e. lldpStatsRxPortAgeoutsTotal for all ports.

               2. LLDP agent updates remote systems MIB objects, and
                  sends out notifications to a list of notification
                  destinations.

               3. NMS receives the notifications and compares the new
                  values of objects listed in step 1.  

                  Periodically, NMS should poll the object
                  lldpStatsRemTablesLastChangeTime to find out if anything
                  has changed since the last poll.  if something has
                  changed, NMS will poll the objects listed in step 1 to
                  figure out what kind of changes occurred in the tables.

                  if value of lldpStatsRemTablesInserts has changed,
                  then NMS will walk all tables by employing TimeFilter
                  with the last-polled time value.  This request will
                  return new objects or objects whose values are updated
                  since the last poll.

                  if value of lldpStatsRemTablesAgeouts has changed,
                  then NMS will walk the lldpStatsRxPortAgeoutsTotal and
                  compare the new values with previously recorded ones.
                  For ports whose lldpStatsRxPortAgeoutsTotal value is
                  greater than the recorded value, NMS will have to
                  retrieve objects associated with those ports from
                  table(s) without employing a TimeFilter (which is
                  performed by specifying 0 for the TimeFilter.)

                  lldpStatsRemTablesDeletes and lldpStatsRemTablesDrops
                  objects are provided for informational purposes."
    ::= { lldpRemoteSystemsData 1 }

lldpRemTable · current

lldpRemTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF LldpRemEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            "This table contains one or more rows per physical network
            connection known to this agent.  The agent may wish to ensure
            that only one lldpRemEntry is present for each local port,
            or it may choose to maintain multiple lldpRemEntries for
            the same local port.

            The following procedure may be used to retrieve remote
            systems information updates from an LLDP agent:

               1. NMS polls all tables associated with remote systems
                  and keeps a local copy of the information retrieved.
                  NMS polls periodically the values of the following
                  objects:
                     a. lldpStatsRemTablesInserts
                     b. lldpStatsRemTablesDeletes
                     c. lldpStatsRemTablesDrops
                     d. lldpStatsRemTablesAgeouts
                     e. lldpStatsRxPortAgeoutsTotal for all ports.

               2. LLDP agent updates remote systems MIB objects, and
                  sends out notifications to a list of notification
                  destinations.

               3. NMS receives the notifications and compares the new
                  values of objects listed in step 1.  

                  Periodically, NMS should poll the object
                  lldpStatsRemTablesLastChangeTime to find out if anything
                  has changed since the last poll.  if something has
                  changed, NMS will poll the objects listed in step 1 to
                  figure out what kind of changes occurred in the tables.

                  if value of lldpStatsRemTablesInserts has changed,
                  then NMS will walk all tables by employing TimeFilter
                  with the last-polled time value.  This request will
                  return new objects or objects whose values are updated
                  since the last poll.

                  if value of lldpStatsRemTablesAgeouts has changed,
                  then NMS will walk the lldpStatsRxPortAgeoutsTotal and
                  compare the new values with previously recorded ones.
                  For ports whose lldpStatsRxPortAgeoutsTotal value is
                  greater than the recorded value, NMS will have to
                  retrieve objects associated with those ports from
                  table(s) without employing a TimeFilter (which is
                  performed by specifying 0 for the TimeFilter.)

                  lldpStatsRemTablesDeletes and lldpStatsRemTablesDrops
                  objects are provided for informational purposes."
    ::= { lldpRemoteSystemsData 1 }

Meaning

Descriptions

1 unique

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

This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one lldpRemEntry is present for each local port, or it may choose to maintain multiple lldpRemEntries for the same local port. The following procedure may be used to retrieve remote systems information updates from an LLDP agent: 1. NMS polls all tables associated with remote systems and keeps a local copy of the information retrieved. NMS polls periodically the values of the following objects: a. lldpStatsRemTablesInserts b. lldpStatsRemTablesDeletes c. lldpStatsRemTablesDrops d. lldpStatsRemTablesAgeouts e. lldpStatsRxPortAgeoutsTotal for all ports. 2. LLDP agent updates remote systems MIB objects, and sends out notifications to a list of notification destinations. 3. NMS receives the notifications and compares the new values of objects listed in step 1. Periodically, NMS should poll the object lldpStatsRemTablesLastChangeTime to find out if anything has changed since the last poll. if something has changed, NMS will poll the objects listed in step 1 to figure out what kind of changes occurred in the tables. if value of lldpStatsRemTablesInserts has changed, then NMS will walk all tables by employing TimeFilter with the last-polled time value. This request will return new objects or objects whose values are updated since the last poll. if value of lldpStatsRemTablesAgeouts has changed, then NMS will walk the lldpStatsRxPortAgeoutsTotal and compare the new values with previously recorded ones. For ports whose lldpStatsRxPortAgeoutsTotal value is greater than the recorded value, NMS will have to retrieve objects associated with those ports from table(s) without employing a TimeFilter (which is performed by specifying 0 for the TimeFilter.) lldpStatsRemTablesDeletes and lldpStatsRemTablesDrops objects are provided for informational purposes.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)FS.COM official Documentation Hub native MIB packages

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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), FS.COM official Documentation Hub native MIB packages1 record · 3 sources

Description 1

lldpRemTable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), FS.COM official Documentation Hub native MIB packages3 sources

Status in source: current.

Names: lldpRemTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "lldpRemTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "LldpRemEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one lldpRemEntry is present for each local port, or it may choose to maintain multiple lldpRemEntries for the same local port. The following procedure may be used to retrieve remote systems information updates from an LLDP agent: 1. NMS polls all tables associated with remote systems and keeps a local copy of the information retrieved. NMS polls periodically the values of the following objects: a. lldpStatsRemTablesInserts b. lldpStatsRemTablesDeletes c. lldpStatsRemTablesDrops d. lldpStatsRemTablesAgeouts e. lldpStatsRxPortAgeoutsTotal for all ports. 2. LLDP agent updates remote systems MIB objects, and sends out notifications to a list of notification destinations. 3. NMS receives the notifications and compares the new values of objects listed in step 1. Periodically, NMS should poll the object lldpStatsRemTablesLastChangeTime to find out if anything has changed since the last poll. if something has changed, NMS will poll the objects listed in step 1 to figure out what kind of changes occurred in the tables. if value of lldpStatsRemTablesInserts has changed, then NMS will walk all tables by employing TimeFilter with the last-polled time value. This request will return new objects or objects whose values are updated since the last poll. if value of lldpStatsRemTablesAgeouts has changed, then NMS will walk the lldpStatsRxPortAgeoutsTotal and compare the new values with previously recorded ones. For ports whose lldpStatsRxPortAgeoutsTotal value is greater than the recorded value, NMS will have to retrieve objects associated with those ports from table(s) without employing a TimeFilter (which is performed by specifying 0 for the TimeFilter.) lldpStatsRemTablesDeletes and lldpStatsRemTablesDrops objects are provided for informational purposes.\"",
    "::=",
    "{",
    "lldpRemoteSystemsData",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "LldpRemEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one lldpRemEntry is present for each local port, or it may choose to maintain multiple lldpRemEntries for the same local port. The following procedure may be used to retrieve remote systems information updates from an LLDP agent: 1. NMS polls all tables associated with remote systems and keeps a local copy of the information retrieved. NMS polls periodically the values of the following objects: a. lldpStatsRemTablesInserts b. lldpStatsRemTablesDeletes c. lldpStatsRemTablesDrops d. lldpStatsRemTablesAgeouts e. lldpStatsRxPortAgeoutsTotal for all ports. 2. LLDP agent updates remote systems MIB objects, and sends out notifications to a list of notification destinations. 3. NMS receives the notifications and compares the new values of objects listed in step 1. Periodically, NMS should poll the object lldpStatsRemTablesLastChangeTime to find out if anything has changed since the last poll. if something has changed, NMS will poll the objects listed in step 1 to figure out what kind of changes occurred in the tables. if value of lldpStatsRemTablesInserts has changed, then NMS will walk all tables by employing TimeFilter with the last-polled time value. This request will return new objects or objects whose values are updated since the last poll. if value of lldpStatsRemTablesAgeouts has changed, then NMS will walk the lldpStatsRxPortAgeoutsTotal and compare the new values with previously recorded ones. For ports whose lldpStatsRxPortAgeoutsTotal value is greater than the recorded value, NMS will have to retrieve objects associated with those ports from table(s) without employing a TimeFilter (which is performed by specifying 0 for the TimeFilter.) lldpStatsRemTablesDeletes and lldpStatsRemTablesDrops objects are provided for informational purposes."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.3320)

Bin Lin

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.3320.127.1.4.1.1 lldpRemEntry1212

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.3320.127.1.4.2 lldpRemManAddrTable16
1.3.6.1.4.1.3320.127.1.4.3 lldpRemUnknownTLVTable13
1.3.6.1.4.1.3320.127.1.4.4 lldpRemOrgDefInfoTable15