9500MPR R 1.2.1 Operation and Maintenance

9500MPR R 1.2.1 Operation and Maintenence - Page 1All Rights Reserved © Alcatel-Lucent 2009

All Rights Reserved © Alcatel-Lucent 2009

9500 MPR9500MPR R 1.2.1 Operation and

Maintenence

STUDENT GUIDE

TWT63013-R 1.2.1-SG1-SEN- I1.0 Issue 1.00

All rights reserved © Alcatel-Lucent 2009 Passing on and copying of this document, use and communication of its contents

not permitted without written authorization from Alcatel-Lucent



9500MPR R 1.2.1 Operation and Maintenence9500 MPR2

Empty page

Switch to notes view!

This page is left blank intentionally




Terms of Use and Legal Notices

Switch to notes view!1. Safety WarningBoth 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 MarksAlcatel-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. CopyrightThis 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 rights reserved © Alcatel-Lucent 2009

4. DisclaimerIn 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 LawThe 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 LegalNotices shall remain in full force and effect.




Blank Page






Course Outline

About This CourseCourse outlineTechnical supportCourse objectives

1. Topic/Section is Positioned HereXxxXxxXxx

2. Topic/Section is Positioned Here






Section 1. Product Overview

Module 1. Introduction

Module 2. Architecture

Module 3. Management System

Section 2. Functional Description

Module 1. MSS HW Hardware Architecture

Module 2. ODU HW Hardware Architecture

Section 3. NE operation

Module 1. Operator interface

Module 2. Initial configuration

Module 3. Performance monitoring

Section 4. Maintenance

Module 1. Fault management

Module 2. Software download




Course Outline [cont.]






Course Objectives


Welcome to 9500MPR R 1.2.1 Operation and Maintenence

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

Configure and manage the 9500MPR




Course Objectives [cont.]






About this Student Guide

Switch to notes view!Conventions used in this guide

Where you can get further information

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

Technical Practices for the specific product

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

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.

WarningAlerts you to instances where non-compliance could result in equipment damage or personal injury.




About this Student Guide [cont.]






Self-assessment of Objectives

At the end of each section you will be asked to fill this questionnairePlease, return this sheet to the trainer at the end of the training


Contract number :

Course title :

Client (Company, Center) :

Language : Dates from : to :

Number of trainees : Location :

Surname, First name :

Did you meet the following objectives ?Tick the corresponding box

Please, return this sheet to the trainer at the end of the training

Instructional objectives Yes (or globally

yes)

No (or globally

no) Comments

1 To be able to: • Describe the basic concepts of

9500MPR

2 To be able to: • Describe the main functionalities

of the 9500MPR

3 To be able to: • Describe the management system of

the 9500MPR

4 To be able to : • Describe the functionality of each unit

of the MSS

5 To be able to: • Describe the functionality of the ODUs

6 To be able to: • understand all the menus available

with the LCT

7 To be able to: • Configure a NE starting from scratch

8 To be able to: • Activate and evaluate the performance

monitoring application

9 To be able to: • Performa the troubleshooting of the

9500MPR

10 To be able to: • Perform the SW download of the 9500MPR




Self-assessment of Objectives [cont.]


Instructional objectives Yes (or Globally

yes)

No (or globally

no) Comments

Thank you for your answers to this questionnaire

Other comments

Section 1 · Module 1 · Page 1

All Rights Reserved © 2007, Alcatel-Lucent3JK Edition 1.00

Do not delete this graphic elements in here:


Module 1Introduction

3JK Edition 1.00

Section 1Product Overview




9500 MPR · 9500MPR R 1.2.1 Operation and MaintenenceProduct Overview · Introduction1 · 1 · 2

Blank Page


First editionExternal Consultant2007-07-3001

RemarksAuthorDateEdition

Document History





Objectives

Objectives: to be able todescribe the basic concepts of the 9500 MPR.





Objectives [cont.]






Table of Contents

Switch to notes view! Page

1 Understanding the 9500MPR innovations 71.1 Classification of the new generation products 81.2 Presentation 91.3 Multiservice Aggregation Layer 101.4 Service Awareness 121.5 Packet Node 141.6 Service-driven Packet Adaptive Modulation 16

Blank Page 182 System description 19

2.1 System description 202.2 9500 MPR Node 23

Blank Page 283 Radio configuration 29

3.1 Radio configuration 304 System configuration 31

4.1 Example of System configurations 32Blank Page 37End of Module 38





Table of Contents [cont.]







1 Understanding the 9500MPR innovations






1.1 Classification of the new generation products

Alcatel-Lucent microwave product acronyms are derived as follows:

9 5 0 0 MPR9 5 0 0 MPR

Means radioproduct

5 for Radio Cross-Connect M = Microwave

P = Packet

R = Radio






1.2 Presentation

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






1.3 Multiservice Aggregation Layer

nxE1

Ethernet

ISAM, WiMAX

2GAggregated trafficover Ethernet

Packet Backhaul network

Ethernet aggregation layer

Access network

Any TDM/Ethernet interfaces

nxE1

3G HSDPAVoice on R99

9500 MPR

GSM

Single technology throughout the network: Ethernet as convergence layer

9500 MPR aggregates and carries over a COMMON PACKET LAYER: TDM 2G, 3G and IP/Ethernet. This allows sharing of common packet transmission infrastructures, regardless of the nature of carried traffic.

Due to the nature of Ethernet, each service can be discriminated based on several parameters like quality of service.

Mapping different access technologies over Ethernet is achieved by standardized protocols like circuit emulation and pseudo-wire.






1.3 Multiservice Aggregation Layer [cont.]

Multiservice aggregation layer means the capacity to use Ethernet as common transmission layer to transport any kind of traffic. Ethernet becomes the convergence layer.

E1, ATM and IP/Eth is carried over a common layer and therefore over one single physical interface. This allows sharing a common packet transmission infrastructure, regardless of the nature of carried traffic.

Due to the nature of Ethernet we can then discriminate each service based over several parameters like quality of service.

Mapping over Ethernet of these different technologies is achieved by standardized protocols like circuit-emulation and pseudo-wire. The use of standard protocol is a key factor that allows operators to recover their original traffic at any point in the network from any equipment compliant to the standards.






1.4 Service Awareness

SERVICE CLASSIFICATION: Voice, BroadbandINPUTS : Any interfaces (E1, Ethernet) PACKETIZATION PROCESSING:

TDM Standard CEoEth [MEF8]Ethernet Native

High Priority Queue;Guaranteed bit rate

Low Priority Queue;Remaining bit rate

SERVICE AGGREGATION and OVERBOOKING: Service aggregation using statistical multiplexing, obtaining dramatic band reduction

SERVICE QUALITY MANAGEMENT:Service scheduler queuing packets according to the quality of service assigned.HIGH for real-time traffic, LOW for Broadband

Constant bit rate servicesRevenue based on real-time communication

Constant bit rate servicesRevenue based on real-time communication

Variable bit rate servicesRevenue based on access to contents

Variable bit rate servicesRevenue based on access to contents

Voice, Video Telephony

HiSpeed @, VideoD & Gaming

Decoupling access technology from transport technology: manage services

Service awareness means the ability to discriminate the different traffic types carried over the converged Ethernet stream. Our traffic flow can be composed by E1s, ATM and/or IP/Eth, coming from different sources, and therefore having different requirements. For instance ATM traffic from a 3G base stations can carry voice (high priority, real time service) and data (lower priority and possibly non real time with high variability load, such as internet browsing, music download or video streaming).

Service awareness is what allows identifying the traffic types, and in case of the non real time variable bit rate one, optimize the band with overbooking of the radio scarce resource.






1.4 Service Awareness [cont.]






1.5 Packet Node

Address new data services in the best way: packet natively

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






1.5 Packet Node [cont.]

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






1.6 Service-driven Packet Adaptive Modulation

14 MHz 16 Mb/s in 4 QAM at 99.999% availability

14 MHz 48 Mb/s in 64 QAM at 99.9% availability

Capa

city

Time line unavailability

99.999.9999.999

Outage

Capacity

Customer Satisfaction

Sati

sfac

tion

16 QAM

4 QAM

64 QAM

Modulation schemes

Voice Traffic Best Effort Traffic

9500 MPR

Maintain the same level of quality for voice services as in the TDM network

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






1.6 Service-driven Packet Adaptive Modulation [cont.]

Total BandNative Packet trafficFadingTotal Band

Packets traffic over TDM Fading

Microwave TDM Microwave Packet

Adaptive modulation adds or removes capacity from physical interfaces

Complex physical interfaces networking operation is required to ensure that only low priority traffic is dropped

Adaptive modulation adds or removes capacity from best effort services, regardless of physical interface

Interface decoupling from service classification removes any additional networking operations, low priority service is always dropped, regardless of what the interface is





Blank Page






2 System description






2.1 System description

9500 MPR radio system family supports, in a common platform, PDH E1 and packet data (Ethernet) applications. Outdoor transceivers are available in the frequency range from 6 GHz up to 38 GHz. For the Outdoor transceiver, 1+0 is the optimized configuration, with branching systems outside the ODU. 1+1 configuration is obtained with external dedicated mechanical arrangement.






2.1 System description [cont.]

9500 MPR in the split mount architecture is built by two separate units:

MSS (Microwave Service Switch): indoor unit for split mount and stand alone configurations (Ethernet uplink)

ODU300 microwave uplink for split mount configurations






2.1 System description [cont.]

MSS implements functionalities of grooming, routing, switching and protection, exploiting a packet oriented technology.The Core-E platform, with symmetrical x-connection functions, manages different radio directions, with the possibility to add-drop tributaries in case of local PDH/Ethernet accesses. Core-E platform is based on packet technology (Ethernet Switch) with a generic interface serial GbEth between Core-E and peripheralsThe peripherals are independent modules connecting the Core-E to a set of different external interfaces, through a high speed serial bus. The available peripherals are:

32 x E1 local access modulesRadio Access modules (modem card)

The PDH incoming traffic is converted into Ethernet packets and then sent to the Ethernet switch; the packet overhead is optimized before to be sent in the air.






2.2 9500 MPR Node

The 9500 MPR Node supports up to 6 RF links for operation on the same or different frequency bands using the MSS-8 Unit.

The ODU for each link is connected to plug-in Radio Access card inside the site aggregator.

Other plug-in cards provide line interface access (TDM and native IP), management, and so on.

9500 MPR Node supports a mix of non-protected and protected or diversity operation for single link, repeater or star radio configurations.






2.2 9500 MPR Node [cont.]

MSS-8

Slot 1 Slot 2

Slot 3 Slot 4

Slot 5 Slot 6

Slot 7 Slot 8

Slot

9

Slot 1 reserved for Core-E Main Slot 2 reserved for Core-E SpareSlot 3 to 8 Universal (any Tributary and Radio card)Slot 9 reserved for FANSThe cards belonging to a protected configuration must be installed on the same row (the Main card is on the left side, the Spare card is on the right side)Supports 6 Unprotected links or1 Protected and 4 Unprotected links or2 Protected and 2 Unprotected links or3 Protected links

The figure illustrates platform functions/capabilities.





Slot 1 reserved for Core-E Main Slot 2 reserved for Core-E SpareSlot 3 and 4 Universal (any Tributary and Radio card)Slot 5 reserved for FANSIn case of protected configuration the Main card is on the left side, the Spare card is on the right side.Supports 2 Unprotected links or1 Protected link



MSS-4

Slot 1 Slot 2

Slot 3 Slot 4 Slot

5

The figure illustrates platform functions/capabilities.







Radio capacity, channelling scheme and modulation (Static Modulation)

68 E1156,80 Mbit/s128 QAM

128 QAM

256 QAM

64 QAM

32 QAM

16 QAM

4 QAM

64 QAM

16 QAM

4 QAM

64 QAM

16 QAM

4 QAM

Modulation

313,60 Mbit/s

177,60 Mbit/s

130,56 Mbit/s

111,36 Mbit/s

87,04 Mbit/s

43,52 Mbit/s

65,28 Mbit/s

43,52 Mbit/s

21,76 Mbit/s

32,64 Mbit/s

21,76 Mbit/s

10,88 Mbit/s

Net radio throughput

136 E156 MHz

77 E1

56 E1

48 E128 MHz

37 E1

18 E1

27 E1

18 E114 MHz

8 E1

13 E1

8 E17 MHz

4 E1

E1 Equivalent Capacity(TDM2TDM)Channel Spacing

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







Radio capacity, channelling scheme and modulation (Adaptive Modulation)

32,64 Mbit/s

21,76 Mbit/s

10,88 Mbit/s

65,28 Mbit/s

43,52 Mbit/s

21,76 Mbit/s

130,56 Mbit/s

87,04 Mbit/s

43,52 Mbit/s

Net radio throughput

13 E164 QAM

8 E116 QAM

4 E14 QAM

7 MHz

27 E164 QAM

18 E116 QAM

8 E14 QAM

14 MHz

56 E164 QAM

37 E116 QAM

18 E14 QAM

28 MHz

Equivalent capacity E1 (Note)

ModulationChannellingSpacing

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





Blank Page






3 Radio configuration





3 Radio configuration

3.1 Radio configuration

1+0 unprotected

1+1 Hot-Standby (HS) (2 coupler types: balanced 3dB and unbalanced 1.5/6.0dB)

1+1 Hot-Standby Space Diversity (HSSD) (no combiner)

1+1/2x(1+0) Frequency Diversity (FD) (co-polar)

1+1/2x(1+0) Frequency Diversity (FD) (hetero-polar)





4 System configuration






4.1 Example of System configurations

TDM Over Ethernet Packet Node - Mapping of 32 E1 on Ethernet






4.1 Example of System configurations [cont.]

TDM and Ethernet Terminal Packet Transport - 32 E1 Access, 1 Radio Direction







TDM and Ethernet Add/Drop N1 Packet Node - Ethernet and 32 E1 Local Access, 2 unprotected links







TDM and Ethernet Terminal Packet Node-Ethernet and 32 E1 Local Access, 1 protected link







TDM and Ethernet Add/Drop Packet Node-Ethernet and 32 E1 Local Access, 1 unprotected link, 1 protected link





Blank Page






End of ModuleIntroduction





Module 2Architecture

3JK Edition 1.00





9500 MPR · 9500MPR R 1.2.1 Operation and MaintenenceProduct Overview · Architecture1 · 2 · 2

Blank Page




Document History





Objectives

Objectives: to be able todescribe the main functionalities of the 9500 MPR.





Objectives [cont.]






Table of Contents


1 MSS Architecture 71.1 MSS Architecture 81.2 PDH Terminal with PDH local accesses 91.3 Flash Cards with Licences 101.4 ODUs 13

Blank Page 142 Traffic profiles 15

2.1 Traffic profiles 162.2 TDM2TDM 192.3 TDM2Eth 212.4 ETH2ETH 23

Blank Page 243 Traffic Management (QoS) 25

3.1 Quality Of Services (QoS) 263.2 Core-E QoS 273.3 Core-E scheduler 283.4 Modem unit QoS 293.5 Modem unit scheduler 303.6 Ethernet Traffic Management 31

3.6.1 Bridge type change 323.6.2 Reserved Multicast Addresses 33

4 Synchronisation 354.1 Synchronisation 364.2 Differential clock recovery 374.3 Adaptive clock recovery 384.4 Synchronisation Interface 39

Blank Page 405 Cross-connections 41

5.1 Cross-connection 425.2 E1 Cross-connection 435.3 Ethernet Cross-connection 44

6 Protections 456.1 Protections 466.2 9500 MPR Packet Node Full Protection (Radio) 476.3 RPS Switching Criteria 496.4 EPS Switching Criteria 506.5 HSB Switching Criteria 51

End of Module 52












1 MSS Architecture





1 MSS-8 Architecture

1.1 MSS Architecture

ControllerPSU

ETHERNETSWITCH

4x10/100/1000 Ethernet

LIU

Flash

RAM

GbEthGbEth

Core-E

32xE1 AccessModule

AccessPeripherals

RadioPeripherals

MODEM 300 Module –IF interface

(to ODU)

1x1000 Optical Ethernet

LIU

Core-E platform:

symmetrical Cross-connection function

able to manage different radio directions

add-drop tributaries in case of local PDH/Ethernet accesses

4 x Electrical GbEth + 1 optional Optical GbEth

Peripherals (6 modules in MSS-8; 2 modules in MSS-4)

32 x E1 local access module (SCSI 68 32E1)

Radio IF interface






1.2 PDH Terminal with PDH local accesses

MODEM

300

Module

ControllerFlash

RAM

PSU

PDHAccessModule(TDMoP)

E1

ODUETHERNET

SWITCH

MSSMSS LIU

4xEth.

Core-E

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






1.3 Flash Cards with Licences

Super PDH licences (TDM2TDM):6x40 Mbps5x40/1x80 Mbps4x40/2x80 Mbps6x80 Mbps5x40/1x100 Mbps4x40/2x100 Mbps6x100 Mbps5x40/1x150 Mbps4x40/2x150 Mbps6x150 Mbps5x40/1x300 Mbps4x40/2x300 Mbps6x300 Mbps

5x40/1x60 Mbps4x40/2x60 Mbps6x60 Mbps5x40/1x130 Mbps4x40/2x130 Mbps6x130 Mbps

The licences are stored in the Flash card installed in the Core-E Module. The Flash card stores also the Equipment software, the equipment MIB and the equipment MAC address.

Note: With these flash cards the available circuit emulations are: TDM2TDM, ETH2ETH.






1.3 Flash Cards with Licences [cont.]

Site Aggregator licences(TDM2TDM & TDM2ETH):

6x40 Mbps5x40/1x80 Mbps4x40/2x80 Mbps6x80 Mbps5x40/1x100 Mbps4x40/2x100 Mbps6x100 Mbps5x40/1x150 Mbps4x40/2x150 Mbps6x150 Mbps5x40/1x300 Mbps4x40/2x300 Mbps6x300 Mbps

5x40/1x60 Mbps4x40/2x60 Mbps6x60 Mbps5x40/1x130 Mbps4x40/2x130 Mbps6x130 Mbps

The licences are stored in the Flash card installed in the Core-E Module. The Flash card stores also the Equipment software, the equipment MIB and the equipment MAC address.

Note: With these flash cards the available circuit emulations are: TDM2TDM, ETH2ETH, TDM2ETH.






1.3 Flash Cards with Licences [cont.]

Adaptive Modulation (TDM2TDM):5x40/1x130 Mbps4x40/2x130 Mbps6x130 Mbps6x404x40/2x80 Mbps6x80 Mbps5x40/1x150 Mbps

Adaptive Modulation (TDM2ETH):5x40/1x130 Mbps4x40/2x130 Mbps6x130 Mbps6x404x40/2x80 Mbps6x80 Mbps5x40/1x150 Mbps






1.4 ODUs

ODU300 are designed for direct-antenna mounting.ODU300 supports:

Modulation rates from 4 QAM to 256 QAMBandwidths from 7 to 56 MHzFrequency bands from 6 to 38 GHzHigh transmit power





Blank Page






2 Traffic profiles





2 Traffic profiles

2.1 Traffic profiles

Three kinds of traffic profiles have been identified:

1. TDM2TDM ( 9500MPR ⇔ 9500MPR, internal TDM ) 2. TDM2Eth ( 9500MPR ⇔ TDM to Ethernet )3. DATA (Ethernet to Ethernet)

Profiles 1 and 2 meet MEF8 standard





2 Traffic profiles

2.1 Traffic profiles [cont.]

Case 1

The E1 stream is inserted in Node 1 and extracted in Node 2. In this case the two IWFs used to packetizethe traffic for the Ethernet switch in the Core-E module are both internal to the 9500 MPR network. The Circuit Emulation Service is TDM2TDM in Node 1 and Node 2. The Cross connections to be implemented are PDH-Radio type.

Case 2

The E1 stream is inserted in Node 1 and extracted in Node 2. One IWF is inside the 9500 MPR, but the second IWF is external to the 9500 MPR network. The Circuit Emulation Service is TDM2ETH in Node 1 and Node 2. The Cross connections to be implemented are PDH-Radio type in Node 1 and Radio-Eth type in Node 2

Case 3

The E1 stream is inserted/extracted in Node 1. One IWF is inside the 9500 MPR, but the second IWF is external to the 9500 MPR network. The Circuit Emulation Service is TDM2ETH in Node 1 and Node 2. The Cross connections to be implemented are PDH-Eth type in Node 1.





2 Traffic profiles

2.1 Traffic profiles [cont.]

Cases 4 and 5

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





2 Traffic profiles

2.2 TDM2TDM

E1 traffic packetized only internally to 9500MPR equipment

E1

BSC

PDH

RADIORADIO

RADIO

BTS

E1

BTSE1

BTSE1

Flow Id present (user defined)

intermediate node configuration (E1 provisioning):

node by node (building Cross-connection tables based on Flow Id)

bandwidth guaranteed (according to QoS Highest Queue Priority association)

no flooding-autolearning necessary





2 Traffic profiles

2.2 TDM2TDM [cont.]

Both the IWFs belong to 9500MPR and the packets are not supposed to exit the 9500 MPR network.

The IWF parameters listed above, have predetermined values and don’t need to be provisioned.

Mac addresses are determined as consequences of the cross connections.

Payload size is fixed to 122 bytes

ECID will be the same value as Flow Id

TDM clock source: clock recovery differential,

Flow Id provisioned by ECT/NMS

ECID = Emulated Circuit Identifier





2 Traffic profiles

2.3 TDM2Eth

E1 traffic both internal and external to 9500MPR equipment

E1

BSC

E1EthEth

PSN

BTS

BTS

BTSE1

E1

Flow Id present (user defined)

all the parameters must be configured compliant with the MEF8 standard

adaptive or differential clock recovery supported

bandwidth guaranteed (according to QoS Highest Queue Priority association)

destination MAC added before going into whole network (MEF8 compliant)





2 Traffic profiles

2.3 TDM2Eth [cont.]

Only one of the IWFs belongs to 9500MPR and the packets are supposed to exit the 9500MPR network.

MAC addresses: in all involved nodes are determined as consequences of the cross connections; the only exception is the Ethernet Terminal Node (the node where the TDM2ETH traffic goes through an user Ethernet port). In such ETN the source address is the node Mac address, the destination Mac address will be provisioned by ECT/NMS.

Payload size: fixed to 256 bytes

ECID : provisioned by ECT/NMS, 2 different values may be used for each direction

TDM clock source is provisioned by ECT/NMS: clock recovery adaptive, clock recovery differential

Flow Id is provisioned by ECT/NMS (One Vlan is assigned to each bi-directional circuit emulated E1 flow)

ECID = Emulated Circuit Identifier





2 Traffic profiles

2.4 ETH2ETH

None of the IWFs belongs to 9500MPR.

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

Eth

Eth

RNCEth

Eth

WiMAX(NodeB)

WiMAX(NodeB)

WiMAX(NodeB)

EthEth

EthRNC

PSN

PSN

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.





Blank Page






3 Traffic Management (QoS)






3.1 Quality Of Services (QoS)

The QoS function inside 9500 MPR is the result of a distributed implementation in the switch and Radio Interface module. Both those QoS functions must be properly configured in order to get the wished behavior on Ethernet flows that will be transmitted towards the Radio.






3.2 Core-E QoS

The figure shows an overview of the QoS implementation inside the switch.

The Quality of Service feature of the Ethernet switch provides four internal queues per port to support four different traffic priorities. Typically the high-priority traffic experiences less delay than that low-priority in the switch under congested conditions.

For each egress port according to method of QoS classification configured in the switch, the packets are assigned to each queue. The higher priority queue is reserved for TDM flows; the remaining queues are shared by all Ethernet flows according the classification mechanism configured by CT/NMS.

For generic Ethernet flows in the switch it is possible by CT/NMS to assign the priority to each packet according to the information in:

1. IEEE std 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag. If the tag is present the correspondent priority is assigned to the packet.

2. DiffServ: each packet is classified based on DSCP field in the IP header to determine the priority.

802.1P priority Queue 111, 110 Q5 (higher priority)

101 Q4 100 Q3

011, 000 Q2 010, 001 Q1

DiffServ priority Queue 111000, 110000, 101110, 101000 Q5 (higher priority) 100110, 100100, 100010, 100000 Q4 011110, 011100, 011010, 011000 Q3 010110, 010100, 010010, 010000 001110, 001100, 001010, 001000

000000

Q2

All remaining values Q1






3.3 Core-E scheduler

The scheduler algorithm cannot be configured.

HQP scheduler algorithm is used on queues Q8, Q7 and Q6.

Deficit Weighted Round Robin (DWRR) is used on the other queues with the following weights:

1Q1

2Q2

4Q3

8Q4

16Q5 (higher priority)

WEIGHTQUEUE






3.4 Modem unit QoS

In the figure is shown an overview of the QoS implementation inside the Radio Interface module.

The QoS feature provides eight internal queues to support different traffic priorities. The QoS function can assign the packet to one of the eight egress transmit queues according to the information inside the packet as 802.1P field, DiffServ field, Ethertype or 802.1Q VLAN_ID.

QoS based on IEEE std. 802.1pWhen 802.1p QoS mechanism is adopted, the reference is the standard “IEEE 802.1D-2004 Annex G User priorities and traffic classes” that defines 7 traffic types and the corresponding user priority values.

Considering that in the Radio Interface module for generic Ethernet traffic there are five egress queuesthe mapping 802.1p value to queue is the following:

QoS based on DiffServ

802.1p priority Queue 111, 110 Q5 (higher priority)

101 Q4 100 Q3

011, 000 Q2 010, 001 Q1

DiffServ priority Queue 111000, 110000, 101110, 101000 Q5 (higher priority) 100110, 100100, 100010, 100000 Q4 011110, 011100, 011010, 011000 Q3 010110, 010100, 010010, 010000

001010, 001100, 001010, 001000, 000000 Q2 All remaining values Q1






3.5 Modem unit scheduler

The scheduler algorithm implemented inside the Modem unit is High Queue Pre-empt: when a packet arrives in the higher priority queue it is immediately transmitted.






3.6 Ethernet Traffic Management

The Ethernet traffic is all the traffic entered the MPR network from user Ethernet ports. By ECT/NMS it is possible to define the way to manage the Ethernet traffic according to one of the following options:

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






3.6.1 Bridge type change

In case of change of the bridge type from 802.1Q to 802.1D, the content of the VLAN table and the VLAN assigned to the user Ethernet ports, remains stored in the NE MIB. Note: To change the configuration from 802.1D to 802.1Q, it is necessary to configure all the Ethernet ports in “Admit all” mode to avoid hits on the traffic on that specific port.






3.6.2 Reserved Multicast Addresses

ForwardCCM and LTM Group Destination MAC Addresses (IEEE 802.1ag)

01-80-C2-00-00-30 - 01-80-C2-00-00-3F

ForwardReserved for GARP Application 01-80-C2-00-00-22 - 01-80-C2-00-00-2F

ForwardGVRP Address (IEEE 802.1Q) 01-80-C2-00-00-21

ForwardGMRP Address (Clause 10 of IEEE 802.1D) 01-80-C2-00-00-20

ForwardReserved 01-80-C2-00-00-11 - 01-80-C2-00-00-1F

ForwardAll LANs Bridge Management Group Address01-80-C2-00-00-10

DiscardReserved for future standardization 01-80-C2-00-00-0F

DiscardIEEE 802.1AB LLDP multicast address 01-80-C2-00-00-0E

DiscardReserved for future standardization 01-80-C2-00-00-04 - 01-80-C2-00-00-0D

Discard IEEE 802.1X PAE address 01-80-C2-00-00-03

Discard Clause 43 (Link Aggregation) and Clause 57 (OAM) of IEEE 802.3 01-80-C2-00-00-02

Flow-Control enabled: Peer Flow-Control disabled: DiscardClause 31 (MAC Control) of IEEE 802.3 01-80-C2-00-00-01

Forward Bridge Group Address 01-80-C2-00-00-00

Action Function Reserved Multicast Address

The table summarizes the actions taken for specific reserved multicast addresses. Frames identified with these destination addresses are handled uniquely since they are designed for Layer 2 Control Protocols.

The actions taken by the system can be:

Discard - The system discards all ingress Ethernet frames and must not generate any egress Ether-net Frame carrying the reserved multicast address.

Forward - The system accepts all ingress Ethernet frames as standard multicast frames and for-wards them accordingly.

Peer - The system acts as a peer of the connected device in the operation of the relevant Layer 2 Control Protocol.





Blank Page






4 Synchronisation





4 Synchronisation

