- play_arrow Understanding Layer 2 Networking
- play_arrow Configuring MAC Addresses
- play_arrow Configuring MAC Learning
- play_arrow Configuring MAC Accounting
- play_arrow Configuring MAC Notification
- play_arrow Configuring MAC Table Aging
- play_arrow Configuring Learning and Forwarding
- play_arrow Configuring Bridging and VLANs
- play_arrow Configuring 802.1Q VLANs
- 802.1Q VLANs Overview
- 802.1Q VLAN IDs and Ethernet Interface Types
- Configuring Dynamic 802.1Q VLANs
- Enabling VLAN Tagging
- Configuring Tagged Interface with multiple tagged vlans and native vlan
- Sending Untagged Traffic Without VLAN ID to Remote End
- Configuring Tag Protocol IDs (TPIDs) on QFX Series Switches
- Configuring Flexible VLAN Tagging on PTX Series Packet Transport Routers
- Configuring an MPLS-Based VLAN CCC with Pop, Push, and Swap and Control Passthrough
- Binding VLAN IDs to Logical Interfaces
- Associating VLAN IDs to VLAN Demux Interfaces
- Configuring VLAN and Extended VLAN Encapsulation
- Configuring a Layer 2 VPN Routing Instance on a VLAN-Bundled Logical Interface
- Example: Configuring a Layer 2 VPN Routing Instance on a VLAN-Bundled Logical Interface
- Specifying the Interface Over Which VPN Traffic Travels to the CE Router
- Configuring Access Mode on a Logical Interface
- Configuring a Logical Interface for Trunk Mode
- Configuring the VLAN ID List for a Trunk Interface
- Configuring a Trunk Interface on a Bridge Network
- Configuring a VLAN-Bundled Logical Interface to Support a Layer 2 VPN Routing Instance
- Configuring a VLAN-Bundled Logical Interface to Support a Layer 2 VPN Routing Instance
- Configuring a Layer 2 Circuit on a VLAN-Bundled Logical Interface
- Example: Configuring a Layer 2 Circuit on a VLAN-Bundled Logical Interface
- Guidelines for Configuring VLAN ID List-Bundled Logical Interfaces That Connect CCCs
- Specifying the Interface to Handle Traffic for a CCC
- Specifying the Interface to Handle Traffic for a CCC Connected to the Layer 2 Circuit
- play_arrow Configuring Static ARP Table Entries
- play_arrow Configuring Restricted and Unrestricted Proxy ARP
- play_arrow Configuring Gratuitous ARP
- play_arrow Adjusting the ARP Aging Timer
- play_arrow Configuring Tagged VLANs
- play_arrow Stacking and Rewriting Gigabit Ethernet VLAN Tags
- Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview
- Stacking and Rewriting Gigabit Ethernet VLAN Tags
- Configuring Frames with Particular TPIDs to Be Processed as Tagged Frames
- Configuring Tag Protocol IDs (TPIDs) on PTX Series Packet Transport Routers
- Configuring Stacked VLAN Tagging
- Configuring Dual VLAN Tags
- Configuring Inner and Outer TPIDs and VLAN IDs
- Stacking a VLAN Tag
- Stacking Two VLAN Tags
- Removing a VLAN Tag
- Removing the Outer and Inner VLAN Tags
- Removing the Outer VLAN Tag and Rewriting the Inner VLAN Tag
- Rewriting the VLAN Tag on Tagged Frames
- Rewriting a VLAN Tag on Untagged Frames
- Rewriting a VLAN Tag and Adding a New Tag
- Rewriting the Inner and Outer VLAN Tags
- Examples: Stacking and Rewriting Gigabit Ethernet IQ VLAN Tags
- Understanding Transparent Tag Operations and IEEE 802.1p Inheritance
- Understanding swap-by-poppush
- Configuring IEEE 802.1p Inheritance push and swap from the Transparent Tag
- play_arrow Configuring Private VLANs
- Private VLANs
- Understanding Private VLANs
- Bridge Domains Setup in PVLANs on MX Series Routers
- Bridging Functions With PVLANs
- Flow of Frames on PVLAN Ports Overview
- Guidelines for Configuring PVLANs on MX Series Routers
- Configuring PVLANs on MX Series Routers in Enhanced LAN Mode
- Example: Configuring PVLANs with Secondary VLAN Trunk Ports and Promiscuous Access Ports on a QFX Series Switch
- IRB Interfaces in Private VLANs on MX Series Routers
- Guidelines for Configuring IRB Interfaces in PVLANs on MX Series Routers
- Forwarding of Packets Using IRB Interfaces in PVLANs
- Configuring IRB Interfaces in PVLAN Bridge Domains on MX Series Routers in Enhanced LAN Mode
- Example: Configuring an IRB Interface in a Private VLAN on a Single MX Series Router
- play_arrow Configuring Layer 2 Bridging Interfaces
- play_arrow Configuring Layer 2 Virtual Switch Instances
- play_arrow Configuring Layer 2 Protocol Tunneling
- play_arrow Configuring Virtual Routing Instances
- play_arrow Configuring Layer 3 Logical Interfaces
- play_arrow Configuring Routed VLAN Interfaces
- play_arrow Configuring Integrated Routing and Bridging
- play_arrow Configuring VLANS and VPLS Routing Instances
- play_arrow Configuring Multiple VLAN Registration Protocol (MVRP)
- play_arrow Configuring Ethernet Ring Protection Switching
- play_arrow Configuring Q-in-Q Tunneling and VLAN Translation
- play_arrow Configuring Redundant Trunk Groups
- play_arrow Configuring Proxy ARP
- play_arrow Configuring Layer 2 Interfaces on Security Devices
- play_arrow Configuring Security Zones and Security Policies on Security Devices
- play_arrow Configuring Ethernet Port Switching Modes on Security Devices
- play_arrow Configuring Ethernet Port VLANs in Switching Mode on Security Devices
- play_arrow Configuring Secure Wire on Security Devices
- play_arrow Configuring Reflective Relay on Switches
- play_arrow Configuring Edge Virtual Bridging
- play_arrow Troubleshooting Ethernet Switching
- play_arrow Configuration Statements and Operational Commands
Configuring the Transmission of Maximum VLAN Name TLVs in LLDP
This topic discusses the support of transmitting maximum number of VLAN Name TLVs in Link Layer Discovery Protocol (LLDP) protocol data units (PDUs).
Generally, an LLDP PDU can incorporate a maximum of 5 VLAN Name TLVs. To advertise
more than 5 VLAN Name TLVs, run the set protocols lldp interface
<name> transmit-max-vlan-name-tlv command. This command
is a one-time switch which enables the support of transmitting maximum number of
VLAN Name TLVs. However, to disable the support and reset the system to limit up to
5 VLAN Name TLVs, run the delete protocols lldp interface <name>
transmit-max-vlan-name-tlv command.
The <name> in the above commands indicates the
interface name.
The maximum number of VLAN Name TLVs that can be carried is calculated dynamically. The number is based on the maximum transmission unit (MTU) capacity of the PDU while considering the other necessary TLVs that need to be carried in the PDU.
Considerations for Enabling Transmission of Maximum VLAN Name TLVs in LLDP PDUs
Consider the following conditions before enabling the transmission of maximum VLAN Name TLVs in LLDP PDUs:
In a default scenario, wherein VLANs configured on the interface have IDs 2 to 1000, with a default MTU value of 1500, 68 VLAN Name TLVs are transmitted.
If MTU of the interface is increased to 9192 which is the maximum, then 523 VLAN Name TLVs are transmitted. The number of VLAN Name TLVs may vary based on the size of VLAN ID. That is, if the VLAN IDs are more than a single digit, then the maximum number of VLAN Name TLVs, which are transmitted decreases.
If the
vlan-name-tlv-option nameis selected to be transmitted in the VLAN Name TLV, the number of transmitted TLVs changes based on the size of the names of the VLANs. By default, VLAN Name is transmitted as “vlan-ID#”. Therefore, the number of VLAN Name TLVs may increase, or decrease depending on the VLAN names being larger or smaller compared to the default name.The VLANs that are transmitted is decided by the VLAN Name TLV key. By default, it is decided by the VLAN ID. For example, if VLANs are configured from 101 to 200, the first 68 VLANs are transmitted.
Each LLDP PDU transmits the same VLAN Name TLVs until new VLANs are added or deleted, or if the MTU is changed. If new VLANs are added or deleted, then the next set of TLVs are formed based on the conditions mentioned above.
The maximum VLAN Name length which can be accommodated in the VLAN Name TLV is 34 bytes. Therefore, if the VLAN Name length is more than 32 bytes, that vlan is eliminated form the list.
As an example, the table below contains the maximum number of VLAN Name TLVs which can be sent in a given scenario. In the table, the configured VLAN IDs start from 101 and go till 200, which means that the default VLAN Name has a length of 10 bytes, and the maximum VLAN Name that is configured is with the length of 32 bytes. The MTU is set to the default value of 1500.
Table 1: Maximum Number of VLAN Name TLVs Variations TLVs Data Size Maximum Number of VLAN Name TLVs Having vlan-name-tlv-optionset as vlan-id (each of length - 15 bytes)Having vlan-name-tlv-optionset as Name and VLAN size of 32 bytes (each VLAN Name TLV of length - 39 bytes)Example 1
Mandatory TLVs:
Chassis id- 7 bytes
Port Id- 4 bytes
TTL- 2 bytes
End tlv- 0 bytes
13 bytes
65
27
Port Description TLV
8 bytes
System Name TLV
25 bytes
System Description TLV
171 bytes
System Capabilities TLV
7 bytes
Management Address TLV
8 bytes
Mac-PHY status TLV
9 bytes
Link Aggregation subtype 3 and Subtype 7
9 bytes + 9 bytes
Max Frame size TLV
6 bytes
2 Juniper Specific TLVs
16 bytes each
Port Vlan-ID TLV
6 bytes
Example 2 -Includes TLVs in Example 1 with the addition of...
3 DCBX TLVs
25 bytes + 25 bytes + 6 bytes
60
25
LLDP MED Capabilities TLV
7 bytes
Example 3 -Includes TLVs in Example 2 with the addition of...
5 Management Address TLVs of type IPV6
36 bytes
50
20
Power via MDI
12 bytes
Extended power via MDI
7 bytes
