Professional Documents
Culture Documents
Alcatel-Lucent 9500
MICROWAVE PACKET RADIO for ETSI | RELEASE 5.2.0
Configuration File Management
3DB19901BFAA Edition 01
Alcatel-Lucent Proprietary
This document contains proprietary information of Alcatel-Lucent and is not to be disclosed
or used except in accordance with applicable agreements.
Copyright 2014 © Alcatel-Lucent. All rights reserved.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change
without notice.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks
are the property of their respective owners.
Disclaimers
Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering,
they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe
performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic
control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to
death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale,
license or other distribution of the products for any such application without the prior written consent of
Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent
harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the
use, sale, license or other distribution of the products in such applications.
This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please
note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this
information accurately reflects information provided by the supplier, please refer to the materials provided with any
non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or
liability for incorrect or incomplete information provided about non-Alcatel-Lucent products.
However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products,
if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers.
This document was originally written in English. If there is any conflict or inconsistency between the English
version and any other version of a document, the English version shall prevail.
Table of Contents
Preface ............................................................................................................... 11
Preliminary Information..................................................................................................... 11
WARNING .................................................................................................................. 11
NOTICE..................................................................................................................... 11
COPYRIGHT NOTIFICATION.............................................................................................. 11
TECHNICAL SUPPORT .................................................................................................... 11
SAFETY RECOMMENDATION ............................................................................................. 12
SERVICE PERSONNEL SKILL .............................................................................................. 12
Applicability .................................................................................................................. 12
Scope........................................................................................................................... 13
History ......................................................................................................................... 13
Handbook Structure ......................................................................................................... 14
General on Customer Documentation..................................................................................... 14
Customer–Independent Standard Customer Documentation ...................................................... 14
Product levels and associated Customer Documentation .......................................................... 15
Handbook Updating ...................................................................................................... 16
Changes introduced in the same product–release (same handbook P/N) ....................................... 16
Supplying updated handbooks to Customers......................................................................... 17
Changes due to new product version ................................................................................. 17
Customer documentation on CD-ROM................................................................................. 17
Contents, creation and production of a CD-ROM.................................................................... 18
Use of the CD-ROM....................................................................................................... 18
CD-ROM identification................................................................................................... 19
CD-ROM updating......................................................................................................... 19
5 — Appendix...................................................................................................... 169
5.1 — Configuration File No Restart tool ................................................................................169
5.1.1 — Tool Launch on JUSM .........................................................................................170
5.1.2 — Main view.......................................................................................................170
5.1.3 — How to perform Delta Configuration without NE Restart ...............................................171
5.1.4 — Import/Export of Enhanced Configuration files ..........................................................174
5.2 — File Transfer Manager tool .........................................................................................174
5.2.1 — Tool Launch on JUSM ........................................................................................175
5.2.2 — Main View ......................................................................................................176
5.2.3 — Import/Export of Enhanced Configuration files ..........................................................178
5.3 — ATMoMPLS Protocol Stack Configuration by HTTP interface (MPR WebServer) ............................178
5 — Appendix...................................................................................................... 169
Figure 5.1 — Configuration File No Restart Tool Launch..............................................................170
Figure 5.2 — Main view.....................................................................................................171
Figure 5.3 — Delta Configuration Operation 1/3 .......................................................................172
Figure 5.4 — Delta Configuration Operation 2/3 .......................................................................173
Figure 5.5 — Delta Configuration Operation 3/3 .......................................................................174
Figure 5.6 — FTM Tool Launch ............................................................................................176
Figure 5.7 — Main view.....................................................................................................177
Figure 5.8 — MPR WebServer Main page.................................................................................179
Figure 5.9 — MPR WebServer MPLS Setting Page 1/2..................................................................180
Figure 5.10 — MPR WebServer MPLS Setting Page 2/2 ................................................................181
Preface ............................................................................................................... 11
Table 1 — Product Releases ............................................................................................... 13
Table 2 — History ............................................................................................................ 13
Table 3 — Handbook structure ............................................................................................ 14
Preliminary Information
WARNING
Any warranty must be referred exclusively to the terms of the contract of sale of the
equipment to which this handbook refers to.
Alcatel-Lucent makes no warranty of any kind with regards to this manual, and specifically
disclaims the implied warranties of merchantability and fitness for a particular purpose.
ALCATEL-LUCENT will not be liable for errors contained herein or for damages, whether
direct, indirect, consequential, incidental, or special, in connection with the furnishing,
performance, or use of this material.
NOTICE
The product specification and/or performance levels contained in this document are for
information purposes only and are subject to change without notice. They do not represent
any obligation on the part of ALCATEL-LUCENT.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL-LUCENT and must
not be copied, reproduced or disclosed to a third party without written consent.
TECHNICAL SUPPORT
Please contact your Local Alcatel Technical Assistance Center for questions referred to the
information contained in this document.
To send your comments about this handbook please follow the indication on Customer
Documentation Feedback.
SAFETY RECOMMENDATION
The safety recommendations here below must be considered to avoid injuries on persons
and/or damage to the equipment:
1. Service Personnel
Installation and service must be carried out by authorized persons having appropriate
technical training and experience necessary to be aware of hazardous operations
during installation and service, so as to prevent any personal injury or danger to other
persons, as well as preventing damage to the equipment.
2. Access to the Equipment
Access to the Equipment in use must be restricted to Service Personnel only.
3. Safety Rules
Local safety regulations must be used if mandatory. Safety instructions in this
handbook should be used in addition to the local safety regulations. In case of conflict
between safety instructions stated in this manual and those indicated in local
regulations, mandatory local norms will prevail. Should not local regulations be
mandatory, then safety rules stated in this manual will prevail.
Applicability
This document applies to 9500MPR R.5.2.0.
PRODUCT RELEASE
Scope
Scope of this document is to define:
in order to obtain a specific behavior unobtainable with the supported configuration tools.
Note: The command described in this document are examples of the command
application, the user should adapt the described commands with the correct data for the
equipment
History
Table 2 — History
Handbook Structure
This handbook has been edited according to the Alcatel-Lucent standardized “drawing-up
guides" complying with such suggestion.
This handbook is divided into the main topics described in the table of contents:
Handbook Updating
Each handbook is identified by:
• the name of the "product–release" (and "version" when the handbook is applicable to
the versions starting from it, but not to the previous ones),
• the handbook name,
• the handbook Part Number,
• the handbook edition (usually first edition=01),
• the handbook issue date. The date on the handbook does not refer to the date of print
but to the date on which the handbook source file has been completed and released
for the production.
• only the date changes (pointed out in the Table of Contents) when modifications are
made to the editorial system not changing the technical contents of the handbook.
• the edition, hence the date, is changed because modifications made concern technical
contents. In this case:
• the changes with respect to the previous edition are listed in History.
• in affected chapters, revision bars on the left of the page indicate modifications
in text and drawings.
Changes concerning the technical contents of the handbook cause the edition number
increase (e.g. from Ed.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same
edition but with the addition of a version character (e.g. from Ed.02 to Ed.02A). Version
character can be used for draft or proposal editions.
Moreover, should the screen prints included in the handbook contain the product–release's
"version" marking, they are not replaced in the handbooks related to a subsequent
version, if the screen contents are unchanged.
By updated handbook delivery it is meant the supply of a complete copy of the handbook
new issue (supplying errata-corrige sheets is not envisaged).
In this case the modified parts of the handbook are not listed.
In some other cases, the same CD-ROM can contain the documentation of different
product-release(-version)s for a certain language.
As a general rule:
The files processed in this way are added to files/images for managing purpose and a master
CD-ROM is recorded.
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.
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.
Then the Customer is allowed to read the handbooks on the PC/WS screen, using the
navigation and zooming tools included in the tool, and to print selected parts of the
documentation through a local printer.
CD-ROM identification
Each CD-ROM is identified:
CD-ROM updating
The list of source handbook/document P/Ns-editions indicated in CD-ROM identification,
in association with the CD-ROM's own P/N-edition, is also loaded in the Alcatel-
Information-System as a structured list.
This causes the planning and creation of a new edition of the CD-ROM.
Updating of CD-ROMs always follows, with a certain delay, the updating of the single
handbooks composing the collection.
It will contain 3 numbers separated by two blank (space) characters in the following order:
Jitter Buffer Size is 479us (that is, the initial filling level); Queue Size is 8 packets (2exp3);
Payload size is 26 bytes.
The flag file will affect any TDM2ETH terminated in the NE.
It is mandatory to apply that to NE where DS1 enter and exit (this is not mandatory if the
NE is only traversed by DS1).
• Only all synchronous DS1 on a single hop in 1+0 / 1+1 without lag
• Only 1 hop with 30 MHz/128 QAM profile
• Payload size 26
• max jitter buffer (queue size 8 packets)
The user must be aware that reducing Payload length will affect the maximum number of
DS1 that can fit on a specific profile: when the Payload length is reduced the number of
DS1 fitting on a specific profile is reduced accordingly.
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 Alarm Severity Assignment must be named def_asap4.psh.
The configuration file for SFP 2E1/DS1 Circuit Emulation must be named as follows based
on the optical port used to host the SFP module and CORE slot used:
The configuration files for a radio direction provisioned to have MPT as split-mount ODU
must be named as follow, according to the MSS slot/port used for connection:
MPTcf_x_y.psh where
• x=0, y=0,1,2,3,4,5 identifies the case of MPT connected to Core Main port:
y=0 identifies Port 1 Electrical
y=1 identifies Port 2 Electrical
y=2 identifies Port 3 Electrical
y=3 identifies Port 4 Electrical
y=4 identifies Port 5 Optical
The configuration file for Ethernet switch inside the EAS plug-in must be named
fullConfig_eas.psh.
In case of multiple EAS cards, this file must contain the commands for all EAS cards.
The configuration file for Ethernet switch inside the EASv2 plug-in must be named
fullConfig_easv2.psh.
In case of multiple EASv2 cards, this file must contain the commands for all EASv2 cards.
When CORE protection is not configured in the system, only configuration files for CORE
Main (a and/or b) should be present in the Flash Card, while, when CORE protection is
present, all configuration files (a and/or b together with c and/or d).
Anyway the presence of CORE Spare configuration files in a not protected configuration
does not create any issue to the system. At the same time, it could be a good approach that
allows the system to be ready to a possible upgrade to CORE protection in case CORE
spare is in a second time.
Use # at beginning of the line to write a comment inside the Configuration File, the
comment is 'private'.
def_asap4.psh and MPTcf_x_y.psh files must be uploaded to the Compact Flash (on main
CORE when it is active) via File Transfer Manager tool (see Appendix section 5.2).
Through the embedded file editor, user can define its own configuration file and save it on
local PC using the proper file name as indicated in File Name. Once all necessary
commands have been inserted, by the means of “Add File” button the user copies the file
from local PC to the NE and the file is consequently saved inside Compact Flash.
For MOD300, MPT Access, EAS, and EASv2 card supporting Enhanced configuration
with one file for all provisioned peripheral type, the insertion of a single plug-in also causes
the execution of the whole Configuration file, including the command related to peripheral
that were not plugged-in at that time.
That means that it is assumed that “re-application of commands related to peripherals that
were not plugged-in does not have any traffic impact”.
Selecting the intended file, the user can remove each configuration from the list of file
inside the Flash Card. This action results in file removal from Flash Card only. In order to
disable all configuration file features see Restoring Ethernet switch initial configuration,
Restoring MOD300 initial configuration, and Restoring SFP 2xE1/DS1 configuration.
Simply removing configuration file from Compact Flash does not imply the removal of all
features applied by configuration file itself.
Differently from what has been described above, def_asap4.psh and MPTcf_x_y.psh
removal requires to use the “Delete” button of File Transfer Manager (see Appendix
section 5.2). Also in this case, removal of file doesn't imply the removal of all features.
The operator is allowed to append a new command on one of the following and already in
use configuration files:
• enhanced_eth_feature.psh
• fullConfig_mptacc.psh
• fullConfig_radio.psh
• fullConfig_eas.psh
• fullConfig_easv2.psh
By Configuration File No Restart tool, the user is required to create a new file on local PC
that will include all the new commands. Then, once finished, the user must select from the
list of files already present on the NE, the intended file to be appended and use the “Append
Command” button. This action triggers the execution of the new commands on the NE and
the consequent file update in Compact Flash.
On the contrary, all configuration files for SFP 2xE1/DS1 shall not be appended.
Configuration File No Restart tool does not prevent the operator to add any new command
inside a file already present inside the Flash Card, but it is extremely important to respect
the command order shown in Configuration File basic structure. Not following that scheme
causes a wrong SFP module configuration and the service is not established.
For this reason, SFP configuration files must be always copied locally, removed from flash
card (since CFNR tool requires this), updated with all new commands according to
paragraph Configuration File basic structure and then uploaded as new complete file in the
NE using “AddFile”.
Any configuration file update operation may cause a temporary traffic impact.
Caution: Do not switch the CORE Board after Configuration File upload, until the new
Configuration File is applied.
• enhanced_eth_feature.psh
• fullConfig_mptacc.psh
• fullConfig_radio.psh
• MPTcf_x_y.psh
• fullConfig_eas.psh
• fullConfig_easv2.psh
1. restore the initial configuration of the switch or radio (see Restoring Ethernet switch
initial configuration, Restoring MOD300 initial configuration, and Restoring MPT
initial configuration).
2. upload a new configuration file if necessary according to the procedure described in
section Configuration File upload and execution.
This procedure does not apply to SFP 2xE1/DS1 configuration files. Whenever the operator
needs to remove one of the two tributaries or change a parameter to an existing one (e.g.
change the VLAN ID), it is required the complete configuration file(s) removal (see
Configuration File Removal) and the upload of the new configuration file(s) according to
paragraph Configuration File upload and execution.
Note: Do not switch the CORE Board after Configuration File upload, until the new
Configuration File is applied.
1. CORE, EAS, EASv2 and MPT-ACC CFs must be removed from flash card (see
Configuration File Removal);
2. CORE, EAS, EASv2 and MPT-ACC “restoring CF” (see below) must be executed on
the NE (see Configuration File upload and execution);
3. CORE, EAS, EASv2 and MPT-ACC “restoring CF” must be removed from flash card
(see Configuration File Removal).
4. After this, the user must perform an NE restart by CT/NMS to completely remove the
effect of the configuration file.
After this, the user must perform a NE restart by CT/NMS to completely remove the effect
of configuration file.
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)
Where S nibble assumes the following value based on AUX card slot position:
S=3 if the AUX Board is inserted into slot 4 (second column, second row)
S=7 if the AUX Board is inserted into slot 8 (second column, fourth row)
In order to restore this MPT default configuration, after deletion of the file from NE
Compact Flash, in order MPT to apply to HW its persistent configuration, a cold restart of
MPT is needed.
In the current release MPT cold restart can be achieved only as result of NE or MPT power
switch off/on (the latter is available to management system in case of connection to MPT
Access plug-in).
If the above procedure is not possible or wanted, the alternative solution for restore of MPT
default configuration is to explicitly put it into the MPT config file and then trigger its
execution (see section Configuration File upload and execution).
At the same time, a different behavior is supported for 2xE1/DSI SFP since there are
dedicated configuration file for CORE Main and CORE Spare (see File Name)
When CORE protection is not configured in the system, only SFP configuration file(s) for
the Main CORE card must be present in the Flash Card. On the contrary, when CORE
protection is present, all SFP configuration files for both Main and Spare must be present.
Regarding the configuration file for MOD300, MPT-ACC, EAS, and EASv2 boards
(fullConfig_radio.psh, fullConfig_mptacc.psh, fullConfig_eas.psh, and
fullConfig_easv2.psh), the mated Board is managed as an independent Radio Board. In
this case the radio configuration file must contain the configuration of both radio cards.
Additionally, even all commands inserted into enhanced_eth_feature.psh file have to be
duplicated for both Main and Spare ports in case of radio in protection.
The same principle applies for MPT. In this case the user has to provide a Configuration
file MPTcf_x_y.psh for each radio channel, where x,y identifies MSS slot/port the MPT is
connected to. The content of the these two files must be the same.
Feature
MPR-E 1.2.2
MPR-E 1.3.0
MPR-E 1.4.0
MPR-E 3.0.0
MPR-E 3.2.0
MPR-E 3.4.0
MPR-E 4.1.0
MPR-E 5.0.0
MPR-E 5.2.0
2.1.0
3.1.0
3.3.0
4.0.0
4.2.0
5.1.0
QINQ YES YES YES YES YES YES n.a. n.a n.a
Autonegotiation on SFP port n.a. YES YES n.a. n.a. n.a. n.a. n.a n.a
VLAN swap YES YES YES YES YES YES YES n.a n.a
Out of Range VLAN swap n.a. YES YES YES YES YES YES YES YES
VLAN swap and dot1p n.a. YES YES YES YES YES YES YES YES
Remarking for ATM PW
Service
VLAN swap and forwarding n.a. YES YES YES YES YES YES YES YES
for “local ATM switch"
Port Based Rate Limiting n.a. n.a. YES YES YES n.a. n.a. n.a. n.a
Storm Control n.a. n.a. YES YES YES n.a. n.a. n.a. n.a
Access Control List n.a. n.a. YES YES YES YES YES YES YES
Per VLAN rate limiting n.a. n.a. YES YES YES n.a. n.a. n.a n.a
Ethernet Switch Scheduler YES YES YES YES n.a. n.a. n.a. n.a n.a
Setting
MOD300 Scheduler Setting NO YES YES YES n.a. n.a. n.a. n.a n.a
MOD300 802.1p Mapping to YES YES YES YES n.a. n.a. n.a. n.a n.a
Queues
Ethernet Switch Mapping NO NO NO NO n.a. n.a. n.a. n.a n.a
DiffServ to Queues for IPv4
frames
MOD300 Mapping DiffServ to YES YES YES YES n.a. n.a. n.a. n.a n.a
Queues for IPv4 frames
Ethernet Switch IPv6 QoS NO NO NO NO n.a. n.a. n.a. n.a n.a
support with flexible
mapping traffic class to
queues
MOD300 IPv6 QoS support YES YES YES YES n.a. n.a. n.a. n.a n.a
with flexible mapping traffic
class to queues
SFP 2E1/DS1 CIRCUIT n.a. n.a. n.a. YES YES YES YES YES YES
EMULATION
ASAP n.a. n.a. n.a. YES YES YES YES YES YES
QoS based on MPLS TC n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. YES
Each not portable Ethernet feature can be easily adapted following the rules described this
document. Once a configuration file, already in use in a previous release, has been adapted
it is possible to upgrade the system with MPR 5.x.
If a Core Port is provisioned as Radio Port, the applicable Enhanced Configuration is the
one that is applicable as Radio Port, not as User Port.
Unless otherwise stated, Enhanced Configuration features related to User Port are
applicable to EAS Ports and EASv2 Ports provisioned as User Ports.
Enhanced Configuration features are applicable to EAS Ports or EASv2 Ports provisioned
as Radio Ports only for what regards VLAN management (as it applied in case of MPT-
ACC prior to MPR 3.1.0).
• enhanced_eth_feature.psh.
• fullConfig_mptacc.psh
• fullConfig_eas.psh
• fullConfig_easv2.psh
• fullConfig_radio.psh.
• def_asap4.psh.
• SFP_2xE1DS1_x_y.psh with x=0,1 for Core Main/Spare, y=1,2 for Optical Port 5/
6 respectively
• MPTcf_x_y.psh with
• x=0, y=0,1,2,3,4,5 identifies the case of MPT connected to Core Main port
• x=2,3,4,5,6,7 y=0,1,2,3 identifies the case of MPT connected to MPT Access
plug-in port
ge6 7 ge4 5
ge20 21
Slot 1 Slot 2
Slot 3 Slot 4
Slot 5 Slot 6
Slot 7 Slot 8
Slot 1 Slot 2
Slot 3 Slot 4
All the commands applicable to Core Switch User Ports are applicable to EAS User Ports
and EASv2 User Ports.
Conversely, not all the commands reported inside this guide are valid for MPT-ACC
switch.
For this reason, all commands applicable for MPT-ACC will be expressively indicated into
the relative paragraph later on in the document. When not indicated, the command is
intended to be applicable for CORE, EAS, or EASv2 only and so it must be inserted into
“enhanced_eth_feature.psh”, “fullConfig_eas.psh”, or “fullConfig_easv2.psh” only.
The following syntax has to be respected based on MPT-ACC, EAS or EASv2 slot position.
Command example:
This example creates VLAN 100 inside MPT-ACC on ge5 and ge9 interfaces.
Moreover, some of the features illustrated in this guide require a preliminary configuration
not only for CORE Ethernet switch, but also for MPT-ACC switch, EAS switch or EASv2
switch. So, it is required to specify the correct SLOT number MPT-ACC/EAS/EASv2 is
lodged for each preliminary configuration command. In case of multiple MPT-ACC/EAS/
EASv2, the preliminary configuration must be replicated for all MPT-ACC/EAS/EASv2
present into the system changing the SLOT number accordingly.
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:
Nibble Y and X depends on the slot position (CORE Main/Spare) and port (optical 5/6) of
the module:
So, assuming SFP plugged into CORE Main optical port 5 and no CORE protection
configured, the following could be an example of register write operation:
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:
<<byte stream for MAP message>> is the sequence of ASCII characters representing
hexadecimal coding of MAP message octets with space separator
3.4.1 — Example
#Configure QoS Classification
MAP, 4 6c 0 0 1 1
0 : reserved.
The configuration described in this section therefore is no more applicable. It is kept only
for information purpose.
4.1.2 — Overview
Auto-Negotiation configuration on SFP ports is handled by a single register according to
Figure 4.1.
On CORE Main, disable Auto-Negotiation on both optical ports 5 and 6 (flow control
disabled):
Note: in order to apply the command, it is required to disable and enable again the port
by CT/NMS once the configuration file has been applied.
On CORE Main, enable Auto-Negotiation on both optical ports 5 and 6 (flow control
disabled):
On CORE Main, enable Auto-Negotiation on optical port 6 keeping port 5 with Auto-
Negotiation disabled (flow control disabled):
On CORE Main, enable Auto-Negotiation on optical port 5 keeping port 6 with Auto-
Negotiation disabled (flow control disabled):
Note: in order to apply the command, it is required to disable and enable again the port
by CT/NMS once the configuration file has been applied.
4.2.1 — Background
MPR official releases provides full 802.1Q feature only for VLAN in range [2:4080]. For
some specific network condition, it may be required to have MPR in charge to transport
traffic having VLAN ID out of this range. It is possible to admit out of range VLANs inside
MPR following the guidelines described inside this chapter.
The scenario considered in this chapter is the one shown in Figure 4.2.
The MPR is used to connect two already existing 802.1Q environments that use a VLAN
out of MPR range. All MPR equipment inside the MPR network should be configured in
802.1Q bridge mode and fully provisioned by CT/NMS. Only two MPRs require
configuration file in order to admit the out of range VLAN and are indicated as Gateway 1
and Gateway 2. These two Gateways can emulate the same behavior obtainable with
802.1Q bridge mode.
• VLAN creation/membership
• port role definition
• port VLAN assignment
• port parameters
• VLAN SWAP rules
This configuration has an intrinsic limitation and cannot accept more than 1000 different
VLANs on UNI ports (sum of UNI VLANs).
# configure Radio ports of EAS as NNI (if SFP ports are provisioned as radio ports).
If a EAS SFP Port is instead provisioned as User Port, then the same command applied to
Electrical Ports has to be used.
# configure Radio ports of EASv2 as NNI (if SFP ports are provisioned as radio ports).
If a EASv2 SFP Port is instead provisioned as User Port, then the same command applied
to Electrical Ports has to be used.
• <pbm>: list of possible ports; Core Switch range: ge5, ge6, ge17, ge18, ge19, ge20
and each slot lodging a MOD300 Radio Board/EAS/EASv2 or AUX board; EAS
switch range and EASv2 switch range: see Switch to equipment ports assignment;
mandatory.
• <type>: it is the port definition that can be internal for NNI ports or external for UNI
ports; mandatory.
Note: on CORE ports from ge11 to ge16 refers to MSS slots; this command must not be
applied to ports toward slot where a PDH and ASAP cards is lodged. Applying this command
toward PDH or ASAP slots will destroy all the E1/ATM traffic.
In case of EAS or EASv2, the <slot-1> number must be added to the above command.
For all user ethernet ports configured as UNI, requires the following commands.
• <pbm>: user UNI port bitmap; Core switch range: ge6, ge17, ge18, ge19, ge20; EAS
switch range and EASv2 switch range: see section Switch to equipment ports
assignment; mandatory.
• <vid>: integer number used as VLAN ID; range: 2-4080; mandatory. Vid must have
been created previously and all ports in <pbmp> must belong to that VLAN.
• <n>: 802.1p priority value for incoming untagged frames; range [0:7]; mandatory;
Note: The bcm port command implies always a switch off/on of the involved port; so,
anytime the configuration file will be applied a traffic hit will always occurs on the
involved port.
In case of EAS or EASv2, the <slot-1> number must be added to the above command.
For all user ethernet ports configured as NNI, requires the following commands.
• <pbm>: user NNI port bitmap; range: Core switch ge5, ge6, ge17, ge18, ge19, ge20;
EAS switch range and EASv2 switch range: see section Switch to equipment ports
assignment; mandatory.
• <vid>: integer number used as VLAN ID; range: 2-4080; mandatory. Vid must have
been created previously and all ports in <pbmp> must belong to that VLAN.
• <n>: 802.1p priority value for incoming untagged frames; range [0:7]; mandatory;
• <type>: possible vale are tag|untag|none in order to drop respectively tagged,
untagged or none frames; mandatory.
Note: The bcm port command implies always a switch off/on of the involved port; so,
anytime the configuration file will be applied a traffic hit will always occurs on the
involved port.
In case of EAS or EASv2, the <slot-1> number must be added to above command.
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 as crossconnect internal flows (i.e. TDM2TDM, TDM2ETH, ATM)
cannot be used; mandatory.
• <pbmp>: pbmp is a list of possible ports members of VLAN <id>;
a. CORE range: ge5, ge6, ge11-ge20; mandatory.
b. MPT-ACC range: ge5, ge6, ge7, ge8, ge9; mandatory.
c. EAS range: see Switch to equipment ports assignment for the list of backplane
and User/Radio Ports.
d. EASv2 range: see Switch to equipment ports assignment for the list of
backplane and User/Radio Ports.
• <ubmp>: pbmp is a list of possible ports members of VLAN <id> that forward the
frame untagged;
a. CORE range: ge5, ge6, ge17, ge18, ge19, ge20; optional.
b. MPT-ACC range [none]; not applicable.
c. EAS range: see Switch to equipment ports assignment for the list of User Ports;
optional.
d. EASv2 range: see Switch to equipment ports assignment for the list of User
Ports; optional.
Note: on CORE ports from ge11 to ge16 refers to MSS slots; this command must not be
applied to ports towards slot where a PDH, AUX and ASAP cards are lodged.
Note: This configuration has an intrinsic limitation and cannot accept more than 1000
different VLANs on UNI ports (sum of UNI VLANs).
• <pmb>: port bitmap associated to the newVlanID; AUX, PDH and ASAP card must
not be included into this bitmap; Core switch range ge11-ge20; EAS switch range and
EASv2 switch range: see Switch to equipment ports assignment; mandatory.
• <portNum>: user port number which is receiving out of range VLAN; Core Switch
range: 6,7, 18,19,20,21; EAS switch range and EASv2 switch range: see Switch to
equipment ports assignment; mandatory.
• <oldID>: incoming out of range VLANID to be swapped; range [4081:4094];
mandatory.
• <newID>: new VLANID used to remark the incoming out of range VLANID; range
[2:4080]; mandatory.
• <n>: priority value used to replace the incoming 802.1p bits; -1 value is used in order
to not replace the incoming frame priority; mandatory.
• <portNum>: user port number which is receiving out of range VLAN; Core switch
range: 6,7, 18,19,20,21; EAS switch range and EASv2 switch range: see Switch to
equipment ports assignment; mandatory.
• <vlanID>: UNI incoming/outgoing VLANID; range [2:4080]; mandatory.
Note: This configuration has an intrinsic limitation and cannot accept more than 1000
different VLAN on UNI ports (sum of UNI VLANs).
• <pbm>: pbmp is a list of possible ports; Core switch range: ge5, ge6, ge17, ge18,
ge19, ge20; EAS switch range and EASv2 switch range: see Switch to equipment
ports assignment; mandatory.
Note: The above command implies always a switch off/on of the involved port; so,
anytime the configuration file will be applied a traffic hit will always occurs on the
involved port.
Gateway 1 NE configuration:
Gateway 2 NE configuration:
#Configure UNI
#Configure NNI
#Configure UNI
#Configure NNI
4.3.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 having same CoS and forwarding path).
Moreover, dot1p bit field within VLAN tag of ATM PW frames is used to dynamically
mark them, on the MPR NEs where it is present the native ATM interface (ATM/IMA/E1),
as "Green" (MPR network is committed to reserve bandwidth on each radio interfaces) or
"Yellow" (they can be dropped in case of congestion on any of radio interfaces) as result of
bandwidth profiling resulting from native ATM Traffic Descriptor.
VLAN Swap and dot1p remarking can be provisioned to support inter-working of ATM
PseudoWire Service with IP/MPLS equipment (to support that a special configuration of
all MPR NEs in the network is required).
In short this feature allows to make independent, on the MPR NE interfacing the IP/MPLS
equipment, the ATM PW Service from Ethernet Layer 2 transport used within the overall
MPR network:
• all ATM PW flows egressing MPR network will have the same VLAN ID, which has
been swapped from the several VLAN IDs used by ATM PW flows within MPR
network
• for the opposite direction, all ATM PW flows ingressing MPR network will have the
above common VLAN ID swapped to VLAN IDs used by ATM PW flows on single
PW basis (i.e. according to the PW Label value)
• all ATM PW flows egressing MPR network will have the same 802.1p bit field
remarked according to ATM PW CoS information contained into EXP bit field of
ATM PW Label (removing the "Green" or "Yellow" information)
• for the opposite direction, all ATM PW flows ingressing MPR network will have the
same 802.1p bit field remarked as "Green"
Such operations requires, only for MPR NE interfacing the IP/MPLS equipment, the use of
a dedicated configuration file as described in the following.
Since cross-connection of ATM PW flows is not supported for EAS User ports and EASv2
User ports, this configuration is applicable only to Core User Ports.
The presence of this flag file is needed on all NEs where ATMoMPLS frames with Tunnel
Label are transported (e.g. to enable the specific header compression on radio cards).
In addition to that, the procedure allows the define the NE common value of the MPLS
Tunnel Label itself for the NE with ASAP Card(s) (as it is the ASAP Card that add the
MPLS Tunnel Label to all ATM PWs).
In this way the NE DataBase and MIB will be automatically updated without the need of
performing the setting by the NE WebServer as described in Appendix section
ATMoMPLS Protocol Stack Configuration by HTTP interface (MPR WebServer).
The file must contain a single line with the decimal value of the common MPLS Tunnel
Value to be applied by the ASAP Card(s), if any. For example if the MPLS_Migration file
contains the row
5000
the decimal value of MPLS Tunnel Value added by ASAP Card(s), if any, will be 5000 and
in any case the NE in configured to manage ATMoMPLS frames with Tunnel Label.
Warning: Applicable only for release MPR-E 2.1: the file used for migration /home/adm-
lc-ng/debug/MPLS_Migration must be removed after the migration to release MPR-E 2.1
has been performed.
All ATM PW flow cross-connections (radio to user Ethernet port or ASAP Card to
Ethernet) have to be provisioned by CT/NMS as usual, with assignment of the VLAN IDs
and Peer MAC Address.
This enhanced configuration may overlap for FP Group #4 and rule IDs used with the
feature described in DOT1P ASSIGNMENT BASED ON INCOMING DIFFSERV. It is
up to the user to ensure consistency in case these features are being applied at the same time
(i.e. avoiding creating Group #4 twice and using same IDs).
Note: this feature is normally intended to be used together with “mpls_label_enable” flag
file (see Management of flag file on MPR).
Command example:
Assuming to have a ATM PW XC configured on port ge11 and port ge17 (user ethernet
port 1), the previous commands enable 802.1p bits remarking for traffic coming from both
ports.
n n
ge6 1 ge19 4
ge17 2 ge20 5
ge18 3
The following commands are needed for the common VLAN ID value used to swap the
several VLAN IDs used by ATM PW flows:
• <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.
• <egrLAN> is the common VLAN ID used by all ATM PW frames egressing MPR
NE; mandatory.
• <egrPortNum> user ethernet port number where ATM PW frames will egress MPR
network; range 7, 18,19,20,21; mandatory.
• <n> vlan swap rule entry; this value is the one referred at paragraph Per CoS 802.1p
bit remarking rule definition, so this two parameters must have the same value; see n
values on a per port basis depending on user ethernet port used; mandatory.
• <egrVLANH>: must be expressed in hex coding; mandatory.
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:
• <ID>: rule ID number; range[512:527]; the chosen value should not be shared among
different rules; mandatory.
• <CoS>: CoS value number; see CoS and newdot1p parameters by ATM PW CoS ;
mandatory.
• <NE MAC Address>: MPR NE MAC Address in xx:xx:xx:xx:xx:xx format (HEX);
mandatory.
• <n>: vlan swap rule entry; this value is the one referred at paragraph Egress VLAN
swap rule definition, so this two parameters must have the same value; see n values
on a per port basis depending on user Ethernet port used; mandatory.
• <egrDot1p>: 802.1p bits value to remap in egress direction on a per ATM PW CoS
basis; see the table below; mandatory.
For MPR 3.0.0 release, 3 rules are therefore needed for CRB/UBR+/UBR CoS, Table 4.2
reports the values for above CoS and newdot1p parameters according to ATM PW CoS:
CBR 0x00000C00 6
UBR+ 0x00000400 2
UBR 0x00000000 0
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.
• <m>: vlan swap rule entry; this value is also referred at paragraph Per ATM PW flow
802.1p bit remarking rule definition and, considering a single ATM PW, this value
must be equal to the one used at paragraph Per ATM PW flow 802.1p bit remarking
rule definition; range [6:245]; mandatory.
• <VLANH>: is the VLAN ID associated to the ATM PW flow; must be expressed in
hex coding; mandatory.
For each ATM PW flow, a rule with below pattern must be configured:
• <ID>: unique rule ID number; range[528:767]; the chosen value should not be shared
among different rules; mandatory
• <PW Label>: 0xZZZZZ000, ZZZZZ is the hex coding of 20-bit PW Label value;
mandatory.
• <NE MAC ADDRESS>: MPR NE MAC Address in xx:xx:xx:xx:xx:xx format
(HEX); mandatory.
• <ingPbm>: user ethernet port bitmap where ATM PW frames will ingress MPR
network; see Table 4.5; mandatory.
• <m>: vlan swap rule entry; this value is also referred in Ingress VLAN swap rule
definition and, considering a single ATM PW, this value must be equal to the one
used in Ingress VLAN swap rule definition; range[6:245]; mandatory.
• <NextPbm>: user ethernet port(s) bitmap where ATM PW frames are forwarded to
(e.g. radio/PDH ports in 1+0, or 1+1); see Table 4.4; mandatory.
• <ingDot1p>: 802.1p bits value to remap in ingress on a per ATM PW CoS basis; see
Table 4.3; mandatory.
CBR 0x00000C00 6
UBR+ 0x00000400 4
UBR 0x00000000 4
Table 4.4 — User ethernet port bitmap where ATM PW frames are forwarded
NextPbm NextPbm
ge15 0x010000
Table 4.5 — User Ethernet port bitmap where ATM PW frames ingress the network
ingPbm ingPbm
#Preliminary Configuration
# Ingress 802.1p bits remarking for ATM PW CBR with label=0x80000 forwarded to ge12
4.4.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:
The purpose of configuration file is to allow ATM PW flow frame forwarding, without an
external cable if two ports are involved, and the swap between VLAN IDs used by ATM
PW flow pair.
The structure of configuration file is similar to the one used for “VLAN swap and dot1p
Remarking for ATM PW Service”, section VLAN SWAP AND DOT1P REMARKING
FOR ATM PW SERVICE.
For this “Local ATM Switch” feature, however no flag file is foreseen.
In principle this feature can be used on the same NE where “VLAN swap and dot1p
Remarking for ATM PW Service” feature is enabled, but for sure it involves different ATM
PW flows: the “Local ATM Switch” foresees termination at ATM level, while “VLAN
swap and dot1p Remarking for ATM PW Service” is applied at ATMoMPLS traffic.
Since cross-connection of ATM PW flows is not supported for EAS User ports and EASv2
User ports, this configuration is applicable only to Core User Ports.
• ATM PW flow #1, with PWLabel_1, terminated on ASAP Card #1, uses VLAN_1 to
be cross-connected towards Ethernet User port #1, with MAC DA #1.
• ATM PW flow #2, with PWLabel_1, terminated on ASAP Card #2, uses VLAN_2 to
be cross-connected towards Ethernet User port #2, with MAC DA #2.
The following commands must be then added to the Core Ethernet Switch configuration
file.
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).
• <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
• <n_x>,<n_y>: vlan swap rule entries; these values are the ones referred at paragraph
VLAN swap and frame forwarding rule definition; mandatory.
• <VLAN_xH>, <VLAN_yH>: VLAN IDs used by ATM PW flow #x and #y, must
be expressed in hex coding; mandatory.
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.
• <ID1>: unique rule ID1 number; range[528:767]; the chosen value should not be
shared among different rules; mandatory;
• <VLAN_xH>: VLAN IDs provisioned for ATM PW flow #x; must be expressed in
hex coding; mandatory.
• <pbmp_y> is the port bitmap, as defined by User Ethernet port bitmap where ATM
PW frames ingress the network, that identifies the CORE port connected to ASAP #y;
• <n_y>: vlan swap rule entry; this value is the one referred at paragraph VLAN swap
- preliminary definition; mandatory.
The next list of commands defines the actual rule that identifies ATM PW frames belonging
to ATM PW#y (terminated on ASAP #y), swap their VLAN_y into VLAN_x and forward
it to CORE Ethernet Switch port connected to ASAP Card #x.
• <ID2>: unique rule ID2 number; range[528:767]; the chosen value should not be
shared among different rules; mandatory;
• <VLAN_yH>: VLAN IDs provisioned for ATM PW flow #y; must be expressed in
hex coding; mandatory.
• <pbmp_x> is the port bitmap, as defined by User Ethernet port bitmap where ATM
PW frames ingress the network, that identifies the CORE port connected to ASAP #x;
• <n_x>: vlan swap rule entry; this value is the one referred at paragraph VLAN swap
- preliminary definition; mandatory.
1. ATM PW #1 and #2 are terminated on ASAP #1 and ASAP #2, with below
parameters:
• same E1 and IMA configuration (optional)
• same ATM configuration (VPI,VCI, VP role, TD, etc)
• same PW label
• same cell concatenation configuration
2. For ATM PW #1 terminated on ASAP #1, below Ethernet encapsulation parameters
applies:
• MAC DA = 30:30:30:30:30:30
• MAC SA = NE MAC = 44:44:44:44:44:44
• VLAN ID = 4
3. For ATM PW #2 terminated on ASAP #2, below Ethernet encapsulation parameters
applies:
• MAC DA = 32:32:32:32:32:32
• MAC SA = NE MAC = 44:44:44:44:44:44
• VLAN ID = 5
Content of “enhanced_eth_feature.psh”:
# Entry 114 is used for ATM PW#2 frames, VLAN swap from 5 to 4
# Entry 115 is used for ATM PW#1 frames, VLAN swap from 4 to 5
This feature can be applied to EAS User Ports and EASv2 User Ports.
• <pbm>: user ethernet port bitmap where ACL applies to; see Table 4.6; mandatory.
pbm Description
ge5, ge6,ge17-ge19 0x1c00c0 All user port except port 4 (ge20) when used as TMN
ge5-ge12 0x3fc0 All EAS user port (ETH1-ETH4,SFP5-SFP8)
Id parameters defined above has to be considered differently in the following three bridge
mode:
• 802.1D
• id is equal to 1 if the frame was originally untagged;
• id is equal to VLAN id carried inside VLAN Tag if the frame was originally
tagged and this VLAN id is already in use by a TDM2ETH XC involving any
user ethernet port;
• 802.1Q
• id is equal to VLAN id carried inside vlan Tag if the frame was originally
tagged;
• id is equal to PVLAN in case the frame is coming in untagged and then tagged
on a port based way;
• 802.1D + QINQ (by cfg file)
• id is equal to Service VLAN id the incoming packet is mapped to;
In case of EAS or EASv2, the <slot-1> number must be added to above command.
4.6.1 — Description
SFP 2E1/DS1 is an SFP module supporting circuit emulation service of up to 2 tributaries
(E1/DS1) that can be hosted in one of the two optical ports of the CORE card. None of the
other optical ports in the equipment can support this module in this release. Despite the
hardware readiness of the module, this release supports circuit emulation service for E1/
DS1 in TDM2ETH/TDM2TDM profile only. Moreover, SFP module is supposed to be
connected to one of the two optical ports of the CORE card. Additionally, SFP module is
supposed to properly work without static LAG.
SFP module can interwork with radio interfaces (M300, MPT) and PDH card. The way of
configuring the module is divided into two parts. The former makes use of a configuration
file (whose content is described here) and the latter is based and CT/NMS. Based on the
configuration needed, a configuration file (or more, see paragraph 6.1) shall be loaded
inside the NE Flash Card. The content of the file(s) shall include all the commands
necessary to properly configure the circuit emulation service up to two IWF. Once the SFP
module is properly configured, using CT/NMS the operator has to perform cross-
connection operation using the proper panel in order to establish the cross-connection
between the SFP and any other interface/card of the equipment. In order to complete the
cross-connection, CT/NMS requires as input the Next Hop MAC address. See Normal
procedure to use the proper MAC address.
During XC configuration, the operator will be asked to select the TDM service and
inserting Flow ID (supposed to be equal to VLAN ID used to configure the specific
tributary) along with the destination MAC address (see SFP configuration). Depending on
the ports the SFP module has been insert, MAC address to be used must be on of the
following two:
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.
setreg 03300020 0c
setreg 03300003 29
setreg 03300005 00
setreg 03300002 09
setreg 03300025 00
setreg 03200000 34
setreg 04300020 0c
setreg 04300003 29
setreg 04300005 00
setreg 04300002 09
setreg 04300025 00
setreg 04200000 34
setreg 03500004 FE
setreg 03500000 01
setreg 03500005 03
setreg 03500006 07
setreg 03500007 00
setreg 03500008 04
setreg 03500009 14
setreg 0350000a 00
setreg 0350000b 00
setreg 03500010 0c
setreg 03500011 00
setreg 03500018 00
setreg 0350001d a2
setreg 0350001e 86
setreg 0350001f 41
setreg 03500001 00
setreg 03500002 00
setreg 03500003 00
setreg 03700080 50
setreg 03700081 35
setreg 03700082 0c
setreg 03700083 00
setreg 03700084 b0
setreg 03700085 34
setreg 03700086 0c
setreg 03700087 00
setreg 03700088 00
setreg 03700089 35
setreg 0370008a 0c
setreg 0370008b 00
setreg 0370008c 00
setreg 0370008d 0c
setreg 0370008e 00
setreg 0370008f 00
setreg 03700090 03
setreg 03700091 00
setreg 03700092 02
setreg 03700093 00
setreg 03700094 04
setreg 03700095 01
setreg 03700096 07
setreg 03700097 f0
Note: "setreg 0350001c" has not been specialize here, see Clock recovery type
setreg 03500044 FE
setreg 03500040 01
setreg 03500045 03
setreg 03500046 07
setreg 03500047 00
setreg 03500048 04
setreg 03500049 14
setreg 0350004a 00
setreg 0350004b 00
setreg 03500050 0c
setreg 03500051 00
setreg 03500058 00
setreg 0350005d a2
setreg 0350005e 86
setreg 0350005f 41
setreg 03500041 00
setreg 03500042 00
setreg 03500043 00
setreg 037000c0 50
setreg 037000c1 35
setreg 037000c2 0c
setreg 037000c3 00
setreg 037000c4 b0
setreg 037000c5 34
setreg 037000c6 0c
setreg 037000c7 00
setreg 037000c8 00
setreg 037000c9 35
setreg 037000ca 0c
setreg 037000cb 00
setreg 037000cc 00
setreg 037000cd 0c
setreg 037000ce 00
setreg 037000cf 00
setreg 037000d0 03
setreg 037000d1 00
setreg 037000d2 02
setreg 037000d3 00
setreg 037000d4 04
setreg 037000d5 01
setreg 037000d6 07
setreg 037000d7 f0
Note: “setreg 0350005c" has not been specialize here, see Clock recovery type
setreg 04500004 FE
setreg 04500000 01
setreg 04500005 03
setreg 04500006 07
setreg 04500007 00
setreg 04500008 04
setreg 04500009 14
setreg 0450000a 00
setreg 0450000b 00
setreg 04500010 0c
setreg 04500011 00
setreg 04500018 00
setreg 0450001d a2
setreg 0450001e 86
setreg 0450001f 41
setreg 04500001 00
setreg 04500002 00
setreg 04500003 00
setreg 04700080 50
setreg 04700081 35
setreg 04700082 0c
setreg 04700083 00
setreg 04700084 b0
setreg 04700085 34
setreg 04700086 0c
setreg 04700087 00
setreg 04700088 00
setreg 04700089 35
setreg 0470008a 0c
setreg 0470008b 00
setreg 0470008c 00
setreg 0470008d 0c
setreg 0470008e 00
setreg 0470008f 00
setreg 04700090 03
setreg 04700091 00
setreg 04700092 02
setreg 04700093 00
setreg 04700094 04
setreg 04700095 01
setreg 04700096 07
setreg 04700097 f0
Note: "setreg 0450001c" has not been specialize here, see Clock recovery type
setreg 04500044 FE
setreg 04500040 01
setreg 04500045 03
setreg 04500046 07
setreg 04500047 00
setreg 04500048 04
setreg 04500049 14
setreg 0450004a 00
setreg 0450004b 00
setreg 04500050 0c
setreg 04500051 00
setreg 04500058 00
setreg 0450005d a2
setreg 0450005e 86
setreg 0450005f 41
setreg 04500041 00
setreg 04500042 00
setreg 04500043 00
setreg 047000c0 50
setreg 047000c1 35
setreg 047000c2 0c
setreg 047000c3 00
setreg 047000c4 b0
setreg 047000c5 34
setreg 047000c6 0c
setreg 047000c7 00
setreg 047000c8 00
setreg 047000c9 35
setreg 047000ca 0c
setreg 047000cb 00
setreg 047000cc 00
setreg 047000cd 0c
setreg 047000ce 00
setreg 047000cf 00
setreg 047000d0 03
setreg 047000d1 00
setreg 047000d2 02
setreg 047000d3 00
setreg 047000d4 04
setreg 047000d5 01
setreg 047000d6 07
setreg 047000d7 f0
Note: "setreg 0450005c" has not been specialize here, see Clock recovery type
setreg 03600040 00
setreg 03600042 d8
setreg 03600043 88
setreg 03700000 0a
setreg 03700001 14
setreg 03700002 00
setreg 03700003 00
setreg 03600000 09
setreg 03600001 9f
setreg 03600002 80
setreg 03600003 00
setreg 03600006 50
setreg 03600007 f0
setreg 03600008 09
setreg 03600009 9f
setreg 0360000a 80
setreg 0360000b 00
setreg 0360000e 50
setreg 0360000f f0
setreg 03600010 09
setreg 03600011 9f
setreg 03600012 80
setreg 03600013 00
setreg 03600016 50
setreg 03600017 f0
setreg 03600018 09
setreg 03600019 9f
setreg 0360001a 80
setreg 0360001b 00
setreg 0360001e 50
setreg 0360001f f0
setreg 03600020 09
setreg 03600021 9f
setreg 03600022 80
setreg 03600023 00
setreg 03600026 50
setreg 03600027 f0
setreg 03600028 09
setreg 03600029 9f
setreg 0360002a 80
setreg 0360002b 00
setreg 0360002e 50
setreg 0360002f f0
setreg 03600030 09
setreg 03600031 9f
setreg 03600032 80
setreg 03600033 00
setreg 03600036 50
setreg 03600037 f0
setreg 03600038 09
setreg 03600039 9f
setreg 0360003a 80
setreg 0360003b 00
setreg 0360003e 50
setreg 0360003f f0
setreg 04600040 00
setreg 04600042 d8
setreg 04600043 88
setreg 04700000 0a
setreg 04700001 14
setreg 04700002 00
setreg 04700003 00
setreg 04600000 09
setreg 04600001 9f
setreg 04600002 80
setreg 04600003 00
setreg 04600006 60
setreg 04600007 f0
setreg 04600008 09
setreg 04600009 9f
setreg 0460000a 80
setreg 0460000b 00
setreg 0460000e 60
setreg 0460000f f0
setreg 04600010 09
setreg 04600011 9f
setreg 04600012 80
setreg 04600013 00
setreg 04600016 60
setreg 04600017 f0
setreg 04600018 09
setreg 04600019 9f
setreg 0460001a 80
setreg 0460001b 00
setreg 0460001e 60
setreg 0460001f f0
setreg 04600020 09
setreg 04600021 9f
setreg 04600022 80
setreg 04600023 00
setreg 04600026 60
setreg 04600027 f0
setreg 04600028 09
setreg 04600029 9f
setreg 0460002a 80
setreg 0460002b 00
setreg 0460002e 60
setreg 0460002f f0
setreg 04600030 09
setreg 04600031 9f
setreg 04600032 80
setreg 04600033 00
setreg 04600036 60
setreg 04600037 f0
setreg 04600038 09
setreg 04600039 9f
setreg 0460003a 80
setreg 0460003b 00
setreg 0460003e 60
setreg 0460003f f0
In order to define all the macro-blocks described in Configuration File basic structure, this
section reports how to configure each specific register within a macro-block.
a. 0x58 Differential Clock recovery (requires RTP protocol, see Per port Tributaries
enable command)
b. 0x5A Node timing
The following six registers contain the destination MAC address split by byte for each
tributary IWF and must be equal to the NE public MAC address. NE MAC address is can
be found inside CT/NMS inside "Configuration -> System Settings" menu.
Whenever the radio interface involved in the cross-connection is protected, the NE public
MAC address must be inserted in the multicast version. Multicast version corresponds to
the NE public MAC shown at CT/NMS having bit 40 fixed at 1.
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.
setreg yx10000C 01
setreg yx5000z0 01
Here below are reported in table format the supported configurations (ETSI market context
only) for SFP 2xE1/DS1 when the interworking is done with a 32 E1 PDH card (Figure 4.6)
or with an equivalent SFP module (Figure 4.7).
Figure 4.6 — Compatibility table between 32E1 PDH card and 2xE1/DS1 SFP Module
setreg 03300020 0c
setreg 03300003 29
setreg 03300005 00
setreg 03300002 09
setreg 03300025 00
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 03200000 34
setreg 0340000A 80
setreg 0310000c 01
setreg 04300020 0c
setreg 04300003 29
setreg 04300005 00
setreg 04300002 09
setreg 04300025 00
setreg 04200000 34
setreg 04400002 80
setreg 0410000C 01
setreg 04300005 00
setreg 04300002 09
setreg 04300025 00
setreg 04200000 34
setreg 0440000A 80
setreg 0410000c 01
setreg yx300020 1c
setreg yx300003 29
setreg yx300005 02
setreg yx300002 12
setreg yx300025 00
Example for Core Main, Optical Port 5, DS1 (ANSI) traffic selection:
setreg 0310000A 01
setreg 03700002 01
z = 0 Tributary 1 z = 8 Tributary 2
setreg 03300000 80
Please notice that in <HEX value1> must be also configured the RTP Header presence
that's mandatory for DCR, which turns to be mandatory for TDM2TDM.
setreg yx50001e B8
setreg yx50001f 40
setreg yx700080 32
setreg yx700081 C5
setreg yx700082 05
setreg yx700084 E7
setreg yx700085 C4
setreg yx700086 05
setreg yx700088 0D
setreg yx70008A 05
setreg yx70008C AC
setreg yx70008D 05
setreg yx50001d ea
setreg yx50001e f4
setreg yx50001f 40
setreg yx700080 65
setreg yx700081 A7
setreg yx700082 07
setreg yx700084 00
setreg yx700085 A7
setreg yx700086 07
setreg yx700088 32
setreg yx70008A 07
setreg yx70008C 90
setreg yx70008D 07
4.6.7 — Example
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
setreg 03300020 0c
setreg 03300003 29
setreg 03300005 00
setreg 03300002 09
setreg 03300025 00
setreg 03200000 34
setreg 03500004 FE
setreg 03500000 01
setreg 03500005 03
setreg 03500006 07
setreg 03500007 00
setreg 03500008 04
setreg 03500009 14
setreg 0350000a 00
setreg 0350000b 00
setreg 03500010 0c
setreg 03500011 00
setreg 03500018 00
setreg 0350001c 58
setreg 0350001d a2
setreg 0350001e 86
setreg 0350001f 41
setreg 03500001 00
setreg 03500002 00
setreg 03500003 00
setreg 03700080 50
setreg 03700081 35
setreg 03700082 0c
setreg 03700083 00
setreg 03700084 b0
setreg 03700085 34
setreg 03700086 0c
setreg 03700087 00
setreg 03700088 00
setreg 03700089 35
setreg 0370008a 0c
setreg 0370008b 00
setreg 0370008c 00
setreg 0370008d 0c
setreg 0370008e 00
setreg 0370008f 00
setreg 03700090 03
setreg 03700091 00
setreg 03700092 02
setreg 03700093 00
setreg 03700094 04
setreg 03700095 01
setreg 03700096 07
setreg 03700097 f0
setreg 03600040 00
setreg 03600042 d8
setreg 03600043 88
setreg 03700000 0a
setreg 03700001 14
setreg 03700002 00
setreg 03700003 00
setreg 03600000 09
setreg 03600001 9f
setreg 03600002 80
setreg 03600003 00
setreg 03600006 50
setreg 03600007 f0
setreg 03600008 09
setreg 03600009 9f
setreg 0360000a 80
setreg 0360000b 00
setreg 0360000e 50
setreg 0360000f f0
setreg 03600010 09
setreg 03600011 9f
setreg 03600012 80
setreg 03600013 00
setreg 03600016 50
setreg 03600017 f0
setreg 03600018 09
setreg 03600019 9f
setreg 0360001a 80
setreg 0360001b 00
setreg 0360001e 50
setreg 0360001f f0
setreg 03600020 09
setreg 03600021 9f
setreg 03600022 80
setreg 03600023 00
setreg 03600026 50
setreg 03600027 f0
setreg 03600028 09
setreg 03600029 9f
setreg 0360002a 80
setreg 0360002b 00
setreg 0360002e 50
setreg 0360002f f0
setreg 03600030 09
setreg 03600031 9f
setreg 03600032 80
setreg 03600033 00
setreg 03600036 50
setreg 03600037 f0
setreg 03600038 09
setreg 03600039 9f
setreg 0360003a 80
setreg 0360003b 00
setreg 0360003e 50
setreg 0360003f f0
setreg 03200000 6C
setreg 03500012 07
setreg 03500013 00
setreg 0350000c 00
setreg 0350000d 00
setreg 0350000e 00
setreg 0350000f 01
setreg 03500014 0a
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
#Remove THz
setreg 0310000C 01
#ENABLE CHAN 1
setreg 03500004 FF
setreg 03500000 01
This example illustrates a configuration file for CORE Main Spare to configure 2 tributaries
on SFP port 6, with TDM2TDM profile.
setreg 04300020 0c
setreg 04300003 29
setreg 04300005 00
setreg 04300002 09
setreg 04300025 00
setreg 04200000 34
#Common Configuration
setreg 04600040 00
setreg 04600042 d8
setreg 04600043 88
setreg 04700000 0a
setreg 04700001 14
setreg 04700002 00
setreg 04700003 00
setreg 04600000 09
setreg 04600001 9f
setreg 04600002 80
setreg 04600003 00
setreg 04600006 60
setreg 04600007 f0
setreg 04600008 09
setreg 04600009 9f
setreg 0460000a 80
setreg 0460000b 00
setreg 0460000e 60
setreg 0460000f f0
setreg 04600010 09
setreg 04600011 9f
setreg 04600012 80
setreg 04600013 00
setreg 04600016 60
setreg 04600017 f0
setreg 04600018 09
setreg 04600019 9f
setreg 0460001a 80
setreg 0460001b 00
setreg 0460001e 60
setreg 0460001f f0
setreg 04600020 09
setreg 04600021 9f
setreg 04600022 80
setreg 04600023 00
setreg 04600026 60
setreg 04600027 f0
setreg 04600028 09
setreg 04600029 9f
setreg 0460002a 80
setreg 0460002b 00
setreg 0460002e 60
setreg 0460002f f0
setreg 04600030 09
setreg 04600031 9f
setreg 04600032 80
setreg 04600033 00
setreg 04600036 60
setreg 04600037 f0
setreg 04600038 09
setreg 04600039 9f
setreg 0460003a 80
setreg 0460003b 00
setreg 0460003e 60
setreg 0460003f f0
setreg 04200000 2C
#########################################################
# CHANNEL 1 #
#########################################################
setreg 04500004 E2
setreg 04500005 01
setreg 04500006 07
setreg 04500007 00
setreg 04500008 04
setreg 04500009 14
setreg 0450000a 00
setreg 0450000b 00
setreg 0450000c 09
setreg 0450000d 9f
setreg 0450000e 80
setreg 0450000f 00
setreg 04500010 0c
setreg 04500011 00
setreg 04500012 03
setreg 04500013 f3
setreg 04500014 0a
setreg 04500015 a0
setreg 04500016 00
setreg 04500017 00
setreg 04500018 00
setreg 04500019 a0
setreg 0450001a 00
setreg 0450001b 00
#Differential/Adaptive/Node timing
setreg 0450001c 58
setreg 0450001d a2
setreg 0450001e B8
setreg 0450001f 40
setreg 04500000 01
setreg 04500001 00
setreg 04500002 00
setreg 04500003 00
setreg 04700080 32
setreg 04700081 C5
setreg 04700082 05
setreg 04700083 00
setreg 04700084 E7
setreg 04700085 C4
setreg 04700086 05
setreg 04700087 00
setreg 04700088 0D
setreg 04700089 35
setreg 0470008a 05
setreg 0470008b 00
setreg 0470008c AC
setreg 0470008d 05
setreg 0470008e 00
setreg 0470008f 00
setreg 04700090 03
setreg 04700091 00
setreg 04700092 02
setreg 04700093 00
setreg 04700094 04
setreg 04700095 01
setreg 04700096 07
setreg 04700097 f0
setreg 04500012 F3
setreg 04500013 0A
setreg 0450000c 00
setreg 0450000d AE
setreg 0450000e 21
setreg 0450000f 00
setreg 04500014 48
setreg 04500015 83
#ECID Tx
setreg 04500016 34
#ECID Tx
setreg 04500017 00
#ECID Rx (7:4)
setreg 04500019 80
#ECID Rx
setreg 0450001a 34
#ECID Rx
setreg 0450001b 00
#Remove THz
setreg 0410000C 01
#ENABLE CHAN 1
setreg 04500004 E3
setreg 04500000 01
##########################################################
CHANNEL 2 #
#########################################################
setreg 04500044 E2
setreg 04500045 01
setreg 04500046 07
setreg 04500047 00
setreg 04500048 04
setreg 04500049 14
setreg 0450004a 00
setreg 0450004b 00
setreg 0450004c 09
setreg 0450004d 9f
setreg 0450004e 80
setreg 0450004f 00
setreg 04500050 0c
setreg 04500051 00
setreg 04500052 03
setreg 04500053 f3
setreg 04500054 0b
setreg 04500055 c0
setreg 04500056 00
setreg 04500057 00
setreg 04500058 00
setreg 04500059 d0
setreg 0450005a 00
setreg 0450005b 00
#Differential/Adaptive/Node timing
setreg 0450005c 58
setreg 0450005d a2
setreg 0450005e B8
setreg 0450005f 40
setreg 04500040 01
setreg 04500041 00
setreg 04500042 00
setreg 04500043 00
setreg 047000c0 32
setreg 047000c1 C5
setreg 047000c2 05
setreg 047000c3 00
setreg 047000c4 E7
setreg 047000c5 C4
setreg 047000c6 05
setreg 047000c7 00
setreg 047000c8 0D
setreg 047000c9 35
setreg 047000ca 05
setreg 047000cb 00
setreg 047000cc AC
setreg 047000cd 05
setreg 047000ce 00
setreg 047000cf 00
setreg 047000d0 03
setreg 047000d1 00
setreg 047000d2 02
setreg 047000d3 00
setreg 047000d4 04
setreg 047000d5 01
setreg 047000d6 07
setreg 047000d7 f0
setreg 04500052 F3
setreg 04500053 0A
setreg 0450004c 00
setreg 0450004d AE
setreg 0450004e 21
setreg 0450004f 00
setreg 04500054 9a
setreg 04500055 a1
#ECID Tx
setreg 04500056 19
#ECID Tx
setreg 04500057 00
#ECID Rx (7:4)
setreg 04500059 a0
#ECID Rx
setreg 0450005a 19
#ECID Rx
setreg 0450005b 00
#Remove THz
setreg 0410000C 01
#ENABLE CHAN 2
setreg 04500044 E3
setreg 04500040 01
This example illustrates a configuration file for CORE Main to configure on SFP port 5
two tributaries with TDM2TDM profile:
The DS1 are cross-connected between the SFP module and a radio direction.The selected
clock recovery is differential and CES frames carry RTP protocol.
#LIU CONFIG
setreg 03300020 1c
setreg 03300003 29
setreg 03300005 02
setreg 03300002 12
setreg 03300025 00
setreg 0310000A 01
# TRIBUTARY 1 CONFIGURATION
setreg 03500004 ff
setreg 03500005 02
setreg 03500006 07
setreg 03500007 00
setreg 03500008 04
setreg 03500009 14
setreg 0350000a 00
setreg 0350000b 00
setreg 0350000c 08
setreg 0350000d 60
setreg 0350000e 20
setreg 0350000f 00
setreg 03500010 0d
setreg 03500011 00
setreg 03500012 01
setreg 03500013 03
setreg 03500014 0a
setreg 03500015 a0
setreg 03500016 00
setreg 03500017 00
setreg 03500018 00
setreg 03500019 a0
setreg 0350001a 00
setreg 0350001b 00
setreg 0350001c 58
#TDM2ETH configuration
setreg 0350001d 9a
setreg 0350001e 84
setreg 0350001f 41
setreg 03500001 00
setreg 03500002 00
setreg 03500003 00
setreg 03700080 1e
setreg 03700081 25
setreg 03700082 0c
setreg 03700083 00
setreg 03700084 7f
setreg 03700085 24
setreg 03700086 0c
setreg 03700087 00
setreg 03700088 cf
setreg 03700089 24
setreg 0370008a 0c
setreg 0370008b 00
setreg 0370008c 00
setreg 0370008d 0c
setreg 0370008e 00
setreg 0370008f 00
setreg 03700090 03
setreg 03700091 00
setreg 03700092 02
setreg 03700093 00
setreg 03700094 04
setreg 03700095 01
setreg 03700096 07
setreg 03700097 f0
setreg 03600000 09
setreg 03600001 9f
setreg 03600002 80
setreg 03600003 00
setreg 03600004 00
setreg 03600005 00
setreg 03600006 60
setreg 03600007 f0
setreg 03600008 09
setreg 03600009 9f
setreg 0360000a 80
setreg 0360000b 00
setreg 0360000c 00
setreg 0360000d 00
setreg 0360000e 06
setreg 0360000f f6
setreg 03600010 09
setreg 03600011 9f
setreg 03600012 80
setreg 03600013 00
setreg 03600014 00
setreg 03600015 00
setreg 03600016 60
setreg 03600017 f0
setreg 03600018 09
setreg 03600019 9f
setreg 0360001a 80
setreg 0360001b 00
setreg 0360001c 00
setreg 0360001d 00
setreg 0360001e 60
setreg 0360001f f0
setreg 03600020 09
setreg 03600021 9f
setreg 03600022 80
setreg 03600023 00
setreg 03600024 00
setreg 03600025 00
setreg 03600026 60
setreg 03600027 f0
setreg 03600028 09
setreg 03600029 9f
setreg 0360002a 80
setreg 0360002b 00
setreg 0360002c 00
setreg 0360002d 00
setreg 0360002e 60
setreg 0360002f f0
setreg 03600030 09
setreg 03600031 9f
setreg 03600032 80
setreg 03600033 00
setreg 03600034 00
setreg 03600035 00
setreg 03600036 60
setreg 03600037 f0
setreg 03600038 09
setreg 03600039 9f
setreg 0360003a 80
setreg 0360003b 00
setreg 0360003c 00
setreg 0360003d 00
setreg 0360003e 60
setreg 0360003f f0
setreg 03600040 00
setreg 03600041 00
# MEF8 Ethertype
setreg 03600042 d8
setreg 03600043 88
setreg 03700000 0a
setreg 03700001 14
setreg 03700002 01
setreg 03700003 00
setreg 03200000 2C
setreg 0310000C 01
setreg 03500000 01
# TRIBUTARY 2 CONFIGURATION
setreg 03500004 ff
setreg 03500005 02
setreg 03500006 07
setreg 03500007 00
setreg 03500008 04
setreg 03500009 14
setreg 0350000a 00
setreg 0350000b 00
setreg 0350000c 09
setreg 0350000d 9f
setreg 0350000e 80
setreg 0350000f 00
setreg 03500010 0d
setreg 03500011 00
setreg 03500012 03
setreg 03500013 f3
setreg 03500014 0a
setreg 03500015 a0
setreg 03500016 00
setreg 03500017 00
setreg 03500018 00
setreg 03500019 a0
setreg 0350001a 00
setreg 0350001b 00
setreg 0350001c 58
setreg 0350001d 9a
setreg 0350001e 84
setreg 0350001f 41
setreg 03500001 00
setreg 03500002 00
setreg 03500003 00
setreg 03700080 1e
setreg 03700081 25
setreg 03700082 0c
setreg 03700083 00
setreg 03700084 7f
setreg 03700085 24
setreg 03700086 0c
setreg 03700087 00
setreg 03700088 cf
setreg 03700089 24
setreg 0370008a 0c
setreg 0370008b 00
setreg 0370008c 00
setreg 0370008d 0c
setreg 0370008e 00
setreg 0370008f 00
setreg 03700090 03
setreg 03700091 00
setreg 03700092 02
setreg 03700093 00
setreg 03700094 04
setreg 03700095 01
setreg 03700096 07
setreg 03700097 f0
setreg 03600000 09
setreg 03600001 9f
setreg 03600002 80
setreg 03600003 00
setreg 03600004 00
setreg 03600005 00
setreg 03600006 60
setreg 03600007 f0
setreg 03600008 09
setreg 03600009 9f
setreg 0360000a 80
setreg 0360000b 00
setreg 0360000c 00
setreg 0360000d 00
setreg 0360000e 03
setreg 0360000f f3
setreg 03600010 09
setreg 03600011 9f
setreg 03600012 80
setreg 03600013 00
setreg 03600014 00
setreg 03600015 00
setreg 03600016 60
setreg 03600017 f0
setreg 03600018 09
setreg 03600019 9f
setreg 0360001a 80
setreg 0360001b 00
setreg 0360001c 00
setreg 0360001d 00
setreg 0360001e 60
setreg 0360001f f0
setreg 03600020 09
setreg 03600021 9f
setreg 03600022 80
setreg 03600023 00
setreg 03600024 00
setreg 03600025 00
setreg 03600026 60
setreg 03600027 f0
setreg 03600028 09
setreg 03600029 9f
setreg 0360002a 80
setreg 0360002b 00
setreg 0360002c 00
setreg 0360002d 00
setreg 0360002e 60
setreg 0360002f f0
setreg 03600030 09
setreg 03600031 9f
setreg 03600032 80
setreg 03600033 00
setreg 03600034 00
setreg 03600035 00
setreg 03600036 60
setreg 03600037 f0
setreg 03600038 09
setreg 03600039 9f
setreg 0360003a 80
setreg 0360003b 00
setreg 0360003c 00
setreg 0360003d 00
setreg 0360003e 60
setreg 0360003f f0
setreg 03600040 00
setreg 03600041 00
setreg 03600042 d8
setreg 03600043 88
setreg 03700000 0a
setreg 03700001 14
setreg 03700002 01
setreg 03700003 00
setreg 03500000 01
This example illustrates a configuration file for CORE Main to configure on SFP port 5
two tributaries with TDM2TDM profile:
The DS1 are cross-connected between the SFP module and a radio direction. According to
TDM2TDM profile, the selected clock recovery is differential and CES frames carry RTP
protocol.
#LIU CONFIG
setreg 03300020 1c
setreg 03300003 29
setreg 03300005 02
setreg 03300002 12
setreg 03300025 00
setreg 0310000A 01
# TRIBUTARY 1 CONFIGURATION
setreg 03500004 e3
setreg 03500005 01
setreg 03500006 07
setreg 03500007 00
setreg 03500008 04
setreg 03500009 14
setreg 0350000a 00
setreg 0350000b 00
setreg 0350000c 09
setreg 0350000d 9f
setreg 0350000e 80
setreg 0350000f 00
setreg 03500010 0d
setreg 03500011 00
setreg 03500012 03
setreg 03500013 f3
setreg 03500014 0a
setreg 03500015 a0
setreg 03500016 00
setreg 03500017 00
setreg 03500018 00
setreg 03500019 a0
setreg 0350001a 00
setreg 0350001b 00
setreg 0350001c 58
setreg 0350001d ea
setreg 0350001e f4
setreg 0350001f 40
setreg 03500001 00
setreg 03500002 00
setreg 03500003 00
setreg 03700080 65
setreg 03700081 a7
setreg 03700082 07
setreg 03700083 00
setreg 03700084 00
setreg 03700085 a7
setreg 03700086 07
setreg 03700087 00
setreg 03700088 32
setreg 03700089 a7
setreg 0370008a 07
setreg 0370008b 00
setreg 0370008c 90
setreg 0370008d 07
setreg 0370008e 00
setreg 0370008f 00
setreg 03700090 03
setreg 03700091 00
setreg 03700092 03
setreg 03700093 00
setreg 03700094 04
setreg 03700095 01
setreg 03700096 07
setreg 03700097 f0
setreg 03600000 09
setreg 03600001 9f
setreg 03600002 80
setreg 03600003 00
setreg 03600004 00
setreg 03600005 00
setreg 03600006 60
setreg 03600007 f0
setreg 03600008 09
setreg 03600009 9f
setreg 0360000a 80
setreg 0360000b 00
setreg 0360000c 00
setreg 0360000d 00
setreg 0360000e 03
setreg 0360000f f3
setreg 03600010 09
setreg 03600011 9f
setreg 03600012 80
setreg 03600013 00
setreg 03600014 00
setreg 03600015 00
setreg 03600016 60
setreg 03600017 f0
setreg 03600018 09
setreg 03600019 9f
setreg 0360001a 80
setreg 0360001b 00
setreg 0360001c 00
setreg 0360001d 00
setreg 0360001e 60
setreg 0360001f f0
setreg 03600020 09
setreg 03600021 9f
setreg 03600022 80
setreg 03600023 00
setreg 03600024 00
setreg 03600025 00
setreg 03600026 60
setreg 03600027 f0
setreg 03600028 09
setreg 03600029 9f
setreg 0360002a 80
setreg 0360002b 00
setreg 0360002c 00
setreg 0360002d 00
setreg 0360002e 60
setreg 0360002f f0
setreg 03600030 09
setreg 03600031 9f
setreg 03600032 80
setreg 03600033 00
setreg 03600034 00
setreg 03600035 00
setreg 03600036 60
setreg 03600037 f0
setreg 03600038 09
setreg 03600039 9f
setreg 0360003a 80
setreg 0360003b 00
setreg 0360003c 00
setreg 0360003d 00
setreg 0360003e 60
setreg 0360003f f0
setreg 03600040 00
setreg 03600041 00
setreg 03600042 d8
setreg 03600043 88
setreg 03700000 0a
setreg 03700001 14
setreg 03700002 01
setreg 03700003 00
setreg 03500000 01
# TRIBUTARY 2 CONFIGURATION
setreg 03500044 e3
setreg 03500045 01
setreg 03500046 07
setreg 03500047 00
setreg 03500048 04
setreg 03500049 14
setreg 0350004a 00
setreg 0350004b 00
setreg 0350004c 09
setreg 0350004d 9f
setreg 0350004e 80
setreg 0350004f 00
setreg 03500050 0d
setreg 03500051 00
setreg 03500052 03
setreg 03500053 f3
setreg 03500054 0b
setreg 03500055 b0
setreg 03500056 00
setreg 03500057 00
setreg 03500058 00
setreg 03500059 b0
setreg 0350005a 00
setreg 0350005b 00
setreg 0350005c 58
setreg 0350005d ea
setreg 0350005e f4
setreg 0350005f 40
setreg 03500041 00
setreg 03500042 00
setreg 03500043 00
setreg 037000c0 65
setreg 037000c1 a7
setreg 037000c2 07
setreg 037000c3 00
setreg 037000c4 00
setreg 037000c5 a7
setreg 037000c6 07
setreg 037000c7 00
setreg 037000c8 32
setreg 037000c9 a7
setreg 037000ca 07
setreg 037000cb 00
setreg 037000cc 90
setreg 037000cd 07
setreg 037000ce 00
setreg 037000cf 00
setreg 037000d0 03
setreg 037000d1 00
setreg 037000d2 03
setreg 037000d3 00
setreg 037000d4 04
setreg 037000d5 01
setreg 037000d6 07
setreg 037000d7 f0
setreg 03600000 09
setreg 03600001 9f
setreg 03600002 80
setreg 03600003 00
setreg 03600004 00
setreg 03600005 00
setreg 03600006 60
setreg 03600007 f0
setreg 03600008 09
setreg 03600009 9f
setreg 0360000a 80
setreg 0360000b 00
setreg 0360000c 00
setreg 0360000d 00
setreg 0360000e 03
setreg 0360000f f3
setreg 03600010 09
setreg 03600011 9f
setreg 03600012 80
setreg 03600013 00
setreg 03600014 00
setreg 03600015 00
setreg 03600016 60
setreg 03600017 f0
setreg 03600018 09
setreg 03600019 9f
setreg 0360001a 80
setreg 0360001b 00
setreg 0360001c 00
setreg 0360001d 00
setreg 0360001e 60
setreg 0360001f f0
setreg 03600020 09
setreg 03600021 9f
setreg 03600022 80
setreg 03600023 00
setreg 03600024 00
setreg 03600025 00
setreg 03600026 60
setreg 03600027 f0
setreg 03600028 09
setreg 03600029 9f
setreg 0360002a 80
setreg 0360002b 00
setreg 0360002c 00
setreg 0360002d 00
setreg 0360002e 60
setreg 0360002f f0
setreg 03600030 09
setreg 03600031 9f
setreg 03600032 80
setreg 03600033 00
setreg 03600034 00
setreg 03600035 00
setreg 03600036 60
setreg 03600037 f0
setreg 03600038 09
setreg 03600039 9f
setreg 0360003a 80
setreg 0360003b 00
setreg 0360003c 00
setreg 0360003d 00
setreg 0360003e 60
setreg 0360003f f0
setreg 03600040 00
setreg 03600041 00
setreg 03600042 d8
setreg 03600043 88
setreg 03700000 0a
setreg 03700001 14
setreg 03700002 01
setreg 03700003 00
setreg 03500040 01
4.7.1 — Description
Alarm Severity Assignment Profile feature allows the operator to realize a custom re-
mapping of "NonServiceAffecting" (NSA) severity and "ServiceAffecting" (SA) severity
of each alarm supported into the system.
Note: the configuration file used to apply this feature is to be managed by FTM tool (see
Appendix section File Transfer Manager tool), see Configuration File upload and execution
for this specific file upload to Flash Card.
However as described in mentioned SR ID, automatic migration will not cover the case of
change for the new SW release of default severity for some of the alarms already present in
the ASAP Configuration File in SW release used to deploy it. For this specific case, ASAP
Configuration File must be updated manually.
Each command insert inside "def_asap4.psh" configuration file must respect the following
structure:
<Alarm ID>: identifier corresponding to specific alarm whose severity the user wants to
change; see Alarm IDs;
<SA severity>: severity in case of service affecting alarm; see Table 4.9;
<NSA severity>: severity in case of non service affecting alarm; see Table 4.9;
NO_ALARM 0
MINOR 1
MAJOR 2
CRITICAL 3
WARNING 4
For each alarm, the operator is required to insert both SA and NSA severities.
4.7.5 — Example
# <Alarm ID> <SA severity> <NSA severity>
2 2 1 # Cable LOS
3 2 1 # RX Fail
5 2 1 # Demodulator Fail
12 4 4 # Early Warning
25 2 1 # Incompatible Frequency
26 2 1 # Incompatible Tx Power
29 2 1 # AIS
30 1 4 # Degrade
32 2 1 # Loss Of Frame
34 2 1 # Loss Of Signal
37 1 4 # High BER
39 2 1 # Unavailable Time
51 1 1 # Battery Failure
54 1 1 # Version Mismatch
59 2 1 # Loss Of Protection
77 1 1 # Housekeeping Alarm
78 2 1 # Threshold Crossed
80 1 4 # PPP Fail
82 1 1 # Loss Of Alignment
90 2 1 # Incompatible Shifter
91 1 1 # Provisioning Mismatch
120 2 1 # CLA
When limit is reached, new frames with new source MAC address are discarded.
This feature can be also applied to EAS User Ports and EASv2 User Ports.
In case of EAS or EASv2, the <slot-1> number must be added to the above commands.
#Consequent action to be applied on port ge17 when limit is exceeded: here it is drop
In case of EAS or EASv2, the <slot-1>: number must be added to the above commands.
4.9.1 — Overview
This enhanced configuration allows for IPv4 frames having 802.1q or QinQ VLAN tag:
• for IPv4 frames ingressing MPR, to assign the 802.1p bits based on the value of
DiffServ field
• for IPv4 frames egressing MPR, to assign the DiffServ field based on the value of the
802.1p bits field
Generally both two configurations above should be usually applied, but there can be cases
where only one of them is needed.
• <ID>: rule ID number; range[512:583]; the chosen value should not be shared among
different rules; mandatory.
• <ingPbm>: user Ethernet port bitmap where IP Packets will ingress MPR network;
see User Ethernet port bitmap where ATM PW frames ingress the network;
mandatory.
• <DSCP> DSCP hex value; mandatory.
• <Dot1p>: 802.1p bits decimal value [0-7]; mandatory.
• <Dot1pVLANTag> - VLANTag hex mask value for given 802.1p value, e.g. 0xe000
identifies 802.1p value = 7 ; mandatory
In case of EAS or EASv2, the <slot-1> number must be added to above commands, while
the same <ID> range applies
4.9.4 — Example
#DSCP bits - 802.1p bits
4.10.1 — Overview
This enhanced configuration allows to change the MAC Aging time, i.e. the time needed to
clear a dynamic entry in the Address Table of Ethernet Switch.
This feature can be also applied to MPT Access, EAS and EASv2 Switch.
In case of MPT Access/EAS/EASv2, the <slot-1> number must be added to the above
command.
4.10.3 — Example
# set Core Switch Aging time to 1 second
bcm age 1
4.11.1 — Overview
This enhanced configuration allows to perform QoS based on MPLS TC (Traffic Class)
field (a.k.a. EXP Bits) mapping the MPLS TC field (3 bits) into VLAN Tag PCP field
(3bits) and mapping MPLS TC to Ethernet switch queues.
The enhanced configuration is useful when MPLS traffic is not carried by VLAN tagged
Ethernet frames and it is not possible to apply QoS based on VLAN Tag priority.
In order to perform QoS based on MPLS TC it is needed to add a VLAN Tag to the MPLS
traffic traversing the radio link made by MPR equipments.
This is achieved configuring by CT or NMS at least one VLAN to carry MPLS traffic over
radio link and to put in the member set of this VLAN the interfaces, both User Ethernet and
radio, where MPLS traffic is flowing. User Ethernet interfaces must be also put in the
untagged set of the VLAN and the VLAN ID must be set as Port VLAN ID of the User
Ethernet interfaces.
This configuration allows to accept untagged Ethernet traffic carrying MPLS and deliver
untagged Ethernet traffic as well out of MPR radio link.
The enhanced configuration can be applied to the Core and EASv2 Switch, according
where the User Ethernet interfaces delivering MPLS traffic are placed.
This enhanced configuration may overlap for FP Group #4 and rule IDs used with the
features described in VLAN SWAP AND DOT1P REMARKING FOR ATM PW
SERVICE and DOT1P ASSIGNMENT BASED ON INCOMING DIFFSERV. It is up to
the user to ensure consistency in case these features are being applied at the same time (i.e.
avoiding creating Group #4 twice and using same IDs).
# preliminary configuration
#preliminary Configuration
In order to apply the mapping of MPLS TC to Ethernet switch queues, the User Ethernet
interface (or interfaces) where MPLS traffic ingress the MPR equipment must be removed
from the existing mapping of VLAN Tag priority to Ethernet switch queues.
• <ingPbm>: User Ethernet interfaces bitmap removing the interface where MPLS
traffic ingresses MPR equipment from existing mapping; see Table 4.11; mandatory.
ingPbm ingPbm
ge20 0x1fffff — —
ingPbm ingPbm
ge17 0x3bffff — —
ge18 0x37ffff — —
Legend:
• <portNum>: User Ethernet port number where MPLS traffic ingresses MPR
equipment. In case of more than one port, an entry of the command must be used for
each port. Core Switch range: 6,7,18,19,20,21. See Switch to equipment ports
assignment for association with port name; mandatory.
• <ID>: unique rule ID number; range[512:519]; the chosen value should not be shared
among different rules; mandatory;
• <ingPbm>: User Ethernet ports bitmap where MPLS traffic ingresses MPR
equipment, see Table 4.13, must be the same ports defined by <portNum>;
mandatory;
• <n>: 0-2-4-6-8-a-c-e values related to 0-1-2-3-4-5-6-7 values of TC field; mandatory;
• <Dot1p>: 802.1p bits decimal value [0-7]; mandatory
ingPbm ingPbm
Legend:
• <portNum>: User Ethernet port number where MPLS traffic ingresses MPR
equipment. In case of more than one port, an entry of the command must be used for
each port. EASv2 Switch range: 6,7,8,9,10,11,18,19. See Switch to equipment ports
assignment for association with port name; mandatory;
• <ingPbm>: User Ethernet ports bitmap where MPLS traffic ingresses MPR
equipment, see Table 4.14, must be the same ports defined by <portNum>;
mandatory;
ingPbm ingPbm
ge17 0x40000 — —
ge18 0x80000 — —
Legend:
• <ID>: unique rule ID number; range[88:95]; the chosen value should not be shared
among different rules; mandatory;
• <ingPbm>: User Ethernet interfaces bitmap where MPLS traffic ingresses MPR
equipment; see Table 4.13; mandatory;
• <n>: 0-2-4-6-8-a-c-e values related to 0-1-2-3-4-5-6-7 values of TC field; mandatory;
• <queue>: Ethernet switch queue, decimal value [0-4]; mandatory
Legend:
• <ID>: unique rule ID number; range[640:647]; the chosen value should not be shared
among different rules; mandatory;
• <ingPbm>: User Ethernet interfaces bitmap where MPLS traffic ingresses MPR
equipment; please refer to Table 4; mandatory;
• <n>: 0-2-4-6-8-a-c-e values related to 0-1-2-3-4-5-6-7 values of TC field; mandatory;
• <queue>: Ethernet switch queue, decimal value [0-4]; mandatory.
4.11.6 — Example
#Remove EASv2 electrical User ports 1,2,3,and 4 from 802.1p to queues mapping
#Preliminary Configuration
# Enable 802.1p bits remarking on electrical User port 1 to User port 4 (ge5, ge6, ge7 and
ge8) of EASv2
• be text files
• have *.psh extension
• contain only commands executable on a shell interface, e.g. bcm, setreg
Files managed by CTNR tool are transferred only to and from the directory foreseen for
Configuration File (see section Configuration File path in NE File System)
Note: The tool is not meant for general distribution with MPR SW Package, but only for
use for dedicated customers under Alcatel-Lucent control.
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.
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
To perform Delta Configuration without NE Restart, the following steps must be followed:
The file on NE flash has been updated with executed commands, as it can seen by looking
at blue box in below picture:
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.
• apply Local Access Control Management (when Network Manager is supervising the
NE)
Files managed by FTM tool are transferred only to and from the directory foreseen for Flag
File and Configuration File (see Flag File path in NE File System and Configuration File
path in NE File System).
The main difference with the CF No Restart tool is the this one allows to append new
commands to existing Configuration Files. FTM instead just allows to move Configuration
Files from/to the NE.
Note: The tool is not meant for general distribution with MPR SW Package, but only for
use for dedicated customers under Alcatel-Lucent control.
The tool can be used if the following lines are present in the JUSM_config.properties file
Then, a new menu item appears under the menu Configuration called FTM Tool.
1. Add File
Copy the selected file from Local workspace area to NE Flash. If the file is already
existing on NE, the user is prompted for confirmation of overwrite
2. Copy to LocalPC
Copy the selected file on NE from NE Flash to Local workspace area. If the Local
workspace is not empty, the user is prompted for confirmation of overwrite
3. Remove
Delete the selected file on NE from NE Flash or from Local workspace area. The user
is prompted for confirmation of deletion
4. Edit
The text file in the Local workspace can be edited
5. New
A new blank text file can be created in the Local workspace
1. By clicking on Import Menu it's possible to import in the local workspace files
previously saved on PC FileSystem, USB key, CD....
2. By clicking on Export Menu it's possible to save on PC File System or other devices
the file presenton local repository.
See Migration Procedure for details about applicable migration procedure that allows to
avoid explicit setting from previous release in case the flag file was used.
This setting is needed not only on the NEs where ATMoMPLS is terminated by ASAP Card
(as it is the ASAP Card that add the MPLS Tunnel Label to all ATM PW frames) but on all
NE where ATM PW traffic is transported (e.g. to enable the specific header compression
on radio cards).
1. Connect to MPR NE WebServer by a Web Browser like Internet Explorer (NE must
be reachable at IP level)
2. Perform logon procedure supply username and password for a Security Profile that is
enable to modify NE settings, e.g. Administrator/Craftperson Profile
3. A page like the one shown in Figure 5.8 will be displayed.
4. Click on “MPLS Setting” link shown in the left part of the screen (below MPLS
item)
5. An HTML page like one in Figure 5.9 will be shown.
6. By supplying an input (in decimal format) in the MPLS Tunnel Label field, the
ATMoMPLS Protocol Stack is configured with the presence of MPLS Tunnel Label.
In case there are ASAP Cards in the NE, such value will be used as common value
for MPLS Tunnel Label by all ATM PWs terminated on that NE.
7. Assuming the MPLS Tunnel Label value = 1000 (decimal format) is given as input
in the MPLS Tunnel Label field and it is accepted by NE, the following HTML page
will be shown:
8. The same operation has to be performed to change the value of MPLS Tunnel Label.
That has effect only in case there are ASAP Cards in the NE, such new value will be
used as common value for MPLS Tunnel Label by all ATM PWs terminated on that
NE.
9. To disable instead the MPLS Tunnel Label presence from ATMoMPLS Protocol
Stack, a value of 0 must be provided in the MPLS Tunnel Label field.
ABBREVIATION MEANING
AM Adaptive Modulation
CD Current Data
CF Configuration File
CT Craft Terminal
DS Differentiated Services
EA Encryption Algorithm
EC Equipment Controller
ABBREVIATION MEANING
ETH Ethernet
FC Flash Card
FCS Frame Check Sequence
FD Frequency Diversity
FE Fast Ethernet
HS Hitless Switch
IP Internet Protocol
MC Main Core
ABBREVIATION MEANING
NP Network Processor
PM Performance Monitoring
PW Pseudo Wire
SC Spare Core
SD Space Diversity
SF Signal Fail
SP Strict Priority
TC Traffic Class
TS Time Slot
UNI User to Network Interface
ABBREVIATION MEANING
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.
Craft Terminal (CT): Workstation or Personal computer (PC) from which the local access
to an NE is possible. It can be used to configure or perform monitoring tasks on the NE.
EML Application: This application is responsible for the configuration and management of
NEs.
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.
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.
User Service Manager (USM): These are presentation processes used by PNM to manage
the user interface and facilitate the interaction with the product.
Customer documentation
http://www.alcatel-lucent.com/myaccess
Product manuals and documentation updates are available at alcatel-lucent.com. If you
are a new user and require access to this service, please contact your Alcatel-Lucent sales
representative.
Technical support
http://support.alcatel-lucent.com
Documentation feedback
documentation.feedback@alcatel-lucent.com
© 2014 Alcatel-Lucent. All rights reserved.
3DB 19901 BFAA Edition 01