IP Packet Format
IP Packets Product Documentation contains the main data transmission protocol used in a variety of packet formats, packet example. By IP Packets Product Documentation, be able to enhance understanding of various protocol packets.
IP Packets Product Documentation contains the main data transmission protocol used in a variety of packet formats, packet example. By IP Packets Product Documentation, be able to enhance understanding of various protocol packets.
LLDP Frame
The Link Layer Discovery Protocol (LLDP) is a standard Layer 2 discovery protocol defined in IEEE 802.1ab. It encapsulates a local device's main capability, management address, device ID, and interface ID into LLDP packets and sends the packets to neighboring nodes. After receiving the information, the neighboring nodes save the information in a standard management information base (MIB) for the network management system (NMS) to query and judge the communication status of links. An LLDP data unit (LLDPDU) can be encapsulated into an LLDP packet in either Ethernet II or 802.3 logical link control (LLC) Subnetwork Access Protocol (SNAP) format.
Frame Format
+--------------15---------------31 | DMAC | + ----------------| | | | +-------------- | | SMAC | +-------------------------------| | Type | | | +-------------------------------| | Data | | (n bytes) | +-------------------------------| | FCS | +-------------------------------|
Field |
Length |
Description |
---|---|---|
DMAC |
6 bytes |
This field indicates the destination MAC address of the LLDP frame. According to IEEE 802.1AB, the following three values are available:
On Huawei devices running the Versatile Routing Platform (VRP ®) operating system, the destination MAC address is 0x0180-C200-000E. |
SMAC |
6 bytes |
This field indicates the source MAC address, which is the port MAC address or device bridge MAC address. If a port address is available, use the port MAC address. Otherwise, use the device bridge MAC address. |
Type |
2 or 8 bytes |
This field indicates the protocol type.
|
Data |
Variable |
This field indicates the payload of the frame (namely, LLDPDU). LLDPDU is a data unit that is encapsulated in an LLDP frame. A device encapsulates the local information in the Type-Length-Value (TLV) format. Several such TLVs constitute an LLDPDU and are transmitted in an LLDP frame. Figure 1-60 shows the format of an LLDPDU. |
FCS |
4 bytes |
This field provides a method for the receiving network adapter to determine whether a transmission error occurs. If errors are detected, involved frames are discarded. FCS is a general name for multiple verification methods. In an Ethernet frame, CRC is usually used as the FCS. |
LLDPDU Format
An LLDPDU contains multiple TLVs, which start with the Chassis ID TLV, Port ID TLV, and TTL TLV and end with the End TLV. The middle TLVs are optional, as shown in Figure 1-60. An LLDPDU must contain the Chassis ID TLV, Port ID TLV, and TTL TLV. Otherwise, the packet is invalid. Optional TLVs mean that LLDPDUs may or may not contain these TLVs. In IEEE 802.1AB, TLVs are classified into basic TLVs, organizationally specific TLVs, and reserved TLVs.
+----------------------------------------------+ | Chassis ID TLV(Type = 1bytes) | +----------------------------------------------+ | Port ID TLV(Type = 2bytes) | +----------------------------------------------+ | TTL TLV (Type = 3bytes) | +----------------------------------------------+ | Optional TLV (Type = 4bytes) | +----------------------------------------------+ | ... | +----------------------------------------------+ | Optional TLV | +----------------------------------------------+ | Optional End TLV | +----------------------------------------------+
+----------------------------------------------+ | Chassis ID (Type = 1bytes) | +----------------------------------------------+ | Port ID (Type = 2bytes) | +----------------------------------------------+ | Time To Live (Type = 3bytes) | +----------------------------------------------+ | Port Description (Type = 4bytes) | +----------------------------------------------+ | System Name (Type = 5bytes) | +----------------------------------------------+ | System Description (Type = 6bytes)| +----------------------------------------------+ | System Capabilities (Type = 7bytes)| +----------------------------------------------+ | Management Address (Type = 8bytes)| +----------------------------------------------+ | Optional End of LLDPDU | +----------------------------------------------+
TLV Name |
Description |
Mandatory/Optional |
---|---|---|
End of LLDPDU |
This 2-byte all-0 TLV is used to mark the end of an LLDPDU. The format of the TLV is as follows: +----------------------------------------------+ | TLV type = 0 (7 bits) | +----------------------------------------------+ | TLV information string length = 0 (9 bits) | +----------------------------------------------+ |
Optional |
Chassis ID (Type = 1) |
This TLV indicates the ID of the chassis sending LLDPDUs. It is the first TLV in LLDPDUs. Each LLDPDU must contain one and only one such TLV. The format of the TLV is as follows: +----------------------------------------------+ | TLV type = 1 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | chassis ID subtype (8 bits) | +----------------------------------------------+ | chassis ID (1 < n < 255 octets) | +----------------------------------------------+ The TLV Value field of the Chassis ID TLV must start with an 8-bit chassis ID subtype. The meanings of these subtypes are as follows: ID Subtype Description Reference 0 Reserved - 1 Chassis component IETF RFC 4133 2 Interface alias IETF RFC 2863 3 Port component IETF RFC 4133 4 MAC address IEEE Std 802 5 Network address 1-byte character string, identifying a network address family and an associated network address 6 Interface name IETF RFC 2863 7 Locally assigned Locally assigned character string that contains letters and digits 8-255 Reserved On Huawei devices running the Versatile Routing Platform (VRP ®) operating system, the value of the Chassis ID TLV is set to the bridge MAC address of the chassis (subtype = 4). |
Mandatory |
Port ID (Type = 2) |
This TLV indicates the name of the port that sends the LLDPDU. Each LLDPDU must contain one and only one Port ID TLV. The format of the TLV is as follows: +----------------------------------------------+ | TLV type = 2 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | port ID subtype (8 bits) | +----------------------------------------------+ | port ID (1 < n < 255 octets) | +----------------------------------------------+ The Port ID TLV also carries the ID subtype field. The meanings of these subtypes are as follows: ID Subtype Description Reference 0 Reserved - 1 Interface alias IETF RFC 2863 2 Port component IETF RFC 4133 3 MAC address IEEE Std 802 4 Network address 1-byte character string, identifying a network address family and an associated network address 5 Interface name IETF RFC 2863 6 Agent circuit ID IETF RFC 3046 7 Locally assigned Locally assigned character string that contains letters and digits 8-255 Reserved On Huawei devices running the VRP ® (Versatile Routing Platform) operating system, the Port ID TLV is set to the value of the ifName leaf node in IF-MIB (IETF RFC 2863) (subtype = 5). |
Mandatory |
Time To Live (Type = 3) |
This 4-byte TLV identifies the lifetime (in seconds) of an LLDPDU on a neighbor. The value is an integer from 0 to 65535. It conveys the validity period of a message sent to a receiver. If the sender does not update the message after this period, the receiver discards the message. Upon receipt of this TLV, the receiver updates the message lifetime of its remote peer based on the validity period. The format of the TLV is as follows: +----------------------------------------------+ | TLV type = 3 (7 bits) | +----------------------------------------------+ | TLV information string length = 2 (9 bits) | +----------------------------------------------+ | time to live (TTL) (2 octets) | +----------------------------------------------+ Each LLDPDU must contain one and only one Time To Live TLV. |
Mandatory |
Port Description (Type = 4) |
This TLV identifies the description of the local device port. If the device supports IETF RFC 2863, the value of this TLV must be the same as the value of the ifDescr leaf node in the iftable entry defined in RFC 2863. An LLDPDU can contain only one Port Description TLV. The format of the TLV is as follows: +----------------------------------------------+ | TLV type = 4 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | port description (0 < n < 255 octets) | +----------------------------------------------+ |
Optional |
System Name (Type = 5) |
This TLV indicates the complete domain name of the local device. If the device supports IETF RFC 3418, the value of this TLV must be the same as the value of sysName in RFC 3418. An LLDPDU can contain only one System Name TLV. The format of the TLV is as follows: +----------------------------------------------+ | TLV type = 5 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | system name (0 < n < 255 octets) | +----------------------------------------------+ |
Optional |
System Description (Type = 6) |
This TLV indicates the full name of the local device, system hardware version, operating system, network software, and so on. If the device supports IETF RFC 3418, the value of this TLV must be the same as the value of sysDesc in RFC 3418. An LLDPDU can contain only one System Description TLV. The format of the TLV is as follows: +----------------------------------------------+ | TLV type = 6 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | system description (0 < n < 255 octets) | +----------------------------------------------+ |
Optional |
System Capabilities (Type = 7) |
This TLV indicates the functions supported by the device and the functions that are enabled on the device. If the enabled functions listed in the TLV are not supported by the system, the TLV is considered incorrect and discarded. The format of the TLV is as follows: +----------------------------------------------+ | TLV type = 7 (7 bits) | +----------------------------------------------+ | TLV information string length = 4 (9 bits) | +----------------------------------------------+ | system capabilities (2 octets) | +----------------------------------------------+ | enabled capabilities (2 octets) | +----------------------------------------------+ System functions and corresponding flags are as follows: Bit Capability Reference 1 Other - 2 Repeater IETF RFC 2108 3 MAC Bridge IEEE Std 802.1D 4 WLAN Access Point IEEE Std 802.11 MIB 5 Router IETF RFC 1812 6 Telephone IETF RFC 4293 7 DOCSIS cable device IETF RFC 4639 and IETF RFC 4546 8 Station Only IETF RFC 4293 9 C-VLAN Component IEEE Std 802.1Q 10 S-VLAN Component IEEE Std 802.1Q 11 Two-port MAC Relay (TPMR) IEEE Std 802.1Q 12–16 Reserved - |
Optional |
Management Address (Type = 8) |
This TLV indicates the management address, interface number, and object identifier (OID). The format of the TLV is as follows: +----------------------------------------------+ | TLV type= 8 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | management address string length (1 octet) | +----------------------------------------------+ | management address subtype (1 octet) | +----------------------------------------------+ | management address ( 1-31 octets) | +----------------------------------------------+ | interface numbering subtype (1 octet) | +----------------------------------------------+ | interface number (4 octets) | +----------------------------------------------+ | OID string length (1 octet) | +----------------------------------------------+ | object identifier (0-128 octets) | +----------------------------------------------+ |
Optional |
Organizationally Specific TLV Format
This type of TLV allows different organizations, such as IEEE 802.1, IEEE 802.3, and IETF, or software or device vendors to define TLVs.
Figure 1-62 shows the format of this type of TLV.
Table 1-32 lists the TLVs defined by IEEE 802.1.
Table 1-33 lists the TLVs defined by IEEE 802.3.
+----------------------------------------------+ | TLV type= 127 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | organizationally unique identifier (OUI) | | (3 octets) | +----------------------------------------------+ | organizationally defined subtype (1 octet) | +----------------------------------------------+ | organizationally defined information string | | (0 <= n <= 507 octets) | +----------------------------------------------+
Field |
Length |
Description |
---|---|---|
TLV type |
7 bits |
This field indicates the TLV type. The value is fixed as 127. All organizationally specific TLVs use this value. |
TLV information string length |
9 bits |
This field indicates the length (in bytes) of the TLV information string. |
organizationally unique identifier (OUI) |
3 bytes |
This field indicates the organizationally unique identifier (OUI). Section 9 of the IEEE Std 802 standard defines the OUI. |
organizationally defined subtype |
1 byte |
This field indicates the organizationally defined TLV subtype. |
organizationally defined information string |
0–507 bytes |
This field indicates the information string of the organization-defined TLV. |
TLVs Defined by IEEE 802.1
IEEE 802.1 Subtype |
TLV Name |
Description |
---|---|---|
0x01 |
Port VLAN ID |
This TLV is an optional fixed-length TLV that allows a VLAN bridge port to advertise its port VLAN ID (PVID) in untagged frames or frames with priority values (see section 8.4.4 in IEEE 802.1Q-2005). The format of the TLV is as follows: +----------------------------------------------+ | TLV type= 127 (7 bits) | +----------------------------------------------+ | TLV information string length = 6 (9 bits) | +----------------------------------------------+ | 802.1OUI = 0x00-80-C2 (3 octets) | +----------------------------------------------+ | 802.1 subtype = 1 (1 octet) | +----------------------------------------------+ | port VLAN identifier (PVID) (2 octets) | +----------------------------------------------+ The port VLAN identifier field is the VLAN ID of the bridge port defined in section 8.4.4 of the IEEE Std 802.1Q-2005 standard. If a device does not know the PVID or does not support port-based VLAN operations, the value of this field is 0. |
0x02 |
Port And Protocol VLAN ID |
This optional TLV indicates the protocol VLAN ID of the port. The format of the TLV is as follows: +----------------------------------------------+ | TLV type= 127 (7 bits) | +----------------------------------------------+ | TLV information string length = 7 (9 bits) | +----------------------------------------------+ | 802.1OUI = 0x00-80-C2 (3 octets) | +----------------------------------------------+ | 802.1 subtype = 2 (1 octet) | +----------------------------------------------+ | flags (1 octet) | +----------------------------------------------+ | port and protocol VLAN identifier (PPVID) | | (2 octets) | +----------------------------------------------+ Meanings of bits in the flags field are as follows: Bit Function Value/meaning 1 Port and protocol VLAN supported 1 = supported 0 = not supported 2 Port and protocol VLAN enabled 1 = enabled 0 = not enabled 3–8 Reserved for future standardization Set to zero |
0x03 |
VLAN Name |
This optional TLV indicates the name of the device port VLAN. The format of the TLV is as follows: +----------------------------------------------+ | TLV type= 127 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | 802.1OUI = 0x00-80-C2 (3 octets) | +----------------------------------------------+ | 802.1 subtype = 3 (1 octet) | +----------------------------------------------+ | VLAN ID (2 octets) | +----------------------------------------------+ | VLAN name length (1 octet) | +----------------------------------------------+ | VLAN name (0-32 octets) | +----------------------------------------------+ If multiple VLAN Name TLVs are defined for a port, the combination of the VLAN ID and the corresponding VLAN name must be unique. The VLAN ID field refers to the VLAN ID corresponding to the VLAN name. The VLAN name length field indicates the length of the VLAN name, in bytes. If the length of the VLAN name is 0, no VLAN name is configured. If a device supports IETF RFC 4363, the VLAN name is set to the dot1QVLANStaticName object. |
0x04 |
Protocol Identity |
This optional TLV identifies the protocol type supported by the device port. The format of the TLV is as follows: +----------------------------------------------+ | TLV type= 127 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | 802.1OUI = 0x00-80-C2 (3 octets) | +----------------------------------------------+ | 802.1 subtype = 4 (1 octet) | +----------------------------------------------+ | protocol identity length (1 octet) | +----------------------------------------------+ | protocol identity ( <= 255 octets) | +----------------------------------------------+ |
0x05 |
VID Usage Digest |
This optional TLV identifies the VID usage summary of the device. The format of the TLV is as follows: +----------------------------------------------+ | TLV type= 127 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | 802.1OUI = 0x00-80-C2 (3 octets) | +----------------------------------------------+ | 802.1 subtype = 5 (1 octet) | +----------------------------------------------+ | VID usage digest (4 octets) | +----------------------------------------------+ |
0x06 |
Management VID |
This optional TLV indicates the management VLAN ID of the device. The format of the TLV is as follows: +----------------------------------------------+ | TLV type= 127 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | 802.1OUI = 0x00-80-C2 (3 octets) | +----------------------------------------------+ | 802.1 subtype = 6 (1 octet) | +----------------------------------------------+ | Management ID (2 octets) | +----------------------------------------------+ If the device does not have a management VID, set this value to 0. |
0x07 |
Link Aggregation |
This TLV indicates the link aggregation capability and enabling status of a port. The format of the TLV is as follows: +----------------------------------------------+ | TLV type= 127 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | 802.1OUI = 0x00-80-C2 (3 octets) | +----------------------------------------------+ | 802.1 subtype = 7 (1 octet) | +----------------------------------------------+ | aggregation status (1 octet) | +----------------------------------------------+ | aggregated port ID (4 octets) | +----------------------------------------------+ The meanings of the bits in the link aggregation status field are as follows:
|
0x08 - 0xFF |
Reserved |
- |
TLVs Defined by IEEE 802.3
IEEE 802.3 Subtype |
TLV Name |
Description |
---|---|---|
1 |
MAC/PHY Configuration/Status |
This optional TLV identifies the following:
The format of the TLV is as follows: +----------------------------------------------+ | TLV type= 127 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | 802.1OUI = 0x00-12-0F (3 octets) | +----------------------------------------------+ | 802.3 subtype = 1 (1 octet) | +----------------------------------------------+ | auto-negotiation support/status (1 octet) | +----------------------------------------------+ | PMD auto-negotiation advertised capability | | (2 octets) | +----------------------------------------------+ | operational MAU type (2 octets) | +----------------------------------------------+ The meanings of the bits in the auto-negotiation support/status field are as follows: Bit Function Value/Meaning IETF RFC 4836 Reference 0 Auto-negotiation support 1 = supported 0 = not supported ifMauAutoNegSupported 1 Auto-negotiation status 1 = enabled 0 = not enabled ifMauAutoNegAdminStatus 2–7 - Reserved - The PMD auto-negotiation advertised capability field uses the BITS pseudotype encoding mode. 0 is the most significant bit (leftmost) of the byte. The operational MAU type field is an integer that identifies the MAU type of the sending device. This value is set to the location corresponding to dot3MauType in IETF RFC 4836 or later versions, or set to the last number corresponding to dot3MauType OID. |
2 |
Power Via Medium Dependent Interface (MDI) |
This TLV allows an NMS to advertise and discover the port power supply capability of the sending device. IEEE 802.3 defines three implementations: 10BASE-T, 100BASE-TX, and 1000BASE-T. The format of the TLV is as follows: +----------------------------------------------+ | TLV type= 127 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | 802.1OUI = 0x00-12-0F (3 octets) | +----------------------------------------------+ | 802.3 subtype = 2 (1 octet) | +----------------------------------------------+ | MDI power support (1 octet) | +----------------------------------------------+ | PSE power pair (1 octet) | +----------------------------------------------+ | power class (1 octet) | +----------------------------------------------+ The meanings of the bits in the MDI power support field are as follows: Bit Meaning Value/Meaning IETF RFC 3621 Object 0 Port class 1 = PSE 0 = PD 1 Power Sourcing 1 = supported Equipment (PSE) 0 = not supported MDI power support 2 PSE MDI power state 1 = enabled 0 = disabled pethPsePortAdminEnable 3 PSE pairs control 1 = pair selection ability can be controlled 0 = pair selection pethPsePortPowerPairContolAbility can not be controlled 4–7 - Reserved - The PSE power pair field is an integer and is set to the pethPsePortPowerPairs object in IETF RFC 3621. The power class field is also an integer and is set to the pethPsePortPowerClassifications object in IETF RFC 3621. |
3 |
Link Aggregation (deprecated) |
N/A |
4 |
Maximum Frame Size |
This TLV indicates the maximum transmission unit (MTU) value configured for a port. The format of the TLV is as follows: +----------------------------------------------+ | TLV type= 127 (7 bits) | +----------------------------------------------+ | TLV information string length (9 bits) | +----------------------------------------------+ | 802.1OUI = 0x00-12-0F (3 octets) | +----------------------------------------------+ | 802.3 subtype = 4 (1 octet) | +----------------------------------------------+ | maximum 802.3 frame size (2 octets) | +----------------------------------------------+ The value of this TLV is an integer, indicating the maximum frame length (in bytes) supported by a port.
|
5–255 |
Reserved |
- |
Frame Example
Frame 1: 331 bytes on wire (2648 bits), 331 bytes captured (2648 bits) Arrival Time: Jan 1, 1970 08:00:00.018129000 Epoch Time: 0.018129000 seconds [Time delta from previous captured frame: 0.000000000 seconds] [Time delta from previous displayed frame: 0.000000000 seconds] [Time since reference or first frame: 0.000000000 seconds] Frame Number: 1 Frame Length: 331 bytes (2648 bits) Capture Length: 331 bytes (2648 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:lldp] [Coloring Rule Name: Broadcast] [Coloring Rule String: eth[0] & 1]
Ethernet II, Src: 12:34:43:21:12:34 (12:34:43:21:12:34), Dst: LLDP_Multicast (01:80:c2:00:00:0e) Destination: LLDP_Multicast (01:80:c2:00:00:0e) Address: LLDP_Multicast (01:80:c2:00:00:0e) .... ...1 .... .... .... .... = IG bit: Group address (multicast/broadcast) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) Source: 12:34:43:21:12:34 (12:34:43:21:12:34) Address: 12:34:43:21:12:34 (12:34:43:21:12:34) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) .... ..1. .... .... .... .... = LG bit: Locally administered address (this is NOT the factory default) Type: 802.1 Link Layer Discovery Protocol (LLDP) (0x88cc)
Link Layer Discovery Protocol Chassis Subtype = MAC address, Id: 12:34:43:21:12:34 0000 001. .... .... = TLV Type: Chassis Id (1) .... ...0 0000 0111 = TLV Length: 7 Chassis Id Subtype: MAC address (4) Chassis Id: 12:34:43:21:12:34 (12:34:43:21:12:34) Port Subtype = Interface name, Id: GigabitEthernet1/1/9 0000 010. .... .... = TLV Type: Port Id (2) .... ...0 0001 0101 = TLV Length: 21 Port Id Subtype: Interface name (5) Port Id: GigabitEthernet1/1/9 Time To Live = 120 sec 0000 011. .... .... = TLV Type: Time to Live (3) .... ...0 0000 0010 = TLV Length: 2 Seconds: 120 System Name = R4 0000 101. .... .... = TLV Type: System Name (5) .... ...0 0000 0010 = TLV Length: 2 System Name = R4 System Description = Huawei Versatile Routing Platform Software\r\nVRP (R) software, Version 5.70 (NE40E&80E V600R001C00SPCe00)\r\nCopyright (C) 2000-2011 Huawei Technologies Co., Ltd.\r\nHUAWEI NE40E \r\n 0000 110. .... .... = TLV Type: System Description (6) .... ...0 1011 0000 = TLV Length: 176 System Description = Huawei Versatile Routing Platform Software\r\nVRP (R) software, Version 5.70 (NE40E&80E V600R001C00SPCe00)\r\nCopyright (C) 2000-2011 Huawei Technologies Co., Ltd.\r\nHUAWEI NE40E \r\n Port Description = HUAWEI, Quidway Series, GigabitEthernet1/1/9 Interface 0000 100. .... .... = TLV Type: Port Description (4) .... ...0 0011 0110 = TLV Length: 54 Port Description: HUAWEI, Quidway Series, GigabitEthernet1/1/9 Interface Capabilities 0000 111. .... .... = TLV Type: System Capabilities (7) .... ...0 0000 0100 = TLV Length: 4 Capabilities: 0x0004 .... .... .... .1.. = Bridge Enabled Capabilities: 0x0004 .... .... .... .1.. = Bridge Management Address 0001 000. .... .... = TLV Type: Management Address (8) .... ...0 0001 1101 = TLV Length: 29 Address String Length: 5 Address Subtype: IPv4 (1) Management Address: 10.254.161.11 (10.254.161.11) Interface Subtype: ifIndex (2) Interface Number: 6016 OID String Length: 18 Object Identifier: 060f2b060104018f5b051929010201010100 End of LLDPDU 0000 000. .... .... = TLV Type: End of LLDPDU (0) .... ...0 0000 0000 = TLV Length: 0
Reference
Standard |
Description |
---|---|
IEEE Standard for Local and Metropolitan Area Networks: Station and Media Access Control Connectivity Discovery |