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

from Alcatel-Lucent Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

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 training course 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 AlcatelLucent from time to time without prior notice to you. Your use of the Alcatel-Lucent training materials after such update or amendment 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 voltages present. Always observe all safety precautions and do not work on the equipment alone. The user is strongly advised not to wear conductive jewelry while working on the products. Equipment referred to or used during this course may be electrostatic sensitive. Please observe correct anti-static precautions. PERMISSION TO USE CONTENT The information, communications, scripts, photos, text, video, graphics, music, sounds, images and other materials provided in this training course (collectively the "Content"), is intended for the lawful use of employees of Alcatel-Lucent and other authorized participants in this Alcatel-Lucent training course. You are hereby granted a non-exclusive, nontransferable permission to access and use the Content solely for your personal training and non-commercial use. This permission may be terminated by Alcatel-Lucent at any time for any reason or no reason, with or without notice. You must immediately 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 rights laws (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 and presentation of the Content. Alcatel-Lucent does not grant you any permission to use the Content other than the permission expressly stated in these Terms 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 derivative works from, distribution, performance, display, incorporation into another training course or presentation, or in any other way exploiting any of the Content, in whole or in part, for uses other than those expressly permitted herein is strictly prohibited and shall not be made without Alcatel-Lucent’s prior written consent. All characters appearing in this training course 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 the Content. Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logos are trademarks of Alcatel-Lucent. All other trademarks are 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 for training 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, STRICT LIABILITY OR OTHERWISE, THAT ARISES OUT OF OR IS IN ANY WAY CONNECTED WITH (A) ANY USE OR MISUSE OF THE CONTENT 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 is governed by the laws of the country that governs your employment contract, if applicable. If any provision of these Terms of 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 a provision that reflects the intent of the original provision as closely as possible. All other provisions of these Terms of Use and 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 an offer 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

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

Welcome to 9500 MPR-E (Microwave Packet Radio) ETSI R4.0 Node Configuration Operation & Maintenance Section 1 Product Overview Introduction Architecture

Module 1 Module 2 Section 2

Functional Description MSS Hardware Architecture ODU300 Hardware Architecture MPT-HC Hardware Architecture MPT-HC V2 Hardware Architecture MPT-MC Hardware Architecture

Module 1 Module 2 Module 3 Module 4 Module 5 Section 3

NE Operation TCO Operator Interface

Module 1

Module 2
Module 3 Module 4 Section 4

Equipment Views & Settings
Cross-Connection Configurations Performance Monitoring

Maintenance Fault Management Protection Software Download

Module 1 Module 2 Module 3 Section 5 Terms

Module 1 Appendix A Module 1 Appendix B

Acronyms

Initial Configuration

Module 1

MPR Management
Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Page 3

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

Describe the basic concepts of the 9500 MPR Turn-up and provision the system Respond to and manage alarm conditions Monitor system and application status Maintain 9500 MPR hardware and software

Your feedback is appreciated! Please feel free to Email your comments to: training.feedback@alcatel-lucent.com Please include the following training reference in your email: TWT42025 Edition 2.0 Thank you!

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Page 4

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Page 5

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Page 6

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Page 7

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Page 8

This page intentionally left blank

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Page 9

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Page 10

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 1

This page is left blank intentionally

Document History Edition 3.4 4.0 Date 2012-06-14 2012-09-15 Author AL University AL University Remarks First edition Updated for release 4.0

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 2

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 3

This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 4

Page 1 Understanding the 9500MPR Innovations 7 1.1 Classification of the New Generation Products 8 1.2 Presentation 9 1.3 Multiservice Aggregation Layer 12 1.4 Service Awareness 13 1.5 Packet Node 14 1.6 Service-driven Packet Adaptive Modulation 15 1.7 Power Consumption Reduction 16 1.8 Hybrid or Packet Mode: for Efficient Data Transport 17 2 MPR in New Market Segments 19 2.1 The Most Effective Solution 20 2.2 MPR-e Enabling Zero-Footprint Microwave Configurations 22 2.3 MPR in Last Mile 23 2.4 LTE and Full Ethernet 3G Ready 24 2.5 From Current PDH/SDH Network to Packet Transport Network Evolution 25 2.6 MPR addresses All Microwave Applications in Aggregation 26 2.7 MPR addresses Metro Ring/Partial Mesh Application 27 3 System Description 29 3.1 Alcatel-Lucent 9500 Microwave Packet Radio 30 3.2 9500 MPR System Family 31 3.3 9500 MPR Key Features 33 3.4 9500 MPR Node 35 4 Radio Configuration 45 4.1 Radio Configuration 46 5 System Configuration 47 5.1 Example of System configurations 48 6 Management Systems 53 6.1 Network Management 54

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 5

This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 6

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 7

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 8

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 9

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 10

Notes:

• Multiservice aggregation layer - the capacity to use Ethernet as a common transmission layer to

transport any kind of traffic, independently by the type of interface. Ethernet becomes the convergence layer. of service assigned, independently by the type of interface type of service requirements and type of interface

• Service awareness - traffic handling and quality management, queuing traffic according to the type

• Packet node - no service aggregation limits with all traffic aggregated in packets, in term of: capacity, • Service-driven adaptive modulation- fully exploit the air bandwidth in its entirety by changing
modulation scheme according to the propagation availability and allocate transport capacity, discriminating traffic by different services, only possible in a packet-based environment

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 11

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 circuit emulation 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 speed downlink 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 GSMbased networks. WCDMA (Wideband Code Division Multiple Access) – interface standard found in 3G mobile telecommunications networks. WiMAX (Worldwide Interoperability for Microwave Access) - telecommunications protocol that provides fixed and mobile Internet access

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 12

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, coming from different sources, and therefore having different requirements. For instance, DS1 or ATM traffic from a 3G base station can carry voice (high priority, real time service) and data (lower priority and possibly non real time with high variability load, such as internet browsing, music download or video streaming). zService awareness is what allows identifying the traffic types, and in the case of non real time variable bit rate one, optimize the band with overbooking of the radio scarce resource.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 13

aggregate and handle any of the possible incoming traffic types with virtually no capacity limits (up to 10 GB/s). All Rights Reserved. Copyright © 2012 Alcatel-Lucent. Packets can be transported over Ethernet or PDH in any direction.Notes: • 9500 MPR offers a SINGLE PACKET MATRIX able to switch. service types and interface types. Note: The TDM can be also E3. Edition 2 Section 1 · Module 1 · Page 14 . avoiding service aggregation bottlenecks in terms of capacity. • • The MSS can also provide Gigabit Ethernet (GigE) and metallic uplinks.

Notes: • • Traffic with high priority will always have bandwidth available. with modulation scheme changes driven by propagation conditions. Copyright © 2012 Alcatel-Lucent. like voice (deterministic approach) Broadband traffic is discriminated by QoS dynamically. Edition 2 Section 1 · Module 1 · Page 15 . All Rights Reserved.

This product improves packet aggregation. increases bandwidth. It also adapts packets to the air conditions and quality required by different service types. so it efficiently transports multimedia traffic by handling packets natively while still supporting legacy TDM. and optimizes Ethernet connectivity. All Rights Reserved.Notes: This true packet product is not based on TDM (circuit-based) technology. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 1 · Page 16 .

Edition 2 Section 1 · Module 1 · Page 17 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 1 · Module 1 · Page 18 .544 Mb/s interface Copyright © 2012 Alcatel-Lucent.048 Mb/s interface 34 Mb/s interface Ethernet Gigabit Ethernet IMA MPLS PDH T1 Inverse Multiplexing over ATM Multiprotocol Label Switching Plesiochronous Digital Hierarchy 1. All Rights Reserved.Notes: DSL E1 E3 Eth GigE Digital Subscriber Line 2.

Edition 2 Section 1 · Module 1 · Page 19 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 20 .

Edition 2 Section 1 · Module 1 · Page 21 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 22 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Hybrid & Packet operational modes Zero foot print for Ethernet applications. to cover all MW applications under a single platform „ • • Introducing 9500 MPR-e Î stand-alone “full outdoor” Existing compatibility with 9500 MXC Copyright © 2012 Alcatel-Lucent. ½ rack length. common to all MSS platform. Edition 2 Section 1 · Module 1 · Page 23 . MW radio protection. enables integrated solution for MPLS metro network Multipurpose ODU Î the MPT. Very low power consumption.Notes: • • Extended 9500 MPR packet transport family to cover last mile access Î MSS-1c „ Low cost.

and packets that exceed that number are held back until the next visit of the scheduler.is a scheduling method for packets of variable size. A maximum packet size number is subtracted from the packet length.Notes: • • • CAC (Call Admission Control) . Edition 2 Section 1 · Module 1 · Page 24 . It is used in the call set-up phase and applies to real-time media traffic as opposed to data traffic. HPQ (High Preempt Queue) NMS • • Copyright © 2012 Alcatel-Lucent.prevents oversubscription of VoIP networks. ??CBR – Constant Bit Rate or Constraint Based Routing?? DWRR (Deficit Weighted Round Robin) . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 25 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 26 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 1 · Page 27 . All Rights Reserved.

Edition 2 Section 1 · Module 1 · Page 28 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 1 · Page 29 . All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 1 · Page 30 .

Edition 2 Section 1 · Module 1 · Page 31 .a standardized technology used to transport ATM traffic over a bundle of T1 or E1 cables where a stream of Asynchronous Transfer Mode cells is spread over multiple physical links. Backward compatibility with hybrid installed base • Copyright © 2012 Alcatel-Lucent.Notes: • IMA (Inverse Multiplexing over ATM) . All Rights Reserved.

Up to 8 can be powered directly by the MSS-8 shelf.Notes: • 9500 MPR in the stand alone (zero-footprint) architecture is built by only one unit for Ethernet applications: • Outdoor Unit. • 9500 MPR in the split mount architecture is built by two separate units: • MSS (Microwave Service Switch): indoor unit for split mount and stand alone configurations (Ethernet uplink) • Outdoor Unit. • Outdoor Unit is connected to the MPLS metro networks equipment with one coaxial cable for the power supply and one Ethernet optical or electrical cable (with MPT). • • • • 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 14 MPT can be connected to an MSS-4 Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 1 · Page 32 . All Rights Reserved. • MSS and Outdoor Unit are connected with a single standard coaxial cable (with ODU300) or with one coaxial cable for the power supply and one Ethernet optical or electrical cable (with MPT).

Edition 2 Section 1 · Module 1 · Page 33 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

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

Notes: • • • • The 9500 MPR Node supports up to 18 RF links for operation on the same or different frequency bands using the MSS-8. The ODU for each link is connected to a plug-in card inside the site aggregator. Edition 2 Section 1 · Module 1 · Page 35 . management. 9500 MPR Node supports a mix of non-protected and protected or diversity operation for single link. All Rights Reserved. and so on. repeater or star radio configurations. Copyright © 2012 Alcatel-Lucent. Other plug-in cards provide line interface access (TDM and native IP).

All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 36 .4/8 (MSS-4 / MSS-8) Copyright © 2012 Alcatel-Lucent.Notes: Microwave Service Switch .

All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 37 .Notes: Supports unprotected or protected links Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 38 .Copyright © 2012 Alcatel-Lucent.

Notes: Supports unprotected or protected links Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 39 .

Edition 2 Section 1 · Module 1 · Page 40 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

it contains the logic for the EPS Core-E protection. Base-T. ATM traffic is transported within MPR network as "special" Ethernet traffic. the cable interface functions to ODU. the interface to/from the alternate Radio module (for RPS management). • The optional +24 Vdc/-48 Vdc Converter unit (to be installed in transport slot 4. This traffic is managed by the MPR using RFC 4717 (IETF ATM PseudoWire EdgetoEdgeeEmulation. with E1/IMA physical layer. • MPT access card (with PFoE): this unit is used to interface the MPT. manages the encapsulation/reconstruction of PDH data to/from standard Ethernet packets and sends/receives standard Ethernet packets to/from both Core-E modules.Notes: • 32E1/DS1 card: provides the external interfaces for up to 32xE1/T1 tributaries. • ASAP card: provides external interfaces to transport 16xE1 ATM traffic. in an MPR network. the RPS logic. It sends/receives standard Ethernet packets to/from both Core-E modules. Edition 2 Section 1 · Module 1 · Page 41 . PFoE (Power Feed over Ethernet) is used to carry the power supply to the MPT-HC through an electrical Ethernet traffic connector. • 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. All Rights Reserved. or Copper Cable access directly available on the EAS module. manages the encapsulation/reconstruction of SDH data to/from standard Ethernet packets and sends/receives standard Ethernet packets to/from both Core-E modules. Copyright © 2012 Alcatel-Lucent. manages the radio frame (on Ethernet packet form) generation/termination. 6 or 8 of MSS-8 can be used to power the MSS for +24 Vdc office applications. PWE3) with N-1 encapsulation format. Interfaces can be 1000BASE-LX (GbE LX 10 km) or 1000BASE-SX (GbE SX 550 m) or 1000BASECX (GbE CX 25 m) • Modem 300: this unit is used to interface the ODU300. • 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.

Notes: To manage more directions the “Stacking configuration” can be realized by installing up to 3 MSS. In the example of Figure are shown two interconnected MSS. All Rights Reserved. interconnected through the Ethernet ports in the Core-E module. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 1 · Page 42 .

Edition 2 Section 1 · Module 1 · Page 43 . 3 MSS can be interconnected as shown in figure.Notes: • • With the Core protection max. To enable this alarm the “Ethernet LOS Criteria” feature has to be enabled. To implement this configuration the LOS alarm on the Ethernet ports must be enabled as switching criterion of the Core protection. All Rights Reserved. Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 1 · Module 1 · Page 44 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 1 · Page 45 .

Edition 2 Section 1 · Module 1 · Page 46 . Copyright © 2012 Alcatel-Lucent.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. In 1+1 configuration the 2 ODUs must be of the same types. MPT-XP. or 9558HC can be implemented with or without an interconnection cable between the two ODUs. All Rights Reserved. MPT-HC V2.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 1 · Page 47 .

All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 48 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 1 · Page 49 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 50 .

Edition 2 Section 1 · Module 1 · Page 51 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 1 · Module 1 · Page 52 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 1 · Module 1 · Page 53 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

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

Copyright © 2012 Alcatel-Lucent.Notes: 9500 MPR can be managed: • by Alcatel-Lucent 1350 OMS Network Management System. Edition 2 Section 1 · Module 1 · Page 55 . All Rights Reserved. • by Alcatel-Lucent 5620 SAM.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 1 · Page 56 .

This page intentionally left blank Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 1 · Page 57 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 1 · Page 58 . All Rights Reserved.

Edition 2 Section 1 · Module 2 · Page 1 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition Updated for Release 4.4 4. Edition 2 Section 1 · Module 2 · Page 2 .0 Copyright © 2012 Alcatel-Lucent.This page is left blank intentionally Document History Edition 3. All Rights Reserved.

Edition 2 Section 1 · Module 2 · Page 3 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 4 .

3 Differential/Adaptative clock recovery 5. Edition 2 Section 1 · Module 2 · Page 5 .5 SDH2SDH 2.5.2 Clock Source Selection and Distribution 5.1 MSS 1.4 Synchronization Interface 5.4 TDM2Eth 2.4 L2 Ethernet LAG 5 Synchronization 5.2 MPT-HCV2 connectivity 1.2 QoS Configuration Overview 4 LAG (Link Aggregation Group) 4.7 ETH2ETH 2.1 Cross-connection 7 8 9 10 11 12 13 16 20 23 24 30 34 36 38 40 43 44 47 48 50 61 62 63 64 67 69 73 74 79 80 83 84 89 90 Copyright © 2012 Alcatel-Lucent.3 MPT-MC connectivity 2 Traffic Profiles 2.3 TDM2TDM 2.8 Ethernet Traffic Management 3 Traffic Management 3. All Rights Reserved.5.1 LAG overview 4.1.1 Link aggregation on Radio ports (Radio LAG) 4.3 MSS-ODU300 cable (Interfaces and Traffic) 1.2 Flash Cards with Licenses 1.6 ATM Traffic Management 2.5.2 L1 LAG 4.2 Traffic profiles 2.1 MPT-HC connectivity 1.1 Synchronization 5.1 Managed Services and profiles 2.3 L2 LAG 4.4 MPT 1.5 Synchronization Interface 6 Cross-connections 6.1 QoS Overview 3.Page 1 MSS Architecture 1.5 MSS-MPT Cable (Interfaces and Traffic) 1.

Page Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 6 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 7 .

2 modules in MSS-4) • 32 x E1 PDH access module (SCSI 68 32E1) • 2 x STM-1 access module (2 optional electrical or optical SFP) • ASAP (ATM 16xE1) access module (SCSI 68 16E1) • AUX peripheral module • Modem module (to ODU300) • MPT Access module (to MPT) Copyright © 2012 Alcatel-Lucent. All Rights Reserved.Notes: • Core-E platform: • symmetrical Cross-connection function • able to manage different radio directions • add-drop tributaries in case of local PDH/ASAP/Ethernet accesses • 4 x Electrical GbEth + 2 optional SFPs • Peripherals (6 modules in MSS-8. Edition 2 Section 1 · Module 2 · Page 8 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 9 .

ODU cable. Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 10 . connectors and grounding kits are separately provided. cable length is up to 150 m. The max. The ODU cable carries DC power (-48 Vdc) for the ODU and five signals: • • • • • • Tx telemetry Rx telemetry Reference signal to synchronize the ODU IQ Mod/Demod oscillator 311 MHz IQ modulated signal from the ODU300 Radio Interface (transmit IF) 126 MHz IQ modulated signals from the ODU (receive IF) Signal extracting and merging is carried out in N-Plexers within the ODU300 Radio Interface and ODU.Notes: • • A single 50 ohm coaxial cable connects a ODU300 Radio Interface to its ODU.

one coaxial cable for the Power Supply and one optical cable for the Ethernet Traffic (as MPT-HC). All Rights Reserved. The differences are: • MPT-HC V2 can be natively Ethernet powered through a proprietary PFoE (or as alternative by using two • MPT-HC V2 is XPIC-ready (by the installation of a dedicated module). Edition 2 Section 1 · Module 2 · Page 11 .Notes: • MPT-HC V2 is similar to MPT-HC from architecture standpoint and can be used as spare part of the MPT-HC. cables. Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. The second cable is an optical Gigabit Ethernet cable. Copyright © 2012 Alcatel-Lucent. This cable is an electrical Gigabit Ethernet cable with Power Feed over Ethernet (Not for MPT-HC).Notes: • Electrical connection . • Optical connection = (only for MPT-HC and MPT-HCV2) • • • • Two cables connect an MPT Access unit in the MSS to its MPT. MPT-HC and MPT-HCV2) • • • One cable connect an MPT Access unit in the MSS to its MPT. One cable is a 50 ohm coaxial cable to send the -48 V power supply to the MPT-HC/MPT-HC V2. The max cable length for optical Ethernet connection is 350 m. Edition 2 Section 1 · Module 2 · Page 12 . The max cable length for electrical Ethernet connection is 100 m.(for MPT-MC.

zMPT Access Card PoE z2 MPT per MPT Access Card 2x Coax connection (power feed in case of Optical connection) 2x SFP ports for optical connection option 2x 1000BaseT port with Power over CAT5e cable (Electrical connectivity Data+Power over a single CAT cable) Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 13 .

All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 14 .Notes: Pigtail: N-RJ45 two wires Transition Connector. Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 1 · Module 2 · Page 15 . Copyright © 2012 Alcatel-Lucent.Notes: MPT-HC must be connected to a fuse or a breaker on a customer power distribution box. The recommended value is 3 Amps. All Rights Reserved.

Notes: • • • One electrical Ethernet cable connects an MPT Access unit in the MSS to its MPT-HC V2 (the MPT Access unit provides the PFoE). The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001). All Rights Reserved. Copyright © 2012 Alcatel-Lucent. The max cable length is 100 m. Edition 2 Section 1 · Module 2 · Page 16 .

Copyright © 2012 Alcatel-Lucent. • The Ethernet optical cable is preassembled and available in different lengths (up to 450 m). for length higher than 100m. Note: A special cord adapter must be connected to the coaxial cable on the MPT-HC V2. the cable is a 50 ohm coaxial cable to send the power supply to the MPTHC V2 Note: In case of length lower than 100m and presence in the field of 1 coaxial already installed and free it is recommended to use the coax cable to minimize the installation effort.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 to • the MPT-HC V2 . All Rights Reserved. • The second cable is an Ethernet optical cable. The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001). Edition 2 Section 1 · Module 2 · Page 17 .

Copyright © 2012 Alcatel-Lucent. The recommended value is 3 Amps. the cable is a 50 ohm coaxial cable to send the power supply to the MPTHC V2 „ Note: In case of length lower than 100m and presence in the field of 1 coaxial already installed and free it is recommended to use the coax cable to minimize the installation effort. The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001). Note: A special cord adapter must be connected to the coaxial cable on the MPT-HC V2.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 to the MPT-HC V2 . Edition 2 Section 1 · Module 2 · Page 18 . The Ethernet optical cable is preassembled and available in different lengths (up to 350 m). Note: MPT-HC V2 must be connected to a fuse or a breaker on a customer power distribution box. • The second cable is an Ethernet optical cable. for length higher than 100m. All Rights Reserved.

All Rights Reserved. Copyright © 2012 Alcatel-Lucent.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 recommended value is 3 Amps. Edition 2 Section 1 · Module 2 · Page 19 .

All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 20 .Notes: • Both injectors include: • Powering of two MPT • Lightning protection • DC protection • LEDs for power output Power Injector plug-in Power Injector box Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.Notes: The MPT-HC must be connected to a fuse or a breaker on a customer power distribution box. The recommended value is 3 Amps. Edition 2 Section 1 · Module 2 · Page 21 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 22 . All Rights Reserved.

All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 23 .Copyright © 2012 Alcatel-Lucent.

• TDM to ETH – This is the service allowing the TDM traffic to be aggregated and output in a single ETH stream. • ATM to ETH (ETSI) – This profile allows the ATM service to be terminated and encapsulated into an Ethernet stream towards an IP/MPLS Core Network. • ATM to ATM (ETSI) – This profile allows the management of the ATM services inside a 9500 MPR network. E1s IMA/ATM are terminated/reconstructed at the borders of the 9500 MPR cloud. switched and provided to an external ETH network in standard format (MEF-8). switched and terminated inside a MPR network. • ETH to ETH (ETSI) DATA (ANSI) – This is not a real CES due to the native IP architecture of MPR.Notes: • TDM to TDM – This is the typical service associated to a traditional TDM network in which E1/T1 traffic is transported. VLANs etc. • SDH to SDH – This is the typical service associated to a traditional SDH transport network. switched and terminated inside a MPR network. Edition 2 Section 1 · Module 2 · Page 24 . Ethernet traffic is directly managed by the L2 switch on the Core board. All Rights Reserved. On this service specific algorithms are applied in order the E1/T1 is transported. thanks to the autolearning algorithm. STM1 traffic is transparently transported. Copyright © 2012 Alcatel-Lucent. encapsulation/extraction of ATM streams into/from ATM PW packets is performed according to RFC 4717.

in which E1/T1s are terminated before entering into aggregation network.Notes: • Definition: This service identifies a flow inside MPR network. switched and terminated. Copyright © 2012 Alcatel-Lucent. in which E1/T1 is transported. Edition 2 Section 1 · Module 2 · Page 25 . All Rights Reserved. • Application: Typical microwave 2G backhauling application.

• Application: Typical microwave 2G backhauling application. in which E1/T1s are terminated before entering into aggregation network. E1/T1s are not terminated at the end of the microwave backhauling and an end-to-end circuit emulation services could be established between 9500 MPR and the service router in front of BSC/RNC Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 26 . where aggregation network is a packet network. E1/T1s are transported.Notes: • Definition: E1/T1 TDM input signals are packetized according to MEF8 standard. All Rights Reserved. switched and provided to an external ETH network in standard format (MEF-8).

Notes: • • Definition: This service identifies a flow inside MPR network. in which STM-1 is transparently transported. Application: Typical microwave transport application. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 27 . switched and terminated. All Rights Reserved.

All Rights Reserved. Copyright © 2012 Alcatel-Lucent. in which transport of Ethernet packets coming from base stations is requested.Notes: • • Definition: Ethernet traffic is transported and switched automatically by the standard autolearning algorithm of the built-in MPR 10 Gbit Ethernet switch. Application: Typical microwave 3G backhauling/WiMax application. Edition 2 Section 1 · Module 2 · Page 28 .

Edition 2 Section 1 · Module 2 · Page 29 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 1 · Module 2 · Page 30 .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 Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

The Cross connections are PDH-Radio type. 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 Cross connections are SDH-Radio type. The Circuit Emulation Service is SDH2SDH in Node 1 and Node 2. Case 2 (TDM2Eth) • The E1/T1 stream is inserted in Node 1 and extracted in Node 2. The Circuit Emulation Service is TDM2ETH in Node 1 and Node 2. All Rights Reserved. but the second IWF is external to the 9500 MPR network. One IWF is inside the 9500 MPR. One IWF is inside the 9500 MPR. Case 1 for STM-1 (SDH2SDH) • The STM-1 stream is inserted in Node 1 and extracted in Node 2. the second IWF is external to the 9500 MPR-E network. The Circuit Emulation Service is TDM2ETH in Node 1 and Node 2. The Cross connections are PDH-Radio type in Node 1 and Radio-Eth type in Node 2. Copyright © 2012 Alcatel-Lucent. 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.Notes: Case 1 for E1/T1 (TDM2TDM over MPR network) • The E1/T1 stream is inserted in Node 1 and extracted in Node 2. Case 3 (TDM2Eth) • The E1/T1 stream is inserted/extracted in Node 1. The Cross connections to be implemented are PDH-Eth type in Node 1. The Circuit Emulation Service is TDM2TDM in Node 1 and Node 2. Edition 2 Section 1 · Module 2 · Page 31 .

The Circuit Emulation Service is ETH2ETH in Node 1 and Node 2.Notes: Cases 4 and 5 (ETH2ETH) • In these cases Ethernet packets enter Node 1 and are extracted in Node 2. Copyright © 2012 Alcatel-Lucent. in case 5 the packets are native Ethernet packets. In case 4 the Ethernet packets encapsulate the E1 stream. The path is automatically implemented with the standard auto-learning algorithm of the 9500 MPR Ethernet switch. All Rights Reserved. None of the IWFs belongs to the 9500 MPR network. No Cross connections must be implemented. Edition 2 Section 1 · Module 2 · Page 32 .

Edition 2 Section 1 · Module 2 · Page 33 . The Cross connections are PDH-Eth type.Notes: Case 6 for E1/T1 (TDM2TDM over Ethernet) • The E1/T1 stream is inserted in Node 1 and extracted in Node 2. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. In this case the two IWFs used to packetize the traffic for the Ethernet switch in the Core-E module are both internal to the 9500 MPR network. The Circuit Emulation Service is TDM2TDM in Node 1 and Node 2.

Edition 2 Section 1 · Module 2 · Page 34 .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 Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 1 · Module 2 · Page 35 .Notes: • • ECID = Emulated Circuit Identifier IWF = Inter-Working Function Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 1 · Module 2 · Page 36 . All Rights Reserved.Notes: • • • • • Flow Id present (user defined) all the parameters must be configured compliant with the MEF8 standard adaptive or differential clock recovery supported bandwidth guaranteed (according to QoS Æ Highest Queue Priority association) destination MAC added before going into whole network (MEF8 compliant) Copyright © 2012 Alcatel-Lucent.

Notes: • ECID = Emulated Circuit Identifier Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 37 . All Rights Reserved.

All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 38 . 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. Copyright © 2012 Alcatel-Lucent.Notes: • • • • • Flow Id present (user defined) If there are intermediate nodes in each node build the Cross-connection tables based on Flow Id.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 39 .

Edition 2 Section 1 · Module 2 · Page 40 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 41 .Copyright © 2012 Alcatel-Lucent.

• In figure is shown a more detailed block diagram of the ASAP unit in Ingress. Edition 2 Section 1 · Module 2 · Page 42 . Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 43 .Notes: • Any packet belonging to an Eth2Eth TDM flow is treated as any other Ethernet packet with the only exception of giving it an higher priority based on the MEF 8 Ethertype.

Edition 2 Section 1 · Module 2 · Page 44 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 45 .

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

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 47 .

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 Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 48 . All Rights Reserved. Both those QoS functions are properly configured in order to get the wished behavior on Ethernet flows that will be transmitted towards the Radio.Notes: • • 9500MPR uses a Connection Admission Control (CAC) for committed services and two schedulers in series (on Core embedded L2 switch and on Radio peripheral) The two schedulers need to jointly interoperate to guarantee determistic behavior of the services • • The QoS function inside 9500 MPR-E is the result of a distributed implementation in the switch in the Core-E unit and Radio Interface unit.

Edition 2 Section 1 · Module 2 · Page 49 . • • • • 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. The QoS feature provides eight internal queues to support different traffic priorities. All Rights Reserved.1p field or DiffServ field.Notes: • • In the figure is shown an overview of the QoS implementation inside the Core-E unit and Modem unit which is used to interface the ODU300. Copyright © 2012 Alcatel-Lucent. The QoS function can assign the packet to one of the eight egress transmit queues.

Edition 2 Section 1 · Module 2 · Page 50 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 51 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 52 .

When a radio port is removed from a L1 LAG port. The queue sizes are set to the default values. All Rights Reserved. When a radio port is added to the L1 LAG port. Edition 2 Section 1 · Module 2 · Page 53 . The previous configuration of queue sizes of the Radio QoS of Spare interface is lost. the NE QoS settings are applied to the radio port. the Radio QoS of Main interface maintains the previous configuration of queue sizes.Notes: • • • • In case the configuration of radio interfaces changes from 1+0 to 1+1. Copyright © 2012 Alcatel-Lucent. the Radio QoS of Spare interface takes the queue sizes of the Radio QoS of Main interface. all custom QoS and queue size configuration is lost. while the Spare interface takes the default queue sizes according to the configured Modem Profile. In case of the configuration of radio interfaces changes from 1+1 to 1+0.

Notes: • In order to give an estimation of the maximum delay. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 54 . the WebEML shows a read-only value. which is the queue size configured by the operator converted in a time value (msec). that an Ethernet frame can experience when entering the specific queue in case of congestion of radio interface. All Rights Reserved.

All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 55 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 56 .

Edition 2 Section 1 · Module 2 · Page 57 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 1 · Module 2 · Page 58 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 59 . All Rights Reserved.

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 60 . All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 61 .

All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 62 .Copyright © 2012 Alcatel-Lucent.

being this the value for 256QAM@56 MHz) Protection. The discarded or dropped traffic is the one with lower priority: high priority traffic is still running on the remaining active channels. The overall radio Ethernet throughput is more than 1 Gbit/sec (4 x 350 Mbit/s. Edition 2 Section 1 · Module 2 · Page 63 . Copyright © 2012 Alcatel-Lucent. All Rights Reserved. all the traffic is redirected on the remaining link (with a throughput of around 0.Notes: • In this example. Main advantages: • • Throughput.35 Gbit/sec). user traffic is split up into radio channels. In case of a failure of one of the three channels.

. the Distributor performs a packet-based traffic distribution over multiple links regardless of the content of the packets. Copyright © 2012 Alcatel-Lucent. this kind of Link Aggregation is called Layer1 (i. associated to the physical layer). All Rights Reserved. The Distributor takes into account the number of bytes sent over a specific link and loads links according to the available bandwidth. Since the distribution does not depend on Layer2 or Layer3 header content.e. As a consequence. Layer1 Link Aggregation allows a traffic load balancing independently of traffic content.Notes: • • In Layer1 Link Aggregation. Edition 2 Section 1 · Module 2 · Page 64 .

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 Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 65 .

Edition 2 Section 1 · Module 2 · Page 66 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Notes: Radio L2 LAG ports configured in Active/Standby mode are NOT recommended in this release of the 9500 MPR. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 67 . All Rights Reserved.

Notes: One MPT per MPT plug-in. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 68 . Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent.Notes: The Ethernet ports involved in a LAG cannot be used as TMN In-band interface. Edition 2 Section 1 · Module 2 · Page 69 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 70 .

1000 Mbps) Duplex Mode VLAN 802. 100.1Q port priority VLAN 802. All Rights Reserved.1Q port filter mode Auto Negotiation Enabled/Disabled Disable the port Synchronous Ethernet Operation Mode SynchE Master/Slave (electrical only) SSM support Copyright © 2012 Alcatel-Lucent. the following user Ethernet port parameters may not be modified: • • • • • • • • • Link Capacity (10.Notes: After a user Ethernet port has been added to an Ethernet L2 LAG port. Edition 2 Section 1 · Module 2 · Page 71 .

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 72 .

Edition 2 Section 1 · Module 2 · Page 73 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 74 .Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 75 .Notes: With MSS-1c and with MPR-e the SSM are transparency forwarded in most of the configurations.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 76 .

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

All Rights Reserved. Synchronization (frequency) is delivered to the cell site using any of the options available on MPR. E1/T1 at the egress) via a simple configuration. Worth repeating ingress and egress methods can be mixed (i.Notes: • • The availability of the Clock in the Network represents the most common scenario. Copyright © 2012 Alcatel-Lucent.e. Synch -Eth at the ingress. characterized by a time source available at the ingress of the microwave backhauling network. derived from the primary reference clock. depending on the operator’s need. Edition 2 Section 1 · Module 2 · Page 78 .

Notes: • • 9500 MPR has an embedded reference clock which is distributed to each board of the network element. Edition 2 Section 1 · Module 2 · Page 79 . Copyright © 2012 Alcatel-Lucent. Such clock is generated in the Clock Reference Unit (CRU) of the core unit (controller). All Rights Reserved.

“network-synchronous operation for service clock”) introduces an additional possibility to recover E1 clock. but performances depends on the PDV (Packet Delay Variation) in the Network.Notes: • • • Differential: used in case of clock distribution on the whole network. 823 synchronization masks. In node-timing working mode. This means that. 8261 wording. Copyright © 2012 Alcatel-Lucent. Always used when the reference clock isn’t distributed on the whole network. also used in TDM2TDM traffic (MPR to MPR). Node Timing: this feature (called either “network clock re-timing” or “node timing” or. Edition 2 Section 1 · Module 2 · Page 80 . It’s more reliable than Adaptive. all the E1s are re-sampled with the network element clock. as also reported in G8261. Recovered E1 clock is according to G. Adaptive: simpler network. this method does not preserve the service timing (E1 clock). • • • Node timing is a way to recover TDM clock quite popular in the industry of service routers and site aggregator boxes. This feature inside the 9500 MPR platform is adding interworking capabilities with third parties service routers and circuit emulations gateway. according to G. All Rights Reserved.

If the NODE TIMING is enabled. the CT still propose the possible selection between ACR and DCR: in this specific case. Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 81 . the meaning of this option is not related to the clock recovery algorithms but rather to the MRF8 frame format.Notes: • • In meshed networks (rings) do not close the synchronization configuration.

at RX side. at RX side. Edition 2 Section 1 · Module 2 · Page 82 . generate output clock based on data arrival rate: TDM clock is slowly adjusted to maintain the average fill level of a jitter buffer at its midpoint.Notes: • Differential clock recovery • • • Common reference clock IS available at both Ends. IWF system. IWF system. All Rights Reserved. Adaptative clock recovery • • Common reference clock is NOT available at both Ends. Copyright © 2012 Alcatel-Lucent. generate output clock based on RTP TimeStamps which are sent together with each Fragments.

All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 83 .Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 1 · Module 2 · Page 84 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 85 . All Rights Reserved.

causes the switching of the Synchronization Source. the CRU detects the signal Degrade Alarm on each available sync source.Notes: • • • Each Module will mute its own Synchronization clock in case of Fail Alarm. For each available sync source. Such Signal Degrade alarm raises also in case of muted (missing) clock. or the relevant Card Fail. Copyright © 2012 Alcatel-Lucent. The Signal Degrade Alarm relevant to the selected Synchronization Source. Edition 2 Section 1 · Module 2 · Page 86 . All Rights Reserved.

Edition 2 Section 1 · Module 2 · Page 87 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 88 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 89 .Copyright © 2012 Alcatel-Lucent.

port #) must be associated to a signal flow ID Copyright © 2012 Alcatel-Lucent. The decision made by the switch to forward the received packet is based on the destination MAC address. All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 90 .Notes: • • • The cross-connections between slots and between slot and Ethernet user ports are realized with a Layer-2 Ethernet Switch inside the Main Core-E. 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 #.

All Rights Reserved. Edition 2 Section 1 · Module 2 · Page 91 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 1 · Module 2 · Page 92 .

All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 1 .Copyright © 2012 Alcatel-Lucent.

This page is left blank intentionally Document History Edition 3. All Rights Reserved.4 4.0 Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 2 .0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition Updated for Release 4.

Edition 2 Section 2 · Module 1 · Page 3 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 4 .

1 +24/-48 Volt Power Converter 13 Power Extractor 13.1 P32E1DS1 (DS1/PDH) Card 5.2 CSM-E/Core-E Card Block Diagram 3.1 Fan Card 11.2 Power Injector Plug-in 14.2 AUX Card Block Diagram 8.3 LEDs 15 MPT power unit Copyright © 2012 Alcatel-Lucent.2 MSS-8 Cards 2 Microwave Service Switch (MSS-4) 2.4 MOD300 Card LEDs 8 AUX Card 8.2 MOD300 Card Block Diagram 7.2 P8ETH/EAS Card Block Diagram 4.4 CSM-E/Core-E Card LEDs 4 Ethernet Access Switch/P8ETH 4.3 P32E1DS1 (DS1/PDH) Card Status LED 6 MPTACC Card 6.4 ASAP Card LEDs 11 Fan Card 11.3 MOD300 Card Status LED 7.2 P32E1DS1 (DS1/PDH) Card Block Diagram 5.1 CSM-E/Core-E Card 3.1 MSS-8 Overview 1.3 AUX Card Status LED 8.4 EAS/P8ETH Card LEDs 5 P32E1DS1 (DS1/PDH) Card 5.2 Fan 2U Card with Alarms LEDs 12 +24/-48 Volt Power Converter 12. All Rights Reserved.1 MSS-4 Overview 2.3 ASAP Card Status LED 10.4 MPTACC Card LEDs 7 MOD300 Card 7.4 AUX Card LEDs 9 2xSTM-1 Local Access Card 9.1 2xSTM-1 Local Access Card 9.3 MPTACC Card Status LED 6.1 AUX Card 8.2 MPTACC Card Block Diagram 6.1 Power Injector 14.1 P8ETH/EAS Card 4.2 MSS-4 Cards 3 Control and Switching Module/Core-E 3.Page 1 Microwave Service Switch (MSS-8) 1.3 P8ETH/EAS Card Status LED 4.2 2xSTM-1 Local Access Card Block Diagram 10 ASAP Card 10.2 ASAP Card Block Diagram 10.1 MOD300 Card 7.1 MPTACC Card 6.1 ASAP Card 10. Edition 2 Section 2 · Module 1 · Page 5 7 8 9 11 12 13 15 16 21 22 23 25 26 27 28 29 31 32 33 34 35 36 37 38 39 41 42 43 44 45 47 48 49 50 51 53 54 55 57 58 59 60 61 63 64 65 67 68 69 70 71 72 73 74 75 .1 Power Extractor 14 Power Injector 14.3 CSM-E/Core-E Card Status LED 3.

Page 15.2 32E1 SCSI 75 Ohm Patch Panel 18.3 MSS-1c Status LED 17.3 LEDs 17 Microwave Service Switch (MSS-1c) 17. All Rights Reserved.2 MPT extended power unit block diagram 16.1 E1/T1 RJ-45 120 Ohm Patch Panel 18.3 LEDs 16 MPT extended power unit 16.1 MSS-1c 17.2 MPT power unit block diagram 15.1 MPT power unit 15. Edition 2 Section 2 · Module 1 · Page 6 .4 MSS-1c 18 Distributors/Patch Panels 18.3 E1/T1 Tributaries (Protected Pair) 18.4 E1/T1 D-Connector Patch Panel 76 78 79 81 82 84 85 87 88 89 90 91 93 94 95 96 97 Copyright © 2012 Alcatel-Lucent.2 MSS-1c Block Diagram 17.1 MPT extended power unit 16.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 7 . All Rights Reserved.

Edition 2 Section 2 · Module 1 · Page 8 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 9 .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 to PDU).

