Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring LLDP

 

You configure LLDP by including the lldp statement and associated parameters at the [edit protocols] hierarchy level. The complete set of LLDP statements follows:

The following statements have default values:

  • advertisement-interval—The default value is 30 seconds. The allowable range is from 5 through 32768 seconds.

  • hold-multiplier—The default values is 4. The allowable range is from 2 through 10.

  • ptopo-configuration-maximum-hold-time—The default value is 300 seconds. The allowable range is from 1 through 2147483647 seconds.

  • transmit-delay—The default values is 2 seconds. The allowable range is from 1 through 8192 seconds.

The following statements must be explicitly configured:

  • lldp-configuration-notification-interval—The allowable range is from 0 through 3600 seconds. There is no default value.

  • ptopo-configuration-trap-interval—The allowable range is from 1 through 2147483647 seconds. There is no default value.

By default, LLDP is disabled, and user must configure it using [set protocols lldp interface (all | interface-name)] to use the LLDP services. If it is enabled for all interfaces, you can disable LLDP on specific interfaces.

Note

The interface-name must be the physical interface (for example, ge-1/0/0) and not a logical interface (unit).

  • To configure LLDP on all interfaces:

    [edit protocols lldp]

    user@switch# set interface all
  • To configure LLDP on a specific interface:

    [edit protocols lldp]

    user@switch# set interface interface-name

To disable LLDP, include the disable option:

  • To disable LLDP on all interfaces:

    [edit protocols lldp]

    user@switch# set interface all disable
  • To disable LLDP on a specific interface:

    [edit protocols lldp]

    user@switch# set interface interface-name disable

Starting with Junos OS Release 14.2, you can configure management interfaces, such as fxp0 or me0, on MX Series routers to send LLDP frames to and receive LLDP frames from neighboring LLDP interfaces. To configure the management interfaces, nclude the interface interface-name statement at the [edit protocols lldp] and [edit routing-instances routing-instance-name protocols lldp] hierarchy levels. By default, the functionality to send LLDP frames is enabled. You can also specify a management interface with the show lldp neighbors interface interface-name command to view configuration details about LLDP neighbors for the corresponding management interface.

To configure LLDP on a T Series router within a TX Matrix, you must specify the interface name in the LLDP configuration for the TX Matrix. For information about interface names for TX Matrix routers, see TX Matrix Router Chassis and Interface Names. For information about FPC numbering, see Routing Matrix with a TX Matrix Router FPC Numbering.

Starting with Junos OS Release 14.2, LLDP is supported on extended ports in the Junos Fusion technology.For information about interface names in the Junos Fusion technology, see Understanding Junos Fusion Ports .

The advertisement interval determines the frequency that an LLDP interface sends LLDP advertisement frames. The default value is 30 seconds. The allowable range is from 5 through 32768 seconds. You adjust this parameter by including the advertisement-interval statement at the [edit protocols lldp] hierarchy level.

The hold multiplier determines the multiplier to apply to the advertisement interval. The resulting value in seconds is used to cache learned LLDP information before discard. The default value is 4. When used with the default advertisement interval value of 30 seconds, this makes the default cache lifetime 120 seconds. The allowable range of the hold multiplier is from 2 through 10. You adjust this parameter by including the hold-multiplier statement at the [edit protocols lldp] hierarchy level.

The transmit delay determines the delay between any two consecutive LLDP advertisement frames. The default value is 2 seconds. The allowable range is from 1 through 8192 seconds. You adjust this parameter by including the transmit-delay statement at the [edit protocols lldp] hierarchy level.

The physical topology configuration maximum hold time determines the time interval for which an agent device maintains physical topology database entries. The default value is 300 seconds. The allowable range is from 1 through 2147483647 seconds. You adjust this parameter by including the ptopo-configuration-maximum-hold-time statement at the [edit protocols lldp] hierarchy level.

The LLDP configuration notification interval determines the period for which trap notifications are sent to the SNMP Master Agent when changes occur in the database of LLDP information. This capability is disabled by default. The allowable range is from 0 (disabled) through 3600 seconds. You adjust this parameter by including the lldp-configuration-notification-interval statement at the [edit protocols lldp] hierarchy level.

The physical topology configuration trap interval determines the period for which trap notifications are sent to the SNMP Master Agent when changes occur in the global physical topology statistics. This capability is disabled by default. The allowable range is from 0 (disabled) through 3600 seconds. The LLDP agent sends traps to the SNMP Master Agent if this interval has a value greater than 0 and there is any change during the lldp-configuration-notification-interval trap interval. You adjust this parameter by including the ptopo-configuration-trap-interval statement at the [edit protocols lldp] hierarchy level.

Starting in Junos OS Release 15.1R7, you can enable or disable the Link Layer Discovery Protocol (LLDP) and Physical Topology (PTOPO) MIB traps for a specific interface or for all interfaces on EX3300, EX4200, EX4500, EX4550, EX6200, and EX8200 switches by configuring the trap-notification statement at the [edit protocols lldp interface interface-name] hierarchy level.

By default, LLDP generates the SNMP index of the interface for the port ID Type, Length, and Value (TLV). Starting with Junos OS Release 12.3R1, you can generate the interface name as the port ID TLV. To do so, include the interface-name statement at the [edit protocols lldp port-id-subtype] hierarchy level. When the interface-name statement is configured on the remote LLDP neighbor, the show lldp neighbors command output displays the interface name in the Port ID field rather than the SNMP index of the interface, which is displayed by default. If you change the default behavior of generating the SNMP index of the interface as the Port ID TLV, you can reenable the default behavior by including the locally-assigned statement at the [edit protocols lldp port-id-subtype] hierarchy level.

Note

Starting with Junos OS Release 12.3, the value of the MIB variable lldpLocPortId depends on the SNMP MIB object entity that is used to generate the port ID TLV. If the port ID TLV generation is configured to use the interface name in the set port-id-subtype interface-name command, then the value of the MIB variable lldpLocPortId is the interface name and not the SNMP index.

Release History Table
Release
Description
Starting in Junos OS Release 15.1R7, you can enable or disable the Link Layer Discovery Protocol (LLDP) and Physical Topology (PTOPO) MIB traps for a specific interface or for all interfaces on EX3300, EX4200, EX4500, EX4550, EX6200, and EX8200 switches by configuring the trap-notification statement at the [edit protocols lldp interface interface-name] hierarchy level.
Starting with Junos OS Release 14.2, you can configure management interfaces, such as fxp0 or me0, on MX Series routers to send LLDP frames to and receive LLDP frames from neighboring LLDP interfaces.
Starting with Junos OS Release 14.2, LLDP is supported on extended ports in the Junos Fusion technology.
Starting with Junos OS Release 12.3R1, you can generate the interface name as the port ID TLV.
Starting with Junos OS Release 12.3, the value of the MIB variable lldpLocPortId depends on the SNMP MIB object entity that is used to generate the port ID TLV.