MPR 300 Conf File MNGM

Configuration
Configuration File Management

9500 MPR ETSI
3DB 18793 BAAA
Issue 1
Rel.3.0.0
November 2010

Status: RELEASED
All rights reserved.
Passing on and copying of this document,
use and communication of its contents is not permitted
without written authorization from Alcatel-Lucent.
3DB 18793 BAAA
Issue 1
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent.
All other trademarks are the property of their respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no
responsibility for inaccuracies contained herein.
Copyright 2010 Alcatel-Lucent
Configuration
Table of Contents
9500 MPR ETSI Rel.3.0.0
3DB 18793 BAAA Issue 1 1/162
TABLE OF CONTENTS
LIST OF FIGURES ......................................................................................................................... 5
LIST OF TABLES........................................................................................................................... 7
PREFACE......................................................................................................................................... 9
Preliminary Information.............................................................................................................. 9
Applicability................................................................................................................................. 11
Scope ........................................................................................................................................... 11
Relevant Note.............................................................................................................................. 11
History.......................................................................................................................................... 11
Handbook Structure ................................................................................................................... 12
General on Customer Documentation ...................................................................................... 13
1 MANAGEMENT OF FLAG FILE ON MPR................................................................................... 17
1.1 File Name.............................................................................................................................. 17
1.2 Flag File Format ................................................................................................................... 17
1.3 Flag File upload.................................................................................................................... 17
1.4 FTP connection.................................................................................................................... 17
1.5 How to run a Flag File.......................................................................................................... 18
2 MANAGEMENT OF ENHANCED CONFIGURATION FILE ........................................................ 19
2.1 File Name.............................................................................................................................. 19
2.2 File Format............................................................................................................................ 19
2.3 Configuration File upload and execution .......................................................................... 20
2.4 Configuration File Removal ................................................................................................ 20
2.5 Configuration File update: add a new command/feature................................................. 20
2.6 Configuration File update: remove an existing command/feature.................................. 21
2.7 Restoring Ethernet switch initial configuration................................................................ 21
2.8 Restoring MOD300 initial configuration ............................................................................ 23
2.9 Restoring SFP 2xE1/DS1 configuration............................................................................. 23
2.10 Behavior during SW restart .............................................................................................. 23
2.11 SW package activation ...................................................................................................... 23
2.12 Behavior in CORE protection ........................................................................................... 23
2.13 Behavior in Radio protection............................................................................................ 24
2.14 Behaviour in Ethernet Link Aggregation......................................................................... 24
2.15 Behaviour in Radio Link Aggregation.............................................................................. 24
2.16 TMN enabled on ETH4 port ............................................................................................... 24
2.17 Software package upgrade ............................................................................................... 24
2.18 List of portable/unportable features from previous releases ........................................ 26
2.19 List of new features ........................................................................................................... 27
2.20 Relevant notes ................................................................................................................... 27
3 COMMON ASSUMPTION............................................................................................................ 29
3.1 Switch to equipment ports assignment ............................................................................. 29
3.2 MPT-ACC switch command definition ............................................................................... 30
3.3 SFP 2E1/DS1 command definition ..................................................................................... 31
4 FEATURES SUPPORTED THROUGH CONFIGURATION FILE MANAGEMENT..................... 33
4.1 QinQ...................................................................................................................................... 33
4.1.1 Preliminary configuration ................................................................................................ 33
4.1.2 TPID setting.................................................................................................................... 34
4.1.3 Port configuration............................................................................................................ 34
4.1.4 VLAN Table management ............................................................................................... 35
Configuration
Table of Contents
3DB 18793 BAAA Issue 1 2/162
4.1.5 QINQ management usage examples ............................................................................. 36
4.2 Autonegotiation on SFP port .............................................................................................. 48
4.2.1 Overview......................................................................................................................... 48
4.2.2 Disable Auto-Negotiation example ................................................................................. 48
4.2.3 Re-Enable Auto-Negotiation example ............................................................................ 49
4.3 VLAN SWAP.......................................................................................................................... 50
4.3.2 Enable VLAN swap......................................................................................................... 50
4.3.3 VLAN Creation................................................................................................................ 51
4.3.4 Create an ingress VLAN swap rule................................................................................. 51
4.3.5 Create an ingress VLAN swap rule pushing the VLAN tag............................................. 52
4.3.6 Create an egress VLAN swap rule ................................................................................. 52
4.3.7 Enable VLAN swap miss drop ........................................................................................ 53
4.3.8 Port enabling................................................................................................................... 53
4.3.9 VLAN SWAP usage examples........................................................................................ 53
4.3.10 QinQ + VLAN SWAP usage examples ......................................................................... 61
4.4 OUT OF RANGE VLAN SWAP............................................................................................. 68
4.4.1 Background..................................................................................................................... 68
4.4.3 Port configuration............................................................................................................ 69
4.4.4 VLAN Table management ............................................................................................... 71
4.4.5 Admit out of range VLAN................................................................................................ 71
4.4.6 Manage in range VLAN on user UNI .............................................................................. 72
4.4.7 User UNI Port enable command..................................................................................... 72
4.4.8 Example of configuration for VLAN 4092 Swap.............................................................. 72
4.5 VLAN SWAP AND DOT1P REMARKING FOR ATM PW SERVICE.................................... 75
4.5.1 Background..................................................................................................................... 75
4.5.2 Migration Procedure ....................................................................................................... 75
4.5.4 Enable 802.1p bit remarking........................................................................................... 77
4.5.5 VLAN swap and 802.1p remarking for Egress Direction ................................................ 77
4.5.6 VLAN swap and 802.1p remarking for Ingress Direction................................................ 79
4.5.7 Example of configuration for VLAN Swap for ATM PW Service ..................................... 81
4.6 VLAN SWAP AND FORWARDING FOR "LOCAL ATM SWITCH"...................................... 83
4.6.1 Background..................................................................................................................... 83
4.6.3 VLAN swap and frame forwarding.................................................................................. 83
4.6.4 Example of configuration for "Local" ATM Switch........................................................... 85
4.7 PORT BASED RATE LIMITING............................................................................................ 88
4.7.2 Ingress/Egress port rate limiting ..................................................................................... 88
4.8 STORM CONTROL ............................................................................................................... 89
4.8.1 Broadcast Storm Control................................................................................................. 89
4.8.2 Multicast Storm Control................................................................................................... 89
4.8.3 DLF Storm Control .......................................................................................................... 90
4.9 ACCESS CONTROL LIST .................................................................................................... 92
4.9.2 Feature activation ........................................................................................................... 92
4.9.3 Define an entry in the ACL.............................................................................................. 93
4.10 PER VLAN RATE LIMITING ............................................................................................... 94
4.10.1 Preliminary configuration .............................................................................................. 94
4.10.2 Create a VLAN rate limiter entry................................................................................... 94
4.11 SCHEDULER SETTING...................................................................................................... 96
4.11.1 Preliminary information ................................................................................................. 96
Configuration
Table of Contents
3DB 18793 BAAA Issue 1 3/162
4.11.2 Default configuration ..................................................................................................... 96
4.11.3 Switch configuration...................................................................................................... 97
4.11.4 MOD300 configuration .................................................................................................. 98
4.12 MAPPING 802.1p TO QUEUES.......................................................................................... 99
4.12.1 Default configuration..................................................................................................... 99
4.12.3 MOD300 configuration.................................................................................................. 106
4.13 MAPPING DiffServ TO QUEUES FOR IPv4 FRAMES...................................................... 107
4.13.1 Default configuration..................................................................................................... 107
4.14 IPv6 QoS SUPPORT WITH FLEXIBLE MAPPING TRAFFIC CLASS TO QUEUES......... 112
4.14.1 Preliminary configuration .............................................................................................. 112
4.15 SFP 2E1/DS1 CIRCUIT EMULATION................................................................................. 117
4.15.1 Description.................................................................................................................... 117
4.15.2 Normal procedure......................................................................................................... 117
4.15.3 Configuration File basic structure ................................................................................. 118
4.15.4 Blue Signal configuration.............................................................................................. 134
4.15.5 Example........................................................................................................................ 135
4.16 ALARM SEVERITY ASSIGNMENT PROFILE.................................................................... 141
4.16.1 Description.................................................................................................................... 141
4.16.2 Normal procedure......................................................................................................... 141
4.16.3 File content ................................................................................................................... 141
4.16.4 Example........................................................................................................................ 144
5 APPENDIX.................................................................................................................................... 145
5.1 Configuration File No Restart tool ..................................................................................... 145
5.1.1 Tool Launch on JUSM..................................................................................................... 146
5.1.2 Main view........................................................................................................................ 147
5.1.3 How to perform Delta Configuration without NE Restart................................................. 148
5.1.4 Import/Export of Enhanced Configuration files ............................................................... 150
5.2 ATMoMPLS Protocol Stack Configuration by HTTP interface (MPR WebServer) .......... 151
ABBREVIATIONS ............................................................................................................................ 155
INDEX............................................................................................................................................... 159
CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 161
Configuration
Table of Contents
3DB 18793 BAAA Issue 1 4/162
Configuration
List of Figures
3DB 18793 BAAA Issue 1 5/162
LIST OF FIGURES
Figure 1. ........................................................................................................................................... 117
Figure 2. Configuration File Tool Launch .......................................................................................... 146
Figure 3. Main view........................................................................................................................... 147
Figure 4. Delta Configuration Operation 1/3 ..................................................................................... 148
Figure 7. MPR WebServer Main page .............................................................................................. 151
Figure 8. MPR WebServer MPLS Setting Page 1/2 ......................................................................... 152
Figure 9. MPR WebServer MPLS Setting Page 2/2 ......................................................................... 153
Configuration
List of Figures
3DB 18793 BAAA Issue 1 6/162
Configuration
List of Tables
3DB 18793 BAAA Issue 1 7/162
LIST OF TABLES
Table 1. ............................................................................................................................................ 77
Table 2. ............................................................................................................................................ 78
Table 3. ............................................................................................................................................ 80
Table 4. ............................................................................................................................................ 80
Table 5. ............................................................................................................................................ 80
Table 6. ............................................................................................................................................ 93
Table 7. ............................................................................................................................................ 95
Table 8. Compatibility table between 32E1 PDH card and 2xE1/DS1 SFP Module.......................... 133
Table 9. Compatibility table between two 2xE1/DS1 SFP modules .................................................. 133
Table 10. Severity table..................................................................................................................... 141
Table 11. Alarm IDs........................................................................................................................... 143
Configuration
List of Tables
3DB 18793 BAAA Issue 1 8/162
Configuration
Preface
3DB 18793 BAAA Issue 1 9/162
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, inci-
dental, 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 cop-
ied, reproduced or disclosed to a third party without written consent.
TECHNICAL SUPPORT
Please contact your Local Alcatel Technical Assistance Center for questions reffered to the infor-
mation contained in this document.
To send your comments about this handbook please follow the indication on Customer Documen-
tation 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 prevent-
damaging the equipment.
Configuration
Preface
3DB 18793 BAAA Issue 1 10/162
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 pre-
vail. Should not local regulations be mandatory, then safety rules stated in this manual will pre-
vail.
SERVICE PERSONNEL SKILL
Service Personnel must have an adequate technical background on telecommunications and in par-
ticular on the equipment subject of this handbook.
An adequate background is required to properly install, operate and maintain equipment. The fact
of merely reading this handbook is considered as not enough.
Configuration
Preface
3DB 18793 BAAA Issue 1 11/162
Applicability
This document applies to 9500MPR R.3.0.0.
This document applies to following productreleases:
PRODUCT
9500 MPR-E
PRODUCT RELEASE
9500 MPR-E 3.0.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 FPGA inside the Modem 300 board
SFP 2xE1/DS1 module
in order to obtain a specific behaviour unobtainable with the supported configuration tools.
Relevant 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 responsability.
History
ISSUE DATE DESCRIPTIONS
01 October 2010 Creation for Release 3.0.0
Configuration
Preface
3DB 18793 BAAA Issue 1 12/162
Handbook Structure
This handbook has been edited according to the Alcatel-Lucent standardized drawing-up guides" com-
plying with such suggestion.
This handbook is divided into the main topics described in the table of contents:
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
Configuration File
Describes the management of new features possible through con-
figuration file.
Common Assumption Describes the Switch to equipment ports assignment.
Features supported through
Configuration file management
Describes features tha can be implemented through configuration
files and how to implement them.
Abbreviations The abbreviation list is supplied.
Index Index references are inserted
Customer Documentation
Feedback
It contains info regarding customer opinions collection about this
document
Safety This section includes all the safety instructions.
Configuration
Preface
3DB 18793 BAAA Issue 1 13/162
General on Customer Documentation
This paragraph describes in general the AlcatelLucent Customer Documentation system, details the
association between the product levels and the associated documentation, and explains Customer Doc-
umentation characteristics as well as the policies for its delivery and updating.
CustomerIndependent Standard Customer Documentation
a) Definition
Standard Customer Documentation, referred to hereafter, must be always meant as plantindepen-
dent and is always independent of any Customization.
Plantdependent and/or Customized documentation, if envisaged by the contract, is subjected to
commercial criteria as far as contents, formats and supply conditions are concerned.
N.B. Plantdependent 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 maintain-
ing the equipment according to AlcatelLucent Laboratory design and Installation Dept. choices. In
particular:
the contents of the chapters associated to the software applications focus on the explanation
of the manmachine interface and of the operating procedures allowed by it;
maintenance is described down to faulty PCB location and replacement.
N.B. No supply to Customers of design documentation (like PCB hardware design andproduction
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 productreleases, which are the real products marketed
for their delivery at a certain productrelease availability date. A certain productrelease performs
more functionalities than the previous one.
E.g. Rel.1.0 and Rel.2.0 are two successive productreleases of the same product.
A productrelease comprehends a set of hardware components and at least one Software Pack-
age (SWP); as a whole, they identify the possible network applications and the equipment perfor-
mances that the specific productrelease has been designed, engineered, and marketed for.
c) Configurations and Network Elements
In some cases, a productrelease includes different possible configurations which are distin-
guished from one another by different Network Element (NE) types and, from the management
point of view, by different SWPs.
d) SWP releases, versions, and CDROMs
Each SWP is distributed by means of a specific SWP CDROM.
A SWP is identified by its Denomination, P/N (Part Number) and CS (Change Status), that
are printed on the CDROMs 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.
Configuration
Preface
3DB 18793 BAAA Issue 1 14/162
A SWP with new Version Level, providing main features in addition to those of the previous Ver-
sion Level SWP, is distributed by means of a SWP CDROM 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, andis
distributed by means of a SWP CDROM, that can be identified:
by the same P/N of the former CDROM, 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 "productrelease" (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 productrelease (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 edi-
torial 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 on page 11.;
in affected chapters, revision bars on the left of the page indicate modifications in text and draw-
ings.
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 edi-
tions.
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
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 productrelease'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 (sup-
plying errata-corrige sheets is not envisaged).
Configuration
Preface
3DB 18793 BAAA Issue 1 15/162
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 eletronic 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(-ver-
sion)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 applicative 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.
Configuration
Preface
3DB 18793 BAAA Issue 1 16/162
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 previous para. point 2) , 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 com-
posing the collection.
Configuration
Management of flag file on MPR
3DB 18793 BAAA Issue 1 17/162
1 Management of flag file on MPR
1.1 File Name
Flag files are empty files without any extension and they must be created on PC (Windows or Linux or
MAC).
The ones reported below refers to features managed in previous release (pre MPR-E 2.1.0):
ENABLE_16E1
mpls_label_enable
MPR 3.0.0 release support a single flag file in order to select the market type between ANSI and ETSI.
1.2 Flag File Format
The flag files are empty file, they must be created on PC (Windows or Linux or MAC). The content of the
flag file must be empty (file size 0 bytes). File needs to be created with the proper name in order to enable
the specific functionality. System is case sensitive, please take care if capital letters when used.
1.3 Flag File upload
The flag files must be uploaded to the Compact Flash (on main CORE when it is active) via FTP con-
nection (please refer to 1.4). The flag files must be put in the EC compact flash inside the following direc-
tory /home/adm-lc-ng/debug.
1.4 FTP connection
Using any FTP client (e.g. FileZilla) it is possible to connect to the NE using the following information:
User Id: ftp
Password: ftp
Address: NE IP address
Port: 21
Configuration
Management of flag file on MPR
3DB 18793 BAAA Issue 1 18/162
1.5 How to run a Flag File
In order to run (apply) a flag file, a switch off/on operation is needed.
Configuration
Management of enhanced Configuration File
3DB 18793 BAAA Issue 1 19/162
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 follow based 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
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 cre-
ated on PC (Windows or Linux or MAC) . The content of the configuration file is formed by a list of com-
mands each of them using a different line.
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.
Configuration
3DB 18793 BAAA Issue 1 20/162
2.3 Configuration File upload and execution
Configuration files must be uploaded to the Compact Flash (on main CORE when it is active) via Con-
figuration File No Restart tool (please refer to APPENDIX 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 at para-
graph 2.1. 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.
Differently from what has been described above, def_asap4.psh upload requires an FTP connection to
the NE in order to upload it into the Flash Card. Please refer to paragraph 1.4 since the procedure
described for flag files applies also to this configuration file.
Configuration files are not part of NE Backup feature.
2.4 Configuration File Removal
Configuration files can be removed from the Compact Flash (on main CORE when it is active) via Con-
figuration 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 fea-
tures please refer to paragraph 2.7/2.8/2.9. Simply removing configuration file from Compact Flash
doesn't imply the removal of all features applied by configuration file itself.
Differently from what has been described above, def_asap4.psh removal requires an FTP connection to
the NE in order to remove it from the Flash Card. Please refer to paragraph 1.4.
2.5 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 refer to 2.7/2.8.
The operator is allowed to append a new command on one of the following and already in use configu-
ration files:
enhanced_eth_feature.psh
fullConfig_mptacc.psh
fullConfig_radio.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 command order shown later at paragraph 4.15.3.
Not following that scheme causes a wrong SFP module configuration and the service is not established.
Configuration
3DB 18793 BAAA Issue 1 21/162
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 4.15.3 and then
uploaded as new complete file in the NE using "AddFile".
Any configuration file update operation may cause a temporary traffic impact.
N.B. Do not switch the CORE Board after Configuration File upload, until the new Configuration File
is applied.
2.6 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_mptacc.psh
fullConfig_radio.psh
it is necessary to follow the procedure described below:
restore the initial configuration of the switch or radio (see 2.7/2.8).
upload a new configuration file if necessary according to the procedure described in 2.3.
On the other side, this procedure does not apply to SFP 2xE1/DS1 configuration files. Whenever the oper-
ator 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 2.4) and the upload of the new
configuration file(s) according to paragraph 2.3.
N.B. Do not switch the CORE Board after Configuration File upload, until the new Configuration File
is applied.
2.7 Restoring Ethernet switch initial configuration
To restore the initial configuration of CORE 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 and MPT-ACC CFs must be removed from flash card (see 2.4);
2) both CORE and MPT-ACC "restoring CF" (see below) must be executed on the NE (see 2.3);
3) both CORE and MPT-ACC "restoring CF" must be removed from flash card (see 2.4).
After this, the user must perform a NE restart by CT/NMS to completely remove the effect of configuration
file.
restoring "enhanced_eth_feature.psh" configuration file:
#start enhanced configuration file
setreg 00500001 0001
Configuration
3DB 18793 BAAA Issue 1 22/162
#end enhanced configuration file
restoring "fullConfig_mptacc.psh " configuration file:
setreg S0300300 0000
In case the system is equipped with multiple MPT-ACC plug-in, in order to restore the original configu-
ration of the MPT-ACC plug-in, the command above have to be replicated for all MPT-ACC 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 on the NE 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.
restoring "enhanced_eth_feature.psh" configuration file (AUX card case):
setreg 00500001 0001
setreg S0300300 0001
Where S nibble assumes the following value based on AUX card slot position:
S=0x3 if the Radio Board is inserted into slot 4 (second column, second row)
S=0x7 if the Radio Board is inserted into slot 8 (second column, fourth row)
Configuration
3DB 18793 BAAA Issue 1 23/162
2.8 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 2.4);
2) per feature "restoring CF" must be executed on the NE (see 2.3);
3) "restoring CF" must be removed from flash card (see 2.4).
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 clear-
ing 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 Behavior during SW restart
A traffic hit may occur during "NE restart".
2.11 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.12 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 becom-
ing active will have enhanced features already configured.
At the same time, a different behaviour is supported for 2xE1/DSI SFP since there are dedicated config-
uration file for CORE Main and CORE Spare (see paragraph 2.1)
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 con-
figuration files for both Main and Spare must be present.
Configuration
3DB 18793 BAAA Issue 1 24/162
2.13 Behavior in Radio protection
Regarding the configuration file for MOD300 and MPT-ACC board (fullConfig_radio.psh and
fullConfig_mptacc.psh), the Board Spare 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.
2.14 Behaviour 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.15 Behaviour in Radio Link Aggregation
All commands to be applied to a radio LAG inserted into fullConfig_mptacc.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.
2.16 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.17 Software package upgrade
Configuration
3DB 18793 BAAA Issue 1 25/162
This paragraph describes how to upgrade an old Software Package with MPR 3.0.0. The block diagram
above shows the operation to be performed in order to activate the configuration file on top of MPR 3.0.0.
The same diagram shows the only allowed update procedures.
1) Passing from MPR-E 2.1.0 (or or previous) to MPR 3.0.0, it is necessary to follow normal soft-
ware package upgrade procedure.
2) In order to activate CF on top of a specific release, do as follows:
a) for MPR-E 1.2.2 please refer to "MPR-E r1.2.2 Enhanced Configuration" (3DB 18649
0000 TQZZA)
b) for MPR-E 1.3.0 please refer to "MPR-E r1.3.0 Enhanced Configuration" (3DB 18649
0001 TQZZA)
c) for MPR-E 1.4.0 please refer to "MPR-E r1.4.0 Enhanced Configuration" (3DB 18648
0002 DSZZA)
d) for MPR-E 2.1.0 please refer to "MPR-E r2.1.0 Enhanced Configuration" (3DB 18648
0003 DSZZA)
e) for MPR 3.0.0 please refer to the indications reported inside this document.
3) In order to update an existing MPR-E CF release, do as follows:
a) for MPR-E 1.2.2 CF updated with:
i) MPR-E 1.3.0 CF please refer to "MPR-E r1.3.0 Enhanced Configuration" (3DB
18649 0001 TQZZA) for MPR-E 1.3.0;
ii) MPR-E 1.4.0 CF please refer to "MPR-E r1.4.0 Enhanced Configuration" (3DB
18648 0002 DSZZA) for MPR-E 1.4.0;
iii) MPR-E 2.1.0 CF please refer to "MPR-E r2.1.0 Enhanced Configuration" (3DB
18648 0003 DSZZA) for MPR-E 2.1.0
b) for MPR-E 1.3.0 CF updated with:
i) MPR-E 1.4.0 CF no special actions are required, so configuration files running on
MPR-E 1.3.0 CF can be fully supported by these new releases;
ii) MPR-E 2.1.0 CF no special actions are required, so configuration files running on
MPR-E 1.3.0 CF can be fully supported by these new releases;
c) for MPR-E 1.4.0 CF updated with
i) MPR-E 2.1.0 CF, no special actions are required, so configuration files running on
MPR-E 1.4.0 CF can be fully supported by MPR-E 2.1.0 CF;
ii) MPR 3.0.0 0 please refer to this document; once configuration files have been
adapted according to the indications here reported, the new software package can
be activated;
d) for MPR-E 2.1.0 updated with MPR 3.0.0 0 please refer to this document; once configu-
ration files have been adapted according to the indications here reported, the new soft-
ware package can be activated.
4) In order to restore an official MPR-E Release please refer to:
Configuration
3DB 18793 BAAA Issue 1 26/162
a) "MPR-E r1.2.2 Enhanced Configuration" (3DB 18649 0000 TQZZA) for MPR-E 1.2.2;
b) "MPR-E r1.3.0 Enhanced Configuration" (3DB 18649 0001 TQZZA) for MPR-E 1.3.0;
c) "MPR-E r1.4.0 Enhanced Configuration" (3DB 18648 0002 DSZZA) for MPR-E 1.4.0;
d) "MPR-E r2.1.0 Enhanced Configuration" (3DB 18648 0003 DSZZA) for MPR-E 2.1.0;
e) paragraphs 2.7 and 2.8 inside this document for MPR 3.0.0.
N.B. if all "not portable" features running in the current release are not adapted to the destination
release before executing the software upgrade, inconsistent behaviour or unrecoverable traffic
impact may be experienced. So, it is extremely important to update configuration file if neces-
sary and pay attention to this document's guidelines.
2.18 List of portable/unportable features from previous releases
Here below is shown the list of portable features from pre MPR 3.0.0 releases.
Feature MPR-E
1.2.2
MPR-E
1.3.0
MPR-E
1.4.0
MPR-E
2.1.0
1 Q
IN
Q YES YES YES YES
2 Autonegotiation on SFP port n.a. YES YES YES
3 VLAN swap YES YES YES YES
4 Out of Range VLAN swap n.a. YES YES YES
5 VLAN swap and dot1p Remarking for ATM PW Service n.a. YES YES YES
6 VLAN swap and forwarding for local ATM switch" n.a. n.a. YES YES
7 Port Based Rate Limiting n.a. n.a. YES YES
8 Storm Control n.a. n.a. YES YES
9 Acess Control List n.a. n.a. YES YES
10 Per VLAN rate limiting n.a. n.a. YES YES
11
Ethernet Switch Scheduler Setting YES YES YES YES
MOD300 Scheduler Setting NO YES YES YES
12
Ethernet Switch 802.1p Mapping to Queues NO NO NO NO
MOD300 802.1p Mapping to Queues YES YES YES YES
13
Ethernet Switch Mapping DiffServ to Queues for IPv4 frames NO NO NO NO
MOD300 Mapping DiffServ to Queues for IPv4 frames YES YES YES YES
14
Ethernet Switch IPv6 QoS support with flexible mapping traffic class to
queues
NO NO NO NO
MOD300 IPv6 QoS support with flexible mapping traffic class to queues YES YES YES YES
Configuration
3DB 18793 BAAA Issue 1 27/162
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 3.0.0.
2.19 List of new features
The new features introduced in MPR 3.0.0 CF, with respect to those available in MPR-E 2.1.0 CF, are:
Circuit Emulation for SFP 21/DS1 module (chapter 4.15)
Alarm Severity Assignment Profile (chapter 4.16)
2.20 Relevant notes
MPR 3.0.0 introduces the second optical port not supported by all the previous releases of MPR. For this
reason, all configuration files valid for any previous release may need to be updated according to what
is reported into this guide if any previous release, once migrated to MPR 3.0.0, required the second optical
port.
On the contrary, if any previous release migrated to MPR 3.0.0 does not require the second optical port
the configuration files do not need to be updated unless otherwise stated in paragraph 6.18.
Ethernet Connectivity Fault Management is not for supported for any VLAN created by configuration file.
This new feature introduced in MPR 3.0.0 is supported only for services created by CT/NMS and CLI.
Configuration
3DB 18793 BAAA Issue 1 28/162
Configuration
Common Assumption
3DB 18793 BAAA Issue 1 29/162
3 Common Assumption
3.1 Switch to equipment ports assignment
CORE MPT-ACC
Port Name Port Number Port Name Port Number
ge11 12 ge5 6
ge12 13 ge6 7
ge13 14 ge7 8
ge14 15 ge8 9
ge15 16 ge9 10
ge16 17
ge17 18
ge18 19
ge19 20
ge20 21
MSS-8 shelf description.
Slot 1 Slot 2
Slot 3 Slot 4
Slot 5 Slot 6
Slot 7 Slot 8
Configuration
Common Assumption
3DB 18793 BAAA Issue 1 30/162
MSS-4 shelf description.
Slot 1 Slot 2
Slot 3 Slot 4
3.2 MPT-ACC switch command definition
Not all the commands reported inside this guide are valid for MPT-ACC switch. For this reason, all com-
mands 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 only and so it must
be inserted into "enhanced_eth_feature.psh" only.
In order to apply a command to MPT-ACC 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 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. So, it is required to specify the correct SLOT number
MPT-ACC is lodged for each preliminary configuration command. In case of multiple MPT-ACC, the pre-
liminary configuration must be replicated for all MPT-ACC present into the system changing the SLOT
number accordingly.
Configuration
Common Assumption
3DB 18793 BAAA Issue 1 31/162
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:
Y=0: used inside SFP_2xE1DS1_0_1.psh and SFP_2xE1DS1_0_2.psh files used to contain respec-
tively 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 respec-
tively 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 con-
figuration 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 con-
figuration 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 fol-
lowing 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
Configuration
Common Assumption
3DB 18793 BAAA Issue 1 32/162
Configuration
Features supported through Configuration file man-
3DB 18793 BAAA Issue 1 33/162
4 Features supported through Configuration file
management
4.1 QinQ
To properly configure QinQ feature inside the MPR this procedure should be followed:
1) Preliminary configuration
2) TPID setting
3) Port configuration (UNI, NNI)
4) S-VLAN definition
5) S-VLAN priority definition
4.1.1 Preliminary configuration
In order to manage the QinQ capabilities with configuration file the NE must be configured in 802.1D
bridge mode by CT/NMS. Additionally, to manage the QoS according the 802.1p value the NE must be
properly configured by CT/NMS.
All the service VLANs will be configured by configuration file.
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
Preliminary configuration of "fullConfig_mptacc.psh":
# configure all ports as NNI.
Configuration
3DB 18793 BAAA Issue 1 34/162
bcm <SLOT-1>: dtag mode ge5 internal
bcm < SLOT-1>: dtag mode ge6 internal
4.1.2 TPID setting
In Q-in-Q bridging mode, it is required to define a TPID value. The default is 0x8100. The same TPID on
all permitted ports should be used. Changing TPID on MOD300, MPT-ACC, ASAP, AUX and PDH ports
is forbidden.
bcm dtag tpid <pbm> <ex value>
<pbm>: list of possible ports; range: ge5,ge6, ge17, ge18, ge19, ge20; mandatory.
<ex value>: TPID value in hexadecimal..
bcm vlan port <pbm> outertpidselect 0
<pbm>: list of possible ports; range: ge5,ge6, ge17, ge18, ge19, ge20;
N.B. This command should not be applied if the TPID=0x8100 (since this value of TPID is the default
value).
Command example:
bcm dtag tpid ge17 0x9100
bcm vlan port ge17 outertpidselect 0
On user port 1 the TPID will be 0x9100. The outer TPID will be the per port configured TPID.
4.1.3 Port configuration
In Q-in-Q bridging mode, each port must be defined as user to network interface (UNI) or network to net-
work interface (NNI).
bcm dtag mode <pbm> <type>
<pbm>: list of possible ports; range: ge5,ge6, ge17, ge18, ge19, ge20 and each slot lodging
a MOD300 or an MPT-ACC; mandatory.
<type>: it is the port definition that can be internal for NNI ports or external for UNI ports; man-
datory.
N.B. Ports from ge11 to ge16 refers to MSS slots; this command must not be applied to ports toward
slot where a PDH, ASAP or AUX cards is lodged. Applying this command toward PDH or ASAP
slots will destroy all the E1/ATM traffic.
Configuration
3DB 18793 BAAA Issue 1 35/162
All radio ports (MOD300 and MPT-ACC) shall be NNI ports.
Command example:
bcm dtag mode ge17 external
bcm dtag mode ge20 internal
bcm port <pbmp> priority=<n> discard=none
<pbmp>: list of possible ports; range: ge5,ge6, ge17, ge18, ge19, ge20; mandatory.
<n>: the possible values are in range 0-7; mandatory.
N.B. The above commands implies always a switch off/on of the involved port; so, anytime the con-
figuration file will be applied a traffic hit will always occurs on the involved port.
bcm pvlan set <pbmp> <vid>
<pbmp>: pbmp is a list of possible ports; range: ge5,ge6, ge17, ge18, ge19, ge20; mandatory.
<vid>: integer number used as VLAN ID; range: 2-4080; mandatory. Vid must have been cre-
ated previously and all ports in <pbmp> must belong to that VLAN.
bcm vlan port <pbmp> useinnerpri <n>
<pbmp>: pbmp is a list of possible ports; range: ge5,ge6, ge17, ge18, ge19, ge20; mandatory.
<n>: 0 the priority used will be the port priority; 1 the priority used will be the C-VLAN priority
if present; mandatory.
Command example:
bcm pvlan set ge17 100
bcm port ge17 priority=3 discard=none
bcm vlan port ge17 useinnerpri 1
The PVLAN=100 will be added on user port 1. For untagged frame the priority will be 3 while for tagged
frame the priority will be copied from C-VLAN.
4.1.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.
Configuration
3DB 18793 BAAA Issue 1 36/162
<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.
<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.
N.B. 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.
Command example:
bcm vlan create 1000 portbitmap=ge11,ge12,ge20 untagbitmap=ge20
The VLAN ID number 1000 will be created; the user port 4 and the slots 4 and 6 will be members of this
VLAN and the frame forwarded by Eth port 4 (with VLAN_ID=1000) will be untagged.
Command example:
bcm 2: vlan create 1000 portbitmap=ge5,ge9
The VLAN ID number 1000 will be created inside MPT-ACC in slot 3; the MPT electrical port1 and port
connected to CORE will be members of this VLAN.
4.1.5 Q
IN
Q management usage examples
4.1.5.1 Use Case A: Two EVC transport
NE1 has the MOD300 inserted in slot 3.
Configuration
3DB 18793 BAAA Issue 1 37/162
Each Equipment transmits untagged and tagged frames and is connected to specific Eth port on NE1:
EQL1=> Eth1; EQL2=> Eth2; EQR1=> Eth1; EQR2=> Eth2;
Inside the MPR network the following provisioning will be done
RED tunnel: S-VLAN ID= 100; S-VLAN PRI= C-VLAN PRI (if the C-VLAN is not present the S-VLAN PRI
will be 011);
BLUE tunnel: S-VLAN ID= 101; S-VLAN PRI= port PRI
TPID=0x8100
Content of "enhanced_eth_feature.psh" for NE1:
#start preliminary configuration
# discard not provisioned traffic on all user ports.
#end preliminary configuration
# Definition of user ports as UNI
# Definition of MOD300 port as NNI
#definition of VLANs on user and radio ports
bcm vlan create 100 pbm=ge17,ge14 ubm=ge17
#definition of Port VLANs.
Configuration
3DB 18793 BAAA Issue 1 38/162
#definition of Port PRI and enable incoming traffic.
bcm port ge17 prio=3 discard=none
# if the C-VLAN is present, copy the C-PRI into S-PRI
# use S-PRI=101
Configuration
3DB 18793 BAAA Issue 1 39/162
# use S-PRI=101
4.1.5.2 Use Case B: Mobile Backhauling
NE2 has the MOD300 inserted in slot 3 and slot 4.
Each BS transmits untagged and Customer tagged frames; the RNC transmits Service Tagged frames:
BS1=> Eth1; BS2=> Eth1; RNC=> Eth1;
will be 001);
BLUE tunnel: S-VLAN ID= 101; S-VLAN PRI= C-VLAN PRI (if the C-VLAN is not present the S-VLAN PRI
will be 001);
Configuration
3DB 18793 BAAA Issue 1 40/162
TPID=0x8100
# Definition of user port as UNI
Configuration
3DB 18793 BAAA Issue 1 41/162
bcm vlan create 100 pbm=ge14,ge11
Configuration
3DB 18793 BAAA Issue 1 42/162
# Definition of MOD300 and user ports as NNI
# enable traffic on specific port
bcm port ge17 discard=none
4.1.5.3 Use Case C: Mobile Backhauling with MPT
NE1 has MPT inserted in slot 3 port1.
NE2 has MPTs inserted in slot 3 port1 and slot 3 port2.
NE3 has MPT inserted in slot 3 port1.
Configuration
3DB 18793 BAAA Issue 1 43/162
Each BS transmits untagged and Customer tagged frames; the RNC transmits Service Tagged frames:
will be 001);
BLUE tunnel: S-VLAN ID= 101; S-VLAN PRI= C-VLAN PRI (if the C-VLAN is not present the S-VLAN PRI
will be 001);
TPID=0x8100
# Definition of user port as UNI
# Definition of MPT-ACC port as NNI
Configuration
3DB 18793 BAAA Issue 1 44/162
Content of "fullConfig_mptacc.psh" for NE1:
#start mpt-acc configuration file
bcm 2: dtag mode ge5 internal
#Create vlan 100 inside MPT-ACC
#end mpt-acc configuration file
Configuration
3DB 18793 BAAA Issue 1 45/162
# Definition of MPT-ACC port as NNI
#Create vlan 100 and 101 inside MPT-ACC slot 3
Configuration
3DB 18793 BAAA Issue 1 46/162
# Definition of Radio and user ports as NNI
# enable traffic on specific port
Configuration
3DB 18793 BAAA Issue 1 47/162
#Create vlan 100 and 101 inside MPT-ACC
Configuration
3DB 18793 BAAA Issue 1 48/162
4.2 Autonegotiation on SFP port
4.2.1 Overview
Auto-Negotiation configuration on SFP ports is handled by a single register according to the picture below.
y=0 CORE Main y=1 CORE Spare
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.2.2 Disable Auto-Negotiation example
In order to disable Auto-Negotiation on SFP ports, the following commands are required inside configu-
ration 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
N.B. 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.
Configuration
3DB 18793 BAAA Issue 1 49/162
4.2.3 Re-Enable Auto-Negotiation example
In order to enable again Auto-Negotiation on SFP ports, the following commands are required inside con-
figuration file for Ethernet switch named enhanced_eth_feature.psh. This command must replace the
disable commands of paragraph 4.2.2.
On CORE Main, enable Auto-Negotiation on both optical ports 5 and 6 (flow control disabled):
setreg 00500065 00000000
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
N.B. 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.
Configuration
3DB 18793 BAAA Issue 1 50/162
4.3 VLAN SWAP
In order to manage the VLAN SWAP capabilities by configuration file the NE must be configured in 802.1D
bridge mode. Additionally, to manage the QoS according the 802.1p value the NE must be properly con-
figured by CT/NMS.
The VLAN SWAP feature is available in conjunction with QinQ.
4.3.2 Enable VLAN swap
bcm vlan port <pbm> <direction> 1
<pbm>: list of possible ports; range: ge5,ge6, ge17, ge18, ge19, ge20; mandatory.
<direction>: translateegress/ translateingress; to enable the VLAN translation in egress or
ingress.; mandatory.
Command example:
bcm vlan port ge17 translateegress 1
bcm vlan port ge17 translateingress 1
As result of these commands the VLAN translation capability is enabled in ingress and egress of user port
1.
Configuration
3DB 18793 BAAA Issue 1 51/162
4.3.3 VLAN Creation
In order to manage the VLAN Swap feature, it is required to explicitly create all the VLANs involved in a
swap rule using the following command:
<id> : id is a integer number used as VLAN ID; range: 2-4080. The VLAN IDs already defined
a) CORE range: ge5, ge6, ge11-ge20; mandatory.
untagged;
4.3.4 Create an ingress VLAN swap rule
bcm vlan translate add port=<portNum> oldVlan=<oldID> newVlan=<newID> prio=<n>
<portNum>: port number; range: 7, 18,19,20,21; mandatory.
<oldID>: incoming VLANID to be swapped; the old VLANID must have been created before
applying any ingress VLAN swap rule; mandatory.
<newID>: new VLANID used to remark the old VLANID frame field; the new VLANID must have
been created before applying any ingress VLAN swap rule; mandatory.
<n>: priority value used to replace the .1p bits; -1 value is used in order to not replace the incom-
ing frame priority; mandatory.
Command example:
bcm vlan translate add port=18 oldvlan=2 newvlan=102 prio=-1
This command defines a VLAN swap rule on user port 1. Every incoming frames on user port 1 having
VLANID 2 will be remarked with VLANID 102 without changing the priority (.1p btis).
Configuration
3DB 18793 BAAA Issue 1 52/162
4.3.5 Create an ingress VLAN swap rule pushing the VLAN tag
bcm vlan translate dtag add port=<portNum> oldVlan=<oldID> newVlan=<newID> prio=<n>
<oldID>: incoming VLANID to be swapped; the old VLANID must have been created before
applying any ingress VLAN swap rule; mandatory.
been created before applying any ingress VLAN swap rule; mandatory.
Command example:
bcm vlan translate dtag add port=18 oldvlan=2 newvlan=102 prio=5
This command defines a VLAN swap rule on user port 1. Every incoming frames on user port 1 having
VLANID 2 will have a new VLAN tag added. The new tag will have VLANID equal to 102 using priority
5 (802.1p bits).
4.3.6 Create an egress VLAN swap rule
bcm vlan translate egress add port=<portNum> oldVlan=<oldID> newVlan=<newID> prio=<n>
<oldID>: outgoing VLANID to be swapped; the old VLANID must have been created before
applying any egress VLAN swap rule; mandatory.
been created before applying any egress VLAN swap rule; mandatory.
Command example:
bcm vlan translate egress add port=18 oldvlan=2 newvlan=102 prio=-1
This command defines a VLAN swap rule on user port 1. Every outgoing frames on user port 1 having
VLANID 2 will be remarked with VLANID 102 without changing the priority (.1p btis).
Configuration
3DB 18793 BAAA Issue 1 53/162
4.3.7 Enable VLAN swap miss drop
bcm vlan port <pbm> <direction> <n>
<pbm>: list of possible ports; range: ge5, ge6, ge17, ge18, ge19, ge20; mandatory.
<direction>: translateingressmissdrop / translateegressmissdrop; to enable the VLAN trans-
lation miss dropping function in egress or ingress; mandatory.
<n>: 0 (disable) or 1 (enable) the dropping mechanism of unknown VLANs; mandatory.
Command example:
bcm vlan port ge17 translateingressmissdrop 1
bcm vlan port ge17 translateegressmissdrop 1
The result of this commands is that any incoming (outgoing) VLAN on user port 1 that have not an explicit
ingress (egress) swap rule configured will be automatically dropped.
4.3.8 Port enabling
bcm port <pbmp> discard=none
<pbm>: list of possible ports; range: ge5, ge6, ge17, ge18, ge19, ge20; mandatory.
Command example:
The result of this commands is that ge17 is now allowed to accept incoming frames.
4.3.9 VLAN SWAP usage examples
4.3.9.1 Use Case A: Mobile Backhauling
Configuration
3DB 18793 BAAA Issue 1 54/162
NE2 has the MOD300 inserted in slot 3 and slot 4.
NE3 has the MOD300 inserted in slot 3. For this NE the configuration file is not needed, the VLANs will
be configured by CT/NMS.
Each BS transmits Customer tagged frames; the RNC transmits Customer Tagged frames:
RED tunnel: C-VLAN ID=2 and C-VLAN ID=3 received on Eth1 will be swapped in C-VLAN ID=102 and
C-VLAN ID=103; The PRI bits will be copied.
BLUE tunnel: C-VLAN ID=2 and C-VLAN ID=3 received on Eth1 will be swapped in C-VLAN ID=104 and
# end preliminary configuration
# enable ingress and egress VLAN translate
Configuration
3DB 18793 BAAA Issue 1 55/162
#enable dropping of VLANs without ingress translation rule defined
# Definition of MOD300 as NNI
#definition of Port translation rules
Configuration
3DB 18793 BAAA Issue 1 56/162
configuration file for NE3:
NE3 should be configured in 802.1Q and VLANs from 102 to 105 must be configured by the means of CT.
4.3.9.2 Use Case B: Mobile Backhauling with MPT
NE1 has MPT inserted in slot 3.
NE2 has MPTs inserted in slot 3 port1 and slot 3 port2
Configuration
3DB 18793 BAAA Issue 1 57/162
NE3 has MPT in slot 3. For this NE the configuration file is not needed, the VLANs will be configured by
CT/NMS.
Each BS transmits Customer tagged frames; the RNC transmits Customer Tagged frames:
RED tunnel: C-VLAN ID=2 and C-VLAN ID=3 received on Eth1 will be swapped in C-VLAN ID=102 and
BLUE tunnel: C-VLAN ID=2 and C-VLAN ID=3 received on Eth1 will be swapped in C-VLAN ID=104 and
#definition of VLANs on user and MPT-ACC ports
Configuration
3DB 18793 BAAA Issue 1 58/162
# Definition of MPT-ACC as NNI
#Create vlan 102 and 103 inside MPT-ACC
Configuration
3DB 18793 BAAA Issue 1 59/162
Configuration
3DB 18793 BAAA Issue 1 60/162
#Create vlan from 102 to 105 inside MPT-ACC
Configuration files for NE3:
NE3 should be configured in 802.1Q and VLANs from 102 to 105 must be configured by the means of CT.
Configuration
3DB 18793 BAAA Issue 1 61/162
4.3.10 QinQ + VLAN SWAP usage examples
4.3.10.1 Use Case A: Mobile Backhauling
BS1, BS2 and BS3 transmits/receives Customer tagged frames; the RNC transmits/receives Service
Tagged frames:
BS1=> Eth1; BS2=> Eth2; BS3=> Eth3; RNC=> Eth1;
RED tunnel: C-VLAN ID=10 will be carried using S-VLAN ID=100 pushing a Service VLAN tag using VLAN
translation command; The PRI bits will be copied.
BLUE tunnel: C-VLAN ID=20 will be carried using in S-VLAN ID=200 pushing a Service VLAN tag using
VLAN translation command; The PRI bits will be copied.
ORANGE tunnel: C-VLAN ID=30 will be carried using in S-VLAN ID=300 pushing a Service VLAN tag in
a port based way; The PRI bits will be fixed at 2 on a port based.
Configuration
3DB 18793 BAAA Issue 1 62/162
# enable ingress VLAN translate
#Drop any unexpected C-VLAN not included into VLAN swap provisioning
bcm vlan create 100 pbm=ge18,ge19 ,ge14 ubm=ge18,ge19
bcm vlan create 200 pbm=ge18,ge19, ge14 ubm=ge18,ge19
bcm vlan create 300 pbm=ge17, ge14 ubm=ge17
#Assingn PVLAN 300 to port ge17
#definition of Port translation rules pushing the proper S-VLAN
bcm vlan translate dtag add port=19 oldVlan=10 newVlan=100 prio=-1
bcm port ge17 prio=2
Configuration
3DB 18793 BAAA Issue 1 63/162
# Definition of user ports 1 and 2 as UNI
#enable incoming traffic.
Configuration
3DB 18793 BAAA Issue 1 64/162
4.3.10.2 Use Case B: Mobile Backhauling
NE1 has the MPT inserted in slot 3 port 1.
NE2 has the MPT inserted in slot 3 port 1.
BS1, BS2 and BS3 transmits/receives Customer tagged frames; the RNC transmits/receives Service
Tagged frames:
BS1=> Eth1; BS2=> Eth2; BS3=> Eth3; RNC=> Eth1;
RED tunnel: C-VLAN ID=10 will be carried using S-VLAN ID=100 pushing a Service VLAN tag using VLAN
translation command; The PRI bits will be copied.
BLUE tunnel: C-VLAN ID=20 will be carried using in S-VLAN ID=200 pushing a Service VLAN tag using
VLAN translation command; The PRI bits will be copied.
ORANGE tunnel: C-VLAN ID=30 will be carried using in S-VLAN ID=300 pushing a Service VLAN tag in
a port based way; The PRI bits will be fixed at 2 on a port based.
Configuration
3DB 18793 BAAA Issue 1 65/162
# enable ingress VLAN translate
#Drop any unexpected C-VLAN not included into VLAN swap provisioning
bcm vlan create 100 pbm=ge18,ge19 ,ge14 ubm=ge18,ge19
bcm vlan create 200 pbm=ge18,ge19, ge14 ubm=ge18,ge19
bcm vlan create 300 pbm=ge17, ge14 ubm=ge17
#Assingn PVLAN 300 to port ge17
#definition of Port translation rules pushing the proper S-VLAN
Configuration
3DB 18793 BAAA Issue 1 66/162
# Definition of user ports 1, 2 and 3 as UNI
Configuration
3DB 18793 BAAA Issue 1 67/162
#enable incoming traffic.
# Definition of MPT-ACC port and port 1 as NNI
Configuration
3DB 18793 BAAA Issue 1 68/162
4.4 OUT OF RANGE VLAN SWAP
4.4.1 Background
MPR official releases provides full 802.1Q feature only for VLAN in range [2:4080]. For some specific net-
work 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 MPR configuration illustrated in this chapter is based on a mix of QinQ and VLAN SWAP
features respectively described in paragraphs 4.1 and 4.3.
The scenario considered in this chapter is the one shown above. 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 Gate-
way 2. These two Gateways, exploiting QinQ and VLAN SWAP, can emulate the same behaviour obtain-
able with 802.1Q bridge mode.
In this condition, configuration on Gateway MPRs has to be provisioned by configuration file for the fol-
lowing purpose:
VLAN creation/membership
port role definition
port VLAN assignment
Configuration
3DB 18793 BAAA Issue 1 69/162
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).
In order to manage the VLAN SWAP capabilities by configuration file the NE must be configured in 802.1D
bridge mode.
# discard all traffic on all user ports.
bcm fp entry remove 1
4.4.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 net-
work 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; range: ge5,ge6, ge17, ge18, ge19, ge20 and each slot lodging
a MOD300 Radio Board or AUX board; mandatory.
<type>: it is the port definition that can be internal for NNI ports or external for UNI ports; man-
datory.
Configuration
3DB 18793 BAAA Issue 1 70/162
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.
4.4.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; range: ge6, ge17, ge18, ge19, ge20; mandatory.
<n>: 802.1p priority value for incoming untagged frames; range [0:7]; mandatory;
N.B. The bcm port command implies always a switch off/on of the involved port; so, anytime the con-
4.4.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: ge5,ge6, ge17, ge18, ge19, ge20; mandatory.
<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.
N.B. The bcm port command implies always a switch off/on of the involved port; so, anytime the con-
Configuration
3DB 18793 BAAA Issue 1 71/162
4.4.4 VLAN Table management
In order to manage the VLAN Table the following command should be used:
<id>: id is a integer number used as VLAN ID; range: 2-4080. The VLAN IDs already defined
a) CORE range: ge5, ge6, ge11-ge20; mandatory.
untagged;
N.B. This configuration has an intrinsic limitation and cannot accept more than 1000 different VLANs
on UNI ports (sum of UNI VLANs).
4.4.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=<newP-
rio>
<pmb>: port bitmap associated to the newVlanID; AUX, PDH and ASAP card must not be
included into this bitmap; range ge11-ge20; mandatory.
<portNum>: user port number which is receiving out of range VLAN; range: 7, 18,19,20,21;
mandatory.
<oldID>: incoming out of range VLANID to be swapped; range [4081:4094]; mandatory.
Configuration
3DB 18793 BAAA Issue 1 72/162
<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.4.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; range: 7, 18,19,20,21;
mandatory.
<vlanID>: UNI incoming/outgoing VLANID; range [2:4080]; mandatory.
N.B. This configuration has an intrinsic limitation and cannot accept more than 1000 different VLAN
on UNI ports (sum of UNI VLANs).
4.4.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; range: ge5, ge6, ge17, ge18, ge19, ge20; mandatory.
N.B. The above command implies always a switch off/on of the involved port; so, anytime the con-
4.4.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
Configuration
3DB 18793 BAAA Issue 1 73/162
Content of "enhanced_eth_feature.psh" for Gateway 1
bcm port ge5 discard=all
#Define user ethernet port as NNI
#Define port receiving out of range VLAN as UNI
#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
#Manage in range VLAN on UNI
#VLAN table management (in range VLANs)
#Configure UNI
#Configure NNI
bcm port ge17 vf=1 prio=5 discard=none
#Enable UNI port
Configuration
3DB 18793 BAAA Issue 1 74/162
Content of "enhanced_eth_feature.psh" for Gateway 2:
#Define user ethernet port as NNI
#Define port receiving out of range VLAN as UNI
#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
#Manage in range VLAN on UNI
#VLAN table management (in range VLANs)
#Configure UNI
#Configure NNI
bcm port ge17 vf=1 prio=5 discard=none
#Enable UNI port
Configuration
3DB 18793 BAAA Issue 1 75/162
4.5 VLAN SWAP AND DOT1P REMARKING FOR ATM PW SERVICE
4.5.1 Background
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 hav-
ing 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 com-
mitted to reserve bandwidth on each radio interfaces) or "Yellow" (they can be dropped in case of con-
gestion 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 Ser-
vice 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.
4.5.2 Migration Procedure
The migration procedure is aimed to support migration from release 1.3.0/1.4.0 where ATMoMPLS pro-
tocol 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 trans-
ported (e.g. to enable the specific header compression on radio cards) .
Configuration
3DB 18793 BAAA Issue 1 76/162
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 paragraph 5.2.
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 chapter 1.
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: 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.
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 4 1
N.B. this feature is normally intended to be used together with "mpls_label_enable" flag file (see
chapter 1).
Configuration
3DB 18793 BAAA Issue 1 77/162
4.5.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 pre-
vious commands enable 802.1p bits remarking for traffic coming from both ports.
4.5.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
4.5.5.1 and 4.5.5.2 must be configured using the same value for parameter n. Please refer to Table 1. in
order to choose the right n value on a per port basis.
n n
ge6 1 ge19 4
ge17 2 ge20 5
ge18 3
Table 1.
4.5.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; manda-
tory.
Configuration
3DB 18793 BAAA Issue 1 78/162
<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=<egrVLAN
H
>
<n> vlan swap rule entry; this value is the one referred at paragraph 4.5.5.2, so this two param-
eters must have the same value; please refer to Table 1. depending on user ethernet port used;
mandatory.
<egrVLANH>: must be expressed in hex coding; mandatory.
4.5.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; please refer to Table 2. ; 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 4.5.5.1, so this two param-
eters must have the same value; please refer to Table 1. depending on user ethernet port used;
mandatory.
<egrDot1p>: 802.1p bits value to remap in egress direction on a per ATM PW CoS basis;
please refer to the table below; mandatory.
For MPR 3.0.0 release, 3 rules are therefore needed for CRB/UBR+/UBR CoS, the following table reports
the values for above CoS and newdot1p parameters according to ATM PW CoS:
CoS Egress dot1p
CBR 0x00000C00 6
UBR+ 0x00000400 2
UBR 0x00000000 0
Table 2.
Configuration
3DB 18793 BAAA Issue 1 79/162
4.5.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.5.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 4.5.6.2 and, considering a
single ATM PW, this value must be equal to the one used at paragraph 4.5.6.2; range [6:245];
mandatory.
<VLAN
H
>: is the VLAN ID associated to the ATM PW flow; must be expressed in hex coding;
mandatory.
4.5.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> ethertype 0x8847 0xffff
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; please
refer to Table 5.; mandatory.
<m>: vlan swap rule entry; this value is also referred at paragraph 4.5.6.1 and, considering a
single ATM PW, this value must be equal to the one used at paragraph 4.5.6.1; 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); please refer to Table 4.; mandatory.
Configuration
3DB 18793 BAAA Issue 1 80/162
<ingDot1p>: 802.1p bits value to remap in ingress on a per ATM PW CoS basis; please refer
to Table 3.; mandatory.
CoS Ingress dot1p
CBR 0x00000C00 6
UBR+ 0x00000400 4
UBR 0x00000000 4
Table 3.
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.
ingPbm ingPbm
ge5 0x000060 ge18 0x080000
ge6 0x000080 ge19 0x100000
ge17 0x040000 ge20 0x200000
Table 5.
Configuration
3DB 18793 BAAA Issue 1 81/162
4.5.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.
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
Configuration
3DB 18793 BAAA Issue 1 82/162
#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
bcm fp action add 528 priopktnew 6
#Ingress VLAN swap rule definition
bcm mod EGR_L3_NEXT_HOP 6 1 intf_num=0x3E8
Configuration
3DB 18793 BAAA Issue 1 83/162
4.6 VLAN SWAP AND FORWARDING FOR "LOCAL ATM SWITCH"
4.6.1 Background
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.
For further details see MPR-E 2.1 SRS, SR ID 8270.
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", paragraph 4.5.
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.
The same as the one for "VLAN swap and dot1p Remarking for ATM PW Service". Please refer to para-
graph 4.5.1.
4.6.3 VLAN swap and frame forwarding
The below 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-con-
nected towards Ethernet User port #1, with MAC DA #1.
Configuration
3DB 18793 BAAA Issue 1 84/162
ATM PW flow #2, with PWLabel_1, terminated on ASAP Card #2, uses VLAN_2 to be cross-con-
nected 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.6.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 4.6.3.2; man-
datory.
<VLAN_xH>, <VLAN_yH>: VLAN IDs used by ATM PW flow #x and #y, must be expressed in hex
coding; mandatory.
4.6.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>
Configuration
3DB 18793 BAAA Issue 1 85/162
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 dif-
ferent rules; mandatory;
<VLAN_xH>: VLAN IDs provisioned for ATM PW flow #x; must be expressed in hex coding; man-
datory.
<pbmp_y> is the port bitmap, as defined by Table 5., that identifies the CORE port connected to
ASAP #y;
<n_y>: vlan swap rule entry; this value is the one referred at paragraph 4.6.3.1; 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 dif-
ferent rules; mandatory;
<VLAN_yH>: VLAN IDs provisioned for ATM PW flow #y; must be expressed in hex coding; man-
datory.
<pbmp_x> is the port bitmap, as defined by Table 5., that identifies the CORE port connected to
ASAP #x;
<n_x>: vlan swap rule entry; this value is the one referred at paragraph 4.6.3.1; mandatory.
4.6.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, ect)
Configuration
3DB 18793 BAAA Issue 1 86/162
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 group destroy 4
bcm fp qset clear
bcm fp qset add UserDefined 2
# 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
Configuration
3DB 18793 BAAA Issue 1 87/162
# 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
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
Configuration
3DB 18793 BAAA Issue 1 88/162
4.7 PORT BASED RATE LIMITING
The following commands must be applied in order to enable the port based rate limiting feature.
bcm m BKPMETERINGCONFIG_EXT.ge5 BKPDISCARD_ACCT_EN=0
4.7.2 Ingress/Egress port rate limiting
bcm portrate <pbm> <mode><rate> <burst>
<bpm>: list of possible ports; range: ge5, ge6, ge17, ge18, ge19, ge20; mandatory.
<mode>: can be egress or ingress; mandatory.
<rate>: rate is expressed in kilobits per second (1000 bps); range: 0 to 1000000 (with step of
64); mandatory.
<burst>: burst (max number of bits admitted at link speed) is expressed in kilobits (1000 bits);
range: 32 to 128000 ; mandatory.
Command example:
bcm portrate ge17 egress 15000 24
This command defines an egress rate limiting on user port 1 at 15Mbps with a burst of 24000 bits (3000
bytes).
Configuration
3DB 18793 BAAA Issue 1 89/162
4.8 STORM CONTROL
This feature allows to restrict the number of incoming broadcast, multicast or DLF traffic in a 1 second
interval on a specific port. When in a 1 second time interval, the number of broadcast, multicast and DLF
exceeds the configured limit, the dropping mechanism is applied.
4.8.1 Broadcast Storm Control
bcm m BCAST_STORM_CONTROL .<pbm> THRESHOLD=<fps> ENABLE=1
<pbm>: pbm is the specific interface the storm control applies to;
CORE range: ge5, ge6, ge11-ge20; mandatory.
MPT-ACC range: ge5, ge6, ge7, ge8; mandatory.
<fps>: it is frame rate per second that this specific interface is allowed to accept; it is expressed
in HEX; mandatory.
ports toward slot where a PDH, ASAP or AUX cards is lodged. Applying this command toward
PDH or ASAP slots will destroy all the E1/ATM traffic.
Command example:
bcm m BCAST_STORM_CONTROL.ge17 THRESHOLD=0x64 ENABLE=1
bcm m BCAST_STORM_CONTROL.ge18 THRESHOLD=0xC8 ENABLE=1
This command defines a broadcast rate limit at 100 fps and 200 fps for respectively to port ge17 and port
ge18.
Command example:
bcm 2: m BCAST_STORM_CONTROL.ge5 THRESHOLD=0x64 ENABLE=1
bcm 2: m BCAST_STORM_CONTROL.ge6 THRESHOLD=0xC8 ENABLE=1
This command defines a broadcast rate limit at 100 fps and 200 fps for respectively to port ge5 and port
ge6 for MPTs connected to respectively Slot 3 port 1 and port 2.
4.8.2 Multicast Storm Control
bcm m MCAST_STORM_CONTROL .<pbm> THRESHOLD=<fps> ENABLE=1
Configuration
3DB 18793 BAAA Issue 1 90/162
in HEX; mandatory.
Command example:
bcm m MCAST_STORM_CONTROL.ge17 THRESHOLD=0x64 ENABLE=1
bcm m MCAST_STORM_CONTROL.ge18 THRESHOLD=0xC8 ENABLE=1
This command defines a multicast rate limit at 100 fps and 200 fps for respectively to port ge17 and port
ge18.
Command example:
bcm 2: m MCAST_STORM_CONTROL.ge5 THRESHOLD=0x64 ENABLE=1
bcm 2: m MCAST_STORM_CONTROL.ge6 THRESHOLD=0xC8 ENABLE=1
This command defines a multicast rate limit at 100 fps and 200 fps for respectively to port ge5 and port
ge6 for MPTs connected to respectively Slot 3 port 1 and port 2.
N.B. This command must not be applied to ports where a TDM2ETH XC is created whose traffic is
coming/going from/to a PDH card in EPS or a radio in EPS. Applying this command will destroy
all the E1/ATM traffic.
4.8.3 DLF Storm Control
bcm m DLFBC_STORM_CONTROL.<pbm> THRESHOLD=<fps> ENABLE=1
in HEX; mandatory.
ports toward slot where a PDH, ASAP or AUX cards is lodged. Applying this command toward
PDH or ASAP slots will destroy all the E1/ATM traffic.
Command example:
bcm m DLFBC_STORM_CONTROL.ge17 THRESHOLD=0x64 ENABLE=1
bcm m DLFBC_STORM_CONTROL.ge18 THRESHOLD=0xC8 ENABLE=1
Configuration
3DB 18793 BAAA Issue 1 91/162
This command defines a DLF rate limit at 100 fps and 200 fps for respectively to port ge17 and port ge18.
Command example:
bcm 2: m DLFBC_STORM_CONTROL.ge5 THRESHOLD=0x64 ENABLE=1
bcm 2: m DLFBC_STORM_CONTROL.ge6 THRESHOLD=0xC8 ENABLE=1
This command defines a DLF rate limit at 100 fps and 200 fps for respectively to port ge5 and port ge6
for MPTs connected to respectively Slot 3 port 1 and port 2.
Configuration
3DB 18793 BAAA Issue 1 92/162
4.9 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.
bcm fp qset clear
bcm fp qset add LookupStatus
bcm port ge5 learn=4
4.9.2 Feature activation
bcm fp qual 768 inports <pbm> 0x3fffff
Configuration
3DB 18793 BAAA Issue 1 93/162
bcm fp qual 768 LookupStatus l2srcstatic=0
bcm fp action add 768 drop
<pbm>: user ethernet port bitmap where ACL applies to; please refer to Table 6.; mandatory.
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
Table 6.
4.9.3 Define an entry in the ACL
bcm l2 add MAC=<MAC_ADDRESS> vlan=<id> pbm=<pbmp> st=t rp=f
<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 con-
nected 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.
N.B. 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;
Command example:
bcm l2 add MAC=00:00:00:C2:F5:01 vlan=2 pbm=ge18 st=t rp=f
Configuration
3DB 18793 BAAA Issue 1 94/162
4.10 PER VLAN RATE LIMITING
This feature allows to apply an rate limiter to a specific VLAN ingressing the MPR network. This feature
is applicable in both 802.1Q and 802.1ad (QinQ) bridge mode.
bcm fp qset clear
bcm fp qset add LookupStatus
4.10.2 Create a VLAN rate limiter entry
bcm fp counter create <ID>
bcm fp meter create <ID>
bcm fp meter setc <ID> <CIR> <BURST>
bcm fp qual <ID> outervlan <vlanID> 0x0fff
bcm fp qual <ID> inports <ingPbm> 0x3fffff
bcm fp action add <ID> colorindependent 1
bcm fp action add <ID> MeterConfig flow committed
bcm fp action add <ID> RpDrop
Configuration
3DB 18793 BAAA Issue 1 95/162
<ID>: rule ID number; range [769:1023]; the chosen value should not be shared among different
rules (wrt chapter 4.5 and 4.4); mandatory.
<CIR>: Committed Information Rate expressed in Kbps (granularity 64Kbps); mandatory.
<BURST>: burst in Kbits; mandatory.
<vlanID>: vlan ID (expressed in HEX) rate limiter applies to; mandatory.
<ingPbm>: user ethernet port bitmap where chosen VLAN's frames will ingress MPR network;
please refer to Table 7.; mandatory.
ingPbm ingPbm
ge5 0x00040 ge18 0x080000
ge6 0x000080 ge19 0x100000
ge17 0x040000 ge20 0x200000
Table 7.
N.B. Id parameters defined above has to be considered differently in the following three bridge
mode:
802.1Q
vlanID is equal to VLAN id carried inside vlan Tag if the frame was originally tagged;
vlanID is equal to PVLAN in case the frame is coming in untagged and then tagged
on a port based way;
802.1D and QINQ (by cfg file)
vlanID is equal to Service VLAN id the incoming packet is mapped to;
Command example:
bcm fp counter create 769
bcm fp meter create 769
bcm fp meter setc 769 1000 1000
bcm fp qual 769 outervlan 0x0064 0x0fff
bcm fp qual 769 inports 0x40000 0x3fffff
bcm fp action add 769 colorindependent 1
bcm fp action add 769 MeterConfig flow committed
bcm fp action add 769 RpDrop
This command applies a per VLAN rate limiting to VLAN 100 (HEX: 0x0064) on port ge17 at 1000 Kbps
with 1000Kbits of burst .
Configuration
3DB 18793 BAAA Issue 1 96/162
4.11 SCHEDULER SETTING
4.11.1 Preliminary information
The MPR has 8 queues per each switch port and each radio board. In this document we refer to queue
7 as the highest priority one (top one) and to queue 0 as the lower priority one (in some other documents
the queue index can be from 1 to 8) .
The scheduler can be configured into the CORE Ethernet switch, MPT-ACC Ethernet switch and MOD300
board. With MPR 3.0.0 release, Enhanced Configuration of this feature is not available with MPT ODU.
4.11.2 Default configuration
Ethernet switch and all radio interfaces of MPR use HQP scheduler over queues Q7, Q6 and Q5.
Deficit Weighted Round Robin (DWRR) will be used on the other queues with the following weights:
Queue Weight
Q4 (higher priority) 16
Q3 8
Q2 4
Q1 2
Q0 1
Configuration
3DB 18793 BAAA Issue 1 97/162
4.11.3 Switch configuration
4.11.3.1 Deficit Weighted Round Robin Scheduler definition
bcm cos drr w0=<#> w1=<#> w2=<#> w6=<#> w7=<#>
<#>: weight expressed in Kbits per queue; range: 1 to 2032; mandatory.
N.B. If any XC flows (TDM2TDM, TDM2ETH, ATM) are configured inside the MPR, this type of
scheduler is not recommended; in order to have the appropriate QoS for XC flows, it is suggest
to apply a very high queue weight to queue 7, 6 and 5.
Command example for CORE:
bcm cos drr w0=2 w1=4 w2=8 w3=16 w4=32 w5=64 w6=128 w7=256
Command example for MPT-ACC in slot 3:
bcm 2: cos drr w0=2 w1=4 w2=8 w3=16 w4=32 w5=64 w6=128 w7=256
This command defines the DWRR scheduler assigning the queues' weight in an incremental way.
Clarification:
DWRR scheduler accepts queue weights in the range specified here after in the document. Depending
on the configured values' spreading, the DRR algorithm automatically quantizes the weights with a gran-
ularity of 2048, 4096, 8192, 16384 bytes. So, chosen the granularity, not all values can be admitted.
Command example:
In order to represent w7=2032, 16384 bytes is used as granularity. This automatic selection imposes a
minimum weight if 16 Kbytes.
Queue 0: 16384 bytes x 1 = 16 Kbytes
So, low priority queues must have at least the minimum weight that corresponds to 16Kbytes.
Configuration
3DB 18793 BAAA Issue 1 98/162
4.11.3.2 Strict Priority + Deficit Weighted Round Robin Scheduler definition
bcm cos drr w0=<#> w1=<#> w2=<#> w6=<#> w7=<#>
<#>: weight expressed in Kbytes per queue value; setting # equal to 0 implies a queue to be
strict priority mode; mandatory.
N.B. If any XC (TDM2TDM, TDM2ETH, ATM) flows is configured inside the MPR, it is recommended
to have at least queue 7 and queue 6 in strict priority in order to have the appropriate QoS to
XC flows. It is important to clarify that only queue 7, 6 and 5 can be configured in strict priority
starting from queue 7 down to queue 5. For example, the following configuration is forbidden:
In order to have queue 5 in strict priority, also queue 7 and 6 must be in strict priority
In order to have queue 6 in strict priority, also queue 7 must be in strict priority
Command example for CORE:
Command example for MPT-ACC in slot 3:
bcm 2: cos drr w0=2 w1=4 w2=8 w3=16 w4=32 w5=64 w6=0 w7=0
This command defines the SP+DWRR scheduler assigning the queues' weight in an incremental way,
except for those queues that are in strict priority.
4.11.4 MOD300 configuration
4.11.4.1 Overview
In order to configure the scheduler in DWRR mode it is needed to write some configuration registers. To
enable this feature contact your local Alcatel-Lucent support.
Configuration
3DB 18793 BAAA Issue 1 99/162
4.12 MAPPING 802.1p TO QUEUES
To manage properly this feature it is needed to configure CORE Ethernet switch, MPT-ACC Ethernet
switch and MOD 300 board.
By CT/NMS the 802.1p QoS mechanism must be selected as QoS classification criteria for the Ethernet
flows before applying the configuration file. With MPR 3.0.0 release, Enhanced Configuration of this fea-
ture is not available with MPT ODU.
Inside the switch and MOD300 card the mapping between the 802.1p values and queues is predefined
and not configurable by ECT/NMS. It is the following:
802.1p priority Queue
111, 110 Q4 (higher priority)
101 Q3
100 Q2
011, 000 Q1
010, 001 Q0
It is possible define up to 7 rules with the following commands:
bcm fp entry remove <ruleNumber>
bcm fp entry destroy <ruleNumber>
bcm fp entry create 1 <ruleNumber>
bcm fp qual <ruleNumber> outervlan <vlan> <mask>
bcm fp action add <ruleNumber> cosqnew <queue>
bcm fp entry install <ruleNumber>
<ruleNumber>: number of rule (integer); range: 44-50; mandatory.
<vlanTag>: including all 16 bits representing respectively PCP (15:13), CFI/DEI (12) and VLAN ID
(11:0); value (hex); the only relevant portion of the tag is the PCP field; mandatory.
<vlanTagMask>: mask in hex including all 16 bits representing respectively PCP (15:13), CFI/DEI
(12) and VLAN ID (11:0); 1=match, 0=don't care; mask value should include only the 3bits PCP field
containing priority value; mandatory.
<queue>: queue number (integer); range 0 (low priority) to 4 (high priority); mandatory.
Configuration
3DB 18793 BAAA Issue 1 100/162
4.12.2.1 802.1p to queues mapping usage examples
4.12.2.1.1 Use case A
Mapping between 802.1p values and queues according the following table:
101 Q3
100 Q2
011, 000 Q1
010, 001 Q0
# changing only priority 2 and priority 0
bcm fp action remove 48 cosqnew
bcm fp action add 48 cosqnew 1
bcm fp entry reinstall 48
Content of "fullConfig_mptacc.psh" having MPT-ACC in slot 3:
# changing only priority 2 and priority 0
bcm 2: fp action remove 48 cosqnew
bcm 2: fp action add 48 cosqnew 1
bcm 2: fp entry reinstall 48
Configuration
3DB 18793 BAAA Issue 1 101/162
4.12.2.1.2 Use case B
Q4 (higher priority)
111, 110 Q3
100, 101 Q2
011, 010 Q1
000, 001 Q0
# Remapping .1p to only 4 queues
Configuration
3DB 18793 BAAA Issue 1 102/162
Configuration
3DB 18793 BAAA Issue 1 103/162
4.12.2.1.3 Use case C
111 Q4 (higher priority)
110 Q3
100, 101 Q2
011, 010 Q1
000, 001 Q0
bcm fp entry destroy 44
bcm fp qual 44 outervlan 0x0000 0xC000
Configuration
3DB 18793 BAAA Issue 1 104/162
bcm fp qual 47 outervlan 0xC000 0xE000
bcm fp qual 48 outervlan 0xE000 0xE000
# Remapping .1p to 5 queues
bcm 2: fp entry remove 44
Configuration
3DB 18793 BAAA Issue 1 105/162
bcm 2: fp entry destroy 44
bcm 2: fp entry create 1 44
bcm 2: fp qual 44 outervlan 0x0000 0xC000
bcm 2: fp entry install 44
bcm 2: fp qual 47 outervlan 0xC000 0xE000
bcm 2: fp qual 48 outervlan 0xE000 0xE000
Configuration
3DB 18793 BAAA Issue 1 106/162
4.12.3.1 Overview
Configuration
3DB 18793 BAAA Issue 1 107/162
4.13 MAPPING DiffServ TO QUEUES FOR IPv4 FRAMES
To manage properly this feature it is needed to configure CORE Ethernet switch, MPT-ACC Ethernet
switch and MOD 300 board.
By CT/NMS the DiffServ QoS mechanism must be selected as QoS classification criteria for the Ethernet
Inside the switch and MOD300 card the mapping between the DSCP values (6 bits) and queues is pre-
defined and not configurable by ECT/NMS. It is the following:
DiffServ priority Queue
111000, 110000, 101110, 101000 Q4 (higher priority)
100110, 100100, 100010, 100000 Q3
011110, 011100, 011010, 011000 Q2
010110, 010100, 010010, 010000
001110, 001100, 001010, 001000
000000
Q1
All remaining values Q0
bcm fp entry remove <rule number>
bcm fp entry destroy <rule number>
bcm fp entry create 1 <rule number>
bcm fp qual <rule number> dscp <ToS> <Mask>
bcm fp action add <rule number> cosqnew <queue>
bcm fp entry install <rule number>
<rule number>: number of rule (integer); range: 44-51; mandatory.
<ToS>: ToS value (hex); range 0x00-0xff; mandatory.
<Mask>: ToS mask (hex), 1=match; 0x00-0xff; mandatory.
<Queue>: Queue number (integer); range 0 (low priority) to 4 (high priority); mandatory.
Configuration
3DB 18793 BAAA Issue 1 108/162
4.13.2.1 DiffServ to queues mapping usage examples
4.13.2.1.1 Use case
Mapping between DiffServ values and queues according the following table:
101110, 101000 Q3
011110, 011100 Q2
010110, 010100 Q1
# All DiffServ rules are removed
Configuration
3DB 18793 BAAA Issue 1 109/162
#Definition of new rules
bcm fp qual 44 dscp 0xc0 0xdc
bcm fp action add 44 CosQNew 4
bcm fp qual 45 dscp 0xb8 0xfc
bcm fp qual 46 dscp 0xa0 0xfc
bcm fp qual 47 dscp 0x78 0xf4
bcm fp qual 48 dscp 0x58 0xf4
Configuration
3DB 18793 BAAA Issue 1 110/162
# All DiffServ rules are removed
bcm 2: fp qual 44 ethertype 0x0800 0xffff
bcm 2: fp qual 44 dscp 0xc0 0xdc
bcm 2: fp action add 44 CosQNew 4
Configuration
3DB 18793 BAAA Issue 1 111/162
bcm 2: fp qual 45 dscp 0xb8 0xfc
bcm 2: fp qual 46 dscp 0xa0 0xfc
bcm 2: fp qual 47 dscp 0x78 0xf4
bcm 2: fp qual 48 dscp 0x58 0xf4
4.13.3.1 Overview
Configuration
3DB 18793 BAAA Issue 1 112/162
4.14 IPv6 QoS SUPPORT WITH FLEXIBLE MAPPING TRAFFIC CLASS
TO QUEUES
By CT/NMS the DiffServ QoS mechanism must be selected as QoS classification criteria for the Ethernet
The NE can be configured in 802.1D or 802.1Q bridge mode.
To enable the IPv6 QoS support with the default mapping between traffic class value and queue (see user
manual), it is needed to apply the configuration file only to the Core/MPT-ACC switch, for all others map-
ping the configuration file must be apply also to the MOD300 card.
bcm fp entry destroy <rule number>
bcm fp entry create 1 <rule number>
bcm fp qual <rule number> dscp <TC> <Mask>
bcm fp action add <rule number> cosqnew <queue>
bcm fp entry install <rule number>
<rule number>: number of rule (integer); range: 52-59; mandatory.
<TC>: TC value (hex); range 0x00-0xff; mandatory.
<Mask>: TC mask (hex), 1=match; 0x00-0xff; mandatory.
<Queue>: Queue number (integer); range 0 (low priority) to 4 (high priority); mandatory.
4.14.2.1 Traffic Class to queues mapping usage examples
4.14.2.1.1 Use case (as default configuration for IPv4)
111000, 110000, 101110, 101000 Q4 (higher priority)
100110, 100100, 100010, 100000 Q3
011110, 011100, 011010, 011000 Q2
Configuration
3DB 18793 BAAA Issue 1 113/162
To obtain the mapping between the DSCP values (inside the traffic class) and queues as showed in the
table above, the following configuration file must be applied:
bcm fp qual 52 dscp 0xe0 0xdc
bcm fp qual 52 ethertype 0x86dd 0xffff
bcm fp qual 53 dscp 0xb8 0xfc
bcm fp qual 54 dscp 0xa0 0xfc
bcm fp qual 55 dscp 0x98 0xe4
010110, 010100, 010010, 010000
001110, 001100, 001010, 001000
000000
Q1
Configuration
3DB 18793 BAAA Issue 1 114/162
bcm fp qual 59 dscp 0x00 0xfc
Configuration
3DB 18793 BAAA Issue 1 115/162
bcm 2: fp qual 52 dscp 0xe0 0xdc
bcm 2: fp qual 52 ethertype 0x86dd 0xffff
bcm 2: fp qual 53 dscp 0xb8 0xfc
bcm 2: fp qual 54 dscp 0xa0 0xfc
bcm 2: fp qual 55 dscp 0x98 0xe4
Configuration
3DB 18793 BAAA Issue 1 116/162
bcm 2: fp qual 59 dscp 0x00 0xfc
4.14.3.1 Overview
Configuration
3DB 18793 BAAA Issue 1 117/162
4.15 SFP 2E1/DS1 CIRCUIT EMULATION
4.15.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 equip-
ment can support this module in this release. Despite the hardware readiness of the module, this release
supports circuit emulation service for E1 in TDM2ETH 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 and without LOS as CORE EPS switching criteria.
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, please refer to paragraph 6.1) shall be loaded inside the NE Flash Card. and 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. Please refer to paragraph 4.15.2 in order to use the proper
MAC address.
4.15.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 1.
Configuration
3DB 18793 BAAA Issue 1 118/162
During XC configuration, the operator will be asked to select the TDM service and inserting Flow ID (sup-
posed to be equal to VLAN ID used to configure the specific tributary) along with the destination MAC
address (see Figure 1.). 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.15.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 (refer to 4.15.3.1)
1.2. Optical Port 6 default configuration (refer to 4.15.3.2)
2. IWF specific configuration
2.1. Optical port 5 Tributary 1 IWF configuration (refer to 4.15.3.3)
3. Per port common tributaries configuration
3.1. Optical port 5 Tributaries common configuration (refer to 4.15.3.7)
3.2. Optical port 6 Tributaries common configuration (refer to 4.15.3.8)
4. Per port Tributaries configuration apply command (refer to 4.15.3.9.2)
5. Protocol specific configuration (refer to 4.15.3.9.3 and 4.15.3.9.4)
5.1. Optical port 5 Tributary 1 Dst MAC, VLAN ID and ECID
6. Per port LIU enable command (refer to 4.15.3.9.5)
6.1. Optical port 5 LIU enable command
6.2. Optical port 6 LIU enable command
7. Per port Tributaries enable command (refer to 4.15.3.9.6)
7.1. Optical port 5 Tributary 1 enable command
Configuration
3DB 18793 BAAA Issue 1 119/162
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.15.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.15.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.15.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
Configuration
3DB 18793 BAAA Issue 1 120/162
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
Configuration
3DB 18793 BAAA Issue 1 121/162
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, please refer to 4.15.3.9.1
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
Configuration
3DB 18793 BAAA Issue 1 122/162
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
setreg 04500004 FE
setreg 04500000 01
setreg 04500005 03
setreg 04500006 07
setreg 04500007 00
Configuration
3DB 18793 BAAA Issue 1 123/162
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
Configuration
3DB 18793 BAAA Issue 1 124/162
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
Configuration
3DB 18793 BAAA Issue 1 125/162
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.15.3.7 Optical port 5 tributaries common configuration
setreg 03600040 00
setreg 03600042 d8
Configuration
3DB 18793 BAAA Issue 1 126/162
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
Configuration
3DB 18793 BAAA Issue 1 127/162
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.15.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
Configuration
3DB 18793 BAAA Issue 1 128/162
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
Configuration
3DB 18793 BAAA Issue 1 129/162
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.15.3.9 Relevant registers
In order to define all the macro-blocks described in paragraph 4.15.3, this section reports how to configure
each specific register within a macro-block.
4.15.3.9.1 Clock recovery type
setreg yx5000zC 01
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 4.15.3.9.6)
b. 0x5A Node timing
Configuration
3DB 18793 BAAA Issue 1 130/162
4.15.3.9.2 Tributaries configuration apply command
setreg yx200000 <HEX value>
a. 0x6C to apply configuration to Tributaries 1 only
b. 0xAC to apply configuration to Tributaries 2 only
c. 0xEC to apply configuration to both Tributaries 1 and 2
HEX value reported in a) and b) has to be used when a single tributary is used inside the SFP module,
while c) has to be used when 2 tributaries are used.
4.15.3.9.3 Tributary Destination MAC address
The following six registers contain the destination MAC address splitted in 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.
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:--
Configuration
3DB 18793 BAAA Issue 1 131/162
For the previous two registers, the following value apply:
Write byte 3 of the MAC address [23:16] bits --:--:--: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 value apply:
4.15.3.9.4 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.
Configuration
3DB 18793 BAAA Issue 1 132/162
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 value apply:
4.15.3.9.5 Per port LIU enable command
setreg yx10000C 01
4.15.3.9.6 Per port Tributaries enable command
setreg yx5000z0 01
Configuration
3DB 18793 BAAA Issue 1 133/162
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 (Table 8.) or with an equivalent SFP mod-
ule (Table 9.).
Table 8. Compatibility table between 32E1 PDH card and 2xE1/DS1 SFP Module
Table 9. Compatibility table between two 2xE1/DS1 SFP modules
Configuration
3DB 18793 BAAA Issue 1 134/162
4.15.4 Blue Signal configuration
This section applies in the only case SFP module is used for synchronization purpose. With the config-
uration 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.15.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
Configuration
3DB 18793 BAAA Issue 1 135/162
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.15.5 Example
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
Configuration
3DB 18793 BAAA Issue 1 136/162
#Optical port 5 Tributary 1 IWF config
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
Configuration
3DB 18793 BAAA Issue 1 137/162
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 config
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
Configuration
3DB 18793 BAAA Issue 1 138/162
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
Configuration
3DB 18793 BAAA Issue 1 139/162
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 :DESTIMNATION 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
Configuration
3DB 18793 BAAA Issue 1 140/162
#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
Configuration
3DB 18793 BAAA Issue 1 141/162
4.16 ALARM SEVERITY ASSIGNMENT PROFILE
4.16.1 Description
Alarm Severity Assignment Profile feature allows the operator to realize a custom re-mapping of "Non-
ServiceAffecting" (NSA) severity and "ServiceAffecting" (SA) severity of each alarm supported into the
system.
Note: the configuration file used to apply this feature is not managed by CFNR tool, so please refer to para-
graph 2.3 for this specific file upload to Flash Card.
4.16.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.16.3 File content
Each command insert inside "def_asap4.psh" configuration file must respect the following structure:
<Alarm value> <SA severity> <NSA severity>
<Alarm value>: id corresponding to specific alarm whose severity the user wants to change; please refer
to Table 11.;
<SA severity>: severity in case of service affecting alarm; please refer to Table 10.;
<NSA severity>: severity in case of non service affecting alarm; please refer to Table 10.;
Severity Severity Value
NO_ALARM 0
MINOR 1
MAJOR 2
CRITICAL 3
WARNING 4
Table 10. Severity table
For each alarm, the operator is required to insert the both severities, the system depending on the context.
Configuration
3DB 18793 BAAA Issue 1 142/162
Alarm ID Alarm Name
2 cableLOS
3 rxFail
5 demFail
12 earlyWarning
17 atpcLoopCommunicationProblem
18 rxDivFail/dialogFailure
25 incompatibleFreq
26 incompatibleTxPower
29 AIS
30 degradedSignal
32 lossOfFrame
34 lossOfSignal
37 excessiveBER
39 unavail
46 replaceableUnitMissing
47 replaceableUnitTypeMismatch
50 replaceableUnitProblem
51 batteryFailure
52 sfwrEnviromentProble
54 versionMismatch
57 URU
58 URUS
59 lossOfProt
60 lossOfESMC
61 SyncSigFail
62 sectionTraceMis
64 internalCommunicationProblem
67 unconfiguredEqptPresent
75 remoteDefectIndication
Configuration
3DB 18793 BAAA Issue 1 143/162
Table 11. Alarm IDs
76 linkIdentifierMismatch
77 housekeepingAlarm
78 thresoldCross
79 SbyVersionMismatch
80 PPPFail
82 lossOfAlignment
88 LossOfCESoETHframe
90 incompatibleShifter
91 LicenceCodeMismatch
92 XConnFailure
93 outOfFrame
98 Link_LossOfCellDeliniation
99 Link_LossOfImaframe
100 Link_LossOfDelaySynch
101 Link_Rdi
102 Group_TrailSignalFail
103 RetimingBufferOverflow
104 loopProblem
105 powerSupplyFailure
106 incompatibleModulation
107 clockFailure
108 URD
109 bandwidthOverflow
110 ethSignalDegrade
111 excessEnvTemp
112 RPSPathFail
Alarm ID Alarm Name
Configuration
3DB 18793 BAAA Issue 1 144/162
4.16.4 Example
# <Alarm value> <SA severity> <NSA severity>
2 4 4 # cableLOS
3 4 4 # rxFail
5 4 4 # demFail
Configuration
Appendix
3DB 18793 BAAA Issue 1 145/162
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 chapter 2, the tool
is just making easy it as it hides the FTP and Telnet session needed to transfer configuration files and exe-
cute related commands.
The tool works assuming the NE is reachable at IP level.
It is available only for Administrator Profile (CT and NM)
WARNING
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 CFNR Tool.
Configuration
Appendix
3DB 18793 BAAA Issue 1 146/162
5.1.1 Tool Launch on JUSM
Figure 2. Configuration File Tool Launch
From Configuration Menu, select Configuration File Menu Item.
Configuration
Appendix
3DB 18793 BAAA Issue 1 147/162
5.1.2 Main view
Figure 3. 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
Configuration
Appendix
3DB 18793 BAAA Issue 1 148/162
5.1.3 How to perform Delta Configuration without NE Restart
Figure 4. 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
Configuration
Appendix
3DB 18793 BAAA Issue 1 149/162
The file on NE flash has been updated with executed commands, as it can seen by looking at blue box
in below picture:
Configuration
Appendix
3DB 18793 BAAA Issue 1 150/162
5.1.4 Import/Export of Enhanced Configuration files
Select File Menu in Main View, see Figure 3.:
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.

