Configuration Guide for Cisco NCS 1004, IOS XR Release 25.x.x

PDF

Configuration Guide for Cisco NCS 1004, IOS XR Release 25.x.x

Configure LLDP drop

Updated: July 31, 2026

Want to summarize with AI?

Log in

Use this procedure to configure the LLDP drop feature for muxponder or muxponder slices on the NCS 1004 to control how LLDP frames are handled..

Enable or disable LLDP (Link Layer Discovery Protocol) frame dropping on muxponder or muxponder slices to control network discovery function and enhance security as needed.

By default, the LLDP drop status is set to False. When you enable LLDP drop, the status is set to True.

Note

By default, LLDP is enabled for NCS 1004. When you enable and then disable LLDP in global configuration mode, LLDP is disabled on all interfaces. To restore LLDP, enable it globally or reload the router.

When you disable LLDP globally, the LLDP gets disabled on all the interfaces

Follow these steps to configure LLDP drop on a muxponder or muxponder slice:

Procedure

1.

Run these commands to configure LLDP drop on a muxponder or muxponder slice.

  • configure hw-module location location mxponder drop-lldp
  • configure hw-module location location mxponder-slice slice-number drop-lldp

    Use the no form of the command to disable LLDP drop.

Example:


RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios#hw-module location 0/1 mxponder drop-lldp
RP/0/RP0/CPU0:ios#commit

Example:

This is a sample in which slice 0 client ports are enabled with LLDP drop.


RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0 drop-lldp
RP/0/RP0/CPU0:ios(config)#commit
2.

Run the show hw-module location all mxponder command to verify the LLDP drop enabled status.

Example:

RP/0/RP0/CPU0:ios#show hw-module location all mxponder
Fri Feb 22 13:22:19.281 UTC

Location:             0/0
Client Bitrate:       NONE
Trunk  Bitrate:       NONE
Status:               Not Provisioned


Location:             0/1
Slice ID:             0
Client Bitrate:       100GE
Trunk  Bitrate:       500G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/1/0/0
                                Traffic Split Percentage

HundredGigECtrlr0/1/0/2         ODU40/1/0/0/0                      100
HundredGigECtrlr0/1/0/3         ODU40/1/0/0/1                      100
HundredGigECtrlr0/1/0/4         ODU40/1/0/0/2                      100
HundredGigECtrlr0/1/0/5         ODU40/1/0/0/3                      100
HundredGigECtrlr0/1/0/6         ODU40/1/0/0/4                      100


Location:             0/1
Slice ID:             1
Client Bitrate:       100GE
Trunk  Bitrate:       500G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/1/0/1
                                Traffic Split Percentage

HundredGigECtrlr0/1/0/8         ODU40/1/0/1/0                      100
HundredGigECtrlr0/1/0/9         ODU40/1/0/1/1                      100
HundredGigECtrlr0/1/0/10        ODU40/1/0/1/2                      100
HundredGigECtrlr0/1/0/11        ODU40/1/0/1/3                      100
HundredGigECtrlr0/1/0/12        ODU40/1/0/1/4                      100


Location:             0/2
Slice ID:             0
Client Bitrate:       100GE
Trunk  Bitrate:       500G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/2/0/0
                                Traffic Split Percentage

HundredGigECtrlr0/2/0/2         ODU40/2/0/0/0                      100
HundredGigECtrlr0/2/0/3         ODU40/2/0/0/1                      100
HundredGigECtrlr0/2/0/4         ODU40/2/0/0/2                      100
HundredGigECtrlr0/2/0/5         ODU40/2/0/0/3                      100
HundredGigECtrlr0/2/0/6         ODU40/2/0/0/4                      100


Location:             0/2
Slice ID:             1
Client Bitrate:       100GE
Trunk  Bitrate:       500G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/2/0/1
                                Traffic Split Percentage

