Harmony First Mile 200 Product Description

Harmony First Mile 200, R2.5.
1
IDU Product Description
Issue 1, updated in February, 2014
Document Number: PM-000016-01-EN
Notice
This document contains DragonWave proprietary information. Use,
disclosure, copying or distribution of any part of the information contained
herein, beyond that for which it was originally furnished, requires the written
permission of DragonWave Inc.
The information in this document is subject to change without notice and

relates only to the product defined in the introduction of this document.
DragonWave intends that information contained herein is, to the best of its
knowledge, correct and accurate. However, any/all liabilities associated with
the use or accuracy of the information contained herein must be defined in a
separate agreement between DragonWave and the customer/user.
Copyright DragonWave Inc. 2014. All rights reserved.
Preface
Contents
1
Preface .................................................................................................................................................................... 6
1.1
Intended audience ...................................................................................................................................... 6
1.2
Structure of this document ....................................................................................................................... 6
1.3
History of changes ...................................................................................................................................... 6
1.4
Symbols and conventions ......................................................................................................................... 7
1.5
Waste electrical and electronic equipment (WEEE) ............................................................................ 8
1.6
RoHS compliance ........................................................................................................................................ 9
1.7
CE compliance ............................................................................................................................................. 9
1.8
MEF compliance........................................................................................................................................... 9
Overview .............................................................................................................................................................. 10
2.1
Harmony Microwave ................................................................................................................................. 10
2.2
First Mile 200 Indoor Unit ......................................................................................................................... 10
2.2.1
Interfaces ............................................................................................................................................. 11
2.2.2
Licensing .............................................................................................................................................. 16
2.2.3
Software release ................................................................................................................................ 16
Features ............................................................................................................................................................... 17
3.1
General features ......................................................................................................................................... 18
3.2
Carrier Ethernet Transport ...................................................................................................................... 18
3.2.1
Ethernet services ............................................................................................................................... 18
3.2.2
Ethernet QoS ....................................................................................................................................... 20
3.2.3
Ethernet OAM...................................................................................................................................... 29
3.2.4
Link Layer Discovery Protocol (LLDP) ......................................................................................... 31
3.2.5
Bridging modes .................................................................................................................................. 32
3.3
TDM circuit emulation service (CES) .................................................................................................... 32
3.3.1
CESoP for E1/T1/J1 ........................................................................................................................... 33
3.3.2
SAToP for E1 ....................................................................................................................................... 33
3.3.3
Mixed configuration of SAToP with CESoP for E1 ................................................................... 34
3.4
Protection .................................................................................................................................................... 34
3.4.1
LPG protection ................................................................................................................................... 34
3.4.2
xSTP for E-LAN service .................................................................................................................... 36
3.4.3
LAG protection ................................................................................................................................... 37
3.4.4
CESoP and SAToP linear protection ............................................................................................ 38
3.4.5
G.8031 linear protection ................................................................................................................... 38
3.4.6
G.8032 ring protection ...................................................................................................................... 40
3.5
Synchronization ......................................................................................................................................... 42
3.5.1
Synchronization overview ............................................................................................................... 42
3.5.2
Synchronization from TDM interface ............................................................................................ 44
3.5.3
Synchronization from Ethernet interface .................................................................................... 45
3.5.4
Clock recovery.................................................................................................................................... 45
3.6
Performance management ...................................................................................................................... 45
3.6.1
Performance management based Ethernet service ................................................................. 45
3.6.2
Performance management based CESoP service .................................................................... 46
3.6.3
Performance management based OAM ....................................................................................... 46
3.6.4
Performance monitoring .................................................................................................................. 46
3.7
Security management............................................................................................................................... 47
3.7.1
SSH/SFTP ............................................................................................................................................. 48
3.7.2
SNMPv2c/SNMPv3 ............................................................................................................................. 48
3.7.3
User class management................................................................................................................... 49
3.7.4
Securing management protocols .................................................................................................. 50
3.8
Web-based LCT management ................................................................................................................ 50
3.8.1
4
Preface
DCN configuration auto-recovery.................................................................................................. 51
Application .......................................................................................................................................................... 52
4.1
Network application .................................................................................................................................. 52
4.2
Site configurations .................................................................................................................................... 53
4.2.1
Tail site: 3G BTS only ....................................................................................................................... 53
4.2.2
Tail site: 2G and 3G BTSs collocation ......................................................................................... 53
4.2.3
Tail site: 2G, 3G, and 4G BTSs collocation ................................................................................. 54
4.2.4
Chain site ............................................................................................................................................. 54
Management ........................................................................................................................................................ 55
5.1
Network management using Nokia Siemens Networks ................................................................... 55
5.2
Network management using NetViewer .............................................................................................. 55
5.3
Commissioning Tool................................................................................................................................. 55
5.4
Network management using First Mile 200 R2.5.1 Web- based LCT............................................. 56
5.5
Accessing IDU ............................................................................................................................................ 56
5.6
SNMP agent ................................................................................................................................................. 56
Preface
5.7
SNTP, FTP, and Telnet .............................................................................................................................. 57
5.8
Memory Key ................................................................................................................................................ 57
5.9
License ......................................................................................................................................................... 57
Mechanical structure and interfaces ............................................................................................................ 59

6.1
First Mile 200 interface ............................................................................................................................. 59
6.1.1
Installation ........................................................................................................................................... 59
6.1.2
Power supply ...................................................................................................................................... 60
6.1.3
Handling requirements ..................................................................................................................... 60
6.1.4
Reset ..................................................................................................................................................... 60
6.2
7
Connection to ODUs ................................................................................................................................. 60
Technical specifications .................................................................................................................................. 61

7.1
Dimensions and weight ............................................................................................................................ 61
7.2
Power requirements.................................................................................................................................. 61
7.3
Temperature requirements ..................................................................................................................... 61
7.4
Interfaces ..................................................................................................................................................... 63
7.5
LEDs indication .......................................................................................................................................... 63
7.6
GE electrical Ethernet cable (for local traffic)..................................................................................... 64
7.7
GE electrical Ethernet cable (for ODU) ................................................................................................. 64
7.8
GE SFP optical Ethernet cable ............................................................................................................... 64
7.9
GE SFP electrical Ethernet cable ........................................................................................................... 65
7.10
E1/T1/J1 cable ............................................................................................................................................. 65
7.11
Power cable ................................................................................................................................................. 65
7.12
Memory Key ................................................................................................................................................ 65
7.13
Optical Splitter ............................................................................................................................................ 65
7.14
Standards .................................................................................................................................................... 66
Preface
1 Preface
This document provides technical description and technical specifications of First Mile
200, an Indoor Unit (IDU).
The Product Description does not contain any instructions to be carried out.
This document concerns the software release 2.5.1 only.
1.1 Intended audience

This document is intended for the radio network planners and the technicians who are
in charge of operating and maintaining First Mile 200.
1.2
Structure of this document

The document is divided into the following main chapters:
Chapter
Title
Subject
Chapter 1
Preface
Provides an introduction and overview of this

Product Description document
Chapter 2
Overview
Provides an overview on First Mile 200
Chapter 3
Features
Provides the main features introduction
Chapter 4
Application
Provides the main applications that can be

implemented with First Mile 200
Chapter 5
Management
Provides the information regarding the

management of First Mile 200
Chapter 6
Mechanical structure
and interfaces
Provides the information regarding the

structure and the external interfaces of First
Mile 200
Chapter 7
Technical specifications
Lists the technical data
Table 1
1.3
Structure of this document
History of changes
Issue
1.0
Table 2
Issue date
February, 2014
History of changes
Remarks
1st version
Preface
1.4 Symbols and conventions

The following symbols and mark-up conventions are used in this document:
Representation
DANGER!
WARNING!
CAUTION!
Meaning
A safety message indicates a dangerous situation where
personal injury is possible.
The keywords denote hazard levels with the following meaning:
DANGER! - Indicates a hazardous situation which, if not
avoided, will result in death or serious (irreversible) personal
injury.
WARNING! - Indicates a hazardous situation which, if not
avoided, could result in death or serious (irreversible) personal
injury.
CAUTION! - Indicates a hazardous situation which, if not
avoided, may result in minor or moderate (reversible) personal
injury.
NOTICE:
A property damage message indicates a hazard that may result

in equipment damage, data loss, traffic interruption, and so on.
A note provides important information related to the topic, for
example, not obvious exceptions to a rule or side effects.
A tip provides additional information related to the topic which is
not essential in the context, but given for convenience.
Bold
Italic
All names of graphical user interface (GUI) objects, such as

windows, field names, buttons, and so on.
Example: Select the Full Screen check box and press OK.
Terms and abbreviations which are linked to an entry in the

glossary and list of abbreviations respectively
Important key words
Files, folders, and file system paths.

Example: /usr/etc/sbin/ftpd.exe
Emphasized words
typewriter
<angle brackets>
Input to be typed in a command line or a GUI field.

Examples:
ping -t 192.168.0.1
Enter World in the Domain field.
Output from a command, error messages, content of a status
line, and so on
File content, such as program sources, scripts, logs, and
settings
Placeholders, for example as part of a file name or field value.

Examples:
<picture name>.png or <ip address>:<port
Table 3
List of symbols and conventions
number>
Preface
Representation
[square brackets]
Meaning
A key to be pressed on a PC keyboard, for example [F11].
Keys to be pressed simultaneously are concatenated with a +
sign, for example [CTRL]+[ALT]+[DEL].
Keys to be pressed one after another are concatenated with
spaces, for example [ESC] [SPACE] [M].
>
The greater than symbol > is used to concatenate a series of

GUI items in order to depict a GUI path. This is an abridged
presentation of a procedure to be carried out in order to perform
an action or display a window or dialog box.
Examples:
A simple menu path: File > Save as ...
A more complex GUI path:
SURPASS TransNet window > Tools menu >
3R-Matrix Report command > 3R-Matrix Report dialog box
x
(in card names)
For convenience, card names are sometimes listed with a lower

case x variable, in order to concisely represent multiple cards.
Example:
I01T40G-x (is to be interpreted as I01T40G-1 and I01T40G-2)
Table 3
List of symbols and conventions (Cont.)
Screenshots of the graphical user interface are examples only to illustrate principles.
This especially applies to a software version number visible in a screenshot.
1.5
Waste electrical and electronic equipment (WEEE)

All waste electrical and electronic products must be disposed of separately from the
municipal waste stream via designated collection facilities appointed by the government
or the local authorities. The WEEE label (see Figure 1) is applied to all such devices.
Figure 1
WEEE label
The correct disposal and separate collection of waste equipment will help prevent
potential negative consequences for the environment and human health. It is a
precondition for reuse and recycling of used electrical and electronic equipment.
For more detailed information about disposal of such equipment, please contact
DragonWave.
The above statements are fully valid only for equipment installed in the countries of the
European Union and is covered by the directive 2002/96/EC. Countries outside the
Preface
European Union may have other regulations regarding the disposal of electrical and
electronic equipment.
1.6 RoHS compliance

First Mile 200 R2.5.1 complies with the European Union RoHS Directive
2011/65/EU on the restriction of use of certain hazardous substances in electrical and
electronic equipment.
The directive applies to the use of lead, mercury, cadmium, hexavalent chromium, polybrominated biphenyls (PBB), and polybrominated diphenylethers (PBDE) in electrical
and electronic equipment put on the market after 1 July 2006.
First Mile 200 R2.5.1 complies with the Chinese standard SJ/T 11364-2006 on the
restriction of the use of certain hazardous substances in electrical and electronic
equipment. The standard applies to the use of lead, mercury, cadmium, hexavalent
chromium, polybrominated biphenyls (PBB), and polybrominated diphenyl ethers
(PBDE) in electrical and electronic equipment put on the market after 1 March 2007.
1.7 CE compliance
First Mile 200 R2.5.1 is in compliance with the essential requirements and other
relevant provisions of Directive: 2006/95/EC, 2004/108/EC, and 1999/5/EC.
The product is marked with the CE marking

Figure 2
CE marking
1.8 MEF compliance

First Mile 200 R2.5.1 operating at the NNI delivers EPL, EVPL and E-LAN service
complies with the Metro Ethernet Forum MEF14 technical specification. First Mile 200
R2.5.1 operating at the UNI delivers EPL, EVPL and E-LAN service complies with the
Metro Ethernet Forum MEF9 technical specification.
Figure 3
MEF certified compliant logo
Overview
2 Overview
First Mile 200 is a reliable and flexible indoor unit (IDU) of Harmony Microwave family,
which can be used for tail and chain applications in the mobile backhaul. It can be
connected to Harmony Radio (ODU) to carry traditional TDM traffic and Ethernet traffic.
2.1 Harmony Microwave

Harmony Microwave is a new packet microwave system designed to meet the
requirements of evolved transport networks with the target of minimizing the operators
Total Cost of Ownership (TCO). It joins together the benefits of an advanced scalable
microwave radio and of a real carrier grade Ethernet nodal solution.
Harmony Microwave is the means of deploying a cost-effective microwave infrastructure
for 3G, WiMAX and LTE backhaul, high speed wireless Internet networks, fixed
broadband access backhaul and private wireless networks.
Harmony Microwave is the right solution to design advanced mobile backhaul
networks based on Ethernet transport. The solution is conceived both for pure packet
and TDM+Packet hybrid networks.
Harmony Microwave family includes the following:
Harmony Radio (ODU)
Harmony MultiRadio (ODU)
Harmony First Mile 200 (IDU)

