288113969-01GB ADR2500eXtra

STM-16 ADD-DROP MULTIPLEXER
MULTIPLEXEUR ADD-DROP STM-16
ADR2500 eXtra
Installation and User Guide

Guide d'Installation et d'Utilisation
288 113 969-01
November 2006 Issue

Edition Novembre 2006
LIST OF CHANGES
REPERTOIRE DES MISES A JOUR
(A new edition replaces any previous versions)
(Une nouvelle dition annule et remplace la prcdente)
No/N
Date/Date
Change description/
Description de la mise jour
Page/Page
288 054 178-01
June 2004
Juin 2004
Creation of original user guide/

Cration du document l'dition originale
All pages/
Toutes pages
288 054 178-02
January 2005
Addition of SWITCH 32 VC4 HO/LO card

/ DCC Transparency / GFP150 eXtra
card
Ajout carte SWITCH 32 VC4 HO/LO /
Aboutement DCC / carte GFP150 eXtra
All pages/
Toutes pages
3E3DS3FA card / TCM function /

New data features on GFP /
New alarms on GIG-E and GFP
Carte 3E3DS3FA / Fonction TCM /
Nouvelles fonctions data sur GFP /
Nouvelles alarmes sur GIG-E et GFP
All pages/
Toutes pages
Addition of Pause mode (flow control)

New optical Booster
Ajout mode Pause (contrle de flux)
Nouvel Ampli optique
All page s/
Toutes pages
November 2006
New SDH alarms

Addition of VCG_RDI alarm
Addition of following cards :
- STM1-SFP
- STM4-SFP
- STM16-SFP
-xGE-DM
- 2GE-DM-SFP
- 63E1FA
All pages /
November 2006
Nouvelles alarmes SDH

Ajout alarme VCG_RDI
Ajout des cartes suivantes :
- STM1-SFP
- STM4-SFP
- STM16-SFP
- xGE-DM
- 2GE-DM-SFP
- 63E1FA
Toutes pages
Janvier 2005
288 054 178-03
June 2005
Juin 2005
288 054 178-04
January 2006
Janvier 2006
288 113 969-01
Installation and User Guide / Guide d'Installation et d'Utilisation 288 113 969-01
Sagem Communication document. Reproduction and disclosure prohibited
Document Sagem Communication Reproduction et divulgation interdites
Page 0-2
STM-16 ADD-DROP MULTIPLEXER
ADR2500 eXtra
Installation and User Guide
288 113 969-01
November 2006 Issue
Installation and User Guide- 288 113 969-01

Page A0-1
PORTS SECURITY LEVELS
ADR2500 eXtra shelf ports security levels

Front panel connectors
Function
Safety level
LTU3E3DS3 card
TR and REC
G703 34 or 45 Mbit/s traffic access
SELV
G703 120 2 Mbit/s traffic access
SELV
SELV
G703 34 or 45 Mbit/s traffic access
SELV
SELV
LTU21E120 card
E1 INPUT and
E1 OUTPUT
LTU21E75 card
E1 INPUT and
E1 OUTPUT
3E3DS3FA card
TR and REC
63E1FA card
E1 INPUT and
E1 OUTPUT
CCU-2G card
POWER/ALM
Access to station power supply and alarms
SELV
LOOPS
Access to signaling and dry loops
SELV
SYNC
Access to G.703 2 MHz synchronization
SELV
ETH
Access to remote management via Ethernet network
SELV
COMM
Access to local management via VT100 console or a

PC
SELV
CTRL-2G card
Optical interface cards

TR and REC
G.957 STM-n Optical access

(n=1, 4 or 16)
Class 1 laser
Harmless
G703 STM-1 Electrical access
SELV
Engineering Order Wire
SELV
4ERE card
TR and REC
AUX card
EOW and AUX
GIG-E card
TR et REC
Optical Gigabit Ethernet Access
RS232
Maintenance Access
Class 1 laser
Harmless
SELV
xGE-DM card
TR et REC
Optical Gigabit Ethernet Access
Class 1 laser
Harmless
GFP150 eXtra card

ETH
IEEE802.3 10/100 Base TX Ethernet / Fast Ethernet

Access
SELV

Page A0-2
The ADR2500 eXtra shelf must only be mounted in racks with lower part
closed or equipped with a class V1 or HF1 air filter (minimum) or resting
on a non-inflammable floor.
Safe grounding obligation

This equipment must only be installed by qualified personnel. The protective ground terminal
must be connected to a safe grounding system with resistance of Z < 5 ohms to fulfil technical
compliance.
Handling precaution
Use of an electrostatic bracelet is mandatory for all interventions inside the
equipment.
, marked on certain cards, puts in guard against burns which can
The logo
be caused by an important elevation of the temperature of the radiator.

Page A0-3
ENVIRONMENT
Preservation of the environment as part of a sustainable development logic is an essential concern of

Sagem Communication. The desire of Sagem Communication is to operate systems observing the
environment and consequently it has decided to integrate environmental performances in the life cycle
of its products, from manufacturing to commissioning, use and elimination.
PACKAGING
The presence of the logo (green dot) means that a contribution is paid to an approved
national organisation to improve packaging recovery and recycling infrastructures.
To facilitate recycling, please respect the sorting rules set up locally for this kind of waste.
BATTERIES
If your product contains batteries, they must be disposed of at appropriate collection points.
THE PRODUCT
The crossed-out waste bin stuck on the product (or on its accessories) means that the
product belongs to the family of electrical and electronic equipment.
In this respect, the European regulations ask you to dispose of it selectively :
At sales points in the event of the purchase of similar equipment.
At the collection points made available to you locally (drop-off centre, selective
collection, etc.).
In this way you can participate in the re-use and upgrading of Electrical and Electronic Equipment
Waste, which can have an effect on the environment and human health.

Page A0-4
TABLE OF CONTENTS
CHANGE LIST ..................................................................................................................................... 0-2
SECTION A - Installation and User Guide ........................A0-1 to AC-6

PORTS SECURITY LEVELS .............................................................................................................A0-2
ENVIRONMENT .................................................................................................................................A0-4
TABLE OF CONTENTS..................................................................................................... A0-5 to A0-11
INSTALLATION ............................................................................................................................ 1-1

1.1 - GENERAL INFORMATION .............................................................................................................. 1-1
1.2 - INSTALLATION OF THE SHELF........................................................................................................ 1-4
1.3 - CONNECTION OF ACCESS POINTS ............................................................................................... 1-11
1.3.1 - Connection to LTU21E1 or LTU21E75 cards .................................................................. 1-12
1.3.2 - Connection to LTU3E3DS3 card...................................................................................... 1-14
1.3.3 - Connection to CCU-2G card ............................................................................................ 1-14
1.3.3.1 - "POWER/ALM" connector ........................................................................................................ 1-15
1.3.3.2 - Remote signaling, remote control and station alarms access : LOOPS" ................................. 1-16
1.3.3.3 - 2 MHz G.703 sync access : "SYNC" ........................................................................................ 1-17
1.3.4 - Connection to CTRL-2G card .......................................................................................... 1-18

1.3.4.1 - Management access : "COMM" connector............................................................................... 1-18
1.3.4.2 - Management access : "ETH" connector ................................................................................... 1-19
1.3.5 - Connection to AUX cards................................................................................................. 1-21

1.3.6 - Connection to 3E3DS3FA card........................................................................................ 1-22
1.3.7 - Connection to 63E1FA card............................................................................................. 1-23
- Connection of optical STM-n access points.............................................................................. 1-23
1.3.9 - Connection of electrical STM-1 access points................................................................. 1-27
1.3.10 - Connection to GIG-E cards............................................................................................ 1-27
1.3.10.1 - Gigabit Ethernet access points ............................................................................................... 1-28
1.3.10.2 - Maintenance access : "RS232" connector.............................................................................. 1-28
1.3.11- Connection to xGE-DM cards ......................................................................................... 1-29

1.3.12 - Connection to GFP150 eXtra card................................................................................. 1-30
1.4 - SHELF WITHOUT PDH PROTECTION ............................................................................................. 1-31
2
COMMISSIONING AND OPERATION ......................................................................................... 2-1

2.1 - COMMISSIONING ......................................................................................................................... 2-1
2.1.1 - Required configuration....................................................................................................... 2-1
2.1.2 - Procedure........................................................................................................................... 2-3
2.1.3 - Description of communication function .............................................................................. 2-4
2.1.4 - Description of DCC transparency function......................................................................... 2-6
2.1.5 - Defining parameters for IP address and Ethernet port ...................................................... 2-7
2.1.6 - Using the Web browser.................................................................................................... 2-11
2.1.6.1 - Browser configuration............................................................................................................... 2-11
2.1.6.2 - Initial commissioning ................................................................................................................ 2-12
2.1.6.3 - Menus tree ............................................................................................................................... 2-12
2.1.6.4 - Presentation of the Graphical User Interface............................................................................ 2-14

Page A0-5
2.2 - OPERATION .............................................................................................................................. 2-17

2.2.1 - Functional description ...................................................................................................... 2-17
2.2.2 - General information ......................................................................................................... 2-17
2.2.3 - Operation parameters ...................................................................................................... 2-18
2.2.3.1 - Network Configuration Parameters........................................................................................... 2-19
2.2.3.2 - Equipment Configuration Parameters....................................................................................... 2-22
2.2.3.3 - Maintenance commands and operations.................................................................................. 2-42
2.2.3.4 - Alarm processing...................................................................................................................... 2-42
2.2.4 - Performance processing .................................................................................................. 2-55

2.2.5 - Optical Supervision .......................................................................................................... 2-56
2.2.6 - Synchronization................................................................................................................ 2-57
2.2.7 - Loops Management ......................................................................................................... 2-59
2.2.8 - MS-SPRing protection on LINE interfaces....................................................................... 2-61
2.2.8.1 - Introduction............................................................................................................................... 2-61
2.2.8.2 - Principle.................................................................................................................................... 2-61
2.2.8.3 - Configuration rules relative to 2-fibers MS-SPRing protection.................................................. 2-62
2.2.9 - TCM Function................................................................................................................... 2-66

2.2.9.1 - TCM Points at Equipment Level ............................................................................................... 2-66
2.2.9.2 - TCM VC4 Points Management by http ..................................................................................... 2-70
2.2.10 - Quality of service for VC4nv GigaEthernet .................................................................... 2-72

2.2.10.1 - Classification criteria............................................................................................................... 2-72
2.2.10.2 - Bandwidth management......................................................................................................... 2-75
2.2.10.3 - Congestion management in emission on the WAN ................................................................ 2-75
2.2.10.4 - Congestion management in reception WAN........................................................................... 2-77
2.3 - CARDS PROTECTION ................................................................................................................. 2-78

2.3.1 - PDH cards protection ....................................................................................................... 2-78
2.3.2 - SWITCH HO/LO card protection...................................................................................... 2-78
2.3.3 - PSU card protection ......................................................................................................... 2-79
2.4 - SUB-ASSEMBLY REPLACEMENT PROCEDURES ............................................................................. 2-79
2.4.1 - Replacement of an Interface card.................................................................................... 2-79
2.4.2 - Replacement of a SWITCH HO/LO card ......................................................................... 2-80
2.4.3 - Replacement of a PSU module........................................................................................ 2-80
2.4.4 - Replacement of a CTRL-2G card .................................................................................... 2-81
2.4.5 - Replacement of a CCU-2G card ...................................................................................... 2-82
2.4.6 - Replacement of FAN-2G module..................................................................................... 2-82
2.4.7 - Preventive maintenance .................................................................................................. 2-82
3
SPARE PARTS AND CABLES .................................................................................................... 3-1

3.1 3.2 3.3 -
LIST OF NO ROHS ADR2500 EXTRA ITEMS ................................................................................ 3-1

LIST OF ROHS ADR2500 EXTRA ITEMS ..................................................................................... 3-3
LIST OF AVAILABLE CABLES ....................................................................................................... 3-4
TECHNICAL CHARACTERISTICS .............................................................................................. 4-1
START-UP GUIDE........................................................................................................................ 5-1

5.1 - INSTALLING THE EQUIPMENT ........................................................................................................ 5-1
5.2 - CONNECTING TO AN ADR2500 EXTRA......................................................................................... 5-2
5.3 - CONFIGURING A PPP PORT ......................................................................................................... 5-9
5.4 - VIEWING THE ROUTING CONFIGURATION ..................................................................................... 5-10
5.5 - BUILDING A POINT-TO-POINT LINK ............................................................................................... 5-11
5.6 - BUILDING A BUS LINK ................................................................................................................. 5-12
5.7 - BUILDING A RING ....................................................................................................................... 5-13
5.8 - MANAGING EQUIPMENT THROUGH THE NETWORK OF A DIFFERENT SUPPLIER ................................ 5-14

Page A0-6
DEGRADED MODE ...................................................................................................................... 6-1

6.1 - DEFINITION ................................................................................................................................. 6-1
6.2 - CHARACTERIZATION .................................................................................................................... 6-2
6.3 - POSSIBLE CAUSES ...................................................................................................................... 6-2
6.4 - OPERATOR ACTIONS ................................................................................................................... 6-4
6.5 - DEGRADED MODE SWITCH WARNING ............................................................................................ 6-8
6.6 - ACTIONS TO REALIZE ACCORDING TO CASES ................................................................................. 6-9
GFP150 EXTRA CARD ................................................................................................................ 7-1

7.1 - GFP150 EXTRA CARD AND SERVICES PRESENTATION.................................................................. 7-1
7.2 - CONFIGURATION AND APPLICATIONS OF THE GFP150 EXTRA CARDS ............................................ 7-3
7.2.1 - GFP150 eXtra card setup .................................................................................................. 7-3
7.2.2 - Create a LAN interconnection............................................................................................ 7-3
7.2.2.1 - Point-to-Point mode interconnection : EPLine service ............................................................. 7-3
7.2.2.2 - Point-to-Point mode interconnection : EVPLine service (aggregation)..................................... 7-9
7.2.2.3 - Hub and Spoke interconnection: EPLAN service................................................................. 7-13
7.2.2.4 - Bus interconnection : service EPLAN..................................................................................... 7-18
7.2.2.5 - Bus interconnection : service EVPLAN ................................................................................ 7-22
7.2.3 - Implementation of the OAM-CC function (Operation Administration Maintenance Continuity Check) on the GFP150 eXtra card............................................................................. 7-23
7.2.4 - Using Quality of Service features of GFP150 eXtra card ................................................ 7-24
7.2.4.1 - QoS functions of the GFP150 eXtra card ................................................................................. 7-24
7.2.4.2 - Configuring the QoS features ................................................................................................... 7-26
7.2.5 - Using the Multiple Spanning Tree Protocol on the GFP150 eXtra card .......................... 7-30
7.2.5.1 - Description of the Multiple Spanning Tree Protocol on the GFP150 eXtra card ....................... 7-30
7.2.5.2 - MSTP Licence Activation on a GFP150 eXtra card .................................................................. 7-32
7.2.5.3 - Example of MSTP configuration ............................................................................................... 7-33
7.2.6 - Using LCAS on the GFP150 eXtra card .......................................................................... 7-37

7.2.6.1 - Description of LCAS ................................................................................................................. 7-37
7.2.6.2 - Example of LCAS configuration................................................................................................ 7-37
7.3 - A FEW RULES FOR SET-UP ......................................................................................................... 7-40

7.3.1 - Various configuration rules .............................................................................................. 7-40
7.3.2 - QoS configuration rules ................................................................................................... 7-40
7.4 - APPLICATIONS .......................................................................................................................... 7-40
7.4.1 - Meshed networks ............................................................................................................. 7-40
7.4.2 - Protection of channels ..................................................................................................... 7-40
7.4.3 - Degraded mode ............................................................................................................... 7-41
7.5 - TECHNICAL CHARACTERISTICS .................................................................................................. 7-41
7.5.1 - Main characteristics ......................................................................................................... 7-41
7.5.2 - Ethernet rate / VCG rate .................................................................................................. 7-42
7.5.3 - Number of VC12 in a VCG............................................................................................... 7-43
7.5.4 - Number of VC3 in a VCG................................................................................................. 7-43
A
CONSTRUCTION OF AN IP NETWORK ADRESSING PLAN....................................................A-1

A.1 - PRELIMINARY REMARKS ..............................................................................................................A-1
A.2 - IP ADDRESSING ..........................................................................................................................A-2
A.3 - ADDRESSING PLAN .....................................................................................................................A-3
A.4 - USE OF STATIC TABLES ...............................................................................................................A-3
A.5 - USE OF RIP ROUTING DAEMON ...................................................................................................A-5
A.6 - USE OF OSPF ROUTING DAEMON................................................................................................A-6

Page A0-7
OPTICAL BOOSTER....................................................................................................................B-1
B.1 - INSTALLATION........................................................................................................................B-1
B.1.1 - Access security level .........................................................................................................B-1
B.1.2 - General information ...........................................................................................................B-1
B.1.3 - Installation..........................................................................................................................B-2
B.1.4 - Connection of access points..............................................................................................B-2
B.1.4.1 - Optical ports ...............................................................................................................................B-2
B.1.4.2 - Power port..................................................................................................................................B-3
B.1.4.3 - Alarm loops ................................................................................................................................B-4
B.2 - OPERATION ............................................................................................................................B-4

B.2.1 - General information ...........................................................................................................B-4
B.2.2 - Maintenance command and operation ..............................................................................B-4
B.2.3 - Display and directions for use ...........................................................................................B-5
B.2.4 - Alarm processing ...............................................................................................................B-5
B.3 - SPARE PART AND CABLES...................................................................................................B-6
B.4 - TECHNICAL CHARACTERISTICS..........................................................................................B-7
C
MUX 10000 A/T.............................................................................................................................C-1

C.1 - INSTALLATION........................................................................................................................C-1
C.1.1 - General information ...........................................................................................................C-1
C.1.2 - Installation .........................................................................................................................C-2
C.1.3 - Connection of access points .............................................................................................C-3
C.2 - OPERATION ............................................................................................................................C-3
C.2.1 - General information ...........................................................................................................C-3
C.2.2 - Maintenance command and operation ..............................................................................C-4
C.2.3 - Multiplexing demultiplexing function specification..........................................................C-4
C.2.4 - Optical power budget ........................................................................................................C-5
C.3 - SPARE PARTS AND CABLES ................................................................................................C-5
C.4 - TECHNICAL CHARACTERISTICS..........................................................................................C-6
SECTION B - Guide d'installation et d'utilisation.............B0-1 to BC-6

Page A0-8
LIST OF FIGURES
Figure 1-1 - Installation of ADR2500 eXtra shelf in 19" rack................................................................ 1-5

Figure 1-2 - Installation of ADR2500 eXtra shelf in ETSI rack ............................................................. 1-6
Figure 1-3 - ADR2500 eXtra equipped shelf ........................................................................................ 1-7
Figure 1-4 - Front panel of LTU21E120 card ..................................................................................... 1-12
Figure 1-5 - Front panel of LTU3E3DS3 card .................................................................................... 1-14
Figure 1-6 - Front panel of CCU-2G card........................................................................................... 1-14
Figure 1-7 - POWER/ALM power supply cable ............................................................................. 1-16
Figure 1-8 - Front panel of CTRL-2G card ......................................................................................... 1-18
Figure 1-9 - Comm connection cable ........................................................................................... 1-19
Figure 1-10 - Straight-through Ethernet cable.............................................................................. 1-20
Figure 1-11 - Cross-over Ethernet cable ..................................................................................... 1-20
Figure 1-12 - Front panel of AUX card ............................................................................................... 1-21
Figure 1-13 - AUX/EOW connection cable................................................................................... 1-21
Figure 1-14 - Front panel of 3E3DS3FA card..................................................................................... 1-22
Figure 1-15 - Front panel of 63E1FA card.......................................................................................... 1-23
Figure 1-16 - Front panel of STM-1 interface card ............................................................................. 1-23
Figure 1-17 - Front panel of STM-4 interface card ............................................................................. 1-24
Figure 1-18 - Front panel of STM-16 interface card........................................................................... 1-24
Figure 1-19 - Front panel of 4ERE interface card .............................................................................. 1-27
Figure 1-20 - Front panel of GIG-E interface card.............................................................................. 1-27
Figure 1-21 - Front panel of 2GE-DM interface card.......................................................................... 1-29
Figure 1-22 - Front panel of GFP150 eXtra card................................................................................ 1-30
Figure 2-1 - Commissioning process for an ADR2500 eXtra network ................................................. 2-2
Figure 2-2 - Communication function on an ADR2500 eXtra............................................................... 2-4
Figure 2-3 - Example of communication on an ADR2500 eXtra, ADR 2500c, ADR155c and other
equipment network ........................................................................................................................ 2-5
Figure 2-4 - Menus tree ...................................................................................................................... 2-13
Figure 2-5 - Shelf view screen of web browser ............................................................................. 2-14
Figure 2-6 - Synchronization using 2 MHz external synchronization input (T3)................................. 2-58
Figure 2-7 - Synchronization using a synchronous tributary access.................................................. 2-58
Figure 2-8 - Remote loopback function (collection of alarms on a Central Site)............................... 2-60
Figure 2-9 - Example of a protected ring............................................................................................ 2-61
Figure 2-10 - Topological map of a ring ............................................................................................. 2-63
Figure 2-11 - Example of incoming and outgoing traffic of a ring....................................................... 2-63
Figure 2-12 - TC EndPoints X/Y......................................................................................................... 2-67
Figure 2-13 - TC EndPoints X/Y - Source facing Sink ....................................................................... 2-67
Figure 2-14 - TC EndPoints X/Y - Source not facing Sink ................................................................. 2-68
Figure 2-15 - TC EndPoints X/Y Source and Sink back to back ..................................................... 2-68
Figure 2-16 - TC Monitoring Point Z located between TC EndPoint X and TC EndPoint Y .............. 2-69

Page A0-9
Figure 7-1- Hardware design of the card.............................................................................................. 7-2

Figure 7-2 - EPLine service .................................................................................................................. 7-3
Figure 7-3 - Configuring the Ethernet interface .................................................................................... 7-4
Figure 7-4 - Configuring the VCG (1) ................................................................................................... 7-6
Figure 7-5 - Configuring the VCG (2) ................................................................................................... 7-6
Figure 7-6 - Configuring the Ethernet Switch (1).................................................................................. 7-7
Figure 7-7 - Configuring the Ethernet Switch (2).................................................................................. 7-7
Figure 7-8 - Configuring the SDH Cross Connects .............................................................................. 7-8
Figure 7-9 - Connectivity check ............................................................................................................ 7-9
Figure 7-10 - Service EVPLine ........................................................................................................... 7-10
Figure 7-11 - Configuring the VCG (1) ............................................................................................... 7-10
Figure 7-13 - Configuring the Ethernet Switch .................................................................................. 7-12
Figure 7-14 - Configuring the SDH Cross Connects .......................................................................... 7-12
Figure 7-15 - EPLAN service.............................................................................................................. 7-13
Figure 7-16 - Configuring the Ethernet interface ................................................................................ 7-14
Figure 7-19 - Configuring the Ethernet Switch (1).............................................................................. 7-16
Figure 7-21 - EPLAN Service - "bus" mode ....................................................................................... 7-18
Figure 7-26 - EVPLAN Service - "bus" mode ..................................................................................... 7-22
Figure 7-27 - Example of OAM utilization........................................................................................... 7-23
Figure 7-28 - QoS architecture ........................................................................................................... 7-24
Figure 7-29 - Traffic profile ................................................................................................................. 7-25
Figure 7-30 - Configuring a srTCM profile.......................................................................................... 7-27
Figure 7-31 - Configuring a trTCM profile........................................................................................... 7-27
Figure 7-32 - Reading Traffic Classes parameters ............................................................................ 7-28
Figure 7-33 - Regulating Traffic Classes SP parameters................................................................... 7-28
Figure 7-34 - SLA compliance counters ............................................................................................. 7-29
Figure 7-35 - VMAN Port counters ..................................................................................................... 7-29
Figure 7-36 - MSTP port types ........................................................................................................... 7-31
Figure 7-37 - MSTP Licence Activation............................................................................................. 7-32
Figure 7-38 - Example of MSTP configuration ................................................................................... 7-33
Figure 7-39 - Activating MSTP on the ADR2500 eXtra 2 and 4 (1) ................................................... 7-34
Figure 7-40 - Activating MSTP on the ADR2500 eXtra 2 and 4 (2) ................................................... 7-35
Figure 7-41 - MSTI Checking (1) ....................................................................................................... 7-36
Figure 7-42 - MSTI Checking (2) ....................................................................................................... 7-36
Figure 7-43 - Configuring the VCG (LCAS) (1) .................................................................................. 7-38
Figure 7-44 - Configuring the VCG (LCAS) (2) .................................................................................. 7-38
Figure 7-45 - Configuring the SDH cross-connects (LCAS)............................................................... 7-39
Figure A-1 - IP protocol stack ...............................................................................................................A-1
Figure A-2 - Example TMN architecture...............................................................................................A-4
Figure B-1 - Optical booster Installation in rack ................................................................................B-2
Figure B-2 - Optical booster Optical access points ...........................................................................B-2
Figure C-1 - MUX10000T Block diagram (1/2 MUX 10000A) ..............................................................C-1
Figure C-2 - MUX 10000 T Front panel.............................................................................................C-2
Figure C-3 - MUX 10000 A Front panel.............................................................................................C-2
Figure C-4 - MUX 10000 A Installation in 19" rack............................................................................C-2
Figure C-5 - MUX 10000 A or T Optical access points .....................................................................C-3

Page A0-10
LIST OF TABLES
Table 1-1 - Designation of ADR2500 eXtra slots ................................................................................. 1-8

Table 1-2 - Characteristics of single mode interfaces ........................................................................ 1-25
Table 1-3 - Characteristics of multimode interface............................................................................. 1-26
Table 1-4 - Characteristics of GigaEthernet interface ........................................................................ 1-28
Table 1-5 - Characteristics of GigaEthernet interface ........................................................................ 1-29
Table 2-1 - Minimum configuration for operation PC ........................................................................... 2-1
Table 2-2 - Functional blocks of ADR2500 eXtra ............................................................................... 2-17
Tables 2-3 to 2-5 - Network configuration parameters....................................................................... 2-19
Tables 2-6 to 2-25 - Equipment configuration parameters................................................................. 2-22
Table 2-26 - Maintenance commands and operations....................................................................... 2-42
Table 2-27 - Specific indicator LEDs to CTRL-2G card ..................................................................... 2-42
Table 2-28 - TRAFFIC indicator LEDs on PDH, STM, GIG-E, xGE-DM, GFP150 eXtra
and
SWITCH HO/LO cards ................................................................................................................ 2-43
Table 2-29 - STATUS indicator LEDs on all cards except PSU and FAN-2G ............................. 2-43
Table 2-30 - STATUS indicator LEDs on PSU cards ................................................................... 2-43
Table 2-31 - Specific indicator LEDs to GFP150 eXtra card.............................................................. 2-43
Table 2-32 - Pushbuttons ................................................................................................................... 2-44
Tables 2-33 to 2-37 - Alarms and severity levels ............................................................................... 2-45
Table 2-38 - Associated informations to card defective alarm ........................................................... 2-50
Table 2-39 - Correlation of STM-n faults ............................................................................................ 2-51
Table 2-40 - Correlation of MSP faults ............................................................................................... 2-51
Table 2-41 - Correlation of MS-SPRing faults .................................................................................... 2-51
Table 2-42 - Correlation of HPOM/HPT faults from SDH and xGE-DM cards ................................... 2-52
Table 2-43 - Correlation of HPT faults from GIG-E cards ................................................................. 2-52
Table 2-44 - Correlation of HPA/LPOM/LPT faults ........................................................................... 2-53
Table 2-45 - Correlation of 2, 34, 45 Mbit/s ports faults ..................................................................... 2-53
Table 2-46 - Correlation of VCG faults from GFP150 eXtra, GIG-E and xGE-DM cards................... 2-54
Tables 3-1 to 3-2 - List of no rohs ADR2500 eXtra items .................................................................... 3-1
Table 3-3 - List of rohs ADR2500 eXtra items ..................................................................................... 3-3
Table 3-4 - List of rohs optical modules of ADR2500 eXtra ................................................................. 3-4
Tables 3-5 to 3-7 - List of available cables........................................................................................... 3-4
Tables 4-1 to 4-3 - Technical characteristics of ADR2500 eXtra ......................................................... 4-1
Tables 6-1 to 6-5 - Actions to realize according to cases .................................................................... 6-9
Table B-1 - Access security level .........................................................................................................B-1
Table B-2 - Failure indication definition ................................................................................................B-5
Table B-3 - List of items........................................................................................................................B-6
Table B-4 - List of available cables ......................................................................................................B-6
Table B-5 - Technical characteristics ...................................................................................................B-7
Table C-1 - MUX/DEMUX Specification ...............................................................................................C-4
Table C-2 - Optical power budget ........................................................................................................C-5
Table C-3 - List of items .......................................................................................................................C-5
Table C-4 - List of available cables ......................................................................................................C-6
Table C-5 - Technical Characteristics ..................................................................................................C-6

Page A0-11

Page A0-12
1 - INSTALLATION
1 INSTALLATION
1.1 - GENERAL INFORMATION

The ADR2500 eXtra (Add-Drop multiplexer 2500 Mbit/s) is an STM-16 optical add-drop
multiplexer used to build STM-16 point-to-point links, STM-16 rings or meshed networks with
SNC path protection or MSP protection or MS-SPRing protection (line) to fulfil transport
of 2 Mbit/s, 34/45 Mbit/s, STM-1, STM-4, STM-16 links, of 10/100 Base TX Fast Ethernet data, of
gigabit Ethernet data.
The ADR2500 eXtra offers a cross-connection with VC4-16c, VC4-4c, VC4, VC3, VC12
granularity, called "SWITCH HO/LO" with 64x64 VC4 (or 32x32 VC4), 192x192 VC3 (or 96x96
VC3) and/or 4032x4032 VC12 (or 2016x2016 VC12) capacity, unidirectional or bi-directional.
From P2.4 release, the STM-n and xGE-DM cards offer extractable interfaces SFP (Small Form
Factor Pluggable), also integrating DDM (DIGITAL Diagnostic Monitoring) function.
On STM-16 side, the ADR2500 eXtra allows regeneration sections of up to 60 km at 1310 nm and
100 km at 1550 nm ; if it is associated to an optical booster, via an U16.2 card, the section can
reach 150 km.
The association with a MUX 10000 Unit allows an optical multiplexing - demultiplexing function of
four STM-16 signals from four L16.2+ cards with wavelength in the 200 GHz grid (1,6 nm).
The ADR2500 eXtra can optionally include the protection of power supply, of switching matrix
function and of PDH cards.
The ADR2500 eXtra can be used as :
Terminal Multiplexer with maximum capacity of 1 STM-16 or 4 STM-4 or 16 STM-1 or 378

E1 tributaries (with 63E1FA card) or 18 E3/DS3 tributaries (with E3DS3FA card) and with
tributary and line protection MSP 1+1,
Pseudo-repeater, with capacity to regenerate 1 or 2 STM-16 lines,
STM-16 add/drop Multiplexer with maximum capacity of 2 STM-16 line and of 378 E1
tributaries (with 63E1FA card) or 18 E3/DS3 tributaries (with E3DS3FA card) or 32 STM-1 or
8 STM-4 or 2 STM-16 tributaries,
STM-4 add/drop Multiplexer with maximum capacity of 2 STM-4 line and of 378 E1
tributaries (with 63E1FA card) or 18 E3/DS3 tributaries (with E3DS3FA card) or 8 STM-1 or
2 STM-4 tributaries.
LAN over VC12 or VC3 interconnection point through the GFP150 eXtra card
The GFP150 eXtra data traffic is compatible with those of the GFP150 and 4E/FE cards of
the ADR155X.
Gigabit Ethernet over SDH transport through the GIG-E or xGE-DM cards.
The ADR2500 eXtra interworks with equipment of the synchronous digital hierarchy complying
with recommendations G.707, G.783 and G.7041 of the ITU-T.
Installation and User Guide - 288 113 969-01

Page A1-1
1 - INSTALLATION
This equipment can be managed :
by a local terminal with VT100 emulation required on commissioning for communication

parameter configuration ("COMM" access),
by an HTTP server for local or remote interactive operation using a Web Browser,
remotely, by means of an SNMP protocol via an IONOS NMS network manager ; using
SNMP protocol also allows the supervision of the whole network
The connection of this manager to the management network is performed via the Ethernet
access ("ETH") of the CTRL-2G management card.
The management network is made of the Ethernet access ("ETH"), of the DCC (D1-D3 and
D4-D6), of the STM-16 line and STM-n tributaries, of the 2 VC12 that can be used for
management.
The VC12 used for management of the ADR2500 eXtra are compatible with those of the
ADR 155c (from P4.1-ae release), those of the ADR155CPE and those of the
ADR2500c P3.
The ADR2500 eXtra is mounted in a 19" or ETSI rack.

The ADR2500 eXtra is made of :
one 14U shelf equipped with a back panel,
one to twelve LTU interface cards :
one to twelve LTU21E120 or LTU21E75 cards dedicated by group of 3 to the tributary

PDH 63E1 cards. Each LTU includes the connectors for 21x2 Mbit/s ports.
one to four LTU3E3DS3 cards dedicated to the tributary PDH 3E3DS3 cards. Each
LTU includes the connectors for 3x 34 or 45 Mbit/s ports.
One or two 48 VDC Power Supply Unit cards (PSU-160 or PSU-2G).

Only one PSU card is required if the equipment receives a SW 32 HO/LO card, two PSU
cards are mandatory if the equipment receives a SWITCH HO/LO card
A second or third card can be inserted in the shelf as automatic 1:1 or 1:2 protection
The utilization of the PSU-2G card is possible in order to arrange an unique maintenance
share between ADR 2500c and ADR2500 eXtra.
one Common Connecting Unit card (CCU-2G) for the power supply, the remote signaling,
the station remote controls and alarms and the synchronization signals,
one Control Unit card (CTRL-2G),
two Auxiliary Channels cards (AUX),
one SWITCH HO/LO card enabling VC4-16c, VC4-4c, VC4, VC3, VC12 granularity,
- either one SWITCH HO/LO card with 64 VC4 max switching
- either one SW 32 HO/LO card with 32 VC4 max switching
A second card, inevitably of the same type that the first, can be inserted in the shelf as
automatic or manual 1:1 protection.

Page A1-2
1 - INSTALLATION
one to ten interface cards as required :
one to four tributary PDH 63E1 cards allowing 63 VC12 connections.

Each card is associated to a LTU21E1 group from 1 to 3.
A fifth card can be inserted in the shelf as automatic or manual 1:4 max protection
one to six tributary PDH 63E1FA cards allowing 63 VC12 connections
This card regroups the functions of LTU interface and tributary ; it includes the
connectors for 63x2 Mbit/s ports ; it allows to increase the add/drop capacity of PDH
access points.
This card cannot be protected nor to be used in protection
one to four tributary PDH 3E3DS3 cards allowing 3 VC3 connections.
Each card is associated to a LTU3E3DS3.
A fifth card can be inserted in the shelf as automatic or manual 1:4 max protection
one to six tributary PDH 3E3DS3FA cards allowing 3 VC3 connections
This card regroups the functions of LTU interface and tributary ; it includes the
connectors for 3x 34 or 45 Mbit/s ports ; it allows to increase the add/drop capacity of
PDH access points
This card cannot be protected nor to be used in protection
one to eight cards with 1 to 4 optical STM-1 access points enabling on each access
one VC4 connection or 3 VC3 connections or 63 VC12 connections.
one to eight 4ERE cards with 4 electrical STM-1 access points enabling on each
access one VC4 connection or 3 VC3 connections or 63 VC12 connections.
one to ten cards with one optical STM-4 access enabling one VC4-4c connection or 4
VC4 connections or 12 VC3 connections or 252 VC12 connections.
one to four cards with 1 optical STM-16 access enabling one VC4-16c connection or
4 VC4-4c connections or 16 VC4 connections or 48 VC3 connections or 1008 VC12
connections
one to four GigaEthernet GIG-E cards enabling a Gigabit Ethernet over SDH transport
service on a VCG composed of n VC4 (n = 1 to 7)
one to N GigaEthernet xGE-DM (x=1 or 2 ports), exploitable in STM4 mode (N=10) or
in STM16 mode(N=4) ; this card allows a Gigabit Ethernet over SDH transport service
on one or two VCG (1 per port) composed of n VC4 (n = 1 to 4 in STM4 mode and n =
1 to 7 in STM16 mode).
one to six GFP150 eXtra card with 8 10/100 Base TX Fast Ethernet ports, allowing
up to 3 VC3 or 63 VC12 connections in 8 Virtually Concatenated Groups
one extractable FAN-2G unit in bottom of the shelf.

FAN-2G is a fan module in charge of pushing external ambiant temperature air into the shelf
for power dissipation purposes.
It is composed of three separately monitored and controlled FANs, all powered by the output
of the embedded 48V // 12V DC converter.
Note that the 48V // 12 V DC converter can optionally be redunded for best possible
availability.
The minimum configuration in Terminal application - comprises a shelf equipped with one or
two PSU cards (according to the type of inserted SWITCH HO/LO card), one CCU-2G card, one
CTRL-2G card, one SWITCH HO/LO card, one FAN-2G unit, one line card and one SDH or
PDH tributary card (with corresponding LTU card if necessary) to which the necessary
transmission and redundancy cards are added.
For the connection of the different access points of cards, see 1.3 "Connection of Access
points"

Page A1-3
1 - INSTALLATION
1.2 - INSTALLATION OF THE SHELF

The ADR2500 eXtra shelf, equipped with a back panel, can be installed in a 19" or ETSI rack.
(see Figure 1-1 and Figure 1-2).
The ADR2500 eXtra shelf is delivered with an adequate adaptation kit (in its own packing) :
either a 19" kit constituted of 2 19" brackets (1 right + 1 left) + 12 screws M3x6 + 12 flat
washers M3,
either an ETSI kit constituted of 2 ETSI brackets (1 right + 1 left) + 12 screws M3x6 + 12 flat
washers M3,
The mounting kit for installation of the shelf on the uprights of the 19" or ETSI rack, formed by 6
cage nuts and 6 screws, is not supplied with the shelf
Installation in 19" rack

The ADR2500 eXtra has ventilation-type heat regulation system. When installing, provide for two
appropriate spaces : one below the shelf for the hold of air (minimum 75 mm), the other in top of
the shelf for the evacuation of air and the passage of cables (minimum 75 mm).
Proceed as following :
Insert the FAN-2G module in the shelf before integrating this one in the rack.
provide a 14U position in the rack for each equipment, 2U space under the shelf and 2U
space above the shelf, placing either a passive equipment (coiling assembly for example)
either a deflector of air between 2 shelves.
secure the mounting brackets for installation in a 19" rack to either side of the empty shelf,
placing a washer behind the screw head.
clip the 3 cage nuts M6 in their housings on the left upright of the rack (see distance
between 2 cage nuts on figure),
clip the 3 cage nuts M6 in their housings on the right upright of the rack (see distance
between 2 cage nuts on figure),
offer the rear of the shelf facing the rack,
slide the shelf equipped with the FAN-2G module until the mounting brackets come into
contact with the uprights, in line with the 6 cage nuts, then secure using the 6 screws
M 6 x 12.
Installation in ETSI rack

The installation of the shelf in the ETSI rack is the same than the procedure used for the 19"
rack.
In this case, use the set of mounting brackets specific to installation in ETSI rack
Provide a 25 SU position in the rack for each equipment, 3 SU space under the shelf and 4 SU
space above the shelf, placing either a passive equipment (coiling assembly for example) either
a deflector of air between 2 shelves.

Page A1-4
1 - INSTALLATION
177,8 mm
177,8 mm
3 screws
M6x12
3 cage
nuts M6
Figure 1-1 : Installation of ADR2500 eXtra shelf in 19" rack

Page A1-5
1 - INSTALLATION
175 mm
175 mm
3 screws
M6x12
3 cage
nuts M6
Figure 1-2 : Installation of ADR2500 eXtra shelf in ETSI rack

Page A1-6
1 - INSTALLATION
Figure 1-3 : ADR2500 eXtra equipped shelf

Page A1-7
1 - INSTALLATION
LTU 5-1
LTU 5-2 LTU 5-3 LTU 6-1
2 Mbits
34/45
Mbits
PDH
Ports
2 Mbits
PDH
Ports
2 Mbits
PDH
Ports
PSU 2
PSU 3
PSU 1
PSU-160
PSU-2G
CCU
CCU2G
PSU-160 PSU-160
PSU-2G PSU-2G
EXT 1
AUX
EXT 2
AUX
CTRL
CTRL2G
LTU 6-2 LTU 6-3
2 Mbits
2 Mbits
34/45
PDH
Mbits
Ports
PDH Ports
TRIB 2
2 Mbits
PDH
Ports
TRIB 4 TRIB 6
STM-1
STM-4
E1 Prot or
working
GFP150
eXtra
3E3DS3FA
63E1FA
xGE-DM
STM-1
STM-4
STM-16
GIG-E
xGE-DM
TRIB 1
TRIB 3 TRIB 5
STM-1
STM-4
E3 Prot or
working
GFP150
eXtra
3E3DS3FA
63E1FA
xGE-DM
STM-1
STM-4
STM16
GIG-E
xGE-DM
STM-1
STM-4
63E1
63E1FA
3E3DS3
3E3DS3FA
GFP150
eXtra
xGE-DM
STM-1
STM-4
63E1
63E1FA
3E3DS3
3E3DS3FA
GFP150
eXtra
xGE-DM
LTU 7-1
LTU 7-2 LTU 7-3
2 Mbits
2 Mbits
34/45
PDH
Mbits
Ports
PDH Ports
TRIB 8
STM-1
STM-4
63E1
63E1FA
3E3DS3
3E3DS3FA
GFP150
2 Mbits
PDH
Ports
LTU 8-1
LINE 2 SWITCH 1
STM-16
STM-4
GIG-E
xGE-DM
LTU 8-2
2 Mbits
2 Mbits
34/45
PDH
Mbits
Ports
PDH Ports
SWITCH HO/LO
SW32HOLO
SWITCH 2
SWITCH HO/LO
SW32HOLO
eXtra
xGE-DM
TRIB 7
STM-1
STM-4
63E1
63E1FA
3E3DS3
3E3DS3FA
GFP150
eXtra
xGE-DM
LINE 1
STM-16
STM-4
GIG-E
xGE-DM
FAN (FAN-2G)
Table 1-1 : Designation of ADR2500 eXtra slots
The fully equipped ADR2500 eXtra contains (See Chapter 3 - Tables 3-1 to 3-4 : List of
ADR2500 eXtra items) :
one to twelve LTU interface cards :
one to twelve LTU21E120 or LTU21E75 cards (LTU 5-x to LTU 8-x)

one to four LTU3E3DS3 cards (LTU 5-1, LTU 6-1, LTU 7-1, LTU 8-1)
If a LTU3E3DS3 card is inserted in LTU x-1 slot, the LTU x-2 and LTU x-3 cannot be
used.
one to three power supply unit cards PSU (PSU 1, PSU 2 and PSU 3 slots),
one common connecting unit card CCU-2G (CCU slot)
one control unit card CTRL-2G (CTRL slot),
two auxiliary channels cards AUX (EXT 1 and EXT 2 slots),
one to ten interface cards as required :
one to five PDH 63E1 cards (TRIB 5 to TRIB 8 and TRIB 2 slots)
In TRIB 5 to TRIB 8, this card is mandatory associated to a corresponding LTU21E1
group from 1 to 3.
In TRIB 2, this card is used either in protection mode or in working mode ; in this last
case, it will be associated to a LTU21E1 group from 1 to 3

Page A1-8
LTU 8-3
2 Mbits
PDH
Ports
1 - INSTALLATION
one to six PDH 63E1FA cards (TRIB 1, TRIB 2, TRIB 5 to TRIB 8 slots)
one to five PDH 3E3DS3 cards (TRIB 5 to TRIB 8 and TRIB 1 slots)
In TRIB 5 to TRIB 8, this card is mandatory associated to the corresponding
LTU3E3DS3.
In TRIB 1, this card is used either in protection mode or in working mode ; in this last
case, it will be associated to one LTU3E3DS3.
one to six PDH 3E3DS3FA cards (TRIB 1, TRIB 2, TRIB 5 to TRIB 8 slots)
one to eight STM-1 cards (TRIB 1 to TRIB 8 slots)
one to ten STM-4 cards (TRIB 1 to TRIB 8, LINE 1 or LINE 2 slots)
one to four STM-16 cards (TRIB 3, TRIB 4, LINE 1 or LINE 2 slots),
The STM-16 cards which take place in TRIB 3 or TRIB 4 are exploited without MSSPRing Protection ; in these configurations, the TRIB 1, TRIB 5 and TRIB 7 or TRIB
2, TRIB 4 and TRIB 6 slots cannot be used, because the STM-16 card uses all its
bandwidth.
one to four GIG-E cards (TRIB 3, TRIB 4, LINE 1 or LINE 2 slots)
If the GIG-E cards take place in TRIB 3 or TRIB 4, the TRIB 1, TRIB 5 and TRIB 7 or
TRIB 2, TRIB 4 and TRIB 6 slots cannot be exploited, because the GIG-E card uses
an internal bandwidth equivalent to a STM-16.
One to N xGE-DM cards according to the chosen configuration :
- in STM4 mode, N=10 (TRIB 1 to TRIB 8, LINE 1 or LINE 2 slots)
- en STM16 mode, N=4 (TRIB 3, TRIB 4, LINE 1 or LINE 2 slots)
The xGE-DM cards, configured in STM16 mode, which take place in TRIB 3 or TRIB 4
slots make not exploitable the TRIB 1, TRIB 5 and TRIB 7 or TRIB 2, TRIB 6 and
TRIB 8 slots, because the xGE-DM card uses an internal bandwidth equivalent to a
STM-16
one to six GFP150 eXtra cards (TRIB 1, TRIB 2 or TRIB 5 to TRIB 8 slots)
one or two SWITCH HO/LO cards (SWITCH 1 and SWITCH 2 slots),

If the equipement receives a SW32 HO/LO card, the "LINE 1" and "LINE 2" slots cannot be
used.
one FAN-2G unit located at the bottom of the shelf (FAN slot).
No adjustment or configuration is required on the equipment to be installed. All parameter values

are defined during the commissioning procedure and using the on-board operating software.
The "TRIB" and "LINE" slots have a double width in order to be able to receive 63E1, 63E1FA,
3E3DS3, 3E3DS3FA, SFP release STM-n, GIG-E and xGE-DM cards.
The STM-n cards will be positioned in the right part of the slot, the left part receiving an
appropriated cover.
The GFP150 eXtra cards will take place in the left part of the slot, with cover in the right part.
Covers are also provided for the other empty slots
All connections are performed on the front panel of the cards.
Layout of cards
REMINDER : Before all intervention on the cards, be sure to put on an antistatic bracelet.
Refer to Table 1-1 : Designation of ADR2500 eXtra slots

Page A1-9
1 - INSTALLATION
TRIB and LINE slots are unmarked slots with the following constraints :
-
the STM-16 and GIG-E cards take only place in the TRIB 3, TRIB 4, LINE 1 and LINE 2
slots.
the xGE-DM cards can be configured in STM16 mode only in the TRIB 3, TRIB 4, LINE 1
and LINE 2 slots
the LINE 1 and LINE 2 slots can only receive STM-4, STM-16, GIG-E or xGE-DM cards.
To make wiring more easy and fulfil the same configuration in all the sites, it is recommended to
proceed as following :
place the LTU cards from left to right by using of preference LTU 6-x and LTU 8-x blocks for
the 2 Mbit/s connectings (E1) and the LTU 5-x and LTU 7-x blocks for the 34/45 Mbit/s
connectings (E3/DS3).
place the first PSU card in the PSU 1 slot,
place the first AUX card in the EXT 1 slot,
place the first SWITCH HO/LO card in the SWITCH 1 slot,
In the absence of 2 Mbit/s connectings (E1), in order to allow STM-16 tributaries and a
protection of 34/45 Mbit/s accesses :
place the tributary PDH, STM-1, STM-4, GFP150 eXtra card(s) by starting with TRIB
1, TRIB 3, TRIB 5 and TRIB 7 slots and by continuing with TRIB 2, TRIB 4, TRIB 6
and TRIB 8 slots
place the first tributary STM-16 card in the TRIB 4 slot,
place the first line STM-16 card in the LINE 2 slot,
place the first GIG-E or xGE-DM card in the TRIB 4 slot,
In the absence of 34/45 Mbit/s connectings (E3/DS3), in order to allow STM-16 tributaries
and a protection of 2 Mbit/s accesses :
place the tributary PDH, STM-1, STM-4, GFP150 eXtra card(s) by starting with TRIB
2, TRIB 4, TRIB 6 and TRIB 8 slots and by continuing with TRIB 1, TRIB 3, TRIB 5
and TRIB 7 slots
place the first tributary STM-16 card in the TRIB 3 slot,
place the first line STM-16 card in the LINE 2 slot,
place the first GIG-E or xGE-DM card in the TRIB 3 slot,
secure the cards, the covers and the ventilation unit by screwing.

Page A1-10
1 - INSTALLATION
1.3 - CONNECTION OF ACCESS POINTS

All the connections are performed on the front panel of the cards. The PSU, 63E1, 3E3DS3 and
SWITCH HO/LO cards do not have connectors ; the power supply cord is connected to the
CCU-2G card.
The cards can be removed without intervening on the other cards or on their connections.
On the LTU21E120 and LTU21E75 cards :
21x2Mbit/s traffic ports "E1 OUTPUT" and "E1 INPUT"
On the LTU3EDS3 card :
3x 34 or 45 Mbit/s traffic ports "TR" and "REC"
On the CCU-2G card :
station power supply and alarms access "POWER/ALM 48V 13A maxi"
remote signaling and remote control access "LOOPS"
2MHz synchronization access " SYNC"
On the CTRL-2G card :
Ethernet management access "ETH"
IP address configuration access "COMM" : allows the connection to a VT 100 terminal or

emulation
On the AUX card :
3 Engineering Order Wire access points
On the 63E1FA card :
3x 21x2Mbit/s traffic ports "E1 OUTPUT" and "E1 INPUT"
On the 3EDS3FA card :
3x 34 or 45 Mbit/s traffic ports "TR" and "REC"
On the STM-n cards, according to the kind of card :
1 to 4 optical STM-1 access points "TR" and "REC"
4 electrical STM-1 access points "TR" and "REC"
1 optical STM-4 access "TR" and "REC"
1 optical STM-16 access "TR" and "REC"
On the GIG-E card :
optical Gigabit Ethernet access "TR" and "REC"
maintenance access "RS232" : allows the connection to a VT 100 terminal or emulation

Page A1-11
1 - INSTALLATION
On the xGE-DM card :
1 or 2 optical Gigabit Ethernet access "TR" and "REC"
On the GFP150 eXtra card :
8 10/100 Base TX Fast Ethernet access points "ETH"
Refer to the list of available cables in Chapter 3 - Spare parts and Cables.
Connection rules
All the access points are provided directly on the front panel of the cards.
All the cables are directed upwards through the intermediary of fibers-guide, except the
cable of power supply that is oriented downwards.
The cable paths should not interfere with extraction of a module; therefore, the connecting of
the shelf should have sufficient slack.
1.3.1 - Connection to LTU21E1 or LTU21E75 cards
Figure 1-4 Front panel of LTU21E120 card
"E1 INPUT" and "E1 OUTPUT" G.703 21x2 Mbit/s traffic ports :
ports
21 x 2 Mbit/s traffic ports compliant with the ITU-T G.703

Recommendation ( 9.3 for input port, tab.7 for output port) and
ETS 300 166
Bit rate
2,048 Mbit/s 50 ppm,
Code
HDB3,
Impedance
75 or 120 balanced,
Connector
SUB D HD female 44 pins supporting L907 cable (21 ports).
15
30
44
1
16
31

Page A1-12
1 - INSTALLATION
This interface uses two connectors : E1 INPUT connector for inputs (named RX) and
E1 OUTPUT connector for outputs (named TX).
Pin N
Ports
16
31
1
17
2
32
3
18
33
3
19
5
34
6
20
35
5
21
8
36
9
22
37
10
7
23
11
38
12
24
39
13
9
25
14
40
10
15
26
41
16
11
27
17
42
12
18
28
43
19
13
29
20
44
14
21
30
15
Signal name
Comments
GND
ground
TX(RX) 1B
Output (Input) 2 Mbit/s (hot point)
TX(RX) 1A
Output (input) 2 Mbit/s (cold point)
TX(RX) 2B
TX(RX) 2A
TX(RX) 3B
TX(RX) 3A
TX(RX) 4B
TX(RX) 4A
TX(RX) 5B
TX(RX) 5A
TX(RX) 6B
TX(RX) 6A
TX(RX) 7B
TX(RX) 7A
TX(RX) 8B
TX(RX) 8A
TX(RX) 9B
TX(RX) 9A
TX(RX) 10B
TX(RX) 10A
TX(RX) 11B
TX(RX) 11A
TX(RX) 12B
TX(RX) 12A
TX(RX) 13B
TX(RX) 13A
TX(RX) 14B
TX(RX) 14A
TX(RX) 15B
TX(RX) 15A
TX(RX) 16B
TX(RX) 16A
TX(RX) 17B
TX(RX) 17A
TX(RX) 18B
TX(RX) 18A
TX(RX) 19B
TX(RX) 19A
TX(RX) 20B
TX(RX) 20A
TX(RX) 21B
TX(RX) 21A
GND
Ground
NOTE : The shielding of the connector case is connected to the subrack front panel ground
Note : on each LTU, the Retiming function is supported by the #1 and #2 ports

Page A1-13
1 - INSTALLATION
1.3.2 - Connection to LTU3E3DS3 card
Figure 1-5 Front panel of LTU3E3DS3 card
"TR" and "REC" G.703 34 or 45 Mbit/s traffic ports :

Ports
75 ohms 34/45 Mbit/s Interface compliant to ITU-T G.703

( 11) Recommendation and ETS 300 166 allowing 34 Mbit/s or
45Mbit/s plesiochronous stream exclusive connection
Connector
1.0/2.3 75
1.3.3 - Connection to CCU-2G card
Power supply and

station alarm access
Remote signaling,
Remote control access
2MHz G.703
Synchronization access
Figure 1-6 : Front panel of CCU-2G card
The ADR2500 eXtra has three PSU cards.

It operates with one or two PSU cards if a backup power supply card is not present or when
replacing a faulty PSU card.
The ADR2500 eXtra can be supplied by a PAPA : power supply input is located on the CCU-2G
card.

Page A1-14
1 - INSTALLATION
1.3.3.1 - "POWER/ALM" connector
male connector
HE5 - 25 pins
Pin N
Signal name
-48V2
14
-48V2
15
-48V2 (not used)
16
-48V1
17
-48V1 (not used)
-48V1
-48V1
Audible minor alarm

18
6
19
Visual minor alarm

Audible major alarm
20
-48VS
21
Visual major alarm
-48VS (not used)
OB1
22
OB2
23
OB2
24
Shelf ground
25
Shelf ground
10
OB1
11
Shelf ground
12
NOTE
0BS
0BS (not used)
13
-48V2
Shelf ground
Shelf ground
: The connector shielding is connected to the equipment ground.

: OB is the logical "OR" of signals OB1 and OB2 of the power supply access.
Power supply interface :

Input voltage :
One or two - 48 V power supply sources, SELV type (Safety Extra

Low Voltage)
Operating voltage range : - 36 V to - 60 V
Maximum voltage range : - 36 V to - 72 V
Power :
260 W max. (see Chapter 4).

The audible and visual minor alarm outputs are interconnected just
like the audible and visual major alarm outputs.

Page A1-15
1 - INSTALLATION
PAPA connection cable (see diagram below) :

PAPA equipment side
male connector HE5 25 pins
ADR2500 eXtra side

Power/ALM 48V 13A max.
"Female" connector HE5 25 pins
Figure 1-7 : POWER/ALM power supply cable
Warning : As the shelf power supply connector is located on the CCU card, it is mandatory to
disconnect the powering cable from the POWER/ALM connector before CCU card extraction, to
prevent any risk of contact with hazardous voltages while manipulating the card.
1.3.3.2 - Remote signaling, remote control and station alarms access

: LOOPS"
Access
4 remote signaling inputs (Local user inputs) for floating contacts,

biased to - 48 VS internally, active in the closed state, with galvanic
insulation (loop current between 1 and 10 mA),
2 dry loop outputs (common, break and make) (Local user outputs)
used as station alarm or remote control
(maximum current = 100mA on resistive load).
M C B
(Schematic diagram of a dry loop)
female connector
8
15
1
9
HE5 - 15 pins

Page A1-16
1 - INSTALLATION
Pin N
1
Quad
Pair
Color
Signal name
In/Out
ALA2R
St
ALA2C
St
Vi
ALA2T
St
10
ALA1R
St
Bc
ALA1C
St
11
ALA1T
St
2
3
4
GND
12
TELE4B (OBs)
St
TELE4A
Et
TELE3B (OBs)
St
Vi
TELE3A
Et
14
TELE2B (OBs)
St
TELE2A
Et
15
TELE1B (OBs)
St
Vi
TELE1A
Et
13
6
7
8
Outgoing dry loop No. 2
Outgoing dry loop No. 1

Signal Ground
Remarks
Remote signaling loop No. 4

NOTE : The Quad, Pair and Color indications concern the 4-Quad cable L907 of the SAGEM
cable.
1.3.3.3 - 2 MHz G.703 sync access : "SYNC"

Access
2 external sync input interfaces operating at 2 MHz G.703 (T3) and

2 identical sync output interfaces operating at 2 MHz G.703 (T4),
comply with recommendation G.703 of ITU-T ( 13.3 and 13.4 for
input interface, tab.10 13.2 tab.11 and 13.4 for output table)
Impedance
120 balanced,
5
female connector
Pin N
1
6
Quad
Pair
HE5 9 pins (120 ).
GND
6
2
7
3
8
4
9
5
Signal name
Color
Remarks
Signal Ground
TX1 RING (T4-)
Output T4-1 (LO)
Bc
TX1 TIP (T4+)
Output T4-1 (HI)
Vi
RX2 TIP (T3+)
Input T3-2 (HI)
RX1 TIP (T3+)
Input T3-1 (HI)
RX1 RING (T3-)
Input T3-1 (LO)
RX2 RING (T3-)
Input T3-2 (LO)
Vi
TX2 RING (T4-)
Output T4-2(LO)
TX2 IP (T4+)
Output T4-2(HI)
NOTE : The connector shielding is connected to the electrical ground on the front panel.
The Quad, Pair and Color indications concern the two-Quad cable L907 of the cable supplied by
SAGEM.
The 75 ohm unbalanced interfaces are obtained by adding a cable which also provides BNC
connectors.

Page A1-17
1 - INSTALLATION
1.3.4 - Connection to CTRL-2G card

Major/critical and minor
alarm indicator LEDs for
the whole equipment
Card alarm indicator

LEDs (status, in service)
Alarm acknowledge button
SmartCard access
Management
Ethernet access
COMM access
Figure 1-8 : Front panel of CTRL-2G card
1.3.4.1 - Management access : "COMM" connector

Access
RS232, interconnection of a console or VT100 emulation
Rate
19200 bauds (8 data bits, no parity bit and 1 stop bit),
female connector
1
9
Pin N
Signal name
1
6
2
Remarks
DCD
Data Carrier Detect (Connected to DSR)
DSR
Data Set Ready (to DCE)*
RX
Data reception (to DCE)*
RTS
CTS
Clear To Send (to DCE)*
DTR
Data Terminal Ready (from DCE)*
TX
4
9
5
HE5 9 pins
RI
GND
Request To Send (from DCE)*

Data send (from DCE)*
Ring Indicator (not connected)

Signal Ground
* The ADR2500 eXtra is seen as a DCE.

Page A1-18
1 - INSTALLATION
COMM equipment side

male connector HE5 9 pins
VT100 or PC side
Female connector HE5 9 pins
Figure 1-9 : Comm connection cable
WARNING : Only use a straight cord, such as the one provided by SAGEM.
1.3.4.2 - Management access : "ETH" connector

Access
Ethernet management interface operating at 10 Mbit/s in halfduplex or full-duplex mode in accordance with mode used by party
(Ethernet port is dynamically adapted to each new connection of
the party),
If the Ethernet interface doesn't work, force the configuration
of the network card of the PC in duplex half mode.
Contact 1
Contact 8
RJ45 (10 base T) : front view
Connector
Pin N.
Signal name
TX_ETH_TIP
TX_ETH_RING
RX_ETH_TIP
4 and 5
NC
RX_ETH_RING
7 and 8
NC
Remarks
Ethernet output (HI)
Ethernet output (LO)
Ethernet input (HI)
BSTERM1
Ethernet input (LO)
BSTERM1
NOTE : Two indicator LEDs are associated to the "ETH" connector :

green indicator LED : traffic status indicator,
yellow indicator LED : link status indicator.

Page A1-19
1 - INSTALLATION
Cable for connection to an HUB (see diagram below).
ADR2500 eXtra Eth side

male shielded RJ45 connector with 8 pins
HUB side
Figure 1-10 : Straight-through Ethernet cable
Cable for direct connection to a PC (see diagram below).
ADR2500 eXtra Eth side

PC side
Figure 1-11 : Cross-over Ethernet cable

Page A1-20
1 - INSTALLATION
1.3.5 - Connection to AUX cards
Figure 1-12 : Front panel of AUX card

Each AUX card has three ports (6 ports in total with identical pin assignments)
E1 or F1 overhead bytes of STM-n tributaries or aggregates can be rerouted to these ports, for
order wire purposes for instance.
In addition, four internal connections can be created between E1 or between F1 bytes.
Connection of service channels :
Access
V.11 synchronous (differential)
Rate
64 kbit/s
8
female connector
Pin N
TA
(-)
10
TOFPB
(+)
TOFPA
(-)
RB
(+)
RA
(-)
11
4
12
5
13
6
14
7
15
Remarks
Not connected
TB
HE5 - 15 pins
Polarity
9
2
15
Signal name
(+)
Input, data to send on STM-n frame and sampled on rising edge

of clockT64 (B-A)
Output, transmit Octet Frame Pulse indicating position of bit 1
and transmitted on rising edge of clock T64 (B-A)
Output, data extracted from STM-n frame and transmitted on
falling edge of clock R64 (B-A)
ROFPB
(+)
ROFPA
(-)
Output, Receive Octet Frame Pulse indicating position of bit 1

and transmitted on falling edge of clock R64 (B-A)
R64B
(+)
Output, 64 kHz reception clock
R64A
(-)
T64B
(+)
T64A
(-)
Output, 64 kHz transmit clock

Not connected
Signal Ground
Cable for connection of V11 access to an ARDAX equipment or a VDS EOW300 equipment
(see diagram below).
Figure 1-13 : AUX/EOW connection cable

Page A1-21
1 - INSTALLATION
Timing diagram of "EOW/AUX"

synchronous operation) :
interface
in
counter-directional
mode
(64 kbit/s
T64 (B-A)
(Output, transmit clock)
T (B-A)
B8
B1
B2
B8
B1
B2
(Input, data to send)
TOFP (B-A)
(Output, transmit
byte sync)
R64 (B-A)
(Output, reception clock)
R (B-A)
(Output, received data)
ROFP (B-A)
(Output, reception frame
pulse)
1.3.6 - Connection to 3E3DS3FA card
Figure 1-14 Front panel of 3E3DS3FA card

"TR" and "REC" G.703 34 or 45 Mbit/s traffic ports :
Ports
75 ohms 34/45 Mbit/s Interface compliant to ITU-T G.703

( 11) Recommendation and ETS 300 166 allowing 34 Mbit/s or
45Mbit/s plesiochronous stream exclusive connection
Connector
1.0/2.3 75

Page A1-22
1 - INSTALLATION
1.3.7 - Connection to 63E1FA card
Figure 1-15 Front panel of 63E1FA card

"E1 INPUT" and "E1 OUTPUT" G.703 21x2 Mbit/s traffic ports :
ports
21 x 2 Mbit/s traffic ports compliant with the ITU-T G.703

Recommendation ( 9.3 for input port, tab.7 for output port) and
ETS 300 166
Bit rate
2,048 Mbit/s 50 ppm,
Code
HDB3,
Impedance
120 balanced,
Connector
SUB D HD female 44 pins supporting L907 cable (21 ports).

15
30
44
1
16
31
The E1 INPUT and E1 OUTPUT connectors and their connections are are identical to those of
the LTU21E1 card. (1.3.1)
Note : on the 63E1FA card the retiming function is supported by the ports #1 to #6
1.3.8 - Connection of optical STM-n access points
Figure 1-16 : Front panel of STM-1 interface card

Page A1-23
1 - INSTALLATION
All the access points are located on the front panel of the cards :
the STM-1 cards have 1 to 4 optical STM-1 interfaces
the STM-4 cards have 1 optical STM-4 interface
the STM-16 cards have 1 optical STM-16 interface
Each interface has a transmission access "TR" (Equipment output) and a reception access
"REC"( Input).
Remove the contact protection connector.
Connect the STM access points to the connectors on the front panel :
Transmission
TR connector
Reception
REC connector

Page A1-24
1 - INSTALLATION
"TR" and "REC" access points:

Single mode interfaces
Common characteristics
Standards
ITU-T G.957 and SFF-8472-Rev 9.5
Code
Uncoded (NRZ)
Optical fiber
single mode (1310 nm or 1550 nm, ITU-T G.652)
Connector
SC / PC (STM-n cards) or LC / PC (STM-n SFP cards)
SFP optical modules : Small Form factor Pluggable Transceiver MultiSource

Agreement 14 Sept 2000
Interfaces
S1.1
L1.1
L1.2
S4.1
L4.1
1310 nm
1310 nm
1550 nm
1310 nm
1310 nm
155,52 Mbit/s
155,52 Mbit/s
155,52 Mbit/s
622,08 Mbit/s
622,08 Mbit/s
20 ppm
20 ppm
20 ppm
20 ppm
20 ppm
0-12 dB
10-28 dB
10-28 dB
0-12 dB
10-24 dB
-15 to - 8 dBm
-5 to 0 dBm
-5 to 0 dBm
-15 to -8 dBm
-3 to + 2dBm
Sensitivity at 10
-28 dBm
-34 dBm
-34 dBm
-28 dBm
-28 dBm
Max. acceptable
power
-8 dBm
-10 dBm
-10 dBm
-8 dBm
-8 dBm
Typical range (*)
0 - 28 km
22 - 68 km
40 - 100 km
0 - 28 km
22 - 58 km
1 dB
1 dB
1 dB
1 dB
1 dB
L4.2
L16.1
L16.2
L16.2+ (1) (2)
U16.2 (3)
1550 nm
1310 nm
1550 nm
1550 nm
1550,92 nm
622,08 Mbit/s
2488,32 Mbit/s
2488,32 Mbit/s
2488,32 Mbit/s
2488,32 Mbit/s
20 ppm
20 ppm
20 ppm
20 ppm
20 ppm
10-24 dB
10-24 dB
10-24 dB
13-27 dB
25-39 dB
-3 to + 2dBm
-2 to +2 dBm
-2 to 2 dBm
+1 to +5 dBm
+14 to +17 dBm
Sensitivity at 10
-28 dBm
-27 dBm
-28 dBm
-28 dBm
-28 dBm
Max. acceptable
power
-8 dBm
-8 dBm
-8 dBm
-8 dBm
Typical range (*)
35 - 92 km
0** - 58 km
0** - 85 km
50 - 100 km
80 - 150 km
1 dB
1 dB
2 dB
2 dB
3 dB
Wave length
Rate
Guaranteed
attenuation
Transmit power
-10
Optical path penalty

Interfaces
Wave length
Rate
Guaranteed
attenuation
Transmit power
-10
Optical path penalty
-8 dBm
Table 1-2 : Characteristics of single mode interfaces

For the STM-16 cards, the optical fibers attached to the transmission laser and to the reception
photodiode are single mode devices with 10 micron core.
Page A1-25
1 - INSTALLATION
(*) The typical ranges suppose the use of normalized fibers adapted to the emission wavelength
and for the mentioned optic penalty. A previous measure of the optic balance is recommended
(**) 0 Km with optical attenuators if necessary
Note (1) : No wavelength multiplexing : use lasers with wavelength of 1550,92 nm 0,1 nm
With wavelength multiplexing : use lasers with following wavelengths : 1550,92 nm 0,1 nm,
1547,72 nm 0,1 nm, 1549,32 nm 0,1 nm, 1552,52 nm 0,1.nm
These interfaces must be used with MUX 10000 Unit (see Annex C).
Note (2) : If wavelength multiplexing is implemented, a 6dB attenuation for the optical
multiplexer/demultiplexer pair inserted on the line should be taken into account.
Note (3) : The U16.2 characteristics are given for a U16.2 card associated to the
OPTICAL BOOSTER + 14 DBM unit (see Annex B).
WARNING (1) : In case of higher ambient temperature, the radiator equipping the L16.2+ and
U16.2 interface cards can reach a temperature superior to 50C. This heat risk at the extraction of
the card is indicated by a sticker in front panel.
(2) : Input optical power > -8dBm may cause irreversible damage
For 0 km, use an appropriate attenuation patch cord or add-on attenuator
Warranty void if not properly used
Multimode interface
Interfaces
Standard
MM1
ANSI T1.646
Wavelength
1310 nm
155,52 Mbit/s
Rate
20 ppm
Code
Uncoded (NRZ),
Guaranteed attenuation
Transmit power
0 to 4 dB
-20 to -14dBm
-10
Sensitivity at 10
- 31 dBm
Max. acceptable power
-14 dBm
Typical range
0 2 km
Passband
500 MHz per km
Connector
SC/PC
Table 1-3 : Characteristics of multimode interface

Page A1-26
1 - INSTALLATION
1.3.9 - Connection of electrical STM-1 access points
Figure 1-19 : Front panel of 4ERE interface card

The 4ERE card has 4 electrical STM-1 interfaces : each interface has a transmission access
"TR" (equipment output) and a reception access "REC" (input).
"TR" and "REC" access points :

Rate
155,520 Mbit/s 20 ppm,
Standard
ITU-T G.703 15,
Code
CMI,
Electrical level
1V 0.1V peak-to-peak
Input attenuation
12.7 dB in f at 78MHz
Adaptation
15 dB between 8MHz and 240MHz
attenuation at input
Connector
1.0/2.3 75 ohms
WARNING :
Prior to any connection on the ERE card, be sure that the "male"
contact of the jumper is properly centered.
1.3.10 - Connection to GIG-E cards
Figure 1-20 : Front panel of GIG-E interface card

Page A1-27
1 - INSTALLATION
1.3.10.1 - Gigabit Ethernet access points

The GIG-E cards offer one or two optical Gigabit Ethernet interface on their front panel : each
interface has a transmission access "TR" (Equipment output) and a reception access "REC"
(Input).
Connect the Ethernet access points to the SC connectors on the front panel :
Transmission
TR connector
Reception
REC connector
"TR" and "REC" access points:

Interfaces
SX
LX
ZX
Interface
Multimode
Single mode
Single mode
Standard
IEEE 802.3z
IEEE 802.3z
No standard
Wavelength
770 - 860 nm
1270 1355 nm
1500 1580 nm
1250 Mbit/s
100 ppm
1250 Mbit/s
100 ppm
1250 Mbit/s
100 ppm
-9,5 dBm min

-9,5 dBm min
-11 dBm min

-11,5 dBm min
-11,5 dBm min
0 to 5 dBm
-
Sensitivity at 10
-17 dBm
-19 dBm
-21 dBm
Max. acceptable
power
0 dBm
-3 dBm
-3 dBm
500 m min
220 m min
5000 m min
550 m min
550 m min
40 km min
-
SC/PC
SC/PC
SC/PC
Rate
Transmit power
Fiber 10 m
Fiber 50 m
Fiber 62,5 m
-10
Typical range
Fiber 10 m
Fiber 50 m
Fiber 62,5 m
Connector
Table 1-4 : Characteristics of GigaEthernet interface
1.3.10.2 - Maintenance access : "RS232" connector
This is a private access for Sagem staff ; it is not usefull to users.

Page A1-28
1 - INSTALLATION
1.3.11 - Connection to xGE-DM cards
Figure 1-21 : Front panel of 2GE-DM interface card

Gigabit Ethernet access points
The xGE-DM cards offer one or two optical Gigabit Ethernet interface on their front panel : each
interface has a transmission access "TR" (Equipment output) and a reception access "REC"(
Input).
Connect the Ethernet access points to the SC connectors on the front panel :
Transmission
TR connector
Reception
REC connector
Interfaces
SX
LX
ZX
Interface
Multimode
Single mode
Single mode
Standard
IEEE 802.3z
IEEE 802.3z
No standard
Wavelength
770 - 860 nm
1270 1355 nm
1500 1580 nm
1250 Mbit/s
100 ppm
1250 Mbit/s
100 ppm
1250 Mbit/s
100 ppm
-9,5 dBm min

-9,5 dBm min
-11 dBm min

-11,5 dBm min
-11,5 dBm min
-5 to 0 dBm
-
Sensitivity at 10
-17 dBm
-19 dBm
-21 dBm
Max. acceptable
power
0 dBm
-3 dBm
-3 dBm
500 m min
220 m min
5000 m min
550 m min
550 m min
40 km min
-
LC/PC
LC/PC
LC/PC (2GE-DM-SFP)
SC/PC (xGE-DM-ZX)
Rate
Transmit power
Fiber 10 m
Fiber 50 m
Fiber 62,5 m
-10
Typical range
Fiber 10 m
Fiber 50 m
Fiber 62,5 m
Connector
Table 1-5 : Characteristics of GigaEthernet interface

Page A1-29
1 - INSTALLATION
1.3.12 - Connection to GFP150 eXtra card
Figure 1-22 : Front panel of GFP150 eXtra card
"ETH" Interface :
Port
Traffic Ethernet interface operating at 10 or 100 Mbit/s in halfduplex or full- duplex mode according to the mode used by the
interlocutor (validated or not autonegotiation),
The ADRGFP150 have a direct or a cross Ethernet interface depending on the configuration.
Every access supports the automatic inversion of pairs (MDIX auto) in order to avoid the
recourse to cross-over cables. However it is possible to force the type of cable by configuration.
Connector
Ethernet 10 or 100 BaseT Shielded RJ45 type.

Contact 1
Contact 8
Front view
Pin N
Signal name
Function
(direct interface)
Function
(cross interface)
TX_ETH_TIP
Ethernet output (hot point)
TX_ETH_RING
Ethernet output (cold point)
Ethernet input (hot point)

Ethernet input (cold point)
RX_ETH_TIP
Ethernet input (hot point)
Ethernet output (hot point)
NC
Reserved
Reserved
NC
Reserved
Reserved
RX_ETH_RING
Ethernet input (cold point)
Ethernet output (cold point)
7 and 8
NC
Reserved
Reserved
NOTE: Two LEDs are linked to the "ETH" interface:

Green LED : Link status indicator,
Yellow LED : Traffic status indicator.
The connection cables are identical those of the "ETH" management access of the CTRL-2G card
(see 1.3.4.2 Figure 1-10 and Figure 1-11)
The using and the working of the GFP150 extra card are described in the chapter 7.

Page A1-30
1 - INSTALLATION
1.4 - SHELF WITHOUT PDH PROTECTION

A new type of shelf, without PDH protection, is available from P2.4 release.
The difference with the other shelf is this one does not offer LTU connectors.
This shelf extends connectivity in a number of PDH access points with the 63E1FA and
3E3DS3FA cards and does not manage the 63E1, 3E3DS3, LTU21E120, LTU21E75 and
LTU3E3DS3 cards.
PSU-160
PSU-2G
CCU
CCU2G
PSU-160 PSU-160
PSU-2G PSU-2G
EXT 1
AUX
EXT 2
AUX
CTRL
CTRL2G
STM-1
STM-4
GFP150
eXtra
3E3DS3FA
63E1FA
xGE-DM
STM-1
STM-4
STM-16
GIG-E
xGE-DM
TRIB 1
TRIB 3
STM-1
STM-4
GFP150
eXtra
3E3DS3FA
63E1FA
xGE-DM
STM-1
STM-4
STM16
GIG-E
xGE-DM
STM-1
STM-4
63E1FA
3E3DS3FA
GFP150
eXtra
xGE-DM
TRIB 5
STM-1
STM-4
63E1FA
3E3DS3FA
GFP150
eXtra
xGE-DM
STM-1
STM-4
63E1FA
3E3DS3FA
GFP150
STM-16
STM-4
GIG-E
xGE-DM
SWITCH HO/LO
SW32HOLO
SWITCH HO/LO
SW32HOLO
eXtra
xGE-DM
TRIB 7
STM-1
STM-4
63E1FA
3E3DS3FA
GFP150
eXtra
xGE-DM
LINE 1
STM-16
STM-4
GIG-E
xGE-DM
FAN (FAN-2G)

Page A1-31
1 - INSTALLATION

Page A1-32
2 - COMMISSIONING AND OPERATION
2 COMMISSIONING AND OPERATION
2.1 - COMMISSIONING
The equipment can be commissioned and operated from a PC equipped with a VT100
emulation system and a Web Browser : the minimum configuration is defined in section 2.1.1
To access the equipment via the management function, a local terminal with VT100 emulation is
necessary the first time the equipment is commissioned : however, this will only enable the
parameter configurations required for the communication function (definition of equipment IP
address).
2.1.1 - Required configuration

The minimum configuration proposed for the operation PC is given below :
Description
Configuration 1
Processor
Configuration 2
Observations
450 MHz Pentium III
Memory
64 MB
Display
128 MB
1024x768
RS232 serial interface
SUB-D straight cable

9pts Male / Female
Ethernet 10 Base T network card
RJ45 crossed Ethernet

cable
Interfaces
Operating system
Windows NT4 / 2000
Windows XP
HyperTerminal for Windows

Softwares
1
Web Browser : Internet Explorer 5.5 (*)

Table 2-1 : Minimum configuration for operation PC
(*) The operating PC can be equipped with Internet Explorer 6.0 (delivered release with Windows XP).
Trademark of Microsoft Corporation

Page A2-1
LOCAL TEST
Equipment inventory
Check of - 48 V power supplies
Aggregate optical loopback
Insertion of communication parameters (VT100)
Time set and insertion of tributary accesses test configuration

(web browser)
Continuity check of tributary accesses
Redundancy check of - 48 V
Check of alarms and A / B loops

* case of
an under-equipped
Unit equipment
Local transmission test (30 min.) *
Optical connection
Connection of external synchronization input of

a "master" equipment (optional)
Preparation of configuration
no
Local test of last

equipment on network ?
yes
Link connection
Optical measurements
Reset of performance counters
24 H performance test on link
Operational equipment
(preparation of installation data package)
Backup of configuration
Figure 2-1 : Commissioning process for an ADR2500 eXtra network

Page A2-2
2.1.2 - Procedure
) On initial start-up, the equipment analyzes its constitution and takes this as the expected
configuration, under controlled service. It is therefore recommend to insert all the interface
cards before switching on the equipment in order to accelerate the commissioning procedure.
NOTES :
-
The initial commissioning procedure is normally carried out in factory.
If the four LEDs of the CTRL-2G card permanently flash, this means the card is passed
in degraded mode To go out of this degraded mode, see the chapter 6 "DEGRADED
MODE"
) Start up the power supply connected to the equipment.

) The equipment runs its selftests :
when the selftests are successful, the green indicator LED "STATUS" of the CTRL-2G
card lights permanent
if not successful, a flashing code defines the faulty selftest (contact the Hotline)
) Configure the IP address for the equipment using the VT100 (see 2.1.5)
) Using the web browser (see 2.1.6) :
Up to date the time and date of the equipment (Equipment > Date and time menu) if this
one is not managed by a NMS network manager. In presence of a NMS manager, the
updating is automatic
Configure the remote management ports using the web browser
) Connect the PDH 2, 34, 45 Mbit/s, STM-1, STM-4, STM-16, Ethernet, GigaEthernet, Fast
Ethernet and SYNC access points required in accordance with the equipment composition
) Connect the necessary AUX access points
) Download a predefined configuration or generate the required configuration using the web
browser :
Create the connections on the PDH , STM-n and GFP150 eXtra cards
Create the connections between the two GigaEthernet cards of the network. Select the
number of used VC4 on each card, then apply the configuration
Setup the required protection features (MSP, MS-SPRing, SNC, Cards protections, etc.)
Select the synchronization source and modify its parameters if necessary
Create the overhead byte traffic connections
If necessary, modify the monitoring parameters and the alarms configuration

The default configuration for the various parameters is given in 2.2.3
) Perform the STM-16 link tests observing the described process in procedure Figure 2-1 :
Commissioning process for an ADR2500 eXtra network

Page A2-3
) The equipment is now operational.

) The operation alarms may indicate an incorrect access points connection.
) Check the access points connection and the alarms corresponding to the connected access
points and correct any problems you may have detected.
) Back up the configuration.
NOTE : Once the commissioning procedure has been performed, connecting additional
access points (PDH, STM-1, STM-4, STM-16, GigaEthernet or Fast Ethernet) and inserting
or removing cards which are powered up is possible (with restriction for the PSU card : see
2.4.3.
2.1.3 - Description of communication function

With maximal configuration (if all tributaries are STM-1), the routing function enables
implementing 34 PPP interfaces.
34
PPP
Application
Management access
HTTP / SNMP
Operation protocols
1
ETH
Routing functions
Figure 2-2 : Communication function on an ADR2500 eXtra

Page A2-4
ADR155c
ETH
D1 D3
D4-D6
on STM16 West
HTTP / SNMP
IONOS NMS
The operating PC can be connected to

any Ethernet interface when the
parameter definitions enable reaching
an equipment to be operated
HTTP
/ SNMP
ADR2500 eXtra
PPP
D1 D3
on STM16 East
ETH
PPP
D1 D3
D4-D6
on STM16 East
D1 - D3 on STM1
ADR2500 eXtra
ETH
PPP
HTTP / SNMP
D1 D3
on STM16 West
R
Management
VC12 P1/P2
PPP
D1 D3
on STM16 West
Management
VC12 P1/P2
Other
equipment
PPP
D1 D3
on STM16 East
ETH
HTTP / SNMP
HTTP / SNMP
ETH
ADR 2500c
ADR2500 eXtra
Figure 2-3 : Example of communication on an ADR2500 eXtra, ADR 2500c, ADR155c and other
equipment network
To correctly operate, the application needs a unique address in the network (the addressing
rules are reviewed in Annex A and apply to the numbered interfaces).
The Ethernet port also needs an explicit address if operating. On the other hand, the PPI ports,
carried by the DCCs of the SDH links or by the management VC12, do not need to have an
explicit address, thus facilitating implementation of these and limiting the number of required
addresses.
Unnumbered type is thus selected in the screen : IP Parameters Interfaces
Configuration .
There are however certain cases in which explicit addressing of the PPP ports is required :
if the SDH link used is connected to an ADR 155c for releases P1 or P2, or to a FOT 155c
if two equipment are connected by more than one PPP link.
In these conditions, for proper operation, OSPF routing daemon should be used on these
interfaces, not RIP.
NOTE : The utilization of a management port of P type (P1 or P2) requires the utilization of two
resources VC12 at the level of the switching matrix, but one alone VC12 on the STM-n link.

Page A2-5
2.1.4 - Description of DCC transparency function

The transparency functionality of the DCC flows (D1-D3, D4-D6) allows to transport, in an ADR
network, the management flows in transparency of another operator by using the DCCr (D1-D3). The
management flows must be to the HDLC format.
In an heterogeneous network of ADR155c, ADR155CPE, ADR2500c or eXtra and no-ADR equipment :
the ADR equipment management is transported through the DCCm of the ADR and of the
management VC12 when they must cross a network of no-ADR.
the no-ADR management is transported through the DCCr of the ADR when they must cross a
network of ADR.
The DCCm of ADR155c and of ADR155CPE are not compatible with those of ADR2500 eXtra ; their
rates are diffrent.
The transparency of the DCC is independent of the protection mechanisms. The operator must use a
mechanism of routage to protect its path of DCC.
The transparency of the DCCr and DCCr is only configurable by HTTP and is always bi-directional
The system of transparency does not go up alarm or information on the state of the transported flow.

Page A2-6
2.1.5 - Defining parameters for IP address and Ethernet port

) Connect the "COMM" access to a free "COM" port on the PC with VT100 emulation.
) Switch on the PC.
) If it is the first time you have run the HyperTerminal application on this PC, process as
following :
successively select, in the Windows desktop, the Start, Programs, Accessories and
Hyperterminal buttons
select the icon representing the Hyperterminal application : a description window for the
application is displayed
enter a name and choose an icon for the connection, then validate your choices : a new
window is displayed
select the "COM" port on the PC which is connected to the equipment then validate your
choice. A new window is displayed
configure the port parameters as indicated below :

Bits per second
: 19200
Data bits
:8
Parity
: none
Stop bits
:1
Flow control
: none
validate the programming.
save the connection ("Save" command in application File menu).
NOTE : The next time you want to open the "Hyperterminal" application, you will simply
need to choose the connection icon to connect to the equipment. Once the equipment is
powered up, the operation menu is displayed.
to exit the "Hyperterminal" application, select Exit in the File menu.
) Open a session and enter your password (to configure the communication function, it is
necessary to have "supervisor" rights)
NOTE : by default, for the initial commissioning procedure, the password is empty.

Page A2-7
The following screen is displayed :
To select a command, type the command number in the "Choice ?" text area and press the
"ENTER" key to validate your choice.
> Choice "1" : Configuration of equipment IP address.
The IP address must be different from that of the other equipment and must be defined in a
different subnetwork of the one of the Ethernet.
The default value 000.000.000.000 corresponds to no configuration of the IP address.
When the IP address exists and is modified, equipment REBOOT is proposed. This
REBOOT operates itself without affecting the trafic.
Page A2-8
Error message "Equipment address is mandatory" : the equipment address is mandatory

when at least one PPP link is not numbered.
> Choice "2" : Configuration of Ethernet interface.
The above screen presents an Ethernet communication interface with its characteristics :
"Interface State" : choice of interface state : 0 (Interface off) or 1 (Interface on).
"IP Address" : IP address (default adress : 135.10.114.11)
"Subnet mask" : sub-network mask.
"Route Protocol" : protocol : 0 (None), 1 (RIP) or 2 (OSPF)
The addresses of the gateway and no gateway equipment must be defined in different
subnetworks.
When the IP address exists and is modified, equipment REBOOT is proposed. This
REBOOT operates itself without affecting the trafic.
> Choice "3" : choice of equipment REBOOT.
This command is used to immediately reboot the application and restart with the parameters
already stored in the equipment.
This REBOOT is performed with no impact on the traffic.
> Choice "4" : Logout / Disconnection
Once the parameter definition process is completed, this command closes the current
session.
An automatic session exit is performed after a few minutes if no activity is detected (this time
period can be configured using the manager).

Page A2-9
> Choice "5" : Ping.
"IP Address" : Choice of IP address of equipment to be contacted.

Round trip time in ms
NOTE : The Ping command is used to check the accessibility and the return path from the
remote equipment by testing both the address of the interface and the address of this
equipment. If the address of the port by which the Ping command is generated is different
from the address of the equipment, two commands are generated.
> Choice "6" : Trace route.
"IP Address" : choice of IP address of equipment to be contacted.

Page A2-10
The screen displays the management routes already defined with their characteristics :
Hops : hop 1, 2, 3Path to go from one machine to another.
IP address : IP address of recipient (equipment or sub-network).
Delay (ms) : round trip time.
Unit. size : Maximum size of IP packet which can reach to the remote equipment.
2.1.6 - Using the Web browser

2.1.6.1 - Browser configuration
IE 5.5 and IE 6.0 configurations
1.
In the Internet Explorer Tools menu, click Internet options.
2.
In the General tab, click Parameters.
3.
Tick the radio button : On each page visit, then define the disk space to be used for
1 Mbyte. Click [OK].
4.
In the Temporary Internet files tab, click Delete Files.
5.
Tick Delete all offline content, then click [OK].
6.
In the Internet options dialog box, click [OK], then close the IE browser to allow the options
to be acknowledged.
The Automatic cache option with a disk space of 30 Mbytes provides for much faster operation
to display the pages.
With IE 6. 0, it is possible to configure the level of confidentiality, that is to say the choice of the
cookies type that is allowed to copy on the target PC. To open the ADRs, it is necessary to let
the parameter of confidentiality of Internet to the default value "Medium" for the access to the
Web sites.
With IE6. 0 and a PC equipped of Windows XP SP2, the installed Center of Security modifies
the manner of which IE displays the HTTP windows. In order to correctly open an ADR, it is
necessary to untick the parameter "Block pop-ups" of the tab " Privacy" of IE properties .
In the same way, the installed Center of Security blocks the program Tftpd32 used by the ADRs
for the Upload and the Download. On the warning window , to click on the button "Unblock" : this
action adds the program tftpd32 in the list of exceptions.
Page A2-11
Remark
After an upgrade (application code + HTTP custom), the cache must be cleared as following :
In the Internet Explorer "Tools" menu click "Internet Options / General tab / Temporary Internet
files tab / Delete Files"
Tick "Delete all offline content", then click "OK".
Then close and start again the Browser.
PC Configuration
To get a correct date for the equipment HTTP, the environment variable "TZ" must not be
defined. To list all environment variables, type "Set" in the MS DOS console.
Otherwise, to get a correct display of HTML pages, fonts must not be defined as "large" in
display properties of the configuration panel and the Webdings police must be installed.
2.1.6.2 - Initial commissioning

The PC is connected via the Ethernet (the PC's gateway must be in the same subnetwork as the
Ethernet interface of the ADR).
1.
Run the INTERNET EXPLORER 5.5 or 6.0 application.
2.
In the Address field of the home screen, enter the IP address for the ADR2500 eXtra
equipment, the browser home screen is displayed : Welcome on the ADR2500 eXtra's site.
3.
On initial commissioning, the password is empty. Click on [Apply] to access the screen :
ADR2500 eXtra shelf view.
The web browser is now operational.
2.1.6.3 - Menus tree

See following Figure 2-4 : Menus tree

Page A2-12

DS
Main Menu
Session
Synchronization
Connection
Aux
Current Alarms
Information
Login
Logout
T0
T4
Configuration
Delete
Multiple connections
HO Level
LO Level
LPOM List
Configuration
New Windows
Polling
Name
Date and Time
Inventories
Security
Management
Upload Download
Failure hold off/on time
WTR
Event Logs
Performance
Delete
"EMPTY" Menu
"FAN-2G" Menu
"PSU" Menu
"EXT AUX" Menu
Monitoring
Service
Expected Card
Monitoring
Alarms
Board status
Maintenance
Monitoring
Expected Card
Monitoring
Service
Expected card
Board status
AUX
Board status
Board status
"LTU21E1" Menu
Shelf view / Equipment
Capabilities
"LTU3E3DS3" Menu
Maintenance
Monitoring
Service
Expected Card
Board status
Maintenance
Monitoring
Service
Expected Card
Board status
1/2/3 TR REC
E3/DS3
E1 ports
"CCU-2G" Menu
"CTRL-2G" Menu
Board status
Alarms
Loops
Synchronization
Monitoring
Board status
IP Parameters
DCC Connection
"SWITCH HO/LO" Menu

Maintenance
Monitoring
Service
Expected Card
Board Status
TC List
TC Performance
"TRIB 63E1" Menu
"TRIB 3E3DS3" Menu
"TRIB STM1" Menu
"TRIB or Line STM4" Menu
"TRIB or LINE STM16" Menu
Monitoring
Service
Expected Card
Performance
Board status
PDH Board Protection (*)
LPT (**)
Monitoring
Service
Expected Card
Performance
Board status
PDH Board Protection (*)
Maintenance
Monitoring
Service
Expected Card
Performance
Board status
1 TR REC
2 TR REC
3 TR REC
4 TR REC
Maintenance
Monitoring
Service
Expected Card
Performance
Board status
TR REC
Maintenance
Monitoring
Service
Expected Card
Performance
Board status
LPT (**)
E1 Retiming (**)
TR REC
"TR REC" Menu

"TRIB or LINE GIG-E" Menu
"TRIB 63E1FA" Menu
"TRIB 3E3DS3FA" Menu
Monitoring
Service
Expected Card
Performance
Board status
TR REC
Settings
Maintenance
Monitoring
Service
Expected Card
Performance
Board status
E1 Ports
E1 Retiming
Maintenance
Monitoring
Service
Expected Card
Performance
Board status
1/2/3 TR REC
E3/DS3
SFP
SPI / RST / MST
MSP / MS-SPRing
MSA / HPT /HPOM
HPA / LPOM
"TRIB ou LINE xGE-DM

Menu "
Monitoring
Service
Expected Card
Performance
Board status
SFP
(on SFP card)
ETH
VCG
HPT
"TR REC" Menu

WAN
HPT
VCG
GFP
Access
(*) If the card is inserted in TRIB 1

(3E3DS3) or TRB 2 (63E1)
(**) If the card is configured in working
mode
SFP block for STMn-SFP cards

"MS-SPRing" block accessible if
selected and for STM16 card in
" Line" slot
" TRIB GFP150 eXtra"

Menu
Monitoring
Service
Expected Card
Performance
Board status
Global Params
ETH
Switch
VCG
LPT
OAM CC
MSTP
Figure 2-4 : Menus tree

Page A2-13
2.1.6.4 - Presentation of the Graphical User Interface

When a session is opened on the web browser, the "Shelf view" screen (
Figure 2-5) is displayed with a general view of the equipment, in which each slot is marked with
its name in bottom (left for FAN-2G ) : LTU x-y, PSU 1-2-3, CCU, CTRL, EXT 1-2, TRIB 1-8,
LINE 1-2, SWITCH 1-2, FAN.
Click on "LTU" to visualize the LTU strip, click on "Shelf" to visualize the cards of the shelf.
Figure 2-5 : Shelf view screen of web browser

Page A2-14
This screen is used to display the status of the equipment, in particular :
the inconsistencies between configuration and composition, the card status ; each slot
displays an info bubble including
- the name of the expected card : always present information
- the card status : present information if default card (board missing, board mismatch,
defective board)
- the name of the inserted card : present information if the inserted card in the shelf is
different of the one programmed on the GUI
each card presents on bottom an horizontal border (vertical border on left for FAN-2G)
which is colored grey if the card is not monitored, red in case of insertion alarm (Missing,
Mismatch, Defective). For FAN-2G, the coloration can also reflects the state of the alarms
card.
the connectors in the modules with a critical alarm condition are colored according to the
severity of the most serious alarm.
the present and configured out of service modules include an icon representing a red X to
indicate this administrative status
the present and configured on maintenance modules include an icon representing a

caution to indicate this administrative status
the "Status" and "Traffic" LEDs of the cards, and the "ALM" LEDs of the CTRL-2G card are
dynamic devices.
Their meaning is specified to 2.2.3.4 :
The MSP, MS-SPRing and PDH Cards protections, the TC connections are indicated on
labels of information that appear then on the concerned cards.
This screen is also used to :
have informations on the session :

- red information of "No Session" and "Login" link
- opened grey padlock if the writing session is not locked, closed red if the writing session
is locked by another user, closed green if the writing session is locked the user.
navigate using the info bubble buttons "Refresh", "Stop", "Previous", "Next"
reach help using the info bubble button"Help"
visualize the release and the current packs using the info bubble button"About"
at any moment return on the "Shelf view" screen using the info bubble icon "Shelf view"
display the "Equipment" menu and its items on the left of the screen, at the same time that
the visualization of the shelf
activate the common functions of the equipment (such as synchronization, security, traffic
information, etc.) by clicking on a function on the main menu bar located above the
equipment view. This opens a sub-menu on the left of the screen :
see Figure 2-4 : Menus Tree

Page A2-15
access the functions related to a specific module (for example, MS-SPRing protection
function in the case of a line STM-16 module) : by clicking on the module to be selected, its
specific menu appears on the left of the screen according to the type of card :
see Figure 2-4 : Menus Tree
display the characteristics specific to an access (connections made, connection

configuration, status of alarms, etc.) by selecting the corresponding connector.
For each displayed function, the configuration parameters, operating controls, active parameters
and status of the alarms are grouped on the same screen ; the various possible actions are
accessible (or not) to the operator depending on the operator's authorization level.
The browser window heading indicates the equipment name, its IP address and the granted
authorization level.
A mini view, located on the right top of the screen, indicates the cards which present alarms :
- colored grey slot : no monitored
- colored light yellow slot : warning alarm
- colored yellow slot : minor alarm
- colored red slot : major alarm
- colored magenta slot : magenta alarm
- colored white slot : monitored slot and no alarm
When a slot is colored on this mini view, click on the info bubble button "Refresh" to make appear
the alarm's indications on the Equipment shelf view
This mini view is automatically refreshed according to a defined frequency in the "Polling" menu.

Page A2-16
2.2 - OPERATION
2.2.1 - Functional description

The ADR2500 eXtra is an STM-16 optical add-drop multiplexer used to build STM-16 point-topoint links, STM-16 rings or meshed networks.
The ADR2500 eXtra can also be connected to an equipment of the synchronous digital hierarchy
complying with G.707 and G.783 recommendations of ITU-T standard.
The ADR2500 eXtra modelling into functional blocks according to G.783 standard is as following :
SFP : Small Form Factor Pluggable
SPI : Synchronous Physical Interface

RST : Regenerator Section Termination
OHA : OverHead Access
MST : Multiplex Section Termination
MSP : Multiplex Section Protection
SETS : Synchronous Equipment

Timing Source
MS-SPRing on two fibers
SETPI : Synchronous Equipment

synchronization Physical Interface
MSA : Multiplex Section Adaptation
SEMF : Synchronous Equipment

Management Function
HPOM : High order Path Overhead Monitoring
MCF : Message Communication

Function
HPC : High order Path Connection

HPT : High order Path Ternination
HPA : High order Path Adaptation
LUG : Lower order path Unequipped Generator
GFP - Frame
LPOM : Lower order Path Overhead Monitor
VCAT
LPC Lower order Path Connection
LCAS
LPT : Lower order Path Ternination

LPA : Lower order Path Adaptation
(VC12)
Lower order Path Adaptation

(VC3)
PPI : Plesiochronous Physical

Interface (VC12)
Plesiochronous Physical
Interface (VC3)
Table 2-2 : Functional blocks of ADR2500 eXtra
2.2.2 - General information

Operation and maintenance of the ADR2500 eXtra is performed :
either directly on the equipment, by means of the front panel indicator LEDs and of the two
technical management outgoing loops (A and B loops),
or, using a PC equipped with a web browser,

Page A2-17
or, from a network manager using the SNMP protocol for the network and supervision
aspects, and the included web browser.
The IONOS-NMS management software provides an efficient and comprehensive network

administration solution for SAGEM systems ADR 155C, ADR155CPE, ADR 2500c and
ADR2500 eXtra (refer to IONOS-NMS installation and user guide).
The equipment management functions (EMS) are developed at network administration level
(NML) in accordance with the telecommunications network architecture (TMN) :
point-to-point trail configuration,
management of alarms appearing on links,
management of protection systems : MSP, MS-SPRing (only for ADR 2500c and ADR2500
eXtra), SNC-P.
2.2.3 - Operation parameters

The operation parameters comprise :
the configuration parameters,
the maintenance commands or operations (these actions are cleared in case of power
supply loss)
the alarms and their severity level.
Configuration parameters
The enclosed tables (Tables 2-3 to 2-5 : Network configuration parameters and Tables 2-6 to
2-25 : Equipment configuration parameters show the configuration functions.
The "Access and Parameter Path" column indicates :
the access paths (in bold italic) from the main menu functions (Figure 2-4 : Menus tree) or
from the selected card in the equipment view (
Figure 2-5 : Shelf view screen of web browser)
Ex : Connection menu > Output port > Configuration or Multiple Connections
The parameters to be defined, (bold between quotes) :
Ex : "Login" in Session menu
Configuration constraints
When configuring the name (Equipment > Name menu), you are limited to using upper and lower
case characters, numbers, the space and the and _ characters.
Accented characters and certain special characters will not be displayed on the VT100 interface.
The configuration downloads on the equipment (download all database) must be realized only
with absence of default on the equipment, without switched protection. If the MS-SPRing
protection is set on the equipment, this restraint is expanded to the absence of default or forced
operation on the STM-16 ring.

Page A2-18
2.2.3.1 - Network Configuration Parameters
Configuration
Connection
Protection
Wording
Connection matrix
(SWITCH HO/LO card,
HPC, LPC)
Ring protection
mechanisms
SNC protection
Access paths and parameters
Default value
Menu : Connection > Output port > Configuration or Multiple

No connection
Connections
"VC Type" or "VC-n type" type, unidirectional or bi-directional
Connections of VC12, VC3 LO, VC4, VC4-4c, VC4-16c HO
"Input Port" or "First Input Port"
The dropdown list depends on the declared cards in the shelf.
"Name"
Identifications of the connection
"Activate TC" and "TC Configuration" link
to set connections and parameters associated to TCM function
Menu : Connection > Output port > Configuration
None
No ticked
Usable on a remote
connection
Non in service
Protection of VC12, VC3, VC4, VC4-4c, VC4-16c paths

"Status" : traffic status.
Protection status reading (channel used, cause of switchover)
"Revertive"
Reversibility authorization for each path : return, after a WTR period, to
No
normal link when fault (SF or SD) has disappeared
"WTR"
WTR period (Wait Time to Restore) : in "Revertive" mode, waiting time for 60 s
return to normal link.
WTR programmable value for each path from 30 to 900 s in 1s steps
Hold Off Time
Persistence value programmable for each path from 0 to 10 s in 1/10 s
0 ms
steps.
For SNC/N, take account of the SD created by the end of the SF.
Table 2-3 : Network configuration parameters

Page A2-19
Configuration
Wording
MS-SPRing protection
on optical STM-16 line

"SNC Type" :
* SNC/I : the protection criteria are tu-lop and tu-ais for VC12/VC3,
au-lop and au-ais for VC4)
* SNC/N : SNC/I + SD criteria only :
HO SD (VC4 B3) for VC4,
LO SD (VC3 B3) for VC3,
LO SD (V5) for VC12,
Other criteria are not supplied).
For VC12 and VC3 the number of SNC/N is limited to 28.
"Protection Input Port"
Definition of the assistance port
The dropdown list depends on the declared cards in the shelf
"Operation"
Operator action by path and by order of priority :
Clear (Forced operation cancel),
Lockout of protection,
Forced Switch to Working,
Forced Switch to Protection,
Manual Switch to Working,
Manual Switch to Protection
Swap SNC : swap the working and protection input ports
Card menu : LINE 1 and 2 > TR REC > MSP/MS-SPRing > MS-SPRing
Default value
SNC/I
No protection
Clear
MS-SPRing
Activation or not
Off
"NE ID"
Identification number ; values : none, 0 to 15
None
"WTR"
WTR period (Wait Time to Restore) : in "Revertive" mode, waiting time for 300 s
return to normal link
Configurable value from 30 to 900s in 1s steps

Page A2-20
Configuration
Wording

Multiple Ring Switch Handling
Type of operation.
Not selected : single fault ; Selected : double fault
"Operation" West and East
Operator command by order of priority :
Clear (Forced operation cancel),
Forced Switch,
Manual Switch
"Fault"
Alarms related to MS-SPRing
"Status"
Status of traffic on ring (normal/protection)
"Node Configuration"
Configuration of the identification N ; values : none, 0 to 15.
"Topology map"
16 elements topology map with values : none, 0 to 15
"Misconnection map"
Signal cancellation map with (topological) addresses of nodes in which
AU4 traffic (passing through a time interval) enters and exits the ring.
Values : none, 0 to 15
"Nut map"
8 elements map that identifies the configured AUs as Non-preemptible
Unprotected traffic.
Default value
No selected
Clear
None
None
None
Disable

Page A2-21
2.2.3.2 - Equipment Configuration Parameters
Configuration
Shelf
configuration
Wording
Equipment choice
Configuration of
equipment name

Menu : Equipment > Name
Configuration of
Menu : Equipment > Date and time
equipment date and time
Equipment Date and Time by applying PC Date and Time
Reading hardware
inventories of inserted
sub-assemblies
Reading software
inventories of inserted
sub-assemblies
Menu Equipment > Inventories > Hardware

Menu: Equipment > Inventories > Software
Current application codes and FPGA
Menu : Equipment > Upload/Download
Backup and
downloading
Backup all configuration
Backup "Shelf"
configuration
Backup "Network"
configuration
Upload > All Database (type of uploaded information)

Backup of all equipment configuration (Shelf + Network + Management)
Upload > Shelf database (type of uploaded informations
Backup of shelf configuration (cards, alarms, performances, connections,
protection, synchronization)
Upload > Network Database (type of uploaded informations)
Backup of management network parameters (PPP, IP address, routing
Protocols)
Table 2-6 : Equipment configuration parameters

Page A2-22
Default value
None
DD/MM/YYYY hh:mn:ss
Configuration
Wording
Backup "Management"
configuration
Download all
configuration
Download "Shelf"
configuration
Download "Network"
configuration
Download
"Management"
configuration
Download codes and
customization of
equipment except those
of GIG-E and GFP150
eXtra cards
Download codes of
GIG-E cards

Upload > Management Database (type of uploaded informations)
Backup of parameters required by management
(list of managers, trap recipients, etc.)
Download > All Database (type of downloaded informations)
Restoration of all equipment configuration (Shelf + Network +
Management).
Download > Shelf database (type of downloaded informations)
Restoration of shelf configuration (cards, alarms, performances,
connections, protection, synchronization)
Download > Network database (type of downloaded informations)
Restoration of management network parameters (PPP, IP address,
routing protocols)
Download > Management database (type of downloaded informations)
Restoration of parameters required by management (list of Managers,
trap recipients)
Download > Shelf Pack (type of downloaded informations)
Download of whole codes in reserve bank in flash (Software, FPGA,
customization) forf all the cards which can be found in the equipment
except GIG-E and GFP150 eXtra .
The current codes are saved in current banque in flash. Switchover to
downloaded new codes takes place following a manual command by
operator.
Download > GIG-E Pack (type of downloaded informations)
Download of whole codes (Software, FPGA) of GIG-E card in reserve
bank in flash.
downloaded new code takes place following a manual command by
operator.
Default value

Page A2-23
Configuration
Wording
Download codes of
GFP150 eXtra cards
Apply default
configuration
Switchover on reserve
codes
Switchover on reserve
codes and application
IP addressing
Alarms
Interfaces
Routing table
Global Parameters
Interfaces Configuration
Static Routes
Configuration

Download > GFP150-eXtra Pack (type of downloaded informations)
Download of whole codes (Software, FPGA) of GFP150 eXtra card in
reserve bank in flash.
downloaded new code takes place following a manual command by
operator.
Switching > Take effect
Default Configuration : application of default configurations (severities
and monitoring alarms, quality thresholds) on all equipment
Switching > Switch (Next card reset will apply selected version)
GIG-E Pack : Switchover to GIG-E reserve code
GFP150-eXtra Pack : Switchover to GFP150 eXtra reserve code
Switching > Switch and reset
Shelf Pack : Switchover to equipment reserve codes then application by
reset
GIG-E Pack_ :
Switchover to GIG-E reserve codes then application by reset
GFP150-eXtra Pack_ :
Switchover to GFP150 eXtra reserve codes then application by reset
Menu : CTRL-2G card > IP Parameters
Used to configure monitoring and severity of management interface
alarms.
Summary of management interface configurations (Eth and PPP)
Reading of Ethernet port information
Reading of STM-n / DCCr / DCCm / VC12 port information
Summary of routing tables
Equipment management IP address
RIP routing
OSPF
PPP interfaces configuration
Equipment static routes configuration

Page A2-24
Default value
Eth : minor
PPP : minor
@ ETH : 135.10.114.11
0.0.0.0
0
1
Configuration
Synchronization
Wording
Synchronization sources Menu : Synchronization
and propagation
configuration
T0 Synchronization
"Name"
T3_1
T3_2
T2_LTU x:y (maximum 1 T2 by 63E1 card)
T2_LTU x:y (maximum 1 T2 by 63E1 card)
T2_TRIB x:y (maximum 1 T2 by 63E1FA card)
T2_TRIB x:y (maximum 1 T2 by 63E1FA card)
T1_TRIB x:y
T1_TRIB x:y
T1_LINE 1
T1_LINE 2
"SSm" (Synchronization Status Message)
Use of synchronization status messages
"Quality provided" (when "SSM" is "false")
Quality level of potential sources :
PRC (Primary Reference Clock),
SSUT (Synchronization Supply Unit Transit),
SSUL (Synchronization Supply Unit Local),
SEC (Synchronization Equipment Clock),
DNU (Do Not Use)
Default value
True
T3_1 = PRC
T3_2 = PRC
T2_LTU x:y = SEC
T2_LTU x:y = SEC
T1_LINE 1:1 =SEC
T1_LINE 2:1 = SEC
T1_TRIB x:y = SEC
T1_TRIB x:y = SEC
"T0 priority"
Priority table of T0 according to sources declared.
Possible values from P1 to P8 and disable (dis).
Possible sources :
2 sources T1 extracted from incoming tributary access points STM-1,
STM-4, STM-16
2 sources T1 extracted from incoming line access points STM-16
2 sources T2 extracted from 2 Mbit/s incoming access points
2 sources T3, external, 2MHz G.703
T3_1 = p1
T3_2 = dis
T2_LTU x:y = dis
T2_LTU x:y = dis
T1_LINE 1:1 = p2
T1_LINE 2:1 = p3
T1_TRIB x:y = dis
T1_TRIB x:y = dis

Page A2-25
Configuration
Wording

"LOS Severity"
Alarm severity associated to the source status .
Default value
Warning for T1_Line,
T1_Trib and T2
Minor for T3
T0 Synchronization
Holdover in case of automatic mode and no valid source
"Mode"
Synchronization operating mode.
Choice between "Automatic" and "Free-run"
"Command"
Operator action : manual switchover, forced operation or clear to be
configured
"Revert"
Reversibility authorization common to all sources : return, after a WTR, to
normal link when default (SF or SD) causing switchover has disappeared.
"WTR"
WTR period (Wait Time to Restore) : in "Revert" mode, waiting time for
return to normal link. Common value to all programmable sources from
30 to 900 s in 1s steps
"Sync Freq Out of Range Severity
Alarm severity associated to the T0 output frequency
T4 Synchronization
"Active source"
Selected source : None, T0 and each T1 source
"Minimum Quality"
Quality threshold for T4. Choice between :
PRC (Primary Reference Clock),
SSUT (Synchronization Supply Unit Transit),
SSUL (Synchronization Supply Unit Local),
SEC (Synchronization Equipment Clock)

Page A2-26
Automatic
Clear
True
60 sec
Minor
None
PRC
Configuration
Cards
configuration
Wording
Declaration of cards
presence and card type
by slot
Card monitoring
Disconnection of a card
SFP modules
34 or 45 Mbit/s Port
Default value
"Sase"
Mode control : activation / deactivation ;
If activation : choice of T3 source between T3_1 and T3_2
"LOS T4 Severity"
Alarm severity associated to the T4 output status.
Card menu > Expected card : declaration of status of LTU, SWITCH,
LINE, TRIB, AUX, PSU slots. A slot can be configured empty or with an
expected card
Card menu > Monitoring
A non-monitored card is made grey in the equipment view. When a card
is not monitored, all relative events to the alarms on the card (card and
access points) are inhibited. The performance data is logged whatever
the configured monitoring mode.
Card menu > Service
The disconnected module is ignored by the management function. The
configuration modifications requested are stored but are not implemented.
Card menu : STM-n SFP > TR REC > SFP >"Expected SFP"
Card menu : 2GE-DM SFP > SFP >"Expected SFP"
Choice of the expected SFP module
Card menu LTUE3DS3 or 3E3DS3FA > E3/DS3
"E3 (34M)" or "DS3 (45M)"
34 or 45 Mbit/s physical interface selection
"Type of cable" (DS3/45Mbit/s mode only
"long" or "short" (length < 225 ft or 70m)
Connecting cable length selection so that transmitted pulse complies to
template defined in Bellcore GR-489-CORE standard
False
T3_1
Minor
EMPTY
Monitoring
In service
EMPTY
"E3 (34M)"
"short"

Page A2-27
Configuration
Protection
Wording
E1 Retiming

Card menu : 63E1 or 63E1FA > E1 Retiming
Selection of the retiming function :
- on the first and the second ports of each LTU associated with a 63E1
card
- on the #1 to # 6 ports of each 63E1FA card
(maximum 6 E1 retiming functions by 63E1 or 63E1FA card)
MSP(*)
Card menu : LINE or TRIB > TR REC > MSP/MS-SPRing > MSP
optical or electrical STMn access points
Type "1+0" or "1+1"
"Ports MSP type"
Choice between Working (normal) and Protection (backup) for the
selected port
"Ports MSP Complment"
Definition of the complementary port of the MSP couple
"Revertive"
Reversibility authorization : return, after a WTR, to the normal link when
the fault (SF or SD) which caused the switchover has disappeared.
Choice between Yes and No
"Mode"
Protection mode. Choice between unidirectional or bi-directional
"WTR"
return to normal link. Common value to all programmable sources from
30 to 900 s in 1s steps
"Hold off time"
Persistence value, configurable from 0 to 10 s in 1/10s steps
Default value
Disable
1+0 : non activated
Yes
Bidir.
900 sec
0s

(*) In case of a MSP protection created on STM-16 LINE interfaces, two PPP links (one per port) need to be created.
In case of a MSP protection created on STM-n TRIB interfaces, one PPP link is needed, created on the Working port.

Page A2-28
Configuration
Wording
WTR Configuration
PDH cards
Protection configuration

"Sf / Sd priority"
Value "High-G783" or "Low"
"Operation"
Operator command by order of priority :
Clear (Cancel forced operation),
Lockout of protection,
Forced switch to Working,
Forced switch to Protection,
Manual switch to Working,
Manual switch to Protection
"Fault"
Alarms related to MSP
"Status"
Traffic status
Menu Equipment > WTR
return to normal link. Programmable value from 30 to 900 s in 1s steps
Global MSP WTR : Default configuration of the WTR for all the MSP
protections
Global SNC WTR : Default configuration of the WTR for all the SNC
protections
Card menu : TRIB 1-2 > PDH Board Protection
Default value
Low
Clear
900s
60s
"No Protection" : the PDH card is used in working mode and the LTU
"No Protection"
window allows to associate it at a free LTU card
"1:n" : the PDH card is used in protection mode and the "Board to
Protect" windows allow to configure the cards to be protected (maximun 4
cards in TRIB 5 to TRIB 8)

Page A2-29
Configuration
Service channel
Wording
Order Wire E1
Auxiliary channel F1
DCC
Transparency
Loops
Power supply

"Operation"
Operator commands :
Clear (Cancel forced operation),
Lockout of protection (protection is forbidden),
Forced Switch TRIB x to Protection (Traffic is routed on Protection card),
Manual Switch to Working (Manual switching of traffic on working card).
Card menu : EXT > AUX > Output port > Configuration
"Type" : Choice between "E1" and "F1"
4 terminations max. and 6 outputs (E1 or F1), contra-directional master
"Input Port"
The dropdown list depends on the declared cards in the shelf.
"Name"
Identification of the order wire
Card menu CTRL-2G > DCC Connection
"DCC Type" : Choice between "D1-D3" and "D4-D6"
Max 16 transparencies on a SWITCH HO/LO card and max 5
transparencies on a SW32 HOLO card
Card menu : CCU-2G > Loops
Used to configure severity and name of 4 incoming loops and 2 outgoing
loops, closure criteria for these 2 last, the "Central Site" option and the
parameters of the loops deport function
Card menu : CCU-2G > Alarms
Used to configure monitoring and severity of 48V#1, 48V#2 and 48VS
alarms.

Page A2-30
Default value
Clear
No connection
No connection
User Input x (x = 1 to 4)
User Output x (x = 1 to 2)
Configuration
Alarms
Wording
Severity
Monitor

Default value
Card menu : LTU, TRIB 1-8 and LINE 1-2 > TR REC or E1 ports or LPT
or HPT or VCG
Card menu : FAN-2G > Alarms
Card menu : CCU-2G > Alarms or Loops or Synchronization
Card menu : CTRL-2G > IP Parameters > Alarms
Card menu : SWITCH > TC List > TC Configuration
Severity configuration. The severity level of each alarm can be configured
separately with the following attributes :
"Critical"
"Major"
"Minor"
"Warning"
"Critical-inv"
"Major-inv"
"Minor-inv"
"Warning-inv"
Card menu : LTU, TRIB 1-8 and LINE 1-2 > TR REC or E1 ports or LPT
or HPT or VCG
The alarms can be monitored by block :
Monitoring
- SFP, SPI, RST, MST, MSP, MS-SPRing, MSA, HPT, HPOM, HPA,
LPOM. for the optical or electrical STM-n access points
- LPT, PPI for the 2/34/45 Mbit/s access points
- HPT, LPT, VCG, ETH, GFP, Access for the DATA cards

Page A2-31
Configuration
Wording
Thresholds
Path Traces

> SPI / RST / MST > RST :
-5
- management of EBER B1 (10 ) alarm
- "TIMdis" (Trace Identifier Mismatch) : enable or disable
- configuration of J0 PathTrace
- "Autodiscovery" (*) enable or disable
Enable : allows to generate automatically the Trace Sent in order to
enable an autodiscovery of equipment and networking by a network
management (**)
> SPI / RST / MST > MST
-3
- management of EBER B2 (10 ) alarm
-5
-9
- configuration of SD B2 threshold (10 to 10 )
-4
-9
- management of REI alarm and configuration of threshold (10 to 10 )
> HPT/HPOM or HPT
-5
- management of EBER B3 (10 ) alarm for VC4
-5
-9
- configuration of SD B3 threshold (10 to 10 ) for VC4
- management of REI alarm for VC4 and configuration of threshold
-4
-9
(10 to 10 )
- "TIMdis" (Trace Identifier Mismatch) : enable or disable
- configuration of J1 PathTrace for VC4
> HPA/LPOM or LPT
-3
-3
- management of EBER B3 (10 ) alarm for VC3 or EBER V5 (10 )
alarm for VC12
- configuration of SD B3 threshold for VC3 or SD V5 threshold for VC12
-5
-9)
(10 to 10
- management of REI G1 alarm for VC3 or REI V5 alarm for VC12
-4
-9
and configuration of threshold (10 to 10 )
- "TIMdis" (Trace Identifier Mismatch : enable or disable
- configuration of PathTraces: J1 for VC3 or J2 for VC12
Default value
Disable
Clicked (no TIM)
UNNAMED RS
Auto
Enable
-6
10
-6
Disable / 10
Enable
-6
10
Disable
-6
10
Clicked (no TIM)
UNNAMED VC
Enable
-6
10
Disable
-6
10
Clicked (no TIM)
UNNAMED VC
GFP FRAMED VC3 or
VC12 (GFP150 eXtra)

(*) AUTO = XXXXXXXX_**Y:01 (XXXXXXXX corresponds to the IP management address converted in hexadecimal, Y corresponds to the slot in which the
card is inserted
(**) In case of interconnection between an ADR2500 eXtra and an ADR10000, Autodiscovery must be unclicked and J0 programmed at " UNNAMED RS"
Page A2-32
Configuration
Wording
Path Trace
TCM Connections

Card menu : SWITCH > TC List > TC Configuration for VC4 TC
connections
- configuration of N1 PathTraces
- management of APIM alarm
Labels
TC TRACE
Disable
> HPT/HPOM or HPT or LPT or LPOM

Configuration of C2 label for VC4 and VC3 or V5 label for VC12 (the sent
or expected value "Unspecified" should be used only in case of
interworking problem)
Menu : Equipment > Failure Hold off/on time
Persistence Configuration .
Persistence for the appearance : X = 0, 1, 3, 10 or 30s
X=3s
Persistence for the disappearance : Y = 0, 1, 3, 10 or 30s
Y=3s
Acknowledgement of major and minor alarms output loops by pushbutton
on front panel of CTRL-2G card.
Persistence
Acknowledgement
Performance
Default value
Visualisation of alarms
and events log
Visualisation of
current alarms
RESET alarms and
events log
Logs
optical or electrical
STM-n, 2/34/45 Mbit/s,
Fast Ethernet,
GigaEthernet (xGE-DM
card) access points, TC
Connections
Menu : Equipment > Event Logs

Menu : Current Alarms
Menu : Equipment > Event Logs > Clear All
Card menu : TRIB 1-8 and LINE 1-2 > Performance > VC12 Near or
VC12 Far or VC3 Near or VC3 Far or VC4 Near or VC4 Far or MST
NEAR or MST FAR or RST NEAR
Card menu : SWITCH HO/LO >TC Performance > IEC Near
Displays performance log for the selected monitoring point as following :
- the 15 mn different from 0 counters (1 current and 16 saved)
- the 24 H different from 0 counters (1 current and 1 saved)
- the different from 0 unavailability periods ( until 6 max)
Gives access to Reset and threshold configuration sub-menus.

Page A2-33
Configuration
Wording

Option Clear current counters for this point
Clears current 15 mn and 24 H counters of selected point
Option Clear all counters for this point
Clears all counters for selected point
Option Counters configuration
Configures the 15 mn and 24 H thresholds for the selected point.
Default value
VC12
BBE : 9 000 , 12 000
ES : 120 , 350
SES : 15 , 20
UAS : 10 , 10
VC3
BBE : 36 000 , 48 000
ES : 150 , 600
SES : 15 , 20
UAS : 10 , 10
VC4 / IEC
BBE : 36 000 , 48 000
ES : 180 , 1500
SES : 15 , 20
UAS : 10 , 10
MST
BBE : 288 000 , 432 000
ES : 50 , 150
SES : 10 , 15
UAS : 10 , 10
RST
BBE
ES
SES
UAS

Page A2-34
: 9 000, 48 000
: 180, 1500
: 15 , 20
: 10,10
Configuration
Wording
Logs GigaEthernet
access points (GIG-E
card)
Default value
Card menu : TRIB 3-4 and LINE 1-2 > Performance > LAN, QoS or GFP
Displays GigaEthernet access (LAN), GFP layer and quality of service
treatment (QoS) performance log.
Gives access to Reset sub-menus
Option Clear statistics counters for this layer
Clears specific counters to the selected entity (LAN, QoS or GFP)
Option Clear all statistics counters
Clears all counters LAN, QoS and GFP
Card menu : TRIB 3-4 and LINE 1-2 > Performance > VC4 Near , VC4
Far
Displays performance log for the selected monitoring point as following :
- the 15 mn different from 0 counters (1 current and 16 saved)
- the 24 H different from 0 counters (1 current and 1 saved)
- the different from 0 unavailability periods ( until 6 max)
Gives access to Reset and threshold configuration sub-menus.
Option Clear current counters for this point
Clears current 15 mn and 24 H counters of selected point
Option Clear all counters for this point
Clears all counters of selected point
Option Counters configuration
Configures the 15 mn and 24 H thresholds for the selected point.
VC4
BBE : 36 000 , 48 000
ES : 180 , 1500
SES : 15 , 20
UAS : 10 , 10

Page A2-35
Configuration
Wording
Logs
Equipment
Security
Session
Authorized Managers

Menu : Equipment > Performance
> 15 Minutes Counters
Displays all the 15 mn different from 0 counters for all the monitoring
points of the equipment
> 24 Hours Counters
Displays all the 24 H no different from 0 counters for all the monitoring
points of the equipment
> Unavailable Periods
Displays all the different from 0 unavailability periods of the equipment
Option Clear all current counters
Clears current counter for all monitoring points.
Option Clear all counters & restart 15 mn
Clears all current counters for all monitoring points and restarts the 15Min
period.
Menu : Session
"Session Information"
Informations on current session
" Session-Login"
Enters session. Requests for qualification.
Restriction : only one authorized login for writing at a time
" Session-Logout"
Exits session subsequent to operator command or time-out
Menu : Equipment > Management
Managers List
"N IP"
IP addresses entry for the authorized stations to reach the equipment (10
possible addresses) according to qualification.

Page A2-36
Default value
Configuration
Wording

Choice of a qualification class by increasing order of rights :
- "Observer"
- "Operator"
- "Supervisor"
The class is granted according to the password. It is displayed.
Address of managers and levels authorized.
Each manager is associated to a maximum qualification level.
Ex. : Even with the Supervisors password, if the max level associated to
this IP address is "Operator", the granted level will be Operator.
Traps Managers Dest
"Dest IP"
Gives the list of recipient stations of the SNMP traps
"Community"
Authorization for transmission of traps to management : managers list.
Menu : Equipment > Security > Supervisor or Operator or Observer
"New password" and "Confirm new password"
One password per qualification class. Only Supervisor level is allowed to
modify password.
Passwords
Default value
Supervisor
GigaEthernet
Set-up
AdminStatus up
Auto Negotiation Enable
Pause Capability
Card menu : GIG-E > Settings > LAN

Traffic authorization on the LAN GigaEthernet interface
Self negotiation Mechanism Authorization for Pause mode
Operation Configuration for Pause mode if the self negotiation
mechanism is not validated.
Activated
Activated
Non activated

Page A2-37
Configuration
Wording
QoS parameters

Default value
Card menu : GIG-E > Settings > QoS > Pause Mode
Credit High Threshold : Over this threshold pause frames will be sent ;
60 %
receiving a pause frame, the link partner will stop sending frames
Credit Low Threshold : Under this threshold pause frames will no more be 10 %
sent ; the link partner will restart sending frames
Monitor : allows or not Pause Mode Rejected alarm monitoring
Activated
See paragraph 2.2.10.3
Card menu : GIG-E > Settings > QoS > 802.1d Priority
Class : associated class to the field Priority of the 802.1q frame
Card menu : GIG-E > Settings > QoS > IP V4 TOS
Class : associated class to the field TOS of the IP V4 header
Card menu : GIG-E > Settings > QoS > IP V6 TClass
Class : associated class to the field TClass of the IP V6 header
Card menu : GIG-E > Settings > QoS > VLAN ID
Class 0 to Class 3 : allows the addition or deletion of one correspondance
between a VLAN Id and a class
- Item : identification number of the configuration
- Range Size : number of configurated VLAN Id at which the class must
be associated
- First VLAN Id : first VLAN Id at which the class is associated
- Last VLAN Id : last VLAN Id at which the class is associated
All Classes : displays whole configuration data

Page A2-38
Configuration
GFP150 eXtra
Set-up
Wording
RED Configuration

Card menu : GIG-E > Settings > QoS > None
First Point Cross X : Over this threshold received frames dropping rate is
proportional to buffer use rate
Second Point Cross X : Over this threshold all received frames are
dropped
WRED Configuration
Card menu : GIG-E > Settings > QoS > IP V4 TOS
Profile Configuration
First profile or second profile see paragraph 2.2.10.3
Bandwidth Configuration Card menu : GIG-E > Settings > QoS > Balanced
Min : defines the minimum guaranteed percentage of the bandwidth by
class
Max : defines the maximum authorized percentage of the bandwidth by
class
WAN Configuration
Card menu : GIG-E > TR REC > WAN
Enabled VCs number : configuration of the number of VCs constituting
the GigaEthernet channel
For configuration of this card, refer to the chapter 7 of the present user
guide
10/100 Mbps Access
Card menu : GFP150 eXtra > ETH > Interface Settings
points
"ifAdminStatus"
Traffic authorization on the Ethernet interface
"Logical Interface"
- UNI : client side interface
- NNI untagged : non tagged network side interface
- NNI tagged : tagged network side interface
Default value
20 %
90 %
First profile
"100 Mbps Full"

Activated
UNI

Page A2-39
Configuration
Wording
MSTP

"Physical Interface"
Choice of the "Automatic" (with autonegotiation) or "Manual" physical
interface : 10/100 Mbps, Half/Full Duplex, Pause/No Pause
In "Automatic" the capabilities represent the local capacities of the
equipement that are negotiated with the remote equipment. The result of
this autonegotiation is visualisable in the Status " field ".
In "Manual" no autonegotiation, the "Status" field reflects the operator
configuration.
In order to have a correct link, it is recommended to configure both local
and remote equipment Ethernet interfaces with the same configuration :
- "Automatic" on both side or
- "Manual" and same duplex/speed configuration on both side
Note : in "Automatic" mode, if the remote equipment is set to "Manual",
local interface automatically switches to half duplex.
"Connecting Interface"
Adaptation according to the used cable : "Crossed", "Direct" or
"Automatic"
"Link Down Retransmit"
In point to point mode (one VMAN constituted of one ETH + one VCG in
each equipment), "Enable" allows to report one ETH Down (or one VCG
Down) on the remote ETH link.
Card menu : GFP150 eXtra > MSTP >Bridge Settings
By default, the MSTP protocol is activated, under condition of activation of
the licence
See 7.2.5 - Using the Multiple Spanning Tree Protocol on the GFP150
eXtra card

Page A2-40
Default value
100 Mbps Full
No pause
Automatic
Disable
MSTP
Configuration
xGE-DM
Set-up
Wording
GigaEthernet Access
Points

Card menu : xGE-DM > ETH
"ifAdminStatus"
Traffic authorization on the Ethernet interface
VCG
Default value
Activated
"Logical Interface"
- UNI : client side interface
"Physical Interface"
Choice of the "Automatic" (with autonegotiation of the Pause mode) or No pause
"Manual" physical interface : Pause/No Pause
In order to have a correct link, it is recommended to configure both local
and remote equipment Ethernet interfaces with the same configuration
Configuration of VCG(s)
The principle is identical to that of the GFP150 eXtra card ( 7.2.2.1)
without SWITCH function (Each "ETH #n" port is necessarily associated
to the "VCG #n" port).

Page A2-41
2.2.3.3 - Maintenance commands and operations

Wording
Parameters
Optical interface card STM-1 STM-4 STM-16 in Maintenance menu
Loop-back
"No loop-back" :
"Line" : transparent line loop-back,
activated/not activated
"Equipment" : transparent equipment
loop-back, activated/not activated
Laser (Automatic Laser Shutdown)
"ALS Enable"
The automatic shutdown function for
the laser can be not activated (global
function to equipment)
Restart
"2 sec" on operator action
"90 sec" on operator action
LTU, 3E3DS3FA, 63E1FA, electrical interface STM-1 cards in Maintenance
menu
Loop-back
"No loop-back" :
"Line" : Transparent line loop-back,
activated/not activated
"Equipment" : Transparent equipment
loop-back, activated/not activated
SWITCH HO/LO card in Maintenance menu
Traffic on SWITCH HO/LO 1 (or 2)
"Manual Switch to SWITCH 2 (or 1)"
activated
Switchover of traffic on the other
SWITCH HO/LO card
PSU card in Maintenance menu
Power On/Off
"On"
"Off"
Default value
Activated
Not activated
Not activated
Activated
Not activated
Not activated
Activated
Not activated
Not activated
Activated
Not activated
Table 2-26 : Maintenance commands and operations.
2.2.3.4 - Alarm processing

Indicator LEDs and pushbuttons
The tables below give the meanings for the various indicator LEDs when activated and the
purpose of the pushbuttons.
Specific indicator LEDs to CTRL-2G card
Component
monitored
Name
Remark
State
Equipment
"ALA M"
"ALA m"
Without
Red
Yellow
Green
On
On
On
Off
Major or critical alarm

Minor alarm
Transmission in progress
No traffic
Without
Yellow
On
Off
Link correct
No link
Ethernet
(management
access)
Meaning
Table 2-27 : Specific indicator LEDs to CTRL-2G card

Page A2-42
"TRAFFIC" indicator LEDs on PDH, STM, GIG-E, xGE-DM, GFP150 eXtra and
SWITCH HO/LO cards
Yellow indicator
LED
Meaning
On
Card carrying useful traffic : removal will result in traffic disturbance
Off
Card not carrying traffic
Table 2-28 : TRAFFIC indicator LEDs on PDH, STM, GIG-E, xGE-DM, GFP150 eXtra
and SWITCH HO/LO cards
"STATUS" indicator LEDs on all cards except PSU and FAN-2G

Green indicator
LED
Red indicator
LED
On
On
Off
Off
Flashing
Off
On
Off
On
Meaning
Card in service
Card in service and with alarm condition
Card hardware fault (fuse)
Card out of service
Selftest fault
Table 2-29 : STATUS indicator LEDs on all cards except PSU and FAN-2G
"STATUS" indicator LEDs on PSU card
Green indicator
LED
Red indicator
LED
Meaning
On
Off
On
Off
On
Off
Off
On
The card supplies the subrack (forbidden extraction

without maintenance operation)
Card in service and with alarm condition
Card hardware fault
The card does not produce current
Out of service or failure card
The card does not produce current
Table 2-30 : STATUS indicator LEDs on PSU cards

Specific indicator LEDs to GFP150 eXtra
Component
monitored
Name
Remark
State
Ethernet
(traffic access)
Without
Yellow
Without
Green
On
Off
On
Off
Meaning
Transmission in progress
No traffic
Link correct
No link
Table 2-31 : Specific indicator LEDs to GFP150 eXtra card

Page A2-43
Pushbuttons
Name
Location
Purpose
"ACK"
CTRL-2G
front panel
CTRL-2G
Alarm
acknowledge.
Configuration
reload
"INIT
CONFIG"*
Result when pressed

When pressed, disables outgoing alarm
loops A, B. Visual alarm is maintained.
"Manufacturer" configuration is reloaded
Table 2-32 : Pushbuttons

* To use the "INIT" pushbutton, press the pushbutton for at least 5 seconds. This pushbutton
is inaccessible (and not used) in normal operation.
The card located in EXT 2 slot must be extracted for access.

Page A2-44
Faults and alarms

The tables below give the severity level default values associated to the failures.
An alarm of gravity "major" or "critical" activates the major outgoing loops of the "POWER/ALM"
connector of the CCU-2G card
An alarm of gravity "minor" activates the minor outgoing loops of the "POWER/ALM" connector
of the CCU-2G card
An alarm of gravity "warning" does not activate any outgoing loop (available on HTTP).
Alarms
Optical SPI :
Name
Severity level
Loss Of Signal
major
Transmit Fail
major
(Temperature out of range (only for L16.2+ and

U16.2 cards)
major
SDH Physical Interface
SPI-LOS
SPI-TF
SPI-LASER TEMP
OUT OF RANGE
RST :
RST-LOF
RST-EBER-B1
RST-TIM
MST :
MST-AIS
MST-EBER-B2
MST-SD-B2
Regenerator Section Termination

Loss of frame for more than 1 to 3 ms
-5
Bit Error Rate > 10 on B1 Byte

Regenerator Section Trace Identifier Mismatch
major
major
minor
Multiplex Section Termination

Alarm Indication Signal
-3
warning
major
Degraded signal computed using bytes B2
minor
MST-REI
Remote Error Indication
warning
MST-RDI
Remote Defect Indication
warning
MSP :
Multiplex Section Protection
PAM
Protection Architecture Mismatch

(mismatch bit 5 in received K2 byte)
minor (1)
SCM
Selector Control Mismatch

(protocol mismatch)
minor (1)
OTM
MS-SPRing :
ARV
Operation Type Mismatch

[DNR (Do Not Reverse) request is received in K1
and protection is revertive or SF/SD request is
received in K1 with incorrect Sf/Sd Priority
Multiplex Section Shared Protection Ring
APS protocol Rules Violation failure
minor (1)
major
ATO
APS protocol Time Out failure
major
AUN
APS protocol Unknown Node failure
major
PTM
Potential Traffic Misconnection failure
minor
MMS
Multiple Multiplex Section failure
minor
Table 2-33 : Alarms and severity levels

(1) When the MSP is configured in 1+1

Page A2-45
Alarms
Name
Severity level
AU-AIS
Administrative Unit - Alarm Indication Signal
warning
AU-LOP
Administrative Unit - Loss Of Pointer
major
MSA :
Multiplex Section Adaptation
HPOM :
High order Path Overhead Monitoring

-5
HO-EBER-B3
major
High Order Path - Signal Degrade
minor
HO-REI
Remote Error Indication (G1 byte)
warning
HO-RDI
High Order Path - Remote Defect Indication

(G1 byte)
warning
warning
HO-SD-B3
HO-UNEQ
HO-TIM
HPT :
HO-RDI
minor
High order Path Termination
HO-SD-B3
HO-EBER-B3
High Order Path - Signal Degrade

-5
minor
major
HO-REI
warning
HO-RDI
High Order Path - Remote Defect Indication

(G1 byte)
warning
High Order Path - UNEQuipped payload)
warning
HO-TIM
High Order Path - Trace Identifier Mismatch
minor
HO-PLM
Payload Label Mismatch
warning
HO-LOM
High Order Path - Loss Of Multitrame
minor
HO-UNEQ
HPA : Higher order Path Adaptation

TU-AIS
Tributary Unit - Alarm Indication Signal
TU-LOP
Tributary Unit - Loss Of Pointer
warning
minor
LPOM : Lower order Path Overhead Monitor

LO-EBER-B3 (VC3)
LO-EBER-V5 (VC12)
LO-SD-B3 (VC3)
LO-SD-V5 (VC12)
LO-REI
LO-RDI
LO-UNEQ
LO-TIM
-3
major
-3
Signal Degrade - B3
major
minor
Signal Degrade - V5
minor

Bit Error Rate > 10 on V5 Byte
Remote Error Indication (G1 or V5 byte)
warning
Low order Path - Remote Defect Indication

(G1 or V5 byte)
warning
Low order Path - UNEQuipped payload
warning
Low Order Path - Trace Identifier Mismatch
minor

Page A2-46
Alarms
LPT :
Name
Severity level
Lower order Path Termination

-3
major
-3
Signal Degrade - B3
major
minor
Signal Degrade - V5
minor
LO-REI
Remote Error Indication (G1 or V5 byte)
warning
LO-RDI
Low order Path - Remote Defect Indication

(G1 or V5 byte)
warning
LO-UNEQ
LO-TIM
Low order Path UNEQuipped

Low Order Path - Trace Identifier Mismatch
warning
minor
LO-PLM
Low order Path Payload Label Mismatch
PPI : PDH Physical Interface
warning
LO-EBER-B3 (VC3)
LO-EBER-V5 (VC12)
LO-SD-B3 (VC3)
Bit Error Rate > 10 on V5 Byte
LO-SD-V5 (VC12)
PPI-LOS (21 x 2M)

PPI-LOS (34 / 45M)
PPI-AIS
PPI-RLOL (34 / 45 M)
Loss Of Signal
Loss Of Signal
Alarm Indication Signal
Receive Loss Of Lock
minor-Inv.
minor-Inv.
warning
warning
LOM
Loss of Multiframe
warning
SQM
SeQuence Mismatch
warning
LOA
Loss of Aligment
VCG - Remote Defect Indication
major
warning
All VCG is failed, interrupted traffic
major
Some VCG are failed, degraded traffic
minor
VCG :
Virtual Container
VCG rdi (2)

(only GFP150)
VCG defect (3)
VCG degraded (3) (4)
LCAS : Link Capacity Adjustment Scheme

LCAS Member fail (4)
GFP :
LFD
LOCS
LOCCS
A member of VCG is failed
warning
General Framing Procedure

Loss of GFP Frame Delineation
major
Los Of Client Signal
minor
Los Of Client Character Synchronisation
minor
UPM
User Payload Mismatch
minor
EXM
EXtension header Mismatch
minor

(2) This alarm raises only in LCAS mode when SF (TU-AIS, TU-LOP, SD) is detected on all
the VCG members of the remote equipment.
(3) These alarms are indications of state of the path elaborated for the network manager in
supplement of faults indications ; of this fact 2 indications can be transmitted in logs for
only one default.
(4) This alarm raises only if LCAS mode is active.

Page A2-47
Alarms
Name
Severity level
Access :
Data Physical Interface
ETH Interface Defect
Loss of Ethernet link
major
LOS
Loss of Optical Signal
major
Loss of Data
major
Pause Mode Rejected
major
LINK DOWN
Pause Mode Rejected
(5)
SETS :
Synchronous Equipment Timing Source
LOS T3
Loss of signal on synchronization input T3
minor
LOS T2
warning
LOS T1
warning
LOS T4
Fault on synchronization output T4
minor
Synchronization rhythm frequency out of phase

locked loop range (6)
minor
SYNC FREQ OUT OF

RANGE
TCM : Tandem Connection Monitoring

LTC
Loss of Tandem Connection
major
TC - INComing AIS
minor
TC - Access Point Identifier Mismatch
major
TC-RDI
TC - Remote Defect Indication
minor
TC-ODI
TC - Outgoing Defect Indication
minor
TC-REI
TC - Remote Error Indication
minor
TC-OEI
TC - Outgoing Error Indication
minor
TC UNEQuipped payload
major
Local user inputs # 1
Local input loop 1
warning
Local input loop 2
warning
Local input loop 3
major
Local input loop 4
minor
Local user output # 1
Local output loop 1
warning (7)
Local user output # 2
Local output loop 2
warning (8)
TC-INCAIS
TC-APIM
TC-UNEQ
Local equipment

(5) For GIG-E card, this alarm is raised when QoS Mode Pause is selected and if the card
cannot send pause frames.
For GFP150 and xGE-DM cards, this alarm is raised when the "Automatic" mode and the
"Pause" capability are selected and the Pause status = No Pause (the remote equipment
has refused the negotiation of Pause).
(6) Internal equipment rhythm is then kept in a 9.2 ppm range
(7) By default, the Local user output #1 loop is activated when a major alarm is present
(8) By default, the Local user output #2 loop is activated when a minor alarm is present
Page A2-48
Alarms
Name
Severity level
Remote equipment
Remote Mngt major
Remote major alarm
major (9)
Remote Mngt minor
Remote minor alarm
minor (9)
One Fan Failed
major
At least two Fans Failed
major
Power Supply Fail 1

(10)
Defective Power supply block 1
major
Power Supply Fail 2

(10)
Defective Power supply block 2
major
48V#1
Missing of 48V#1 input
major
48V#2
Missing of 48V#2 input
major
48VS
Missing of 48V signaling input
minor
Loss of management link PPP#i
minor
Loss of Ethernet link
minor
Missing Card
major
Mismatch Card
major
Traffic not provided (only PDH cards)
major
Defective Card
(see Table 2-38)
major
No MSTP Licence
(only GFP150 eXtra card)
major
SFP missing
major
SFP mismatch
major
SFP defective
SFP not approve
major
FAN-2G module
One Fan Failed
Fans Failed
Power supply
Equipment management
PPP#1 to 34 DOWN
Ethernet DOWN
Others
Card Alarms
major
(9) If the configured equipment is declared central office

(10)The two alarm indications are operational only if the module FAN-2G arranges the option
of redundant converter.

Page A2-49
Information
Localization
Description
"FPGA Codes Missing or

Not Compatible"
CTRL-2G Card
At least one flash FPGA code is absent or is

incompatible
"Soft. Codes Missing or

Not Compatible"
CTRL-2G Card
At least one flash soft code is absent or is

incompatible
"RAM Test Failed"
CCU-2G Card
RAM self test has failed
"RAM Too Small"
CCU-2G Card
The RAM size is too small
"Hardware Incompatible"
All Cards
The hardware release of the card is

incompatible with the CTRL soft
"Unknown Family in
Inventory"
All Cards
The card family is not managed by the CTRL

soft
"Inventory Not Readable"
All Cards
The card inventory is not readable
"Incorrect Inventory"
All Cards
The card inventory is incorrect
"FPGA Code
Incompatible"
All Cards
A FPGA code is incompatible with the CTRL

soft
"FPGA Code Missing"
All Cards
A FPGA code is missing in flash memory
"Cannot Load FPGA"
All Cards
A FPGA code cannot be loaded
"FPGA Test Failed"
All Cards
The FPGA self test has failed
"MICRO FPGA Test

Failed"
SWITCH HO/LO
Cards
The MICRO FPGA self test has failed
"BDT FPGA Test Failed"
SWITCH HO/LO
Cards
The BDT FPGA self test has failed
"WEST FPP ASIC" Test

Failed"
SWITCH HO/LO
Cards
The "WEST FPP ASIC(s)" self test has failed
"EAST FPP ASIC" Test

Failed"
SWITCH HO/LO
Cards
The "EAST FPP ASIC(s)" self test has failed
"Soft. Code Incompatible"
GIG-E Card
The software code revision is incompatible

with the CTRL software
"Soft. Code Missing"
GIG-E Card
The software code is missing in flash memory
"Cannot Load Software"
GIG-E Card
The software code cannot be loaded
"Software Not
Responding"
GIG-E Card
The software card does not respond
"Supply Failure"
"PSU Family Mismatch"
"Incorrect Inventory or
Power Supply Failed"
All Cards
PSU cards
LTU21E1 or
LTU3E3DS3 Cards
Power supply failure

The PSU card is incompatible with the other
PSU cards of the shelf
Power supply failure or incorrect inventory
"PDH ASIC 1 Test

Failed"
63E1 or 3E3DS3
Cards
The ASIC 1 self test has failed
"PDH ASIC 2 Test

Failed"
63E1 or 3E3DS3
Cards
"PDH ASIC 3 Test

Failed"
63E1 or 3E3DS3
Cards
"LTU CPLD Test Failed"
LTU21E1 or
LTU3E3DS3 Cards
The CPLD self test has failed
"LTU LIU Test Failed"
LTU3E3DS3 Cards
The LIU self test has failed
Table 2-38 : Associated informations to card defective alarm

Page A2-50
Fault correlation
A correlation processing is performed on all the detected faults.
This correlation mechanism, implemented on each change of information collected, is used to
remove faults induced by other faults to facilitate fault isolation.
The tables below define the faults which are masked by each fault detected in the system.
Key :
X
: The fault considered on the current line is masked by the faults of the current
column.
ex : Fault 3 (LOF) is masked by fault 2 (LOS).
Correlation of STM-n faults

FAULTS
1
TF
FAULTS
2
LOS
3
LOF
4
TIM
5
EBER
-B1
6
AIS
SPI-TF
SPI-LOS
RST-LOF
RST-TIM
RST-EBER-B1
MST-AIS
MST-EBER-B2
MST-SD-B2
MST-RDI
10
MST-REI
7
EBERB2
8
SD-B2
9
RDI
X
X
Table 2-39 : Correlation of STM-n faults

Correlation of MSP faults
FAULTS
FAULTS
1
PAM
PAM
SCM
OTM
2
SCM
3
OTM
Table 2-40 : Correlation of MSP faults

Correlation of MS-SPRing faults
FAULTS
FAULTS
1
AUN
2
ARV
3
ATO
AUN
ARV
ATO
PTM
MMS
4
PTM
5
MMS
Table 2-41 : Correlation of MS-SPRing faults

Page A2-51
10
REI
Correlation of HPOM/HPT faults from SDH and xGE-DM cards

The HO faults are masked by the STM-n faults : LOS, LOF and MST-AIS..
The HO-LOM fault is filtered if there is no configured VC12 connection on this STM-n
FAULTS
FAULTS
1
AU-AIS
2
AU-LOP
3
UNEQ
4
TIM
AU-AIS
AU-LOP
HO-UNEQ
HO-TIM
HO-RDI
HO-REI
HO-PLM (HPT)
HO-LOM (HPT)
HO-EBER-B3
10
HO-SD-B3
5
RDI
6
REI
7
PLM
8
9
TU-LOM EBER
-B3
10
SDB3
X
X
Table 2-42 : Correlation of HPOM/HPT faults from SDH and xGE-DM cards
Correlation of HPT faults from GIG-E cards

The HPT faults are masked by the STM faults : LOS, LOF and MST-AIS.
The only alarm associated to the SDH channel is LOA and is correlative by the LOM, SQM,
PLM, UNEQ, TIM and VC-AIS of all VC4 that compose the channel.
FAULTS
1
AU-AIS =
VC4-AIS
2
3
AU-LOP = SD-B3
VC4-AIS
4
UNEQ
5
TIM
6
PLM
FAULTS
AU-AIS = VC4-AIS
AU-LOP = VC4-AIS
HO-SD-B3
HO-UNEQ
HO-TIM
HO-PLM
HO-RDI
Concat_LOM
Concat_SQM
7
RDI
8
9
Concat_ Concat_
LOM
SQM
Table 2-43 : Correlation of HPT faults from GIG-E cards

Page A2-52
Correlation of HPA/LPOM/LPT faults

The HPA/LPOM/LPT faults are masked by the STM faults (LOS, LOF and MST-AIS), the MSA
faults (AU-AIS and AU-LOP) and the HPT faults (UNEQ, TIM, PLM and LOM)
The HPA faults (TU-AIS and TU-LOP) are correlative by the HO-LOM fault only for the
connections of VC12 type.
FAULTS
FAULTS
1
TU-AIS
2
TU-LOP
3
UNEQ
4
TIM
TU-AIS
TU-LOP
LO-UNEQ
LO-TIM
LO-RDI
LO-REI
LO-PLM (LPT)
LO-EBER
LO-SD
5
RDI
6
REI
7
PLM
8
EBER
9
SD
X
X
Table 2-44 : Correlation of HPA/LPOM/LPT faults
Correlation of 2, 34, 45 Mbit/s ports faults

FAULTS
FAULTS
1
1
LOS
3
RLOL
2
AIS
PPI-LOS
PPI-RLOL (*)
PPI-AIS
Table 2-45 : Correlation of 2, 34, 45 Mbit/s ports faults

(*) only for 34/45 Mbits ports
Correlation of remote faults

LO-REI, LO-RDI, HO-REI and HO-RDI faults of unidirectional connection input are filtered.

Page A2-53
Correlation of VCG faults from GFP150 eXtra, GIG-E and xGE-DM cards
The LOA, LFD, LOCS, LOCCS, UPM, EXM, RDI, DEFECT and DEGRADED alarms are VCG
alarms.
The LOM, SQM, LCAS_MemberFail alarms are alarms of member constituting a VCG.
FAULTS
10
11
12
LOA
LFD
LOCS
LOCCS
EXM
UPM
LOM#i
SQM#i
LCAS_
Member
Fail#i
RDI
DEF
ECT
DEGR
ADED
FAULTS
1
LOA
LFD
LOCS
LOCCS
EXM
UPM
LOM#i
SQM#i
LCAS_
Member
Fail#i
X
X
10 RDI
11 DEFECT
12 DEGRADED
Table 2-46 : Correlation of VCG faults from GFP150 eXtra, GIG-E and xGE-DM cards
Definitions of VCG_DEFECT and VCG DEGRADED synthesized failure indications
Notations used in the following paragraphes :
SF Member#i corresponds to at least one of among failures LOM#i, SQM#i, SF_LPT#i or LCAS
Member Fail#i of VC member #i of a VCG.
SF_LPT#i corresponds to at least one of among failures TU-LOM (for VC-12 only), TU-AIS, TULOP, LO-SD (if LCAS activated), LO-PLM, LO-UNEQ, LO-TIM of the LPT functional block of VC
#i.
Please note that LCAS Member Fail#i is computed only if LCAS is active.
Definitions:
When LCAS mode is not active,
- VCG_DEFECT is set whenever one of the LOCS, LOCCS, UPM, EXM, LFD, LOA failure
indications is raised or at least one of the SF Member#i is raised.
- VCG_DEGRADED is never set
When LCAS mode is active,
- VCG_DEFECT is set if one of the LOCS, LOCCS, UPM, EXM, LFD, LOA, RDI failure
indications is raised or all SF Member#1 to SF Member#X are simultaneously raised.
- VCG_DEGRADED is set if VCG_DEFECT is not set and at least one of the SF Member#i is
raised.
VCG_DEGRADED alerts the operator that, although Ethernet over SDH traffic is still going on, thanks to LCAS scheme the requested SLA may not be achieved due to lack of SDH
bandwidth.
Page A2-54
2.2.4 - Performance processing

Performance processing consists of supervising the following monitoring points :
For the local equipment :
the regeneration section (byte B1) ("near end working (protection) RS"),
the multiplexing section (byte B2) ("near end working (protection) MS"),
the VC4 tributary paths ("near end High Path Virtual Container"),
VC3 tributary paths ("near end Low Path Virtual Container"),
VC12 tributary paths (byte V5) ("near end Low Path Virtual Container"),
TCM tributary paths (N1 byte) (IEC : incoming error counter)
For the remote equipment :
the multiplexing section (byte M1) ("far end working (protection) MS"),
the VC4 tributary paths ("far end High Path Virtual Container").
VC3 tributary paths ("far end Low Path Virtual Container")
VC12 tributary paths (byte V5) ("far end Low Path Virtual Container").
Performance processing involves the following functions :
computation of number of erroneous blocks on the local and remote malfunctions and
monitoring for appearance of faults over a period of one second,
computation and determination of states : ES (Errored Second), SES (Severely Errored

Second ), BBE (Background Block Error) and UAS (UnAvailable Second) for each
monitoring point,
preparation, for each monitoring point, of 15 minute and 24 hour counters (BBE, ES, SES
and UAS).
Determination of performance states : ES, SES and UAS :

For each monitoring point, the performance states are as following :
ES (Errored Seconds)
period of 1 s or a fault,
SES (Severely Errored Seconds) : number of severely errored seconds,
: number of seconds with at least one error detected over a

Page A2-55
Monitoring point
RS (byte B1) (for local)
MS (byte B2) (for local) and MS (byte M1) (for remote)
SES declaration threshold

2400 (1 block by frame)
28 800 (24 blocss by frame)
HP VC4 / IEC
LP - VC3
LP - VC12 (byte V5)
600 (1 block by 4 frames)
UAS (UnAvailable Second) : number of unavailable seconds,
BBE (Background Block Error) : number of erroneous blocks not including SES.
REMINDER :
An SES is a second for which the number of errors exceed the defined
threshold or during which at least one fault is detected.
Generation of 15 minute and 24 hour counters :

The result of the computations is then combined for each monitoring point in :
24 hour counters (BBE, ES, SES and UAS),
15 minute counters (BBE, ES, SES and UAS).
The last six "unavailable periods" are preserved and displayed on the web browser.
Performance processing is initialized on creation of the connection.
The following information can be displayed on the web browser : the last 16 non-null 15 minute
counters, the current 15 minute counter, the last non-null 24 hour counter, the current 24 hour
counter and the last 6 unavailable periods.
2.2.5 - Optical Supervision

Optical modules SFP DDM (Digital Diagnostic Monitoring) allow the supervision of the parameters
below (Menu : STM-n > TR REC > SFP or 2GE-DM > SFP) :
OOP : Optical Output Power (dBm)
OIP : Optical input Power (dBm)
LBC : Laser Bias Current (mA)
Temp : SFP module Temperature (C)
Voltage : SFP module supply Voltage (V)

Page A2-56
2.2.6 - Synchronization
Synchronization of the local and remote equipment is managed in accordance with the available
synchronization sources, their quality and the priority assigned to each.
The possible synchronization sources include :
standalone operation (holdover* or local oscillator mode),
2 sources T1 extracted from incoming tributary STM-1, STM-4 or STM-16 trains (1 to 32

possibilities depending on number and type of cards present in equipment),
2 sources T1 extracted from incoming line STM-16 trains (1 to 2 possibilities depending on

number of "LINE" cards in equipment),
2 sources T2 extracted from incoming tributary 2 Mbit/s trains (maximum 1 T2 by 63E1 or

63E1FA card).
The 63E1FA card does not propose T2 synchronization when it is located in "TRIB 1" slot.
The TRIB 8 and LTU 8-x slots are only proposed in T2_1.
T3_1 and T3_2 : two external sources, 2 MHz G.703
* The Holdover mode is a memorization of a last valid synchronization timing.

Until 60s can be necessary after a source selection to validate the holdover mode.
NOTE :
On creation of an MSP protection, the Protection link inherits the configurations of

the Working link and therefore, in particular,those of synchronization.
The Synchronization screen summarizes the status of the timing obtained from the
traffic link under the Working interface reference.
The figures below give examples of synchronization in accordance with the equipment
connections.

Page A2-57
External synchronization
input at 2 MHz (T3) :
- Quality = PRC,
- Priority = 1.
)
1)
)
ADR2500 eXtra 1
Internal
synchronization
T0 = T3
(
(2
(
STM16 access (T1-c) =:

- Quality = DNU
- Priority = 2.
SSM = PRC
STM16 access(T1-c) =:
- Quality = DNU
- Priority = 2.
)
1)
)
(
(2
(
ADR2500 eXtra 2
T0 = T1 Line 1
T1 Line2=T0
=T3 (ADR2500
eXtra 1)
T1 Line2 = T0 = T3
2 MHz clock output

T4 = T0 = T3 (ADR2500 eXtra 1)
ADR2500 eXtra 3
SSM = PRC
)
2)
)
T0 = T1 Line1
Synchronization of
other equipment
(
(1
(
2 MHz clock output

T4 = T0 = T1 Line1 = T3 (ADR2500 eXtra 1)
Synchronization of other equipment
Figure 2-6 : Synchronization using 2 MHz external synchronization input (T3)
T1"Trib" STM-n access

SSM = PRC,
- Priority = 1.
)
1)
)
ADR2500 eXtra 1
Internal
synchronization
T0 = T1"Trib"
(
(2
(

- Quality = DNU
- Priority = 2.
SSM = PRC

- Quality = DNU
- Priority = 2.
)
1)
)
ADR2500 eXtra 2
T0 = T1 Line 1
(
(2
(
T1 Line2=T0
=T1"Trib"(ADR2500 eXtra 1)
T1 Line2=T0=T1"Trib"
2 MHz clock output

T4 = T0 = T1"Trib" (ADR2500 eXtra 1)
ADR2500 eXtra 3
SSM = PRC
)
2)
)
T0 = T1 Line1
(
(1
(
2 MHz clock output

T4 = T0 = T1 Line1 = T1"Trib" (ADR2500 eXtra 1)
Synchronization of other equipment
Figure 2-7 : Synchronization using a synchronous tributary access

Page A2-58
2.2.7 - Loops Management

On remote sites (i.e. non-central site), two local outgoing loops (Major and minor local user
outputs) are activated on the appearance of local alarms : equipment alarms and configured remote
indication loops (Local user input #1, #2, #3 and #4).
The remote loopback function allows an equipment named "Central Site", to register faults
present on remote sites.
This function requires each site to transmit to the "Central Site" an alarm presence message.
Depending on the configuration, this message corresponds to the local alarms and/or the remote
monitoring loopback 1 and 2 (Local user input #1 or #2). Data are transmitted within the S1 byte (the 4
bits not used for the synchronisation).
For each site in the network, data chaining in either a bus or ring type network architecture is
provided by a "OR" function between data received via the incoming S1 STM-n, and local data (Local
alarms and/or Local user input #1and #2).
In the "Central Site" equipment, an "OR" function between data received via incoming S1
STM-n and local data enables local alarm loopbacks to be activated (Local user outputs Major and
Minor). Furthermore, a major/critical or minor remote default detected via S1 will trigger in the Central
Site equipment a local alarm with the major or minor severity.
S1 emission and reception may be configured separately for each STM-n access. This allows
the rejection of S1 received from a remote equipment which does not use the S1 byte for remote
loopback. This is also used to deselect S1 emission in some or all STM-n access points from central
sites in order to prevent a permanent alarm activation.
To configure the remote loopback function, the following parameters should be programmed :
"Central Site", Send Remote 1 and Send Remote 2 for local data, and Enable Input (Reception of
S1) and Enable Output (Emission of S1) for each configured STM-n access.
The Enable Input and Enable Output parameters take default values on each modification
of the Central Site option. Therefore, if the equipment becomes Central Site, the Enable Input
boxes become selected and the Enable Output boxes unselected. And if the equipment becomes
Remote Site (default configuration), all Enable Input and Enable Output boxes become
unselected. Then, these default values may be modified when required.
NOTE 1 : When Local User Input #1 and #2 collect major/critical and minor alarm informations, it is
necessary to give them a "warning" severity in order to avoid a permanent activation.
NOTE 2 : If the equipment loopback function is configured, it is necessary to deselect the S1 reception
on the corresponding STM-n access in order to avoid a permanent alarm activation.
NOTE 3 : If a MSP type protection is configured, the loops management parameters are not
configurable on the Protection access. They take the same values as the Working access parameters
and the S1 byte is broadcasted on both access points of the MSP pair.
The Figure 2-8 gives an example of remote management of the local outgoing loops
according to the equipment connections.

Page A2-59
Local Outgoing Loops =

Local Alarms + Remote alarms
* Invalid S1 : S1 whose
most significant bit is set
to 1
* Valid S1 : OR with the

local alarms and the received
S1 alarms (excepted twin one
with valid one)
ADR2500 eXtra 1
Central Site
S1 Reception enabled
for all accesses
Invalid S1*
S1Emission not
enabled for any access
Valid S1*
Invalid S1*
Valid S1*
ADR2500 eXtra 2
Remote Site
S1 emission and
reception enabled for
all accesses
ADR2500 eXtra 3
Remote Site
Valid S1*
S1 emission and
reception enabled for
all accesses
Valid S1*

Local Alarms

Local Alarms
Figure 2-8 : Remote loopback function (collection of alarms on a Central Site)

Page A2-60
2.2.8 - MS-SPRing protection on LINE interfaces

2.2.8.1 - Introduction
To protect a ring-type digital data transmission network, several protection mechanisms are
available, including MS-SPRing, SNC and MSP. The MSP and MS-SPRing protection systems are
exclusive with respect to each other on a single multiplexing section, and the SNC protection does
not apply to channels protected by MS-SPRing.
The MS-SPRing protection function (Multiplex Section Shared Protection Ring) is available on ring
topologies with up to 16 nodes. Compared to the SNC protection, it provides the advantage of
shared use of protection resources for several trails within the ring.
In these multiplex section shared protection rings, the active channels carry the normal traffic
signals whereas the protection channels are reserved for protection of the traffic. This is available
on the Line interfaces of the ADR2500 eXtra.
2.2.8.2 - Principle
The ADR2500 eXtra implements the MS-SPRing protection diagram (BSHR) for ring protection
on 2 fibers.
The fibers are divided into channels; for example, one STM-16 contains 16 AU4 channels. The set
of channels is divided into Working channels and protection channels. There are an equal number
of each. A so called "channel" is a channel within the ring and not within an equipment.
Mechanisms are implemented by an equipment to route the Working channel information on
Protection channels in the opposite direction when a fiber break occurs, for example.
Half of the channels on each fiber are used for protection. Thus, there is only a single physical
ring.
The standard calls for the possibility of transmitting the unprotected traffic on certain channels
while other channels are protected : thus we have NUT channels (Non-preemptible Unprotected
Traffic) which cannot be interrupted for protection purposes and Extra-Traffic which is carried in
protection channels, available when the ring is idle, and therefore interrupted during a protection
action (Extra Traffic non supported).
Normal
Backup
Dir.
Figure 2-9 : Example of a protected ring

Page A2-61
In the example given above, there is a connection between nodes 6 and 3 via nodes 1 and 2. A
fiber break between nodes 2 and 3 requires re-routing of the channels in node 2. The channels
thus protected cross the ring in the reverse direction to reach node 3 using the protection
channels..
The protection diagram contains 8 Working channels and 8 Protection channels :
Chan.
Type
1
W
2
W
3
W
4
W
5
W
6
W
7
W
8
W
9
10
11
12
13
14
15
16
P(1) P(2) P(3) P(4) P(5) P(6) P(7) P(8)
When there is no problem on the ring, the traffic passes in 8 AU4 (8 Working).
The association of numbers to the Working and protection channels is defined by the standard
and cannot be reordered. Channel 11 always protects channel 3.
2.2.8.3 - Configuration rules relative to 2-fibers MS-SPRing protection

This section contains the configuration rules to be applied (mandatory). These rules are
automatically applied transparently by IONOS-NMS.
CAUTIONS :
- Implementation and maintenance of the MS-SPRing protection configuration using the operation
interface without the IONOS-NMS network manager is extremely tricky and is not recommended
by SAGEM.
- Node-by-node activation of the protection should only be performed provided no section fault (SF
or SD) is present.
For any automatic configuration of the MS-SPRing protection, refer to the IONOS-NMS installation
and user guide.
Configuration of topological map
The topological map appears in the form of an ordered set of values called identifiers which must
be different for each NE, and therefore unique within a ring.
Starting from any first node, the topological map is filled in by listing the identifiers node by node
while turning in the conventional direction : "East to West" in an node crossed, and therefore
"Line West (L1) to Line East (L2)" between two nodes.
Each node has a topological map of the ring updated by the local personnel or by the
management system.

Page A2-62
Figure 2-10 : Topological map of a ring

Nodes
Identifiers
1
A
2
J
3
M
4
P
5
B
6
L
7
K
8
G
9
S
10
E
11
F
12
R
13
C
14
D
15
N
16
H
RULES :
Adding or deleting a node in a ring requires modification of the topological maps of all the nodes.
A MS-SPRing ring cannot contain more than 16 nodes.
Configuration of misconnection map in the case where the VC4 of the ring transport
containers of lower order (VC3 and VC12) that are all extracted in a unique point of the
ring
In this case, the VC4 are the links point to point between the entrance and the exit of the ring and
we are brought back to a MS-SPRing protection therefore with suppression of signal at the level
VC4 normalized
The signal cancellation topological map (used in each node) contains the topological addresses of
the nodes through which the AU4 traffic enters and exits the ring : this map is only used for signal
cancellation purposes (injection of AU-AIS) subsequent to potential erroneous connections
occurring during multiple faults in the ring.
R
T=W3
Normal
Backup
Dir.
T=W5
Figure 2-11 : Example of incoming and outgoing traffic of a ring

Page A2-63
For each outgoing traffic via the time slots of the East and West interfaces, the signal cancellation
table gives the node identifier where the traffic is inserted in the ring and the node identifier where
the traffic exits the ring.
In the example above, the signal cancellation table in node 2 is :
Node 2 West :
Time slot
Entry
Exit
W1
W2
W3
3
1
W4
W5
4
6
W6
W7
W8
W1
W2
W3
W4
W5
W6
W7
W8
Node 2 East :
Time slot
Entry
Exit
The Q connection enters the ring in node 4 and exits in node 6.

It crosses node 2 in the East/West direction on Working timeslot 5.
The R connection enters the ring in node 3 and exits in node 1.
It crosses node 2 in the East/West direction on Working timeslot 3.
No connection crosses node 2 in the West/East direction.
Configuration of misconnection map in the case where the VC4 of the ring transport
containers of lower order (VC3 and VC12) that are inserted / dropped to different places
of the ring (case of the VC4 omnibuses)
In this case, two protection solutions with choice by the operator at the time of the configuration
are proposed :
- the VC4 omnibuses are decomposed in n VC4 carriers joining every adjacent equipment; these
VC4 are protected in MS-Spring and the suppression of signal is assured at the VC4 level in
accordance with the norm. The inter-operability is guaranteed thus
- the VC4 omnibuses are declared as NUT trafic ; they are not therefore protected at the level MSSpring and one uses the SNC protection for lower order paths that they transport
RULES :
- The signal cancellation table of each node must be updated when a trail is created or deleted in
the network.
- In each node, each Working timeslot of the signal cancellation table must contain both the entry
and exit numbers of the node on which the traffic circulates on the ring.

Page A2-64
Configuration des NUT

The NUT map (unprotected uninterrupted traffic) must be identical in each node.
It indicates the NUT channels, i.e. channels for which the protection mechanism is inactivated.
Only Working channels are contained in the NUT map. If the Working channel is NUT, the
corresponding protection channel is also NUT.
Example :
Time slot
NUT
W1
W2
W3
X
W4
W5
W6
W7
W8
In the above example, the channel 3 is set to NUT, so the Working channel N 3 and its
Protection channel N 11 are both NUT.

Page A2-65
2.2.9 - TCM Function

The TCM function takes place at network level and provides the operator with a monitoring service for
VC4 data paths by the mean of TC trail delimited by TCM Points.
2.2.9.1 - TCM Points at Equipment Level

TCM Points can be set up at VC4 bi-directional cross-connections level within each equipement.
TCM Points can be configured in 2 modes :
-
intrusive mode : TC EndPoint,

non-intrusive mode : TC Monitoring Point.
The TC EndPoint consists of a Source entity and a Sink entity ; the TC EndPoints work on a pair basis
(TC Endpoint X and TC EndPoint Y) ; the part of data path delimited by the pair X/Y is named a TC
Trail.
The Source of Point X generates a multiframe which is carried by the N1 byte alongside the TC Trail
up to the Sink of Point Y ; samely in the reverse direction, the Source of Point Y generates a
multiframe carried by the N1 byte up to the Sink of Point X.
The Figure 2-12 shows the four entities Source X, Sink X, Source Y and Sink Y working together
according to :
-
their localisation within a same EndPoint ;

their assocation within a same direction.

Page A2-66
TC EndPoint X
TC EndPoint Y
Direction 1
Source
Sink
Sink
Source
Direction 2
TC Trail
Consequential Action RDI
4 Entities : Source X, Sink X, Source Y, Sink Y
2 EndPoints : X (Source X + Sink X) + Y (Source Y + Sink Y)
2 Directions : D1 (Source X + Sink Y) + D2 (Source Y + Sink
VC4 XConnection
Physical Connection
Figure 2-12 : TC EndPoints X/Y
The operator has to take care of setting up the pair X/Y in a tte-bche position (Soure X(Y) facing
Sink Y(X)) in order to the Source of one Point can communicate with the Sink of the other Point and
this for each direction. TC-UNEQ and Loss of TC alarms can be due to a wrong setting up of the pair
X/Y ; please refer to Figure 2-13, Figure 2-14 and Figure 2-15.
TC EndPoint X
TC EndPoint Y
Source
Sink
Sink
Source
TC Trail
TC EndPoints X/Y are Source facing Sink ; they can delimit a TC Trail
Figure 2-13 : TC EndPoints X/Y - Source facing Sink

Page A2-67
TC EndPoint X
TC EndPoint Y
Source
Source
Sink
Sink
TC EndPoints X/Y are not Source facing Sink ; they cannot delimit a TC Trail
Figure 2-14 : TC EndPoints X/Y - Source not facing Sink
TC EndPoint X
TC EndPoint Y
Sink
Source
Source
Sink
TC EndPoints X/Y are back to back ; they cannot delimit a TC Trail

Figure 2-15 : TC EndPoints X/Y Source and Sink back to back
Sources and Sinks are then in position to cooperate and provide the following services :
-
the Sink can detect a potential multiframe witin the received N1 bytes stream : TC-UNEQ
and Loss of TC alarms are raised if needed,
the Sink extracts data from the received multiframe : IEC Counter, TC-REI, OEI, TC-RDI,
ODI indications, TC-API field,
the Source inserts the same data into the transmitted multiframe,
in case of of incoming AIS signal, VC-AIS information is forced by the Source into the IEC
counter ; this VC-AIS is detected by the Sink and reported as TC-incAIS alarm,
the Source transmits a API : TC-API Sent configurable by the operator,
the Sink detects the received API (TC-API Received) ; this API is compared to the TC-API
Expected (configurable by the operator),
an alarm TC-APIM is reported in case of mismatch between TC-API Expected and TC-API
Received ; this alarm can be inhibited by the operator.
The pair X/Y coherently configured can then take the consequential actions when defaults are detected
by a Sink, by propagating AIS signal in the downwards direction and by generating a RDI indication in
the upwards direction (Sink interacts with local Source) ; consequential actions are taken by a TC
EndPoint only if it has been activated by the operator.

Page A2-68
Nota1 : in order to minimize traffic errors, when a pair of TC Endpoints are set up, it is recommended
to follow the sequence :
-
configure TC EndPoint X,
configure TC EndPoint Y (normally located on another equipment),
activate TC EndPoint X (or Y),
activate TC EndPoint Y (or X).
Nota2 : in order to minimize traffic errors, when a pair of TC Endpoints are removed, it is
recommended to follow the sequence :
-
deactivate TC EndPoint X,
deactivate TC EndPoint Y (normally located on another equipment),
unconfigure TC EndPoint X (or Y),
unconfigure TC EndPoint Y (or X).
The TC Monitoring Point consists of two Monitor entities ; each one of them dealing with one traffic
direction ; each Monitor entity is able to intercept the N1 byte received in its direction, extract from the
multiframe the same informations as a Sink entity ; however the N1 byte is not terminated and it
continues to flow unchanged in the downwards stream.
A TC Monitoring Point is standalone ; it cannot be activated ; it cannot take consequential actions.
The target of a TC Monitoring Point (Point Z) is to localise the source of a defect causing errors on TC
trail delimited by TC EndPoints X and Y ; the operator can walk Point Z alongside the TC trail between
X and Y ; please refer to Figure 2-16.
When a cross-connection (bearing a TCM Point) is removed , the TCM Point is implicitly removed :
desactivation (if EndPoint) and unconfiguration.
A TCM Point can be located on STM-1/4/16 boards ; GFP, GIGE and PDH boards cannot bear a TCM
Point.
A TCM Point cannot be located on a Stm access involved into a MSP (Working side or Protected side).
A TCM Point cannot be located on a Connection Point involved into a SNCP.
TC EndPoint X
TC MonPoint Z
TC EndPoint Y
Source
Mon1
Sink
Sink
Mon2
Source
TC Trail
Figure 2-16 : TC Monitoring Point Z located between TC EndPoint X and TC EndPoint Y

Page A2-69
TC Alarms collected by a Sink/Monitor entity are as following :

Name
ltc
tc-incAIS
Alarm
Loss of Tandem Connection
Incoming AIS
tc-APIM
TC-API Mismatch
tc-rdi
TC-RDI
tc-odi
ODI
tc-rei
TC-REI
tc-oei
OEI
tc-uneq
TC-UNEQ
Meaning
Sink or Monitor is unable to synchronize on multiframe
IEC field is forced to VC-AIS as indication that the
upward Source receives an AIS signal ; the problem is
located upward to the TC trail.
The TC-API Received is different from the TC-API
Expected
TC-RDI indication is raised by the upward Source
because its local Sink detects a fault (in the reverse
direction).
ODI indication is raised by the upward Source because
its local Sink has generated an AIS signal (in the
reverse direction).
TC-REI indication is raised by the upward Source
because its local Sink has propagated (in the reverse
direction) blocks with errors caused by the TC trail
crossing.
OEI indication is raised by the upward Source because
its local Sink has propagated (in the reverse direction)
blocks with errors.
Received N1 byte has value 0 ; there is not a TC
Source in the upwards direction.
Performance Counters collected by Sink/Monitor entity are only IEC Near counter showing BIP errors
caused by the TC trail crossing from the Source.
2.2.9.2 - TCM VC4 Points Management by http

A TCM VC4 Point is associated to VC4 cross-connection.
A VC4 cross-connection can be selected from the Traffic Connection window by means of its output
Connection Point :
-
selection of the output Slot,

selection of the output Connection Point.
Configuration of the TC mode is made by checking check-boxes in the Select the interface
belonging to the TC section of the Tandem Connection Function window as following :
Operator action
Check-box A
Not checked
Checked
Not checked
Checked
Check-box B
Not checked
Checked
Checked
Not checked
Result
TC Configuration State
TC is not configured
TC is configured in non-intrusive mode
TC is configured in intrusive mode at Interface B
TC is configured in intrusive mode at Interface A

Page A2-70
In order to configure a TCM VC4 Point :

-
select the VC4 cross-connection (the output being point A),

click on Configuration for access to Traffic Connection window,
check the Activate TC check-box ,
click on TC Configuration for access to Tandem Connection Function window,
select the mode and the interface of the TC as indicated before,
configure the different items of
the TC (Monitoring check-box, Fault severities,
APIMDisable check-box, Expected TC-API, sent TC-API).
In order to unconfigure a TCM VC4 Point ;

-
select the VC4 cross-connection,

uncheck the Activate TC check-box .
In order to activate/deactivate a TCM VC4 Point ;

-
select the VC4 cross-connection,

click on TC Configuration for access to Tandem Connection Function window,
check/uncheck the Consequent Actions Enable TC check-box .
The Traffic Connection window can also be accessed (only if there is at least one configured TC) :
-
click on a Switch board icon for access to Switch board options,

click on TC List option for acces to TC Configuration window,
select from the TC Interfaces section the TC to amend/display.
The Traffic Connection window shows following items :

-
the Select the interface belonging to the TC section,

the Configuration section gathering following items :
Mon check-box (used if TC alarms/conters are monitored),
Consequent Actions Enable TC check-box,
Fault severity fields (one for each alarm type),
One (intrusive mode) or two (non-intrusive mode) Trace A/B sub-sections,
One (intrusive mode) or two (non-intrusive mode) Fault A/B sub-sections,
One Trace A/B sub-section gathers following items :

-
APIMDisable check-box (tc-APIM fault if mismatch between TC-API Received and TC-API
Expected),
(Trace) Received field : value of received TC-API,
(Trace) Exp. field : value configured for expected TC-API,
(Trace) Sent field : value configured for sent TC-API,
One sub-section Fault A/B gives the list of current active alarms of a Sink/Monitor entity.
The Counters IEC Near window can be made as following :
-
click on a Switch board icon for access to Switch board options,

click on TC Performance option.
This window shows usual performance items.

Page A2-71
2.2.10 - Quality of service for VC4nv GigaEthernet

The GIG-E card allows the association of a gigabit Ethernet flow with a WAN SDH of variable
bandwidth.
If the number of VC4 used on the WAN is strictly lower than 7, then the outgoing bandwidth on
the WAN is lower than the maximum flow on the gigabit Ethernet link and it is advisable to manage the
cases of congestion which can occur.
Moreover, the functions for classification available with the GIG-E card allows to define up to
four classes of traffic.
The ADR2500 eXTra offers several types of parameter settings, adapted to various
applications and various needs for differentiating user flows.
Some operating modes use the flow classification in order to handle the necessary droppings,
but there exists a mode of rejection without discrimination, the QoS None mode, as well as a mode
without loss, the Pause mode used to inform the equipment upstream of the congestion.
Denomination
Bandwidth control
QoS None
Classification
Yes, among 5
criteria
Yes, among 4
criteria
No
Pause Mode
No
WRED
Traffic Loss
Yes
Criteria
Respect of the requested contract of
traffic
Yes
Increasing priorities assigned to
classes
Yes, by RED Use rate of the transmission buffer on
the WAN side
No
Use rate of the transmission buffer on
the WAN side
2.2.10.1 - Classification criteria

This paragraph enumerates various classifications available within the GIG-E card.
The choice of the classification criterion is exclusive for the whole gigabit Ethernet port.
Excepting the "QoS None" mode depicted below, if the incoming flows do not have the expected type
by the selected mode or if no configuration is explicitly associated with an incoming flow, the implicit
class is class 0.
In these modes, the flows of Ethernet administration - frames with a destination address format as 01
80 C2 XX XX XX - are systematically assigned to class 3.
"None" mode :
In this mode, all the frames coming from the gigabit Ethernet port are associated to the same
class.
Thus, they have the same precedence and consequently the elimination is done without
distinction on the flow types.
Using this mode with small WAN flows and important specific traffics (ftp) can induce some
inconvenience for applications with small traffic.

Page A2-72
"802.1d" mode :
The 802.1d mode is based on the priority field of the 802.1Q header. The configuration
screen allows to assign a service class to each "Priority" value.
802.1Q header format
0
Priority
3
4
5
Destination Ethernet address
Source Ethernet address
TPID (Tag Protocol ID)
CFI
VLAN ID
Type/Length
VLAN ID
"IPV4 TOS" mode :

The IPV4 TOS mode is based on the value of the precedence field from the "Type Of
Service" byte in the IP header. The configuration screen allows to assign a service class to each value
of the precedence field.
IPV4 header format
0
4
Ver
IHL
Identification
TTL
Source Address
Destination Address
Options and padding
8
TOS
Protocol
16
Total length
Flags
Fragment Offset
Header checksum
31
4
T
7
0
TOS field format :

0
1
Precedence
3
D
5
R
6
C
The precedence field on 3 bits allows to indicate 8 levels of priority : from 000 for the lowest to 111 for
the highest. Bits D,T,R and C are used to specify the transport mode for the data gram
D:
T:
R:
C:
0 = Normal Delay,
0 = Normal Throughput,
0 = Normal Reliability,
0 = Normal cost,
1 = Low Delay.
1 = High Throughput.
1 = High Reliability.
1 = Minimal cost
"IPV6 TClass" mode :

The IPV6 TClass mode is based on the value of the TClass field (Traffic Class) from the
IPV6 header. The configuration screen allows to assign a service class to each value of TClass
"Priority" included between 8 and 15 - bit 0 forced to 1-

Page A2-73
IPV6 header format (according to the RFC 2460) :

0
Version
4
Traffic Class
Payload Length
IP source address
IP destination address
12
16
31
Flow Label
Next Header
Hop Limit
Traffic Class (TClass) field format :

0
2
Priority
Only the 0 to 3 bits are used to define the 16 levels of priority from 0000 for the lowest, to 1111
for the highest.
"VLanId" mode :
This mode is based on the VLanId field of the 802.1Q header. The configuration screen
allows to assign a service class to each value of the "VlanId" or to a list of VlanId values. The size for
the "Arranges Size" field is in power of 2.
It is possible to define 8 VlanId fields for each four class.
To assign a class of service to a VLanId" or to a group of VLanId :
- select the class of service,
- fill out the First Vlan Id field
- fill out either the Last Vlan Id field or the Range Size field
- click on the Add button
To remove VLanId or a group of VLanId from a class of service :
- select a class of service,
- in the combo box at the bottom of the Item column, select VlanId to be removed
- click on the Delete button
To display all the VLanId configuration
- - select "All Classes".
802.1Q header format :
0
Priority
3
4
5
Destination Ethernet address
Source Ethernet address
TPID (Tag Protocol ID)
CFI
VLAN ID
Type/Length
VLAN ID

Page A2-74
"Balanced" mode :
The Balanced mode is based on the two less significant bits of the VLanId field in the
802.1Q header. It implements a fixed assignment.
VlanId = xx00
VlanId = xx01
VlanId = xx10
VlanId = xx11
-> class 0
-> class 1
-> class 2
-> class 3
It is also associated with a mode for bandwidth allocation preset to a minimum of 25% and to a
maximum of 100% for each class.
2.2.10.2 - Bandwidth management

"Bandwidth" mode :
In the bandwidth mode, classification is used not to define relative priorities but contracts of
bandwidth for each class. The parameters are the minimum and maximum thresholds.
The minimum threshold indicates the percentage of bandwidth guaranteed for the class. The
sum of the minimum thresholds of the four classes cannot exceed 100%.
The maximum threshold indicates the maximum percentage of the bandwidth that will be
allocated. If a class has an incoming flow equal to the outgoing flow and its maximum threshold is to 80
%, it will be allocated only 80% even if the remaining 20% of the bandwidth are lost.
The "Bandwidth" mode carries out, beyond the flows guaranteed minima, a statistical onassignment starting from the flow not allocated with the interval of previous time, which is distributed
equitably between the classes being able there to claim. The rejections related to a going beyond of
the contract of traffic are thus temporal, not statistic.
The configuration screen displays the bandwidth related to the number of VC constituting the
WAN channel.
2.2.10.3 - Congestion management in emission on the WAN

This paragraph enumerates the various methods of congestion management in the GIG-E
card. All the following explanations refer to a context of congestion.
"Red" mode :
This mode, dedicated to the configuration "QoS None", is used to handle frames in a
completely equitable way. As long as the buffer use rate does not reach the "First Point" value, the
frames are accumulated in the buffer without dropping.
Between "First Point" and "Second Point", the recently received frames are dropped
proportionally to the use rate.
When the use rate is above the "Second Point", all frames are dropped, thus making it
possible for the buffer to empty itself.
The rejection with RED makes it possible to use the depth of the outgoing buffer to temporarily
accept an incoming flow with a higher rate than the WAN flow defined before starting to drop
packages. In addition, the statistical and progressive loss leads the higher-layer protocols to control
their outgoing traffic.
Page A2-75
% Loss
100
Buffer use rate

0
First Point
Second Point
"WRed" mode :
In this mode, the frames are dropped according to their class of service : the most important
class is the class 3, least important is the class 0 that is implicit class. The behavior of each class is
defined by the "Profile".
In the case of the "First Profile", below a use rate of 1%, no frame is dropped.
Between 1% and 25%, class 0 frames are dropped proportionally to the buffer use rate, but frames of
other classes are not dropped to in any case.
Beyond 25% of use rate, all frames of class 0 are dropped. An identical reasoning can be held for
classes 1, 2 and 3.
The behavior is the same one in the case of the "Second Profile", only the value of the
thresholds changes.
First Profile
% Loss
100
Class 0
Class 1
Class 2
Class 3
25
Buffer use rate
1
25
50
75
99
Second Profile
% Loss
100
Class 0
Class 2
Class 3
Class 1
25
Buffer use rate
1
69
90
97 99

Page A2-76
"Pause" mode :
In the pause mode, the equipment at the ends of the Ethernet link may send or receive
specific frames to temporarily suspend sending traffic. Operation in pause mode depends on the
capacities being allocated to the equipment : Autonegotiation field and Pause Capability field.
If Pause Negotiation status is equal to Disabled, the pause mechanism is disabled. Thus
the equipment is able neither to handle incoming pause frames nor to send them.
If Pause Negotiation status is equal to Received, the equipment will handle incoming
pause frames.
If the Pause Negotiation status is equal to Sent and depending on the buffer use rate, the
equipment will send a pause frame to ask the other end to suspend its traffic.
If the Pause Negotiation status is equal to Sent & Received, the equipment is able to handle
both sending and reception pause frames.
High Threshold defines the buffer use rate from which the equipment will cease sending
pause frames in order to tell the other end to suspend sending.
Low Threshold defines the buffer use rate under which the equipment will have stop sending
pause frames in order to allow the other end to restart sending.
Stop sending
XOFF frame
XOFF frame
sending
% Loss
100
Buffer use rate

0
Low Threshold
High Threshold
Since the Ethernet Pause frames apply to all flow without distinction, no classification is
associated there.
2.2.10.4 - Congestion management in reception WAN

The flow received from the SDH for a transmission on the gigabit Ethernet port has a simplified
congestion management, limited to the treatment of the pauses frames received from the opposite
Ethernet Local. A buffer is used to prevent from immediate rejections, but those are inevitable if the
request for suspending frame transmission continue.

Page A2-77
2.3 - CARDS PROTECTION
2.3.1 - PDH cards protection

The PDH cards (63E1 or 3E3DS3) are inserted in the TRB 5 to TRIB 8 slots.
A PDH card inserted in TRIB 2 (63E1) or TRIB 1 (3E3DS3) allows to have a function of 1:n (n=4 max)
card protection provided that it is configured in protection mode as following :
- select in the card menu the "PDH Board Protection" item
- check "1:n"
- define the slots of the PDH cards to be protected in "Board to Protect" (the cases to check appear
according to the present PDH cards in the shelf)
The traffic switching on the protection card is automatic since a default (card default, missing card,
auto test defautl) is detected on the working card ; however the return of the traffic on this card,afer
repair, is not automatic : it is necessary to select "Manual Switch to Working" in the operation window.
If the traffic of a defective card has been switched on the protection card, no other traffic of another
card, even defective, can be switched on the help.
If several cards ask to switch their traffic simultaneously on the protection card, the card in the bigger
number slot TRIB will have the priority.
Example : the TRIBn+1 slot est more important than TRIBn.
In the absence of protection and in the event that TRIB 5 to TRIB 8 slots would be occupied, a PDH
card can be inserted in TRIB 2 or TRIB 1 to function in working mode provided that it is configured it as
following :
- select in the card menu the "PDH Board Protection" item
- check "No protection"
- associate at this card a free LTU proposed in the dropdown of the "LTU" window
The choice of operating of the card will be validated by clicking on "Apply".
The traffic alarm "Traffic not provided" is activated if :
- the traffic of a working card in defect switches on a protection card itself in defect
- a working card is in breakdown and that no protection has been configured
This alarm is provided by the working card.
2.3.2 - SWITCH HO/LO card protection

A shelf equipped of two SWITCH HO/LO cards allows to have a function of cards protection 1:1.
If a SWITCH HO/LO card falls in breakdown, (auto test default, fuse default, board missing) the traffc
switches automatically on the other card.
The "Maintenance" menu allows, after repair or replacement, to select the card used for traffic.
This menu offers to the operator a manual switch, no reversible ; this switch will be refused if the
SWITCH HO/LO card is not operational.

Page A2-78
2.3.3 - PSU card protection

According to the type of SWITC HO/LO card, one or two PSU cards are mandatory for the equipment.
If a second or third card is inserted in the shelf, it allows a function of 1:1 or 1:2 card protection.
As long as no problem appears, loads of power supply are distributed on the present cards ; if one of
them breaks down, loads are automatically balanced on the one or other cards.
2.4 - SUB-ASSEMBLY REPLACEMENT PROCEDURES

REMINDERS :
Whenever handling a card, be sure to wear a tightly secured antistatic

bracelet on your wrist connected to ground.
To clean optical connectors, use a pressurized air can.
2.4.1 - Replacement of an Interface card

Remarks :
Alarms will appear when a card is extracted from the shelf. To avoid the alarms and ALA 1
and ALA 2 loops from being fed back, the card should be declared as out of service.
Each module can be extracted or inserted without intervening on the other modules or on
their wiring. The only disturbance will concern the traffic in the concerned module.
Procedure :
The procedure described below can be applied, unless otherwise specified, to all the cards in
the equipment.
1. Switch any possible protected traffic to the redundant card. If the yellow "Traffic" indicator
LED goes off, the replacement will not result in any disturbance.
2. Set the card "out of service" using the web browser.
3. Remove the external connections from the front panel of the card.
NOTE :
When the external optical fibers are disconnected, install the protected
covers on the connectors.
4. Unscrew and remove the card observing the mandatory safety measures relative to
electrostatic discharges.
5. Place the card in an antistatic bag.
6. Remove the new card from its antistatic bag.
7. Carefully insert the card in its slot while observing the mandatory safety precautions relative
to electrostatic discharges and secure it.
8. Perform the connections on the front panel of the card.
NOTE :
For the optical cards, remove the protective covers from the connectors.
9. Configure the card if necessary and activate the card.

Page A2-79
2.4.2 - Replacement of a SWITCH HO/LO card

REMINDER :
If you do not have a redundant SWITCH HO/LO card, this operation

will result in total interruption of traffic.
WARNING :
Never replace a SWITCH HO/LO card if a CTRL-2G card is not in

position or has failed (STATUS indicator LEDs off) : inserting a
SWITCH HO/LO card in the shelf without a CTRL-2G card can result
in interruption of traffic.
Replacement procedure if a redundant SWITCH HO/LOcard is present :

1. Switch protected traffic to the redundant SWITCH HO/LOcard.
2. Wait for the yellow "traffic" indicator LED to go off. When the traffic indicator LED is off, the
card can be replaced without causing any disturbance.
3. Set the card "out of service" on the web browser.
7. Carefully insert the new card in its slot observing the mandatory safety measures relative to
electrostatic discharges and secure it.
8. Activate the card.
9. Wait for 2 or 3 minutes, duration for the holdover automaton to validate the current
synchronization source.
2.4.3 - Replacement of a PSU module

Procedure :
1. Using the maintenance menu, set the PSU module to be replaced to "Off".
NOTE :
If the PSU modules are not to the number of three, the transition to "Off"
will be rejected.
2. Wait for the green indicator LED to go off and the red indicator LED to come on.
3. On the MMI, the maintenance panel will be displayed (refresh the shelf view).
4. Unscrew and remove the PSU module observing the mandatory safety measures relative to
5. Place the module in an antistatic bag.
6. Remove the new module from its antistatic bag.
7. Insert a new module observing the mandatory safety measures relative to electrostatic
discharges and secure it.
NOTE : The new module is set into service automatically once inserted.

Page A2-80
Remarque :
If the equipment receives a SWITCH HO/LO card and if one only PSU card is inserted in the
shelf, the equipment went to degraded mode.
To leave this degraded mode, see the chapter 6 "DEGRADED MODE"
2.4.4 - Replacement of a CTRL-2G card

The CTRL-2G card can be extracted or inserted without disturbing the traffic transiting through an
ADR2500 eXtra.
Without a CTRL-2G card in the shelf, the automatic control functions relative to protection,
synchronization of the equipment and management of the shelf assembly are not fulfilled.
Exception : Even without a CTRL-2G card in place, switchover from a failing in traffic SWITCH
HO/LO card to its protection card is achieved. A CTRL-2G card is needed to put any card type into
service though.
If the CTRL-2G card inserted is different from that previously removed and no power
supply cutout has occurred since the card was extracted, the equipment configuration will
be preserved in its original condition. A date and time set operation is however required to
complete the equipment configuration procedure.
If a new CTRL-2G card is inserted in a shelf which is not powered up, the configuration
saved in the CTRL-2G card will be applied to the equipment on power up. A date and time
set operation is however required to complete the equipment configuration procedure.
Procedure :
1. Remove the external connections on the front panel of the card.2
5. Carefully insert the card in its slot observing the mandatory safety measures relative to
7. Configure the card if necessary.
Remark :
If the four LEDs permanently flash, this means the card went to degraded mode
To leave this degraded mode, see the chapter 6 "DEGRADED MODE"

Page A2-81
2.4.5 - Replacement of a CCU-2G card

Warning : As the shelf power supply connector is located on the CCU card, it is mandatory to
disconnect the powering cable from the POWER/ALM connector before CCU card extraction, to
prevent any risk of contact with hazardous voltages while manipulating the card.
Procedure :
1. Remove the external connections on the front panel of the card.
5. Carefully insert the card in its slot observing the mandatory safety measures relative to
7. Configure the card if necessary.
2.4.6 - Replacement of FAN-2G module

The FAN-2G module contains three redundant FAN-2G to secure adequate ventilation should
any of the fans fail. Fan failures are detected on the card by monitoring the current consumed.
As soon as a default is detected on one of fans or on the power supply, it is necessary to replace
the FAN-2G module.
The FAN-2G module can be removed and replaced with no disturbance to traffic.
Procedure :
1. Unscrew and remove the module observing the mandatory safety measures relative to
2. Place the module in an antistatic bag.
3. Remove the new module from its antistatic bag.
4. Carefully insert the module in its position observing the mandatory safety measures relative
to electrostatic discharges and secure it.
2.4.7 - Preventive maintenance

In order to avoid a deterioration in the efficiency of ventilation, it is advised to be careful that the
grids of ventilation and blades of the modules FAN-2G are not fouled. A regular check and, if
necessary, a dusting is recommended.

Page A2-82
3 SPARE PARTS AND CABLES
3.1 - LIST OF NO ROHS ADR2500 EXTRA ITEMS

Mnemonic
Name
No rohs code
ADR2500 EXTRA SHELF
251 313 627
ADR2500 EXTRA SHELF NO LTU
252 711 385
FAN MODULE 2G
251 313 700
KIT FACIA FAN SAGEM
288 069 950
SWITCH COVER
251 089 333
PSU COVER
251 089 346
TRIB/LINE COVER
251 089 354
1 LTU cover
1 LTU COVER
251 311 248
3 LTU cover
3 LTU COVER
251 311 219
LTU21E120
21E120 LINE TERMINATION UNIT
251 313 635
LTU21E75
251 313 648
3E3DS3 LINE TERMINATION UNIT
251 313 656
PSU-2G
POWER SUPPLY UNIT 2G
251 253 537
PSU-160
POWER SUPPLY UNIT 160 W
251 515 677
CCU-2G
COMMON CONNECTION UNIT 2G
251 313 680
CTRL-2G
CONTROL UNIT 2G
251 313 698
AUXILIARY UNIT
251 049 173
SWITCH HO/LO
64 VC4 HO/LO SWITCH UNIT
251 253 529
SW32HOLO
251 607 962
63E1 TRIBUTARY UNIT
251 313 677
63E1FA
63E1TRIBUTARY UNIT FRONT ACCESS
252 485 331
3E3DS3
3E3DS3 TRIBUTARY UNIT
251 313 669
3x34/45 TRIBUTARY UNIT FRONT

ACCESS
251 943 074
4ERE
4X STM-1 ELECTRICAL UNIT
251 049 152
4xS1.1
4X STM-1 S-1.1 OPTICAL UNIT
251 524 259
4xL1.1
4X STM-1 L-1.1 OPTICAL UNIT
251 530 434
2xL1.1
251 705 057
4xL1.2
251 530 447
ADR2500 eXtra
Shelf
Shelf without LTU
FAN-2G
KIT FACIA FAN
SWITCH HO/LO cover
PSU cover
Trib/line cover
Cards
LTU3E3DS3
AUX
63E1
3E3DS3FA
Table 3-1 : List of no rohs ADR2500 eXtra items

Page A3-1
3 SPARES PARTS AND CABLES
Mnemonic
Name
No rohs code
1xL1.2
251 632 473
4xMM1
4X STM-1 MM1 OPTICAL UNIT
251 735 360
4XSTM1 SFP UNIT
252 578 425
S4.1
STM-4 S-4.1 OPTICAL UNIT
251 049 149
L4.1
STM-4 L-4.1 OPTICAL UNIT
251 122 550
L4.2
251 196 005
STM4 SFP UNIT
252 578 446
L16.1
251 049 128
L16.2
251 483 164
L1550.92
251 049 131
L1547.72
251 070 735
L1549.32
251 070 748
L1552.52
251 070 756
U16.2
STM-16 OPTICAL UNIT for booster
251 120 861
STM16 SFP UNIT
252 578 438
GIG-E SX (**)
GIG-E SX UNIT
251 068 024
GIG-E LX
GIG-E LX UNIT
251 560 362
GIG-E ZX
GIG-E ZX UNIT
251 582 884
1GE-DM ZX
1GE DUAL MODE ZX UNIT
252 583 398
2GE-DM ZX
252 590 893
2GE-DM-SFP
2GE DUAL MODE SFP UNIT
252 668 670
GFP150 eXtra
GFP150EXTRA PLATINUM
251 435 209
19 IN KIT
19 IN MOUNTING KIT
251 436 793
ETSI KIT
ETSI MOUNTING KIT
251 436 805
OPTICAL BOOSTER +14 DBM
251 125 832
MUX 10000 T
251 156 410
MUX 10000 A
251 163 949
4xSTM1-SFP (*)
STM4-SFP (*)
STM16-SFP (*)
Adaptation Kits
Units
Table 3-2 : List of no rohs ADR2500 eXtra items

(*) The STMx-SFP cards will be equipped with the choice with one of the types of codified
SFP modules. Table 3-4 : List of rohs optical modules of ADR2500 eXtra
(**) "GIG-E SX" corresponds to previously named GIG-E card of ADR 2500c

Page A3-2
3.2 - LIST OF ROHS ADR2500 EXTRA ITEMS
Mnemonic
Name
No rohs code
FAN MODULE 2G SAGEM
252 727 817
LTU21E120
252 728 273
LTU21E75
252 728 294
3E3DS3 LINE TERMINATION UNIT
252 728 306
PSU-160
POWER SUPPLY UNIT 160 W
252 727 838
CCU-2G
COMMON CONNECTION UNIT 2G
252 728 210
CTRL-2G
CONTROL UNIT 2G SAGEM
252 763 339
AUXILIARY UNIT
252 728 249
SWITCH HO/LO
252 728 228
SW32HOLO
252 758 705
63E1 TRIBUTARY UNIT
252 728 231
63E1FA
63E1TRIBUTARY UNIT FRONT ACCESS
252 794 553
3E3DS3
3E3DS3 TRIBUTARY UNIT
252 790 203
3x34/45 TRIBUTARY UNIT FRONT

ACCESS
252 790 191
4X STM-1 ELECTRICAL UNIT
252 728 260
4XSTM1 SFP UNIT
252 790 211
STM4 SFP UNIT
252 790 224
252 728 380
STM16 SFP UNIT
252 790232
GIG-E ZX UNIT
252 728 314
1GE-DM ZX
252 790 183
2GE-DM ZX
252 790 170
2GE-DM-SFP
2GE DUAL MODE SFP UNIT
252 790 245
GFP150 eXtra
GFP150EXTRA PLATINUM
252 728 252
19 IN KIT
19 IN MOUNTING KIT
252 759 864
ETSI KIT
ETSI MOUNTING KIT
252 759 905
ADR2500 eXtra
FAN-2G
Cards
LTU3E3DS3
AUX
63E1
3E3DS3FA
4ERE
4xSTM1-SFP
STM4-SFP
L16.2
STM16-SFP
GIG-E ZX
Adaptation Kits
Table 3-3 : List of rohs ADR2500 eXtra items

Page A3-3
Mnemonic
Name
No rohs code
SFP DDM S-1.1 MODULE
252 709 939
SFP DDM L-1.1 MODULE
252 586 245
252 709 947
SFP DDM S-4.1 MODULE
252 709 950
252 709 905
252 709 918
252 709 968
252 586 373
SFP DDM SX MODULE
252 791 015
SFP DDM LX MODULE
252 791 002
SFP DDM ZX MODULE
252 791 023
Optical modules
Table 3-4 : List of rohs optical modules of ADR2500 eXtra
3.3 - LIST OF AVAILABLE CABLES

Card
LTU 21E75
Name
Length
Code
2,5 m
12 m
251 581 853

251 581 874
2,5 m
12 m
251 581 808

251 581 829
E1 INPUT or E1 OUTPUT
75 ohms SUB D St 21x2 Mbit/s In or
Out
( cable)
LTU 21E120
63E1FA
E1 INPUT or E1 OUTPUT
LTU3E3DS3
3E3DS3FA
TR or REC 1x155 Mbit/s 75 ohms

1.0/2.3
( cable)
2,5 m
12 m
55 670 592
55 670 594
TR or REC 3x155 Mbit/s 75 ohms

1.0/2.3
( cable)
2,5 m
12 m
55 670 602
55 670 604
120 ohms SUB D St 21x2 Mbit/s In

or Out
( cable)
Table 3-5 : List of available cables

Page A3-4
Card
CCU-2G
Name
Length
Code
SYNC SYNCHRO 120
2,5 m
251 008 309
( cable)
12 m
251 008 320
SYNC BNC SYNCHRO 75

(adapter)
30 cm
251 118 155
LOOPS (GTR + TS)
2,5 m
6 013 628
( cable)
12 m
6 013 161
Toward PAPA (whole cable)
3m
251 361 272
Free ( cable)
3m
251 361 285
1,8 m
4 980 214
Direct connection to a HUB
3m
55 670 422
Cross over connection to a PC
3m
55 670 610
V11 access to ARDAX/EOW300
3m
55 670 253
2,5 m
12 m
55 670 602
55 670 604
Straight-through cable
3m
55 670 422
Cross-over cable
3m
55 670 610
(whole cable - one T3 input / one T4

output)
POWER
CTRL-2G
COMM COM VT100

ETH Ethernet
AUX
(Cable supplied with VDS

equipment)
4ERE
TR or REC
4x155 Mbit/s 1.0/2.3 75 ohms
( cable)
GFP150
eXtra
ETH Ethernet
Optical cards 10DB 1,3/1,5m SC/PC

Optical attenuator
187 835 698
10DB 1,3/1,5m LC/PC

Optical attenuator
TR or REC - Optical jumper
SC-PC/FC-PC
2,5 m
3,4 m
4,6 m
5,8 m
7m
8,2 m
9,4 m
12 m
15 m
20 m
251 035 997

251 036 001
251 036 019
251 036 022
251 036 030
251 036 043
251 036 051
251 036 064
251 036 072
251 036 085

Page A3-5
Card
Name
TR or REC - Optical jumpers
SC-PC/FC-PC with 10 db attenuator
TR or REC - Optical jumper
SC-PC/SC-PC
TR or REC - Optical jumber

SC-PC/SC-PC with 10 dB attenuator
TR or REC (STMn-SFP cards)
Optical jumper LC-PC/LC-PC
TR or REC (STMn-SFP cards)

Optical jumper LC-PC/SC-PC
TR or REC Multimode optical

jumber SC-PC/SC-PC
Length
Code
2,5 m
5,8 m
12 m
20 m
251 091 700

251 091 656
251 091 669
251 091 648
1,5 m
2,5 m
3,4 m
4,6 m
5,8 m
7m
8,2 m
9,4 m
12 m
15 m
20 m
251 035 872

251 035 880
251 035 893
251 036 209
251 036 212
251 036 220
251 036 233
251 036 241
251 036 251
251 036 262
251 036 275
2,5 m
5,8 m
12 m
20 m
251 091 627

251 091 635
251 091 677
251 091 698
2.5 m
5m
10 m
15 m
20 m
50 m
251 559 377

251 559 504
251 559 517
251 559 525
251 559 567
251 559 570
2.5 m
5m
10 m
15 m
20 m
50 m
251 454 262

251 454 283
251 454 296
251 454 402
251 454 410
251 454 423
2,5 m
4,6 m
7,0 m
251 157 433

251 157 446
251 157 454

Page A3-6
4 - TECHNICAL CHARACTERISTICS
4 TECHNICAL CHARACTERISTICS
EQUIPMENT
Optical characteristics
(see 1.3.8 Connection of STM-1 / STM-4 / STM-16)

optical access points
Mechanical characteristics
Height
Width
Depth
Weight
Protection Index (PI)
SFP optical modules
14U (623 mm)

19" or ETSI (446 mm)
238 mm
11,6 kg empty + 2,3 kg (two brackets) ; 26 kg for
maximum configuration
Corresponds to PI of used rack
Small Form factor Pluggable Transceiver MultiSource
Agreement 14 Sept 2000
See
Consumption
Table 4-3
Environment characteristics
Mechanical
Climatic condition
Operating temperature
Extended operating temperature
Transport and storage temperature
Relative humidity
Electrical
Interference voltage (radioelectric
frequency emissions)
Safety
Power
ETS 300 019

ETS 300 019
- 5C to + 45C
-25 C to + 55C (MTBF [Mean Time Between
Failure] slightly downgraded)
- 40C to + 70C
< 85%
NF EN 300 386 (April 2000)
NF EN 55022
NF EN 60950-1 (Avril 2002)
ETS 300 132-2 (equipment is SELV)
Table 4-1 : Technical characteristics of ADR2500 eXtra

Page A4-1
EQUIPMENT
Predicted reliability (1)
FDP
FAN-2G
LTU21E120
LTU21E75
LTU3E3DS3
PSU-2G
PSU-160
CCU-2G
CTRL-2G
AUX
SWITCH HO/LO
SW32HOLO
63E1
63E1FA
3E3DS3
3E3DS3FA
4xS1.1, 4xL1.1, 4xL1.2, 4xMM1
2xL1.1
1xL1.2
4ERE
4xSTM1-SFP (without optical module)
SFP S1.1 Module (2)
SFP L1.1 Module (2)
SFP L1.2 Module (2)
S4.1, L4.1, L4.2
STM4-SFP (without optical module)
SFP S4.1 Module (2)
SFP L4.1 Module (2)
SFP L4.2 Module (2)
L16.1, L16.2
L16.2+, U16.2
STM16-SFP (without optical module)
SFP L16.1 Module
SFP L16.2 Module
GIG-E SX, GIG-E LX, GIG-E ZX
1GE-DM-ZX
2GE-DM-ZX
2GE-DM-SFP (without optical module)
SFP SX Module (2)
SFP LX Module (2)
GFP150 eXtra
-6
3.73 10
-6
5.65 10
-6
0.25 10
-6
0.25 10
-6
0.14 10
-6
2.58 10
-6
1.44 10
-6
0.41 10
-6
0.65 10
-6
0.11 10
-6
2.10 10
-6
1.71 10
-6
0.58 10
-6
0.90 10
-6
0.52 10
-6
0.57 10
-6
3.67 10
-6
1.92 10
-6
1.07 10
-6
0.39 10
-6
0.24 10
0.26 10-6
0.35 10-6
0.39 10-6
-6
1.08 10
-6
0.18 10
-6
0.27 10
-6
0.31 10
-6
0.75 10
-6
0.99 10
-6
0.93 10
-6
0.41 10
-6
0.95 10
-6
0.95 10
-6
2.72 10
-6
1.93 10
-6
2.80 10
-6
1.08 10
-6
0.13 10
-6
0.17 10
-6
1.08 10

(1) The predicted reliability computations have been realized with the RAM COMMANDER
software Release 7.2 according to the UTE C 80-810 RDF 2000 standard under ambient
temperature conditions of 25C (with ventilation conditions ensuring an average internal
temperature in the rack not exceeding 40C) and precise conditions relative to the
environment (on ground, fixed and protected), qualification and age of the components. Any
changes to these hypotheses will provide different results.
(2) Predicted reliability calculated for a case temperature of 40C
Page A4-2
EQUIPMENT
Power consumption (3) per sub-assembly (measured on 48V power supply)
LTU21E120
LTU21E75
LTU3E3DS3
CCU-2G + FAN-2G
CTRL-2G
AUX
SWITCH HO/LO
SW32HOLO
63E1
63E1FA
3E3DS3
3E3DS3FA
4xS1.1
4xL1.1
2xL1.1
4xL1.2
1xL1.2
4ERE
4xMM1
4xSTM1-SFP (equipped with four
optical modules)
S4.1
L4.1
L4.2
STM4-SFP (equipped with one
optical module)
L16.1
L16.2
L16.2+,
U16.2
STM16-SFP (equipped with one
optical module)
GIG-E SX, LX, ZX
1GE-DM-ZX
2GE-DM-ZX
2GE-DM-SFP (equipped with two
optical modules)
GFP150 eXtra
3.2 W
3.2 W
1.7 W
11 W
4.6 W
1.1 W
34.5 W
21.6 W
6W
15 W
7.8 W
9.3 W
5.1 W
5.1 W
3.2 W
5,1 W
2.4 W
12.5 W
5.1 W
5W
3.7 W
3.7 W
3.7 W
3.7 W
8.0 W
8.5 W
9.5 W (4)
9.5 W (4)
8W
22 W
16.3 W
18.6 W
18.8 W
14.6 W

(3) These power consumption data are typical values and can be used to evaluate the
dissipation. 20% should be added when estimating the peak values governing sizing of the
power supply devices. This provides for transient variations in consumption and variations in
efficiency of the converter as a function of the total power.
Caution : an additional 10% should be added if a 72V power supply is used.
(4) This consumption can reach the max value of 12,5 W at laser power up, during its
operation temperature acquisition (for less than 5 seconds).

Page A4-3

Page A4-4
5 - START-UP GUIDE
5 START-UP GUIDE
Introduction
Thank you for acquiring the ADR2500 eXtra equipment.
The start-up procedure is supplied with the equipment to help you, using examples, to configure it in accordance with the topology of the network to
be built.
5.1 - INSTALLING THE EQU IPMENT

a) Unpack the equipment
b) Insert and screw the cards into the slots used
c) Connect the power cable and power up the equipment
d) After a few seconds, check that the green STATUS LED of the Controller card comes on steady

Page A5-1
5 - START-UP GUIDE
5.2 - CONNECTING TO AN A DR2500 EXTRA

Minimum PC characteristics
Description
Configuration 1
Processor
Memory
Display
Configuration 2
450 MHz Pentium III

64 MB
128 MB
1024x768
RS232 serial interface
SUB-D straight cable

9pts Male / Female
Ethernet 10 Base T network card
RJ45 crossed Ethernet

cable
Interfaces
Operating system
Observations
Windows NT4 / 2000
Windows XP
HyperTerminal for Windows

Softwares
Web Browser : Internet Explorer1 5.5 (*)
(*) The operating PC can be equipped with Internet Explorer 6.0 (delivered release with Windows XP)

Page A5-2
5 - START-UP GUIDE
In order to be managed, the ADR2500 eXtra subrack must have the Equipment address and the Ethernet port address configured in two different subnetworks.
The Equipment and Ethernet port addresses are configured using the Windows HyperTerminal application.
Connect the equipment's "COMM" port to an unused "COM" port of the PC using the 9pts Male / Female SUB-D straight cable
Power up the PC
Start Windows and run the HyperTerminal application

(Menus: Start/Programs/Accessories/HyperTerminal)
Give a name and select an icon for the connection then apply the choices
Select the PC's "COM" port that is connected to the equipment then apply the choice
Configure the port parameters according to the characteristics below then apply the settings
Bits per second

Data bits
Parity
Stop bits
Flow control
:
:
:
:
:
19200
8
None
1
None
Save the connection settings. The next time you will run the HyperTerminal, just click on the connection icon to connect to the
equipment.
Press "ENTER" twice on the keyboard

The MAIN MENU window appears on screen.
Configuring the Equipment address

The equipment address will be used to notify alarms and events to the Manager. This address is mandatory when using Unnumbered PPP links ( In the
example below, the Equipment address is 192.168.114.30 ).

Page A5-3
5 - START-UP GUIDE
Follow the instructions below to configure the Equipment address
Choose menu 1 and

confirm by pressing
"ENTER" key on the
keyboard.

Page A5-4
5 - START-UP GUIDE
Answer the questions

and confirm each one
by pressing "ENTER"
key on the keyboard.
In this example, the
Equipment address
is 192.168.114.30
The IP address can be input with or without non-significant "0" :

192.168.114.30 or 192.168.114.030
The equipment will be restated after the configuration of the Ethernet port address.

Page A5-5
5 - START-UP GUIDE
Configuring the Ethernet port
This port's address must be located in the same network as the PC's Ethernet port one (in the example given below, the sub-network address is
135.11.114.8 and the sub-network mask is 255.255.255.252).
NOTE:
With Windows 9x, the PC's address can be viewed by selecting (right-click) Properties of the Network Neighborhood icon, then (left-click)
Properties of the TCP/IP component (TCP/IP -> "Network Card Name").
With Windows NT, the PC's address can be viewed by selecting (right-click) Properties of the Network Neighborhood icon, then (left-click)
Properties of the TCP/IP component (TCP/IP protocol).
With Windows 2000/XP, the PC's address can be viewed by selecting, in succession, (right-click) Properties of the My Network Places
icon, Properties of the Local Area Connection icon, then (left-click) Properties of the TCP/IP component (Internet Protocol (TCP/IP)).
Follow the instructions below to configure the equipment's Ethernet port
Choose menu 2 and

confirm by pressing
"ENTER" key on the
keyboard.

Page A5-6
5 - START-UP GUIDE
Answer the questions

and confirm each one
by pressing "ENTER"
key on the keyboard.
In this example, the
address of the unit's
Ethernet port is
135.11.114.10
The IP address can be input with or without non-significant "0" :

135.11.114.10 or 135.011.114.010
) After you type y to confirm the question Save interface parameters (y/n)? there are a few seconds delay before display of the
sentence You must restart this equipment for modifications to take effect.
After restarting the equipment, the word Password: appears at the top left of the window. Close HyperTerminal application.
The equipment can now be managed by an HTTP browser.
Page A5-7
5 - START-UP GUIDE
Managing the equipment

Example:
The equipment is managed by an HTTP browser.
Connect the Controller card's "ETH" port to the PC's Ethernet card using the RJ45 crossed Ethernet cable
) The yellow LED of the Controller card's "ETH" connector must go on.
Run the HTTP browser

) If the display is set to 800x600, select "Smaller" with INTERNET EXPLORER 5.x or superior. (Consult the help menu of the HTTP
browser to set the font size)
On the home page, complete the "Address" field with the Equipment address (192.168.114.30)
The window Welcome on the SAGEM ADR2500 eXtra's site appears on the screen. By default , there is no Password; click on "Apply"
The window Shelf view appears on the screen.
To be able to manage the equipment, consult the help menu by clicking on the Help link of the main window.

Page A5-8
5 - START-UP GUIDE
5.3 - CONFIGURING A PPP
PORT
A PPP (Point to Point Protocol) port of an equipment must be configured when extending a network, just as for modification of the Equipment
address and the Ethernet port, using the HTTP browser.
In the example below, the instructions are given for configuring the PPP2 port. Configuration of the PPP1 and PPP3 to PPP34 ports is identical to
the PPP2 port.
Connect the Controller card's "ETH" port to the PC's Ethernet card using the RJ45 crossed Ethernet cable
) The yellow LED of the Controller card's "ETH" connector must go on.
Run the HTTP browser
In the home page, complete the "Address" field with the Equipment address (192.168.114.30)
The window Welcome on the SAGEM ADR2500 eXtra's site appears on screen. By default, there is no Password; click on "Apply"
The window Shelf view appears on screen.
Click on the Controller cards ETH port then on the Interfaces Configuration link to configure the equipment's PPP2 port
Click on the Apply button then

validate the reboot prompt with the
Restart Now button.
After restarting the equipment, the
PPP2 port is configured.

Page A5-9
5 - START-UP GUIDE
5.4 - VIEWING THE ROUTIN G
CONFIGURATION
Click on the Routing Table link to view the equipment's routing configuration.
Example :

Page A5-10
5 - START-UP GUIDE
5.5 - BUILDING A POINT-T O - POINT LINK

This chapter describes the IP configuration of the interfaces for a bus link using an example.
For each equipment, you can configure the Ethernet port, the Equipment address and the 34 PPP (Point to Point Protocol) software ports from
PPP1 to PPP34 (DCCr or DCCm). PPP1 software port is assigned to the physical port LINE1, PPP2 software port is assigned to the physical port LINE2
and the PPP3 to PPP34 software ports are assigned to one of the 32 physical ports corresponding to the slots TRIB1 to TRIB8. You can also assign two
VC12 channels, P#1 and P#2, to each PPP3 to PPP34 software ports.
Example:
Refer to the chapter Connecting to an

ADR2500 eXtra to configure the Ethernet
port and the Equipment address of each
equipment.
Refer to the chapter Configuring a PPP
port to configure the PPP ports of each
The gateway adress matches the Ethernet

port address of the equipment opposite the
PC.
The two ADR2500 eXtra units can be managed by an HTTP browser.
Refer to the chapter Connecting to an ADR2500 eXtra for managing the equipment by the HTTP browser.

Page A5-11
5 - START-UP GUIDE
5.6 - BUILDING A BUS LINK

This chapter describes the IP configuration of the interfaces for a bus link using an example.
Example:

equipment.
The three ADR2500 eXtra units can be operated using an HTTP browser.
Refer to the chapter Connecting to an ADR2500 eXtra for operating the equipment with the HTTP browser.

Page A5-12
5 - START-UP GUIDE
5.7 - BUILDING A RING

This chapter describes the IP configuration of the interfaces for a ring network using an example.
Example:

equipment.
i
t
The three ADR2500 eXtra units can be managed by an HTTP browser. The management links are secured by the OSPF protocol.
Refer to the chapter Connecting to an ADR2500 eXtra for managing the equipment by the HTTP browser.
Page A5-13
5 - START-UP GUIDE
5.8 - MANAGING EQUIPME NT THROUGH THE NETWORK OF A DIFFERENT SUPPLIER

This chapter describes the IP configuration of the interfaces for a network whose management links pass through a different manufacturers
equipment.
Example:
Refer to the chapter Connecting to an ADR2500 eXtra to configure

the Ethernet port and the Equipment address of each equipment.
Refer to the chapter Configuring a PPP port to configure the PPP
ports of each equipment.
Refer to the next page for more details on configuring the PPP3 port of
ADR2500 eXtra N3 and the PPP3 port of ADR2500 eXtra N4.
Page A5-14
5 - START-UP GUIDE
Details on configuring the PPP3 port of ADR2500 eXtra N3 and the PPP3 port of ADR2500 eXtra N4
Choice of the management VC12
1. The choice of the VC12 i is restricted to 20 first ones VC12 of a
TUG-3 and the VC12 i+1 is unusable.
2.
Only the VC12 numbers whose next one is free are proposed in
the ports list.
Configuring the PPP3 port of ADR2500 eXtra N3

3. Configure the PPP3 port with HTTP browser
Refer to the chapter Configuring a PPP port for the procedure
4. Create a connection with the HTTP browser between the P#1
port and the T2:4#1_62 port of Trib2 Port4.
Consult the ADR2500 eXtra help menu to create a connection
by clicking on the HELP link of the main window.
Configuring the PPP3 port of ADR2500 eXtra N4
1. Configure the PPP3 port with HTTP browser
Refer to the chapter Configuring a PPP port for the procedure
2. Create a connection with the HTTP browser between the P#1
port and the T1:1#1_62 port of Trib1 Port1.
Consult the ADR2500 eXtra help menu to create a connection by
clicking on the HELP link of the main window.

Page A5-15
5 - START-UP GUIDE

Page A5-16
6 - DEGRADED MODE
6 DEGRADED MODE
6.1 - DEFINITION
The degraded mode is an operation mode in which the CTRL-2G card software can switch when
starting, after a CTRL-2G card replacement (maintenance) or a shelf power supply cut.
The software switches in this mode on at least one of following cases :
- incompatibility between the CTRL software and the FPGA codes of the GIG-E pack or
between the CTRL software and the GIG-E software code in CTRL Flash (missing or
incompatible code in Flash)
- incompatibility between the CTRL software and the FPGA codes of the GFP150 eXtra pack
or between the CTRL software and the GFP150 eXtra software code in CTRL Flash (missing
or incompatible code in Flash)
- incompatibility between the CTRL software and the current shelf configuration (database in
the CCU-2G card memory)
- incompatibility between the CTRL software and the shelf current states memory ("shelf hot
data" in the CCU-2G card memory) ; these data persist on CTRL-2G card extraction but on
shelf power supply cut
- FPGA code change between already loaded codes in shelf cards and present codes in
CTRL-2G card Flash
- a GIG-E software code change between already loaded codes in shelf GIG-E cards and
present code in CTRL-2G card Flash
- a GFP150 eXtra software code change between already loaded codes in shelf GFP150 eXtra
cards and present code in CTRL-2G card Flash
- only one operational PSU associated to a SWITCH HO/LO card (minimum 2 cards are
mandatory)
The CTRL software switches in this mode in order to avoid to :
-
loss the current shelf configuration

loss the informations of the shelf current states
switch to a default card
load again a FPGA code or a GIG-E software code or a GFP150 eXtra software code
and so, to avoid a temporarily or definitely transmission cutting

These cases correlate, either to CTRL-2G card replacement by a card with not updated Flash software
or to momentary shelf power supply cut when the software or the FPGA codes in CTRL Flash are not
all updated.

Page A6-1
6 - DEGRADED MODE
To go out of this degraded mode :

- in case of software incompatibility, the operator must locally act on the equipment by updating
the software codes or the FPGA codes in CTRL-2G card memory Flash or by forcing the
software start-up,
- in case of only one operational PSU associated to a SWITCH HO/LO card, insert a second
one or change the failed card. Software automatically reset until 2 PSU cards are in service.
6.2 - CHARACTERIZATION
In case of software incompatibility, the switch on this degraded mode is indicated by the four LEDS of
CTRL-2G card which flash (switched on red status + minor alarm LEDS, then switched on green status
+ major alarm LEDS).
The state of major and minor alarms output loops is not modified.
At VT100, by pressing "enter" touch, the switch reason is displayed.
In case of only one operational PSU, equipment reset every 20 seconds.
6.3 - POSSIBLE CAUSES

The causes are indicated in the "Definition" paragraph.
Nine cases are managed by the CTRL software ; at each time, a message is displayed on the VT 100
terminal which is connected on the CTRL-2G card COMM interface.
1) - The CTRL software code is not compatible with the FPGA codes of the Shelf, GIG-E or GFP150
eXtra packs in Flash or some FPGA codes are missing in Flash.
The CTRL software version is not compatible with Fpga codes in Flash
If you start CTRL software, incompatible or missing Fpga codes
will not be loaded and some cards will be declared failed!!!
2) -The software code CTRL is not compatible with the GIG-E or GFP150 eXtra software codes or one
of these software codes is missing in Flash (only if a GIG-E card or a GFP150 eXtra card is configured
in the shelf).
The CTRL software version is not compatible with Soft. codes in Flash
If you start CTRL software, incompatible or missing Soft. codes
will not be loaded and some cards will be declared failed!!!
3) - The software code of the inserted CTRL-2G card is not compatible with the Shelf Database ; some
parts of Database can be reinitialized, if continue.
This case correlates to an older software CTRL than this which has generated the Shelf Database and
which is not compatible with this database
For example, if a CTRL-2G card with a level 2 CTRL software is replaced by a level 1
The Shelf Database is not compatible with CTRL software of the new CTRL-2G card
If you start CTRL software, part of Database (Configuration) will be lost !!!
and the transmission will be broken up to new configuration

Page A6-2
6 - DEGRADED MODE
4) -The software code of the inserted CTRL-2G card is compatible with the Shelf Database provided
some parts of this database are converted.
This case correlates to a more recent software CTRL than this which has generated the Shelf
Database and which must convert. some parts of this database
If conversion is accepted by the operator, then if later the previous CTRL-2G card (level 1) is inserted
again, the converted parts of database will be reinitialized (case 3).
The Shelf Database is compatible with CTRL software of the new CTRL-2G card
But will be convert to a new format ; if you continue and convert the database
you will not insert the previous CTRL-2G card without breaking part of database !!!
5) -The software code of the inserted CTRL-2G card is not compatible with the Shelf Hot Data ; some
parts of Hot Data can be reinitialized, if continue.
This case correlates to an older software CTRL than this which has generated the Shelf Hot Data and
which is not compatible with this Hot Data.
The Shelf Hot Data is not compatible with CTRL software of the new CTRL-2G card
If you start CTRL software, part of Hot Data will be lost
and transmission will be broken a few seconds
6) -The software code of the inserted CTRL-2G card is compatible with the Shelf Hot Data provided
some parts of this Hot Data are converted.
This case correlates to a more recent software CTRL than this which has generated the Shelf Hot Data
and which must convert. some parts of this Hot Data
If conversion is accepted by the operator, then if later the previous CTRL-2G card is inserted again
(level 1), the converted parts of Hot Data will be reinitialized (case 5).
The Shelf Hot Data is compatible with CTRL software of the new CTRL-2G card
But will be convert to a new format ; if you continue and convert Hot Data
you will not insert the previous CTRL-2G card without breaking transmission !!!
7) -Some FPGA codes,already loaded on cards, must be loaded again because new releases exist in
Flash.
If a FPGA code must be loaded again, the transmission will be broken during the loading time and the
commissioning card.
Some of Fpga codes will be loaded because the new CTRL-2G card contains
other Fpga Codes in Flash than those loaded in hardware
If you start CTRL software, transmission will be broken a few seconds
8) The GIG-E code present in flash is different from the GIG-E code in progress.
If the GIG-E code must be loaded again, the transmission will be broken during the loading time and
the commissioning card.
The Soft. codes will be loaded because the new CTRL-2G card contains
other Soft. codes in Flash than those loaded in hardware

Page A6-3
6 - DEGRADED MODE
9) The GFP150 eXtra code present in flash is different from the GFP150 eXtra code in progress.
If the GFP150 eXtra code must be loaded again, the transmission will be broken during the loading
time and the commissioning card.
The Soft. codes will be loaded because the new CTRL-2G card contains
other Soft. codes in Flash than those loaded in hardware
10) Only one operational PSU (in case of a SWITCH HO/LO card inserted in the shelf) :
Two PSU cards are mandatory to supply the Equipment
Insert another PSU card
Software automatically reset until two PSU cards are in service
6.4 - OPERATOR ACTIONS

The possible operator actions are of 3 kinds :
CTRL-2G card extraction

Extract the CTRL-2G card and update the Shelf, GIG-E and GFP150 eXtra packs on a non-operational
shelf.
VT100 operation
Connect a VT100 Terminal or an emulation VT100 PC on the CTRL-2G card, type "enter" in order to
- display the cause, the software release of the previous CTRL-2G in case of card change, the
releases of the Shelf, GIG-E and GFP150 eXtra packs in Flash
- have access to the commands menu
The commands menu is as following :
1 - Switch GIG-E pack
2 - Switch and Reset GIG-E pack
3 - Switch GFP150 eXtra pack
4 - Switch and Reset GFP150 eXtra pack
5 - Switch and Reset Shelf pack
6 - Start CTRL Code
1) - Switch GIG-E Pack
The software swaps the GIG-E packs in Flash (selected and reserve) then displays again the
codes in flash then displays again the commands menu.
2) - Switch and Reset GIG-E Pack
The software swaps the GIG-E packs in Flash (selected and reserve) then start again the
CTRL software.

Page A6-4
6 - DEGRADED MODE
3) - Switch GFP150 eXtra Pack

The software swaps the GFP150 eXtra packs in Flash (selected and reserve) then displays
again the codes in flash then displays again the commands menu.
4) - Switch and Reset GFP150 eXtra Pack
The software swaps the GFP150 eXtra packs in Flash (selected and reserve) then start
again the CTRL software.
5) - Switch and Reset Shelf Pack
The software swaps the Shelf packs (CTRL software code, FPGA codes of Equipment
cards,) in Flash (selected and reserve) then start again the CTRL software
6) - Start CTRL Code
Before hitting (6),.it is recommended to upgrade the Shelf, GIG-E and GFP150 eXtra
packs by using a "cross-over Ethernet" cable (between PC and CTRL-2G card) and the
default IP address "135.10.114.11"
If the operator ignores the recommendations and ask the shelf operation starting, the
transmission risks to be disrupted.
Warning : when the software goes out of the degraded mode after theStart CTRL Code, it
causes a CTRL software reset in order to be able to restart the Ethernet interface with the
configured IP address (the default IP address in degraded mode is 135.10.114.11)

Page A6-5
6 - DEGRADED MODE
HTTP operation
A reduced operation HTTP can be started in local via the Ethernet interface.
The equipment IP address via the Ethernet interface is the default address 135.10.114.11.
A download window allows the download of the software codes that are not updated.

Page A6-6
6 - DEGRADED MODE
A switching window of software packs allows to select the current packs and to restart the CTRL
software.
The VT100 operation is always possible in parallel with the HTTP operation

Page A6-7
6 - DEGRADED MODE
6.5 - DEGRADED MODE SWITCH WARNING

On codes upgrade or downgrade from HTTP or from SNMP, the degraded mode is never used.
Nevertheless, we can have incompatibilities between the CTRL software and the FPGA codes or the
software codes of transmission cards.
In this case and if a momentary power supply cut appends, the CTRL-2G card software would fatally
switch in degraded mode, that can have unfortunate consequences as an intervention on the site.
In order to prevent these problems, a board defective alarm is positioned on the CTRL-2G card.as
soon as a risk exists.
An associated information to this alarm stipulates the cause which can be :
Fpga Codes Missing or Not Compatible
Unless one FPGA code in CTRL Flash is missing or is not compatible
Soft. Codes Missing or Not Compatible
The GIG-E code in CTRL Flash is missing or is not compatible (only if a GIG-E card is
configured in the shelf).
The GFP150 eXtra code in CTRL Flash is missing or is not compatible (only if a GFP150 eXtra
card is configured in the shelf).
This alarm is updated on the download and switch of Shelf, GIG-E or GFP150 eXtra packs.

Page A6-8
6 - DEGRADED MODE
6.6 - ACTIONS TO REALIZE ACCORDING TO CASES

1) Incompatibility between the FPGA codes of the Shelf,
GIG-E or GFP150 eXtra packs and the CTRL software, or
FPGA codes missing
Make them compatible by changing the Shelf pack or the
GIG-E pack or the GFP150 eXtra pack
Manual Action
- Replace the CTRL-2G card
- Update the CTRL-2G card
on another shelf then reinsert
it.
VT100
- Start (Alarm "ON" on the
CTRL-2G card)
- Switch and Reset of Shelf
pack (return to the previous
version)
In case of start-up :
The cards whose the FPGA codes are incompatible or
missing and which already are in service, stay in service,
The cards whose the FPGA codes are incompatible or
missing and which must switch in service, pass in
defective state,
An alarm stay "ON" on the CTRL-2G. card FPGA Codes
Missing or not compatible
HTTP
- Download of Shelf pack then
Switch and Reset of Shelf
pack
- Download of GIG-E pack
then Switch and Reset of
GIG-E pack
- Download of GFP150 eXtra
pack then Switch and Reset of
GFP150 eXtra pack
version)
- Switch and Reset of GIG-E
version)
- Switch and Reset of GFP150
eXtra pack (return to the
previous version)
Table 6-1 : Actions to realize according to cases

Page A6-9
6 - DEGRADED MODE
Manual Action
2) Incompatibility between the GIG-E software code or the
GFP150 eXtra software code and the CTRL software, or
GIG-E software code missing or GFP150 eXtra software
code missing
Make them compatible by changing the Shelf pack or the
GIG-E pack or the GFP150 eXtra pack
In case of start-up :
The GIG-E cards or the GFP150 eXtra cards whose the
software code is incompatible or missing and which
already are in service, stay in service,
The GIG-E cards or the GFP150 eXtra cards whose the
software code is incompatible or missing and which must
switch in service, pass in defective state,
An alarm stay "ON" on the CTRL-2G. card Soft Codes
Missing or not compatible
VT100
- Start (Alarm "ON" on the
CTRL-2G card)
version)
version)
HTTP
pack
GIG-E pack
GFP150 eXtra pack

previous version)
version)
version)
previous version)

Page A6-10
6 - DEGRADED MODE
3) The database is incompatible with the CTRL software and

will be partly reinitialized
> case of downgrade (switching to a CTRL software release
previous to the one that generated the database) of CTRL
software incompatible with the current database
Start at VT100 ; the database is partly reinitialized
Manual Action
it.
VT100
HTTP
- Start (the incompatible parts - Download of Shelf pack then
of database are reinitialized by Switch and Reset of Shelf
pack
default)
version)

version)
Otherwise, return to the previous CTRL software code

(Switch and Reset of Shelf pack)
4) The database is incompatible with the CTRL software and
will be converted
> case of upgrade (switching to a CTRL software release
posterior to the one that generated the database) of CTRL
software incompatible with the current database
- Start (the incompatible parts

of database are converted
version)
Start at VT100 ; the transmission will not be perturbed and

the database will be converted
This message prevents that, after effected conversions,
previous CTRL card insertion will cause a reinitialization of
some parts of database (case 3).

Page A6-11
6 - DEGRADED MODE
5) The Hot Data are incompatible with the CTRL software and
will be partly reinitialized
> case of downgrade (switching to a CTRL software release
previous to the one that generated the Hot Data) of CTRL
software incompatible with the current Hot Data
Start at VT100 ; the Hot Data is partly reinitialized
Manual Action
- Replace the CTRL-2G. card
it.
VT100
HTTP
- Start (the incompatible parts - Download of Shelf pack then
of Hot Data are reinitialized by Switch and Reset of Shelf
pack
default)
version)

6) The Hot Data are incompatible with the CTRL software and
will be converted
> case of upgrade (switching to a CTRL software release
posterior to the one that generated the Hot Data) of CTRL
software incompatible with the current Hot Data
- Start (the incompatible parts

of Hot Data are converted)
version)
Start at VT100 , the transmission will not be perturbed and

the Hot Data will be converted
This message prevents that a return to the previous
software will cause a loss of Hot Data part and will be able
to cause a temporarily transmission breaking (case 5).

Page A6-12

version)
6 - DEGRADED MODE
7), 8) and 9) Some FPGA or GIG-E or GFP150 eXtra codes

will be loaded, that can perturb the transmission.
Manual Action
it.
Start at VT100
Otherwise, switch again to the previous Shelf pack or to
the previous GIG-E pack or to the GFP150 eXtra pack
VT100
- Start (the FPGA or the
software code of some cards
will be loaded)
HTTP
pack

pack

GIG-E pack

pack

- Switch and Reset of GFP150 GFP150 eXtra pack
eXtra pack
version)
version)
previous version)
10) The shelf does not contain 2 operational PSU
(in case of a SWITCH HO/LO card inserted in the shelf)
- If only one PSU card is

present in the shelf, insert a
second one.
- If 2 PSU cards are inserted
in the shelf, replace the failed
card.
Whatever is the case, wait for
the next automatic reset (all
20s)

Page A6-13
6 - DEGRADED MODE

Page A6-14
7 GFP150 EXTRA CARD
7 GFP150 EXTRA CARD
All the services mentioned in this document can be performed between the GFP150 eXtra cards from ADR2500
eXtra but also between the GFP150 eXtra cards and the GFP150 cards from ADR155C.
Only the EPLine and EPLAN services can be interconnected with the EPLine service proposed by a 4E/FE card
of an ADR155C or of an ADR155CPE.
Each ADR2500 eXtra can include up to six GFP150 eXtra cards which must take place in "TRIB 1" or "TRIB 2"
or "TRIB 5" to "TRIB 8" slots, in the left part of the slot.
7.1 - GFP150 EXTRA CARD AND SERVICES PRESENTATION

This chapter has for objective to guide the user for the commissioning of the GFP150 eXtra card in the
ADR2500 eXtra. It gives simple examples which should be easily adapted to the needs.
Services provided by GFP150 eXtra card in ADR2500 eXtra are :
SMART LL EPLine Service (from P2.1 release) :

The EPLine service (Ethernet Private Line) allows Ethernet 10/100 BaseT point to point interconnection
through a SDH network by using, for each connection, a VCG (VC-Group) based on virtual concatenation
(VCAT). It is possible to obtain up to 8 independant point to point connections per GFP150 eXtra card. Rate
granularity for each VCG is based either on VC12, or on VC3. With each VCG, it is possible to concatenate
from 1 to 46 VC12 or from 1 to 2 VC3. The sum of the concatenated Ethernet rates, on the whole of the 8
ETH ports, cannot be above the STM1 payload (about 150Mbit/s).
AGGREGATION EVPLine Service (from P2.2 release) :

The EVPLine service (Ethernet Virtual Private Line) allows several Ethernet 10/100 BaseT point to point
interconnection through a SDH network by using over shared VCG (VC-Group) based on virtual
concatenation (VCAT). These VMAN are separated by Tag VMAN, that adds a level of VLAN in relation to
the possible VLANs of Customers. It is possible to put until 16 aggregation traffic (VMAN) on a VCG. In the
GFP150 eXtra card we can have 64 (63 if the MSTP protection is used) different VMAN maximum.
The rate granularity for each VCG is the same as EPLine.
SMART LL EPLAN Service (from P2.1 release) :

The EPLAN service (Ethernet Private LAN) allows Ethernet 10/100 BaseT multipoint to multipoint
interconnection through a SDH network by using, for each connection between two points of the network, a
VCG (VC-Group) based on virtual concatenation (VCAT). It is possible to obtain up to 8 independant
connections per GFP150 eXtra card. Rate granularity for each VCG is based either on VC12, or on VC3.
With each VCG, it is possible to concatenate from 1 to 46 VC12 or from 1 to 2 VC3. The sum of the
concatenated Ethernet rates, on the whole of the 8 ETH ports, cannot be above the STM1 payload (about
150Mbit/s). In this case, each GFP150 eXtra card includes a switch allowing Ethernet 10/100 BaseT
multipoint to multipoint interconnection.

Page A7-1
7 GFP150 EXTRA CARD
AGGREGATION EVPLAN Service (from P2.2 release) :

The EVPLAN service (Ethernet Virtual Private LAN) allows several Ethernet 10/100 BaseT multipoint to
multipoint interconnection through a SDH network by using over shared VCG (VC-Group) based on virtual
concatenation (VCAT).
It is possible to configure 4 VMANs by COS1 class of traffic and 12 VMANs by COS0 class of traffic
(2 classes of traffic are available on the GFP150 eXtra card).It is therefore possible to put until 16
aggregation traffic (VMAN) on a VCG. In the GFP150 eXtra card we can have 64 (63 if the MSTP protection
is used) different VMAN maximum.
In this case, each GFP150 eXtra card includes a switch function allowing Ethernet 10/100 BaseT multipoint
to multipoint interconnection
These services allow to answer, for example, to the following needs :
point to point application: to build an Ethernet LAN between 2 sites
multilink application (Star) : LAN interconnection between a central site and remote sites
multipoint to multipoint application : to share a LAN between several sites in a BUS topology
Ethernet frames are transported on SDH by using the GFP-F protocol.

The use of the GFP protocol and the advanced Switch features allows to offer Quality of Services features
(QoS). The QoS in GFP150 eXtra card is based on a traffic differentiation : metering, congestion control and
scheduling.
Hardware design
Micro
MicroProcessor
Processor
To switch
fabric
155 Mb/s
GFP
GFPMapper
Mapper
Switch
Switch
Figure 7-1: Hardware design of the card

Page A7-2
8
E/FE TX
7 GFP150 EXTRA CARD
7.2 - CONFIGURATION AND APPLICATIONS OF THE GFP150 EXTRA CARDS

7.2.1 - GFP150 eXtra card setup
a)
Unwrap the card
b)
Insert and screw the card in an allowed slot of the ADR2500 eXtra shelf.
c)
Verify with HTTP configuration manager that the GFP150 eXtra pack (Upload/Download > Switching
menu) is present in the system.
d)
In the HTTP configuration manager, select GFP150 eXtra as expected card on the slot where it was
inserted
e)
Connect the Ethernet cables to the GFP150 eXtra card
f)
Wait a few seconds and check that the green LED status is steadily on.
7.2.2 - Create a LAN interconnection

7.2.2.1 - Point-to-Point mode interconnection : EPLine service
In the diagram below, one intends to deport a full duplex LAN Ethernet 100 BaseT between 2 sites equipped of
ADR2500 extra. In a first time, one supposes that the rate of the Ethernet traffic exchanged between the 2 sites
does not exceed 10Mbps. The QoS configuration is explained later in this document in greater details.
ADR2500 eXtra
ADR2500 eXtra
Eth/VC12
SDH
Ethernet 10/100M
Ethernet 10/100M
Figure 7-2 : EPLine service
7.2.2.1.1 - GFP150 eXtra cards configuration

Login on the first ADR2500 eXtra to open the Shelfview HTTP screen. On this screen, click on the GFP150
eXtra card then on the ETH link.

Page A7-3
7 GFP150 EXTRA CARD
Configuring the Ethernet interface

Click on the Interface Settings link. By default the Ethernet interface is forced in 100Base T full duplex. We
choose to keep the default configuration for this example.
Figure 7-3 : Configuring the Ethernet interface
Note : The Ethernet interface of the remote equipment (switch, IP router, PC, ) connected to the GFP150
eXtra card MUST always be configured the same way. Due to possible interoperability issues with AutoNegotiation between equipments from different origins, this feature (Automatic option) should
preferably not be used.
This screen is also used to set the severity associated to the interface defect of that interface.
Logical Interface
Select the UNI mode (User to Network Interface) : this type of interface corresponds to an interface customer
with one service per port. On these interfaces the provider OAM and BPDU MSTP management frames are
filtered : they are not sent to the customer network.
The NNI untagged choice (Network to Network Interfacing) corresponds to a provider interface without provider
VMAN tag (no VLAN aggregation).
The NNI tagged choice (Network to Network Interfacing) corresponds to a provider interface on which a
provider VMAN tag is inserted in the outcoming frames and a provider VMAN tag is treated in the incoming
frames.

Page A7-4
7 GFP150 EXTRA CARD
Link Down Retransmit

The Link Down Retransmit function can only be used in point to point mode on a VMAN constituted of one ETH
port and one VCG port in each equipment.
Tick "Enable" allows to report the state of the Ethernet Down or VCG Down link on the remote Ethernet link.
ETH Down Report

Status Down
2
1
ETH
GFP 150
"LDR
Enable"
SDH
VCG
VCG
Locs + VCG Down

4
GFP 150
"LDR
Enable"
Forced
Cut off
ETH
VCG Down Report

VCG Down
3
Forced
Cut off
ETH
GFP 150
"LDR
Enable"
SDH
VCG
VCG
1
VCG Down
GFP 150
"LDR
Enable"
ETH
3
Forced
Cut off
Pause Mode
The Pause function (IEEE 802.3 Flow control) can only be used in point to point mode/full duplex on a VMAN
constituted of one UNI ETH port and one NNI untagged VCG port (or of two UNI and NNI untagged ETH ports).
If the "Status" field = Pause (result of autonegotiation or forcing)
-
At reception of a pause frame on the ETH port, the transmission of Ethernet frames on the ETH port is
suspended temporarily
On detection of traffic obstruction on the VMAN considered in the sense ETH = > VCG, a pause frame is
transmitted on the ETH port to ask the remote equipment to stop the transmission of Ethernet frame
temporarily.
Warning : When the Pause mode is activated, be careful to configure the CIR and PIR to the maximum of the
capacity of the VCG
Configuring a VCG
Click on the VCG link, then on the List link. For the selected VCG#1 interface, click on VC#1 and then on the
Multiple Add Member link. In the new screen coming up, select VC12 as type and VC#6 as last connection.
Click on Apply in order to create the virtually concatenated group of 6 VC12 (VC12#1 to VC12#6) that will be
used to transport Ethernet traffic.

Page A7-5
7 GFP150 EXTRA CARD
Figure 7-4 : Configuring the VCG (1)

Click on the Settings link. Verify that VCG#1 is set with the default configuration: Admin Status at Up,
"Logical Interface NNI" at "untagged", LCAS at Yes and FCS at No. We choose to keep the default
options for this example. This screen also displays the type of VCG#1 (VC12) and the number of constituting
VC members (6).

Logical Interface NNI (Network to Network Interface) : untagged or tagged
- untagged : corresponds to a provider interface without provider VMAN tag (no VLAN aggregation).
- tagged : corresponds to a provider interface on which a provider VMAN tag is inserted in the outcoming
frames and a provider VMAN tag is treated in the incoming frames.
Page A7-6
7 GFP150 EXTRA CARD
Click on the "VCG" link and then on the "Alarms " link. Select interface VCG#1 . Tick option "Monitor " and click
on "APPLY " in order to start monitoring alarms on this port (see Figure 7-9).
Configuring the Ethernet Switch
Click on the Switch link, then on the VMAN Create link. Enter 2 as new VMAN ID and click on Apply in
order to add it. A new screen comes up in order to associate ports to this VMAN.
Click on the Add Port link. Select the Ethernet interface ETH#1, the trTCM policing algorithm, enter 10Mbps
for the CIR and PIR, and 7 for the "User Priority " (maximun priority) (for more information on the notion of
priority, see the chapter on the QoS). The CBS and EBS values are left to default. Then click on Add to
complete the addition of this port to VMAN 2.
Click on the Add Port link again. Select the Ethernet interface VCG#1, the trTCM policing algorithm, and
enter 10Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values
are left to default value. Then click on Add to complete the addition of this port to VMAN 2.
Figure 7-6 : Configuring the Ethernet Switch (1)
The association of these 2 ports to the same and unique VMAN ID isolates the Ethernet Switching between
these 2 ports from the rest of the ports (all the other Ethernet and VCG interfaces). Ethernet traffic forwarded
between these 2 ports cannot leak out on other ports and vice versa.
Note : In order to install a point-to-point connection (EPLine service), there should never be more than 2 ports
(1 customer UNI Ethernet port and 1 untagged NNI Ethernet or VCG port) in the same VMAN on the
GFP150 eXtra card.
To double check the configuration click on the VMAN List link. A table displays what ports are associated with
each VMAN configured on the GFP150 eXtra card.

Page A7-7
7 GFP150 EXTRA CARD
Configuring the SDH cross-connects

Click on the Connection tab of the shelf view and configure the connections from VC12#1 to VC12#6 of the
GFP150 eXtra card as usual in order to have end-to-end SDH connectivity with the remote GFP150 eXtra card.
Figure 7-8 : Configuring the SDH Cross Connects

Configuring the remote GFP150 eXtra card
Just do the configuration on the second ADR2500 eXtra following the exact same steps again.
Activating the end-to-end Ethernet connection
Once both ADR2500 eXtra systems are configured, the ports used by the Point-to-Point can be activated on
each ADR2500 eXtra.
Click on the ETH link, then on the Interface Settings link. For interface ETH#1 , tick ifAdminStatus up and
click on Apply.
7.2.2.1.2 - Connectivity check

Perform the following verifications with both GFP150 eXtra cards:
1. Click on the "ETH" link, check that the Ethernet ports in use are not highlighted (the given box would be
marked yellow or red depending on alarm severity) ; then click on the "VCG" and "Alarms" links, check that
the VCG ports in use are not highlighted (the given box would be marked yellow or red depending on alarm
severity). Otherwise click on the alarmed port to go to the proper screen, where the specific alarm is
displayed (this brings you directly to step 2, 3 or 4 below). Repeat the operation for every alarmed port.
2. Click on the ETH link and select Ethernet interface ETH#1. Verify that the interface is running in 100BaseT
full duplex and that there is no alarm (the Fault option of the Interface Defect alarm is unchecked).
Otherwise double-check both the cables and the configuration of the connected Ethernet interface.
3. Verify that there are no alarms on all the VC's being used. Otherwise double-check end-to-end SDH
configuration as well as the signal quality over the various links.

Page A7-8
7 GFP150 EXTRA CARD

4. Click on the VCG link then on the Alarms link, and select the VCG#1 interface. Once configuration is
complete all alarms should disappear after a few seconds. Otherwise double-check the configuration in the
VCG functional block on both ends as well as the configuration of the SDH cross-connects.
Figure 7-9 : Connectivity check

Note : This screen can be used to configure the severity of the alarms related to concatenated VCs.
5. Click on the Settings link and verify that the VCG#1 is Up.
6. Try sending bi-directional Ethernet traffic across the end-to-end connection. You could for example:
Run a ping or a file transfer between 2 PCs to control Ethernet connectivity.
Use an Ethernet traffic generator in order to further qualify the end-to-end connection.
As a final step, double-check compliance of the GFP150 eXtra counters on both ends based on the traffic
being forwarded. Namely the following counters:
- Ethernet counters: click on the ETH link and then on the MIB2 Counters link
- GFP counters: click on the VCG link and then on the MIB2/GFP Counters link
- SLA compliance counters: click on the Switch link. Select VMAN ID 2, click on the VMAN SLA
counters link. Verify the set of counters for interfaces ETH#1 and VCG#1. These counters are
described later in this document in greater details.
7.2.2.2 - Point-to-Point mode interconnection : EVPLine service (aggregation)

In the diagram below, one intends to deport two full duplex LAN Ethernet 100 BaseT between 2 sites equipped
of ADR2500 extra by sharing the same VCG for the two traffics (aggregation), this in order to optimize the SDH
bandwidth.
One supposes that the Ethernet traffic rate exchanged between the 2 sites does not exceed 10Mbps for each
flow.

Page A7-9
7 GFP150 EXTRA CARD
1 VCG
ADR2500 eXtra
ADR2500 eXtra
Eth/VC12
SDH
Ethernet 10/100M
Ethernet 10/100M
Figure 7-10 : Service EVPLine
7.2.2.2.1 - GFP150 eXtra cards configuration

Configuration of the Ethernet interface
Click on the "ETH" link then on the Interface Settings link. By default the Ethernet interface is forced in
100Base T full duplex. Apply the same configuration for all Ethernet ports.
Configuring a VCG
Click on the VCG link, then on the List link. For the VCG#1 interface, select the VC#1 and click on the
Multiple Add Member link. In the new window, select VC12 as type and the VC#12 as last connection. Click
on Apply in order to create the virtually concatenated group of 12 VC12 (VC12#1 to VC12#12) that will be
used to transport Ethernet traffic.

Page A7-10
7 GFP150 EXTRA CARD
Click on the Settings link to configure VCG#1 as following : Admin Status at Up, "Logical Interface NNI" at
"tagged", LCAS at Yes and FCS at No. These options correspond to the needed example for the
aggregation, on the VCG1 the frames must be tagged
This screen also displays the type of VCG#1 (VC12) and the number of constituting VC members (12).

Click on the "Alarms " link. Select the interface VCG#1 . Tick "Monitor " option and click on "APPLY " in order to
start monitoring alarms on this port (see Figure 7-9).
For the first ETH port (ETH1):
order to add it. A new window comes up in order to associate ports to this VMAN.
for the CIR and PIR, and 7 for the "User Priority " (maximun priority) (for more information on the notion of
priority, see the chapter on the QoS). The CBS and EBS values are left to default values. Then click on Add to
complete the addition of this port to VMAN 2.
Click on the Add Port link again. Select the Ethernet interface VCG#1, the trTCM policing algorithm, enter
10Mbps for the CIR and PIR, and 7 for the "User Priority ". The CBS and EBS values are left to default values.
Then click on Add to complete the addition of this port to VMAN 2.
Then for the other Eth port (ETH2):
order to add it. A new window comes up in order to associate ports to this VMAN.
for the CIR and PIR, and 7 for the "User Priority " (maximun priority) (for more oinformation on the notion of
priority, see the chapter on the QoS). The CBS and EBS values are left to default values. Then click on Add to
complete the addition of this port to VMAN 3
Click on the Add Port link again. Select the Ethernet interface VCG#1, the trTCM policing algorithm, enter
10Mbps for the CIR and PIR, and 7 for the "User Priority ". The CBS and EBS values are left to default values.
Then click on Add to complete the addition of this port to VMAN 3.

Page A7-11
7 GFP150 EXTRA CARD

The association of these 2 ports to the same and unique VMAN ID isolates the Ethernet Switching between
these 2 ports from the rest of the ports (all the other Ethernet and VCG interfaces). Ethernet traffic forwarded
between these 2 ports cannot leak out on other ports and vice versa.
With the selection of tagged mode for the VCG1, it is possible to differentiate traffics of the two Eth links on the
VCG.
Note : In order to install a point-to-point connection (EVPLine service), there should never be more than 2
ports (1 customer UNI Ethernet port and 1 tagged NNI Ethernet or VCG port) in the same VMAN on the
GFP150 eXtra card.
To check the configuration click on the VMAN List link. A table displays the associated ports to each
configured VMAN on the GFP150 eXtra card.
Figure 7-13 : Configuring the Ethernet Switch

Click on the Connection tab of the shelf view and configure the connections from VC12#1 to VC12#12 of the
GFP150 eXtra card as usual in order to have end-to-end SDH connectivity with the remote GFP150 eXtra card.
Figure 7-14 : Configuring the SDH Cross Connects

Page A7-12
7 GFP150 EXTRA CARD

Configuring the remote GFP150 eXtra card
Just do the configuration on the second ADR2500 eXtra by following the exact same steps again.
Activating the end-to-end Ethernet connection
Once both ADR2500 eXtra systems are configured, the ports used by the point-to-point links can be activated
on each ADR2500 eXtra.
Click on the ETH link, then on the Interface Settings link. For ETH#1 and ETH#2 interfaces, tick
ifAdminStatus up and click on Apply.
7.2.2.2.2 - Control of the link

Take again the procedure of the paragraph 7.2.2.1.2 - to do controls, by verifying the 2 links.
7.2.2.3 - Hub and Spoke interconnection: EPLAN service

In the network below, we show interconnection of three remote sites with one central site in a hub and spoke
topology. Although Ethernet interfaces are 100BaseT full duplex, the load of traffic between the remote sites
and the central site is as follows:
remote sites 1 and 2 : 10Mbps (6VC12),
remote site 3 : 5Mbps (3VC12).
The sum of the data rates going to the central site is 25Mbps. However we consider in this example that the
total rate of traffic going in the opposite direction (a.k.a. from the central site to the remote sites) doesnt go over
20Mbps ; this is just for the purpose of the example.
In this example, the central site acts as a full bridge : Ethernet frames can be forwarded between remote sites.
If no traffic must be allowed between remote sites (for security purpose for instance), one should use 3 separate
Ethernet interfaces on the central site, and 1 point to point connection between each remote site and the central
site. In this case configure 3 independent point-to-point connections as described in the previous section.
Remote site 1
Eth / 6xVC12
Central site
SD H
Ethernet 10/100
Eth / 6xVC12
Eth / 3xVC12
Ethernet 10/100
Ethernet 10/100
Remote site 3
Remote site 2
Ethernet 10/100
Figure 7-15 : EPLAN service

Page A7-13
7 GFP150 EXTRA CARD

7.2.2.3.1 - Configuring the GFP150 eXtra card of the central site
Login on the ADR2500 eXtra of the central site to open the Shelfview HTTP screen. On this screen, click on
the GFP150 eXtra card then on the ETH link.
Configuring the Ethernet interface
Click on the Interface Settings link. By default the Ethernet interface is forced in 100Base T full duplex. We
choose to keep the default configuration for this example.
Note : The Ethernet interface of the remote equipment (switch, IP router, PC, ) connected to the GFP150
eXtra card MUST always be configured the same way. Due to possible interoperability issues with AutoNegotiation between equipments from different origins, this feature (Automatic option) should
preferably not be used.
Figure 7-16 : Configuring the Ethernet interface

Configuring the VCGs
Click on the VCG link and then on the List link. For the selected VCG#1 interface, click on VC#1 and then on
the Multiple Add Member link. In the new screen coming up, select VC12 as type and VC#6 as last
connection. Click on Apply in order to create the virtually concatenated group of 6 VC12 (VC12#1 to VC12#6)
that will be used to transport Ethernet traffic.
Select interface VCG#2 and redo the same operation to add a new group of 6 VC12 (VC12#7 to VC12#12) ; if
the request is refused, verify that the VCG#2 is configured to Down in the "VCG > Settings" window.
Select interface VCG#3 and redo the same operation to add a new group of 3 VC12 (VC12#13 to VC12#15).

Page A7-14
7 GFP150 EXTRA CARD
Click on the Settings link. Verify that VCG#1, VCG#2 and VCG#3 are set with default configuration: Admin
Status at Up, "Logical Interface NNI" at "untagged", LCAS at Yes and FCS at No. We choose to keep
the default options for this example. This screen also displays the type of VCG#1,#2,#3 (VC12) and the number
of constituting VC members (6,6,3).

Page A7-15
7 GFP150 EXTRA CARD
Click on the "Alarms" link. Select interface VCG#1. Tick option "Monitor " and click on "APPLY " in order to start
monitoring alarms on this port (see Figure 7-9). Repeat with VCG#2 and VCG#3.
Click on the Switch link and then on the VMAN Create link. Enter 2 as new VMAN ID and click on Apply in
Click on the Add Port link. Select the Ethernet interface ETH#1, the trTCM policing algorithm, and enter
20Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values are left
to default. Then click on Add to complete the addition of this port to VMAN 2.
enter 10Mbps for the CIR, and PIR and 7 for the "User Priority " (maximun priority). The CBS and EBS values
are left to default. Then click on Add to complete the addition of this port to VMAN 2.
enter 5Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values are
left to default. Then click on Add to complete the addition of this port to VMAN 2.

Page A7-16
7 GFP150 EXTRA CARD

Click on the Connection tab. Configure the connections from VC12#1 to VC12#6 of the GFP150 eXtra card as
usual in order to have end-to-end SDH connectivity between the central site and remote site 1.
Configure the connections from VC12#7 to VC12#12 of the GFP150 eXtra card as usual in order to have endto-end SDH connectivity between the central site and remote site 2.
Configure the connections from VC12#13 to VC12#15 of the GFP150 eXtra card as usual in order to have endto-end SDH connectivity between the central site and remote site 3.
7.2.2.3.2 - Configuring the GFP150 eXtra cards of the remote sites

The GFP150 eXtra cards of the remote sites must be configured as if they were in point-to-point mode. Hence,
we apply the configuration described in the point-to-point section of this document ( 7.2.2.1 -). However the
policing rates (10Mbps or 5Mbps) and the right number of VC12 (6 or 3) must be configured appropriately for
each remote site 1, 2 and 3 (see Figure 7-15). See the topology figure of this example.
Activating the end-to-end Ethernet connections
Once both GFP150 eXtra cards at the ends of a connection are configured, the Ethernet interfaces should be
activated.
Click on the ETH link and then on the Interface Settings link. For interface ETH#1 , tick ifAdminStatus up
and click on Apply.

For each GFP150 eXtra card, perform the following verifications:
marked yellow or red depending on alarm severity) ; then click on the "VCG" link and on the "Alarms" link,
check that the VCG ports in use are not highlighted (the given box would be marked yellow or red
depending on alarm severity). Otherwise click on the alarmed port to go to the proper screen, where the
specific alarm is displayed (this brings you directly to step 2, 3 or 4 below). Repeat the operation for every
alarmed port.
3. Verify that there are no alarms on all the VCs being used. Otherwise double-check end-to-end SDH
4. Click on the VCG link and on the Alarms link, then select the VCG#1, VCG#2 and VCG#3 on the central
site and only VCG#1 on a remote site. Once configuration is complete all alarms should disappear after a
few seconds. Otherwise double-check the configuration in the VCG functional block on both ends as well
as the configuration of the SDH cross-connects.
5. Click on the Settings link and verify that the VCG is Up.
6. Try sending bi-directional Ethernet traffic over each point-to-point connection. You could for example:
being forwarded.
Page A7-17
7 GFP150 EXTRA CARD
7.2.2.4 - Bus interconnection : service EPLAN

In the network below, we setup an Ethernet 100BaseT LAN spanning over 4 sites connected to an ADR2500
eXtra.
In this example, sites 2 and 4 play the role of a full bridge: : Ethernet frames can be forwarded between all
remote sites based on MAC address learning.
Each inter-site link of the bus topology is configured to transport a load of 10Mbps (6 VC12). Similarly, on each
ADR2500 eXtra the Ethernet interface connected to the bus is policed at 10Mbps.
Site n1
Eth / 4xVC12
Eth / 4xVC12
Site n3
SDH
Ethernet 10/100
Ethernet 10/100
Site n2
Ethernet 10/100
Site n4
Ethernet 10/100
Figure 7-21 : EPLAN Service - "bus" mode
7.2.2.4.1 - Configuring the GFP150 eXtra cards of sites 1 and 3

The GFP150 eXtra cards of sites 1 and 3 must be configured in point-to-point mode following configuration
guidelines of the point-to-point section of this document ( 7.2.2.1 -).
7.2.2.4.2 - Configuring the GFP150 eXtra cards of sites 2 and 4

For sites 2 and 4, the configuration of functional blocks VCG, Connection and Ethernet Switch is different from
the two other sites.

Page A7-18
7 GFP150 EXTRA CARD

Configuring the VCGs
Click on the VCG link and then on the List link. For the selected VCG#1 interface, click on VC#1 and then on
the Multiple Add Member link. In the new screen coming up, select VC12 as type and VC#6 as last
connection. Click on Apply in order to create the virtually concatenated group of 6 VC12 (VC12#1 to VC12#6)
that will be used to transport Ethernet traffic.
Select interface VCG#2 and redo the same operation to add a new group of 6 VC12 (VC12#7 to VC12#12).

"Logical Interface NNI" at "untagged", LCAS at Yes and FCS at No. We choose to keep the default
options for this example. This screen also displays the type of VCG#1 and VCG#2 (VC12) and the number of
constituting VC members (6).

Page A7-19
7 GFP150 EXTRA CARD
Click on the "Alarms " link. Select interface VCG#1 . Tick option "Monitor " and click on "APPLY " in order to
start monitoring alarms on this port (see Figure 7-9). Repeat with VCG#2.
Click on the Switch link and then on the VMAN Create link. Enter 2 as new VMAN ID and click on Apply in
Click on the Add Port link. Select the Ethernet interface ETH#1, the trTCM policing algorithm, and enter
10Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values are left
to default. Then click on Add to complete the addition of this port to VMAN 2.

Page A7-20
7 GFP150 EXTRA CARD

Click on the Connection tap. Configure the connections from VC12#1 to VC12#6 of the GFP150 eXtra card as
usual in order to have end-to-end SDH connectivity between each middle site (2 or 4) and each edge site
(respectively 1 or 3, see Figure 7-21).
Configure the connections from VC12#7 to VC12#12 of the GFP150 eXtra card as usual in order to have endto-end SDH connectivity between both middle sites (2 and 4).
Activating the end-to-end Ethernet connections
Once both GFP150 eXtra cards at the ends of a connection are configured, the Ethernet and VCG interfaces
should be activated.
Click on the ETH link and then on the Interface Settings link. For interface ETH#1 , tick ifAdminStatus up
and click on Apply.

For each GFP150 eXtra card, perform the following verifications:
marked yellow or red depending on alarm severity) ; then click on the "VCG" link, check that the VCG ports
in use are not highlighted (the given box would be marked yellow or red depending on alarm severity).
Otherwise click on the alarmed port to go to the proper screen, where the specific alarm is displayed (this
brings you directly to step 2, 3 or 4 below). Repeat the operation for every alarmed port.
3. Verify that there are no alarms on all the VCs being used. Otherwise double-check end-to-end SDH
4. Click on the VCG link and on the Alarms link, then select the VCG#1, VCG#2 and VCG#3 on the central
site and only VCG#1 on a remote site. Once configuration is complete all alarms should disappear after a
few seconds. Otherwise double-check the configuration in the VCG functional block on both ends as well
as the configuration of the SDH cross-connects.
5. Click on the Settings link and verify that the VCG is Up.
6. Try sending bi-directional Ethernet traffic over each point-to-point connection. You could for example:
being forwarded.

Page A7-21
7 GFP150 EXTRA CARD
7.2.2.5 - Bus interconnection : service EVPLAN

In the network below, we setup two Ethernet 100BaseT LAN spanning over 4 sites connected to an ADR2500
eXtra.
To the difference of the EPLAN service, the two LAN use the same VCG to circulate, it is possible with the
aggregation in the same VCG. For this the VCG ports of the N1, N2, N3 and N4 equipment must be
configured in fashion NNI tagged.
In this example, 2 and 4 sites play the role of a full bridge: : Ethernet frames can be forwarded between all
remote sites based on MAC address learning.
Each inter-site link of the bus topology is configured to transport a load of 20Mbps (12 VC12). Similarly, on each
ADR2500 eXtra, the Ethernet interface connected to the bus is policed at 10Mbps.
Site n1
Eth/12xVC12
Eth/12xVC12
Site n3
SDH
Ethernet 10/100
Ethernet 10/100
Site n4
Site n2
Ethernet 10/100
Ethernet 10/100
Figure 7-26 : EVPLAN Service - "bus" mode

Page A7-22
7 GFP150 EXTRA CARD
7.2.3 - Implementation of the OAM-CC function (Operation Administration

Maintenance - Continuity Check) on the GFP150 eXtra card
The OAM function (Operation Administration Maintenance) in the GFP card, is used to supervise the customer
traffic.
This function consists in the broadcast and receipt of specific messages to supervise customer traffic. This
allows to know the state of the network, in relation to the progress of this flux
It is based on the IEEE-802. 1ag] norm . The supervision frames for broadcast and receipt are named frames
CC : Continuity Check.
Below an example of utilization of the OAM function:
NNI
CE
NNI
UNI
UNI
SDH Network
CE
ADR2500 eXtra N1
ADR2500 eXtra N 2
VMANi
Probe Source OAM-CC

Probe Sink OAM-CC
Figure 7-27 : Example of OAM utilization
The OAM-CC function is constituted of source and sink probes:
A source probe that transmits a multicast frame periodically (by default 10 seconds in the extra) toward
sink probes. A probe source can transmits toward several sink probes.
A sink probe that treats the multicast frame, and a time-out (by default 10 secondes in the eXtra).
In the example of the figure N1, a source probe is declared in the equipment N1 and a sink probe in the
equipment N2 on the same VMANi, that allows the monitoring of the VMANi customer traffic between
equipment N1 and equipment N2 in one sense
To supervise the other sense of this VMANi it is necessary to add two supplementary probes, a source probe on
the equipment N2 and a sink probe on the equipment N1.
The OMA-CC function manages 2 supervision alarms :
OAM Degraded : in this case it is the loss of one up to three consecutive CC frames
OAM Defect : in this case it is the loss of at least four consecutive CC frames.
The period between two OAM frames is configurable : 10s by default.
The number of source probes is limited to 10 and the number of sink probes to 64 by GFP150 eXtra card.
The frame multicast OAM is not distributed on the UNI port (customer), and is distributed tagged on tagged NNI
port and no tagged on untagged NNI port
The OAM CC multicast MAC address is by default: 01-80-C2-00-00-67.

Page A7-23
7 GFP150 EXTRA CARD

Notes :
- The periodic OAM defect, can mean that network capacity for the VCG are not adjusted, and that congestions
appear (example : a VC link loss in a VCG with LCAS).
- No OAM probe must be activated on a flow created between a GFP150 eXtra card and a 4E/FE card. The
provider OAMcc frames are not filtered by the 4E/FE card and are forwarded to the customer network.
7.2.4 - Using Quality of Service features of GFP150 eXtra card

7.2.4.1 - QoS functions of the GFP150 eXtra card
The GFP150 eXtra card provides various QoS functions. These functions format outgoing traffic flows on all
interfaces. Namely:
Traffic is forwarded in compliance with a pre-configured Service Level Agreement (SLA)

Committed and peak rates are guaranteed for every traffic flow
The QoS functions implemented on the GFP150 eXtra card are:
definition of guaranteed rate contracts per traffic flow
congestion management of traffic flows in agreement with their conformity to contracts
Functional diagram
The GFP150 eXtra QoS can be represented by the following diagram. It includes:
a block of metering and policing,
two waiting queues, one file (TC0) in Low priority and one queue (TC1) in SP (Strict Priority)
a scheduler mechanism for outgoing theses packets of theses queues toward the exit port.
The goal of this mechanism is to encourage an important customer by report on a lower customer in aggregate
traffic to respect times of latency associated to every class of service.
The egress treatment (side port broadcast) permits a differentiated treatment according to the priority of the
VMAN with these different queues of transmission (TC: Traffic Class) as well as the means of outgoing
(scheduling in priority the TC1 SP (Strict Priority) file untill its shaping is reached).
This diagram applies to all ports: the 8 Ethernet interfaces plus the 8 Ethernet over SDH interfaces. All functions
are configured separately per port.
Compteurs SLA
File TC 0
From
Ethernet
GREEN
Metering
GREEN
Policing
YELLOW
File TC 1
LP
SP
%Shaping
YELLOW
RED
Ingress
Egress
Figure 7-28 : QoS architecture

Page A7-24
S
C
H
E
D
U
L
E
R
Toward SDH
switch fabric
VC3-nV or VC12-nV
7 GFP150 EXTRA CARD

QoS management - Rate control
Rate control compares the temporal characteristics of received traffic (based on the rate and length of bursts)
with a contract subscribed by the customer sending this traffic. This type of contract is commonly called a
Service Level Agreement (SLA).
In the first stage, the temporal characteristics of the actual traffic flow are measured (metering). By comparing
them to the configured profile (or contract), each frame is colored according to the following rule:
Green: the frame is in profile
Yellow: the frame is partially out of profile
Red: the frame is entirely out of profile
The GFP150 eXtra card provides counters displaying the number of frames associated with each color.
In a second stage, all frames run through the policing function and all Red frames are dropped. Only Green and
Yellow frames can progress.
Metering of the GFP150 eXtra card is based on two IETF standards that can be selected via configuration:
Single Rate Three Color Marker (srTCM) per the IETF RFC 2697
Two Rate Three Color Marker (trTCM) per the IETF RFC 2698
When an interface is added to a VMAN, a traffic profile must be configured to be used with traffic entering that
interface. In the current version of the GFP150 eXtra card, an interface can be associated to only one VMAN,
hence only one profile.
Traffic profiles
Traffic profiles use the following parameters on the GFP150 eXtra card:
Parameter
CIR
PIR
EBS
CBS
Description
Committed Information Rate
Peak Information Rate
Excess Burst Size
Committed Burst Size
Unit
Mbps
Mbps
KB
KB
srTCM
YES
NO
YES
YES
trTCM
YES
YES
YES
YES
Figure 7-29 : Traffic profile

The QoS parameters strictly apply to the Ethernet traffic. The overhead generated by GFP encapsulation is not
accounted for in these rates.
srTCM (single rate Three Color Marker) :
A srTCM meter is useful for policing of a service where only the length and not the peak rate of the burst
determine its eligibility. Metering is based on a Committed Information Rate (CIR) and two associated burst
sizes, a Committed Burst Size (CBS) and an Excess Burst Size (EBS). A packet is set compliant or green if its
rate is less or equal to the CIR or if its excess rate does not exceed the CBS. It is set partially compliant or
yellow if its excess rate does exceed the CBS but not the EBS. It is set non compliant or red otherwise.
trTCM (two rate Three Color Marker) :
A trTCM meter is useful for policing of a service where a peak rate needs to be enforced separately from a
committed rate. Metering is based on two rates, Peak Information Rate (PIR) and Committed Information Rate
(CIR) and their associated burst sizes, Excess Burst Size (EBS) and Committed Burst Size (CBS). A packet is
set non compliant or red if its rate exceeds the PIR and its excess rate exceeds the EBS. A packet is set
compliant or green if its rate is less or equal to the CIR or if its excess rate does not exceed the CBS. Otherwise
it is set partially compliant or yellow.

Page A7-25
7 GFP150 EXTRA CARD
Congestion avoidance and buffer management

The GFP150 eXtra card uses a standard algorithm to control the distribution of resources between classes of
service LP (Low Priority) and SP (Strict Priority) in order to manage congestion phases.
The QOS configuration in the GFP150 extra holds account of the priority information affected to every
aggregate customer. The priority affectation to a customer is done according to a SLA (service level
agreement), via the field configuration "User Priority" (between 0 and 7). To a priority data (configured in UNI
and NNI untagged ports or extracted from VMAN tags in NNI tagged ports) corresponds a traffic class :
User Priority 0,1,2,3,4,5 => TC0 (Low Priority)
User Priority 6,7 => TC1 (Strict Priority)
In the current version of GFP150 eXtra card, congestion can happen on transmission on an Ethernet or an
Ethernet over SDH interface under the following two (non exclusive) circumstances:
In a point-to-multipoint topology, when traffic coming from several ports must be mixed for transmission over
another port of the GFP150 eXtra. There can be more or less transitory phases where the sum of incoming
traffic is significantly greater than the bandwidth available on the outbound port. Point-to-multipoint
topologies especially subject to this type of congestion are those involving an Ethernet port configured at
10Mbps or an Ethernet over SDH port configured with a small number of VCs.
Regardless of the actual topology, when a large quantity of traffic goes through the policing stage but with
the Yellow color (only partially compliant traffic). There can be more or less transitory phases where the
excess rate is actually too high to be transmitted fast enough over the outbound port. Traffic profiles
especially subject to this type of congestion are those with a large differential between the configured CIR
and PIR.
Some repetitive or lasting congestion problems generally require an evolution of the topology network.
7.2.4.2 - Configuring the QoS features

Configuring Metering and Policing, Classification
Examples above with Point-to-Point, Hub-and-Spoke and Bus topologies already describe the configuration of a
traffic profile when adding a new port to a VMAN (see Configuring the Ethernet Switch for each example).
Instructions are different to configure a traffic profile on ports already associated with a VMAN. Click on the
Switch link and on the VMAN List link. Then three commands are available:
Add Port: use this link to add a new port in a VMAN with a traffic profile
Delete Port: use this link to remove a port from a VMAN and remove the associated traffic profile
Modify Port: use this link to change the traffic profile associated with a VMAN configured on a port
The following screen shows the configuration of a srTCM traffic profile on an Ethernet port.

Page A7-26
7 GFP150 EXTRA CARD
Figure 7-30 : Configuring a srTCM profile
The following screen shows the configuration of a trTCM traffic profile on an Ethernet port.
Figure 7-31 : Configuring a trTCM profile
User Priority
The priority affectation to a customer (VMAN) is done via the "User Priority" field configuration (between 0 and
7). The values 6 and 7 are the most important values because they use the SP.
Parameters regulating for Classes of Service

The GFP150 eXtra card rules the reserved bandwidth for the SP queue (SP Bandwidth%). To read theses
informations, click on the " Global Params " link then on the " Classes of service " link ; the following screen is
then displayed:

Page A7-27
7 GFP150 EXTRA CARD
Figure 7-32 : Reading Traffic Classes parameters

If the operator wants to modify one of these parameters he must disactivate the calculation mode automatic.
For this, click on the "Global Params " link then on the "Advanced " link, select the wanted port for the mode
change, then pass from ON to OFF the column parameter " Auto ", then one can modify the SP bandwidth.
Figure 7-33 : Regulating Traffic Classes SP parameters

Page A7-28
7 GFP150 EXTRA CARD

SP Bandwidth % (1-100%) Translation in percentage of configured bandwidth for Strict Priority waiting
queue.
This queue encourages flux latency times that are affected to it, but with a limited queue shaping in order to
keep bandwidth for low priority queue.
Reading the SLA counters
The GFP150 eXtra card provides counters with the quantity of compliant (green), partially compliant (yellow)
and non-compliant (red) traffic received on a specific interface for a specific VMAN. Click on the Switch link
and on the VMAN List link. Select the row of the VMAN, click on the VMAN SLA Counters link. Then select a
port.
Figure 7-34 : SLA compliance counters

The GFP150 eXtra card also offers supplementary counters by port and VMAN.To read these counters, click on
the "Switch " link then on the "VMANPortCounters " link. In the top window, select the ETH and VCG ports on
which one wants these counters. The number is limited to 2.
In the below window, select the wanted port for the visualization.
Figure 7-35 : VMAN Port counters

Page A7-29
7 GFP150 EXTRA CARD
7.2.5 - Using the Multiple Spanning Tree Protocol on the GFP150 eXtra
card
7.2.5.1 - Description of the Multiple Spanning Tree Protocol on the GFP150 eXtra card
The GFP150 eXtra card enables activation of the "Multiple Spanning Tree Protocol " (MSTP), standard Ethernet
protocol defined in IEEE 802.1S.
MSTP can remove loops in an Ethernet network setup with redundant links. Without MSTP, these loops are
forbidden by the Ethernet standard to avoid a "broadcast storm ". With a loop and no MSTP, all broadcast
frames or unicast frames with an unknown address are endlessly replicated on all the links to the point where
the whole bandwidth is consumed.
In simple topologies such as point-to-point, hub-and-spoke or bus, MSTP is not necessary.
However, in ring or meshed topologies, MSTP is recommended since the network contains Ethernet loops.
Notes :
- A SDH loop to activate SDH protection mechanisms does not imply a loop at the Ethernet level. Ethernet links
are terminated by Ethernet ports or Ethernet over SDH ports.
- No MSTP must be activated on a flow created between a GFP150 eXtra card and a 4E/FE card. The provider
BPDU MSTP frames are not filtered by the 4E/FE card and are forwarded to the customer network.
On the GFP150 eXtra card, MSTP can be turned ON/OFF at a global level first. Then, once globally activated,
each port Ethernet or Ethernet over SDH can be included or not in the Spanning Tree. Once a port is configured
with MSTP, the protocol controls transmission over this port. Namely, MSTP can block transmission on the port
momentarily or until MSTP converges again following a link loss on an Ethernet port.
The MSTP protocol on the GFP150 eXtra card permanently exchanges control packets called "BPDUs " with all
other GFP150 eXtra cards running MSTP in the network. These packets are only forwarded on links included in
the Spanning Tree by configuration.
Note : In the present configuration, only the VMAN of which the identifying is between 4032 and 4094 can use
MSTP. Therefore, MSTP can only be used on 63 VMANS.
Warning :
- The VMAN ID of an activated VMAN cannot be modified ; this VMAN must be formerly suppressed.
- The aggregation of a VMAN using MSTP (VMAN ID from 4032 to 4094) with a VMAN without MSTP (VMAN
ID from 2 to 4031) can broke the traffic associated to the VMAN without MSTP because this last is automatically
in the CIST.
CIST and MSTI definition
CIST (Common Instance Spanning Tree) manages a region, when more than 63 instances are used.
MSTI (Multi Spanning Tree Instance) manages a VLAN.
CIST and MSTI are independent .
Each MSTI is independent of other one. Each MSTI corresponds to one and only one VLAN.
Port MSTP state
Once a port is included in the Spanning Tree, MSTP compute the state of the port based both on the
information of the BPDUs received from the network as well as the transitions of the operational state of any
local port (in case of link loss/recovery for example).
Each MSTP port is managed by two different informations PORT STATE and PORT ROLE.
PORT STATE can be:
"DISABLED " : The port is not included in the MSTP Protocol. This happens when the physical port is
disconnected or when MSTP is deactivated by configuration on that port.
"FORWARDING " : The port id included in the MSTP Protocol and is connected.
Page A7-30
7 GFP150 EXTRA CARD
PORT ROLE can be:

"DISCARDING " : The MSTP protocol decided to block transmission on the port to avoid an Ethernet loop.
Once a port in this state, it cannot receive or transmit any kind of Ethernet frame, except for MSTP BPDUs
that it continues to manage.
"BACKUP " : The MSTP protocol decided to block transmission on the port to avoid an Ethernet loop. This
state indicates the bridge has received its owner frame.
"LEARNING " : The port is going to transit to "DISCARDING " or "FORWARDING " state depending on the
result of MSTP convergence. No other Ethernet frame than BPDUs are received or transmitted on that port
in this state. However, in this state, MAC address learning starts for frames received on that port.
"DESIGNATED " : The port is completely functional. The port transmits data and learning @MAC.
"ROOT " : The port is completely functional. The port transmits data and learning @MAC. The root port is
the shortest way to the ROOT BRIDGE.
The following example displays a network with an Ethernet loop annihilated by MSTP. It shows the principle of
convergence towards a Tree topology ("Multiple Spanning Tree ") with a node elected as root of the tree ("Root
Bridge ").
Root Port
1
Bridge C
Designated
Port
Bridge A
Designated
Ports
Bridge Z
(Root)
Root Ports
Bridge D
Blocking
Designated
Port
Root Ports
4
3
Bridge B
2
1
Bridge E
Designated
Ports
Forwarding frames between Root ports and Designated ports
Figure 7-36 : MSTP port types

Page A7-31
7 GFP150 EXTRA CARD

Controlling MSTP convergence
A specific MSTP cost can be configured on every port (port priority), and on every Bridge (Bridge priority) in
order to control the Tree topology of the network during stable phases. At times where there is no link loss on
any port, either Ethernet or Ethernet over SDH. Naturally, redundant links blocked by MSTP during stable
phases can be unblocked when a link is lost in the network. Later, when the link failure is fixed and the primary
link comes back up, MSTP re-converges towards the stable topology and blocks back the redundant links.
Transparency of MSTP on the GFP150 eXtra
Per IEEE 802.1D standard, MSTP BPDUs must be sent with a reserved multicast address as MAC destination :
01-80-C2-00-00-00 ("Bridge Group Address "). "). By default, the GFP150 eXtra card uses the address :
01-80-C2-00-00-08.
However, the MSTP implementation on the GFP150 eXtra card supports configuration of a different multicast
address (standard : 01-80-C2-00-00-00 or non standard : inside the range 01-80-C2-00-00-04 to 01-80-C2-0000-0F) for use by the protocol. Using a different address does not change the MSTP algorithm at all. It is just a
way to distinguish the BPDUs sent by the GFP150 eXtra card from BPDUs sent by any other Ethernet bridge
(which would logically use the standard address).
The GFP150 eXtra cards are useful to interconnect client Ethernet LANs across a network providers backbone
(Ethernet over SDH). There can be cases where the clients themselves would be running STP between their
remote sites. By using a non standard address only known by the ADR2500 eXtra, the GFP150 eXtra card can
transport BPDUs coming from client networks in a totally transparent manner.
This way, the STP protocol in the operator network is completely isolated from any MSTP instances running in
the client networks. Moreover, the ADR2500 eXtra ensures continuity of clients STP across remote client sites.
Note : It is recommended not to activate MSTP on the Ethernet ports unless otherwise required by the
topology. It is generally useless to activate the operator MSTP on ports connected to client networks.
7.2.5.2 - MSTP Licence Activation on a GFP150 eXtra card

The MSTP utilization by the GFP150 eXtra card is submitted to a Licence. To activate this Licence, proceed as
following :
1) note the GFP150 eXtra MAC address on which the MSTP Licence must be activated
2) provide these informations to the Hotline via phone or E-MAIL to get the Licence key
3) enter the MSTP Licence key (32 characters) provided by the Hotline, via the "MSTP > Licence Activation"
menu, then click on Apply.
Figure 7-37 : MSTP Licence Activation

Page A7-32
7 GFP150 EXTRA CARD
Nota :
An alarm "No MSTP Licence" of card level is activated if at least one port has a MSTP configuration to ON and
if the MSTP licence is not activated.
The severity of this alarm is major and no configurable.
7.2.5.3 - Example of MSTP configuration

Use the previous example with a bus topology. Just a redundant link between the remote ADR2500 eXtra 1 and
3 is added. The final topology works like a ring.
First the 4 ADR2500 eXtra should be configured according to the instructions of the bus topology section of this
document (*). Then, the three steps below should be followed in order :
1. Configure the redundant link (*).
2. Activate MSTP on all ports of the bus (as well as on the redundant link)
3. Turn ON the redundant link
Once the link is activated, one should see that MSTP puts each end of the redundant link in the
"DISCARDING " state. All other ports of the bus go in "FORWARDING " or ROOT state.
(*) Warning : the used VMAN for MSTP should have a VMAM ID between 4032 and 4094 ; it will be 4032 for
this example.
Site n1
Eth / 4xVC12
Eth / 4xVC12
Site n3
SDH
Ethernet 10/100
Ethernet 10/100
Site n2
Ethernet 10/100
Site n4
Ethernet 10/100
Figure 7-38 : Example of MSTP configuration

Page A7-33
7 GFP150 EXTRA CARD
Bus configuration
See the bus section in this document. ( 7.2.2.4 -)
Configuring the redundant link between the ADR2500 eXtra 1 and 3
Configure the VCG#2 port on ADR2500 eXtra 1 and 3 with the same instructions as for VCG#2 between
ADR2500 eXtra 2 and 4.
In the end, ADR2500 eXtra 1 and 3 must be connected via VCG#2 configured with 6 VC12 and included in the
same VMAN as all other ports (VMAN ID "4032").
Note : The link is not activated yet in order to avoid creating an Ethernet loop in the network before MSTP is
running.
Activating MSTP on ADR2500 eXtra 2 and 4
Click on the "MSTP" link then on the "Bridge settings " link of the GFP150 eXtra card. Set the "MSTP Procotol "
parameter at the "MSTP " value and click on "Apply ".
Figure 7-39 : Activating MSTP on the ADR2500 eXtra 2 and 4 (1)

The default values of fields of the Bridge Configuration screen are those of the 802.1d norm ; to optimize the
times of convergence of the MSTP protocol, it is necessary to adjust the parameters "Forward Delay",
"Hello Time" and "Max Age".
The other parameters allow to configure MSTP according to the user's , Before modify these fields, read the
802.1s standard.

Page A7-34
7 GFP150 EXTRA CARD
Click on the "Port Settings " link. Set ports VCG#1 and VCG#2 at the "Enable " value and leave other field at
default value, then click on "Apply ".
Figure 7-40 : Activating MSTP on the ADR2500 eXtra 2 and 4 (2)
Activating MSTP on ADR2500 eXtra 1 and 3

To activate MSTP on cards n1 and n3, repeat previous step.
Activating the redundant link
On ADR2500 eXtra 1 and 3, we turn ON the VCG#2 interfaces :
Click on the VCG link of the GFP150 eXtra and then on the Settings link. Set the Admin Status of interface
VCG#2 to Up and click on Apply.
Once the two interfaces are activated, MSTP starts exchanging BPDUs across the new link and a new state is
calculated. However, after a few seconds each port of this link goes in "BLOCKING " state thanks to the
difference in "Path Cost " over the ring. Except for MSTP BPDUs, no Ethernet frame is forwarded over this link.
Connectivity check
It is possible to check a MSTI state on a GFP150 card.
Click on the "MSTP" link then on the "MSTI List" link.

Page A7-35
7 GFP150 EXTRA CARD
Figure 7-41 : MSTI Checking (1)
Select MSTI Id 1and click on the MSTI-Port Informations and Settings link to see the next panel.
All selected MSTI port state can be verified.
Figure 7-42 : MSTI Checking (2)

Page A7-36
7 GFP150 EXTRA CARD
7.2.6 - Using LCAS on the GFP150 eXtra card

7.2.6.1 - Description of LCAS
The GFP150 eXtra card enables activation of the standard protocol "Link Capacity Adjustment System" (LCAS)
independently on each of the 8 VCGs.
LCAS is useful to :
Dynamically add or remove VC members from a VCG without deactivating the VCG (making it a hitless
operation for traffic)
Dynamically adjust the available bandwidth when alarms are triggered ON/OFF on the VC members of a
VCG. The bandwidth of every VC under failure is subtracted from the VCG bandwidth. Hence, in case of
failures the VCG continues to forward traffic as long as there is still at least one operational VC.
Without LCAS :
The GFP150 eXtra card requires deactivation of a VCG before VC members can be added or removed (it
forces a traffic interruption)
A VCG becomes completely broken as soon as an alarm is triggered on at least one VC member. Plus, it
becomes operational again only once no VC is under failure anymore.
In order to run, LCAS only needs to be activated on both ends of a VCG. LCAS is transparent for the SDH
backbone point of view. Once both ends of a VCG are configured with LCAS they start exchanging control
information in the SDH overhead (namely, in the multi-frame of virtual concatenation).
LCAS can be used as a mechanism to protect transmission of Ethernet traffic : when a part of the VCs of a VCG
fail, transmission continues with the remaining operational VCs.
This protection mechanism makes sense only if the VCs of a VCG are not all configured the same way across
the SDH network :
Either they must take different path via independent SDH links ;
Or a part of the VCs must be protected at the SDH level (SNC, etc.) ;
Or some of both.
7.2.6.2 - Example of LCAS configuration

We use again the point-to-point connection example described earlier in this document. The VCs just use two
different SDH paths. The LCAS option is at Yes by default.
Configuring the VCG
Click on the VCG link and then on the List link. For the VCG#1 interface, select VC#1 and click on the Multiple
Add Member link. In the new screen coming up, select VC12 as type and VC#6 as last connection. Click on
Apply in order to create the virtually concatenated group of 6 VC12 (VC12#1 to VC12#6) that will be used to
transport Ethernet traffic.

Page A7-37
7 GFP150 EXTRA CARD
Figure 7-43 : Configuring the VCG (LCAS) (1)
LCAS at Yes and FCS at No. This screen also displays the type of VCG#1 (VC12) and the number of
constituting VC members (6).
Figure 7-44 : Configuring the VCG (LCAS) (2)
Click on the "Alarms " link. Select interface VCG#1 . Tick option "Monitor " and click on "APPLY " in order to
start monitoring alarms on this port (see Figure 7-9).

Page A7-38
7 GFP150 EXTRA CARD

Click on the Connection tap. Configure the connections from VC12#1 to VC12#6 of the GFP150 eXtra card in
way where 3 VC12 go through a SDH card and the 3 other VC12 go through a second SDH card. Make sure
you have end-to-end SDH connectivity with the remote ADR2500 eXtra.
Figure 7-45 : Configuring the SDH cross-connects (LCAS)

Page A7-39
7 GFP150 EXTRA CARD
7.3 - A FEW RULES FOR SET-UP

7.3.1 - Various configuration rules
1. The configuration of the Ethernet interface must be identical between the GFP150 eXtra card and the
transmission equipment present on the LAN. It is preferable to use the manual modes rather than the
"auto negotiation" mode because of the incompatibility of operation of this mode between certain
equipment.
2. The changes of configuration of VCG interface (LCAS, FCS) must be done when the interface is "OFF "
(Admin Status ticked "Down"). The interface is configured to "ON " (Admin Status ticked "Up") when
configurations of the 2 extremities of the link are effective. However, when LCAS is activated on a VCG
interface and when this interface is itself in the state "ON ", it is possible to modify the VCG composition
(add/delete VC members) without putting the interface "OFF " before. In this case, these modifications are
directly taken into account.
3. For each VCG, it is preferable to configure the FCS parameter to "No ".
7.3.2 - QoS configuration rules

It is necessary to respect the following rules, when configuring the QoS :
1. For each customer Ethernet interface, corresponding CIR and PIR must be under 100Mbit/sec if this
interface is configured in 100BaseT or in Auto negotiation, or under 10Mbit/sec if this interface is configured
in 10BaseT (corresponding to the Connection Automatic Control feature).
2. For each Ethernet over SDH interface with associated CIR and PIR, the VCG payload must be upper CIR +
0.1*(PIR-CIR) (corresponding to the Connection Automatic Control feature).
7.4 - APPLICATIONS
7.4.1 - Meshed networks
In topologies of the type "shared LAN", in multipoint to multipoint (EPLAN or EVPLAN), it is necessary to avoid
to create Ethernet loops between 2 GFP150 eXtra cards (site 1 to 2, 2 to 3 and 1 to 3)
- either to avoid to create Ethernet loops by construction of the links, which makes unnecessary the
activation of MSTP
- or to activate the "multiple spanning tree " protocol (MSTP).
7.4.2 - Protection of channels

The VC12/VC3 containers used by the GFP150 eXtra card can be protected by SNCP mechanism as all other
VC12/VC3.

Page A7-40
7 GFP150 EXTRA CARD
7.4.3 - Degraded mode

When a virtual container (VC3 or VC12) used by the GFP150 eXtra card is out of service, transmission folds
back on VC3/VC12 left (thanks to the LCAS protocol, when activated). In these conditions, transmission over an
interface is possible as long as there is at least one VC3 or VC12 available (for this interface).
When the VC3/VC12 comes back available, the VCG resynchronize automatically (thanks to the LCAS protocol)
and the transmission restarts over all the available VC3/VC12.
7.5 - TECHNICAL CHARACTERISTICS

7.5.1 - Main characteristics
Main characteristics of the GFP150 eXtra card in the ADR2500 eXtra are :
Default values of GFP header fields :

PFI field (Payload FCS Indicator ) is at 0 (absence of FCS on Payload)
Permanent values of GFP header fields :

PTI field (Payload Type Identifier) is at 000 (Data Client Frame)
EXI field (Extension Header Identifier) is at 0000 (Null Extension Header)
UPI field (User Payload Identifier) is at 0000 0001 (Frame-Mapped Ethernet)
Number of VCG per GFP150 eXtra card : 1 to 8
Number of virtual containers per VCG : from 1 to 46 VC12 (with a limitation to 63 VC12 for the whole VCGs)
or from 1 to 2 VC3 (with a limitation of 3 VC3 for the whole VCGs)
VCG/VC12-nV and VCG/VC3-nV mixity allowed
Differential delay between VCG containers VC12/VC3 : 47ms maximum for VC12 and 47ms maximum for
VC3
Ethernet interface 10/100BaseT half or full duplex
MTU is 1548 bytes (including @dest, @src, lgd trame and FCS), which allows to transport the ISL protocol.
Frames which length is under 64 bytes are rejected.
In validated PAUSE mode (Flow control), the PAUSE frames are generated and managed.
In no validated PAUSE mode, the received PAUSE frames are thrown and no PAUSE frame is generated.
The received PAUSE frames are counted in the InPauseFrame counter but not in the InOctets counter.
The MAC address table runs in IVL mode (Independent VLAN Learning)
Ethernet frames with a reserved MAC destination address (01-80-C2-00-00-00 to 01-80-C2-00-00-FF) are
transparently forwarded. It deviates from the IEEE recommendation for Ethernet bridges. However, this
design choice ensures continuity of the "client STP" across remote client sites. Naturally, if MSTP is
activated on the ADR2500 eXtra, frames received with the address 01-80-C2-00-00-00 (Mac STP address)
on MSTP ports will be transparently forwarded because the MSTP of ADR2500 eXtra uses the Mac
addresses 01-80-C2-00-00-04 to 01-80-C2-00-00-04F (by default 01-80-C2-00-00-08) (for more details, see
7.2.5.1 -).

Page A7-41
7 GFP150 EXTRA CARD
7.5.2 - Ethernet rate / VCG rate

The goal of this chapter is to help the user when configuring VCG regarding Ethernet rates on GFP150 eXtra
card interfaces.
Concerning Ethernet rates :
The Ethernet rate configured for each interface of the GFP150 eXtra card is corresponding to the payload
avalaible at the Ethernet interface.
This rate is called MTU (64 to 1548 bytes including 6 Bytes @dest, 6 Bytes @src, 2 Bytes lgd trame, and 4
Bytes FCS).
Knowing there is 12 intergap Bytes between 2 Ethernet frames, which are outside the payload, and 8
preamble Bytes per Ethernet frame, which are also outside the payload, when an Ethernet 100 BaseT
interface is used to the maximum of its capacity (end to end frames at 100Mbit/sec), payload rate in
100BaseT is 76.19Mbit/sec for 64 Bytes (MTU) frames, and 98.72Mbit/sec for 1548 Bytes (MTU) frames.
In the same way, payload rate in 10BaseT is 7.62Mbit/sec for 64 Bytes (MTU) frames, and 9.87Mbit/sec for
1548 Bytes (MTU) frames.
Because we dont control Ethernet frames lengths in a link, which may change from frame to frame, we
have to imagine the most critical case, in order to configure the VCG rate for the link. Note the GFP protocol
adds an 8 Bytes header (12 Bytes when the GFP FCS is ON), header taken into account in
7.5.3 -and 7.5.4 -
Note that even if we know how to configure, in the case of 100BaseT, a CIR upper than 1 and under 100
Mbit/sec (per 1Mbit/sec step) at the customer Ethernet interface (and in the case of the 10BaseT mode a CIR
between 1 and 10Mbit/sec sec (per 1Mbit/sec step)), some normal limitations are to be taken into account :
1. When the active mode is 100BaseT :
The maximum rate is 98.72Mbit/sec, with a limitation to 76.29Mbit/sec for a customer flow including only
64 Bytes length frames, even if the configuration is CIR=100Mbit/sec.
When the VCG is a VC3-2V, the Ethernet rate is limited to 96.27Mbit/sec by taken into account the GFP
header in the VC3-2V payload (VC3-2V payload is 96.768Mbit/sec). It is impossible in this case to
obtain an Ethernet rate upper 96Mbit/sec.
2. When the active mode is 10BaseT :
The maximum rate is 9.872Mbit/sec, with a limitation to 7.629Mbit/sec for a customer flow including only
64 Bytes length frames, even if the configuration is CIR=10Mbit/sec.
3. In all cases :
The addition of payload rates of each active VCG must be under the payload of a VC4. So, we can
consider 4 cases :
1. No VC3 used (neither for VCG, nor by another card in ADR2500 eXtra) : the number of all VC12
used must be 63.
2. 1 VC3 is used among all the VCG and/or the other cards in ADR2500 eXtra : the number of all
VC12 used must be 42.
3. 2 VC3 are used among all the VCG and/or the other cards in ADR2500 eXtra : the number of all
VC12 used must be 21.
4. 3 VC3 are used among all the VCG and/or the other cards in ADR2500 eXtra : No VC12 can be
used
Of course, if others VC3 and/or VC12 are used for transporting flows coming from other cards in
ADR2500 eXtra, it must be taken into account.
Note than all VCG VC3 based in the GFP150 eXtra card cant use more than 2 VC3.

Page A7-42
7 GFP150 EXTRA CARD
7.5.3 - Number of VC12 in a VCG

VC12 payload is Dvc12=2.176 Mbit/sec.
The maximum number of VC12 allowed per VCG equals 46.
We suppose customer Ethernet interfaces CIR and PIR in the link are already configured.
In point to point (EPLine service), the minimal number N of VC12 necessary for transmitting a CIR of E
Mbit/sec at the customer Ethernet interface is :
N = UPPER_ROUND_NUMBER(E*1.125/Dvc12) and N46
This calculation takes into account GFP header with FCS OFF. When FCS is ON, replace 1.125 with 1.1875.
Note that in this case, the customer Ethernet interface remote rate must equals E and we advise to configure
PIR=CIR.
Example :
If we suppose E=PIR=20Mbit/sec
We obtain N=UPPER_ROUND_NUMBER(20*1.125/2.176)=UPPER_ROUND_NUMBER(10.34)=11 (46)
In all cases, we advise after the configuration of customers interfaces Ethernet CIR/PIR and the corresponding
VCG, to configure Ethernet over SDH interfaces CIR/PIR as CIR=PIR=VCG payload.
7.5.4 - Number of VC3 in a VCG

VC3 payload is Dvc3=48.384 Mbit/sec.
The maximum number of VC3 allowed per VCG equals 2.
We suppose customer Ethernet interfaces CIR and PIR in the link are already configured.
In point to point (EPLine service), the minimal number N of VC3 necessary for transmitting a CIR of E
Mbit/sec at the customer Ethernet interface is :
N = UPPER_ROUND_NUMBER(E*1.125/Dvc3) and N2
This calculation takes into account GFP header with FCS OFF. When FCS is ON, replace 1.125 with 1.1875.
Note that in this case, the customer Ethernet interface remote rate must equals E and we advise to configure
PIR=CIR.
Example :
If we suppose E=PIR=60Mbit/sec
We obtain N=UPPER_ROUND_NUMBER(60*1.125/48.384)=UPPER_ROUND_NUMBER(1.395)=2 (2)
In all cases, we advise after the configuration of customers interfaces Ethernet CIR/PIR and the corresponding
VCG, to configure Ethernet over SDH interfaces CIR/PIR as CIR=PIR=VCG payload.

Page A7-43
7 GFP150 EXTRA CARD

Page A7-44
ANNEX A - CONSTRUCTION OF AN IP NETWORK ADDRESSING PLAN
A CONSTRUCTION OF AN IP NETWORK ADRESSING PLAN

This appendix provides a brief description of the rules implemented in building a TMN based on
an IP protocol stack.
A.1 - PRELIMINARY REMAR KS

The IP protocol stack is used in a data transmission network to transport data in the form of
packets between two points in the network.
Depending on the ISO model, IP is the network layer protocol. It is therefore in charge, within
each node, of routing the packets so that they can be routed in the network.
The protocols located below the IP correspond to the link and physical layers: these protocols
set up the links between two consecutive nodes in the network.
The protocols "above" the IP (TCP and UDP) are transport layer protocols. These protocols fulfil
end-to-end data transmission between two distant points in the network. The protocols based
on the TCP/UDP are application-oriented: they provide services such as file transfer (TFTP on
UDP, FTP on TCP), equipment management (SNMP), mail transfer (SMTP), etc.
The figure below describes how the main protocols acting in a network node are stacked.
HTTP server
HTTP
To downloading
Automaton
TFTP
SNMP
RIP
OSPF
UDP
TCP
ICMP
ARP
To operation
functions
IP
MAC
PPP
Ethernet
EOC
Figure A-1 : IP protocol stack

Note:
The MAC protocol is attached to the Ethernet physical port (point to multi-point media)
and the PPP protocol is attached to the physical ports ensuring the point-to-point links
(optical media, microwave, V11,...)

Page AA-1
A.2 - IP ADDRESSING
To route packets within a node, the IP uses an addressing mechanism: depending on the
destination address contained in the packet, the IP determines (by scanning its routing table)
the nearby router to which it must send the packet and deduces the physical interface on which
the packet must be sent. The term "router" and "equipment" will be used indifferently in the
discussions which follow.
There are two non-exclusive ways to manage the IP routing tables:
by static routes entered by the operator,
by of a routing daemon (such as RIP, RIP2, OSPF) which dynamically manages the routing
tables through the network.
The IP addresses are coded in the form of 4 bytes and are usually represented in decimal form
(example: 135.11.33.115). An IP address is divided into 3 fields at most:
NET field located to the left,
subnet field located at center,
host field located to the right.
The length of the first field depends on the class to which the address belongs. The length of
the "subnet" and "host" fields is defined by a mask associated to the address. There are three
address classes:
class A: the NET field is coded on the first byte; the three other bytes are reserved for the
SUBNET and HOST fields. The class A addresses vary from 1.0.0.0 to 126.255.255.254 ,
class B: the NET field is coded on the first two bytes; the other two bytes are reserved for
the SUBNET and HOST fields. The class B addresses vary from 128.0.0.0 to
191.255.255.254 ,
class C: the NET field is coded on the first three bytes; the last byte is reserved for the
SUBNET and HOST fields. The class C addresses vary from 192.0.0.0 to
223.255.255.254. ; up to 254 equipment can belong to a single class C IP network (having the
same NET).
Note:
Addresses beginning by 127 and addresses containing "1" or "0" in the SUBNET and
HOST fields are prohibited.
Note:
The IP standard allows that the SUBNET and HOST fields be coded on a number
of bits which does not correspond to a byte border. In general, this is not implemented
for address readability reasons and since most of the routing daemon (RIP)
implementations do not support this function.
The SUBNET field is defined by a mask which is written in the form: 255.255.255.0,
255.255.0.0, 255.0.0.0, etc: the number of bits at zero in the right hand part of the mask defines
the length of the HOST field. Ex: for address 40.2.2.2 associated to mask 255.255.255.0, the
NET field takes the value 40, the SUBNET field takes the value 2.2 and the HOST field
takes the value 2.

Page AA-2Sagem Communication document. Reproduction and disclosure prohibited
A.3 - ADDRESSING PLAN

A global IP network must be subdivided into N networks each having a "NET" number.
Within each network, each physical link (point-to-point or multipoint) has its own SUBNET
number.
Each equipment connected to this link (2 for a point-to-point link, N for an Ethernet segment)
has its own "HOST" number.
Depending on the number of equipment and links, class A, B and C addresses and
SUBNETs encoded on one or two types will be used.
To conclude, a pair formed by an IP address and its SUBNET mask shall be associated to
each interface of a network node.
A.4 - USE OF STATIC TABL ES

Where static tables are used, each network node must have its routing table completed to allow
it to correctly route the packets received.
All IP routes of a routing table for a given equipment comprise the following fields:
destination @IP: refers to the IP address of the equipment or sub-network (or even
network) to be reached from the given equipment,
subnet mask: sub-network mask associated to the IP address defined in destination

@IP ; all equipment whose IP address part defined by the 1 bits of this field correspond
to the same value as the destination @IP part defined by this same mask will be
reachable via this route,
next hop @IP: IP address of next equipment (connected directly with given equipment) to
which the packet will be sent,
metric (this can also be understood as "cost" or distance): value from 1 to 15 indicating the
number of hops to reach the equipment corresponding to the destination @IP address. 16
corresponds to infinite for the RIP routing daemon. This field is only used by a possible
routing daemon to choose a preferential route when several routes are available for the
same destination. This field can always be filled in with 1 to simplify if use of the field is not
necessary,
interf.: interface number for interface by which next equipment will be reached (whose IP
address is next hop @IP).
Note : When interface IP addresses are declared, implicit static routes are set up to the
associated SUBNETs. It is therefore not necessary to define static routes to join two
equipment belonging to a single SUBNET.
Note:
The IP addresses of an equipment are the addresses of its interfaces (or ports)
configured. The manager only knows one IP address per equipment. Therefore, the socalled Equipment IP address is often the address filled in the manager database. This
is the address of the port by which the equipment normally dialogues with the manager.
Note:
To use an equipment via a PC and an Ethernet interface, the IP address of the

operation PC must be modified so that it belongs to the same SUBNET as the Ethernet
interface used to connect to the network.
We recommend that you leave the HOST 1 number free on each subnet, meaning that
you begin to number the equipment starting with the HOST 2 number. The PC will then
always take an IP address of the type: NET.SUBNET.1
Note : A default router can be defined (this option is sometimes available) to which all packets
which cannot be routed by the routing table are transmitted.

Page AA-3

The figure below gives an example of an IP network and routing tables associated to two typical
equipment. Note that each port on the on-board routing function corresponds to a different
SUBNET.
140.1.1.3
F3
Manager
F1
140.1.0.2 140.1.0.3
Fiber
140.1.1.2
140.1.1.4
F2
Ethernet
128.1.0.2
128.1.0.1
Ethernet
NET 128.1
F4
140.1.1.5
128.1.0.3
NET 140 - 1
F6
F5
PPP1 150.1.0.2
Fiber
Fiber
150.1.0.3
F7
Ethernet
Ethernet
150.1.1.3
150.1.1.2
150.1.1.4
F8
150.1.1.5
F9
NET 160.1
F10
NET 150.1
Figure A-2 : Example TMN architecture
Configuration of ADR F6
Interfaces
Eth
Sub-network mask
128.1.0.3
255.255.0.0
PPP1
Sub-network mask
150.1.0.2
255.255.255.0
Other PPP
None
Static routes
Dest @IP
140.1.0.0
150.1.1.0
Subnet mask
255.255.0.0
255.255.255.0
Next hop
128.1.0.2
150.1.0.3
Interface
Metric
eth
ppp1
1
1
Remarks
Entire NET 140.1
Entire SUBNET 150.1.1


Configuration of ADR F8
Interfaces
Eth
Sub-network mask
150.1.1.3
255.255.255.0
Other PPP
None
Static routes
Dest @IP
128.1.0.0
140.1.0.0
150.1.0.0
Subnet mask
255.255.0.0
255.255.0.0
255.255.255.0
A.5 - USE OF RIP ROUTIN G
Next hop
150.1.1.2
150.1.1.2
150.1.1.2
Interface
Metric
eth
eth
eth
2
3
1
Remarks
Entire NET 128.1
Entire NET 140.1
Entire SUBNET 150.1.0
DAEMON
The RIP routing daemon for TCP/IP networks is based on the area and Autonomous System
(AS) principles, each having a different NET number.
An area contains a set of routers in a single geographical space.
An autonomous system (AS) contains a set of areas organized hierarchically with a

backbone area.
The RIP routing daemon periodically distributes all of its routing table. This makes this protocol
slower than the OSPF protocol. On the other hand, the RIP selects its active routes only on
the basis of the number of hops, i.e. the number routers crossed in a AS to reach a network.
On the other hand, the metric used by the OSPF protocol integrates other parameters.
Each AS is a RIP routing domain limited to a distance of 15 hops (max.) between two
equipment exchanging packets within the AS . The maximum distance is taken into account
to include the worst case network protection scenario.
These ASs are separate with respect to each other (within RIP) and connected by isolation
networks. Each isolation network, formed by a single Ethernet or point-to-point link, has its own
NET number.
The interfaces used with equipment belonging to an isolation network must be filtered (RIP
filtering option activated on interfaces) to inhibit export of RIP routing table automatic updates.
This equipment uses "border" typed interfaces.
Within an "AS", all the equipment must have their RIP routing daemon activated. Within each
"AS", each link connecting two equipment is described by a specific SUBNET value.
Routing from one AS to another AS via an isolation network is described by static routes.
In the example given above, NET 128.1 corresponds to an isolation network and NET
160.1. and 150.1 correspond to ASs in which RIP protocols are active.

Page AA-5
A.6 - USE OF OSPF ROUT I NG DAEMON

The OSPF routing daemon for IP networks is based on the same principle as the RIP
daemon except that the OSPF computes the routes using several parameters defined by the
administrator: link rate, cost of communication, number of hops, etc. This protocol also provides
for routing on areas of unlimited size.
Within an autonomous system AS, the border routers do not distribute all the routes, but only
route intervals, thus eliminating the need for a portion of the static routing tables.

ANNEX B - OPTICAL BOOSTER
B OPTICAL BOOSTER
B.1 - INSTALLATION
B.1.1 - Access security level
Connectors
Function
Power
Access to station power supply
Loops
Access to dry loops
Optical access points
Optical access "IN" and "OUT"
Safety level
SELV
SELV
Class 1 laser
Harmless
Table B-1 Access security level

Note : The safety level Laser class 1 (compliant to the standard EN 60 825) is got :
-
On the one hand, by output power shutdown when the input power is under a defined level
(for example fiber breaking) or when the hood for the protection of plugs is opened.
On the other hand, by a key switch which is authorized user's ownership.
B.1.2 - General information

The amplificateur booster is associated to the U16.2 card of an ADR2500 eXtra in order to supply a
regeneration section until 150 km.
This equipment is the subject of a separated Operation Manual "Optical Booster EDFA
(Er-Doped Fiber Amplifier)" N 288 107 383.
It appears as an independent module of 1U height, whose width is adaptable to 19" or ETSI size.
Booster depth is compatible with a 300-mm ETSI rack.
This equipment offers :
-
one key switch

one input optical access "IN" connected to the U16.2 card and one output optical access
"OUT" connected to the line ; these access points are protected by a hood
one 48 V power supply connector " DC POWER "
one connector with two alarm loops "ALARM PORT"
one LCD display allowing the user to know the operation parameters of the booster ; this
display is associated to three keys of command
one LED indicating the commissioning of the pump laser "POWER"
one operation status LED "NORMAL"
two alarms indicator LEDs "MAJOR" and "MINOR"
an unused connector for RS232 access

Page AB-1
Protection
hood.
Fibers
access
Key
Status LCD
switch of
and Display
the pump alarms
laser
LEDs
Keys of
command
Power supply
RS232
connector
Interface
Alarms
Pump laser
loops
status LED
Figure B-1 Optical booster Installation in rack
B.1.3 - Installation
The optical booster can be installed in a 19" or ETSI rack. A mounting kit to adapt the equipment to
either one is supplied. This kit contains :
-
a 19" left bracket

an ETSI left bracket
a 19" right bracket
an ETSI right bracket
a screws and flat washers kit
The mounting kit for installation of the equipment on the uprights of the 19" or ETSI rack, formed by 4
cage nuts and 4 screws, is not supplied with the equipment
Check that the unit's position in the rack does not prevent heat dissipation from other equipment ; to do
that, let 1 U between ADR2500 eXtra and booster.
Connect imperatively to the rack the pin ground located at the rear of the equipment.
No setting or configuration is needed on the equipment. All the parameters have been set in factory.
B.1.4 - Connection of access points

B.1.4.1 - Optical ports
Figure B-2 Optical booster Optical access points

Page AB-2
The booster offers one input optical access "IN" and one output optical access "OUT", on
optical fiber compliant to the ITU-T G652 recommendation.
Open the hood and connect the output optical cable of the ADR2500 eXtra on the SC/PC
connection "IN" of the booster and the output optical cable of the booster "OUT" to the line.
Remark : opening the hood leads to an optical output shutdown, however, it is preferable to
make these connections without powered booster.
B.1.4.2 - Power port

The optical booster can be powered either by a PAPA or by all other power supply sources.
9-way HE5 male connector
5
9
Pin N
1
6
Signal name
-48V1
6
OB1
-48V1
7
3
OB1
Reserved
8
4
OB2
-48V2
9
5
OB2
-48V2
NOTA : The shielding of the connector is connected to the equipment ground
Power supply interface :

Input voltage :
Two - 48 V power supply sources, TBTS type (Safety extra low

voltage)
Operating voltage range : - 36 V to - 60 V
Maximum voltage range : - 36 V to - 72 V
Power :
20 W max.

Page AB-3
B.1.4.3 - Alarm loops

Two dry loops outputs (Common, Set, Reset) used as station alarm
These loops can be collected by the ADR2500 eXtra via the CCU card ("LOOPS" access points)
HE5 - 15 pins Female Connector
8
15
Pin N
Signal name
Reserved
9
Reserved
Reserved
10
Reserved
11
Reserved
Reserved
Reserved
12
Minor R
Reserved
13
Minor C
14
Major R
Minor S
Reserved
15
1
9
Major C
Major S
B.2 - OPERATION
B.2.1 - General information
The equipment commissioning is realized by the switch key located on the front panel ; this key can be
removed either on the "ON" or "OFF" position.
The equipment monitoring is performed by :
-
one LCD display controlled by three push buttons

one LED indicating the commissioning of the pump laser " POWER " (green)
one indicator LED indicating the equipment status "NORMAL" (green)
two alarms indicator LEDs "MAJOR" (red) and "MINOR" (red)
two alarm loops
B.2.2 - Maintenance command and operation

It is possible to realize a maintenance operation by looping booster on ADR2500 eXtra reception via an
optical attenuator.
This operation allows local test of ADR2500 eXtra on booster.

Page AB-4
The optical attenuator value must be set such as ADR2500 eXtra received power is compliant with the
U16.2 card specification.
B.2.3 - Display and directions for use

By pressure on the right keys, the LCD display allows to acceed to two dropdown menus :
1 - "ALARM MENU" (default displayed menu) :
- failures indications
- operating parameters of booster :
- current and temperature of pump laser
- equipment temperature
- status of DC power supply
- input and output powers
2 - "MAIN MENU" : set up menu which does not be used.
B.2.4 - Alarm processing

The following table indicates the display, the activation of LEDs, alarm loops and APR (Automatic
Power Reduction) associated to each failure.
Failure indication
No failure
No power supply
LCD Display
"POWER"
LED
"NORMAL"
LED
"MAJOR"
"MINOR"
LEDs
"MAJOR"
"MINOR"
Loops
"NO ALARM"
Green
Green
Off
Opened
Off
Off
Off
Off
Consequ
ent
action
MAJOR
and MINOR
Power supply failure
"DC 48VX FAIL"
Green
Off
MAJOR
MAJOR
"NO ALARM"
Red
Green
Off
Opened
APR
"INPUT POWER LOW "
Red
Off
MAJOR
MAJOR
APR
"INPUT POWER HI"
Green
Off
MAJOR
MAJOR
Output power out of

limits
"OUTPUT POWER LOW "

"OUTPUT POWER HI"
Green
Off
MAJOR
MAJOR
Internal temperature
out of limits
"ENV TEMP OVER LIMITS"
Green
Off
MINOR
MINOR
"LD1 TEMP OVER "
Green
Off
MINOR
MINOR
"LD1 BIAS OVER"
Green
Off
MINOR
MINOR
Opened fiber hood

Input power under
threshold
Input power over
threshold
Laser temperature out

of limits
Laser current out of
limits
Table B-2 Failure indication definition

Page AB-5
B.3 - SPARE PART AND CABLES
Mnemonic
Designation
Optical booster
Code n
251 125 832
OPTICAL BOOSTER +14 DBM

Table B-3 List of items
Designation
Length
Code n
LOOPS Alarm loops
2,5 m
6 013 628
(1/2 cable)
12 m
6 013 161
POWER (1/2 cable)
3m
251 065 817
- (PAPA)
3m
55 670 797
IN or OUT Optical jumper
1,5 m
251 035 872
SC-PC/SC-PC
2,5 m
251 035 880
3,4 m
251 035 893
4,6 m
251 036 209
5,8 m
251 036 212
7m
251 036 220
8,2 m
251 036 233
9,4 m
251 036 241
12 m
251 036 251
15 m
251 036 262
20 m
251 036 275
Table B-4 List of available cables

Page AB-6
B.4 - TECHNICAL CHARACTERISTICS
EQUIPMENT
Optical characteristics
Wavelength range
Operating input range
Saturated output power
Noise figure
1530 nm to 1565 nm
-5 to +5 dBm
+14 to +17 dBm
6 dB max
Height
Width
Depth
Weight
Protection Index (PI)
1U
19" or ETSI
Compatible with a 300 mm ETSI rack
> 5 kg
Corresponds to PI of used rack
Consumption
Equipment
< 20 W
Mechanical (transport)
Mechanical (operation)
Climatic conditions
Relative humidity (storage)
Electrical
Interference voltage (radioelectric
frequency emissions)
Safety
Power
ETS 300 019-2-2

ETS 300 019-2-3
ETS 300 019
- 5 C to + 50C
- 20C to + 75C
5% to 95%
ETS 300 386-2 of September 1999
NF EN 55022
NF EN 60950, EN 60825
ETS 300 132-2 (equipment is TBTS)
Predicted reliability
Equipment
-6
5 10 at 40C
Table B-5 Technical characteristics

Page AB-7

Page AB-8
ANNEX C - MUX 10000 A/T
C MUX 10000 A/T
C.1 - INSTALLATION
C.1.1 - General information

Two MUX 10000 are proposed : a MUX 10000A and a MUX 10000T ; the MUX A is a double
equipment of the MUX T and so realizes the MUX T function twice.
The MUX 10000T is associated to an terminal node (terminal ADR2500 eXtra).
The MUX 10000A is associated to an add/drop node (add/drop ADR2500 eXtra).
The MUX 10000T realizes the optical multiplexing demultiplexing of four wavelengths included in the
C band and spaced of 1,6 nm (200 GHz). This MUX 10000T is associated with ADR2500 eXtra
equipment which supply the four optical STM-16 signals from L16.2+ cards.
The four wavelengths values are :
- 1547,72 nm 0,1
- 1549,32 nm 0,1
- 1550,92 nm 0,1
- 1552,52 nm 0,1
OUT MUX
Optical line
This function is described by the following synoptic :
IN MUX
IN 1547,72nm
OUT 1547,72nm
IN 1549,32 nm
OUT 1549,32 nm
IN1550.92 nm
OUT1550.92 nm
IN 1552.52 nm
MUX 10000T
OUT 1552.52 nm
Figure C-1 - MUX10000T Block diagram (1/2 MUX 10000A)
This equipment is made up of passive components, therefore no external power supply is

needed.

Page AC-1
ANNEXC - MUX 10000A/T
This equipment appears as an independent module of 1U height, whose width is adaptable to

19" or ETSI size.
All the MUX 10000T access points are SC/PC optical and are located on front panel.
Figure C-1 block diagram and figure C-2 front panel show the MUX 10000T access points :
-
4 multiplexer optical inputs IN 1547,72, IN 1549,32, IN 1550,92 and IN 1552,52 which are
connected to optical emissions of four L16.2+ cards, each one with the right wavelength.
4 demultiplexer optical outputs OUT 1547,72, OUT 1549,32, OUT 1550,92 and OUT
1552,52 which are connected to optical receptions of four L16.2+ cards.
1 output OUT MUX which corresponds to the multiplexer output and offers up to 4
wavelengths, each one supporting a STM-16 signal
1 input IN MUX which corresponds to the demultiplexer input and offers up to 4
wavelengths, each one supporting a STM-16 signal
MUX 10000T
OUT
OUT 1547.72
IN
OUT 1549.32
IN
MUX
IN
OUT 1550.92
IN
OUT 1552.52
IN
Figure C-2 MUX 10000 T Front panel
The MUX 10000T description applies also to the MUX 10000A ; this one contains, in the same
mechanism, two MUX 10000T functions. So, the MUX 10000A front panel presents the same
connectors access points twice.
MUX 10000A
OUT
OUT 1547.72
IN
OUT 1549.32
MUX1
IN
OUT
IN
OUT 1550.92
IN
OUT 1552.52
IN
OUT 1547.72
IN
OUT 1549.32
IN
MUX2
IN
OUT 1550.92
Figure C-3 MUX 10000 A Front panel
C.1.2 - Installation
Figure C-4 MUX 10000 A Installation in 19" rack

Page AC-2
IN
OUT 1552.52
IN
According to the MUX 10000 location (19" or ETSI rack), there are specific fixation organs :
-
two 19" brackets

two ETSI brackets
a screws and flat washers kit, already joined with the unit
The mounting kit for installation of the unit on the uprights of the 19" or ETSI rack, formed by 4
cage nuts and 4 screws, is not supplied with the equipment
Check that the unit's position in the rack does not prevent heat dissipation from other
equipment ; to do that, let 1 U between ADR2500 eXtra and MUX 10000.
No setting or configuration is needed on the equipment.
C.1.3 - Connection of access points
Figure C-5 MUX 10000 A or T Optical access points

All access points are located on equipment front panel
Connections :
-
Connect the optical output cables of the ADR2500 eXtra to the SC/PC connections IN
1547,72, IN 1549,32, IN 1550,92 and IN 1552,52 of the MUX 10000 (lower front plate
location)
Connect the optical input cables of the ADR2500 eXtra to the SC/PC connections OUT
1547,72, OUT 1549,32, OUT 1550,92 and OUT 1552,52 of the MUX 10000 (lower front
plate location)
Connect the optical output OUT MUX and input IN MUX cables of the MUX 10000 (uper
front plate location) towards the optical line.
C.2 - OPERATION
C.2.1 - General information

The equipment commissioning is realized by connection of optical cables on the associated
equipment and line.

Page AC-3
C.2.2 - Maintenance command and operation

It is possible to realize a maintenance operation by looping output OUT MUX of the MUX
10000 on its input IN MUX, via an optical attenuator.
This operation allows local test of ADR2500 eXtra on MUX 10000.
The optical attenuator value must be set so that the ADR2500 eXtra received power is
compliant to the L16.2+ card receiver specification.
C.2.3 - Multiplexing demultiplexing function specification

The following table gives technical specification of the multiplexing demultiplexing function.
Parameters
Operating Center
Wavelength
Tolerance in relation to the
Center Wavelength
Channel Spacing
Passband Width
MUX
Insertion loss
DEMUX
Units
nm
Values
Remarks
1547,72 / 1549,32 / 1550,92 /

1552,52
nm (Max)
0,1
nm
nm(Min.)
1,6
0,8 ( 0,4)
2.0
2.0
dB(Max.)
Passband Ripple
dB(Max.)
0,5
Channel Uniformity
dB (Max.)
Isolation
dB (Min.)
30
Isolation
dB (Min.)
40
Directivity
dB (Min.)
45
Return Loss
dB (Min.)
45
PDL
dB (Max.)
0,2
PMD
ps (max.)
0,2
Thermal stability
dB/C (max.)
0,005
Thermal Wavelength Drift
nm/C (max.)
0,002
Operating Temperature
0 to + 70
Storage Temperature
- 20 to + 70
Package Dimension
mm
88 X 58 X 6,6
Table C-1 - MUX/DEMUX Specification

Page AC-4
200 GHz
at 0,5dB
Adjacent
Channels
Non-Adjacent
Channels
LxWxD
C.2.4 - Optical power budget
Values
1547,72/1549,32/
1550,92/1552,52
Charactristics
Wavelengths (nm)
Agregate rate (Mbit/s)
9953,28 20 ppm
(4x2488,32)
Code
Budget without external
attenuator (*)
Mean launched power at S point
on each optical multiplexer input
(**)
Receiver sensitivity at R point
Receiver overload at R point
Connector
Uncoded (NRZ)
13 to 21 dB
+1 to +5 dBm
- 28 dBm
- 8 dBm
SC/PC
Table C-2 Optical power budget

(*) In case of short optical line, an external optical attenuator is required to obtain an attenuation
between 13 dB and 21 dB. This attenuator is put at emission side on the output OUT MUX.
(**) Foresee optical 6 dB for the Add-Drop function
C.3 - SPARE PARTS AND CABLES
Designation
Code n
MUX 10000 T
251 156 410
MUX 10000 A
251 163 949

Table C-3 List of items

Page AC-5
Designation
Length
Code n
IN or OUT Optical jumper
1,5 m
251 035 872
SC-PC/SC-PC
2,5 m
251 035 880
3,4 m
251 035 893
4,6 m
251 036 209
5,8 m
251 036 212
7m
251 036 220
8,2 m
251 036 233
9,4 m
251 036 241
12 m
251 036 251
15 m
251 036 262
20 m
251 036 275
Table C-4 List of available cables
C.4 - TECHNICAL CHARACTERISTICS
EQUIPMENT
Height
Width
Depth
Weight
Protection index (PI)
1U
19" or ETSI
< 300 mm
< 3 kg
Corresponds to Pi of used rack
Mechanical (transport)
Mechanical (operation)
Climatic conditions
Relative humidity (storage)
IEC 68-2-36 and IEC 68-2-29

IEC 68-2-27
ETS 300 019
- 5 C to + 45C
- 20C to + 70C
< 95%
Predicted reliability *
Equipment
-6
MUX T : 3,4 10
-6
MUX A : 6,8 10
Table C-5 Technical Characteristics

Page AC-6
En cas de difficults rencontres lors de l'installation ou de l'utilisation, n'hsitez pas :

If you encounter problems during installation or use, do not hesitate to:
CONTACTER NOTRE HOTLINE "PRODUITS SDH"

CONTACT OUR "SDH PRODUCTS" HOTLINE
UN SEUL NUMERO DE TELEPHONE :
ON A SINGLE TELEPHONE NUMBER:
en France mtropolitaine/in mainland France : 01 40 70 60 60
ou depuis l'tranger/or from abroad : 33 1 40 70 60 60
UN SEUL NUMERO DE FAX :
ON A SINGLE FAX NUMBER:
en France mtropolitaine/in mainland France : 01 40 70 60 80
ou depuis l'tranger/or from abroad : 33 1 40 70 60 80
UN SEUL Email :
ON A SINGLE Email address:
hotline.arp@sagem.com
N'oubliez pas de vous munir de votre numro de client qui est

inscrit sur votre facture.
Don't forget to provide yourself with your customer number
which is written on your invoice.
Installation and User Guide / Guide d'Installation et d'Utilisation 288 113 969-01
Document Sagem Communication. Reproduction et divulgation interdites
Sige social : 27, rue Leblanc - 75512 PARIS CEDEX 15 - FRANCE

Tl. : +33 1 58 11 77 00 - Fax : +33 1 58 11 77 50
http://www.sagem.com
Socit Anonyme au capital de 300 272 000 - 480 108 158 RCS Paris

288113969-01GB ADR2500eXtra

Transféré par

Droits d'auteur :

Formats disponibles

288113969-01GB ADR2500eXtra

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

288113969-01GB ADR2500eXtra

Transféré par

Droits d'auteur :

Formats disponibles

STM-16 ADD-DROP MULTIPLEXER

MULTIPLEXEUR ADD-DROP STM-16

Installation and User Guide

288 113 969-01

November 2006 Issue

288 054 178-01

Creation of original user guide/

288 054 178-02

Addition of SWITCH 32 VC4 HO/LO card

3E3DS3FA card / TCM function /

Addition of Pause mode (flow control)

New SDH alarms

Nouvelles alarmes SDH

288 054 178-04

288 113 969-01

STM-16 ADD-DROP MULTIPLEXER

Installation and User Guide

288 113 969-01

November 2006 Issue

Installation and User Guide- 288 113 969-01

PORTS SECURITY LEVELS

ADR2500 eXtra shelf ports security levels

G703 34 or 45 Mbit/s traffic access

G703 120 2 Mbit/s traffic access

G703 75 2 Mbit/s traffic access

G703 34 or 45 Mbit/s traffic access

G703 120 2 Mbit/s traffic access

Access to station power supply and alarms

Access to signaling and dry loops

Access to G.703 2 MHz synchronization

Access to remote management via Ethernet network

Access to local management via VT100 console or a

Optical interface cards

G.957 STM-n Optical access

G703 STM-1 Electrical access

Engineering Order Wire

Optical Gigabit Ethernet Access

Optical Gigabit Ethernet Access

GFP150 eXtra card

IEEE802.3 10/100 Base TX Ethernet / Fast Ethernet

Installation and User Guide- 288 113 969-01

Safe grounding obligation

Installation and User Guide- 288 113 969-01

Preservation of the environment as part of a sustainable development logic is an essential concern of

Installation and User Guide- 288 113 969-01

CHANGE LIST ..................................................................................................................................... 0-2

SECTION A - Installation and User Guide ........................A0-1 to AC-6

INSTALLATION ............................................................................................................................ 1-1

1.3.4 - Connection to CTRL-2G card .......................................................................................... 1-18

1.3.5 - Connection to AUX cards................................................................................................. 1-21

1.3.11- Connection to xGE-DM cards ......................................................................................... 1-29

COMMISSIONING AND OPERATION ......................................................................................... 2-1

Installation and User Guide- 288 113 969-01

2.2 - OPERATION .............................................................................................................................. 2-17

2.2.4 - Performance processing .................................................................................................. 2-55

2.2.9 - TCM Function................................................................................................................... 2-66

2.2.10 - Quality of service for VC4nv GigaEthernet .................................................................... 2-72

2.3 - CARDS PROTECTION ................................................................................................................. 2-78

SPARE PARTS AND CABLES .................................................................................................... 3-1

LIST OF NO ROHS ADR2500 EXTRA ITEMS ................................................................................ 3-1