Alcatel-Lucent 5620 SERVICE AWARE MANAGER MPR USER GUIDE R7 December HE AAAG TQZZA Edition 01

Transcription

1 MPR USER GUIDE 12.0 R7 December HE AAAG TQZZA Edition 01 Alcatel-Lucent 5620 SERVICE AWARE MANAGER MPR USER GUIDE Alcatel-Lucent Proprietary This document contains proprietary information of Alcatel-Lucent and is not to be disclosed or used except in accordance with applicable agreements. Copyright 2014 Alcatel-Lucent. All rights reserved.

2 Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change without notice. Alcatel, Lucent, Alcatel-Lucent, the Alcatel-Lucent logo, lightradio, and TiMetra are registered trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. Copyright 2014 Alcatel-Lucent. All rights reserved. Disclaimers Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, license or other distribution of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications. This document may contain information regarding the use and installation of non-alcatel-lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-alcatel-lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete information provided about non-alcatel-lucent products. However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers. This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail. When printed by Alcatel-Lucent, this document is printed on recycled paper.

3 Contents Getting started 1 What s new? What s new in Release 12.0 for 9500 MPR and 9500 MPRe devices Deprecation notice Maintenance releases What s new in Release 12.0 R What s new in Release 12.0 R What s new in Release 12.0 R What s new in Release 12.0 R MPR/9500 MPRe overview management of 9500 MPR/9500 MPRe devices Supported device objects, auxiliary equipment, and service types Supported MSS types IDUs and ODUs MPR/9500 MPRe card support Fan tray MPR LAG objects MPR services and service tunnel support MPR/9500 MPRe NEtO support XPIC MPRe support Workflow to manage 9500 MPR/9500 MPRe devices Alcatel-Lucent 5620 Service Aware Manager iii

4 Contents 9500 MPR/9500 MPRe management MPR/9500 MPRe device commissioning and management MPR/9500 MPRe device commissioning and management overview MPR/9500 MPRe management MPR radio link discovery and management Workflow to commission 9500 MPR/9500 MPRe devices MPR/9500 MPRe device commissioning and management procedures Procedure 3-1 To commission a 9500 MPR/9500 MPRe for management Procedure 3-2 To configure polling for 9500 MPR/9500 MPRe devices Procedure 3-3 To enable management of 9500 MPR/9500 MPRe devices MPR/9500 MPRe object configuration MPR/9500 MPRe object configuration overview Workflow to configure and manage 9500 MPR/9500 MPRe device objects MPR/9500 MPRe device object configuration procedures Procedure 4-1 To configure system settings on a 9500 MPR Procedure 4-2 To resolve 9500 MPR MIB inconsistencies Procedure 4-3 To configure a scope of command role for NEtO access Procedure 4-4 To start the 9500 MPR/9500 MPRe external element manager from the GUI Procedure 4-5 To configure a DSCP value for in-band TMN interfaces on the 9500 MPR MPR LAG object configuration Working with 9500 MPR LAG objects MPR LAG objects Workflow to configure and manage 9500 MPR LAG objects MPR LAG configuration procedures Procedure 5-1 To create an L1 radio LAG, L2 radio LAG, or Ethernet LAG on a 9500 MPR Procedure 5-2 To delete a 9500 MPR LAG MPR/9500 MPRe shelf object configuration MPR/9500 MPRe shelf object configuration overview Working with shelf objects on 9500 MPR/9500 MPRe devices Working with card and card slot objects on 9500 MPR/9500 MPRe devices MPR card support Workflow to manage shelf objects on 9500 MPR/9500 MPRe devices iv Alcatel-Lucent 5620 Service Aware Manager

5 Contents MPR/9500 MPRe shelf object configuration procedures Procedure 6-1 To migrate the 9500 MPRe connected to a 7705 SAR from standalone mode to single NE mode Procedure 6-2 To manage the 9500 MPR/9500 MPRe running software Procedure 6-3 To configure a 9500 MPR basic or advanced fan tray Procedure 6-4 To configure 9500 MPR card protection Procedure 6-5 To remove 9500 MPR card protection Procedure 6-6 To switch between a 9500 MPR in-service protected radio link and a standby protected radio link Procedure 6-7 To configure MPT-HLS radio MPR/9500 MPRe port object configuration MPR/9500 MPRe port configuration overview IMA support Combiner support MPR Ethernet port QoS schemes Workflow to manage port objects on 9500 MPR/9500 MPRe devices Port configuration procedures Procedure 7-1 To configure 9500 MPR/9500 MPRe Ethernet ports Procedure 7-2 To configure 9500 MPR 2 STM ports Procedure 7-3 To configure 9500 MPR 1 STM (Channelized) ports Procedure 7-4 To configure 9500 MPR E1 and DS1 ports Procedure 7-5 To configure 9500 MPR DS3 ports Procedure 7-6 To configure 9500 MPR AUX alarm ports Procedure 7-7 To configure a 9500 MPRe port Procedure 7-8 To configure analog performance management on 9500 MPR 1x radio modem ports Procedure 7-9 To configure power level performance management on 9500 MPR 1x radio modem ports Procedure 7-10 To configure 9500 MPR port segregation Procedure 7-11 To configure a 9500 MPR power source type Procedure 7-12 To configure synchronization on Ethernet ports Procedure 7-13 To add 9500 MPR port protection Procedure 7-14 To remove 9500 MPR port protection Procedure 7-15 To configure a loopback test on a 9500 MPR DS1, ES1, STM, or 1 x radio modem port MPR/9500 MPRe policy and service management MPR/9500 MPRe QoS policies MPR/9500 MPRe QoS policies overview ATM QoS policies NE QoS policies Radio Interface Queue Map policies Alcatel-Lucent 5620 Service Aware Manager v

6 Contents 8.2 Workflow to configure 9500 MPR/9500 MPRe QoS policies MPR/9500 MPRe QoS policies procedures Procedure 8-1 To configure and distribute a 9500 MPR ATM QoS policy Procedure 8-2 To configure and distribute a 9500 Radio Interface Queue Map policy Procedure 8-3 To configure and distribute a 9500 NE QoS policy MPR service management and service tunnels MPR service management overview Supported service types Complete transport service MPR services support MPR and 9500 MPRe service provisioning considerations and constraints MPR service tunnel overview MPR service tunnel (ERPS) support Ethernet (G.8032) rings ERP topology MPR ERPS tail node support on Ethernet (G.8032) rings Supported ERP service types Configuring service tunnels on 9500 MPR devices Procedure 9-1 To create an Ethernet radio ring element on a 9500 MPR Workflow to configure a composite service with VLAN service on the 9500 MPR and VPLS on the 7210 SAS MPR VLAN service management MPR VLAN service management overview Supported VLAN services types for 9500 MPR devices VLAN groups and paths Workflow to create VLAN services on 9500 MPR devices VLAN service management procedures for 9500 MPR devices Procedure 10-1 To create a VLAN group Procedure 10-2 To create a 9500 MPR VLAN path Procedure 10-3 To create a 9500 MPR (dot1q) VLAN service Procedure 10-4 To create a 9500 MPR (dot1ad) VLAN service Procedure 10-5 To create a CoS rate limiter per VLAN on a 9500 MPR Procedure 10-6 To discover 9500 MPR services Procedure 10-7 To delete a VLAN group or group member Procedure 10-8 To delete a 9500 MPR VLAN path MPR VLL service management MPR VLL service management overview Supported VLL services types for 9500 MPR devices Workflow to create VLL services on 9500 MPR devices vi Alcatel-Lucent 5620 Service Aware Manager

7 Contents 11.3 VLL service management procedures for 9500 MPR devices Procedure 11-1 To create a VLL Apipe service on the 9500 MPR (ETSI only) Procedure 11-2 To create a VLL Cpipe service on a 9500 MPR Procedure 11-3 To create a single site VLL Cpipe service on 9500 MPR connected to an MSS1c lightweight GNE Procedure 11-4 To discover a single-site Cpipe service on 9500 MPR connected to an MSS-1c lightweight GNE Procedure 11-5 To fix a failed cross-connection in a 9500 MPR Cpipe or a hop-based VLAN service Procedure 11-6 To configure a GNE site on a VLL service Appendices A MPR SAM-E license functionality A-1 A MPR SAM-E license functionality... A-2 Alcatel-Lucent 5620 Service Aware Manager vii

8 Contents viii Alcatel-Lucent 5620 Service Aware Manager

9 Getting started 1 What s new? MPR/9500 MPRe overview Alcatel-Lucent 5620 Service Aware Manager

10 Alcatel-Lucent 5620 Service Aware Manager

11 1 What s new? 1.1 What s new in Release 12.0 for 9500 MPR and 9500 MPRe devices 1-2 Alcatel-Lucent 5620 Service Aware Manager 1-1

12 1 What s new? 1.1 What s new in Release 12.0 for 9500 MPR and 9500 MPRe devices This section highlights new 9500 MPR and 9500 MPRe features for Release 12.0 and provides pointers into the documentation for more information about using the features. Feature lists and high-level feature descriptions are also available in the Release Description. Deprecation notice This chapter will be deprecated in Release 13.0 R1 and the feature information moved to the New Features chapter of the Documentation Map. The Documentation Map provides entry points into the customer documentation suite from various user, role, function and feature perspectives, and can be used today as an alternative to this What s new chapter for navigation to new features for the entire release. Maintenance releases Some releases may not be listed in this section, either because no new 9500 MPR or 9500 MPRe features were introduced or the features introduced do not require documentation. What s new in Release 12.0 R7 Table 1-1 describes the 9500 MPR and 9500 MPRe features added in Release 12.0 R7. Table 1-1 Release 12.0 R7 features Feature ID Feature or function Description See SAM MPT-HLS combiner configuration The supports configuration of a combiner on the MPT-HLS transceiver. Section 6.3 SAM workspace customized for 9500 MPR The supports configuration of a customized workspace for 9500 MPR. Chapter custom workspaces in the User Guide SAM MPT-HCv2 connected to EASv2 optical ports with 1+1 cross configuration The supports configuration of the MPT-HCv2 transceiver on the optical ports with 1+1 cross-configuration. Section 6.3 SAM MPT-HLS connected to EASv2 optical port in N+0 intra or cross LAG configuration with or without combiner The supports configuration of a combiner on an MPT-HLS transceiver configured on an EASv2 optical port that is associated with an N+0 intra or cross LAG. Section 6.3 SAM N+0 cross L1 LAG configuration of MPT-HCv2 connected to EASv2 electrical port. The supports N+0 cross L1 LAG configuration of MPT-HCv2 transceiver connected to the electrical ports of the EASv2 card. Section 6.3 (1 of 2) 1-2 Alcatel-Lucent 5620 Service Aware Manager

13 1 What s new? Feature ID Feature or function Description See SAM N+0 intra and inter L1 LAG configuration of MPT-MC connected to EASv2 electrical port The supports N+0 intra and cross L1 LAG configuration of MPT-MC transceiver connected to the electrical ports of the EASv2 card. Section 6.3 SAM Complete transport service support for cross-connects deleted from NEtO The supports configuration of the complete transport service action when you delete the cross-connects of the intermediate nodes from NEtO. Section 9.1 SAM Radio ports of ring and tail nodes as access The allows you to add radio ports of ring and tail nodes as access in a ring-based VLAN service. Procedure 10-3 SAM Configure and discover hop-based Cpipe services with termination point on MSS-1c GNE or 9500 MPRe The supports configuration and discovery of a hop-based Cpipe service if a radio port connecting to a MSS-1c GNE or 9500 MPRe is added as access interface in the 9500 MPR Cpipe service. Section 9.1 (2 of 2) What s new in Release 12.0 R5 Table 1-2 describes the 9500 MPR and 9500 MPRe features added in Release 12.0 R5. Table 1-2 Release 12.0 R5 features Feature ID Feature or function Description See SAM SAM MPT-HC and MPT-MC support The supports the configuration of MPT-HC and MPT-MC on the electrical ports of the EASv2 card. Section 6.3 SAM SAM SAM SAM SAM MPT-HLC support The supports the following: configuration of MPT-HLC on ports 5 and 6 of the CORE-E card or MSS-1 shelf and on ports 5 to 8 of an EASv2 card configuration of combiner on the MPT-HLC port configuration of radio L1 LAG Sections 2.1, 5.1, and 6.3 Procedure 5-1 SAM SAM MPT-HQAM support The supports the configuration of the MPT-HQAM on a 9500 MPR Release 5.2 and later. Section 2.1 SAM PoE on EASv2 cards The supports the configuration of PoE on EASv2 card. Procedure 7-11 SAM Synchronous Ethernet on EASv2 card The supports the configuration of synchronous Ethernet on EASv2 card. Procedure 7-12 SAM Remote NE auto-discovery The supports auto-discovery of the radio links. Section 3.1 NEtO distribution for 9500 MPR/9500 MPRe 5.2. The supports NEtO distribution for the 5.2 node version of the 9500 MPR and 9500 MPRe, in addition to the 5.1, 5.0, 4.2, 4.1, and 4.0 releases for 9500 MPR and the 5.1, 5.0, 4.2, and 4.1 releases for 9500 MPRe. Alcatel-Lucent 5620 Service Aware Manager 1-3

14 1 What s new? What s new in Release 12.0 R2 Table 1-3 describes the 9500 MPR and 9500 MPRe features added in Release 12.0 R2. Table 1-3 Release 12.0 R2 features Feature ID Feature or function Description See SAM Cross and intra LAG configuration support The supports configuration of cross and intra LAGs for MPT-HLS. Section 5.1 SAM MPT-HLS support The supports configuration of MPT-HLS on core-enhanced cards and EASv2 cards. Section 2.1 Procedure 6-7 SAM EASv2 card support for MPT-HLS The supports viewing the adaptive modulation values for the usage time 512 QAM and 1024 QAM in MPT-HLS Section 6.5 What s new in Release 12.0 R1 Table 1-4 lists the 9500 MPR and 9500 MPRe features added in Release 12.0 R1. Table 1-4 Release 12.0 R1 features Feature ID Feature or function Description See SAM EASv2 card support The supports EASv2 card configuration at EASv1 level. Section 6.5 SAM NEtO distribution for 9500 MPR/9500 MPRe 5.1. The supports NEtO distribution for the 5.1 node version of the 9500 MPR and 9500 MPRe, in addition to the 5.0, 4.2, 4.1, and 4.0 releases for 9500 MPR and the 5.0, 4.2, and 4.1 releases for 9500 MPRe. 1-4 Alcatel-Lucent 5620 Service Aware Manager

15 MPR/9500 MPRe overview 2.1 management of 9500 MPR/9500 MPRe devices Workflow to manage 9500 MPR/9500 MPRe devices 2-9 Alcatel-Lucent 5620 Service Aware Manager 2-1

16 MPR/9500 MPRe overview 12.0 R7 December HE AAAG TQZZA Edition management of 9500 MPR/9500 MPRe devices The Alcatel-Lucent 9500 MPR is a microwave digital radio family that supports PDH and Ethernet to migrate from TDM to IP. The 9500 MPR provides a generic, modular IP platform for multiple network applications such as 2G, 3G, HSDPA, and WiMAX to accommodate broadband services to Metro Ethernet areas. This solution improves packet aggregation, increases bandwidth and optimizes Ethernet connectivity. The 9500 MPR radio family supports low, medium, and high capacity applications using ANSI and ETSI data rates, frequencies, channel plans, and tributary interfaces. Supported device objects, auxiliary equipment, and service types The 9500 MPR consists of one MSS and one or more ODUs. The support for the 9500 MPR includes the following device objects, auxiliary equipment, and service types. MSS MSS-1 MSS-4 MSS-8 IDU and ODU ODU300 MPT-HCv2 MPT-XP MPT-MC MPT-HL MPT-HLC MPT-HLS MPT-HQAM 9500 MPR card support includes: core-enhanced card core-b card 1 radio modem card 2+2 Ethernet (EAS) card 4+4 Ethernet (EAS) card EASv2 card 2 STM card 16 E1 (ASAP) card 32 E1 card 32 DS1 card 2 DS3 card 1 STM (Channelized) card AUX alarm card basic and advanced fan trays LAG objects services and service tunnels 2-2 Alcatel-Lucent 5620 Service Aware Manager

17 MPR/9500 MPRe overview XPIC NEtO The also supports the native management of the 9500 MPRe, a variant of the 9500 MPR. See 9500 MPRe support in this section. Supported MSS types Three types of MSS can be managed by the : MSS-1 shelf The MSS-1 is a 1-rack-unit, 1-slot shelf. The first four ports of this shelf are Ethernet ports. Ports 5 and 6 are SFP ports. The shelf also supports 16 DS1 or 16 E1 ports. The MSS-1 shelf supports only the following types of services on the : VLL (Cpipe only) VLAN Note 1 The equipment tree in the GUI displays the MSS-1 shelf as a card slot with Ethernet ports numbered from 1/1 to 1/6 and TDM ports from 1/7 to 1/22. Note 2 Radio LAG (L1 and L2) are not supported. MSS-4 and MSS-8 shelves Slots 1 and 2 are reserved for core-enhanced cards. Each shelf requires a core-enhanced card in slot 1 and can have an optional spare card installed in slot 2 to protect the main card. The MSS-4 shelf supports cards in slots 3 and 4. A card in slot 3 can be protected by an identical card in slot 4. The MSS-8 shelf supports cards in slots 3 to 8. Protected cards must be installed in slots 3, 5, or 7 and are protected by optional identical cards in slots 4, 6, and 8, respectively. IDUs and ODUs The ODU is a microprocessor-controlled transceiver that interfaces the MSS with the microwave antenna. Each radio modem card connects to one ODU. A 1+0 radio modem protection scheme requires one radio modem card and one ODU for each radio direction. Two radio modem cards and two associated ODUs must be provisioned in each radio direction for the 1+1 protection scheme. The can manage the following IDU and ODU variants: Alcatel-Lucent 5620 Service Aware Manager 2-3

18 MPR/9500 MPRe overview 12.0 R7 December HE AAAG TQZZA Edition 01 ODU300 The ODU300 transmitter consist of a cable interface, local oscillator, up converter/mixer, power amplifier, and a diplexer. The receiver consist of a diplexer, low-noise amplifier, local oscillator, down converter/mixer, automatic gain control, and cable interface. The ODU300 is frequency dependent. MPT-HCv2 The MPT-HCv2 ODU transports Ethernet traffic over an RF radio channel between the MSS and the antenna according to the configured QoS and to the scheduler algorithms. The input interface is a standard Giga Ethernet interface (electrical or optical). The MPT-HCv2 is XPIC-ready by the installation of a dedicated module.the MPT-HC V2 is frequency dependent. MPT-XP The MPT-XP is a very high power version of the MPT-HCv2 and provides +7-8 db of additional transmit power as compared to equivalent MPT-HCv2. The MPT-XP is frequency dependent. MPT-MC The MPT-MC is similar to MPT-HCv2 from an architecture standpoint. The differences are: MPT-MC is medium capacity MPT-MC is natively Ethernet powered through a proprietary PFoE MPT-MC has an optical cable length limit of 100 m MPT-HL The MPT-HL transceiver card is a microprocessor controlled RF transceiver that interfaces with the Core-E card or MSS-1 shelf MPT-HL port with an antenna. The MPT-HL transceiver microprocessor manages transmit and receive frequencies, transmit power, alarms, and performance monitoring. The MPT-HL transceiver resides in the MPT-HL shelf. The following configurations are supported: one or two Non-Standby (1+0) radios Hot Standby (1+1) and Hot Standby space frequency diversity MPT-HLC The MPT-HLC transceiver card is a microprocessor controlled RF transceiver that interfaces with the Core-E card, EASv2 card, or MSS-1 shelf MPT-HLC port with an antenna. The MPT-HLC transceiver microprocessor manages transmit and receive frequencies, transmit power, alarms, and performance monitoring. The MPT-HLC transceiver resides in the MPT-HL shelf. The following configurations are supported: one or two Non-Standby (1+0) radios Hot Standby (1+1) and Hot Standby space 2-4 Alcatel-Lucent 5620 Service Aware Manager

19 MPR/9500 MPRe overview frequency diversity single-shelf repeater MPT-HLS The MPT-HLS is a fully indoor radio system, for long haul and cabinet requirements, and transports Ethernet traffic over an RF radio channel. The MPT-HLS transceiver is connected to an MSS-1, MSS-4, or MSS-8. The MPT-HLS can be connected to the core-enhanced card or to an EASv2 card. The MPT-HLS is a four-rack (2200, 2000, 1700, 1300 mm) unit with two RT subracks. The subracks can be hosted with up to 10 transceivers. The TRU (always protected) is located on the top of the ETSI rack. A fan subrack is configured for each RT subrack. Two types of fan modules are available for configuration, Fan 4 and Fan 8. See Procedure 6-7 for more information about configuring the MPT-HLS radio. The supports viewing the adaptive modulation values for the usage time 512 QAM and 1024 QAM in MPT-HLS. MPT-HQAM The MPT-HQAM outdoor unit is a microprocessor controlled RF transceiver that interfaces with the MSS-1/4/8/1c shelf; MPTACC, Core-E, P8ETH, and EASv2 card, or MPR-e (stand-alone) with the antenna. Fixed and adaptive modulation schemes are supported. Channel frequency is software selectable within tuning range of the MPT-HQAM transceiver. The MPT-HQAM transceiver is frequency dependent. An MPT-HQAM connected to a Core-E, P8ETH, and EASv2 card requires a power source. The MPT-HQAM has integrated XPIC and RPS functions. The supports two operating modes in the MPT-HQAM: Standard mode The MPT-HQAM is used with its own capabilities and profiles. The air compatibility with another MPT-HQAM in Standard mode is supported. MPT-HC Compatibility mode MPT-HQAM is used with the MPT-HC capabilities and profiles. The air compatibility with another MPT-HQAM in MPT-HC Compatibility mode or with an MPT-HC is supported. The operating modes are configured on the NEtO and the supports viewing the MPTHC Compatibility parameter, with the values set to True or False, on the Radio General tab of the Physical Port (Edit) form. The supports 1+1 protection configuration for: two MPT-HQAMs, both configured in Standard mode two MPT-HQAMs, both configured in MPT-HC Compatibility mode two MPT-HQAMs, one configured in Standard mode and one in MPT-HCv2 Compatibility mode one MPT-HCv2 (with the main role as protection) and one MPT HQAM configured in Standard or MPT-HC Compatibility mode one MPT-HQAM configured in MPT-HC Compatibility mode (with the main role as protection) and one MPT-HCv2 Alcatel-Lucent 5620 Service Aware Manager 2-5

20 MPR/9500 MPRe overview 12.0 R7 December HE AAAG TQZZA Edition 01 The supports radio L1 LAG by adding: MPT-HQAM in MPT-HC Compatibility mode to an L1 LAG of MPT-HCv2 MPT-HQAM in Standard mode to an LAG L1 of MPT-HCv2 MPT-HQAM in Standard or MPT-HC Compatibility mode to an L1 LAG of MPT-MC MPT-HQAM in Standard/MPT-HC Compatibility mode or MPT-MC to an L1 LAG of MPT-HQAM in MPT-HC Compatibility or Standard mode The supports radio L2 LAG by adding: MPT-HQAM in MPT-HC Compatibility mode to an L2 LAG of MPT-HCv2 MPT-HQAM in Standard mode to an L2 LAG of MPT-HCv2 MPT-HQAM in Standard/MPT-HC Compatibility mode to an L2 LAG of MPT-HQAM in MPT-HC Compatibility/Standard mode An MPT type conversion procedure allows the you to update an MPT-HCv2 to an MPT-HQAM on the node. For the complete procedure see Alcatel-Lucent 9500 MPR-A Maintenance and Trouble Clearing Guide. The node restarts after the conversion and the displays the updated MPT-HQAM on the equipment tree and the Port Usage parameter value in the General tab of the Physical Port (Edit) form MPR/9500 MPRe card support See Working with card and card slot objects on 9500 MPR/9500 MPRe devices in chapter 6 for the supported cards and auxiliary equipment on 9500 MPR/9500 MPRe devices. Fan tray The 9500 MPR supports two fan tray types: basic and advanced. For the advanced fan tray, you can configure four ports for housekeeping alarms. See Procedure 6-3 for more information about configuring a 9500 MPR fan tray MPR LAG objects The supports the configuration and discovery of the L1 LAG associations from the or NEtO external element manager for equipment functions on the 9500 MPR (ANSI and ETSI), Release 3.4 or later. See chapter MPR services and service tunnel support The supports the configuration of VLANs, VLLs, and composite services on 9500 MPR devices. See chapter 9 for an overview of supported services. See chapter 10 for information about configuring VLAN services on the 9500 MPR. See chapter 11 for information about configuring VLL services on the 9500 MPR. See the Composite service management chapter in the User Guide about configuring composite services on 9500 MPR. 2-6 Alcatel-Lucent 5620 Service Aware Manager

21 MPR/9500 MPRe overview 9500 MPR/9500 MPRe NEtO support You can install and launch the 9500 MPR external element manager, the NEtO, from the GUI. See Procedure 4-4 for information about installing and launching the NEtO. Note 1 For the 9500 MPRe, the NEtO cross-launch only occurs if the 9500 MPRe registration table entry has not reached the limit of 15 entries. Note 2 A 9500 MPR SAM-E license restricts the functionality to basic node management in scenarios where NEtO is used for service management. For a comparison of management functionality with a -E license, compared to service management with the NEtO, see Appendix A. Note 3 The NEtO multi-version auto-downloads and cross-launch to IPv6 nodes to work, those nodes need to be reachable (IPv6 route must exist) from the Windows Client from which the auto-download or cross-launch is being attempted. NEtO distribution through the The manages the distribution of the NEtO application and all related profiles. Any discovered 9500 MPR has all cross-launch paths automatically configured in policies so that no user configuration is required to use the NEtO. The cross-launch function also supports the option to run TACACS+ in the network, in which case NEtO has a NULL authentication when cross-launched, and the user is prompted for a username and password. The first time a user cross-launches the NEtO, the Java Webstart installs the application on the client system. Any update to the NEtO installation files on the server results in an update to the NEtO installation on the client system. The supports the selection of user profiles to access the NEtO. The Admin NEtO launch, Viewer NEtO launch, and Default NEtO launch are listed in the scope of command roles that allows you to access the NEtO for a specific user profile. See the appendix to the System Administrator Guide for the list of scope of command roles. See Procedure 4-3 for information about configuring a scope of command role to access the NEtO for the required user profile. During an upgrade, the leaves property files in place for existing NEs, retaining any user edits made to support the NEs. An operator can change the property files to change the login behavior, as described in Procedure 3-3. The Install Directory property is a property required only by releases earlier than 10.0 R5; the current release manages the NEtO installation. See the applicable 9500 MPR Release Notice for the supported versions of NEtO. Alcatel-Lucent 5620 Service Aware Manager 2-7

