Management and Configuration Guide K/KA/KB.15.15

<port-list>
int <port-list> qos priority 0 - 7
vlan vid qos dscp codepoint
NOTE: A codepoint must have an 802.1p priority before you can configure it for use in prioritizing
packets by VLAN-ID. If a codepoint you want to use shows No Override in the Priority column
of the DSCP policy table (display with show qos-dscp map, then use qos-dscp map
codepoint priority 0 - 7 to configure a priority before proceeding.
For more information on this topic, see the Advanced Traffic Management Guide.
PoE advertisements
These advertisements inform an LLDP-MED endpoint of the power (PoE) configuration on switch
ports. Similar advertisements from an LLDP-MED endpoint inform the switch of the endpoint's power
needs and provide information that can be used to identify power priority mismatches.
PoE TLVs include the following power data:
Power type Indicates whether the device is a power-sourcing entity (PSE) or a PD. Ports
on the J8702A PoE zl module are PSE devices. A MED-capable VoIP
telephone is a PD.
Power source Indicates the source of power in use by the device. Power sources for PDs
include PSE, local (internal), and PSE/local. The switches advertise
unknown.
Power priority Indicates the power priority configured on the switch (PSE) port or the power
priority configured on the MED-capable endpoint.
Power value Indicates the total power in watts that a switch port (PSE) can deliver at a
particular time, or the total power in watts that the MED endpoint (PD)
requires to operate.
Location data for LLDP-MED devices
You can configure a switch port to advertise location data for the switch itself, the physical wall-jack
location of the endpoint (recommended), or the location of a DHCP server supporting the switch,
endpoint, or both. You also have the option of configuring these different address types:
Civic address Physical address data such as city, street number, and
building information.
ELIN (Emergency Location
Identification Number)
An emergency number typically assigned to MLTS (Multiline
Telephone System) Operators in North America.
Coordinate-based location Attitude, longitude, and altitude information (Requires
configuration via an SNMP application.)
Configuring coordinate-based locations
Latitude, longitude, and altitude data can be configured per switch port using an SNMP management
application. For more information, see the documentation provided with the application. A further
source of information on this topic is the RFC 3825: Dynamic Host Configuration Protocol Option
for Coordinate-based Location Configuration Information.
NOTE: Endpoint use of data from a medPortLocation TLV sent by the switch is device-dependent.
See the documentation provided with the endpoint device.
The code assignments in the following table are examples from a work-in-progress (the internet
draft titled "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses
Configuration Information draft-ietf-geopriv-dhcp-civil-06" dated May 30, 2005.) For the actual
Advertising device capability, network policy, PoE status and location data 261