Edition 2 Section 2 · Module 1 · Page 10 .This page intentionally left blank Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 11 .

All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 12 .Copyright © 2012 Alcatel-Lucent.

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 Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 13 . All Rights Reserved.

Edition 2 Section 2 · Module 1 · Page 14 . All Rights Reserved.This page intentionally left blank Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 2 · Module 1 · Page 15 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

• For any “packetized” flow. VLAN management and MAC based • Ethernet MAC learning • Cross-connect function for PDH and Data payload traffic.Notes: • • Gigabit Ethernet serial internal interfaces between CSM-E/Core-E and peripherals CSM-E/Core-E Macro Functions: • • Controller Layer 2+ Ethernet Switch. • • Selection of the synchronization clock to be distributed to each plug-in. Copyright © 2012 Alcatel-Lucent. The flash card stores the license. equipment MIB. the switch will be in charge to also manage the Equipment Protection Switching (EPS). All Rights Reserved. and equipment MAC address. equipment software. Edition 2 Section 2 · Module 1 · Page 16 . • Quality of Service (QoS) management.

Edition 2 Section 2 · Module 1 · Page 17 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

withdraw it and then installed it again. All Rights Reserved.Notes: The SFP must be installed after the Configuration File has been downloaded. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 18 . If the SFP has been installed before.

All Rights Reserved.Notes: For the correct operation of the EoSDH SFP it is necessary to disable the autonegotiation via WebEML or via the Configuration File. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 19 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 20 . All Rights Reserved.

port #6). Copyright © 2012 Alcatel-Lucent. MPT-HCV2. • to be used to connect an MPT: MPT-HC (ETSI). These ports can be also used to connect directly an MPT-HC/MPT-HCV2.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 optional SFP must be installed). Edition 2 Section 2 · Module 1 · Page 21 . All Rights Reserved. port#4. an MPT-HC only to port#5 and port#6. or MPT-MC (ETSI) to port#1 to • The Core-E unit has the option to equip two SFPs (in port #5.

DiffServ priorities are based on one of eight tags. All Rights Reserved. first in.1D-2004 Annex G User Priorities and Traffic Classes that defines seven traffic types and corresponding user priority values. each identifying one of eight traffic types and corresponding user priority values.Notes: • • • The CSM-E/Core-E consists of microprocessor and Ethernet switch circuits. Edition 2 Section 2 · Module 1 · Page 22 . Copyright © 2012 Alcatel-Lucent. all traffic inside the switch has the same priority. This means that for each switch port there is only one queue. If QoS is disabled. The Ethernet Switch provides a Quality of Service (QOS) mechanism to control all streams.1 priorities are set based on IEEE 802. first out (FIFO) Three QoS settings in GUI are available as follows: • • • Disabled 802.

Where a Status LED on a plug-in is off (unlit). or flash card realignment in progress In Service. Normal Operation. properly provisioned as EPS Card fail Card mismatch NE Major Alarm (M) NE Minor Alarm (m) NE Warning Alarm (W) NE Abnormal Condition (A) Status (S) • • • • Always check to see if symptoms match the alarm. 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. which can help narrow down the location and type of failure. Edition 2 Section 2 · Module 1 · Page 23 . Copyright © 2012 Alcatel-Lucent. All Rights Reserved. software Booting. check the seating of the affected plug-in.Notes: Check front-panel LED indications INDICATOR Link (L) Green Activity (A) STATUS Off Link Up Off Blinking Yellow Red Red Yellow Yellow Off Green Blinking Green Yellow Red Blinking Red DEFINITION Link Down No Tx/Rx activity Tx/Rx activity At least one alarm is present on the NE with major severity is present on the NE At least one alarm is present on the NE with minor severity is present on the NE At least one alarm is present on the NE with warning severity is present on the NE At least one abnormal condition is present on the NE Card not equipped. or not powered Download. not provisioned. but power to the MSS-8 is confirmed by LEDs on other plug-ins. LEDs provide summary alarm indications. and Properly Provisioned In protect.

All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 24 .This page intentionally left blank Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 25 .Copyright © 2012 Alcatel-Lucent.

• • • The main P8ETH/EAS is equipped in slots 3. 6. or 7 The protect (spare) P8ETH/EAS is equipped in slots 4. The protect (spare) P8ETH/EAS is equipped in slot 4 directly across from the main. MSS-4 shelf: • • • Supports one protected pair of P8ETH/EAS cards or two unprotected P8ETH/EAS cards. In protected radio configurations. • • • • The main P8ETH/EAS is equipped in slot 3. P8ETH/EAS is supported in slots 3-8 for unprotected radio configurations. In protected radio configurations. P8ETH/EAS is supported in slots 3 and 4 for unprotected radio configurations. The protect card protects the radio if the main fails. or 8 directly across from the main. All Rights Reserved. 5. a pair of P8ETH/EASs are required. MPT-HL – ANSI market Copyright © 2012 Alcatel-Lucent. The protect card protects the radio if the main fails. a pair of P8ETH/EASs are required. Edition 2 Section 2 · Module 1 · Page 26 .Notes: MSS-8 shelf: • • • Supports three protected pairs of P8ETH/EAS cards or six unprotected P8ETH/EAS cards.

Notes: • • • If more than six local Ethernet accesses are required (built into the Core-E). All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 27 . the EAS (P8ETH) offers an additional four 10/100/1000 Ethernet interfaces plus 4 1 GbEth optical An embedded 10 Gbit/sec L2 switch is present on the unit. Copyright © 2012 Alcatel-Lucent. There are four Electrical 10/100/1000 base-T electrical ports and 4 optical SFP (LX and SX).

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 28 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 29 .

This page intentionally left blank Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 30 . All Rights Reserved.

Edition 2 Section 2 · Module 1 · Page 31 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

a maximum of five DS1 connections can be assigned. Additional DS1 connections may be added to separate links that do not contain DS3 connections. Edition 2 Section 2 · Module 1 · Page 32 . All Rights Reserved.Notes: • SAToP: Structure-Agnostic TDM over Packet • In a radio link containing a DS3 connection. Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Notes: • • • In the TX direction. the P32E1DS1 card extracts data from the Ethernet data packets and processes the data to provide up to 32 output lines. the P32E1DS1 card processes and encapsulates up to 32 input lines into 2 Ethernet packets. In the RX direction. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 33 . 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-directional interfaces on the backplane.

Copyright © 2012 Alcatel-Lucent. Two are required. Edition 2 Section 2 · Module 1 · Page 34 . 5.Notes: • There are equipping options for the P32E1DS1. or 7 and the protect (spare) module in the slot directly across from the main (slot 6 or 8). All Rights Reserved. The protect (spare) P32E1DS1 module protects the E1/T1 stream if the main P32E1DS1 card fails. the main module in slot 3. • • Can be equipped in slots 3-8.

Edition 2 Section 2 · Module 1 · Page 35 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

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 Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 36 . All Rights Reserved.

If has been enabled port #1 (optical or electrical). If the optical port has to be used. the associated Power Supply port is #1. an SFP plug-in must be installed. The connection to the MPT-MC is realized by using only one electrical Ethernet cable with the enabling of the PFoE (Power Feed over Ethernet) function (Ethernet traffic + Power Supply on the same cable). Copyright © 2012 Alcatel-Lucent. The connection to the MPT-HC can be realized: • by using two connectors: • • • • • • • one DC power Supply connector to send the power supply to the MPT-HC one Gigabit Ethernet connector (electrical or optical) to send the Ethernet traffic and the Ethernet control frames to the MPT-HC or by using only one electrical Ethernet cable with the enabling of the PFoE (Power Feed over Ethernet) function (Ethernet traffic + Power Supply on the same cable). All Rights Reserved. Two MPT-HC or MPT-MC can be connected to one MPT Access unit. the associated Power Supply port is #2. If has been enabled port #2 (optical or electrical). Edition 2 Section 2 · Module 1 · Page 37 .Notes: • • • • The MPT Access Unit is the interface for two MPT: MPT-HC or MPT-MC. The two MPT can be configured in unprotected or protected configuration.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 38 .

Edition 2 Section 2 · Module 1 · Page 39 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 40 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 41 .

Edition 2 Section 2 · Module 1 · Page 42 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

the MODEM Module generates the IF signal to be sent to an MXC Out Door Unit.Notes: • In Tx direction. All Rights Reserved. • RX Analog Chain • 126 MHz IF RX demodulation to I & Q • low pass filtering & ADC •Digital Demodulator • Carrier & CK recovery • Equalization • Error Correction •Digital Deframer • RPS (hitless) • Defragmentation Copyright © 2012 Alcatel-Lucent. the MODEM 300 Module terminates the IF signal coming from the ODU300 extracting the original CBR and then the original Ethernet packets to be given the Core-E which distributes them to the proper Module. Edition 2 Section 2 · Module 1 · Page 43 • . Digital Framer • Classification of incoming packets from the Core-E (QoS) • Fragmentation • Air Frame Generation (synchronous with NE clock) • Digital Modulator • TX Analog Chain • DAC & low pass filtering • Modulation to 311 MHz IF TX • In Rx direction.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 44 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 45 .

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 46 .

All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 47 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. By CT/NMS the polarity can be changed independently for each alarm (both normally closed and normally open contacts are available on the I/O connector). Output alarms By default the presence of active alarm corresponds to closed relay contact with a common wire available to the customer. When the power supply is down (and also when the power supply is on but the SW has not yet initialized the HW).11 DCE co-directional Radio Service Channels On each radio direction three 64 kbit/s out-of-band channels are dedicated to Service Channel transmission. Copyright © 2012 Alcatel-Lucent. the user can enable/disable the 64 kbit/s Service Channel interfaces. all the relays of the outputs of the alarms/housekeeping are in the "open" state (HW default condition). The default is disabled: • When enabled. if the voltage on the input is high (open contact) or if the voltage is low (closed contact). Alarm-Housekeeping 13 Alarm-Housekeeping pins are provided: • 6 pins are configured as inputs • 7 pins are configured as outputs. It is possible to assign one user label for each output. The state of each alarm input is configurable in order to be active. Input alarms The polarity of each input Alarm-Housekeeping is configurable. The Output Housekeeping can be managed in Manual mode only: in Manual mode the output state of each housekeeping is controlled by the operator. Edition 2 Section 2 · Module 1 · Page 48 .Notes: Service Channels Using the CT/NMS. Service Channel interfaces 1 and 2can be configured to transport the following protocol: • Synchronous 64 Kb/s RS422/V. This second option is the default value. It is possible to assign one user label for each input.

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) Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 49 .Notes: • • Service Channels access and Housekeeping alarms are available with the optional Auxiliary peripheral unit.

Notes: EOW . All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 50 .Engineering Express Order Wire Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 2 · Module 1 · Page 51 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

This page intentionally left blank Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 52 .

Edition 2 Section 2 · Module 1 · Page 53 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

In the event the clock source is lost. addressing two different network scenarios: • STM-1 channelized. It multiplexes NxE1 into an STM-1 electrical/optical line connection. The clock source can be “Loop time” or “Node time”.Notes: •The STM-1 unit can be used in two different working modes. Edition 2 Section 2 · Module 1 · Page 54 . Clock source from the incoming STM-1 signal can be selected as Network Element source clock. 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). STM-1 card manages one 155 Mbit/s STM1 interface and up to 63xE1. it terminates or originates the SDH frame. In the Rx direction. Typical application is a direct connection to SDH add-drop multiplexers (ADMs). In the Tx direction. provision card as SDHAC • The STM-1 channelized interface works as a terminal multiplexer. provision card as SDHCHAN • STM-1 transparent. clocking falls back to the internal clock or to other of any synch in options. the STM-1 Local Access unit processes and encapsulates up to 2xSTM-1 input lines into an Ethernet packet that is sent to the Core-E card(s). two STM-1 units must be installed. that means that a VC4 directly maps up to 63xVC12 into an STM-1 signal (in turn each VC12 contains 1xE1). Standard VC4 mapping of lower-order E1 traffic streams to/from STM-1 is applied. • • • • • Copyright © 2012 Alcatel-Lucent. All Rights Reserved. the STM-1 Local Access unit extracts data from the Ethernet data packets and processes the data to provide up to 2 STM-1 output lines.

Edition 2 Section 2 · Module 1 · Page 55 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 56 . All Rights Reserved.

Edition 2 Section 2 · Module 1 · Page 57 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

It is possible to manage only VP switching (=only VPI change) All the VC inside the VP must have same QoS (= for ex. • VCC mode • • • • • • • • It is possible to transport max 48 VC for every IMA group. PWE3) with N-1 encapsulation format. Policing and shaping at ATM level has performed VC mode only The VC of the same class level (CBR / UBR+ / UBR) are managed in the same radio tail than are available 3 different radio tails VPC mode It is possible to transport max 48 VP for every IMA group. The sum of VP + VC configured on a single ASAP card must be <128. Copyright © 2012 Alcatel-Lucent. It is possible to manage VC switching (= VCI and VPI change) It is possible to assign at every VC one specific QoS. The ASAP cards are unprotected (No 1+1 EPS is available). ATM PW Ethernet traffic is managed by MPR is such a way to emulate the native QoS that would be applied by ATM equipment. all CBR or all UBR) The radio QoS (= radio tails) and QoS ATM (=policing and shaping) are managed at VP level. Edition 2 Section 2 · Module 1 · Page 58 . 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 PseudoWire EdgetoEdgeeEmulation.Notes: • • • • • The ASAP card is used to transport 16xE1 ATM traffic. with E1/IMA physical layer. All Rights Reserved.

loss of signaling multi-frame and loss of CRC multi-frame. • • Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 59 . ML-PPP can be supported by the SW application controlling the Data Path and running on a different MIPS processor embedded on the same chip. •The 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. The main function implemented in the confederation FPGA is the clock management. CESoP. ATM-IMA over PseudoWire. All Rights Reserved. • The Network Processor is the heart of the ASAP card and provides the implementation of the protocols to be supported as well as data forwarding. • Line code supported: HDB3. SAToP (like on the PDH card). • Pulse shape: digitally programmable • Framing to G. loss of frame. 120 ohm. • Detection of alarm conditions as loss of signal.704 E1 signals and to CRC-4 multi-frame alignment signals. The right-hand side is the backplane with the 1 Gb bus shared among the other slots and hence common with the other units (PDH units and Modem units).Notes: •The 16xE1 ATM streams enter the ASAP unit on the front panel.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 60 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 61 .

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 62 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 63 . All Rights Reserved.

Edition 2 Section 2 · Module 1 · Page 64 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 65 . All Rights Reserved.

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 66 . All Rights Reserved.

All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 67 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 68 .Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 69 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 70 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 71 . All Rights Reserved.

The bracket can support two boxes side by side. Height: 1.Notes: Power Injector box: stand-alone box. All Rights Reserved. powered through two connectors on the front providing power supply redundancy.3 U. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 72 . • • • The box can be mounted in a rack by means of a separate bracket.

Notes: • • • Two DC connectors in the front (for box version). or power from the back panel (for plug-in version). Edition 2 Section 2 · Module 1 · Page 73 . All Rights Reserved. Two RJ45 for the data in (DATA) Two RJ45 for the data + DC out (DC+DATA) Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 74 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 75 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 76 . All Rights Reserved.

Edition 2 Section 2 · Module 1 · Page 77 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 78 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 79 . All Rights Reserved.

Edition 2 Section 2 · Module 1 · Page 80 .This page intentionally left blank Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 81 .

Edition 2 Section 2 · Module 1 · Page 82 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 2 · Module 1 · Page 83 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 2 · Module 1 · Page 84 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 85 .

Edition 2 Section 2 · Module 1 · Page 86 .This page intentionally left blank Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 87 .

Edition 2 Section 2 · Module 1 · Page 88 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 2 · Module 1 · Page 89 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 90 . All Rights Reserved.

Notes: Check front-panel LED indications INDICATOR Link (L) STATUS Off Green Off Blinking Yellow Red Red Yellow Yellow DEFINITION Link Down Link Up No Tx/Rx activity Tx/Rx activity At least one alarm is present on the NE with major severity At least one alarm is present on the NE with minor severity (not supported) At least one alarm is present on the NE with warning severity (not supported) At least one abnormal condition is present on the NE . as explained above. Warning and Abnormal) • lights on the MPT LED as yellow. Minor. red.Tx Power muted by operator . or yellow.ACM frozen by operator . Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 91 .MPT loopback active MPT1 Off Green Yellow Red MPT MPT MPT MPT is is is is not emitting power according with the known configuration emitting power as expected according the known configuration not emitting power due to a forced Squelch condition ABNORMALLY emitting power Activity (A) Major Alarm (M) Minor Alarm (m) Warning Alarm (W) Abnormal Condition (A) MPT2 (not supported) At start-up the MSS-1c: • lights on all the alarm LEDs (Major. then this LED will be green. All Rights Reserved.

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 92 .

All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 93 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 1 · Page 94 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 95 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 96

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 97

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 98

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 99

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 100

This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 101

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 1 · Page 102

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 1

This page is left blank intentionally

Document History Edition 3.4 4.0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition Updated for Release 4.0

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 2

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 3

This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 4

Page 1 Outdoor Unit 1.1 ODU300 Construction and Mounting 1.2 ODU300 Characteristics 2 ODU300 Block Diagram 2.1 ODU300 Block Diagram 3 Outdoor Installations 3.1 ODU300 and Antenna 3.2 ODU300 Mounting Options 3.3 Installing the ODU 3.4 Direct-Mounted ODUs 3.5 Remote-Mounted ODUs (solution 1) 3.6 Remote-Mounted ODUs (solution 2) 3.7 Waveguide Flange Data 3.8 Grounding the ODU 3.9 ODU300 External Connectors 7 8 9 11 12 13 14 15 16 17 18 19 21 22 23

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 5

This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 6

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 7

Notes:

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

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

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

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

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

• Unequal is nominally 1/6 dB. • The ODU assembly meets the ASTME standard for a 2000 hour salt-spray test, and relevant IEC, UL, and
Bellcore standards for wind-driven rain.

• ODUs are frequency-band specific, but within each band are capacity-independent up to their design
maximums.
Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 8

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 9

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 10

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 11

Notes:

• The quadrature modulated 311 MHz IF signal from the MSS is extracted at the N-Plexer and passed via a cable AGC
circuit to an IQ demodulator/modulator. signal from the MSS.

• Here the 311 MHz IF is demodulated to derive the separate I and Q signals using the 10 MHz synchronizing reference • These I and Q signals modulate a Tx IF, which has been set to a specific frequency between 1700 and 2300 MHz, such
that when mixed with the Tx local oscillator signal (TXLO) in the subsequent mixer stage, it provides the selected transmit frequency. Both the IF and Tx local oscillators are synthesizer types.

• Between the IQ modulator and the mixer, a variable attenuator provides software adjustment of Tx power. • After the mixer, the transmit signal is amplified in the PA (Power Amplifier) and passed via the diplexer to the antenna
feed port.

• A microprocessor in the ODU supports configuration of the synthesizers, transmit power, and alarm and performance
monitoring. The ODU microprocessor is managed under the NCC microprocessor, with which it communicates via the telemetry channel.

• A DC-DC converter provides the required low-voltage DC rails from the -48 Vdc supply. • In the receive direction, the signal from the diplexer is passed via the LNA (Low Noise Amplifier) to the Rx mixer, where

it is mixed with the receive local oscillator (RXLO) input to provide an IF of between 1700 and 2300 MHz. It is then amplified in a gain-controlled stage to compensate for fluctuations in receive level, and in the IF mixer, is converted to a 126 MHz IF for transport via the ODU cable to the MSS. provided are based on ETSI plans for each frequency band. The actual frequency range per band and the allowable Tx/Rx splits are range-limited within 9500MPR-E to prevent incorrect user selection.

• The offset of the transmit frequencies at each end of the link is determined by the required Tx/Rx split. The split options

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

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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 12

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 13

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 14

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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 15

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 16

Edition 2 Section 2 · Module 2 · Page 17 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 19

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 20

Notes:

• • •

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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 21

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 22

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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 23

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 24

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 25

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 2 · Page 26

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 1

This page is left blank intentionally

Document History Edition 3.4 4.0 Date 2012-06-14 2012-09-14 Author AL University AL University Remarks First edition Updated for release 4.0

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 2

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 3

This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 4

Page 1 Outdoor Units 1.1 MPT-HC Construction and Mounting 1.2 MPT-HC Characteristics 2 MPT-HC Block Diagram 2.1 MPT-HC Block Diagram 3 Outdoor Installations 3.1 Installing the MPT-HC 3.2 6-7-8 GHz MPT-HC: integrated antenna (1+0) 3.3 11-38 GHz MPT-HC: integrated antenna (1+0) 3.4 6-7-8 GHz MPT-HC: integrated antenna (1+1) 3.5 11-38 GHz MPT-HC: integrated antenna (1+1) 3.6 6-7-8 GHz MPT-HC: non-integrated antenna (1+0) 3.7 11-38 GHz MPT-HC: non-integrated antenna (1+0) 3.8 6-7-8 GHz MPT-HC: non-integrated antenna (1+1) 3.9 11-38 GHz MPT-HC: non-integrated antenna (1+1) 3.10 MPT-HC External Connectors 3.11 DC Extractor 7 8 13 15 16 17 18 19 20 21 22 23 24 25 26 27 32

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 5

This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 6

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 7

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 8

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 9

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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 10

Notes:

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

• • • •

the BRANCHING assembly (containing the diplexer) the RF TRANSCEIVER assembly (containing the RF section)

Each of this type of MPT-HC is identified by two Logistical Items, one for the BRANCHING assembly and another for the RF TRANSCEIVER assembly. To read the BRANCHING assembly identification label it is necessary to separate the BRANCHING assembly from the RF TRANSCEIVER assembly.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 11

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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 12

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 13

This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 14

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 15

that can be either optical or electrical depending on the needs and the cable length.Notes: • The MPT-HC is broken down into the following sections: • Common Belt section. Copyright © 2012 Alcatel-Lucent. All Rights Reserved. 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. If the optical port has/have to be used (data and/or RPS port). the corresponding SFP plug-in must be installed by opening the Cobox. Edition 2 Section 2 · Module 3 · Page 16 . This section is Frequency independent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 3 · Page 17 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 3 · Page 18 .

Edition 2 Section 2 · Module 3 · Page 19 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 2 · Module 3 · Page 20 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 21 .Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 22 .

Edition 2 Section 2 · Module 3 · Page 23 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 2 · Module 3 · Page 24 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 3 · Page 25 .

Edition 2 Section 2 · Module 3 · Page 26 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

It must never be removed.Warning: A waterproofing tape is glued on the waveguide of the MPT-HC. cable Hole for Ethernet connection (in the co-box) waveguide male N 50 ohm Gland for Cat5e or optical cable (optional) Connector Hole for connection to a second MPT-HC in 1+1 (in the ODC co-box) (5) Co-box FREQUENCY GHz -> Waveguide type -> 11 WR75 13-15 WR62 18-25 WR42 38 WR28 Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 3 · Page 27 . Ref. in figure (1) (2) (3) (4) Interface RF interface for connection of antenna or coupler Connector for power supply coax. All Rights Reserved.

cable Hole for Ethernet connection (in the co-box) waveguide male N 50 ohm Gland for Cat5e or optical cable (optional) Connector Hole for connection to a second MPT-HC in 1+1 (in the ODC co-box) (5) Co-box FREQUENCY GHz -> Waveguide type -> 7 WR112 8 WR112 Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 3 · Page 28 .Warning: A waterproofing tape is glued on the waveguide of the MPT-HC. It must never be removed. Ref. in figure (1) (2) (3) (4) Interface RF interface for connection of antenna or coupler Connector for power supply coax. All Rights Reserved.

in figure (1) (2) (3) (4) Interface RF interface for connection of antenna or coupler Connector for power supply coax. Edition 2 Section 2 · Module 3 · Page 29 . All Rights Reserved. cable Hole for Ethernet connection (in the co-box) waveguide male N 50 ohm Gland for Cat5e or optical cable (optional) Connector Hole for connection to a second MPT-HC in 1+1 (in the ODC co-box) (5) Co-box FREQUENCY GHz -> Waveguide type -> 6 WR137 Copyright © 2012 Alcatel-Lucent. It must never be removed. Ref.Warning: A waterproofing tape is glued on the waveguide of the MPT-HC.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 3 · Page 30 .

Notes: • • Optional cable (P/N 3CC52191AA**). • Banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio Rx field. Copyright © 2012 Alcatel-Lucent. through a multi–meter it is possible to easily point the antenna until the measured voltage is the maximum. corresponding to the maximum radio Rx field. to connect the MCT directly to the MPT. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 31 . During equipment line–up. 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.

ƒ The DC Extractor then separates the Power Supply from the Ethernet traffic. which are separately sent to the MPT-HC. installed close to the MPT-HC. with the DC Extractor itself Copyright © 2012 Alcatel-Lucent.Notes: ƒ The DC Extractor. allows to interconnect the MSS and the MPT-HC with a single electrical Ethernet cable by using the “Power Feed over Ethernet” solution (Ethernet traffic and Power Supply on the same cable). are provided. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 32 . already terminated (2 m long). interconnecting the DC Extractor to the MPT-HC (the Power Supply cable to be connected to the DC Out connector of the DC Extractor and Ethernet cable to be connected to the Data Out connector of the DC Extractor). ƒ The two cables.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 3 · Page 33 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 3 · Page 34 .

All Rights Reserved.This page intentionally left blank Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 3 · Page 35 .

Edition 2 Section 2 · Module 3 · Page 36 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 2 · Module 4 · Page 1 .Copyright © 2012 Alcatel-Lucent.

0 Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 4 · Page 2 .0 Date 2012-06-14 2012-09-14 Author AL University AL University Remarks First edition Updated for release 4. All Rights Reserved.This page is left blank intentionally Document History Edition 3.4 4.

All Rights Reserved. Edition 2 Section 2 · Module 4 · Page 3 .Copyright © 2012 Alcatel-Lucent.

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 4 · Page 4 .

1 MPT-HCV2 Characteristics 1. All Rights Reserved.2 MPT-HCV2 External Connectors 7 8 10 11 13 14 15 17 18 19 Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 4 · Page 5 .1 MPT-HC V2/MPT-XP block diagram 2.Page 1 Outdoor Units 1.1 Installing the MPT-HC V2/MPT-XP 3.2 MPT-XP Characteristics 1.2 MPT-HC V2/MPT-XP RF section block diagram 3 Outdoor Installations 3.3 MPT-HC V2/MPT-XP XPIC 2 MPT-HC V2/MPT-XP/9558HC block diagram 2.

All Rights Reserved. Edition 2 Section 2 · Module 4 · Page 6 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 2 · Module 4 · Page 7 .Copyright © 2012 Alcatel-Lucent.

one for the BRANCHING assembly and another for the RF TRANSCEIVER assembly. where MPT-HC V2 is composed by two independent units: the BRANCHING assembly (containing the diplexer) and the RF TRANSCEIVER assembly (containing the RF section). where the branching (diplexer) is internal to the MPT-HC V2 cabinet. With external diplexer: due to a high number of shifters the diplexer is external for the flexibility of the shifter customization.Notes: Two mechanical solutions are adopted: • • With embedded diplexer for cost optimization. To read the BRANCHING assembly identification label it is necessary to separate the BRANCHING assembly from the RF TRANSCEIVER assembly. this type of unit is identified by one Logistical Item only. Copyright © 2012 Alcatel-Lucent. each of this type of MPT-HC V2 is identified by two Logistical Items. Edition 2 Section 2 · Module 4 · Page 8 . All Rights Reserved.

Edition 2 Section 2 · Module 4 · Page 9 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2 Section 2 · Module 4 · Page 10 .Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 2 · Module 4 · Page 11 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 4 · Page 12 . All Rights Reserved.

All Rights Reserved. Edition 2 Section 2 · Module 4 · Page 13 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Notes: • • The common belt section is frequency-independent. It is the digital section of the MPT-HC V2/MPTXP. Copyright © 2012 Alcatel-Lucent. Input voltage range is -28 to -58 Vdc. There are two architecture types for the RF section. there are two frequency conversions between RF input frequency and baseband frequency For all other bands. the differences between these two architectures are on the Rx side: • • • For 7/8 GHz. there are three frequency conversions The power comes from office power. Edition 2 Section 2 · Module 4 · Page 14 .

Edition 2 Section 2 · Module 4 · Page 15 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2 Section 2 · Module 4 · Page 16 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 4 · Page 17 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 4 · Page 18 .

Warning: A waterproofing tape is glued on the waveguide of the MPT-HCV2. FREQUENCY GHz -> Waveguide type -> 6 WR137 11 WR75 13-15 WR62 18-25 WR42 38 WR28 Copyright © 2012 Alcatel-Lucent. It must never be removed. Edition 2 Section 2 · Module 4 · Page 19 . All Rights Reserved. Remove the plastic cover.Note: RF interface for connection of antenna or coupler.

Remove the plastic cover. It must never be removed. All Rights Reserved. FREQUENCY GHz -> 7 8 WR112 Waveguide type -> WR112 Copyright © 2012 Alcatel-Lucent. Warning: A waterproofing tape is glued on the waveguide of the MPT-HC V2. Edition 2 Section 2 · Module 4 · Page 20 .Notes: RF interface for connection of antenna or coupler.

Edition 2 Section 2 · Module 4 · Page 21 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 2 · Module 4 · Page 22 .Notes: • • Optional cable (P/N 3CC52191AA**). • Banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio Rx field. • Note: LEMO is the cable manufacturer • (M2) RJ45 connector. During equipment line-up. Connector usage: • (M1) LEMO connector. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. corresponding to the maximum radio Rx field. to connect the MCT directly to the MPT. to be plugged into LEMO connector on MPT-HC V2/MPT-MC. through a multi–meter it is possible to easily point the antenna until the measured voltage is the maximum.

All Rights Reserved. Edition 2 Section 2 · Module 4 · Page 23 .Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 4 · Page 24 . All Rights Reserved.

This page intentionally left blank Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 4 · Page 25 . All Rights Reserved.

All Rights Reserved. Edition 2 Section 2 · Module 4 · Page 26 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 2 · Module 5 · Page 1 .Copyright © 2012 Alcatel-Lucent.

This page is left blank intentionally Document History Edition 3.4 4.0 Copyright © 2012 Alcatel-Lucent.0 Date 2012-06-14 2012-09-14 Author AL University AL University Remarks First edition Updated for Release 4. Edition 2 Section 2 · Module 5 · Page 2 . All Rights Reserved.

Edition 2 Section 2 · Module 5 · Page 3 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 2 · Module 5 · Page 4 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

2 7-8 GHz MPT-MC: integrated antenna (1+0) 3.7 7-8 GHz MPT-MC: non-integrated antenna (1+1) 3.5 6 and 11-38 GHz MPT-MC: integrated antenna (1+1) 3.4 7-8 GHz MPT-MC: integrated antenna (1+1) 3.2 MPT-MC Characteristics 2 MPT-MC Block Diagram 2.1 Installing the MPT-MC 3.6 MPT-MC: non-integrated antenna (1+0) 3.8 6 and 11-38 GHz MPT-MC: non-integrated antenna (1+1) 3. All Rights Reserved.Page 1 Outdoor Units 1.3 6 and 11-38 GHz MPT-MC: integrated antenna (1+0) 3.1 MPT-MC Block Diagram 3 Outdoor Installations 3.1 MPT-MC Construction and Mounting 1. Edition 2 Section 2 · Module 5 · Page 5 .9 MPT-MC External Connectors 7 8 10 13 14 15 16 17 18 19 20 21 22 23 24 Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 2 · Module 5 · Page 6 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 5 · Page 7 . All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 5 · Page 8 .

where MPT-MC is composed by two independent units: • • • • the BRANCHING assembly (containing the diplexer) and the RF TRANSCEIVER assembly (containing the RF section). With external diplexer: due to a vary high number of shifters the diplexer is external for the flexibility of the shifter customization (7 GHz and 8 GHz). To read the BRANCHING assembly identification label it is necessary to separate the BRANCHING assembly from the RF TRANSCEIVER assembly. where the branching (diplexer) is internal to the MPT-MC cabinet. Edition 2 Section 2 · Module 5 · Page 9 . this type of MPT-MC is identified by one Logistical Item only. All Rights Reserved. Copyright © 2012 Alcatel-Lucent.Notes: • • With embedded diplexer for cost optimization (6 GHz and from 11 GHz to 38 GHz). one for the BRANCHING assembly and another for the RF TRANSCEIVER assembly. Each of this type of MPT-MC is identified by two Logistical Items.

All Rights Reserved. 16. 64. 7. and 56 MHz • modulations: 4. 128. 8. 16. and 256 QAM • Adaptive radio profiles: • bandwidths: 3.5. 14. and 256 QAM Copyright © 2012 Alcatel-Lucent. 128. 28. 32. 14. 8. 40.Notes: • Static radio profiles: • bandwidths: 3. and 56 MHz • modulations: 4. 28. 40. 7. 64.5. Edition 2 Section 2 · Module 5 · Page 10 . 32.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 5 · Page 11 .

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 5 · Page 12 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 5 · Page 13 .

It has limited capacity vs. • The MPT-MC is similar to MPT-HC from architecture standpoint. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 5 · Page 14 .Notes: • The MPT-MC breaks down into the following sections: • Common Belt section. MPT-HC and is natively Ethernet powered (no Power extractor required). and all the features relevant to this unit are common to all the MPT RF options. • RF section that is frequency dependent. All Rights Reserved. This section is Frequency independent.

Edition 2 Section 2 · Module 5 · Page 15 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 5 · Page 16 .

All Rights Reserved. Edition 2 Section 2 · Module 5 · Page 17 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 5 · Page 18 .

Edition 2 Section 2 · Module 5 · Page 19 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 2 · Module 5 · Page 20 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 2 · Module 5 · Page 21 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2 Section 2 · Module 5 · Page 22 .Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 5 · Page 23 . All Rights Reserved.

where the branching (diplexer) is internal to the MPT-MC cabinet. this type of MPT-MC is identified by one Logistical Item only. Edition 2 Section 2 · Module 5 · Page 24 . All Rights Reserved. It must never be removed.Notes: • • WARNING: A waterproofing tape is glued on the waveguide of the MPT-MC. With embedded diplexer for cost optimization (6 GHz and from 11 GHz to 38 GHz). FREQUENCY GHz -> 6 11 WR75 13-15 WR62 18-25 WR42 38 WR28 Waveguide type -> WR137 Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. To read the BRANCHING assembly identification label it is necessary to separate the BRANCHING assembly from the RF TRANSCEIVER assembly. • • Each of this type of MPT-MC is identified by two Logistical Items. FREQUENCY GHz -> Waveguide type -> 7 WR112 8 WR112 Copyright © 2012 Alcatel-Lucent. With external diplexer: due to a vary high number of shifters the diplexer is external for the flexibility of the shifter customization (7 GHz and 8 GHz). one for the BRANCHING assembly and another for the RF TRANSCEIVER assembly.Notes: • • WARNING: A waterproofing tape is glued on the waveguide of the MPT-MC. where MPT-MC is composed by two independent units: • • the BRANCHING assembly (containing the diplexer) the RF TRANSCEIVER assembly (containing the RF section). Edition 2 Section 2 · Module 5 · Page 25 . It must never be removed.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 2 · Module 5 · Page 26 .

All Rights Reserved. Copyright © 2012 Alcatel-Lucent. Note: LEMO is the cable manufacturer (M2) RJ45 connector. Edition 2 Section 2 · Module 5 · Page 27 . corresponding to the maximum radio Rx field. • Banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio Rx field.Notes: • • Optional cable (P/N 3CC52191AA**). through a multi–meter it is possible to easily point the antenna until the measured voltage is the maximum. to connect the MCT directly to the MPT. to be plugged into LEMO connector on MPT-HC V2/MPT-MC. During equipment line-up. Connector usage: • • • (M1) LEMO connector.

Edition 2 Section 2 · Module 5 · Page 28 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 2 · Module 5 · Page 29 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 2 · Module 5 · Page 30 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 1 . All Rights Reserved.

0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition Updated for Release 4.0 Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 2 . All Rights Reserved.4 4.This page is left blank intentionally Document History Edition 3.

Edition 2 Section 3 · Module 1 · Page 3 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 1 · Page 4 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

2 Main Tool Bar Area 2.4 Restart MPT 5.2 NE Time Menu 3.3.4 Remote Inventory 4.15 Traffic Descriptors 3.3.3 IP Configuration .IP Static Routing Configuration 3.1 WebEML start 2 WebEML Main View 2.6 Summary Block Diagram View 4.16 Profiles Management 3.1 Description 9 Synchronization Tab Copyright © 2012 Alcatel-Lucent.1Q 3.1 SW Download Menu 7 Equipment Tab 7.4 Routing Information 3.3.11 XPIC Configuration Menu 3.4 Domain Alarm Synthesis Area 2.1 Supervision Menu 5.5 System Settings 3.5 MIB Management 5.4 Alarm Severities 3.2 Access State 5.Selection Criteria 3 Configuration Menu 3.8 LAG Configuration 3.6 Cross Connections 3.1 NTP Configuration 3.12 VLAN Configuration 3.5 Alarm & State Panels 2.3.Page 1 WebEML start 1.1D 3.3 Severity Alarm Panel 2.9 QoS Configuration 3.2 Alarms 4.802.10 AUX Cross Connections 3. All Rights Reserved.6 SW License 6 SW Download Menu 6.17 Ethernet Features Shell 4 Diagnosis Menu 4.7 Current Configuration View 5 Supervision Menu 5.7 Ring Configuration 3.3 Network Configuration Menu 3.802.5 Abnormal Condition List 4.1 Configuration Menu 3.1 Equipment Tab panel 7.6 Resource Tree Area .3 Restart NE 5.2 IP Configuration .2 Starting From Scratch 7. Edition 2 Section 3 · Module 1 · Page 5 9 10 19 20 22 24 25 26 27 29 30 31 32 34 35 36 37 38 41 42 46 47 48 52 55 56 57 58 60 62 70 73 74 75 87 92 93 94 97 99 100 101 103 104 105 109 111 112 113 114 117 118 133 134 137 .OSPF Area Configuration 3.3 Tab panels in the Resource Detail Area 8 Protection Schemes Tab 8.1 WebEML Main view 2.13 VLAN Configuration .14 VLAN Configuration .3 Log Browsing 4.1 Diagnosis Menu 4.

3 Browser Interface .Date & Time Setting 11.Alarm Screen 11.6 Browser Interface .Configuration Info 11.Logon 11.Date & Time NTP Enabled 11.5 Browser Interface .Logout 138 139 141 142 143 145 146 147 148 149 150 151 152 153 155 156 157 158 Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 6 .License Info 11.2 Synchronization Window 9.DHCP 11.Page 9.2 Browser Interface .8 Browser Interface .9 Community Strings Setting 11.1 Synchronization Window 9.10 Browser Interface .1 Connections Menu 11 Browser Interface 11.5 SSM Summary Table 10 Connections Tab 10.4 Allowed synchronization sources assignment 9.1 Browser Interface 11.7 Browser Interface .3 Synchronization sources assignment rules 9.4 Browser Interface . All Rights Reserved.

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 7 . All Rights Reserved.

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 8 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 9 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 10 . All Rights Reserved.

All Rights Reserved.Notes: • • • The Main Screen is the starting point of the craft terminal application. Only one NE can be managed in a NEtO session. you get an Alarm overview. Edition 2 Section 3 · Module 1 · Page 11 . When you are connected to an NE. Copyright © 2012 Alcatel-Lucent.

There is no default location for the database.NETO”. All data related to all NEs added to the list is saved in a custom format called “.NETO files that you produced with NEs information inside. Site Database • • • • You can manage and organize a list of available NEs in a table on a server or a local PC. You can have your own NEs lists repository. Edition 2 Section 3 · Module 1 · Page 12 . containing all . Copyright © 2012 Alcatel-Lucent. You can save these anywhere. All Rights Reserved. It defines what community of people can access the NE.Notes: Community Strings The Community String (CS) acts like a password to control access to an NE. but be sure you remember where you put it.

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 Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 13 .

• Confidentiality using encryption. The supported SNMP operating modes are the following: • SNMPv2: This is the default mode. Copyright © 2012 Alcatel-Lucent. SNMPv3 addresses security problems by adding two new features on top of the existing SNMPv1 and SNMPv2 network management protocols: • Authentication using hashing and time stamps. Edition 2 Section 3 · Module 1 · Page 14 . • • SNMPv3: Only SNMPv3 managers are allowed access to the NE. All Rights Reserved.Notes: • The 9500 MPR-A/E supports access from SNMP managers implementing both SNMPv2/v1 andSNMPv3 protocols. Only SNMPv2/v1 managers are allowed access to the NE for both reading and writing.

Edition 2 Section 3 · Module 1 · Page 15 . Copyright © 2012 Alcatel-Lucent. All Rights Reserved.Notes: To access the NE the PC must be set to obtain automatically or have a static IP address within the same subnet.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 16 .

numeric and special characters). All Rights Reserved. Type your password .must not be more than 20 characters. Type your username .must not be less than eight (8) or more than 20 characters and must be composed of ASCII characters set (UPPER/lower case. Edition 2 Section 3 · Module 1 · Page 17 . Copyright © 2012 Alcatel-Lucent.Notes: Login • • ).

