Courseiva
CDP / LLDPInterface Config

lldp transmit

Enables LLDP transmission on an interface, allowing the device to advertise its identity and capabilities to neighboring LLDP-enabled devices.

Definition: lldp transmit is a Cisco IOS interface config command. Enables LLDP transmission on an interface, allowing the device to advertise its identity and capabilities to neighboring LLDP-enabled devices.

Overview

The `lldp transmit` command, issued in interface configuration mode, enables the transmission of Link Layer Discovery Protocol (LLDP) advertisements on a specific interface. LLDP is a vendor-neutral, IEEE 802.1AB standard protocol that allows network devices to advertise their identity, capabilities, and neighbors on an Ethernet network. By enabling LLDP transmit on an interface, the device sends periodic LLDP frames containing information such as chassis ID, port ID, system name, system description, and supported capabilities (e.g., routing, bridging, telephony).

This command is essential for network discovery, topology mapping, and inventory management, especially in multi-vendor environments where Cisco's proprietary CDP may not be supported. Network engineers reach for `lldp transmit` when they need to ensure that a device advertises itself to LLDP neighbors, typically in conjunction with `lldp receive` to enable bidirectional LLDP operation. The command is often used during initial network deployment, when integrating new devices, or when troubleshooting connectivity issues where neighbor discovery is required.

It fits into a broader workflow of enabling LLDP globally with `lldp run`, then selectively enabling transmit/receive on specific interfaces. Important IOS behavior includes that LLDP is disabled by default globally and on all interfaces; the `lldp run` global command must be issued first. The `lldp transmit` command modifies the running configuration and is saved to startup-config with `copy running-config startup-config`.

There is no privilege level restriction beyond standard user EXEC (privilege level 1 for show commands, but configuration requires privilege level 15). The command takes effect immediately, and LLDP frames are sent at a default interval of 30 seconds (configurable with `lldp timer`). Buffered output is not applicable; the command directly updates the interface configuration.

Understanding this command is critical for CCNA and CCNP candidates as it appears in exam topics on network discovery and troubleshooting. In practice, enabling LLDP transmit on interfaces that connect to other LLDP-enabled devices (switches, routers, wireless LAN controllers, IP phones) populates the neighbor table, which can be viewed with `show lldp neighbors`. This information is invaluable for verifying physical connectivity, detecting unauthorized devices, and automating network management tasks.

The command is also a prerequisite for advanced features like LLDP-MED (Media Endpoint Discovery) for VoIP devices. When compared to CDP, LLDP is preferred in multi-vendor networks, while CDP remains useful in pure Cisco environments. The `lldp transmit` command is the interface-level counterpart to the global `lldp run` command; without it, the interface will not send LLDP frames even if LLDP is globally enabled.

A common mistake is forgetting to enable LLDP globally first, which results in the interface command being accepted but having no effect. Another pitfall is enabling transmit without receive, which prevents the device from learning about neighbors. For CCNA/CCNP candidates, mastering this command involves understanding its interaction with `lldp receive`, `lldp timer`, `lldp holdtime`, and `lldp reinit`.

In summary, `lldp transmit` is a foundational command for network discovery, enabling devices to announce their presence and capabilities to neighboring devices, thereby simplifying network management and troubleshooting.

Syntax·Interface Config
lldp transmit

When to Use This Command

  • Enable LLDP transmit on a switch port connected to a VoIP phone to advertise VLAN information and PoE capabilities.
  • Configure LLDP transmit on a router interface to allow a network management system to discover the device topology.
  • Enable LLDP transmit on an access port to provide neighboring switches with device identification and management IP.
  • Use in conjunction with 'lldp receive' to enable full LLDP operation for network discovery and troubleshooting.

Command Examples

Enable LLDP transmit on an interface

interface GigabitEthernet0/1 lldp transmit
Switch(config-if)# lldp transmit
Switch(config-if)#

The command is entered in interface configuration mode. No output is displayed upon successful execution; the prompt returns without error.

Verify LLDP transmit is enabled

show lldp interface GigabitEthernet0/1
GigabitEthernet0/1:
  Tx: enabled
  Rx: disabled
  Tx state: IDLE
  Rx state: IDLE

The output shows that LLDP transmit is enabled (Tx: enabled) and receive is disabled (Rx: disabled). Tx state and Rx state indicate the current LLDP state machine status.

Understanding the Output

The command 'lldp transmit' itself produces no output when successful. To verify, use 'show lldp interface <interface>'. The key field is 'Tx: enabled' indicating LLDP transmission is active.

If 'Tx: disabled' appears, LLDP transmit is not enabled. The 'Tx state' field shows the internal state machine (IDLE, TRANSMITTING, etc.) and is typically IDLE when not actively sending frames. 'Rx state' is irrelevant for transmit-only configuration.

In a real network, ensure both 'Tx' and 'Rx' are enabled for full LLDP operation unless only one direction is needed.

Configuration Scenarios

Enable LLDP Transmit on an Interface Connecting to a Multi-Vendor Switch

