Guide to basic concepts and information about the DM2104

This guide aims to assist the technician responsible for the configuration of the DM2104 equipment.
in its main functionalities.
The content covered is described below.

Basic information for access;

2. Creating a VLAN by adding interfaces to the VLAN;
3. STP Configuration;
4. LAG configuration (LACP and static);
5. Application of QinQ;
6. Application of CESoP;
7. Firmware Update.

Teracom Telematics S/A

Rua América, 1000
Eldorado do Sul - RS - Brazil
Postal Code 92990-000

[Link]
 1. Basic information for first access to DM2104:

The DM2104 equipment has two ways to access its settings, the first is through the
console port, located at the front of the equipment, as shown in figure 1.
You will need a console cable, which comes with the equipment, or an equivalent.

Figure 1. Front panel of the DM2104 equipment

Figure 2. Rear panel of the DM2104 equipment

The second way to access is via a UTP-RJ45 cable directly to one of the LAN PORTS. The IP
the default of the equipment is [Link]/24. Configure a static IP on your machine, within this same
range of IPs and execute a TELNET access through an application, such as Putty.

The user to access the equipment is admin and the password is also admin.

After accessing the equipment, change the username and password using the following commands:

DmSwitch#configure
DmSwitch(config)#username user admin password 0 user password
DmSwitch(config)#username user admin access-level 15

Teracom Telecommunications S/A

America Street, 1000
Eldorado do Sul - RS - Brazil
ZIP code 92990-000
[Link]
 2. Creating a VLAN and configuring an untagged interface (access) and
a tagged interface (trunk):

In some situations, it will be necessary to segment your network into VLANs. Follow the procedures to
continue. The chosen VLAN numbers and Ethernet interfaces are illustrative.

Create a VLAN and set an interface as access (untagged) - Usually used for PCs or
deliver a door to a customer:

DmSwitch#configure
DmSwitch(config) # interface vlan 30
DmSwitch(config-if-vlan-30)#set-member untagged ethernet 3

In the above example, we assigned Ethernet interface 3 as an untagged (access) member of VLAN 30.
After it has been inserted into the interface in the VLAN, it is necessary to specify the ethernet interface of which VLAN will be native.

DmSwitch#configure
DmSwitch(config)#interface ethernet 3
DmSwitch(config-if-eth-1/3)#switchport native vlan 30

Now the ethernet interface 3 is an access interface of VLAN 3.

Inserting interface 4 as tagged (trunk) for VLAN 30 – Tagged interface is usually used.
in uplink interfaces between switches:

DmSwitch#configure
DmSwitch(config)#interface vlan 30
DmSwitch(config-if-vlan-30)#set-member tagged ethernet 4

Now the ethernet interface 4 is configured as a tagged member, meaning it will send the packets with the
The 'tag' will interpret and distribute packets with this VLAN tag if they arrive on
equipment.

Some rules:

A VLAN can have multiple interfaces as tagged members, these interfaces will transmit and receive.
packets of these specific VLANs;
An access interface can be native to only one VLAN, normally the access interface
is related to a client or station.

Teracom Telematics S/A

America Street, 1000
Eldorado do Sul - RS - Brazil
ZIP Code 92990-000
[Link]
 3. STP (Spanning Tree Protocol) Configuration:

The STP (Spanning Tree Protocol) is a standard protocol for protecting against network loops, and it can
to be used in various topologies, but with longer convergence times compared to others
protocols that operate in ring topology, such as EAPS. DATACOM switches support the
STP (Spanning Tree Protocol), RSTP (Rapid Spanning Tree Protocol) and MSTP (Multiple Spanning Tree Protocol)
in all lines of equipment.
RSTP is enabled by default in the equipment's configuration and can be viewed using the
command: show running-config.

Create VLAN groups for STP protection:

DmSwitch(config)#vlan-group <0-3>(We can choose the group from 0 to 3)

DmSwitch(config)#vlan-group <0-3> vlan range <1-4094> (In the group we chose, we will
define the range of VLANs that will be part of the group

Select the type of STP - In the command below, we can choose between Multiple, Rapid, and Spanning Tree.
traditional

DmSwitch(config)#spanning-tree mode <mstp | rstp | stp>

Create an instance and map the VLAN groups to these instances - In the command below we can
choose between the instances from 0 to 7 and choose which vlan group we want to put, as well as all or one
specific range of VLAN group:

DmSwitch(config)#spanning-tree <0-7>
DmSwitch(config)#spanning-tree <0-7> vlan-group <0-3 | all | range>

Change the STP priority - In the command below, we choose the STP instance and its priority, which must
be a multiple of 4096 between 0 and 61440:

DmSwitch(config)#spanning-tree <0-7> priority <0-61440>

