9500MPR R 1.2.1 Operation and Maintenance

9500 MPR
9500MPR R 1.2.1 Operation and

Maintenence
TWT63013-R 1.2.1-SG1-SEN- I1.0 Issue 1.00
STUDENT GUIDE
All Rights Reserved © Alcatel-Lucent 2009
All rights reserved © Alcatel-Lucent 2009

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

9500MPR R 1.2.1 Operation and Maintenence - Page 1
Empty page
Switch to notes view!
2 All Rights Reserved © Alcatel-Lucent 2009

9500 MPR
9500MPR R 1.2.1 Operation and Maintenence
This page is left blank intentionally

Terms of Use and Legal Notices
1. Safety to
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-Lucent’s 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 written consent of
Alcatel-Lucent.
All
3 rights reserved © Alcatel-Lucent 2009 All Rights Reserved © Alcatel-Lucent 2009
9500 MPR
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 1. Course
This Product Overview
4. Topic/Section is Positioned Here
Course Module
outline 1. Introduction
Technical support
Module 2. Architecture
Course Module
objectives
3. Management System
Section 2. Functional Description
1. Topic/Section is Positioned Here 6. Topic/Section is Positioned Here
Xxx Module 1. MSS HW Hardware Architecture
Xxx Module 2. ODU HW Hardware Architecture
Xxx 3. NE operation
Section
Module 1. Operator interface
2. Topic/Section is Initial
Module 2. Positioned Here
configuration
Module 3. Performance monitoring
3. Section
Topic/Section is Positioned Here
4. Maintenance
Module 1. Fault management
Module 2. Software download

9500 MPR

Course Outline [cont.]
6
9500 MPR

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

9500 MPR

Course Objectives [cont.]

9500 MPR

About this Student Guide
z
Conventions used
Switch 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.
9 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.]
z Switch to notes view!

9500 MPR

Self-assessment of Objectives
Contract number :
z At the end of each section you will be asked to fill this questionnaire
Course title :
z Please, return this sheet to the trainer at the end of the training
Client (Company, Center) :
Language : 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:
Section 1
Product Overview
Module 1
Introduction
3JK Edition 1.00
All Rights Reserved © 2007, Alcatel-Lucent

3JK Edition 1.00
Section 1 · Module 1 · Page 1
Blank Page
1·1·2 All Rights Reserved © Alcatel-Lucent 2009

Product Overview · Introduction
9500 MPR · 9500MPR R 1.2.1 Operation and Maintenence This page is left blank intentionally
Document History
Edition Date Author Remarks
01 2007-07-30 External Consultant First edition

3JK Edition 1.00
Objectives
z Objectives: to be able to
describe the basic concepts of the 9500 MPR.

9500 MPR · 9500MPR R 1.2.1 Operation and Maintenence

3JK Edition 1.00
Objectives [cont.]


3JK Edition 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 10
1.4 Service Awareness 12
1.5 Packet Node 14
1.6 Service-driven Packet Adaptive Modulation 16
Blank Page 18
2 System description 19
2.1 System description 20
2.2 9500 MPR Node 23
Blank Page 28
3 Radio configuration 29
3.1 Radio configuration 30
4 System configuration 31
4.1 Example of System configurations 32
Blank Page 37
End of Module 38


3JK Edition 1.00
Table of Contents [cont.]
1·1·6
ThisAll Rights
page is left blank intentionally
Reserved © Alcatel-Lucent 2009

3JK Edition 1.00
1 Understanding the 9500MPR
innovations


3JK Edition 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 P = Packet
M = Microwave
5 for Radio Cross-Connect


3JK Edition 1.00
1.2 Presentation
z 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 Edition 1.00
1.3 Multiservice Aggregation Layer
Access network Packet Backhaul network

Any TDM/Ethernet interfaces Ethernet aggregation layer
nxE1 9500 MPR
GSM Aggregated traffic
2G over Ethernet
ISAM,
WiMAX
Ethernet
3G HSDPA
Voice on R99
nxE1
Single technology throughout the network: Ethernet as convergence layer
1 · 1 · 10 All Rights Reserved © Alcatel-Lucent 2009

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

3JK Edition 1.00
1.3 Multiservice Aggregation Layer [cont.]

z Multiservice aggregation layer means the capacity to use Ethernet as common transmission layer to
transport any kind of traffic. Ethernet becomes the convergence layer.
z E1, ATM and IP/Eth is carried over a common layer and therefore over one single physical interface. This
allows sharing a common packet transmission infrastructure, regardless of the nature of carried traffic.
z Due to the nature of Ethernet we can then discriminate each service based over several parameters like
quality of service.
z Mapping over Ethernet of these different technologies is achieved by standardized protocols like circuit-
emulation and pseudo-wire. The use of standard protocol is a key factor that allows operators to recover
their original traffic at any point in the network from any equipment compliant to the standards.

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

INPUTS : Any interfaces (E1, Ethernet)
PACKETIZATION PROCESSING:
TDM Æ Standard CEoEth [MEF8]
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

z 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, 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).
z 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 Edition 1.00
1.4 Service Awareness [cont.]


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

z 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 Edition 1.00
1.5 Packet Node [cont.]

z Packet Node permits to handle all the traffic over a common layer (Multiservice Aggregation Layer),
allowing overbooking across different technologies: the same services generated by an ATM source and an IP
source can share the same bandwidth resource.

3JK Edition 1.00
1.6 Service-driven Packet Adaptive Modulation
Modulation
schemes
64 QAM
Satisfaction
99.9
16 QAM Capacity
99.99
4 QAM 99.999
9500 MPR
Time line Outage Customer unavailability
Satisfaction
Capacity
14 MHz 16 Mb/s in 4 QAM at 99.999%

availability
14 MHz 48 Mb/s in 64 QAM at 99.9%
availability Voice Traffic Best Effort Traffic
Maintain the same level of quality for voice services as in the TDM network

z 9500 MPR allows to fully exploit the air bandwidth in its entirety by changing modulation scheme according
to the propagation availability, associating to the different services quality the available transport capacity.

3JK Edition 1.00
1.6 Service-driven Packet Adaptive Modulation [cont.]
Microwave TDM Microwave Packet

Adaptive modulation adds or Adaptive modulation adds or
removes capacity from physical removes capacity from best effort
interfaces services, regardless of physical
interface
Complex physical interfaces
networking operation is required Interface decoupling from service
to ensure that only low priority classification removes any additional
traffic is dropped networking operations, low priority
service is always dropped, regardless
of what the interface is
Fading Packets traffic over TDM

Total Band Fading Native Packet traffic
Total Band


3JK Edition 1.00
Blank Page


3JK Edition 1.00
2 System description


3JK Edition 1.00
2.1 System description
z 9500 MPR radio system family supports, in a common platform, PDH E1

and packet data (Ethernet) applications.
z Outdoor transceivers are available in the frequency range from 6 GHz
up to 38 GHz.
z 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.


3JK Edition 1.00
2.1 System description [cont.]

z 9500 MPR in the split mount architecture is built by two separate units:
z MSS (Microwave Service Switch): indoor unit for split mount and stand alone configurations (Ethernet
uplink)
z ODU300 microwave uplink for split mount configurations

3JK Edition 1.00
2.1 System description [cont.]
z MSS implements functionalities of grooming, routing, switching and

protection, exploiting a packet oriented technology.
z The Core-E platform, with symmetrical x-connection functions,
manages different radio directions, with the possibility to add-drop
tributaries in case of local PDH/Ethernet accesses. Core-E platform is
based on packet technology (Ethernet Switch) with a generic interface
serial GbEth between Core-E and peripherals
z 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:
32 x E1 local access modules
Radio Access modules (modem card)
z 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.


3JK Edition 1.00
2.2 9500 MPR Node

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

3JK Edition 1.00
2.2 9500 MPR Node [cont.]
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 and Radio 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

z The figure illustrates platform functions/capabilities.

3JK Edition 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 and Radio 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

z The figure illustrates platform functions/capabilities.

3JK Edition 1.00
z Radio capacity, channelling scheme and modulation (Static Modulation)

Net radio E1 Equivalent Capacity
Channel Spacing Modulation
throughput (TDM2TDM)
4 QAM 10,88 Mbit/s 4 E1
7 MHz 16 QAM 21,76 Mbit/s 8 E1
64 QAM 32,64 Mbit/s 13 E1
4 QAM 21,76 Mbit/s 8 E1
14 MHz 16 QAM 43,52 Mbit/s 18 E1
64 QAM 65,28 Mbit/s 27 E1
4 QAM 43,52 Mbit/s 18 E1
16 QAM 87,04 Mbit/s 37 E1
32 QAM 111,36 Mbit/s 48 E1
28 MHz 64 QAM 130,56 Mbit/s 56 E1
128 QAM 156,80 Mbit/s 68 E1
256 QAM 177,60 Mbit/s 77 E1
56 MHz 128 QAM 313,60 Mbit/s 136 E1

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

3JK Edition 1.00
z Radio capacity, channelling scheme and modulation

(Adaptive Modulation)
Channelling Modulation Net radio throughput Equivalent capacity
Spacing E1 (Note)
4 QAM 43,52 Mbit/s 18 E1
28 MHz 16 QAM 87,04 Mbit/s 37 E1
64 QAM 130,56 Mbit/s 56 E1
4 QAM 21,76 Mbit/s 8 E1
14 MHz 16 QAM 43,52 Mbit/s 18 E1
64 QAM 65,28 Mbit/s 27 E1
4 QAM 10,88 Mbit/s 4 E1
64 QAM 32,64 Mbit/s 13 E1

z Note: the total capacity associated to the TDM2TDM and TDM2Eth profiles is always the capacity relevant to
the lowest modulation scheme (4 QAM if the Adaptive Modulation is in the 4/16/64 QAM range and 4 QAM if
the Adaptive Modulation is in the 4/16 QAM range).

3JK Edition 1.00
Blank Page


3JK Edition 1.00
3 Radio configuration


3JK Edition 1.00
3 Radio configuration
3.1 Radio configuration
z 1+0 unprotected
z 1+1 Hot-Standby (HS) (2 coupler types: balanced 3dB and unbalanced

1.5/6.0dB)
z 1+1 Hot-Standby Space Diversity (HSSD) (no combiner)
z 1+1/2x(1+0) Frequency Diversity (FD) (co-polar)
z 1+1/2x(1+0) Frequency Diversity (FD) (hetero-polar)


3JK Edition 1.00
4 System configuration


3JK Edition 1.00
4.1 Example of System configurations
z TDM Over Ethernet Packet Node - Mapping of 32 E1 on Ethernet


3JK Edition 1.00
4.1 Example of System configurations [cont.]
z TDM and Ethernet Terminal Packet Transport - 32 E1 Access, 1 Radio

Direction


3JK Edition 1.00
z TDM and Ethernet Add/Drop N1 Packet Node - Ethernet and 32 E1 Local

Access, 2 unprotected links


3JK Edition 1.00
z TDM and Ethernet Terminal Packet Node-Ethernet and 32 E1 Local

Access, 1 protected link


3JK Edition 1.00
z TDM and Ethernet Add/Drop Packet Node-Ethernet and 32 E1 Local

Access, 1 unprotected link, 1 protected link


3JK Edition 1.00
Blank Page


3JK Edition 1.00
End of Module
Introduction


3JK Edition 1.00
Section 1
Product Overview
Module 2
Architecture
3JK Edition 1.00

3JK Edition 1.00
Blank Page

Product Overview · Architecture
Document History

3JK Edition 1.00
Objectives
describe the main functionalities of the 9500 MPR.


3JK Edition 1.00
Objectives [cont.]


3JK Edition 1.00
Table of Contents
Page
1 MSS Architecture 7
1.1 MSS Architecture 8
1.2 PDH Terminal with PDH local accesses 9
1.3 Flash Cards with Licences 10
1.4 ODUs 13
Blank Page 14
2 Traffic profiles 15
2.1 Traffic profiles 16
2.2 TDM2TDM 19
2.3 TDM2Eth 21
2.4 ETH2ETH 23
Blank Page 24
3 Traffic Management (QoS) 25
3.1 Quality Of Services (QoS) 26
3.2 Core-E QoS 27
3.3 Core-E scheduler 28
3.4 Modem unit QoS 29
3.5 Modem unit scheduler 30
3.6 Ethernet Traffic Management 31
3.6.1 Bridge type change 32
3.6.2 Reserved Multicast Addresses 33
4 Synchronisation 35
4.1 Synchronisation 36
4.2 Differential clock recovery 37
1 · 2 · 54.3 Adaptive clock recovery All Rights Reserved © Alcatel-Lucent 2009 38
9500 MPR 4.4 Synchronisation Interface 39
· 9500MPR R 1.2.1 Operation and Maintenence
Blank Page 40
5 Cross-connections 41
5.1 Cross-connection 42
5.2 E1 Cross-connection 43
5.3 Ethernet Cross-connection 44
6 Protections 45
6.1 Protections 46
6.2 9500 MPR Packet Node Full Protection (Radio) 47
6.3 RPS Switching Criteria 49
6.4 EPS Switching Criteria 50
6.5 HSB Switching Criteria 51
End of Module 52

3JK Edition 1.00
1·2·6
ThisAll Rights

3JK Edition 1.00
1 MSS Architecture


3JK Edition 1.00
1 MSS-8 Architecture
1.1 MSS Architecture
Core-E
Access
Radio
Peripherals
Flash Peripherals
PSU Controller
RAM
GbEth ETHERNET GbEth

32xE1 Access MODEM 300 Module –
SWITCH IF interface
Module
(to ODU)
LIU LIU
4x10/100/1000 1x1000 Optical

Ethernet Ethernet

z Core-E platform:
z symmetrical Cross-connection function
z able to manage different radio directions
z add-drop tributaries in case of local PDH/Ethernet accesses
z 4 x Electrical GbEth + 1 optional Optical GbEth
z Peripherals (6 modules in MSS-8; 2 modules in MSS-4)
z 32 x E1 local access module (SCSI 68 32E1)
z Radio IF interface

3JK Edition 1.00
1.2 PDH Terminal with PDH local accesses
PSU Flash
Controller
RAM
MODEM
ODU
PDH 300
Access ETHERNET
E1 SWITCH Module
Module
(TDMoP)
LIU
MSS Core-E
4xEth.

z In the figure is shown the easiest configuration: PDH terminal.

3JK Edition 1.00
1.3 Flash Cards with Licences
z Super PDH licences (TDM2TDM):

6x40 Mbps 5x40/1x60 Mbps
5x40/1x80 Mbps 4x40/2x60 Mbps
4x40/2x80 Mbps 6x60 Mbps
5x40/1x100 Mbps 4x40/2x130 Mbps
6x100 Mbps
5x40/1x150 Mbps
4x40/2x150 Mbps
6x150 Mbps
5x40/1x300 Mbps
4x40/2x300 Mbps
6x300 Mbps

z The licences are stored in the Flash card installed in the Core-E Module. The Flash card stores also the
Equipment software, the equipment MIB and the equipment MAC address.
z Note: With these flash cards the available circuit emulations are: TDM2TDM, ETH2ETH.

3JK Edition 1.00
1.3 Flash Cards with Licences [cont.]
z Site Aggregator licences

(TDM2TDM & TDM2ETH):
5x40/1x100 Mbps 4x40/2x130 Mbps
6x100 Mbps
5x40/1x150 Mbps
4x40/2x150 Mbps
6x150 Mbps
5x40/1x300 Mbps
4x40/2x300 Mbps
6x300 Mbps

z The licences are stored in the Flash card installed in the Core-E Module. The Flash card stores also the
Equipment software, the equipment MIB and the equipment MAC address.
z Note: With these flash cards the available circuit emulations are: TDM2TDM, ETH2ETH, TDM2ETH.

3JK Edition 1.00
1.3 Flash Cards with Licences [cont.]
z Adaptive Modulation (TDM2TDM): z Adaptive Modulation (TDM2ETH):

5x40/1x130 Mbps 5x40/1x130 Mbps
4x40/2x130 Mbps 4x40/2x130 Mbps
6x130 Mbps 6x130 Mbps
6x40 6x40
6x80 Mbps 6x80 Mbps
5x40/1x150 Mbps 5x40/1x150 Mbps


3JK Edition 1.00
1.4 ODUs
z ODU300 are designed for direct-antenna mounting.

z ODU300 supports:
Modulation rates from 4 QAM to 256 QAM
Bandwidths from 7 to 56 MHz
Frequency bands from 6 to 38 GHz
High transmit power


3JK Edition 1.00
Blank Page


3JK Edition 1.00
2 Traffic profiles


3JK Edition 1.00
2 Traffic profiles
2.1 Traffic profiles
z Three kinds of traffic profiles have been identified:
1. TDM2TDM ( 9500MPR ⇔ 9500MPR, internal TDM )

2. TDM2Eth ( 9500MPR ⇔ TDM to Ethernet )
3. DATA (Ethernet to Ethernet)

z Profiles 1 and 2 meet MEF8 standard

3JK Edition 1.00
2 Traffic profiles
2.1 Traffic profiles [cont.]

z Case 1
z 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 network. The
Circuit Emulation Service is TDM2TDM in Node 1 and Node 2. The Cross connections to be implemented are
PDH-Radio type.
z Case 2
z The E1 stream is inserted in Node 1 and extracted in Node 2. One IWF is inside the 9500 MPR, but the
second IWF is external to the 9500 MPR 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
z Case 3
z The E1 stream is inserted/extracted in Node 1. One IWF is inside the 9500 MPR, but the second IWF is
external to the 9500 MPR 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.1 Traffic profiles [cont.]

z Cases 4 and 5
z 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 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 Ethernet switch.

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

z Flow Id present (user defined)

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

3JK Edition 1.00
2 Traffic profiles
2.2 TDM2TDM [cont.]
z Both the IWFs belong to 9500MPR and the packets are not supposed to
exit the 9500 MPR network.
z The IWF parameters listed above, have predetermined values and don’t
need to be provisioned.
y Mac addresses are determined as consequences of the cross connections.
y Payload size is fixed to 122 bytes
y ECID will be the same value as Flow Id
y TDM clock source: clock recovery differential,
y Flow Id provisioned by ECT/NMS

z ECID = Emulated Circuit Identifier

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

z Flow Id present (user defined)

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

3JK Edition 1.00
2 Traffic profiles
2.3 TDM2Eth [cont.]
z Only one of the IWFs belongs to 9500MPR and the packets are supposed
to exit the 9500MPR network.
y 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.
y Payload size: fixed to 256 bytes
y ECID : provisioned by ECT/NMS, 2 different values may be used for each direction
y TDM clock source is provisioned by ECT/NMS: clock recovery adaptive, clock recovery
differential
y Flow Id is provisioned by ECT/NMS (One Vlan is assigned to each bi-directional circuit
emulated E1 flow)

z ECID = Emulated Circuit Identifier

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

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

z 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
Blank Page


3JK Edition 1.00
3 Traffic Management (QoS)


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

implementation in the switch and Radio Interface module. Both those
QoS functions must be properly configured in order to get the wished
behavior on Ethernet flows that will be transmitted towards the Radio.


3JK Edition 1.00
3.2 Core-E QoS

z The figure shows an overview of the QoS implementation inside the switch.
z 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.
z 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 is reserved for TDM flows; the remaining queues are
shared by all Ethernet flows according the classification mechanism configured by CT/NMS.
z 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
2. DiffServ: each packet is classified based on DSCP field in the IP header to determine the priority.
010, 001 Q1
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.3 Core-E scheduler
z The scheduler algorithm cannot be configured.

z HQP scheduler algorithm is used on queues Q8, Q7 and Q6.
z 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.4 Modem unit QoS

z In the figure is shown an overview of the QoS implementation inside the Radio Interface module.
z 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.
z QoS based on IEEE std. 802.1p
z 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.
z 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

111, 110 Q5 (higher priority)
101 Q4
100 Q3
011, 000 Q2
010, 001 Q1
z QoS based on DiffServ
DiffServ priority Queue

111000, 110000, 101110, 101000 Q5 (higher priority)
100110, 100100, 100010, 100000 Q4
011110, 011100, 011010, 011000 Q3
010110, 010100, 010010, 010000
001010, 001100, 001010, 001000, 000000 Q2
All remaining values Q1

3JK Edition 1.00
3.5 Modem unit scheduler
z The scheduler algorithm implemented inside the Modem unit is High

Queue Pre-empt: when a packet arrives in the higher priority queue it
is immediately transmitted.


3JK Edition 1.00
3.6 Ethernet Traffic Management
z The Ethernet traffic is all the traffic entered the MPR network from
user Ethernet ports.
z 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
3.6.1 Bridge type change
z 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.
z Note: 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
3.6.2 Reserved Multicast Addresses
Reserved Multicast
Function Action
Address
01-80-C2-00-00-00 Bridge Group Address Forward
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)

z 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.
z The actions taken by the system can be:
z Discard - The system discards all ingress Ethernet frames and must not generate any egress Ether-net
Frame carrying the reserved multicast address.
z Forward - The system accepts all ingress Ethernet frames as standard multicast frames and for-wards
them accordingly.
z 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
Blank Page