Harmony First Mile 200i (IDU)
Harmony Hub 800
For detailed information of each product in Harmony Microwave family, please refer
to the dedicated customer documentation of each product provided by DragonWave.
2.2 First Mile 200 Indoor Unit

First Mile 200 is an indoor unit with less than 1U high, which is 32 mm high only (1U =
44.45 mm, and minimum 1U system installation space in rack is required for power
dissipation). It can be connected to Harmony Radio to support Ethernet uplink and
downlink traffic. It offers advanced Ethernet processing features as well as maximum
flexibility to support TDM traffic via circuit emulation. Access interfaces include Fast and
Gigabit Ethernet, E1, T1 and J1.
Additionally, as part of the Carrier Ethernet portfolio, it allows a smooth integration in
the network, ensuring end to end Quality of Service (QoS) and easy provisioning.
ODU can be connected to First Mile 200 through a single Ethernet cable using ports
with ODU power feeding support. Alternative option is to use 2 cables (with a separate
power supply cable).
Overview
In First Mile 200, ODU link protection group (LPG) is supported. It is possible to
install up to 2 pairs of protecting ODUs. Mixed configuration can be supported, for
example (1+1)+2x(1+0).
First Mile 200 can be commissioned by Commissioning Tool through the local
Ethernet connection.
First Mile 200 can be configured, monitored, and administered by Web-based
Local Craft Terminal (WebLCT) or NetViewer management tool locally / remotely
through connection via Data Communication Network (DCN) port.
2.2.1
Interfaces
Figure 4 shows the First Mile 200 front panel, the interfaces as follows:
1. 1 x DC input (-48 V)
2. 4 x 10/100/1000 BaseT electrical ports with synchronous Ethernet (two ports
supports ODU power feeding)
3. 2 x Small Form Pluggable (SFP) Ethernet ports
4. 8 x E1/T1/J1 ports with 120, 100 and 75 Ohm impedance
5. 1 x DCN (In-band management)
6. 1 x OOB management port (local management)
7. 1 x Dry contact (two inputs and five outputs, used for alarm interface)
8. 1 x Memory Key
Figure 4
Front panel view of First Mile 200
First Mile 200 interfaces are shown in Figure 5.

Networks
E1/T1/J1
DRY CONTACT 10/100 Base-T

PW R
C / MJ
MN / W
Harmony
FirstMi le 200
Memory Key
Figure 5
RST
OOB
DCN
10/100/1000 Base-T
GbEth SFP
LINK
MK
TEST
ODU
ACT
LINK
ACT
23(PWR) 4(PW R)
D.C. PWR
+ -
Front Panel view of First Mile 200
The optical Ethernet port (SFP) cannot be used to connect ODU. Both SFP
optical and electrical Ethernet ports can be connected to other equipment for local traffic.
There are two choices of SFP connector when connecting to the SFP Ethernet ports:
connector
cable type
Electrical SFP
10Base-T/100Base-TX/1000Base-T
Optical SFP
1000Base-X
Table 4
SFP connectors
Overview
For detailed information of Memory Key, please refer to Chapter 5.8.
2.2.2
Licensing
Customer who wants to use certain features has to purchase the corresponding license.
A license can be bought by the customer together with the hardware and the application
software in the initial purchase order, or it can be later purchased and installed into an
already operating appliance.
First Mile 200 is delivered to customer with the basic license pre-installed, with the
essential functions enabled. If additional features need to be activated, customer can
acquire upgrading licenses. Detailed information of license is described in Chapter 5.9.
2.2.3
Software release
Please refer to Customer Release Note for detailed information of First Mile 200
R2.5.1 software release load.
Features
3 Features
The followings are main features of First Mile 200 R2.5.1:
General features
Memory Key
Directly power injecting to ODU on 2 Gigabit Copper Ethernet Ports
LEDs
Carrier Ethernet Transport
Ethernet services
Queue Scheduling: SP, SP+WRR, SP+WDRR
Support for Multi-QoS (i.e., multiple priorities per service)

Traffic Shaping per port and per queue
Congestion management with sRED
Rate limit on broadcast/multicast/unknown traffic per port for E-LAN service

Ethernet OAM
End-to-end performance monitoring according to Y.1731
End-to-end fault management according to 802.1ag
End-to-end performance of services per port
Service (E-Line/E-LAN) statistics
16 15 minutes and 4 24 hours period statistics

UNI port shutdown on service failure
Link Layer Discovery Protocol (LLDP)
One-way connectionless protocol

Bridging modes
CESoP for E1/T1/J1
SAToP for E1
Protection
LPG protection
xSTP for E-LAN service
LAG protection
CESoP and SAToP linear protection

G.8031 linear protection
IEEE802.1Q
IEEE802.1ad
TDM circuit emulation service (CES)
E-Line service
E-LAN service
Ethernet QoS
Traffic policing supporting CIR and PIR bandwidth profile
8 priority queues per port
G.8032 ring protection

Synchronization
Synchronization from TDM interface
Synchronization from Sync Etherne
Clock recovery
SSM supported
Features
Performance management
Performance monitoring
Security management
Performance management for Ethernet, CESoP and OAM services
SNMPv3 with encryption, SSH/SFTP
Web-based LCT management
DCN configuration auto-recovery
3.1 General features

There is a Memory Key Slot on First Mile 200 front panel. A 32 Mbit Serial Data Flash
Memory is suitable for in-system reprogramming using Serial Peripheral Interface (SPI).
More detailed information of the Memory Key is described in Chapter 5.8 Memory Key.
A Power Source Equipment (PSE) is integrated into First Mile 200 and is
able to deliver DC power supply to ODU acting as a one-port end-span power injector
The ODU powering procedure is controlled by software and can be started only if the
interface is configured to support an ODU. In any condition, if the ODU power supply is
disabled for that interface, the procedure is stopped and voltage is removed.
Two Ethernet Ports 3(PWR) and 4(PWR) support the power injector function.
On First Mile 200 front panel, there are four types of LEDs to indicate the status of
system, Memory Key, Ethernet ports and E1/T1 ports.
More detailed information of the LEDs, please refer to Chapter 7.5 LEDs indication.
3.2 Carrier Ethernet Transport

3.2.1
Ethernet services
The Carrier Ethernet Transport is to provide end-to-end service to customer with a
guaranteed quality of service, such as a guaranteed bandwidth for services with
different priority, delay and delay variation, reliability and redundancy, etc.
First Mile 200 supports both E-Line service and E-LAN service.
3.2.1.1
E-Line service
For E-Line service, traffic from any configurable port can go to any other configurable
port, see Figure 6. Packets received from ingress port, are parsed and processed, e.g.,
policing, countering, editing. The selection of egress port is not based on L2 bridging,
but based on service mapping rule definition (thus, E-Line service does not need to learn
MAC address).
Features
Figure 6
E-Line illustration
Figure 7 demonstrates E-Line service.
Figure 7
3.2.1.2
E-Line service application
E-LAN service
E-LAN service is based on L2 bridging by learning the source MAC address and
matching the destination MAC address. The packet destination MAC address + VLAN
ID determines its egress port, see the illustration in Figure 8.
Features
Figure 8
E-LAN service illustration
E-LAN service is a multipoint-to-multipoint service that can be used for both

management plane (management E-LAN) and for data plane. For example in 4G
networks, packets received from a BTS can be directed either to core network or a
neighbor BTS, the forwarding decision is based on destination MAC address matching.
Figure 9 demonstrates E-LAN service.
Figure 9
3.2.2
E-LAN service application
Ethernet QoS
Figure 10 shows the QoS architecture of First Mile 200 with main components as:
Ingress storm control
Classifier and filter rule database
Per-flow TrTCM marker/policing (Two-rate three-color-marker)
Buffer management and Congestion avoidance
Scheduling
CoS queue and egress port rate limiting (Shaping)
Features
Figure 10
3.2.2.1
QoS architecture
Ingress storm control

In the network, a malfunction by a user e.g., sending unicast, broadcast, or multicast
traffic at a very high rate could cause a flooding in the network. Thus it is required a
switch to have the capability preventing the flooding packets from going to other
segments of the network.
First Mile 200 provides a per-port byte-rate control mechanism to control the flooding at
the ingress. In First Mile 200, broadcast, multicast and unknown unicast packets are
monitored. Each type of packets has separate counters. The ingress counter counts
the number of packets which enable multicasting and broadcasting received on each
port. The packets are discarded if the respective count exceeds a programmed
threshold in a given time interval.
3.2.2.2
Classifier and filter rule database

There are 3 main functions in classification:
VLAN ID determination
Priority determination
Egress port determination
Both storm control and per port rate limit only apply to E-LAN service bearing on the port,
dont apply to E-Line service.
Classification at UNI
At UNI port, ingress frames are mapped into services according to configurable mapping
rule (also known as: configuration rule). Priority between the classification rules defined
in a port is configurable on the port basis.
In First Mile 200 R2.5.1, the mapping field supported on UNI and NNI ports are
different. In addition, the mapping field used for E-Line service and E-LAN service on
UNI port is different either.
Features
There are two kinds of mapping rules existing on the UNI port of a service: service
mapping rule and QoS mapping rule.
Mapping fields on UNI port for E-Line service:
MAC DA (Destination Address)
MAC SA (Source Address)

VLAN priority (C-tag)
VLAN ID (C-tag)
CVLAN untagging
EtherType
Protocol Type
Source IP address
Destination IP address
L4 source port
L4 destination port
DSCP
A combination of rules can also be used to define a service, e.g. VLAN ID=100 AND
DSCP = 32.
Mapping fields on UNI port for E-LAN service:
MAC SA
VLAN ID (C-tag)
Source IP address
untagged traffic or remaining traffic (all the traffic not compliant to rules defined for
other services)
The mapping rule for E-LAN service on UNI port has the following limitations:
MAC SA/Source IP address are per system based
For a single mapping rule, only one field can be used for classification
Priority of these fields is fixed as (from highest to lowest): VLAN ID, MAC SA, Source
IP address, untagged traffic/remaining traffic
Mapping on broadcast/unicast/multicast
First Mile 200 supports the classification of broadcast, unicast, and multicast
traffic. A service can be configured to either single-CoS service or multi-CoS
service.
For a single-CoS service, all the traffic on the service will be enqueued with the same
queue.
For a multi-CoS service, the different flows of the services will be enqueued with the
different queues.
For a single CoS E-Line and E-LAN service, there is one or two UNI ports on the service
and one or more service mapping rules on a certain UNI. All the UNI and the underlying
service mapping rules use the same global service CoS.
For a multi-CoS E-Line and E-LAN service, there is one or two UNI ports on the service
and one or more service mapping rules on a certain UNI. Each underlying QoS mapping
rule has its own CoS.
Features
On NNI port, only source port and SVID are used for classification.
Order mapping rules
It is possible that a single frame can be matched into multiple mapping rules. Thus
mapping rules must be ordered to avoid the confusion. User should assign a matching
priority for each rule and the mapping rule with lower index number will be matched first.
W hen re-ordering the rules, all services running on that port need to be disabled first.
Then after the mapping rules have been changed successfully, all the services will be
up again. 128 E-LAN and 256 E-Line services are also supported in First Mile 200
R2.5.1. And the maximum of total service is 256 in any case.
VLAN manipulation
VLAN translation only applies on UNI port. On UNI port, only untagged and C-tagged
frame can be accepted. W hen these frames enter switch, a service VLAN tag (S-tag) is
assigned to packets belonging to a service, that is, to packets matching the classification
rules defined for the service.
Transparent mode: the C-tag is not modified and kept as it is, S-tag is added prior
to C-tag at ingress UNI and S-tag is removed at egress UNI
Translation mode: for those services whose classifier is VLAN ID, C-tag is removed
before adding S-tag at ingress UNI. And at egress UNI, the C-tag is added and the
S-tag is removed
W hen the packet leaves the UNI port, it is always C-tagged or untagged.
At NNI, S-tag of ingress traffic is transmitted transparently. An example of traffic flow is
depicted in Figure 11.
Features
Figure 11
VLAN manipulation
Priority determination
At UNI, after classification, a Class of Service is assigned to the traffic. Options are:
All traffic of a service is mapped to the same CoS
Traffic of a service is assigned to different Classes (Multi QoS). Multi QoS

classification is based on mapping rules for both untagged and tagged traffic
Egress port determination

For E-Line service, egress port is determined by the classification.
For E-LAN service, egress port is determined by VLAN-aware L2 bridging.
3.2.2.3
Bandwidth profiles and traffic policing

