twt42025-r4.0-sg1-sen-i2.0

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0

http://slidepdf.com/reader/full/twt42025-r40-sg1-sen-i20 1/1149

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

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

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



TERMS OF USE AND LEGAL NOTICE

Alcatel-Lucent provides this training course to you subject to these Terms of Use and Legal Notice. Your use of this trainingcourse and/or this site constitutes your acceptance of and agreement to these Terms of Use and Legal Notice. These

Terms of Use and Legal Notice, as well as the contents of this training course, may be updated or amended by Alcatel-Lucent from time to time without prior notice to you. Your use of the Alcatel-Lucent training materials after such update oramendment constitutes your acceptance of and agreement to said updated or amended Terms of Use and Legal Notice.

SAFETY WARNING

Alcatel-Lucent training materials can be for products or refer to products that have both lethal and dangerous voltagespresent. Always observe all safety precautions and do not work on the equipment alone. The user is strongly advised notto wear conductive jewelry while working on the products. Equipment referred to or used during this course may beelectrostatic sensitive. Please observe correct anti-static precautions.

PERMISSION TO USE CONTENT

The information, communications, scripts, photos, text, video, graphics, music, sounds, images and other materialsprovided in this training course (collectively the "Content"), is intended for the lawful use of employees of Alcatel-Lucentand other authorized participants in this Alcatel-Lucent training course. You are hereby granted a non-exclusive, non-

transferable permission to access and use the Content solely for your personal training and non-commercial use. Thispermission may be terminated by Alcatel-Lucent at any time for any reason or no reason, with or without notice. You mustimmediately cease use of the Content upon such termination.

COPYRIGHTS AND TRADEMARKS

The unauthorized copying, displaying or other use of any Content from this training course is a violation of the law and Alcatel-Lucent’s corporate policies. The Content is protected in France, the U.S. and other countries by a variety of laws,including but not limited to, copyright laws and treaty provisions, trademark laws, patent laws and other proprietary rightslaws (collectively, "IP Rights"). In addition to Alcatel-Lucent’s IP Rights in the Content, in part and in whole, Alcatel-Lucent,and any of the third parties who have licensed and/or contributed to the Content, owns a copyright in the formatting andpresentation of the Content.

Alcatel-Lucent does not grant you any permission to use the Content other than the permission expressly stated in theseTerms of Use and Legal Notice. All other use of Content from this training course, including, but not limited to, modification,publication, transmission, participation in the transfer or sale of, copying, reproduction, republishing, creation of derivativeworks from, distribution, performance, display, incorporation into another training course or presentation, or in any otherway exploiting any of the Content, in whole or in part, for uses other than those expressly permitted herein is strictlyprohibited and shall not be made without Alcatel-Lucent’s prior written consent. All characters appearing in this trainingcourse are fictitious. Any resemblance to real persons, living or dead, is purely coincidental.

There may be a number of proprietary logos, marks, trademarks, slogans and product designations found in theContent. Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logos are trademarks of Alcatel-Lucent. All other trademarksare the property of their respective owners. Alcatel-Lucent does not grant you a license to use any of the foregoing logos,marks, trademarks, slogans and product designations in any fashion. Granting of the right to access and use the Content fortraining purposes does not confer upon you any license under any of Alcatel-Lucent’s or any third party's IP Rights.

DISCLAIMER

ALCATEL-LUCENT DISCLAIMS ALL WARRANTIES REGARDING THE TRAINING COURSES OR THE CONTENT, EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. THE ALCATEL-LUCENT WILL NOT BE RESPONSIBLE OR LIABLE FOR ANY INJURY, LOSS, CLAIM,DAMAGE, OR ANY SPECIAL, EXEMPLARY, PUNITIVE, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OF ANY KIND

(INCLUDING WITHOUT LIMITATION LOSS PROFITS OR LOSS SAVINGS), WHETHER BASED IN CONTRACT, TORT, STRICTLIABILITY OR OTHERWISE, THAT ARISES OUT OF OR IS IN ANY WAY CONNECTED WITH (A) ANY USE OR MISUSE OF THECONTENT OR THE TRAINING COURSES BY YOU, OR (B) ANY FAILURE OR DELAY BY ALCATEL-LUCENT, ITS OFFICERS,DIRECTORS, AGENTS OR EMPLOYEES IN CONNECTION WITH THE CONTENT OR THE TRAINING COURSES (INCLUDING,WITHOUT LIMITATION, THE USE OF OR INABILITY TO USE ANY COMPONENT OF THE CONTENT OR TRAINING BY

YOU). SOME JURISDICTIONS LIMIT OR PROHIBIT SUCH EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITIES AND SO THE FOREGOING EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITY MAY NOT APPLY TO YOU.

GOVERNING LAW

These Terms of Use and Legal Notice are governed by the laws of France. The operation and use of the training course isgoverned by the laws of the country that governs your employment contract, if applicable. If any provision of these Termsof Use and Legal Notice, or the application thereto to a person or circumstance, is held invalid or unenforceable by law,statute or a court of competent jurisdiction, for any reason, then such provision shall be modified and/or superseded by aprovision that reflects the intent of the original provision as closely as possible. All other provisions of these Terms of Useand Legal Notice shall remain in full force and effect. You may not assign these Terms of Use or any permission granted

hereunder without Alcatel-Lucent’s prior written consent. Nothing herein shall be deemed an employment agreement or anoffer of employment or an alteration in any way of a user’s terms of employment with or within Alcatel -Lucent.

Copyright © 2011 Alcatel-Lucent. All Rights Reserved

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Welcome to 9500 MPR-E (Microwave Packet Radio) ETSI

R4.0 Node Configuration Operation & Maintenance Section 1 Product Overview

Module 1 Introduction

Module 2 Architecture

Section 2 Functional Description

Module 1 MSS Hardware Architecture

Module 2 ODU300 Hardware Architecture

Module 3 MPT-HC Hardware Architecture

Module 4 MPT-HC V2 Hardware Architecture

Module 5 MPT-MC Hardware Architecture

Section 3 NE Operation

Module 1 TCO Operator Interface

Module 2 Equipment Views & SettingsModule 3 Cross-Connection Configurations

Module 4 Performance Monitoring

Section 4 Maintenance

Module 1 Fault Management

Module 2 Protection

Module 3 Software Download

Section 5 Terms

Module 1 Acronyms

Appendix A

Module 1 Initial Configuration

Appendix B

Module 1 MPR Management

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Welcome to 9500 MPR-E (Microwave Packet Radio) ETSI

R4.0 Node Configuration Operation & Maintenance Upon completion of this course, you should be able to:

z Describe the basic concepts of the 9500 MPR z Turn-up and provision the systemz Respond to and manage alarm conditionsz Monitor system and application status

z Maintain 9500 MPR hardware and software

Your feedback is appreciated!

Please feel free to Email your comments to:

[email protected]

Please include the following training reference in your email:

TWT42025 Edition 2.0

Thank you!

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



This page intentionally left blank

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


Copyright © 2012 Alcatel-Lucent. All Rights Reserved.Edition 2

Section 1 · Module 1 · Page 1

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




This page is left blank intentionally

Document History

Edition Date Author Remarks

3.4 2012-06-14 AL University First edition

4.0 2012-09-15 AL University Updated for release 4.0

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 Understanding the 9500MPR Innovations 71.1 Classification of the New Generation Products 81.2 Presentation 91.3 Multiservice Aggregation Layer 121.4 Service Awareness 131.5 Packet Node 141.6 Service-driven Packet Adaptive Modulation 151.7 Power Consumption Reduction 161.8 Hybrid or Packet Mode: for Efficient Data Transport 17 2 MPR in New Market Segments 192.1 The Most Effective Solution 202.2 MPR-e Enabling Zero-Footprint Microwave Configurations 222.3 MPR in Last Mile 23

2.4 LTE and Full Ethernet 3G Ready 242.5 From Current PDH/SDH Network to Packet Transport Network Evolution 252.6 MPR addresses All Microwave Applications in Aggregation 262.7 MPR addresses Metro Ring/Partial Mesh Application 27 3 System Description 293.1 Alcatel-Lucent 9500 Microwave Packet Radio 303.2 9500 MPR System Family 313.3 9500 MPR Key Features 333.4 9500 MPR Node 35 4 Radio Configuration 454.1 Radio Configuration 46 5 System Configuration 475.1 Example of System configurations 48

6 Management Systems 536.1 Network Management 54

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Multiservice aggregation layer - the capacity to use Ethernet as a common transmission layer totransport any kind of traffic, independently by the type of interface. Ethernet becomes the convergencelayer.

• Service awareness - traffic handling and quality management, queuing traffic according to the type of service assigned, independently by the type of interface

• Packet node - no service aggregation limits with all traffic aggregated in packets, in term of: capacity,type of service requirements and type of interface

• Service-driven adaptive modulation- fully exploit the air bandwidth in its entirety by changingmodulation scheme according to the propagation availability and allocate transport capacity, discriminatingtraffic by different services, only possible in a packet-based environment


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 9500 MPR aggregates and carries over a COMMON PACKET LAYER : TDM 2G, 3G, LTE 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 circuitemulation and pseudo-wire.

• R99 - original standard for UMTS WCDMA based networks

• HSDPA (High Speed Data Packet Access) - add on to R99/UMTS networks which adds a shared high speeddownlink packet channel

• ISAM (Indexed Sequential Access Method) - a method for indexing data for fast retrieval

