JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Administration: Network Interfaces and Network Virtualization     Oracle Solaris 11 Information Library
search filter icon
search icon

Document Information


1.  Overview of the Networking Stack

Network Configuration in This Oracle Solaris Release

The Network Stack in Oracle Solaris

Network Devices and Datalink Names

Administration of Other Link Types

Part I Network Auto-Magic

2.  Introduction to NWAM

3.  NWAM Configuration and Administration (Overview)

4.  NWAM Profile Configuration (Tasks)

5.  NWAM Profile Administration (Tasks)

6.  About the NWAM Graphical User Interface

Part II Datalink and Interface Configuration

7.  Using Datalink and Interface Configuration Commands on Profiles

8.  Datalink Configuration and Administration

9.  Configuring an IP Interface

10.  Configuring Wireless Interface Communications on Oracle Solaris

11.  Administering Bridges

12.  Administering Link Aggregations

13.  Administering VLANs

14.  Introducing IPMP

15.  Administering IPMP

16.  Exchanging Network Connectivity Information With LLDP

Overview of LLDP in Oracle Solaris

Components of an LLDP Implementation

Functions of the LLDP Agent

Configuring How the LLDP Agent Operates

How to Enable LLDP

Configuring What Information To Advertise

How to Specify TLV Units for LLDP Packets

Managing TLV Units

How to Define Global TLV Values

Data Center Bridging

How to Set Per-Agent TLV Values

Monitoring LLDP Agents

How to Display Advertisements

How to Display LLDP Statistics

Part III Network Virtualization and Resource Management

17.  Introducing Network Virtualization and Resource Control (Overview)

18.  Planning for Network Virtualization and Resource Control

19.  Configuring Virtual Networks (Tasks)

20.  Using Link Protection in Virtualized Environments

21.  Managing Network Resources

22.  Monitoring Network Traffic and Resource Usage



Managing TLV Units

Each TLV unit has properties that you can further configure with specific values. When that TLV unit is enabled as an LLDP agent's property, then that TLV unit is advertised in the network only with the specified values. Consider, for example, the TLV value syscapab which advertises a system's capabilities. These capabilities can potentially include support for routers, bridges, repeaters, telephones, and other devices. However, you can set syscapab so that only those capabilities that are actually supported in your specific system, such as routers and bridges, are advertised.

The procedure for managing TLVs depends on whether you are configuring global TLVs or per-agent TLVs.

Global TLVs apply to all the LLDP agents on the system. The following table displays the global TLV values and their corresponding possible configurations.

Table 16-2 Global TLVs and Their Properties

TLV Name
TLV Property Name
Possible Property Values
Value Description
other, repeater, bridge, wlan-ap, router, telephone, docsis-cd, station, cvlan, sylvan, tpmr
Represent the primary supported functions of the system. Default values are router, station, and bridge.
Subset of the values listed for supported
Represents the enabled functions of the system.
ipv4 or ipv6
Specifies the type of IP addresses that will be associated with the local LLDP agent. The addresses will be used to reach higher layer entities and will assist in discovery by network management. Only one type can be specified.

TLV units that cannot have global values are managed at the LLDP agent level. With per-agent TLV units, the values that you provide are used when the TLV unit is enabled for transmission by a specific LLDP agent.

The following table displays the TLV values and their corresponding possible configurations for an LLDP agent.

Table 16-3 Per-Agent TLV Units and Their Properties

TLV Name
TLV Property Name
Possible Property Values
Value Description
on, off
Sets an LLDP agent to accept or reject configuration information from a remote machine.
Values are taken from the information that is defined in the Application Priority Table.
Configures the Application Priority Table. This table contains the list of application TLV units and their corresponding priorities. The application is identified by the id/selector pair. The contents of the table use the following format:


The following procedure shows how to define global TLV values. For a discussion about how to define per-agent TLV units, see Data Center Bridging.

How to Define Global TLV Values

This procedure shows how to provide global values for specific TLV units. To set global TLV values, you use the llpadm set-tlvprop subcommand.

  1. Configure the appropriate TLV property to contain the values that you want to advertise.

    For reference, see Table 16-2.

    # lldpadm set-tlvprop -p tlv-property=value[,value,value,...] tlv
  2. (Optional) Display the values of the property that you have just configured.
    # lldpadm show-tlvprop

Example 16-3 Specifying the System's Capabilities and the Management IP Address

This example accomplishes two objectives:

# llpdadm set-tlvprop -p supported=bridge,router,repeater syscapab
# llpdadm set-tlvprop -p enabled=router syscapab
# llpdadm set-tlvprop -p ipaddr= mgmtaddr
# llpdadm show-tlvprop
syscapab   supported  rw    bridge,      bridge,router,  other,router,
                            router,      station         repeater,bridge,
                            repeater                     wlan-ap,telephone,
syscapab   enabled    rw    router       none            bridge,router,
mgmtaddr   ipaddr     rw  none            --

Data Center Bridging

To support Fibre Channel over Ethernet (FCoE) traffic, the LLDP implementation in Oracle Solaris includes data center bridging (DCB) support.

In networks that use traditional Ethernet for traffic exchange, an ongoing risk is that packets might be dropped when the network is busy. A key requirement for FCoE traffic is that no packet drops can occur during transmission. With support for Data Center Bridging Exchange (DCBx), the priority—based flow control (PFC) TLV, and the Application TLV, dropped packets are avoided.

PFC extends the standard PAUSE frame to include the priority information for packets. Typically, a PAUSE frame is sent on a link when traffic is heavy to enable the receiving end to process packets it has already received. With PFC, instead of transmitting a PAUSE frame to stop all traffic on the link, traffic is paused according to priorities defined for the packets. A PFC frame can be sent for the priority for which traffic needs to be paused. The sender stops traffic for that specific priority, while traffic for other priorities are unaffected. After a specified time, another PFC frame is sent to signal that the paused traffic can resume.

PFC configuration information is exchanged between peer stations by means of DCBx. If peers in a traffic exchange have matching PFC configurations, then PFC can pause or resume traffic transmission as needed. To enable different packets to be assigned different priorities, the Application TLV is used to define priority information. If peers have mismatching PFC configurations, the PFC TLV can be customized to accept the other peer's configuration, as shown in the procedure that follows.

Data Center Bridging is a specific case to illustrate how to configure per-agent TLV units as explained in Managing TLV Units.

How to Set Per-Agent TLV Values

This procedure shows how to set TLV values at the LLDP agent level by using the llpadm set-agenttlvprop subcommand.

  1. Configure the appropriate TLV property to contain the values that you want to advertise by a given LLDP agent.

    For reference, see Table 16-3.

    # lldpadm set-agenttlvprop -p tlv-property[+|-]=value[,value,value,...] -a agent tlv-name
  2. (Optional) Display the values of the property that you have just configured.
    # lldpadm show-agenttlvprop

Example 16-4 Enabling the LLDP Agent to Accept Information and Specifying TLV Application Priorities

This example shows how the pfc as well as the appln TLV values are customized. The TLV units in this example specify how DCB operates for FCoE traffic. The system is configured to accept the peer's PFC configuration in case the local configuration does not match the peer's configuration. The example also shows how the priority is set for the LLDP agent's application TLV.

# lldpadm set-agenttlvprop -p willing=on -a net0 pfc
# lldpadm set-agenttlvprop -p apt=8906/1/4 -a net0 appln
# lldpadm show-agenttlvprop
net0    pfc       willing    rw     on         off       on,off
net0    appln     apt        rw     8906/1/4   --        --