User`s manual

MediaPack SIP
MediaPack SIP User’s Manual 196 Document #: LTRT-65405
9.6 VLANS and Multiple IPs
9.6.1 Multiple IPs
Media, Control and Management (OAM) traffic in the MediaPack can be separated into three
dedicated networks. Instead of a single IP address, the MediaPack can be assigned three IP
addresses and subnet masks, each relates to a different traffic type. This architecture enables
users to integrate the MediaPack into a three-network environment that is focused on security
and segregation. Each entity in the MediaPack (e.g., Web, RTP) is mapped to a single traffic type
(according to Table
9-1 on page 197) in which it operates.
Refer to the following notes:
• In the current version, a default gateway is only supported for the Media traffic type; for the
other two, use the IP Routing table.
• The IP address and subnet mask used in the Single IP Network mode are carried over to the
OAM traffic type in the Multiple IP Network mode.
For detailed information on integrating the MediaPack into a VLAN and multiple IPs network, refer
to Section
9.6.3 on page 197. For detailed information on configuring the multiple IP parameters,
refer to Section
5.6.1.1 on page 114.
9.6.2 IEEE 802.1p/Q (VLANs and Priority)
The Virtual Local Area Network (VLAN) mechanism enables the MediaPack to be integrated into
a VLAN-aware environment that includes switches, routers and endpoints.
When in VLAN-enabled mode, each packet is tagged with values that specify its priority (class-of-
service) (IEEE 802.1p) and the identifier (traffic type) of the VLAN to which it belongs (media,
control or management) (IEEE 802.1Q).
The class-of-service mechanism can be utilized to accomplish Ethernet QoS. Packets sent by the
MediaPack to the Ethernet network are divided into five, different-priority classes (Network,
Premium media, Premium control, Gold and Bronze). The priority of each class is determined by
a corresponding ini file parameter.
Traffic type tagging can be used to implement Layer 2 VLAN security. By discriminating traffic into
separate and independent domains, the information is preserved within the VLAN. Incoming
packets received from an incorrect VLAN are discarded.
For the mapping of an application to its class-of-service and traffic type, refer to Table
9-1 below.
Media traffic type is assigned ‘Premium media’ class of service, Management traffic type is
assigned ‘Bronze’ class of service, and Control traffic type is assigned ‘Premium control’ class of
service.
For example, RTP/RTCP traffic is assigned the Media VLAN ID and ‘Premium media’ class of
service, whereas Web traffic is assigned the Management VLAN ID and ‘Bronze’ class of service.
Each of these parameters can be configured with a 802.1p/q value: traffic type to VLAN ID, and
class of service to 802.1p priority.
Note 1: The VLAN mechanism is activated only when the gateway is loaded from the
flash memory. Therefore, when using BootP:
Load an ini file with ‘VlanMode = 1’ and ‘SaveConfiguration = 1’. Then (after
the gateway is active) reset the gateway using any method except for BootP.
Note 2: The gateway must be connected to a VLAN-aware switch, and the switch’s
PVID must be equal to the gateway’s native VLAN ID.