3JK Edition 1.00
4 Synchronisation


3JK Edition 1.00
4 Synchronisation
4.1 Synchronisation
z TDM data flow is fragmented and the fragments are transmitted over a
Packet Switched Network (PSN);
z The received fragments need to be reassembled in the original TDM
data flow at the “original bit rate”
z Two main methods can be used to recover at the RX site, the original
bit rate:
Differential clock recovery: recalculation of the original clock based of the

Delta respect to a reference clock that is available at both TX and RX site
Adaptive clock recovery: based on the average rate at which the packets
(fragments) arrive at RX site

z Adaptive: simpler network, but performances depends on the PDV (Packet Delay Variation) in the Network.
Always used when the reference clock isn’t distributed on the whole network.
z Differential: used in case of clock distribution on the whole network. It’s more reliable than Adaptive; also
used in TDM2TDM traffic (MPR to MPR).
z N.B.: In meshed networks (rings) do not close the synchronisation configuration.

3JK Edition 1.00
4 Synchronisation
4.2 Differential clock recovery
End End
System1 System2
IWF PSN
PSN IWF

z Common reference clock IS available at both Ends.

z IWF system, at RX side, generate output clock based on RTP TimeStamps which are sent together with each
Fragments.

3JK Edition 1.00
4 Synchronisation
4.3 Adaptive clock recovery
End End
System1 System2
IWF PSN
PSN IWF

z Common reference clock is NOT available at both Ends.

z 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
4 Synchronisation
4.4 Synchronisation Interface
To implement differential CK recovery, for each node must be defined:

z NE Role definition, related to NE CK
Master
Slave
z NE Synchronisation Source definition
Primary
Secondary
z Source choice, both for primary and secondary, with proper rule
free running
PDH interface [port]
external interface [2.048; 5.000; 10.000 MHz]
radio interface


3JK Edition 1.00
Blank Page


3JK Edition 1.00
5 Cross-connections


3JK Edition 1.00
5 Cross-connections
5.1 Cross-connection
SLOT 3 (PDH) SLOT 4 (RADIO)
SLOT 5 SLOT 6 (RADIO)
SLOT 7 SLOT 8
ETH 4
ETH 2
ETH 1
ETH 3

z 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.
z The decision made by the switch to forward the received packet is based on the destination MAC address.

3JK Edition 1.00
5 Cross-connections
5.2 E1 Cross-connection
z Each E1 can be cross connected independently

z E1 can be cross connected to any of the following interfaces:
Radio interface
Ethernet interface
z Each E1 (board #, port #) must be associated to a signal flow ID


3JK Edition 1.00
5 Cross-connections
5.3 Ethernet Cross-connection
z Ethernet cross connection is based on Ethernet switching (level 2)

z According to destination address each packet is switched to the correct
port, as reported in an “Address Resolution Table” (ART)
z If destination address is not present in the ART a flooding mechanism is
foreseen


3JK Edition 1.00
6 Protections


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

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

y Spare ODU module is powered off.


3JK Edition 1.00
6 Protections
6.2 9500 MPR Packet Node Full Protection (Radio)

z Legend:
z 1 RPS
z 2 EPS
z 3 HSB

3JK Edition 1.00
6 Protections
6.2 9500 MSS Packet Node Full Protection (Radio) [cont.]
2
z Legend:
z 2 EPS

3JK Edition 1.00
6 Protections
6.3 RPS Switching Criteria
z The switching criteria are:
y Early Warning
y High BER
y Dem Fail
y Loss of Frame (LOF) on the radio signal coming from the direct way
y Loss of Frame (LOF) on the radio signal coming from the cross way


3JK Edition 1.00
6 Protections
6.4 EPS Switching Criteria
z The switching criteria are:
y Peripheral Card Fail (switching off of the peripheral included)

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


3JK Edition 1.00
6 Protections
6.5 HSB Switching Criteria
z The switching criteria are :
y Radio Interface Peripheral Card Fail (switching off of the peripheral included)
y Radio Interface Peripheral Card Missing
y MSS-ODU cable loss
y 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
End of Module
Architecture


3JK Edition 1.00
Section 1
Product Overview
Module 3
Management System
3JK Edition 1.00

3JK Edition 1.00
Blank Page

Product Overview · Management System
Document History
01 2007-07-30 External consultant First edition

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


3JK Edition 1.00
Objectives [cont.]


3JK Edition 1.00
Table of Contents
Page
1 Management System 7
1.1 Network Management 8
1.2 IP addresses 9
1.3 TMN communication channels 10
1.4 LCT Connection 11
Answer the Questions 12
Blank Page 13
End of Module 14


3JK Edition 1.00
1·3·6

3JK Edition 1.00
1 Management System


3JK Edition 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

z Providing a single managed network reduce the operational expenditure of a network directly improving the
margin in the P&L of an Operator.
z 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.
z 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

3JK Edition 1.00
1 Management System
1.2 IP addresses
z The NE has the following IP addresses:

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.
z 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 Edition 1.00
1 Management System
1.3 TMN communication channels
z On the 9500 MPR two 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).


3JK Edition 1.00
1 Management System
1.4 LCT Connection
z 9500MPR can be controlled by a LCT connected to the Core-E unit.

z The connection can be performed by using:
The dedicated NMS Ethernet port
Traffic Ethernet port, configured as TMN port.


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

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


3JK Edition 1.00
VLAN ID
NE IP 10.0.3.1 11 12 13 14 27 28 41 42
NMS IP Blank Page

10.0.10.1
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
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
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
Syncro Scheme
9500 MPR · 9500MPR R 1.2.1 Operation and Maintenence 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 Edition 1.00
End of Module
Management System


3JK Edition 1.00
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
Document History

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
Page
1 PDH Access Unit 7
1.1 PDH Access unit 8
Blank Page 10
2 Modem unit 11
2.1 Modem unit 12
Blank Page 14
3 Core-E unit 15
3.1 Core-E unit 16
Blank Page 18
4 Distributors 19
4.1 Distributor 20
Blank Page 30
End of Module 31


3JK Edition 1.00
2·1·6
ThisAll Rights

3JK Edition 1.00
1 PDH Access Unit


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

z 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).
z 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.
z 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
z 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 PDH Access Unit
1.1 PDH Access unit [cont.]
E1 E1
17-32 1-16


3JK Edition 1.00
Blank Page


3JK Edition 1.00
2 Modem unit


3JK Edition 1.00
2 Modem unit
2.1 Modem unit
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

z In Tx direction, the MODEM 300 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.
z Digital Framer
z Classification of incoming packets from the Core-E (QoS)
z Fragmentation
z Air Frame Generation (synchronous with NE clock)
z Digital Modulator
z TX Analog Chain
z DAC & low pass filtering
z Modulation to 311 MHz IF TX
z In Rx direction, the MODEM 300 Module terminates the IF signal coming from the MXC Out Door Unit
extracting the original CBR and then the original Ethernet packets to be given the Core-E which distributes
them to the proper Module.
z RX Analog Chain
z 126 MHz IF RX demodulation to I & Q
z low pass filtering & ADC
z Digital Demodulator
z Carrier & CK recovery
z Equalisation
z Error Correction
z Digital Deframer
z RPS (hitless)
z Defragmentation

3JK Edition 1.00
2 Modem unit
2.1 Modem unit [cont.]
Transmitter connected to the antenna


3JK Edition 1.00
Blank Page


3JK Edition 1.00
3 Core-E unit


3JK Edition 1.00
3 Core-E unit
3.1 Core-E unit

z Based on packet technology with 8 GbEth serial internal interfaces between Core-E and peripherals
(jumbo frames 9728 bytes allowed)
z 4x10/100/1000 Eth embedded interface (RJ45)
} 1x1000 base-Lx or Sx (SFP optical interference), available with an optical plug-in.
z Macro Functions
z Controller
z 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.
z Selection of the synchronization Ck to be distributed to all plug-in.
z The flash card stores the licence type, the equipment software, the equipment MIB and the equipment MAC
address.

3JK Edition 1.00
3 Core-E unit
3.1 Core-E unit [cont.]


3JK Edition 1.00
Blank Page


3JK Edition 1.00
4 Distributors


3JK Edition 1.00
4 Distributors
4.1 Distributor
z The Distributor subracks available are shown in the next pages.


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

(3DB16104AAAA)


3JK Edition 1.00
4 Distributors
z Protection Panel RJ45 120 ohm (Front/Rear) (1AF15245ABAA)


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


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


3JK Edition 1.00
4 Distributors
z Connector support 1.6/5.6 75 ohm Panel 1U (3CC08061AAAA)


3JK Edition 1.00
4 Distributors
z Connector support BNC 75 ohm Panel 1U (3CC08061ABAA)


3JK Edition 1.00
4 Distributors
z Support 19 Inch modules 120 ohm Panel 3U (3CC07810AAAA)


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


3JK Edition 1.00
z How many E1 streams are available on the front panel of the PDH
access unit?
z When the Power Emission Status LED of the Modem unit is green ON in
the HSB configuration?
z 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
Section 2
Functional Description
Module 2
ODU HW Hardware Architecture
3JK Edition 1.00

3JK Edition 1.00
Blank Page

Functional Description · ODU HW Hardware Architecture
Document History
01 YYYY-MM-DD Last name, first name First edition

3JK Edition 1.00
Objectives
describe the functionality of the ODUs.


3JK Edition 1.00
Objectives [cont.]


3JK Edition 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
End of Module 24


3JK Edition 1.00
2·2·6

3JK Edition 1.00
1 Outdoor Units


3JK Edition 1.00
1 Outdoor Units
1.1 ODU300 Construction and Mounting
z Construction comprises:
Cast aluminium base
Pressed aluminium cover
Base and cover passivated and then polyester powder coated
Compression seal for base-cover weatherproofing
Carry-handle
ODU300 Housing

z 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.
z The ODUs, are designed for direct antenna attachment via an 9500MPR-specific mounting collar supplied
with the antennas.
z ODU polarization is determined by the position of a polarization rotator fitted within the mounting collar.
z 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.
z ODUs are fixed for Tx High or Tx Low operation.
z 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.0/3.0 dB.
z Unequal is nominally 1.5/6.0 dB.

3JK Edition 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 4, 16, 32, 64, 128 QAM
IF Specifications
Intermediate Frequency Transmit 311 MHz
Receive 126 MHz
Maximum IF 10.3 mm MSS to ODU 150 meters
Cable length [NB]

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

3JK Edition 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 Edition 1.00
2 ODU300 block diagram


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

z 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.
z 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.
z 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.
z Between the IQ modulator and the mixer, a variable attenuator provides software adjustment of Tx
power.
z After the mixer, the transmit signal is amplified in the PA (Power Amplifier) and passed via the diplexer
to the antenna feed port.
z 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.
z A DC-DC converter provides the required low-voltage DC rails from the -48 Vdc supply.
z 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.
z 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 to prevent incorrect user
selection.
z 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 Edition 1.00
3 Outdoor Installations


3JK Edition 1.00
3.1 Installing the ODU
z All ODUs are designed for direct-mounting to a collar supplied with

direct-fit antennas. ODUs can also be installed with standard antennas
using a remote-mount kit.
z 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.
z On the next slides, information are given concerning:
Direct-Mounted ODUs
Remote-Mounted ODUs
Grounding the ODU


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


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

z 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:
z a flexible waveguide is required.
z The remote mount allows use of standard, single or dual polarization antennas.
z 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.
z 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.
z 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 Edition 1.00
3.4 Remote-Mounted ODUs (solution 2)


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


3JK Edition 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

z Table lists the antenna port flange types, plus their mating flange options and fastening hardware for
remote mount installations. UDR/PDR flanges are rectangular; UBR/PDR flanges are square.
z 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.
z 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.
z All fastening hardware is metric.

3JK Edition 1.00
3.6 Grounding the ODU
z The one ground wire can be used to ground both the ODU and the
suppressor only in case a pressed-cover ODU is installed with a
suppressor support bracket.
z For all other set-ups, one ground wire must be installed to ground the
suppressor, and one to ground the ODU.

The ODU must be installed with a lightning surge suppressor. Failure to do so can invalidate the warranty.

3JK Edition 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 Edition 1.00
3.7 ODU external connectors [cont.]
z 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 Edition 1.00
z Which modulations are supported in the ODU?
z Which is the maximum length of the IF cable?
z Can the ODU be directly connected to the antenna?
z When must be used the RSSI monitoring point?


3JK Edition 1.00
End of Module
ODU HW Hardware Architecture


3JK Edition 1.00
Section 3
NE operation
Module 1
Operator interface
3JK Edition 1.00

3JK Edition 1.00
Blank Page

NE operation · Operator interface
Document History

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
Page
Blank Page 8
1 Network Element Overview 9
1.1 Main View 10
1.2 NE Configuration area 11
1.2.1 NE Information 12
1.2.2 NE Description 13
1.2.3 Command Buttons 14
1.3 Status & Alarms area 15
1.4 Supervision Function 16
1.5 Menu Bar 17
1.6 Suggested sequence for NETO interface and NE list 19
Blank Page 20
2 Main View 21
2.1 Main view 22
2.2 Main Tool Bar Area 25
2.3 Severity Alarm Panel 26
2.4 Domain Alarm Synthesis Panel 27
2.5 Management State Control Panel 28
2.6 Selection Criteria 29
2.7 Button Policy 30
3 Menu Configuration 31
3.1 Menu Configuration 32
3.2 Menu NE Time 33
3.3 Menu Network Configuration 34
3 · 1 · 5 3.3.1 Local Configuration All Rights Reserved © Alcatel-Lucent 2009 35
3.3.2 NTP
Configuration
9500 MPR · 9500MPR R 1.2.1 Operation and Maintenence 36
3.3.3 IP Static Routing Configuration 37
3.3.4 OSPF Area Configuration 39
3.3.5 Routing Information 41
3.4 Menu System Settings 42
3.5 Menu Cross Connections 43
3.5.1 Connectors 44
3.5.2 Graphical Area 46
3.5.3 Buttons 47
3.5.4 Segregated port view 48
3.5.5 How to segregate slots or ports 49
3.5.6 How to create a cross-connection 51
3.5.7 Creation Dialogs 54
3.5.8 Information Dialogs 55
3.5.9 Possible Cross-Connections 56
3.5.10 PDH – Radio 57
3.5.11 Radio - Radio 59
3.5.12 Radio - Ethernet 62
3.5.13 PDH - Ethernet 65
3.5.14 Cross-Connections with TDM2Eth Profile 67
3.5.15 How to modify a cross-connection 70
3.5.15.1 PDH-Radio 71
3.5.15.2 Radio-Radio 72
3.5.15.3 Radio-Ethernet 73
3.5.15.4 PDH-Ethernet 74
3.6 Menu VLAN Configuration 75
3.6.1 802.1D 76
3.6.2 802.1Q 77
3.6.2.1 VLAN 1 Management 78
3.6.2.2 VLAN Table Management 79

3JK Edition 1.00
Page
3.7 Menu Profile Management 81
3.7.1 User Profiles Management 82
3.7.2 User Management 83
3.7.3 How to Create a New User 84
3.7.4 How to Delete a User 86
3.7.5 Change the Password (by the Administrator) 87
3.7.6 Change Password (by the User) 88
4 Menu Diagnosis 89
4.1 Menu Diagnosis 90
4.2 Alarms 91
4.2.1 File Menu 97
4.2.2 Filters Menu 98
4.2.2.1 Add a Filter … 99
4.2.2.2 Delete Filters ... 100
4.2.2.3 Save Filters As ... 101
4.2.2.4 Load Filters From ... 102
4.2.3 Help Menu 103
4.3 Log Browsing 104
4.3.1 Event Log Browser 105
4.3.1.1 File Menu 107
4.3.1.2 Help Menu 110
4.4 Remote Inventory 111
4.5 Abnormal Condition List 112
4.6 Summary Block Diagram View 113
3 · 1 · 6 4.6.1 Main Block diagram view All Rights Reserved © Alcatel-Lucent 2009 114
4.6.2 PDH
unit secondary
9500 MPR · 9500MPR R 1.2.1 Operation and Maintenence view 115
4.6.3 Radio unit secondary view 119
4.7 Current Configuration View 125
Blank Page 126
5 Menu Supervision 127
5.1 Menu Supervision 128
5.2 Access State 129
5.2.1 Requested (Switching OS CT access state) 130
5.2.2 OS (Switching CT access state OS) 131
5.2.3 LAC Time Out Period 132
5.3 Restart NE 133
5.4 SW Licence 134
6 Tab-panel Equipment 135
6.1 Starting From Scratch 136
6.2 Tab panels in the Resource Detail Area 137
6.2.1 Alarms tab-panel 138
6.2.2 Settings tab-panel 139
6.2.2.1 Equipment Type 140
6.2.2.2 Protection Type 141
6.2.3 Remote Inventory tab-panel 143
Blank Page 144
7 Tab-panel Protection Schemes 145
7.1 General 146
7.2 EPS Management 148
7.2.1 Protection Schema Parameters 149
7.2.2 Commands 150
7.3 RPS Management 151
7.3.2 Commands 153
7.4 HSB Protection Management 154
7.4.2 Commands 156

3JK Edition 1.00
Switch to notes view! Page
8 Tab-panel Synchronization 157

