TN-LLDP-MIB
AI MIB Summary
The TN-LLDP-MIB module enables monitoring and management of Link Layer Discovery Protocol (LLDP) neighbor discovery data, including system identification, port descriptions, and TLV (Type-Length-Value) attributes, on Trellix (formerly McAfee) network infrastructure devices. This private MIB extension facilitates the collection of LLDP session states and neighbor topology information for network inventory and connectivity verification.
This is a private version of the LLDP MIB
Main OID:
tnLldpMib.1.3.6.1.4.1.868.2.5.151
189
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
189 total| Object Name |
|---|
tnLldpMibThis is a private version of the LLDP MIB MODULE-IDENTITY .1.3.6.1.4.1.868.2.5.151 |
tnLldpMibObjects OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1 |
tnLldpConfig OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.2 |
tnLldpConfigGlobal OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.2.1 |
tnLldpConfigGlobalReInitDelaySet the LLDP tx reinitialization delay in seconds. Valid range 1-10. When a port is disabled, LLDP is disabled or the switch is rebooted, a LLDP shutdown frame is transmitted to the neighboring units, signaling that the LLDP information isn't valid anymore. Tx reinitialization delay controls the amount of seconds between the shutdown frame and a new LLDP initialization. Note: Must be less than 0.25 times the Tx interval.rw TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.1.1 |
tnLldpConfigGlobalMsgTxHoldSet the LLDP tx hold times . Valid range 2-10. Each LLDP frame contains information about how long time the information in the LLDP frame shall be considered valid. The LLDP information valid period is set to tx hold times multiplied by tx interval seconds.rw TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.1.2 |
tnLldpConfigGlobalMsgTxIntervalSet the LLDP tx interval in seconds. The switch periodically transmits LLDP frames to its neighbors for having the network discovery information up-to-date. The interval between each LLDP frame is determined by the tx Interval value. Valid range 5-32768 seconds.rw TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.1.3 |
tnLldpConfigGlobalTxDelaySet the LLDP tx delay in seconds. Valid range 1-8192. If some configuration is changed (e.g. the IP address) a new LLDP frame is transmitted, but the time between the LLDP frames will always be at least the value of tx delay seconds. Note: tx Delay cannot be larger than 1/4 of the tx interval.rw TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.1.4 |
tnLldpConfigTableThis is a table to configure LLDP configurations for a specific interface. SEQUENCE OF TNLldpConfigEntry .1.3.6.1.4.1.868.2.5.151.1.2.2 |
tnLldpConfigEntryEach interface has a set of control parameters TNLldpConfigEntry .1.3.6.1.4.1.868.2.5.151.1.2.2.1 |
tnLldpConfigIfIndexLogical interface number index. TNInterfaceIndex (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.2.1.1 |
tnLldpConfigAdminStateSets the LLDP admin state for the interface.rw TNlldpAdminState .1.3.6.1.4.1.868.2.5.151.1.2.2.1.3 |
tnLldpConfigCdpAwareEnables/disables CDP awareness for the interface. CDP is Cisco's equivalent to LLDP. The CDP operation is restricted to decoding incoming CDP frames (The switch doesn't transmit CDP frames). CDP frames are only decoded if LLDP on the port is enabled. Only CDP TLVs that can be mapped to a corresponding field in the LLDP neighbors' table are decoded. All other TLVs are discarded (Unrecognized CDP TLVs and discarded CDP frames are not shown in the LLDP statistics.). CDP TLVs are mapped onto LLDP neighbors' table as shown below. CDP TLV 'Device ID' is mapped to the LLDP 'Chassis ID' field. CDP TLV 'Address' is mapped to the LLDP 'Management Address' field. The CDP address TLV can contain multiple addresses, but only the first address is shown in the LLDP neighbors table. CDP TLV 'Port ID' is mapped to the LLDP 'Port ID' field. CDP TLV 'Version and Platform' is mapped to the LLDP 'System Description' field. Both the CDP and LLDP support 'system capabilities', but the CDP capabilities cover capabilities that are not part of the LLDP. These capabilities are shown as 'others' in the LLDP neighbors' table. If all ports have CDP awareness disabled the switch forwards CDP frames received from neighbor devices. If at least one port has CDP awareness enabled all CDP frames are terminated by the switch. Note: When CDP awareness on a port is disabled the CDP information isn't removed immediately, but gets removed when the hold time is exceeded.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.151.1.2.2.1.4 |
tnLldpConfigOptionalTlvsEnables/Disables the LLDP optional TLVs. Bit mask, where setting the bit to 1 means enable transmission of the corresponding TLV. Bit 0 represents Port Description TLV. Bit 1 represents System Name TLV. Bit 2 represents System Description. Bit 3 represents System Capabilities TLV. Bit 4 represents Management Address TLV.rw TNUnsigned8 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.2.1.5 |
tnLldpConfigMed OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.2.3 |
tnLldpConfigMedTableThis is a table to configure LLDP MEDIA configurations for a specific interface. SEQUENCE OF TNLldpConfigMedEntry .1.3.6.1.4.1.868.2.5.151.1.2.3.1 |
tnLldpConfigMedEntryEach interface has a set of control parameters TNLldpConfigMedEntry .1.3.6.1.4.1.868.2.5.151.1.2.3.1.1 |
tnLldpConfigMedIfIndexLogical interface number index. TNInterfaceIndex (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.3.1.1.1 |
tnLldpConfigMedOptionalTlvsEnables/Disables the LLDP optional TLVs. Bit mask, where setting the bit to 1 means enable transmission of the corresponding optional TLV. Bit 0 represents the capabilities TLV. Bit 1 represents the network Policy TLV. Bit 2 represents the location TLV. Bit 3 represents the PoE TLV.rw TNUnsigned8 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.3.1.1.3 |
tnLldpConfigMedDeviceTypeSetting device type to configure the mode the device shall operate as.rw TNlldpmedDeviceType .1.3.6.1.4.1.868.2.5.151.1.2.3.1.1.4 |
tnLldpConfigMedPolicyTableThis is a table to configure LLDP MED Policies for the device. SEQUENCE OF TNLldpConfigMedPolicyEntry .1.3.6.1.4.1.868.2.5.151.1.2.3.2 |
tnLldpConfigMedPolicyEntryNetwork Policy Discovery enables the efficient discovery and diagnosis of mismatch issues with the VLAN configuration, along with the associated Layer 2 and Layer 3 attributes, which apply for a set of specific protocol applications on that port. Improper network policy configurations are a very significant issue in VoIP environments that frequently result in voice quality degradation or loss of service. Policies are only intended for use with applications that have specific 'real-time' network policy requirements, such as interactive voice and/or video services. TNLldpConfigMedPolicyEntry .1.3.6.1.4.1.868.2.5.151.1.2.3.2.1 |
tnLldpConfigMedPolicyLldpmedPolicyPolicy index. Integer32 .1.3.6.1.4.1.868.2.5.151.1.2.3.2.1.1 |
tnLldpConfigMedPolicyApplicationTypeThe LLDP policy application type.rw TNlldpmedRemoteNetworkPolicyApplicationType .1.3.6.1.4.1.868.2.5.151.1.2.3.2.1.3 |
tnLldpConfigMedPolicyTaggedThe LLDP policy tagged flag. Defines if LLDP policy uses tagged VLAN.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.151.1.2.3.2.1.4 |
tnLldpConfigMedPolicyVlanIdThe LLDP policy VLAN ID. Only valid when policy 'Tagged' is TRUErw TNUnsigned16 .1.3.6.1.4.1.868.2.5.151.1.2.3.2.1.5 |
tnLldpConfigMedPolicyL2PriorityThe LLDP policy L2 priority.rw TNUnsigned8 .1.3.6.1.4.1.868.2.5.151.1.2.3.2.1.6 |
tnLldpConfigMedPolicyDscpThe LLDP policy DSCP.rw TNUnsigned8 .1.3.6.1.4.1.868.2.5.151.1.2.3.2.1.7 |
tnLldpConfigMedPolicyActionActionrw TNRowEditorState (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.3.2.1.100 |
tnLldpConfigMedPolicyListTableEach interface can be mapped to multiple policies. Set to TRUE in order to enable the corresponding policy to be transmitted at the interface. It is a requirement that the policy is defined. SEQUENCE OF TNLldpConfigMedPolicyListEntry .1.3.6.1.4.1.868.2.5.151.1.2.3.3 |
tnLldpConfigMedPolicyListEntryEach location information has a control parameter TNLldpConfigMedPolicyListEntry .1.3.6.1.4.1.868.2.5.151.1.2.3.3.1 |
tnLldpConfigMedPolicyListIfIndexLogical interface number index. TNInterfaceIndex (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.3.3.1.1 |
tnLldpConfigMedPolicyListLldpmedPolicyPolicy index. Integer32 .1.3.6.1.4.1.868.2.5.151.1.2.3.3.1.3 |
tnLldpConfigMedPolicyListLldpmedPoliciesListSet to TRUE assign the corresponding policy index to the interface.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.151.1.2.3.3.1.4 |
tnLldpConfigMedGlobal OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.2.3.4 |
tnLldpConfigMedGlobalFastRepeatCountNumber of times to repeat LLDP frame transmission at fast start Rapid startup and Emergency Call Service Location Identification Discovery of endpoints is a critically important aspect of VoIP systems in general. In addition, it is best to advertise only those pieces of information which are specifically relevant to particular endpoint types (for example only advertise the voice network policy to permitted voice-capable devices), both in order to conserve the limited LLDPU space and to reduce security and system integrity issues that can come with inappropriate knowledge of the network policy. With this in mind LLDP-MED defines an LLDP-MED Fast Start interaction between the protocol and the application layers on top of the protocol, in order to achieve these related properties. Initially, a Network Connectivity Device will only transmit LLDP TLVs in an LLDPDU. Only after an LLDP-MED Endpoint Device is detected, will an LLDP-MED capable Network Connectivity Device start to advertise LLDP-MED TLVs in outgoing LLDPDUs on the associated port. The LLDP-MED application will temporarily speed up the transmission of the LLDPDU to start within a second, when a new LLDP-MED neighbor has been detected in order share LLDP-MED information as fast as possible to new neighbors. Because there is a risk of an LLDP frame being lost during transmission between neighbors, it is recommended to repeat the fast start transmission multiple times to increase the possibility of the neighbors receiving the LLDP frame. With fast start repeat count it is possible to specify the number of times the fast start transmission would be repeated. The recommended value is 4 times, given that 4 LLDP frames with a 1 second interval will be transmitted, when an LLDP frame with new information is received. It should be noted that LLDP-MED and the LLDP-MED Fast Start mechanism is only intended to run on links between LLDP-MED Network Connectivity Devices and Endpoint Devices, and as such does not apply to links between LAN infrastructure elements, including Network Connectivity Devices, or other types of links.rw TNUnsigned8 .1.3.6.1.4.1.868.2.5.151.1.2.3.4.1 |
tnLldpConfigMedGlobalLatitudeLatitude degrees in 2s-complement as specified in RFC 3825. Positive numbers are north of the equator and negative numbers are south of the equator.rw TNInteger64 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.3.4.2 |
tnLldpConfigMedGlobalLongitudeLongitude degrees in 2s-complement as specified in RFC 3825. Positive values are East of the prime meridian and negative numbers are West of the prime meridian.rw TNInteger64 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.3.4.3 |
tnLldpConfigMedGlobalAltitudeTypeSetting altitude type Possible to select between two altitude types (floors or meters). Meters are representing meters of altitude defined by the vertical datum specified. Floors are representing altitude in a form more relevant in buildings which have different floor-to-floor dimensions. An altitude = 0.0 is meaningful even outside a building, and represents ground level at the given latitude and longitude. Inside a building, 0.0 represents the floor level associated with ground level at the main entrance.rw TNlldpmedAltitudeType .1.3.6.1.4.1.868.2.5.151.1.2.3.4.4 |
tnLldpConfigMedGlobalAltitudeAltitude value in 2s-complement as specified in RFC 3825rw Integer32 .1.3.6.1.4.1.868.2.5.151.1.2.3.4.5 |
tnLldpConfigMedGlobalElinAddrEmergency Call Service ELIN identifier data format is defined to carry the ELIN identifier as used during emergency call setup to a traditional CAMA or ISDN trunk-based PSAP. This format consists of a numerical digit string, corresponding to the ELIN to be used for emergency calling. Maximum number of octets are 25.rw TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.2.3.4.6 |
tnLldpConfigMedGlobalDatumSetting datum to configure the datum (geodetic system) to use. The Map Datum is used for the coordinates given in these options: WGS84: (Geographical 3D) - World Geodesic System 1984, CRS Code 4327, Prime Meridian Name: Greenwich. NAD83/NAVD88: North American Datum 1983, CRS Code 4269, Prime Meridian Name: Greenwich;The associated vertical datum is the North American Vertical Datum of 1988 (NAVD88).This datum pair is to be used when referencing locations on land, not near tidal water(which would use Datum = NAD83/MLLW). NAD83/MLLW: North American Datum 1983, CRS Code 4269, Prime Meridian Name: Greenwich; The associated vertical datum is Mean Lower Low Water (MLLW). This datum pair is to be used when referencing locations on water/sea/ocean.rw TNlldpmedDatumType .1.3.6.1.4.1.868.2.5.151.1.2.3.4.7 |
tnLldpConfigMedGlobalCountryCodeThe two-letter ISO 3166 country code in capital ASCII letters - Example: DK, DE or US.rw TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.2.3.4.8 |
tnLldpConfigMedLocationInformationTableThe civic address location information. Each civic address can contain up to 250 characters, but the total amount of characters for the combined civic address locations must not exceed 250 bytes. Note: If an civic address location is non-empty it uses the amount of characters plus addition two characters. This is described in TIA1057, Section 10.2.4.3.2. SEQUENCE OF TNLldpConfigMedLocationInformationEntry .1.3.6.1.4.1.868.2.5.151.1.2.3.5 |
tnLldpConfigMedLocationInformationEntryEach civic address type as defined in TIA1057, Section 3.4 in Annex B TNLldpConfigMedLocationInformationEntry .1.3.6.1.4.1.868.2.5.151.1.2.3.5.1 |
tnLldpConfigMedLocationInformationLldpmedIndexCivic address type. 1 - State/National subdivisions 2 - County, parish, gun (JP), district (IN) 3 - City, township 4 - City division, borough, city district, ward, chou (JP) 5 - Neighborhood, block 6 - Street 16 - Leading street direction 17 - Trailing street direction 18 - Street suffix 19 - House number 20 - House number suffix 21 - Landmark or vanity address 22 - Additional location information 23 - Name 24 - Postal/zip code 25 - Building 26 - Unit 27 - Floor 28 - Room 29 - Place type 30 - Postal 31 - Post office 32 - Additional code TNlldpmedCivicAddressType .1.3.6.1.4.1.868.2.5.151.1.2.3.5.1.2 |
tnLldpConfigMedLocationInformationCivicAddressCivic addressrw TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.2.3.5.1.3 |
tnLldpConfigMedPolicyRowEditor OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.2.3.6 |
tnLldpConfigMedPolicyRowEditorLldpmedPolicyPolicy index.rw Integer32 .1.3.6.1.4.1.868.2.5.151.1.2.3.6.1 |
tnLldpConfigMedPolicyRowEditorApplicationTypeThe LLDP policy application type.rw TNlldpmedRemoteNetworkPolicyApplicationType .1.3.6.1.4.1.868.2.5.151.1.2.3.6.3 |
tnLldpConfigMedPolicyRowEditorTaggedThe LLDP policy tagged flag. Defines if LLDP policy uses tagged VLAN.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.151.1.2.3.6.4 |
tnLldpConfigMedPolicyRowEditorVlanIdThe LLDP policy VLAN ID. Only valid when policy 'Tagged' is TRUErw TNUnsigned16 .1.3.6.1.4.1.868.2.5.151.1.2.3.6.5 |
tnLldpConfigMedPolicyRowEditorL2PriorityThe LLDP policy L2 priority.rw TNUnsigned8 .1.3.6.1.4.1.868.2.5.151.1.2.3.6.6 |
tnLldpConfigMedPolicyRowEditorDscpThe LLDP policy DSCP.rw TNUnsigned8 .1.3.6.1.4.1.868.2.5.151.1.2.3.6.7 |
tnLldpConfigMedPolicyRowEditorActionActionrw TNRowEditorState (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.2.3.6.100 |
tnLldpStatus OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.3 |
tnLldpStatusStatistics OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.3.1 |
tnLldpStatusStatisticsGlobalCounters OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.3.1.1 |
tnLldpStatusStatisticsGlobalCountersTableInsertsShows the number of new entries added since switch reboot.ro Unsigned32 .1.3.6.1.4.1.868.2.5.151.1.3.1.1.1 |
tnLldpStatusStatisticsGlobalCountersTableDeletesShows the number of new entries deleted since switch reboot.ro Unsigned32 .1.3.6.1.4.1.868.2.5.151.1.3.1.1.2 |
tnLldpStatusStatisticsGlobalCountersTableDropsShows the number of LLDP frames dropped due to the entry table being full.ro Unsigned32 .1.3.6.1.4.1.868.2.5.151.1.3.1.1.3 |
tnLldpStatusStatisticsGlobalCountersTableAgeOutsShows the number of entries deleted due to Time-To-Live expiring.ro Unsigned32 .1.3.6.1.4.1.868.2.5.151.1.3.1.1.4 |
tnLldpStatusStatisticsGlobalCountersLastChangeTimeShows the time when the last entry was last deleted or added. It also shows the time elapsed since the last change was detected.ro TNUnsigned64 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.1.1.5 |
tnLldpStatusStatisticsTableThis table represents the LLDP interface counters SEQUENCE OF TNLldpStatusStatisticsEntry .1.3.6.1.4.1.868.2.5.151.1.3.1.2 |
tnLldpStatusStatisticsEntryEach port interface has a set of statistics counters TNLldpStatusStatisticsEntry .1.3.6.1.4.1.868.2.5.151.1.3.1.2.1 |
tnLldpStatusStatisticsIfIndexLogical interface number index. TNInterfaceIndex (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.1.2.1.1 |
tnLldpStatusStatisticsTxTotalShows the number of LLDP frames transmitted.ro Unsigned32 .1.3.6.1.4.1.868.2.5.151.1.3.1.2.1.2 |
tnLldpStatusStatisticsRxTotalShows the number of LLDP frames received.ro Unsigned32 .1.3.6.1.4.1.868.2.5.151.1.3.1.2.1.3 |
tnLldpStatusStatisticsRxErrorShows the number of received LLDP frames containing some kind of error.ro Unsigned32 .1.3.6.1.4.1.868.2.5.151.1.3.1.2.1.4 |
tnLldpStatusStatisticsRxDiscardedShow the number of LLDP frames discarded. If a LLDP frame is received at an interface, and the switch's internal table has run full, the LLDP frame is counted and discarded. This situation is known as 'Too Many Neighbors' in the LLDP standard. LLDP frames require a new entry in the table when the Chassis ID or Remote Port ID is not already contained within the table. Entries are removed from the table when a given interface's link is down, an LLDP shutdown frame is received, or when the entry ages out.ro Unsigned32 .1.3.6.1.4.1.868.2.5.151.1.3.1.2.1.5 |
tnLldpStatusStatisticsTLVsDiscardedShows the number of TLVs discarded. Each LLDP frame can contain multiple pieces of information, known as TLVs (TLV is short for 'Type Length Value'). If a TLV is malformed, it is counted and discarded.ro Unsigned32 .1.3.6.1.4.1.868.2.5.151.1.3.1.2.1.6 |
tnLldpStatusStatisticsTLVsUnrecognizedShows the number of well-formed TLVs, but with an unknown type value.ro Unsigned32 .1.3.6.1.4.1.868.2.5.151.1.3.1.2.1.7 |
tnLldpStatusStatisticsTLVsOrgDiscardedShows the number of well-formed TLVs, but with an organizationally TLV which is not supported.ro Unsigned32 .1.3.6.1.4.1.868.2.5.151.1.3.1.2.1.8 |
tnLldpStatusStatisticsAgeOutsShow the number of age-outs. Each frame contains information about how long time the LLDP information is valid (age-out time). If no new LLDP frame is received within the age out time, the information is removed, and the counter is incremented.ro Unsigned32 .1.3.6.1.4.1.868.2.5.151.1.3.1.2.1.9 |
tnLldpStatusNeighborsInformationTableThis is a table to show the LLDP neighbors information for a specific interface. SEQUENCE OF TNLldpStatusNeighborsInformationEntry .1.3.6.1.4.1.868.2.5.151.1.3.2 |
tnLldpStatusNeighborsInformationEntryEach interface has a set of neighbors information TNLldpStatusNeighborsInformationEntry .1.3.6.1.4.1.868.2.5.151.1.3.2.1 |
tnLldpStatusNeighborsInformationIfIndexLogical interface number index. TNInterfaceIndex (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.2.1.1 |
tnLldpStatusNeighborsInformationLldpmedIndexNeighbor information table entry index. Integer32 .1.3.6.1.4.1.868.2.5.151.1.3.2.1.2 |
tnLldpStatusNeighborsInformationChassisIdShows the LLDP neighbor's chassis Id.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.2.1.4 |
tnLldpStatusNeighborsInformationPortIdShows the LLDP neighbor's port id.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.2.1.5 |
tnLldpStatusNeighborsInformationPortDescriptionShows the LLDP neighbor's port description.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.2.1.6 |
tnLldpStatusNeighborsInformationSystemNameShows the LLDP neighbor's system name.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.2.1.7 |
tnLldpStatusNeighborsInformationSystemDescriptionShows the LLDP neighbor's system description.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.2.1.8 |
tnLldpStatusNeighborsInformationSystemCapabilitiesShows the LLDP neighbor's system capabilities as bit mask. If the bit is set, it means that the functionality is supported by the neighbor system. Bit 0 represents Other. Bit 1 represents Repeater. Bit 2 represents Bridge. Bit 3 represents WLAN Access Point. Bit 4 represents Router. Bit 5 represents Telephone. Bit 6 represents DOCSIS cable device. Bit 7 represents Station Only. Bit 8 represents Reserved.ro TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.2.1.9 |
tnLldpStatusNeighborsInformationSystemCapabilitiesEnableShows the LLDP neighbor's system capabilities which is enabled. If the bit is set, it means that the functionality is currently enabled at the neighbor system. Bit 0 represents Other. Bit 1 represents Repeater. Bit 2 represents Bridge. Bit 3 represents WLAN Access Point. Bit 4 represents Router. Bit 5 represents Telephone. Bit 6 represents DOCSIS cable device. Bit 7 represents Station Only. Bit 8 represents Reserved.ro TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.2.1.10 |
tnLldpStatusNeighborsMgmtInformationTableThis is a table to show the LLDP neighbors information for a specific interface. SEQUENCE OF TNLldpStatusNeighborsMgmtInformationEntry .1.3.6.1.4.1.868.2.5.151.1.3.3 |
tnLldpStatusNeighborsMgmtInformationEntryEach interface has a set of neighbors information TNLldpStatusNeighborsMgmtInformationEntry .1.3.6.1.4.1.868.2.5.151.1.3.3.1 |
tnLldpStatusNeighborsMgmtInformationIfIndexLogical interface number index. TNInterfaceIndex (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.3.1.1 |
tnLldpStatusNeighborsMgmtInformationLldpmedIndexNeighbor information table entry index. Integer32 .1.3.6.1.4.1.868.2.5.151.1.3.3.1.2 |
tnLldpStatusNeighborsMgmtInformationLldpManagementNeighbor management information table entry index. Integer32 .1.3.6.1.4.1.868.2.5.151.1.3.3.1.4 |
tnLldpStatusNeighborsMgmtInformationSystemMgmAddressSubtypeLLDP neighbor's management address subtype , section 9.5.9.3 IEEE802.1AB-2005.ro TNUnsigned8 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.3.1.5 |
tnLldpStatusNeighborsMgmtInformationSystemMgmtAddressLLDP neighbor's management address string, section 9.5.9.4 IEEE802.1AB-2005.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.3.1.6 |
tnLldpStatusNeighborsMgmtInformationSystemMgmtInterfaceSubtypeInterface numbering subtype, section 9.5.9.5 IEEE802.1AB-2005.ro Integer32 .1.3.6.1.4.1.868.2.5.151.1.3.3.1.7 |
tnLldpStatusNeighborsMgmtInformationSystemMgmtInterfaceInterface number, section 9.5.9.6 IEEE802.1AB-2005.ro Integer32 .1.3.6.1.4.1.868.2.5.151.1.3.3.1.8 |
tnLldpStatusNeighborsMgmtInformationSystemMgmtOidObject identifier, section 9.5.9.8 IEEE802.1AB-2005.ro OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.3.3.1.9 |
tnLldpStatusMed OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.3.4 |
tnLldpStatusMedRemoteDeviceInfoTableThis is a table to show the LLDP neighbors information for a specific interface. SEQUENCE OF TNLldpStatusMedRemoteDeviceInfoEntry .1.3.6.1.4.1.868.2.5.151.1.3.4.1 |
tnLldpStatusMedRemoteDeviceInfoEntryEach interface has a set of neighbors information TNLldpStatusMedRemoteDeviceInfoEntry .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1 |
tnLldpStatusMedRemoteDeviceInfoIfIndexLogical interface number index. TNInterfaceIndex (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.1 |
tnLldpStatusMedRemoteDeviceInfoLldpmedIndexNeighbor information table entry index. Integer32 .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.2 |
tnLldpStatusMedRemoteDeviceInfoCapabilitiesLLDP neighbor's capabilities bit mask. Bit 0 represents LLDP-MED capabilities. Bit 1 represents Network Policy. Bit 2 represents Location Identification. Bit 3 represents Extended Power via MDI - PSE. Bit 4 represents Extended Power via MDI - PD Bit 5 represents Inventoryro TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.4 |
tnLldpStatusMedRemoteDeviceInfoCapabilitiesEnabledLLDP neighbor's capabilities bit mask for the capabilities which are currently enabled. Bit 0 represents LLDP-MED capabilities. Bit 1 represents Network Policy. Bit 2 represents Location Identification. Bit 3 represents Extended Power via MDI - PSE. Bit 4 represents Extended Power via MDI - PD Bit 5 represents Inventoryro TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.5 |
tnLldpStatusMedRemoteDeviceInfoLatitudeLatitude degrees in 2s-complement as specified in RFC 3825. Positive numbers are north of the equator and negative numbers are south of the equator.ro TNInteger64 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.6 |
tnLldpStatusMedRemoteDeviceInfoLongitudeLongitude degrees in 2s-complement as specified in RFC 3825. Positive values are East of the prime meridian and negative numbers are West of the prime meridian.ro TNInteger64 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.7 |
tnLldpStatusMedRemoteDeviceInfoAltitudeTypeAltitude type as either floors or meters. Meters are representing meters of altitude defined by the vertical datum specified. Floors are representing altitude in a form more relevant in buildings which have different floor-to-floor dimensions. An altitude = 0.0 is meaningful even outside a building, and represents ground level at the given latitude and longitude. Inside a building, 0.0 represents the floor level associated with ground level at the main entrance.ro TNlldpmedAltitudeType .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.8 |
tnLldpStatusMedRemoteDeviceInfoAltitudeAltitude value in 2s-complement as specified in RFC 3825ro Integer32 .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.9 |
tnLldpStatusMedRemoteDeviceInfoDatumDatum (geodetic system) . The Map Datum is used for the coordinates given in these options: WGS84: (Geographical 3D) - World Geodesic System 1984, CRS Code 4327, Prime Meridian Name: Greenwich. NAD83/NAVD88: North American Datum 1983, CRS Code 4269, Prime Meridian Name: Greenwich; The associated vertical datum is the North American Vertical Datum of 1988 (NAVD88). This datum pair is to be used when referencing locations on land, not near tidal water(which would use Datum = NAD83/MLLW). NAD83/MLLW: North American Datum 1983, CRS Code 4269, Prime Meridian Name: Greenwich; The associated vertical datum is Mean Lower Low Water (MLLW). This datum pair is to be used when referencing locations on water/sea/ocean.ro TNlldpmedDatumType .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.10 |
tnLldpStatusMedRemoteDeviceInfoElinaddrEmergency Call Service ELIN identifier data format is defined to carry the ELIN identifier as used during emergency call setup to a traditional CAMA or ISDN trunk-based PSAP. This format consists of a numerical digit string, corresponding to the ELIN to be used for emergency calling. Maximum number of octets are 25.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.11 |
tnLldpStatusMedRemoteDeviceInfoDeviceTypeShows the LLDP neighbor's device type.ro TNlldpmedRemoteDeviceType .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.12 |
tnLldpStatusMedRemoteDeviceInfoHwRevShows the LLDP neighbor's hardware revision.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.13 |
tnLldpStatusMedRemoteDeviceInfoFwRevShows the LLDP neighbor's firmware revision.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.14 |
tnLldpStatusMedRemoteDeviceInfoSwRevShows the LLDP neighbor's software revision.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.15 |
tnLldpStatusMedRemoteDeviceInfoSerialNoShows the LLDP neighbor's serial number.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.16 |
tnLldpStatusMedRemoteDeviceInfoManufacturerNameShows the LLDP neighbor's manufacturer name.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.17 |
tnLldpStatusMedRemoteDeviceInfoModelNameShows the LLDP neighbor's model name.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.18 |
tnLldpStatusMedRemoteDeviceInfoAssetIdShows the LLDP neighbor's asset id.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.19 |
tnLldpStatusMedRemoteDeviceInfoEeeRxTwSysShows the LLDP neighbor's Receive tw_sys_rx . Tw_sys_rx is defined as the time (expressed in microseconds) that the transmitting link partner will wait before it starts transmitting data after leaving the Low Power Idle (LPI) mode. Section 79.3.5.2, IEEE802.3az.ro TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.20 |
tnLldpStatusMedRemoteDeviceInfoEeeTxTwSysShows the LLDP neighbor's Transmit Tw_sys_tx . Tw_sys_tx is defined as the time (expressed in microseconds) that the receiving link partner is requesting the transmitting link partner to wait before starting the transmission data following the Low Power Idle (LPI) mode. Section 79.3.5.1, IEEE802.3az.ro TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.21 |
tnLldpStatusMedRemoteDeviceInfoEeeFbTwSysShows the LLDP neighbor's Fallback tw_sys_tx. A receiving link partner may inform the transmitter of an alternate desired Tw_sys_tx. Since a receiving link partner is likely to have discrete levels for savings, this provides the transmitter with additional information that it may use for a more efficient allocation. Section 79.3.5.3, IEEE802.3az.ro TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.22 |
tnLldpStatusMedRemoteDeviceInfoEeeTxTwSysEchoShows the LLDP neighbor's echo transmit Tw. The respective echo values shall be defined as the local link partners reflection (echo) of the remote link partners respective values. When a local link partner receives its echoed values from the remote link partner it can determine whether or not the remote link partner has received, registered, and processed its most recent values. Section 79.3.5.4, IEEE802.3az.ro TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.23 |
tnLldpStatusMedRemoteDeviceInfoEeeRxTwSysEchoShows the LLDP neighbor's echo receive Tw. The respective echo values shall be defined as the local link partners reflection (echo) of the remote link partners respective values. When a local link partner receives its echoed values from the remote link partner it can determine whether or not the remote link partner has received, registered, and processed its most recent values. Section 79.3.5.4, IEEE802.3az.ro TNUnsigned16 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.1.1.24 |
tnLldpStatusMedRemoteDeviceLocInfoTableThis is a table to show the LLDP-MED remote device (neighbor) civic location information for a specific interface. SEQUENCE OF TNLldpStatusMedRemoteDeviceLocInfoEntry .1.3.6.1.4.1.868.2.5.151.1.3.4.2 |
tnLldpStatusMedRemoteDeviceLocInfoEntryEach interface has a set of neighbors information TNLldpStatusMedRemoteDeviceLocInfoEntry .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1 |
tnLldpStatusMedRemoteDeviceLocInfoIfIndexLogical interface number index. TNInterfaceIndex (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.1 |
tnLldpStatusMedRemoteDeviceLocInfoLldpmedIndexNeighbor information table entry index. Integer32 .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.2 |
tnLldpStatusMedRemoteDeviceLocInfoStateNational subdivisionro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.5 |
tnLldpStatusMedRemoteDeviceLocInfoCountyCountyro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.6 |
tnLldpStatusMedRemoteDeviceLocInfoCityCityro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.7 |
tnLldpStatusMedRemoteDeviceLocInfoDistrictCity districtro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.8 |
tnLldpStatusMedRemoteDeviceLocInfoBlockBlock (Neighborhood)ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.9 |
tnLldpStatusMedRemoteDeviceLocInfoStreetStreetro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.10 |
tnLldpStatusMedRemoteDeviceLocInfoLeadingStreetDirectionStreet Directionro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.11 |
tnLldpStatusMedRemoteDeviceLocInfoTrailingStreetSuffixTrailing Street Suffixro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.12 |
tnLldpStatusMedRemoteDeviceLocInfoStreetSuffixStreet Suffixro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.13 |
tnLldpStatusMedRemoteDeviceLocInfoHouseNoHouse No.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.14 |
tnLldpStatusMedRemoteDeviceLocInfoHouseNoSuffixHouse No. Suffixro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.15 |
tnLldpStatusMedRemoteDeviceLocInfoLandmarkLandmarkro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.16 |
tnLldpStatusMedRemoteDeviceLocInfoAdditionalInfoAdditional Location Inforo TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.17 |
tnLldpStatusMedRemoteDeviceLocInfoNameNamero TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.18 |
tnLldpStatusMedRemoteDeviceLocInfoZipCodeZip codero TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.19 |
tnLldpStatusMedRemoteDeviceLocInfoBuildingBuildingro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.20 |
tnLldpStatusMedRemoteDeviceLocInfoApartmentApartment/unitro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.21 |
tnLldpStatusMedRemoteDeviceLocInfoFloorFloorro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.22 |
tnLldpStatusMedRemoteDeviceLocInfoRoomNumberRoom Numberro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.23 |
tnLldpStatusMedRemoteDeviceLocInfoPlaceTypePlace typero TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.24 |
tnLldpStatusMedRemoteDeviceLocInfoPostalCommunityNamePostal Community Namero TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.25 |
tnLldpStatusMedRemoteDeviceLocInfoPoBoxPost Office Boxro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.26 |
tnLldpStatusMedRemoteDeviceLocInfoAdditionalCodeAddination Codero TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.27 |
tnLldpStatusMedRemoteDeviceLocInfoCountryCodeThe two-letter ISO 3166 country code in capital ASCII letters - Example: DK, DE or US.ro TNDisplayString .1.3.6.1.4.1.868.2.5.151.1.3.4.2.1.28 |
tnLldpStatusMedRemoteDeviceNetworkPolicyInfoTableThis is a table to show the LLDP-MED remote device (neighbor) network policies information for a specific interface. SEQUENCE OF TNLldpStatusMedRemoteDeviceNetworkPolicyInfoEntry .1.3.6.1.4.1.868.2.5.151.1.3.4.3 |
tnLldpStatusMedRemoteDeviceNetworkPolicyInfoEntryEach interface has a set of neighbors information TNLldpStatusMedRemoteDeviceNetworkPolicyInfoEntry .1.3.6.1.4.1.868.2.5.151.1.3.4.3.1 |
tnLldpStatusMedRemoteDeviceNetworkPolicyInfoIfIndexLogical interface number index. TNInterfaceIndex (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.3.1.1 |
tnLldpStatusMedRemoteDeviceNetworkPolicyInfoLldpmedIndexNeighbor information table entry index. Integer32 .1.3.6.1.4.1.868.2.5.151.1.3.4.3.1.2 |
tnLldpStatusMedRemoteDeviceNetworkPolicyInfoLldpmedPolicyPolicy index. Integer32 .1.3.6.1.4.1.868.2.5.151.1.3.4.3.1.3 |
tnLldpStatusMedRemoteDeviceNetworkPolicyInfoApplicationTypeThe LLDP policy application type.ro TNlldpmedRemoteNetworkPolicyApplicationType .1.3.6.1.4.1.868.2.5.151.1.3.4.3.1.5 |
tnLldpStatusMedRemoteDeviceNetworkPolicyInfoUnknownPolicyPolicy indicates that an Endpoint Device wants to explicitly advertise that the policy is required by the device. Can be either Defined or Unknown Unknown: The network policy for the specified application type is currently unknown. Defined: The network policy is defined (known).ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.3.1.6 |
tnLldpStatusMedRemoteDeviceNetworkPolicyInfoTaggedDefines if LLDP policy uses tagged VLAN.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.151.1.3.4.3.1.7 |
tnLldpStatusMedRemoteDeviceNetworkPolicyInfoVlanIdThe policy VLAN ID. Only valid when policy 'Tagged' is TRUEro TNUnsigned16 .1.3.6.1.4.1.868.2.5.151.1.3.4.3.1.8 |
tnLldpStatusMedRemoteDeviceNetworkPolicyInfoL2PriorityShows the LLDP neighbor's policy L2 priority.ro TNUnsigned8 .1.3.6.1.4.1.868.2.5.151.1.3.4.3.1.9 |
tnLldpStatusMedRemoteDeviceNetworkPolicyInfoDscpLLDP policy DSCP.ro TNUnsigned8 .1.3.6.1.4.1.868.2.5.151.1.3.4.3.1.10 |
tnLldpControl OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.4 |
tnLldpControlStatisticsClear OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.4.1 |
tnLldpControlStatisticsClearTableThis is a table to clear LLDP statistics for a specific interface. SEQUENCE OF TNLldpControlStatisticsClearEntry .1.3.6.1.4.1.868.2.5.151.1.4.1.1 |
tnLldpControlStatisticsClearEntryEach interface has a set of statistics counters TNLldpControlStatisticsClearEntry .1.3.6.1.4.1.868.2.5.151.1.4.1.1.1 |
tnLldpControlStatisticsClearIfIndexLogical interface number index. TNInterfaceIndex (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.4.1.1.1.1 |
tnLldpControlStatisticsClearStatisticsClearSet to TRUE to clear the LLDP statistics of an interface.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.868.2.5.151.1.4.1.1.1.2 |
tnLldpControlStatisticsClearGlobal OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.1.4.1.2 |
tnLldpControlStatisticsClearGlobalClearClear LLDP global counters.rw TNUnsigned8 (TN-TC) .1.3.6.1.4.1.868.2.5.151.1.4.1.2.1 |
tnLldpMibConformance OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.2 |
tnLldpMibCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.2.1 |
tnLldpMibComplianceThe compliance statement for the implementation. Unknown .1.3.6.1.4.1.868.2.5.151.2.1.1 |
tnLldpMibGroups OBJECT IDENTIFIER .1.3.6.1.4.1.868.2.5.151.2.2 |
tnLldpConfigGlobalInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.1 |
tnLldpConfigInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.2 |
tnLldpConfigMedInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.3 |
tnLldpConfigMedPolicyInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.4 |
tnLldpConfigMedPolicyListInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.5 |
tnLldpConfigMedGlobalInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.6 |
tnLldpConfigMedLocationInformationInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.7 |
tnLldpConfigMedPolicyRowEditorInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.8 |
tnLldpStatusStatisticsGlobalCountersInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.9 |
tnLldpStatusStatisticsTableInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.10 |
tnLldpStatusNeighborsInformationInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.11 |
tnLldpStatusNeighborsMgmtInformationInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.12 |
tnLldpStatusMedRemoteDeviceInfoInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.13 |
tnLldpStatusMedRemoteDeviceLocInfoInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.14 |
tnLldpStatusMedRemoteDeviceNetworkPolicyInfoInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.15 |
tnLldpControlStatisticsClearTableInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.16 |
tnLldpControlStatisticsClearGlobalInfoGroupA collection of objects suitable for bulk operations. Unknown .1.3.6.1.4.1.868.2.5.151.2.2.17 |