Bandwidth profile
One of the attributes of Ethernet service is bandwidth profile. From customer
perspective, bandwidth profile specifies the average rate of committed and
excessive customers frames allowed into service providers network on UNI port,
according to the definition of Metro Ethernet Forum (MEF).
A bandwidth profile has four major parameters: CIR (Committed Information Rate), PIR
(Peak Information Rate), CBS (CIR Burst Size), and PBS (PIR Burst Size). The
definitions and explanations of these parameters can be found in a whitepaper of MEF
on its website http://metroethernetforum.org/PDF_Documents/Bandwidth-Profiles-for-
Features
Ethernet-Services.pdf. Note that bandwidth profile parameter Color Mode is not supported by the current release of First Mile 200, which means that only color-blind
mode is supported. Note also that MEF uses EIR (Excessive Information Rate)
instead of PIR for the same meaning.
First Mile 200 supports four types of bandwidth profile:
Per UNI bandwidth profile
Per service bandwidth profile

Per CoS bandwidth profile
Per mapping rule bandwidth profile
Figure 12 below illustrates the effect of each type of bandwidth profile applied to
Ethernet services.
Figure 12
Bandwidth profiles
A service can be applied with only one type of bandwidth profile. However, a service
can have multiple bandwidth profiles of the same type (either the type of per CoS bandwidth profile or the type of per mapping rule bandwidth profile). Likewise, when there are
multiple services on a UNI, each service can have its own bandwidth profiles of single
type except the case where per UNI bandwidth profile is applied to the UNI.
Per UNI bandwidth profile
The ingress bandwidth profile provides a bandwidth profile that applies to all the ingress
traffic on an UNI port, even in case where there are several services on this port. It takes
effect only when none of the other types of bandwidth profile (per-service bandwidth
profile, per-CoS bandwidth profile, and per mapping rule bandwidth profile) is applied to
the services bound to the port. On WebLCT, per UNI Bandwidth Profile is shown as Port
Bandwidth Profile.
Features
Per service bandwidth profile

This type of bandwidth profile is applied to the traffic of an E-Line or E-LAN service on
an UNI port in any case of either Single-CoS or Multi-CoS enabled for the services.
Per CoS bandwidth profile
This type of bandwidth profile can be applied to a service when Multi-CoS is enabled for
the service. Instead of specifying the bandwidth for the whole service, per CoS bandwidth profile specifies the bandwidth of each class of traffic of the service.
Per mapping rule bandwidth profile
This type of bandwidth profile can be applied to each mapping rule of a service. Refer
to 3.2.2.2 Classifier and filter rule database for the details of service mapping rules.
Other traffic policers
W hole Traffic Policer is an independent traffic policer that can be applied to a port and
limit the rate of all the traffic on this port. Compared with Port Bandwidth Profile, it has
only one rate that throttles the whole traffic on a port. In most cases, W hole Traffic
Policer is not used because each service has its own traffic policer. In this case, W hole
Traffic Policer should be disabled.
BC/MC/Unknown Policer is the traffic policer that limits all the Broadcast, Multicast and
Unknown-Address traffic rate on a port for all the E-LAN services on this port.
Traffic policing
One of the key QoS components to enforce bandwidth profile is traffic policing on UNI.
Other components include congestion control and queue scheduling.
An Ethernet frame received on UNI is considered as in-profile if it conforms to the
bandwidth profile, otherwise it is considered as out-of-profile. Traffic policing determines
whether a frame is in-profile or out-of-profile and marks the result for the frame
accordingly so that the other QoS components can handle the frame in the correct way.
First Mile 200 supports two-rate three-color-marker (TrTCM) mechanism. At the point
when a frame is received on UNI port, traffic policer calculates the traffic rate by using
dual- token-bucket algorithm. The rate is then compared against the bandwidth profile
assigned to the service the frame belongs to and the frame is processed as below
depending on the result of policing:
1
If the rate is below or equal to CIR, the frame is perceived as in-profile and is marked
green on the color- bit allocated to the frame. The frame is then sent to the egress
queue, waiting for the next step of processing. Normally, green frames will always
get to its destination without being dropped. This is how CIR is ensured end-to-end.
If the rate is above PIR, the frame is perceived as out-of-profile and is marked red
and dropped right away.
If the rate is between CIR and PIR, the frame is still in-profile (in the sense of PIR)
but is marked yellow and sent to the egress queue waiting for the next step of
processing. If the frame does not experience congestion, it will get to its destination.
Otherwise, it may or may not be dropped. In other words, the delivery of yellow
frame is not ensured.
For detailed description of TrTCM, please refer to IETF RFC2698.
3.2.2.4
Features
Congestion avoidance
The simple Random Early Detection (sRED) is implemented to prevent TCP
synchronization by randomly discarding packets as interface's output queue begins to
fill. First Mile 200 provides a color-aware, probabilistic dropping mechanism, which is
dependent upon the instantaneous queue size. This proactive approach starts
discarding specific colored packets before the packet buffer becomes full. Each time a
packet is received, the current queue depth is examined.
If the queue depth is less than the low threshold (minimum), there is minimal or no
congestion and the packet is enqueued.
If the queue depth is between the two thresholds (minimum and maximum), the
congestion is determined to be moderate and the packet will be dropped according to
the drop rate.
If the queue depth is above high threshold (maximum), all the yellow packets are
dropped.
sRED only works for yellow packets. The green packets will be dropped only when the
buffer becomes full. All the red packets are dropped.
3.2.2.5
Scheduling
The following scheduling modes are supported in First Mile 200:
Strict Priority (SP)
Weighted Round Robin (W RR)
Weighted Deficit Round Robin (WDRR)
SP + W RR/DRR
Strict Priority
The strict priority method schedules the access to the egress port across the QoS
queues from highest QoS queue index to the lowest. The purpose is to provide lower
latency service to the higher QoS classes of traffic.
The maximum and minimum metering mechanisms may be used to influence the
behavior of the scheduler. For example, if the bandwidth exceeds the maximum meter
of a high priority queue, even there are packets in the queue, the low priority queue will
be served.
Weighted Round Robin
The WRR scheduler provides a weighted packet round robin scheme across the QoS
queues. The purpose is to provide a weighted access to the egress port bandwidth (at
a packet level).
The scheduler will select one packet from each QoS queue and go around all active
queues that have a pending packet. The weights will be programmed with each QoS
queue based on the desired packet distribution. The unit of the weight is one packet that
can represent anywhere from 64 bytes to 9216 bytes jumbo frames. And the range of
weight varies from 1 to 127. By default the weight from QoS 7 to QoS 0 shall be
8:7:6:5:4:3:2:1.
Weighted Deficit Round Robin
An inherent limitation of the WRR mode is that bandwidth is allocated in terms of
packets. WRR works well if the average packet size of each coarse-grained CoS queue
Features
flow is known. In most instances, however, this attribute is traffic-dependent and can
vary over time. DRR provides a bandwidth allocation scheduler mode that takes into
account the variably sized packet issue by maintaining sufficient state information when
arbitrating across the CoS queues. In DRR scheduler, queues are served in round robin
order while taking account two state variables: the quantum and credit counter. Each
CoS queue has associated with it a configurable quantum, similar to a WRR weight
value. However, the unit for the quantum is in bytes. The purpose of the credit counter
is to track the overuse of bandwidth by a particular CoS queue relative to its specified
quantum.
A set of queues is serviced by the DRR scheduler, where each queue is associated with
a particular QoS. These queues are served in round robin order while taking into
account two state variables: the quantum and credit counter. Each QoS queue has a
configurable quantum, similar to a W RR weight value. However, the unit for the quantum
is in bytes. The credit counter is to track the overuse of bandwidth by a particular QoS
queue relative to its specified quantum. The weight of each QoS queue can be selected
by operator. The range of weight varies from 1 to 127. By default the weight from QoS
7 to QoS 0 shall be 8:7:6:5:4:3:2:1.
SP + WRR
The combination of SP + WRR is supported in First Mile 200. A certain number of QoS
queues out of 8 on a egress port can be selected to work in strict priority mode, the rest
queues on the port work in WRR mode. In this case, strict priority queues are serviced
first in the order of their QoS numbering, the rest QoS queues are serviced in WRR
manner.
It is possible to enable all QoS queues either in SP mode or WRR mode, or one part in
SP mode and the other in WRR mode. But the queues with SP mode must have higher
index and the index must be consecutive. The weight of each queue shall be
configurable from 1 to 127, by default all queues shall be in WRR mode with the ratio
8:7:6:5:4:3:2:1.
SP + DRR
In scheduling mode of SP + DRR, a certain number of QoS queues out of 8 on an egress
port can be selected to work in SP mode, the rest queues on the port work in DRR mode.
It is possible to enable all QoS queues either in SP mode or DRR mode, or one part in
SP mode and the other in DRR mode. But the queues with SP mode must have higher
index and the index must be consecutive. The weight of each queue shall be
configurable from 1 to 127, by default all queues shall be in DRR mode with the ratio
8:7:6:5:4:3:2:1.
3.2.2.6
CoS queue and egress port rate metering (Shaping)

Traffic shaping is supported across each egress port as well as across each QoS queue.
Configurable port shaping burst is used. The port shaping burst range is 0 Bytes to 16
Mbytes in step of 4096 Bytes. The port shaping default burst size is 4096 Bytes.
On CoS queue level, both maximum and minimum rate metering are supported.
Minimum bandwidth meter is to enable operators to provide strict minimum bandwidth
guarantees on a per CoS granularity. The range of the minimum bandwidth setting for
each CoS queue is between 64 Kbps to 1 Gbps, in 64 Kbps increments.
Features
Maximum bandwidth meter is to enable operators to provide strict maximum bandwidth

limitation on per CoS granularity. The range of the maximum bandwidth setting for each
CoS queue is between 64 Kbps to 1 Gbps, in 64 Kbps increments.
On egress port level, only maximum rate metering is supported with the same range as
CoS level.
For each CoS queue, maximum rate meter > minimum rate meter must be ensured.
3.2.3
Ethernet OAM
OAM stands for Operations, Administrations, and Maintenance functions. It is a general
term used to describe the processes, activities, tools, standards, etc. involved with
operating, administering, managing and maintaining any system. Though the term, and
the concept, originated in the wired telephony world, the discipline has expanded to
other spheres in which the same sorts of work are done, including cable television and
many aspects of Internet service and network operation. Ethernet OAM mainly includes
two parts:
Connectivity Fault Management (CFM)

CFM defines standardized continuity checks, loopbacks and link trace for fault
management capabilities in enterprise and carrier networks. This standard also
partitions the network into 8 hierarchical administrative domains.
3.2.3.1
Performance Monitor (PM)

PM defines performance monitoring measurements such as frame loss ratio, frame
delay and frame delay variation to assist with SLA assurance and capacity planning .
For fault management, the standard defines continuity checks, loopbacks, link trace
and alarm suppression (AIS, RDI) for effective fault detection, verification, isolation
and notification in carrier networks.
Continuity check message (CCM)

The Continuity Check Message provides a means to detect connectivity failures in an
Maintenance Association (MA). CCMs are multicast messages.
Due to First Mile 200 R2.5.1 CPU capacity limitation, if CPU consumes too much
capacity on CCM, CPU may be too busy to handle other tasks. In order to make the
system more stable, some limitations are added to OAM function:
MD, MA, MEP number
Support 16 MD per system

MD level 0 - 7, default MD level is 0.
Support char string format, the maximum string length is 20 bytes.
Support 64 MA per system
Support char string, primary VID. For char string, the maximum string length is
20 bytes. The primary VID value range shall be 51 - 4094.
Each MA can support the following CCM interval: 3.33ms, 10ms, 100ms, and 1s.
Support 64 MEP per system
Support both service level and link level MEP.
Only support down MEP.
For each MEP, there is only one RMEP.
64 MA can be allocated to arbitrary MD, and each MA can only have one MEP
Features
CCM
Only support 64 P2P CCM flow, each CCM flow supports 3.33ms, 10ms, 100ms,
1s CCM interval
Not support STP and CCM at the same port same VLAN
Support MEP on LAG

In some cases, service traffic goes through one LAG member port, and CCM
which monitors the service goes to other LAG member port, then even if the data
traffic is interrupted, CCM will still result OK. So it is not recommended to configure MEP on LAG.
3.2.3.2
Support fast CCM over LPG
Loopback
Loopback messages are unicast and multicast frames that a Maintenance End Point
(MEP) transmits. It is used to verify the connectivity of a MEP with a Maintenance Intermediate Points (MIP) or peer MEPs. They are similar in concept to an Internet Control
Message Protocol (ICMP) Echo (Ping) messages, sending Loopback to successive
MIPs in order to determine the location of a fault. Sending a high volume of Loopback
Messages can test bandwidth, reliability, or jitter of a service, which is similar to flood
ping. A MEP can send a Loopback to any MEP or MIP in the service. Unlike CCMs,
Loopback messages are administratively initiated and stopped.
The minimum LB message interval is 1s. In this release only 1s and 10s intervals are
supported. The total LB sessions supported are 1s x 8 and 10s x128.
3.2.3.3
AIS
Ethernet alarm indication signal function (ETH-AIS) is used to suppress alarms
following detection of defect conditions at the server (sub-) layer. Due to independent
restoration capabilities provided within the spanning tree protocol (STP) environments, ETH
AIS is not expected to be applied in the STP environments.
3.2.3.4
RDI
Ethernet remote defect indication function (ETH-RDI) can be used by a MEP to
communicate to its peer MEPs that a defect condition has been encountered. ETH-RDI
is used only when ETH-CC transmission is enabled.
3.2.3.5
Loss measurement
OAM functions for performance monitoring allow measurement of different performance
parameters. The performance parameters are defined for point-to-point Ethernet
connections. First Mile 200 R2.5.1 covers the following performance:
Frame loss ratio
Frame delay
Ethernet loss measurement can be performed in two ways:
Dual-ended Ethernet loss measurement