• UMTS (Universal Mobile Telecommunications System – 3rd generation mobile cellular technology for GSM-based networks.

• WCDMA (Wideband Code Division Multiple Access) – interface standard found in 3G mobiletelecommunications networks.

• WiMAX (Worldwide Interoperability for Microwave Access) - telecommunications protocol that provides fixedand mobile Internet access


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



zService awareness means the ability to discriminate the different traffic types carried over the converged

Ethernet stream. Our traffic flow can be composed of E1, E3, STM-1, ATM, DS1, DS3, and/or IP/Eth, comingfrom different sources, and therefore having different requirements. For instance, DS1 or ATM traffic from a3G base station can carry voice (high priority, real time service) and data (lower priority and possibly non realtime with high variability load, such as internet browsing, music download or video streaming).

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Traffic with high priority will always have bandwidth available, like voice (deterministic approach)

• Broadband traffic is discriminated by QoS dynamically, with modulation scheme changes driven bypropagation conditions.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Extended 9500 MPR packet transport family to cover last mile access Î MSS-1c

Low cost, ½ rack length, Very low power consumption, MW radio protection, Hybrid & Packet operational modes

• Multipurpose ODU Î the MPT; to cover all MW applications under a single platform

Zero foot print for Ethernet applications, common to all MSS platform, enables integrated solution for MPLS metronetwork

• Introducing 9500 MPR-e Î stand-alone “full outdoor”

• Existing compatibility with 9500 MXC


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 9500 MPR in the stand alone (zero-footprint) architecture is built by only one unit for Ethernet applications:

• Outdoor Unit.

• Outdoor Unit is connected to the MPLS metro networks equipment with one coaxial cable for the powersupply and one Ethernet optical or electrical cable (with MPT).

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

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

• Outdoor Unit.

• MSS and Outdoor Unit are connected with a single standard coaxial cable (with ODU300) or with onecoaxial cable for the power supply and one Ethernet optical or electrical cable (with MPT).

• Up to 6 ODU300 can be connected to an MSS-8

• Up to 2 ODU300 can be connected to an MSS-4

• Up to 18 MPT can be connected to an MSS-8. Up to 8 can be powered directly by the MSS-8 shelf.

• Up to 14 MPT can be connected to an MSS-4


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Link Aggregation groups a set of ports so that two network nodes can be interconnected usingmultiple links to increase link capacity and availability between them.

• When aggregated, two or more physical links operate as a single logical link with a trafficcapacity that is the sum of the individual link capacities.

• This doubling, tripling or quadrupling of capacity is relevant where more capacity is requiredthan can be provided on one physical link.

• Link aggregation also provides redundancy between the aggregated links. If a link fails, itstraffic is redirected onto the remaining link, or links.

• If the remaining link or links do not have the capacity needed to avoid a traffic bottleneck,appropriate QoS settings are used to prioritize traffic so that all high priority traffic continues to

get through.• The Link Aggregation is performed according to 802.3ad and can be applied to Radio ports and

to User Ethernet ports.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The 9500 MPR Node supports up to 18 RF links for operation on the same or different frequency bands usingthe MSS-8.

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

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

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Supports unprotected or protected links


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 32E1/DS1 card: provides the external interfaces for up to 32xE1/T1 tributaries, manages theencapsulation/reconstruction of PDH data to/from standard Ethernet packets and sends/receives standardEthernet packets to/from both Core-E modules.

• ASAP card: provides external interfaces to transport 16xE1 ATM traffic, with E1/IMA physical layer, in an MPR network. ATM traffic is transported within MPR network as "special" Ethernet traffic. This traffic is managed bythe MPR using RFC 4717 (IETF ATM PseudoWire EdgetoEdgeeEmulation, PWE3) with N-1 encapsulation format.

• AUX card: provides the external interfaces for Service Channels access and Housekeeping alarms.

• STM-1 card: provides the external interfaces for up to 2 electrical or optical STM-1 signals, manages theencapsulation/reconstruction of SDH data to/from standard Ethernet packets and sends/receives standardEthernet packets to/from both Core-E modules.

• EAS Peripheral (P8ETH) card: provides access for customer Ethernet traffic and supports the following traffic

external interfaces:• 4xEthernet 10/100/1000 Base-T

• 4xEthernet SFP 4x1000 Base-X optical, Base-T, or Copper Cable access directly available on the EASmodule. Interfaces can be 1000BASE-LX (GbE LX 10 km) or 1000BASE-SX (GbE SX 550 m) or 1000BASE-CX (GbE CX 25 m)

• Modem 300: this unit is used to interface the ODU300. It sends/receives standard Ethernet packets to/fromboth Core-E modules, manages the radio frame (on Ethernet packet form) generation/termination, the interfaceto/from the alternate Radio module (for RPS management), the cable interface functions to ODU; it containsthe logic for the EPS Core-E protection, the RPS logic.

• MPT access card (with PFoE): this unit is used to interface the MPT. PFoE (Power Feed over Ethernet) is used tocarry the power supply to the MPT-HC through an electrical Ethernet traffic connector.

• The optional +24 Vdc/-48 Vdc Converter unit (to be installed in transport slot 4, 6 or 8 of MSS-8 can be used topower the MSS for +24 Vdc office applications.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• With the Core protection max. 3 MSS can be interconnected as shown in figure.

• To implement this configuration the LOS alarm on the Ethernet ports must be enabled as switching criterion of the Core protection. To enable this alarm the “Ethernet LOS Criteria” feature has to be enabled.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The 1+1 configuration with MPT-MC does not require any interconnection cable between the two ODUs.

• The 1+1 configuration with MPT-HC, MPT-HC V2, MPT-XP, or 9558HC can be implemented with or withoutan interconnection cable between the two ODUs.

• In 1+1 configuration the 2 ODUs must be of the same types.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 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 integratedinto 1350 OMS Network Management System providing all the tools required to operate the network.

• 9500 MPR can also be managed by Alcatel-Lucent 5620 SAM.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

9500 MPR can be managed:

• by Alcatel-Lucent 1350 OMS Network Management System,

• by Alcatel-Lucent 5620 SAM.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History



4.0 2012-09-14 AL University Updated for Release 4.0

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• MPT-HC V2 is similar to MPT-HC from architecture standpoint and can be used as spare part of the MPT-HC.The differences are:

• MPT-HC V2 can be natively Ethernet powered through a proprietary PFoE (or as alternative by using twocables, one coaxial cable for the Power Supply and one optical cable for the Ethernet Traffic (as MPT-HC).

• MPT-HC V2 is XPIC-ready (by the installation of a dedicated module).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



zMPT Access Card PoE

z2 MPT per MPT Access Card

2x 1000BaseT port with Power over CAT5e cable(Electrical connectivity Data+Power over a single CAT cable)

2x SFP ports for optical connection option

2x Coax connection(power feed in case of Optical connection)


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Pigtail: N-RJ45 two wires Transition Connector.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

MPT-HC must be connected to a fuse or a breaker on a customer power distribution box. The recommended valueis 3 Amps.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• One electrical Ethernet cable connects an MPT Access unit in the MSS to its MPT-HC V2 (the MPT Access unitprovides the PFoE).

• The max cable length is 100 m.

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Two cables connect an MPT Access unit in the MSS to its MPT-HC V2:

• One cable is a 50 ohm coaxial cable to send the power supply to the MPT-HC V2:

• for length lower or equal to 100 m the power cable can be CAT5E cable to send the power supply tothe MPT-HC V2 . The Ethernet electrical cable is provided with connectors to be mounted on site withthe specific RJ45 tool (1AD160490001);

• for length higher than 100m, the cable is a 50 ohm coaxial cable to send the power supply to the MPT-HC V2

Note: In case of length lower than 100m and presence in the field of 1 coaxial already installed and free it isrecommended to use the coax cable to minimize the installation effort.

• The second cable is an Ethernet optical cable.

• The Ethernet optical cable is preassembled and available in different lengths (up to 450 m).

Note: A special cord adapter must be connected to the coaxial cable on the MPT-HC V2.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Two cables connect an MPT Access unit in the MSS to its MPT-HC V2:

• One cable is a 50 ohm coaxial cable to send the power supply to the MPT-HC V2:

for length lower or equal to 100 m the power cable can be CAT5E cable to send the power supply tothe MPT-HC V2 . The Ethernet electrical cable is provided with connectors to be mounted on site withthe specific RJ45 tool (1AD160490001);

for length higher than 100m, the cable is a 50 ohm coaxial cable to send the power supply to the MPT-HC V2

Note: In case of length lower than 100m and presence in the field of 1 coaxial already installed and free it isrecommended to use the coax cable to minimize the installation effort.

• The second cable is an Ethernet optical cable.

The Ethernet optical cable is preassembled and available in different lengths (up to 350 m).

Note: A special cord adapter must be connected to the coaxial cable on the MPT-HC V2.

Note: MPT-HC V2 must be connected to a fuse or a breaker on a customer power distribution box. Therecommended value is 3 Amps.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Two cables connect the MPT:

• one optical cable connected to port#5 or port #6 of the Core-E unit

• a coaxial cable connected to the station battery to provide the power supply.

• MPT-HC V2 must be connected to a fuse or a breaker on a customer power distribution box. The recommendedvalue is 3 Amps.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Both injectors include:

• Powering of two MPT

• Lightning protection

• DC protection

• LEDs for power output

Power Injector plug-in

Power Injector box


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Definition: This service identifies a flow inside MPR network, in which E1/T1 is transported,switched and terminated.

• Application: Typical microwave 2G backhauling application, in which E1/T1s are terminatedbefore entering into aggregation network.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Definition: E1/T1 TDM input signals are packetized according to MEF8 standard; E1/T1s aretransported, switched and provided to an external ETH network in standard format (MEF-8).

• Application: Typical microwave 2G backhauling application, in which E1/T1s are terminatedbefore entering into aggregation network, where aggregation network is a packet network.E1/T1s are not terminated at the end of the microwave backhauling and an end-to-end circuitemulation services could be established between 9500 MPR and the service router in front of BSC/RNC


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Definition: This service identifies a flow inside MPR network, in which STM-1 is transparentlytransported, switched and terminated.

• Application: Typical microwave transport application.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Definition: Ethernet traffic is transported and switched automatically by the standard auto-learning algorithm of the built-in MPR 10 Gbit Ethernet switch.

• Application: Typical microwave 3G backhauling/WiMax application, in which transport of Ethernet packets coming from base stations is requested.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• TDM2TDM and TDM2ETH profiles are managed in compliancy with Metro Ethernet Forum specifications

• MEF 8- Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks

• Same behavior than PDH/SDH transmission devices (QoS)

• Reduced impact of the “packetization” overhead

• Same Radio performances than PDH/SDH devices


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Case 1 for E1/T1 (TDM2TDM over MPR network)

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

Case 1 for STM-1 (SDH2SDH)

• The STM-1 stream is inserted in Node 1 and extracted in Node 2. In this case the two IWFs used to

packetize the traffic for the Ethernet switch in the Core-E module are both internal to the 9500 MPR network.The Circuit Emulation Service is SDH2SDH in Node 1 and Node 2. The Cross connections are SDH-Radio type.

Case 2 (TDM2Eth)

• The E1/T1 stream is inserted in Node 1 and extracted in Node 2. One IWF is inside the 9500 MPR, thesecond IWF is external to the 9500 MPR-E network. The Circuit Emulation Service is TDM2ETH in Node 1 andNode 2. The Cross connections are PDH-Radio type in Node 1 and Radio-Eth type in Node 2.

Case 3 (TDM2Eth)

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Cases 4 and 5 (ETH2ETH)

• In these cases Ethernet packets enter Node 1 and are extracted in Node 2. In case 4 the Ethernet packetsencapsulate 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 Crossconnections must be implemented. The path is automatically implemented with the standard auto-learningalgorithm of the 9500 MPR Ethernet switch.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Case 6 for E1/T1 (TDM2TDM over Ethernet)

• The E1/T1 stream is inserted in Node 1 and extracted in Node 2. In this case the two IWFs usedto packetize the traffic for the Ethernet switch in the Core-E module are both internal to the 9500MPR network. The Circuit Emulation Service is TDM2TDM in Node 1 and Node 2. The Crossconnections are PDH-Eth type.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Flow Id present (user defined)

• intermediate node configuration (E1/T1 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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• ECID = Emulated Circuit Identifier

• IWF = Inter-Working Function


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:


• 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)


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• ECID = Emulated Circuit Identifier


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:


• If there are intermediate nodes in each node build the Cross-connection tables based on Flow Id.

• Bandwidth guaranteed (according to QoS Æ Highest Queue Priority association)

• No flooding-autolearning necessary

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 9500MPR uses a Connection Admission Control (CAC) for committed services and two schedulers inseries (on Core embedded L2 switch and on Radio peripheral)

• The two schedulers need to jointly interoperate to guarantee determistic behavior of the services

• The QoS function inside 9500 MPR-E is the result of a distributed implementation in the switch in the Core-Eunit and Radio Interface unit. Both those QoS functions are properly configured in order to get the wishedbehavior on Ethernet flows that will be transmitted towards the Radio.

• The QoS configuration is the same for all the involved units:

• Core-E

• EAS

• Modem unit (to interface the ODU300)

• MPT-HC/MPT-HC V2/MPT-MC


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In the figure is shown an overview of the QoS implementation inside the Core-E unit and Modem unit whichis used to interface the ODU300.

• The QoS feature provides eight internal queues to support different traffic priorities. The QoS function canassign the packet to one of the eight egress transmit queues.

• Queue 8 is assigned to TDM2TDM traffic (fixed assignment)

• Queue 7 is assigned to TDM2Eth traffic (fixed assignment)

• Queue 6 is assigned to TMN (fixed assignment)

• Queues 1 to 5 are assigned to Ethernet traffic according to the information inside the packet as 802.1pfield or DiffServ field.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In case the configuration of radio interfaces changes from 1+0 to 1+1, the Radio QoS of Spareinterface takes the queue sizes of the Radio QoS of Main interface. The previous configuration of queue sizes of the Radio QoS of Spare interface is lost.

• In case of the configuration of radio interfaces changes from 1+1 to 1+0, the Radio QoS of Maininterface maintains the previous configuration of queue sizes, while the Spare interface takes thedefault queue sizes according to the configured Modem Profile.

• When a radio port is added to the L1 LAG port, all custom QoS and queue size configuration islost.

• When a radio port is removed from a L1 LAG port, the NE QoS settings are applied to the radio

port. The queue sizes are set to the default values.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In order to give an estimation of the maximum delay, that an Ethernet frame can experiencewhen entering the specific queue in case of congestion of radio interface, the WebEML shows aread-only value, which is the queue size configured by the operator converted in a time value(msec).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In this example, user traffic is split up into radio channels. Main advantages:

• Throughput. The overall radio Ethernet throughput is more than 1 Gbit/sec (4 x 350 Mbit/s,being this the value for 256QAM@56 MHz)

• Protection. In case of a failure of one of the three channels, all the traffic is redirected onthe remaining link (with a throughput of around 0.35 Gbit/sec). The discarded or droppedtraffic is the one with lower priority: high priority traffic is still running on the remainingactive channels.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In Layer1 Link Aggregation, the Distributor performs a packet-based traffic distribution overmultiple links regardless of the content of the packets.

• The Distributor takes into account the number of bytes sent over a specific link and loads linksaccording to the available bandwidth. As a consequence, Layer1 Link Aggregation allows a trafficload balancing independently of traffic content. Since the distribution does not depend on Layer2or Layer3 header content, this kind of Link Aggregation is called Layer1 (i.e., associated to thephysical layer).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The following radio configurations are supported:

• 1+0 MPT-HC connected to P8ETH SFP port

• 1+0 MPT-HL connected to P8ETH SFP port

• 1+1 MPT-HL connected to P8ETH SFP port


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

One MPT per MPT plug-in.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Ethernet ports involved in a LAG cannot be used as TMN In-band interface.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• On the radio channel, a 9500 MPR transfers the reference clock to an adjacent MPR device through the radiocarrier frequency at physical layer.

• This method offers two main advantages:

• No bandwith is consumed for the synchronization distribution,

• Total immunity to the network load.

• End-to-end scenarios where time-of-day/phase alignment are requested are fully supported, as 1588 PTP v2is carried transparently by MPR across the microwave backhauling network.

• Both for Hybrid and Packet working modes, the Clock can be received at hand-off or delivered at the cell site.Synch-Eth, E1, PDH and BITS clock modes are available.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The availability of the Clock in the Network represents the most common scenario, characterized by a timesource available at the ingress of the microwave backhauling network, derived from the primary referenceclock.

• Synchronization (frequency) is delivered to the cell site using any of the options available on MPR, dependingon the operator’s need. Worth repeating ingress and egress methods can be mixed (i.e. Synch-Eth at theingress, E1/T1 at the egress) via a simple configuration.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 9500 MPR has an embedded reference clock which is distributed to each board of the network element.

• Such clock is generated in the Clock Reference Unit (CRU) of the core unit (controller).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

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

• Node Timing: this feature (called either “network clock re-timing” or “node timing” or, according to G. 8261wording, “network -synchronous operation for service clock”) introduces an additional possibility to recover E1clock.

• Node timing is a way to recover TDM clock quite popular in the industry of service routers and siteaggregator boxes. This feature inside the 9500 MPR platform is adding interworking capabilities withthird parties service routers and circuit emulations gateway.

• In node-timing working mode, all the E1s are re-sampled with the network element clock. This meansthat, as also reported in G8261, this method does not preserve the service timing (E1 clock).

• Recovered E1 clock is according to G. 823 synchronization masks.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In meshed networks (rings) do not close the synchronization configuration.

• If the NODE TIMING is enabled, the CT still propose the possible selection between ACR andDCR: in this specific case, the meaning of this option is not related to the clock recoveryalgorithms but rather to the MRF8 frame format.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Differential clock recovery

• Common reference clock IS available at both Ends.

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

• Adaptative clock recovery

• Common reference clock is NOT available at both Ends.

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• For each available sync source, the CRU detects the signal Degrade Alarm on each available syncsource. 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 CardFail, causes the switching of the Synchronization Source.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

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

• Each E1 /T1can be cross connected independently

• E1/T1s can be cross connected to any of the following interfaces:

• Radio interface

• Ethernet interface

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 Microwave Service Switch (MSS-8) 71.1 MSS-8 Overview 81.2 MSS-8 Cards 9 2 Microwave Service Switch (MSS-4) 112.1 MSS-4 Overview 122.2 MSS-4 Cards 13 3 Control and Switching Module/Core-E 153.1 CSM-E/Core-E Card 163.2 CSM-E/Core-E Card Block Diagram 213.3 CSM-E/Core-E Card Status LED 223.4 CSM-E/Core-E Card LEDs 23 4 Ethernet Access Switch/P8ETH 254.1 P8ETH/EAS Card 26

4.2 P8ETH/EAS Card Block Diagram 274.3 P8ETH/EAS Card Status LED 284.4 EAS/P8ETH Card LEDs 29 5 P32E1DS1 (DS1/PDH) Card 315.1 P32E1DS1 (DS1/PDH) Card 325.2 P32E1DS1 (DS1/PDH) Card Block Diagram 335.3 P32E1DS1 (DS1/PDH) Card Status LED 34 6 MPTACC Card 356.1 MPTACC Card 366.2 MPTACC Card Block Diagram 376.3 MPTACC Card Status LED 386.4 MPTACC Card LEDs 39 7 MOD300 Card 41

7.1 MOD300 Card 427.2 MOD300 Card Block Diagram 437.3 MOD300 Card Status LED 447.4 MOD300 Card LEDs 45 8 AUX Card 478.1 AUX Card 488.2 AUX Card Block Diagram 498.3 AUX Card Status LED 508.4 AUX Card LEDs 51 9 2xSTM-1 Local Access Card 539.1 2xSTM-1 Local Access Card 549.2 2xSTM-1 Local Access Card Block Diagram 55 10 ASAP Card 57

10.1 ASAP Card 5810.2 ASAP Card Block Diagram 5910.3 ASAP Card Status LED 6010.4 ASAP Card LEDs 61 11 Fan Card 6311.1 Fan Card 6411.2 Fan 2U Card with Alarms LEDs 65 12 +24/-48 Volt Power Converter 6712.1 +24/-48 Volt Power Converter 68 13 Power Extractor 6913.1 Power Extractor 70 14 Power Injector 7114.1 Power Injector 72

14.2 Power Injector Plug-in 7314.3 LEDs 74 15 MPT power unit 75

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Page

15.1 MPT power unit 7615.2 MPT power unit block diagram 7815.3 LEDs 79 16 MPT extended power unit 8116.1 MPT extended power unit 8216.2 MPT extended power unit block diagram 8416.3 LEDs 85 17 Microwave Service Switch (MSS-1c) 8717.1 MSS-1c 8817.2 MSS-1c Block Diagram 8917.3 MSS-1c Status LED 9017.4 MSS-1c 91 18 Distributors/Patch Panels 93

18.1 E1/T1 RJ-45 120 Ohm Patch Panel 9418.2 32E1 SCSI 75 Ohm Patch Panel 9518.3 E1/T1 Tributaries (Protected Pair) 9618.4 E1/T1 D-Connector Patch Panel 97


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

General Rules:

• One CSM-E/Core-E card is required (unprotected)

• Can be protected with 2nd CSM-E/Core-E

• One Flash card is required for every CSM-E/Core-E card

• Fan card provides Major/Minor relay alarms and a Summary Relay for Major or Minor (usually tied toPDU).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

General Rules:

• One CSM-E/Core-E card is required (unprotected)

• Can be protected with 2nd CSM-E/Core-E

• One Flash card is required for every CSM-E/Core-E card


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Gigabit Ethernet serial internal interfaces between CSM-E/Core-E and peripherals

• CSM-E/Core-E Macro Functions:

• Controller

• Layer 2+ Ethernet Switch, VLAN management and MAC based

• Ethernet MAC learning

• Cross-connect function for PDH and Data payload traffic;

• For any “packetized” flow, the switch will be in charge to also manage the EquipmentProtection Switching (EPS).

• Quality of Service (QoS) management.

• Selection of the synchronization clock to be distributed to each plug-in.

• The flash card stores the license, equipment software, equipment MIB, and equipment MACaddress.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• The Ethernet ports of the Core-E can be configured in two ways:

• to be used as GigaEthernet interface for Ethernet traffic (Note: for port#5 and port#6 the optionalSFP must be installed);

• to be used to connect an MPT: MPT-HC (ETSI), MPT-HCV2, or MPT-MC (ETSI) to port#1 toport#4; an MPT-HC only to port#5 and port#6.

• The Core-E unit has the option to equip two SFPs (in port #5, port #6). These ports can be also usedto connect directly an MPT-HC/MPT-HCV2.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The CSM-E/Core-E consists of microprocessor and Ethernet switch circuits. The Ethernet Switchprovides a Quality of Service (QOS) mechanism to control all streams.

• If QoS is disabled, all traffic inside the switch has the same priority. This means that for each switchport there is only one queue, first in, first out (FIFO)

• Three QoS settings in GUI are available as follows:

• Disabled

• 802.1 priorities are set based on IEEE 802.1D-2004 Annex G User Priorities and Traffic Classesthat defines seven traffic types and corresponding user priority values.

• DiffServ priorities are based on one of eight tags, each identifying one of eight traffic types andcorresponding user priority values.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Check front-panel LED indications

INDICATOR STATUS DEFINITION

Link (L) Off Link Down

Green Link Up

Activity (A) Off No Tx/Rx activity

Blinking Yellow Tx/Rx activity

NE Major Alarm (M) Red At least one alarm is present on the NE with major severity is present on the NE

NE Minor Alarm (m) Red At least one alarm is present on the NE with minor severity is present on the NE

NE Warning Alarm (W) Yellow At least one alarm is present on the NE with warning severity is present on the NE

NE Abnormal Condition (A) Yellow At least one abnormal condition is present on the NE

Status (S) Off Card not equipped, not provisioned, or not powered

Green Blinking Download, software Booting, or flash card realignment in progress

Green In Service, Normal Operation, and Properly Provisioned

Yellow In protect, properly provisioned as EPS

Red Card fail

Blinking Red Card mismatch

• Always check to see if symptoms match the alarm.

• LEDs provide summary alarm indications, which can help narrow down the location and type of failure.

• The LEDs on the CSM-E/Core-E front panel for each Ethernet connector are a good indicator of correct connectivity and activity on

the Ethernet port.

• Where a Status LED on a plug-in is off (unlit), but power to the MSS-8 is confirmed by LEDs on other plug-ins, check the seating of the affected plug-in.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

MSS-8 shelf:

• Supports three protected pairs of P8ETH/EAS cards or six unprotected P8ETH/EAS cards.

• P8ETH/EAS is supported in slots 3-8 for unprotected radio configurations.

• In protected radio configurations, a pair of P8ETH/EASs are required.

• The main P8ETH/EAS is equipped in slots 3, 5, or 7

• The protect (spare) P8ETH/EAS is equipped in slots 4, 6, or 8 directly across from the main.

• The protect card protects the radio if the main fails.

MSS-4 shelf:

• Supports one protected pair of P8ETH/EAS cards or two unprotected P8ETH/EAS cards.

• P8ETH/EAS is supported in slots 3 and 4 for unprotected radio configurations.

• In protected radio configurations, a pair of P8ETH/EASs are required.

• The main P8ETH/EAS is equipped in slot 3.

• The protect (spare) P8ETH/EAS is equipped in slot 4 directly across from the main.

• The protect card protects the radio if the main fails.

• MPT-HL – ANSI market


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• If more than six local Ethernet accesses are required (built into the Core-E), the EAS (P8ETH) offersan additional four 10/100/1000 Ethernet interfaces plus 4 1 GbEth optical

• An embedded 10 Gbit/sec L2 switch is present on the unit.

• There are four Electrical 10/100/1000 base-T electrical ports and 4 optical SFP (LX and SX).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• SAToP: Structure-Agnostic TDM over Packet

• In a radio link containing a DS3 connection, a maximum of five DS1 connections can be assigned. Additional DS1 connections may be added to separate links that do not contain DS3 connections.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In the TX direction, the P32E1DS1 card processes and encapsulates up to 32 input lines into 2Ethernet packets.

• In the RX direction, the P32E1DS1 card extracts data from the Ethernet data packets and processesthe data to provide up to 32 output lines.

• The P32E1DS1 card performs the following macro functions:

• Termination of 32 E1/T1 signals (32 E1/T1 bi-directional interfaces on the front panel)

• Framed E1/T1 bi-directional alarm management

• Encapsulation/Extraction of PDH data flows into/from standard Ethernet packets

• Reconstruction of the original PDH Timing

• Selection of the Active CSM-E/Core-E

• Sending/getting Ethernet packets to the CSM-E/Core-E

• Communication with the Controller for provisioning and status report

• The module communicates with the CSM-E/Core-E Gigabit Ethernet Serial copper bi-directionalinterfaces on the backplane.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• There are equipping options for the P32E1DS1.

• Can be equipped in slots 3-8.

• Two are required, the main module in slot 3, 5, or 7 and the protect (spare) module in the slotdirectly across from the main (slot 6 or 8). The protect (spare) P32E1DS1 module protects theE1/T1 stream if the main P32E1DS1 card fails.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Main functions:

• Provide the power supply interface and the Ethernet interface

• Provide the Power Feed over Ethernet function

• Lightning and surge protection

• Ethernet and power interface supervision

• EPS/HSB management function

• Clock distribution function

• L2 packet based Proprietary clock algorithm

• Ethernet link quality monitor function

• Radio Link Quality notification through MPR Protection Protocol frames

• Communication with Core controller for provisioning and status report


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The MPT Access Unit is the interface for two MPT: MPT-HC or MPT-MC.

• Two MPT-HC or MPT-MC can be connected to one MPT Access unit.

• The two MPT can be configured in unprotected or protected configuration.

• The connection to the MPT-HC can be realized:

• by using two connectors:

• one DC power Supply connector to send the power supply to the MPT-HC

• one Gigabit Ethernet connector (electrical or optical) to send the Ethernet traffic and theEthernet control frames to the MPT-HC

• or by using only one electrical Ethernet cable with the enabling of the PFoE (Power Feed over

Ethernet) function (Ethernet traffic + Power Supply on the same cable).

• If the optical port has to be used, an SFP plug-in must be installed.

• If has been enabled port #1 (optical or electrical), the associated Power Supply port is #1.

• If has been enabled port #2 (optical or electrical), the associated Power Supply port is #2.

• The connection to the MPT-MC is realized by using only one electrical Ethernet cable with the enablingof the PFoE (Power Feed over Ethernet) function (Ethernet traffic + Power Supply on the same cable).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Service Channels access and Housekeeping alarms are available with the optional Auxiliaryperipheral unit.

• The Auxiliary peripheral unit on front panel is equipped with four connectors:

• one connector to manage the Service Channel 1

• one connector to manage the Service Channel 2

• one connector to manage the housekeeping alarms

• one connector for EOW (not used in the current release)


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

EOW - Engineering Express Order Wire


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

•The STM-1 unit can be used in two different working modes, addressing two different network scenarios:

• STM-1 channelized, provision card as SDHCHAN

• STM-1 transparent, provision card as SDHAC

• The STM-1 channelized interface works as a terminal multiplexer; it terminates or originates the SDH frame.It multiplexes NxE1 into an STM-1 electrical/optical line connection. The clock source can be “Loop time” or

“Node time”. Typical application is a direct connection to SDH add-drop multiplexers (ADMs). STM-1 cardmanages one 155 Mbit/s STM1 interface and up to 63xE1. Standard VC4 mapping of lower-order E1 trafficstreams to/from STM-1 is applied, that means that a VC4 directly maps up to 63xVC12 into an STM-1 signal(in turn each VC12 contains 1xE1).

• Link options include:

• 1+0 non-protected operation

• 1+1 EPS protection (available ONLY with the optical interface)

• When protection of the unit is required (1+1 EPS protection), two STM-1 units must be installed.

• Clock source from the incoming STM-1 signal can be selected as Network Element source clock. In the eventthe clock source is lost, clocking falls back to the internal clock or to other of any synch in options.

• In the Tx direction, the STM-1 Local Access unit processes and encapsulates up to 2xSTM-1 input lines intoan Ethernet packet that is sent to the Core-E card(s).

• In the Rx direction, the STM-1 Local Access unit extracts data from the Ethernet data packets and processesthe data to provide up to 2 STM-1 output lines.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The ASAP card is used to transport 16xE1 ATM traffic, with E1/IMA physical layer.

• The ASAP cards are unprotected (No 1+1 EPS is available).

• ATM traffic is transported within the MPR network as "special" Ethernet traffic.

• This "special" Ethernet traffic is managed by the MPR using RFC 4717 (IETF ATM PseudoWireEdgetoEdgeeEmulation, PWE3) with N-1 encapsulation format.

• ATM PW Ethernet traffic is managed by MPR is such a way to emulate the native QoS that wouldbe applied by ATM equipment.

• VCC mode

•

It is possible to transport max 48 VC for every IMA group. It is possible to manage VCswitching (= VCI and VPI change)

• It is possible to assign at every VC one specific QoS. Policing and shaping at ATM level hasperformed VC mode only

• The VC of the same class level (CBR / UBR+ / UBR) are managed in the same radio tailthan are available 3 different radio tails

• VPC mode

• It is possible to transport max 48 VP for every IMA group. It is possible to manage only VPswitching (=only VPI change)

• All the VC inside the VP must have same QoS (= for ex. all CBR or all UBR)

•The radio QoS (= radio tails) and QoS ATM (=policing and shaping) are managed at VP level.

• The sum of VP + VC configured on a single ASAP card must be <128.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

•The 16xE1 ATM streams enter the ASAP unit on the front panel.

•The block diagram is divided into 3 parts:

• LIU/Framer

• Network Processor

• Confederation FPGA

•The main functions implemented by the LIU/Framer are:

• Internal termination supported: 75 ohm, 120 ohm.

• Line code supported: HDB3.

• Pulse shape: digitally programmable

• Framing to G.704 E1 signals and to CRC-4 multi-frame alignment signals.

• Detection of alarm conditions as loss of signal, loss of frame, loss of signaling multi-frame andloss of CRC multi-frame.

• The Network Processor is the heart of the ASAP card and provides the implementation of theprotocols to be supported as well as data forwarding. ATM-IMA over PseudoWire, SAToP (like onthe PDH card), CESoP, ML-PPP can be supported by the SW application controlling the Data Pathand running on a different MIPS processor embedded on the same chip.

• The main function implemented in the confederation FPGA is the clock management.

• The right-hand side is the backplane with the 1 Gb bus shared among the other slots and hencecommon with the other units (PDH units and Modem units).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Two DC connectors in the front (for box version), or power from the back panel (for plug-inversion).

• Two RJ45 for the data in (DATA)

• Two RJ45 for the data + DC out (DC+DATA)


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Check front-panel LED indications

INDICATOR STATUS DEFINITION

Link (L) Off Link Down

Green Link Up

Activity (A) Off No Tx/Rx activity

Blinking Yellow Tx/Rx activity

Major Alarm (M) Red At least one alarm is present on the NE with major severity

Minor Alarm (m) Red At least one alarm is present on the NE with minor severity (not supported)

Warning Alarm (W) Yellow At least one alarm is present on the NE with warning severity (not supported)

Abnormal Condition (A) Yellow At least one abnormal condition is present on the NE

- Tx Power muted by operator

- ACM frozen by operator

- MPT loopback active

MPT1 Off MPT is not emitting power according with the known configuration

Green MPT is emitting power as expected according the known configuration

Yellow MPT is not emitting power due to a forced Squelch condition

Red MPT is ABNORMALLY emitting power

MPT2 (not supported)

At start-up the MSS-1c:

• lights on all the alarm LEDs (Major, Minor, Warning and Abnormal)

• lights on the MPT LED as yellow, then this LED will be green, red, or yellow, as explained above.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 Outdoor Unit 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 ODU300 and Antenna 143.2 ODU300 Mounting Options 153.3 Installing the ODU 163.4 Direct-Mounted ODUs 173.5 Remote-Mounted ODUs (solution 1) 183.6 Remote-Mounted ODUs (solution 2) 193.7 Waveguide Flange Data 21

3.8 Grounding the ODU 223.9 ODU300 External Connectors 23

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The ODUs include a waveguide antenna port, Type-N female connector for the ODU cable, a BNC femaleconnector (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 suppliedwith 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 standardantenna, 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 diversityconfigurations, a direct-mounting coupler is used. They are available for equal or unequal loss operation.Equal loss is nominally 3 dB.

• Unequal is nominally 1/6 dB.

• The ODU assembly meets the ASTME standard for a 2000 hour salt-spray test, and relevant IEC, UL, andBellcore standards for wind-driven rain.

• ODUs are frequency-band specific, but within each band are capacity-independent up to their designmaximums.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The quadrature modulated 311 MHz IF signal from the MSS is extracted at the N-Plexer and passed via a cable AGCcircuit 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 referencesignal from the MSS.

• These I and Q signals modulate a Tx IF, which has been set to a specific frequency between 1700 and 2300 MHz, suchthat when mixed with the Tx local oscillator signal (TXLO) in the subsequent mixer stage, it provides the selectedtransmit frequency. Both the IF and Tx local oscillators are synthesizer types.

• Between the IQ modulator and the mixer, a variable attenuator provides software adjustment of Tx power.

• After the mixer, the transmit signal is amplified in the PA (Power Amplifier) and passed via the diplexer to the antennafeed port.

• A microprocessor in the ODU supports configuration of the synthesizers, transmit power, and alarm and performancemonitoring. The ODU microprocessor is managed under the NCC microprocessor, with which it communicates via thetelemetry 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, whereit is mixed with the receive local oscillator (RXLO) input to provide an IF of between 1700 and 2300 MHz. It is thenamplified in a gain-controlled stage to compensate for fluctuations in receive level, and in the IF mixer, is converted to a126 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 optionsprovided are based on ETSI plans for each frequency band. The actual frequency range per band and the allowableTx/Rx splits are range-limited within 9500MPR-E to prevent incorrect user selection.

• A power monitor circuit is included in the common port of the diplexer assembly to provide measurement of transmit

power. It is used to confirm transmit output power for performance monitoring purposes, and to provide a closed-loopfor power level management over the specified ODU temperature and frequency range.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The ODU mounts directly to an Antenna: Non-protected.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 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 couplerconnects 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) or900 mm (3 ft). Both flange ends are identical, and are grooved for a half-thickness gasket, which is suppliedwith the waveguide, along with flange mounting bolts.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Table lists the antenna port flange types used with the ODU300, plus their mating flange options andfastening hardware for remote mount installations.

• UDR/PDR flanges are rectangular; UBR/PDR flanges are square.

• On the ODU, the two flange styles are:

• UDR . 6-hole or 8-hole (6/8 bolt holes depending on frequency range/waveguide type), flush-faceflange 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.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 Outdoor Units 71.1 MPT-HC Construction and Mounting 81.2 MPT-HC Characteristics 13 2 MPT-HC Block Diagram 152.1 MPT-HC Block Diagram 16 3 Outdoor Installations 173.1 Installing the MPT-HC 183.2 6-7-8 GHz MPT-HC: integrated antenna (1+0) 193.3 11-38 GHz MPT-HC: integrated antenna (1+0) 203.4 6-7-8 GHz MPT-HC: integrated antenna (1+1) 213.5 11-38 GHz MPT-HC: integrated antenna (1+1) 223.6 6-7-8 GHz MPT-HC: non-integrated antenna (1+0) 233.7 11-38 GHz MPT-HC: non-integrated antenna (1+0) 24

3.8 6-7-8 GHz MPT-HC: non-integrated antenna (1+1) 253.9 11-38 GHz MPT-HC: non-integrated antenna (1+1) 263.10 MPT-HC External Connectors 273.11 DC Extractor 32

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• With external diplexer: due to a vary high number of shifters the diplexer is external for the flexibility of theshifter customization (7 GHz and 8 GHz), where MPT-HC is composed by two independent units:

• the BRANCHING assembly (containing the diplexer)

• the RF TRANSCEIVER assembly (containing the RF section)

• Each of this type of MPT-HC is identified by two Logistical Items, one for the BRANCHING assembly andanother for the RF TRANSCEIVER assembly.

• To read the BRANCHING assembly identification label it is necessary to separate the BRANCHING assemblyfrom the RF TRANSCEIVER assembly.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

•The MPT-HC is broken down into the following sections:• Common Belt section. This section is Frequency independent, and all the features relevant to this unit are

common to all the MPT RF options.

• RF section that is frequency dependent.

• The MPT-HC interface is based on a Gb Ethernet, that can be either optical or electrical depending on theneeds and the cable length. If the optical port has/have to be used (data and/or RPS port), thecorresponding SFP plug-in must be installed by opening the Cobox.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Warning: A waterproofing tape is glued on the waveguide of the MPT-HC. It must never be removed.

FREQUENCY GHz -> 11 13-15 18-25 38

Waveguide type -> WR75 WR62 WR42 WR28


Ref. infigure

Interface Connector

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

(2) Connector for power supply coax. cable male N 50 ohm

(3) Hole for Ethernet connection (in the co-box) Gland for Cat5e or optical cable

(optional)

(4) Hole for connection to a second MPT-HC in 1+1 (in the

co-box)

ODC

(5) Co-box

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




FREQUENCY GHz -> 7 8

Waveguide type -> WR112 WR112


Ref. infigure

Interface Connector




(optional)


co-box)

ODC

(5) Co-box

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




FREQUENCY GHz -> 6

Waveguide type -> WR137


Ref. infigure

Interface Connector




(optional)


co-box)

ODC

(5) Co-box

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• Connector usage:

• (M1) LEMO connector, to be plugged into LEMO connector on MPT-HC V2/MPT-MC.

• Note: LEMO is the cable manufacturer

• (M2) RJ45 connector, to connect the MCT directly to the MPT.

• Banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio Rx field. Duringequipment line –up, through a multi –meter it is possible to easily point the antenna until the measuredvoltage is the maximum, corresponding to the maximum radio Rx field.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The DC Extractor, installed close to the MPT-HC, allows to interconnect the MSS and the MPT-HC with asingle electrical Ethernet cable by using the “Power Feed over Ethernet” solution (Ethernet traffic and PowerSupply on the same cable).

The DC Extractor then separates the Power Supply from the Ethernet traffic, which are separately sent to theMPT-HC.

The two cables, interconnecting the DC Extractor to the MPT-HC (the Power Supply cable to be connected tothe DC Out connector of the DC Extractor and Ethernet cable to be connected to the Data Out connector of the DC Extractor), are provided, already terminated (2 m long), with the DC Extractor itself


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 Outdoor Units 71.1 MPT-HCV2 Characteristics 81.2 MPT-XP Characteristics 101.3 MPT-HC V2/MPT-XP XPIC 11 2 MPT-HC V2/MPT-XP/9558HC block diagram 132.1 MPT-HC V2/MPT-XP block diagram 142.2 MPT-HC V2/MPT-XP RF section block diagram 15 3 Outdoor Installations 173.1 Installing the MPT-HC V2/MPT-XP 183.2 MPT-HCV2 External Connectors 19

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Two mechanical solutions are adopted:

• With embedded diplexer for cost optimization, where the branching (diplexer) is internal to the MPT-HC V2 cabinet; this type of unit is identified by one Logistical Item only.

• With external diplexer: due to a high number of shifters the diplexer is external for the flexibility of theshifter customization, where MPT-HC V2 is composed by two independent units: the BRANCHINGassembly (containing the diplexer) and the RF TRANSCEIVER assembly (containing the RF section);each of this type of MPT-HC V2 is identified by two Logistical Items, one for the BRANCHING assemblyand another for the RF TRANSCEIVER assembly. To read the BRANCHING assembly identification label it

is necessary to separate the BRANCHING assembly from the RF TRANSCEIVER assembly.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The common belt section is frequency-independent. It is the digital section of the MPT-HC V2/MPT-XP.

• There are two architecture types for the RF section, the differences between these twoarchitectures are on the Rx side:

• For 7/8 GHz, there are two frequency conversions between RF input frequency and basebandfrequency

• For all other bands, there are three frequency conversions

• The power comes from office power. Input voltage range is -28 to -58 Vdc.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



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

Warning: A waterproofing tape is glued on the waveguide of the MPT-HCV2. It must never be removed.

FREQUENCY GHz -> 6 11 13-15 18-25 38

Waveguide type -> WR137 WR75 WR62 WR42 WR28


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

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




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:






• Banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio Rx field.During equipment line-up, through a multi –meter it is possible to easily point the antenna until themeasured voltage is the maximum, corresponding to the maximum radio Rx field.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 Outdoor Units 71.1 MPT-MC Construction and Mounting 81.2 MPT-MC Characteristics 10 2 MPT-MC Block Diagram 132.1 MPT-MC Block Diagram 14 3 Outdoor Installations 153.1 Installing the MPT-MC 163.2 7-8 GHz MPT-MC: integrated antenna (1+0) 173.3 6 and 11-38 GHz MPT-MC: integrated antenna (1+0) 183.4 7-8 GHz MPT-MC: integrated antenna (1+1) 193.5 6 and 11-38 GHz MPT-MC: integrated antenna (1+1) 203.6 MPT-MC: non-integrated antenna (1+0) 213.7 7-8 GHz MPT-MC: non-integrated antenna (1+1) 22

3.8 6 and 11-38 GHz MPT-MC: non-integrated antenna (1+1) 233.9 MPT-MC External Connectors 24

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• With external diplexer: due to a vary high number of shifters the diplexer is external for the flexibility of theshifter customization (7 GHz and 8 GHz), where MPT-MC is composed by two independent units:

• the BRANCHING assembly (containing the diplexer) and

• the RF TRANSCEIVER assembly (containing the RF section);

• Each of this type of MPT-MC is identified by two Logistical Items, one for the BRANCHING assembly andanother for the RF TRANSCEIVER assembly.



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

•Static radio profiles:

• bandwidths: 3.5, 7, 14, 28, 40, and 56 MHz

• modulations: 4, 8, 16, 32, 64, 128, and 256 QAM

• Adaptive radio profiles:

• bandwidths: 3.5, 7, 14, 28, 40, and 56 MHz

• modulations: 4, 8, 16, 32, 64, 128, and 256 QAM


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

•The MPT-MC breaks down into the following sections:• Common Belt section. This section is Frequency independent, and all the features relevant to this unit are

common to all the MPT RF options.

• RF section that is frequency dependent.

• The MPT-MC is similar to MPT-HC from architecture standpoint. It has limited capacity vs. MPT-HC and isnatively Ethernet powered (no Power extractor required).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

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

FREQUENCY GHz -> 6 11 13-15 18-25 38

Waveguide type -> WR137 WR75 WR62 WR42 WR28


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• With external diplexer: due to a vary high number of shifters the diplexer is external for the flexibility of theshifter customization (7 GHz and 8 GHz), where MPT-MC is composed by two independent units:

• the BRANCHING assembly (containing the diplexer)

• the RF TRANSCEIVER assembly (containing the RF section);

• Each of this type of MPT-MC is identified by two Logistical Items, one for the BRANCHING assembly andanother for the RF TRANSCEIVER assembly.





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:






• Banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio Rx field. Duringequipment line-up, through a multi –meter it is possible to easily point the antenna until the measuredvoltage is the maximum, corresponding to the maximum radio Rx field.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 WebEML start 91.1 WebEML start 10 2 WebEML Main View 192.1 WebEML Main view 202.2 Main Tool Bar Area 222.3 Severity Alarm Panel 242.4 Domain Alarm Synthesis Area 252.5 Alarm & State Panels 262.6 Resource Tree Area - Selection Criteria 27 3 Configuration Menu 293.1 Configuration Menu 303.2 NE Time Menu 313.3 Network Configuration Menu 32

3.3.1 NTP Configuration 343.3.2 IP Configuration - IP Static Routing Configuration 353.3.3 IP Configuration - OSPF Area Configuration 363.3.4 Routing Information 373.4 Alarm Severities 383.5 System Settings 413.6 Cross Connections 423.7 Ring Configuration 463.8 LAG Configuration 473.9 QoS Configuration 483.10 AUX Cross Connections 523.11 XPIC Configuration Menu 553.12 VLAN Configuration 56

3.13 VLAN Configuration - 802.1D 573.14 VLAN Configuration - 802.1Q 583.15 Traffic Descriptors 603.16 Profiles Management 623.17 Ethernet Features Shell 70 4 Diagnosis Menu 734.1 Diagnosis Menu 744.2 Alarms 754.3 Log Browsing 874.4 Remote Inventory 924.5 Abnormal Condition List 934.6 Summary Block Diagram View 944.7 Current Configuration View 97

5 Supervision Menu 995.1 Supervision Menu 1005.2 Access State 1015.3 Restart NE 1035.4 Restart MPT 1045.5 MIB Management 1055.6 SW License 109 6 SW Download Menu 1116.1 SW Download Menu 112 7 Equipment Tab 1137.1 Equipment Tab panel 1147.2 Starting From Scratch 1177.3 Tab panels in the Resource Detail Area 118

8 Protection Schemes Tab 1338.1 Description 134 9 Synchronization Tab 137

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

9.1 Synchronization Window 1389.2 Synchronization Window 1399.3 Synchronization sources assignment rules 1419.4 Allowed synchronization sources assignment 1429.5 SSM Summary Table 143 10 Connections Tab 14510.1 Connections Menu 146 11 Browser Interface 14711.1 Browser Interface 14811.2 Browser Interface - Logon 14911.3 Browser Interface - Alarm Screen 15011.4 Browser Interface - Date & Time Setting 15111.5 Browser Interface - Date & Time NTP Enabled 152

11.6 Browser Interface - Configuration Info 15311.7 Browser Interface - DHCP 15511.8 Browser Interface - License Info 15611.9 Community Strings Setting 15711.10 Browser Interface - Logout 158

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:

• The Main Screen is the starting point of the craft terminal application.

• Only one NE can be managed in a NEtO session.

• When you are connected to an NE, you get an Alarm overview.

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:

Community Strings

The Community String (CS) acts like a password to control access to an NE. It defines what communityof people can access the NE.

Site Database

• You can manage and organize a list of available NEs in a table on a server or a local PC.

• All data related to all NEs added to the list is saved in a custom format called “.NETO”.

• You can have your own NEs lists repository, containing all .NETO files that you produced with NEs

information inside.

• There is no default location for the database. You can save these anywhere, but be sure youremember where you put it.

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:

Icon in System Tray (highest alarm level in NE)

• Gray: Supervision is not active

• Red: Highest alarm is Critical

• Orange: Highest alarm is Major

• Yellow: Highest alarm is Minor

• Cyan: Highest alarm is Warning

• Blue: Highest alarm is Indeterminate

• Green: No Active Alarms

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:• The 9500 MPR-A/E supports access from SNMP managers implementing both SNMPv2/v1 andSNMPv3

protocols. The supported SNMP operating modes are the following:

• SNMPv2: This is the default mode. Only SNMPv2/v1 managers are allowed access to the NEfor both reading and writing.

• SNMPv3: Only SNMPv3 managers are allowed access to the NE.

• SNMPv3 addresses security problems by adding two new features on top of the existing SNMPv1 andSNMPv2 network management protocols:

• Authentication using hashing and time stamps. • Confidentiality using encryption.

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:

Login

• Type your username - must not be more than 20 characters.

• Type your password - must not be less than eight (8) or more than 20 characters and must becomposed of ASCII characters set (UPPER/lower case, numeric and special characters).

).

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The WebEML provides an alarm functionality that informs the operator on the severity of thedifferent alarms in the NE as well as on the number of current alarms.

• There are five alarm severity levels.

• Each alarm severity is represented by an alarm icon situated in the top left hand corner of theview.

• The shape of the alarm icons in the alarm panel gives an indication of the occurrence of alarms.

•

An alarm icon with a circle inside it (and a number at the bottom of the icon) indicates thatalarms 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 iconare occurring.

• An alarm icon grayed out indicates that spontaneous incoming alarm notification have beeninhibited.

• In the WebEML 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).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:

Alarm Functionality

• The Craft Terminal provides an alarm functionality that informs the operator on the severity of thedifferent alarms in the NE as well as on the number of current alarms.

• There are five different alarm severity levels. These different levels are associated with colors (greenin normal condition).

• Red: Critical alarm (C)

• Orange: Major alarm (M)

• Yellow: Minor alarm (m)• Cyan: Warning alarm (W)

• White: Indeterminate (I) Not operative

• The shape of the alarm icons in the alarm panel gives an indication of alarm occurrence.

• An alarm icon with a rectangle inside indicates that no alarms of the type defined by the icon areoccurring.

• 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 grayed out indicates that a spontaneous incoming alarm notification has been inhibited.

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:

Status Control Area

• LOCK : Local Access state: indicates whether the NE is managed by a craft terminal or by the OS.

• Green: Indicates that the terminal has the OS permission to manage the NE (granted).

• Cyan: Indicates that the terminal does not have the OS permission to manage the NE (denied).

• COM: Operational state: indicates whether or not the communication with the OS is established.

• Green: SDH service link up

• Red: SDH service link down

• SUP: Supervision state: indicates whether or not the NE is under OS supervision.

• Green: NE is under supervision.

• Orange: NE is not under supervision.• OS: OS isolation.

• Green: NE is not managed by the 1353SH.

• Cyan: NE is managed by the 1353SH.

• NTP: Server Status

• Orange: NTP function is disabled.

• Green: Loss of communication with Main and Standby servers.

• Cyan: NE is communicating with NTP Main or Standby servers.

• AC: Indicates whether some abnormal conditions have been recognized. The operator can visualize them with theDiagnosis-> Abnormal condition list menu.

• Green: Normal operating condition

• Cyan: Detection of an Abnormal operative condition

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Each tree node consists of possibly three symbols and a label.

• The first optional symbol indicates structure state: if symbol is "+", there can be expanded

• showing its contained lower levels. Tree structure can be collapsed if symbol is "-". With nosymbol, node represents a tree leaf.

• Second symbol is the graphical representation of resource itself.

• Third symbol is a round-shape icon showing the 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 or Double left click:

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

• Double left click: expands tree structure, so activating the display/update of resource list.

As soon as a node is expanded, another double click on such node would collapse treestructure to its closed view.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Configuration Menu is divided into:

• NE Time

• Network Configuration

• Alarm Severities

• System Settings

• Cross Connections

• Ring Configuration

• LAG Configuration

• QoS Configuration

• AUX Cross Connections

• XPIC Configuration

• VLAN Configuration

• Traffic Description

• Profiles Management

• Ethernet Features Shell


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 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 MenuConfiguration → Network Configuration → NTP Configuration.

• The NTP Status field shows:

• status of NTP (enabled/disabled);

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

• IP address of the Spare Server (IP address of a second NTP Server), which replaces the MainServer in case of failure.

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

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

• The dialogue box opens, from which the local NE can be set.

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

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

• The Refresh button causes the refresh of the screen.

Note: If a change of Change Time Zone on the PC is applied with the JUSM opened, in order tomake it updated on WebEML Close/Open the JUSM application and Read Time another time.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Network Configuration menu supports the the following operations:

• Local Configuration:

• defines the local virtual NE address

• NTP Configuration

• defines the Network Time Protocol

• Ethernet Configuration

• not implemented

• IP Configuration which comprises:

• IP static routing configuration: defines Host/Network destination address for IP static

routing• OSPF Area configuration: defines the Open Shortest Path First address

• IP Point-To-Point Configuration: defines the IP address of the interfaces which use thePPP protocol (not implemented)

• Routing information:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Select the Network Configuration option and then, from the cascading menu, the LocalConfiguration option.

• The dialogue box opens, which allows to configure the local IP address of the NE. This local IPaddress is the IP address associated to a virtual interface and to the other interfaces which usethe PPP protocol (the TMN-RF channels).

• Apply button - used to perform a configuration change of the data contained in the dialogue boxand 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.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Put a check mark in the NTP protocol field to enable the protocol.

• Enter the IP address in the Main Server address field for the server, that distributes the time toall the NEs in the network. In the Spare Server address field, enter the IP address of the SpareServer.

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

• "Main server reachable"

• "Spare server reachable"

• "None servers reachable"

• "Both servers reachable"

• Click Refresh to update the screen.

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

• Click Close to close the NTP Configuration window.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The following fields and data are present:

• IP Address: IP address necessary to reach a specific host/network

• IP Mask: IP Mask to reach a network

• Default Gateway IP Address: address of the next hop gateway

• Interface type: point to point interfaces made available by the NE.

Host or Network Address:

• For Host, click the Host button and enter the IP address in the IP Address field

• Network, click the Network button and enter the IP Mask of the radio in the IP Mask field

Gateway or Point to Point I/F Choice:

• For default gateway, click the Gateway IP Address, button enter the default gateway IPaddress in the Gateway IP Address field.

• For point to point, click the Point to Point Interface Index button and select Gateway from the Interface Type dropdown menu.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The following fields and data are present:

• OSPF Area IP Address

• OSPF Area Stub

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

• Apply button is used to perform a configuration change of the data contained in the completeRAP table and close the view; the view is visible until the end of the operations and a wait cursoris 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".

• To configure a new area tick the "new" check box to ungray the IP address stub area. Enter the

OSPF Area Address and the OSPF Area Stub Flag (True/False) and press "Create" button toapply and add the area to the table.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Refresh button allows to refresh the information shown in the screen.

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Profile Name field the four alarm severity profiles are listed:

• Profile "No Alarms". With this profile all alarms are disabled.

• Profile "All Alarms". This profile enables the emission of all the alarms.

• Profile "Radio Tx Alarms". This profile enables the emission of the Tx alarms of the radiolink.

• Profile "Radio Rx Alarms". This profile enables the emission of the Rx alarms of the radiolink.

• An Alarm Profile is the complete set of the equipment alarms with their severity in case of Service Affecting situation and No Service Affecting situation.

• Each alarm has its Service Affecting and No Service Affecting attribute, which can differ accordingto the Alarm Severity Profile.

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

1. Select the object to which an Alarm Profile has to be associated.

2. Click on the icon.

The Alarm Severity Profile screen displays.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

3. Select the Alarm Profile to be associated.

4. Put a check mark on the"Show details" box.

5. The list of the alarms with the relevant severity displays.

6. Click Apply to associate the Alarm Profile.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The System Settings window supports system configuration, providing the setting of someparameters for the NE setup. The NE configuration tab-panel has 9 fields:

• Tributary Port Configuration - set the suitable impedance of the E1 stream (Unbalanced 75ohms/Balanced 120 ohm).

• DHCP - configures automatically IP address, IP mask and default gateway of the PC Ethernetinterface used to reach the NE.

• Admission Control for Adaptive Modulation (ODU300 only) – the Admission Control forTDM flows (cross-connected to radio direction working in Adaptive Modulation). Default: “Enabled”.

• Ethernet LOS Criteria - By enabling this feature the following additional criteria are added to

the Core protection switching criteria.• Static Lag Criteria - the Ethernet ports of the Core-E unit in stand-by are in ON state

(enabled) like the ports of the Active Core-E unit, but the Ethernet traffic is not forwarded.

• System Priority Parameter - required to provision the System Priority (2 bytes) associated tothe NE. This parameter, plus the System ID (NE MAC address), determines the System Aggregation Priority ([0 - 1 bytes] System Priority [2 - 7 bytes] NE MAC address)

• Event and Alarm Log – Enables (default) event and alarm logging. When disabled, the eventsare not sent to the Event Log Browser application

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

• SNMP Mode – This field indicates which protocol is allowed for SNMP managers accessing theNE: SNMPv2 or SNMPv3. Default is SNMPv2.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 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:

• The CORE module is on the left side of the screen.

• The even numbered slots of rows 2 to 4 are on the top of the screen.

• The odd numbered slots of rows 2 to 4 are on the bottom of the screen.

• Protection groups are represented by dashed lines

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

• LAG and Ring icons are displayed on the right side of the screen with identifying numbers.

•

LAG and Ring icons• Different icons are used to identify Radio LAG or Ethernet LAG.

• Ethernet ports involved in an Ethernet LAG are only present in the LAG area (not in theCORE-E area).

• In the figure LAG #4 is a Radio LAG, LAG #1 is an Ethernet LAG.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The connectors representing the MSS slots are start- and end-point for actual cross-connections. Byusing the mouse drag-and-drop operations the operator can create cross-connections through thesepoints.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

•White: a connector able to accept a cross-connection and has no active cross-connection yet;

• Green: a connector able to accept a cross-connection and already has one active cross-connection at least;

• Blue: a connector not able to accept a cross-connection.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• This area contains a panel and various components representing NE cross-connectable slots (orconnectors).

• The operator can directly edit with the mouse this graphical area to visually create and modifycross-connections between available connectors.

• The figure shows an example of ongoing cross-connections configuration.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Ring Configuration window consists of the following panels:

• Ring Topologies

• ERP Instances


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The LAG Configuration window consists of the following panels:

• Configured LAGs – Contains status and ID nformation about all currently created LAGs

• LAG Settings:

• LAG information

• Displays information about a LAG selected in the LAG Configuration window.

• Contains changeable fields for Name, Size, Timeout , and Hash

• Allows the selected LAG to be enabled.

• PPP RF – allows enabling of PPP routing information (displays only for L1/L2 radio LAGS)

• Available Ports: displays port information (Slot, Port User Label) about ports that can be

added to the LAG.

• Added Ports – Lists ports that are added from the Available Ports panel.

• LAG Creation window

• ID drop-down menu - select lag ID number (1-14).

•Name - Enter the LAG name, optional (up to 32 characters max.).

•Type drop-down menu - select (L1 Radio, L2 Radio, or L2 Ethernet).

•Size drop-down menu - select LAG size (for L1 Radio (1-4), for L2 Ethernet/Radio (1-8))

•Key drop-down menu - If Type is L2 Ethernet/Radio, then select Admin Key value (1-32).

• LACP drop-down menu - L2 Ethernet, select LACP support ( Active, Passive, or Disabled).

•Timeout - timeout period (Short or Long).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The QoS Configuration menu has 3 tab-panels:

• Scheduler Configuration

• Queue Size Configuration

• QoS Classification


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

In the figure the default configuration is shown.

• Mode field – contains a drop-down menu that contains the following queue scheduling algorithmselections:

• SP – Strict Priority

• DWRR – Deficit Weighted Round Robin

• Weight field – priority weight (1-32)

• Restore button – return to the previous configuration.

• Defaults button – return to the default settings.

• Apply button – applies changes to the NE

• Refresh button – resets unapplied changes


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Each queue can have an assigned buffer size (in bytes) for each radio direction. For example, Q4for radio direction #7.1 has a buffer size of 100000 bytes with a maximum delay of 8 msec.

• Note: If you float the cursor over field, the current and default values of the queue size withrelevant conversion in msec are displayed.

• Copy and Paste buttons - Copy and Paste the parameters of one Radio direction can be copiedto another Radio direction.

• Restore button – return to the previous configuration

• Defaults button - return to the default settings. Note: The Default button only shows thedefault values. Press the Apply button to confirm the default values.

• Apply button – apply changes to the NE.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The classification can be done according to:

• IEEE 802.1p

• DiffServ

• Select the suitable classification in the QoS Classification Criterion field and press Apply.Then click Yes.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Two types of AUX Cross-Connections can be implemented:

• Local User Service Channel Cross-Connection

• Service Channels Cross-connection in pass-through

Local user service channel cross-connection

The two local 64 kbit/s service channels on the AUX peripherial can be cross-connected to anODU300 radio link, with one of the three radio service channels (service channel to MPT is notsupported in this release).

Service channels cross-connection in pass-throughIt is possible to cross-connect each individual radio service channel with a radio service channel of another radio direction, without any local termination.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

1. Select the first termination point in the New Cross-Connection area (this can be a localservice channel or a service channel in a radio link).

Note: the local service channel must be first enabled in the AUX unitsetting menu.

2. Select the second Termination Point as shown in the example in the figure.

Note: the cross-connections are bi-directional.

3. Click on Add. The new cross-connection will appear in the list (upper part of the screen asshown in the figure).

Note: The Apply button is not operational in this release.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

1. Select the Cross-Connection to be deleted (see the figure).

2. Click Delete. The selected cross-connection is removed from the window.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The 1+1 XPIC Configuration consists of two groups of 1+ HSB with different polarization.

• The XPIC Configuration menu opens by clicking on the relevant button on the Tool bar.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• When the NE is configured in this mode (default configuration), the Ethernet traffic is switchedaccording 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.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• New - create a new VLAN (refer to VLAN table management)

• Edit - change the parameters of a VLAN (VLAN name, VLAN member ports, VLAN untagged portsin egress).

• Delete: 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 iningress to untagged frames.

• Export - export the VLAN configuration in a file with extension CSV. The file can be stored in thePC to be read later.

• Filter – display a filter by inserting a name in the "Filter by Name" box and clicking on Filter.

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

• Refresh - the VLAN table is updated.

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

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

WARNING: The VLAN ID values configurable must be in the range 2 - 4080. The VLAN IDsalready defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) cannot be used. Themanagement system prohibits the definition of VLAN ID already used. The VLAN ID must bedifferent also from the Flow Id associated to E1 tributaries not yet cross connected.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• If a Radio LAG or an Ethernet LAG has been created, they will appear in the VLAN management,as shown in the figure.

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.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Create or delete the traffic descriptors, that will be associated to the ATM traffic at the ingressand/or at the egress.