4.1 Synchronisation

TDM data flow is fragmented and the fragments are transmitted over a Packet Switched Network (PSN); The received fragments need to be reassembled in the original TDM data flow at the “original bit rate”

Two main methods can be used to recover at the RX site, the original bit rate:

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

Adaptive: simpler network, but performances depends on the PDV (Packet Delay Variation) in the Network. Always used when the reference clock isn’t distributed on the whole network.

Differential: used in case of clock distribution on the whole network. It’s more reliable than Adaptive; also used in TDM2TDM traffic (MPR to MPR).

N.B.: In meshed networks (rings) do not close the synchronisation configuration.





4 Synchronisation

4.2 Differential clock recovery

End System1

IWF IWF

End System2

PSNPSN

Common reference clock IS available at both Ends.

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





4 Synchronisation

4.3 Adaptive clock recovery

End System1

IWF IWF

End System2

PSNPSN

Common reference clock is NOT available at both Ends.

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





4 Synchronisation

4.4 Synchronisation Interface

To implement differential CK recovery, for each node must be defined:NE Role definition, related to NE CK

MasterSlave

NE Synchronisation Source definitionPrimarySecondary

Source choice, both for primary and secondary, with proper rulefree runningPDH interface [port]external interface [2.048; 5.000; 10.000 MHz]radio interface





Blank Page






5 Cross-connections





5 Cross-connections

5.1 Cross-connection

SLOT 3 (PDH) SLOT 4 (RADIO)

SLOT 5 SLOT 6 (RADIO)

SLOT 7 SLOT 8

ETH 4

ETH 3

ETH 2

ETH 1

The cross-connections between slots and between slot and Ethernet user ports are realized with a Layer-2 Ethernet Switch inside the Main Core-E.

The decision made by the switch to forward the received packet is based on the destination MAC address.





5 Cross-connections

5.2 E1 Cross-connection

Each E1 can be cross connected independentlyE1 can be cross connected to any of the following interfaces:

Radio interfaceEthernet interface

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





5 Cross-connections

5.3 Ethernet Cross-connection

Ethernet cross connection is based on Ethernet switching (level 2)According to destination address each packet is switched to the correct port, as reported in an “Address Resolution Table” (ART)If destination address is not present in the ART a flooding mechanism is foreseen





6 Protections





6 Protections

6.1 Protections

Supported Protection types :

1) RPS (Radio Protection Switching) Hitless for each radio direction (RPS-RX)RPS is distributed in 9500 MSS modules before termination of 9500 MSS frame.

2) EPS (Equipment Protection Switching) for each module typeBoth Working and Spare modules send its own signal to the Core-E. Core-E selects the best signal.

3) HSB (Hot StandBy)Spare ODU module is powered off.





6 Protections

6.2 9500 MPR Packet Node Full Protection (Radio)

Legend:

1 RPS

2 EPS

3 HSB





6 Protections

6.2 9500 MSS Packet Node Full Protection (Radio) [cont.]

2

2

Legend:

2 EPS





6 Protections

6.3 RPS Switching Criteria

The switching criteria are:

Early Warning

High BER

Dem Fail

Loss of Frame (LOF) on the radio signal coming from the direct way

Loss of Frame (LOF) on the radio signal coming from the cross way





6 Protections

6.4 EPS Switching Criteria

The switching criteria are:

Peripheral Card Fail (switching off of the peripheral included)

Peripheral Card Missing

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





6 Protections

6.5 HSB Switching Criteria

The switching criteria are :

Radio Interface Peripheral Card Fail (switching off of the peripheral included)

Radio Interface Peripheral Card Missing

MSS-ODU cable loss

ODU TX chain alarm (this is an OR of the following alarms: LOS at ODU input, modFail, txFail, ODU card fail)





End of ModuleArchitecture





Module 3Management System

3JK Edition 1.00





9500 MPR · 9500MPR R 1.2.1 Operation and MaintenenceProduct Overview · Management System1 · 3 · 2

Blank Page


First editionExternal consultant2007-07-3001


Document History





Objectives

Objectives: to be able todescribe the Management System of the 9500 MPR.





Objectives [cont.]






Table of Contents


1 Management System 71.1 Network Management 81.2 IP addresses 91.3 TMN communication channels 101.4 LCT Connection 11

Answer the Questions 12Blank Page 13End of Module 14












1 Management System





1 Management System

1.1 Network Management

1350 OMS1350 OMS

Access & Transport Network Management

Multi-protocol management

SNMP

Q3

QB3*

TL1

All Access and Transport

Integrated in a single

Network Management Suite

9600 LSY9600 LSY 9600 USY

9400 AWY

1650SMC1662SMC1642EMNew

9500 MPR

1850TSS9500 MXC

Providing a single managed network reduce the operational expenditure of a network directly improving themargin in the P&L of an Operator.

Alcatel-Lucent offers a unified management system capable to manage the entire access and transportnetwork under a single Network Management Suite: the 1350 OMS.

9500 MPR together with all other Microwave and Optical transmission Network Element is fully integrated into 1350 OMS Network Management System providing all the tools required to operate the network





1 Management System

1.2 IP addresses

The NE has the following IP addresses:NE IP address: it is the Controller IP address (default IP address = 10.0.1.2 with fixed mask 255.255.255.255);TMN IP address: it is the IP address relevant to the Ethernet TMN port (default IP address = 10.0.1.2 with mask 255.255.255.0);TMN Port 4 IP address: the Port 4 can be used not for traffic, but for TMN.

IP address assignment rules:the TMN IP addresses of 2 NEs connected through a radio link must belong to 2 different subnetworks;the TMN IP addresses of 2 NEs connected through an Ethernet cable must belong to the same subnetwork.

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





1 Management System

1.3 TMN communication channels

On the 9500 MPR two types of TMN communication channels are present:

TMN channel carried by 64 kbits/sec channel inside Radio frame;TMN channel carried by Ethernet frames in Ethernet tributary 4 (on the front panel of the Core-E module).





1 Management System

1.4 LCT Connection

9500MPR can be controlled by a LCT connected to the Core-E unit.The connection can be performed by using:

The dedicated NMS Ethernet portTraffic Ethernet port, configured as TMN port.





Answer the Questions

How many IP addresses can be assigned to the NE?Which bit rate has been assigned to the TMN RF channel in the Radio frame?Which connections are available for the LCT?





Blank PageNode A

ETH GeneratorPDH Generator

Node E

Node B

Node C

Node D

0.0.0.1OSPF AREAOFFNMS P4

00:20:60:05:02:07NE MAC10.0.10.1NMS IP10.0.3.1NE IP

VLAN ID11 12 13 14

10 11

1+1 HSB

1+1 FD

Traffic E1+ETHTMNTraffic E1 TDM2ETH

Traffic ETHPort NumberVLAN ID

Traffic E1 TDM2TDM

VLAN ID

11 12 13 14 27 28 41 42

1 2 3 4 17 18 3132

1 2

VLAN ID27 28

1,2,…

1,2,…

5 6 7 8

VLAN ID41 42

ETH 2

ETH 1

ETH 1

ETH 2


00:20:60:05:02:08NE MAC10.0.30.2NMS IP10.0.3.2NE IP


00:20:60:27:02:07NE MAC10.0.30.3NMS IP10.0.3.3NE IP

0.0.0.1OSPF AREA10.0.5.4NMS P4

00:20:60:27:02:05NE MAC10.0.4.4NMS IP10.0.3.4NE IP


00:20:60:05:02:06NE MAC10.0.4.5NMS IP10.0.3.5NE IP

0.0.0.1OSPF AREA10.0.5.6NMS P4

00:20:60:05:02:05NE MAC10.0.6.6NMS IP10.0.3.6NE IP

10.0.10.1DEFAULT GATEWAY10.0.10.100PC IP

10.0.6.6DEFAULT GATEWAY10.0.6.100PC IP

Node F

TDM A

TDM C

TDM B

TDM C

TDM A

TDM B

Syncro Scheme

Net Mask 255.255.255.0





End of ModuleManagement System





Module 1MSS HW Hardware Architecture

3JK Edition 1.00

Section 2Functional Description




9500 MPR · 9500MPR R 1.2.1 Operation and MaintenenceFunctional Description · MSS HW Hardware Architecture2 · 1 · 2

Blank Page




Document History





Objectives

Objectives: to be able todescribe the functionality of each unit of the MSS-4/MSS-8.





Objectives [cont.]






Table of Contents


1 PDH Access Unit 71.1 PDH Access unit 8

Blank Page 102 Modem unit 11

2.1 Modem unit 12Blank Page 14

3 Core-E unit 153.1 Core-E unit 16

Blank Page 184 Distributors 19

4.1 Distributor 20Answer the Questions 29Blank Page 30End of Module 31












1 PDH Access Unit





1 PDH Access Unit

1.1 PDH Access unit

CESoP32 E1 LIUs

32 E1 module

wk Core-E

sp Core-E

wk Core-E

sp Core-E

FPGA(Ceres)

In the TX direction, the E1 PDH card (E1 Access) processes and encapsulates up to 32 E1 input lines into an Ethernet packet that is sent to the Core-E card(s).

In the RX direction, the E1 Access card extracts data from the Ethernet data packets and processes the data to provide up to 32 E1 output lines.

The 32xE1 Local Access Module performs the following macro functions:

Termination of 32 E1 signals (32 E1 bi-directional interfaces according ITU-T G.703 on the front panel)

Framed E1 bi-directional alarm management

Bi-directional Performance Monitoring on Framed E1

Encapsulation/Extraction of those PDH data flows into/from standard Ethernet packets Inter Working Function

Reconstruction of the original PDH Timing meeting G823/824 Req.

Selection of the Active Core-E

Sending/getting those std Eth packets to the Core-E module

Communication with the Controller for provisioning and status report

The module communicates with the Core-E modules through two GbEth Serial copper bi-directional interfaces on the backplane. The spare Core-E in not implemented.





1 PDH Access Unit

1.1 PDH Access unit [cont.]

E117-32

E11-16





Blank Page






2 Modem unit





2 Modem unit

2.1 Modem unit

Analog Chain

GbE Serial from/to Alternate Radio Board for RPS

TXMODULATOR

RXDEMOD

MODEMASIC

DAC

∏ / 2

DAC

I

Q

IF RX

311 Mhz

ADC

∏ / 2

ADC

I

Q

126 Mhz

IF cableinterface

AIR FRAMERPDH/Data

management

IDU/ODUcommunication

EPSTX

AIR deFRAMERPDH/Data

management

ODU/IDUcommunication

RPS RX

FPGA(Guinnes)

IF TX

In Tx direction, the MODEM 300 Module generates the IF signal to be sent to an MXC Out Door Unit. Such signal contains a Constant Bit Rate signal built with the Ethernet packets coming from the Core-E; those packets are managed in a different way depending on their own native nature.Digital Framer

Classification of incoming packets from the Core-E (QoS)FragmentationAir Frame Generation (synchronous with NE clock)

Digital ModulatorTX Analog Chain

DAC & low pass filteringModulation to 311 MHz IF TX

In Rx direction, the MODEM 300 Module terminates the IF signal coming from the MXC Out Door Unit extracting the original CBR and then the original Ethernet packets to be given the Core-E which distributes them to the proper Module. RX Analog Chain

126 MHz IF RX demodulation to I & Qlow pass filtering & ADC

Digital DemodulatorCarrier & CK recoveryEqualisationError Correction

Digital DeframerRPS (hitless)Defragmentation





2 Modem unit

2.1 Modem unit [cont.]

Transmitter connected to the antenna





Blank Page






3 Core-E unit





3 Core-E unit

3.1 Core-E unit

Based on packet technology with 8 GbEth serial internal interfaces between Core-E and peripherals (jumbo frames 9728 bytes allowed)

4x10/100/1000 Eth embedded interface (RJ45)

1x1000 base-Lx or Sx (SFP optical interference), available with an optical plug-in.

Macro Functions

Controller

Layer 2+ Eth Switch, VLAN management & MAC based

Ethernet MAC learning

x-connect function for PDH and Data payload traffic;

For any “packetized” flow, the switch will be in charge to manage the EPS also.

QoS management.

Selection of the synchronization Ck to be distributed to all plug-in.

The flash card stores the licence type, the equipment software, the equipment MIB and the equipment MAC address.





3 Core-E unit

3.1 Core-E unit [cont.]





Blank Page






4 Distributors





4 Distributors

4.1 Distributor

The Distributor subracks available are shown in the next pages.





4 Distributors

4.1 Distributor [cont.]

Protection Panel 32E1 SCSI 68 - 1.0/2.3 75 ohm (Front/Rear) (3DB16104AAAA)





4 Distributors


Protection Panel RJ45 120 ohm (Front/Rear) (1AF15245ABAA)





4 Distributors


Protection Panel 32E1 SCSI 68 - 1.6/5.6 75 ohm (Front)





4 Distributors


Protection Panel 32E1 BNC 75 ohm (Front)





4 Distributors


Connector support 1.6/5.6 75 ohm Panel 1U (3CC08061AAAA)





4 Distributors


Connector support BNC 75 ohm Panel 1U (3CC08061ABAA)





4 Distributors


Support 19 Inch modules 120 ohm Panel 3U (3CC07810AAAA)





4 Distributors


E1 Protection SCSI 68/Sub-D 37 (Front/Rear) (3DB16102AAAA)






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





End of ModuleMSS HW Hardware Architecture





Module 2ODU HW Hardware Architecture

3JK Edition 1.00

Section 2Functional Description




9500 MPR · 9500MPR R 1.2.1 Operation and MaintenenceFunctional Description · ODU HW Hardware Architecture2 · 2 · 2

Blank Page


First editionLast name, first nameYYYY-MM-DD01


Document History





Objectives

Objectives: to be able todescribe the functionality of the ODUs.





Objectives [cont.]






Table of Contents


1 Outdoor Units 71.1 ODU300 Construction and Mounting 81.2 ODU300 Characteristics 9

2 ODU300 block diagram 112.1 ODU300 block diagram 12

3 Outdoor Installations 133.1 Installing the ODU 143.2 Direct-Mounted ODUs 153.3 Remote-Mounted ODUs solution 1 163.4 Remote-Mounted ODUs solution 2 173.5 Waveguide Flange Data 193.6 Grounding the ODU 203.7 ODU external connectors 21

Answer the Questions 23End of Module 24












1 Outdoor Units





1 Outdoor Units

1.1 ODU300 Construction and Mounting

Construction comprises:Cast aluminium basePressed aluminium coverBase and cover passivated and then polyester powder coatedCompression seal for base-cover weatherproofingCarry-handle

ODU300 Housing

The ODUs include a waveguide antenna port, Type-N female connector for the ODU cable, a BNC female connector (with captive protection cap) for RSSI access, and a grounding stud.

The ODUs, are designed for direct antenna attachment via an 9500MPR-specific mounting collar supplied with the antennas.

ODU polarization is determined by the position of a polarization rotator fitted within the mounting collar.

A remote ODU mounting kit is available as an option. These may be used to connect an ODU to a standard antenna, or to a dual-polarized antenna for co-channel link operation.

ODUs are fixed for Tx High or Tx Low operation.

Where two ODUs are to be connected to a single antenna for hot-standby or frequency diversity configurations, a direct-mounting coupler is used. They are available for equal or unequal loss operation. Equal loss is nominally 3.0/3.0 dB.

Unequal is nominally 1.5/6.0 dB.





1 Outdoor Units

1.2 ODU300 Characteristics

4, 16, 32, 64, 128 QAMModulation support

L6, U6, 7, 8, 11, 13, 15, 18, 23, 26, 28, 38 GHz

Frequency Band options

General Specification

150 metersMSS to ODUMaximum IF 10.3 mm Cable length [NB]

126 MHzReceive

311 MHzTransmitIntermediate Frequency

IF Specifications

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





1 Outdoor Units

1.2 ODU300 Characteristics [cont.]

Remote mount via flex/elliptical waveguide

6-38 GHz, optional

Proprietary direct mount for antenna diameters 0.3 to 1.8m

Remote mount for antenna diameters>1.8m

6-38 GHz, standardPolarisation, field selectable Antenna Mounting

Standard EIA rectangular waveguide, refer to ODU System specifications

Vertical (standard) or Horizontal

6-38 GHzAntenna port Interface

BNCAGC monitor point

N-TypeIF cable connector

ODU Interfaces





2 ODU300 block diagram





2 ODU300 block diagram

2.1 ODU300 block diagram

To MSS

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





3 Outdoor Installations






3.1 Installing the ODU

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

Direct-Mounted ODUsRemote-Mounted ODUsGrounding the ODU






3.2 Direct-Mounted ODUs

The ODU is attached to its mounting collar using four mounting bolts, which have captive 19 mm (3/4”) nuts for fastening.The ODU mounts directly to its antenna mount, as shown in Figure.

Pressed-Cover ODU and Mounting Collar






3.3 Remote-Mounted ODUs (solution 1)

ODUs can be installed separately from its antenna, using a remote-mount to support the ODU, and a flexible-waveguide or coaxial cable to connect the ODU to its antenna:

a flexible waveguide is required.

The remote mount allows use of standard, single or dual polarization antennas.

The mount can also be used to remotely support a protected ODU pairing installed on a coupler. The coupler connects to the remote mount assembly in the same way as an ODU.

The remote mount clamps to a standard 112 mm (4”) pole-mount, and is common to all frequency bands. Figure shows an ODU installed on a remote mount.

Flexible waveguides are frequency band specific and are normally available in two lengths, 600 mm (2 ft) or 900 mm (3 ft). Both flange ends are identical, and are grooved for a half-thickness gasket, which is supplied with the waveguide, along with flange mounting bolts.






3.4 Remote-Mounted ODUs (solution 2)






3.4 Remote-Mounted ODUs (solution 2) [cont.]






3.5 Waveguide Flange Data

Flange thickness + Hole depth - 2mm

66HM3x0.544 x M3WR28PBR320UBR32028/32/38 GHz


66HM3x0.544 x M3WR42PBR220UBR22018/23/26 GHz


86HM4x0.744 x M4WR62PBR140UBR14015 GHz


86HM4x0.744 x M4WR75PBR120UBR12013 GHz


86HM4x0.788 x M4WR90PDR100UDR10011 GHz


86HM4x0.788 x M4WR112PDR84UDR847/8 GHz


106HM5x0.888 x M5WR137PDR70UDR706 GHz

Bolt Length RequiredHoleDepthmm

ThreadSpec

BoltType

BoltsReqd

SpringWashersReqd

Waveguide Type

WaveguideMating Flange

Radio FlangeFreq Band

Table lists the antenna port flange types, plus their mating flange options and fastening hardware forremote mount installations. UDR/PDR flanges are rectangular; UBR/PDR flanges are square.On the ODU, the two flange styles are:

UDR. 6-hole or 8-hole (6/8 bolt holes depending on frequency range/waveguide type), flush-face flange with threaded, blind holes.UBR. 4-hole flush-face flange with threaded, blind holes.

The corresponding mating flange styles are:PDR. 6-hole or 8-hole flange with gasket groove and clear holes.PBR. 4-hole flange with a gasket groove and clear holes.

All fastening hardware is metric.






3.6 Grounding the ODU

The one ground wire can be used to ground both the ODU and the suppressor only in case a pressed-cover ODU is installed with a suppressor support bracket.

For all other set-ups, one ground wire must be installed to ground the suppressor, and one to ground the ODU.

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






3.7 ODU external connectors

Vertical Polarization Horizontal Polarization

Waveguide feed headRSSI connector

IF cable connector

(to Indoor Unit)

IF cable connector (to Indoor Unit)

RSSI connector






3.7 ODU external connectors [cont.]

RSSI Monitoring PointThe ODU has a capped BNC female connector to access RSSI during antenna alignment. There is a linear relationship of voltage to RSSI, as shown in the table below; an RSSI of 0.25 Vdc is equivalent to -10 dBm RSSI, and each additional 0.25 Vdc RSSI increase thereafter corresponds to a 10 dBm decrease in RSSI. The lower the voltage the higher RSSI and better aligned the antenna is.The RSSI figures in dBm are identical to the RSL figures displayed in A9500 MPR Craft Terminal.

RSSI Table

-100-90-80-70-60-50-40-30-20-10RSSI (dBm)2.52.252.01.751.51.251.00.750.50.25BNC (Vdc)

MeasurementUnits






Which modulations are supported in the ODU?

Which is the maximum length of the IF cable?

Can the ODU be directly connected to the antenna?

When must be used the RSSI monitoring point?





End of ModuleODU HW Hardware Architecture





Module 1Operator interface

3JK Edition 1.00

Section 3NE operation




9500 MPR · 9500MPR R 1.2.1 Operation and MaintenenceNE operation · Operator interface3 · 1 · 2

Blank Page




Document History





Objectives

Objectives: to be able tounderstand all the menus available with the LCT.





Objectives [cont.]






Table of Contents


Blank Page 81 Network Element Overview 9

1.1 Main View 101.2 NE Configuration area 11

1.2.1 NE Information 121.2.2 NE Description 131.2.3 Command Buttons 14

1.3 Status & Alarms area 151.4 Supervision Function 161.5 Menu Bar 171.6 Suggested sequence for NETO interface and NE list 19

Blank Page 202 Main View 21

2.1 Main view 222.2 Main Tool Bar Area 252.3 Severity Alarm Panel 262.4 Domain Alarm Synthesis Panel 272.5 Management State Control Panel 282.6 Selection Criteria 292.7 Button Policy 30

3 Menu Configuration 313.1 Menu Configuration 323.2 Menu NE Time 333.3 Menu Network Configuration 34

3.3.1 Local Configuration 353.3.2 NTP Configuration 363.3.3 IP Static Routing Configuration 373.3.4 OSPF Area Configuration 393.3.5 Routing Information 41

3.4 Menu System Settings 423.5 Menu Cross Connections 43

3.5.1 Connectors 443.5.2 Graphical Area 463.5.3 Buttons 473.5.4 Segregated port view 483.5.5 How to segregate slots or ports 493.5.6 How to create a cross-connection 513.5.7 Creation Dialogs 543.5.8 Information Dialogs 553.5.9 Possible Cross-Connections 563.5.10 PDH – Radio 573.5.11 Radio - Radio 593.5.12 Radio - Ethernet 623.5.13 PDH - Ethernet 653.5.14 Cross-Connections with TDM2Eth Profile 673.5.15 How to modify a cross-connection 70

3.5.15.1 PDH-Radio 713.5.15.2 Radio-Radio 723.5.15.3 Radio-Ethernet 733.5.15.4 PDH-Ethernet 74

3.6 Menu VLAN Configuration 753.6.1 802.1D 763.6.2 802.1Q 77

3.6.2.1 VLAN 1 Management 783.6.2.2 VLAN Table Management 79







3.7 Menu Profile Management 813.7.1 User Profiles Management 823.7.2 User Management 833.7.3 How to Create a New User 843.7.4 How to Delete a User 863.7.5 Change the Password (by the Administrator) 873.7.6 Change Password (by the User) 88

4 Menu Diagnosis 894.1 Menu Diagnosis 904.2 Alarms 91

4.2.1 File Menu 974.2.2 Filters Menu 98

4.2.2.1 Add a Filter … 994.2.2.2 Delete Filters ... 1004.2.2.3 Save Filters As ... 1014.2.2.4 Load Filters From ... 102

4.2.3 Help Menu 1034.3 Log Browsing 104

4.3.1 Event Log Browser 1054.3.1.1 File Menu 1074.3.1.2 Help Menu 110

4.4 Remote Inventory 1114.5 Abnormal Condition List 1124.6 Summary Block Diagram View 113

4.6.1 Main Block diagram view 1144.6.2 PDH unit secondary view 1154.6.3 Radio unit secondary view 119

4.7 Current Configuration View 125Blank Page 126

5 Menu Supervision 1275.1 Menu Supervision 1285.2 Access State 129

5.2.1 Requested (Switching OS � CT access state) 1305.2.2 OS (Switching CT access state � OS) 1315.2.3 LAC Time Out Period 132

5.3 Restart NE 1335.4 SW Licence 134

6 Tab-panel Equipment 1356.1 Starting From Scratch 1366.2 Tab panels in the Resource Detail Area 137

6.2.1 Alarms tab-panel 1386.2.2 Settings tab-panel 139

6.2.2.1 Equipment Type 1406.2.2.2 Protection Type 141

6.2.3 Remote Inventory tab-panel 143Blank Page 144

7 Tab-panel Protection Schemes 1457.1 General 1467.2 EPS Management 148

7.2.1 Protection Schema Parameters 1497.2.2 Commands 150

7.3 RPS Management 1517.3.1 Protection Schema Parameters 1527.3.2 Commands 153

7.4 HSB Protection Management 1547.4.1 Protection Schema Parameters 1557.4.2 Commands 156







8 Tab-panel Synchronization 1578.1 Menu Synchronization 1588.2 How to synchronize 159

Blank Page 1629 Tab-panel Connections 163

9.1 Menu Connections 16410 PDH view for PDH domain 165

10.1 PDH Unit configuration 16610.1.1 Alarms tab-panel 16810.1.2 Settings tab-panel 169

Blank Page 17011 Radio view for Radio domain 171

11.1 Radio domain menu 17211.2 Settings 173

11.2.1 Direction area 17411.2.1.1 Mode 17511.2.1.2 Link Identifier Configuration 18411.2.1.3 PPP RF 185

11.2.2 Channel area 18611.2.2.1 Frequency 18711.2.2.2 ATPC 18811.2.2.3 Manual Transmit Power Control 18911.2.2.4 Tx Mute 19211.2.2.5 Alarm Profile 193

11.3 Measurement 19411.3.1 How to read a Power Measurement file 197

11.4 Loopback 19811.4.1 How to activate a loopback 19911.4.2 How to remove a loopback 200

12 Core-E view for Core-E and Ethernet domain 20112.1 Core-E domain 202

12.1.1 Ethernet Physical Interface 20312.1.1.1 Alarm tab-panel 20512.1.1.2 Settings tab-panel (for Ethernet Port#1 to Port#4) 20612.1.1.3 Settings tab-panel (for Ethernet Port#5) 207

12.1.2 TMN Interface 20812.1.2.1 TMN Ethernet port 20912.1.2.2 Port #4 TMN Ethernet 210

Answer the Questions 211End of Module 212





Blank Page






1 Network Element Overview






1.1 Main View

When NETO starts, the main view screen is shown below.

This screen has two specific areas:NE Configuration area: displays NE general information (left side);Status & Alarms area: reports supervision status and alarms (right side).Discovered NEs: in the lower part of the screen is shown the list of the discovered NEs. With a double click on a row the IP address of the NE in the row automatically is written in the NE Info field.

“Show” and “Alarm Monitor” buttons are enabled when a NE is supervised only. Supervision starts as soon as the operator writes an IP address in the specific field and press the “OK” button.

The Network Element Overview (NETO) is the starting point of the CT application.

NETO functions require to know the NE identity by means of the related IP Address.

Only one NE can be managed in a NETO session.

NETO Main view can also be minimized by using the shrink glass ( ) button in the Menu Bar.

The magnifying glass ( ) button allows to show the normal NETO main view.

The alarm severity icon appears in operating system “tray bar”, close to system clock and other system software icons.

This icon also has a specific tooltip, visible when mouse cursor is moved over it, that will show: name of application, NE IP address, and highest severity alarms number. Tray-bar icon is not interactive and does not present any menu or executable command if clicked either with left or right mouse button.






1.2 NE Configuration area

The NE configuration area is divided in three sections:

1) NE Info section, containing information related to NE addressing;

2) NE Description section, with information about NE characteristics;

3) Command Buttons section, providing buttons to manage NETO functions.






1.2.1 NE Information

This area is related to the wanted NE identification.

“IP Address” field displays the actual NE IP address used by NETO functions.

“OK” button will start supervision on specified NE, if reachable. Keyboard shortcut “Alt + o” behaves as clicking on “OK” button with mouse.

Whether the IP address is correctly written, other than clicking on “OK” button, supervision process will start on specified NE by pressing “enter” (carriage return) key on keyboard.






1.2.2 NE Description

This area contains some parameters displaying general information about the supervised NE.

Parameters can be read and modified (and applied to NE using the“Apply” button).

Please note that changing these labels values will also automatically update NETO window title content: window title will always contain “Site Name” of supervised NE. Keyboard shortcut “Alt + a” behaves the same as clicking on “Apply” button with mouse.






1.2.3 Command Buttons

Command buttons available through NETO are:

“Show” button will start WebEML (JUSM/CT) application on a supervised NE.“Alarm Monitor” button starts AM application. Both buttons will be enabled when NE is supervised only. “Exit” button will close NETO, stopping a possibly running supervisionand closing all related applications.

Keyboard shortcut “Alt + S” behaves as clicking on “Show” button with mouse. Keyboard shortcut “Alt + m”behaves as clicking on “Alarm Monitor” button with mouse. Key-board shortcut “Alt + E” behaves as clicking on “Exit” button with mouse.






1.3 Status & Alarms area

Information on supervision status and active alarms are shown in this area.

Round-shaped icons change their colours according to current NETO functions and situation. With respect to “Supervision” status:

green colour means that supervision function is ongoing,

red colour means that NE link does not work,

gray icons mean that supervision is not active (to be started).

Alarm synthesis contains the list of the alarms listed by severity: whether an icon is not gray, means that such kind of severity contains one alarm at least. “Alarm Monitor” button shown in Figure opens the Alarm Monitor application external tool.






1.4 Supervision Function

The supervision function allows operator registering a new manager inside NE MIB and performing cyclic (periodic) monitoring on connection. To start supervision, the operator must specify NE IP address in the “IP Address” field and then simply press “OK” button.If supervision succeeds, screen is updated with information retrieved from NE and supervision icon changes its colour from gray to green stating NE is correctly supervised. When a supervision error, a link down or other problems arise during supervision, icon will become red. Alarm Synthesis area will be updated as well. Clicking on “Show” button, NETO will open the WebEML(JUSM/CT) for MPR equipment. To close an ongoing supervision, simply click on “Exit” button (this will also close NETO) or change NE IP address and click “OK” button to start supervision procedure on a different NE (this will stop previoussupervision).






1.5 Menu Bar

(New)(Open)(Magnifying glass)

NETO Main view can also be minimized by using the shrink glass ( ) button.Using both (New) and (Open) icons, the operator will be able to open NEs table modal window (see following Figure). “Open” icon allows opening a previously saved file containing a list of NEs. “New” icon allows creating a new list, specifying the file name containing its data, only when those data will be saved.

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






1.5 Menu Bar [cont.]

NETO List Management

“Get Current” button is used to read information from main NETO view. This operation will always add a new line in NE list table with all information related to currently supervised NE. This happens even though a NE with corresponding IP address is still present in the list;

“New” button, adding a new NE from scratch. This allows the operator to fill the “IP Address” field only with its needed NE.

“Remove” button, removing a selected NE;

“Set Current” button, filling main NETO view IP address with datum from selected NE. The operator must previously select a valid line in NEs table and then click on “Set Current” button so filling NETO main window data. This operation will automatically close the NE list window but does not start supervision on set NE;

“Save” button, saving table list in a specified file.

To close this window click on “Close” button.

All data are saved in a custom XML format called “NETO” and this structured file will contain all data shown in Figure related to all NEs added to the list.

The operator can have its own NEs lists repository, containing all .NETO files that it produced with NEsinformation inside.






1.6 Suggested sequence for NETO interface and NE list

1. Fill NETO main view “IP Address” field with NE IP address;2. Start supervision by clicking “Ok” button;3. Open the NEs table (any method, through “New” or “Open” button);4. Click on “Get Current”;5. “Save” the list and “Close” the list window.

This operation will produce a clean and up-to-date NEs table list. The NE table lists are not updated, if the operator will modify, NE site name site location or even IP address. Such data are used for references purposes, but the operator must take care to keep them updated.





Blank Page






2 Main View





2 Main View

2.1 Main view

Two Main views are possible according to the MSS version:

MSS-8

MSS-4





MSS-8

2 Main View

2.1 Main view [cont.]

Domain AlarmSynthesis Panel

The Main View Area manages all domains from which the operator can start. It is organized with tab panels, e.g. many windows placed one upon another. Each window is selectable (placing it on top of the others) with a tab shown on the top.Tab-panelsEach tab-panel represents a set of functions. The following tab-panels are present:

Equipment (to manage the equipment configuration)Protection Schemes (to manage the protection schemes in 1+1 configuration only)Synchronization (to manage the synchronization)Connections (to manage the cross-connections)

Each tab-panel consists of three areas:Resource-Tree Area: displays all the available resources of the NE.Resource-List Area: may be represented by: Tabular View or Graphical View.

Tabular View: displays a tabular representation of the selected resource. As default, no tabular element is shown.Graphical View: displays a graphical representation of the selected resource. As default, no tabular element is shown.

Resource-Detail Area: displays detailed information of a selected item in the Resource List area. As a default, no entry view is displayed as a consequence of the default behavior of the Resource List area.

Figure (Main view) is the entry point of the application and provides basic diagnostic and configuration functions. Following multiple main views are available:

Equipment view, for Equipment configuration;Radio view, for Radio domain (double click on a Radio unit);PDH view, for PDH domain (double click on a PDH unit);Core-E view, for Core-E and Ethernet domain (double click on a Core-E unit).

Navigation from main view to multiple main views (related to the equipment components) can be done by simply double-clicking on the component graphical representation. Such operation will open a new window containing selected secondary view. Starting from mainview, the operator will also see all slots and ODUs layout. Each slot contains schematics of available board (if present) together with status and other details. Slots schematics will in fact contain usual alarms information with a clarifying coloured icon that reports the same icon visible in tree view. Other icons are:

On the right of the unit front panel, a new icon could be a check mark ( ) or a switch symbol ( ).: it means the slot is “active”;: it means the slot is in “stand-by” mode.

As shown in Figure, an X-shaped icon ( ) will be added on the left to slots when some cross connections are related to it.





2 Main View

2.1 Main view [cont.]

MSS-4Domain AlarmSynthesis Panel

The Main View Area manages all domains from which the operator can start. It is organized with tab panels, e.g. many windows placed one upon another. Each window is selectable (placing it on top of the others) with a tab shown on the top.Tab-panelsEach tab-panel represents a set of functions. The following tab-panels are present:

Equipment (to manage the equipment configuration)Protection Schemes (to manage the protection schemes in 1+1 configuration only)Synchronization (to manage the synchronization)Connections (to manage the cross-connections)

Each tab-panel consists of three areas:Resource-Tree Area: displays all the available resources of the NE.Resource-List Area: may be represented by: Tabular View or Graphical View.

Tabular View: displays a tabular representation of the selected resource. As default, no tabular element is shown.Graphical View: displays a graphical representation of the selected resource. As default, no tabular element is shown.

Resource-Detail Area: displays detailed information of a selected item in the Resource List area. As a default, no entry view is displayed as a consequence of the default behavior of the Resource List area.

Figure (Main view) is the entry point of the application and provides basic diagnostic and configuration functions. Following multiple main views are available:

Equipment view, for Equipment configuration;Radio view, for Radio domain (double click on a Radio unit);PDH view, for PDH domain (double click on a PDH unit);Core-E view, for Core-E and Ethernet domain (double click on a Core-E unit).

Navigation from main view to multiple main views (related to the equipment components) can be done by simply double-clicking on the component graphical representation. Such operation will open a new window containing selected secondary view. Starting from mainview, the operator will also see all slots and ODUs layout. Each slot contains schematics of available board (if present) together with status and other details. Slots schematics will in fact contain usual alarms information with a clarifying coloured icon that reports the same icon visible in tree view. Other icons are:

On the right of the unit front panel, a new icon could be a check mark ( ) or a switch symbol ( ).: it means the slot is “active”;: it means the slot is in “stand-by” mode.

As shown in Figure, an X-shaped icon ( ) will be added on the left to slots when some cross connections are related to it.





2 Main View

2.2 Main Tool Bar Area

This area contains a selection of handy quick-access buttons for common features.

Left arrow to previous screen

Second button: not operative

Right arrow to next screen

Block Diagram View: opens the Summary Diagram view

Current Configuration View: opens the Current Configuration view

Cross-Connections: opens the Cross-Connections menu

Segregated Ports: opens the Segregated Ports menu

VLAN management: opens the VLAN Management menu

Performance Monitoring Tool: opens the Performance Monitoring Toolmenu





2 Main View

2.3 Severity Alarm Panel

The CT provides an alarm functionality that informs the operator on the severity of the different alarms in the NE as well as on the number of current alarms. There are five different alarm severity levels. In the CT these different levels are associated with colors:

Red: Critical alarm (CRI). Orange: Major alarm (MAJ). Yellow: Minor alarm (MIN). Cyan: Warning alarm (WNG). Blue: Indeterminate (IND).

Each alarm severity is represented by an alarm icon situated in the top left hand corner of the view. These alarm icons are constantly represented on the different Equipment views (NE view, Board view or Port view) so that the operator is always aware of the alarms occurring in the system.Furthermore the shape of the alarm icons in the alarm panel gives an indication of the occurrence of alarms. The figures below describe the different examples.An alarm icon with a circle inside it (and a number at the bottom of the icon) indicates that alarms of the number and the type defined by the icon are occurring.An alarm icon with a rectangle inside it indicates that no alarms of the type defined by the icon are occurring.An alarm icon grayed out indicates that spontaneous incoming alarm notification have been inhibited.

N.B. The meaning of the icons in the Severity alarm synthesis is:

1) CRI - Critical alarm

Synthesis of alarms that needs immediate troubleshooting (typical: NE isolation).

2) MAJ - Major (Urgent) alarm

Synthesis of alarms that needs immediate troubleshooting.

3) MIN - Minor (Not Urgent) alarmSynthesis of alarms for which a deferred intervent can be decided.

4) WNG - Warning alarmSynthesis of alarms due to failure of other NE in the network. NB1.

5) IND - Indeterminate alarmSynthesis of alarms not associated with the previous severities. Not operative.





2 Main View

2.4 Domain Alarm Synthesis Panel

This area contains the bitmaps (more than one) representing the alarms per domain. Each bitmap indicates the number of alarm occurrences for each domain. The meaning of the icons in the Domain alarm synthesis area is:1) EXT - External Point (Housekeeping alarm)

Not implemented in the current release.2) EQP – Equipment alarm

Synthesis of alarms of the Equipment domain.3) TRS – Transmission alarm

Synthesis of alarms of the Transmission domain.





2 Main View

2.5 Management State Control Panel

The different management states concerning the NE are also represented via icons located in the top right corner of the equipment views. These icons are (from up to down):

1) Icon with a key symbol: Local Access state: indicates whether the NE is managed by a craft terminal or by the OS 2) COM icon: Operational state: indicates whether or not the communication with the OS is established. 3) SUP icon: Supervision state: indicates whether or not the NE is under OS supervision. 4) OS icon: OS isolation.5) NTP Server Status icon.6) AC icon: abnormal condition state: indicates whether some abnormalconditions have been recognized. The operator can visualize them with the Diagnosis-> Abnormal condition list menu.

N.B.: As for the alarm icons, a rectangular management state icon represents the stable state while a circular icon shape represents an unstable management state.The meaning of the icons in the Management State Control Panel is:

1) Local Access StateGREEN LED: Indicates that the Craft Terminal has the OS permission to manage the NE (granted).CYAN LED: Indicates that the Craft Terminal has not the OS permission to manage the NE (denied).

2) COM – NE rechable/unreachableGREEN LED: Identifies the “Enable” operational state of the connection between NE and Craft Terminal (link down).RED LED: Identifies the “Disable” operational state of the connection between NE and Craft Terminal (link down).

3) SUP – Supervision stateGREEN LED: NE is under supervisionBROWN LED: NE is not under supervisionUsed in the OS.

4) OS – OS isolation5) NTP – Network Timing Protocol

BROWN LED: Protocol disabledGREEN LED: Protocol enabled, but the two servers are unreachable.CYAN LED: Protocol enabled and one of the two servers is reachable.

6) AC – Abnormal ConditionGREEN LED: Normal operating condition.CYAN LED: Detection of an ABNORMAL operative condition. Type: switch forcing.





2 Main View

2.6 Selection Criteria

Each tree node consists of possibly three symbols and a label. The first optional symbol indicates structure state: if symbol is , three can be expanded showing its contained lower levels. Tree structure can be collapsed if symbol is . With no symbol, node represents a tree leaf. Second symbol is the graphical representation of resource itself. Third symbol is alarm status of component. The operator can select resource by clicking with mouse to perform the action dependent on click type. Resource Detail Area related to the selected item is displayed.Each resource listed above may be selected by using the mouse by a:

Single left click:By a single left click the resource is highlighted. This selection causes the activation of the resource list area, e.g., every time the operator selects a resource in the resource tree area the corresponding data are displayed in the “Resource list area”.

Double left click:Double click operation on resource tree items allows the operator expanding tree structure, so activating the display/update of resource list area, that will display same information as for single click operation. As soon as a node is expanded, another double click on such node would collapse tree structure to its closed view.





2 Main View

2.7 Button Policy

The possible buttons for selection are the following:

Applythis button activates the “modify”, but it does not close the window.

Cancelthis button closes the window without modifying the parameters displayed in the window.

OKthis button activates the modify and closes the window

Closethis button closes the window

Helpthis button provides the help management for the functions of the supporting window.





3 Menu Configuration






3.1 Menu Configuration

Menu Configuration is divided in:

NE Time

Network Configuration

Alarm Severities (not implemented in the current release)

System Settings

Cross Connections

VLAN Configuration

Profile Management






3.2 Menu NE Time

Note: The NTP Status field is not implemented.

The NE local time can be displayed and/or re-aligned to the OS time basis.

From the Configuration pull down menu, select the NE Time option.

The dialogue box opens, from which you can set the local NE time.

The NE Time dialogue box displays the current NE time and the current OS time.

To re-align the NE time to the OS time, click on the Set NE Time With OS Time check box and click the Apply pushbutton to validate.

The Refresh pushbutton causes the refresh of the screen.

The NTP Status field is a read-only field, which shows the configuration regarding the NTP (Network Time Protocol), if the protocol has been enabled and configured in Menu Configuration → Network Configuration → NTP Configuration.

The NTP Status field shows:

status of NTP (enabled/disabled);

IP address of the Main Server, which distributes the time to all the NEs in the network;

IP address of the Spare Server (if any), which replaces the Main Server in case of failure.






3.3 Menu Network Configuration

The Network Configuration allows to perform the following operations:Local Configuration:

defines the local virtual NE addressNTP Configuration (not implemented):Ethernet Configuration (not implemented):IP Configuration which comprises:

IP static routing configuration: defines the Host/Network destination address for IP static routingOSPF Area configuration: defines the Open Shortest Path First addressIP Point-To-Point Configuration: defines the IP address of the interfaces which use the PPP protocol (not implemented)

Routing information: shows a summary of the information relevant to the routing which has been configured.






3.3.1 Local Configuration

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

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

Close button closes the dialogue.

Help button provides some useful information on the dialogue.






3.3.2 NTP Configuration

This menu allows to enable the NTP (Network Time Protocol).

Put a check mark in the NTP protocol field to enable the protocol and write in the Main Server addressfield the IP address of the server, which is in charge to distribute the time to all the NEs in the network. In the Spare Server address field write the IP address of the Spare Server, if any.

The Server reachability field is a read-only field, which shows the reachability of the NTP servers. The following information can appear:

"Main server reachable"

"Spare server reachable"

"None servers reachable"

"Both servers reachable"

Click on Refresh to update the screen.

Click on Apply to send to the NE the NTP Configuration.






3.3.3 IP Static Routing Configuration

By selecting IP static routing configuration a dialog-box opens, which allows to configure the parameters for IP Static Routing Configuration.The following fields and data are present:

IP Address: allows to define the IP address necessary to reach a specific HostIP Mask: allows to define the IP Mask to reach a networkDefault Gateway IP Address: allows to define the address of the next hop gatewayInterface type: allows to use point to point interfaces made available by the NE.

By pressing Create pushbutton another screen opens.In the Host or Network Address Choice field select:

Host to address to a single IP address;Network to address to a range of IP addresses.

In the Default Gateway or Point to Point I/F Choice select:Default Gateway IP Address for the Ethernet interface;Point to Point Interface Index for the NMS channels (NMS-RF)

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

The default software uses first the static routes and then the dynamic routes. An open static route is always considered as a preferential path.

If in the screen the Default Gateway IP Address check box has been selected, write in the Default Gateway IP Address field below the relevant IP address.

If in screen the Point To Point Interface Index check box has been selected another screen opens.

Apply button is used to perform a configuration change of the data contained in the complete table and close the view; the view is visible until the end of the operations and a wait cursor is displayed.

New button is used to insert a new page.

Delete button is used to delete the selected page.

Close button closes the dialogue without changing of the data.






3.3.3 IP Static Routing Configuration [cont.]






3.3.4 OSPF Area Configuration

By selecting OSPF Area Configuration a dialog-box opens, which allows to configure the parameters for OSPF (Open Shortest Path First) Area Table Configuration.The following fields and data are present:

OSPF Area IP AddressOSPF Area Range MaskOSPF Area Stub

The fields give a synthetical information that includes all the addresses (specific to a NE and to a Network) in an Area.

Apply button is used to perform a configuration change of the data contained in the complete RAP table and close the view; the view is visible until the end of the operations and a wait cursor is displayed.

New button is used to insert a new page.

Delete button is used to delete the selected page.

Close button closes the dialogue without changing of the data.

WARNING: When the area is a Stub area, all the interfaces (NMS and Ethernet) must be defined “Stub".

By pressing Create pushbutton a new screen opens.

N.B. 3 areas max. can be created.

In this new screen write the IP address, the IP mask and select the flag (True/False).






3.3.4 OSPF Area Configuration [cont.]






3.3.5 Routing Information

By selecting Routing Information a dialog-box opens: this screen is a read-only screen and displays the routing parameters currently active on the NE.

The pushbutton Refresh allows to refresh the information shown in the screen.

The Close button closes the dialogue without changing of the data.






3.4 Menu System Settings

This menu allows the system configuration, providing the setting of some parameters for the NE setup. The NE configuration tab-panel has 6 fields:

Tributary Port ConfigurationQuality Of ServiceDHCPAdmission Control for Adaptive ModulationEvent and Alarm LogNE MAC Address

1) Tributary Port ConfigurationThis field allows to set the suitable impedance of the E1 stream (Unbalanced 75 ohms/Balanced 120 ohm). To activate the new impedance, click on Apply.

2) Quality Of ServiceThis field allows to set the suitable Quality Of Service (Disabled/DiffServ/802.1p). To activate the new value, click on Apply.The Ethernet switch provides a Quality of Service mechanism to control all streams. If the QoS is disabled, all traffic inside the switch has the same priority, this means that for each switch port there is only one queue (FIFO) therefore the first packet that arrives is the first that will be transmitted.The following values are available:

IEEE std 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag. If the tag is present the correspondent priority is assigned to the packet;DiffServ: each packet is classified based on DSCP field in the IP header to assign the priority;

3) DHCPThe DHCP server configures automatically IP address, IP mask and default gateway of the PC Ethernet interface used to reach the NE. The PC must be configured to get automatically an IP address.The DHCP server uses an address pool of only one IP address, defined according to the NE Ethernet port IP address:

NE Ethernet port IP address plus one, if this address is not a direct broadcast address, otherwise NE Ethernet port IP address minus one.

The IP mask is set to the mask of the NE local Ethernet port and the default gateway is set to the NE IP address.The lease time is fixed to 5 minutes.To activate the DHCP server, select Enabled and click on Apply.

4) Admission Control for Adaptive ModulationThe Admission Control for TDM flows (cross-connected to radio direction working in Adaptive Mod-ulation) can be enabled or disabled. Default: “Enabled”.When the Admission Control is "Enabled", the check is performed taking into account the capacity of the 4 QAM modulation scheme for the relevant Channel Spacing. When the Admission Control is "Disabled", the check is performed taking into account the capacity of the highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-16-64 QAM range or 16 QAM for 4-16 QAM range).Warning: The disabling of the Admission Control can be done in 1+0 configuration only.

5) Event and Alarm LogAs default the Logging is enabled. If set to "Disabled" the events are not sent to the Event Log Browser application.

6) NE MAC AddressThis field is a read-only field, which shows the MAC address of the NE. This MAC address must be used in the cross-connection with TDM2Eth profile.






3.5 Menu Cross Connections

Note: Ethernet port#5 will appear only if the optional optical SFP plug-in has been installed and enabled in the Core-E unit. To enable the SFP plug-in go to the Setting tab-panel of the Core-E unit in the Equipment tab-panel.

The Main view is a graphical representation of Cross-connectable slots. Slots and Ethernet ports (represented by “connectors”) are arranged according to the equipment configuration:

There are a maximum of 5 Ethernet ports placed on the bottom, ordered from 1 to 5 from left to right. Port 4 is visible only when set to “transport” mode. If Ethernet port 4 is set to “TMN”, icon 4 is not shown. Port 5 is visible if in the Core-E unit has been installed and enabled the SFP optical plug-in.

There are a maximum of 6 (PDH/Radio) slots (placed as in the MSS sub-rack).

When two units are protected, the 2 protected slots are linked by a dashed line, (e.g.: Slot#5 RADIO is protected with Slot#6 RADIO).






3.5.1 Connectors

The connectors representing the MSS slots are start- and end-point for actual cross-connections. By using the mouse drag-and-drop operations the operator can create cross-connections through these points. These connectors have specific icons:

identifies Ethernet RJ-45 connector (Ethernet ports);identifies PDH slots;identifies Radio slots.

The connectors have different colours depending on the associated slot’s state:

White: a connector, in a cross-connection, which is able to accept a cross-connection and has no active cross-connection yet;Green: a connector able to accept a cross-connection and already has one active cross-connection at least;Blue: a connector that is not able to accept a cross-connection.






3.5.1 Connectors [cont.]

After a cross-connection creation between the points, their state will change and a line will be drawn between the two cross-connected points.






3.5.2 Graphical Area

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

Some steps would differ depending on cross-connection types.






3.5.3 Buttons

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






3.5.4 Segregated port view

From the Cross Connection view by pressing Alt+W the Segregated Port view opens.

In the default configuration all the slots and Ethernet ports in Core unit are cross-connectedable each other (all the slots/ports are not segregated).

To go back to the Cross Connection View press Alt+W.






3.5.5 How to segregate slots or ports

Double click on a slot icon or an Ethernet port icon and select the slots/ports that can be connected (this means that the not selected slots/ports cannot be connected; they are segregated).Example: with a double click on the icon of Slot#7 RADIO figure opens.

To segregate Slot#7 RADIO from Ethernet ports#2, #3, #4, #5 in the Core unit, click on the relevant square to remove the check mark.






3.5.5 How to segregate slots or ports [cont.]

By clicking OK the Segregated Port view opens, which now shows (with dashed lines) the segregated ports.

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






3.5.6 How to create a cross-connection

A cross-connection between two points is performed by:Moving the mouse pointer on the source slot;Press the left button and, while keeping button pressed, move mouse pointer onto destination slot;Release the left button.






3.5.6 How to create a cross-connection [cont.]

Cross-connections Example

If the action involves two cross-connectable slots, a dialog will appear allowing the operator to setup a cross-connection. Looking at figure, it is possible to see different aspects of configuration created by the operator:

Slot#8 PDH is cross-connected to Slot#7 radio;

Slot#4 PDH is cross-connected to Slot#7 radio;

Slot#3 PDH is cross-connected to Ethernet Port#1;

Slot#5 RADIO (and Slot#6 RADIO) are cross-connected to Ethernet Port#2;

Slot#8 PDH is cross-connected to Ethernet Port#4;

Slot#4 PDH (blue) could not accept more cross-connections;

Slot#3 PDH (green) could accept more cross-connections;

Radio slots#5 and #6 (green) could accept more cross-connections.






3.5.6 How to create a cross-connection [cont.]

Legenda

PDH-Radio connectionPDH-Eth connectionRadio-Eth line

Actual colored view example

Each connection line is coloured according to slots types it connects (as shown in figure):

PDH-Radio connection: black line;

PDH-Eth connection: blue line;

Radio-Radio connection: red line;

Radio-Eth line: green line.

These colours will be applied to the graphical area, when the operator releases the mouse button above cross-connection destination slot. All the lines appears as solid.






3.5.7 Creation Dialogs

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






3.5.8 Information Dialogs

By using the right-click button, the operator can gain information about the graphical representation of the cross-connections. This information can be obtained on both connectors and connection lines. The operator can perform different actions in the area, depending on target and mouse-click type:

Connector, right click: a dialog with information about all selected tributaries for that connector will appear.Line, right click: a dialog with information about selected tributaries for that line will appear.






3.5.9 Possible Cross-Connections

The Cross-connections to be implemented are: PDH-RadioRadio-RadioRadio-EthPDH-Eth

After a cross-connection has been created, two cross-connected slots are visually linked by a line: a line in the context of this application represents a bundle of flows, which share same source and destination entity.






3.5.10 PDH – Radio

By dragging a connection between a PDH slot and a radio slot, the operator will see the configuration dialog in the Figure.

PDH-Radio configuration dialog

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






3.5.10 PDH – Radio [cont.]

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

Completed PDH-radio cross-connection






3.5.11 Radio - Radio

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

Radio-Radio configuration dialog






3.5.11 Radio - Radio [cont.]

Configuration parameters will introduce Flow ID number, as coming from remote radio signal, and a parameter related to profile and TDM Clock Source. The operator has to fill in data to complete the cross-connection configuration. The operator can use ranges and values.To create in one shot several cross-connections the operator can use in the Flow Id field the notation [n-m] to create all Flow IDs from n to m, both included. If the operator wants to specify different Flow Ids grouping them without using ranges, commas can used to separate values.For example:

by entering in the FlowId field 10-15 in one shot will be created all the cross connections from FlowId 10 to FlowId 15 (10 and 15 included); by entering in the FlowId field 10, 200, 250 in one shot will be created the cross connections with FlowId 10, FlowId 200 and FlowId 250.

It is not possible to merge the two solutions (ranges and values) by writing [n-m],[a-b], ... and so on. Based on used input style (ranges or values), the operator will see two different confirmation dialogs.






3.5.11 Radio - Radio [cont.]

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

Completed Radio-Radio cross-connection






3.5.12 Radio - Ethernet

By dragging a connection between a Radio slot and an Ethernet port, the operator will see the configuration dialog in Figure.

Radio-Ethernet configuration dialog (ranges)






3.5.12 Radio - Ethernet [cont.]

By using [n-m] the operator will specify adding all Flow IDs from n to m, both included. If the operator wants to specify different Flow Ids grouping them without using ranges, it can use commas to separate values as shown in figure.

Radio-Ethernet configuration dialog (values)

It is not possible to merge the two solutions (ranges and values) by writing [n-m],[a-b], … and so on. Based on used input style (ranges or values), the operator will see two different confirmation dialogs.

Once correctly completed the cross-connection configuration and clicked on “OK” button, the operator will be able to see a green line describing the Radio-Ethernet cross-connection defined.






3.5.12 Radio - Ethernet [cont.]

Completed Radio-Ethernet cross-connection






3.5.13 PDH - Ethernet

By dragging a connection between a PDH slot and an Ethernet port, the operator can see the configuration dialog in Figure.

PDH-Ethernet configuration dialog

Configuration parameters will introduce Flow ID number, as associated in PDH slot, and all parameters related to such Flow ID. The operator has to put the correct MAC address to complete the cross-connection configuration.






3.5.13 PDH - Ethernet [cont.]

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

Completed PDH-Ethernet cross-connection






3.5.14 Cross-Connections with TDM2Eth Profile

No protection

1+1 radio protection between NE B and C

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






3.5.14 Cross-Connections with TDM2Eth Profile [cont.]

1+1 EPS protection in NE A






3.5.14 Cross-Connections with TDM2Eth Profile [cont.]

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

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






3.5.15 How to modify a cross-connection

An existing cross-connection can be modified by double-clicking with the left mouse button on its symbolic line. Now from the screen you have to delete the cross-connections by removing the check mark from the relevant Flow Id box and createagain a new cross-connections.






3.5.15.1 PDH-Radio

In figure the operator is modifying a previously created cross-connection (in this case Slot#7 PDH and Slot#5 radio): this action brings up a dialog almost like the creation one, but with some differences in allowed actions:

Previously assigned tributaries (703 in the example) are active and selected;

Tributaries assigned to another cross-connection (706, 709 and others) are not active and not selected.






3.5.15.2 Radio-Radio

The operator can click on a specific (red) line in order to modify connection parameters. With a double click with the mouse on the connection line, the dialog window shown in Figure will appear.

Remove the check mark and create again a cross-connection.






3.5.15.3 Radio-Ethernet

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







3.5.15.4 PDH-Ethernet

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







3.6 Menu VLAN Configuration

Two different ways to manage the Ethernet traffic are allowed:802.1D (MAC Address Bridge)802.1Q (Virtual Bridge)






3.6.1 802.1D

When the NE is configured in this mode (default configuration), the Ethernet traffic is switched according to the destination MAC address without looking the VLAN.

The packets from the user Ethernet ports having the VLAN ID out the allowed range (0 and 2-4080) are dropped. The packets having a VLAN ID already used for a TDM flow are accepted.






3.6.2 802.1Q

When the NE is configured in this mode, the management of Ethernet traffic looking the VLAN is enabled.

In this modality, one VLAN will be assigned to all Ethernet frames inside the MPR network.





3.6.2 802.1Q

3.6.2.1 VLAN 1 Management

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

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

Edit: to change the parameters of a VLAN (VLAN name, VLAN member ports, VLAN untagged ports in egress).

Delete: to delete a VLAN-ID. It is possible to remove a VLAN-ID from the VLAN-ID table even if this VLAN-ID has been already configured on one or more user ports as Port VLAN to be added in ingress to untagged frames. As consequence, the VLAN-ID=1 and PRI=0 are added to the untagged frames received on this port. Before applying this deletion, a confirmation of the operation is shown to the operator.

Export: to export the VLAN configuration in a file with extension CSV. The file can be stored in the PC to be read later.

Filter: by inserting a name in the "Filter by Name" box and by clicking on Filter will be displayed in the table only the VLAN, which name corresponds (totally or partially) to the name written in the "Filter by Name" box.

Clear Filter: by clicking this button all the VLAN created in VLAN table will again appear.

Refresh: the VLAN table is updated.





3.6.2 802.1Q

3.6.2.2 VLAN Table Management

To create a VLAN follow the following instructions.

1) VLAN ID field: Enter the VLAN ID (the configurable values must be in the range 2 - 4080)

N.B.: The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) cannot be used.

2) VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.

N.B.: There is no check on unambiguity name.

3) VLAN Ports field: Select the ports members of this VLAN by putting a check mark on the relevant check box. All the user Ethernet ports and all the Radio directions can be considered. Both enabled and disabled user Ethernet ports (radio ports when declared are implicitly enabled) can be member of a VLAN. This means that a disabled port can be configured as a member of a VLAN and a port already member of a VLAN can be disabled continuing to be a member of the same VLAN.

4) Untagged Ports field: Select, among the ports belonging to this VLAN (members), the untagged ports (in egress the VLAN will be removed from the frames). Only the user Ethernet ports, enabled and disabled, are manageable. The VLAN cannot be removed from the radio ports (with the exception of the VLAN 1).

N.B.: The VLAN-ID values allowed are in the range 2 - 4080. By default, for the VLAN IDs defined, all the ports are members and the Untag flag is set to “False”, which means all the frames are transmitted with Tag.

N.B.: Tagged frames

If one tagged packet with VLAN-ID X is received on a port which is not member of the VLAN-ID X, the packet is dropped.





3.6.2 802.1Q

3.6.2.2 VLAN Table Management [cont.]

In the following figure, as example, three VLANs have been created (VLAN 2, 3 and 4).

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






3.7 Menu Profile Management

After the Start Supervision, each time the operator performs the ShowEquipment action, the following Dialog screen is displayed after the window with JUSM start-up message and before the window with loading bar indicating JUSM start-up progress.

Login window

The operator has to insert the user name and related password: by clicking on the Apply button, the parameters are sent to NE.

The default Operator Name is “initial”.

The default Password is “adminadmin”.

According to the operator authentication (correct couple username/password) managed by the NE, the operator will be authorized or not to continue. If the login parameters are not correct, an error message will be displayed, while the Login window is still open for a new attempt. After 3 consecutive failed attempts the login procedure is closed and JUSM does not start.

On the contrary if the user name and password are correct, JUSM will be started and the operator will be allowed to perform the actions according to the right related to his profile.

WARNING: The NE rejects usernames and passwords that do not meet the following rules:

Password length: the length must be not less than eight (8) characters under any circumstances. Moreover the password length must be not longer than 20 characters.

Password composition: the password can include full ASCII characters set (UPPER/lower case, numeric and special characters).

Username length: the length must be not longer than 20 characters.

By clicking on the Cancel button, the login procedure is stopped and the JUSM does not start.






3.7.1 User Profiles Management

If the operator right allows the profiles management, the operator can perform some actions on the profiles.Under Configuration menu, the Profiles Management menu displays two items:

Users ManagementChange Password

These items will be enabled according to the right of user profile recognised at login.






3.7.2 User Management

By clicking on Users Management the window displayed in the Figure appears.The operator can perform the following actions:

Create a new User by clicking on the Create button. After the selection of a user in the table, it’s possible:

Delete an existing User (the Admin user cannot be deleted) by clicking on the Delete button.Change PW (by Administrator) by clicking on the Change PW button.

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

By clicking on the Help button the help browser will display the help-on-line pages dedicated to this function.






3.7.3 How to Create a New User

By clicking on the Create button, the following window appears and allows the user Administrator to create a new user.






3.7.3 How to Create a New User [cont.]

The operator has to insert the parameters to define the new user and his profile rights:

1. AdminPassword: the password of Administrator for confirmation and validation.2. UserName: the specific name to be assigned to the new User (if it exists, the action will be failed).3. Profile: the specific profile to be assigned to the new User.4. Password: the specific password to be assigned to the new User.5. Confirm Password: again the specific password to be assigned for confirmation and validation.

The supported profiles are:Administrator: full access also for security parametersOperator: person in charge to operate at network level, not at radio side; dangerous operations that require NE reconfiguration at radio site are not permitted including backup/restore and restart NE features; could change own passwordCraftPerson: person in charge for installation and the maintenance at radio site; full access to NE but not for security parameters, only for own passwordViewer: only to explore the NE

Supported operations by the profiles:Administrator profile: All the NE parameters are accessible both in writing and reading mode. Also the management of user accounts is allowed (create/delete user accounts and change of all passwords).Operator profile: Full reading access to NE parameters. For writing mode the following parameters are allowed to change:

ATPC configuration (not implemented)Performance Monitoring management

start/stop CD threshold tables configuration reset archiving (only for NMS system)

CraftPerson profile: This operator has the same priviledges of the Administrator, but cannot manage the user accountsViewer profile: This operator can only read and can change his own password.

By clicking on Apply button, at first JUSM performs a syntax check of each field: if there are some errors, JUSM will display the specific message and allows the operator to correct them. If all parameters are correct, all parameters are sent to NE; after to have automatically closed the window, a message with result of the action will be displayed.By clicking on Cancel button, the Create User window closes and no action will be performed.






3.7.4 How to Delete a User

After the selection of a User in the Profile Table, by clicking on the Delete button, at first a confirmation dialog (Figure “Delete user confirmation”) will be displayed; then the window to confirm the administrator password will be displayed (Figure “Confirm Administrator Password to Delete a User”).

Delete user confirmation Confirm Administrator Passwordto Delete a User

By clicking on the Apply button, a message with the result action will be displayed after to have closed automatically the window above.

If the operator clicks on Cancel button the window will closes and no action is performed.






3.7.5 Change the Password (by the Administrator)

The Administrator User can change the password of another user: select the user in the Profile Table and then click on Change PW button. The following dialog box is displayed:

Change Password of User by Admin

The admin has to insert his password and the new password for selected user in the two text fields.

By clicking on Apply button, at first JUSM performs a syntax check of each field: if there are some errors, JUSM will display the specific message and allows the operator to correct them. If all parameters are correct, all parameters are sent to NE; after to have automatically closed the window, a message with result of the action will be displayed.

By clicking on Cancel button, the window will be closed.






3.7.6 Change Password (by the User)

If the operator wants to change his password, he has to select the Change Password menu item. The following dialog will be displayed:

Change User Password

The operator has to insert the current password and the new password in the two text fields.

By clicking on Apply button, at first JUSM performs a syntax check of each field: if there are some errors, JUSM will display the specific message and allows the operator to correct them. If all parameters are correct, all parameters will be sent to NE; after to have automatically closed the window, a message with result of the action will be displayed.

By clicking on Cancel button, the window closes.





4 Menu Diagnosis





4 Menu Diagnosis

4.1 Menu Diagnosis

Menu Diagnosis is divided in:

Alarms

Log Browsing

Remote Inventory

Abnormal Condition List

Summary Block Diagram View

Current Configuration View





4 Menu Diagnosis

4.2 Alarms

Alarms Monitor is an application which allows to display and store the alarms of all the NEs requiring it.

Alarms Monitor can be also started by clicking on the Alarms Monitor button on Neto.





4 Menu Diagnosis

4.2 Alarms [cont.]

On the left side of the application, below each NE, two global lists of alarms are displayed:

CURRENT_ALARM shows all the equipment alarms currently present,ALARM_LOG shows all the equipment alarms currently present and the history of the alarms (i.e. cleared alarms).

Each global list has some default filters (5 filters for the CURRENT_ALARM list and 8 filters for the ALARM_LOG list), as follows:

1) CRI contains all the alarms having a CRITICAL severity2) MAJ contains all the alarms having a MAJOR severity3) MIN contains all the alarms having a MINOR severity4) WRG contains all the alarms having a WARNING severity5) IND contains all the alarms having an INDETERMINATE severity6) CLR contains all the alarms which are in the CLEARED state, that is, which are no longer active (this filter is available within the list ALARM_LOG only).

For each list and for each filter, the number of active alarms is shown inside brackets.These two lists can be filtered using customized filters provided by means of the menu Filters → Add a Filter.

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





4 Menu Diagnosis

4.2 Alarms [cont.]

Single clicking on a filter or on a global list on the left part of the screen shows up on the right side the relevant tab panel with all the alarms.At the top right, the field Synthesis shows the number of active alarms for any severity.The alarms have a different color according to their severity and their state.

Red: CRITICAL alarmBrown: MAJOR alarmYellow: MINOR alarmBlue: WARNIG alarmWhite: INDETERMINATE alarm (Note that the equipment has no alarm having such severity)Green: CLEARED alarm (alarm no longer active).

Note: when the application is opened for the first time, only the tab-panels of the two global lists are displayed on the right part of the window.





4 Menu Diagnosis

4.2 Alarms [cont.]

Within the tab-panel, each alarm is provided with the information below.

Time & Date: date and time of the alarm. The format of date and time is yyyy/mm/dd hh:mm:ss.Probable cause: name of the probable cause of the alarm.Alarm Type: alarm class (TRS = Transmission Alarm – alarm not created inside the equipment, but generated by a connected equipment or due to transmission/propagation problems; EQUIPMENT: inside alarm of the equipment).Friendly Name: object of the equipment where the alarm occurred.Severity: alarm severity.Add Text: not available.Specific problem: for some alarms, additional information is provided about the involved resource (for instance, when a threshold alarm is raised, it states the specific threshold exceeded)





4 Menu Diagnosis

4.2 Alarms [cont.]

Right-clicking on an alarm row opens the menu shown in the following figure.

Navigate to USM: to navigate to the object involved with the selected alarm and to open the relevant window. Note: this option is available in the CURRENT_ALARM global list and in the relevant filters only.

Export Alarm: to create a file containing alarms data. Alarms have to be selected by means of the menu Select All. Generated file formats are CSV, HTML and XML.

Print current view: it is possible to print the list of the alarms. The “Print Dialog” box is shown to choose the printer and set Print range and Copies number.

Select: to select all the alarm of the list (All) or to select none (None) for further use, e.g. to export alarms to a file.





4 Menu Diagnosis

4.2 Alarms [cont.]

The Menu Bar provides the following menus:

File

Filters

Help





4.2 Alarms

4.2.1 File Menu

Save Log for selected NEThis menu allows to save a file with one of the two global lists of each NE. Select the global list of a specific NE, open the Save History menu for the selected NE and enter filename and relevant directory in the opening window.

Load Log to selected NEBy means of this menu it is possible to display the global list of a certain NE previously saved.

Export AlarmsThis menu allows to save a file with the alarms of the selected Log. Select the log, select "Export Alarms" menu, choose the file format (CSV, HTML or HML) and then assign the name of the file.





4.2 Alarms

4.2.2 Filters Menu

The Menu Filters provides the following menus:

Add a Filter …

Delete Filters …

Save Filters As …

Load Filters From …





4.2.2 Filters Menu

4.2.2.1 Add a Filter …

This menus allows to create customized logs adding some new specific filters. The windows which opens is shown below.

Filter Name fieldEnter the filter name in the Filter Name field.

The filters can be created selecting one of the following fields (or more). To save the created filter click on the Donepushbutton. (Clicking on the Cancel pushbutton clears the filter configuration). The created filter appears on the left side of the application.

Scope fieldSelect APT (Current) to create a filter showing the current alarms only or select Log to create a filter for current and cleared alarms.

The filter can be applied to all the NEs by selecting All or it can be applied to one or more NEs by selecting one or more NEs using the mouse.

Alarm Type fieldSelect Alarm Type to create a filter for the selected type of alarm:

TRS = Transmission Alarm

EQUIPMENT = Equipment alarm

Perceived severity fieldSelect Perceived severity and then one or more severity levels and/or Cleared state to filter the alarm having the selected severity levels.

Event Time fieldSelect Event Time and then enter the starting date (From) and the ending date (To) to filter the alarms created during that specific time frame only.

Probable Cause fieldSelect Probable Cause and the choose a specific alarm (one or more) to filter these particular alarms only.

Resource fieldPut a check mark on the Resource box and write the object name the alarms of which have to be filtered (if required).





4.2.2 Filters Menu

4.2.2.2 Delete Filters ...

When this menu is selected, the window shown below opens.

By means of this menu the filters previously created can be canceled. Default filters cannot be canceled.

Select one specific NE (or more NEs) in the Scope column, select a specific filter (or more filters) in the Filters column and then click on the Done Pushbutton.

Clicking on the Cancel pushbutton all the selections are cleared.





4.2.2 Filters Menu

4.2.2.3 Save Filters As ...

A default filter, or a filter previously created by means of the Add a filter … menu can be saved to be used for some other LCTs.

Select in the Scope and Filters columns a specific filter to be saved, enter the filter name in the Namefield, select the Folder where to save the file relevant to filter and then click on the Done Pushbutton.

Clicking on the Cancel pushbutton all the selections are cleared.





4.2.2 Filters Menu

4.2.2.4 Load Filters From ...

A filter previously saved can be loaded on the LCT by means of the following menu.

Click on Browse to navigate and then choose the filter file to be loaded. The Scope and the Loaded Filterscolumns will show respectively the NE list and the filters list made available by the selected file.

Entering some characters in the Filters Prefix field and then clicking on the Done pushbutton, the inserted characters are attached before the names of the Loaded Filters. For instance entering <Vim>, the names of the filters change from APT to VimAPT.





4.2 Alarms

4.2.3 Help Menu

This menu shows the Product Version.





4 Menu Diagnosis

4.3 Log Browsing

In the Diagnosis pull-down menu select the Log Browsing option.

The Alarm Log option is not available in the current release.

The Software Trace Log option is reserved to the Alcatel-Lucent technicians.

The Event Log option opens the Event Log browser application.





4.3 Log Browsing

4.3.1 Event Log Browser

Event Log Browser is an application which allows to display all the events occurred in the NE. An event is meant to be:

a configuration changea change of the value of an attributean automatic switchovera manual operation carried out by the operator.

The following information is provided for each event:

Time: date and time of occurrence of the event. The format is week day/month/day hh:mm:ss. Reference Time (CEST) year.

Notification ID: a unique identifier for the event.

Explanation: a statement built with the event log data to explain what the event represents.





4.3 Log Browsing

4.3.1 Event Log Browser [cont.]

The Menu Bar provides the following menus:

File

Help






4.3.1.1 File Menu

The Menu File makes available the following menus:Refresh TablesExportPrintExit

Refresh TablesBy means of this menu the event log is refreshed.A refresh may be executed as well clicking on the relevant pushbutton below the menu bar.






4.3.1.1 File Menu [cont.]

ExportThis menu allows to export the alarm table as a file.

The file can have the HTML, CSV, PDF or XML format. The file can store all the events (All entries) or only those selected by means of the pointer of the mouse (Selection).The Export may be executed as well clicking on the relevant pushbutton below the menu bar.






4.3.1.1 File Menu [cont.]

PrintIt is possible to print the event list (all or just the selected ones). The Print Dialog box shows up allowing to choose the printer and set print range and number of copies.

The print may be executed as well clicking on the relevant pushbutton below the menu bar.






4.3.1.2 Help Menu

This menu shows the Product Version.





4 Menu Diagnosis

4.4 Remote Inventory

This screen is a read-only screen, which shows all the information on the equipment.





4 Menu Diagnosis

4.5 Abnormal Condition List

The Abnormal Condition List option in the Diagnosis menu displays all the abnormal conditions currently active in the NE.An abnormal condition is generated each time a non usual condition is present in the NE, detected automatically (i.e. automatic Tx mute) or as consequence of management systems operation (i.e. force switching, loopbacks, manual Tx mute).

The list of the events which cause an abnormal condition:

Forced switch (EPS, RPS, TPS)

Lockout (EPS, RPS, TPS)

Loopback activation

Local radio Tx mute (manual)

Adaptive Modulation in normal mode





4 Menu Diagnosis

4.6 Summary Block Diagram View

The “Summary Block Diagram View” of the Diagnosis menu displays a global logical view (strictly related to the physical implementation) highlighting a synthesis of all the alarms and statuses present in the system.






4.6.1 Main Block diagram view

The Figure shows an example of the Main block diagram view.

Each block has its Alarm indicator (coloured ball icon) that shows the alarm status (different colors according to the alarm severity).

In the Main view the current configuration of the PNU is shown, with the equipped units (PDH or Radio), with the protection schemes and with the cross-connections implemented between the different units and the different Ethernet ports, if any.

On the RADIO slot icon there is the symbol because on this unit a loopback can be activated, the symbol because it is also possible to activate a Performance monitoring and the symbol because it is possible to activate the Ethernet traffic counters. If these symbols are green, it means that the loopback is active or the Perfomance monitoring/Ethernet Counters have been activated.

By clicking on an object it s possible to navigate to specific views. In detail:

by clicking on the Abnormal Condition List box, it is possible to navigate to the Abnormal Condition List menu;

by clicking on the NMS Interfaces box, it is possible to navigate to the NMS view in the Core-E unit;

by clicking on the Ethernet icon in the Cross Connection Matrix, it is possible to navigate to the Ethernet port view in the Core-E unit;

by clicking on a PDH slot icon in the Cross Connection Matrix, it is possible to navigate to the secondary view for the PDH unit;

by clicking on a Radio slot icon in the Cross Connection Matrix, it is possible to navigate to the secondary view for the Radio unit;

The “Refresh” button will close all secondary windows, updating the main view one, and re-opening all previously opened secondary windows, with updated content views.

All diagrams are automatically refreshed. According to following figures, bold light green lines update according to the actually NE working way; alarm icons update as well.

The green line is the current active path.






4.6.2 PDH unit secondary view

Depending on the configuration, different diagrams are shown to the operator, describing the actual NE status and working mode.

1+0 block diagram (PDH unit) (without Core-E protection)






4.6.2 PDH unit secondary view [cont.]

1+0 block diagram (PDH unit) (with Core-E protection)







1+1 block diagram (PDH units) (without Core-E protection)







1+1 block diagram (PDH units) (with Core-E protection)






4.6.3 Radio unit secondary view

Depending on the configuration, different diagrams are shown to the operator, describing the actual NE status and working mode.

1+0 block diagram (Radio unit) (without Core-E protection)

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

Performance monitoring icons ( ) are shown in green whenever a PM is active.

By clicking on the Performance Monitoring icon ( ) the navigation to the Performance Monitoring tool starts.

Ethernet Counters icon ( ) is shown in green whenever the counter has been activated.

By clicking on the Loopback icon, on the PM icon or on the Ethernet Counters icon the navigation to the relevant menus starts.

Switch block (“EPS Core”, “RPS TX”, “RPS Rx”, …) are updated according to the signal path, following light green-coloured line.






4.6.3 Radio unit secondary view [cont.]

1+0 block diagram (Radio unit) (with Core-E protection)







1+1 FD block diagram (Radio units) (without Core-E protection)







1+1 FD block diagram (Radio units) (with Core-E protection)







1+1 Hot Standby block diagram (Radio units) (without Core-E protection)







1+1 Hot Standby block diagram (Radio units) (with Core-E protection)





4 Menu Diagnosis

4.7 Current Configuration View

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





Blank Page






5 Menu Supervision





5 Menu Supervision

5.1 Menu Supervision

Menu Supervision is divided in:

Access State

Restart NE

MIB Management (not implemented in the current release)

SW Licence





5 Menu Supervision

5.2 Access State

The NE can be managed by the OS or by the Craft Terminal. To control the competition of the OS and the CT, a Local Access Control (LAC) is available.If the LAC is “access denied”, it means that the OS manages the NE and the CT is not allowed to modify the NE configuration (it can only «read»). In the view, the icon with a key symbol has a circular shape.If the LAC is “granted”, it means that the CT is allowed to manage the NE. In the view, the icon with a key symbol has a rectangular shape. If the LAC is “requested”, it means that the CT has requested a permission from the OS and is waiting for a replay.However, the OS does continue to provide a certain number of services. These services include:

Alarm reception and processing,Performance processing,Switching back to the OS access state.

The access state of an NE can be modified from two types of views.





5.2 Access State

5.2.1 Requested (Switching OS CT access state)

Select the Supervision pull down menu. Then select the Requestedoption from the Access State cascading menu.If the OS does not answer in a predefined time, it is assumed that the NE is in the Craft access state and can be managed by a Craft Terminal.





5.2 Access State

5.2.2 OS (Switching CT access state OS)

Select the Supervision pull down menu. Then from the Access Statecascading menu select the OS option.The NE is now managed by the OS.

N.B. The key symbol icon on the management states of the NE view indicates whether the NE is managed by a craft terminal or by the OS.

N.B. Local Craft Terminal access is denied on recovery phase after a loss of communication of the NE. When the communication with the NE is lost, the OS automatically recovers the communication and forces the state existing before the loss of communication (therefore, Craft Terminal access can be denied or granted).





5.2 Access State

5.2.3 LAC Time Out Period

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





5 Menu Supervision

5.3 Restart NE

The Restart operation is a software reset and can be executed innormal traffic conditions.From the Supervision cascading menu, select the Restart NE option.A dialogue box opens.Click the Yes button to confirm the restart NE operationClick the No button to abort the restart NE operation.

WARNING: After the activation of the Restart NE Command (or after the pressing of the HW reset push-button) the supervision of the local NE and the remote NEs is lost.





5 Menu Supervision

5.4 SW Licence

In this screen the following fields are present.RMU Serial Number: in this read-onlyfield appears the Serial Number of the Flash Card.License String: in this read-only field appears the type of the license written in the Flash Card.License Key: this field is used to upgrade the license. To upgrade the license copy in this field the code of the new license and click on Apply.

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





6 Tab-panel Equipment






6.1 Starting From Scratch

When the equipment configuration panel is open starting from a scratched NE, the operator will see the panel in figure below. The Resource Tree area contains a list of empty slots that have to be configured. Icon is used to identify an empty slot.

To configure a card:

Select a slot.

Click on Settings panel.

Select the correct type of unit.

Click on Apply.

Now in the MSS will appear the new card in the slot.






6.2 Tab panels in the Resource Detail Area

For every unit in the MSS there are 3 tab-panels:

Alarms

Settings

Remote Inventory






6.2.1 Alarms tab-panel

The Alarms tab panel provides the fault management, which checks the current state of alarms related to the selected object.The alarm tab panel has one row for each possible alarm, but only rows related to the active alarms are highlighted. When the alarm disappears it is automatically cleared in the screen.For every alarm the following information is given:

Severity: the severity associated to the alarm and assigned in the Alarm ProfileEvent Time: the time of the generation of the alarmEntity: the entity involved in the alarmProbable Cause: the probable cause of the alarmManaged Object Class: the class of the alarm.






6.2.2 Settings tab-panel

In the Setting tab-panel the following fields are present:

Equipment Type

Protection Type Configuration

Alarm Profile (not implemented)






6.2.2.1 Equipment Type

The operator must set for all the slots the expected equipment type. The list box shows the expected equipment type (P32E1DS1 or MD300) for slot 3 to 8;Select the equipment type and click Apply.

The Setting tab-panel of the Core-E unit is shown here below.Click on Apply on the Plug-in Type field to enable the SFP optional optical plug-in, if the plug-in has been installed in the Core-E unit.






6.2.2.2 Protection Type

The operator can configure the NE protection type. This function is shown selecting slots 3 to 8 only.For slots 1 and 2 (reserved to Main and Spare Core-E units) the protection type is automatically configured by the system. After the equipment selection, protection type list box is filled with allowed protection types list (the content depends on expected equipment configured):

If it is configured as P32E1DS1, allowed protection types are “1+0” and “1+1 EPS”;If it is configured as MD300, allowed protection types are “1+0”, “1+1 HSB”and “1+1 FD”.

Select the Protection type and click on Apply.

If the operator selects a protection type equal to received one, apply button is disabled. If operator selects a protection type different from received one, apply button is enabled. If slot is in protection mode (received protection type different from “1+0”): apply button related to expected-equipment is disabled (equipment changing is allowed in “1+0” configuration only).






6.2.2.2 Protection Type [cont.]

When a board shows the check mark ( ) icon, while same-pair (same-row) one shows switch symbol ( ), this means pair (row) is protected. In this situation, the couple is considered as if it is one board and each single board cannot be removed/un-configured unless removing protection.

Check mark icon ( ) denotes “active” board while switch one ( ) represents “stand-by” board.

Same behaviour occurs when X-shaped icon ( ), representing cross-connections, appears. PDH board cannot be removed as well when Flow IDs are configured. An error message will be shown if the operator will try to perform such operations.






6.2.3 Remote Inventory tab-panel

The Remote Inventory feature stores information used to identify all product components.The whole information related to selected equipment type can be read, if available, in the remote inventory panel, inside the Resource Detail area. Remote inventory data won’t be available for levels that do not have remote inventory itself, as IDU Ch#1 or IDU Ch#0.





Blank Page






7 Tab-panel Protection Schemes






7.1 General

The 1+1 protection schemes implemented are:

Equipment protection: EPS protection in Tx and Rx sides (this protection scheme can be implemented for all the unit types: Radio unit, PDH unit and Core-E unit)Rx Radio protection: RPS Hitless Switch in Rx side (available for the Radio unit only)HSB protection: Hot Stand-by protection (available for the Radio unit only)FD protection: Frequency Diversity protection (available for the Radio unit only)Synchronization protection: This protection scheme will appear, if in the synchronization tab panel the Primary Source and the Secondary Source have been selected.

Note 1: For the pair of Core-E units (slot 1 and 2) the only protection type is the Equipment Protection.

Note 2: For the pair of Radio units the protection type are the Equipment Protection, Radio Protection and HSB Protection or FD protection.

Note 3: For the pair of PDH units the only protection type is the Equipment Protection.






7.1 General [cont.]

Protection scheme screen

To see the current position of the switches enter the menu Diagnosis Summary Block Diagram View and click on the icon of the equipped units.






7.2 EPS Management

The Equipment Protection Management is performed by selecting the Equipment Protection tree element.This window allows a complete view of all NE resource involved in the EPS protection.The tab-panels are:

Protection Schema ParametersCommands





7.2 EPS Management

7.2.1 Protection Schema Parameters

The tab-panel “Schema Parameters” displays the parameters that can be modify.

The parameters are:

Protection Type: this parameter is defined at creation time and it is read only. The supported type is: 1+1, e.g. a working channel (Main) is protected by a protecting channel (Spare).

Restoration Criteria: it defines if automatic restoration from protecting to protected channel is allowed (revertive mode) or inhibited (not revertive mode). The operator choice for “Operation Type” will be applied by clicking on “Apply” button.

Note: The Core protection type is Revertive and cannot be changed.





7.2 EPS Management

7.2.2 Commands

To enter the Commands menu click on the Spare #0 element in the Tree view or on the Main #1 element. The operator by the Craft Terminal can modify the state of the switch through commands Lockout, Forced and Manual. Select the suitable command and click on Apply.Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel), independently of the possible active alarms. This command activates signaling ABN.Forced has higher priority than the automatic operation: the activation of this command forces in service Channel 0, independently of the possible active alarms. This command activates signaling ABN.Automatic Switch is the normal operation condition: the position of the switch depends on the commands generated by the logic.Manual has the lowest priority: it is performed only if there are no alarms that can activate an automatic switch. It cannot be performed if Lockout or Forced commands are already activated. If this command is active, it will be removed by an incoming alarm. This command does not activate signaling ABN.