All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 18 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 19 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 20 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 21 . All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 22 .

Edition 2 Section 3 · Module 1 · Page 23 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Each alarm severity is represented by an alarm icon situated in the top left hand corner of the view. In the WebEML these different levels are associated with colors: • Red: Critical alarm (CRI). • Orange: Major alarm (MAJ). • Yellow: Minor alarm (MIN). • Blue: Indeterminate (IND). Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 24 . There are five alarm severity levels. All Rights Reserved.Notes: • • • The WebEML provides an alarm functionality that informs the operator on the severity of the different alarms in the NE as well as on the number of current alarms. • • • • • The shape of the alarm icons in the alarm panel gives an indication of the occurrence of alarms. An alarm icon with a rectangle inside it indicates that no alarms of the type defined by the icon are occurring. • Cyan: Warning alarm (WNG). An alarm icon grayed out indicates that spontaneous incoming alarm notification have been inhibited. 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.

These different levels are associated with colors (green in normal condition). There are five different alarm severity levels. An alarm icon with a rectangle inside indicates that no alarms of the type defined by the icon are occurring. An alarm icon grayed out indicates that a spontaneous incoming alarm notification has been inhibited. Copyright © 2012 Alcatel-Lucent. • • • • • • • • • 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 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.Notes: Alarm Functionality • • The Craft Terminal provides an alarm functionality that informs the operator on the severity of the different alarms in the NE as well as on the number of current alarms. Edition 2 Section 3 · Module 1 · Page 25 . All Rights Reserved.

Orange: NE is not under supervision. COM: Operational state: indicates whether or not the communication with the OS is established. Green: NE is not managed by the 1353SH. Cyan: Indicates that the terminal does not have the OS permission to manage the NE (denied). NTP: Server Status • Cyan: NE is communicating with NTP Main or Standby servers. Orange: NTP function is disabled. Edition 2 Section 3 · Module 1 · Page 26 . • • • • • • • • • Green: NE is under supervision. • • Green: Indicates that the terminal has the OS permission to manage the NE (granted). AC: Indicates whether some abnormal conditions have been recognized.Notes: Status Control Area • • • LOCK: Local Access state: indicates whether the NE is managed by a craft terminal or by the OS. Green: Loss of communication with Main and Standby servers. All Rights Reserved. • • Green: Normal operating condition Cyan: Detection of an Abnormal operative condition Copyright © 2012 Alcatel-Lucent. The operator can visualize them with the Diagnosis-> Abnormal condition list menu. • Green: SDH service link up • Red: SDH service link down SUP: Supervision state: indicates whether or not the NE is under OS supervision. OS: OS isolation. Cyan: NE is managed by the 1353SH.

The first optional symbol indicates structure state: if symbol is "+". so activating the display/update of resource list. As soon as a node is expanded.g. Third symbol is a round-shape icon showing the alarm status of component. 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: . Tree structure can be collapsed if symbol is "-".. Edition 2 Section 3 · Module 1 · Page 27 . e. With no symbol.Notes: • • • • • • • Each tree node consists of possibly three symbols and a label. All Rights Reserved. another double click on such node would collapse tree structure to its closed view. Double left click: expands tree structure. node represents a tree leaf.the resource is highlighted. Copyright © 2012 Alcatel-Lucent. This selection causes the activation of the resource list area. The operator can select resource by clicking with mouse to perform the action dependent on click type. Second symbol is the graphical representation of resource itself. every time the operator selects a resource in the resource tree area the corresponding data are displayed in the “Resource list area”. there can be expanded showing its contained lower levels.

Notes: • The MPT-HL is for the ANSI market only • The same MPT icon is displayed for the following out door units: • • • • • MPT-MC (ETSI market only) MPT-HC MPT-HCV2 MPT-XP 9558HC (ANSI market only) Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 28 . All Rights Reserved.

All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 29 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.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 Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 30 .

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

Edition 2 Section 3 · Module 1 · Page 32 . Copyright © 2012 Alcatel-Lucent.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 the PPP protocol (not implemented) • Routing information: • shows a summary of the information relevant to the routing which has been configured. All Rights Reserved.

The dialogue box opens.closes the dialogue. Close button . the dialogue is visible until the end of the operations and a wait cursor is displayed.provides some useful information on the dialogue.used to perform a configuration change of the data contained in the dialogue box and closes it. All Rights Reserved. This local IP address is the IP address associated to a virtual interface and to the other interfaces which use the PPP protocol (the TMN-RF channels). the Local Configuration option. which allows to configure the local IP address of the NE. • • • Copyright © 2012 Alcatel-Lucent. from the cascading menu.Notes: • • Select the Network Configuration option and then. Edition 2 Section 3 · Module 1 · Page 33 . Apply button . Help button .

In the Spare Server address field. The Server reachability field is a read-only field. The following information can appear: • • • • • • • • "Main server reachable" "Spare server reachable" "None servers reachable" "Both servers reachable" Click Refresh to update the screen. which shows the reachability of the NTP servers.Notes: • • Put a check mark in the NTP protocol field to enable the protocol. that distributes the time to all the NEs in the network. All Rights Reserved. Enter the IP address in the Main Server address field for the server. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 34 . Click Close to close the NTP Configuration window. Click Apply to send to the NE the NTP Configuration. enter the IP address of the Spare Server.

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. enter the default gateway IP • For point to point.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. button address in the Gateway IP Address field. from the Interface Type dropdown menu. click the Gateway IP Address. click the Host button and enter the IP address in the IP Address field • Network. Host or Network Address: • For Host. All Rights Reserved. click the Point to Point Interface Index button and select Gateway Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 35 .

Enter the OSPF Area Address and the OSPF Area Stub Flag (True/False) and press "Create" button to apply and add the area to the table. Edition 2 Section 3 · Module 1 · Page 36 . New button is used to insert a new page. WARNING: When the area is a Stub area. the view is visible until the end of the operations and a wait cursor is displayed. Apply button is used to perform a configuration change of the data contained in the complete RAP table and close the view. Delete button is used to delete the selected page. All Rights Reserved. • • • • To configure a new area tick the "new" check box to ungray the IP address stub area. Close button closes the dialogue without changing of the data.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 a Network) in an Area. Copyright © 2012 Alcatel-Lucent. all the interfaces (NMS and Ethernet) must be defined “Stub".

Copyright © 2012 Alcatel-Lucent. The Close button closes the dialogue without changing of the data. Edition 2 Section 3 · Module 1 · Page 37 . All Rights Reserved.Notes: • • The Refresh button allows to refresh the information shown in the screen.

All Rights Reserved. Copyright © 2012 Alcatel-Lucent. Profile "All Alarms". Edition 2 Section 3 · Module 1 · Page 38 . This profile enables the emission of all the alarms. Each alarm has its Service Affecting and No Service Affecting attribute. This screen is a read-only screen. This profile enables the emission of the Tx alarms of the radio link. With this profile all alarms are disabled. • • • • Profile "Radio Rx Alarms". It is only possible to select one Profile Name and display the relevant alarms. Profile "Radio Tx Alarms". which can differ according to the Alarm Severity Profile. This profile enables the emission of the Rx alarms of the radio link.Notes: • The Profile Name field the four alarm severity profiles are listed: • • • Profile "No Alarms". 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.

The Alarm Severity Profile screen displays. All Rights Reserved. Select the object to which an Alarm Profile has to be associated. Edition 2 Section 3 · Module 1 · Page 39 . Copyright © 2012 Alcatel-Lucent. Click on the icon. 2.Notes: 1.

Notes: 3. Put a check mark on the "Show details" box. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 40 . Select the Alarm Profile to be associated. 4. Copyright © 2012 Alcatel-Lucent. The list of the alarms with the relevant severity displays. 5. Click Apply to associate the Alarm Profile. 6.

