AudioCodes Mediant Quick start guide

Configuration Note
Multi-Service Business Routers Product Series
Mediant MSBR
Layer 2 Bridging using the CLI
Version 6.8

Version 6.8 3 Mediant MSBR
Configuration Note Contents
Table of Contents
1Introduction .........................................................................................................7
2Layer 2 Switching Interfaces..............................................................................9
2.1 Commands.............................................................................................................9
2.2 Examples .............................................................................................................10
3VLANs ................................................................................................................11
3.1 Commands...........................................................................................................11
3.2 Examples .............................................................................................................12
4Trunk Bridging ..................................................................................................15
4.1 Commands...........................................................................................................15
4.2 Examples .............................................................................................................16
5Port-Monitoring .................................................................................................17
5.1 Commands...........................................................................................................17
5.2 Examples .............................................................................................................18
6Bridge Group Virtual Interface (BVI) Interfaces..............................................21
6.1Commands...........................................................................................................21
6.2 Examples .............................................................................................................22
7802.1p Priority/Layer 2 QoS..............................................................................25
7.1 Commands...........................................................................................................25
7.2 Examples .............................................................................................................25
8QinQ ...................................................................................................................27
8.1 Commands...........................................................................................................27
8.2 Example...............................................................................................................28
9Pseudo Wires ....................................................................................................29
9.1 Connectivity Fault Management (CFM) ................................................................29
9.2 Commands...........................................................................................................29
9.3 Example...............................................................................................................30

Configuration Note 4 Document #: LTRT-31672
Layer 2 Bridging using CLI
This page is intentionally left blank.

Version 6.8 5 Mediant MSBR
Configuration Note Notices
Notice
This document describes the configuration of the Layer 2 bridging provided by AudioCodes
Mediant Multi-Service Business Router (MSBR) series.
Information contained in this document is believed to be accurate and reliable at the time of
printing. However, due to ongoing product improvements and revisions, AudioCodes cannot
guarantee accuracy of printed material after the Date Published nor can it accept responsibility
for errors or omissions. Before consulting this document, check the corresponding Release
Notes regarding feature preconditions and/or specific support in this release. In cases where
there are discrepancies between this document and the Release Notes, the information in the
Release Notes supersedes that in this document. Updates to this document and other
documents as well as software files can be downloaded by registered customers at
http://www.audiocodes.com/downloads.
© Copyright 2016 AudioCodes Ltd. All rights reserved.
This document is subject to change without notice.
Date Published: June-22-2016
Trademarks
AudioCodes, AC, HD VoIP, HD VoIP Sounds Better, IPmedia, Mediant, MediaPack, What’s
Inside Matters, OSN, SmartTAP, VMAS, VoIPerfect, VoIPerfectHD, Your Gateway To
VoIP, 3GX, VocaNOM and CloudBond 365 are trademarks or registered trademarks of
AudioCodes Limited All other products or trademarks are property of their respective
owners. Product specifications are subject to change without notice.
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed
of with unsorted waste. Please contact your local recycling authority for disposal of this
product.
Customer Support
Customer technical support and services are provided by AudioCodes or by an authorized
AudioCodes Service Partner. For more information on how to buy technical support for
AudioCodes products and for contact information, please visit our Web site at
www.audiocodes.com/support.
Abbreviations and Terminology
Each abbreviation, unless widely used, is spelled out in full when first used.
Document Revision Record
LTRT Description
31672 Added Q-in-Q section.

Configuration Note 6 Document #: LTRT-31672
Layer 2 Bridging using CLI
Documentation Feedback
AudioCodes continually strives to produce high quality documentation. If you have any
comments (suggestions or errors) regarding this document, please fill out the
Documentation Feedback form on our Web site at http://www.audiocodes.com/downloads.

Configuration Note 1. Introduction
Version 6.8 7 Mediant MSBR
1 Introduction
This document describes the Layer 2 bridging configuration on the MSBR device.

Configuration Note 8 Document #: LTRT-31672
Layer 2 Bridging using CLI
This page is intentionally left blank.