Note:

On the Main#1 channel the only available commands are Manual and Forced.

On the Spare#0 channel the only available commands are Manual and Lockout.WARNING: the EPS Lockout command is not error free, even if it is raised when traffic is not on the spare channel.

Note: The “Forced” command for channel 1 is equivalent to the “Lockout” command for the channel 0. In both case, the result is that the relevant channel protection path is forced to standby status.

Command priority list

N.B. To release a previously activated command select None and click on Apply.

4Manual

3Automatic switch

2Forced

1Lockout

PriorityCommand






7.3 RPS Management

The Radio Protection Management is performed by selecting the RxRadio Protection element tree.This window allows a complete view of all NE resource involved in a RPS protection.The tab-panels are:






7.3 RPS Management


The tab-panel “Protection Schema Parameters” displays the parameters that can be modify.

The Schema Parameters are:

Protection Type field: defines the protection schema architecture: 1+1 hitless;

Operation Type field: the possible values are revertive (automatic restoration allowed) or notRevertive(automatic restoration Inhibited).





7.3 RPS Management

7.3.2 Commands

To enter the Commands menu click on the Spare #0 element in the Tree view or on the Main #1 element. The operator by the Craft Terminal can modify the state of the switch through commands Lockout, Forced and Manual. Select the suitable command and click on Apply.Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel), independently of the possible active alarms. This command activates signaling ABN.Forced has higher priority than the automatic operation: the activation of this command forces in service Channel 0, independently of the possible active alarms. This command activates signaling ABN.Automatic Switch is the normal operation condition: the position of the switch depends on the commands generated by the logic.Manual has the lowest priority: it is performed only if there are no alarms that can activate an automatic switch. It cannot be performed if Lockout or Forced commands are already activated. If this command is active, it will be removed by an incoming alarm. This command does not activate signaling ABN.

Note:


On the Spare#0 channel the only available commands are Manual and Lockout.Note: The “Forced” command for channel 1 is equivalent to the “Lockout” command for the channel 0. In both case, the result is that the relevant channel protection path is forced to standby status.



4Manual

3Automatic switch

2Forced

1Lockout

PriorityCommand






7.4 HSB Protection Management

The Transmission Protection Management is performed by selecting the HSB Protection element tree.This window allows a complete view of all NE resource involved in the protection.The tab-panels are:








The tab-panel “Protection Schema Parameters” displays the parameters that can be modify.

The Schema parameters are:

Protection Type: this parameter is defined at creation time and it is read only. The supported type are: 1+1 (onePlusOne) ,e.g. a working element is protected by one protecting unit.

Operation type: it defines if automatic restoration from protecting to protected unit is allowed (revertivemode) or inhibited (not revertive mode). The operator choice for «Operation Type» will be applied clicking on “Apply” button.






7.4.2 Commands

To enter the Commands menu click on the Spare #0 element or on the Main #1 element in the Tree view.The operator by the Craft Terminal can modify the state of the switch through commands Lockout, Forced and Manual. Select the suitable command and click on Apply.Lockout has higher priority than Forced: the activation connects to theantenna Transmitter 1 (default transmitter), independently of the possible active alarms. This command activates signaling ABN.Forced has higher priority than the automatic operation: the activation of this command connects to the antenna Transmitter 0, independently of the possible active alarms. This command activates signaling ABN.Automatic Switch is the normal operation condition: the position of the switch depends on the commands generated by the logic.Manual has the lowest priority: it is performed only if there are no alarms that can activate an automatic switch. It cannot be performed if Lockout or Forced commands are already activated. If this command is active, it will be removed by an incoming alarm. This command does not activate signaling ABN.

Note:


On the Spare#0 channel the only available commands are Manual and Lockout.Note: The “Forced” command for channel 1 is equivalent to the “Lockout” command for the channel 0. In both case, the result is that the relevant channel protection path is forced to standby status.



4Manual

3Automatic switch

2Forced

1Lockout

PriorityCommand





8 Tab-panel Synchronization






8.1 Menu Synchronization

Synchronization menu allows the operator to manage the synchronization features.

Using “Synchronization” tab view (shown in the figure below) the operator can select and configure synchronization source(s) for the equipment.

Together with “Role” and “Restoration” criteria, the operator can select Input and Output ports and can discriminate between different possible “Primary” or “Secondary” sources, according to the Role.

The Resource list area shows the configuration summary describing current synchronization.






8.2 How to synchronize

Each Network Element must have a reference Clock (NEC), which will be distributed to each board of the NE. Such clock is a 25 MHz generated in the Core-E Module.The NEC also provides a Sync Out port on the Core-E Module, which can be used to synchronize other NEs.The NEC is locked to a Synchronization Source. The sources can be:

[1] Free Run Local Oscillator.[2] Any E1 available at input traffic interfaces (the specific E1 port has to be chosen)[3] Sync-In port is a specific synchronization input, which can be configured according to the following options:

a) 2.048 MHz, electrical levels according G.703, clause 13b) 5 MHz, + 6 dBm into 50 , sine-wavec) 10 MHz, + 6 dBm into 50 , sine-wave.

[4] Radio Port: Symbol Rate of the Rx signal of any available Radio direction (the specific Radio Port has to be chosen)






8.2 How to synchronize [cont.]






8.2 How to synchronize [cont.]

All the NEC has to be configured as Master Role or Slave Role.Only one Master is allowed in the network.

If Master Role,The Restoration Mode can be Revertive and Not RevertiveThe Primary sources must be chosen among 1), 2) or 3).If the selected Master Primary Source is 1)

then the Master Secondary Source doesn't need to be selected because the Primary is never supposed to fail.

If the selected Master Primary Source is 2) or 3)then Master Secondary Source must be selected among 1), 2) or 3).

If Slave Role,The Restoration Mode is fixed to Revertive.The Primary Source must chosen between 3) and 4)

Slave primary sources is allowed to be 3) for full indoor configuration and future Piling configuration

The Secondary Source can be chosen among 1), 2) or 3).

Each Module will mute its own Synchronization clock in case of Fail Alarm.

For each available sync source, the signal Degrade Alarm is detected on each available sync source. Such Signal Degrade alarm raises also in case of muted (missing) clock.

The Signal Degrade Alarm relevant to the selected Synchronization Source, or the relevant Card Fail, causes the switching of the Synchronization Source.





Blank Page






9 Tab-panel Connections





9 Tab-panel Connections

9.1 Menu Connections

This menu (available in the Main view) contains a summary table for all the implemented cross-connections. This menu is shown in the figure.

In the Resource Detail Area are available two different functions usable to export and save cross-connections data with different formats:

hardcopy (Send To Printer);

file (Export To File).





10 PDH view for PDH domain






10.1 PDH Unit configuration

This menu opens with double click on a PDH unit in the Equipment tab-panel.

In the Resource List Area is given the information related to the tributaries:

1) Port Number: port for a given channel and type of port

2) Signal Mode: type of frame (Framed/Unframed/Disabled)

3) Flow Id: identifier of the tributary for the cross-connection

4) Service Profile: possible profile to be associated to the tributary (TDM2TDM/TDM2Eth)

5) Payload: bytes of the payload (256)

6) ECID Tx: Emulated Circuit Identifier in Tx direction

7) ECID Rx: Emulated Circuit Identifier in Rx direction

8) TDM Clock source: type of the clock to be associated to the tributary (Adaptive/Differential/Tdmline)

Note: Columns 5, 6, 7 and 8 are only available if the Service Profile is TDM2Eth.






10.1 PDH Unit configuration [cont.]

For every E1 tributary two tab-panels are available:

Alarms tab-panel

Settings tab-panel






10.1.1 Alarms tab-panel

The Alarms tab panel provides the fault management, which checks the current state of alarms related to the selected object.The alarm tab panel has one row for each possible alarm, but only rows related to the active alarms are highlighted. When the alarm disappears it is automatically cleared in the screen.By putting a tick in the Include alarms from sub-nodes box the alarms currently active in the sub-nodes of the object will also appear.For every alarm the following information is given:

Severity: the severity associated to the alarm and assigned in the Alarm ProfileEvent Time: the time of the generation of the alarmEntity: the entity involved in the alarmProbable Cause: the probable cause of the alarmManaged Object Class: the class of the alarm.







This tab-panel performs all available functions for a tributary port. Themanaged tributary types are E1 streams. To define the involved ports, the interface selection in the tree view is first required; therefore the selection of the desired tributary port in the tabular view enables the “Resource Detail list” to show the available functions for the single one resource.

Warning: to change something in the Settings tab-panel first changes the Signal Mode to Unframed. After this, all the other fields can be changed.In the Setting tab-panel there are the following fields:

Port Number: identifies the ports for a given interface and type of port (read-only fields)Signal Mode. The possible values are:

Unframed for the unframed received signalDisabledThe current state can be modified selecting a different signal mode value and then click on the “Apply” button to send the new value to NE.

Flow Id: To implement cross-connections between line side and radio side each E1 tributary must be associated to an identifier. Enter the Flow identifier value in the relevant field (possible values: 2 to 4080) and press Apply. Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if the Service Profile is TDM2Eth.With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time Protocol is used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP - Real Time Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have mixed configurations with service profiles using RTP and other service profiles not using RTP. Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure other E1 with service profile TDM2Eth only with the Differential clock source (not with the Adaptive clock source). If the Adaptive clock source is requested the E1 must be connected to another PDH unit. Alarm profile: Not implemented now.

Buttons:Apply: the configuration for the selected E1 tributary will become activeApply to All: the configuration present in the screen will be applied to all the ports.Help: by clicking on this button the operator calls the help on line.





Blank Page






11 Radio view for Radio domain






11.1 Radio domain menu

To enter this menu double click on the front panel of the Radio unit in the Equipment tab-panel and then click on the setting tab-panel.

The above screen opens.

Five tab panels are present:

Alarms: shows the active alarms

Settings: configures some radio parameters

Measurements: performs the Tx and Rx power measurements.

Loopback: activates the loopbacks available with the equipment.






11.2 Settings

This tab-panel is divided in 3 areas:

Direction #

Channel 1

Channel 0 (present only in 1+1 configuration)





11.2 Settings

11.2.1 Direction area

This area is divided in 3 parts:

1) Mode

2) Link Identifier Configuration

3) PPP RF





a) Operation without the Adaptive Modulation

Radio unit without Adaptive Modulation settings


11.2.1.1 Mode

Select in the Mode field “Presetting”.

Select in the Reference Channel Spacing field the suitable channel spacing to be used.

Select in the Modulation field the suitable Modulation scheme.

According to the selected Channel Spacing and to the Modulation the relevant capacity in the Capacity field will appear.

To confirm the selection click on Apply.

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






11.2.1.1 Mode [cont.]

Radio capacity, channelling scheme and modulation (Static Modulation)

136 E1313,60 Mbit/s128 QAM

72 E1166,40 Mbit/s16 QAM56 MHz

77 E1177,60 Mbit/s256 QAM

68 E1156,80 Mbit/s128 QAM

56 E1130,56 Mbit/s64 QAM

48 E1111,36 Mbit/s32 QAM

37 E187,04 Mbit/s16 QAM

18 E143,52 Mbit/s4 QAM

28 MHz

27 E165,28 Mbit/s64 QAM

18 E143,52 Mbit/s16 QAM


14 MHz

13 E132,64 Mbit/s64 QAM



7 MHz

E1 Equivalent Capacity (TDM2TDM)Net radio throughputModulationChannel

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






11.2.1.1 Mode [cont.]

b) Operation with the Adaptive Modulation

Radio unit with Adaptive Modulation settings

Select in the Mode field “Adaptive Modulation”.

Select in the Modulation Range field the Modulation range (4/16 QAM or 4/16/64 QAM) to be used by the Adaptive Modulation.

Select in the Reference Channel Spacing field the suitable channel spacing.

Select in the Reference Modefield the spectral efficiency class to be set as reference.

To confirm the selection click on Apply.

Select in the Remote Threshold field how many dB the switching thresholds have to be moved from the default value (+4 dB/-2 dB). The default value is approx. 6 dB below the 10-6 Rx threshold.

The Current Modulationfield is a read-only field, which shows the current used modulation. The current modulation will depend on the fading activity during the propagation.

With a check mark in the Manual Operation box it is possible to force a modulation scheme by selecting the scheme in the Forced Modulation field.

The main idea behind Adaptive Modulation in Point to Point system is to adjust adaptively the modulation as well as a range of other system parameters based on the near-instantaneous channel quality information perceived by the receiver, which is fed back to the transmitter with the aid of a feedback channel.

The switching between the modulation schemes is hitless and maintains the same RF channel bandwidth.

The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB) Radio configuration without ATPC.

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.






11.2.1.1 Mode [cont.]

Radio capacity, channelling scheme and modulation (Adaptive Modulation)

13 E132,64 Mbit/s64 QAM



7 MHz

27 E165,28 Mbit/s64 QAM

18 E143,52 Mbit/s16 QAM


14 MHz

56 E1130,56 Mbit/s64 QAM

37 E187,04 Mbit/s16 QAM


28 MHz

Equivalent capacity E1 (Note)

Net radio throughputModulationChannel Spacing

Note: The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive Modulation) can be enabled or disabled.

When the Admission Control is enabled, the check is performed taking into account the capacity of the 4 QAM modulation scheme for the relevant Channel Spacing.

When the Admission Control is disabled, the check is performed taking into account the capacity of the highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-16-64 QAM range or 16 QAM for 4-16 QAM range).






11.2.1.1 Mode [cont.]

How to change the operation mode (from operation without Adaptive Modulation to operation with Adaptive Modulation) in 1+1 HSB configurationFollow the procedure:1. Mute the 2 Transmitters2. Remove the protection scheme: enter the Equipment tab-panel, select the

unit and remove the protection scheme3. Enter the Main Radio unit setting tab-panel: set Mode Adaptive Modulation4. Create again the protection scheme: enter the Equipment tab-panel,

select the unit and create the protection scheme (1+1 HSB)5. Remove the muting from the Transmitters.






11.2.1.1 Mode [cont.]

Channel Spacing ChangeCapacity Up-Grade

When the admission control is enabled, this applies when the lowest modulation scheme of the new channel spacing has a capacity which is larger than the one with the old channel spacing. In this case all the pre-configured TDM2TDM or TDM2ETH will be kept. The residual bandwidth for the lowest modulation scheme is recomputed. When the admission control is disabled, this applies when the highest modulation scheme of the new channel spacing has a capacity which is larger than the one with the old channel spac-ing. In this case all the pre-configured TDM2TDM or TDM2ETH will be kept. The residual band-width for the highest modulation scheme is recomputed.

Capacity Down-GradeWhen the admission control is enabled this applies when the lowest modulation scheme of the new channel spacing has a capacity which is smaller than the one with the old channel spacing. If all the pre-configured TDM2TDM or TDM2ETH stays in the capacity associated to the lowest modulation scheme, they will be kept and the residual bandwidth for the lowest modulation scheme is recomputed. If all the pre-configured TDM2TDM or TDM2ETH cannot stay in the capacity associated to the lowest modulation scheme, the change of channel spacing is rejected by CT/NMS.

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.






11.2.1.1 Mode [cont.]

When the admission control is disabled this applies when the highest modulation scheme of the new channel spacing has a capacity which is smaller than the one with the old channel spac-ing. If all the pre-configured TDM2TDM or TDM2ETH stays in the capacity associated to the highest modulation scheme, they will be kept and the residual bandwidth for the highest mod-ulation scheme is recomputed. If all the pre-configured TDM2TDM or TDM2ETH cannot stay in the capacity associated to the highest modulation scheme, the change of channel spacing is rejected by CT/NMS.






11.2.1.1 Mode [cont.]

Modulation ChangeCapacity Up-Grade

This applies when the new modulation scheme has a capacity which is larger than the old one. When the admission control is enabled all the pre-configured 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-GradeThis applies when the new modulation scheme has a capacity which is smaller than the old one. When the admission control is enabled, since the admission control was performed with the capacity of the lowest modulation scheme, all the pre-configured TDM2TDM or TDM2ETH will be kept. When the admission control is disabled, since the admission control was performed with the capacity of the highest modulation scheme, all the pre-configured TDM2TDM or TDM2ETH will be kept if the current capacity is able to support all of them, otherwise all pre-configured TDM2TDM or TDM2ETH will be completely lost.

When the AM engine changes the modulation, the pre-configured TDM2TDM or TDM2ETH traffic must be managed according to the behavior here after described. Two cases must be taken into account: Capacity Up-grade and Capacity Down-Grade.






11.2.1.1 Mode [cont.]

Modulation Working Mode ChangeFrom Static to Adaptive

Adaptive Modulation can be enabled only if the ATPC is disabled.When the Adaptive Modulation is enabled and Admission Control is enabled the behavior is:

If all the pre-configured TDM2TDM or TDM2ETH in the Old Static Modem Profile, stay in the capacity associated to the lowest Modulation Scheme, the request of change is accepted and the residual bandwidth for the lowest Modulation Scheme is computed. If all the pre-configured TDM2TDM or TDM2ETH cannot stay in the capacity associated to the lowest Modulation Scheme, the request of change is rejected.

When the Adaptive Modulation is enabled and Admission Control is disabled all the pre-con-figured TDM2TDM or TDM2ETH in the Old Static Modem Profile stay in the capacity associated to the highest Modulation Scheme, then the request of change is always accepted and the residual bandwidth for the highest Modulation Scheme is computed.

From Adaptive to Static When the Adaptive Modulation is disabled, if all the pre-configured TDM2TDM or TDM2ETH in the Old Adaptive Modem Profile, stays in the capacity of the New Static Modem Profile, the request is accepted and the residual bandwidth for new Static Modem Profile will be computed. If all the pre-configured TDM2TDM or TDM2ETH cannot stay in the capacity of the New Static Modem Profile, the request of change is rejected.

A specific behavior must be followed when it is needed to move from Adaptive Modulation to Static Modulation or vice-versa, in order to preserve any pre-configured TDM2TDM or TDM2ETH. Two cases must be taken into account: from Static to Adaptive Modulation and from Adaptive to Static Modulation. The working mode changes, here below described, are generic. The changes cover both the change of the modulation but with the same Channel Spacing and the change of the Channel Spacing.






11.2.1.2 Link Identifier Configuration

The operator can define the expected and sent identifier values of parameters related to the link management and, if necessary, modify them.If the Link Identifier is Enabled the following fields can be written:

Expected Identifier: this field is the link identifier expected at the receiving NESent Identifier: this field is the link identifier inserted on the transmittingNE.

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






11.2.1.3 PPP RF

The “PPP-RF” interface is a communication interface based on the use of an inframe RF proprietary 64 kbit/s channel. Through the “PPP-RF”interface the NE can exchange management messages with a remote OS (or Craft Terminal) station.The PPP-RF channel can be Enabled or Disabled.If enabled, in the Remote Address field will appear the IP address of the remote connected NE.In the Routing IP Protocol field enter the used IP protocol and in case of OSPF protocol select also the associated OSPF area.





11.2 Settings

11.2.2 Channel area

This area is divided in 5 parts:

1) Frequency

2) ATPC (this menu is alternative to Manual Transmit Power Control menu)

3) Manual Transmit Power Control (this menu is alternative to ATPC menu)

4) Tx Mute

5) Alarm Profile





11.2.2 Channel area

11.2.2.1 Frequency

The system can operate with different types of ODU according to the RF band and to the channel arrangement. There are ODUs which can manage only one shifter or several predefined shifters.In the Shifter field select the suitable shifter.In the Tx frequency field insert the suitable Tx frequency (the Rx frequency is automatically calculated by using the inserted Txfrequency and the shifter) and press push-button Apply.





11.2.2 Channel area

11.2.2.2 ATPC

The ATPC can be Enabled or Disabled. The new value will be applied when the Apply button is pressed. If the ATPC has been enabled, the ATPC Range and ATPC Rx Thresholdparameters must be filled.

ATPC RangeThe Min Tx power and Max Tx power, regarding the Tx Range in the ATPC management, can be written in the relevant field.When the Apply button is pressed the new values will be applied.

ATPC Rx ThresholdThe value of the low power threshold can be changed by writing the new value in the field. When the Rx power is equal to this power the ATPC algorithm starts to operate.When the Apply button is pressed the new values will be applied.

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





11.2.2 Channel area

11.2.2.3 Manual Transmit Power Control

Manual Transmit Power Control (without Adaptive Modulation)If the ATPC is disabled the manual Tx Power field is present. For the TxPower range refer to the table.In this field write the new value within the allowed transmitted power range. The range is shown on the right side of Manual Transmit Power Control area.

Tx Power (with Adaptive Modulation)The operator can modify only the 4 QAM field. In this field the operator has to enter the constant power, which will be used with 4 QAM modulation. The power range is shown on the right side and depends on the selected reference mode. For the Tx Power range refer to the table.

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





11.2.2 Channel area

11.2.2.3 Manual Transmit Power Control [cont.]

Tx Power values

18131914221624,515,524,515,512856

1656

161017111813201322,51322,51322,51325628

181019112013221324,51324,51324,51312828

191020112114231325,51325,51325,5136428

19,5720,51123,5132613261326133228

20102111241326,51326,51326,5131628

22223326628,58,528,58,528,58,5428

197208231025,51025,5106414

207218241026,51026,5101614

22223326628,58,528,58,5414

19420523725,58,525,58,5647

20421524726,58,526,58,5167

22223326628,58,528,58,547

dBmdBmdBmdBmdBmdBmdBmdBmdBmdBmdBmdBmdBmdBm

maxminmaxminmaxminmaxminmaxminmaxminmaxmin(MHz)

Tx PowerTx PowerTx PowerTx PowerTx PowerTx PowerTx PowerQAM

Reference Channel Spacing

15GHz13GHz11GHz10.5GHz8GHz7GHz6GHz





11.2.2 Channel area

11.2.2.3 Manual Transmit Power Control [cont.]

13,5114-111111,5215,56,515,56,512856

15,5116-1,513113,51,517,5617,561656

11,5012-29-29,5-113,53,513,53,525628

13,5014-211-211,5-115,53,515,53,512828

14,5015-212-212,5-116,53,516,53,56428

15015,5-212,5-213-1173,5173,53228

15,5016-213-213,5-117,53,517,581628

17,5018-215-515,5-4,519,5-0,519,5-0,5428

14,5015-212-512,5-416,5016,5-0,56414

15,5016-213-513,5-417,5017,551614

17,5018-215-515,5-4,519,5-0,519,5-0,5414

16,5-0,5647

15,5016-213-513,5-4,517,5-0,517,52167

17,5018-215-515,5-4,519,5-0,519,5-0,547

dBmdBmdBmdBmdBmdBmdBmdBmdBmdBmdBmdBm

maxminmaxminmaxminmaxminmaxminmaxmin(MHz)

Tx PowerTx PowerTx PowerTx PowerTx PowerTx PowerQAMReference

Channel Spacing

38GHz32GHz28GHz26GHz23GHz18GHz





11.2.2 Channel area

11.2.2.4 Tx Mute

The information related to the transmitter status is shown in the TxMute field (Off/Manual/Auto). To squelch the transmitter select Enableand press Apply button.The following indications will appear in the Tx Mute field:

Off: Transmitter not squelchManual: Transmitter squelched due to the manual operationAuto: Transmitter squelched due to an automatic operation





11.2.2 Channel area

11.2.2.5 Alarm Profile

Not implemented in the current release.






11.3 Measurement

The Power Measurements capability is performed by means of the Measurement tabbed panel.

The Measurement screen allows the operator to set initial parameters for the required measurement.

“Measurement interval” fields allow the operator to set the time duration of the measurement. The default is Days: 7, Hours: 0, Minutes: 0. A 7-day measurement interval is also the maximum allowed interval.

“Sample time” field is the period between two consecutive measurement samples. The choice is among 2, 6, 30, 60 sec.

The last section of the dialog is referred to an optional Log file.

By selecting Create File the log file is created and a default path and name for this file is displayed to the operator. The file is stored in the MPRE_CT_V00.07.08 directory.

The log file contains the sample value and records the measurement up to a maximum dimension (7 days for a 2 s sample time).

Note: The file name must not include the following characters: \ ? : * “ < > |.

By clicking on the “Start” button the screen “Power Measurement Graphic” appears.

The Power Measurement Graphic is available only if the CT is connected to the NE.






11.3 Measurement [cont.]

The Power Measurement Graphic screen shows the Tx and Rx measurements related to the local and remote NE.

Through this screen the operator can see, in real time, the power transmitted by the local and remote transmitter (Tx) and the power received by the local and remote receiver (Rx).

The top graphic screen area shows the TX curves (local and remote), while the bottom area shows the Rx curves (local and remote). Note that the colors represent the linked end-point of the two NE; for example, if the local TX is blue, the remote receiver will also have the same color.

The top of the screen offers all the characteristics present in the current measurement:

Radio port: gives the symbolic name associated to the radio channel being analyzed

Sample time: indicates the frequency used to send the measurement requests to NE;

Start time: is the first request time;

Stop time: is the interval time selected in the previous parameters window, added to the start time;

Time: is the current response time;

Log File: is the complete pathname of the file where the received values are stored.






11.3 Measurement [cont.]

By clicking on «Show details» box, on the left side of the Power Measurement Graphic, a new table appears; this table shows the following relevant values of the received and transmitted power:

Tx Local Endmax Tx local value and date when this value was received for the first time.min. Tx local value and its current date when this value was received for the first time.current Tx local value and its current date.

Tx Far Endmax Tx remote value and date when this value was received for the first time.min. Tx remote value and its current date when this value was received for the first time.current Tx remote value and its current date.

Rx Local Endmax Rx local value and date when this value was received for the first time.min. Rx local value and its current date when this value was received for the first time.current Rx local value and its current date.

Rx Far Endmax Rx remote value and date when this value was received for the first time.min. Rx remote value and its current date when this value was received for the first time.current Rx remote value and its current date.

N.B. PTx and PRx levels software readings tolerance is:PTx = Real Value ± 3dBPRx = Real Value ± 5dB

WARNING:If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HST Configuration the transmitter is in standby).If in the Tx end field the indication in dBm is +99 and, at the same time, in the relevant Rx end field the information in dBm is -99, probably the supervision has been lost. The confirmation of the loss of the supervision is given by a broken red icon in NES screen.





11.3 Measurement

11.3.1 How to read a Power Measurement file

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

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






11.4 Loopback

The functions described in this section allow to perform the test operations by loopbacks.In the Resource List Area are listed all the loopbacks which can be performed.In this area the following information is given:

1) Interface: the number of the channel and the type of the loopback2) Direction: the type of the loopback (Internal/Internal IF/External Line)3) Activation: the activation status of a loopback (Active/Not Active)4) Activation date: the date of loopback activation5) Timeout: the timeout period, if has been set.

This domain view consists of the following areas:

Resource Tree Area: displays the object on which the loopbacks can be performed, sorted by number.

Resource List Area: displays tabular information about the loopback supported by the resource selected in the tree area.

Resource Detail Area: displays, through tabbed windows, the properties done in list area. This area enable to perform the available functions for the involved resource.





11.4 Loopback

11.4.1 How to activate a loopback

[1] Before to activate the loopback (IF loopback) squelch the local transmitter, because the loopback is NOT “Loop and Continue” type.[2] Select the suitable loopback to be activated by clicking on the relevant object in the Resource Tree Area or by selecting the relevant row in the Resource List Area.[3] Select Active in the Activation field.[4] Click on Apply.[5] The Loopback is now ACTIVE (in the row in the Resource List Area the Activation field of the relevant loopback will change from Not Active to Active).

Note: In the Timeout Period field a timeout period can be set for the loopback activation (max. 4 days). At the end of this period the loopback will be automatically deactivated.





11.4 Loopback

11.4.2 How to remove a loopback

[1] Select the suitable loopback to be removed by clicking on the relevant object in the Resource Tree Area or by selecting the relevant row in the Resource List Area.[2] Select Not Active in the Activation field.[3] Click on Apply.[4] The Loopback is now DEACTIVATED (in the row in the Resource List Area the Activation field of the relevant loopback will change from Active to Not Active).[5] Remove the squelch of the local Transmitter.





12 Core-E view for Core-E and Ethernet domain





12 Core-E view for Core-E and Ethernet domain

12.1 Core-E domain