required to provision the System Priority (2 bytes) associated to the NE. • Ethernet LOS Criteria . This MAC address must be used in the cross-connection with TDM2Eth profile. Default is SNMPv2. All Rights Reserved. plus the System ID (NE MAC address). the events are not sent to the Event Log Browser application • NE MAC Address . providing the setting of some parameters for the NE setup.This field is a read-only field.By enabling this feature the following additional criteria are added to the Core protection switching criteria.1 bytes] System Priority [2 .7 bytes] NE MAC address) • Event and Alarm Log – Enables (default) event and alarm logging. The NE configuration tab-panel has 9 fields: • Tributary Port Configuration . This parameter. but the Ethernet traffic is not forwarded. Default: “Enabled”. • Static Lag Criteria . determines the System Aggregation Priority ([0 . When disabled. • Admission Control for Adaptive Modulation (ODU300 only) – the Admission Control for TDM flows (cross-connected to radio direction working in Adaptive Modulation).set the suitable impedance of the E1 stream (Unbalanced 75 ohms/Balanced 120 ohm). IP mask and default gateway of the PC Ethernet interface used to reach the NE. • SNMP Mode – This field indicates which protocol is allowed for SNMP managers accessing the NE: SNMPv2 or SNMPv3. Copyright © 2012 Alcatel-Lucent.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. • System Priority Parameter .Notes: • The System Settings window supports system configuration.configures automatically IP address. Edition 2 Section 3 · Module 1 · Page 41 . which shows the MAC address of the NE. • DHCP .

: Slot#5 RADIO is protected with Slot#6 RADIO). the 2 protected slots are linked by a dashed line. LAG #1 is an Ethernet LAG.g. Edition 2 Section 3 · Module 1 · Page 42 . (e. Ethernet ports involved in an Ethernet LAG are only present in the LAG area (not in the CORE-E area). Copyright © 2012 Alcatel-Lucent. • 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. • • • • LAG and Ring icons Different icons are used to identify Radio LAG or Ethernet LAG. • LAG and Ring icons are displayed on the right side of the screen with identifying numbers.Notes: • The Main view is a graphical representation of Cross-connectable slots. • The even numbered slots of rows 2 to 4 are on the top of the screen. In the figure LAG #4 is a Radio LAG. 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. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 43 . By using the mouse drag-and-drop operations the operator can create cross-connections through these points.and end-point for actual cross-connections.Notes: The connectors representing the MSS slots are start.

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. Edition 2 Section 3 · Module 1 · Page 44 . All Rights Reserved. • Green: a connector able to accept a cross-connection and already has one active crossconnection at least. Copyright © 2012 Alcatel-Lucent. • Blue: a connector not able to accept a cross-connection.

Notes: • • • This area contains a panel and various components representing NE cross-connectable slots (or connectors). The figure shows an example of ongoing cross-connections configuration. Edition 2 Section 3 · Module 1 · Page 45 . Copyright © 2012 Alcatel-Lucent. All Rights Reserved. The operator can directly edit with the mouse this graphical area to visually create and modify cross-connections between available connectors.

Notes: The Ring Configuration window consists of the following panels: • • Ring Topologies ERP Instances Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 46 .

L2 Radio.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.).If Type is L2 Ethernet/Radio. • Timeout . • Size drop-down menu . Size. • Type drop-down menu .select lag ID number (1-14).select LAG size (for L1 Radio (1-4). Port User Label) about ports that can be added to the LAG. and Hash • Allows the selected LAG to be enabled. Copyright © 2012 Alcatel-Lucent. or L2 Ethernet). Passive. • LACP drop-down menu .Enter the LAG name. • Added Ports – Lists ports that are added from the Available Ports • LAG Creation window panel. All Rights Reserved. • Contains changeable fields for Name. • Name . Timeout .select (L1 Radio. optional (up to 32 characters max. • ID drop-down menu . then select Admin Key value (1-32).timeout period (Short or Long). for L2 Ethernet/Radio (1-8)) • Key drop-down menu . Edition 2 Section 3 · Module 1 · Page 47 . or Disabled). • PPP RF – allows enabling of PPP routing information (displays only for L1/L2 radio LAGS) • Available Ports: displays port information (Slot. select LACP support (Active.L2 Ethernet.

Notes: The QoS Configuration menu has 3 tab-panels: • Scheduler Configuration • Queue Size Configuration • QoS Classification Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 48 .

Notes: In the figure the default configuration is shown. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 49 . Apply button – applies changes to the NE Refresh button – resets unapplied changes Copyright © 2012 Alcatel-Lucent. Defaults button – return to the default settings. • Mode field – contains a drop-down menu that contains the following queue scheduling algorithm selections: • • • • • • • SP – Strict Priority DWRR – Deficit Weighted Round Robin Weight field – priority weight (1-32) Restore button – return to the previous configuration.

Notes: • • • • • • Each queue can have an assigned buffer size (in bytes) for each radio direction. Apply button – apply changes to the NE. Edition 2 Section 3 · Module 1 · Page 50 .return to the default settings. All Rights Reserved.1 has a buffer size of 100000 bytes with a maximum delay of 8 msec. For example. the current and default values of the queue size with relevant conversion in msec are displayed. Press the Apply button to confirm the default values. Copyright © 2012 Alcatel-Lucent. Q4 for radio direction #7. Note: The Default button only shows the default values. Copy and Paste buttons .Copy and Paste the parameters of one Radio direction can be copied to another Radio direction. Note: If you float the cursor over field. Restore button – return to the previous configuration Defaults button .

• Copyright © 2012 Alcatel-Lucent. All Rights Reserved.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. Edition 2 Section 3 · Module 1 · Page 51 .

without any local termination. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 52 . Service channels cross-connection in pass-through It is possible to cross-connect each individual radio service channel with a radio service channel of another radio direction.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 an ODU300 radio link. with one of the three radio service channels (service channel to MPT is not supported in this release). Copyright © 2012 Alcatel-Lucent.

2. Note: The Apply button is not operational in this release. Note: the local service channel must be first enabled in the AUX unit setting menu.Notes: 1. Select the first termination point in the New Cross-Connection area (this can be a local service channel or a service channel in a radio link). Note: the cross-connections are bi-directional. The new cross-connection will appear in the list (upper part of the screen as shown in the figure). Select the second Termination Point as shown in the example in the figure. Copyright © 2012 Alcatel-Lucent. 3. Click on Add. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 53 .

2. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 54 . Click Delete.Notes: 1. Select the Cross-Connection to be deleted (see the figure). The selected cross-connection is removed from the window.

Notes: • • The 1+1 XPIC Configuration consists of two groups of 1+ HSB with different polarization. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. The XPIC Configuration menu opens by clicking on the relevant button on the Tool bar. Edition 2 Section 3 · Module 1 · Page 55 .

All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 56 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. The packets from the user Ethernet ports having the VLAN ID out the allowed range (0 and 24080) are dropped. the Ethernet traffic is switched according to the destination MAC address without looking the VLAN.Notes: • • When the NE is configured in this mode (default configuration). Edition 2 Section 3 · Module 1 · Page 57 . Copyright © 2012 Alcatel-Lucent. The packets having a VLAN ID already used for a TDM flow are accepted.

export the VLAN configuration in a file with extension CSV. The management system prohibits the definition of VLAN ID already used. Refresh . The file can be stored in the PC to be read later. Edition 2 Section 3 · Module 1 · Page 58 .4080. TDM2ETH) cannot be used. Delete: delete a VLAN-ID. The VLAN IDs already defined to cross-connect internal flows (i. VLAN untagged ports in egress). • • • • • Filter – display a filter by inserting a name in the "Filter by Name" box and clicking on Filter.change the parameters of a VLAN (VLAN name. The VLAN ID must be different also from the Flow Id associated to E1 tributaries not yet cross connected. All Rights Reserved.by clicking this button all the VLAN created in VLAN table will again appear. the management of Ethernet traffic looking the VLAN is enabled.e.Notes: • • • • New . Copyright © 2012 Alcatel-Lucent. It is possible to remove a VLAN-ID from the VLAN-ID table even if this VLAN-ID has been already configured on one or more user ports as Port VLAN to be added in ingress to untagged frames. Clear Filter . Export . one VLAN will be assigned to all Ethernet frames inside the MPR network. TDM2TDM. In this mode. VLAN member ports. WARNING: The VLAN ID values configurable must be in the range 2 .create a new VLAN (refer to VLAN table management) Edit . When the NE is configured in this mode.the VLAN table is updated.

Edition 2 Section 3 · Module 1 · Page 59 . All Rights Reserved. VLAN 1 Management • • • • VLAN-ID 1 is automatically defined by the NE when the 802. but it cannot be neither changed nor deleted. they will appear in the VLAN management. In egress VLAN-ID 1 is always removed from all the ports.Notes: • If a Radio LAG or an Ethernet LAG has been created.1Q bridge type is selected. as shown in the figure. Copyright © 2012 Alcatel-Lucent. VLAN-ID 1 is shown to the operator. All the user Ethernet ports (enabled and disabled) and all the radio ports are members of the VLAN 1.

z 6. The already created Traffic Descriptor will appear in the List Traffic Descriptors area. UBR+ or UBR (rtVBR and nrtVBR are not managed) Conformance Definition: CBR. based on the related ingress ATM Traffic Descriptor. All Rights Reserved.) x 6 (6 ASAP units in the NE max. • To create a Traffic Descriptor: 1. Configure the following parameters: z Service Category: CBR. Enable or disable the Policing.1. • To delete a Traffic Descriptor: 1.Notes: Create or delete the traffic descriptors. Edition 2 Section 3 · Module 1 · Page 60 .). Click on Create 7. VBR. The default configuration of ATM Policing is according to configured Service Category: z enabled for VP/VC having Service Category CBR. Select the domain: ATM (if in the NE the ASAP unit is present) or PWE3 (in the repeater nodes or in the nodes.3 are not managed) z 4.2. VBR. Insert a label to identify the Traffic Descriptor 3. disabled for VP/VC having Service Category UBR+ and UBR. Select in the List Traffic Descriptors area the Traffic Descriptor to be deleted and click on Delete. For each VP/VC it is possible to enable/disable a cell-based ATM Policing. Configure the following TD Parameters: PCR. that will be associated to the ATM traffic at the ingress and/or at the egress. MDCR 5. Copyright © 2012 Alcatel-Lucent. Note: The maximum number of ATM Traffic Descriptors configurable on a NE is given by 2 times the max number of configurable VPs multiplied by max number of ASAP Cards that can be hosted: 2 (2 traffic Descriptors per circuit) x 128 (128 circuits max. CDVT.1 (VBR. where an Ethernet termination is present) 2.

Edition 2 Section 3 · Module 1 · Page 61 . z z Copyright © 2012 Alcatel-Lucent. for CDVT the unit is microseconds.SCR) are defined in terms of cell/second. range for CDVT is 0 to 40000 microseconds.Notes: z UBR+ Service Category is defined as an UBR Service Category with Traffic Descriptor Parameter 3 (MDCR) > 0 ATM Traffic Descriptor Parameters for VP/VC rates (PCR. range for MBS is 0 to 1000 cells. for MBS the unit is cells Range for ATM Traffic Descriptor Parameters with VP/VC rates is 0 to the bandwidth of related physical or logical ATM interface. All Rights Reserved.

All Rights Reserved. are accepted and maintained. • Password composition: the password can include full ASCII characters set (UPPER/lower case. • Username length: the length must be not longer than 20 characters. Moreover the password length must be not longer than 20 characters. an error message will be displayed. • By clicking on the Cancel button. After 3 consecutive failed attempts the login procedure is closed and JUSM does not start. Edition 2 Section 3 · Module 1 · Page 62 . created with older software versions. JUSM will be started and the operator will be allowed to perform the actions according to the right related to his profile. The default Password is “adminadmin”. If the login parameters are not correct. the operator will be authorized or not to continue. • 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. numeric and special characters). • The existing passwords less than eight characters (e. According to the operator authentication (correct couple username/password) managed by the NE.g.. the login procedure is stopped and the JUSM does not start.Notes: • • • The default Operator Name is “initial”. Copyright © 2012 Alcatel-Lucent. while the Login window is still open for a new attempt. 6 or 7 characters). On the contrary if the user name and password are correct.

Edition 2 Section 3 · Module 1 · Page 63 . All Rights Reserved. Copyright © 2012 Alcatel-Lucent.Notes: These items will be enabled according to the right of user profile recognized at login.

• The operator can perform the following actions: z Create z After „ a new User by clicking on the Create button. By clicking on Users Management the window displayed in the Figure appears. Edition 2 Section 3 · Module 1 · Page 64 . Change PW (by Administrator) by clicking on the Change PW button. Help button – displays the help browser with context sensitive help information.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. All Rights Reserved. the operator can perform the following actions: Delete an existing User (the Initial and Craftsperson Users cannot be deleted) by clicking on the Delete button. „ Copyright © 2012 Alcatel-Lucent. the selection of a user in the table.

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.. Also the management of user accounts is allowed (create/delete user accounts and change of all passwords). For writing mode the following parameters are allowed to change: • ATPC configuration (enabled.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 security parameters. Received Power Levels. . but cannot manage the user accounts • Viewer profile: This operator can only read and can change his own password. 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. Edition 2 Section 3 · Module 1 · Page 65 .) • 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... E1. • Copyright © 2012 Alcatel-Lucent. All Rights Reserved. • Operator profile: Full reading access to NE parameters.

If all parameters are correct.Notes: • • • By clicking on Apply button. the Create User window closes and no action will be performed. a message with result of the action will be displayed. Edition 2 Section 3 · Module 1 · Page 66 . Copyright © 2012 Alcatel-Lucent. after to have automatically closed the window. All Rights Reserved. JUSM will display the specific message and allows the operator to correct them. By clicking on Cancel button. all parameters are sent to NE. at first JUSM performs a syntax check of each field: if there are some errors.

Notes: 1. The Delete User window is displayed. Copyright © 2012 Alcatel-Lucent. Clicking the Delete button. 4. A Deletion Confirmation dialog box is displayed. 3. Edition 2 Section 3 · Module 1 · Page 67 . Click the Yes button on the dialog box. Click the Apply button to delete the user (or click the Cancel button to stop the deletion and close the window. 2. Select a user in the profile table in the Profiles Management window. All Rights Reserved. Enter the administrator password. 5.

The Changing Password window is displayed.Notes: The Administrator can change the password of another user with the following procedure: 1. Enter the following in the respective fields: • • • 4. 2. Click the Change PW button. Edition 2 Section 3 · Module 1 · Page 68 . 3. 2. Select the Configuration > Profiles Management > Users Management menu item. Copyright © 2012 Alcatel-Lucent. Old Password (existing user’s password) New Password Confirm New Password Click the Apply button to accept the new password or Cancel to abort the change and close the window. All Rights Reserved. Select the user in the profile table whose password will be changed. The Profiles Management window is displayed.

All Rights Reserved. Copyright © 2012 Alcatel-Lucent. Enter the following in the respective fields: • • • 3. Select the Configuration > Profiles Management > Change Password menu item.Notes: 1. Old Password (existing password) New Password Confirm New Password Click the Apply button to accept the new password or Cancel to abort the change and close the window. Edition 2 Section 3 · Module 1 · Page 69 . 2. the system will display the specific message and allow the user to correct the errors. the system performs a syntax check of each field: if there are errors. The Changing Password window is displayed. Once the Apply button is clicked.

All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 70 .Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 1 · Page 71 . letter L is placed on the MPT icon on the Equipment view. are in italics. in the CORE-E domain in the Ethernet Physical Interface tab-panel the Settings tab-panel of the Ethernet port grouped in a LAG is gray (no changes can be done). but it not possible to see the association of a specific User Ethernet port to a specific Ethernet LAG. All Rights Reserved.Notes: • • The keywords are in bold the variables. • Copyright © 2012 Alcatel-Lucent. To know if an Ethernet user port is grouped in an Ethernet LAG. but in this view it not possible to see the association of a specific MPT to a specific Radio LAG. To know if an MPT is grouped in a radio LAG.

All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 72 .Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 1 · Page 73 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Notes: The Diagnosis Menu contains: • Alarms • Log Browsing • Remote Inventory • Abnormal Condition List • Summary Block Diagram View • Current Configuration View • Performance Monitoring Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 74 .

Notes: • • Alarms Monitor is an application which allows to display and store the alarms of all the NEs requiring it. All Rights Reserved. Alarms Monitor can be also started by clicking on the Alarms Monitor button on NEtO. Edition 2 Section 3 · Module 1 · Page 75 . Copyright © 2012 Alcatel-Lucent.

• ALARM_LOG shows all the equipment alarms currently present and the history of the alarms (i. 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 in the ALARM_LOG list as a cleared alarm.Notes: • On the left side of the application. which are no longer active (this filter is available within the list ALARM_LOG only). that is. • • Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 76 . The number of active alarms is shown inside brackets. below each NE. two global lists of alarms are displayed: • CURRENT_ALARM shows all the equipment alarms currently present. All Rights Reserved. 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.e.

• 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). Edition 2 Section 3 · Module 1 · Page 77 . the field Synthesis shows the number of active alarms for any severity. Click on a filter or on a global list on the left part of the screen shows up on the right side the relevant tab panel with all the alarms. Copyright © 2012 Alcatel-Lucent. At the top right. • The alarms have a different color according to their severity and their state. All Rights Reserved.Notes: • • • When the application is opened for the first time. only the tab-panels of the two global lists are displayed on the right part of the window.

• Severity: alarm severity. • Specific problem: for some alarms. The format of date and time is yyyy/mm/dd hh:mm:ss. • Friendly Name: object of the equipment where the alarm occurred. when a threshold alarm is raised. • Probable cause: name of the probable cause of the alarm. • Add Text: this is an additional text regarding the alarm.Notes: Within the tab-panel. additional information is provided about the involved resource (for instance. All Rights Reserved. • Alarm Type: alarm class (TRS = Transmission Alarm – alarm not created inside the equipment. Edition 2 Section 3 · Module 1 · Page 78 . EQUIPMENT: inside alarm of the equipment). each alarm is provided with the information below. but generated by a connected equipment or due to transmission/propagation problems. it states the specific threshold exceeded) Copyright © 2012 Alcatel-Lucent. • Time & Date: date and time of the alarm.

HTML. Print current view: it is possible to print the list of the alarms. e.Notes: • Navigate to USM: to navigate to the object involved with the selected alarm and to open the relevant window. to export alarms to a file. Note: this option is available in the CURRENT_ALARM global list and in the relevant filters only. Edition 2 Section 3 · Module 1 · Page 79 . All Rights Reserved. Alarms have to be selected by means of the menu Select Æ All.g. Select All: to select all the alarm of the list for further use. • • • • Copyright © 2012 Alcatel-Lucent. Select None: to select no alarm. Generated file formats are CSV. Export Alarm: to create a file containing alarms data. XML and PDF. The “Print Dialog” box is shown to choose the printer and set Print range and Copies number.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 80 . All Rights Reserved.

• Remove selected NE • Remove an NE. Copyright © 2012 Alcatel-Lucent. Select the global list of a specific NE. HML or PDF) and then assign the name of the file. select "Export Alarms" menu. selected in the list. HTML.Notes: • Save Log for selected NE • Save a file with one of the two global lists of each NE. open the Save History menu for the selected NE and enter filename and relevant directory in the opening window. Edition 2 Section 3 · Module 1 · Page 81 . All Rights Reserved. choose the file format (CSV. • Load Log to selected NE • Display the global list of a certain NE previously saved. • Export Alarms • Save a file with the alarms of the selected Log. Select the log.

Close a currently opened filter • Add a Filter … • Edit Selected Filter … • Delete Selected Filter … • Delete Filters … • Save Filters As … • Load Filters From … Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 82 .Notes: The Filters menu provides the following menus: • Close Filter .

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). The created filter appears on the left side of the application. Event Time field • Select Event Time and then enter the starting date (From) and the ending date (To) to filter the alarms created during that specific time frame only. (Clicking on the Cancel pushbutton clears the filter configuration). • Select APT (Current) to create a filter showing the current alarms only or select Log to create a filter for current and cleared alarms.Notes: • Filter Name field • Enter the filter name in the Filter Name field. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 83 . To save the created filter click • Scope field on the Done pushbutton. All Rights Reserved. • The filter can be applied to all the NEs by selecting All or it can be applied to one or more NEs by selecting one or more NEs using the mouse. Probable Cause field • Select Probable Cause and choose a specific alarm (one or more) to filter these particular alarms only. • The filters can be created selecting one of the following fields (or more). • Alarm Type field • Select Alarm Type to create a filter for the selected type of alarm: • TRS = Transmission Alarm • EQUIPMENT = Equipment alarm • • • • Perceived severity field • Select Perceived severity and then one or more severity levels and/or Cleared state to filter the alarm having the selected severity levels.

Edition 2 Section 3 · Module 1 · Page 84 . Copyright © 2012 Alcatel-Lucent. Default filters cannot be canceled. 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.Notes: • • • Cancel previously created Filters. Select one specific NE (or more NEs) in the Scope column. All Rights Reserved.

enter the filter name in the Name field. Edition 2 Section 3 · Module 1 · Page 85 . • Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Clicking on the Cancel pushbutton cleasrs all selections. select the Folder where to save the file relevant to filter and then click on the Done Pushbutton.Notes: • Select in the Scope and Filters columns a specific filter to be saved.

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. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. For instance entering <Vim>. Edition 2 Section 3 · Module 1 · Page 86 . the names of the filters change from APT to VimAPT.Notes: • • Click on Browse to navigate and then choose the filter file to be loaded. The Scope and the Loaded Filters columns will show respectively the NE list and the filters list made available by the selected file.

All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 87 .Copyright © 2012 Alcatel-Lucent.

• Notification ID: a unique identifier for the event. All Rights Reserved.Notes: • The following information is provided for each event: • Time: date and time of occurrence of the event. Reference Time (CEST) year. The format is week day/month/day hh:mm:ss. The Menu Bar provides the following menus: • File • Help Copyright © 2012 Alcatel-Lucent. • Event Log Browser is an application which allows to display all the events occurred in the NE. The max. 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. • Explanation: a statement built with the event log data to explain what the event represents. number of stored events is 500. Edition 2 Section 3 · Module 1 · Page 88 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 89 .

Copyright © 2012 Alcatel-Lucent. The Export may be executed as well clicking on the relevant pushbutton below the menu bar. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 90 . CSV. The file can store all the events (All entries) or only those selected by means of the pointer of the mouse ( Selection).Notes: • • The file can have the HTML. PDF or XML format.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 91 . All Rights Reserved.

All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 92 .Copyright © 2012 Alcatel-Lucent.

RPS. detected automatically (i.e.Notes: • An abnormal condition is generated each time: • • • a non usual condition is present in the NE. automatic Tx mute) as consequence of management systems operation (i. Edition 2 Section 3 · Module 1 · Page 93 . force switching. loopbacks. TPS) • Loopback activation • Local radio Tx mute (manual) • Adaptive Modulation in normal mode Copyright © 2012 Alcatel-Lucent. All Rights Reserved. TPS) • Lockout (EPS. •The list of the events which cause an abnormal condition: • Forced switch (EPS. RPS.e. manual Tx mute).

Edition 2 Section 3 · Module 1 · Page 94 . Copyright © 2012 Alcatel-Lucent.Notes: The “Summary Block Diagram View” displays a global logical view (strictly related to the physical implementation) highlighting a synthesis of all the alarms and statuses present in the system. All Rights Reserved.

grouped in Ethernet LAG#1. with updated content views. pp • An Ethernet User port involved in an Ethernet LAG disappears from the CORE-E area (in figure port #1 and #2 are show ow because are optional and have not been configured. it is possible to navigate to the Abnormal Condition List menu. • In the Main view the current configuration of the MSS is shown. with the protection schemes and with the cross-connections implemented between the different units and the different Ethernet ports. Port #5 and #6 are not sh shown • On the RADIO/MPTACC slot icon there is the symbol because on this unit a loopback can be activated. • by double clicking on an MPTACC slot icon. If these symbols are green. • The “Refresh” button will close all secondary windows. with the equipped units (PDH or SDH or Radio or MPTACC). Edition 2 Section 3 · Module 1 · Page 95 . it is possible to navigate to the TMN view in the Core-E unit. • by double clicking on a Radio slot icon. Copyright © 2012 Alcatel-Lucent. • The Core-E has 2 alarm indicators in case of Core-E protection (as shown in figure) and only 1 alarm indicator (the ball icon on the left side) in case of unprotected configuration. if any. it is possible to navigate to the secondary view for the Radio unit. According to following figures. bold light green lines update according to the actually NE working way. In figure LAG #4 is a Radio LAG. • by double clicking on the TMN Local Interface box. with the created LAG. and re-opening all previously opened secondary windows. it is possible to navigate to the secondary view for the MPTACC unit. • Different icons identify Radio LAG or Ethernet LAG. updating the main view one. • by double clicking on a PDH slot icon. LAG #1 is an Ethernet LAG. • by double clicking on a Loopback the relevant configuration is displayed. it is possible to navigate to the secondary view for the PDH unit. • by double clicking on a Protection switch the relevant configuration is displayed. In detail: • by double clicking on the Alarm indicator the relevant active alarm is displayed • by double clicking on the Abnormal Condition List box.Notes: • Each block has its Alarm indicator (colored ball icon) that shows the alarm status by color. alarm icons update as well. • By double clicking on an object it s possible to navigate to specific views. • The green line is the current active path. All Rights Reserved. • All diagrams are automatically refreshed. the symbol because it is also possible to activate a Performance monitoring and/or the Ethernet traffic counters. it means that the loopback is active or the Performance monitoring/Ethernet Counters have been activated.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 96 .

Notes: The Current Configuration View contains configuration information that is organized into the following 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 Cross Connections Ring Bridge Synchronization Software Package Status Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 97 .

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 98 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 99 . All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 100 .

a Local Access Control (LAC) is available. However. the OS does continue to provide a certain number of services. • Performance processing. the icon with a key symbol has a rectangular shape.Notes: • To control the competition of the OS and the WebEML. • Switching back to the OS access state. the icon with a key symbol has a circular shape. Edition 2 Section 3 · Module 1 · Page 101 . In the view. • If the LAC is “access denied”. it means that the WebEML has requested a permission from the OS and is waiting for a replay. it means that the WebEML is allowed to manage the NE. These services include: • Alarm reception and processing. it means that the OS manages the NE and the WebEML is not allowed to modify the NE configuration (it can only «read»). • • • Copyright © 2012 Alcatel-Lucent. If the LAC is “requested”. In the view. All Rights Reserved. The access state of an NE can be modified from two types of views. If the LAC is “granted”.

Notes: •Requested option does not and can be When the Requested option from the Access State cascading menu and the OS answer in a predefined time. WebEML access can be denied or granted). the OS automatically recovers the communication and forces the state existing before the loss of communication (therefore. All Rights Reserved. •The key symbol icon on the management states of the NE view indicates whether the NE is managed by a WebEML or by the OS. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 102 . When the communication with the NE is lost. •OS option managed by the Select the OS option from the Access State cascading menu. The NE is now OS. it is assumed that the NE is in the Craft access state managed by a WebEML. •Local WebEML access is denied on recovery phase after a loss of communication of the NE.

All Rights Reserved.Notes: WARNING: After the activation of the Restart NE Command (or after the pressing of the HW reset push-button) the supervision of the local NE and the remote NEs is lost. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 103 .

All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 104 .Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 1 · Page 105 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

1. Confirm the backup operation by clicking Yes to start the operation. Warning: The backup file name must not include the following characters: space. Copyright © 2012 Alcatel-Lucent. To backup the configuration write the filename in the File Name field and press Save. corresponding to version V2. when the MIB back-up file is created.0).4. The file name contains always the version as prefix (example: "V020100". and is under the path where you have performed the Local copy of WebEML(Jusm/CT). This folder is automatically selected when you perform any of the commands of the MIB management menu. Edition 2 Section 3 · Module 1 · Page 106 . When the backup is completed in the upper part appears the list of the previously created backups.Notes: • • • • The Backup function saves the NE configuration using the WebEML. "V030400". and is used automatically by the SW.0. The folder name is "backup". &. corresponding to version V3. /. All Rights Reserved. when the MIB restore must be performed. This prefix is inserted automatically by the SW. • • There is one default repository folder of MIB back-up files for all NEs having the same SWPrelease.

Select one of the backups to be downloaded in the upper part and press Open. Click Yes. Copyright © 2012 Alcatel-Lucent.Notes: • • • • The Restore/Activate function downloads and activates a previously created backup using the WebEML. When the restore is completed a message displays prompting for activation of the restored file. Edition 2 Section 3 · Module 1 · Page 107 . All Rights Reserved. Confirm the restore operation by clicking Yes to start the operation.

Edition 2 Section 3 · Module 1 · Page 108 . To remove a backup select the file in the upper part and press Remove file.Notes: • • • • The Remove file function removes selected backups from the list. Copyright © 2012 Alcatel-Lucent. By pressing Refresh the list in the upper part of the screen is updated. All Rights Reserved. Confirm the operation by clicking Yes to start the operation.

Notes: • The following fields are present: • • • • RMU Serial Number: in this read-only field appears the Serial Number of the Flash Card. All Rights Reserved. License String: in this read-only field appears the type of the license written in the Flash Card. To upgrade the license copy in this field the code of the new license and click on Apply. License Key: this field is used to upgrade the license. Copyright © 2012 Alcatel-Lucent. The Refresh button activates a new reading of the read-only fields. Edition 2 Section 3 · Module 1 · Page 109 .

Edition 2 Section 3 · Module 1 · Page 110 . All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 111 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 112 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 113 Section 3 · Module 1 · Page 113 . All Rights Reserved.

Notes: • • The ODU300 is identified by a number indicating the slot number in the MSS. Copyright © 2012 Alcatel-Lucent. the second digit indicating the enabled Ethernet port in the MPT Access unit or in the CoreE unit (from 1 to 6). where the Modem unit is installed. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 114 . 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 MPT-HC or MPT-MC (ETSI market) is identified by two digits: • • • the first digit indicating the slot number in the MSS. The icon of the MPT-HC or MPT-MC will appear only if the MPT Access unit has been configured in the MSS and one port (from 1 to 4) has been enabled.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 115 .

All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 116 .Copyright © 2012 Alcatel-Lucent.

Select the unit type in the Equipment type profile. Click the Settings panel. Click Apply. 3. Select a slot. 2. All Rights Reserved. 4. To configure a card: 1. Copyright © 2012 Alcatel-Lucent.Notes: The Resource Tree area contains a list of empty slots that have to be configured. Edition 2 Section 3 · Module 1 · Page 117 . The icon is used to identify an empty slot.

All Rights Reserved.Notes: For every unit there are 3 tab-panels: • Alarms • Settings • Remote Inventory Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 118 .

The alarm tab panel has one row for each possible alarm. All Rights Reserved. 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 Copyright © 2012 Alcatel-Lucent. which checks the current state of alarms related to the selected object. Edition 2 Section 3 · Module 1 · Page 119 .Notes: • • • • The Alarms tab panel provides the fault management. but only rows related to the active alarms 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 in the sub-nodes of the object to appear.

Edition 2 Section 3 · Module 1 · Page 120 . All Rights Reserved.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 Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. • Select the unit type in the equipment type profile and click Apply. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 121 .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.

an MPT-HC only to port#5 and port#6. All Rights Reserved.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 SFP must be installed). Edition 2 Section 3 · Module 1 · Page 122 . Copyright © 2012 Alcatel-Lucent. • Select the option (SFP or MPT-HC/MPT-MC) and click on Apply. • MPT interface: MPT-HC or MPT-MC to port#1 to port#4.

Copyright © 2012 Alcatel-Lucent. • Port#1 and Port#3. Port#2 and Port#4 are mutually exclusive. Port#1 and Port#2 are electrical Ethernet ports and Port#3 and Port#4 are optical Ethernet ports. Select as Usage MPT-HC or MPT-MC (in 2 ports max) and click on Apply. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 123 .Notes: • • • In the Setting tab-panel one or two of the four Ethernet ports (to be connected to the MPT-HC or MPT-MC) must be enabled as shown in figure above.

only SFP#1 with SDHCHAN) and click Apply. Copyright © 2012 Alcatel-Lucent.Notes: • • • The Settings tab-panel of the STM-1 unit is shown above. Edition 2 Section 3 · Module 1 · Page 124 . 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. All Rights Reserved.

Notes: • • Port #5 to #8 can be configured to accept an optical SFP. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 125 . Select option SFP and click Apply. All Rights Reserved.

Edition 2 Section 3 · Module 1 · Page 126 . in Local TMN Ethernet interface and in the Radio object). All Rights Reserved.Notes: This function relates to an alarm severity profile to be assigned to a selected object (it has been implemented in MSS shelf. Copyright © 2012 Alcatel-Lucent.

before creating protection in MIB.Notes: • • • This function allows the operator to configure the NE protection type. if peer board is not configured. Edition 2 Section 3 · Module 1 · Page 127 . Copyright © 2012 Alcatel-Lucent. All Rights Reserved. If the user applies a new expected protection type. involved slots are bounded by light green lines. Configuring a 1+1 protected board. With a configured 1+1 protection. both tree view and configuration panel are reloaded and updated. This function is shown selecting slots 3 to 8 only. the WebEML will be in charge of applying such configuration to un-configured peer board.

1.Notes: To configure the protection scheme select the MPT. In the example MPT-HC#52: connected to Port#2 of the MPT Access unit in Slot#5. All Rights Reserved. Choose in the Protect Port field one port available in the list. Copyright © 2012 Alcatel-Lucent. 2. As protection can be also used an 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. Edition 2 Section 3 · Module 1 · Page 128 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 129 . All Rights Reserved.Notes: After the configuration in the screen will appear the two jointed MPT-HC.

Edition 2 Section 3 · Module 1 · Page 130 . All Rights Reserved. Copyright © 2012 Alcatel-Lucent.Notes: The field Protection Type appear only when the 2 STM-1 units have the same configuration (only with SFP-O. not with SFP-E).

The stacking configuration is highlighted in green as shown in the following figure (units in slots #3 and #4).Notes: • • Two MPTACCess units or two P8ETH units installed on the same row are automatically grouped in a stacking configuration. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 131 . Copyright © 2012 Alcatel-Lucent.

Clicking on the Remote Inventory tab displays information for the selected Core-E card in the example. The Remote Inventory tab displays information for a piece of equipment that is selected either from the resource tree or from the work area. All Rights Reserved. A read-only copy of the remote inventory for the entire NE can be generated from the Diagnosis Menu. Copyright © 2012 Alcatel-Lucent. It is also highlighted in the MSS-8 that is displayed in the work area. the Core-E card (Slot#1 MSS/CORE-MAIN) is selected from the Resource Tree. Edition 2 Section 3 · Module 1 · Page 132 .Notes: • • • • • Selecting from either the equipment tree or the resource area will display remote inventory data if it is available. In the example above.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 133 .

Notes: • The 1+1 protection schemes implemented are: • Equipment protection: EPS protection in Tx and Rx sides (this protection scheme can be implemented for all the unit types: Modem unit. All Rights Reserved. For the pair of SDH units the only protection type is the Equipment Protection (ETSI market). For the pair of PDH units the only protection type is the Equipment Protection. 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. For the pair of Radio units or MPT Access units the protection type are the Equipment Protection. • • • • Copyright © 2012 Alcatel-Lucent. For the pair of Core-E units (slot 1 and 2) the only protection type is the Equipment Protection. Radio Protection and HSB Protection or FD protection. Edition 2 Section 3 · Module 1 · Page 134 . if in the synchronization tab panel the Primary Source and the Secondary Source have been selected or the NE has been configured as Master with Free Running mode.

The supported type is: 1+1. No changes can be done separately for 1+1 HSB-EPS. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 135 . is allowed (revertive mode) or inhibited (not revertive mode).Notes: Protection Scheme Parameters • • The tab-panel “Scheme Parameters” displays the parameters that can be modified.g. The PDH/SDH protection type is Not-Revertive and cannot be changed. The restoration criteria selected for HSB-TPS will be applied to EPS automatically. The operator choice for “Restoration Criteria” will be applied by clicking on “Apply” button. a working channel (Main) is protected by a protecting channel (Spare). the restoration criteria are always grayed out. In case of 1+1 HSB-EPS. e. • Restoration Criteria: it defines if automatic restoration from protecting to protected channel • • The Core-E protection type is Not-Revertive and cannot be changed. The parameters are: • Protection Type: this parameter is defined at creation time and it is read only. Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 136 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 1 · Page 137 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 1 · Page 138 .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 Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

048 MHz to 1. clause 13.812).Notes: The physical interfaces to be assigned to Primary and Secondary synchronization sources can be chosen among the following: [1] Free Run Local Oscillator. sine-wave. „ c) 10 MHz. + 6 dBm into 50 ohm. „ b) 5 MHz. When the SSM support is enabled the QL and QL Priority are acquired from ESMC PDUs received on the specific radio interface. Default value for Quality Level is QL-SSU-A (G. the value of QL Priority is Master1 if the NEC is configured as Master and Slave1 if the NEC is configured as Slave. sine-wave. electrical levels according to G. „ d) 1. [3] A specific synchronization signal available from the dedicated Sync-In port.024 MHz. electrical levels according to G.703.812/G8262).703. { [4] The Symbol Rate of the RX signal of any available Radio (the specific Radio Port has to be chosen). [2] Any E1 available at input traffic interfaces (the specific E1 port has to be chosen).048 MHz. Copyright © 2012 Alcatel-Lucent. Quality Level value is fixed to QL-SEC/EEC1 (G. which can be configured according the following options: „ a) 2. Edition 2 Section 3 · Module 1 · Page 139 . All Rights Reserved. clause 13 with the following exceptions: timing properly scaled from 2. + 6 dBm into 50 ohm.024 MHz.

Notes: The physical interfaces to be assigned to Primary and Secondary synchronization sources can be chosen 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 User Ethernet port has to be chosen). Copyright © 2012 Alcatel-Lucent. [7] None of the above. [6] Any STM1 available at SDH input traffic interfaces (the specific STM1 port must be selected). Edition 2 Section 3 · Module 1 · Page 140 . this means that no physical synchronization interface is assigned to the synchronization clock source input. All Rights Reserved. In case of failure of the other clock source input the CRU enters the Holdover state.

it cannot be selected as Secondary too. The NEC has to be defined (configured) as Master or Slave. All Rights Reserved. • If an E1/T1 is chosen to be Primary source. another MPT radio interface connected to the same MPT Access peripheral cannot be selected as Secondary source and vice-versa. another STM1 coming from the same peripheral Copyright © 2012 Alcatel-Lucent. • If a specific interface is chosen as Primary. cannot be selected as Secondary source and vice-versa. another E1/T1 coming from the same peripheral cannot be selected as Secondary source and vice-versa. • If an STM1 is chosen to be Primary source. Edition 2 Section 3 · Module 1 · Page 141 . • If an MPT radio interface is chosen to be Primary source.Notes: Some rules have to be followed while assigning the Primary and Secondary clock sources.

2). 6) or 7). If the selected Master Primary clock source input is 2). If Master: • The Restoration Mode must be chosen between Revertive and Non-Revertive. 6) or 7). If the selected Master Primary clock source input is 1: • the Master Secondary clock source input doesn't need to be selected because the Primary is never supposed to fail. If Slave: • The Restoration Mode is fixed to Revertive. Edition 2 Section 3 · Module 1 · Page 142 . • The Primary clock source input must be chosen among 3). 2). 3). 4). 5) or 6). Slave Primary clock source input is allowed to be 3) or 5) for full indoor configuration and for Piling configuration. 5). 5). 3). 3). 2).Notes: • • Only one Master is allowed in the network. 4) or 5). All Rights Reserved. • • Copyright © 2012 Alcatel-Lucent. • The Primary clock source input must be chosen among 1). • The Secondary clock source input must be chosen among 1). 5) or 6): • the Master Secondary clock source input must be selected among 1). 3).

Edition 2 Section 3 · Module 1 · Page 143 . Copyright © 2012 Alcatel-Lucent. which shows the SSM status (enabled/disabled) of the interfaces carrying the SSM messages. All Rights Reserved.Notes: By pressing the SSM Summary button the SSM summary Table opens.

Edition 2 Section 3 · Module 1 · Page 144 . All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 145 .

This menu is shown in the figure above. All Rights Reserved. • • This menu (available in the Main view) contains a summary table for all the implemented crossconnections. In the Resource Detail Area are available two different functions usable to export and save crossconnections data with different formats: • hardcopy (Send To Printer). Edition 2 Section 3 · Module 1 · Page 146 . In the Resource Detail Area are available two different functions usable to export and save crossconnections data with different formats: • hardcopy (Send To Printer). • file (Export To File). Copyright © 2012 Alcatel-Lucent.Notes: • • This menu (available in the Main view) contains a summary table for all the implemented crossconnections. This menu is shown in the figure above. • file (Export To File).

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 147 .

Edition 2 Section 3 · Module 1 · Page 148 .Notes: This is another method of monitoring alarms. Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 3 · Module 1 · Page 149 . All Rights Reserved.Notes: Your 9500 MPR username and password Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 1 · Page 150 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 151 .

All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 152 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 153 .

All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 154 .Copyright © 2012 Alcatel-Lucent.

Notes: • Dynamic Host Configuration Protocol (DHCP) is a client/server protocol that automatically provides an Internet Protocol (IP) host with its IP address and other related configuration information such as the subnet mask and default gateway. Edition 2 Section 3 · Module 1 · Page 155 . Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 156 .

Notes: • • The Community String (CS) acts like a password to control access to an NE. It defines what community of people can access the NE. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 157 . 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 NEtO session currently active. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 1 · Page 158 .

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 159 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 1 · Page 160 . All Rights Reserved.

Edition 2 Section 3 · Module 2 · Page 1 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

This page is left blank intentionally Document History Edition 3. Edition 2 Section 3 · Module 2 · Page 2 .4 4.0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition First edition Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 3 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 4 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.1Q Copyright © 2012 Alcatel-Lucent.2 EAS/P8ETH Ethernet Ports 9.1 Provision MPTACC 7 PDH Access Card Views and Settings 7.4 Channel area 5 Radio Measurements Tab 5.4 MOD300 Settings .1 Equipment View .QoS Classification 12 LAG Configuration 12.3 Channel area 3.1 QoS Configuration .1 Equipment View .Page 1 Configuration View 1.Channel area 3 MPT-HC Views and Settings 3.2 Port Rate Limiter Ingress or Egress 9.2 ERP Configuration Procedure 10.3. EAS.1 Storm Control Ingress 9.6 TMN In-band 9.3 MOD300 Settings .1 Direction area 4.1 Configuration View screen 2 ODU300 Views and Settings 2.QoS Classification 11.1 Provision Plug-In Cards 9 Ethernet Ports Configuration 9.3 Advanced Ethernet functions for Core-E.4 Per-VLAN-Per-CoS Rate Limiter 9.1 Ethernet Ring Protection (ERP) overview 10.5 TMN Interface 9.1 LAG Creation Rules 12.Radio Modem 3.2 MOD300 Settings .2 Provision Plug-In Cards 8 SDH Access Card Views and Settings 8.2 Direction area 3.3.802.3 LAG Removal 13 XPIC Configuration 13.3 QoS Configuration . and PETH 9.4 C-VLAN Translation 9.Direction area 2. Edition 2 Section 3 · Module 2 · Page 5 7 8 11 12 13 16 17 19 20 21 28 32 33 34 39 41 42 43 44 48 49 50 57 58 59 63 64 69 70 71 72 73 74 75 76 77 82 83 84 87 88 89 97 99 100 101 105 111 112 113 117 119 120 127 128 .2 LAG Creation 12.1 Provision Plug-In Cards 7.3.2 How to read a Power Measurement file 6 MPTACC Settings 6.Queue Size Configuration 11.1 Radio Modem Power Measurements Graphic 5.2 QoS Configuration .4 Power Source 4 MPT-MC Views and Settings 4.Radio Modem 2.1 VLAN Configuration .7 TMN Ethernet port 10 Ethernet Ring Configuration 10.3 Configuration example of an Ethernet ring 11 QoS Configuration 11.1 XPIC Configuration 14 VLAN Configuration 14.3.3 Channel area 4.Direction area 2.1 CSM-E/Core-E Ethernet Ports 9.2 Channel area 4.3 VLAN Rate Limiter Ingress 9.

Ethernet Ring 130 Copyright © 2012 Alcatel-Lucent.Page 14. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 6 .2 VLAN Configuration .

Edition 2 Section 3 · Module 2 · Page 7 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.Notes: The Current Configuration View contains configuration information that is organized into the following 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 • Cross Connections • Ring • Bridge • Synchronization • Software Package Status Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 8 .

The File menu supports the following: • • • Save As – Save the configuration view as a text file. Edition 2 Section 3 · Module 2 · Page 9 . Exit – Close the Configuration View screen. Copyright © 2012 Alcatel-Lucent. Print – Send a copy of the configuration view to a printer. All Rights Reserved.

Edition 2 Section 3 · Module 2 · Page 10 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 11 .

Edition 2 Section 3 · Module 2 · Page 12 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 2 · Page 13 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 3 · Module 2 · Page 14 . Copyright © 2012 Alcatel-Lucent. All Rights Reserved.Notes: • The operation mode can be without or with the Adaptive Modulation.

Note: If the current Modulation scheme is 4 QAM.Notes: • The main idea behind Adaptive Modulation in Point to Point system is to adjust adaptively the modulation as well as a range of other system parameters based on the near-instantaneous channel quality information perceived by the receiver. Also if the current Modulation is 64 QAM. to pass to 4 QAM first must be forced to 16 QAM and then to 4 QAM. • • • • • Copyright © 2012 Alcatel-Lucent. All Rights Reserved. but first must be forced to 16 QAM and then to 64 QAM. The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB) without ATPC. The switching between the modulation schemes is hitless and maintains the same RF channel bandwidth. it not possible to force to 64 QAM. 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. it is possible to increase or decrease the part of the screen relevant to the parameters of the Adaptive Modulation. Warning: with the up and down arrows. below the Forced Modulation field. Edition 2 Section 3 · Module 2 · Page 15 . which is fed back to the transmitter with the aid of a feedback channel.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Through the “PPP-RF” interface the NE can exchange management messages with a remote OS (or Craft Terminal) station. 4) PPP RF The “PPP-RF” interface is a communication interface based on the use of an inframe RF proprietary 64 kbit/s channel. Edition 2 Section 3 · Module 2 · Page 16 . if necessary. 6) Synchronization Tick on Enable to enable the transmission of the SSM message over the radio channel. 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: z Expected z Sent Identifier: this field is the link identifier expected at the receiving NE Identifier: this field is the link identifier inserted on the transmitting NE (range: 1-256). The PPP-RF channel can be Enabled or Disabled. 5) Alarm Profile Not implemented in the current release. modify them.Notes: 3) Link Identifier This part allows the operator to define the expected and sent identifier values of parameters related to the link management and.

3) Manual Transmit Power Control Manual Transmit Power Control (without Adaptive Modulation) . The Data Help table is useful. shifter and Tx frequency will appear.Notes: 1) Frequency . Press the Data Help button the list of all the available ODUs with the relevant P/N. In the Shifter field select the suitable shifter. In the Tx frequency field insert the suitable Tx frequency and press Apply. if you are not connected to the ODU. In this field the operator has to enter the constant power. which will be used with 4 QAM modulation. Tick the Show details check box to see the severity associated to each alarm.If the ATPC is disabled the manual Tx Power field is present. If the ATPC has been enabled. the ATPC Range and ATPC Rx Threshold parameters must be filled.The operator can modify only the 4 QAM field.By clicking on the icon the Alarm Severity Profile menu opens.The information related to the transmitter status is shown in the Tx Mute field (Off/Manual/Auto). Tx Power (with Adaptive Modulation) .The system can operate with different types of ODU according to the RF band and to the channel arrangement. All Rights Reserved. 5) Alarm Profile . Edition 2 Section 3 · Module 2 · Page 17 . 4) Tx Mute . which allows to associate to the radio channel a specific alarm profile. Copyright © 2012 Alcatel-Lucent. Select one Alarm Profile in the Profile Name list (4 alarm profiles are listed) and click Apply. To squelch the transmitter select Enable and press Apply button. For the Tx Power range refer to the table. 2) ATPC The ATPC can be Enabled or Disabled. The new value will be applied when the Apply button is pressed.

Edition 2 Section 3 · Module 2 · Page 18 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 3 · Module 2 · Page 19 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 20 . All Rights Reserved.

All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 21 .Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent.Notes: • • The operation mode can be without or with the Adaptive Modulation. The SDH capacity mask must be selected in the following two profiles: CS (MHz) 28 56 z In z In FCM Mode Modulation 128QAM 128QAM # E1 TDM2TDM 72 145 # STM-1 SDH2SDH 1 2 the first case 1xSTM-1 or 72 E1s can be transmitted. the second case 2xSTM-1 or 145 E1s can be transmitted. Edition 2 Section 3 · Module 2 · Page 22 . All Rights Reserved.

the second case 2xSTM-1 or 145 E1s can be transmitted. All Rights Reserved. it not possible to force to 64 QAM. Edition 2 Section 3 · Module 2 · Page 23 . • The SDH capacity mask must be selected in the following two profiles: CS (MHz) 28 56 z In z In FCM Mode Modulation 128QAM 128QAM # E1 TDM2TDM 72 145 # STM-1 SDH2SDH 1 2 the first case 1xSTM-1 or 72 E1s can be transmitted. Warning: with the up and down arrows. to pass to 4 QAM first must be forced to 16 QAM and then to 4 QAM. Note: The Remote Switching Threshold is not supported. Note: If the current Modulation scheme is 4 QAM.Notes: • Adaptive Modulation in a Point to Point system adjusts the modulation as well as a range of other system parameters based on the near-instantaneous channel quality information perceived by the receiver. it is possible to increase or decrease the part of the screen relevant to the parameters of the Adaptive Modulation. but first must be forced to 16 QAM and then to 64 QAM. Copyright © 2012 Alcatel-Lucent. • The switching between the modulation schemes is hitless and maintains the same RF channel bandwidth. below the Forced Modulation field. • Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB/1+1 FD) Radio configuration without ATPC). which is fed back to the transmitter with the aid of a feedback channel. Also if the current Modulation is 64 QAM.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 24 . All Rights Reserved.

All Rights Reserved.Notes: Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 25 .

4. In the Polarization field select the polarization to be used by the radio channel (Vertical or Horizontal). Note: The XPIC can be implemented in 1+0 or 1+1 HSB with the Static Modulation or Adaptive Modulation.Notes: • • • This field is available only with the MPT-HC V2 with the XPIC+RPS external module installed and if in the Mode area in the Option field a mask with XPIC has been selected. By clicking on the icon on the right of the Associated Interface field you can navigate to the associated radio channel menu. Copyright © 2012 Alcatel-Lucent. Go in the XPIC Configuration menu by clicking the relevant button in the Tool bar. Now in the Associated Interface field will appear the radio channel associated in the XPIC Configuration. 2. How to configure the XPIC 1. 3. Refer to XPIC Configuration. Edition 2 Section 3 · Module 2 · Page 26 . All Rights Reserved.

7) Synchronization Tick on Enable to enable the transmission of the SSM message over the radio channel. 5) PPP RF The “PPP-RF” interface is a communication interface based on the use of an inframe RF proprietary 64 kbit/s channel. All Rights Reserved. modify them. Edition 2 Section 3 · Module 2 · Page 27 . In the Routing IP Protocol field enter the used IP protocol and in case of OSPF protocol select also the associated OSPF area.Notes: 4) Link Identifier This part allows the operator to define the expected and sent identifier values of parameters related to the link management and. Through the “PPP-RF” interface the NE can exchange management messages with a remote OS (or Craft Terminal) station. The operator choices will be sent to the NE by clicking on the related “Apply” button. If enabled. 6) Alarm Profile Not implemented in the current release. if necessary. The PPP-RF channel can be Enabled or Disabled. in the Remote Address field will appear the IP address of the remote connected NE. 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). Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Notes: • The Channel #1 area is always present (in 1+0 and 1+1 configuration). The Channel #0 area is present in 1+1 configuration only. Edition 2 Section 3 · Module 2 · Page 28 . Warning: To configure the unit first configure the Shifter and the Tx Frequency in the Frequency field (in the Channel menu) and click on Apply. Copyright © 2012 Alcatel-Lucent. Then configure all the other parameters.

All Rights Reserved. • When the Apply button is pressed the new values will be applied.Notes: 1) Frequency The system can operate with different types of ODU according to the RF band and to the channel arrangement. Copyright © 2012 Alcatel-Lucent. but this frequency can be changed in +5 MHz range to implement the “Exotic” shifter configuration. In the Rx frequency field will appear the calculated Rx frequency. Change the Rx frequency and press Apply. regarding the Tx Range in the ATPC management. In the Shifter field select the suitable shifter. If the ATPC has been enabled. 2) ATPC The ATPC can be Enabled or Disabled. In the Tx frequency field insert the suitable Tx frequency (the Rx frequency is automatically calculated by using the inserted Tx frequency and the shifter) and press push-button Apply. When the Rx power is equal to this power the ATPC algorithm starts to operate. The new value will be applied when the Apply button is pressed. if required. Edition 2 Section 3 · Module 2 · Page 29 . •ATPC Rx Threshold • The value of the low power threshold can be changed by writing the new value in the field. the ATPC Range and ATPC Rx Threshold parameters must be filled. can be written in the relevant field. There are ODUs which can manage only one shifter or several predefined shifters. ATPC Range • The Min Tx power and Max Tx power. • When the Apply button is pressed the new values will be applied.

5) MSE Driving Criteria Select in the MSE Driving Criteria field the suitable value. 4) RSL Driving Criteria Select in the RSL Driving Criteria field the suitable value. which will be used with the lowest modulation.Notes: • The same power value will be used by the other modulation schemes 3) Manual Transmit Power Control Manual Transmit Power Control (without Adaptive Modulation) • If the ATPC is disabled the manual Tx Power field is present. Copyright © 2012 Alcatel-Lucent. • In this field write the new value within the allowed transmitted power range. In 1+1 FD and HSB configurations both the transmitters can be driven by the lowest (1) or by the highest MSE values (2) of the two remote demodulators. In 1+1 FD and HSB configurations both the transmitters can be driven by the lowest or by the highest RSL values of the two remote demodulators. In this field the operator has to enter the constant power. For the Tx Power range refer to the table. Edition 2 Section 3 · Module 2 · Page 30 . The range is shown on the right side of Manual Transmit Power Control area. All Rights Reserved. Tx Power (with Adaptive Modulation) • The operator can modify only the Tx power relevant to the lowest modulation scheme.

Copyright © 2012 Alcatel-Lucent.Notes: 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. Edition 2 Section 3 · Module 2 · Page 31 . which allows to associate to the radio channel a specific alarm profile. All Rights Reserved. Tick the Show details check box to see the severity associated to each alarm. The following indications will appear in the Tx Mute field: z Off: Transmitter not squelch Transmitter squelched due to the manual operation Transmitter squelched due to an automatic operation z Manual: z Auto: 7) Alarm Profile By clicking on the icon the Alarm Severity Profile menu opens. Select one Alarm Profile in the Profile Name list (4 alarm profiles are listed) and click Apply.

Notes: • • • • Two Sources are available because the MPT Access unit can interface two MPT. All Rights Reserved. • Mode 1 . In this mode the MPT-HC is power supplied with a dedicated coaxial cable connected on the QMA connector on the front panel of the MPT Access unit Mode 2 . The Alarm Profile field is not supported.QMA (MPT-HC only) • • • This mode is the default mode. After the power supply selection click on Apply. Edition 2 Section 3 · Module 2 · Page 32 . If the Type is Disabled no power supply is provided to the MPT. Warning: An MPT-MC or an MPT-HC V2 can be connected to an external Power Injector Box which adds the Power Supply and the Ethernet Traffic on the same cable.PFoE (Power Feed on Ethernet) • In this mode the MPT-HC or MPT-MC are power supplied by using the electrical Ethernet cable. Copyright © 2012 Alcatel-Lucent. In this case the Power Source Type must be Disabled.