22 MPR/9500 MPRe overview 12.0 R7 December HE AAAG TQZZA Edition 01 Service management with NEtO You can use the NEtO to manage services on the 9500 MPR. The use of an external element manager to change key network management information usually managed by the (such as service IDs, SAP or site information, or VLAN information) could result in data loss or corruption. To avoid this problem, site information is persisted so that management actions (such as moving service access from one DS1 port to another) do not result in data loss. The only takes the following additional actions to accommodate service changes made using the NEtO: A move between ports by the NEtO generates an alarm. The new port attachment is discovered and the deleted port is retained. The user can copy provisioning information to the new port in the or manually reverse the change, if required. A move between radio backhaul paths by the NEtO generates an alarm and is accepted. The alarm message retains the old and new path information, allowing the user to change the service back to its original form, if required. A move between radio and Ethernet backhaul paths by the NEtO generates an alarm and is accepted. The alarm message retains the old and new path information, allowing the user to change the service back to its original form, if required. When using the NEtO to change VLAN IDs for a service, the new service is discovered and alarms are generated for both services. An informational alarm is generated for the new service, and a major alarm is generated for the old service. A clean up on the service deletes all new discovery alarms and old SAPs, and accepts the new SAPs. Note The service changes from the NEtO in the preceding list are not supported for ERPS (radio or fiber). XPIC The XPIC function is required on the two radio interfaces in order to provide additional cross polarization discrimination, avoiding co-channel interference. Only the MPT-HCv2/MPT-XP supports the XPIC function. See Procedure 7-11 to configure power source type over Ethernet on a 2+2 Ethernet (EAS) card. See the 9500 MPR user documentation for more information about how to use the NEtO software to configure XPIC MPRe support The 9500 MPRe is the standalone, outdoor application of the MPT-MC and MPT-HCv2 ODU, without a shelf unit. The 9500 MPRe provides fixed or mobile Ethernet site backhauling and supports converged MPLS metro networks. 2-8 Alcatel-Lucent 5620 Service Aware Manager

23 MPR/9500 MPRe overview The supports native management of the 9500 MPRe, R3.3 or later. As a native NE, the 9500 MPRe appears on maps and equipment managers. All standard SNMP-based features, including discovery and alarms, are supported with the same naming as the rest of the 9500 MPR family. Some features require a cross-launch of the NEtO external element manager. See 9500 MPR/9500 MPRe NEtO support. See Procedure 7-7 for information about configuring ports on the 9500 MPRe. 2.2 Workflow to manage 9500 MPR/9500 MPRe devices The following workflow describes the high-level tasks required to commission and discover 9500 MPR and 9500 MPRe devices, configure and manage the device objects, and configure and manage the policies and services associated with the devices. 1 Review the workflow to prepare the to perform network management described in the supported devices chapter in User Guide before starting this workflow. The steps in this workflow are common to all -managed devices. 2 Commission 9500 MPR/9500 MPRe devices for management; see chapter 3. 3 Use the to discover 9500 MPR/9500 MPRe devices; see the Device discovery chapter in the User Guide. 4 View, manage, and configure 9500 MPR/9500 MPRe device network objects as required; see the Working with network objects chapter in the User Guide. 5 View, manage, and configure 9500 MPR/9500 MPRe device objects; see chapter 4. 6 View, manage, and configure 9500 MPR device LAG objects; see chapter 5. 7 View, manage, and configure 9500 MPR/9500 MPRe device shelf objects; see chapter 6. 8 Configure ports on 9500 MPR/9500 MPRe devices; see chapter 7. 9 Create policies that define the conditions for management functions on 9500 MPR devices. a b Before creating policies for 9500 MPR devices, review the Policies overview chapter in the User Guide for information about policy management and the workflow on how to create and distribute policies. Create QoS device-specific policies as required for 9500 MPR devices; see chapter 8. Alcatel-Lucent 5620 Service Aware Manager 2-9

24 MPR/9500 MPRe overview 12.0 R7 December HE AAAG TQZZA Edition Before configuring VLAN, VLL, or composite services and related functions on 9500 MPR devices; perform the following as required: a b c d Review the Service management and QoS chapter in the User Guide for information about configuring services on 9500 MPR devices using the. Review the Customer configuration and service management chapter in the User Guide for information about, and workflow on, how to create and manage customers and the services they subscribe to. As required, create customer profiles. Review the 9500 MPR service management and service tunnels chapter for specific information on supported service types; see chapter 9. Configure service tunnels to carry service traffic on 9500 MPR devices; see chapter Configure VLAN groups, paths, and services for subscribers connected to 9500 MPR devices; see chapter Configure VLL Apipe, Cpipe, and Epipe services for subscribers connected to 9500 MPR/9500 MPRe devices; see chapter Configure composite services to connect the types of services for subscribers connected to 9500 MPR devices; see the Composite service management chapter in the User Guide. 14 Perform specific 9500 MPR device maintenance functions, as required, such as: on-demand or scheduled NE configuration backup and restore device configurations perform a 9500 MPR/9500 MPRe device on-demand software upgrade monitor deployment of configuration changes to 9500 MPR devices configure the OLC state on a 9500 MPR device object to specify whether the object is in maintenance or in-service mode to filter alarms in the alarm window perform daily, weekly, monthly, and supplemental routine maintenance to maintain hardware and system integrity and efficiencies of 9500 MPR devices See the System Administrator Guide for more information. 15 Collect and NE statistics to monitor the and 9500 MPR/9500 MPRe devices, network and service performance, compile equipment usage and billing data, and ensure SLA compliance; see the Statistics Management Guide Alcatel-Lucent 5620 Service Aware Manager

25 9500 MPR/9500 MPRe management MPR/9500 MPRe device commissioning and management MPR/9500 MPRe object configuration MPR LAG object configuration MPR/9500 MPRe shelf object configuration MPR/9500 MPRe port object configuration Alcatel-Lucent 5620 Service Aware Manager

26 Alcatel-Lucent 5620 Service Aware Manager

27 MPR/9500 MPRe device commissioning and management MPR/9500 MPRe device commissioning and management overview Workflow to commission 9500 MPR/9500 MPRe devices MPR/9500 MPRe device commissioning and management procedures 3-7 Alcatel-Lucent 5620 Service Aware Manager 3-1

28 MPR/9500 MPRe device commissioning and management MPR/9500 MPRe device commissioning and management overview The 9500 MPR requires commissioning and device-specific preconfiguration before the can manage it. When this preconfiguration is complete, the can discover the device. See section 3.2 for the workflow that describes the sequence of high-level tasks required to commission a 9500 MPR before discovery by the. The 9500 MPR and 9500 MPRe network elements require that two mediation policies - one for read/write and one for traps to be created manually. While creating the read/write mediation policy, you must select FTP for the File Transfer Type, and specify FTP User Name 'ftp' and FTP User Password 'ftp'. While creating the trap mediation policy, you must specify 'SNMP-trap' as the SNMP v1/v2c Community String. When a node type is natively managed in the, it cannot be managed as a GNE. The Release 10.0 R3 and later supports the 9500 MPRe Release 3.3 and the 9500 MPRe Release 3.4. You cannot manage the 9500 MPRe Releases 2.x, 3.1, or 3.2 as GNEs in the Release 10.0 R3 and later. To upgrade to the Release 10.0 R3 and later from a release that has an 9500 MPRe managed as a GNE, you must unmanage the 9500 MPRe GNEs in the before the upgrade and you must upgrade the NE to the 9500 MPRe Release 3.3 or compatible 9500 MPRe version. You must re-manage the 9500 MPRe in Release 10.0 R3 and later. See the Network Element Compatibility Guide for more information about release specific information MPR/9500 MPRe management The supports in-band and out-of-band management of devices. When you configure in-band management only, management traffic between the and a 9500 MPR/9500 MPRe is transmitted through any port that is configured for network access, but not the management port. Using in-band management, the sends management traffic to the system IP address of the device, or to an optional L3 management interface. When you configure out-of-band management only, management traffic between the and a 9500 MPR/9500 MPRe is transmitted through the management port of the device. Using out-of-band management, the sends management traffic to the management IP address of the device. See the User Guide for more information about device bandwidth management. Note A 9500 MPR/9500 MPRe device can only be managed by up to five instances of the. 3-2 Alcatel-Lucent 5620 Service Aware Manager

29 MPR/9500 MPRe device commissioning and management 9500 MPR/9500 MPRe in-band management To enable 9500 MPR in-band management, the requires connectivity to the 9500 MPR NE, as shown in Figure 3-1 and described in the associated example configuration steps. Ensure that the trap receiving interface on the server is configured with the IP address of the in-band NIC that connects to the 9500 MPR network. Figure 3-1 Example of 9500 MPR/9500 MPRe In-band management 9500 MPR network server Switch or Router 9500 MPR A Management (TMN) port: Local IP: MPR B Local IP: Perform the following initial configuration on the 9500 MPR: 1 Connect the first 9500 MPR Node 1 to the switch using the TMN port or port 4 of the 9500 MPR A. When the is connected to the 9500 MPR network via non-9500 MPR devices like the 7705 SAR or 7750 SR, expect that the TMN in-band feature is enabled on Node 1 of the 9500 MPR that is connected to non-9500 MPR devices. For example, SAM SAR_1/1/1-----port1/4_MPR (radio)------mpr2... In the preceding example, the 9500 MPR Node 1 and port 1/4 are enabled with VLAN ID and IP addresses and the 7705 SAR is configured with the same VLAN and IP address from the same subnet. 2 Ensure that the radio links between the 9500 MPRs are working by pinging the local IP addresses. A connection between two 9500 MPR NEs could be over an Ethernet or optical link. If the core Ethernet or core optical port is used between two 9500 MPRs, the ports should be enabled with TMN in-band on the 9500 MPR. Note The management port IP, TMN in-band IP, and local IP can be in different subnets. Perform the following network configuration: 1 Verify that you can ping the local IP address of all the NEs from the server. Alcatel-Lucent 5620 Service Aware Manager 3-3

30 MPR/9500 MPRe device commissioning and management 2 Verify that you can ping the server IP address from each of the 9500 MPR NEs. Note You can manage the 9500 MPR through the local IP address even though the management interface via the server is not reachable. 3 The should be able to discover and manage the local IP addresses of the 9500 MPRs after connectivity is established between the and the 9500 MPR NEs MPR radio link discovery and management Radio links between 9500 MPR devices are automatically discovered by the. The auto-discovery is supported for the following radio links: L2 LAG L1 LAG After the auto-discovery, the displays the following parameters on the Radio tab of the Physical Port (Edit) form: Remote IPv6/IPv4 Address Remote Interface Remote Port The radio interface can be: ODU300 MPT-xC MPT-HLv1 MPT-HLv2 Radio links between 9500 MPR devices are shown as physical links by the, with ports as the endpoint type. To enable 9500 MPR radio link discovery and management, the requires connectivity between the 9500 MPR NE radio ports, as shown in Figure 3-2 and described in Table Alcatel-Lucent 5620 Service Aware Manager

31 MPR/9500 MPRe device commissioning and management Figure 3-2 Connectivity example for 9500 MPR/9500 MPRe radio link discovery and management Switch 9500 MPR 1-MSS MPR 3-MSS MPR 4-MSS-4 2x(1+0) RADIO CONFIGURATION with: LINKGRP=2 LINKMEMBER=3, MPR 2-MSS-4 3x(1+0) RADIO CONFIGURATION with: LINKGRP=1 LINKMEMBER=1, 3, Table 3-1 Connectivity parameter details 1-MSS-4 2-MSS-4 3-MSS-8 4-MSS-4 2-MSS-4 PPPRF Enabled LinkID (as assigned) PPPRF Enabled LinkID (as assigned) 3-MSS-8 PPPRF Enabled LinkID (23, 23) PPPRF Disabled LinkID (26, 26) PPPRF Enabled LinkID (as assigned) PPPRF Enabled LinkID (11, 11) PPPRF Disabled LinkID (13, 13) PPPRF Disabled LinkID (15, 15) To discover multiple radio links, you must provision the radio ports on the 9500 MPR based on the following criteria. 1 Only one radio port can have PPPRF enabled. The far endpoint on the same link must have the same configuration as the first endpoint. PPPRF should be disabled on both endpoints for the second and any subsequent radio links. 2 LinkID requirements include: The LinkID must be enabled for all of the port members of the configuration that have the same LINKGRP, and a different LINKMEMBER that matches the far endpoint. Expected and Sent values must be equal (for example, 11, 11 or 13, 13). For a multiple N (1+x) radio configurations on the same NE, the LINKGRP must be unique without overlapping (for example, 1 and 2). LinkID should be formatted as LINKGRP:LINKMEMBER in a hexadecimal format where LINKGRP is the first character and LINKMEMBER are the members. Any mismatch between the LinkID at the link level (for example, Send is not equal to Expected) mutes the radio connection (MPT case). Alcatel-Lucent 5620 Service Aware Manager 3-5

32 MPR/9500 MPRe device commissioning and management 3 As a requirement for the first radio link to be discovered, the remote address must be present at both endpoints. For subsequent links, alarms cannot be present on the radio port. 4 When radio link aggregation is enabled for any of the radio links between two 9500 MPRs, all radio links must belong to the same LAG. 5 When 1+1 configuration is deleted resulting in two 1+0 radio links, the can display incorrect information for the remote interfaces. The Remote interface for previously Spare port can be set to Main port or 0. The incorrect information occurs because the 9500 MPR node sends incorrect values in the transient phase. 6 When the LAG member links are deleted, the does not update the display of the link. For example, the LAG configuration with links to two members can display as one link or no link even after the two links are deleted. The incorrect information occurs because the 9500 MPR node sets the remote interface to 0 momentarily. Note The PPPRF configuration and LinkID configuration are not applicable for the 9500 MPR, Release 5.2 and later. If the PPPRF and LinkID parameters are disabled on all the radio ports. Radio links are still discovered successfully. Criteria 1 and 2 are not applicable for the 9500 MPR, Release 5.2 and later MPR radio link protection schemes You can apply 9500 MPR radio link protection by configuring the Protection Type parameter on the protection tab on supported card slot objects or port objects. See Procedure 6-4 and 7-13 for more information. Additionally, you can switch between an in-service protected radio link and a standby protected link to perform routine maintenance tasks. See Procedure 6-6 for more information. In-service protected radio links are represented as green links on the Physical topology map; standby links are shown as blue links; out-of-service radio links, main or spare, are represented as red links. If a mismatch of active and standby states should occur, main links are represented as green links on the Physical topology map; spare links are shown as blue links. Note The status of a protected link does not have a direct impact on the status of a service. See Table 9-1 for more information about the service status. 3-6 Alcatel-Lucent 5620 Service Aware Manager

33 MPR/9500 MPRe device commissioning and management 3.2 Workflow to commission 9500 MPR/9500 MPRe devices Prepare the 9500 MPR for management by commissioning the device before discovery by the ; see the Device commissioning and management chapter in the User Guide for the generic procedures that apply to this device type. In addition, perform the following device-specific procedures as required: 1 Enable and configure SNMP on a 9500 MPR device and configure a mediation policy and discovery rule; see Procedure Configure how and when the polls the device for MIB changes; see Procedure If required, modify the properties files of 9500 MPR NEs originally discovered using the, Release 10.0 R4 or earlier, to enable the opening of NEtO sessions using the GUI. See Procedure MPR/9500 MPRe device commissioning and management procedures The following procedures describe how to commission 9500 MPR/9500 MPRe devices for commissioning and management by the. Procedure 3-1 To commission a 9500 MPR/9500 MPRe for management Perform this procedure to configure a mediation policy and discovery rule for a 9500 MPR. Note Ensure that you create the mediation policy based on whether the 9500 MPR device supports SNMPv2 or SNMPv3, along with the appropriate Trap mediation policy with community string. 1 To configure SNMPv2 management of the device, perform the following steps. Note The uses the default SNMPv2 mediation security policy to discover the 9500 MPR. i ii iii iv Choose Administration Discovery Manager from the main menu. The Discovery Manager (Edit) form opens with the Discovery Rules tab displayed. Click on the Create button. The Create Discovery Rule step form opens. Enter a description in the Description field for the discovery rule. Click on the Next button. In step 2 of the step form (Add Rule Elements), click on the Create button. The Topology Discovery Rule Element (Create) form opens. Alcatel-Lucent 5620 Service Aware Manager 3-7

34 MPR/9500 MPRe device commissioning and management v vi vii viii ix x xi xii xiii xiv Enter the 9500 MPR management IP address as the rule element for the discovery rule and click on the OK button. A warning message appears. Click on the OK button to acknowledge and dismiss the warning message. Go to step 4 in the step form by clicking on the Next button. Click on the Select button in the Read Access Mediation Policy panel. The Configure Mediation Security Topology Discovery Rule form appears. Select a mediation security policy and click on the OK button. The form closes and the selected policy displays in the Read Policy Name parameter field. Repeat steps 1 viii and 1 ix to select a Write Access Mediation Policy and Trap Access Mediation Policy. Click on the Finish button to save and close the Create Discovery Rule step form. A warning message appears. Click on the OK button to acknowledge and dismiss the warning message. Click on the OK button. The Discovery Manager (Edit) form opens with the new discovery rule displayed. Click on the OK button. The Discovery Manager (Edit) form closes. xv Go to step 7. 2 To configure SNMPv3 management of the device, see the Device discovery chapter in the User Guide. 3 Create an SNMPv3 user on the. i ii iii Choose Administration Security NE User Configuration from the main menu. The NE User Configuration form opens. Click on the Create button. The NE User, Global Policy (Create) form opens with the General tab displayed. Configure the parameters: User Name Enter the username created in step 2 (snmpv3_username). Description Access Choose the snmp option. The SNMPv3 tab appears in the NE User, Global Policy (Create) form. iv v Click on the SNMPv3 tab. When a user has SNMPv3 permissions, you can configure the authentication parameters. Verify that the SNMPv3 user and user group have been created on the managed NE. Configure the parameters: Authentication Protocol Choose MD5 as the authentication protocol. Privacy Protocol Choose No Privacy as the privacy protocol. New Authentication Password Confirm New Auth Password 3-8 Alcatel-Lucent 5620 Service Aware Manager

35 MPR/9500 MPRe device commissioning and management vi vii Click on the OK button. The NE User, Global Policy (Create) form closes. Click on the Search button on the NE User Configuration form to confirm the creation of the SNMPv3 user. 4 Configure an SNMPv3 mediation security policy for the SNMPv3 user created in step 3. i ii iii iv v Choose Administration Mediation from the main menu. The Mediation (Edit) form opens with the General tab displayed. Click on the Mediation Security tab. Click on the Create button to create a mediation security policy. The Mediation Policy (Create) form opens. Configure the Displayed Name parameter to identify the policy. Set the Security Model parameter to SNMP v3 (USM). vi In the SNMP panel, set the Port parameter to 161. vii viii ix x xi In the SNMPv3 panel, click on the Select button. The Select User Mediation Policy form opens. Choose the SNMPv3 user created in step 3 and click on the OK button. The user is added to the SNMPv3 panel on the Mediation Policy (Create) form. Click on the OK button to save the changes. A dialog box appears. Click on the OK button. Click on the OK button. The Mediation (Edit) form closes. 5 Create a discovery rule for the 9500 MPR on the. i ii iii Perform steps 1 i to 1 x in this procedure to initiate the creation of the discovery rule. In step 4 of the step form (the Configure Mediation Security step), click on the Select button and choose the mediation security policy that you created in step 4 in this procedure for the Read Policy ID, Write Policy ID, and Trap Policy ID parameters. Perform steps 1 xi to 1 xv in this procedure to complete the creation of the discovery rule. 6 If you plan to use a auxiliary server to collect 9500 MPR statistics using IPv4 or IPv6, perform the following steps. i ii iii iv Choose Administration System Information from the main menu. The System Information form opens. Click on the Auxiliary Servers tab. Choose the auxiliary server from the list and click on the Properties button. The Auxiliary Server (View) form opens. Click on the Auxiliary Services tab. Alcatel-Lucent 5620 Service Aware Manager 3-9

36 MPR/9500 MPRe device commissioning and management v vi vii Select the STATS_SERVICE entry from the list and click on the Properties button. The Auxiliary Service - STATS_SERVICE (Edit) form opens. If you are using IPv6, configure the IPv6 Address parameter. Click on the OK button. The Auxiliary Service - STATS_SERVICE (Edit) form closes. During the subsequent device discovery, the registers the IPv6 address of the auxiliary server on each discovered 9500 MPR or 9500 MPRe. viii ix x Click on the OK button. The Auxiliary Server (View) form closes. To configure another auxiliary server, repeat steps 6 iii to viii. Close the System Information form. 7 Use the client to discover the NE and to verify that the NE configuration allows management of the 9500 MPR. See the Device discovery chapter in the User Guide. Procedure 3-2 To configure polling for 9500 MPR/9500 MPRe devices 1 Choose Equipment or Routing from the navigation tree view selector. The managed devices are displayed. 2 Right-click on an icon that represents a 9500 MPR and choose Properties. The Network Element (Edit) form opens with the General tab displayed. 3 Record the system IP address and the management IP address. Configure the Location and Current OLC State parameters, if required. 4 Click on the Polling tab. 5 Configure the Scheduled Polling parameter if you are configuring a 9500 MPR. Scheduled polling is configured using the Mediation configuration form. See the Device discovery chapter in the User Guide. 6 View the read-only parameters to determine the current polling status: Resync Status indicates whether the last poll successfully completed. Last Resync Start Time and Last Resync End Time indicate the start and finish of the last poll. Scheduled Resync Status indicates whether the last scheduled poll successfully completed. Last Scheduled Resync Start Time and Last Scheduled Resync End Time indicate the start and finish of the last scheduled poll Alcatel-Lucent 5620 Service Aware Manager

37 MPR/9500 MPRe device commissioning and management 7 Click on the OK button. A dialog box appears. 8 Click on the Yes button to confirm the action. The Network Element (Edit) form closes. Procedure 3-3 To enable management of 9500 MPR/9500 MPRe devices Perform this procedure to enable the to manage a 9500 MPR or 9500 MPRe, and to enable the opening of NEtO sessions using the GUI. Note The NEtO application is installed and configured to open automatically for newly discovered 9500 MPR NEs. Use this procedure only to modify properties files of 9500 MPR NE versions that are not supported in NEtO distribution in Release 10.0 R5. See Procedure 4-4 for information about how to install or launch the NEtO from the GUI. 1 Log in to a client station. 2 Discover a 9500 MPR or 9500 MPRe NE and verify that the can manage the device. Note If this is the first time you are enabling management of a 9500 MPR or 9500 MPRe in your network, you must manually create a Read-Write mediation policy and a Trap mediation policy as part of the discovery rule creation process. Special parameter settings apply if you are enabling FTP access. See the Device discovery chapter in the User Guide. 3 On a Windows client, navigate to the following directory: path\nms\thirdparty\config where path is the client installation location, typically C:\5620sam\client 4 Find the required 9500 MPR properties file, which is named Alcatel-MPR-9500_Release.properties. where Release is the appropriate 9500 MPR release identifier, for example, Open the file using a plain-text editor. 6 Replace ${path} in the following line with the NEtO directory path; for example, D:\\NEtO install_dir =${path} 7 For the 9500 MPR only: change the profile name, as required. The format is, profile_name = <role> <community string> <user id> <password>. For example: Alcatel-Lucent 5620 Service Aware Manager 3-11

38 MPR/9500 MPRe device commissioning and management profile_name = admin private initial adminadmin Note If you do not edit the profile name, the community string is derived from the mediation policy of the discovery rule. 8 Save and close the file. 9 Select the equipment view of the navigation tree on the GUI. Right-click on a 9500 MPR or 9500 MPRe NE, and select External Element Manager from the menu. 10 Verify that the NEtO software launches Alcatel-Lucent 5620 Service Aware Manager

39 MPR/9500 MPRe object configuration MPR/9500 MPRe object configuration overview Workflow to configure and manage 9500 MPR/9500 MPRe device objects MPR/9500 MPRe device object configuration procedures 4-2 Alcatel-Lucent 5620 Service Aware Manager 4-1

40 MPR/9500 MPRe object configuration 12.0 R7 December HE AAAG TQZZA Edition MPR/9500 MPRe object configuration overview The device object is the discovered device at the top of the hierarchy in the navigation tree, directly below the network icon. This chapter contains the procedures to configure 9500 MPR/9500 MPRe device objects using the navigation tree. Device object properties forms, which are used to configure specific parameters for discovered devices, are accessed using objects on the navigation tree. See the Navigation tree overview chapter in the User Guide. 4.2 Workflow to configure and manage 9500 MPR/9500 MPRe device objects The following workflow describes the sequence of high-level tasks required to configure and manage 9500 MPR/9500 MPRe device objects; see the Device object configuration chapter in the User Guide for the generic procedures that apply to this device type. Also, configure the following device-specific tasks and functions. 1 Configure the system settings for a 9500 MPR/9500 MPRe device; see Procedure Remove any inconsistencies created due to MIB population failures that can occur during service creation on a 9500 MPR NE; see Procedure Configure a scope of command role for NEtO access; see Procedure Start the 9500 MPR external element manager from the GUI; see Procedure As required, configure or modify the DSCP value for TMN in-band interfaces on the 9500 MPR. See Procedure As required, review the list of the specific functionality for a 9500 MPR SAM-E license compared to management functions available in the NEtO. See Appendix A MPR/9500 MPRe device object configuration procedures Use the following procedures to configure devices using the navigation tree. Procedure 4-1 To configure system settings on a 9500 MPR 1 Right-click on a 9500 MPR device in the navigation tree and choose Properties from the contextual menu. The Network Element (Edit) form for the device opens with the General tab displayed. 2 Click on the System Settings tab. 4-2 Alcatel-Lucent 5620 Service Aware Manager

41 MPR/9500 MPRe object configuration 3 Configure the parameters as required: DHCP Server Admission Control Bridge Type Event and Alarm Log Ethernet LOS Criteria Static Lag Criteria Physical Impedance System Priority Ais Insertion LOF Detection 4 Click on the OK button. A dialog box appears. 5 Click on the Yes button. The Network Element (Edit) form closes. Procedure 4-2 To resolve 9500 MPR MIB inconsistencies Perform this procedure to resolve inconsistencies created due to MIB population failures that can occur during service creation on a 9500 MPR NE. Alcatel-Lucent recommends that inconsistencies be resolved before any service creation. For failures during 9500 MPR service creation, perform a resynchronization of the NE in order to restore existing NE entries. Inconsistencies are detected during NE synchronization or when opening the NE properties form. If there are inconsistencies, an alarm with a Warning severity level on the NE appears. 1 Right-click on a 9500 MPR NE device in the navigation tree, and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 2 If there are NE inconsistencies, a Cleanup Inconsistencies button appears on the form, or the Cleanup Inconsistencies option appears under the More Actions button. 3 Click on the Cleanup Inconsistencies button. If the Cleanup Inconsistencies button is not visible, click on the More Actions button and choose Cleanup Inconsistencies. 4 Click on the Faults tab of the Network Element (Edit) form to check for any remaining NE inconsistency alarms. Procedure 4-3 To configure a scope of command role for NEtO access 1 Using an account with an assigned security scope of command role, choose Administration Security User Security from the main menu. The User Security - Security Management (Edit) form opens with the General tab displayed. 2 Click on the Scope of Command tab. 3 Click on the Create button and choose Profile. The Scope of Command Profile (Create) form opens with the General tab displayed. Alcatel-Lucent 5620 Service Aware Manager 4-3

42 MPR/9500 MPRe object configuration 12.0 R7 December HE AAAG TQZZA Edition 01 4 Configure the parameters: Auto-Assign ID Profile ID Profile Name Description 5 Click on the Roles tab and click on the Add button. The Select Role - Role form opens. 6 Perform one of the following: a b c Choose Admin NEtO launch to open the NEtO with the administration profile. Choose Viewer NEtO launch to open the NEtO with the viewer profile. Choose Default NEtO launch to open the NEtO with the null profile. Note If the option to run TACACS+ in the network is enabled, choose the Default NEtO launch. 7 Click on the OK button. The Select Role - Role form closes and a dialog box appears. 8 Click on the OK button. 9 Click on the OK button. The Scope of Command Profile (Create) form closes. 10 Close the User Security - Security Management (Edit) form. Procedure 4-4 To start the 9500 MPR/9500 MPRe external element manager from the GUI To cross-launch the NEtO, you must belong to a user group that includes a scope of command profile that is configured with the Administrator role, or another role that has the following permissions set to Update/Execute: netw.networkelement.method_guicrosslaunch mediation security.mediationpolicy Note For the 9500 MPRe, the NEtO cross-launch only occurs if the 9500 MPRe registration table entry has not reached the limit of 15 entries. 4-4 Alcatel-Lucent 5620 Service Aware Manager