The Core-E domain multiple main view contains two tab-panels:Ethernet Physical InterfaceTMN Interface

Core-E Main view

This menu opens with a double click on the Core-E unit in the Equipment tab-panel.

This domain view consists of the following areas:

Resource Tree, displaying Ethernet physical interface with related port number;

Resource List, displaying tabular information about tributaries in tree area;

Resource Detail, providing access to Core-E detail view “Alarms” and “Settings”.





12.1 Core-E domain

12.1.1 Ethernet Physical Interface

This tab-panel refers to the 4 Ethernet ports, which can be used as traffic ports and includes two tab-panels:

Alarm tab-panelSettings tab-panel





12.1 Core-E domain

12.1.1 Ethernet Physical Interface [cont.]

This tab-panel refers to the Ethernet ports, which can be used as trafficports and includes two tab-panels:

Alarm tab-panelSettings tab-panel






12.1.1.1 Alarm tab-panel

“Alarm” view shows the Ethernet ports-related alarms. Selecting the node in Tree area allows checking Ethernet tributary alarms current state.






12.1.1.2 Settings tab-panel (for Ethernet Port#1 to Port#4)

The Settings view performs all the available functions for Ethernet tributary ports. Information related to a data port configuration is provided by the following parameters:

Port Status (Enabled or Disabled);Alarm Profile (not implemented);Auto-Negotiation Status (Enabled or Disabled);Flow Control (Enabled or Disabled);

N.B.: Only asymmetric pause capability can be configured to transmit pause frame but not receive pause frame on the Ethernet ports. If a pause frame is received on Ethernet ports such frame is dropped. Default values for manual mode are 100 Mbit/s, full duplex, pause disable

Configuration (“Other” / “Configuring” / “Complete” / “Disabled” / “Parallel Detect Fail”) all read-only;Advertised Capability, (“10 Mb/s – Half Duplex”, “10 Mb/s – Full Duplex”, “100 Mb/s – Half Duplex”, “100 Mb/s – Full Duplex”). The “Restart” button allows forcing auto-negotiation to begin link re-negotiation.VLAN configuration. The traffic, received on each user Ethernet port, can be untagged or tagged. For each port it is possible to configure:

Acceptable Frame Type: Admit tagged only (only tagged frames are allowed in ingress) Admit all (tagged and untagged frames are allowed in ingress)Default value: “Admit all”.

Port VLAN ID: if the Acceptable Frame Type is set to “Admit all” the VLAN-ID and Priority fields, to be added in ingress to untagged frames, must be configured. Only VLAN-ID values already defined (in the VLAN management menu) can be configured for this purpose. The Priority values allowed are in the range 0 - 7.The default Port VLAN-ID and Priority values are: VLAN-ID=1; PCP=0.When the Port VLAN-ID value is different from the default value, the relevant port is removed as member of the VLAN 1. N.B.: Untagged frames

The untagged frames received on one user Ethernet port, configured as “Admit tagged only”, are dropped. N.B.: Priority frames

The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as “Admit tagged only”, aredropped.The priority packets (VLAN-ID=0) received on one user Ethernet port, with the “Admit all” configuration enabled, aremanaged as untagged frames for VLAN-ID field, while the Priority field is the same of the received packets.






12.1.1.3 Settings tab-panel (for Ethernet Port#5)

The Settings view performs all the available functions for Ethernet tributary port#5. Information related to the port configuration is provided by the following parameters:

Port Status (Enabled or Disabled);Alarm Profile (not implemented);Auto-Negotiation Status (Enabled or Disabled);Flow Control (Enabled or Disabled);

N.B.: Only asymmetric pause capability can be configured to transmit pause frame but not receive pause frame on the Ethernet ports. If a pause frame is received on Ethernet ports such frame is dropped. Default values for manual mode are 100 Mbit/s, full duplex, pause disable

Configuration (“Other” / “Configuring” / “Complete” / “Disabled” / “Parallel Detect Fail”) all read-only;Advertised Capability, (“1000 Mb/s – Full Duplex”).Optical Info field: it is a read-only field not implemented in the current release. The “Restart” button allows forcing auto-negotiation to begin link re-negotiation.VLAN configuration. The traffic, received on each user Ethernet port, can be untagged or tagged. For each port it is possible to configure:

Acceptable Frame Type: Admit tagged only (only tagged frames are allowed in ingress) Admit all (tagged and untagged frames are allowed in ingress)Default value: “Admit all”.

Port VLAN ID: if the Acceptable Frame Type is set to “Admit all” the VLAN-ID and Priority fields, to be added in ingress to untagged frames, must be configured. Only VLAN-ID values already defined (in the VLAN management menu) can be configured for this purpose. The Priority values allowed are in the range 0 - 7.The default Port VLAN-ID and Priority values are: VLAN-ID=1; PCP=0.When the Port VLAN-ID value is different from the default value, the relevant port is removed as member of the VLAN 1. N.B.: Untagged frames

The untagged frames received on one user Ethernet port, configured as “Admit tagged only”, are dropped. N.B.: Priority frames

The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as “Admit tagged only”, aredropped.The priority packets (VLAN-ID=0) received on one user Ethernet port, with the “Admit all” configuration enabled, aremanaged as untagged frames for VLAN-ID field, while the Priority field is the same of the received packets.





12.1 Core-E domain

12.1.2 TMN Interface

This tab-panel refers to the TMN Interface. The interfaces are of two types:

1) TMN Ethernet on a dedicated connector2) Port #4 of the Ethernet traffic ports, which can be dedicated to TMN purpose and not to traffic.

This tab-panel has 2 tab-panels:

Alarm tab-panel

Settings tab-panel






12.1.2.1 TMN Ethernet port

If used, the TMN Ethernet must be:

Enabled.

Assigned an IP address with its IP mask.

Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also the area number.

Click on Apply to activate the selections.






12.1.2.2 Port #4 TMN Ethernet

If the Ethernet Port 4 has been used as TMN port, the port 4 must be:

Enabled.

Assigned an IP address with its IP mask.

Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also the area number.

Click on Apply to activate the selections.






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





End of ModuleOperator interface





Module 2Initial configuration

3JK Edition 1.00





9500 MPR · 9500MPR R 1.2.1 Operation and MaintenenceNE operation · Initial configuration3 · 2 · 2

Blank Page




Document History





Objectives

Objectives: to be able toConfigure the equipment starting from a scratched NE.





Objectives [cont.]






Table of Contents


1 Initial Configuration 71.1 General Requirements 81.2 Initial Turn-up 101.3 Enable Plug-In Cards 141.4 Provision Plug-In Cards 231.5 Provision Synchronization 371.6 Provision NTP protocol 421.7 Provision NE Time 431.8 Provision VLAN 441.9 Cross-connections 45

1.9.1 PDH-To-Radio 471.9.2 PDH (E1 Access Card) to ETH (Ethernet) 481.9.3 ETH (Ethernet) to RADIO (Modem Card) 491.9.4 RADIO (Modem Card) to RADIO (Modem Card) 50

1.10 Provision System 511.11 Provision Local NE IP Address 541.12 Provision TMN Ethernet Port 551.13 Provision Ethernet Port 4 for TMN (if required) 561.14 Provision IP Static Routing 571.15 Provision OSPF Static Routing 59

2 TCO suite – Provisioning tool 612.1 TCO Main menu 622.2 Provisioning Tool screens 632.3 Configuration Options Screen 662.4 Core-E Configuration 672.5 E1 configuration 692.6 Radio Provisioning 702.7 Synchronization Configuration 742.8 Cross Connections Configuration 752.9 802.1D management 812.10 802.1Q management 822.11 VLAN Management 842.12 Port VLAN Configuration 852.13 Network Configuration 862.14 Trusted Managers 882.15 Typical Report Panel 89











1 Initial Configuration






1.1 General Requirements

PC HW ConfigurationCPU: Pentium III 850 MHzRAM: 500MByte (minimum), 1 Gbyte (suggested)Min. disk space: 1,5 GByte (available space needed for log files, JRE excluded)Min. resolution: equal or higher than 1024x768 pixelCD-ROM Drive: 24xPrimary Interface: Ethernet Card 10/100 Mbit/sec.

Operating Systems SupportedMicrosoft Windows 32-bit versions: Microsoft Windows XP Professional servicepack 2, Windows Vista Ultimate.






1.1 General Requirements [cont.]

Additional requirementsMicrosoft Internet Explorer 6.0 6.0.2900.2180 SP1+ or higher, Microsoft InternetExplorer 7 7.0.5730.11C0 + or higher, Mozilla 1.7.10, Mozilla Firefox 2.0.0.12 or higher.Minimum HTML page size shown shall be 1024x768 pixels.Standard user can be used to run the applications but for TCO Suite usageAdministrator password is neededJRE (Java Runtime Environment) 6 Update 3Disable all Firewall software on used PC






1.2 Initial Turn-up

1 - Install software on PC.Before operating the user system interface (USI) for the first time, the programs contained on the CD ROM must be installed on the PC. The installation process configures the PC for its unique requirements and prepares it to run the program.

A - Insert CD ROM disk into PC.B - On Windows desktop, double click on My Computer icon. My Computer window displays.C - In My Computer window, click on CD ROM icon. Files window displaysD - Load Craft Terminal software on PC on a directory without blank spaces in the directory name.

2 - Turn on the 9500MPR.3 - Establish communication between equipment and Craft terminal computer. Default NE IP address: 10.0.1.24 – Startup

Follow the steps on following figures to open communication with the equipment.

Note: if it is necessary to scratch the MIB use the following procedure.

Database scratch procedure:1. Power off the equipment

2. Move the dip-switch 2 on the Core-E board.

3. Re-plug the Core-E board in the subrack.

4. When EC software starts, detects the switch position and starts with database scratch: all the configuration information will be erased (radio parameters, synch, XCONN, network, ecc). The informationof SWP is maintained (the stand-by and active SWP banks are not deleted).

5. It is possible to understand when the scratch procedure is over: make a “ping” towards NE with default IP address.

6. After this, plug-out the Core-E board and restore the original dip-switch 2 position.

7. Re-plug the Core-E board.

Note: Average time necessary to scratch the database (from SW start): 6-7 minutes.






1.2 Initial Turn-up [cont.]

Startup Procedure

See next slide

Click OK

Insert the NE IP address

Click Show

Click OK







Startup Procedure

When the startup procedure is over, Main Screen is displayed

Type in User Name

Type in Password

Click to start the loading process

Loading Performance MIB and other processes loading status.







5 - Provisioning MPR START

Enable Plug-In Cards

Provision Plug-In Cards

Provision Synchronization

Provision NE Time

Provision VLAN

Provision System

Provision IP/SNMP

Provision NTP Protocol

Provision Cross-Connections

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

See the figure for the recommended sequence.





Enabling SFP optical plug-in


1.3 Enable Plug-In Cards

Apply the Equipment Type

Click to start

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

Settings tab





Enabling Spare Core-E Card


1.3 Enable Plug-In Cards [cont.]

Click to start

Choose Core-E from the dropdown menu for the spare protected Core-E card in slot 2

Settings tab

Apply the Equipment Type

Display Profile Name selected on Alarm Severity Profile screen





Enabling E1 Access Card



Click to start

Choose the P32E1DS1 unit

Settings tab

Click to apply changes

In order to communicate to the microprocessor in the Core-E Card the slot number & type of board housed in the MSS, E1 Access Card and Radio Access Card have to be enabled.

This is accomplished on the Settings screen for that card. The Core-E Card in MSS slot 1 is always enabled. The ODU is enabled automatically when the associated Radio Access Card is enabled. The Fan Unit must be enabled.








Click to start

Choose the P32E1DS1 unit

Settings tab









Click to start

Select 1+1 EPS

Settings tab






Enabling Radio Access Card



Click to start

Settings tab


Choose the MD300 unit

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








Click to start

Settings tab

Click to apply changesChoose the MD300 unit









Click to start

Settings tab


Select the suitable protection scheme








Enabling Fan Unit

Click to start

Settings tab


Select the FANS






1.4 Provision Plug-In Cards

Core-E Card Provisioning (Ethernet ports 1-4)

Go to next page

Double left click






1.4 Provision Plug-In Cards [cont.]

Core-E Card Provisioning (Ethernet ports 1-4)

Check to enable the selector port. Uncheck to disable first in order to change any settings.

Current provisioning for Ethernet Ports #01-#04. Area updates when Apply buttons are clicked

Check to enable input and output pause features.

For the configuration refer to the Core-E unit.

B1

A3

C1

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.

A1

Check to enable NE auto-negotiation functions.

A2

Click this Apply button.B2

Click Apply button.A4







Core-E Card Provisioning (Ethernet port 5)

Go to next page

Double left click







Core-E Card Provisioning (Ethernet port 5)

Check to enable the selector port. Uncheck to disable first in order to change any settings.

Current provisioning for Ethernet Port #05. Area updates when Apply buttons are clicked.

Check to enable input and output pause features.

The Optical Info field is a read-only field not implemented in the current release.

Check to enable NE auto-negotiation functions.

Click this Apply button.

Click Apply button.For the configuration refer to the Core-E unit.







E1 Access Card Provisioning

Go to next page

Double left click







E1 Access Card Provisioning (TDM2TDM)

Apply the Flow ID number.

To enable the port select “Framed/ Unframed” and click on Apply

Choose TDM2TDM if radio is being used to transport E1 data only (no Ethernet).

Flow ID number required to transport E1 data. Enter any number between 2 and 4020.

Flow Id: To implement cross-connections between line side and radio side each E1 tributary must be associated to an identifier. Enter the Flow identifier value in the relevant field (possible values: 2 to 4080) and press Apply.







E1 Access Card Provisioning (TDM2ETH)

Apply the Flow ID number.

Flow ID number required to transport E1 data. Enter any number from Table 4-1 Valid Ranges.

Select Adaptive to synch TDM output to packets.Select Differential to synch TDM output to NE Synchronization source.

Choose TDM2ETH if radio is being used to transport just Ethernet or Ethernet plus E1 data.

Set ECID (Tx and Rx) values.







Access Card Details Select Disabled if port (E1 line) is not:– being used as a source or destination (typical choice for a line

not being used at a terminal or not being dropped and inserted at a repeater);

– being dropped or inserted (typical choice for a line being passed through at a through repeater and not being dropped and inserted at a drop and insert repeater).

Select Framed: to be able to collect the performances at the input in Tx side and at the output in Rx side.

Select Unframed:– being used as a source or destination (typical choice for a line

being used at a terminal);– being dropped or inserted (typical choice for a line being

dropped and inserted at a drop and insert repeater)

Signal Mode.Configures line format. Allows user to choose if line is dropped and inserted (by selecting Framed/Unframed) or passed through or not used (by selecting Disabled)







Radio Access Card Provisioning

Go to next page

Double left click







Operation without Adaptive ModulationMode. Select Presetting from dropdown list.

Reference. Displays reference channel spacing based on capacity and modulation. Select from dropdown list.

Modulation. Displays modulation scheme based on reference channel spacing and capacity. Select from dropdown list.

Capacity. Read Only Field.This is the nominal bit rate for quantity of E1 lines being used.

PPP RF. Check to enable PPPRF port. When not checked(disabled) user cannot change:• Routing IP Protocol• OSPF Area• Remote Address

Alarm Profile. Read Only Field. Displays Profile Name selected on Alarm Severity Profile screen.

Click to enable Open Shortest PathFirst protocol then select area name that has OSPF protocol. Select from dropdown list.

Check to enable radio ID mismatch function.

Enter number from 1 to 100 for receiver ID. Must match transmitter ID at other end of hop.

Enter number from 1 to 100 for transmitter ID. Must match associated receiver ID at other end of hop.







Shifter. Select TX (go) and RX (Return) separation frequency from the Shifter Data Help list.

Range. Displays range of TXRF frequencies that may beentered.

Tx Mute. Read Only Field.Status of Local Tx Mute function.

Alarm Profile. Displays ProfileName selected on AlarmSeverity Profile Screen.

Remote ATPC Rx Threshold.Default value is -55 dBm.

ATPC Power Range.

TX RF Frequency is automaticallyentered by ODU when ODU isconnected to MSS. If the ODU isnot connected to the MSS, enterthe TX RF frequency, withinallowed range.

Read Only Field.Displays RX RF frequency.Result of calculation:RX Freq - X Freq = Shifter Freq.

ATPC. Check to enable ATPC.

Note: When the Mode is changed from Presetting to Adaptive Modulation, the radio defaults to 14 MHz bandwidth at 4 QAM. If the capacity of the radio (number of E1 lines cross connected) exceeds the available capacity of a 14 MHz Channel at 4 QAM, Adaptive Modulation will not enable. It may be necessary to perform one of the following provisioning changes:

1.Reduce the quantity of E1 lines being transported to meet the required capacity.

2.Increase Reference Channel Spacing.







Operation with Adaptive ModulationMode.Select Adaptive Modulation from the drop down list.

Modulation Range.Displays modulation scheme based on the modulation mode. Select from the drop down list.

Remote Threshold (dB).The default level is 0, which corresponds to threshold. The operator can select switching levels above threshold (0 to +4 dB corresponding to threshold level +0 to 4 dB) or below threshold (0 to -2 dB) corresponding to threshold level -0 to 2 dB).

Reference Channel Spacing.Displays reference channelspacing based on themodulation mode and themodulation range. Select fromthe drop down list.

Reference Modulation.Modulation scheme used for path coordination. (normally worst case is used for path coordination).







Manual Operation.When checked, allows user to select and test a specific modulation scheme.

Current Modulation.Read Only Field. Displaysmodulation scheme the radiois currently using.

PPP RF.Check to enable PPP RF port. When not checked (disabled) user cannot change:• Routing IP Protocol• OSPF Area• Remote Address

Link Identifier Configuration.Check to enable radio IDmismatch function.

Expected Identifier.Enter number from 1 to 100for receiver ID. Must matchtransmitter ID at other end ofHop.

Forced Modulation.Select modulation scheme (one from the Modulation Range selected) to test. When activated by the Apply button, radio is forced to operate using selected modulation scheme.

Sent Identifier.Enter number from 1 to 100for Transmitter ID. Must match associated receiver ID at other end of hop.







Select TX (Go and RX (Return)separation frequency from thedropdown list.

Displays range of TX RF frequenciesthat may be entered.

Read Only Field.Displays Profile Name selectedon Alarm Severity Profile screen.

Read Only Field.Displays RX RF frequency.Result of calculation:RX Freq - TX Freq = Shifter Freq.

Check to enable the muting of Tx output power.

The Tx Power function allows the operator to select the transmitter output power of each modulation scheme. The default level is the expected output power. The minimum and maximum range of each modulation scheme is shown in parenthesis (min XX - max YY).

Read Only Field.Status of Local Tx Mute function.

TX RF Frequency is automatically entered by ODU when ODU is connected to MSS. If the ODU is not connected to the MSS, enter the TX RF frequency, within allowed range.






1.5 Provision Synchronization

All 9500 MPR radios in the network must be synchronized to the same clock. One radio in the network is provisioned as Master. All other radios in the network must be provisioned as Slave. The slave radios are all synchronised to the clock provided by the master.

Normal OperationDuring normal operation, the master can be provisioned to get sync clock from two separate sources: an internal local oscillator (most common source) or external clock from customer provided equipment. The slave radios can be provisioned to receive the sync clock from one of two sources: clock recovered by the radio receiver or the sync clock from another radio in the network. Normally at a repeater, the sync clock is received over the RF path and recovered by the radio receiver. A typical slave terminal uses the clock from an adjacent radio. See following figures for typical master terminal provisioning and for typical slave terminal provisioning.

Failed Primary OperationWith the exception of the master when the radio is provisioned to sync off the local oscillator, the provisioned secondary sync source is enabled if the primary source fails. When the master, provisioned to accept sync clock at the Core-E from an external source, fails, the internal free-running local oscillator is enabled. Provisioning choices for the secondary source for slave radios depend upon the choices made from the primary source.

Sync SwitchingWith the exception of the master when the radio is provisioned to sync off the local oscillator, the sync clock source is switched from primary to secondary if the primary source fails. Sync clock switching provisioning is dependent on the role of the radio in the network (master or slave) and on user preference. A revertive switching feature is a provisioning option that restores the sync clock to the original source when the alarm on the primary source is cleared. If revertive switching is not selected, the secondary sync source continues to provide sync clock, and if the secondary source fails, must be manually switched to the primary source.






1.5 Provision Synchronization [cont.]

Provisioning Master with Free Run Local Oscillator as Primary Source

Go to next page







Provisioning Master with Free Run Local Oscillator as Primary Source

From to previous page







Provisioning Slave with Radio Port as Primary Source

Go to next page







Provisioning Slave with Radio Port as Primary Source

From to previous page






1.6 Provision NTP protocol

Enable the NTP (Network Time Protocol).

Put a check mark in the NTP protocol field to enable the protocol and write in the Main Server addressfield the IP address of the server, which is in charge to distribute the time to all the NEs in the network. In the Spare Server address field write the IP address of the Spare Server, if any.

The Server reachability field is a read-only field, which shows the reachability of the NTP servers. The following information can appear:

"Main server reachable"

"Spare server reachable"

"None servers reachable"

"Both servers reachable"

Click on Refresh to update the screen.

Click on Apply to send to the NE the NTP Configuration.






1.7 Provision NE Time

NE Time Provisioning

When checked, enables function to synchronize Operating System and Network Equipment Times.

Click to display pop-up dialog for NE Time configuration.

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






1.8 Provision VLAN

To provision VLAN refer to S3-M1 chapter 3.6.






1.9 Cross-connections

The cross connections screen is used to configure switching of packetized data through the Core-E Card. Using this screen, the operator can switch:

E1 ports (lines) from/to an E1 Access Card (PDH) to/from a Modem Card (RADIO) and/or any of four Ethernet (ETH) ports on the Core-E Card.Ethernet (ETH) data from/to an external source to/from a Modem Card (RADIO) and/or to/from an E1 Access Card (PDH).

Valid Cross Connections:PDH -to- RADIOPDH -to ETHETH -to- RADIORADIO -to- RADIO






1.9 Cross-connections [cont.]

Go to next page

Click to open Cross Connections Screen






1.9.1 PDH-To-Radio

Double left click anywhere on line to open line select dialog box

E1 line(s) 1-32 you want transported

Click to PDH box (source) and drag line to radio box (destination)

Flow ID required to transport

The following rules and guidelines apply to switching E1 ports 1 through 32 on the E1 Access Card through the Core-E Card to the Radio Modem Card. Follow the steps to cross-connect E1 lines to Radio.

1. The license key installed on the Core-E Card determines the number of E1 ports that can be cross connected.

2. The E1 Access Card (E1 source) and Radio Modem Card (destination) must be Enabled on the respective card provisioning screens.

3. Each E1 port to be cross connected must be Enabled on the E1 provisioning screen.

4. Each E1 port to be cross connected must have a Flow ID number assigned to it on the E1 provisioning screen. Refer to Flow ID number rules.

5. The Flow ID number check box on the cross connections screen must be checked for each E1 port to be cross connected.






1.9.2 PDH (E1 Access Card) to ETH (Ethernet)

The following rules and guidelines apply to switching E1 ports 1 through 32 on the E1 Access Card through the Core-E Card to the Ethernet ports 1 through 4. Follow the steps to cross-connect PDH to ETH.

1. The license key installed on the Core-E Card determines the capacity of the Ethernet data that can be cross connected.

2. The Ethernet port (source) and E1 Access Card (destination) must be Enabled on the respective Core-E Card and E1 Access Card provisioning screens.

3. The Service Profile on the E1 Access Card Settings screen must be set to TDM2ETH for each E1 cross connected.

4. A Flow ID number must be assigned to each E1 cross connected on the E1 Access Card Settings screen. Refer to the Flow ID number rules.

5. The Ethernet port to be cross connected must have a Flow ID number assigned to it on the Ethernet provisioning screen. Refer to the Flow ID Number rules.

6. The Flow ID number check box on the cross connections screen must be checked for each Ethernet port to be cross connected.

7. The MAC Address of the Ethernet equipment connected to the Ethernet connectors on the Core-E card must be entered on the pop up.






1.9.3 ETH (Ethernet) to RADIO (Modem Card)

The following rules and guidelines apply to switching Ethernet ports 1 through 4 on the Core-E Card to the Modem Card. Follow the steps to cross connect Ethernet to Radio.

1. The license key installed on the Core-E Card determines the Ethernet data capacity that can be cross connected.

2. The Ethernet port (source) and Modem Card (destination) must be Enabled on the respective Core-E Card and Modem Card provisioning screens.

3. The Service Profile on the E1 Access Card Settings screen must be set to TDM2ETH for each E1 cross connected.

4. A Flow ID number must be assigned to each E1 cross connected on the E1 Access Card Settings screen. Refer to the Flow ID number rules.

5. The Ethernet port to be cross connected must have a Flow ID number assigned to it on the Ethernet provisioning screen. Refer to the Flow ID Number rules.

6. The Flow ID number check box on the cross connections screen must be checked for each Ethernet port to be cross connected.

7. The MAC Address of the Ethernet equipment connected to the Ethernet connectors on the Core-E Card must be entered on the pop up.






1.9.4 RADIO (Modem Card) to RADIO (Modem Card)

The following rules and guidelines apply to switching Modem Card to Modem Card (such as a through repeater). Follow the steps to cross-connect Radio-to-Radio.

1. The license key installed on the Core-E Card determines the Ethernet data capacity that can be cross connected.

2. Each Modem Card must be enabled.

3. Capacity of Modem Cards on Settings screens must match.






1.10 Provision System

System Setting

Go to next page

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





System Setting


1.10 Provision System [cont.]

1) Tributary Port ConfigurationThis field allows to set the suitable impedance of the E1 stream (Unbalanced 75 ohms/Balanced 120 ohm). To activate the new impedance, click on Apply.

2) Quality Of ServiceThis field allows to set the suitable Quality Of Service (Disabled/DiffServ/802.1p). To activate the new value, click on Apply.

The Ethernet switch provides a Quality of Service mechanism to control all streams. If the QoS is disabled, all traffic inside the switch has the same priority; this means that for each switch port there is only one queue (FIFO) therefore the first packet that arrives is the first that will be transmitted.

The following values are available:

IEEE std 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag. If the tag is present the correspondent priority is assigned to the packet;

DiffServ: each packet is classified based on DSCP field in the IP header to determine the priority.

3) DHCP

The DHCP server configures automatically IP address, IP mask and default gateway of the PC Ethernet interface used to reach the NE. The PC must be configured to get automatically an IP address.

The DHCP server uses an address pool of only one IP address, defined according to the NE Ethernet port IP address:

NE Ethernet port IP address plus one, if this address is not a direct broadcast address,

otherwise NE Ethernet port IP address minus one.

The IP mask is set to the mask of the NE local Ethernet port and the default gateway is set to the NE IP address. The lease time is fixed to 5 minutes.

To activate the DHCP server, select Enabled and click on Apply.






1.10 Provision System [cont.]

11 12

4) Admission Control for Adaptive ModulationThe Admission Control for TDM flows (cross-connected to radio direction working in Adaptive Mod-ulation) can be enabled or disabled. Default: “Enabled”.

When the Admission Control is "Enabled", the check is performed taking into account the capacity of the 4 QAM modulation scheme for the relevant Channel Spacing.

When the Admission Control is "Disabled", the check is performed taking into account the capacity of the highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-16-64 QAM range or 16 QAM for 4-16 QAM range).

Warning: The disabling of the Admission Control can be done in 1+0 configuration only.

5) Event and Alarm LogAs default the Logging is enabled. If set to "Disabled" the events are not sent to the Event Log Browser application.

6) NE MAC AddressThis field is a read-only field, which shows the MAC address of the NE. This MAC address must be used in the cross-connection with TDM2Eth profile.






1.11 Provision Local NE IP Address

Local Configuration Provisioning

Click to display pop-up dialog for the IP Configuration.

Enter NE IP address

Apply the IP Address.






1.12 Provision TMN Ethernet Port

Double click on the front panel of the Core-E unit in the Equipment menuSelect the TMN Ethernet Select the Setting tab-panel

Enable TMN Ethernet

Enter IP address.

Select Static Routing for manual routing. Select OSPF (Open Shortest Path First protocol) for automatic routing.

Enter IP Mask and click on Apply.

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






1.13 Provision Ethernet Port 4 for TMN (if required)

Double click on the front panel of the Core-E unit in the Equipment menuSelect the Port #4 TMN EthernetSelect the Setting tab-panel