A network engineer needs to enable LLDP transmission on a Cisco router interface connected to a Juniper switch to allow the Juniper switch to discover the Cisco router. LLDP is globally enabled, but transmit must be enabled on the specific interface.

Topology

R1(Gi0/0)---10.0.12.0/30---(Gi0/0)Juniper-SW

Steps

  1. 1.Step 1: Enter global configuration mode: Router> enable
  2. 2.Step 2: Enter global configuration mode: Router# configure terminal
  3. 3.Step 3: Enable LLDP globally (if not already): Router(config)# lldp run
  4. 4.Step 4: Enter interface configuration mode for GigabitEthernet0/0: Router(config)# interface GigabitEthernet0/0
  5. 5.Step 5: Enable LLDP transmission on the interface: Router(config-if)# lldp transmit
  6. 6.Step 6: Optionally enable LLDP reception: Router(config-if)# lldp receive
  7. 7.Step 7: Exit and save configuration: Router(config-if)# end
  8. 8.Step 8: Save running config: Router# copy running-config startup-config
Configuration
! Enable LLDP globally
lldp run
!
interface GigabitEthernet0/0
 description Link to Juniper Switch
 ip address 10.0.12.1 255.255.255.252
 lldp transmit
 lldp receive
!

Verify: Use `show lldp neighbors` to verify that the router is sending LLDP frames. Expected output should show the Juniper switch as a neighbor (if it also has LLDP enabled). Example output: Router# show lldp neighbors 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 Juniper-SW Gi0/0 120 B ge-0/0/0 Total entries displayed: 1

Watch out: Forgetting to enable LLDP globally with `lldp run` before configuring `lldp transmit` on the interface. The interface command will be accepted, but no LLDP frames will be sent until the global command is issued.

Enable LLDP Transmit on a Trunk Port to a Wireless LAN Controller

A Cisco switch connects to a third-party wireless LAN controller (WLC) via a trunk port. The network team wants the WLC to discover the switch via LLDP for topology mapping. Only LLDP transmission is required on the switch side; reception is optional.

Topology

SW1(Gi0/1)---Trunk---(Gi0/0)WLC

Steps

  1. 1.Step 1: Enter privileged EXEC mode: Switch> enable
  2. 2.Step 2: Enter global configuration mode: Switch# configure terminal
  3. 3.Step 3: Enable LLDP globally: Switch(config)# lldp run
  4. 4.Step 4: Enter interface configuration mode for GigabitEthernet0/1: Switch(config)# interface GigabitEthernet0/1
  5. 5.Step 5: Configure the interface as a trunk (if not already): Switch(config-if)# switchport mode trunk
  6. 6.Step 6: Enable LLDP transmission: Switch(config-if)# lldp transmit
  7. 7.Step 7: Exit and save: Switch(config-if)# end
  8. 8.Step 8: Save configuration: Switch# copy running-config startup-config
Configuration
! Enable LLDP globally
lldp run
!
interface GigabitEthernet0/1
 description Trunk to WLC
 switchport mode trunk
 lldp transmit
!

Verify: Use `show lldp neighbors interface GigabitEthernet0/1` to check if the WLC is discovered. Expected output should list the WLC if it has LLDP enabled. Example: Switch# show lldp neighbors interface GigabitEthernet0/1 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 WLC-5508 Gi0/1 120 B,W Gi0/0 Total entries displayed: 1

Watch out: On trunk ports, LLDP frames are sent on the native VLAN by default. Ensure the native VLAN is consistent between the switch and WLC; otherwise, LLDP frames may not be received. Also, some WLCs require LLDP to be enabled on their side.

Troubleshooting with This Command

When troubleshooting LLDP transmission issues, the first step is to verify that LLDP is globally enabled using `show lldp`. Healthy output should indicate 'LLDP is enabled' and show the timer and holdtime values. If LLDP is not enabled globally, the `lldp transmit` interface command will have no effect.

Next, check the specific interface with `show lldp interface [interface]`. Healthy output shows 'LLDP is enabled' for both transmit and receive (if configured). Problem indicators include 'LLDP is disabled' or 'LLDP transmit is disabled'.

If transmit is disabled, reapply the `lldp transmit` command. Common symptoms include a missing neighbor in `show lldp neighbors`. Focus on the 'Device ID', 'Local Intf', and 'Port ID' fields.

If a neighbor is missing, verify that the neighbor device also has LLDP enabled and that both sides have compatible LLDP configurations. Check for interface errors or VLAN mismatches. Use `show lldp neighbors detail` to see detailed information including system description and capabilities.

If LLDP frames are not being sent, verify the interface is up/up with `show interfaces`. Also check if the interface is configured as a switchport access or trunk; LLDP operates on all Ethernet interfaces regardless of mode. Another diagnostic step is to use `debug lldp packets` (with caution in production) to see if LLDP frames are being transmitted and received.