Configuration Note 2. Layer 2 Switching Interfaces
Version 6.8 9 Mediant MSBR
2 Layer 2 Switching Interfaces
In the MSBR, the Layer 2 switching is hardware-based and uses the host's Media Access
Control (MAC) address from the host's network interface cards (NICs) to decide where to
forward frames. The MAC addresses that the MSBR acquires are used to build a MAC
Address table, also known as a ''CAM Table''. Layer 2 switching interfaces also support
high speed, low latency, and wire speed.
2.1 Commands
The table below describes Layer 2 switching Interface commands.
Table 2-1: Layer 2 Switching Interfaces
Command Description
MSBR# configure data
Enter the data configuration menu.
(config-data)# interface
<physical_interface>
[slot/port.vlanID]
The interface command allows you to enter
a specific interface configuration mode.
<physical_interface> - selects the type of
interface.
[slot/port.vlanID] – slot and port number is
taken from the device panel.
Note: The interface configuration mode
changes after the command is entered.
(conf-if-GE SlotNum/PortNum)#
desc [WORD] Defines a description. It is a recommended
to write a useful and informative interface
description.
(conf-if-GE SlotNum/PortNum)#
duplex [Auto/Half/Full] Configures negotiation duplex on the
interface:
•Auto (default)
•Half
•
Full
(conf-if-GE SlotNum/PortNum)#
speed[10/100/Auto] Configures speed negotiation on the
interface:
•10
•100
•
Auto (default)
(conf-if-GE SlotNum/PortNum)#
shutdown
Disables the interface.

Configuration Note 10 Document #: LTRT-31672
Layer 2 Bridging using CLI
Command Description
(conf-if-GE SlotNum/PortNum)#
spanning-tree [cost/edge/point-
to-point/priority]
Relates to the spanning-tree protocol (STP)
issues on the interface.
•edge – this type of port mode will not
participate on spanning-tree converge
and acts as a port fast port according to
STP.
•cost – sets a cost value for the interface
to be used in calculations of the cost to
the root bridge in STP.
•point-to-point – enables link type point-to-
point to make the link become designated
port.
•priority – local priority number on
interface configuration mode.
MSBR# sh data interface
<physical_interface>
[slot/port.vlanID]
Displays interface statistics, port mode,
speed, duplex and PoE information.
2.2 Examples
This example shows how to configure an interface to access mode and auto-negotiation
100BaseT full permanent:
#interface configured as access mode
MSBR(config-data)# interface gigabitethernet 4/1
MSBR(conf-if-GE 4/1)# duplex full
MSBR(conf-if-GE 4/1)# speed 100
MSBR(conf-if-GE 4/1)# switchport mode access
MSBR(conf-if-GE 4/1)# spanning-tree edge enabled
MSBR(conf-if-GE 4/1)# exit
MSBR(config-data)# interface vlan 200
MSBR(config-data)# interface vlan 300
#interface configured as Trunk mode
MSBR(config-data)# interface gigabitethernet 4/2
MSBR(conf-if-GE 4/2)# switchport mode trunk
MSBR(conf-if-GE 4/2)# switchport native vlan 200 [ All Untagged
packets send to vlan 200]
MSBR(config-data)# interface gigabitethernet 4/3
MSBR(conf-if-GE 4/3)# switchport mode trunk
MSBR(conf-if-GE 4/3)# switchport native vlan 300[ All Untagged
packets send to vlan 300]

Configuration Note 3. VLANs
Version 6.8 11 Mediant MSBR
3 VLANs
A VLAN is a broadcast domain that is created by switches. Typically, it is the router that
connects between the switches that broadcast to the VLAN domain.
The VLAN represents a group of hosts with a common set of requirements, independent of
a physical location. VLANs have the same attributes as a physical LAN, but allow you to
group end stations even if they are not located physically on the same LAN segment.
VLANs are usually associated with IP sub-networks. For example, all the end stations in a
particular IP subnet belong to the same VLAN. Traffic between VLANs must be routed.
LAN port VLAN membership is assigned manually on a port-by-port basis.
While configuring switch ports in a VLAN other than 1 (the default VLAN), all ports in a
single VLAN reside in the same broadcast domain.
VLANs are broadcast domains defined within switches to allow control of broadcast,
multicast, unicast, and unknown unicast within a Layer 2 device.
3.1 Commands
The table below describes how to assign an interface to a specific VLAN.
Table 3-1: VLAN Commands
Command Description
MSBR# configure data
Enter the data configuration menu.
(config-data)# interface
<physical_interface>
[slot/port.vlanID]
Allows you to enter a specific interface
configuration mode.
•<physical_interface> - selects the type of
interface.
•[slot/port.vlanID] – slot and port number is
taken from the device panel.
Note: The interface configuration mode
changes after the command is entered.
(conf-if-GE SlotNum/PortNum)#
Switchport mode access
Sets the port into access mode.
(conf-if-GE SlotNum/PortNum)#
switchport access vlan
[Vlan_ID]
Changes the VLAN membership of the port
from default to the VLAN ID it will use.