Configure a port as access - In the command below we define interface 1/1 as an edge port, that is,
The Spanning Tree will not perform any checks on this port:

DmSwitch(config-if-eth-1/1)#spanning-tree edge-port

Avoid being the Root in case of the lowest ID and lowest MAC - Whenever the port receives this line, it cannot be a
root port. That is:

DmSwitch(config-if-eth1/1)#spanning-tree restricted-role

To avoid generating and propagating notifications of topology changes or link failures:

DmSwitch(config-if-eth-1/1)#spanning-tree restricted-tcn
Teracom Telematics S/A
America Street, 1000
Eldorado do Sul - RS - Brazil
ZIP Code 92990-000
[Link]
 Figure 3. Status of interfaces with STP protection

The status of the interfaces is described below.

AD= Alternative Discarding (Blocked Port);

RF = Root Forwarding (Port that goes towards the Root);
DF= Designated Forwarding (Port that receives and sends BPDUs).

Teracom Telematics Inc.

America Street, 1000
Eldorado do Sul - RS - Brazil
Postal Code 92990-000

[Link]
 4. LAG (Link Aggregation Group) Configuration:

LAG (PortChannel, Etherchannel or Link Aggregation) is the technology that allows for aggregation of
ethernet interfaces between two switches.
The benefits of using a LAG are the increased capacity of the uplink, forming a single
logical interface to provide bandwidth increase, redundancy in case of failures, and load balancing
packages.
The DM2104 supports the creation of up to 8 PortChannel interface groups, with the maximum grouping
up to 8 Ethernet interfaces.
To create a LAG, observe the following sequences, according to the desired type.

STATIC:

Define in the PortChannel interface to be created which ethernet interfaces will be inserted as members:

DmSwitch(config)#interface port-channel 1
DmSwitch(config-if-port-ch-1)#set-member ethernet range 5 6

Check the static Port-Channel:

DmSwitch#show interfaces status port-channel <1-3>

DYNAMIC:

Disable the remote-devices:

DmSwitch(config)#no remote-devices enable

Define the interfaces that will be part of the PortChannel:

DmSwitch(config)#interface ethernet range 5 6

Enable the LACP Actor key and the LACP:

DmSwitch(config-if-eth-1/5-to-1/6)#lacp
DmSwitch(config-if-eth-1/5-to-1/6)#lacp actor admin-key 1

When executing the above commands, the PortChannel will be automatically created based on the MACs of
neighbors, therefore, if you have two connected ports on a device, when creating and enabling olacp
act on these interfaces, automatically creating the LAG.
It is noteworthy that if the PortChannel created on one side is of dynamic type, the remote side must also be.
it should be dynamic.

Check the LACP:

DmSwitch#show lacp counters

DmSwitch#show lacp neighbors

Teracom Telematics Inc.

America Street, 1000
Eldorado do Sul - RS - Brazil
ZIP Code 92990-000
[Link]
 5. QinQ Configuration:
802.1q (QinQ) aims to transport multiple VLANs from different customers over a single
Service VLAN (which belongs to the operator or a provider). In this way, the operator saves on the use of
VLANs, optimizing and simplifying traffic.
There are two types of ports in the use of 'QinQ':

EXTERNAL: These are the Ethernet interfaces facing the customer. They are input interfaces so that the
VLANs of various customers are transported by the operator or provider. Interfaces from 5 to 8 per
default, they are already in EXTERNAL mode.

INTERNAL: These are the ethernet interfaces directed towards the operator's or provider's network and
they will carry out the transport of the service. At the EXTERNAL ports, there will be the decapsulation of the customers' VLANs.
The interfaces from 1 to 4 by default are already in INTERNAL mode.
Observe the topology:

Figure 4. Example of QinQ topology

It is observed that VLANs 10, 20, and 30 are encapsulated by VLAN 550, which belongs to the operator.

The ports with the information 'E' are directed towards the side of the routers, as we explained.
previously and the doors with the information 'I' to the side of the operator or provider's VLAN.

Below is an example of EDD A configuration, which also applies to EDD B.

Note: For learning purposes, the internal and external commands will be inserted into the interfaces.
however, these settings are native to the equipment, according to the characteristics of each range (1 to 4 or 5 to
8) and can be changed via CLI.

Enable 'QinQ' globally on the equipment:

EDD_A#configure
EDD_A(config)#vlan qinq

Create the service VLAN:

EDD_A(config-if-vlan-30)#interface vlan 550

EDD_A(config-if-vlan-550)#name OPERADORA
Teracom Telematics S/A
America Street, 1000
Eldorado do Sul - RS - Brazil
ZIP Code 92990-000
[Link]
 EDD_A(config-if-vlan-550)#set-member tagged ethernet 1