8.1 Menu Synchronization 158
8.2 How to synchronize 159
Blank Page 162
9 Tab-panel Connections 163
9.1 Menu Connections 164
10 PDH view for PDH domain 165
10.1 PDH Unit configuration 166
10.1.1 Alarms tab-panel 168
10.1.2 Settings tab-panel 169
Blank Page 170
11 Radio view for Radio domain 171
11.1 Radio domain menu 172
11.2 Settings 173
11.2.1 Direction area 174
11.2.1.1 Mode 175
11.2.1.2 Link Identifier Configuration 184
11.2.1.3 PPP RF 185
11.2.2 Channel area 186
11.2.2.1 Frequency 187
11.2.2.2 ATPC 188
3·1·7
11.2.2.3 Manual Transmit Power Control
189
11.2.2.4 Tx Mute
192
11.2.2.5 Alarm Profile 193
11.3 Measurement 194
11.3.1 How to read a Power Measurement file 197
11.4 Loopback 198
11.4.1 How to activate a loopback 199
11.4.2 How to remove a loopback 200
12 Core-E view for Core-E and Ethernet domain 201
12.1 Core-E domain 202
12.1.1 Ethernet Physical Interface 203
12.1.1.1 Alarm tab-panel 205
12.1.1.2 Settings tab-panel (for Ethernet Port#1 to Port#4) 206
12.1.1.3 Settings tab-panel (for Ethernet Port#5) 207
12.1.2 TMN Interface 208
12.1.2.1 TMN Ethernet port 209
12.1.2.2 Port #4 TMN Ethernet 210
End of Module 212

3JK Edition 1.00
Blank Page


3JK Edition 1.00
1 Network Element Overview


3JK Edition 1.00
1.1 Main View
z When NETO starts, the main view screen is shown below.
z This screen has two 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.
z “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.

z The Network Element Overview (NETO) is the starting point of the CT application.
z NETO functions require to know the NE identity by means of the related IP Address.
z Only one NE can be managed in a NETO session.
z NETO Main view can also be minimized by using the shrink glass ( ) button in the Menu Bar.
z The magnifying glass ( ) button allows to show the normal NETO main view.
z The alarm severity icon appears in operating system “tray bar”, close to system clock and other system
software icons.
z 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. 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
1.2 NE Configuration area
z 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
1.2.1 NE Information
z This area is related to the wanted NE identification.
z “IP Address” field displays the actual NE IP address used by NETO

functions.

z “OK” button will start supervision on specified NE, if reachable. Keyboard shortcut “Alt + o” behaves as
clicking on “OK” button with mouse.
z 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
1.2.2 NE Description
z This area contains some parameters displaying general information

about the supervised NE.
z Parameters can be read and modified (and applied to NE using the

“Apply” button).

z 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
1.2.3 Command Buttons
z Command buttons available through NETO are:
z “Show” button will start WebEML (JUSM/CT) application on a

supervised NE.
z “Alarm Monitor” button starts AM application. Both buttons will be
enabled when NE is supervised only.
z “Exit” button will close NETO, stopping a possibly running supervision
and closing all related applications.

z 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
1.3 Status & Alarms area
z Information on supervision status and active alarms are shown in this

area.

z Round-shaped icons change their colours according to current NETO functions and situation. With respect to
“Supervision” status:
z green colour means that supervision function is ongoing,
z red colour means that NE link does not work,
z gray icons mean that supervision is not active (to be started).
z 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
1.4 Supervision Function
z The supervision function allows operator registering a new manager

inside NE MIB and performing cyclic (periodic) monitoring on
connection.
z To start supervision, the operator must specify NE IP address in the “IP
Address” field and then simply press “OK” button.
z 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.
z 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.
z 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
1.5 Menu Bar
z (New)
z (Open)
z (Magnifying glass)
NETO Main view can also be minimized by using the shrink glass ( ) button.
z Using both (New) and (Open) icons, the operator will be able to
open NEs table modal window (see following Figure).
z “Open” icon allows opening a previously saved file containing a list of
NEs.
z “New” icon allows creating a new list, specifying the file name
containing its data, only when those data will be saved.

z NETO can manage and organize a list of available NEs by showing operator a table containing such data.

3JK Edition 1.00
1.5 Menu Bar [cont.]
NETO List Management

z “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;
z “New” button, adding a new NE from scratch. This allows the operator to fill the “IP Address” field only
with its needed NE.
z “Remove” button, removing a selected NE;
z “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;
z “Save” button, saving table list in a specified file.
z To close this window click on “Close” button.
z 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.
z The operator can have its own NEs lists repository, containing all .NETO files that it produced with NEs
information inside.

3JK Edition 1.00
1.6 Suggested sequence for NETO interface and NE list
z 1. Fill NETO main view “IP Address” field with NE IP address;

z 2. Start supervision by clicking “Ok” button;
z 3. Open the NEs table (any method, through “New” or “Open” button);
z 4. Click on “Get Current”;
z 5. “Save” the list and “Close” the list window.

z 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
Blank Page


3JK Edition 1.00
2 Main View


3JK Edition 1.00
2 Main View
2.1 Main view
z Two Main views are possible according to the MSS version:
MSS-8
MSS-4


3JK Edition 1.00
2 Main View
2.1 Main view [cont.]
z MSS-8
Domain Alarm
Synthesis Panel

z 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.
z Tab-panels
z Each tab-panel represents a set of functions. The following tab-panels are present:
z Equipment (to manage the equipment configuration)
z Protection Schemes (to manage the protection schemes in 1+1 configuration only)
z Synchronization (to manage the synchronization)
z Connections (to manage the cross-connections)
z Each tab-panel consists of three areas:
z Resource-Tree Area: displays all the available resources of the NE.
z 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.
z 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.
z Figure (Main view) is the entry point of the application and provides basic diagnostic and configuration functions. Following multiple
main views are available:
z Equipment view, for Equipment configuration;
z Radio view, for Radio domain (double click on a Radio unit);
z PDH view, for PDH domain (double click on a PDH unit);
z Core-E view, for Core-E and Ethernet domain (double click on a Core-E unit).
z 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.
z Other icons are:
z 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.
z 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 Main View
2.1 Main view [cont.]
z MSS-4
Domain Alarm
Synthesis Panel

z 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.
z Tab-panels
z Each tab-panel represents a set of functions. The following tab-panels are present:
z Equipment (to manage the equipment configuration)
z Protection Schemes (to manage the protection schemes in 1+1 configuration only)
z Synchronization (to manage the synchronization)
z Connections (to manage the cross-connections)
z Each tab-panel consists of three areas:
z Resource-Tree Area: displays all the available resources of the NE.
z 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.
z 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.
z Figure (Main view) is the entry point of the application and provides basic diagnostic and configuration functions. Following multiple
main views are available:
z Equipment view, for Equipment configuration;
z Radio view, for Radio domain (double click on a Radio unit);
z PDH view, for PDH domain (double click on a PDH unit);
z Core-E view, for Core-E and Ethernet domain (double click on a Core-E unit).
z 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.
z Other icons are:
z 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.
z 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 Main View
2.2 Main Tool Bar Area
z 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
VLAN management: opens the VLAN Management menu
Performance Monitoring Tool: opens the Performance Monitoring Tool
menu


3JK Edition 1.00
2 Main View
2.3 Severity Alarm Panel
z 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).
z 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.
z 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.
z 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.
z An alarm icon with a rectangle inside it indicates that no alarms of the type defined by
the icon are occurring.
z An alarm icon grayed out indicates that spontaneous incoming alarm notification have
been inhibited.

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

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


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

represented via icons located in the top right corner of the equipment
views.
z 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.

z 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.
z The meaning of the icons in the Management State Control Panel is:
z 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).
z 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).
z 3) SUP – Supervision state
} GREEN LED: NE is under supervision
} BROWN LED: NE is not under supervision
} Used in the OS.
z 4) OS – OS isolation
z 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.
z 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 Main View
2.6 Selection Criteria
z 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.
z Each resource listed above may be selected by using the mouse by a:
Single left click:
y 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:
y 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 Main View
2.7 Button Policy
z The possible buttons for selection are the following:
Apply
y this button activates the “modify”, but it does not close the window.
Cancel
y this button closes the window without modifying the parameters displayed in the
window.
OK
y this button activates the modify and closes the window
Close
y this button closes the window
Help
y 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
z Menu Configuration is divided in:
NE Time
Network Configuration
Alarm Severities (not implemented in the current release)
System Settings
Cross Connections
VLAN Configuration
Profile Management


3JK Edition 1.00
3.2 Menu NE Time

z Note: The NTP Status field is not implemented.

z The NE local time can be displayed and/or re-aligned to the OS time basis.
z From the Configuration pull down menu, select the NE Time option.
z The dialogue box opens, from which you can set the local NE time.
z The NE Time dialogue box displays the current NE time and the current OS time.
z 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.
z The Refresh pushbutton causes the refresh of the screen.
z 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.
z The NTP Status field shows:
z status of NTP (enabled/disabled);
z IP address of the Main Server, which distributes the time to all the NEs in the network;
z IP address of the Spare Server (if any), which replaces the Main Server in case of failure.

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

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


3JK Edition 1.00
3.3.1 Local Configuration
z Select the Network Configuration option and then, from the cascading
menu, the Local Configuration option.
z The dialogue box opens, which allows to configure the local IP address
of the NE.
z 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).
z Default IP address: 10.0.1.2
z Default mask: 255.255.255.255

z 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.
z Close button closes the dialogue.
z Help button provides some useful information on the dialogue.

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

z 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.
z The Server reachability field is a read-only field, which shows the reachability of the NTP servers. The
following information can appear:
z "Main server reachable"
z "Spare server reachable"
z "None servers reachable"
z "Both servers reachable"
z Click on Refresh to update the screen.
z Click on Apply to send to the NE the NTP Configuration.

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

allows to configure the parameters for IP Static Routing Configuration.
z The following fields and data are present:
IP Address: allows to define the IP address necessary to reach a specific Host
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.
z By pressing Create pushbutton another screen opens.
z 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.
z 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 (NMS-RF)

z WARNING: No pending (open) static routes are allowed.

z The default software uses first the static routes and then the dynamic routes. An open static route is always
considered as a preferential path.
z 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.
z If in screen the Point To Point Interface Index check box has been selected another screen opens.
z 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.
z New button is used to insert a new page.
z Delete button is used to delete the selected page.
z Close button closes the dialogue without changing of the data.

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


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

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

z 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.
z New button is used to insert a new page.
z Delete button is used to delete the selected page.
z Close button closes the dialogue without changing of the data.
z WARNING: When the area is a Stub area, all the interfaces (NMS and Ethernet) must be defined “Stub".
z By pressing Create pushbutton a new screen opens.
z N.B. 3 areas max. can be created.
z 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
z 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.

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

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

some parameters for the NE setup.
z The NE configuration tab-panel
has 6 fields:
Tributary Port Configuration
Quality Of Service
DHCP
Admission Control for
Adaptive Modulation
Event and Alarm Log
NE MAC Address

z 1) Tributary Port Configuration

z 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.
z 2) Quality Of Service
z This field allows to set the suitable Quality Of Service (Disabled/DiffServ/802.1p). To activate the new value, click on Apply.
z 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.
z 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;
z 3) DHCP
z The DHCP server configures automatically IP address, IP mask and default gateway of the PC Ethernet interface used to reach the
NE.
z The PC must be configured to get automatically an IP address.
z The DHCP server uses an address pool of only one IP address, defined according to the NE Ethernet port IP address:
} NE Ethernet port IP address plus one, if this address is not a direct broadcast address,
} otherwise NE Ethernet port IP address minus one.
z The IP mask is set to the mask of the NE local Ethernet port and the default gateway is set to the NE IP address.
z The lease time is fixed to 5 minutes.
z To activate the DHCP server, select Enabled and click on Apply.
z 4) Admission Control for Adaptive Modulation
z The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive Mod-ulation) can be enabled or
disabled. Default: “Enabled”.
z 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.
z 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).
z Warning: The disabling of the Admission Control can be done in 1+0 configuration only.
z 5) Event and Alarm Log
z As default the Logging is enabled. If set to "Disabled" the events are not sent to the Event Log Browser application.
z 6) NE MAC Address
z 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.5 Menu Cross Connections

z Note: Ethernet port#5 will appear only if the optional optical 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.
z 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:
z There are a maximum of 5 Ethernet ports placed on the bottom, ordered from 1 to 5 from left to right.
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 is visible if in the Core-E unit has been installed and enabled the SFP optical plug-in.
z There are a maximum of 6 (PDH/Radio) slots (placed as in the MSS sub-rack).
z 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).

3JK Edition 1.00
3.5.1 Connectors
z 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.
z The connectors have different colours depending on the associated

slot’s state:
White: a connector, in a cross-connection, which is 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 that is not able to accept a cross-connection.


3JK Edition 1.00
3.5.1 Connectors [cont.]
z 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.5.2 Graphical Area

z 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.
z Some steps would differ depending on cross-connection types.

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

Apply: will apply changes (if any) to NE. After they’ve been applied it will
update graphical state by performing a refresh; if the operation completes
without errors the sub-sequent refresh won’t 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.5.4 Segregated port view
z From the Cross Connection view by pressing Alt+W the Segregated Port
view opens.

z 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).
z To go back to the Cross Connection View press Alt+W.

3JK Edition 1.00
3.5.5 How to segregate slots or ports
z 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).
z Example: with a double click on the icon of Slot#7 RADIO figure opens.
z To segregate Slot#7 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.5.5 How to segregate slots or ports [cont.]
z By clicking OK the Segregated Port view opens, which now shows (with
dashed lines) the segregated ports.

z 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.5.6 How to create a cross-connection
z 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.5.6 How to create a cross-connection [cont.]
Cross-connections Example

z 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:
z Slot#8 PDH is cross-connected to Slot#7 radio;
z Slot#4 PDH is cross-connected to Slot#7 radio;
z Slot#3 PDH is cross-connected to Ethernet Port#1;
z Slot#5 RADIO (and Slot#6 RADIO) are cross-connected to Ethernet Port#2;
z Slot#8 PDH is cross-connected to Ethernet Port#4;
z Slot#4 PDH (blue) could not accept more cross-connections;
z Slot#3 PDH (green) could accept more cross-connections;
z Radio slots#5 and #6 (green) could accept more cross-connections.

3JK Edition 1.00
3.5.6 How to create a cross-connection [cont.]
z Legenda
PDH-Radio connection
PDH-Eth connection
Radio-Eth line
Actual colored view example

z Each connection line is coloured according to slots types it connects (as shown in figure):
z PDH-Radio connection: black line;
z PDH-Eth connection: blue line;
z Radio-Radio connection: red line;
z Radio-Eth line: green line.
z These colours will be applied to the graphical area, when the operator releases the mouse button above
cross-connection destination slot. All the lines appears as solid.

3JK Edition 1.00
3.5.7 Creation Dialogs
z 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.
z The “Ok” button will visually save the current modifications (this
means that data are graphically saved only, not sent to the NE!)
z The “Cancel” button will graphically discard ongoing cross-connection,
keeping the previous graphical.


3JK Edition 1.00
3.5.8 Information Dialogs
z 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.5.9 Possible Cross-Connections
z The Cross-connections to be implemented are:

PDH-Radio
Radio-Radio
Radio-Eth
PDH-Eth
z 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.5.10 PDH – Radio
z By dragging a connection between a PDH slot and a radio slot, the

operator will see the configuration dialog in the Figure.
PDH-Radio configuration dialog

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

3JK Edition 1.00
3.5.10 PDH – Radio [cont.]
z Once correctly completed the cross-connection configuration and

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


3JK Edition 1.00
3.5.11 Radio - Radio
z By dragging a connection between two different radio slots, the operator can see the
configuration dialog in Figure.
z To create other cross-connections drag other lines between the two radio slots and
repeat the operations.
Radio-Radio configuration dialog


3JK Edition 1.00
3.5.11 Radio - Radio [cont.]
z 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.
z 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.
z 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.
z 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.5.11 Radio - Radio [cont.]

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


3JK Edition 1.00
3.5.12 Radio - Ethernet
z By dragging a connection between a Radio slot and an Ethernet port,

the operator will see the configuration dialog in Figure.
Radio-Ethernet configuration dialog (ranges)


3JK Edition 1.00
3.5.12 Radio - Ethernet [cont.]
z 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-Ethernet configuration dialog (values)

z 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.
z Once correctly completed the cross-connection configuration and clicked on “OK” button, the operator will
be able to see a green line describing the Radio-Ethernet cross-connection defined.

3JK Edition 1.00
3.5.12 Radio - Ethernet [cont.]
Completed Radio-Ethernet cross-connection


3JK Edition 1.00
3.5.13 PDH - Ethernet
z By dragging a connection between a PDH slot and an Ethernet port, the

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

z 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.5.13 PDH - Ethernet [cont.]

clicked on “OK” button, the operator can see a green line describing
the PDH-Ethernet cross-connection defined (see Figure).
Completed PDH-Ethernet cross-connection


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

z 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.5.14 Cross-Connections with TDM2Eth Profile [cont.]
z 1+1 EPS protection in NE A


3JK Edition 1.00
3.5.14 Cross-Connections with TDM2Eth Profile [cont.]
z 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.

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

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

the left mouse button on its symbolic line.
z 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.5.15.1 PDH-Radio

z In figure the operator is modifying a previously created cross-connection (in this case Slot#7 PDH and Slot#5
radio): this action brings up a dialog almost like the creation one, but with some differences in allowed
actions:
z Previously assigned tributaries (703 in the example) are active and selected;
z Tributaries assigned to another cross-connection (706, 709 and others) are not active and not selected.

3JK Edition 1.00
3.5.15.2 Radio-Radio

z 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.
z Remove the check mark and create again a cross-connection.

3JK Edition 1.00
3.5.15.3 Radio-Ethernet

z 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.5.15.4 PDH-Ethernet

z The operator can click on specific (blue) 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 Menu VLAN Configuration
z Two different ways to manage the Ethernet traffic are allowed:

802.1D (MAC Address Bridge)
802.1Q (Virtual Bridge)


3JK Edition 1.00
3.6.1 802.1D

z 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.
z 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.6.2 802.1Q

z When the NE is configured in this mode, the management of Ethernet traffic looking the VLAN is enabled.
z In this modality, one VLAN will be assigned to all Ethernet frames inside the MPR network.

3JK Edition 1.00
3.6.2 802.1Q
3.6.2.1 VLAN 1 Management
z VLAN-ID 1 is automatically defined by the NE when the 802.1Q bridge

type is selected.
z VLAN-ID 1 is shown to the operator, but it cannot be neither changed
nor deleted.
z All the user Ethernet ports (enabled and disabled) and all the radio
ports are members of the VLAN 1.
z In egress VLAN-ID 1 is always removed from all the ports.

z New: to create a new VLAN (refer to VLAN table management)

z Edit: to change the parameters of a VLAN (VLAN name, VLAN member ports, VLAN untagged ports in egress).
z 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.
z Export: to export the VLAN configuration in a file with extension CSV. The file can be stored in the PC to be
read later.
z 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.
z Clear Filter: by clicking this button all the VLAN created in VLAN table will again appear.
z Refresh: the VLAN table is updated.

3JK Edition 1.00
3.6.2 802.1Q
3.6.2.2 VLAN Table Management
z To create a VLAN follow the following instructions.

z 1) VLAN ID field: Enter the VLAN ID (the configurable values must be in the range 2 - 4080)
z N.B.: The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) cannot be
used.
z 2) VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.
z N.B.: There is no check on unambiguity name.
z 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.
z 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).
z 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.
z 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.6.2 802.1Q
3.6.2.2 VLAN Table Management [cont.]
z In the following figure, as example, three VLANs have been created

(VLAN 2, 3 and 4).

z N.B.: When a board, on which there is at least one port member of a VLAN, is declared by the operator as
no more expected in the current slot position, the management system advises the operator that there are
ports on the board member of a VLAN, asking confirmation of the operation. If confirmed, the port(s) are
automatically removed by the NE from the list of ports member of the VLAN and from the list of the
untagged ports in egress.

3JK Edition 1.00
3.7 Menu Profile Management
z 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
z The operator has to insert the user name and related password: by
clicking on the Apply button, the parameters are sent to NE.

z The default Operator Name is “initial”.

z The default Password is “adminadmin”.
z 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.
z 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.
z WARNING: The NE rejects usernames and passwords that do not meet the following rules:
z Password length: the length must be not less than eight (8) characters under any circumstances.
Moreover the password length must be not longer than 20 characters.
z Password composition: the password can include full ASCII characters set (UPPER/lower case, numeric
and special characters).
z Username length: the length must be not longer than 20 characters.
z By clicking on the Cancel button, the login procedure is stopped and the JUSM does not start.

3JK Edition 1.00
3.7.1 User Profiles Management
z If the operator right allows the profiles management, the operator can
perform some actions on the profiles.
z Under Configuration menu, the Profiles Management menu displays
two items:
Users Management
Change Password
z These items will be enabled according to the right of user profile
recognised at login.


3JK Edition 1.00
3.7.2 User Management
z By clicking on Users Management the window displayed in the Figure

appears.
z The operator can perform the following actions:
Create a new User by clicking on the Create button.
z After the selection of a user in the table, it’s 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.

z By clicking on the Cancel button the Profiles Management window closes.

z 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.7.3 How to Create a New User
z 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.7.3 How to Create a New User [cont.]
z 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.

z The supported profiles are:

z Administrator: full access also for security parameters
z 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
z 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
z Viewer: only to explore the NE
z Supported operations by the profiles:
z 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).
z Operator profile: Full reading access to NE parameters. For writing mode the following parameters are allowed to
change:
} ATPC configuration (not implemented)
} Performance Monitoring management
{ start/stop CD
{ threshold tables configuration
{ reset
{ archiving (only for NMS system)
z CraftPerson profile: This operator has the same priviledges of the Administrator, but cannot manage the user
accounts
z Viewer profile: This operator can only read and can change his own password.
z 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.
z By clicking on Cancel button, the Create User window closes and no action will be performed.

3JK Edition 1.00
3.7.4 How to Delete a User
z 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

z By clicking on the Apply button, a message with the result action will be displayed after to have closed
automatically the window above.
z If the operator clicks on Cancel button the window will closes and no action is performed.

3JK Edition 1.00
3.7.5 Change the Password (by the Administrator)
z 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
z The admin has to insert his password and the new password for
selected user in the two text fields.

z 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.
z By clicking on Cancel button, the window will be closed.

3JK Edition 1.00
3.7.6 Change Password (by the User)
z If the operator wants to change his password, he has to select the

Change Password menu item.
z The following dialog will be displayed:
Change User Password
z The operator has to insert the current password and the new password
in the two text fields.

z 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.
z By clicking on Cancel button, the window closes.

3JK Edition 1.00
4 Menu Diagnosis


3JK Edition 1.00
4 Menu Diagnosis
4.1 Menu Diagnosis
z Menu Diagnosis is divided in:
Alarms
Log Browsing
Remote Inventory
Abnormal Condition List
Summary Block Diagram View
Current Configuration View


3JK Edition 1.00
4 Menu Diagnosis
4.2 Alarms

z Alarms Monitor is an application which allows to display and store the alarms of all the NEs requiring it.
z 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.]
z 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).
z 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).
z For each list and for each filter, the number of active alarms is shown
inside brackets.
z These two lists can be filtered using customized filters provided by
means of the menu Filters → Add a Filter.

z Note: When an alarm is no longer active it disappears from the two global lists and it is displayed in the
ALARM_LOG list as a cleared alarm.

3JK Edition 1.00
4 Menu Diagnosis
4.2 Alarms [cont.]
z 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.
z At the top right, the field Synthesis shows the number of active alarms
for any severity.
z 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).

z 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.]
z 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: not available.
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.]
z Right-clicking on an alarm row opens the menu shown in the following

figure.

z 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.
z 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 and XML.
z 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.
z Select: to select all the alarm of the list (All) or to select none (None) for further use, e.g. to export alarms
to a file.

3JK Edition 1.00
4 Menu Diagnosis
4.2 Alarms [cont.]
z The Menu Bar provides the following menus:
File
Filters
Help


3JK Edition 1.00
4.2 Alarms
4.2.1 File Menu
z Save Log for selected NE

z 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.
z Load Log to selected NE

z By means of this menu it is possible to display the global list of a
certain NE previously saved.
z Export Alarms
z 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 or HML) and then assign the name of the file.


3JK Edition 1.00
4.2 Alarms
4.2.2 Filters Menu
z The Menu Filters provides the following menus:
Add a Filter …
Delete Filters …
Save Filters As …
Load Filters From …


3JK Edition 1.00
4.2.2 Filters Menu
4.2.2.1 Add a Filter …
z This menus allows to create customized logs adding some new specific
filters. The windows which opens is shown below.

z Filter Name field