Configuration Note 12 Document #: LTRT-31672
Layer 2 Bridging using CLI
The table below describes how to configure a VLAN on Layer 3:
Table 3-2: VLAN on Layer 3 Commands
Command Description
MSBR# configure data
Enter the data configuration menu.
(config-data)# interface vlan
[Vlan-ID] Allows you to enter a specific interface
VLAN mode.
Vlan-ID – actual VLAN number.
(conf-if-GE SlotNum/PortNum)#
ip address [A.B.C.D]
[Subnet_Mask]
Assigns an IP address to the VLAN
interface.
3.2 Examples
In this example, two interfaces have been assigned to the same VLAN and the interface
VLAN layer 3 has also been configured.
Figure 3-1: VLAN
Client 1
Host on Vlan100 Client 2
Host on Vlan100
MSBR
The above example is implemented using the following commands:
MSBR(config-data)# interface gigabitethernet 4/1
MSBR(conf-if-GE 4/1)# switchport mode access
MSBR(conf-if-GE 4/1)# switchport access vlan 100
MSBR(conf-if-GE 4/1)# exit
MSBR(config-data)# interface gigabitethernet 4/2
MSBR(conf-if-GE 4/2)# switchport mode access
MSBR(conf-if-GE 4/2)# switchport access vlan 100
MSBR(conf-if-GE 4/2)# exit
MSBR(config-data)# interface vlan 100
MSBR(conf-if-VLAN 100)# ip address 192.168.100.1 255.255.255.0

Configuration Note 3. VLANs
Version 6.8 13 Mediant MSBR
An advanced example shows when the MSBR can recognize LAN ports as Trunk mode:

VLAN 100 is configured on both the MSBR1 and switch devices.

On the switch, VLAN 100 and VLAN 300 is configured with clients.

On MSBR1, only enable VLAN 300 with access to the private network.
Figure 3-2: Trunk
Client 1
Host on Vlan100 Client 3
Host on Vlan100 Client 4
Host on Vlan300
Trunk Link
(Pass Vlan 100,300)
MSBR
Gig 4/1
Switch
The above example is implemented using the following commands:
MSBR(config-data)# interface gigabitethernet 4/1
MSBR(conf-if-GE 4/1)# switchport mode trunk
MSBR(conf-if-GE 4/1)# switchport trunk allowed vlan add 100,300
MSBR(conf-if-GE 4/1)# exit
MSBR(config-data)# interface gigabitethernet 4/2
MSBR(conf-if-GE 4/2)# switchport mode access
MSBR(conf-if-GE 4/2)# switchport access vlan 100
MSBR(conf-if-GE 4/2)# exit

Configuration Note 14 Document #: LTRT-31672
Layer 2 Bridging using CLI
This page is intentionally left blank.

Configuration Note 4. Trunk Bridging
Version 6.8 15 Mediant MSBR
4 Trunk Bridging
Ethernet interfaces can be configured either as an access port or as trunk ports. Trunks
carry the traffic of multiple VLANs over a single link. A trunk port can have two or more
VLANs configured on the interface and can carry traffic for several VLANs simultaneously.
To correctly deliver the traffic on a trunk port with several VLANs, the device uses the IEEE
802.1Q encapsulation (tagging) method that uses a tag that is inserted into the frame
header. This tag carries information about the specific VLAN to which the frame and packet
belong. This method allows packets that are encapsulated for several different VLANs to
traverse the same port and maintain traffic separation between the VLANs. The
encapsulated VLAN tag also allows the trunk to move traffic end-to-end through the
network on the same VLAN.
4.1 Commands
The table below describes the trunk birding commands.
Table 4-1: Trunk Bridging Commands
Command Description
MSBR# configure data
Enter the data configuration menu.
(config-data)# interface
<physical_interface>
[slot/port.vlanID]
Allows you to enter a specific interface
configuration mode.
•<physical_interface> - selects the type of
interface.
•[slot/port.vlanID] – slot and port number is
taken from the device panel.
Note:The interface configuration mode
changes after the command is entered.
(conf-if-GE SlotNum/PortNum)#
Switchport mode trunk
Switches the port into trunk mode.
(conf-if-GE SlotNum/PortNum)#
switchport trunk allowed vlan
[add/remove]
Takes control of specific VLANs that will be
transmitted on the trunk interface.
Any VLAN that is not configured won’t be
allowed to transmit data on this trunk
interface.
(conf-if-GE SlotNum/PortNum)#
switchport trunk native vlan
[Native_VlanID]
Configures the native VLAN for this trunk
interface. Any packet on this interface
without a tag is tagged to the native VLAN
number.