It is used as proactive OAM for performance monitoring and is applied to fault
management. In this case, each MEP sends periodic dual-ended frames with loss
Features
measurement information to its peer MEP to facilitate frame loss measurements at

the peer MEP. Each MEP terminates the dual-ended frames with loss
measurement information and makes the near-end and far-end loss
measurements.
Single-ended Ethernet loss measurement

It is used for on-demand OAM. In this case, a MEP sends frames with loss
measurement request information to its peer MEP and receives frames with loss
measurement reply information from its peer MEP to carry out loss measurements.
The minimum LM message interval is 1s. In this release only 1s and 10s intervals are
supported. The total LM sessions supported are 1s x 8 and 10s x128.
3.2.3.6
Delay measurement
Frame delay can be specified as round-trip delay for a frame. It is defined as the time
elapsed since the start of transmission of the first bit of the frame by a source node until
the reception of the last bit of the loopbacked frame by the same source node. The
loopback is performed at the frame's destination node.
Delay measurement can be used for on-demand OAM to measure frame delay and
frame delay variation. Frame delay and frame delay variation measurements are performed by sending periodic frames with delay measurement information to the peer
MEP and receiving frames with delay measurement information from the peer MEP
during the diagnostic interval. Each MEP may perform frame delay and frame delay
variation measurement. When a MEP is enabled to generate frames with delay
measurement information, it periodically sends frames with delay measurement
information to its peer MEP. When a MEP is enabled to generate frames with delay
measurement information, it also expects to receive frames with delay measurement
information from its peer MEP.
Delay measurement can be performed in two ways:
One-way delay measurement

Each MEP sends a frame with one-way delay measurement information to its peer
MEP to facilitate one-way frame delay and/or one-way frame delay variation
measurements at the peer MEP. If the clocks between the two MEPs are
synchronized, one-way frame delay measurement can be carried out. Otherwise,
only one-way frame delay variation measurement can be performed.
Two-way delay measurement

A MEP sends frames with delay measurement request information to its peer MEP
and receives frames with delay measurement reply information from its peer MEP
to carry out two-way frame delay and two-way frame delay variation measurements.
The minimum DM message interval is 1s. In this release only 1s and 10s intervals are
supported. The total DM sessions supported are 1s x 8 and 10s x128.
3.2.4
Link Layer Discovery Protocol (LLDP)

LLDP is supported in First Mile 200 R2.5.1 to advertise the system key capabilities on
the Ethernet LAN and also learn the key capabilities of other systems on the same
Ethernet LAN. Information like system name and description, IP management address,
etc. can be sent or received as LLDPDU (LLDP Data Unit) for every station to know
their neighbors. LLDP frames are sent at a fixed rate on each port of every station and no
acknowledgement is expected from the receiver. It is so-called one way connectionless
data link layer protocol which runs on MAC layer.
Features
LLDP allows the NMS to build the physical topology of the network under its supervision.
The NMS can only get a complete picture of the controlled network when all the NEs
support LLDP.
For detailed information of LLDP, please refer to IEEE 802.1 AB TM -2005.
3.2.5
Bridging modes
L2 bridging is compliant with 802.1ad Provider Bridge, forwarding is performed
according to {S-VID, DA} pair. {S-VID, DA} pair is automatically learned by the bridge,
protection is based on RSTP or MSTP reaction to topology change. It only applies to ELAN service, for E-Line service uses point to point rule, typically {Source Port, VLAN
ID}.
For UNI port:
In IEEE802.1Q mode, First Mile 200 supports xSTP peer on any port.
3.3 TDM circuit emulation service (CES)

The TDMoP processing in First Mile 200 complies with the RFC5086 standard for
CESoP and RFC4553 for SAToP. The packet format is IPv4/IPv6 PSN with UDP (User
Data Protocol) demultiplexing and the basic NxDS0 (Digital Service level 0) service is
supported.
The interworking function (IWF) encapsulates multiple DS0 signals into a single Pseudo
Wire (PW). The input DS0 signals is demultiplexed from TDM signal. Multiple TDM interfaces can be bound to a single Ethernet Virtual Connection (EVC). The maxim um
number of supported PWs is 8.
Figure 13
IW F at the PSN bound
Features
Figure 14
IW F at the CE bound
The system is hardware ready for mapping of time slots pertaining to one E1/T1/J1 interface to multiple EVC in future releases.
Two FPGA firmware is provided. One is used to support the E1 CESoP and E1
SAToP. And the other is used to support T1/J1 CESoP. The operator can configure
CESoP and SAToP services by using an E1/T1/J1 interface. At a certain time, only one
mode will be configured through a certain E1/T1/J1 interface. The operator can switch
CESoP/SAToP mode from NMS and cold-reboot the system. After switching finished,
all TDM service related configuration on the interface will be removed.
W hen the operator switches from one mode to another, First Mile 200 need to be
cold rebooted.
The two FPGA firmware and SW firmware will be integrated to a single package whe n
delivered to customer.
3.3.1
CESoP for E1/T1/J1

In First Mile 200, Circuit Emulation Services over Packet (CESoP) is supported. Pseudo
Wire Emulation (PWE) function encapsulates a TDM signal stream into packets and the
packets are sent via EVC tunnel towards the far end PWE device. The packets are
decapsulated back to TDM signal in the far end PWE device. The PWE function
decapsulates a TDM signal from a packet stream received within a PSN tunnel and
transmits the signal as a TDM link. The PWE function provides the control of EVC tunnel
establishment and maintenance. The following common configuration has to be applied
at the PWE entities:
3.3.2
List of TDM time slots per TDM frame
Number of TDM frames per packet
Number of PSN tunnels per PWE device
SAToP for E1
In First Mile 200, Structure-Agnostic Time Division Multiplexing (TDM) over Packet is
also supported. But only E1 SAToP is supported. Firstly, a global variable TDM
Features
mode need to be selected. After selecting the TDM interface E1 mode, SAToP can be
configured thereafter.
SAToP addresses only structure-agnostic transport, i.e., the protocol completely
disregards any structure that may possibly be imposed on these signals, in particular
the structure imposed by standard TDM framing. This emulation is referred to as
emulation of unstructured TDM circuits. The following common configuration has to be
applied at the PWE entities:
Admin status
Number of TDM frames per packet

Number of PSN tunnels per PWE device
Due to the fact that SAToP carries TDM streams in their entirety, any TDM
signalling/framing information will be handled transparently and without any specific
processing. Therefore the emulated TDM services are more sensitive to the PSN
packet loss, when compared to Structure Aware emulation that locally regenerates TDM
framing/signalling information.
3.3.3
Mixed configuration of SAToP with CESoP for E1

First Mile 200 also supports the mixed configuration of SAToP with CESoP
for E1. The operator can configure an E1 interface to SAToP or CESoP mode. At a
certain time, only one mode shall be configured on a certain E1 interface. The
configuration for the E1 interfaces is independent. i.e. some of the E1 interfaces can be
configured to CESoP, while the others can be configured to SAToP. The operator can
switch between SAToP/CESoP modes from NMS. After the switching, all TDM service
related configuration of the E1 interface will be removed.
3.4 Protection
3.4.1
LPG protection
In order to provide resilience against hardware failures of ODU, First Mile 200 supports
link protection group (LPG). There are up to 4 electrical Gigabit Ethernet interfaces for
connection to the ODUs. Therefore it is possible to install up to 2 pairs of protecting
ODUs. Mixed configuration can be supported, for example (1+1) + 2x(1+0). The
protection scheme supports the ODU system types: 1+1 HSBY, 2+0 XPIC, 2+0 FD, 1+1
FD, 1+1 SD, etc. First Mile 200 supports ODU swapping and repairing in LPG without
traffic interruption.
In Figure 15, two ODUs are configured as 1 + 1 protection pair, the other 2 ODUs are
connected to separate radio links. In the protection scheme it can be revertive or nonrevertive based on the configuration.
Features
Figure 15
Mixed protection configuration
The 1+1 HSBY protection involves a pair of ODUs, one is active and the other is
standby. Traffic is routed to both ODUs, in case of one ODU failure, the standby ODU
becomes active.
3.4.1.1
LPG configuration
First Mile 200 supports two LPGs. LPG1 is the group of GE electrical port 1 & 2;
LPG2 is the group of GE electrical port 3 & 4.
First Mile 200 LPG configuration has the following features:
LPG cannot be empty (with no members) and at most be two member ports.
LPG members can only be physical ports.

LPG can be administratively enabled or disabled.
W hen a LPG is created, LPG will automatically receive the configurable attributes of
the first added port. The second port will inherit the configurable attributes of the
LPG.
W hen a port is removed from LPG, its configurable attributes will stay the same.
If any member port is link up status, LPG is link up status.
If all member ports are link down status, LPG is link down status.
Member port link status can be changed by E-CCM and RDI.
Two kinds of CCM are defined in protection scheme:
E-CCM: Continuity check between IDU and ODU.
P-CCM: Continuity check between two protected ODUs.
CCM time interval: The time interval for generation and detection of E-CCM. It can be
configured from a minimum of 10 ms to a maximum of 1s. The default value is 100 ms
Before to set this parameter, refer to the documentation of ODU used in order to verify
the compatibility.
Features
3.4.2
xSTP for E-LAN service
Figure 16
MSTP illustration
First Mile 200 R2.5.1 implements the IEEE 802.1W Rapid Spanning Tree Protocol
(RSTP) and the IEEE 802.1S Multiple STP (MSTP). RSTP provides rapid convergence
of the spanning tree. MSTP, which uses RSTP to provide rapid convergence, enables
VLANs to be grouped into a spanning-tree instance. It provides for multiple forwarding
paths for data traffic, and enables load balancing. It improves the fault tolerance of the
network because a failure in one instance (forwarding path) does not affect the other
instances (forwarding paths).
The most common initial deployment of MSTP and RSTP is in the backbone and
distribution layers of network. The rapid spanning tree algorithm and protocol (RSTP)
provides full and symmetric connectivity in a bridged LAN. It provides rapid
reconfiguration of the spanning tree active topology in case of physical network
changes with reduced port states as forwarding, learning and discarding only.
The multiple spanning tree protocol (MSTP) allows frames assigned to different VLANs
to follow separate paths. Each path is based on an independent multiple spanning tree
instance within multiple spanning tree regions. MSTP can support 8 MSTP instance.
Both RSTP and MSTP improve the operation of the spanning tree while maintaining
backward compatibility with equipment that is based on the (original) 802.1D spanning
tree.
BPDU processing
At UNI port, there are three ways to process STP/RSTP/MSTP BPDU:
Peering: Processed at the UNI. The subscriber network becomes part of the network
for which a single STP is calculated
Tunneling: Tunneled by the service. The service is perceived by the subscriber

network as a single segment. In this case, subscriber STP can be created between
its sites
Features
Discarding: Dropped at the UNI. The subscriber should manually ensure that
network does not contain loops going through the service
Faster Hello Time

In RSTP/MSTP, standard Hello Time range is 1s~10s. In order to improve the
convergence time, First Mile 200 can set Hello Time between 100ms and 10s. 100ms
Hello Time will significantly reduce the convergence time, compared with
1s Hello Time.
Edge Port
W hen linkup a normal MSTP/RSTP port (not Edge Port), it will wait for 2 *
ForwardingDelay before change to forwarding state if there is no peer device that
support MSTP/RSTP Port.
First Mile 200 R2.5.1 has various enhancements in xSTP. It supports ODU
management when xSTP is running over LPG and fast topology update.
For detailed information of STP, RSTP, and MSTP, please refer to IEEE 802.1D,
802.1W, and 802.1 respectively.
3.4.3
LAG protection
Link aggregation grouping allows multiple links to be aggregated together to form a Link
Aggregation Group (LAG). A MAC client treats the LAG as if it is a single logical link. For
bridge functionality, the LAG is considered as a single bridge port. LAG consists of N
parallel full duplex point-to-point links. First Mile 200 R2.5.1 only supports static LAG
configuration.
LAG provides the following functionality:
Increased bandwidth
The capacity of multiple links is combined into one logical link.

Linearly incremental bandwidth
Increased availability
Load sharing
Rapid configuration and reconfiguration
Deterministic behavior
Low risk of duplication or mis-ordering Support of

existing IEEE 802.3 MAC clients Backwards
compatibility with aggregation Accommodation of
differing capabilities constraints No change to the