Edition 2 Section 3 · Module 2 · Page 33 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 3 · Module 2 · Page 34 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Notes: • • The operation mode can be without or with the Adaptive Modulation. Note: The SDH capacity mask must be selected in the following profile: CS (MHz) 28 z In FCM Mode Modulation 128QAM # E1 TDM2TDM 72 # STM-1 SDH2SDH 1 the first case 1xSTM-1 or 72 E1s can be transmitted. Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 35 .

The Remote Switching Threshold is not supported. The switching between the modulation schemes is hitless and maintains the same RF channel bandwidth. it not possible to force to 64 QAM. The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB/1+1 FD) Radio configuration without ATPC). below the Forced Modulation field. Also if the current Modulation is 64 QAM. Warning: with the up and down arrows. Example: if the current Modulation scheme is 4 QAM. All Rights Reserved. but first must be forced to 16 QAM and then to 64 QAM. • • • In 1+1 configuration the Driving MSE field is not supported. Copyright © 2012 Alcatel-Lucent. it is possible to increase or decrease the part of the screen relevant to the parameters of the Adaptive Modulation. which is fed back to the transmitter with the aid of a feedback channel. Note: The SDH capacity mask must be selected in the following profile: CS (MHz) 28 56 z In FCM Mode Modulation 128QAM 128QAM # E1 TDM2TDM 72 145 # STM-1 SDH2SDH 1 2 the first case 1xSTM-1 or 72 E1s can be transmitted.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 perceived by the receiver. to pass to 4 QAM first must be forced to 16 QAM and then to 4 QAM. Edition 2 Section 3 · Module 2 · Page 36 .

Edition 2 Section 3 · Module 2 · Page 37 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

6) Alarm Profile . If enabled. 4) Link Identifier This part allows the operator to define the expected and sent identifier values of parameters related to the link management and. The PPP-RF channel can be Enabled or Disabled. 5) PPP RF The “PPP-RF” interface is a communication interface based on the use of an inframe RF proprietary 64 kbit/s channel. 7) Synchronization Click on Enable to enable the transmission of the SSM message over the radio channel. All Rights Reserved. in the Remote Address field will appear the IP address of the remote connected NE. Copyright © 2012 Alcatel-Lucent. if necessary. The operator choices will be sent to the NE by clicking on the related “Apply” button.Notes: 3) XPIC Configuration .Not implemented in the current release. If the Link Identifier is Enabled the following fields can be written: z Expected z Sent Identifier: this field is the link identifier expected at the receiving NE Identifier: this field is the link identifier inserted on the transmitting NE (range: 0-256).Not available with the MPT-MC. Through the “PPP-RF” interface the NE can exchange management messages with a remote OS (or Craft Terminal) station. Edition 2 Section 3 · Module 2 · Page 38 . In the Routing IP Protocol field enter the used IP protocol and in case of OSPF protocol select also the associated OSPF area. modify them.

Notes: • The Channel #1 area is always present (in 1+0 and 1+1 configuration). Copyright © 2012 Alcatel-Lucent. The Channel #0 area is present in 1+1 configuration only. Warning: To configure the unit first configure the Shifter and the Tx Frequency in the Frequency field (in the Channel menu) and click on Apply. Edition 2 Section 3 · Module 2 · Page 39 . All Rights Reserved. Then configure all the other parameters.

All Rights Reserved. Copyright © 2012 Alcatel-Lucent. In the Rx frequency field will appear the calculated Rx frequency. Edition 2 Section 3 · Module 2 · Page 40 . ATPC Range • The Min Tx power and Max Tx power. can be written in the relevant field. but this frequency can be changed in +5 MHz range to implement the “Exotic” shifter configuration.Notes: Warning: To configure the unit first configure the Shifter and the Tx Frequency in the Frequency field (in the Channel menu) and click Apply. regarding the Tx Range in the ATPC management. ipress Apply. 2) ATPC The ATPC can be Enabled or Disabled. In the Tx frequency field insert the suitable Tx frequency (the Rx frequency is automatically calculated by using the inserted Tx frequency and the shifter) and press push-button Apply. When the Rx power is equal to this power the ATPC algorithm starts to operate. • When the Apply button is pressed the new values will be applied. • When the Apply button is pressed the new values will be applied. The new value will be applied when the Apply button is pressed. If the ATPC has been enabled. Then configure all the other parameters. ATPC Rx Threshold • The value of the low power threshold can be changed by writing the new value in the field. the ATPC Range and ATPC Rx Threshold parameters must be filled. 1) Frequency The system operate with different types of ODUs according to the RF band and channels.

In 1+1 FD and HSB configurations both the transmitters can be driven by the lowest or by the highest RSL values of the two remote demodulators. which will be used with the lowest modulation.Notes: Warning: To configure the unit first configure the Shifter and the Tx Frequency in the Frequency field (in the Channel menu) and click on Apply. 4) RSL Driving Criteria Select in the RSL Driving Criteria field the suitable value. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. • In this field write the new value within the allowed transmitted power range. Then configure all the other parameters. The range is shown on the right side of Manual Transmit Power Control area. 3) Manual Transmit Power Control Manual Transmit Power Control (without Adaptive Modulation) • If the ATPC is disabled the manual Tx Power field is present. For the Tx Power range refer to the table. Tx Power (with Adaptive Modulation) The operator can modify only the Tx power relevant to the lowest modulation scheme. Edition 2 Section 3 · Module 2 · Page 41 . In this field the operator has to enter the constant power.

All Rights Reserved. Click Show details check box to see the severity associated to each alarm. Edition 2 Section 3 · Module 2 · Page 42 . Copyright © 2012 Alcatel-Lucent. Select one Alarm Profile in the Profile Name list (4 alarm profiles are listed) and click Apply. 6) Tx Mute The information related to the transmitter status is shown in the Tx Mute field (Off/Manual/Auto). 5) MSE Driving Criteria Select in the MSE Driving Criteria field the suitable value. In 1+1 FD and HSB configurations both the transmitters can be driven by the lowest (1) or by the highest MSE values (2) of the two remote demodulators.Notes: Warning: To configure the unit first configure the Shifter and the Tx Frequency in the Frequency field (in the Channel menu) and click on Apply. 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. Then configure all the other parameters. which allows to associate to the radio channel a specific alarm profile.

Edition 2 Section 3 · Module 2 · Page 43 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

The choice is among 2. Edition 2 Section 3 · Module 2 · Page 44 . • The log file contains the sample value and records the measurement up to a maximum dimension (7 days for a 2 s sample time). The last section of the dialog is referred to an optional Log file.08 directory. 4. 60 sec. All Rights Reserved. Minutes: 0.07. A 7-day measurement interval is also the maximum allowed interval.Notes: • • "Measurement interval" fields . Copyright © 2012 Alcatel-Lucent. Hours: 0. By selecting Create File the log file is created and a default path and name for this file is displayed to the operator. 6.The default is Days: 7. 30. The file is stored in the MPRE_CT_V00. "Sample time" field . • The file name must not include the following characters: \ ? : * “ < > |.

The operator can see. for example. if the local TX is blue. Note that the colors represent the linked end-point of the two NE. • The Power Measurement Graphic screen shows the Tx and Rx measurements related to the local and remote NE. the power transmitted by the local and remote transmitter (Tx) and the power received by the local and remote receiver (Rx). The top graphic screen area shows the TX curves (local and remote). Edition 2 Section 3 · Module 2 · Page 45 . • Copyright © 2012 Alcatel-Lucent. All Rights Reserved. the remote receiver will also have the same color. • The Power Measurement Graphic is available only if the WebEML is connected to the NE. while the bottom area shows the Rx curves (local and remote). in real time.Notes: By clicking on the "Start" button the screen "Power Measurement Graphic" appears.

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. Copyright © 2012 Alcatel-Lucent. All Rights Reserved. added to the start time • Time: is the current response time • Log File: is the complete pathname of the file where the received values are stored. Edition 2 Section 3 · Module 2 · Page 46 .

Card Missing. • In case of failure on reading the register containing the received power the value shown at management system is 99. All Rights Reserved. • In case of alarms on the remote NE on one of the two radio channels in HSB configuration (typically ICP. Card Fail).7 dBm.8 dBm. Card Missing.7 dBm. • In case of mute status the value shown at management system is -100 dBm. • Radio analog received power level (local ODU) • In case of ICP or Cable Loss alarms the value shown at management system is -99. WARNING: • Radio analog transmitted power level (local ODU) • In case of ICP or Cable Loss alarms the value shown at management system is -99. • If the power level read is out of the allowed range. the value shown by the management system is -101 dBm. Copyright © 2012 Alcatel-Lucent. • In case of mute status the value shown at management system is -100 dBm. Card Fail).6 dBm.7 dBm. the value shown by the management system is -127 dBm.8 dBm. I • f the power level read is out of the allowed range. the value shown by the management system is -101 dBm. Cable Loss. RSL value is not set to a fixed specific value.Notes: • When not receiving any signal. • Radio analog received power level (remote ODU) • In case of failure on reading the register containing the remote received power the value shown at management system is -99. the value shown by the management system is -101 dBm. the value shown by the management system is -127 dBm. In case of alarms on the remote NE on one of the two radio channels in HSB configuration (typically ICP. the value shown by the management system is -101 dBm. In case of failure on reading the register containing the remote transmitted power the value shown at management system is -99. • If the power level read is out of the allowed range. • Radio analog transmitted power level (remote ODU) • In case of broken radio link the value shown at management system is -99. • If the power level read is out of the allowed range. Cable Loss. Edition 2 Section 3 · Module 2 · Page 47 .

WordPad). Click button Start (on the right side of the Sample Time field). • • As default the measurement files are stored in the MPRE_CT_Vxx.xx directory and have extension . The measurements are shown in the tabular mode.g. Click the Read File box and press the Select File button. 2.xx.Notes: 1. The buttons in the lower part of the window allow to flow the graph within the measurement interval. The measurement file can be opened also with a standard text editor (e. The selected file will appear in the Log file field. The directory of the WebEML automatically opens to navigate to the power measurement file. Edition 2 Section 3 · Module 2 · Page 48 . Copyright © 2012 Alcatel-Lucent. All Rights Reserved. 3.txt. Select the desired file and click the Open. The file opens. Go in the directory where the txt files have been stored and open the file.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 49 .

All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 50 .Copyright © 2012 Alcatel-Lucent.

remove the power supply. unprovision the MPT 3. Copyright © 2012 Alcatel-Lucent. perform a Tx Mute 2. All Rights Reserved.Notes: To unprovision an MPT: 1. Edition 2 Section 3 · Module 2 · Page 51 .

Select the suitable Polarization: Vertical or Horizontal. All Rights Reserved. NOT ALL the channel spacings and modulation schemes can support the XPIC Configuration. Copyright © 2012 Alcatel-Lucent. The XPIC can be configured in 1+0 or 1+1 HSB (no adaptive modulation. no ATPC).Notes: • • • • With the Presetting mode the Adaptive modulation is disabled. Edition 2 Section 3 · Module 2 · Page 52 . This field is available only with the MPT-HC V2 with the XPIC+RPS external module installed and if in the Mode area in the Option field a mask with XPIC has been selected.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 53 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 54 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 55 .

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 56 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 57 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 58 . All Rights Reserved.

Loss of E1 data can occur. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 59 .Notes: Flow Id number: is system unique and must not be repeated in radio network.

Notes: Flow Id number: is system unique and must not be repeated in radio network. Edition 2 Section 3 · Module 2 · Page 60 . Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Loss of E1 data can occur.

Edition 2 Section 3 · Module 2 · Page 61 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 62 .

Edition 2 Section 3 · Module 2 · Page 63 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 2 · Page 64 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Notes: • Flow ID number is system unique and must not be repeated in radio network. no Regeneration section Termination is done. • J0 byte is only read. Edition 2 Section 3 · Module 2 · Page 65 . Loss of STM-1 data can occur. Copyright © 2012 Alcatel-Lucent. • Auto LASER Shutdown . All Rights Reserved.This field will appear only if the Settings tab-panel of the STM-1 unit the optical SFP has been selected.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 66 . All Rights Reserved.

Note: byte J0 is only read. if required. [5] Enable the J0. By enabling the Node Timing the E1 streams in Rx side are retimed at the output with the network element clock.Notes: [2] Put a check mark in the Port Status box to enable the STM-1. The Node Timing is the timing from the network clock as defined in G. [4] Select the Clock Source. All Rights Reserved. the E1 Node Timing Configuration. Copyright © 2012 Alcatel-Lucent. This field will appear only if the Settings tab-panel of the STM-1 unit the optical SFP has been selected. [6] Click Apply. [3] Set the Auto Laser Shutdown: Enabled/Disabled ForcedOn/Disabled ForcedOff. 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 the Sending J0 field select one of the two modes and enter the value to be transmitted. no Regeneration section Termination is done. Edition 2 Section 3 · Module 2 · Page 67 . [7] Enable. The enabling of the Node Timing is applied to all E1s of the unit.8261.

Notes: [8] Configure all the E1s to be mapped/demapped in the STM-1. ECID Rx. All Rights Reserved. [14] Fields ECID Tx. Note: The service profile must be the same for all the E1s. [10] Signal Mode: The possible values are: z Unframed for the unframed received signal z Framed for the collection of the performances at the input in Tx side and at the output in Rx side z Disabled [11] Click Apply. The E1s are identified by a progressive number from #1 to #63. The E1 tab-panel performs all available functions for the tributary. [12] Service Profile: The possible profiles are: z TDM2TDM z TDM2Eth [13] Flow Id: To implement cross-connections between line side and radio side each E1 tributary must be associated to an identifier. Enter the Flow identifier value in the relevant field (possible values: 2 to 4080) and press Apply. [9] Select Settings. Payload Size and TDM Clock Source can be written only if the Service Profile is TDM2Eth. Copyright © 2012 Alcatel-Lucent. [15] Alarm profile: Not implemented now. [16] Click Apply. Edition 2 Section 3 · Module 2 · Page 68 . but also by the standard SDH identification (x-y-z).

Edition 2 Section 3 · Module 2 · Page 69 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

the Ethernet port must be set as Synch-E Slave. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 70 .Notes: If the electrical Ethernet port has to be used as Synchronous Source.

Edition 2 Section 3 · Module 2 · Page 71 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

VLAN based Rate Limiter allows a user to provision. VLAN Rate Limiter . • • • • • CIR can be configured in the range from 64 Kbit/s to 1. All Rights Reserved.supported on user Ethernet interfaces. Default is 100 Frame/s for all. Default value for CIR is 64 Kbit/s. Port based Rate Limiting allows a user to provision on a per user Ethernet port basis the maximum data rate on ingress and egress directions. Multicast. on a per VLAN ID basis. C-VLAN ID (To) are changed to C-VLAN ID (From) exiting the User Ethernet interface. C-VLAN ID (From). Edition 2 Section 3 · Module 2 · Page 72 .000 Kbit/s at step of 64 Kbit/s. multicast.Used on Ethernet interfaces for the ingress direction.Storm Control provides a mechanism to control the effects of broadcast.000. Port Based Rate Limiting . Storm Control (Broadcast. Tagged ingress frames entering the User Ethernet interface. and unknown unicast storms on physical user Ethernet interfaces. CBS (Committed Burst Size) can be configured in the range from 4 Kbytes (4096 bytes) to 16 MBytes at step of 4 Kbytes. This helps prevent traffic storms from being disruptive and degrading network performance.777.supported on user Ethernet interfaces. tagged egress frames. and unknown Unicast) . are changed to a new C-VLAN ID (To). default value for CBS is 12 Kbytes. the translation is applied bidirectional.215 Frames for all.Notes: • C-VLAN Translation . The frame rate threshold can be configured in the range from 1 Frame to 16. the maximum data rate for the ingress direction • Copyright © 2012 Alcatel-Lucent. At the same time.

All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 73 .Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 2 · Page 74 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 75 .Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 76 .

Edition 2 Section 3 · Module 2 · Page 77 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 78 .

1 Mbytes.Ethernet throughput not taking into account Preamble and IFG frames. 32 Kbytes.Notes: Per-VLAN-Per-CoS Rate limiter Parameters • Ingress CIR (Committed Information Rate) . Ingress CBS (Committed Burst Size) . Default value for CBS is 16 Kbytes. A value of 0 Kbit/s indicates a drop of the Ethernet flow. 16 Mbytes. Default value for CIR is 64 Kbit/s. 16 Kbytes. 512 Kbytes. 4 Mbytes. 8 Mbytes. 256 Kbytes. 8 Kbytes. 64 Kbytes. • Copyright © 2012 Alcatel-Lucent. The allowed values for CBS are: 4 Kbytes. Range is from 0 Kbit/s to 1 Gbit/s in steps of 64 Kbit/s. Edition 2 Section 3 · Module 2 · Page 79 . 128 Kbytes.CBS is configured in the range from 4 Kbytes (4096 bytes) to 16 MBytes. All Rights Reserved. 2 Mbytes.

the Per-VLAN Per-CoS Rate Limiter must apply to Ethernet frames that meet the Port Rate Limiter parameters. The allowed values for CBS are: 4 Kbytes. Default value for CIR is 64 Kbit/s. 2 Mbytes. 32 Kbytes. Default value for CBS is 16 Kbytes. 16 Kbytes. Per-VLAN-Per-CoS Rate limiter Parameters • Ingress CIR (Committed Information Rate) . Edition 2 Section 3 · Module 2 · Page 80 . 128 Kbytes. A value of 0 Kbit/s indicates a drop of the Ethernet flow. • Copyright © 2012 Alcatel-Lucent.CBS is configured in the range from 4 Kbytes (4096 bytes) to 16 MBytes. 1 Mbytes.Notes: Caution: Possibility of service interruption.Ethernet throughput not taking into account Preamble and IFG frames. Range is from 0 Kbit/s to 1 Gbit/s in steps of 64 Kbit/s. 512 Kbytes. When a Per-VLAN Per-CoS Rate Limiter is activated in conjunction with a Port Rate Limiter. 4 Mbytes. 8 Mbytes. 256 Kbytes. 16 Mbytes. 8 Kbytes. Ingress CBS (Committed Burst Size) . 64 Kbytes. All Rights Reserved.

Range is from 0 Kbit/s to 1 Gbit/s in steps of 64 Kbit/s. Ingress CBS (Committed Burst Size) . 8 Mbytes.Notes: Caution: Possibility of service interruption. The allowed values for CBS are: 4 Kbytes. 16 Mbytes. • Copyright © 2012 Alcatel-Lucent.Ethernet throughput not taking into account Preamble and IFG frames.CBS is configured in the range from 4 Kbytes (4096 bytes) to 16 MBytes. the Per-VLAN Per-CoS Rate Limiter must apply to Ethernet frames that meet the Port Rate Limiter parameters. 128 Kbytes. Default value for CIR is 64 Kbit/s. 256 Kbytes. A value of 0 Kbit/s indicates a drop of the Ethernet flow. When a Per-VLAN Per-CoS Rate Limiter is activated in conjunction with a Port Rate Limiter. 1 Mbytes. 2 Mbytes. 4 Mbytes. Per-VLAN-Per-CoS Rate limiter Parameters • Ingress CIR (Committed Information Rate) . All Rights Reserved. 8 Kbytes. 32 Kbytes. 64 Kbytes. Edition 2 Section 3 · Module 2 · Page 81 . 512 Kbytes. 16 Kbytes. Default value for CBS is 16 Kbytes.

Edition 2 Section 3 · Module 2 · Page 82 . All Rights Reserved.Notes: This tab-panel has 2 tab-panels: z Alarm tab-panel tab-panel z Settings Copyright © 2012 Alcatel-Lucent.

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. are segregated. configured in different TMN In-band logical interfaces. If two Ethernet ports. • If the TMN In-band interface has been configured and the traffic classifier is according to 802.0. each having its own IP address and subnet.3. • The delivery of TMN In-Band can be enabled on all User Ethernet interface of the Core board. If the traffic classifier is according to DiffServ.1p. the two ports do not communicate each other. as they have 2 different VLAN IDs).0. are segregated.2/24 for interface #1 and 10. associated to the same TMN In-band logical interface. • If two Ethernet ports.Notes: • The TMN In-Band feature allows the extension of the DCN over User Ethernet interfaces used to carry user traffic.0.4. • The OSPF and related Area ID can be enabled on a TMN In-Band interface.0 Copyright © 2012 Alcatel-Lucent. All Rights Reserved. • The Ethernet ports involved in a LAG cannot be used as TMN In-band interface. the priority on the TMN traffic is low and the traffic on the other Ethernet ports must be taken in consideration. both Optical and Electrical. • The TMN traffic delivered In-Band is VLAN tagged and identified by a specific VLAN ID defined by the operator in the range 2-4080. as for the normal Ethernet traffic (they have the same VLAN ID).0. • Two default TMN In-Band interfaces (TMN In-band #1 and #2) are supported. the two ports can communicate each other. • For each TMN In-Band interface the following parameters must be selected: • IP address and subnet: default 10. Edition 2 Section 3 · Module 2 · Page 83 . the priority on the TMN traffic is highest.

Select one Alarm Profile in the Profile Name list (4 alarm profiles are listed). • Click on the Alarm Profile icon to open the Alarm Severity Profile menu to associate to the TMN Ethernet port a specific alarm profile.Notes: • If used. the TMN Ethernet must be: • Enabled. Tick the Show details check box to see the severity associated to each alarm. Copyright © 2012 Alcatel-Lucent. If OSPF has been selected. • Click on Apply to activate the selections. • Assigned an IP address with its IP mask. • Selected the IP Routing Protocol: Static Routing or OSPF. assign also the area number. Edition 2 Section 3 · Module 2 · Page 84 . All Rights Reserved.

• Assigned an IP address with its IP mask. • Selected the IP Routing Protocol: Static Routing or OSPF. All Rights Reserved. assign also the area number. • Click on Apply to activate the selections. the port 4 must be: • Enabled. Edition 2 Section 3 · Module 2 · Page 85 . If OSPF has been selected.Notes: • If the Ethernet Port 4 has been used as TMN port. Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 86 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 87 .

the RPL Owner.Notes: • • One designated node. Edition 2 Section 3 · Module 2 · Page 88 . the RPL Owner is responsible to unblock the RPL. Under a ring failure condition. allowing the RPL to be used for traffic. is responsible to block traffic over the RPL. All Rights Reserved. Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 89 . All Rights Reserved.

The East Port and West Port must have the same type of ODU: ODU300 or MPT. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 90 .Notes: The Port can be associated only to ODU300 or MPT in 1+0. Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 91 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 92 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 93 .

Edition 2 Section 3 · Module 2 · Page 94 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 95 .

If VLAN Id 1 is not associated to any instances. a Warning will alert the operator in order to avoid traffic (if untagged) loop. After the operator clicks on Close button.Notes: • • All the parameters in “Runtime Parameters” Panel can be modified at run time (ERP Instance enabled). Copyright © 2012 Alcatel-Lucent. All Rights Reserved. the WebEML checks VLAN Id 1 association. Edition 2 Section 3 · Module 2 · Page 96 .

Edition 2 Section 3 · Module 2 · Page 97 . All Rights Reserved.Notes: • • In Figure is shown a simple example of an Ethernet ring. Copyright © 2012 Alcatel-Lucent. VLAN Id 100 and an E1/T1 stream (with Flow Id 500) are inserted in NE1 and extracted in NE4 and vice versa.

Edition 2 Section 3 · Module 2 · Page 98 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 99 .

Notes: • • For each queue and for each radio direction the buffer size (in Bytes) can be assigned. Press the Apply button to confirm the default values. 3. By buttons Copy and Paste the parameters of one Radio direction can be copied to another Radio direction. • • For each buffer size automatically is calculated the max delay in ms. Double click on the relevant field and enter the new value. Click on Restore to go back to the previous configuration. All Rights Reserved. 1. Click on Apply to send to the NE the changes. Click on Defaults to go back to the default settings. Copyright © 2012 Alcatel-Lucent. A tooltip on each field shows the current and default values of the queue size with relevant conversion in msec. 2. Edition 2 Section 3 · Module 2 · Page 100 . The Default button only shows the default values. 4. 5.

Edition 2 Section 3 · Module 2 · Page 101 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 102 .

All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 103 .Copyright © 2012 Alcatel-Lucent.

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.Notes: When the Default values are applied (by pressing button Defaults or manually by entering in the fields the default values). All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 104 . Copyright © 2012 Alcatel-Lucent. as shown in figure: for Direction 5. in Q3 the default value has been set. all the other queues have the default value.1. in Q4 the value is different from default.

Edition 2 Section 3 · Module 2 · Page 105 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

