MPR Configuration File Management PDF

Configuration File Management
Alcatel-Lucent 9500
MICROWAVE PACKET RADIO for ETSI | RELEASE 5.2.0
Configuration File Management
3DB19901BFAA Edition 01
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.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change
without notice.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are 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.
Table of Contents
Preface ............................................................................................................... 11
Preliminary Information..................................................................................................... 11
WARNING .................................................................................................................. 11
NOTICE..................................................................................................................... 11
COPYRIGHT NOTIFICATION.............................................................................................. 11
TECHNICAL SUPPORT .................................................................................................... 11
SAFETY RECOMMENDATION ............................................................................................. 12
SERVICE PERSONNEL SKILL .............................................................................................. 12
Applicability .................................................................................................................. 12
Scope........................................................................................................................... 13
History ......................................................................................................................... 13
Handbook Structure ......................................................................................................... 14
General on Customer Documentation..................................................................................... 14
Customer–Independent Standard Customer Documentation ...................................................... 14
Product levels and associated Customer Documentation .......................................................... 15
Handbook Updating ...................................................................................................... 16
Changes introduced in the same product–release (same handbook P/N) ....................................... 16
Supplying updated handbooks to Customers......................................................................... 17
Changes due to new product version ................................................................................. 17
Customer documentation on CD-ROM................................................................................. 17
Contents, creation and production of a CD-ROM.................................................................... 18
Use of the CD-ROM....................................................................................................... 18
CD-ROM identification................................................................................................... 19
CD-ROM updating......................................................................................................... 19
1 — Management of flag file on MPR............................................................................ 21

1.1 — File Name .............................................................................................................. 21
1.2 — Flag File Format ...................................................................................................... 21
1.3 — Flag File path in NE File System.................................................................................... 21
1.4 — Flag File upload ....................................................................................................... 21
1.5 — How to run a Flag File ............................................................................................... 21
1.6 — Backup & Restore for FlagFile ...................................................................................... 22
1.7 — Flag file to enable the Low Latency feature for TDM2ETH DS1 ............................................... 22
1.8 — Flag file to invert the polarity of housekeeping outputs of the MSS-1 ....................................... 23
2 — Management of enhanced Configuration File ........................................................... 25

2.1 — File Name .............................................................................................................. 25
2.2 — File Format ............................................................................................................ 26
2.3 — Configuration File path in NE File System ........................................................................ 27
2.4 — Configuration File upload and execution ......................................................................... 27
2.5 — Configuration File Removal ......................................................................................... 28
2.6 — Configuration File update: add a new command/feature...................................................... 28
2.7 — Configuration File update: remove an existing command/feature ........................................... 29
2.8 — Restoring Ethernet switch initial configuration.................................................................. 30
2.8.1 — Restoring “enhanced_eth_feature.psh” configuration file: ............................................. 30
Configuration 3DB19901BFAA Edition 01 3

2.8.2 — Restoring “fullConfig_mptacc.psh”, fullConfig_eas.psh, and fullConfig_easv2.psh
configuration file:........................................................................................................ 31
2.8.3 — Restoring “enhanced_eth_feature.psh” configuration file (AUX card case): ......................... 31
2.8.4 — Restoring MOD300 initial configuration ..................................................................... 32
2.9 — Restoring SFP 2xE1/DS1 configuration ............................................................................ 32
2.10 — Restoring MPT initial configuration .............................................................................. 32
2.11 — Behavior during SW restart ........................................................................................ 33
2.12 — SW package activation ............................................................................................. 33
2.13 — Behavior in CORE protection ...................................................................................... 33
2.14 — Behavior in Radio protection ...................................................................................... 33
2.15 — Behavior in Ethernet Link Aggregation .......................................................................... 34
2.16 — Behavior in Radio Link Aggregation .............................................................................. 34
2.17 — TMN enabled on ETH4 port ........................................................................................ 34
2.18 — Software package upgrade ........................................................................................ 34
2.19 — List of portable/unportable features from previous releases ................................................ 35
2.20 — Relevant notes....................................................................................................... 36
2.21 — List of removed features........................................................................................... 36
2.22 — Backup & Restore for Configuration Files ....................................................................... 37
3 — Common Assumption ......................................................................................... 39

3.1 — Switch to equipment ports assignment ........................................................................... 39
3.2 — MPT-ACC, EAS and EASv2 switch command definition .......................................................... 41
3.3 — SFP 2E1/DS1 command definition.................................................................................. 42
3.4 — MPT Configuration File and command definition ................................................................ 43
3.4.1 — Example ......................................................................................................... 44
4 — Features supported through Configuration file management........................................ 45

4.1 — Autonegotiation on SFP port ........................................................................................ 45
4.1.1 — Autonegotiation managed since MPR 3.1 release ......................................................... 45
4.1.2 — Overview ........................................................................................................ 45
4.1.3 — Disable Auto-Negotiation example .......................................................................... 46
4.1.4 — Re-Enable Auto-Negotiation example ....................................................................... 46
4.2 — OUT OF RANGE VLAN SWAP ......................................................................................... 47
4.2.1 — Background...................................................................................................... 47
4.2.2 — Preliminary configuration..................................................................................... 48
4.2.3 — Port configuration.............................................................................................. 50
4.2.3.1 — User UNI port specific commands ..................................................................... 50
4.2.3.2 — User NNI port specific commands ..................................................................... 51
4.2.4 — VLAN Table management ..................................................................................... 52
4.2.5 — Admit out of range VLAN ..................................................................................... 53
4.2.6 — Manage in range VLAN on user UNI .......................................................................... 53
4.2.7 — User UNI Port enable command.............................................................................. 54
4.2.8 — Example of configuration for VLAN 4092 Swap ............................................................ 54
4.2.8.1 — Content of “enhanced_eth_feature.psh” for Gateway 1 .......................................... 54
4.2.8.2 — Content of “enhanced_eth_feature.psh” for Gateway 2: ......................................... 56
4.3 — VLAN SWAP AND DOT1P REMARKING FOR ATM PW SERVICE .................................................... 58
4.3.1 — Background...................................................................................................... 58
4.3.2 — Migration Procedure .......................................................................................... 59
4 Configuration 3DB19901BFAA Edition 01

4.3.4 — Enable 802.1p bit remarking ................................................................................. 60
4.3.5 — VLAN swap and 802.1p remarking for Egress Direction .................................................. 61
4.3.5.1 — Egress VLAN swap rule definition ..................................................................... 61
4.3.5.2 — Per CoS 802.1p bit remarking rule definition....................................................... 62
4.3.6 — VLAN swap and 802.1p remarking for Ingress Direction ................................................. 63
4.3.6.1 — Ingress VLAN swap rule definition..................................................................... 63
4.3.6.2 — Per ATM PW flow 802.1p bit remarking rule definition ............................................ 63
4.3.7 — Example of configuration for VLAN Swap for ATM PW Service ......................................... 65
4.3.7.1 — Content of “enhanced_eth_feature.psh”: ........................................................... 65
4.4 — VLAN SWAP AND FORWARDING FOR “LOCAL ATM SWITCH” .................................................... 67
4.4.1 — Background...................................................................................................... 67
4.4.3 — VLAN swap and frame forwarding .......................................................................... 68
4.4.3.1 — VLAN swap - preliminary definition ................................................................... 68
4.4.3.2 — VLAN swap and frame forwarding rule definition................................................... 69
4.4.4 — Example of configuration for “Local” ATM Switch ........................................................ 70
4.5 — ACCESS CONTROL LIST ............................................................................................... 72
4.5.2 — Feature activation ............................................................................................. 74
4.5.2.1 — Define an entry in the ACL ............................................................................. 74
4.6 — SFP 2E1/DS1 CIRCUIT EMULATION.................................................................................. 75
4.6.1 — Description ...................................................................................................... 75
4.6.2 — Normal procedure .............................................................................................. 76
4.6.3 — Configuration File basic structure ........................................................................... 77
4.6.3.1 — Optical Port 5 default configuration .................................................................. 78
4.6.3.2 — Optical Port 6 default configuration .................................................................. 78
4.6.3.3 — Optical port 5 Tributary 1 IWF configuration........................................................ 79
4.6.3.7 — Optical port 5 tributaries common configuration................................................... 86
4.6.3.8 — Optical port 6 tributaries common configuration................................................... 88
4.6.3.9 — Relevant registers ....................................................................................... 90
4.6.4 — Blue Signal configuration ..................................................................................... 95
4.6.4.1 — Optical port 5 Tributary 1 .............................................................................. 95
4.6.5 — Configuration for DS1 traffic ................................................................................. 97
4.6.5.1 — LIU Configuration ........................................................................................ 97
4.6.5.2 — E1/DS1 selection in Adorno Configuration block.................................................... 97
4.6.5.3 — E1/DS1 selection in Adorno Tdm interface .......................................................... 98
4.6.5.4 — Configuration of framed/unframed and ESF for DS1 Tributaries ................................. 98
4.6.6 — Configuration for TDM2TDM profile ......................................................................... 99
4.6.6.1 — Packet Length Configuration .......................................................................... 99
4.6.6.2 — Other parameters for ETSI traffic ....................................................................100
4.6.6.3 — Other parameters for ANSI traffic....................................................................100
4.6.7 — Example ........................................................................................................101
4.6.7.1 — E1 traffic, TDM2ETH profile ...........................................................................101

4.6.7.2 — E1 traffic, TDM2TDM profile ..........................................................................107
4.6.7.3 — DS1 traffic, TDM2ETH profile .........................................................................120
4.6.7.4 — DS1 traffic, TDM2TDM profile .........................................................................131
4.7 — ALARM SEVERITY ASSIGNMENT PROFILE ..........................................................................142
4.7.1 — Description .....................................................................................................142
4.7.2 — Normal procedure .............................................................................................142
4.7.3 — Migration in case of SWP Upgrade ..........................................................................142
4.7.4 — File content ....................................................................................................143
4.7.5 — Example ........................................................................................................146
4.8 — PORT MAC LEARNING LIMITING ...................................................................................150
4.8.1 — Preliminary configuration....................................................................................150
4.8.2 — Feature activation ............................................................................................150
4.9 — DOT1P ASSIGNMENT BASED ON INCOMING DIFFSERV ...........................................................151
4.9.1 — Overview .......................................................................................................151
4.9.2 — Preliminary configuration....................................................................................151
4.9.3 — Feature activation ............................................................................................151
4.9.4 — Example ........................................................................................................152
4.10 — MAC AGING TIME CONFIGURATION ..............................................................................153
4.10.1 — Overview ......................................................................................................153
4.10.2 — Feature activation ...........................................................................................153
4.10.3 — Example .......................................................................................................154
4.11 — QOS BASED ON MPLS TC (ALSO CALLED EXP BITS).............................................................154
4.11.1 — Overview ......................................................................................................154
4.11.2 — Preliminary Configuration ..................................................................................154
4.11.3 — Removal of User Ethernet interface from existing QoS mapping.....................................155
4.11.4 — Mapping MPLS TC field into PCP field of VLAN Tag .....................................................158
4.11.5 — Mapping MPLS TC field to Ethernet switch queues .....................................................160
4.11.6 — Example .......................................................................................................161
5 — Appendix...................................................................................................... 169
5.1 — Configuration File No Restart tool ................................................................................169
5.1.1 — Tool Launch on JUSM .........................................................................................170
5.1.2 — Main view.......................................................................................................170
5.1.3 — How to perform Delta Configuration without NE Restart ...............................................171
5.1.4 — Import/Export of Enhanced Configuration files ..........................................................174
5.2 — File Transfer Manager tool .........................................................................................174
5.2.1 — Tool Launch on JUSM ........................................................................................175
5.2.2 — Main View ......................................................................................................176
5.2.3 — Import/Export of Enhanced Configuration files ..........................................................178
5.3 — ATMoMPLS Protocol Stack Configuration by HTTP interface (MPR WebServer) ............................178
6 — Abbreviations ................................................................................................ 183

List of Figures

Figure 3.1 — Equipment ports.............................................................................................. 40
Figure 3.2 — Map message format......................................................................................... 44

Figure 4.1 — Autonegotiation configuration on SFP ports ............................................................. 45
Figure 4.2 — Out of range VLAN swap .................................................................................... 47
Figure 4.3 — SFP configuration ............................................................................................ 76
Figure 4.4 — Tributary destination MAC address ........................................................................ 92
Figure 4.5 — Tributary VLAN ID and ECID ................................................................................ 93
Figure 4.6 — Compatibility table between 32E1 PDH card and 2xE1/DS1 SFP Module ............................ 94
Figure 4.7 — Compatibility table between two 2xE1/DS1 SFP modules ............................................. 95
5 — Appendix...................................................................................................... 169
Figure 5.1 — Configuration File No Restart Tool Launch..............................................................170
Figure 5.2 — Main view.....................................................................................................171
Figure 5.3 — Delta Configuration Operation 1/3 .......................................................................172
Figure 5.6 — FTM Tool Launch ............................................................................................176
Figure 5.7 — Main view.....................................................................................................177
Figure 5.8 — MPR WebServer Main page.................................................................................179
Figure 5.9 — MPR WebServer MPLS Setting Page 1/2..................................................................180
Figure 5.10 — MPR WebServer MPLS Setting Page 2/2 ................................................................181

List of Tables
Preface ............................................................................................................... 11
Table 1 — Product Releases ............................................................................................... 13
Table 2 — History ............................................................................................................ 13
Table 3 — Handbook structure ............................................................................................ 14
2 — Management of enhanced Configuration File ........................................................... 25

Table 2.1 — Portable features from previous releases ................................................................ 35

Table 3.1 — Port assignment .............................................................................................. 40
Table 3.2 — MSS-8 shelf .................................................................................................... 41
Table 3.3 — MSS-4 shelf .................................................................................................... 41

Table 4.1 — n values on a per port basis ................................................................................ 61
Table 4.2 — CoS and newdot1p parameters by ATM PW CoS ......................................................... 63
Table 4.3 — 801.1p bit values to remap in ingress ..................................................................... 64
Table 4.4 — User ethernet port bitmap where ATM PW frames are forwarded ................................... 64
Table 4.5 — User Ethernet port bitmap where ATM PW frames ingress the network ............................ 65
Table 4.6 — User Ethernet port bitmap where ACL applies .......................................................... 74
Table 4.7 — Register mask for Adorno Configuration block .......................................................... 98
Table 4.8 — Register mask for framed/unframed and ESF ........................................................... 99
Table 4.9 — Severity table ................................................................................................143
Table 4.10 — Alarm IDs ....................................................................................................143
Table 4.11 — ingPbm values .............................................................................................157
Table 4.12 — ingPbm values (2) .........................................................................................158
6 — Abbreviations ................................................................................................ 183

Table 6.1 — Abbreviations ................................................................................................183

Preface
Preliminary Information
WARNING
Any warranty must be referred exclusively to the terms of the contract of sale of the
equipment to which this handbook refers to.
Alcatel-Lucent makes no warranty of any kind with regards to this manual, and specifically
disclaims the implied warranties of merchantability and fitness for a particular purpose.
ALCATEL-LUCENT will not be liable for errors contained herein or for damages, whether
direct, indirect, consequential, incidental, or special, in connection with the furnishing,
performance, or use of this material.
NOTICE
The product specification and/or performance levels contained in this document are for
information purposes only and are subject to change without notice. They do not represent
any obligation on the part of ALCATEL-LUCENT.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL-LUCENT and must
not be copied, reproduced or disclosed to a third party without written consent.
TECHNICAL SUPPORT

Applicability
Please contact your Local Alcatel Technical Assistance Center for questions referred to the
information contained in this document.
To send your comments about this handbook please follow the indication on Customer
Documentation Feedback.
SAFETY RECOMMENDATION
The safety recommendations here below must be considered to avoid injuries on persons
and/or damage to the equipment:
1. Service Personnel
Installation and service must be carried out by authorized persons having appropriate
technical training and experience necessary to be aware of hazardous operations
during installation and service, so as to prevent any personal injury or danger to other
persons, as well as preventing damage to the equipment.
2. Access to the Equipment
Access to the Equipment in use must be restricted to Service Personnel only.
3. Safety Rules
Local safety regulations must be used if mandatory. Safety instructions in this
handbook should be used in addition to the local safety regulations. In case of conflict
between safety instructions stated in this manual and those indicated in local
regulations, mandatory local norms will prevail. Should not local regulations be
mandatory, then safety rules stated in this manual will prevail.
SERVICE PERSONNEL SKILL

Service Personnel must have an adequate technical background on telecommunications and
in particular on the equipment subject of this handbook.
Applicability
This document applies to 9500MPR R.5.2.0.
This document applies to following product–releases:

Scope
Table 1 — Product Releases
PRODUCT RELEASE
9500 MPR-E 5.2.0
Scope
Scope of this document is to define:
• the configuration files and the procedure to apply them

• how to load Flag file on MPR system to enable special behaviors
By the means of this configuration file it will be possible to configure:
• the Ethernet switch inside the CORE,

• the Ethernet switch inside the MPT-ACC plug-in
• the Ethernet switch inside the EAS plug-in
• the Ethernet switch inside the EASv2 plug-in
• the FPGA inside the Modem 300 board
• SFP 2xE1/DS1 module
• the MPT-xC
in order to obtain a specific behavior unobtainable with the supported configuration tools.
Note: The command described in this document are examples of the command
application, the user should adapt the described commands with the correct data for the
equipment
Commands not described in this document are under user responsibility.
History
Table 2 — History
ISSUE DATE DESCRIPTIONS
01 October 2014 Creation for Release 5.2.0

Handbook Structure
Handbook Structure
This handbook has been edited according to the Alcatel-Lucent standardized “drawing-up
guides" complying with such suggestion.
This handbook is divided into the main topics described in the table of contents:
Table 3 — Handbook structure
Preface It contains general information as preliminary information,

safety recommendation, handbook scope, history, related
documents. Furthermore, it describes the handbook structure
and the customer documentation.
Management of enhanced Describes the management of new features possible through

Configuration File configuration file.
Common Assumption Describes the Switch to equipment ports assignment.
Features supported through Describes features that can be implemented through

Configuration file management configuration files and how to implement them.
Abbreviations The abbreviation list is supplied.
Index Index references are inserted
Customer Documentation It contains info regarding customer opinions collection about

Feedback this document
Safety This section includes all the safety instructions.
General on Customer Documentation

This paragraph describes in general the Alcatel–Lucent Customer Documentation system,
details the association between the product levels and the associated documentation, and
explains Customer Documentation characteristics as well as the policies for its delivery and
updating.
Customer–Independent Standard Customer Documentation

a. Definition
Standard Customer Documentation, referred to hereafter, must be always meant as
plant–independent and is always independent of any Customization.

Plant–dependent and/or Customized documentation, if envisaged by the contract, is

subjected to commercial criteria as far as contents, formats and supply conditions are
concerned.
Plant–dependent and Customized documentation is not described here.
b. Aims of standard Customer Documentation
Standard system, hardware and software documentation is meant to give the
Customer personnel the possibility and the information necessary for installing,
commissioning, operating, and maintaining the equipment according to Alcatel–
Lucent Laboratory design and Installation Dept. choices. In particular:
• the contents of the chapters associated to the software applications focus on the
explanation of the man–machine interface and of the operating procedures
allowed by it;
• maintenance is described down to faulty PCB location and replacement.
• No supply to Customers of design documentation (like PCB hardware design
and production documents and files, software source programs, programming
tools, etc.) is envisaged.
Product levels and associated Customer Documentation

a. Products
A “product” is defined by the network hierarchical level where it can be inserted and
by the whole of performances and services that it is meant for.
E.g. 9500 MPR-E is a product.
b. Product-releases
A ”product” evolves through successive “product–releases”, which are the real
products marketed for their delivery at a certain ”product–release” availability date.
A certain ”product–release” performs more functionalities than the previous one.
E.g. Rel.1.0 and Rel.2.0 are two successive “product–releases” of the same “product”.
A “product–release” comprehends a set of hardware components and at least one
“Software Package” (SWP); as a whole, they identify the possible network
applications and the equipment performances that the specific “product–release” has
been designed, engineered, and marketed for.
c. Configurations and Network Elements
In some cases, a “product–release” includes different possible “configurations”
which are distinguished from one another by different “Network Element” (NE)
types and, from the management point of view, by different SWPs.
d. SWP releases, versions, and CD–ROMs
• Each SWP is distributed by means of a specific SWP CD–ROM.

• A SWP is identified by its “Denomination”, “P/N” (Part Number) and “CS”

(Change Status), that are printed on the CD–ROM’s label:
• the first and second digits of the “Denomination” (e.g. 2.0) correspond to
the “HW product–release” number;
• the third digit of the of the “Denomination” (e.g. 2.0.2) identifies the
Version Level of the SWP.
• A SWP with new Version Level, providing main features in addition to those of
the previous Version Level SWP, is distributed by means of a SWP CD–ROM
having new “Denomination”,“P/N” (Part Number), and “CS” restarting from
01
• A SWP patch version, if any, is created to correct SW bugs, and/or to add minor
features, and is distributed by means of a SWP CD–ROM, that can be
identified:
• by the same “P/N” of the former CD–ROM, but with an incremented
“CS” number (e.g.CS=02 instead of previous CS=01)
• or by a new “P/N”, and “CS” restarting from 01.
Handbook Updating
Each handbook is identified by:
• the name of the "product–release" (and "version" when the handbook is applicable to
the versions starting from it, but not to the previous ones),
• the handbook name,
• the handbook Part Number,
• the handbook edition (usually first edition=01),
• the handbook issue date. The date on the handbook does not refer to the date of print
but to the date on which the handbook source file has been completed and released
for the production.
Changes introduced in the same product–release (same

handbook P/N)
The edition and date of issue might change on future handbook versions for the following
reasons:
• only the date changes (pointed out in the Table of Contents) when modifications are
made to the editorial system not changing the technical contents of the handbook.