Correlate with `show logging` to capture any LLDP-related errors. If the neighbor is discovered but then disappears, check the holdtime and timer values; the default holdtime is 120 seconds, and the timer is 30 seconds. If the neighbor is not receiving frames, ensure there is no ACL blocking LLDP (destination MAC 0180.c200.000e).

On some platforms, LLDP may be disabled by default on certain interface types (e.g., loopback). Also, verify that the interface is not in err-disabled state. For multi-vendor environments, ensure that the neighbor supports the same LLDP TLVs (Type-Length-Values).

Use `show lldp tlv` to see which TLVs are being advertised. If the problem persists, check the global LLDP configuration with `show running-config | include lldp`. A step-by-step diagnostic flow: 1) `show lldp` to confirm global status. 2) `show lldp interface` to confirm per-interface status. 3) `show lldp neighbors` to see if any neighbors are discovered. 4) If no neighbors, check physical connectivity and interface status. 5) Verify neighbor device LLDP configuration. 6) Use `debug lldp packets` to observe frame exchange. 7) Check for ACLs or VLAN issues. 8) Review logs for LLDP errors.

By following this flow, network engineers can quickly isolate and resolve LLDP transmission issues.

CCNA Exam Tips

1.

CCNA exam tip: 'lldp transmit' is configured per interface; it does not enable LLDP globally. You must also enable 'lldp run' globally first.

2.

CCNA exam tip: LLDP is a vendor-neutral protocol; Cisco also has CDP which is proprietary. Know the difference and when to use each.

3.

CCNA exam tip: The 'lldp transmit' command can be used independently of 'lldp receive'; you can enable only one direction.

4.

CCNA exam tip: On some Cisco platforms, LLDP is disabled by default; you must enable it globally with 'lldp run' before interface-level commands take effect.

Common Mistakes

Mistake: Forgetting to enable LLDP globally with 'lldp run' before configuring 'lldp transmit' on an interface. Consequence: The interface command is accepted but LLDP does not operate.

Mistake: Enabling 'lldp transmit' but not 'lldp receive' when full neighbor discovery is needed. Consequence: The device advertises itself but cannot learn about neighbors.

Mistake: Applying 'lldp transmit' to a trunk port without considering that LLDP may carry VLAN information that could conflict with CDP. Consequence: Potential misconfiguration if both protocols are used.

lldp transmit vs lldp receive

The commands 'lldp transmit' and 'lldp receive' are often considered together because they control the two unidirectional halves of LLDP operation on an interface. While both are configured in interface configuration mode, one enables sending LLDP advertisements and the other enables listening for advertisements from neighbors.

Aspectlldp transmitlldp receive
ScopePer-interface control of sending LLDP framesPer-interface control of receiving LLDP frames
Configuration modeInterface configuration modeInterface configuration mode
Default stateEnabled globally but disabled per interface (if global enabled)Enabled globally but disabled per interface (if global enabled)
PersistenceSurvives reload, stored in running-configSurvives reload, stored in running-config
Typical useTo advertise device identity and capabilities to neighborsTo learn about neighboring devices and build topology
PrecedenceRequires 'lldp run' globally; per-interface setting overrides defaultRequires 'lldp run' globally; per-interface setting overrides default

Use lldp transmit when you need the device to announce its presence and capabilities to LLDP neighbors, such as for network discovery and inventory systems.

Use lldp receive when you need to listen for LLDP advertisements from neighbors to map the network topology or gather neighbor information.

Platform Notes

In IOS-XE (e.g., Catalyst 9000 series), the `lldp transmit` command syntax is identical to classic IOS. However, IOS-XE may have additional options such as `lldp tlv-select` to customize which TLVs are transmitted. The output of `show lldp neighbors` is similar but may include additional fields like 'Network Address' in newer versions.

In NX-OS (e.g., Nexus switches), the equivalent command is `lldp transmit` under interface configuration mode, but the global enable command is `feature lldp` instead of `lldp run`. For example: `interface ethernet 1/1 ; lldp transmit`. NX-OS also supports `no lldp transmit` to disable.

In ASA (Adaptive Security Appliance), LLDP is not supported; instead, CDP is used for neighbor discovery. ASA does not have an `lldp transmit` command. For IOS-XR (e.g., ASR 9000), LLDP is supported with the command `lldp` under interface configuration, but the syntax is slightly different: `lldp transmit` is valid, but the global enable is `lldp` (no `run` keyword).

For example: `interface GigabitEthernet0/0/0/0 ; lldp transmit`. In IOS versions 12.x and earlier, LLDP was introduced in 12.2(33)SB and later; earlier versions may not support LLDP. In 15.x and 16.x, LLDP is fully supported.

Some older IOS versions require the `lldp run` command to be entered before interface-level commands take effect. In all platforms, the command is saved in running-config and can be verified with `show running-config interface`. Always check the specific platform documentation for any nuances.

Related Commands

Practice for the CCNA 200-301

Test your knowledge with practice questions covering all CCNA 200-301 exam domains.

Practice CCNA 200-301 Questions