• then from the FC (Forwarding Class) to the Egress Queue (Q#): on the right area of the screen.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 the screen. • Click Apply. Then click Yes. Edition 2 Section 3 · Module 2 · Page 106 . All Rights Reserved. Copyright © 2012 Alcatel-Lucent. This association is fixed and cannot be changed.

Click on Defaults to go back to the default settings. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 107 . All Rights Reserved.Notes: • • • Click on Apply to send to the NE the changes. Click on Restore to go back to the previous configuration.

then from the FC (Forwarding Class) to the Egress Queue (Q#): on the right area of the screen. Then click Yes.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. Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 108 . Click on Apply. This association is fixed and cannot be changed.

Notes: • • • Click on Apply to send to the NE the changes. Edition 2 Section 3 · Module 2 · Page 109 . Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Click on Defaults to go back to the default settings. Click on Restore to go back to the previous configuration.

All Rights Reserved. as shown in the figure. Edition 2 Section 3 · Module 2 · Page 110 .Notes: Click the Table form button to open a read-only table with the current association "DiffServ to Forwarding Class Mapping". Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 111 .

All Rights Reserved. but it not possible to see the association of a specific User Ethernet port to a specific Ethernet LAG. letter L (followed by the number of the LAG) is placed on the ODU icon on the Equipment view (example: L01 means that the ODU has been associated to Radio LAG #01).Notes: Warning: the other port of the MPT Access unit must be DISABLED. • • To know if an ODU is grouped in a radio LAG. in the CORE-E domain in the Ethernet Physical Interface tab-panel the Settings tab-panel of the Ethernet port grouped in a LAG is gray (no changes can be done). To know if an Ethernet user port is grouped in an Ethernet LAG. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 112 .

By default L2 hashing is selected. After configuring the Link Aggregation Type. the user can change the hashing algorithm in order to select L2 (distribution of frames based on MAC header and VLAN Tag) or L3 (distribution of frames based on IP header). Click Create.Notes: 1.) Note: Link Aggregation Type is used to distinguish between Radio Link Aggregation an Ethernet Link Aggregation. Edition 2 Section 3 · Module 2 · Page 113 . The newly created LAG displays in the Configured LAG panel. 4. All Rights Reserved. Press the Create button. The LAG Creation window displays Enter the required information for one of the following LAG types (more detail and examples on next slide): „ „ „ L1 Radio L2 Radio L2 Ethernet 3. 2. Select the already created LAG to complete the configuration process (described on following slides. Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 2 · Page 114 . c.select LAG size (for L1 Radio (1-4). h. select timeout period ( Short or Long).If Type is L2 Ethernet. All Rights Reserved. or Disabled). then from the Timeout field. f.select (L1 Radio. L2 Radio.Enter the LAG name. b. or L2 Ethernet). e.select lag ID number (1-14).Notes: a.). then select Admin Key value ( 1-32). d. for L2 Ethernet/Radio (1-8)) Key drop-down menu . Type drop-down menu . LACP drop-down menu . g.If LACP Active or Passive.If Type is L2 Ethernet/Radio. Size drop-down menu . Click Create Copyright © 2012 Alcatel-Lucent. Name . ID drop-down menu . select LACP support (Active. Passive. Timeout . optional (up to 32 characters max.

5. Click the Enabled check box. Select the suitable port and click on the Right Arrow button to move the selected port in the Added Ports area. Edition 2 Section 3 · Module 2 · Page 115 .Notes: All of the configured ports display in the Available Ports area. Select the Hash algorithm (L2 or L3). 1. enable the PPP RF channel and select the OSPF Area. 4. Filter the list according to the ODU type: MPT or MD300. All Rights Reserved. 3. 2. If required. giving a detail information on the field as shown in next figure. By putting the mouse on a column a tooltip will appear. The PPP RF channel for TMN is managed here at LAG level and not at ODU level. • • Copyright © 2012 Alcatel-Lucent.

5. z The Priority values allowed are in the range 0 . For each port it is possible to configure: • Acceptable Frame Type: „ Admit tagged only (only tagged frames are allowed in ingress. If required. The default Port VLAN-ID and Priority values are: VLAN-ID=1. Edition 2 Section 3 · Module 2 · Page 116 . The priority packets (VLAN-ID=0) received on one user Ethernet port. while the Priority field is the same of the received packets.The untagged frames received on one user Ethernet port. z Copyright © 2012 Alcatel-Lucent. configured as “Admit tagged only”. 3. Select the Hash algorithm (L2 or L3). are managed as untagged frames for VLAN-ID field. All Rights Reserved. The traffic.The priority packets (VLAN-ID=0) received on one user Ethernet port. If required. Click the Enabled check box. are dropped. 1. „ Untagged frames .Notes: All of the configured ports display in the Available Ports area. configure the VLAN in the VLAN Configuration area. 2. the untagged frames are dropped) „ Admit all (tagged and untagged frames are allowed in ingress) Default value: “Admit all”. Port VLAN ID: if the Acceptable Frame Type is set to “Admit all” the VLAN-ID and Priority fields (to be added in ingress to untagged frames). must be configured. VLAN 1 is always removed when the frame is forwarded. change the priority of the port in the Priority column. Only VLAN-ID values already defined (in the VLAN management menu) can be configured for this purpose. received on the user Ethernet ports.7. are dropped. The VLAN configuration is at LAG level (not at port level). 4. can be untagged or tagged. with the “Admit all” configuration enabled. „ Priority frames . Select the suitable port and click on the Right Arrow button to move the selected port in the Added Ports area. Priority=0. configured as “Admit tagged only”.

Remove the ports associated to the LAG: select the ports in the " Added Ports" area. All Rights Reserved. 3. Remove the check on the Enabled check box in the LAG Information area (Radio LAG and Ethernet LAG). Segregations. Copyright © 2012 Alcatel-Lucent. 6. Edition 2 Section 3 · Module 2 · Page 117 . Click Apply. Remove all the Cross-connections. 5. Click Destroy. For Radio LAG remove the check on the Enabled check box in the PPP RF area. if any. 4. For Ethernet LAG. 2. VLANs associated to the LAG. go to Step 4.Notes: 1. press the Left Arrow button and click Apply.

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 118 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 119 .

All Rights Reserved. configure the 1+1 HSB protection between the two mate MPT-HC V2. 2. • Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 120 .Notes: • In the XPIC Configuration screen are shown in GREEN the MPT-HC V2 with a mask with XPIC set in the “Option” field (Allowed configurations: 1+0 or 1+1 HSB with or without Adaptive Modulation) previously configured in the Radio menu and with a suitable polarization (vertical or horizontal) as shown in the above figure. To configure the double 1+1 HSB co-channel XPIC follow the following steps: 1. configure the XPIC on the protection radio (in the MPT-HC V2 1+1 Main view configure properly the Option for XPIC profile).

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 121 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 122 . All Rights Reserved.

Notes: The radio channel associated in the XPIC configuration displays in the Radio menu in the Associated Interface. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 123 . Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 124 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 2 · Page 125 . All Rights Reserved.

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 126 .

Edition 2 Section 3 · Module 2 · Page 127 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

The VLAN cannot be removed from the radio ports (with the exception of the VLAN 1). Edition 2 Section 3 · Module 2 · Page 128 . All the user Ethernet ports and all the Radio directions can be considered. 3.Notes: 1. Only the user Ethernet ports. By default. VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.If one tagged packet with VLAN-ID X is received on a port which is not member of the VLAN-ID X. TDM2ETH) cannot be used. enabled and disabled. Untagged Ports field: Select. the packet is dropped. VLAN Ports field: Select the ports members of this VLAN by putting a check mark on the relevant check box. All Rights Reserved. TDM2TDM. • The VLAN-ID values allowed are in the range 2 . 2. VLAN ID field: Enter the VLAN ID (the configurable values must be in the range 2 . are manageable. • There is no check on unambiguity name. Copyright © 2012 Alcatel-Lucent. 4. • Tagged frames .4080. all the ports are members and the Untag flag is set to “False”.e. among the ports belonging to this VLAN (members).4080) • The VLAN IDs already defined to cross-connect internal flows (i. which means all the frames are transmitted with Tag. for the VLAN IDs defined. the untagged ports (in egress the VLAN will be removed from the frames).

All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 129 .Copyright © 2012 Alcatel-Lucent.

the VLAN ID of the R-APS relevant to the ERP Instances must be inserted in the VLAN Configuration as shown in the figure. All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 130 . Copyright © 2012 Alcatel-Lucent.Notes: • • If an Ethernet Ring has been created. The R-APS is AUTOMATICALLY inserted in the VLAN configuration.

All Rights Reserved. Edition 2 Section 3 · Module 2 · Page 131 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 2 · Page 132 Section 3 · Module 2 · Page 132 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 1 . All Rights Reserved.

4 4. All Rights Reserved.This page is left blank intentionally Document History Edition 3.0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition Updated for Release 4. Edition 2 Section 3 · Module 3 · Page 2 .0 Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 3 . All Rights Reserved.

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 4 .

7 SDH to Radio/MPTACC 3.5 PDH to Ethernet 2.9 Radio/MPTACC to Ethernet 2.4 SDH to Radio/MPTACC 3.2 Connections Tab with Ethernet Cross-Connection 8 Radio Cross-Connections 8. 5.1 TDM Cross-Connections 2.Ring 6. Edition 2 Section 3 · Module 3 · Page 5 .1 ATM Cross-Connections 4.1 SDH Cross-Connections with SDHACC 3.4 Pass-through 6.9 How to modify an SDH cross-con.2 SDH to Radio/MPTACC 3.Page 1 Cross-Connection Creation 1.4 Radio – Ethernet 4.2 CSM-E/Core-E Ethernet Port Segregation 9.3 Radio to Radio 3.3 How to modify a LAG-LAG cross-connection 6 Ring Cross-Connections 6.Ring 6.1 How to create a cross-connection 1.10 SDH to Radio/MPTACC 3.2 PDH to Radio/MPTACC 2.2 Radio LAG .3 Radio to Radio 2.1 Port Segregation 9.8 PDH to SDH 3.6 Cross-Connections with TDM2Eth Profile 2.2 Radio – Ring 6.11 PDH to SDH 4 ATM Cross-Connections 4.5 ASAP – Ethernet 4.1 Ethernet Cross-Connections 7.1 Radio to Radio Cross-Connections 9 Port Segregation 9.4 Configuration 7 8 10 11 12 13 15 17 20 22 24 25 26 27 29 30 31 33 35 36 37 38 40 42 43 44 45 46 47 50 53 55 57 63 64 66 68 71 72 74 76 78 80 85 86 89 91 92 95 96 97 98 100 Copyright © 2012 Alcatel-Lucent.3 Radio – Radio 4.3 EAS/P8ETH Ethernet Port Segregation 9.10 PDH to Ethernet 3 SDH Cross-Connections 3.2 Dialog Boxes 2 TDM Cross-Connections 2.5 Radio to Radio 3.7 PDH to Radio/MPTACC 2.1 Ethernet LAG .4 Radio/MPTACC to Ethernet 2.Radio LAG cross-conn. All Rights Reserved.5 How to modify a Ring cross-connection 7 Ethernet Cross-Connections 7.Radio LAG cross-conn.3 Ethernet . with SDHCHAN 3.6 SDH Cross-Connections with SDHCHAN 3.8 Radio to Radio 2.2 ASAP – Radio 4.6 How to modify an ATM cross-connection 5 LAG-LAG Cross-Connections 5.1 PDH . 5.

Page Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 6 .

Edition 2 Section 3 · Module 3 · Page 7 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

2. Release the left button. Press the left button and. Edition 2 Section 3 · Module 3 · Page 8 . Place the mouse pointer on the source slot. while keeping button pressed. All Rights Reserved. Copyright © 2012 Alcatel-Lucent.Notes: To create a cross-connection between two points: 1. 3. drag the mouse to the destination slot.

• ATM-Radio connection: orange line. • Slot#4 MPTACC is cross-connected to Ethernet Port#1. • PDH-Eth connection: blue line. • • These colors will be applied to the graphical area. a dialog will appear allowing the operator to setup a cross-connection. All Rights Reserved. Colors not shown in the figure: • ATM-Radio connection: orange line (ETSI market) • ATM-Eth connection: magenta line (ETSI market) • Ring connection: cyan Copyright © 2012 Alcatel-Lucent. • Radio-Radio connection: red line. when the operator releases the mouse button above cross-connection destination slot. • Slot#5 RADIO (and Slot#6 RADIO) are cross-connected to Ethernet Port#2. Edition 2 Section 3 · Module 3 · Page 9 . • Ethernet Port#3 PDH (blue) could not accept cross-connections. • Slot#3 MPTACC is cross-connected to Slot#4 MPTACC. • Each connection line is colored according to slots types it connects (as shown in Figure): • PDH-Radio connection: black line. • Radio-Eth connection: green line. to Slot#4 MPTACC and to Ethernet Port#1. • Slot#5 and Slot#6 are in 1+1 configuration. it is possible to see different aspects of configuration created by the operator: • Slot#8 PDH is cross-connected to Slot#5 radio ODU300.Notes: • If the action involves two cross-connectable slots. Looking at figure. • Slot#3 and Slot#4 (green) could accept more cross-connections.

keeping the previous graphical. • • • • All the dialog boxes have a specific title describing the building cross-connection. Copyright © 2012 Alcatel-Lucent. Ethernet parameters. close to the destination point. Dialog boxes can ask for specific Flow Ids through a set of checkboxes. a field to fill-in “external” (incoming) Flow Ids. a dialog will appear.Notes: • When connecting two linkable slots through a cross-connection. Each cross-connection has different parameters and required data and information will depend on ongoing cross-connecting. Edition 2 Section 3 · Module 3 · Page 10 . etc. depending on start. this states both slots numbers and types (Slot#8 PDH – Slot#5 RADIO in the example figure). not sent to the NE!) The “Cancel” button will graphically discard ongoing cross-connection. The “Ok” button will visually save the current modifications (this means that data are graphically saved only. All Rights Reserved.and end-point of connection itself. This dialog contains connection information.

Edition 2 Section 3 · Module 3 · Page 11 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.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". Edition 2 Section 3 · Module 3 · Page 12 . Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent.Notes: Configuration parameters will ask to specify Flow ID number. Edition 2 Section 3 · Module 3 · Page 13 . as associated in PDH slot. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 14 . All Rights Reserved.

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

Edition 2 Section 3 · Module 3 · Page 16 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 17 . All Rights Reserved.

the operator will see two different confirmation dialogs. • Copyright © 2012 Alcatel-Lucent. Based on used input style (ranges or values).[a-b]. … and so on. Edition 2 Section 3 · Module 3 · Page 18 . If the operator wants to specify different Flow Ids grouping them without using ranges. It is not possible to merge the two solutions (ranges and values) by writing [n-m]. both included. it can use commas to separate values as shown in figure. All Rights Reserved.Notes: • By using [n-m] the operator will specify adding all Flow IDs from n to m.

Edition 2 Section 3 · Module 3 · Page 19 .Notes: Once correctly completed the cross-connection configuration and clicked on “OK” button. the operator will see a green line describing the Radio/MPTACC to Ethernet cross-connection defined). Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

The Profile can be TDM2Eth or TDM2TDM. The operator has to put the correct MAC address to complete the cross-connection configuration. as associated in PDH slot. Edition 2 Section 3 · Module 3 · Page 20 . As associated in PDH slot. and all parameters related to such Flow ID.Notes: • • • • • By dragging a connection between a PDH slot and an Ethernet port. All Rights Reserved. The operator has to enter the destination MAC address to complete the crossconnection configuration and click OK. Copyright © 2012 Alcatel-Lucent. Select the Flow ID number. the operator can see the configuration dialog in Figure. Configuration parameters will introduce Flow ID number. the parameters related to such Flow ID are retrieved. To create other cross-connections drag other lines between the PDH slot and the Ethernet port and repeat the operations.

Notes: • Once correctly completed the cross-connection configuration and clicked on “OK” button. Edition 2 Section 3 · Module 3 · Page 21 . Considering a connection to Ethernet ports. when a port reaches its full capacity. the operator will be able to see a blue line describing the PDH to Ethernet cross-connection defined (see Figure). the operator will see a specific report. All Rights Reserved. • Copyright © 2012 Alcatel-Lucent.

multicast address in case of protected configurations) must be inserted during the cross-connection creation.Notes: • In these types of cross-connections the destination MAC address of the adjacent NE (unicast address in case of unprotected configurations. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 22 . Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 3 · Page 23 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Now from the screen you have to delete the cross-connections by removing the check mark from the relevant Flow Id box and create again a new cross-connections. Edition 2 Section 3 · Module 3 · Page 24 . but with some differences in allowed actions: • • previously assigned tributaries (400 to 405 in the example) are active and selected. All Rights Reserved. In figure the operator is modifying a previously created cross-connection (in this case Slot#8 PDH and Slot#5 radio): this action brings up a dialog almost like the creation one. Copyright © 2012 Alcatel-Lucent. tributaries assigned to another cross-connection (406 to 431) are not active and not selected.Notes: • • • An existing cross-connection can be modified by double-clicking with the left mouse button on its symbolic line.

All Rights Reserved. Remove the check mark and create again a cross-connection. Edition 2 Section 3 · Module 3 · Page 25 . With a double click with the mouse on the connection line.Notes: • The operator can click on a specific (red) line in order to modify connection parameters. • Copyright © 2012 Alcatel-Lucent. the dialog window shown in Figure will appear.

Remove the check mark and create again a cross-connection. With a double click with the mouse on the connection line. the dialog window shown in the Figure above can be managed by the operator. Edition 2 Section 3 · Module 3 · Page 26 .Notes: • The operator can click on specific (green) line in order to modify connection parameters. All Rights Reserved. • Copyright © 2012 Alcatel-Lucent.

• Copyright © 2012 Alcatel-Lucent. Remove the check mark and create again a cross-connection.Notes: • The operator can click on specific (blue) line in order to modify connection parameters. the dialog window shown in Figure can be managed by the operator. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 27 . With a double click with the mouse on the connection line.

All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 28 .This page intentionally left blank Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 29 .

Edition 2 Section 3 · Module 3 · Page 30 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 3 · Page 31 .Notes: • • By dragging a connection between a SDH slot and a Radio slot or MPTACC slot. Copyright © 2012 Alcatel-Lucent. The Flow ID is automatically recognized as associated to the SDH slot. the operator will see the configuration dialog. All Rights Reserved.

All Rights Reserved.Notes: Once correctly completed the cross-connection configuration and clicked on "OK" button. the operator will see a black line describing the SDH to Radio cross-connection defined . Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 32 .

Copyright © 2012 Alcatel-Lucent. The operator has to fill in data to complete the cross-connection configuration. as coming from remote radio signal. To create other cross-connections drag other lines between the two radio slots and repeat the operations. and the profile. the operator will see the configuration dialog in figure. All Rights Reserved.Notes: • • • By dragging a connection between two different Radio slots. Edition 2 Section 3 · Module 3 · Page 33 . Configuration parameters will introduce Flow ID number.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 34 .

In the Figure. Edition 2 Section 3 · Module 3 · Page 35 .Notes: • • • An existing cross-connection can be modified by double-clicking with the left mouse button on its symbolic line. then click Apply. Copyright © 2012 Alcatel-Lucent. Now from the screen you have to delete the cross-connections by removing the check mark from the relevant Flow ID box and create again a new cross-connections. All Rights Reserved. • Select the Flows ID and click OK to remove the cross-connection. the operator is modifying a previously created cross-connection (in this case Slot#8 SDH and Slot#4 MPTACC): this action brings up a dialog almost like the creation one. but with some differences in allowed actions: • Previously assigned STM-1 (222 in the example) is active and selected. • In the example of the figure there is no other Flow ID and for this reason it is not possible to create another cross-connection.

Notes: • The operator can click on a specific (red) line in order to modify connection parameters. Edition 2 Section 3 · Module 3 · Page 36 . the dialog window shown in the Figure will appear. Remove the check mark and create again a cross-connection. With a double click with the mouse on the connection line. • Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 37 .Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 38 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 39 .

Note: In the SDH unit only the E1 streams enabled (Unframed). can be cross-connected to a PDH unit. Copyright © 2012 Alcatel-Lucent. but with no associated Flow Id. Edition 2 Section 3 · Module 3 · Page 40 .Notes: • • Select the Flow ID of the E1 in the PDH unit and the E1 of the SDH. Press the Right Arrow button. All Rights Reserved.

All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 41 .Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 3 · Page 42 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Copyright © 2012 Alcatel-Lucent. the operator is modifying a previously created cross-connection (in this case Slot#8 SDH and Slot#4 MPTACC): this action brings up a dialog almost like the creation one.Notes: • In the Figure. then click Apply. Edition 2 Section 3 · Module 3 · Page 43 . but with some differences in allowed actions: • Deselect the Flow ID and select another Flow Id and click OK to change the cross-connection.

Notes: Select the cross-connection on the right-side field. Edition 2 Section 3 · Module 3 · Page 44 . then click on Apply. All Rights Reserved. click OK. click on the Left Arrow button. Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 45 . All Rights Reserved.

All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 46 .Copyright © 2012 Alcatel-Lucent.

with the following main differences: • • MAC DA is also explicitly provisioned in the NE acting as TPE role admission control. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. ATM "Light" Cross-connection Provisioning • In this release when a cross-connection toward a radio direction with MPT is involved.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. the related provisioning is performed in almost the same way as with ODU300. is never performed. Edition 2 Section 3 · Module 3 · Page 47 . in terms of checking bandwidth required but ATM PW flow against the available bandwidth on radio interface.

Edition 2 Section 3 · Module 3 · Page 48 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 49 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. To create other cross-connections drag other lines between the two radio slots and repeat the operations. the operator will see the configuration dialog. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 50 .Notes: • • By dragging a connection between two different radio slots.

All Rights Reserved. • An ATM PW is made up of two undirectional flows.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 Descriptor previously created. Edition 2 Section 3 · Module 3 · Page 51 . Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 52 .

Copyright © 2012 Alcatel-Lucent.Notes: • Configuration parameters are: • select the Service: ATM or PW3 • select the PW label • assign the VLAN ID • enter the Destination MAC address • associate the Traffic Descriptor by clicking on Browse and selecting a Traffic Descriptor previously created. All Rights Reserved. • An ATM PW is made up of two undirectional flows. Edition 2 Section 3 · Module 3 · Page 53 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 54 .

Edition 2 Section 3 · Module 3 · Page 55 . All Rights Reserved. Copyright © 2012 Alcatel-Lucent.Notes: • Configuration parameters are: • select the ATM interface • select the PW label • enter the VPI • assign the VLAN ID • 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-connection configuration.

when a port reaches its full capacity.Notes: Considering a connection to Ethernet ports. Copyright © 2012 Alcatel-Lucent. the operator will see a specific report. Edition 2 Section 3 · Module 3 · Page 56 . All Rights Reserved.

Edition 2 Section 3 · Module 3 · Page 57 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. • Tributaries assigned to another cross-connection are not active and not selected. Copyright © 2012 Alcatel-Lucent.Notes: • In Figure the operator is modifying a previously created cross-connection: this action brings up a dialog almost like the creation one: • Previously assigned tributaries (111 in the example) are active and selected. • Select the ATM interface and remove the check mark and create again a cross-connection. Edition 2 Section 3 · Module 3 · Page 58 .

All Rights Reserved. • Copyright © 2012 Alcatel-Lucent.Notes: • The operator can click on a specific (red) line in order to modify connection parameters. Edition 2 Section 3 · Module 3 · Page 59 . the dialog window shown in Figure will appear. With a double click with the mouse on the connection line. Select the ATM Service and remove the check mark and create again a cross-connection.

the dialog window shown in Figure can be managed by the operator.Notes: • The operator can click on specific (green) line in order to modify connection parameters. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 60 . Select the ATM Service and remove the check mark and create again a cross-connection. With a double click with the mouse on the connection line. • Copyright © 2012 Alcatel-Lucent.

• Copyright © 2012 Alcatel-Lucent. With a double click with the mouse on the connection line. Edition 2 Section 3 · Module 3 · Page 61 . Select the ATM interface and remove the check mark and create again a cross-connection. the dialog window shown in Figure can be managed by the operator. All Rights Reserved.Notes: • The operator can click on specific (blue) line in order to modify connection parameters.

This page intentionally left blank Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 62 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 63 .

Radio LAG cross-connections Copyright © 2012 Alcatel-Lucent.Radio LAG cross-connections Radio LAG . The operator has to put the correct MAC address to complete the cross-connection configuration. Flow ID number and all parameters related to such Flow ID. Two types of cross-connections can be implemented: • • • Ethernet LAG . Edition 2 Section 3 · Module 3 · Page 64 . All Rights Reserved.Notes: • Configuration parameters will introduce the Service (TDM or ATM).

Edition 2 Section 3 · Module 3 · Page 65 .Notes: To create other cross-connections drag other lines between the Radio LAG and the Ethernet LAG and repeat the operations. All Rights Reserved. Copyright © 2012 Alcatel-Lucent.

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

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 67 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 68 .

the operator is modifying a previously created cross-connection (in this case Radio LAG #2 SDH and Ethernet LAG #24): this action brings up a dialog almost like the creation one. Edition 2 Section 3 · Module 3 · Page 69 . Copyright © 2012 Alcatel-Lucent. then click Apply.Notes: • In the Figure. In the example of the figure there is no other Flow ID and for this reason it is not possible to create another cross-connection. but with some differences in allowed actions: • • • Previously assigned Flow ID (654 in the example) is active and selected. All Rights Reserved. Select the Service and the Flows ID and click OK to remove the cross-connection.

In the example of the figure there is no other Flow ID and for this reason it is not possible to create another cross-connection. then click Apply. Edition 2 Section 3 · Module 3 · Page 70 . Select the Service and the Flows ID and click OK to remove the cross-connection.Notes: • • • Previously assigned Flow ID (654 in the example) is active and selected. Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 71 .Copyright © 2012 Alcatel-Lucent.

The Cross-connections to be implemented are: • • • • PDH .Ring cross-connections Pass-through cross-connections Warning: After the Ring cross-connection creation enable the ERP in the Ring menu (click on the Ring icon in the Tool bar).Ring cross-connections Radio . All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 72 . Copyright © 2012 Alcatel-Lucent.Notes: • • Configuration parameters will ask to select the instance and to select Flow ID number.Ring cross-connections Ethernet . as associated in PDH slot.

All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 73 .Copyright © 2012 Alcatel-Lucent.

Service Profile and TDM Clock Source (if the Profile in TDM2Eth).Notes: • • • Configuration parameters are the Ring Instance. VLAN (multiple selection can be done). The operator has to fill in data to complete the cross-connection configuration and click on the Right Arrow button. The dialog screen displays the cross-connected VLANs (see figure). All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 74 . Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 3 · Page 75 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 76 .Notes: • • • Configuration parameters are the Ring Instance. Service Profile. The dialog screen displays the cross-connected VLANs (see figure). The operator has to fill in data to complete the cross-connection configuration and click on the Right Arrow button. VLAN (multiple selection can be done). All Rights Reserved. TDM Clock Source (if the Profile in TDM2Eth) and the destination MAC Address.

Copyright © 2012 Alcatel-Lucent.Notes: When a port reaches its full capacity. Edition 2 Section 3 · Module 3 · Page 77 . All Rights Reserved. the operator will see a specific report.

Service Profile and TDM Clock Source (if the profile is TDM2Eth). The operator has to fill in data to complete the cross-connection configuration and click on the Right Arrow button. Edition 2 Section 3 · Module 3 · Page 78 .Notes: • • • Configuration parameters are the Ring Instance. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. The dialog screen displays the cross-connected VLANs (see figure). VLAN (multiple selection can be done).

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 79 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 3 · Page 80 .

Edition 2 Section 3 · Module 3 · Page 81 . Slot#3 PDH and Radio): this action brings up a dialog almost like the creation one. but with some differences in allowed actions Copyright © 2012 Alcatel-Lucent. Click OK and Apply.Notes: • In the Figure above. the operator is modifying a previously created cross-connection (in this case • Deselect the Flow Id and select another one. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent.Notes: • • The operator can click on a specific line in order to modify connection parameters. the dialog window shown in the Figure above will appear. Select the cross-connected VLANs in the right-side field and click on the Left Arrow arrow. Change the Instance. With a double click with the mouse on the connection line. Edition 2 Section 3 · Module 3 · Page 82 . then select another VLAN and click the Right Arrow button. if required. Click on OK and Apply. All Rights Reserved.

With a double click with the mouse on the connection line. Change the Instance. Select the cross-connected VLANs in the right-side field and click on the Left Arrow arrow. then select another VLAN and click the Right Arrow button. Copyright © 2012 Alcatel-Lucent.Notes: • • The operator can click on a specific line in order to modify connection parameters. Click on OK and Apply. if required. Edition 2 Section 3 · Module 3 · Page 83 . All Rights Reserved. the dialog window shown in the Figure will appear.

Change the Instance. Select the cross-connected VLANs in the right-side field and click on the Left Arrow arrow. With a double click with the mouse on the connection line. if required. Edition 2 Section 3 · Module 3 · Page 84 . All Rights Reserved. Copyright © 2012 Alcatel-Lucent. the dialog window shown in the Figure can be managed by the operator. Click on OK and Apply. then select another VLAN and click the Right Arrow button.Notes: • • The operator can click on specific line in order to modify connection parameters.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 85

Notes: Remember Flow Id must be the same on both ends of the path and only used once in the network.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 86

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)

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 87

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.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 88

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 89

This page intentionally left blank

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 90

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 91

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 the same through the entire path).
3. On the RADIO-RADIO pop-up, click OK. 4. On the Cross-Connections screen, click Apply.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 92

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 93

This page intentionally left blank

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 94

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 95

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 96

Notes:

• • • • •

When provisioning multiple radio links on the same path use port segregation to avoid any Ethernet loops. 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

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 97

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 98

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 99

Notes:

• •

The switch ports in a private VLAN domain have special characteristics. One key characteristic is port segregation within an isolated VLAN. Isolated or segregated ports are typically used for those endpoints that only require access to a limited number of outgoing interfaces.


• • •

An endpoint connected to an isolated port will only possess the ability to communicate with those endpoints 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 a warning that the port is segregated. Press Alt-W. Notice the screens are different if any ports are segregated.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 100

This page intentionally left blank

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 101

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 3 · Page 102

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 1

This page is left blank intentionally

Document History Edition 3.4 4.0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition Updated for Release 4.0

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 2

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 3

This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 4

Page 1 WT Performance Monitoring Suite 1.1 Introduction 1.2 Tool bar 1.3 Menu bar 1.4 NE Measurement Main Tree 1.5 How to Start the Measurements 1.6 How to Stop the Measurements 1.7 Offline Mode 1.8 PM selectable options 2 Ethernet Statistics 2.1 Ethernet Statistics tab 2.2 CORE-ENH unit Ethernet Statistics 2.3 Radio QoS Ethernet Port PM example 3 RADIO PMs 3.1 RADIO PMs procedures 3.2 Manage thresholds 3.3 24-Hour Current List View example 3.4 24-Hour Current Overview example 3.5 24-Hour Current Birdseye View example 3.6 Radio Port PM example 4 Adaptive Modulation PM 4.1 Performance monitoring procedures 4.2 Adaptive Modulation PM example 5 PDH Performance Monitoring 5.1 P32E1DS1 unit performances 5.2 Incoming 5.3 How to display a threshold 5.4 Example of the other views 6 IMA Layer Statistics 6.1 IMA Layer Statistics 7 ATM Layer Statistics 7.1 ATM Interface Statistics 7.2 Interface# 7.3 Logical VPs and Not Logical VPs 8 RSL History 8.1 RSL History 7 8 11 13 15 21 22 23 26 27 28 29 40 41 42 44 48 49 50 51 53 54 56 57 58 59 60 62 65 66 69 70 71 72 75 76

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 5

All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 6 .Page Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 7 .

All Rights Reserved.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 Tool Bar from the WebEML in Main menu > Diagnosis > Performance Monitoring from the WebEML in Main menu > Diagnosis > Summary Block Diagram View Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 8 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 9 .

Edition 2 Section 3 · Module 4 · Page 10 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Refresh button retrieves the current PM reports form NE and update the table view and chart view with the recently collected data. Reset button resets the data collection and related counters. Start/Stop button starts or stops the counters for the data collection.Notes: The buttons in the Toolbar have the following functionalities: • • • • • • • • Close button removes a NE from the NE list. All Rights Reserved. Sort button (not available). Copyright © 2012 Alcatel-Lucent. The current measurement status is shown. Background button (not available). Move to front button (not available). when the Current Data have been stopped or started. Move to back button (not available). Edition 2 Section 3 · Module 4 · Page 11 .

All Rights Reserved. Help button show help content. 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. Export button saves the report. Copyright © 2012 Alcatel-Lucent.Notes: • • • • • • • • • • • Archive button archives in the NM environment the PDH PM and the Radio PM (only the radio counters). Overview button to display all the PM counters in a graphic format. Note button shows the meaning of each parameter. Edition 2 Section 3 · Module 4 · Page 12 . Offline Mode button saves the current status of the WT Performance Monitoring Suite to have later the possibility to see the PM offline. List View to display all the PM counters in a tabular format. Print button prints the user selected performance point. Collect button forces in the NM environment the PM collection.

All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 13 . Threshold Editor (opens the Editor for the thresholds to be associated in the PDH PM feature bar or in the Radio PM feature bar) List View Overview Bird’s Eye View Move to front (not available) Move to back (not available) Sort (not available) Background (not available) Close: removes a NE from the NE list • Edit: • Network: • Action: Copyright © 2012 Alcatel-Lucent.Notes: • File: Export Print Offline mode Exit: closes the application (this menu is available only in NM environment).

Notes: • Tools: • • • Start/Stop: starts or stops the counters for the data collection. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 14 . 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 view with 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 Copyright © 2012 Alcatel-Lucent.

In the List View the Custom View tab-panel enabes the display of a subset of the available counters. slot. The opposite operation can be done by selecting the counter in the right area and by clicking the lower arrow to move it to the left area. • You can customize the view by clicking on tab Custom View. • The view is divided into two areas: • left area.png or . which contains the list of the selectable counters. selected through the navigation bars. • 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 .Notes: • In the List View all the available counters for a selected feature. All Rights Reserved. but by deselecting the check box of a particular measurement counter on the legend. • right area. measurement point are shown in the tabular format. are displayed. Edition 2 Section 3 · Module 4 · Page 15 . Click on OK button to confirm. • • In the Overview all the measurements are shown in a small graphic format in one screen. • 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. which contains the list of the selected counters. • By default all the measurements. the relevant counter is removed from the view. 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. • The user can select a counter on the left area and by clicking the upper arrow move it to the right area in order to customize the counter view.jpeg • Print: to print the image • Zoom In: to enlarge the image • Zoom Out: to shrink the image • AutoRange: to fit the image Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 16 .

Edition 2 Section 3 · Module 4 · Page 17 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 18 . All Rights Reserved.

3. Click the right arrow to move the fields into the Selected panel. Not Selected panel. Edition 2 Section 3 · Module 4 · Page 19 . Click OK. Ethernet Statistics Radio PM Adaptive Modulation PM PDH MP IMA Layer Statistics (ETSI) ATM Interface Statistics (ETSI) RSL Statistics To change the field display: Click the Custom View tab (see next slide) From the Custom View Composer.Notes: • The Custom View Composer (launched from the Custom View tab) allows the user to specify which PM fields are displayed in the List View and the Overview for the respective PM categories: • • • • • • • • 1. All Rights Reserved. select the fields to be displayed. 2. 4. Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 4 · Page 20 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

(2) The slot selection corresponds to the selection of the unit. after the selection of the slot. In the figure. All Rights Reserved. in this example the counters of all equipped ports will be displayed. (3) Optionally. The PM can be started individually or at slot level. In this case. The selection of the unit will cause the display of the counters of all its available subordinate objects. Slot 1 has been selected. you can select one of its subordinate objects. only the selected object is highlighted in the frame area. i. Copyright © 2012 Alcatel-Lucent.Notes: • • (1) In the example shown.e. Edition 2 Section 3 · Module 4 · Page 21 . Ethernet Statistics has been selected. • • • (4) The start time is displayed in the Configuration area (left-lower part of the window).

All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 22 .Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 23 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 24 .

Notes: The Toolbar and the Menu bar are the same bars of the WTPMS. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 25 . Copyright © 2012 Alcatel-Lucent. The only differences are: z Start/Stop z and Refresh buttons are not available in the Offline Mode allows to open another NE in offline mode.

Notes: • Several tab-panels can be present: • A .Specific tab-panel (identified by the NE IP address) for each NE. • • By clicking an NE in the NEs List or in the specific NE tab-panel. The following types of Performance Monitoring are available: 1. 2. 6. which launched the application. 5. which launched the application • B .NEs List: it includes all the NEs. 7. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 26 . 4. Ethernet Statistics Radio PM Adaptive Modulation PM PDH PM IMA Layer Statistics (ETSI market) ATM Interface Statistics (ETSI market) RSL History Copyright © 2012 Alcatel-Lucent. 3. the available PM will appear.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 27 .

All Rights Reserved. The MD300 unit is the interface to ODU300.Notes: Stability measurement on Ethernet counters (with duration from few hours to 24 Hours) should be performed by selecting an high value (60 seconds) as collection time of the performances (refer to parameter Interval in the Configuration subwindow). Edition 2 Section 3 · Module 4 · Page 28 . Copyright © 2012 Alcatel-Lucent. • • The MPTACC unit is the interface to MPT-HC/MPT-MC.

The default duration is 1 hour.Notes: • • The right-hand area contains the statistic data for the Ports. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 29 . The following tab are selectable for each port: • Ethernet Aggregate Tx • Ethernet Aggregate Rx • Custom view • • The default interval is 5 seconds.

Edition 2 Section 3 · Module 4 · Page 30 .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. • TDF: total number of Transmitted Ethernet frames. but the TDF counter is not incremented. All Rights Reserved. Reserved Multicast frames are discarded. including Ethernet header characters. which were chosen to be discarded due to buffer congestion. to the broadcast address. • TTF Multicast: total number of good packets transmitted by this address that were directed to a multicast address. • TTF: total number of Ethernet frames transmitted out by the interface. • TTF Broadcast: total number of good packets transmitted by this address that were directed Copyright © 2012 Alcatel-Lucent. This number does not include packets directed to the broadcast address. • TTF Unicast: total number of Ethernet Unicast frames transmitted out by the Virtual Ethernet Interface.

B. • TRF Unicast: total number of Ethernet Unicast frames received correctly by the Virtual Ethernet Interface.: Reserved Multicast frames are discarded. but the TDF counter is not incremented. • TRF Broadcast: total number of good packets received that were directed to the broadcast Copyright © 2012 Alcatel-Lucent. • TDF: total number of Ethernet frames discarded for congestion. • TRF: total number of Ethernet frames received by the Virtual Ethernet Interface. • TRSEF: total number of errored frames.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. • TRF Multicast: total number of good packets received that were directed to a multicast address. This number does not include packets directed to the broadcast address. including Ethernet header characters. This number does not include multicast packets. Edition 2 Section 3 · Module 4 · Page 31 . „ N. address. All Rights Reserved.

Notes: • • Click on the Navigation bar to change the view. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 32 . In the buttom 2 tab-panels show the counters: • • Deafult Counters: collected on the NE row Elaborated Counters: processed on the PC and are available only when the PC is connected to the NE. Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 4 · Page 33 . Copyright © 2012 Alcatel-Lucent.Notes: • • Click on the Navigation bar to change the view. All Rights Reserved. In the buttom 2 tab-panels show the counters: • • Deafult Counters: collected on the NE row Elaborated Counters: processed on the PC and are available only when the PC is connected to the NE.

Edition 2 Section 3 · Module 4 · Page 34 . All Rights Reserved.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) Copyright © 2012 Alcatel-Lucent.

• Queue 6 is reserved to TMN traffic. up to 256QAM • MPT-HC (Medium Capacity). Edition 2 Section 3 · Module 4 · Page 35 . • Queue 7 is reserved to TDM2Eth traffic. Queue 5 is the highest priority queue.Notes: • Two types of MPT are available: • MPT-HC (High Capacity). • The remaining 5 queues are reserved to Ethernet traffic. up to 128QAM • The MPTACC unit has 8 output queues: • Queue 8 is reserved to TDM2TDM traffic. All Rights Reserved. Copyright © 2012 Alcatel-Lucent.

but the TDF counter is not incremented. including Ethernet header characters. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. • Reserved Multicast frames are discarded. The available performances at queue level (for each queue) are: • TTO: total number of octets of Ethernet frames transmitted out by the Interface. • TDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer congestion. • TTF: total number of Ethernet frames transmitted out by the interface.Notes: • Select the tab of the queue to display. Edition 2 Section 3 · Module 4 · Page 36 .

Notes: • • Click on the Navigation bar to change the view. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 37 . All Rights Reserved. In the buttom 2 tab-panels show the counters: • • Default Counters: collected on the NE row Elaborated Counters: processed on the PC and are available only when the PC is connected to the NE.

In the buttom 2 tab-panels show the counters: • • Default Counters: collected on the NE row Elaborated Counters: processed on the PC and are available only when the PC is connected to the NE. Edition 2 Section 3 · Module 4 · Page 38 . Copyright © 2012 Alcatel-Lucent.Notes: • • Click on the Navigation bar to change the view. All Rights Reserved.

Edition 2 Section 3 · Module 4 · Page 39 . All Rights Reserved. Copyright © 2012 Alcatel-Lucent. In the buttom 2 tab-panels show the counters: • • Default Counters: collected on the NE row Elaborated Counters: processed on the PC and are available only when the PC is connected to the NE.Notes: • • Click on the Navigation bar to change the view.

Edition 2 Section 3 · Module 4 · Page 40 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 41 . All Rights Reserved.

The same functions are provided for both time periods. Two types of counters are supported: • • Radio Counters – Errored seconds. The performance reports can be displayed in 15 minutes or 24 hour time periods. The PM are of HOP or LINK type: • • • HOP refers to the PM before the RPS switch. All Rights Reserved. Background Block Error. average.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. Severely Errored Seconds. and maximum power levels during the elasped time. and Unavailable Seconds Analog Counters – minimum. Edition 2 Section 3 · Module 4 · Page 42 . LINK refers to Performance Monitoring after the RPS switch. Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. It displayes the time of Refresh. It displays the elapsed time in the current interval of monitoring.Notes: • The view contains the following collection data parameters: • Time. the Performance Monitoring. An interval is defined as “suspect” if at least one of the following conditions occurs in the collection period: • the elapsed time deviates more than 10 seconds of the nominal time • loss of the Performance Monitoring data in the equipment • performance counters have been reset during the interval. Edition 2 Section 3 · Module 4 · Page 43 . • The displayed counters are: • BBE (Background block Errors) • ES (Errored Seconds) • SES (Severily Errored Seconds) • UAS (Unavailable Seconds) Copyright © 2012 Alcatel-Lucent. it is highlighted in red. It displays the number of intervals (reports) suppressed in the History because they don’t have errors. • If an interval is suspected. • Suppressed Intervals. This time changes after the Auto • Elapsed Time.

All Rights Reserved.Notes: • • • • • • • For the ANSI market the PDH PM Thresholds assigned to Performance Monitoring counters can be created. There are two default thresholds for LINK: Threshold #1 (15 min report) and Threshold #3 (for 24 hour report). There are threshold tables for the HOP and for the LINK. The following actions can be performed: • Thresholds display • Create threshold • Delete threshold • Associate a threshold to a monitoring point Copyright © 2012 Alcatel-Lucent. or changed. There are two default thresholds for HOP: Threshold #1 (for 15 min report) and Threshold #4 (for 24 hour report). The user can manage thresholds to be associated to Hop or Link 15min report or 24h report. displayed. Edition 2 Section 3 · Module 4 · Page 44 .

Two standard thresholds are available for the LINK (Threshold #1 and #3). All Rights Reserved. #5 and #6).Notes: • • • • Four threshold tables can be created for the HOP (Threshold #2. Two standard thresholds are available for the HOP (Threshold #1. Two threshold tables can be created for the LINK (Threshold #2 and #4). Edition 2 Section 3 · Module 4 · Page 45 . Copyright © 2012 Alcatel-Lucent. #3. #4).

Notes: Only the created thresholds can be modified or deleted. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 46 . The default thresholds can be only displayed.

only the thresholds applicable to the selected Monitoring Point are presented. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 47 .Notes: The list of the available thresholds for the previously selected Monitoring Point is presented by clicking on the down arrow beside the field name (threshold in this case). Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 4 · Page 48 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2 Section 3 · Module 4 · Page 49 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 50 .

In 1+1 HSB radio configuration. 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 or equal to 30% of the blocks in one second. The qualifying ten consecutive SES seconds are included in the UAS time period. is a second in which an LOF or DemFail occurs. is a second in which an LOF occurs at the link level after RPS. All Rights Reserved. Unavailable Seconds (UAS)-A time period starting after ten consecutive SES events are detected. Errored Block count for a link hop section equals the number of link level errored blocks after RPS. Defect second on a radio hop section. Errored Block count for a radio hop section equals the number of errored blocks. Adaptive Modulation PM is not supported in 1+1 FD radio configurations. the statistics are associated with the link level after RPS.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 is enabled. Edition 2 Section 3 · Module 4 · Page 51 . Copyright © 2012 Alcatel-Lucent. Defect second on a link hop section. Background Block Error (BBE)-The number of block errors in a one second period and the second is not an SES. Ending upon the detection of ten consecutive non SES events. These non SES seconds are not included in the UAS time period.

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 52 .

All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 53 .Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 4 · Page 54 . the WT Performance Monitoring Suite will display Adaptive Modulation performance information. Copyright © 2012 Alcatel-Lucent. All Rights Reserved.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 MPTACC unit (for MPT).

• Elapsed Time. • Modulation schemes (from QPSK to 256 QAM). It displayes the time of the Performance Monitoring. It displays the elapsed time in the current interval of monitoring. All Rights Reserved. This time changes after the Auto Refresh. it is highlighted in red. • If an interval is suspected. It shows (for each modulation scheme) the time during which a specific modulation scheme has been used. Edition 2 Section 3 · Module 4 · Page 55 .Notes: • The view contains the following collection data parameters: • Time. An interval is defined as "suspect" if at least one of the following conditions occurs in the collection period: • the elapsed time deviates more than 10 seconds of the nominal time • loss of the Performance Monitoring data in the equipment • performance counters have been reset during the interval. Copyright © 2012 Alcatel-Lucent.

Edition 2 Section 3 · Module 4 · Page 56 . the statistics are associated with the link level after Radio Protection Switching. Adaptive Modulation PM is not supported in 1+1 FD radio configurations.Notes: • Adaptive Modulation PM captures the modulation scheme used for the transmitter when adaptive modulation is enabled. In 1+1 HSB radio configuration. All Rights Reserved. • Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 57 .Copyright © 2012 Alcatel-Lucent.

The CRC is used to detect the quality of the E1 stream. For a better quality in the Performance Monitoring it is recommended to start up to 128 E1 PM counters on the same NE. All Rights Reserved. This means 4 counters (Incoming 15 Minutes.Notes: • The following description explains the functions to provide the Performance Monitoring process with a granularity period of 15 min. Edition 2 Section 3 · Module 4 · Page 58 . The Counters can be displayed in three different views: • List View • Overview • Bird’s Eye View Copyright © 2012 Alcatel-Lucent. • 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". Outgoing 15 Minutes and Outgoing 24 Hours) for 32 E1 streams. The same functions are provided for 24h Performance Monitoring process. 9500MPR is transparent regarding the E1 stream. Incoming 24 hours.

Edition 2 Section 3 · Module 4 · Page 59 .Notes: • If an interval is suspected. • These values refer to the last refresh performed with the Refresh button in the Tool bar. Copyright © 2012 Alcatel-Lucent. All Rights Reserved. An interval is defined as “Suspect” if at least one of the following conditions occurs in the collection period: • the elapsed time deviates more than 10 seconds of the nominal time • loss of the Performance Monitoring data in the equipment • performance counters have been reset during the interval. it is highlighted in red.

There are two default threshold: • Threshold #1 (to be associated to 15 min report) • Threshold #4 (to be associated to 24 h report). • Associate a threshold to a monitoring point. There are two default threshold: • Threshold #1. to be associated to 15 min report. All Rights Reserved. • Create a threshold. • • The threshold management procedures for PDH are the same as previously described for Radio PM. • Threshold #4.Notes: • Threshold management describes how to display or change or create the threshold to be assigned to Performance Monitoring counters. Edition 2 Section 3 · Module 4 · Page 60 . to be associated to 24 h report. • Modify/delete a threshold. Copyright © 2012 Alcatel-Lucent. • The following actions can be done: • Display a threshold.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 61 .

All Rights Reserved. Copyright © 2012 Alcatel-Lucent. In the buttom 2 tab-panels show the counters: • Deafult Counters: collected on the NE row • Elaborated Counters: processed on the PC and are available only when the PC is connected to the NE. Edition 2 Section 3 · Module 4 · Page 62 .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 connected to the NE. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 63 . Copyright © 2012 Alcatel-Lucent.Notes: • • Click on the Navigation bar to change the view.

Edition 2 Section 3 · Module 4 · Page 64 . All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 65 . All Rights Reserved.

Unavail Secs: counter of the seconds where the IMA group traffic state machine is down. The Counters can be displayed in three different modalities: • List View • Overview • Bird’s Eye View • In the following example. Blocked-FE) has been reported for Near-End IMA Group. The quality of IMA Group and Links is evaluated by monitoring IMA Group and Link Counters. Config-Aborted-FE. no tables will appear. only the List View is shown. To display the other views select in the Menu bar the view or click the view on the relevant icon in the Tool bar.Notes: • • • The IMA Layer Statistics are available with the A16E1DS1 unit. Insufficient-Links-FE. Edition 2 Section 3 · Module 4 · Page 66 . • • • • By selecting the slot. NeNumFailures: counter of the number of times a failure alarm condition (Config-Aborted. Insufficient-Links. Copyright © 2012 Alcatel-Lucent. This monitoring is based on IMA standard. All Rights Reserved.

for Near-End side. this link at Tx direction for Near-End side. UAS-IMA conditions. for Near-End side. except during SES-IMA or • NeSES (Severly Errored Seconds): counter of one second intervals containing more then 30% of the ICP cells counted as “IMA Violation”. OOF/LOF. belonging to an activated IMA Group. AIS.g. LOS. or LODS defects. • Ne Tx UUS (UnUsable Seconds): counter of unusable seconds declared by the Link State • Ne Tx failure: counter of the number of times a failure alarm condition has been entered on • Ne Rx failure: counter of the number of times a failure alarm condition has been entered on Copyright © 2012 Alcatel-Lucent. the following counters are available: • IMA Violation: counter of errored. invalid or missing ICP cells. this link at Rx direction for Near-End side. LIF defects. except during SES-IMA or UAS-IMA conditions. Edition 2 Section 3 · Module 4 · Page 67 . or LCD). All Rights Reserved. except during UAS-IMA condition. Machine at TX and RX directions for Near-End side. • NeUAS (UnAvailable Seconds): counter of the seconds unavailability beginning at the onset of 10 contiguous SES-IMA and ends at the onset of 10 contiguous seconds with no SES-IMA.. • OIF (Out of IMA Frame) anomalies: counter of OIF anomalies. or one or more link defects (e.Notes: • For each active IMA link.

Edition 2 Section 3 · Module 4 · Page 68 . All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 69 .

Edition 2 Section 3 · Module 4 · Page 70 . To display the other views select in the Menu bar the view or click the view on the relevant icon in the Tool bar. Copyright © 2012 Alcatel-Lucent. only the List View is shown. All Rights Reserved.Notes: • The Counters can be displayed in three different views: • List View • Overview • Bird’s Eye View • In the following example.

• Inv Header Discarded Cells: counter of the number of cells discarded because of Invalid Header. All Rights Reserved. invalid VPI or invalid VCI.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. Edition 2 Section 3 · Module 4 · Page 71 . Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 72 .

• Usage Rx: counter of the total number of valid VP/VC cells received including both CLP=0 and CLP=1 cells. The cells are counted prior to the application of the traffic policing. All Rights Reserved. This includes cells originally received with CLP=0 and CLP=1. • Discarded CLP0 Cells: counter of the total number of valid VP/VC cells received with CLP=0 • Tagged Cells: counter of the total number of valid VP/VC cells tagged by the traffic policing entity from CLP=0 to CLP=1 and transmitted. and active VC configured over an active ATM interface. and discarded by the traffic policing entity. are counted prior to the application of the traffic policing. The cells Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 73 . are counted prior to the application of the traffic policing. The cells • Usage Tx CLP0: counter of the number of valid VP/VC cells transmitted with CLP=0. • Usage Rx CLP0: counter of the number of valid VP/VC cells received with CLP=0. if configured as Termination end-point.Notes: • For each active VP. the following counters are available: • Discarded Cells: counter of the total number of valid VP/VC cells discarded by the traffic policing entity. The cells are counted prior to the application of the traffic policing. • Usage Tx: counter of the total number of valid VP/VC cells transmitted including both CLP=0 and CLP=1 cells.

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 74 .

All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 75 .Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 76 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 77 . All Rights Reserved.

Edition 2 Section 3 · Module 4 · Page 78 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2 Section 3 · Module 4 · Page 79 .

Copyright © 2012 Alcatel-Lucent. Edition 2 Section 3 · Module 4 · Page 80 . All Rights Reserved.

Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Section 4 · Module 1 · Page 1 .

4 4. Edition 2. All Rights Reserved.This page is left blank intentionally Document History Edition 3.0 Copyright © 2012 Alcatel-Lucent.0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition Updated for R4.0 Section 4 · Module 1 · Page 2 .

Edition 2.Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 1 · Page 3 . All Rights Reserved.

0 Section 4 · Module 1 · Page 4 . All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2.

7 Troubleshooting TMN Problems 1.3 Flash Card Replacement Procedure 2.1 MSS-8/MSS-4 Card Removal and Replacement 2.6 Troubleshooting Ethernet Problems 1.5 Troubleshooting Configuration Problems 1. All Rights Reserved.2 Core-E Card Removal and Replacement 2. Edition 2.0 Section 4 · Module 1 · Page 5 .1 Troubleshooting 1.8 Analyzing Ethernet Traffic 2 Failed Equipment Removal and Replacement 2.2 Before Going to Site Checklist 1.Page 1 Fault Management 1.5 MPT-MC Removal and Replacement 7 8 9 11 16 19 20 22 26 33 34 36 37 38 39 Copyright © 2012 Alcatel-Lucent.4 Troubleshooting Path Problems 1.4 ODU300 Removal and Replacement 2.3 Troubleshooting Basics 1.

Edition 2.0 Section 4 · Module 1 · Page 6 . All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

Edition 2.Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 1 · Page 7 . All Rights Reserved.

Edition 2.0 Section 4 · Module 1 · Page 8 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2. do not take any action until the weather abates. All Rights Reserved. Copyright © 2012 Alcatel-Lucent.Notes: If the fault suggests a rain fade or other weather related fade condition and it matches the prevailing weather conditions.0 Section 4 · Module 1 · Page 9 .

Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 1 · Page 10 . Edition 2. All Rights Reserved.

All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 1 · Page 11 .

Edition 2.0 Section 4 · Module 1 · Page 12 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2.0 Section 4 · Module 1 · Page 13 .

Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 1 · Page 14 . Edition 2. All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2.0 Section 4 · Module 1 · Page 15 .

All Rights Reserved.0 Section 4 · Module 1 · Page 16 . Edition 2.Notes: A path extends from ODU antenna port to ODU antenna port. Copyright © 2012 Alcatel-Lucent.

0 Section 4 · Module 1 · Page 17 . a spectrum analyzer may have to be used to confirm interference. All Rights Reserved.Notes: Ultimately. Copyright © 2012 Alcatel-Lucent. which is not an easy task given the need to connect directly to the antenna port. Edition 2. after removing the ODU.

0 Section 4 · Module 1 · Page 18 . All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.

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 has software from an earlier release. install the latest software. compatible 9500 MPR software is required. Edition 2. To remove the alarm. Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Section 4 · Module 1 · Page 19 .

Notes: This section gives general guidance on troubleshooting problems related to the four Ethernet ports on the Core-E Card. Edition 2. All Rights Reserved. Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 1 · Page 20 .

Edition 2. All Rights Reserved.Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 1 · Page 21 .

Edition 2.Notes: • • This section gives general guidance on troubleshooting problems related to the four Ethernet ports on the Core-E Card. Refer to table “Troubleshooting Ethernet Problems” on next slides for detail troubleshooting using the LEDs locally at the alarmed site.0 Section 4 · Module 1 · Page 22 . All Rights Reserved. Copyright © 2012 Alcatel-Lucent.

Refer to table “Troubleshooting Ethernet Problems” on next slides for detail troubleshooting using the LEDs locally at the alarmed site. All Rights Reserved. Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 1 · Page 23 . Edition 2.Notes: • • This section gives general guidance on troubleshooting problems related to the four Ethernet ports on the Core-E Card.

Notes: • • This section gives general guidance on troubleshooting problems related to the four Ethernet ports on the Core-E Card. Edition 2. Refer to table “Troubleshooting Ethernet Problems” on next slides for detail troubleshooting using the LEDs locally at the alarmed site.0 Section 4 · Module 1 · Page 24 . All Rights Reserved. Copyright © 2012 Alcatel-Lucent.

Edition 2. All Rights Reserved. Refer to table “Troubleshooting Ethernet Problems” on next slides for detail troubleshooting using the LEDs locally at the alarmed site.Notes: • • This section gives general guidance on troubleshooting problems related to the four Ethernet ports on the Core-E Card. Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 1 · Page 25 .

All Rights Reserved.0 Section 4 · Module 1 · Page 26 . Copyright © 2012 Alcatel-Lucent. Password: adminadmin.Notes: • Enter: • • User Name: initial. Edition 2.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.Notes: • • “Run command” provides the output on the web page. Edition 2. “Save output to file” provides the output on the web page and also saves the output on a file.0 Section 4 · Module 1 · Page 27 .

0 Section 4 · Module 1 · Page 28 . All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.

0 Section 4 · Module 1 · Page 29 .Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.

0 Section 4 · Module 1 · Page 30 . Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2.0 Section 4 · Module 1 · Page 31 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 1 · Page 32 . Edition 2.

Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 1 · Page 33 . Edition 2. All Rights Reserved.

0 Section 4 · Module 1 · Page 34 . Edition 2. Copyright © 2012 Alcatel-Lucent.Notes: All plug-in cards can be removed and installed with power applied. All Rights Reserved.

0 Section 4 · Module 1 · Page 35 . Failure to do so will comprise EMI integrity and the cooling capacity of the fan. All Rights Reserved. Edition 2.Notes: All slots must be filled with a plug-in card or a blank panel. Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Local and far end Core-E Cards must use the same software version.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. but do not have to be the same type.0 Section 4 · Module 1 · Page 36 . Edition 2.

Insert the Core-E with the new FLASH CARD. Edition 2. Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 1 · Page 37 . Remove the faulty FLASH CARD from the main Core-E and insert the spare one. 4. Second case: Core-E Not Protected 1. Carry-out the RESTORE procedure. 3. Get a spare FLASH CARD with the same sw-package release and license of the Main flash. 3. The MIB (MAIN FLASH) will be automatically aligned with the MIB (SPARE FLASH). 4. Remove the faulty FLASH CARD from the main Core-E and insert the spare one. 2. Get a spare FLASH CARD with the same sw-package release and license. Insert the Core-E with the new FLASH CARD. 2. All Rights Reserved.First case: Core-E Protected 1.

Notes: For 1+1 configurations: • before replacing the ODU make sure that the traffic is transmitted over the other channel.0 Section 4 · Module 1 · Page 38 . Copyright © 2012 Alcatel-Lucent. force with the CT the traffic onto the other channel. Edition 2. Otherwise. All Rights Reserved.

All Rights Reserved. Edition 2.Notes: For 1+1 configurations: • before replacing the ODU make sure that the traffic is transmitted over the other channel.0 Section 4 · Module 1 · Page 39 . Otherwise. force with the CT the traffic onto the other channel. Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.0 Section 4 · Module 1 · Page 40 .Copyright © 2012 Alcatel-Lucent. Edition 2.

Edition 2.Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 1 . All Rights Reserved.

All Rights Reserved.4 4.0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition Updated for Release 4.0 Section 4 · Module 2 · Page 2 .This page is left blank intentionally Document History Edition 3. Edition 2.0 Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.0 Section 4 · Module 2 · Page 3 .

0 Section 4 · Module 2 · Page 4 . All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2.

2 RPS Switching Criteria 1.2 User Ethernet interfaces protection 5.4 HSB Switching Criteria 5 Core-E protection 5.1 EPS Management 6.1 Core-E protection 5.1 Protections with MPT-HCV2/MPT-XP 2.3 EPS Switching Criteria 4.Overview 8.3 TMN Local Ethernet interface protection 5.4 HSB Switching Criteria 2 Protections with MPT-HC V2/MPT-XP 2.4 HSB Switching Criteria 3 MSS-4/MSS-8 XPIC (with MPT-HC V2 /MPT-XP only) 3.5 Core-E protection Switching Criteria 6 EPS. Edition 2.1 MSS-4/MSS-8 XPIC (with MPT-HCV2/MPT-XP only) 4 Protection with MPT-MC 4.3 HSB Protection Management 7 Ring Protection 7.2 RPS Switching Criteria 4.1 Protections with ODU300 1.3 EPS Switching Criteria 2. RPS.1 Protection with MPT-MC 4. and HSB Management 6.2 RPS Switching Criteria 2.3 Fiber-Microwave Protection Configuration 7 8 11 12 13 15 16 20 21 22 23 24 27 28 30 31 32 33 34 35 36 37 38 39 40 43 46 49 50 55 56 60 61 Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 5 .2 Fiber-Microwave Protection Creation .1 Overview 8. All Rights Reserved.2 RPS Management 6.4 Core-E protection 5.1 ERPS operation 8 Fiber-Microwave Protection 8.3 EPS Switching Criteria 1.Page 1 Protections with ODU300 1.

Page Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 2 · Page 6 .

Edition 2. All Rights Reserved.0 Section 4 · Module 2 · Page 7 .Copyright © 2012 Alcatel-Lucent.

0 Section 4 · Module 2 · Page 8 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2.

All Rights Reserved. Edition 2.0 Section 4 · Module 2 · Page 9 .Legend: •1 •2 •3 RPS EPS HSB Copyright © 2012 Alcatel-Lucent.

Edition 2. All Rights Reserved.Legend: 2 EPS Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 10 .

Edition 2.0 Section 4 · Module 2 · Page 11 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

0 Section 4 · Module 2 · Page 12 . All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.

0 Section 4 · Module 2 · Page 13 . Edition 2. All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.0 Section 4 · Module 2 · Page 14 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 2 · Page 15 .

All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 16 .

0 Section 4 · Module 2 · Page 17 . All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent.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.0 Section 4 · Module 2 · Page 18 . Edition 2. All Rights Reserved.

Edition 2.0 Section 4 · Module 2 · Page 19 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

aimed to reach a quick reaction time and increasing significantly the quality of the radio interface in the Rx side. The Enhanced RPS switching criterion depends on the presence of errors in the decoded LDPC word. The Enhanced RPS assumes that the "classical" RPS criteria are used to give indication about the "preferred" channel.0 Section 4 · Module 2 · Page 20 .Notes: • MPT-HCV2/MPT-XP supports a further embedded functionality called "Enhanced RPS". whose frame has to be selected. • • • Copyright © 2012 Alcatel-Lucent. All Rights Reserved. when the frame-based choice between the 2 streams is not possible (e. due to the frame alignment error). Edition 2. It assumes the alignment between the 2 received radio channels and it is based on frame by frame selection of the "best" frame between the frames received from the Main and the Spare radio channel. Enhanced RPS is a frame-based protection mechanism.g.

0 Section 4 · Module 2 · Page 21 .Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.

All Rights Reserved. if there is an inter-MPT coupling link failure.Notes: Where there is a cross configuration (EPS on Spare & TPS on main). Copyright © 2012 Alcatel-Lucent. HSB (TPS) will switch and align with EPS position. Edition 2.0 Section 4 · Module 2 · Page 22 .

0 Section 4 · Module 2 · Page 23 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.

Edition 2. The actual improvement will depend on the native discrimination provided at antenna alignment. XPIC typically provides 20 dB improvement in polarization discrimination. Copyright © 2012 Alcatel-Lucent. All Rights Reserved. and any reduction of this discrimination caused by atmospheric effects (fading).Notes: • • • This function is implemented by installing the “RPS+XPIC” external module).0 Section 4 · Module 2 · Page 24 .

All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 25 .

0 Section 4 · Module 2 · Page 26 . Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2.0 Section 4 · Module 2 · Page 27 .

All Rights Reserved. Edition 2.0 Section 4 · Module 2 · Page 28 .Copyright © 2012 Alcatel-Lucent.

0 Section 4 · Module 2 · Page 29 .Notes: • • Since there is no coupling link in the current release the TPS Operator Commands are not supported. Edition 2. Copyright © 2012 Alcatel-Lucent. Only Operator Commands for EPS are supported. All Rights Reserved.

The Enhanced RPS assumes that the "classical" RPS criteria are used to give indication about the "preferred" channel. Enhanced RPS is a frame-based protection mechanism. All Rights Reserved. whose frame has to be selected. when the frame-based choice between the 2 streams is not possible (e. Copyright © 2012 Alcatel-Lucent. due to the frame alignment error). aimed to reach a quick reaction time and increasing significantly the quality of the radio interface in the Rx side. Edition 2.Notes: • MPT-MC supports a further embedded functionality called "Enhanced RPS".0 Section 4 · Module 2 · Page 30 .g. • • The Enhanced RPS switching criterion depends on the presence of errors in the decoded LDPC word.

All Rights Reserved.0 Section 4 · Module 2 · Page 31 . Edition 2.Copyright © 2012 Alcatel-Lucent.

0 Section 4 · Module 2 · Page 32 .Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.

0 Section 4 · Module 2 · Page 33 . Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2. Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 34 . are available (via back panel) to each peripheral in order to allow to each logic to take the same decision.Notes: All the switching criteria coming from both the Core units.

Edition 2. All Rights Reserved.Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 35 .

0 Section 4 · Module 2 · Page 36 . Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2.0 Section 4 · Module 2 · Page 37 .Copyright © 2012 Alcatel-Lucent.

the application SW refuses/removes a manual switch command. All Rights Reserved. Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 38 .Notes: In case of stand-by Flash Card realignment in progress. Edition 2.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Section 4 · Module 2 · Page 39 . Edition 2.

All Rights Reserved. Edition 2.0 Section 4 · Module 2 · Page 40 .Copyright © 2012 Alcatel-Lucent.

0 Section 4 · Module 2 · Page 41 . Edition 2.Notes: Restoration Criteria field: the possible values are Revertive (automatic restoration allowed) or not Revertive (automatic restoration Inhibited). Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

independently of the possible active alarms. • • • • • Some commands are not supported by selected elements. In both case. If this command is active. Edition 2. Note: The “Forced” command for channel 1 is equivalent to the “Lockout” command for the channel 0. the result is that the relevant channel protection path is forced to standby status. Copyright © 2012 Alcatel-Lucent.Notes: • The operator by the Craft Terminal can modify the state of the switch through commands Lockout. it will be removed by an incoming alarm. Forced and Manual. Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel).0 Section 4 · Module 2 · Page 42 . Select the suitable command and click on Apply. independently of the possible active alarms. Forced has higher priority than the automatic operation: the activation of this command forces in service Channel 0. Warning: All the commands are not error free. It cannot be performed if Lockout or Forced commands are already activated. All Rights Reserved. Manual has the lowest priority: it is performed only if there are no alarms that can activate an automatic switch. Automatic Switch is the normal operation condition: the position of the switch depends on the commands generated by the logic.

Notes: The Alarms tab displays the alarms that have been genereated for the selected element. Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 2 · Page 43 .

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 cable between the two MPT-HC or the two MPT-HC V2 two MPT-HC V2 • Physical cable not checked: no physical interconnection cable between the two MPT-HC or the Copyright © 2012 Alcatel-Lucent.Notes: • • Restoration Criteria field: the possible values are Revertive (automatic restoration allowed) or not Revertive (automatic restoration Inhibited).0 Section 4 · Module 2 · Page 44 . All Rights Reserved. Edition 2.

0 Section 4 · Module 2 · Page 45 . All Rights Reserved. Automatic Switch is the normal operation condition: the position of the switch depends on the commands generated by the logic. the result is that the relevant channel protection path is forced to standby status. Manual has the lowest priority: it is performed only if there are no alarms that can activate an automatic switch. independently of the possible active alarms. Select the suitable command and click on Apply. Forced has higher priority than the automatic operation: the activation of this command forces in service Channel 0. independently of the possible active alarms. • • • • • Some commands are not supported by selected elements Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel). In both case. It cannot be performed if Lockout or Forced commands are already activated. Forced and Manual. Edition 2. Copyright © 2012 Alcatel-Lucent. it will be removed by an incoming alarm. Warning: All the commands are not error free. If this command is active. Note: The “Forced” command for channel 1 is equivalent to the “Lockout” command for the channel 0.Notes: • The operator by the Craft Terminal can modify the state of the switch through commands Lockout.

0 Section 4 · Module 2 · Page 46 . All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.

0 Section 4 · Module 2 · Page 47 . Copyright © 2012 Alcatel-Lucent.Notes: Restoration Criteria field: the possible values are Revertive (automatic restoration allowed) or not Revertive (automatic restoration Inhibited). Edition 2. All Rights Reserved.

If this command is active.0 Section 4 · Module 2 · Page 48 . it will be removed by an incoming alarm. Select the suitable command and click on Apply. All Rights Reserved. the result is that the relevant channel protection path is forced to standby status. In both case. It cannot be performed if Lockout or Forced commands are already activated. Edition 2. independently of the possible active alarms. Forced and Manual. Automatic Switch is the normal operation condition: the position of the switch depends on the commands generated by the logic. Note: The “Forced” command for channel 1 is equivalent to the “Lockout” command for the channel 0. Manual has the lowest priority: it is performed only if there are no alarms that can activate an automatic switch. Some commands are not supported by selected elements Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel). Copyright © 2012 Alcatel-Lucent. Warning: All the commands are not error free.Notes: • • • • • • The operator by the Craft Terminal can modify the state of the switch through commands Lockout. Forced has higher priority than the automatic operation: the activation of this command forces in service Channel 0. independently of the possible active alarms.

Edition 2.Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 49 . All Rights Reserved.

i. • • The loop avoidance in the ring is achieved by guaranteeing that. • Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 50 . the RPL Owner. B. One designated node. • utilization of learning. and address table mechanisms defined in the Ethernet flow forwarding function. This particular link is called the Ring Protection Link (RPL). not used for traffic.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). allowing the RPL to be used for traffic. Edition 2.. Under a ring failure condition.e. All Rights Reserved. The fundamentals of this ring protection switching architecture are: • principle of loop avoidance. and C also blocked. forwarding. the RPL owner is responsible to unblock the RPL. traffic may flow on all but one of the ring links. at any time. Under normal conditions the RPL link is blocked. In the example above. is responsible to block traffic over the RPL. the RPL owner (Node A) has the RPL connection point blocked with VLANs A.

Under a ring failure condition. and C to be blocked. The connection points between Radio West and Radio East are blocked to Node D and Node C respectively.0 Section 4 · Module 2 · Page 51 . the RPL owner (Node A) is responsible for unblocking the RPL (between Node A and Radio East). Edition 2. a blocked port on Node D causes VLANs A. B. All Rights Reserved.Notes: • • • In the example above. Copyright © 2012 Alcatel-Lucent. allowing the RPL to be used for traffic.

All Rights Reserved. Each instance selects its own RPL and RPL Owner. The default value is 5 minutes.0 Section 4 · Module 2 · Page 52 . it is configured by the operator in 1 minute steps between 1 and 12 minutes. In the example above. Only revertive switching mechanism is supported. Node A owns ERP 1 (between Radio East and Node A) and ERP 2 (between Radio West and Node A). • • Copyright © 2012 Alcatel-Lucent. • to flush the learned MAC address table. • 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. The Wait-to-Restore is managed by the RPL Owner. Edition 2.Notes: • Two ERPS Control Processes are configured on each ring’s node.

during the failure Ethernet flow was dropped by the radio QoS. Edition 2. In the example above. All Rights Reserved. and D to be blocked. Under a ring failure condition.Notes: • • In the example above. the RPL owner (Node A) for ERP 1 and ERP 2 is responsible for unblocking the RPLs (between Node A and Radio East and Radio West). a blocked port on Node D causes ERP 1 and ERP 2 and VLANs A. B. allowing the RPLs to be used for traffic. C.0 Section 4 · Module 2 · Page 53 . • Copyright © 2012 Alcatel-Lucent.

0 Section 4 · Module 2 · Page 54 . All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2.

0 Section 4 · Module 2 · Page 55 . Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

0 Section 4 · Module 2 · Page 56 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.

Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 57 . All Rights Reserved. Edition 2.

the usage of two Instances to load balance traffic in the Ring is not supported. Define one of the two NEs as RPL Owner and configure the radio interface as RPL.Notes: • Create a single Instance in the Topology created before. In no-fault condition. All Rights Reserved. this will set the Ring Port related to the radio interface in blocking. Since it is requested to manage the overall traffic either over Fiber connection or over radio link. Edition 2.0 Section 4 · Module 2 · Page 58 . allowing the traffic to be forwarded over Ethernet optical connection. • Copyright © 2012 Alcatel-Lucent.

Create two Topologies in the NE acting as Node. allowing the traffic to be forwarded over Ethernet optical connection. In no-fault condition. Create a single Instance in both the Topologies created before For each Instance. define the NE acting as Node or the other NE at Tail end as RPL Owner and configure the radio interface as RPL.Notes: The scenario is supported by the MPR NE using ERPS performing the following configuration: 1. All Rights Reserved. 3. Edition 2. Copyright © 2012 Alcatel-Lucent. 2. this will left Ring Port related to radio interface in blocking.0 Section 4 · Module 2 · Page 59 . each Topology having a radio interface and an optical User Ethernet interface as Ring Ports.

Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.0 Section 4 · Module 2 · Page 60 .

All Rights Reserved.0 Section 4 · Module 2 · Page 61 .Copyright © 2012 Alcatel-Lucent. Edition 2.

Edition 2.Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 62 . All Rights Reserved.

Ring Node 2 west port R-APS MEG ID West and Ring Node 1 east port R-APS MEG ID East must be provisioned with the same value). Ring Node 1 east port R-APS MEG ID East and Ring Node 2 west port R-APS MEG ID West must be provisioned with the same value). All Rights Reserved.Notes: • R-APS MEG ID East is the ID of the east end of the ring link and must be configured to the same value as the corresponding R-APS MEG ID West value for the west end of the ring link (ex. • Copyright © 2012 Alcatel-Lucent. Edition 2. R-APS MEG ID West identifier is the ID of the west end of the ring link and must be configured to the same value as the corresponding R-APS MEG ID East value for the east end of the ring link (ex.0 Section 4 · Module 2 · Page 63 .

Copyright © 2012 Alcatel-Lucent. Edition 2.0 Section 4 · Module 2 · Page 64 . All Rights Reserved.

Notes: • • “Printing Format” is supported to manage in one shot multiple groups of VLAN IDs: i.e. 100-130.1Q Virtual Bridge). (5 -10. 150). but the TMN In-band working mode is disabled.0 Section 4 · Module 2 · Page 65 . Edition 2. Copyright © 2012 Alcatel-Lucent. • The VLANs to be protected must be first added in menu Configuration > VLAN Configuration (802. 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. All Rights Reserved.

All Rights Reserved.0 Section 4 · Module 2 · Page 66 .Copyright © 2012 Alcatel-Lucent. Edition 2.

Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Section 4 · Module 2 · Page 67 .

Edition 2.Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 68 . All Rights Reserved.

Edition 2. All Rights Reserved.Copyright © 2012 Alcatel-Lucent.0 Section 4 · Module 2 · Page 69 .

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Section 4 · Module 2 · Page 70 . Edition 2.

All Rights Reserved.0 Section 4 · Module 2 · Page 71 . Edition 2.Copyright © 2012 Alcatel-Lucent.

0 Section 4 · Module 2 · Page 72 .Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 1

This page is left blank intentionally

Document History Edition 3.4 4.0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition Updated for Release 4.0

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 2

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 3

This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 4

Page 1 MPR Node Software Download Menu 1.1 Server Access Configuration 1.2 Init Software Download 1.3 Software Status 1.4 Software Status 1.5 How to upgrade the software from an older version 7 8 9 10 11 13

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 5

This page is left blank intentionally

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 6

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 7

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 directory name from which the software can be downloaded. By clicking on the Set Default button, the server access values will be filled in automatically with the default configuration. The CT is the default FTP server with the following parameters:

• • • • • •

User Id: anonymous Password: Address: local host IP address. Port: 21 Root Dir: /

The System Default can be changed by writing different values in the fields and then by clicking OK.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 8

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 to the NE).
5. Click Yes to begin the download process. 6. When the SW download starts, a screen showing the in progress operation of the download appears. The

download is aborted if the Abort button is pressed.
7. Click Ok.

Recommended operation: Before to start the software download it is recommended to disable the ATPC operation (if it has been enabled) and to set in RTPC mode the max. Tx power. 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 and concurred downloads.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 9

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 the standby 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.
Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 10

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 11

Notes:

• •

Click the Software Units Status button. A screen opens that displays additional information on the software 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.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 12

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 13

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 4 · Module 3 · Page 14

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 5 · Module 1 · Page 1

This page is left blank intentionally

Document History Edition 3.4 4.0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition Updated for Release 4.0

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 5 · Module 1 · Page 2

A AIS AMI ANSI APT Alarm Indication Signal Alternating Mark Inversion American National Standards Institute Active Problem Table

ASAP
ASIC ATPC AVC

Alarm Severity Assignment Profile
Application Specific Integrated Circuit Automatic Transmit Power Control Attribute Value Change

B BBE BER BIP Background Block Error Bit Error Rate Bit Interleaved Parity

C CAS CD CES CESoETH CESoP CFA CLA Channel Associated Signaling Current Data Circuit Emulation Service Circuit Emulation Service over Ethernet Circuit Emulation Services over Packet Carrier Failure Alarm Common Loss Alarm

CRC
CRU CSM CSM-E CT

Cyclic Redundancy Check
Clock Reference Unit Control and Switching Module (Core module) Enhanced Control and Switching Module (Core module) Craft Terminal

D DC DL DS DS1 DS3 DSCP DWRR Direct Current Data Link Differentiated Services Digital Signal Level 1 Digital Signal Level 3 Differentiated Services Code Point Deficient Waited round Robin
Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 5 · Module 1 · Page 3

E EAS EC ECID ECT Ethernet Access Switch Module Equipment Controller Emulation Identification Equipment Craft Terminal

EFC
EFD EOW EPS ES ETH ETSI EW

Ethernet Flow Control
Event Forwarding Discriminator Engineering Order Wire Equipment Protection Switch Errored Second Ethernet European Telecommunications Standards Institute Early Warning

F
F FAS FCS FD FE FEC FPGA Framing Frame Alignment Signal Frame Check Sequence Frequency Diversity Fast Ethernet Forward Error Correction Field Programmable Gate Array

G
GFP GigE GNE GPIO Generic Frame Protocol Gigabit Ethernet Gateway Network Element General Purpose I/O

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 5 · Module 1 · Page 4

H HBER HD HDB3 HET High Bit Error Ratio History Data High Density order 3 Bipolar encoding Hetero frequency

HQP
HS HSB HSDPA HSSD HW

High Queue Preempt
Hitless Switch Hot Standby High Speed Data Packet Access Hot-Standby Space Diversity Hardware

I IDU Indoor Unit

ILM
IM IP ISAM ISPB IWF

Infomodel Level Management
Information Model Internet Protocol Indexed Sequential Access Method Intra Shelf Parallel Switching Interworking Function

J JA Jitter Attenuator

JTAG
JUSM

Joint Test Action Group
Java User-based Security Model

K

L LAN LAPD LBER LIM LIU LOF LOS Local Area Network Link Access Procedure on D-channel Low Bit Error Ration Link Identifier Mismatch Line Interface Unit Loss Of Frame Loss Of Signal
Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 5 · Module 1 · Page 5

M MAC MAU MCF MCT Medium Access Control Medium Attachment Unit Message Communication Function Microwave Craft Terminal

MEF8
MEN MIB MOD300 MPR MPT MPT-HC MPT-HL MPT-MC

Metro Ethernet Forum
Metro Ethernet Network Management Information Base Radio Interface Module Microwave Packet Radio Microwave Packet Transport Microwave Packet Transport – High Capacity Microwave Packet Transport – High Power, Long Haul Microwave Packet Transport – Medium Capacity

MOD300EN Enhanced Radio Interface Module

MRTIE
MSOH MSS MTIE MXC

Maximum Relative Time Interval Error
Multiple Section Overhead Microwave Service Switch Maximum Time Interval Error Microwave Cross Connect

N NE NEtO Network Element Network Element Overview

NMS
NNI NRZ NSA NTP

Network Management System
Network Node Interface Not Return to Zero Not Service Affecting Network Time Protocol

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 5 · Module 1 · Page 6

O OC ODU ODU300 OFS ODU Controller Outdoor Unit Outdoor Unit 300 Out of Frame Second

OH
OMS OOF OS OSPF

Overhead
Operations Management System Out Of Frame Operation System Open Short Path First

P P2E3DS3 DS3 Module P32E1DS1 DS1 Module

PDH
PDU PDV PFoE PLM PLM PM PMMF PNU PPM

Plesyochronous Digital Hierarchy
Protocol Data Unit Packet Delay Variation Power Feed over Ethernet Payload Mismatch Physical Level management Performance Monitoring Physical Machine Management Function Packet Node Unit Part Per Million

PPP
PPPoE PRBS PRS PSN PSU PTU PWE3 Q QAS QoS

Point-to-Point Protocol
Point-to-Point Protocol over Ethernet Pseudo Random Binary Sequence Clock Primary Reference Source Clock Packet Switched Network Power Supply Unit Packet Transport Unit Pseudowire emulation edge to edge

Quadrature Amplitude Modulation Quality of Service

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 5 · Module 1 · Page 7

R R99 RAI RDI REI Original standard for UMTS WCDMA based network Remote Alarm Indication Remote Defect Indication Remote Error Indication

RFC
RI RPS RSOH RSL RSSI RTPC RTU RU

Remote Frequency Control
Remote Inventory Radio Protection Switching Regenerator Section Over-Head Receive Signal Level Remote Signal Strength Indication Remote Transmit Power Control Right To Use Rack Unit

S SA SD SDH SerDes SES SF SFP SGMII Service Affecting Space Diversity Synchronous Digital Hierarchy Serializer/Deserializer Severely Errored Second Signal Fail Small form-factor pluggable transceiver Serial Gigabit Media Independent Interface

SNMP
SP SP SPI SW SWP

Simple Network Management Protocol
Spare Strict Priority Serial Peripheral Interface Software Software Package

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 5 · Module 1 · Page 8

T TBI TCA TCO TD Ten Bit Interface Threshold Crossing Alarm Total Cost of Ownership Threshold Data

TDEV
TDF TDM TDM2ETH TIM TMN TPS TRCF TRCO

Time Deviation
Total Discarded Frames Time Division Multiplexed Time Division Multiplexed To Ethernet Trace Identifier Mismatch Telecommunication Management Network Transmit Protection Switching Total Received Correct Frames Total Received Correct Octets

TDM2TDM Time Division Multiplexed To Time Division Multiplexed

TRSEF
TS TSM TTF TTO TTP

Total Received Service Errored Frames
Time Slot Transmission Systems Manager Total Transmitted Frames Total Transmitted Octets Trail Termination Point

U UAS UnAvailable Second

UAT
UI UMTS

UnAvailable Time
Unit Interval Universal Mobile Telecommunications System

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Section 5 · Module 1 · Page 9

All Rights Reserved. Edition 2.V VC-n VLAN VMMF Virtual Container .n Virtual Local Area Network Virtual Machine Management Function W WCDMA WebEML WiMAX WK WRR WT WTPM Wideband Code Division Multiple Access Web Element Manager Layer Worldwide Interoperability for Microwave Access Working Weighted Round Robin Wireless Transmission Wireless Transmission Performance Monitoring X XPIC Cross-Polarized Interference Cancellation Y Z ZBTSI Zero Byte Time Slot Interchange Copyright © 2012 Alcatel-Lucent.0 Section 5 · Module 1 · Page 10 .

This page intentionally left blank Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Section 5 · Module 1 · Page 11 . Edition 2.

Edition 2.Copyright © 2012 Alcatel-Lucent.0 Section 5 · Module 1 · Page 12 . All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix A · Module 1 · Page 1 .

0 Appendix A · Module 1 · Page 2 .0 Copyright © 2012 Alcatel-Lucent.0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition Updated for Release 4. Edition 2.This page is left blank intentionally Document History Edition 3. All Rights Reserved.4 4.

Edition 2. All Rights Reserved.Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 3 .

This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Appendix A · Module 1 · Page 4 .

enabling: 1+1) 2.9 Provision VLAN 1.1 Start Provisioning Tool 2. Edition 2.8 MPT Access configuration (1+0) 2.3 Enable Plug-In Cards 1. (without A.18 Provision TMN Ethernet Port 1.21 Port VLAN Configuration 2.21 Provision IP Static Routing 1.7 Modem Provisioning 2.3 Configuration Options Screen 2.22 Network Configuration 2.1Q management 2.20 VLAN Management 2.15 Provision Ethernet Connectivity fault management 1.14 Provision QoS 1.1 General Requirements 1.23 Trusted Managers 2.4 Provision Plug-In Cards 1.0 Appendix A · Module 1 · Page 5 . (with A.19 802.22 Provision OSPF Static Routing 2 Provisioning by Provisioning tool 2.1D management 2.2 Initial Turn-up 1.10 Provision Cross-connections 1.16 Cross Connections Configuration 2.10 MPT Access configuration (prot.9 MPT Access Provisioning 2.20 Provision TMN in-band 1. M.14 XPIC Configuration 2.13 Synchronization Configuration 2.19 Provision TMN Ethernet Port 1.15 Ring Configuration 2.11 MPT Access Prov.16 Provision System 1.8 Provision NE Time 1. All Rights Reserved.6 Provision Synchronization 1.12 Provision Ethernet Ring 1.) (1+1) 2.5 Provision XPIC 1.4 Core-E Configuration 2.12 MPT Access Prov.) (1+1) 2.18 802.17 Segregated Port Configuration 2.6 STM-1 configuration 2.11 Provision AUX Cross-Connections 1. M.24 Typical Report Panel 7 8 10 14 37 67 68 69 70 71 72 73 74 75 76 77 78 83 84 85 86 87 89 91 92 95 99 100 103 104 106 110 111 116 117 119 121 125 126 127 128 129 130 132 133 134 136 137 Copyright © 2012 Alcatel-Lucent.Page 1 Initial Configuration 1.7 Provision NTP protocol 1.2 Provisioning Tool screens 2.17 Provision Local NE IP Address 1.5 E1 configuration 2.13 Provision LAG 1.

Page Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 6 . Edition 2. All Rights Reserved.

0 Appendix A · Module 1 · Page 7 . Edition 2. All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix A · Module 1 · Page 8 . All Rights Reserved.

All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 9 .

It is possible to understand when the scratch procedure is over: make a “ping” towards NE with default IP address. plug-out the Core-E board and restore the original dip-switch 2 position. 4. network. Power off the equipment 2. XCONN. synch. 5. 3. 6. Database scratch procedure: 1. The information of SWP is maintained (the stand-by and active SWP banks are not deleted). Re-plug the Core-E board in the subrack. • Average time necessary to scratch the database (from SW start): 6-7 minutes. When EC software starts. 7. After this. Re-plug the Core-E board. ecc). Copyright © 2012 Alcatel-Lucent.Notes: • • If it is necessary to scratch the MIB use the following procedure. All Rights Reserved. Move the dip-switch 2 on the Core-E board. Edition 2.0 Appendix A · Module 1 · Page 10 . detects the switch position and starts with database scratch: all the configuration information will be erased (radio parameters.

All Rights Reserved.0 Appendix A · Module 1 · Page 11 .Copyright © 2012 Alcatel-Lucent. Edition 2.

Profile: administrator Username: initial Password: adminadmin Profile: craftPerson Username: Craftperson Password: craftcraft Copyright © 2012 Alcatel-Lucent. Default User Accounts – at the NE installation time. full access to NE but not for security parameters. All Rights Reserved.0 Appendix A · Module 1 · Page 12 .Notes: • • • • • • • • • • • • Profile Types – there are four user profiles defined. Operator (person in charge to operate at the network level. only for own password. Edition 2. Administrator (full access also for NMS local system security parameters). Viewer (view screens only). CraftPerson: person in charge for installation and the mantenance at radio site. not at the radio side). two default user accounts are created on NE independently from the SNMP operating mode.

Copyright © 2012 Alcatel-Lucent. See the figure for the recommended sequence.0 Appendix A · Module 1 · Page 13 . Edition 2. All Rights Reserved. Warning: If from this NE remote NEs have to be reached.Notes: • • • Changes to provisioning do not have to be made in any particular order. if the remote NE is connected through the radio link or of the NMS Ethernet Port. remember to configure properly the Routing Protocol of the PPP RF channel. if the remote NE is connected through the Ethernet cable.

Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 14 . Edition 2. All Rights Reserved.

0 Appendix A · Module 1 · Page 15 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.

Edition 2. All Rights Reserved.0 Appendix A · Module 1 · Page 16 .Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 17 . All Rights Reserved. Edition 2.

Edition 2. All Rights Reserved.Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 18 .

Notes: This operation must be done to enable the EPS protection. Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 19 . All Rights Reserved. Edition 2.

0 Appendix A · Module 1 · Page 20 . All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Appendix A · Module 1 · Page 21 . Edition 2.

Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.0 Appendix A · Module 1 · Page 22 .

0 Appendix A · Module 1 · Page 23 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Appendix A · Module 1 · Page 24 . Edition 2.

Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 25 . Edition 2.Notes: ODU is automatically enabled when Modem Card is enabled. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2.Notes: zODU is automatically enabled when Modem Card is enabled.0 Appendix A · Module 1 · Page 26 . All Rights Reserved.

Edition 2.Notes: This operation must be done to enable the protection: 1+1 FD or 1+1 HSB. Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 27 . All Rights Reserved.

0 Appendix A · Module 1 · Page 28 .Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.

0 Appendix A · Module 1 · Page 29 . Edition 2. All Rights Reserved.Notes: Two unprotected or protected MPT-HC or MPT-MC can be connected to one MPT Access unit. Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 30 . All Rights Reserved. Edition 2.

Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 31 . All Rights Reserved. Edition 2.

Edition 2. All Rights Reserved.0 Appendix A · Module 1 · Page 32 . Copyright © 2012 Alcatel-Lucent.Notes: This operation must be done to enable the protection: 1+1 FD or 1+1 HSB.

Edition 2.0 Appendix A · Module 1 · Page 33 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

0 Appendix A · Module 1 · Page 34 . Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Edition 2. All Rights Reserved.0 Appendix A · Module 1 · Page 35 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 36 . Edition 2.

All Rights Reserved.0 Appendix A · Module 1 · Page 37 . Edition 2.Copyright © 2012 Alcatel-Lucent.

Notes: • (8): If the electrical Ethernet port has to be used as Synchronous Source. the Ethernet port must be set as Synch-E Slave. Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Appendix A · Module 1 · Page 38 . Edition 2.

Edition 2.0 Appendix A · Module 1 · Page 39 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

0 Appendix A · Module 1 · Page 40 . the Ethernet port must be set as Synch-E Slave. All Rights Reserved. Copyright © 2012 Alcatel-Lucent. Edition 2.Notes: • (7): If the electrical Ethernet port has to be used as Synchronous Source.

0 Appendix A · Module 1 · Page 41 . Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Loss of E1 data can occur.Notes: Flow Id number: is system unique and must not be repeated in radio network. Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Appendix A · Module 1 · Page 42 . Edition 2.

All Rights Reserved. Edition 2.0 Appendix A · Module 1 · Page 43 .Notes: Flow Id number: is system unique and must not be repeated in radio network. Loss of E1 data can occur. Copyright © 2012 Alcatel-Lucent.

0 Appendix A · Module 1 · Page 44 . All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Appendix A · Module 1 · Page 45 . Edition 2.

All Rights Reserved. Loss of STM-1 data can occur. Copyright © 2012 Alcatel-Lucent. Edition 2.Notes: Flow ID number is system unique and must not be repeated in radio network.0 Appendix A · Module 1 · Page 46 .

Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Appendix A · Module 1 · Page 47 .

[7] Enable. [6] Click Apply.0 Appendix A · Module 1 · Page 48 .8261. if required. Note: byte J0 is only read. [5] Enable the J0. By enabling the Node Timing the E1 streams in Rx side are retimed at the output with the network element clock. the E1 Node Timing Configuration. [3] Set the Auto Laser Shutdown: Enabled/Disabled ForcedOn/Disabled ForcedOff. by selecting one of the two modes (SixteenBytesFrame/OneRepeated Byte) in the Expected Receiving Value field and enter the expected value and in the Sending J0 field select one of the two modes and enter the value to be transmitted. Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.Notes: [2] Put a check mark in the Port Status box to enable the STM-1. if required. This field will appear only if the Settings tab-panel of the STM-1 unit the optical SFP has been selected. no Regeneration section Termination is done. The enabling of the Node Timing is applied to all E1s of the unit. The Node Timing is the timing from the network clock as defined in G. [4] Select the Clock Source.

[14] Fields ECID Tx. Payload Size and TDM Clock Source can be written only if the Service Profile is TDM2Eth. Enter the Flow identifier value in the relevant field (possible values: 2 to 4080) and press Apply. Copyright © 2012 Alcatel-Lucent. [12] Service Profile: The possible profiles are: z TDM2TDM z TDM2Eth [13] Flow Id: To implement cross-connections between line side and radio side each E1 tributary must be associated to an identifier. The E1s are identified by a progressive number from #1 to #63. Note: The service profile must be the same for all the E1s.Notes: [8] Configure all the E1s to be mapped/demapped in the STM-1. but also by the standard SDH identification (x-y-z). Edition 2. [9] Select Settings. [10] Signal Mode: The possible values are: z Unframed for the unframed received signal z Framed for the collection of the performances at the input in Tx side and at the output in Rx side z Disabled [11] Click Apply. [15] Alarm profile: Not implemented now. [16] Click Apply. All Rights Reserved. ECID Rx.0 Appendix A · Module 1 · Page 49 . The E1 tab-panel performs all available functions for the tributary.

All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 50 .

All Rights Reserved. Edition 2. Copyright © 2012 Alcatel-Lucent.Notes: With the Presetting mode the Adaptive modulation is disabled.0 Appendix A · Module 1 · Page 51 .

Notes: • • • When the Mode is changed from Presetting to Adaptive Modulation. the radio defaults to 14 MHz bandwidth at 4 QAM. 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. Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 52 . All Rights Reserved. Edition 2. Adaptive Modulation will not enable. If the capacity of the radio (number of E1 lines cross connected) exceeds the available capacity of a 14 MHz Channel at 4 QAM.

Edition 2.Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 53 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 54 . All Rights Reserved. Edition 2.

All Rights Reserved. Edition 2.0 Appendix A · Module 1 · Page 55 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 56 .

0 Appendix A · Module 1 · Page 57 . All Rights Reserved. • remove the power supply.Notes: • To unprovision an MPT: • perform a Tx Mute. Edition 2. Copyright © 2012 Alcatel-Lucent. • unprovision the MPT.

Copyright © 2012 Alcatel-Lucent. Edition 2. The XPIC can be configured in 1+0 or 1+1 HSB (no adaptive modulation. no ATPC). Select the suitable Polarization: Vertical or Horizontal.Notes: • • • • With the Presetting mode the Adaptive modulation is disabled. This field is available only with the MPT-HC V2 with the XPIC+RPS external module installed and if in the Mode area in the Option field a mask with XPIC has been selected.0 Appendix A · Module 1 · Page 58 . NOT ALL the channel spacings and modulation schemes can support the XPIC Configuration. All Rights Reserved.

0 Appendix A · Module 1 · Page 59 . Edition 2. All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.0 Appendix A · Module 1 · Page 60 .

Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix A · Module 1 · Page 61 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Appendix A · Module 1 · Page 62 .

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. All Rights Reserved. Edition 2.0 Appendix A · Module 1 · Page 63 . Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.Notes: Configuration the Ethernet ports as explained in S3-M2.0 Appendix A · Module 1 · Page 64 . Copyright © 2012 Alcatel-Lucent. Edition 2.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Appendix A · Module 1 · Page 65 . Edition 2.

Edition 2. For the ATM traffic the Traffic Descriptors must be also configured.0 Appendix A · Module 1 · Page 66 . Refer to Menu Configuration > Traffic Descriptors in S3-M1. Copyright © 2012 Alcatel-Lucent. All Rights Reserved.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.

0 Appendix A · Module 1 · Page 67 . Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Appendix A · Module 1 · Page 68 . Edition 2.

which shows the reachability of the NTP servers.Notes: • Put a check mark in the NTP protocol field to enable the protocol and write in the Main Server address field the IP address of the server. if any. 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. The Server reachability field is a read-only field. All Rights Reserved. Refresh push-button can be used to update the screen. In the Spare Server address field write the IP address of the Spare Server.0 Appendix A · Module 1 · Page 69 . which is in charge to distribute the time to all the NEs in the network. Copyright © 2012 Alcatel-Lucent. Edition 2.

All Rights Reserved. Time and date provisioning is accomplished using the NE Time Configuration screens.0 Appendix A · Module 1 · Page 70 .Notes: The user can synchronize the NE time from either the PC/laptop or Network Time Protocol (NTP) servers. Copyright © 2012 Alcatel-Lucent. Edition 2.

All Rights Reserved.0 Appendix A · Module 1 · Page 71 .Copyright © 2012 Alcatel-Lucent. Edition 2.

Edition 2. All Rights Reserved.0 Appendix A · Module 1 · Page 72 .Copyright © 2012 Alcatel-Lucent.

0 Appendix A · Module 1 · Page 73 . All Rights Reserved.Notes: • Valid Cross Connections: • Local User Service Cross-Connection • Pass-through User Service Cross-Connection Copyright © 2012 Alcatel-Lucent. Edition 2.

0 Appendix A · Module 1 · Page 74 .Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.

0 Appendix A · Module 1 · Page 75 . Edition 2. All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Appendix A · Module 1 · Page 76 .

All Rights Reserved.0 Appendix A · Module 1 · Page 77 . Edition 2.Copyright © 2012 Alcatel-Lucent.

quality of service classification. Copyright © 2012 Alcatel-Lucent. Edition 2. and enter NE MAC address. All Rights Reserved.Notes: Follow the steps to provision tributary port impedance.0 Appendix A · Module 1 · Page 78 .

The lease time is fixed to 10 minutes. click Apply.To activate the DHCP server. defined according to the NE TMN port IP address. The PC must be configured to get automatically an IP address. Edition 2. • The DHCP server uses an address pool of 10 IP addresses.Notes: 1) Tributary Port Configuration • This field allows to set the suitable impedance of the E1 stream (Unbalanced 75 ohms/Balanced 120 ohm). 2) DHCP • The DHCP server configures automatically IP address. • The IP mask is set to the mask of the NE TMN port and the default gateway is set to the NE IP address.0 Appendix A · Module 1 · Page 79 . IP mask and default gateway of the PC Ethernet interface used to reach the NE. All Rights Reserved. select Enabled and click Apply. To activate the new impedance. Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. all the TDM traffic is impacted. Default: “Enabled”. In this case. As soon as the RSL value further decreases. modulation schemes are downgraded first from 64QAM to 16QAM: the traffic with lower priority exceeding 16QAM bandwidth is dropped and of course the E1s are kept. • It is possible to provision a number of E1s exceeding the 4QAM throughput. the check is performed taking into account the capacity of the 4 QAM modulation scheme for the relevant Channel Spacing.0 Appendix A · Module 1 · Page 80 . but without giving up the benefits of adaptive modulation for Ethernet traffic. modulation scheme are downgraded to 4QAM and all the traffic exceeding 4QAM bandwidth is dropped (while the E1s are kept). This feature is answering the need of transmitting an high number of E1s. the remaining capacity is devoted to other types of traffic such as ATM or Ethernet. the maximum number of E1s that could be provisioned is 18.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. when RSL value degrades and modulation scheme is downgraded from 16QAM to 4QAM. All Rights Reserved. Edition 2. • Taking as example 28 MHz channel spacing (with around 130 Mbit/s of net throughput available with 64QAM). the check is performed taking into account the capacity of the highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-1664 QAM range or 16 QAM for 4-16 QAM range). • When the Admission Control is "Disabled". up to 37E1s (value linked with 16QAM capacity). • When the Admission Control is "Enabled". • When RSL value decreases. always keeping 28 MHz channel as example. it is possible to provision more than 18E1s.