Enable the TMN Port 4

Enter IP address

Select Static Routing for manual routing. Select OSPF (Open Shortest Path First protocol) for automatic routing.

Enter IP Mask and click on Apply.






1.14 Provision IP Static Routing

IP Static Routing Provisioning

Go to next page

Click to display pop-up dialog for IP Static Routing Configuration

Follow the steps to provision.






1.14 Provision IP Static Routing [cont.]

IP Static Routing Provisioning

Route to a specific IP address.

Enter IP address.

IP Mask.

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.

List of RF path directions.Click to view drop down list.

Create new or change existing IP static routes.






1.15 Provision OSPF Static Routing

OSPF Static Routing Provisioning

IP Static Routing Configuration screen. Click to display pop-up dialog for OSPF Area Configuration

Follow the steps to provision Open Shortest Path First (OSPF) protocol static (automatic) routing.





Blank Page






2 TCO suite – Provisioning tool






2.1 TCO Main menu

Open Java runtime environment and start provisioning






2.2 Provisioning Tool screens

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






2.2 Provisioning Tool screens [cont.]

Opening screen with off-line operation

The buttons present in this screen has the following meaning:

Open: allows opening an existing MCML (XML-based) configuration file. MCML file can contains NE configuration data and it can be used to fill panels fields and data.

Get: not operative.

Create: allows to create a new configuration file.

Prev: not operative.

Cancel: not operative.

Help: by clicking on this button the operator calls the help on line.

By clicking on the "Open" button a window opens, which gives the possibility to open a configuration file created in 1.1.0 version or in 1.0.0 old version. If a 1.0.0 configuration file is open a new screen appears, which asks to convert the file from 1.0.0 to 1.1.0.

By clicking on the "Create" button it will be possible to create a file in 1.1.0 version or in the 1.0.0 old version.

After opening a configuration file, the user will see a configuration preview in order to understand, for example, if the file is correct and contains the wanted configuration. Click "Next" button from such preview panel or "Create" button.






2.2 Provisioning Tool screens [cont.]

Opening screen with the connection to the NE

The buttons present in this screen has the following meaning:

Open: allows opening an existing MCML (XML-based) configuration file. MCML file can contains NE configuration data and it can be used to fill panels fields and data.

Get: this button is operative if you are physically connected to the NE and it is used to upload the configuration from the NE to the tool.

Create: allows to create a new configuration file.

Prev: not operative.

Cancel: not operative.

Help: by clicking on this button the operator calls the help on line.

By clicking on the "Open" button a window opens, which gives the possibility to open a configuration file created in 1.1.0 version or in 1.0.0 old version. If a 1.0.0 configuration file is open a new screen appears, which asks to convert the file from 1.0.0 to 1.1.0.

By clicking on the "Create" button it will be possible to create a file in 1.1.0 version or in the 1.0.0 old version.

After opening a configuration file, the user will see a configuration preview in order to understand, for example, if the file is correct and contains the wanted configuration. Click "Next" button from such preview panel or "Create" button.






2.3 Configuration Options Screen

The screen below is a generic one that depicts all of the pull-down options possible depending on which card is selected in the card slot. Protections options shown below are for all cards. See the screens shown below for more information.

Protections options for the Core-E cards

Protections options shown for Slot 3 and Slot 4

Protections options shown for Slot 5 and Slot 6






2.4 Core-E Configuration

Ethernet Icon

E1 Access Card Icon

Radio Access Card Icon

When checked this feature enables input and output pause features

Check to enable auto negotiation

Check to enable the selected port

Check to allow communication at data rate but in only one direction at a time.

Check to allow communication at data rate in both directions at the same time.

Note:

A white icon indicates that there are no cross-connections, but cross-connections can be created.

A blue icon indicates the destination is full. The limits granted by the license key have been exceeded. A message is also displayed stating that no more E1 ports will be accepted.

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






2.4 Core-E Configuration [cont.]

Priority forwarding disabled.

The Quality Of Servicefeature enables priority forwarding in the Core-E Card switch based on how the packets are tagged: not tagged or tagged 802.1p or DiffServ. For general traffic, the packets are not tagged and QOS can be disabled. The user has to know if the packets are tagged, and if tagged 802.1p or DiffServ in order to know which QOS function to chose.

Each packet is based on DSCP field in IP header to determine priority.

Each packet is classified based on presence of valid 802.1p user priority tag.

Select Transport if ETH Port 4 on the Core-E Card is used to transport Ethernet data.

Select TMN if ETH Port 4 on the Core-E Card is used for SNMP data.

Check to enable the optical SFP plug-in

Note:

A white icon indicates that there are no cross-connections, but cross-connections can be created.

A blue icon indicates the destination is full. The limits granted by the license key have been exceeded. A message is also displayed stating that no more E1 ports will be accepted.

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






2.5 E1 configuration

Select Unbalance 75 Ohm if tributary cable is coax.

Select Balance 120 Ohm if tributary cable is twisted pair.

Choose TDM2TDM if radio is being used to transport E1 data only (no Ethernet).

Choose TDM2ETH if radio is being used to transport just Ethernet or Ethernet plus E1 data.

Flow ID is unique to network. No two Flow IDs in a network can be the same.

Tx Over-the-hop ID

Rx Over-the-hop ID. Must match Rx/Tx ID at other end.

The purpose of TMN Clock Source provisioning is to select the mode that will be used to sync TDM E1 data to the node Synchronization source. The user can select one of three modes: Adaptive, Differential, and TDM_Line_In. Select Adaptive to sync TDM output to packets. Select Differential to sync TDM output to NE Synchronization source.






2.6 Radio Provisioning

Radio Configuration Screen (without Adaptive Modulation)

Select Revertive feature if you want traffic on the protection channel to automatically switch back to the main channel when alarms clear or a switch command is released.

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


Enter number from 1 to 100 for Transmitter ID. Must match associated Transmitter ID at other end of hop.

Enter number from 1 to 100 for Receiver ID. Must match associated Receiver ID at other end of hop.

No check mark here.

Select the modulation scheme.

Select the suitable reference channel spacing.






2.6 Radio Provisioning [cont.]

Select TX (Go) and RX (Return) separation frequency from drop-down list.

Select the modulation schemeEnter the Tx RF

frequency within the allowed range.

Check to enable ATPC.

Enter the ATPC parameters.

Enter the Tx Power

No check mark here.







Radio Configuration Screen (with Adaptive Modulation)

Select Revertive feature if you want traffic on the protection channel to automatically switch back to the main channel when alarms clear or a switch command is released.

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


Enter number from 1 to 100 for Transmitter ID. Must match associated Transmitter ID at other end of hop.

Enter number from 1 to 100 for Receiver ID. Must match associated Receiver ID at other end of hop.

Enter the Tx Power (see Note 2).

Check mark to enable the Adaptive Modulation (see Note 1).

Note 1: With the Adaptive Modulation the only available configuration is: 1+1 HSB.

Note 2: The operator The operator can modify only the 4 QAM field. In this field the operator has to enter the constant power, which will be used with 4 QAM modulation. The power range is shown on the right side and depends on the selected reference mode.

The same power value will be used by the 16 QAM and 64 QAM modulation schemes.







Select TX (Go) and RX (Return) separation frequency from drop-down list.

Enter the TxRF frequency within the allowed range.

Check mark to enable the Adaptive Modulation.

Select in the Scheme field the Modulation range (4/16 QAM or 4/16/64 QAM) to be used by the Adaptive Modulation.

Select in the Reference Channel Spacing field the suitable channel spacing.

Select in the Reference Mode field the spectral efficiency class to be set as reference.

Select in the Thresholds field how many dB the switching thresholds have to be moved from the default value (+4 dB/-2 dB). The default value is approx. 6 dB below the 10-6 Rx threshold.





2 TCO suite –Provisioning

2.7 Synchronization Configuration

Synchronization Role. Master or Slave.

Revertive - Switches sync source back to primary source after alarm on primary source clears.

Non-Revertive - Does not switch back to primary source after primary alarm clears and stays on secondary sync source.

Synch-Out Port Configuration -Connector that can be used to provide sync to another radio or ancillary equipment.

Synch-In Port -SClock from external source received on the Sync In connector on the Core-E card.

Any Available E1 -Clock from E1 source via E1 peripheral.

Free Run LocalOscillator - Local oscillator on Core-E Card. Normal Master primary sync source.





2 TCO suite – Provisioning

2.8 Cross Connections Configuration

Radio Access Card icon. A white icon indicates the source/destination is unavailable. Check to make sure the card is enabled.

White ETH icons: A white icon indicates the source/destination is unavailable. Check to make sure the card is enabled.Blue ETH icons: A blue icon indicates the destination is full. The limits granted by the license key have been exceeded. A message is also displayed stating that no more E1 ports will be accepted.Green ETH icons: A green icon indicates that the source and destination are available and the destination can accept more E1 ports.






2.8 Cross Connections Configuration [cont.]

Black Line: E1 to Radio connection. Click on this line to display the popup window shown below.

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







Black Line: E1 to Radio connection.

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







Blue Line: E1 to Ethernet connection.

The purpose of TMN Clock Source provisioning is to select the mode that will be used to sync TDM E1 data to the node Synchronization source. The user can select one of three modes: Adaptive, Differential, and TDM_Line_In. Select Adaptive to sync TDM output to packets. Select Differential to sync TDM output to NE Synchronization source. Select TDM_Line_In to sync TDM output to TDM input. Click now for more details.

Enter MAC address of link partner (External Ethernet Equipment).

Rx Over-the-hop ID. Must match Rx/Tx ID at other end.

Tx Over-the-hop ID.

Flow ID is unique to network. No two Flow IDs in a network can be the same.








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













2.9 802.1D management

When the NE is configured in this mode (default configuration), the Ethernet traffic is switched according to the destination MAC address without looking the VLAN. The packets from the user Ethernet ports having the VLAN ID out the allowed range (0 and 2-4080) are dropped. The packets having a VLAN ID already used for a TDM flow are accepted.






2.10 802.1Q management

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

VLAN 1 Management VLAN-ID 1 is automatically defined by the NE when the 802.1Q bridge type is selected. VLAN-ID 1 is shown to the operator, but it can-not be neither changed nor deleted. All the user Ethernet ports (enabled and dis-abled) and all the radio ports are members of the VLAN 1. In egress VLAN-ID 1 is always removed from all the ports.






2.10 802.1Q management [cont.]

ADD VLan: to create a new VLAN (refer to VLAN management figure)

EDIT VLan: to change the parameters of a VLAN (VLAN name, VLAN member ports, VLAN untagged ports in egress).

DEL VLan: to delete a VLAN-ID. It is possible to remove a VLAN-ID from the VLAN-ID table even if this VLAN-ID has been already configured on one or more user ports as Port VLAN to be added in ingress to untagged frames. As consequence, the VLAN-ID=1 and PRI=0 are added to the untagged frames received on this port. Before applying this deletion, a confirmation of the operation is shown to the operator.

By clicking Next the Port VLancon-figuration screen opens






2.11 VLAN Management

[1] VLAN ID field: Enter the VLAN ID (the configurable values must be in the range 2 - 4080)

N.B.: The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) can-not be used.

[2] VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.

N.B.: There is no check on unambiguity name.

[3] VLAN Ports field: Select the ports members of this VLAN by putting a check mark on the relevant check box. All the user Ethernet ports and all the Radio directions can be considered. Both enabled and disabled user Ethernet ports (radio ports when declared are implicitly enabled) can be member of a VLAN. This means that a disabled port can be configured as a member of a VLAN and a port already member of a VLAN can be disabled continuing to be a member of the same VLAN.

[4] Untagged Ports field: Select, among the ports belonging to this VLAN (members), the untagged ports (in egress the VLAN will be removed from the frames). Only the user Ethernet ports, enabled and disabled, are manageable. The VLAN cannot be removed from the radio ports (with the exception of the VLAN 1).

N.B.: The VLAN-ID values allowed are in the range 2 - 4080. By default, for the VLAN IDs defined, all the ports are members and the Untag flag is set to “False”, which means all the frames are trans-mitted with Tag.

N.B.: Tagged frames If one tagged packet with VLAN-ID X is received on a port which is not member of the VLAN-ID X, the packet is dropped.






2.12 Port VLAN Configuration

Admit tag frames only (only tagged frames are allowed in ingress)

Admit all frames (tagged and untagged frames are allowed in ingress)

Port VLAN ID and Priority: if the Acceptable Frame Type is set to “Admit all frames” the VLAN-ID and Priority fields, to be added in ingress to untagged frames, must be configured. Only VLAN-ID values already defined (in the VLAN management menu) can be configured for this purpose. The Priority values allowed are in the range 0 - 7.The default Port VLAN-ID and Priority values are: VLAN-ID=1; PCP=0.When the Port VLAN-ID value is different from the default value, the relevant port is removed as member of the VLAN 1.

Note: The Port VLan Configuration screen opens only if in the Bridge Configuration screen the 802.1Q (Virtual Bridge) has been selected.






2.13 Network Configuration

Select Static Routing for manual routing. Select OSPF (Open Shortest Path First Protocol) for automatic routing.

Enter IP Address for radio.

Enable TMN VLAN feature on Core-E.

Enter local IP Address.






2.13 Network Configuration [cont.]

Displays status (Enabled when checked) of NTP Protocol provisioning on NTP Server Configuration screen.

Displays the IP address of the Main NTP server entered as Main Server address on the NTP Server Configuration screen.

Displays the IP address of the Spare (standby) NTP server entered as Spare Server address on the NTP Server Configuration screen.






2.14 Trusted Managers

The Manager Type cannot be changed (it is fixed tp 5620 SAM)

The default UDP Port is 5010, but with a click on this column another port can be configured

To remove a manager select the manager from the list and clik on Remove Manager(s).The multiple selection of different managers can be done to remove more than one manager in one shot.

To activate a trusted manager click on Add Manager, then click on the IP Address column and write the IP address of the SNMP manager.To confirm the selection click Enter.

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






2.15 Typical Report Panel

Buttons: Prev: the procedure goes back to the previous step

Save: allows to save the configuration file

Apply: it is operative only if you are physically connected to the NE and it activates the download of the configuration to the NE

Cancel: the procedure goes back to step 1 (Opening screen)





Exercise

Configure completely the NEs of the training center by following the procedure given in this section.





Blank Page






End of ModuleInitial configuration





Module 3Performance monitoring

3JK Edition 1.00





9500 MPR · 9500MPR R 1.2.1 Operation and MaintenenceNE operation · Performance monitoring3 · 3 · 2

Blank Page




Document History





Objectives

Objectives: to be able toactivate and evaluate the Performance Monitoring application.





Objectives [cont.]






Table of Contents


1 Performance Monitoring Tool 713.1 Introduction 813.2 Core-E unit performances 10

13.2.1 Ethernet Aggregate Rx Table 1113.2.2 Ethernet Aggregate Tx Table 14

13.3 MD300 unit performances 1713.3.1 Current Data Table 2013.3.2 CD parameters 2313.3.3 CD counters 2413.3.4 History Data Table 2513.3.5 HD counters 2613.3.6 Threshold tables 2713.3.7 How to create a new threshold table 2813.3.8 How to change/delete a threshold table 2913.3.9 Threshold table association 3013.3.10 Adaptive Modulation performance 3113.3.11 Ethernet Aggregate Tx Table 3413.3.12 Ethernet Aggregate Per Queue 36

13.4 P32E1DS1 unit performances 3913.4.1 Incoming (Current Data Table) 4013.4.2 CD parameters 4313.4.3 CD counters 4413.4.4 Incoming (History Data Table) 4513.4.5 HD Counters 4613.4.6 Outgoing (Current Data Table) 4713.4.7 CD parameters 5013.4.8 CD counters 5113.4.9 Outgoing (History Data Table) 5213.4.10 HD Counters 5313.4.11 Threshold tables 5513.4.12 How to create a new threshold table 5613.4.13 How to change/delete a threshold table 5713.4.14 Threshold table association 58

13.4.14.1 One-Shot Threshold association 5913.4.14.2 Specific E1 Port # association 6013.4.14.3 Specific E1 Port # Incoming or Outgoing 61

Exercise 63Exercise 64Blank Page 65End of Module 66











1 Performance Monitoring Tool






13.1 Introduction

To open the Performance Monitoring tool click on the relevant icon in the Menu bar as shown in the next figure.

The Performance Monitoring tool allows to display all the performances available on the units of MPR:

Core-E unit MD300 unit P32E1DS1 unit






13.1 Introduction [cont.]

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

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






13.2 Core-E unit performances

Two groups of Performance Monitoring are available:

Ethernet Aggregate Rx Table (incoming side)

Ethernet Aggregate Tx Table (outgoing side)






13.2.1 Ethernet Aggregate Rx Table

To activate the Rx performances (Incoming side):

1) Select the Ethernet Aggregate Rx Table row as shown in the next figure.

2) Select the Interval (the collection time of the performances): 4, 6, 30, 60 seconds. The default value is 4 sec.

3) Select the Duration of the performance monitor in hour and minutes. The max. duration is 24 hours.

4) Click on the Start button to start the monitoring.






13.2.1 Ethernet Aggregate Rx Table [cont.]

To display the performance monitor select the suitable port (port #2 in the example).

The available performances at port level are:

TRCO: total number of octects of Ethernet frames received by the Virtual Ethernet Interface, including Ethernet header characters.

TRCF: total number of Ethernet frames received by the Virtual Ethernet Interface.

TRSEF: total number of errored frames.

TDF: total number of Ethernet frames which were chosen to be discarded due to buffer congestion.

TRCF Unicast: total number of Ethernet Unicast frames received correctly by the Virtual Ethernet Interface.TRCF Multicast: total number of good packets received that were directed to a multicast address. This number does not include packets directed to the broadcast address.

TRCF Broadcast: total number of good packets received that were directed to the broadcast address. This number does not include multicast packets.

The performances are displayed in two different formats:

graphical format in the lower part

tabular format in the upper part

In the graphical format by putting a check mark on the check box only one (or more than one or all) performance can be displayed.






13.2.1 Ethernet Aggregate Rx Table [cont.]

By selecting the Ethernet Aggregate Rx Table all the performances regarding all the enabled Ethernet ports are shown in tabular format.






13.2.2 Ethernet Aggregate Tx Table

To activate the Tx performances (Outgoing side):

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









13.2.2 Ethernet Aggregate Tx Table [cont.]

To display the performance monitor select the suitable port (port #2 in the example).

The available performances at port level are:

TTO: total number of octets of Ethernet frames transmitted out by the Interface, including Ethernet header characters.

TTF: total number of Ethernet frames transmitted out by the interface.

TDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer congestion.

TRCF Unicast: total number of Ethernet Unicast frames transmitted out by the Virtual Ethernet Interface.

TRCF Multicast: total number of good packets transmitted by this address that were directed to a multicast address. This number does not include packets directed to the broadcast address.

TRCF Broadcast: total number of good packets transmitted by this address that were directed to the broadcast address.




In the graphical format by putting a check mark on the check box only one (or more than one or all) performance can be displayed







By selecting the Ethernet Aggregate Tx Table all the performances regarding all the enabled Ethernet ports are shown in tabular format.






13.3 MD300 unit performances

By selecting the MD300 unit the screen in Figure opens.






13.3 MD300 unit performances [cont.]

The counters supported are the following:Errored SecondsSeverely Errored SecondsBackground Block ErrorUnavailable Seconds

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

Quality of service PM is performed in accordance with G.826 and G.784.

It has assumed that the quality of the single tributary (E1, ...) can be derived from the quality of the aggregate signal, therefore no dedicated quality of service Performance Monitoring is foreseen on the single tributaries.

Considering one section, one current register is for 15 min report and one for 24 h report; 96 history data can be stored for 15 min report and 8 history data for 24 h report.

Two different radio sections can be monitored:

Radio Hop Section: the section between two radio stations inside the protection section.

Radio Link Section: the section identifying the protected section.

Note: The 15 min Performance Monitoring data are stored in the History Data report only if errors have been occurred. The 24 h Performance Monitoring data are always stored in the History Data report. .






13.3 MD300 unit performances [cont.]

The performance reports can be of 2 different types: 15 minutes 24 hours

The following description explains the functions to provide the Performance Monitoring process with a granularity period of 15 min. The same functions are provided for 24h Performance Monitoring process. The Performance Monitoring are of HOP or LINK type. HOP refer to Performance Monitoring before the RPS switch. LINK refer to Performance Monitoring after the RPS switch. The current report can be seen (and configured) and the history log can be seen.






13.3.1 Current Data Table

To see (and configure) the Current Data report:

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

2) Click on the Start button in the Tool bar.






13.3.1 Current Data Table [cont.]

Refer to Figure to see an example of the Current Data display.






13.3.1 Current Data Table [cont.]

Refer to Figure to see the Alarm Data tab panel to see the alarms regarding the performances, if any.






13.3.2 CD parameters

The fields displayed in the upper part of the screen allow the operator to check and manage the parameter of the current data collection.

Suspect interval shows whether the current data are suspect or not (Note).Elapsed Time field (read-only) displays the elapsed time in the current interval of monitoring.Last Update: display time of the PM in the graphical description and in thetabular description in the upper part of the screen. By pressing the Refreshbutton this time changes.Max Interval supp.: max. number of intervals (reports) which can be suppressed in the History because they don’t have errors.Num. Interval supp.: number of intervals (reports) suppressed in the History because they don’t have errors.

Note: An interval is defined as “Suspect” if at least one of the following conditions occurs in the collection period:

the elapsed time deviates more than 10 seconds of the nominal time

loss of the PM data in the equipment

performance counters have been reset during the interval.






13.3.3 CD counters

BBE (Background Block Error)

ES (Errored Second)

SES (Severely Errored Second)

UAS (Unavailable Second)

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






13.3.4 History Data Table

Refer to Figure to open the History Data Table.

To see an History Data report:

1) Click on the desired granularity (15 m or 24 h) on the History Data Table below the HOP channel (0 or 1) (in 1+0 configuration channel 1 only) to see the HOP report or click on LINK to see the LINK report.

The Performance Monitoring process monitors the parameters during a specified interval (i.e. 15min) and stores their values in history data. A History Data collection is created automatically at the end of each time interval of Current Data.

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






13.3.5 HD counters

BBE (Background Block Errors)

ES (Errored Second)








13.3.6 Threshold tables

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

There are two default threshold tables for LINK: Threshold #1 (to be associated to 15 min report) and Threshold #3 (to be associated to 24 h report).






13.3.7 How to create a new threshold table

Note: Four threshold tables can be created for the HOP (Threshold #2, #3, #5 and #6). Two threshold tables can be created for the LINK (Threshold #2 and #4).

To create a new threshold table:

1) Click on Threshold Tables HOP (or LINK) node tree. The Threshold Data Creation screen will appear, as shown in the next figure (Hop threshold).

2) Write the values for the Low and High thresholds.

3) Click on Create. Automatically the new threshold takes a name with a progressive number.






13.3.8 How to change/delete a threshold table

1

2

3

Note: Only the created thresholds can be modified or deleted. The default thresholds can be only displayed.

1) Click on the Threshold to be modified/deleted in Threshold node tree (Threshold #3 in the example of the figure).

2) Low and high thresholds for each counter are shown. Edit the new values in the table fields to change them.

3) Click on the Apply button to confirm the changes or click on the Delete button to delete the threshold.






13.3.9 Threshold table association

To each Performance Monitoring can be associated a Threshold Table.

To associate a Threshold Table click on Current Data Table or History Data Table of HOP-Channel#0 (or Channel#1) or of LINK. The 15min&24h tab panel will appear.

In the Counter Thresholds field select the threshold to be associated and click on Apply.






13.3.10 Adaptive Modulation performance

If the Adaptive Modulation has been enabled in the Modem unit, in the Performance Monitoring tool will appear also the performances regarding the Adaptive Modulation: these performances show the time during which a specific modulation scheme has been active.

To activate the Adaptive Modulation performance:

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







13.3.10 Adaptive Modulation performance [cont.]

Figure shows a display of Current Data report (15 min).

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






13.3.10 Adaptive Modulation performance [cont.]

Figure shows a display of History Data report (15 min).







13.3.11 Ethernet Aggregate Tx Table

To activate the Tx performances (Outgoing side):

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










Refer to figure to see the performances.

The available performances at output Tx radio port are:

TTO: total number of octets of Ethernet frames transmitted out by the Interface, including Ethernet header characters.

TTF: total number of Ethernet frames transmitted out by the interface.

TDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer congestion.




In the graphical format by putting a check mark on the check box only one (or more than one or all) performance can be displayed.






13.3.12 Ethernet Aggregate Per Queue

The MD300 unit has 8 output queues.

Queue 8 is reserved to TDM2TDM traffic.

Queue 7 is reserved to TDM2Eth traffic.

Queue 6 is reserved to TMN traffic.

The remaining 5 queues are reserved to Ethernet traffic. Queue 5 is the highest priority queue.

To activate the Ethernet Aggregate Per Queue performances (Outgoing radio side):

1) Select the Ethernet Aggregate Per Queue row as shown in the next figure.









13.3.12 Ethernet Aggregate Per Queue [cont.]

To display the performance monitor select the suitable queue (Queue #1 in the example).

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

TCF: total number of Ethernet conforming frames accepted and transmitted out by the specific queue of the interface.

Discard TCF: total number of Discarded Ethernet conforming frames accepted by the specific queue of the interface.

TCO: total number of Ethernet conforming octects accepted and transmitted out by the specific queue of the interface.




In the graphical format by putting a check mark on the check box only one (or more or all) performance can be displayed.






13.3.12 Ethernet Aggregate Per Queue [cont.]

By selecting the Ethernet Aggregate Per Queue row all the performances regarding all the queues are shown in tabular format.






13.4 P32E1DS1 unit performances

By selecting the P32E1DS1 unit the screen opens.

The performance monitoring (PM) gives indication on the quality of the E1 streams, which have been configured as "Framed".In Figure the E1 streams, configured as "Framed" are shown in bold; for all the other E1 streams (in grey) the performance are not available because the relevant streams are disabled or they have been configured as "Unframed".Two types of performances are available:

Incoming: these performances are detected at the input in Tx side.Outgoing: these performances are detected at the output in Rx side.

Note: 9500MPR is transparent regarding the E1 stream. The CRC is used to detect the quality of the E1 stream; it is never changed.The Quality is performed in accordance with G.826 and G.784. The performance reports are of 2 different types:

15 minutes 24 hours

One current register is for 15 min report and one for 24 h report; 96 history data can be stored for 15 min report and 8 history data for 24 h report.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. Note: For a better quality in the Performance Monitoring it is recommended to start up to 128 E1 PM counters on the same NE. This means 4 counters (Incoming 15 Minutes, Incoming 24 hours, Outgoing 15 Minutes and Outgoing 24 Hours) for 32 E1 streams. Note: Stability measurement on Ethernet counters (with duration from few hours to 24 Hours) should be performed by selecting an high value (60 seconds) as collection time of the performances (refer to parameter Interval in Ethernet Aggregate Tx Table section).The following description explains the functions to provide the Performance Monitoring process with a granularity period of 15 min. The same functions are provided for 24h Performance Monitoring process.






13.4.1 Incoming (Current Data Table)


1) Click on the desired granularity (15 m or 24 h) on the Current Data Table. Refer to the next figure.


3) Click on Refresh button to update the collection.






13.4.1 Incoming (Current Data Table) [cont.]

Example of the Current Data display






13.4.1 Incoming (Current Data Table) [cont.]

To see the Alarm Data tab panel to see the alarms regarding the performances, if any.








Suspect interval shows whether the current data are suspect or not (Note). Elapsed Time field (read-only) displays the elapsed time in the current interval of monitoring. Last Update: display time of the Performance Monitoring in the graphical description and in the tabular description. This time changes after the Auto Refresh. Max Interval supp.: max. number of intervals (reports) which can be suppressed in the History because they don’t have errors. Num. Interval supp.: number of intervals (reports) suppressed in the History because they don’t have errors.



loss of the Performance Monitoring data in the equipment







13.4.3 CD counters


ES (Errored Second)



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






13.4.4 Incoming (History Data Table)

To see an History Data report: 1) Click on the desired granularity (15 m or 24 h) on the History Data Table.








13.4.5 HD Counters


ES (Errored Second)








13.4.6 Outgoing (Current Data Table)


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


3) Click on Refresh button to update the collection.






13.4.6 Outgoing (Current Data Table) [cont.]

Example of the Current Data display






13.4.6 Outgoing (Current Data Table) [cont.]