• To create a Traffic Descriptor:

1. Select the domain: ATM (if in the NE the ASAP unit is present) or PWE3 (in the repeaternodes or in the nodes, where an Ethernet termination is present)

2. Insert a label to identify the Traffic Descriptor

3. Configure the following parameters:

z Service Category: CBR, UBR+ or UBR (rtVBR and nrtVBR are not managed)

z Conformance Definition: CBR.1 (VBR.1, VBR.2, VBR.3 are not managed)

4. Configure the following TD Parameters: PCR, CDVT, MDCR

5. Enable or disable the Policing. For each VP/VC it is possible to enable/disable a cell-based ATM Policing, based on the related ingress ATM Traffic Descriptor. The default configurationof ATM Policing is according to configured Service Category:

z enabled for VP/VC having Service Category CBR;

z disabled for VP/VC having Service Category UBR+ and UBR.

6. Click on Create

7. The already created Traffic Descriptor will appear in the List Traffic Descriptors area.

• To delete a Traffic Descriptor:

1. Select in the List Traffic Descriptors area the Traffic Descriptor to be deleted and click onDelete.

Note: The maximum number of ATM Traffic Descriptors configurable on a NE is given by 2 times the maxnumber of configurable VPs multiplied by max number of ASAP Cards that can be hosted: 2 (2 trafficDescriptors per circuit) x 128 (128 circuits max.) x 6 (6 ASAP units in the NE max.).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

z UBR+ Service Category is defined as an UBR Service Category with Traffic DescriptorParameter 3 (MDCR) > 0

z ATM Traffic Descriptor Parameters for VP/VC rates (PCR,SCR) are defined in terms of cell/second, for CDVT the unit is microseconds, for MBS the unit is cells

z Range for ATM Traffic Descriptor Parameters with VP/VC rates is 0 to the bandwidth of relatedphysical or logical ATM interface, range for CDVT is 0 to 40000 microseconds, range for MBS is0 to 1000 cells.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The default Operator Name is “initial”.

• The default Password is “adminadmin”.

• According to the operator authentication (correct couple username/password) managed by theNE, the operator will be authorized or not to continue. If the login parameters are not correct, anerror message will be displayed, while the Login window is still open for a new attempt. After 3consecutive 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 operatorwill 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. Moreover thepassword length must be not longer than 20 characters.

• The existing passwords less than eight characters (e.g., 6 or 7 characters), created witholder software versions, are accepted and maintained.