z Enter the filter name in the Filter Name field.
z 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.
z Scope field
z Select APT (Current) to create a filter showing the current alarms only or select Log to create a filter for current and
cleared alarms.
z 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.
z Alarm Type field
z Select Alarm Type to create a filter for the selected type of alarm:
} TRS = Transmission Alarm
} EQUIPMENT = Equipment alarm
z Perceived severity field
z Select Perceived severity and then one or more severity levels and/or Cleared state to filter the alarm having the
selected severity levels.
z Event Time field
z 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.
z Probable Cause field
z Select Probable Cause and the choose a specific alarm (one or more) to filter these particular alarms only.
z Resource field
z 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.2 Delete Filters ...
z When this menu is selected, the window shown below opens.

z By means of this menu the filters previously created can be canceled. Default filters cannot be canceled.
z 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.
z Clicking on the Cancel pushbutton all the selections are cleared.

3JK Edition 1.00
4.2.2 Filters Menu
4.2.2.3 Save Filters As ...
z 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.

z 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.
z Clicking on the Cancel pushbutton all the selections are cleared.

3JK Edition 1.00
4.2.2 Filters Menu
4.2.2.4 Load Filters From ...
z A filter previously saved can be loaded on the LCT by means of the

following menu.

z 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.
z 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
z This menu shows the Product Version.


3JK Edition 1.00
4 Menu Diagnosis
4.3 Log Browsing
z In the Diagnosis pull-down menu select the Log Browsing option.
The Alarm Log option is not available in the current release.
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
z 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.

z The following information is provided for each event:

z Time: date and time of occurrence of the event. The format is week day/month/day hh:mm:ss.
Reference Time (CEST) year.
z Notification ID: a unique identifier for the event.
z 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.]
z The Menu Bar provides the following menus:
File
Help


3JK Edition 1.00
4.3.1.1 File Menu
z The Menu File makes available the following menus:

Refresh Tables
Export
Print
Exit
z 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.]
z 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.]
z 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
z This menu shows the Product Version.


3JK Edition 1.00
4 Menu Diagnosis
4.4 Remote Inventory
z 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
z The Abnormal Condition List option in the Diagnosis menu displays all
the abnormal conditions currently active in the NE.
z 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).

z The list of the events which cause an abnormal condition:

z Forced switch (EPS, RPS, TPS)
z Lockout (EPS, RPS, TPS)
z Loopback activation
z Local radio Tx mute (manual)
z Adaptive Modulation in normal mode

3JK Edition 1.00
4 Menu Diagnosis
4.6 Summary Block Diagram View
z 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
z The Figure shows an example of the Main block diagram view.

z Each block has its Alarm indicator (coloured ball icon) that shows the alarm status (different colors
according to the alarm severity).
z In the Main view the current configuration of the PNU is shown, with the equipped units (PDH or Radio),
with the protection schemes and with the cross-connections implemented between the different units and
the different Ethernet ports, if any.
z On the RADIO 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 the symbol because it is possible to
activate 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.
z By clicking on an object it s possible to navigate to specific views. In detail:
z by clicking on the Abnormal Condition List box, it is possible to navigate to the Abnormal Condition List
menu;
z by clicking on the NMS Interfaces box, it is possible to navigate to the NMS view in the Core-E unit;
z by clicking on the Ethernet icon in the Cross Connection Matrix, it is possible to navigate to the Ethernet
port view in the Core-E unit;
z by clicking on a PDH slot icon in the Cross Connection Matrix, it is possible to navigate to the secondary
view for the PDH unit;
z by clicking on a Radio slot icon in the Cross Connection Matrix, it is possible to navigate to the secondary
view for the Radio unit;
z 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.
z 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.
z The green line is the current active path.

3JK Edition 1.00
4.6.2 PDH unit secondary view
z 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)


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 Radio unit secondary view
z Depending on the configuration, different diagrams are shown to the

operator, describing the actual NE status and working mode.
1+0 block diagram (Radio unit) (without Core-E protection)

z Loopback icons ( ) are shown in green colour ( ) whenever a loopback is active.

z Performance monitoring icons ( ) are shown in green whenever a PM is active.
z By clicking on the Performance Monitoring icon ( ) the navigation to the Performance Monitoring tool
starts.
z Ethernet Counters icon ( ) is shown in green whenever the counter has been activated.
z By clicking on the Loopback icon, on the PM icon or on the Ethernet Counters icon the navigation to the
relevant menus starts.
z Switch block (“EPS Core”, “RPS TX”, “RPS Rx”, …) are updated according to the signal path, following light
green-coloured line.

3JK Edition 1.00
4.6.3 Radio unit secondary view [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 Menu Diagnosis
4.7 Current Configuration View

z This view is a read-only screen, which shows the current configuration of the NE.

3JK Edition 1.00
Blank Page


3JK Edition 1.00
5 Menu Supervision


3JK Edition 1.00
5 Menu Supervision
5.1 Menu Supervision
z Menu Supervision is divided in:
Access State
Restart NE
MIB Management (not implemented in the current release)
SW Licence


3JK Edition 1.00
5 Menu Supervision
5.2 Access State
z 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.
z 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.
z 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.
z If the LAC is “requested”, it means that the CT has requested a
permission from the OS and is waiting for a replay.
z 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.
z 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)
z Select the Supervision pull down menu. Then select the Requested
option from the Access State cascading menu.
z 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)
z Select the Supervision pull down menu. Then from the Access State
cascading menu select the OS option.
z The NE is now managed by the OS.

z 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.
z 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.2 Access State
5.2.3 LAC Time Out Period
z When the CT operator asks to the OS to access to the NE (by pressing

“Requested”) after the time set in this screen, the CT gets the control
and enters in the state “LAC Requested” only if OS cannot reach the
NE.
z With the Refresh button it is possible to see the time which has been
previously set.


3JK Edition 1.00
5 Menu Supervision
5.3 Restart NE
z The Restart operation is a software reset and can be executed in

normal traffic conditions.
z From the Supervision cascading menu, select the Restart NE option.
z A dialogue box opens.
z Click the Yes button to confirm the restart NE operation
z Click the No button to abort the restart NE operation.

z 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 SW Licence
z 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.

z The Refresh button activates a new reading of the read-only fields.

3JK Edition 1.00
6 Tab-panel Equipment


3JK Edition 1.00
6.1 Starting From Scratch
z 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.
z Icon is used to identify an empty slot.

z To configure a card:
z Select a slot.
z Click on Settings panel.
z Select the correct type of unit.
z Click on Apply.
z Now in the MSS will appear the new card in the slot.

3JK Edition 1.00
6.2 Tab panels in the Resource Detail Area
z For every unit in the MSS there are 3 tab-panels:
Alarms
Settings
Remote Inventory


3JK Edition 1.00
6.2.1 Alarms tab-panel
z The Alarms tab panel provides the fault management, which checks the
current state of alarms related to the selected object.
z 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.
z 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.2.2 Settings tab-panel
z In the Setting tab-panel the following fields are present:
Equipment Type
Protection Type Configuration
Alarm Profile (not implemented)


3JK Edition 1.00
6.2.2.1 Equipment Type
z 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 equipment type and click Apply.
z The Setting tab-panel of the Core-E unit is shown here below.

Click on Apply on the Plug-in Type field to enable the SFP optional optical
plug-in, if the plug-in has been installed in the Core-E unit.


3JK Edition 1.00
6.2.2.2 Protection Type
z The operator can configure the NE protection type. This function is

shown selecting slots 3 to 8 only.
z For slots 1 and 2 (reserved to Main and Spare Core-E units) the
protection type is automatically configured by the system.
z 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”.
z Select the Protection type and click on Apply.

z 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).

3JK Edition 1.00
6.2.2.2 Protection Type [cont.]

z When a board shows the check mark ( ) icon, while same-pair (same-row) one shows switch symbol
( ), this means pair (row) is protected. In this situation, the couple is considered as if it is one board and
each single board cannot be removed/un-configured unless removing protection.
z Check mark icon ( ) denotes “active” board while switch one ( ) represents “stand-by” board.
z Same behaviour occurs when X-shaped icon ( ), representing cross-connections, appears. PDH board
cannot be removed as well when Flow IDs are configured. An error message will be shown if the operator
will try to perform such operations.

3JK Edition 1.00
6.2.3 Remote Inventory tab-panel
z The Remote Inventory feature stores information used to identify all

product components.
z 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 won’t 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
z 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: Radio 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.

z Note 1: For the pair of Core-E units (slot 1 and 2) the only protection type is the Equipment Protection.
z Note 2: For the pair of Radio units the protection type are the Equipment Protection, Radio Protection and
HSB Protection or FD protection.
z Note 3: For the pair of PDH units the only protection type is the Equipment Protection.

3JK Edition 1.00
7.1 General [cont.]
Protection scheme screen

z 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
z The Equipment Protection Management is performed by selecting the

Equipment Protection tree element.
z This window allows a complete view of all NE resource involved in the
EPS protection.
z The tab-panels are:
Protection Schema Parameters
Commands


3JK Edition 1.00
7.2 EPS Management
7.2.1 Protection Schema Parameters
z The tab-panel “Schema Parameters” displays the parameters that can

be modify.

z The parameters are:

z 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).
z 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.
z Note: The Core protection type is Revertive and cannot be changed.

3JK Edition 1.00
7.2 EPS Management
7.2.2 Commands
z To enter the Commands menu click on the Spare #0 element in the

Tree view or on the Main #1 element.
z 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.
z 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.
z 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.
z Automatic Switch is the normal operation condition: the position of
the switch depends on the commands generated by the logic.
z 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.

z Note:
z On the Main#1 channel the only available commands are Manual and Forced.
z On the Spare#0 channel the only available commands are Manual and Lockout.
z WARNING: the EPS Lockout command is not error free, even if it is raised when traffic is not on the spare
channel.
z 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.
z Command priority list
Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
z N.B. To release a previously activated command select None and click on Apply.

3JK Edition 1.00
7.3 RPS Management
z The Radio Protection Management is performed by selecting the Rx

Radio Protection element tree.
z This window allows a complete view of all NE resource involved in a
RPS protection.
Commands


3JK Edition 1.00
7.3 RPS Management
z The tab-panel “Protection Schema Parameters” displays the

parameters that can be modify.

z The Schema Parameters are:

z Protection Type field: defines the protection schema architecture: 1+1 hitless;
z 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
z To enter the Commands menu click on the Spare #0 element in the

Tree view or on the Main #1 element.
z 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.
of this command forces in service Channel 0, independently of the

z Note:
Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4

3JK Edition 1.00
7.4 HSB Protection Management
z The Transmission Protection Management is performed by selecting the

HSB Protection element tree.
z This window allows a complete view of all NE resource involved in the
protection.
Commands


3JK Edition 1.00
z The tab-panel “Protection Schema Parameters” displays the

parameters that can be modify.

z The Schema parameters are:

z 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.
z 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
z To enter the Commands menu click on the Spare #0 element or on the

Main #1 element in the Tree view.
z Lockout has higher priority than Forced: the activation connects to the
antenna Transmitter 1 (default transmitter), independently of the
of this command connects to the antenna Transmitter 0, independently
of the possible active alarms. This command activates signaling ABN.

z Note:
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

z Synchronization menu allows the operator to manage the synchronization features.

z Using “Synchronization” tab view (shown in the figure below) the operator can select and configure
synchronization source(s) for the equipment.
z 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.
z The Resource list area shows the configuration summary describing current synchronization.

3JK Edition 1.00
8.2 How to synchronize
z 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.
z The NEC also provides a Sync Out port on the Core-E Module, which can
be used to synchronize other NEs.
z The NEC is locked to a Synchronization Source.
z 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] Sync-In port is a specific synchronization input, which can be configured
according to the following options:
y a) 2.048 MHz, electrical levels according G.703, clause 13
y b) 5 MHz, + 6 dBm into 50 , sine-wave
y c) 10 MHz, + 6 dBm into 50 , sine-wave.
[4] Radio Port: Symbol Rate of the Rx signal of any available Radio direction
(the specific Radio Port has to be chosen)


3JK Edition 1.00
8.2 How to synchronize [cont.]


3JK Edition 1.00
8.2 How to synchronize [cont.]
z All the NEC has to be configured as Master Role or Slave Role.

z Only one Master is allowed in the network.
If Master Role,
y The Restoration Mode can be Revertive and Not Revertive
y The Primary sources must be chosen among 1), 2) or 3).
y 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.
y If the selected Master Primary Source is 2) or 3)
{ then Master Secondary Source must be selected among 1), 2) or 3).
If Slave Role,
y The Restoration Mode is fixed to Revertive.
y The Primary Source must chosen between 3) and 4)
{ Slave primary sources is allowed to be 3) for full indoor configuration and future Piling
configuration
y The Secondary Source can be chosen among 1), 2) or 3).

z Each Module will mute its own Synchronization clock in case of Fail Alarm.
z 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.
z 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
Blank Page


3JK Edition 1.00
9 Tab-panel Connections


3JK Edition 1.00
9 Tab-panel Connections
9.1 Menu Connections

z This menu (available in the Main view) contains a summary table for all the implemented cross-connections.
This menu is shown in the figure.
z In the Resource Detail Area are available two different functions usable to export and save cross-
connections data with different formats:
z hardcopy (Send To Printer);
z file (Export To File).

3JK Edition 1.00
10 PDH view for PDH domain


3JK Edition 1.00
10.1 PDH Unit configuration

z This menu opens with double click on a PDH unit in the Equipment tab-panel.
z In the Resource List Area is given the information related to the tributaries:
z 1) Port Number: port for a given channel and type of port
z 2) Signal Mode: type of frame (Framed/Unframed/Disabled)
z 3) Flow Id: identifier of the tributary for the cross-connection
z 4) Service Profile: possible profile to be associated to the tributary (TDM2TDM/TDM2Eth)
z 5) Payload: bytes of the payload (256)
z 6) ECID Tx: Emulated Circuit Identifier in Tx direction
z 7) ECID Rx: Emulated Circuit Identifier in Rx direction
z 8) TDM Clock source: type of the clock to be associated to the tributary (Adaptive/Differential/Tdmline)
z 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.]
z 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
z The Alarms tab panel provides the fault management, which checks the
current state of alarms related to the selected object.
z 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.
z 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.
z 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
z This tab-panel 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 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.

z Warning: to change something in the Settings tab-panel first changes the Signal Mode to Unframed. After
this, all the other fields can be changed.
z In the Setting tab-panel there are the following fields:
z Port Number: identifies the ports for a given interface and type of port (read-only fields)
z Signal Mode. The possible values are:
} Unframed for the unframed received signal
} 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.

z 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.
z Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if the Service Profile is
TDM2Eth.
z 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.
z Alarm profile: Not implemented now.
z Buttons:
z Apply: the configuration for the selected E1 tributary will become active
z Apply to All: the configuration present in the screen will be applied to all the ports.
z Help: by clicking on this button the operator calls the help on line.

3JK Edition 1.00
Blank Page


3JK Edition 1.00
11 Radio view for Radio domain


3JK Edition 1.00
11.1 Radio domain menu

z To enter this menu double click on the front panel of the Radio unit in the Equipment tab-panel and then
click on the setting tab-panel.
z The above screen opens.
z Five tab panels are present:
z Alarms: shows the active alarms
z Settings: configures some radio parameters
z Measurements: performs the Tx and Rx power measurements.
z Loopback: activates the loopbacks available with the equipment.

3JK Edition 1.00
11.2 Settings
z This tab-panel is divided in 3 areas:
Direction #
Channel 1
Channel 0 (present only in 1+1 configuration)


3JK Edition 1.00
11.2 Settings
11.2.1 Direction area
z This area is divided in 3 parts:
1) Mode
2) Link Identifier Configuration
3) PPP RF


3JK Edition 1.00
11.2.1.1 Mode
z a) 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.
Radio unit without Adaptive Modulation settings

z The operation mode can be without or with the Adaptive Modulation.

3JK Edition 1.00
11.2.1.1 Mode [cont.]
z Radio capacity, channelling scheme and modulation (Static Modulation)

Channel Modulation Net radio throughput E1 Equivalent Capacity (TDM2TDM)
4 QAM 10,88 Mbit/s 4 E1
64 QAM 32,64 Mbit/s 13 E1
4 QAM 21,76 Mbit/s 8 E1
14 MHz 16 QAM 43,52 Mbit/s 18 E1
64 QAM 65,28 Mbit/s 27 E1
4 QAM 43,52 Mbit/s 18 E1
16 QAM 87,04 Mbit/s 37 E1
32 QAM 111,36 Mbit/s 48 E1
28 MHz
64 QAM 130,56 Mbit/s 56 E1
128 QAM 156,80 Mbit/s 68 E1
256 QAM 177,60 Mbit/s 77 E1
16 QAM 166,40 Mbit/s 72 E1
56 MHz
128 QAM 313,60 Mbit/s 136 E1

z Warning: Modulation 256 QAM with 56 MHz spacing is not supported.

3JK Edition 1.00
11.2.1.1 Mode [cont.]
z b) Operation with the Adaptive Modulation

Select in the Remote Select in the Mode field “Adaptive
Threshold field how Modulation”.
many dB the switching
thresholds have to be
moved from the default Select in the Modulation Range
value (+4 dB/-2 dB). The field the Modulation range (4/16
default value is approx. QAM or 4/16/64 QAM) to be used
6 dB below the 10-6 Rx by the Adaptive Modulation.
threshold.
Select in the Reference Channel

The Current Modulation Spacing field the suitable channel
field is a read-only field,
which shows the current
spacing.
used modulation. The
current modulation will
depend on the fading Select in the Reference Mode
activity during the field the spectral efficiency class
propagation. to be set as reference.
With a check mark in the

Manual Operation box it is To confirm the selection click on
possible to force a Apply.
modulation scheme by
selecting the scheme in the
Forced Modulation field. Radio unit with Adaptive Modulation settings

z 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.
z The switching between the modulation schemes is hitless and maintains the same RF channel bandwidth.
z The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB) Radio configuration
without ATPC.
z 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.
z 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
11.2.1.1 Mode [cont.]
z Radio capacity, channelling scheme and modulation (Adaptive

Modulation)
Channel Spacing Modulation Net radio throughput Equivalent capacity E1

(Note)
4 QAM 43,52 Mbit/s 18 E1
28 MHz 16 QAM 87,04 Mbit/s 37 E1
64 QAM 130,56 Mbit/s 56 E1
4 QAM 21,76 Mbit/s 8 E1
14 MHz 16 QAM 43,52 Mbit/s 18 E1
64 QAM 65,28 Mbit/s 27 E1
4 QAM 10,88 Mbit/s 4 E1
64 QAM 32,64 Mbit/s 13 E1

z Note: The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive
Modulation) can be enabled or disabled.
z 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.
z 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 Edition 1.00
11.2.1.1 Mode [cont.]
z How to change the operation mode (from operation without

Adaptive Modulation to operation with Adaptive Modulation) in 1+1
HSB configuration
z 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
11.2.1.1 Mode [cont.]
z Channel Spacing Change

Capacity Up-Grade
y 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 TDM2TDM or TDM2ETH
will be kept. The residual bandwidth for the lowest modulation scheme is
recomputed.
y When the admission control is disabled, this applies when the highest modulation
scheme of the new channel spacing has a capacity which is larger than the one with
the old channel spac-ing. In this case all the pre-configured TDM2TDM or TDM2ETH
will be kept. The residual band-width for the highest modulation scheme is
recomputed.
Capacity Down-Grade
y 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 TDM2TDM or TDM2ETH 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 TDM2TDM or TDM2ETH cannot stay in the capacity associated to the
lowest modulation scheme, the change of channel spacing is rejected by CT/NMS.

z 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: Capacity Up-
grade and Capacity Down-Grade.

3JK Edition 1.00
11.2.1.1 Mode [cont.]
y When the admission control is disabled this applies when the highest modulation
scheme of the new channel spacing has a capacity which is smaller than the one with
the old channel spac-ing. If all the pre-configured TDM2TDM or TDM2ETH 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 TDM2TDM or TDM2ETH cannot stay in the capacity associated to the
highest modulation scheme, the change of channel spacing is rejected by CT/NMS.


3JK Edition 1.00
11.2.1.1 Mode [cont.]
z Modulation Change
Capacity Up-Grade
y This applies when the new modulation scheme has a capacity which is larger than the
old one.
y When the admission control is enabled all the pre-configured TDM2TDM or TDM2ETH
are kept.
y When the admission control is disabled 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
y This applies when the new modulation scheme has a capacity which is smaller than
the old one.
y When the admission control is enabled, since the admission control was performed
with the capacity of the lowest modulation scheme, all the pre-configured TDM2TDM
or TDM2ETH will be kept.
y When the admission control is disabled, since the admission control was performed
with the capacity of the highest modulation scheme, 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.

z When the AM 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.

3JK Edition 1.00
11.2.1.1 Mode [cont.]
z Modulation Working Mode Change