To see the Alarm Data tab panel to see the alarms regarding the performances, if any.








Suspect interval shows whether the current data are suspect or not (Note). Elapsed Time field (read-only) displays the elapsed time in the current interval of monitoring. Last Update: display time of the Performance Monitoring in the graphical description and in the tabular description. This time changes after the Auto Refresh. Max Interval supp.: max. number of intervals (reports) which can be suppressed in the History because they don’t have errors. Num. Interval supp.: number of intervals (reports) suppressed in the History because they don’t have errors.



loss of the Performance Monitoring data in the equipment







13.4.8 CD counters


ES (Errored Second)



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






13.4.9 Outgoing (History Data Table)

To see an History Data report: 1) Click on the desired granularity (15 m or 24 h) on the History Data Table.








13.4.10 HD Counters


ES (Errored Second)








13.4.10 HD Counters [cont.]

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

1) Click on PDH. The One-Shot Start/Stop PM panel will appear.

2) Select the E1 Port #.3) Select the Signal type.

4) Select the Interval type.

5) Click on Start.






13.4.11 Threshold tables

This section describes how to display or change or create the threshold tables assigned to Performance Monitoring counters. To view the available threshold for Performance Monitoring process, the operator must select the Thresholds Tables node tree.There are two default threshold tables:

Threshold #1 (to be associated to 15 min report) Threshold #4 (to be associated to 24 h report).






13.4.12 How to create a new threshold table

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

To create a new threshold table:

1) Click on the Threshold Tables. The Threshold Data Creation screen will appear, as shown in the figure (E1 threshold).

2) Write the values for the Low and High thresholds.

3) Click on Create. Automatically the new threshold takes a name with a progressive number.






13.4.13 How to change/delete a threshold table

Note: Only the created thresholds can be modified or deleted. The default thresholds can be only displayed.

1) Click on the Threshold to be modified in Threshold node tree (Threshold #2 in the example of the figure).

2) Low and high thresholds for each counter are shown. Edit the new values in the table fields to change them.

3) Click on the Apply button to confirm the changes or click on the Delete button to delete the threshold.







To each Performance Monitoring can be associated a Threshold Table.To associate a Threshold Table to an E1 stream three methods can be used:

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






13.4.14.1 One-Shot Threshold association

To associate a Threshold Table:

1) Click on E1 Threshold. The One-Shot Threshold Apply panel will appear.

2) Select the E1 Port #.3) Select the the threshold to be associated to the 15min and/or 24h performance interval .

4) Click on Apply.






13.4.14.2 Specific E1 Port # association


1) Click on the E1 Port #. The 15min&24h tab panel will appear.

2) In the Counter Thresholds field select the threshold to be associated and click on Apply.






13.4.14.3 Specific E1 Port # Incoming or Outgoing

Threshold association (Incoming)


1) Click on the E1 Port #. The 15min&24h tab panel will appear.

2) In the Counter Thresholds field select the threshold to be associated and click on Apply.






13.4.14.3 Specific E1 Port # Incoming or Outgoing [cont.]

Threshold association (Outgoing)





Exercise

Using the test link described in the following slide, do the following steps:

1. Enable Performance Monitoring on the NE A and B to monitor the quality of the path connecting the two Test Instruments

2. Using the variable attenuator, simulate a link degradation and display the current and the historical collected data





Exercise

BATest Instr.

Operator 1 Operator 2

VARIABLEATTENUATOR

Test Instr.





Blank Page






End of ModulePerformance monitoring





Module 1Fault management

3JK Edition 1.00

Section 4Maintenance




9500 MPR · 9500MPR R 1.2.1 Operation and MaintenenceMaintenance · Fault management4 · 1 · 2

Blank Page




Document History





Objectives

Objectives: to be able toperform the troubleshooting of the 9500 MPR.





Objectives [cont.]






Table of Contents


1 Fault Management 71.1 Troubleshooting 8

1.1.1 Before Going to Site Checklist 91.1.2 Troubleshooting Basics 111.1.3 Troubleshooting Path Problems 27

1.1.3.1 Path Problems on a Commissioned Link 281.1.3.2 Path Problems on a New Link 30

1.1.4 Troubleshooting Configuration Problems 311.1.5 Troubleshooting Ethernet Problems 33

1.2 MSS Card removal and replacement 371.3 ODU removal and replacement 39

End of Module 40












1 Fault Management





1 Fault Management

1.1 Troubleshooting

This section provides guidance on:Before Going to Site ChecklistTroubleshooting BasicsTroubleshooting Path ProblemsTroubleshooting Configuration Problems Troubleshooting Ethernet Problems





1.1 Troubleshooting

1.1.1 Before Going to Site Checklist

Where possible, before going to site obtain the following information:Does the fault require immediate attention? Determine who is the best-placed person to attend the fault.Confirm the nature and severity of the reported fault, its location, 9500 MPR type, frequency band, high/low end ODU, capacity, modulation andconfiguration (nonprotected, protected, diversity). Ask:

Is just one 9500 MPR link affected, or a number of links in the same geographical area?Is the path down completely or is traffic passing but with a BER alarm?Is only one or a number of tributaries affected?Could the fault be in the equipment connected to 9500 MPR, rather than in 9500 MPR? Are there alarms on other, connected equipment?Is it a hard or intermittent fault?Do alarms confirm which end of an alarmed link is faulty?Could the weather (rain, ice, high wind, temperature) be a factor in the reported fault?

Note: If the fault suggests a rain fade or other weather related fade condition and it matches the prevailing weather conditions, do not take any action until the weather abates.





1.1 Troubleshooting

1.1.1 Before Going to Site Checklist [cont.]

Does link history suggest any fault trends? Does the fault history for the link indicate a likely cause?Is the 9500 MPR link newly installed?Has there been any recent work done on the link?

Ensure that you have with you: Appropriate spares. Where an equipment failure is suspected, these should include replacement cards/plug-ins and ODU. If an ODU is suspected then local/national climbing safety requirements must be adhered to.A laptop PC loaded with Craft Terminal, and an Ethernet connection cable. (You need the 9500 MPR IP address and also the addresses for any remote sites to be accessed).If login security has been enabled, you need the 'engineer' password for the local and also any remote sites to be accessed.Any special test equipment that may be needed, such as a BER tester.Toolkit.Key(s) for access to the site.





1.1 Troubleshooting

1.1.2 Troubleshooting Basics

Check front-panel LED indications. These provide summary alarm indications, which can help narrow down the location and type offailure.

Where a Status LED on a plug-in is off (unlit), but power to the MSS is confirmed by LEDs on other plug-ins, check the seating of the affected plug-in.

Check Main Screen. When logging into 9500 MPR with Craft Terminal, the opening screen is the Main Screen. Use the information provided to check for severity and problem type. Refer to table Alarm Matrix for probable cause and recommended action.

This section provides general guidance on 9500 MPR troubleshooting.





1.1 Troubleshooting

1.1.2 Troubleshooting Basics [cont.]

Table Alarm Matrix

continue

MinorMinorMinorPPP IP Fail

Check link partner and cable between link partner and ETH 4 connector

No Ethernet input signaldetected on ETH 4 on Core-E Card

MinorMinorMinorLOS on ETH TMN Interface

Provision cardCard in slot is not provisioned (enabled)

MinorMinorN/AUnconfiguredEquipment

Install Core-E Card in slot

Core-E card is missing from slot

MinorMinorN/ACard Missing

Install correct configured card

Card in slot does not match card configured in Core-E memory

MinorMinorN/AEquipment Mismatch

Replace Core-E CardCore-E card failedMinorMinorMajorCard FailCore-E Card

1+1 FD1+1 HS1+0ActionMost Probable Cause

Configuration/AlarmAlarm DescriptionEquipment





1.1 Troubleshooting


continue

Install correct flash card for license

Wrong flash card installed on Core-E Card

MajorMajorMajorLicense Mismatch for Equipment Provisioned

Check sync source for errors

Sync clk errors detected at Sync in port on Core-E Card

MinorMinorMinorDegraded Signal on Sync Interface

Check sync source and cable between sync source and Sync in port

No sync clk detected at Sync in port on Core-E Card

MinorMinorMinorLOS on Sync Interface

Wait for downloading to complete

Status of downloadMinorMinorMinorFirmware Download In Progress

Check link partner and cable between link partner and ETH 1-4 connector

Loss of Ethernet is detected on ETH 1-4 on Core-E Card

MinorMinorMajorLOS on Gigabit ETH Interface

Core-E Card







1.1 Troubleshooting


continue

Check for upstream E1 source for errors

AIS detected by the receive circuits on one or more E1 lines, indicating upstream failure

MajorMajorMajorAIS on PDH Tributary (RX)

Check E1 sourceErrors on input signal detected on any one or more of 32 lines

MinorMinorMinorDegraded Signal

Check E1 source and/or cable

No E1 input signal detected on any one or more of 32 lines

MinorMinorMajorLOS on PDH Tributary

Enable cardCard is not Enabled on the Settings screen

MajorMajorMajorUnconfiguredEquipment

Install E1 Access Card in slot

E1 Access Card is missing from slot

MinorMinorMajorCard Missing


Card in slot does not match Card configured in Core-E memory

MinorMinorMajorEquipment Mismatch

Replace E1 Access Card

Failure of E1 Access CardMinorMinorMajorCard FailE1 Access Card







1.1 Troubleshooting


continue

1. Verify sync provisioning at both ends of hop2. Replace alarmed E1 Access Card2. Troubleshoot sync problem between local and farend

Packet overflow causingbuffer spill. Could be caused by sync problem or E1 Access Card circuit failure

MajorMajorMajorJitter Buffer Overrun

1.Check/troubleshoot farend alarms2.Replace alarmed E1 Access Card

Packets are not being received by the emulation circuits

MajorMajorMajorLoss of CESoETH Frame

Check E1 sourceAIS detected on one or more E1 lines at input to PDH 32xE1 Access Card

MajorMajorMajorAIS on PDH Tributary (TX)

E1 Access Card







1.1 Troubleshooting


continue


Status of downloadMinorMinorMinorFirmware Download In Progress

E1 Access Card

Enable fan unitUnit is not Enabled on the Settings screen

MinorMinorMinorUnconfiguredEquipment

Install fan unitFan unit is missing from slot

--MajorCard Missing

Replace fan unitFan failed--MajorCard Fail

1.Verify sync provisioningat both ends of hop2.Replace alarmed E1 Access Card3.Troubleshoot sync problem between local and farend

Buffer spill. Could be caused by sync problem or E1 Access Card circuit failure

MajorMajorMajorJitter Buffer Underrun

Fans Unit







1.1 Troubleshooting


continue

Check/repair IF cable connection on alarmed Radio Access Card

Bad cable connection at IF in/out connector on Radio Access Card

MinorMinorMajorMSS-ODU Cable Loss

Enable cardCard is not Enabled on the Settings screen

MinorMinorMinorUnconfiguredEquipment

Install Radio Access Card in slot

Radio Access Card is missing from slot

MinorMinorMajorCard Missing


Card in slot does not match card configured in Core-E memory

MinorMinorMinorEquipment Mismatch

Replace radio Access Card

Radio Access Card failedMinorMinorMajorCard FailRadio Access Card







1.1 Troubleshooting


continue

1.Replace main Radio Access Card2.Replace protect Radio Access Card3.Replace main ODU4.Replace protect ODU

Delay between main and protect RF paths detected

MinorMinorN/ALoss of Alignment

1.Switch far-end XMTRs(in a protected system). If alarm clears, replace far-end off-line Radio Access Card.2.Check/troubleshoot far-end alarms3.Replace alarmed Radio Access card

Far-end equipment problems, RF path problems, or local circuit failures have caused BER to increase to the point that frames are being lost

MinorMinorMinorLoss of Radio Frame

Radio Access Card







1.1 Troubleshooting


continue

No action is required at this time. Monitor receive signal for increased degrading

10E-9 BER detectedMinorMinorN/AEarly Warning

1.Verify RF path is clear, antenna is aligned, and no existing weather-related problems2.Verify RSL is above Receiver threshold. If not – check upstream

Bit Error Rate threshold (10E-4) exceeded on Receiver input circuits on modem

MinorMinorMajorHigh BER

Replace Radio Access Card

Internal receive circuit failure

MinorMinorMajorDemodFunction Fail

Radio Access Card







1.1 Troubleshooting


continue

Set numbers at both ends of hop to match

Link identifier number provisioned on Radio Access Card settings screen is different from link identifier number provisioned at other end of hop

MajorMajorMajorLink Identifier Mismatch

1.Switch far-end XMTRs(in a protected system).If alarm clears, replace far-end off-line Radio Access Card2.Check/troubleshoot far-end alarms3.Replace alarmed Radio Access Card

Loss of ATPC command path between far-end XMTR and local RCVR

MinorMinorMinorATPC LoopRadio Access Card







1.1 Troubleshooting


continue

1.Switch farend XMTRs(in a protected system). If alarm clears, replace farendoff-line Radio Access Card

10 consecutive SES (unavailable time period) detected on main Radio Access Card

MajorN/AN/AUAT on Radio Link

Alarm threshold exceeded on standby Radio Access Card after switching from main to standby

MinorN/AMajorTCA on Radio Hop

1.Switch far-end XMTRs(in a protected system). If alarm clears, replace far-end off-line Radio Access Card

Alarm threshold exceeded on standby Radio Access Card

MajorN/AN/ATCA on Radio Link

Radio Access Card



TCA – Threshold Crossing Alarm

UAT – Un-Available Time





1.1 Troubleshooting


continue

Replace Radio Access Card with correct card

Modem card type does not match card type stored in memory on the Core-E Card flash card

MajorMajorMajorLicense Mismatch for Equipment Provisioned

1.Replace Radio Access Card

Bit errors have increased and have exceeded degraded signal threshold

MinorMinorMinorDegraded Signal

1.Replace Radio Access Card

Loss of sync clock detectedMinorMinorMinorLOS on Sync Interface


Download statusMinorMinorMinorFirmware Download In Progress

10 consecutive SES (unavailable time period) detected on standby Radio Access Card after switching from admin to standby

MinorN/AMajorUAT on Radio Hop

Radio Access Card



TCA – Threshold Crossing Alarm

UAT – Un-Available Time





1.1 Troubleshooting


continue

Re-configure shifter value

Configured shifter value not supported by ODU

MinorMinorMajorShifter Frequency Mismatch

ODU

Re-configure TX power value

Configured TX power value not supported by ODU

MinorMinorMinorTX Power Mismatch

Re-configure frequencyFrequency out-of-range of configured TX frequency

MinorMinorMajorRF Frequency Mismatch

Replace ODUODU RCVR circuit failedMinorMinorMajorRCV Function Fail

Replace ODUODU does not match ODU configured in Core-E memory

MinorMinorMajorEquipment Mismatch

Replace ODUODU failedMinorMinorMajorCard Fail







1.1 Troubleshooting



Download statusMinorMinorMinorFirmware Download In Progress

1.Replace ODU2.Replace alarmed Radio Access Card

Loss of communication with ODU

MinorMinorMinorODU Not Responding

Download correct software version

Software version on ODU does not match software version on Core-E

MinorMinorMinorSoftware Mismatch

ODU







1.1 Troubleshooting


Check the basics first. For example, if multiple alarms are present, and these include power supply voltage or hardware alarms, always check their cause before looking at resultant down-stream path failure or path warning (signal) alarms.Similarly, if a path-related failure is indicated (no hardware or software alarms), investigate the path. Go to the Craft Terminal History screen (15 minute view), to check supporting data, such as low RSL and incidence of intermittent pre-failure BER alarms, which if present are evidence of a path-related failure. Refer to Troubleshooting Path Problems for more information.

Check if symptoms match the alarm. Alarms reflect the alarm state, but in exceptional circumstances an alarm may be raised because of a failure to communicate correctly with the alarm source, or a failure in alarm management processing. Always check to see if symptoms match the alarm, using LED indications and the Craft Terminal.





1.1 Troubleshooting


Check if recent work may be a cause. Recent work at the site may be a cause or contributing factor. Check for a configuration change, software upgrade, power recycling (reboot), or other site work:

Many hardware alarms are only initiated as a loss-of-communications alarm during a reboot, software upgrade, or reconfiguration. By not being able to communicate with the Core-E, their settings cannot be loaded. The fault may be at the hardware device (most likely), communications to it, or the Core-E.Hardware/software compatibility alarms will be raised when a new plug-in is installed that needs a later version of 9500 MPR software.Hardware incompatible alarms will be raised when a plug-in is installed in a slot that has been configured for a different plug-in.

MSS before an ODU. If there is doubt about whether a fault is in the MSS or ODU, always replace the MSS first; it is quicker and easier.Hot-pluggable. MSS cards are hot-pluggable. There is no need to power-down before replacing, but traffic will be lost unless the plug-in is protected.Plug-in restoration time. Ensure adequate time is allowed for services to resume when a plug-in is replaced.





1.1 Troubleshooting

1.1.3 Troubleshooting Path Problems

A path-related problem, with the exception of interference, is characterized by traffic being similarly affected in both directions. Generally, if you are experiencing only a one-way problem, it is not a path problem.

Normally a path problem is signalled by a reduced RSL, and depending on its severity, a high BER.Only in worst case situations, such as an antenna knocked out of alignment, will a path fail completely, and stay that way.For weather-related problems, such as rain or ducting, the path problem willdisappear as the weather returns to normal.

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






1.1.3.1 Path Problems on a Commissioned Link

A path problem on an existing link, one that has been operating satisfactorily may be caused by:

Weather-related path degradationIf BER alarms are fleeting / not permanent and RSL returns to its normal, commissioned level after the alarm is cleared, rain, diffraction, or multipath fading is indicated. Rain fade is the likely cause of fade for links 13 GHz and higher. Diffraction and multipath/ducting for links 11 GHz and lower. If these alarms are persistent, there could be a problem with the link design or original installation.

Changed antenna alignment or antenna feed problemIf RSLs do not return to commissioned levels after a period of exceptionally strong winds, suspect antenna alignment.Also, check the antenna for physical damage, such as may occur with ice-fall. For a remote-mounted ODU, check its antenna feeder.

New path obstructionWhere all other parameters check as normal, and the path has potential for it to be obstructed by construction works, view/survey the path for possible new obstructions.






1.1.3.1 Path Problems on a Commissioned Link [cont.]

Interference from other signal sourcesInterference usually affects traffic in just one direction. Unlike other path problems, RSL is not affected. If suspected, check for new link installations at, or in the same geographical area, as the affected site. Ultimately, a spectrum analyzer may have to be used to confirm interference, which is not an easy task given the need to connect directly to the antenna port, after removing the ODU.






1.1.3.2 Path Problems on a New Link

For a new link, potential problems can extend to also include:Incorrect antenna alignment

One or both antennas incorrectly aligned. Refer to Installation alignment procedure.Mismatching antenna polarizations

Given a typical polarization discrimination of 30 dB, for most links it is not possible to capture a signal to begin the antenna alignment process.

Incorrect path calculationsIf the RSLs are too low or too high, antenna alignment is correct, and Tx power settings are correct, check the path calculations used to determine the link performance. A good calculation match is +/- 2 dB. Disagreements in excess of 3 dB should be investigated.

ReflectionsReflection (path cancellation) problems may not have been picked up at the path planning stage, particularly if the survey was a simple line-of-sight. If suspected, resurvey the path.





1.1 Troubleshooting

1.1.4 Troubleshooting Configuration Problems

Configuration problems should only occur during the set up of a new link, or reconfiguration of an existing link. The more common problems may be broadly categorized as:

Compatibility problemsThe two alarms that may activate are Configuration Not Supported, and SW/HW Incompatible:

Configuration Not Supported: The plug-in installed is not enabled or is incorrect for the configuration.SW/HW Incompatible: Typically raised when new hardware is plugged into an existing MSS that has software from an earlier release. To remove the alarm, compatible 9500 MPR software is required; install the latest software.

Incorrect circuit connectionsNo alarms are activated for incorrect circuit connections. An incorrect assignment means the expected end-to-end circuit connectivity will not happen. Re-check circuit assignments for all nodes carrying the lost circuit(s)Take extra care when configuring ring circuits.Where the problem is not obvious, use the tributary loopback BER test to track a single circuit through a 9500 MPR network, beginning at the node closest to the node applying the BER test.





1.1 Troubleshooting

1.1.4 Troubleshooting Configuration Problems [cont.]

Incorrect ID naming, and commissioningAll traffic-carrying circuits must have a unique flow ID for the cross-connect capability to operate.

Incorrect/incompatible trib settingsTrib line interface settings incorrect, or line levels incompatible. While no alarm activates for an incorrect setting, its effect may result in ine levels being too low (LOS alarm), or too high, resulting in a high BER.

ATPC settingsEnsure ATPC settings are correct, specifically that the target fade margin allows adequate headroom for local Tx power, while ensuring an adequate fade margin.





1.1 Troubleshooting

1.1.5 Troubleshooting Ethernet Problems

The most common Ethernet problems are network and connectivity related and therefore always check the following first:

Verify link partner capability, provisioning, and connectionVerify radio provisioning matches link partnerVerify cabling between radio and link partner

The LEDs on the Core-E Card front panel for each Ethernet connector are a good indicator of correct connectivity and activity on theEthernet port.

This section gives general guidance on troubleshooting problems related to the four Ethernet ports on the Core-E Card.

Refer to table “Troubleshooting Ethernet Problems” on next slides for detail troubleshooting using the LEDslocally at the alarmed site.





1.1 Troubleshooting

1.1.5 Troubleshooting Ethernet Problems [cont.]

continue

1.Check local Ethernet provisioning screen.2.Check link partner provisioning.

Loss of Ethernet RCV/radio XMT signal in. Most probable causes:1.Cable between link partner and radio is disconnected/broken.Connect/repair cable.2.Speed/Mode provisioning mismatch between link partner and radio

Green LEDNot Lit

ETH IN LOS

Corrective ActionProbable CauseIndicationLED





1.1 Troubleshooting


Loss of Ethernet XMT/radio RCV signal out. Most probable causes:

Green LEDNot Lit

ETH OUT LOS

Check local RSL screen on CT. Is RSL ok?Yes - Check farend for Ethernet alarm.No - Check farend Tx output. Is farend Tx Out ok?Yes - Check path, antenna, waveguide/cablingNo - Check/replace farend radio Access Card.

1.Loss of RF input to radio Access Card

Check farend for Ethernet alarms.Are any alarms indicated?Yes - Troubleshoot farend alarmsNo - Check farend Ethernet status. Is only abnormal status indicated?Yes - Troubleshoot farend Ethernet status.No -1.Replace local alarmed Core-E Card. 2.Replace local radio Access Card.

2.Loss of Ethernet input to radio Access Card

Corrective ActionProbable CauseIndicationLED





1.1 Troubleshooting


In order for the green Link LED to light:1 - Cable must be connected to Ethernet port2 - Ethernet port must be enabled (provisioned Enabled on Core-E Settings Screen)3 - Speed and mode (on Core-E Settings Screen) must be provisioned the same as the link partner.

The yellow LED opposite the green on the connector indicates activity only. The flashing yellow LED is not an indicator of signal type or quality.





1 Fault Management

1.2 MSS Card removal and replacement

Never install, change or remove a card without first connecting to the shelf with an ESD grounding cable. Failure to do so may cause ESD damage to the cards.Plug-ins must be withdrawn and inserted using their finger-grip fastener/pulls. Never withdraw or insert using attached cable(s). Pulling on the cables may damage the cable, plug-in connector, and/or plug-in card connector attachment.When installing a plug-in, ensure its backplane connector is correctly engaged before applying sufficient pressure to bring the plug-in panel flush with the front panel. Improper alignment can result in damaged pins on the backplane con-nector and/or damage to the plug-in connector.

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





1 Fault Management

1.2 MSS Card removal and replacement [cont.]

All slots must be filled with either a peripheral plug-in card or a blank panel. Failure to do so will compromise EMC integrity and cooling air from the fan.Use extreme caution when connecting or disconnecting the ODU cable on the Radio Access Card. The shelf battery voltage is present on the center conductor of the connector. When removing or replacing a radio Access Card, withdraw the card from the shelf before disconnecting the cable to the ODU. Failure to follow these cautions may cause arcing and/or possible power spikes that could affect traffic on other links installed at the node.Removing an in-service card in an unprotected link will cause loss of traffic. Removing an in-service card in a protected link requires switching the traffic onto the standby (protection) channel.





1 Fault Management

1.3 ODU removal and replacement

Get a spare unit with the same P/N.Disconnect the MSS-ODU cable.Change the ODU.Reconnect the MSS-ODU cable.Check with the CT that there are no alarms.

Note for 1+1 configurations:

before replacing the ODU make sure that the traffic is transmitted over the other channel. Otherwise, force with the CT the traffic onto the other channel.





End of ModuleFault management





Module 2Software download

3JK Edition 1.00

Section 4Maintenance




9500 MPR · 9500MPR R 1.2.1 Operation and MaintenenceMaintenance · Software download4 · 2 · 2

Blank Page




Document History





Objectives

Objectives: to be able todownload a new software version.





Objectives [cont.]






Table of Contents


1 Software download menu 7Server Access Configuration 8Init Software Download 9Software Status 10End of Module 12












1 Software download menu





An FTP server can be used to speed up the software download to the NE.This menu allows to configure an FTP server on which the previously loaded software will be downloaded.Copy the SW file present in the software CD on the FTP server.

Server access configuration screen


Server Access Configuration

User Id and Password are the login information to access the FTP server.

In the Address field write the IP address of the FTP server.

In the Port field write the port to be used and in the Root Directory field write the FTP server directory name from which the software can be downloaded.

By clicking on the Set Default button, the server access values will be filled in automatically with the default configuration.

The CT is the default FTP server with the following parameters:

User Id: anonymous

Password: -

Address: local host IP address.

Port: 21

Root Dir: /

N.B. the System Default can be changed by writing different values in the fields and then by clickingon button OK.





Init Software Download screen


Init Software Download

To start download select the desired software version and click on the Init download button.The Forced check box can be used to force download (i.e. the complete description file is downloaded to the NE).

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

Using this menu, software is downloaded to the NE in order to upgrade the NE software version.

Note: If the Forced download is not selected, the system will compare the software to be downloaded with the software present in the NE and will proceed with the download operation only if the versions are different.

The Add button must be used to display another software file (extension DSC) in this screen to be then downloaded.

The Delete button must be used to delete a software file in this screen.

NOTE

This screen displays the software packages previously stored.

Recommended operation: Before starting the software download it is recommended to disable theATPC operation (if it has been enabled) and to set in RTPC mode the max.Tx power.





Software Status screen


Software Status

By clicking on the Software Unit Status button a software unit status screen opens (see on the next page) and gives additional information on the software package.

This menu gives the information of the software installed in the NE.

The following information is displayed:

Name: software name

Version: software version

Operational state: enabled or disabled

Current status: committed or standby

The committed status refers to the software currently in use

The Flash Card, which stores the NE software, contains 2 banks.

The 2 banks can store 2 different software versions. One bank will be committed (active) and theother bank will be standby.

NOTE The second bank appears when a new software package has been downloaded the first time.

During download, necessary to update the software version, the download file is automatically stored in the standby bank.

To activate the new version first check the operational status of the standby bank. If the status is enabled(this means that download took place without errors) select Activation or Forced Activation in the Software Management Action field and click on the Apply Action button.

By selecting Forced Activation the bank to be activated is forced to restart.

By selecting Activation the bank to be activated restarts only if the content of the two banks differ.





Software Units Details screen


Software Status [cont.]

The following information is displayed on the screen:

EC: software on the Equipment Controller

OC_R: software on the ODU Controller (Radio)

FDUFF, FCERE, FGUIN: FPGA firmware version

MDPAR: firmware version of the FPGA involved in the MSS/ODU communication channel





End of ModuleSoftware download

@@COURSENAME - Page 1All Rights Reserved © Alcatel-Lucent @@YEAR

All Rights Reserved © Alcatel-Lucent @@YEAR

@@COURSENAME@@PRODUCT1

Last But One Page



@@COURSENAME - Page 2All Rights Reserved © Alcatel-Lucent @@YEAR

All rights reserved © Alcatel-Lucent @@YEARPassing on and copying of this document, use and communication of its

contents not permitted without written authorization from Alcatel-Lucent

9500MPR R 1.2.1 Operation and Maintenance

Documents

alcatellucent equipment

rights reserved alcatellucent

trademarks of alcatel

prior consent of alcatel

trade marksalcatellucent

information purposes

terms of use

current information