Connectivity Guide

Table 13. Service tag TLV (Type – 127, OUI – 0xF8-0xB1-0x56)
TLV Subtype Description
Service tag 21 Indicates the service tag associated with the
device.
Table 14. Solution ID TLVs (Type – 127, OUI – 0xF8-0xB1-0x56)
TLV Subtype Description
Product base 22 Indicates the product base.
Product serial number 23 Indicates the product serial number.
Product part number 24 Indicates the product part number.
Media endpoint discovery
LLDP-MED provides additional organizationally-specic TLVs to allow endpoint devices and network-connectivity devices to advertise their
characteristics and conguration information.
LLDP-MED devices are located at the IEEE 802 LAN network edge and participate in IP communication service using the LLDP-MED
framework, such as IP phones and conference bridges. LLDP-MED network connectivity devices provide access to the IEEE 802-based
LAN infrastructure for LLDP-MED endpoint devices, such as IP phones. An OS10 device acts as an LLDP-MED network connectivity
device.
LLDP-MED provides network connectivity devices to:
• Manage inventory
• Manage power over ethernet (PoE)
• Identify physical location
• Identify network policy
NOTE
: Only the Rx function is supported for managing PoE and identifying the physical location. LLDP-MED is designed for but
not limited to VoIP endpoints.
Network connectivity device
OS10 acts as an LLDP-MED network-connectivity device (Type 4). Network connectivity devices transmit an LLDP-MED capability TLV to
endpoint devices and stores information that endpoint devices advertise.
127/1 — LLDP-MED
capabilities
• If the transmitting device supports LLDP-MED
• What LLDP-MED TLVs are supported
• LLDP device class
127/2 — Network
policy
Application type, VLAN ID, L2 priority, and DSCP value.
127/3 — Local
identication
Physical location of the device expressed in one of three formats:
• Coordinate-based LCI
292 Layer 2