From Static to Adaptive
y Adaptive Modulation can be enabled only if the ATPC is disabled.
y When the Adaptive Modulation is enabled and Admission Control is enabled the
behavior is:
{ If all the pre-configured TDM2TDM or TDM2ETH 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 TDM2TDM or TDM2ETH cannot stay in the capacity associated to the
lowest Modulation Scheme, the request of change is rejected.
y When the Adaptive Modulation is enabled and Admission Control is disabled all the
pre-con-figured TDM2TDM or TDM2ETH 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
y 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 Static
Modem Profile, the request is accepted and the residual bandwidth for new Static
Modem Profile will be computed. If all the pre-configured TDM2TDM or TDM2ETH
cannot stay in the capacity of the New Static Modem Profile, the request of change
is rejected.

z 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 TDM2TDM or TDM2ETH. 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
11.2.1.2 Link Identifier Configuration
z The operator can define the expected and sent identifier values of
parameters related to the link management and, if necessary, modify
them.
z 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.

z The operator choices will be sent to the NE by clicking on the related “Apply” button.

3JK Edition 1.00
11.2.1.3 PPP RF
z 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.
z The PPP-RF channel can be Enabled or Disabled.
z If enabled, in the Remote Address field will appear the IP address of
the remote connected NE.
z 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
11.2 Settings
11.2.2 Channel area
z This area is divided in 5 parts:
1) Frequency
2) ATPC (this menu is alternative to Manual Transmit Power Control menu)
3) Manual Transmit Power Control (this menu is alternative to ATPC menu)
4) Tx Mute
5) Alarm Profile


3JK Edition 1.00
11.2.2 Channel area
11.2.2.1 Frequency
z 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.
z In the Shifter field select the suitable shifter.
z 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.


3JK Edition 1.00
11.2.2 Channel area
11.2.2.2 ATPC
z The ATPC can be Enabled or Disabled.

z 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.
z 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.
z 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.
When the Apply button is pressed the new values will be applied.

z Note: the ATPC area is not present if the Adaptive Modulation has been selected.

3JK Edition 1.00
11.2.2 Channel area
11.2.2.3 Manual Transmit Power Control
z 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.
z 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. For the Tx Power range refer to the table.

z Note: the same power value will be used by the 16 QAM and 64 QAM modulation schemes

3JK Edition 1.00
11.2.2 Channel area
11.2.2.3 Manual Transmit Power Control [cont.]
z Tx Power values
6GHz 7GHz 8GHz 10.5GHz 11GHz 13GHz 15GHz
Reference
Channel
Spacing QAM Tx Power Tx Power Tx Power Tx Power Tx Power Tx Power Tx Power
(MHz) min max min max min max min max min max min max min max
dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm
7 4 8,5 28,5 8,5 28,5 6 26 3 23 2 22
7 16 8,5 26,5 8,5 26,5 7 24 5 21 4 20
7 64 8,5 25,5 8,5 25,5 7 23 5 20 4 19
14 4 8,5 28,5 8,5 28,5 6 26 3 23 2 22
14 16 10 26,5 10 26,5 10 24 8 21 7 20
14 64 10 25,5 10 25,5 10 23 8 20 7 19
28 4 8,5 28,5 8,5 28,5 8,5 28,5 6 26 3 23 2 22
28 16 13 26,5 13 26,5 13 26,5 13 24 11 21 10 20
28 32 13 26 13 26 13 26 13 23,5 11 20,5 7 19,5
28 64 13 25,5 13 25,5 13 25,5 13 23 14 21 11 20 10 19
28 128 13 24,5 13 24,5 13 24,5 13 22 13 20 11 19 10 18
28 256 13 22,5 13 22,5 13 22,5 13 20 13 18 11 17 10 16
56 16
56 128 15,5 24,5 15,5 24,5 16 22 14 19 13 18


3JK Edition 1.00
11.2.2 Channel area
11.2.2.3 Manual Transmit Power Control [cont.]
18GHz 23GHz 26GHz 28GHz 32GHz 38GHz

Reference
Channel Spacing QAM Tx Power Tx Power Tx Power Tx Power Tx Power Tx Power
(MHz) min max min max min max min max min max min max
dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm
7 4 -0,5 19,5 -0,5 19,5 -4,5 15,5 -5 15 -2 18 0 17,5
7 16 2 17,5 -0,5 17,5 -4,5 13,5 -5 13 -2 16 0 15,5
7 64 -0,5 16,5
14 4 -0,5 19,5 -0,5 19,5 -4,5 15,5 -5 15 -2 18 0 17,5
14 16 5 17,5 0 17,5 -4 13,5 -5 13 -2 16 0 15,5
14 64 -0,5 16,5 0 16,5 -4 12,5 -5 12 -2 15 0 14,5
28 4 -0,5 19,5 -0,5 19,5 -4,5 15,5 -5 15 -2 18 0 17,5
28 16 8 17,5 3,5 17,5 -1 13,5 -2 13 -2 16 0 15,5
28 32 3,5 17 3,5 17 -1 13 -2 12,5 -2 15,5 0 15
28 64 3,5 16,5 3,5 16,5 -1 12,5 -2 12 -2 15 0 14,5
28 128 3,5 15,5 3,5 15,5 -1 11,5 -2 11 -2 14 0 13,5
28 256 3,5 13,5 3,5 13,5 -1 9,5 -2 9 -2 12 0 11,5
56 16 6 17,5 6 17,5 1,5 13,5 1 13 -1,5 16 1 15,5
56 128 6,5 15,5 6,5 15,5 2 11,5 1 11 -1 14 1 13,5


3JK Edition 1.00
11.2.2 Channel area
11.2.2.4 Tx Mute
z 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.
z 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
11.2.2 Channel area
11.2.2.5 Alarm Profile
z Not implemented in the current release.


3JK Edition 1.00
11.3 Measurement
z The Power Measurements capability is performed by means of the

Measurement tabbed panel.

z The Measurement screen allows the operator to set initial parameters for the required measurement.
z “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.
z “Sample time” field is the period between two consecutive measurement samples. The choice is among 2,
6, 30, 60 sec.
z The last section of the dialog is referred to an optional Log file.
z 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.
z The log file contains the sample value and records the measurement up to a maximum dimension (7 days for
a 2 s sample time).
z Note: The file name must not include the following characters: \ ? : * “ < > |.
z By clicking on the “Start” button the screen “Power Measurement Graphic” appears.
z The Power Measurement Graphic is available only if the CT is connected to the NE.

3JK Edition 1.00
11.3 Measurement [cont.]

z The Power Measurement Graphic screen shows the Tx and Rx measurements related to the local and remote
NE.
z 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).
z 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.
z The top of the screen offers all the characteristics present in the current measurement:
z Radio port: gives the symbolic name associated to the radio channel being analyzed
z Sample time: indicates the frequency used to send the measurement requests to NE;
z Start time: is the first request time;
z Stop time: is the interval time selected in the previous parameters window, added to the start time;
z Time: is the current response time;
z Log File: is the complete pathname of the file where the received values are stored.

3JK Edition 1.00
11.3 Measurement [cont.]

z 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:
z 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.
z 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.
z 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.
z 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.
z N.B. PTx and PRx levels software readings tolerance is:
} PTx = Real Value ± 3dB
} PRx = Real Value ± 5dB
z WARNING:
} If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HST Configuration the transmitter is
in standby).
} If in the Tx end field the indication in dBm is +99 and, at the same time, in the relevant Rx end field the
information in dBm is -99, probably the supervision has been lost. The confirmation of the loss of the supervision is
given by a broken red icon in NES screen.

3JK Edition 1.00
11.3 Measurement
11.3.1 How to read a Power Measurement file
z Click on Read File field and press on the Select File button.
z The directory of the CT automatically opens to navigate and get the
power measurement file.
z Select the desired file and click the Open button in the Power
Measurement tab panel to open the file.
z Click again the button Open on the right side of the Sample Time field.
z The buttons in the lower part of the window allow to flow the graph
within the measurement interval.
z Select the .txt file and click with the mouse right push-button to open
.txt file with a text editor (e.g. WordPad) and to see the power
information in tabular mode.

z N.B. As default the measurement files are stored in the MPRE_CT_V00.07.08 directory and have extension
.txt.

3JK Edition 1.00
11.4 Loopback
z The functions described in this section allow to perform the test

operations by loopbacks.
z In the Resource List Area are listed all the loopbacks which can be
performed.
z 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 (Internal/Internal IF/External Line)
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.

z This domain view consists of the following areas:

z Resource Tree Area: displays the object on which the loopbacks can be performed, sorted by number.
z Resource List Area: displays tabular information about the loopback supported by the resource selected
in the tree area.
z 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.

3JK Edition 1.00
11.4 Loopback
11.4.1 How to activate a loopback
z [1] Before to activate the loopback (IF loopback) squelch the local
transmitter, because the loopback is NOT “Loop and Continue” type.
z [2] Select the suitable 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.
z [3] Select Active in the Activation field.
z [4] Click on Apply.
z [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).

z 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
11.4 Loopback
11.4.2 How to remove a loopback
z [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.
z [2] Select Not Active in the Activation field.
z [3] Click on Apply.
z [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).
z [5] Remove the squelch of the local Transmitter.


3JK Edition 1.00
12 Core-E view for Core-E and Ethernet
domain


3JK Edition 1.00
12 Core-E view for Core-E and Ethernet domain
12.1 Core-E domain
z The Core-E domain multiple main view contains two tab-panels:

Ethernet Physical Interface
TMN Interface
Core-E Main view

z This menu opens with a double click on the Core-E unit in the Equipment tab-panel.
z This domain view consists of the following areas:
z Resource Tree, displaying Ethernet physical interface with related port number;
z Resource List, displaying tabular information about tributaries in tree area;
z Resource Detail, providing access to Core-E detail view “Alarms” and “Settings”.

3JK Edition 1.00
12.1 Core-E domain
12.1.1 Ethernet Physical Interface
z This tab-panel refers to the 4 Ethernet ports, which can be used as

traffic ports and includes two tab-panels:
Alarm tab-panel
Settings tab-panel


3JK Edition 1.00
12.1 Core-E domain
12.1.1 Ethernet Physical Interface [cont.]
z 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


3JK Edition 1.00
12.1.1.1 Alarm tab-panel
z “Alarm” view shows the Ethernet ports-related alarms.

z Selecting the node in Tree area allows checking Ethernet tributary
alarms current state.


3JK Edition 1.00
12.1.1.2 Settings tab-panel (for Ethernet Port#1 to Port#4)

z 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:
z Port Status (Enabled or Disabled);
z Alarm Profile (not implemented);
z Auto-Negotiation Status (Enabled or Disabled);
z 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
z Configuration (“Other” / “Configuring” / “Complete” / “Disabled” / “Parallel Detect Fail”) all read-only;
z 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.
z 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)

{ 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.
When the Port VLAN-ID value is different from the default value, the relevant port is removed as member of the VLAN 1.
} 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
12.1.1.3 Settings tab-panel (for Ethernet Port#5)

z 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:
z Port Status (Enabled or Disabled);
z Alarm Profile (not implemented);
z Auto-Negotiation Status (Enabled or Disabled);
z 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
z Configuration (“Other” / “Configuring” / “Complete” / “Disabled” / “Parallel Detect Fail”) all read-only;
z Advertised Capability, (“1000 Mb/s – Full Duplex”).
z Optical Info field: it is a read-only field not implemented in the current release. The “Restart” button allows forcing auto-
negotiation to begin link re-negotiation.
z 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)

{ 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.
When the Port VLAN-ID value is different from the default value, the relevant port is removed as member of the VLAN 1.
} 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
12.1 Core-E domain
12.1.2 TMN Interface
z This tab-panel refers to the TMN Interface.

z 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.

z This tab-panel has 2 tab-panels:

z Alarm tab-panel
z Settings tab-panel

3JK Edition 1.00
12.1.2.1 TMN Ethernet port

z If used, the TMN Ethernet must be:

z Enabled.
z Assigned an IP address with its IP mask.
z Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also the area
number.
z Click on Apply to activate the selections.

3JK Edition 1.00
12.1.2.2 Port #4 TMN Ethernet

z If the Ethernet Port 4 has been used as TMN port, the port 4 must be:
z Enabled.
z Assigned an IP address with its IP mask.
z Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also the area
number.
z Click on Apply to activate the selections.

3JK Edition 1.00
z Configure the equipment.

z Enable the tributaries.
z Create some cross-connections.
z Set the Transmitter of Channel 1 to transmit a constant power.
z Read the Rx power of Channel 1.
z Read the RF frequency of Channel 1.
z Show the current position of the switches (through their commands in
the CT).
z Manually switch the 3 switches to the protecting channel (through their
commands in the CT).
z Activate the loopback.


3JK Edition 1.00
End of Module
Operator interface


3JK Edition 1.00
Section 3
NE operation
Module 2
Initial configuration
3JK Edition 1.00

3JK Edition 1.00
Blank Page

NE operation · Initial configuration
Document History

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
Page
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 23
1.5 Provision Synchronization 37
1.6 Provision NTP protocol 42
1.7 Provision NE Time 43
1.8 Provision VLAN 44
1.9 Cross-connections 45
1.9.1 PDH-To-Radio 47
1.9.2 PDH (E1 Access Card) to ETH (Ethernet) 48
1.9.3 ETH (Ethernet) to RADIO (Modem Card) 49
1.9.4 RADIO (Modem Card) to RADIO (Modem Card) 50
1.10 Provision System 51
1.11 Provision Local NE IP Address 54
1.12 Provision TMN Ethernet Port 55
1.13 Provision Ethernet Port 4 for TMN (if required) 56
1.14 Provision IP Static Routing 57
1.15 Provision OSPF Static Routing 59
2 TCO suite – Provisioning tool 61
2.1 TCO Main menu 62
2.2 Provisioning Tool screens 63
2.3 Configuration Options Screen 66
3 · 2 · 52.4 Core-E Configuration All Rights Reserved © Alcatel-Lucent 2009 67
9500 MPR 2.5 E1R 1.2.1
configuration 69
· 9500MPR Operation and Maintenence
2.6 Radio Provisioning 70
2.7 Synchronization Configuration 74
2.8 Cross Connections Configuration 75
2.9 802.1D management 81
2.10 802.1Q management 82
2.11 VLAN Management 84
2.12 Port VLAN Configuration 85
2.13 Network Configuration 86
2.14 Trusted Managers 88
2.15 Typical Report Panel 89

3JK Edition 1.00
Page


3JK Edition 1.00
1 Initial Configuration


3JK Edition 1.00
1.1 General Requirements
z PC HW Configuration
CPU: Pentium III 850 MHz
RAM: 500MByte (minimum), 1 Gbyte (suggested)
Min. disk space: 1,5 GByte (available space needed for log files, JRE
excluded)
Min. resolution: equal or higher than 1024x768 pixel
CD-ROM Drive: 24x
Primary Interface: Ethernet Card 10/100 Mbit/sec.
z Operating Systems Supported

Microsoft Windows 32-bit versions: Microsoft Windows XP Professional service
pack 2, Windows Vista Ultimate.


3JK Edition 1.00
1.1 General Requirements [cont.]
z Additional requirements
Microsoft Internet Explorer 6.0 6.0.2900.2180 SP1+ or higher, Microsoft
Internet
Explorer 7 7.0.5730.11C0 + or higher, Mozilla 1.7.10, Mozilla Firefox 2.0.0.12
or higher.
Minimum HTML page size shown shall be 1024x768 pixels.
Standard user can be used to run the applications but for TCO Suite usage
Administrator password is needed
JRE (Java Runtime Environment) 6 Update 3
Disable all Firewall software on used PC


3JK Edition 1.00
1.2 Initial Turn-up
z 1 - Install software on PC.

Before operating the user system interface (USI) for the first time, the
programs contained on the CD ROM must be installed on the PC. The
installation process configures the PC for its unique requirements and
prepares it to run the program.
y A - Insert CD ROM disk into PC.
y B - On Windows desktop, double click on My Computer icon. My Computer window
displays.
y C - In My Computer window, click on CD ROM icon. Files window displays
y D - Load Craft Terminal software on PC on a directory without blank spaces in the
directory name.
z 2 - Turn on the 9500MPR.
z 3 - Establish communication between equipment and Craft terminal
computer. Default NE IP address: 10.0.1.2
z 4 – Startup
Follow the steps on following figures to open communication with the
equipment.

z Note: if it is necessary to scratch the MIB use the following procedure.
z 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.
z Note: Average time necessary to scratch the database (from SW start): 6-7 minutes.

3JK Edition 1.00
1.2 Initial Turn-up [cont.]
z Startup Procedure
n Insert the NE IP address
o Click OK
p Click Show
q Click OK
See next slide r


3JK Edition 1.00
z Startup Procedure
s Type in User Name
t Type in Password
u Click to start the

loading process
Loading Performance MIB and

other processes loading
status.
v When the startup procedure is over, Main Screen is displayed


3JK Edition 1.00
z 5 - Provisioning MPR START
Enable Plug-In Cards
Provision Plug-In Cards
Provision Synchronization
Provision NTP Protocol
Provision NE Time
Provision VLAN
Provision Cross-Connections
Provision System
Provision IP/SNMP

z Note: Changes to provisioning do not have to be made in any particular order.

z See the figure for the recommended sequence.

3JK Edition 1.00
1.3 Enable Plug-In Cards
z Enabling SFP
optical plug-in
n Click to start
p Click on Apply on the Plug-

in Type field to enable the
SFP optional optical plug-in,
if the plug-in has been q Apply the
installed in the Core unit Equipment Type
o Settings
tab


3JK Edition 1.00
1.3 Enable Plug-In Cards [cont.]
z Enabling Spare
Core-E Card
n Click to start
p Choose Core-E from the dropdown

menu for the spare protected
Core-E card in slot 2
o Settings tab
Display Profile Name selected q Apply the

on Alarm Severity Profile screen Equipment Type


3JK Edition 1.00
z Enabling E1
Access Card
n Click to start
q Click to apply
changes
o Settings tab
p Choose the P32E1DS1 unit

z In order to communicate to the microprocessor in the Core-E Card the slot number & type of board housed
in the MSS, E1 Access Card and Radio Access Card have to be enabled.
z This is accomplished on the Settings screen for that card. The Core-E Card in MSS slot 1 is always enabled.
The ODU is enabled automatically when the associated Radio Access Card is enabled. The Fan Unit must be
enabled.

3JK Edition 1.00
z Enabling E1
Access Card
n Click to start
o Settings tab
p Choose the P32E1DS1 unit q Click to apply

changes


3JK Edition 1.00
z Enabling E1
Access Card
n Click to start
q Click to
apply
o Settings tab changes
p Select 1+1 EPS


3JK Edition 1.00
z Enabling Radio
Access Card
n Click to start
q Click to apply
changes
o Settings tab
p Choose the MD300 unit

z Note: ODU is automatically enabled when Radio Access Card is enabled.

3JK Edition 1.00
z Enabling Radio
Access Card
n Click to start
o Settings tab
q Click to apply
p Choose the MD300 unit changes


3JK Edition 1.00
z Enabling Radio
Access Card
n Click to start
q Click to
apply
changes
o Settings tab
p Select the suitable

protection scheme

3JK Edition 1.00
z Enabling Fan Unit
n Click to start
q Click to apply
changes
o Settings tab
p Select the FANS


3JK Edition 1.00
1.4 Provision Plug-In Cards
z Core-E Card Provisioning (Ethernet ports 1-4)
n Double left click
Go to next page


3JK Edition 1.00
1.4 Provision Plug-In Cards [cont.]
z 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
z Core-E Card Provisioning (Ethernet port 5)
n Double left click
Go to next page


3JK Edition 1.00
z Core-E Card Provisioning (Ethernet port 5)
Current provisioning for Ethernet

Port #05. Area updates when Apply
buttons are clicked.
p Click this Apply button.
o Check to enable the q Check to enable NE

selector port. Uncheck to auto-negotiation
disable first in order to functions.
change any settings.
The Optical Info field is
r Check to enable input a read-only field not
and output pause implemented in the
features. current release.
s For the configuration

refer to the Core-E unit. t Click Apply button.


3JK Edition 1.00
z E1 Access Card Provisioning
n Double left click
Go to next page


3JK Edition 1.00
z E1 Access Card Provisioning (TDM2TDM)
p q To enable the port

select “Framed/
Unframed” and click
on Apply
t Flow ID number
required to r Choose TDM2TDM if
transport E1 data.
radio is being used
Enter any number
to transport E1 data
between 2 and
4020. only (no Ethernet).
u Apply the Flow ID number. s

z 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.

3JK Edition 1.00
z E1 Access Card Provisioning (TDM2ETH)

s Select Adaptive to synch
p TDM output to packets.
Select Differential to
synch TDM output to NE
Synchronization source.
q Choose TDM2ETH if
radio is being used
to transport just
Ethernet or Ethernet
plus E1 data.
u Flow ID number
required to
transport E1
data. Enter any
number from
Table 4-1 Valid
r Set ECID
Ranges. (Tx and Rx)
values.
v Apply the Flow ID number. t


3JK Edition 1.00
z Access Card Details q 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
z Radio Access Card Provisioning
n Double left click
Go to next page


3JK Edition 1.00
z Operation without Adaptive Modulation 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
Select from dropdown list. function.
Enter number from 1 to 100 for

receiver ID. Must match transmitter
ID at other end of hop.
Capacity. Read Only Field. Enter number from 1 to 100 for
This is the nominal bit rate for transmitter ID. Must match associated
quantity of E1 lines being used. receiver ID at other end of hop.
Click to enable Open Shortest Path

PPP RF. Check to enable PPP First protocol then select area name
RF port. When not checked that has OSPF protocol.
(disabled) user cannot change: Select from dropdown list.
• Routing IP Protocol
• OSPF Area Alarm Profile. Read Only Field.
• Remote Address Displays Profile Name selected on
Alarm Severity Profile screen.


3JK Edition 1.00
TX RF Frequency is automatically
entered by ODU when ODU is
connected to MSS. If the ODU is
Shifter. Select TX (go) and RX not connected to the MSS, enter
(Return) separation frequency the TX RF frequency, within
from the Shifter Data Help list. allowed range.
Range. Displays range of TX Read Only Field.

RF frequencies that may be Displays RX RF frequency.
entered. Result of calculation:
RX Freq - X Freq = Shifter Freq.
ATPC. Check to enable ATPC.
ATPC Power Range.

Tx Mute. Read Only Field.
Status of Local Tx Mute Remote ATPC Rx Threshold.
function. Default value is -55 dBm.
Alarm Profile. Displays Profile

Name selected on Alarm
Severity Profile Screen.

z 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:
z 1.Reduce the quantity of E1 lines being transported to meet the required capacity.
z 2.Increase Reference Channel Spacing.

3JK Edition 1.00
z Operation with Adaptive Modulation

Mode.
Select Adaptive Modulation from Reference Channel Spacing.
the drop down list. Displays reference channel
spacing based on the
Modulation Range. modulation mode and the
Displays modulation scheme modulation range. Select from
based on the modulation mode. the drop down list.
Select from the drop down list.
Remote Threshold (dB).

Reference Modulation.
The default level is 0, which corresponds to
Modulation scheme used for
threshold. The operator can select
path coordination. (normally
switching levels above threshold (0 to +4 dB
worst case is used for path
corresponding to threshold level +0 to 4 dB)
coordination).
or below threshold (0 to -2 dB)
corresponding to threshold level -0 to 2 dB).


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 100
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 100
• Routing IP Protocol for Transmitter ID. Must
• OSPF Area match associated receiver ID
• Remote Address at other end of hop.


