Link Layer Discovery Protocol (LLDP) Media Endpoint Discovery (MED) Network Policy Configuration on the 200/300 Series Managed Switches

Objective

Link Layer Discovery Protocol (LLDP) is a protocol that allows network managers to troubleshoot and modify network management in multi-vendor environments. LLDP Media Endpoint Discovery (LLDP-MED) provides additional capabilities to support media endpoint devices such as enabling the advertisement of network polices for applications like voice or video, device location discovery, and troubleshooting information. An LLDP-MED network policy is a set of configuration settings for a real-time application such as voice or video. A network policy is included into the outgoing LLDP packets to the attached media endpoint device. The MED then sends its traffic as specified in the network policy it receives. This article explains how to set up an LLDP MED network policy on the 200/300 Series Managed Switches.

Applicable Devices

• SF/SG 200 and SF/SG 300 Series Managed Switches

Software Version

• 1.3.0.62

LLDP MED Network Policy Configuration

Step 1. Log in to the web configuration utility and choose Administration > Discovery - LLDP > LLDP MED Network Policy. The LLDP MED Network Policy page opens:

Step 2. Check the Auto check box in the LLDP-MED Network Policy for Voice Application field if you would like the switch to automatically generate and advertise a network policy for the voice application.

Note: The user may not manually configure a voice network policy when the Auto box is checked.

Step 3. Click Apply to update the current configuration.

Step 4. In order to define a new network policy, click Add. The Add LLDP MED Network Policy window appears.

Step 5. Choose the number of the policy to be created in the Network Policy Number drop-down list.

Step 6. Choose the application type of the network policy in the Application drop-down list. The available options are:

• Voice — To apply the network policy to a voice application.

• Voice Signaling — To apply the network policy to a Voice Signaling application.

• Guest Voice — To apply the network policy to a guest voice application.

• Guest Voice Signaling — To apply the network policy to a guest voice signaling application.

• Softphone Voice — To apply the network policy to a softphone voice application.

• Video Conferencing — To apply the network policy to a video conferencing application.

• Streaming Video — To apply the network policy to a streaming video application.

• Video Signaling — To apply the network policy to a video signaling application.

Step 7. Enter the VLAN to which the traffic should be sent in the VLAN ID field.

Step 8. Click one option to tag the VLAN in the VLAN Tag field. The available options are:

• Tagged — Use this option to pass the VLAN information between different switches via a trunk port.

• Untagged — Use this option if the VLAN is only used locally via an access port.

Step 9. In the User Priority drop-down list, choose the priority applied to traffic defined by this network policy. This value is the Class of Service (CoS) value which has a range from 0 to 7. Each DSCP value treats network traffic as follow:

• 0 — Background.

• 1 — Best effort.

• 2 — Excellent effort.

• 3 — Critical application.

• 4 — Video.

• 5 — Voice.

• 6 — Inter-work control.

• 7 — Network control.

Step 10. In the Differentiated Services Code Point (DSCP) drop-down list, choose the DSCP value that you would like to associate with application data sent by neighbors. This DSCP value is used by the neighbors to mark any application data sent to the switch. DSCP manages and provides proper Quality of Service (QoS) to network traffic.

Step 11. Click Apply to save the configuration.

The image below depicts the changes in the LLDP MED Network Policy page after the configuration.

Steo 12. To edit a LLDP MED Network Policy, check the check box of the policy you wish to edit, and click Edit.

Steo 13. To delete a LLDP MED Network Policy, check the check box of the policy you wish to edit, and click Delete.

Revision History

Revision	Publish Date	Comments
1.0	10-Dec-2018	Initial Release