HundredGigECtrlr0/2/0/8         ODU40/2/0/1/0                      100
HundredGigECtrlr0/2/0/9         ODU40/2/0/1/1                      100
HundredGigECtrlr0/2/0/10        ODU40/2/0/1/2                      100
HundredGigECtrlr0/2/0/11        ODU40/2/0/1/3                      100
HundredGigECtrlr0/2/0/12        ODU40/2/0/1/4                      100


Location:             0/3
Slice ID:             0
Client Bitrate:       100GE
Trunk  Bitrate:       300G
Status:               Provisioned
LLDP Drop Enabled:    TRUE
Client Port                     Mapper/Trunk Port          CoherentDSP0/3/0/0
                                Traffic Split Percentage

HundredGigECtrlr0/3/0/2         ODU40/3/0/0/0                      100
HundredGigECtrlr0/3/0/3         ODU40/3/0/0/1                      100
HundredGigECtrlr0/3/0/4         ODU40/3/0/0/2                      100
LLDP drop is configured on the selected muxponder or slice.

LLDP support on management interfaces

A management interface's LLDP support is a network discovery feature that

  • enables the NCS 1004 to form LLDP neighbor relationships over management interfaces,

  • advertises and learns LLDP neighbor information for Operations, Administration, and Maintenance (OAM), and

  • supports configurable attributes such as holdtime, reinit delay, and timer rate.

LLDP attributes and behavior

Advantages of LLDP

  • Provides support on non-Cisco devices.

  • Enables neighbor discovery between non-Cisco devices.

Limitation

  • When you disable LLDP globally, the LLDP gets disabled on all the interfaces.

Note

By default, LLDP is enabled for NCS 1004. But when you enable and disable LLDP in the global configuration mode, LLDP gets disabled on all the interfaces.

Workaround: You must enable LLDP globally or reload the Router.

Cisco Discovery Protocol (CDP) vs LLDP

The CDP is a device discovery protocol that runs over Layer 2. Layer 2 is also known as the data link layer that runs on all Cisco devices, such as routers, bridges, access servers, and switches. This protocol allows the network management applications to automatically discover and learn about other Cisco devices that connect to the network.

The LLDP is also a device discovery protocol that runs over Layer 2. This protocol allows the network management applications to automatically discover and learn about other non-Cisco devices that connect to the network.

Interoperability between non-Cisco devices using LLDP

LLDP is also a neighbor discovery protocol that is used by network devices to advertise information about themselves to other devices on the network. This protocol runs over the data link layer, which allows two systems running different network layer protocols to learn about each other.

With LLDP, the user can also access the information about a particular physical network connection. If the user uses a non-Cisco monitoring tool (through SNMP), LLDP helps you identify the Object Identifiers (OIDs) that the system supports.

These OIDs are supported:

  • 1.0.8802.1.1.2.1.4.1.1.4

  • 1.0.8802.1.1.2.1.4.1.1.5

  • 1.0.8802.1.1.2.1.4.1.1.6

  • 1.0.8802.1.1.2.1.4.1.1.7

  • 1.0.8802.1.1.2.1.4.1.1.8

  • 1.0.8802.1.1.2.1.4.1.1.9

  • 1.0.8802.1.1.2.1.4.1.1.10

  • 1.0.8802.1.1.2.1.4.1.1.11

  • 1.0.8802.1.1.2.1.4.1.1.12

Neighbor discovery

System advertises the LLDP TLV (Type Length Value) details over the management network using which other devices in the management network can learn about this device.

Configuring LLDP

  • LLDP full stack functionality is supported on all three management interfaces supported in NCS 1004.

  • You can selectively enable or disable LLDP on any of the management interfaces on demand.

  • You can selectively enable or disable LLDP transmit or receive functionality at the management interface level.

  • Information gathered using LLDP can be stored in the device Management Information Database (MIB) and queried with the Simple Network Management protocol (SNMP).

  • LLDP operational data are available in both Command Line Interface and netconf-yang interface.