Copyright © 2012 Alcatel-Lucent. Ethernet interfaces in case of Core protection switching.0 Appendix A · Module 1 · Page 81 . • This behavior allows to reduce the out of service time of user traffic passing through the User • This feature shall not be used.Notes: 4) Ethernet LOS Criteria • By enabling this feature the following additional criteria are added to the Core protection switching criteria: • LOS of Optical User Ethernet interface • Card Fail of SFP optical module • Card Missing of SFP optical module • LOS of any Electrical User Ethernet interfaces. Edition 2. All Rights Reserved. when the NE is connected to an equipment performing Link Aggregation and not supporting Active/Standby management of aggregated links. but the Ethernet traffic is not forwarded. including the LOS of the forth User Ethernet interface working as TMN Local Ethernet interface. • Note: the default switching criteria are: • Core Card Missing • Core Card Fail • 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 (as the ports of the Active Core-E unit).

Edition 2. which shows the MAC address of the NE. determines the System Aggregation Priority (8 bytes).0 Appendix A · Module 1 · Page 82 . • System Aggregation Priority: • [0 .535 (default: 32. • The Ports are selected for aggregation by each System based upon the port priority assigned by the System with the higher System Aggregation Priority. This MAC address must be used in the cross-connection with TDM2Eth profile.7 bytes] NE MAC address • The System Aggregation Priority of each System is an eight octet binary number. applying the particular constraints imposed on the System concerned. 7) Event and Alarm Log • As default the Logging is enabled. The System with the numerically lower value of System Aggregation Priority has the higher priority. starting with the highest priority port of the System with the higher priority. Copyright © 2012 Alcatel-Lucent.Notes: 6) System Priority Parameter • This parameter is required to provision the System Priority (2 bytes) associated to the NE.768).1 bytes] System Priority • [2 . If set to "Disabled" the events are not sent to the Event Log Browser application. • This parameter. All Rights Reserved. and working downward through the ordered list of Port Aggregation Priority values for the N ports. 8) NE MAC Address • This field is a read-only field. The range for the System Priority parameter is: 0 to 65. together with the System ID (the NE MAC address).