IEEE 802.3 frame format
Network management support
Only six Ethernet ports on the front panel can be configured for LAG.
There are six modes of LAG distribution algorithm, see in Table 5.
Mode
Hashing criteria
SA, VLAN, EtherType, source module and port ID
DA, VLAN, EtherType, source module and port ID
Table 5
Hash mode operation
Features
Mode
3
SA-XOR-DA, VLAN, EtherType, source module and port ID
SIP and source TCP/UDP port
DIP and destination TCP/UDP port
SIP-XOR-DIP, source and destination TCP/UDP port
Table 5
3.4.4
Hashing criteria
Hash mode operation (Cont.)
CESoP and SAToP linear protection

In First Mile 200, CESoP/SAToP linear protection is implemented. There are two paths
on packet network between two end nodes of this CESoP/SAToP protection E-Line
service. The protection uses one path as a working path and the other one as protection
path. This service does not support untagged services. For one CESoP/SAToP
protection service, once the working path broken, the CESoP/SAToP traffic will be
transported on redundancy path. The protection switch-over time is less than 50 ms.
The protection switch-over time 50 ms is required only for bi-direction broken on forwarding path. The Uni-direction failure protection will be added in the future release.
CESoP/SAToP linear protection service over LPG and LAG is supported.
CESoP/SAToP linear protection switching time over LPG and LAG is 50 ms.
Switching command
Operator can issue commands to make CES traffic switching to Working path or
Protection path.
Switch to working path

Before issuing switch to working command, it is recommended to use OAM like
method to check the working path status. After issuing this command, it can override
normal protective switching mechanisms. It will check Hold-switch time, if Holdswitch time does not return to zero, the command will be aborted.
Switch to protection path

Before issuing switch to protection command, it is recommended to use OAM like
method to check the protection path status. After issuing this command, it can
override protection auto-switch mechanisms. It will check Hold-switch time, if Holdswitch time does not return to zero, the command will be aborted.
The time between switching from Protection to working and vice versa is hold-switch
time. The default value is 1s.
3.4.5
G.8031 linear protection

First Mile 200 supports linear APS (Automatic Protection Switching) which complies
with ITU-T G.8010/Y.1306. G.8031 linear protection can be applied only to point-topoint E- Line transport service. It requires Ethernet OAM (licensed) as pre-condition
because G.8031 linear protection needs to make use of OAM CCM to detect the link
status of both working and protection paths.
The following performance and features are to be considered when applying First Mile
200 G.8031 linear protection.
Features
First Mile 200 supports 24 protection services.
The switch-over time varies with the number of protected E-Line services in one
First Mile 200 that are affected by the failure on the working path. For example, if
only one E-line service in First Mile 200 is affected by a failure, the switch-over time
is less than 50 ms; if 24 protected services in one First Mile 200 are affected by a
failure, the switch-over time is less than 400 ms.
Both revertive and non-revertive modes are supported.

In revertive mode, when the working path is repaired, traffic will be switched back to
the working path after WTR (W ait to Restore) time expires. The WTR period range
is: 1 min to 15 min in steps of 1 min, the default value is 5 min.
In non-revertive mode, when the working path is repaired, traffic will stay on the protection path. Revertive mode is the default mode.
WebLCT supports the following G.8031 commands:
Manual switch normal traffic signal-to-working

When there is no failure on either the working path or the protection path in nonrevertive mode, this command forces a normal traffic signal to switch from the
working path.
Manual switch normal traffic signal-to-protection

When there is no failure on either the working path or the protection path, this
command forces a normal traffic signal to switch from the protection path.
Clear
This command clears the active near end Lockout of Protection, Forced Switch,
Manual Switch and WTR state.
Lockout of protection
This command prevents a working signal from switching from working path to
protection path. This effectively disables the protection switch-over until Lockout
command is dismissed.
Force switch normal traffic signal-to-protection
This command forces a normal traffic signal to switch to the protection path
when there is no failure on the protection path.
Hold-off timer.
Hold-off timer is intended for controlling when the switch-over takes place once 3
consecutive CCM messages are found to get lost on the working path.
The range of the hold-off timer is 500 ms to 10 s in steps of 100 ms. The default
value is 0.
G.8031 linear protection interworking with other functions
SVLAN for working path and protection path

Two SVLANs are allocated for a G.8031 protected E-Line service, one on the
working path and another on the protection path. Even if there is no service traffic
on one of the paths, APS and CCM messages are still sent over it.
Features
STP
G.8031 does not change any topology and thus STP active topology information
is not affected by G.8031. Meanwhile, since STP cannot be applied to E-Line
service but only to E-LAN service, there is no conflict between G.8031 and STP.
CCM
CCM must run on each protected VLAN path, and CCM Loss / RDI / Link Down is
used to trigger linear protection switch-over. It means that G.8031 requires Ethernet
OAM so the license for G.8031 and Ethernet OAM have to be installed.
LPG
LPG is treated as a normal port in G.8031 linear protection. LPG protection is faster
than linear protection when there are lots of services on the LPG.G.8031.
For example, if the LPG carries 24 services and a failure happens on the active
ODU, both G.8031 and LPG will start to switch. Once the LPG has finished
switching, the CCM LOS of the remaining G.8031 services which havent finished
switching will be cleared, thus the remaining G.8031 services will continue to
choose the LPG as their active path.
Reboot
During NE doing a warm reboot, First Mile 200 cannot send out APS PDU, but can
still send out CCM PDU. In this period, if there is service failure, NE cannot protect
the failure service. After NE finishes warm reboot, First Mile 200 will check the
service status and continue to finish the protection.
During NE doing a cold reboot, the protected service will be interrupted, after the
system boot up, the protected service will be restored again.
In general, after reboot (warm or cold), the traffic can be on working or protection
path randomly if there is no manual command. For revertive mode, after the W TR
timer expires, the traffic will be on working path. For non-revertive mode, if user
needs to switch the traffic to working path, user can use lockout command, and the n
clears it.
3.4.6
G.8032 ring protection

First Mile 200 R2.5.1 supports the Ethernet ring protection which is complied with ITUT G.8032/Y.1344 Ethernet ring protection switching 2008. G.8032 ring protection
requires Ethernet OAM (licensed) as pre-condition because OAM is the mechanism
used by G.8032 to detect failures on the working path. In Figure 17 shows the G.8032
supported ring topology by First Mile 200.
Features
Figure 17
First Mile 200 G.8032 supported ring topology
Following features are supported in First Mile 200 G.8032 ring protection:
Only single logical ring protection is supported on one physical ring.
First Mile 200 supports up to 4 single ring protection instances.
The ring ports physical media can be Optical GE, Electrical GE or Microwave.
The revertive mode is supported.

After link failure is repaired, G.8032 restores the normal topology after WTR
timer expires. WTR period can be configured by the operator in 1 min to 12 mins
in step of 1 min; the default value is 5 mins.
Traffic restore time is less than 50 ms when:

3.33 ms CCM is used for monitor ring link
there are less than 8 ring nodes in the ring

only one ring is configured on First Mile 200
First Mile 200 supports the following protection commands:
Force switch - It moves the blocking role of the RPL by blocking a different ring
link followed by unblocking the RPL
Manual switch - In the absence of a failure, this command moves the blocking
role of the RPL by blocking a different ring link and unblocking the RPL
Features
Clear - Clears the active near commands (force switch or manual switch
commands)
Hold-off timer is supported.

Each protection group has a configurable hold-off timer. The hold-off timer is
allowing a server layer protection switch to have a chance to fix the problem before
switching at a client layer. The suggested range of the hold-off timer is 0 to 10
seconds in steps of 100 ms.
Guard timer is supported.

The guard timer is used to prevent ring nodes from receiving outdated R-APS
messages. During the duration of the guard timer, all received R-APS messages
are ignored by the ring protection control process. The period of the guard timer can
be configured by the operator from 100 ms to 2 sec in steps of 100 ms; the default
value is 500 ms.
G.8032 interwoking with other functions
STP
G.8032 and STP can be enabled at the same time at the same port. For some VLAN
(such as Management VLAN) can use STP to protect traffic, while for some VLAN
(such as data traffic VLAN) can use G.8032 to protect traffic.
LPG
First Mile 200 supports G.8032 on LPG ring port. First Mile 200 transmits CCM on
the active LPG link. While the active radio link fails, FPGA based MEP will detect
the failure in 3.5 x 3.33 ms, both ports in LPG will be blocked. After a short time,
LPG will switch to the backup ODU, and then the MEP will clear loss defect. Then
G.8032 will switch the traffic to original topology.
3.5 Synchronization
3.5.1
Synchronization overview
First Mile 200 system can be configured to support the SSM protocol or not by
configuring the Normal Mode or SSM Mode.
Normal Mode
If Normal Mode is selected, the SSM protocol is not supported by system and two
different synchronization sources among all the possible sources are possible to be
selected. While two synchronization sources are selected, one as primary source
and the other as secondary. W hen the primary source is not available, system
automatically uses the secondary one. Once the primary source is recovered,
system comes back to the primary source if the revertive mode is set, or stay on the
secondary source if the non-revertive mode is configured.
SSM (Synchronization Status Message) Mode
In SSM Mode, system supports the SSM protocol in order to select the best
synchronization source according to quality level and priority, in order to inform the
downlink network elements about the quality of the received synchronism.
Features
W hen the mode is switched between SSM Mode and Normal Mode, the clock source
mode will keep unchanged.
Synchronization states
If using internal source, only one synchronization state is foreseen: freerun.
If using external source, the following states are foreseen:
Freerun
This state is selected after startup or after a synchronization reset command.
System will keep working in Freerun mode if no valid source is available.
Locked
This state is selected after the PLL has locked and no synchronization alarm is
present, i.e. a qualified reference source is available at the selected interface.
Holdover
This state is selected when the reference source has been disqualified due to some
problem.
Synchronization subsystem
The First Mile 200 synchronization subsystem is composed of a synchronization
processing unit and a clock unit.
The processing unit performs the clock selection based on synchronization alarms and
on the quality level extracted from received synchronization status message (SSM)
according to ITU-T G.781 standard. The processing unit also generates SSM messages
towards downlink devices and communicates with the SNMP agent.
The clock unit, commanded by processing unit, actuates the following:
source selection
clock de-jittering / handover functions

system clock generation and distribution to interested parts
Figure 18 gives an illustration of First Mile 200 synchronization subsystem.
Features
Figure 18
3.5.2
Synchronization subsystem
Synchronization from TDM interface

Two E1/T1/J1 interfaces can be selected as TDM synchronization output interfaces. The
E1/T1/J1 interface selected as TDM synchronization output interface carries a locally
generated structured E1/T1/J1 with pseudo-random payload in case of no
synchronization alarms. Vice versa it carries full Alarm Indication Signal (AIS) in case
synchronization alarms exist.
The E1/T1/J1 interface selected as TDM synchronization output interface cannot be
bounded to a TDMoP EVC and does not carry usable traffic.
E1/T1/J1 interface can be used as TDM synchronization input interface. System detects
alarms related to the TDM synchronization input interface as in the following:
Features
3.5.3
LOS (local alarm, the traceability to PRS is lost)

LOF (it is only for CESoP)
AIS
RDI
Synchronization from Ethernet interface

Each Ethernet interface can be configured as clock master, clock slave, or for
autonegotiating the clock direction.
If own internal synchronism is selected, the synchronous Ethernet functionality is disabled, the clock direction is determined by the auto-negotiation function on every
Ethernet interface.
If external reference is selected, one interface will be selected as a synchronization
source. On this interface, First Mile 200 will behave as a clock slave recovering the
clock from the data stream and looping it to the TX side; on other interfaces First Mile
200 will behave as a clock master, driving the clock of the interface.
3.5.4
Clock recovery
Following options are supported to retrieve clock of each TDM interface in First Mile
200:
Loop timing
The E1/T1/J1 TX clock is derived from E1/T1/J1 RX clock directly.
Centralized clock (system clock)

The E1/T1/J1 clock is recovered from the system clock. The system clock is tracked
to the external source (Sync Ethernet or E1/T1/J1 interface).
Differential clock recovery

The system clock is used as the common clock and it is required on both edges of
the TDMoP service. The operator must guarantee the system clock has been
correctly configured. Two external clock sources may be chosen as common clock,
the SyncE interface or TDM interface.
3.6 Performance management

The performance managements are based on 15 minutes and 24 hours intervals as in
the following:
current 15 minutes interval
16 15 minutes interval
4 24 hours interval
The actual start of the 15 minutes/24 hours intervals is synchronized by the system date
and time through EMS.
Performance management data for Ethernet port is saved to an XML file. The files are
retrieved by the manager via FTP protocol.
3.6.1
Performance management based Ethernet service

First Mile 200 supports performance management of Ethernet services and the
following measurements are supported:
Green frames/octet number
Features
Yellow frames/octet number
Total frames/octet number
User can select octet or packet as performance management. But the choice is done
before enabling the performance management. User can enable or disable the
performance management per Ethernet service. By default, it is disabled.
Performance management for Ethernet service is for UNI port only.
3.6.2
Performance management based CESoP service

