CIE1000-LLDP-MIB: View SNMP OID List / Download MIB

This is a private version of the LLDP MIB

Set 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.

Set 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.

Set 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.

Set 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.

This is a table to configure LLDP configurations for a specific interface.

Each interface has a set of control parameters

Logical interface number index.

Sets the LLDP admin state for the interface.

Enables/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.

Enables/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.

Enable/disable of SNMP Trap notification.

This is a table to configure LLDP MEDIA configurations for a specific interface.

Each interface has a set of control parameters

Logical interface number index.

Enables/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.

Setting device type to configure the mode the device shall operate as.

This is a table to configure LLDP MED Policies for the device.

Network 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.

Policy index.

The LLDP policy application type.

The LLDP policy tagged flag. Defines if LLDP policy uses tagged VLAN.

The LLDP policy VLAN ID. Only valid when policy 'Tagged' is TRUE

The LLDP policy L2 priority.

The LLDP policy DSCP.

Action

Each 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.

Each location information has a control parameter

Logical interface number index.

Policy index.

Set to TRUE assign the corresponding policy index to the interface.

Number 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.

Latitude degrees in 2s-complement as specified in RFC 3825. Positive numbers are north of the equator and negative numbers are south of the equator.

Longitude 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.

Setting 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.

Altitude value in 2s-complement as specified in RFC 3825

Emergency 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.

Setting 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.

The two-letter ISO 3166 country code in capital ASCII letters - Example: DK, DE or US.

The 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.

Each civic address type as defined in TIA1057, Section 3.4 in Annex B

Civic 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

Civic address

Policy index.

The LLDP policy application type.

The LLDP policy tagged flag. Defines if LLDP policy uses tagged VLAN.

The LLDP policy VLAN ID. Only valid when policy 'Tagged' is TRUE

The LLDP policy L2 priority.

The LLDP policy DSCP.

Action

Shows the number of new entries added since switch reboot.

Shows the number of new entries deleted since switch reboot.

Shows the number of LLDP frames dropped due to the entry table being full.

Shows the number of entries deleted due to Time-To-Live expiring.

Shows the time when the last entry was last deleted or added. It also shows the time elapsed since the last change was detected.

This table represents the LLDP interface counters

Each port interface has a set of statistics counters

Logical interface number index.

Shows the number of LLDP frames transmitted.

Shows the number of LLDP frames received.

Shows the number of received LLDP frames containing some kind of error.

Show 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.

Shows 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.

Shows the number of well-formed TLVs, but with an unknown type value.

Shows the number of well-formed TLVs, but with an organizationally TLV which is not supported.

Show 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.

This is a table to show the LLDP neighbors information for a specific interface.

Each interface has a set of neighbors information

Logical interface number index.

Neighbor information table entry index.

Shows the LLDP neighbor's chassis Id.

Shows the LLDP neighbor's port id.

Shows the LLDP neighbor's port description.

Shows the LLDP neighbor's system name.

Shows the LLDP neighbor's system description.

Shows 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.

Shows 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.

This is a table to show the LLDP neighbors information for a specific interface.

Each interface has a set of neighbors information

Logical interface number index.

Neighbor information table entry index.

Neighbor management information table entry index.

LLDP neighbor's management address subtype , section 9.5.9.3 IEEE802.1AB-2005.

LLDP neighbor's management address string, section 9.5.9.4 IEEE802.1AB-2005.

Interface numbering subtype, section 9.5.9.5 IEEE802.1AB-2005.

Interface number, section 9.5.9.6 IEEE802.1AB-2005.

Object identifier, section 9.5.9.8 IEEE802.1AB-2005.

This is a table to show the LLDP neighbors information for a specific interface.

Each interface has a set of neighbors information

Logical interface number index.

Neighbor information table entry index.

LLDP 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 Inventory

LLDP 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 Inventory

Latitude degrees in 2s-complement as specified in RFC 3825. Positive numbers are north of the equator and negative numbers are south of the equator.

Longitude 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.

Altitude 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.

Altitude value in 2s-complement as specified in RFC 3825

Datum (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.

Emergency 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.

Shows the LLDP neighbor's device type.

Shows the LLDP neighbor's hardware revision.

Shows the LLDP neighbor's firmware revision.

Shows the LLDP neighbor's software revision.

Shows the LLDP neighbor's serial number.

Shows the LLDP neighbor's manufacturer name.

Shows the LLDP neighbor's model name.

Shows the LLDP neighbor's asset id.

Shows 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.

Shows 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.

Shows 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.

Shows 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.

Shows 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.

This is a table to show the LLDP-MED remote device (neighbor) civic location information for a specific interface.

Each interface has a set of neighbors information

Logical interface number index.

Neighbor information table entry index.

National subdivision

County

City

City district

Block (Neighborhood)

Street

Street Direction

Trailing Street Suffix

Street Suffix

House No.

House No. Suffix

Landmark

Additional Location Info

Name

Zip code

Building

Apartment/unit

Floor

Room Number

Place type

Postal Community Name

Post Office Box

Additional Code

The two-letter ISO 3166 country code in capital ASCII letters - Example: DK, DE or US.

This is a table to show the LLDP-MED remote device (neighbor) network policies information for a specific interface.

Each interface has a set of neighbors information

Logical interface number index.

Neighbor information table entry index.

Policy index.

The LLDP policy application type.

Policy 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).

Defines if LLDP policy uses tagged VLAN.

The policy VLAN ID. Only valid when policy 'Tagged' is TRUE

Shows the LLDP neighbor's policy L2 priority.

LLDP policy DSCP.

This is a table to clear LLDP statistics for a specific interface.

Each interface has a set of statistics counters

Logical interface number index.

Set to TRUE to clear the LLDP statistics of an interface.

Set to TRUE to clear the LLDP global statistics.

The compliance statement for the implementation.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.

A collection of objects.