Falcon R-Class | User Guide
226
It should be noted that LLDP-MED is not intended to run on links other than between Network
Connectivity Devices and Endpoints, and therefore does not need to advertise the multitude of
network policies that frequently run on an aggregated link interior to the LAN.
Delete
Check to delete the policy. It will be deleted during the next save.
Policy ID
ID for the policy. This is auto generated and shall be used when selecting the
polices that shall be mapped to the specific interfaces
Application
Type
Intended use of the application types:
1.
Voice
- for use by dedicated IP Telephony handsets and other similar
appliances supporting interactive voice services. These devices are typically
deployed on a separate VLAN for ease of deployment and enhanced security by
isolation from data applications.
2.
Voice Signaling
(conditional) - for use in network topologies that require a
different policy for the voice signaling than for the voice media. This application
type should not be advertised if all the same network policies apply as those
advertised in the
Voice
application policy.
3.
Guest Voice
- support a separate 'limited feature-set' voice service for guest
users and visitors with their own IP Telephony handsets and other similar
appliances supporting interactive voice services.
4.
Guest Voice Signaling
(conditional) - for use in network topologies that require
a different policy for the guest voice signaling than for the guest voice media.
This application type should not be advertised if all the same network policies
apply as those advertised in the
Guest Voice
application policy.
5.
Softphone Voice
- for use by softphone applications on typical data centric
devices, such as PCs or laptops. This class of endpoints frequently does not
support multiple VLANs, if at all, and are typically configured to use an 'untagged'
VLAN
or
a
single
'tagged'
data
specific
VLAN.
When a network policy is defined for use with an 'untagged' VLAN (see Tagged
flag below), then the L2 priority field is ignored and only the DSCP value has
relevance.
6.
Video Conferencing
- for use by dedicated Video Conferencing equipment and
other similar appliances supporting real-time interactive video/audio services.
7.
Streaming
Video - for use by broadcast or multicast-based video content
distribution and other similar applications supporting streaming video services
that require specific network policy treatment. Video applications relying on TCP
with buffering would not be an intended use of this application type.
8.
Video Signaling
(conditional) - for use in network topologies that require a
separate policy for the video signaling than for the video media. This application
type should not be advertised if all the same network policies apply as those
advertised in the
Video Conferencing
application policy.
Tag
Tag
indicating whether the specified application type is using a 'tagged' or an
'untagged' VLAN.
Untagged
indicates that the device is using an untagged frame format and as
such does not include a tag header as defined by IEEE 802.1Q-2003. In this case,
both the VLAN ID and the Layer 2 priority fields are ignored and only the DSCP
value has relevance.
Содержание Falcon-RX/812/G/A
Страница 1: ...Falcon R Class User Guide Falcon RX Software version 8 0 20 www fibrolan com...
Страница 11: ...Falcon R Class User Guide 11 2 System Description 2 1 Block Diagram Figure 2 1 R Class functional block diagram...
Страница 86: ...Falcon R Class User Guide 86 Web GUI Configuration QoS DSCP Translation Figure 4 58 DSCP Translation...
Страница 221: ...Falcon R Class User Guide 221 Web GUI Configuration LLDP LLDP MED Figure 4 162 LLDP MED Configuration displays...
