Overview
Describes how to allow LLDP packets to be transmitted in clear text, facilitating neighbor discovery and troubleshooting on MACsec-enabled ports while maintaining encryption for all other data traffic.
A MACsec policy exception for LLDP packets is a MACsec configuration mechanism that
-
allows the transmission of LLDP (Link Layer Discovery Protocol) packets in clear text even when MACsec encryption is enabled,
-
enables network administrators to facilitate neighbor discovery and troubleshooting by making LLDP packets visible on the network, and
-
maintains MACsec encryption for all other traffic, ensuring the overall security of the data link layer.
| Feature Name |
Release Information |
Feature Description |
|---|---|---|
| MACsec Policy Exception for Link Layer Discovery Protocol Packets |
Release 26.1.1 |
Introduced in this release on: Fixed Systems (8700 [ASIC: K100], 8010 [ASIC: A100])(select variants only*); *This feature is supported on:
|
| MACsec Policy Exception for Link Layer Discovery Protocol Packets |
Release 24.4.1 |
Introduced in this release on: Fixed Systems (8200 [ASIC: P100], 8700 [ASIC: P100])(select variants only*); Modular Systems (8800 [LC ASIC: P100])(select variants only*) *This feature is supported on:
|
| MACsec Policy Exception for Link Layer Discovery Protocol Packets |
Release 7.11.1 |
We have introduced an option in MACsec policy exceptions to accommodate Link Layer Discovery Protocol (LLDP) packets in an unencrypted format. LLDP packets in clear text format help you troubleshoot LLDP neighbor discovery network issues on MAcsec-enabled ports. By default, MACsec always operates in must-secure mode, allowing encrypted traffic flow including LLDP packets only after securing the MACsec Key Agreement (MKA) session. The feature introduces these changes: CLI:
YANG Data Models:
(See GitHub, YANG Data Models Navigator) |
By default, when MACsec is enabled, it encrypts all network traffic at the data link layer, including LLDP packets. This ensures that communications between peers remain secure. The router stores information learned from LLDP exchanges in the Management Information Base (MIB).
However, starting from Cisco IOS XR Software Release 7.11.1, routers provide an option to transmit LLDP packets in clear text even when MACsec is enabled. Administrators can enable this exception using the allow lldp-in-clear command in the MACsec policy. This functionality is useful for troubleshooting LLDP neighbor discovery issues, as it allows network administrators to view LLDP packets unencrypted for diagnostic purposes.
By default, MACsec operates in must-secure mode, permitting encrypted traffic flow—including LLDP packets—only after the MACsec Key Agreement (MKA) session is secured.
We strongly advise against enabling the MACsec exception to retain LLDP packets unencrypted unless necessary for network maintenance. You must ensure to configure LLDP packets in clear text at both ends of the MACsec link.
| Feature |
Default MACsec behavior |
With LLDP exception enabled |
|---|---|---|
| LLDP packet encryption | Encrypted | Clear text (unencrypted) |
| Troubleshooting support | Limited (due to encryption) | Enhanced (LLDP packets visible in plain text) |
| Security posture | Highest (all packets encrypted) | Slightly reduced for LLDP, others encrypted |
LLDP packet handling in MACsec: default encryption and clear-text exception
-
An administrator enables the allow lldp-in-clear command to transmit LLDP packets in clear text on a MACsec-enabled port for troubleshooting neighbor discovery issues.
-
By default, a router encrypts LLDP packets with MACsec, ensuring all data link layer communications are secured.
MACsec LLDP clear-text: troubleshooting challenges and security risks
-
Without enabling the LLDP exception, LLDP packets remain encrypted under MACsec, making it difficult to diagnose neighbor discovery problems using packet captures.
-
Transmitting all protocol packets, including LLDP, in clear text on a MACsec-enabled port would compromise the security provided by MACsec, which is not the default or recommended configuration.