Performance management is to select and store the most important events occurred
on the CESoP connection that can cause impairments on the E1, T1 and J1.
The following measurements are supported:
Jitter buffer underrun / overrun events counter
PDV-drop counter
Wrong packets: sum of stray packets, malformed packets, multiple packets, out-ofsequence-packets
User can enable/disable the performance management per CESoP service. By default it is
disabled. First Mile 200 supports performance management for all the CESoP services.
Performance management for CESoP service is for UNI port only.
3.6.3
Performance management based OAM

First Mile 200 supports the performance management of delay measurement and
packet loss.
Packet loss can be easily summarized per interval
Delay must be processed, e.g., min, average, max delay should be provided per
interval
User can enable or disable the performance management per service. By default, it is
disabled. First Mile 200 supports the performance management for all the OAM
services. However it is with the following limitations:
Only supports E-Line
Calculation on packet loss is per service. It needs per-port and per-service packet
counter statistics. But for example, if a packet is dropped by egress shaping, such a
dropped packet cannot be counted. It will affect the calculation on packet loss
W hen the user is using the OAM LM function, the performance management will be
rejected during this time period, vice versa
3.6.4
Performance monitoring
Performance monitoring (PM) parameters are routinely collected for TDM services
and provide an important maintenance mechanism in TDM networks. The
system supports the gathering of performance statistics related to E1, T1 and J1
signal.
G.826 EB Errored Block
G.826 ES - Errored Second
Features
G.826 SES - Severely Errored Second
G.826 BBE - Background Block Error

G.826 TT - Total Time
G.826 UT- Unavailable time
3.7 Security management

First Mile 200 R2.5.1 aligns security features with Harmony Radio.
IDU embedded SW is modular, all the algorithms and some protocols to be used when
security is enabled is contained in an add-on file. Security is automatically enabled when
the security features has been licensed on the NE. The security features include:
SSH / SFTP
SNMP V3.0
The security add-on package is available for enabling the security features and it
contains:
Only authentication and encryption functionality
Once all security items are configured completely, system realizes the upgrade from
basic mode to secure mode. There are two kinds of secure modes: light mode and
strong mode.
Strong mode:
Only SNMPv3 with AuthPriv is available
SSH/SFTP username/password are the same as SNMPv3 username/password,

and SSH/SFTP does not support Create User/Change Password
Any supporting user for security installation is automatically removed from the
system as soon as the command of security startup is issued
Light mode:
SNMPv3 is available. And SNMPv2c is still available, but answers to public com-
munity are no more available

Telnet/Ftp/Http are supported
Telnet/Ftp username/password are the same as SNMPv3 username/password, and

Telnet/Ftp does not support Create User/Change Password
Any supporting user for security installation can be manually removed from the
system as soon as the command of security startup is issued
Regarding the upgrading of security features, one temporary administrator user is used
to add the first users privilege. As soon as this special user has been created and the
first installation is ended, a command shall be available to trigger the security startup
IDU shall be warm-rebooted and start working in the configured mode. And the
temporary user will be deleted from the system. The following is the upgrade procedure
from basic mode to secure mode:
Get license and add-on security package
Install license and download the security package
Activate the light mode or strong mode
Features
Regarding the upgrading from light mode to strong mode, the only thing is to activate
strong mode and it will be available in future release.
3.7.1
SSH/SFTP
Once the security feature is enabled and the security add-on is installed, First Mile 200
R2.5.1 will support SSH (secure shell) which is based on TCP/IP protocol stack. SSH
allows data to be exchanged between two network devices in secure channel. It is a
substitute for TELNET and supports for the secure file transfer together with SFTP
(Secure File Transfer Protocol). SSH authenticates the users login from a shell on a
remote host and encrypts the traffic exchanged between two parties in order to improve
the security of the communication. SSH does not implement file transfer by itself,
instead it starts the remote file transfer agent and talk to it (SFTP) after the connection
to the remote host is established.
No compression method is supported in First Mile 200 R2.5.1.
3.7.2
SNMPv2c/SNMPv3
An SNMP entity consists of an SNMP engine and one or more associated applications
An SNMP engine provides services for sending and receiving messages, authenticating
and encrypting messages, and controlling accesses to managed objects. There is oneto-one association between an SNMP engine and an SNMP entity.
Security model
The user-based security model is based on some general data: EngineID, EngineBoots,
EngineTime, UserName. EngineID in First Mile 200 R2.5.1 is both the Authoritative
SNMP EngineID and the context EngineID which indicates where the data is coming
from. EngineBoots is a count of the number of times an SNMP engine has rebooted or
re-initialized since the EngineID is last set. EngineTime is the number of seconds since
the EngineBoots counter is last incremented. The UserName is the name for the user
whose secret key is used to possibly authenticate and encrypt the packet.
Key and user management

SNMPv2c uses the notion of communities to establish trust between managers and
agents. Different user classes in First Mile 200 environment are divided into different
communities which are defined for each user class.
In SNMPv3, the community concept is substituted by the username which must match
to ensure a similar minimal authentication. A set of keys is generated from a password
and then these key pairs are made unique to a SNMP engine pair. The users password
must be at least 8 characters long.
A new user can only be created by cloning from another existing user. So there should
be three types of users pre-existing: read-only, read-write and admin user class. Once
the new user is created successfully, the key must be immediately changed and the
template users need to be deleted by the manager.
3.7.3
Features
User class management

The user class defines the privilege levels of access to First Mile 200
and related information. Each user class has its own set of privileges. Higher
classes have higher privileges. A superior class normally inherits all the privileges of
the inferior class.
Admin
Any user of this class has read/write access to the complete set of MIB fields. Moreover, users in this class can change passwords for itself and for the lower class
users.
Read & Write
Any user of this class may read and write all the MIB fields whose property list is
READWRITE, with the exceptions:
Change IP parameters of the NE

Set date and time
Modify SNMP and more generally security parameters

Perform software download and restore or bulk commit operations
ReadOnly
Any user of this class cannot modify whatever parameter in the network element
except the registration data for receiving notifications. Anonymous users are also
allowed with the same privileges of read-only users, but the password is not
required.
Anonymous
Any user of this class is with the same privileges of ReadOnly users, but do not
need any password.
User class
Password string
Protocol map
admin
sysmanager
SNMPv2c, SNMPv3, SSH,

SFTP, FTP, TELNET
readwrite
readwrite
SNMPv2c, SNMPv3, FTP,

SFTP
readonly
readonly
SNMPv2c, SNMPv3, FTP,

SFTP
readonly (anonymous)
any value including null

string
SFTP, FTP
Table 6
Default password for different user classes
Account log
First Mile 200 R2.5.1 embedded software stores a list of records (up to 120 records)
regarding log actions(Login or Logout) performed by users. All successful log actions
will be recorded. Each record includes the following information fields:
IP address of the user
Authentication name or community in case of SNMPv2c
Protocol type
Log action type (login, logout, password)
Features
Date and time of the log action
Once an alarm is triggered, it needs to be downloaded and cleared from EMS. Then NE
clears alarm. Following is the procedure for the alarm and log file:
NE sends the alarm to EMS
Download log file from NE and clears the log file manually
NE clears alarm
3.7.4
Securing management protocols

Availability of the different protocols and corresponding ports according to the security
mode are listed in Table 7.
Port
Protocol
Availability according to security mode

Basic mode
Light mode
Strong
mode
20-TCP
FTP (1)
yes
no
no
20-TCP
SFTP (1) (2)
no
yes
yes
21-TCP
FTP
yes
no
no
21-TCP
SFTP (2)
no
yes
yes
22-TCP
SSH (CLI like)
no
yes
yes
23-TCP
telnet
yes
no
no
80-TCP
HTTP
yes
no
no
123-UDP
SNTP
yes
yes
yes
161-UDP
SNMPv2c
yes
no
no
161-UDP
SNMPv3
yes
no
no
no
yes
no
no
yes
yes
(no auth no privacy)

161-UDP
SNMPv3
(authentication no privacy)
161-UDP
SNMPv3
(authentication and
privacy)
Table 7
Availability of protocols and ports according to the security mode
3.8 Web-based LCT management

Through an embedded W ebLCT program of First Mile 200, user can access First Mile
200 through the network and launch the WebLCT program to monitor, administer and
configure system remotely. All the parameters are divided into different groups, e.g.
Device, NE Management, Clock Sync.
For detailed information, please refer to the Harmony First Mile 200 Rel. 2.5 Operate
and Maintain manual.
3.8.1
Features
DCN configuration auto-recovery

DCN configuration auto-recovery feature cab be used to recover the connectivity
between NMS & IDU in case wrong configuration change has been applied via NMS and
IDU is disconnected with the NMS. Management configuration of IDU includes public IP,
IP mask & IP gateway. On WebLCT, operator can select whether to enable or disable
DCN configuration auto-recovery function. By default the function is disabled.
Application
4 Application
4.1 Network application
First Mile 200 is mainly used in tail and chain site configurations. It is a cost-effective
solution for all sites requiring multi-traffic aggregation, for instance, where 2G networks
BTS are collocated with 3Gs. It fits in the standard BTS outdoor housing, providing a
zero-footprint solution and an extensive operating
temperature range.
With other products of Harmony Radio family, Figure 19 provides a complete mobile
backhauling solution.
Figure 19
A complete mobile backhauling solution
The individual site configurations with First Mile 200 are described in the following chapters.
Application
4.2 Site configurations

4.2.1
Tail site: 3G BTS only
Figure 20
Tail site with 3G BTS only
In this configuration, the 3G BTS is connected to First Mile 200 through the GE interface.
If the BTS is configured for full packet transport, Harmony makes also possible a zero
footprint installation, i.e., BTS is directly connected to Harmony Radio.
4.2.2
Tail site: 2G and 3G BTSs collocation
Figure 21
Tail site with 2G and 3G BTSs collocation
In this configuration, the 3G BTS is connected to First Mile 200 through the GE
interface, while the 2G BTS is connected to First Mile 200 through the E1 interface.
Application
4.2.3
Tail site: 2G, 3G, and 4G BTSs collocation
Figure 22
Tail site with 2G, 3G, and 4G BTSs collocation
First Mile 200 is ready to support 4G traffic as well.
4.2.4
Chain site
Figure 23
Chain site
In this configuration First Mile 200 aggregates local traffic of 2G and 3G BTSs with
traffic collected from the tail site.
Management
5 Management
5.1 Network management using Nokia Siemens Networks
NetAct
Nokia Siemens Networks NetAct (later referred to as NetAct) is the central network
management system for collecting alarms and measurement data from First Mile 200
and associated Harmony Radio in the network. Communication between NetAct and
the network elements is enabled via IP DCN.
Fault and performance management data is collected to NetAct via NetViewer-NetAct
Connector that's integrated to NetViewer EMS.
For more detailed information, please refer to NetAct documentations.
5.2 Network management using NetViewer

NetViewer is a PC-based software application for controlling and monitoring First Mile
200 and associated Harmony Radio.
NetViewer communications with First Mile 200 via IP DCN. It reads and interprets the
information directly from the node and the information can then be easily modified and
sent back to the node.
For more detailed information, please refer to the relevant documents.
5.3 Commissioning Tool

Scope of Commissioning Tool is to support the first installation and upgrade of the
Harmony system (IDU, ODU) with the following tasks:
to configure the E-LAN reachability for all ODUs and IDU with their public IP
addresses, after this operation, it will be possible to address all the management
SNMP agents on the whole system with their public IP addresses and through their
relevant plug-in
to configure 1 + 1 protection relationship between two ODUs (system type,

alignment of GE/Radio parameters)
to configure and align the ODUs parameters inside the Link Protection Group (LPG)
to change topology of an already working system, thus adding/removing an ODU;
with its own public IP address, this means to build up a communication tunnel to
reach each ODU, to configure the DCN data set and to provide the IDU with the
relevant data
Management
5.4 Network management using First Mile 200 R2.5.1 Webbased LCT
Embedded First Mile 200 R2.5.1 W ebLCT program can be launched as a Java program
through the network connection. With the user-friendly GUI, the user can do the
following task:
Device settings
NE management
Clock synchronization setting
Ethernet general configuration
Service management
QoS setting
Protection settings
OAM configuration
Performance settings
Maintenance settings
Security settings
For detailed information about WebLCT and how to manage First Mile 200 using
WebLCT, please refer to the Harmony First Mile 200 Rel.2.5 Operate and Maintain
manual.
5.5 Accessing IDU

First Mile 200 IDU has a default private IP address for local management and a
default public IP address for remote management, see Table 8:
Connection
port
IP address
changeabili
ty
Note
OOB port
192.168.254.100
fixed
This always allows the

operator to access the
device when the out-band
public address is not known.
It cannot be reached from a
different IP subnet since no
default gateway is assignable to this port.
DCN port
192.168.255.100
(default)
changeable
This port can be reached

from a different IP subnet by
means of a gateway.
Table 8
Accessing IDU
5.6 SNMP agent

First Mile 200 has an build-in SNMP (Simple Network Management Protocol) agent
that provides management functions for the whole radio terminal. Fault, performance,
and configuration management functions can be performed using SNMP actions. The
version supported is the SNMP version 2c.
Management
5.7 SNTP, FTP, and Telnet