43 MPR/9500 MPRe object configuration For general information about user security, creating a scope of command role, and creating a scope of command profile, see the System Administrator Guide. For specific information about creating a scope of command role for NEtO access, see Procedure Choose Equipment from the view selector in the navigation tree. The navigation tree displays the Equipment view. 2 Right-click on a discovered 9500 MPR or 9500 MPRe and choose External Element Manager. 3 Type your login credentials. The NEtO main view screen appears. Note If the NEtO is not installed on your client system, the NEtO installer window opens. After the NEtO installation completes, the NEtO main view screen appears for all subsequent launches, with the NEtO version adjusted to the NE version from which the NEtO launched. See the appropriate 9500 for information about configuring and using the NEtO external element manager. Procedure 4-5 To configure a DSCP value for in-band TMN interfaces on the 9500 MPR You can configure or modify the DSCP value for TMN in-band interfaces following this procedure or specified as part of a global 9500 MPR NE QoS policy. See Procedure 8-3 for the 9500 MPR NE QoS policy method. Note You cannot change the DSCP value if the in-band TMN interface is set to enabled. 1 Right-click on a 9500 MPR device on the navigation tree and choose Properties from the pull-down menu. The Network Element [Edit] form opens with the General tab displayed. 2 Click on the Polling tab. 3 Click on the TMN Details tab. The current setting of TMN interface on the selected device are displayed in the TMN Working Mode column (either Enabled or Disabled). 4 Select one of the following for an TMN in-band interface: a b To configure a new DSCP value, double-click on an appropriate Disabled TMN interface. Go to step 5. To modify an existing new DSCP value, double-click on appropriate Enabled TMN interface. Go to Step 7. The MPR TMN - TMN In-band (Edit) form opens. Alcatel-Lucent 5620 Service Aware Manager 4-5

44 MPR/9500 MPRe object configuration 12.0 R7 December HE AAAG TQZZA Edition 01 5 Set the DSCP parameter to the appropriate level. 6 As required, configure the VLAN ID parameter within a range of 2 to 4080 to prevent a server validation error. 7 Configure the TMN Working Mode parameter to one of the following options: a Enabled to configure a new DSCP value. Go to step 8. b Disabled to modify a new DSCP value. Go back to step 5. Note To modify an existing DSCP values for an in-band TMN interface, the TMN Working Mode parameter must be set to Disabled before you re-configure the DSCP parameter to the appropriate level. 8 Click on the OK button. The MPR TMN - TMN In-band [Edit] form closes. 9 Click on the Apply button on the devices properties form. A confirmation box appears. 10 Click on the Yes button to proceed with the configuration change. 11 As required, repeat steps 4 to 10 to configure the DSCP value for the second in-band TMN interface. 4-6 Alcatel-Lucent 5620 Service Aware Manager

45 MPR LAG object configuration 5.1 Working with 9500 MPR LAG objects Workflow to configure and manage 9500 MPR LAG objects MPR LAG configuration procedures 5-4 Alcatel-Lucent 5620 Service Aware Manager 5-1

46 MPR LAG object configuration 12.0 R7 December HE AAAG TQZZA Edition Working with 9500 MPR LAG objects Link Aggregation groups (LAGs) are a set of ports used to interconnect network nodes using multiple links to increase link capacity and availability between them. LAGs also provides redundancy between the aggregated links. If a link fails, traffic is redirected onto the remaining link, or links. LAGs on the GUI are represented as part of the navigation tree objects and are located below a device icon. You can configure LAGs using the configuration forms available when you choose Create LAG from the LAG object navigation tree contextual menu. See the Logical group object configuration chapter in the User Guide for more information MPR LAG objects The supports the configuration and discovery of the LAG associations from the or NEtO external element manager for equipment functions on the 9500 MPR, Release 3.4 or later. You can configure the following LAG types for the 9500 MPR: L1 radio LAG (both static and adaptive modulation are supported) L2 radio LAG (only static modulation is supported) L2 Ethernet LAG (supported modulation type does not apply to this LAG type) Service configuration is supported across L1 and L2 radio LAGs using the suite of current service functionality. For example, support is provided for detection of end-to-end bandwidth on the VLAN path or correlation of link level alarms up to paths that include L1 radio LAGs. The 9500 MPR LAG support includes: up to four L1 radio LAGs on an 9500 MPR device up to four L2 radio LAGs on an 9500 MPR device up to two L1 radio LAGs, L2 radio LAGs, or both) on an 9500 MPR MSS-4 shelf up to five radio LAGs (L1 radio LAG, L2 radio LAG or both, but excludes L2 Ethernet LAGs) on an 9500 MPR device up to eight LAGs (L1 radio LAG, L2 radio LAG or both, and includes L2 Ethernet LAGs) on a 9500 MPR device L1 LAGs can be created in the following configurations: Intra plug-in LAG Cross plug-in LAG An intra plug-in LAG is a LAG with MPT-HLS configured on the same card. A cross plug-in LAG is a LAG with MPT-HLS configured on two EASv2 cards on the same MSS row. 5-2 Alcatel-Lucent 5620 Service Aware Manager

47 MPR LAG object configuration L1 radio port deployment guidelines A L1 radio LAG follows a similar deployment model as an L2 radio LAG except that the L1 radio LAG functions are deployed at the radio layer. As a result, the L1 radio LAG has different port associations, cross-connections, and validations from the L2 radio LAG. The advantage of a L1 radio LAG is that highly correlated upper-layer traffic can be hashed. For example, an LSP hashes to the same port in an L2 radio LAG. L1 radio LAG port modulation configuration guidelines The supports the configuration of both static and adaptive modulation when deploying L1 radio LAGs on the 9500 MPR. See Procedure 5-1 for information about how to configure L1 radio LAGs. Adaptive modulation techniques ensure that high-priority services are prioritized before other traffic types, simplify network planning, and improve spectral efficiency. Members of a L1 radio LAG configured with static or adaptive modulation: must all terminate on the same radio interface type (MPT-HCv2, MPT-XP, MPT-HL, or MPT-HLC ODUs and IDUs are supported). all radio links in the LAG must have same modem profile, either static (preset) modulation or adaptive modulation, set on all radio links in the LAG. must all have same channel spacing, option, and modulation scheme (the modulation scheme requirement only applies to radio links in a static (preset) modulation mode). The recommended settings for the aggregation of radio links configured in adaptive modulation mode are: Minimal channel spacing for: ETSI = 14 MHz ANSI = 10 MHz Minimal modulation scheme = 16 QAM Note You must use the 4+4 Ethernet (EAS) card for L1 radio LAG endpoints configured with adaptive modulation. 5.2 Workflow to configure and manage 9500 MPR LAG objects The following workflow describes the sequence of high-level tasks required to configure and manage 9500 MPR LAG objects; see the Logical group object configuration chapter in the User Guide for the generic procedures that apply to this device type. Also, configure the following device-specific tasks and functions. 1 Configure a L1 radio LAG or L2 radio LAG or Ethernet LAG on the 9500 MPR; see Procedure Delete a 9500 MPR LAG; see Procedure 5-2. Alcatel-Lucent 5620 Service Aware Manager 5-3

48 MPR LAG object configuration 12.0 R7 December HE AAAG TQZZA Edition MPR LAG configuration procedures Use the following procedures to manage LAGs using the navigation tree. Procedure 5-1 To create an L1 radio LAG, L2 radio LAG, or Ethernet LAG on a 9500 MPR You can create a L1 radio LAG, L2 radio LAG or Ethernet LAG on the 9500 MPR, Release 3.4 or later. Note 1 Mixed ports cannot be associated with a LAG; for example, MPT-HCv2, MPT-MC, MPT-XP, MPT-HL, or ODU. You can only associate a L1 radio or L2 radio LAG with an MPT-HL port, and a L1 radio LAG with an MPT-HLC port. Note 2 Before you associate a L1 radio or L2 radio port with a LAG, PPP-RF must be disabled using the NEtO element manager. Note 3 The radio LAG is always in network mode. By default, Ethernet LAG is in access mode and can be used as a SAP. If a physical link is created using Ethernet LAGs as the endpoints, the mode automatically changes from access to network mode. If a physical link is created between MPR and non-mpr LAG ports, and the MPR LAG port must be used as a SAP, the user must change the mode to access. See step 19 for more information about how to change the mode. Note 4 An Ethernet member port with a physical link or radio port with protection cannot be added to a LAG. To add the port, you must delete the physical link and then add the port to the LAG. See the Topology map management chapter in the User Guide for more information about how to delete a physical link. Note 5 For Fast Ethernet LAGs, electrical ports cannot be grouped with the optical ports. 1 Choose Equipment from the navigation tree view selector. The navigation tree is displayed in the Equipment view. 2 Expand the device where you need to create the LAG. 3 Right-click on the LAGs icon and choose Create LAG from the contextual menu. The Create LAG - Define General Properties form opens. 4 Configure the parameters: LAG ID Auto-Assign ID 5 Click on the Next button. The Create LAG - Configure LAG Parameters form opens. 5-4 Alcatel-Lucent 5620 Service Aware Manager

49 MPR LAG object configuration 6 Configure the parameters: Name Note The Name parameter configuration must be limited to a maximum of 15 characters. Lag Aggregation Type Size 7 Click on the Next button. The Create LAG - Configure LACP form opens. 8 Configure the parameters: Actor Administration Key LACP Timeout Note The LACP and Timeout parameters are only applicable to Ethernet LAGs. 9 Click on the Next button. The Create LAG - Configure LAG Members form opens. 10 Click on the Create button to add ports to the LAG. The Create LAG Member - Only show compatible ports form opens. Note The Show Only Compatible Ports parameter on this form does not apply to the 9500 MPR. The Class parameter depends on the Lag Aggregation Type specified in step Click on the Next button. The Create LAG Member - Select Ports form opens. 12 Click on the Search button to display a list of compatible ports. Choose one or more ports from the list. Note For L1 radio LAG port members, see the L1 radio LAG port modulation configuration guidelines for the required configuration guidelines. 13 Click on the Finish button. A dialog box appears. 14 Click on the OK button. The Create LAG - Configure LAG Members form displays the LAG members. 15 Click on the Finish button. The Create LAG - Wizard Completed form opens. 16 If required, select the View the newly created Port Termination check box to view the LAG properties. 17 Click on the Close button to close the form. The LAG appears under the LAGs icon in the navigation tree. Alcatel-Lucent 5620 Service Aware Manager 5-5

50 MPR LAG object configuration 12.0 R7 December HE AAAG TQZZA Edition Turn up the LAG: i ii Right-click on the LAG and choose Turn Up from the contextual menu. A dialog box appears. Click on the Yes button. 19 As required, right-click on the LAG and choose Properties from the contextual menu to view information about the created LAG or to modify the LAG parameters. The LAG (Edit) form opens. The General tab displays the LAG ID and description. For a radio LAG and Ethernet LAG, choose one of the following Mode parameter values: Access (Ethernet LAG only) Network (radio LAG only) The Link Aggregation Group tab displays the Name of the LAG, the number of ports associated with the LAG member ports, and the Lag Aggregation Type. For Ethernet LAG, choose Hash and Size from the drop-down menu. For radio LAG, choose Size and Wait to Restore (ms) from the drop-down menu. LACP parameters can be modified from the LACP tab. See step 8. LAG member ports can be added from the LAG Members tab. See steps 9 to 15. The Administrative State parameter can be configured to Up in the States tab, only if at least one port is associated with a LAG. The LAG state cannot be set to Down if a service is associated with the LAG. Procedure 5-2 To delete a 9500 MPR LAG 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Select the device where you need to delete the LAG. 3 On the Network Element (Edit) form navigation tree, expand the Logical Groups icon. 4 Expand the LAGs icon, right-click on a LAG object, and choose Delete from the contextual menu. A dialog box appears. 5 Click on the Yes button to complete the deletion. Note A LAG can be deleted only if a member is not associated with the LAG. To delete the last member from a LAG, the Administrative State of the LAG must be set to Down. A LAG can be shut down only when the LAG is not a part of any service or physical link. 5-6 Alcatel-Lucent 5620 Service Aware Manager

51 MPR/9500 MPRe shelf object configuration MPR/9500 MPRe shelf object configuration overview Working with shelf objects on 9500 MPR/9500 MPRe devices Working with card and card slot objects on 9500 MPR/9500 MPRe devices Workflow to manage shelf objects on 9500 MPR/9500 MPRe devices MPR/9500 MPRe shelf object configuration procedures 6-9 Alcatel-Lucent 5620 Service Aware Manager 6-1

52 MPR/9500 MPRe shelf object configuration MPR/9500 MPRe shelf object configuration overview In the equipment navigation tree, shelf objects are children of device objects. Shelf objects appear below logical group objects in the navigation tree. Card slot objects are children of shelf objects, and as such appear below the shelf object in the navigation tree. This chapter contains the procedures to configure shelf and card slots using the navigation tree on 9500 MPR/9500 MPRe devices. 6.2 Working with shelf objects on 9500 MPR/9500 MPRe devices Shelf objects represent the hardware that is configured on a shelf. When you choose the shelf object in the navigation tree and click on Properties in the contextual menu, you can view the states and conditions of the 9500 MPR shelf including: general information fan tray state and speed card slots timing faults port segregation software control module software bank information cross connects For 9500 MPRe devices, you can view the following states and conditions on the shelf: general information display card slots software control module software bank information faults The Display tab displays a graphical representation of the device shelf and its equipment components, such as the empty card slots and the cards that are installed on the device. You can double-click on an object in the tab to open its Properties configuration form. Right-click on the object and you have access to the contextual menus for the object and any child objects; for example the ports of a card (dynamic graphical representation only). 6.3 Working with card and card slot objects on 9500 MPR/9500 MPRe devices When you click on the plus sign beside a shelf object, the card slots in the shelf appear in the navigation tree. They can appear as empty card slots when a card is not provisioned for the slot. Card slot objects for 9500 MPR/9500 MPRe devices can be configured for plug-in cards; there are no daughter cards associated with these devices. 6-2 Alcatel-Lucent 5620 Service Aware Manager

