Supported TLVs in LLDP
Table of Contents
10.1
Expand all | Collapse all
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
Supported TLVs in LLDP
LLDPDUs include mandatory and optional TLVs. The following
table lists the mandatory TLVs that the firewall supports:
Mandatory TLVs | TLV Type | Description |
|---|---|---|
Chassis ID TLV | 1 | Identifies the firewall chassis. Each firewall
must have exactly one unique Chassis ID. The Chassis ID subtype
is 4 (MAC address) on Palo Alto Networks ® models will
use the MAC address of Eth0 to ensure uniqueness. |
Port ID TLV | 2 | Identifies the port from which the LLDPDU
is sent. Each firewall uses one Port ID for each LLDPDU message
transmitted. The Port ID subtype is 5 (interface name) and uniquely
identifies the transmitting port. The firewall uses the interface’s
ifname as the Port ID. |
Time-to-live (TTL) TLV | 3 | Specifies how long (in seconds) LLDPDU information
received from the peer is retained as valid in the local firewall
(range is 0-65,535). The value is a multiple of the LLDP Hold Time
Multiplier. When the TTL value is 0, the information associated
with the device is no longer valid and the firewall removes that
entry from the MIB. |
End of LLDPDU TLV | 0 | Indicates the end of the TLVs in the LLDP
Ethernet frame. |
The following table lists the optional TLVs that the Palo Alto
Networks firewall supports:
Optional TLVs | TLV Type | Purpose and Notes
Regarding Firewall Implementation |
|---|---|---|
Port Description TLV | 4 | Describes the port of the firewall in alpha-numeric
format. The ifAlias object is used. |
System Name TLV | 5 | Configured name of the firewall in alpha-numeric
format. The sysName object is used. |
System Description TLV | 6 | Describes the firewall in alpha-numeric
format. The sysDescr object is used. |
System Capabilities | 7 | Describes the deployment mode of the interface,
as follows:
|
Management Address | 8 | One or more IP addresses used for firewall
management, as follows:
If
no management IP address is provided, the default is the MAC address
of the transmitting interface. Included is the interface number
of the management address specified. Also included is the OID of
the hardware interface with the management address specified (if
applicable). If more than one management address is specified,
they will be sent in the order they are specified, starting at the
top of the list. A maximum of four Management Addresses are supported. This
is an optional parameter and can be left disabled. |