• Password composition: the password can include full ASCII characters set (UPPER/lowercase, 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.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Create button – opens the Create User window to enter information for a new user.

• Change PW button – opens the Changing Password window to change a user’s initial password.

• Cancel button – closes the Profiles Management window.

• Help button – displays the help browser with context sensitive help information.

• By clicking on Users Management the window displayed in the Figure appears.

• The operator can perform the following actions:

zCreate a new User by clicking on the Create button.

z After the selection of a user in the table, the operator can perform the following actions:

Delete an existing User (the Initial and Craftsperson Users cannot be deleted) by clickingon the Delete button.

Change PW (by Administrator) by clicking on the Change PW button.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

•The supported profiles are:• Administrator: full access also for security parameters

• Operator: person in charge to operate at network level (not at radio side)

• CraftPerson: person in charge for installation and the maintenance at radio site; full access to NE but not for securityparameters, only for own password

• Viewer: only 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 tochange:

• ATPC configuration (enabled, disabled)

• Performance Monitoring management

• start/stop CD

• threshold tables configuration

• reset

• archiving (only for NMS system)

• Supported for all the types of Performance Monitoring (Radio Hop/Link, E1, Received Power Levels, ....)

• NTP protocol:

• Enabled/Disabled

• NTP main server address configuration

• NTP spare server address configuration

• CraftPerson profile: This operator has the same privileges of the Administrator, but cannot manage the user accounts

• Viewer profile: This operator can only read and can change his own password.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• By clicking on Apply button, at first JUSM performs a syntax check of each field: if there aresome 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 thewindow, 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.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

1. Select a user in the profile table in the Profiles Management window.

2. Clicking the Delete button. A Deletion Confirmation dialog box is displayed.

3. Click the Yes button on the dialog box. The Delete User window is displayed.

4. Enter the administrator password.

5. Click the Apply button to delete the user (or click the Cancel button to stop the deletion and

close the window.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Administrator can change the password of another user with the following procedure:

1. Select the Configuration > Profiles Management > Users Management menu item.

The Profiles Management window is displayed.

2. Select the user in the profile table whose password will be changed.

3. Click the Change PW button.

The Changing Password window is displayed.

2. Enter the following in the respective fields:

• Old Password (existing user’s password)

• New Password

• Confirm New Password

4. Click the Apply button to accept the new password or Cancel to abort the change and closethe window.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

1. Select the Configuration > Profiles Management > Change Password menu item.

The Changing Password window is displayed.

2. Enter the following in the respective fields:

• Old Password (existing password)

• New Password

• Confirm New Password

3. Click the Apply button to accept the new password or Cancel to abort the change and closethe window.

Once the Apply button is clicked, the system performs a syntax check of each field: if there areerrors, the system will display the specific message and allow the user to correct the errors.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The keywords are in bold the variables , are in italics.

• To know if an MPT is grouped in a radio LAG, letter L is placed on the MPT icon on the Equipmentview, but in this view it not possible to see the association of a specific MPT to a specific RadioLAG.

• To know if an Ethernet user port is grouped in an Ethernet LAG, in the CORE-E domain in theEthernet Physical Interface tab-panel the Settings tab-panel of the Ethernet port grouped in aLAG is gray (no changes can be done), but it not possible to see the association of a specific UserEthernet port to a specific Ethernet LAG.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Diagnosis Menu contains:

• Alarms

• Log Browsing

• Remote Inventory

• Abnormal Condition List

• Summary Block Diagram View

• Current Configuration View

• Performance Monitoring


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 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 as follows:

1) CRI contains all the alarms having a CRITICAL severity

2) MAJ contains all the alarms having a MAJOR severity

3) MIN contains all the alarms having a MINOR severity

4) WRG contains all the alarms having a WARNING severity

5) IND contains all the alarms having an INDETERMINATE severity

6) CLR contains all the alarms which are in the CLEARED state, that is, which are no longer

active (this filter is available within the list ALARM_LOG only).The number of active alarms is shown inside brackets.

• The two lists can be filtered using customized filters provided by means of the menu Filters→ Add a Filter

• When an alarm is no longer active it disappears from the current Global list and it is displayed inthe ALARM_LOG list as a cleared alarm.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• When the application is opened for the first time, only the tab-panels of the two global lists aredisplayed on the right part of the window.

• Click on a filter or on a global list on the left part of the screen shows up on the right side therelevant tab panel with all the alarms.

• At the top right, the field Synthesis shows the number of active alarms for any severity.

• The alarms have a different color according to their severity and their state.

•

Red: CRITICAL alarm• Brown: MAJOR alarm

• Yellow: MINOR alarm

• Blue: WARNIG alarm

•White: INDETERMINATE alarm (Note that the equipment has no alarm having such severity)

• Green: CLEARED alarm (alarm no longer active).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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/ddhh:mm:ss.

• Probable cause: name of the probable cause of the alarm.

• Alarm Type: alarm class (TRS = Transmission Alarm – alarm not created inside theequipment, but generated by a connected equipment or due to transmission/propagationproblems; EQUIPMENT: inside alarm of the equipment).

• Friendly Name: object of the equipment where the alarm occurred.

• Severity: alarm severity.

• Add Text: this is an additional text regarding the alarm.

• Specific problem: for some alarms, additional information is provided about the involvedresource (for instance, when a threshold alarm is raised, it states the specific thresholdexceeded)


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Save Log for selected NE

• 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 inthe opening window.

• Load Log to selected NE

• Display the global list of a certain NE previously saved.

• Remove selected NE

•

Remove an NE, selected in the list.

• Export Alarms

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Filters menu provides the following menus:

• Close Filter - Close a currently opened filter

• Add a Filter …

• Edit Selected Filter …

•Delete Selected Filter …

•Delete Filters …

• Save Filters As …

• Load Filters From …


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Filter Name field

• Enter the filter name in the Filter Name field.

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

• Scope field

• Select APT (Current) to create a filter showing the current alarms only or select Log to create a filterfor 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 byselecting one or more NEs using the mouse.

• Alarm Type field

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

• TRS = Transmission Alarm

• EQUIPMENT = Equipment alarm

• Perceived severity field

• Select Perceived severity and then one or more severity levels and/or Cleared state to filter the alarmhaving the selected severity levels.

• Event Time field

• Select Event Time and then enter the starting date (From) and the ending date (To) to filter the alarmscreated during that specific time frame only.

• Probable Cause field

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

• Resource field

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Cancel previously created Filters. 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.

• Click on the Cancel button to clear all the selections.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• Clicking on the Cancel pushbutton cleasrs all selections.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Click on Browse to navigate and then choose the filter file to be loaded. The Scope and theLoaded Filters columns will show respectively the NE list and the filters list made available bythe 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 instanceentering <Vim>, the names of the filters change from APT to VimAPT.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The following information is provided for each event:

• Time: date and time of occurrence of the event. The format is week day/month/dayhh: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.

• Event Log Browser is an application which allows to display all the events occurred in the NE.The max. number of stored events is 500. An event is meant to be:

• a configuration change

•

a change of the value of an attribute• an automatic switchover

• a manual operation carried out by the operator.

• The Menu Bar provides the following menus:

• File

•Help


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The file can have the HTML, CSV , PDF or XML format. The file can store all the events ( Allentries) 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.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• An abnormal condition is generated each time:

• a non usual condition is present in the NE,

• detected automatically (i.e. automatic Tx mute)

• as consequence of management systems operation (i.e. force switching, loopbacks, manualTx 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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

•Each block has its Alarm indicator (colored ball icon) that shows the alarm status by color.

• The Core-E has 2 alarm indicators in case of Core-E protection (as shown in figure) and only 1 alarm indicator (the ballicon on the left side) in case of unprotected configuration.

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

• Different icons identify Radio LAG or Ethernet LAG. In figure LAG #4 is a Radio LAG, LAG #1 is an Ethernet LAG.

• An Ethernet User port involved in an Ethernet LAG disappears from the CORE-E area (in figure port #1 and #2 aregrouped in Ethernet LAG#1. Port #5 and #6 are not shown because are optional and have not been configured.

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

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

• by double clicking on the Alarm indicator the relevant active alarm is displayed

• by double clicking on the Abnormal Condition List box, it is possible to navigate to the Abnormal Condition Listmenu;

• by double clicking on the TMN Local Interface box, it is possible to navigate to the TMN view in the Core-E unit;

• by double clicking on a PDH slot icon, it is possible to navigate to the secondary view for the PDH unit;

• by double clicking on a Radio slot icon, it is possible to navigate to the secondary view for the Radio unit;

• by double clicking on an MPTACC slot icon, it is possible to navigate to the secondary view for the MPTACC unit.

• by double clicking on a Protection switch the relevant configuration is displayed;

• by double clicking on a Loopback the relevant configuration is displayed.

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

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

• The green line is the current active path.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Current Configuration View contains configuration information that is organized into thefollowing categories

• Site Name & Location

• Quality of Service Configuration

• Trusted Managers

• Core Configuration (including Ethernet ports)

• LAGs Configuration

• Slots Configuration (occupied slots in MSS-8 or MSS-4)

• XPIC Association Interface

• OSPF Areas• MTP Configuration

• DHCP Configuration

• TMN Ethernet Interface

• TMN Inband Profiles

• Static Routes


• Ring

• Bridge

• Synchronization• Software Package Status


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• To control the competition of the OS and the WebEML, a Local Access Control (LAC) is available.

• If the LAC is “access denied”, it means that the OS manages the NE and the WebEML is notallowed to modify the NE configuration (it can only «read»). In the view, the icon with a keysymbol has a circular shape.

• If the LAC is “granted”, it means that the WebEML is allowed to manage the NE. In the view, theicon with a key symbol has a rectangular shape.

• If the LAC is “requested”, it means that the WebEML has requested a permission from the OS andis 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.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

•Requested option

When the Requested option from the Access State cascading menu and the OSdoes not answer in a predefined time, it is assumed that the NE is in the Craft access stateand can be managed by a WebEML.

•OS option

Select the OS option from the Access State cascading menu. The NE is nowmanaged by the OS.

•The key symbol icon on the management states of the NE view indicates whether the NE ismanaged by a WebEML or by the OS.

•Local WebEML access is denied on recovery phase after a loss of communication of the NE. Whenthe communication with the NE is lost, the OS automatically recovers the communication and forcesthe state existing before the loss of communication (therefore, WebEML access can be denied orgranted).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Backup function saves the NE configuration using the WebEML.

• To backup the configuration write the filename in the File Name field and press Save.

• Confirm the backup operation by clicking Yes to start the operation.

• When the backup is completed in the upper part appears the list of the previously createdbackups.

Warning: The backup file name must not include the following characters: space, &, /.The file name contains always the version as prefix (example: "V020100", corresponding to version V2.1.0; "V030400", corresponding to version V3.4.0). This prefix is inserted automatically by theSW, when the MIB back-up file is created, and is used automatically by the SW, when the MIB

restore must be performed.

• There is one default repository folder of MIB back-up files for all NEs having the same SWP-release.

• The folder name is "backup", and is under the path where you have performed the Local copyof WebEML(Jusm/CT).This folder is automatically selected when you perform any of the commands of the MIBmanagement menu.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Restore/Activate function downloads and activates a previously created backup using theWebEML.

• Select one of the backups to be downloaded in the upper part and press Open.

• Confirm the restore operation by clicking Yes to start the operation.

• When the restore is completed a message displays prompting for activation of the restored file.Click Yes.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Remove file function removes selected backups from the list.

• To remove a backup select the file in the upper part and press Remove file.

• Confirm the operation by clicking Yes to start the operation.

• By pressing Refresh the list in the upper part of the screen is updated.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The following fields are present:

• RMU Serial Number: in this read-only field appears the Serial Number of the Flash Card.

• License String: in this read-only field appears the type of the license written in the Flash Card.

• License Key: this field is used to upgrade the license. To upgrade the license copy in this fieldthe code of the new license and click on Apply.

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The ODU300 is identified by a number indicating the slot number in the MSS, where the Modemunit is installed.

• The MPT-HC or MPT-MC (ETSI market) is identified by two digits:

• the first digit indicating the slot number in the MSS, where the MPT Access unit is installed(if the MPT is connected to the port of the Core-E unit the digit is 1),

• the second digit indicating the enabled Ethernet port in the MPT Access unit or in the Core-E unit (from 1 to 6).

• The icon of the MPT-HC or MPT-MC will appear only if the MPT Access unit has been configured inthe MSS and one port (from 1 to 4) has been enabled.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Resource Tree area contains a list of empty slots that have to be configured.

The icon is used to identify an empty slot.

To configure a card:

1. Select a slot.

2. Click the Settings panel.

3. Select the unit type in the Equipment type profile.

4. Click Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

For every unit there are 3 tab-panels:

• Alarms

• Settings

• Remote Inventory


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Alarms tab panel provides the fault management, which checks the current state of alarmsrelated to the selected object.

• The alarm tab panel has one row for each possible alarm, but only rows related to the activealarms are highlighted. When the alarm disappears it is automatically cleared in the screen.

• Clicking the Include alarms from sub-nodes check box causes the alarms currently active inthe sub-nodes of the object to appear.

• For every alarm the following information is given:

• Severity: the severity associated to the alarm and assigned in the Alarm Profile

• Event Time: the time of the generation of the alarm

• Entity: the entity involved in the alarm

• Probable Cause: the probable cause of the alarm


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• Equipment Type

• Alarm Profile

• Protection Type Configuration

• Protection Type Configuration with MPT Access unit

• Protection Type Configuration with STM-1 units

• Unit stacking


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The operator must set for all the slots the expected equipment type.

• The list box shows the expected equipment type for slot 3 to 8;

• Select the unit type in the equipment type profile and click Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Core-E Ethernet ports can be configured in 2 ways:

• GigaEthernet interface for Ethernet traffic (Note: for port#5 and port#6 the optional SFPmust be installed);

• MPT interface: MPT-HC or MPT-MC to port#1 to port#4; an MPT-HC only to port#5 andport#6.

• Select the option (SFP or MPT-HC/MPT-MC) and click on Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In the Setting tab-panel one or two of the four Ethernet ports (to be connected to the MPT-HC orMPT-MC) must be enabled as shown in figure above.

• Select as Usage MPT-HC or MPT-MC (in 2 ports max) and click on Apply.

• Port#1 and Port#2 are electrical Ethernet ports and Port#3 and Port#4 are optical Ethernetports.

• Port#1 and Port#3, Port#2 and Port#4 are mutually exclusive.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Settings tab-panel of the STM-1 unit is shown above.

• The Equipment type can be "SDHACC" or "SDHCHAN"

• Select the optical SFP (SFP-O) or the electrical SFP (SFP-E) installed on the STM-1 ports(SFP#1 and/or SFP#2 with SDHACC, only SFP#1 with SDHCHAN) and click Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Port #5 to #8 can be configured to accept an optical SFP.

• Select option SFP and click Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

This function relates to an alarm severity profile to be assigned to a selected object (it has beenimplemented in MSS shelf, in Local TMN Ethernet interface and in the Radio object).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• This function allows the operator to configure the NE protection type. This function is shownselecting slots 3 to 8 only.

• Configuring a 1+1 protected board, if peer board is not configured, the WebEML will be in chargeof applying such configuration to un-configured peer board, before creating protection in MIB.

• If the user applies a new expected protection type, both tree view and configuration panel arereloaded and updated. With a configured 1+1 protection, involved slots are bounded by lightgreen lines.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

To configure the protection scheme select the MPT.

1. In the example MPT-HC#52: connected to Port#2 of the MPT Access unit in Slot#5.

2. Choose in the Protect Port field one port available in the list. As protection can be also usedan MPT connected to the same MPT Access unit.

3. Choose the suitable Protection Type (1+1 FD or 1+1 HSB) and click on Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

After the configuration in the screen will appear the two jointed MPT-HC.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The field Protection Type appear only when the 2 STM-1 units have the same configuration (onlywith SFP-O, not with SFP-E).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Two MPTACCess units or two P8ETH units installed on the same row are automatically grouped ina stacking configuration.

• The stacking configuration is highlighted in green as shown in the following figure (units in slots#3 and #4).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Selecting from either the equipment tree or the resource area will display remote inventory data if it is available.

• The Remote Inventory tab displays information for a piece of equipment that is selected eitherfrom the resource tree or from the work area.

• In the example above, the Core-E card (Slot#1 MSS/CORE-MAIN) is selected from the ResourceTree. It is also highlighted in the MSS-8 that is displayed in the work area.

• Clicking on the Remote Inventory tab displays information for the selected Core-E card in theexample.

• A read-only copy of the remote inventory for the entire NE can be generated from the Diagnosis Menu.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The 1+1 protection schemes implemented are:

• Equipment protection: EPS protection in Tx and Rx sides (this protection scheme can beimplemented for all the unit types: Modem unit, PDH unit and Core-E unit)

• Rx Radio protection: RPS Hitless Switch in Rx side

•HSB protection: Hot Stand-by protection (available for the Radio unit only)

• FD protection: Frequency Diversity protection (available for the Radio unit only)

• The Synchronization protection scheme will appear, if in the synchronization tab panel thePrimary Source and the Secondary Source have been selected or the NE has been configured asMaster with Free Running mode.

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

• For the pair of Radio units or MPT Access units the protection type are the EquipmentProtection, Radio Protection and HSB Protection or FD protection.

• For the pair of PDH units the only protection type is the Equipment Protection.

• For the pair of SDH units the only protection type is the Equipment Protection (ETSI market).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Protection Scheme Parameters

• The tab-panel “Scheme Parameters” displays the parameters that can be modified.

• The parameters are:

• Protection Type: this parameter is defined at creation time and it is read only. The supportedtype 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 channelis allowed (revertive mode) or inhibited (not revertive mode). The operator choice for “Restoration Criteria” will be applied by clicking on “ Apply” button.

• The Core-E protection type is Not-Revertive and cannot be changed. The PDH/SDH protectiontype is Not-Revertive and cannot be changed.

• In case of 1+1 HSB-EPS, the restoration criteria are always grayed out. No changes can be doneseparately for 1+1 HSB-EPS. The restoration criteria selected for HSB-TPS will be applied to EPSautomatically.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Synchronization window contains the following settings panels:

• Sync Ports

• Role

• Restoration

• Primary Source

• Secondary Source

The Synchronization window contains the following buttons:

• Apply

• Help

• Refresh

• SSM Summary


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The physical interfaces to be assigned to Primary and Secondary synchronization sources can bechosen among the following:

[1] Free Run Local Oscillator. Quality Level value is fixed to QL-SEC/EEC1 (G.812/G8262), thevalue of QL Priority is Master1 if the NEC is configured as Master and Slave1 if the NEC isconfigured as Slave.

[2] Any E1 available at input traffic interfaces (the specific E1 port has to be chosen). Defaultvalue for Quality Level is QL-SSU-A (G.812).

[3] A specific synchronization signal available from the dedicated Sync-In port, which can beconfigured according the following options:

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

c) 10 MHz, + 6 dBm into 50 ohm, sine-wave;

d) 1.024 MHz, electrical levels according to G.703, clause 13 with the followingexceptions:

{ timing properly scaled from 2.048 MHz to 1.024 MHz.

[4] The Symbol Rate of the RX signal of any available Radio (the specific Radio Port has to bechosen). When the SSM support is enabled the QL and QL Priority are acquired from ESMC PDUsreceived on the specific radio interface.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The physical interfaces to be assigned to Primary and Secondary synchronization sources can bechosen among the following:

[5] Any Synchronous Ethernet clock source available at enabled User Ethernet traffic interfaces(both electrical and optical) configured in synchronous slave operation mode (the specific UserEthernet port has to be chosen).

[6] Any STM1 available at SDH input traffic interfaces (the specific STM1 port must be selected).

[7] None of the above, this means that no physical synchronization interface is assigned to thesynchronization clock source input. In case of failure of the other clock source input the CRUenters the Holdover state.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Some rules have to be followed while assigning the Primary and Secondary clock sources.

The NEC has to be defined (configured) as Master or Slave.

• If a specific interface is chosen as Primary, it cannot be selected as Secondary too.

• If an E1/T1 is chosen to be Primary source, another E1/T1 coming from the same peripheralcannot be selected as Secondary source and vice-versa.

• If an MPT radio interface is chosen to be Primary source, another MPT radio interfaceconnected to the same MPT Access peripheral cannot be selected as Secondary source andvice-versa.

• If an STM1 is chosen to be Primary source, another STM1 coming from the same peripheralcannot be selected as Secondary source and vice-versa.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Only one Master is allowed in the network.

• If Master:

• The Restoration Mode must be chosen between Revertive and Non-Revertive;

• The Primary clock source input must be chosen among 1), 2), 3), 5) or 6).

• If the selected Master Primary clock source input is 1:

• the Master Secondary clock source input doesn't need to be selected because the Primary isnever supposed to fail. If the selected Master Primary clock source input is 2), 3), 5) or 6):

• the Master Secondary clock source input must be selected among 1), 2), 3), 5), 6) or 7).

• If Slave:

• The Restoration Mode is fixed to Revertive.

• The Primary clock source input must be chosen among 3), 4) or 5). Slave Primary clock source input is allowed to be 3) or 5) for full indoor configuration and for Piling configuration.

• The Secondary clock source input must be chosen among 1), 2), 3), 4), 5), 6) or 7).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

By pressing the SSM Summary button the SSM summary Table opens, which shows the SSM status(enabled/disabled) of the interfaces carrying the SSM messages.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

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

•

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

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

This is another method of monitoring alarms.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Your 9500 MPR username and password


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Dynamic Host Configuration Protocol (DHCP) is a client/server protocol that automatically provides anInternet Protocol (IP) host with its IP address and other related configuration information such as thesubnet mask and default gateway.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Community String (CS) acts like a password to control access to an NE. It defines whatcommunity of people can access the NE.

• Two community strings are supported:

• Get CS

• Default value: public

• Both Read and Read-Write objects operate in Read mode only

• Set CS

• Default value: private

• Both Read and Read-Write objects operate in their respective modes

NOTE: Provisioning new Community Strings will cause a loss of communication on ALL NEtOsession currently active.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 Configuration View 71.1 Configuration View screen 8 2 ODU300 Views and Settings 112.1 Equipment View - Radio Modem 122.2 MOD300 Settings - Direction area 132.3 MOD300 Settings - Direction area 162.4 MOD300 Settings - Channel area 17 3 MPT-HC Views and Settings 193.1 Equipment View - Radio Modem 203.2 Direction area 213.3 Channel area 283.4 Power Source 32 4 MPT-MC Views and Settings 33

4.1 Direction area 344.2 Channel area 394.3 Channel area 414.4 Channel area 42 5 Radio Measurements Tab 435.1 Radio Modem Power Measurements Graphic 445.2 How to read a Power Measurement file 48 6 MPTACC Settings 496.1 Provision MPTACC 50 7 PDH Access Card Views and Settings 577.1 Provision Plug-In Cards 587.2 Provision Plug-In Cards 59 8 SDH Access Card Views and Settings 63

8.1 Provision Plug-In Cards 64 9 Ethernet Ports Configuration 699.1 CSM-E/Core-E Ethernet Ports 709.2 EAS/P8ETH Ethernet Ports 719.3 Advanced Ethernet functions for Core-E, EAS, and PETH 729.3.1 Storm Control Ingress 739.3.2 Port Rate Limiter Ingress or Egress 749.3.3 VLAN Rate Limiter Ingress 759.3.4 C-VLAN Translation 769.4 Per-VLAN-Per-CoS Rate Limiter 779.5 TMN Interface 829.6 TMN In-band 839.7 TMN Ethernet port 84

10 Ethernet Ring Configuration 8710.1 Ethernet Ring Protection (ERP) overview 8810.2 ERP Configuration Procedure 8910.3 Configuration example of an Ethernet ring 97 11 QoS Configuration 9911.1 QoS Configuration - Queue Size Configuration 10011.2 QoS Configuration - QoS Classification 10111.3 QoS Configuration - QoS Classification 105 12 LAG Configuration 11112.1 LAG Creation Rules 11212.2 LAG Creation 11312.3 LAG Removal 117 13 XPIC Configuration 119

13.1 XPIC Configuration 120 14 VLAN Configuration 12714.1 VLAN Configuration - 802.1Q 128

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

14.2 VLAN Configuration - Ethernet Ring 130

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Current Configuration View contains configuration information that is organized into thefollowing categories

• Site Name & Location

• Quality of Service Configuration

• Trusted Managers

• Core Configuration (including Ethernet ports)

• LAGs Configuration

• Slots Configuration (occupied slots in MSS-8 or MSS-4)

• XPIC Association Interface

• OSPF Areas• MTP Configuration

• DHCP Configuration

• TMN Ethernet Interface

• TMN Inband Profiles

• Static Routes


• Ring

• Bridge

• Synchronization• Software Package Status


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



The File menu supports the following:

• Save As – Save the configuration view as a text file.

• Print – Send a copy of the configuration view to a printer.

• Exit – Close the Configuration View screen.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• The switching between the modulation schemes is hitless and maintains the same RF channelbandwidth.

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

• Example: if the default switching threshold is -64 dBm by setting +4 dB the new value is -60

dBm and by setting -2 dB the new value is -66 dBm.

• Note: If the current Modulation scheme is 4 QAM, it not possible to force to 64 QAM, but first must be forced to 16 QAM and then to 64 QAM. Also if the current Modulation is 64 QAM, to passto 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 toincrease or decrease the part of the screen relevant to the parameters of the AdaptiveModulation.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

3) Link Identifier

This part allows the operator to define the expected and sent identifier values of parameters relatedto the link management and, if necessary, modify them.

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

If the Link Identifier is Enabled the following fields can be written:

zExpected Identifier: this field is the link identifier expected at the receiving NE

zSent Identifier: this field is the link identifier inserted on the transmitting NE (range: 1-256).

4) PPP RF

The “PPP-RF” interface is a communication interface based on the use of an inframe RF proprietary64 kbit/s channel. Through the “PPP-RF” interface the NE can exchange management messageswith a remote OS (or Craft Terminal) station.

The PPP-RF channel can be Enabled or Disabled.

5) Alarm Profile

Not implemented in the current release.

6) Synchronization

Tick on Enable to enable the transmission of the SSM message over the radio channel.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

1) Frequency - The system can operate with different types of ODU according to the RF bandand to the channel arrangement. In the Shifter field select the suitable shifter. In the Tx frequency field insert the suitable Tx frequency and press Apply. Press the Data Help button the list of all the available ODUs with the relevant P/N, shifter and Tx frequency willappear. The Data Help table is useful, if you are not connected to the ODU.

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

3) Manual Transmit Power Control

Manual Transmit Power Control (without Adaptive Modulation) - If the ATPC is disabledthe manual Tx Power field is present. For the Tx Power range refer to the table.

Tx Power (with Adaptive Modulation) - The operator can modify only the 4 QAM field. Inthis field the operator has to enter the constant power, which will be used with 4 QAMmodulation.