53 MPR/9500 MPRe shelf object configuration 9500 MPR card support Tables 6-1 and 6-2 provide a summary of the supported cards and ancillary equipment on the 9500 MPR by releases. Specific information about the cards is provided after the tables. Table MPR supported cards Release 7.0 R3 to 9.0 R7 Card Shelf release Notes 7.0 R3 7.0 R5 8.0 R1 8.0 R3 8.0 R5 9.0 R1 9.0 R5 9.0 R7 Core-enhanced Core-B 1 radio modem 2+2 Ethernet (EAS) 4+4 Ethernet (EAS) MSS-8 MSS-4 MSS-8 MSS-4 MSS-8 MSS-4 MSS-8 MSS-4 MSS-8 MSS-4 For ETSI nodes, supported from 7.0 R3 (Node version 1.2.0) For ANSI nodes, supported from 7.0 R5 (Node version 2.0.0) Supported for pre-1.2 versions only For ETSI nodes, supported from 8.0 R5 (Node version 2.1 For ANSI nodes, supported from 9.0 R1 (Node version 3.0.0) 2 STM MSS-8 MSS-4 16 E1 (ASAP) MSS-8 MSS-4 32 E1 MSS-8 MSS-4 32 DS1 MSS-8 MSS-4 2 DS3 MSS-8 MSS-4 Available for ETSI nodes only Available for ETSI nodes only Available for ANSI nodes only Available for ANSI nodes only 1 STM (Channelized) MSS-8 MSS-4 Available for ETSI nodes only Table MPR supported cards Release 10. R3 to 12.0 Rx Card Shelf release Notes 10.0 R R R R R R R R1 Core-enhanced Core-B (1 of 2) MSS-8 MSS-4 MSS-8 MSS-4 Supported for pre-1.2 versions only Alcatel-Lucent 5620 Service Aware Manager 6-3

54 MPR/9500 MPRe shelf object configuration Card Shelf release Notes 10.0 R R R R R R R R1 1 radio modem 2+2 Ethernet (EAS) 4+4 Ethernet (EAS) EASv2 MSS-8 MSS-4 MSS-8 MSS-4 MSS-8 MSS-4 MSS-8 MSS-4 2 STM MSS-8 MSS-4 16 E1 (ASAP) MSS-8 MSS-4 32 E1 MSS-8 MSS-4 32 DS1 MSS-8 MSS-4 2 DS3 MSS-8 MSS-4 Available for ETSI nodes only Available for ETSI nodes only Available for ANSI nodes only Available for ANSI nodes only 1 STM (Channelized) AUX alarm MSS-8 MSS-4 MSS-8 MSS-4 Available for ETSI nodes only Ancillary equipment MSS-1 MSS-1 The MSS-1 has a fixed card; support is available from R4.1 onward. Fan (2 of 2) MSS-8 MSS-4 Advanced Fan MPR 4.2 onwards Core-enhanced card The core-enhanced card in slot 1 provides the following: device management and control functions DC power a plug-in flash memory card to store device configuration and license data an Ethernet switch that implements the cross-connections between the radio modem or 32 DS1 / 32 E1 cards, between the Ethernet user ports, and between the Ethernet ports and the radio modem or 32 DS1 / 32 E1 cards four electrical Ethernet ports; port 4 can be used as another management port, if required two SFP Ethernet ports; the ports are supported by the when an SFP MDA is installed up to six MPT radio ports; ports 1 to 4 support MPT-HCv2, and MPT-MC; ports 5 and 6 support MPT-HCv2, MPT-HL, MPT-HLC, MPT-HLS, and SFP 6-4 Alcatel-Lucent 5620 Service Aware Manager

55 MPR/9500 MPRe shelf object configuration An optional identical core-enhanced card can be installed in card slot 2. The card provides protection if the card in slot 1 fails. The MPT-HL does not support radio LAGs or 1+1 protection configurations. See the 9500 MPR user documentation for information about supported cross-connections for the MPT-HL and core-enhanced card. When an MPT pair (MPT-HCv2 with RPS module, or MPT-MC) is used for a protected configuration, both MPTs must use the same type of GigE port (optical or electrical) to use the same IDU-ODU synchronization method. A protected configuration is only allowed between ports 1-2, 3-4, and 5-6. The following protection types are supported when MPT-HCv2 or MPT-MC is used as an ODU in a split-mount configuration and directly connected to a core-enhanced card: radio protection switching (RPS) RPS is always supported in 1+1 radio configurations (FD and HSB). RPS is implemented directly on a pair of MPTs. transmission protection switching (TPS) TPS is always supported in 1+1 HSB radio configurations. equipment protection switching (EPS) EPS protects the MPT and cables connecting the MPT to the IDU. RPS protection always assumes the MPT EPS. When an MPT ODU protection group is configured on a core-enhanced card: the MPT ODU connected to port 1 (electrical), port 3 (electrical), or port 5 (optical) is defined as main the MPT ODU connected to port 2 (electrical), port 4 (electrical), and port 6 (optical) is defined as spare See Procedure 7-13 for information about adding 9500 MPR port protection. Core-B card The core-b card in slot 1 provides the following: device management and control functions DC power a plug-in flash memory card to store device configuration and license data an Ethernet switch that implements the cross-connections between the radio modem or 32 DS1 / 32 E1 cards, between the Ethernet user ports, and between the Ethernet ports and the radio modem or 32 DS1 / 32 E1 cards four GigE electrical interfaces and one GigE SFP optical interface Alcatel-Lucent 5620 Service Aware Manager 6-5

56 MPR/9500 MPRe shelf object configuration 1 radio modem card The 1 radio modem card contains EPS and RPS logic, and performs the following: sends and receives standard Ethernet packets to and from the core-enhanced cards manages the radio frame generation and termination, the interface to and from the alternate radio transport card, and the cable interface functions to the ODU generates internal DC power for the card Note Protected ports on the 1 radio modem card are displayed under the Odd/Main card slot and are labeled as main and spare on the equipment tree. For example, if slots 5 and 6 on the 1 radio modem card are protected, the corresponding protected entities on the NEtO (channels 0 and 1) display as 5/0 and 5/1 under card 5 on the GUI. See Procedure 7-8 for information about configuring analog radio statistics on 1 radio modem ports. See Procedure 7-9 for information about configuring power level performance management on 1 radio modem ports. 2+2 Ethernet (EAS) card The 2+2 EAS card can be configured with three types of MPT radio ports: MPT-HC, MPT-HCv2, and MPT-MC. MPT-MC can be configured only on ports 1 and 2, and does not support protection. MPT-HC and MPT-HCv2 can be configured on any of the four ports if the corresponding port on the consecutive slot has the same card with the same MPT type. MPT-ACC ports are supported for 9500 MPR devices. See Procedure 7-11 for information about configuring the for a 2+2 Ethernet (EAS) card. 4+4 Ethernet (EAS) card The 4+4 (EAS) card can be configured in any card slot on the 9500 MPR. The card supports 4 Ethernet 10/100/1000BaseT (traffic) and 4+4 Ethernet (Access/MPT) connection interfaces. Each chassis allows up to two EAS modules. Ports 5 to 8 of a 4+4 Ethernet (EAS) card support the following radio types: ANSI, Release 3.4 or later MPT-HL MPT-HC port protection not supported SFP ETSI, Release 3.4 or later MPT-HC port protection not supported SFP EASv2 card The EASv2 card is used as an interface card to interconnect up to eight MPTs. The card can be configured in card slots 3 to 8 on the 9500 MPR. The card provides eight ports used for the following traffic interfaces: 6-6 Alcatel-Lucent 5620 Service Aware Manager

57 MPR/9500 MPRe shelf object configuration Ports 1 to 4 Ethernet 10/100/1000 Base-T configuration of MPT-HC and MPT-MC Ports 5 to 8 Ethernet SFP 1000 Base-X optical; 1000BASE-LX, 1000BASE-SX, 1000BASE-CX configuration of MPT-HC and MPT-HLS in ETSI and configuration of MPT-HC, MPT-HL, and MPT-HLC in ANSI Protection is not supported for MPT-HLC in R12.0. However, 1+1 cross configuration is supported on an MPT-HCv2 and MPT-HQAM connected to one of ports 5 to 8. See Procedure 7-11 for more information about configuring the power source type of an EASv2 card. Table 6-3 lists the supported EASv2 features in the corresponding release. Table 6-3 EASv2 features in the releases release Supported features on EASv R MPR 5.1 version with EASv2 at the level of EASv R MPR 5.1 version with MPT-HLS and LAG support 12.0 R MPR 5.1 version with MPT-HLC support 9500 MPR 5.1 version with a support for configuring MPT-HC/MC on the first four electrical ports 9500 MPR 5.2 version with combiner configuration on MPT-HLC 9500 MPR 5.2 version with MPT-HQAM support 12.0 R MPR 5.1 version with combiner configuration on MPT-HLS 9500 MPR 5.1 version with combiner configuration on MPT-HLS associated with an N+0 intra or cross configuration LAG 9500 MPR 5.1 version with 1+1 cross configuration protection for MPT-HCv2 connected to optical ports 9500 MPR 5.2 version with the MPT-HCv2 L1 LAG cross configuration support on electrical ports 1 to MPR 5.2 version with the MPT-MC L1 LAG intra and cross configuration support on electrical ports 1 to 4 2 STM card The 2 STM card supports optical signaling on the 9500 MPR. The 2 STM card can be configured in all card slots on the 9500 MPR. Up to two ports can be configured. A card in a 9500 MPR ETSI or a 9500 MPR ANSI, Release 4.0 or later, supports the SFP-O and the SFP-E port usage types. See Procedure 7-2 for information about configuring ports on a 2 STM card. Alcatel-Lucent 5620 Service Aware Manager 6-7

58 MPR/9500 MPRe shelf object configuration 16 E1 (ASAP) card The 16 E1 (ASAP) card enables the management of ATM services on the 9500 MPR, through collecting IMA traffic, terminating the IMA groups, and encapsulating and extracting the ATM cells into and from ATM PW packets toward the core board. ATM interfaces are established over PDH physical interfaces. ATM traffic is transported by the ATM PW service and encapsulated in Ethernet frames. 32 E1 card and 32 DS1 card Two 32-port versions (32 E1 and 32 DS1) are available: provide external interfaces for up to 32 E1 or DS1 ports manage the encapsulation and reconstruction of PDH data for standard Ethernet packets send and receive standard Ethernet packets to and from core-enhanced cards contain the switch for EPS core protection generate internal DC power See Procedure 7-4 for information about configuring ports on the 32 E1 card or 32 DS1 card. 2 DS3 card Two DS3 ports are available: support up to six units per shelf provide 1+1 EPS protection See Procedure 7-5 for information about configuring ports on the 2 DS3 card. 1 STM (Channelized) card The 1 STM (Channelized) card can be configured in all card slots on the 9500 MPR. Up to one port can be configured. This ETSI card supports SFP-O and SFP-E port usage type. Up to 63 E1 channels are supported. Services are deployed at the E1 channel level as TDM. See Procedure 7-3 for information about configuring ports on the 1 STM (Channelized) card. AUX alarm card The AUX alarm card provides support to monitor a number of housekeeping, station input, and station output alarms. The support for the AUX alarm card only applies to following alarm types: card fail card missing equipment mismatch unconfigured equipment firmware download in progress housekeeping 6-8 Alcatel-Lucent 5620 Service Aware Manager

59 MPR/9500 MPRe shelf object configuration See the Alarm Reference for the alarm descriptions, the generating and clearing conditions of alarms, and the remedial actions to fix the problems. Only one AUX alarm card is supported per 9500 MPR MSS shelf. On the MSS-4 shelf, the AUX alarm card is supported in slot 4. On the MSS-8 shelf, the AUX alarm card is supported in slot 8. See Procedure 7-6 for information about configuring ports on the AUX alarm card. 6.4 Workflow to manage shelf objects on 9500 MPR/9500 MPRe devices The following workflow describes the sequence of high-level tasks required to configure and manage 9500 MPR/9500 MPRe device shelf objects; see the Shelf object configuration chapter in the User Guide for the generic procedures that apply to this device type. Also, configure the following device-specific tasks or functions: 1 As required, perform the following procedures to configure 9500 MPR/9500 MPRe device shelf objects. a Configure NTP on 9500 MPR devices; see the Shelf object configuration chapter in the User Guide. Note When adding an NTP server, can allow invalid configuration in the form. Close the form and re-open it to retry the operation with correct values. b Migrate a 9500 MPRe connected to a 7705 SAR from standalone mode to single NE mode; see Procedure 6-1. c Manage 9500 MPR running software; see Procedure 6-2. d Configure a basic or advanced fan tray on the 9500 MPR; see Procedure As required, configure the card and card slot objects as follows: a Assign a card type to a chassis slot; see the Shelf object configuration chapter in the User Guide. b Add 9500 MPR card protection; see Procedure 6-4. c Remove 9500 MPR card protection; see Procedures As required, switch between an in-service protected radio link and a standby protected radio link for 9500 MPR devices; see Procedures MPR/9500 MPRe shelf object configuration procedures Use the following procedures to configure shelf objects using the navigation tree. Alcatel-Lucent 5620 Service Aware Manager 6-9

60 MPR/9500 MPRe shelf object configuration Procedure 6-1 To migrate the 9500 MPRe connected to a 7705 SAR from standalone mode to single NE mode The following requirements must be met before you change the 9500 MPRe from standalone mode to single NE mode: Ensure that the 7705 SAR is upgraded to Release 6.0 R1 and the 9500 MPRe is upgraded to Release Ensure that the MPT software packages are in the cf3:/images/<timos.xx.xx> directory on the 7705 SAR NE. Ensure that the MWA converted database (*.tar) file is in the cf3:<config file path> on the 7705 SAR NE. Ensure that the MPT state is operationally up when it is in standalone mode by connecting it to the 7705 SAR. Note 1 This procedure assumes you have configured a 7705 SAR MW link and link member before starting this procedure; see the Shelf object configuration chapter in the User Guide. Note 2 If the 9500 MPRe is discovered as a standalone device on the, then later changed to single NE mode, you must manually remove the 9500 MPRe node from the database because it shows as unreachable on the. Note 3 For information about the 7705 SAR and 9500 MPRe, see the 9500 MPRe user documentation and the appropriate 7705 SAR 6.0 R1 hardware guides. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Choose Network NE Shelf, where shelf is the 7705 SAR shelf object. 3 Click on the shelf object to expand the tree view. 4 Right-click on the port that you associated with the MW link and choose Properties. The MW Link Member (Edit) form opens with the General tab displayed Alcatel-Lucent 5620 Service Aware Manager

61 MPR/9500 MPRe shelf object configuration 5 Configure the parameters, if required: Radio Name StandAlone Database Filename Note 1 For migration, restart the MPT using the MCT and deselect the Standalone check box within 30 to 60 s of the radio restart or the MPT may not function as expected. If the restart fails to change the MPT to single NE mode, the MPT must be physically restarted. Note 2 You can use the MCT only if the 9500 MPRe is in standalone mode and managed by the. If the 9500 MPRe is connected to the 7705 SAR in standalone mode, but not managed by, you must use the NEtO/MCT. 6 Click on the Radio tab. 7 Configure the parameters, if required: Radio Transmit State Reboot 8 Click on the OK button. A dialog box appears. 9 Click on the Yes button. The MW Link Member (Edit) form closes. Alcatel-Lucent 5620 Service Aware Manager 6-11

62 MPR/9500 MPRe shelf object configuration Procedure 6-2 To manage the 9500 MPR/9500 MPRe running software Perform this procedure to manage the software in the 9500 MPR/9500 MPRe committed and standby banks. You can upgrade or downgrade the running software release on a 9500 MPR/9500 MPRe. See NE maintenance overview in the System Administrator Guide for information about creating software upgrade policies and performing software upgrades. During the software upgrade, the NE audit process is not supported for 9500 MPR NEs. Warning A 9500 MPR/9500 MPRe may require a firmware upgrade before a device software upgrade. To avoid a service outage, ensure that the device firmware version supports the software upgrade. See the device software Release Notes to obtain information about firmware and software release compatibility. Caution When you reboot a 9500 MPR/9500 MPRe that is in service, it is service-affecting. Ensure that the reboot activity occurs during a maintenance window. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR/9500 MPRe NE object. 3 Right-click on the 9500 MPR/9500 MPRe device that you need to upgrade or downgrade and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 4 Click on a shelf object. The Shelf (Edit) form opens with the General tab displayed. 5 Click on the Software Bank Details tab. The committed and standby software information is displayed. The committed software is the software currently running on the 9500 MPR/9500 MPRe. The standby software is new software uploaded to the 9500 MPR/9500 MPRe or formerly committed software. 6 Verify that the operational state of the standby software is Enabled, by examining the Operational State column of the displayed list. You can also examine the Software Version of the standby and committed software. If the software version of the standby software is more recent than the committed software version, the 9500 MPR/9500 MPRe can be upgraded. If the standby software version is older than the committed software version, the 9500 MPR/9500 MPRe can be downgraded. 7 Choose the standby entry from the displayed list. 8 Click on the Properties button. 9 The MPRSoftwarePackage (Edit) form opens with the Software Bank Details tab displayed. 10 Configure the Activation parameter Alcatel-Lucent 5620 Service Aware Manager

63 MPR/9500 MPRe shelf object configuration 11 Click on the OK button. The MPRSoftwarePackage (Edit) form closes. The entry in the Activation column for the standby software should be the same as the option chosen in step Click on the OK button. A dialog box appears. 13 Click on the Yes button. When the standby and committed software versions are different or the forced activation option is selected, the 9500 MPR/9500 MPRe reboots using the standby software. If the standby and committed software versions are the same and the activation option is chosen, the 9500 MPR/9500 MPRe does not reboot and the Shelf (Edit) form closes. 14 When the 9500 MPR/9500 MPRe reboots, you can confirm that the 9500 MPR/9500 MPRe is running the software stored in the former standby bank. The former standby software is the committed software and the previous committed software is the standby software. Procedure 6-3 To configure a 9500 MPR basic or advanced fan tray For the advanced fan tray, you can configure four ports for housekeeping alarms. If you configured a basic fan and you need to change to an advanced fan, you do not need to decommission the basic fan first. The advanced fan is only supported on the 9500 MPR Release 4.2 or later. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR NE object. 3 RIght-click on a shelf object. The Shelf (Edit) form opens with the General tab displayed. 4 Click on the Fan Trays tab. 5 Click on the Create button. The Fan Tray (Create) form opens. 6 Configure the parameters: Tray ID Fan Type 7 If you configured the Fan Type parameter as A-Fan, go to step 8. Otherwise, go to step Click on the External Point Inputs tab. 9 Click on the Properties button. The Auxiliary Inputs (Edit) form opens with the Aux Input tab displayed. Alcatel-Lucent 5620 Service Aware Manager 6-13

64 MPR/9500 MPRe shelf object configuration 10 Configure the parameters, as required: User Label Polarity 11 Click on the OK button. The Auxiliary Inputs (Edit) form closes and the Fan Tray (Edit) form reappears. 12 Repeat steps 8 to 11 to configure more ports for housekeeping alarms, as required. 13 Click on the OK button. A dialog box appears. 14 Click on the Yes button. The Fan Tray (Edit) form closes. Procedure 6-4 To configure 9500 MPR card protection The 9500 MPR supports card protection for all card types. EPS card protection for the CORE-ENH card in slot 1 is automatically configured by the system when an optional spare CORE-ENH card is provisioned into slot 2. Radio modem and 32 x DS1/E1 cards in slots 3, 5, and 7 can be protected by corresponding identical cards in slots 4, 6, and 8. Protection for cards in slots 3, 5, and 7 must be configured. The protected card is referred to as the main card and the protecting card is referred to as the spare card. Use the following procedure to configure optional card protection for radio modem and 32 x DS1/E1 cards. Note 1 All cross connections, flow-ids, and synchronization sources must be removed from the port under the spare card slot before protection can be enabled. Note 2 To configure protection type 1+1 FD on Radio, the Mode cannot be Adaptive Modulation. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Right-click on the 9500 MPR object and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 3 On the Network Element (Edit) form navigation tree, expand the Shelf object. 4 Click on the card slot object that you need to configure. The Card Slot (Edit) form opens with the General tab displayed. 5 Click on the Protection tab. 6 Configure the following parameters on the main/spare card: Protection Type Restoration Criteria Commands 7 Click on the OK button. A dialog box appears Alcatel-Lucent 5620 Service Aware Manager

65 MPR/9500 MPRe shelf object configuration 8 Click on the Yes button. The Card Slot (Create) form closes. 9 Verify that the protection is enabled. The status of the main card should be Active and the status of the spare card should be Standby. Procedure 6-5 To remove 9500 MPR card protection Note If 1+1 HSB is configured as the protection type for a radio card, the transmitter must be muted from the NEtO to remove the protection. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Right-click on the 9500 MPR object and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 3 On the Network Element (Edit) form navigation tree, expand the Shelf object. 4 Click on the card slot object that you need to configure. The Card Slot (Edit) form opens with the General tab displayed. 5 Click on the Protection tab. 6 Set the Protection Type parameter to No Protection. 7 Click on the OK button. A dialog box appears. 8 Click on the Yes button. The Card Slot (Create) form closes. 9 Verify that the protection is removed from the previously main and spare cards. Procedure 6-6 To switch between a 9500 MPR in-service protected radio link and a standby protected radio link You can switch between an in-service protected radio link and a standby protected radio link on 9500 MPR devices to reroute traffic when you need to perform routine maintenance on the radio link. This procedure assumes that link protection has been configured prior to starting this procedure; see Procedure This procedure only applies to switching radio links that terminate on port endpoints. 1 On the Physical topology map, select a radio link group between two 9500 MPR NEs. The plus sign on the link group highlights. 2 Right-click on the plus sign and choose Expand Group to view all radio links. In-service protected radio links are represented as green links; standby links are shown as blue links. Alcatel-Lucent 5620 Service Aware Manager 6-15

66 MPR/9500 MPRe shelf object configuration To switch radio links that terminate on Radio Modem cards, go to step 3. The configuration to perform the switchover for this card type is done at the card level. To switch radio links that terminate on 2+2 (EAS), 4+4 (EAS), or CORE-ENH cards, go to step 11. The configuration to perform the switchover for these card types is done at the port level. 3 Expand the Shelf icon to display the available Radio Modem cards. 4 Right-click on one of the 9500 MPR link endpoints and choose Properties. The Network Elements [Edit form] opens. 5 Right-click on the Radio Modem-MAIN card and choose Properties. The Card Slot, Radio Modem [Edit] form opens with the General tab displayed. 6 Click on the Protection tab and choose one of the following Commands parameter options on the Equipment Protection Scheme Parameters panel to initiate the switchover: Manual (switchover condition checks are validated before the switch) Forced (switchover condition checks are skipped) 7 Click on the OK button to make the changes and close the Card Slot, Radio Modem [Edit] form. 8 A confirmation box appears. Click the Yes button to proceed. 9 Repeat steps 4 to 8 on the second 9500 MPR link endpoint to complete the switchover. The standby radio link becomes the in-service radio link and traffic is re-routed over this link. 10 Verify the switchover occurred by repeating steps 4 to 5 on the Radio Modem-SPARE card and clicking on the Protection tab and verifying that the Status parameter on the Equipment Protection Scheme Parameters panel reads Active. 11 Right-click on an in-service radio link port and choose Properties. The Radio Link-Physical Port (Edit) form opens with the General tab displayed. 12 Click on the Properties button for Endpoint A-Port. The Physical Port (Edit) form opens with the General tab displayed. 13 Click on the Protection tab and choose one of the following Commands parameter options on the Receiver Protection Scheme Parameters panel to initiate the switchover: Manual (switchover condition checks are validated before the switch) Forced (switchover condition checks are skipped) 14 Click on the OK button to make the changes and close the Physical Port (Edit) form. A confirmation box appears. Click the Yes button to proceed Alcatel-Lucent 5620 Service Aware Manager

67 MPR/9500 MPRe shelf object configuration 15 Repeat steps 11 to 14 for Endpoint B - Port on the same radio link to complete the switchover. The standby radio link becomes the in-service radio link and traffic is re-routed over this link. 16 Verify the switchover occurred by repeating steps 11 to 12 for the card and clicking on the Protection tab and verifying that the Status parameter on the Receiver Protection Scheme Parameters panel reads Active. Procedure 6-7 To configure MPT-HLS radio The MPT-HLS is configured on the core-enhanced card or an EASv2 card. The MPT-HLS radio is configured in an ETSI rack. Inside the ETSI rack two different RT subracks are available with up to 10 transceivers in each. For each RT subrack two fan subracks can be configured. Enable subracks 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Right-click on the 9500 MPR object and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 3 Click on the Subracks tab. The bottom and top subracks are listed. 4 Choose a subrack and click on the Properties button. The Sub Racks (Edit) form opens with the General tab displayed. 5 Set the Subrack Status parameter to Enabled. 6 Click on the Apply button. A dialog box appears. 7 Click on the OK button. The dialog box closes and the Sub Racks (Edit) form reappears. 8 Click on the OK button. The Sub Racks (Edit) form closes and the Network Element (Edit) form reappears. 9 Click on the Apply button. A dialog box appears. 10 Click on the Yes button. The dialog box closes and the Network Element (Edit) form reappears. 11 Close the Network Element (Edit) form. Configure MPT-HLS radio 12 Choose 9500 MPR Shelf Card (CORE-ENH or EASv2) Port (5 or 6 of CORE-ENH; 5,6,7, or 8 of EASv2) on the navigation tree. 13 Right-click on the port object and choose Properties from the contextual menu. The Physical Port (Edit) form opens with the General tab displayed. 14 Set the Port Usage parameter to MPT-HLS. The Subrack Connection Panel appears. Alcatel-Lucent 5620 Service Aware Manager 6-17

68 MPR/9500 MPRe shelf object configuration 15 Click on the Select button beside the Slot parameter in the Subrack Connection panel. The Select Subrack Connection form opens with a list of subracks. 16 Choose a subrack where the MPT-HLS needs to be configured and click on the OK button. The Select Subrack Connection form closes and the Physical Port (Edit) form reappears with the Subrack Connection panel updated with the subrack information. 17 Click on the Apply button. A dialog box appears. 18 Click on the Yes button to complete the configuration. Deployment icons appear beside parameters for which a deployment is in progress. 19 Wait for the deployment to be completed and close the Physical Port (Edit) form. Configure the fan 20 Right-click on the 9500 MPR object and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 21 Click on the Subracks tab. The bottom and top subracks are listed. 22 Choose the subrack where MPT-HLS is configured and click on the Properties button. The Sub Racks (Edit) form opens with the General tab displayed. 23 Click on the Subrack Elements tab. The subracks where MPT-HLS can be configured are listed from Slot 1 to 10 and the subracks where fans can be configured are listed from Slot 11 to Choose Slot 11 or 12 subrack and click on the Properties button. The Subrack Elements (Edit) form opens with the Subrack Elements tab displayed. 25 Configure the Equipment Type parameter. The Fan details panel appears. Note The Equipment Type parameter has three values: Empty SR-Fan4 SR-Fan8 Fan 4 occupies one slot and Fan 8 occupies two slots. 26 Click on the Select button beside the Name parameter in the Fan details panel. The Select First Fan Handler form opens with a list of ports that are configured with the MPT-HLS radio. 27 Choose a port and click on the OK button. The Select First Fan Handler form closes and the Subrack Elements (Edit) form reappears. Note 1 Optionally, you can configure two fan handlers, First Fan Handler and Second Fan Handler. A minimum of one fan handler configuration is mandatory. Note 2 An MPT-HLS port can be mapped to only one fan handler. 28 Click on the Apply button. A dialog box appears Alcatel-Lucent 5620 Service Aware Manager

69 MPR/9500 MPRe shelf object configuration 29 Click on the OK button. The dialog box closes and Subrack Element (Edit) form reappears. 30 Click on the OK button. A dialog box appears. 31 Click on the OK button. The Subrack Elements (Edit) form closes and the Sub Racks (Edit) form appears with the updated list of subracks. 32 Click on the Apply button. A dialog box appears. 33 Click on the OK button. The dialog box closes and Sub Racks (Edit) form reappears. 34 Click on the OK button. A dialog box appears. 35 Click on the OK button. The Sub Racks (Edit) form closes and the Network Element (Edit) form reappears. 36 Click on the Apply button. A dialog box appears. 37 Click on the Yes button to save the changes. 38 Close the Network Element (Edit) form. Alcatel-Lucent 5620 Service Aware Manager 6-19

70 MPR/9500 MPRe shelf object configuration 6-20 Alcatel-Lucent 5620 Service Aware Manager

71 MPR/9500 MPRe port object configuration MPR/9500 MPRe port configuration overview Workflow to manage port objects on 9500 MPR/9500 MPRe devices Port configuration procedures 7-4 Alcatel-Lucent 5620 Service Aware Manager 7-1

72 MPR/9500 MPRe port object configuration MPR/9500 MPRe port configuration overview Port objects are children of card slot objects. Port objects appear below the card slot after the card is configured. Port objects for 9500 MPR/9500 MPRe devices can be configured for plug-in cards; there are no daughter cards associated with these devices. Properties forms for port objects are accessed using the navigation tree. You can configure the following 9500 MPR device ports: Ethernet ports 2 STM card ports 1 STM (Channelized) card port E1 and DS1 ports DS3 ports 1 radio modem ports AUX alarm ports 9500 MPRe ports See the Port and channel object configuration chapter in the User Guide for more information about working with port objects. IMA support For 9500 MPR/9500 MPRe devices, IMA is supported on the 16 E1 ASAP Access (ETSI) card. Each IMA group bundle can have up to 16 links and there can be up to 8 IMA groups on a card. Each ATM interface supports up to 48 VP/VC connection points. Each 16 E1 ASAP Access (ETSI) board supports up to 128 VP/VC connection points. An IMA group bundle has the following common interface properties: ATM encapsulation type is displayed in the ATM Interface form by clicking on the Edit ATM button. ATM interface characteristics can be viewed by clicking on the Edit ATM button on the Bundle Properties form. Interface mode is access only for the 9500 MPR. MTU value (of the primary link) Combiner support You can enable or disable a combiner on the port by configuring the Combiner parameter on the Port Usage panel in the port properties form of the following types of radio ports: MPT-HLC MPT-HLS 7-2 Alcatel-Lucent 5620 Service Aware Manager

73 MPR/9500 MPRe port object configuration 9500 MPR Ethernet port QoS schemes You can configure the following protection schemes on 9500 MPR Ethernet ports: traffic storm control A traffic storm occurs when packets flood a LAN creating excessive traffic and degrading network performance. You can use traffic storm control to prevent Ethernet ports from being disrupted by a broadcast, multicast, or unicast traffic storm on the physical interfaces, and limit the impact of VLAN misconfigurations. Traffic storm control monitors the incoming traffic levels over a 1-s interval and, during the interval, compares the traffic level with the traffic storm control level that you configure on the. The traffic storm control level is a percentage of the total available bandwidth of the Ethernet port. For example, if traffic storm control is enabled for ingress traffic and it reaches the configured level on the port with the interval, the traffic is dropped until the traffic storm control interval ends. port rate limiting You can use port rate limiting to protect the radio-side bandwidth from being overloaded by an ingress or egress port. A common application for port rate limiting is when a 9500 MPR provides the backhaul service for multiple 7705 SAR devices whose queues do not have the visibility of the bandwidth available of the radio side. dot1q VLAN rate limiting You can use VLAN rate limiting to protect the radio side bandwidth on the 9500 MPR from being overloaded by an ingress port when transporting IP/MPLS over MPR transport services on dot1q VLANs. A common application of the VLAN rate limiting feature is to monitor the 9500 MPR backhaul services providing transport to multiple 7705 SAR devices whose queues could individually exceed the available radio bandwidth. Traffic storm control, port rate limiting, and dot1q VLAN rate limiting are supported on the core-enhanced card and the 4+4 Ethernet (EAS) card on the 9500 MPR. See Procedure 7-1 for information about enabling traffic storm control, port rate limiting, and dot1q VLAN rate limiting on the 9500 MPR. Alcatel-Lucent 5620 Service Aware Manager 7-3

74 MPR/9500 MPRe port object configuration 7.2 Workflow to manage port objects on 9500 MPR/9500 MPRe devices The following workflow describes the sequence of high-level tasks required to configure and manage 9500 MPR or 9500 MPRe device ports; see the Port and channel object configuration chapter in the User Guide for the generic procedures that apply to this device type. In addition, configure the following device-specific procedures as required: 1 As required, change the port mode between Network, Access, and Hybrid modes. See the Port and channel object configuration chapter in the User Guide for the generic procedures that apply to this device type. 2 As required, configure the ports on 9500 MPR or 9500 MPRe devices: a Ethernet ports; see Procedure 7-1 b 2 STM card ports; see Procedure 7-2 c 1 STM (Channelized) card port; see Procedure 7-3 d E1 and DS1 ports; see Procedure 7-4 e DS3 ports; see Procedure 7-5 f AUX alarm ports; see Procedure 7-6 g 9500 MPRe ports; see Procedure As required, configure or perform the following on 9500 MPR or 9500 MPRe device ports: a b analog performance management on 9500 MPR 1x radio modem ports; see Procedure 7-8 power level performance management on 9500 MPR 1x radio modem ports; see Procedure 7-9 c 9500 MPR port segregation; see Procedure 7-10 d e f power source type on 2+2 Ethernet (EAS) card slots for 9500 MPR; see Procedure 7-11 add or delete 9500 MPR port protection; see Procedures 7-13 or Procedure 7-14 loopback test on a 9500 MPR DS1, ES1, or 1x radio modem port; see Procedure Port configuration procedures Use the following procedures to manage 9500 MPR or 9500 MPRe device ports using the navigation tree. 7-4 Alcatel-Lucent 5620 Service Aware Manager

75 MPR/9500 MPRe port object configuration Procedure 7-1 To configure 9500 MPR/9500 MPRe Ethernet ports 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR NEs icon. 3 Right-click on the device where you need to configure an 9500 MPR Ethernet port and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 4 On the Network Element (Edit) form navigation tree, expand the Shelf icon. 5 Expand to the port level and click on a port object. The Physical Port (Edit) form opens with the General tab displayed. 6 Configure the Port Usage parameter if you are provisioning the following ports: ports 1 to 4 on the 2+2 Ethernet (EAS) card ports 5 to 8 on the 4+4 Ethernet (EAS) card ports 1 to 6 on the core-enhanced card 7 Configure the parameters: Current OLC State User Label Note The User Label parameter configuration must be limited to a maximum of 15 characters. 8 Click on the States tab. 9 Configure the Administrative State parameter. 10 Click on the Ethernet tab. The Ethernet port configuration form opens with the General tab displayed. 11 Configure the parameters: Duplex Auto-negotiate Advertised Capability Note Check the combinations that are supported for the Advertised Capability parameter in the Configure the following parameters if you need to enable traffic storm control on the ports. See 9500 MPR Ethernet port QoS schemes in this section. Enable Unicast Frame Rate (Frames/sec) Multicast Frame Rate (Frames/sec) Broadcast Frame Rate (Frames/sec) Alcatel-Lucent 5620 Service Aware Manager 7-5

76 MPR/9500 MPRe port object configuration 13 Configure the following parameters if you need to enable port rate limiting on the ports. See 9500 MPR Ethernet port QoS schemes in this section. Ingress Enabled Ingress CIR (Kb/s) Ingress Max Burst (KB) Egress Enabled Egress CIR (Kb/s) Egress Max Burst (KB) 14 Click on the VLAN Rate Limiter tab if you need to police the input bandwidth on dot1q VLANs. The Ethernet ports that support VLAN rate limiting are listed. See 9500 MPR Ethernet port QoS schemes in this section. Note 1 VLAN rate limiting should not be activated in conjunction with port rate limiting configured in step 13. Note 2 You can enable up to eight VLAN rate limits on an Ethernet port. 15 Choose an Ethernet port to apply VLAN rate limiting and click on the Properties button. The VLAN Rate Limiter (Edit) form opens with the General tab displayed. 16 Configure the parameters: Enable VLAN Rate Limit Ingress CIR (Kb/s) Ingress Max Burst (KB) 17 Repeat steps 15 and 16, as required, to configure more Ethernet ports for VLAN rate limiting. 18 Click on the OK button. The Physical Port (Edit) form reappears. 19 Click on the OK button. A dialog box appears. 20 Click on the OK button. The Physical Port (Edit) form closes. Procedure 7-2 To configure 9500 MPR 2 STM ports 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR NEs icon. 3 Right-click on the card where you need to configure the 2 STM card type and choose Configure card from the contextual menu. The Card Slot (Create) form opens with the General tab displayed. 4 Set the Assigned Card Type parameter to 2xSTM. The card is configured and two ports are displayed. 5 Expand to the port level and right-click on Properties. The Physical Port (Edit) form opens with the General tab displayed. 7-6 Alcatel-Lucent 5620 Service Aware Manager

77 MPR/9500 MPRe port object configuration 6 Configure the User Label parameter. 7 In the Port Usage panel, configure the ports by choosing one of the following: EMPTY SFP-O SFP-E Note 1 To configure the User Label parameter, you need to set the port usage type to SFP-O or SFP-E in step 7. Note 2 The User Label parameter configuration must be limited to a maximum of 15 characters. a b c When you set the port to SFP-O, the 2 STM port is configured and the Protection tab is enabled. See Procedure 6-4 for more information about card protection. When you set the port to SFP-E, the 2 STM port is configured but the Protection tab is disabled. When you set the port to EMPTY, all the configured ports revert to an empty slot after the port is shut down. Note 1 You need to shut down the configured port to remove the port. Select the port and choose Port Shut Down. Choose Port Properties. Configure the Port Usage parameter to EMPTY. The SFP-O ports are removed. You can now configure other ports. Note 2 Protection for cards is at the card level, and cannot be configured at the port level. Configure protection for the main cards and the spare cards. Note Protection can be set at different card levels. This provides redundancy. 8 After the SFP-O ports are configured, choose Card Properties. The Card [Edit] form opens with the Protection tab enabled. 9 Set the Protection Type parameter to 1+1 EPS protection. All of the SFP-O ports are protected. 10 Click on the OK button to save the change. A dialog box appears. 11 Click on the Yes button. The Card [Edit] form closes. Procedure 7-3 To configure 9500 MPR 1 STM (Channelized) ports 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR NEs icon. Alcatel-Lucent 5620 Service Aware Manager 7-7

78 MPR/9500 MPRe port object configuration 3 Right-click on the card where you need to configure the 1 STM (Channelized) card type and choose Configure card from the contextual menu. The Card Slot [Create] form opens with the General tab displayed. 4 Set the Assigned Card Type parameter to 1 STM (Channelized). 5 Expand to the port level and right-click on Properties. The Physical Port [Edit] form opens with the General tab displayed. 6 In the Port Usage panel, configure the ports by choosing one of the following: EMPTY SFP-O SFP-E a b c When you set the port to SFP-O, the 1 STM port is configured and the Protection tab is enabled. See Procedure 6-4 for more information about card protection. When you set the port to SFP-E, the 1 STM port is configured but the Protection tab is disabled. When you set the port to EMPTY, all the configured ports revert to an empty slot after the port is shut down. Note 1 You need to shut down the configured port to remove the port. Select the port and choose Port Shut Down. Choose Port Properties. Configure the Port Usage parameter to EMPTY. The SFP-O ports are removed. You can now configure other ports. Note 2 Protection for cards is at the card level, and cannot be configured at the port level. Configure protection for the main cards and the spare cards. Protection is enabled only for the SFP-O port. Note Protection can be set at different card levels. This provides redundancy. Both cards should be enabled and configured to SFP-O before protection is set. 7 After the SFP-O port is configured, select Card Properties. The Card [Edit] form opens with the Protection tab enabled. 8 From the Protection Type drop-down menu, select 1+1 EPS protection. The SFP-O port is protected. 9 Expand to the channel level and right-click on a channel. The Channel [Edit] form opens. 7-8 Alcatel-Lucent 5620 Service Aware Manager

79 MPR/9500 MPRe port object configuration 10 Click on the Channel tab. Configure the User Label parameter. Note 1 To configure the User Label parameter, you need to set the port usage type to SFP-O or SFP-E. See step 6. Note 2 For channels, the user label can be configured only for the channels, and not for ports. Note 3 The User Label parameter configuration must be limited to a maximum of 15 characters. 11 Click on the OK button to save the change. A dialog box appears. 12 Click on the Yes button. The Card [Edit] form closes. Procedure 7-4 To configure 9500 MPR E1 and DS1 ports 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR NEs icon. 3 Right-click on the device where you need to configure a 9500 MPR E1 or DS1 port and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 4 On the Network Element (Edit) form navigation tree, expand the Shelf icon. 5 Expand to the port level and click on a port object. The Physical Port (Edit) form opens with the General tab displayed. 6 Configure the parameters: Current OLC State User Label Note The User Label parameter configuration must be limited to a maximum of 15 characters. 7 Click on the States tab. 8 Configure the Administrative State parameter. 9 Click on the DS1/E1 tab. 10 Configure the parameters: Signal Mode Line Code If you are configuring an E1 port, you can only configure the Signal Mode parameter. Alcatel-Lucent 5620 Service Aware Manager 7-9

80 MPR/9500 MPRe port object configuration 11 Click on the other tabs in the properties form to view more port information. 12 Click on the OK button. A dialog box appears. 13 Click on the Yes button. The Physical Port (Edit) form closes. Procedure 7-5 To configure 9500 MPR DS3 ports 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR NEs icon. 3 Right-click on the device where you need to configure a 9500 MPR DS3 port and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 4 On the Network Element (Edit) form navigation tree, expand the Shelf icon. 5 Expand to the port level and click on a port object. The Physical Port (Edit) form opens with the General tab displayed. 6 Configure the parameters: Current OLC State User Label Note The User Label parameter configuration must be limited to a maximum of 15 characters. 7 Click on the States tab. 8 Configure the Administrative State parameter. 9 Click on the DS3/E3 tab. 10 Configure the parameters: Signal Mode Line Code AIS Signal Type 11 Click on the other tabs in the properties form to view more port information. 12 Click on the OK button. A dialog box appears. 13 Click on the Yes button. The Physical Port (Edit) form closes Alcatel-Lucent 5620 Service Aware Manager

81 MPR/9500 MPRe port object configuration Procedure 7-6 To configure 9500 MPR AUX alarm ports This procedure applies only to ports on 9500 MPR, Release 3.0 and later, AUX alarm cards. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR NE icon to the MSS shelf level. 3 Right-click on an empty card slot and choose Configure Card from the contextual menu. The Card Slot - Shelf (Create) form opens with the General tab displayed. Note Only one AUX alarm card is supported per 9500 MPR MSS shelf. On the MSS-4 shelf, the AUX alarm card is supported in slot 4. On the MSS-8 shelf, the AUX alarm card is supported in slot 8. 4 Set the Assigned Card Type parameter to AUX and click on the OK button to apply the changes. 5 Right-click on the AUX alarm card and choose Properties from the contextual menu. The Card Slot [Port Number], AUX, Shelf (Edit) form opens with the General tab displayed. 6 Click on the External Point Inputs tab. 7 Double-click on a port. The Auxiliary Input - auxin [Edit] form opens. 8 Configure the parameters: User Label Note The User Label parameter configuration must be limited to a maximum of 15 characters. Polarity 9 Click on the OK button to apply the changes. 10 Click on the External Point Outputs tab. 11 Double-click on a port. The Auxiliary Output - auxout [Edit] form opens. 12 Configure the parameters: User Label Note The User Label parameter configuration must be limited to a maximum of 15 characters. Polarity External State 13 Click on the OK button to apply the changes. Alcatel-Lucent 5620 Service Aware Manager 7-11

82 MPR/9500 MPRe port object configuration 14 Optionally, click on the Aux Card Specifics tab or IO Card tab to display more read-only AUX alarm card properties. 15 Click on the OK button to apply the changes and close the Card Slot [Port Number], AUX, Shelf (Edit) form. Procedure 7-7 To configure a 9500 MPRe port Perform this procedure to configure the OLC parameters and administrative state of a 9500 MPRe port. All other radio port parameters must be configured using the MCT. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPRe icon to the port level and click on a port object. The Physical Port (Edit) form opens with the General tab displayed. 3 Right-click on the device where you need to configure a 9500 MPRe port and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 4 Configure the Current OLC State and Revert OLC State parameters. 5 Click on the OK button. A dialog box appears. 6 Click on the OK button. The Physical Port (Edit) form closes. Procedure 7-8 To configure analog performance management on 9500 MPR 1x radio modem ports This procedure provides the analog radio statistics for 9500 MPR 1x radio modem ports. Note 1 When per-queue statistics are collected, Q1 record is not available for the collected statistics. Note 2 When per-queue statistics are collected, nothing is returned by the NE. Note 3 When plotting is performed real-time, a data missing exception occurs for the specific interval. Note 4 The retrieve time is not correctly updated. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR NEs icon Alcatel-Lucent 5620 Service Aware Manager

83 MPR/9500 MPRe port object configuration 3 Right-click on the device on which you want to configure analog performance management and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 4 On the Network Element (Edit) form navigation tree, expand the Shelf icon. 5 Expand to the port level and click on a port object. The Physical Port (Edit) form opens with the General tab displayed. 6 Click on the Statistics tab. 7 In the Select Object Type area, choose Radio Analog Statistics (Radio Equipment) from the contextual menu. 8 Click on the Collect button. 9 A statistics record appears in the Physical Port (Edit) form. Select the record. 10 Click on the Properties button. The Statistics Record - Radio Analog Statistics form opens. 11 View the read-only analog performance parameter values for the 1x radio modem port. 12 Click on the Close button. The Statistics Record - Radio Analog Statistics form closes. 13 Close the Physical Port (Edit) form. Procedure 7-9 To configure power level performance management on 9500 MPR 1x radio modem ports Note 1 When per-queue statistics are collected, Q1 record is not available for the collected statistics. Note 2 When per-queue statistics are collected, nothing is returned by the NE. Note 3 When plotting is performed real-time, a data missing exception occurs for the specific interval. Note 4 The retrieve time is not correctly updated. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR NEs icon. 3 Right-click on the device on which you want to configure power level performance management and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 4 On the Network Element (Edit) form navigation tree, expand the Shelf icon. Alcatel-Lucent 5620 Service Aware Manager 7-13

84 MPR/9500 MPRe port object configuration 5 Expand to the port level and click on a port object. The Physical Port (Edit) form opens with the General tab displayed. 6 Click on the Statistics tab. 7 In the Select Object Type area, choose one of the following from the contextual menu: Hop Current Data Stats Link Current Data Stats RSL Hop Current Data Stats TSL Hop Current Data Stats 8 Click on the Collect button. 9 A statistics record appears in the Physical Port (Edit) form. Select the record. 10 Click on the Properties button. The Statistics Record - RSL/TSL Hop Current Data Stats form opens. 11 View the read-only power level performance parameter values for the 1x radio modem port. 12 Click on the Close button. The Statistics Record - RSL/TSL Hop Current Data Stats form closes. 13 Close the Physical Port (Edit) form. Procedure 7-10 To configure 9500 MPR port segregation 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR NEs icon. 3 Right-click on the device where you need to configure port segregation and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 4 Click on a shelf object. The Shelf (Edit) form opens with the General tab displayed. 5 Click on the Port Segregation tab. 6 Click on the Create button. The Add Member step form opens. 7 For an EAS module, the Select From Type step is displayed. Choose a value for the From Type parameter from the drop-down menu and click on the Next button. 8 In the From Port step, click on the Select button beside the From Port field. The Select From Port - Port Segregation form opens. 9 Choose a port from the list Alcatel-Lucent 5620 Service Aware Manager

85 MPR/9500 MPRe port object configuration 10 Click on the OK button. The Select From Port - Port Segregation form closes and the Add Member step form reappears. 11 For an EAS module, the Select To Type step is displayed. Choose a value for the To Type parameter from the drop-down menu, and click on the Next button. 12 In the To Port step, choose a port from the list and click on the Finish button. A dialog box appears. 13 Click on the OK button. The Add Member Wizard form closes. 14 To add more port combinations, repeat steps 6 to Click on the OK button. The Shelf (Edit) form closes. Procedure 7-11 To configure a 9500 MPR power source type You can configure the power source type on the following card slots: 2+2 x Ethernet (EAS) EASv2 MSS1 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR NEs icon. 3 Right-click on the device on which you want to configure a power source type and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 4 On the Network Element (Edit) form navigation tree, expand Shelf icon. 5 Expand to the card level and click on a 2+2 Ethernet (EAS), EASv2, or MSS1 card slot object. The Card Slot (Edit) form opens with the General tab displayed. 6 Click on the Power Source tab. 7 Select a displayed interface. If no interface is displayed, click on the Search button and then select a displayed interface. The Power Source (edit) form opens. 8 In the Power Source panel, configure the Type parameter. 9 Click on the OK button. The Power Source (Edit) form closes. 10 The Card Slot (Edit) form reappears. Click on the OK button. A dialog box appears. 11 Click on the Yes button. The Card Slot (Edit) form closes. Alcatel-Lucent 5620 Service Aware Manager 7-15

86 MPR/9500 MPRe port object configuration Procedure 7-12 To configure synchronization on Ethernet ports PDH and SDH data flow is fragmented and the fragments are transmitted over a packet-switched network. The data rates are controlled by the terminating sites using clocks. The rate at which the fragments are transferred varies based on the variations in these clocks. By synchronizing the clocks on the terminating devices, the received fragments are reassembled in the original PDH or SDH data flow at the original bit rate. You can configure synchronization on the Ethernet ports on the following cards: Core-enhanced EASv2 Before configuring synchronous Ethernet, ensure the following. SFP must be configured on ports 5 and 6 on a core-enhanced card. SFP must be configured on ports 5 to 8 on an EASv2 card. Ethernet ports and SFPs must be administratively up. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand to the required port level on the required 9500 MPR device. 3 Right-click on the port and choose Properties from the contextual menu. The Physical Port (Edit) form opens. 4 Click on the Timing tab. 5 Configure the parameters in the Sync-E panel: Operation Mode Operation Role 6 Configure the SSM parameter as Disabled or Enabled to disable or enable the transmission of the synchronization status message over the radio channel. 7 Click on the OK button. A dialog box appears. 8 Click on the Yes button. The Physical Port (Edit) form closes Alcatel-Lucent 5620 Service Aware Manager

87 MPR/9500 MPRe port object configuration Procedure 7-13 To add 9500 MPR port protection Note 1 The Protection tab only appears for MPT-type ports of EAS modules if the corresponding spare port is configured as MPT. Note 2 All cross-connections, flow-ids, and synchronization sources must be removed from the port under the spare card slot before protection can be enabled. Note 3 To configure protection type 1+1 FD on MPT/Radio, the Mode cannot be Adaptive Modulation. Note 4 In Release 3.0.0, for the 2+2 EAS MPT ports, the protect port can be chosen as the consecutive port of the same card or the same port of the corresponding even slot. Note 5 MPT-HC/MC pair protection can be configured on the core-enhanced card. When an MPT pair (MPT-HC or MPT-HCv2 with RPS module, or MPT-MC) is used for a protected configuration, both MPTs must use the same type of GigE port (optical or electrical), to use the same IDU-ODU synchronization method. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR icon, right-click on the 9500 MPR object you need to configure as the main port of the protection pair, and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 3 On the Network Element (Edit) form navigation tree, expand the Shelf icon. 4 Expand the Card Slot icon and click on the port object that you need to configure. The Port (Edit) form opens with the General tab displayed. 5 Click on the Protection tab. 6 Configure the Protection Type parameter on the main/spare MPT port. 7 For radio ports, configure the parameters: Restoration Criteria in the Receiver Protection Scheme Parameters panel Commands Receiver Protection Scheme Parameters panel Restoration Criteria in the Transmitter Protection Scheme Parameters panel. Commands in the Transmitter Protection Scheme Parameters panel. Note For Protection Type, 1+1 FD, Transmitter Protection Scheme parameters are not applicable. 8 Click on the OK button. A dialog box appears. Alcatel-Lucent 5620 Service Aware Manager 7-17

88 MPR/9500 MPRe port object configuration 9 Click on the Yes button. The Port (Edit) form closes. 10 Verify that the protection is enabled. The status of the main port should be Active and the status of the spare port should be Standby. Procedure 7-14 To remove 9500 MPR port protection Note If 1+1 HSB is configured as the protection type for an MPT port, the transmitter must be muted from the NEtO to remove the protection. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR icon, right-click on the 9500 MPR spare port object, and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 3 On the Network Element (Edit) form navigation tree, expand the Shelf icon. 4 Expand the Card Slot icon and click on the port object that you need to configure. The Port (Edit) form opens with the General tab displayed. 5 Click on the Protection tab. 6 Set the Protection Type parameter to No Protection. 7 Click on the OK button. A dialog box appears. 8 Click on the Yes button. The Port (Edit) form closes. 9 Verify that the protection is removed from the previously main and spare ports. Procedure 7-15 To configure a loopback test on a 9500 MPR DS1, ES1, STM, or 1 x radio modem port Perform the steps in this procedure as required on the port type that you are configuring. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Expand the 9500 MPR NEs icon. 3 Right-click on the device on which you want to configure a loopback test and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 4 On the Network Element (Edit) form navigation tree, expand the Shelf icon Alcatel-Lucent 5620 Service Aware Manager

89 MPR/9500 MPRe port object configuration 5 Expand to the port level and click on a 9500 MPR port object (DS1, ES1, or 1x radio modem). The Physical Port (Edit) form opens with the General tab displayed. 6 Click on the Loopback tab. 7 Two interfaces are available - line facing and core facing. Select an interface. Click on the Properties button. 8 The Loopback (Edit) form opens. 9 Configure the parameters: Activation Timeout Period (Days) Timeout Period (Hrs) Timeout Period (Mins) 10 Click on the OK button. The Loopback (Edit) form closes. 11 On the Physical Port (Edit) form, click on the OK button. 12 The Physical Port (Edit) form closes. Note If the card containing the ports is configured but not equipped, a loopback test cannot be performed on the physical ports of the card. Alcatel-Lucent 5620 Service Aware Manager 7-19

90 MPR/9500 MPRe port object configuration 7-20 Alcatel-Lucent 5620 Service Aware Manager

91 9500 MPR/9500 MPRe policy and service management MPR/9500 MPRe QoS policies MPR service management and service tunnels MPR VLAN service management MPR VLL service management Alcatel-Lucent 5620 Service Aware Manager

92 Alcatel-Lucent 5620 Service Aware Manager

93 MPR/9500 MPRe QoS policies MPR/9500 MPRe QoS policies overview Workflow to configure 9500 MPR/9500 MPRe QoS policies MPR/9500 MPRe QoS policies procedures 8-3 Alcatel-Lucent 5620 Service Aware Manager 8-1

94 MPR/9500 MPRe QoS policies 12.0 R7 December HE AAAG TQZZA Edition MPR/9500 MPRe QoS policies overview QoS policies define how network traffic is shaped and queued on one or more 9500 MPR and 9500 MPRe devices. You can use the to create the following 9500 MPR/9500 MPRe-specific QoS policies to define how network traffic is shaped and queued and to regulate data throughput on 9500 MPR and 9500 MPRe device ports: 9500 ATM QoS policies 9500 NE QoS policies 9500 Radio interface queue map policies 9500 ATM QoS policies 9500 ATM QoS policies define the ATM traffic descriptors, service category, policing, and marking behavior for network traffic that traverse 9500 MPR/9500 MPRe device ports. You can create up to two thousand 9500 ATM QoS policies per device. Note The number of ATM traffic descriptors that you can configure on a 9500 MPR is 1536, which is twice the number of configurable VPs multiplied by the number of ASAP cards that can be hosted ( ) NE QoS policies 9500 NE QoS policies define the QoS classification used for network traffic that traverse 9500 MPR/9500 MPRe device ports and to apply the 9500 Radio Interface Queue Map policy Radio Interface Queue Map policies 9500 Radio Interface Queue Map policies specify the queue size and queue delay for all queues for the radio interface that connect to 9500 MPR/9500 MPRe ports. This policy is applied when the 9500 NE QoS policy is configured. The following variants are supported for this policy type: ODU MPT-HL MPT-HC/MPT-MC MPT-HLS (9500 MPR version 5.1 and higher) MPT-HLC (9500 MPR version 5.1 and higher) MPT-HQAM (9500 MPR version 5.2 and higher) 8-2 Alcatel-Lucent 5620 Service Aware Manager

95 MPR/9500 MPRe QoS policies 8.2 Workflow to configure 9500 MPR/9500 MPRe QoS policies 1 Review the Policies overview chapter in the User Guide for information about policy management and for the workflow to create and distribute policies. 2 Review the QoS policies chapter in the User Guide for information about how to create and distribute QoS policies. 3 Create the following QoS device-specific policies as required: a 9500 MPR ATM QoS policy; see Procedure 8-1. b 9500 Radio Interface Queue Map policy; see Procedure 8-2. c 9500 NE QoS policies; see Procedure MPR/9500 MPRe QoS policies procedures This section contains procedures relating to the configuration of QoS policies for 9500 MPR and 9500 MPRe devices. Procedure 8-1 To configure and distribute a 9500 MPR ATM QoS policy 1 Choose Policies QoS 9500 MPR QoS 9500 ATM QoS from the main menu. The 9500 ATM QoS Policies form opens. 2 Perform one of the following: a b Configure the Policy scope parameter to Global. Configure the Policy scope parameter to Local. i ii iii Configure the Local Node IP Address parameter, if required. Click on the Select button and choose a device. Click on the OK button. 3 Click on the Create button. The 9500 ATM QoS Policy, Global Policy (Create) form opens with the General tab displayed. 4 Configure the parameters: Auto-Assign ID Displayed Name 5 Click on the QoS tab. Alcatel-Lucent 5620 Service Aware Manager 8-3

96 MPR/9500 MPRe QoS policies 12.0 R7 December HE AAAG TQZZA Edition 01 6 Configure the parameters: Service Category Policing PCR (cells/second) CDVT (microseconds) MDCR (cells/second) 7 Click on the OK button to save the policy. The ATM QoS Policy (Create) form closes and the 9500 ATM QoS Policies form reappears. 8 Click on the Search button to display the created policy or policies. 9 To distribute the 9500 ATM QoS policy, see the Policies overview chapter in the User Guide. Procedure 8-2 To configure and distribute a 9500 Radio Interface Queue Map policy When configuring a 9500 Radio Interface Queue Map policy, the following QoS variants are supported: ODU, MPT-HL, MPT-HC/MPT-MC. 1 Choose Policies QoS 9500 MPR QoS 9500 Radio Interface Queue Map from the main menu. The 9500 Radio Interface Map Policies form opens. 2 Perform one of the following: a b Configure the Policy scope parameter to Global. Configure the Policy scope parameter to Local. i ii iii Configure the Local Node IP Address parameter, if required. Click on the Select button and choose a device. Click on the OK button. 3 Click on the Create button. The 9500 Radio Interface Queue Map Global Policy (Create) form opens with the General tab displayed. 4 Configure the parameters: Auto-Assign ID ID Description 5 Click on the Radio Interface Queue Map tab. 6 Click on the Create button. The 9500 Radio Interface Queue Map Global Policy (Create) form opens. 8-4 Alcatel-Lucent 5620 Service Aware Manager

97 MPR/9500 MPRe QoS policies 7 Configure the parameters in the Radio Interface and Queue Size Settings panels: Card ID Port ID Snmp Port ID Status Reset all Queues Queue 1 Size Queue 2 Size Queue 3 Size Queue 4 Size Queue 5 Size Note You cannot configure the queue size parameters when the Reset all Queues parameter is selected. 8 Click on the OK button. 9 Click on the Yes button. The 9500 Radio Interface Queue Map Global Policy (Create) form closes. 10 Click on the Search button on the 9500 Radio Interface Map Policies form to display the created policy or policies. 11 To distribute the 9500 Radio Interface Map policy, see the Policies overview chapter in the User Guide. Procedure 8-3 To configure and distribute a 9500 NE QoS policy 1 Choose Policies QoS 9500 MPR QoS 9500 NE QoS from the main menu. The 9500 NE QoS Policies form opens. 2 Perform one of the following: a b Configure the Policy scope parameter to Global. Configure the Policy scope parameter to Local. i ii iii Configure the Local Node IP Address parameter, if required. Click on the Select button and choose a device. Click on the OK button. 3 Click on the Create button. The 9500 NE QOS Global Policy (Create) form opens with the General tab displayed. 4 Configure the parameters: Auto-Assign ID ID QoS Classification Description Alcatel-Lucent 5620 Service Aware Manager 8-5

98 MPR/9500 MPRe QoS policies 12.0 R7 December HE AAAG TQZZA Edition 01 The QoS Classification parameter default setting is Disabled. If you configure the QoS Classification parameter to 802.1p, the Dot1p tab appears. If you configure the QoS Classification parameter to DiffServ, the DSCP tab appears. 5 Click on the QueueMap policy tab to associate a 9500 Radio Interface Queue Map Policy. i ii Click on the Select button. The Select 9500 Radio Interface Queue Map Policy form opens. Choose a policy and click on the OK button. The 9500 NE QoS Global Policy (Create) form reappears. 6 Click on the Apply button. The 9500 NE QoS Global Policy (Create) form closes and the 9500 NE QOS Global Policy (Edit) form opens. 7 Optionally click on the TMN VLAN tab if you want to configure the DSCP value for the TMN in-band interfaces, otherwise go to step 8. Configure the following parameters for both TMN Inband interfaces: Enable In-band TMN VLAN ID (2-4080) DSCP 8 Click on the Global Queue Setting tab. 9 Choose a Queue number and click on the Properties button. The RadioQ, Global Policy (Edit) form opens. 10 Configure the parameters: Queue Number Algorithm Weight 11 Click on the OK button. The RadioQ, Global Policy (Edit) form closes. 12 Click on the OK button. A dialog box appears. 13 Click on the Yes button. 14 Click on the Search button on the 9500 NE QoS Policies form to display the created policy or policies. 15 To distribute the 9500 NE QoS policy, see the Policies overview chapter in the User Guide. 8-6 Alcatel-Lucent 5620 Service Aware Manager

99 MPR service management and service tunnels MPR service management overview MPR service tunnel overview Ethernet (G.8032) rings Configuring service tunnels on 9500 MPR devices Workflow to configure a composite service with VLAN service on the 9500 MPR and VPLS on the 7210 SAS 9-18 Alcatel-Lucent 5620 Service Aware Manager 9-1

100 MPR service management and service tunnels MPR service management overview The supports the configuration of VLANs, VLLs, and composite services on 9500 MPR devices. A 9500 MPR service with a VLAN path is created by configuring sites and access interfaces. The creates cross-connects between the physical ports on all 9500 MPRs along the VLAN path. These paths with cross-connects are called VLAN path instances. VLAN path instances are specific to a service, and each VLAN service has its own underlying VLAN path instance. A VLAN path can have multiple VLAN path instances. The VLAN path instance and all of the cross-connects on the service can be viewed along with other service properties. All 9500 MPR services use the default customer and are identified by a VLAN ID assigned at each inflow interface and a service ID. The service ID and VLAN ID have different values.the VLAN ID can be automatically assigned by the or assigned by the user. When the assigns the VLAN ID, the ID is based on the VLAN group that the endpoint 9500 MPR belongs to. Supported service types You can configure the following service type on 9500 MPR devices: P2P or P2MP (dot1q) VLAN services; see Procedure 10-3 P2P or P2MP (dot1ad) VLAN services; see Procedure 10-4 VLL services; see chapter 11: Apipe (ETSI) Cpipe (ANSI and ETSI) Composite services; see the Composite service management chapter in the User Guide Note 1 P2P VLAN services are for users who need to restrict a VLAN service to two sites. Therefore, adding sites to the P2P VLAN service is restricted. Note 2 P2MP VLAN services are for users who need to have a VLAN service with two or more sites. Note 3 To convert P2P VLAN services to P2MP VLAN services, you must unmanage the service using the Unmanage MPR 9500 Services button on the Manage Services form. Reactivate the service by clicking on the Discover MPR 9500 Services button. 9-2 Alcatel-Lucent 5620 Service Aware Manager

101 MPR service management and service tunnels Service-in-service automatic discovery The supports automatic discovery for service-in-service associations created with the 9500 MPR. Service-in-service refers to a transport service that carries services for network routers. Automatic discovery allows the to automatically associate a transport service with a service tunnel when a physical link is created between the 9500 MPR and a non-mpr NE. Service faults generated on either of the associated services become cross-correlated in the. Note 1 Service-in-service automatic discovery will not overwrite a service that is already associated with a service tunnel. Users can, however, manually overwrite an automatic association with another service. Only one service can be associated with a service tunnel. See the Service tunnels chapter in the User Guide for more information about associating a service to a service tunnel. Note 2 If the physical link between the 9500 MPR and the network router is removed, the automatically disassociates the service from the service tunnel. Switching between in-service radio links and standby radio links You can switch between an in-service protected radio link and a standby protected radio link during a maintenance window, if required. See Procedure 6-6 for more information. In-service protected radio links are represented as green links on the Physical topology map; standby radio links are shown as blue links. The status of a 9500 MPR service, spanning over any protected link, does not depend on the status of the link. The status of the service depends on the Radio Direction Operative Status. See Table 9-1 for more information about the service status. Table MPR service status Protection Type Main switching criteria/ command Spare switching criteria/ command Main status Spare status Radio Direction Operative Status (1) EPS Auto (Equipment Failure) None Standby Active Up None Auto (Equipment Failure) Auto (Equipment Failure) Auto (Equipment Failure) Active Standby Up Active/Standby Standby/Active Down Forced Switch None Standby Active Up Forced Switch Auto (Equipment Failure) Standby Active Down None Lockout Active Standby Up Auto (Equipment Failure) Lockout Active Standby Down Manual Switch None Standby Active Up None Manual Switch Active Standby Up (1 of 2) Alcatel-Lucent 5620 Service Aware Manager 9-3

102 MPR service management and service tunnels Protection Type Main switching criteria/ command Spare switching criteria/ command Main status Spare status Radio Direction Operative Status (1) TPS Auto (Equipment Failure) None Standby Active Up None Auto (Equipment Failure) Auto (Equipment Failure) Auto (Equipment Failure) Active Standby Up Active/Standby Standby/Active Down Forced Switch None Standby Active Up Forced Switch Auto (Equipment Failure) Standby Active Down None Lockout Active Standby Up Auto (Equipment Failure) Lockout Active Standby Down Manual Switch None Standby Active Up None Manual Switch Active Standby Up RPS Auto (Signal Fail/HBER) Auto (EW) Standby Active Up Auto (Signal Fail) Auto (HBER) Standby Active Errors Auto (Signal Fail) Auto (Signal Fail) Active/Standby Standby/Active Down None Auto (EW) Auto (Signal Fail/HBER/EW) Auto (Signal Fail/HBER) Active Standby Up Active Standby Up Auto (HBER) Auto (Signal Fail) Active Standby Errors Auto (EW) Auto (EW) Active/Standby Standby/Active Up Auto (HBER) Auto (HBER) Active/Standby Standby/Active Errors Forced Switch None Standby Active Up Forced Switch Auto (Signal Fail/HBER/EW) Standby Active Down None Lockout Active Standby Up Auto (Signal Fail/HBER/EW) Lockout Active Standby Down Manual Switch None Standby Active Up None Manual Switch Active Standby Up (2 of 2) Note (1) If the radio direction operative status is Up, the services are not affected. If the radio direction operative status is down, the services are affected. The traffic status is Rx operative Up, if the status is Up for all the protection types (EPS and RPS). The traffic status is Tx operative Up, if the status is Up for all the protection types (EPS and TPS). 9-4 Alcatel-Lucent 5620 Service Aware Manager

103 MPR service management and service tunnels Complete transport service The complete transport service action can be performed for: hop-based VLAN service hop-based Cpipe service ring-based Cpipe service The complete transport service action is performed when: the fails to establish one or more cross-connections of the intermediate and terminating nodes, during or after a hop-based VLL and VLAN service configuration one or more cross-connects on the intermediate nodes are deleted from NEtO. The action is performed for hop and ring based VLL Cpipe services. The MAC address deployments for the missing cross-connects are based on the algorithm. The complete transport service action cannot be performed when the topology is changed. See Procedure 11-5 for more information about configuring the complete transport service function MPR services support Table 9-2 summarizes the hop-based services that the 9500 MPR supports. Table 9-2 Summary of 9500 MPR hop-based services support Profile type Node profile type VLAN path type VLAN path creation type Extension of VLAN path Terminates on radio NEtO service interworking Service Discovery Initial release Hop-based services related to radio ports Cpipe TDM2TDM TDM2ETH TDM2TDMoETH SDH2SDH P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 8.0 R5 Apipe ATM2ATM ATM2ETH P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 8.0 R5 VLAN Dot1Q Dot1AD P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 8.0 R5 VLAN Dot1Q Dot1AD P2MP (hop-based) Auto (point to multipoint) Yes No Limited Discover MPR 9500 Services button from 10.0 R5 or later 10.0 R3 Epipe (1) (2) TDM2ETH P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 8.0 R5 (1 of 3) Alcatel-Lucent 5620 Service Aware Manager 9-5

104 MPR service management and service tunnels Profile type Node profile type VLAN path type VLAN path creation type Extension of VLAN path Terminates on radio NEtO service interworking Service Discovery Initial release Hop-based services related to L1 LAGS Cpipe TDM2TDM TDM2ETH TDM2TDMoETH P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 10.0 R3 VLAN Dot1Q Dot1AD P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 10.0 R3 VLAN Dot1Q Dot1AD P2MP (hop-based) Auto (point to multipoint) Yes No Limited Discover MPR 9500 Services button from 10.0 R5 or later 10.0 R3 Epipe (1) (2) TDM2ETH P2MP (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 10.0 R3 Hop-based services related to L2 LAGs Cpipe TDM2TDM TDM2ETH TDM2TDMoETH SDH2SDH (L2 on MPT HC) P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 9.0 R5 Apipe (L2 on MPT HC) ATM2ATM ATM2ETH P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 9.0 R5 VLAN Dot1Q Dot1AD P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 9.0 R5 VLAN Dot1Q Dot1AD P2MP (hop-based) Auto (point to multipoint) Yes No Limited Discover MPR 9500 Services button from 10.0R5 or later 9.0 R5 Epipe (1) (2) TDM2ETH P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 9.0 R5 Hop-based services related to Ethernet LAGs Cpipe TDM2ETH TDM2TDMoETH P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 9.0 R5 Apipe ATM2ATM ATM2ETH P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 9.0 R5 (2 of 3) 9-6 Alcatel-Lucent 5620 Service Aware Manager

105 MPR service management and service tunnels Profile type Node profile type VLAN path type VLAN path creation type Extension of VLAN path Terminates on radio NEtO service interworking Service Discovery Initial release VLAN Dot1Q Dot1AD P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 9.0 R5 VLAN Dot1Q Dot1AD P2MP (hop-based) Auto (point to multipoint) Yes No Limited Discover MPR 9500 Services button from 10.0 R5 or later 10.0 R3 Hop-based services related to Ethernet links Cpipe TDM2ETH TDM2TDMoETH P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 8.0 R5 Apipe ATM2ATM ATM2ETH P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 8.0 R5 VLAN Dot1Q Dot1AD P2P (hop-based) Manual Auto P2P No No Limited Discover MPR 9500 Services button from 10.0 R5 or later 8.0 R5 VLAN Dot1Q Dot1AD P2MP (hop-based) Auto (point to multipoint) Yes No Limited Discover MPR 9500 Services button from 10.0 R5 or later 10.0 R3 (3 of 3) Notes (1) Deprecated from the in Release 11.0R1. (2) Only supported on ANSI nodes MPR and 9500 MPRe service provisioning considerations and constraints The following considerations and constraints apply to Tables 9-2 and 9-3 when provisioning services on a 9500 MPR or 9500 MPRe. You cannot convert P2P VLAN paths to P2MP VLAN path and vice versa. Services and VLAN paths are only supported on the MSS-x shelf. You cannot configure the radio-end of the service using the. NEtO services support is limited to the scenarios described in the release description. VLAN path creation is limited to one radio/fiber ring. When configuring services with the that are cross-connected, see the node documentation. Complete transport service feature support is limited to only services provisioned from the. Alcatel-Lucent does not recommend provisioning services in tandem with the NEtO. Adjacent Ethernet links are not supported for VLL services. Alcatel-Lucent 5620 Service Aware Manager 9-7

106 MPR service management and service tunnels The supports the TDM2TDMoETH service profile using the TDM2TDM service profile for VLL services over Ethernet links. The creation of 9500 MPR services across different VLAN groups is not supported. VLAN groups are not mandatory for VLL services; if VLL services are not added to a VLAN group, VLAN space management is not supported. The operational state of VLAN services over rings does not consider the state of the working or protected ring path; the operational state service is calculated based on the network and access port state. The conversion of ring path to tail-based ring path is not supported The discovery of VLAN paths and services by the is based on the service components deployed on the nodes. The MAC address for services involving the TDM2TDMoETH service profile is automatically calculated and populated based on unicast or multicast. Manual configuration is not supported. You can discover ERPS/Fiber ring and tail-based services using the Discover MPR 9500 Services button on the Manage Services form for Release 11.0R3 or later. You can only discover VLAN services with the if the nodes are part of a VLAN group. If the VLAN group or VLAN path are configured with ERPS ring and tails using the, hop-based VLAN and VLL service discovery is restricted for ERPS with tail nodes. Any new VLAN services discovered by the will be associated with a P2MP VLAN path, however, existing VLAN services using P2P are untouched. If a radio port that is connected to a 9500 MPR is added as access in a hop-based VLAN service, the does not list the radio port as access upon service discovery. If a radio port that is connected to 9500 MPRe is added as access in a hop-based VLAN service, the lists the radio port as access upon service discovery. If a physical link exists between an Ethernet port and a GNE, the Ethernet port cannot be used as an access or termination port for a hop based VLAN service. If the VLAN paths are associated with VLL services, two paths P2P for VLL and P2M for VLAN are discovered. The 9500 MPR VLAN service displays the Admin State parameter as Up in the service topology map even when the requirement of having minimum of two access interfaces is not met. The does not validate whether inflow is present on the node or whether the same TDM channel is used for Cpipe L2 access, which could cause inconsistencies. The does not validate unsupported node cross-connect deployment, which could cause inconsistencies. Cpipe single L2 access is not supported. A Cpipe service must be created with both L2 access endpoints. Hop-based Cpipe services do not support radio termination. However, you can configure or discover a hop-based Cpipe service, in which one endpoint is an E1 port and the other is a radio port connected to an MSS-1c GNE or MPRe. The supports the creation of a VLAN service only when all of the nodes are in dot1q or dot1ad mode. VLAN services across nodes with mixed dot1q or dot1ad modes are not supported. 9-8 Alcatel-Lucent 5620 Service Aware Manager

107 MPR service management and service tunnels Service creation/discovery spanning across two or more rings is not supported except in the case of fiber microwave daisy chain, where the creation/discovery of VLAN service is allowed as tail(s)-based services. Radio termination is not supported for ring node for VLL/VLAN service creation/discovery. The tail termination can only be one site in the case of VLL (Cpipe service) for ring and tail-based service. Complete transport service action is not supported for ring-based services. Tail termination with LAG is not supported. Alarms are not generated for the VLL and VLAN services when the node reboots MPR service tunnel overview A service tunnel is an entity used to unidirectionally direct traffic from one device to another device. The service tunnel is provisioned to use a specific encapsulation method, such as GRE or MPLS, and the services are then mapped to the service tunnel. The 9500 MPR devices can use the following service tunnel types: Ethernet radio ring (G.8032): Discovery adds the Ethernet radio ring that the Ethernet Element is a member of. Mobile backhaul (applicable to 9500 MPR and 7705 SAR on MPLS-based services running over a VLAN): Discovery adds MPR VLL services that are associated with an SDP tunnel or are traversing through network interfaces that are being used by an L2/L3 VPN through any static or dynamic LSPs that are bound to SDPs on the service. See the Service tunnels chapter in the User Guide for the complete list of supported objects that service tunnels can be configured for, and for more service tunnel information MPR service tunnel (ERPS) support You can configure the 9500 MPR using an ERPS topology to create a collection of Ethernet ring nodes to form a closed physical loop. Between two and sixteen Ethernet ring nodes are supported per ERPS topology. The 9500 MPR ERPS support includes tail nodes that connect to ERPS ring nodes. Multiple tail node configurations are supported by the. Table 9-3 provides a summary of the ERPS service types that are supported on the 9500 MPR. See the 9500 MPR and 9500 MPRe service provisioning considerations and constraints subsection in this chapter. See the Service tunnels chapter in the User Guide for information about Ethernet (G.8032) rings and the 9500 MPR ERPS tail node support, and the service types supported. See Procedure 9-1 for information about how to create an Ethernet radio ring element on a 9500 MPR. Alcatel-Lucent 5620 Service Aware Manager 9-9

108 MPR service management and service tunnels Table 9-3 Summary of 9500 MPR ERPS services support Profile type Node profile type VLAN path type VLAN path creation type Extension of VLAN path Terminates on radio NEtO service interworking Service Discovery Initial release ERPS services - without tail (Radio Ring type) Cpipe TDM2TDM TDM2ETH Ring based with tail Manual No No None On adding ring elements to ring 9.0 R7 VLAN Dot1Q Ring based Manual Yes Yes None On adding ring elements to ring 9.0 R7 ERPS services - without tail (Fiber Microwave type) Cpipe TDM2TDM TDM2ETH TDM2TDMoETH Ring based Manual No No None On adding ring elements to ring 10.0 R7 VLAN Dot1Q Ring based Manual No No None On adding ring elements to ring 10.0 R7 ERPS services - Ring tail based (Radio Ring type) Cpipe TDM2TDM TDM2ETH TDM2TDMoETH Ring based with tail Manual No Yes None On adding ring elements to ring 10.0 R3 VLAN Dot1Q Ring based with tail multipoint Manual Yes Yes None On adding ring elements to ring 10.0 R3 ERPS services - Ring tail based (L1 LAG as tail type) Cpipe TDM2TDM TDM2ETH TDM2TDMoETH Ring based with tail Manual No Yes None On adding ring elements to ring 10.0 R3 VLAN Dot1Q Ring based with tail multipoint Manual Yes Yes None On adding ring elements to ring 10.0 R3 ERPS services - Ring tail based (Ethernet link as tail type) Cpipe TDM2ETH Ring based with tail VLAN Dot1Q Ring based with tail multipoint Manual No Yes None On adding ring elements to ring Manual Yes Yes None On adding ring elements to ring 10.0 R R3 ERPS services - Ring tail based (Fiber Microwave as tail type) Cpipe TDM2TDM TDM2ETH TDM2TDMoETH Ring based with tail Manual No Yes None On adding ring elements to ring 10.0 R7 VLAN Dot1Q Ring based with tail multipoint Manual Yes Yes None On adding ring elements to ring 10.0 R Alcatel-Lucent 5620 Service Aware Manager

109 MPR service management and service tunnels 9.3 Ethernet (G.8032) rings Ethernet Ring Protection (ERP), as specified in ITU-T G.8032, is a protection mechanism for Ethernet ring topologies that provides a resilient Ethernet network. ERP provides sub-50 ms protection and recovery switching for Ethernet traffic in a ring topology while ensuring that loops are not formed at the Ethernet layer. G.8032v1 supports a single ring topology; G.8032v2 supports multiple rings/ladder topology. For more information about Ethernet (G.8032) rings, see the ITU website at ERP topology An ERP topology is a collection of Ethernet ring nodes that forms a closed physical loop. Between two and sixteen Ethernet ring nodes are supported per ERP topology. One ERP topology is supported per NE. Up to two ERP instances are supported per ERP topology. Ethernet ring links connect two adjacent Ethernet ring nodes participating in the same ERP topology. Loop avoidance in the ring is achieved by guaranteeing that at anytime, traffic may flow on all but one of the ring links. This link is called the ring protection link (RPL). One designated node, the RPL Owner (also referred to as the master node), is responsible to block traffic over the RPL MPR ERPS tail node support on Ethernet (G.8032) rings Previous releases of the had a limitation that all services could only begin and end on Ethernet (G.8032) rings on the 9500 MPR. The extends EPS support to include tail nodes that connect to ERPS ring nodes. You can configure several tail network configurations on the 9500 MPR including: a tail network of one or more MSS-4 or MSS-8 shelves attached to the ring to create, for example, a tree or linear chain a tail network of one 9500 MPRe attached to the ring to create an 9500 MPRe extension a head-end network of one or more MSS-4 or MSS-8 shelves Figures 9-1 and 9-2 show the service configurations for ERPS tail nodes on the 9500 MPR. Alcatel-Lucent 5620 Service Aware Manager 9-11

110 MPR service management and service tunnels Figure MPR ERPS tail node service configuration types (sample 1) IP/ MPLS TDM Eth ERPS Ring TDM Eth 7705 SAR MPLS Ring Tail TDM Composite service Figure MPR ERPS tail node service configuration types (sample 2) IP/ MPLS Eth ERPS Ring Eth TDM 7705 SAR MPLS TDM Integrated Tail MPR ERPS tail node service provisioning On 9500 MPR MSS-4 and MSS-8 shelves, you can provision any service on a tail node; for example, TDM-over-Ethernet using a hybrid path. The services can terminate on a ERPS ring node or on another tail node. For the service workflow, you must choose the hybrid paths/rings and the service endpoint delivery node. For the 9500 MPRe, a single hop is supported by allowing a service to terminate on a network radio port. The service terminates on the radio port as a network attachment with a remote node is the target. You can add a manual link for the 9500 MPRe on the map to provide a representation of the 9500 MPRe-to-MSS relationship on the ring. A one-hop 9500 MPRe tail node can also be used in a more traditional 9500 MPR network MPR ERPS fiber-microwave protection You can configure fiber-microwave protection for services that traverse 9500 MPR NEs, to protect a fiber link with a microwave link when you create the Ethernet radio ring element for a radio ring, fiber ring, or mixed ring configuration. See Procedure Alcatel-Lucent 5620 Service Aware Manager

111 MPR service management and service tunnels The fiber link can be a fiber connection between two 9500 MPR NEs or a wireline network connection between two 9500 MPR NEs, where the 9500 MPR access to that wireline network uses a fiber connection. Figure 9-3 Fiber-microwave protection on the 9500 MPR TDM Eth TMN Microwave Fiber TDM Eth TMN Microwave Wireline network Figure 9-4 Fiber-microwave protection - operation Microwave Fiber/Primary Microwave LOS Fiber/Primary X LOS Fiber/Primary When you create a VLAN service over a single point-to-multipoint VLAN path that traverses multiple ERPS ring and tail nodes, the verifies the presence of the second ring element and deploys the VLAN service appropriately on all nodes. No additional configuration is required to apply the fiber-microwave protection to the service. See section 10.2 for the workflow to create VLAN services on 9500 MPR devices. Alcatel-Lucent 5620 Service Aware Manager 9-13

112 MPR service management and service tunnels Figure 9-5 Fiber-microwave protection on tail nodes NODE Microwave Microwave TAIL_1 Fiber Fiber TAIL_ Supported ERP service types You can configure the following service types in an ERP (G.8032) topology using the on 9500 MPR/9500 MPRe devices: VLAN service VLL Cpipe service 9.4 Configuring service tunnels on 9500 MPR devices Use the following procedures to configure service tunnels for 9500 MPR devices. See the Service tunnels chapter in the User Guide for the generic procedures that apply to this device type. Procedure 9-1 To create an Ethernet radio ring element on a 9500 MPR You can use this procedure to create an Ethernet radio ring element for a radio ring, fiber ring, or mixed ring on the 9500 MPR. Ethernet radio ring elements are supported on the 9500 MPR, Release 3.1 or later devices. Note 1 The radio ring operation status is not correctly displayed when an NE that is part of a ring is not reachable. Note 2 The state cause of Provisioning Mismatch is not displayed for MEG ID/level mismatch parameter of the radio ring. Note 3 Ring operation state is not updated correctly when multiple radio links are down. Note 4 The Ring Down state cause is not displayed for 9500 MPR VLAN Services. Note 5 The Link Down state cause for 9500 MPR VLL and VLAN services is not displayed when a link in a ring is down Alcatel-Lucent 5620 Service Aware Manager

113 MPR service management and service tunnels Create the ERP topology 1 Right-click on a 9500 MPR NE object on the navigation tree, and select Properties from the contextual menu. The Network Element [Edit] form opens with the General tab displayed. 2 Click on the Radio Ring Component tab button. 3 Click on the Create button. The Radio Ring Component (Create) form opens. 4 Configure the Topology Name parameter. 5 Click on the Select button beside the East Port Name parameter. The Select East Port - Radio Ring Component - new Object form opens. 6 Choose a port for the east port and click on the OK button. 7 Click on the Select button beside the West Port Name parameter. The Select West Port - Radio Ring Component - new Object form opens. 8 Choose a port for the west port and click on the OK button. 9 Click on the OK button to save the changes. A warning message appears. 10 Click on the OK button to acknowledge the warning message and to close the Radio Ring Component new Object (Create) form. Note The Type field is updated automatically to Radio or Fiber based on the selected East Port and West Port. 11 Click on the OK button to save the changes. A confirmation message appears. 12 Click on the Yes button to proceed. The Network Element (Edit) form closes. 13 Repeat steps 1 to 12 for each 9500 MPR NE that you want to add to your ERSP topology. Create the radio ring representation 14 Choose Manage Service Tunnels from the main menu. The Manage Service Tunnels form opens. 15 Choose Radio Ring (Ethernet Ring) from the Tunnel (Service Tunnel Management) contextual menu. 16 Click on the Create button and choose Radio Ring from the contextual menu. The Radio Ring [Create] form opens with the General tab displayed. 17 Configure the parameters: Mgr ID Auto-Assign ID Name Description Hold Time Down Guard Time Alcatel-Lucent 5620 Service Aware Manager 9-15

114 MPR service management and service tunnels 18 Click on the Apply button to make the changes. The Radio Ring, new Object (Edit) form opens with the General tab displayed. Define the elements in the radio ring 19 Click on the Components tab. The Radio Ring and Ring Elements icons are displayed. 20 Right-click on the Ring Elements object on the navigation tree and choose one of the following from the contextual menu: a Create Ethernet Ring Element. The Select Network Elements form opens. Go to step 21. b Add Existing Element. Go to step Double-click on a network element. The Ethernet Ring Element (Create) form opens. 22 Configure the parameters: ID Auto-Assign ID Site ID Description Guard Time CCM Hold Time Down (deciseconds) Guard Time Ring Protection Link Type R-APS Vlan ID MEG Level 23 Click on the Select button beside the Topology Name parameter. The Select Radio Ring Topology - Ethernet Ring Element - new object form opens. 24 Select the appropriate ERP topology created in steps 1 to 12. The Ethernet Ring Element - new object (Create) form opens with the General tab displayed. 25 Click on the Path Endpoints tab. 26 Double-click on the path A endpoint. The Ethernet Ring Path Endpoint - (Create) form opens. 27 Configure the MEG ID parameter. 28 Click on the OK button to save the changes. A warning message appears. 29 Click on the OK button to acknowledge the warning message and to close the Ethernet Ring Path Endpoint - new object (Create) form. 30 Repeat steps 26 to 29 for path B endpoint. Note The MEG ID parameter for path B endpoint must be a different value than the one used for the path A endpoint. 31 Click on the OK button to save the change and close the Ethernet Ring Element new Object (Create) form Alcatel-Lucent 5620 Service Aware Manager

115 MPR service management and service tunnels Configure a ring protection link for the radio ring 32 As required, configure a ring protection link for the radio ring by performing the following: i ii iii iv v vi vii viii Select a site located under Ring Elements icon on the Radio Ring (Edit) form and choose Properties from the contextual menu. The Ethernet Ring Element (Edit) form opens with the General tab displayed. Set the Ring Protection Link Type parameter to Owner. Click on the Path Endpoints tab. Double-click on the endpoint that you want to delegate as the ring protection link. The Ethernet Ring Path Endpoint - Element - Node form opens with the General tab displayed. Set the Path Endpoint Type parameter to the Ring Protection Link End. Click on the OK button to save the changes and close the Ethernet Ring Path Endpoint - Element - Node form. The Ethernet Ring Element (Edit) form reappears. Click on the OK button to save the changes and close the Ethernet Ring Element (Edit) form. A confirmation window appears. Click on the Yes button to proceed. Add other ring elements as required to the radio ring 33 Repeat steps 19 to 31 to create additional new ring element to add to the radio ring. 34 As required, add existing ring elements to the radio ring by performing the following: i ii iii Right-click on the Ring Elements icon on the Radio Ring (Edit) form and choose Add Existing Element from the contextual menu. The Select Elements form opens. Click on the Search button to display a list of radio ring elements. Choose a radio ring element and click on the OK button. Turn up all the ring elements 35 As required, turn up the radio ring elements in your radio ring by performing the following: i ii Select all the sites located under Ring Elements icon on the Radio Ring (Edit) form and choose Turn Up from the contextual menu. A confirmation window appears. Click on the Yes button to proceed. Alcatel-Lucent 5620 Service Aware Manager 9-17

116 MPR service management and service tunnels Add the radio ring to a VLAN path 36 Perform Procedure 10-2 to create a VLAN path. Choose Ring Based as the VLAN path type to add the radio ring to the VLAN. Note When you add the radio ring to a VLAN path, you can optionally extend ERPS (G.8032) support to include tail nodes that connect to the ERPS ring nodes. Create a service on the ERPS topology 37 Perform one of the following to create a service for the 9500 MPR: a b Perform Procedure 10-3 to create a 9500 MPR (dot1q) VLAN service. Perform Procedure 11-2 to create a VLL Cpipe service. Note 1 For VLL services, terminating sites must be manually added to the service. For VLAN services, the sites are auto populated. Note 2 When you create a VLL or VLAN service for the 9500 MPR, select the Ring Based path type. Note 3 The allows you to discover fiber Ethernet rings created by the NEtO. 9.5 Workflow to configure a composite service with VLAN service on the 9500 MPR and VPLS on the 7210 SAS The following workflow describes the sequence of high-level tasks required to configure a composite service with VLAN service on a 9500 MPR device and VPLS on a 7210 SAS device. Note To create a VLAN service on a 9500 MPR node, configure the ports which are connected to the 7210 SAS node as a SAP in access mode otherwise these ports cannot be used in SCP. If all ring elements in a ring are not 9500 MPR, service discovery for VLAN services is not supported. On the physical topology map, the color yellow indicates a composite service in which SCP port is RPL blocked on 7210 SAS node. 1 Configure an Ethernet radio ring on a 9500 MPR device. See Procedure Configure Ethernet CFM MD, MEG, NE MEG, and MEP. See To configure an Ethernet CFM MD and subordinate objects associated with the MD in the User Guide. 3 Configure an Ethernet (G.8032) ring on the 7210 SAS device. See To create an Ethernet (G.8032) ring in the User Guide. 4 Configure a VPLS on 7210 SAS device. See To create a VPLS in the User Guide Alcatel-Lucent 5620 Service Aware Manager

117 MPR service management and service tunnels 5 Configure a VLAN service on a 9500 MPR device. See Procedure Configure a composite service between the services created in step 4 and step 5. See Composite service management procedures in the User Guide. Alcatel-Lucent 5620 Service Aware Manager 9-19

118 MPR service management and service tunnels 9-20 Alcatel-Lucent 5620 Service Aware Manager

119 MPR VLAN service management MPR VLAN service management overview Workflow to create VLAN services on 9500 MPR devices VLAN service management procedures for 9500 MPR devices 10-4 Alcatel-Lucent 5620 Service Aware Manager 10-1

120 MPR VLAN service management 12.0 R7 December HE AAAG TQZZA Edition MPR VLAN service management overview VLAN services provide the segmentation services traditionally provided by routers in LAN configurations. VLANs address issues such as scalability, security, and network management. Routers in VLAN topologies provide broadcast filtering, security, address summarization, and traffic flow management. See chapter 9 for service creation information for 9500 MPR devices. See the VLAN service management chapter in the User Guide for more information about VLAN service creation. Supported VLAN services types for 9500 MPR devices The supports the creation of the following VLAN service types for 9500 MPR devices: 9500 MPR (dot1ad) VLAN 9500 MPR P2P (dot1q) VLAN 9500 MPR P2MP (dot1q) VLAN VLAN groups and paths The supports the configuration and provisioning of VLAN groups and paths that are used by 9500 MPR devices to configure VLAN and VLL services MPR VLAN groups You can use VLAN groups to: logically group 9500 MPR devices to represent a typical network topology. A 9500 MPR device cannot belong to more than one VLAN group. manage the VLAN IDs that are assigned to 9500 MPR VLAN group members Note When you create a 9500 MPR service, it can only be configured between 9500 MPRs that belong to the same VLAN group. See Procedure 10-1 for more information about creating VLAN groups Alcatel-Lucent 5620 Service Aware Manager

121 MPR VLAN service management 9500 MPR VLAN paths A VLAN path is a bidirectional service provision path that is used to support alarm correlation and turn up radio backhaul services on 9500 MPR devices. VLAN paths use a tree topology. The paths can span NEs that are connected by both radio links and physical links. You can configure a VLAN path as follows: Ring based An ERPS topology is a collection of Ethernet ring nodes that form a closed physical loop. Each Ethernet ring node is connected to two adjacent Ethernet ring nodes via a duplex communications facility. An Ethernet ring can contain from 2 to 16 Ethernet ring nodes. Hop based Users specify the number of hops from a source 9500 MPR to a destination 9500 MPR. Each hop in the path is a 9500 MPR that belongs to the same VLAN group.the following hop-based VLAN path variants are supported. Auto A user defines the head end of the VLAN path, the hops the VLAN path takes, and optionally, the bandwidth requirements, and whether the shortest path should be used. The determines the appropriate available route for the VLAN path. Manual A user defines the source 9500 MPR, the hops and links the VLAN path takes, and optionally, the bandwidth requirements. Point 2 Point A user defines the source and destination 9500 MPR, the number of allowed hops and, optionally, the bandwidth requirements, and whether the shortest path should be used. See Procedure 10-2 for more information about creating VLAN paths Workflow to create VLAN services on 9500 MPR devices Configure VLAN services for subscribers connected to 9500 MPR devices; see the VLAN service management chapter in the User Guide for the generic procedures that apply to this device type. Also, configure the following device-specific VLAN service types and functions. 1 Remove any inconsistencies created due to MIB population failures that can occur during service creation on a 9500 MPR NE; see Procedure Create VLAN groups and add members to each group; see Procedure Create the VLAN paths that are required between the 9500 MPR group members. The VLAN path can be hop based or ring based. See Procedure Create one of the following VLAN service types: a 9500 MPR (dot1q) VLAN services; see Procedure b 9500 MPR (dot1ad) VLAN services; see Procedure Configure the VLAN endpoints for traffic storm control, VLAN rate limiting, or dot1q VLAN rate limiting if you need to monitor the input bandwidth; see Procedure Associate access interfaces (the physical ports to which end users connect, similar to SAPs) with the VLAN services. Use the L2 Interfaces tab on the VLAN properties form to associate VLAN services with the ports used by end users. See the VLAN service management chapter in the User Guide. Alcatel-Lucent 5620 Service Aware Manager 10-3

122 MPR VLAN service management 12.0 R7 December HE AAAG TQZZA Edition 01 7 Create a CoS rate limiter for 9500 MPR VLANs, if required; see Procedure Discover 9500 MPR VLAN services; see Procedure Perform the following, as required: a View the VLAN service operational status or view the service topology map associated with a VLAN service; see the User Guide. b Delete a VLAN group or group member; see Procedure c Delete a 9500 MPR VLAN path; see Procedure d Modify or delete a VLAN service; see the User Guide VLAN service management procedures for 9500 MPR devices Use the following procedures to perform VLAN service creation and management tasks for 9500 MPR devices. Procedure 10-1 To create a VLAN group 1 Choose Manage VLAN VLAN Groups from the main menu. The Manage VLAN Groups form opens. 2 Click on the Create button. The VLAN Group (Create) form opens with the General tab displayed. 3 Configure the parameters: Group Name Description Node Type Topology VLAN Space Management by SAM You can configure the VLAN Space Management by SAM parameter when the Node Type parameter is set to Click on the Apply button. 5 Click on the Group Members tab. 6 Click on the Create button. The Select Network Elements form opens and a list of available NEs appears. Only NE types specified by the Node Type parameter are displayed in the list. 7 Choose one or more NEs and click on the OK button. A dialog box appears. 8 Click on the OK button. The selected NEs are listed in the VLAN Group (Edit) form Alcatel-Lucent 5620 Service Aware Manager

123 MPR VLAN service management 9 If you need to apply a span of control to a group, other than the default, click on the Spans tab. Otherwise, go to step 10. i ii iii iv Click on the Add button. The Select Span(s) - VLan Group form opens with a list of available spans. Choose one or more spans of control to apply to the VLAN group. Click on the OK button. The Select Span(s) - VLan Group form closes and a dialog box appears. Click on the OK button. 10 Click on the OK button. A dialog box appears. 11 Click on the Yes button. The VLAN Group (Edit) form closes. 12 A list of VLAN groups appears in the Manage VLAN Groups form. 13 Close the Manage VLAN Groups form. Procedure 10-2 To create a 9500 MPR VLAN path Note 1 To create a ring-based VLAN path, you need a radio ring element; see Procedure 9-1. Note 2 When you create an Auto or P2P variant of a hop-based VLAN path, all 9500 MPR NEs that traverse the VLAN path must be part of the same VLAN group. For manually created VLAN paths, a VLAN group is not required. See Procedure 10-1 for information about creating VLAN groups. Note 3 You can also use this procedure to provision a VLAN path for a tail node. 1 Choose Manage VLAN Paths from the main menu. The Manage VLAN Paths form opens. 2 Click on the Create button. The Create VLAN Path step form opens with the Path Type step displayed. 3 Configure the Path Type parameter. 4 Click on the Next button. The Identification step appears. 5 Configure the parameters: Name Description Creation Type The Creation Type parameter appears when the Path Type parameter is set to Hop Based. Alcatel-Lucent 5620 Service Aware Manager 10-5

124 MPR VLAN service management 12.0 R7 December HE AAAG TQZZA Edition 01 6 Click on the Next button. For ring-based VLAN paths, the Select Ring step appears. For hop-based VLAN paths, the Specify Vlan Path Constraints step appears. 7 Perform one of the following: a If you set the Path Type parameter option to Ring Based, go to step 8. b If you set the Path Type parameter option to Hop Based, go to step Click on the Select button. The Select Ring - VLAN Path form opens. 9 Choose a radio ring from the list and click on the OK button. The Select Ring - VLAN Path form closes and the ID of the selected Radio Ring appears in the Mgr ID parameter. 10 Configure the following parameters if a tail node needs to be attached to the ring element; otherwise, go to step 48. Has Tail Is Point to Multipoint Configure the Has Tail parameter if you need standard VLAN paths for the tail node. Configure the Is Point to Multipoint parameter if you need dot1q VLAN paths for the tail node. 11 Click on the Next button. The Define the Provisioned Path step opens. 12 Click on the Insert Hop button. The Hop for New Vlan Path [Create] form opens. 13 Click on the Select button to add a network element to the VLAN path. The Select a Network Element - New VLAN Path form opens. 14 Choose a Network Element and click on the OK button. The Hop for New Vlan Path [Create] form reappears. 15 Click on the Select button to add a radio link to the VLAN path. The Select Links - New VLAN Path form appears. 16 Choose a radio link and click on the OK button. The Hop for New Vlan Path [Create] form closes and the Define the Provisioned Path step reappears. 17 Perform one of the following: a b Repeat steps 12 to 16 to add another tail node to the ring element. Click on the Finish button and close button to complete the provisioning of the VLAN path on a tail node. 18 Perform one of the following: a b Set the Creation Type parameter option to Manual. The Specify Vlan Path Constraints step opens. Go to step 19. Set the Creation Type parameter option to Auto or Point 2 Point. The Specify Vlan Path Constraints step opens. Go to step Configure the Minimum Bandwidth (kbps) parameter. 20 Click on the Next button. The Define Source Site step appears Alcatel-Lucent 5620 Service Aware Manager

125 MPR VLAN service management 21 Click on the Select button. The Select a Network Element - Define Source Site form opens. Choose a 9500 MPR from the list and click on the OK button. The Select a Network Element - Define Source Site form closes and the IP address of the selected 9500 MPR appears in the Starting Network Element parameter. 22 Click on the Next button. The Define the Provisioned Path step appears. 23 Click on the Insert Hop button to insert a VLAN path hop. The Hop for New VLAN Path (Create) form opens. 24 Click on the Select Network Element button. The Select a Network Element - New VLAN Path form opens. 25 Choose a 9500 MPR from the list and click on the OK button. The New VLAN Path form closes and the IP address of the NE appears in the Network Element parameter. 26 Click on the Select Link button. The Select Links - New Vlan Path form opens. 27 Choose a link from the list and click on the OK button. 28 If you need to add another hop, click on the Apply button and repeat steps 23 to 27. Click on the OK button after you add the required hops. 29 Close the Hop for New VLAN Path (Create) form. Go to step Configure the parameters: Max Sites Minimum Bandwidth (kbps) Select Shortest Path 31 Perform one of the following: a b If you set the Creation Type parameter option in step 5 to Auto, go to step 32. If you set the Creation Type parameter option in step 5 to Point 2 Point, go to step Click on the Next button. The Specify if the Vlan Path is a Point to Multipoint step appears. 33 Configure the Is Point to Multipoint parameter. 34 Click on the Next button. The Define Head step appears. 35 Click on the Select button. The Select a Network Element - Define Head End form opens. Choose a 9500 MPR from the list and click on the OK button. The Select a Network Element - Define Head End form closes and the IP address of the selected 9500 MPR appears in the Head End parameter. 36 Click on the Next button. The Possible Vlan Paths step appears. 37 Choose one or more possible VLAN paths and click on the OK button. Go to Step Click on the Next button. The Define Source Site step appears. Alcatel-Lucent 5620 Service Aware Manager 10-7

126 MPR VLAN service management 12.0 R7 December HE AAAG TQZZA Edition Perform one of the following: a b Enter the IP address of the starting VLAN path endpoint in the Starting Network Element parameter. Click on the Select button. The Select a Network Element - Define Source Site form opens. Choose a 9500 MPR from the list and click on the OK button. The Select a Network Element - Define Source Site form closes and the IP address of the selected 9500 MPR appears in the Starting Network Element parameter. 40 Click on the Next button. The Define Destination Site step appears. 41 Click on the Select button. The Select a Network Element - Define Destination Site form opens. Choose a 9500 MPR from the list and click on the OK button. The Select a Network Element - Define Destination Site form closes and the IP address of the selected 9500 MPR appears in the Destination Network Element parameter. 42 Click on the Next button. The Possible Vlan Paths step appears. 43 Click on the Insert Hop button to insert a VLAN path hop. The Hop for New VLAN Path (Create) form opens. 44 Click on the Select Network Element button. The Select a Network Element - New VLAN Path form opens. 45 Choose a 9500 MPR from the list and click on the OK button. The New VLAN Path form closes and the IP address of the NE appears in the Network Element parameter. 46 If you need to add another hop, click on the Apply button and repeat steps 44 and 45. Click on the OK button after you add all hops. 47 Close the Hop for New VLAN Path (Create) form. 48 Click on the Finish Button to save the VLAN path configuration. 49 Click on the Close button. The Create VLAN Path form closes. 50 Close the Manage VLAN Paths form. Procedure 10-3 To create a 9500 MPR (dot1q) VLAN service Perform the following procedures before creating a 9500 MPR (dot1q) VLAN service, as required: Create a customer profile; see the Customer configuration and service management chapter in the User Guide. Create a VLAN group; see Procedure Alcatel-Lucent 5620 Service Aware Manager

127 MPR VLAN service management Create a VLAN path if you need to assign a specific VLAN path to the 9500 MPR (dot1q) VLAN service; see Procedure Configure the VLAN endpoints for traffic storm control, VLAN rate limiting, or dot1q VLAN rate limiting if you need to monitor the input bandwidth; see Procedure Right-click on a 9500 MPR object in the navigation tree and choose Properties from the contextual menu. The Network Element (Edit) form opens with the General tab displayed. 2 Click on the System Settings tab and set the Bridge Type parameter to 802.1Q. 3 Close the Network Element (Edit) form. 4 Choose Create Service VLAN from the main menu. The VLAN Service (Create) form opens with the General tab displayed. 5 Click on the Select button to choose a customer to associate with the 9500 (dot1q) VLAN service. The Select Customer - VLAN Service form opens. 6 Choose a customer for the 9500 MPR (dot1q) VLAN service and click on the OK button. The Select Customer - VLAN Service form closes and the VLAN Service (Create) Service form reappears with the customer information displayed on the General tab. 7 Configure the parameters: Service ID Auto-Assign ID SVC Mgr Service ID Service Name Description Service Tier Service Priority Administrative State Current OLC State Revert OLC State The Service ID parameter is configurable when the Auto-Assign ID parameter is disabled. The SVC Mgr Service ID parameter is configurable when the Auto-Assign ID parameter is disabled. The Current OLC State and Revert OLC State parameters are configurable when you click on the Apply button on the VLAN Service (Create) form. 8 Click on the VLAN tab and set the Application parameter to 9500 VLAN. 9 Click on the Select button in the Group panel to choose a VLAN group to associate with the 9500 MPR (dot1q) VLAN service. The Select Group - VLAN Service form opens. 10 Choose a VLAN group and click on the OK button. The Select Group - VLAN Service form closes and the VLAN Service (Create) form reappears with the group information displayed. Alcatel-Lucent 5620 Service Aware Manager 10-9

128 MPR VLAN service management 12.0 R7 December HE AAAG TQZZA Edition Perform one of the following: a b Enable the Auto-Assign ID parameter. The chooses the VLAN ID when the Auto-Assign ID parameter is enabled. Disable the Auto-Assign ID parameter to configure the VLAN ID parameter. 12 Perform one of the following: a b Enable the Specify VLAN Path parameter. Disable the Specify VLAN Path parameter to specify a VLAN path by clicking on the Select button in the VLAN path panel. Go to step Configure the parameters: Path Type Point to Point VLAN The Point to Point VLAN parameter is configurable when the Path Type parameter is set to Hop Based. Note 1 To create a 9500 MPR VLAN service on an ERPS tail node, set the Path Type parameter to Ring Based. Note 2 The service created using Point to Point VLAN service is discovered as a standard VLAN service without the point-to-point option. Note 3 You cannot reconfigure the Point to Point VLAN parameter after you choose a VLAN path. To change the parameter, you need to delete the selected VLAN path. 14 Click on the Select button in the VLAN Path panel to choose a VLAN Path to associate with the 9500 MPR (dot1q) VLAN service. The Select VLAN Path - VLAN Service form opens. Note If you choose the Ring Based option for the Path Type parameter in step 13, only P2MP paths are listed. You cannot use a P2P path with a tail VLAN Path on a 9500 MPR Ring Based VLAN. 15 Choose a VLAN Path and click on the OK button. The Select VLAN Path - VLAN Service form closes and the VLAN Service (Create) form reappears with the group information displayed. Note The VLAN path may consist of a P2P, P2MP, or Has Tail VLAN path, and consecutive physical links, non-consecutive physical links, or radio links spanning NEs Alcatel-Lucent 5620 Service Aware Manager

129 MPR VLAN service management 16 In the navigation tree, right-click on VLAN Service and choose Create VLAN Site. The Select Network Elements - VLAN Service form opens. Note The service navigation tree is auto-populated with sites that correspond to the hops in the specified VLAN Path. 17 Choose a site and click on the OK button. The Select Network Elements - VLAN Service form closes and the VLAN Site (Create) form opens with the site information displayed on the General tab. 18 Configure the parameters: Description Administrative State Monitor Access Interface Operational State 19 Click on the OK button. The VLAN Site (Create) form closes and a dialog box appears. 20 Click on the OK button. The VLAN Service (Create) form reappears with the new site information displayed in the service navigation tree. Note During the creation of VLAN services, intermediate sites are automatically added to the service topology view. 21 In the navigation tree, click on the site with which you need to associate the new access interface; expand the entries for the site. 22 Right-click on L2 Access Interfaces and choose Create VLAN Access Interface. The VLAN Access Interface (Create) form opens with the General tab displayed. 23 Configure the parameters: Description Administrative State 24 Click on the Port tab. Alcatel-Lucent 5620 Service Aware Manager 10-11

130 MPR VLAN service management 12.0 R7 December HE AAAG TQZZA Edition Click on the Select button to choose a port for the VLAN access interface. The Select Terminating Port - VLAN Access Interface form opens. Note 1 The form lists Ethernet ports in access or hybrid mode and also radio ports. To choose an Ethernet port that is not listed, you must set the Mode parameter for the port to Access or Hybrid and click on the Search button. Note 2 For a hop-based VLAN service, you can add a radio port as an access interface. A network port that is used in a VLAN path cannot be added as an access interface. Note 3 For a ring-based VLAN service, you can add a radio port of a ring or tail node as an access interface. 26 Use the configurable filter and Search button to choose a port for the VLAN access interface, and click on the OK button. The Select Terminating Port - VLAN Access Interface form closes, and the VLAN Access Interface (Create) form displays the port information. 27 Click on the VLAN tab and configure the parameters: VLAN Tagging Provider Bridge Type S-VLAN TPID Priority of UNI 28 Click on the OK button. The VLAN Access Interface (Create) form closes, and a dialog box appears. 29 Click on the Apply button to save the changes. The VLAN Service (Create) form closes. Procedure 10-4 To create a 9500 MPR (dot1ad) VLAN service Perform the following procedures before you create a 9500 MPR (dot1ad) VLAN service. Create a customer profile; see the customer configuration and service management chapter in the User Guide. Create a VLAN group; see Procedure Create a VLAN path if you need to assign a specific VLAN path to the 9500 MPR (dot1ad) VLAN service; see Procedure Configure the VLAN endpoints for traffic storm control, VLAN rate limiting, or dot1ad VLAN rate limiting if you need to monitor the input bandwidth; see Procedure Right-click on a 9500 MPR in the navigation tree and choose Properties from the contextual menu. The 9500 MPR properties form opens with the General tab displayed. 2 Click on the System Settings tab and set the Bridge Type parameter to 802.1ad Alcatel-Lucent 5620 Service Aware Manager

131 MPR VLAN service management 3 Close the 9500 MPR properties form. 4 Right-click on the 9500 MPR Ethernet port and choose Properties from the contextual menu. The Physical Port (Edit) form opens with the General tab displayed. Note The provider bridge configuration parameters are available only on Ethernet ports. 5 Click on the Ethernet tab and configure the provider bridge configuration parameters: Provider Bridge Type S-VLAN TPID UNI Priority Untag C-VLAN Note 1 When the Provider Bridge Type parameter is set to NNI, the S-VLAN TPID parameter can be configured. Note 2 When the Provider Bridge Type parameter is set to UNI, UNI priority parameter can be configured. Note 3 When the Provider Bridge Type parameter is set to UNI (C-VLAN), the Untag C-VLAN check box appears. The Untag C-Vlan check box cannot be selected if the ingress mapping has no entry. 6 If you set the Provider Bridge Type parameter to UNI (C-Vlan Based) in step 5, perform the following to configure the C-VLAN/S-VLAN mapping. i ii Click on the Ingress Mapping tab and click on the Create button. The Ingress C-VLAN/S-VLAN Mapping (Create) form opens. Configure the parameters, as required: C Vlan ID SVlan Priority Inherited Remove C-Vlan ID Note 1 The value for the S Vlan ID parameter is set to 1 and cannot be configured. iii iv v vi Note 2 Only one of the ingress mapping entries can have the Remove C-Vlan ID check box selected. Click on the OK button. The Ingress C-VLAN/S-VLAN Mapping (Create) form closes and the Ingress Mapping tab and a dialog box appears. Click on the OK button. The new C-VLAN/S-VLAN mapping entry appears in the ingress mapping list. Click on the Apply button. A dialog box appears. Click on the Yes button. Alcatel-Lucent 5620 Service Aware Manager 10-13

132 MPR VLAN service management 12.0 R7 December HE AAAG TQZZA Edition 01 vii viii ix Click on the Egress Mapping tab. The C-VLAN/S-VLAN mapping entry appears in the egress mapping list. Choose the entry and click on the Properties button. The Egress C-VLAN/S-VLAN Mapping (Edit) form opens. Configure the C Vlan ID parameter. Note The value for the S Vlan ID parameter is set to 1 and cannot be configured. x Click on the OK button. The Egress C-VLAN/S-VLAN Mapping (Edit) form closes and the Egress Mapping tab reappears. 7 Click on the Apply button. A dialog box appears. 8 Click on the Yes button to apply the changes. 9 Choose Create Service VLAN from the main menu. The VLAN (Create) Service form opens with the General tab displayed. 10 Click on the Select button to choose a customer to associate with the 9500 MPR (dot1ad) VLAN service. The Select Customer - VLAN Service form opens. 11 Choose a customer for the 9500 MPR (dot1ad) VLAN service and click on the OK button. The Select Customer - VLAN Service form closes and the VLAN (Create) Service form reappears with the customer information displayed on the General tab. 12 Configure the parameters: Service ID Service ID SVC Mgr Service ID Service Name Description Service Tier Service Priority Administrative State The Service ID parameter is configurable when the Auto-Assign ID parameter is disabled. The SVC Mgr Service ID parameter is configurable when the Auto-Assign ID parameter is disabled. 13 Click on the VLAN tab and set the Application parameter to 9500 VLAN. 14 Click on the Select button in the Group panel to choose a VLAN group to associate with the 9500 MPR (dot1ad) VLAN service. The Select Group - VLAN Service form opens. 15 Choose a VLAN group and click on the OK button. The Select Group - VLAN Service form closes and the VLAN (Create) form reappears with the group information displayed Alcatel-Lucent 5620 Service Aware Manager

133 MPR VLAN service management 16 Perform one of the following steps. a b Enable the Auto-Assign ID parameter. The chooses the VLAN ID when the Auto-Assign ID parameter is enabled. Disable the Auto-Assign ID parameter to configure the VLAN ID parameter. 17 Perform one of the following steps. a b Enable the Specify VLAN Path parameter. Disable the Specify VLAN Path parameter to specify a VLAN path by clicking on the Select button in the VLAN path panel. Go to step Configure the parameters: Path Type Point to Point VLAN The Point to Point VLAN parameter is configurable when the Path Type parameter is set to Hop Based. Note 1 The service that is created using point-to-point VLAN service is discovered as a standard VLAN service without the point-to-point option. Note 2 You cannot reconfigure the Point to Point VLAN parameter after you choose a VLAN path. To change the parameter, you need to delete the selected VLAN path. Note 3 During the creation of VLAN services, intermediate sites are automatically added to the service topology view. 19 Click on the Select button in the VLAN Path panel to choose a VLAN Path to associate with the 9500 MPR (dot1ad) VLAN service. The Select VLAN Path - VLAN Service form opens. 20 Choose a VLAN Path and click on the OK button. The Select VLAN Path - VLAN Service form closes and the VLAN (Create) form reappears with the group information displayed. Note The VLAN Path may consist of the following: P2P P2MP Tail VLAN path consecutive physical links non-consecutive physical links radio links spanning NEs 21 Choose 802.1AD as the bridge type from the Bridge Type drop-down menu and click on the Apply button. The service is created and VLAN Path Instance appears in the navigation tree. Alcatel-Lucent 5620 Service Aware Manager 10-15

134 MPR VLAN service management 12.0 R7 December HE AAAG TQZZA Edition In the navigation tree, right-click on VLAN and choose Create VLAN Site. The Select Network Elements - VLAN form opens. Note The service navigation tree is auto-populated with sites that correspond to the hops in the specified VLAN path. 23 Choose a site and click on the OK button. The Select Network Elements - VLAN form closes and the Site (Create) form opens with the site information displayed on the General tab. 24 Configure the parameters: Description Administrative State Monitor Access Interface Operational State 25 Click on the OK button. The Site (Create) form closes and a dialog box appears. 26 Click on the OK button. The VLAN (Create) form reappears with the new site information displayed in the service navigation tree. 27 Click on the OK button to close the VLAN (Create) form. 28 In the navigation tree, click on the site with which you need to associate the new access interface; expand the entries for the site. 29 Right-click on L2 Access Interfaces and choose Create VLAN Access Interface. The VLAN Access Interface (Create) form opens with the General tab displayed. 30 Configure the parameters: Description Administrative State 31 Click on the Port tab. 32 Click on the Select button to choose a port for the VLAN access interface. The Select Terminating Port - VLAN Access Interface form opens. Note 1 The form lists Ethernet ports in access or hybrid mode and also radio ports. To choose an Ethernet port that is not listed, you must set the Mode parameter for the port to Access or Hybrid and click on the Search button. Note 2 For a hop-based VLAN service, you can add a radio port as an access interface. A network port that is used in a VLAN path cannot be added as an access interface. 33 Use the configurable filter and Search button to choose a port for the VLAN access interface, and click on the OK button. The Select Terminating Port - VLAN Access Interface form closes, and the VLAN Access Interface (Create) form displays the port information Alcatel-Lucent 5620 Service Aware Manager

135 MPR VLAN service management 34 Click on the VLAN tab and configure the parameters: VLAN Tagging Provider Bridge Type S-VLAN TPID Priority of UNI When the Provider Bridge Type is set to NNI, the UNI Priority parameter options are dimmed. When the Provider Bridge Type is set to UNI, the S-VLAN TPID parameter options are dimmed. 35 If you set the VLAN Tagging parameter to Untagged and the Provider Bridge Type parameter to UNI (C-Vlan Based) in step 34, perform the following steps to configure the C-VLAN/S-VLAN mapping. Note You can configure C-VLAN/S-VLAN mapping also for LAG and ring-based services. i ii Click on the Ingress Mapping tab and click on the Create button. The Ingress C-VLAN/S-VLAN Mapping (Create) form opens. Configure the parameters, as required: C Vlan ID SVlan Priority Inherited Remove C-Vlan ID Note Select the Remove C-Vlan ID check box for any one of the ingress mapping entries. iii iv v vi vii Click on the OK button. The Ingress C-VLAN/S-VLAN Mapping (Create) form closes. The new C-VLAN/S-VLAN mapping entry appears in the ingress mapping list upon clicking the Search button. Click on the Egress Mapping tab. The C-VLAN/S-VLAN mapping entry appears in the egress mapping list. Choose the entry and click on the Properties button. The Egress C-VLAN/S-VLAN Mapping (Edit) form opens. Configure the C Vlan ID parameter. Click on the OK button. The Egress C-VLAN/S-VLAN Mapping (Edit) form closes and the Egress Mapping tab reappears. 36 Click on the OK button. The VLAN Access Interface (Create) form closes, and a dialog box appears. Alcatel-Lucent 5620 Service Aware Manager 10-17

136 MPR VLAN service management 12.0 R7 December HE AAAG TQZZA Edition Click on the OK button. The VLAN - Service Name (Edit) form reappears with the new interface displayed in the service navigation tree under Access Interfaces for the specified site. 38 Click on the Apply button to complete the configuration. The provider bridge is configured. Procedure 10-5 To create a CoS rate limiter per VLAN on a 9500 MPR A CoS rate limiter per VLAN can be applied to each user Ethernet interface for the ingress direction. The rate limiter is applied to a tagged Ethernet flow. The combination of the values of one VLAN ID and one PCP identifies a specific VLAN Ethernet flow. 1 Choose Equipment from the navigation tree view selector. The navigation tree displays the Equipment view. 2 Choose Network NE Shelf Card Slot Port. 3 Right-click on the port object and choose Properties from the contextual menu. The Physical Port (Edit) form opens with the General tab displayed. 4 Click on the CoS Rate Limiter tab and click on the Create button. The CoS Rate Limiter (Create) form opens. 5 Click on the Select button and choose a Port Binding VLAN ID from the list. Click on the OK button. 6 Configure the parameters: PCP Ingress CIR (kbps) Ingress Max Burst (Kbytes) 7 Click on the OK button. A dialog box appears. 8 Click on the OK button. The CoS Rate Limiter (Create) form closes Alcatel-Lucent 5620 Service Aware Manager

137 MPR VLAN service management Procedure 10-6 To discover 9500 MPR services The 9500 MPR services are not discovered automatically during NE discovery. Perform this procedure after all 9500 MPR NEs are synchronized in the. Note 1 A prerequisite for discovering VLAN services on the 9500 MPR is that the nodes that are part of the VLAN service must be contained in a VLAN group. If any of the discovered nodes contain ring instances, they should be added to ring elements before using the hop or ring-based discovery button. Note 2 VLAN groups are not mandatory for VLL services; if VLL services are not added to a VLAN group, VLAN space management is not supported. If any of the discovered nodes contain ring instances, they should be added to ring elements before using the hop or ring-based option on the Discover MPR 9500 Services button. Note 3 For a ring-based service, the ring element must be added to the ring. See Procedure 10-1 for information about creating VLAN groups. See Procedure 9-1 for information about creating an Ethernet radio ring element. 1 Choose Manage Service Services from the main menu. The Manage Services form opens. 2 Click on the Discover MPR 9500 Services button and choose one of the following options: Hop Based Ring Based The Ring Based option discovers both VLL and VLAN services associated with the ring and tail. The Discover MPR 9500 Services form opens with the network groups in the list. 3 Choose a network group and click on the OK button. The Discover MPR 9500 Services form closes and the Manage Services form reappears. If you created network subgroups and the nodes are split over different subgroups, you must select all of the subgroups and click on the OK button to discover all of the services. 4 Click on the Search button. The discovered services appear in the Manage Services form. Note You can optionally exclude a 9500 MPR VLAN from management without having to unmanage the entire 9500 MPR device by clicking on the Unmanage MPR 9500 Services button. Service configurations are maintained in the database during this operational state. You can reactivate the VLAN services using the Discover MPR 9500 Services button on the Manage Services form. 5 Close the Manage Services form. Alcatel-Lucent 5620 Service Aware Manager 10-19

138 MPR VLAN service management 12.0 R7 December HE AAAG TQZZA Edition 01 Procedure 10-7 To delete a VLAN group or group member Note 1 You must delete all of the members from a group before you can delete the group. Note 2 A 9500 MPR group member cannot be deleted if it is part of a VLAN path. 1 Choose Manage VLAN VLAN Groups from the main menu. The Manage VLAN Groups form opens. 2 Apply a filter, or create and apply a filter, and click on the Search button. A list of VLAN groups appears. 3 Choose a VLAN group. 4 Click on the Properties button. The VLAN Groups (Edit) form opens with the General tab displayed. 5 Click on the Group Members tab. 6 If the group does not contain any members, go to step 9. Otherwise, go to step 7. 7 Choose one or more members of the VLAN group and click on the Delete button. A dialog box appears. 8 Click on the OK button to delete the group members. 9 Close the VLAN Groups (Edit) form. The Manage VLAN Groups form reappears. 10 Choose the VLAN group that you need to delete from the displayed list. 11 Click on the Delete button. A dialog box appears. 12 Click on the Yes button to delete the VLAN group. 13 Close the Manage VLAN Groups form Alcatel-Lucent 5620 Service Aware Manager

139 MPR VLAN service management Procedure 10-8 To delete a 9500 MPR VLAN path Note You cannot delete a VLAN path if the path is being used by a service. 1 Choose Manage VLAN Paths from the main menu. The Manage VLAN Paths form opens. 2 Apply a filter, or create and apply a filter, and click on the Search button. A list of VLAN paths appears. Note If VLAN paths are already in your network, the 9500 MPR NE that the path traverses is auto-discovered by the. The paths appear in the Manage VLAN Paths form with a name with the following syntax: Discovered-VLANPath-<IP address of the source 9500 MPR>-<IP address of the destination 9500 MPR. 3 Choose a VLAN path and click on the Delete button. The VLAN path and all of the associated hops are deleted. 4 Close the Manage VLAN Paths form. Alcatel-Lucent 5620 Service Aware Manager 10-21

140 MPR VLAN service management 12.0 R7 December HE AAAG TQZZA Edition Alcatel-Lucent 5620 Service Aware Manager

141 MPR VLL service management MPR VLL service management overview Workflow to create VLL services on 9500 MPR devices VLL service management procedures for 9500 MPR devices 11-3 Alcatel-Lucent 5620 Service Aware Manager 11-1

142 MPR VLL service management 12.0 R7 December HE AAAG TQZZA Edition MPR VLL service management overview The supports the provisioning of VLL services on 9500 MPR devices. A VLL service is an L2 point-to-point service that connects access interfaces. A VLL service is completely transparent to customer or subscriber data and to control protocols. Because of this transparency, the device performs no MAC learning in a VLL service. See the VLL service management chapter in the User Guide for detailed information about VLAN service creation. Supported VLL services types for 9500 MPR devices The supports the creation of the following VLL service types for 9500 MPR devices: 9500 MPR (ETSI only) VLL Apipe services 9500 MPR VLL Cpipe services 11.2 Workflow to create VLL services on 9500 MPR devices Configure VLL services for subscribers connected to 9500 MPR devices; see the VLL service management chapter in the User Guide for the generic procedures that apply to this device type. Also, configure the following device-specific VLL service types and functions: 1 Remove any inconsistencies created due to MIB population failures that can occur during service creation on a 9500 MPR NE; see Procedure Create VLAN groups and add members to each group; see Procedure Create the VLAN paths that are required between the 9500 MPR group members. The VLAN path can be hop based or ring based. See Procedure Create one of the following VLL service types: a 9500 MPR (ETSI only) VLL Apipe services; see Procedure b 9500 MPR VLL Cpipe services; see Procedure Fix failed cross-connections on a 9500 MPR VLL Cpipe service, as required; see Procedure Configure a GNE site on a 9500 MPR VLL Apipe or Cpipe service; see Procedure Discover 9500 MPR VLL services; see Procedure Alcatel-Lucent 5620 Service Aware Manager

143 MPR VLL service management 8 Turn up the VLL service as required by configuring the Administrative State parameter in the Create Services form to Up. 9 Perform the following, as required: a View the VLL service operational status or view the service topology map associated with a VLL service; see the User Guide. b Delete a VLAN group or group member; see Procedure c Delete a 9500 MPR VLAN path; see Procedure d Modify or delete a VLL service; see the User Guide VLL service management procedures for 9500 MPR devices Use the following procedures to perform VLL service creation and management tasks for 9500 MPR devices. Procedure 11-1 To create a VLL Apipe service on the 9500 MPR (ETSI only) 1 Choose Create Service 9500 VLL Apipe (ATM to ATM/Eth) from the main menu. The 9500 MPR Apipe Service (Create) form opens with the General tab displayed. 2 Click on the Select button to choose a customer to associate with the Apipe service. The Select Customer MPR Apipe Service form opens. 3 Choose the Default Customer as the customer for the Apipe service and click on the OK button. The Select Customer MPR Apipe Service form closes and the 9500 MPR Apipe Service (Create) form reappears with the customer information displayed. 4 Configure the parameters: Service ID Auto-Assign ID SVC Mgr Service ID Service Name Description Service Tier Service Priority Specify VLAN Path Current OLC State Revert OLC State The Service ID parameter is configurable when the Auto-Assign ID parameter is disabled. The SVC Mgr Service ID parameter is configurable when the Auto-Assign ID parameter is disabled. The Current OLC State parameter is configurable when you click on the Apply button. Alcatel-Lucent 5620 Service Aware Manager 11-3

144 MPR VLL service management 12.0 R7 December HE AAAG TQZZA Edition 01 5 Perform the following procedure if the Specify VLAN Path parameter check-box is selected in step 4. i Click on the Select button to choose a VLAN path to associate with the Apipe service. The Select VLAN Path MPR Apipe Service form opens. ii Choose a VLAN path and click on the OK button. The Select VLAN Path MPR Apipe Service form closes and the 9500 MPR Apipe Service (Create) form reappears with the VLAN path information displayed on the General tab. Note If no VLAN path exists, see Procedure 10-2 for information about how to create VLAN paths. 6 Configure the parameters: VLAN ID Auto-Assign ID Service Class PW Label Auto-Assign ID VC Type The VLAN ID and PW Label parameters are enabled when the Auto-Assign ID parameters are disabled. 7 Configure the MAC Address parameter, if you configured the Service Class parameter as ATM to Eth in step 6. 8 Right-click on the 9500 MPR Apipe Service on the navigation tree and choose Create 9500 MPR Apipe Site from the contextual menu. The Select Network Element form opens. For information about adding a GNE site to a VLL service, see Procedure Choose an NE from the list and click on the OK button. The Select Network Element form closes and the 9500 MPR Apipe Site (Create) form opens with the General tab displayed. 10 Configure the parameters: Name Description 11 Click on the Components tab. 12 Right-click on L2 Access Interfaces and choose Create 9500 MPR Apipe L2 Access Interface. The 9500 MPR Apipe L2 Access Interface (Create) form opens with the General tab displayed. 13 Configure the parameters: Name Description 11-4 Alcatel-Lucent 5620 Service Aware Manager

145 MPR VLL service management 14 Click on the Port tab. 15 Click on the Select button to choose a terminating port for the L2 access interface. The Select Terminating Port MPR Apipe L2 Access Interface form opens. 16 Use the configurable filter and Search button to choose a port, and click on the OK button. The Select Terminating Port MPR Apipe L2 Access Interface form closes, and the 9500 MPR Apipe L2 Access Interface (Create) form displays the port information. Note 1 If ports on a card slot of the 2+2 Ethernet (EAS) card are used to create the Apipe service, first configure the Profile Name parameter on the card slot. See Procedure 7-11 for information about how to configure this parameter. Note 2 If MPT-MC or MPT-HC ports are being used as network ports on the 2+2 x Ethernet (EAS) card, the peer MAC Address must be specified for the L2 Access Interface. 17 Perform one of the following. a If you selected a value of VCC for the VC Type parameter, go to step 18. b If you selected a value of VPC for the VC Type parameter, go to step Configure the parameters: Outer Encapsulation Value (VPI) Inner Encapsulation Value (VCI) Outer Encapsulation Value (VPI) Inner Encapsulation Value (VCI) 19 Configure the parameters: Outer Encapsulation Value (VPI) Outer Encapsulation Value (VPI) 20 Click on the ATM tab. 21 Click on the Select button to choose an Ingress ATM Policy. The Select Ingress ATM Policy - ATM Configuration form opens. 22 Use the configurable filter and Search button to choose a policy, and click on the OK button. The Select Ingress ATM Policy - ATM Configuration form closes, and the L2 Access Interface (Create) form displays the policy information. 23 Click on the Select button to choose an Egress ATM Policy. The Select Egress ATM Policy - ATM Configuration form opens. 24 Use the configurable filter and Search button to choose a policy, and click on the OK button. The Select Egress ATM Policy - ATM Configuration form closes, and the L2 Access Interface (Create) form displays the policy information. 25 Click on the OK button. A dialog box appears. Alcatel-Lucent 5620 Service Aware Manager 11-5

146 MPR VLL service management 12.0 R7 December HE AAAG TQZZA Edition Click on the OK button. The L2 Access Interface (Create) form closes, and the Apipe Site (Create) form reappears with the new interface information displayed in the service navigation tree. 27 Perform one of the following: a Create another site for the VLL service, if required. Repeat steps 8 to 26. b Go to step Click on the OK button. The Apipe Service (Create) form closes. You can use the service topology maps to view the service. Note If service creation fails or generated NE inconsistencies occur, see Procedure 4-2. Procedure 11-2 To create a VLL Cpipe service on a 9500 MPR 1 Choose Create Service 9500 VLL Cpipe (CEM to CEM/Eth) from the main menu. The Cpipe Service (Create) form opens with the General tab displayed. 2 Click on the Select button to choose a customer to associate with the Cpipe service. The Select Customer - Cpipe Service form opens. 3 Choose the Default Customer as the customer for the Cpipe service and click on the OK button. The Select Customer - Cpipe Service form closes and the Cpipe Service (Create) form reappears with the customer information displayed. 4 Configure the parameters: Service ID Auto-Assign ID SVC Mgr Service ID Service Name Description Service Tier Service Priority Specify VLAN Path Path Type Current OLC State Revert OLC State The Service ID parameter is configurable when the Auto-Assign ID parameter is disabled. The SVC Mgr Service ID parameter is configurable when the Auto-Assign ID parameter is disabled Alcatel-Lucent 5620 Service Aware Manager

147 MPR VLL service management The Current OLC State parameter is configurable when you click on the Apply button. Note To create a 9500 MPR Cpipe service with an ERPS tail node, set the Path Type parameter to Ring Based. 5 Click on the Select button to choose a VLAN path to associate with the Cpipe service. The Select VLAN Path - Cpipe Service form opens. Note 1 If no VLAN path exists, see Procedure 10-2 for information about how to create a VLAN path. Note 2 You cannot create VLL Cpipe services on a 9500 MPR using the if the associated VLAN path spans across adjacent physical links. The VLL Cpipe service must have at least one radio link. If required, contact your Alcatel-Lucent technical support representative for alternative VLL Cpipe service configuration options. 6 Choose a VLAN path and click on the OK button. The Select VLAN Path - Cpipe Service form closes and the Cpipe Service (Create) form reappears with the VLAN path information displayed on the General tab. 7 Configure the parameters: Auto-Assign ID VLAN ID The VLAN ID parameter is enabled when the Auto-Assign ID parameter is disabled. 8 Configure the Service Class parameter. 9 If you specified the CEM to Eth option in step 8, configure the parameters: EC ID Tx/Rx Auto-Assign ID Clock Source Mac Address The EC ID Tx/Rx parameter is configurable when the Auto-Assign ID parameter is disabled. 10 If you set the Service Class parameter to the SDH to SDH option in step 8, configure the parameters: Clock Source Jitter Buffer Depth 11 In the navigation tree, right-click on a 9500 MPR Cpipe Service and choose Create Cpipe Site. The Select Network Elements - Cpipe Service form opens with a list of available 9500 MPR sites. For information about adding a GNE site to a VLL service, see Procedure Alcatel-Lucent 5620 Service Aware Manager 11-7

148 MPR VLL service management 12.0 R7 December HE AAAG TQZZA Edition Choose a site and click on the OK button. The Select Network Elements - Cpipe Service form closes and the Cpipe Site (Create) form opens with the General tab displayed. 13 Configure the parameters: Name Description Administrative State Monitor Access Interface Operational State 14 Click on the Components tab. 15 Right-click on L2 Access Interfaces and choose Create L2 Access Interface. The L2 Access Interface (Create) form opens with the General tab displayed. 16 Configure the parameters: Name Description 17 Click on the Port tab. 18 Click on the Select button to choose a port for the L2 access interface. The Select Terminating Port - L2 Access Interface form opens. Note The form lists only ports in access or hybrid mode. To choose a port that is not listed, you must set the Mode parameter for the port to Access or Hybrid. 19 Use the configurable filter and Search button to choose a port, and click on the OK button. The Select Terminating Port - L2 Access Interface form closes, and the L2 Access Interface (Create) form displays the port information. 20 Click on the OK button. A dialog box appears. 21 Click on the OK button. The L2 Access Interface (Create) form closes, and the Cpipe Site (Create) form reappears with the new interface information displayed in the service navigation tree. 22 If the 9500 MPR Cpipe service is for an ERPS tail node, a radio or Ethernet termination port is required for the site: i ii iii Click on the Tail Terminating Port tab. Click on the Select button to choose an ERPS tail terminating port. The Select ERPS Tail Terminating Port - Cpipe Site form opens. Choose an ERPS tail terminating port and click on the OK button. The Cpipe Site (Create) form reappears. 23 If you need to create another L2 access interface for the site in the Cpipe service, repeat steps 15 to Alcatel-Lucent 5620 Service Aware Manager

149 MPR VLL service management 24 Perform one of the following: a Create an another site for the VLL service, if required. Repeat steps 11 to 21. b Go to step Click on the OK button. The Cpipe Service (Create) form closes. You can use the service topology maps to view the service. Note If service creation fails or generated NE inconsistencies occur, see Procedure 4-2. Procedure 11-3 To create a single site VLL Cpipe service on 9500 MPR connected to an MSS1c lightweight GNE You must configure a physical link between the 9500 MPR MSS-8, MSS-4, or MSS-1 port and the MSS1c lightweight GNE before performing this procedure. See the procedure To create a physical link in the User Guide for more information about configuring a physical link. 1 Choose Create Service 9500 VLL Cpipe (CEM to CEM/Eth) from the main menu. The 9500 MPR Cpipe Service (Create) form opens with the General tab displayed. 2 Click on the Select button to choose a customer to associate with the Cpipe service. The Select Customer MPR Cpipe Service form opens. 3 Choose the Default Customer as the customer for the Cpipe service and click on the OK button. The Select Customer - Cpipe Service form closes and the Cpipe Service (Create) form reappears with the customer information displayed. 4 Configure the parameters: Service ID Auto-Assign ID SVC Mgr Service ID Service Name Description Service Priority The Service ID parameter is configurable when the Auto-Assign ID parameter is disabled. The SVC Mgr Service ID parameter is configurable when the Auto-Assign ID parameter is disabled. 5 Deselect the Specify VLAN Path checkbox. Alcatel-Lucent 5620 Service Aware Manager 11-9

150 MPR VLL service management 12.0 R7 December HE AAAG TQZZA Edition 01 6 In the navigation tree, right-click on a 9500 MPR Cpipe Service and choose Create 9500 MPR Cpipe Site. The Select Network Elements MPR Cpipe Service form opens with a list of available 9500 MPR sites. 7 Choose a 9500 MPR site and click on the OK button. The Select Network Elements - Cpipe Service form closes and the 9500 MPR Cpipe Site (Create) form opens with the General tab displayed. 8 Configure the parameters: Name Description 9 Click on the Network Port tab. 10 Click on the Select button to choose a port. The Select Network Port form opens. 11 Choose a port that is configured with the physical link to the MSS1c lightweight GNE and click on the OK button. The Select Network Port form closes and the port information appears in the 9500 MPR Cpipe Site (Create) form. 12 Click on the Interfaces tab and click on the Create button. The 9500 MPR Cpipe L2 Access Interface (Create) form opens with the General tab displayed. 13 Configure the parameters: Name Description 14 Click on the Port tab. 15 Click on the Select button to choose a port for the L2 access interface. The Select Terminating Port MPR Cpipe L2 Access Interface form opens. 16 Choose a port and click on the OK button. The Select Terminating Port MPR Cpipe L2 Access Interface form closes and the 9500 MPR Cpipe L2 Access Interface (Create) form displays the port information. 17 Click on the OK button. A dialog box appears. 18 Click on the OK button. The L2 Access Interface (Create) form closes, and the Cpipe Site (Create) form reappears with the new interface information displayed in the service navigation tree. 19 Click on the Apply button to save the changes Alcatel-Lucent 5620 Service Aware Manager

151 MPR VLL service management Procedure 11-4 To discover a single-site Cpipe service on 9500 MPR connected to an MSS-1c lightweight GNE 1 Choose Manage Service Services from the main menu. The Manage Services form opens. 2 Click on the Discover MPR 9500 Services and choose Hop Based from the contextual menu. The Discover MPR 9500 Services form opens with a list of topology groups. 3 Choose the topology group containing the 9500 MPR devices and click on the OK button. The Discover MPR 9500 Services form closes and the Manage Service form reappears with a list of services. Procedure 11-5 To fix a failed cross-connection in a 9500 MPR Cpipe or a hop-based VLAN service The may fail to establish one or more cross-connects when you deploy or create a 9500 MPR Cpipe service or a hop-based VLAN service. If you determine that a service is down because of a failed cross-connect, you can try to re-establish the cross-connect. Note You must clear deployment errors that are associated with a failed cross-connect before you attempt to re-establish the cross-connect. 1 Choose Manage Service Services from the main menu. The Manage Services form opens. 2 Configure the filter criteria for the service type that you need to find and click on the Search button. A list of services appears. 3 Choose a 9500 MPR Cpipe service and click on the Properties button. The Cpipe Service (Edit) form opens with the General tab displayed. 4 Click on the Complete Transport Service button. A dialog box appears. 5 Click on the Yes button. 6 Verify that the cross-connects are operational. 7 Close the Manage Services form. Alcatel-Lucent 5620 Service Aware Manager 11-11

152 MPR VLL service management 12.0 R7 December HE AAAG TQZZA Edition 01 Procedure 11-6 To configure a GNE site on a VLL service Perform this procedure to add a GNE site and GNE service interfaces to a VLL service. This procedure applies to 9500 MPR VLL Apipe and Cpipe services. 1 Choose Manage Service Services from the main menu. The Manage Services form opens. 2 Configure the filter criteria. A list of services appears. 3 Select a VLL service and click on the Properties button. The VLL_type Service (Edit) form opens with the General tab displayed. 4 On the component tree, right-click on VLL_type Service and choose Create GNE Site. The Select Network Elements - VLL_type Service form opens with a list of available NEs. 5 Choose a site and click on the OK button. The GNE Site (Create) form opens with the General tab displayed. 6 Configure the parameters: Name Description 7 Click on the Apply button. 8 To configure an interface for the GNE site, perform the following steps: i ii Click on the GNE Service Interfaces tab and click on the Create button. The GNE Service Interface (Create) form opens with the general tab displayed. Configure the parameters: Name Description Type iii iv v Click on the Ports tab and click on the Select button beside the Interface Index field. The Select Generic NE Interface form opens. Choose an interface from the list and click on the OK button. The GNE Service Interface (Create) form reappears with the interface information displayed. Configure the parameters: Encapsulation Type Outer Encapsulation Value Inner Encapsulation Value vi Click on the OK button. The GNE Site (Create) form reappears with the interface information displayed in the service component tree. 9 Click on the Scripts tab to attach or run configuration scripts on the GNE site. The Scripts tab displays the script instances and versions that are applied to the device. See the Scripts and Templates Developer Guide Alcatel-Lucent 5620 Service Aware Manager

153 MPR VLL service management 10 Click on the OK button. The VLL_type Service (Edit) form reappears with the new information displayed in the service component tree. 11 Click on the OK button. The VLL_type Service (Edit) form closes. You can use the topology maps to view the service. See the topology map management chapter in the User Guide for more information. Alcatel-Lucent 5620 Service Aware Manager 11-13

154 MPR VLL service management 12.0 R7 December HE AAAG TQZZA Edition Alcatel-Lucent 5620 Service Aware Manager

155 Appendices A MPR SAM-E license functionality A-1 Alcatel-Lucent 5620 Service Aware Manager

156 Alcatel-Lucent 5620 Service Aware Manager

157 A MPR SAM-E license functionality A MPR SAM-E license functionality A-2 Alcatel-Lucent 5620 Service Aware Manager A-1

158 A MPR SAM-E license functionality 12.0 R7 December HE AAAG TQZZA Edition 01 A MPR SAM-E license functionality This appendix describes functionality with a 9500 MPR SAM-E license. The SAM-E module restricts end to end functionality to basic node management. In this scenario, customers are expected to use a craft tool such as NEtO for service management. Table A-1 lists the specific functionality for a SAM-E license, compared to management functions available in NEtO. Table A-1 SAM-E and NEtO management functionality Feature NEtO Notes SAM-E System administration Scalable system Y Y Protected configuration (high availability) Y Y North bound interfaces Y Y Security management (user profiles, login check, password rules etc.) Y Y (see note) Same profile as user Y User access profiles Y Y (see note) Same profile as user Y Community string Y Y Y NEtO TACACS+ support Y Y (see note) NEtO cross launch with null for TACACS+ Y SNMPv3 support Y Y Y Graphic environment NE creation/discovery N/A Y Y NE equipment View Y Y GUI panels, trees, equipment manager UI navigation Y Y GUI panels, trees, equipment manager UI alarm navigation N/A Y Alarms to GUI config forms, GUI MAP, GUI managers Y Y Y Map: topology view N/A Y Maps are a -EAP feature N Map: automatic radio link discovery N/A Y Maps are a -EAP feature N Map: automatic traffic ports discovery (LLDP) N/A Y Maps are a -EAP feature N NE administration Change IP address Y Y (see note) Requires opening NEtO Y Change routing parameters Y Y (see note) Requires opening NEtO Y Change system settings Y Y Y Date and time configuration Y Y Y NTP support Y Y (see note) Use NEtO for configuration and the -E alarm support Y Synchronization (TDM, radio, ethernet, SDH) Y Y Y Equipment inventory Y Y (see note) equipment manager Y Chassis configuration and visualization Y Y Y (1 of 5) A-2 Alcatel-Lucent 5620 Service Aware Manager

159 A MPR SAM-E license functionality Feature NEtO Notes SAM-E Board/port configuration and visualization Y Y Y Port segregation Y Y Y QoS configuration Y Y Since 9500 MPR Release 3.2 Y ATM I/F bundle Y Y Y Radio parameter view Y Y Y Statistics view per radio and ethernet traffic port Y Y Y Frequency configuration Y Y (see note) Requires opening NEtO Y Link identifier Y Y (see note) Requires opening NEtO Y PPP RF Y Y (see note) Requires opening NEtO Y RTPC configuration Y Y (see note) Requires opening NEtO Y ATPC configuration Y Y (see note) Requires opening NEtO Y Current power levels visualization Y Y Y Channel switching Y Y (see note) Requires opening NEtO Y Loopbacks Y Y Y SWDL on NE base Y Y Y Backup on NE base Y Y Y Restore on NE base Y Y Y Alarms Representation in NE Y Y Y Alarm synthesis Y Y Y Alarms and events reporting Y Y Y Alarm severity assignment profile Y Y (see note) since 9500 MPR Release 3.0; requires opening NEtO Y Equipment correlation (port - card - chassis) N Y -E base correlation Y Common loss alarm Y Y N Vertical correlation (links/ports/tca - paths - services) Vertical correlation (9500 MPR transport SAR services) Performance management N Y -EAP E2E services and transport N Y -EAP E2E services and transport N N PM activation Y Y (see note) Requires opening NEtO Y PM visualization Y Y Y - PM radio: G.826 Y Y Y - PM radio: Analogue measurements TSL/RSL Y Y Y - PM E1 framed Y Y Y - PM adaptive modulation Y Y Y - PM Ethernet counters (statistics) over radio TX and traffic port Y Y Same as in NEtO Y (2 of 5) Alcatel-Lucent 5620 Service Aware Manager A-3

160 A MPR SAM-E license functionality 12.0 R7 December HE AAAG TQZZA Edition 01 Feature NEtO Notes SAM-E - PM Ethernet elaborated (statistics) over radio TX and traffic port Y N Y - PM plotter Y Y N - PM AM/radio/Ethernet elaboration Y N N - PM AM/radio/Ethernet TCA Y N N Specific protections Status/configuration - N x (1+K) radio (x:0..1) Y Y (see note) N x 1+0 configuration form / status and labels through NEtO Y Status/configuration - LAG L2 (radio) Y Y Y Status/configuration - LAG L2 (user side) Y Y Y Status/configuration - XPIC (1+1 redundancy) Y Y (see note) XPIC configuration form; status and labels through NEtO Y Status/configuration - virtual protection links (VCL) Y Y (see note) VPC configuration form / status and labels through NEtO Y Status/configuration - ERP 8032 ring Y Y (see note) Ring (No Services) - Release 3.3 and Release 3.4 Status/configuration - LAG L1 - radio Y Y (see note) XPIC configuration form; status and labels through NEtO - Release 3.4 Y Y Protection Impact - e2e path N/A Y (see note) In path management N Protection Impact - services N/A Y (see note) In service management N Protection Impact - map N/A Y (see note) In L1/L2 map N Common network management Network management (up to thousands of NEs) N (see note) Y Limited to few NEs of the same type Y Support for multiple concurrent operator sessions N Y Y Centralized management of alarms N Y Y Centralized management of PM N Y Y Centralized management of network inventory N Y Y Scheduled backup on multiple devices (configurable) Scheduled SW download on multiple devices (configurable) Support of northbound open interfaces towards external OSS Archiving of network data on a configurable period of time N Y Y N Y Y N Y Y N Y Y Service Provisioning X-connect (create/delete) Service profiles (3 of 5) NE based Y per NE X-connection N A-4 Alcatel-Lucent 5620 Service Aware Manager

161 A MPR SAM-E license functionality Feature NEtO Notes SAM-E - TDM2ETH NE based Y profile, access/site templates and local configurations N - ATM2ATM NE based Y profile, access/site templates and local configurations N - ATM2ETH NE based Y profile, access/site templates and local configurations N - SDH2SDH NE based Y profile, access/site templates and local configurations N - TDM2ETH-over-SDH NE based Y profile, access/site templates and local configurations N L2 PW - E2E DOT1Q service NE based Y Full E2E services including automated X-connection N L2 PW - E2E ATM service NE based Y Full E2E services and automated X-connection N L2 PW - E2E TDM service NE based Y Full E2E services and automated X-connection N L2 PW - E2E SDH service NE based Y Full E2E services and automated X-connection N L2 BRIDGED - E2E DOT1Q PTP service NE based Y Full E2E services and automated X-connection N L2 BRIDGED - E2E DOT1Q P2MP service NE based Y Full E2E services and automated X-connection N L2 BRIDGED - E2E DOT1Q P2MP service NE based Y Full E2E services and automated X-connection N L2 ERPS PTP service NE based Y Full E2E services and automated X-connection N L2 ERPS PTMP service NE based Y Full E2E services and Automated X-connection N L2 service maps (eg. transport service connectivity) N/A Y Full E2E services N L2 service manager N/A Y Full E2E services N L2 per service alarms (filtered per view) N/A Y Full E2E services N NEtO - service interworking N/A Y Allows NEtO and service configuration N End to end network management End to end TDM traffic provisioning N Y N End to end ATM traffic provisioning N Y N End to end 802.1Q traffic provisioning N Y N End to end SDH2SDH traffic provisioning N Y N P2P path creation and visualization N Y Network L2 Route & metric / hop cost - e2e correlation N (4 of 5) Alcatel-Lucent 5620 Service Aware Manager A-5

162 A MPR SAM-E license functionality 12.0 R7 December HE AAAG TQZZA Edition 01 Feature NEtO Notes SAM-E P2MP Path (bridging) creation and visualization N Y Network L2 Route & metric / hop cost - e2e correlation N VLAN groups and VLAN space management N Y N QoS policy distribution and audit N Y starting with 9500 MPR Release 3.2 including policy bundling N CAC management N Y N Radio tail support N Y Enhanced composite service N Service in service - path - service impact N Y Alarm correlation from radio / path to services N Service in service - path to 7705 SAR service impact N Y Alarm correlation from radio / path to services N Auto tunnel creation - N x (1+0) - P2P N Y N Auto tunnel creation - N x (1+0) - P2MP N Y N (5 of 5) A-6 Alcatel-Lucent 5620 Service Aware Manager

163 Customer documentation and product support Customer documentation Customer Documentation Welcome Page Technical Support Documentation feedback

164 2014 Alcatel-Lucent. All rights reserved.