TWT63037-9500MPR R (1) .3.0.ce

9500 MPR
9500MPR R 3.0 Operation and

Maintenance
TWT63037-R 3.0-SG1-SEN- I1.0 Issue 1.00
STUDENT GUIDE
All Rights Reserved Alcatel-Lucent 2011
All rights reserved Alcatel-Lucent 2011

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent

9500MPR R 3.0 Operation and Maintenance - Page 1
Empty page
Switch to notes view!
2 All Rights Reserved Alcatel-Lucent 2011

9500 MPR
9500MPR R 3.0 Operation and Maintenance
This page is left blank intentionally

Terms of Use and Legal Notices
1. Safetyto
Switch Warning
notes view!
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to
wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the
equipment alone.
The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.
All other trademarks, service marks and logos (Marks) are the property of their respective holders, including Alcatel-
Lucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning
the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to
change without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No
other use or transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and
must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may
be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from
Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly
prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes or
describes, and is expressly prohibited from modifying the information or creating derivative works without the express
3written consent of Alcatel-Lucent. All Rights Reserved Alcatel-Lucent 2011
9500 MPR
All rights reserved Alcatel-Lucent 2011
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including
lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not Alcatel-
Lucent has been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an
endorsement, nor a recommendation.
This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The
information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some
cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely
accurate.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment
and its operation, or contact your nearest Alcatel-Lucent representative for more information.
The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. Alcatel-
Lucent disclaims any warranties in connection with the products as used and described in the courses or the related
documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties,
including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of
dealing, usage or trade practice.
Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed
internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in
nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are
governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal
Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including,
but not limited to, the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a
valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these
Terms of Use and Legal Notices shall remain in full force and effect.

Blank Page

9500 MPR

Course Outline
Section
About This1.Course
Product Overview
4. Topic/Section is Positioned Here
Module 1. Introduction
Course outline
Technical support
Module 2. Architecture 5. Topic/Section is Positioned Here
Course objectives
Module 3. Management System
Section 2. Functional
1. Topic/Section Description
is Positioned Here 6. Topic/Section is Positioned Here
Xxx Module 1. MSS node HW Architecture
Xxx Module 2. ODU300 HW Architecture 7. Topic/Section is Positioned Here
Xxx
Module 3. MPT-HC HW Architecture
Module 4. MPT-HC V2 HW architecture
Module 5. MPT-MC HW Architecture
Module 6. MSS terminal HW architecture
Section 3. NE operation
Module 1. Operator interface MPR node
Module 2. Initial configuration MPR node
Module 3. Performance monitoring MPR node
Module 4. Operator interface MPR terminal
Module 5. Initial configuration MPR terminal
Module 6. Performance monitoring MPR terminal
5 Section 4. Maintenance
9500 MPR

Module 1. Fault management
Module 2. Software download

Course Outline [cont.]

9500 MPR

Course Objectives
Welcome to 9500MPR R 3.0 Operation and Maintenance
Upon completion of this course, you should be able to:
Configure and manage the 9500MPR

9500 MPR

Course Objectives [cont.]

9500 MPR

About this Student Guide

Conventions
Switch used
to notes in this guide
view!
Note
Provides you with additional information about the topic being discussed.
Although this information is not required knowledge, you might find it useful
or interesting.
Technical Reference
(1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical
Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment
damage or personal injury.
Where you can get further information

9500 MPR
If you want further information you can refer to the following:

Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com

About this Student Guide [cont.]

9500 MPR

Self-assessment of Objectives
Contract number :
At the end of each section you will be asked to fill this questionnaire
Course title :
Please, return this sheet to the trainer at the end of the training
Client (Company, Center) :
Language :
Switch to notes view! Dates from : to :
Number of trainees : Location :
Surname, First name :
Did you meet the following objectives ?

Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
Yes (or No (or

Instructional objectives globally globally Comments
yes) no)
1 To be able to:
Describe the basic concepts of
9500MPR
2 To be able to:
11
Describe the main functionalities
9500 MPR of the 9500MPR
3 To be able to:
Describe the management system of
the 9500MPR
4 To be able to :
Describe the functionality of each unit
of the MSS
5 To be able to:
Describe the functionality of the ODUs
6 To be able to:
understand all the menus available
with the LCT
7 To be able to:
Configure a NE starting from scratch
8 To be able to:
Activate and evaluate the performance
monitoring application
9 To be able to:
Performa the troubleshooting of the
9500MPR
10 To be able to:
Perform the SW download of the 9500MPR

Self-assessment of Objectives [cont.]
Yes (or No (or

Instructional objectives Globally globally Comments
yes) no)

9500 MPR
Other comments
Thank you for your answers to this questionnaire


Do not delete this graphic elements in here:
11
Section 1
Product Overview
Module 1
Introduction
3JK Issue 1.00
9500 MPR

3JK Issue 1.00
Section 1 Module 1 Page 1
Blank Page

Product Overview Introduction
9500 MPR 9500MPR R 3.0 Operation and Maintenance
Document History
Edition Date Author Remarks
01 2010-07-21 ALU University, First edition

Marcoussis
02 2011-02-01 ALU University, Updated to rel.3.0

Vimercate

3JK Issue 1.00
Module Objectives
Upon completion of this module, you should be able to:
Describe the Basic Concepts of the 9500 MPR.


3JK Issue 1.00
Module Objectives [cont.]


3JK Issue 1.00
Table of Contents
Page
1 Understanding the 9500MPR Innovations 7
1.1 Classification of the New Generation Products 8
1.2 Presentation 9
1.3 Multiservice Aggregation Layer 12
1.4 Service Awareness 13
1.5 Packet Node 14
1.6 Service-driven Packet Adaptive Modulation 15
1.7 Power Consumption Reduction 16
1.8 Hybrid or Packet Mode: for Efficient Data Transport 17
1.9 Packet node: Minimizing Equipment at Each Site 19
Blank Page 20
2 MPR in New Market Segments 21
2.1 The Most Effective Solution 22
2.2 MPR-e Enabling Zero-Footprint Microwave Configurations 24
2.3 MPR in Last Mile 25
2.4 LTE and Full Ethernet 3G Ready 26
2.5 From Current PDH/SDH Network to Packet Transport Network Evolution 27
2.6 MPR addresses All Microwave Applications in Aggregation 28
2.7 MPR addresses Metro Ring/Partial Mesh Application 29
Blank Page 30
3 System Description 31
3.1 Alcatel-Lucent 9500 Microwave Packet Radio 32
3.2 9500 MPR System Family 33
115 3.3 9500 MPR Key Features All Rights Reserved Alcatel-Lucent 2011 35
3.4
Product Overview 9500 MPR
Introduction Node
37
3.5 9500 MPR Terminal 46
3.6 OutDoor Unit 300 51
3.7 Microwave Packet Transport 53
4 Radio Configuration 59
4.1 Radio Configuration 60
5 System Configuration 61
5.1 Example of System configurations 62
Blank Page 67
End of Module 68

3JK Issue 1.00
Table of Contents [cont.]
Page


3JK Issue 1.00
1 Understanding the 9500MPR
Innovations


3JK Issue 1.00
1 Understanding the 9500MPR Innovations
1.1 Classification of the New Generation Products
Alcatel-Lucent microwave product acronyms are derived as

follows:
9 5 0 0 MPR
R = Radio
Means radio
product Frequency Band P = Packet
M = Microwave
5 for Radio Cross-Connect


3JK Issue 1.00
1.2 Presentation
ALU 9500 MPR, currently is the best combination of features/prices in the

Backhauling environment (from Last Mile to Metro Networks)
Backhauling Backbone
Last Mile Aggregated Link Metro

Microwave
Microwave
Microwave for
BSC
BTS backbone
Node B RNC
9400 family 9600 family
9400AWY 9600USY
9500 MXC
9500MPR 9500MXC 9600LSY

9500 MPR


3JK Issue 1.00
1.2 Presentation [cont.]
2
4
Trunking platforms
4,7 9600LSY
6L
6U
7 MDR 8000
8
10
11
13
Frequency
9500MPR
6L
Urban platforms
6U
7
9500MXC 9600USY
9400AWY
38
GHz 4 34 45 64 155 311 622 1240 2480 MBps
Capacity
1 1 10 All Rights Reserved Alcatel-Lucent 2011

3JK Issue 1.00
1.2 Presentation [cont.]
The 9500 MPR innovative solutions mainly are:

Multiservice aggregation layer:
the capacity to use Ethernet as a common transmission layer to transport any
kind of traffic, independently by the type of interface. Ethernet becomes the
convergence layer.
Service awareness:
traffic handling and quality management, queuing traffic according to the
type of service assigned, independently by the type of interface
Packet node:
no service aggregation limits with all traffic aggregated in packets, in term
of: capacity, type of service requirements and type of interface
Service-driven adaptive modulation:
fully exploit the air bandwidth in its entirety by changing modulation scheme
according to the propagation availability and allocate transport capacity,
discriminating traffic by different services, only possible in a packet-based
environment


3JK Issue 1.00
1.3 Multiservice Aggregation Layer
Access network Packet Backhaul network
Any TDM/Ethernet interfaces Ethernet aggregation layer
GSM Aggregated traffic

2G over Ethernet
nxE1
ISAM, WiMAX
Ethernet
nxE1
3G HSDPA
Voice on R99 9500 MPR
Single technology throughout the network: Ethernet as convergence layer

TDM networking Packet networking
Stacking Converging
Maximizing the available bandwidth
9500 MPR aggregates and carries over a COMMON PACKET LAYER: TDM 2G, 3G, SDH and IP/Ethernet.
This allows sharing of common packet transmission infrastructures, regardless of the nature of
carried traffic.
Due to the nature of Ethernet, each service can be discriminated based on several parameters like
quality of service.
Mapping different access technologies over Ethernet is achieved by standardized protocols like
circuit emulation and pseudo-wire.

3JK Issue 1.00
1.4 Service Awareness
SERVICE CLASSIFICATION: Voice, Broadband

INPUTS : Any interfaces (E1, Ethernet)
PACKETIZATION PROCESSING:
TDM Standard CEoEth [MEF8]
SDH
ATM Standard PWE3
Ethernet Native
Constant bit rate services

High Priority Queue;
Revenue based on real-time
Guaranteed bit rate communication
Voice, Video Telephony
Variable bit rate services
Low Priority Queue; Revenue based on access
Remaining bit rate to contents
HiSpeed @, VideoD & Gaming
SERVICE AGGREGATION and OVERBOOKING: SERVICE QUALITY MANAGEMENT:

Service aggregation using statistical Service scheduler queuing packets according to
multiplexing, obtaining dramatic band the quality of service assigned.
reduction HIGH for real-time traffic, LOW for Broadband
Decoupling access technology from transport technology: manage services

Service awareness means the ability to discriminate the different traffic types carried over the
converged Ethernet stream. Our traffic flow can be composed by E1s, STM-1, ATM and/or IP/Eth,
coming from different sources, and therefore having different requirements. For instance ATM
traffic from a 3G base stations can carry voice (high priority, real time service) and data (lower
priority and possibly non real time with high variability load, such as internet browsing, music
download or video streaming).
Service awareness is what allows identifying the traffic types, and in case of the non real time
variable bit rate one, optimize the band with overbooking of the radio scarce resource.

3JK Issue 1.00
1.5 Packet Node
Address new data services in the best way: packet natively

9500 MPR offers a SINGLE PACKET MATRIX able to switch, aggregate and handle any of the possible
incoming traffic types with virtually no capacity limits (up to 10 GBps).

3JK Issue 1.00
1.6 Service-driven Packet Adaptive Modulation
Guarantee 100%
Mobile 9500 MPR 9500 MPR

2G,3G,4G
Traffic with high priority will always have bandwidth available, like voice
(deterministic approach)
Broadband traffic is discriminated by QoS dynamically, with modulation scheme
changes driven by propagation conditions
Fully exploit the air bandwidth for any access technology


3JK Issue 1.00
1.7 Power Consumption Reduction
Adaptive modulation:
To reduce power consumption,
rethink network architecture
Increases the power efficiency
Thanks to higher modulation schemes used in different MPR releases
(see graph)
Reduces antenna size by 50%: Less visual impact
Node consumption Througput per Watt (1+0 with mixed 6 Eth and 10xE1)
Nodal capability:
Reduces floor space by 90 12
Cumulated 11
50%*: Collapses 6 direction 80
-4% 125% 10
-10% -40%
radio node into only 2 70 9
Power (Watt)
Mpbs/Watt
physical units 60 8
85% 7
50 22% 6
(aW
tro
P
)w
e
14% Cumulated:
5
W
ta/sb
p
M
40 -40%
4
30
3
20 2
MPR MPR MPR MPR MPR
(*) Compared to last-generation TDM microwave R1.1 R1.2 R2.0 R2.1 R2.2
platform in lab environment
Native packets at the air reduce power consumption and antenna size

This true packet product is not based on TDM (circuit-based) technology, so it efficiently transports
multimedia traffic by handling packets natively while still supporting legacy TDM. It also adapts
packets to the air conditions and quality required by different service types. This product improves
packet aggregation, increases bandwidth and optimizes Ethernet connectivity.

3JK Issue 1.00
1.8 Hybrid or Packet Mode: for Efficient Data Transport
9500 MPR is able to work in:

TDM or Hybrid mode ,
Enable mixed E1 and Ethernet Layer 2
Same simplicity in architecture, same operation, same performances and quality
as any Hybrid/TDM microwave
Packet mode
Ethernet as convergence layer
Simplify and optimized use of infrastructure for any access technology
Common Hardware applicable for both mode
Simple upgrade of OS (through Network management) : from Hybrid OS to Packet OS.
9500 MPR offer Hybrid and Packet with single Hardware solution


3JK Issue 1.00
1.8 Hybrid or Packet Mode: for Efficient Data Transport
[cont.]
GbE Packet domain

MW radio
E1/STM-1/Eth
SDH domain
Packet networking
Mobile
2G,3G,4G GigE handoff
GigE
TDM
Converged ATM Eth
9500 MPR
Eth
Private ATM
Business office
TDM 9500 MPR
GigE
IMA/n x E1/T1
Native handoff
nxE1/T1
Eth
Fixed DSL
ATM
9500 MPR TDM
Phone
Network Management E2E Provisioning

9500 MPR can operate in Hybrid or Packet Mode with same hardware
Enabling possibility for smooth migration from Hybrid mode to Packet mode
DSL Digital Subscriber Line

E1 2.048 Mb/s interface
Eth Ethernet
GigE Gigabit Ethernet
IMA Inverse Multiplexing over ATM
MPLS Multiprotocol Label Switching
PDH Plesiochronous Digital Hierarchy
T1 1.544 Mb/s interface

3JK Issue 1.00
1.9 Packet node: Minimizing Equipment at Each Site
Repeater site
Hub site
Access Access
9500 MPR
9500 MPR
9500 MPR
9500 MPR
MSS-8
Access
Protected or
high-capacity
Local traffic backhaul link
Access ATM, TDM, Ethernet
Up to 6 ODUs connected to a single subrack, with over 6 GB capacity throughput

Single packet matrix provides 16 GB switching capacity, with no need for an
external switch
Any traffic mix in any direction, with no need to duplicate I/O cards
Nodal solution minimize equipment, reduce power consumption and cabling

I/O input/output
MSS Microwave Service Switch
ODU outdoor unit

3JK Issue 1.00
Blank Page


3JK Issue 1.00
2 MPR in New Market Segments


3JK Issue 1.00
2.1 The Most Effective Solution
Full outdoor Split mount application Networking and MW
Common ODU
Current
Market
offering
Dedicated system
for full outdoor Point to point
Nodal-IDU IDU P2p + external
applications networking gear
Segments
Growth are
LTE driven
9500 MPR MPLS networking gear
-Hybrid solution
TDM native quality
--low cost ptp- Today seldom used in mobile backhauling,
Tree/star/spoke topology mainly in WiMax/enterprise applications
- Physical link protection (1+1) Represents the vast majority
-link availability 99.999 of the MW market
- Nodal configuration
Today addressed with 2 boxes; MW + SDH/SONET
gear, trend moving toward MPLS based technology
9500 MPR Release 2 : Multipurpose ODU, to address all applications


3JK Issue 1.00
2.1 The Most Effective Solution [cont.]
Multi purpose Microwave Radio Concept
Single MW solution
across multiple use
Hybrid Stand Alone Nodal Integrated MW in

Connectivity Split-Mount fiber Node
Any BS
Any CPE
NO IDU
MSS-1c Optimize MSS-4/8 SAR/TSS
Optimize Optimize Optimize Optimize
Fixed/Mobile
E1 and Ethernet Ethernet Only Microwave Nodal MPLS Node
Convergence
Site Site Site Site
Carrier Ethernet MPLS

Carrier Ethernet MPLS


3JK Issue 1.00
2.2 MPR-e Enabling Zero-Footprint Microwave Configurations
9500 MPR-e
Gigabit Ethernet Gigabit Ethernet
MPT MPT
9500 MPR-e
9500 MPR-e 9500 MPR
Optimize
Nodal Site IP/MPLS Route
Ethernet Only Site
MPR-e enable zero footprint configurations in Ethernet Only sites


3JK Issue 1.00
2.3 MPR in Last Mile
Up to 12 ODUs
Up to 6 ODUs
Extended 9500 MPR packet transport family to cover last mile access MSS-1c
Low cost, rack length, Very low power consumption, MW radio protection, Hybrid & Packet operational
modes
Multipurpose ODU the MPT; to cover all MW applications under a single platform
Zero foot print for Ethernet applications, common to all MSS platform, enables integrated solution for MPLS
metro network
Introducing 9500 MPR-e stand-alone full outdoor
Existing compatibility with 9500 MXC
- Introducing backward compatibility to 9400 AWY to address existing hybrid deployments

3JK Issue 1.00
2.4 LTE and Full Ethernet 3G Ready
Voice, signalling, NMS, CBR Best Effort classes
Guaranteed CPU
throughput @ (core)
Queue #8 4QAM
HPQ+CAC
DATA AWARE PROCESSING

PACKET FRAGMENTATION
Queue #7
Queue #6
Traffic Traffic Queue #5 Radio

RF
From Classification Framer &
Core (CoS) Modem
Queue #4
802.1p bits DWRR

IPV4 DiffSerf Queue #3
IPV6 Diffserv
VLAN-ID
Ethertype Queue #2
MPLS Exp. bits
Queue #1
Scheduler
HPQ + Call Admission Control per radio direction is the only way to guarantee
Voice (high priority) performances

3JK Issue 1.00
2.5 From Current PDH/SDH Network to Packet Transport
Network Evolution
Access Aggregation Microwave Microwave
(tree, star) (ring/mesh)
Current Networking Transmission
Solution Solution
Mix of techno in the RAN
PDH/SDH/ETH NG-SDH
Deploy Packet Microwave PDH/SDH/ETH NG-SDH
In Hybrid Mode (9500 MPR)
In the access connecting to 9500 MPR
existing SDH aggregation 9500 MPR-e
Evolution MSS
Converge to a Pseudo Wire
Packet
Packet infrastructure
Microwave
Microwave MPLS
MPLS Enable Packet Mode in
Packet Microwave (9500-MPR)
Deploy MPLS in the aggregation
E2E Circuit emulation/PW
MPT
SAR
Focus on MPLS aggregation
Integrated 9500 MPR Microwave
solution in IP/MPLS 7705 SAR nodes
IP/MPLS
IP/MPLS
IP/MPLS
9500 MPR and 9500 MPR-e in any network topology

3JK Issue 1.00
2.6 MPR addresses All Microwave Applications in Aggregation
MPT
Mobile Antenna MPT

MPT or MPT
Eth ODU300 or
MSS 1c ODU300
TDM
9500 MPR
MPT
MPT
Eth MPT
Mobile Antenna
or
Eth ODU300
9500 MPR
9500 MPR-e
MPT
or MSS-8
ODU300
9500 MPR
Mobile Antenna
Eth
Eth
ATM
ATM Packet Microwave
MSS-4 TDM
TDM
9500 MPR Mobile Antenna
Hybrid, Packet and Full outdoor with a single product 9500 MPR

3JK Issue 1.00
2.7 MPR addresses Metro Ring/Partial Mesh Application
Mobile Antenna
9500 MPR-e
Ring/Partial mesh 9500 MPR-e
Eth IP/MPLS Metro Network
TDM
9500 MPR
Eth
IP/MPLS
Eth
ATM 9500 MPR-e
TDM
Mobile Antenna
MW Access 7705 SAR-8

Network 7705 SAR-18
7705 SAR-8
7705 SAR-8
7705-SAR single node solution for

MW and fiber aggregation rings. Can
be also used as access network hub
connected to the far end with as
9500 MPR node.
7705 SAR-M


3JK Issue 1.00
Blank Page


3JK Issue 1.00
3 System Description


3JK Issue 1.00
3.1 Alcatel-Lucent 9500 Microwave Packet Radio
E1, STM-1, ATM-IMA and Eth

No performance
degradation


3JK Issue 1.00
3.2 9500 MPR System Family
9500 MPR radio system family supports, in a common platform,

PDH E1, SDH STM1, ATM-IMA traffic and packet data (Ethernet) applications.
Outdoor transceivers are available
in the frequency range from 6 GHz up to 38 GHz and 80 GHz.
For the Outdoor transceiver,
1+0 is the optimized configuration, with branching systems outside the ODU,
1+1 configuration is obtained with external dedicated mechanical arrangement.
MSS-8 MSS-4 MSS-1c No IDU
MSS-8 MSS-4 MSS-1c Zero-

(2U height) (1 U height) (1U height) footpri
(19 rack (19 rack (half 19 rack nt
length) length) length)
MPT
Up to 12 with Up to 6 with Up to 2 with Ge MPT
ethernet ethernet ethernet cable
cable cable
Up to 6 with Up to 2 with - - ODU ODU 300
coaxial cable coaxial cable 300
Up to xx Up to x with - - AWY
AWY-ODU
coaxial cable coaxial cable ODU

Backward compatibility with hybrid installed base

3JK Issue 1.00
3.2 9500 MPR System Family [cont.]
9500 MPR
Microwave Packet Radio
MPR-e Three types of Three types of MSS

Stand alone OutDoor Unit (Microwave Service Switch)
MSS-8
( 8 slots )
MPT ODU 300
MSS-4
( 4 slots )
MPT
MSS-1c
( Terminal InDoor Unit )
AWY-ODU

9500 MPR in the stand alone (zero-footprint) architecture is built by only one unit for Ethernet
applications:
Outdoor Unit.
Outdoor Unit is connected to the MPLS metro networks equipment with one coaxial cable for the
power supply and one Ethernet optical or electrical cable (with MPT).
9500 MPR in the split mount architecture is built by two separate units:
MSS (Microwave Service Switch): indoor unit for split mount and stand alone configurations
(Ethernet uplink)
Outdoor Unit.
MSS and Outdoor Unit are connected with a single standard coaxial cable (with ODU300 or AWY
ODU) or with one coaxial cable for the power supply and one Ethernet optical or electrical cable
(with MPT).

3JK Issue 1.00
3.3 9500 MPR Key Features


3JK Issue 1.00
3.3 9500 MPR Key Features [cont.]
Link Aggregation Group (Radio/Ethernet):

Link Aggregation groups a set of ports so that two network nodes can be
interconnected using multiple links to increase link capacity and availability
between them.
When aggregated, two or more physical links operate as a single logical link
with a traffic capacity that is the sum of the individual link capacities.
This doubling, tripling or quadrupling of capacity is relevant where more
capacity is required than can be provided on one physical link.
Link aggregation also provides redundancy between the aggregated links. If a
link fails, its traffic is redirected onto the remaining link, or links.
If the remaining link or links do not have the capacity needed to avoid a
traffic bottleneck, appropriate QoS settings are used to prioritize traffic so
that all high priority traffic continues to get through.
The Link Aggregation is performed according to 802.3ad and can be applied
to Radio ports and to User Ethernet ports.


3JK Issue 1.00
3 System description
3.4 9500 MPR Node

The 9500 MPR Node supports up to 6 RF links for operation on the same or different frequency bands
using the MSS-8 Unit.
The ODU for each link is connected to plug-in card inside the site aggregator.
Other plug-in cards provide line interface access (TDM and native IP), management, and so on.
9500 MPR Node supports a mix of non-protected and protected or diversity operation for single link,
repeater or star radio configurations.

3JK Issue 1.00
3.4 9500 MPR Node [cont.]
Local traffic Highest switching capacity (16 Gb/s)

NxE1 TDM and capacity throughput (>4 Gb/s) in
NxIMA ATM the market, and E1 termination (up to
NxF/Gig Ethernet 192xE1s)
Operational modes 5x less space in nodal configuration
Hybrid and packet mode (compared to traditional hybrid-only
nodes)
Microwave trunk
MSS-8: up to 12 ODUs 6x less power consumption in
MSS-4: up to 6 ODUs 6 directions packet node (compared
to traditional hybrid systems)
MSS-8 Operates as:
Split mount Hybrid or packet node
MSS-4
Commercial 9500 MPR

9500 MPR-e
Item
MSS-4/8 MSS-4/8
MSS-8/-4 9500 MPR
NE: 9500 MPR 9500 MPR

NE: 9500 MPR

Microwave Service Switch 4/8 (MSS-4 / MSS-8)

3JK Issue 1.00
MSS-8
Slot 1 Slot 2
Slot 3 Slot 4
Slot 9
Slot 5 Slot 6
Slot 7 Slot 8
Slot 1 reserved for Core-E Main

Slot 2 reserved for Core-E Spare
Slot 3 to 8 Universal (any Tributary unit or Modem unit or MPT Access
unit)
Slot 8 can be equipped also with AUX peripheral card
Slot 9 reserved for FANS
The cards belonging to a protected configuration must be installed on the
same row (the Main card is on the left side, the Spare card is on the right
side)

Supports 6 Unprotected links or

1 Protected and 4 Unprotected links or
2 Protected and 2 Unprotected links or
3 Protected links

3JK Issue 1.00
Simplified block diagram of the MSS-8


3JK Issue 1.00
MSS-4
Slot 1 Slot 2
Slot 5
Slot 3 Slot 4
Slot 1 reserved for Core-E Main

Slot 2 reserved for Core-E Spare
Slot 3 and 4 Universal (any Tributary unit or Modem unit or MPT Access
unit)
Slot 4 can be equipped also with AUX peripheral card
Slot 5 reserved for FANS
In case of protected configuration the Main card is on the left side, the
Spare card is on the right side.

Supports 2 Unprotected links or

1 Protected link

3JK Issue 1.00
Simplified block diagram of the MSS-4


3JK Issue 1.00
MSS implements functionalities of grooming, routing, switching and

protection, exploiting a packet oriented technology.
The Core-E platform, with symmetrical cross-connection functions,
manages different radio directions, with the possibility to add-drop
tributaries in case of local TDM/Ethernet accesses. Core-E platform is
based on packet technology (Ethernet Switch) with a generic interface
serial GbEth between Core-E and peripherals
The peripherals are independent modules connecting the Core-E to a
set of different external interfaces, through a high speed serial bus.
The available peripherals are:
32xE1 PDH access unit, ASAP access unit (ATM 16xE1), AUX peripheral unit
STM-1 local access module
Modem unit (to interface the ODU300)
MPT Access card and MPT Access card with PFoE (to interface the MPT)
AWY Access card (to interface the ODU AWY)
The TDM incoming traffic is converted into Ethernet packets and then
sent to the Ethernet switch; the packet overhead is optimized before to
be sent in the air.

32E1/DS1 PDH access unit: provides the external interfaces for up to 32xE1 tributaries, manages the
encapsulation/reconstruction of PDH data to/from standard Ethernet packets and sends/receives
standard Ethernet packets to/from both Core-E modules; it contains the switch for the EPS Core-E
protection and the DC/DC converter unit.
STM-1 local access module: provides the external interfaces for up to 2 electrical or optical STM-1
signals, manages the encapsulation/reconstruction of SDH data to/from standard Ethernet packets and
sends/receives standard Ethernet packets to/from both Core-E modules; it contains the switch for the
EPS Core-E protection and the DC/DC converter unit.
ASAP access unit: provides the external interfaces to transport 16xE1 ATM traffic, with E1/IMA physical
layer, in an MPR network. ATM traffic is transported within MPR network as "special" Ethernet traffic.
This "special" Ethernet traffic is managed by MPR following to RFC 4717 (IETF ATM PseudoWire
EdgetoEdgeeEmulation, PWE3) with N-1 encapsulation format.
AUX peripheral unit: provides the external interfaces for Service Channels access and Housekeeping
alarms.
Modem unit: this unit is used to interface the ODU300. It sends/receives standard Ethernet packets
to/from both Core-E modules, manages the radio frame (on Ethernet packet form)
generation/termination, the interface to/from the alternate Radio module (for RPS management), the
cable interface functions to ODU; it contains the logic for the EPS Core-E protection, the RPS logic and
the DC/DC converter unit.
MPT access card (with PFoE): this unit is used to interface the MPT. PFoE (Power Feed over Ethernet) is
used to carry the power supply to the MPT-MC through an electrical Ethernet traffic connector.
AWY access card: this unit is used to interface the ODU AWY. It sends/receives standard Ethernet
packets to/from both Core-E modules. It contains the logic for the EPS Core-E protection and the
DC/DC converter unit.

3JK Issue 1.00
Stacking Configuration

To manage more directions the Stacking configuration can be realized by installing up to 3 MSS,
interconnected through the Ethernet ports in the Core-E module. In the example of Figure are shown
two interconnected MSS.

3JK Issue 1.00
Stacking Configuration [cont.]

With the Core protection max. 2 MSS can be interconnected as shown in figure.
To implement this configuration the LOS alarm on the Ethernet ports must be enabled as switching
criterion of the Core protection. To enable this alarm the Ethernet LOS Criteria feature has to be
enabled.

3JK Issue 1.00
3.5 9500 MPR Terminal

The 9500 MPR Terminal supports up to 2 RF links for operation on the same or different frequency
bands using the MSS-1c Unit.
The ODU for each link is connected to MSS-1c Unit inside the site aggregator.
9500 MPR Terminal supports non-protected and protected or diversity operation for single link radio
configurations.

3JK Issue 1.00
3.5 9500 MPR Terminal [cont.]
Local traffic 50% space reduction compared to

4x F/Gig Ethernet traditional terminal IDU in 1+0
10xE1 configuration
Operational modes 4x less space for MW radio
Hybrid and packet mode protection with single size IDU
Microwave trunk 7x more capacity then 64 Mb/s
MSS-1c
2xMPT ODU connections (32xE1) traditional terminals
(electrical/optical Ethernet)
Operates as:
Point-to-point link Last mile/remote site for node
Traditional
point-to-point IDU
(e.g., 9400 AWY
IDU)
Commercial MSS-1c
MSS-1c
Item
MSS-1c MSS-1c
MSS-8/-4 MSS-1c
NE: 9500 MPR MSS-1c NE: 9500 MPR

Microwave Service Switch 1 Terminal (MSS-1c)

3JK Issue 1.00
Packet Radio Solution for Tail ODU300 ODU300
Cost effective solution

Compact : 1U rack size
Fully part of MPR family
MSS 8 MSS 8
Low power consumption (13 W)
MPT MPT
MPT
MPT
MSS 8
Eth
TDM
MSS 1c
MSS-1c + MPT: Compact and Low Consumption Solution for Tail

MSS-1c Characteristics:
- 10 x E1 (hybrid TDMtoTDM and Packet Mode TDMtoETH)

- 4 GEthernet user ports
- Up to 2 MPT
1+0,
1+1,
repeater configurations.
- L2 switch
QoS (IEEE 802.1p),
Diffserv,
VLAN management.
- SynchE
- Housekeeping
- 2 ports for TMN chaining

3JK Issue 1.00
Simplified block diagram of the MSS-1c FAN unit connector
Power Lightning
supply PSU
Protection
HK PFoE
(not supported FPGA
in the current
release)
8 E1 INTERFACE
MPT1 (opt. Int.)
8 E1
INTERFACE
MPT2 (opt. Int.)
RADIO
LIU IWF ETHERNET MPT1 (elect. Int.)
2
2 E1 SWITCH MPT2 (elect. Int.)
LCT RJ45
NMS1 RJ45
MSS-1c
NMS2 RJ45
4x 10/100/1000
Ethernet ports
MSS1-c platform:
symmetrical Cross-connection function
able to manage different radio directions
add-drop tributaries in case of local PDH/Ethernet accesses
2 x Electrical GbEth + 2 x Optical GbEth
Peripherals
10 x E1 local access function (2 x Sub-D 37 pins)
MPT Access function (to MPT)

3JK Issue 1.00
Compact IDU (MSS-1c) implements functionalities of grooming, routing,

switching and protection, exploiting a packet oriented technology.
The MSS-1c, with symmetrical cross-connection functions, manages different
radio directions, with the possibility to add-drop tributaries in case of local
PDH/Ethernet accesses. MSS-1c is based on packet technology (Ethernet Switch)
with a generic interface serial GbEth between Ethernet Switch and peripherals
The peripherals are independent functions inside the compact IDU (MSS-1c)
connecting the Ethernet Switch to a set of different external interfaces,
through a high speed serial bus. The available peripherals are:
10 x E1 local access function
MPT Access function (to interface the Microwave Packet Transport)
The PDH incoming traffic is converted into Ethernet packets and then sent to
the Ethernet switch; the packet overhead is optimized before to be sent in the
air.

10E1/DS1 local access function: provides the external interfaces for up to 10xE1 tributaries,
manages the encapsulation/reconstruction of PDH data to/from standard Ethernet packets and
sends/receives standard Ethernet packets to/from Ethernet Switch.
MPT access function: this function is used to interface the Microwave Packet Transport (MPT). The
interface to the MPT is a standard GbEth interface (electrical or optical). It sends/receives standard
Ethernet packets to/from Ethernet Switch.

3JK Issue 1.00
3.6 OutDoor Unit 300
ODU300 (Static Modulation) : Radio capacity, channelling and modulation
Channel FCM Mode ETSI Class # E1 (TDM2TDM) Ethernet Throughput (1518 bytes)
4 QAM 2 4 E1 9,3 Mbit/s
7 MHz 16 QAM 4 8 E1 19,9 Mbit/s
64 QAM 5 13 E1 30,5 Mbit/s
4 QAM 2 8 E1 19,9 Mbit/s
14 MHz 16 QAM 4 18 E1 41,1 Mbit/s
64 QAM 5 27 E1 62,3 Mbit/s
4 QAM 2 18 E1 41,1 Mbit/s
16 QAM 4 37 E1 83,6 Mbit/s
32 QAM 4 48 E1 107,3 Mbit/s
28 MHz
64 QAM 5 56 E1 126,1 Mbit/s
128 QAM 5 68 E1 151,7 Mbit/s
256 QAM 6 77 E1 172,0 Mbit/s
16 QAM 4 72 E1 161,0 Mbit/s
56 MHz 128 QAM 5 136 E1 304,7 Mbit/s
256 QAM 6 150 E1 335,9 Mbit/s

The table summaries the relations among Radio capacity, channelling scheme and modulation (Static
Modulation).

3JK Issue 1.00
3.6 OutDoor Unit 300 [cont.]
ODU300 (Adaptative Modulation) : Radio capacity, channelling and modulation
Channel Spacing ACM Mode ETSI Class # E1 (Note) Ethernet Throughput

(TDM2TDM) (1518 bytes)
4 QAM 2 18 E1 41,1 Mbit/s
28 MHz 16 QAM 4 37 E1 83,6 Mbit/s
64 QAM 5 56 E1 126,1 Mbit/s
4 QAM 2 8 E1 19,9 Mbit/s
14 MHz 16 QAM 4 18 E1 41,1 Mbit/s
64 QAM 5 27 E1 62,3 Mbit/s
4 QAM 2 4 E1 9,3 Mbit/s
7 MHz 16 QAM 4 8 E1 19,9 Mbit/s
64 QAM 5 13 E1 30,5 Mbit/s

Note:
The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive
Modulation) can be enabled or disabled.
When the Admission Control is enabled, the check is performed taking into account the capacity of
the 4 QAM modulation scheme for the relevant Channel Spacing.
When the Admission Control is disabled, the check is performed taking into account the capacity of
the highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-16-64 QAM range or
16 QAM for 4-16 QAM range).

3JK Issue 1.00
2 9500MPR Family
3.7 Microwave Packet Transport
What is MPT ?
It is a new multipurpose ODU to address any microwave application,

extremely compact in size providing:
MPT MC up to 200Mbps
MPT HC/MPT-HC V2 up tp 440Mbps
MPT GC millimeter wave
MPT-xx can be deployed in stand-alone configuration (9500 MPR-e) or
it can be deployed in split mount solution connected to any MSS-x IDU.
Up to 12 MPT connected to an MSS-8; highest density ever
Up to 6 MPT connected to an MSS-4; highest density ever
Up to 2 MPT HC/MC connected to MSS-1c
9500 MPR-e it is the stand alone, full outdoor application of the MPT xx
to address full Ethernet site backhauling (fix or mobile alike).
Deployed together with 7705SAR or 1850 TSS to address converged MPLS
metro networks reducing the number of deployed equipment.


3JK Issue 1.00
3.7 Microwave Packet Transport [cont.]
Local traffic Single solution to operate as

Gig Ethernet standalone and split-mount
Microwave capacity Interconnect Cable
MPT-GC up to 1 Gb/s Gig Ethernet
Millimeter wave CAT-5 electrical or optical
MPT-MC
Typical 157 Mb/s, 64-byte Ethernet 240 Mb/s
MPT-HC up to 530 Mb/s
Typical 350 Mb/s, 64-byte Ethernet 530 Mb/s
Operates as:
MPT
9500 MPR-e network element 9500 MPR network element
stand-alone solution split-mount solution
Commercial
Item
MSS-1c MSS-8/-4
NE: 9500 MPR-e NE: 9500 MPR


3JK Issue 1.00
MPT-HC/MPT-HC V2/MPT-MC : Radio capacity, channelling scheme
and modulation (Static Modulation) (1/2)
Channel Spacing FCM Mode ETSI Class # E1 Typical Ethernet Throughput

(MHz) (TDM2TDM) (1518 bytes)
4 QAM 2 4 8,8 Mbit/s
16 QAM 4 9 19,4 Mbit/s
32 QAM 4 11 24,2 Mbit/s
7
64 QAM 5 13 29,6 Mbit/s
128 QAM 5 16 35,4 Mbit/s
256 QAM (NB3) 6 19 40,6 Mbit/s
4 QAM 2 9 19,9 Mbit/s
16 QAM 4 19 40,7 Mbit/s
32 QAM 4 23 50,3 Mbit/s
14
64 QAM 5 29 62,0 Mbit/s
128 QAM 5 34 73,5 Mbit/s
256 QAM (NB3) 6 41 86,7 Mbit/s

Modulation).
N.B.1: New ETSI mask.
N.B.2: MPT-MC does not support this Channel Spacing.
N.B.3: MPT-MC does not support this FCM mode.

3JK Issue 1.00
and modulation (Static Modulation) (2/2)
Channel Spacing FCM Mode ETSI Class # E1 Typical Ethernet Throughput

(MHz) (TDM2TDM) (1518 bytes)
4 QAM 2 (NB1) 19 41,1 Mbit/s
16 QAM 4 (NB1) 39 83,5 Mbit/s
32 QAM 4 50 106,9 Mbit/s
28
64 QAM 5 60 128,4 Mbit/s
128 QAM 5 71 151,9 Mbit/s
256 QAM (NB3) 6 85 180,2 Mbit/s
64 QAM 5 88 186,1 Mbit/s
40 (NB2)
128 QAM 5 104 220,1 Mbit/s
16 QAM 4 75 159,3 Mbit/s
32 QAM 4 92 195,6 Mbit/s
56 (NB2) 64 QAM 5 119 252,2 Mbit/s
128 QAM 5 141 298,2 Mbit/s
256 QAM 6 160 339,4 Mbit/s

Modulation).
N.B.1: New ETSI mask.
N.B.3: MPT-MC does not support this FCM mode.

3JK Issue 1.00
and modulation (Adaptive Modulation) (1/2)
Channel Spacing ACM Mode ETSI Class Modulation range Typical Ethernet
(MHz) Reference Throughput
(1518 bytes)
4 QAM 2 4 QAM to 256 QAM 8,8 Mbit/s
7
14

Note:
the lowest modulation scheme for the relevant Channel Spacing.
the highest modulation scheme for the relevant Channel Spacing.

3JK Issue 1.00
and modulation (Adaptive Modulation) (2/2)
Channel Spacing ACM Mode ETSI Class Modulation range Typical Ethernet
(MHz) Reference Throughput
(1518 bytes)
28
32QAM 4 32 QAM to 256 QAM 106,9 Mbit/s
64QAM 5 64 QAM to 256 QAM 128,4 Mbit/s
40 (NB1) 64 QAM 5 64 QAM to 128 QAM 186,1 Mbit/s
56 (NB1) 32 QAM 4 32 QAM to 256 QAM 195,6 Mbit/s

Note:
the lowest modulation scheme for the relevant Channel Spacing.
the highest modulation scheme for the relevant Channel Spacing.

3JK Issue 1.00
4 Radio Configuration


3JK Issue 1.00
4 Radio Configuration
4.1 Radio Configuration
1+0 unprotected
1+1 Hot-Standby (HSB)

two types of coupler for ODU300:
3 dB/3 dB balanced coupler or 1.5 dB/6.0 dB unbalanced coupler
two types of coupler for MPT-HC/MPT-MC:
3 dB/3 dB balanced coupler or 1 dB/10 dB unbalanced coupler
1+1 Hot-Standby Space Diversity (HSB SD) (no coupler)
1+1/2x(1+0) Frequency Diversity (FD) (co-polar)
1+1/2x(1+0) Frequency Diversity (FD) (hetero-polar)

N.B.: MPT-MC does not support the FD configuration.

N.B.: In 1+1 configuration the 2 Outdoor Units must be of the same types.

3JK Issue 1.00
5 System Configuration


3JK Issue 1.00
5.1 Example of System configurations
PDH/ATM Over Ethernet Packet Node

Mapping of 32 E1 TDM and 16 E1 ATM on Ethernet
Embedded
interfaces
Embedded
interfaces
MSS
ETH
ETH
Ethernet
Ethernet
Switch
Switch
ATM
Peripheral
TDM
Peripheral
E1 ATM
Peripheral
E1 TDM
Peripheral
16 E1
32 E1
16
32


3JK Issue 1.00
5.1 Example of System configurations [cont.]
PDH/SDH/ATM and Ethernet Terminal Packet Transport

32 E1 TDM and 16 E1 ATM Access, 1 Radio Direction
Embedded
interfaces
Embedded
interfaces
MSS
ETH
ETH
MW
MW ODU
ODU Ethernet
Ethernet
Peripheral
Peripheral Switch
Switch
ATM
Peripheral
TDM
Peripheral
E1 ATM
Peripheral
E1 TDM
Peripheral
16 E1
32 E1
16
32


3JK Issue 1.00
PDH/SDH/ATM and Ethernet Add/Drop N1 Packet Node

Ethernet and 32 E1 TDM and 16 E1 ATM Local Access, 2 unprotected links
Embedded
interfaces
Embedded
interfaces
MSS
ETH
ETH
MW
MW ODU
ODU Ethernet
Ethernet MW
MW ODU
ODU
Peripheral
Peripheral Switch
Switch
TDM
Peripheral
Peripheral
ATM
Peripheral
Peripheral
E1 TDM
E1 ATM
Peripheral
Peripheral
16 E1
32 E1
16
32


3JK Issue 1.00
PDH/SDH/ATM and Ethernet Terminal Packet Node

Ethernet and 32 E1 TDM and 16 E1 ATM Local Access, 1 protected link
Embedded
interfaces
Embedded
interfaces
MSS
ETH
ETH
MW
MW ODU
ODU
Peripheral
Peripheral
Ethernet
Ethernet
MW
MW ODU
ODU Switch
Switch
Peripheral
Peripheral
ATM
Peripheral
TDM
Peripheral
E1 ATM
Peripheral
E1 TDM
Peripheral
16 E1
32 E1
16
32


3JK Issue 1.00
PDH/SDH/ATM and Ethernet Add/Drop Packet Node

Ethernet and 32 E1 TDM and 16 E1 ATM Local Access,
1 unprotected link and 1 protected link
Embedded
interfaces
Embedded
interfaces
MSS
ETH
ETH
MW
MW ODU
ODU MW
MW ODU
ODU
Peripheral
Peripheral Peripheral
Peripheral
Ethernet
Ethernet
Switch MW
MW ODU
ODU
Switch
Peripheral
Peripheral
ATM
TDM
Peripheral
Peripheral
E1 ATM
E1 TDM
Peripheral
Peripheral
16 E1
32 E1
16
32


3JK Issue 1.00
Blank Page


3JK Issue 1.00
End of Module
Introduction


3JK Issue 1.00
12
Section 1
Product Overview
Module 2
Architecture
3JK Edition 1.00
All Rights Reserved 2007, Alcatel-Lucent

3JK Edition 1.00
Blank Page

Product Overview Architecture
Document History
01 2007-07-30 External Consultant First edition
02 2011-02-02 External Consultant Update to rel. 3.0

Vimercate

3JK Edition 1.00
Objectives
Objectives: to be able to
describe the main functionalities of the 9500 MPR
Node and Terminal.


3JK Edition 1.00
Objectives [cont.]


3JK Edition 1.00
Table of Contents
Switch to notes view! Page
1 MSS Architecture 7
1.1 9500 MPR Architecture 8
1.2 MSS 9
1.3 Flash Cards with Licences 11
1.4 ODUs 12
1.5 MSS-ODU300 cable (Interfaces and Traffic) 13
1.6 MPT 14
1.7 MSS-MPT Cable (Interfaces and Traffic) 15
1.7.1 MPT-HC connectivity 16
1.7.2 MPT-HC V2 connectivity 19
1.7.3 MPT-MC connectivity 23
Blank Page 26
2 Traffic Profiles 27
2.1 Managed Services and profiles 28
2.1.1 TDM to TDM flow 29
2.1.2 TDM to ETH flow 30
2.1.3 SDH to SDH flow 31
2.1.4 ETH to ETH flow 32
2.1.5 ATM to ATM flow 33
2.1.6 ATM to ETH flow 34
2.2 Traffic profiles 35
2.3 TDM2TDM 38
2.4 TDM2Eth 40
1 2 5 2.5 SDH2SDH All Rights Reserved Alcatel-Lucent 2011 42
2.6 ATM Traffic
Management
44
2.7 ETH2ETH 47
2.8 Ethernet Traffic Management 48
3 Traffic Management (QoS) 51
3.1 Quality Of Services (QoS) in the MPR Node 52
3.1.1 QoS in the Core-E 53
3.1.2 Radio Air Block QoS 55
3.1.3 How 9500 MPR manage QoS 57
3.1.4 Flows classification 59
3.2 Quality Of Services (QoS) in the MPR Terminal 63
3.2.1 QoS in the MSS-1c 64
3.2.2 Flows classification 66
3.3 Quality Of Services (QoS) in the MPT 68
3.3.1 Radio Air Block QoS for MPR Node 69
3.3.2 Radio Air Block QoS for MPR Terminal 70
3.3.3 Radio Air Block QoS Scheduler 71
3.4 Quality Of Services (QoS) in the MPR-e 72
Blank Page 74
4 LAG (Link Aggregation Group) 75
4.1 LAG overview 76
4.1.1 Link aggregation on Radio ports (Radio LAG) 77
4.1.2 Link aggregation on User Ethernet ports (Ethernet LAG) 79
Blank Page 80
5 Synchronisation 81
5.1 Synchronisation 82
5.2 Clock Source Selection and Distribution 88
5.3 Differential/Adaptative clock recovery 89
5.4 Synchronisation Interface 92
5.5 Synchronisation Interface 93
5.6 Synchronisation Interface in MPR-e 97
6 Cross-connections 98

3JK Edition 1.00
6.1 Cross-connection 99
6.2 E1 Cross-connection 101
6.3 STM-1 Cross-connections 102
6.4 Radio-Radio Cross-connection 103
6.5 Ethernet Cross-connection 104
6.6 ATM PW Cross-connection 105
6.7 ATM Light Cross-connection Provisioning 106
6.8 MAC SA of ATM PW Generated by ASAP Unit 107
Blank Page 108
7 Protections with ODU300 109
7.1 Protections with ODU300 110
7.2 RPS Switching Criteria 113
7.3 EPS Switching Criteria 114
7.4 HSB Switching Criteria 115
Blank Page 116
8 Protections with MPT-HC/MPT-HC V2 117
8.1 Protections with MPT-HC/MPT-HC V2 118
8.2 RPS Switching Criteria 121
8.3 EPS Switching Criteria 122
8.4 HSB Switching Criteria 123
Blank Page 124
9 Protection with MPT-MC 125
9.1 Protection with MPT-MC 126
1 2 6 9.2 EPS Switching Criteria All Rights Reserved Alcatel-Lucent 2011 128
9.3 HSB Switching
Criteria
129
Blank Page 130
10 Core-E protection 131
10.1 Core-E protection 132
10.2 Core-E protection Switching Criteria 136
Blank Page 137
End of Module 138

3JK Edition 1.00
1 MSS Architecture


3JK Edition 1.00
1 MSS Architecture
1.1 9500 MPR Architecture
Embedded
interfaces
Embedded
interfaces
ETH
ETH
ASAP board
Patented data-aware algorithms:
Service type is recognized
Bandwidth Optimization NxE1 ATM-IMA
Latency control ATM
ATM
BER improvement
Peripheral
Peripheral
MW ATM PseudoWiring
MW ODU
ODU 16
16 Gb/s
Gb/s
Peripheral
Peripheral Ethernet
Ethernet Switch
Switch
Standard Gigabit Ethernet
Peripheral
Peripheral
SDH/TDM
SDH/TDM
SDH or TDM over Ethernet standard

mapping
Microwave Transport
NxE1 TDM Stream
2xSTM-1 Stream
This chart shows the architecture of MPR equipment. The core of the device is a 10 gb/s Ethernet
switch able to manage several kinds of peripheral [TDM, ETHERNET (embedded) and ATM-IMA (from
R.1.3)] and interface the packetized tributaries with the MW ODU through an apposite peripheral
endowed of patented data-aware algorithms for bandwidth optimization and BER improvement.

3JK Edition 1.00
1 MSS Architecture
1.2 MSS
Access Core-E Radio

Peripherals Peripherals
Flash
PSU Controller
RAM
GbEth
32xE1 Access
Module MPT Access Module
(Giga Ethernet
GbEth interface)
ASAP Access ETHERNET (to MPT-HC/MPT-MC)
Module
SWITCH
GbEth GbEth
AUX MODEM Module
Peripheral (IF interface)
Module (to ODU300)
GbEth
2xSTM-1
Access
Module
LIU LIU
4x10/100/1000 2 SFPs
MSS-8 MSS-4
Ethernet (Optional)

Core-E platform:
add-drop tributaries in case of local PDH/ASAP/Ethernet accesses
4 x Electrical GbEth + 2 optional SFPs
Peripherals (6 modules in MSS-8; 2 modules in MSS-4)
32 x E1 PDH access module (SCSI 68 32E1)
2 x STM-1 access module (2 optional electrical or optical SFP)
ASAP (ATM 16xE1) access module (SCSI 68 16E1)
AUX peripheral module
Modem module (to ODU300)
MPT Access module (to MPT)

3JK Edition 1.00
1 MSS Architecture
1.2 MSS [cont.]
FAN unit connector
Power Lightning
supply PSU
Protection
HK PFoE
(not supported FPGA
in the current
release)
8 E1 INTERFACE
MPT1 (opt. Int.)
8 E1
INTERFACE
MPT2 (opt. Int.)
RADIO
LIU IWF ETHERNET MPT1 (elect. Int.)
2
2 E1 SWITCH MPT2 (elect. Int.)
LCT RJ45
NMS1 RJ45
MSS-1c
NMS2 RJ45
4x 10/100/1000 MSS-1c
Ethernet ports
MSS1-c platform:
add-drop tributaries in case of local PDH/Ethernet accesses
2 x Electrical GbEth + 2 x Optical GbEth
Peripherals
10 x E1 local access function (2 x Sub-D 37 pins)
MPT Access function (to MPT)

3JK Edition 1.00
1 MSS Architecture
1.3 Flash Cards with Licences
The licences are stored in the Flash card installed in the Core-E.
Different types of licence according to:
Capacity
Service: TDM2TDM or TDM2ETH
Static Modulation (FCM) or Adaptive Modulation (ACM)
Note: The Flash card stores

1. The License
2. The Equipment Software
3. The Equipment MIB
4. The Equipment MAC Address.


3JK Edition 1.00
1 MSS Architecture
1.4 ODUs
Several types of ODU are available: ODU300 , MPT-HC (High Capacity) ,

MPT-MC (Medium Capacity)
Both ODUs are designed for direct-antenna mounting.
ODU300 and MPT-HC/MPT-HC V2 support:

Modulation rates from 4 QAM to 256 QAM
Bandwidths from 7 to 56 MHz
Frequency bands from 6 to 38 GHz
MPT-MC support:
Modulation rates from 4 QAM to 128 QAM
Bandwidths from 7 to 28 MHz


3JK Edition 1.00
1 MSS Architecture
1.5 MSS-ODU300 cable (Interfaces and Traffic)

A single 50 ohm coaxial cable connects a ODU300 Radio Interface to its ODU. The max. cable length is
up to 150 m. ODU cable, connectors and grounding kits are separatly provided.
The ODU cable carries DC power (-48 Vdc) for the ODU and five signals:
Tx telemetry
Rx telemetry
Reference signal to synchronize the ODU IQ Mod/Demod oscillator
311 MHz IQ modulated signal from the ODU300 Radio Interface (transmit IF)
126 MHz IQ modulated signals from the ODU (receive IF)
Signal extracting and merging is carried out in N-Plexers within the ODU300 Radio Interface and ODU.

3JK Edition 1.00
1 MSS Architecture
1.6 MPT
Two types of MPT are available:

MPT-MC
MPT-HC/MPT-HC V2
Both MPTs are designed for

direct-antenna mounting.
MPT-MC support:
Modulation rates from QPSK to 128 QAM
Bandwidths from 3,5 to 28 MHz
MPT-HC/MPT-HC V2 support:
Modulation rates from QPSK to 256 QAM
Bandwidths from 3,5 to 56 MHz

MPT-HC V2 is similar to MPT-HC from architecture standpoint and can be used as spare part of the
MPT-HC. The differences are:
MPT-HC V2 can be natively Ethernet powered through a proprietary PFoE (or as alternative by using
two cables, one coaxial cable for the Power Supply and one optical cable for the Ethernet Traffic
(as MPT-HC).
MPT-HC V2 is XPIC-ready (by the installation of a dedicated module). The XPIC connector will be
used, when this feature will be available.

3JK Edition 1.00
1 MSS Architecture
1.7 MSS-MPT Cable (Interfaces and Traffic)
Electrical connection
(for MPT-MC, MPT-HC and MPT-HC V2)
One cable connect an MPT Access unit in the MSS to its MPT.
This cable is an electrical Gigabit Ethernet cable with Power Feed over
Ethernet (Not for MPT-HC).
The max cable length for electrical Ethernet connection is 100 m.
Optical connection
(only for MPT-HC and MPT-HC V2)
Two cables connect an MPT Access unit in the MSS to its MPT.
One cable is a 50 ohm coaxial cable to send the -48 V power supply to
the MPT-HC/MPT-HC V2.
The second cable is an optical Gigabit Ethernet cable.
The max cable length for optical Ethernet connection is 500 m.

Note: By using the optional DC Extractor, installed close to the MPT-HC, the interconnection
between the MSS and the MPT-HC can be made with a single electrical Ethernet cable by using the
Power Feed over Ethernet (Ethernet traffic and Power Supply on the same cable). The DC Extractor
then separates the Power Supply from the Ethernet traffic, which are separately send to the MPT-
HC.

3JK Edition 1.00
1.7.1 MPT-HC connectivity
Power extractor
CAT5e
RJ45
Ethernet CAT5e Coaxial cable

Ethernet CAT5e and RJ45 QMA and N
MPT Access Card
MPT-HC electrical connectivity (up to 100m)

MPT Access Card PoE

2 MPT per MPT Access Card
2x Coax connection
(power feed in case of Optical connection)
2x SFP ports for optical connection option
2x 1000BaseT port with Power over CAT5e cable

(Electrical connectivity Data+Power over a single CAT cable)

3JK Edition 1.00
1.7.1 MPT-HC connectivity [cont.]
fiber Fiber
LC-LC
Coaxial cable
N-N Coaxial cable
QMA-N
Pigtail
RJ45-N
MPT-HC optical connectivity (up to 350m)

Pigtail: N-RJ45 two wires Transition Connector, Reference: 3CC52159AAxx

3JK Edition 1.00
1.7.1 MPT-HC connectivity [cont.]
Coaxial cable +lightning

arrestor
+ low pass
Ethernet CAT5e filter Optical cable Coaxial cable
Up to 100m + pigtail Up to 350m +lightning

arrestor
battery + low pass
filter
+ pigtail
battery
MPT-HC connectivity to CORE-E

Low Pass Filter: Reference: 1AB251350001
Lightning Arrestor: Reference: 3CC50030AAAA

3JK Edition 1.00
1.7.2 MPT-HC V2 connectivity
MPT-HC V2 One cable (MPT Access unit to MPT-HC V2)

One electrical Ethernet cable connects an MPT Access unit in the MSS to its MPT-HC V2 (the MPT Access
unit provides the PFoE).
The max cable length is 100 m.
The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45
tool (1AD160490001).

3JK Edition 1.00
1.7.2 MPT-HC V2 connectivity [cont.]
MPT-HC V2 Two cables (MPT Access unit to MPT-HC V2)

Two cables connect an MPT Access unit in the MSS to its MPT-HC V2:
One cable is a 50 ohm coaxial cable to send the power supply to the MPT-HC V2:
for length lower or equal to 100 m the power cable can be CAT5E cable to send the power supply to
the MPT-HC V2 . The Ethernet electrical cable is provided with connectors to be mounted on site
with the specific RJ45 tool (1AD160490001);
for length higher than 100m, the cable is a 50 ohm coaxial cable to send the power supply to the
MPT-HC V2
Note: In case of length lower than 100m and presence in the field of 1 coaxial alredy installed and
free it is recomended to use the coax cable to minimise the installation effort.
The second cable is an Ethernet optical cable.
The Ethernet optical cable is preassembled and available in different lengths (up to 450 m).
Note: A special cord adapter must be connected to the coaxial cable on the MPT-HC V2.

3JK Edition 1.00
MPT-HC V2 Two cables (MPT Access unit to MPT-HC V2)

Two cables connect an MPT Access unit in the MSS to its MPT-HC V2:
for length lower or equal to 100 m the power cable can be CAT5E cable to send the power supply to
the MPT-HC V2 . The Ethernet electrical cable is provided with connectors to be mounted on site
MPT-HC V2
Note: A special cord adapter must be connected to the coaxial cable on the MPT-HC V2.

3JK Edition 1.00
MPT-HC V2 Two cables (Core-E unit to MPT-HC V2)

Two cables connect the MPT:

one optical cable connected to port#5 or port #6 of the Core-E unit
a coaxial cable connected to the station battery to provide the power supply.

3JK Edition 1.00
1.7.3 MPT-MC connectivity
Option 1 Option 2
Ethernet CAT5e
MSS4/8
Twin power injector

MSS-1c (Not real colour)
MPT-MC electrical connectivity (up to 100m)

Both injectors include:

Powering of two MPT
Lightning protection
DC protection
LEDs for power output
Power Injector plug-in
Power Injector box

3JK Edition 1.00
1.7.3 MPT-MC connectivity [cont.]
Up to 100m Coaxial cable Up to 350m Coaxial cable

N-N
+lightning +lightning
arrestor arrestor
+ low pass + low pass
filter filter
Ethernet CAT5e + pigtail + pigtail
battery battery
Optical connection
NB: lightning arrestor is same as MXC LC-xx
MPT-HC stand-alone connectivity

Low Pass Filter: Reference: 1AB251350001
Lightning Arrestor: Reference: 3CC50030AAAA

3JK Edition 1.00
1.7.3 MPT-MC connectivity [cont.]
Power +
data
Power Injector plug-in

Power injector box
Both injectors include:

Cable 2x1 mm
Same as MSS-1c powering of two MPT
lightning protection
Battery 1 DC protection
LEDs for power output
Battery 2
MPT-MC stand-alone connectivity (up to 100m)


3JK Edition 1.00
Blank Page


3JK Edition 1.00
2 Traffic Profiles


3JK Edition 1.00
2 Traffic Profiles
2.1 Managed Services and profiles
Association of managed services and profiles:

TDM to TDM This is the typical service associated to a traditional TDM
network in which E1 traffic is transported, switched and terminated inside a
MPR network.
TDM to ETH This is the service allowing the TDM traffic to be aggregated
and output in a single ETH stream. On this service specific algorithms are
applied in order the E1 is transported, switched and provided to an external
ETH network in standard format (MEF-8).
SDH to SDH This is the typical service associated to a traditional SDH
transport network. STM-1 traffic is transparently transported, switched and
terminated inside a MPR network.
ETH to ETH This is not a real CES due to the native IP architecture of MPR.
Ethernet traffic is directly managed by the L2 switch on the Core board,
thanks to the auto-learning algorithm, VLANs etc.
ATM to ATM This profile allows the management of the ATM services inside
a 9500 MPR network. E1s IMA/ATM are terminated/reconstructed at the
borders of the 9500 MPR cloud; encapsulation/extraction of ATM streams
into/from ATM PW packets is performed according to RFC 4717.
ATM to ETH This profile allows the ATM service to be terminated and
encapsulated into an Ethernet stream towards an IP/MPLS Core Network.


3JK Edition 1.00
2.1.1 TDM to TDM flow
Definition: This service identifies a flow inside MPR network, in which

E1 is transported, switched and terminated.
Application: Typical microwave 2G backhauling application, in which

E1s are terminated before entering into aggregation network.


3JK Edition 1.00
2.1.2 TDM to ETH flow
Definition: E1 TDM input signals are packetized according to MEF8 standard;

E1s are transported, switched and provided to an external ETH network in
standard format (MEF-8).
Application:
a) Typical microwave 2G backhauling application, in which E1s are terminated before
entering into aggregation network, where aggregation network is a packet network.
E1s are not terminated at the end of the microwave backhauling and an end-to-end
circuit emulation services could be established between 9500 MPR and the service
router in front of BSC/RNC
b) 9500 MPR without ODU (MSS-8 or MSS-4 stand alone) provides the same level of
feature of a site aggregator box, grooming together different services (in this
particular case E1 TDM) into the common Ethernet layer


3JK Edition 1.00
2.1.3 SDH to SDH flow
Definition: This service identifies a flow inside MPR network, in which

STM-1 is transparently transported, switched and terminated.
Application: Typical microwave transport application.


3JK Edition 1.00
2.1.4 ETH to ETH flow
Definition: Ethernet traffic is transported and switched automatically

by the standard auto-learning algorithm of the built-in MPR 10 Gbit
Ethernet switch.
Application: Typical microwave 3G backhauling/WiMax application, in

which transport of Ethernet packets coming from basestations is
requested.


3JK Edition 1.00
2.1.5 ATM to ATM flow
Definition: 9500 MPR terminates the native IMA/ATM and performs

encapsulation/extraction of those ATM flows into/from ATM PW packets
according to RFC 4717. The 9500MPR facing the aggregation network,
the original ATM flows are re-built on ASAP board.

transport of Ethernet packets coming from 3G base station is
requested.


3JK Edition 1.00
2.1.6 ATM to ETH flow
Definition: 9500 MPR terminates the native IMA/ATM and ATM traffic,
encapsulated in Ethernet frames, is transported into IP/MPLS Core
Network.

transport of Ethernet packets coming from 3G base station is requested.


3JK Edition 1.00
2 Traffic Profiles
2.2 Traffic profiles
Six kinds of traffic profiles have been identified:
TDM2TDM ( 9500MPR 9500MPR, internal TDM )

TDM2Eth ( 9500MPR TDM to Ethernet )
SDH2SDH ( 9500 MPR-E 9500 MPR-E, internal to the MPR network )
ATM2ATM ( 9500MPR 9500MPR, internal ATM )
ATM2Eth ( 9500MPR ATM to Ethernet )
DATA ( Ethernet to Ethernet )

Notes:
TDM2TDM and TDM2ETH profiles are managed in compliancy with Metro Ethernet Forum specifications
MEF 8 - Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet
Networks
- Same behavior than PDH/SDH transmission devices (QoS)
- Reduced impact of the packetization overhead
- Same Radio performances than PDH/SDH devices
ATM2ATM and ATM2ETH profiles are managed in compliancy with the RFC 4717 (IETF ATM PWE3 -
Pseudo Wire Edge to Edge Emulation) standard.

3JK Edition 1.00
2 Traffic Profiles
2.2 Traffic profiles [cont.]
Cases 1, 2, 3

Case 1 for E1
The E1 stream is inserted in Node 1 and extracted in Node 2. In this case the two IWFs used to
packetize the traffic for the Ethernet switch in the Core-E module are both internal to the 9500
MPR-E network. The Circuit Emulation Service is TDM2TDM in Node 1 and Node 2. The Cross
connections to be implemented are PDH-Radio type.
Case 1 for STM-1
The STM-1 stream is inserted in Node 1 and extracted in Node 2. In this case the two IWFs used to
packetize the traffic for the Ethernet switch in the Core-E module are both internal to the 9500
MPR-E network. The Circuit Emulation Service is SDH2SDH in Node 1 and Node 2. The Cross
connections to be implemented are SDH-Radio type.
Case 2
The E1 stream is inserted in Node 1 and extracted in Node 2. One IWF is inside the 9500 MPR-E, but
the second IWF is external to the 9500 MPR-E network. The Circuit Emulation Service is TDM2ETH
in Node 1 and Node 2. The Cross connections to be implemented are PDH-Radio type in Node 1 and
Radio-Eth type in Node 2.
Case 3
The E1 stream is inserted/extracted in Node 1. One IWF is inside the 9500 MPR-E, but the second
IWF is external to the 9500 MPR-E network. The Circuit Emulation Service is TDM2ETH in Node 1
and Node 2. The Cross connections to be implemented are PDH-Eth type in Node 1.

3JK Edition 1.00
2 Traffic Profiles
2.2 Traffic profiles [cont.]
Cases 4, 5

Cases 4 and 5
In these cases Ethernet packets enter Node 1 and are extracted in Node 2. In case 4 the Ethernet
packets encapsulate the E1 stream; in case 5 the packets are native Ethernet packets. None of the
IWFs belongs to the 9500 MPR-E network. The Circuit Emulation Service is ETH2ETH in Node 1 and
Node 2. No Cross connections must be implemented. The path is automatically implemented with
the standard auto-learning algorithm of the 9500 MPR-E Ethernet switch.

3JK Edition 1.00
2 Traffic Profiles
2.3 TDM2TDM
E1 traffic packetized only internally to 9500MPR equipment
RADIO
E1
BTS RADIO
RADIO
PDH
E1
E1
BTS
BSC
E1
BTS

Flow Id present (user defined)

intermediate node configuration (E1 provisioning):
node by node (building Cross-connection tables based on Flow Id)
bandwidth guaranteed (according to QoS Highest Queue Priority association)
no flooding-autolearning necessary

3JK Edition 1.00
2 Traffic Profiles
2.3 TDM2TDM [cont.]
Both the IWFs belong to 9500MPR and the packets are not supposed to
exit the 9500 MPR network.
The IWF parameters listed above, have predetermined values and dont
need to be provisioned.
Mac addresses are determined as consequences of the cross connections.

Payload size is fixed to 121 bytes
ECID will be the same value as Flow Id
TDM clock source: clock recovery differential,
Flow Id provisioned by ECT/NMS

ECID = Emulated Circuit Identifier

IWF = Inter-Working Function

3JK Edition 1.00
2 Traffic Profiles
2.4 TDM2Eth
E1 traffic both internal and external to 9500MPR equipment
E1
BTS
PSN
Eth Eth E1
E1
BTS BSC
E1
BTS


all the parameters must be configured compliant with the MEF8 standard
adaptive or differential clock recovery supported
bandwidth guaranteed (according to QoS Highest Queue Priority association)
destination MAC added before going into whole network (MEF8 compliant)

3JK Edition 1.00
2 Traffic Profiles
2.4 TDM2Eth [cont.]
Only one of the IWFs belongs to 9500MPR and the packets are supposed
to exit the 9500MPR network.
MAC addresses: in all involved nodes are determined as consequences of the

cross connections; the only exception is the Ethernet Terminal Node (the
node where the TDM2ETH traffic goes through an user Ethernet port). In
such ETN the source address is the node Mac address, the destination Mac
address will be provisioned by ECT/NMS.
Payload size: fixed to 256 bytes
ECID : provisioned by ECT/NMS, 2 different values may be used for each
direction
TDM clock source is provisioned by ECT/NMS: clock recovery adaptive, clock
recovery differential
Flow Id is provisioned by ECT/NMS (One Vlan is assigned to each bi-
directional circuit emulated E1 flow)

ECID = Emulated Circuit Identifier

3JK Edition 1.00
2 Traffic Profiles
2.5 SDH2SDH
STM-1 traffic packetized only internally to 9500 MPR-E equipment.
STM-1
STM-1


If there are intermediate nodes in each node build the Cross-connection tables based on Flow Id.
Bandwidth guaranteed (according to QoS Highest Queue Priority association)
No flooding-autolearning necessary
Both the IWFs belong to 9500 MPR-E and the packets are not supposed to exit the 9500 MPR-E network.

3JK Edition 1.00
2 Traffic Profiles
2.5 SDH2SDH [cont.]
Mac addresses are determined as consequences of the cross connections.

Payload size is fixed
Clock source: clock recovery differential/node timing


3JK Edition 1.00
2 Traffic Profiles
2.6 ATM Traffic Management
Three Ethernet CoS are foreseen for ATM PW flows, derived from ATM
Service Category configured for the related VP/VC at ATM layer (by
ATM Traffic Descriptor):
CBR
UBR+ (MDCR > 0)
UBR
By proper mapping of these CoSs to Core Switch and Modem Switch
(refer to Figure 65.), the native ATM QoS can be emulated.
ATM PW flow-based packet queueing is performed inside the ASAP unit,
its Ethernet flow CIR/PIR/MBS/EBS parameters are also derived from
configured ATM TD.
ATM PW flows that have been classified as CBR and UBR+ will be
subjected to admission control and then have guaranteed bandwidth;
the required bandwidth will be derived from Ethernet flow CIR, taking
in account the ATM PW encapsulation and air frame structure.


3JK Edition 1.00
2 Traffic Profiles
2.6 ATM Traffic Management [cont.]
ATM Traffic Management - General block diagram


3JK Edition 1.00
2 Traffic Profiles
2.6 ATM Traffic Management [cont.]
Block diagram for ATM Ingress (ATM -> Packet) direction

In figure is shown a more detailed block diagram of the ASAP unit in Ingress.

3JK Edition 1.00
2 Traffic Profiles
2.7 ETH2ETH
PSN
WiMAX
(NodeB) Eth Eth
Eth
Eth
RNC
PSN
WiMAX Eth
Eth
(NodeB) RNC
WiMAX
(NodeB) Eth
None of the IWFs belongs to 9500MPR.

None of the parameters listed in the previous slide has to be configured
(the 9500 MPR is transparent).

Any packet belonging to an Eth2Eth TDM flow is treated as any other Ethernet packet with the only
exception of giving it an higher priority based on the MEF 8 Ethertype.

3JK Edition 1.00
2 Traffic Profiles
2.8 Ethernet Traffic Management
Ethernet Traffic
The Ethernet traffic is all the traffic entered the MPR network from
user Ethernet ports.
By ECT/NMS it is possible to define the way to manage the Ethernet

traffic according to one of the following options:
802.1D (MAC Address bridge)

802.1Q (Virtual Bridge)


3JK Edition 1.00
2 Traffic Profiles
2.8 Ethernet Traffic Management [cont.]
Bridge type change

In case of change of the bridge type from 802.1Q to 802.1D, the
content of the VLAN table and the VLAN assigned to the user Ethernet
ports, remains stored in the NE MIB.
To change the configuration from 802.1D to 802.1Q, it is necessary to

configure all the Ethernet ports in Admit all mode to avoid hits on
the traffic on that specific port.


3JK Edition 1.00
2 Traffic Profiles
2.8 Ethernet Traffic Management [cont.]
Reserved Multicast Addresses
Reserved Multicast
Function Action
Address
MSS-8/MSS-4: Forward
01-80-C2-00-00-00 Bridge Group Address
MSS-1c: Discard
Flow-Control enabled: Peer
01-80-C2-00-00-01 Clause 31 (MAC Control) of IEEE 802.3
Flow-Control disabled: Discard
Clause 43 (Link Aggregation) and Clause 57 (OAM) of
01-80-C2-00-00-02 Discard
IEEE 802.3
01-80-C2-00-00-03 IEEE 802.1X PAE address Discard
01-80-C2-00-00-04 - 01-
Reserved for future standardization Discard
80-C2-00-00-0D
01-80-C2-00-00-0E IEEE 802.1AB LLDP multicast address Discard
01-80-C2-00-00-0F Reserved for future standardization Discard
01-80-C2-00-00-10 All LANs Bridge Management Group Address Forward
01-80-C2-00-00-11 - 01-
Reserved Forward
80-C2-00-00-1F
01-80-C2-00-00-20 GMRP Address (Clause 10 of IEEE 802.1D) Forward
01-80-C2-00-00-21 GVRP Address (IEEE 802.1Q) Forward
01-80-C2-00-00-22 - 01-
Reserved for GARP Application Forward
80-C2-00-00-2F
01-80-C2-00-00-30 - 01- CCM and LTM Group Destination MAC Addresses (IEEE
Forward
80-C2-00-00-3F 802.1ag)

The table summarizes the actions taken for specific reserved multicast addresses. Frames identified
with these destination addresses are handled uniquely since they are designed for Layer 2 Control
Protocols.
The actions taken by the system can be:
Discard - The system discards all ingress Ethernet frames and must not generate any egress Ether-
net Frame carrying the reserved multicast address.
Forward - The system accepts all ingress Ethernet frames as standard multicast frames and for-
wards them accordingly.
Peer - The system acts as a peer of the connected device in the operation of the relevant Layer 2
Control Protocol.

3JK Edition 1.00
3 Traffic Management (QoS)


3JK Edition 1.00
3.1 Quality Of Services (QoS) in the MPR Node
The QoS function inside MPR is the result of a distributed implementation

on the Core Switch and on the Radio Interface
Embedded
interfaces
Embedded
interfaces
MSS
ETH
ETH
Core Packet Radio Air Block
Scheduler Scheduler
MW
MW ODU
ODU Ethernet
CAC
Ethernet MW
MW ODU
ODU
Peripheral
Peripheral Switch
Switch
Peripheral
Peripheral Peripheral
Peripheral
TDM
TDM
Connection
Admission
Control

9500MPR uses a Connection Admission Control (CAC) for committed services and two schedulers in series (on Core
embedded L2 switch and on Radio peripheral)
The two schedulers need to jointly interoperate to guarantee determistic behavior of the services

3JK Edition 1.00
3.1.1 QoS in the Core-E
Ethernet User ports

(egress) Per egress port QoS
8 queues Scheduler
U1 U2 U3 U4
Queue #8
HPQ+CAC

Queue #7
Slot 3 Slot 3
Slot 4 Slot 4 Queue #6
Classifier
Slot 5 Slot 5
Traffic Queue #5
Slot 6 Slot 6 Classification
(CoS)
Slot 7 Slot 7 Queue #4
802.1p bits DWRR

Slot 8 Slot 8 IPV4 DiffSerf Queue #3
IPV6 Diffserv
VLAN-ID
Ethertype Queue #2
MPLS Exp. bits
U1 U2 U3 U4
Queue #1
Ethernet User ports
(ingress)

The figure shows an overview of the QoS implementation inside the switch.
The Quality of Service feature of the Ethernet switch provides eight internal queues per port to
support eight different traffic priorities. Typically the high-priority traffic experiences less delay
than that low-priority in the switch under congested conditions.
For each egress port according to method of QoS classification configured in the switch, the
packets are assigned to each queue. The higher priority queue Q8 is reserved for TDM flows; the
remaining queues are shared by all Ethernet flows according the classification mechanism
configured by CT/NMS.
For generic Ethernet flows in the switch it is possible by CT/NMS to assign the priority to each
packet according to the information in:
1. IEEE std 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag. If
the tag is present the correspondent priority is assigned to the packet.
802.1P priority Queue
111, 110 Q5 (higher priority)
101 Q4
100 Q3
011, 000 Q2
010, 001 Q1
2. DiffServ: each packet is classified based on DSCP field in the IP header to determine the priority.
DiffServ priority Queue
111000, 110000, 101110, 101000 Q5 (higher priority)
100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000 Q2
001110, 001100, 001010, 001000
000000
All remaining values Q1

3JK Edition 1.00
3.1.1 QoS in the Core-E [cont.]
Core-E Scheduler
The scheduler algorithm cannot be configured.

HQP scheduler algorithm is used on queues Q8, Q7 and Q6.
Deficit Weighted Round Robin (DWRR) is used on the other queues with
the following weights:
QUEUE WEIGHT
Q5 (higher priority) 16
Q4 8
Q3 4
Q2 2
Q1 1


3JK Edition 1.00
3.1.2 Radio Air Block QoS
Switch Radio Interface
The scheduler algorithm implemented inside the Radio Interface is High Queue
Pre-empt: when a packet arrives in the higher priority queue it is immediately
transmitted.
The Radio Air Block QoS is implemented by MPT itself (not in the MSS).
In the figure is shown an overview of the QoS implementation inside the Radio Interface module.
The QoS feature provides eight internal queues to support different traffic priorities. The QoS
function can assign the packet to one of the eight egress transmit queues according to the
information inside the packet as 802.1P field, DiffServ field, Ethertype or 802.1Q VLAN_ID.
QoS based on IEEE std. 802.1p
When 802.1p QoS mechanism is adopted, the reference is the standard IEEE 802.1D-2004 Annex G
User priorities and traffic classes that defines 7 traffic types and the corresponding user priority
values.
Considering that in the Radio Interface module for generic Ethernet traffic there are five egress
queues the mapping 802.1p value to queue is the following:
802.1p priority Queue

101 Q4
100 Q3
011, 000 Q2
010, 001 Q1
QoS based on DiffServ

100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000
001010, 001100, 001010, 001000, 000000 Q2

3JK Edition 1.00
3.1.2 Radio Air Block QoS [cont.]
Radio Air Block Scheduler
HQP scheduler algorithm will be used on Q8, Q7 and Q6.

Deficit Weighted Round Robin (DWRR) algorithm will be used for the
other five queues.
By default, the DWRR algorithm is used with the following weights:
Queue Weight
Q4 8
Q3 4
Q2 2
Q1 1


3JK Edition 1.00
3.1.3 How 9500 MPR manage QoS
L2 switch on Core unit
Eight Queues per Output Port

Scheduler
Service type MPR QoS
type
Classification TDM
#8
Voice -> MACDA+VLAN VoIP
ATM PWE3 -> MACDA+VLAN TDM2ETH
ATM CBR, VBRrt HPQ #7
TMN -> VLAN
ETHERNET TMN #6
No priority -> all queue #1 ATM VBRnrt, UBR+

#5
1p ETHERNET
DiffServ ETHERNET #4
ETHERNET DWRR #3
Ethernet based frame
ETHERNET #2
ATM UBR
#1
ETHERNET


3JK Edition 1.00
3.1.3 How 9500 MPR manage QoS [cont.]
Modem unit (Radio side)

Eight Queues per Radio Direction
Scheduler
Service type MPR QoS
type
Classification TDM
#8
Voice -> MACDA+VLAN VoIP
ATM PWE3 -> MACDA+VLAN TDM2ETH

ATM CBR, VBRrt HPQ #7
TMN -> VLAN
ETHERNET TMN #6
No priority -> all queue #1
ATM VBRnrt, UBR+
1p ETHERNET
#5
DiffServ
Open platform ready for additional services ETHERNET #4
ETHERNET DWRR #3
Air block base entities
Fragmentation ETHERNET #2
Fair scheduling (Jumbo) ATM UBR

#1
ETHERNET


3JK Edition 1.00
Section 1 Module 2 Page 58 58
3.1.4 Flows classification
For Radio Air Block QoS:
All TMN traffic flows are assigned to the Q6 egress priority queue.
For both Core-E QoS and Radio Air Block QoS:
All the TDM2TDM traffic flows will be assigned to the highest egress
priority queue (Q8).
All the TDM2ETH traffic flows will be assigned to the Q7 egress priority
queue.
All the MEF-8 ETH2ETH traffic flows will be assigned to the Q5 egress
priority queue.


3JK Edition 1.00
3.1.4 Flows classification [cont.]
For generic Ethernet flows in the switch and the modem it is possible by
CT/NMS to assign the priority to each packet according to the information in:
IEEE 802.1p: the packet is examined for the presence of a valid 802.1P user-
priority tag. If the tag is present the correspondent priority is assigned to the
packet. 802.1P priority Queue
101 Q4
100 Q3
011, 000 Q2
010, 001 Q1
DiffServ: each packet is classified based on DSCP field in the IP header to

determine the priority.
100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000 Q2
001110, 001100, 001010, 001000
000000

When 802.1p QoS mechanism is adopted,

the reference is the standard IEEE 802.1D-2004 Annex G User priorities and traffic classes that
defines 7 traffic types and the corresponding user priority values.

3JK Edition 1.00
ATM PW flows will be assigned to Ethernet switch and modem egress

priority queues according to their CoS , as below reported:
ATM PW CoS Switch Egress Queue

Guaranteed (CBR) Q7 (higher priority)
Best Effort (UBR+) Q6
BackGround (UBR) Q1


3JK Edition 1.00
Jumbo frames:
While there is no physical limitation to the number of ports that can

receive jumbo frame,
if more jumbo flows are transmitted toward the same port into two
different queues the QoS could work in wrong way.
It is recommended to forward jumbo frame only in the queue Q1 (lower

priority).


3JK Edition 1.00
3.2 Quality Of Services (QoS) in the MPR Terminal
The QoS function inside MPR is the result of a distributed implementation

on the MSS-1c Switch and on the MPT
Embedded
interfaces
Embedded
interfaces
MSS-1c
ETH
ETH
Core Packet Radio Air Block
Scheduler Scheduler
Ethernet
CAC
Ethernet Radio
Radio
Switch
Switch Interface
Interface
Interfaces
Interfaces
TDM
TDM
Connection
Admission MPT
Control

9500MPR uses a Connection Admission Control (CAC) for committed services and two schedulers in series (on MSS-1c
embedded L2 switch and on MPT)
The two schedulers need to jointly interoperate to guarantee determistic behavior of the services

3JK Edition 1.00
3.2.1 QoS in the MSS-1c
Per egress port QoS

4 queues Scheduler
U1 U2 U3 U4
HPQ+CAC

Queue #4
Classifier
10E1
Traffic Queue #3
Classification
(CoS)
802.1p bits DWRR

IPV4 DiffSerf Queue #2
IPV6 Diffserv
VLAN-ID
Ethertype
MPLS Exp. bits
TMN1 TMN2 CT
Queue #1

The figure shows an overview of the QoS implementation inside the switch.
The Quality of Service feature of the Ethernet switch provides four internal queues per port to
support four different traffic priorities. Typically the high-priority traffic experiences less delay
than that low-priority in the switch under congested conditions.
For each egress port according to method of QoS classification configured in the switch, the
packets are assigned to each queue. The higher priority queue Q4 is reserved for TDM flows; the
remaining queues are shared by all Ethernet flows according the classification mechanism
configured by CT/NMS.
For generic Ethernet flows in the switch it is possible by CT/NMS to assign the priority to each
packet according to the information in:
1. IEEE std 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag. If
the tag is present the correspondent priority is assigned to the packet.
101 Q4
100 Q3
011, 000 Q2
010, 001 Q1
2. DiffServ: each packet is classified based on DSCP field in the IP header to determine the priority.
100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000 Q2
001110, 001100, 001010, 001000
000000

3JK Edition 1.00
3.2.1 QoS in the MSS-1c [cont.]
MSS-1c Scheduler
The scheduler algorithm cannot be configured.

HQP scheduler algorithm is used on queues Q4.
Deficit Weighted Round Robin (DWRR) is used on the other queues with
the following weights:
QUEUE WEIGHT
Q2 2
Q1 1


3JK Edition 1.00
3.2.2 Flows classification
All the TDM traffic flows will be assigned to the highest egress priority queue
(Q4)
For generic Ethernet flows in the switch it is possible by CT/NMS to assign the
priority to each packet according to the information in:
packet.
101, 100 Q2
011, 010, 001, 000 Q1
DiffServ: each packet is classified based on DSCP field in the IP header to

determine the priority.
100110, 100100, 100010, 100000 Q2
011110, 011100, 011010, 011000

When 802.1p QoS mechanism is adopted,

the reference is the standard IEEE 802.1D-2004 Annex G User priorities and traffic classes that
defines 7 traffic types and the corresponding user priority values.

3JK Edition 1.00
Jumbo frames:
While there is no physical limitation to the number of ports that can

receive jumbo frame,
if more jumbo flows are transmitted toward the same port into two
different queues the QoS could work in wrong way.
It is recommended to forward jumbo frame only in the queue Q1 (lower

priority).


3JK Edition 1.00
3.3 Quality Of Services (QoS) in the MPT
The Radio QoS is implemented by
MPT itself (not in the MPT Access unit and not inside the MSS-1c).
The set of MPT Radio QoS features is the same of the one specified for
the Modem unit with the exception of:
the ATM CBR and UBR+ CoS:

in MPT they are sent to queue #5 and queue #4 respectively
(and not to queue #7 and queue #6).


3JK Edition 1.00
3.3.1 Radio Air Block QoS for MPR Node
Switch MPT
The scheduler algorithm implemented inside the MPT is High Queue Pre-empt:
when a packet arrives in the higher priority queue it is immediately
transmitted.
In the figure is shown an overview of the QoS implementation inside the MPT.
values.
Considering that in the MPT for generic Ethernet traffic there are five egress queues the mapping
802.1p value to queue is the following:

101 Q4
100 Q3
011, 000 Q2
010, 001 Q1

100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000
001010, 001100, 001010, 001000, 000000 Q2

3JK Edition 1.00
3.3.2 Radio Air Block QoS for MPR Terminal
transmitted.
In the figure is shown an overview of the QoS implementation inside the MPT.
values.

101 Q4
100 Q3
011, 000 Q2
010, 001 Q1

100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000
001010, 001100, 001010, 001000, 000000 Q2

3JK Edition 1.00
3.3.3 Radio Air Block QoS Scheduler

Deficit Weighted Round Robin (DWRR) algorithm will be used for the
other five queues.
Queue Weight
Q4 8
Q3 4
Q2 2
Q1 1


3JK Edition 1.00
3.4 Quality Of Services (QoS) in the MPR-e
transmitted.

In the figure is shown an overview of the QoS implementation inside the MPR-e.
values.

101 Q4
100 Q3
011, 000 Q2
010, 001 Q1

100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000
001010, 001100, 001010, 001000, 000000 Q2

3JK Edition 1.00
3.4 Quality Of Services (QoS) in the MPR-e [cont.]

For the other 5 queues can be selected, by the MCT, the HQP mode or
the DWRR (Deficit Weighted Round Robin) mode.
If the DWRR has been selected, the weight to be assigned to each
queue can be configured by the MCT.
Queue Weight
Q4 8
Q3 4
Q2 2
Q1 1


3JK Edition 1.00
Blank Page


3JK Edition 1.00
4 LAG (Link Aggregation Group)


3JK Edition 1.00
4 LAG (Link Aggregation Group)
4.1 LAG overview
Link Aggregation groups a set of ports so that two network nodes can be
interconnected using multiple links to increase link capacity and
availability between them.
When aggregated, two or more physical links operate as a single logical
link with a traffic capacity that is the sum of the individual link
capacities.
This doubling, tripling or quadrupling of capacity is relevant where
more capacity is required than can be provided on one physical link.
Link aggregation also provides redundancy between the aggregated
links. If a link fails, its traffic is redirected onto the remaining link, or
links.
If the remaining link or links do not have the capacity needed to avoid a
traffic bottleneck, appropriate QoS settings are used to prioritize
traffic so that all high priority traffic continues to get through.
The Link Aggregation is performed according to 802.3ad and can be
applied to Radio ports and to User Ethernet ports.


3JK Edition 1.00
4.1 LAG overview
4.1.1 Link aggregation on Radio ports (Radio LAG)
Link aggregation can be applied to radio ports (in this case it is named
Radio Link Aggregation).

In this example, user traffic is split up into radio channels. Main advantages:
Throughput. The overall radio Ethernet throughput is more than 1 Gbit/sec (2 x 530 Mbit/s, being
this the value for 256QAM@56 MHz)
Protection. In case of a failure of one of the three channels, all the traffic is redirected on the
remaining link (with a throughput of around 0.5 Gbit/sec). The discarded or dropped traffic is the
one with lower priority: high priority traffic is still running on the remaining active channels.

3JK Edition 1.00
4.1 LAG overview
4.1.1 Link aggregation on Radio ports (Radio LAG) [cont.]

One MPT per MPT plug-in.

3JK Edition 1.00
4.1 LAG overview
4.1.2 Link aggregation on User Ethernet ports (Ethernet LAG)
Link aggregation can be applied to Ethernet user ports (electrical or

optical ) on the same Core-E unit.
The LACP protocol is supported.

Note 1: the Ethernet ports involved in a LAG cannot be used as TMN In-band interface.

3JK Edition 1.00
Blank Page


3JK Edition 1.00
5 Synchronisation


3JK Edition 1.00
5 Synchronisation
5.1 Synchronisation
Synch delivery Packet microwave Synch source

Access type options nodal configuration options
Line clock Line clock E1/T1

Mobile (ACR/DCR, NTP)* E1/T1
2G,3G,4G
9500 MPR
SvncE Eth SyncE
Eth
Synch in/out 9500 MPR Synch in/out 2 MHz

Private 2 MHz
ports ports 5 MHz
Business
5 MHz (external source)
(external source) 10 MHz
Office 10MHz
9500 MPR
9500 MPR
Time delivery Time source
options options
Fixed
DSL
Transparent Transparent
1588v2 1588v2
transport of transport of
Phone TOD TOD
protocol protocol
*Adaptive and differential clock

recovery, node timing protocol
MSS-8 and MSS-4
Synchronisation transferred through radio carrier at physical layer
Given Sync Source, 9500 MPR can deliver synchronization at the far end under any format
Any Sync IN, any Sync OUT


3JK Edition 1.00
5 Synchronisation
5.1 Synchronisation [cont.]
Synchronization Status Messages and Quality Level Determination

Compliant to G.8264
SSM can be applied to Ethernet user port or to radios
When SSM are applied to radios, the radio direction with best synchronization
quality is selected.
9500MPR inserted in a ring delivers the synchronizations taken from the best
of West or East radio
Determine and select the Quality Level 9500MPR synchro delivery:
1. synchE
highest quality source Quality 2. E1/DS1
Radio 1
Level (QL) Reference 3. 2/5/10 MHz
selector
Quality
Radio 2 Level (QL)
MSS-8 and MSS-4

9500MPR can be positioned inside a microwave ring (where traffic
management is done by an external gear).

Note: With MSS-1c and with MPR-e the SSM are transparency forwarded in most of the configurations.

3JK Edition 1.00
5 Synchronisation


2G,3G,4G
9500 MPR
SvncE Eth SyncE
Eth
9500 MPR
Private
Business
Office
9500 MPR
9500 MPR
options options
Fixed
DSL
1588v 1588v2
Phone 2 TOD TOD
protocol protocol

MSS-1c


3JK Edition 1.00
5 Synchronisation

Mobile
2G,3G,4G
9500 MPR
SvncE Eth SyncE
Eth
9500 MPR
Private
Business
Office
9500 MPR
9500 MPR
options options
Fixed
DSL
1588v 1588v2
Phone 2 TOD TOD
protocol protocol

MPR-e


3JK Edition 1.00
5 Synchronisation
Network Synchronisation in Mobile Backhauling

On the radio channel, a 9500 MPR transfers the reference clock to an adjacent MPR device through the
radio carrier frequency at physical layer.
This method offers two main advantages:
No bandwith is consumed for the synchronisation distribution,
Total immunity to the network load.
End-to-end scenarios where time-of-day/phase alignment are requested are fully supported, as 1588
PTP v2 is carried transparently by MPR across the microwave backhauling network.
Both for Hybrid and Packet working modes, the Clock can be received at hand-off or delivered at the
cell site. Synch-Eth, E1, PDH and BITS clock modes are available.

3JK Edition 1.00
5 Synchronisation
Network Clock Available
Differential Clock Recovery

The availability of the Clock in the Network represents the most common scenario, characterized by a
time source available at the ingress of the microwave backhauling network, derived from the
primary reference clock.
Synchronization (frequency) is delivered to the cell site using any of the options available on MPR,
depending on the operators need. Worth repeating ingress and egress methods can be mixed (i.e.
Synch-Eth at the ingress, E1/T1 at the egress) via a simple configuration.

3JK Edition 1.00
5 Synchronisation
5.2 Clock Source Selection and Distribution

9500 MPR has an embedded reference clock which is distributed to each board of the network
element.
Such clock is generated in the Clock Reference Unit (CRU) of the core unit (controller).

3JK Edition 1.00
5 Synchronisation
5.3 Differential/Adaptative clock recovery
TDM data flow is fragmented and the fragments are transmitted over a
Packet Switched Network (PSN);
The received fragments need to be reassembled in the original TDM
data flow at the original bit rate
Three main methods can be used to recover at the RX site, the original
bit rate:
Differential clock recovery (DCR): recalculation of the original clock based
of the Delta respect to a reference clock that is available at both Tx and Rx
site. This method can be selected for each E1 stream
Adaptive clock recovery (ACR): based on the average rate at which the
packets (fragments) arrive at RX site. This method can be selected for each
E1 stream
Node Timing: timing from the network clock as defined in G.8261. The
enabling of the Node Timing is applied to all E1s of the PDH unit.

Differential: used in case of clock distribution on the whole network. Its more reliable than
Adaptive; also used in TDM2TDM traffic (MPR to MPR).
Adaptive: simpler network, but performances depends on the PDV (Packet Delay Variation) in the
Network. Always used when the reference clock isnt distributed on the whole network.
Node Timing: this feature (called either network clock re-timing or node timing or, according to
G. 8261 wording, network-synchronous operation for service clock) introduces an additional
possibility to recover E1 clock.
Node timing is a way to recover TDM clock quite popular in the industry of service routers and site
aggregator boxes. This feature inside the 9500 MPR platform is adding interworking capabilities with
third parties service routers and circuit emulations gateway.
In node-timing working mode, all the E1s are re-sampled with the network element clock. This
means that, as also reported in G8261, this method does not preserve the service timing (E1 clock).
Recovered E1 clock is according to G. 823 synchronization masks.

3JK Edition 1.00
5 Synchronisation
5.3 Differential/Adaptative clock recovery [cont.]
The available clock recovery techniques with TDM2TDM profile are:

DCR: differential clock recovery
Node timing
The available clock recovery techniques with TDM2ETH profile are:
ACR: adaptive clock recovery (if a common reference clock is not available)
DCR: differential clock recovery
Node timing

Note: in meshed networks (rings) do not close the synchronisation configuration.
N.B.: If the NODE TIMING is enabled, the CT still propose the possible selection between ACR and DCR:
in this specific case, the meaning of this option is not related to the clock recovery algorithms but
rather to the MRF8 frame format.

3JK Edition 1.00
5 Synchronisation
5.3 Differential/Adaptative clock recovery [cont.]
End End
System1 IWF
PSN
PSN IWF System2
Differential clock recovery
End End
System1 IWF
PSN
PSN
IWF System2
Adaptative clock recovery

Differential clock recovery

Common reference clock IS available at both Ends.
IWF system, at RX side, generate output clock based on RTP TimeStamps which are sent together
with each Fragments.
Adaptative clock recovery

Common reference clock is NOT available at both Ends.
IWF system, at RX side, generate output clock based on data arrival rate: TDM clock is slowly
adjusted to maintain the average fill level of a jitter buffer at its midpoint.

3JK Edition 1.00
5 Synchronisation
5.4 Synchronisation Interface
Each Network Element must have a reference clock (NEC), which will
be distributed to each circuit of the NE. Such clock is a 25 MHz
generated in the Clock Reference Unit (CRU) function.
The NEC is locked to a Synchronization Source.
Both for all MSS and MPR-e, the sources can be:
1. Free Run Local Oscillator.
2. Any E1 available at input traffic interfaces (the specific E1 port has to be

chosen). No E1 coming from the ASAP card can be used as Synch source.


3JK Edition 1.00
5 Synchronisation
5.5 Synchronisation Interface
3. SynchrE: Any Synchronous Ethernet clock source available at enabled User

Ethernet traffic interfaces (both electrical and optical) configured in
synchronous operation mode (the specific User Ethernet port has to be
chosen).
From ITU-T G.8264 point of view, the MSS is a Synchronous Ethernet equipment
equipped with a system clock (NEC) following the ITU-T G.8262 recommendation.
A User Ethernet interface configured in synchronous operation mode can work only
at 1Gigabit/s.
In the particular case of electrical User Ethernet interfaces, these interfaces
perform link auto negotiation to determine the master and slave clocks for the link.
The clock slave role must be configured as part of auto negotiation parameters in
order to use the interface as Synchronous Ethernet clock source.
N.B.: SSM is not supported, therefore MPR cannot be included in a Synch-E ring.
4. The Symbol Rate of the Rx signal of any available Radio direction (the
specific Radio Port has to be chosen).


3JK Edition 1.00
5 Synchronisation
5.5 Synchronisation Interface [cont.]
For only MSS-8 and MSS-4
The NEC also provides a Sync Out port on the Core-E Module.
The other sources can be:
5. A specific synchronization signal available from the dedicated Sync-In port,

which can be configured according to the following options:
2.048 MHz, electrical levels according G.703, clause 13
5 MHz, + 6 dBm 50 ohm, sine-wave
10 MHz, + 6 dBm 50 ohm, sine-wave
1.024 MHz, electrical levels according to G.703, clause 13 with the following
exceptions:
timing properly scaled from 2.048 MHz to 1.024 MHz.


3JK Edition 1.00
5 Synchronisation
Some rules have to be followed while configuring the Primary and

Secondary clock sources.
All the NEC has to be configured as Master or Slave.
Only one Master is allowed in the network.
If Master,
The Restoration Mode can be Revertive and Not Revertive
The Primary sources must be chosen among 1), 2), 3) or 5).
If the selected Master Primary Source is 1)
then the Master Secondary Source doesn't need to be selected because the Primary is never
supposed to fail.
If the selected Master Primary Source is 2), 3) or 5)
then Master Secondary Source must be selected among 1), 2), 3) or 5).
If Slave,
The Restoration Mode is fixed to Revertive.
The Primary Source must chosen between 3), 4) or 5)
Slave primary sources is allowed to be 3) or 5)
The Secondary Source can be chosen among 1), 2), 3) or 5).

Each Module will mute its own Synchronization clock in case of Fail Alarm.
For each available sync source, the CRU detects the signal Degrade Alarm on each available sync
source. Such Signal Degrade alarm raises also in case of muted (missing) clock.
The Signal Degrade Alarm relevant to the selected Synchronization Source, or the relevant Card Fail,
causes the switching of the Synchronization Source.

3JK Edition 1.00
5 Synchronisation
Synchronization for E1 ports with ASAP unit
The synchronization of each E1 ATM port in the ASAP unit can be

configured (by the Craft Terminal) in two ways:
Loop-timed: the transmit clock is derived from the E1 clock source received
Node-timed: the transmit clock is the NE clock
The E1 ports belonging to the same IMA group must have the same
configuration.


3JK Edition 1.00
5 Synchronisation
5.6 Synchronisation Interface in MPR-e
Only for MPT in stand-alone
The MPT can be configured to be synchronized in two different modes:
SynchE (Synchronous Ethernet).

With this mode for the electrical interface the selection among
Autonegotiation/Master/Slave must be performed.
PCR (Proprietary Clock Recovery): the time stamp inside the Ethernet
frame is used.
With this mode the Source MAC address and the Destination MAC address
must be assigned.


3JK Edition 1.00
6 Cross-connections


3JK Edition 1.00
6 Cross-connections
6.1 Cross-connection CORE-E
Making any-service cross connections is as simple as drawing a row
By TCO or by NM
The cross-connections between slots and between slot and Ethernet user ports are realized with a
Layer-2 Ethernet Switch inside the Main Core-E.
The decision made by the switch to forward the received packet is based on the destination MAC
address.

3JK Edition 1.00
6 Cross-connections
6.1 Cross-connection [cont.] MSS-1c
Making any-service cross connections is as simple as drawing a row
STM-1 Service
E1 Service
TDM2ETH Ethernet
MEF8 Service
Service
By TCO or by NM
The cross-connections are realized with a Layer-2 Ethernet Switch inside the MSS-1c.
The decision made by the switch to forward the received packet is based on the destination MAC
address

3JK Edition 1.00
6 Cross-connections
6.2 E1 Cross-connection
E1 Cross-connection
Each E1 can be cross connected independently
E1 can be cross connected to any of the following interfaces:

Radio interface
Ethernet interface
Each E1 (board #, port #) must be associated to a signal flow ID


3JK Edition 1.00
6 Cross-connections
6.3 STM-1 Cross-connections
STM-1 Cross-connection
Each STM-1 can be cross connected independently
STM-1 can be cross connected to the following interface:

Radio interface
Each STM-1 (board #, port #) must be associated to an unique signal flow ID


3JK Edition 1.00
6 Cross-connections
6.4 Radio-Radio Cross-connection
Radio-Radio Cross-connection
Ethernet frames, coming from a radio direction, can be cross-

connected to another radio direction.


3JK Edition 1.00
6 Cross-connections
6.5 Ethernet Cross-connection
Ethernet Cross-connection
Generic Ethernet flows

All flows different from the TDM2TDM and TDM2ETH ones are managed
as the standard Ethernet packets: if the 802.1Q is enabled the related
management is performed looking the VLAN and then, according to the
destination address, each packet is switched to the correct port: radio,
user Ethernet or E1/DS1. If the 802.1Q is not enabled only the
destination address is considered.
For each radio interface, the bandwidth assigned, globally, to the
Ethernet traffic is the consequence, with a given radio capacity, of the
number of E1/DS1 cross-connected on that radio interface. Hence the
available bandwidth for Ethernet flows will be the configured radio
bandwidth decreased by bandwidth used by each TDM2TDM and
TDM2ETH.


3JK Edition 1.00
6 Cross-connections
6.6 ATM PW Cross-connection
ATM PW Cross-connection
Cross-connection of ATM PW flows involves the following levels of

operation:
an ATM PW is composed of two unidirectional flows, so its cross-connection is
internally managed by NE as two unidirectional flow cross-connections
for ATM PW flow with guaranteed bandwidth, an admission control check
must be performed in each flow direction: there shall be enough available
bandwidth on both directions
VLAN-based settings in terms of Ethernet switch and Radio QoS are then
performed (as the same VLAN can be used for ATM PW flows with same CoS
and path).
The minimum bandwidth foreseen for an ATM PW flow corresponds to the
case of PCR, SCR or MDCR of 1 cell/s rate, with max 1 cell for frame.


3JK Edition 1.00
6 Cross-connections
6.7 ATM Light Cross-connection Provisioning
ATM Light Cross-connection Provisioning
In this release when a cross-connection toward a radio direction with

MPT is involved, the related provisioning is performed in almost the
same way as with ODU300, with the following main differences:
MAC DA is also explicitly provisioned in the NE acting as TPE role
admission control, in terms of checking bandwidth required bt ATM PW flow

against the available bandwidth on radio interface, is never performed


3JK Edition 1.00
6 Cross-connections
6.8 MAC SA of ATM PW Generated by ASAP Unit
MAC SA of ATM PW generated by ASAP unit
MAC Source Address of ATM PW frames generated by ASAP peripheral

should be assigned to be equal to:
the internal MAC Address of slot hosting that ASAP peripheral in case of cross-
connection towards radio interface
the NE Mac Address in case of cross-connection towards Ethernet interface.
In this release it is accepted to assign always the NE Mac Address as

MAC Source Address of ATM PW frames generated by ASAP peripheral.


3JK Edition 1.00
Blank Page


3JK Edition 1.00
7 Protections with ODU300


3JK Edition 1.00
7.1 Protections with ODU300
Supported Protection types :
1) RPS (Radio Protection Switching) Hitless for each radio direction (RPS-RX)
RPS is distributed in 9500 MSS modules before termination of 9500 MSS frame.
2) EPS (Equipment Protection Switching) for each module type

Both Working and Spare modules send its own signal to the Core-E.
Core-E selects the best signal.
3) HSB-TPS (Hot StandBy - Transmission Protection Switch)

Spare ODU module is squelched.


3JK Edition 1.00
7.1 Protections with ODU300 [cont.]
2 3
2 1

Legend:
1 RPS
2 EPS
3 HSB

3JK Edition 1.00
7.1 Protections with ODU300 [cont.]
2
2
Legend:
2 EPS

3JK Edition 1.00
7.2 RPS Switching Criteria
The switching criteria are:
SF (Signal Fail): generated from transmission and equipment alarms affecting the Rx
radio section:
Rx Fail
Demodulator Fail
IDU-ODU cable loss
LOF of aggregate signal radio side
Main and spare ODU, IDU HW failures (card fail)
HBER (high BER)
EW (Early Warning)


3JK Edition 1.00
7.3 EPS Switching Criteria
Peripheral Card Fail (switching off of the peripheral included)

Peripheral Card Missing
LOS of all the tributaries (of course only in case of PDH local access peripheral
protection) managed via SW.


3JK Edition 1.00
7.4 HSB Switching Criteria
The switching criteria are :
Radio Interface Peripheral Card Fail (switching off of the peripheral included)
Radio Interface Peripheral Card Missing
MSS-ODU cable loss
ODU TX chain alarm (this is an OR of the following alarms: LOS at ODU input,
modFail, txFail, ODU card fail)


3JK Edition 1.00
Blank Page


3JK Edition 1.00
8 Protections with MPT-HC/MPT-HC V2


3JK Edition 1.00
8.1 Protections with MPT-HC/MPT-HC V2
To implement the 1+1 configuration an optical cable must be connected

from one MPT-HC/MPT-HC V2 to the second MPT-HC/MPT-HC V2. In the
figure Ethernet port 2 of one MPT-HC/MPT-HC V2 is connected to
Ethernet port 2 of the second MPT-HC/MPT-HC V2.
Supported Protection types:
1) RPS (Radio Protection Switching) Hitless for each radio direction

RPS is implemented directly on the two MPT-HC/MPT-HC V2.
2) EPS (Equipment Protection Switching) for the MPT-HC/MPT-HC V2

EPS protects the MPT-HC/MPT-HC V2 and the cables connecting it to the MSS.



3JK Edition 1.00
8.1 Protections with MPT-HC/MPT-HC V2 [cont.]
2 2 3
Legend:
1 RPS
2 EPS
3 HSB
2 2 1


3JK Edition 1.00
8.1 Protections with MPT-HC/MPT-HC V2 [cont.]


3JK Edition 1.00
8.2 RPS Switching Criteria
SF (Signal Fail): generated from transmission and equipment alarms affecting

the Rx radio section
Rx Fail
Demodulator Fail
LOF of aggregate signal radio side
inter-MPT coupling link failure
HBER (high BER) based on the demodulated erroneous blocks ratio
EW (Early Warning) based on MSE

Moreover, MPT-HC supports a further embedded functionality called "Enhanced RPS". Enhanced RPS
is a frame-based protection mechanism, aimed to reach a quick reaction time and increasing
significantly the quality of the radio interface in the Rx side. It assumes the alignment between the 2
received radio channels and it is based on frame by frame selection of the "best" frame between the
frames received from the Main and the Spare radio channel. The Enhanced RPS assumes that the
"classical" RPS criteria are used to give indication about the "preferred" channel, whose frame has to
be selected, when the frame-based choice between the 2 streams is not possible (e.g. due to the
frame alignment error). The Enhanced RPS switching criterion depends on the presence of errors in
the decoded LDPC word.

3JK Edition 1.00
MPT Access Card Fail status

IDU-ODU Connection Failure
ICP alarm
Mated MPT Access card Failure


3JK Edition 1.00

ICP alarm
Incompatible Shifter alarm
Incompatible Frequency alarm
Incompatible Power alarm
Incompatible Modulation Parameters alarm
Inter-MPT coupling link failure. Where there is a cross configuration (EPS on
Spare & TPS on main), HSB (TPS) will switch and align with EPS position, if
there is an inter-MPT coupling link failure.


3JK Edition 1.00
Blank Page


3JK Edition 1.00
9 Protection with MPT-MC


3JK Edition 1.00
9.1 Protection with MPT-MC
Supported Protection types:
1) EPS (Equipment Protection Switching) for the MPT-MC

EPS protects the MPT-MC and the cables connecting it to the MSS.



3JK Edition 1.00
9.1 Protection with MPT-MC [cont.]

Note: Since there is no coupling link in the current release the TPS Operator Commands are not
supported.
Only Operator Commands for EPS are supported.

3JK Edition 1.00

ICP alarm


3JK Edition 1.00

ICP alarm
Incompatible Shifter alarm
Incompatible Frequency alarm
Incompatible Power alarm
Incompatible Modulation Parameters alarm


3JK Edition 1.00
Blank Page


3JK Edition 1.00
10 Core-E protection


3JK Edition 1.00
10.1 Core-E protection
The logic of this protection is distributed in each access and radio

peripheral unit. All the switching criteria coming from both the Core
units, are available (via backpanel) to each peripheral in order to allow
to each logic to take the same decision.
Both the Cores (main and spare) send their signals to all the traffic
peripherals.
Core protection supports two different types of protection:
Traffic/services protection (protection of all the transport functions with the
exception of the control platform)
Control Platform protection
In order to provide this protection the Flash Cards on the two Core
boards are kept aligned (in terms of SW and configuration data) both in
case of new operations done by the management systems and in case of
Flash Card replacement.


3JK Edition 1.00
10.1 Core-E protection [cont.]
User Ethernet interfaces protection

In order to support User Ethernet interfaces protection using an
external device, the User Ethernet ports of the Core in standby status
are switched off.
The switch on of the User Ethernet interfaces when the Core in standby
status becomes active, due to operator commands or automatic switch,
is done within 5 seconds. In case of Optical Ethernet interface, the
Lambda, Link Length, Connector and Gigabit Ethernet Compliance Code
information are read from the active Core.


3JK Edition 1.00
TMN Local Ethernet interface protection

In order to support TMN Local Ethernet interface protection using an
external device, the relevant Ethernet port of the Core in standby
status is switched off.
The switch on of the TMN Local Ethernet interface when the Core in
standby status becomes active, due to operator commands or
automatic switch, is done within 5 seconds.
In order to avoid impact on the Core, the external device used for the
TMN Local Ethernet interface protection is kept separate from the one
used for protection of User Ethernet interface. External synchronization
interface protection


3JK Edition 1.00
External synchronization interface protection

The Protection of the external synchronization interface is supported.
The output port on the stand-by Core is muted.
Node-Timed PDH interface protection

In case of node-timed PDH interface the protection of the NE Clock
provided by Core is supported.
Core protection restoration mode

The restoration mode is always revertive: the Core main becomes
active as soon as it has recovered from failure or when a switch
command is released.


3JK Edition 1.00
10.2 Core-E protection Switching Criteria

Core Card Fail
Core Card Missing
Control Platform operational status failure
Flash Card realignment in progress
Flash Card failure
If the Ethernet LOS Criteria feature has been enabled the following
additional switching criteria are added:
Card Fail of SFP optical module
Card Missing of SFP optical module
LOS of any Electrical User Ethernet interfaces, including the LOS of the forth
User Ethernet interface working as TMN Local Ethernet interface.

Note: In case of stand-by Flash Card realignment in progress, the application SW refuses/removes a
manual switch command.

3JK Edition 1.00
Blank Page


3JK Edition 1.00
End of Module
Architecture


3JK Edition 1.00
13
Section 1
Product Overview
Module 3
Management System
3JK Issue 1.00
9500 MPR

3JK Issue 1.00
Blank Page

Product Overview Management System
Document History

Marcoussis
02 2011-02-01 ALU University Second edition

Vimercate

3JK Issue 1.00
Module Objectives
describe the Management System of the 9500 MPR.


3JK Issue 1.00


3JK Issue 1.00
Table of Contents
Page
1 Management System 7
1.1 Network Management 8
Blank Page 10
2 MPR Management 11
2.1 9500 MPR Management 12
2.2 MPR IP addresses 13
2.3 TMN communication channels 15
2.4 TMN interfaces (9500 MPR Node) 16
2.5 LCT Connection 17
2.6 MPR Capability IP Parameters 18
Answer the Questions 21
Annexe: Example of MPR IP Addresses 22
End of Module 23


3JK Issue 1.00

9500 MPR 9500MPR R 3.0 Operation and Maintenance This page is left blank intentionally

3JK Issue 1.00
1 Management System


3JK Issue 1.00
1 Management System
1.1 Network Management
All Access and Transport Multi-protocol management

Integrated in a single
SNMP
Network Management Suite
Q3
1350 OMS QB3*
Access & Transport TL1

Network Management
9400 AWY New 1642EM

9500 MPR 1662SMC
1650SMC
9600 USY 1850TSS
9600 LSY 9500 MXC
1350 Open Management Suite

Providing a single managed network reduce the operational expenditure of a network directly
improving the margin in the P&L of an Operator.
Alcatel-Lucent offers a unified management system capable to manage the entire access and
transport network under a single Network Management Suite: the 1350 OMS.
9500 MPR together with all other Microwave and Optical transmission Network Element is fully
integrated into 1350 OMS Network Management System providing all the tools required to operate
the network.
9500 MPR can also be managed by Alcatel-Lucent 5620 SAM.

3JK Issue 1.00
1 Management System
1.1 Network Management [cont.]
1350 OMS
TMN Platforms (common remote management evolution)

9500 MPR can be managed:

by Alcatel-Lucent 1350 OMS Network Management System,
by Alcatel-Lucent 5620 SAM.

3JK Issue 1.00
Blank Page


3JK Issue 1.00
2 MPR Management


3JK Issue 1.00
2 MPR Management
2.1 9500 MPR Management
E1 TDM Service, STM-1 SDH Service, ATM services and Ethernet services
can be managed end To end :
End to End Provisioning
End To End Monitoring
E2E traffic management
9500 MPR
TDM Packet
Microwave
Ethernet 9500 MPR
Packet 9500 MPR 9500 MPR SDH/MPLS

Microwave
9500 MPR 1350 OMS
Ethernet
9500 MPR
NMS


3JK Issue 1.00
2 MPR Management
2.2 MPR IP addresses
MPR Node
The NE has the following IP addresses: (with MSS8 & MSS4)
NE IP address: it is the Controller IP address (default IP address = 10.0.1.2

with fixed mask 255.255.255.255);
TMN IP address: it is the IP address relevant to the Ethernet TMN port
(default IP address = 10.0.1.2 with mask 255.255.255.0);
TMN Port 4 IP address: the Port 4 can be used not for traffic, but for TMN.
Two TMN In-band addresses (by using the Ethernet traffic ports)
IP address assignment rules:
the TMN IP addresses of 2 NEs connected through a radio link must belong to
2 different subnetworks;
the TMN IP addresses of 2 NEs connected through an Ethernet cable must
belong to the same subnetwork.

As example of the IP address assignment refer to the attached diagram.

3JK Issue 1.00
2 MPR Management
2.2 MPR IP addresses [cont.]
MPR Terminal
The NE has the following IP addresses: (with MSS1c)
NE IP address: it is the Controller IP address (default IP address = 10.0.1.2

with fixed mask 255.255.255.255);
TMN IP address (NMS1): it is the IP address relevant to the NMS1 TMN port
TMN IP address (NMS2): it is the IP address relevant to the NMS2 TMN port
IP address assignment rules:
the TMN IP addresses of 2 NEs connected through a radio link must belong to
2 different subnetworks;
the TMN IP addresses of 2 NEs connected through an Ethernet cable must
belong to the same subnetwork.

As example of the IP address assignment refer to the attached diagram.

3JK Issue 1.00
2 MPR Management
2.3 TMN communication channels
On the 9500 MPR Node three types of TMN communication channels are
present:
TMN channel carried by 64 kbits/sec channel inside Radio frame;

TMN channel carried by Ethernet frames in Ethernet tributary 4 (on the front
panel of the Core-E module).
Two TMN In-band interfaces
On the 9500 MPR Terminal three types of TMN communication channels

are present:
TMN channel carried by 64 kbits/sec channel inside Radio frame;

TMN channel carried locally by Ethernet frames in NMS1/NMS2 TMN ports (on
the front panel of the MSS-1c).
TMN channel carried inside a User Ethernet traffic frame defined with a VLAN
identifier (TMN In-Band).


3JK Issue 1.00
2 MPR Management
2.4 TMN interfaces (9500 MPR Node)

With the introduction of TMN In-Band two new IP interfaces are added to those already available.
NE Local IP Address
TMN Local Ethernet interface, IP/subnet
TMN Out-of-Band interface on User Ethernet port 4, IP/subnet
TMN In-Band interface #1, IP/subnet
TMN In-Band interface #2, IP/subnet
User Ethernet port 4 can then used as:
pure Ethernet traffic interface
pure Out-of-band TMN Local Ethernet interface
Ethernet traffic interface carrying TMN In-Band traffic
The NE Local IP Address can be reused on one of the other TMN interfaces. These interfaces must have
different IP subnets.

3JK Issue 1.00
2 MPR Management
2.5 LCT Connection
9500MPR Node can be controlled by a LCT connected to the Core-E

unit.
The connection can be performed by using:

The dedicated NMS Ethernet port
Traffic Ethernet port, configured as TMN port.
9500MPR Terminal can be controlled by a LCT connected to the MSS-

1c.
The connection can be performed by using:

The dedicated CT Ethernet port.
The NMS1/NMS2 TMN ports.
The TMN In-Band inside any User Ethernet traffic port defined with a VLAN
identifier.


3JK Issue 1.00
2 MPR Management
2.6 MPR Capability IP Parameters
MPR Node NMS radio channel
(with MSS8 & MSS4)
Traffic
An address with a subnet An address with a NMS radio channel
mask for the Ethernet subnet mask for the
Tributary 4 port craft terminal port
Traffic
Ethernet Tributary 4 Craft Terminal NMS radio channel
port: RJ45 port: RJ45
Traffic
MPR has routing capability. From an IP point of view it is a router.

Each port can activate OSPF or static routing.
In case of OSPF each address must belong to an OSPF area.
With an internal DHCP server, MPR gives an address to the CT connected to the CT port.


3JK Issue 1.00
2 MPR Management
2.6 MPR Capability IP Parameters [cont.]
MPR Terminal
(with MSS1c)
An address with a An address with a subnet NMS radio channel

subnet mask for the mask for the
craft terminal port NMS1/NMS2 TMN ports
Traffic
Craft Terminal NMS1 & NMS2 TMN NMS radio channel
port: RJ45 ports: RJ45
Traffic

Each port can activate static routing.
With an internal DHCP server, MPR gives an address to the CT connected to the CT port.


3JK Issue 1.00
2 MPR Management
2.6 MPR Capability IP Parameters [cont.]
MPR-e Stand-alone
NMS radio channel
MPT Interconnections
An address with a With/without Traffic
Power Injector Box
subnet mask for the
craft terminal port
connection
Ethernet
Craft Terminal
port: RJ45
GE
GEthernet
Generic
Device
FE

Each port can activate static routing.
With an internal DHCP server, MPR gives an address to the CT connected to the FE port of
the GEthernet Generic Device.


3JK Issue 1.00
Answer the Questions
How many IP addresses can be assigned to the NE?

Which bit rate has been assigned to the TMN RF channel in the Radio
frame?
Which connections are available for the LCT?


3JK Issue 1.00
Example of MPR IP addresses
VLAN ID
NE IPAnnexe
1 Management System
10.0.3.1 11 12 13 14 27 28 41 42
Annexe:
ExampleExample
NMS IP of MPR IP
10.0.10.1 ofaddresses
MPR IP Addresses 1 2 3 4 17 18 3132
TDM B
NE MAC 00:20:60:05:02:07
Node A TDM C
NMS P4 OFF
OSPF AREA 0.0.0.1
PC IP 10.0.10.100
TDM A DEFAULT GATEWAY 10.0.10.1
ETH 1
ETH 2
MPR IP Addresses
VLAN ID 1+1 HSB
27 28
NE IP 10.0.3.2
NMS IP 10.0.30.2 1 2
NE MAC 00:20:60:05:02:08 Node B Traffic E1+ETH

NMS P4 OFF TMN
OSPF AREA 0.0.0.1 - Example - Traffic E1 TDM2ETH
TDM C Traffic E1 TDM2TDM
Traffic ETH
1,2, Port Number
NE IP 10.0.3.3 1,2, VLAN ID
NMS IP 10.0.30.3
NE MAC 00:20:60:27:02:07 Node C
ETH Generator
NMS P4 OFF
OSPF AREA 0.0.0.1
PDH Generator
1 3 22 All Rights Reserved Alcatel-Lucent 2011 Syncro Scheme
@@SECTION
Product Overview Management
@@MODULE 20
System All Rights Reserved Alcatel-Lucent @@YEAR
9500 MPR 9500MPR @@MODULETITLE
@@SECTIONTITLE R 3.0 Operation and Maintenance
@@PRODUCT @@COURSENAME Net Mask 255.255.255.0
TDM A
11 12 13 14
VLAN ID
1+1 FD
NE IP 10.0.3.4
NMS IP 10.0.4.4 5 6 7 8
NE MAC 00:20:60:27:02:05 Node D

NMS P4 10.0.5.4
OSPF AREA 0.0.0.1
PC IP 10.0.6.100
DEFAULT GATEWAY 10.0.6.6
ETH 1
VLAN ID
41 42
10 11
Node E Node F
TDM B
NE IP 10.0.3.5 NE IP 10.0.3.6
ETH 2
NMS IP 10.0.4.5 NMS IP 10.0.6.6
NE MAC 00:20:60:05:02:06 NE MAC 00:20:60:05:02:05
NMS P4 OFF NMS P4 10.0.5.6
OSPF AREA 0.0.0.1 OSPF AREA 0.0.0.1

3JK Issue 1.00
End of Module
Management System


3JK Issue 1.00
21
Section 2
Functional Description
Module 1
MSS HW Hardware Architecture
3JK Edition 1.00

3JK Edition 1.00
Blank Page

Functional Description MSS HW Hardware Architecture
9500 MPR 9500MPR R 2.1 Operation and Maintenence
Document History
02 2011-02-01 ALU University Update to rel. 3.0

Vimercate

3JK Edition 1.00
Objectives
describe the functionality of each unit of the MSS-4/MSS-8.


3JK Edition 1.00
Objectives [cont.]


3JK Edition 1.00
Table of Contents
1 PDH Local Access Unit 7

1.1 PDH Local Access unit 8
Blank Page 10
2 2xSTM-1 Local Access unit 11
2.1 2xSTM-1 Local Access unit 12
Blank Page 14
3 ASAP unit 15
3.1 ASAP unit 16
4 Modem unit (to interface ODU300) 19
4.1 Modem unit (to interface ODU300) 20
Blank Page 22
5 MPT Access Unit (with PFoE) 23
5.1 MPT Access Unit (with PFoE) 24
6 AUX peripheral unit 27
6.1 AUX peripheral unit 28
Blank Page 34
7 Core-E unit 35
7.1 Core-E unit 36
8 Distributors 41
8.1 Distributor 42
End of Module 52


3JK Edition 1.00


3JK Edition 1.00
1 PDH Local Access Unit


3JK Edition 1.00
1.1 PDH Local Access unit
32 E1 module
wk Core-E
FPGA
32 E1 sp Core-E
LIUs (Ceres) CESoP
wk Core-E
sp Core-E

In the TX direction, the E1 PDH card (E1 Access) processes and encapsulates up to 32 E1 input lines into
an Ethernet packet that is sent to the Core-E card(s).
In the RX direction, the E1 Access card extracts data from the Ethernet data packets and processes the
data to provide up to 32 E1 output lines.
The 32xE1 Local Access Module performs the following macro functions:
Termination of 32 E1 signals (32 E1 bi-directional interfaces according ITU-T G.703 on the front
panel)
Framed E1 bi-directional alarm management
Bi-directional Performance Monitoring on Framed E1
Encapsulation/Extraction of those PDH data flows into/from standard Ethernet packets Inter
Working Function
Reconstruction of the original PDH Timing meeting G823/824 Req.
Selection of the Active Core-E
Sending/getting those std Eth packets to the Core-E module
Communication with the Controller for provisioning and status report
The module communicates with the Core-E modules through two GbEth Serial copper bi-directional
interfaces on the backplane. The spare Core-E in not implemented.

3JK Edition 1.00
1.1 PDH Local Access unit [cont.]
E1 E1
17-32 1-16


3JK Edition 1.00
Blank Page


3JK Edition 1.00
2 2xSTM-1 Local Access unit


3JK Edition 1.00
2.1 2xSTM-1 Local Access unit
2xSTM-1 Local Access unit

This unit can manage up to 2xSTM-1 by installing two optional STM-1 SFP plug-ins (electrical or optical).
In the Tx direction, the STM-1 Local Access unit processes and encapsulates up to 2xSTM-1 input lines
into an Ethernet packet that is sent to the Core-E card(s).
In the Rx direction, the STM-1 Local Access unit extracts data from the Ethernet data packets and
processes the data to provide up to 2 STM-1 output lines.
The 2xSTM-1 Local Access Unit performs the following macro functions:
Transparent transport of the STM-1
Encapsulation/Extraction of the STM-1 into/from standard Ethernet packets Inter Working Function
Reconstruction of the original STM-1 Timing
Selection of the Active Core-E
Sending/getting those std Eth packets to the Core-E module
Communication with the Controller for provisioning and status report
The unit communicates with the Core-E modules through two GbEth Serial copper bi-directional
interfaces on the backplane.

3JK Edition 1.00
2.1 2xSTM-1 Local Access unit [cont.]


3JK Edition 1.00
Blank Page


3JK Edition 1.00
3 ASAP unit


3JK Edition 1.00
3 ASAP unit
3.1 ASAP unit

The ASAP unit is used to transport 16xE1 ATM traffic, with E1/IMA physical layer, in an MPR network.
The ASAP units are unprotected (No 1+1 EPS is available).
ATM traffic is transported within MPR network as "special" Ethernet traffic.
This "special" Ethernet traffic is managed by MPR following to RFC 4717 (IETF ATM PseudoWire
EdgetoEdgeeEmulation, PWE3) with N-1 encapsulation format.
ATM PW Ethernet traffic is managed by MPR is such a way to emulate the native QoS that would be
applied by an ATM equipment; in addition to that, specific techniques, similar to those applied to
TDM2ETH traffic, are applied to have air bandwidth optimisation (ATM PW Header Compression) and
reduce Cell Error Rate degradation due to packetization.

3JK Edition 1.00
3 ASAP unit
3.1 ASAP unit [cont.]
Main Characteristics
16xE1 G.704 supporting ATM/IMA
IMA protocol 1.1
Node-timed/loop-timed E1 port synch
ATM PWE3 encapsulation with N-to-one (N=1) encapsulation format (RFC
4717)
Max 8 IMA group
Max 16 E1 per IMA group
The IMA group must be in the same ASAP card
Ingress/Egress VPI translation
Transport of ATM traffic can be done in VCC mode or VPC mode (all the
nodes of the MPR chain must have the same mode):
VCC mode
VPC mode
Interfaces
16 E1 G.704 - SCSI Connectors
75 ohm or 120 ohm (at NE level)

VCC mode
It is possible to transport max 48 VC for every IMA group. It is possible to manage VC switching (= VCI
and VPI change)
It is possible to assign at every VC one specific QoS. Policing and shaping at ATM level has performed
VC mode only
The VC of the same class level (CBR / UBR+ / UBR) are managed in the same radio tail than are
available 3 different radio tails
VPC mode
It is possible to transport max 48 VP for every IMA group. It is possible to manage only VP switching
(=only VPI change)
All the VC inside the VP must have same QoS (= for ex. all CBR or all UBR)
The radio QoS (= radio tails) and QoS ATM (=policing and shaping) is managed only at VP level.
N.B.: The sum of VP + VC configured on a single ASAP card must be <128.

3JK Edition 1.00
3 ASAP unit
3.1 ASAP unit [cont.]

The 16xE1 ATM streams enter the ASAP unit on the front panel.
The block diagram is divided in 3 parts:
LIU/Framer
Network Processor
Confederation FPGA
The main functions implemented by the LIU/Framer are:
Internal termination supported: 75 ohm, 120 ohm.
Line code supported: HDB3.
Pulse shape: digitally programmable
Framing to G.704 E1 signals and to CRC-4 multi-frame alignment signals.
Detection of alarm conditions as loss of signal, loss of frame, loss of signaling multi-frame and loss of
CRC multi-frame.
The Network Processor is the heart of the ASAP card and provides the implementation of the protocols
to be supported as well as data forwarding. ATM-IMA over PseudoWire, SAToP (like on the PDH card),
CESoP, ML-PPP can be supported by the SW application controlling the Data Path and running on a
different MIPS processor embedded on the same chip.
The main function implemented in the confederation FPGA is the clock management.
The right-hand side is the backplane with the 1 Gb bus shared among the other slots and hence
common with the other units (PDH units and Modem units).

3JK Edition 1.00
4 Modem unit (to interface ODU300)


3JK Edition 1.00
4.1 Modem unit (to interface ODU300)
FPGA
(Guinnes)
AIR FRAMER
I
PDH/Data DAC IF TX
EPS
management TX TX Q
MODULATOR DAC
IDU/ODU
communication
311 Mhz /2
MODEM
ASIC
IF cable
AIR deFRAMER interface
PDH/Data I
RPS ADC
management IF RX
RX RX
Q
DEMOD ADC
ODU/IDU
communication
126 Mhz /2
Analog Chain
GbE Serial from/to Alternate

Radio Board for RPS

In Tx direction, the MODEM Module generates the IF signal to be sent to an MXC Out Door Unit. Such
signal contains a Constant Bit Rate signal built with the Ethernet packets coming from the Core-E;
those packets are managed in a different way depending on their own native nature.
Digital Framer
Classification of incoming packets from the Core-E (QoS)
Fragmentation
Air Frame Generation (synchronous with NE clock)
Digital Modulator
TX Analog Chain
DAC & low pass filtering
Modulation to 311 MHz IF TX
In Rx direction, the MODEM 300 Module terminates the IF signal coming from the ODU300 extracting
the original CBR and then the original Ethernet packets to be given the Core-E which distributes them
to the proper Module.
RX Analog Chain
126 MHz IF RX demodulation to I & Q
low pass filtering & ADC
Digital Demodulator
Carrier & CK recovery
Equalisation
Error Correction
Digital Deframer
RPS (hitless)
Defragmentation

3JK Edition 1.00
4.1 Modem unit (to interface ODU300) [cont.]
Transmitter connected to the antenna


3JK Edition 1.00
Blank Page


3JK Edition 1.00
5 MPT Access Unit (with PFoE)


3JK Edition 1.00
5.1 MPT Access Unit (with PFoE)

The MPT Access Unit is the interface for two MPT: MPT-HC or MPT-MC.
Two unprotected MPT-HC or MPT-MC can be connected to one MPT Access unit, but only one MPT-HC or
MPT-MC if the MPT has to be configured in 1+1 with another MPT in another MPT Access unit.
The connection to the MPT-HC can be realized:
by using two connectors:
one DC power Supply connector to send the power supply to the MPT-HC
one Gigabit Ethernet connector (electrical or optical) to send the Ethernet traffic and the Ethernet
control frames to the MPT-HC
or by using only one electrical Ethernet cable with the enabling of the PFoE (Power Feed over
Ethernet) function (Ethernet traffic + Power Supply on the same cable).
If the optical port has to be used, an SFP plug-in must be installed.
N.B.: If has been enabled port #1 (optical or electrical), the associated Power Supply port is #1.
N.B.: If has been enabled port #2 (optical or electrical), the associated Power Supply port is #2.
The connection to the MPT-MC is realized by using only one electrical Ethernet cable with the enabling
of the PFoE (Power Feed over Ethernet) function (Ethernet traffic + Power Supply on the same cable).

3JK Edition 1.00
5.1 MPT Access Unit (with PFoE) [cont.]
Main functions:
Provide the power supply interface and the Ethernet interface
Provide the Power Feed over Ethernet function
Lightning and surge protection
Ethernet and power interface supervision
EPS/HSB management function
Clock distribution function
L2 packet based Proprietary clock algorithm
Ethernet link quality monitor function
Radio Link Quality notification through MPR Protection Protocol frames
Communication with Core controller for provisioning and status report


3JK Edition 1.00
5.1 MPT Access Unit (with PFoE) [cont.]

Warning: The optional SFP plug-in, which has to be installed in the MPT Access unit, contains a Class 1
laser source. The laser source is placed in the left side of the SFP plug-in.
According to the IEC 60825-1 the explanatory label is not sticked on the equipment due to the lack of
space.

3JK Edition 1.00
6 AUX peripheral unit


3JK Edition 1.00
6.1 AUX peripheral unit
AUX peripheral unit block diagram

Service Channels access and Housekeeping alarms are available with the optional Auxiliary peripheral
unit.
Only one Auxiliary peripheral can be equipped. It can be installed in Slot 8 of MSS-8 or Slot 4 of MSS-4.
The Auxiliary peripheral unit on front panel is equipped with four connectors:
one connector to manage the Service Channel 1
one connector to manage the Service Channel 2
one connector to manage the housekeeping alarms
one connector for EOW (not used in the current release)

3JK Edition 1.00
6.1 AUX peripheral unit [cont.]
Service Channels
By CT/NMS the user can enable/disable the 64 kbit/s Service Channel
interfaces. By default they are disabled.
When enabled, the Service Channel interface 1 can be configured to
transport the following protocol:
1) Synchronous 64 Kb/s RS422/V.11 DCE co-directional
When enabled, the Service Channel interface 2 can be configured to
transport the following protocol:
1) Synchronous 64 Kb/s RS422/V.11 DCE co-directional
Radio Service Channels

On each radio direction three 64 kbit/s out-of-band channels are
dedicated to the transmission of the Service Channels.


3JK Edition 1.00
Alarm-Housekeeping
13 Alarm-Housekeeping pins are provided:
6 pins are configured as inputs
7 pins are configured as outputs.


3JK Edition 1.00
Input alarms
The polarity of each input Alarm-Housekeeping is configurable. The
state of each alarm input is configurable in order to be active, if the
voltage on the input is high (open contact) or if the voltage is low
(closed contact). This second option is the default value.
It is possible to assign one user label for each input.


3JK Edition 1.00
Output alarms
By default the presence of active alarm corresponds to closed relay
contact with a common wire available to the customer. By CT/NMS the
polarity can be changed independently for each alarm (both normally
closed and normally open contacts are available on the I/O connector).
When the power supply is down (and also when the power supply is on
but the SW has not yet initialized the HW), all the relays of the outputs
of the alarms/housekeeping are in the "open" state (HW default
condition).
The Output Housekeeping can be managed in Manual mode only: in
Manual mode the output state of each housekeeping is controlled by
the operator.
It is possible to assign one user label for each output.

Note: the Automatic mode is not supported in this release.

3JK Edition 1.00


3JK Edition 1.00
Blank Page


3JK Edition 1.00
7 Core-E unit


3JK Edition 1.00
7 Core-E unit
7.1 Core-E unit
2 SPFs
(option)

Based on packet technology with 7 GbEth serial internal interfaces between Core-E and peripherals
(jumbo frames 9728 bytes allowed)
4x10/100/1000 Ethernet electrical embedded interface (RJ45): port #1 to port #4
2 optional SFPs: port #5 and port #6.
N.B.: To port #5 and port #6 can be connected directly the MPT-HC.
The flash card stores the licence type, the equipment software, the equipment MIB and the equipment
MAC address.
Main Functions
Controller
Layer 2+ Eth Switch, VLAN management & MAC based
Ethernet MAC learning
x-connect function for PDH and Data payload traffic;
For any packetized flow, the switch will be in charge to manage the EPS also.
QoS management.
Selection of the synchronization Ck to be distributed to all plug-in.
The Core-E unit has the option to equip two SFPs(in port #5, port #6. These ports can be also used to
connect directly an MPT-HC.

3JK Edition 1.00
7 Core-E unit
7.1 Core-E unit [cont.]
(optional)

Warning: The optional optical SFP plug-in, which has to be installed in port #5 and port #6 of the Core-
E unit, contains a Class 1 laser source. The laser source is placed in the left side of the SFP plug-in.
According to the IEC 60825-1 the explanatory label is not sticked on the equipment due to the lack of
space.

3JK Edition 1.00
7 Core-E unit
Available SFPs for port #5 and port #6

The following SFPs are available:
1000BASE-LX (optical interface for Ethernet traffic)
1000BASE-SX (optical interface for Ethernet traffic)
1000BASE-T (electrical interface for Ethernet traffic)
2xE1 (electrical interface for 2 E1 streams)
EoSDH (optical interface for STM-1 signal with Ethernet traffic encapsulation)


3JK Edition 1.00
7 Core-E unit
2xE1 SFP
The 2xE1 SFP is an SFP module supporting MEF8 circuit emulation of up to 2
E1.
This module supports:
differential clock recovery
node timing
loop timing
This module is Synchronous Ethernet capable and it is compliant to optical
SFP 1000BASE-X. It can deliver the clock recovered from one of two
tributaries to hosting card through the standard SFP pin-out.
SFP module supports TDM2TDM and TDM2ETH services.
The port, in which the SFP has been installed, must be enabled by the
WebEML as an optical port, then all the configuration must be done with an
Enhanced Configuration File.

Note: The SFP must be installed after the Configuration File has been downloaded. If the SFP has been
installed before, withdraw it and then installed it again.

3JK Edition 1.00
7 Core-E unit
EoSDH SFP
The Ethernet over SDH SFP is an SFP module supporting the delivery of
Ethernet traffic over SDH layer by GFP encapsulation.
The module is compliant to 1000BASE-X specification and support one STM1
interface.
The NE manages the EoSDH SFP as an optical User Ethernet interface.
Synchronous operation mode and SSM support are not available, when EoSDH
SFP is hosted as optical User Ethernet interface.

Note: For the correct operation of the EoSDH SFP it is necessary to disable the autonegotiation via the
Configuration File.

3JK Edition 1.00
8 Distributors


3JK Edition 1.00
8 Distributors
8.1 Distributor
The Distributor subracks available are shown in the next pages.


3JK Edition 1.00
8 Distributors
8.1 Distributor [cont.]
Protection Panel 32E1 SCSI 68 - 1.0/2.3 75 ohm (Front/Rear)


3JK Edition 1.00
8 Distributors
Protection Panel RJ45 120 ohm (Front/Rear)


3JK Edition 1.00
8 Distributors
Protection Panel 32E1 SCSI 68 - 1.6/5.6 75 ohm (Front)


3JK Edition 1.00
8 Distributors
Protection Panel 32E1 BNC 75 ohm (Front)


3JK Edition 1.00
8 Distributors
Connector support 1.6/5.6 75 ohm Panel 1U


3JK Edition 1.00
8 Distributors
Connector support BNC 75 ohm Panel 1U


3JK Edition 1.00
8 Distributors
Support 19 Inch modules 120 ohm Panel 3U


3JK Edition 1.00
8 Distributors
E1 Protection SCSI 68/Sub-D 37 (Front/Rear)


3JK Edition 1.00
How many E1 streams are available on the front panel of the PDH
access unit?
When the Power Emission Status LED of the Modem unit is green ON in
the HSB configuration?
Which information is stored in the Flash Card installed in the Core-E
unit?


3JK Edition 1.00
End of Module
MSS HW Hardware Architecture


3JK Edition 1.00
22
Section 2
Module 2
ODU300 HW Architecture
3JK Issue 1.00
9500 MPR

3JK Issue 1.00
Blank Page

Functional Description ODU300 HW Architecture
Document History

Marcoussis

3JK Issue 1.00
Module Objectives
Describe the functionality of the ODU 300.


3JK Issue 1.00


3JK Issue 1.00
Table of Contents
Page
1 Outdoor Units 7
1.1 ODU300 Construction and Mounting 8
1.2 ODU300 Characteristics 9
2 ODU300 block diagram 11
2.1 ODU300 block diagram 12
3 Outdoor Installations 13
3.1 Installing the ODU 14
3.2 Direct-Mounted ODUs 15
3.3 Remote-Mounted ODUs (solution 1) 16
3.4 Remote-Mounted ODUs (solution 2) 17
3.5 Waveguide Flange Data 19
3.6 Grounding the ODU 20
3.7 ODU external connectors 21


3JK Issue 1.00


3JK Issue 1.00
1 Outdoor Units


3JK Issue 1.00
1 Outdoor Units
1.1 ODU300 Construction and Mounting
Construction comprises:
Cast aluminium base (alloy 380)
Pressed aluminium cover (sheet grade alloy 1050)
Base and cover passivated and then polyester powder coated
Compression seal for base-cover weatherproofing
Carry-handle
ODU300 Housing

The ODUs include a waveguide antenna port, Type-N female connector for the ODU cable, a BNC
female connector (with captive protection cap) for RSSI access, and a grounding stud.
The ODUs, are designed for direct antenna attachment via an 9500MPR-E-specific mounting collar
supplied with the antennas.
ODU polarization is determined by the position of a polarization rotator fitted within the mounting
collar.
A remote ODU mounting kit is available as an option. These may be used to connect an ODU to a
standard antenna, or to a dual-polarized antenna for co-channel link operation.
ODUs are fixed for Tx High or Tx Low operation.
Where two ODUs are to be connected to a single antenna for hot-standby or frequency diversity
configurations, a direct-mounting coupler is used. They are available for equal or unequal loss
operation. Equal loss is nominally 3 dB.
Unequal is nominally 1/6 dB.
The ODU assembly meets the ASTME standard for a 2000 hour salt-spray test, and relevant IEC, UL,
and Bellcore standards for wind-driven rain.
ODUs are frequency-band specific, but within each band are capacity-independent up to their design
maximums.

3JK Issue 1.00
1 Outdoor Units
1.2 ODU300 Characteristics
General Specification
Frequency Band options L6, U6, 7, 8, 11, 13, 15, 18,
23, 26, 28, 38 GHz
Modulation support (Static modulation) 4, 16, 32, 64, 128, 256 QAM
Modulation support (Adaptive modulation) 4, 16, 64 QAM
IF Specifications
Intermediate Frequency Transmit 311 MHz
Receive 126 MHz
Maximum IF 10.3 mm Cable length [NB] MSS to ODU 150 meters

[NB] Longer distances are possible using higher specification cable.

3JK Issue 1.00
1 Outdoor Units
1.2 ODU300 Characteristics [cont.]
ODU Interfaces
IF cable connector N-Type
AGC monitor point BNC
Antenna port Interface 6-38 GHz Standard EIA rectangular waveguide,
refer to ODU System specifications
Vertical (standard) or Horizontal
Polarisation, field 6-38 GHz, standard Proprietary direct mount for antenna
selectable Antenna diameters 0.3 to 1.8m
Mounting Remote mount for antenna diameters
>1.8m
6-38 GHz, optional Remote mount via flex/elliptical
waveguide


3JK Issue 1.00
2 ODU300 block diagram


3JK Issue 1.00
2 ODU300 block diagram
2.1 ODU300 block diagram
To MSS

The quadrature modulated 311 MHz IF signal from the MSS is extracted at the N-Plexer and passed via a cable
AGC circuit to an IQ demodulator/modulator.
Here the 311 MHz IF is demodulated to derive the separate I and Q signals using the 10 MHz synchronizing
reference signal from the MSS.
These I and Q signals modulate a Tx IF, which has been set to a specific frequency between 1700 and 2300 MHz,
such that when mixed with the Tx local oscillator signal (TXLO) in the subsequent mixer stage, it provides the
selected transmit frequency. Both the IF and Tx local oscillators are synthesizer types.
Between the IQ modulator and the mixer, a variable attenuator provides software adjustment of Tx power.
After the mixer, the transmit signal is amplified in the PA (Power Amplifier) and passed via the diplexer to the
antenna feed port.
A microprocessor in the ODU supports configuration of the synthesizers, transmit power, and alarm and
performance monitoring. The ODU microprocessor is managed under the NCC microprocessor, with which it
communicates via the telemetry channel.
A DC-DC converter provides the required low-voltage DC rails from the -48 Vdc supply.
In the receive direction, the signal from the diplexer is passed via the LNA (Low Noise Amplifier) to the Rx
mixer, where it is mixed with the receive local oscillator (RXLO) input to provide an IF of between 1700 and
2300 MHz. It is then amplified in a gain-controlled stage to compensate for fluctuations in receive level, and in
the IF mixer, is converted to a 126 MHz IF for transport via the ODU cable to the MSS.
The offset of the transmit frequencies at each end of the link is determined by the required Tx/Rx split. The
split options provided are based on ETSI plans for each frequency band. The actual frequency range per band
and the allowable Tx/Rx splits are range-limited within 9500MPR-E to prevent incorrect user selection.
A power monitor circuit is included in the common port of the diplexer assembly to provide measurement of
transmit power. It is used to confirm transmit output power for performance monitoring purposes, and to
provide a closed-loop for power level management over the specified ODU temperature and frequency range.

3JK Issue 1.00
3 Outdoor Installations


3JK Issue 1.00
3.1 Installing the ODU
The type is ODU300.

All ODUs are designed for direct-mounting to a collar supplied with direct-
fit antennas.
All ODUs can also be installed with standard antennas using a remote-
mount kit.
For single-antenna protected operation a coupler is available to support
direct mounting of the two ODUs to its antenna, or to support direct
mounting onto a remote-mounted coupler.
On the next slides, information are given concerning:
Direct-Mounted ODUs
Remote-Mounted ODUs
Grounding the ODU


3JK Issue 1.00
3.2 Direct-Mounted ODUs
The ODU is attached to its mounting collar using four mounting bolts,
which have captive 19 mm (3/4) nuts for fastening.
The ODU mounts directly to its antenna mount, as shown in Figure.
Pressed-Cover ODU and Mounting Collar


3JK Issue 1.00
3.3 Remote-Mounted ODUs (solution 1)

ODUs can be installed separately from its antenna, using a remote-mount to support the ODU, and a
flexible-waveguide or coaxial cable to connect the ODU to its antenna:
a flexible waveguide is required.
The remote mount allows use of standard, single or dual polarization antennas.
The mount can also be used to remotely support a protected ODU pairing installed on a coupler. The
coupler connects to the remote mount assembly in the same way as an ODU.
The remote mount clamps to a standard 112 mm (4) pole-mount, and is common to all frequency
bands. Figure shows an ODU installed on a remote mount.
Flexible waveguides are frequency band specific and are normally available in two lengths, 600 mm (2
ft) or 900 mm (3 ft). Both flange ends are identical, and are grooved for a half-thickness gasket, which
is supplied with the waveguide, along with flange mounting bolts.

3JK Issue 1.00
3.4 Remote-Mounted ODUs (solution 2)


3JK Issue 1.00
3.4 Remote-Mounted ODUs (solution 2) [cont.]


3JK Issue 1.00
3.5 Waveguide Flange Data
Spring Hole
Radio WaveguideM Waveguide Bolts Bolt Thread
Freq Band Washers Depth Bolt Length Required
Flange ating Flange Type Reqd Type Spec
Reqd mm
6 GHz UDR70 PDR70 WR137 8 x M5 8 M5x0.8 6H 10 Flange thickness + Hole
depth - 2mm
7/8 GHz UDR84 PDR84 WR112 8 x M4 8 M4x0.7 6H 8 Flange thickness + Hole
depth - 2mm
11 GHz UDR100 PDR100 WR90 8 x M4 8 M4x0.7 6H 8 Flange thickness + Hole
depth - 2mm
13 GHz UBR120 PBR120 WR75 4 x M4 4 M4x0.7 6H 8 Flange thickness + Hole
depth - 2mm
15 GHz UBR140 PBR140 WR62 4 x M4 4 M4x0.7 6H 8 Flange thickness + Hole
depth - 2mm
18/23/26 UBR220 PBR220 WR42 4 x M3 4 M3x0.5 6H 6 Flange thickness + Hole
GHz depth - 2mm
28/32/38 UBR320 PBR320 WR28 4 x M3 4 M3x0.5 6H 6 Flange thickness + Hole
GHz depth - 2mm

Table lists the antenna port flange types used with the ODU300, plus their mating flange options
and fastening hardware for remote mount installations.
UDR/PDR flanges are rectangular; UBR/PDR flanges are square.
On the ODU, the two flange styles are:
UDR. 6-hole or 8-hole (6/8 bolt holes depending on frequency range/waveguide type), flush-face
flange with threaded, blind holes.

UBR. 4-hole flush-face flange with threaded, blind holes.
The corresponding mating flange styles are:

PDR. 6-hole or 8-hole flange with gasket groove and clear holes.
PBR. 4-hole flange with a gasket groove and clear holes.
All fastening hardware is metric.

3JK Issue 1.00
3.6 Grounding the ODU
For all set-ups, one ground wire must be installed to ground the ODU.

The lightning surge suppressor is integrated in the ODU.

3JK Issue 1.00
3.7 ODU external connectors
Vertical Polarization Horizontal Polarization
IF cable
connector
(to Indoor Unit) RSSI
Waveguide feed head connector
RSSI connector
IF cable connector
(to Indoor Unit)


3JK Issue 1.00
3.7 ODU external connectors [cont.]
RSSI Monitoring Point

The ODU has a capped BNC female connector to access RSSI during antenna
alignment.
There is a linear relationship of voltage to RSSI, as shown in the table below;
an RSSI of 0.25 Vdc is equivalent to -10 dBm RSSI, and each additional 0.25
Vdc RSSI increase thereafter corresponds to a 10 dBm decrease in RSSI.
The lower the voltage the higher RSSI and better aligned the antenna is.
The RSSI figures in dBm are identical to the RSL figures displayed in A9500
MPR Craft Terminal.
RSSI Table
Units Measurement
BNC (Vdc) 0.25 0.5 0.75 1.0 1.25 1.5 1.75 2.0 2.25 2.5
RSSI (dBm) -10 -20 -30 -40 -50 -60 -70 -80 -90 -100


3JK Issue 1.00
Which modulations are supported in the ODU?
Which is the maximum length of the IF cable?
Can the ODU be directly connected to the antenna?
When must be used the RSSI monitoring point?


3JK Issue 1.00
End of Module
ODU300 HW Architecture


3JK Issue 1.00
23
Section 2
Module 3
MPT-HC HW Architecture
xx Issue 1.0
9500 MPR

xx Issue 1.0
Blank Page

Functional Description MPT-HC HW Architecture
Document History
01 2010-10-28 ALU Universitu, First edition

Marcoussis

xx Issue 1.0
Module Objectives
Describe the functionality of the MPT-HC.


xx Issue 1.0


xx Issue 1.0
Table of Contents
Page
1 Outdoor Units 7
1.1 MPT-HC Construction and Mounting 8
1.2 MPT-HC Characteristics 13
2 MPT-HC block diagram 15
2.1 MPT-HC block diagram 16
3.1 Installing the MPT-HC 20
3.2 6-7-8 GHz MPT-HC: integrated antenna (1+0) 21
3.3 11-38 GHz MPT-HC: integrated antenna (1+0) 22
3.4 6-7-8 GHz MPT-HC: integrated antenna (1+1) 23
3.5 11-38 GHz MPT-HC: integrated antenna (1+1) 24
3.6 6-7-8 GHz MPT-HC: non-integrated antenna (1+0) 25
3.7 11-38 GHz MPT-HC: non-integrated antenna (1+0) 26
3.8 6-7-8 GHz MPT-HC: non-integrated antenna (1+1) 27
3.9 11-38 GHz MPT-HC: non-integrated antenna (1+1) 28
3.10 MPT-HC external connectors 29
3.11 DC Extractor 34


xx Issue 1.0


xx Issue 1.0
1 Outdoor Units


xx Issue 1.0
1 Outdoor Units
1.1 MPT-HC Construction and Mounting
MPT-HC (Microwave Packet Transport) is a Microwave Equipment

capable to transport the Ethernet traffic over an RF radio channel.
The MPT-HC includes a waveguide antenna port, type-N female
connector for the DC connection, a maintenance connector (with
captive protection cap) for RSSI access, 1 electrical GE interface, 2 GE
optical interfaces (1 for data, 1 for for RPS) and a grounding stud.
The MPT-HC can be installed on an integrated antenna or on standard
poles, wall or pedestal mount, with an appropriate fastening system.
The MPT-HC (one or two depending on the configuration 1+0 or 1+1,
each one with a solar shield) incorporates the complete RF transceiver
and can be associated with an integrated or separate antenna.
The MPT-HC can be rapidly installed on standard poles with an
appropriate fastening system. The pole mounting is the same for 1+0 or
1+1 configurations from 6 to 38 GHz.


xx Issue 1.0
1 Outdoor Units
1.1 MPT-HC Construction and Mounting [cont.]
For 6 GHz & 7/8 GHz, the MPT-HC polarization is determined by the
rotation of the MPT-HC in 1+0 configuration and by the position of a
polarization rotator fitted within the coupler in 1+1 configuration.
For 11 GHz to 38 GHz, the MPT-HC polarization is determined by the
rotation of the polarization rotator fitted in the antenna port of the
MPT-HC in 1+0 configuration and by the position of a polarization
rotator fitted within the coupler in 1+1 configuration.
Where two MPT-HC have to be connected to a single antenna for hot-
standby or frequency diversity configurations, a direct-mounting
coupler is used. They are available for equal or unequal loss operation.
Equal loss is nominally 3 dB. Unequal is nominally 1/10 dB.
Three mechanical solutions are adopted.


xx Issue 1.0
1 Outdoor Units
11-38 GHz MPT-HC housing

With embedded diplexer for cost optimisation (11 GHz to 38 GHz), where the branching (diplexer) is
internal to the MPT-HC cabinet; this type of MPT-HC is identified by one Logistical Item only.

xx Issue 1.0
1 Outdoor Units
6 GHz MPT-HC housing

With embedded diplexer for cost optimisation and different mechanics from 11-38 GHz (6 GHz),
where the branching (diplexer) is internal to the MPT-HC cabinet; this type of MPT-HC is identified by
one Logistical Item only;

xx Issue 1.0
1 Outdoor Units
7-8 GHz MPT-HC housing

With external diplexer: due to a vary high number of shifters the diplexer is external for the flexibility
of the shifter customization (7 GHz and 8 GHz), where MPT-HC is composed by two independent units:
the BRANCHING assembly (containing the diplexer) and the RF TRANSCEIVER assembly (containing the
RF section); each of this type of MPT-HC is identified by two Logistical Items, one for the BRANCHING
assembly and another for the RF TRANSCEIVER assembly. To read the BRANCHING assembly
identification label it is necessary to separate the BRANCHING assembly from the RF TRANSCEIVER
assembly.

xx Issue 1.0
1 Outdoor Units
1.2 MPT-HC Characteristics
23, 26, 38 GHz
Modulation support (Adaptive modulation) 4, 16, 32, 64, 128, 256 QAM
Cable lenght
Power Supply cable > 200 m with cable diam. = 10.3 mm
< 200 m with cable diam. = 6.85 mm
Ethernet cable 100 m with electrical cable
500 m with optical cable
Optical cable to be used in 1+1 20 m (to interconnect the two MPT-HC)
configuration


xx Issue 1.0
Blank Page

This
All page
Rights is left blank
Reserved intentionally
Alcatel-Lucent 2011
xx Issue 1.0
2 MPT-HC block diagram


xx Issue 1.0
2.1 MPT-HC block diagram
MPT system

MPT-HC is break down into the following sections:

MPT-CB: Common Belt section. This section is Frequency independent, and all the features
relevant to this unit are common to all the MPT RF options.
MPT-RF: Radio Frequency section that is frequency dependent.
The MPT-HC interface is based on a Gb Ethernet, that can be either optical or electrical depending on
the needs and the cable length. If the optical port has/have to be used (data and/or RPS port), the
corresponfing SFP plug-in must be installed by opening the Cobox.

xx Issue 1.0
2.1 MPT-HC block diagram [cont.]


xx Issue 1.0
Blank Page

This
All page
Alcatel-Lucent 2011
xx Issue 1.0


xx Issue 1.0
3.1 Installing the MPT-HC
MPT-HC is designed for direct-mounting to a collar supplied with direct-

fit antennas. MPT-HC can also be installed with standard antennas using
a remote-mount kit.
direct mounting of the two MPT-HC to its antenna, or to support direct
Installation with integrated antenna
Installation with non-integrated antenna


xx Issue 1.0
3.2 6-7-8 GHz MPT-HC: integrated antenna (1+0)


xx Issue 1.0
3.3 11-38 GHz MPT-HC: integrated antenna (1+0)


xx Issue 1.0
3.4 6-7-8 GHz MPT-HC: integrated antenna (1+1)


xx Issue 1.0
3.5 11-38 GHz MPT-HC: integrated antenna (1+1)


xx Issue 1.0
3.6 6-7-8 GHz MPT-HC: non-integrated antenna (1+0)


xx Issue 1.0
3.7 11-38 GHz MPT-HC: non-integrated antenna (1+0)


xx Issue 1.0
3.8 6-7-8 GHz MPT-HC: non-integrated antenna (1+1)


xx Issue 1.0
3.9 11-38 GHz MPT-HC: non-integrated antenna (1+1)
PROTECTION RF coupler MAIN

MPT-HC MPT-HC


xx Issue 1.0
3.10 MPT-HC external connectors
(1)
RF
connection
CO-BOX
(2)
(5)
Power Supply
Place to install the SFP for 1+1

optional SFP plug-in configuration
RJ45
(3) (4)
Eth. Second MPT-HC
connection connection in 1+1
Views of MPT-HC with embedded diplexer (11-38 GHz)

WARNING: A waterproofness tape is glued on the waveguide of the MPT-HC. It must never be removed.
(1) Ref. in RF interface Interface

for connection of antenna or coupler waveguide
Connector
(2) figure Connector for power supply coaxial cable male N 50 ohm
(3) (1) RF Hole for Ethernet
interface connection
for connection (in the co-box)
of antenna Gland for Cat5e or optical cable (optional)
waveguide
or coupler
(4) Hole for connection to a second MPT-HC in 1+1 (in the co-box) Not used
(2) Connector for power supply coax. cable male N 50 ohm
(5) Co-box
(3) Hole for Ethernet connection (in the co- Gland for Cat5e or optical
box) cable (optional)
(4) Hole for connection to a second ODC
MPT-HC in 1+1 (in the co-box)
FREQUENCY GHz -> 11 13-15 18-26 38

Waveguide type -> WR75 WR62 WR42 WR28

xx Issue 1.0
3.10 MPT-HC external connectors [cont.]
(1)
RF
connection
(2)
Power Supply
OPENING THE CO-BOX

(3) RJ45 for electrical
connection
Eth.
connection CO-BOX
(5) Place to install the
(4) optional SFP for
Second optical connection
MPT-HC
Connection
in 1+1 SFP for 1+1
configuration
Views of MPT-HC with embedded diplexer (7 GHz and 8 GHz)

(1)Ref. in RF interfaceInterface
for connection of antenna or coupler waveguide
Connector
(2) figure Connector for power supply coaxial cable male N 50 ohm
(3) (1) Hole for Ethernet
RF interface connection
for connection (in the co-box)
of antenna Gland for Cat5e or optical cable (optional)
waveguide
or coupler
(2) Connector for power supply coax. cable male N 50 ohm
(5) Co-box
FREQUENCY GHz -> 7 8

Waveguide type -> WR112 WR112

xx Issue 1.0
(1)
RF
connection
(2)
Power Supply
OPENING THE CO-BOX

(3)
RJ45 for electrical
Eth.
connection CO-BOX
connection
(4) (5) Place to install the
Second
optional SFP for optical
MPT-HC connection
Connection
in 1+1
SFP for 1+1
configuration
Views of MPT-HC with embedded diplexer (6 GHz)

(1) RF interface for connection of antenna or coupler waveguide

Ref. in Interface Connector
(2) Connector for power supply coaxial cable male N 50 ohm
figure
(3) Hole for Ethernet connection (in the co-box) Gland for Cat5e or optical cable (optional)
(1) RF interface for connection of antenna waveguide
or coupler
(5) (2) Connector
Co-box for power supply coax. cable male N 50 ohm
FREQUENCY GHz -> 6

Waveguide type -> WR137

xx Issue 1.0

A voltmeter, such as a multimeter, is used to measure RSSI voltage.
Use the Light service kit cable for the power monitoring in addition to a
voltmeter.
Connect a voltmeter to the MPT-HC through the Light service kit cable.
The RSSI voltage provides a direct relationship with RSL, as follows:
Units Measurement (with MPT-HC)

Service kit cable (Vdc) 5 4.71 4.12 3.5 2.9 2.3 1.71 1.11 0.59 0.14
RSL (dBm) -10 -20 -30 -40 -50 -60 -70 -80 -90 -100


xx Issue 1.0
MPT Service Cord

Optional cable (P/N 3CC52191AA**).

Connector usage:
(M1) LEMO connector, to be plugged into LEMO connector on MPT-HC/MPT-MC.
banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio Rx field. During
equipment lineup, through a multimeter it is possible to easily point the antenna until the
measured voltage is the maximum, corresponding to the maximum radio Rx field.
(M2) RJ45 connector, to connect the MCT directly to the MPT.

xx Issue 1.0
3.11 DC Extractor

The DC Extractor, installed close to the MPT-HC, allows to interconnect the MSS and the MPT-HC with a
single electrical Ethernet cable by using the Power Feed over Ethernet solution (Ethernet traffic and
Power Supply on the same cable). The DC Extractor then separates the Power Supply from the Ethernet
traffic, which are separately sent to the MPT-HC.
The two cables, interconnecting the DC Extractor to the MPT-HC (the Power Supply cable to be
connected to the DC Out connector of the DC Extractor and Ethernet cable to be connected to the
Data Out connector of the DC Extractor), are provided, already terminated (2 m long), with the DC
Extractor itself.

xx Issue 1.0
Which modulations are supported in the MPT-HC?
Which is the maximum length of the Power Supply cable?
Can the MPT-HC be directly connected to the antenna?


xx Issue 1.0
End of Module
MPT-HC HW Architecture


xx Issue 1.0
24
Section 2
Module 4
MPT-HC V2 HW architecture
a Issue 01
9500 MPR

a Issue 01
Blank Page

Functional Description MPT-HC V2 HW architecture
Document History
01 2010-10-28 ALU Universitu, First edition

Marcoussis

a Issue 01
Module Objectives
Describe the functionality of the MPT-HC V2.


a Issue 01


a Issue 01
Table of Contents
Page
1 Outdoor Units 7
1.1 MPT-HC V2 Construction and Mounting 8
1.2 MPT-HC V2 Characteristics 11
Blank Page 12
2 MPT-HC V2 block diagram 13
2.1 MPT-HC V2 block diagram 14
3.1 Installing the MPT-HC V2 16
3.2 MPT-HC V2 external connectors 17
End of Module 22


a Issue 01


a Issue 01
1 Outdoor Units


a Issue 01
1 Outdoor Units
1.1 MPT-HC V2 Construction and Mounting
MPT-HC V2 is similar to MPT-HC from architecture standpoint and can

be used as spare part of the MPT-HC.
The differences vs MPT-HC are:
MPT-HC V2 can be natively Ethernet powered through a proprietary PFoE
MPT-HC V2 is capable to host external modules (RPS module or XPIC_RPS
module)
Two mechanical solutions are adopted.

With release MPR3.0, the presence of one of the 2 modules is mandatory.

a Issue 01
1 Outdoor Units
1.1 MPT-HC V2 Construction and Mounting [cont.]
MPT-HC V2 housing (6 GHz and 11 GHz to 38 GHz)

With embedded diplexer for cost optimisation (6 GHz and 11 GHz to
38 GHz), where the branching (diplexer) is internal to the MPT-HC V2
cabinet; this type of MPT-HC V2 is identified by one Logistical Item
only.


a Issue 01
1 Outdoor Units
1.1 MPT-HC V2 Construction and Mounting [cont.]
With external diplexer: due to a vary high number of shifters the

diplexer is external for the flexibility of the shifter customization (7
GHz and 8 GHz), where MPT-HC V2 is composed by two independent
units: the BRANCHING assembly (containing the diplexer) and the RF
TRANSCEIVER assembly (containing the RF section); each of this type of
MPT-HC V2 is identified by two Logistical Items, one for the BRANCHING
assembly and another for the RF TRANSCEIVER assembly. To read the
BRANCHING assembly identification label it is necessary to separate the
BRANCHING assembly from the RF TRANSCEIVER assembly.


a Issue 01
1 Outdoor Units
1.2 MPT-HC V2 Characteristics
23, 26, 38 GHz
Modulation support (Adaptive modulation) 4, 16, 32, 64, 128, 256 QAM
Cable lenght
Power Supply cable (Note 1) > 200 m with cable diam. = 10.3 mm
< 200 m with cable diam. = 6.85 mm
Ethernet cable (Note 2) 100 m with electrical cable
500 m with optical cable
Cable to be used in 1+1 configuration to interconnect the two MPT-HC V2

Note 1: The PS cable is used if the PFoE solution is not adopted.

Note 2: The Ethernet electrical cable is used with the PFoE solution.

a Issue 01
Blank Page


a Issue 01
2 MPT-HC V2 block diagram


a Issue 01
2 MPT-HC V2 block diagram
2.1 MPT-HC V2 block diagram
For the block diagram refer to the MPT-HC block diagram.


a Issue 01


a Issue 01
3.1 Installing the MPT-HC V2
MPT-HC V2 is designed for direct-mounting to a collar supplied with

direct-fit antennas. MPT-HC V2 can also be installed with standard
antennas using a remote-mount kit.
direct mounting of the two MPT-HC V2 to its antenna, or to support
direct mounting onto a remote-mounted coupler.


a Issue 01
3.2 MPT-HC V2 external connectors
MPT-HC V2 basic
(1)
(3) (2)
MPT-HC V2 equipped with RPS module MPT-HC V2 equipped with XPIC-RPS module
(5)
(4) (4)
(3) (2) (3) (2)
Views of MPT-HC V2 with embedded diplexer (6 GHz and 11-38 GHz)

RF interface for connection of antenna or coupler. Remove the plastic cover.

WARNING: A waterproofness tape is glued on the waveguide of the MPT-HC V2. It must never be
removed.

figure
(1) RF interface for connection of antenna or coupler Waveguide
(2) Connector for power supply cable or for PFoE RJ45 + R2CT
(Power Supply + Ethernet Traffic) cable
(3) Optical Ethernet connection LC + Q-XCO
(4) Connection to a second MPT-HC V2 in 1+1 LC + Q-XCO
(5) XPIC connector Not used in the current release
FREQUENCY GHz -> 6 11 13-15 18-26 38

Waveguide type -> WR137 WR75 WR62 WR42 WR28

a Issue 01
3.2 MPT-HC V2 external connectors [cont.]
MPT-HC V2 basic
(1)
(3) (2)
MPT-HC V2 equipped with RPS module MPT-HC V2 equipped with XPIC-RPS module
(5)
(4) (4)
(3) (2) (2)

(3)
Views of MPT-HC V2 with embedded diplexer (7 GHz and 8 GHz)
RF interface for connection of antenna or coupler. Remove the plastic cover.

WARNING: A waterproofness tape is glued on the waveguide of the MPT-HC V2. It must never be
removed.

figure
(1) RF interface for connection of antenna or coupler Waveguide
(2) Connector for power supply cable or for PFoE RJ45 + R2CT
(Power Supply + Ethernet Traffic) cable
(3) Optical Ethernet connection LC + Q-XCO
(4) Connection to a second MPT-HC V2 in 1+1 LC + Q-XCO
(5) XPIC connector Not used in the current release


a Issue 01

voltmeter.
Connect a voltmeter to the MPT-HC V2 through the Light service kit cable.
Units Measurement (with MPT-HC V2)

RSL (dBm) -10 -20 -30 -40 -50 -60 -70 -80 -90 -100


a Issue 01
MPT Service Cord


Connector usage:
(M1) LEMO connector, to be plugged into LEMO connector on MPT-HC V2/MPT-MC.
banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio Rx field.
During equipment lineup, through a multimeter it is possible to easily point the antenna until the

a Issue 01
Which modulations are supported in the MPT-HC V2?
Can the MPT-HC V2 be directly connected to the antenna?


a Issue 01
End of Module
MPT-HC V2 HW architecture


a Issue 01
25
Section 2
Module 5
MPT-MC HW Architecture
xx Issue 1.0
9500 MPR

xx Issue 1.0
Blank Page

Functional Description MPT-MC HW Architecture
Document History

Marcoussis
02 2011-02-01 ALU University, Update to rel. 3.0

Vimercate

xx Issue 1.0
Module Objectives
Describe the functionality of the MPT-MC.


xx Issue 1.0


xx Issue 1.0
Table of Contents
Page
1 Outdoor Units 7
1.1 MPT-MC Construction and Mounting 8
1.2 MPT-MC Characteristics 12
2 MPT-MC block diagram 13
2.1 MPT-MC block diagram 14
3.1 Installing the MPT-MC 18
3.2 7-8 GHz MPT-MC: integrated antenna (1+0) 19
3.3 6 and 11-38 GHz MPT-MC: integrated antenna (1+0) 20
3.4 7-8 GHz MPT-MC: integrated antenna (1+1) 21
3.5 6 and 11-38 GHz MPT-MC: integrated antenna (1+1) 22
3.6 MPT-MC: non-integrated antenna (1+0) 23
3.7 7-8 GHz MPT-MC: non-integrated antenna (1+1) 24
3.8 6 and 11-38 GHz MPT-MC: non-integrated antenna (1+1) 25
3.9 MPT-MC external connectors 26


xx Issue 1.0


xx Issue 1.0
1 Outdoor Units


xx Issue 1.0
1 Outdoor Units
1.1 MPT-MC Construction and Mounting
MPT-MC (Microwave Packet Transport) is a Microwave Equipment

capable to transport the Ethernet traffic over an RF radio channel.
The MPT-MC includes a waveguide antenna port, type-N female
connector for the DC connection, a maintenance connector (with
captive protection cap) for RSSI access, 1 electrical GE interface, 2 GE
optical interfaces (1 for data, 1 for for RPS) and a grounding stud.
The MPT-MC can be installed on an integrated antenna or on standard
poles, wall or pedestal mount, with an appropriate fastening system.
The MPT-MC (one or two depending on the configuration 1+0 or 1+1,
each one with a solar shield) incorporates the complete RF transceiver
and can be associated with an integrated or separate antenna.
The MPT-MC can be rapidly installed on standard poles with an
appropriate fastening system. The pole mounting is the same for 1+0 or
1+1 configurations from 6 to 38 GHz.


xx Issue 1.0
1 Outdoor Units
1.1 MPT-MC Construction and Mounting [cont.]
Two mechanical solutions are adopted.


xx Issue 1.0
1 Outdoor Units
6 and 11-38 GHz MPT-MC housing

With embedded diplexer for cost optimisation (6 GHz and from 11 GHz to 38 GHz), where the
branching (diplexer) is internal to the MPT-MC cabinet; this type of MPT-MC is identified by one
Logistical Item only.

xx Issue 1.0
1 Outdoor Units
7-8 GHz MPT-MC housing

With external diplexer: due to a vary high number of shifters the diplexer is external for the flexibility
of the shifter customization (7 GHz and 8 GHz), where MPT-MC is composed by two independent units:
the BRANCHING assembly (containing the diplexer) and the RF TRANSCEIVER assembly (containing the
RF section); each of this type of MPT-MC is identified by two Logistical Items, one for the BRANCHING
assembly and another for the RF TRANSCEIVER assembly. To read the BRANCHING assembly
identification label it is necessary to separate the BRANCHING assembly from the RF TRANSCEIVER
assembly.

xx Issue 1.0
1 Outdoor Units
1.2 MPT-MC Characteristics
23, 26, 38 GHz
Modulation support (Static modulation) 4, 16, 32, 64, 128 QAM
Modulation support (Adaptive modulation) 4, 16, 32, 64, 128 QAM
Cable lenght
Ethernet cable (Power Feed over 100 m
Ethernet)


xx Issue 1.0
2 MPT-MC block diagram


xx Issue 1.0
2.1 MPT-MC block diagram
MPT system

MPT-MC is break down into the following sections:

MPT-CB:Common Belt section. This section is Frequency independent, and all the features
relevant to this unit are common to all the MPT RF options.
MPT-RF: Radio Frequency section that is frequency dependent.
MPT-MC is similar to MPT-HC from architecture standpoint. MPT-MC has limited capacity vs MPT-HC
and is natively Ethernet powered (no Power extractor required).

xx Issue 1.0
2.1 MPT-MC block diagram [cont.]


xx Issue 1.0
Blank Page

This
All page
Alcatel-Lucent 2011
xx Issue 1.0


xx Issue 1.0
3.1 Installing the MPT-MC
MPT-MC is designed for direct-mounting to a collar supplied with direct-

fit antennas. MPT-MC can also be installed with standard antennas using
a remote-mount kit.
direct mounting of the two MPT-MC to its antenna, or to support direct
Installation with integrated antenna
Installation with non-integrated antenna


xx Issue 1.0
3.2 7-8 GHz MPT-MC: integrated antenna (1+0)


xx Issue 1.0
3.3 6 and 11-38 GHz MPT-MC: integrated antenna (1+0)


xx Issue 1.0
3.4 7-8 GHz MPT-MC: integrated antenna (1+1)
RF
COUPLER
MAIN
MPT-MC


xx Issue 1.0
3.5 6 and 11-38 GHz MPT-MC: integrated antenna (1+1)
MAIN
MPT-MC
RF COUPLER


xx Issue 1.0
3.6 MPT-MC: non-integrated antenna (1+0)


xx Issue 1.0
3.7 7-8 GHz MPT-MC: non-integrated antenna (1+1)
PROTECTION
MPT-MC
RF COUPLER


xx Issue 1.0
3.8 6 and 11-38 GHz MPT-MC: non-integrated antenna (1+1)


xx Issue 1.0
3.9 MPT-MC external connectors
RF
Connection
(1)
(2)
Eth.
connection
Views of MPT-MC with embedded diplexer (6 and 11-38 GHz)

WARNING: A waterproofness tape is glued on the waveguide of the MPT-MC. It must never be removed.

(2) Ref. in figureEthernet electrical cable Interface
R2CT Connector
(2) Ethernet electrical cable R2CT
FREQUENCY GHz -> 6 11 13-15 18-26 38

Waveguide type -> WR137 WR75 WR62 WR42 WR28

xx Issue 1.0
3.9 MPT-MC external connectors [cont.]
RF
Connection
(1)
Eth. Elec.
Connect.
(2)
Views of MPT-MC with embedded diplexer (7 GHz and 8 GHz)

WARNING: A waterproofness tape is glued on the waveguide of the MPT-MC. It must never be removed.

(2) Ref. in figureEthernet electrical cable Interface
R2CT Connector
(2) Ethernet electrical cable R2CT


xx Issue 1.0

voltmeter.
Connect a voltmeter to the MPT-MC through the Light service kit cable.
Units Measurement (with MPT-MC)

RSL (dBm) -10 -20 -30 -40 -50 -60 -70 -80 -90 -100


xx Issue 1.0
MPT Service Cord


Connector usage:
(M1) LEMO connector, to be plugged into LEMO connector on MPT-HC/MPT-MC.
banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio Rx field. During
equipment lineup, through a multimeter it is possible to easily point the antenna until the

xx Issue 1.0
Which modulations are supported in the MPT-MC?
Can the MPT-MC be directly connected to the antenna?


xx Issue 1.0
Blank Page

This
All page
Alcatel-Lucent 2011
xx Issue 1.0
End of Module
MPT-MC HW Architecture


xx Issue 1.0
26
Section 2
Module 6
MSS terminal HW architecture
a Issue 01
9500 MPR

a Issue 01
Blank Page

Functional Description MSS terminal HW architecture
Document History

Marcoussis

Vimercate

a Issue 01
Module Objectives
Describe the functionality of each function of the MSS-1c.


a Issue 01


a Issue 01
Table of Contents
Page
1 MSS-1c Indoor Unit 7
1.1 MSS-1C 8
1.2 MSS Access Bloc Diagram 10
1.3 MSS-1c Features 11
1.4 MSS-1c Front and Rear Views 14
1.5 MSS-1c and Fan Unit 15
1.6 MSS-1c to MPT Interconnection 16
2 Distributors 21
2.1 Integrated DDF 22
2.2 Alternative Distributor Subracks 23
2.3 E1 SFP Modules 26
End of Module 28


a Issue 01


a Issue 01
1 MSS-1c Indoor Unit


a Issue 01
1.1 MSS-1C
The MSS-1c provides user port interface, cross-connection and switching

management.
The cross-connection matrix implements all the cross-connections between the

User ports (4 Ethernet ports and 10 E1 streams) and the Radio port. The matrix
is a standard Ethernet switch, based on VLAN, assigned by the MCT.
The 10xE1 enter the LIU and then the IWF, which manages the
encapsulation/reconstruction of PDH data to/from standard Ethernet packets
and sends/receives standard Ethernet packets to/from the Ethernet switch.
The Radio Interface interfaces the MPT-HC or the MPT-MC. The radio interface
is a standard GbEth interface electrical for MPT-MC, electrical or optical for
MPT-HC. It sends/receives standard Ethernet packets to/from the Ethernet
switch.
In case of electrical radio interface, on the same cable is also sent the power
supply for the MPT by using the Power Feed over Ethernet (PFoE) function.


a Issue 01
1.1 MSS-1C [cont.]
2xGE user ports HouseKeeping 2x NMS

E1s
Optical or electrical SFP RJ45 Ports RJ45
2x Sub-D 37 pins
Power Supply
2x MPT connections 2x 10/100/1000 BaseT Local CT 2x MPT connections

Optical SFP User ports RJ45 RJ45 Ethernet Powering


a Issue 01
1.2 MSS Access Bloc Diagram


a Issue 01
1.3 MSS-1c Features
More radio and site scalability and flexibility for installation teams:
Limited need for factory presetting channel frequency or bandwidth

Supports cellular mobile networks, and microcellular network back and
common carrier, private carrier and data networks, and utility haul
applications.
2G, 2.5G, and 3G network compatible
Outdoor Unit capacity and modulation independent
Outdoor Unit can support either split-mount and full-outdoor architecture
with the same hardware
Flexible aggregate capacity sharing between E1 and Ethernet
Adaptive packet transport that improves performance for priority services
Output power agility
ATPC
Adaptive Modulation
Packet-based internal cross-connect
TDM MEF8 encapsulation
Electrical GE interfaces
Software-based configuration
High Switching Capacity


a Issue 01
1.3 MSS-1c Features [cont.]
Loopbacks with MPT
1) Line Side loopback: this loopback routes data from the output of the Tx Data
Awareness block (after compression) to the input of the Rx data awareness
(decompression).
This is an internal loopback. It is a Loop and Continue.
It is possible to enable this loopback only at aggregate level.
When this loopback is activated the behavior is the following:

TDM2TDM and TDM2ETH flows are forwarded back to MSS-1c with source and
destination MAC address swapped. For TDM2ETH flows the loopback works only
if the ECID Tx and ECID Rx are the same. In case of ECID Tx different from
ECID Rx the loopback doesn't work.
Generic Ethernet flows are dropped. (This includes the ETH2ETH flows).

a Issue 01
1.3 MSS-1c Features [cont.]
Loopbacks with MPT [cont.]
2) Radio facing loopback: remote loopback allows an over-the-air loopback test to

be performed when the modem is operating in a continuous mode.
This is a line external loopback and connects the Receive data interface to the
Transmit data interface. This loopback is a Loop and Continue.
It is possible to enable this loopback only at aggregate level.
When this loop is enabled the expected behavior is the following:

TDM2TDM and TDM2ETH flows are looped back with source and destination MAC
address swapped. For TDM2ETH flows the loopback works only if the ECID Tx
and ECID Rx are the same. In case of ECID Tx different from ECID Rx the
loopback doesn't work.
Generic Ethernet flows are dropped. (This includes the ETH2ETH flows).

a Issue 01
1.4 MSS-1c Front and Rear Views
MSS-1c Front View
See the notes below

MSS-1c Rear View
Note 1: To use the User Ethernet Ports 3 and 4 an SFP plug-in (electrical or optical) must be installed.
Note 2: The meaning of the six LEDs is:

LED M: Major Alarm (red)
LED m: Minor Alarm (red) (not supported in the current release: permanently OFF)
LED W: Warning (yellow) (not supported in the current release: permanently OFF)
LED MPT1: MPT Status (green/red/yellow)
LED MPT2: not supported
LED A: Abnormal condition (yellow)
LED A is ON in the following conditions: Tx Power muted by operator

ACM frozen by operator
MPT loopback active
LED MPT1 can be:
GREEN: MPT is emitting power as expected according the known configuration
YELLOW: MPT is not emitting power due to a forced Squelch condition
RED: MPT is ABNORMALLY emitting power
SWITCHED OFF: MPT is not emitting power according with the known configuration
At start-up the MSS-1c:

lights on all the alarm LEDs (Major, Minor, Warning and Abnormal)
lights on the MPT LED as yellow, then this LED will be GREEN, RED or YELLOW, as explained above.

a Issue 01
1.5 MSS-1c and Fan Unit
An optional Fan unit must be used to dissipate the MSS-1c

in special case when the ambient temperature is > +50C.
The MSS-1c and the Fan unit are mounted on a bracket compatible with 19" rack.
Height is 1.3U.
The Fan unit is powered by the MSS-1c with a cable placed on the rear side. The
cable is provided with the Fan unit.
The Fan unit includes two fans.
One bi-color LED on the front panel gives the status of the Fan unit:
- Fans alarm = OFF <-> LED = green
Fans alarm = ON <-> LED = red
Note:
Installation position: the MSS-1c on the right and the Fan unit on the left.

a Issue 01
1.6 MSS-1c to MPT Interconnection
MPT-HC electrical connection (up to 100m)

One electrical Ethernet cable connects the MSS-1c to its MPT-HC.

The Ethernet electrical cable is provided with connectors to be mounted on site with the specific
RJ45 tool (1AD160490001).
Note: With the MPT-HC the Power Extractor must be installed close to the MPT-HC. In this case the
interconnection between the MSS-1c and the MPT-HC is made with a single electrical Ethernet cable
by using the Power Feed over Ethernet (Ethernet traffic and Power Supply on the same cable). The
Power Extractor then separates the Power Supply from the Ethernet traffic, which are separately
send to the MPT-HC.

a Issue 01
1.6 MSS-1c to MPT Interconnection [cont.]
MPT-HC optical connection (up to 350m)

One optical Ethernet cable connects the MSS-1c to its MPT-HC.

A coaxial cable connects the MPT-HC to the MSS-1c or to Station battery.

a Issue 01
MPT-HC V2 electrical connection (up to 100m)

One electrical Ethernet cable connects the MSS-1c to its MPT-HC V2.
The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45
tool (1AD160490001).

a Issue 01
MPT-HC V2 optical connection
(optical cable + power (optical cable + power supply

supply cable to MSS-1c) cable to Station battery)

Two cables connect the MSS-1c to its MPT-HC V2:

for length lower or equal to 100 m the power cable can be CAT5E cable to send the power supply
to the MPT-HC V2 . The Ethernet electrical cable is provided with connectors to be mounted on site
MPT-HC V2.
Note: A special adapter cord must be connected to the coaxial cable on the MPT-HC V2.

a Issue 01
MPT-MC optical connection (up to 100m)

One electrical Ethernet cable connects the MSS-1c to its MPT-MC.

The Ethernet electrical cable is provided with connectors to be mounted on site with the specific
RJ45 tool (1AD160490001).

a Issue 01
2 Distributors


a Issue 01
2 Distributors
2.1 Integrated DDF
The integrated DDF are mounted in the MSS rack and support the
connectors of the tributary cables.
There is also a 1U version (non-EMC)
Connector support 1.6/5.6 75 ohm Panel 1U


a Issue 01
2 Distributors
2.2 Alternative Distributor Subracks
They are an alternative to the previous cables, and combine protection

and distribution
They are connected to MSS with:

- one SCSI68-SCSI68 cord in 16 E1 1+0 up to
- four SCSI68-SCSI68 cords in 32 E1 1+1
available in 1.0/2.3 , RJ45 , 1.6/5.6 , BNC

(these available Distributor subracks are shown in the next pages)


a Issue 01
2 Distributors
2.2 Alternative Distributor Subracks [cont.]
Protection Panel 32E1 SCSI 68 - 1.0/2.3 75 ohm (Front/Rear)
Protection Panel RJ45 120 ohm (Front/Rear)


a Issue 01
2 Distributors
2.2 Alternative Distributor Subracks [cont.]
Protection Panel 32E1 SCSI 68 - 1.6/5.6 75 ohm (Front)
Protection Panel 32E1 BNC 75 ohm (Front)


a Issue 01
2 Distributors
2.3 E1 SFP Modules
various cords are available:

cord RJ45 plug - free 120 ohms
cord RJ45 plug - 2 x RJ45 plugs
cord RJ45 plug - 4 x coax free
Y protection cord RJ45


a Issue 01
How many E1 streams are available on the front panel

of the PDH access function ?
How many TMN accesses are available on the front
panel of the MSS-1c subrack ?


a Issue 01
End of Module
MSS terminal HW architecture


a Issue 01
31
Section 3
NE operation
Module 1
Operator interface MPR node
3JK Edition 1.00

3JK Edition 1.00
Blank Page

NE operation Operator interface MPR node
Document History

Vimercate

3JK Edition 1.00
Objectives
understand all the menus available with the LCT.


3JK Edition 1.00
Objectives [cont.]


3JK Edition 1.00
Table of Contents
Blank Page 10
1 WebEML start 11
1.1 WebEML start 12
Blank Page 15
2 WebEML Main View 16
2.1 WebEML Main view 17
2.2 Main Tool Bar Area 20
2.3 Severity Alarm Panel 21
2.4 Domain Alarm Synthesis Panel 22
2.5 Management State Control Panel 23
2.6 Selection Criteria 24
2.7 Button Policy 25
3 Menu Configuration 26
3.1 Menu Configuration 27
3.2 Menu NE Time 28
3.3 Menu Network Configuration 29
3.3.1 Local Configuration 30
3.3.2 NTP Configuration 31
3.3.3 IP Static Routing Configuration 32
3.3.4 OSPF Area Configuration 34
3.3.5 Routing Information 36
3.4 Menu Alarm Severities 37
3.5 Menu System Settings 41
3 1 5 3.6 Menu Cross Connections All Rights Reserved Alcatel-Lucent 2011 44
3.6.1 LAG area
45
3.6.2 Connectors 46
3.6.3 Graphical Area 48
3.6.4 Buttons 49
3.6.5 Segregated port view 50
3.6.6 How to segregate slots or ports 51
3.6.7 How to create a cross-connection 53
3.6.8 Creation Dialogs 55
3.6.9 Information Dialogs 56
3.6.10 TDM Cross-Connections 57
3.6.10.1 PDH to Radio/MPT-ACC 58
3.6.10.2 Radio to Radio 60
3.6.10.3 Radio/MPT-ACC to Ethernet 62
3.6.10.4 PDH to Ethernet 65
3.6.11 Cross-Connections with TDM2Eth Profile 67
3.6.12 How to modify a TDM cross-connection 70
3.6.12.1 PDH to Radio/MPT-ACC 71
3.6.12.3 Radio/MPT-ACC to Ethernet 73
3.6.12.4 PDH to Ethernet 74
3.6.13 SDH Cross-Connections 75
3.6.13.1 SDH to Radio/MPT-ACC 76
3.6.14 How to modify an SDH cross-connection 80
3.6.14.1 SDH to Radio/MPT-ACC 81
3.6.15 ATM Cross-Connections 83
3.6.15.1 ASAP Radio 84
3.6.15.2 Radio Radio 87
3.6.15.3 Radio Ethernet 90
3.6.15.4 ASAP Ethernet 92

3JK Edition 1.00
3.6.16 How to modify an ATM cross-connection 94

3.6.16.1 ASAP-Radio 95
3.6.16.2 Radio-Radio 96
3.6.16.3 Radio-Ethernet 97
3.6.16.4 ASAP-Ethernet 98
3.6.17 LAG-LAG Cross-Connections 99
3.6.17.1 Ethernet LAG - Radio LAG cross-connections 100
3.6.17.2 Radio LAG - Radio LAG cross-connections 102
3.6.18 How to modify a LAG-LAG cross-connection 104
3.6.18.1 Ethernet LAG to Radio LAG 105
3.6.18.2 Radio LAG to Radio LAG 106
3.7 Menu AUX Cross Connections 107
3.7.1 Local User Service Channel Cross-connection 108
3.7.2 Service Channels Cross-connect. in pass-through 109
3.7.3 How to create an AUX cross-connection 110
3.7.4 How to delete an AUX Cross Connection 112
3.8 Menu VLAN Configuration 113
3.8.1 802.1D 114
3.8.2 802.1Q 115
3.8.2.1 VLAN 1 Management 116
3.8.2.2 VLAN Table Management 117
3.8.2.3 VLAN Table Management (with LAGs) 119
3.9 Menu Traffic Descriptors 120
3 1 6 3.10 Menu Profile Management All Rights Reserved Alcatel-Lucent 2011 123
3.10.1 User Profiles
Management 124
3.10.2 User Management 125
3.10.3 How to Create a New User 126
3.10.4 How to Delete a User 128
3.10.5 Change the Password (by the Administrator) 129
3.10.6 Change Password (by the User) 130
3.11 Ethernet Features Shell 131
3.11.1 Simple examples for LAG creation 132
Blank Page 134
4 Menu Diagnosis 135
4.1 Menu Diagnosis 136
4.2 Alarms 137
4.2.1 File Menu 143
4.2.2 Filters Menu 144
4.2.2.1 Close Filter ... 145
4.2.2.2 Add a Filter 146
4.2.2.3 Edit Selected Filter 147
4.2.2.4 Delete Selected Filter 148
4.2.2.5 Delete Filters ... 149
4.2.2.6 Save Filters As ... 150
4.2.2.7 Load Filters From ... 151
4.2.3 Help Menu 152
4.3 Log Browsing 153
4.3.1 Event Log Browser 154
4.3.1.1 File Menu 156
4.3.1.2 Help Menu 159
4.4 Remote Inventory 160
4.5 Abnormal Condition List 161

3JK Edition 1.00
Page
4.6 Summary Block Diagram View 162
4.6.1 Main Block diagram view 163
4.6.2 PDH unit secondary view 164
4.6.3 SDH unit secondary view 168
4.6.4 Radio unit secondary view (ODU300) 172
4.6.5 MPT-ACC unit secondary view (MPT-HC) 178
4.6.6 MPT-ACC unit secondary view (MPT-MC) 184
4.7 Current Configuration View 188
5 Menu Supervision 189
5.1 Menu Supervision 190
5.2 Access State 191
5.2.1 Requested (Switching OS <-> CT access state) 192
5.2.2 OS (Switching CT access state <-> OS) 193
5.3 Restart NE 194
5.4 MIB Management 195
5.4.1 Backup 196
5.4.2 Restore 197
5.4.3 Remove file 198
5.5 SW Licence 199
Blank Page 200
6 Tab-panel Equipment 201
6.1 Tab-pabel equipment 202
6.2 Starting From Scratch 203
3 1 7 6.3 Tab panels in the Resource Detail All Rights Area
Reserved Alcatel-Lucent 2011 204
6.3.1 Alarms
tab-panel
9500 MPR 9500MPR R 3.0 Operation and Maintenance 205
6.3.2 Settings tab-panel 206
6.3.2.1 Equipment Type 207
6.3.2.2 Alarm Profile 211
6.3.2.3 Protection Type (P32E1DS1 & MD300) 212
6.3.2.4 Protection Type with MPT Access unit 214
6.3.2.5 Protection Type Configuration with STM-1 units 216
6.3.3 Remote Inventory tab-panel 217
Blank Page 218
7 Tab-panel Protection Schemes 219
7.1 General 220
7.2 EPS Management 222
7.2.1 Protection Schema Parameters 223
7.2.2 Commands 224
7.3 RPS Management 225
7.3.2 Commands 227
7.4 HSB Protection Management 228
7.4.2 Commands 230
8 Tab-panel Synchronization 231
8.1 Menu Synchronization 232
8.2 Synchronization Sources assignment 233
8.3 Synchronization sources assignment rules 237
8.4 Allowed synchronization sources assignment 238
8.5 SSM Summary Table 239
Blank Page 240

3JK Edition 1.00
Page
9 Tab-panel Connections 241
9.1 Menu Connections 242
10 PDH view for PDH domain 243
10.1 PDH Unit configuration 244
10.1.1 Alarms tab-panel 246
10.1.2 Settings tab-panel 247
10.1.3 General information on Circuit Emulation 248
10.1.4 Node Timing configuration 251
10.2 Loopback 252
10.2.1 How to activate a loopback 253
10.2.2 How to remove a loopback 254
11 SDH view for SDH domain 255
11.1 General information 256
11.1.1 Protection 257
11.1.2 Tab-panels 258
11.2 Alarms 259
11.3 Settings 260
12 Radio view for Radio domain 261
12.1 Radio domain menu 262
12.2 Alarms 263
12.3 Settings 264
12.3.1 ODU300 265
12.3.1.1 Direction area 266
318 12.3.1.2 Channel area All Rights Reserved Alcatel-Lucent 2011 277
12.3.2 MPT-HC
12.3.3 MPT-MC 304
12.4 Measurement 323
12.4.1 How to read a Power Measurement file 327
12.5 Loopback 328
12.5.1 How to activate a loopback 331
12.5.2 How to remove a loopback 332
12.6 Power Source 333
13 ATM view for ATM DOMAIN 335
13.1 ATM view for ATM DOMAIN 336
13.1.1 E1 Layer 337
13.1.2 IMA Layer 338
13.1.3 ATM Layer 341
13.1.3.1 ATM Layer Configuration 342
13.1.3.2 VP Layer Configuration 344
13.1.3.3 VC Layer Configuration 349
13.1.4 ATM PW Layer 352
13.1.4.1 ATM PW Parameters 353
13.1.4.2 VPI/VCI Translation 356
14 Core-E view for Core-E and Ethernet domain 357
14.1 Core-E domain 358
14.1.1 Ethernet Physical Interface 359
14.1.1.1 Alarm tab-panel 360
14.1.1.2 Settings tab-panel (Ethernet Port#1 to Port#4) 361
14.1.1.3 Settings tab-panel (Ethernet Port#5 and #6) 362

3JK Edition 1.00
Page
14.1.2 TMN Interface 363

14.1.2.1 Alarms tab-panel 364
14.1.2.2 TMN In-band 365
14.1.2.3 TMN Ethernet port 366
14.1.2.4 TMN Ethernet Port #4 367
14.1.3 Ethernet LAG 368
14.1.3.1 MPT-HC connected to the Core-E 370
15 AUX view for AUX DOMAIN 371
15.1 Name of Level 2 372
15.1.1 Settings 373
15.1.2 External Points 374
15.1.2.1 Input External Points 375
15.1.2.2 Output External Points 376
16 Annex A: Network Element Overview 377
16.1 Main View 378
16.2 NE Configuration area 379
16.2.1 NE Information 380
16.2.2 NE Description 381
16.2.3 Command Buttons 382
16.3 Status & Alarms area 383
16.4 Supervision Function 384
16.5 Menu Bar 385
3 1 9 16.6 Sequence for NETO interfaceAlland NE list
Rights Reserved Alcatel-Lucent 2011 387
Blank Page 389
End of Module 390

3JK Edition 1.00
Blank Page


3JK Edition 1.00
1 WebEML start


3JK Edition 1.00
1 WebEML start
1.1 WebEML start
This chapter explains all the screens of the WebEML, which is started
by a double click on the WebEML icon of the PC desktop.
The PC must be connected to the TMN port of the Core-E unit in the
MSS.
1) Start the WebEML by double click on the relevant icon on the PC desktop.


3JK Edition 1.00
1 WebEML start
1.1 WebEML start [cont.]
2) NEtO opens. Insert the IP address of the NE (default: 10.0.1.2) and click OK.
For more details on NEtO refer to Annex A: Network Element Overview.

Note: To access the NE the PC must be configured to Get automatically an IP address, because the
NE is configured as DHCP Server with default IP address 10.0.1.2.

3JK Edition 1.00
1 WebEML start
1.1 WebEML start [cont.]
3) When the NE is supervised, click Show.
4) The Main view opens.


3JK Edition 1.00
Blank Page


3JK Edition 1.00
2 WebEML Main View


3JK Edition 1.00
2 WebEML Main View
2.1 WebEML Main view
The WebEML Main View Area manages all domains from which the
operator can start. It is organized with tab panels, e.g. many windows
placed one upon another. Each window is selectable (placing it on top
of the others) with a tab shown on the top.
Two Main views are possible according to the MSS version:
MSS-8
MSS-4


3JK Edition 1.00
2 WebEML Main View
2.1 WebEML Main view [cont.]
MSS-8

The Main View Area manages all domains from which the operator can start. It is organized with tab panels, e.g. many windows
placed one upon another. Each window is selectable (placing it on top of the others) with a tab shown on the top.
Tab-panels
Each tab-panel represents a set of functions. The following tab-panels are present:
Equipment (to manage the equipment configuration)
Schemes (to manage the protection schemes in 1+1 configuration)
Synchronization (to manage the synchronization)
Connections (to manage the cross-connections)
Each tab-panel consists of three areas:
Resource-Tree Area: displays all the available resources of the NE.
Resource-List Area: may be represented by: Tabular View or Graphical View.
Tabular View: displays a tabular representation of the selected resource. As default, no tabular element is shown.
Graphical View: displays a graphical representation of the selected resource. As default, no tabular element is shown.
Resource-Detail Area: displays detailed information of a selected item in the Resource List area. As a default, no entry view is
displayed as a consequence of the default behavior of the Resource List area.
Figure (Main view) is the entry point of the application and provides basic diagnostic and configuration functions. Following
multiple main views are available:
Equipment view, for Equipment configuration;
Radio view, for Radio domain (double click on a Radio unit);
PDH view, for PDH domain (double click on a PDH unit);
ATM view, for ATM domain (double click on an ASAP unit);
AUX view, for Auxiliary channel domain (double click on the AUX peripheral unit);
Core-E view, for Core-E and Ethernet domain (double click on a Core-E unit).
Navigation from main view to multiple main views (related to the equipment components) can be done by simply double-clicking
on the component graphical representation. Such operation will open a new window containing selected secondary view. Starting
from main view, the operator will also see all slots and ODUs layout. Each slot contains schematics of available board (if present)
together with status and other details. Slots schematics will in fact contain usual alarms information with a clarifying coloured
icon that reports the same icon visible in tree view.
Other icons are:
On the right of the unit front panel, a new icon could be a check mark ( ) or a switch symbol ( ).
: it means the slot is active;
: it means the slot is in stand-by mode.
As shown in Figure, an X-shaped icon ( ) will be added on the left to slots when some cross connections are related to it.

3JK Edition 1.00
2 WebEML Main View
2.1 WebEML Main view [cont.]
MSS-4

The Main View Area manages all domains from which the operator can start. It is organized with tab panels, e.g. many windows
placed one upon another. Each window is selectable (placing it on top of the others) with a tab shown on the top.
Tab-panels
Each tab-panel represents a set of functions. The following tab-panels are present:
Equipment (to manage the equipment configuration)
Schemes (to manage the protection schemes in 1+1 configuration only)
Synchronization (to manage the synchronization)
Connections (to manage the cross-connections)
Each tab-panel consists of three areas:
Resource-Tree Area: displays all the available resources of the NE.
Resource-List Area: may be represented by: Tabular View or Graphical View.
Tabular View: displays a tabular representation of the selected resource. As default, no tabular element is shown.
Graphical View: displays a graphical representation of the selected resource. As default, no tabular element is shown.
Resource-Detail Area: displays detailed information of a selected item in the Resource List area. As a default, no entry view is
displayed as a consequence of the default behavior of the Resource List area.
Figure (Main view) is the entry point of the application and provides basic diagnostic and configuration functions. Following
multiple main views are available:
Equipment view, for Equipment configuration;
Radio view, for Radio domain (double click on a Radio unit);
PDH view, for PDH domain (double click on a PDH unit);
ATM view, for ATM domain (double click on an ASAP unit);
AUX view, for Auxiliary channel domain (double click on the AUX peripheral unit);
Core-E view, for Core-E and Ethernet domain (double click on a Core-E unit).
Navigation from main view to multiple main views (related to the equipment components) can be done by simply double-clicking
on the component graphical representation. Such operation will open a new window containing selected secondary view. Starting
from main view, the operator will also see all slots and ODUs layout. Each slot contains schematics of available board (if present)
together with status and other details. Slots schematics will in fact contain usual alarms information with a clarifying coloured
icon that reports the same icon visible in tree view.
Other icons are:
On the right of the unit front panel, a new icon could be a check mark ( ) or a switch symbol ( ).
: it means the slot is active;
: it means the slot is in stand-by mode.
As shown in Figure, an X-shaped icon ( ) will be added on the left to slots when some cross connections are related to it.

3JK Edition 1.00
2 WebEML Main View
2.2 Main Tool Bar Area
This area contains a selection of handy quick-access buttons for common

features.
Left arrow to previous screen
Second button: not operative
Right arrow to next screen
Block Diagram View: opens the Summary Diagram view
Current Configuration View: opens the Current Configuration view
Cross-Connections: opens the Cross-Connections menu
Segregated Ports: opens the Segregated Ports menu
AUX Cross Connections: opens the AUX Cross Connections menu
VLAN management: opens the VLAN Management menu
Performance Monitoring Tool: opens the Performance Monitoring Tool
menu


3JK Edition 1.00
2 WebEML Main View
2.3 Severity Alarm Panel
The CT provides an alarm functionality that informs the operator on the severity of the
different alarms in the NE as well as on the number of current alarms. There are five
different alarm severity levels. In the CT these different levels are associated with
colors:
Red: Critical alarm (CRI).
Orange: Major alarm (MAJ).
Yellow: Minor alarm (MIN).
Cyan: Warning alarm (WNG).
Blue: Indeterminate (IND).
Each alarm severity is represented by an alarm icon situated in the top left hand corner
of the view. These alarm icons are constantly represented on the different Equipment
views (NE view, Board view or Port view) so that the operator is always aware of the
alarms occurring in the system.
Furthermore the shape of the alarm icons in the alarm panel gives an indication of the
occurrence of alarms. The figures below describe the different examples.
An alarm icon with a circle inside it (and a number at the bottom of the icon) indicates
that alarms of the number and the type defined by the icon are occurring.
An alarm icon with a rectangle inside it indicates that no alarms of the type defined by
the icon are occurring.
An alarm icon grayed out indicates that spontaneous incoming alarm notification have
been inhibited.

N.B. The meaning of the icons in the Severity alarm synthesis is:
1) CRI - Critical alarm
Synthesis of alarms that needs immediate troubleshooting (typical: NE isolation).
2) MAJ - Major (Urgent) alarm
Synthesis of alarms that needs immediate troubleshooting.
3) MIN - Minor (Not Urgent) alarm
Synthesis of alarms for which a deferred intervent can be decided.
4) WNG - Warning alarm
Synthesis of alarms due to failure of other NE in the network.
5) IND - Indeterminate alarm
Synthesis of alarms not associated with the previous severities. Not operative.

3JK Edition 1.00
2 WebEML Main View
2.4 Domain Alarm Synthesis Panel
This area contains the bitmaps (more than one) representing the alarms
per domain. Each bitmap indicates the number of alarm occurrences for
each domain.
The meaning of the icons in the Domain alarm synthesis area is:
1) EXT - External Point
Synthesis of the External Points (Housekeeping alarms).
2) EQP Equipment alarm
Synthesis of alarms of the Equipment domain.
3) TRS Transmission alarm
Synthesis of alarms of the Transmission domain.


3JK Edition 1.00
2 WebEML Main View
2.5 Management State Control Panel
The different management states concerning the NE are also

represented via icons located in the top right corner of the equipment
views.
These icons are (from up to down):
1) Icon with a key symbol: Local Access state: indicates whether the NE is
managed by a craft terminal or by the OS
2) COM icon: Operational state: indicates whether or not the communication
with the OS is established.
3) SUP icon: Supervision state: indicates whether or not the NE is under OS
supervision.
4) OS icon: OS isolation.
5) NTP Server Status icon.
6) AC icon: abnormal condition state: indicates whether some abnormal
conditions have been recognized. The operator can visualize them with the
Diagnosis -> Abnormal condition list menu.

N.B.: As for the alarm icons, a rectangular management state icon represents the stable state while a
circular icon shape represents an unstable management state.
The meaning of the icons in the Management State Control Panel is:
1) Local Access State
GREEN LED: Indicates that the Craft Terminal has the OS permission to manage the NE (granted).
CYAN LED: Indicates that the Craft Terminal has not the OS permission to manage the NE (denied).
2) COM NE rechable/unreachable
GREEN LED: Identifies the Enable operational state of the connection between NE and Craft
Terminal (link down).

RED LED: Identifies the Disable operational state of the connection between NE and Craft
Terminal (link down).

3) SUP Supervision state
GREEN LED: NE is under supervision
BROWN LED: NE is not under supervision
Used in the OS.
4) OS OS isolation
5) NTP Network Timing Protocol
BROWN LED: Protocol disabled
GREEN LED: Protocol enabled, but the two servers are unreachable.
CYAN LED: Protocol enabled and one of the two servers is reachable.
6) AC Abnormal Condition
GREEN LED: Normal operating condition.
CYAN LED: Detection of an ABNORMAL operative condition. Type: switch forcing.

3JK Edition 1.00
2 WebEML Main View
2.6 Selection Criteria
Each tree node consists of possibly three symbols and a label. The first
optional symbol indicates structure state: if symbol is , three can be
expanded showing its contained lower levels. Tree structure can be
collapsed if symbol is . With no symbol, node represents a tree leaf.
Second symbol is the graphical representation of resource itself. Third
symbol is alarm status of component. The operator can select resource
by clicking with mouse to perform the action dependent on click type.
Resource Detail Area related to the selected item is displayed.
Each resource listed above may be selected by using the mouse by a:
Single left click:
By a single left click the resource is highlighted. This selection causes the activation
of the resource list area, e.g., every time the operator selects a resource in the
resource tree area the corresponding data are displayed in the Resource list area.
Double left click:
Double click operation on resource tree items allows the operator expanding tree
structure, so activating the display/update of resource list area, that will display
same information as for single click operation. As soon as a node is expanded,
another double click on such node would collapse tree structure to its closed view.


3JK Edition 1.00
2 WebEML Main View
2.7 Button Policy
The possible buttons for selection are the following:
Apply
this button activates the modify, but it does not close the window.
Cancel
this button closes the window without modifying the parameters displayed in the
window.
OK
this button activates the modify and closes the window
Close
this button closes the window
Help
this button provides the help management for the functions of the supporting
window.


3JK Edition 1.00
3 Menu Configuration


3JK Edition 1.00
3.1 Menu Configuration
Menu Configuration is divided in:
NE Time
Network Configuration
Alarm Severities
System Settings
Cross Connections
AUX Cross Connections
VLAN Configuration
Profiles Management
Ethernet Features Shell


3JK Edition 1.00
3.2 Menu NE Time

The NE local time can be displayed and/or re-aligned to the OS time basis.
From the Configuration pull down menu, select the NE Time option.
The dialogue box opens, from which the local NE can be set.
The NE Time dialogue box displays the current NE time and the current OS time.
To re-align the NE time to the OS time, click on the Set NE Time With OS Time check box and click the
Apply pushbutton to validate.
The Refresh pushbutton causes the refresh of the screen.
The NTP Status field is a read-only field, which shows the configuration regarding the NTP (Network
Time Protocol), if the protocol has been enabled and configured in Menu Configuration Network
Configuration NTP Configuration.
The NTP Status field shows:
status of NTP (enabled/disabled);
IP address of the Main Server, which distributes the time to all the NEs in the network;
IP address of the Spare Server (IP address of a second NTP Server), which replaces the Main Server in
case of failure.
Note: If a change of Change Time Zone on the PC is applied with the JUSM opened, in order to make it
updated on CT Close/Open the JUSM application and Read Time another time.

3JK Edition 1.00
3.3 Menu Network Configuration
The Network Configuration allows to perform the following operations:

Local Configuration:
defines the local virtual NE address
NTP Configuration
defines the Network Time Protocol
Ethernet Configuration
not implemented
IP Configuration which comprises:
IP static routing configuration: defines the Host/Network destination address for IP
static routing
OSPF Area configuration: defines the Open Shortest Path First address
IP Point-To-Point Configuration: defines the IP address of the interfaces which use
the PPP protocol (not implemented)
Routing information:
shows a summary of the information relevant to the routing which has been
configured.


3JK Edition 1.00
3.3.1 Local Configuration
Select the Network Configuration option and then, from the cascading
menu, the Local Configuration option.
The dialogue box opens, which allows to configure the local IP address
of the NE.
This local IP address is the IP address associated to a virtual interface
and to the other interfaces which use the PPP protocol (the TMN-RF
channels).
Default IP address: 10.0.1.2
Default mask: 255.255.255.255

Apply button is used to perform a configuration change of the data contained in the dialogue box and
closes it; the dialogue is visible until the end of the operations and a wait cursor is displayed.
Close button closes the dialogue.
Help button provides some useful information on the dialogue.

3JK Edition 1.00
3.3.2 NTP Configuration
This menu allows to enable the NTP (Network Time Protocol).

Put a check mark in the NTP protocol field to enable the protocol and write in the Main Server
address field the IP address of the server, which is in charge to distribute the time to all the NEs in the
network. In the Spare Server address field write the IP address of the Spare Server.
The Server reachability field is a read-only field, which shows the reachability of the NTP servers. The
following information can appear:
"Main server reachable"
"Spare server reachable"
"None servers reachable"
"Both servers reachable"
Click on Refresh to update the screen.
Click on Apply to send to the NE the NTP Configuration.

3JK Edition 1.00
3.3.3 IP Static Routing Configuration
By selecting IP static routing configuration a dialog-box opens, which

allows to configure the parameters for IP Static Routing Configuration.
The following fields and data are present:
IP Address: allows to define the IP address necessary to reach a specific
host/network
IP Mask: allows to define the IP Mask to reach a network
Default Gateway IP Address: allows to define the address of the next hop
gateway
Interface type: allows to use point to point interfaces made available by the
NE.
In the Host or Network Address Choice field select:
Host to address to a single IP address;
Network to address to a range of IP addresses.
In the Default Gateway or Point to Point I/F Choice select:
Default Gateway IP Address for the Ethernet interface;
Point to Point Interface Index for the NMS channels.

Apply button is used to perform a configuration change of the data contained in the complete table
and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
Close button closes the dialogue without changing of the data.
This is the IP interface to a host or network. Typically used at a spur to interface a host over the RF
path. In this scenario, the Default Gateway IP Address is 0.0.0.0 and the IP Mask (greyed out) is 0.0.0.0.
Also typically used at an end terminal in a radio link for interface with the network.
WARNING:
No pending (open) static routes are allowed.
The default software uses first the static routes and then the dynamic routes. An open static
route is always considered as a preferential path.
If in the screen the Default Gateway IP Address check box has been selected, write in the Default
Gateway IP Address field below the relevant IP address.
By pressing Create pushbutton it is possible to create new or change existing IP static routes

3JK Edition 1.00
3.3.3 IP Static Routing Configuration [cont.]


3JK Edition 1.00
3.3.4 OSPF Area Configuration
By selecting OSPF Area Configuration a dialog-box opens, which allows

to configure the parameters for OSPF (Open Shortest Path First) Area
Table Configuration.
OSPF Area IP Address
OSPF Area Stub
The fields give a synthetical information that includes all the addresses
(specific to a NE and to a Network) in an Area.

Apply button is used to perform a configuration change of the data contained in the complete RAP
table and close the view; the view is visible until the end of the operations and a wait cursor is
displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
Close button closes the dialogue without changing of the data.
WARNING: When the area is a Stub area, all the interfaces (NMS and Ethernet) must be defined Stub".
By pressing Create pushbutton a new screen opens.
N.B. 3 areas max. can be created.
In this new screen write the IP address, the IP mask and select the flag (True/False).

3JK Edition 1.00
3.3.4 OSPF Area Configuration [cont.]


3JK Edition 1.00
3.3.5 Routing Information
By selecting Routing Information a dialog-box opens: this screen is a

read-only screen and displays the routing parameters currently active
on the NE.

The pushbutton Refresh allows to refresh the information shown in the screen.
The Close button closes the dialogue without changing of the data.

3JK Edition 1.00
3.4 Menu Alarm Severities

This screen is a read-only screen. It is only possible to select one Profile Name and display the relevant
alarms.

3JK Edition 1.00
3.4 Menu Alarm Severities [cont.]
In this screen in the Profile Name field are listed the 4 default Alarm
Severity Profiles:
Profile "No Alarms". With this profile all alarms are disabled.
Profile "All Alarms". This profile enables the emission of all the alarms.
Profile "Radio Tx Alarms". This profile enables the emission of the Tx
alarms of the radio link.
Profile "Radio Rx Alarms". This profile enables the emission of the Rx
alarms of the radio link.
An Alarm Profile is the complete set of the equipment alarms with their
severity in case of Service Affecting situation and No Service Affecting
situation.
Each alarm has its Service Affecting and No Service Affecting attribute,
which can differ according to the Alarm Severity Profile.
In the current release only to 3 objects in the equipment (MSS subrack,
TMN local Ethernet, Radio) can be assigned a specific Alarm Profile.


3JK Edition 1.00
1. Select the object to which an Alarm Profile has to be associated.

2. Click on the icon.


3JK Edition 1.00
3. Select the Alarm Profile to be associated.

4. Put a check mark on the
"Show details" box.
5. The list of the alarms with
the relevant severity will
appear.
6. Click on Apply to
associate the
Alarm Profile.


3JK Edition 1.00
3.5 Menu System Settings
This menu allows the system configuration, providing the setting of

some parameters for the NE setup.
The NE configuration tab-panel has 8 fields:
Tributary Port Configuration
Quality Of Service
DHCP
Admission Control for Adaptive Modulation (ODU300 only)
Ethernet LOS Criteria
Static Lag Criteria
Event and Alarm Log
NE MAC Address

1) Tributary Port Configuration

This field allows to set the suitable impedance of the E1 stream (Unbalanced 75 ohms/Balanced 120
ohm). To activate the new impedance, click on Apply.
2) Quality Of Service
This field allows to set the suitable Quality Of Service (Disabled/DiffServ/802.1p). To activate the
new value, click on Apply.
The Ethernet switch provides a Quality of Service mechanism to control all streams. If the QoS is
disabled, all traffic inside the switch has the same priority, this means that for each switch port
there is only one queue (FIFO) therefore the first packet that arrives is the first that will be
transmitted.
The following values are available:
IEEE std 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag. If the
tag is present the correspondent priority is assigned to the packet;

DiffServ: each packet is classified based on DSCP field in the IP header to assign the priority;
3) DHCP
The DHCP server configures automatically IP address, IP mask and default gateway of the PC Ethernet
interface used to reach the NE.
The PC must be configured to get automatically an IP address.
The DHCP server uses an address pool of 10 IP address, defined according to the NE TMN port IP
address.
The IP mask is set to the mask of the NE TMN port and the default gateway is set to the NE IP
address.
The lease time is fixed to 10 minutes.
To activate the DHCP server, select Enabled and click on Apply.

3JK Edition 1.00
3.5 Menu System Settings [cont.]

4) Admission Control for Adaptive Modulation (ODU300 only)

Modulation) can be enabled or disabled. Default: Enabled.
When the Admission Control is "Enabled", the check is performed taking into account the capacity of
Taking as example 28 MHz channel spacing (with around 130 Mbit/s of net throughput available with
64QAM), the maximum number of E1s that could be provisioned is 18; the remaining capacity is
devoted to other types of traffic such as ATM or Ethernet.
When RSL value decreases, modulation schemes are downgraded first from 64QAM to 16QAM: the
traffic with lower priority exceeding 16QAM bandwidth is dropped and of course the E1s are kept. As
soon as the RSL value further decreases, modulation scheme are downgraded to 4QAM and all the
traffic exceeding 4QAM bandwidth is dropped (while the E1s are kept). It should be noted that there
is no possibility to provision a number of E1s greater than 18, because being all the E1s with the same
priority, it should not possible from system point of view to decide "which" E1s should be dropped
passing from 16QAM to 4QAM. In order to facilitate provisioning and commissioning operations, a
specific admission control check at CT level has been inserted, avoiding any potential mistakes from
the user provisioning a number of E1s that are not fitting inside 4QAM bandwidth.
When the Admission Control is "Disabled", the check is performed taking into account the capacity of
the highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-16-64 QAM range or 16
QAM for 4-16 QAM range).
It is possible to provision a number of E1s exceeding the 4QAM throughput; always keeping 28 MHz
channel as example, it is possible to provision more than 18E1s, up to 37E1s (value linked with 16QAM
capacity). In this case, when RSL value degrades and modulation scheme is downgraded from 16QAM
to 4QAM, all the TDM traffic is impacted. This feature is answering the need of transmitting an high
number of E1s, but without giving up the benefits of adaptive modulation for Ethernet traffic.

3JK Edition 1.00
3.5 Menu System Settings [cont.]

5) Ethernet LOS Criteria

By enabling this feature the following additional criteria are added to the Core protection switching
criteria:
LOS of Optical User Ethernet interface
LOS of any Electrical User Ethernet interfaces, including the LOS of the forth User Ethernet
interface working as TMN Local Ethernet interface.

Note: the default switching criteria are:
Core Card Missing
Core Card Fail
Flash Card failure
6) Static Lag Criteria

This feature is available only if the spare Core unit has been installed.
By enabling this feature the Ethernet ports of the Core-E unit in stand-by are in ON state (as the ports
of the Active Core-E unit), but the Ethernet traffic is not forwarded.
This behavior allows to reduce the out of service time of user traffic passing through the User
Ethernet interfaces in case of Core protection switching.
This feature shall not be used, when the NE is connected to an equipment performing Link
Aggregation and not supporting Active/Standby management of aggregated links.
7) Event and Alarm Log
As default the Logging is enabled. If set to "Disabled" the events are not sent to the Event Log
Browser application.
8) NE MAC Address
This field is a read-only field, which shows the MAC address of the NE. This MAC address must be used
in the cross-connection with TDM2Eth profile.

3JK Edition 1.00
3.6 Menu Cross Connections

The Main view is a graphical representation of Cross-connectable slots. Slots and Ethernet ports
(represented by connectors) are arranged according to the equipment configuration:
There are a maximum of 6 Ethernet ports placed on the Core-E area in the left side of the screen.
Port 4 is visible only when set to transport mode. If Ethernet port 4 is set to TMN, icon 4 is not
shown. Port 5 and 6 are visible, if in the Core-E unit has been installed and enabled the SFP plug-in.
There are a maximum of 6 PDH/SDH/ASAP/Radio/MPT-ACC slots (placed in the MSS-8 sub-rack) or 2
PDH/SDH/ASAP/Radio/MPT-ACC slots (placed in the MSS-4 sub-rack).
Note: In the following pages the examples will be done with MSS-8.
When two units are protected, the 2 protected slots are linked by a dashed line, (e.g.: Slot#5 RADIO is
protected with Slot#6 RADIO).
Note: Ethernet port#5 and port#6 will appear only if the optional SFP plug-in has been installed and
enabled in the Core-E unit. To enable the SFP plug-in go to the Setting tab-panel of the Core-E unit in
the Equipment tab-panel.
Note: If Ethernet port#4 has been configured as TMN, the port does not appear in the Main Cross-
Connections view.

3JK Edition 1.00
3.6.1 LAG area

If a LAG (Radio or Ethernet) has been created by using menu Configuration > Ethernet Features Shell
in the LAG area (on the right side of the screen) will appear the icons of the LAG with the identifying
number of the LAG.
Different icons are used to identify Radio LAG or Ethernet LAG.
The Ethernet ports involved in an Ethernet LAG are only present in the LAG area (not in the CORE-E
area).
In the figure LAG #4 is a Radio LAG, LAG #1 is an Ethernet LAG.

3JK Edition 1.00
3.6.2 Connectors
The connectors representing the MSS slots are start- and end-point for
actual cross-connections. By using the mouse drag-and-drop operations
the operator can create cross-connections through these points. These
connectors have specific icons:
identifies Ethernet RJ-45 connector (Ethernet ports);
identifies PDH slots;
identifies Radio slots (to interface ODU300);
identifies MPT-ACC slots (to interface MPT-HC);
identifies Radio LAG;
identifies Ethernet LAG.
The connectors have different colours depending on the associated
slots state:
White: a connector able to accept a cross-connection and has no active cross-
connection yet;
Green: a connector able to accept a cross-connection and already has one
active cross-connection at least;
Blue: a connector not able to accept a cross-connection.


3JK Edition 1.00
3.6.2 Connectors [cont.]
After a cross-connection creation between the points, their state will

change and a line will be drawn between the two cross-connected
points.


3JK Edition 1.00
3.6.3 Graphical Area

This area contains a panel and various components representing NE cross-connectable slots (or
connectors). The operator can directly edit with the mouse this graphical area to visually create and
modify cross-connections between available connectors. Figure shows an example of ongoing cross-
connections configuration.
Some steps would differ depending on cross-connection types.

3JK Edition 1.00
3.6.4 Buttons
At the bottom in the menu there are four buttons:

Apply: will apply changes (if any) to NE. After theyve been applied it will
update graphical state by performing a refresh; if the operation completes
without errors the sub-sequent refresh wont produce any visual change (in
other words, the state of the NE will be consistent with what is shown in the
GUI) anyway, clicking on Apply button will show a progress dialog;
Refresh: reloads the data from the NE and update the graphical state; any
modification performed and not applied will be lost;
Close: closes the cross-connection view, and return to the caller
(JusmMainView), any modification performed and not applied will be lost;
Help: opens the Help On Line.


3JK Edition 1.00
3.6.5 Segregated port view
From the Cross Connection view by pressing Alt+W the Segregated Port
view opens.

In the default configuration all the slots and Ethernet ports in Core unit are cross-connectedable each
other (all the slots/ports are not segregated).
To go back to the Cross Connection View press Alt+W.

3JK Edition 1.00
3.6.6 How to segregate slots or ports
Double click on a slot icon or an Ethernet port icon and select the
slots/ports that can be connected (this means that the not selected
slots/ports cannot be connected; they are segregated).
Example: with a double click on the icon of Slot#5 RADIO figure opens.
To segregate Slot#5 RADIO from Ethernet ports#2, #3, #4, #5 in the

Core unit, click on the relevant square to remove the check mark.


3JK Edition 1.00
3.6.6 How to segregate slots or ports [cont.]
By clicking OK the Segregated Port view opens, which now shows (with
dashed lines) the segregated ports.

With the mouse pointer on a dashed line the following message will appear: "Dashed lines mean that
these ports cannot be cross-connected".

3JK Edition 1.00
3.6.7 How to create a cross-connection
A cross-connection between two points is performed by:

Moving the mouse pointer on the source slot;
Press the left button and, while keeping button pressed, move mouse pointer
onto destination slot;
Release the left button.


3JK Edition 1.00
3.6.7 How to create a cross-connection [cont.]
Cross-connections Example

If the action involves two cross-connectable slots, a dialog will appear allowing the operator to setup a cross-
connection. Looking at figure, it is possible to see different aspects of configuration created by the operator:
Slot#8 PDH is cross-connected to Slot#5 radio ODU300, to Slot#4 MPT-ACC and to Ethernet Port#1;
Slot#4 MPT-ACC is cross-connected to Ethernet Port#1;
Slot#5 RADIO (and Slot#6 RADIO) are cross-connected to Ethernet Port#2;
Slot#3 MPT-ACC is cross-connected to Slot#4 MPT-ACC;
Ethernet Port#3 PDH (blue) could not accept cross-connections;
Slot#3 and Slot#4 (green) could accept more cross-connections;
Slot#5 and Slot#6 are in 1+1 configuration.
Each connection line is coloured according to slots types it connects (as shown in Figure):
PDH-Radio connection: black line;
SDH-Radio connection: black line;
ATM-Radio connection: orange line;
PDH-Eth connection: blue line;
ATM-Eth connection: magenta line;
Radio-Radio connection: red line;
Radio-Eth line: green line.
These colours will be applied to the graphical area, when the operator releases the mouse button above cross-
connection destination slot.
Note: the ATM cross-connection lines have the following colours:
ATM-Radio connection: orange line;
ATM-Eth connection: magenta line.
In the types of cross-connections above Eth means "Ethernet User Port" or "Ethernet LAG" and Radio means "Radio
to interface ODU300" or "Radio LAG".

3JK Edition 1.00
3.6.8 Creation Dialogs
When connecting two linkable slots through a cross-connection, a dialog

will appear, close to the destination point. This dialog contains
connection information, depending on start- and end-point of
connection itself. Each cross-connection has different parameters and
required data and information will depend on ongoing cross-connecting.
Dialog boxes can ask for specific Flow Ids through a set of checkboxes,
a field to fill-in external (incoming) Flow Ids, Ethernet parameters
and so on. All the dialog boxes have a specific title describing the
building cross-connection; this states both slots numbers and types.
The Ok button will visually save the current modifications (this
means that data are graphically saved only, not sent to the NE!)
The Cancel button will graphically discard ongoing cross-connection,
keeping the previous graphical.


3JK Edition 1.00
3.6.9 Information Dialogs
By using the right-click button, the operator can gain information about
the graphical representation of the cross-connections. This information
can be obtained on both connectors and connection lines. The operator
can perform different actions in the area, depending on target and
mouse-click type:
Connector, right click: a dialog with information about all selected
tributaries for that connector will appear.
Line, right click: a dialog with information about selected tributaries for that
line will appear.


3JK Edition 1.00
3.6.10 TDM Cross-Connections
The Cross-connections to be implemented are:

PDH to Radio/MPT-ACC
Radio to Radio or MPT-ACC to MPT-ACC or Radio to MPT-ACC or MPT-ACC to
Radio
Radio/MPT-ACC to Eth
PDH to Eth
In the types of cross-connections above Eth means "Ethernet User Port"
or "Ethernet LAG" and Radio means "Radio to interface ODU300" or
"Radio LAG".
After a cross-connection has been created, two cross-connected slots
are visually linked by a line: a line in the context of this application
represents a bundle of flows, which share same source and destination
entity.


3JK Edition 1.00
3.6.10.1 PDH to Radio/MPT-ACC
By dragging a connection between a PDH slot and a Radio slot or MPT-

ACC slot, the operator will see the configuration dialog in Figure.
PDH to Radio configuration dialog

Configuration parameters will ask to specify Flow ID number, as associated in PDH slot.

3JK Edition 1.00
3.6.10.1 PDH to Radio/MPT-ACC [cont.]
Once correctly completed the cross-connection configuration and

clicked on OK button, the operator can see a black line describing
the PDH to Radio cross-connection defined (see Figure).
Completed PDH to Radio cross-connection


3JK Edition 1.00
3.6.10.2 Radio to Radio
Radio to Radio or MPT-ACC to MPT-ACC or Radio to MPT-ACC or MPT-

ACC to Radio
By dragging a connection between two different radio slots, the operator can
see the configuration dialog in Figure.
To create other cross-connections drag other lines between the two radio
slots and repeat the operations.
Radio to Radio configuration dialog

Configuration parameters will introduce Flow ID number, as coming from remote radio signal, and a
parameter related to profile and TDM Clock Source. The operator has to fill in data to complete the
cross-connection configuration. The operator can use ranges and values.
To create in one shot several cross-connections the operator can use in the Flow Id field the notation
[n-m] to create all Flow IDs from n to m, both included. If the operator wants to specify different Flow
Ids grouping them without using ranges, commas can used to separate values.
For example:
by entering in the FlowId field 10-15 in one shot will be created all the cross connections from FlowId
10 to FlowId 15 (10 and 15 included);
by entering in the FlowId field 10, 200, 250 in one shot will be created the cross connections with
FlowId 10, FlowId 200 and FlowId 250.
It is not possible to merge the two solutions (ranges and values) by writing [n-m],[a-b], ... and so on.
Based on used input style (ranges or values), the operator will see two different confirmation dialogs.

3JK Edition 1.00
3.6.10.2 Radio to Radio [cont.]

clicked on OK button, the operator will see a red line describing the
Radio-Radio cross-connection defined (see Figure).
Completed Radio to Radio cross-connection


3JK Edition 1.00
3.6.10.3 Radio/MPT-ACC to Ethernet
By dragging a connection between a Radio slot and an Ethernet port,

the operator will see the configuration dialog in Figure.
Radio/MPT-ACC to Ethernet configuration dialog (ranges)


3JK Edition 1.00
3.6.10.3 Radio/MPT-ACC to Ethernet [cont.]
By using [n-m] the operator will specify adding all Flow IDs from n to m,
both included. If the operator wants to specify different Flow Ids
grouping them without using ranges, it can use commas to separate
values as shown in figure.
Radio/MPT-ACC to Ethernet configuration dialog (values)

It is not possible to merge the two solutions (ranges and values) by writing [n-m],[a-b], and so on.

3JK Edition 1.00
3.6.10.3 Radio/MPT-ACC to Ethernet [cont.]

clicked on OK button, the operator will see a green line describing
the Radio/MPT-ACC to Ethernet cross-connection defined).
Completed Radio/MPT-ACC to Ethernet cross-connection


3JK Edition 1.00
3.6.10.4 PDH to Ethernet
By dragging a connection between a PDH slot and an Ethernet port, the

operator can see the configuration dialog in Figure.
PDH to Ethernet configuration dialog

To create other cross-connections drag other lines between the PDH slot and the Ethernet port and
repeat the operations.
Configuration parameters will introduce Flow ID number, as associated in PDH slot, and all parameters
related to such Flow ID. The operator has to put the correct MAC address to complete the cross-
connection configuration.

3JK Edition 1.00
3.6.10.4 PDH to Ethernet [cont.]

clicked on OK button, the operator will be able to see a blue line
describing the PDH to Ethernet cross-connection defined (see Figure).
Completed PDH to Ethernet cross-connection

Considering a connection to Ethernet ports, when a port reaches its full capacity, the operator will see
a specific report.

3JK Edition 1.00
3.6.11 Cross-Connections with TDM2Eth Profile
No protection
1+1 radio protection between NE B and C

In these types of cross-connections the destination MAC address of the adjacent NE (unicast address in
case of unprotected configurations, multicast address in case of protected configurations) must be
inserted during the cross-connection creation. In the figures of the current and next slide 3 examples
are given.

3JK Edition 1.00
3.6.11 Cross-Connections with TDM2Eth Profile [cont.]
1+1 EPS protection in NE A


3JK Edition 1.00
3.6.11 Cross-Connections with TDM2Eth Profile [cont.]
To assign the multicast MAC address

of a NE start from the unicast MAC
address and change a digit in the
first pair of digits in order to
generate an odd binary number:
example change the first pair of the
address from 00 to 01.

Note: The unicast MAC address of the NE is shown in the System Settings menu (Bridge Address).

3JK Edition 1.00
3.6.12 How to modify a TDM cross-connection
An existing cross-connection can be modified by double-clicking with

the left mouse button on its symbolic line.
Now from the screen you have to delete the cross-connections by
removing the check mark from the relevant Flow Id box and create
again a new cross-connections.


3JK Edition 1.00
3.6.12.1 PDH to Radio/MPT-ACC

In figure the operator is modifying a previously created cross-connection (in this case Slot#8 PDH and
Slot#5 radio): this action brings up a dialog almost like the creation one, but with some differences in
allowed actions:
previously assigned tributaries (400 to 405 in the example) are active and selected;
tributaries assigned to another cross-connection (406 to 431) are not active and not selected.

3JK Edition 1.00

ACC to Radio

The operator can click on a specific (red) line in order to modify connection parameters. With a double
click with the mouse on the connection line, the dialog window shown in Figure will appear.
Remove the check mark and create again a cross-connection.

3JK Edition 1.00
3.6.12.3 Radio/MPT-ACC to Ethernet

The operator can click on specific (green) line in order to modify connection parameters. With a double
click with the mouse on the connection line, the dialog window shown in Figure can be managed by the
operator.

3JK Edition 1.00
3.6.12.4 PDH to Ethernet

The operator can click on specific (blue) line in order to modify connection parameters. With a double
operator.

3JK Edition 1.00
3.6.13 SDH Cross-Connections

SDH to Radio/MPT-ACC
Radio to Radio or MPT-ACC to MPT-ACC or Radio to MPT-ACC or MPT-ACC to
Radio

entity.


3JK Edition 1.00
3.6.13.1 SDH to Radio/MPT-ACC
By dragging a connection between a SDH slot and a Radio slot or MPT-

ACC slot, the operator will see the configuration dialog in Figure.
The Flow ID is automatically recognized as associated to the SDH slot.


3JK Edition 1.00
3.6.13.1 SDH to Radio/MPT-ACC [cont.]

clicked on "OK" button, the operator will see a black line describing the
SDH to Radio cross-connection defined .


3JK Edition 1.00

ACC to Radio

By dragging a connection between two different Radio slots, the operator will see the configuration
dialog in figure.
To create other cross-connections drag other lines between the two radio slots and repeat the
operations.
Configuration parameters will introduce Flow ID number, as coming from remote radio signal, and the
profile. The operator has to fill in data to complete the cross-connection configuration.

3JK Edition 1.00
3.6.13.2 Radio to Radio [cont.]

Radio to Radio cross-connection defined.


3JK Edition 1.00
3.6.14 How to modify an SDH cross-connection

removing the check mark from the relevant Flow ID box and create


3JK Edition 1.00
3.6.14.1 SDH to Radio/MPT-ACC

In Figure, the operator is modifying a previously created cross-connection (in this case Slot#8 SDH and
Slot#4 MPT-ACC): this action brings up a dialog almost like the creation one, but with some differences
in allowed actions:
Previously assigned STM-1 (222 in the example) is active and selected;
In the example of the figure there is no other Flow ID and for this reason it is not possible to create
another cross-connection.
Select the Flows ID and click OK to remove the cross-connection, then click Apply.

3JK Edition 1.00

ACC to Radio


3JK Edition 1.00
3.6.15 ATM Cross-Connections

ASAP-Radio
Radio-Radio
Radio-Eth
ASAP-Eth
In the types of cross-connections above Eth means "Ethernet User Port"

or "Ethernet LAG" and Radio means "Radio to interface ODU300" or
"Radio LAG".
entity.


3JK Edition 1.00
3.6.15.1 ASAP Radio
By dragging a connection between an ASAP slot and a radio slot, the

operator will see the configuration dialog (ODU300) in Figure.

Configuration parameters will ask to:

select the ATM interface (this interface is the IMA group: from 1 to 8)
select the PW label
enter the VPI
assign the VLAN ID
enter the Destination MAC Address (only with MPT-HC or MPT-MC)
Note: The Traffic Descriptor is automatically created.
Note: ATM "Light" Cross-connection Provisioning

In this release when a cross-connection toward a radio direction with MPT is involved, the related
provisioning is performed in almost the same way as with ODU300, with the following main
differences:
MAC DA is also explicitly provisioned in the NE acting as TPE role
admission control, in terms of checking bandwidth required bt ATM PW flow against the available
bandwidth on radio interface, is never performed.

3JK Edition 1.00
3.6.15.1 ASAP Radio [cont.]
By dragging a connection between an ASAP slot and a radio slot, the

operator will see the configuration dialog (MPT-HC or MPT-MC) in
Figure.


3JK Edition 1.00
3.6.15.1 ASAP Radio [cont.]

clicked on OK button, the operator will see a black line describing
the ASAP-radio cross-connection defined (see Figure).


3JK Edition 1.00
3.6.15.2 Radio Radio
The ATM Radio-Radio Cross-connections can be implemented between

ODU300-ODU300, MPT-MPT but not between ODU300-MPT.
By dragging a connection between two different radio slots, the
operator will see the configuration dialog in Figure.
To create other cross-connections drag other lines between the two
radio slots and repeat the operations.


3JK Edition 1.00
3.6.15.2 Radio Radio [cont.]
The operator has to fill in data to complete the cross-connection

configuration.

Configuration parameters are:

select the Service: ATM or PW3
select the PW label
assign the VLAN ID
associate the Traffic Descriptor by clicking on Browse and selecting a Traffic Descriptor previously
created.
Note: an ATM PW is made up of two undirectional flows.

3JK Edition 1.00
3.6.15.2 Radio Radio [cont.]


3JK Edition 1.00
3.6.15.3 Radio Ethernet
By dragging a connection between a Radio slot and an Ethernet port,



select the Service: ATM or PW3
select the PW label
assign the VLAN ID
enter the Destination MAC address
associate the Traffic Descriptor by clicking on Browse and selecting a Traffic Descriptor previously
created.
Note: an ATM PW is made up of two undirectional flows.

3JK Edition 1.00
3.6.15.3 Radio Ethernet [cont.]

clicked on OK button, the operator will see a green line describing
the Radio-Ethernet cross-connection defined.


3JK Edition 1.00
3.6.15.4 ASAP Ethernet
By dragging a connection between an ASAP slot and an Ethernet port,

To create other cross-connections drag other lines between the ASAP
slot and the Ethernet port and repeat the operations.


select the ATM interface
select the PW label
enter the VPI
assign the VLAN ID
enter the Destination MAC address
Note: The Traffic Descriptor is automatically created.

The operator has to put the correct Destination MAC address to complete the cross-connection
configuration.

3JK Edition 1.00
3.6.15.4 ASAP Ethernet [cont.]

clicked on OK button, the operator will be able to see a green line
describing the ASAP-Ethernet cross-connection defined (see Figure).

Considering a connection to Ethernet ports, when a port reaches its full capacity, the operator will see
a specific report.

3JK Edition 1.00
3.6.16 How to modify an ATM cross-connection

removing the check mark from the relevant Flow Id box and create


3JK Edition 1.00
3.6.16.1 ASAP-Radio

In Figure the operator is modifying a previously created cross-connection: this action brings up a dialog
almost like the creation one:
Previously assigned tributaries (111 in the example) are active and selected;
Tributaries assigned to another cross-connection are not active and not selected.
Select the ATM interface and remove the check mark and create again a cross-connection.

3JK Edition 1.00
3.6.16.2 Radio-Radio

Select the ATM Service and remove the check mark and create again a cross-connection.

3JK Edition 1.00
3.6.16.3 Radio-Ethernet

The operator can click on specific (green) line in order to modify connection parameters. With a double
operator.
Select the ATM Service and remove the check mark and create again a cross-connection.

3JK Edition 1.00
3.6.16.4 ASAP-Ethernet

The operator can click on specific (blue) line in order to modify connection parameters. With a double
operator.
Select the ATM interface and remove the check mark and create again a cross-connection.

3JK Edition 1.00
3.6.17 LAG-LAG Cross-Connections
Two types of cross-connections can be implemented:

Ethernet LAG - Radio LAG cross-connections
Radio LAG - Radio LAG cross-connections


3JK Edition 1.00
3.6.17.1 Ethernet LAG - Radio LAG cross-connections
By dragging a connection between a Radio LAG icon and an Ethernet

LAG icon, the operator will see the configuration dialog in Figure.

Configuration parameters will introduce the Service (TDM or ATM), Flow ID number and all parameters
related to such Flow ID. The operator has to put the correct MAC address to complete the cross-
connection configuration.

3JK Edition 1.00
3.6.17.1 Ethernet LAG - Radio LAG cross-connections [cont.]

clicked on OK button, the operator will be able to see a green line
describing the Radio LAG to Ethernet LAG cross-connection defined.

To create other cross-connections drag other lines between the Radio LAG and the Ethernet LAG and
repeat the operations.

3JK Edition 1.00
3.6.17.2 Radio LAG - Radio LAG cross-connections
By dragging a connection between two different Radio LAG icons, the

operator will see the configuration dialog in Figure.

Configuration parameters will introduce the Service (TDM or ATM), Flow ID number, as coming from
remote radio signal, and a parameter related to profile and TDM Clock Source. The operator has to fill
in data to complete the cross-connection configuration. The operator can use ranges and values.
To create in one shot several cross-connections the operator can use in the Flow ID field the notation
[n-m] to create all Flow IDs from n to m, both included. If the operator wants to specify different Flow
IDs grouping them without using ranges, commas can used to separate values.
For example:
by entering in the FlowId field 10-15 in one shot will be created all the cross connections from FlowId
10 to FlowId 15 (10 and 15 included);
by entering in the FlowId field 10, 200, 250 in one shot will be created the cross connections with
FlowId 10, FlowId 200 and FlowId 250.
It is not possible to merge the two solutions (ranges and values) by writing [n-m],[a-b], ... and so on.

3JK Edition 1.00
3.6.17.2 Radio LAG - Radio LAG cross-connections [cont.]

Radio LAG to Radio LAG cross-connection defined .


3JK Edition 1.00
3.6.18 How to modify a LAG-LAG cross-connection

removing the check mark from the relevant Flow ID box and create


3JK Edition 1.00
3.6.18.1 Ethernet LAG to Radio LAG

In Figure, the operator is modifying a previously created cross-connection (in this case Radio LAG #2
SDH and Ethernet LAG #24): this action brings up a dialog almost like the creation one, but with some
differences in allowed actions:
Previously assigned Flow ID (654 in the example) is active and selected;
Select the Service and the Flows ID and click OK to remove the cross-connection, then click Apply.

3JK Edition 1.00
3.6.18.2 Radio LAG to Radio LAG
The operator can click on a specific (red) line in order to modify

connection parameters. With a double click with the mouse on the
connection line, the dialog window shown in Figure will appear.

Previously assigned Flow ID (654 in the example) is active and selected;

Select the Service and the Flows ID and click OK to remove the cross-connection, then click Apply.

3JK Edition 1.00
3.7 Menu AUX Cross Connections
Two types of AUX Cross-Connections can be implemented:

Local User Service Channel Cross-Connection
Service Channels Cross-connection in pass-through

Note: Cross-Connection towards MPT

In this release cross-connection of Service Channels towards a radio direction with MPT is not
supported.
The operator therefore will not have the possibility to select a radio direction with MPT for such
cross-connection.

3JK Edition 1.00
3.7.1 Local User Service Channel Cross-connection
The two local user 64 kbit/s Service Channels on the AUX peripheral
unit can be cross-connected to one radio link with one of the three
available radio Service Channels.

Note:
Before disabling a local user Service Channel interface, all Service Channel cross-connections
involving this interface must be removed.
Before disabling an Auxiliary or Radio peripheral, any Service Channel cross-connections involving this
peripheral must be removed.

3JK Edition 1.00
3.7.2 Service Channels Cross-connect. in pass-through
Independently of the presence of the Auxiliary peripheral unit, it is

always possible to cross-connect each individual radio Service Channel
with a radio Service Channel of another radio direction, without any
local termination.


3JK Edition 1.00
3.7.3 How to create an AUX cross-connection

1. Select in the New Cross-Connection area the firt Termination Point (this can be a local service
channel or a service channel in a radio link).
2. Select the second Termination Point as shown in the example in the figure.
Note: The cross-connections are bi-directional.
3. Click on Add. The new cross-connection will appear in the list (upper part of the screen as shown in
the next figure).
Note: Button Apply has not been implemented.

3JK Edition 1.00
3.7.3 How to create an AUX cross-connection [cont.]


3JK Edition 1.00
3.7.4 How to delete an AUX Cross Connection

1. Select the Cross-Connection to be deleted from the list (as shown in the figure).
2. Click on Delete.
Note: The multiple deletion of the Cross-Connection is not possible.
Note: Button Apply has not been implemented.

3JK Edition 1.00
3.8 Menu VLAN Configuration
Two different ways to manage the Ethernet traffic are allowed:

802.1D (MAC Address Bridge)
802.1Q (Virtual Bridge)


3JK Edition 1.00
3.8.1 802.1D

When the NE is configured in this mode (default configuration), the Ethernet traffic is switched
according to the destination MAC address without looking the VLAN.
The packets from the user Ethernet ports having the VLAN ID out the allowed range (0 and 2-4080) are
dropped. The packets having a VLAN ID already used for a TDM flow are accepted.

3JK Edition 1.00
3.8.2 802.1Q

When the NE is configured in this mode, the management of Ethernet traffic looking the VLAN is
enabled.
In this modality, one VLAN will be assigned to all Ethernet frames inside the MPR network.
WARNING: The VLAN ID values configurable must be in the range 2 - 4080. The VLAN IDs already
defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) cannot be used. The management
system prohibits the definition of VLAN ID already used. The VLAN ID must be different also from the
Flow Id associated to E1 tributaries not yet cross connected

3JK Edition 1.00
3.8.2 802.1Q
3.8.2.1 VLAN 1 Management
VLAN-ID 1 is automatically defined by the NE when the 802.1Q bridge

type is selected.
VLAN-ID 1 is shown to the operator, but it cannot be neither changed
nor deleted.
All the user Ethernet ports (enabled and disabled) and all the radio
ports are members of the VLAN 1.
In egress VLAN-ID 1 is always removed from all the ports.

New: to create a new VLAN (refer to VLAN table management)

Edit: to change the parameters of a VLAN (VLAN name, VLAN member ports, VLAN untagged ports in
egress).
Delete: to delete a VLAN-ID. It is possible to remove a VLAN-ID from the VLAN-ID table even if this
VLAN-ID has been already configured on one or more user ports as Port VLAN to be added in ingress to
untagged frames. As consequence, the VLAN-ID=1 and PRI=0 are added to the untagged frames received
on this port. Before applying this deletion, a confirmation of the operation is shown to the operator.
Export: to export the VLAN configuration in a file with extension CSV. The file can be stored in the PC
to be read later.
Filter: by inserting a name in the "Filter by Name" box and by clicking on Filter will be displayed in the
table only the VLAN, which name corresponds (totally or partially) to the name written in the "Filter by
Name" box.
Clear Filter: by clicking this button all the VLAN created in VLAN table will again appear.
Refresh: the VLAN table is updated.

3JK Edition 1.00
3.8.2 802.1Q
3.8.2.2 VLAN Table Management
To create a VLAN follow the following instructions.

1) VLAN ID field: Enter the VLAN ID (the configurable values must be in the range 2 - 4080)
N.B.: The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) cannot
be used.
2) VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.
N.B.: There is no check on unambiguity name.
3) VLAN Ports field: Select the ports members of this VLAN by putting a check mark on the relevant
check box. All the user Ethernet ports and all the Radio directions can be considered. Both enabled and
disabled user Ethernet ports (radio ports when declared are implicitly enabled) can be member of a
VLAN. This means that a disabled port can be configured as a member of a VLAN and a port already
member of a VLAN can be disabled continuing to be a member of the same VLAN.
4) Untagged Ports field: Select, among the ports belonging to this VLAN (members), the untagged ports
(in egress the VLAN will be removed from the frames). Only the user Ethernet ports, enabled and
disabled, are manageable. The VLAN cannot be removed from the radio ports (with the exception of
the VLAN 1).
N.B.: The VLAN-ID values allowed are in the range 2 - 4080. By default, for the VLAN IDs defined, all
the ports are members and the Untag flag is set to False, which means all the frames are transmitted
with Tag.
N.B.: Tagged frames
If one tagged packet with VLAN-ID X is received on a port which is not member of the VLAN-ID X, the
packet is dropped.

3JK Edition 1.00
3.8.2 802.1Q
3.8.2.2 VLAN Table Management [cont.]
In the following figure, as example, three VLANs have been created

(VLAN 2, 3 and 4).


3JK Edition 1.00
3.8.2 802.1Q
3.8.2.3 VLAN Table Management (with LAGs)
In the following figure the LAGs (previously created) are also shown:
Ethernet LAG #1 and Radio LAG #23.

N.B.: When an ODU300/MPT-HC or MPT-MC port which is member of a VLAN, is unconfigured, the
operation is denied stating that "Operation not permitted: the board <board no> is member of a static
VLAN". To unconfigure this board, the user must first navigate to VLAN Configuration window and
remove this port from the static VLAN.

3JK Edition 1.00
3.9 Menu Traffic Descriptors
This menu allows to create or to delete the traffic descriptors, that will
be associated to the ATM traffic at the ingress and/or at the egress.


3JK Edition 1.00
3.9 Menu Traffic Descriptors [cont.]
To create a Traffic Descriptor:

1. Select the domain: ATM (if in the NE the ASAP unit is present) or PWE3 (in the
repeater nodes or in the nodes, where an Ethernet termination is present)
2. Insert a label to identify the Traffic Descriptor
3. Configure the following parameters:
Service Category: CBR, UBR+ or UBR (rtVBR and nrtVBR are not managed)
Conformance Definition: CBR.1 (VBR.1, VBR.2, VBR.3 are not maneged)
4. Configure the following TD Parameters: PCR, CDVT, MDCR
5. Enable or disable the Policing. For each VP/VC it is possible to enable/disable a cell-
based ATM Policing, based on the related ingress ATM Traffic Descriptor. The default
configuration of ATM Policing is according to configured Service Category:
enabled for VP/VC having Service Category CBR;
disabled for VP/VC having Service Category UBR+ and UBR.
6. Click on Create
7. The already created Traffic Descriptor will appear in the List Traffic Descriptors
area.
To delete a Traffic Descriptor:
1. Select in the List Traffic Descriptors area the Traffic Descriptor to be deleted and
click on Delete.

Note: By clicking on Refresh the list of the Traffic Descriptors will be updated.
Note: The maximum number of ATM Traffic Descriptors configurable on a NE is given by 2 times the
max number of configurable VPs multiplied by max number of ASAP Cards that can be hosted: 2 (2
traffic Descriptors per circuit) x 128 (128 circuits max.) x 6 (6 ASAP units in the NE max.).

3JK Edition 1.00
3.9 Menu Traffic Descriptors [cont.]
The types of ATM Traffic Contract (that is the Service Category/

Conformance Definition pair) to be supported by MPR system and its
relation with Traffic Descriptor parameters is reported in the table
below.
Service Conform Traffic Descr Type Traffic Traffic Traffic

Category Def. Descr Descr Descr
Param1 Param2 Param3
cbr CBR.1 atmClpTransparentNoScr PCR CDVT -
(CLP=0+1)
ubr+ CBR.1 atmClpTransparentNoScr PCR CDVT MDCR > 0
(CLP=0+1) (CLP=0+1)
ubr CBR.1 atmClpTransparentNoScr PCR CDVT MDCR = 0
(CLP=0+1) (CLP=0+1)

Notes:
1. UBR+ Service Category is defined as an UBR Service Category with Traffic Descriptor Parameter 3
(MDCR) > 0
2. ATM Traffic Descriptor Parameters for VP/VC rates (PCR,SCR) are defined in terms of cell/second,
for CDVT the unit is microseconds, for MBS the unit is cells
3. Range for ATM Traffic Descriptor Parameters with VP/VC rates is 0 to the bandwidth of related
physical or logical ATM interface, range for CDVT is 0 to 40000 microseconds, range for MBS is 0 to
1000 cells.

3JK Edition 1.00
3.10 Menu Profile Management
After the Start Supervision, each time the operator performs the Show
Equipment action, the following Dialog screen is displayed after the
window with JUSM start-up message and before the window with
loading bar indicating JUSM start-up progress.
Login window
The operator has to insert the user name and related password: by
clicking on the Apply button, the parameters are sent to NE.

The default Operator Name is initial.

The default Password is adminadmin.
According to the operator authentication (correct couple username/password) managed by the NE, the
operator will be authorized or not to continue. If the login parameters are not correct, an error
message will be displayed, while the Login window is still open for a new attempt. After 3 consecutive
failed attempts the login procedure is closed and JUSM does not start.
On the contrary if the user name and password are correct, JUSM will be started and the operator will
be allowed to perform the actions according to the right related to his profile.
WARNING: The NE rejects usernames and passwords that do not meet the following rules:
Password length: the length must be not less than six (6) characters under any circumstances.
Moreover the password length must be not longer than 20 characters.
Password composition: the password can include full ASCII characters set (UPPER/lower case,
numeric and special characters).
Username length: the length must be not longer than 20 characters.
By clicking on the Cancel button, the login procedure is stopped and the JUSM does not start.

3JK Edition 1.00
3.10.1 User Profiles Management
If the operator right allows the profiles management, the operator can
perform some actions on the profiles.
Under Configuration menu, the Profiles Management menu displays
two items:
Users Management
Change Password
These items will be enabled according to the right of user profile
recognised at login.


3JK Edition 1.00
3.10.2 User Management
By clicking on Users Management the window displayed in the Figure

appears.
The operator can perform the following actions:
Create a new User by clicking on the Create button.
After the selection of a user in the table, its possible:
Delete an existing User (the Admin user cannot be deleted) by clicking on the
Delete button.
Change PW (by Administrator) by clicking on the Change PW button.

By clicking on the Cancel button the Profiles Management window closes.

By clicking on the Help button the help browser will display the help-on-line pages dedicated to this
function.

3JK Edition 1.00
3.10.3 How to Create a New User
By clicking on the Create button, the following window appears and

allows the user Administrator to create a new user.


3JK Edition 1.00
3.10.3 How to Create a New User [cont.]
The operator has to insert the parameters to define the new user and
his profile rights:
1. AdminPassword: the password of Administrator for confirmation and
validation.
2. UserName: the specific name to be assigned to the new User (if it exists,
the action will be failed).
3. Profile: the specific profile to be assigned to the new User.
4. Password: the specific password to be assigned to the new User.
5. Confirm Password: again the specific password to be assigned for
confirmation and validation.

The supported profiles are:

Administrator: full access also for security parameters
Operator: person in charge to operate at network level, not at radio side; dangerous operations that require NE reconfiguration
at radio site are not permitted including backup/restore and restart NE features; could change own password
CraftPerson: person in charge for installation and the maintenance at radio site; full access to NE but not for security
parameters, only for own password
Viewer: only to explore the NE
Supported operations by the profiles:

Administrator profile: All the NE parameters are accessible both in writing and reading mode. Also the management of user
accounts is allowed (create/delete user accounts and change of all passwords).
Operator profile: Full reading access to NE parameters. For writing mode the following parameters are allowed to change:
ATPC configuration (enabled, disabled)
Performance Monitoring management
start/stop CD

threshold tables configuration

reset

archiving (only for NMS system)

Supported for all the types of Performance Monitoring (Radio Hop/Link, E1, Received Power Levels, ....)
NTP protocol:
Enabled/Disabled

NTP main server address configuration

NTP spare server address configuration

CraftPerson profile: This operator has the same priviledges of the Administrator, but cannot manage the user accounts
Viewer profile: This operator can only read and can change his own password.
By clicking on Apply button, at first JUSM performs a syntax check of each field: if there are some errors, JUSM will display the
specific message and allows the operator to correct them. If all parameters are correct, all parameters are sent to NE; after to
have automatically closed the window, a message with result of the action will be displayed.
By clicking on Cancel button, the Create User window closes and no action will be performed.

3JK Edition 1.00
3.10.4 How to Delete a User
After the selection of a User in the Profile Table, by clicking on the

Delete button, at first a confirmation dialog (Figure Delete user
confirmation) will be displayed; then the window to confirm the
administrator password will be displayed (Figure Confirm
Administrator Password to Delete a User).
Delete user confirmation Confirm Administrator Password

to Delete a User

By clicking on the Apply button, a message with the result action will be displayed after to have closed
automatically the window above.
If the operator clicks on Cancel button the window will closes and no action is performed.

3JK Edition 1.00
3.10.5 Change the Password (by the Administrator)
The Administrator User can change the password of another user: select
the user in the Profile Table and then click on Change PW button. The
following dialog box is displayed:
Change Password of User by Admin
The admin has to insert his password and the new password for
selected user in the two text fields.

By clicking on Apply button, at first JUSM performs a syntax check of each field: if there are some
errors, JUSM will display the specific message and allows the operator to correct them. If all
parameters are correct, all parameters are sent to NE; after to have automatically closed the window,
a message with result of the action will be displayed.
By clicking on Cancel button, the window will be closed.

3JK Edition 1.00
3.10.6 Change Password (by the User)
If the operator wants to change his password, he has to select the

Change Password menu item.
The following dialog will be displayed:
Change User Password
The operator has to insert the current password and the new password
in the two text fields.

By clicking on Apply button, at first JUSM performs a syntax check of each field: if there are some
errors, JUSM will display the specific message and allows the operator to correct them. If all
parameters are correct, all parameters will be sent to NE; after to have automatically closed the
window, a message with result of the action will be displayed.
By clicking on Cancel button, the window closes.

3JK Edition 1.00
3.11 Ethernet Features Shell
The LAG can be created by CLI commands launched with the WebEML
from the menu Configuration > Ethernet Features Shell.


3JK Edition 1.00
3.11.1 Simple examples for LAG creation
Here below two examples of the CLI commands useful to create LAG.
Example 1 : Ethernet LAG with Ethernet User port 1 and 2

1. Create the LAG with index 1, Ethernet type, size 2 (2 user ports: max
allowed number) called mario
lag 1 create type ethernet name mario size 2
2. Add User port 1 of the Core unit (slot 1) with priority 128 (128 means that
the two ports have the same priority)
lag 1 port add 1/1 priority 128
3. Add User port 2 of the Core unit (slot 1) with priority 128
4. Enable the LAG
lag 1 enable true

In bold characters the keywords, in italic characters the variables.

N.B.: When from the WebEML is launched the CLI, the WebEML closes.
Note 1: To know if an MPT is grouped in a radio LAG, letter L is placed on the MPT icon on the
Equipment view, but in this view it not possible to see the association of a specific MPT to a specific
Radio LAG.
Note 2: To know if an Ethernet user port is grouped in an Ethernet LAG, in the CORE-E domain in the
Ethernet Physical Interface tab-panel the Settings tab-panel of the Ethernet port grouped in a LAG is
gray (no changes can be done), but it not possible to see the association of a specific User Ethernet
port to a specific Ethernet LAG.

3JK Edition 1.00
3.11.1 Simple examples for LAG creation [cont.]
Example 2: Radio LAG between port 1 on MPACC in slot 3 and port

2 on MPTACC in slot 4
1. Create the LAG with index 5, Radio type, size 2 (2 radio ports: max allowed
number), called paolo
lag 5 create type radio name paolo size 2
2. Add port 1 of the MPTACC in slot 3 with priority 128
3. Add port 2 of the MPTACC in slot 4 with priority 128
4. Enable the LAG
lag 5 enable true

In bold characters the keywords, in italic characters the variables.

N.B.: When from the WebEML is launched the CLI, the WebEML closes.
Note 1: To know if an MPT is grouped in a radio LAG, letter L is placed on the MPT icon on the
Equipment view, but in this view it not possible to see the association of a specific MPT to a specific
Radio LAG.
Note 2: To know if an Ethernet user port is grouped in an Ethernet LAG, in the CORE-E domain in the
Ethernet Physical Interface tab-panel the Settings tab-panel of the Ethernet port grouped in a LAG is
gray (no changes can be done), but it not possible to see the association of a specific User Ethernet
port to a specific Ethernet LAG.

3JK Edition 1.00
Blank Page


3JK Edition 1.00
4 Menu Diagnosis


3JK Edition 1.00
4 Menu Diagnosis
4.1 Menu Diagnosis
Menu Diagnosis is divided in:
Alarms
Log Browsing
Remote Inventory
Abnormal Condition List
Summary Block Diagram View
Current Configuration View
Performance Monitoring


3JK Edition 1.00
4 Menu Diagnosis
4.2 Alarms

Alarms Monitor is an application which allows to display and store the alarms of all the NEs requiring it.
Alarms Monitor can be also started by clicking on the Alarms Monitor button on Neto.

3JK Edition 1.00
4 Menu Diagnosis
4.2 Alarms [cont.]
On the left side of the application, below each NE, two global lists of
alarms are displayed:
CURRENT_ALARM shows all the equipment alarms currently present,
ALARM_LOG shows all the equipment alarms currently present and the
history of the alarms (i.e. cleared alarms).
Each global list has some default filters (5 filters for the
CURRENT_ALARM list and 8 filters for the ALARM_LOG list), as follows:
1) CRI contains all the alarms having a CRITICAL severity
2) MAJ contains all the alarms having a MAJOR severity
3) MIN contains all the alarms having a MINOR severity
4) WRG contains all the alarms having a WARNING severity
5) IND contains all the alarms having an INDETERMINATE severity
6) CLR contains all the alarms which are in the CLEARED state, that is, which
are no longer active (this filter is available within the list ALARM_LOG only).
For each list and for each filter, the number of active alarms is shown
inside brackets.
These two lists can be filtered using customized filters provided by
means of the menu Filters Add a Filter.

Note: When an alarm is no longer active it disappears from the current Global list and it is displayed in
the ALARM_LOG list as a cleared alarm.

3JK Edition 1.00
4 Menu Diagnosis
4.2 Alarms [cont.]
Single clicking on a filter or on a global list on the left part of the

screen shows up on the right side the relevant tab panel with all the
alarms.
At the top right, the field Synthesis shows the number of active alarms
for any severity.
The alarms have a different color according to their severity and their
state.
Red: CRITICAL alarm
Brown: MAJOR alarm
Yellow: MINOR alarm
Blue: WARNIG alarm
White: INDETERMINATE alarm (Note that the equipment has no alarm having
such severity)
Green: CLEARED alarm (alarm no longer active).

Note: when the application is opened for the first time, only the tab-panels of the two global lists are
displayed on the right part of the window.

3JK Edition 1.00
4 Menu Diagnosis
4.2 Alarms [cont.]
Within the tab-panel, each alarm is provided with the information

below.
Time & Date: date and time of the alarm. The format of date and time is
yyyy/mm/dd hh:mm:ss.
Probable cause: name of the probable cause of the alarm.
Alarm Type: alarm class (TRS = Transmission Alarm alarm not created inside
the equipment, but generated by a connected equipment or due to
transmission/propagation problems; EQUIPMENT: inside alarm of the
equipment).
Friendly Name: object of the equipment where the alarm occurred.
Severity: alarm severity.
Add Text: this is an additional text regarding the alarm.
Specific problem: for some alarms, additional information is provided about
the involved resource (for instance, when a threshold alarm is raised, it
states the specific threshold exceeded)


3JK Edition 1.00
4 Menu Diagnosis
4.2 Alarms [cont.]
Right-clicking on an alarm row opens the menu shown in the following

figure.

Navigate to USM: to navigate to the object involved with the selected alarm and to open the relevant
window. Note: this option is available in the CURRENT_ALARM global list and in the relevant filters
only.
Export Alarm: to create a file containing alarms data. Alarms have to be selected by means of the
menu Select All. Generated file formats are CSV, HTML, XML and PDF.
Print current view: it is possible to print the list of the alarms. The Print Dialog box is shown to
choose the printer and set Print range and Copies number.
Select All: to select all the alarm of the list for further use, e.g. to export alarms to a file.
Select None: to select no alarm.

3JK Edition 1.00
4 Menu Diagnosis
4.2 Alarms [cont.]
The Menu Bar provides the following menus:
File
Filters
Help


3JK Edition 1.00
4.2 Alarms
4.2.1 File Menu
Save Log for selected NE

This menu allows to save a file with one of the two global lists of each NE.
Select the global list of a specific NE, open the Save History menu for the
selected NE and enter filename and relevant directory in the opening
window.
Load Log to selected NE
By means of this menu it is possible to display the global list of a certain NE
previously saved.
Remove selected NE
By means of this menu an NE, selected in the list, can be removed.
Export Alarms
This menu allows to save a file with the alarms of the selected Log. Select
the log, select "Export Alarms" menu, choose the file format (CSV, HTML, HML
or PDF) and then assign the name of the file.


3JK Edition 1.00
4.2 Alarms
4.2.2 Filters Menu
The Menu Filters provides the following menus:
Close Filter
Add a Filter
Edit Selected Filter
Delete Selected Filter
Delete Filters
Save Filters As
Load Filters From


3JK Edition 1.00
4.2.2 Filters Menu
4.2.2.1 Close Filter ...
The Filter, currently open, is closed.


3JK Edition 1.00
4.2.2 Filters Menu
4.2.2.2 Add a Filter
This menus allows to create customized logs adding some new specific
filters. The windows which opens is shown below.

Filter Name field

Enter the filter name in the Filter Name field.
The filters can be created selecting one of the following fields (or more). To save the created filter click on the
Done pushbutton. (Clicking on the Cancel pushbutton clears the filter configuration). The created filter appears
on the left side of the application.
Scope field
Select APT (Current) to create a filter showing the current alarms only or select Log to create a filter for
current and cleared alarms.
The filter can be applied to all the NEs by selecting All or it can be applied to one or more NEs by selecting one
or more NEs using the mouse.
Alarm Type field
Select Alarm Type to create a filter for the selected type of alarm:
TRS = Transmission Alarm
EQUIPMENT = Equipment alarm
Perceived severity field
Select Perceived severity and then one or more severity levels and/or Cleared state to filter the alarm having
the selected severity levels.
Event Time field
Select Event Time and then enter the starting date (From) and the ending date (To) to filter the alarms created
during that specific time frame only.
Probable Cause field
Select Probable Cause and the choose a specific alarm (one or more) to filter these particular alarms only.
Resource field
Put a check mark on the Resource box and write the object name the alarms of which have to be filtered (if
required).

3JK Edition 1.00
4.2.2 Filters Menu
4.2.2.3 Edit Selected Filter
A filter, previously created, can be modified.


3JK Edition 1.00
4.2.2 Filters Menu
4.2.2.4 Delete Selected Filter
A filter, previously created, can be deleted.


3JK Edition 1.00
4.2.2 Filters Menu
4.2.2.5 Delete Filters ...
When this menu is selected, the window shown below opens.

By means of this menu the filters previously created can be canceled. Default filters cannot be
canceled.
Select one specific NE (or more NEs) in the Scope column, select a specific filter (or more filters) in the
Filters column and then click on the Done Pushbutton.
Clicking on the Cancel pushbutton all the selections are cleared.

3JK Edition 1.00
4.2.2 Filters Menu
4.2.2.6 Save Filters As ...
A default filter, or a filter previously created by means of the Add a

filter menu can be saved to be used for some other LCTs.

Select in the Scope and Filters columns a specific filter to be saved, enter the filter name in the Name
field, select the Folder where to save the file relevant to filter and then click on the Done Pushbutton.
Clicking on the Cancel pushbutton all the selections are cleared.

3JK Edition 1.00
4.2.2 Filters Menu
4.2.2.7 Load Filters From ...
A filter previously saved can be loaded on the LCT by means of the

following menu.

Click on Browse to navigate and then choose the filter file to be loaded. The Scope and the Loaded
Filters columns will show respectively the NE list and the filters list made available by the selected
file.
Entering some characters in the Filters Prefix field and then clicking on the Done pushbutton, the
inserted characters are attached before the names of the Loaded Filters. For instance entering <Vim>,
the names of the filters change from APT to VimAPT.

3JK Edition 1.00
4.2 Alarms
4.2.3 Help Menu
This menu shows the Product Version.


3JK Edition 1.00
4 Menu Diagnosis
4.3 Log Browsing
In the Diagnosis pull-down menu select the Log Browsing option.
The Software Trace Log option is reserved to the Alcatel-Lucent technicians.
The Event Log option opens the Event Log browser application.


3JK Edition 1.00
4.3 Log Browsing
4.3.1 Event Log Browser
Event Log Browser is an application which allows to display all the

events occurred in the NE. An event is meant to be:
a configuration change
a change of the value
of an attribute
an automatic switchover
a manual operation carried
out by the operator.

The following information is provided for each event:

Time: date and time of occurrence of the event. The format is week day/month/day hh:mm:ss.
Reference Time (CEST) year.
Notification ID: a unique identifier for the event.
Explanation: a statement built with the event log data to explain what the event represents.

3JK Edition 1.00
4.3 Log Browsing
4.3.1 Event Log Browser [cont.]
The Menu Bar provides the following menus:
File
Help


3JK Edition 1.00
4.3.1.1 File Menu
The Menu File makes available the following menus:

Refresh Tables
Export
Print
Exit
Refresh Tables
By means of this menu the event log is refreshed.
A refresh may be executed as well clicking on the relevant pushbutton below
the menu bar.


3JK Edition 1.00
4.3.1.1 File Menu [cont.]
Export
This menu allows to export the alarm table as a file.
The file can have the HTML, CSV, PDF or XML format. The file can store all
the events (All entries) or only those selected by means of the pointer of the
mouse (Selection).
The Export may be executed as well clicking on the relevant pushbutton
below the menu bar.


3JK Edition 1.00
4.3.1.1 File Menu [cont.]
Print
It is possible to print the event list (all or just the selected ones). The Print
Dialog box shows up allowing to choose the printer and set print range and
number of copies.
The print may be executed as well clicking on the relevant pushbutton below
the menu bar.


3JK Edition 1.00
4.3.1.2 Help Menu
This menu shows the Product Version.


3JK Edition 1.00
4 Menu Diagnosis
4.4 Remote Inventory
This screen is a read-only screen, which shows all the information on

the equipment.


3JK Edition 1.00
4 Menu Diagnosis
4.5 Abnormal Condition List
The Abnormal Condition List option in the Diagnosis menu displays all
the abnormal conditions currently active in the NE.
An abnormal condition is generated each time a non usual condition is
present in the NE, detected automatically (i.e. automatic Tx mute) or
as consequence of management systems operation (i.e. force switching,
loopbacks, manual Tx mute).

The list of the events which cause an abnormal condition:

Forced switch (EPS, RPS, TPS)
Lockout (EPS, RPS, TPS)
Loopback activation
Local radio Tx mute (manual)
Adaptive Modulation in normal mode

3JK Edition 1.00
4 Menu Diagnosis
4.6 Summary Block Diagram View
The Summary Block Diagram View of the Diagnosis menu displays a

global logical view (strictly related to the physical implementation)
highlighting a synthesis of all the alarms and statuses present in the
system.


3JK Edition 1.00
4.6.1 Main Block diagram view
The Figure shows an example of the Main block diagram view.

Each block has its Alarm indicator (coloured ball icon) that shows the alarm status (different colors according to the alarm
severity).
N.B.: The Core-E has 2 alarm indicators in case of Core-E protection (as shown in figure) and only 1 alarm indicator (the ball
icon on the left side) in case of unprotected configuration.
In the Main view the current configuration of the MSS is shown, with the equipped units (PDH or SDH or Radio or MPT-ACC, with
the created LAG), with the protection schemes and with the cross-connections implemented between the different units and the
different Ethernet ports, if any.
Note 1: The connection line between Slot #5 and Slot #6 in figure means that the two ports of the two units are involved in a
protection scheme.
Note 2: The connection square between Slot #3 and Slot #4 in figure means that the SDHACC units are involved in a EPS
protection scheme.
Note 3: Different icons are used to identify Radio LAG or Ethernet LAG. In figure LAG #4 is a Radio LAG, LAG #1 is an Ethernet
LAG.
Note 4: An Ethernet User port involved in an Ethernet LAG disappears from the CORE-E area (in figure port #1 and #2 are grouped
in Ethernet LAG#1. Port #5 and #6 are not shown because are optional and have not been configured.
On the RADIO/MPT-ACC slot icon there is the symbol because on this unit a loopback can be activated, the symbol
because it is also possible to activate a Performance monitoring and/or the Ethernet traffic counters. If these symbols are green,
it means that the loopback is active or the Perfomance monitoring/Ethernet Counters have been activated.
By double clicking on an object it s possible to navigate to specific views. In detail:
by double clicking on the Alarm indicator the relevant active alarm is displayed
by double clicking on the Abnormal Condition List box, it is possible to navigate to the Abnormal Condition List menu;
by double clicking on the TMN Local Interface box, it is possible to navigate to the TMN view in the Core-E unit;
by double clicking on a PDH slot icon, it is possible to navigate to the secondary view for the PDH unit;
by double clicking on a Radio slot icon, it is possible to navigate to the secondary view for the Radio unit;
by double clicking on an MPT-ACC slot icon, it is possible to navigate to the secondary view for the MPT-ACC unit.
by double clicking on a Protection switch the relevant configuration is displayed;
by double clicking on a Loopback the relevant configuration is displayed.
The Refresh button will close all secondary windows, updating the main view one, and re-opening all previously opened
secondary windows, with updated content views.
All diagrams are automatically refreshed. According to following figures, bold light green lines update according to the actually
NE working way; alarm icons update as well.
The green line is the current active path.

3JK Edition 1.00
4.6.2 PDH unit secondary view
Depending on the configuration, different diagrams are shown to the

operator, describing the actual NE status and working mode.
1+0 block diagram (PDH unit) (without Core-E protection)

Performance monitoring icons ( ) are shown in green whenever a PM is active.

By double clicking on the Performance Monitoring icon ( ) the navigation to the Performance
Monitoring tool starts.

3JK Edition 1.00
4.6.2 PDH unit secondary view [cont.]
1+0 block diagram (PDH unit) (with Core-E protection)


3JK Edition 1.00
1+1 block diagram (PDH units) (without Core-E protection)


3JK Edition 1.00
1+1 block diagram (PDH units) (with Core-E protection)


3JK Edition 1.00
4.6.3 SDH unit secondary view

1+0 block diagram (SDH unit) (without Core-E protection)

Performance monitoring icons ( ) are are not supported.

3JK Edition 1.00
4.6.3 SDH unit secondary view [cont.]
1+0 block diagram (SDH unit) (with Core-E protection)


3JK Edition 1.00
1+1 block diagram (SDH units) (without Core-E protection)


3JK Edition 1.00
1+1 block diagram (SDH units) (with Core-E protection)


3JK Edition 1.00
4.6.4 Radio unit secondary view (ODU300)

1+0 block diagram (Radio unit) (without Core-E protection)

Loopback icons ( ) are shown in green colour ( ) whenever a loopback is active.

Ethernet Counters icon ( ) is shown in green whenever the counter has been activated.
By double clicking on the Loopback icon, on the PM icon or on the Ethernet Counters icon the
navigation to the relevant menus starts.
The switch blocks are updated according to the signal path, following light green-coloured line.

3JK Edition 1.00
4.6.4 Radio unit secondary view (ODU300) [cont.]
1+0 block diagram (Radio unit) (with Core-E protection)


3JK Edition 1.00
1+1 FD block diagram (Radio units) (without Core-E protection)


3JK Edition 1.00
1+1 FD block diagram (Radio units) (with Core-E protection)


3JK Edition 1.00
1+1 Hot Standby block diagram (Radio units) (without Core-E protection)


3JK Edition 1.00
1+1 Hot Standby block diagram (Radio units) (with Core-E protection)


3JK Edition 1.00
4.6.5 MPT-ACC unit secondary view (MPT-HC)

1+0 block diagram (MPT-ACC unit) (without Core-E protection)



3JK Edition 1.00
4.6.5 MPT-ACC unit secondary view (MPT-HC) [cont.]
1+0 block diagram (MPT-ACC unit) (with Core-E protection)


3JK Edition 1.00
1+1 FD block diagram (MPT-ACC units) (without Core-E protection)


3JK Edition 1.00
1+1 FD block diagram (MPT-ACC units) (with Core-E protection)


3JK Edition 1.00
1+1 Hot Standby block diagram (MPT-ACC units) (without Core-E

protection)


3JK Edition 1.00
1+1 Hot Standby block diagram (MPT-ACC units) (with Core-E protection)


3JK Edition 1.00
4.6.6 MPT-ACC unit secondary view (MPT-MC)

1+0 block diagram (MPT-ACC unit) (without Core-E protection)



3JK Edition 1.00
4.6.6 MPT-ACC unit secondary view (MPT-MC) [cont.]
1+0 block diagram (MPT-ACC unit) (with Core protection)


3JK Edition 1.00
1+1 Hot Standby block diagram (MPT-ACC units) (without Core protection)


3JK Edition 1.00
1+1 Hot Standby block diagram (MPT-ACC units) (with Core protection)


3JK Edition 1.00
4 Menu Diagnosis
4.7 Current Configuration View

This view is a read-only screen, which shows the current configuration of the NE.

3JK Edition 1.00
5 Menu Supervision


3JK Edition 1.00
5 Menu Supervision
5.1 Menu Supervision
Menu Supervision is divided in:
Access State
Restart NE
MIB Management
SW Licence


3JK Edition 1.00
5 Menu Supervision
5.2 Access State
The NE can be managed by the OS or by the Craft Terminal. To control

the competition of the OS and the CT, a Local Access Control (LAC) is
available.
If the LAC is access denied, it means that the OS manages the NE and
the CT is not allowed to modify the NE configuration (it can only
read). In the view, the icon with a key symbol has a circular shape.
If the LAC is granted, it means that the CT is allowed to manage the
NE. In the view, the icon with a key symbol has a rectangular shape.
If the LAC is requested, it means that the CT has requested a
permission from the OS and is waiting for a replay.
However, the OS does continue to provide a certain number of services.
These services include:
Alarm reception and processing,
Performance processing,
Switching back to the OS access state.
The access state of an NE can be modified from two types of views.


3JK Edition 1.00
5.2 Access State
5.2.1 Requested (Switching OS <-> CT access state)
Select the Supervision pull down menu. Then select the Requested
option from the Access State cascading menu.
If the OS does not answer in a predefined time, it is assumed that the
NE is in the Craft access state and can be managed by a Craft Terminal.


3JK Edition 1.00
5.2 Access State
5.2.2 OS (Switching CT access state <-> OS)
Select the Supervision pull down menu. Then from the Access State
cascading menu select the OS option.
The NE is now managed by the OS.

N.B.The key symbol icon on the management states of the NE view indicates whether the NE is
managed by a craft terminal or by the OS.
N.B. Local Craft Terminal access is denied on recovery phase after a loss of communication of the NE.
When the communication with the NE is lost, the OS automatically recovers the communication and
forces the state existing before the loss of communication (therefore, Craft Terminal access can be
denied or granted).

3JK Edition 1.00
5 Menu Supervision
5.3 Restart NE
The Restart operation is a software reset and can be executed in

normal traffic conditions.
From the Supervision cascading menu, select the Restart NE option.
A dialogue box opens.
Click the Yes button to confirm the restart NE operation
Click the No button to abort the restart NE operation.

WARNING: After the activation of the Restart NE Command (or after the pressing of the HW reset
push-button) the supervision of the local NE and the remote NEs is lost.

3JK Edition 1.00
5 Menu Supervision
5.4 MIB Management
It is divided in:
Backup
Restore
Remove file


3JK Edition 1.00
5.4 MIB Management
5.4.1 Backup
This menu allows to save on the CT the NE configuration.

To backup the configuration write the filename in the File Name field
and press Save.
Confirm the backup operation by clicking Yes to start the operation.
When the backup is completed in the upper part appears the list of the
previously created backups.

Warning: The backup file name must not include the following characters: space, &, /.
The file name contains always the version as prefix (example: "V020100_", corresponding to version
V2.1.0; "V030000_", corresponding to version V3.0.0). This prefix is inserted automatically by the SW,
when the MIB back-up file is created, and is used automatically by the SW, when the MIB restore
mustbe performed.
Note: There is one default repository folder of MIB back-up files for all NEs having the same SWP-
release.
The folder name is "backup", and is under the path where you have performed the Local copy of
WebEML(Jusm/CT).
This folder is automatically selected when you perform any of the commands of the MIB managerment
menu.

3JK Edition 1.00
5.4 MIB Management
5.4.2 Restore
This menu allows to download to the NE a previously created backup.

Select one of the backups to be downloaded in the upper part and press
Open.
Confirm the restore operation by clicking Yes to start the operation.
When the restore is completed a message appears asking to activate
the restored file. Click on Yes.


3JK Edition 1.00
5.4 MIB Management
5.4.3 Remove file
This menu allows to remove from the list of the backups one particular
backup.
To remove a backup select the backup file in the upper part and press
Remove file.
Confirm the operation by clicking Yes to start the operation.
By pressing Refresh the list of backups in the upper part of the screen is
updated.


3JK Edition 1.00
5 Menu Supervision
5.5 SW Licence
In this screen the following fields are present.

RMU Serial Number: in this read-only
field appears the Serial Number of
the Flash Card.
License String: in this read-only field
appears the type of the license
written in the Flash Card.
License Key: this field is used to
upgrade the license. To upgrade the
license copy in this field the code of
the new license and click on Apply.

The Refresh button activates a new reading of the read-only fields.

3JK Edition 1.00
Blank Page


3JK Edition 1.00
6 Tab-panel Equipment


3JK Edition 1.00
6.1 Tab-pabel equipment

The ODU300 is identified by a number indicating the slot number in the MSS, where the Modem unit is
installed.
The MPT-HC or MPT-MC is identified by two digits:
the first digit indicating the slot number in the MSS, where the MPT Access unit is installed,
the second digit indicating the enabled Ethernet port in the MPT Access unit (from 1 to 4).
NB: The icon of the MPT-HC or MPT-MC will appear only if the MPT Access unit has been configured in
the MSS and one port (from 1 to 4) has been enabled.

3JK Edition 1.00
6.2 Starting From Scratch
When the equipment configuration panel is open starting from a scratched NE,
the operator will see the panel in figure below. The Resource Tree area
contains a list of empty slots that have to be configured.
Icon is used to identify an empty slot.

To configure a card:
Select a slot.
Click on Settings panel.
Select the unit type in the Equipment type profile.
Click on Apply.

3JK Edition 1.00
6.3 Tab panels in the Resource Detail Area
For every unit there are 3 tab-panels:
Alarms
Settings
Remote Inventory


3JK Edition 1.00
6.3.1 Alarms tab-panel
The Alarms tab panel provides the fault management, which checks the
current state of alarms related to the selected object.
The alarm tab panel has one row for each possible alarm, but only rows
related to the active alarms are highlighted. When the alarm disappears
it is automatically cleared in the screen.
By putting a tick in the Include alarms from sub-nodes box the alarms
currently active in the sub-nodes of the object will also appear.
For every alarm the following information is given:
Severity: the severity associated to the alarm and assigned in the Alarm
Profile
Event Time: the time of the generation of the alarm
Entity: the entity involved in the alarm
Probable Cause: the probable cause of the alarm
Managed Object Class: the class of the alarm.


3JK Edition 1.00
6.3.2 Settings tab-panel
In the Setting tab-panel the following fields are present:
Equipment Type
Alarm Profile
Protection Type Configuration
Protection Type Configuration with MPT Access unit
Protection Type Configuration with STM-1 units


3JK Edition 1.00
6.3.2.1 Equipment Type
The operator must set for all the slots the expected equipment type.
The list box shows the expected equipment type (P32E1DS1 or MD300) for slot
3 to 8;
Select the unit type in the equipment type profile and click Apply.


3JK Edition 1.00
6.3.2.1 Equipment Type [cont.]
Core-E unit configuration

Port #5 and port #6 of the Core-E can be configured in 2 ways:
to be used as optical/electrical GigaEthernet interface for Ethernet traffic (by
installing the optional SFP)
to be used to connect an MPT-HC
Select the option (SFP/MPT-HC) and click on Apply.


3JK Edition 1.00
MPT Access unit configuration

In the Setting tab-panel one or two of the four Ethernet ports (to be
connected to the MPT-HC or MPT-MC) must be enabled as shown in figure.

Select as Usage MPT-HC or MPT-MC (in 2 ports max) and click on Apply.
N.B.: Port#1 and Port#2 are electrical Ethernet ports and Port#3 and Port#4 are optical Ethernet ports.

3JK Edition 1.00
STM-1 unit configuration

The Settings tab-panel of the STM-1 unit is shown below.
Select the optical SFP (SFP-O) or the electrical SFP (SFP-E) installed on the
STM-1 ports (SFP#1 and/or SFP#2) and click Apply.


3JK Edition 1.00
6.3.2.2 Alarm Profile
This function relates to an alarm severity profile to be assigned to a

selected object (implemented in MSS object, in Local TMN Ethernet
interface and in the Radio object).


3JK Edition 1.00
6.3.2.3 Protection Type (P32E1DS1 & MD300)
This function allows the operator to configure the NE protection type.

This function is shown selecting slots 3 to 8 only.
After the equipment selection, protection type list box is filled with
allowed protection types list (the content depends on expected
equipment configured):
If it is configured as P32E1DS1, allowed protection types are 1+0 and 1+1
EPS;
If it is configured as MD300, allowed protection types are 1+0, 1+1 HSB
and 1+1 FD.
If the operator selects a protection type equal to received one, apply
button is disabled.
If operator selects a protection type different from received one, apply
button is enabled.
If slot is in protection mode (received protection type different from
1+0): apply button related to expected-equipment is disabled
(equipment changing is allowed in 1+0 configuration only).

N.B.: For slots 1 and 2 (reserved to Main and Spare Core-E boards), protection type is configured by the
system, according to equipped Core-E board.

3JK Edition 1.00
6.3.2.3 Protection Type (P32E1DS1 & MD300) [cont.]
Protection Example

Configuring a 1+1 protected board, if peer board is not configured, the CT will be in charge of applying
such configuration to un-configured peer board, before creating protection in MIB.
If the user applies a new expected protection type, both tree view and configuration panel are
reloaded and updated. With a configured 1+1 protection, involved slots are bounded by light green
lines.

3JK Edition 1.00
6.3.2.4 Protection Type with MPT Access unit
To configure the protection scheme select the MPT.

In the example MPT-HC#72: connected to Port#2 of the MPT Access unit in Slot#7.
Choose in the Protect Port field one the ports available in the list. As protection can be also used an
MPT connected to the same MPT Access unit.
Choose the suitable Protection Type (1+1 FD or 1+1 HSB) and click on Apply.

3JK Edition 1.00
6.3.2.4 Protection Type with MPT Access unit [cont.]

After the configuration in the screen will appear the two jointed MPT-HC.

3JK Edition 1.00
6.3.2.5 Protection Type Configuration with STM-1 units
To configure the protection select 1+1 EPS in the Protection Type field
and click Apply.

N.B.: The field Protection Type appear only when the 2 STM-1 units have the same configuration (only
with SFP-O, not with SFP-E).

3JK Edition 1.00
6.3.3 Remote Inventory tab-panel
The Remote Inventory feature stores information used to identify all

product components.
The whole information related to selected equipment type can be read,
if available, in the remote inventory panel, inside the Resource Detail
area. Remote inventory data wont be available for levels that do not
have remote inventory itself, as IDU Ch#1 or IDU Ch#0.


3JK Edition 1.00
Blank Page


3JK Edition 1.00
7 Tab-panel Protection Schemes


3JK Edition 1.00
7.1 General
The 1+1 protection schemes implemented are:
Equipment protection: EPS protection in Tx and Rx sides (this protection

scheme can be implemented for all the unit types: Modem unit, PDH unit and
Core-E unit)
Rx Radio protection: RPS Hitless Switch in Rx side (available for the Radio
unit only)
HSB protection: Hot Stand-by protection (available for the Radio unit only)
FD protection: Frequency Diversity protection (available for the Radio unit
only)
Synchronization protection: This protection scheme will appear, if in the
synchronization tab panel the Primary Source and the Secondary Source have
been selected or the NE has been configured as Master with Free Running
mode.

Note 1: For the pair of Core-E units (slot 1 and 2) the only protection type is the Equipment
Protection.
Note 2: For the pair of Radio units or MPT Access units the protection type are the Equipment
Protection, Radio Protection and HSB Protection or FD protection.
Note 3: For the pair of PDH units the only protection type is the Equipment Protection.
Note 4: For the pair of SDH units the only protection type is the Equipment Protection.

3JK Edition 1.00
7.1 General [cont.]
Protection scheme screen

To see the current position of the switches enter the menu Diagnosis Summary Block Diagram View
and click on the icon of the equipped units.

3JK Edition 1.00
7.2 EPS Management
The Equipment Protection Management is performed by selecting the

Equipment Protection tree element.
This window allows a complete view of all NE resource involved in the
EPS protection.
The tab-panels are:
Protection Schema Parameters
Commands


3JK Edition 1.00
7.2 EPS Management
7.2.1 Protection Schema Parameters
The tab-panel Schema Parameters displays the parameters that can

be modify.
The parameters are:
Protection Type: this parameter is defined at creation time and it is read
only. The supported type is: 1+1, e.g. a working channel (Main) is protected
by a protecting channel (Spare).
Restoration Criteria: it defines if automatic restoration from protecting to
protected channel is allowed (revertive mode) or inhibited (not revertive
mode). The operator choice for Operation Type will be applied by clicking
on Apply button.

Note: The Core-E protection type is Not-Revertive and cannot be changed. The PDH/SDH protection
type is Not-Revertive and cannot be changed.
Note: In case of 1+1 HSB-EPS, the restoration criteia are always greyed out. No changes can be done
separately for 1+1 HSB-EPS. The restoration criteria selected for HSB-TPS will be applied to EPS
autoatically.

3JK Edition 1.00
7.2 EPS Management
7.2.2 Commands
To enter the Commands menu click on the Spare #0 element in the

Tree view or on the Main #1 element.
The operator by the Craft Terminal can modify the state of the switch
through commands Lockout, Forced and Manual. Select the suitable
command and click on Apply.
Lockout has higher priority than Forced: the activation forces in service
Channel 1 (default channel), independently of the possible active
alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation
of this command forces in service Channel 0, independently of the
possible active alarms. This command activates signaling ABN.
Automatic Switch is the normal operation condition: the position of
the switch depends on the commands generated by the logic.
Manual has the lowest priority: it is performed only if there are no
alarms that can activate an automatic switch. It cannot be performed if
Lockout or Forced commands are already activated. If this command is
active, it will be removed by an incoming alarm. This command does
not activate signaling ABN.

Note:
On the Main#1 channel the only available commands are Manual and Forced (only Forced for the
Core-E protection).
On the Spare#0 channel the only available commands are Manual and Lockout (only Lockout for the
Core-E protection.
Warning: All the commands are not error free.
Note: The Forced command for channel 1 is equivalent to the Lockout command for the channel 0.
In both case, the result is that the relevant channel protection path is forced to standby status.
Command priority list
Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
N.B. To release a previously activated command select None and click on Apply.
Warning for Core-E protection in Stacking Configuration with 3 Nes

If the Static Lag Criteria has not been enabled in the System Settings menu, after a Forced command
to restore the correct operation the Lockout command has to be entered.

3JK Edition 1.00
7.3 RPS Management
The Radio Protection Management is performed by selecting the Rx

Radio Protection element tree.
This window allows a complete view of all NE resource involved in a
RPS protection.
The tab-panels are:
Commands


3JK Edition 1.00
7.3 RPS Management
The tab-panel Protection Schema Parameters displays the

parameters that can be modify.
The Schema Parameters are:
Protection Type field: defines the protection schema architecture: 1+1
hitless;
Operation Type field: the possible values are revertive (automatic
restoration allowed) or notRevertive (automatic restoration Inhibited).


3JK Edition 1.00
7.3 RPS Management
7.3.2 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view
or on the Main #1 element.
The operator by the Craft Terminal can modify the state of the switch through
commands Lockout, Forced and Manual. Select the suitable command and
click on Apply.
Lockout has higher priority than Forced: the activation forces in service
Channel 1 (default channel), independently of the possible active alarms. This
command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation of this
command forces in service Channel 0, independently of the possible active
alarms. This command activates signaling ABN.
Automatic Switch is the normal operation condition: the position of the switch
depends on the commands generated by the logic.
Manual has the lowest priority: it is performed only if there are no alarms that
can activate an automatic switch. It cannot be performed if Lockout or Forced
commands are already activated. If this command is active, it will be removed
by an incoming alarm. This command does not activate signaling ABN. The
Manual command can be activated only if the two channels are aligned.

Note:
On the Main#1 channel the only available commands are Manual and Forced.
On the Spare#0 channel the only available commands are Manual and Lockout.
The Manual command can be activated only if the two channels are aligned.
Note: The Forced command for channel 1 is equivalent to the Lockout command for the channel
0. In both case, the result is that the relevant channel protection path is forced to standby status.
Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4

3JK Edition 1.00
7.4 HSB Protection Management
The Transmission Protection Management is performed by selecting the

HSB Protection element tree.
This window allows a complete view of all NE resource involved in the
protection.
The tab-panels are:
Commands


3JK Edition 1.00
The tab-panel Protection Schema Parameters displays the

parameters that can be modify.
Protection Type: this parameter is defined at creation time and it is read
only. The supported type are: 1+1 (onePlusOne) ,e.g. a working element is
protected by one protecting unit.
Operation type: it defines if automatic restoration from protecting to
protected unit is allowed (revertive mode) or inhibited (not revertive mode).
The operator choice for Operation Type will be applied clicking on Apply
button.


3JK Edition 1.00
7.4.2 Commands
To enter the Commands menu click on the Spare #0 element or on the

Main #1 element in the Tree view.
The operator by the Craft Terminal can modify the state of the switch
through commands Lockout, Forced and Manual. Select the suitable
command and click on Apply.
Lockout has higher priority than Forced: the activation connects to the
antenna Transmitter 1 (default transmitter), independently of the
possible active alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation
of this command connects to the antenna Transmitter 0, independently
of the possible active alarms. This command activates signaling ABN.
Automatic Switch is the normal operation condition: the position of
the switch depends on the commands generated by the logic.
Manual has the lowest priority: it is performed only if there are no
alarms that can activate an automatic switch. It cannot be performed if
Lockout or Forced commands are already activated. If this command is
active, it will be removed by an incoming alarm. This command does
not activate signaling ABN.

Note:
On the Main#1 channel the only available commands are Manual and Forced.
On the Spare#0 channel the only available commands are Manual and Lockout.
Warning: All the commands are not error free.
Note: The Forced command for channel 1 is equivalent to the Lockout command for the channel
0. In both case, the result is that the relevant channel protection path is forced to standby status.
Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4

3JK Edition 1.00
8 Tab-panel Synchronization


3JK Edition 1.00
8.1 Menu Synchronization

Synchronization menu allows the operator to manage the synchronization features.

Using Synchronization tab view (shown in the figure below) the operator can select and configure
synchronization source(s) for the equipment.
Together with Role and Restoration criteria, the operator can select Input and Output ports and
can discriminate between different possible Primary or Secondary sources, according to the Role.
The Resource list area shows the configuration summary describing current synchronization.
As for all other views, Synchronization contains Alarms tab as well and it allows discriminating
synchronization-specific alarms.
Each Network Element must have a reference Clock (NEC), which will be distributed to each board of
the NE. Such clock is a 25 MHz generated in the Core-E Module in the Clock Reference Unit (CRU)
function.
The NEC also provides a Sync Out port on the Core-E Module, which can be used to synchronize other
NEs.

3JK Edition 1.00
8.2 Synchronization Sources assignment
The physical interfaces to be assigned to Primary and Secondary

synchronization sources can be chosen among the following:
[1] Free Run Local Oscillator. Quality Level value is fixed to QL-SEC/EEC1
(G.812/G8262), the value of QL Priority is Master1 if the NEC is configured as
Master and Slave1 if the NEC is configured as Slave.
[2] Any E1 available at input traffic interfaces (the specific E1 port has to be
chosen). Default value for Quality Level is QL-SSU-A (G.812), the value of QL
Priority is Master1 if the NEC is configured as Master and Slave1 if the NEC is
configured as Slave.
[3] A specific synchronization signal available from the dedicated Sync-In
port, which can be configured according the following options:
a) 2.048 MHz, electrical levels according to G.703, clause 13;
b) 5 MHz, + 6 dBm into 50 ohm, sine-wave;
c) 10 MHz, + 6 dBm into 50 ohm, sine-wave;
d) 1.024 MHz, electrical levels according to G.703, clause 13 with the following
exceptions:
timing properly scaled from 2.048 MHz to 1.024 MHz.


3JK Edition 1.00
8.2 Synchronization Sources assignment [cont.]
[4] The Symbol Rate of the RX signal of any available Radio (the specific
Radio Port has to be chosen). When the SSM support is enabled the QL and QL
Priority are acquired from ESMC PDUs received on the specific radio
interface. When the SSM support is disabled the default value for Quality
Level is QL-SSU-A (G.812), the value of QL Priority is Master1 if the NEC is
configured as Master and Slave1 if the NEC is configured as Slave.


3JK Edition 1.00
[5] Any Synchronous Ethernet clock source available at enabled User Ethernet
traffic interfaces (both electrical and optical) configured in synchronous slave
operation mode (the specific User Ethernet port has to be chosen). From ITU-
T G.8261 point of view, the MSS is a Synchronous Ethernet equipment
equipped with a system clock (NEC) following the ITU-T G.8262
recommendation. A User Ethernet interface configured in synchronous
operation mode can work only at 1000 Mbit/s.
In the particular case of electrical User Ethernet interfaces, these interfaces
perform link auto negotiation to determine the master/slave role for clocks
delivery over the link. The clock slave role must be configured as part of auto
negotiation parameters in order to use the interface as Synchronous Ethernet
clock source input, either as Primary or Secondary. This check is performed
by WebEML/NMS but not by EC. The clock master role must be configured as
part of auto negotiation parameters in order to use the interface as
Synchronous Ethernet clock source output to distribute NEC to other
equipments. For Synchronous Ethernet clock sources from electrical User
Ethernet ports the Fail alarm will be raised when Loss of Synch (i.e. Ethernet
Link Down) will happen. For Synchronous Ethernet clock sources from optical
User Ethernet ports the Fail alarm will be raised when Loss of Optical signal
will happen.


3JK Edition 1.00
[6] Any STM1 available at SDH input traffic interfaces (the specific STM1 port
must be selected). Default value for Quality Level is QL-SSU-A (G.812), the
value of QL Priority is Master1 if the NEC is configured as Master and Slave1 if
the NEC is configured as Slave.
[7] None of the above, this means that no physical synchronization interface
is assigned to the synchronization clock source input. In case of failure of the
other clock source input the CRU enters the Holdover state.


3JK Edition 1.00
8.3 Synchronization sources assignment rules
Some rules have to be followed while assigning the Primary and

Secondary clock sources.
The NEC has to be defined (configured) as Master or Slave.
If a specific interface is chosen as Primary, it cannot be selected as
Secondary too.
If an E1/T1 is chosen to be Primary source, another E1/T1 coming from the
same peripheral cannot be selected as Secondary source and vice-versa.
If an MPT radio interface is chosen to be Primary source, another MPT radio
interface connected to the same MPT Access peripheral cannot be selected as
Secondary source and vice-versa.
If an STM1 is chosen to be Primary source, another STM1 coming from the
same peripheral cannot be selected as Secondary source and vice-versa.


3JK Edition 1.00
8.4 Allowed synchronization sources assignment

If Master:
The Restoration Mode must be chosen between Revertive and Non-Revertive;
The Primary clock source input must be chosen among 1), 2), 3), 5) or 6).
If the selected Master Primary clock source input is 1):
the Master Secondary clock source input doesn't need to be selected because
the Primary is never supposed to fail. If the selected Master Primary clock
source input is 2), 3), 5) or 6):
the Master Secondary clock source input must be selected among 1), 2), 3),
5), 6) or 7).
If Slave:
The Primary clock source input must be chosen among 3), 4) or 5). Slave
Primary clock source input is allowed to be 3) or 5) for full indoor
configuration and for Piling configuration.
The Secondary clock source input must be chosen among 1), 2), 3), 4), 5), 6)
or 7).


3JK Edition 1.00
8.5 SSM Summary Table
By pressing the SSM Summary button the SSM summary Table opens,
which shows the SSM status (enabled/disabled) of the interfaces
carrying the SSM messages.


3JK Edition 1.00
Blank Page


3JK Edition 1.00
9 Tab-panel Connections


3JK Edition 1.00
9 Tab-panel Connections
9.1 Menu Connections

This menu (available in the Main view) contains a summary table for all the implemented cross-
connections. This menu is shown in the figure.
In the Resource Detail Area are available two different functions usable to export and save cross-
connections data with different formats:
hardcopy (Send To Printer);
file (Export To File).

3JK Edition 1.00
10 PDH view for PDH domain


3JK Edition 1.00
10.1 PDH Unit configuration

This menu opens with double click on a PDH unit in the Equipment tab-panel.
In the Resource List Area is given the information related to the tributaries:
1) Port Number: port for a given channel and type of port
2) Signal Mode: type of frame (Framed/Unframed/Disabled)
3) Flow Id: identifier of the tributary for the cross-connection
4) Service Profile: possible profile to be associated to the tributary (TDM2TDM/TDM2Eth)
5) Payload: bytes of the payload (256)
6) ECID Tx: Emulated Circuit Identifier in Tx direction
7) ECID Rx: Emulated Circuit Identifier in Rx direction
8) TDM Clock source: type of the clock to be associated to the tributary (Adaptive/Differential)
Note: The selection of TDM clock source (clock recovery type) as to be common for all the E1
belonging to the same 32E1 PDH card, independently if the node timing has been enabled in the same
NE, it is possible to mix 32 E1 PDH card with E1s set in DCR and 32 E1 PDH card with E1s set in ACR.
Of course the NODE TIMING must be use properly
Note: Columns 5, 6, 7 and 8 are only available if the Service Profile is TDM2Eth.

3JK Edition 1.00
10.1 PDH Unit configuration [cont.]
For every E1 tributary two tab-panels are available:
Alarms tab-panel
Settings tab-panel


3JK Edition 1.00
10.1.1 Alarms tab-panel
The Alarms tab panel has one row for each possible alarm, but only
rows related to the active alarms are highlighted. When the alarm
disappears it is automatically cleared in the screen.
Profile


3JK Edition 1.00
This tab-panel performs all available functions for a tributary port. The
managed tributary types are: E1. To define the involved ports, the
interface selection in the tree view is first required; therefore the
selection of the desired tributary port in the tabular view enables the
Resource Detail list to show the available functions for the single one
resource.

Warning: to change something in the Settings tab-panel first changes the Signal Mode to Framed/Unframed. Then,
all the other fields can be changed.
In the Setting tab-panel there are the following fields:
Port Number: identifies the ports for a given interface and type of port (read-only fields)
Signal Mode. The possible values are:
Unframed for the unframed received signal
Framed for the collection of the performances at the input in Tx side and at the output in Rx side
Disabled
The current state can be modified selecting a different signal mode value and then click on the Apply button
to send the new value to NE.
Service Profile: The possible profiles are:
TDM2TDM
TDM2Eth
Flow Id: To implement cross-connections between line side and radio side each E1 tributary must be associated
to an identifier. Enter the Flow identifier value in the relevant field (possible values: 2 to 4080) and press Apply.
WARNING: The Flow Id must be unique in the MPR network.
Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if the Service Profile is
TDM2Eth.
Note: With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time Protocol
is used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP - Real Time Protocol is
used) or Adaptive (RTP is not used). In the unit it is not possible to have mixed configurations with service
profiles using RTP and other service profiles not using RTP.
Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure other E1 with service
profile TDM2Eth only with the Differential clock source (not with the Adaptive clock source). If the Adaptive
clock source is requested the E1 must be connected to another PDH unit.
Alarm profile: Not implemented now.
Buttons:
Apply: the configuration for the selected E1 tributary will become active
Apply to All: the configuration present in the screen will be applied to all the ports.
Help: by clicking on this button the operator calls the help on line.

3JK Edition 1.00
10.1.3 General information on Circuit Emulation
9500 MPR-E performs Circuit Emulation on PDH TDM flows, and then
transport those "TDM packets" mixed to native Ethernet frames.
The Circuit Emulation IWF (inter-working function) is according the
Metro Ethernet Forum implementation agreement known as MEF 8,
limited to the structure agnostic case.
MEF 8 emulated circuits is based on exchange of service parameters
between two CES IWFs at either end of the emulated circuit; if one of
those IWFs belong to the 9500 MPR-E the following parameters are
defined:
MAC addresses of the two IWFs
Payload size
ECID (2 different values may be used for each direction).
TDM clock source
clock recovery adaptive
clock recovery differential
VLAN (One Vlan is assigned to each bi-directional circuit emulated E1 flow)

It is suggested to set ECID Tx and ECID Rx with the same value of the Flow Id.
Two different cases of Circuit Emulation services are implemented:

1) TDM2TDM
2) TDM2ETH

3JK Edition 1.00
10.1.3 General information on Circuit Emulation[cont.]
TDM2TDM
Both the IWFs belong to 9500 MPR-E and the packets are not supposed
to go out the 9500 MPR-E network.
MAC addresses are determined as consequences of the cross connections.


3JK Edition 1.00
10.1.3 General information on Circuit Emulation[cont.]
TDM2ETH
Only one of the IWFs belongs to 9500 MPR-E and the packets are
supposed to go out the 9500 MPR-E network.
node where that TDM2ETH traffic goes through an user Ethernet port). In
such ETN the source address will be the node Mac address, the dest. mac
ECID: provisioned by ECT/NMS, 2 different values may be used for each
direction
TDM clock source will be provisioned by ECT/NMS: clock recovery adaptive,
Flow Id will be provisioned by ECT/NMS (One Vlan is assigned to each bi-


3JK Edition 1.00
10.1.4 Node Timing configuration
Click on the slot icon to access the Node Timing menu.

Node Timing: timing from the network clock as defined in G.8261. The enabling of the Node Timing is
applied to all E1s of the PDH unit.
By enabling the Node Timing the E1 streams in Rx side are retimed at the output with the network
element clock.

3JK Edition 1.00
10.2 Loopback
The functions described in this section allow to perform the test

operations by loopbacks.

Note: The loopbacks can be activated on the local NE only.
In the Resource List Area are listed all the loopbacks which can be performed. In the current software
version only the IF cable loopback is available.
In this area the following information is given:
Interface: number of the channel and type of the loopback
Direction: type of the loopback
Activation: activation status of a loopback (Active/Not Active)
Activation date: date of loopback activation
Timeout: timeout period, if has been set.

3JK Edition 1.00
10.2 Loopback
10.2.1 How to activate a loopback
Select the E1 tributary and select the loopback to be activated by

clicking on the relevant object in the Resource Tree Area or by
selecting the relevant row in the Resource List Area.
Select Active in the Activation field.
Click on Apply.
The Loopback is now ACTIVE (in the row in the Resource List Area the
Activation field of the loopback will change from Not Active to Active).

In the Timeout Period field a timeout period can be set for the loopback activation (max. 4 days).
At the end of this period the loopback will be automatically deactivated.

3JK Edition 1.00
10.2 Loopback
10.2.2 How to remove a loopback
Select the loopback to be removed by clicking on the relevant object in

the Resource Tree Area or by selecting the relevant row in the Resource
List Area.
Select Not Active in the Activation field.
Click on Apply.
The Loopback is now DEACTIVATED (in the row in the Resource List Area
the Activation field of the relevant loopback will change from Active to
Not Active).


3JK Edition 1.00
11 SDH view for SDH domain


3JK Edition 1.00
11.1 General information
The STM-1 unit supports up to 2 STM-1 interfaces.

The STM-1 signal is transported in a transparent way.
Link options include:
1+0 non-protected operation
1+1 EPS protection


3JK Edition 1.00
11.1.1 Protection
When the protection of the unit is required (1+1 EPS protection), two
STM-1 units must be installed.


3JK Edition 1.00
11.1.2 Tab-panels
Two tab-panels are present:

Alarms: shows the active alarms
Settings: allows to configure the STM-1 interface.


3JK Edition 1.00
11.2 Alarms
The alarm tab panel has one row for each possible alarm, but only rows
related to the active alarms are highlighted. When the alarm disappears
it is automatically cleared in the screen.
Profile


3JK Edition 1.00
11.3 Settings
This tab-panel allows to configure the STM-1 signal.

To configure the STM-1:

Put a check mark in the Port Status box to enable the STM-1.
Click on Apply.
Set the Auto Laser Shutdown: Enabled/Disabled ForcedOn/Disabled ForcedOff. This field will appear
only if the Settings tab-panel of the STM-1 unit the optical SFP has been selected.
Enable the J0, if required, by selecting one of the two modes (SixteenBytesFrame/OneRepeatedByte)
and in the Expected Receiving Value field enter the expected value. Note: byte J0 is only read, no
Regeneration section Termination is done.
Click on Apply on the left part.
Enter the Flow ID (range: 2 to 4080). Warning: the flow id must be unique in the MPR network.
Select the Jitter Buffer Depth: High/Low.
Select the TDM Clock Source: Differential/Node Timing.
Click on Apply on the right part.
N.B.: The Service profile is fixed to SDH2SDH: the STM-1 is packetized and is transmitted over an MPR
radio port.
N.B.: The Alarm Profile field is not supported in the current release.

3JK Edition 1.00
12 Radio view for Radio domain


3JK Edition 1.00
12.1 Radio domain menu
The Radio domain view allows the operator to manage the resources of
the radio transmission channel.
Three types of Outdoor Units are available:
ODU300 (up to 256 QAM/up to 56 MHz)
MPT-HC (High Capacity: up to 256 QAM/up to 56 MHz)
MPT-MC (Medium Capacity: up to 128 QAM/up to 28 MHz)
A Radio NE consists of one or two radio channels with a set of
functional blocks (tributary ports, radio ports etc).
This domain view consists of three areas.
Four tab panels are present in the Resource Detail Area.
The tab-panel Power Source is available only with the MPT Access unit
to interface MPT-HC or MPT-MC.

The areas of the domain view are:

Resource Tree Area: displays the radio ports sorted by channel number.
Resource List Area: displays tabular information about the selected resource in tree area.
Resource Detail Area: displays, through tab windows, the object s properties selected in list area.
This area enables to execute the available functions for involved resource.
The tab panels present in the Resource Detail Area are:
Alarms: shows the active alarms
Settings: configures the radio parameters
Measurements: performs the Tx and Rx power measurements.
Loopback: activates the loopbacks available with the equipment.
The tab-panel Power Source is available only with the MPT Access unit to interface MPT-HC or MPT-MC.

3JK Edition 1.00
12.2 Alarms
The Alarms tab panel has one row for each possible alarm, but only
rows related to the active alarms are highlighted. When the alarm
disappears it is automatically cleared in the screen.
Profile


3JK Edition 1.00
12.3 Settings
ODU300
MPT-HC
MPT-MC


3JK Edition 1.00
12.3 Settings
12.3.1 ODU300
To configure click in the Main view on the icon of the Modem unit to be
configured.
The Radio Main View opens.
The Radio Main View is divided in two parts:
on the left side is present the Direction # menu
on the right side is present the Channel #1 menu (for 1+0 configuration) and
Channel #1 and Channel #0 menus (for 1+1 configuration).

Warning: to configure the Radio unit first configure the Shifter and the Tx Frequency in the Frequency
field (in the Channel menu) and click on Apply. Then configure all the other parameters.

3JK Edition 1.00
12.3.1 ODU300
12.3.1.1 Direction area
This area is divided in 5 parts:
1) Mode
2) Link Identifier Configuration
3) PPP RF
4) Alarm Profile
5) Synchronization


3JK Edition 1.00
12.3.1 ODU300
12.3.1.1 Direction area [cont.]
1) Mode
Operation without the Adaptive Modulation
Select in the Mode field Presetting.
Select in the Reference Channel

Spacing field the suitable channel
spacing to be used.
Select in the Modulation field the

suitable Modulation scheme.
According to the selected Channel

Spacing and to the Modulation the
relevant capacity in the Capacity field
will appear.
To confirm the selection click on

Apply.

The operation mode can be without or with the Adaptive Modulation.

3JK Edition 1.00
12.3.1 ODU300
Operation with the Adaptive Modulation

Select in the Mode field Adaptive
Select in the Remote Modulation.
Switching Threshold
field how many dB the
switching thresholds Select in the Modulation Range
have to be moved from field the Modulation range (4/16
the default value (+4 QAM or 4/16/64 QAM) to be used
dB/-2 dB). The default
value is approx. 6 dB by the Adaptive Modulation.
below the 10-6 Rx
threshold (NB).
Select in the Reference Channel
The Current Modulation Spacing field the suitable channel
field is a read-only field, spacing.
which shows the current
used modulation. The
current modulation will The Reference Mode field is not
depend on the fading supported.
activity during the
propagation.
With a check mark in the To confirm the selection click on

Manual Operation box it is Apply.
possible to force a
modulation scheme by
selecting the scheme in the
Forced Modulation field.

The main idea behind Adaptive Modulation in Point to Point system is to adjust adaptively the
modulation as well as a range of other system parameters based on the near-instantaneous channel
quality information perceived by the receiver, which is fed back to the transmitter with the aid of a
feedback channel.
The switching between the modulation schemes is hitless and maintains the same RF channel
bandwidth.
The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB) without ATPC.
NB: Example: if the default switching threshold is -64 dBm by setting +4 dB the new value is -60 dBm
and by setting -2 dB the new value is -66 dBm.
Note: If the current Modulation scheme is 4 QAM, it not possible to force to 64 QAM, but first must be
forced to 16 QAM and then to 64 QAM. Also if the current Modulation is 64 QAM, to pass to 4 QAM first
must be forced to 16 QAM and then to 4 QAM.
Warning: with the up and down arrows, below the Forced Modulation field, it is possible to increase or
decrease the part of the screen relevant to the parameters of the Adaptive Modulation.

3JK Edition 1.00
12.3.1 ODU300
How to change the operation mode (from operation without

Adaptive Modulation to operation with Adaptive Modulation) in 1+1
HSB configuration
Follow the procedure:
1. Mute the 2 Transmitters
2. Remove the protection scheme: enter the Equipment tab-panel, select the
unit and remove the protection scheme
3. Enter the Main Radio unit setting tab-panel: set Mode Adaptive Modulation
4. Create again the protection scheme: enter the Equipment tab-panel,
select the unit and create the protection scheme (1+1 HSB)
5. Remove the muting from the Transmitters.


3JK Edition 1.00
12.3.1 ODU300
Channel Spacing Change

Capacity Up-Grade
When the admission control is enabled, this applies when the lowest modulation
scheme of the new channel spacing has a capacity which is larger than the one with
the old channel spacing. In this case all the pre-configured TDM or ATM PW will be
kept. The residual bandwidth for the lowest modulation scheme is recomputed.
When the admission control is disabled, this applies when the highest modulation
the old channel spac-ing. In this case all the pre-configured TDM or ATM PW will be
kept. The residual band-width for the highest modulation scheme is recomputed.
Capacity Down-Grade
When the admission control is enabled this applies when the lowest modulation
scheme of the new channel spacing has a capacity which is smaller than the one with
the old channel spacing. If all the pre-configured TDM or ATM PW stays in the
capacity associated to the lowest modulation scheme, they will be kept and the
residual bandwidth for the lowest modulation scheme is recomputed. If all the pre-
configured TDM or ATM PW cannot stay in the capacity associated to the lowest
modulation scheme, the change of channel spacing is rejected by CT/NMS.

A specific behavior must be followed when the Channel Spacing needs to be changed, to pre-serve any
pre-configured TDM or ATM PW. Consequently, two cases must be taken into account: Capacity Up-
grade and Capacity Down-Grade.

3JK Edition 1.00
12.3.1 ODU300
When the admission control is disabled this applies when the highest modulation
the old channel spac-ing. If all the pre-configured TDM or ATM PW stays in the
capacity associated to the highest modulation scheme, they will be kept and the
residual bandwidth for the highest mod-ulation scheme is recomputed. If all the pre-
configured TDM or ATM PW cannot stay in the capacity associated to the highest


3JK Edition 1.00
12.3.1 ODU300
Modulation Change
Capacity Up-Grade
This applies when the new modulation scheme has a capacity which is larger than the
old one.
When the admission control is enabled all the pre-configured TDM or ATM PW are
kept.
When the admission control is disabled all the pre-configured TDM or ATM PW will
work if the current capacity is able to support all of them, otherwise all pre-
configured TDM or ATM PW will not work.
Capacity Down-Grade
This applies when the new modulation scheme has a capacity which is smaller than
the old one.
When the admission control is enabled, since the admission control was performed
with the capacity of the lowest modulation scheme, all the pre-configured TDM or
ATM PW will be kept.
When the admission control is disabled, since the admission control was performed
with the capacity of the highest modulation scheme, all the pre-configured TDM or
ATM PW will be kept if the current capacity is able to support all of them, otherwise
all pre-configured TDM or ATM PW will be completely lost.

When the AM engine changes the modulation, the pre-configured TDM or ATM PW traffic must be
managed according to the behavior here after described. Two cases must be taken into account:
Capacity Up-grade and Capacity Down-Grade.

3JK Edition 1.00
12.3.1 ODU300
Modulation Working Mode Change

From Static to Adaptive
Adaptive Modulation can be enabled only if the ATPC is disabled.
When the Adaptive Modulation is enabled and Admission Control is enabled the
behavior is:
If all the pre-configured TDM or ATM PW in the Old Static Modem Profile, stay in the capacity
associated to the lowest Modulation Scheme, the request of change is accepted and the
residual bandwidth for the lowest Modulation Scheme is computed.
If all the pre-configured TDM or ATM PW cannot stay in the capacity associated to the lowest
Modulation Scheme, the request of change is rejected.
When the Adaptive Modulation is enabled and Admission Control is disabled all the
pre-con-figured TDM or ATM PW in the Old Static Modem Profile stay in the capacity
associated to the highest Modulation Scheme, then the request of change is always
accepted and the residual bandwidth for the highest Modulation Scheme is
computed.
From Adaptive to Static
When the Adaptive Modulation is disabled, if all the pre-configured TDM or ATM PW
in the Old Adaptive Modem Profile, stays in the capacity of the New Static Modem
Profile, the request is accepted and the residual bandwidth for new Static Modem
Profile will be computed. If all the pre-configured TDM or ATM PW cannot stay in the
capacity of the New Static Modem Profile, the request of change is rejected.

A specific behavior must be followed when it is needed to move from Adaptive Modulation to Static
Modulation or vice-versa, in order to preserve any pre-configured TDM or ATM PW. Two cases must be
taken into account: from Static to Adaptive Modulation and from Adaptive to Static Modulation. The
working mode changes, here below described, are generic. The changes cover both the change of the
modulation but with the same Channel Spacing and the change of the Channel Spacing.

3JK Edition 1.00
12.3.1 ODU300
2) Link Identifier
This part allows the operator to define the expected and sent identifier
values of parameters related to the link management and, if necessary,
modify them.
The operator choices will be sent to the NE by clicking on the related
Apply button.
If the Link Identifier is Enabled the following fields can be written:
Expected Identifier: this field is the link identifier expected at the receiving
NE
Sent Identifier: this field is the link identifier inserted on the transmitting
NE.


3JK Edition 1.00
12.3.1 ODU300
3) PPP RF
The PPP-RF interface is a communication interface based on the use

of an inframe RF proprietary 64 kbit/s channel. Through the PPP-RF
interface the NE can exchange management messages with a remote OS
(or Craft Terminal) station.
The PPP-RF channel can be Enabled or Disabled.
If enabled, in the Remote Address field will appear the IP address of
the remote connected NE.
In the Routing IP Protocol field enter the used IP protocol and in case
of OSPF protocol select also the associated OSPF area.


3JK Edition 1.00
12.3.1 ODU300
4) Alarm Profile
Not implemented in the current release.
5) Synchronization
Tick on Enable to enable the transmission of the SSM message over the
radio channel.


3JK Edition 1.00
12.3.1 ODU300
12.3.1.2 Channel area
1) Frequency
2) ATPC (this menu is alternative to RTPC menu)
3) Manual Transmit Power Control (this menu is alternative to ATPC menu)
4) Tx Mute
5) Alarm Profile


3JK Edition 1.00
12.3.1 ODU300
12.3.1.2 Channel area [cont.]
1) Frequency
The system can operate with different types of ODU according to the RF
band and to the channel arrangement. There are ODUs which can
manage only one shifter or several predefined shifters.
In the Shifter field select the suitable shifter.
In the Tx frequency field insert the suitable Tx frequency (the Rx
frequency is automatically calculated by using the inserted Tx
frequency and the shifter) and press push-button Apply.
By pressing the Data Help button the list of all the available ODUs with
the relevant P/N, shifter and Tx frequency will appear. The Data Help
table is usefull, if you are not connected to the ODU.


3JK Edition 1.00
12.3.1 ODU300
2) ATPC
The ATPC can be Enabled or Disabled.

The new value will be applied when the Apply button is pressed. If the
ATPC has been enabled, the ATPC Range and ATPC Rx Threshold
parameters must be filled.
ATPC Range
The Min Tx power and Max Tx power, regarding the Tx Range in the ATPC
management, can be written in the relevant field.
When the Apply button is pressed the new values will be applied.
ATPC Rx Threshold
The value of the low power threshold can be changed by writing the new
value in the field. When the Rx power is equal to this power the ATPC
algorithm starts to operate.

Note: the ATPC area is not present if the Adaptive Modulation has been selected.

3JK Edition 1.00
12.3.1 ODU300
3) Manual Transmit Power Control
Manual Transmit Power Control (without Adaptive Modulation)

If the ATPC is disabled the manual Tx Power field is present. For the Tx
Power range refer to the table.
In this field write the new value within the allowed transmitted power range.
The range is shown on the right side of Manual Transmit Power Control area.
Tx Power (with Adaptive Modulation)

The operator can modify only the 4 QAM field. In this field the operator has
to enter the constant power, which will be used with 4 QAM modulation. The
power range is shown on the right side and depends on the selected
reference mode.

Note: the same power value will be used by the 16 QAM and 64 QAM modulation schemes

3JK Edition 1.00
12.3.1 ODU300
4) Tx Mute
The information related to the transmitter status is shown in the Tx

Mute field (Off/Manual/Auto). To squelch the transmitter select Enable
and press Apply button.
The following indications will appear in the Tx Mute field:
Off: Transmitter not squelch
Manual: Transmitter squelched due to the manual operation
Auto: Transmitter squelched due to an automatic operation


3JK Edition 1.00
12.3.1 ODU300
5) Alarm Profile
By clicking on the icon the Alarm Severity Profile menu opens, which
allows to associate to the radio channel a specific alarm profile. Select
one Alarm Profile in the Profile Name list (4 alarm profiles are listed)
and click Apply. Tick the Show details check box to see the severity
associated to each alarm.


3JK Edition 1.00
12.3 Settings
12.3.2 MPT-HC
To configure click in the Main view on the icon of the MPT-HC or of the
MPT Access unit to be configured.
The Radio Main View has 3 tab-panels:
Power Source
Port ##1
Port ##2 (this tab-panel is present if in the MPT Access unit a second port has
been configured)

Warning: First configure the Port and then the Power Source. Pay attention to configure properly the
Power Source.

3JK Edition 1.00
12.3.2 MPT-HC
1) Mode
3) PPP RF
4) Alarm Profile
5) Synchronization


3JK Edition 1.00
12.3.2 MPT-HC
1) Mode
Operation without the Adaptive Modulation (1+0 MPT Access unit)
Select in the Reference Channel Spacing

field the suitable channel spacing to be
used (up to 56 MHz).
Select in the Modulation field the suitable

Modulation scheme (up to 256 QAM).
Select the Option ETSI mask: Current ETSI

mask or New ETSI mask
According to the selected Channel Spacing

and to the Modulation the relevant
capacity in the Capacity field will appear.
To confirm the selection click on Apply.


3JK Edition 1.00
12.3.2 MPT-HC
Operation without the Adaptive Modulation (1+1 MPT Access unit)






3JK Edition 1.00
12.3.2 MPT-HC
Operation with the Adaptive Modulation (1+0 MPT Access unit)

Choose in the Modulation.
Supported Modulation
field all the modulation
schemes to be used with Select in the Reference Channel
the Adaptive Spacing field the suitable channel
Modulation. The spacing.
modulation schemes
(from the lowest to the
highest scheme) must Select in the Modulation field the
be contiguous the lowest modulation scheme
(from QPSK) to be used by the
The Current Modulation Adaptive Modulation.
field is a read-only field,
used modulation. The Select in the Option field the
current modulation will spectral efficiency class to be set
depend on the fading as reference: Current ETSI mask or
activity during the New ETSI mask
propagation.

possible to force a

feedback channel.
bandwidth.
The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB/1+1 FD) Radio
configuration without ATPC).
Note: The Remote Switching Threshold is not supported.


3JK Edition 1.00
12.3.2 MPT-HC
Operation with the Adaptive Modulation (1+1 MPT Access unit)

modulation schemes
propagation.
With a check mark in the Select in the Driving MSE field the
Manual Operation box it is receiver to be used to drive the
possible to force a Adaptive Modulation engine
Forced Modulation field. To confirm the selection click on
Apply.
feedback channel.
bandwidth.


3JK Edition 1.00
12.3.2 MPT-HC

HSB configuration


3JK Edition 1.00
12.3.2 MPT-HC

Capacity Up-Grade
Capacity Down-Grade


3JK Edition 1.00
12.3.2 MPT-HC


3JK Edition 1.00
12.3.2 MPT-HC
Modulation Change
Capacity Up-Grade
old one.
kept.
Capacity Down-Grade
the old one.


3JK Edition 1.00
12.3.2 MPT-HC

behavior is:
computed.


3JK Edition 1.00
12.3.2 MPT-HC
2) Link Identifier
modify them.
Apply button.
NE
NE.

The "Link Identifier Mismatch" drops all the traffic.

3JK Edition 1.00
12.3.2 MPT-HC
3) PPP RF



3JK Edition 1.00
12.3.2 MPT-HC
4) Alarm Profile
5) Synchronization
radio channel.


3JK Edition 1.00
12.3.2 MPT-HC
1) Frequency
4) RSL Driving Criteria (only in 1+1 configuration without Adaptive

Modulation)
5) Tx Mute
6) Alarm Profile

Warning: To configure the unit first configure the Shifter and the Tx Frequency in the Frequency field
(in the Channel menu) and click on Apply. Then configure all the other parameters.

3JK Edition 1.00
12.3.2 MPT-HC
1) Frequency
In the Rx frequency field will appear the calculated Rx frequency, but
this frequency can be changed in +5 MHz range to implement the
Exotic shifter configuration, if required. Change the Rx frequency
and press Apply.
table is usefull, if you are not connected to the ODU.


3JK Edition 1.00
12.3.2 MPT-HC
2) ATPC

ATPC Range
ATPC Rx Threshold


3JK Edition 1.00
12.3.2 MPT-HC


The operator can modify only the Tx power relevant to the lowest modulation
scheme. In this field the operator has to enter the constant power, which will
be used with the lowest modulation.

Note: the same power value will be used by the other modulation schemes

3JK Edition 1.00
12.3.2 MPT-HC
4) RSL Driving Criteria
Select in the RSL Driving Criteria field the suitable value. In 1+1 FD and
HSB configurations both the transmitters can be driven by the lowest or
by the highest RSL values of the two remote demodulators.


3JK Edition 1.00
12.3.2 MPT-HC
5) Tx Mute



3JK Edition 1.00
12.3.2 MPT-HC
6) Alarm Profile


3JK Edition 1.00
12.3 Settings
12.3.3 MPT-MC
To configure click in the Main view on the icon of the MPT-MC or of the
MPT Access unit to be configured.
The Radio Main has 3 tab-panels:
Power Source
Port ##1
Port ##2 (this tab-panel is present if in the MPT Access unit a second port has
been configured)

Warning: First configure the Port and then the Power Source. The MPT-MC cannot support 1+1 FD.
The MPT-MC cannot support 1+1 FD.

3JK Edition 1.00
12.3.3 MPT-MC
1) Mode
3) PPP RF
4) Alarm Profile
5) Synchronization


3JK Edition 1.00
12.3.3 MPT-MC
1) Mode
Operation without the Adaptive Modulation






3JK Edition 1.00
12.3.3 MPT-MC
Operation with the Adaptive Modulation

modulation schemes
propagation.

possible to force a

feedback channel.
bandwidth.
Note: In 1+1 configuration the Driving MSE field is not supported.

Note: Example: if the current Modulation scheme is 4 QAM, it not possible to force to 64 QAM, but first
must be forced to 16 QAM and then to 64 QAM. Also if the current Modulation is 64 QAM, to pass to 4
QAM first must be forced to 16 QAM and then to 4 QAM.

3JK Edition 1.00
12.3.3 MPT-MC

HSB configuration


3JK Edition 1.00
12.3.3 MPT-MC

Capacity Up-Grade
Capacity Down-Grade


3JK Edition 1.00
12.3.3 MPT-MC


3JK Edition 1.00
12.3.3 MPT-MC
Modulation Change
Capacity Up-Grade
old one.
kept.
Capacity Down-Grade
the old one.


3JK Edition 1.00
12.3.3 MPT-MC

behavior is:
computed.


3JK Edition 1.00
12.3.3 MPT-MC
2) Link Identifier
modify them.
Apply button.
NE
NE.

The "Link Identifier Mismatch" drops all the traffic.

3JK Edition 1.00
12.3.3 MPT-MC
3) PPP RF



3JK Edition 1.00
12.3.3 MPT-MC
4) Alarm Profile
5) Synchronization
radio channel.


3JK Edition 1.00
12.3.3 MPT-MC
1) Frequency
4) RSL Driving Criteria (only in 1+1 configuration without Adaptive

Modulation)
5) Tx Mute
6) Alarm Profile

Note: The Channel #1 area is always present (in 1+0 and 1+1 configuration).
The Channel #0 area is present in 1+1 configuration only.
Warning: To configure the unit first configure the Shifter and the Tx Frequency in the Frequency field
(in the Channel menu) and click on Apply. Then configure all the other parameters.

3JK Edition 1.00
12.3.3 MPT-MC
1) Frequency
In the Rx frequency field will appear the calculated Rx frequency, but
this frequency can be changed in +5 MHz range to implement the
Exotic shifter configuration, if required. Change the Rx frequency
and press Apply.
table is usefull if you are not connected to the ODU.


3JK Edition 1.00
12.3.3 MPT-MC
2) ATPC

ATPC Range
ATPC Rx Threshold


3JK Edition 1.00
12.3.3 MPT-MC


The operator can modify only the Tx power relevant to the lowest modulation
scheme. In this field the operator has to enter the constant power, which will
be used with the lowest modulation.

Note: the same power value will be used by the other modulation schemes

3JK Edition 1.00
12.3.3 MPT-MC
4) RSL Driving Criteria
Select in the RSL Driving Criteria field the suitable value. In 1+1 FD and
HSB configurations both the transmitters can be driven by the lowest or
by the highest RSL values of the two remote demodulators.


3JK Edition 1.00
12.3.3 MPT-MC
5) Tx Mute



3JK Edition 1.00
12.3.3 MPT-MC
6) Alarm Profile


3JK Edition 1.00
12.4 Measurement
The Power Measurements capability is performed by means of the

Measurement tabbed panel.
The Measurement screen allows the operator to set initial parameters
for the required measurement.
"Measurement interval" fields allow the operator to set the time
duration of the measurement. The default is Days: 7, Hours: 0, Minutes:
0. A 7-day measurement interval is also the maximum allowed interval.
"Sample time" field is the period between two consecutive
measurement samples. The choice is among 2, 4, 6, 30, 60 sec.
The last section of the dialog is referred to an optional Log file.
By selecting Create File the log file is created and a default path and
name for this file is displayed to the operator. The file is stored in the
MPRE_CT_V00.07.08 directory.

Note: The file name must not include the following characters: \ ? : * < > |.

3JK Edition 1.00
12.4 Measurement [cont.]
The log file contains the sample value and records the measurement up
to a maximum dimension (7 days for a 2 s sample time).
By clicking on the "Start" button the screen "Power Measurement
Graphic" appears.
The Power Measurement Graphic is available only if the CT is connected
to the NE.
The Power Measurement Graphic screen shows the Tx and Rx
measurements related to the local and remote NE.
Through this screen the operator can see, in real time, the power
transmitted by the local and remote transmitter (Tx) and the power
received by the local and remote receiver (Rx).
The top graphic screen area shows the TX curves (local and remote),
while the bottom area shows the Rx curves (local and remote). Note
that the colors represent the linked end-point of the two NE; for
example, if the local TX is blue, the remote receiver will also have the
same color.


3JK Edition 1.00
The top of the screen offers all the characteristics present in the
current measurement:
Radio port: gives the symbolic name associated to the radio channel being
analyzed
Sample time: indicates the frequency used to send the measurement requests
to NE;
Start time: is the first request time;
Stop time: is the interval time selected in the previous parameters window,
added to the start time;
Time: is the current response time;
Log File: is the complete pathname of the file where the received values are
stored.


3JK Edition 1.00
By clicking on "Show details" box, on the left side of the Power Measurement
Graphic, a new table appears; this table shows the following relevant values of
the received and transmitted power:
Tx Local End
max Tx local value and date when this value was received for the first time.
min. Tx local value and its current date when this value was received for the first time.
current Tx local value and its current date.
Tx Far End
max Tx remote value and date when this value was received for the first time.
min. Tx remote value and its current date when this value was received for the first time.
current Tx remote value and its current date.
Rx Local End
max Rx local value and date when this value was received for the first time.
min. Rx local value and its current date when this value was received for the first time.
current Rx local value and its current date.
Rx Far End
max Rx remote value and date when this value was received for the first time.
min. Rx remote value and its current date when this value was received for the first time.
current Rx remote value and its current date.

Note: PTx and PRx levels software readings tolerance: PTx=Real Value 3dB; PRx=Real Value 5dB.
WARNING:
Radio analog transmitted power level (local ODU)
In case of ICP or Cable Loss alarms the value shown at management system is -99.8 dBm. In case of
mute status the value shown at management system is -100 dBm. If the power level read is out of
the allowed range, the value shown by the management system is -101 dBm.
Radio analog received power level (local ODU)
failure on reading the register containing the received power the value shown at management
system is -99.7 dBm. If the power level read is out of the allowed range, the value shown by the
management system is -101 dBm.
Radio analog transmitted power level (remote ODU)
In case of broken radio link the value shown at management system is -99.6 dBm. In case of mute
status the value shown at management system is -100 dBm. In case of failure on reading the
register containing the remote transmitted power the value shown at management system is -99.7
dBm. If the power level read is out of the allowed range, the value shown by the management
system is -101 dBm. In case of alarms on the remote NE on one of the two radio channels in HSB
configuration (typically ICP, Cable Loss, Crad Missing, Card Fail), the value shown by the
Radio analog received power level (remote ODU)
In case of failure on reading the register containing the remote received power the value shown at
management system is -99.7 dBm. If the power level read is out of the allowed range, the value
shown by the management system is -101 dBm. In case of alarms on the remote NE on one of the
two radio channels in HSB configuration (typically ICP, Cable Loss, Card Missing, Card Fail), the
value shown by the management system is -127 dBm.

3JK Edition 1.00
12.4 Measurement
12.4.1 How to read a Power Measurement file
Click on Read File field and press on the Select File button.
The directory of the CT automatically opens to navigate and get the
power measurement file.
Select the desired file and click the Open.
Click button Open on the right side of the Sample Time field.
The buttons in the lower part of the window allow to flow the graph
within the measurement interval.

N.B. As default the measurement files are stored in the MPRE_CT_V00.01.02 directory and have
extension .txt.
Note: The measurement file can be opened also with a standard text editor (e.g. WordPad). Go in the
directory where the txt files are stored and open the file. The measurements are shown in the tabular
mode.

3JK Edition 1.00
12.5 Loopback
The functions described in this section allow to perform the test

operations by loopbacks.
In the Resource List Area are listed all the loopbacks which can be
performed.
In the current software version the following loopbacks can be
implemented:
IF cable loopback with ODU300
Core-facing and Radio-facing loopbacks with MPT-HC and MPT-MC
In this area the following information is given:
1) Interface: the number of the channel and the type of the loopback
2) Direction: the type of the loopback
3) Activation: the activation status of a loopback (Active/Not Active)
4) Activation date: the date of loopback activation
5) Timeout: the timeout period, if has been set.

This domain view consists of the following areas:

Resource Tree Area: displays the object on which the loopbacks can be performed, sorted by
number.
Resource List Area: displays tabular information about the loopback supported by the resource
selected in the tree area.
Resource Detail Area: displays, through tabbed windows, the properties done in list area. This area
enable to perform the available functions for the involved resource.
N.B.: The loopbacks can be activated on the local NE only.

3JK Edition 1.00
12.5 Loopback [cont.]
Loopback with ODU300

In the figure is given the association of the loopback and the position in the block diagram of the
equipment provided by the Summary Block Diagram View option, available in the Diagnosis menu.

3JK Edition 1.00
12.5 Loopback [cont.]
Loopbacks with MPT-HC and MPT-MC

In the figure is given the association of the loopback and the position in the block diagram of the
equipment provided by the Summary Block Diagram View option, available in the Diagnosis menu.

3JK Edition 1.00
12.5 Loopback
12.5.1 How to activate a loopback
[1] This operation must be done only with the Modem unit connected
with ODU300. Before to activate the loopback mute the Transmitter.
Double click on the front panel of the Modem unit and enter the
Settings tab-panel.
[2] Select the loopback to be activated by clicking on the relevant
object in the Resource Tree Area or by selecting the relevant row in the
Resource List Area.
[3] Select Active in the Activation field.
[4] Click on Apply.
[5] The Loopback is now ACTIVE (in the row in the Resource List Area
the Activation field of the relevant loopback will change from Not
Active to Active).

Note: The loopback are active only on the cross-connections with TDM2TDM and TDM2Eth profiles.
Note: In the Timeout Period field a timeout period can be set for the loopback activation (max. 4
days). At the end of this period the loopback will be automatically deactivated.

3JK Edition 1.00
12.5 Loopback
12.5.2 How to remove a loopback
[1] Select the suitable loopback to be removed by clicking on the

relevant object in the Resource Tree Area or by selecting the relevant
row in the Resource List Area.
[2] Select Not Active in the Activation field.
[3] Click on Apply.
[4] The Loopback is now DEACTIVATED (in the row in the Resource List
Area the Activation field of the relevant loopback will change from
Active to Not Active).
[5] Remove the squelch of the local Transmitter.


3JK Edition 1.00
12.6 Power Source
This menu is available only with MPT-HC and MPT-MC and it refers to
the 2 different modes to power supply the MPT:
QMA
PFoE

Two Sources are available because the MPT Access unit can interface two MPT.
If the Type is Disabled no power supply is provided to the MPT.
After the power supply selection click on Apply.
N.B.: The Alarm Profile field is not supported.

3JK Edition 1.00
12.6 Power Source [cont.]
Mode 1 - QMA (only with MPT-HC)

This mode is the default mode.
In this mode the MPT-HC is power supplied with a dedicated coaxial cable
connected on the QMA connector on the front panel of the MPT Access unit.
Mode 2 - PFoE (Power Feed on Ethernet)

In this mode the MPT-HC or MPT-MC are power supplied by using the
electrical Ethernet cable.

Warning: Check the MPT Access card P/N before to provide power supply to the PFoE port. To check
the P/N use the Remote Inventory facility.
Warning: To implement this mode with MPT-HC the DC Extractor must be installed, near the MPT-HC,
to separate the Ethernet traffic and the power supply.
Warning: If you connect directly (without the DC Extractor) the MPT-HC with PFoE, you can cause
irreversible damages to the MPT-HC.

3JK Edition 1.00
13 ATM view for ATM DOMAIN


3JK Edition 1.00
13 ATM view for ATM DOMAIN
13.1 ATM view for ATM DOMAIN
The configuration of the ASAP unit is divided in four tab-panels:

E1 Layer
IMA Layer
ATM Layer
ATM PW Layer

Warning: Migrations to MPR-E 2.1.

All the ATM PW flows configured on the NE but not yet cross-connected must be deleted before
performing the download of the MPR-E 2.1 SW Package. Otherwise, with the MPR-E 2.1 SW Package,
later configuration related to these ATM PW flows can lead to incoerent DataBase contents.

3JK Edition 1.00
13.1.1 E1 Layer
ASAP E1 Layer view

This menu allows to configure the physical E1 layer.

To configure the E1 layer:
1. Select the E1 port# (from 1 to 16)
2. Select the Signal mode: Framed/Disabled
3. Select the Clock mode: node-timed/loop-timed.
4. Click on Apply.
Note: By clicking on Apply To All the same configuration will be applied to the 16 E1 ports.
Note: The line impedance is fixed to 75 ohm or 120 ohm.
Note: The Alarm Profile is not implemented in the current release.

3JK Edition 1.00
13.1.2 IMA Layer
ASAP IMA Layer view

In the ASAP unit max. 8 IMA groups can be created.

To configure an IMA group:
1. Select the IMA group (from #01 to #08).
2. Enter the Near End ID (this identifier will be written in the ATM cells of the IMA protocol).
3. Enter the Min number of links (this is the minimum numbers of working E1 links, with which the IMA
group is still operational).
4. Enter the Max Differential Delay (in ms) between the E1 streams of the IMA group.
5. Click on Apply in the IMA Group Parameters are.
6. Select the E1 streams, which will be associated to the IMA group, by putting a check mark in the
Add check box. Up to 16 E1 links can be associated to the same IMA group.
7. Click on Apply in the IMA Link Table area.
Note: When an E1 has to be removed from an IMA group it is necessary, before applying the operation,
to set the administrative status to down. In this case there is no affect on the traffic.
Note: The Administrative Status must be set to Up in the ATM Layer tab-panel.

3JK Edition 1.00
13.1.2 IMA Layer [cont.]
By clicking on the Monitor in the Link column in the IMA Link Table
area, the screen in Figure opens.

This screen is a read-only screen in which all the parameters regarding the E1 link are shown.

3JK Edition 1.00
13.1.2 IMA Layer [cont.]
By clicking on the IMA Group Monitoring the screen in Figure opens.

This screen is a read-only screen in which all the parameters regarding the IMA group are shown.

3JK Edition 1.00
13.1.3 ATM Layer
ATM Layer Configuration

VP Layer Configuration
VC Layer Configuration


3JK Edition 1.00
13.1.3 ATM Layer
13.1.3.1 ATM Layer Configuration
By clicking in the ATM # mode, as shown in Figure, the ATM Interface

type can be selected: UNI or NNI.
ATM Interface type

Each ATM interface (from #01 to #08) is an IMA group.

To activate an IMA group set the Admin Status to Up and click on Apply.

3JK Edition 1.00
13.1.3 ATM Layer
13.1.3.1 ATM Layer Configuration [cont.]
ASAP ATM Layer view


3JK Edition 1.00
13.1.3 ATM Layer
13.1.3.2 VP Layer Configuration
Create a VPI
To create a new VPI click on Create VPI. The next screen opens.


3JK Edition 1.00
13.1.3 ATM Layer
13.1.3.2 VP Layer Configuration [cont.]
The definition of a VP over an ATM i/f is performed by the

configuration the following parameters:
VPI: in the range 0 to the value configured for the ATM i/f ;
VP role: Not Logical (Connection end-point) or Logical (Termination end-

point).
Ingress and Egress Traffic Descriptors: For each VP it is possible to associate

its ingress and egress ATM Traffic Descriptors.
This applies in both cases of VP configured as Connection or Termination end-
point. In the latter case, the VP ATM Traffic Descriptor is used only to
characterize the available bandwidth for ATM Admission Control function.
Click on Browse (the next screen opens for the Ingress Traffic Descriptor) and
select the TD in the Select TD field and click on OK.

If the VP Role is configured as VP Connection end-point, then:

ATM PW Service will be done in VPC mode, that is transport of ATM traffic into Ethernet frames is
done by encapsulating all ATM cells (i.e. for all VCs transported by that VP) with the configured VPI
into the same Ethernet flow;
VP ATM Traffic Descriptor will be directly used to derive the traffic characteristic of the related ATM
PW Ethernet flow.
If the VP Role is configured as VP Termination end-point, then:
ATM PW service will be done in VCC mode, that is transport of ATM traffic into Ethernet frames is
done by encapsulating into the same Ethernet flow only the ATM cells belonging to the same VC (with
the configured VPI);
the VP configuration actually defines a "logical" ATM i/f, a specific VCI range can be configured by
NMS through SNMP interface for that VP (within the range previously configured for the ATM i/f); by
ECT instead, this parameter is not configurable (that is the default range for the ATM i/f range
applies);
VP ATM Traffic Descriptor is not used to derive the traffic characteristic of the related ATM PW
Ethernet flow(s) but only to define the available bandwidth for "logical" ATM i/f (in ordet to perform
ATM Admission Control at VC level);
ATM Policing and Shaping are not applicable at VP level (but instead are to be configured at VC
level).

3JK Edition 1.00
13.1.3 ATM Layer
The TD must be previously created in menu Configuration -> Traffic

Descriptors.
Ingress Policing: this field allows to configure the policing in Ingress.

Egress Shaping: this field is a read-only field. The shaping is automatically
assigned according to the Service Category.

The configuration of a Traffic Descriptor associated to a Logical VP must be:

Service Category = CBR
PCR = sum of PCR of its CBR type VCs and MDCR of its UBR+ type VCs
CDVT = don't care
Policing = don't care

3JK Edition 1.00
13.1.3 ATM Layer
Edit VPI
To modify a previously created VPI select the VPI from the Available VP list
and click Edit VPI.
Change the parameters and click on Apply.
Delete VPI
To delete a previously created VPI select the VPI from the Available VP list
and click Delete VPI.
For every created VP an ATM Admission Control is performed in order to
check that the resulting allocated bandwidth is less or equal to the
bandwidth available on the ATM i/f.
This applies in both cases of VP that is being configured as Connection or
Termination end-point.
In case the resulting allocated bandwidth is greater than the ATM i/f
available bandwidth, the VP definition cannot be performed and an error
indication is returned.

Note: The VPI can be modified only if it is not involved in cross-connection. Otherwise the cross-
connection must be deleted, the PWE3 must be deleted and the VPI set to "Not in service".
Note: The VPI can be deleted only if it is not involved in cross-connection. Otherwise the cross-
connection must be deleted, the PWE3 must be deleted and the VPI set to "Not in service".
Note: If the VP contains the VC, the VC must be removed.
Note: VP ATM Admission Control.

3JK Edition 1.00
13.1.3 ATM Layer
The allocated bandwidth is computed as the sum of the egress VP ATM Traffic
Descriptor parameters, according to the type of Traffic Contract (ATM Service
Category/Conformance Definition pair) reported in the below table:
Service Category Conformance Definition VP/VC Bandwidth

Cbr CBR.1 PCR
ubr+ CBR.1 MDCR (> 0)
ubr CBR.1 MDCR (= 0)
In case of VP that is being configured as Termination end-point, the egress VP

ATM Traffic Descriptor parameter defined in the above table is also defining
the available bandwidth for the related "logical" ATM i/f.


3JK Edition 1.00
13.1.3 ATM Layer
13.1.3.3 VC Layer Configuration
The VC Layer Management is used to define the characteristics of the

VCs transported over an already configured VP.
The VC Layer Configuration and relevant buttons are available only if a
VPI has been configured Logical as VP Role.
Create VCI
To create a VCI select the relevant VP in the Available VP list and click
on Create VCI. The next screen opens.


3JK Edition 1.00
13.1.3 ATM Layer
13.1.3.3 VC Layer Configuration [cont.]
The definition of a VC (over an already configured VP) is performed by

the configuration the following parameters:
VCI: in the range from 32 to the value configured for the underlaying logical
(VP) ATM interface
Ingress and Traffic Descriptor. For each VC it is possible to associate its
ingress and egress ATM Traffic Descriptors.
Click on Browse (the next screen opens for the Ingress Traffic Descriptor) and
select the TD in the Select TD field and click on OK.
The TD must be previously created in menu Configuration -> Traffic
Descriptors.
Ingress Policing: this field allows to configure the policing in Ingress.
Egress Shaping: this field is a read-only field. The shaping is automatically
assigned according to the Service Category.


3JK Edition 1.00
13.1.3 ATM Layer
13.1.3.3 VC Layer Configuration [cont.]
Edit VCI
To modify a previously created VCI select the VCI from the Available VC list
and click Edit VCI.
Change the parameters and click on Apply.
Delete VCI
To delete a previously created VCI select the VCI from the Available VC list
and click Delete VCI.
For every created VC an ATM Admission Control is performed in order to
check that the resulting allocated bandwidth is less or equal to the
bandwidth available on the underlying VP, that is the "logical" ATM i/f.
In case the resulting allocated bandwidth is greater than the "logical" ATM i/f
available bandwidth, the VC definition cannot be performed and an error
indication is returned.
The allocated bandwidth is computed as the sum of the egress VC ATM Traffic
Descriptor parameters, according to the type of Traffic Contract (ATM Service
Category/Conformance Definition pair).

Note: The VCI can be modified only if it is not involved in cross-connection. Otherwise the cross-
connection must be deleted, the PWE3 must be deleted and the VCI set to "Not in service".
Note: The VCI can be deleted only if it is not involved in cross-connection. Otherwise the cross-
connection must be deleted, the PWE3 must be deleted and the VCI set to "Not in service".
Note: VC ATM Admission Control.

3JK Edition 1.00
13.1.4 ATM PW Layer


3JK Edition 1.00
13.1.4 ATM PW Layer
13.1.4.1 ATM PW Parameters
To configure an ATM PW Layer select the Interface (from #01 to #08),

enter the following parametrs and click on Apply.
PW Label: it is possible to configure for each ATM PW, only one value, to be
assigned to both Inbound (Packet -> ATM direction) and Outbound (ATM ->
Packet direction) PW Labels. The value must be in the range: 16-65535.
Since de-multiplexing of ATM PW flows towards ATM interface is based on
ATM PW Inbound Label value, a check on all Inbound values, configured on
the same NE, must be done in order to avoid duplications.
The remaining fields of the 32-bit PW Label to be inserted into ATM PW
frames will be assigned as below reported:
3-bit EXP field is assigned according to the ATM PW flow CoS
1-bit S field is set to 1 (Bottom of Stack)
8-bit TTL is set to 255

Click on Create to configure another ATM PW.

To delete an ATM PW select the ATM PW and click on Delete.

3JK Edition 1.00
13.1.4 ATM PW Layer
13.1.4.1 ATM PW Parameters [cont.]
VPC/VCC Mode: it is possible to configure to have ATM PW Service in:

VPC mode, i.e the multiplexing of one (N=1) or more (N>1) VPs to the same ATM PW Ethernet
flow;
VCC mode, i.e the multiplexing of one (N=1) or more (N>1) VCs, belonging to the same VP, to the
same PWE3 ATM flow, will be supported.
In order to perform an ATM PW Service in VPC mode, the related VP must had be previously
configured at ATM Layer as Connection end-point.
In order to perform an ATM PW Service in VCC mode, it must had been previously configured at
ATM Layer the related VP, as Termination end-point, and VC.
Max Cell Concatenation and Max Delay (timeout): for each ATM PW flow it is possible
to configure how ATM cells will be concatenated into the same Ethernet packet:
1. a timeout, after the reception of first ATM cell, expires;
2. a maximum number of concatenated ATM cells is reached
The above configuration parameters allow, for each ATM PW, to find the trade-off between
latency and ATM PW encapsulation overhead.
The timeout is configurable in the range 0.1 to 40 ms, with 0.1 ms steps. Default value is 1 ms.
The maximum number of concatenated cells is is configurable by ECT/NMS in the range 1 to 28
cells, with 1 cell step . Default value is 1 cell (limitation for Cell Concatenation).
In this release the following limitations apply:
only timeout values from 1 to 10 ms, with 1 ms step, are configurable and tested;
only maximum cell concatenation number 1, 2, 4, 5, 10, 28 cells are configurable and tested.

If in VPC mode, the VPI only can be changed. If in VCC mode, the VPI only, the VCI only or both can be
changed.

3JK Edition 1.00
13.1.4 ATM PW Layer
13.1.4.1 ATM PW Parameters [cont.]
Admin Status: this field is a read-only field. The status is automatically set to "up",
when a cross-connection is established and set to "down", when a cross-connection is
deleted.


3JK Edition 1.00
13.1.4 ATM PW Layer
13.1.4.2 VPI/VCI Translation
For each ATM PW flow, it is possible to change the VPI/VCI value of

transported cells to a different value from that used in the ATM VP/VC
configuration.
Ingress VPI/VCI Translation (ATM -> Ethernet direction): VPI/VCI value can
be changed to a configurable value in the ATM Cell(s) encapsulated into ATM
PW Ethernet frames:
if the ATM PW is configured in VPC mode, only VPI can be changed, with range from
0 to 255 or 4095 according to UNI or NNI configuration of related ATM interface;
if the ATM PW is configured in VCC mode, then VPI, VCI or both can be changed, with
range from 0 to 65535
No check shall be performed on the new VPI/VCI values against the VPI/VCI
range foreseen for ATM i/f (VPC mode) or terminating VP (VCC mode).
Egress VPI/VCI Translation (Ethernet -> ATM direction): whatever is the
VPI/VCI value within ATM cell(s) transported by ATM PW frame, it is changed
into the ATM Cells sent towards ATM interface to the configured value of
related VP (in case of VPC mode) or VC (VCC mode).


3JK Edition 1.00
14 Core-E view for Core-E and Ethernet
domain


3JK Edition 1.00
14 Core-E view for Core-E and Ethernet domain
14.1 Core-E domain
The Core-E domain multiple main view contains two tab-panels:

Ethernet Physical Interface
TMN Interface
Core-E Main view

This domain view consists of the following areas:

Resource Tree, displaying Ethernet physical interface with related port number;
Resource List, displaying tabular information about tributaries in tree area;
Resource Detail, providing access to Core-E detail view Alarms and Settings.

3JK Edition 1.00
14.1 Core-E domain
14.1.1 Ethernet Physical Interface
This tab-panel refers to the Ethernet ports, which can be used as traffic
ports and includes two tab-panels:
Alarm tab-panel
Settings tab-panel

If the optional SFP optical plug-in has been enabled in the Core-E unit (refer to Equipment menu) also
the Ethernet Port #5 will appear (see Figure above).

3JK Edition 1.00
14.1.1.1 Alarm tab-panel
Alarm view shows the Ethernet ports-related alarms.

Selecting the node in Tree area allows checking Ethernet tributary
alarms current state.


3JK Edition 1.00
14.1.1.2 Settings tab-panel (Ethernet Port#1 to Port#4)

The Settings view performs all the available functions for Ethernet tributary ports. Information related to a data port
configuration is provided by the following parameters:
Port Status (Enabled or Disabled);
Warning: Before enabling an Ethernet port, when the Static LAG Criteria and the Ethernet Interface Criteria for 1+1 EPS
Core features have been enabled in Menu Configuration > System Settings, it is recommended first to disable the Ethernet
Interface Criteria for 1+1 EPS Core feature. This feature could be enabled again after that this additional port has been
properly configured. No traffic impact is foreseen with this operation.
Auto-Negotiation Status (Enabled or Disabled);
Flow Control (Enabled or Disabled);
N.B.: Only asymmetric pause capability can be configured to transmit pause frame but not receive pause frame on the
Ethernet ports. If a pause frame is received on Ethernet ports such frame is dropped. Default values for manual mode are 100
Mbit/s, full duplex, pause disable
Configuration (Other / Configuring / Complete / Disabled / Parallel Detect Fail) all read-only;
Advertised Capability (10 Mb/s Half Duplex, 10 Mb/s Full Duplex, 100 Mb/s Half Duplex, 100 Mb/s Full Duplex).
The Restart button allows forcing auto-negotiation to begin link re-negotiation.
VLAN configuration. The traffic, received on each user Ethernet port, can be untagged or tagged. For each port it is possible
to configure:
Acceptable Frame Type:
Admit tagged only (only tagged frames are allowed in ingress; the untagged frames are dropped)
Admit all (tagged and untagged frames are allowed in ingress). Default value: Admit all.
Port VLAN ID: if the Acceptable Frame Type is set to Admit all the VLAN-ID and Priority fields, to be added in ingress to
untagged frames, must be configured. Only VLAN-ID values already defined (in the VLAN management menu) can be
configured for this purpose. The Priority values allowed are in the range 0 - 7.
The default Port VLAN-ID and Priority values are: VLAN-ID=1; PCP=0.
The VLAN 1 is always removed, when the frame is forwarded.
N.B.: Untagged frames - The untagged frames received on one user Ethernet port, configured as Admit tagged only, are
dropped.
N.B.: Priority frames - The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as Admit tagged
only, are dropped. The priority packets (VLAN-ID=0) received on one user Ethernet port, with the Admit all configuration
enabled, are managed as untagged frames for VLAN-ID field, while the Priority field is the same of the received packets.
Alarm Profile (not implemented);
Synchronous Ethernet Operation Mode - From the Ethernet traffic interfaces (configured as 1000 Mb/s) it is possible to
recover the physical Rx synchronization signal or to deliver the Network Element Clock synchronization signal (in this case the
Ethernet port must be set as Sync-E Master). This feature is needed in order to realize "synchronous Ethernet Networks"
addressed by G.8261. Enable the Synch-E mode by setting Synchronous and selecting the operating mode: Master or Slave.
Note: If the electrical Ethernet port has to be used as Synchronous Source, the Ethernet port must be set as Synch-E Slave.

3JK Edition 1.00
14.1.1.3 Settings tab-panel (Ethernet Port#5 and #6)

The Settings view performs all the available functions for Ethernet tributary port#5. Information related to the port configuration
is provided by the following parameters:
Warning: Before enabling an Ethernet port, when the Static LAG Criteria and the Ethernet Interface Criteria for 1+1 EPS
Core features have been enabled in Menu Configuration > System Settings, it is recommended first to disable the Ethernet
Interface Criteria for 1+1 EPS Core feature. This feature could be enabled again after that this additional port has been
properly configured. No traffic impact is foreseen with this operation.
Flow Control (Enabled or Disabled);
N.B.: Only asymmetric pause capability can be configured to transmit pause frame but not receive pause frame on the
Ethernet ports. If a pause frame is received on Ethernet ports such frame is dropped. Default values for manual mode are 100
Mbit/s, full duplex, pause disable
Configuration (Other / Configuring / Complete / Disabled / Parallel Detect Fail) all read-only;
Advertised Capability (1000 Mb/s Full Duplex). The Restart button allows forcing auto-negotiation to begin link re-
negotiation.
Optical Info field: it is a read-only field not implemented in the current release.
VLAN configuration. The traffic, received on each user Ethernet port, can be untagged or tagged. For each port it is possible
to configure:
Admit all (tagged and untagged frames are allowed in ingress). Default value: Admit all.
Port VLAN ID: if the Acceptable Frame Type is set to Admit all the VLAN-ID and Priority fields, to be added in ingress to
untagged frames, must be configured. Only VLAN-ID values already defined (in the VLAN management menu) can be
configured for this purpose. The Priority values allowed are in the range 0 - 7.
The VLAN 1 is always removed, when the frame is forwarded.
N.B.: Untagged frames - The untagged frames received on one user Ethernet port, configured as Admit tagged only, are
dropped.
N.B.: Priority frames - The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as Admit tagged
only, are dropped. The priority packets (VLAN-ID=0) received on one user Ethernet port, with the Admit all configuration
enabled, are managed as untagged frames for VLAN-ID field, while the Priority field is the same of the received packets.
Alarm Profile (not implemented);
Synchronous Ethernet Operation Mode - From the optical Ethernet traffic interface it is possible to recover the physical Rx
synchronization signal or to deliver the Network Element Clock synchronization signal (in this case the Ethernet port must be
set as Sync-E Master). This feature is needed in order to realize "synchronous Ethernet Networks" addressed by G.8261. Enable
the Synch-E mode by setting Synchronous.

3JK Edition 1.00
14.1 Core-E domain
14.1.2 TMN Interface
The interfaces are of two types:

1) TMN Ethernet on a dedicated connector
2) Port #4 of the Ethernet traffic ports, which can be dedicated to TMN
purpose and not to traffic.

This tab-panel has 2 tab-panels:

Alarm tab-panel
Settings tab-panel

3JK Edition 1.00
14.1.2.1 Alarms tab-panel
Alarm view shows the Ethernet ports-related alarms.

Selecting the node in Tree area allows checking Ethernet tributary
alarms current state.


3JK Edition 1.00
14.1.2.2 TMN In-band

The TMN In-Band feature allows the extension of the DCN over User Ethernet interfaces used to carry
user traffic.
Two default TMN In-Band interfaces (TMN In-band #1 and #2) are supported, each having its own IP
address and subnet.
The TMN traffic delivered In-Band is VLAN tagged and identified by a specific VLAN ID defined by the
operator in the range 2-4080.
The delivery of TMN In-Band can be enabled on all User Ethernet interface of the Core board, both
Optical and Electrical.
Note 1: the Ethernet ports involved in a LAG cannot be used as TMN In-band interface.
Note 2: If the TMN In-band interface has been configured and the traffic classifier is according to
802.1p, the priority on the TMN traffic is highest. If the traffic classifier is according to DiffServ, the
priority on the TMN traffic is low and the traffic on the other Ethernet ports must be taken in
consideration.
Note 3: If two Ethernet ports, associated to the same TMN In-band logical interface, are segregated,
the two ports do not communicate each other, as for the normal Ethernet traffic (they have the same
VLAN ID). If two Ethernet ports, configured in different TMN In-band logical interfaces, are segregated,
the two ports can communicate each other, as they have 2 different VLAN IDs).
The OSPF and related Area ID can be enabled on a TMN In-Band interface.
For each TMN In-Band interface the following parameters must be selected:
IP address and subnet: default 10.0.3.2/24 for interface #1 and 10.0.4.2/24 for interface #2
VLAN ID: default 4097 for interface #1 and interface #2
List of User Ethernet interfaces where transmit/receive TMN In-Band traffic: default None (multiple
selection or deselection can be done by holding the Ctrl key, while clicking on one or more entries)
OSPF enable/disable: default disabled for both interfaces
Area ID in case of OSPF protocol enabled: default 0.0.0.0

3JK Edition 1.00
14.1.2.3 TMN Ethernet port

If used, the TMN Ethernet must be:

Enabled.
Assigned an IP address with its IP mask.
Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also the
area number.
Click on the Alarm Profile icon to open the Alarm Severity Profile menu to associate to the TMN
Ethernet port a specific alarm profile. Select one Alarm Profile in the Profile Name list (4 alarm
profiles are listed). Tick the Show details check box to see the severity associated to each alarm.
Click on Apply to activate the selections.

3JK Edition 1.00
14.1.2.4 TMN Ethernet Port #4

If the Ethernet Port 4 has been used as TMN port, the port 4 must be:
Enabled.
Assigned an IP address with its IP mask.
Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also the
area number.
Click on Apply to activate the selections.

3JK Edition 1.00
14.1 Core-E domain
14.1.3 Ethernet LAG

If in the Configuration > Ethernet Features Shell menu have been created the Ethernet LAGs (Link
Aggregation Group), the created Ethernet LAGs will appear in the Ethernet Physical Interface tab-panel
as shown in the figure. In the figure two LAGs have been created (Port #1 and Port #15).

3JK Edition 1.00
14.1 Core-E domain
14.1.3 Ethernet LAG [cont.]
Each Ethernet LAG has its Setting tab-panel.

In this tab-panel only the VLAN configuration field can be modified (all the other fields are read-only).
VLAN configuration. The traffic, received on each user Ethernet port, can be untagged or tagged.
For each port it is possible to configure:
Admit all (tagged and untagged frames are allowed in ingress)
Default value: Admit all.
Port VLAN ID: if the Acceptable Frame Type is set to Admit all the VLAN-ID and Priority fields (to
be added in ingress to untagged frames), must be configured. Only VLAN-ID values already defined
(in the VLAN management menu) can be configured for this purpose. The Priority values allowed
are in the range 0 - 7.
The default Port VLAN-ID and Priority values are: VLAN-ID=1; Priority=0.
VLAN 1 is always removed when the frame is forwarded.
N.B.: Untagged frames
The untagged frames received on one user Ethernet port, configured as Admit tagged only, are
dropped.
N.B.: Priority frames
The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as Admit tagged
only, are dropped.
The priority packets (VLAN-ID=0) received on one user Ethernet port, with the Admit all
configuration enabled, are managed as untagged frames for VLAN-ID field, while the Priority field is
the same of the received packets.

3JK Edition 1.00
14.1.3 Ethernet LAG
14.1.3.1 MPT-HC connected to the Core-E

When the Ethernet port #5 or/and port #6 are sent and used to connect an MPT-HC, a new toolbar
button is available inside the Core-E view; this button allows to access the MPT-HC menu.
In the example an MPT-HC (tab-panel Port #1.5) has been connected to Port #5.
The Ethernet Port #5 is not available as an Ethernet Physical Interface: it is removed from the
Tributaries Data list.

3JK Edition 1.00
15 AUX view for AUX DOMAIN


3JK Edition 1.00
15 AUX view for AUX DOMAIN
15.1 Name of Level 2
The AUX peripheral unit has two tab-panels:

Settings
External points


3JK Edition 1.00
15.1.1 Settings
To enable the 64 kbit/s user Service channel #1 or #2 set the Channel

Status to Enabled and click Apply.

Note: the Protocol Type is fixed to Synchronous 64 kbit/s RS422/V.11 DCE co-directional.
Note: The EOW Interface is not implemented in the current release.

3JK Edition 1.00
15.1.2 External Points
There are two types of external points:

input external points
output external points
By clicking on the tree root the tree will be expanded.
A single left click selection of a tree element causes the activation of
the corresponding Tabular representation displayed in the "Resource list
area" (upper righ side of the screen).
A click on a row in the Resource list area opens the Settings menu.


3JK Edition 1.00
15.1.2.1 Input External Points

An input external point is described by the following parameters:

Id: identification number
UserLabel: associates a user friendly name to an external point
Polarity: describes the polarity (Active Low/ Active High)
External State: describes the state (on /off)
Alarm Profile: describes the associated Alarm Profile (not implemented)
After a row selection, the user can modify the User Label, the Polarity.
The operator choices will be sent to NE after selecting the "Apply" button.

3JK Edition 1.00
15.1.2.2 Output External Points

Seven output external points are available.

The output external points (CPO#1 ... 7) are described by the following parameters:
Id: identification number
UserLabel: a user friendly name can be associated to an external point
Polarity: describes the polarity (Active Low/ Active High). In this field the polarity of the external
point can be changed.
Criteria: fixed to Manual. (The output can be activated manually). Note: the Automatic mode is not
supported in this release.
External State: describes the state (on /off). In this field the external point can be activated (on) or
deactivated (off).
The operator choices will be sent to NE by clicking on the "Apply" button.

3JK Edition 1.00
16 Annex A: Network Element Overview


3JK Edition 1.00
16.1 Main View
When NETO starts, the main view screen is shown below.
This screen has three specific areas:

NE Configuration area: displays NE general information (left side);
Status & Alarms area: reports supervision status and alarms (right side).
Discovered NEs: in the lower part of the screen is shown the list of the discovered
NEs. With a double click on a row the IP address of the NE in the row automatically is
written in the NE Info field.
Show and Alarm Monitor buttons are enabled when a NE is supervised
only. Supervision starts as soon as the operator writes an IP address in the
specific field and press the OK button.

The Network Element Overview (NETO) is the starting point of the CT application.
NETO functions require to know the NE identity by means of the related IP Address.
Only one NE can be managed in a NETO session.
The User Interface is provided by the NETO Main View.
NETO Main view can also be reduced by using the shrink glass ( ) button in the Menu Bar.
The reduced NETO view allows the operator to save screen space while continuously checking
supervision and alarms status. Gray icons mean that supervision is not active.
The magnifying glass ( ) button allows to show the normal NETO main view.
The alarm severity icon appears in operating system tray bar, close to system clock and other system
software icons.
This icon also has a specific tooltip, visible when mouse cursor is moved over it, that will show: name
of application, NE IP address, and highest severity alarms number. The tray-bar icon is present in the
Windows system bar (in the lower part of the screen). The tray-bar icon takes the color of the most
severe alarm. The tray-bar icon is not interactive and does not present any menu or executable
command if clicked either with left or right mouse button.

3JK Edition 1.00
16.2 NE Configuration area
The NE configuration area is divided in three sections:
1) NE Info section, containing information related to NE addressing;
2) NE Description section, with information about NE characteristics;
3) Command Buttons section, providing buttons to manage NETO functions.


3JK Edition 1.00
16.2.1 NE Information
This area is related to the wanted NE identification.
IP Address field displays the actual NE IP address used by NETO

functions.

OK button will start supervision on specified NE, if reachable. Keyboard shortcut Alt + o behaves as
clicking on OK button with mouse.
Whether the IP address is correctly written, other than clicking on OK button, supervision process
will start on specified NE by pressing enter (carriage return) key on keyboard.

3JK Edition 1.00
16.2.2 NE Description
This area contains some parameters displaying general information

about the supervised NE.
Parameters can be read and modified (and applied to NE using the

Apply button).

Please note that changing these labels values will also automatically update NETO window title
content: window title will always contain Site Name of supervised NE. Keyboard shortcut Alt + a
behaves the same as clicking on Apply button with mouse.

3JK Edition 1.00
16.2.3 Command Buttons
Command buttons available through NETO are:
Show button will start WebEML (JUSM/CT) application on a

supervised NE.
Alarm Monitor button starts AM application. Buttons Show and
Alarm Monitor will be enabled when NE is supervised only.
Exit button will close NETO, stopping a possibly running supervision
and closing all related applications.

Keyboard shortcut Alt + S behaves as clicking on Show button with mouse. Keyboard shortcut Alt +
m behaves as clicking on Alarm Monitor button with mouse. Key-board shortcut Alt + E behaves as
clicking on Exit button with mouse.

3JK Edition 1.00
16.3 Status & Alarms area
Information on supervision status and active alarms are shown in this

area.

Round-shaped icons change their colours according to current NETO functions and situation. With
respect to Supervision status:
green colour means that supervision function is ongoing,
red colour means that NE link does not work,
gray icons mean that supervision is not active (to be started).
Alarm synthesis contains the list of the alarms listed by severity: whether an icon is not gray, means
that such kind of severity contains one alarm at least. Alarm Monitor button shown in Figure opens
the Alarm Monitor application external tool.

3JK Edition 1.00
16.4 Supervision Function
The supervision function allows operator registering a new manager

inside NE MIB and performing cyclic (periodic) monitoring on
connection.
To start supervision, the operator must specify NE IP address in the IP
Address field and then simply press OK button.
If supervision succeeds, screen is updated with information retrieved
from NE and supervision icon changes its colour from gray to green
stating NE is correctly supervised.
When a supervision error, a link down or other problems arise during
supervision, icon will become red. Alarm Synthesis area will be updated
as well. Clicking on Show button, NETO will open the WebEML
(JUSM/CT) for MPR equipment.
To close an ongoing supervision, simply click on Exit button (this will
also close NETO) or change NE IP address and click OK button to start
supervision procedure on a different NE (this will stop previous
supervision).


3JK Edition 1.00
16.5 Menu Bar
(New)
(Open)
(Magnifying glass)
NETO Main view can also be minimized by using the shrink glass ( ) button.
Using both (New) and (Open) icons, the operator will be able to
open NEs table modal window (see following Figure).
Open icon allows opening a previously saved file containing a list of

NEs.
New icon allows creating a new list, specifying the file name
containing its data, only when those data will be saved.

NETO can manage and organize a list of available NEs by showing operator a table containing such data.

3JK Edition 1.00
16.5 Menu Bar [cont.]
NETO List Management

Get Current button is used to read information from main NETO view. This operation will always add
a new line in NE list table with all information related to currently supervised NE. This happens even
though a NE with corresponding IP address is still present in the list;
New button, adding a new NE from scratch. This allows the operator to fill the IP Address field
only with its needed NE.
Remove button, removing a selected NE;
Set Current button, filling main NETO view IP address with datum from selected NE. The operator
must previously select a valid line in NEs table and then click on Set Current button so filling NETO
main window data. This operation will automatically close the NE list window but does not start
supervision on set NE;
Save button, saving table list in a specified file.
To close this window click on Close button.
All data are saved in a custom XML format called NETO and this structured file will contain all data
shown in Figure related to all NEs added to the list.
The operator can have its own NEs lists repository, containing all .NETO files that it produced with NEs
information inside.

3JK Edition 1.00
16.6 Sequence for NETO interface and NE list
1. Fill NETO main view IP Address field with NE IP address;

2. Start supervision by clicking Ok button;
3. Open the NEs table (any method, through New or Open button);
4. Click on Get Current;
5. Save the list and Close the list window.

This operation will produce a clean and up-to-date NEs table list. The NE table lists are not updated, if
the operator will modify, NE site name site location or even IP address. Such data are used for
references purposes, but the operator must take care to keep them updated.

3JK Edition 1.00
Configure the equipment.

Enable the tributaries.
Create some cross-connections.
Set the Transmitter of Channel 1 to transmit a constant power.
Read the Rx power of Channel 1.
Read the RF frequency of Channel 1.
Show the current position of the switches (through their commands in
the CT).
Manually switch the 3 switches to the protecting channel (through their
commands in the CT).
Activate the loopback.


3JK Edition 1.00
Blank Page


3JK Edition 1.00
End of Module
Operator interface MPR node


3JK Edition 1.00
32
Section 3
NE operation
Module 2
Initial configuration MPR node
3JK Edition 1.00

3JK Edition 1.00
Blank Page

NE operation Initial configuration MPR node
Document History

Vimercate

3JK Edition 1.00
Objectives
Configure the equipment starting from a scratched NE.


3JK Edition 1.00
Objectives [cont.]


3JK Edition 1.00
Table of Contents
1 Initial Configuration 7
1.1 General Requirements 8
1.2 Initial Turn-up 10
1.3 Enable Plug-In Cards 14
1.4 Provision Plug-In Cards 35
1.5 Provision ASAP Card 57
1.6 Provision AUX Card 59
1.7 Provision Synchronization 61
1.8 Provision NTP protocol 63
1.9 Provision NE Time 64
1.10 Provision VLAN 65
1.11 TDM Cross-connections 66
1.12 STM-1 Cross-connections 67
1.13 ATM Cross-Connections 68
1.14 AUX Cross-Connections 69
1.15 Provision System 70
1.16 Provision LAG 74
1.17 Provision Local NE IP Address 75
1.18 Provision TMN Ethernet Port 76
1.19 Provision Ethernet Port 4 for TMN (if required) 77
1.20 Provision TMN in-band 78
1.21 Provision IP Static Routing 79
1.22 Provision OSPF Static Routing 81
325 Blank Page All Rights Reserved Alcatel-Lucent 2011 82
2 Provisioning by
Provisioning
tool 83
2.1 Start Provisioning Tool 84
2.2 Provisioning Tool screens 87
2.3 Configuration Options Screen 91
2.4 Core-E Configuration 92
2.5 E1 configuration 95
2.6 STM-1 configuration 96
2.7 Modem Provisioning 97
2.8 MPT Access configuration (1+0) 101
2.9 MPT Access Provisioning 102
2.10 MPT Access configuration (prot. enabling: 1+1) 106
2.11 MPT Access Prov. (without A. M.) (1+1) 107
2.12 MPT Access Prov. (with A. M.) (1+1) 109
2.13 Synchronization Configuration 111
2.14 Cross Connections Configuration 115
2.15 Segregated Port Configuration 116
2.16 802.1D management 117
2.17 802.1Q management 118
2.18 VLAN Management 120
2.19 Port VLAN Configuration 121
2.20 Network Configuration 122
2.21 Trusted Managers 124
2.22 Typical Report Panel 125
Exercise 126
Blank Page 127
End of Module 128

3JK Edition 1.00


3JK Edition 1.00
1 Initial Configuration


3JK Edition 1.00
1.1 General Requirements
PC HW Configuration
CPU: AMD Atlhon/Intel Celeron/Intel Pentium 4 or higher
RAM: 500 MB (1 GB recommended - strongly recommended with Windows
Vista)
Hard Disk space: 1.5 GB (available space for log files, JRE excluded)
Display Resolution: 1024x768 pixel
CD-ROM Drive: 24X
Serial Interface: RS-232-C 9.6 to 57.5 Kbps
Ethernet Interface: Ethernet Card 10/100 Mbps
Operating Systems Supported

Microsoft Windows XP Professional service pack 3 or Microsoft Windows Vista
Ultimate service pack 2


3JK Edition 1.00
1.1 General Requirements [cont.]
Additional requirements
Microsoft Internet Explorer 6 SP1, 7, 8, Mozilla Firefox 2, 3, 3.5
Standard user can be used to run the applications, but for TCO Suite usage
Administrator password is needed
Java Runtime Environment (JRE) 6 Update 14
Disable all Firewall software on PC used


3JK Edition 1.00
1.2 Initial Turn-up
1 - Copy software on PC.

Before operating the user system interface (USI) for the first time, the
programs contained on the CD ROM must be copied on the PC.
A - Insert CD ROM disk into PC.
B - On Windows desktop, double click on My Computer icon. My Computer window
displays.
C - In My Computer window, click on CD ROM icon. Files window displays
D - Copy Craft Terminal software on PC on a directory.
2 - Turn on the 9500MPR.
3 - Establish communication between equipment and Craft terminal
computer. Default NE IP address: 10.0.1.2
4 Startup
Follow the steps on following figures to open communication with the
equipment.

Note: if it is necessary to scratch the MIB use the following procedure.
Database scratch procedure:

1. Power off the equipment
2. Move the dip-switch 2 on the Core-E board.
3. Re-plug the Core-E board in the subrack.
4. When EC software starts, detects the switch position and starts with database scratch: all the
configuration information will be erased (radio parameters, synch, XCONN, network, ecc). The
information of SWP is maintained (the stand-by and active SWP banks are not deleted).
5. It is possible to understand when the scratch procedure is over: make a ping towards NE with
default IP address.
6. After this, plug-out the Core-E board and restore the original dip-switch 2 position.
7. Re-plug the Core-E board.
Note: Average time necessary to scratch the database (from SW start): 6-7 minutes.

3JK Edition 1.00
1.2 Initial Turn-up [cont.]
Startup Procedure
Click OK
Enter the IP
Address or
DNS name
See next slide


3JK Edition 1.00

If the Supervision
is ongoing, click
Show
Type your username

must not be more than 20
The application has characters
been started pop-up
will automatically
close in a few Type your password must
seconds. The Login not be less than six (6) or
screen will appear more than 20 characters
and must be composed of
full ASCII characters set
(UPPER/lower case,
numeric and special
Click on Apply characters).

Note: Profile Types there are four user profiles defined.
Administrator (full access also for NMS local system security parameters).
CraftPerson: person in charge for installation and the mantenance at radio site; full access to NE but
not for security parameters, only for own password.
Operator (person in charge to operate at the network level, not at the radio side).
Viewer (view screens only).
Note: Default User Accounts at the NE installation time, two default user accounts are created on NE
independently from the SNMP operating mode.
Profile: administrator
Username: initial
Password: adminadmin
Profile: craftPerson
Username: Craftperson
Password: craftcraft

3JK Edition 1.00
START
Provisioning MPR
Enable Plug-In Cards
Provision Plug-In Cards
Provision Synchronization
Provision NTP Protocol
Provision NE Time
Provision VLAN (if required)
TDM Cross-Connections
STM-1 Cross-Connections
ATM Cross-Connections
AUX Cross-Connections
Provision System
Provision management parameters

Note: Changes to provisioning do not have to be made in any particular order.

See the figure for the recommended sequence.
Warning: If from this NE remote NEs have to be reached, remember to configure properly the Routing
Protocol of the PPP RF channel, if the remote NE is connected through the radio link or of the NMS
Ethernet Port, if the remote NE is connected through the Ethernet cable.

3JK Edition 1.00
1.3 Enable Plug-In Cards
All the cards that can be inserted in MSS4 or MSS8 chassis must be
enabled in the equipment section:
Spare CORE-E (in slot 2 only)
E1-PDH Access card
STM-1 Access card
Modem Access card (ODU300 interconnection)
MPT Access card (MPT interconnection)
AUX board
ASAP board
FAN board
SFP optical plug-in
Enable the MSS cards by using the following procedures.


3JK Edition 1.00
1.3 Enable Plug-In Cards [cont.]
Enabling SFP
optical plug-in
Click to start

Click on Apply on the Plug-
in Type field to enable the
SFP optional optical plug-in,
if the plug-in has been Apply the
installed in the Core unit Equipment Type
Settings
tab


3JK Edition 1.00
Enabling Spare
Core-E Card
Click to start
Settings tab
Alarm Profile: not nsupported

Choose Core-E from the dropdown menu for Apply the
the spare protected Core-E card in slot 2 Equipment Type


3JK Edition 1.00
Enabling E1
Access Card 1
Click to start
Click to apply
Settings tab changes

Choose the P32E1DS1 unit


3JK Edition 1.00
Enabling E1
Access Card 2
Click to start
Settings tab
Click to apply

Choose the P32E1DS1 unit changes

3JK Edition 1.00
Enabling
protection
Click to start
Settings tab Click to apply

changes

Select 1+1 EPS
This operation must be done to enable the EPS protection.

3JK Edition 1.00
Enabling STM-1
Access Card 1
Click to start
Click to apply

Choose the SDHACC unit


3JK Edition 1.00
Enabling SFP
Select the optical SFP (SFP-O) or the electrical

SFP (SFP-E) installed on the STM-1 ports (SFP#1
and/or SFP#2) and click Apply.
Note: It is not possible to enable SFP #1 and
SFP #2 at the same time.


3JK Edition 1.00
Enabling STM-1
Access Card 2
Click to start
Settings tab
Click to apply

Choose the SDHACC unit changes

3JK Edition 1.00
Enabling
protection
Click to start

changes

Select 1+1 EPS

3JK Edition 1.00
Enabling Modem
Card 1
(to interface
ODU300)
Click to start
Click to apply

Choose the MD300 unit

Note: ODU is automatically enabled when Modem Card is enabled.

3JK Edition 1.00
Enabling
Modem Card 2
Click to start
Settings tab
Click to apply

Choose the MD300 unit changes

Note: ODU is automatically enabled when Modem Card is enabled.

3JK Edition 1.00
Enabling
protection
Click to start
Click to apply

Select the suitable protection scheme
This operation must be done to enable the protection: 1+1 FD or 1+1 HSB.

3JK Edition 1.00
Enabling MPT
Access Card 1
(to interface
te MPT-HC and
MPT-MC)
Click to start

changes

Choose the MPTACC unit


3JK Edition 1.00
Enabling one port

in the MPT
Select as Usage MPT-HC or MPT-MC in one or
Access Card two Ports.
N.B. Port#1 and Port#2 are electrical Ethernet
ports and Port#3 and Port#4 are optical
Ethernet ports.
Click on Apply

N.B.: Two unprotected or protected MPT-HC or MPT-MC can be connected to one MPT Access unit.

3JK Edition 1.00
Enabling MPT
Access Card 2
Click to start
Settings tab
Click to apply

Choose the MPTACC unit changes

3JK Edition 1.00
Enabling one port

in the MPT
Select as Usage MPT-HC or MPT-MC in one or
Access Card two Ports.
N.B. Port#1 and Port#2 are electrical Ethernet
ports and Port#3 and Port#4 are optical
Ethernet ports.
Click on Apply


3JK Edition 1.00
Enabling protection To configure the protection scheme

select the MPT-HC. (In the example
MPT-HC#31: connected to Port#1 of
the MPT Access unit in Slot#3)
Settings
tab
Select the suitable
protection scheme
Click to apply
changes
This operation must be done to enable the protection: 1+1 FD or 1+1 HSB.

3JK Edition 1.00
Enabling ASAP
Card
Click to start
Settings tab Click to apply changes

Choose the A16E1DS1 unit


3JK Edition 1.00
Enabling AUX
Card (option)
Click to start
Click to apply

Choose the AUX unit


3JK Edition 1.00
Enabling Fan
Unit
Click to start
Settings tab

Select the FANS
Click to apply changes


3JK Edition 1.00
1.4 Provision Plug-In Cards
Core-E Card Provisioning (Ethernet ports 1-4)
Double left click
Go to next page


3JK Edition 1.00
1.4 Provision Plug-In Cards [cont.]
Core-E Card Provisioning (Ethernet ports 1-4)
B2 Click this Apply button.

Current provisioning for Ethernet
Ports #01-#04. Area updates when
Apply buttons are clicked A2 Check to enable NE
auto-negotiation
functions.
B1 Check to enable the
selector port. Uncheck to
disable first in order to A1 Check to allow
change any settings. communication at the
selected data rate
between two locations.
A3 Check to enable input Choose half duplex for
and output pause only one direction at a
features. time, or full duplex for
communication in both
directions at the same
C1 For the configuration time.
refer to the Core-E unit.
A4 Click Apply button.


3JK Edition 1.00
Core-E Card Provisioning (Ethernet port 5)
Double left click
Go to next page


3JK Edition 1.00
Core-E Card Provisioning (Ethernet port 5)
Current provisioning for Ethernet

Port #05. Area updates when Apply
buttons are clicked.

Click this Apply button.
Check to enable the Check to enable NE

selector port. Uncheck to auto-negotiation
disable first in order to functions.
change any settings.
The Optical Info field is
Check to enable input a read-only field not
and output pause implemented in the
features. current release.
For the configuration

refer to the Core-E unit. Click Apply button.


3JK Edition 1.00
E1 Access Card Provisioning
Double left click
Go to next page


3JK Edition 1.00
E1 Access Card Provisioning (TDM2TDM)

See details
Choose TDM2TDM if
radio is being used
to transport E1 data
Flow ID number required to only (no Ethernet).
transport E1 data.

Flow Id number: is system unique and must not be repeated in radio network. Loss of E1 data can
occur.

3JK Edition 1.00
E1 Access Card Provisioning (TDM2ETH)

See details

Flow ID number required to
transport E1 data.

occur.

3JK Edition 1.00
Access Card Details Select Disabled if port (E1 line) is not:

being used as a source or destination (typical choice for a line
not being used at a terminal or not being dropped and inserted
at a repeater);
Signal Mode. being dropped or inserted (typical choice for a line being passed
Configures line format. through at a through repeater and not being dropped and
Allows user to choose if inserted at a drop and insert repeater).
line is dropped and Select Framed: to be able to collect the performances at the input
inserted (by selecting in Tx side and at the output in Rx side.
Framed/Unframed) or Select Unframed:
passed through or not being used as a source or destination (typical choice for a line
used (by selecting being used at a terminal);
Disabled) being dropped or inserted (typical choice for a line being
dropped and inserted at a drop and insert repeater)


3JK Edition 1.00
SDH Access Card (SDH2SDH)
Double left click
Go to next page


3JK Edition 1.00
Set the Auto Laser Shutdown: Enabled/Disabled

ForcedOn/Disabled ForcedOff. This field will
SDH Access Card (SDH2SDH) appear only if the Settings tab-panel of the STM-1
unit the optical SFP has been selected.
Enter the Flow ID (range:

Put a check mark in the 2 to 4080). Warning: the
Port Status box to enable flow id must be unique in
the STM-1. the MPR network.
Enable the J0, if required, by Click on Apply on

selecting one of the two modes the left part.
(SixteenBytesFrame/
OneRepeatedByte) and in the
Expected Receiving Value field
enter the expected value.
Note: byte J0 is only read, no
Regeneration section
Termination is done.
Select the Jitter
Buffer Depth: High/Low

Click Apply button.
Select the TDM Click on Apply on
Clock Source: the right part.
Differential/
Node Timing.
Flow ID number is system unique and must not be repeated in radio network. Loss of STM-1 data can
occur.

3JK Edition 1.00
Modem Card
Double left click
Go to next page


3JK Edition 1.00
Presetting mode Modulation. Displays modulation

Mode. Select Presetting from scheme based on reference channel
dropdown list. spacing and capacity.
Select from dropdown list.
Reference. Displays reference
channel spacing based on
capacity and modulation.
Check to enable radio ID mismatch
Capacity. Read Only Field. function.
PPP RF. Check to enable PPP Enter number from 1 to 255 for
RF port. When not checked receiver ID. Must match transmitter
(disabled) user cannot change: ID at other end of hop.
Routing IP Protocol
OSPF Area Enter number from 1 to 255 for
Remote Address transmitter ID. Must match associated
receiver ID at other end of hop.
Click to enable Open Shortest Path
First protocol then select area
name that has OSPF protocol. Tick on Enable to enable the
Select from dropdown list. transmission of the SSM message over
the radio channel.
Alarm Profile. Not managed

With the Presetting mode the Adaptive modulation is disabled.

3JK Edition 1.00
Tx RF Frequency is automatically
Shifter. Select the frequency entered by ODU when ODU is
separation from the Shifter connected to MSS. If the ODU is
Data Help list. not connected to the MSS, enter
the Tx RF frequency, within
allowed range.
Range. Displays range of Tx
RF frequencies that may be
entered. Read Only Field.
Displays Rx RF frequency.
Result of calculation:
Tx Mute. Read Only Field. Rx Freq - Tx Freq = Shifter Freq.
Status of Local Tx Mute
function.
ATPC. Check to enable ATPC.
By clicking on the icon the Alarm ATPC Power Range.

Severity Profile menu opens,
which allows to associate to the
radio channel a specific alarm Remote ATPC Rx Threshold.
profile. Select one Alarm Profile Default value is -55 dBm.
in the Profile Name list (4 alarm
profiles are listed) and click
Apply. Tick the Show details
check box to see the severity

Note: When the Mode is changed from Presetting to Adaptive Modulation, the radio defaults to 14 MHz
bandwidth at 4 QAM. If the capacity of the radio (number of E1 lines cross connected) exceeds the
available capacity of a 14 MHz Channel at 4 QAM, Adaptive Modulation will not enable. It may be
necessary to perform one of the following provisioning changes:
1.Reduce the quantity of E1 lines being transported to meet the required capacity.
2.Increase Reference Channel Spacing.

3JK Edition 1.00
Adaptive Modulation Mode

Mode. Select from the drop
down list.
Modulation Range.
Displays modulation scheme
based on the modulation mode.
Select from the drop down list.
Reference Channel Spacing.
Displays reference channel
spacing based on the
modulation mode and the
Remote Threshold (dB). modulation range. Select from
The default level is 0, which corresponds to the drop down list.
threshold. The operator can select
switching levels above threshold (0 to +4 dB
corresponding to threshold level +0 to 4 dB)
or below threshold (0 to -2 dB)
corresponding to threshold level -0 to 2 dB).
Reference Modulation.
Not supported.


3JK Edition 1.00
Manual Operation.
When checked, allows user to select and
test a specific modulation scheme.
Current Modulation.
Read Only Field. Displays
modulation scheme the radio
is currently using. Link Identifier Configuration.
Check to enable radio ID
Forced Modulation. mismatch function.
Select modulation scheme (one from the
Modulation Range selected) to test. Expected Identifier.
When activated by the Apply button, Enter number from 1 to 255
radio is forced to operate using selected for receiver ID. Must match
modulation scheme. transmitter ID at other end of
Hop.
PPP RF.
Check to enable PPP RF port. When not Sent Identifier.
checked (disabled) user cannot change: Enter number from 1 to 255
Routing IP Protocol for Transmitter ID. Must
OSPF Area match associated receiver ID
Remote Address at other end of hop.


3JK Edition 1.00
Tx RF Frequency is
automatically entered by ODU
Select the frequency separation when ODU is connected to
from the dropdown list. MSS. If the ODU is not
connected to the MSS, enter
allowed range.
Displays range of TX RF frequencies
that may be entered.
Read Only Field.

Displays RX RF frequency.
Result of calculation:
The Tx Power function allows the Rx Freq - Tx Freq = Shifter
operator to select the transmitter Freq.
output power for the 4 QAM
modulation.
Check to enable the muting of
Tx output power.
Read Only Field.

Read Only Field. Status of Local Tx Mute
Displays Profile Name selected function.
on Alarm Severity Profile screen.


3JK Edition 1.00
MPT Access Card Provisioning
Double left click
Go to next page


3JK Edition 1.00
Power Source configuration
Mode 2 - PFoE (Power Fixed on

Ethernet)
Mode 1 - QMA (only with MPT-HC) In this mode the MPT-HC or MPT-MC
In this mode the MPT-HC is power are power supplied by using the
supplied with a dedicated coaxial electrical Ethernet cable.
cable connected on the QMA Note: To implement this mode with
connector on the front panel of MPT-HC the DC Extractor must be
the MPT Access unit. installed, near the MPT-HC, to
separate the Ethernet traffic and the
power supply.


3JK Edition 1.00
Presetting Mode
Mode. Select Presetting from Modulation. Displays modulation
dropdown list. scheme based on reference channel
spacing and capacity.
Reference Channel Spacing.
Displays reference channel
spacing based on capacity and Check to enable radio ID mismatch
modulation. Select from function.
dropdown list.
Enter number from 1 to 255 for
Capacity. Read Only Field. receiver ID. Must match transmitter
ID at other end of hop.

PPP RF. Check to enable PPP transmitter ID. Must match associated
RF port. When not checked receiver ID at other end of hop.
(disabled) user cannot change:
Routing IP Protocol Click to enable Open Shortest Path
OSPF Area First protocol then select area name
Remote Address that has OSPF protocol. Select from
dropdown list.
Alarm Profile. Not supported. Tick on Enable to enable the

transmission of the SSM message over
the radio channel.
With the Presetting mode the Adaptive modulation is disabled.

3JK Edition 1.00
Shifter. Select the frequency Tx RF Frequency is automatically

separation from the Shifter entered by ODU when ODU is
Data Help list. connected to MSS. If the ODU is
not connected to the MSS, enter
Range. Displays range of Tx allowed range.
RF frequencies that may be
entered.
Read Only Field.
Displays Rx RF frequency.
ATPC Power Range. Result of calculation:
Rx Freq - Tx Freq = Shifter Freq.
Remote ATPC Rx Threshold.
Default value is -55 dBm. ATPC. Check to enable ATPC.
By clicking on the icon the Select in the RSL Driving Criteria

Alarm Severity Profile menu field the suitable value. In 1+1
opens, which allows to FD and HSB configurations both
associate to the radio channel the transmitters can be driven by
a specific alarm profile. Select the lowest or by the highest RLS
one Alarm Profile in the Profile values of the two remote
Name list (4 alarm profiles are demodulators.
listed) and click Apply. Tick the
Show details check box to see Tx Mute. Read Only Field.
the severity associated to each Status of Local Tx Mute
alarm. function.


3JK Edition 1.00
Reference Channel Spacing. Displays

Adaptive Modulation Mode reference channel spacing based on the
modulation mode and the modulation range.
Mode. Select from dropdown list. Select from the dropdown list
Select the spectral efficiency class to be set

as reference: None, Old ETSI mask or New
ETSI mark.
Modulation.
Select the lowest modulation scheme.
Choose in the Supported Modulation field
Manual Operation. When checked, all the modulation schemes to be used with
allowed user to select and test a specific the Adaptive Modulation. The modulation
modulation scheme. schemes (from the lowest to the highest
scheme) must be contiguous.
Note: With MPT-MC max. scheme is 128 QAM.
Current Modulation. Read Onyl Field.
Displays modulation scheme the radio is
The Remote Switching Threshold field is not
currently using.
supported.
Forced Modulation. Select modulation Link Identifier Confguration.

scheme (one from the Modulation Range Check to enable radio ID mismatch function.
selected) to test. When activated by the
Apply button, radio is forced to operate
using selected modulation scheme. Expected Identifier. Enter number from 1 to
255 for receiver ID. Must match transmitter
PPP RF. Check to enable PPP RF port.
When not checked (disabled) user cannot
change: - Routing IP Protocol Sent Identifier. Enter number from 1 to 255
- OSPF Area for transmitter ID. Must match associated
- Remote Address receiver ID at other end of hop.


3JK Edition 1.00
Select the frequency separation

from the dropdown list. Tx RF Frequency is automatically
entered by ODU when ODU is
Displays range of Tx RF connected to MSS. If the ODU is
frequencies that may be entered. not connected to the MSS, enter
The Tx Power function allows allowed range.
the operator to select the
transmitter output power of Read Only Field.
each modulation scheme. The Displays Rx RF frequency.
default level is the expected Result of calculation:
output power. The minimum Rx Freq - Tx Freq = Shifter Freq.
and maximum range of each
modulation scheme is shown in Select in the RSL Driving
parenthesis (min XX- max YY). Criteria field the suitable value.
In 1+1 FD and HSB configurations
both the transmitters can be
By clicking on the icon the Alarm driven by the lowest or by the
Severity Profile menu opens, highest RLS values of the two
which allows to associate to the remote demodulators.
radio channel a specific alarm
profile. Select one Alarm Profile
in the Profile Name list (4 alarm Check to enable the Tx output
profiles are listed) and click power out of ODU.
Apply. Tick the Show details
check box to see the severity Read Only Field.
associated to each alarm. Status of Local Tx Mute function.


3JK Edition 1.00
1.5 Provision ASAP Card
Double left click
Go to next page


3JK Edition 1.00
1.5 Provision ASAP Card [cont.]

The configuration of the ASAP unit is divided in four tab-panels:

E1 Layer
IMA Layer
ATM Layer
ATM PW Layer
For the configuration of the tab-panels refer to S3-M1.

3JK Edition 1.00
1.6 Provision AUX Card
Double left click
Go to next page


3JK Edition 1.00
1.6 Provision AUX Card [cont.]

The configuration of the AUX unit is divided in two tab-panels:

Settings
External Points
For the configuration of the tab-panels refer to S3-M1.
For the ATM traffic the Traffic Descriptors must be also configured. Refer to Menu Configuration ->
Traffic Descriptors in S3-M1.

3JK Edition 1.00
1.7 Provision Synchronization
All the NEs radios in the network must be synchronized to the same
clock.
One radio in the network is provisioned Master.
All other radios in the network must be provisioned Slave.
The slave radios all sync to the clock provided by the master.


3JK Edition 1.00
1.7 Provision Synchronization [cont.]

In figure is given an example of a Master NE Synchronization by an E1 stream.

3JK Edition 1.00
1.8 Provision NTP protocol
Enable the NTP (Network

Time Protocol).

Put a check mark in the NTP protocol field to enable the protocol and write in the Main Server
address field the IP address of the server, which is in charge to distribute the time to all the NEs in the
network. In the Spare Server address field write the IP address of the Spare Server, if any.
The Server reachability field is a read-only field, which shows the reachability of the NTP servers. The
following information can appear:
"Main server reachable"
"Spare server reachable"
"None servers reachable"
"Both servers reachable"
Click on Apply to send to the NE the NTP Configuration.
Refresh push-button can be used to update the screen.

3JK Edition 1.00
1.9 Provision NE Time
NE Time Provisioning
Click to display
pop-up dialog for NE
Time configuration.

If NPT Protocol is disabled, when
checked, enables function to
synchronize Operating System and
Network Equipment Times.

The user can synchronize the NE time from either the PC/laptop or Network Time Protocol (NTP)
servers. Time and date provisioning is accomplished using the NE Time Configuration screens.

3JK Edition 1.00
1.10 Provision VLAN
To provision VLAN refer to S3-M1 chapter 3.6.


3JK Edition 1.00
1.11 TDM Cross-connections
The cross connections screen is used to configure switching of

packetized data through the Core-E Card.
The valid Cross Connections are:
PDH to RADIO
PDH to ETH
ETH to RADIO
RADIO to RADIO
To create the TDM cross-connections refer to S3_M1 par. 3.5.


3JK Edition 1.00
1.12 STM-1 Cross-connections
The cross connections screen is used to configure switching of

The valid Cross Connections are:
SDH to RADIO
RADIO to RADIO
To create the STM-1 cross-connections refer to S3_M1.


3JK Edition 1.00
1.13 ATM Cross-Connections
The cross-connections screen is used to configure switching of

The valid cross-connections are:
ASAP to RADIO
RADIO to RADIO
RADIO to ETH
ASAP to ETH
To create the ATM Cross-connections refer to S3-M1.


3JK Edition 1.00
1.14 AUX Cross-Connections
From the Configuration menu select AUX Cross-Connections.
Select in the New

Cross-connection
area the first
Termination
Point (this can
be a local Select the second
service channel Termination Point
or a service (the cross-
channelin a radio connections are
link) bi-directional)

Click on Add.
The new cross-
connection will
appear in the
list

Valid Cross Connections:

Local User Service Cross-Connection
Pass-through User Service Cross-Connection

3JK Edition 1.00
1.15 Provision System
System Setting

Go to next page

Follow the steps to provision tributary port impedance, quality of service classification, and enter NE
MAC address.

3JK Edition 1.00
1.15 Provision System [cont.]
System Setting


1) Tributary Port Configuration

This field allows to set the suitable impedance of the E1 stream (Unbalanced 75 ohms/Balanced 120
ohm). To activate the new impedance, click on Apply.
2) Quality Of Service
This field allows to set the suitable Quality Of Service (Disabled/DiffServ/802.1p). To activate the
new value, click on Apply.
The Ethernet switch provides a Quality of Service mechanism to control all streams. If the QoS is
disabled, all traffic inside the switch has the same priority; this means that for each switch port
there is only one queue (FIFO) therefore the first packet that arrives is the first that will be
transmitted.
The following values are available:
IEEE std 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag. If the
tag is present the correspondent priority is assigned to the packet;
DiffServ: each packet is classified based on DSCP field in the IP header to determine the priority.
3) DHCP
The DHCP server configures automatically IP address, IP mask and default gateway of the PC Ethernet
interface used to reach the NE. The PC must be configured to get automatically an IP address.
The DHCP server uses an address pool of 10 IP addresses, defined according to the NE TMN port IP
address.
The IP mask is set to the mask of the NE TMN port and the default gateway is set to the NE IP
address.The lease time is fixed to 10 minutes.To activate the DHCP server, select Enabled and click
on Apply.

3JK Edition 1.00

4) Admission Control for Adaptive Modulation (ODU300 only)

Modulation) can be enabled or disabled. Default: Enabled.
When the Admission Control is "Enabled", the check is performed taking into account the capacity of
Taking as example 28 MHz channel spacing (with around 130 Mbit/s of net throughput available with
64QAM), the maximum number of E1s that could be provisioned is 18; the remaining capacity is
devoted to other types of traffic such as ATM or Ethernet.
When RSL value decreases, modulation schemes are downgraded first from 64QAM to 16QAM: the
traffic with lower priority exceeding 16QAM bandwidth is dropped and of course the E1s are kept. As
soon as the RSL value further decreases, modulation scheme are downgraded to 4QAM and all the
traffic exceeding 4QAM bandwidth is dropped (while the E1s are kept). It should be noted that there
is no possibility to provision a number of E1s greater than 18, because being all the E1s with the same
priority, it should not possible from system point of view to decide "which" E1s should be dropped
passing from 16QAM to 4QAM. In order to facilitate provisioning and commissioning operations, a
specific admission control check at CT level has been inserted, avoiding any potential mistakes from
the user provisioning a number of E1s that are not fitting inside 4QAM bandwidth.
When the Admission Control is "Disabled", the check is performed taking into account the capacity of
the highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-16-64 QAM range or 16
QAM for 4-16 QAM range).
It is possible to provision a number of E1s exceeding the 4QAM throughput; always keeping 28 MHz
channel as example, it is possible to provision more than 18E1s, up to 37E1s (value linked with 16QAM
capacity). In this case, when RSL value degrades and modulation scheme is downgraded from 16QAM
to 4QAM, all the TDM traffic is impacted. This feature is answering the need of transmitting an high
number of E1s, but without giving up the benefits of adaptive modulation for Ethernet traffic.

3JK Edition 1.00
11 12
13 14
15 16

5) Ethernet LOS Criteria

By enabling this feature the following additional criteria are added to the Core protection switching criteria:
LOS of Optical User Ethernet interface
LOS of any Electrical User Ethernet interfaces, including the LOS of the forth User Ethernet interface working as
TMN Local Ethernet interface.
Note: the default switching criteria are:
Core Card Missing
Core Card Fail
Flash Card failure
6) Static Lag Criteria

This feature is available only if the spare Core unit has been installed.
By enabling this feature the Ethernet ports of the Core-E unit in stand-by are in ON state (as the ports of the
Active Core-E unit), but the Ethernet traffic is not forwarded.
This behavior allows to reduce the out of service time of user traffic passing through the User Ethernet
interfaces in case of Core protection switching.
This feature shall not be used, when the NE is connected to an equipment performing Link Aggregation and not
supporting Active/Standby management of aggregated links.
7) Event and Alarm Log
As default the Logging is enabled. If set to "Disabled" the events are not sent to the Event Log Browser
application.
8) NE MAC Address
This field is a read-only field, which shows the MAC address of the NE. This MAC address must be used in the
cross-connection with TDM2Eth profile.

3JK Edition 1.00
1.16 Provision LAG
LAG creation

Go to next page

3JK Edition 1.00
1.17 Provision Local NE IP Address
Local Configuration
Provisioning

Click to display pop-
up dialog for the IP
Configuration
Enter NE IP address
Apply the IP Address

Note: After IP address change, the NE restarts.

3JK Edition 1.00
1.18 Provision TMN Ethernet Port
Double click on the front panel of the Core-E unit in the Equipment menu
Select the TMN Ethernet

Select the Setting tab-panel
Enable TMN Ethernet
Enter IP address
Select Static Routing for manual

routing. Select OSPF (Open
Shortest Path First protocol) for
automatic routing
Click on the Alarm Profile icon to

open the Alarm Severity Profile menu
to associate to the TMN Ethernet port
a specific alarm profile. Select one
Alarm Profile in the Profile Name list
(4 alarm profiles are listed). Tick the
Show details check box to see the
severity associated to each alarm
Enter IP Mask and click on Apply

Follow the steps to provision TMN Ethernet on the Core-E Card to carry SNMP data.

3JK Edition 1.00
1.19 Provision Ethernet Port 4 for TMN (if required)
Double click on the front panel of the Core-E unit in the Equipment menu
Select the Port #4 TMN Ethernet

Select the Setting tab-panel
Enable the TMN Port 4
Enter IP address
Enter IP Mask
and click on
Select Static Routing for manual Apply
routing. Select OSPF (Open
Shortest Path First protocol) for
automatic routing
Click on the Alarm Profile icon to open the

Alarm Severity Profile menu to associate to
the TMN Ethernet port a specific alarm
profile. Select one Alarm Profile in the
Profile Name list (4 alarm profiles are listed).
Tick the Show details check box to see the
severity associated to each alarm


3JK Edition 1.00
1.20 Provision TMN in-band
List of User Ethernet interfaces

where transmit/receive TMN In-

Enable Band traffic: default None
(multiple selection with the mouse
can be done)
IP address and subnet:

default 10.0.3.2/24 for
interface #1 and 10.0.4.2/24
for interface #2
OSPF enable/disable: default disabled

for both interfaces VLAN ID: default
1000 for interface
Area ID in case of OSPF protocol #1 and 1001 for
interface #2
enabled: default 0.0.0.0


3JK Edition 1.00
1.21 Provision IP Static Routing
IP Static Routing Provisioning

Click to display pop-up

dialog for IP Static Routing
Configuration
Go to next page

Follow the steps to provision.

3JK Edition 1.00
1.21 Provision IP Static Routing [cont.]
IP Static Routing
Provisioning
Route to a specific
IP address.
Input IP address.
IP Mask.
IP interface to a host
or network. Typically
used at a spur to
interface a host over List of RF path
the RF path. In this
scenario, the Default directions.
Gateway IP Address is Click to view
0.0.0.0 and the IP drop down
Mask (greyed out) is list.
0.0.0.0. Also typically
used at an end
terminal in a radio link
for interface with the
network.
Create new or change existing IP static routes.

3JK Edition 1.00
1.22 Provision OSPF Static Routing
OSPF Static Routing

Provisioning

IP Static Routing
Configuration screen.
Click to display pop-up
dialog for OSPF Area
Configuration

Follow the steps to provision Open Shortest Path First (OSPF) protocol static (automatic) routing.

3JK Edition 1.00
Blank Page


3JK Edition 1.00
2 Provisioning by Provisioning tool


3JK Edition 1.00
2.1 Start Provisioning Tool
Double click on the mpreSuite300 icon on the Desktop.

Click on MPR Tools.


3JK Edition 1.00
2.1 Start Provisioning Tool [cont.]
Double click on the MSS-4/MSS-8 icon.


3JK Edition 1.00
2.1 Start Provisioning Tool [cont.]
Click on the Provisioning Tool button.
Start provisioning


3JK Edition 1.00
2.2 Provisioning Tool screens

The Provisioning Tool can be used "offline" and "online".

In case of offline, it allows to prepare the provisionning in back office. Minimizing time on field and
mistakes.
With the online mode you can either apply the "offline" configuration or fullfil online.
This tool is recommended for first installation.
Thanks to a step by step approach this tool is easy to handle and allows to minimise time for
provisioning
WebEML is more flexible and mandatory to configure AUX and ATM boards (not yet supported in
provisioning tool).
Select:
the direct connection to the NE by putting a check mark on Connect to NE. When you locally
connect the PC to the NE, in the IP Address field automatically (through the autodiscovery) appears
the IP Address of the NE (in the NE the default configuration of the DHCP server is enabled; for this
reason your PC must be configured to obtain an IP Address automatically).
Click on OK.
Note 1: If the DHCP server is disabled, the IP address to be entered is the IP address of the NMS
Ethernet port.
or
the off-line configuration by putting a check mark on Do not connect to NE and by clicking on
Apply.

3JK Edition 1.00
2.2 Provisioning Tool screens [cont.]
Opening screen with off-line operation

The buttons present in this screen has the following meaning:

Open: allows opening an existing MCML (XML-based) configuration file. MCML file can contains NE
configuration data and it can be used to fill panels fields and data.
Get: not operative.
Create: allows to create a new configuration file.
Prev: not operative.
Cancel: not operative.
By clicking on the "Open" button a window opens, which gives the possibility to open a configuration
file created in an older version. If an older configuration file is open a new screen appears, which asks
to convert the file.
By clicking on the "Create" button it will be possible to create a file in the current version or in the
older version.
After opening a configuration file, the user will see a configuration preview in order to understand, for
example, if the file is correct and contains the wanted configuration. Click "Next" button from such
preview panel or "Create" button.

3JK Edition 1.00
Opening screen with the direct connection to the NE

The buttons present in this screen has the following meaning:

Open: allows opening an existing MCML (XML-based) configuration file. MCML file can contains NE
configuration data and it can be used to fill panels fields and data.
Get: this button is operative if you are physically connected to the NE and it is used to upload the
configuration from the NE to the tool.
Create: allows to create a new configuration file.
Prev: not operative.
Cancel: not operative.
By clicking on the "Open" button a window opens, which gives the possibility to open a configuration
file created in an older version. If an older configuration file is open a new screen appears, which asks
to convert the file.
By clicking on the "Create" button it will be possible to create a file in the current version or in the
older version.
After opening a configuration file, the user will see a configuration preview in order to understand, for
example, if the file is correct and contains the wanted configuration. Click "Next" button from such
preview panel or "Create" button.

3JK Edition 1.00

Press the Clear Database and Restart NE button and then press Create to create a new configuration
or press Open to open a previously created configuration.
N.B.: If you don't press the Clear Database and Restart NE button at the end of the configuration you
can save the file, but you cannot apply the configuration to the NE. (The Apply button will not be
available at the end of the procedure).

3JK Edition 1.00
2.3 Configuration Options Screen
Protections options
for the Core-E cards
Protections options
for Slot 3 and Slot 4

This screen is a generic one that depicts all of the pull-down options possible depending on which card
is selected in the card slot. Protections options shown are for all cards.
Warning: The Provisioning Tool allows to configue all the units, except the ASAP and AUX units. (The
ASAP and AUX units must be configured with the WebEML and also the relevant ATM and Service
Channel cross-connections).
Warning: To configure the equipment extract the ASAP and/or AUX units, if any.
Warning: If from this NE remote NEs have to be reached, remember to configure properly the Routing
Protocol of the TMN-RF channel, if the remote NE is connected through the radio link or of the NMS
Ethernet Port, if the remote NE is connected through the Ethernet cable.
Buttons:
Restore: allows to restore in the screen the initial data without any change
Prev: the procedure goes back to the previous step (the changed data may be lost after the Warning
message)
Next: the procedure goes on to the next step (some checks and data storage is done)
Cancel: the procedure goes back to step 1 (Opening screen)

3JK Edition 1.00
2.4 Core-E Configuration
When checked this

Check to enable feature enables input
E1 Access Ethernet the selected port and output pause
Card Icon Icon features
Modem card +
ODU300 icon
Check to enable auto
MPT Access card negotiation
+ MPT-HC icon
Check to allow communication at data Check to allow communication at data

rate in both directions at the same time. rate but in only one direction at a time.

Note:
A white icon indicates that there are no cross-connections, but cross-connections can be created.
A blue icon indicates the destination is full. The limits granted by the license key have been exceeded.
A message is also displayed stating that no more E1 ports will be accepted.
A green icon indicates that the source and destination are available and the destination can accept
more E1 ports.

3JK Edition 1.00
2.4 Core-E Configuration [cont.]
Select TMN if ETH Port 4 on the Core

Card is used for SNMP data.
Select Transport if ETH Port 4 on the Core

Card is used to transport Ethernet data.
Check to select the

operation mode
Select Master or
Tick to enable the SSM Slave


3JK Edition 1.00
2.4 Core-E Configuration [cont.]
The Quality Of Service feature enables priority

forwarding in the Core-E Card switch based on how
the packets are tagged: not tagged or tagged
802.1p or DiffServ. For general traffic, the packets
are not tagged and QOS can be disabled. The user
has to know if the packets are tagged, and if
Check to enable the tagged 802.1p or DiffServ in order to know which
Admission Control QOS function to chose.
Check to enable the

optical SFP plug-in
Priority forwarding disabled.
Each packet is based on DSCP field Each packet is classified based on

in IP header to determine priority. presence of valid 802.1p user priority tag.


3JK Edition 1.00
2.5 E1 configuration
Flow ID is unique Tx Over-the-hop ID

Choose TDM2ETH if radio to network. No
is being used to transport two Flow IDs in a Rx Over-the-hop ID.
just Ethernet or Ethernet network can be Must match Rx/Tx ID
plus E1 data. the same. at other end.
The purpose of TMN

Clock Source
provisioning is to
select the mode
that will be used to
sync TDM E1 data to
the node
Synchronization
source. The user
can select one of
two modes:
Adaptive and
Choose TDM2TDM Differential.
if radio is being Select Adaptive to
used to transport sync TDM output to
E1 data only (no packets.
Ethernet). Select Differential
Select Balance to sync TDM output
120 Ohm if to NE
Select Unbalance 75 Ohm tributary cable Synchronization
is twisted pair. source.
if tributary cable is coax.

Note: With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time
Protocol is used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP - Real
Time Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have mixed
configurations with service profiles using RTP and other service profiles not using RTP. Example: if in
the unit only one E1 has service profile TDM2TDM it is possible to configure other E1 with service
profile TDM2Eth only with the Differential clock source (not with the Adaptive clock source). If the
Adaptive clock source is requested the E1 must be connected to another PDH unit.

3JK Edition 1.00
2.6 STM-1 configuration
Select the type: Enter the Flow ID (range:

Put a check mark in the 2 to 4080). Warning: the
Port Status box to enable Electrical or Optical
flow id must be unique in
the STM-1 the MPR network.
Select the Jitter

Buffer Depth:
High/Low
Select the TDM Clock

Source:
Differential/Node
Timing
Set the Auto Laser Shutdown:

Enable the J0, if required, Enabled/ Disabled ForcedOn/
by selecting one of the two Disabled ForcedOff. This
modes (SixteenBytesFrame/ field will appear only if the
OneRepeatedByte) and in Settings tab-panel of the
the Expected Receiving STM-1 unit the optical SFP
Value field enter the has been selected.
expected value. Note: byte
J0 is only read, no
Regeneration section Enter the
Termination is done. Expected Value


3JK Edition 1.00
2.7 Modem Provisioning
Modem Configuration Screen (without Adaptive Modulation)

The Revertive Restoration
Check to enable Criteria are available only
PPP RF port. in 1+1 configuration, if
The user can you want traffic on the
select: protection channel to
Static routing or automatically switch back
OSPF Area to the main channel when
alarms clear or a switch
Tick to enable the command is released.
SSM Transmission
over the radio Select the suitable reference
channel channel spacing.
Check to enable Select the modulation scheme.

radio ID mismatch
function. No check mark here.

Enter number from 1 to Transmitter ID. Must match associated
255 for Receiver ID. Transmitter ID at other end of hop.
Must match associated
Receiver ID at other
end of hop.


3JK Edition 1.00
2.7 Modem Provisioning [cont.]
No check mark here.

Select the
frequency
separation from Select the suitable
drop-down list. reference channel
spacing
Check to enable ATPC.

Select the
modulation scheme
Enter the Tx RF
frequency within
the allowed range.
Enter the Tx Power


3JK Edition 1.00
Modem Configuration Screen (with Adaptive Modulation)

Enable PPP RF port.
The user can select:
Static routing or
OSPF Area
Tick to enable the SSM

Transmission over the
radio channel
The Revertive Restoration
Check to enable radio Criteria are available only in
ID mismatch function. 1+1 configuration, if you want
traffic on the protection
channel to automatically
Enter number from 1 to 255 switch back to the main
for Transmitter ID. Must channel when alarms clear or
match associated Transmitter a switch command is released.
Check mark to enable the Adaptive
Enter number from 1 to 255 Modulation. The only available
for Receiver ID. Must match configuration is: 1+0, 1+1 HSB.
associated Receiver ID at
other end of hop. Enter the Tx Power.

Note 1: With the Adaptive Modulation the only available configuration is: 1+0 or 1+1 HSB.
Note 2: The operator can modify only the 4 QAM field. In this field the operator has to enter the
constant power, which will be used with 4 QAM modulation. The power range is shown on the right side
and depends on the selected reference mode.
The same power value will be used by the 16 QAM and 64 QAM modulation schemes.

3JK Edition 1.00
Check mark Select in the Reference Channel

to enable the Spacing field the suitable channel
Adaptive spacing.
Modulation.
The only
available Select in the
configuration Thresholds field
is: 1+0, 1+1 how many dB
HSB. the switching
thresholds have
Select the to be moved
frequency from the default
separation value (+4 dB/-2
from drop- dB). The default
down list. value is approx.
6 dB below the
10-6 Rx
Enter the Tx threshold.
RF frequency
within the
allowed range.
Select in the Scheme field the
Select in the Reference Modulation range (4/16 QAM
Mode field the spectral or 4/16/64 QAM) to be used by
efficiency class to be set the Adaptive Modulation.
as reference.


3JK Edition 1.00
2.8 MPT Access configuration (1+0)
Enable one or two of

the four ports by
selection the MPT
type: HC or MC:
Port#1 and Port#2 are
electrical Ethernet
ports and Port#3 and
Port#4 are optical
Ethernet ports.

N.B.: The selection of the Power Supply mode, used to supply the MPT (through 1 cable for MPT-MC or
MPT-HC with the DC Extractor or through 2 cables for MPT-HC) mst be done only with WebEML.

3JK Edition 1.00
2.9 MPT Access Provisioning
MPT Access Provisioning (without Adaptive Modulation)

Check to enable PPP RF port.
Static routing or
OSPF Area
Tick to
enable the
SSM
Transmission
over the
radio channel Select the suitable reference
channel spacing.
Check to
enable radio Select the modulation scheme.
ID mismatch
function. Select in the ETSI mask field the
spectral efficiency class to be set as
Enter number reference: None, Old ETSI mask or
from 1 to 255 for New ETSI mask
Transmitter ID.
Must match No check mark here.
associated
Transmitter ID at Enter number from 1 to 255 for
other end of hop. Receiver ID. Must match associated
Receiver ID at other end of hop.


3JK Edition 1.00
2.9 MPT Access Provisioning [cont.]
Select Tx (Go)
and Rx (Return)
separation
frequency from
drop-down list.
Check mark to enable

ATPC, if required.
Enter the Tx RF frequency

within the allowed range.
Enter the Tx Power


3JK Edition 1.00
MPT Access Provisioning (with Adaptive Modulation)
Check to enable
PPP RF port.
Tick to enable The user can
the SSM select:
Transmission Static routing or
over the radio OSPF Area
channel
Check to
enable radio
ID mismatch Check mark to enable the Adaptive
function. Modulation.
Enter number
from 1 to 255 for Enter the Tx Power
Transmitter ID.
Must match
associated
Transmitter ID at
other end of hop. Enter number from 1 to 255 for
Receiver ID. Must match associated
Receiver ID at other end of hop.


3JK Edition 1.00
Choose in the Supported Modulation field all the modulation schemes to be used with the Adaptive
Modulation. The modulation schemes (from the lowest to the highest scheme) must be contiguous.
Select the frequency separation

from drop-down list.
Enter the Tx RF frequency

within the allowed range.
Select in the ETSI mask field the

spectral efficiency class to be set
as reference: None, Old ETSI
mask or New ETSI mask.
Select in the Reference Mode field Select in the MSE Driving Criteria field the suitable
the spectral efficiency class to be value. In 1+1 FD and HSB configurations both the
set as reference. transmitters can be driven in a not relevant mode
(0) or by the lowest (1) or by the highest MSE
values (2) of the two remote demodulators.
Select in the Reference Channel Select in the Remote Switching Threshold field how many
Spacing field the suitable channel dB the switching thresholds have to be moved from the
spacing. default value (+4 dB/-2 dB). The default value is approx.
6 dB below the 10-6 Rx threshold.


3JK Edition 1.00
2.10 MPT Access configuration (prot. enabling: 1+1)
Enable one of the four ports for the

unit on the left side and on the
right side: Port#1 and Port#2 are
electrical Ethernet ports and
Port#3 and Port#4 are optical
Ethernet ports.
Click on Add to enable the

protection scheme
Select the protection scheme:

1+1 HSB, 1+1 FD.
With MPT-MC only 1+1 HSB
Select the Ports used in the

protection scheme


3JK Edition 1.00
2.11 MPT Access Prov. (without A. M.) (1+1)
Check to enable
PPP RF port.
The user can Select Revertive feature if
select: you want traffic on the
Static routing or protection channel to
OSPF Area automatically switch back
to the main channel when
alarms clear or a switch
Tick to enable command is released.
the SSM
Transmission Select the suitable reference
over the radio channel spacing.
channel
Select the modulation scheme.
Check to
enable radio
ID mismatch Select in the ETSI mask field the
function. spectral efficiency class to be set as
reference: None, Old ETSI mask or
New ETSI mask
Enter number
from 1 to 255 for No check mark here.
Receiver ID. Must
match associated Enter number from 1 to 255 for
Receiver ID at Transmitter ID. Must match associated
other end of hop. Transmitter ID at other end of hop.


3JK Edition 1.00
2.11 MPT Access Prov. (without A. M.) (1+1) [cont.]
Select Tx (Go)
and Rx (Return)
separation
frequency from
drop-down list.
Enter the Tx RF
frequency within
the allowed range.
Check mark to
enable the ATPC,
if required
Enter the Tx Power


3JK Edition 1.00
2.12 MPT Access Prov. (with A. M.) (1+1)
Check to enable PPP RF port.
Static routing or
OSPF Area
Tick to enable
the SSM
Transmission
over the radio Select Revertive feature
channel if you want traffic on
the protection channel
to automatically switch
Check to enable radio back to the main
ID mismatch function. channel when alarms
clear or a switch
Enter number from 1 to 255 command is released.
for Transmitter ID. Must
match associated
Transmitter ID at other end
of hop.
Enter number from 1 to Check mark to enable the Adaptive

255 for Receiver ID. Must Modulation. The available
match associated configurations are: 1+1 HSB, 1+1
Receiver ID at other end FD.
of hop.
Enter the Tx Power.


3JK Edition 1.00
2.12 MPT Access Prov. (with A. M.) (1+1) [cont.]

field the suitable channel spacing.
The Remote
Switching
Select in the Reference Mode Threshold field
field the spectral efficiency is not
class to be set as reference. supported.
Select the frequency

separation from
drop-down list. Select in the MSE
Driving Criteria
field the suitable
Enter the Tx RF value. In 1+1 FD
frequency within and HSB
the allowed range. configurations both
the transmitters
Select in the ETSI mask field the spectral can be driven in a
efficiency class to be set as reference: not relevant mode
None, Old ETSI mask or New ETSI mask. (0) or by the lowest
(1) or by the
highest MSE values
Choose in the Supported Modulation field all the (2) of the two
modulation schemes to be used with the Adaptive remote
Modulation. The modulation schemes (from the demodulators.
lowest to the highest scheme) must be contiguous.


3JK Edition 1.00
2.13 Synchronization Configuration
Master
Synchronization
Role: Master.
Restoration Criteria:
- Revertive - Switches sync
source back to primary source
after alarm on primary source
clears.
- Non-Revertive - Does not switch
back to primary source after
primary alarm clears and stays on
secondary sync source.
This field will appear, if as Source Synch-Out Port configuration -

(Primary or Secondary) has been Connector that can be used to
selected the Synch-In port: provide sync to another radio
1.024 MHz, 2.048 MHz, 5 MHz, or ancillary equipment: 1.024
10 MHz. MHz, 2.048 MHz, 5 MHz,
10 MHz.


3JK Edition 1.00
2.13 Synchronization Configuration [cont.]
Primary source:
- Synch-In Port - Clock from
external source received on the
Sync In connector on the Core card.
-Any available E1 - Clock from E1
source via E1 peripheral.
-Any available Synch-E - Clock
from Giga Ethernet traffic.
-Any available STM-1 port
- Clock from STM-1 source via STM-
1 peripheral.
- Free Run Local Oscillator - Local
oscillator on Core Card.
This field will appear, if a Secondary source:

Secondary Source has been - Synch-In Port - Clock from external
selected. Select the suitable source received on the Sync In
configuration. connector on the Core card.
-Any available E1 - Clock from E1
source via E1 peripheral.
-Any available Synch-E - Clock from
Giga Ethernet traffic.
-Any available STM-1 port - Clock from
Enter the WTR time in the range STM-1 source via STM-1 peripheral.
0-12 minutes at 10 second step. - Free Run Local Oscillator
(Default: 5 minutes) - Local oscillator on Core Card.


3JK Edition 1.00
Slave
Synchronization
Role: Slave.
This field will appear, if

as Primary Source has
been selected the Rx
Symbol Rate. Select the
radio slot to be used.
Synch-Out Port configuration -

Connector that can be used to
provide sync to another radio
or ancillary equipment: 1.024
MHz, 2.048 MHz, 5 MHz,
10 MHz.
This field will appear, if as Secondary Source has

been selected the Any available E1.
Select the slot number and the E1 tributary number.


3JK Edition 1.00
Primary source:
- Synch-In Port - Clock from
external source received on the
Sync In connector on the Core
card.
- Any available Synch-E - Clock
from Giga Ethernet traffic.
- Rx Symbol Rate - Clock
extracted from the radio side.
Secondary source:
- Synch-In Port - Clock from external
source received on the
Sync In connector on the Core card.
This field will appear, if as - Any available E1 - Clock from E1
Source (Primary or Secondary) source via E1 peripheral.
has been selected the Synch-In - Any available Synch-E - Clock from
port: 1.024 MHz, 2.048 MHz, Giga Ethernet traffic.
5 MHz, 10 MHz. - Any available STM-1 port - Clock from
STM-1 source via STM-1 peripheral.
- Rx Symbol Rate - Clock extracted
from the radio side.
- Free Run Local Oscillator - Local
oscillator on Core Card.


3JK Edition 1.00
2.14 Cross Connections Configuration
By pressing Alt+W the

Segregated Port View
opens (refer to the
next figure).

Note: To create the Cross-Connection refer to S3_M1 par. 3.5 where the explanation refer to the JUSM
menu. The creation procedure is identical. The only difference is in pushbutton Apply, Refresh and
Close: not available in the Provisioning tool.

3JK Edition 1.00
2.15 Segregated Port Configuration
By pressing Alt+W the

Cross Connection
View opens (refer to
the previous figure).

Note: To segregate the ports refer to S3_M1 par. 3.5 where the explanation refer to the JUSM menu.
The procedure is identical. The only difference is in pushbutton Apply, Refresh and Close: not available
in the Provisioning tool.

3JK Edition 1.00
2.16 802.1D management
When the NE is configured in this

mode (default configuration), the
Ethernet traffic is switched according
to the destination MAC address
without looking the VLAN. The
packets from the user Ethernet ports
having the VLAN ID out the allowed
range (0 and 2-4080) are dropped.
The packets having a VLAN ID already
used for a TDM flow are accepted.


3JK Edition 1.00
2.17 802.1Q management
When the NE is
configured in this mode,
the management of
Ethernet traffic looking
the VLAN is enabled. In
this mode, one VLAN
will be assigned to all
Ethernet frames inside
the MPR network.
VLAN 1 Management
VLAN-ID 1 is automatically defined by the NE when the
802.1Q bridge type is selected. VLAN-ID 1 is shown to the
operator, but it can-not be neither changed nor deleted.
All the user Ethernet ports (enabled and disabled) and all
the radio ports are members of the VLAN 1. In egress
VLAN-ID 1 is always removed from all the ports.


3JK Edition 1.00
2.17 802.1Q management [cont.]
DEL VLan: to delete a VLAN-ID. It is possible

to remove a VLAN-ID from the VLAN-ID table
even if this VLAN-ID has been already
EDIT VLan: to change the configured on one or more user ports as Port
parameters of a VLAN (VLAN VLAN to be added in ingress to untagged
name, VLAN member ports, frames. As consequence, the VLAN-ID=1 and
VLAN untagged ports in egress). PRI=0 are added to the untagged frames
received on this port. Before applying this
deletion, a confirmation of the operation is
ADD VLan: to create a shown to the operator.
new VLAN (refer to VLAN
management figure)
By clicking Next the Port VLan
configuration screen opens


3JK Edition 1.00
2.18 VLAN Management

[1] VLAN ID field: Enter the VLAN ID (the configurable values must be in the range 2 - 4080)
N.B.: The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) can-not
be used.
[2] VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.
[3] VLAN Ports field: Select the ports members of this VLAN by putting a check mark on the relevant
check box. All the user Ethernet ports and all the Radio directions can be considered. Both enabled and
disabled user Ethernet ports (radio ports when declared are implicitly enabled) can be member of a
VLAN. This means that a disabled port can be configured as a member of a VLAN and a port already
member of a VLAN can be disabled continuing to be a member of the same VLAN.
[4] Untagged Ports field: Select, among the ports belonging to this VLAN (members), the untagged
ports (in egress the VLAN will be removed from the frames). Only the user Ethernet ports, enabled and
disabled, are manageable. The VLAN cannot be removed from the radio ports (with the exception of
the VLAN 1).
the ports are members and the Untag flag is set to False, which means all the frames are trans-
mitted with Tag.
N.B.: Tagged frames - If one tagged packet with VLAN-ID X is received on a port which is not member of
the VLAN-ID X, the packet is dropped.

3JK Edition 1.00
2.19 Port VLAN Configuration
The untagged
frames, received
If the untagged on each user
frames are accepted, Ethernet port (port
the VLAN-ID and 1 to 4, and port 5
Priority fields must if the optical SFP
be configured. Only plug-in has been
VLAN-ID values installed and
already defined (in configured), can
the VLAN be Accepted or
management menu) Discarded.
can be configured for
this purpose. The
Priority values
allowed are in the
range 0 - 7.
The default Port
VLAN-ID and Priority
values are: VLAN-
ID=1; Priority=0.
VLAN 1 is always
removed, when the
frame is forwarded.

Note: The Port VLan Configuration screen opens only if in the Bridge Configuration screen the 802.1Q
(Virtual Bridge) has been selected.

3JK Edition 1.00
2.20 Network Configuration
Enter local Enter IP Address for radio.

IP Address.
Enable TMN VLAN
feature on Core-E.
Select Static Routing

for manual routing.
Select OSPF (Open
Shortest Path First
Protocol) for automatic
routing.


3JK Edition 1.00
2.20 Network Configuration [cont.]
Enter the
parameters for
the TMN In-band
management (if
required)
Enter the
IP address
Enable the NTP of the
Protocol. Spare
(standby)
NTP
server.
Enable the IP address of
the Main NTP server.


3JK Edition 1.00
2.21 Trusted Managers
The default UDP Port is 5010, The Manager Type cannot be

but with a click on this column changed (it is fixed tp 5620
another port can be configured SAM)
To remove a manager select the

To activate a trusted manager click on manager from the list and clik on
Add Manager, then click on the IP Remove Manager(s).
Address column and write the IP The multiple selection of different
address of the SNMP manager. managers can be done to remove
To confirm the selection click Enter. more than one manager in one shot.

A Trusted manager is an SNMP manager to which the NE automatically sends the TRAPS generated
inside the NE.

3JK Edition 1.00
2.22 Typical Report Panel

Buttons:
Prev: the procedure goes back to the previous step
Save: allows to save the configuration file
Apply: it is operative only if you are physically connected to the NE and it activates the download of
the configuration to the NE
Cancel: the procedure goes back to step 1 (Opening screen)

3JK Edition 1.00
Exercise
Configure completely the NEs of the training center by following the

procedure given in this section.


3JK Edition 1.00
Blank Page


3JK Edition 1.00
End of Module
Initial configuration MPR node


3JK Edition 1.00
33
Section 3
NE operation
Module 3
Performance monitoring MPR node
3JK Edition 1.00

3JK Edition 1.00
Blank Page

NE operation Performance monitoring MPR node
Document History
01 2007-07-30 External consultant First edition

Vimercate

3JK Edition 1.00
Objectives
activate and evaluate the Performance Monitoring application.


3JK Edition 1.00
Objectives [cont.]


3JK Edition 1.00
Table of Contents
1 WT Performance Monitoring Suite 7

1.1 Introduction 8
1.2 How to start the WT Performance Monitoring Suite 9
1.3 Tool bar 10
1.4 Menu bar 11
1.4.1 Export 12
1.4.2 Print 14
1.5 Menu available on the Birds Eye View 15
1.6 PM selectable options 16
1.7 How to start the PM 17
1.8 How to stop the PM 19
1.9 Offline Mode 20
1.10 Ethernet Statistics 22
1.10.1 CORE-ENH unit Ethernet Statistics 23
1.10.1.1 Ethernet Aggregate Tx 24
1.10.1.2 Ethernet Aggregate Rx 25
1.10.1.3 Port Custom view 26
1.10.1.4 Example of the other views 27
1.10.2 MPTACC unit and MD300 Ethernet Statistics 29
1.10.2.1 Queue #1 to Queue #5 32
1.10.2.2 Ethernet Aggregate Tx 33
1.10.2.3 Customized view builder (Aggr.Tx and Queues) 34
1.10.2.4 Example of the other views 35
3 3 5 1.11 RADIO PMs All Rights Reserved Alcatel-Lucent 2011 38
1.11.1 RADIO PMs
performance monitoring procedures 40
1.11.2 Radio Custom view 43
1.11.3 Manage Thresholds 44
1.11.4 How to display a threshold 45
1.11.5 How to create a new threshold 46
1.11.6 How to delete a threshold 48
1.11.7 How to associate a threshold 49
1.12 PDH Performance Monitoring 50
1.12.1 P32E1DS1 unit performances 51
1.12.2 Incoming 52
1.12.3 Outgoing 54
1.12.4 Customized view builder 55
1.12.5 Manage Thresholds 56
1.12.5.1 How to create a new threshold table 57
1.12.5.2 How to delete a threshold 58
1.12.5.3 How to associate a threshold 59
1.12.6 Example of the other views 60
1.13 IMA Layer Statistics 62
1.13.1 IMA Group Monitoring 63
1.14 ATM Interface Statistics 66
1.14.1 Interface 67
1.14.1.1 Not Logical VPs and Logical VPs 68
Exercise 71
Exercise 72
Blank Page 73
End of Module 74

3JK Edition 1.00


3JK Edition 1.00
1 WT Performance Monitoring Suite


3JK Edition 1.00
1.1 Introduction
To open the WT Performance Monitoring Suite click on the relevant icon

in the Menu bar as shown in the figure.
WT Performance Monitoring
Suite icon
The WT Performance Monitoring Suite provides PM measurements for

Ethernet, Radio, E1, IMA and ATM user lines.


3JK Edition 1.00
1.2 How to start the WT Performance Monitoring Suite
The WT Performance Monitoring Suite can be invoked from WebEML by

clicking the WT Performance Monitoring Suite icon button in the Main
Tool Bar. This operation opens the WT Performance Monitoring Suite
view described in the following


3JK Edition 1.00
1.3 Tool bar
The Tool bar provides an interface to collect the performance data

from NE network elements and provides the basic functionalities to
collect the performance related statistics and other types of
measurements.

The buttons shown in the above figure, have the following functionalities:
"Close" command removes a NE from NE list
"Move to front" command moves a selected NE performance monitoring view to the front.
"Move to back" command moves a selected NE performance monitoring view to back.
"Sort" command orders each NE performance monitoring view.
"Background" command set the background colour of NE performance monitoring view.
"Start/Stop" command starts or stops the counters for the data collection, when the CD (Current
Data) has been stopped or started.
"Refresh" command retrieves the current PM reports form NE and update the table view and chart
view with the recently collected data.
"Reset" button resets the data collection and related counters.
"Archive" button archives current PM reports.
"Export" button saves the report
"Print" button prints the user selected performance point
Offline Mode button saves the current status of the WT Performance Monitoring Suite to have later
the possibility to see the PM offline
"List View" to display all PM points' table view and chart view in one screen.
"Overview" button to display a selected PM point's chart view in one screen
"Birds Eye View" button displays a selected PM point's table view and chart view in one screen
"Note" button shows the meaning of each parameter.
"Help" button show help content

3JK Edition 1.00
1.4 Menu bar
The following menus are available:

File: Export
Print
Exit
Network: List View
Overview
Birds Eye View
Action: Close
Windows: it shows the IP address of the NEs
Help: it shows some information on the Help
In the Menu bar are available the same menus present in the Tool bar.


3JK Edition 1.00
1.4 Menu bar
1.4.1 Export
This menu allows to export in specific CSV files all the active
performance tables.
By selecting this menu the following screen opens.
Select the directory (or create a new folder) and click on Open.


3JK Edition 1.00
1.4 Menu bar
1.4.1 Export [cont.]
The tables are saved individually in a specific file with IP address of the
NE, slot number of the unit and type of the counter as shown in the
following figure.


3JK Edition 1.00
1.4 Menu bar
1.4.2 Print


3JK Edition 1.00
1.5 Menu available on the Birds Eye View
By right clicking with the mouse on the graphic the following menu will
appear:
Copy: to storage the image
Save as: to save the image as .png or .jpeg
Print: to print the image
Zoom In: to enlarge the image
Zoom Out: to shrink the image
AutoRange: to fit the image


3JK Edition 1.00
1.6 PM selectable options

Several tab-panels can be present:

NEs List: it includes all the NEs, which launched the application
Specific tab-panel (identified by the NE IP address) for each NE, which launched the application.
By clicking an NE in the NEs List or in the specific NE tab-panel, the available PM will appear.
The following types of Performance Monitoring are available:
1. Ethernet Statistics
2. Radio PM
3. PDH PM
4. IMA Layer Statistics
5. ATM Interface Statistics
In the left area a small rounded icon is associated to each object, taking the color and the letter of
the object alarm condition (C = Critical, M = Major, m = minor, W = Warning).

3JK Edition 1.00
1.7 How to start the PM

1) Select the type of PM. In the example shown in the figure which follows, Ethernet Statistics has been
selected.
2) Select the slot. The slot selection corresponds to the selection of the unit. In the example which
follows Ethernet Statistics has been selected. The selection of the unit will cause the display of the
counters of all its subordinate objects, i.e. in this example the counters of all equipped ports will be
displayed.
3) Optionally, after the selection of the unit, you can select one of its subordinate objects. In this case,
only the selected object is highlighted in the frame area.
N.B.: The PM can be started individually or at slot level.
4) Start the counters by pressing button Stopped. Button Stopped (red-colored) changes appearance
and becomes green.
The start time is displayed in the Configuration area (left-lower part of the window). In the
configuration dialog box, you can select the collecting interval and Duration. Available collecting
intervals are 5s,10s,30s and 60s. The Duration is from 1 hour to 24 hours.

3JK Edition 1.00
1.7 How to start the PM [cont.]


3JK Edition 1.00
1.8 How to stop the PM
To stop PM application select the counter and click Stop button. Start
and Stop buttons are shown below.

N.B.: The PM can be stopped individually or at slot level.

3JK Edition 1.00
1.9 Offline Mode
By clicking the Offline button on the Tool-bar the current status of the
WT Performance Monitoring Suite is saved.
Write the archive name and click OK.
Click on Yes to save the current NE status.


3JK Edition 1.00
1.9 Offline Mode [cont.]
The current status is saving.
Close NEtO. Click on the Offline Mode icon on the Desktop.
The screen in figure opens. Select the file and click on OK.
Now the WT Performance Monitoring Suite previously saved open and

you can navigate in all the menus.


3JK Edition 1.00
1.10 Ethernet Statistics
This option provides Ethernet PM statistical counters.

In the left area select bar Ethernet Statistics. The selected bar is moved to
the upper part of the left tree area.
You can expand the tree view of slots 1-8.
The slot equipped by CORE-ENH unit allows to select the enabled user ports
1-6.
The Ethernet Statistics are available in the Core-ENH unit, in MPTACC unit
and in MD300 unit. The MPTACC unit is the interface to MPT-HC/MPT-MC; the
MD300 unit is the interface to ODU300.


3JK Edition 1.00
1.10.1 CORE-ENH unit Ethernet Statistics
1) From the left-hand side tree execute the suitable selection of the
CORE-ENH unit, to get the display of the counters of all ports.
2) From the Configuration subwindow (lower left side of the window),
select the Interval (the collection time of the performances): 4, 6, 30,
60 seconds. The default value is 4 sec. From the same subwindow
select the Duration of the performance monitor in hour and minutes.
The max. duration is 24 hours.
3) Click on the Start button to start the monitoring.
4) The right-hand area contains the statistic data for the Ports.
Per each port the following tabs are selectable:
Ethernet Aggregate Tx
Ethernet Aggregate Rx
Custom view

N.B.: Ethernet Counters can be displayed in three different modalities:

List View
Overview
Birds Eye View
In the example, the List View is shown. To display the other views select in the Menu bar the view or
click the view on the relevant icon in the Tool bar.

3JK Edition 1.00
1.10.1.1 Ethernet Aggregate Tx

The available performances at port level are (see Port 1 selected in the above figure):
TTO: total number of octets of Ethernet frames transmitted out by the Interface, including Ethernet
header characters.
TTF: total number of Ethernet frames transmitted out by the interface.
TDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer
congestion.
TTF Unicast: total number of Ethernet Unicast frames transmitted out by the Virtual Ethernet
Interface.
TTF Multicast: total number of good packets transmitted by this address that were directed to a
multicast address. This number does not include packets directed to the broadcast address.
TTF Broadcast: total number of good packets transmitted by this address that were directed to the
broadcast address.

3JK Edition 1.00
1.10.1.2 Ethernet Aggregate Rx

The available performances at port level (see Port 1 selected in the above figure):
TRO: total number of octects of Ethernet frames received by the Virtual Ethernet Interface, including
Ethernet header characters.
TRF: total number of Ethernet frames received by the Virtual Ethernet Interface.
TRSEF: total number of errored frames.
TDF: total number of Ethernet frames which were chosen to be discarded due to buffer congestion.
TRF Unicast: total number of Ethernet Unicast frames received correctly by the Virtual Ethernet
Interface.
TRF Multicast: total number of good packets received that were directed to a multicast address. This
number does not include packets directed to the broadcast address.
TRF Broadcast: total number of good packets received that were directed to the broadcast address.
This number does not include multicast packets.

3JK Edition 1.00
1.10.1.3 Port Custom view
You can customize the view by clicking on tab Custom View.

The customized View Builder box is presented.

The view is divided into two areas:

left area which contains the list of the selectable counters
right area which contains the list of the selected counters
The user can select a counter on the left area and by clicking the upper arrow move it to the right area
in order to customize the counter view.
The opposite operation can be done by selecting the counter in the right area and by clicking the lower
arrow to move it to the left area.
Click on OK button to confirm.

3JK Edition 1.00
1.10.1.4 Example of the other views

Note: Click on the Navigation bar to change the view.

Note: In the buttom 2 tab-panels show the counters:
Deafult Counters: collected on the NE row
Elaborated Counters: processed on the PC and are available only when the PC is connected to the
NE.

3JK Edition 1.00
1.10.1.4 Example of the other views [cont.]


NE.

3JK Edition 1.00
1.10.2 MPTACC unit and MD300 Ethernet Statistics

In the figure is shown the screen regarding the MPTACC unit. The screen for the MD300 is the same.
N.B.: Ethernet Counters can be displayed in three different modalities:
List View
Overview
Birds Eye View
In the example, the List View is shown. To display the other views select in the Menu bar the view or
click the view on the relevant icon in the Tool bar.

3JK Edition 1.00
1.10.2 MPTACC unit and MD300 Ethernet Statistics [cont.]
The figure which follows shows examples of selection of a MPTACC unit:

MPTACC in slot #3 refers to a 1+1 configuration
MPTACC in slot #4 refers to a 1+0 configuration
MPTACC in slot #5 refers to a non 1+1 configuration


3JK Edition 1.00
1.10.2 MPTACC unit and MD300 Ethernet Statistics [cont.]
Per each Direction the following tabs are selectable:

Queue #1 to Queue #5
Ethernet Aggregate Tx
Custom view

Two types of MPT are available:

MPT-HC (High Capacity), up to 256QAM
MPT-HC (Medium Capacity), up to 128QAM
The MPTACC unit has 8 output queues:

Queue 8 is reserved to TDM2TDM traffic.
Queue 7 is reserved to TDM2Eth traffic.
Queue 6 is reserved to TMN traffic.
The remaining 5 queues are reserved to Ethernet traffic. Queue 5 is the highest priority queue.

3JK Edition 1.00
1.10.2.1 Queue #1 to Queue #5

Select the tab of the queue to display. The available performances at queue level (for each queue) are:
TTO: total number of octets of Ethernet frames transmitted out by the Interface, including Ethernet
header characters.
TDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer
congestion.

3JK Edition 1.00
1.10.2.2 Ethernet Aggregate Tx
The available performances at aggregate level are:

TTO: total number of octets of Ethernet frames transmitted out by the
Interface, including Ethernet header characters.
TDF: total number of Transmitted Ethernet frames which were chosen to be
discarded due to buffer congestion.


3JK Edition 1.00
1.10.2.3 Customized view builder (Aggr.Tx and Queues)
You can customize the view by clicking on tab Custom View.

The customized View Builder box is presented.



3JK Edition 1.00
1.10.2.4 Example of the other views
Modem unit


NE.

3JK Edition 1.00
Birds Eye View - MPT Access unit (Default Counters)


NE.

3JK Edition 1.00
Birds Eye View (Elaborated Counters)


NE.

3JK Edition 1.00
1.11 RADIO PMs
Two different radio sections can be monitored:

Radio Hop Section: the section between two radio stations inside the
protection section
Radio Link Section: the section identifying the protected section.

The performance monitoring (PM) gives indication on the quality of the service.
Quality of service PM is performed in accordance with G.826 and G.784.
It is assumed that the quality of the single tributary (E1, ) can be derived from the quality of the
aggregate signal, therefore no dedicated quality of service PM is foreseen on the single tributaries.
Considering one section (see below figure), one current register is for 15 min report and one for 24 h
report; 96 history data can be stored for 15 min report and 8 history data for 24 h report.
The 24 h Performance Monitoring data are always stored in the History Data report.
N.B.: The 15 min Performance Monitoring data are stored in the History Data report only if errors have
been occurred.

3JK Edition 1.00
1.11 RADIO PMs [cont.]
The counters supported are the following:

Errored Seconds
Severely Errored Seconds (N.B.)
Background Block Error
Unavailable Seconds
The performance reports can be of 2 different types:
15 minutes
24 hours
The following description explains the functions to provide the PM
process with a granularity period of 24 h. The same functions are
provided for 24h PM process.
The PM are of HOP or LINK type:
HOP refers to the PM before the RPS switch.
LINK refers to Performance Monitoring after the RPS switch. The current
report can be seen (and configured) and the history log can be seen.

N.B.: According to ITU--T G.826 a second is declared Severely Errored Second if it is a second period
with more than 30 % of errored blocks or at least one defect.

3JK Edition 1.00
1.11 RADIO PMs
1.11.1 RADIO PMs performance monitoring procedures
RADIO Performance Monitoring provides quality data regarding the radio

channels.
To the RADIO measurements thresholds can be associated. See
procedure which follows.
Only the quality of the aggregate signal is provided.
In the left area select bar RADIO PM. The selected bar is moved to the upper
part of the left tree area.
Select the slot housing the MD300 or the MPTACC unit.
Select the Direction, in this example Direction #3.1/3.2 (MPT-HC).
Select the granularity tab-panel (15 min/24h). In the example which follows
15 min granularity has been selected.

N.B.: Radio Counters can be displayed in three different modalities:

List View
Overview
Birds Eye View

3JK Edition 1.00
1.11 RADIO PMs
1.11.1 RADIO PMs performance monitoring procedures [cont.]
In the following example, the List View is shown.

To display the other views select in the Menu bar the view or click the view on the relevant icon in the
Tool bar.
The following tabs are selectable:

Hop Ch 0 (Stand-by channel)
Hop Ch 1 (Working channel)
Link (RPS switch included)
In the example which follows Hop Ch 1 has been selected.

3JK Edition 1.00
1.11 RADIO PMs
1.11.1 RADIO PMs performance monitoring procedures [cont.]

The view contains the following collection data parameters:

Time. It displayes the time of the Performance Monitoring. This time changes after the Auto
Refresh.
Elapsed Time. It displays the elapsed time in the current interval of monitoring.
Suppressed Intervals. It displays the number of intervals (reports) suppressed in the History because
they dont have errors.
Suspect. It contains a flag symbol in case of suspect of data inconsistency.
N.B.: An interval is defined as suspect if at least one of the following conditions occurs in the
collection period:
the elapsed time deviates more than 10 seconds of the nominal time
loss of the Performance Monitoring data in the equipment
performance counters have been reset during the interval.
The displayed counters are:

BBE (Background block Errors)
ES (Errored Seconds)
SES (Severily Errored Seconds)
UAS (Unavailable Seconds)

3JK Edition 1.00
1.11 RADIO PMs
1.11.2 Radio Custom view
You can customize the view by clicking on tab Custom View. The
customized View Builder box is presented.



3JK Edition 1.00
1.11 RADIO PMs
1.11.3 Manage Thresholds
It describes how to display or change or create the thresholds assigned

to Performance Monitoring counters.
There are threshold tables for the HOP and for the LINK.
There are two default thresholds for HOP: Threshold #1 (to be
associated to 15 min report) and Threshold #4 (to be associated to 24
h report).
There are two default thresholds for LINK: Threshold #1 (to be
associated to 15 min report) and Threshold #3 (to be associated to 24
h report).
The user can manage thresholds to be associated to Hop or Link 15min
report or 24h report. The following actions are available, starting from
button Manage Thresholds in the Configuration area:
Thesholds display
Create threshold
Delete threshold
Associate a threshold to a monitoring point


3JK Edition 1.00
1.11 RADIO PMs
1.11.4 How to display a threshold
Click on button Manage Thresholds. The Manage Thresholds subwindow

is displayed.


3JK Edition 1.00
1.11 RADIO PMs
1.11.5 How to create a new threshold

Four threshold tables can be created for the HOP (Threshold #2, #3, #5 and #6).
Two threshold tables can be created for the LINK (Threshold #2 and #4).
Two standard thresholds are available for the HOP (Threshold #1, #4).
Two standard thresholds are available for the LINK (Threshold #1 and #3).
To create a new threshold:
1. Click on Manage Thresholds button. The Manage Threshold subwindow opens.
2. Select HOP or LINK.

3JK Edition 1.00
1.11 RADIO PMs
1.11.5 How to create a new threshold [cont.]

3. Select the Measurement type: 15 min or 24 h.

4. Enter the values for the Low and High thresholds.
5. Click on Create. Automatically the new threshold takes a name with a progressive number. See below
the figure.

3JK Edition 1.00
1.11 RADIO PMs
1.11.6 How to delete a threshold
Only the created thresholds can be deleted. The default thresholds

can be only displayed.
1. Select the Threshold to be deleted and click on Delete button.


3JK Edition 1.00
1.11 RADIO PMs
1.11.7 How to associate a threshold
You can assign the desired theshold to a certain Monitoring Point.

Execute the following steps:
1. From the left-hand side lower Configuration area select the Monitor Point.
2. Select the Collection Period (15 min or 24h )
3. Select the Threshold. The list of the available thresholds for the previously
selected Monitoring Point is presented by clicking on the down arrow beside
the field name (threshold in this case).
4. Notice that only the thresholds applicable to the selected Monitoring Point
are presented.
5. The Threshold to be selected is identified by a number, in accordance to
the detailed list contained in the upper area of the Manage Thresholds
dialog box.
6. Click on Apply button to confirm the assignment.


3JK Edition 1.00
1.12 PDH Performance Monitoring
The PDH Performance Monitoring are available in the P32E1DS1 unit.


3JK Edition 1.00
1.12.1 P32E1DS1 unit performances
Selecting the P32E1DS1 unit, the Performance Monitoring (PM) gives indication
on the quality of the E1 Tributaries, which have been configured as "Framed".
E1 Tributaries, configured as "Framed" are shown in bold; for all the other E1
Tributaries (in grey) the performance are not available, because the relevant
streams are disabled or they have been configured as "Unframed".
Two types of performances are available:
Incoming: performances detected at the input in Tx side.
Outgoing: performances detected at the output in Rx side.
The Quality is performed in accordance with G.826 and G.784.
The performance reports are of 2 different types:
15 minutes
24 hours
The following description explains the functions to provide the Performance
Monitoring process with a granularity period of 15 min. The same functions are
provided for 24h Performance Monitoring process.
Incoming
Outgoing
Customer View

Note: 9500MPR is transparent regarding the E1 stream. The CRC is used to detect the quality of the E1
stream.
Note: For a better quality in the Performance Monitoring it is recommended to start up to 128 E1 PM
counters on the same NE. This means 4 counters (Incoming 15 Minutes, Incoming 24 hours, Outgoing 15
Minutes and Outgoing 24 Hours) for 32 E1 streams.
Note: Stability measurement on Ethernet counters (with duration from few hours to 24 Hours) should
be performed by selecting an high value (60 seconds) as collection time of the performances (refer to
parameter Interval in the Configuration subwindow).
N.B.: The Counters can be displayed in three different modalities:
List View
Overview
Birds Eye View
In the following example, only the List View is shown. To display the other views select in the Menu bar
the view or click the view on the relevant icon in the Tool bar.

3JK Edition 1.00
1.12.2 Incoming


3JK Edition 1.00
1.12.2 Incoming [cont.]
The displayed parameters are:

Time. It displays the time of the Performance Monitoring. This time changes
after the Auto Refresh
Elapsed Time. It displays the elapsed time in the current interval of
Performance Monitoring.
Suppressed Intervals: number of intervals (reports) which are automatically
suppressed, because they dont have errors.
Suspect: shows whether the data are suspect or not (Note).
BBE (Background Block Errors)
ES (Errored Second)
SES (Severely Errored Second)
UAS (Unavailable Second).

Note: An interval is defined as Suspect if at least one of the following conditions occurs in the
collection period:
Note: These values refer to the last refresh performed with the Refresh button in the Tool bar.

3JK Edition 1.00
1.12.3 Outgoing
The displayed parameters are:

Time. It displays the time of the Performance Monitoring. This time changes
after the Auto Refresh
Elapsed Time. It displays the elapsed time in the current interval of
Performance Monitoring.
Suppressed Intervals: number of intervals (reports) which are automatically
suppressed, because they dont have errors.
Suspect: shows whether the data are suspect or not (Note).
BBE (Background Block Errors)
ES (Errored Second)
SES (Severely Errored Second)
UAS (Unavailable Second).

collection period:
Note: These values refer to the last refresh performed with the Refresh button in the Tool bar.

3JK Edition 1.00
1.12.4 Customized view builder
The user can select a counter on the left area and by clicking the upper
arrow move it to the right area in order to customize the counter view.
The opposite operation can be done by selecting the counter in the
right area and by clicking the lower arrow to move it to the left area.


3JK Edition 1.00

There are two default threshold:

Threshold #1 (to be associated to 15 min report)
Threshold #4 (to be associated to 24 h report).

3JK Edition 1.00
1.12.5.1 How to create a new threshold table
To create a new threshold table:

Click on the Manage Threshold. The E1 Threshold screen will appear.
Select the Measurement type: 15 min or 24 h.
Enter the values for the Low and High thresholds.
Click on Create. Automatically the new threshold takes a name with a
progressive number.

Note: Four threshold tables can be created (Threshold #2, #3 for 15 min report and #5 and #6 for 24 h
report).

3JK Edition 1.00
1.12.5.2 How to delete a threshold
Click on the Threshold to be deleted in the upper area of Manage

Thresholds window.
Click on Delete button to delete the threshold.

Note: Only the created thresholds can be deleted. The default thresholds can be only displayed.

3JK Edition 1.00
1.12.5.3 How to associate a threshold
To associate a Threshold to E1 tributary:

From the left-hand side lower Configuration area select the Monitor Point
(Incoming/Outgoing).
Select the Collection Period (15 min or 24h )
Select the Threshold. The list of the available thresholds for the previously
selected Monitoring Point is presented by clicking on the down arrow beside
the field name (threshold in this case).
Notice that only the thresholds applicable to the selected Monitoring Point
are presented.
The Threshold to be selected is identified by a number, in accordance to the
detailed list contained in the upper area of the Manage Thresholds dialog
box.
Click on Apply button to confirm the assignment.


3JK Edition 1.00
1.12.6 Example of the other views


NE.

3JK Edition 1.00
1.12.6 Example of the other views [cont.]


NE.

3JK Edition 1.00
1.13 IMA Layer Statistics
The IMA Layer Statistics are available with the A16E1DS1 unit.


3JK Edition 1.00
1.13.1 IMA Group Monitoring
For each configured and active IMA

Group the following counters are
available:
Unavail Secs: counter of the seconds
where the IMA group traffic state
machine is down.
NeNumFailures: counter of the
number of times a failure alarm
condition (Config-Aborted,
Insufficient-Links, Config-Aborted-FE,
Insufficient-Links-FE, Blocked-FE)
has been reported for Near-End IMA
Group.

The quality of IMA Group and Links is evaluated by monitoring IMA Group and Link Counters.
This monitoring is based on IMA standard.
The Counters can be displayed in three different modalities:

List View
Overview
Birds Eye View

3JK Edition 1.00
1.13.1 IMA Group Monitoring [cont.]
For each active IMA link, belonging to an activated IMA Group, the
following counters are available:
IMA Violation: counter of errored, invalid or missing ICP cells, except during
SES-IMA or UAS-IMA conditions;
OIF (Out of IMA Frame) anomalies: counter of OIF anomalies, except during
SES-IMA or UAS-IMA conditions;
NeSES (Severly Errored Seconds): counter of one second intervals containing
more then 30% of the ICP cells counted as IMA Violation, or one or more
link defects (e.g., LOS,OOF/LOF, AIS, or LCD), LIF defects, or LODS defects,
except during UAS-IMA condition, for Near-End side;
NeUAS (UnAvailable Seconds): counter of the seconds unavailability
beginning at the onset of 10 contiguous SES-IMA and ends at the onset of 10
contiguous seconds with no SES-IMA, for Near-End side;
Ne Tx UUS (UnUsable Seconds): counter of unusable seconds declared by the
Link State Machine at TX and RX directions for Near-End side;
Ne Tx failure: counter of the number of times a failure alarm condition has
been entered on this link at Tx direction for Near-End side;
Ne Rx failure: counter of the number of times a failure alarm condition has
been entered on this link at Rx direction for Near-End side.


3JK Edition 1.00



3JK Edition 1.00
1.14 ATM Interface Statistics
The quality of ATM PW Service is evaluated by monitoring the ATM

interface and VP/VC cell counters.
Interface #
Not Logical VPs
Logical VPs
Custom View

The Counters can be displayed in three different modalities:

List View
Overview
Birds Eye View

3JK Edition 1.00
1.14.1 Interface
Select the Interface as shown in figure (Interface #1 has been

selected).

For each configured and active ATM interface the following counters are available:
Usage Rx: counter of the number of cells received on the ATM interface.
Usage Tx: counter of the number of cells transmitted on the ATM interface.
Inv Header Discarded Cells: counter of the number of cells discarded because of Invalid Header,
invalid VPI or invalid VCI.

3JK Edition 1.00
1.14.1 Interface
1.14.1.1 Not Logical VPs and Logical VPs
In the screen will appear all the configured VP/VC.

In the figure the screen refer to VP #144/VC #35.


3JK Edition 1.00
1.14.1 Interface
1.14.1.1 Not Logical VPs and Logical VPs [cont.]
For each active VP, if configured as Termination end-point, and active VC

configured over an active ATM interface, the following counters are available:
Discarded Cells: counter of the total number of valid VP/VC cells discarded by the
traffic policing entity. This includes cells originally received with CLP=0 and CLP=1.
Discarded CLP0 Cells: counter of the total number of valid VP/VC cells received with
CLP=0 and discarded by the traffic policing entity.
Tagged Cells: counter of the total number of valid VP/VC cells tagged by the traffic
policing entity from CLP=0 to CLP=1 and transmitted.
Usage Rx: counter of the total number of valid VP/VC cells received including both
CLP=0 and CLP=1 cells. The cells are counted prior to the application of the traffic
policing.
Usage Tx: counter of the total number of valid VP/VC cells transmitted including both
CLP=0 and CLP=1 cells. The cells are counted prior to the application of the traffic
policing.
Usage Rx CLP0: counter of the number of valid VP/VC cells received with CLP=0. The
cells are counted prior to the application of the traffic policing.
Usage Tx CLP0: counter of the number of valid VP/VC cells transmitted with CLP=0.
The cells are counted prior to the application of the traffic policing.


3JK Edition 1.00
The user can select a counter on the left area and by clicking the upper
arrow move it to the right area in order to customize the counter view.
The opposite operation can be done by selecting the counter in the
right area and by clicking the lower arrow to move it to the left area.


3JK Edition 1.00
Exercise
Using the test link described in the following slide,

do the following steps:
1. Enable Performance Monitoring on the NE A and B to

monitor the quality of the path connecting the two
Test Instruments
2. Using the variable attenuator, simulate a link degradation and display the
current and the historical collected data


3JK Edition 1.00
Exercise
VARIABLE
ATTENUATOR
Test Test
Instr. A B Instr.
Operator 1 Operator 2


3JK Edition 1.00
Blank Page


3JK Edition 1.00
End of Module
Performance monitoring MPR node


3JK Edition 1.00
34
Section 3
NE operation
Module 4
Operator interface MPR terminal
a Issue 01
9500 MPR

a Issue 01
Blank Page

NE operation Operator interface MPR terminal
Document History

Marcoussis
01 2011-02-01 ALU university, Update to rel. 3.0

Vimercate

a Issue 01
Module Objectives
understand all the menus available with the MCT.


a Issue 01


a Issue 01
Table of Contents
Page
1 MPT Craft Terminal 7
1.1 Starting with NETO 8
1.2 Main View 10
1.3 Suggested sequence for MPT Craft Terminal interface 11
2 Main View 13
2.1 Main view 14
2.2 Line NE Status 17
2.4 Alarms Synthesis Panel 19
2.5 General Information Panel 21
2.6 Main Tab Panel 22
2.7 Navigator Area 29
2.9 MCT Menus 31
3 System Overview 33
3.1 System Overview Display 34
3.2 Alarm Symbol & Alarms Tab Panel 35
4 Commissioning Perspective 41
4.1 Commissioning Perspective Navigation 42
5 Inventory Tool 47
5.1 Inventory Tool 48
6 Software Download Tool 51
6.1 Software Download Tool 52
7 Configuration Tool 55
3 4 5 7.1 Configuration Tool All Rights Reserved Alcatel-Lucent 2011 56
NE operation7.2 Date/Time
Operator Configuration
interface MPR terminal 60
7.3 Site Information 61
7.4 Protection Configuration 62
7.6 Radio Configuration 68
7.6.1 Telecommunication Standard 71
7.6.2 Modulation 72
7.6.3 Transmit Power Control 78
7.6.4 Frequency 83
7.7 Advanced Radio 85
7.8 MSS-1c Provisioning 87
7.9 Ethernet Traffic QoS Configuration 93
7.9.1 QoS Classification 96
7.9.2 Ether Type Classification 97
7.9.3 Scheduling Algorithms 98
7.9.4 IEEE 802.1p Classification 99
7.9.5 Diffserv Classification 100
7.10 Networking Configuration 104
7.10.1 Network Interfaces Configuration 105
7.10.2 Static Routing Configuration 109
7.10.3 Trusted SNMP Managers Configuration 113
7.11 Backup/Restore NE Configuration 116
8 Monitoring Tool 121
8.1 Monitoring Tool 122
8.2 Alarms 124
8.3 Power Measurements 129
8.3.1 Start/Stop Monitoring 131
8.3.2 Power Measurements Graphic 133
8.3.3 Power Measurements Curves Management 135
8.3.4 Export Power Measurements Data 139
8.4 Modem Measurements 141

a Issue 01
Page
8.4.1 Start/Stop Monitoring 143
8.4.2 Mean Square Error 145
8.4.3 Modem Measurements Graphic 146
8.4.4 Modem Measurements Curves Management 148
8.4.5 Export Modem Measurements Data 149
9 Maintenance Perspective 151
9.1 Maintenance Perspective Navigation 152
9.4 Radio Tool 156
9.5 Alarms Tool 157
9.6 Power Measurements Tool 158
9.7 Modem Measurements Tool 159
10 Troubleshooting Perspective 161
10.1 Troubleshooting Perspective Navigation 162
10.3 Troubleshooting Tool 165
10.4 Alarms Tool 172
10.5 Power Measurements Tool 173
10.6 Modem Measurements Tool 174
10.7 Events Tool 175
11 Performance Monitoring Perspective 179
11.1 Performance Monitoring Perspective Navigation 180
3 4 6 MSS-1c Provisioning Tool - MainAllView
12 Rights Reserved Alcatel-Lucent 2011 183
NE operation12.1 Main
Operator interfaceview
MPR terminal 184
12.4 Main Tab Panel 186
12.5 Navigator Area 187
12.6 Provisioning Tool Menus 188
13 MSS-1c Provisioning Tool - Configuration Perspective 189
13.1 Configuration Perspective Navigation 190
13.2 File Management Tool 192
13.3 MSS-1c Configuration Tool 196
13.4 Ethernet Port Configuration 197
13.5 PDH Port Configuration 200
13.5.1 PDH Port Setting 201
13.5.2 Information on Circuit Emulation 202
13.5.3 Circuit Emulation Application Examples 207
13.6 Management Port Configuration 209
13.7 TDM Cross-Connection Between Radio and Users Ports 212
13.9 Bridge Configuration 222
13.10 Port VLAN Configuration 227

a Issue 01
1 MPT Craft Terminal


a Issue 01
1.1 Starting with NETO
WebEML Start To start the WebEML double click on

the relevant icon on the PC desktop
NETO
opens
Insert the IP address

of the NE
(default: 192.168.30.1)
and click <OK>
See next slide

N.B.
To access the NE the PC must be configured to Get automatically an IP address, because the NE is
configured as DHCP Server with default IP address 192.168.30.1 and subnet mask 255.255.255.252.
The PC Ethernet port must be connected to the CT connector of the MSS-1c.
N.B.
192.168.30.1 is the IP address of the port from MSS-1c and cannot be modified. The management can
be done also by the NMS port, but the PC must be configured with fixed IP and gateway. First open
the WebEML and after connect the cable.
Warning:
Without the MPT connected to the MSS-1c, it is not possible to open the WebEML on the CT port from
MSS-1c.
Warning:
If all the WebEML images/icons are missing, check that file msimg32.dll is present in <System32>.

a Issue 01
1.1 Starting with NETO [cont.]
When the NE is supervised,

click on <Show>
Then, the <Main view> opens

Note: Default User Accounts at the NE installation time, one default user account is created on NE
Username: admin
Password: admin

a Issue 01
1.2 Main View
MPR-e
MSS-1c
4) The Main view opens

The 9500MPT Craft Terminal (MCT) is the starting point of the CT application.
MCT functions require to know the NE identity by means of the related IP Address.
Only one NE can be managed in a MCT session.
The User Interface is provided by the MCT Main View.
The MCT connects to the 9500MPT with a transparent DHCP server which is not configurable.

a Issue 01
1.3 Suggested sequence for MPT Craft Terminal interface
With the NETO Main view:
1. Fill the IP address or DNS name field with the NE IP address;
2. Click on the OK button;
3. When the NE is supervised, click on <Show>
4. Write down the User name and Password;
5. Click on the Finish button.


a Issue 01
Blank Page


a Issue 01
2 Main View


a Issue 01
2 Main View
2.1 Main view
Two Main views are possible according to the 9500MPT version:
MSS-1c
MPR-e (MPT Stand-Alone)


a Issue 01
2 Main View
2.1 Main view [cont.] MSS-1c
Title Main Tool Bar Area
MSS-1c Alarms Synthesis Panel
Main Tab-panel
Domain Alarm Synthesis Panel
RESOURCE AREA
NAVIGATOR
GENERAL
INFORMATION
LINE NE STATUS
The Main View Area manages all domains from which the operator can start. It is organized with tab panels, e.g.
many windows placed one upon another. Each window is selectable (placing it on top of the others) with a tab
shown on the top.
Title: MCT connected to:

IP address, site name and site location of the equipment
Main Tab-panel
The Main Tab-panel permits to choose a specific tool (named perspective)
to manage the NE.
The following perspectives are present:
Commissioning (to provision, to configure the equipment)
Maintenance (to perform Maintenance tasks on the equipment)
Troubleshooting (to perform Troubleshooting tasks on the equipment)
Performance (to perform the Performance Monitoring on the equipment)
Navigator Area: displays all the available management tasks for a specific tool.
Resource Area: may be represented by: Tabular View or Graphical View.
Tabular View: displays a tabular representation of the selected resource. As default, no tabular element is
shown.
Graphical View: displays a graphical representation of the selected resource. As default, no tabular element
is shown.
General Information Area: displays the Management State Control of the equipment.
Line NE status Area: displays the MCT connection and the operator commands status.
Figure (Main view) is the entry point of the application and provides basic diagnostic and configuration
functions. Following multiple main views are available.
Navigation from main view to multiple main views (related to the equipment components) can be done by
simply double-clicking on the component graphical representation. Such operation will open a new window
containing selected secondary view. Starting from main view, the operator will also see MSS-1c, ODUs and
antennas layout. Each slot contains schematics of available board (if present) together with status and other
details. Slots schematics will in fact contain usual alarms information with a clarifying coloured icon that
reports the same icon visible in tree view.

a Issue 01
2 Main View
2.1 Main view [cont.] MPR-e
MPR-e Alarms Synthesis Panel
Main Tab-panel
Domain Alarm Synthesis Panel
RESOURCE AREA
NAVIGATOR
GENERAL
INFORMATION
LINE NE STATUS
shown on the top.
Title: MCT connected to:

IP address, site name and site location of the equipment
Main Tab-panel
to manage the NE.
shown.
is shown.
General Information Area: displays the Management State Control of the equipment.
Line NE status Area: displays the MCT connection and the operator commands status.
Figure (Main view) is the entry point of the application and provides basic diagnostic and configuration functions.
Following multiple main views are available.
Navigation from main view to multiple main views (related to the equipment components) can be done by simply
double-clicking on the component graphical representation. Such operation will open a new window containing
selected secondary view. Starting from main view, the operator will also see MSS-1c, ODUs and antennas layout.
Each slot contains schematics of available board (if present) together with status and other details. Slots
schematics will in fact contain usual alarms information with a clarifying coloured icon that reports the same
icon visible in tree view.

a Issue 01
2 Main View
2.2 Line NE Status
Line NE Status
This area contains information about the status of the NE.

Status of the connection between MCT and the NE with its NE IP address
General status of the NE and Operator commands status


a Issue 01
2 Main View
Quick Access Buttons
This area contains a selection of handy quick-access buttons for

common features.
Exit button from the Main View
Second button: to connect the MCT to the NE
The screen presented in Connection Parameters View (on page 9) appears
It is possible to connect the MCT to another NE
Third button: to disconnect the MCT from the NE


a Issue 01
2 Main View
2.4 Alarms Synthesis Panel
Severity Alarms Synthesis
The CT provides an alarm functionality that informs the operator on the

severity of the different alarms in the NE as well as on the number of current
alarms. There are five different alarm severity levels. In the CT these different
levels are associated with colors:
Red: Critical alarm (CRI).
Orange: Major alarm (MAJ).
Yellow: Minor alarm (MIN).
Cyan: Warning alarm (WNG).
Blue: Indeterminate (IND).
Each alarm severity is represented by an alarm icon situated in the top left
hand corner of the view. These alarm icons are constantly represented on the
different Equipment views (NE view, Board view or Port view) so that the
operator is always aware of the alarms occurring in the system.
An alarm icon grayed out indicates that spontaneous incoming alarm
notification have been inhibited.

N.B. The meaning of the icons in the Severity alarms synthesis is:
1) CRI - Critical alarm
Synthesis of alarms that needs immediate troubleshooting (typical: NE isolation).
2) MAJ - Major (Urgent) alarm
Synthesis of alarms that needs immediate troubleshooting.
3) MIN - Minor (Not Urgent) alarm
Synthesis of alarms for which a deferred intervent can be decided.
4) WNG - Warning alarm
Synthesis of alarms due to failure of other NE in the network.
5) IND - Indeterminate alarm
Synthesis of alarms not associated with the previous severities. Not operative.

a Issue 01
2 Main View
2.4 Alarms Synthesis Panel [cont.]
Domain Alarms Synthesis
This area contains the bitmaps (more than one) representing the alarms
per domain. Each bitmap indicates the number of alarm occurrences for
each domain.
The meaning of the icons in the Domain alarm synthesis area is:
1) EQP Equipment alarm
Synthesis of alarms of the Equipment domain.
2) COM Communication alarm
Synthesis of alarms of the Communication domain.


a Issue 01
2 Main View
2.5 General Information Panel
General Information
The different management states concerning the NE are shown in two

tab-panels.
The Radio Synthesis tab-panel gives information on the:

Abnormal Condition state: indicates whether some abnormal conditions have
been recognized.
The Network Supervision tab-panel gives information on the:

Local Access state: indicates whether the NE is managed by a craft terminal
or by the Operating System (OS)
OS Supervision: indicates whether or not the communication with the
Operating System (OS) is established

The meaning of the icons in the General Information Panel is:

1) Local Access State
GREEN LED: Indicates that the Craft Terminal has the OS permission to manage the NE (granted).
CYAN LED: Indicates that the Craft Terminal has not the OS permission to manage the NE
(denied).
2) OS OS isolation
3) AC Abnormal Condition
GREEN LED: Normal operating condition.
CYAN LED: Detection of an ABNORMAL operative condition. Type: switch forcing.

a Issue 01
2 Main View
2.6 Main Tab Panel
Main Tab Panel

or
The Main Tab panel permits to choose a specific tool (called

Perspective) to manage the NE.


The operator choice in the Main Tab Panel makes changes in the contents of:
1) Navigator Area
This area displays all the available tasks for a specific tool (perspective).
2) Resource area
This area displays a representation in tabular view or in graphical view of the selected resource
for a specific tool (perspective).
Operator facility:
By moving the margin, we can see all the opened tools (perspectives)

a Issue 01
2 Main View
2.6 Main Tab Panel [cont.]
Show Perspective Button
This menu propose to open a new

specific tool (Perspective) in the
Main Tab panel


a Issue 01
2 Main View
Perspective Menu
This menu propose

to Customize the Perspective
to Save the Perspective according to the customization
to Reset the Perspective to its default values
to Close the Perspective from the Main Tab panel


a Issue 01
2 Main View
Perspective Menu
Customize


a Issue 01
2 Main View
Perspective Menu
Save As
Reset


a Issue 01
2 Main View
Main Tab Panel Visualization

or
From the Show Perspective Button or from the opened Perspective,

we can customize the Main Tab Panel visualization
Show Text ON
Show Text OFF
Dock On (Next Page)


a Issue 01
2 Main View
Main Tab Panel Visualization

or
Dock On
From the Show Perspective Button or from the opened Perspective,

we can customize the Main Tab Panel visualization
Dock On Right Dock On Left
Dock On Top Right

Dock On Top Left


a Issue 01
2 Main View
2.7 Navigator Area
Navigator Area
The Navigator Area displays all the available management tasks for a
specific tool (Perspective).
The following tools are present:


a Issue 01
2 Main View
2.7 Navigator Area [cont.]
Selection Criteria
Each tree node consists of possibly three symbols and a label. The first
optional symbol indicates structure state: if symbol is , tree can be
expanded showing its contained lower levels. Tree structure can be
collapsed if symbol is . With no symbol, node represents a tree leaf.
Second symbol is alarm status of component. The operator can select
resource by clicking with mouse to perform the action dependent on
click type. Resource Detail Area related to the selected item is
displayed.
Each resource listed above may be selected by using the mouse by a:
Single left click:
By a single left click the resource is highlighted. This selection causes the activation
of the resource list area, e.g., every time the operator selects a resource in the
resource tree area the corresponding data are displayed in the Resource list area.
Double left click:
Double click operation on resource tree items allows the operator expanding tree
structure, so activating the display/update of resource list area, that will display
same information as for single click operation. As soon as a node is expanded,
another double click on such node would collapse tree structure to its closed view.

Button Policy
The possible buttons for selection are the following:
Apply
this button activates the modify, but it does not close the window.
Cancel
this button closes the window without modifying the parameters displayed in the window.
OK
this button activates the modify and closes the window
Close
this button closes the window
Help
this button provides the help management for the functions of the supporting window.

a Issue 01
2 Main View
2.9 MCT Menus
9500MPT Craft Terminal Menus
Three menus are available:
1) FILE
One choice: to exit the MCT.
2) WINDOW
One choice: Operators preference to display the windows.
3) HELP
One choice: to have an help on MCT.

Windows Menu
Help Menu
Configuration Details
Plug-in Details
a Issue 01
Blank Page


a Issue 01
3 System Overview


a Issue 01
3 System Overview
3.1 System Overview Display
The System Overview of the MCT Main View displays a global logical
view (strictly related to the physical implementation) highlighting a
synthesis of all the alarms and statuses present in the system.
MPR-e
MSS-1c

NOTE:
The Refresh button updates the display of the System Overview view.

a Issue 01
3 System Overview
3.2 Alarm Symbol & Alarms Tab Panel
By clicking on an Alarm Symbol on the block diagram, an Alarms Tab

Panel appears below the System Overview display.


a Issue 01
3 System Overview
3.2 Alarm Symbol & Alarms Tab Panel [cont.]
MSS-1c Alarm


a Issue 01
3 System Overview
MPT-MC Cable Alarm


a Issue 01
3 System Overview
MPT-MC Alarm


a Issue 01
3 System Overview
MPT-MC Antenna Alarm


a Issue 01
Blank Page


a Issue 01
4 Commissioning Perspective


a Issue 01
4.1 Commissioning Perspective Navigation MSS-1c


a Issue 01
4.1 Commissioning Perspective Navigation [cont.] MSS-1c
Commissioning Perspective is divided in:
Inventory
Software Download
Configuration
Date/Time
Site Information
Protection
Radio
Advanced Radio
MSS-1c
Networking
Network Interfaces
Static Routing
Trusted SNMP Managers
Monitoring
Alarms
Power Measurements
Modem Measurements


a Issue 01
4.1 Commissioning Perspective Navigation [cont.] MPR-e


a Issue 01
4.1 Commissioning Perspective Navigation [cont.] MPR-e
Commissioning Perspective is divided in:
Inventory
Software Download
Configuration
Date/Time
Site Information
Protection
Synchronization
Radio
Advanced Radio
Ethernet Traffic QoS
Networking
Network Interfaces
Static Routing
Monitoring
Alarms
Power Measurements
Modem Measurements
Events


a Issue 01
Blank Page


a Issue 01
5 Inventory Tool


a Issue 01
5 Inventory Tool
5.1 Inventory Tool MSS-1c
the equipment.
The Remote
Inventory feature
stores information
used to identify
all product
components.

a Issue 01
5 Inventory Tool
5.1 Inventory Tool [cont.] MPR-e
the equipment.
The Remote Inventory feature

stores information used to identify
all product components.


a Issue 01
5 Inventory Tool
5.1 Inventory Tool [cont.]
With the Export Button, we can save the Remote Inventory
information of the equipment in a text file.


a Issue 01
6 Software Download Tool


a Issue 01
6.1 Software Download Tool


a Issue 01
6.1 Software Download Tool [cont.]
Software Download Tab Panel
Two fields are available:
1) DOWNLOAD SOFTWARE PACKAGE

FTP SERVER PARAMETERS
This field allows to configure the FTP server to be used to download the SWP
to the NE.
SOFTWARE PACKAGE
Through this field the software is downloaded to the NE in order to upgrade
the NE software version.
The use of this Tool
2) SOFTWARE INFORMATION Software Download
This field gives the information is explained in the
of the software installed in the NE. module Section 4
Module 2


a Issue 01
Blank Page


a Issue 01
7 Configuration Tool


a Issue 01
7.1 Configuration Tool
7.1 Configuration Tool MSS-1c


a Issue 01
7.1 Configuration Tool [cont.] MSS-1c
Configuration Tool
Configuration Tool is divided in:
Date/Time
Site Information
Protection
Radio
Advanced Radio
MSS-1c
Networking (Network Interfaces, Static Routing, Trusted SNMP Managers)
In Configuration Tool, at the top right of the window

mainly we have three push-buttons:
1) <Refresh> : To update the display of the window.

2) <Apply> : To apply the configuration parameters set by the operator to the equipment.
3) <Defaults> : To set in the configuration parameters the defaults values saved in the
system.


a Issue 01
7.1 Configuration Tool [cont.] MPR-e


a Issue 01
7.1 Configuration Tool [cont.] MPR-e
Configuration Tool
Configuration Tool is divided in:
Date/Time
Site Information
Protection
Synchronization
Radio
Advanced Radio
Networking (Network Interfaces, Static Routing, Trusted SNMP Managers)
In Configuration Tool, at the top right of the window

mainly we have three push-buttons:
1) <Refresh> : To update the display of the window.

2) <Apply> : To apply the configuration parameters set by the operator to the equipment.
3) <Defaults> : To set in the configuration parameters the defaults values saved in the
system.


a Issue 01
7.2 Date/Time
7.2 Date/Time Configuration

The NE local time can be displayed and/or re-aligned to the Computer time basis.
The NE Date/Time field displays the current NE time.

The On-Demand NE Time Synchronization field displays the current Computer time.
To re-align the NE time to the Computer time, click on the Synchronize NE with Computer
pushbutton to validate.
The SNTP NE Time Synchronization field permits to configure the SNTP Servers regarding the NTP
(Network Time Protocol).
To enable this feature, click on SNTP Enabled (enabled/disabled);
Then, configure the IP address of the Main Server, which distributes the time to all the NEs in the
network;
And, configure the IP address of the Spare Server (IP address of a second NTP Server), which
replaces the Main Server in case of failure.
Note: If a change of Change Time Zone on the PC is applied with the MCT opened, in order to
make it updated on CT Close/Open the MCT application and Read Time another time.
NOTE: Do not forget to apply your configuration parameters changes

by clicking on <Apply> button

a Issue 01
7.3 Date/Time
7.3 Site Information
In Site Information , write down the:
Site Name
Site Location
of the equipment



a Issue 01
7.4 Protection
7.4 Protection Configuration



a Issue 01
7.4 Protection
7.4 Protection Configuration [cont.]
Choice: RPS 1+0


a Issue 01
7.5 Synchronization
7.5 Synchronization Configuration MPR-e only
Synchronization
tab panel


a Issue 01
7.5 Synchronization
7.5 Synchronization Configuration [cont.] MPR-e only

Mobile
2G,3G,4G
9500 MPR
SvncE Eth SyncE
Eth
9500 MPR
Private
Business
Office
9500 MPR
9500 MPR
options options
Fixed
DSL
1588v 1588v2
Phone 2 TOD TOD
protocol protocol


All the NEs radios in the network must be synchronized to the same clock.
SynchrE: Any Synchronous Ethernet clock source available at enabled User Ethernet traffic interfaces
(both electrical and optical) configured in synchronous operation mode (the specific User Ethernet
port has to be chosen).
From ITU-T G.8264 point of view, the MSS is a Synchronous Ethernet equipment equipped with a
system clock (NEC) following the ITU-T G.8262 recommendation.
A User Ethernet interface configured in synchronous operation mode can work only at
1Gigabit/s.
In the particular case of electrical User Ethernet interfaces, these interfaces perform link auto
negotiation to determine the master and slave clocks for the link.
The clock slave role must be configured as part of auto negotiation parameters in order to use
the interface as Synchronous Ethernet clock source.
N.B.: SSM are transparently forwarded in most of the configurations.

a Issue 01
7.5 Synchronization
Synchronization Tab Panel
Synchronization Tab Panel is divided in fields:

Synchronization Type
External Synchronization Type
<Apply> : To apply the configuration parameters set by the operator to

the equipment.


a Issue 01
7.5 Synchronization
Synchronization Configuration
This field allows to choose the synchronization

type between PCR and SyncE
PCR configuration
(Proprietary Clock Recovery): the time stamp
inside the Ethernet frame is used.
Fill in the corresponding Source and Destination
Mac Address
SyncE configuration
With this mode for the electrical interface the
selection among Autonegotiation/Master/Slave
must be performed.
Choose the role of the NE for the synchronization
(Automatic, Master, Slave)


a Issue 01
7.6 Radio
7.6 Radio Configuration
Radio
tab panel
1/2

The Radio Configuration view allows the operator to manage the resources of the radio transmission
channel.
A Radio NE consists of one or two radio channels with a set of functional blocks (tributary ports,
radio ports etc).


a Issue 01
7.6 Radio
7.6 Radio Configuration [cont.]
Radio
tab panel
2/2

The Radio Configuration view allows the operator to manage the resources of the radio transmission
channel.
A Radio NE consists of one or two radio channels with a set of functional blocks (tributary ports,
radio ports etc).

a Issue 01
7.6 Radio
7.6 Radio Configuration [cont.]
Radio Tab Panel
Radio Tab Panel is divided in fields:
Telecommunication Standard
Modulation
Transmit Power Control
Frequency
<Apply> : To apply the configuration parameters set by the operator to

the equipment.


a Issue 01
7.6 Radio
7.6.1 Telecommunication Standard
This field allows to configure the Telecommunication Standard market used by

the equipment:
ETSI: European Telecommunications Standards Institute.
ANSI: American National Standards Institute.


a Issue 01
7.6 Radio
7.6.2 Modulation
This field allows to configure the

modulation structure on the air:
Coding Modulation Type

Channel Spacing
Modem Profile Option
Reference Modulation
Allowed Modulations: This field is READ

only and presents the capacity in Mbit/s
on the air depending on, together:
Coding Modulation Type choice,
Channel Spacing choice,
Modem Profile Option choice,
Reference Modulation choice.


a Issue 01
7.6 Radio
7.6.2 Modulation [cont.]
Operation without the Adaptive Modulation (Fixed Coded Modulation)

Select in the Coding Modulation Type field
Fixed (FCM).
Select in the Channel Spacing field the

suitable channel spacing to be used.
Select in the Modem Profile Option field

the spectral efficiency class to be set as
reference
Select in the Reference Modulation field

the suitable Modulation scheme.
According to the previous four selections the

relevant capacity in the Allowed
Modulations field will appear.

The possible choices for each field:
Coding Modulation Type:

Fixed (Fixed Coded Modulation)
Adaptative (Adaptative Coded Modulation)
Channel Spacing:
3,5 MHz
7 MHz
14 MHz
28 MHz
40 MHz
56 MHz
Modem Profile Option:

Current Mask Standard Profile
Current Mask SDH Capacity
New Mask Standard Profile
Reference Modulation:
QPSK
8 PSK
16 QAM
32 QAM
64 QAM
128 QAM
256 QAM

a Issue 01
7.6 Radio
Operation with the Adaptive Modulation (Adaptative Coded Modulation)
Select in the Channel Spacing field the suitable Select in the Coding Modulation Type
channel spacing to be used. field Adaptative (ACM).
Select in the Modem Profile Option field the

spectral efficiency class to be set as reference
Select in the Reference Modulation field the

lowest modulation scheme (from QPSK) to be
used by the Adaptative Modulation.
Choose in the Allowed Modulation field all the

modulation schemes to be used with the
Adaptive Modulation. The modulation schemes
(from the lowest to the highest scheme) must
be contiguous
The Allowed Modulation field is a read-only

field, which shows the current used modulation
and capacity. The current modulation will
depend on the fading activity during the
propagation.
To update this field press the Refresh button. To confirm the selection click on Apply.


Channel Spacing:
3,5 MHz, 7 MHz, 14 MHz, 28 MHz, 40 MHz, 56 MHz

QPSK, 16 QAM, 32 QAM, 64 QAM

a Issue 01
7.6 Radio
Capacity Up-Grade
In this case all the pre-configured TDM2TDM or TDM2ETH will be kept.
The residual bandwidth for the lowest modulation scheme is recomputed.
Capacity Down-Grade
If all the pre-configured TDM2TDM or TDM2ETH stays in the capacity
associated to the new modulation scheme:
they will be kept,
the residual bandwidth for the new modulation scheme is recomputed.
If all the pre-configured TDM2TDM or TDM2ETH cannot stay in the capacity
associated to the new modulation scheme:
the change of channel spacing is rejected by CT/NMS.

A specific behavior must be followed when the Channel Spacing needs to be changed, to pre-serve
any pre-configured TDM2TDM or TDM2ETH. Consequently, two cases must be taken into account:
When the admission control is enabled,

It means that the admission control was performed with the capacity of the lowest modulation scheme.
When the admission control is disabled,
It means that the admission control was performed with the capacity of the highest modulation scheme.

a Issue 01
7.6 Radio
Modulation Change
Capacity Up-Grade
all the pre-configured TDM2TDM or TDM2ETH are kept.
all the pre-configured TDM2TDM or TDM2ETH will work if the current capacity
is able to support all of them, otherwise all pre-configured TDM2TDM or
TDM2ETH will not work.
Capacity Down-Grade
all the pre-configured TDM2TDM or TDM2ETH will be kept.
all the pre-configured TDM2TDM or TDM2ETH will be kept if the current
capacity is able to support all of them, otherwise all pre-configured TDM2TDM
or TDM2ETH will be completely lost.

When the Adaptative Modulation engine changes the modulation, the pre-configured TDM2TDM or
TDM2ETH traffic must be managed according to the behavior here after described. Two cases must be
taken into account: Capacity Up-grade and Capacity Down-Grade.

It means that the admission control was performed with the capacity of the lowest modulation scheme.
It means that the admission control was performed with the capacity of the highest modulation scheme.

a Issue 01
7.6 Radio

From Fixed to Adaptive
behavior is:

If all the pre-configured TDM2TDM or TDM2ETH in the Old Fixed Modem Profile, stay in the
capacity associated to the lowest Modulation Scheme, the request of change is accepted and
the residual bandwidth for the lowest Modulation Scheme is computed.

If all the pre-configured TDM2TDM or TDM2ETH cannot stay in the capacity associated to the
lowest Modulation Scheme, the request of change is rejected.
pre-con-figured TDM2TDM or TDM2ETH in the Old Fixed Modem Profile stay in the
capacity associated to the highest Modulation Scheme, then the request of change is
always accepted and the residual bandwidth for the highest Modulation Scheme is
computed.
From Adaptive to Fixed
When the Adaptive Modulation is disabled, if all the pre-configured TDM2TDM or
TDM2ETH in the Old Adaptive Modem Profile, stays in the capacity of the New Fixed
Modem Profile, the request is accepted and the residual bandwidth for new Fixed
Modem Profile will be computed. If all the pre-configured TDM2TDM or TDM2ETH
cannot stay in the capacity of the New Fixed Modem Profile, the request of change
is rejected.

A specific behavior must be followed when it is needed to move from Adaptive Modulation to Fixed
Modulation or vice-versa, in order to preserve any pre-configured TDM2TDM or TDM2ETH. Two cases
must be taken into account: from Fixed to Adaptive Modulation and from Adaptive to Fixed Modulation.
The working mode changes, here below described, are generic. The changes cover both the change of
the modulation but with the same Channel Spacing and the change of the Channel Spacing.

a Issue 01
7.6 Radio
7.6.3 Transmit Power Control
This field allows to

configure the Transmit
Power of the Radio
channels on the air:
To mute the transmitters
To choose the Transmit

Power Control Mode:
RTPC
ATPC


a Issue 01
7.6 Radio
7.6.3 Transmit Power Control [cont.]
Mute Tick on <Mute>

Then, click on <OK>, then <Apply>
Consequence in Monitoring/Alarms

The information related to the transmitter status is shown by an icon closed to the Mute field. To
squelch the transmitter tick on Mute field and press Apply button.

a Issue 01
7.6 Radio
Transmit Power Control Mode

RTPC
After the setting, click on <Apply>

If the ATPC is disabled the manual Tx Power field is present.
In the middle field write the new value within the allowed transmitted power range.
The range is shown in <TX Power> field in the left and right fields.

The operator can modify only the Tx power relevant to the reference modulation
scheme.

Note: the same power value will be used by the

16 QAM and 64 QAM modulation schemes

a Issue 01
7.6 Radio

ATPC
For the ATPC mode, the ATPC Range

and ATPC Remote RSL Threshold
ATPC Range
The Min Tx power and Max Tx power,
regarding the Tx Range in the ATPC
management, can be written in the
After the setting, click on <Apply>
relevant field.
ATPC Remote RSL Threshold

The value of the low power threshold can be changed by writing the new value in the
field. When the Rx power is equal to this power the ATPC algorithm starts to operate.

Note: the ATPC area is not present if the

Adaptive Modulation has been selected.

a Issue 01
7.6 Radio

ATPC
RSL Driving Criteria
Select in the
<Driving Remote RSL in 1+1 HSB>
field the suitable value.
In 1+1 FD and HSB configurations both

the transmitters can be driven by the
lowest or by the highest RSL values of After the setting, click on <Apply>
the two remote demodulators.
This feature is Not Applicable in the current release


a Issue 01
7.6 Radio
7.6.4 Frequency
This field allows to configure the Frequencies of the Radio channels.
The system can operate with different types of ODU according to the RF band and to
the channel arrangement. There are ODUs which can manage only one shifter or
several predefined shifters.
In the Tx frequency field insert the suitable Tx frequency (the Rx frequency is
automatically calculated by using the inserted Tx frequency and the shifter).
Note: The Tick button <Allow Rx Frequency Tuning> permits to change both the Tx
and Rx Frequencies.

The Tx and Rx frequencies fields have three values of frequencies:
The middle field is used to set a frequency inside the allowed frequency range given by the ODU
represented by the left and right fields.

a Issue 01
7.6 Radio
7.6.4 Frequency [cont.]
By clicking on ,
you can display the associated frequency plan of the connected ODU according
to the Radio channels frequencies configuration (Shifter, Tx Frequency, Rx
Frequency) with, in red, the channel spacing configured in Modulation field.


a Issue 01
7.7 Advanced Radio
7.7 Advanced Radio
The Advanced Radio configuration permits

To set the Radio Link Identifiers



a Issue 01
7.7 Advanced Radio
7.7 Advanced Radio [cont.]
This part allows the operator to define the expected and

sent identifier values of parameters related to the link
management and, if necessary, modify them.
The operator choices will be sent to the NE by clicking on
the related Apply button.
If the Link Identifier is Enabled the following fields can be
written:
Expected Rx Identifier: this field is the link identifier expected
at the receiving NE
Tx Identifier: this field is the link identifier inserted on the
transmitting NE.


a Issue 01
7.8 MSS-1c
7.8 MSS-1c Provisioning
The configuration of the MSS-1c is done with a

< Provisioning Tool > application


a Issue 01
7.8 MSS-1c
7.8 MSS-1c Provisioning [cont.]
MSS-1c Provisioning Tab Panel
Four fields are available:
1) MSS-1c PROVISIONING TOOL

This field allows to configure the MSS-1c with the < Provisioning Tool >
application.
2) FTP SERVER PARAMETERS
This field allows to configure the FTP server to be used to download the
<MSS-1c Provisioning File> to the NE.
3) DOWNLOAD AND EXECUTE MSS-1c PROVISIONING FILE
Through this field the <MSS-1c Configuration File> is downloaded to the NE
in order to set the MSS-1c subrack with operational parameters.
4) UPLOAD MSS-1c PROVISIONING FILE
Through this field the MSS-1c subrack operational parameters is saved in a
<MSS-1c Provisioning File>.


a Issue 01
7.8 MSS-1c
This field allows to configure the MSS-1c with the

< Provisioning Tool > application
MSS-1c Provisioning Tool screen
Click on the Start Tool button to run the < Provisioning Tool >
application

The < Provisioning Tool > application is explained later in this document

a Issue 01
7.8 MSS-1c
<MSS-1c Configuration File> to the NE.
Server access configuration screen

In the Server Address field write the IP address of the FTP server.
User Name and Password are the login information to access the FTP server.
In the Port field write the port to be used.
By clicking on the Check button, the server access values will be filled in automatically with the default
configuration.
The CT is the default FTP server with the following parameters:

User Id: anonymous
Password: -
Address: local host IP address.
Port: 21
Root Dir: /

a Issue 01
7.8 MSS-1c
Through this field the <MSS-1c Configuration File> is downloaded to the

NE in order to set the MSS-1c subrack with operational parameters.
This field can be used as a configuration RESTORE .
Download and Execute MSS-1c Configuration File screen

Follow the steps to perform this procedure:
1. Click on Browse button to select in your PC

the directory and,
the <MSS-1c Configuration File> file
containing the MSS-1c operational parameters you want to download to the MSS-1c subrack.
2. Then, click on the Download and Execute button to begin the download process.
3. When the <MSS-1c Configuration File> download starts, a screen showing the in progress operation of
the download appears. The download is aborted if the Abort button is pressed.
4. Click Ok.

a Issue 01
7.8 MSS-1c
Through this field the MSS-1c subrack operational parameters is saved in

a <MSS-1c Configuration File>.
This field can be used as a configuration BACKUP .
Upload MSS-1c Configuration File screen

1. Click on Browse button to select and choose in your PC:

the directory and,
the <MSS-1c Configuration File> file name
where you want to upload the ACTIVE MSS-1c operational parameters from the MSS-1c subrack.
2. Then, click on the Upload button to begin the upload process.
3. When the ACTIVE MSS-1c operational parameters upload starts, a screen showing the in progress
operation of the upload appears. The upload is aborted if the Abort button is pressed.
4. Click Ok.

a Issue 01
7.9 Ethernet Traffic QoS
7.9 Ethernet Traffic QoS Configuration MPR-e only

tab panel



a Issue 01
7.9 Ethernet Traffic QoS Configuration [cont.] MPR-e only
QoS Configuration Tab Panel
QoS Configuration Tab Panel is divided in fields:
Legacy Ethernet Traffic QoS

(this field allows to configure the Ethernet Traffic
QoS parameters to be applied to the equipment):
QoS Classification (None, 802.1p, Diffserv)

Ether Type Classification
Scheduling Algorithms
<Apply> : To apply the configuration

parameters set by the operator to the
equipment.


a Issue 01
7.9 Ethernet Traffic QoS Configuration [cont.] MPR-e only
QoS Configuration Tab Panel [cont.]
IEEE 802.p
None Diffserv
Depending on the QoS Classification,

three Legacy Ethernet Traffic QoS
screens can be seen:


a Issue 01
7.9.1 QoS Classification MPR-e only
Quality Of Service
The Ethernet switch provides a Quality of Service mechanism to control all
streams. If the QoS is disabled, all traffic inside the switch has the same
priority, this means that for each switch port there is only one queue (FIFO)
therefore the first packet that arrives is the first that will be transmitted.
This field allows to set the suitable Quality Of Service to be applied to

the NE:
None
packet;
Diffserv: each packet is classified based on DSCP field in the IP header to
assign the priority;
DEFAULTS VALUES:
values.
Considering that in the Radio Interface module for generic Ethernet traffic there are five egress
queues the mapping 802.1p value to queue is the following:

101 Q4
100 Q3
011, 000 Q2
010, 001 Q1
DiffServ priority Diffserv value Queue

111000, 110000, 101110, 101000 56, 48, 46, 40 Q5 (higher priority)
100110, 100100, 100010, 100000 38, 36, 34, 32 Q4
011110, 011100, 011010, 011000 30, 28, 26, 24 Q3
010110, 010100, 010010, 010000 22, 20, 18, 16 Q2
001110, 001100, 001010, 001000 14, 12, 10, 8,
000000 0

a Issue 01
7.9.2 Ether Type Classification MPR-e only
Ether Type Classification
This field allows to set, if desired, for

each non High Priority Queue (1 to 5),
the type of Ethernet frame that will
be sent to this queue.
Ether Type examples:

0x0800=IP
0x0806 = ARP
0x8035 = RARP
0x888E = 802.1X
0x8863 = PPPoE Control frames
0x8864 = PPPoE Data frames

Adding/Deleting a Ether Type Classification:
Add Last: to add at the top of the list
Add: to add at the end of the list
Delete: to delete the highlighted line

a Issue 01
7.9.3 Scheduling Algorithms MPR-e only
Scheduling Algorithms
This field allows to configure, if

desired, for each non High Priority
Queue (1 to 5):
The Scheduling Mode: DWRR,
The DWRR Weight of the Deficit Weight
Round Robin scheduler chosen for this
queue.
Note: you can choose the Defaults

values


a Issue 01
7.9.4 IEEE 802.1p Classification MPR-e only
IEEE 802.1p Classification This field allows to configure the IEEE

802.1p priority frames allowed for
each non High Priority Queue (1 to 5)
classified as:
Best Effort frames (001),
Background frames (000),
Spare frames (010),
Excellent Effort frames (100),
Controlled Load frames (011),
Video frames (110),
Voice frames (111),
Network Control frames (101).
Note: you can choose the Defaults

values


a Issue 01
7.9.5 Diffserv Classification MPR-e only
Diffserv Classification
This field allows to set, if desired, for

each non High Priority Queue (1 to 5),
the range of Diffserv classification
values:
Minimum Diffserv Code Point
Maximum Diffserv Code Point
Notes:
You can choose the Defaults values
The highest priority queue is 5
The highest priority queue corresponds to the transmission of packets whose
diffserv classification priority is the highest (range of diffserv priority values).
The next queue does not contain the range of diffserv priority values of the
previous queue.
The range of diffserv priority values has to be set in ascending order
corresponding to the ascending order of the queues.

a Issue 01
7.9.5 Diffserv Classification [cont.] MPR-e only
Diffserv Classification Values Choice
The choice for Queue Identifier is one

of the the non High Priority Queue (1 to 5)
The choice for Minimum Diffserv Code Point and Maximum Diffserv Code
Point is one of the Diffserv classification values 0 (000000) to 63 (111111)


a Issue 01
Adding a Diffserv Classification
Add Last: to add the Diffserv

Classification at the top of the list
Add: to add the Diffserv Classification

at the end of the list


a Issue 01
Deleting a Diffserv Classification
Delete: to delete the highlighted

Example with Errors
Example of setting with errors:

Range of diffserv priority values of the
first 2 queues do not follow the rules.


a Issue 01
7.10 Networking
7.10 Networking Configuration
For Networking configuration, three tool

tab-panels are available:
1) NETWORK INTERFACES TOOL

2) STATIC ROUTING TOOL
3) TRUSTED SNMP MANAGERS


a Issue 01
7.10 Networking
7.10.1 Network Interfaces Configuration MSS-1c
Network Interfaces
Configuration
Tab Panel

a Issue 01
7.10 Networking
7.10.1 Network Interfaces Configuration [cont.] MSS-1c
Network Interfaces Configuration Tab Panel
Six fields are available:
1) NE IP PARAMETERS
Defines the local IP address of the NE.
Default mask: 255.255.255.255
2) TMN RF ACCESS
To validate the TMN RF channel to supervise the remote station.
3) NMS1
Defines the IP address associated to the physical interface Network Management
Service 1 (NMS1 connector).
4) NMS2
Defines the IP address associated to the physical interface Network Management
Service 2 (NMS2 connector).
5) TMN IN-BAND
Defines the IP address of the TMN supervision channel defined with a VLAN identifier
inside a user Ethernet traffic.
6) CT
Defines the IP address associated to the Craft Terminal connected to the physical
interface CT (CT connector). These fields are Read-only.

If used:
Assign an IP address with its IP mask
When you have finished to configure the Network Interfaces Configuration tab panel,
do not forget to apply it to the NE (<Apply> button on the top right of the window).

a Issue 01
7.10 Networking
7.10.1 Network Interfaces Configuration [cont.] MPR-e
Network Interfaces
Configuration
Tab Panel

a Issue 01
7.10 Networking
7.10.1 Network Interfaces Configuration [cont.] MPR-e
Network Interfaces Configuration Tab Panel
Three fields are available:
1) NE IP PARAMETERS
Defines the local IP address of the NE.
Default mask: 255.255.255.255
2) TMN RF ACCESS
To validate the TMN RF channel to supervise the remote station.
3) TMN IN-BAND
Defines the IP address of the TMN supervision channel defined with a VLAN
identifier inside a user Ethernet traffic.

If used:
Assign an IP address with its IP mask
When you have finished to configure the Network Interfaces Configuration tab panel,
do not forget to apply it to the NE (<Apply> button on the top right of the window).

a Issue 01
7.10 Networking
7.10.2 Static Routing Configuration
Static Routing Configuration Tab Panel



a Issue 01
7.10 Networking
7.10.2 Static Routing Configuration [cont.]
Static Routing Configuration
For each Static Route to configure, we have to make a choice for:

- Route Type
- Point To Point Link

This is the IP interface to a host or network. Typically used at a spur to interface a host over the RF path. In
this scenario, the Default Gateway IP Address is 0.0.0.0 and the IP Mask (greyed out) is 0.0.0.0. Also typically
used at an end terminal in a radio link for interface with the network.
WARNING:


The default software uses first the static routes and then the dynamic routes. An open static route is
always considered as a preferential path.
If in the screen the Default Gateway IP Address check box has been selected, write in the Default Gateway IP
Address field below the relevant IP address.
By pressing Add Last or Add pushbutton it is possible to create new or change existing IP static routes

Route Type (Default, Network, Host)
Destination IP Address: allows to define the IP address necessary to reach a specific host/network
Destination Mask: allows to define the IP Mask to reach a network
Point To Point Link interface type: allows to use point to point interfaces made available by the NE to
address the link on the radio side.
Default Gateway IP Address: allows to define the address of the next hop gateway reachable on the TMN In-
band interface.

a Issue 01
7.10 Networking
Adding a Static Route
Add Last: to add the route at the top of the list
Add: to add the route at the end of the list


a Issue 01
7.10 Networking
Deleting a Static Route
Delete: to delete the highlighted route


a Issue 01
7.10 Networking
7.10.3 Trusted SNMP Managers Configuration

Configuration
Tab Panel


a Issue 01
7.10 Networking
7.10.3 Trusted SNMP Managers Configuration [cont.]
Trusted SNMP Managers Configuration
For each Trusted SNMP Manager to declare, we have to fill in the

following parameters:
- Manager IP Address
- Traps UDP Port
- Type (Network Manager Layer, Equipment Manager Layer)
Definition: A Trusted Manager is a SNMP manager to which the NE automatically

sends the TRAPS generated inside the NE.

a Issue 01
7.10 Networking
7.10.3 Trusted SNMP Managers Configuration [cont.]
Registration
To delete a Manager, select the Manager from the list, then press < Unregister >

a Issue 01
7.11 Backup / Restore
7.11 Backup/Restore NE Configuration


a Issue 01
7.11 Backup/Restore NE Configuration [cont.]
Backup / Restore Tab Panel
Four fields are available:

This field allows to configure the FTP server to be used to backup / restore
the <NE configuration> to/from the PC.
2) BACKUP / RESTORE NE Configuration
Through this field the <MSS-1c Configuration File> is downloaded to the NE
in order to set the MSS-1c subrack with operational parameters.


a Issue 01
This field allows to configure the FTP server to be used to backup /

restore the <NE configuration> to/from the PC.

configuration.

User Id: anonymous
Password: -
Port: 21
Root Dir: /

a Issue 01
This field allows:

- to make a backup (to save the <NE Configuration> to the PC
- to make a restore (to download a <NE Configuration>, from a
previously done backup, to the NE
Backup / Restore NE Configuration screen


the directory and,
the <NE Configuration> file name
containing the NE operational parameters you want to backup/restore to/from the PC.
2. Then, click on the Backup or Restore button to begin the backup/restore process.
3. When the < NE Configuration > backup/restore starts, a screen showing the in-progress operation of
the backup/restore appears. The backup/restore is aborted if the Abort button is pressed.
4. Click Ok.

a Issue 01
Blank Page


a Issue 01
8 Monitoring Tool


a Issue 01
8.1 Monitoring Tool
8.1 Monitoring Tool


a Issue 01
8.1 Monitoring Tool
8.1 Monitoring Tool [cont.]
Monitoring Tool
Monitoring Tool is divided in:
Alarms
Power Measurements
Modem Measurements


a Issue 01
8.2 Alarms
8.2 Alarms
The Alarms tab panel allow to display and

store the alarms of the equipment.


a Issue 01
8.2 Alarms
8.2 Alarms [cont.]
In the Alarms tab panel,

two tab panels for the <Current Alarms> and the <Alarms Log>.
Current Alarms: shows all the equipment alarms currently present,
Alarms Log: shows all the equipment alarms currently present and the history of
the alarms (i.e. cleared alarms).

Note:
When an alarm is no longer active, it disappears from the Current Alarm list and it is displayed in the
Alarm Log list as a cleared alarm.

a Issue 01
8.2 Alarms
8.2 Alarms [cont.]
Within the Alarms tab panel, each alarm is provided with the
information below.
Time Stamp: date and time of the alarm. The format of date and time is
mm/dd/yy hh:mm:ss.
Probable cause: name of the probable cause of the alarm.
Type: alarm class
COMMUNICATION = Communication Alarm alarm not created inside the equipment,
but generated by a connected equipment or due to transmission/propagation
problems
EQUIPMENT: inside alarm of the equipment.
Object: object of the equipment where the alarm occurred (equal to Friendly
Name).
Severity: alarm severity.
Additional Text: this is an additional text regarding the alarm.


a Issue 01
8.2 Alarms
8.2 Alarms [cont.]
Alarms Tab Panel Tool Bar
Four tools menus are available:
1) CLEAR ALARMS LOG

One choice: to clear the Alarms Log list.
2) PRINT
One choice: to print the list of alarms
(Current Alarms or Alarms Log).
3) AUTO-SCROLL
One choice: to scroll automatically the list of the alarms.
4) FILTER
To organize the display of the alarms by a filter or not.


a Issue 01
8.2 Alarms
8.2 Alarms [cont.]
Filter Tool Menu
SEVERITY Filter
TYPE Filter
NO FILTER

Perceived severity filter

Select Alarm Severity and then one severity level to filter the alarm having the selected severity
levels:
CRITICAL
MAJOR
MINOR
WARNING
INDETERMINATE
Alarm Type filter
Select Alarm Type to create a filter for the selected type of alarm:
COMMUNICATION = Communication or Transmission alarm
QUALITY OF SERVICE = Traffic alarm
PROCESSING ERROR = Supervision alarm
EQUIPMENT = Equipment alarm
ENVIRONMENTAL = Housekeeping alarm

a Issue 01
8.3 Power Measurements
The Power Measurements capability is performed by means of

the <Power Measurements> tabbed panel of the Monitoring tool.


a Issue 01
8.3 Power Measurements [cont.]
Power Measurements Tab Panel
Power Measurements Tab Panel is divided in two fields:

Near End to Far End Power Monitoring
Far End to Near End Power Monitoring
These fields are identical for Monitoring and represent the linked end-point of the two
NE (from a local point of view, one field for transmission view and one field for
reception view).

a Issue 01
8.3.1 Start/Stop Monitoring
Span choice for the monitoring
Before to start the monitoring, choose the span of the Power

Measurement Graphic screen, it can be:
1 minute, 5 minutes, 15 minutes, 1 hour, 24 hours.


a Issue 01
8.3.1 Start/Stop Monitoring [cont.]
Start/Stop Monitoring
1) START MONITORING
After clicking on Start Monitoring
button, you have to select the
refresh period for monitoring.
2) SELECT THE REFRESH PERIOD

FOR MONITORING
3) STOP MONITORING
Note: During the monitoring, you can see at

anytime the Refresh Period Time you selected


a Issue 01
8.3.2 Power Measurements Graphic
Power Measurements Graphic
The Power Measurement Graphic screen shows the Tx and Rx

measurements related to the local and remote NE.
Through this screen the operator can see, in real time,
the power transmitted in green color by the local and remote transmitter (Tx),
the power received in blue color by the local and remote receiver (Rx).


a Issue 01
8.3.2 Power Measurements Graphic [cont.]
On the left and right side of the Power Measurement

Graphic screen, two bar-graphs; these bar-graphs,
from left to right, show the following relevant values of
the transmitted and received power :
In the field < Near End to Far End Power Monitoring >
NE Tx Power (in green color)
Near End Tx Power value (local equipment)
FE RSL (in blue color)
Far End Receive Signal Level (remote equipment)
In the field < Far End to Near End Power Monitoring >
NE RSL (in blue color)
Near End Receive Signal Level (local equipment)
FE Tx Power (in green color)
Far End Tx Power value (remote equipment)
Note: The current Tx and Rx local and remote values is given too.

WARNING:

a Issue 01
8.3.3 Power Measurements Curves Management
Go to the first
Measurement point
Go to the last
Measurement point


a Issue 01
8.3.3 Power Measurements Curves Management [cont.]
Move the curve

towards the left
Move the curve

towards the right


a Issue 01
Zoom In
Zoom Out


a Issue 01
Erase all curves !
Scroll lock
To freeze the display


a Issue 01
8.3.4 Export Power Measurements Data
Export Data to a .csv File
By clicking on Export data to a .csv file, you save the Power

Measurements in a .csv file.
Then the MCT asks you to choose a path and name for this file in your
PC (You can store the file in any directory).


a Issue 01
8.3.4 Export Power Measurements Data [cont.]
-1- Choose a path and name for

this file in your PC (You can
store the file in any
directory).
-2- The log file contains the sample value and records the measurement
up to a maximum dimension (7 days for a 2 s sample time).
Note: The measurement file can be opened also with a standard text editor (e.g. WordPad). Go in
the directory where the .csv files are stored and open the file. The measurements are shown in the
tabular mode.

a Issue 01
8.4 Modem Measurements
The Modem Measurements capability is performed by means of the

<Modem Measurements> tabbed panel of the Monitoring tool.


a Issue 01
8.4 Modem Measurements [cont.]
Modem Measurements Tab Panel
Modem Measurements Tab Panel is divided in two fields:

Near End to Far End Modem Monitoring
Far End to Near End Modem Monitoring
These fields are identical for Monitoring and represent the linked end-point of the two
NE (from a local point of view, one field for transmission view and one field for
reception view).

a Issue 01
8.4.1 Start/Stop Monitoring
Before to start the monitoring, choose the span of the Modem

Measurement Graphic screen, it can be:


a Issue 01
8.4.1 Start/Stop Monitoring [cont.]
Start/Stop Monitoring
1) START MONITORING

FOR MONITORING
3) STOP MONITORING
Note: During the monitoring, you can see at

anytime the Refresh Period Time you selected


a Issue 01
8.4.2 Mean Square Error
MSE: Mean Square Error

The Mean Square Error is the arithmetic mean of the
squared differences between forecasts and observations.
Tx message : 1110 1100

Rx message : 1110 1100
1110
1100
In Radio Link Systems,
the Mean Square Error is
a modulation error from
Intersymbol distance the theoretical threshold
of the equipment.
MSE is expressed in dB.
16-QAM Modulation drawback
Rx weak noise


a Issue 01
8.4.3 Modem Measurements Graphic
Modem Measurements Graphic

The Modem Measurement Graphic screen shows the Mean Square
Error (MSE) and the Modulation/Demodulation Schemes measurements
related to the local and remote NE.
the Mean Square Error level (expressed in dB) in pink color measured by the
remote receiver (MSE: Mean Square Error),
the Modulation (in blue color)/Demodulation (in yellow color) Schemes
measured by the local equipment.


a Issue 01
8.4.3 Modem Measurements Graphic [cont.]
On the left and right side of the Modem Measurement

Graphic screen, two bar-graphs; these bar-graphs,
from left to right, show the following relevant values of
the local and remote MSE (Mean Square Error) :
In the field < Near End to Far End Modem Monitoring

>
FE MSE (Mean Square Error), (in pink color)
Far End Margin Signal Expected (remote equipment)
In the field < Far End to Near End Modem Monitoring

>
NE MSE (Mean Square Error), (in pink color)
Near End Margin Signal Expected (local equipment)
Note: The current MSE local and remote values are given too.

WARNING:

a Issue 01
8.4.4 Modem Measurements Curves Management
Go to the first Measurement point

Go to the last Measurement point
Move the curve towards the left
Move the curve towards the right
Zoom In
Zoom Out
Erase all curves !
Scroll lock
It is the same as Power Measurements Curves Management


a Issue 01
8.4.5 Export Modem Measurements Data
By clicking on Export data to a .csv file, you save the Modem

Measurements in a .csv file.
It is the same as Export Power Measurements Data


a Issue 01
Blank Page


a Issue 01
9 Maintenance Perspective


a Issue 01
9.1 Maintenance Perspective Navigation


a Issue 01
9.1 Maintenance Perspective Navigation [cont.]
Maintenance Perspective is divided in:
Inventory
Software Download
Configuration
Radio
Monitoring
Alarms
Power Measurements
Modem Measurements


a Issue 01
9.2 Inventory Tool
This tool is exactly the same tool explained in <Commissioning Perspective>


a Issue 01


a Issue 01
9.4 Radio Tool


a Issue 01
9.5 Alarms Tool


a Issue 01
9.6 Power Measurements Tool


a Issue 01
9.7 Modem Measurements Tool


a Issue 01
Blank Page


a Issue 01
10 Troubleshooting Perspective


a Issue 01
10.1 Troubleshooting Perspective Navigation


a Issue 01
10.1 Troubleshooting Perspective Navigation [cont.]
Troubleshooting Perspective is divided in:
Inventory
Troubleshooting
Monitoring
Alarms
Power Measurements
Modem Measurements
Events


a Issue 01
10.2 Inventory Tool


a Issue 01
10.3 Troubleshooting Tool
MPR-e
MSS-1c
The functions described in this section allow to perform the test operations
by loopbacks.

a Issue 01
10.3 Troubleshooting Tool [cont.]
Troubleshooting Tab Panel
1) LOOPBACK
This field permits to perform tests on the equipment
In this current release, two loopbacks are available:
Line Side loopback (the signal is sent back to the Indoor equipment)
Radio Side loopback (the signal is sent back to the Remote station)
2) RESTART NE
This field permits to restart the NE
3) ACM MANUAL MANAGEMENT

(Adaptative Coded Modulation Manual Management)
This field permits to manually lock the ACM engine
Not active in current release TCO Suite Rel. 4.2


a Issue 01
ACM Manual Management

Tick on the <Lock ACM engine> box
To lock the ACM engine: Then select the modulation scheme to
be used


a Issue 01
Loopback (1/4)
To activate a loopback (1/3):
Choose the values for the

Loopback Timeout
Then click on <Apply> button



a Issue 01
Loopback (2/4)

To activate a loopback (2/3): Tick on the wanted loopback
Then click on <Activate> button
Line Side


a Issue 01
Loopback (3/4)

To activate a loopback (3/3): Tick on the wanted loopback
Then click on <Activate> button
Radio Side


a Issue 01
Loopback (4/4)
To deactivate a loopback:
Click on <Deactivate> button


a Issue 01
10.4 Alarms Tool


a Issue 01
10.5 Power Measurements Tool


a Issue 01
10.6 Modem Measurements Tool


a Issue 01
10.7 Events Tool


a Issue 01
10.7 Events Tool [cont.]
Event Log Browser is an application which

allows to display all the events occurred in the
NE. An event is meant to be:
a configuration change
a change of the value of an attribute
an automatic switchover
a manual operation carried out by the operator.

The following information is provided for each event:

Date: date and time of occurrence of the event. The format is week day/month/year hh:mm:ss.
Reference Time (CEST) year.
Source: Indicates which application (tool) is invoked.
Details: a statement built with the event log data to explain what the event represents.

a Issue 01
Clear: to clear the history events memory
Filter: to filter the display of events (see next page)


a Issue 01
Filter Errors: to display only the non successful events
Filter Informations: to display only the informations events
No Filter: to display all events


a Issue 01
11 Performance Monitoring Perspective


a Issue 01
11.1 Performance Monitoring Perspective Navigation
MSS-1c
MPR-e


a Issue 01
11.1 Performance Monitoring Perspective Navigation [cont.]
Performance Monitoring Perspective

is divided in:
Normalized
CH1 Radio Hop- Counters Thresholds
- 15Min Counters
- 24H Counters
CH0 Radio Hop- Counters Thresholds
- 15Min Counters
- 24H Counters
Radio Link - Counters Thresholds
- 15Min Counters MSS-1c MPR-e
- 24H Counters
Adaptative Modulation
15Min Counters
24H Counters
Ethernet
QoS Counters
Traffic Port Counters (for MPR-e only) The use of this Perspective
Monitoring Performance Monitoring
Alarms
Events is explained in the module
Section 3 Module 6


a Issue 01
Blank Page


a Issue 01
12 MSS-1c Provisioning Tool - Main View

WebEML MPR TCO Suite Rel. 4.2

a Issue 01
12 MSS-1c Provisioning Tool Main View
12.1 Main view
MSS-1c Provisioning Tool Main Tab-panel
RESOURCE AREA
NAVIGATOR

shown on the top.
Title: MCT connected to Provisioning Tool

Main Tab-panel
to manage the NE.
Configuration (to provision, to configure the equipment)
shown.
is shown.
Figure (Main view) is the entry point of the application and provides basic diagnostic and configuration
functions. Following multiple main views are available:
Ethernet Port configuration, for Ethernet domain;
PDH Port configuration, for PDH domain;
Management Port configuration, for Management domain;
TDM cross-connection between Radio and user ports, for Cross-connection domain;
Synchronization configuration, for Synchronization domain;
Bridge configuration, for Bridge domain;
Port VLAN configuration, for VLAN domain;
Navigation from main view to multiple main views (related to the equipment components) can be done by
simply double-clicking on the component graphical representation. Such operation will open a new window
containing selected secondary view.

a Issue 01
Quick Access Buttons
This area contains a selection of handy quick-access

buttons for common features.
Exit button from the Main View
Second button: for File Management to manage the

Configuration Files


a Issue 01
12.4 Main Tab Panel
Main Tab Panel
The Main Tab panel permits to choose a specific tool (called

Perspective) to manage the NE.

Configuration (to provision, to configure the equipment)
NOTE:
The Main Tab panel management is exactly the same as the Main Tab panel
of the MSS-1c main view or MPR-e main view.

The operator choice in the Main Tab Panel makes changes in the contents of:
1) Navigator Area
This area displays all the available tasks for a specific tool (perspective).
2) Resource area
This area displays a representation in tabular view or in graphical view of the selected resource
for a specific tool (perspective).
Operator facility:
By moving the margin, we can see all the opened tools (perspectives)

a Issue 01
12.5 Navigator Area
Navigator Area
The Navigator Area displays all the available

management tasks for a specific tool
(Perspective).
The following tools are present:

File Management
(to manage the Configuration Files)
MSS-1c Configuration
(to provision the MSS-1c of the equipment)
Ethernet Port configuration
PDH Port configuration
Management Port configuration
TDM cross-connection between Radio and user ports
Synchronization configuration
Bridge configuration
Port VLAN configuration

NOTE:
The Navigator Area management is exactly the same as the Navigator Area of the MSS-1c main view or
MPR-e main view.

a Issue 01
12.6 Provisioning Tool Menus
Provisioning Tool Application Menus
Two menus are available:
1) FILE
Two choices:
to exit the MCT.
to manage the Configuration Files
2) HELP
One choice: to have an help on Provisioning Tool.

Help Menu
Configuration Details
Plug-in Details

a Issue 01
13 MSS-1c Provisioning Tool -
Configuration Perspective


a Issue 01
13 MSS-1c Provisioning Tool Configuration Perspective
13.1 Configuration Perspective Navigation
This tool allows to configure the MSS-1c.

It is launched by the < Start Tool > button
on the MSS-1c menu of the WebEML


a Issue 01
13.1 Configuration Perspective Navigation [cont.]
Navigation Configuration
Perspective is divided in:
File Management
PDH port configuration
Management port configuration
TDM cross-connection between Radio and
user ports


a Issue 01
13.2 File Management Tool


a Issue 01
13.2 File Management Tool [cont.]
Provisioning Mode Three Provisioning Mode:
Initial Configuration:
to start from an empty configuration
Reconfiguration:
to load an existing configuration file and then modify
everything
Change Configuration:
to load an existing configuration file and then modify only
some items
Provisioning File

After we have finished the Provisioning of the MSS-1c,
(It means after to have filled in all the parameters inside each tool of all Perspective),
Save it in a Configuration File by using the Provisioning File field with the button < Create >
NOTE:
The Change Configuration mode is useful to modify an running configuration without impacting
already configured services (cross-connections and VLANs).
When this file will be downloaded to the NE by using the WebEML (menu Configuration > MSS-1c )
the NE will not reboot after the download.

a Issue 01
Reconfiguration


a Issue 01
Change Configuration


a Issue 01
13.3 MSS-1c Configuration Tool


a Issue 01
13.4 Ethernet Port Configuration


a Issue 01
13.4 Ethernet Port Configuration [cont.]
First, choose the type of MCT

connection to the equipment:
Optical Port (MPT-e)
Electrical Port (MPT-e, MSS-1c)
For each used User Port,

Enable the Port
Choose the type of connection for SFP
connector :
Disabled
Optical Port
Electrical Port
Choose the Speed Directionality

The Settings view performs all the available functions for Ethernet tributary ports. Information
related to a data port configuration is provided by the following parameters:
Check the box: the port will negotiate speed and duplex mode with its peer.
Uncheck the box: speed and duplex mode are selected by the operator (forced mode).
Speed -Directionality, (10 Mb/s Half Duplex, 10 Mb/s Full Duplex, 100 Mb/s Half Duplex,
100 Mb/s Full Duplex). Check to allow communication at the selected data rate between two
locations. Choose half duplex for only one direction at a time, or full duplex for communication in
both directions at the same time.

a Issue 01
13.4 Ethernet Port Configuration [cont.]
Example :
Ethernet Port
configuration
using the 4 users ports
Only for User 2 port, we have the possibility to

choose a Network Synchronisation for 1 Gb/s
Ethernet frames in Autonegociated mode.
(Auto, SyncE IN, SyncE OUT)

Speed -Directionality, (10 Mb/s Half Duplex, 10 Mb/s Full Duplex, 100 Mb/s Half
Duplex, 100 Mb/s Full Duplex). Check to allow communication at the selected data rate
between two locations. Choose half duplex for only one direction at a time, or full duplex for
communication in both directions at the same time.
NOTE:
To configure a SyncE electrical port like user 2, proceed the same way as for user 1. In addition
configure the Network synchronization.
1. Auto, if you do not use the syncE property of the port
2. SyncE IN, if you use the port as synchronization input. MSS-1c receives clock from external
equipment.
3. SyncE OUT, if you use the port as a synchronization output. MSS-1c sends its clock to external
equipment.
this feature is authorized only if the port is set in Auto negotiation mode with speed 1000 Mbit/s
and full duplex only.

a Issue 01
13.5 PDH Port Configuration
Ressource Configuration Area:

displays the tributary port
to be configured and the
choice of impedance (75 or Ressource List Area: displays
120 Ohms) to be performed tabular information about
for all tributaries objects properties through
tab windows. This area
performs the available
functions for involved
resource.

2) Enabled: with a fixed type of frame (Unframed) to enable the port
7) TDM Clock sync: type of the clock to be associated to the tributary
(Adaptive/Differential/Tdmline)
8) Node Timing: to enable for the corresponding port the Node Timing synchronization. When it is
selected, the regenerated E1 at receiver side are synchronized to the network element clock
(NEC).
9) Xco to Port: to cross-connect the E1 port to Radio or User port
10) MAC Address: to set the destination MAC address of the equipment in case of TDM2Eth cross-
connection
Note: Columns 5, 6, and 7 are only available if the Service Profile is TDM2Eth.

a Issue 01
13.5.1 PDH Port Setting
PDH Port Setting

This Resource List Area performs all
available functions for a tributary port. The
managed tributary types are E1 streams. To
define the involved ports, the interface
selection in the Resource List Area is first
required; then make your choice in the
different fields.

In the Resource List Area there are the following fields:

Enabled: with a fixed type of E1 frame (Unframed) to enable the port
Service Profile:
The possible profiles are:
TDM2TDM
TDM2Eth
Flow Id: To implement cross-connections between line side and radio side each E1 tributary must
be associated to an identifier. Enter the Flow identifier value in the relevant field (possible values:
2 to 4080).
Fields ECID Tx, ECID Rx and TDM Clock Sync. can be written only if the Service Profile is
TDM2Eth.
With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time
Protocol is used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP -
Real Time Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have
mixed configurations with service profiles using RTP and other service profiles not using RTP.
Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure other E1
with service profile TDM2Eth only with the Differential clock source (not with the Adaptive clock
source). If the Adaptive clock source is requested the E1 must be connected to another PDH unit.
Node Timing: to enable for the corresponding port the Node Timing synchronization. When it is
selected, the regenerated E1 at receiver side are synchronized to the network element clock
(NEC).
Xco to Port: to cross-connect the E1 port to Radio port or User (User1, User2, User3, User4)
port
MAC Address: to set the destination MAC address of the equipment in case of TDM2Eth cross-
connection
a Issue 01
13.5.2 Information on Circuit Emulation
9500 MPR-E performs Circuit Emulation on PDH TDM flows, and then
transport those "TDM packets" mixed to native Ethernet frames.
The Circuit Emulation IWF (inter-working function) is according the
Metro Ethernet Forum implementation agreement known as MEF 8,
limited to the structure agnostic case.
MEF 8 emulated circuits is based on exchange of service parameters
between two CES IWFs at either end of the emulated circuit; if one of
those IWFs belong to the 9500 MPR-E the following parameters are
defined:
MAC addresses of the two IWFs
Payload size
ECID (2 different values may be used for each direction)
TDM clock source
clock recovery adaptive
VLAN (One Vlan is assigned to each bi-directional circuit emulated E1 flow)


a Issue 01
13.5.2 Information on Circuit Emulation [cont.]
RTP, which is optional in MEF8, is always present, but not used if the
clock recovery is not differential.
The common clock for Differential clock recovery is 25 MHz.
Three different cases of Circuit Emulation services are implemented:
1) TDM2TDM
2) TDM2ETH
3) ETH2ETH
NOTE:
For MPR-e, only one case of Circuit Emulation service is implemented:
1) ETH2ETH


a Issue 01
TDM2TDM
Both the IWFs belong to 9500 MPR-E and the packets are not supposed
to go out the 9500 MPR-E network.
MAC addresses are determined as consequences of the cross
connections.


a Issue 01
TDM2ETH
Only one of the IWFs belongs to 9500 MPR-E and the packets are
supposed to go out the 9500 MPR-E network.
node where that TDM2ETH traffic goes through an user Ethernet port). In
such ETN the source address will be the node Mac address, the dest. mac
ECID: provisioned by ECT/NMS, 2 different values may be used for each
direction
TDM clock source will be provisioned by ECT/NMS: clock recovery adaptive,
Flow Id will be provisioned by ECT/NMS (One Vlan is assigned to each bi-
For this case the expected latency for 1 hop only is 3.5 msec for 256
bytes.


a Issue 01
ETH2ETH
None of the IWFs belongs to 9500 MPR-E.
None of the above parameters has to be configured (the 9500 MPR-E is
transparent).
Any packet belonging to an Eth2Eth TDM flow is treated as any other
Ethernet packet with the only exception of giving it an higher priority
based on the MEF 8 Ethertype.


a Issue 01
13.5.3 Circuit Emulation Application Examples

Case 1
The E1 stream is inserted in Node 1 and extracted in Node 2. In this case the two IWFs used to
packetize the traffic for the Ethernet switch in the Core-E module are both internal to the 9500 MPR-E
network. The Circuit Emulation Service is TDM2TDM in Node 1 and Node 2. The Cross connections to be
implemented are PDH-Radio type.
Case 2
The E1 stream is inserted in Node 1 and extracted in Node 2. One IWF is inside the 9500 MPR-E, but the
second IWF is external to the 9500 MPR-E network. The Circuit Emulation Service is TDM2ETH in Node 1
and Node 2. The Cross connections to be implemented are PDH-Radio type in Node 1 and Radio-Eth
type in Node 2.
Case 3
The E1 stream is inserted/extracted in Node 1. One IWF is inside the 9500 MPR-E, but the second IWF is
external to the 9500 MPR-E network. The Circuit Emulation Service is TDM2ETH in Node 1 and Node 2.
The Cross connections to be implemented are PDH-Eth type in Node 1.

a Issue 01
13.5.3 Circuit Emulation Application Examples [cont.]

Cases 4 and 5
In these cases Ethernet packets enter Node 1 and are extracted in Node 2. In case 4 the Ethernet
packets encapsulate the E1 stream; in case 5 the packets are native Ethernet packets. None of the
IWFs belongs to the 9500 MPR-E network. The Circuit Emulation Service is ETH2ETH in Node 1 and Node
2. No Cross connections must be implemented. The path is automatically implemented with the
standard auto-learning algorithm of the 9500 MPR-E Ethernet switch.

a Issue 01
13.6 Management Port Configuration
NE MAC Address:
This field is read-only
which shows the MAC
Address of the NE. This
MAC Address must be
used in the cross-
connection with
TDM2ETH profile.


a Issue 01
13.6 Management Port Configuration [cont.]
NMS1/NMS2 Port Setting
For each used NMS Port (NMS1, NMS2),

Enable the Port
Enable/Disable the Autonegotiation

Speed -Directionality, (10 Mb/s Half Duplex, 10 Mb/s Full Duplex, 100 Mb/s Half Duplex,
100 Mb/s Full Duplex). Check to allow communication at the selected data rate between two
locations. Choose half duplex for only one direction at a time, or full duplex for communication in
both directions at the same time.

a Issue 01
13.6 Management Port Configuration [cont.]
TMN Inband Port Setting
TMN IN-BAND
Defines the IP address of the TMN supervision channel defined with a VLAN
identifier inside a user Ethernet traffic.
For TMN Inband,

Enable the Port
Choose the User Port where to send the TMN
supervision channel
Enter a VLAN Identifier number for the TMN
supervision channel


a Issue 01
13.7 TDM Cross-Connection Between Radio and Users Ports

The Cross-connections field contains the list for all the implemented cross-connections.
Maximum number of cross-connections: 239.

a Issue 01
13.7 TDM Cross-Connection Between Radio and Users Ports [cont.]
MSS-1c Cross-Connection Block Diagram
The block diagram presents the different elements involved in the cross-
connection, in green the PDH and CES part (encapsulation in Ethernet
frame done by IWF), in blue the Ethernet part realized by the switch.
Radio Port 1 Radio Port 2

MSS-1c
TDM IWF
User Port 1 User Port 2 User Port 3 User Port 4 PDH Ports
E1-1 E1-2

a Issue 01
To Add a New Cross-Connection
With the empty line, fill in the different items:

User Port (User1, User2, User3, User4)
Flow Id
Service Profile
TDM Clock Source (Differential, Adaptative)
Outgoing MAC Source (read-only field: its the local MSS-1c MAC address)
Outgoing MAC Destination
Then click on the < Add Cross-Connection > button

Notes:
The unicast MAC address of the NE is shown in the MSS-1c Provisioning Tool Configuration
Perspective Management Port Configuration (NE Public Mac Address or Bridge Address).
To assign the multicast MAC address of a NE start from the unicast MAC address and change a digit in
the first pair of digits in order to generate an odd binary number: example change the first pair of
the address from 00 to 01.

a Issue 01
To Remove a Cross-Connection
Select the cross-connection line to delete
Then click on the < Remove Cross-Connection > button


a Issue 01
Navigation in the Cross-Connection List
Four buttons to navigate in the Cross-Connection List

To go to the next cross-connection
To go to the last cross-connection
To go to the previous cross-connection
To go to the first cross-connection


a Issue 01
TDM to Ethernet: MAC address configuration
1+0 no protection
1+1 Radio protection between NE B and C

In these types of cross-connections the destination MAC address of the adjacent NE (unicast address in
case of unprotected configurations, multicast address in case of protected configurations) must be
inserted during the cross-connection creation.
To assign the multicast MAC address of a NE, start from the unicast MAC address and change a digit in
the first pair of digits in order to generate an odd binary number: example change the first pair of the
address from 00 to 01.

a Issue 01
13.8 Synchronization Configuration


a Issue 01


2G,3G,4G
9500 MPR
SvncE Eth SyncE
Eth
9500 MPR
Private
Business
Office
9500 MPR
9500 MPR
options options
Fixed
DSL
1588v 1588v2
Phone 2 TOD TOD
protocol protocol


All the NEs radios in the network must be synchronized to the same clock.
SynchrE: Any Synchronous Ethernet clock source available at enabled User Ethernet traffic interfaces
(both electrical and optical) configured in synchronous operation mode (the specific User Ethernet
port has to be chosen).
From ITU-T G.8264 point of view, the MSS is a Synchronous Ethernet equipment equipped with a
system clock (NEC) following the ITU-T G.8262 recommendation.
A User Ethernet interface configured in synchronous operation mode can work only at
1Gigabit/s.
In the particular case of electrical User Ethernet interfaces, these interfaces perform link auto
negotiation to determine the master and slave clocks for the link.
The clock slave role must be configured as part of auto negotiation parameters in order to use
the interface as Synchronous Ethernet clock source.
N.B.: SSM is not supported, therefore MPR cannot be included in a Synch-E ring.
The Symbol Rate of the Rx signal of any available Radio direction (the specific Radio Port has to be
chosen).

a Issue 01
How to Synchronize
Each Network Element must have a reference Clock (NEC), which will be
distributed to each function of the MSS-1c. Such clock is a 25 MHz generated in
the MSS-1c.
The sources can be:
[1] Free Run Local Oscillator.
[2] Any E1 available at input traffic interfaces (the specific E1 port has to be chosen)
[3] Radio Port: Symbol Rate of the Rx signal of any available Radio direction
[4] User 4: Network synchronization for 1 Gb/s Ethernet frames (Auto, SyncE IN, SyncE
OUT)


a Issue 01
NEC Role
All the NEC has to be configured as Master Role or Slave Role.

If Master Role,
The Restoration Mode can be Revertive and Not Revertive
The Primary sources must be chosen among 1) or 2).

then the Master Secondary Source doesn't need to be selected because the Primary is never
supposed to fail.

then Master Secondary Source must be selected among 1) or 2).
If Slave Role,
The Primary Source must chosen between 2) and 3)
The Secondary Source can be chosen among 1) or 2).

Each function will mute its own Synchronization clock in case of Fail Alarm.
For each available sync source, the signal Degrade Alarm is detected on each available sync source.
Such Signal Degrade alarm raises also in case of muted (missing) clock.

a Issue 01
13.9 Bridge Configuration
NE Bridge mode: 802.1D

When the NE is configured in this mode (default configuration), the Ethernet traffic is switched
The packets from the user Ethernet ports having the VLAN ID out the allowed range (0 and 2-4080)
are dropped. The packets having a VLAN ID already used for a TDM flow are accepted.

a Issue 01
13.9 Bridge Configuration [cont.]
NE Bridge mode: 802.1Q

When the NE is configured in this mode, the management of Ethernet traffic looking the VLAN is
enabled.
In this modality, a VLAN will be assigned to all Ethernet frames inside the MPR network.

a Issue 01
To Add a New VLAN NE Bridge mode: 802.1Q

VLAN Id
VLAN Name
Select the User Port (User1, User2, User3, User4) which transports the VLAN
Select for this User Port if it transports only Untagged frames (if not, all
Ethernet frames is sent through this User Port)
Then click on the < Add VLAN > button

N.B.: The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH)
cannot be used.
3) VLAN Ports (User 1, User 2, User 3, User 4): Select the ports members of this VLAN by putting a
check mark on the relevant check box. All the user Ethernet ports can be considered. Both enabled
and disabled user Ethernet ports (radio ports are implicitly enabled) can be member of a VLAN. This
means that a disabled port can be configured as a member of a VLAN and a port already member of
a VLAN can be disabled continuing to be a member of the same VLAN.
4) Untagged Ports : Select, among the ports belonging to this VLAN (members), the untagged ports
disabled, are manageable. The VLAN cannot be removed from the radio ports.
the ports are members and the Untag flag is set to False, which means all the frames are
transmitted with Tag.
N.B.: Tagged frames
packet is dropped.

a Issue 01
To Remove a VLAN NE Bridge mode: 802.1Q
Select the VLAN line to delete
Then click on the < Remove VLAN > button


a Issue 01
Navigation in the VLAN List NE Bridge mode: 802.1Q
Four buttons to navigate in the VLAN List

To go to the next VLAN
To go to the last VLAN
To go to the previous VLAN
To go to the first VLAN


a Issue 01
13.10 Port VLAN Configuration

The Port VLAN Configuration performs all the available functions for Ethernet tributary ports.
Information related to a data port configuration is provided by the following parameters:
The traffic, received on each user Ethernet port, can be untagged or tagged. For each port it is
possible to configure:

Admit tagged only (only tagged frames are allowed in ingress and untagged frames are
dropped)

Admit all (tagged, untagged and priority frames are allowed in ingress)
Port VLAN ID: if the Acceptable Frame Type is set to Admit all the VLAN-ID and Priority fields,
to be added in ingress to untagged frames, must be configured. Only VLAN-ID values already
defined (in the VLAN management menu) can be configured for this purpose. The Priority values
allowed are in the range 0 - 7.
The VLAN 1 is always removed when the frame is forwarded.
The untagged frames received on one user Ethernet port, configured as Admit tagged
only, are dropped.
The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as
Admit tagged only, are
dropped.
The priority packets (VLAN-ID=0) received on one user Ethernet port, with the Admit
all configuration enabled, are
managed as untagged frames for VLAN-ID field, while the Priority field is the same of the
received packets.
a Issue 01
13.10 Port VLAN Configuration [cont.]
How to Configure
For each User Port (User1, User2, User3, User4)

Select for this User Port if it transports All Frames or if it transports
Tagged Frames Only
In case of Admit All Frames
Select the Port VLAN Id (configured previously)

to be sent with a priority
Select the Priority level for this port VLAN Id


Admit tagged only (only tagged frames are allowed in ingress and untagged frames are dropped)

Admit all (tagged, untagged and priority frames are allowed in ingress)
Port VLAN ID: if the Acceptable Frame Type is set to Admit all the VLAN-ID and Priority fields, to
be added in ingress to untagged frames, must be configured. Only VLAN-ID values already defined
(in the VLAN management menu) can be configured for this purpose. The Priority values allowed
are in the range 0 - 7.
only, are dropped.
The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as Admit
tagged only, are
dropped.
The priority packets (VLAN-ID=0) received on one user Ethernet port, with the Admit all
configuration enabled, are
received packets.
a Issue 01
Exercices
Configure the equipment.

Enable the tributaries.
Create some cross-connections.
Set the Transmitter of Channel 1 to transmit a constant power.
Read the Rx power of Channel 1.
Read the RF frequency of Channel 1.
Activate the loopback.


a Issue 01
End of Module
Operator interface MPR terminal


a Issue 01
35
Section 3
NE operation
Module 5
Initial configuration MPR terminal
a Issue 01
9500 MPR

a Issue 01
Blank Page

NE operation Initial configuration MPR terminal
Document History

Marcoussis

a Issue 01
Module Objectives
Configure the MPR Terminal equipment starting from a scratched NE.


a Issue 01


a Issue 01
Table of Contents
Page
1 Initial Configuration 7
1.1 General Requirements 8
1.3 Provision Commissioning 18
1.4 Provision NE Time 20
1.5 Provision Site Information 21
1.6 Provision Protection 22
1.7 Provision Synchronization 23
1.8 Provision Radio 24
1.9 Provision Advanced Radio 30
1.10 Provision MSS-1c 31
1.11 Provision Ethernet Traffic QoS 35
1.12 Provision Networking 38
2 MSS-1c Provisioning Tool 43
2.1 Main view 44
2.2 Configuration Perspective Navigation 45
2.4 File Management Tool 47
2.5 MSS-1c Configuration Tool 48
2.6 Provision Ethernet Port 49
2.7 Provision PDH Port 51
2.8 Provision Management Port 53
2.9 Provision TDM Cross-connection between Radio and User Ports 54
355
2.10 Provision Synchronization All Rights Reserved Alcatel-Lucent 2011 55
2.11
NE operation Provision
Initial configuration Bridge
MPR terminal 56
2.12 Provision Port VLAN 58

a Issue 01


a Issue 01


a Issue 01
1.1 General Requirements
PC HW Configuration
CPU: AMD Atlhon/Intel Celeron/Intel Pentium 4 or higher
RAM: 1 GB
Hard Disk space: 1.5 GB (available space for log files, JRE excluded)
Display Resolution: 1280x800 pixel
DVD-ROM Drive (needed for the TCO Suite)
Ethernet Interface: Ethernet Card 10/100 Mbps
Operating Systems Supported

Microsoft Windows XP Professional service pack 3 or Microsoft Windows Vista
Ultimate service pack 2 or Windows 7
Note:
Classic windows setting must be choosen with Windows Vista and Windows 7


a Issue 01
1.1 General Requirements [cont.]
Additional requirements
Microsoft Internet Explorer 6 SP1, 7, 8, Mozilla Firefox 2, 3, 3.5
The Administrator password is needed only for Java installation
When Java has been installed, the standard user can run the WebEML Suite
Java Runtime Environment (JRE) 6 Update 14
Warning:
An FTP server must be installed on the PC of MCT user with read right &
write right, and the Windows Firewall must be desactivated.


a Issue 01
1.2 Initial Turn-up
Local copy the WebEML to PC.
Before operating the user system interface (USI) for the first time, the
programs contained on the CD ROM must be copied on the PC.
Follow these steps to copy the WebEML software to the PC.
1 - Insert the TCO Software Suite CD into the DVD-ROM drive.
Note:
The TCO Software Suite will auto-run and open up the computer's default
browser program (if auto-run feature is enabled on user's PC) as soon as the
DVD-ROM is read by the PC. If auto-run does not start, user must run
(double-click with left mouse button on it) the Start.exe file, available on
DVD-ROM root, in order to launch the Software Package.
See next slide


a Issue 01
2 The following screen opens:
3 Double click on MPR Tools button See next slide


a Issue 01
4 The following screen opens:
5 Double click on MSS-1c or MPR-e icon to perform the Local

Copy of the WebEML See next slide

NOTE:
An alternative way to perform the Local Copy of the WebEML is by clicking on the Advanced
Settings button.
This alternative way is explained in the User Manual.

a Issue 01
6 Click on <No>

7 Click on <Yes> to perform
the WebEML Local Copy
8 Select the directory

and click on <Open>

9 The copy is now in progress

See next slide

NOTE:
Settings button.

a Issue 01
10 Wait until the following message will appear.

Click on <OK>

11
11 Click on <Yes> to set a

link on the desktop
12
12 An icon will be created on the desktop

NOTE:
Settings button.

a Issue 01
WebEML Start To start the WebEML double click on

the relevant icon on the PC desktop
NETO
opens

Insert the IP address
of the NE
(default: 192.168.30.1)
and click <OK>
See next slide

N.B.
To access the NE the PC must be configured to Get automatically an IP address, because the NE is
configured as DHCP Server with default IP address 192.168.30.1 and subnet mask 255.255.255.252.
The PC Ethernet port must be connected to the CT connector of the MSS-1c.
N.B.
192.168.30.1 is the IP address of the port from MSS-1c and cannot be modified. The management can
be done also by the NMS port, but the PC must be configured with fixed IP and gateway. First open
the WebEML and after connect the cable.
Warning:
Without the MPT connected to the MSS-1c, it is not possible to open the WebEML on the CT port from
MSS-1c.
Warning:
If all the WebEML images/icons are missing, check that file msimg32.dll is present inSystem32.

a Issue 01
When the NE is supervised,

click on <Show>
Then, the <Main view> opens

Note: Default User Accounts at the NE installation time, one default user account is created on NE
Username: admin
Password: admin

a Issue 01
START
Provisioning MPR
Provision NE Time
Provision Site Information
Provision Protection *
Provision Radio
Provision Advanced Radio
Provision MSS-1c
Provision Ethernet Traffic QoS
* Protection: in this current Provision Networking

release, only 1+0


a Issue 01
1.3 Provision Commissioning MSS-1c
Selecting Configuration Tool
Select
Commissioning
Perspective to start
Select
Configuration
Tool


a Issue 01
1.3 Provision Commissioning [cont.] MPR-e
Selecting Configuration Tool
Select
Commissioning
Perspective to start
Select
Configuration
Tool


a Issue 01
1.4 Provision NE Time
Date/Time Configuration
Select
Date/Time Tool
If SNTP Protocol is disabled, when

checked, enables function to
synchronize Operating System and
Network Equipment Times.

The user can synchronize the NE time from either the PC/laptop or Network Time Protocol (NTP)
servers. Time and date provisioning is accomplished using the NE Time Configuration screens.

a Issue 01
1.5 Provision Site Information
Site Information Configuration
Write down the Site Name
Select Site
Information Tool
Write down the Site Location


a Issue 01
1.6 Provision Protection
Protection Configuration
Select the Protection type:

RPS 1+0
Select
Protection
Tool


a Issue 01
1.7 Provision Synchronization MPR-e only
If you select PCR, Fill

in the corresponding
Source and Destination
Mac Address
If you select SyncE, Choose the role

of the NE for the synchronization
Select (Automatic, Master, Slave)
Synchronization
Tool


a Issue 01
1.8 Provision Radio
Radio Configuration
Choose the Telecommunication

Standard: ETSI, ANSI
Select
Radio Tool


a Issue 01
1.8 Provision Radio [cont.]
Radio Configuration in Fixed Coded Modulation
Select in the Coding Modulation

Type field Fixed (FCM).
Select in the Channel Spacing field

the suitable channel spacing to be used.

Select in the Modem Profile Option
field the spectral efficiency class to be
set as reference
Select in the Reference Modulation

field the suitable Modulation scheme.
According to the previous four

selections the relevant capacity in the
Allowed Modulations field will appear.


Channel Spacing:
3,5 MHz
7 MHz
14 MHz
28 MHz
40 MHz
56 MHz

QPSK
8 PSK
16 QAM
32 QAM
64 QAM
128 QAM
256 QAM

a Issue 01
Radio Configuration in Adaptative Coded Modulation
Select in the Channel Spacing field the Select in the Coding Modulation
suitable channel spacing to be used. Type field Adaptative (ACM).

Select in the Modem Profile Option field
the spectral efficiency class to be set as
reference
Select in the Reference Modulation field

the lowest modulation scheme (from QPSK)
to be used by the Adaptative Modulation.
Choose in the Allowed Modulation field

all the modulation schemes to be used with
the Adaptive Modulation. The modulation
schemes (from the lowest to the highest
scheme) must be contiguous
The Allowed Modulation field is a read-only

field, which shows the current used
modulation and capacity. The current
modulation will depend on the fading
activity during the propagation.
To update this field press the Refresh
button.

forced to 16 QAM and then to 64 QAM. Also if the current Modulation is 64 QAM, to pass to 4 QAM
first must be forced to 16 QAM and then to 4 QAM.

Channel Spacing:
3,5 MHz, 7 MHz, 14 MHz, 28 MHz, 40 MHz, 56 MHz

QPSK, 16 QAM, 32 QAM, 64 QAM

a Issue 01
Select in the Transmit Power Control
Mode field the suitable mode (ATPC) to be
used.
Tick on Mute if needed, then click on

<OK>

If the Transmit Power Control Mode is
set as RTPC, in the middle field write the
new value within the allowed transmitted
power range. The range is shown in <TX
Power> field in the left and right fields.
Choose in the ATPC Settings field the

ATPC Range and ATPC Remote RSL
Threshold parameters.
Select in the <Driving Remote RSL in
1+1 HSB> field the suitable value. In 1+1
FD and HSB configurations both the
transmitters can be driven by the lowest or
by the highest RSL values of the two remote
demodulators.
NOT APPLICABLE in this current release

The information related to the transmitter status is shown by an icon closed to the Mute field. To
squelch the transmitter tick on Mute field and press Apply button.

a Issue 01
Frequency
Select in the Shifter field the

suitable frequency separation to be
used.
Select in Tx frequency field the Note: The Tick button

suitable Tx frequency (the Rx <Allow Rx Frequency Tuning>
frequency is automatically calculated permits to change both the Tx
by using the inserted Tx frequency and and Rx Frequencies.
the shifter).


a Issue 01
Frequency Note: By clicking on Frequency Plan you can display the
associated frequency plan of the connected ODU according
[cont.] to the Radio channels frequencies configuration (Shifter,
Tx Frequency, Rx Frequency) with, in red, the channel
spacing configured in Modulation field.


a Issue 01
1.9 Provision Advanced Radio
Advanced Radio Configuration
Select Advanced
Radio Tool
In this Tx Identifier field,
write down the link
identifier inserted on the
Tick on Enabled transmitting NE.
In this Expected Rx
Identifier field, write down
the link identifier expected
at the receiving NE


a Issue 01
1.10 Provision MSS-1c MSS-1c only
Click on the Start Tool button to run
the < Provisioning Tool > application.
Select This tool is explained in the next
MSS-1c chapter 2 MSS-1C Provisioning Tool -
Tool


a Issue 01
1.10 Provision MSS-1c [cont.] MSS-1c only
FTP Server Parameters Configuration

In the FTP Server Parameters, write down the values of the
different fields corresponding on the FTP Server.
By clicking on the Check button, the server access values will
be filled in automatically with the default configuration.

By clicking on the Check button, the server access values will be filled in automatically with the
default configuration.

User Id: anonymous
Password: -
Port: 21
Root Dir: /

a Issue 01
Download and Execute MSS-1c Provisioning File
Through this field the <MSS-1c Configuration

File> is downloaded to the NE in order to set the
MSS-1c subrack with operational parameters.
This field can be used as a configuration RESTORE.


the directory and,
the <MSS-1c Configuration File> file
containing the MSS-1c operational parameters you want to download to the MSS-1c subrack.
2. Then, click on the Download and Execute button to begin the download process.
3. When the <MSS-1c Configuration File> download starts, a screen showing the in progress operation
of the download appears. The download is aborted if the Abort button is pressed.
4. Click Ok.

a Issue 01
Upload MSS-1c Provisioning File
Through this field the MSS-1c subrack

operational parameters is saved in a <MSS-1c
Configuration File>.
This field can be used as a configuration BACKUP.


the directory and,
the <MSS-1c Configuration File> file name
where you want to upload the ACTIVE MSS-1c operational parameters from the MSS-1c subrack.
2. Then, click on the Upload button to begin the upload process.
3. When the ACTIVE MSS-1c operational parameters upload starts, a screen showing the in progress
operation of the upload appears. The upload is aborted if the Abort button is pressed.
4. Click Ok.

a Issue 01
1.11 Provision Ethernet Traffic QoS MPR-e only
Ethernet Traffic QoS Configuration
Select the
QoS Classification
In Ether Type
It can be Classification field,
None set, if desired, for
IEEE 802.1p each non High
Diffserv Priority Queue (1
to 5), the type of
Ethernet frame
that will be sent to
this queue.

In Scheduling
Algorithms field, set,
if desired, for each
non High Priority
Select Ethernet Queue (1 to 5),
Traffic QoS Tool The Scheduling Mode
and the DWRR
Weight of the DWRR
scheduler chosen for
None Classification screen this queue.
Ether Type examples:

0x0800=IP
0x0806 = ARP
0x8035 = RARP
0x888E = 802.1X
0x8863 = PPPoE Control frames
0x8864 = PPPoE Data frames

a Issue 01
1.11 Provision Ethernet Traffic QoS [cont.] MPR-e only
IEEE 802.1p Classification
Select in this field the IEEE

802.1p priority frames
allowed for each non High
Priority Queue (1 to 5)
classified as:
- Best Effort frames (001),
- Background frames (000),
- Spare frames (010),
- Excellent Effort frames (100),
- Controlled Load frames (011),
- Video frames (110),
- Voice frames (111),
- Network Control frames (101).
Note: you can choose the

Defaults values
IEEE 802.1p Classification screen


a Issue 01
1.11 Provision Ethernet Traffic QoS [cont.] MPR-e only
Set, if desired, in this field

the range of Diffserv
classification values for each
non High Priority Queue (1 to 5):
Minimum Diffserv Code Point
Maximum Diffserv Code Point
Note: you can choose the

Defaults values
Diffserv Classification screen

Notes:
The highest priority queue is 5
The highest priority queue corresponds to the transmission of packets whose diffserv classification priority is
the highest (range of diffserv priority values).
The next queue does not contain the range of diffserv priority values of the previous queue.
The range of diffserv priority values has to be set in ascending order corresponding to the ascending order of
the queues.

a Issue 01
1.12 Provision Networking MSS-1c
Network Interfaces Configuration
Tick on TMN RF Access to validate the TMN

RF channel to supervise the remote NE

Fill in the
local IP
Address of
the NE
Fill in the IP
Address of the
NMS1 access
Fill in the IP
Address of the
NMS2 access
Select
Network Fill in the IP address of the This field is
Interfaces TMN supervision channel, read-only (IP
Tool if used, defined with a Address of the
VLAN identifier inside a CT access)
user Ethernet traffic
NE IP Parameters
This local IP address is the IP address associated to a virtual interface and to the other interfaces
which use the PPP protocol (the TMN-RF channels).
Default mask: 255.255.255.255
Note: After NE IP Address change, the NE restarts

a Issue 01
1.12 Provision Networking [cont.] MPR-e
Network Interfaces Configuration
Tick on TMN RF Access to

validate the TMN RF channel
to supervise the remote NE
Select
Network
Fill in the Fill in the IP address of the
Interfaces local IP TMN supervision channel,
Tool Address of if used, defined with a
the NE VLAN identifier inside a
user Ethernet traffic
NE IP Parameters
This local IP address is the IP address associated to a virtual interface and to the other interfaces
which use the PPP protocol (the TMN-RF channels).
Default mask: 255.255.255.255
Note: After NE IP Address change, the NE restarts

a Issue 01
1.12 Provision Networking [cont.]
Static Routing Configuration Select in Route Type the
corresponding route type:
Select Default, Host or Network
Static Fill in the values of Destination
Routing IP & Mask Addresses and
Tool Gateway IP Address if
necessary

Select in Point To Point Link
the corresponding route type:
Default, Host or Network
Add or Add Last

This is the IP interface to a host or network. Typically used at a spur to interface a host over the RF path. In
this scenario, the Default Gateway IP Address is 0.0.0.0 and the IP Mask (greyed out) is 0.0.0.0. Also typically
used at an end terminal in a radio link for interface with the network.
WARNING:
The default software uses first the static routes and then the dynamic routes. An open static route is
always considered as a preferential path.
If in the screen the Default Gateway IP Address check box has been selected, write in the Default Gateway IP
Address field below the relevant IP address.
By pressing Add Last or Add pushbutton it is possible to create new or change existing IP static routes

Route Type (Default, Network, Host)
Destination IP Address: allows to define the IP address necessary to reach a specific host/network
Destination Mask: allows to define the IP Mask to reach a network
Point To Point Link interface type: allows to use point to point interfaces made available by the NE.
Default Gateway IP Address: allows to define the address of the next hop gateway.

a Issue 01
1.12 Provision Networking [cont.]
Trusted SNMP Managers Configuration
Select
Trusted
Click on
SNMP Registe
Managers r, then
Tool OK
For each Trusted SNMP Manager,

fill in the following parameters:
Manager IP Address
Traps UDP Port
Type (Network Manager Layer,
Equipment Manager Layer)


a Issue 01
Blank Page


a Issue 01
2 MSS-1c Provisioning Tool


a Issue 01
2.1 Main view
MSS-1c Provisioning Tool


a Issue 01
2.2 Configuration Perspective Navigation
Configuration Perspective
Navigation Configuration Perspective is

divided in:
File Management


a Issue 01
2.3 Initial Turn-up
START
Provisioning MSS-1c
File Management
Provision Ethernet Port
Provision PDH Port
Provision Management Port
Provision TDM Cross-connection between Radio and User Ports
Provision Bridge
Provision Port VLAN
File Management


a Issue 01
2.4 File Management Tool
File Management
Select a Provisioning Mode:

Initial Configuration
Reconfiguration
Change Configuration
Select File
Management
After we have finished the
Tool MSS-1c Provisioning, click
on Create to save the
provisioning parameters in a
Provisioning File


a Issue 01
2.5 MSS-1c Configuration Tool
MSS-1c Configuration Tool is divided in:

PDH port configuration
Management port configuration
TDM cross-connection between Radio and user
ports


a Issue 01
2.6 Provision Ethernet Port
Ethernet Port Configuration Choose the type of MCT
connection to the equipment:
Optical Port (MPT-e)
Electrical Port (MPT-e, MSS-1c)
Select Ethernet Port

Configuration Tool

For each used User Port,
Enable/Disable the Port
Enable/Disable the Autonegociation
Choose the type of connection for
SFP (Disabled, Optical Port,
Electrical Port)


a Issue 01
2.6 Provision Ethernet Port [cont.]
Example :
Ethernet Port
configuration
using the 4 users ports
Only for User 2 port, we have the possibility to

choose a Network Synchronisation for 1 Gb/s
Ethernet frames in Autonegociated mode.
(Auto, SyncE IN, SyncE OUT)


a Issue 01
2.7 Provision PDH Port
PDH Port Configuration Choose the impedance for all
the E1 (75 or 120 Ohms).
Ports Configuration is read-only
that means that all E1 ports
are in unframed mode

For each used
PDH Port, fill in
the different
parameters
Select PDH
Port
Configuration
Tool

2) Enabled: with a fixed type of frame (Unframed) to enable the port
7) TDM Clock sync: type of the clock to be associated to the tributary
(Adaptive/Differential/Tdmline)
8) Node Timing: to enable for the corresponding port the Node Timing synchronization
9) Xco to Port: to cross-connect the E1 port to Radio or User port
10) MAC Address: to set the destination MAC address of the equipment in case of TDM2Eth cross-
connection
Note: Columns 5, 6, and 7 are only available if the Service Profile is TDM2Eth.
occur.

a Issue 01
2.7 Provision PDH Port [cont.]
PDH Port Setting

This Resource List Area performs all
available functions for a tributary port. The
managed tributary types are E1 streams. To
define the involved ports, the interface
selection in the Resource List Area is first
required; then make your choice in the
different fields.

In the Resource List Area there are the following fields:

Enabled: with a fixed type of E1 frame (Unframed) to enable the port
Service Profile:
The possible profiles are:
TDM2TDM
TDM2Eth
Flow Id: To implement cross-connections between line side and radio side each E1 tributary must
be associated to an identifier. Enter the Flow identifier value in the relevant field (possible
values: 2 to 4080).
Fields ECID Tx, ECID Rx and TDM Clock Sync. can be written only if the Service Profile is
TDM2Eth.
With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time
Protocol is used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP -
Real Time Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have
mixed configurations with service profiles using RTP and other service profiles not using RTP.
Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure other E1
with service profile TDM2Eth only with the Differential clock source (not with the Adaptive clock
source). If the Adaptive clock source is requested the E1 must be connected to another PDH unit.
Node Timing: to enable for the corresponding port the Node Timing synchronization.
Xco to Port: to cross-connect the E1 port to Radio port or User (User1, User2, User3, User4)
port
MAC Address: to set the destination MAC address of the equipment in case of TDM2Eth cross-
connection

a Issue 01
2.8 Provision Management Port
Management Port Configuration For each NMS Port (NMS1, NMS2):
Enable the port,
Enable/Disable the Autonegociation
Choose the Speed-Directionality

For TMN InBand:
Enable the port
Choose User Port where to send
the TMN Supervision channel
Enter a VLAN Identifier number
for the TMN supervision channel
Select
Management Port
Configuration Tool
NE MAC Address:
This field is read-only which
shows the MAC Address
of the NE. This MAC
Address must be used in
the cross-connection
with TDM2ETH profile.

TMN IN-BAND
Defines the IP address of the TMN supervision channel defined with a VLAN identifier inside a user
Ethernet traffic.

a Issue 01
2.9 Provision TDM Cross-connection between Radio and User Ports
TDM Cross-connection between Radio and User Ports Configuration
Select TDM
Cross-connection
between Radio With the empty line, fill in the different items:
and User Ports User Port (User1, User2, User3, User4)
Flow Id
Tool Service Profile
TDM Clock Source (Differential, Adaptative)
Outgoing MAC Source
(read-only field: its the local MSS-1c MAC address)
Outgoing MAC Destination

Click on Add cross-connection

The Cross-connections field contains the list for all the implemented cross-connections.
Four buttons to navigate in the Cross-Connection List

Notes:
The unicast MAC address of the NE is shown in the MSS-1c Provisioning Tool Configuration
Perspective Management Port Configuration (NE Public Mac Address or Bridge Address).
To assign the multicast MAC address of a NE start from the unicast MAC address and change a digit in
the first pair of digits in order to generate an odd binary number: example change the first pair of
the address from 00 to 01.

a Issue 01
2.10 Provision Synchronization
Select the Synchronization Role:
Slave
Master

Select the Primary and
Secondary Sources:
Free Run Local Oscillator
Any E1
Select Radio Port
Synchronization User 2 Port (SyncE IN)
Configuration Tool

How to Synchronize
Each Network Element must have a reference Clock (NEC), which will be distributed to each board of
the NE. Such clock is a 25 MHz generated in the Core-E Module.
The sources can be:
[1] Free Run Local Oscillator.
[2] Any E1 available at input traffic interfaces (the specific E1 port has to be chosen)
[3] Radio Port: Symbol Rate of the Rx signal of any available Radio direction (the specific Radio
Port has to be chosen)
[4] User 2: Network synchronization for 1 Gb/s Ethernet frames (Auto, SyncE IN, SyncE OUT)
Each Module will mute its own Synchronization clock in case of Fail Alarm.
For each available sync source, the signal Degrade Alarm is detected on each available sync source.
Such Signal Degrade alarm raises also in case of muted (missing) clock.

a Issue 01
2.11 Provision Bridge
Bridge Configuration Select the NE bridge mode:
802.1 D
802.1 Q
Select Bridge
Configuration Tool
When the NE Bridge mode is 802.1 D (default configuration), the Ethernet traffic is switched
The packets from the user Ethernet ports having the VLAN ID out the allowed range (0 and 2-
4080) are dropped. The packets having a VLAN ID already used for a TDM flow are accepted.


a Issue 01
2.11 Provision Bridge [cont.]
Bridge Configuration Select the NE bridge mode:
802.1 D
802.1 Q

VLAN Id
Select Bridge VLAN Name
Configuration Tool Select the User Port (User1, User2, User3, User4) which
transports the VLAN
Select for this User Port if it transports only Untagged frames (if
not, all Ethernet frames is sent through this User Port)
When the NE Bridge mode is 802.1 Q , the management of Ethernet traffic looking the VLAN is
enabled.
In this modality, a VLAN will be assigned to all Ethernet frames inside the MPR network.

Click on Add VLAN

N.B.: The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH)
cannot be used.
3) VLAN Ports (User 1, User 2, User 3, User 4): Select the ports members of this VLAN by putting a
check mark on the relevant check box. All the user Ethernet ports can be considered. Both enabled
and disabled user Ethernet ports (radio ports are implicitly enabled) can be member of a VLAN. This
means that a disabled port can be configured as a member of a VLAN and a port already member of
a VLAN can be disabled continuing to be a member of the same VLAN.
4) Untagged Ports : Select, among the ports belonging to this VLAN (members), the untagged ports
disabled, are manageable. The VLAN cannot be removed from the radio ports.
the ports are members and the Untag flag is set to False, which means all the frames are
transmitted with Tag.
N.B.: Tagged frames
packet is dropped.
Four buttons to navigate in the VLAN List


a Issue 01
2.12 Provision Port VLAN
Port VLAN Configuration
Select for each User Port if it
transports All Frames or if it
transports Tagged Frames Only

In case of Admit All Frames
Select the Port VLAN Id (configured
previously) to be sent with a priority
Select the Priority level for this port
VLAN Id
Select Port
Vlan
Configuration
Tool

Admit tagged only (only tagged frames are allowed in ingress)

Admit all (tagged and untagged frames are allowed in ingress)


Port VLAN ID: if the Acceptable Frame Type is set to Admit all the VLAN-ID and Priority fields,
to be added in ingress to untagged frames, must be configured. Only VLAN-ID values already
defined (in the VLAN management menu) can be configured for this purpose. The Priority values
allowed are in the range 0 - 7.
only, are dropped.
The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as
Admit tagged only, are
dropped.
The priority packets (VLAN-ID=0) received on one user Ethernet port, with the Admit
all configuration enabled, are
received packets.

a Issue 01
Exercise
Configure completely the NEs of the training center by following the

procedure given in this section.


a Issue 01
End of Module
Initial configuration MPR terminal


a Issue 01
36
Section 3
NE operation
Module 6
Performance monitoring MPR terminal
a Issue 01
9500 MPR

a Issue 01
Blank Page

NE operation Performance monitoring MPR terminal
Document History

Marcoussis

Vimerctate

a Issue 01
Module Objectives
Activate and evaluate the Performance Monitoring application for the MPR
Terminal.


a Issue 01


a Issue 01
Table of Contents
Page
1 Performance Monitoring Perspective 7
1.3 Performance Monitoring Perspective Navigation 8
1.4 Performance History File Upload 10
2 PM: Normalized 15
2.1 Normalized Tool 16
2.2 MPT Unit Performances 18
2.3 CH1 Radio Hop Configuration 20
2.3.1 Counters Thresholds 21
2.3.2 15Min/24H Counters 23
2.3.2.1 Activate/Start/Stop/Reset the Monitoring 28
2.3.2.2 Current Normalized Counters Monitoring 30
2.3.2.3 History Normalized Counters Graph 34
2.3.2.4 History Normalized Counters Details 38
3 PM: Adaptative Modulation 39
3.1 Adaptative Modulation Tool 40
3.2 15Min/24H Counters 42
3.2.1 Activate/Start/Stop/Reset the Monitoring 47
3.2.2 Current Adaptative Modulation Counters Monitoring 49
3.2.3 History Adaptative Modulation Counters Graph 53
3.2.4 History Adaptative Modulation Counters Details 56
4 PM: Ethernet 57
4.1 Ethernet Tool 58
4.2 MPT QoS Ingress Counters (for MSS-1c only) 60
4.3 QoS Counters (for MPR-e only) 63
3 6 5 4.4 Ethernet QoS Counters Monitoring All Rights Reserved Alcatel-Lucent 2011
66
9500 MPR 4.5
9500MPRTraffic Port
R 3.0 Operation Counters (for MPR-e only)
and Maintenance 76
4.5.1 Activate/Start/Stop/Reset the Monitoring 79
4.5.2 Ingress/Egress Traffic Port Counters Monitoring 81
4.5.3 Ingress/Egress Ethernet Traffic Port Counters Details 86
5 PM: Monitoring 87
5.1 Monitoring Tool 88
5.2 Alarms Tool 90

a Issue 01
Page


a Issue 01


a Issue 01
1.3 Performance Monitoring Perspective Navigation
MPR-e
MSS-1c


a Issue 01
1.3 Performance Monitoring Perspective Navigation [cont.]
Performance Monitoring Perspective is

divided in:
Performance History File Upload MSS-1c

Normalized
CH1 Radio Hop - Counters Thresholds
- 15Min Counters
- 24H Counters
Adaptative Modulation
15Min Counters
24H Counters
Ethernet
MPT QoS Ingress Counters (for MSS-1c only) MPR-e
QoS Counters (for MPR-e only)
Traffic Port Counters (for MPR-e only)
Monitoring
Alarms


a Issue 01
1.4 Performance History File Upload
This tool allows to export in a

.csv file
the data regarding the
performance counters.
This operation is done through

an FTP session.


a Issue 01
1.4 Performance History File Upload [cont.]
Performance History File Tab Panel

This field allows to configure the FTP server to be used to upload the
<Performance History File> from the NE.
2) PERFORMANCE HISTORY PARAMETERS
This field allows to select the type of counters to be exported.
3) DOWNLOAD/UPLOAD FILE FROM FTP
Through this field the Performance History Data is saved in a < Performance
History File >.


a Issue 01
This field allows to configure the FTP server to be used to upload the <
Performance History File > from the NE.

configuration.

User Id: anonymous
Password: -
Port: 21
Root Dir: /

a Issue 01
Select in the Performance Family field the type of counters to be exported:

Normalized Performance Counters
Adaptive Modulation Counters
MPT QoS Ingress Counters (for MSS-1c only)
Note: The counters to be exported must be stopped .
Performance History Parameters screen


a Issue 01
Through this field the Performance History Data is saved in a

<Performance History File>.
Download/Upload File from FTP screen


the directory and,
the <Performance History File> file name
where you want to upload the Performance History Data from the NE.
2. Then, click on the Upload History button to begin the upload process.
3. When the Performance History Data upload starts, a screen showing the in progress operation of the
upload appears. The upload is aborted if the Abort button is pressed.
4. Click Ok.

a Issue 01
2 PM: Normalized


a Issue 01
2.1 Normalized Tool
2.1 Normalized Tool


a Issue 01
2.1 Normalized Tool
2.1 Normalized Tool [cont.]
Normalized Tool
Normalized Tool is divided in:
CH1 Radio Hop

Counters Thresholds
15Min Counters
24H Counters


a Issue 01
2.2 MPT Unit Performances
The counters supported are the following:

ES - Errored Seconds
SES - Severely Errored Seconds
BBE - Background Block Error
UAS - UnAvailable Seconds

The performance monitoring (PM) gives indication on the quality of service.

Quality of service PM is performed in accordance with G.826 and G.784.
It has assumed that the quality of the single tributary (E1, ...) can be derived from the quality of the
aggregate signal, therefore no dedicated quality of service Performance Monitoring is foreseen on the
single tributaries.
Considering one section, one current register is for 15 min report and one for 24 h report; 96 history
data can be stored for 15 min report and 8 history data for 24 h report.
Two different radio sections can be monitored:
Radio Hop Section: the section between two radio stations inside the protection section.
Radio Link Section: the section identifying the protected section.
Note: The 15 min Performance Monitoring data are stored in the History Data report only if errors have
been occurred. The 24 h Performance Monitoring data are always stored in the History Data report.

a Issue 01
2.2 MPT Unit Performances [cont.]
The performance reports can be of 2 different types:

15 minutes
24 hours
The following description explains the functions to provide the
Performance Monitoring process with a granularity period of 15 min.
The same functions are provided for 24h Performance Monitoring
process.
The Performance Monitoring are of HOP or LINK type.
HOP refer to Performance Monitoring before the RPS switch.
LINK refer to Performance Monitoring after the RPS switch. The current
report can be seen (and configured) and the history log can be seen.


a Issue 01
2.3 CH1 Radio Hop
2.3 CH1 Radio Hop Configuration
For CH1 Radio Hop configuration, three

tool tab-panels are available:
1) COUNTERS THRESHOLDS TOOL

2) 15MIN COUNTERS TOOL
3) 24H COUNTERS TOOL


a Issue 01
2.3 CH1 Radio Hop
2.3.1 Counters Thresholds
There are threshold tables for the HOP and for the LINK.
There are two default threshold tables for HOP (Channel 1, Channel 0):
One for CHx Radio Hop 15 Minutes
One for CHx Radio Hop 24 Hours
There are two default threshold tables for LINK:
One for Radio Link 15 Minutes
One for Radio Link 24 Hours



a Issue 01
2.3 CH1 Radio Hop
2.3.1 Counters Thresholds [cont.]
How to create/modify a threshold table
2 3
Note:
By clicking on Defaults button, the Low and High Thresholds are filled in with
the NE defaults values

Note:
Four threshold tables can be created/modified for the HOP (Threshold CH1-15Min, CH1-24H, CH0-15Min
and CH0-24H).
Two threshold tables can be created/modified for the LINK (Threshold Link-15Min and Link-24H).
To create/modify a threshold table:

1) Click on Counters Threshold Tables HOP (or LINK) Navigator tree.
The Threshold Data screen will appear, as shown in the figure (Hop threshold).
2) Write the values for the Low and High thresholds.
3) Click on Apply. Automatically the new thresholds are applied to the NE.

a Issue 01
2.3 CH1 Radio Hop
2.3.2 15Min/24H Counters
15Min Counters
Tab Panel (1/2)


a Issue 01
2.3 CH1 Radio Hop
2.3.2 15Min/24H Counters [cont.]
15Min Counters
Tab Panel (2/2)


a Issue 01
2.3 CH1 Radio Hop
24H Counters
Tab Panel (1/2)


a Issue 01
2.3 CH1 Radio Hop
24H Counters
Tab Panel (2/2)


a Issue 01
2.3 CH1 Radio Hop
15Min/24H Counters Tab Panel
15Min/24H Counters Tab Panel is divided in two fields:

Current Normalized Counters Monitoring
History Normalized Counters Monitoring (Graph and Details)


a Issue 01
2.3 CH1 Radio Hop
2.3.2.1 Activate/Start/Stop/Reset the Monitoring
Measurements Monitoring (1/2)
1) ACTIVATE THE COUNTERS
2) START MONITORING

FOR MONITORING
4) STOP MONITORING


a Issue 01
2.3 CH1 Radio Hop
2.3.2.1 Activate/Start/Stop/Reset the Monitoring [cont.]
5) RESET THE COUNTERS

By clicking on Reset button, the
counters are reinitialized.
Note: During the monitoring, you can see

at anytime the Refresh Period Time you
selected


a Issue 01
2.3 CH1 Radio Hop
2.3.2.2 Current Normalized Counters Monitoring
Current Normalized Counters Monitoring Graphic
The Current Normalized Counters Monitoring screen shows the Normalized

Counters measurements related to the NE.
Through this screen the operator can see,
ES - Errored Seconds in yellow color
SES - Severely Errored Seconds in red color
BBE - Background Block Error in pink color
UAS - UnAvailable Seconds in blue color
In the Title of this screen, the Period Start Date is displayed

Note: The ES, SES, BBE, UAS counters values refer to the last refresh performed with the Auto Refresh.

a Issue 01
2.3 CH1 Radio Hop
2.3.2.2 Current Normalized Counters Monitoring [cont.]
On the left and right side of the Current Normalized Counters

Monitoring Graphic screen;
One Bar-graph Hour Glass (on the left) shows the remaining
time of the current measurement period (15Min or 24H) with
the corresponding values of the counters
One Tabular field Normalized Counters (on the right) shows

the current relevant values of the counters (BBE, ES, SES, UAS)

Note: The ES, SES, BBE, UAS counters values refer to the last refresh performed with the Auto Refresh.

a Issue 01
2.3 CH1 Radio Hop
The graphic shows the curves of the counters (BBE, ES, SES, UAS)
during the current measurement period (15Min or 24H);
On the left, the scale of values in seconds.
On the right, the scale of values in blocks.
In the <Alarms> field, two alarms:

TCA (Threshold Crossed Alarm) indicates that one threshold is reached
UAT (UnAvailable Time) indicates that during the time period, the
measurement was not possible (for example, if the Radio Link path is cut)
Sometimes, the measurements shows Suspect interval which shows whether the current data are
suspect or not.
collection period:
loss of the PM data in the equipment

a Issue 01
2.3 CH1 Radio Hop
Curves Management
Loop Right
Loop Left
Loop Right and Left


a Issue 01
2.3 CH1 Radio Hop
2.3.2.3 History Normalized Counters Graph
History Normalized Counters Graph

The History Normalized Counters Graph screen shows the History of
Normalized Counters measurements related to the NE.
Through this screen the operator can see by bar-graphs the history periods of
time (15Min, 24H) of:
ES - Errored Seconds in yellow color
SES - Severely Errored Seconds in red color The column in pink color indicates
BBE - Background Block Error in pink color that the measurements are not
completed during the time period
UAS - UnAvailable Seconds in blue color

The Performance Monitoring process monitors the parameters during a specified interval (15Min or 24H)
and stores their values in history data. A History Data collection is created automatically at the end of
each time interval of Current Data.
Note: Use the arrows Right and Left in the lower part to pass from one log to another log in the
history.

a Issue 01
2.3 CH1 Radio Hop
2.3.2.3 History Normalized Counters Graph [cont.]
The graphic shows the history bar-graphs of the counters (BBE, ES, SES, UAS)
during the total measurement period since the beginning of the measurements
Activation;
On the right, the scale of values in blocks.


a Issue 01
2.3 CH1 Radio Hop
Curves Management (1/2)
Loop Right
Loop Left
Loop Right and Left


a Issue 01
2.3 CH1 Radio Hop
Curves Management (2/2)
Show erroneous
periods only
Erase all periods


a Issue 01
2.3 CH1 Radio Hop
2.3.2.4 History Normalized Counters Details
History Normalized Counters Details
The History Normalized Counters Details screen shows the History of

Normalized Counters measurements related to the NE in tabular form.
The measurements during the period of time (15Min or 24H) can be
completed or not completed:
The red cross means not completed
The green tick means completed
The last two columns indicate if the alarms are raised:

TCA (Threshold Crossed Alarm) indicates that one threshold is reached
UAT (UnAvailable Time) indicates that during the time period, the
measurement was not possible (for example, if the Radio Link path is cut)

a Issue 01
3 PM: Adaptative Modulation


a Issue 01
3.1 Adaptative Modulation Tool

If the Adaptive Modulation has been enabled in the NE, in the Performance Monitoring tool will appear
also the performances regarding the Adaptive Modulation: these performances show the time during
which a specific modulation scheme has been active.

a Issue 01
3.1 Adaptative Modulation Tool [cont.]
Adaptative Modulation Tool
Adaptative Modulation Tool is divided in:
15Min Counters
24H Counters


a Issue 01
3.2 15Min/24H Counters
15Min Counters
Tab Panel (1/2)


a Issue 01
3.2 15Min/24H Counters [cont.]
15Min Counters
Tab Panel (2/2)


a Issue 01
24H Counters
Tab Panel (1/2)


a Issue 01
24H Counters
Tab Panel (2/2)


a Issue 01
15Min/24H Counters Tab Panel
15Min/24H Counters Tab Panel is divided in two fields:

Current Adaptative Modulation Counters Monitoring
History Adaptative Modulation Counters Monitoring (Graph and Details)


a Issue 01
3.2.1 Activate/Start/Stop/Reset the Monitoring
1) ACTIVATE THE COUNTERS
2) START MONITORING

FOR MONITORING
4) STOP MONITORING


a Issue 01
3.2.1 Activate/Start/Stop/Reset the Monitoring [cont.]


selected


a Issue 01
3.2.2 Current Adaptative Modulation Counters Monitoring
Current Adaptative Modulation Counters Monitoring Graphic
The Current Adaptative Modulation Counters Monitoring screen shows the

Adaptative Modulation Counters measurements related to the NE.
Through this screen the operator can see the time in seconds during which the
NE run with a specific modulation (from QPSK to 256 QAM)
In the Title of this screen, the Period Start Date is displayed

Note: The QPSK, 8 PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM counters values refer to the last
refresh performed with the Auto Refresh.
The different Adaptative Modulation counters:

QPSK - in yellow color
8 PSK - in red color
16 QAM - in pink color
32 QAM - in blue color
64 QAM - in yellow color

a Issue 01
3.2.2 Current Adaptative Modulation Counters Monitoring [cont.]
On the left and right side of the Current Adaptative Modulation

Counters Monitoring Graphic screen;
One Bar-graph Summary (on the left) shows the remaining

time of the current measurement period (15Min or 24H)
One Tabular field Adaptative Modulation Counters (on

the right) shows the current relevant values of the counters
(QPSK, 8 PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM)

Note: The QPSK, 8 PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM counters values refer to the last
refresh performed with the Auto Refresh.
The different Adaptative Modulation counters:

QPSK - in yellow color
8 PSK - in red color
64 QAM - in yellow color

a Issue 01
The graphic shows the curves of the counters (QPSK, 8 PSK, 16 QAM,
32 QAM, 64 QAM, 128 QAM, 256 QAM) during the current measurement
period (15Min or 24H);

Sometimes, the measurements shows Suspect interval which shows whether the current data are
suspect or not.
collection period:
loss of the PM data in the equipment

a Issue 01
Curves Management
Loop Left


a Issue 01
3.2.3 History Adaptative Modulation Counters Graph
History Adaptative Modulation Counters Graph
The History Adaptative Modulation Counters Graph screen shows the History of
Adaptative Modulation Counters measurements related to the NE.
Through this screen the operator can see by bar-graphs the history periods of
time (15Min, 24H) of:
QPSK - in yellow color 64 QAM - in yellow color
8 PSK - in red color 128 QAM - in pink color
16 QAM - in pink color 256 QAM - in blue color

The Performance Monitoring process monitors the parameters during a specified interval (15Min or 24H)
and stores their values in history data. A History Data collection is created automatically at the end of
each time interval of Current Data.
Note: Use the arrows Right and Left in the lower part to pass from one log to another log in the
history.

a Issue 01
3.2.3 History Adaptative Modulation Counters Graph [cont.]
The graphic shows the history bar-graphs of the counters (QPSK, 8 PSK, 16
QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM) during the total measurement
period since the beginning of the measurements Activation;


a Issue 01
3.2.3 History Adaptative Modulation Counters Graph [cont.]
Curves Management
Loop Left
Erase all periods


a Issue 01
3.2.4 History Adaptative Modulation Counters Details
History Adaptative Modulation Counters Details
The History Adaptative Modulation Counters Details screen shows the History
of Adaptative Modulation measurements related to the NE in tabular form.
The measurements during the period of time (15Min or 24H) can be completed or
not completed:
The red cross means not completed
The green tick means completed


a Issue 01
4 PM: Ethernet


a Issue 01
4 PM: Ethernet
4.1 Ethernet Tool


a Issue 01
4 PM: Ethernet
4.1 Ethernet Tool [cont.]
Ethernet Tool
Ethernet Tool is divided in:

MSS-1c
MPT QoS Ingress Counters (for MSS-1c only)
Transmitted Frames
Discarded Frames
Transmitted Bytes
Transmitted Frames
Discarded Frames
Transmitted Bytes
Number of Bytes
MPR-e
Number of Frames
Discarded Frames
Errored Frames
Unicast Frames
Multicast Frames
Broadcast Frames


a Issue 01
4 PM: Ethernet
4.2 MPT QoS Ingress Counters (for MSS-1c only)
MPT QoS Ingress Counters

Tab Panel (1/2)


a Issue 01
4 PM: Ethernet
4.2 MPT QoS Ingress Counters (for MSS-1c only) [cont.]
MPT QoS Ingress Counters

Tab Panel (2/2)


a Issue 01
4 PM: Ethernet
4.2 MPT QoS Ingress Counters (for MSS-1c only) [cont.]
Ethernet MPT QoS Ingress Counters Tab Panel
Ethernet MPT QoS Ingress Counters Tab Panel is divided in one field:
Ethernet MPT QoS Ingress Counters Monitoring


a Issue 01
4 PM: Ethernet
4.3 QoS Counters (for MPR-e only)
QoS Counters
Tab Panel (1/2)


a Issue 01
4 PM: Ethernet
4.3 QoS Counters (for MPR-e only) [cont.]
QoS Counters
Tab Panel (2/2)


a Issue 01
4 PM: Ethernet
4.3 QoS Counters (for MPR-e only) [cont.]
Ethernet QoS Counters Tab Panel
Ethernet QoS Counters Tab Panel is divided in one field:

Ethernet QoS Counters Monitoring


a Issue 01
4 PM: Ethernet
4.4 Ethernet QoS Counters Monitoring
Before to start the monitoring, choose the span of the Ethernet

Counters Measurements Graphic screen, it can be:


a Issue 01
4 PM: Ethernet
4.4 Ethernet QoS Counters Monitoring [cont.]
1) START MONITORING

FOR MONITORING
3) STOP MONITORING


a Issue 01
4 PM: Ethernet


selected


a Issue 01
4 PM: Ethernet
Ethernet QoS Counters Monitoring Tabular View
The Ethernet QoS Counters Tabular View screen shows the History of Ethernet
QoS Counters measurements related to the NE.
Through this screen the operator can see the values for Aggregate and each
queue:
Target Time Discarded Frames (Discarded TCF)
Transmitted Frames (TCF) Transmitted Bytes (TCO)
To see
more or less
details
click on + or -

The MPT unit has 8 output queues.

The Ethernet Aggregate Per Queue performances is measured in Outgoing radio side
The available performances at queue level (for each queue) are:
TCF: total number of Ethernet conforming frames accepted and transmitted out by the specific
queue of the interface.
Discard TCF: total number of Discarded Ethernet conforming frames accepted by the specific queue
of the interface.
TCO: total number of Ethernet conforming octets (bytes) accepted and transmitted out by the
specific queue of the interface.
The different Ethernet QoS counters:

TCF - in light blue color
Discard TCF - in red color
TCO - in dark blue color
Note: The different counters values refer to the last refresh performed with the Auto Refresh.

a Issue 01
4 PM: Ethernet
Ethernet QoS Counters Monitoring Graphical View (1/4)
The Ethernet QoS Counters Monitoring screen shows the Ethernet QoS Counters
measurements related to the NE.
Through this screen the operator can see the transmitted TCF frames, discarded
TCF frames and transmitted TCO bytes on each queue and aggregate frame


of the interface.


a Issue 01
4 PM: Ethernet
Six tab-panels (Aggregate, Queue1, Queue2, Queue3, Queue4, Queue5)

presents the Ethernet QoS measurements in the same graphical display.
Five bar-graphs for the 5 queues shows the relevant values

of the Ethernet QoS counters (transmitted TCF frames,
discarded TCF frames and transmitted TCO bytes).


of the interface.


a Issue 01
4 PM: Ethernet
Six tab-panels (Aggregate, Queue1, Queue2, Queue3, Queue4, Queue5)

presents the Ethernet QoS measurements in the same graphical display.


a Issue 01
4 PM: Ethernet
The graphical view shows the curves of the counters (transmitted TCF
frames, discarded TCF frames and transmitted TCO bytes);
On the left, the scale of values in frames.
On the right, the scale of values in bytes.


a Issue 01
4 PM: Ethernet
Ethernet QoS Counters Curves Management

Go to the first Measurement point
Go to the last Measurement point
Move the curve towards the left
Move the curve towards the right
Zoom In
Zoom Out
Erase all curves !
Scroll lock
It is the same as Power/Modem Measurements Curves Management


a Issue 01
4 PM: Ethernet
By clicking on Export data to a .csv file, you save the Ethernet QoS
Counters Measurements in a .csv file.
It is the same as Export Power Measurements Data


a Issue 01
4 PM: Ethernet
4.5 Traffic Port Counters (for MPR-e only)
Traffic Port Counters Tab Panel (1/2)


a Issue 01
4 PM: Ethernet
4.5 Traffic Port Counters (for MPR-e only) [cont.]
Traffic Port Counters Tab Panel (2/2)


a Issue 01
4 PM: Ethernet
4.5 Traffic Port Counters (for MPR-e only) [cont.]
Ethernet Traffic Port Counters Tab Panel
Ethernet Traffic Port Counters Tab Panel is divided in one field:

Ethernet Ingress Traffic Port Counters Monitoring
Ethernet Egress Traffic Port Counters Monitoring
Ingress/Egress Ethernet Traffic Port Counters Details


a Issue 01
4 PM: Ethernet
4.5.1 Activate/Start/Stop/Reset the Monitoring
1) START MONITORING

FOR MONITORING
3) STOP MONITORING


a Issue 01
4 PM: Ethernet
4.5.1 Activate/Start/Stop/Reset the Monitoring [cont.]


selected


a Issue 01
4 PM: Ethernet
4.5.2 Ingress/Egress Traffic Port Counters Monitoring
Ethernet Ingress/Egress Traffic Port Graphic
The Ethernet Ingress/Egress Traffic Port Graphic screen shows the values of
the different traffic counters measurements related to the NE.
The current traffic port ethernet counters: number of bytes TTO/TRCO (green
color), number of frames TTF/TRCF (green color), discarded TDF frames
(yellow color) and errored TRSEF frames (red color)
The Frames destination: TRCF Unicast, TRCF Multicast and TRCF Broadcast
frames in different blue color

The available performances at port level are:

TTO: total number of octets (bytes) of Ethernet frames transmitted out (Egress) by the Interface, including
TRCO: total number of octets (bytes) of Ethernet frames received (Ingress) by the Virtual Ethernet Interface,
including Ethernet header characters.
TTF: total number of Ethernet frames transmitted out (Egress) by the interface.
TRCF: total number of Ethernet frames received (Ingress) by the Virtual Ethernet Interface.
TDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer congestion.
TRCF Unicast: total number of Ethernet Unicast frames transmitted out (Egress) or received correctly (Ingress)
by the Virtual Ethernet Interface.
TRCF Multicast: total number of good packets transmitted by this address (Egress) or received (Ingress) that
were directed to a multicast address. This number does not include packets directed to the broadcast address.
TRCF Broadcast: total number of good packets transmitted by this address (Egress) or received (Ingress) that
were directed to the broadcast address. This number does not include multicast packets.
The different Ingress/Egress Traffic Port counters:

TCO/TRCO - in green color
TTF/TRCF - in green color
TDF - in yellow color
TRSEF - in red color
TRCF Unicast - in blue color
TRCF Multicast - in blue color
TRCF Broadcast - in blue color

a Issue 01
4 PM: Ethernet
4.5.2 Ingress/Egress Traffic Port Counters Monitoring [cont.]
On the left side of the Ethernet Ingress/Egress Traffic Port

Two Bar-graph Summary shows:

On the left, the distribution of the various counters of the
Current Traffic Port Ethernet Counters field
On the right, the distribution of the various counters of the
Frames Destination field




a Issue 01
4 PM: Ethernet
On the right side of the Ethernet Ingress/Egress Traffic Port

Two Tabular field:

Current Traffic Port Ethernet Counters shows the current
relevant values of the counters (number of bytes, number of
frames, discarded frames, errored frames)
Frames Destination shows the current relevant values of the
counters (Unicast frames, Multicast frames, Broadcast frames )




a Issue 01
4 PM: Ethernet
The graphic shows the curves of the counters (BBE, ES, SES, UAS);
On the left, the scale of values in frames.
On the right, the scale of values in bytes.


a Issue 01
4 PM: Ethernet
Curves Management
Loop Right
Loop Left
Loop Right and Left


a Issue 01
4 PM: Ethernet
4.5.3 Ingress/Egress Ethernet Traffic Port Counters Details
Ingress/Egress Ethernet Traffic Port Counters Details

The Ingress/Egress Ethernet Traffic Port Counters Details screen shows the
History of Ingress/Egress Ethernet Traffic Port measurements related to the NE.
Through this screen the operator can see the values:
Target Time Errored Frames
Number Of Bytes Unicast Frames
Number Of Frames Multicast Frames
Discarded Frames Broadcast Frames


a Issue 01
5 PM: Monitoring


a Issue 01
5 PM: Monitoring
5.1 Monitoring Tool


a Issue 01
5 PM: Monitoring
5.1 Monitoring Tool [cont.]
Monitoring Tool
Monitoring Tool is divided in:
Alarms


a Issue 01
5 PM: Monitoring
5.2 Alarms Tool


a Issue 01
Exercise
Using the test link described in the following slide,

do the following steps:
1. Enable Performance Monitoring on the NE A and B to

monitor the quality of the path connecting the two
Test Instruments
2. Using the variable attenuator, simulate a link degradation and display the
current and the historical collected data


a Issue 01
Exercise
VARIABLE
ATTENUATOR
Test Test
Instr. A B Instr.
Operator 1 Operator 2


a Issue 01
Blank Page


a Issue 01
End of Module
Performance monitoring MPR terminal


a Issue 01
41
Section 4
Maintenance
Module 1
Fault management
3JK Issue 1.00
9500 MPR

3JK Issue 1.00
Blank Page

Maintenance Fault management
Document History

Marcoussis

Vimercate

3JK Issue 1.00
Module Objectives
Perform the troubleshooting of the 9500 MPR.


3JK Issue 1.00


3JK Issue 1.00
Table of Contents
Page
1 Fault Management 7
1.1 Troubleshooting 8
1.1.1 Before Going to Site Checklist 9
1.1.2 Troubleshooting Basics 11
1.1.3 Troubleshooting Path Problems 52
1.1.3.1 Path Problems on a Commissioned Link 53
1.1.3.2 Path Problems on a New Link 55
1.1.4 Troubleshooting Configuration Problems 56
1.1.5 Troubleshooting Ethernet Problems 58
1.1.6 Troubleshooting TMN Problems 60
1.1.7 Troubleshooting MSS-1c Electrical or Optical Connection 64
2 Failed Equipment Removal and Replacement 65
2.1 MSS-8/MSS-4 Card Removal and Replacement 66
2.2 Core-E Card Removal and Replacement 69
2.3 Flash Card Replacement Procedure 70
2.4 ODU Removal and Replacement 72
2.5 MSS-1c Removal and Replacement 73
2.6 MPT-HC Removal and Replacement 74
2.7 MPT-MC Removal and Replacement 75
End of Module 76


3JK Issue 1.00
Page


3JK Issue 1.00
1 Fault Management


3JK Issue 1.00
1 Fault Management
1.1 Troubleshooting
This section provides guidance on:

Before Going to Site Checklist
Troubleshooting Basics
Troubleshooting Path Problems
Troubleshooting Configuration Problems
Troubleshooting Ethernet Problems
Troubleshooting TMN Problems


3JK Issue 1.00
1.1 Troubleshooting
1.1.1 Before Going to Site Checklist
Where possible, before going to site obtain the following information:

Does the fault require immediate attention?
Determine who is the best-placed person to attend the fault.
Confirm the nature and severity of the reported fault, its location, 9500 MPR
type, frequency band, high/low end ODU, capacity, modulation and
configuration (non protected, protected, diversity). Ask:
Is just one 9500 MPR link affected, or a number of links in the same geographical
area?
Is the path down completely or is traffic passing but with a BER alarm?
Is only one or a number of tributaries affected?
Could the fault be in the equipment connected to 9500 MPR, rather than in 9500
MPR? Are there alarms on other, connected equipment?
Is it a hard or intermittent fault?
Do alarms confirm which end of an alarmed link is faulty?
Could the weather (rain, ice, high wind, temperature) be a factor in the
reported fault?

Note: If the fault suggests a rain fade or other weather related fade condition and it matches the
prevailing weather conditions, do not take any action until the weather abates.

3JK Issue 1.00
1.1 Troubleshooting
1.1.1 Before Going to Site Checklist [cont.]
Does link history suggest any fault trends?

Does the fault history for the link indicate a likely cause?
Is the 9500 MPR link newly installed?
Has there been any recent work done on the link?
Ensure that you have with you:
Appropriate spares. Where an equipment failure is suspected, these should include
replacement cards/plug-ins and ODU. If an ODU is suspected then local/national
climbing safety requirements must be adhered to.
A laptop PC loaded with Craft Terminal, and an Ethernet connection cable. (You
need the 9500 MPR IP address and also the addresses for any remote sites to be
accessed).
If login security has been enabled, you need the 'engineer' password for the local and
also any remote sites to be accessed.
Any special test equipment that may be needed, such as a BER tester.
Toolkit.
Key(s) for access to the site.


3JK Issue 1.00
1.1 Troubleshooting
1.1.2 Troubleshooting Basics
Check front-panel LED indications. These provide summary alarm

indications, which can help narrow down the location and type of
failure.
Where a Status LED on a plug-in is off (unlit), but power to the MSS is
confirmed by LEDs on other plug-ins, check the seating of the affected plug-
in.
Check Main Screen. When logging into 9500 MPR with Craft Terminal,
the opening screen is the Main Screen. Use the information provided to
check for severity and problem type. Refer to table Alarm Matrix for
probable cause and recommended action.

This section provides general guidance on 9500 MPR troubleshooting.

3JK Issue 1.00
1.1 Troubleshooting
1.1.2 Troubleshooting Basics [cont.]
Table Alarm Matrix

Configuration/ Most Probable Cause Action
Alarm Alarm
Equipment
Description
1+0 1+1 EPS
Core-E Card Card Fail Major Minor Core-E card failed Replace Core-E Card
Equipment N/A Minor Card in slot does not match card Install correct configured card
Mismatch configured in Core-E memory
Card Missing N/A Minor Core-E card is missing from slot Install Core-E Card in slot
SFP missing Major Minor The SFP optional plug-in is Install the plug-in in the SFP
alarm provisioned, but not present slot
Unconfigured N/A Minor Card in slot is not provisioned Provision card
Equipment (enabled)
LOS on ETH TMN Minor Minor No Ethernet input signal detected Check link partner and cable
Interface on ETH 4 on Core-E Card between link partner and ETH 4
connector
PPP IP Fail Minor Minor - -
LOS on Gigabit Major Minor Loss of Ethernet is detected on ETH Check link partner and cable
ETH Interface 1-4 on Core-E Card between link partner and ETH
1-4 connector
continue


3JK Issue 1.00
1.1 Troubleshooting

Equipment Alarm Description Alarm
1+0 1+1 EPS
Core-E Card Firmware Download Minor Minor Status of download Wait for downloading to
In Progress complete
LOS on Sync Minor Minor No sync clk detected at Sync in port Check sync source and
Interface on Core-E Card cable between sync source
and Sync in port
Degraded Signal on Minor Minor Sync clk errors detected at Sync in Check sync source for
Sync Interface port on Core-E Card errors
License Mismatch for Major Major Wrong flash card installed on Core-E Install correct flash card
Equipment Card for license
Provisioned
Underlying Resource Major Major On detection of card failure the E1 Replace Core-E card
Unavailable (URU) port, Ethernet port, Radio port
objects emit a communication
Alarm notification showing the
transmission resources are affected
by the equipment failure
continue


3JK Issue 1.00
1.1 Troubleshooting

1+0 1+1 EPS
E1 Access Card Fail Major Minor Failure of E1 Access Card Replace E1 Access Card
Card
Equipment Mismatch Major Minor Card in slot does not match Card Install correct configured card
configured in Core-E memory
Card Missing Major Minor E1 Access Card is missing from Install E1 Access Card in slot
slot
Unconfigured Major Major Card is not Enabled on the Enable card
Equipment Settings screen
LOS on PDH Major Minor No E1 input signal detected on Check E1 source and/or cable
Tributary any one or more of 32 lines
Degraded Signal Minor Minor Low quality sync signal for E1 Replace E1 Access Card
Access Card
AIS on PDH Tributary Major Major AIS detected by the receive Check for upstream E1 source
(RX) circuits on one or more E1 lines, for errors
indicating upstream failure
continue


3JK Issue 1.00
1.1 Troubleshooting

1+0 1+1 EPS
E1 Access AIS on PDH Tributary Major Major AIS detected on one or more E1 Check E1 source
Card (TX) lines at input to PDH 32xE1
Access Card
Loss of CESoETH Major Major Packets are not being received by 1. Check/troubleshoot far
Frame the emulation circuits end alarms
2. Replace alarmed E1
Access Card
Firmware Download Minor Minor Status of download Wait for downloading to
Underlying Resource On detection of card failure the Replace E1 Access card
Unavailable (URU) E1 port objects emit a
communication Alarm
notification showing the
transmission resources are
affected by the equipment failure
continue


3JK Issue 1.00
1.1 Troubleshooting

1+0 1+1 EPS
16E1DS1 Card Fail Major - Failure of ASAP Card Replace ASAP Card
ASAP Card
Equipment Mismatch Major - Card in slot does not match Card Install correct configured card
configured in Core-E memory
Card Missing Major - ASAP Card is missing from slot Install ASAP Card in slot
Unconfigured Major - Card is not Enabled on the Enable card
Firmware Download Minor - Status of download Wait for downloading to
Loss Of Signal (LOS) Major - Loss of signal on each incoming Check E1 source and/or cable
E1 signal (detected according to
ITU-T G.775-sect.4)
Tx Alarm Indication Major - Alarm Indication Signal detected Check E1 source
Signal (Tx AIS) on each incoming E1 signal (Tx
side) (detected according to ITU-
T G.775-sect.4)
Loss Of Frame (LOF) Major - Loss of frame on each incoming Check to CRC4 multiframe
E1 signal (detected according to alignment of the Far End
ITU-T G.706-sect.4) equipment
continue


3JK Issue 1.00
1.1 Troubleshooting

1+0 1+1 EPS
16E1DS1 Loss of Cell Major - Loss of ATM cell delineation on Check the ATM scrambling of
ASAP Card Delineation (LCD) each incoming E1 signal, when the Far End equipment
the E1 port is used as physical
layer for ATM (detected
according to ITU-T I.432)
Loss of IMA Frame Major - Loss of IMA Frame on each Check the IMA configuration
(LIF) incoming E1 signal, when the E1 of the Far End equipment
port is used as IMA link (detected
according to IMA Standard AF-
PHY-0086.000)
Link Out of Delay Major - It reports the event that, when Check the synchronization of
Synchronisation the E1 port is used as IMA link, it the Far End equipment
(LODS) is not synchronized with the
other links within the IMA group
(detected according to IMA
Standard AF-PHY-0086.000)
continue


3JK Issue 1.00
1.1 Troubleshooting

1+0 1+1 EPS
16E1DS1 RDI/Link Failure Major - It reports, when the E1 port is Check the Far End equipment
ASAP Card used as IMA link, the OR of other
alarms that are foreseen by IMA
Standard AF-PHY-0086.000:
- RFI-IMA
- Tx-Mis-Connected
- Rx-Mis-Connected
- Tx-Unusable-FE
- Link Rx-Unusable-FE
continue


3JK Issue 1.00
1.1 Troubleshooting

1+0 1+1 EPS
16E1DS1 IMA Group Trail Major - It reports, for a configured IMA Check the Far End equipment
ASAP Card Signal Fail (TSF) Group, the event that its Group
Traffic State Machine is 'down',
that is NE and FE Group State
Machine are both NOT in
"operational" state (IMA Standard
AF-PHY-0086.000)
IMA Group TSFAlarm is also
generated by OR of the following
alarms (IMA Standard AF-PHY-
0086.000):
- Tx-Unusable-FE
- Link Rx-Unusable-FE
- Group Start-up-FE
- Group Config-Aborted
- Group Config-Aborted-FE
- Group Insufficient-Links
- Group Insufficient-Links-FE
- Group Blocked-FE
- Group GR-Timing-Mismatch
continue


3JK Issue 1.00
1.1 Troubleshooting

1+0 1+1 EPS
16E1DS1 Underlying Resource Major Major On detection of card failure the Replace 16E1DS1 ASAP
ASAP Card Unavailable (URU) E1 port objects emit a
communication Alarm
affected by the equipment failure
Fans Unit Card Fail Major Fan failed Replace fan unit
Card Missing Major Fan unit is missing from slot Install fan unit
Unconfigured Minor Minor Unit is not Enabled on the Enable fan unit


3JK Issue 1.00
1.1 Troubleshooting
Modem Card and ODU300 Alarm Matrix
Alarm Configuration/Alarm
Equipment Most Probable Cause Action
Description 1+0 1+1 HS 1+1 FD
Modem Card Fail Major Minor Minor Modem Card failed Replace Modem Card
Card
Equipment Minor Minor Minor Card in slot does not Install correct
Mismatch match card configured in configured card
Core-E memory
Card Missing Major Minor Minor Modem Card is missing Install Modem Card in
from slot slot
Unconfigured Minor Minor Minor Card is not Enabled on Enable card
Equipment the Settings screen
PNU Cable Loss Major Minor Minor Bad cable connection at Check/repair IF cable
IF in/out connector on connection on alarmed
Modem Card Modem Card
continue


3JK Issue 1.00
1.1 Troubleshooting
Modem Loss of Radio Minor Minor Minor Far-end equipment 1.Switch far-end XMTRs
Card Frame problems, RF path (in a protected
problems, or local system). If alarm
circuit failures have clears, replace far-end
caused BER to increase off-line Modem Card.
to the point that frames 2.Check/troubleshoot
are being lost far-end alarms
3.Replace alarmed
Modem card
Loss of N/A Minor Minor Delay between main and 1.Replace main Modem
Alignment protect RF paths Card
detected 2.Replace protect
Modem Card
3.Replace main ODU
4.Replace protect ODU
continue


3JK Issue 1.00
1.1 Troubleshooting
Configuration/Alarm
Alarm
Equipment 1+0 1+1 1+1 FD Most Probable Cause Action
Description
HS
Modem Demod Major Minor Minor Internal receive circuit Replace Modem Card
Card Function Fail failure
High BER Major Minor Minor Bit Error Rate threshold 1. Verify RF path is
(10E-4) exceeded on clear, antenna is
Receiver input circuits aligned, and no
on modem existing weather -
related problems
2. Verify RSL is above
RCV threshold. If not
check upstream
transmitter
output/troubleshoot
transmitter
Early Warning N/A Minor Minor 10E-9 BER detected No action is required at
this time. Monitor
receive signal for
increased degrading
continue


3JK Issue 1.00
1.1 Troubleshooting
Configuration/Alarm
Alarm
Description
HS
Modem Link Identifier Major Major Major Link identifier number Set numbers at both
Card Mismatch provisioned on Modem ends of hop to match
Card settings screen is
different from link
identifier number
provisioned at other end
of hop
TCA on Radio N/A N/A Major Alarm threshold Switch far-end XMTRs
Link exceeded on standby (in a protected
Modem Card system). If alarm
clears, replace far-end
off-line Modem Card
TCA on Radio Major N/A Minor Alarm threshold
Hop exceeded on standby
Modem Card after
switching from main to
standby
continue

TCA Threshold Crossing Alarm

3JK Issue 1.00
1.1 Troubleshooting
Configuration/Alarm
Alarm
Description
HS
Modem UAT on Radio N/A N/A Major 10 consecutive SES Switch farend XMTRs
Card Link (unavailable time period) (in a protected
detected on main Modem system). If alarm
Card clears, replace farend
off-line Modem Card
UAT on Radio Major N/A Minor 10 consecutive SES
Hop (unavailable time period)
detected on standby
Modem Card after
switching from admin to
standby
Firmware Minor Minor Minor Download status Wait for downloading
Download In to complete
Progress
Degraded Minor Minor Minor Low quality sync signal Replace Modem Card
Signal from Modem Card
continue

UAT Un-Available Time

3JK Issue 1.00
1.1 Troubleshooting
Configuration/Alarm
Alarm
Description
HS
Modem License Major Major Major Modem card type does not Replace Modem Card
Card Mismatch for match card type stored in with correct card
Equipment memory on the Core-E type
Provisioned Card flash card
Underlying Major Major Major On detection of card Replace Modem Card

Resource failure the Radio port
Unavailable objects emit a
(URU) communication Alarm
affected by the
equipment failure
continue


3JK Issue 1.00
1.1 Troubleshooting
Configuration/Alarm
Alarm
Description
HS
ODU300 Card Fail Major Minor Minor ODU failed Replace ODU
Equipment Major Minor Minor ODU does not match Replace ODU
Mismatch ODU configured in Core-
E memory
RCV Function Major Minor Minor ODU receiver circuit Replace ODU
Fail failed
RF Frequency Major Minor Minor Frequency out-of-range Re-configure frequency
Mismatch of configured TX
frequency
Shifter Major Minor Minor Configured shifter value Re-configure shifter
Frequency not supported by ODU value
Mismatch
TX Power Minor Minor Minor Configured TX power Re-configure TX power
Mismatch value not supported by value
ODU
continue


3JK Issue 1.00
1.1 Troubleshooting
Configuration/Alarm
Alarm
Description
HS
ODU300 Software Minor Minor Minor Software version on ODU Download correct
Mismatch does not match software software version
version on Core
ODU Not Minor Minor Minor Loss of communication 1.Replace ODU
Responding with ODU 2.Replace alarmed
Modem Card
Firmware Minor Minor Minor Download status Wait for downloading
Progress


3JK Issue 1.00
1.1 Troubleshooting
MPT Access Peripheral Card and MPT-HC Alarm Matrix
MPT Access Card Fail Major - - MPT Access Card failed Replace MPT Access
Card Card
Equipment Major - - Card in slot does not Install correct
Mismatch match card configured in configured card
Core-E memory
Card Missing Major - - MPT Access Card is Install MPT Access
missing from slot Card in slot
Unconfigured Minor - - Card is not Enabled on Enable card
Equipment the Settings screen
MPT Power Major - - Power Supply Failure Check/repair the cable
Supply Failure connection. If ok,
replace MPT-HC
continue


3JK Issue 1.00
1.1 Troubleshooting
MPT Access Loss Of Major - - Loss of the incoming Check the cable
Card Ethernet Signal Ethernet signal (the connection. If ok,
signal is missing) or a replace the MPT
communication problem Accerss unit
with the remote peer
(i.e. the communication
has not been established
for physical problem on
cable or interface -> link
down)
Ethernet Link Minor - - Partial failure of Check the cable
Error electrical or optical connection. If ok,
cable for the GbEth port replace the MPT
Accerss unit
continue


3JK Issue 1.00
1.1 Troubleshooting
MPT Access Degraded Signal Minor - - This alarm is active only Check the cable
Card of the MPT when the interface is
Ethernet selected as Primary or
Interface Secondary
synchronization source
Firmware Minor - - Download status Wait for downloading
Progress
MPT-HC Card Fail Major Minor Minor MPT-HC failed Replace MPT-HC
Equipment Major Minor Minor MPT-HC does not match Replace MPT-HC
Mismatch MPT-HC configured in
Core-E memory
RCV Function Major Minor Minor MPT-HC receiver circuit Replace MPT-HC
Fail failed
continue

RCV Receiver

3JK Issue 1.00
1.1 Troubleshooting
MPT-HC/ RF Frequency Major Minor Minor Frequency out-of-range of Re-configure
MPT-HC V2 Mismatch configured Tx frequency frequency
Shifter Major Minor Minor Configured shifter value Re-configure shifter
Frequency not supported by MPT-HC value
Mismatch
TX Power Minor Minor Minor Configured TX power value Re-configure TX
Mismatch not supported by MPT-HC power value
Modulation Major Minor Minor The modulation Change the
parameters parameters already modulation
Mismatch configured and stored in parameters
the MPR DB are not
actually supported by MPT
Software Minor Minor Minor Software version on MPT- Download correct

Mismatch HC does not match software version
software version on Core
continue


3JK Issue 1.00
1.1 Troubleshooting
MPT-HC/ MPT-HC Not Minor Minor Minor Loss of 1. Replace MPT-HC
MPT-HC V2 Responding communication with 2. Replace alarmed MPT
MPT-HC Access Card
Firmware Minor Minor Minor Download status Wait for downloading to
Download In complete
Progress
Loss of Radio Major Minor Minor Far end problems, RF 1. Switch far end
Frame path problems, or equipment (in a protected
local circuit failures system). If alarm clears,
have caused BER to replace far end off-line
increase to the point MPT-HC.
that frames are being 2. Check/troubleshoot
lost far end alarms
3. Replace alarmed MPT-
HC
continue


3JK Issue 1.00
1.1 Troubleshooting
MPT-HC/ Loss of N/A Minor Minor Delay between main and 1. Replace main MPT-
MPT-HC V2 Alignment protect RF paths MS
detected 2. Replace protect
MPT-MS
Demod Major Minor Minor Internal receive circuit Replace MPT-HC
Function Fail failure
High BER Major Minor Minor Bit Error Rate threshold 1. Verify RF path is
(10E-4) exceeded clear, antenna is
aligned, and no existing
weather-related
problems
RCV threshold. If not
check upstream
transmitter
output/troubleshoot
transmitter
continue


3JK Issue 1.00
1.1 Troubleshooting
MPT-HC/ Early Warning N/A Minor Minor 10E-9 BER detected No action is required at
MPT-HC V2 this time. Monitor
receive signal for
increased degrading
Link Identifier Major Major Major Link identifier number Set numbers at both
Mismatch provisioned is different ends of hop to match
from link identifier
number provisioned at
other end of hop
MPT Loop Minor Minor Minor Communication problem Check the radio hop
Communication between the local MPT
alarm and the remote MPT for
all the functionalities
requiring a
communication loop
(ATPC, ACM, Pre-
distorsion)
continue


3JK Issue 1.00
1.1 Troubleshooting
MPT-HC/ Sync Degraded Minor Minor Minor This alarm can raise if Check the radio hop
MPT-HC V2 signal the addressed Radio
interface has been
configured as
primary/secondary
synchronization source.
It is active if the
frequency of the clock
recovered from radio Rx
signal is mistuned
continue


3JK Issue 1.00
1.1 Troubleshooting
MPT-HC/ Coupling port N/A Minor Minor For the MPT Coupling Check the cable
MPT-HC V2 Loss of optical port:
Ethernet Signal - the loss of incoming
Ethernet signal (the
signal is missing);
- a communication
problem with the
alternate MPT (i.e. the
communication has not
been established for
physical problem on
cable or interface -> link
down).
When this alarm is
raised, RPS is not
working
continue


3JK Issue 1.00
1.1 Troubleshooting
MPT-HC/ Coupling port N/A Minor Minor For the MPT Coupling Check the cable
MPT-HC V2 Link Error optical port, the ratio
between the number of
received errored packets
and the total number of
received packets is
above a given threshold.
When this alarm is
raised, RPS is not
working
Traffic port Minor Minor Minor For the MPT Traffic Check the cable
Link Error optical port, the ratio
between the number of
received errored packets
and the total number of
received packets is
above a given threshold
continue


3JK Issue 1.00
1.1 Troubleshooting
MPT-HC/ MPT Tx Clock Minor Minor Minor The MPT is not able to Check the radio hop
MPT-HC V2 Failure lock the air Tx symbol
rate to the NE Clock
TCA on Radio N/A N/A Major Alarm threshold Switch far end
Link exceeded on standby equipment (in a
MPT-HC protected system). If
alarm clears, replace
far end off-line MPT-HC
TCA on Radio Major N/A Minor Alarm threshold
Hop exceeded on standby
MPT-HC after switching
from main to standby
continue


3JK Issue 1.00
1.1 Troubleshooting
MPT-HC/ UAT on Radio N/A N/A Major 10 consecutive SES Switch far end
MPT-HC V2 Link (unavailable time equipment (in a
period) detected on protected system). If
main MPT-HC alarm clears, replace
far end off-line MPT-HC
UAT on Radio Major N/A Minor 10 consecutive SES
Hop (unavailable time
period) detected on
standby MPT-HC after
switching from admin to
standby
Degraded Signal Minor Minor Minor Low quality sync signal Replace MPT-HC
from MPT-HC
PPP IP Fail Minor Minor Minor Point to point IP failure Check the settings


3JK Issue 1.00
1.1 Troubleshooting
MPT Access Peripheral Card and MPT-MC Alarm Matrix

Alarm Alarm
Equipment
Description
1+0 1+1 HS
MPT-MC Card Fail Major Minor MPT-MC failed Replace MPT-MC
Equipment Major Minor MPT-MC does not match Replace MPT-MC
Mismatch MPT-MC configured in Core-E
memory
RCV Function Fail Major Minor MPT-MC receiver circuit Replace MPT-MC
failed
RF Frequency Major Minor Frequency out-of-range of Re-configure frequency
Mismatch configured Tx frequency
Shifter Frequency Major Minor Configured shifter value not Re-configure shifter value
Mismatch supported by MPT-MC
TX Power Minor Minor Configured TX power value Re-configure TX power
Mismatch not supported by MPT-MC value
continue

RCV Receiver

3JK Issue 1.00
1.1 Troubleshooting

Alarm Alarm
Equipment
Description
1+0 1+1 HS
MPT-MC Modulation Major Minor The modulation parameters Change the modulation
parameters already configured and parameters
Mismatch stored in the MPR DB are not
actually supported by MPT
Software Minor Minor Software version on MPT-MC Download correct
Mismatch does not match software software version
version on Core
MPT-HC Not Minor Minor Loss of communication with 1. Replace MPT-MC
Responding MPT-MC 2. Replace alarmed MPT
Access Card
Firmware Minor Minor Download status Wait for downloading to
Download In complete
Progress
continue


3JK Issue 1.00
1.1 Troubleshooting

Alarm Alarm
Equipment
Description
1+0 1+1 HS
MPT-MC Loss of Radio Major Minor Far end problems, RF path 1. Switch far end
Frame problems, or local circuit equipment (in a
failures have caused BER to protected system).
increase to the point that
frames are being lost If alarm clears,
replace far end off-
line MPT-MC.
2. Check/troubleshoot
far end alarms
3. Replace alarmed
MPT-MC
Demod Function Major Minor Internal receive circuit Replace MPT-MC
Fail failure
continue


3JK Issue 1.00
1.1 Troubleshooting

Alarm Alarm
Equipment
Description
1+0 1+1 HS
MPT-MC High BER Major Minor Bit Error Rate threshold 1. Verify RF path is
(10E-4) exceeded clear, antenna is
aligned, and no
existing weather-
related problems
RCV threshold.
If not check
upstream transmitter
output/troubleshoot
transmitter
Early Warning N/A Minor 10E-9 BER detected No action is required at
this time. Monitor receive
signal for increased
degrading
continue


3JK Issue 1.00
1.1 Troubleshooting

Alarm Alarm
Equipment
Description
1+0 1+1 HS
MPT-MC Link Identifier Major Major Link identifier number Set numbers at both
Mismatch provisioned is different from link ends of hop to match
identifier number provisioned at
other end of hop
MPT Loop Minor Minor Communication problem between Check the radio hop
Communication the local MPT and the remote
alarm MPT for all the functionalities
requiring a communication loop
(ATPC, ACM, Pre-distorsion)
Sync Degraded Minor Minor This alarm can raise if the Check the radio hop
signal addressed Radio interface has
been configured as
primary/secondary
synchronization source. It is
active if the frequency of the
clock recovered from radio Rx
signal is mistuned
continue


3JK Issue 1.00
1.1 Troubleshooting

Alarm Alarm
Equipment
Description
1+0 1+1 HS
MPT-MC MPT Tx Clock Minor Minor The MPT is not able to lock Check the radio hop
Failure the air Tx symbol rate to the
NE Clock
TCA on Radio Link N/A N/A Alarm threshold exceeded Switch far end equipment
on standby MPT-MC (in a protected system). If
alarm clears, replace far
end off-line MPT-MC
TCA on Radio Hop Major N/A Alarm threshold exceeded
on standby MPT-MC after
switching from main to
standby
UAT on Radio N/A N/A 10 consecutive SES Switch far end equipment
Link (unavailable time period) (in a protected system). If
detected on main MPT-MC alarm clears, replace far
end off-line MPT-MC
continue



3JK Issue 1.00
1.1 Troubleshooting

Alarm Alarm
Equipment
Description
1+0 1+1 HS
MPT-MC UAT on Radio Hop Major N/A 10 consecutive SES
(unavailable time period)
detected on standby MPT-MC
after switching from admin
to standby
Degraded Signal Minor Minor Low quality sync signal from Replace MPT-MC
MPT-MC
PPP IP Fail Minor Minor Point to point IP failure Check the settings
continue

3JK Issue 1.00
1.1 Troubleshooting
Equipment Alarm Configuration Most Probable Cause Action

Description 1+0 Alarm
MSS-1c Card Fail Major MSS-1c card fail Replace the MSS-1c
SFP missing alarm Major The SFP optional plug-in is Install the plug-in in the
provisioned, but not present SFP slot
SFP Tx fault (for Major Failure in the optical Replace the SFP
optical only) transmitter
LOS on Gigabit Major Loss of Ethernet is detected Check link partner and
ETH Interface cable between link
partner and ETH
connector
MSS-1c LOS on PDH Major No E1 input signal detected Check E1 source and/or
(E1 section) Tributary on any one cable
CRC4 Minor Low quality sync signal for Check the E1 line
E1 Access Card
continue

3JK Issue 1.00
1.1 Troubleshooting
Equipment Alarm Configuration Most Probable Cause Action

Description 1+0 Alarm
MSS-1c AIS on PDH Major AIS detected by the receive Check for upstream E1
(E1 section) Tributary (RX) circuits on one or more E1 source for errors
lines, indicating upstream
failure
suite
AIS on PDH Major AIS detected on one or more Check E1 source
Tributary (TX) E1 lines at input to PDH 32
Loss of CESoETH Major Packets are not being Check/Troubleshoot far

Frame received by the emulation end alarms
circuits
Fans Unit Card Fail Major Fan failed Replace fan unit


3JK Issue 1.00
1.1 Troubleshooting
Check the basics first.

For example, if multiple alarms are present, and these include power supply voltage
or hardware alarms, always check their cause before looking at resultant down-
stream path failure or path warning (signal) alarms.
Similarly, if a path-related failure is indicated (no hardware or software alarms),
investigate the path. Go to the Craft Terminal History screen (15 minute view), to
check supporting data, such as low RSL and incidence of intermittent pre-failure BER
alarms, which if present are evidence of a path-related failure.
Refer to Troubleshooting Path Problems for more information.
Check if symptoms match the alarm.

Alarms reflect the alarm state, but in exceptional circumstances an alarm may be
raised because of a failure to communicate correctly with the alarm source, or a
failure in alarm management processing.
Always check to see if symptoms match the alarm, using LED indications and the
Craft Terminal.


3JK Issue 1.00
1.1 Troubleshooting
Check if recent work may be a cause. Recent work at the site may be a
cause or contributing factor. Check for a configuration change, software
upgrade, power recycling (reboot), or other site work:
Many hardware alarms are only initiated as a loss-of-communications alarm during a
reboot, software upgrade, or reconfiguration. By not being able to communicate with
the MSS, their settings cannot be loaded. The fault may be at the hardware device
(most likely), communications to it, or the MSS.
Hardware/software compatibility alarms will be raised when a new plug-in is
installed that needs a later version of 9500 MPR software.
Hardware incompatible alarms will be raised when a plug-in is installed in a slot that
has been configured for a different plug-in.
MSS before an ODU. If there is doubt about whether a fault is in the MSS or
ODU, always replace the MSS first; it is quicker and easier.
Hot-pluggable. MSS cards are hot-pluggable. There is no need to power-down
before replacing, but traffic will be lost unless the plug-in is protected.
Plug-in restoration time. Ensure adequate time is allowed for services to
resume when a plug-in is replaced.


3JK Issue 1.00
1.1 Troubleshooting
1.1.3 Troubleshooting Path Problems
A path-related problem, with the exception of interference, is

characterized by traffic being similarly affected in both directions.
Generally, if you are experiencing only a one-way problem, it is not a
path problem.
Normally a path problem is signaled by a reduced RSL, and depending on its
severity, a high BER.
Only in worst case situations, such as an antenna knocked out of alignment,
will a path fail completely, and stay that way.
For weather-related problems, such as rain or ducting, the path problem will
disappear as the weather returns to normal.

Note: A path extends from ODU antenna port to ODU antenna port.

3JK Issue 1.00
1.1 Troubleshooting
1.1.3.1 Path Problems on a Commissioned Link
A path problem on an existing link, one that has been operating

satisfactorily may be caused by:
Weather-related path degradation
If BER alarms are fleeting / not permanent and RSL returns to its normal,
commissioned level after the alarm is cleared, rain, diffraction, or multipath fading
is indicated. Rain fade is the likely cause of fade for links 13 GHz and higher.
Diffraction and multipath/ducting for links 11 GHz and lower. If these alarms are
persistent, there could be a problem with the link design or original installation.
Changed antenna alignment or antenna feed problem
If RSLs do not return to commissioned levels after a period of exceptionally strong
winds, suspect antenna alignment.
Also, check the antenna for physical damage, such as may occur with ice-fall. For a
remote-mounted ODU, check its antenna feeder.
New path obstruction
Where all other parameters check as normal, and the path has potential for it to be
obstructed by construction works, view/survey the path for possible new
obstructions.


3JK Issue 1.00
1.1 Troubleshooting
1.1.3.1 Path Problems on a Commissioned Link [cont.]
Interference from other signal sources

Interference usually affects traffic in just one direction. Unlike other path problems,
RSL is not affected. If suspected, check for new link installations at, or in the same
geographical area, as the affected site. Ultimately, a spectrum analyzer may have to
be used to confirm interference, which is not an easy task given the need to connect
directly to the antenna port, after removing the ODU.


3JK Issue 1.00
1.1 Troubleshooting
1.1.3.2 Path Problems on a New Link
For a new link, potential problems can extend to also include:

Incorrect antenna alignment
One or both antennas incorrectly aligned. Refer to Installation alignment procedure.
Mismatching antenna polarizations
Given a typical polarization discrimination of 30 dB, for most links it is not possible
to capture a signal to begin the antenna alignment process.
Incorrect path calculations
If the RSLs are too low or too high, antenna alignment is correct, and Tx power
settings are correct, check the path calculations used to determine the link
performance. A good calculation match is +/- 2 dB. Disagreements in excess of 3 dB
should be investigated.
Reflections
Reflection (path cancellation) problems may not have been picked up at the path
planning stage, particularly if the survey was a simple line-of-sight. If suspected,
resurvey the path.


3JK Issue 1.00
1.1 Troubleshooting
1.1.4 Troubleshooting Configuration Problems
Configuration problems should only occur during the set up of a new

link, or reconfiguration of an existing link. The more common problems
may be broadly categorized as:
Compatibility problems
The two alarms that may activate are Configuration Not Supported, and SW/HW
Incompatible:
Configuration Not Supported: The plug-in installed is not enabled or is incorrect for the
configuration.
SW/HW Incompatible: Typically raised when new hardware is plugged into an existing MSS that
has software from an earlier release. To remove the alarm, compatible 9500 MPR software is
required; install the latest software.
Incorrect circuit connections
No alarms are activated for incorrect circuit connections. An incorrect assignment
means the expected end-to-end circuit connectivity will not happen. Re-check circuit
assignments for all nodes carrying the lost circuit(s)
Take extra care when configuring ring circuits.


3JK Issue 1.00
1.1 Troubleshooting
1.1.4 Troubleshooting Configuration Problems [cont.]
Incorrect ID naming, and commissioning

All traffic-carrying circuits must have a unique flow ID for the cross-connect
capability to operate.
Incorrect/incompatible trib settings
Trib line interface settings incorrect, or line levels incompatible. While no alarm
activates for an incorrect setting, its effect may result in line levels being too low
(LOS alarm), or too high, resulting in a high BER.


3JK Issue 1.00
1.1 Troubleshooting
1.1.5 Troubleshooting Ethernet Problems
The most common Ethernet problems are network and connectivity

related and therefore always check the following first:
for User and NMS ports, verify link partner capability, provisioning, and
connection
for Radio ports, verify the cabling between ODU and MSS.
The LEDs on the Core-E card or MSS-1c or MPR-e front panel for each
Ethernet connector are a good indicator of correct connectivity and
activity on the Ethernet port.

This section gives general guidance on troubleshooting problems related to the four Ethernet ports on
the Core-E Card or on the MSS-1c or on the MPR-e.

3JK Issue 1.00
1.1 Troubleshooting
1.1.5 Troubleshooting Ethernet Problems [cont.]
In order for the green Link LED to light:

1 - Cable must be connected to Ethernet port
2 - Ethernet port must be enabled (provisioned Enabled on MSS Settings
Screen)
3 - Speed and mode (on MSS Settings Screen) must be provisioned the same as
the link partner.
The yellow LED opposite the green on the connector indicates activity
only.
The flashing yellow LED is not an indicator of signal type or quality.


3JK Issue 1.00
1.1 Troubleshooting
1.1.6 Troubleshooting TMN Problems
This section gives general guidance on troubleshooting TMN problems

related to NMS Ethernet ports 1 and 2 on the MSS-1c.
The most common TMN problems are network related and first alert is
normally observed by improper operation at the SNMP master. Always
check the following first:
Verify master is properly registered in NE to receive traps
Verify SNMP version matches system requirements
Verify correct community string and privileges
Verify proper network routing.
Refer to the next table for detailed TMN network troubleshooting.

Refer to table Troubleshooting Ethernet Problems on next slides for detail troubleshooting using the
LEDs locally at the alarmed site.

3JK Issue 1.00
1.1 Troubleshooting
1.1.6 Troubleshooting TMN Problems [cont.]
Problem Possible Cause Possible Solution

Unusually slow communication in 1. Normal network management There may be too many radios
radio network traffic is saturating the being managed within a single
communications channel. region. Split the radio network
management into different regions
and backhaul the traffic for each
region through separate channels.
2. Polling radios for PM data or Poll the radios more slowly.
missed alarms too rapidly
3. Multiple remote software Download to fewer radios at a
downloads in process time.
4. IP traffic other than network Configure external routers to
management traffic being routed allow only network management
through radio network related traffic through the
Management network of the
radios. Dynamic route updates
(OSPF) may attempt to reroute
high speed traffic through the TMN
network if a high speed link fails.
Continue


3JK Issue 1.00
1.1 Troubleshooting

Unable to operate controls using To perform control operations, the Register the Manager as a craft
SNMP Manager must be registered as a device. Manager registration type
craft device. can be changed as needed to type
ct to allow control operation and
then be changed back to nml for
normal operation.
Can Read SNMP objects but cannot 1. Incorrect community string Use the correct community string.
write to SNMP objects
2. If the TMN Interface is Use the correct write community
configured for SNMPv2, the write string
community string is probably
wrong.
No traps being received from NE 1. Manager not registered in NE to Register Manager with NE.
receive traps
2. Communication failure in Check network connectivity.
network Check redundant network paths
and routing. Traceroute (tracert)
is useful for locating path or
routing faults.
Continue


3JK Issue 1.00
1.1 Troubleshooting

Unable to communicate with the Possible communication path Use traceroute (tracert) to help
NE through the radio network failure or routing failure within locate for communication path or
(unable to ping the NE). the radio network. routing problems.
Can ping the TMN Interface but If using SNMPv2, using the wrong Verify community string or
cannot communicate with the NE community string username/ passphrase.
using SNMP, or can only see a few
SNMP objects in the NE.


3JK Issue 1.00
1.1.7 Troubleshooting MSS-1c Electrical or Optical
Connection
In case of electrical connection with MPT (PFoE: Power Feed over

Ethernet), there must be NO optical SFP plugged in MPT cage port
(even if no fiber connected).
In case of moving from optical to electrical connection with MPT, the

MSS-1c has to be switched off/on AFTER having unplugged the optical
SFP on MPT port.
In case of moving from electrical to optical connection with MPT, the

MSS-1c has to be switched off/on AFTER having plug the optical SFP on
MPT port.


3JK Issue 1.00
2 Failed Equipment Removal and
Replacement


3JK Issue 1.00
2 Failed Equipment Removal and Replacement
2.1 MSS-8/MSS-4 Card Removal and Replacement
Never install, change or remove a card without first connecting to the

shelf with an ESD grounding cable. Failure to do so may cause ESD
damage to the cards.
Plug-ins must be withdrawn and inserted using their finger-grip
fastener/pulls. Never withdraw or insert using attached cable(s).
Pulling on the cables may damage the cable, plug-in connector, and/or
plug-in card connector attachment.
When installing a plug-in, ensure its backplane connector is correctly
engaged before applying sufficient pressure to bring the plug-in panel
flush with the front panel. Improper alignment can result in damaged
pins on the backplane connector and/or damage to the plug-in
connector.

All plug-in cards can be removed and installed with power applied.

3JK Issue 1.00
2.1 MSS-8/MSS-4 Card Removal and Replacement [cont.]
All slots must be filled with either a peripheral plug-in card or a blank
panel. Failure to do so will compromise EMC integrity and cooling air
from the fan.
Use extreme caution when connecting or disconnecting the ODU cable
on the Radio Access Card. The shelf battery voltage is present on the
center conductor of the connector. When removing or replacing a Radio
Access Card, withdraw the card or the function from the shelf before
disconnecting the cable to the ODU. Failure to follow these cautions
may cause arcing and/or possible power spikes that could affect traffic
on other links installed at the node.
Removing an in-service card in an unprotected link will cause loss of
traffic. Removing an in-service card in a protected link requires
switching the traffic onto the standby (protection) channel.


3JK Issue 1.00
2.1 MSS-8/MSS-4 Card Removal and Replacement [cont.]
If the main Core-E Card fails, traffic and platform data will switch to
the spare Core-E Card automatically. Do not remove power from the NE
during the removal and replacement of the failed main Core-E Card
without first reviewing/performing the following procedure:
Turn off NE power.

Remove failed main Core-E Card.
Turn on NE power.
Wait for two (2) minutes.
Install replacement Core-E Card.


3JK Issue 1.00
2.2 Core-E Card Removal and Replacement
If the Main Core-E Card in slot 1 fails, traffic/services protection and

control platform protection switches to the spare Core-E Card in slot 2.
Loopbacks and all other manual operations, such as manual switch, tx
mute, will be lost (deactivated). Alarms previously active will be newly
detected and reported via notification, with a new time stamp.
Verify the replacement Core-E Card meets the following compatibility

rules:
Main Core-E Card (in slot 1) and Spare Core-E Card (in slot 2) must be the
same type.
Local and far end Core-E Cards must use the same software version, but do
not have to be the same type.


3JK Issue 1.00
2.3 Flash Card Replacement Procedure
First case: Core-E Protected
1) Get a spare FLASH CARD with the same sw-package release and license of the
Main flash.
2) Remove the faulty FLASH CARD from the main Core-E and insert the spare
one.
3) Insert the Core-E with the new FLASH CARD.
4) The MIB (MAIN FLASH) will be automatically aligned with the MIB (SPARE
FLASH).
Second case: Core-E Not Protected
1) Get a spare FLASH CARD with the same sw-package release and license.
2) Remove the faulty FLASH CARD from the main Core-E and insert the spare
one.
3) Insert the Core-E with the new FLASH CARD.
4) Carry-out the RESTORE procedure.


3JK Issue 1.00
2.3 Flash Card Replacement Procedure [cont.]
ATTENTION
(caution to avoid complete traffic loss)
Do not insert in the system a Flash Card the content of which is unknowned.
You must be aware that, if a Flash Card with SW information different from
that running in the system is inserted as it is, the software download will
be automatically carried out from the Flash Card toward the System, thus
causing a complete system crash.
NOTE
The license of the Spare Flash card can be different from the license of the Main
Flash card.
Only the license of the Main Flash card manages the NE.
By changing the Main Flash card, also the MAC address changes: in this case the
cross-connection must be reviewed.


3JK Issue 1.00
2.4 ODU Removal and Replacement
Get a spare unit with the same P/N.

Disconnect the MSS-ODU cable.
Change the ODU.
Reconnect the MSS-ODU cable.
Check with the CT that there are no alarms.

Note for 1+1 configurations:

before replacing the ODU make sure that the traffic is transmitted over the other channel.
Otherwise, force with the CT the traffic onto the other channel.

3JK Issue 1.00
2.5 MSS-1c Removal and Replacement
Never install, change or remove a card without first connecting

to the shelf with an ESD grounding cable. Failure to do so
may cause ESD damage to the cards.
Turn off the power supply

Disconnect all the cables and connect them to the spare MSS-1c
Turn on the power supply

All plug-in cards can be removed and installed with power applied.

3JK Issue 1.00
2.6 MPT-HC Removal and Replacement
Disconnect the cables and the co-box from the MPT-HC to be replaced
and connect them to the spare MPT-HC.
Reconfigure the MPT by using the WebEML (menu Commissioning >

Configuration) or if a backup file is available, restore the MPT
configuration by the WebEML (menu Commissioning > Configuration >
Backup/Restore).
Connect the WebEML to the CT port of MSS-1c and configure the PC to

Get automatically an IP address (because the NE is configured as
DHCP Server with default IP address 192.168.30.1 and subnet mask
255.255.255.252).



3JK Issue 1.00
2.7 MPT-MC Removal and Replacement
Disconnect the cables and connect them to the spare MPT-MC.
Reconfigure the MPT by using the WebEML (menu Commissioning >

Configuration) or if a backup file is available, restore the MPT
configuration by the WebEML (menu Commissioning > Configuration >
Backup/Restore).
Connect the WebEML to the CT port of MSS-1c and configure the PC to

Get automatically an IP address (because the NE is configured as
DHCP Server with default IP address 192.168.30.1 and subnet mask
255.255.255.252).



3JK Issue 1.00
End of Module
Fault management


3JK Issue 1.00
42
Section 4
Maintenance
Module 2
Software download
3JK Issue 1.00
9500 MPR

3JK Issue 1.00
Blank Page

Maintenance Software download
Document History

Marcoussis

Vimercate

3JK Issue 1.00
Module Objectives
Download a new software version.


3JK Issue 1.00


3JK Issue 1.00
Table of Contents
Page
1 MPR Node Software Download Menu 7
1.1 Server Access Configuration 8
1.2 Init Software Download 9
1.3 Software Status 10
1.4 How to upgrade the software from an older version 12
2 MPR Terminal Software Download Menu 13
2.2 Server Access Configuration 16
2.3 Init Software Download 17
2.4 Software Status 18
2.5 End of a Correct Download 20


3JK Issue 1.00


3JK Issue 1.00
1 MPR Node Software Download Menu


3JK Issue 1.00
1.1 Server Access Configuration
This menu allows to configure the FTP server to be used to download

the SWP to the NE.
Copy the ECT directory present in the SWP CD on the FTP server.

User Id and Password are the login information to access the FTP server.
In the Address field write the IP address of the FTP server.
In the Port field write the port to be used and in the Root Directory field write the FTP server
directory name from which the software can be downloaded.
By clicking on the Set Default button, the server access values will be filled in automatically with the

User Id: anonymous
Password: -
Port: 21
Root Dir: /
N.B. the System Default can be changed by writing different values in the fields and then by clicking
on button OK.

3JK Issue 1.00
1.2 Init Software Download
Through this menu the software is downloaded to the NE in order to

upgrade the NE software version.
Init Software Download screen


1. Click Add to add the available software packages on the PC.
2. Browse to the directory where the NE software was installed and click Open.
3. Highlight the description file (i.e. R95M.DSC) and click Open.
4. Highlight the line and click on the Init Download button.
The Forced check box can be used to force download (i.e. the complete description file is
downloaded to the NE).
5. Click Yes to begin the download process.
6. When the SW download starts, a screen showing the in progress operation of the download appears.
The download is aborted if the Abort button is pressed.
7. Click Ok.
Recommended operation: Before to start the software download it is recommended to disable the
ATPC operation (if it has been enabled) and to set in RTPC mode the max.
Tx power.

3JK Issue 1.00
1.3 Software Status
By clicking on the Software Unit

Status button a software unit status
screen opens (see on the next page)
and gives additional information on
the software package.
Software Status screen

This menu gives the information of the software installed in the NE.
The following information is displayed:
Name: software name
Version: software version
Operational state: enabled or disabled
Current status: committed or standby
The committed status refers to the software currently in use
Note: With MPT-HC the Sw Status is available only after the MPT-HC software download completion.
Note: The equipment software is installed on the compact flash, which has two banks.
This screen has two panels (each for one bank):
panel 1 refers to bank 1 with the Committed software and relevant information;
panel 2 refers to bank 2 with the Stand by software and relevant information.
The Flash Card, which stores the NE software, contains 2 banks.
The 2 banks can store 2 different software versions. One bank will be committed (active) and the other
bank will be standby.
Note: The second bank appears when a new software package has been downloaded the first time.
During download, necessary to update the software version, the download file is automatically stored in
the standby bank.
To activate the new version first check the operational status of the standby bank. If the status is
enabled (this means that download took place without errors) select Activation or Forced Activation in
the Software Management Action field and click on the Apply Action button.
By selecting Forced Activation the bank to be activated is forced to restart.
By selecting Activation the bank to be activated restarts only if the content of the two banks differ.

3JK Issue 1.00
1.3 Software Status [cont.]
By clicking on the Software Units Status button a screen opens, giving
additional information on the software package.


3JK Issue 1.00
1.4 How to upgrade the software from an older version
Start the SW Download on the Standby bank
Activate the Standby bank by pressing Activation and Apply Action on

the SW Status menu
Start again the SW Download on the Standby bank
Activate the Standby bank by pressing Activation and Apply Action on

the SW Status menu


3JK Issue 1.00
2 MPR Terminal Software Download
Menu


3JK Issue 1.00
2 MPR Terminal Software Download Menu


3JK Issue 1.00
2.1 Software Download Tool [cont.]
Software Download Tab Panel
Two fields are available:
1) SOFTWARE INFORMATION
This field gives the information of the software installed in the NE.
2) DOWNLOAD SOFTWARE PACKAGE
FTP SERVER PARAMETERS

This field allows to configure the FTP server to be used to download the SWP
to the NE.
SOFTWARE PACKAGE
Through this field the software is downloaded to the NE in order to upgrade
the NE software version.


3JK Issue 1.00
2.2 Server Access Configuration
SWP to the NE.
Copy the ECT directory present in the SWP CD on the FTP server.
Warning:
On the PC containing the Software Package must be
installed an FTP Server.
The PCs firewall (i.e Microsofts default firewall) may
prevent the download from starting up.

By clicking on the Check button, the server access values will be filled in automatically with the

User Id: anonymous
Password: -
Port: 21
Root Dir: /

3JK Issue 1.00
2.3 Init Software Download
Through this field the software is downloaded to the NE in order to

upgrade the NE software version.
Init Software Download screen

1. Click on Select Software Package button to add the available software packages on the PC.
2. Highlight the line where you find the File Name (i.e. 9500MPT.DSC) in the list and click on the Start
Download button.
- The Forced check box can be used to force download (i.e. the complete description file is
downloaded to the NE).
- If the Forced download is not selected, the system shall first proceed to compare the software to be
downloaded with the software present in the NE. Then only the differences are downloaded.
3. Click on the Download button to begin the download process.
4. When the SW download starts, a screen showing the in progress operation of the download appears.
The download is aborted if the Abort button is pressed.
5. Click Ok.
Recommended operation: Before starting the software download it is recommended to disable the
ATPC operation (if it has been enabled) and to set in RTPC mode the max.
Tx power.

3JK Issue 1.00
2.4 Software Status
By clicking on the
Active/Standby Software Package Summary
button a software unit status screen opens
(see on the next page) and gives additional
information on the software package.
Software Status screen

This tab panel Software Package Versions gives the information of the software installed in the NE.
The following information is displayed:
Name: software name
Version: software version
Current status: ACTIVE Version or STANDBY Version
The ACTIVE status refers to the software currently in use
NOTE The equipment software is installed on the compact flash, which has two banks.
This screen has two fields (each for one bank):
Active Software Package refers to bank 1 with the Actived software and relevant
information;
Standby Software Package refers to bank 2 with the Stand by software and relevant
information.
The Flash Card, which stores the NE software, contains 2 banks.

The 2 banks can store 2 different software versions. One bank will be committed (active) and the
other bank will be standby.
NOTE The second bank appears when a new software package has been downloaded the first time.
During download, necessary to update the software version, the download file is automatically stored
in the standby bank.
To activate the new version first check the operational status of the standby bank. If the status is
enabled (this means that download took place without errors) click on the Activate button in the
Standby Software Package.

3JK Issue 1.00
2.4 Software Status [cont.]
By clicking on the Active/Standby Software Package Summary tab panel

a screen opens, giving additional information on the software package.
Software Units Details screen

The following information is displayed on the screen:

adamoFpga: MPT FPGA Firmware
bootrom: MPT Boot Software
modem: MPT Modem Configuration Files
pvg610: MPT Modem Firmware
vxWorks: MPT Embedded Software

3JK Issue 1.00
2.5 End of a Correct Download
Activation of the new software:
At the end of the download process, press the < Activate > button of the
Stand-by Software Package field of the Software Status screen.
The NE reboots and the supervision is lost.
No activation of the new software:
At the end of the download process, check that the new software is installed in
the Stand-by Software Package field of the Software Status screen.
Warning:
After the activation of the Stand-by Software Package bank, the
connection between the WebEML (Craft Terminal) and the NE is lost.
The WebEML must be re-launched.


3JK Issue 1.00
Blank Page


3JK Issue 1.00
End of Module
Software download


3JK Issue 1.00
Last But One Page
1 All Rights Reserved Alcatel-Lucent @@YEAR

@@PRODUCT
@@COURSENAME
All Rights Reserved Alcatel-Lucent @@YEAR

@@COURSENAME - Page 1
All rights reserved Alcatel-Lucent @@YEAR
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent
All Rights Reserved Alcatel-Lucent @@YEAR
@@COURSENAME - Page 2

TWT63037-9500MPR R (1) .3.0.ce

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

TWT63037-9500MPR R (1) .3.0.ce

Caricato da

Copyright:

Formati disponibili

9500 MPR

9500MPR R 3.0 Operation and

All Rights Reserved Alcatel-Lucent 2011

All rights reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

Switch to notes view!

2 All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

All rights reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

Switch to notes view!

4 All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

9500MPR R 3.0 Operation and Maintenance

All Rights Reserved Alcatel-Lucent 2011

Switch to notes view!

6 All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

Switch to notes view!

Welcome to 9500MPR R 3.0 Operation and Maintenance

Upon completion of this course, you should be able to:

Configure and manage the 9500MPR

7 All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

Switch to notes view!

8 All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

9 All Rights Reserved Alcatel-Lucent 2011

Where you can get further information

If you want further information you can refer to the following:

All Rights Reserved Alcatel-Lucent 2011

Switch to notes view!

10 All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

Did you meet the following objectives ?

Yes (or No (or

All Rights Reserved Alcatel-Lucent 2011

Switch to notes view!

Yes (or No (or

12 All Rights Reserved Alcatel-Lucent 2011

Thank you for your answers to this questionnaire

All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

112 All Rights Reserved Alcatel-Lucent 2011

This page is left blank intentionally

Edition Date Author Remarks

01 2010-07-21 ALU University, First edition

02 2011-02-01 ALU University, Updated to rel.3.0

All Rights Reserved Alcatel-Lucent 2011

Upon completion of this module, you should be able to:

Describe the Basic Concepts of the 9500 MPR.

113 All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

114 All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

116 All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

117 All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

Alcatel-Lucent microwave product acronyms are derived as

118 All Rights Reserved Alcatel-Lucent 2011