The SNTP (Simple Network Time Protocol) functionality is used to update the nodes
real time clock by connecting to an NTP server, which must be accessible through the
IP-based DCN. The SNTP can be enabled or disabled in Element Manager.
FTP (File Transfer Protocol) is supported for the purpose of software download and
large file size, e.g., performance monitoring data.
Telnet is supported for remote command interface control.
5.8 Memory Key

First Mile 200 works with a valid Memory Key inserted. The Memory Key is used for
First Mile 200 IDU configuration and licenses backup. It provides an easy IDU
replacement in case of system failure.
The Memory Key must be pre-formatted by the factory and contain a serial number with
the right equipment name. The storage size of Memory Key is 32 Mbit.
The following information is stored in Memory Key:
equipment configuration data
available licenses
Equipment name
System type
Memory Key Product Identification Data (PID)
Memory Key serial number
W hen the system is boot up, it will first check the data in the Memory Key; therefore a
valid Memory Key is required to bootup the system successfully.
Replacement of a damaged IDU
In this case, plug out the Memory Key from the damaged IDU, plug it into the replacement
IDU. To perform a complete substitution, the replacement IDU must be powered on wit h
the Memory Key plugged in. At startup, the replacement IDU will find the Memory
Key with correct Equipment Name, System Type and configuration and will load the
configuration and run it.
If the Memory Key does not work properly, being damaged or being lost, please contact
Technical Support team for support.
5.9 License
First Mile 200 is delivered to customer with the dedicated software release for
operation, providing the basic and essential functions needed in-field, which is the
factory default configuration, while there are additional features that could be required,
for instance, when the network scales up, or network security is required.
The factory default configuration is:
2 Ethernet ports can be activated out of 6 Ethernet ports (including the 2 SFP ports)
All the TDM ports can be activated
First Mile 200 R2.5.1 provides the following upgrade licenses:
Management
First Mile 200 full configuration

Enabling of 1+ 1 hot standby (HSBY) protection and all 6 Ethernet ports
Support of RSTP/MSTP
Rapid Spanning Tree Protocol/Multiple Spanning Tree Protocol
Support of security management

SSH, SFTP, SNMPv3, ACL (ACL means Access Control Log, not Access Control
List and is used to record user logging).
Support of OAM (Operations, Administration and Maintenance)

Support of CES linear protection
Support of G.8031
Support of G.8032
In First Mile 200 R2.5.1, the in-field license upgrading is no need of hardware, it will be
delivered through an electronic channel. For the detailed license upgrading procedure,
please refer to the Harmony First Mile 200 Rel.2.5.1 IDU Operate and Maintain manual.
And there is no pre-installed license in factory.
If the upgrading licenses are ordered together with the equipment, licenses are installed
during commissioning.
In-field license upgrading is also supported, which can be done by DragonWave
service staff or by the customers themselves. The upgrading can be done locally or
remotely through the EMS (Element Management System) while the equipment is
running without traffic disruption. There is EMS upgrading window in both LCT
/ NetViewer to transmit/receive license upgrading parameters.
License is implemented using secure plain text messages generated and authorized by
DragonWave. If the license file is lost or corrupted, the valid licensed user can get a
replacement from DragonWave without paying for the feature twice. The license is
bound to the units serial number and cannot be used in another unit. If the radio
hardware is swapped by DragonW ave in a hardware failure case, a new license file will
be generated.
In case the unit is not managed remotely, make sure that the license has been retrieved
for the equipment before going to the site. There are no emergency licenses available
for Harmony microwave products.
The license is ordered through the following ordering process
Customer releases the Purchase Order and provide the product target ID
information to DW I OPS.
DW I OPS will generate the license according to the purchase order.
DWI OPS will ship License Key back to customer.
Mechanical structure and interfaces
6 Mechanical structure and interfaces

6.1 First Mile 200 interface
Memory
Key
Dry
contact
OOB
Reset (RST)
DCN
8 x E1/T1/J1
2 x GE
(Optical)
4 x GE**
(Electrical)
DC power
**Port 3&4 provides power feeding to connected ODUs
Figure 24
Mechanical structure
Front view:
E1/T1/J1
RST
OOB
200
Figure 25
DCN
3(PWR) 4(PWR)
Front view
There are LED indications on the front panel to indicate the status of different type of
signal or connection, for the detail information on LEDs, please refer to Chapter 7.5.
6.1.1
Installation
First Mile 200 IDU is a standard sub-rack compatible with standard ETSI N3 and 19inch rack. As all the interfaces are located in the front panel, cabling can be performed
easily.
For the detailed installation instruction, please refer to the Harmony First Mile 200 IDU
Installation manual.
6.1.2
Mechanical structure and interfaces
Power supply
First Mile 200 requires a power supply input of -48 V DC. The system is equipped with an
internal PSU (DC/DC unit) for the power feeding the internal circuitry. The internally
dissipated power is within 30 W, including the PSU efficiency.
Besides the feeding of the internal circuitry, the IDU provides power feeding to the
connected ODUs. Up to 2 ODUs is supported. The IDU forwards the DC battery voltage
towards the central terminal of the Ethernet transformers. See Figure 26.
Figure 26
Power supply illustration to ODU
IDU continuously performs a load control to detect abnormal working condition. Shortcircuit protection of First Mile 200 prevents the system from over-voltage.
6.1.3
Handling requirements
First Mile 200 is sensitive to electromagnetic discharge. The user should be sure that
the module is properly grounded and wear an antistatic wrist wrap when handling it.
6.1.4
Reset
A reset button is located beside the Memory Key interface on First Mile 200 front
panel. W hen the reset button is pressed, the microprocessor of the system is reset but
leaving the rest of hardware running.
This is a warm reboot without traffic disruption.
6.2
Connection to ODUs
There are two ways to connect Harmony Radio and First Mile 200:
through a single Ethernet cable with ODU powering support
one Ethernet cable and a separate power supply cable for ODU powering
For detailed information of connecting First Mile 200 to Harmony Radio,

please refer to the Harmony Radio Product Description manual.
7 Technical specifications
7.1 Dimensions and weight
The Following table lists the dimension and weight for First Mile 200:
Property
Value
Height
32 mm
Width
442 mm
Depth
210 mm
Weight
(without handle)
1.4 Kg
Table 9
Dimension and weight
7.2 Power requirements

The following table describes the input voltage and power consumption of First Mile 200:
Property
Value
Nominal input voltage
-40.5 ~ - 57.6 V DC
Minimum power consumption
13.5 W
Typical power consumption
15 W
Maximum power consumption
18 W
Table 10
Power requirements
The ODU power consumption needs to be considered in IDU power consumption when
the IDU provides power feeding to connected ODUs.
Please refer to the Harmony Radio Product Description manual for detailed
information about the power consumption of Harmony Radio.
7.3 Temperature requirements

In normal operation condition, lists the temperature requirements for First Mile 200:
Property
Operating temperature
Table 11
Value
-5 ~ +55 C
Operating environment requirements
7.4 Interfaces
Interface
10/100/1000 Base-T
electrical Ethernet port (to
ODU)
SFP port (to local traffic)
Connector
RJ-45 connector
with 2 ports providing embedded power to
Harmony Radio
Electrical SFP with 10Base-T/100BaseTX/1000Base-T cable
Optical SFP with 1000Base-X fiber
DCN port for local and

remote management
FE with RJ-45 connector
OOB port for local

management
FE with RJ-45 connector
Dry contact
D-Sub9 connector
E1/T1/J1 TDM port
RJ-48 connector
DC power
D-Sub2 1 male + 1 female
Table 12
Interfaces
7.5 LEDs indication

First Mile 200 has four types of LEDs on the front panel to indicate the operational status
of the system during operation.
Type
System
Memory
Key
Name
State
Function
PWR
Green
ON
Power on
C/MJ
Red
ON
IDU failure with Critical/Major

severity alarm
MN/W
Red
ON
IDU failure with Minor alarm or

Warning
TEST
Yellow
ON
Test condition active (e.g., loopback, protection forcing)
ODU
Red
ON
ODU failure in at least one of the

connected ODUs
Memory Key
failure
Red
ON
Failure of the memory key/ No

available memory key insert
Green
ON
Connection established
Green
Blink
Activity indication (on Tx or Rx)
Ethernet
Link (left side)
electrical
Active (right side)
and SFP
interfaces
Table 13
Color
LED information
Type
Name
E1/T1/J1
interfaces
LOS/LOF
connection
Color
Red
Green
State
Function
ON
Loss of signal or loss of frame
Blink
AIS In detected or AIS Out

generated
ON
Connection established;
No alarm
Table 13
LED information (Cont.)
7.6 GE electrical Ethernet cable (for local traffic)

Cable type
CAT6 S/FTP cable
Connector type
shielded RJ-45 connector
Temperature range
-40 C to +70 C
Signal on cable
Gigabit Ethernet
Max. length
100 m
Table 14
GE Ethernet cable (for local traffic) requirement
7.7 GE electrical Ethernet cable (for ODU)

Cable type
Double shielded, four twisted pairs, Cat-5e cable compliant (for outdoor condition).Each pin manages at least
24 AWG wire diameter.
Connector type towards

First Mile 200
RJ-45 connector
Connector type towards

Harmony Radio
Lemo connector
Temperature range
-25C to +70C
Signal on cable
Gigabit Ethernet
Max. length
100 m
Table 15
GE Ethernet cable (for ODU) requirement
7.8 GE SFP optical Ethernet cable

Cable type
9/125 and 50/125, Duplex Fiber
Connector type
LC connector
Temperature range
-25C to +70C
Table 16
SFP optical Ethernet cable requirement
7.9 GE SFP electrical Ethernet cable

Cable type
S/FTP, CAT6, AWG26
Connector type
Shield RJ-45
Temperature range
-40C to +75C
Table 17
SFP electrical Ethernet cable requirement
7.10 E1/T1/J1 cable

Cable type
RG179 or 4 Core 120 ohm Cable
Connector type
RJ-45 connector
Temperature range
-20C to +80C
Table 18
E1/T1/J1 cable requirement
7.11 Power cable

Cable type
Bipolar Shield 2 x 1.5 mm 2 cable
Connector type
D-Sub2
Temperature range
-20C to +80C
Table 19
Power cable requirement
7.12 Memory Key

- 30C to 85C
Memory storage
32 Mbit
Table 20
Memory Key
7.13 Optical Splitter

Connector type
LC Simplex
Adaptor type
LC Duplex
Operating wavelength
1310/1550 nm
Fiber type
9/125 um
- 40C to 85C
Temperature range installation
- 50C to 85C
Table 21
Optical splitter - single mode
Connector type
LC Simplex
Adaptor type
LC Duplex
Operating wavelength
1300 40 nm
Fiber type
Multimode 62.5/125 um
- 40C to 85C
Temperature range installation
- 40C to 85C
Table 22
Optical splitter - Multimode
7.14 Standards
Recommendation
Recommendation name
IEEE 802.3-2005
Carrier Sense Multiple Access with Collision Detection

(CSMA/CD) Access Method and Physical Layer
Specifications.
IEEE 802.1Q
Virtual LANs
IEEE 802.1ad
Provider Bridge (QinQ)
IEEE 802.1ah
Provider Backbone Bridge (MAC- in-M AC)
IEEE P802.3at/D1.0
Enhanced Data Terminal Equipment (DTE) Power via

Media Dependent Interface ( MDI) Enhancements
IEEE 802.1ag- 2007
Table 23
Virtual Bridged Local Area Networks: Connectivity Fault

Management
IEEE standard
Recommendation
Recommendation name
ETSI EN 300 119-3
Environmental Engineering (EE); European

Telecommunication Standard for Equipment practice;
Part 3: Engineering requirements for miscellaneous racks
and cabinets.
ETSI EN 300 119-4
Environmental Engineering (EE); European

Telecommunication Standard for Equipment practice;
Part 4: Engineering requirements for sub-racks in
miscellaneous racks and cabinets.

CENELEC EN 60297-5
Mechanical structures for electronic equipment Dimensions of mechanical structures of the 482,6 mm
(19 in) series -- Part 5

EN 300 132-2
Environmental Engineering (EE); Power supply interface

at the input to telecommunications equipment; Part 2:
Operated by direct current (dc)
Table 24
Environment
Recommendation
IETF RFC 5086
Recommendation name
Structure-Aware Time Division Multiplexed (TDM) Circuit
Emulation --Service over Packet Switched Network
( CESoPSN).
IETF RFC 4553
Structure-Agnostic Time Division Multiplexing (TDM) over

Packet ( SAToP)
IETF RFC 2697
A Single Rate Three Color Marker
IETF RFC 2698
A Two Rate Three Color Marker
IETF RFC 2819
Remote Network Monitoring Management Information

Bas e
IETF RFC 2863
The Interfaces Group MIB
IETF RFC 3031
Multiprotocol Label Switching Architecture
IETF RFC 1901
Introduction to Community-based SNMPv2
IETF RFC 1902
Structure of Management Information for version 2 of the

Simple Network Management Protocol (SNMPv2) January 1996
IETF RFC 1903
Textual Convention for Version 2 of the Simple Networ k