3JK Edition 1.00
Select TX (Go and RX (Return)

separation frequency from the TX RF Frequency is
dropdown list. automatically entered by ODU
when ODU is connected to
MSS. If the ODU is not
connected to the MSS, enter
the TX RF frequency, within
allowed range.
Displays range of TX RF frequencies

that may be entered. Read Only Field.
Displays RX RF frequency.
The Tx Power function allows the Result of calculation:
operator to select the transmitter RX Freq - TX Freq = Shifter
output power of each modulation Freq.
scheme. The default level is the
expected output power. The
minimum and maximum range of Check to enable the muting of
each modulation scheme is shown Tx output power.
in parenthesis (min XX - max YY).
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
1.5 Provision Synchronization
z All 9500 MPR radios in the network must be synchronized to the same
clock.
z One radio in the network is provisioned as Master.
z All other radios in the network must be provisioned as Slave.
z The slave radios are all synchronised to the clock provided by the
master.

z Normal Operation
z During normal operation, the master can be provisioned to get sync clock from two separate sources: an
internal local oscillator (most common source) or external clock from customer provided equipment. The
slave radios can be provisioned to receive the sync clock from one of two sources: clock recovered by the
radio receiver or the sync clock from another radio in the network. Normally at a repeater, the sync clock
is received over the RF path and recovered by the radio receiver. A typical slave terminal uses the clock
from an adjacent radio. See following figures for typical master terminal provisioning and for typical slave
terminal provisioning.
z Failed Primary Operation
z With the exception of the master when the radio is provisioned to sync off the local oscillator, the
provisioned secondary sync source is enabled if the primary source fails. When the master, provisioned to
accept sync clock at the Core-E from an external source, fails, the internal free-running local oscillator is
enabled. Provisioning choices for the secondary source for slave radios depend upon the choices made
from the primary source.
z Sync Switching
z With the exception of the master when the radio is provisioned to sync off the local oscillator, the sync
clock source is switched from primary to secondary if the primary source fails. Sync clock switching
provisioning is dependent on the role of the radio in the network (master or slave) and on user
preference. A revertive switching feature is a provisioning option that restores the sync clock to the
original source when the alarm on the primary source is cleared. If revertive switching is not selected, the
secondary sync source continues to provide sync clock, and if the secondary source fails, must be
manually switched to the primary source.

3JK Edition 1.00
1.5 Provision Synchronization [cont.]
z Provisioning Master with Free Run Local Oscillator

as Primary Source
Go to next page


3JK Edition 1.00
z Provisioning Master with Free Run Local Oscillator

as Primary Source
From to previous page


3JK Edition 1.00
z Provisioning Slave with Radio Port as Primary Source
Go to next page


3JK Edition 1.00
z Provisioning Slave with Radio Port as Primary Source

From to previous page


3JK Edition 1.00
1.6 Provision NTP protocol
Enable the NTP (Network

Time Protocol).

z 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.
z The Server reachability field is a read-only field, which shows the reachability of the NTP servers. The
following information can appear:
z "Main server reachable"
z "Spare server reachable"
z "None servers reachable"
z "Both servers reachable"
z Click on Refresh to update the screen.
z Click on Apply to send to the NE the NTP Configuration.

3JK Edition 1.00
1.7 Provision NE Time
z NE Time Provisioning
o Click to display
pop-up dialog for NE
Time configuration.
p When checked, enables function to

synchronize Operating System and
Network Equipment Times. q

z The user can provision the operating system (PC/laptop) to manage time and date stamping functions. Time
and date provisioning is accomplished using the NE Time Configuration screen.

3JK Edition 1.00
1.8 Provision VLAN
z To provision VLAN refer to S3-M1 chapter 3.6.


3JK Edition 1.00
1.9 Cross-connections
z The cross connections screen is used to configure switching of

packetized data through the Core-E Card. Using this screen, the
operator can switch:
E1 ports (lines) from/to an E1 Access Card (PDH) to/from a Modem Card
(RADIO) and/or any of four Ethernet (ETH) ports on the Core-E Card.
Ethernet (ETH) data from/to an external source to/from a Modem Card
(RADIO) and/or to/from an E1 Access Card (PDH).
z Valid Cross Connections:
PDH -to- RADIO
PDH -to ETH
ETH -to- RADIO
RADIO -to- RADIO


3JK Edition 1.00
1.9 Cross-connections [cont.]
n Click to open
Cross
Connections
Screen
Go to next page


3JK Edition 1.00
1.9.1 PDH-To-Radio
Flow ID required to transport
q E1 line(s) 1-32
you want
transported
o Click to PDH
box (source) p Double left
and drag line to click
radio box anywhere
(destination) on line to
open line
select
dialog box

z The following rules and guidelines apply to switching E1 ports 1 through 32 on the E1 Access Card through
the Core-E Card to the Radio Modem Card. Follow the steps to cross-connect E1 lines to Radio.
z 1. The license key installed on the Core-E Card determines the number of E1 ports that can be cross
connected.
z 2. The E1 Access Card (E1 source) and Radio Modem Card (destination) must be Enabled on the respective
card provisioning screens.
z 3. Each E1 port to be cross connected must be Enabled on the E1 provisioning screen.
z 4. Each E1 port to be cross connected must have a Flow ID number assigned to it on the E1 provisioning
screen. Refer to Flow ID number rules.
z 5. The Flow ID number check box on the cross connections screen must be checked for each E1 port to be
cross connected.

3JK Edition 1.00
1.9.2 PDH (E1 Access Card) to ETH (Ethernet)

z The following rules and guidelines apply to switching E1 ports 1 through 32 on the E1 Access Card through
the Core-E Card to the Ethernet ports 1 through 4. Follow the steps to cross-connect PDH to ETH.
z 1. The license key installed on the Core-E Card determines the capacity of the Ethernet data that can be
cross connected.
z 2. The Ethernet port (source) and E1 Access Card (destination) must be Enabled on the respective Core-E
Card and E1 Access Card provisioning screens.
z 3. The Service Profile on the E1 Access Card Settings screen must be set to TDM2ETH for each E1 cross
connected.
z 4. A Flow ID number must be assigned to each E1 cross connected on the E1 Access Card Settings screen.
Refer to the Flow ID number rules.
z 5. The Ethernet port to be cross connected must have a Flow ID number assigned to it on the Ethernet
provisioning screen. Refer to the Flow ID Number rules.
z 6. The Flow ID number check box on the cross connections screen must be checked for each Ethernet port
to be cross connected.
z 7. The MAC Address of the Ethernet equipment connected to the Ethernet connectors on the Core-E card
must be entered on the pop up.

3JK Edition 1.00
1.9.3 ETH (Ethernet) to RADIO (Modem Card)

z The following rules and guidelines apply to switching Ethernet ports 1 through 4 on the Core-E Card to the
Modem Card. Follow the steps to cross connect Ethernet to Radio.
z 1. The license key installed on the Core-E Card determines the Ethernet data capacity that can be cross
connected.
z 2. The Ethernet port (source) and Modem Card (destination) must be Enabled on the respective Core-E
Card and Modem Card provisioning screens.
z 3. The Service Profile on the E1 Access Card Settings screen must be set to TDM2ETH for each E1 cross
connected.
z 4. A Flow ID number must be assigned to each E1 cross connected on the E1 Access Card Settings screen.
Refer to the Flow ID number rules.
z 5. The Ethernet port to be cross connected must have a Flow ID number assigned to it on the Ethernet
provisioning screen. Refer to the Flow ID Number rules.
z 6. The Flow ID number check box on the cross connections screen must be checked for each Ethernet port
to be cross connected.
z 7. The MAC Address of the Ethernet equipment connected to the Ethernet connectors on the Core-E Card
must be entered on the pop up.

3JK Edition 1.00
1.9.4 RADIO (Modem Card) to RADIO (Modem Card)

z The following rules and guidelines apply to switching Modem Card to Modem Card (such as a through
repeater). Follow the steps to cross-connect Radio-to-Radio.
z 1. The license key installed on the Core-E Card determines the Ethernet data capacity that can be cross
connected.
z 2. Each Modem Card must be enabled.
z 3. Capacity of Modem Cards on Settings screens must match.

3JK Edition 1.00
1.10 Provision System
z System Setting
Go to next page

z Follow the steps to provision tributary port impedance, quality of service classification, and enter NE MAC
address.

3JK Edition 1.00
1.10 Provision System [cont.]
z System Setting
p q
r s
t u

z 1) Tributary Port Configuration

z 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.
z 2) Quality Of Service
z This field allows to set the suitable Quality Of Service (Disabled/DiffServ/802.1p). To activate the new
value, click on Apply.
z 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.
z 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.
z 3) DHCP
z 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.
z The DHCP server uses an address pool of only one IP address, defined according to the NE Ethernet port IP
address:
} NE Ethernet port IP address plus one, if this address is not a direct broadcast address,
} otherwise NE Ethernet port IP address minus one.
z The IP mask is set to the mask of the NE local Ethernet port and the default gateway is set to the NE IP
address. The lease time is fixed to 5 minutes.
z To activate the DHCP server, select Enabled and click on Apply.

3JK Edition 1.00
1.10 Provision System [cont.]
v w
11 12

z 4) Admission Control for Adaptive Modulation

z The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive Mod-ulation)
can be enabled or disabled. Default: “Enabled”.
z 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.
z 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).
z Warning: The disabling of the Admission Control can be done in 1+0 configuration only.
z 5) Event and Alarm Log
z As default the Logging is enabled. If set to "Disabled" the events are not sent to the Event Log Browser
application.
z 6) NE MAC Address
z 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.11 Provision Local NE IP Address
z Local Configuration n
Provisioning o
p Click to display pop-

up dialog for the IP
Configuration.
q Enter NE IP address
r Apply the IP Address.


3JK Edition 1.00
1.12 Provision TMN Ethernet Port
n Double click on the front panel of the Core-E unit in the Equipment menu
o Select the TMN Ethernet
p Select the Setting tab-panel
q Enable TMN Ethernet
r Enter IP address.
s Select Static Routing for

manual routing. Select
OSPF (Open Shortest
Path First protocol) for
automatic routing.
t Enter IP Mask and click

on Apply.

z Follow the steps to provision TMN Ethernet on the Core-E Card to carry SNMP data.

3JK Edition 1.00
1.13 Provision Ethernet Port 4 for TMN (if required)
n Double click on the front panel of the Core-E unit in the Equipment menu
o Select the Port #4 TMN Ethernet
p Select the Setting tab-panel
q Enable the TMN

Port 4
r Enter IP address
s Select Static Routing for

manual routing. Select
OSPF (Open Shortest
Path First protocol) for
automatic routing.
t Enter IP Mask and click

on Apply.

3JK Edition 1.00
1.14 Provision IP Static Routing
z IP Static Routing Provisioning
n o p
q Click to display pop-up

dialog for IP Static Routing
Configuration Go to next page

z Follow the steps to provision.

3JK Edition 1.00
1.14 Provision IP Static Routing [cont.]
t IP Mask.
z IP Static Routing
Provisioning
r Route to a specific IP
address.
s Enter IP address.
v List of RF
path
u IP interface to a host or directions.
network. Typically used at a Click to
spur to interface a host over view drop
the RF path. In this scenario, down list.
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.
w Create new or change existing IP static routes.


3JK Edition 1.00
1.15 Provision OSPF Static Routing
z OSPF Static Routing Provisioning
q IP Static Routing
Configuration screen.
Click to display pop-up
dialog for OSPF Area
Configuration

z 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 TCO suite – Provisioning tool


3JK Edition 1.00
2.1 TCO Main menu
Open Java runtime

environment and
start provisioning


3JK Edition 1.00
2.2 Provisioning Tool screens
z This screen gives to the operator the possibility to connect to a NE (by

entering the relevant IP address) or to provision an off-line
configuration.
z If you are connected to the NE to get access the NE you have to enter
the username (default=initial) and the password (default=adminadmin).
z By clicking on OK (after loading the JRE package) the opening screen
opens.


3JK Edition 1.00
2.2 Provisioning Tool screens [cont.]
z Opening screen with off-line operation

z The buttons present in this screen has the following meaning:

z 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.
z Get: not operative.
z Create: allows to create a new configuration file.
z Prev: not operative.
z Cancel: not operative.
z By clicking on the "Open" button a window opens, which gives the possibility to open a configuration file
created in 1.1.0 version or in 1.0.0 old version. If a 1.0.0 configuration file is open a new screen appears,
which asks to convert the file from 1.0.0 to 1.1.0.
z By clicking on the "Create" button it will be possible to create a file in 1.1.0 version or in the 1.0.0 old
version.
z 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
2.2 Provisioning Tool screens [cont.]
z Opening screen with the connection to the NE

z The buttons present in this screen has the following meaning:

z 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.
z 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.
z Create: allows to create a new configuration file.
z Prev: not operative.
z Cancel: not operative.
z By clicking on the "Open" button a window opens, which gives the possibility to open a configuration file
created in 1.1.0 version or in 1.0.0 old version. If a 1.0.0 configuration file is open a new screen appears,
which asks to convert the file from 1.0.0 to 1.1.0.
z By clicking on the "Create" button it will be possible to create a file in 1.1.0 version or in the 1.0.0 old
version.
z 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
2.3 Configuration Options Screen
z The screen below 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 below are for all cards. See the screens shown below for more
information.
Protections options
for the Core-E cards
Protections options
shown for Slot 3
and Slot 4
Protections options
shown for Slot 5
and Slot 6


3JK Edition 1.00
2.4 Core-E Configuration
Check to allow communication Check to

at data rate but in only one enable the Check to enable
direction at a time. selected port auto negotiation When
checked
Ethernet this
feature
Icon enables
input
E1 Access and
output
Card Icon pause
features
Radio
Access
Card Icon
Check to allow communication

at data rate in both directions
at the same time.

z Note:
z A white icon indicates that there are no cross-connections, but cross-connections can be created.
z 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.
z 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.]
The Quality Of Service Select Transport if

feature enables priority ETH Port 4 on the
forwarding in the Core-E Card Core-E Card is used
switch based on how the to transport
packets are tagged: not
tagged or tagged 802.1p or Ethernet data.
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
tagged 802.1p or DiffServ in Select TMN if
order to know which QOS ETH Port 4 on
function to chose. the Core-E
Card is used
for SNMP
data.
Check to enable
the optical SFP
plug-in
Each packet is
Priority forwarding classified based on
disabled. Each packet is based on DSCP presence of valid
field in IP header to determine 802.1p user priority
priority. tag.

z Note:
z A white icon indicates that there are no cross-connections, but cross-connections can be created.
z 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.
z A green icon indicates that the source and destination are available and the destination can accept more E1
ports.

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
three modes:
Adaptive,
Choose TDM2TDM Differential, and
if radio is being TDM_Line_In.
used to transport Select Adaptive to
E1 data only (no sync TDM output to
Ethernet). packets. Select
Select Balance Differential to sync
120 Ohm if TDM output to NE
Select Unbalance 75 Ohm tributary cable Synchronization
is twisted pair. source.
if tributary cable is coax.


3JK Edition 1.00
2.6 Radio Provisioning
z Radio Configuration Screen (without Adaptive Modulation)
Check to enable Select Revertive feature if

PPP RF port. you want traffic on the
The user can protection channel to
select: automatically switch back
• Static routing or to the main channel when
• OSPF Area alarms clear or a switch
command is released.
Check to
enable radio Select the suitable reference
ID mismatch channel spacing.
function.
Select the modulation scheme.
Enter number
from 1 to 100 for
No check mark here.
Transmitter ID.
Must match
associated Enter number from 1 to 100 for
Transmitter ID at Receiver ID. Must match associated
other end of hop. Receiver ID at other end of hop.


3JK Edition 1.00
2.6 Radio Provisioning [cont.]
No check mark here.

Select TX (Go)
and RX (Return)
separation
frequency from
drop-down list.
Select the
modulation scheme
Enter the Tx RF
frequency within
the allowed range.
Enter the Tx Power
Check to enable ATPC.
Enter the ATPC

parameters.


3JK Edition 1.00
z Radio Configuration Screen (with Adaptive Modulation)

Enable PPP RF port.
The user can select:
• Static routing or
• OSPF Area
Check to enable radio

ID mismatch function.
Select Revertive feature if you

want traffic on the protection
channel to automatically
Enter number from 1 to 100 switch back to the main
for Receiver ID. Must match channel when alarms clear or
associated Receiver ID at a switch command is released.
other end of hop.
Check mark to enable the Adaptive

Enter number from 1 to Modulation (see Note 1).
100 for Transmitter ID.
Must match associated
Transmitter ID at other Enter the Tx Power (see Note 2).
end of hop.

z Note 1: With the Adaptive Modulation the only available configuration is: 1+1 HSB.
z Note 2: The operator 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.
Select in the
Select TX Thresholds field
(Go) and RX how many dB
(Return) the switching
separation thresholds have
frequency to be moved
from drop- from the default
down list. value (+4 dB/-2
dB). The default
value is approx.
Enter the Tx 6 dB below the
RF frequency 10-6 Rx
within the threshold.
allowed range.
Select in the Reference Select in the Scheme field the

Mode field the spectral Modulation range (4/16 QAM
efficiency class to be set or 4/16/64 QAM) to be used by
as reference. the Adaptive Modulation.


3JK Edition 1.00
2 TCO suite –Provisioning
2.7 Synchronization Configuration
Revertive - Switches sync

source back to primary Non-Revertive - Does not switch
source after alarm on back to primary source after
primary source clears. primary alarm clears and stays on
secondary sync source.
Synchronization Role.
Master or Slave.
Free Run Local

Oscillator - Local
oscillator on
Synch-Out Port Core-E Card.
Configuration - Normal Master
Connector that can be primary sync
used to provide sync source.
to another radio or
ancillary equipment.
Synch-In Port -
SClock from external Any Available E1 -
source received on Clock from E1
the Sync In connector source via E1
on the Core-E card. peripheral.


3JK Edition 1.00
2 TCO suite – Provisioning
2.8 Cross Connections Configuration
Radio Access Card icon. A white icon

indicates the source/destination is
unavailable. Check to make sure the card
is enabled.
White ETH icons: A white icon indicates the source/destination is unavailable. Check to make sure
the card is enabled.
Blue ETH icons: 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.
Green ETH icons: A green icon indicates that the source and destination are available and the
destination can accept more E1 ports.


3JK Edition 1.00
2.8 Cross Connections Configuration [cont.]
Black Line: E1 to Radio connection.

Click on this line to display the popup
window shown below.
Indicates Flow ID has been created on the Radio Access Card

Settings screen. A Radio Access line must have a Flow ID to be
cross-connected. Flow ID is unique to network. No two Flow
IDs in a network can be the same. Flow ID number is required
to transport E1 data. Enter any number between 2 and 4080.


3JK Edition 1.00
E1 Access Card icon. A

green icon indicates
that the source and
destination are
available and the
destination can accept
more E1 ports.