• the edition, hence the date, is changed because modifications made concern technical
contents. In this case:
• the changes with respect to the previous edition are listed in History.
• in affected chapters, revision bars on the left of the page indicate modifications
in text and drawings.
Changes concerning the technical contents of the handbook cause the edition number
increase (e.g. from Ed.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same
edition but with the addition of a version character (e.g. from Ed.02 to Ed.02A). Version
character can be used for draft or proposal editions.
Note: Handbooks relevant to software applications (typically the Operator's Handbooks)

are not modified unless the new software version distributed to Customers implies man-
machine interface changes or in case of slight modifications not affecting the
understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the product–release's
"version" marking, they are not replaced in the handbooks related to a subsequent
version, if the screen contents are unchanged.
Supplying updated handbooks to Customers

Supplying updated handbooks to Customers who have already received previous issues is
submitted to commercial criteria.
By updated handbook delivery it is meant the supply of a complete copy of the handbook
new issue (supplying errata-corrige sheets is not envisaged).
Changes due to new product version

A new product version changes the handbook P/N and the edition starts from 01.
In this case the modified parts of the handbook are not listed.
Customer documentation on CD-ROM

In the following by 'CD-ROM' it is meant 'Customer Documentation on CD-ROM'

Contents, creation and production of a CD-ROM

In most cases, a CD-ROM contains in read-only electronic format the documentation of one
product-release(-version) and for a certain language.
In some other cases, the same CD-ROM can contain the documentation of different
product-release(-version)s for a certain language.
As a general rule:
• CD-ROMs for Network Management products do not contain:

• the Installation Guides
• the documentation of system optional features that Customers could not buy
from Alcatel together with the main applicable SW.
• CD-ROMs for Network Elements products do not contain:
• the documentation of system optional features (e.g. System Installation
Handbooks related to racks that Customers could not buy from Alcatel together
with the main equipment).
A CD-ROM is obtained collecting various handbooks and documents in .pdf format.

Bookmarks and hyperlinks make the navigation easier. No additional information is added
to each handbook, so that the documentation present in the CD-ROMs is exactly the same
the Customer would receive on paper.
The files processed in this way are added to files/images for managing purpose and a master
CD-ROM is recorded.
Suitable checks are made in order to have a virus-free product.
After a complete functional check, the CD-ROM image is electronically transferred to the
archive of the Production Department, so that the CD-ROM can be produced and delivered
to Customers.
Use of the CD-ROM

The CD-ROM can be used both in PC and Unix WS environments.
The CD-ROM starts automatically with autorun and hyperlinks from the opened “Index"
document permit to visualize the .pdf handbooks
Other hyperlinks permit to get, from the Technical handbooks, the specific .pdf setting
documents.

In order to open the .pdf documents Adobe Acrobat Reader Version 4.0 (minimum) must
have been installed on the platform.
The CD-ROM doesn't contain the Adobe Acrobat Reader program. The Customer is in
charge of getting and installing it.
ReadMe info is present on the CD-ROM to this purpose.
Then the Customer is allowed to read the handbooks on the PC/WS screen, using the
navigation and zooming tools included in the tool, and to print selected parts of the
documentation through a local printer.
CD-ROM identification
Each CD-ROM is identified:
1. by external identifiers, that are printed on the CD-ROM upper surface:

• the name of the "product-release(s)" (and "version" if applicable)
• a writing indicating the language(s),
• the CD-ROM Part Number),
• the CD-ROM edition (usually first edition=01)
2. and, internally, by the list of the source handbooks and documents (P/Ns and editions)
by whose collection and processing the CD-ROM itself has been created.
CD-ROM updating
The list of source handbook/document P/Ns-editions indicated in CD-ROM identification,
in association with the CD-ROM's own P/N-edition, is also loaded in the Alcatel-
Information-System as a structured list.
Whenever a new edition of any of such handbooks/documents is released in the Alcatel

archive system, a check in the Alcatel-Information-System is made to identify the list of
CD-ROMs that must be updated to include the new editions of these handbooks/
documents.
This causes the planning and creation of a new edition of the CD-ROM.
Updating of CD-ROMs always follows, with a certain delay, the updating of the single
handbooks composing the collection.


1 — Management of flag file on MPR
1.1 — File Name

Flag files are usually empty files without any extension and they must be created on PC
(Windows or Linux or MAC). However, in some cases they could be not empty and have
an extension.
1.2 — Flag File Format

The flag files must be created on PC (Windows or Linux or MAC). The content of the flag
file are usually empty (file size 0 bytes). However, in some cases they could be not empty.
The file must be created with the proper name to enable the specific functionality. The
system is case sensitive.
1.3 — Flag File path in NE File System

From this release the only path for Flag files for NE File System is /home/adm-lc-ng/
config.
1.4 — Flag File upload

The flag files must be uploaded to the Compact Flash (on main CORE when it is active)
using the File Transfer Manager tool, see Appendix section 5.2.
1.5 — How to run a Flag File

Backup & Restore for FlagFile
To run (apply) a flag file, a switch off/on operation is needed.
1.6 — Backup & Restore for FlagFile

Since MPR Rel. 3.1.0, NE Backup&Restore feature is applicable in general to Flag Files.
1.7 — Flag file to enable the Low Latency feature for

TDM2ETH DS1
A specific non-empty Flag File may be used to enable the Low Latency feature for
TDM2ETH DS1 and E1 with differential clock recovery.
Flag file name is: /home/adm-lc-ng/config/pdh_latency.psh
It will contain 3 numbers separated by two blank (space) characters in the following order:
1. Jitter Buffer size [us]

2. QueueSize [number of packets]
3. Payload Size [Bytes]
For example, 470 3 26 stands for:
Jitter Buffer Size is 479us (that is, the initial filling level); Queue Size is 8 packets (2exp3);
Payload size is 26 bytes.
The flag file will affect any TDM2ETH terminated in the NE.
It is mandatory to apply that to NE where DS1 enter and exit (this is not mandatory if the
NE is only traversed by DS1).
The following conditions need to be satisfied:
• Only all synchronous DS1 on a single hop in 1+0 / 1+1 without lag
• Only 1 hop with 30 MHz/128 QAM profile
• Payload size 26
• max jitter buffer (queue size 8 packets)
The user must be aware that reducing Payload length will affect the maximum number of
DS1 that can fit on a specific profile: when the Payload length is reduced the number of
DS1 fitting on a specific profile is reduced accordingly.

Flag file to invert the polarity of housekeeping outputs of the MSS-1
1.8 — Flag file to invert the polarity of housekeeping

outputs of the MSS-1
An empty Flag File /home/adm-lc-ng/config/flag_invert_MSS1_HK_output is available to
invert the polarity of the 3 housekeeping outputs of the MSS-1, changing the polarity from
Close contact when output state is active to Open contact when output state is active.
The Flag File is effective only when applied on MSS-1 equipment.

Flag file to invert the polarity of housekeeping outputs of the MSS-1

2 — Management of enhanced
Configuration File
2.1 — File Name

The configuration file for Ethernet switch inside CORE must be named
enhanced_eth_feature.psh.
The configuration file for Ethernet switch inside MPT-ACC must be named
fullConfig_mptacc.psh. In case of multiple MPT-ACC, this file must contain the
commands for all MPT-ACC.
The configuration file for MOD300 board must be named fullConfig_radio.psh.
The configuration file for Alarm Severity Assignment must be named def_asap4.psh.
The configuration file for SFP 2E1/DS1 Circuit Emulation must be named as follows based
on the optical port used to host the SFP module and CORE slot used:
a. CORE card Main Optical port 5: SFP_2xE1DS1_0_1.psh

b. CORE card Main Optical port 6: SFP_2xE1DS1_0_2.psh
c. CORE card Spare Optical port 5: SFP_2xE1DS1_1_1.psh
d. CORE card Spare Optical port 6: SFP_2xE1DS1_1_2.psh
The configuration files for a radio direction provisioned to have MPT as split-mount ODU
must be named as follow, according to the MSS slot/port used for connection:
MPTcf_x_y.psh where
• x=0, y=0,1,2,3,4,5 identifies the case of MPT connected to Core Main port:
y=0 identifies Port 1 Electrical
y=4 identifies Port 5 Optical

File Format

• x=2,3,4,5,6,7 y=0,1,2,3 identifies the case of MPT connected to MPT Access plug-
in port
In this release, configuration files management is supported only for MPT-xC, no

support for MPT-HL is foreseen. In the rest of the document, the general MPT term
is used, to be meant for this release with limited scope to MPT-xC only.
The configuration file for Ethernet switch inside the EAS plug-in must be named
fullConfig_eas.psh.
In case of multiple EAS cards, this file must contain the commands for all EAS cards.
The configuration file for Ethernet switch inside the EASv2 plug-in must be named
fullConfig_easv2.psh.
In case of multiple EASv2 cards, this file must contain the commands for all EASv2 cards.
When CORE protection is not configured in the system, only configuration files for CORE
Main (a and/or b) should be present in the Flash Card, while, when CORE protection is
present, all configuration files (a and/or b together with c and/or d).
Anyway the presence of CORE Spare configuration files in a not protected configuration
does not create any issue to the system. At the same time, it could be a good approach that
allows the system to be ready to a possible upgrade to CORE protection in case CORE
spare is in a second time.
2.2 — File Format

The configuration files are text files (WordPad cannot be used, NotePad is suggested), they
must be created on PC (Windows or Linux or MAC). The content of the configuration file
is formed by a list of commands each of them using a different line.
Each line can be therefore terminated by:
• Unix-style : [LF] (Line feed, '\n', 0x0A)

• Mac OS: [CR] (Carriage return, '\r', 0x0D)
• Windows: [CR]+[LF]

Configuration File path in NE File System
It is possible to insert comments in Configuration File:
Use # at beginning of the line to write a comment inside the Configuration File, the
comment is 'private'.
It is mandatory to insert an additional "carriage return" as last line of each configuration

file. Configuration File No Restart tool provides an embedded text editor to be used for
configuration file definition.
2.3 — Configuration File path in NE File System

Configuration files path in NE File System is /home/adm-lc-ng/config.
2.4 — Configuration File upload and execution

Configuration files must be uploaded to the Compact Flash (on main CORE when it is
active) via Configuration File No Restart tool (see Appendix section 5.1). Through the
embedded file editor, user can define its own configuration file and save it on local PC
using the proper file name as indicated in File Name. Once all necessary command have
been inserted, by the means of “Add File” button, the user triggers the execution of the file
on the NE and the file is consequently saved inside Compact Flash.
def_asap4.psh and MPTcf_x_y.psh files must be uploaded to the Compact Flash (on main
CORE when it is active) via File Transfer Manager tool (see Appendix section 5.2).
Through the embedded file editor, user can define its own configuration file and save it on
local PC using the proper file name as indicated in File Name. Once all necessary
commands have been inserted, by the means of “Add File” button the user copies the file
from local PC to the NE and the file is consequently saved inside Compact Flash.
To trigger execution of def_asap4.psh a NE restart or NE Power Supply switch off/on is

needed.
To trigger execution of MPTcf_x_y.psh it is needed to cause an MSS-MPT Startup

Sequence.
That could be done by following alternative options:
• performing Cold/Warm Reset command for given MPT

• performing MPT Power Supply switch off/on for given MPT
• disconnecting the Ethernet cable between MPT and MSS
• performing NE Restart or NE Power Supply switch off/on

Configuration File Removal
Since this release, configuration files are part of NE Backup feature.
For MOD300, MPT Access, EAS, and EASv2 card supporting Enhanced configuration
with one file for all provisioned peripheral type, the insertion of a single plug-in also causes
the execution of the whole Configuration file, including the command related to peripheral
that were not plugged-in at that time.
That means that it is assumed that “re-application of commands related to peripherals that
were not plugged-in does not have any traffic impact”.
2.5 — Configuration File Removal

Configuration files can be removed from the Compact Flash (on main CORE when it is
active) via Configuration File No Restart tool.
Selecting the intended file, the user can remove each configuration from the list of file
inside the Flash Card. This action results in file removal from Flash Card only. In order to
disable all configuration file features see Restoring Ethernet switch initial configuration,
Restoring MOD300 initial configuration, and Restoring SFP 2xE1/DS1 configuration.
Simply removing configuration file from Compact Flash does not imply the removal of all
features applied by configuration file itself.
Differently from what has been described above, def_asap4.psh and MPTcf_x_y.psh
removal requires to use the “Delete” button of File Transfer Manager (see Appendix
section 5.2). Also in this case, removal of file doesn't imply the removal of all features.
2.6 — Configuration File update: add a new command/

feature
This procedure can be used every time an additional configuration is needed on top of the
current features applied by configuration file (e.g. one additional VLAN is needed). What
is not possible with this procedure is the complete removal of a specific command/feature,
in such case see Restoring Ethernet switch initial configuration and Restoring MOD300
initial configuration.
The operator is allowed to append a new command on one of the following and already in
use configuration files:
• enhanced_eth_feature.psh
• fullConfig_mptacc.psh
• fullConfig_radio.psh

Configuration File update: remove an existing command/feature
• fullConfig_eas.psh
• fullConfig_easv2.psh
By Configuration File No Restart tool, the user is required to create a new file on local PC
that will include all the new commands. Then, once finished, the user must select from the
list of files already present on the NE, the intended file to be appended and use the “Append
Command” button. This action triggers the execution of the new commands on the NE and
the consequent file update in Compact Flash.
On the contrary, all configuration files for SFP 2xE1/DS1 shall not be appended.
Configuration File No Restart tool does not prevent the operator to add any new command
inside a file already present inside the Flash Card, but it is extremely important to respect
the command order shown in Configuration File basic structure. Not following that scheme
causes a wrong SFP module configuration and the service is not established.
For this reason, SFP configuration files must be always copied locally, removed from flash
card (since CFNR tool requires this), updated with all new commands according to
paragraph Configuration File basic structure and then uploaded as new complete file in the
NE using “AddFile”.
Any configuration file update operation may cause a temporary traffic impact.
Caution: Do not switch the CORE Board after Configuration File upload, until the new
Configuration File is applied.
2.7 — Configuration File update: remove an existing

command/feature
This procedure can be used every time one command or feature must be removed from the
system. In order to remove a command or feature included in the following files:
• enhanced_eth_feature.psh
• fullConfig_radio.psh
• MPTcf_x_y.psh
It is necessary to follow the procedure described below:

Restoring Ethernet switch initial configuration
1. restore the initial configuration of the switch or radio (see Restoring Ethernet switch
initial configuration, Restoring MOD300 initial configuration, and Restoring MPT
initial configuration).
2. upload a new configuration file if necessary according to the procedure described in
section Configuration File upload and execution.
This procedure does not apply to SFP 2xE1/DS1 configuration files. Whenever the operator
needs to remove one of the two tributaries or change a parameter to an existing one (e.g.
change the VLAN ID), it is required the complete configuration file(s) removal (see
Configuration File Removal) and the upload of the new configuration file(s) according to
paragraph Configuration File upload and execution.
Note: Do not switch the CORE Board after Configuration File upload, until the new
Configuration File is applied.
2.8 — Restoring Ethernet switch initial configuration

To restore the initial configuration of CORE, EAS, EASv2 and MPT-ACC (the current
configuration without any setting resulting from CF), the procedure includes the following
steps to be performed by Configuration File No Restart tool:
1. CORE, EAS, EASv2 and MPT-ACC CFs must be removed from flash card (see
Configuration File Removal);
2. CORE, EAS, EASv2 and MPT-ACC “restoring CF” (see below) must be executed on
the NE (see Configuration File upload and execution);
3. CORE, EAS, EASv2 and MPT-ACC “restoring CF” must be removed from flash card
(see Configuration File Removal).
4. After this, the user must perform an NE restart by CT/NMS to completely remove the
effect of the configuration file.
After this, the user must perform a NE restart by CT/NMS to completely remove the effect
of configuration file.
2.8.1 — Restoring “enhanced_eth_feature.psh” configuration

file:
#start enhanced configuration file
setreg 00500001 0001

Restoring Ethernet switch initial configuration
#end enhanced configuration file
2.8.2 — Restoring “fullConfig_mptacc.psh”,

fullConfig_eas.psh, and fullConfig_easv2.psh configuration
file:
setreg S0300300 0000
In case the system is equipped with multiple MPT-ACC/EAS/EASv2 plug-in, in order to

restore the original configuration of the MPT-ACC/EAS/EASv2 plug-in, the command
above have to be replicated for all MPT-ACC/EAS/EASv2 setting the "S" nibble to the
right slot number:
S=0x2 if the Radio Board is inserted into slot 3 (first column, second row)
S=0x3 if the Radio Board is inserted into slot 4 (second column, second row)
S=0x4 if the Radio Board is inserted into slot 5 (first column, third row)
S=0x5 if the Radio Board is inserted into slot 6 (second column, third row)
S=0x6 if the Radio Board is inserted into slot 7 (first column, fourth row)
S=0x7 if the Radio Board is inserted into slot 8 (second column, fourth row)
If an AUX card is equipped, an additional command must be added into the

enhanced_eth_feature.psh file. So for this peculiar case only, the CORE restoring
configuration file is the one reported here below.
2.8.3 — Restoring “enhanced_eth_feature.psh” configuration

file (AUX card case):
setreg 00500001 0001
setreg S0300300 0001

Restoring SFP 2xE1/DS1 configuration
Where S nibble assumes the following value based on AUX card slot position:
S=3 if the AUX Board is inserted into slot 4 (second column, second row)
S=7 if the AUX Board is inserted into slot 8 (second column, fourth row)
2.8.4 — Restoring MOD300 initial configuration

For this board, in order to restore card's initial configuration, it is necessary to apply a
specific configuration file for each feature reported in each feature chapter.
The procedure includes the following steps to be performed by Configuration File No

Restart tool:
1. fullConfig_radio.psh must be removed from flash card (see Configuration File

Removal);
2. per feature “restoring CF” must be executed on the NE (see Configuration File upload
and execution);
3. “restoring CF” must be removed from flash card (see Configuration File Removal).
2.9 — Restoring SFP 2xE1/DS1 configuration

SFP module configuration can be easily restored disabling at CT/NMS the optical port,
paying attention to the fact that, if any cross-connection is in place, the user shall remove
first all cross-connections and then disable the port. The port disable operation restores
automatically the SFP initial configuration clearing the previous setting of all tributaries.
Enabling again the port, if any SFP configuration file is present in the Flash Card, the
configuration is applied automatically by the system based on the new commands inside
the file.
2.10 — Restoring MPT initial configuration

The configuration to be restored on MPT is the joiunt result of MPT “default” configuration
and the MSS “default” configuration that is applied to MPT during the MSS-MPT startup
sequence and persistently saved into MPT database (while Enhanced configuration is not
persistent).

Behavior during SW restart
In order to restore this MPT default configuration, after deletion of the file from NE
Compact Flash, in order MPT to apply to HW its persistent configuration, a cold restart of
MPT is needed.
In the current release MPT cold restart can be achieved only as result of NE or MPT power
switch off/on (the latter is available to management system in case of connection to MPT
Access plug-in).
If the above procedure is not possible or wanted, the alternative solution for restore of MPT
default configuration is to explicitly put it into the MPT config file and then trigger its
execution (see section Configuration File upload and execution).
2.11 — Behavior during SW restart

A traffic hit may occur during NE restart.
2.12 — SW package activation

Since the SW package activation implies a EC software reset, the configuration file will be
applied again, no specific operations are required.
2.13 — Behavior in CORE protection

The configuration file is loaded and applied on CORE Spare too. The file is uploaded from
CORE Main compact flash. This is the normal behavior in case of CORE protection since
CORE Main and CORE Spare are kept aligned in terms of configuration. So, as soon as a
CORE switch occurs, the CORE becoming active will have enhanced features already
configured.
At the same time, a different behavior is supported for 2xE1/DSI SFP since there are
dedicated configuration file for CORE Main and CORE Spare (see File Name)
When CORE protection is not configured in the system, only SFP configuration file(s) for
the Main CORE card must be present in the Flash Card. On the contrary, when CORE
protection is present, all SFP configuration files for both Main and Spare must be present.
2.14 — Behavior in Radio protection

Behavior in Ethernet Link Aggregation
Regarding the configuration file for MOD300, MPT-ACC, EAS, and EASv2 boards
(fullConfig_radio.psh, fullConfig_mptacc.psh, fullConfig_eas.psh, and
fullConfig_easv2.psh), the mated Board is managed as an independent Radio Board. In
this case the radio configuration file must contain the configuration of both radio cards.
Additionally, even all commands inserted into enhanced_eth_feature.psh file have to be
duplicated for both Main and Spare ports in case of radio in protection.
The same principle applies for MPT. In this case the user has to provide a Configuration
file MPTcf_x_y.psh for each radio channel, where x,y identifies MSS slot/port the MPT is
connected to. The content of the these two files must be the same.
2.15 — Behavior in Ethernet Link Aggregation

All commands to be applied to an Ethernet LAG inserted into enhanced_eth_feature.psh
file have to be replicated for all ports members of the LAG since all ports are managed
independently.
2.16 — Behavior in Radio Link Aggregation

All commands to be applied to a radio LAG inserted into fullConfig_mptacc.psh/
fullConfig_eas.psh file have to be duplicated for the two ports members of the radio LAG
since all ports are managed independently. Additionally, even all commands inserted into
enhanced_eth_feature.psh file have to be duplicated for both ports facing MPT-ACC/
EAS.
2.17 — TMN enabled on ETH4 port

Whenever CORE ETH4 port is configured for TMN, the related CORE Ethernet interface
ge20 shall not be used in any command referenced in this document.
2.18 — Software package upgrade

See editions of this document related to previous 9500 MPR release.

List of portable/unportable features from previous releases
2.19 — List of portable/unportable features from

previous releases
Table 2.1 shows the list of portable features from previous MPR releases.
Table 2.1 — Portable features from previous releases
Feature
MPR-E 1.2.2
MPR-E 1.3.0
MPR-E 1.4.0
MPR-E 3.0.0
MPR-E 3.2.0
MPR-E 3.4.0
MPR-E 4.1.0
MPR-E 5.0.0
MPR-E 5.2.0
2.1.0
3.1.0
3.3.0
4.0.0
4.2.0
5.1.0
QINQ YES YES YES YES YES YES n.a. n.a n.a
Autonegotiation on SFP port n.a. YES YES n.a. n.a. n.a. n.a. n.a n.a
VLAN swap YES YES YES YES YES YES YES n.a n.a
Out of Range VLAN swap n.a. YES YES YES YES YES YES YES YES
VLAN swap and dot1p n.a. YES YES YES YES YES YES YES YES
Remarking for ATM PW
Service
VLAN swap and forwarding n.a. YES YES YES YES YES YES YES YES
for “local ATM switch"
Port Based Rate Limiting n.a. n.a. YES YES YES n.a. n.a. n.a. n.a
Storm Control n.a. n.a. YES YES YES n.a. n.a. n.a. n.a
Access Control List n.a. n.a. YES YES YES YES YES YES YES
Per VLAN rate limiting n.a. n.a. YES YES YES n.a. n.a. n.a n.a
Ethernet Switch Scheduler YES YES YES YES n.a. n.a. n.a. n.a n.a
Setting
MOD300 Scheduler Setting NO YES YES YES n.a. n.a. n.a. n.a n.a
Ethernet Switch 802.1p NO NO NO NO n.a. n.a. n.a. n.a n.a

Mapping to Queues
MOD300 802.1p Mapping to YES YES YES YES n.a. n.a. n.a. n.a n.a
Queues
Ethernet Switch Mapping NO NO NO NO n.a. n.a. n.a. n.a n.a
DiffServ to Queues for IPv4
frames

Relevant notes
Table 2.1 — Portable features from previous releases (Continued)
MOD300 Mapping DiffServ to YES YES YES YES n.a. n.a. n.a. n.a n.a
Queues for IPv4 frames
Ethernet Switch IPv6 QoS NO NO NO NO n.a. n.a. n.a. n.a n.a
support with flexible
mapping traffic class to
queues
MOD300 IPv6 QoS support YES YES YES YES n.a. n.a. n.a. n.a n.a
with flexible mapping traffic
class to queues
SFP 2E1/DS1 CIRCUIT n.a. n.a. n.a. YES YES YES YES YES YES
EMULATION
ASAP n.a. n.a. n.a. YES YES YES YES YES YES
QoS based on MPLS TC n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. YES
Each not portable Ethernet feature can be easily adapted following the rules described this
document. Once a configuration file, already in use in a previous release, has been adapted
it is possible to upgrade the system with MPR 5.x.
2.20 — Relevant notes

Ethernet Connectivity Fault Management is not for supported for any VLAN created by
configuration file. This feature is supported only for services created by CT/NMS and CLI.
If a Core Port is provisioned as Radio Port, the applicable Enhanced Configuration is the
one that is applicable as Radio Port, not as User Port.
Unless otherwise stated, Enhanced Configuration features related to User Port are
applicable to EAS Ports and EASv2 Ports provisioned as User Ports.
Enhanced Configuration features are applicable to EAS Ports or EASv2 Ports provisioned
as Radio Ports only for what regards VLAN management (as it applied in case of MPT-
ACC prior to MPR 3.1.0).
2.21 — List of removed features

No removed features with respect to those available in 9500 MPR R5.1.0 Enhanced
Configuration.

Backup & Restore for Configuration Files
2.22 — Backup & Restore for Configuration Files

Since MPR Rel. 3.1.0, NE Backup&Restore feature is applicable to following
Configuration Files:
• enhanced_eth_feature.psh.
• fullConfig_radio.psh.
• def_asap4.psh.
• SFP_2xE1DS1_x_y.psh with x=0,1 for Core Main/Spare, y=1,2 for Optical Port 5/
6 respectively
• MPTcf_x_y.psh with
• x=0, y=0,1,2,3,4,5 identifies the case of MPT connected to Core Main port
• x=2,3,4,5,6,7 y=0,1,2,3 identifies the case of MPT connected to MPT Access
plug-in port

Backup & Restore for Configuration Files

3 — Common Assumption
3.1 — Switch to equipment ports assignment

Switch to equipment ports assignment
Figure 3.1 — Equipment ports
Table 3.1 — Port assignment
CORE MPT-ACC EAS EASv2
Port Port Port Port Port Port Port Port

Name Number Name Number Name Number Name Number
ge11 12 ge5 6 ge5 6 ge5 6

MPT-ACC, EAS and EASv2 switch command definition
Table 3.1 — Port assignment (Continued)
CORE MPT-ACC EAS EASv2
ge12 13 ge6 7 ge6 7 ge6 7
ge13 14 ge7 8 ge7 8 ge7 8

ge14 15 ge8 9 ge8 9 ge8 9
ge15 16 ge9 10 ge9 10 ge9 10
ge16 17 ge10 11 ge10 11

ge17 18 ge11 12 ge17 18
ge18 19 ge12 13 ge18 19
ge19 20 ge4 5 ge0 1
ge20 21 ge0 1 ge1 2
ge5 6 ge1 2 ge3 4
ge6 7 ge4 5
ge20 21
MSS-8 shelf description.
Table 3.2 — MSS-8 shelf
Slot 1 Slot 2
Slot 3 Slot 4
Slot 5 Slot 6
Slot 7 Slot 8
MSS-4 shelf description.
Table 3.3 — MSS-4 shelf
Slot 1 Slot 2
Slot 3 Slot 4
3.2 — MPT-ACC, EAS and EASv2 switch command

definition
SFP 2E1/DS1 command definition
All the commands applicable to Core Switch User Ports are applicable to EAS User Ports
and EASv2 User Ports.
Conversely, not all the commands reported inside this guide are valid for MPT-ACC
switch.
For this reason, all commands applicable for MPT-ACC will be expressively indicated into
the relative paragraph later on in the document. When not indicated, the command is
intended to be applicable for CORE, EAS, or EASv2 only and so it must be inserted into
“enhanced_eth_feature.psh”, “fullConfig_eas.psh”, or “fullConfig_easv2.psh” only.
In order to apply a command to MPT-ACC, EAS, or EASv2 switch, it is not enough to

insert it into "fullConfig_mptacc.psh" configuration file.
The following syntax has to be respected based on MPT-ACC, EAS or EASv2 slot position.
bcm <value>: <command> <par1=value> <par2=value> …
where value corresponds to MPT-ACC slot decremented by one.
Command example:
bcm 2: vlan create 100 pbm=ge5,ge9
This example creates VLAN 100 inside MPT-ACC on ge5 and ge9 interfaces.
Moreover, some of the features illustrated in this guide require a preliminary configuration
not only for CORE Ethernet switch, but also for MPT-ACC switch, EAS switch or EASv2
switch. So, it is required to specify the correct SLOT number MPT-ACC/EAS/EASv2 is
lodged for each preliminary configuration command. In case of multiple MPT-ACC/EAS/
EASv2, the preliminary configuration must be replicated for all MPT-ACC/EAS/EASv2
present into the system changing the SLOT number accordingly.
3.3 — SFP 2E1/DS1 command definition

SFP 2xE1/DS1 configuration file contains commands to write device internal registers
whose address is based on the SFP position with the chassis.
Each command is preceded by the keyword “setreg” and followed by a 32 bits address and
a single byte value like in the following example:
e.g. setreg YX50000F 00
Nibble Y and X depends on the slot position (CORE Main/Spare) and port (optical 5/6) of
the module:

MPT Configuration File and command definition
Y=0: used inside SFP_2xE1DS1_0_1.psh and SFP_2xE1DS1_0_2.psh files used to

contain respectively the configuration of SFP inside CORE Main optical port 5 and port 6
Y=1: used inside SFP_2xE1DS1_1_1.psh and SFP_2xE1DS1_1_2.psh files used to

contain respectively the configuration of SFP inside CORE Spare optical port 5 and port 6
X=3: used inside SFP_2xE1DS1_0_1.psh and SFP_2xE1DS1_1_1.psh files used to

contain the configuration of SFP insert in optical port 5 of respectively CORE Main and
Spare
X=4: used inside SFP_2xE1DS1_0_2.psh and SFP_2xE1DS1_1_2.psh files used to

contain the configuration of SFP insert in optical port 6 of respectively CORE Main and
Spare
So, assuming SFP plugged into CORE Main optical port 5 and no CORE protection
configured, the following could be an example of register write operation:
setreg 0350000F 00 to be inserted into SFP_2xE1DS1_0_1.psh:
As an additional example, assuming SFP plugged into CORE Main optical port 5 and
CORE protection configured, the following could be an example of register write
operations:
setreg 0350000F 00 to be insert into SFP_2xE1DS1_0_1.psh
setreg 1350000F 00 to be insert into SFP_2xE1DS1_1_1.psh
3.4 — MPT Configuration File and command definition

Commands for MPT Configuration file MPTcf_x_y.psh must follow the following syntax:
MAP, <<byte stream for MAP message>> [LineTermination]
<<byte stream for MAP message>> is the sequence of ASCII characters representing
hexadecimal coding of MAP message octets with space separator
[LineTermination]= see File Format
The general format for MAP message is the following:

MPT Configuration File and command definition
Figure 3.2 — Map message format
Message Class = 0x04 (Telecommand Request)
Message Identifier = identifies the message used for specific configuration
Reserved = 0x00 (reserved)
Payload Size = size in bytes of the message payload
Payload = identifies the specific configuration setting
See File Format for other applicable constraints:
• it is mandatory to insert an additional “carriage return” as last line of each

configuration file.
• it is possible to insert comments in Configuration File by adding # at beginning of the
line
3.4.1 — Example
#Configure QoS Classification
MAP, 4 6c 0 0 1 1
4 : message class = “Telecommand request”
6c : message identifier = “Configure QoS classification”
0 : reserved.
0 1 : Payload size = 1 byte.
1 : payload = “802.1p” (classification is based on 802.1p information)

4 — Features supported through
Configuration file management
4.1 — Autonegotiation on SFP port
4.1.1 — Autonegotiation managed since MPR 3.1 release

Since MPR 3.1 release the enable/disable of autonegotiation for Core Optical ports will be
managed from CT/NMS, with the autonegotiation enabled as default.
As exception to general rule asserting that migration of features managed by Configuration

file is to be manually done by operator, requires for this feature to support an automatic
migration procedure performed by the NE itself. NE Database and MIB will be therefore
aligned to the configuration of auto-negotiation for Core SFP as resulting from file
enhanced_eth_feature.psh.
The configuration described in this section therefore is no more applicable. It is kept only
for information purpose.
4.1.2 — Overview
Auto-Negotiation configuration on SFP ports is handled by a single register according to
Figure 4.1.
Figure 4.1 — Autonegotiation configuration on SFP ports
y=0 CORE Main y=1 CORE Spare

Autonegotiation on SFP port
a=0 Flow Control disable, 01 Flow Control Enable on optical port 6
b=0 AN enabled, 1 AN disabled on optical port 6
c=00 Flow Control disable, 01 Flow Control Enable on optical port 5
d=0 AN enabled, 1 AN disabled on optical port 5
The setting of this register has to be inserted inside enhanced_eth_feature.psh.
4.1.3 — Disable Auto-Negotiation example

In order to disable Auto-Negotiation on SFP ports, the following commands are required
inside configuration file for Ethernet switch named enhanced_eth_feature.psh.
On CORE Main, disable Auto-Negotiation on optical port 5 (flow control disabled):
setreg 00500065 00000001
On CORE Main, disable Auto-Negotiation on optical port 6 (flow control disabled):
setreg 00500065 00000008
On CORE Main, disable Auto-Negotiation on both optical ports 5 and 6 (flow control
disabled):
setreg 00500065 00000009
Note: in order to apply the command, it is required to disable and enable again the port
by CT/NMS once the configuration file has been applied.
4.1.4 — Re-Enable Auto-Negotiation example

In order to enable again Auto-Negotiation on SFP ports, the following commands are
required inside configuration file for Ethernet switch named enhanced_eth_feature.psh.
This command must replace the disable commands of Disable Auto-Negotiation example.
On CORE Main, enable Auto-Negotiation on both optical ports 5 and 6 (flow control
disabled):
setreg 00500065 00000000

OUT OF RANGE VLAN SWAP
On CORE Main, enable Auto-Negotiation on optical port 6 keeping port 5 with Auto-
Negotiation disabled (flow control disabled):
setreg 00500065 00000001
On CORE Main, enable Auto-Negotiation on optical port 5 keeping port 6 with Auto-
Negotiation disabled (flow control disabled):
setreg 00500065 00000008
Note: in order to apply the command, it is required to disable and enable again the port
by CT/NMS once the configuration file has been applied.
4.2 — OUT OF RANGE VLAN SWAP
4.2.1 — Background
MPR official releases provides full 802.1Q feature only for VLAN in range [2:4080]. For
some specific network condition, it may be required to have MPR in charge to transport
traffic having VLAN ID out of this range. It is possible to admit out of range VLANs inside
MPR following the guidelines described inside this chapter.
The scenario considered in this chapter is the one shown in Figure 4.2.
Figure 4.2 — Out of range VLAN swap

The MPR is used to connect two already existing 802.1Q environments that use a VLAN
out of MPR range. All MPR equipment inside the MPR network should be configured in
802.1Q bridge mode and fully provisioned by CT/NMS. Only two MPRs require
configuration file in order to admit the out of range VLAN and are indicated as Gateway 1
and Gateway 2. These two Gateways can emulate the same behavior obtainable with
802.1Q bridge mode.
In this condition, configuration on Gateway MPRs has to be provisioned by configuration

file for the following purpose:
• VLAN creation/membership
• port role definition
• port VLAN assignment
• port parameters
• VLAN SWAP rules
This configuration has an intrinsic limitation and cannot accept more than 1000 different
VLANs on UNI ports (sum of UNI VLANs).
4.2.2 — Preliminary configuration

In order to manage the VLAN SWAP capabilities by configuration file the NE must be
configured in 802.1D bridge mode.
This feature can be applied to EAS Ports and EASv2 ports.
Preliminary configuration of “enhanced_eth_feature.psh”:
# discard all traffic on all user ports.
bcm port ge5,ge6,ge17-ge20 discard=all
# apply port priority
bcm vlan port ge5,ge6,ge17-ge20 useinnerpri 0
bcm fp entry remove 1
Preliminary configuration of “fullConfig_eas.psh”:
# discard all traffic on all EAS Electrical User ports
bcm <SLOT-1>: port ge5-ge8 discard=all

bcm bcm <SLOT-1>: vlan port ge5-ge8 useinnerpri 0
# configure backplane port of EAS as NNI
bcm <SLOT-1>: dtag mode ge4 internal
# configure Radio ports of EAS as NNI (if SFP ports are provisioned as radio ports).
bcm < SLOT-1>: dtag mode ge9 internal
If a EAS SFP Port is instead provisioned as User Port, then the same command applied to
Electrical Ports has to be used.
Preliminary configuration of “fullConfig_easv2.psh”:
# discard all traffic on all EASv2 Electrical User ports
bcm <SLOT-1>: port ge5-ge8 discard=all
bcm bcm <SLOT-1>: vlan port ge5-ge8 useinnerpri 0
# configure backplane port of EASv2 as NNI
# configure Radio ports of EASv2 as NNI (if SFP ports are provisioned as radio ports).
# configure Master Ports of EASv2 as NNI

If a EASv2 SFP Port is instead provisioned as User Port, then the same command applied
to Electrical Ports has to be used.
Preliminary configuration of “fullConfig_mptacc.psh”:
# configure all ports as NNI.
4.2.3 — Port configuration

In this specific network condition, it is required to configure all CORE ports facing
MOD300 Radio Board, MPT-ACC and AUX board as network to network interface (NNI).
The same configuration must be applied to all user Ethernet ports that are not receiving out
of range VLANs, defining them too as network to network interface (NNI). On the other
side, all user ethernet ports receiving out of range VLANs have to be configured as user to
network interface (UNI).
bcm dtag mode <pbm> <type>
• <pbm>: list of possible ports; Core Switch range: ge5, ge6, ge17, ge18, ge19, ge20
and each slot lodging a MOD300 Radio Board/EAS/EASv2 or AUX board; EAS
switch range and EASv2 switch range: see Switch to equipment ports assignment;
mandatory.
• <type>: it is the port definition that can be internal for NNI ports or external for UNI
ports; mandatory.
Note: on CORE ports from ge11 to ge16 refers to MSS slots; this command must not be
applied to ports toward slot where a PDH and ASAP cards is lodged. Applying this command
toward PDH or ASAP slots will destroy all the E1/ATM traffic.
In case of EAS or EASv2, the <slot-1> number must be added to the above command.
4.2.3.1 — User UNI port specific commands
For all user ethernet ports configured as UNI, requires the following commands.

bcm vlan port <pbm> translateingress 1
bcm vlan port <pbm> translateegress 1
bcm vlan port <pbm> translateingressmissdrop 1
bcm vlan port <pbm> useinnerpri 1
bcm port <pbm> prio=<n>
bcm pvlan set <pbm> <vid>
• <pbm>: user UNI port bitmap; Core switch range: ge6, ge17, ge18, ge19, ge20; EAS
switch range and EASv2 switch range: see section Switch to equipment ports
assignment; mandatory.
• <vid>: integer number used as VLAN ID; range: 2-4080; mandatory. Vid must have
been created previously and all ports in <pbmp> must belong to that VLAN.
• <n>: 802.1p priority value for incoming untagged frames; range [0:7]; mandatory;
Note: The bcm port command implies always a switch off/on of the involved port; so,
anytime the configuration file will be applied a traffic hit will always occurs on the
involved port.
In case of EAS or EASv2, the <slot-1> number must be added to the above command.
4.2.3.2 — User NNI port specific commands
For all user ethernet ports configured as NNI, requires the following commands.
bcm port <pbm> prio=<n> discard=<type> vf=1
bcm pvlan set <pbm> <vid>
• <pbm>: user NNI port bitmap; range: Core switch ge5, ge6, ge17, ge18, ge19, ge20;
EAS switch range and EASv2 switch range: see section Switch to equipment ports
assignment; mandatory.
• <vid>: integer number used as VLAN ID; range: 2-4080; mandatory. Vid must have
been created previously and all ports in <pbmp> must belong to that VLAN.
• <n>: 802.1p priority value for incoming untagged frames; range [0:7]; mandatory;
• <type>: possible vale are tag|untag|none in order to drop respectively tagged,
untagged or none frames; mandatory.
Note: The bcm port command implies always a switch off/on of the involved port; so,
involved port.

In case of EAS or EASv2, the <slot-1> number must be added to above command.
4.2.4 — VLAN Table management

This command applies to both CORE and MPT-ACC switches' interfaces.
In order to manage the VLAN Table the following command should be used:
bcm vlan create <id> portbitmap=<pbmp> untagbitmap=<ubmp>
• <id>: id is a integer number used as VLAN ID; range: 2-4080. The VLAN IDs
already defined as crossconnect internal flows (i.e. TDM2TDM, TDM2ETH, ATM)
cannot be used; mandatory.
• <pbmp>: pbmp is a list of possible ports members of VLAN <id>;
a. CORE range: ge5, ge6, ge11-ge20; mandatory.
b. MPT-ACC range: ge5, ge6, ge7, ge8, ge9; mandatory.
c. EAS range: see Switch to equipment ports assignment for the list of backplane
and User/Radio Ports.
d. EASv2 range: see Switch to equipment ports assignment for the list of
backplane and User/Radio Ports.
• <ubmp>: pbmp is a list of possible ports members of VLAN <id> that forward the
frame untagged;
a. CORE range: ge5, ge6, ge17, ge18, ge19, ge20; optional.
b. MPT-ACC range [none]; not applicable.
c. EAS range: see Switch to equipment ports assignment for the list of User Ports;
optional.
d. EASv2 range: see Switch to equipment ports assignment for the list of User
Ports; optional.
Note: on CORE ports from ge11 to ge16 refers to MSS slots; this command must not be
applied to ports towards slot where a PDH, AUX and ASAP cards are lodged.
Note: This configuration has an intrinsic limitation and cannot accept more than 1000
different VLANs on UNI ports (sum of UNI VLANs).
In case of MPT-ACC/EAS/EASv2, the <slot-1> number must be added to the above

command.

4.2.5 — Admit out of range VLAN

The following commands are required in order to admit a single out of range VLAN inside
MPR.
bcm vlan translate delete port=-10 oldvlan=<oldVLAN>
bcm vlan translate egress delete port=-10 oldvlan=<oldVLAN>
bcm vlan create <newVlanID> pbm=<pbm>
bcm vlan translate add port=21 oldvlan=<oldVLAN> newvlan=<newVLAN>

prio=<newPrio>
bcm vlan translate egress add port=21 oldvlan=<newVLAN> newvlan=<oldVLAN>

prio=<newPrio>
• <pmb>: port bitmap associated to the newVlanID; AUX, PDH and ASAP card must
not be included into this bitmap; Core switch range ge11-ge20; EAS switch range and
EASv2 switch range: see Switch to equipment ports assignment; mandatory.
• <portNum>: user port number which is receiving out of range VLAN; Core Switch
range: 6,7, 18,19,20,21; EAS switch range and EASv2 switch range: see Switch to
equipment ports assignment; mandatory.
• <oldID>: incoming out of range VLANID to be swapped; range [4081:4094];
mandatory.
• <newID>: new VLANID used to remark the incoming out of range VLANID; range
[2:4080]; mandatory.
• <n>: priority value used to replace the incoming 802.1p bits; -1 value is used in order
to not replace the incoming frame priority; mandatory.
4.2.6 — Manage in range VLAN on user UNI

On each user UNI ports, the following command are required for each incoming VLANs
in range [2:4080].
bcm vlan translate add port=<portNum> oldvlan=<vlanID> newvlan=<vlanID> prio=-1
bcm vlan translate egress add port=<portNum> oldvlan=<vlanID> newvlan=<vlanID>

prio=-1
• <portNum>: user port number which is receiving out of range VLAN; Core switch
range: 6,7, 18,19,20,21; EAS switch range and EASv2 switch range: see Switch to
equipment ports assignment; mandatory.
• <vlanID>: UNI incoming/outgoing VLANID; range [2:4080]; mandatory.

Note: This configuration has an intrinsic limitation and cannot accept more than 1000
different VLAN on UNI ports (sum of UNI VLANs).
4.2.7 — User UNI Port enable command

The following command enables UNI user Ethernet port in order to receive/forward traffic.
bcm port <pbm> discard=none
• <pbm>: pbmp is a list of possible ports; Core switch range: ge5, ge6, ge17, ge18,
ge19, ge20; EAS switch range and EASv2 switch range: see Switch to equipment
ports assignment; mandatory.
Note: The above command implies always a switch off/on of the involved port; so,
involved port.
4.2.8 — Example of configuration for VLAN 4092 Swap

Below it is reported an example, in order to admit VLAN 4092 on user Ethernet port 4 of
both MPR Gateway 1 and Gateway 2.
Gateway 1 NE configuration:
• MOD300 card inside slot 4 (ge11)

• User Ethernet port 1 and 2 are receiving in range VLANs
Gateway 2 NE configuration:
• MOD300 card inside slot 3 (ge14)

• User Ethernet port 1 and 2 are receiving in range VLANs
4.2.8.1 — Content of “enhanced_eth_feature.psh” for Gateway 1
#start preliminary configuration
bcm port ge5 discard=all

#end preliminary configuration
#Define user ethernet port as NNI
bcm dtag mode ge17 internal
#Define port receiving out of range VLAN as UNI
bcm dtag mode ge20 external
#All radio as NNI
#Admit VLAN4092 as VLAN 1000 (egress+ingress)
bcm vlan translate delete port=-10 oldvlan=4092
bcm vlan translate egress delete port=-10 oldvlan=4092
bcm vlan create 1000 pbm=ge11,ge20
bcm vlan translate add port=21 oldvlan=4092 newvlan=1000 prio=-1
bcm vlan translate egress add port=21 oldvlan=1000 newvlan=4092 prio=-1
#Setup UNI port
bcm vlan port ge20 translateingress 1
bcm vlan port ge20 translateegress 1
bcm vlan port ge20 translateingressmissdrop 1
#Manage in range VLAN on UNI
#VLAN table management (in range VLANs)

bcm vlan create 200 pbm=ge20,ge11 ubm=ge20
#Configure UNI
bcm pvlan set ge20 200
bcm port ge20 prio=7
#Configure NNI
bcm port ge17 vf=1 prio=5 discard=none
#Enable UNI port
bcm port ge20 discard=none
4.2.8.2 — Content of “enhanced_eth_feature.psh” for Gateway 2:
#Define user ethernet port as NNI
#Define port receiving out of range VLAN as UNI
bcm dtag mode ge20 external

#All radio as NNI
#Admit VLAN4092 as VLAN 1000 (egress+ingress)
bcm vlan translate delete port=-10 oldvlan=4092
bcm vlan translate egress delete port=-10 oldvlan=4092
#Setup UNI port
bcm vlan port ge20 translateingress 1
bcm vlan port ge20 translateegress 1
bcm vlan port ge20 translateingressmissdrop 1
#Manage in range VLAN on UNI
#VLAN table management (in range VLANs)
#Configure UNI
bcm port ge20 prio=7
#Configure NNI
bcm port ge17 vf=1 prio=5 discard=none
#Enable UNI port
bcm port ge20 discard=none

VLAN SWAP AND DOT1P REMARKING FOR ATM PW SERVICE
4.3 — VLAN SWAP AND DOT1P REMARKING FOR ATM PW

SERVICE
ATM PW Service is configured by CT/NMS on all MPR NEs, starting from the one where
it is present the native ATM interface (ATM/IMA/E1), with the assignment for each ATM
PW of PW Label value (that must be unique at Service Level) and VLAN ID used for its
transport (it can be shared among several PWs having same CoS and forwarding path).
Moreover, dot1p bit field within VLAN tag of ATM PW frames is used to dynamically
mark them, on the MPR NEs where it is present the native ATM interface (ATM/IMA/E1),
as "Green" (MPR network is committed to reserve bandwidth on each radio interfaces) or
"Yellow" (they can be dropped in case of congestion on any of radio interfaces) as result of
bandwidth profiling resulting from native ATM Traffic Descriptor.
VLAN Swap and dot1p remarking can be provisioned to support inter-working of ATM
PseudoWire Service with IP/MPLS equipment (to support that a special configuration of
all MPR NEs in the network is required).
In short this feature allows to make independent, on the MPR NE interfacing the IP/MPLS
equipment, the ATM PW Service from Ethernet Layer 2 transport used within the overall
MPR network:
• all ATM PW flows egressing MPR network will have the same VLAN ID, which has
been swapped from the several VLAN IDs used by ATM PW flows within MPR
network
• for the opposite direction, all ATM PW flows ingressing MPR network will have the
above common VLAN ID swapped to VLAN IDs used by ATM PW flows on single
PW basis (i.e. according to the PW Label value)
• all ATM PW flows egressing MPR network will have the same 802.1p bit field
remarked according to ATM PW CoS information contained into EXP bit field of
ATM PW Label (removing the "Green" or "Yellow" information)
• for the opposite direction, all ATM PW flows ingressing MPR network will have the
same 802.1p bit field remarked as "Green"
Such operations requires, only for MPR NE interfacing the IP/MPLS equipment, the use of
a dedicated configuration file as described in the following.
Since cross-connection of ATM PW flows is not supported for EAS User ports and EASv2
User ports, this configuration is applicable only to Core User Ports.

4.3.2 — Migration Procedure

The migration procedure is aimed to support migration from release 1.3.0/1.4.0 where
ATMoMPLS protocol stack management with additional MPLS Tunnel Label is enabled
by specific flag file mpls_label_enable.
The presence of this flag file is needed on all NEs where ATMoMPLS frames with Tunnel
Label are transported (e.g. to enable the specific header compression on radio cards).
In addition to that, the procedure allows the define the NE common value of the MPLS
Tunnel Label itself for the NE with ASAP Card(s) (as it is the ASAP Card that add the
MPLS Tunnel Label to all ATM PWs).
In this way the NE DataBase and MIB will be automatically updated without the need of
performing the setting by the NE WebServer as described in Appendix section
ATMoMPLS Protocol Stack Configuration by HTTP interface (MPR WebServer).
A file named MPLS_Migration has to be added in the NE directory /home/adm-lc-ng/

debug like all the other flag file as indicated in Management of flag file on MPR.
The file must contain a single line with the decimal value of the common MPLS Tunnel
Value to be applied by the ASAP Card(s), if any. For example if the MPLS_Migration file
contains the row
5000
the decimal value of MPLS Tunnel Value added by ASAP Card(s), if any, will be 5000 and
in any case the NE in configured to manage ATMoMPLS frames with Tunnel Label.
Warning: Applicable only for release MPR-E 2.1: the file used for migration /home/adm-
lc-ng/debug/MPLS_Migration must be removed after the migration to release MPR-E 2.1
has been performed.

The below described configuration applies only to the MPR NE which is connected by an
Ethernet port to an IP/MPLS equipment.
All ATM PW flow cross-connections (radio to user Ethernet port or ASAP Card to
Ethernet) have to be provisioned by CT/NMS as usual, with assignment of the VLAN IDs
and Peer MAC Address.

This enhanced configuration may overlap for FP Group #4 and rule IDs used with the
feature described in DOT1P ASSIGNMENT BASED ON INCOMING DIFFSERV. It is
up to the user to ensure consistency in case these features are being applied at the same time
(i.e. avoiding creating Group #4 twice and using same IDs).
bcm fp qset clear
bcm fp qset add userdefined 1
bcm fp qset add dstmac
bcm fp qset add srcmac
bcm fp qset add outervlan
bcm fp qset add innervlan
bcm fp qset add inports
bcm fp qset add ethertype
bcm fp qset add dscp
bcm fp qset add dstport
bcm fp group create 4 8 1
Note: this feature is normally intended to be used together with “mpls_label_enable” flag
file (see Management of flag file on MPR).
4.3.4 — Enable 802.1p bit remarking

The following command is needed to enable 802.1p bits remarking for each port involved
in a XC to/from IP/MPLS network:
bcm port <portNum> 1 USE_INCOMING_DOT1P=0
• <portNum>: port involved in the XC to IP/MPLS equipment; range: 6, 7, 12 to 21;

mandatory.

Command example:
bcm port 18 1 USE_INCOMING_DOT1P=0
Assuming to have a ATM PW XC configured on port ge11 and port ge17 (user ethernet
port 1), the previous commands enable 802.1p bits remarking for traffic coming from both
ports.
4.3.5 — VLAN swap and 802.1p remarking for Egress Direction

For each egress user Ethernet port used by each ATM PW flow, all commands described at
paragraphs Egress VLAN swap rule definition and Per CoS 802.1p bit remarking rule
definition must be configured using the same value for parameter n. See Table 4.1 to
choose the right n value on a per port basis.
Table 4.1 — n values on a per port basis
n n
ge6 1 ge19 4
ge17 2 ge20 5
ge18 3
4.3.5.1 — Egress VLAN swap rule definition
The following commands are needed for the common VLAN ID value used to swap the
several VLAN IDs used by ATM PW flows:
bcm vlan create <egrVLAN> portbitmap=<pbmp>
• <egrLAN> is the common VLAN ID used by all ATM PW frames egressing MPR
NE; range[2:4080], do not reuse any already used VLAN ID for XC; mandatory.
• <pbm> is the list of ports involved in ATM PW Cross-connections (e.g user eth,
radio, ASAP); allowed range [ge11:ge20]; mandatory.
bcm vlan translate add port=<egrPortNum> oldvlan=<egrVLAN> newvlan=<egrVLAN>

prio=-1
• <egrLAN> is the common VLAN ID used by all ATM PW frames egressing MPR
NE; mandatory.

• <egrPortNum> user ethernet port number where ATM PW frames will egress MPR
network; range 7, 18,19,20,21; mandatory.
bcm mod EGR_L3_NEXT_HOP <n> 1 intf_num=<egrVLANH>
• <n> vlan swap rule entry; this value is the one referred at paragraph Per CoS 802.1p
bit remarking rule definition, so this two parameters must have the same value; see n
values on a per port basis depending on user ethernet port used; mandatory.
• <egrVLANH>: must be expressed in hex coding; mandatory.
4.3.5.2 — Per CoS 802.1p bit remarking rule definition
For each ATM PW CoS (up to 3 in current release), a 802.1p remarking rule with below
pattern must be added to the configuration file:
bcm fp entry create 4 <ID>
bcm fp qual <ID> ethertype 0x8847 0xffff
bcm fp qual <ID> srcmac data=<NE MAC ADDRESS> mask=fe:ff:ff:ff:ff:ff
bcm fp qual <ID> userdefined 2 <CoS> 0x00000e00
bcm fp action add <ID> l3changevlan <n>
bcm fp action add <ID> priopktnew <egrDot1p>
bcm fp entry install <ID>
• <ID>: rule ID number; range[512:527]; the chosen value should not be shared among
different rules; mandatory.
• <CoS>: CoS value number; see CoS and newdot1p parameters by ATM PW CoS ;
mandatory.
• <NE MAC Address>: MPR NE MAC Address in xx:xx:xx:xx:xx:xx format (HEX);
mandatory.
• <n>: vlan swap rule entry; this value is the one referred at paragraph Egress VLAN
swap rule definition, so this two parameters must have the same value; see n values
on a per port basis depending on user Ethernet port used; mandatory.
• <egrDot1p>: 802.1p bits value to remap in egress direction on a per ATM PW CoS
basis; see the table below; mandatory.
For MPR 3.0.0 release, 3 rules are therefore needed for CRB/UBR+/UBR CoS, Table 4.2
reports the values for above CoS and newdot1p parameters according to ATM PW CoS:

Table 4.2 — CoS and newdot1p parameters by ATM PW CoS
CoS Egress dot1p
CBR 0x00000C00 6
UBR+ 0x00000400 2
UBR 0x00000000 0
4.3.6 — VLAN swap and 802.1p remarking for Ingress Direction

For each VLAN ID used by each ATM PW flow, all commands described at paragraphs
must be configured using the same value for parameter m.
4.3.6.1 — Ingress VLAN swap rule definition
The following commands are needed for all the VLAN values used within MPR network
by ATM PW flows, that will replace the common VLAN received from MPLS equipment.
bcm mod EGR_L3_NEXT_HOP <m> 1 intf_num=<VLANH>
• <m>: vlan swap rule entry; this value is also referred at paragraph Per ATM PW flow
802.1p bit remarking rule definition and, considering a single ATM PW, this value
must be equal to the one used at paragraph Per ATM PW flow 802.1p bit remarking
rule definition; range [6:245]; mandatory.
• <VLANH>: is the VLAN ID associated to the ATM PW flow; must be expressed in
hex coding; mandatory.
4.3.6.2 — Per ATM PW flow 802.1p bit remarking rule definition
For each ATM PW flow, a rule with below pattern must be configured:
bcm fp qual <ID> userdefined 2 <PW Label> 0xfffff000
bcm fp qual <ID> dstmac data=<NE MAC ADDRESS> mask=fe:ff:ff:ff:ff:ff
bcm fp qual <ID> inports <ingPbm> 0x7fffff

bcm fp action add <ID> l3changevlan <m>
bcm fp action add <ID> redirectpbmp <NextPbm>
bcm fp action add <ID> priopktnew <ingDot1p>
• <ID>: unique rule ID number; range[528:767]; the chosen value should not be shared
among different rules; mandatory
• <PW Label>: 0xZZZZZ000, ZZZZZ is the hex coding of 20-bit PW Label value;
mandatory.
• <NE MAC ADDRESS>: MPR NE MAC Address in xx:xx:xx:xx:xx:xx format
(HEX); mandatory.
• <ingPbm>: user ethernet port bitmap where ATM PW frames will ingress MPR
network; see Table 4.5; mandatory.
• <m>: vlan swap rule entry; this value is also referred in Ingress VLAN swap rule
definition and, considering a single ATM PW, this value must be equal to the one
used in Ingress VLAN swap rule definition; range[6:245]; mandatory.
• <NextPbm>: user ethernet port(s) bitmap where ATM PW frames are forwarded to
(e.g. radio/PDH ports in 1+0, or 1+1); see Table 4.4; mandatory.
• <ingDot1p>: 802.1p bits value to remap in ingress on a per ATM PW CoS basis; see
Table 4.3; mandatory.
Table 4.3 — 801.1p bit values to remap in ingress
CoS Ingress dot1p
CBR 0x00000C00 6
UBR+ 0x00000400 4
UBR 0x00000000 4
Table 4.4 — User ethernet port bitmap where ATM PW frames are forwarded
NextPbm NextPbm
ge11 0x001000 ge16 0x020000
ge12 0x002000 ge11+ge14 0x009000
ge13 0x004000 ge12+ge15 0x012000
ge14 0x008000 ge13+ge16 0x024000
ge15 0x010000

Table 4.5 — User Ethernet port bitmap where ATM PW frames ingress the network
ingPbm ingPbm
ge5 0x000060 ge18 0x080000
ge6 0x000080 ge19 0x100000
ge17 0x040000 ge20 0x200000
4.3.7 — Example of configuration for VLAN Swap for ATM PW

Service
Below it is reported an example, with rules related to CBR CoS and 1 ATM PW flow only
having VLAN=1000 XC toward SFP Ethernet port.
4.3.7.1 — Content of “enhanced_eth_feature.psh”:
#Preliminary Configuration
bcm fp qset clear
# Enable 802.1p bits remarking on port ge12 and ge6

#Egress 802.1p bits remarking for ATM PW CBR on port ge6
bcm fp entry create 4 512
bcm fp qual 512 ethertype 0x8847 0xffff
bcm fp qual 512 srcmac data=00:21:05:6E:5A:8A mask=fe:ff:ff:ff:ff:ff
bcm fp qual 512 userdefined 2 0x00000C00 0x00000e00
bcm fp action add 512 l3changevlan 1
bcm fp action add 512 priopktnew 6
bcm fp entry install 512
#Egress VLAN swap rule definition on port ge6
vlan translate add port=7 oldvlan=4080 newvlan=4080 prio=-1
bcm mod EGR_L3_NEXT_HOP 1 1 intf_num=0xFF0
# Ingress 802.1p bits remarking for ATM PW CBR with label=0x80000 forwarded to ge12
bcm fp qual 528 userdefined 2 0x00800000 0xfffff000
bcm fp qual 528 dstmac data=00:21:05:6E:5A:8A mask=fe:ff:ff:ff:ff:ff
bcm fp qual 528 inports 0x000080 0x7fffff
bcm fp action add 528 redirectpbmp 0x2000
#Ingress VLAN swap rule definition
bcm mod EGR_L3_NEXT_HOP 6 1 intf_num=0x3E8

VLAN SWAP AND FORWARDING FOR “LOCAL ATM SWITCH”
4.4 — VLAN SWAP AND FORWARDING FOR “LOCAL ATM

SWITCH”
Ethernet Switch configuration file is needed to support termination of ATM traffic into the
same MPR Node, also know as “Local ATM Switch”, according to the following
characteristics/limitations:
1. ATM traffic switching requires in any case ATM PW termination

2. The only limitation in terms of involved ATM i/f (IMA Groups), is switching is not
possible between ATM i/fs hosted by same ASAP peripheral: VPs/VCs to be
switched must always belong to two ATM i/fs hosted by different ASAP peripherals;
for example it is possible to aggregate the VP/VC belonging to 2 or more different
ATM i/fs, hosted by same ASAP peripheral, towards a single ATM i/f only if the
latter is hosted by a different ASAP peripheral
3. No direct configuration of cross-connections for the ATM PW flow pair is supported,
instead it will be necessary to configure, for each ATM PW flow belonging to the
ATM PW flow pair to be cross-connected, an ATM->Ethernet cross-connection (see
SR ID 8206) towards a given Ethernet port (it can be the same); the Ethernet port(s)
involved in these cross-connections can be used for other traffic, with the only impact
due to bandwidth reservation, if applicable
4. A proper MAC Destination Address has to be configured for each ATM PW: it has
to be different from NE MAC, but since the ATM PW frames are not sent outside the
NE, in principle any other valid MAC value can be used.
The purpose of configuration file is to allow ATM PW flow frame forwarding, without an
external cable if two ports are involved, and the swap between VLAN IDs used by ATM
PW flow pair.
The structure of configuration file is similar to the one used for “VLAN swap and dot1p
Remarking for ATM PW Service”, section VLAN SWAP AND DOT1P REMARKING
FOR ATM PW SERVICE.
For this “Local ATM Switch” feature, however no flag file is foreseen.
In principle this feature can be used on the same NE where “VLAN swap and dot1p
Remarking for ATM PW Service” feature is enabled, but for sure it involves different ATM
PW flows: the “Local ATM Switch” foresees termination at ATM level, while “VLAN
swap and dot1p Remarking for ATM PW Service” is applied at ATMoMPLS traffic.
Since cross-connection of ATM PW flows is not supported for EAS User ports and EASv2
User ports, this configuration is applicable only to Core User Ports.


The same as the one for “VLAN swap and dot1p Remarking for ATM PW Service”. See
section Background.
4.4.3 — VLAN swap and frame forwarding

The following CT/NMS based configuration has to be performed previously:
• ATM PW flow #1, with PWLabel_1, terminated on ASAP Card #1, uses VLAN_1 to
be cross-connected towards Ethernet User port #1, with MAC DA #1.
• ATM PW flow #2, with PWLabel_1, terminated on ASAP Card #2, uses VLAN_2 to
be cross-connected towards Ethernet User port #2, with MAC DA #2.
Port #1 and #2 may be the same port.
MAC DA #1 and MAC DA #2 may be the same one.
On the contrary, VLAN_1 must be different from VLAN_2.
The following commands must be then added to the Core Ethernet Switch configuration
file.
4.4.3.1 — VLAN swap - preliminary definition
The following commands are needed as preliminary definition for the mutual swap of
VLAN ID values VLAN1 and VLAN2 used by the two ATM PW flows.
The first command pair is needed to extend the VLAN to be swapped to the CORE port
connected to ASAP card (the VLAN used by the ATM PW terminated on the other ASAP
Card).
bcm vlan add <VLAN_x> portbitmap=<pbm_y>
bcm vlan add <VLAN_y> portbitmap=<pbm_x>
• <VLAN_x>, <VLAN_y> are the VLAN IDs used by ATM PW flow #x and #y (i.e.
VLAN_1 or VLAN_2). allowed range[2:4080], mandatory.
• <pbm_x>,<pbm_y> are the CORE ports connected to ASAP Card #x and #y (i.e.
ASAP Card #1 or ASAP Card #2 respectively); allowed range [ge11:ge16];
mandatory.
The second command pair is needed to define the related entries in VLAN swap table

bcm mod EGR_L3_NEXT_HOP <n_x> 1 intf_num=<VLAN_xH>
bcm mod EGR_L3_NEXT_HOP <n_y> 1 intf_num=<VLAN_yH>
• <n_x>,<n_y>: vlan swap rule entries; these values are the ones referred at paragraph
VLAN swap and frame forwarding rule definition; mandatory.
• <VLAN_xH>, <VLAN_yH>: VLAN IDs used by ATM PW flow #x and #y, must
be expressed in hex coding; mandatory.
4.4.3.2 — VLAN swap and frame forwarding rule definition
The next list of commands defines the actual rule that identifies ATM PW frames belonging
to ATM PW#x (terminated on ASAP #x), swap their VLAN_x into VLAN_y and forward
it to CORE Ethernet Switch port connected to ASAP Card #y.
bcm fp entry create 4 <ID1>
bcm fp qual <ID1> srcmac data=<DA MAC ADDRESS #1> mask=fe:ff:ff:ff:ff:ff
bcm fp qual <ID1> dstmac data=<NE MAC ADDRESS> mask=fe:ff:ff:ff:ff:ff
bcm fp qual <ID1> outervlan <VLAN_xH> 0x0FFF
bcm fp action add <ID1> l3changevlan <n_y>
bcm fp action add <ID1> redirectpbmp <pbmp_y>
bcm fp entry install <ID1>
• <ID1>: unique rule ID1 number; range[528:767]; the chosen value should not be
shared among different rules; mandatory;
• <VLAN_xH>: VLAN IDs provisioned for ATM PW flow #x; must be expressed in
• <pbmp_y> is the port bitmap, as defined by User Ethernet port bitmap where ATM
PW frames ingress the network, that identifies the CORE port connected to ASAP #y;
• <n_y>: vlan swap rule entry; this value is the one referred at paragraph VLAN swap
- preliminary definition; mandatory.
The next list of commands defines the actual rule that identifies ATM PW frames belonging
to ATM PW#y (terminated on ASAP #y), swap their VLAN_y into VLAN_x and forward
it to CORE Ethernet Switch port connected to ASAP Card #x.
bcm fp entry create 4 <ID2>
bcm fp qual <ID2> srcmac data=<DA MAC ADDRESS #2> mask=fe:ff:ff:ff:ff:ff

bcm fp qual <ID2> dstmac data=<NE MAC ADDRESS> mask=fe:ff:ff:ff:ff:ff
bcm fp qual <ID2> outervlan < VLAN_yH > 0x0FFF
bcm fp action add <ID2> l3changevlan <n_x>
bcm fp action add <ID2> redirectpbmp <pbmp_x>
bcm fp entry install <ID2>
• <ID2>: unique rule ID2 number; range[528:767]; the chosen value should not be
shared among different rules; mandatory;
• <VLAN_yH>: VLAN IDs provisioned for ATM PW flow #y; must be expressed in
• <pbmp_x> is the port bitmap, as defined by User Ethernet port bitmap where ATM
PW frames ingress the network, that identifies the CORE port connected to ASAP #x;
• <n_x>: vlan swap rule entry; this value is the one referred at paragraph VLAN swap
- preliminary definition; mandatory.
4.4.4 — Example of configuration for “Local” ATM Switch

Below it is reported an example of implementation of “Local” ATM Switch.
ATM PW #1 and #2 configuration assumed for local ATM switch
1. ATM PW #1 and #2 are terminated on ASAP #1 and ASAP #2, with below
parameters:
• same E1 and IMA configuration (optional)
• same ATM configuration (VPI,VCI, VP role, TD, etc)
• same PW label
• same cell concatenation configuration
2. For ATM PW #1 terminated on ASAP #1, below Ethernet encapsulation parameters
applies:
• MAC DA = 30:30:30:30:30:30
• MAC SA = NE MAC = 44:44:44:44:44:44
• VLAN ID = 4
3. For ATM PW #2 terminated on ASAP #2, below Ethernet encapsulation parameters
applies:
• MAC DA = 32:32:32:32:32:32
• MAC SA = NE MAC = 44:44:44:44:44:44
• VLAN ID = 5

4. Cross-connection of ATM PW #1 towards CORE port ge17 (ETH1)

5. Cross-connection of ATM PW #2 towards CORE port ge18 (ETH2)
Content of “enhanced_eth_feature.psh”:
# Start preliminary configuration
# same as “VLAN swap and dot1p Remarking for ATM PW Service”
bcm fp qset clear
bcm fp qset add UserDefined 1
bcm fp qset add UserDefined 2
# end preliminary configuration
# Configure VLAN swap table
bcm mod EGR_L3_NEXT_HOP 4 1 intf_num=4
bcm mod EGR_L3_NEXT_HOP 5 1 intf_num=5
# VLAN 5 extended to port ge17
bcm vlan add 5 pbm=ge17
# Entry 114 is used for ATM PW#2 frames, VLAN swap from 5 to 4
bcm fp qual 114 srcmac data=44:44:44:44:44:44 mask=fe:ff:ff:ff:ff:ff

ACCESS CONTROL LIST
bcm fp qual 114 dstmac data=32:32:32:32:32:32 mask=fe:ff:ff:ff:ff:ff
bcm fp qual 114 outervlan 0x0005 0x0FFF
# VLAN 4 extended to port ge18
bcm vlan add 4 pbm=ge18
# Entry 115 is used for ATM PW#1 frames, VLAN swap from 4 to 5
bcm fp qual 115 srcmac data=44:44:44:44:44:44 mask=fe:ff:ff:ff:ff:ff
bcm fp qual 115 dstmac data=30:30:30:30:30:30 mask=fe:ff:ff:ff:ff:ff
bcm fp qual 115 outervlan 0x0004 0x0FFF
bcm fp action add 115 updatecounter lower
4.5 — ACCESS CONTROL LIST

This feature allows to restrict MAC address in MPR network. Enabling this feature all
MAC address not expressively include in the list will be automatically dropped.
This feature can be applied to EAS User Ports and EASv2 User Ports.


ACCESS CONTROL LIST
bcm fp qset clear
bcm fp qset add LookupStatus
bcm port ge5 learn=4
Preliminary configuration of “fullConfig_eas.psh”:
• same as for “enhanced_eth_feature.psh”, with addition of <SLOT-1> in the

command syntax and use of applicable EAS User ports as specified in Switch to
equipment ports assignment.
• same as for “enhanced_eth_feature.psh”, with addition of <SLOT-1> in the

command syntax and use of applicable EAS User ports as specified in Switch to
equipment ports assignment.

ACCESS CONTROL LIST
4.5.2 — Feature activation

bcm fp qual 768 inports <pbm> 0x3fffff
bcm fp qual 768 LookupStatus l2srcstatic=0
bcm fp action add 768 drop
• <pbm>: user ethernet port bitmap where ACL applies to; see Table 4.6; mandatory.
Table 4.6 — User Ethernet port bitmap where ACL applies
pbm Description
ge5, ge6,ge17-ge20 0x3c00c0 All user port
ge5, ge6,ge17-ge19 0x1c00c0 All user port except port 4 (ge20) when used as TMN
ge5-ge12 0x3fc0 All EAS user port (ETH1-ETH4,SFP5-SFP8)
ge5-ge8 0x3c0 EAS Electrical user port (ETH1-ETH4)
ge5-ge10, ge17-ge18 0x180fc0 All EASv2 user port (ETH1-ETH4, SFP5-SFP8)
ge5-ge8 0x3c0 EASv2 Electrical user port (ETH1-ETH4)
4.5.2.1 — Define an entry in the ACL
bcm l2 add MAC=<MAC_ADDRESS> vlan=<id> pbm=<pbmp> st=t rp=f m=<SLOT-1>
• <MAC_ADDRESS>: MAC address (e.g. 00:00:00:C2:F5:01) of the station admitted

into the system
• <pbmp>: pbm is the specific interface where the station having the
MAC_ADDRESS is connected to; range: ge5, ge6, ge17, ge18, ge19, ge20;
mandatory.
• <id>: it is the vlan ID the MAC_ADDRESS belongs to; valid range [1:4080];
mandatory.
• <SLOT-1>: it is the slot hosting the specific Card (Core or EAS/EASv2); mandatory
Note: In case of Core protection <SLOT-1> shall consider only Core Main.

SFP 2E1/DS1 CIRCUIT EMULATION
Id parameters defined above has to be considered differently in the following three bridge
mode:
• 802.1D
• id is equal to 1 if the frame was originally untagged;
• id is equal to VLAN id carried inside VLAN Tag if the frame was originally
tagged and this VLAN id is already in use by a TDM2ETH XC involving any
user ethernet port;
• 802.1Q
• id is equal to VLAN id carried inside vlan Tag if the frame was originally
tagged;
• id is equal to PVLAN in case the frame is coming in untagged and then tagged
on a port based way;
• 802.1D + QINQ (by cfg file)
• id is equal to Service VLAN id the incoming packet is mapped to;
In case of EAS or EASv2, the <slot-1> number must be added to above command.
Command example (for Core):
bcm l2 add MAC=00:00:00:C2:F5:01 vlan=2 pbm=ge18 st=t rp=f m=0
4.6 — SFP 2E1/DS1 CIRCUIT EMULATION
4.6.1 — Description
SFP 2E1/DS1 is an SFP module supporting circuit emulation service of up to 2 tributaries
(E1/DS1) that can be hosted in one of the two optical ports of the CORE card. None of the
other optical ports in the equipment can support this module in this release. Despite the
hardware readiness of the module, this release supports circuit emulation service for E1/
DS1 in TDM2ETH/TDM2TDM profile only. Moreover, SFP module is supposed to be
connected to one of the two optical ports of the CORE card. Additionally, SFP module is
supposed to properly work without static LAG.
SFP module can interwork with radio interfaces (M300, MPT) and PDH card. The way of
configuring the module is divided into two parts. The former makes use of a configuration
file (whose content is described here) and the latter is based and CT/NMS. Based on the
configuration needed, a configuration file (or more, see paragraph 6.1) shall be loaded
inside the NE Flash Card. The content of the file(s) shall include all the commands
necessary to properly configure the circuit emulation service up to two IWF. Once the SFP
module is properly configured, using CT/NMS the operator has to perform cross-

connection operation using the proper panel in order to establish the cross-connection
between the SFP and any other interface/card of the equipment. In order to complete the
cross-connection, CT/NMS requires as input the Next Hop MAC address. See Normal
procedure to use the proper MAC address.
4.6.2 — Normal procedure

In order to use the 2xE1/DS1 module inside MPR system, the operator is required to:
1. load inside Flash Card, the configuration file(s)

2. equip at CT/NMS level the SFP module on the optical port he intends to use
3. enable the optical port at CT/NMS
4. plug 2E1/DS1 module into the system
5. perform all XC by CT/NMS
Note: if SFP is equipped without having been loaded before the configuration file on the
Flash Card, an NE restart may be necessary through CT/NMS to apply the SFP
configuration.
Figure 4.3 — SFP configuration

During XC configuration, the operator will be asked to select the TDM service and
inserting Flow ID (supposed to be equal to VLAN ID used to configure the specific
tributary) along with the destination MAC address (see SFP configuration). Depending on
the ports the SFP module has been insert, MAC address to be used must be on of the
following two:
• 00:80:9F:09:F0:50 when optical port 5 is used

• 00:80:9F:09:F0:60 when optical port 6 is used
4.6.3 — Configuration File basic structure

This section applies in all the cases SFP module is used to carry an E1 circuit. Each
configuration file for SFP 2xE1/DS1 must respect a predefined structure divided in block
of operations with different purpose.
1. CORE ports initialization

• 1.1. Optical Port 5 default configuration (see Optical Port 5 default
configuration)
• 1.2. Optical Port 6 default configuration (see Optical Port 6 default
configuration)
2. IWF specific configuration
• 2.1.Optical port 5 Tributary 1 IWF configuration (see Optical port 5 Tributary
1 IWF configuration)
3. Per port common tributaries configuration
• 3.1.Optical port 5 Tributaries common configuration (see Optical port 5
tributaries common configuration)
• 3.2.Optical port 6 Tributaries common configuration (see Optical port 6
tributaries common configuration)
4. Per port Tributaries configuration apply command (see Tributaries configuration
apply command)
5. Protocol specific configuration (see Tributary Destination MAC address and
Tributary VLAN ID and ECID)
• 5.1.Optical port 5 Tributary 1 Dst MAC, VLAN ID and ECID


6. Per port LIU enable command (see Per port LIU enable command)
• 6.1.Optical port 5 LIU enable command
• 6.2.Optical port 6 LIU enable command
7. Per port Tributaries enable command (see Per port Tributaries enable command)
• 7.1.Optical port 5 Tributary 1 enable command
Respecting this mandatory order, the operator is in charge to prepare and include inside the
configuration file all the macro-blocks he needs depending on which and how many optical
ports he intends to use and which and how many tributaries he wants to configure.
4.6.3.1 — Optical Port 5 default configuration
setreg 03300020 0c
setreg 03300003 29
setreg 03300005 00
setreg 03300002 09
setreg 03300025 00
setreg 03200000 34
4.6.3.2 — Optical Port 6 default configuration
setreg 04300020 0c
setreg 04300003 29
setreg 04300005 00
setreg 04300002 09
setreg 04300025 00
setreg 04200000 34

4.6.3.3 — Optical port 5 Tributary 1 IWF configuration
setreg 03500004 FE
setreg 03500000 01
setreg 03500005 03
setreg 03500006 07
setreg 03500007 00
setreg 03500008 04
setreg 03500009 14
setreg 0350000a 00
setreg 0350000b 00
setreg 03500010 0c
setreg 03500011 00
setreg 03500018 00
setreg 0350001c <HEX value>
setreg 0350001d a2
setreg 0350001e 86
setreg 0350001f 41
setreg 03500001 00
setreg 03500002 00
setreg 03500003 00
setreg 03700080 50
setreg 03700081 35
setreg 03700082 0c
setreg 03700083 00
setreg 03700084 b0

setreg 03700085 34
setreg 03700086 0c
setreg 03700087 00
setreg 03700088 00
setreg 03700089 35
setreg 0370008a 0c
setreg 0370008b 00
setreg 0370008c 00
setreg 0370008d 0c
setreg 0370008e 00
setreg 0370008f 00
setreg 03700090 03
setreg 03700091 00
setreg 03700092 02
setreg 03700093 00
setreg 03700094 04
setreg 03700095 01
setreg 03700096 07
setreg 03700097 f0
Note: "setreg 0350001c" has not been specialize here, see Clock recovery type
setreg 03500044 FE
setreg 03500040 01

setreg 03500045 03
setreg 03500046 07
setreg 03500047 00
setreg 03500048 04
setreg 03500049 14
setreg 0350004a 00
setreg 0350004b 00
setreg 03500050 0c
setreg 03500051 00
setreg 03500058 00
setreg 0350005d a2
setreg 0350005e 86
setreg 0350005f 41
setreg 03500041 00
setreg 03500042 00
setreg 03500043 00
setreg 037000c0 50
setreg 037000c1 35
setreg 037000c2 0c
setreg 037000c3 00
setreg 037000c4 b0
setreg 037000c5 34
setreg 037000c6 0c
setreg 037000c7 00
setreg 037000c8 00

setreg 037000c9 35
setreg 037000ca 0c
setreg 037000cb 00
setreg 037000cc 00
setreg 037000cd 0c
setreg 037000ce 00
setreg 037000cf 00
setreg 037000d0 03
setreg 037000d1 00
setreg 037000d2 02
setreg 037000d3 00
setreg 037000d4 04
setreg 037000d5 01
setreg 037000d6 07
setreg 037000d7 f0
Note: “setreg 0350005c" has not been specialize here, see Clock recovery type
setreg 04500004 FE
setreg 04500000 01
setreg 04500005 03
setreg 04500006 07
setreg 04500007 00
setreg 04500008 04

setreg 04500009 14
setreg 0450000a 00
setreg 0450000b 00
setreg 04500010 0c
setreg 04500011 00
setreg 04500018 00
setreg 0450001d a2
setreg 0450001e 86
setreg 0450001f 41
setreg 04500001 00
setreg 04500002 00
setreg 04500003 00
setreg 04700080 50
setreg 04700081 35
setreg 04700082 0c
setreg 04700083 00
setreg 04700084 b0
setreg 04700085 34
setreg 04700086 0c
setreg 04700087 00
setreg 04700088 00
setreg 04700089 35
setreg 0470008a 0c
setreg 0470008b 00
setreg 0470008c 00

setreg 0470008d 0c
setreg 0470008e 00
setreg 0470008f 00
setreg 04700090 03
setreg 04700091 00
setreg 04700092 02
setreg 04700093 00
setreg 04700094 04
setreg 04700095 01
setreg 04700096 07
setreg 04700097 f0
setreg 04500044 FE
setreg 04500040 01
setreg 04500045 03
setreg 04500046 07
setreg 04500047 00
setreg 04500048 04
setreg 04500049 14
setreg 0450004a 00
setreg 0450004b 00
setreg 04500050 0c

setreg 04500051 00
setreg 04500058 00
setreg 0450005d a2
setreg 0450005e 86
setreg 0450005f 41
setreg 04500041 00
setreg 04500042 00
setreg 04500043 00
setreg 047000c0 50
setreg 047000c1 35
setreg 047000c2 0c
setreg 047000c3 00
setreg 047000c4 b0
setreg 047000c5 34
setreg 047000c6 0c
setreg 047000c7 00
setreg 047000c8 00
setreg 047000c9 35
setreg 047000ca 0c
setreg 047000cb 00
setreg 047000cc 00
setreg 047000cd 0c
setreg 047000ce 00
setreg 047000cf 00
setreg 047000d0 03

setreg 047000d1 00
setreg 047000d2 02
setreg 047000d3 00
setreg 047000d4 04
setreg 047000d5 01
setreg 047000d6 07
setreg 047000d7 f0
4.6.3.7 — Optical port 5 tributaries common configuration
setreg 03600040 00
setreg 03600042 d8
setreg 03600043 88
setreg 03700000 0a
setreg 03700001 14
setreg 03700002 00
setreg 03700003 00
setreg 03600000 09
setreg 03600001 9f
setreg 03600002 80
setreg 03600003 00
setreg 03600006 50
setreg 03600007 f0
setreg 03600008 09

setreg 03600009 9f
setreg 0360000a 80
setreg 0360000b 00
setreg 0360000e 50
setreg 0360000f f0
setreg 03600010 09
setreg 03600011 9f
setreg 03600012 80
setreg 03600013 00
setreg 03600016 50
setreg 03600017 f0
setreg 03600018 09
setreg 03600019 9f
setreg 0360001a 80
setreg 0360001b 00
setreg 0360001e 50
setreg 0360001f f0
setreg 03600020 09
setreg 03600021 9f
setreg 03600022 80
setreg 03600023 00
setreg 03600026 50
setreg 03600027 f0
setreg 03600028 09
setreg 03600029 9f
setreg 0360002a 80

setreg 0360002b 00
setreg 0360002e 50
setreg 0360002f f0
setreg 03600030 09
setreg 03600031 9f
setreg 03600032 80
setreg 03600033 00
setreg 03600036 50
setreg 03600037 f0
setreg 03600038 09
setreg 03600039 9f
setreg 0360003a 80
setreg 0360003b 00
setreg 0360003e 50
setreg 0360003f f0
4.6.3.8 — Optical port 6 tributaries common configuration
setreg 04600040 00
setreg 04600042 d8
setreg 04600043 88
setreg 04700000 0a
setreg 04700001 14
setreg 04700002 00
setreg 04700003 00
setreg 04600000 09

setreg 04600001 9f
setreg 04600002 80
setreg 04600003 00
setreg 04600006 60
setreg 04600007 f0
setreg 04600008 09
setreg 04600009 9f
setreg 0460000a 80
setreg 0460000b 00
setreg 0460000e 60
setreg 0460000f f0
setreg 04600010 09
setreg 04600011 9f
setreg 04600012 80
setreg 04600013 00
setreg 04600016 60
setreg 04600017 f0
setreg 04600018 09
setreg 04600019 9f
setreg 0460001a 80
setreg 0460001b 00
setreg 0460001e 60
setreg 0460001f f0
setreg 04600020 09
setreg 04600021 9f
setreg 04600022 80

setreg 04600023 00
setreg 04600026 60
setreg 04600027 f0
setreg 04600028 09
setreg 04600029 9f
setreg 0460002a 80
setreg 0460002b 00
setreg 0460002e 60
setreg 0460002f f0
setreg 04600030 09
setreg 04600031 9f
setreg 04600032 80
setreg 04600033 00
setreg 04600036 60
setreg 04600037 f0
setreg 04600038 09
setreg 04600039 9f
setreg 0460003a 80
setreg 0460003b 00
setreg 0460003e 60
setreg 0460003f f0
4.6.3.9 — Relevant registers
In order to define all the macro-blocks described in Configuration File basic structure, this
section reports how to configure each specific register within a macro-block.

Clock recovery type
setreg yx5000z C<HEX value>
x=3 Optical Port1 x=4 Optical Port2
z=1 Tributary 1 z=5 Tributary 2
HEX Value shall be :
a. 0x58 Differential Clock recovery (requires RTP protocol, see Per port Tributaries
enable command)
b. 0x5A Node timing
Tributaries configuration apply command
setreg yx200000 0x2c
Tributary Destination MAC address
The following six registers contain the destination MAC address split by byte for each
tributary IWF and must be equal to the NE public MAC address. NE MAC address is can
be found inside CT/NMS inside "Configuration -> System Settings" menu.
Whenever the radio interface involved in the cross-connection is protected, the NE public
MAC address must be inserted in the multicast version. Multicast version corresponds to
the NE public MAC shown at CT/NMS having bit 40 fixed at 1.

Figure 4.4 — Tributary destination MAC address
Write byte 1 of the MAC address [7:0] bits:--:--:--:--:xx
setreg yx5000z2 <HEX value>
• Write byte 2 of the MAC address [15:8] bits: --:--:--:xx:--

For the previous two registers, the following value apply:
• Write byte 3 of the MAC address [23:16] bit: --:--:--:xx:--:--

setreg yx5000zC <HEX value>
• Write byte 4 of the MAC address [31:24] bits: --:--:xx:--:--:--
setreg yx5000zD <HEX value>
• Write byte 5 of the MAC address [39:32] bits:xx:--:--:--:--
setreg yx5000zE <HEX value>
• Write byte 6 of the MAC address [47:40] bits xx:--:--:--:--:--
setreg yx5000zF <HEX value>
For the previous four registers, the following values apply:


Tributary VLAN ID and ECID
The following seven registers contain the VLAN ID (12 bits), ECID in Tx (20 bits) and
ECID in Rx (20 bits) used by the CES. These values are concatenate and represented inside
consecutive registers. Please, pay attention to register yx5000z9, since the last nibble is
reserved and all its bits have to be set to 0.
Figure 4.5 — Tributary VLAN ID and ECID
• Write VLAN ID [7:0] bits

• Write ECID Tx [3:0] and VLAN ID [11:8] bits
• Write ECID Tx [11:4] bits
• Write ECID Tx [19:12] bits
• Write ECID Rx [3:0] bits
setreg yx5000za <HEX value>
setreg yx5000zb <HEX value>
For the previous seven registers, the following values apply:


Per port LIU enable command
setreg yx10000C 01

Per port Tributaries enable command
setreg yx5000z0 01

HEX Value shall be:
a. 0xFF when IWF uses RTP protocol

b. 0xFD when IWF does not use RTP protocol
Here below are reported in table format the supported configurations (ETSI market context
only) for SFP 2xE1/DS1 when the interworking is done with a 32 E1 PDH card (Figure 4.6)
or with an equivalent SFP module (Figure 4.7).
Figure 4.6 — Compatibility table between 32E1 PDH card and 2xE1/DS1 SFP Module

Figure 4.7 — Compatibility table between two 2xE1/DS1 SFP modules
4.6.4 — Blue Signal configuration

This section applies in the only case SFP module is used for synchronization purpose. With
the configuration reported here, SFP module can generate a framed E1 locked to the NE
clock.
The main application of this configuration is to give a synchronization signal to an external

equipment (e.g. base station).
4.6.4.1 — Optical port 5 Tributary 1
setreg 03300020 0c
setreg 03300003 29
setreg 03300005 00
setreg 03300002 09
setreg 03300025 00
setreg 0050002e 00000000
setreg 03200000 34
setreg 03400002 80
setreg 0310000C 01

setreg 03300020 0c
setreg 03300003 29
setreg 03300005 00
setreg 03300002 09
setreg 03300025 00
setreg 0050002e 00000000
setreg 03200000 34
setreg 0340000A 80
setreg 0310000c 01
setreg 04300020 0c
setreg 04300003 29
setreg 04300005 00
setreg 04300002 09
setreg 04300025 00
setreg 0050002e 00000000
setreg 04200000 34
setreg 04400002 80
setreg 0410000C 01
setreg 04300005 00
setreg 04300002 09

setreg 04300025 00
setreg 0050002e 00000000
setreg 04200000 34
setreg 0440000A 80
setreg 0410000c 01
4.6.5 — Configuration for DS1 traffic

Here are reported the applicable register configuration in case of DS1 tributary.
4.6.5.1 — LIU Configuration
setreg yx300020 1c
setreg yx300003 29
setreg yx300005 02
setreg yx300002 12
setreg yx300025 00

4.6.5.2 — E1/DS1 selection in Adorno Configuration block
setreg yx10000A <HEX value>

Bit 0 of <HEX value> shall be:
a. 0b0 for E1 (ETSI) traffic selection
b. 0b1 for DS1 (ANSI) traffic

according to below register mask:
Table 4.7 — Register mask for Adorno Configuration block
BIT DESCRIPTION DEFAULT VALUE
7:3 Unused 00000
2 Tributary 2 is ENABLE(1) or DISABLE(0) 0
1 Tributary 1 is ENABLE(1) or DISABLE(0) 0

0 ETSI/ANSI SELECTION 0
'0' is ETSI AND '1' is for ANSI.
Example for Core Main, Optical Port 5, DS1 (ANSI) traffic selection:
setreg 0310000A 01
4.6.5.3 — E1/DS1 selection in Adorno Tdm interface
setreg yx700002 <HEX value>

<HEX value> shall be:
a. 0x00 for E1 traffic selection

b. 0x01 for DS1 traffic selection
Example for Core Main, Optical Port 5, DS1 selection:
setreg 03700002 01
4.6.5.4 — Configuration of framed/unframed and ESF for DS1

Tributaries
setreg yx30000z <HEX value>


z = 0 Tributary 1 z = 8 Tributary 2
a. 0b0 for no Extended Super Frame

b. 0b1 for selection of Extended Super Frame
a. 0b0 for unframed

b. 0b1 for framed
according to below register mask:
Table 4.8 — Register mask for framed/unframed and ESF
BIT DESCRIPTION DEFAULT VALUE
7 Extended Super Frame (only for DS1) 0
6 Loop toward IWF on IWF side of framer 0
5 Loop toward LIU on LIU side of framer 0
4 Loop toward LIU on IWF side of framer 0
3 Loop toward IWF on LIU side of framer 0
2 REI transparent (only for E1) 0
1 RAI transparent (only for E1) 0

0 Framed (1) or unframed (0) traffic selection 0
Example for Core Main, Optical Port 5, ESF for Tributary 1:
setreg 03300000 80
4.6.6 — Configuration for TDM2TDM profile

Here are reported the applicable register configuration in case of TDM2TDM tributary.
4.6.6.1 — Packet Length Configuration
setreg yx500004 <HEX value1>

setreg yx500005 <HEX value2>

To configure a 121 byte length for TDM2TDM:
1. <HEX value1> bits 7:2 =0b111000 (Packet length bits 5:0).

2. <HEX value2> = 0x01 (Packet length bits 13:6).
Please notice that in <HEX value1> must be also configured the RTP Header presence
that's mandatory for DCR, which turns to be mandatory for TDM2TDM.
4.6.6.2 — Other parameters for ETSI traffic
setreg yx50001e B8
setreg yx50001f 40
setreg yx700080 32
setreg yx700081 C5
setreg yx700082 05
setreg yx700084 E7
setreg yx700085 C4
setreg yx700086 05
setreg yx700088 0D
setreg yx70008A 05
setreg yx70008C AC
setreg yx70008D 05

4.6.6.3 — Other parameters for ANSI traffic

setreg yx50001d ea
setreg yx50001e f4
setreg yx50001f 40
setreg yx700080 65
setreg yx700081 A7
setreg yx700082 07
setreg yx700084 00
setreg yx700085 A7
setreg yx700086 07
setreg yx700088 32
setreg yx70008A 07
setreg yx70008C 90
setreg yx70008D 07
4.6.7 — Example
4.6.7.1 — E1 traffic, TDM2ETH profile
This example illustrates two configuration file for CORE Main and Spare to configure a
single tributary on SFP port 5 having VLAN 10, ECID Tx=10, ECID Rx=10. The E1 is
cross-connected between the SFP module and a protected radio direction in 1+1 using
multicast version of the NE MAC address. The selected clock recovery is differential and
CES frames carry RTP protocol.
#Port 5 trib1
#Optical Port 5 default configuration
setreg 03300020 0c
setreg 03300003 29
setreg 03300005 00

setreg 03300002 09
setreg 03300025 00
setreg 03200000 34
#Optical port 5 Tributary 1 IWF configuration
setreg 03500004 FE
setreg 03500000 01
setreg 03500005 03
setreg 03500006 07
setreg 03500007 00
setreg 03500008 04
setreg 03500009 14
setreg 0350000a 00
setreg 0350000b 00
setreg 03500010 0c
setreg 03500011 00
setreg 03500018 00
#Clock recovery type differential node timing
setreg 0350001c 58
setreg 0350001d a2
setreg 0350001e 86
setreg 0350001f 41
setreg 03500001 00
setreg 03500002 00
setreg 03500003 00
setreg 03700080 50
setreg 03700081 35

setreg 03700082 0c
setreg 03700083 00
setreg 03700084 b0
setreg 03700085 34
setreg 03700086 0c
setreg 03700087 00
setreg 03700088 00
setreg 03700089 35
setreg 0370008a 0c
setreg 0370008b 00
setreg 0370008c 00
setreg 0370008d 0c
setreg 0370008e 00
setreg 0370008f 00
setreg 03700090 03
setreg 03700091 00
setreg 03700092 02
setreg 03700093 00
setreg 03700094 04
setreg 03700095 01
setreg 03700096 07
setreg 03700097 f0
#Optical port 5 tributaries common configuration
setreg 03600040 00
setreg 03600042 d8
setreg 03600043 88

setreg 03700000 0a
setreg 03700001 14
setreg 03700002 00
setreg 03700003 00
setreg 03600000 09
setreg 03600001 9f
setreg 03600002 80
setreg 03600003 00
setreg 03600006 50
setreg 03600007 f0
setreg 03600008 09
setreg 03600009 9f
setreg 0360000a 80
setreg 0360000b 00
setreg 0360000e 50
setreg 0360000f f0
setreg 03600010 09
setreg 03600011 9f
setreg 03600012 80
setreg 03600013 00
setreg 03600016 50
setreg 03600017 f0
setreg 03600018 09
setreg 03600019 9f
setreg 0360001a 80
setreg 0360001b 00

setreg 0360001e 50
setreg 0360001f f0
setreg 03600020 09
setreg 03600021 9f
setreg 03600022 80
setreg 03600023 00
setreg 03600026 50
setreg 03600027 f0
setreg 03600028 09
setreg 03600029 9f
setreg 0360002a 80
setreg 0360002b 00
setreg 0360002e 50
setreg 0360002f f0
setreg 03600030 09
setreg 03600031 9f
setreg 03600032 80
setreg 03600033 00
setreg 03600036 50
setreg 03600037 f0
setreg 03600038 09
setreg 03600039 9f
setreg 0360003a 80
setreg 0360003b 00
setreg 0360003e 50
setreg 0360003f f0

#Tributaries configuration apply command
setreg 03200000 6C
# CONFIG :DESTINATION MAC - VLAN ID - ECID TX - ECID RX -
#DESTINATION MAC TRIB 1 bits (7:0) : -- -- -- -- -- XX
setreg 03500012 07
#DESTINATION MAC TRIB 1 bits (15:8) : -- -- -- -- XX --
setreg 03500013 00
#DESTINATION MAC TRIB 1 bits (23:16) : -- -- -- XX -- --
setreg 0350000c 00
#DESTINATION MAC TRIB 1 bits (31:24) : -- -- XX -- -- --
setreg 0350000d 00
#DESTINATION MAC TRIB 1 bits (39:32) : -- XX -- -- -- --
setreg 0350000e 00
#DESTINATION MAC TRIB 1 bits (47:40) : XX -- -- -- -- --
setreg 0350000f 01
#VLAN ID LSB (7:0) :
setreg 03500014 0a
#ECID Tx (7:4) + VLAN ID MSB(3:0) :
setreg 03500015 a0
#ECID Tx
setreg 03500016 00
#ECID Tx
setreg 03500017 00
#ECID Rx (7:4)
setreg 03500019 a0
#ECID Rx

setreg 0350001a 00
#ECID Rx
setreg 0350001b 00
#Per port LIU enable command
#Remove THz
setreg 0310000C 01
#Per port Tributaries enable command
#ENABLE CHAN 1
setreg 03500004 FF
setreg 03500000 01
4.6.7.2 — E1 traffic, TDM2TDM profile
This example illustrates a configuration file for CORE Main Spare to configure 2 tributaries
on SFP port 6, with TDM2TDM profile.
# SFP 5 setreg 03XXXXXX for all rows #
# SFP 6 setreg 04XXXXXX for all rows #
#common Configuration port 6
setreg 04300020 0c
setreg 04300003 29
setreg 04300005 00
setreg 04300002 09
setreg 04300025 00
setreg 04200000 34
#Common Configuration
setreg 04600040 00
setreg 04600042 d8

setreg 04600043 88
setreg 04700000 0a
setreg 04700001 14
setreg 04700002 00
setreg 04700003 00
setreg 04600000 09
setreg 04600001 9f
setreg 04600002 80
setreg 04600003 00
#SFP 5 ---> setreg 03600006 50
#SFP 6 ---> setreg 04600006 60
setreg 04600006 60
setreg 04600007 f0
setreg 04600008 09
setreg 04600009 9f
setreg 0460000a 80
setreg 0460000b 00
#SFP 5 ---> setreg 0360000e 50
#SFP 6 ---> setreg 0460000e 60
setreg 0460000e 60
setreg 0460000f f0
setreg 04600010 09
setreg 04600011 9f
setreg 04600012 80
setreg 04600013 00
#SFP 5 ---> setreg 03600016 50

#SFP 6 ---> setreg 04600016 60
setreg 04600016 60
setreg 04600017 f0
setreg 04600018 09
setreg 04600019 9f
setreg 0460001a 80
setreg 0460001b 00
#SFP 5 ---> setreg 0360001e 50
#SFP 6 ---> setreg 0460001e 60
setreg 0460001e 60
setreg 0460001f f0
setreg 04600020 09
setreg 04600021 9f
setreg 04600022 80
setreg 04600023 00
#SFP 5 ---> setreg 03600026 50
#SFP 6 ---> setreg 04600026 60
setreg 04600026 60
setreg 04600027 f0
setreg 04600028 09
setreg 04600029 9f
setreg 0460002a 80
setreg 0460002b 00
#SFP 5 ---> setreg 0360002e 50
#SFP 6 ---> setreg 0460002e 60
setreg 0460002e 60

setreg 0460002f f0
setreg 04600030 09
setreg 04600031 9f
setreg 04600032 80
setreg 04600033 00
#SFP 5 ---> setreg 03600036 50
#SFP 6 ---> setreg 04600036 60
setreg 04600036 60
setreg 04600037 f0
setreg 04600038 09
setreg 04600039 9f
setreg 0460003a 80
setreg 0460003b 00
#SFP 5 ---> setreg 0360003e 50
#SFP 6 ---> setreg 0460003e 60
setreg 0460003e 60
setreg 0460003f f0
#Tributaries configuration apply command
#setreg 04200000 2C both on NO ALS
setreg 04200000 2C
#########################################################
# CHANNEL 1 #
#########################################################
#TDM2ETH with RTP protocol ---> setreg 04500004 FE
#TDM2TDM with RTP protocol ---> setreg 04500004 E2
setreg 04500004 E2

#TDM2ETH ---> setreg 04500005 03
#TDM2TDM ---> setreg 04500005 01
setreg 04500005 01
setreg 04500006 07
setreg 04500007 00
setreg 04500008 04
setreg 04500009 14
setreg 0450000a 00
setreg 0450000b 00
setreg 0450000c 09
setreg 0450000d 9f
setreg 0450000e 80
setreg 0450000f 00
setreg 04500010 0c
setreg 04500011 00
setreg 04500012 03
setreg 04500013 f3
setreg 04500014 0a
setreg 04500015 a0
setreg 04500016 00
setreg 04500017 00
setreg 04500018 00
setreg 04500019 a0
setreg 0450001a 00
setreg 0450001b 00
#Differential/Adaptive/Node timing

#setreg 0450001c <HEX value>
setreg 0450001c 58
setreg 0450001d a2
#TDM2ETH ---> setreg 0450001e 86
#TDM2TDM ---> setreg 0450001e B8
#TDM2ETH ---> setreg 0450001f 41
#TDM2TDM ---> setreg 04500005 40
setreg 0450001e B8
setreg 0450001f 40
setreg 04500000 01
setreg 04500001 00
setreg 04500002 00
setreg 04500003 00
#TDM2ETH ---> setreg 04500080 50
#TDM2TDM ---> setreg 04500081 32
#TDM2ETH ---> setreg 04500081 35
#TDM2TDM ---> setreg 04500081 C5
#TDM2ETH ---> setreg 04500082 0C
#TDM2TDM ---> setreg 04500082 05
setreg 04700080 32
setreg 04700081 C5
setreg 04700082 05
setreg 04700083 00
#TDM2ETH ---> setreg 04500084 B0
#TDM2TDM ---> setreg 04500084 E7
#TDM2ETH ---> setreg 04500085 34

#TDM2TDM ---> setreg 04500085 C4
#TDM2ETH ---> setreg 04500086 0C
#TDM2TDM ---> setreg 04500086 05
setreg 04700084 E7
setreg 04700085 C4
setreg 04700086 05
setreg 04700087 00
#TDM2ETH ---> setreg 04500088 00
#TDM2TDM ---> setreg 04500088 0D
setreg 04700088 0D
setreg 04700089 35
#TDM2ETH ---> setreg 0450008a 0C
#TDM2TDM ---> setreg 0450008a 05
setreg 0470008a 05
setreg 0470008b 00
#TDM2ETH ---> setreg 0450008c 00
#TDM2TDM ---> setreg 0450008c AC
#TDM2ETH ---> setreg 0450008d 0C
#TDM2TDM ---> setreg 0450008d 05
setreg 0470008c AC
setreg 0470008d 05
setreg 0470008e 00
setreg 0470008f 00
setreg 04700090 03
setreg 04700091 00
setreg 04700092 02

setreg 04700093 00
setreg 04700094 04
setreg 04700095 01
setreg 04700096 07
setreg 04700097 f0
# CONFIG :DESTIMNATION MAC - VLAN ID - ECID TX - ECID RX -
setreg 04500012 F3
setreg 04500013 0A
setreg 0450000c 00
setreg 0450000d AE
setreg 0450000e 21
setreg 0450000f 00
# VLAN= 840(Dec) 348 Hex
setreg 04500014 48
setreg 04500015 83
#ECID Tx
setreg 04500016 34
#ECID Tx

setreg 04500017 00
#ECID Rx (7:4)
setreg 04500019 80
#ECID Rx
setreg 0450001a 34
#ECID Rx
setreg 0450001b 00
#Remove THz
setreg 0410000C 01
#ENABLE CHAN 1
#TDM2ETH with RTP protocol ---> setreg 04500004 FF
setreg 04500004 E3
setreg 04500000 01
##########################################################
CHANNEL 2 #
#########################################################
#TDM2ETH with RTP protocol ---> setreg 04500044 FE
setreg 04500044 E2
#TDM2ETH ---> setreg 04500045 03
#TDM2TDM ---> setreg 04500045 01
setreg 04500045 01
setreg 04500046 07

setreg 04500047 00
setreg 04500048 04
setreg 04500049 14
setreg 0450004a 00
setreg 0450004b 00
setreg 0450004c 09
setreg 0450004d 9f
setreg 0450004e 80
setreg 0450004f 00
setreg 04500050 0c
setreg 04500051 00
setreg 04500052 03
setreg 04500053 f3
setreg 04500054 0b
setreg 04500055 c0
setreg 04500056 00
setreg 04500057 00
setreg 04500058 00
setreg 04500059 d0
setreg 0450005a 00
setreg 0450005b 00
#Differential/Adaptive/Node timing
#setreg 0450005c <HEX value>
setreg 0450005c 58
setreg 0450005d a2
#TDM2ETH ---> setreg 0450005e 86

#TDM2TDM ---> setreg 0450005e B8
#TDM2ETH ---> setreg 0450005f 41
#TDM2TDM ---> setreg 0450005f 40
setreg 0450005e B8
setreg 0450005f 40
setreg 04500040 01
setreg 04500041 00
setreg 04500042 00
setreg 04500043 00
#TDM2ETH ---> setreg 045000c0 50
#TDM2TDM ---> setreg 045000c0 32
#TDM2TDM ---> setreg 045000c1 C5
#TDM2ETH ---> setreg 045000c2 0C
setreg 047000c0 32
setreg 047000c1 C5
setreg 047000c2 05
setreg 047000c3 00
#TDM2ETH ---> setreg 045000c4 B0
#TDM2TDM ---> setreg 045000c4 E7
#TDM2TDM ---> setreg 045000c5 C4
#TDM2ETH ---> setreg 045000c6 0C
setreg 047000c4 E7

setreg 047000c5 C4
setreg 047000c6 05
setreg 047000c7 00
#TDM2TDM ---> setreg 045000c8 0D
setreg 047000c8 0D
setreg 047000c9 35
#TDM2ETH ---> setreg 045000ca 0C
#TDM2TDM ---> setreg 045000ca 05
setreg 047000ca 05
setreg 047000cb 00
#TDM2ETH ---> setreg 045000cc 00
#TDM2TDM ---> setreg 045000cc AC
#TDM2ETH ---> setreg 045000cd 0C
#TDM2TDM ---> setreg 045000cd 05
setreg 047000cc AC
setreg 047000cd 05
setreg 047000ce 00
setreg 047000cf 00
setreg 047000d0 03
setreg 047000d1 00
setreg 047000d2 02
setreg 047000d3 00
setreg 047000d4 04
setreg 047000d5 01
setreg 047000d6 07

setreg 047000d7 f0
# CONFIG :DESTIMNATION MAC - VLAN ID - ECID TX - ECID RX -
setreg 04500052 F3
setreg 04500053 0A
setreg 0450004c 00
setreg 0450004d AE
setreg 0450004e 21
setreg 0450004f 00
# VLAN= 410(Dec) 19A Hex
setreg 04500054 9a
setreg 04500055 a1
#ECID Tx
setreg 04500056 19
#ECID Tx
setreg 04500057 00
#ECID Rx (7:4)
setreg 04500059 a0
#ECID Rx

setreg 0450005a 19
#ECID Rx
setreg 0450005b 00
#Remove THz
setreg 0410000C 01
#ENABLE CHAN 2
#TDM2ETH with RTP protocol ---> setreg 04500044 FF
setreg 04500044 E3
setreg 04500040 01
4.6.7.3 — DS1 traffic, TDM2ETH profile
This example illustrates a configuration file for CORE Main to configure on SFP port 5
two tributaries with TDM2TDM profile:
tributary one having VLAN = 10 , ECID Tx=10, ECID Rx=10
tributary two having VLAN = 11 , ECID Tx=11, ECID Rx=11.
The DS1 are cross-connected between the SFP module and a radio direction.The selected
clock recovery is differential and CES frames carry RTP protocol.
#LIU CONFIG
setreg 03300020 1c
setreg 03300003 29
setreg 03300005 02
setreg 03300002 12
setreg 03300025 00

# DS1 Traffic selection
setreg 0310000A 01
# TRIBUTARY 1 CONFIGURATION
# CES Protocol configuration
setreg 03500004 ff
setreg 03500005 02
setreg 03500006 07
setreg 03500007 00
setreg 03500008 04
setreg 03500009 14
setreg 0350000a 00
setreg 0350000b 00
# MAC (.. .. .. xx .. ..)
setreg 0350000c 08
# MAC (.. .. xx .. .. ..)
setreg 0350000d 60
# MAC (.. xx .. .. .. ..)
setreg 0350000e 20
# MAC (xx .. .. .. .. ..)
setreg 0350000f 00
setreg 03500010 0d
setreg 03500011 00
# MAC (.. .. .. .. .. xx)
setreg 03500012 01
# MAC (.. .. .. .. xx ..)
setreg 03500013 03

#VLAN, ECID Tx and ECID Rx = 00a
setreg 03500014 0a
setreg 03500015 a0
setreg 03500016 00
setreg 03500017 00
setreg 03500018 00
setreg 03500019 a0
setreg 0350001a 00
setreg 0350001b 00
# differential clock configuration
setreg 0350001c 58
#TDM2ETH configuration
setreg 0350001d 9a
setreg 0350001e 84
setreg 0350001f 41
setreg 03500001 00
setreg 03500002 00
setreg 03500003 00
setreg 03700080 1e
setreg 03700081 25
setreg 03700082 0c
setreg 03700083 00
setreg 03700084 7f
setreg 03700085 24

setreg 03700086 0c
setreg 03700087 00
setreg 03700088 cf
setreg 03700089 24
setreg 0370008a 0c
setreg 0370008b 00
setreg 0370008c 00
setreg 0370008d 0c
setreg 0370008e 00
setreg 0370008f 00
setreg 03700090 03
setreg 03700091 00
setreg 03700092 02
setreg 03700093 00
setreg 03700094 04
setreg 03700095 01
setreg 03700096 07
setreg 03700097 f0
# MAC DA 1:4 pool (for Eth->TDM packet discard)
setreg 03600000 09
setreg 03600001 9f
setreg 03600002 80
setreg 03600003 00
setreg 03600004 00
setreg 03600005 00
setreg 03600006 60

setreg 03600007 f0
setreg 03600008 09
setreg 03600009 9f
setreg 0360000a 80
setreg 0360000b 00
setreg 0360000c 00
setreg 0360000d 00
#last 4 bytes of destination slot
setreg 0360000e 06
setreg 0360000f f6
setreg 03600010 09
setreg 03600011 9f
setreg 03600012 80
setreg 03600013 00
setreg 03600014 00
setreg 03600015 00
setreg 03600016 60
setreg 03600017 f0
setreg 03600018 09
setreg 03600019 9f
setreg 0360001a 80
setreg 0360001b 00
setreg 0360001c 00
setreg 0360001d 00
setreg 0360001e 60
setreg 0360001f f0

# MAC SA 1:4 pool (TDM->Eth, configuration SA on per PW basis)
setreg 03600020 09
setreg 03600021 9f
setreg 03600022 80
setreg 03600023 00
setreg 03600024 00
setreg 03600025 00
setreg 03600026 60
setreg 03600027 f0
setreg 03600028 09
setreg 03600029 9f
setreg 0360002a 80
setreg 0360002b 00
setreg 0360002c 00
setreg 0360002d 00
setreg 0360002e 60
setreg 0360002f f0
setreg 03600030 09
setreg 03600031 9f
setreg 03600032 80
setreg 03600033 00
setreg 03600034 00
setreg 03600035 00
setreg 03600036 60
setreg 03600037 f0
setreg 03600038 09

setreg 03600039 9f
setreg 0360003a 80
setreg 0360003b 00
setreg 0360003c 00
setreg 0360003d 00
setreg 0360003e 60
setreg 0360003f f0
setreg 03600040 00
setreg 03600041 00
# MEF8 Ethertype
setreg 03600042 d8
setreg 03600043 88
setreg 03700000 0a
setreg 03700001 14
setreg 03700002 01
setreg 03700003 00
setreg 03200000 2C
setreg 0310000C 01
setreg 03500000 01
setreg 03500004 ff
setreg 03500005 02
setreg 03500006 07
setreg 03500007 00
setreg 03500008 04

setreg 03500009 14
setreg 0350000a 00
setreg 0350000b 00
setreg 0350000c 09
setreg 0350000d 9f
setreg 0350000e 80
setreg 0350000f 00
setreg 03500010 0d
setreg 03500011 00
setreg 03500012 03
setreg 03500013 f3
setreg 03500014 0a
setreg 03500015 a0
setreg 03500016 00
setreg 03500017 00
setreg 03500018 00
setreg 03500019 a0
setreg 0350001a 00
setreg 0350001b 00
setreg 0350001c 58
setreg 0350001d 9a
setreg 0350001e 84
setreg 0350001f 41
setreg 03500001 00
setreg 03500002 00
setreg 03500003 00

setreg 03700080 1e
setreg 03700081 25
setreg 03700082 0c
setreg 03700083 00
setreg 03700084 7f
setreg 03700085 24
setreg 03700086 0c
setreg 03700087 00
setreg 03700088 cf
setreg 03700089 24
setreg 0370008a 0c
setreg 0370008b 00
setreg 0370008c 00
setreg 0370008d 0c
setreg 0370008e 00
setreg 0370008f 00
setreg 03700090 03
setreg 03700091 00
setreg 03700092 02
setreg 03700093 00
setreg 03700094 04
setreg 03700095 01
setreg 03700096 07
setreg 03700097 f0
setreg 03600000 09
setreg 03600001 9f

setreg 03600002 80
setreg 03600003 00
setreg 03600004 00
setreg 03600005 00
setreg 03600006 60
setreg 03600007 f0
setreg 03600008 09
setreg 03600009 9f
setreg 0360000a 80
setreg 0360000b 00
setreg 0360000c 00
setreg 0360000d 00
setreg 0360000e 03
setreg 0360000f f3
setreg 03600010 09
setreg 03600011 9f
setreg 03600012 80
setreg 03600013 00
setreg 03600014 00
setreg 03600015 00
setreg 03600016 60
setreg 03600017 f0
setreg 03600018 09
setreg 03600019 9f
setreg 0360001a 80
setreg 0360001b 00

setreg 0360001c 00
setreg 0360001d 00
setreg 0360001e 60
setreg 0360001f f0
setreg 03600020 09
setreg 03600021 9f
setreg 03600022 80
setreg 03600023 00
setreg 03600024 00
setreg 03600025 00
setreg 03600026 60
setreg 03600027 f0
setreg 03600028 09
setreg 03600029 9f
setreg 0360002a 80
setreg 0360002b 00
setreg 0360002c 00
setreg 0360002d 00
setreg 0360002e 60
setreg 0360002f f0
setreg 03600030 09
setreg 03600031 9f
setreg 03600032 80
setreg 03600033 00
setreg 03600034 00
setreg 03600035 00

setreg 03600036 60
setreg 03600037 f0
setreg 03600038 09
setreg 03600039 9f
setreg 0360003a 80
setreg 0360003b 00
setreg 0360003c 00
setreg 0360003d 00
setreg 0360003e 60
setreg 0360003f f0
setreg 03600040 00
setreg 03600041 00
setreg 03600042 d8
setreg 03600043 88
setreg 03700000 0a
setreg 03700001 14
setreg 03700002 01
setreg 03700003 00
setreg 03500000 01
4.6.7.4 — DS1 traffic, TDM2TDM profile
This example illustrates a configuration file for CORE Main to configure on SFP port 5
two tributaries with TDM2TDM profile:
• tributary one having VLAN = 10 , ECID Tx=10, ECID Rx=10

• tributary two having VLAN = 11 , ECID Tx=11, ECID Rx=11.

The DS1 are cross-connected between the SFP module and a radio direction. According to
TDM2TDM profile, the selected clock recovery is differential and CES frames carry RTP
protocol.
#LIU CONFIG
setreg 03300020 1c
setreg 03300003 29
setreg 03300005 02
setreg 03300002 12
setreg 03300025 00
setreg 0310000A 01
# CES Protocol configuration
setreg 03500004 e3
setreg 03500005 01
setreg 03500006 07
setreg 03500007 00
setreg 03500008 04
setreg 03500009 14
setreg 0350000a 00
setreg 0350000b 00
setreg 0350000c 09
setreg 0350000d 9f
setreg 0350000e 80
setreg 0350000f 00
setreg 03500010 0d

setreg 03500011 00
setreg 03500012 03
setreg 03500013 f3
setreg 03500014 0a
setreg 03500015 a0
setreg 03500016 00
setreg 03500017 00
setreg 03500018 00
setreg 03500019 a0
setreg 0350001a 00
setreg 0350001b 00
setreg 0350001c 58
setreg 0350001d ea
setreg 0350001e f4
setreg 0350001f 40
setreg 03500001 00
setreg 03500002 00
setreg 03500003 00
setreg 03700080 65
setreg 03700081 a7
setreg 03700082 07
setreg 03700083 00
setreg 03700084 00
setreg 03700085 a7
setreg 03700086 07
setreg 03700087 00

setreg 03700088 32
setreg 03700089 a7
setreg 0370008a 07
setreg 0370008b 00
setreg 0370008c 90
setreg 0370008d 07
setreg 0370008e 00
setreg 0370008f 00
setreg 03700090 03
setreg 03700091 00
setreg 03700092 03
setreg 03700093 00
setreg 03700094 04
setreg 03700095 01
setreg 03700096 07
setreg 03700097 f0
setreg 03600000 09
setreg 03600001 9f
setreg 03600002 80
setreg 03600003 00
setreg 03600004 00
setreg 03600005 00
setreg 03600006 60
setreg 03600007 f0
setreg 03600008 09
setreg 03600009 9f

setreg 0360000a 80
setreg 0360000b 00
setreg 0360000c 00
setreg 0360000d 00
setreg 0360000e 03
setreg 0360000f f3
setreg 03600010 09
setreg 03600011 9f
setreg 03600012 80
setreg 03600013 00
setreg 03600014 00
setreg 03600015 00
setreg 03600016 60
setreg 03600017 f0
setreg 03600018 09
setreg 03600019 9f
setreg 0360001a 80
setreg 0360001b 00
setreg 0360001c 00
setreg 0360001d 00
setreg 0360001e 60
setreg 0360001f f0
setreg 03600020 09
setreg 03600021 9f
setreg 03600022 80
setreg 03600023 00

setreg 03600024 00
setreg 03600025 00
setreg 03600026 60
setreg 03600027 f0
setreg 03600028 09
setreg 03600029 9f
setreg 0360002a 80
setreg 0360002b 00
setreg 0360002c 00
setreg 0360002d 00
setreg 0360002e 60
setreg 0360002f f0
setreg 03600030 09
setreg 03600031 9f
setreg 03600032 80
setreg 03600033 00
setreg 03600034 00
setreg 03600035 00
setreg 03600036 60
setreg 03600037 f0
setreg 03600038 09
setreg 03600039 9f
setreg 0360003a 80
setreg 0360003b 00
setreg 0360003c 00
setreg 0360003d 00

setreg 0360003e 60
setreg 0360003f f0
setreg 03600040 00
setreg 03600041 00
setreg 03600042 d8
setreg 03600043 88
setreg 03700000 0a
setreg 03700001 14
setreg 03700002 01
setreg 03700003 00
setreg 03500000 01
setreg 03500044 e3
setreg 03500045 01
setreg 03500046 07
setreg 03500047 00
setreg 03500048 04
setreg 03500049 14
setreg 0350004a 00
setreg 0350004b 00
setreg 0350004c 09
setreg 0350004d 9f
setreg 0350004e 80
setreg 0350004f 00
setreg 03500050 0d
setreg 03500051 00

setreg 03500052 03
setreg 03500053 f3
setreg 03500054 0b
setreg 03500055 b0
setreg 03500056 00
setreg 03500057 00
setreg 03500058 00
setreg 03500059 b0
setreg 0350005a 00
setreg 0350005b 00
setreg 0350005c 58
setreg 0350005d ea
setreg 0350005e f4
setreg 0350005f 40
setreg 03500041 00
setreg 03500042 00
setreg 03500043 00
setreg 037000c0 65
setreg 037000c1 a7
setreg 037000c2 07
setreg 037000c3 00
setreg 037000c4 00
setreg 037000c5 a7
setreg 037000c6 07
setreg 037000c7 00
setreg 037000c8 32

setreg 037000c9 a7
setreg 037000ca 07
setreg 037000cb 00
setreg 037000cc 90
setreg 037000cd 07
setreg 037000ce 00
setreg 037000cf 00
setreg 037000d0 03
setreg 037000d1 00
setreg 037000d2 03
setreg 037000d3 00
setreg 037000d4 04
setreg 037000d5 01
setreg 037000d6 07
setreg 037000d7 f0
setreg 03600000 09
setreg 03600001 9f
setreg 03600002 80
setreg 03600003 00
setreg 03600004 00
setreg 03600005 00
setreg 03600006 60
setreg 03600007 f0
setreg 03600008 09
setreg 03600009 9f
setreg 0360000a 80

setreg 0360000b 00
setreg 0360000c 00
setreg 0360000d 00
setreg 0360000e 03
setreg 0360000f f3
setreg 03600010 09
setreg 03600011 9f
setreg 03600012 80
setreg 03600013 00
setreg 03600014 00
setreg 03600015 00
setreg 03600016 60
setreg 03600017 f0
setreg 03600018 09
setreg 03600019 9f
setreg 0360001a 80
setreg 0360001b 00
setreg 0360001c 00
setreg 0360001d 00
setreg 0360001e 60
setreg 0360001f f0
setreg 03600020 09
setreg 03600021 9f
setreg 03600022 80
setreg 03600023 00
setreg 03600024 00

setreg 03600025 00
setreg 03600026 60
setreg 03600027 f0
setreg 03600028 09
setreg 03600029 9f
setreg 0360002a 80
setreg 0360002b 00
setreg 0360002c 00
setreg 0360002d 00
setreg 0360002e 60
setreg 0360002f f0
setreg 03600030 09
setreg 03600031 9f
setreg 03600032 80
setreg 03600033 00
setreg 03600034 00
setreg 03600035 00
setreg 03600036 60
setreg 03600037 f0
setreg 03600038 09
setreg 03600039 9f
setreg 0360003a 80
setreg 0360003b 00
setreg 0360003c 00
setreg 0360003d 00
setreg 0360003e 60

ALARM SEVERITY ASSIGNMENT PROFILE
setreg 0360003f f0
setreg 03600040 00
setreg 03600041 00
setreg 03600042 d8
setreg 03600043 88
setreg 03700000 0a
setreg 03700001 14
setreg 03700002 01
setreg 03700003 00
setreg 03500040 01
4.7 — ALARM SEVERITY ASSIGNMENT PROFILE
4.7.1 — Description
Alarm Severity Assignment Profile feature allows the operator to realize a custom re-
mapping of "NonServiceAffecting" (NSA) severity and "ServiceAffecting" (SA) severity
of each alarm supported into the system.
Note: the configuration file used to apply this feature is to be managed by FTM tool (see
Appendix section File Transfer Manager tool), see Configuration File upload and execution
for this specific file upload to Flash Card.
4.7.2 — Normal procedure

Configuration file used for this feature is different than any other configuration file used by
the system. Once loaded into the Flash Card, in order to apply the configuration contained
into the file, the operator is required to perform a NE restart through CT/NMS.
4.7.3 — Migration in case of SWP Upgrade

As exception to general rule asserting that migration of features managed by Configuration

file is to be manually done by operator.
However as described in mentioned SR ID, automatic migration will not cover the case of
change for the new SW release of default severity for some of the alarms already present in
the ASAP Configuration File in SW release used to deploy it. For this specific case, ASAP
Configuration File must be updated manually.
4.7.4 — File content

The file must contain all alarms re-definition even when the goal is to change just a single
alarm severity. Respect of this rule is mandatory.
Each command insert inside "def_asap4.psh" configuration file must respect the following
structure:
<Alarm ID> <SA severity> <NSA severity>
<Alarm ID>: identifier corresponding to specific alarm whose severity the user wants to
change; see Alarm IDs;
<SA severity>: severity in case of service affecting alarm; see Table 4.9;
<NSA severity>: severity in case of non service affecting alarm; see Table 4.9;
Table 4.9 — Severity table
Severity Severity Value
NO_ALARM 0
MINOR 1
MAJOR 2
CRITICAL 3
WARNING 4
For each alarm, the operator is required to insert both SA and NSA severities.
Table 4.10 — Alarm IDs
Alarm ID Alarm Name SA severity NSA severity
2 Cable LOS Major Minor

3 RX Fail Major Minor

Table 4.10 — Alarm IDs (Continued)
5 Demodulator Fail Major Minor
12 Early Warning Warning Warning

17 ATPC Loop Problem Major Major
24 Dem XPIC LOS Minor Minor
25 Incompatible Frequency Major Minor

26 Incompatible TX Power Major Minor
29 AIS Major Minor
30 Degrade Minor Warning
32 Loss Of Frame Major Minor
34 Loss Of Signal Major Minor
37 High BER Minor Warning
39 Unavailable Time Major Minor
46 Replaceable Unit Missing Major Minor
47 Replaceable Unit Type Mismatch Major Minor
50 Replaceable Unit Problem Major Minor
51 Battery Failure Minor Minor
52 Firmware Download On Going Warning Warning
54 Version Mismatch Minor Minor
57 Underlying Resource Unavailable Major Minor
58 Underlying Resource Unavailable Major Minor

Service
59 Loss Of Protection Major Minor
60 Loss Ethernet Synchronization Minor Warning

Messaging Channel
61 Synchronization Signal Fail Minor Warning
62 Trace Identifier Mismatch Major Major

64 Internal Communication Problem Major Minor
67 Unconfigured Equipment Present Warning Warning
75 Remote Defect Indication Minor Minor

76 Link Identifier Mismatch Major Major
77 Housekeeping Alarm Minor Minor

78 Threshold Crossed Major Minor
79 Standby Version Mismatch Warning Warning
80 PPP Fail Minor Warning

82 Loss Of Alignment Minor Minor
88 Loss Of CESoETH Frame Major Minor
90 Incompatible Shifter Major Minor
91 Provisioning Mismatch Minor Minor
92 Secondary Battery Failure Minor Minor
98 Link Loss Of Cell Delineation (ATM) Major Major
99 Link Loss IMA Frame (ATM) Major Major
100 Link Out Delay Synch (ATM) Major Major
101 Link Remote Defect Indication Major Major

(ATM)
102 Trail Signal Failure Major Major
103 Retiming Buffer Overflow Major Major
104 Loop Problem Minor Minor
105 Power Supply Failure Major Minor
106 Incompatible Modulation Major Minor
107 Clock Failure Major Minor
108 Underlying Resource Degraded Minor Warning

109 Bandwidth Over Flow Major Major
110 Ethernet Signal Degrade Minor Warning
111 Excessive Environmental Warning Warning

Temperature
112 RPS Path Failure Major Minor
113 Dialog Failure Problem Warning Warning
114 EthOAM Loss Of Continuity Minor Warning

115 EthOAM Mismerge Condition Minor Warning
116 EthOAM Unexpected Mep Identifier Minor Warning

117 EthOAM Unexpected Level Minor Warning
118 EthOAM Unexpected Period Minor Warning
119 EthOAM RDI Major Minor

120 CLA Major Minor
121 Incompatible Protection Major Minor
122 Loss Of Pointer Major Minor
123 Signal Label Mismatch Major Minor
124 Loss Of Multiframe Major Minor
125 Bandwidth Degrade for Protection Warning Warning

Switch
126 Flash Card Failure Minor Minor

127 Incompatibility of the power value Major Minor
128 Duplicate Address Detected Minor Minor
129 Fan Communication Problem Minor Minor
130 RF Switch Fail Major Minor
132 Rx Diversity Missing Minor Minor
133 Combiner Loss of Alignment Minor Minor
134 Radio Encryption Mismatch Major Major
136 Flash Card Realignment in Progress Warning Warning
137 Fan Fail Minor Minor

138 Critical Link Event Major Minor
139 OAM Discovery Not Completed Major Minor
140 Service Selective Drop Major Minor
4.7.5 — Example
# <Alarm ID> <SA severity> <NSA severity>

2 2 1 # Cable LOS
3 2 1 # RX Fail
5 2 1 # Demodulator Fail
12 4 4 # Early Warning
17 2 2 # ATPC Loop Problem
24 1 1 # Dem XPIC LOS
25 2 1 # Incompatible Frequency
26 2 1 # Incompatible Tx Power
29 2 1 # AIS
30 1 4 # Degrade
32 2 1 # Loss Of Frame
34 2 1 # Loss Of Signal
37 1 4 # High BER
39 2 1 # Unavailable Time
46 2 1 # Replaceable Unit Missing
47 2 1 # Replaceable Unit Type Mismatch
50 2 1 # Replaceable Unit Problem
51 1 1 # Battery Failure
52 4 4 # Firmware Download On Going
54 1 1 # Version Mismatch
57 2 1 # Underlying Resource Unavailable
58 2 1 # Underlying Resource Unavailable Service
59 2 1 # Loss Of Protection
60 1 4 # Loss Ethernet Synchronization Messaging Channel
61 1 4 # Synchronization Signal Fail
62 2 2 # Trace Identifier Mismatch

64 2 1 # Internal Communication Problem
67 4 4 # Unconfigured Equipment Present
75 1 1 # Remote Defect Indication
76 2 2 # Link Identifier Mismatch
77 1 1 # Housekeeping Alarm
78 2 1 # Threshold Crossed
79 4 4 # Standby Version Mismatch
80 1 4 # PPP Fail
82 1 1 # Loss Of Alignment
88 2 1 # Loss Of CESoETH Frame
90 2 1 # Incompatible Shifter
91 1 1 # Provisioning Mismatch
92 1 1 # Secondary Battery Fail
98 2 2 # Link Loss Of Cell Delineation
99 2 2 # Link Loss IMA Frame
100 2 2 # Link Out Delay Synch
101 2 2 # Link RDI
102 2 2 # Trail Signal Failure
103 2 2 # Retiming Buffer Overflow
104 1 1 # Loop Problem
105 2 1 # Power Supply Failure
106 2 1 # Incompatible Modulation
107 2 1 # Clock Failure
108 1 4 # Underlying Resource Degraded
109 2 2 # Bandwidth Over Flow
110 1 4 # Ethernet Signal Degrade

111 4 4 # Excessive Environmental Temperature
112 2 1 # RPS Path Failure
113 4 4 # Dialog Failure Problem
114 1 4 # EthOAM Loss Of Continuity
115 1 4 # EthOAM Mismerge Condition
116 1 4 # EthOAM Unexpected MEP Identifier
117 1 4 # EthOAM Unexpected Level
118 1 4 # EthOAM Unexpected Period
119 2 1 # EthOAM RDI
120 2 1 # CLA
121 2 1 # Incompatible Protection
122 2 1 # Loss Of Pointer
123 2 1 # Signal Label Mismatch
124 2 1 # Loss Of Multiframe
125 4 4 # Bandwidth Degrade for Protection Switch
126 1 1 # Flash Card Failure
127 2 1 # Incompatibility of power value
128 1 1 # Duplicate Address Detected
129 1 1 #Fan Communication Problem
130 2 1 #RF Switch Fail
132 1 1 #Rx Diversity Missing
133 1 1 #Combiner Loss Of Alignment
134 2 2 #Radio Encryption Mismatch
136 4 4 #Flash Card Realignment In Progress
137 1 1 #Fan Fail
138 2 1 # OAM Discovery Not Completed

PORT MAC LEARNING LIMITING
139 2 1 # Critical Link Event
140 2 1 # Service Selective Drop
4.8 — PORT MAC LEARNING LIMITING

This feature allows restricting the number of MAC addresses that can be learnt by an User
Port.
When limit is reached, new frames with new source MAC address are discarded.
This feature can be also applied to EAS User Ports and EASv2 User Ports.

bcm m mac_limit_enable enable=1
In case of EAS or EASv2, the <slot-1> number must be added to the above commands.

This example limits to 16 the MAC address that can be learned on port ge17 of Core Switch
#MAP port ge17 (a.k.a. 18) to index 18 into the MAC_LIMIT_COUNT_TABLE
bcm mod MAC_LIMIT_PORT_MAP_TABLE 18 1 index=18
#MAC_LIMIT_COUNT_TABLE Line 18 associated to port ge17 contains the max

number of MAC to be learnt by ge17
bcm mod MAC_LIMIT_COUNT_TABLE 18 1 port_trunk_mac_count=16
#Consequent action to be applied on port ge17 when limit is exceeded: here it is drop
bcm mod PORT_TRUNK_MAC_LIMIT_CONTROL_2 18 1 OVER_LIMIT_DROP=1

DOT1P ASSIGNMENT BASED ON INCOMING DIFFSERV
In case of EAS or EASv2, the <slot-1>: number must be added to the above commands.
4.9 — DOT1P ASSIGNMENT BASED ON INCOMING

DIFFSERV
4.9.1 — Overview
This enhanced configuration allows for IPv4 frames having 802.1q or QinQ VLAN tag:
• for IPv4 frames ingressing MPR, to assign the 802.1p bits based on the value of
DiffServ field
• for IPv4 frames egressing MPR, to assign the DiffServ field based on the value of the
802.1p bits field
Generally both two configurations above should be usually applied, but there can be cases
where only one of them is needed.

This enhanced configuration overlaps for FP Group #4 and IDs used in VLAN SWAP AND
DOT1P REMARKING FOR ATM PW SERVICE and QOS BASED ON MPLS TC
(ALSO CALLED EXP BITS) for 802.1P remarking of ATM PW traffic. It is up to the user
to ensure consistency in case both features are being applied (i.e. avoiding creating Group
#4 twice and using same IDs).

# 802.1p remarking based on DSCP for IP packets ingressing MPR
bcm fp qual <ID> dscp <DSCP> 0xdc
bcm fp action add <ID> priopktnew <Dot1p>

DOT1P ASSIGNMENT BASED ON INCOMING DIFFSERV
# DSCP assignment based on 802.1p for IP packets egressing MPR
bcm fp qual <ID> outervlan <Dot1pVLANTag> 0xe000
bcm fp action add <ID> dscpnew <DSCP>
• <ID>: rule ID number; range[512:583]; the chosen value should not be shared among
different rules; mandatory.
• <ingPbm>: user Ethernet port bitmap where IP Packets will ingress MPR network;
see User Ethernet port bitmap where ATM PW frames ingress the network;
mandatory.
• <DSCP> DSCP hex value; mandatory.
• <Dot1p>: 802.1p bits decimal value [0-7]; mandatory.
• <Dot1pVLANTag> - VLANTag hex mask value for given 802.1p value, e.g. 0xe000
identifies 802.1p value = 7 ; mandatory
In case of EAS or EASv2, the <slot-1> number must be added to above commands, while
the same <ID> range applies
4.9.4 — Example
#DSCP bits - 802.1p bits
bcm fp qset clear

MAC AGING TIME CONFIGURATION
# IP Packet ingressing MPR: DCSP = 0XC -> 802.1P = 7
bcm fp qual 512 dscp 0xc0 0xdc
bcm fp qual 512 inports 0x3c00c0 0x7fffff
# IP Packet egressing MPR: 802.1P = 7 -> DCSP = 0X0
bcm fp qual 513 outervlan 0xe000 0xe000
bcm fp action add 513 dscpnew 0x00
4.10 — MAC AGING TIME CONFIGURATION
4.10.1 — Overview
This enhanced configuration allows to change the MAC Aging time, i.e. the time needed to
clear a dynamic entry in the Address Table of Ethernet Switch.
This feature can be also applied to MPT Access, EAS and EASv2 Switch.

bcm age <seconds>
<seconds> is the Aging time measured in second

QOS BASED ON MPLS TC (ALSO CALLED EXP BITS)
In case of MPT Access/EAS/EASv2, the <slot-1> number must be added to the above
command.
4.10.3 — Example
# set Core Switch Aging time to 1 second
bcm age 1
4.11 — QOS BASED ON MPLS TC (ALSO CALLED EXP BITS)
4.11.1 — Overview
This enhanced configuration allows to perform QoS based on MPLS TC (Traffic Class)
field (a.k.a. EXP Bits) mapping the MPLS TC field (3 bits) into VLAN Tag PCP field
(3bits) and mapping MPLS TC to Ethernet switch queues.
The enhanced configuration is useful when MPLS traffic is not carried by VLAN tagged
Ethernet frames and it is not possible to apply QoS based on VLAN Tag priority.
In order to perform QoS based on MPLS TC it is needed to add a VLAN Tag to the MPLS
traffic traversing the radio link made by MPR equipments.
This is achieved configuring by CT or NMS at least one VLAN to carry MPLS traffic over
radio link and to put in the member set of this VLAN the interfaces, both User Ethernet and
radio, where MPLS traffic is flowing. User Ethernet interfaces must be also put in the
untagged set of the VLAN and the VLAN ID must be set as Port VLAN ID of the User
Ethernet interfaces.
This configuration allows to accept untagged Ethernet traffic carrying MPLS and deliver
untagged Ethernet traffic as well out of MPR radio link.
The QoS of MPR equipments must be set to 802.1p.
The enhanced configuration can be applied to the Core and EASv2 Switch, according
where the User Ethernet interfaces delivering MPLS traffic are placed.
4.11.2 — Preliminary Configuration

This enhanced configuration may overlap for FP Group #4 and rule IDs used with the
features described in VLAN SWAP AND DOT1P REMARKING FOR ATM PW
SERVICE and DOT1P ASSIGNMENT BASED ON INCOMING DIFFSERV. It is up to
the user to ensure consistency in case these features are being applied at the same time (i.e.
avoiding creating Group #4 twice and using same IDs).
# preliminary configuration
bcm fp qset clear
#preliminary Configuration
bcm <SLOT-1>: fp qset clear
bcm <SLOT-1>: fp qset add userdefined 1
bcm <SLOT-1>: fp qset add inports
bcm <SLOT-1>: fp qset add ethertype
bcm <SLOT-1>: fp group create 8 4 1
bcm <SLOT-1>: fp qset clear
bcm <SLOT-1>: fp qset add userdefined 1
bcm <SLOT-1>: fp qset add inports
bcm <SLOT-1>: fp qset add ethertype
bcm <SLOT-1>: fp group create 10 5 1
4.11.3 — Removal of User Ethernet interface from existing QoS

mapping

In order to apply the mapping of MPLS TC to Ethernet switch queues, the User Ethernet
interface (or interfaces) where MPLS traffic ingress the MPR equipment must be removed
from the existing mapping of VLAN Tag priority to Ethernet switch queues.
Configuration for “enhanced_eth_feature.psh”:
bcm fp qual 79 inports <ingPbm> 0x3fffff
bcm fp entry reinstall 79

• <ingPbm>: User Ethernet interfaces bitmap removing the interface where MPLS
traffic ingresses MPR equipment from existing mapping; see Table 4.11; mandatory.
Table 4.11 — ingPbm values
ingPbm ingPbm
ge5 0x3fffbf ge5,ge6 0x3fff3f
ge6 0x3fff7f ge17,ge18 0x33ffff
ge17 0x3bffff ge19,ge20 0xfffff
ge18 0x37ffff ge17-ge20 0x3ffff
ge19 0x2fffff ge5,ge6,ge17-ge20 0x3ff3f
ge20 0x1fffff — —
Configuration for “fullConfig_easv2.psh”:

bcm <SLOT-1>: fp entry remove 50
bcm <SLOT-1>: fp qual 50 inports <ingPbm> 0x3fffff


bcm <SLOT-1>: fp entry reinstall 50
• <ingPbm>: User Ethernet interfaces bitmap removing the interface where MPLS
traffic ingresses MPR equipment from existing mapping; see Table 4.12; mandatory.
Table 4.12 — ingPbm values (2)
ingPbm ingPbm
ge5 0x3fffbf ge5,ge6 0x3fff3f
ge6 0x3fff7f ge7,ge8 0x3ffcff
ge7 0x3ffeff ge9,ge10 0x3ff3ff
ge8 0x3ffdff ge17,ge18 0x33ffff
ge9 0x3ffbff ge5-ge8 0x3ffc3f
ge10 0x3ff7ff ge9,ge10,ge17,ge18 0x33f3ff
ge17 0x3bffff — —
ge18 0x37ffff — —
4.11.4 — Mapping MPLS TC field into PCP field of VLAN Tag

bcm port <portNum> 1 USE_INCOMING_DOT1P=0
bcm fp qual <ID> inports <ingPbm> 0x3FFFFF
bcm fp qual <ID> userdefined 1 0x00000<n>00 0x00000e00
bcm fp action add <ID> priopktnew <Dot1q>

Legend:
• <portNum>: User Ethernet port number where MPLS traffic ingresses MPR
equipment. In case of more than one port, an entry of the command must be used for
each port. Core Switch range: 6,7,18,19,20,21. See Switch to equipment ports
assignment for association with port name; mandatory.
among different rules; mandatory;
• <ingPbm>: User Ethernet ports bitmap where MPLS traffic ingresses MPR
equipment, see Table 4.13, must be the same ports defined by <portNum>;
mandatory;
• <n>: 0-2-4-6-8-a-c-e values related to 0-1-2-3-4-5-6-7 values of TC field; mandatory;
• <Dot1p>: 802.1p bits decimal value [0-7]; mandatory
ingPbm ingPbm
ge5 0x40 ge5,ge6 0xc0
ge6 0x80 ge17,ge18 0xc0000
ge17 0x40000 ge19,ge20 0x300000
ge18 0x80000 ge17-ge20 0x3c0000
ge19 0x100000 ge5,ge6,ge17-ge20 0x3c00c0

ge20 0x200000 — —
same as for “enhanced_eth_feature.psh”, with addition of <SLOT-1>: in the command

syntax and use of applicable EASv2 User ports as specified in Switch to equipment ports
assignment.
Legend:
• <portNum>: User Ethernet port number where MPLS traffic ingresses MPR
equipment. In case of more than one port, an entry of the command must be used for
each port. EASv2 Switch range: 6,7,8,9,10,11,18,19. See Switch to equipment ports
assignment for association with port name; mandatory;
• <ingPbm>: User Ethernet ports bitmap where MPLS traffic ingresses MPR
equipment, see Table 4.14, must be the same ports defined by <portNum>;
mandatory;

ingPbm ingPbm
ge5 0x40 ge5,ge6 0xc0
ge6 0x80 ge7,ge8 0x300
ge7 0x100 ge9,ge10 0xc00

ge8 0x200 ge17,ge18 0xc0000
ge9 0x400 ge5-ge8 0x3c0
ge10 0x800 ge9,ge10,ge17,ge18 0xc0c00
ge17 0x40000 — —
ge18 0x80000 — —
4.11.5 — Mapping MPLS TC field to Ethernet switch queues

bcm fp qual <ID> userdefined 1 0x00000<n>00 0x00000e00
bcm fp action add <ID> cosqnew <queue>
Legend:
• <ingPbm>: User Ethernet interfaces bitmap where MPLS traffic ingresses MPR
equipment; see Table 4.13; mandatory;
• <queue>: Ethernet switch queue, decimal value [0-4]; mandatory
bcm <SLOT-1>: fp entry create 5 <ID>

bcm <SLOT-1>: fp qual <ID> inports <ingPmb> 0x3fffff
bcm <SLOT-1>: fp qual <ID> ethertype 0x8847 0xffff
bcm <SLOT-1>: fp qual <ID> userdefined 1 0x00000<n>00 0x00000e00
bcm <SLOT-1>: fp action add <ID> cosqnew <queue>
bcm <SLOT-1>: fp entry install <ID>
Legend:
• <ingPbm>: User Ethernet interfaces bitmap where MPLS traffic ingresses MPR
equipment; please refer to Table 4; mandatory;
• <queue>: Ethernet switch queue, decimal value [0-4]; mandatory.
4.11.6 — Example
#Remove EASv2 electrical User ports 1,2,3,and 4 from 802.1p to queues mapping
bcm 5: fp entry remove 50
bcm 5: fp qual 50 inports 0x3ffc3f 0x3fffff

bcm 5: fp entry reinstall 50
#Preliminary Configuration
bcm 5: fp qset clear
bcm 5: fp qset add userdefined 1
bcm 5: fp qset add inports
bcm 5: fp qset add ethertype
bcm 5: fp group create 8 4 1
bcm 5: fp qset clear
bcm 5: fp qset add userdefined 1
bcm 5: fp qset add inports
bcm 5: fp qset add ethertype
bcm 5: fp group create 10 5 1
# Enable 802.1p bits remarking on electrical User port 1 to User port 4 (ge5, ge6, ge7 and
ge8) of EASv2
bcm 5: port 6 1 USE_INCOMING_DOT1P=0

#Mapping of outer MPLS TC 7 into PCP 7 of VLAN Tag
bcm 5: fp entry create 4 512
bcm 5: fp qual 512 inports 0x3c0 0x3fffff
bcm 5: fp qual 512 ethertype 0x8847 0xffff
bcm 5: fp qual 512 userdefined 1 0x00000e00 0x00000e00
bcm 5: fp action add 512 priopktnew 7
bcm 5: fp entry install 512
bcm 5: fp qual 513 userdefined 1 0x00000c00 0x00000e00
bcm 5: fp qual 514 inports 0x3c0 0xffff
bcm 5: fp qual 514 ethertype 0x8847 0x3fffff
bcm 5: fp qual 514 userdefined 1 0x00000a00 0x00000e00

bcm 5: fp qual 515 userdefined 1 0x00000800 0x00000e00

#Mapping of outer MPLS TC 7 to Queue 5
bcm 5: fp qual 640 userdefined 1 0x00000e00 0x00000e00
bcm 5: fp action add 640 cosqnew 4
bcm 5: fp qual 641 userdefined 1 0x00000c00 0x00000e00
bcm 5: fp qual 642 userdefined 1 0x00000a00 0x00000e00




5 — Appendix
5.1 — Configuration File No Restart tool

Configuration File No Restart is a tool that can be used within MPR CT/JUSM that
improves Enhanced Configuration Management as it allow to:
• apply CT Users Security Management

• apply Local Access Control Management (when Network Manager is supervising the
NE)
• avoid NE restart when Delta Configuration is applied
The overall Enhanced Configuration management is still according to what defined in

Management of enhanced Configuration File, the tool is just making easy it as it hides the
FTP and Telnet session needed to transfer configuration files and execute related
commands.
Configuration files managed by Configuration File No Restart tool must:
• be text files
• have *.psh extension
• contain only commands executable on a shell interface, e.g. bcm, setreg
Files managed by CTNR tool are transferred only to and from the directory foreseen for
Configuration File (see section Configuration File path in NE File System)
The tool works assuming the NE is reachable at IP level.
It is available only for Administrator Profile (CT and NM)
Note: The tool is not meant for general distribution with MPR SW Package, but only for
use for dedicated customers under Alcatel-Lucent control.
For this reason to enable it on CT the following operation must be done:
The tool can be used if the following lines are present in the JUSM_config.properties file

Configuration File No Restart tool
Then, a new menu item appears under the menu Configuration called CFNR Tool.
5.1.1 — Tool Launch on JUSM

From Configuration Menu, select CFNR Tool Menu Item, see Figure 5.1.
Figure 5.1 — Configuration File No Restart Tool Launch
5.1.2 — Main view

Figure 5.2 — Main view
The following commands are available for configuration file management
1. Append Command
execute and append new commands on the file selected in the right part of the screen
2. AddFile
execute commands and save the file in NE flash
3. Copy to Local PC
copy in local workspace area the file selected on NE flash
5.1.3 — How to perform Delta Configuration without NE Restart

Figure 5.3 — Delta Configuration Operation 1/3
To perform Delta Configuration without NE Restart, the following steps must be followed:
1. Add new commands on an empty local file

2. Save the file on local repository
3. Select file to update on NE flash
4. Click on Append Commands button
5. Prompt for User confirmation.
After user confirmation:
• the console is shown

• the commands are applied on NE
• the commands are saved on the file on NE flash

The file on NE flash has been updated with executed commands, as it can seen by looking
at blue box in below picture:

File Transfer Manager tool
5.1.4 — Import/Export of Enhanced Configuration files

Select File Menu in Main View, see Main view:
1. By clicking on Import Menu it's possible to import in the local workspace files
previously saved on PC FileSystem, USB key, CD....
2. By clicking on Export Menu it's possible to save on PC File System or other devices
the file present on local repository.
5.2 — File Transfer Manager tool

File Transfer Manager (FTM) tool that can be used within MPR CT/JUSM to improves
Enhanced Configuration Management as it allow to:
• apply CT Users Security Management

• apply Local Access Control Management (when Network Manager is supervising the
NE)
The overall Enhanced Configuration management is still according to what defined in

Management of enhanced Configuration File, the tool is just making easy it as it hides the
FTP session needed to transfer configuration files.
Configuration files managed by File Transfer Manager tool must:
• be text files, binary files are not supported
No restriction instead applies for extension and the command syntax.
Files managed by FTM tool are transferred only to and from the directory foreseen for Flag
File and Configuration File (see Flag File path in NE File System and Configuration File
path in NE File System).
The main difference with the CF No Restart tool is the this one allows to append new
commands to existing Configuration Files. FTM instead just allows to move Configuration
Files from/to the NE.
The tool works assuming the NE is reachable at IP level.
It is available only for Administrator Profile (CT and NM)
Note: The tool is not meant for general distribution with MPR SW Package, but only for
use for dedicated customers under Alcatel-Lucent control.
For this reason to enable it on CT the following operation must be done:
The tool can be used if the following lines are present in the JUSM_config.properties file
Then, a new menu item appears under the menu Configuration called FTM Tool.
5.2.1 — Tool Launch on JUSM

From Configuration Menu, select FTM Tool Menu Item, see below figure.

Figure 5.6 — FTM Tool Launch
5.2.2 — Main View

Figure 5.7 — Main view
The following commands are available for configuration file management
1. Add File
Copy the selected file from Local workspace area to NE Flash. If the file is already
existing on NE, the user is prompted for confirmation of overwrite
2. Copy to LocalPC
Copy the selected file on NE from NE Flash to Local workspace area. If the Local
workspace is not empty, the user is prompted for confirmation of overwrite
3. Remove
Delete the selected file on NE from NE Flash or from Local workspace area. The user
is prompted for confirmation of deletion
4. Edit
The text file in the Local workspace can be edited
5. New
A new blank text file can be created in the Local workspace

ATMoMPLS Protocol Stack Configuration by HTTP interface (MPR WebServer)
5.2.3 — Import/Export of Enhanced Configuration files

Select File Menu in Main View:
1. By clicking on Import Menu it's possible to import in the local workspace files
previously saved on PC FileSystem, USB key, CD....
2. By clicking on Export Menu it's possible to save on PC File System or other devices
the file presenton local repository.
5.3 — ATMoMPLS Protocol Stack Configuration by HTTP

interface (MPR WebServer)
Starting from release 2.1.0, the MPR WebServer allows to configure the ATMoMPLS
Protocol Stack in terms of presence/value of the MPLS Tunnel Label, replacing the
previous flag file mechanism.
See Migration Procedure for details about applicable migration procedure that allows to
avoid explicit setting from previous release in case the flag file was used.
This setting is needed not only on the NEs where ATMoMPLS is terminated by ASAP Card
(as it is the ASAP Card that add the MPLS Tunnel Label to all ATM PW frames) but on all
NE where ATM PW traffic is transported (e.g. to enable the specific header compression
on radio cards).
Setting by WebBrowser is based on following procedure:
1. Connect to MPR NE WebServer by a Web Browser like Internet Explorer (NE must
be reachable at IP level)
2. Perform logon procedure supply username and password for a Security Profile that is
enable to modify NE settings, e.g. Administrator/Craftperson Profile
3. A page like the one shown in Figure 5.8 will be displayed.

Figure 5.8 — MPR WebServer Main page
4. Click on “MPLS Setting” link shown in the left part of the screen (below MPLS
item)
5. An HTML page like one in Figure 5.9 will be shown.

Figure 5.9 — MPR WebServer MPLS Setting Page 1/2
6. By supplying an input (in decimal format) in the MPLS Tunnel Label field, the
ATMoMPLS Protocol Stack is configured with the presence of MPLS Tunnel Label.
In case there are ASAP Cards in the NE, such value will be used as common value
for MPLS Tunnel Label by all ATM PWs terminated on that NE.
7. Assuming the MPLS Tunnel Label value = 1000 (decimal format) is given as input
in the MPLS Tunnel Label field and it is accepted by NE, the following HTML page
will be shown:

Figure 5.10 — MPR WebServer MPLS Setting Page 2/2
8. The same operation has to be performed to change the value of MPLS Tunnel Label.
That has effect only in case there are ASAP Cards in the NE, such new value will be
used as common value for MPLS Tunnel Label by all ATM PWs terminated on that
NE.
9. To disable instead the MPLS Tunnel Label presence from ATMoMPLS Protocol
Stack, a value of 0 must be provided in the MPLS Tunnel Label field.


6 — Abbreviations
Table 6.1 — Abbreviations
ABBREVIATION MEANING
AIS Alarm Indication Signal
ALiS Automatic Link Shutdown
AM Adaptive Modulation
AMc Adaptive Modulation Controller
ANSI American National Standards Institute
ASAP Any Service Any Port (ASAP Card)
ATM Asynchronous Transfer Mode

CBR Constant Bit Rate
CD Current Data
CF Configuration File
CT Craft Terminal
CRC Cyclic Redundancy Check
DCC Data Communication Channel
DLF Destination Lookup Failure
DS Differentiated Services
DWRR Deficit Weighted Round Robin
EA Encryption Algorithm
EC Equipment Controller
ECID Emulated Circuit Identifier

ECT Equipment Craft Terminal
EFC Ethernet Flow Control
EPS Equipment Protection Switching

Table 6.1 — Abbreviations (Continued)
ETH Ethernet
ETSI European Telecommunications Standards Institute

EW Early Warning
FAW Frame Alignment Word
FC Flash Card
FCS Frame Check Sequence
FD Frequency Diversity
FE Fast Ethernet
FEC Forward Error Correction
GFP Generic Frame Protocol
HQP High Queue Preempt
HS Hitless Switch
HSB Hot Stand-By
HST Hot Stand-by
IDU InDoor Unit
IMA Inverse Multiplexing for ATM
IP Internet Protocol
IWF InterWorking Function
LAN Local Area Network
LOF Loss Of Frame
LOS Loss Of Signal
MAC Medium Access Control
MC Main Core
MPLS Multi-Protocol Label Switching

NE Network Element
NEC Network Element Clock
NMS Network Management System

NNI Network to Network Interface

NP Network Processor
ODU OutDoor Unit

OH OverHead
PBMP Port BitMaP
PDH Plesyochronous Digital Hierarchy

PDV Packet Delay Variation
PM Performance Monitoring
PNU Packet Node Unit
PTU Packet Transport Unit
PW Pseudo Wire
QoS Quality of Service
RAI Remote Alarm Indication
RDI Remote Defect Indication
REI Remote Error Indication
RMU Removable Memory Unit
RPS Radio Protection Switching
RTP Real Time Protocol
SC Spare Core
SD Space Diversity
SF Signal Fail
SFP Small Form-factor Pluggable
SP Strict Priority
TC Traffic Class
TDM Time Division Multiplex

TMN Telecommunication Management Network
ToS Type of Service
TS Time Slot
UNI User to Network Interface

VLAN Virtual Local Area Network
WRR Weighted Round Robin

XC Cross Connection
A definition of some widely used terms is given below to better glance through this
document.
Administrator: A user who has access rights to all the management domains of the product.
He has access to the whole network and to all the management functionality.
Alarm: A warning of a system malfunction, which may have an immediate or potentially

negative impact on the operation of equipment or the OS.
Alarm Status: Identifies the type and severity of an alarm.
Craft Terminal (CT): Workstation or Personal computer (PC) from which the local access
to an NE is possible. It can be used to configure or perform monitoring tasks on the NE.
EML Application: This application is responsible for the configuration and management of
NEs.
Information Manager (IM): A software unit representing the functional core of an

application (or a part of it), handling the application data processing and its persistency. An
IM opposes itself and provides services to an USM (User Service Manager) in charge of
the dialog with the operator.
Management Information Base (MIB): Describes all the managed objects controlled by the
system. The OS MIB and the NE MIB are typical examples in this system.
Network Element (NE): Either a single telecommunications equipment or part of a

Telecommunications Network, it has characteristics compliant with CCITT
recommendations.
Notification: Spontaneous data received by the system concerning an NE.
Operation System (OS): A system dedicated to the supervision of NEs in a standard way,
using protocols and interfaces. It offers to the operator a set of functions necessary to
supervise the NEs.
Operator: The end-user of the product. He supervises a part of the network that is dependant
on his user profile.

Severity: Linked to the alarms, the severity indicates the magnitude of a failure.
Telecommunication Management Network (TMN): Defines the concept of interoperable

management of TNs. They provide an organized network structure to achieve the
interconnection of the different components of the TN and the services to process the
information.
User Service Manager (USM): These are presentation processes used by PNM to manage
the user interface and facilitate the interaction with the product.

Customer documentation and product
support
Customer documentation
http://www.alcatel-lucent.com/myaccess
Product manuals and documentation updates are available at alcatel-lucent.com. If you
are a new user and require access to this service, please contact your Alcatel-Lucent sales
representative.
Technical support
http://support.alcatel-lucent.com
Documentation feedback
documentation.feedback@alcatel-lucent.com
© 2014 Alcatel-Lucent. All rights reserved.
3DB 19901 BFAA Edition 01

MPR Configuration File Management PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MPR Configuration File Management PDF

Uploaded by

Copyright:

Available Formats

Configuration File Management

Copyright 2014 Alcatel-Lucent.

All rights reserved.

1 — Management of flag file on MPR............................................................................ 21

2 — Management of enhanced Configuration File ........................................................... 25

Configuration 3DB19901BFAA Edition 01 3

3 — Common Assumption ......................................................................................... 39

4 — Features supported through Configuration file management........................................ 45

4 Configuration 3DB19901BFAA Edition 01

Configuration 3DB19901BFAA Edition 01 5

6 — Abbreviations ................................................................................................ 183

6 Configuration 3DB19901BFAA Edition 01

3 — Common Assumption ......................................................................................... 39

4 — Features supported through Configuration file management........................................ 45

Configuration 3DB19901BFAA Edition 01 7

2 — Management of enhanced Configuration File ........................................................... 25

3 — Common Assumption ......................................................................................... 39

4 — Features supported through Configuration file management........................................ 45

6 — Abbreviations ................................................................................................ 183

Configuration 3DB19901BFAA Edition 01 9

Configuration 3DB19901BFAA Edition 01 11

SERVICE PERSONNEL SKILL

This document applies to following product–releases:

12 Configuration 3DB19901BFAA Edition 01

Table 1 — Product Releases

9500 MPR-E 5.2.0

• the configuration files and the procedure to apply them

By the means of this configuration file it will be possible to configure:

• the Ethernet switch inside the CORE,

Commands not described in this document are under user responsibility.

ISSUE DATE DESCRIPTIONS

01 October 2014 Creation for Release 5.2.0

Configuration 3DB19901BFAA Edition 01 13

Table 3 — Handbook structure

Preface It contains general information as preliminary information,

Management of enhanced Describes the management of new features possible through

Common Assumption Describes the Switch to equipment ports assignment.

Features supported through Describes features that can be implemented through

Abbreviations The abbreviation list is supplied.

Index Index references are inserted

Customer Documentation It contains info regarding customer opinions collection about

Safety This section includes all the safety instructions.

General on Customer Documentation

Customer–Independent Standard Customer Documentation

14 Configuration 3DB19901BFAA Edition 01

Plant–dependent and/or Customized documentation, if envisaged by the contract, is

Product levels and associated Customer Documentation

Configuration 3DB19901BFAA Edition 01 15

• A SWP is identified by its “Denomination”, “P/N” (Part Number) and “CS”

Changes introduced in the same product–release (same

16 Configuration 3DB19901BFAA Edition 01

Note: Handbooks relevant to software applications (typically the Operator's Handbooks)

Supplying updated handbooks to Customers

Changes due to new product version

Customer documentation on CD-ROM

Configuration 3DB19901BFAA Edition 01 17

Contents, creation and production of a CD-ROM

• CD-ROMs for Network Management products do not contain:

A CD-ROM is obtained collecting various handbooks and documents in .pdf format.

Suitable checks are made in order to have a virus-free product.

Use of the CD-ROM

18 Configuration 3DB19901BFAA Edition 01

ReadMe info is present on the CD-ROM to this purpose.