the NE restarts. Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 83 . Edition 2. All Rights Reserved.Notes: After IP address change.

0 Appendix A · Module 1 · Page 84 .Notes: Follow the steps to provision TMN Ethernet on the Core-E Card to carry SNMP data. Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.

All Rights Reserved. Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix A · Module 1 · Page 85 .Notes: Follow the steps to provision TMN Ethernet on the Core-E Card to carry SNMP data.

Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix A · Module 1 · Page 86 . All Rights Reserved.

All Rights Reserved. Edition 2.Note: Follow the steps to provision. Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 87 .

All Rights Reserved. Edition 2.0 Appendix A · Module 1 · Page 88 .Copyright © 2012 Alcatel-Lucent.

0 Appendix A · Module 1 · Page 89 . Edition 2. Copyright © 2012 Alcatel-Lucent.Notes: Follow the steps to provision Open Shortest Path First (OSPF) protocol static (automatic) routing. All Rights Reserved.

All Rights Reserved.0 Appendix A · Module 1 · Page 90 . Edition 2.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Edition 2.0 Appendix A · Module 1 · Page 91 .

All Rights Reserved.0 Appendix A · Module 1 · Page 92 . Edition 2.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix A · Module 1 · Page 93 . All Rights Reserved.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix A · Module 1 · Page 94 .

• With the online mode you can either apply the "offline" configuration or fulfill online. Copyright © 2012 Alcatel-Lucent. the IP address to be entered is the IP address of the NMS Ethernet port. for this reason your PC must be configured to obtain an IP Address automatically). • • • • 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 for provisioning WebEML is more flexible and mandatory to configure AUX and ATM boards (not yet supported in provisioning tool). Select: • the direct connection to the NE by putting a check mark on “Connect to NE”. • In case of offline. in the IP Address field automatically (through the autodiscovery) appears the IP Address of the NE (in the NE the default configuration of the DHCP server is enabled.0 Appendix A · Module 1 · Page 95 . • or • the off-line configuration by putting a check mark on “Do not connect to NE” and by clicking on Apply. Minimizing time on field and mistakes. Edition 2. When you locally connect the PC to the NE. All Rights Reserved. • Click on OK.Notes: •The Provisioning Tool can be used "offline" and "online". • If the DHCP server is disabled. it allows to prepare the provisioning in back office.

Copyright © 2012 Alcatel-Lucent. • Cancel: not operative.0 Appendix A · Module 1 · Page 96 . the user will see a configuration preview in order to understand. After opening a configuration file. If an older configuration file is open a new screen appears.Notes: • The buttons present in this screen has the following meaning: • Open: allows opening an existing MCML (XML-based) configuration file. • Help: by clicking on this button the operator calls the help on line. Edition 2. which gives the possibility to open a configuration file created in an older version. MCML file can contains NE configuration data and it can be used to fill panels fields and data. Click " Next" button from such preview panel or "Create" button. which asks to convert the file. for example. All Rights Reserved. • • • By clicking on the "Open" button a window opens. • Get: not operative. By clicking on the "Create" button it will be possible to create a file in the current version or in the older version. • Create: allows to create a new configuration file. if the file is correct and contains the wanted configuration. • Prev: not operative.

for example. the user will see a configuration preview in order to understand. All Rights Reserved. which asks to convert the file. By clicking on the "Create" button it will be possible to create a file in the current version or in the older version. • Cancel: not operative. if the file is correct and contains the wanted configuration. Copyright © 2012 Alcatel-Lucent. which gives the possibility to open a configuration file created in an older version. MCML file can contains NE configuration data and it can be used to fill panels fields and data.0 Appendix A · Module 1 · Page 97 . the configuration from the NE to the tool. • Get: this button is operative if you are physically connected to the NE and it is used to upload • Create: allows to create a new configuration file. If an older configuration file is open a new screen appears. • • • By clicking on the "Open" button a window opens. • Help: by clicking on this button the operator calls the help on line. Edition 2. Click " Next" button from such preview panel or "Create" button.Notes: • The buttons present in this screen has the following meaning: • Open: allows opening an existing MCML (XML-based) configuration file. After opening a configuration file. • Prev: not operative.

but you cannot apply the configuration to the NE.0 Appendix A · Module 1 · Page 98 . All Rights Reserved. Edition 2.Note: • • Press the Clear Database and Restart NE button and then press Create to create a new configuration or press Open to open a previously created configuration. Copyright © 2012 Alcatel-Lucent. If you don't press the Clear Database and Restart NE button at the end of the configuration you can save the file. (The Apply button will not be available at the end of the procedure).

(The EAS unit. except the EAS unit. Warning: To configure the equipment extract the ASAP and/or AUX units. if the remote NE is connected through the Ethernet cable. ASAP unit and the AUX unit must be configured with the LCT). Protections options shown are for all cards. ASAP unit and AUX unit. 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.Notes: • • • • This screen is a generic one that depicts all of the pull-down options possible depending on which card is selected in the card slot. if any. Edition 2. remember to configure properly the Routing Protocol of the TMN-RF channel. Warning: the Provisioning Tool allows to configue all the units. Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 99 . All Rights Reserved. Buttons: • Restore: allows to restore in the screen the initial data without any change • Prev: the procedure goes back to the previous step (the changed data may be lost after the Warning message) • Next: the procedure goes on to the next step (some checks and data storage is done) • Cancel: the procedure goes back to step 1 (Opening screen) • Help: by clicking on this button the operator calls the help on line. if the remote NE is connected through the radio link or of the NMS Ethernet Port.

The limits granted by the license key have been exceeded. but cross-connections can be created. Edition 2. A green icon indicates that the source and destination are available and the destination can accept more E1 ports.0 Appendix A · Module 1 · Page 100 . All Rights Reserved. A message is also displayed stating that no more E1 ports will be accepted. A blue icon indicates the destination is full.Notes: • • • A white icon indicates that there are no cross-connections. Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.0 Appendix A · Module 1 · Page 101 .

All Rights Reserved. Edition 2.0 Appendix A · Module 1 · Page 102 .Copyright © 2012 Alcatel-Lucent.

Real Time Protocol is used) or Adaptive (RTP is not used). Edition 2. with the TDM2Eth service profile the TDM Clock source can be Differential (RTP .0 Appendix A · Module 1 · Page 103 . In the unit it is not possible to have mixed configurations with service profiles using RTP and other service profiles not using RTP. If the Adaptive clock source is requested the E1 must be connected to another PDH unit.Real Time Protocol is used).Notes: • • • • With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP . Copyright © 2012 Alcatel-Lucent. All Rights Reserved. Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure other E1 with service profile TDM2Eth only with the Differential clock source (not with the Adaptive clock source).

Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix A · Module 1 · Page 104 . All Rights Reserved.

Edition 2. All Rights Reserved.0 Appendix A · Module 1 · Page 105 .Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.0 Appendix A · Module 1 · Page 106 . Edition 2.Copyright © 2012 Alcatel-Lucent.

Edition 2. All Rights Reserved.Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 107 .

Edition 2. The same power value will be used by the 16 QAM and 64 QAM modulation schemes. • Copyright © 2012 Alcatel-Lucent.Notes: • • With the Adaptive Modulation the only available configuration is: 1+0 or 1+1 HSB. which will be used with 4 QAM modulation. The operator can modify only the 4 QAM field. The power range is shown on the right side and depends on the selected reference mode.0 Appendix A · Module 1 · Page 108 . In this field the operator has to enter the constant power. All Rights Reserved.

All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 109 .

Notes: The selection of the Power Supply mode to supply the MPT can be: PFoE (through 1 cable for MPTMC or MPT-HC with the DC Extractor) or QMA (through 2 cables for MPT-HC). All Rights Reserved. Edition 2.0 Appendix A · Module 1 · Page 110 . Copyright © 2012 Alcatel-Lucent.

Notes: • • • • This field is available only with the MPT-HC V2 with the XPIC+RPS external module installed and if in the Mode area in the Option field a mask with XPIC has been selected. NOT ALL the channel spacings and modulation schemes can support the XPIC Configuration. The XPIC can be configured in 1+0 or 1+1 HSB (no adaptive modulation. no ATPC). To configure the XPIC go to “MPT-HC V2 with XPIC” slide. All Rights Reserved. Edition 2.0 Appendix A · Module 1 · Page 111 . Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.0 Appendix A · Module 1 · Page 112 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix A · Module 1 · Page 113 .

Edition 2.Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 114 . All Rights Reserved.

0 Appendix A · Module 1 · Page 115 .Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.0 Appendix A · Module 1 · Page 116 .

To configure the XPIC go to “MPT-HC V2 with XPIC” slide.Notes: • • • • This field is available only with the MPT-HC V2 with the XPIC+RPS external module installed and if in the Mode area in the Option field a mask with XPIC has been selected. Copyright © 2012 Alcatel-Lucent. no ATPC). NOT ALL the channel spacings and modulation schemes can support the XPIC Configuration. The XPIC can be configured in 1+0 or 1+1 HSB (no adaptive modulation.0 Appendix A · Module 1 · Page 117 . All Rights Reserved. Edition 2.

Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 118 . Edition 2. All Rights Reserved.

All Rights Reserved.0 Appendix A · Module 1 · Page 119 . Edition 2.Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix A · Module 1 · Page 120 . All Rights Reserved.

0 Appendix A · Module 1 · Page 121 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2.

0 Appendix A · Module 1 · Page 122 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2.

All Rights Reserved.Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 123 . Edition 2.

Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 124 . Edition 2. All Rights Reserved.

Edition 2. Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 125 . All Rights Reserved.Notes: To configure the XPIC refer to S3-M2.

0 Appendix A · Module 1 · Page 126 .Notes: To configure the XPIC refer to S3-M2. Edition 2. Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved. Edition 2.0 Appendix A · Module 1 · Page 127 . Copyright © 2012 Alcatel-Lucent.Notes: To create the Cross-Connection refer to S3_M3.

All Rights Reserved.0 Appendix A · Module 1 · Page 128 .Notes: To segregate the ports refer to S3_M3 Copyright © 2012 Alcatel-Lucent. Edition 2.

0 Appendix A · Module 1 · Page 129 . Edition 2. All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

0 Appendix A · Module 1 · Page 130 .Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.

0 Appendix A · Module 1 · Page 131 . Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters. This means that a disabled port can be configured as a member of a VLAN and a port already member of a VLAN can be disabled continuing to be a member of the same VLAN.0 Appendix A · Module 1 · Page 132 . The VLAN cannot be removed from the radio ports (with the exception of the VLAN 1). for the VLAN IDs defined. which means all the frames are transmitted with Tag. VLAN ID field: Enter the VLAN ID (the configurable values must be in the range 2 . There is no check on unambiguity name. Untagged Ports field: Select. Only the user Ethernet ports. Both enabled and disabled user Ethernet ports (radio ports when declared are implicitly enabled) can be member of a VLAN. the untagged ports (in egress the VLAN will be removed from the frames).Notes: 1. 4.4080. the packet is dropped. 3. By default. • • Copyright © 2012 Alcatel-Lucent.e.4080) • 2. The VLAN IDs already defined to cross-connect internal flows (i. all the ports are members and the Untag flag is set to “False”.If one tagged packet with VLAN-ID X is received on a port which is not member of the VLAN-ID X. TDM2ETH) can-not be used. The VLAN-ID values allowed are in the range 2 . TDM2TDM. enabled and disabled. among the ports belonging to this VLAN (members). All Rights Reserved. Edition 2. All the user Ethernet ports and all the Radio directions can be considered. • VLAN Ports field: Select the ports members of this VLAN by putting a check mark on the relevant check box. are manageable. Tagged frames .

Edition 2.Notes: The Port VLAN Configuration screen opens only if in the Bridge Configuration screen the 802. All Rights Reserved.1Q (Virtual Bridge) has been selected. Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 133 .

All Rights Reserved. Edition 2.0 Appendix A · Module 1 · Page 134 .Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix A · Module 1 · Page 135 . All Rights Reserved.

Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 136 . All Rights Reserved.Notes: A Trusted manager is an SNMP manager to which the NE automatically sends the TRAPS generated inside the NE. Edition 2.

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 the download of the configuration to the NE • Cancel: the procedure goes back to step 1 (Opening screen) Copyright © 2012 Alcatel-Lucent.0 Appendix A · Module 1 · Page 137 . All Rights Reserved. Edition 2.

Copyright © 2012 Alcatel-Lucent. All Rights Reserved.0 Appendix A · Module 1 · Page 138 . Edition 2.

0 Appendix A · Module 1 · Page 139 .This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.

Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.0 Appendix A · Module 1 · Page 140 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent.0 Appendix B · Module 1 · Page 1 . Edition 2.

All Rights Reserved.0 Copyright © 2012 Alcatel-Lucent.0 Appendix B · Module 1 · Page 2 .This page is left blank intentionally Document History Edition 3. Edition 2.4 4.0 Date 2012-07-01 2012-09-14 Author AL University AL University Remarks First edition Updated for Release 4.

0 Appendix B · Module 1 · Page 3 . Edition 2.Copyright © 2012 Alcatel-Lucent. All Rights Reserved.

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent.0 Appendix B · Module 1 · Page 4 . Edition 2.

3 TMN communication channels 1. Edition 2. All Rights Reserved.Page 1 MPR Management 1.2 MPR IP addresses 1.4 TMN interfaces (9500 MPR Node) 1.5 LCT Connection 1.0 Appendix B · Module 1 · Page 5 .1 9500 MPR Management 1.6 MPR Capability – IP Parameters 7 8 9 11 12 13 14 Copyright © 2012 Alcatel-Lucent.

All Rights Reserved.This page is left blank intentionally Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix B · Module 1 · Page 6 .

All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.0 Appendix B · Module 1 · Page 7 .

Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix B · Module 1 · Page 8 . All Rights Reserved.

0 Appendix B · Module 1 · Page 9 . Edition 2.Notes: Refer to the attached diagram as an example of the IP address assignment. All Rights Reserved. Copyright © 2012 Alcatel-Lucent.

Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix B · Module 1 · Page 10 . All Rights Reserved.

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. IP/subnet TMN In-Band interface #2. Edition 2. • • • • • NE Local IP Address TMN Local Ethernet interface. IP/subnet TMN Out-of-Band interface on User Ethernet port 4.Notes: • With the introduction of TMN In-Band two new IP interfaces are added to those already available. All Rights Reserved. These interfaces must have different IP subnets.0 Appendix B · Module 1 · Page 11 . IP/subnet TMN In-Band interface #1. Copyright © 2012 Alcatel-Lucent.

All Rights Reserved. Edition 2.Copyright © 2012 Alcatel-Lucent.0 Appendix B · Module 1 · Page 12 .

Copyright © 2012 Alcatel-Lucent. Edition 2. All Rights Reserved.0 Appendix B · Module 1 · Page 13 .

All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2.0 Appendix B · Module 1 · Page 14 .

0 Appendix B · Module 1 · Page 15 . All Rights Reserved.Copyright © 2012 Alcatel-Lucent. Edition 2.

All Rights Reserved. Edition 2.0 Appendix B · Module 1 · Page 16 .Copyright © 2012 Alcatel-Lucent.

0.… VLAN ID NE IP NMS IP NE MAC NMS P4 OSPF AREA 10.30.2 00:20:60:05:02:08 OFF 0.6 00:20:60:05:02:05 10.0 Appendix B · Module 1 · Page 17 10.5 00:20:60:05:02:06 OFF 0.Example of MPR IP addresses VLAN ID NE IP 1 Management System 10.0.0.5.0.0.0.1 All Rights Reserved © Alcatel-Lucent @@YEAR Node C @@SECTION · @@MODULE · 20 @@SECTIONTITLE · @@MODULETITLE @@PRODUCT · @@COURSENAME ETH Generator PDH Generator Syncro Scheme Net Mask 255.0.… Port Number 1.1 Node A TDM A ETH 1 ETH 2 VLAN ID DEFAULT GATEWAY 1+1 HSB Traffic E1+ETH TMN Traffic E1 TDM2ETH Traffic E1 TDM2TDM Traffic ETH 1.0.10.4.0.0.6 10.0.5.3.3.3.0.3 00:20:60:27:02:07 OFF 0.6.1 NE IP NMS IP NE MAC NMS P4 OSPF AREA Copyright © 2012 Alcatel-Lucent.10.0.0.2.1 ETH 2 .3.4 10.4.1 3132 00:20:60:05:02:07 OFF 0. Edition 2.100 10.1 NMS IP NE MAC NMS P4 OSPF AREA Example 10.6 ETH 1 VLAN ID 41 42 10 11 Node E Node F TDM B NE IP NMS IP NE MAC NMS P4 OSPF AREA 10.0.0.6.5 10.0.100 10.0.3.10.0.1 27 28 1 2 Node B TDM C NE IP NMS IP NE MAC NMS P4 OSPF AREA 10.1 11 12 13 14 VLAN ID 1+1 FD 5 6 7 8 Node D PC IP DEFAULT GATEWAY 10.255.1 of MPR IP addresses 1 2 3 4 17 18 11 12 13 14 27 28 41 42 TDM B TDM C PC IP 10.0.0 TDM A NE IP NMS IP NE MAC NMS P4 OSPF AREA 10.255.0.2 10.6 0.0.0.3.30.4 00:20:60:27:02:05 10.0.2.0.0.0. All Rights Reserved.0.6.4 0.0.3 10.0.

0 Appendix B · Module 1 · Page 18 . Edition 2. All Rights Reserved.Copyright © 2012 Alcatel-Lucent.

Page 1 .All Rights Reserved © Alcatel-Lucent @@YEAR @@COURSENAME .

All rights reserved © Alcatel-Lucent Passing on and copying of this document.Page 2 . use and communication of its contents not permitted without written authorization from Alcatel-Lucent All Rights Reserved © Alcatel-Lucent @@YEAR @@COURSENAME .

Sign up to vote on this title
UsefulNot useful