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.
OID reference
lldpRemTable
1.3.6.1.4.1.171.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 …
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.171.127.1.4 (lldpRemoteSystemsData)
- Node code
- 1
- Node name
- lldpRemTable
- Category
- SNMP management object
- Numeric OID
- 1.3.6.1.4.1.171.127.1.4.1
- URN notation
- urn:oid:1.3.6.1.4.1.171.127.1.4.1
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 171 127 1 4 1}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dlink(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) d-link(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) company(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) my(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dlink(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) d-link(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) company(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) my(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nms(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dlink(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) d-link(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) company(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) my(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nms(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dlink(171) nmslldpMIB(127) lldpObjects(1) lldpRemoteSystemsData(4) lldpRemTable(1)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/171/127/1/4/1
- /ISO/Identified-Organization/6/1/4/1/171/127/1/4/1
- /ISO/3/6/1/4/1/171/127/1/4/1
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/dlink/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/enterprise/d-link/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/enterprise/company/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/enterprise/my/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/enterprise/nms/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/enterprises/dlink/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/enterprises/d-link/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/enterprises/company/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/enterprises/my/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/enterprises/nms/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/ldap-enterprise/dlink/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/ldap-enterprise/d-link/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/ldap-enterprise/company/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/ldap-enterprise/my/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/ldap-enterprise/nms/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/lldpRemTable
- /iso/identified-organization/dod/internet/private/vendor-objects/dlink/nmslldpMIB/lldpObjects/lldpRemoteSystemsData/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.
Published definition
The displayed source records contain one distinct definition. Compare its source records.
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
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Evidence
Source records
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Records for description 1D-Link official switch MIBs
lldpRemTable · currentD-Link official switch MIBs
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
]
}- D-Link official switch MIBs
· Publisher's source file: Source package: Private MIB.zip
Module: NMS-LLDP-MIB
See published definition above
· Download NMS-LLDP-MIB.MIBModule 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:
Show all 6 related files and packages
Same file in Private MIB.zip.
Same file in Private MIB.zip.
Same file in Private MIB.zip.
Same file in Private MIB.zip.
Registration
Registration authorities
First Registration Authority (inferred from ancestor 1.3.6.1.4.1.171)
Direct children (1)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.171.127.1.4.1.1 | lldpRemEntry | 12 | 12 |
Siblings (3)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.171.127.1.4.2 | lldpRemManAddrTable | 1 | 6 | |
| 1.3.6.1.4.1.171.127.1.4.3 | lldpRemUnknownTLVTable | 1 | 3 | |
| 1.3.6.1.4.1.171.127.1.4.4 | lldpRemOrgDefInfoTable | 1 | 5 |