Reference record for OID 1.3.6.1.4.1.52642.127.1.4.1

Parent
1.3.6.1.4.1.52642.127.1.4 (lldpExtens, lldpRemoteSystemsData)
Node code
1
Node name
lldpRemTable
Numeric OID
1.3.6.1.4.1.52642.127.1.4.1
URN notation
urn:oid:1.3.6.1.4.1.52642.127.1.4.1
ASN.1 notation

{1 3 6 1 4 1 52642 127 1 4 1}

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

Descriptions

lldpRemTable — FS.COM official S3900-R MIB package, FS.COM MIB copies (LibreNMS/Observium Community)

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.

Source records

lldpRemTable

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
  ]
}
  • FS.COM MIB copies (LibreNMS/Observium Community) · Publisher's source file: NMS-LLDP-MIB

    Vendor MIB copy from the LibreNMS archive. FS.COM support.

    Module: NMS-LLDP-MIB

    Published 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 }
    Module imports
    {'NMS-SMI': ['nms'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'IANA-ADDRESS-FAMILY-NUMBERS-MIB': ['AddressFamilyNumbers']}

    Related source files and packages:


    Source location: NMS-LLDP-MIB::lldpRemTable.
    Source version and references

    Downloaded: 2026-10-23T19:25:11.684116+00:00.

  • FS.COM MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive. FS.COM support.

    Module: FS-NMS-LLDP-MIB

    Published 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 }
    Module imports
    {'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TimeStamp', 'TruthValue'], 'FS-NMS-SMI': ['nms'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'IANA-ADDRESS-FAMILY-NUMBERS-MIB': ['AddressFamilyNumbers']}

    Related source files and packages:


    Source location: FS-NMS-LLDP-MIB::lldpRemTable.
    Source version and references

    Downloaded: 2026-10-23T19:25:17.905938+00:00.

  • FS.COM official S3900-R MIB package · Publisher's source file: Source package: 20230724154543a6vsk6.zip

    Module: NMS-LLDP-MIB

    Published 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 }
    Module imports
    {'NMS-SMI': ['nms'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'IANA-ADDRESS-FAMILY-NUMBERS-MIB': ['AddressFamilyNumbers']}

    Related source files and packages:


    Source location: NMS-LLDP-MIB::lldpRemTable.
    Source version and references

    Downloaded: 2026-10-23T18:41:52.601356+00:00.

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.52642)

FS.COM INC

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.52642.127.1.4.1.1 lldpRemEntry1212

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.52642.127.1.4.2 lldpRemManAddrTable16
1.3.6.1.4.1.52642.127.1.4.3 lldpRemUnknownTLVTable13
1.3.6.1.4.1.52642.127.1.4.4 lldpRemOrgDefInfoTable15