Configuration
Appendix
3DB 18793 BAAA Issue 1 151/162
5.2 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 par. 4.5.2 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 reach-
able 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 (see [2], SR ID : 1972)
3) A page like the below one will be displayed.
Figure 7. 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 the below will be shown
Configuration
Appendix
3DB 18793 BAAA Issue 1 152/162
Figure 8. MPR WebServer MPLS Setting Page 1/2
6) By supplying an input (in decimal format) in the MPLS Tunnel Label field, the ATMoMPLS Pro-
tocol Stack is configured with the presence of MPLS Tunnel Label. In case there're 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. See [2], SR ID:9020, for applicable consistency checks and admissible
range of MPLS Tunnel Label value.
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:
Configuration
Appendix
3DB 18793 BAAA Issue 1 153/162
Figure 9. 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're 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.
Configuration
Appendix
3DB 18793 BAAA Issue 1 154/162
Configuration
Abbreviations
3DB 18793 BAAA Issue 1 155/162
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
Configuration
Abbreviations
3DB 18793 BAAA Issue 1 156/162
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
Configuration
Abbreviations
3DB 18793 BAAA Issue 1 157/162
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
Configuration
Abbreviations
3DB 18793 BAAA Issue 1 158/162
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 pos-
sible. 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 ser-
vices 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 com-
ponents 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 inter-
face and facilitate the interaction with the product.
Configuration
Index
3DB 18793 BAAA Issue 1 159/162
INDEX
Configuration
Index
3DB 18793 BAAA Issue 1 160/162
Configuration
Customer Documentation Feedback
3DB 18793 BAAA Edition 1 161/162
CUSTOMER DOCUMENTATION FEEDBACK
The meaning of this section is to collect customer feedback about this handbook.
Scope of this activity is the improvement and innovation of customer documentation through the under-
standing of customer needs.
Your comments are welcome.
Please send your comment also if you appreciate the handbook.
You can send them to your Local Alcatel Technical Assistance Center.
They will be addressed to the team in charge of the relevant manual.
The following form supplies an example only of useful info, as a guide of the type of expected feedback.
It is possible fill part of the form, add other data and so on.
How to send feedback:
copying the example form, filling it and sending it to your Local Alcatel Technical Assistance
Center. In this case handbook data are already available at the page bottom.
using the same form available as a file in the relevant documentation CD-ROM, saving, filling
and sending it by e-mail to your Local Alcatel Technical Assistance Center.
creating a dedicated form on paper or file and sending it to your Local Alcatel Technical Assis-
tance Center.
Well take your suggestion in account.
We reserve to modify consequently the handbook according to the corretness and congruence of the sug-
gestion and requests.
Configuration
Customer Documentation Feedback
3DB 18793 BAAA Edition 1 162/162
162

CUSTOMER DOCUMENTATION FEEDBACK
Handbook Data
Handbook title, release,version:
Handbook type:
Handbook part number and edition:
General Feedback Evaluation
SUBJECT 5(max) 4 3 2 1 (min)
Total evaluation
Info quantity
Info quality
Info structure
Consulting facility
Layout
Chapters Feedback Evaluation
HANDBOOK PARTS 5(max) 4 3 2 1(min)
PREFACE
CHAPTER 1
CHAPTER 2
CHAPTER 3
CHAPTER 4
Your Comments (stricltly necessary when value is less than 3):
Suggestion for Improvement
Which subject to deepen:
How to deepen:
Subject to eliminate or reduce
Other comments/suggestions
Errors Identified
Reader Info
Name:
Company:
Address:
E-mail:
Phone:
3DB 18793 BAAA
Issue 1

All rights reserved.
Passing on and copying of this document,
use and communication of its contents is not permitted
without written authorization from Alcatel -Lucent.
www.alcatel-lucent.com

MPR 300 Conf File MNGM

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 300 Conf File MNGM

Uploaded by

Copyright:

Available Formats

Configuration

Configuration File Management

You might also like