EDD_A(config-if-vlan-550)#set-member untagged ethernet 4
EDD_A(config-if-vlan-550)#set-member untagged ethernet 5
EDD_A(config-if-vlan-550)#set-member untagged ethernet 6

Insert interfaces 4, 5, and 6 as natives of their respective VLANs and define which ports will be 'QinQ'.
internal and external

EDD_A(config)#
EDD_A(config)#interface ethernet 4
EDD_A(config-if-eth-1/4)#switchport native vlan 550
EDD_A(config-if-eth-1/4)#switchport qinq external

EDD_A(config-if-eth-1/4)#interface ethernet 5
EDD_A(config-if-eth-1/5)#switchport native vlan 550
EDD_A(config-if-eth-1/5)#switchport qinq external

EDD_A(config-if-eth-1/5)#interface ethernet 6
EDD_A(config-if-eth-1/6)#switchport native vlan 550
EDD_A(config-if-eth-1/6)#switchport qinq external

EDD_A(config-if-eth-1/6)#interface ethernet 1
EDD_A(config-if-eth-1/1)#switchport qinq internal

Teracom Telecommunications S/A

America Street, 1000
Eldorado do Sul - RS - Brazil
ZIP Code 92990-000
[Link]
 6. CESoP Setup:

The Circuit Emulation Service over Packets

CESoP is a technology that allows the transmission of services that use Multiplexing by Division of
Time Division Multiplexing (TDM) through asynchronous networks, such as switching networks
packages.
A link with CESoP consists of three elements:

TDM:

TDM, which in Portuguese means Time Division Multiplexing, uses the concept of
allocation of time slots, called timeslots, for the previously sampled signals. The TDM-PCM or
Pulse Code Modulation is the method used to digitally represent analog signals.
sampled. The T1 system is a TDM of 24 voice channels using 7-bit PCM. The E1 system is a TDM of 30
voice channels and 2 channels for synchronization and signaling. Thus, an E1 mode TDM frame contains 32
8-bit timeslots. The synchronization information in TDM mode E1 is present in the first timeslot.
of the frame (TS 0).
In channel associated signaling (CAS), two timeslots are used: the first timeslot
(TS 0) for the frame synchronization information, and the sixteenth timeslot (TS 16) for signaling. The
frame sync loss is identified after the reception of incorrect sync words. This
triggers the resynchronization process and activates the loss of synchronization alarm.
In the TDM interface of the equipment, configure the PCM that corresponds to the type of frame (with/without
synchronization) and number of timeslots, as well as CAS signaling if necessary.

Bundle:

The bundle refers to the Ethernet network, which aims to transmit data over the network.
IP/Ethernet. The bundle represents a mapping of a TDM interface that will be transmitted between two
equipment connected by Pseudo-Wire.

Pseudo-Wire:

The Pseudo-Wire (PW) allows legacy services, such as TDM, to be transported over a connection.
virtual point-to-point through the same circuit in IP/Ethernet networks to its destination. The basic idea is the
use of a third layer in the network, over which an operator needs to transport services
legacies, including also the layer 2 of network services.
The example below shows a scenario where VLAN 20 is transporting TDM 1 from each
equipamento. É importante atentar-se a parte de relógio e sincronismo do circuito. Para isso, deve-se verificar
on which side is the synchronization provided.
In the vast majority of cases, the operator side is what provides the clock for the TDM interface of a
two DM2104.

Teracom Telematics S/A

Rua América, 1000
Eldorado do Sul - RS - Brasil
ZIP 92990-000
[Link]
 Figure 5. Example of CESoP topology

Below are the configurations of the EDD A and EDD B equipment.

EDD EQUIPMENT A

configure
!
interface vlan 20
name TRAFEGO_CESoP
set-member tagged ethernet 1/1 (Interface that communicates with the remote side)
!
interface vlan 3000 (If you have a VLAN for management)
MANAGEMENT
IP address [Link]/24 (IP used as an example for management via TELNET)
set-member tagged ethernet 1/1 (Interface for communication with the remote side)
exit
!
interface pw 1/1
source-ip-addr [Link] (Local IP)
vlan 20 priority 7
exit
!
interface tdm 1/1
line-type unframed (Customer PCM type)
no shutdown
exit
!
interface bundle 1/1
timeslots 0 32 (Where 0 means the initial timeslot and 32 the total number of channels)
PCM)
destination-ip-address [Link] (IP of the remote side)
jitter-buffer 20
circuit-name BUNDLE_TESTE
ip-next-hop [Link] (remote IP)
packet-delay 2 (Needs to be 10x smaller than the Jitter-buffer)
tdm-channel 1 (I inform that bundle 1/1 will use interface TDM 1)
lost-pkt-fill idle-byte (Allows failures to propagate to the remote device)
Teracom Telematics Inc.
Rua América, 1000
Eldorado do Sul - RS - Brazil
ZIP Code 92990-000
[Link]
no shutdown
end
!

