Managing Network Datalinks in Oracle® Solaris 11.2

Exit Print View

Updated: September 2014
 
 

Components of an LLDP Implementation

    LLDP is implemented with the following components:

  • LLDP package – You install this package to enable the LLDP. This package includes the LLDP daemon, command-line utilities, the service manifest and scripts, and other components that are required for LLDP to operate.

  • LLDP service – You can enable the LLDP service by using the svcadm command. This service uses the fault management resource identifier (FMRI) of the service management facility (SMF) service instance, svc:/network/lldp:default, to manage the LLDP daemon, lldpd. This LLDP service is responsible for starting, stopping, restarting, or refreshing the lldpd daemon. This service is automatically enabled after you install the LLDP package.

  • lldpadm command – You can use this command to administer LLDP on individual links and to configure the operating mode of LLDP, to specify TLV units that are transmitted, and to configure DCBX TLV units. For information about TLV units, see Information the LLDP Agent Advertises.

    You must use this command to set the per-agent LLDP properties and global LLDP properties and to get LLDP information for a specific agent or its peer.

    The lldpadm subcommands are described in the following sections. For more information about the lldpadm command, see the lldpadm (1M) man page.

  • LLDP daemon – The LLDP services manage LLDP agents on the system. They also interact with snmpd, the daemon for the Simple Network Management Protocol (SNMP), to retrieve LLDP information that is received on the system through SNMP.

  • LLDP agents – LLDP agents are the LLDP instances that are associated with a physical datalink on which LLDP is enabled. LLDP agents transmit information about the datalink to its peer and also receive information from the peer. You can configure an LLDP agent to advertise specific information about the associated physical datalink. You can enable LLDP only on physical datalinks.