Management Protocol ( SNMPv2) - January 1996
IETF RFC 959
File Transfer Protocol (FTP)
IETF RFC 1950
ZLIB compressed data format specification version 3.3
IETF RFC 1951
DEFLATE compressed data for mat specification version
1.3
IETF RFC 2030
Table 25
Simple Network Time Protocol (SNTP) Version 4 for IPv4,

IPv6 and OSI
IETF standard
Recommendation
MEF 8
Recommendation name
Implementation Agreement for the Emulation of PDH
Circuits over Metro Ethernet Networks.

MEF 9
Abstract Test Suite for Ethernet Services at the UNI.
MEF 14
Abstract Test Suite for Traffic Management Phase 1.
Table 26
MEF standard
Recommendation
ITU- T G.8261/Y.1361
Recommendation name
Timing and synchronization aspects in packet networks
ITU-T G.8262/Y.1362
Timing characteristics of synchronous Ethernet

equipment slave clock (EEC)
ITU-T Y.1731
OAM functions and mechanisms for Ethernet bas ed

networks
Table 27
ITU-T standard
Recommendation
ITU-T G.826
Recommendation name
End-to-end error performance parameters and objectives

for international, constant bit-rate digital paths and
connections
ITU-T G.704
Synchronous frame structures used at 1544, 6312, 2048,

8448 and 44 736 kbit/s hierarchical levels
ITU-T G.707/Y.1322
Network Node Interface
ITU-T G.781
Synchronization Layer
Table 27
ITU-T standard (Cont.)
Recommendation
ETSI EN 302 217- 1
Recommendation name
Fixed Radio Systems; Characteristics and requirements
for point-to-point equipment and antennas; Part 1:

Overview and system-independent common
characteristics
ETSI EN 302 217-2-1

for point-topoint equipment and antennas; Part 2- 1:
System-dependent requirements for digital systems

operating in frequency bands where frequency coordination
is applied
ETSI EN 302 217- 2-2
for point to point equipment and antennas; Part 2-2:

Harmonized EN covering essential requirements of
Article 3(2) of R&TTE Directive for digital systems

operating in frequency bands where frequency co
ETSI EN 302 217-31
Fixed Radio Systems; Characteristics and requirem ents

for point-to-point equipment and antennas; Part 3:
Harmonized EN covering essential requirements of
Article 3(2) of R&TTE Directive for equipment operating

in frequency bands where no frequency co-ordination is
applied
ETSI EN 302 217-4-1
Fixed Radio Systems; Character ist ics and requirements

for point-to-point equipment and antennas; Part 4-1:
System- dependent requirements for antennas
ETSI EN 302 217-4-21
Radio Systems; Characteristics and requirements for

point to point equipment and antennas; Part 4 2:
Harmonized EN covering essential requirements of Article
3( 2) of R&TTE Directive for antennas
Table 28
ETSI TM4 standard
Recommendation
Recommendation name
ETSI EN 301 489-11
Electromagnetic compatibility and Radio spectrum

Matters (ERM); Electromagnetic Compatibility (EMC)
standard for radio equipment and services; Part 1:
Common technical requirements
Table 29
EMC standard
Recommendation
Recommendation name
ETSI EN 301 489-41

Matters (ERM); Electromagnetic Compatibility ( EMC)
standard for radio equipment and services; Part 4:
Specific conditions for fixed radio links and ancillary

equipment and services
ETSI EN 300 3861

Matters (ERM); Telecommunication network equipment;
ElectroMagnetic compatibility (EMC) requirements
Resistibility of telecommunication installed in a
ITU-T K.20
telecommunications overvoltages and overcurrents

Resistibility tests for telecommunication equipment
ITU-T K.44
exposed to over voltages and overcurrents Basic

Recommendation.
ITU- T K.45
Resistibility of telecommunication equipment installed in
the access and trunk networks to overvoltages and overcurrents
ITU-T K.48
EMC requirements for telecommunication equipment

Product family Recommendation
Protection of radio base stations against lightning dis-
ITU- T K.56
charges.
IEC 55022
Information technology equipment - Radio disturbance

characteristics - Limits and methods of measurement.
IEC CISPR22
Information technology equipment - Radio disturbance
characteristics - Limits and methods of measurement.

IEC 61000-3-2
Electromagnetic compatibility (EMC) - Part 3-2: Limits

Limits for harmonic current emissions (equipment input
current 16 A per phase)
IEC 61000-3-3
Electromagnetic compatibility (EMC) - Part 3-3: Limits

Limitation of voltage changes, voltage fluctuations and
flicker in public low-voltage supply systems, for equipment
with rated current 16 A per phase and not subject to
conditional connection
IEC 61000- 3- 11
Electromagnetic compatibility (EMC) - Part 3-11: Limits;
Limitation of voltage changes, voltage fluctuations and

flicker in public low-voltage supply systems; Equipment
with rated current >16 A and 75 A and subject to
conditional connection
IEC 61000- 3- 12
Electromagnetic
compatibility (EMC) - Part 3-12: Limits
Limits for harmonic currents produced by equipment

connected
current
IEC 61000- 4- 2
to
public
low-voltage
systems
with
input
Electromagnetic compatibility ( EMC) - Part 4: Testing and

measuring techniques - Section 2: Electrostatic discharge
immunity test - Basic EMC publication

IEC 61000-4-3
Electromagnetic compatibility (EMC) - Part 4-3: Testing

and measurement techniques - Radiated, radio-
frequency, electromagnetic field immunity test.
Table 29
EMC standard (Cont.)
Recommendation
Recommendation name
IEC 61000-4-4

and measurement techniques - Electrical fast
transient/burst immunity test.
IEC 61000-4-5

and measurement techniques - Surge immunity test.
IEC 61000-4-6

and measurement
techniques
- Immunity to conducted
disturbances, induced by radio-frequency fields.

IEC 61000-4- 11
Electromagnetic
compatibility (EMC) - Part 4-11: Testing
and measurement techniques - Voltage dips, short

interruptions and voltage variations immunity tests.
IEC 61000-4- 29
Electromagnetic compatibility (EMC) Part 4-29: Testing

and measurement techniques Voltage dips, short
interruptions and voltage variations on d.c. input power
port immunity tests

IEC 61000-6- 1
Electromagnetic compatibility (EMC) - Part 6-1: Generic
standards - Immunity for residential, commercial and lightindustrial environments.

IEC 61000-6- 2
standards Immunity for industrial environments.

IEC 61000-6- 3

standards Emission standard for residential, commercial
and light-industrial environments
IEC 60060-1
High-voltage test techniques
IEC 50081-1
Electromagnetic compatibility - Generic emission

standards Part 1: residential, commercial and lightindustrial environments.
IEC 50082-1
Table 29
Electromagnetic compatibility - Generic immunity

standards Part 2: residential, commercial and lightindustrial environments.
EMC standard (Cont.)
Recommendation
Recommendation name
IEC 60950-1
Implementation Agreement for the Emulation of PDH

Circuits over Metro Ethernet Networks.
IEC 60950-22
Information Technology Equipment - Safety - Part 22:

Equipment to be Installed Outdoor s
IEC 60529
Degrees of protection provided by enclosures (IP Code)
IEC 60215
Safety requirements for radio transmitting equipment
IEC 60825-1
Safety of laser products - Part 1: Equipment classification
and requirements
IEC 60825-2
Table 30
Safety of laser products Part 2: Safety of optical fiber

communication
Safety standard
Recommendation
CENELEC EN 50385
Recommendation name
Product standard to demonstrate the compliance of radio

base stations and fixed terminal stations for wireless
telecommunication systems with the basic restrictions on
the reference levels related to human exposure to radio

frequency electromagnetic fields (110 MHz 40 GHz)
General public
CENELEC EN 50265-1
Common test methods for cables under fire conditions Test for resistance to vertical flame propagation for a
single insulated conductor or cable - Part 1: Apparatus
IEC 60332-1-1
Tests on electric and optical fiber cables under fire

conditions - Part 1-1: Test for vertical flame propagation
for a single insulated wire or cable Apparatus
IEC 60332-1-2

for a single insulated wire or cable - Procedure for 1 kW

pre- mixed flame
IEC 60332- 1- 3

for a single insulated wire or cable - Procedure for

determination of flaming droplets/particles
CENELEC EN 50267-2- 1
Common test methods for cables under fir e conditions Tests on gases evolved during combustion of material
from cables - Part 2-1: Procedures; determination of the
amount of halogen acid gas
CENELEC EN 50267-2-2
Common test methods for cables under fire conditions Tests on gases evolved during combusti on of materi als
from cables - Part 2-2: Procedures - Determination of
degree of acidity of gases for materials by measuring pH

and conductivity
CENELEC EN 50267-2- 3
Common test methods for cables under fir e conditions -
Tests on gases evolved during combustion of materials

from cables - Part 2-3: Procedures - Determination of
degree of acidity of gases for cables by determination of
the weighted average of pH and conductivity

IEC 61034-2
Measurement of smoke density of cables burning under

defined conditions - Part 2: Test procedure and
requirements
IEC 60708- 1
Low-frequency cables with polyolefin insulation and

moisture barrier polyolefin sheath. Part 1: General design
details and requirements
Table 30
Safety standard (Cont.)
Recommendation
Recommendation name
ETSI ETS 300 753
Equipment Engineering (EE); Acoustic noise emitted by

telecommunications equipment
ISO 7779 Acoustics
Measurement of Airborne Noise Emitted by Computers

and Business Equipment.
Table 31
Acoustic noise standard
Recommendation
Recommendation name
ETSI EN 300 132-2
Equipment Engineering (EE); Power supply interface at

the input to telecommunications equipment; Part 2:
Operated by direct current (DC)
EN50419
Marking of electric and electronic equipment in

accordance with Article 11(2) of Directive 2002/96/EC
Table 32
Other standard

Harmony First Mile 200 Product Description

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Harmony First Mile 200 Product Description

Hochgeladen von

Copyright:

Verfügbare Formate

Harmony First Mile 200, R2.5.

IDU Product Description

The information in this document is subject to change without notice and

IDU Product Description

Intended audience ...................................................................................................................................... 6

Structure of this document ....................................................................................................................... 6

History of changes ...................................................................................................................................... 6

Symbols and conventions ......................................................................................................................... 7

Waste electrical and electronic equipment (WEEE) ............................................................................ 8

RoHS compliance ........................................................................................................................................ 9

Harmony Microwave ................................................................................................................................. 10

First Mile 200 Indoor Unit ......................................................................................................................... 10

Software release ................................................................................................................................ 16

General features ......................................................................................................................................... 18

Carrier Ethernet Transport ...................................................................................................................... 18

Ethernet services ............................................................................................................................... 18

Ethernet QoS ....................................................................................................................................... 20

Link Layer Discovery Protocol (LLDP) ......................................................................................... 31

Bridging modes .................................................................................................................................. 32

TDM circuit emulation service (CES) .................................................................................................... 32

CESoP for E1/T1/J1 ........................................................................................................................... 33

SAToP for E1 ....................................................................................................................................... 33

Mixed configuration of SAToP with CESoP for E1 ................................................................... 34

LPG protection ................................................................................................................................... 34

xSTP for E-LAN service .................................................................................................................... 36

LAG protection ................................................................................................................................... 37

IDU Product Description

CESoP and SAToP linear protection ............................................................................................ 38

G.8031 linear protection ................................................................................................................... 38

G.8032 ring protection ...................................................................................................................... 40

Synchronization overview ............................................................................................................... 42

Synchronization from TDM interface ............................................................................................ 44

Synchronization from Ethernet interface .................................................................................... 45

Performance management ...................................................................................................................... 45

Performance management based Ethernet service ................................................................. 45

Performance management based CESoP service .................................................................... 46

Performance management based OAM ....................................................................................... 46

Performance monitoring .................................................................................................................. 46

User class management................................................................................................................... 49

Securing management protocols .................................................................................................. 50

Web-based LCT management ................................................................................................................ 50

DCN configuration auto-recovery.................................................................................................. 51

Network application .................................................................................................................................. 52

Site configurations .................................................................................................................................... 53

Tail site: 3G BTS only ....................................................................................................................... 53

Tail site: 2G and 3G BTSs collocation ......................................................................................... 53

Tail site: 2G, 3G, and 4G BTSs collocation ................................................................................. 54

Chain site ............................................................................................................................................. 54

Network management using Nokia Siemens Networks ................................................................... 55

Network management using NetViewer .............................................................................................. 55

Accessing IDU ............................................................................................................................................ 56

SNMP agent ................................................................................................................................................. 56

SNTP, FTP, and Telnet .............................................................................................................................. 57

Memory Key ................................................................................................................................................ 57

Mechanical structure and interfaces ............................................................................................................ 59

First Mile 200 interface ............................................................................................................................. 59

Power supply ...................................................................................................................................... 60

Handling requirements ..................................................................................................................... 60

IDU Product Description

Connection to ODUs ................................................................................................................................. 60

Technical specifications .................................................................................................................................. 61

Dimensions and weight ............................................................................................................................ 61

Temperature requirements ..................................................................................................................... 61

LEDs indication .......................................................................................................................................... 63