9500MPR Terminal Configuration Operation and Maintenance
9500MPR Terminal Configuration Operation and Maintenance
STUDENT GUIDE
All Rights
9500 MPR (Microwave Packet Reserved © Alcatel-Lucent
Radio) R 3.1 2011
Terminal Configuration Operation and
Maintenance (ETSI) - Page 1
Empty page
All Rights
9500 MPR (Microwave Packet Reserved © Alcatel-Lucent
Radio) R 3.1 2011
Terminal Configuration Operation and
Maintenance (ETSI) - Page 2
Terms of Use and Legal Notices
1. Safety Warning
Switch to 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 2011 All Rights Reserved © Alcatel-Lucent 2011
9500 MPR
9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
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.
All Rights
9500 MPR (Microwave Packet Reserved © Alcatel-Lucent
Radio) R 3.1 2011
Terminal Configuration Operation and
Maintenance (ETSI) - Page 3
Blank Page
All Rights
9500 MPR (Microwave Packet Reserved © Alcatel-Lucent
Radio) R 3.1 2011
Terminal Configuration Operation and
Maintenance (ETSI) - Page 4
Course Outline
1. NEThis
About operation
Course 4. Topic/Section is Positioned Here
Course Module
outline 1. 3JK Operator Interface MPR Tterminal
Technical support
Module 2. 3JK Initial Configuration MPR Terminal
5. Topic/Section is Positioned Here
Course Module
objectives
3. 3JK Performance Monitoring MPR Terminal
2. Maintenance
1. Topic/Section is Positioned Here 6. Topic/Section is Positioned Here
Xxx Module 1. 3JK Fault Management
Xxx Module 2. 3JK Software Download 7. Topic/Section is Positioned Here
Xxx
All Rights
9500 MPR (Microwave Packet Reserved © Alcatel-Lucent
Radio) R 3.1 2011
Terminal Configuration Operation and
Maintenance (ETSI) - Page 5
Course Outline [cont.]
6
9500 MPR
This page is left blank intentionally
All Rights Reserved © Alcatel-Lucent 2011
9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
All Rights
9500 MPR (Microwave Packet Reserved © Alcatel-Lucent
Radio) R 3.1 2011
Terminal Configuration Operation and
Maintenance (ETSI) - Page 6
Course Objectives
All Rights
9500 MPR (Microwave Packet Reserved © Alcatel-Lucent
Radio) R 3.1 2011
Terminal Configuration Operation and
Maintenance (ETSI) - Page 7
Course Objectives [cont.]
All Rights
9500 MPR (Microwave Packet Reserved © Alcatel-Lucent
Radio) R 3.1 2011
Terminal Configuration Operation and
Maintenance (ETSI) - Page 8
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.
9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
All Rights
9500 MPR (Microwave Packet Reserved © Alcatel-Lucent
Radio) R 3.1 2011
Terminal Configuration Operation and
Maintenance (ETSI) - Page 9
About this Student Guide [cont.]
All Rights
9500 MPR (Microwave Packet Reserved © Alcatel-Lucent
Radio) R 3.1 2011
Terminal Configuration Operation and
Maintenance (ETSI) - Page 10
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 :
Switch to notes view!
Number of trainees : Location :
Surname, First name :
2 To be able to:
11
• Describe the main functionalities All Rights Reserved © Alcatel-Lucent 2011
9500 MPR of the 9500MPR
9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
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
All Rights
9500 MPR (Microwave Packet Reserved © Alcatel-Lucent
Radio) R 3.1 2011
Terminal Configuration Operation and
Maintenance (ETSI) - Page 11
Self-assessment of Objectives [cont.]
Other comments
All Rights
9500 MPR (Microwave Packet Reserved © Alcatel-Lucent
Radio) R 3.1 2011
Terminal Configuration Operation and
Maintenance (ETSI) - Page 12
Do not delete this graphic elements in here:
Section 1
NE operation
Module 1
Operator Interface MPR Terminal
3JK Issue 2.0
9500 MPR
9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
TWT63044-R 3.1-SG1-SEN- I1.0 Issue 1.00
Document History
Page
Switch to notes view!
1 MPT Craft Terminal 7
1.1 Starting with NETO 8
1.2 Main View 10
1.3 Suggested sequence for MPT CT interface 11
Blank Page 12
2 Main View 13
2.1 Main view 14
2.2 Line NE Status 17
2.3 Main Tool Bar Area 18
2.4 Alarms Synthesis Panel 19
2.5 General Information Panel 21
2.6 Main Tab Panel 22
2.7 Navigator Area 29
2.8 MCT Menus 31
Blank Page 32
3 System Overview 33
3.1 System Overview Display 34
3.2 Alarm Symbol & Alarms Tab Panel 35
Blank Page 40
4 Commissioning Perspective 41
4.1 Commissioning Perspective Navigation 42
Blank Page 46
5 Inventory Tool 47
5.1 Inventory Tool 48
1 · 16· 5Software Download Tool All Rights Reserved © Alcatel-Lucent 2011 51
6.1 Software Download
NE operation · Operator Interface MPR Tterminal
Tool
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI) 52
Blank Page 54
7 Configuration Tool 55
7.1 Configuration Tool 56
7.2 Date/Time Configuration 60
7.3 Site Information 61
7.4 Protection Configuration 62
7.5 Synchronization Configuration 64
7.6 Radio Configuration 68
7.6.1 Telecommunication Standard 71
7.6.2 Modulation 72
7.6.3 Transmit Power Control 78
7.6.4 Frequency 83
7.7 Advanced Radio 85
7.8 MSS-1c Provisioning 87
7.9 Ethernet Traffic QoS Configuration 93
7.9.1 QoS Classification 96
7.9.2 Ether Type Classification 97
7.9.3 Scheduling Algorithms 98
7.9.4 IEEE 802.1p Classification 99
7.9.5 Diffserv Classification 100
7.10 Networking Configuration 104
7.10.1 Network Interfaces Configuration 105
7.10.2 Static Routing Configuration 109
7.10.3 Trusted SNMP Managers Configuration 113
7.11 Backup/Restore NE Configuration 116
Blank Page 120
8 Monitoring Tool 121
8.1 Monitoring Tool 122
8.2 Alarms 124
Page
Switch to notes view!
8.3 Power Measurements 129
8.3.1 Start/Stop Monitoring 131
8.3.2 Power Measurements Graphic 133
8.3.3 Power Measurements Curves Management 135
8.3.4 Export Power Measurements Data 139
8.4 Modem Measurements 141
8.4.1 Start/Stop Monitoring 143
8.4.2 Mean Square Error 145
8.4.3 Modem Measurements Graphic 146
8.4.4 Modem Measurements Curves Management 148
8.4.5 Export Modem Measurements Data 149
Blank Page 150
9 Maintenance Perspective 151
9.1 Maintenance Perspective Navigation 152
9.2 Inventory Tool 154
9.3 Software Download Tool 155
9.4 Radio Tool 156
9.5 Alarms Tool 157
9.6 Power Measurements Tool 158
9.7 Modem Measurements Tool 159
Blank Page 160
10 Troubleshooting Perspective 161
10.1 Troubleshooting Perspective Navigation 162
10.2 Inventory Tool 164
1 · 1 · 610.3 Troubleshooting Tool All Rights Reserved © Alcatel-Lucent 2011 165
10.4 Alarms Tool
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI) 172
10.5 Power Measurements Tool 173
10.6 Modem Measurements Tool 174
10.7 Events Tool 175
11 Performance Monitoring Perspective 179
11.1 Performance Monitoring Perspective Navigation 180
Blank Page 182
12 MSS-1c Provisioning Tool - Main View 183
12.1 Main view 184
12.2 Main Tool Bar Area 185
12.3 Main Tab Panel 186
12.4 Navigator Area 187
12.5 Provisioning Tool Menus 188
13 MSS-1c Provisioning Tool - Configuration Perspective 189
13.1 Configuration Perspective Navigation 190
13.2 File Management Tool 192
13.3 MSS-1c Provisioning Tool 196
13.4 Ethernet Port Provisioning 197
13.5 PDH Port Provisioning 201
13.5.1 PDH Port Setting 202
13.5.2 Information on Circuit Emulation 203
13.5.3 Circuit Emulation Application Examples 208
13.6 Management Port Provisioning 210
13.7 TDM Cross-Connection:Radio<->Users Ports 213
13.8 Network Synchronization Clock 219
13.9 Bridge Provisioning 223
13.10 Port VLAN Provisioning 229
13.11 Storm Control and Rate limiting 232
13.12 Per Flow policer 233
Exercices 234
Blank Page 235
End of Module 236
o NETO
opens
N.B.
To access the NE the PC must be configured to “Get automatically an IP address”, because the NE is
configured as DHCP Server with default IP address 192.168.30.1 and subnet mask 255.255.255.252. The
PC Ethernet port must be connected to the CT connector of the MSS-1c.
N.B.
192.168.30.1 is the IP address of the port from MSS-1c and cannot be modified. The management can be
done also by the NMS port, but the PC must be configured with fixed IP and gateway. First open the
WebEML and after connect the cable.
Warning:
Without the MPT connected to the MSS-1c, it is not possible to open the WebEML on the CT port from MSS-
1c.
Warning:
If all the WebEML images/icons are missing, check that file “msimg32.dll” is present in <System32>.
q When the
NE is
supervised,
click on
<Show>
Note: Default User Accounts – at the NE installation time, one default user account is created on NE
independently from the SNMP operating mode.
z Profile: administrator
z Username: admin
z Password: admin
MPR-e
MSS-1c
z The 9500MPT Craft Terminal (MCT) is the starting point of the CT application.
z MCT functions require to know the NE identity by means of the related IP Address.
z Only one NE can be managed in a MCT session.
z The User Interface is provided by the MCT Main View.
z The MCT connects to the 9500MPT with a transparent DHCP server which is not configurable.
z 1. Fill the “IP address or DNS name” field with the NE IP address;
MSS-1c
RESOURCE AREA
NAVIGATOR
GENERAL
INFORMATION
LINE NE STATUS
1 · 1 · 15 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
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.
RESOURCE AREA
NAVIGATOR
GENERAL
INFORMATION
LINE NE STATUS
1 · 1 · 16 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
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.
Line NE Status
z N.B. The meaning of the icons in the Severity alarms 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.
z 5) IND - Indeterminate alarm
z Synthesis of alarms not associated with the previous severities. Not operative.
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:
1) EQP – Equipment alarm
y Synthesis of alarms of the Equipment domain.
2) COM – Communication alarm
y Synthesis of alarms of the Communication domain.
General Information
z The operator choice in the Main Tab Panel makes changes in the contents of:
z 1) Navigator Area
This area displays all the available tasks for a specific tool (perspective).
z 2) Resource area
This area displays a representation in tabular view or in graphical view of the selected resource for a
specific tool (perspective).
z Operator facility:
By moving the margin, we can see all the opened tools (perspectives)
Perspective Menu
Perspective Menu
Customize
Perspective Menu
Save As
Reset
z Show Text ON
Navigator Area
z The Navigator Area displays all the available management tasks for a
specific tool (Perspective).
The following tools are present:
y Commissioning (to provision, to configure the equipment)
y Maintenance (to perform Maintenance tasks on the equipment)
y Troubleshooting (to perform Troubleshooting tasks on the equipment)
y Performance (to perform the Performance Monitoring on the equipment)
Button Policy
z Apply
this button activates the “modify”, but it does not close the window.
z Cancel
this button closes the window without modifying the parameters displayed in the window.
z OK
this button activates the modify and closes the window
z Close
this button closes the window
z Help
this button provides the help management for the functions of the supporting window.
z 1) FILE –
One choice: to exit the MCT.
z 2) WINDOW –
One choice: Operator’s preference to display the windows.
z 3) HELP –
One choice: to have an help on MCT.
Windows Menu
Help Menu
Configuration Details
Plug-in Details
All Rights Reserved © Alcatel-Lucent 2011
3JK Issue 2.0
Section 1 · Module 1 · Page 31
Blank Page
z The “System Overview” of the MCT Main View displays a global logical
view (strictly related to the physical implementation) highlighting a
synthesis of all the alarms and statuses present in the system.
MPR-e
MSS-1c
NOTE:
The “Refresh” button updates the display of the “System Overview” view.
MSS-1c Alarm
MPT-MC Alarm
Inventory
Software Download
Configuration
y Date/Time
y Site Information
y Protection
y Radio
y Advanced Radio
y MSS-1c
Networking
y Network Interfaces
y Static Routing
y Trusted SNMP Managers
Monitoring
y Alarms
y Power Measurements
y Modem Measurements
Inventory
Software Download
Configuration
y Date/Time
y Site Information
y Protection
y Synchronization
y Radio
y Advanced Radio
y Ethernet Traffic QoS
Networking
y Network Interfaces
y Static Routing
y Trusted SNMP Managers
Monitoring
y Alarms
y Power Measurements
y Modem Measurements
y Events
• The Remote
Inventory feature
stores information
used to identify
all product
components.
1 · 1 · 48 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
Configuration Tool
Date/Time
Site Information
Protection
Radio
Advanced Radio
MSS-1c
Networking (Network Interfaces, Static Routing, Trusted SNMP Managers)
Configuration Tool
Date/Time
Site Information
Protection
Synchronization
Radio
Advanced Radio
Ethernet Traffic QoS
Networking (Network Interfaces, Static Routing, Trusted SNMP Managers)
z The NE local time can be displayed and/or re-aligned to the Computer time basis.
z The SNTP NE Time Synchronization field permits to configure the SNTP Servers regarding the NTP
(Network Time Protocol).
z To enable this feature, click on SNTP Enabled (enabled/disabled);
z Then, configure the IP address of the Main Server, which distributes the time to all the NEs in the
network;
z And, configure the IP address of the Spare Server (IP address of a second NTP Server), which replaces
the Main Server in case of failure.
z Note: If a change of Change Time Zone on the PC is applied with the MCT opened, in order to make it
updated on CT Close/Open the MCT application and Read Time another time.
Site Name
Site Location
of the equipment
Synchronization
tab panel
Mobile
2G,3G,4G
9500 MPR
SvncE D Eth SyncE D
Eth
9500 MPR
Private
Business
Office
9500 MPR
9500 MPR
Time delivery Time source
options options
Fixed
DSL
Transparent Transparent
1588v 1588v2
transport of transport of
Phone 2 TOD TOD
protocol protocol
z All the NEs radios in the network must be synchronized to the same clock.
z One radio in the network is provisioned Master.
z All other radios in the network must be provisioned Slave.
z The slave radios all sync to the clock provided by the master.
SynchrE: Any Synchronous Ethernet clock source available at enabled User Ethernet traffic interfaces (both
electrical and optical) configured in synchronous operation mode (the specific User Ethernet port has to
be chosen).
z From ITU-T G.8264 point of view, the MSS is a Synchronous Ethernet equipment equipped with a
system clock (NEC) following the ITU-T G.8262 recommendation.
z A User Ethernet interface configured in synchronous operation mode can work only at 1Gigabit/s.
z In the particular case of electrical User Ethernet interfaces, these interfaces perform link auto
negotiation to determine the master and slave clocks for the link.
z The clock slave role must be configured as part of auto negotiation parameters in order to use the
interface as Synchronous Ethernet clock source.
Synchronization Configuration
z PCR configuration
(Proprietary Clock Recovery): the time stamp
inside the Ethernet frame is used.
Fill in the corresponding Source and Destination
Mac Address
z SyncE configuration
With this mode for the electrical interface the
selection among Autonegotiation/Master/Slave
must be performed.
Choose the role of the NE for the synchronization
(Automatic, Master, Slave)
Radio
tab panel
1/2
z The Radio Configuration view allows the operator to manage the resources of the radio transmission
channel.
z A Radio NE consists of one or two radio channels with a set of functional blocks (tributary ports, radio
ports etc).
Radio
tab panel
2/2
z The Radio Configuration view allows the operator to manage the resources of the radio transmission
channel.
z A Radio NE consists of one or two radio channels with a set of functional blocks (tributary ports, radio
ports etc).
Telecommunication Standard
Modulation
Transmit Power Control
Frequency
z Channel Spacing:
z 3,5 MHz
z 7 MHz
z 14 MHz
z 28 MHz
z 40 MHz
z 56 MHz
z Reference Modulation:
z QPSK
z 8 PSK
z 16 QAM
z 32 QAM
z 64 QAM
z 128 QAM
z 256 QAM
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.
z Channel Spacing:
z 3,5 MHz, 7 MHz, 14 MHz, 28 MHz, 40 MHz, 56 MHz
z Reference Modulation:
z QPSK, 16 QAM, 32 QAM, 64 QAM
Capacity Up-Grade
In this case all the pre-configured TDM2TDM or TDM2ETH will be kept.
The residual bandwidth for the lowest modulation scheme is recomputed.
Capacity Down-Grade
If all the pre-configured TDM2TDM or TDM2ETH stays in the capacity
associated to the new modulation scheme:
y they will be kept,
y the residual bandwidth for the new modulation scheme is recomputed.
If all the pre-configured TDM2TDM or TDM2ETH cannot stay in the capacity
associated to the new modulation scheme:
y 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.
z Modulation Change
Capacity Up-Grade
When the admission control is enabled,
all the pre-configured TDM2TDM or TDM2ETH are kept.
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
When the admission control is enabled,
all the pre-configured TDM2TDM or TDM2ETH will be kept.
When the admission control is disabled,
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 Adaptative Modulation engine changes the modulation, the pre-configured TDM2TDM or TDM2ETH
traffic must be managed according to the behavior here after described. Two cases must be taken into
account: Capacity Up-grade and Capacity Down-Grade.
z A specific behavior must be followed when it is needed to move from Adaptive Modulation to Fixed
Modulation or vice-versa, in order to preserve any pre-configured TDM2TDM or TDM2ETH. Two cases must be
taken into account: from Fixed to Adaptive Modulation and from Adaptive to Fixed Modulation. The working
mode changes, here below described, are generic. The changes cover both the change of the modulation
but with the same Channel Spacing and the change of the Channel Spacing.
• Consequence in Monitoring/Alarms
z The information related to the transmitter status is shown by an icon closed to the Mute field. To
squelch the transmitter tick on Mute field and press Apply button.
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. After the setting, click on <Apply>
z Select in the
<Driving Remote RSL in 1+1 – HSB>
field the suitable value.
The system can operate with different types of ODU according to the RF band and to
the channel arrangement. There are ODUs which can manage only one shifter or
several predefined shifters.
In the Shifter field select the suitable shifter.
In the Tx frequency field insert the suitable Tx frequency (the Rx frequency is
automatically calculated by using the inserted Tx frequency and the shifter).
Note: The “Tick” button <Allow Rx Frequency Tuning> permits to change both the Tx
and Rx Frequencies.
The middle field is used to set a frequency inside the allowed frequency range given by the ODU
represented by the left and right fields.
z By clicking on ,
you can display the associated frequency plan of the connected ODU according
to the Radio channels frequencies configuration (Shifter, Tx Frequency, Rx
Frequency) with, in red, the channel spacing configured in Modulation field.
The middle field is used to set a frequency inside the allowed frequency range given by the ODU
represented by the left and right fields.
z Click on the “Start Tool” button to run the < Provisioning Tool >
application
z The < Provisioning Tool > application is explained later in this document
z This field allows to configure the FTP server to be used to download the
<MSS-1c Configuration File> to the NE.
zIn the Server Address field write the IP address of the FTP server.
zUser Name and Password are the login information to access the FTP server.
zIn the Port field write the port to be used.
zBy clicking on the Check button, the server access values will be filled in automatically with the default
configuration.
zNote: If as FTP Server the Apache Server, available on the TCO Software Suite Rel. 4.4 DVD-ROM, is used,
enter the following parameters:
z Server address: PC address
z Username: anonymous
z Password: anonymous
z Port: 21
2. Then, click on the Download and Execute button to begin the download process.
3. When the <MSS-1c Configuration File> download starts, a screen showing the in progress operation of the
download appears. The download is aborted if the Abort button is pressed.
4. Click Ok.
3. When the ACTIVE MSS-1c operational parameters upload starts, a screen showing the in progress operation
of the upload appears. The upload is aborted if the Abort button is pressed.
4. Click Ok.
IEEE 802.p
None Diffserv
z Quality Of Service
The Ethernet switch provides a Quality of Service mechanism to control all
streams. If the QoS is disabled, all traffic inside the switch has the same
priority, this means that for each switch port there is only one queue (FIFO)
therefore the first packet that arrives is the first that will be transmitted.
DEFAULTS VALUES:
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:
Scheduling Algorithms
Diffserv Classification
Notes:
z You can choose the “Defaults” values
z The highest priority queue is 5
z The highest priority queue corresponds to the transmission of packets whose
diffserv classification priority is the highest (range of diffserv priority values).
z The next queue does not contain the range of diffserv priority values of the
previous queue.
z The range of diffserv priority values has to be set in ascending order
corresponding to the ascending order of the queues.
1 · 1 · 100 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
z The choice for “Minimum Diffserv Code Point” and “Maximum Diffserv Code
Point” is one of the Diffserv classification values 0 (000000) to 63 (111111)
Network Interfaces
Configuration
Tab Panel
1 · 1 · 105 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
z 1) NE IP PARAMETERS –
Defines the local IP address of the NE.
y Default IP address: 10.0.1.2
y Default mask: 255.255.255.255
z 2) TMN RF ACCESS –
To validate the TMN RF channel to supervise the remote station.
z 3) NMS1 –
Defines the IP address associated to the physical interface Network Management
Service 1 (NMS1 connector).
z 4) NMS2 –
Defines the IP address associated to the physical interface Network Management
Service 2 (NMS2 connector).
z 5) TMN IN-BAND –
Defines the IP address of the TMN supervision channel defined with a VLAN identifier
inside a user Ethernet traffic.
z 6) CT –
Defines the IP address associated to the Craft Terminal connected to the physical
interface CT (CT connector). These fields are Read-only.
z If used:
z Assign an IP address with its IP mask
z When you have finished to configure the “Network Interfaces Configuration” tab panel,
do not forget to apply it to the NE (<Apply> button on the top right of the window).
Network Interfaces
Configuration
Tab Panel
1 · 1 · 107 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
z 1) NE IP PARAMETERS –
Defines the local IP address of the NE.
y Default IP address: 10.0.1.2
y Default mask: 255.255.255.255
z 2) TMN RF ACCESS –
To validate the TMN RF channel to supervise the remote station.
z 3) TMN IN-BAND –
Defines the IP address of the TMN supervision channel defined with a VLAN
identifier inside a user Ethernet traffic.
z If used:
z Assign an IP address with its IP mask
z When you have finished to configure the “Network Interfaces Configuration” tab panel,
do not forget to apply it to the NE (<Apply> button on the top right of the window).
z This is the IP interface to a host or network. Typically used at a spur to interface a host over the RF path. In this
scenario, the Default Gateway IP Address is 0.0.0.0 and the IP Mask (greyed out) is 0.0.0.0. Also typically used at an
end terminal in a radio link for interface with the network.
z WARNING:
{ No pending (open) static routes are allowed.
{ The default software uses first the static routes and then the dynamic routes. An open static route is always
considered as a preferential path.
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 By pressing Add Last or Add pushbutton it is possible to create new or change existing IP static routes
- Manager IP Address
- Traps UDP Port
- Type (Network Manager Layer, Equipment Manager Layer)
Registration
To delete a Manager, select the Manager from the list, then press < Unregister >
1 · 1 · 115 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
zIn the Server Address field write the IP address of the FTP server.
zUser Name and Password are the login information to access the FTP server.
zIn the Port field write the port to be used.
zBy clicking on the Check button, the server access values will be filled in automatically with the default
configuration.
2. Then, click on the Backup or Restore button to begin the backup/restore process.
3. When the < NE Configuration > backup/restore starts, a screen showing the in-progress operation of the
backup/restore appears. The backup/restore is aborted if the Abort button is pressed.
4. Click Ok.
Monitoring Tool
Alarms
Power Measurements
Modem Measurements
Alarms Log: shows all the equipment alarms currently present and the history of
the alarms (i.e. cleared alarms).
Note:
When an alarm is no longer active, it disappears from the Current Alarm list and it is displayed in the Alarm
Log list as a cleared alarm.
z Within the “Alarms” tab panel, each alarm is provided with the
information below.
Time Stamp: date and time of the alarm. The format of date and time is
mm/dd/yy hh:mm:ss.
Probable cause: name of the probable cause of the alarm.
Type: alarm class
y COMMUNICATION = Communication Alarm – alarm not created inside the equipment,
but generated by a connected equipment or due to transmission/propagation
problems
y EQUIPMENT: inside alarm of the equipment.
Object: object of the equipment where the alarm occurred (equal to Friendly
Name).
Severity: alarm severity.
Additional Text: this is an additional text regarding the alarm.
z 2) PRINT –
One choice: to print the list of alarms
(“Current Alarms” or “Alarms Log”).
z 3) AUTO-SCROLL –
One choice: to scroll automatically the list of the alarms.
z 4) FILTER –
To organize the display of the alarms by a filter or not.
z SEVERITY – Filter
z TYPE – Filter
z NO FILTER
These fields are identical for Monitoring and represent the linked end-point of the two
NE (from a local point of view, one field for transmission view and one field for
reception view).
1 · 1 · 130 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
Start/Stop Monitoring
z 1) START MONITORING –
After clicking on “Start Monitoring”
button, you have to select the
refresh period for monitoring.
z 3) STOP MONITORING –
z In the field < Near End to Far End Power Monitoring >
NE Tx Power (in green color)
y Near End Tx Power value (local equipment)
FE RSL (in blue color)
y Far End Receive Signal Level (remote equipment)
z In the field < Far End to Near End Power Monitoring >
NE RSL (in blue color)
y Near End Receive Signal Level (local equipment)
FE Tx Power (in green color)
y Far End Tx Power value (remote equipment)
Note: The current Tx and Rx local and remote values is given too.
z Note: PTx and PRx levels software readings tolerance: PTx=Real Value ± 3dB; PRx=Real Value ± 5dB.
z WARNING:
z Radio analog transmitted power level (local ODU)
In case of ICP or Cable Loss alarms the value shown at management system is -99.8 dBm. In case of mute
status the value shown at management system is -100 dBm. If the power level read is out of the allowed
range, the value shown by the management system is -101 dBm.
z Radio analog received power level (local ODU)
In case of ICP or Cable Loss alarms the value shown at management system is -99.8 dBm. In case of
failure on reading the register containing the received power the value shown at management system is
-99.7 dBm. If the power level read is out of the allowed range, the value shown by the management
system is -101 dBm.
z Radio analog transmitted power level (remote ODU)
In case of broken radio link the value shown at management system is -99.6 dBm. In case of mute status
the value shown at management system is -100 dBm. In case of failure on reading the register containing
the remote transmitted power the value shown at management system is -99.7 dBm. If the power level
read is out of the allowed range, the value shown by the management system is -101 dBm. In case of
alarms on the remote NE on one of the two radio channels in HSB configuration (typically ICP, Cable
Loss, Crad Missing, Card Fail), the value shown by the management system is -127 dBm.
z Radio analog received power level (remote ODU)
In case of failure on reading the register containing the remote received power the value shown at
management system is -99.7 dBm. If the power level read is out of the allowed range, the value shown
by the management system is -101 dBm. In case of alarms on the remote NE on one of the two radio
channels in HSB configuration (typically ICP, Cable Loss, Card Missing, Card Fail), the value shown by
the management system is -127 dBm.
Go to the first
Measurement point
Go to the last
Measurement point
Zoom In
Zoom Out
Scroll lock
To freeze the display
z Then the MCT asks you to choose a path and name for this file in your
PC (You can store the file in any directory).
-2- The log file contains the sample value and records the measurement
up to a maximum dimension (7 days for a 2 s sample time).
1 · 1 · 140 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
z Note: The measurement file can be opened also with a standard text editor (e.g. WordPad). Go in the
directory where the .csv files are stored and open the file. The measurements are shown in the tabular
mode.
These fields are identical for Monitoring and represent the linked end-point of the two
NE (from a local point of view, one field for transmission view and one field for
reception view).
1 · 1 · 142 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
Start/Stop Monitoring
z 1) START MONITORING –
After clicking on “Start Monitoring”
button, you have to select the
refresh period for monitoring.
z 3) STOP MONITORING –
1100
z In Radio Link Systems,
the “Mean Square Error” is
a modulation error from
Intersymbol distance the theoretical threshold
of the equipment.
z MSE is expressed in dB.
16-QAM Modulation – drawback
Rx – weak noise
Note: The current MSE local and remote values are given too.
z Note: PTx and PRx levels software readings tolerance: PTx=Real Value ± 3dB; PRx=Real Value ± 5dB.
z WARNING:
z Radio analog transmitted power level (local ODU)
In case of ICP or Cable Loss alarms the value shown at management system is -99.8 dBm. In case of mute
status the value shown at management system is -100 dBm. If the power level read is out of the allowed
range, the value shown by the management system is -101 dBm.
z Radio analog received power level (local ODU)
In case of ICP or Cable Loss alarms the value shown at management system is -99.8 dBm. In case of
failure on reading the register containing the received power the value shown at management system is
-99.7 dBm. If the power level read is out of the allowed range, the value shown by the management
system is -101 dBm.
z Radio analog transmitted power level (remote ODU)
In case of broken radio link the value shown at management system is -99.6 dBm. In case of mute status
the value shown at management system is -100 dBm. In case of failure on reading the register containing
the remote transmitted power the value shown at management system is -99.7 dBm. If the power level
read is out of the allowed range, the value shown by the management system is -101 dBm. In case of
alarms on the remote NE on one of the two radio channels in HSB configuration (typically ICP, Cable
Loss, Crad Missing, Card Fail), the value shown by the management system is -127 dBm.
z Radio analog received power level (remote ODU)
In case of failure on reading the register containing the remote received power the value shown at
management system is -99.7 dBm. If the power level read is out of the allowed range, the value shown
by the management system is -101 dBm. In case of alarms on the remote NE on one of the two radio
channels in HSB configuration (typically ICP, Cable Loss, Card Missing, Card Fail), the value shown by
the management system is -127 dBm.
z Then the MCT asks you to choose a path and name for this file in your
PC (You can store the file in any directory).
Inventory
Software Download
Configuration
y Radio
Monitoring
y Alarms
y Power Measurements
y Modem Measurements
Inventory
Troubleshooting
Monitoring
y Alarms
y Power Measurements
y Modem Measurements
y Events
MPR-e
MSS-1c
The functions described in this section allow to perform the test operations
by loopbacks.
1 · 1 · 165 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
z 1) LOOPBACK –
This field permits to perform tests on the equipment
In this current release, two loopbacks are available:
y Line Side loopback (the signal is sent back to the Indoor equipment)
y Radio Side loopback (the signal is sent back to the Remote station)
z 2) RESTART NE –
This field permits to restart the NE
Loopback (1/4)
Loopback (2/4)
z …
To activate a loopback (2/3): z Tick on the wanted loopback
z Then click on <Activate> button
Line Side
Loopback (3/4)
z …
To activate a loopback (3/3): z Tick on the wanted loopback
z Then click on <Activate> button
Radio Side
Loopback (4/4)
To deactivate a loopback:
z Click on <Deactivate> button
z MSS-1c
z MPR-e
Normalized
y CH1 Radio Hop - Counters Thresholds
- 15Min Counters
- 24H Counters
y CH0 Radio Hop - Counters Thresholds
- 15Min Counters
- 24H Counters
y Radio Link - Counters Thresholds
- 15Min Counters MSS-1c MPR-e
- 24H Counters
Adaptative Modulation
y 15Min Counters
y 24H Counters
Ethernet
y QoS Counters
y Traffic Port Counters (for MPR-e only) The use of this Perspective
Monitoring
y Alarms
“Performance Monitoring”
y Events is explained in the module
Section 3 – Module 6”
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.
TDM cross-connection between Radio and user ports, for Cross-connection domain;
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.
z NOTE:
The Main Tab panel management is exactly the same as the Main Tab panel
of the MSS-1c main view or MPR-e main view.
z The operator choice in the Main Tab Panel makes changes in the contents of:
z 1) Navigator Area
This area displays all the available tasks for a specific tool (perspective).
z 2) Resource area
This area displays a representation in tabular view or in graphical view of the selected resource for a
specific tool (perspective).
z Operator facility:
By moving the margin, we can see all the opened tools (perspectives)
Navigator Area
NOTE:
The Navigator Area management is exactly the same as the Navigator Area of the MSS-1c main view or
MPR-e main view.
z 1) FILE –
Two choices:
y to exit the MCT.
y to manage the Configuration Files
z 2) HELP –
One choice: to have an help on Provisioning Tool.
Help Menu
Configuration Details
Plug-in Details
z “Navigation Configuration”
Perspective is divided in:
File Management
MSS-1c Provisioning
y Ethernet Port Provisioning
y PDH Port Provisioning
y Management Port Provisioning
y TDM cross-connection between Radio and
user ports
y Synchronization Provisioning
y Bridge Provisioning
y Port VLAN Provisioning
y Storm control and Rate limiting
y Per flow policer
Initial Configuration:
to start from an empty configuration
Reconfiguration:
to load an existing configuration file and then modify
everything
Change Configuration:
to load an existing configuration file and then modify only
some items
Provisioning File
(It means after to have filled in all the parameters inside each tool of all Perspective),
z Save it in a Configuration File by using the Provisioning File field with the button < Create >
NOTE:
z The Change Configuration mode is useful to modify an running configuration without impacting already
configured services (cross-connections and VLANs).
When this file will be downloaded to the NE by using the WebEML (menu « Configuration > MSS-1c ») the
NE will not reboot after the download.
Reconfiguration
(It means after to have filled in all the parameters inside each tool of all Perspective),
z Save it in a Configuration File by using the Provisioning File field with the button < Create >
Change Configuration
(It means after to have filled in all the parameters inside each tool of all Perspective),
z Save it in a Configuration File by using the Provisioning File field with the button < Create >
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 Auto-Negotiation Status (Enabled or Disabled);
Check the box: the port will negotiate speed and duplex mode with its peer.
Uncheck the box: speed and duplex mode are selected by the operator (forced mode).
z Speed -Directionality, (“10 Mb/s – Half Duplex”, “10 Mb/s – Full Duplex”, “100 Mb/s – Half Duplex”,
“100 Mb/s – Full Duplex”). Check to allow communication at the selected data rate between two
locations. Choose half duplex for only one direction at a time, or full duplex for communication in both
directions at the same time.
z Example :
Ethernet Port
configuration
using the 4 users ports
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 Auto-Negotiation Status (Enabled or Disabled);
Check the box: the port will negotiate speed and duplex mode with its peer.
Uncheck the box: speed and duplex mode are selected by the operator (forced mode).
z Speed -Directionality, (“10 Mb/s – Half Duplex”, “10 Mb/s – Full Duplex”, “100 Mb/s – Half Duplex”,
“100 Mb/s – Full Duplex”). Check to allow communication at the selected data rate between two
locations. Choose half duplex for only one direction at a time, or full duplex for communication in
both directions at the same time.
NOTE:
z To configure a SyncE electrical port like user 2, proceed the same way as for user 1. In addition
configure the Network synchronization.
1. Auto, if you do not use the syncE property of the port
2. SyncE IN, if you use the port as synchronization input. MSS-1c receives clock from external
equipment.
3. SyncE OUT, if you use the port as a synchronization output. MSS-1c sends its clock to external
equipment.
z this feature is authorized only if the port is set in Auto negotiation mode with speed 1000 Mbit/s and
full duplex only.
z Thanks to SFP connected into the relevant slots, these two ports can be configured in electrical or optical
mode.
z Once the Port Enable Check box is selected, you can choose the type of SFP in the SFP list (Disable or
Electrical or Optical)
z In the Electrical mode, the configuration is like user 1.
z In the Optical mode, the Port configuration can be set to Auto negotiation or not (forced mode). The speed
is always 1000 Mbit/s.
z The duplex mode is always Full Duplex.
z Note: In optical mode, User port 4 can be used as SynchE port. It is also the case for User port 3 only on
MSS-1c 16E1.
z Note: On MSS-1c 16E1, User Port 3 and 4 cannot be used in Gigabit when configured in electrical mode.
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) Enabled: with a fixed type of frame (Unframed) to enable the port
z 3) Service Profile: possible profile to be associated to the tributary (TDM2TDM/TDM2Eth)
z 4) Flow Id: identifier of the tributary for the cross-connection
z 5) ECID Tx: Emulated Circuit Identifier in Tx direction
z 6) ECID Rx: Emulated Circuit Identifier in Rx direction
z 7) TDM Clock sync: type of the clock to be associated to the tributary (Adaptive/Differential/Tdmline)
z 8) Node Timing: to enable for the corresponding port the Node Timing synchronization. When it is
selected, the regenerated E1 at receiver side are synchronized to the network element clock (NEC).
z 9) Xco to Port: to cross-connect the E1 port to Radio or User port
z 10) MAC Address: to set the destination MAC address of the equipment in case of TDM2Eth cross-
connection
z Note: Columns 5, 6, and 7 are only available if the Service Profile is TDM2Eth.
z 9500 MPR-E performs Circuit Emulation on PDH TDM flows, and then
transport those "TDM packets" mixed to native Ethernet frames.
z The Circuit Emulation IWF (inter-working function) is according the
Metro Ethernet Forum implementation agreement known as MEF 8,
limited to the structure agnostic case.
z MEF 8 emulated circuits is based on exchange of service parameters
between two CES IWFs at either end of the emulated circuit; if one of
those IWFs belong to the 9500 MPR-E the following parameters are
defined:
MAC addresses of the two IWFs
Payload size
ECID (2 different values may be used for each direction)
TDM clock source
y clock recovery adaptive
y clock recovery differential
VLAN (One Vlan is assigned to each bi-directional circuit emulated E1 flow)
z RTP, which is optional in MEF8, is always present, but not used if the
clock recovery is not differential.
z The common clock for Differential clock recovery is 25 MHz.
z Three different cases of Circuit Emulation services are implemented:
1) TDM2TDM
2) TDM2ETH
3) ETH2ETH
NOTE:
For MPR-e, only one case of Circuit Emulation service is implemented:
1) ETH2ETH
z TDM2TDM
z Both the IWFs belong to 9500 MPR-E and the packets are not supposed
to go out the 9500 MPR-E network.
z The IWF parameters listed above, have predetermined values and don’t
need to be provisioned.
z MAC addresses are determined as consequences of the cross
connections.
z Payload size: fixed to 121 bytes
z ECID will be the same value as Flow Id
z TDM clock source: clock recovery differential,
z Flow Id provisioned by ECT/NMS
z TDM2ETH
z Only one of the IWFs belongs to 9500 MPR-E and the packets are
supposed to go out the 9500 MPR-E network.
MAC addresses: in all involved nodes are determined as consequences of the
cross connections; the only exception is the Ethernet Terminal Node (the
node where that TDM2ETH traffic goes through an user Ethernet port). In
such ETN the source address will be the node Mac address, the dest. mac
address will be provisioned by ECT/NMS.
Payload size: fixed to 256 bytes
ECID: provisioned by ECT/NMS, 2 different values may be used for each
direction
TDM clock source will be provisioned by ECT/NMS: clock recovery adaptive,
clock recovery differential
Flow Id will be provisioned by ECT/NMS (One Vlan is assigned to each bi-
directional circuit emulated E1 flow)
z For this case the expected latency for 1 hop only is 3.5 msec for 256
bytes.
z ETH2ETH
z None of the IWFs belongs to 9500 MPR-E.
z None of the above parameters has to be configured (the 9500 MPR-E 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.
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-E 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-E, but the
second IWF is external to the 9500 MPR-E network. The Circuit Emulation Service is TDM2ETH in Node 1 and
Node 2. The Cross connections to be implemented are PDH-Radio type in Node 1 and Radio-Eth type in Node
2.
z Case 3
z The E1 stream is inserted/extracted in Node 1. One IWF is inside the 9500 MPR-E, but the second IWF is
external to the 9500 MPR-E network. The Circuit Emulation Service is TDM2ETH in Node 1 and Node 2. The
Cross connections to be implemented are PDH-Eth type in Node 1.
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-E network. The Circuit Emulation Service is ETH2ETH in Node 1 and Node 2. No Cross
connections must be implemented. The path is automatically implemented with the standard auto-learning
algorithm of the 9500 MPR-E Ethernet switch.
NE MAC Address:
This field is read-only
which shows the MAC
Address of the NE. This
MAC Address must be
used in the cross-
connection with
TDM2ETH profile.
z The Settings view performs all the available functions for Ethernet tributary ports. Information related to
a data Port Provisioning is provided by the following parameters:
z Port Status (Enabled or Disabled);
z Auto-Negotiation Status (Enabled or Disabled);
Check the box: the port will negotiate speed and duplex mode with its peer.
Uncheck the box: speed and duplex mode are selected by the operator (forced mode).
z Speed -Directionality, (“10 Mb/s – Half Duplex”, “10 Mb/s – Full Duplex”, “100 Mb/s – Half Duplex”,
“100 Mb/s – Full Duplex”). Check to allow communication at the selected data rate between two
locations. Choose half duplex for only one direction at a time, or full duplex for communication in both
directions at the same time.
z TMN IN-BAND –
Defines the IP address of the TMN supervision channel defined with a VLAN
identifier inside a user Ethernet traffic.
z The “Cross-connections” field contains the list for all the implemented cross-connections.
z Maximum number of cross-connections: 240.
z The block diagram presents the different elements involved in the cross-
connection, in green the PDH and CES part (encapsulation in Ethernet
frame done by IWF), in blue the Ethernet part realized by the switch.
TDM IWF
User Port 1 User Port 2 User Port 3 User Port 4 PDH Ports
E1-1 E1-2
1 · 1 · 214 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Operator Interface MPR Tterminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
Notes:
z The unicast MAC address of the NE is shown in the “MSS-1c Provisioning Tool – Configuration
Perspective – Management Port Provisioning” (NE Public Mac Address or Bridge Address).
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.
To Remove a Cross-Connection
1+0 no protection
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.
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.
9500 MPR
Private
Business
Office
9500 MPR
9500 MPR
Time delivery Time source
options options
Fixed
DSL
Transparent Transparent
1588v 1588v2
transport of transport of
Phone 2 TOD TOD
protocol protocol
z All the NEs radios in the network must be synchronized to the same clock.
z One radio in the network is provisioned Master.
z All other radios in the network must be provisioned Slave.
z The slave radios all sync to the clock provided by the master.
SynchrE: Any Synchronous Ethernet clock source available at enabled User Ethernet traffic interfaces (both
electrical and optical) configured in synchronous operation mode (the specific User Ethernet port has to
be chosen).
z From ITU-T G.8264 point of view, the MSS is a Synchronous Ethernet equipment equipped with a
system clock (NEC) following the ITU-T G.8262 recommendation.
z A User Ethernet interface configured in synchronous operation mode can work only at 1Gigabit/s.
z In the particular case of electrical User Ethernet interfaces, these interfaces perform link auto
negotiation to determine the master and slave clocks for the link.
z The clock slave role must be configured as part of auto negotiation parameters in order to use the
interface as Synchronous Ethernet clock source.
N.B.: SSM is not supported, therefore MPR cannot be included in a Synch-E ring.
The Symbol Rate of the Rx signal of any available Radio direction (the specific Radio Port has to be
chosen).
How to Synchronize
z Each Network Element must have a reference Clock (NEC), which will be
distributed to each function of the MSS-1c. Such clock is a 25 MHz generated in
the MSS-1c.
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] Radio Port: Symbol Rate of the Rx signal of any available Radio direction
[4] User 4: Network synchronization for 1 Gb/s Ethernet frames (Auto, SyncE IN, SyncE
OUT)
NEC Role
z Each function 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.
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 (User 1, User 2, User 3, User 4): Select the ports members of this VLAN by putting a check
mark on the relevant check box. All the user Ethernet ports can be considered. Both enabled and
disabled user Ethernet ports (radio ports are implicitly enabled) can be member of a VLAN. This means
that a disabled port can be configured as a member of a VLAN and a port already member of a VLAN can
be disabled continuing to be a member of the same VLAN.
z 4) Untagged Ports : 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.
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.
z Note: If all ports are in UNI mode, the S-TPID configuration is not necessary.
Mode: 802.1Q
z The Port VLAN Provisioning performs all the available functions for Ethernet tributary ports. Information
related to a data port configuration is provided by the following parameters:
z 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 Frames Only (only tagged frames are allowed in ingress and untagged frames are
dropped)
{ Admit All Frames (tagged, untagged and priority frames are allowed in ingress)
Default value: “Admit All Frames”.
Port VLAN ID: if the Acceptable Frame Type is set to “Admit all” the VLAN-ID and Priority fields, to
be added in ingress to untagged frames, must be configured. Only VLAN-ID values already defined (in
the VLAN management menu) can be configured for this purpose. The Priority values allowed are in
the range 0 - 7.
The default Port VLAN-ID and Priority values are: VLAN-ID=1; PCP=0.
The VLAN 1 is always removed when the frame is forwarded.
N.B.: Untagged frames: The untagged frames received on one user Ethernet port, configured as
“Admit tagged only”, are dropped.
N.B.: Priority frames: The priority packets (VLAN-ID=0) received on one user Ethernet port,
configured as “Admit tagged only”, are dropped.
The priority packets (VLAN-ID=0) received on one user Ethernet port, with the “Admit
all” configuration enabled, are managed as untagged frames for VLAN-ID field, while
the Priority field is the same of the received packets.
How to Configure
z The Port VLAN Provisioning performs all the available functions for Ethernet tributary ports. Information
related to a data port configuration is provided by the following parameters:
z 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 and untagged frames are dropped)
{ Admit all (tagged, untagged and priority frames are allowed in ingress)
Default value: “Admit all”.
Port VLAN ID: if the Acceptable Frame Type is set to “Admit all” the VLAN-ID and Priority fields, to be
added in ingress to untagged frames, must be configured. Only VLAN-ID values already defined (in the
VLAN management menu) can be configured for this purpose. The Priority values allowed are in the
range 0 - 7.
The default Port VLAN-ID and Priority values are: VLAN-ID=1; PCP=0.
The VLAN 1 is always removed when the frame is forwarded.
N.B.: Untagged frames
The untagged frames received on one user Ethernet port, configured as “Admit tagged only”,
are dropped.
N.B.: Priority frames
The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as “Admit
tagged only”, are
dropped.
The priority packets (VLAN-ID=0) received on one user Ethernet port, with the “Admit all”
configuration enabled, are
managed as untagged frames for VLAN-ID field, while the Priority field is the same of the
received packets.
Mode: 802.1ad (Q in Q)
z If the port is configured in NNI, no choice is offered to the operator (“Admit tagged frames only” is
automatically selected).
z If the port is configured in UNI “Admit all frames” (untagged and C-Tagged frames are admitted) is
automatically selected:
z The S-VLAN associated to this UNI port is displayed and cannot be changed
z Select the S_VLAN priority in the list (from 0 to 7)
z Select or not the use of inner C-VLAN priority for S-VLAN priority
z For Broadcast, Multicast and DLF Storm control, to enable this control, select the check box and enter a
value in the authorized range.
z Per port rate limiting, for each user port, in ingress and egress, rate limit and burst size may be set.
z Note: Per port rate limiting: minimum burst size at egress is 114 kBytes. So the burst size limitation will
become accurate for bust size limitation set over 2500 kBbytes.
z Note: Storm Control thresholds are not guaranteed when total rate at ingress is higher than 1 Gbps.
z This feature is used to control the Committed Information Rate, the Peak Information Rate and associated
burst size of a flow identified by its VLAN Id.
z In 802.1D Bridge mode, the operator can enter any VLAN in the VLAN Id column.
z In 802.1Q and 802.1ad Bridge mode, the operator can select a VLAN in the proposed list of existing VLANs
(created in the Bridge Provisioning window).
z Note: for burst size setting over 8000 bytes, the accuracy of the limitation is not guaranteed.
z Note: when a same VLAN is ingressing and egressing from a User Port, the flow policing cannot be used.
z Note: the flows without flow policer rule are not guaranteed (Yellows frames).
z Default values are proposed. They can be changed by the operator in the authorized range.
Section 1
NE operation
Module 2
Initial Configuration MPR Terminal
3JK Issue 2.0
9500 MPR
9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
TWT63044-R 3.1-SG1-SEN- I1.0 Issue 1.00
Document History
Page
Switch to notes view!
1 Initial Configuration 7
1.1 General Requirements 8
1.2 Initial Turn-up 10
1.3 Provision Commissioning 18
1.4 Provision NE Time 20
1.5 Provision Site Information 21
1.6 Provision Protection 22
1.7 Provision Synchronization 23
1.8 Provision Radio 24
1.9 Provision Advanced Radio 30
1.10 Provision MSS-1c 31
1.11 Provision Ethernet Traffic QoS 35
1.12 Provision Networking 38
Blank Page 42
2 MSS-1c Provisioning Tool 43
2.1 Main view 44
2.2 Configuration Perspective Navigation 45
2.3 Initial Turn-up 46
2.4 File Management Tool 47
2.5 MSS-1c Configuration Tool 48
Exercise 49
End of Module 50
1·2·6
NE operation · Initial Configuration MPR Terminal
ThisAll Rights
page is left blank intentionally
Reserved © Alcatel-Lucent 2011
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
z PC HW Configuration
CPU: AMD Atlhon/Intel Celeron/Intel Pentium 4 or higher
RAM: 1 GB
Hard Disk space: 1.5 GB (available space for log files, JRE excluded)
Display Resolution: 1280x800 pixel
DVD-ROM Drive (needed for the TCO Suite)
Ethernet Interface: Ethernet Card 10/100 Mbps
Note:
“Classic windows” setting must be choosen with Windows Vista and Windows 7
z Additional requirements
Microsoft Internet Explorer 6 SP1, 7, 8, Mozilla Firefox 2, 3, 3.5
The Administrator password is needed only for Java installation
When Java has been installed, the standard user can run the WebEML Suite
Java Runtime Environment (JRE) 6 Update 14
Warning:
An FTP server must be installed on the PC of MCT user with read right &
write right, and the Windows Firewall must be desactivated.
Before operating the user system interface (USI) for the first time, the
programs contained on the CD ROM must be copied on the PC.
Note:
The TCO Software Suite will auto-run and open up the computer's default
browser program (if auto-run feature is enabled on user's PC) as soon as the
DVD-ROM is read by the PC. If auto-run does not start, user must run
(double-click with left mouse button on it) the Start.exe file, available on
DVD-ROM root, in order to launch the Software Package.
See next slide
NOTE:
z An alternative way to perform the Local Copy of the WebEML is by clicking on the Advanced Settings
button.
z This alternative way is explained in the User Manual.
u
z 7 – Click on <Yes> to perform
the WebEML Local Copy
NOTE:
z An alternative way to perform the Local Copy of the WebEML is by clicking on the Advanced Settings
button.
z This alternative way is explained in the User Manual.
11
12
NOTE:
z An alternative way to perform the Local Copy of the WebEML is by clicking on the Advanced Settings
button.
z This alternative way is explained in the User Manual.
o NETO
opens
N.B.
To access the NE the PC must be configured to “Get automatically an IP address”, because the NE is
configured as DHCP Server with default IP address 192.168.30.1 and subnet mask 255.255.255.252. The
PC Ethernet port must be connected to the CT connector of the MSS-1c.
N.B.
192.168.30.1 is the IP address of the port from MSS-1c and cannot be modified. The management can be
done also by the NMS port, but the PC must be configured with fixed IP and gateway. First open the
WebEML and after connect the cable.
Warning:
Without the MPT connected to the MSS-1c, it is not possible to open the WebEML on the CT port from MSS-
1c.
Warning:
If all the WebEML images/icons are missing, check that file msimg32.dll is present inSystem32.
Note: Default User Accounts – at the NE installation time, one default user account is created on NE
independently from the SNMP operating mode.
z Profile: administrator
z Username: admin
z Password: admin
START
Provisioning MPR
Provision NE Time
Provision Protection *
Provision Synchronization
Provision Radio
Provision MSS-1c
n Select
Commissioning
Perspective to start
o Select
Configuration
Tool
n Select
Commissioning
Perspective to start
o Select
Configuration
Tool
n Select
Date/Time Tool
z The user can synchronize the NE time from either the PC/laptop or Network Time Protocol (NTP) servers.
Time and date provisioning is accomplished using the NE Time Configuration screens.
n Select Site
Information Tool p Write down the Site Location
n Select
Protection
Tool
z Synchronization Configuration p
n Select
Radio Tool
Channel Spacing:
z 3,5 MHz
z 7 MHz
z 14 MHz
z 28 MHz
z 40 MHz
z 56 MHz
Reference Modulation:
z QPSK
z 8 PSK
z 16 QAM
z 32 QAM
z 64 QAM
z 128 QAM
z 256 QAM
Note: If the current Modulation scheme is 4 QAM, it not possible to force to 64 QAM, but first must be
forced to 16 QAM and then to 64 QAM. Also if the current Modulation is 64 QAM, to pass to 4 QAM first
must be forced to 16 QAM and then to 4 QAM.
Warning: with the up and down arrows, below the Forced Modulation field, it is possible to increase or
decrease the part of the screen relevant to the parameters of the Adaptive Modulation.
Channel Spacing:
z 3,5 MHz, 7 MHz, 14 MHz, 28 MHz, 40 MHz, 56 MHz
Reference Modulation:
z QPSK, 16 QAM, 32 QAM, 64 QAM
z Note: the ATPC area is not present if the Adaptive Modulation has been selected.
z The information related to the transmitter status is shown by an icon closed to the Mute field. To squelch
the transmitter tick on Mute field and press Apply button.
The middle field is used to set a frequency inside the allowed frequency range given by the ODU
represented by the left and right fields.
The middle field is used to set a frequency inside the allowed frequency range given by the ODU
represented by the left and right fields.
n Select Advanced
Radio Tool p In this Tx Identifier field,
write down the link
identifier inserted on the
o Tick on Enabled transmitting NE.
q In this Expected Rx
Identifier field, write down
the link identifier expected
at the receiving NE
z MSS-1c Configuration
o Click on the “Start Tool” button to run
the < Provisioning Tool > application.
n Select This tool is explained in the next
MSS-1c chapter 2 – MSS-1C Provisioning Tool -
Tool
z In the Server Address field write the IP address of the FTP server.
z User Name and Password are the login information to access the FTP server.
z In the Port field write the port to be used.
z By clicking on the Check button, the server access values will be filled in automatically with the default
configuration.
2. Then, click on the Download and Execute button to begin the download process.
3. When the <MSS-1c Configuration File> download starts, a screen showing the in progress operation of
the download appears. The download is aborted if the Abort button is pressed.
4. Click Ok.
3. When the ACTIVE MSS-1c operational parameters upload starts, a screen showing the in progress
operation of the upload appears. The upload is aborted if the Abort button is pressed.
4. Click Ok.
o Select the
QoS Classification p In Ether Type
It can be Classification field,
None set, if desired, for
IEEE 802.1p each non High
Diffserv Priority Queue (1
to 5), the type of
Ethernet frame
that will be sent to
this queue.
p In Scheduling
Algorithms field, set,
if desired, for each
non High Priority
n Select Ethernet Queue (1 to 5),
Traffic QoS Tool The Scheduling Mode
and the DWRR
Weight of the DWRR
scheduler chosen for
None Classification screen this queue.
1 · 2 · 35 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Initial Configuration MPR Terminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
z Diffserv Classification o
Notes:
z The highest priority queue is 5
z The highest priority queue corresponds to the transmission of packets whose diffserv classification priority is the
highest (range of diffserv priority values).
z The next queue does not contain the range of diffserv priority values of the previous queue.
z The range of diffserv priority values has to be set in ascending order corresponding to the ascending order of the
queues.
p Fill in the
local IP
Address of
the NE
r Fill in the IP
Address of the
NMS1 access
q Fill in the IP
Address of the
NMS2 access
n Select
Network t Fill in the IP address of the s This field is
Interfaces TMN supervision channel, read-only (IP
Tool if used, defined with a Address of the
VLAN identifier inside a CT access)
user Ethernet traffic
1 · 2 · 38 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Initial Configuration MPR Terminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
NE IP Parameters
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
n Select
Network p Fill in the q Fill in the IP address of the
Interfaces local IP TMN supervision channel,
Tool Address of if used, defined with a
the NE VLAN identifier inside a
user Ethernet traffic
1 · 2 · 39 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Initial Configuration MPR Terminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
NE IP Parameters
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 This is the IP interface to a host or network. Typically used at a spur to interface a host over the RF path. In this
scenario, the Default Gateway IP Address is 0.0.0.0 and the IP Mask (greyed out) is 0.0.0.0. Also typically used at an
end terminal in a radio link for interface with the network.
z WARNING:
{ No pending (open) static routes are allowed.
{ The default software uses first the static routes and then the dynamic routes. An open static route is always
considered as a preferential path.
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 By pressing Add Last or Add pushbutton it is possible to create new or change existing IP static routes
n Select
Trusted p Click on
SNMP Registe
Managers r, then
Tool OK
File Management
MSS-1c Configuration
START
z Provisioning MSS-1c
File Management
MSS-1c Configuration
Provision Synchronization
Provision Bridge
File Management
1 · 2 · 46 All Rights Reserved © Alcatel-Lucent 2011
NE operation · Initial Configuration MPR Terminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
n Select File
Management p After we have finished the
Tool MSS-1c Provisioning, click
on Create to save the
provisioning parameters in a
Provisioning File
(It means after to have filled in all the parameters inside each tool of all Perspective),
z Save it in a Configuration File by using the Provisioning File field with the button < Create >
Section 1
NE operation
Module 3
Performance Monitoring MPR Terminal
3JK Issue 2.0
9500 MPR
9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
TWT63044-R 3.1-SG1-SEN- I1.0 Issue 1.00
Document History
Activate and evaluate the Performance Monitoring application for the MPR
Terminal.
Page
Switch to notes view!
1 Performance Monitoring Perspective 7
1.3 Performance Monitoring Perspective Navigation 8
1.4 Performance History File Upload 10
2 PM: Normalized 15
2.1 Normalized Tool 16
2.2 MPT Unit Performances 18
2.3 CH1 Radio Hop Configuration 20
2.3.1 Counters Thresholds 21
2.3.2 15Min/24H Counters 23
2.3.2.1 Activate/Start/Stop/Reset the Monitoring 28
2.3.2.2 Current Normalized Counters Monitoring 30
2.3.2.3 History Normalized Counters Graph 34
2.3.2.4 History Normalized Counters Details 38
2.4 Import History 39
3 PM: Adaptative Modulation 41
3.1 Adaptative Modulation Tool 42
3.2 15Min/24H Counters 44
3.2.1 Activate/Start/Stop/Reset the Monitoring 49
3.2.2 Current Adaptative Modulation Counters Monitoring 51
3.2.3 History Adaptative Modulation Counters Graph 55
3.2.4 History Adaptative Modulation Counters Details 58
4 PM: Ethernet 59
4.1 Ethernet Tool 60
4.2 MPT QoS Ingress Counters (for MSS-1c only) 62
1 · 3 · 54.3 QoS Counters (for MPR-e only) All Rights Reserved © Alcatel-Lucent 2011 65
4.4
NE operation Ethernet
· Performance QoS
Monitoring Counters Monitoring
MPR Terminal
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
68
4.5 Traffic Port Counters (for MPR-e only) 78
4.5.1 Activate/Start/Stop/Reset the Monitoring 81
4.5.2 Ingress/Egress Traffic Port Counters Monitoring 83
4.5.3 Ingress/Egress Ethernet Traffic Port Counters Details 88
5 PM: Monitoring 89
5.1 Monitoring Tool 90
5.2 Alarms Tool 92
Page
Switch to notes view!
MPR-e
MSS-1c
z This field allows to configure the FTP server to be used to upload the <
Performance History File > from the NE.
zIn the Server Address field write the IP address of the FTP server.
zUser Name and Password are the login information to access the FTP server.
zIn the Port field write the port to be used.
zBy clicking on the Check button, the server access values will be filled in automatically with the default
configuration.
zNote: If as FTP Server the Apache Server, available on the TCO Software Suite Rel. 4.4 DVD-ROM, is used,
enter the following parameters:
z Server address: PC address
z Username: anonymous
z Password: anonymous
z Port: 21
2. Then, click on the Upload History button to begin the upload process.
3. When the Performance History Data upload starts, a screen showing the in progress operation of the upload
appears. The upload is aborted if the Abort button is pressed.
4. Click Ok.
Normalized Tool
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 There are threshold tables for the HOP and for the LINK.
z There are two default threshold tables for HOP (Channel 1, Channel 0):
One for “CHx Radio Hop 15 Minutes”
One for “CHx Radio Hop 24 Hours”
z There are two default threshold tables for LINK:
One for “Radio Link 15 Minutes”
One for “Radio Link 24 Hours”
2 3
z Note:
By clicking on “Defaults” button, the Low and High Thresholds are filled in with
the NE defaults values
z Note:
Four threshold tables can be created/modified for the HOP (Threshold CH1-15Min, CH1-24H, CH0-15Min and
CH0-24H).
Two threshold tables can be created/modified for the LINK (Threshold Link-15Min and Link-24H).
15Min Counters
Tab Panel (1/2)
15Min Counters
Tab Panel (2/2)
24H Counters
Tab Panel (1/2)
24H Counters
Tab Panel (2/2)
z 2) START MONITORING –
After clicking on “Start Monitoring”
button, you have to select the
refresh period for monitoring.
z 4) STOP MONITORING –
z Note: The ES, SES, BBE, UAS counters values refer to the last refresh performed with the Auto Refresh.
One Bar-graph “Hour Glass” (on the left) shows the remaining
time of the current measurement period (15Min or 24H) with
the corresponding values of the counters
z Note: The ES, SES, BBE, UAS counters values refer to the last refresh performed with the Auto Refresh.
z The graphic shows the curves of the counters (BBE, ES, SES, UAS)
during the current measurement period (15Min or 24H);
z Sometimes, the measurements shows “Suspect interval” which shows whether the current data are
suspect or not.
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.
Curves Management
• Loop Right
• Loop Left
z The Performance Monitoring process monitors the parameters during a specified interval (15Min or 24H)
and stores their values in history data. A History Data collection is created automatically at the end of
each time interval of Current Data.
z Note: Use the arrows “Right” and “Left” in the lower part to pass from one log to another log in the
history.
• Loop Right
• Loop Left
• Show erroneous
periods only
z If the Adaptive Modulation has been enabled in the NE, in the Performance Monitoring tool will appear
also the performances regarding the Adaptive Modulation: these performances show the time during
which a specific modulation scheme has been active.
15Min Counters
24H Counters
15Min Counters
Tab Panel (1/2)
15Min Counters
Tab Panel (2/2)
24H Counters
Tab Panel (1/2)
24H Counters
Tab Panel (2/2)
z 2) START MONITORING –
After clicking on “Start Monitoring”
button, you have to select the
refresh period for monitoring.
z 4) STOP MONITORING –
z Note: The QPSK, 8 PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM counters values refer to the last
refresh performed with the Auto Refresh.
z Note: The QPSK, 8 PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM counters values refer to the last
refresh performed with the Auto Refresh.
z The graphic shows the curves of the counters (QPSK, 8 PSK, 16 QAM,
32 QAM, 64 QAM, 128 QAM, 256 QAM) during the current measurement
period (15Min or 24H);
z Sometimes, the measurements shows “Suspect interval” which shows whether the current data are
suspect or not.
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.
Curves Management
• Loop Left
z The “History Adaptative Modulation Counters Graph” screen shows the History of
Adaptative Modulation Counters measurements related to the NE.
z Through this screen the operator can see by bar-graphs the history periods of
time (15Min, 24H) of:
•QPSK - in yellow color •64 QAM - in yellow color
•8 PSK - in red color •128 QAM - in pink color
•16 QAM - in pink color •256 QAM - in blue color
•32 QAM - in blue color
z The Performance Monitoring process monitors the parameters during a specified interval (15Min or 24H)
and stores their values in history data. A History Data collection is created automatically at the end of
each time interval of Current Data.
z Note: Use the arrows “Right” and “Left” in the lower part to pass from one log to another log in the
history.
Curves Management
• Loop Left
z The “History Adaptative Modulation Counters Details” screen shows the History
of Adaptative Modulation measurements related to the NE in tabular form.
z The measurements during the period of time (15Min or 24H) can be completed or
not completed:
The red cross means “not completed”
The green tick means “completed”
Ethernet Tool
z Ethernet MPT QoS Ingress Counters Tab Panel is divided in one field:
Ethernet MPT QoS Ingress Counters Monitoring
QoS Counters
Tab Panel (1/2)
QoS Counters
Tab Panel (2/2)
z 1) START MONITORING –
After clicking on “Start Monitoring”
button, you have to select the
refresh period for monitoring.
z 3) STOP MONITORING –
z The “Ethernet QoS Counters Tabular View” screen shows the History of Ethernet
QoS Counters measurements related to the NE.
z Through this screen the operator can see the values for Aggregate and each
queue:
Target Time Discarded Frames (Discarded TCF)
Transmitted Frames (TCF) Transmitted Bytes (TCO)
To see
more or less
details
click on + or -
z The Ethernet Aggregate Per Queue performances is measured in Outgoing radio side
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 octets (bytes) accepted and transmitted out by the specific
queue of the interface.
z Note: The different counters values refer to the last refresh performed with the Auto Refresh.
z The “Ethernet QoS Counters Monitoring” screen shows the Ethernet QoS Counters
measurements related to the NE.
z Through this screen the operator can see the transmitted TCF frames, discarded
TCF frames and transmitted TCO bytes on each queue and aggregate frame
z The Ethernet Aggregate Per Queue performances is measured in Outgoing radio side
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 octets (bytes) accepted and transmitted out by the specific
queue of the interface.
z Note: The different counters values refer to the last refresh performed with the Auto Refresh.
z The Ethernet Aggregate Per Queue performances is measured in Outgoing radio side
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 octets (bytes) accepted and transmitted out by the specific
queue of the interface.
z Note: The different counters values refer to the last refresh performed with the Auto Refresh.
z The graphical view shows the curves of the counters (transmitted TCF
frames, discarded TCF frames and transmitted TCO bytes);
z By clicking on “Export data to a .csv file”, you save the Ethernet QoS
Counters Measurements in a .csv file.
z Then the MCT asks you to choose a path and name for this file in your
PC (You can store the file in any directory).
z 1) START MONITORING –
After clicking on “Start Monitoring”
button, you have to select the
refresh period for monitoring.
z 3) STOP MONITORING –
z TRCF Unicast: total number of Ethernet Unicast frames transmitted out (Egress) or received correctly (Ingress) by
the Virtual Ethernet Interface.
z TRCF Multicast: total number of good packets transmitted by this address (Egress) or received (Ingress) that were
directed to a multicast address. This number does not include packets directed to the broadcast address.
z TRCF Broadcast: total number of good packets transmitted by this address (Egress) or received (Ingress) that were
directed to the broadcast address. This number does not include multicast packets.
z Note: The different counters values refer to the last refresh performed with the Auto Refresh.
z TRCF Unicast: total number of Ethernet Unicast frames transmitted out (Egress) or received correctly (Ingress) by
the Virtual Ethernet Interface.
z TRCF Multicast: total number of good packets transmitted by this address (Egress) or received (Ingress) that were
directed to a multicast address. This number does not include packets directed to the broadcast address.
z TRCF Broadcast: total number of good packets transmitted by this address (Egress) or received (Ingress) that were
directed to the broadcast address. This number does not include multicast packets.
z Note: The different counters values refer to the last refresh performed with the Auto Refresh.
z TRCF Unicast: total number of Ethernet Unicast frames transmitted out (Egress) or received correctly (Ingress) by
the Virtual Ethernet Interface.
z TRCF Multicast: total number of good packets transmitted by this address (Egress) or received (Ingress) that were
directed to a multicast address. This number does not include packets directed to the broadcast address.
z TRCF Broadcast: total number of good packets transmitted by this address (Egress) or received (Ingress) that were
directed to the broadcast address. This number does not include multicast packets.
z Note: The different counters values refer to the last refresh performed with the Auto Refresh.
z The graphic shows the curves of the counters (BBE, ES, SES, UAS);
Curves Management
• Loop Right
• Loop Left
Monitoring Tool
Alarms
2. Using the variable attenuator, simulate a link degradation and display the
current and the historical collected data
VARIABLE
ATTENUATOR
Test Test
Instr. A B Instr.
Operator 1 Operator 2
Section 2
Maintenance
Module 1
Fault Management
3JK Issue 2.0
9500 MPR
9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
TWT63044-R 3.1-SG1-SEN- I1.0 Issue 1.00
Document History
Page
Switch to notes view!
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 with MSS-1c 23
1.1.4 Troubleshooting Path Problems 24
1.1.4.1 Path Problems on a Commissioned Link 25
1.1.4.2 Path Problems on a New Link 27
1.1.5 Troubleshooting Configuration Problems 28
1.1.6 Troubleshooting Ethernet Problems 29
1.1.7 Troubleshooting TMN Problems 31
2 Failed Equipment Removal and Replacement 35
2.1 MSS-1c Removal and Replacement 36
2.2 MSS-1c replaced by MSS-1c 16E1 37
2.3 MSS-1c 16E1 replaced by MSS-1c 38
2.4 MPT-HC Removal and Replacement 39
2.5 MPT-HC V2 removal and replacement 40
2.6 MPT-MC Removal and Replacement 41
End of Module 42
2·1·6
Maintenance · Fault Management
This Allpage is left blank intentionally
Rights Reserved © Alcatel-Lucent 2011
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
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.
z Check the MCT Screen. When logging to the equipment with Craft
Terminal, the opening screen is the Main Screen. Use the information
provided in menu Alarms and in menu Events to check for severity and
problem type.
SFP missing alarm Major The SFP optional plug-in is Install the plug-in in the
provisioned, but not present SFP slot
SFP Tx fault (for Major Failure in the optical Replace the SFP
optical only) transmitter
LOS on Gigabit Major Loss of Ethernet is detected If the user port is in
ETH Interface forced mode, set it in
autonegociation 1000Mb/s
Full Duplex and then
come back to the forced
mode.
continue
Configuration/
Alarm Alarm
Equipment Most Probable Cause Action
Description
1+0
MPT-HC/ Card Fail Major MPT-HC/MPT-HC V2 failed Replace MPT-HC/MPT-HC
MPT-HC V2 V2
Loss of Radio Major Far end problems, RF path 1. Check/troubleshoot
Frame problems, or local circuit far end alarms
failures have caused BER to 2. Replace alarmed
increase to the point that MPT-HC/MPT-HC V2
frames are being lost
Demod Major Internal receive circuit Replace MPT-HC/MPT-
Function Fail failure HC/MPT-HC V2
continue
Configuration/
Alarm Alarm
Equipment Most Probable Cause Action
Description
1+0
MPT-HC/ High BER Major Bit Error Rate threshold 1. Verify RF path is clear,
MPT-HC V2 (10E-4) exceeded antenna is aligned, and no
existing weather-related
problems
2. Verify RSL is above RCV
threshold. If not – check
upstream transmitter
output/troubleshoot transmitter
Early Warning Minor 10E-9 BER detected No action is required at this
time. Monitor receive signal for
increased degrading
Link Identifier Major Link identifier number Set numbers at both ends of hop
Mismatch provisioned is different to match
from link identifier
number provisioned at
other end of hop
continue
Configuration/
Alarm Alarm
Equipment Most Probable Cause Action
Description
1+0
MPT-HC/ MPT Loop Minor Communication problem Check the radio hop
MPT-HC V2 Communication between the local MPT and the
alarm remote MPT for all the
functionalities requiring a
communication loop (ATPC,
ACM, Pre-distorsion)
Sync Degraded Minor This alarm can raise if the Check the radio hop
signal addressed Radio interface has
been configured as
primary/secondary
synchronization source. It is
active if the frequency of the
clock recovered from radio Rx
signal is mistuned
continue
Configuration/
Alarm Alarm
Equipment Most Probable Cause Action
Description
1+0
MPT-HC/ TCA on Radio Major Alarm threshold exceeded on
MPT-HC V2 Hop standby MPT-HC/MPT-HC V2
after switching from main to
standby
UAT on Radio Major 10 consecutive SES (unavailable
Hop time period) detected on
standby MPT-HC/MPT-HC V2
after switching from admin to
standby
continue
z RCV – Receiver
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 MSS, their settings cannot be loaded. The fault may be at the hardware device
(most likely), communications to it, or the MSS.
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.
z Note: A path extends from ODU antenna port to ODU antenna port.
z The most common TMN problems are network related and first alert is
normally observed by improper operation at the SNMP master. Always
check the following first:
Verify master is properly registered in NE to receive traps
Verify SNMP version matches system requirements
Verify correct community string and privileges
Verify proper network routing.
z Refer to the next table for detailed TMN network troubleshooting.
Continue …
Continue …
z This section gives general guidance on troubleshooting problems related to the four Ethernet ports on the
MSS-1c or on the MPR-e.
z Refer to table “Troubleshooting Ethernet Problems” on next slides for detail troubleshooting using the
LEDs locally at the alarmed site.
z All plug-in cards can be removed and installed with power applied.
z Disconnect the cables and the co-box from the MPT-HC to be replaced
and connect them to the spare MPT-HC.
z Note: The MPT-HC V2 can also be used to replace the MPT-HC. The 23 GHz MPT-HC V2 is a Tx High Power
version vs. MPT-HC. Take in account it when MPT-HC V2 is used as spare of MPT-HC.
z Disconnect the cables and connect them to the spare MPT-HC V2.
z Reconfigure the MPT by using the WebEML (menu Commissioning >
Configuration) or if a backup file is available, restore the MPT
configuration by the WebEML (menu Commissioning > Configuration >
Backup/Restore).
z Connect the WebEML to the CT port of MSS-1c and configure the PC to
“Get automatically an IP address” (because the NE is configured as
DHCP Server with default IP address 192.168.30.1 and subnet mask
255.255.255.252).
Section 2
Maintenance
Module 2
Software Download
3JK Issue 2.0
9500 MPR
9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
TWT63044-R 3.1-SG1-SEN- I1.0 Issue 1.00
Document History
Page
Switch to notes view!
1 MPR Terminal Software Download Menu 7
1.1 Software Download Tool 8
1.2 Server Access Configuration 10
1.3 Init Software Download 11
1.4 Software Status 12
1.5 End of a Correct Download 14
Blank Page 15
End of Module 16
2·2·6
Maintenance · Software Download
This page is left blank intentionally
All Rights Reserved © Alcatel-Lucent 2011
9500 MPR · 9500 MPR (Microwave Packet Radio) R 3.1 Terminal Configuration Operation and Maintenance (ETSI)
z 1) SOFTWARE INFORMATION –
This field gives the information of the software installed in the NE.
SOFTWARE PACKAGE –
Through this field the software is downloaded to the NE in order to upgrade
the NE software version.
z This field allows to configure the FTP server to be used to download the
SWP to the NE.
z Copy the ECT directory present in the SWP CD on the FTP server.
Warning:
z On the PC containing the Software Package must be
installed an FTP Server.
z The PC’s firewall (i.e Microsoft’s default firewall) may
prevent the download from starting up.
zIn the Server Address field write the IP address of the FTP server.
zUser Name and Password are the login information to access the FTP server.
zIn the Port field write the port to be used.
zBy clicking on the Check button, the server access values will be filled in automatically with the default
configuration.
zNote: If as FTP Server the Apache Server, available on the TCO Software Suite Rel. 4.4 DVD-ROM, is
used, enter the following parameters:
z Server address: PC address
z Username: anonymous
z Password: anonymous
z Port: 21
1. Click on Select Software Package button to add the available software packages on the PC.
2. Highlight the line where you find the File Name (i.e. 9500MPT.DSC) in the list and click on the Start
Download button.
- The Forced check box can be used to force download (i.e. the complete description file is downloaded
to the NE).
- If the Forced download is not selected, the system shall first proceed to compare the software to be
downloaded with the software present in the NE. Then only the differences are downloaded.
3. Click on the Download button to begin the download process.
4. When the SW download starts, a screen showing the in progress operation of the download appears. The
download is aborted if the Abort button is pressed.
5. Click Ok.
Recommended operation: Before starting the software download it is recommended to disable the
ATPC operation (if it has been enabled) and to set in RTPC mode the max.
Tx power.
By clicking on the
Active/Standby Software Package Summary
button a software unit status screen opens
(see on the next page) and gives additional
information on the software package.
z This tab panel “Software Package Versions” gives the information of the software installed in the NE.
z The following information is displayed:
z Name: software name
z Version: software version
z Current status: “ACTIVE Version” or “STANDBY Version”
The ACTIVE status refers to the software currently in use
NOTE The equipment software is installed on the compact flash, which has two banks.
This screen has two fields (each for one bank):
“Active Software Package” refers to bank 1 with the Actived software and relevant information;
“Standby Software Package” refers to bank 2 with the Stand by software and relevant
information.
NOTE The second bank appears when a new software package has been downloaded the first time.
z During download, necessary to update the software version, the download file is automatically stored in
the standby bank.
z To activate the new version first check the operational status of the standby bank. If the status is
enabled (this means that download took place without errors) click on the Activate button in the Standby
Software Package.
z At the end of the download process, press the < Activate > button of the
“Stand-by Software Package” field of the Software Status screen.
z The NE reboots and the supervision is lost.
z At the end of the download process, check that the new software is installed in
the “Stand-by Software Package” field of the Software Status screen.
Warning:
z After the activation of the “Stand-by Software Package” bank, the
connection between the WebEML (Craft Terminal) and the NE is lost.
z The WebEML must be re-launched.