4) Tx Mute - The information related to the transmitter status is shown in the Tx Mute field(Off/Manual/Auto). To squelch the transmitter select Enable and press Apply button.

5) Alarm Profile - By clicking on the icon the Alarm Severity Profile menu opens, which allows toassociate to the radio channel a specific alarm profile. Select one Alarm Profile in the ProfileName list (4 alarm profiles are listed) and click Apply. Tick the Show details check box to see theseverity associated to each alarm.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:


• The SDH capacity mask must be selected in the following two profiles:

z In the first case 1xSTM-1 or 72 E1s can be transmitted.

z In the second case 2xSTM-1 or 145 E1s can be transmitted.

CS (MHz) FCM Mode Modulation # E1 TDM2TDM # STM-1 SDH2SDH

28 128QAM 72 1

56 128QAM 145 2


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Adaptive Modulation in a Point to Point system adjusts the modulation as well as a range of othersystem parameters based on the near-instantaneous channel quality information perceived by thereceiver, which is fed back to the transmitter with the aid of a feedback channel.


• Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB/1+1 FD) Radioconfiguration without ATPC).

• The SDH capacity mask must be selected in the following two profiles:


z In the second case 2xSTM-1 or 145 E1s can be transmitted.

Note: The Remote Switching Threshold is not supported.

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 to4 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 toincrease or decrease the part of the screen relevant to the parameters of the Adaptive Modulation.


28 128QAM 72 1

56 128QAM 145 2


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• This field is available only with the MPT-HC V2 with the XPIC+RPS external module installed andif in the Mode area in the Option field a mask with XPIC has been selected.

• Note: The XPIC can be implemented in 1+0 or 1+1 HSB with the Static Modulation or AdaptiveModulation.

• How to configure the XPIC

1. In the Polarization field select the polarization to be used by the radio channel (Vertical orHorizontal).

2. Go in the XPIC Configuration menu by clicking the relevant button in the Tool bar. Refer toXPIC Configuration.

3. Now in the Associated Interface field will appear the radio channel associated in the XPICConfiguration.

4. By clicking on the icon on the right of the Associated Interface field you can navigate to theassociated radio channel menu.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

4) Link Identifier

This part allows the operator to define the expected and sent identifier values of parameters relatedto the link management and, if necessary, modify them. The operator choices will be sent to the NEby clicking on the related “ Apply” button.

If the Link Identifier is Enabled the following fields can be written:

• Expected Identifier: this field is the link identifier expected at the receiving NE

• Sent Identifier: this field is the link identifier inserted on the transmitting NE (range: 0-256).

5) PPP RF

The “PPP-RF” interface is a communication interface based on the use of an inframe RF proprietary64 kbit/s channel. Through the “PPP-RF” interface the NE can exchange management messageswith 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. Inthe Routing IP Protocol field enter the used IP protocol and in case of OSPF protocol select alsothe associated OSPF area.

6) Alarm Profile

Not implemented in the current release.

7) Synchronization

Tick on Enable to enable the transmission of the SSM message over the radio channel.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Channel #1 area is always present (in 1+0 and 1+1 configuration). The Channel #0 area ispresent in 1+1 configuration only.

Warning: To configure the unit first configure the Shifter and the Tx Frequency in theFrequency field (in the Channel menu) and click on Apply. Then configure all the otherparameters.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

1) Frequency

The system can operate with different types of ODU according to the RF band and to the channelarrangement. There are ODUs which can manage only one shifter or several predefined shifters. Inthe Shifter field select the suitable shifter.

In the Tx frequency field insert the suitable Tx frequency (the Rx frequency is automaticallycalculated by using the inserted Tx frequency and the shifter) and press push-button Apply.

In the Rx frequency field will appear the calculated Rx frequency, but this frequency can bechanged in +5 MHz range to implement the “Exotic” shifter configuration, if required. Change theRx frequency and press Apply.

2) ATPC

The ATPC can be Enabled or Disabled.

The new value will be applied when the Apply button is pressed. If the ATPC has been enabled,the ATPC Range and ATPC Rx Threshold parameters must be filled.

ATPC Range

• The Min Tx power and Max Tx power, regarding the Tx Range in the ATPC management,can be written in the relevant field.

• When the Apply button is pressed the new values will be applied.

• ATPC Rx Threshold

• The value of the low power threshold can be changed by writing the new value in the field.When the Rx power is equal to this power the ATPC algorithm starts to operate.



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The same power value will be used by the other modulation schemes


Manual Transmit Power Control (without Adaptive Modulation)

• If the ATPC is disabled the manual Tx Power field is present. For the Tx Power range refer tothe table.

• In this field write the new value within the allowed transmitted power range. The range isshown on the right side of Manual Transmit Power Control area.

Tx Power (with Adaptive Modulation)

•

The operator can modify only the Tx power relevant to the lowest modulation scheme. In thisfield the operator has to enter the constant power, which will be used with the lowestmodulation.

4) RSL Driving Criteria

Select in the RSL Driving Criteria field the suitable value. In 1+1 FD and HSB configurations boththe transmitters can be driven by the lowest or by the highest RSL values of the two remotedemodulators.

5) MSE Driving Criteria

Select in the MSE Driving Criteria field the suitable value. In 1+1 FD and HSB configurations boththe transmitters can be driven by the lowest (1) or by the highest MSE values (2) of the two remotedemodulators.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Two Sources are available because the MPT Access unit can interface two MPT.

• If the Type is Disabled no power supply is provided to the MPT.

• After the power supply selection click on Apply.

• The Alarm Profile field is not supported.

Warning: An MPT-MC or an MPT-HC V2 can be connected to an external Power Injector Box whichadds the Power Supply and the Ethernet Traffic on the same cable. In this case the Power SourceType must be Disabled.

• Mode 1 - QMA (MPT-HC only)

• This mode is the default mode.

• In this mode the MPT-HC is power supplied with a dedicated coaxial cable connected on theQMA connector on the front panel of the MPT Access unit

• Mode 2 - PFoE (Power Feed on Ethernet)

• In this mode the MPT-HC or MPT-MC are power supplied by using the electrical Ethernetcable.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:


• Note: The SDH capacity mask must be selected in the following profile:



28 128QAM 72 1


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Adaptive Modulation in a Point to Point system is to adjusts the modulation as well as a range of other system parameters based on the near-instantaneous channel quality information perceivedby the receiver, which is fed back to the transmitter with the aid of a feedback channel.


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

Note: The SDH capacity mask must be selected in the following profile:


• In 1+1 configuration the Driving MSE field is not supported.

• The Remote Switching Threshold is not supported.

• Example: if the current Modulation scheme is 4 QAM, it not possible to force to 64 QAM, butfirst must be forced to 16 QAM and then to 64 QAM. Also if the current Modulation is 64 QAM, topass 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 toincrease or decrease the part of the screen relevant to the parameters of the Adaptive Modulation.


28 128QAM 72 1

56 128QAM 145 2


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

3) XPIC Configuration - Not available with the MPT-MC.

4) Link Identifier

This part allows the operator to define the expected and sent identifier values of parameters relatedto the link management and, if necessary, modify them. The operator choices will be sent to the NEby clicking on the related “ Apply” button. If the Link Identifier is Enabled the following fields can bewritten:

zExpected Identifier: this field is the link identifier expected at the receiving NE

zSent Identifier: this field is the link identifier inserted on the transmitting NE (range: 0-256).

5) PPP RFThe “PPP-RF” interface is a communication interface based on the use of an inframe RF proprietary64 kbit/s channel. Through the “PPP-RF” interface the NE can exchange management messageswith 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 selectalso the associated OSPF area.

6) Alarm Profile - Not implemented in the current release.

7) Synchronization Click on Enable to enable the transmission of the SSM message over the radio channel.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Channel #1 area is always present (in 1+0 and 1+1 configuration). The Channel #0 area ispresent in 1+1 configuration only.



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Warning: To configure the unit first configure the Shifter and the Tx Frequency in theFrequency field (in the Channel menu) and click Apply. Then configure all the other parameters.

1) Frequency

The system operate with different types of ODUs according to the RF band and channels.

In the Tx frequency field insert the suitable Tx frequency (the Rx frequency is automaticallycalculated by using the inserted Tx frequency and the shifter) and press push-button Apply.

In the Rx frequency field will appear the calculated Rx frequency, but this frequency can bechanged in +5 MHz range to implement the “Exotic” shifter configuration, ipress Apply.

2) ATPC

The ATPC can be Enabled or Disabled.

The new value will be applied when the Apply button is pressed. If the ATPC has been enabled,the ATPC Range and ATPC Rx Threshold parameters must be filled.

ATPC Range

• The Min Tx power and Max Tx power, regarding the Tx Range in the ATPC management,can be written in the relevant field.


ATPC Rx Threshold

• The value of the low power threshold can be changed by writing the new value in the field.When the Rx power is equal to this power the ATPC algorithm starts to operate.



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:



Manual Transmit Power Control (without Adaptive Modulation)

• If the ATPC is disabled the manual Tx Power field is present. For the Tx Power range refer tothe table.

• In this field write the new value within the allowed transmitted power range. The range isshown on the right side of Manual Transmit Power Control area.

Tx Power (with Adaptive Modulation)

The operator can modify only the Tx power relevant to the lowest modulation scheme. In this fieldthe operator has to enter the constant power, which will be used with the lowest modulation.

4) RSL Driving Criteria

Select in the RSL Driving Criteria field the suitable value. In 1+1 FD and HSB configurations boththe transmitters can be driven by the lowest or by the highest RSL values of the two remotedemodulators.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:


5) MSE Driving Criteria

Select in the MSE Driving Criteria field the suitable value. In 1+1 FD and HSB configurations boththe transmitters can be driven by the lowest (1) or by the highest MSE values (2) of the two remotedemodulators.

6) Tx Mute

The information related to the transmitter status is shown in the Tx Mute field (Off/Manual/Auto).To squelch the transmitter select Enable and press Apply button.

The following indications will appear in the Tx Mute field:

• Off : Transmitter not squelch

• Manual: Transmitter squelched due to the manual operation

• Auto: Transmitter squelched due to an automatic operation

7) Alarm Profile

By clicking on the icon the Alarm Severity Profile menu opens, which allows to associate to the radio

channel a specific alarm profile. Select one Alarm Profile in the Profile Name list (4 alarm profiles arelisted) and click Apply. Click Show details check box to see the severity associated to each alarm.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• "Measurement interval" fields - The default is Days: 7, Hours: 0, Minutes: 0. A 7-daymeasurement interval is also the maximum allowed interval.

• "Sample time" field - The choice is among 2, 4, 6, 30, 60 sec. The last section of the dialog isreferred to an optional Log file. By selecting Create File the log file is created and a defaultpath and name for this file is displayed to the operator. The file is stored in theMPRE_CT_V00.07.08 directory.

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

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

By clicking on the "Start" button the screen "Power Measurement Graphic" appears.• The Power Measurement Graphic is available only if the WebEML is connected to the NE.