For synchronization, observe the situations below.

sync-source hierarchy 1 transmit-clock-source internal (For equipment without a source of

synchronism. Use the internal source)

sync-source hierarchy 1 transmit-clock-source tdm 1 (Synchronization source through the

TDM interface. Used when connected directly to the operator)

sync-source hierarchy 1 transmit-clock-source adaptive bundle 1 (Remote side and unconnected)

directly with the operator. Used on the side opposite to the configuration described above)

EDD B EQUIPMENT

configure
!
interface vlan 20
TRAFFIC_CESoP
set-member tagged ethernet 1/1 (Interface that has communication with the remote side)
exit
!
interface vlan 3000 (If you have a management VLAN)
MANAGEMENT
ip address [Link]/24 (IP used as an example for management via TELNET)
set-member tagged ethernet 1/1 (Interface for communication with the remote side)
exit
!
interface pw 1/1
source-ip-addr [Link] (Local IP)
vlan 20 priority 7
exit
!
interface tdm 1/1
line-type unframed (Client's PCM type)
no shutdown
exit
!
interface bundle 1/1
timeslots 0 32 (Where 0 means the initial timeslot and 32 the total number of channels)
PCM
destination-ip-address [Link] (IP of the remote side)
jitter-buffer 20
circuit-name BUNDLE_TESTE
ip-next-hop [Link] (remote IP)
packet-delay 2(Necessita ser 10x menor que o Jitter-buffer)
tdm-channel 1 (I inform that bundle 1/1 will use the TDM interface 1)
lost-pkt-fill idle-byte (Allows failures to propagate to the remote equipment)
no shutdown
end

For synchronization, observe the situations below:

Teracom Telematics S/A

America Street, 1000
Eldorado do Sul - RS - Brazil
ZIP Code 92990-000
[Link]
sync-source hierarchy 1 transmit-clock-source internal (For equipment without a source of
synchronism. Use the internal source)

sync-source hierarchy 1 transmit-clock-source tdm 1 (Synchronization source through the

TDM interface. Used when connected directly to the operator)

sync-source hierarchy 1 transmit-clock-source adaptive bundle 1 (Remote side and not connected)
directly with the operator. Used on the opposite side to the configuration described above

Commands for verification:

#show interfaces status bundle 1 (where 1 is the configured bundle number)

#show interfaces status tdm 1 (where 1 is the configured TDM number)

DmSwitch#show interface status bundle 1

Bundle 1/1 - Status Information:
Bundle Name: BUNDLE_TEST
Local Bundle: Ok
Remote Bundle: Ok
TDM Local: Ok
TDM Remote: OK
Packet size: Ok
Next-Hop: Ok
MAC: 00:04:DF:xx:xx:xx

Teracom Telematics S/A

America Street, 1000
Eldorado do Sul - RS - Brazil
ZIP Code 92990-000
[Link]
7. Firmware Update:

In the following examples, the Putty application was used for remote access via TELNET (In-band management)
as a client for connection to the equipment and the TFTP server Tftpd32 / Tftpd64 version 4.50 which is
being executed through a computer/notebook with the IP address [Link].
The DM2104 and DM2106 devices have only one firmware position. When carried out the
your update, this will be allocated in memory and upon rebooting, the firmware is written to the flash memory.
Below are all the steps for the update in detail.

Initialize a TELNET/SSH session logging the entire session;

Make the firmware image available on a TFTP server that is accessible from the
equipment
Unlike the other devices in the DmSwitch line, it is necessary to save the configuration of
equipment before proceeding. Execute the command copy running-config startup-
config to save the configuration. If the equipment is set to factory configuration, it is
it is necessary to select the startup flash before this. Type the syntax select flash-config <1-
to select one of the positions where the equipment settings will be saved.

Figure 6. Selecting the Startup

Figure 7. Saving the settings

Execute a ping from the device to check the connectivity with the TFTP server.

Figure 8. Ping test

Teracom Telematics S/A

America Street, 1000
Eldorado do Sul - RS - Brazil
ZIP code 92990-000
[Link]
 Check the current version using the command show firmware.

Figure 9. Firmware Version

To update the firmware, use the syntax:

copy tftp <server_IP> <image_name.im> firmware

After executing the command, a message will be displayed informing that the equipment will be
restarted at the end of the update. Confirming this option, the image will be downloaded
of the firmware for the DM2104 equipment.

Figure 10. Update syntax

Below is the example of the update.

Figure 11. Example of update

After the reboot, confirm the firmware version.

Figure 12. Firmware version

Teracom Telematics S/A

America Street, 1000
Eldorado do Sul - RS - Brazil
ZIP Code 92990-000
[Link]