OID reference

tnLldpRemPortIndexTable

1.3.6.1.4.1.7483.6.1.2.59.4.3

Description

Note that this table is same as tnLldpRemTable except that the order of two indices tnLldpRemTimeMark and tnPortPortID are reversed. This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one tnLldpRemEntry is present for each local port and des…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.7483.6.1.2.59.4 (tnLldpRemoteSystemsData)
Node code
3
Node name
tnLldpRemPortIndexTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.7483.6.1.2.59.4.3
URN notation
urn:oid:1.3.6.1.4.1.7483.6.1.2.59.4.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 7483 6 1 2 59 4 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) tropic(7483) tnProducts(6) tnSRMIB(1) tnSRObjs(2) tnLldpObjects(59) tnLldpRemoteSystemsData(4) tnLldpRemPortIndexTable(3)}
OID-IRI notation
  • /1/3/6/1/4/1/7483/6/1/2/59/4/3
  • /ISO/Identified-Organization/6/1/4/1/7483/6/1/2/59/4/3
  • /ISO/3/6/1/4/1/7483/6/1/2/59/4/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/7483/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/identified-organization/dod/internet/private/enterprise/tropic/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/identified-organization/dod/internet/private/enterprises/7483/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/identified-organization/dod/internet/private/enterprises/tropic/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/7483/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/tropic/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/7483/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/tropic/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/org/dod/internet/private/enterprise/7483/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/org/dod/internet/private/enterprise/tropic/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/org/dod/internet/private/enterprises/7483/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/org/dod/internet/private/enterprises/tropic/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/org/dod/internet/private/ldap-enterprise/7483/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/org/dod/internet/private/ldap-enterprise/tropic/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/org/dod/internet/private/vendor-objects/7483/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • /iso/org/dod/internet/private/vendor-objects/tropic/tnProducts/tnSRMIB/tnSRObjs/tnLldpObjects/tnLldpRemoteSystemsData/tnLldpRemPortIndexTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF TnLldpRemPortIndexEntry
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.

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

tnLldpRemPortIndexTable                OBJECT-TYPE
    SYNTAX     SEQUENCE OF TnLldpRemPortIndexEntry
    MAX-ACCESS not-accessible
    STATUS     current
    DESCRIPTION
        "Note that this table is same as tnLldpRemTable except that the order of two
         indices tnLldpRemTimeMark and tnPortPortID are reversed.

         This table contains one or more rows per physical network
         connection known to this agent. The agent may wish to ensure
         that only one tnLldpRemEntry is present for each local port
         and destination MAC address,
         or it may choose to maintain multiple tnLldpRemEntry rows for
         the same local port and destination MAC address.

         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. tnLldpStatsRemTablesInserts
                  b. tnLldpStatsRemTablesDeletes
                  c. tnLldpStatsRemTablesDrops
                  d. tnLldpStatsRemTablesAgeouts
                  e. tnLldpStatsRxPortAgeouts 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
               tnLldpStatsRemTablesLastChangeTime 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 tnLldpStatsRemTablesInserts 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 tnLldpStatsRemTablesAgeouts has changed,
               then NMS will walk the tnLldpStatsRxPortAgeouts and
               compare the new values with previously recorded ones.
               For ports whose tnLldpStatsRxPortAgeouts 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.)

               tnLldpStatsRemTablesDeletes and tnLldpStatsRemTablesDrops
               objects are provided for informational purposes."
    ::= { tnLldpRemoteSystemsData   3 }

Meaning

Descriptions

1 unique

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

Note that this table is same as tnLldpRemTable except that the order of two indices tnLldpRemTimeMark and tnPortPortID are reversed. This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one tnLldpRemEntry is present for each local port and destination MAC address, or it may choose to maintain multiple tnLldpRemEntry rows for the same local port and destination MAC address. 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. tnLldpStatsRemTablesInserts b. tnLldpStatsRemTablesDeletes c. tnLldpStatsRemTablesDrops d. tnLldpStatsRemTablesAgeouts e. tnLldpStatsRxPortAgeouts 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 tnLldpStatsRemTablesLastChangeTime 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 tnLldpStatsRemTablesInserts 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 tnLldpStatsRemTablesAgeouts has changed, then NMS will walk the tnLldpStatsRxPortAgeouts and compare the new values with previously recorded ones. For ports whose tnLldpStatsRxPortAgeouts 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.) tnLldpStatsRemTablesDeletes and tnLldpStatsRemTablesDrops objects are provided for informational purposes.

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

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

Status in source: current.

Names: tnLldpRemPortIndexTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "tnLldpRemPortIndexTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "TnLldpRemPortIndexEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Note that this table is same as tnLldpRemTable except that the order of two indices tnLldpRemTimeMark and tnPortPortID are reversed. This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one tnLldpRemEntry is present for each local port and destination MAC address, or it may choose to maintain multiple tnLldpRemEntry rows for the same local port and destination MAC address. 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. tnLldpStatsRemTablesInserts b. tnLldpStatsRemTablesDeletes c. tnLldpStatsRemTablesDrops d. tnLldpStatsRemTablesAgeouts e. tnLldpStatsRxPortAgeouts 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 tnLldpStatsRemTablesLastChangeTime 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 tnLldpStatsRemTablesInserts 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 tnLldpStatsRemTablesAgeouts has changed, then NMS will walk the tnLldpStatsRxPortAgeouts and compare the new values with previously recorded ones. For ports whose tnLldpStatsRxPortAgeouts 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.) tnLldpStatsRemTablesDeletes and tnLldpStatsRemTablesDrops objects are provided for informational purposes.\"",
    "::=",
    "{",
    "tnLldpRemoteSystemsData",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "TnLldpRemPortIndexEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Note that this table is same as tnLldpRemTable except that the order of two indices tnLldpRemTimeMark and tnPortPortID are reversed. This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one tnLldpRemEntry is present for each local port and destination MAC address, or it may choose to maintain multiple tnLldpRemEntry rows for the same local port and destination MAC address. 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. tnLldpStatsRemTablesInserts b. tnLldpStatsRemTablesDeletes c. tnLldpStatsRemTablesDrops d. tnLldpStatsRemTablesAgeouts e. tnLldpStatsRxPortAgeouts 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 tnLldpStatsRemTablesLastChangeTime 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 tnLldpStatsRemTablesInserts 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 tnLldpStatsRemTablesAgeouts has changed, then NMS will walk the tnLldpStatsRxPortAgeouts and compare the new values with previously recorded ones. For ports whose tnLldpStatsRxPortAgeouts 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.) tnLldpStatsRemTablesDeletes and tnLldpStatsRemTablesDrops 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.7483)

Vieregge Richard

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.7483.6.1.2.59.4.3.1 tnLldpRemPortIndexEntry99

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.7483.6.1.2.59.4.1 tnLldpRemTable113
1.3.6.1.4.1.7483.6.1.2.59.4.2 tnLldpRemManAddrTable16
1.3.6.1.4.1.7483.6.1.2.59.4.4 tnLldpRemManAddrPortIndexTable14