Enabling LLDP globally

When you enable LLDP globally, all interfaces that support LLDP are automatically enabled for both transmit and receive operations.

Note

You can override this default operation at the interface to disable receive or transmit operations.

This table describes the global LLDP attributes that the user can configure:

Table 1.

Attribute

Default

Range

Description

Holdtime

120

0–65535

Specifies the hold time (in sec). Hold time refers to the time or duration that an LLDP device maintains the neighbor information before discarding.

Reinit

2

2–5

Delay (in sec) for LLDP initialization on any interface

Timer

30

5-65534

Specifies the rate at which LLDP packets are sent (in sec)

Debugging LLDP issues

These commands are used for debugging issues in the LLDP functionality.

  • show lldp traffic

  • debug lldp all

  • debug lldp errors

  • debug lldp events

  • debug lldp packets

  • debug lldp tlvs

  • debug lldp trace

  • debug lldp verbose

Configure LLDP on management port

Enable LLDP to facilitate device discovery and neighbor information exchange on the management port.
Follow these steps to configure LLDP on the management port:

Procedure

1.

Run the lldp management enable command to enable LLDP on all management interfaces.

Example:

This example shows the commands to configure LLDP globally. The global LLDP configuration enables LLDP on all the three management interfaces.


RP/0/RP0/CPU0:regen#configure terminal
RP/0/RP0/CPU0:regen(config)#lldp management enable 
RP/0/RP0/CPU0:regen(config)#lldp holdtime 30 
RP/0/RP0/CPU0:regen(config)#lldp reinit 2 
RP/0/RP0/CPU0:regen(config)#commit
2.

Run the show running-config lldp command to verify the LLDP configuration.

Example:


RP/0/RP0/CPU0:regen#show running-config lldp
Tue Dec 10 10:36:11.567 UTC
lldp
timer 30
reinit 2
holdtime 120
management enable
!
3.

Run the show lldp interface and show lldp neighbors commads to verify the LLDP data.

Example:

This is a sample output of show lldp interface command.


RP/0/RP0/CPU0:regen#show lldp interface 
Thu Nov  7 08:45:22.934 UTC
MgmtEth0/RP0/CPU0/0:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME
MgmtEth0/RP0/CPU0/1:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME

This is a sample output of show lldp neighbors command.


RP/0/RP0/CPU0:M-131#show lldp neighbors
Mon Dec  2 11:01:20.143 CET
Capability codes:
        (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
        (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other

Device ID       Local Intf               Hold-time  Capability     Port ID
[DISABLED]      MgmtEth0/RP0/CPU0/0      120        B               gi19
MYS-130         MgmtEth0/RP0/CPU0/1      120        R               MgmtEth0/RP0/CPU0/1

where [ DISABLED] shows that the LLDP is disabled on the interface MgmtEth0/RP0/CPU0/0.

Enabling LLDP per Management Interface

This example shows the commands to configure LLDP at the management interface level.


RP/0/RP0/CPU0:ios(config)#interface mgmtEth 0/RP0/CPU0/X
RP/0/RP0/CPU0:ios(config-if)#lldp enable
RP/0/RP0/CPU0:ios(config-if)#commit

Disabling LLDP Transmit and Receive Operations

This example shows the commands to disable the LLDP transmit operations at the specified management interface.


RP/0/RP0/CPU0:ios(config)#interface mgmtEth 0/RP0/CPU0/X
RP/0/RP0/CPU0:ios(config-if)#lldp transmit disable
RP/0/RP0/CPU0:ios(config-if)#commit

This example shows the commands to disable the LLDP receive operations at the specified management interface.


RP/0/RP0/CPU0:ios(config)#interface mgmtEth 0/RP0/CPU0/X
RP/0/RP0/CPU0:ios(config-if)#lldp receive disable
RP/0/RP0/CPU0:ios(config-if)#commit
LLDP is successfully configured on the management port.