Configuration Note 16 Document #: LTRT-31672
Layer 2 Bridging using CLI
4.2 Examples
This example shows two different VLANs configured on each switch port with a connecting
trunk that allows the transmission of data from VLAN 100 and VLAN 200. This example
describes how the same VLAN can be configured on different switch ports and at the same
time be connected to other hosts on the same VLAN via the Trunk. This is shown in the
figure below.
Figure 4-1: Trunk Bridging
The above example is implemented using the following commands:

MSBR1:
MSBR1(config-data)# interface gigabitethernet 0/0
MSBR1(conf-if-GE 0/0)# switchport mode trunk
MSBR1(conf-if-GE 0/0)# switchport trunk allowed vlan add
100,200
MSBR1(conf-if-GE 0/0)# switchport trunk native vlan 1

MSBR2:
MSBR2(config-data)# interface gigabitethernet 0/0
MSBR2(conf-if-GE 0/0)# switchport mode trunk
MSBR2(conf-if-GE 0/0)# switchport trunk allowed vlan add
100,200
MSBR2(conf-if-GE 0/0)# switchport trunk native vlan 1
Client 1
Host on Vlan100 Client 2
Host on Vlan200 Client 3
Host on Vlan100 Client 4 Host on Vlan200
MSBR2
MSBR1
Trunk Link

Configuration Note 5. Port-Monitoring
Version 6.8 17 Mediant MSBR
5 Port-Monitoring
Port Monitoring, also known as 'mirroring', is used on a network switch to send a copy of
network packets seen on one switch port (or an entire VLAN) to a network monitoring
connection on another switch port. Port mirroring is configured by assigning a port from
which to copy all packets and another port to which those packets will be sent. Usually a
protocol analyzer, for example, Wireshark is run on the port receiving the mirrored data to
monitor each segment separately. The analyzer, sometimes called a sniffer or packet
sniffer, captures and evaluates the data without affecting the client on the original port. The
port mirroring can also be used as a diagnostic or debugging tool.
5.1 Commands
The table below describes the port mirroring commands.
Table 5-1: Port Monitoring Commands
Command Description
MSBR# configure data
Enter the data configuration menu.
(config-data)# interface
<physical_interface>
[slot/port.vlanID]
Accesses a specific interface configuration mode.
•<physical_interface> - selects the type of
interface.
•[slot/port.vlanID] – slot and port number is taken
from the device panel.
Note: The interface configuration mode changes
after the command is entered.
(conf-if-GE
SlotNum/PortNum)# port-
monitor gigabitethernet
[slot/port.vlanID] [both-
direction|ingress|egress]
Allows this port to monitor the traffic on another
port:
•both-direction – monitors all incoming and
outgoing packets for this port.
•ingress – monitors all incoming packets for this
port.
•egress – monitors all outgoing packets for this
port.

Configuration Note 18 Document #: LTRT-31672
Layer 2 Bridging using CLI
5.2 Examples
In this example, a sniffer is connected to one of the switch ports on the MSBR and a client
connected to another switch port. The figure below shows how the sniffer listens to all
transport that passes through from the Gigabit Ethernet interface 1/2.
Figure 5-1: Port-Monitor
Sniffer Client 1
IP Address:192.168.0.1
IP Address:192.168.0.3
Gi 1/1
MSBR
Gi 1/2
The above example is implemented using the following commands:
MSBR# configure data
MSBR (config-data)# interface vlan 1
MSBR (conf-if-VLAN 1)# ip address 192.168.0.1
MSBR (config-data)# interface gigabitethernet 1/1
MSBR (conf-if-GE 1/1)# port-monitor gigabitethernet 1/2 both-
direction

Configuration Note 5. Port-Monitoring
Version 6.8 19 Mediant MSBR
To view packets for the gigabitethernet 1/1 interface:
1. Connect a network sniffer, such as Wireshark (free download on the internet).
2. After downloading the software, activate the packet filter on specific Ethernet NIC.
3. Ping with repeat of 1000 packets to the MSBR from the client, and then Get Next
Result.
A screen similar to the following is displayed:
Figure 5-2: ICMP Filter
You can apply a filter that displays only ICMP packets sent. Every packet contains data
and information.

Configuration Note 20 Document #: LTRT-31672
Layer 2 Bridging using CLI
This page is intentionally left blank.