3JK Edition 1.00
Flow ID is unique to
network. No two Flow
IDs in a network can be
the same.
Tx Over-the-hop ID.
The purpose of TMN Clock Source
provisioning is to select the
mode that will be used to sync
TDM E1 data to the node Rx Over-the-hop ID.
Synchronization source. The user Must match Rx/Tx ID at
can select one of three modes: other end.
Adaptive, Differential, and
TDM_Line_In. Select Adaptive to
sync TDM output to packets. Enter MAC address of
Select Differential to sync TDM link partner (External
output to NE Synchronization Ethernet Equipment).
source. Select TDM_Line_In to
sync TDM output to TDM input. Blue Line: E1 to
Click now for more details. Ethernet connection.


3JK Edition 1.00
Indicates Flow ID has been created on the Radio Access Card

Settings screen. A Radio Access line must have a Flow ID to be
cross-connected. Flow ID is unique to network. No two Flow
IDs in a network can be the same. Flow ID number is required
to transport E1 data. Enter any number between2 and 4080.


3JK Edition 1.00


3JK Edition 1.00
2.9 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.10 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 dis-abled) 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.10 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
con-figuration screen opens


3JK Edition 1.00
2.11 VLAN Management

z [1] VLAN ID field: Enter the VLAN ID (the configurable values must be in the range 2 - 4080)
z N.B.: The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) can-not be
used.
z [2] VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.
z N.B.: There is no check on unambiguity name.
z [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.
z [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).
z 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 trans-mitted with
Tag.
z 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.12 Port VLAN Configuration
Admit all frames Admit tag

(tagged and frames only
untagged frames are (only tagged
allowed in ingress) frames are
allowed in
ingress)
Port VLAN ID and Priority: if the

Acceptable Frame Type is set to
“Admit all frames” 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.When the Port VLAN-
ID value is different from the
default value, the relevant port is
removed as member of the VLAN 1.

z 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.13 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.13 Network Configuration [cont.]
Displays the
Displays status (Enabled IP address of
when checked) of NTP the Spare
Protocol provisioning on (standby) NTP
NTP Server server
Configuration screen. entered as
Spare Server
address on
the NTP
Displays the IP address of the Main NTP Server
server entered as Main Server address on Configuration
the NTP Server Configuration screen. screen.


3JK Edition 1.00
2.14 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.

z A Trusted manager is an SNMP manager to which the NE automatically sends the TRAPS generated inside the
NE.

3JK Edition 1.00
2.15 Typical Report Panel

z Buttons:
z Prev: the procedure goes back to the previous step
z Save: allows to save the configuration file
z Apply: it is operative only if you are physically connected to the NE and it activates the download of the
configuration to the NE
z Cancel: the procedure goes back to step 1 (Opening screen)

3JK Edition 1.00
Exercise
z 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


3JK Edition 1.00
Section 3
NE operation
Module 3
Performance monitoring
3JK Edition 1.00

3JK Edition 1.00
Blank Page

NE operation · Performance monitoring
Document History

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
Page
1 Performance Monitoring Tool 7
13.1 Introduction 8
13.2 Core-E unit performances 10
13.2.1 Ethernet Aggregate Rx Table 11
13.2.2 Ethernet Aggregate Tx Table 14
13.3 MD300 unit performances 17
13.3.1 Current Data Table 20
13.3.2 CD parameters 23
13.3.3 CD counters 24
13.3.4 History Data Table 25
13.3.5 HD counters 26
13.3.6 Threshold tables 27
13.3.7 How to create a new threshold table 28
13.3.8 How to change/delete a threshold table 29
13.3.9 Threshold table association 30
13.3.10 Adaptive Modulation performance 31
13.3.11 Ethernet Aggregate Tx Table 34
13.3.12 Ethernet Aggregate Per Queue 36
13.4 P32E1DS1 unit performances 39
13.4.1 Incoming (Current Data Table) 40
13.4.2 CD parameters 43
13.4.4 Incoming (History Data Table) 45
13.4.5 HD Counters 46
3 · 3 · 5 13.4.6 Outgoing (Current Data Table) All Rights Reserved © Alcatel-Lucent 2009 47
13.4.7 R 1.2.1CD parameters
9500 MPR · 9500MPR Operation and Maintenence 50
13.4.9 Outgoing (History Data Table) 52
13.4.10 HD Counters 53
13.4.11 Threshold tables 55
13.4.12 How to create a new threshold table 56
13.4.13 How to change/delete a threshold table 57
13.4.14 Threshold table association 58
13.4.14.1 One-Shot Threshold association 59
13.4.14.2 Specific E1 Port # association 60
13.4.14.3 Specific E1 Port # Incoming or Outgoing 61
Exercise 63
Exercise 64
Blank Page 65
End of Module 66

3JK Edition 1.00
Page


3JK Edition 1.00
1 Performance Monitoring Tool


3JK Edition 1.00
13.1 Introduction
z To open the Performance Monitoring tool click on the relevant icon in

the Menu bar as shown in the next figure.
z The Performance Monitoring tool allows to display all the performances

available on the units of MPR:
Core-E unit
MD300 unit
P32E1DS1 unit


3JK Edition 1.00
13.1 Introduction [cont.]
z The welcome screen of the Performance Monitoring screen is shown in

Figure.
z The Performance Monitoring tool can be used for different NEs. In the
left column will be present all the NEs. In the example only one NE is
present (151.98.96.117).

z By clicking on a specific unit will appear the performances available with the selected unit.

3JK Edition 1.00
13.2 Core-E unit performances
z Two groups of Performance Monitoring are available:
Ethernet Aggregate Rx Table (incoming side)
Ethernet Aggregate Tx Table (outgoing side)


3JK Edition 1.00
13.2.1 Ethernet Aggregate Rx Table

z To activate the Rx performances (Incoming side):

z 1) Select the Ethernet Aggregate Rx Table row as shown in the next figure.
z 2) Select the Interval (the collection time of the performances): 4, 6, 30, 60 seconds. The default value is
4 sec.
z 3) Select the Duration of the performance monitor in hour and minutes. The max. duration is 24 hours.
z 4) Click on the Start button to start the monitoring.

3JK Edition 1.00
13.2.1 Ethernet Aggregate Rx Table [cont.]
z To display the performance monitor select the suitable port (port #2 in

the example).

z The available performances at port level are:

z TRCO: total number of octects of Ethernet frames received by the Virtual Ethernet Interface, including
Ethernet header characters.
z TRCF: total number of Ethernet frames received by the Virtual Ethernet Interface.
z TRSEF: total number of errored frames.
z TDF: total number of Ethernet frames which were chosen to be discarded due to buffer congestion.
z TRCF Unicast: total number of Ethernet Unicast frames received correctly by the Virtual Ethernet
Interface.
z TRCF 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.
z TRCF Broadcast: total number of good packets received that were directed to the broadcast address. This
number does not include multicast packets.
z The performances are displayed in two different formats:
z graphical format in the lower part
z tabular format in the upper part
z In the graphical format by putting a check mark on the check box only one (or more than one or all)
performance can be displayed.

3JK Edition 1.00
13.2.1 Ethernet Aggregate Rx Table [cont.]
z By selecting the Ethernet Aggregate Rx Table all the performances

regarding all the enabled Ethernet ports are shown in tabular format.


3JK Edition 1.00
13.2.2 Ethernet Aggregate Tx Table

z To activate the Tx performances (Outgoing side):

z 1) Select the Ethernet Aggregate Tx Table row as shown in the next figure.
4 sec.

3JK Edition 1.00
13.2.2 Ethernet Aggregate Tx Table [cont.]
z To display the performance monitor select the suitable port (port #2 in

the example).

z The available performances at port level are:

z TTO: total number of octets of Ethernet frames transmitted out by the Interface, including Ethernet
header characters.
z TTF: total number of Ethernet frames transmitted out by the interface.
z TDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer
congestion.
z TRCF Unicast: total number of Ethernet Unicast frames transmitted out by the Virtual Ethernet Interface.
z TRCF 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.
z TRCF Broadcast: total number of good packets transmitted by this address that were directed to the
broadcast address.
performance can be displayed

3JK Edition 1.00
z By selecting the Ethernet Aggregate Tx Table all the performances

regarding all the enabled Ethernet ports are shown in tabular format.


3JK Edition 1.00
13.3 MD300 unit performances
z By selecting the MD300 unit the screen in Figure opens.


3JK Edition 1.00
13.3 MD300 unit performances [cont.]
z The counters supported are the following:

Errored Seconds
Severely Errored Seconds
Background Block Error
Unavailable Seconds

z The performance monitoring (PM) gives indication on the quality of service.

z Quality of service PM is performed in accordance with G.826 and G.784.
z 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.
z 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.
z Two different radio sections can be monitored:
z Radio Hop Section: the section between two radio stations inside the protection section.
z Radio Link Section: the section identifying the protected section.
z 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. .

3JK Edition 1.00
13.3 MD300 unit performances [cont.]
z The performance reports can be of 2 different types:

15 minutes
24 hours
z 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.
z The Performance Monitoring are of HOP or LINK type.
z HOP refer to Performance Monitoring before the RPS switch.
z LINK refer to Performance Monitoring after the RPS switch. The current
report can be seen (and configured) and the history log can be seen.


3JK Edition 1.00
13.3.1 Current Data Table

z To see (and configure) the Current Data report:

z 1) Click on the desired granularity (15 m or 24 h) on the Current Data Table below the HOP channel (0 or
1) (in 1+0 configuration channel 1 only) to see the HOP report or below the LINK to see the LINK report.
Refer to the figure.
z 2) Click on the Start button in the Tool bar.

3JK Edition 1.00
13.3.1 Current Data Table [cont.]
z Refer to Figure to see an example of the Current Data display.


3JK Edition 1.00
13.3.1 Current Data Table [cont.]
z Refer to Figure to see the Alarm Data tab panel to see the alarms
regarding the performances, if any.


3JK Edition 1.00
13.3.2 CD parameters
z The fields displayed in the upper part of the screen allow the operator
to check and manage the parameter of the current data collection.
Suspect interval shows whether the current data are suspect or not (Note).
Elapsed Time field (read-only) displays the elapsed time in the current
interval of monitoring.
Last Update: display time of the PM in the graphical description and in the
tabular description in the upper part of the screen. By pressing the Refresh
button this time changes.
Max Interval supp.: max. number of intervals (reports) which can be
suppressed in the History because they don’t have errors.
Num. Interval supp.: number of intervals (reports) suppressed in the History
because they don’t have errors.

z Note: An interval is defined as “Suspect” if at least one of the following conditions occurs in the collection
period:
z the elapsed time deviates more than 10 seconds of the nominal time
z loss of the PM data in the equipment
z performance counters have been reset during the interval.

3JK Edition 1.00
13.3.3 CD counters
z BBE (Background Block Error)
z ES (Errored Second)
z SES (Severely Errored Second)
z UAS (Unavailable Second)

z Note: These values refer to the last refresh performed with the Auto Refresh.

3JK Edition 1.00
13.3.4 History Data Table
z Refer to Figure to open the History Data Table.

z To see an History Data report:

z 1) Click on the desired granularity (15 m or 24 h) on the History Data Table below the HOP channel (0 or 1)
(in 1+0 configuration channel 1 only) to see the HOP report or click on LINK to see the LINK report.
z The Performance Monitoring process monitors the parameters during a specified interval (i.e. 15min) and
stores their values in history data. A History Data collection is created automatically at the end of each time
interval of Current Data.
z Note: Use the arrows “Right” and “Left” in the lower part to pass from one log to another log in the
history.

3JK Edition 1.00
13.3.5 HD counters
z BBE (Background Block Errors)


3JK Edition 1.00
13.3.6 Threshold tables
z To view the available threshold for Performance Monitoring process,

the operator must select the Thresholds Tables node tree.
z There are threshold tables for the HOP and for the LINK.
z There are two default threshold tables for HOP: Threshold #1 (to be
associated to 15 min report) and Threshold #4 (to be associated to 24 h
report).
z There are two default threshold tables for LINK: Threshold #1 (to be
associated to 15 min report) and Threshold #3 (to be associated to 24 h
report).


3JK Edition 1.00
13.3.7 How to create a new threshold table

z Note: 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).
z To create a new threshold table:

z 1) Click on Threshold Tables HOP (or LINK) node tree. The Threshold Data Creation screen will appear, as
shown in the next figure (Hop threshold).
z 2) Write the values for the Low and High thresholds.
z 3) Click on Create. Automatically the new threshold takes a name with a progressive number.

3JK Edition 1.00
13.3.8 How to change/delete a threshold table

z Note: Only the created thresholds can be modified or deleted. The default thresholds can be only
displayed.
z 1) Click on the Threshold to be modified/deleted in Threshold node tree (Threshold #3 in the example of
the figure).
z 2) Low and high thresholds for each counter are shown. Edit the new values in the table fields to change
them.
z 3) Click on the Apply button to confirm the changes or click on the Delete button to delete the threshold.

3JK Edition 1.00
13.3.9 Threshold table association

z To each Performance Monitoring can be associated a Threshold Table.

z To associate a Threshold Table click on Current Data Table or History Data Table of HOP-Channel#0 (or
Channel#1) or of LINK. The 15min&24h tab panel will appear.
z In the Counter Thresholds field select the threshold to be associated and click on Apply.

3JK Edition 1.00
13.3.10 Adaptive Modulation performance

z If the Adaptive Modulation has been enabled in the Modem unit, 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.
z To activate the Adaptive Modulation performance:
z 1) Click on the desired granularity (15 m or 24 h) on the Current Data Table below the HOP channel (0 or
1) (in 1+0 configuration channel 1 only) to see the HOP report or below the LINK to see the LINK report.
Refer to the next figure.

3JK Edition 1.00
13.3.10 Adaptive Modulation performance [cont.]
z Figure shows a display of Current Data report (15 min).

z The Scale of the diagram can be changed by using the arrows (up and down) on the scale field and by
pressing Update.

3JK Edition 1.00
13.3.10 Adaptive Modulation performance [cont.]
z Figure shows a display of History Data report (15 min).

history.

3JK Edition 1.00
13.3.11 Ethernet Aggregate Tx Table

z To activate the Tx performances (Outgoing side):

z 1) Select the Ethernet Aggregate Tx Table row as shown in the next figure.
4 sec.

3JK Edition 1.00
z Refer to figure to see the performances.

z The available performances at output Tx radio port are:

z TTO: total number of octets of Ethernet frames transmitted out by the Interface, including Ethernet
header characters.
z TTF: total number of Ethernet frames transmitted out by the interface.
z TDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer
congestion.
performance can be displayed.

3JK Edition 1.00
13.3.12 Ethernet Aggregate Per Queue

z The MD300 unit has 8 output queues.

z Queue 8 is reserved to TDM2TDM traffic.
z Queue 7 is reserved to TDM2Eth traffic.
z Queue 6 is reserved to TMN traffic.
z The remaining 5 queues are reserved to Ethernet traffic. Queue 5 is the highest priority queue.
z To activate the Ethernet Aggregate Per Queue performances (Outgoing radio side):
z 1) Select the Ethernet Aggregate Per Queue row as shown in the next figure.
4 sec.

3JK Edition 1.00
13.3.12 Ethernet Aggregate Per Queue [cont.]
z To display the performance monitor select the suitable queue (Queue

#1 in the example).

z The available performances at queue level (for each queue) are:

z TCF: total number of Ethernet conforming frames accepted and transmitted out by the specific queue of
the interface.
z Discard TCF: total number of Discarded Ethernet conforming frames accepted by the specific queue of
the interface.
z TCO: total number of Ethernet conforming octects accepted and transmitted out by the specific queue of
the interface.
z In the graphical format by putting a check mark on the check box only one (or more or all) performance can
be displayed.

3JK Edition 1.00
13.3.12 Ethernet Aggregate Per Queue [cont.]
z By selecting the Ethernet Aggregate Per Queue row all the

performances regarding all the queues are shown in tabular format.


3JK Edition 1.00
13.4 P32E1DS1 unit performances
z By selecting the P32E1DS1 unit the screen opens.

z The performance monitoring (PM) gives indication on the quality of the E1 streams, which have been
configured as "Framed".
z In Figure the E1 streams, configured as "Framed" are shown in bold; for all the other E1 streams (in grey) the
performance are not available because the relevant streams are disabled or they have been configured as
"Unframed".
z Two types of performances are available:
z Incoming: these performances are detected at the input in Tx side.
z Outgoing: these performances are detected at the output in Rx side.
z Note: 9500MPR is transparent regarding the E1 stream. The CRC is used to detect the quality of the E1
stream; it is never changed.
z The Quality is performed in accordance with G.826 and G.784.
z The performance reports are of 2 different types:
z 15 minutes
z 24 hours
z 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.
z 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.
z 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.
z 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 Ethernet Aggregate Tx Table section).
z 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.

3JK Edition 1.00
13.4.1 Incoming (Current Data Table)


z 1) Click on the desired granularity (15 m or 24 h) on the Current Data Table. Refer to the next figure.
z 3) Click on Refresh button to update the collection.

3JK Edition 1.00
13.4.1 Incoming (Current Data Table) [cont.]
z Example of the Current Data display


3JK Edition 1.00
13.4.1 Incoming (Current Data Table) [cont.]
z To see the Alarm Data tab panel to see the alarms regarding the
performances, if any.


3JK Edition 1.00
Last Update: display time of the Performance Monitoring in the graphical
description and in the tabular description. This time changes after the Auto
Refresh.

period:
z loss of the Performance Monitoring data in the equipment

3JK Edition 1.00
13.4.3 CD counters

z Note: These values refer to the last refresh performed with the Refresh button in the Tool bar.

3JK Edition 1.00
13.4.4 Incoming (History Data Table)

1) Click on the desired granularity (15 m or 24 h) on the History Data Table.

history.

3JK Edition 1.00
13.4.5 HD Counters


3JK Edition 1.00
13.4.6 Outgoing (Current Data Table)


z 1) Click on the desired granularity (15 m or 24 h) on the Current Data Table.
z 3) Click on Refresh button to update the collection.

3JK Edition 1.00
13.4.6 Outgoing (Current Data Table) [cont.]
z Example of the Current Data display


3JK Edition 1.00
13.4.6 Outgoing (Current Data Table) [cont.]
z To see the Alarm Data tab panel to see the alarms regarding the
performances, if any.


3JK Edition 1.00
Last Update: display time of the Performance Monitoring in the graphical
description and in the tabular description. This time changes after the Auto
Refresh.

period:
z loss of the Performance Monitoring data in the equipment

3JK Edition 1.00
13.4.8 CD counters

z Note: These values refer to the last refresh performed with the Refresh button in the Tool bar.

3JK Edition 1.00
13.4.9 Outgoing (History Data Table)

1) Click on the desired granularity (15 m or 24 h) on the History Data Table.

z Note: Use the arrows “Right” and “Left” in the lower part to pass from one log to another log in the history.

3JK Edition 1.00
13.4.10 HD Counters


3JK Edition 1.00
13.4.10 HD Counters [cont.]

z Note: How to Start/Stop the perfomance monitoring for a selected E1 in one-shot.

z 1) Click on PDH. The One-Shot Start/Stop PM panel will appear.
z 2) Select the E1 Port #.
z 3) Select the Signal type.
z 4) Select the Interval type.
z 5) Click on Start.

3JK Edition 1.00
13.4.11 Threshold tables
z This section describes how to display or change or create the threshold

tables assigned to Performance Monitoring counters.
z To view the available threshold for Performance Monitoring process,
the operator must select the Thresholds Tables node tree.
z There are two default threshold tables:
Threshold #1 (to be associated to 15 min report)
Threshold #4 (to be associated to 24 h report).


3JK Edition 1.00
13.4.12 How to create a new threshold table

z Note: Four threshold tables can be created (Threshold #2, #3 for 15 min report and #5 and #6 for 24 h
report).
z To create a new threshold table:

z 1) Click on the Threshold Tables. The Threshold Data Creation screen will appear, as shown in the figure
(E1 threshold).
z 2) Write the values for the Low and High thresholds.
z 3) Click on Create. Automatically the new threshold takes a name with a progressive number.

3JK Edition 1.00
13.4.13 How to change/delete a threshold table

z Note: Only the created thresholds can be modified or deleted. The default thresholds can be only
displayed.
z 1) Click on the Threshold to be modified in Threshold node tree (Threshold #2 in the example of the
figure).
z 2) Low and high thresholds for each counter are shown. Edit the new values in the table fields to change
them.
z 3) Click on the Apply button to confirm the changes or click on the Delete button to delete the threshold.

3JK Edition 1.00
z To each Performance Monitoring can be associated a Threshold Table.

z To associate a Threshold Table to an E1 stream three methods can be
used:
1) One-Shot Threshold association (from E1 threshold): with this method the
same Threshold Table is applied in one shot for the selected E1 streams, to
Incoming, Outgoing or both.
2) Specific E1 Port # association: with this method a Threshold Table is
applied only to a specific E1 stream, Incoming and Outgoing.
3) Specific E1 Port # Incoming or Outgoing: with this method a Threshold
Table is applied only to a specific E1 stream, Incoming or Outgoing.


3JK Edition 1.00
13.4.14.1 One-Shot Threshold association

z To associate a Threshold Table:

z 1) Click on E1 Threshold. The One-Shot Threshold Apply panel will appear.
z 2) Select the E1 Port #.
z 3) Select the the threshold to be associated to the 15min and/or 24h performance interval .
z 4) Click on Apply.

3JK Edition 1.00
13.4.14.2 Specific E1 Port # association


z 1) Click on the E1 Port #. The 15min&24h tab panel will appear.
z 2) In the Counter Thresholds field select the threshold to be associated and click on Apply.

3JK Edition 1.00
13.4.14.3 Specific E1 Port # Incoming or Outgoing
z Threshold association (Incoming)


z 1) Click on the E1 Port #. The 15min&24h tab panel will appear.
z 2) In the Counter Thresholds field select the threshold to be associated and click on Apply.

3JK Edition 1.00
13.4.14.3 Specific E1 Port # Incoming or Outgoing [cont.]
z Threshold association (Outgoing)


3JK Edition 1.00
Exercise
z 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


3JK Edition 1.00
Section 4
Maintenance
Module 1
Fault management
3JK Edition 1.00

3JK Edition 1.00
Blank Page

Maintenance · Fault management
Document History

3JK Edition 1.00
Objectives
perform the troubleshooting of the 9500 MPR.


3JK Edition 1.00
Objectives [cont.]


3JK Edition 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 27
1.1.3.1 Path Problems on a Commissioned Link 28
1.1.3.2 Path Problems on a New Link 30
1.1.4 Troubleshooting Configuration Problems 31
1.1.5 Troubleshooting Ethernet Problems 33
1.2 MSS Card removal and replacement 37
1.3 ODU removal and replacement 39
End of Module 40


3JK Edition 1.00
4·1·6

3JK Edition 1.00
1 Fault Management


3JK Edition 1.00
1 Fault Management
1.1 Troubleshooting
z This section provides guidance on:

Before Going to Site Checklist
Troubleshooting Basics
Troubleshooting Path Problems
Troubleshooting Configuration Problems
Troubleshooting Ethernet Problems


3JK Edition 1.00
1.1 Troubleshooting
1.1.1 Before Going to Site Checklist
z 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 (nonprotected, protected, diversity). Ask:
y Is just one 9500 MPR link affected, or a number of links in the same geographical
area?
y Is the path down completely or is traffic passing but with a BER alarm?
y Is only one or a number of tributaries affected?
y Could the fault be in the equipment connected to 9500 MPR, rather than in 9500
MPR? Are there alarms on other, connected equipment?
y Is it a hard or intermittent fault?
y Do alarms confirm which end of an alarmed link is faulty?
y Could the weather (rain, ice, high wind, temperature) be a factor in the reported
fault?

z 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 Edition 1.00
1.1 Troubleshooting
1.1.1 Before Going to Site Checklist [cont.]
Does link history suggest any fault trends?

y Does the fault history for the link indicate a likely cause?
y Is the 9500 MPR link newly installed?
y Has there been any recent work done on the link?
Ensure that you have with you:
y 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.
y 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).
y If login security has been enabled, you need the 'engineer' password for the local and
also any remote sites to be accessed.
y Any special test equipment that may be needed, such as a BER tester.
y Toolkit.
y Key(s) for access to the site.


3JK Edition 1.00
1.1 Troubleshooting
1.1.2 Troubleshooting Basics
z 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.
z 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.

z This section provides general guidance on 9500 MPR troubleshooting.

3JK Edition 1.00
1.1 Troubleshooting
1.1.2 Troubleshooting Basics [cont.]
z Table Alarm Matrix

Alarm Configuration/Alarm
Equipment Most Probable Cause Action
Description 1+0 1+1 HS 1+1 FD
Core-E Card Fail Major Minor Minor Core-E card failed Replace Core-E Card
Card
Equipment N/A Minor Minor Card in slot does not Install correct
Mismatch match card configured configured card
in Core-E memory
Card Missing N/A Minor Minor Core-E card is missing Install Core-E Card in
from slot slot
Unconfigured N/A Minor Minor Card in slot is not Provision card
Equipment provisioned (enabled)
LOS on ETH Minor Minor Minor No Ethernet input signal Check link partner and
TMN Interface detected on ETH 4 on cable between link
Core-E Card partner and ETH 4
connector
PPP IP Fail Minor Minor Minor
continue


3JK Edition 1.00
1.1 Troubleshooting
Core-E LOS on Gigabit Major Minor Minor Loss of Ethernet is Check link partner and
Card ETH Interface detected on ETH 1-4 on cable between link
Core-E Card partner and ETH 1-4
connector
Firmware Minor Minor Minor Status of download Wait for downloading
Download In to complete
Progress
LOS on Sync Minor Minor Minor No sync clk detected at Check sync source and
Interface Sync in port on Core-E cable between sync
Card source and Sync in port
Degraded Signal Minor Minor Minor Sync clk errors detected Check sync source for
on Sync at Sync in port on Core-E errors
Interface Card
License Major Major Major Wrong flash card Install correct flash
Mismatch for installed on Core-E Card card for license
Equipment
Provisioned
continue


3JK Edition 1.00
1.1 Troubleshooting
E1 Access Card Fail Major Minor Minor Failure of E1 Access Card Replace E1
Card Access Card
Equipment Major Minor Minor Card in slot does not match Card Install correct
Mismatch configured in Core-E memory configured card
Card Missing Major Minor Minor E1 Access Card is missing from Install E1 Access
slot Card in slot
Unconfigured Major Major Major Card is not Enabled on the Enable card
Equipment Settings screen
LOS on PDH Major Minor Minor No E1 input signal detected on Check E1 source
Tributary any one or more of 32 lines and/or cable
Degraded Minor Minor Minor Errors on input signal detected Check E1 source
Signal on any one or more of 32 lines
AIS on PDH Major Major Major AIS detected by the receive Check for
Tributary (RX) circuits on one or more E1 lines, upstream E1
indicating upstream failure source for errors
continue


3JK Edition 1.00
1.1 Troubleshooting
E1 Access AIS on PDH Major Major Major AIS detected on one or Check E1 source
Card Tributary (TX) more E1 lines at input to
PDH 32xE1 Access Card
Loss of Major Major Major Packets are not being 1.Check/troubleshoot
CESoETH Frame received by the farend alarms
emulation circuits 2.Replace alarmed E1
Access Card
Jitter Buffer Major Major Major Packet overflow causing 1. Verify sync
Overrun buffer spill. Could be provisioning at both
caused by sync problem ends of hop
or E1 Access Card circuit 2. Replace alarmed E1
failure Access Card
2. Troubleshoot sync
problem between local
and farend
continue


3JK Edition 1.00
1.1 Troubleshooting
Configuration/Alarm
Equipment Alarm Description Most Probable Cause Action
1+0 1+1 HS 1+1 FD
E1 Access Jitter Buffer Major Major Major Buffer spill. Could be 1.Verify sync
Card Underrun caused by sync provisioning
problem or E1 Access at both ends of hop
Card circuit failure 2.Replace alarmed
E1 Access Card
3.Troubleshoot sync
problem between
local and farend
Firmware Download Minor Minor Minor Status of download Wait for
In Progress downloading to
complete
Fans Unit Card Fail Major - - Fan failed Replace fan unit
Card Missing Major - - Fan unit is missing Install fan unit

from slot
Unconfigured Minor Minor Minor Unit is not Enabled on Enable fan unit
Equipment the Settings screen
continue


3JK Edition 1.00
1.1 Troubleshooting
Radio Card Fail Major Minor Minor Radio Access Card failed Replace radio Access
Access 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 Radio Access Card is Install Radio Access
missing from slot Card in slot
Unconfigured Minor Minor Minor Card is not Enabled on Enable card
Equipment the Settings screen
MSS-ODU Cable Major Minor Minor Bad cable connection at Check/repair IF cable
Loss IF in/out connector on connection on alarmed
Radio Access Card Radio Access Card
continue


3JK Edition 1.00
1.1 Troubleshooting
Radio Loss of Radio Minor Minor Minor Far-end equipment 1.Switch far-end XMTRs
Access Frame problems, RF path (in a protected
Card problems, or local system). If alarm
circuit failures have clears, replace far-end
caused BER to increase off-line Radio Access
to the point that frames Card.
are being lost 2.Check/troubleshoot
far-end alarms
3.Replace alarmed
Radio Access card
Loss of N/A Minor Minor Delay between main and 1.Replace main Radio
Alignment protect RF paths Access Card
detected 2.Replace protect
Radio Access Card
3.Replace main ODU
4.Replace protect ODU
continue


3JK Edition 1.00
1.1 Troubleshooting
Radio Demod Major Minor Minor Internal receive circuit Replace Radio Access
Access Function Fail failure Card
Card
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 existing
on modem weather-related
problems
2.Verify RSL is above
Receiver threshold.
If not – check upstream
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 Edition 1.00
1.1 Troubleshooting
Radio ATPC Loop Minor Minor Minor Loss of ATPC command 1.Switch far-end XMTRs
Access path between far-end (in a protected
Card XMTR and local RCVR system).
If alarm clears, replace
far-end off-line Radio
Access Card
2.Check/troubleshoot
far-end alarms
3.Replace alarmed
Radio Access Card
Link Identifier Major Major Major Link identifier number Set numbers at both
Mismatch provisioned on Radio ends of hop to match
Access Card settings
screen is different from
link identifier number
provisioned at other end
of hop
continue


3JK Edition 1.00
1.1 Troubleshooting
Radio TCA on Radio N/A N/A Major Alarm threshold 1.Switch far-end XMTRs
Access Link exceeded on standby (in a protected
Card Radio Access Card system). If alarm
clears, replace far-end
off-line Radio Access
Card
TCA on Radio Major N/A Minor Alarm threshold
Hop exceeded on standby
Radio Access Card after
switching from main to
standby
UAT on Radio N/A N/A Major 10 consecutive SES 1.Switch farend XMTRs
Link (unavailable time (in a protected
period) detected on system). If alarm
main Radio Access Card clears, replace farend
off-line Radio Access
Card
continue

z TCA – Threshold Crossing Alarm

z UAT – Un-Available Time

3JK Edition 1.00
1.1 Troubleshooting
Radio UAT on Radio Major N/A Minor 10 consecutive SES
Access Hop (unavailable time period)
Card detected on standby Radio
Access Card after switching
from admin to standby
Firmware Minor Minor Minor Download status Wait for
Download In downloading to
Progress complete
LOS on Sync Minor Minor Minor Loss of sync clock detected 1.Replace Radio
Interface Access Card
Degraded Signal Minor Minor Minor Bit errors have increased 1.Replace Radio
and have exceeded Access Card
degraded signal threshold
License Major Major Major Modem card type does not Replace Radio Access
Mismatch for match card type stored in Card with correct
Equipment memory on the Core-E Card card
Provisioned flash card
continue

z TCA – Threshold Crossing Alarm

z UAT – Un-Available Time

3JK Edition 1.00
1.1 Troubleshooting
ODU 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 RCVR circuit failed Replace ODU
Fail
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 Edition 1.00
1.1 Troubleshooting
ODU Software Minor Minor Minor Software version on ODU Download correct
Mismatch does not match software software version
version on Core-E
ODU Not Minor Minor Minor Loss of communication 1.Replace ODU
Responding with ODU 2.Replace alarmed
Radio Access Card
Firmware Minor Minor Minor Download status Wait for downloading
Download In to complete
Progress


3JK Edition 1.00
1.1 Troubleshooting
Check the basics first.

y 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.
y 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 Edition 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:
y 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 Core-E, their settings cannot be loaded. The fault may be at the hardware device
(most likely), communications to it, or the Core-E.
y Hardware/software compatibility alarms will be raised when a new plug-in is
installed that needs a later version of 9500 MPR software.
y 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 Edition 1.00
1.1 Troubleshooting
1.1.3 Troubleshooting Path Problems
z 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 signalled 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.

z Note: A path extends from ODU antenna port to ODU antenna port.

3JK Edition 1.00
1.1.3.1 Path Problems on a Commissioned Link
z A path problem on an existing link, one that has been operating

satisfactorily may be caused by:
Weather-related path degradation
y 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
y If RSLs do not return to commissioned levels after a period of exceptionally strong
winds, suspect antenna alignment.
y 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
y 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 Edition 1.00
1.1.3.1 Path Problems on a Commissioned Link [cont.]
Interference from other signal sources

y 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 Edition 1.00
1.1.3.2 Path Problems on a New Link
z For a new link, potential problems can extend to also include:

Incorrect antenna alignment
y One or both antennas incorrectly aligned. Refer to Installation alignment procedure.
Mismatching antenna polarizations
y 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
y 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
y 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 Edition 1.00
1.1 Troubleshooting
1.1.4 Troubleshooting Configuration Problems
z 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
y 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
y 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)
y Take extra care when configuring ring circuits.
y Where the problem is not obvious, use the tributary loopback BER test to track a
single circuit through a 9500 MPR network, beginning at the node closest to the node
applying the BER test.


3JK Edition 1.00
1.1 Troubleshooting
1.1.4 Troubleshooting Configuration Problems [cont.]
Incorrect ID naming, and commissioning

y All traffic-carrying circuits must have a unique flow ID for the cross-connect
capability to operate.
Incorrect/incompatible trib settings
y Trib line interface settings incorrect, or line levels incompatible. While no alarm
activates for an incorrect setting, its effect may result in ine levels being too low
(LOS alarm), or too high, resulting in a high BER.
ATPC settings
y Ensure ATPC settings are correct, specifically that the target fade margin allows
adequate headroom for local Tx power, while ensuring an adequate fade margin.


3JK Edition 1.00
1.1 Troubleshooting
1.1.5 Troubleshooting Ethernet Problems
z The most common Ethernet problems are network and connectivity

related and therefore always check the following first:
Verify link partner capability, provisioning, and connection
Verify radio provisioning matches link partner
Verify cabling between radio and link partner
z The LEDs on the Core-E Card front panel for each Ethernet connector
are a good indicator of correct connectivity and activity on the
Ethernet port.

z This section gives general guidance on troubleshooting problems related to the four Ethernet ports on the
Core-E Card.
z Refer to table “Troubleshooting Ethernet Problems” on next slides for detail troubleshooting using the LEDs
locally at the alarmed site.

3JK Edition 1.00
1.1 Troubleshooting
1.1.5 Troubleshooting Ethernet Problems [cont.]
LED Indication Probable Cause Corrective Action

ETH IN Green LED Loss of Ethernet RCV/radio XMT 1.Check local Ethernet provisioning
LOS Not Lit signal in. Most probable causes: screen.
1.Cable between link partner and 2.Check link partner provisioning.
radio is disconnected/broken.
Connect/repair cable.
2.Speed/Mode provisioning
mismatch between link partner
and radio
continue


3JK Edition 1.00
1.1 Troubleshooting
LED Indication Probable Cause Corrective Action

ETH OUT Green LED Loss of Ethernet XMT/radio
LOS Not Lit RCV signal out. Most probable
causes:
1.Loss of RF input to radio Check local RSL screen on CT. Is RSL ok?
Access Card Yes - Check farend for Ethernet alarm.
No - Check farend Tx output. Is farend Tx Out
ok?
Yes - Check path, antenna,
waveguide/cabling
No - Check/replace farend radio Access Card.
2.Loss of Ethernet input to Check farend for Ethernet alarms.
radio Access Card Are any alarms indicated?
Yes - Troubleshoot farend alarms
No - Check farend Ethernet status. Is only
abnormal status indicated?
Yes - Troubleshoot farend Ethernet status.
No -
1.Replace local alarmed Core-E Card.
2.Replace local radio Access Card.


3JK Edition 1.00
1.1 Troubleshooting
z 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 Core-E Settings
Screen)
3 - Speed and mode (on Core-E Settings Screen) must be provisioned the same
as the link partner.
z The yellow LED opposite the green on the connector indicates activity
only.
z The flashing yellow LED is not an indicator of signal type or quality.


3JK Edition 1.00
1 Fault Management
1.2 MSS Card removal and replacement
z 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.
z 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.
z 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 con-nector and/or damage to the plug-in
connector.

z All plug-in cards can be removed and installed with power applied.

3JK Edition 1.00
1 Fault Management
1.2 MSS Card removal and replacement [cont.]
z 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.
z 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 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.
z 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 Edition 1.00
1 Fault Management
1.3 ODU removal and replacement
z Get a spare unit with the same P/N.

z Disconnect the MSS-ODU cable.
z Change the ODU.
z Reconnect the MSS-ODU cable.
z Check with the CT that there are no alarms.

z Note for 1+1 configurations:

z 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 Edition 1.00
End of Module
Fault management


3JK Edition 1.00
Section 4
Maintenance
Module 2
Software download
3JK Edition 1.00

3JK Edition 1.00
Blank Page

Maintenance · Software download
Document History

3JK Edition 1.00
Objectives
download a new software version.


3JK Edition 1.00
Objectives [cont.]


3JK Edition 1.00
Table of Contents
Page
1 Software download menu 7
Server Access Configuration 8
Init Software Download 9
Software Status 10
End of Module 12


3JK Edition 1.00
4·2·6

3JK Edition 1.00
1 Software download menu


3JK Edition 1.00
Server Access Configuration
z An FTP server can be used to speed up the software download to the

NE.
z This menu allows to configure an FTP server on which the previously
loaded software will be downloaded.
z Copy the SW file present in the software CD on the FTP server.
Server access configuration screen

zUser Id and Password are the login information to access the FTP server.
zIn the Address field write the IP address of the FTP server.
zIn 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.
zBy clicking on the Set Default button, the server access values will be filled in automatically with the
default configuration.
zThe CT is the default FTP server with the following parameters:

z User Id: anonymous
z Password: -
z Address: local host IP address.
z Port: 21
z 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 Edition 1.00
Init Software Download
z To start download select the

desired software version 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).
z When the Software Download

starts a screen, showing the in
progress operation of the
download, appears. Download is
aborted when the Abort button is
pressed.
Init Software Download screen

zUsing this menu, software is downloaded to the NE in order to upgrade the NE software version.
zNote: If the Forced download is not selected, the system will compare the software to be downloaded with
the software present in the NE and will proceed with the download operation only if the versions are
different.
zThe Add button must be used to display another software file (extension DSC) in this screen to be then
downloaded.
zThe Delete button must be used to delete a software file in this screen.
NOTE
zThis screen displays the software packages previously stored.
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 Edition 1.00
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

zThis menu gives the information of the software installed in the NE.
zThe following information is displayed:
z Name: software name
z Version: software version
z Operational state: enabled or disabled
z Current status: committed or standby
The committed status refers to the software currently in use
z The Flash Card, which stores the NE software, contains 2 banks.

z 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.
zDuring download, necessary to update the software version, the download file is automatically stored in the
standby bank.
zTo 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.
z By selecting Forced Activation the bank to be activated is forced to restart.
z By selecting Activation the bank to be activated restarts only if the content of the two banks differ.

3JK Edition 1.00
Software Status [cont.]
Software Units Details screen

zThe following information is displayed on the screen:

z EC: software on the Equipment Controller
z OC_R: software on the ODU Controller (Radio)
z FDUFF, FCERE, FGUIN: FPGA firmware version
z MDPAR: firmware version of the FPGA involved in the MSS/ODU communication channel

3JK Edition 1.00
End of Module
Software download


3JK Edition 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

9500MPR R 1.2.1 Operation and Maintenance

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

9500MPR R 1.2.1 Operation and Maintenance

Încărcat de

Drepturi de autor:

Formate disponibile

9500 MPR

9500MPR R 1.2.1 Operation and

All Rights Reserved © Alcatel-Lucent 2009

All rights reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

2 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

4 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

5 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

9500MPR R 1.2.1 Operation and Maintenence

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

Welcome to 9500MPR R 1.2.1 Operation and Maintenence

Upon completion of this course, you should be able to:

z Configure and manage the 9500MPR

7 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

8 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

9 Where you can get further information

9500MPR R 1.2.1 Operation and Maintenence

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

All Rights Reserved © Alcatel-Lucent 2009

z Switch to notes view!

10 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

Did you meet the following objectives ?

Yes (or No (or

All Rights Reserved © Alcatel-Lucent 2009

Switch to notes view!

Yes (or No (or

12 All Rights Reserved © Alcatel-Lucent 2009

Thank you for your answers to this questionnaire

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © 2007, Alcatel-Lucent

1·1·2 All Rights Reserved © Alcatel-Lucent 2009

Edition Date Author Remarks

01 2007-07-30 External Consultant First edition

All Rights Reserved © 2007, Alcatel-Lucent

1·1·3 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © 2007, Alcatel-Lucent

1·1·4 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © 2007, Alcatel-Lucent

1·1·5 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © 2007, Alcatel-Lucent

Switch to notes view!

9500 MPR · 9500MPR R 1.2.1 Operation and Maintenence

All Rights Reserved © 2007, Alcatel-Lucent

1·1·7 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © 2007, Alcatel-Lucent

Alcatel-Lucent microwave product acronyms are derived as

1·1·8 All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © 2007, Alcatel-Lucent

z The 9500 MPR innovative solutions mainly are:

1·1·9 All Rights Reserved © Alcatel-Lucent 2009