
Configuring Security, Quality, and Network Features
Configuring VLAN Settings
Cisco Small Business SPA300 Series, SPA500 Series, and WIP310 IP Phone Administration Guide
161
5
LLDP-MED Capabilities TLV
For the outgoing LLDPDU, the TLV should have the device type 3 (End Point Class
III) and with the following bits set for 2-octet Capability field:
For the incoming TLV, if the LLDP-MED TLV is not present, the LLDPDU is
discarded. The LLDP-MED Capabilities TLV is mandatory and only one is allowed
for the outgoing and incoming LLDPDUs. Any other LLDP-MED TLVs will be
ignored if they present before the LLDP-MED Capabilities TLV.
Network Policy TLV
Outgoing LLDPDU—The phone will send out only one Network Policy TLV with the
Application Type Value set to 1 (Voice). Before the VLAN or DSCP is determined,
the Unknown Policy Flag (U) is set to 1. If the VLAN setting or DSCP is known, the
value is set to 0. When the policy is unknown, all other values are set to 0. Before
the VLAN is determined or used, the Tagged Flag (T) is set to 0. If the tagged VLAN
(VLAN ID > 1) is used for the phone, the Tagged Flag (T) is set to 1. Reserved (X) is
always set to 0. If the VLAN is used, the corresponding VLAN ID and L2 Priority will
be set accordingly. VLAN ID valid value is range from 1-4094. However, VLAN ID=1
will never be used (limitation). If DSCP is used, the value range from 0-63 is set
accordingly.
Incoming LLDPDU—Multiple Network Policy TLVs for different application types
are allowed. The phone will only support and interpret the TLV with the application
type=1 (Voice). TLVs for other application types are ignored and not validated.
Bit Position
Capability
0
LLDP-MED Capabilities
1
Network Policy
4
Extended Power via MDI-PD
5
Inventory