• The Power Measurement Graphic screen shows the Tx and Rx measurements related to the localand remote NE. The operator can see, in real time, the power transmitted by the local and remotetransmitter (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 areashows 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.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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 starttime

• Time: is the current response time

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• When not receiving any signal, RSL value is not set to a fixed specific value.WARNING:

• Radio analog transmitted power level (local ODU)

• In case of ICP or Cable Loss alarms the value shown at management system is -99.8 dBm.

• In case of mute status the value shown at management system is -100 dBm. I

• f the power level read is out of the allowed range, the value shown by the management system is -101 dBm.

• Radio analog received power level (local ODU)

• In case of ICP or Cable Loss alarms the value shown at management system is -99.8 dBm.

• In case of failure on reading the register containing the received power the value shown at management system is -99.7 dBm.

• If the power level read is out of the allowed range, the value shown by the management system is -101 dBm.

• Radio analog transmitted power level (remote ODU)

•

In case of broken radio link the value shown at management system is -99.6 dBm.• In case of mute status the value shown at management system is -100 dBm. In case of failure on reading the

register containing the remote transmitted power the value shown at management system is -99.7 dBm.

• If the power level read is out of the allowed range, the value shown by the management system is -101 dBm. Incase of alarms on the remote NE on one of the two radio channels in HSB configuration (typically ICP, Cable Loss,Card Missing, Card Fail), the value shown by the management system is -127 dBm.

• Radio analog received power level (remote ODU)

• In case of failure on reading the register containing the remote received power the value shown at managementsystem is -99.7 dBm.

• If the power level read is out of the allowed range, the value shown by the management system is -101 dBm.

• In case of alarms on the remote NE on one of the two radio channels in HSB configuration (typically ICP, CableLoss, Card Missing, Card Fail), the value shown by the management system is -127 dBm.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

1. Click the Read File box and press the Select File button.

The directory of the WebEML automatically opens to navigate to the power measurement file.

2. Select the desired file and click the Open. The selected file will appear in the Log file field.

3. Click button Start (on the right side of the Sample Time field). The file opens.

The buttons in the lower part of the window allow to flow the graph within the measurementinterval.

• As default the measurement files are stored in the MPRE_CT_Vxx.xx.xx directory and haveextension .txt.

• The measurement file can be opened also with a standard text editor (e.g. WordPad). Go in thedirectory where the txt files have been stored and open the file. The measurements are shown inthe tabular mode.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

To unprovision an MPT:

1. perform a Tx Mute

2. unprovision the MPT

3. remove the power supply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• With the Presetting mode the Adaptive modulation is disabled.


• The XPIC can be configured in 1+0 or 1+1 HSB (no adaptive modulation, no ATPC).NOT ALL the channel spacings and modulation schemes can support the XPIC Configuration.

•

Select the suitable Polarization: Vertical or Horizontal.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Flow Id number: is system unique and must not be repeated in radio network. Loss of E1 datacan occur.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Flow ID number is system unique and must not be repeated in radio network. Loss of STM-1 datacan occur.

• J0 byte is only read, no Regeneration section Termination is done.

• Auto LASER Shutdown - This field will appear only if the Settings tab-panel of the STM-1 unit theoptical SFP has been selected.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

[2] Put a check mark in the Port Status box to enable the STM-1.

[3] Set the Auto Laser Shutdown: Enabled/Disabled ForcedOn/Disabled ForcedOff. This field will

appear only if the Settings tab-panel of the STM-1 unit the optical SFP has been selected.

[4] Select the Clock Source.

[5] Enable the J0, if required, by selecting one of the two modes(SixteenBytesFrame/OneRepeated

Byte) in the Expected Receiving Value field and enter the expected value and in theSending J0

field select one of the two modes and enter the value to be transmitted. Note: byte J0 is onlyread,

no Regeneration section Termination is done.

[6] Click Apply.

[7] Enable, if required, the E1 Node Timing Configuration. The Node Timing is the timingfrom the network clock as defined in G.8261. The enabling of the Node Timing is applied to allE1s of the unit. By enabling the Node Timing the E1 streams in Rx side are retimed at theoutput with the network element clock.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

[8] Configure all the E1s to be mapped/demapped in the STM-1. The E1s are identified by aprogressive number from #1 to #63, but also by the standard SDH identification (x-y-z).

The E1 tab-panel performs all available functions for the tributary.

[9] Select Settings.

[10] Signal Mode:The possible values are:

zUnframed for the unframed received signal

zFramed for the collection of the performances at the input in Tx side and at the outputin Rx side

zDisabled

[11] Click Apply.

[12] Service Profile:The possible profiles are:

zTDM2TDM

zTDM2Eth

[13] Flow Id: To implement cross-connections between line side and radio side each E1 tributarymust be associated to an identifier. Enter the Flow identifier value in the relevant field (possiblevalues: 2 to 4080) and press Apply.

[14] Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if theService Profile is TDM2Eth.Note: The service profile must be the same for all the E1s.

[15] Alarm profile: Not implemented now.

[16] Click Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

If the electrical Ethernet port has to be used as Synchronous Source, the Ethernet port must be setas Synch-E Slave.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• C-VLAN Translation - supported on user Ethernet interfaces, the translation is applied bi-directional. Tagged ingress frames entering the User Ethernet interface, C-VLAN ID (From), arechanged to a new C-VLAN ID (To). At the same time, tagged egress frames, C-VLAN ID (To) arechanged to C-VLAN ID (From) exiting the User Ethernet interface.

• Port Based Rate Limiting - supported on user Ethernet interfaces. Port based Rate Limitingallows a user to provision on a per user Ethernet port basis the maximum data rate on ingressand egress directions.

• CIR can be configured in the range from 64 Kbit/s to 1,000,000 Kbit/s at step of 64 Kbit/s.

• CBS (Committed Burst Size) can be configured in the range from 4 Kbytes (4096 bytes) to

16 MBytes at step of 4 Kbytes.• Default value for CIR is 64 Kbit/s, default value for CBS is 12 Kbytes.

• Storm Control (Broadcast, Multicast, and unknown Unicast) - Storm Control provides amechanism to control the effects of broadcast, multicast, and unknown unicast storms on physicaluser Ethernet interfaces. This helps prevent traffic storms from being disruptive anddegrading network performance. The frame rate threshold can be configured in the range from 1Frame to 16.777.215 Frames for all. Default is 100 Frame/s for all.

• VLAN Rate Limiter - Used on Ethernet interfaces for the ingress direction. VLAN based RateLimiter allows a user to provision, on a per VLAN ID basis, the maximum data rate for the ingressdirection


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Per-VLAN-Per-CoS Rate limiter Parameters

• Ingress CIR (Committed Information Rate) - Ethernet throughput not taking into accountPreamble and IFG frames. Range is from 0 Kbit/s to 1 Gbit/s in steps of 64 Kbit/s. Default valuefor CIR is 64 Kbit/s. A value of 0 Kbit/s indicates a drop of the Ethernet flow.

• Ingress CBS (Committed Burst Size) - CBS is configured in the range from 4 Kbytes (4096bytes) to 16 MBytes. Default value for CBS is 16 Kbytes. The allowed values for CBS are: 4Kbytes, 8 Kbytes, 16 Kbytes, 32 Kbytes, 64 Kbytes, 128 Kbytes, 256 Kbytes, 512 Kbytes, 1Mbytes, 2 Mbytes, 4 Mbytes, 8 Mbytes. 16 Mbytes.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Caution: Possibility of service interruption. When a Per-VLAN Per-CoS Rate Limiter is activated inconjunction with a Port Rate Limiter, the Per-VLAN Per-CoS Rate Limiter must apply to Ethernetframes that meet the Port Rate Limiter parameters.



• Ingress CBS (Committed Burst Size) - CBS is configured in the range from 4 Kbytes (4096

bytes) to 16 MBytes. Default value for CBS is 16 Kbytes. The allowed values for CBS are: 4Kbytes, 8 Kbytes, 16 Kbytes, 32 Kbytes, 64 Kbytes, 128 Kbytes, 256 Kbytes, 512 Kbytes, 1Mbytes, 2 Mbytes, 4 Mbytes, 8 Mbytes. 16 Mbytes.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

This tab-panel has 2 tab-panels:

z Alarm tab-panel

zSettings tab-panel


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The TMN In-Band feature allows the extension of the DCN over User Ethernet interfaces used tocarry user traffic.

• Two default TMN In-Band interfaces (TMN In-band #1 and #2) are supported, each having itsown IP address and subnet.

• The TMN traffic delivered In-Band is VLAN tagged and identified by a specific VLAN ID defined bythe operator in the range 2-4080.

• The delivery of TMN In-Band can be enabled on all User Ethernet interface of the Core board,both Optical and Electrical.

• The Ethernet ports involved in a LAG cannot be used as TMN In-band interface.

• If the TMN In-band interface has been configured and the traffic classifier is according to 802.1p,the priority on the TMN traffic is highest. If the traffic classifier is according to DiffServ, the

priority on the TMN traffic is low and the traffic on the other Ethernet ports must be taken inconsideration.

• If two Ethernet ports, associated to the same TMN In-band logical interface, are segregated, thetwo ports do not communicate each other, as for the normal Ethernet traffic (they have the same VLAN ID). If two Ethernet ports, configured in different TMN In-band logical interfaces, aresegregated, the two ports can communicate each other, as they have 2 different VLAN IDs).

• The OSPF and related Area ID can be enabled on a TMN In-Band interface.

• For each TMN In-Band interface the following parameters must be selected:

• IP address and subnet: default 10.0.3.2/24 for interface #1 and 10.0.4.2/24 for interface #2

• VLAN ID: default 4097 for interface #1 and interface #2

• List of User Ethernet interfaces where transmit/receive TMN In-Band traffic: default None

• OSPF enable/disable: default disabled for both interfaces• Area ID in case of OSPF protocol enabled: default 0.0.0.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 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, assignalso the area number.

• Click on the Alarm Profile icon to open the Alarm Severity Profile menu to associate to the TMNEthernet port a specific alarm profile. Select one Alarm Profile in the Profile Name list (4 alarmprofiles are listed). Tick the Show details check box to see the severity associated to eachalarm.

• Click on Apply to activate the selections.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 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, assignalso the area number.

• Click on Apply to activate the selections.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• One designated node, the RPL Owner, is responsible to block traffic over the RPL.

• Under a ring failure condition, the RPL Owner is responsible to unblock the RPL, allowing the RPLto be used for traffic.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Port can be associated only to ODU300 or MPT in 1+0. The East Port and West Port must havethe same type of ODU: ODU300 or MPT.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• All the parameters in “Runtime Parameters” Panel can be modified at run time (ERP Instanceenabled).

• After the operator clicks on Close button, the WebEML checks VLAN Id 1 association. If VLAN Id 1is not associated to any instances, a Warning will alert the operator in order to avoid traffic (if untagged) loop.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In Figure is shown a simple example of an Ethernet ring.

• VLAN Id 100 and an E1/T1 stream (with Flow Id 500) are inserted in NE1 and extracted in NE4and vice versa.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• For each queue and for each radio direction the buffer size (in Bytes) can be assigned.

• A tooltip on each field shows the current and default values of the queue size with relevantconversion in msec.

1. Double click on the relevant field and enter the new value.

2. Click on Restore to go back to the previous configuration.

3. Click on Defaults to go back to the default settings.

The Default button only shows the default values.

4. Press the Apply button to confirm the default values.5. Click on Apply to send to the NE the changes.

• For each buffer size automatically is calculated the max delay in ms.

• By buttons Copy and Paste the parameters of one Radio direction can be copied to another Radiodirection.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

When the Default values are applied (by pressing button Defaults or manually by entering in thefields the default values), check that all the values of the relevant radio directions (for each queue)are equal to the default values, otherwise a Warning message will appear, as shown in figure: forDirection 5.1, in Q3 the default value has been set, in Q4 the value is different from default, all theother queues have the default value.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The classification of the Priority Code Point to a specific queue is done in 2 steps:

• first from the Priority Code Point (P#) to the FC (Forwarding Class): on the left area of thescreen;

• then from the FC (Forwarding Class) to the Egress Queue (Q#): on the right area of thescreen. This association is fixed and cannot be changed.

• Click Apply. Then click Yes.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Click on Apply to send to the NE the changes.

• Click on Restore to go back to the previous configuration.

• Click on Defaults to go back to the default settings.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The classification of the DiffServ Code Point to a specific queue takes place in 2 steps:

• first from the DiffServ Code Point (#) to the FC (Forwarding Class): on the left area of the screen;

• then from the FC (Forwarding Class) to the Egress Queue (Q#): on the right area of the screen.This association is fixed and cannot be changed.

• Click on Apply. Then click Yes.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Click on Apply to send to the NE the changes.

• Click on Restore to go back to the previous configuration.

• Click on Defaults to go back to the default settings.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Click the Table form button to open a read-only table with the current association "DiffServ toForwarding Class Mapping", as shown in the figure.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Warning: the other port of the MPT Access unit must be DISABLED.

• To know if an ODU is grouped in a radio LAG, letter L (followed by the number of the LAG) isplaced on the ODU icon on the Equipment view (example: L01 means that the ODU has beenassociated to Radio LAG #01).

• To know if an Ethernet user port is grouped in an Ethernet LAG, in the CORE-E domain in theEthernet Physical Interface tab-panel the Settings tab-panel of the Ethernet port grouped in aLAG is gray (no changes can be done), but it not possible to see the association of a specific UserEthernet port to a specific Ethernet LAG.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

1. Press the Create button.

The LAG Creation window displays

2. Enter the required information for one of the following LAG types (more detail and examples onnext slide):

L1 Radio

L2 Radio

L2 Ethernet

3. Click Create.

The newly created LAG displays in the Configured LAG panel.

4. Select the already created LAG to complete the configuration process (described on followingslides.)

Note: Link Aggregation Type is used to distinguish between Radio Link Aggregation an EthernetLink Aggregation. After configuring the Link Aggregation Type, the user can change the hashingalgorithm in order to select L2 (distribution of frames based on MAC header and VLAN Tag) or L3(distribution of frames based on IP header). By default L2 hashing is selected.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

a. ID drop-down menu - select lag ID number (1-14).

b. Name - Enter the LAG name, optional (up to 32 characters max.).

c. Type drop-down menu - select (L1 Radio, L2 Radio, or L2 Ethernet).

d. Size drop-down menu - select LAG size (for L1 Radio (1-4), for L2 Ethernet/Radio (1-8))

e. Key drop-down menu - If Type is L2 Ethernet/Radio, then select Admin Key value (1-32).

f. LACP drop-down menu - If Type is L2 Ethernet, select LACP support ( Active, Passive, orDisabled).

g. Timeout - If LACP Active or Passive, then from the Timeout field, select timeout period (Shortor Long).

h. Click Create


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

All of the configured ports display in the Available Ports area.

1. Filter the list according to the ODU type: MPT or MD300.

2. Select the suitable port and click on the Right Arrow button to move the selected port in the Added Ports area.

3. Select the Hash algorithm (L2 or L3).

4. Click the Enabled check box.

5. If required, enable the PPP RF channel and select the OSPF Area.

• The PPP RF channel for TMN is managed here at LAG level and not at ODU level.

• By putting the mouse on a column a tooltip will appear, giving a detail information on the field asshown in next figure.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

All of the configured ports display in the Available Ports area.

1. Select the suitable port and click on the Right Arrow button to move the selected port in the AddedPorts area.

2. Select the Hash algorithm (L2 or L3).

3. Click the Enabled check box.

4. If required, change the priority of the port in the Priority column.

5. If required, configure the VLAN in the VLAN Configuration area. The VLAN configuration is at LAG level(not at port level). The traffic, received on the user Ethernet ports, can be untagged or tagged. Foreach port it is possible to configure:

• Acceptable Frame Type:

Admit tagged only (only tagged frames are allowed in ingress; the untagged frames are dropped)

Admit all (tagged and untagged frames are allowed in ingress)Default value: “Admit all”.

z Port VLAN ID: if the Acceptable Frame Type is set to “Admit all” the VLAN-ID and Priority fields (to beadded 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. VLAN 1 is always removed when the frame isforwarded.

z The Priority values allowed are in the range 0 - 7.The default Port VLAN-ID and Priority values are: VLAN-ID=1; Priority=0.

Untagged frames - The untagged frames received on one user Ethernet port, configured as “Admittagged only”, are dropped.

Priority frames - The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as

“Admit tagged only”, are dropped. The priority packets (VLAN-ID=0) received on one user Ethernetport, with the “Admit all” configuration enabled, are managed as untagged frames for VLAN-ID field,while the Priority field is the same of the received packets.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

1. Remove all the Cross-connections, Segregations, VLANs associated to the LAG, if any.

2. Remove the check on the Enabled check box in the LAG Information area (Radio LAG andEthernet LAG). For Ethernet LAG, go to Step 4.

3. For Radio LAG remove the check on the Enabled check box in the PPP RF area.

4. Remove the ports associated to the LAG: select the ports in the " Added Ports" area, press theLeft Arrow button and click Apply.

5. Click Apply.

6. Click Destroy.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In the XPIC Configuration screen are shown in GREEN the MPT-HC V2 with a mask with XPIC setin the “Option” field (Allowed configurations: 1+0 or 1+1 HSB with or without AdaptiveModulation) previously configured in the Radio menu and with a suitable polarization (vertical orhorizontal) as shown in the above figure.

• To configure the double 1+1 HSB co-channel XPIC follow the following steps:

1. configure the 1+1 HSB protection between the two mate MPT-HC V2;

2. configure the XPIC on the protection radio (in the MPT-HC V2 1+1 Main view configureproperly the Option for XPIC profile).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The radio channel associated in the XPIC configuration displays in the Radio menu in the Associated Interface.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

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

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

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

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

• Tagged frames - If one tagged packet with VLAN-ID X is received on a port which is not memberof the VLAN-ID X, the packet is dropped.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• If an Ethernet Ring has been created, the VLAN ID of the R-APS relevant to the ERP Instancesmust be inserted in the VLAN Configuration as shown in the figure.

• The R-APS is AUTOMATICALLY inserted in the VLAN configuration.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 Cross-Connection Creation 71.1 How to create a cross-connection 81.2 Dialog Boxes 10 2 TDM Cross-Connections 112.1 TDM Cross-Connections 122.2 PDH to Radio/MPTACC 132.3 Radio to Radio 152.4 Radio/MPTACC to Ethernet 172.5 PDH to Ethernet 202.6 Cross-Connections with TDM2Eth Profile 222.7 PDH to Radio/MPTACC 242.8 Radio to Radio 252.9 Radio/MPTACC to Ethernet 26

2.10 PDH to Ethernet 27 3 SDH Cross-Connections 293.1 SDH Cross-Connections with SDHACC 303.2 SDH to Radio/MPTACC 313.3 Radio to Radio 333.4 SDH to Radio/MPTACC 353.5 Radio to Radio 363.6 SDH Cross-Connections with SDHCHAN 373.7 SDH to Radio/MPTACC 383.8 PDH to SDH 403.9 How to modify an SDH cross-con. with SDHCHAN 423.10 SDH to Radio/MPTACC 433.11 PDH to SDH 44

4 ATM Cross-Connections 454.1 ATM Cross-Connections 464.2 ASAP – Radio 474.3 Radio – Radio 504.4 Radio – Ethernet 534.5 ASAP – Ethernet 554.6 How to modify an ATM cross-connection 57 5 LAG-LAG Cross-Connections 635.1 Ethernet LAG - Radio LAG cross-conn. 645.2 Radio LAG - Radio LAG cross-conn. 665.3 How to modify a LAG-LAG cross-connection 68 6 Ring Cross-Connections 716.1 PDH - Ring 72

6.2 Radio – Ring 746.3 Ethernet - Ring 766.4 Pass-through 786.5 How to modify a Ring cross-connection 80 7 Ethernet Cross-Connections 857.1 Ethernet Cross-Connections 867.2 Connections Tab with Ethernet Cross-Connection 89 8 Radio Cross-Connections 918.1 Radio to Radio Cross-Connections 92 9 Port Segregation 959.1 Port Segregation 969.2 CSM-E/Core-E Ethernet Port Segregation 979.3 EAS/P8ETH Ethernet Port Segregation 98

9.4 Configuration 100

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

To create a cross-connection between two points:

1. Place the mouse pointer on the source slot.

2. Press the left button and, while keeping button pressed, drag the mouse to the destinationslot.

3. Release the left button.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• Slot#8 PDH is cross-connected to Slot#5 radio ODU300, to Slot#4 MPTACC and to Ethernet Port#1;

• Slot#4 MPTACC is cross-connected to Ethernet Port#1;

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

• Slot#3 MPTACC is cross-connected to Slot#4 MPTACC;

• Ethernet Port#3 PDH (blue) could not accept cross-connections;

• Slot#3 and Slot#4 (green) could accept more cross-connections;

• Slot#5 and Slot#6 are in 1+1 configuration.

• Each connection line is colored according to slots types it connects (as shown in Figure):

• PDH-Radio connection: black line;

• ATM-Radio connection: orange line;

• PDH-Eth connection: blue line;

• Radio-Radio connection: red line;

• Radio-Eth connection: green line;

• These colors will be applied to the graphical area, when the operator releases the mouse button abovecross-connection destination slot.

• Colors not shown in the figure:

• ATM-Radio connection: orange line (ETSI market)

• ATM-Eth connection: magenta line (ETSI market)

• Ring connection: cyan


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• When connecting two linkable slots through a cross-connection, a dialog will appear, close to thedestination point. This dialog contains connection information, depending on start- and end-pointof connection itself.

• Each cross-connection has different parameters and required data and information will depend onongoing 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, etc.

• All the dialog boxes have a specific title describing the building cross-connection; this states bothslots numbers and types (Slot#8 PDH – Slot#5 RADIO in the example figure).

• The “Ok ” button will visually save the current modifications (this means that data are graphicallysaved only, not sent to the NE!)

• The “Cancel” button will graphically discard ongoing cross-connection, keeping the previousgraphical.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

In the types of cross-connections above Eth means "Ethernet User Port" or "Ethernet LAG" and Radio means"Radio to interface ODU300" or "Radio LAG".


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Configuration parameters will introduce Flow ID number, as coming from remote radio signal, anda parameter related to profile and TDM Clock Source. The operator has to fill in data to completethe 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 fieldthe notation [n-m] to create all Flow IDs from n to m, both included. If the operator wants tospecify different Flow Ids grouping them without using ranges, commas can used to separatevalues.

• For example:

• by entering in the FlowId field 10-15 in one shot will be created all the cross connections fromFlowId 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 connectionswith 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 soon. Based on used input style (ranges or values), the operator will see two different confirmationdialogs.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Once correctly completed the cross-connection configuration and clicked on “OK ” button, theoperator will see a green line describing the Radio/MPTACC to Ethernet cross-connection defined).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• To create other cross-connections drag other lines between the PDH slot and the Ethernet portand repeat the operations.

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

• Select the Flow ID number. As associated in PDH slot, the parameters related to such Flow ID areretrieved. The operator has to enter the destination MAC address to complete the cross-connection configuration and click OK.

•The Profile can be TDM2Eth or TDM2TDM.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Once correctly completed the cross-connection configuration and clicked on “OK ” button, theoperator will be able to see a blue line describing the PDH to Ethernet cross-connection defined(see Figure).

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In these types of cross-connections the destination MAC address of the adjacent NE (unicastaddress in case of unprotected configurations, multicast address in case of protectedconfigurations) must be inserted during the cross-connection creation.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• An existing cross-connection can be modified by double-clicking with the left mouse button on itssymbolic line.

• Now from the screen you have to delete the cross-connections by removing the check mark fromthe relevant Flow Id box and create again a new cross-connections.

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

• previously assigned tributaries (400 to 405 in the example) are active and selected;

• tributaries assigned to another cross-connection (406 to 431) are not active and notselected.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The operator can click on specific (blue) line in order to modify connection parameters. With adouble click with the mouse on the connection line, the dialog window shown in Figure can bemanaged by the operator.



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• By dragging a connection between a SDH slot and a Radio slot or MPTACC slot, the operator willsee the configuration dialog.

• The Flow ID is automatically recognized as associated to the SDH slot.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• By dragging a connection between two different Radio slots, the operator will see theconfiguration dialog in figure.

• To create other cross-connections drag other lines between the two radio slots and repeat theoperations.

• Configuration parameters will introduce Flow ID number, as coming from remote radio signal, andthe profile. The operator has to fill in data to complete the cross-connection configuration.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Select the Flow ID of the E1 in the PDH unit and the E1 of the SDH. Press the Right Arrow button.

• Note: In the SDH unit only the E1 streams enabled (Unframed), but with no associated Flow Id,can be cross-connected to a PDH unit.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In the Figure, the operator is modifying a previously created cross-connection (in this case Slot#8SDH and Slot#4 MPTACC): this action brings up a dialog almost like the creation one, but withsome differences in allowed actions:

• Deselect the Flow ID and select another Flow Id and click OK to change the cross-connection,then click Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Select the cross-connection on the right-side field, click on the Left Arrow button, click OK , thenclick on Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Enter the following Configuration parameters:

• ATM interface (this interface is the IMA group: from 1 to 8)

• PW label

• VPI

• VLAN ID

• Destination MAC Address (only with MPT-HC or MPT-MC)

• The Traffic Descriptor is automatically created.

• ATM "Light" Cross-connection Provisioning

• In this release when a cross-connection toward a radio direction with MPT is involved, therelated provisioning is performed in almost the same way as with ODU300, with the followingmain differences:

• MAC DA is also explicitly provisioned in the NE acting as TPE role

• admission control, in terms of checking bandwidth required but ATM PW flow against theavailable bandwidth on radio interface, is never performed.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• By dragging a connection between two different radio slots, the operator will see theconfiguration dialog.

• To create other cross-connections drag other lines between the two radio slots and repeat theoperations.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Configuration parameters are:

• select the Service: ATM or PW3

• select the PW label

• assign the VLAN ID

• associate the Traffic Descriptor by clicking on Browse and selecting a Traffic Descriptorpreviously created.

• An ATM PW is made up of two undirectional flows.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:


• select the Service: ATM or PW3



• enter the Destination MAC address

• associate the Traffic Descriptor by clicking on Browse and selecting a Traffic Descriptorpreviously created.

• An ATM PW is made up of two undirectional flows.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:


• select the ATM interface


• enter the VPI


• enter the Destination MAC address

• The Traffic Descriptor is automatically created.

• The operator has to put the correct Destination MAC address to complete the cross-connectionconfiguration.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In Figure the operator is modifying a previously created cross-connection: this action brings up adialog almost like the creation one:

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

• Tributaries assigned to another cross-connection are not active and not selected.

• Select the ATM interface and remove the check mark and create again a cross-connection.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• Select the ATM Service and remove the check mark and create again a cross-connection.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The operator can click on specific (green) line in order to modify connection parameters. With adouble click with the mouse on the connection line, the dialog window shown in Figure can bemanaged by the operator.

• Select the ATM Service and remove the check mark and create again a cross-connection.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The operator can click on specific (blue) line in order to modify connection parameters. With adouble click with the mouse on the connection line, the dialog window shown in Figure can bemanaged by the operator.

• Select the ATM interface and remove the check mark and create again a cross-connection.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Configuration parameters will introduce the Service (TDM or ATM), Flow ID number and allparameters related to such Flow ID. The operator has to put the correct MAC address to completethe cross-connection configuration.

• Two types of cross-connections can be implemented:

• Ethernet LAG - Radio LAG cross-connections

• Radio LAG - Radio LAG cross-connections


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

To create other cross-connections drag other lines between the Radio LAG and the Ethernet LAGand repeat the operations.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Configuration parameters will introduce the Service (TDM or ATM), Flow ID number, as comingfrom remote radio signal, and a parameter related to profile and TDM Clock Source. The operatorhas to fill in data to complete the cross-connection configuration. The operator can use rangesand values.

• To create in one shot several cross-connections the operator can use in the Flow ID field thenotation [n-m] to create all Flow IDs from n to m, both included. If the operator wants to specifydifferent 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 connectionsfrom 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 crossconnections 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 soon. Based on used input style (ranges or values), the operator will see two different confirmationdialogs.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In the Figure, the operator is modifying a previously created cross-connection (in this case RadioLAG #2 SDH and Ethernet LAG #24): this action brings up a dialog almost like the creation one,but with some differences in allowed actions:

• Previously assigned Flow ID (654 in the example) is active and selected;

• In the example of the figure there is no other Flow ID and for this reason it is not possible tocreate another cross-connection.

• Select the Service and the Flows ID and click OK to remove the cross-connection, then click Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Previously assigned Flow ID (654 in the example) is active and selected;

• In the example of the figure there is no other Flow ID and for this reason it is not possible tocreate another cross-connection.

• Select the Service and the Flows ID and click OK to remove the cross-connection, then click Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Configuration parameters will ask to select the instance and to select Flow ID number, asassociated in PDH slot.

• The Cross-connections to be implemented are:

• PDH - Ring cross-connections

• Radio - Ring cross-connections

• Ethernet - Ring cross-connections

• Pass-through cross-connections

Warning: After the Ring cross-connection creation enable the ERP in the Ring menu (click on theRing icon in the Tool bar).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Configuration parameters are the Ring Instance, VLAN (multiple selection can be done), ServiceProfile and TDM Clock Source (if the Profile in TDM2Eth).

• The operator has to fill in data to complete the cross-connection configuration and click on theRight Arrow button.

• The dialog screen displays the cross-connected VLANs (see figure).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Configuration parameters are the Ring Instance, VLAN (multiple selection can be done), ServiceProfile, TDM Clock Source (if the Profile in TDM2Eth) and the destination MAC Address.




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

When a port reaches its full capacity, the operator will see a specific report.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Configuration parameters are the Ring Instance, VLAN (multiple selection can be done), ServiceProfile and TDM Clock Source (if the profile is TDM2Eth).




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In the Figure above, the operator is modifying a previously created cross-connection (in this caseSlot#3 PDH and Radio): this action brings up a dialog almost like the creation one, but with somedifferences in allowed actions

• Deselect the Flow Id and select another one. Click OK and Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The operator can click on a specific line in order to modify connection parameters. With a doubleclick with the mouse on the connection line, the dialog window shown in the Figure above willappear.

• Select the cross-connected VLANs in the right-side field and click on the Left Arrow arrow.Change the Instance, if required, then select another VLAN and click the Right Arrow button.Click on OK and Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The operator can click on specific line in order to modify connection parameters. With a doubleclick with the mouse on the connection line, the dialog window shown in the Figure can bemanaged by the operator.



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:

Remember Flow Id must be the same on both ends of the path and only used once in the network.

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:

Ethernet Flow IDs

• For multiple Flow IDs:

• List each Flow ID separately, with a comma separator (56, 57, 60, 70)

• List an inclusive range of Flow IDs (56-65, 70, 72)

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:

Ethernet to Radio Cross-Connections

1. Select Ethernet port and drag and draw line to Radio port. RADIO-ETH pop-up displays.

2. On the RADIO-ETH pop-up, enter Flow ID number in the Flow ID field.

3. Enter the destination MAC address where the DS1 will be terminated in the MAC Address field.

4. On the RADIO-ETH pop-up, click OK .

5. On the Cross-Connection screen, click Apply.

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:

Radio to Radio Cross-Connections

1. Select Radio port and drag and draw line to Radio port. RADIO-RADIO pop-up displays.

2. On the RADIO-RADIO pop-up, enter Flow ID number in the Flow Id field (flow ID must be thesame through the entire path).

3. On the RADIO-RADIO pop-up, click OK.

4. On the Cross-Connections screen, click Apply.

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:

• When provisioning multiple radio links on the same path use port segregation to avoid any Ethernetloops.

• Double-click on the provisioned port. Uncheck all ports to be segregated. Select OK then Apply.

• This option sets the segregation state to exclude the port from exchanging frames with a given list of ports.

• In this way a segregated port can exchange frames only with a non-segregated port.

• Port segregation is used to:

• save bandwidth (prevent collisions and broadcasts)

• save resources on the node and on the ports

• improve the security and the privacy of the transmission

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Notes:

• The switch ports in a private VLAN domain have special characteristics. One key characteristic is portsegregation within an isolated VLAN.

• Isolated or segregated ports are typically used for those endpoints that only require access to a limitednumber of outgoing interfaces.

• An endpoint connected to an isolated port will only possess the ability to communicate with thoseendpoints connected to provisioned ports.

• Endpoints connected to adjacent isolated ports cannot communicate with one another.

•If you attempt to setup a cross-connection between ports that have been segregated, you will get awarning that the port is segregated.

• Press Alt-W. Notice the screens are different if any ports are segregated.

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 WT Performance Monitoring Suite 71.1 Introduction 81.2 Tool bar 111.3 Menu bar 131.4 NE Measurement Main Tree 151.5 How to Start the Measurements 211.6 How to Stop the Measurements 221.7 Offline Mode 231.8 PM selectable options 26 2 Ethernet Statistics 272.1 Ethernet Statistics tab 282.2 CORE-ENH unit Ethernet Statistics 292.3 Radio QoS Ethernet Port PM example 40

3 RADIO PMs 413.1 RADIO PMs procedures 423.2 Manage thresholds 443.3 24-Hour Current List View example 483.4 24-Hour Current Overview example 493.5 24-Hour Current Birdseye View example 503.6 Radio Port PM example 51 4 Adaptive Modulation PM 534.1 Performance monitoring procedures 544.2 Adaptive Modulation PM example 56 5 PDH Performance Monitoring 575.1 P32E1DS1 unit performances 585.2 Incoming 59

5.3 How to display a threshold 605.4 Example of the other views 62 6 IMA Layer Statistics 656.1 IMA Layer Statistics 66 7 ATM Layer Statistics 697.1 ATM Interface Statistics 707.2 Interface# 717.3 Logical VPs and Not Logical VPs 72 8 RSL History 758.1 RSL History 76

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The WT Performance Monitoring Suite can be invoked:

• from NEtO by clicking on the WTPMS (WT Performance Monitoring Suite) button

• from the WebEML by clicking the WTPMS (WT Performance Monitoring Suite) icon in the ToolBar

• from the WebEML in Main menu > Diagnosis > Performance Monitoring

• from the WebEML in Main menu > Diagnosis > Summary Block Diagram View


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The buttons in the Toolbar have the following functionalities:

• Close button removes a NE from the NE list;

• Move to front button (not available);

• Move to back button (not available);

• Sort button (not available);

• Background button (not available);

• Start/Stop button starts or stops the counters for the data collection, when the Current Datahave been stopped or started. The current measurement status is shown;

• Refresh button retrieves the current PM reports form NE and update the table view and chartview with the recently collected data;

• Reset button resets the data collection and related counters;


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Archive button archives in the NM environment the PDH PM and the Radio PM (only theradio counters);

• Collect button forces in the NM environment the PM collection;

• Export button saves the report;

• Print button prints the user selected performance point;

• Offline Mode button saves the current status of the WT Performance Monitoring Suite tohave later the possibility to see the PM offline;

• List View to display all the PM counters in a tabular format;

• Overview button to display all the PM counters in a graphic format;

•

Bird's Eye View button displays a selected PM counter in a graphic• format with the possibility to zoom in/out and autorange the graphic and to navigate in the

graphic;

• Note button shows the meaning of each parameter;

• Help button show help content.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• File: ExportPrintOffline modeExit: closes the application

• Edit: (this menu is available only in NM environment). Threshold Editor (opensthe Editor for the thresholds to be associated in the PDH PM feature baror in the Radio PM feature bar)

• Network : List View

OverviewBird’s Eye View

• Action: Move to front (not available)Move to back (not available)Sort (not available)Background (not available)Close: removes a NE from the NE list


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Tools:

• Start/Stop: starts or stops the counters for the data collection, when the Current Data have

been stopped or started

• Reset: resets the data collection and related counters

• Refresh: retrieves the current PM reports form NE and update the table view and chart viewwith the recently collected data Archive (this option is available only in NM environment):archives in the NM environment the PDH PM and the Radio PM (only the radio counters)

• Windows: shows the list of the open windows

• Help: shows some information on the Help


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In the List View all the available counters for a selected feature, slot, measurement point are shown in the tabularformat. In the List View the Custom View tab-panel enabes the display of a subset of the available counters.

• You can customize the view by clicking on tab Custom View.

• The view is divided into two areas:

• left area, which contains the list of the selectable counters;

• right area, which contains the list of the selected counters.

• The user can select a counter on the left area and by clicking the upper arrow move it to the right area in order tocustomize the counter view. The opposite operation can be done by selecting the counter in the right area and byclicking the lower arrow to move it to the left area. Click on OK button to confirm.

• In the Overview all the measurements are shown in a small graphic format in one screen.

• In the Bird’s Eye View the measurements are shown in graphic format one by one.

• By using the navigation bar in the upper part of the screen a specific port or a specific counter can be displayed.

• By default all the measurements, selected through the navigation bars, are displayed, but by deselecting the check box of a particular measurement counter on the legend, the relevant counter is removed from the view.

• In the lower part of the screen the Default counters and the Elaborated Counters are shown in a tabular format.

• Default Counters: collected on the NE

• Elaborated Counters: processed on the PC and available only when the PC is connected to the NE.

• By right clicking with the mouse on the graphic the following options will appear:

• Copy: to storage the image

• Save as: to save the image as .png or .jpeg

• Print: to print the image

• Zoom In: to enlarge the image

• Zoom Out: to shrink the image

• AutoRange: to fit the image


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Custom View Composer (launched from the Custom View tab) allows the user to specifywhich PM fields are displayed in the List View and the Overview for the respective PMcategories:

• Ethernet Statistics

• Radio PM

• Adaptive Modulation PM

• PDH MP

• IMA Layer Statistics (ETSI)

• ATM Interface Statistics (ETSI)

•

RSL Statistics

• To change the field display:

1. Click the Custom View tab (see next slide)

2. From the Custom View Composer, Not Selected panel, select the fields to be displayed.

3. Click the right arrow to move the fields into the Selected panel.

4. Click OK .


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• (1) In the example shown, Ethernet Statistics has been selected.

• (2) The slot selection corresponds to the selection of the unit. In the figure, Slot 1 has beenselected. The selection of the unit will cause the display of the counters of all its availablesubordinate objects, i.e. in this example the counters of all equipped ports will be displayed.

• (3) Optionally, after the selection of the slot, you can select one of its subordinate objects. In thiscase, only the selected object is highlighted in the frame area.

• The PM can be started individually or at slot level.

• (4) The start time is displayed in the Configuration area (left-lower part of the window).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Toolbar and the Menu bar are the same bars of the WTPMS. The only differences are:

zStart/Stop and Refresh buttons are not available in the Offline Mode

z allows to open another NE in offline mode.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Several tab-panels can be present:

• A - NEs List: it includes all the NEs, which launched the application

• B - Specific tab-panel (identified by the NE IP address) for each NE, which launchedthe application.

• By clicking an NE in the NEs List or in the specific NE tab-panel, the available PM will appear.

• The following types of Performance Monitoring are available:

1. Ethernet Statistics

2. Radio PM

3. Adaptive Modulation PM

4. PDH PM5. IMA Layer Statistics (ETSI market)

6. ATM Interface Statistics (ETSI market)

7. RSL History


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Stability measurement on Ethernet counters (with duration from few hours to 24 Hours) should beperformed by selecting an high value (60 seconds) as collection time of the performances (refer toparameter Interval in the Configuration subwindow).

• The MPTACC unit is the interface to MPT-HC/MPT-MC.

• The MD300 unit is the interface to ODU300.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The right-hand area contains the statistic data for the Ports.

• The following tab are selectable for each port:

• Ethernet Aggregate Tx

• Ethernet Aggregate Rx

• Custom view

• The default interval is 5 seconds.

• The default duration is 1 hour.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The available performances at port level are (see Port 1 selected in the above figure):

• TTO: total number of octets of Ethernet frames transmitted out by the Interface, includingEthernet 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 tobuffer congestion.

Reserved Multicast frames are discarded, but the TDF counter is not incremented.

• TTF Unicast: total number of Ethernet Unicast frames transmitted out by the Virtual EthernetInterface.

• TTF Multicast: total number of good packets transmitted by this address that were directedto a multicast address. This number does not include packets directed to the broadcastaddress.

• TTF Broadcast: total number of good packets transmitted by this address that were directedto the broadcast address.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The available performances at port level (see Port 1 selected in the above figure):

• TRO: total number of octects of Ethernet frames received by the Virtual Ethernet Interface,including Ethernet header characters.

• TRF: total number of Ethernet frames received by the Virtual Ethernet Interface.

• TRSEF: total number of errored frames.

• TDF: total number of Ethernet frames discarded for congestion.

N.B.: Reserved Multicast frames are discarded, but the TDF counter is not incremented.

• TRF Unicast: total number of Ethernet Unicast frames received correctly by the VirtualEthernet Interface.

•

TRF Multicast: total number of good packets received that were directed to a multicastaddress. This number does not include packets directed to the broadcast address.

• TRF Broadcast: total number of good packets received that were directed to the broadcastaddress. This number does not include multicast packets.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Click on the Navigation bar to change the view.

• In the buttom 2 tab-panels show the counters:

• Deafult Counters: collected on the NE row

• Elaborated Counters: processed on the PC and are available only when the PC is connectedto the NE.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:






7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Figure 1 above shows examples of selection of an MPTACC unit:

• MPTACC in slot #3 refers to a 1+1 configuration

• MPTACC in slot #4 refers to a 1+0 configuration

• MPTACC in slot #5 refers to a non 1+1 configuration

• Figure 2 above shows examples of selection of a P8ETh unit:

• P8ETH in slot#3 refers to a 1+1 configuration (port #5)


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Two types of MPT are available:

• MPT-HC (High Capacity), up to 256QAM

• MPT-HC (Medium Capacity), up to 128QAM

• The MPTACC unit has 8 output queues:

• Queue 8 is reserved to TDM2TDM traffic.

• Queue 7 is reserved to TDM2Eth traffic.

• Queue 6 is reserved to TMN traffic.

• The remaining 5 queues are reserved to Ethernet traffic. Queue 5 is the highest priority queue.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Select the tab of the queue to display. The available performances at queue level (for eachqueue) are:

• TTO: total number of octets of Ethernet frames transmitted out by the Interface, includingEthernet 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 tobuffer congestion.

• Reserved Multicast frames are discarded, but the TDF counter is not incremented.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:



• Default Counters: collected on the NE row

• Elaborated Counters: processed on the PC and are available only when the PC isconnected to the NE.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:



• Default Counters: collected on the NE row

• Elaborated Counters: processed on the PC and are available only when the PC isconnected to the NE.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



1) The following Radio tabs are selectable:

• Hop Ch 0 (Spare channel)

• Hop Ch 1 (Main channel)

• Link (RPS active channel)

• Use the Menu bar the or click the relevant icon in the Tool bar to display the other views,

• The performance reports can be displayed in 15 minutes or 24 hour time periods. The samefunctions are provided for both time periods.

• The PM are of HOP or LINK type:

• HOP refers to the PM before the RPS switch.

• LINK refers to Performance Monitoring after the RPS switch.

• Two types of counters are supported:

• Radio Counters – Errored seconds, Severely Errored Seconds, Background Block Error, andUnavailable Seconds

• Analog Counters – minimum, average, and maximum power levels during the elasped time.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The view contains the following collection data parameters:

• Time. It displayes the time of the Performance Monitoring. This time changes after the AutoRefresh.

• Elapsed Time. It displays the elapsed time in the current interval of monitoring.

• Suppressed Intervals. It displays the number of intervals (reports) suppressed in the Historybecause they don’t have errors.

• If an interval is suspected, it is highlighted in red. An interval is defined as “suspect” if at leastone of the following conditions occurs in the collection period:

• the elapsed time deviates more than 10 seconds of the nominal time

• loss of the Performance Monitoring data in the equipment

• performance counters have been reset during the interval.

• The displayed counters are:

• BBE (Background block Errors)

• ES (Errored Seconds)

• SES (Severily Errored Seconds)

• UAS (Unavailable Seconds)


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• For the ANSI market the PDH PM

• Thresholds assigned to Performance Monitoring counters can be created, displayed, or changed.

• There are threshold tables for the HOP and for the LINK.

• There are two default thresholds for HOP: Threshold #1 (for 15 min report) and Threshold#4 (for 24 hour report).

• There are two default thresholds for LINK : Threshold #1 (15 min report) and Threshold #3

(for 24 hour report).

• The user can manage thresholds to be associated to Hop or Link 15min report or 24h report.

• The following actions can be performed:

• Thresholds display

• Create threshold

• Delete threshold

• Associate a threshold to a monitoring point


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Four threshold tables can be created for the HOP (Threshold #2, #3, #5 and #6).

• Two threshold tables can be created for the LINK (Threshold #2 and #4).

• Two standard thresholds are available for the HOP (Threshold #1, #4).

• Two standard thresholds are available for the LINK (Threshold #1 and #3).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Only the created thresholds can be modified or deleted. The default thresholds can be onlydisplayed.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The list of the available thresholds for the previously selected Monitoring Point is presented byclicking on the down arrow beside the field name (threshold in this case); only the thresholdsapplicable to the selected Monitoring Point are presented.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Radio Hop Section and Link Hop Section are defined as follows:

• Radio Hop Section-The unprotected radio channel (before RPS in 1+1 radio configurations)

• Link Hop Section-The protected radio channel (after RPS); Only supported in 1+1 radio configurations.

• Adaptive Modulation PM captures the modulation scheme used on the Tx side when adaptive modulation isenabled. In 1+1 HSB radio configuration, the statistics are associated with the link level after RPS. AdaptiveModulation PM is not supported in 1+1 FD radio configurations.

• Defect second on a radio hop section, is a second in which an LOF or DemFail occurs.

• Defect second on a link hop section, is a second in which an LOF occurs at the link level after RPS.

• Errored Block count for a radio hop section equals the number of errored blocks.

• Errored Block count for a link hop section equals the number of link level errored blocks after RPS.

• Four PM counters are supported as follows:

• Errored Second (ES)-When a defect second is set or if there is at least one or more errored blocks.

• Severely Errored Seconds (SES)-When a defect second is set and if the errored block count is greater orequal to 30% of the blocks in one second.

• Background Block Error (BBE)-The number of block errors in a one second period and the second is not anSES.

• Unavailable Seconds (UAS)-A time period starting after ten consecutive SES events are detected. Thequalifying ten consecutive SES seconds are included in the UAS time period. Ending upon the detection of ten consecutive non SES events. These non SES seconds are not included in the UAS time period.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The Counters can be displayed in three different views:

• List View

• Overview

• Bird's Eye View

• If the Adaptive Modulation has been enabled in the MOD300 (unit for ODU300) or in the MPTACCunit (for MPT), the WT Performance Monitoring Suite will display Adaptive Modulationperformance information.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The view contains the following collection data parameters:

• Time. It displayes the time of the Performance Monitoring. This time changes after the AutoRefresh.

• Elapsed Time. It displays the elapsed time in the current interval of monitoring.

• Modulation schemes (from QPSK to 256 QAM). It shows (for each modulation scheme) thetime during which a specific modulation scheme has been used.

• If an interval is suspected, it is highlighted in red. An interval is defined as "suspect" if at leastone of the following conditions occurs in the collection period:





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Adaptive Modulation PM captures the modulation scheme used for the transmitter when adaptivemodulation is enabled. In 1+1 HSB radio configuration, the statistics are associated with the link level after Radio Protection Switching.

• Adaptive Modulation PM is not supported in 1+1 FD radio configurations.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

•The following description explains the functions to provide the Performance Monitoring processwith a granularity period of 15 min. The same functions are provided for 24h PerformanceMonitoring process.

• The following tabs are selectable:

• Incoming

• Outgoing

• Customer View

• By selecting the unit slot all the PM of the enabled E1s can be started in "one-shot".

• 9500MPR is transparent regarding the E1 stream. The CRC is used to detect the quality of the E1stream.

• For a better quality in the Performance Monitoring it is recommended to start up to 128 E1 PMcounters 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. The Counters can be displayedin three different views:

• List View

• Overview

• Bird’s Eye View


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• If an interval is suspected, it is highlighted in red. An interval is defined as “Suspect” if at leastone of the following conditions occurs in the collection period:




• These values refer to the last refresh performed with the Refresh button in the Tool bar.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Threshold management describes how to display or change or create the threshold to be assignedto Performance Monitoring counters. There are two default threshold:

• Threshold #1, to be associated to 15 min report;

• Threshold #4, to be associated to 24 h report.

• The following actions can be done:

• Display a threshold;

• Create a threshold;

• Modify/delete a threshold;

• Associate a threshold to a monitoring point.

• The threshold management procedures for PDH are the same as previously described for RadioPM.

• There are two default threshold:

• Threshold #1 (to be associated to 15 min report)

• Threshold #4 (to be associated to 24 h report).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:






7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The IMA Layer Statistics are available with the A16E1DS1 unit.

• Unavail Secs: counter of the seconds where the IMA group traffic state machine is down.

• NeNumFailures: counter of the number of times a failure alarm condition (Config-Aborted,Insufficient-Links, Config-Aborted-FE, Insufficient-Links-FE, Blocked-FE) has been reported forNear-End IMA Group.

• By selecting the slot, no tables will appear.

• The quality of IMA Group and Links is evaluated by monitoring IMA Group and Link Counters.

• This monitoring is based on IMA standard.

• The Counters can be displayed in three different modalities:

• List View

• Overview

• Bird’s Eye View

• In the following example, only the List View is shown. To display the other views select in theMenu bar the view or click the view on the relevant icon in the Tool bar.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• For each active IMA link , belonging to an activated IMA Group, the following counters areavailable:

• IMA Violation: counter of errored, invalid or missing ICP cells, except during SES-IMA orUAS-IMA conditions;

• OIF (Out of IMA Frame) anomalies: counter of OIF anomalies, except during SES-IMA orUAS-IMA conditions;

• NeSES (Severly Errored Seconds): counter of one second intervals containing more then30% of the ICP cells counted as “IMA Violation”, or one or more link defects (e.g., LOS,OOF/LOF, AIS, or LCD), LIF defects, or LODS defects, except during UAS-IMA condition, forNear-End side;

•NeUAS (UnAvailable Seconds): counter of the seconds unavailability beginning at the onsetof 10 contiguous SES-IMA and ends at the onset of 10 contiguous seconds with no SES-IMA,for Near-End side;

• Ne Tx UUS (UnUsable Seconds): counter of unusable seconds declared by the Link StateMachine at TX and RX directions for Near-End side;

• Ne Tx failure: counter of the number of times a failure alarm condition has been entered onthis link at Tx direction for Near-End side;

• Ne Rx failure: counter of the number of times a failure alarm condition has been entered onthis link at Rx direction for Near-End side.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• For each configured and active ATM interface the following counters are available:

• Received Cells: counter of the number of cells received on the ATM interface.

• Transmitted Cells: counter of the number of cells transmitted on the ATM interface.

• Inv Header Discarded Cells: counter of the number of cells discarded because of InvalidHeader, invalid VPI or invalid VCI.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• For each active VP, if configured as Termination end-point, and active VC configured over anactive ATM interface, the following counters are available:

• Discarded Cells: counter of the total number of valid VP/VC cells discarded by the trafficpolicing entity. This includes cells originally received with CLP=0 and CLP=1.

• Discarded CLP0 Cells: counter of the total number of valid VP/VC cells received with CLP=0and discarded by the traffic policing entity.

• Tagged Cells: counter of the total number of valid VP/VC cells tagged by the traffic policingentity from CLP=0 to CLP=1 and transmitted.

• Usage Rx: counter of the total number of valid VP/VC cells received including both CLP=0 andCLP=1 cells. The cells are counted prior to the application of the traffic policing.

• Usage Tx: counter of the total number of valid VP/VC cells transmitted including both CLP=0and CLP=1 cells. The cells are counted prior to the application of the traffic policing.

• Usage Rx CLP0: counter of the number of valid VP/VC cells received with CLP=0. The cellsare counted prior to the application of the traffic policing.

• Usage Tx CLP0: counter of the number of valid VP/VC cells transmitted with CLP=0. The cellsare counted prior to the application of the traffic policing.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History



4.0 2012-09-14 AL University Updated for R4.0

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 Fault Management 71.1 Troubleshooting 81.2 Before Going to Site Checklist 91.3 Troubleshooting Basics 111.4 Troubleshooting Path Problems 161.5 Troubleshooting Configuration Problems 191.6 Troubleshooting Ethernet Problems 201.7 Troubleshooting TMN Problems 221.8 Analyzing Ethernet Traffic 26 2 Failed Equipment Removal and Replacement 332.1 MSS-8/MSS-4 Card Removal and Replacement 342.2 Core-E Card Removal and Replacement 362.3 Flash Card Replacement Procedure 37

2.4 ODU300 Removal and Replacement 382.5 MPT-MC Removal and Replacement 39

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

If the fault suggests a rain fade or other weather related fade condition and it matches the prevailing weatherconditions, do not take any action until the weather abates.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

A path extends from ODU antenna port to ODU antenna port.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Ultimately, a spectrum analyzer may have to be used to confirm interference, which is not an easy task giventhe need to connect directly to the antenna port, after removing the ODU.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

•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 hassoftware from an earlier release. To remove the alarm, compatible 9500 MPR software is required; installthe latest software.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

This section gives general guidance on troubleshooting problems related to the four Ethernet ports on theCore-E Card.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• This section gives general guidance on troubleshooting problems related to the four Ethernet ports on theCore-E Card.

• Refer to table “Troubleshooting Ethernet Problems” on next slides for detail troubleshooting using the LEDslocally at the alarmed site.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Enter:

• User Name: initial;

• Password: adminadmin.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• “Run command” provides the output on the web page.

• “Save output to file” provides the output on the web page and also saves the output on a file.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

All slots must be filled with a plug-in card or a blank panel. Failure to do so will comprise EMI integrity and thecooling capacity of the fan.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Verify the replacement Core-E Card meets the following compatibility rules:

• Main Core-E Card (in slot 1) and Spare Core-E Card (in slot 2) must be the same type.

• Local and far end Core-E Cards must use the same software version, but do not have to be the sametype.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



First case: Core-E Protected

1. Get a spare FLASH CARD with the same sw-package release and license of the Main flash.

2. Remove the faulty FLASH CARD from the main Core-E and insert the spare one.

3. Insert the Core-E with the new FLASH CARD.

4. The MIB (MAIN FLASH) will be automatically aligned with the MIB (SPARE FLASH).

Second case: Core-E Not Protected

1. Get a spare FLASH CARD with the same sw-package release and license.

2. Remove the faulty FLASH CARD from the main Core-E and insert the spare one.

3. Insert the Core-E with the new FLASH CARD.

4. Carry-out the RESTORE procedure.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 Protections with ODU300 71.1 Protections with ODU300 81.2 RPS Switching Criteria 111.3 EPS Switching Criteria 121.4 HSB Switching Criteria 13 2 Protections with MPT-HC V2/MPT-XP 152.1 Protections with MPT-HCV2/MPT-XP 162.2 RPS Switching Criteria 202.3 EPS Switching Criteria 212.4 HSB Switching Criteria 22 3 MSS-4/MSS-8 XPIC (with MPT-HC V2 /MPT-XP only) 233.1 MSS-4/MSS-8 XPIC (with MPT-HCV2/MPT-XP only) 24 4 Protection with MPT-MC 27

4.1 Protection with MPT-MC 284.2 RPS Switching Criteria 304.3 EPS Switching Criteria 314.4 HSB Switching Criteria 32 5 Core-E protection 335.1 Core-E protection 345.2 User Ethernet interfaces protection 355.3 TMN Local Ethernet interface protection 365.4 Core-E protection 375.5 Core-E protection Switching Criteria 38 6 EPS, RPS, and HSB Management 396.1 EPS Management 406.2 RPS Management 43

6.3 HSB Protection Management 46 7 Ring Protection 497.1 ERPS operation 50 8 Fiber-Microwave Protection 558.1 Overview 568.2 Fiber-Microwave Protection Creation - Overview 608.3 Fiber-Microwave Protection Configuration 61

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Legend:

• 1 RPS

• 2 EPS

• 3 HSB


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Legend:

2 EPS


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

In the figure Ethernet port 2 of one MPT-HCV2/MPT-XP is connected to Ethernet port 2 of the second MPT-HC V2/MPT-XP.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• MPT-HCV2/MPT-XP supports a further embedded functionality called "Enhanced RPS". Enhanced RPS is aframe-based protection mechanism, aimed to reach a quick reaction time and increasing significantly thequality of the radio interface in the Rx side.

• It assumes the alignment between the 2 received radio channels and it is based on frame by frame selectionof the "best" frame between the frames received from the Main and the Spare radio channel.

• The Enhanced RPS assumes that the "classical" RPS criteria are used to give indication about the "preferred"channel, whose frame has to be selected, when the frame-based choice between the 2 streams is notpossible (e.g. due to the frame alignment error).

• The Enhanced RPS switching criterion depends on the presence of errors in the decoded LDPC word.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Where there is a cross configuration (EPS on Spare & TPS on main), HSB (TPS) will switch and align with EPSposition, if there is an inter-MPT coupling link failure.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• This function is implemented by installing the “RPS+XPIC” external module).

• The actual improvement will depend on the native discrimination provided at antenna alignment,and any reduction of this discrimination caused by atmospheric effects (fading).

• XPIC typically provides 20 dB improvement in polarization discrimination.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Since there is no coupling link in the current release the TPS Operator Commands are notsupported.

• Only Operator Commands for EPS are supported.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• MPT-MC supports a further embedded functionality called "Enhanced RPS". Enhanced RPS is aframe-based protection mechanism, aimed to reach a quick reaction time and increasingsignificantly the quality of the radio interface in the Rx side.

• The Enhanced RPS assumes that the "classical" RPS criteria are used to give indication about the"preferred" channel, whose frame has to be selected, when the frame-based choice between the2 streams is not possible (e.g. due to the frame alignment error).

• The Enhanced RPS switching criterion depends on the presence of errors in the decoded LDPCword.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

All the switching criteria coming from both the Core units, are available (via back panel) to each peripheral inorder to allow to each logic to take the same decision.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Restoration Criteria field: the possible values are Revertive (automatic restoration allowed) ornot Revertive (automatic restoration Inhibited).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The operator by the Craft Terminal can modify the state of the switch through commandsLockout, Forced and Manual. Select the suitable command and click on Apply.

• Some commands are not supported by selected elements.

• Lockout has higher priority than Forced: the activation forces in service Channel 1 (defaultchannel), independently of the possible active alarms.

• Forced has higher priority than the automatic operation: the activation of this command forces inservice Channel 0, independently of the possible active alarms.

•

Automatic Switch is the normal operation condition: the position of the switch depends on thecommands generated by the logic.

• Manual has the lowest priority: it is performed only if there are no alarms that can activate anautomatic 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.

Warning: All the commands are not error free.

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Restoration Criteria field: the possible values are Revertive (automatic restoration allowed) ornot Revertive (automatic restoration Inhibited).

• RPS Configuration: (this parameter can be changed only with MPT-HC/MPT-HC V2):

• Physical cable checked: the protection takes place through a physical interconnection cablebetween the two MPT-HC or the two MPT-HC V2

• Physical cable not checked: no physical interconnection cable between the two MPT-HC or thetwo MPT-HC V2


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:


• Some commands are not supported by selected elements


• Forced has higher priority than the automatic operation: the activation of this command forces inservice Channel 0, independently of the possible active alarms.

• Automatic Switch is the normal operation condition: the position of the switch depends on thecommands generated by the logic.



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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Restoration Criteria field: the possible values are Revertive (automatic restoration allowed) ornot Revertive (automatic restoration Inhibited).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:


• Some commands are not supported by selected elements


• Forced has higher priority than the automatic operation: the activation of this command forces in

service Channel 0, independently of the possible active alarms.

• Automatic Switch is the normal operation condition: the position of the switch depends on thecommands generated by the logic.



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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Ethernet Ring Protection Switch (EPRS) is a protection switching mechanism is based on the Automatic Protection Switching protocol for Ethernet ring topologies (called R-APS).

• The fundamentals of this ring protection switching architecture are:

• principle of loop avoidance.

• utilization of learning, forwarding, and address table mechanisms defined in the Ethernet flowforwarding function.

• The loop avoidance in the ring is achieved by guaranteeing that, at any time, traffic may flow onall but one of the ring links. This particular link is called the Ring Protection Link (RPL).

• Under normal conditions the RPL link is blocked, i.e., not used for traffic. One designated node,the RPL Owner, is responsible to block traffic over the RPL. In the example above, the RPL owner(Node A) has the RPL connection point blocked with VLANs A, B, and C also blocked.

• Under a ring failure condition, the RPL owner is responsible to unblock the RPL, allowing the RPLto be used for traffic.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In the example above, a blocked port on Node D causes VLANs A, B, and C to be blocked.

• The connection points between Radio West and Radio East are blocked to Node D and Node Crespectively.

• Under a ring failure condition, the RPL owner (Node A) is responsible for unblocking the RPL(between Node A and Radio East), allowing the RPL to be used for traffic.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Two ERPS Control Processes are configured on each ring’s node. Each instance selects its ownRPL and RPL Owner. In the example above, Node A owns ERP 1 (between Radio East and Node A) and ERP 2 (between Radio West and Node A).

• The ERPS Control Process controls the forwarding function to perform the following actions:• to disable forwarding over the set of VLANs assigned to the ERPS instance corresponding to

blocked ring links;• to flush the learned MAC address table.

• Only revertive switching mechanism is supported.

• The Wait-to-Restore is managed by the RPL Owner, it is configured by the operator in 1 minutesteps between 1 and 12 minutes. The default value is 5 minutes.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• In the example above, a blocked port on Node D causes ERP 1 and ERP 2 and VLANs A, B, C, andD to be blocked.

• Under a ring failure condition, the RPL owner (Node A) for ERP 1 and ERP 2 is responsible forunblocking the RPLs (between Node A and Radio East and Radio West), allowing the RPLs to beused for traffic.

• In the example above, during the failure Ethernet flow was dropped by the radio QoS.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Create a single Instance in the Topology created before. Since it is requested to manage theoverall traffic either over Fiber connection or over radio link, the usage of two Instances to loadbalance traffic in the Ring is not supported.

• Define one of the two NEs as RPL Owner and configure the radio interface as RPL. In no-faultcondition, this will set the Ring Port related to the radio interface in blocking, allowing the trafficto be forwarded over Ethernet optical connection.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The scenario is supported by the MPR NE using ERPS performing the following configuration:

1. Create two Topologies in the NE acting as Node, each Topology having a radio interface and anoptical User Ethernet interface as Ring Ports;

2. Create a single Instance in both the Topologies created before

3. For each Instance, define the NE acting as Node or the other NE at Tail end as RPL Owner andconfigure the radio interface as RPL. In no-fault condition, this will left Ring Port related to radiointerface in blocking, allowing the traffic to be forwarded over Ethernet optical connection.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• “Printing Format” is supported to manage in one shot multiple groups of VLAN IDs: i.e. (5-10,100-130, 150).

• The WebEML checks the following:

– the admitted values are in [1-4080] range

– VLAN Id is not used yet as R-APS VLAN Id in any instance

– VLAN Id is already used in TMN In-band, but the TMN In-band working mode is disabled.

• The VLANs to be protected must be first added in menu Configuration > VLAN Configuration(802.1Q Virtual Bridge).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 MPR Node Software Download Menu 71.1 Server Access Configuration 81.2 Init Software Download 91.3 Software Status 101.4 Software Status 111.5 How to upgrade the software from an older version 13

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 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 directoryname 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 defaultconfiguration.

• The CT is the default FTP server with the following parameters:

• User Id: anonymous

• Password: -

• Address: local host IP address.

• Port: 21

• Root Dir: /

• The System Default can be changed by writing different values in the fields and then by clicking OK .


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Follow the steps to perform this procedure:

1. Click Add to add the available software packages on the PC.

2. Browse to the directory where the NE software was installed and click Open.

3. Highlight the description file (i.e. R95M.DSC) and click Open.

4. Highlight the line and click on the Init Download button.

The Forced check box can be used to force download (i.e. the complete description file is downloaded tothe NE).

5. Click Yes to begin the download process.

6. When the SW download starts, a screen showing the in progress operation of the download appears. Thedownload is aborted if the Abort button is pressed.

7. Click Ok .

Recommended operation: Before to start the software download it is recommended to disable the ATPC operation (if it has been enabled) and to set in RTPC mode the max.Tx power.

Warning: if the Software Download is in progress and more managers are connected to the same NE,the WebEML makes grey the Init Download button to save the NE from contemporary andconcurred downloads.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 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

• With MPT-HC the Sw Status is available only after the MPT-HC software download completion.

• The equipment software is installed on the compact flash, which has two banks.

• This screen has two panels (each for one bank):

• panel 1 refers to bank 1 with the Committed software and relevant information;

• panel 2 refers to bank 2 with the Stand by software and relevant information.

• The Flash Card, which stores the NE software, contains 2 banks.

• The 2 banks can store 2 different software versions. One bank will be committed (active) and the other bank will be standby.

• 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 thestandby bank.

• To activate the new version first check the operational status of the standby bank.

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Click the Software Units Status button. A screen opens that displays additional information on thesoftware package.

• The following information is displayed on the screen:

• MDPAR: firmware version of the FPGA involved in the MSS/ODU communication channel

• OC_R: software on the ODU300 Controller (ODU300)

• BOMPT, FGUIN, MDPAR, FDUFF, FCERE, FDUJU, FMPVG, SWMPT, FADAM, FMSS1, PAMPT, PAMM1

•The other software packages are the FPGA softwares in the other units.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




A

AIS Alarm Indication Signal

AMI Alternating Mark Inversion

ANSI American National Standards Institute

APT Active Problem Table

ASAP Alarm Severity Assignment Profile

ASIC Application Specific Integrated Circuit

ATPC Automatic Transmit Power Control

AVC Attribute Value Change

B

BBE Background Block Error

BER Bit Error Rate

BIP Bit Interleaved Parity

C

CAS Channel Associated Signaling

CD Current Data

CES Circuit Emulation Service

CESoETH Circuit Emulation Service over Ethernet

CESoP Circuit Emulation Services over Packet

CFA Carrier Failure Alarm

CLA Common Loss Alarm

CRC Cyclic Redundancy Check

CRU Clock Reference Unit

CSM Control and Switching Module (Core module)

CSM-E Enhanced Control and Switching Module (Core module)

CT Craft Terminal

D

DC Direct Current

DL Data Link

DS Differentiated Services

DS1 Digital Signal Level 1

DS3 Digital Signal Level 3

DSCP Differentiated Services Code Point

DWRR Deficient Waited round Robin

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




H

HBER High Bit Error Ratio

HD History Data

HDB3 High Density order 3 Bipolar encoding

HET Hetero frequency

HQP High Queue Preempt

HS Hitless Switch

HSB Hot Standby HSDPA High Speed Data Packet Access HSSD Hot-Standby Space Diversity

HW Hardware

I

IDU Indoor Unit

ILM Infomodel Level Management

IM Information Model

IP Internet Protocol

ISAM Indexed Sequential Access Method

ISPB Intra Shelf Parallel Switching

IWF Interworking Function

J

JA Jitter Attenuator

JTAG Joint Test Action Group

JUSM Java User-based Security Model

K

L

LAN Local Area Network

LAPD Link Access Procedure on D-channel

LBER Low Bit Error Ration

LIM Link Identifier Mismatch

LIU Line Interface Unit

LOF Loss Of Frame

LOS Loss Of Signal

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




M

MAC Medium Access Control

MAU Medium Attachment Unit

MCF Message Communication Function

MCT Microwave Craft Terminal

MEF8 Metro Ethernet Forum

MEN Metro Ethernet Network

MIB Management Information Base

MOD300 Radio Interface Module

MOD300EN Enhanced Radio Interface Module

MPR Microwave Packet Radio

MPT Microwave Packet Transport

MPT-HC Microwave Packet Transport – High Capacity

MPT-HL Microwave Packet Transport – High Power, Long Haul

MPT-MC Microwave Packet Transport – Medium Capacity

MRTIE Maximum Relative Time Interval Error

MSOH Multiple Section Overhead

MSS Microwave Service Switch

MTIE Maximum Time Interval Error

MXC Microwave Cross Connect

N

NE Network Element

NEtO Network Element Overview

NMS Network Management System

NNI Network Node Interface

NRZ Not Return to Zero

NSA Not Service Affecting

NTP Network Time Protocol

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




O

OC ODU Controller

ODU Outdoor Unit

ODU300 Outdoor Unit 300

OFS Out of Frame Second

OH Overhead

OMS Operations Management System

OOF Out Of Frame

OS Operation System

OSPF Open Short Path First

P

P2E3DS3 DS3 Module

P32E1DS1 DS1 Module

PDH Plesyochronous Digital Hierarchy

PDU Protocol Data Unit

PDV Packet Delay Variation

PFoE Power Feed over Ethernet

PLM Payload Mismatch

PLM Physical Level management

PM Performance Monitoring

PMMF Physical Machine Management Function

PNU Packet Node Unit

PPM Part Per Million

PPP Point-to-Point Protocol

PPPoE Point-to-Point Protocol over Ethernet

PRBS Pseudo Random Binary Sequence

PRS Clock Primary Reference Source Clock

PSN Packet Switched Network

PSU Power Supply Unit

PTU Packet Transport Unit

PWE3 Pseudowire emulation edge to edge

Q

QAS Quadrature Amplitude Modulation

QoS Quality of Service

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




R

R99 Original standard for UMTS WCDMA based network

RAI Remote Alarm Indication

RDI Remote Defect Indication

REI Remote Error Indication

RFC Remote Frequency Control

RI Remote Inventory

RPS Radio Protection Switching

RSOH Regenerator Section Over-Head

RSL Receive Signal Level

RSSI Remote Signal Strength Indication

RTPC Remote Transmit Power Control

RTU Right To Use

RU Rack Unit

S

SA Service Affecting

SD Space Diversity

SDH Synchronous Digital Hierarchy

SerDes Serializer/Deserializer

SES Severely Errored Second

SF Signal Fail

SFP Small form-factor pluggable transceiver

SGMII Serial Gigabit Media Independent Interface

SNMP Simple Network Management Protocol

SP Spare

SP Strict Priority

SPI Serial Peripheral Interface

SW Software

SWP Software Package

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




T

TBI Ten Bit Interface

TCA Threshold Crossing Alarm

TCO Total Cost of Ownership

TD Threshold Data

TDEV Time Deviation

TDF Total Discarded Frames

TDM Time Division Multiplexed

TDM2ETH Time Division Multiplexed To Ethernet

TDM2TDM Time Division Multiplexed To Time Division Multiplexed

TIM Trace Identifier Mismatch

TMN Telecommunication Management Network

TPS Transmit Protection Switching

TRCF Total Received Correct Frames

TRCO Total Received Correct Octets

TRSEF Total Received Service Errored Frames

TS Time Slot

TSM Transmission Systems Manager

TTF Total Transmitted Frames

TTO Total Transmitted Octets

TTP Trail Termination Point

U

UAS UnAvailable Second

UAT UnAvailable Time

UI Unit Interval

UMTS Universal Mobile Telecommunications System

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




V

VC-n Virtual Container - n

VLAN Virtual Local Area Network

VMMF Virtual Machine Management Function

W

WCDMA Wideband Code Division Multiple Access

WebEML Web Element Manager Layer

WiMAX Worldwide Interoperability for Microwave Access

WK Working

WRR Weighted Round Robin

WT Wireless Transmission

WTPM Wireless Transmission Performance Monitoring

X

XPIC Cross-Polarized Interference Cancellation

Y

Z

ZBTSI Zero Byte Time Slot Interchange

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Appendix A · Module 1 · Page 1

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 Initial Configuration 71.1 General Requirements 81.2 Initial Turn-up 101.3 Enable Plug-In Cards 141.4 Provision Plug-In Cards 371.5 Provision XPIC 671.6 Provision Synchronization 681.7 Provision NTP protocol 691.8 Provision NE Time 701.9 Provision VLAN 711.10 Provision Cross-connections 721.11 Provision AUX Cross-Connections 731.12 Provision Ethernet Ring 74

1.13 Provision LAG 751.14 Provision QoS 761.15 Provision Ethernet Connectivity fault management 771.16 Provision System 781.17 Provision Local NE IP Address 831.18 Provision TMN Ethernet Port 841.19 Provision TMN Ethernet Port 851.20 Provision TMN in-band 861.21 Provision IP Static Routing 871.22 Provision OSPF Static Routing 89 2 Provisioning by Provisioning tool 912.1 Start Provisioning Tool 922.2 Provisioning Tool screens 95

2.3 Configuration Options Screen 992.4 Core-E Configuration 1002.5 E1 configuration 1032.6 STM-1 configuration 1042.7 Modem Provisioning 1062.8 MPT Access configuration (1+0) 1102.9 MPT Access Provisioning 1112.10 MPT Access configuration (prot. enabling: 1+1) 1162.11 MPT Access Prov. (without A. M.) (1+1) 1172.12 MPT Access Prov. (with A. M.) (1+1) 1192.13 Synchronization Configuration 1212.14 XPIC Configuration 1252.15 Ring Configuration 126

2.16 Cross Connections Configuration 1272.17 Segregated Port Configuration 1282.18 802.1D management 1292.19 802.1Q management 1302.20 VLAN Management 1322.21 Port VLAN Configuration 1332.22 Network Configuration 1342.23 Trusted Managers 1362.24 Typical Report Panel 137

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• 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 theconfiguration information will be erased (radio parameters, synch, XCONN, network, ecc). Theinformation of SWP is maintained (the stand-by and active SWP banks are not deleted).

5. It is possible to understand when the scratch procedure is over: make a “ping” towards NE withdefault 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.

• Average time necessary to scratch the database (from SW start): 6-7 minutes.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Profile Types – there are four user profiles defined.

• Administrator (full access also for NMS local system security parameters).

• CraftPerson: person in charge for installation and the mantenance at radio site; full access to NEbut not for security parameters, only for own password.

• Operator (person in charge to operate at the network level, not at the radio side).

• Viewer (view screens only).

• Default User Accounts – at the NE installation time, two default user accounts are created on NE

independently from the SNMP operating mode.

• Profile: administrator

• Username: initial

• Password: adminadmin

• Profile: craftPerson

• Username: Craftperson

• Password: craftcraft


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Changes to provisioning do not have to be made in any particular order.

• See the figure for the recommended sequence.

• Warning: If from this NE remote NEs have to be reached, remember to configure properly theRouting Protocol of the PPP RF channel, if the remote NE is connected through the radio link or of the NMS Ethernet Port, if the remote NE is connected through the Ethernet cable.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

This operation must be done to enable the EPS protection.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

ODU is automatically enabled when Modem Card is enabled.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

zODU is automatically enabled when Modem Card is enabled.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

This operation must be done to enable the protection: 1+1 FD or 1+1 HSB.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Two unprotected or protected MPT-HC or MPT-MC can be connected to one MPT Access unit.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

This operation must be done to enable the protection: 1+1 FD or 1+1 HSB.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• (8): If the electrical Ethernet port has to be used as Synchronous Source, the Ethernet port mustbe set as Synch-E Slave.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• (7): If the electrical Ethernet port has to be used as Synchronous Source, the Ethernet port mustbe set as Synch-E Slave.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Flow ID number is system unique and must not be repeated in radio network. Loss of STM-1 datacan occur.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

[2] Put a check mark in the Port Status box to enable the STM-1.

[3] Set the Auto Laser Shutdown: Enabled/Disabled ForcedOn/Disabled ForcedOff. This field will

appear only if the Settings tab-panel of the STM-1 unit the optical SFP has been selected.

[4] Select the Clock Source.

[5] Enable the J0, if required, by selecting one of the two modes(SixteenBytesFrame/OneRepeated

Byte) in the Expected Receiving Value field and enter the expected value and in theSending J0

field select one of the two modes and enter the value to be transmitted. Note: byte J0 is onlyread,

no Regeneration section Termination is done.

[6] Click Apply.

[7] Enable, if required, the E1 Node Timing Configuration. The Node Timing is the timingfrom the

network clock as defined in G.8261. The enabling of the Node Timing is applied to all E1s of the unit.

By enabling the Node Timing the E1 streams in Rx side are retimed at the output with thenetwork

element clock.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

[8] Configure all the E1s to be mapped/demapped in the STM-1. The E1s are identified by aprogressive number from #1 to #63, but also by the standard SDH identification (x-y-z).

The E1 tab-panel performs all available functions for the tributary.

[9] Select Settings.

[10] Signal Mode:The possible values are:

zUnframed for the unframed received signal

zFramed for the collection of the performances at the input in Tx side and at the outputin Rx side

zDisabled

[11] Click Apply.

[12] Service Profile:The possible profiles are:

zTDM2TDM

zTDM2Eth

[13] Flow Id: To implement cross-connections between line side and radio side each E1 tributarymust be associated to an identifier. Enter the Flow identifier value in the relevant field (possiblevalues: 2 to 4080) and press Apply.

[14] Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if theService Profile is TDM2Eth.Note: The service profile must be the same for all the E1s.

[15] Alarm profile: Not implemented now.

[16] Click Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

With the Presetting mode the Adaptive modulation is disabled.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• When the Mode is changed from Presetting to Adaptive Modulation, the radio defaults to 14 MHzbandwidth 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:

• Reduce the quantity of E1 lines being transported to meet the required capacity.

• Increase Reference Channel Spacing.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• To unprovision an MPT:

• perform a Tx Mute;

• unprovision the MPT;

• remove the power supply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• With the Presetting mode the Adaptive modulation is disabled.


• The XPIC can be configured in 1+0 or 1+1 HSB (no adaptive modulation, no ATPC).NOT ALL the channel spacings and modulation schemes can support the XPIC Configuration.

• Select the suitable Polarization: Vertical or Horizontal.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The configuration of the ASAP unit is divided in four tab-panels:

• E1 Layer

• IMA Layer

• ATM Layer

• ATM PW Layer

• For the configuration of the tab-panels refer to S3-M2.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Configuration the Ethernet ports as explained in S3-M2.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• The configuration of the AUX unit is divided in two tab-panels:

• Settings

• External Points

• For the configuration of the tab-panels refer to S3-M1.

• For the ATM traffic the Traffic Descriptors must be also configured. Refer to Menu Configuration -> Traffic Descriptors in S3-M1.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Put a check mark in the NTP protocol field to enable the protocol and write in the Main Serveraddress field the IP address of the server, which is in charge to distribute the time to all the NEsin 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 NTPservers. The following information can appear:

• "Main server reachable"

• "Spare server reachable"

• "None servers reachable"

• "Both servers reachable"

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

• Refresh push-button can be used to update the screen.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The user can synchronize the NE time from either the PC/laptop or Network Time Protocol (NTP)servers. Time and date provisioning is accomplished using the NE Time Configuration screens.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• Valid Cross Connections:

• Local User Service Cross-Connection

• Pass-through User Service Cross-Connection


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

1) Tributary Port Configuration• This field allows to set the suitable impedance of the E1 stream (Unbalanced 75

ohms/Balanced 120 ohm). To activate the new impedance, click Apply.

2) 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 IPaddress.

• The DHCP server uses an address pool of 10 IP addresses, defined according to the NE TMNport IP address.

• The IP mask is set to the mask of the NE TMN port and the default gateway is set to the NE IPaddress.The lease time is fixed to 10 minutes.To activate the DHCP server, select Enabled and

click Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

3) Admission Control for Adaptive Modulation (ODU300 only)• The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive

Modulation) can be enabled or disabled. Default: “Enabled”.

• When the Admission Control is "Enabled", the check is performed taking into account thecapacity of the 4 QAM modulation scheme for the relevant Channel Spacing.

• Taking as example 28 MHz channel spacing (with around 130 Mbit/s of net throughputavailable with 64QAM), the maximum number of E1s that could be provisioned is 18; theremaining capacity is devoted to other types of traffic such as ATM or Ethernet.

• When RSL value decreases, modulation schemes are downgraded first from 64QAM to 16QAM:the traffic with lower priority exceeding 16QAM bandwidth is dropped and of course the E1sare kept. As soon as the RSL value further decreases, modulation scheme are downgraded to

4QAM and all the traffic exceeding 4QAM bandwidth is dropped (while the E1s are kept).• When the Admission Control is "Disabled", the check is performed taking into account the

capacity of the highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-16-64 QAM range or 16 QAM for 4-16 QAM range).

• It is possible to provision a number of E1s exceeding the 4QAM throughput; always keeping 28MHz channel as example, it is possible to provision more than 18E1s, up to 37E1s (value linkedwith 16QAM capacity). In this case, when RSL value degrades and modulation scheme isdowngraded from 16QAM to 4QAM, all the TDM traffic is impacted. This feature is answeringthe need of transmitting an high number of E1s, but without giving up the benefits of adaptivemodulation for Ethernet traffic.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

4) Ethernet LOS Criteria

• By enabling this feature the following additional criteria are added to the Core protectionswitching criteria:

• LOS of Optical User Ethernet interface

• Card Fail of SFP optical module

• Card Missing of SFP optical module

• LOS of any Electrical User Ethernet interfaces, including the LOS of the forth User Ethernetinterface working as TMN Local Ethernet interface.

• Note: the default switching criteria are:

•

Core Card Missing• Core Card Fail

• Control Platform operational status failure

• Flash Card realignment in progress

• Flash Card failure

5) Static Lag Criteria

• This feature is available only if the spare Core unit has been installed.

• By enabling this feature the Ethernet ports of the Core-E unit in stand-by are in ON state (asthe ports of the Active Core-E unit), but the Ethernet traffic is not forwarded.

• This behavior allows to reduce the out of service time of user traffic passing through the UserEthernet interfaces in case of Core protection switching.

• This feature shall not be used, when the NE is connected to an equipment performing Link Aggregation and not supporting Active/Standby management of aggregated links.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

6) System Priority Parameter • This parameter is required to provision the System Priority (2 bytes) associated to the NE.• This parameter, together with the System ID (the NE MAC address), determines the System Aggregation Priority (8 bytes). The range for the System Priority parameter is: 0 to 65,535(default: 32,768).

• System Aggregation Priority:• [0 - 1 bytes] System Priority• [2 - 7 bytes] NE MAC address

• The System Aggregation Priority of each System is an eight octet binary number. The Systemwith the numerically lower value of System Aggregation Priority has the higher priority.

• The Ports are selected for aggregation by each System based upon the port priority assignedby the System with the higher System Aggregation Priority, starting with the highest priority

port of the System with the higher priority, and working downward through the ordered list of Port Aggregation Priority values for the N ports, applying the particular constraints imposed onthe System concerned.

7) Event and Alarm Log

• As default the Logging is enabled. If set to "Disabled" the events are not sent to the Event LogBrowser application.

8) NE MAC Address

• This field is a read-only field, which shows the MAC address of the NE. This MAC address must

be used in the cross-connection with TDM2Eth profile.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

After IP address change, the NE restarts.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Note:

Follow the steps to provision.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Follow the steps to provision Open Shortest Path First (OSPF) protocol static (automatic) routing.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

•The Provisioning Tool can be used "offline" and "online".

• In case of offline, it allows to prepare the provisioning in back office. Minimizing time on fieldand mistakes.

• With the online mode you can either apply the "offline" configuration or fulfill online.

• This tool is recommended for first installation.

• Thanks to a step by step approach this tool is easy to handle and allows to minimize time forprovisioning

• WebEML is more flexible and mandatory to configure AUX and ATM boards (not yet supported inprovisioning tool).

• Select:

• the direct connection to the NE by putting a check mark on “Connect to NE”. When youlocally connect the PC to the NE, in the IP Address field automatically (through theautodiscovery) appears the IP Address of the NE (in the NE the default configuration of theDHCP server is enabled; for this reason your PC must be configured to obtain an IP Addressautomatically).

• Click on OK .

• If the DHCP server is disabled, the IP address to be entered is the IP address of the NMSEthernet port.

• or

• the off-line configuration by putting a check mark on “Do not connect to NE” and by clicking

on Apply.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• Open: allows opening an existing MCML (XML-based) configuration file. MCML file can containsNE 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 aconfiguration file created in an older version. If an older configuration file is open a new screenappears, which asks to convert the file.

• By clicking on the "Create" button it will be possible to create a file in the current version or inthe older version.

• After opening a configuration file, the user will see a configuration preview in order tounderstand, for example, if the file is correct and contains the wanted configuration. Click "Next"button from such preview panel or "Create" button.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

• Open: allows opening an existing MCML (XML-based) configuration file. MCML file can containsNE 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 uploadthe configuration from the NE to the tool.

• Create: allows to create a new configuration file.

• Prev: not operative.

• Cancel: not operative.


• By clicking on the "Open" button a window opens, which gives the possibility to open aconfiguration file created in an older version. If an older configuration file is open a new screenappears, which asks to convert the file.

• By clicking on the "Create" button it will be possible to create a file in the current version or inthe older version.

• After opening a configuration file, the user will see a configuration preview in order tounderstand, for example, if the file is correct and contains the wanted configuration. Click "Next"button from such preview panel or "Create" button.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Note:

• Press the Clear Database and Restart NE button and then press Create to create a newconfiguration or press Open to open a previously created configuration.

• If you don't press the Clear Database and Restart NE button at the end of the configurationyou can save the file, but you cannot apply the configuration to the NE. (The Apply button willnot be available at the end of the procedure).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• This screen is a generic one that depicts all of the pull-down options possible depending on whichcard is selected in the card slot. Protections options shown are for all cards.

• Warning: the Provisioning Tool allows to configue all the units, except the EAS unit, ASAP unitand AUX unit. (The EAS unit, ASAP unit and the AUX unit must be configured with the LCT).

• Warning: To configure the equipment extract the ASAP and/or AUX units, if any.

• The SDH unit is available in 2 versions:

• SDHACC (operation in transparent mode)

• SDHCHAN (operation in channelized mode)

•

Warning: If from this NE remote NEs have to be reached, remember to configure properly theRouting Protocol of the TMN-RF channel, if the remote NE is connected through the radio link orof the NMS Ethernet Port, if the remote NE is connected through the Ethernet cable.

• Buttons:

• Restore: allows to restore in the screen the initial data without any change

• Prev: the procedure goes back to the previous step (the changed data may be lost after theWarning message)

• Next: the procedure goes on to the next step (some checks and data storage is done)

• Cancel: the procedure goes back to step 1 (Opening screen)



7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• A white icon indicates that there are no cross-connections, but cross-connections can becreated.

• A blue icon indicates the destination is full. The limits granted by the license key have beenexceeded. 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 canaccept more E1 ports.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real TimeProtocol 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 RTPand other service profiles not using RTP.

• Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure otherE1 with service profile TDM2Eth only with the Differential clock source (not with the Adaptiveclock source).

• If the Adaptive clock source is requested the E1 must be connected to another PDH unit.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• With the Adaptive Modulation the only available configuration is: 1+0 or 1+1 HSB.

• The operator can modify only the 4 QAM field. In this field the operator has to enter the constantpower, which will be used with 4 QAM modulation. The power range is shown on the right sideand depends on the selected reference mode.

• The same power value will be used by the 16 QAM and 64 QAM modulation schemes.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The selection of the Power Supply mode to supply the MPT can be: PFoE (through 1 cable for MPT-MC or MPT-HC with the DC Extractor) or QMA (through 2 cables for MPT-HC).


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:


• The XPIC can be configured in 1+0 or 1+1 HSB (no adaptive modulation, no ATPC).

• NOT ALL the channel spacings and modulation schemes can support the XPIC Configuration.

• To configure the XPIC go to “MPT-HC V2 with XPIC” slide.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:


• The XPIC can be configured in 1+0 or 1+1 HSB (no adaptive modulation, no ATPC).

• NOT ALL the channel spacings and modulation schemes can support the XPIC Configuration.

• To configure the XPIC go to “MPT-HC V2 with XPIC” slide.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

To configure the XPIC refer to S3-M2.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

To create the Cross-Connection refer to S3_M3.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

To segregate the ports refer to S3_M3


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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

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

• There is no check on unambiguity name.

3. VLAN Ports field: Select the ports members of this VLAN by putting a check mark on therelevant 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 implicitlyenabled) can be member of a VLAN. This means that a disabled port can be configured as amember 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 Ethernetports, enabled and disabled, are manageable. The VLAN cannot be removed from the radioports (with the exception of the VLAN 1).

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

• Tagged frames - If one tagged packet with VLAN-ID X is received on a port which is not memberof the VLAN-ID X, the packet is dropped.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

The Port VLAN Configuration screen opens only if in the Bridge Configuration screen the 802.1Q(Virtual Bridge) has been selected.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

A Trusted manager is an SNMP manager to which the NE automatically sends the TRAPS generatedinside the NE.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

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 thedownload of the configuration to the NE

• Cancel: the procedure goes back to step 1 (Opening screen)


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Appendix B · Module 1 · Page 1

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





Document History




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




Page

1 MPR Management 71.1 9500 MPR Management 81.2 MPR IP addresses 91.3 TMN communication channels 111.4 TMN interfaces (9500 MPR Node) 121.5 LCT Connection 131.6 MPR Capability – IP Parameters 14

7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0





7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

Refer to the attached diagram as an example of the IP address assignment.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0



Notes:

• With the introduction of TMN In-Band two new IP interfaces are added to those already available.

• NE Local IP Address

• TMN Local Ethernet interface, IP/subnet

• TMN Out-of-Band interface on User Ethernet port 4, IP/subnet

• TMN In-Band interface #1, IP/subnet

• TMN In-Band interface #2, IP/subnet

• User Ethernet port 4 can then used as:

• pure Ethernet traffic interface

• pure Out-of-band TMN Local Ethernet interface

• Ethernet traffic interface carrying TMN In-Band traffic

• The NE Local IP Address can be reused on one of the other TMN interfaces. These interfacesmust have different IP subnets.


7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0




7/22/2019 TWT42025-R4.0-SG1-SEN-I2.0


1 Management System

Example of MPR IP addresses

Node A

Node B

NE IP 10.0.3.1

NMS IP 10.0.10.1

NE MAC 00:20:60:05:02:07

NMS P4 OFF

OSPF AREA 0.0.0.1

1+1 HSB

Traffic E1+ETH

TMN

Traffic E1 TDM2ETH

Traffic ETHPort Number

VLAN ID

Traffic E1 TDM2TDM

VLAN ID

11 12 13 14 27 28 41 42

1 2 3 4 17 18 3132

1 2

VLAN ID

27 28

1,2,…

1,2,…

ETH 1

ETH 2

NE IP 10.0.3.2

NMS IP 10.0.30.2

NE MAC 00:20:60:05:02:08

NMS P4 OFF

OSPF AREA 0.0.0.1

NE IP 10.0.3.3

PC IP 10.0.10.100

DEFAULT GATEWAY 10.0.10.1TDM A

TDM C

TDM B

TDM C

Example of MPR IP addresses

twt42025-r4.0-sg1-sen-i2.0

Documents