ADR155C UserGuide

COMPACT 155 MBIT/SADD-DROP MULTIPLEXER

MULTIPLEXEUR ADD-DROPA 155 MBIT/S COMPACT

ADR155C P5.2

Installation and User GuideGuide d'Installation et d'Utilisation

288 091 808-02

Issue : May 2006

Edition : Mai 2006

Installation and User Guide / Guide d'Installation et d'Utilisation – 288 091 808-02Sagem Communication document. Reproduction and disclosure prohibitedDocument Sagem Communication. Reproduction et divulgation interdites

Page 0-2

LIST OF CHANGESREPERTOIRE DES MISES A JOUR

(A new edition replaces any previous versions)(Une nouvelle édition annule et remplace la précédente)

No/N° Date/Date Change description/Description de lamise à jour

Page/Page

01 March 2006/Mars 2006

Change from User Guide288 071 364-02 of July 2005 /Mise à jour du Guide utilisateur288 071 364-02 de Juillet 2005

New SDH alarms4E/FE card addition

New data features (EVPLAN, EVPLINE,MSTP) and New alarms on GFP /

Addition of Pause mode(flow control)

Nouvelles alarmes SDHAjout carte 4E/FE

Nouvelles fonctions data (EVPLAN,EVPLINE, MSTP) et

Nouvelles alarmes sur GFP /Ajout mode Pause (contrôle de flux)

All pages/Toutes pages

02 May 2006/Mai 2006

GFP Class Of Services correctionsCorrection Class Of Services GFP150

Chapter 6Chapitre 6

Installation and User Guide - 288 091 808-02SAGEM Communication document. Reproduction and disclosure prohibited Page A0-1

COMPACT 155 MBIT/S

ADD-DROP MULTIPLEXER

ADR155C P5.2

Installation and User Guide

Issue : May 2006

Installation and User Guide - 288 091 808-02Page A0-2 Sagem Communication document. Reproduction and disclosure prohibited

PORTS SECURITY LEVELSPort safety level for the ADR155C P5.2 subrack access

Connectors on the front panels

Function Securitylevel

Motherboard75 ΩΩΩΩ or 120 ΩΩΩΩSYNC G.703 120 Ω 2 Mbit/s synchronization ports SELV1

E1 OUTPUT and E1 INPUT G.703 75 Ω or 120 Ω 2 Mbit/s traffic ports SELVCOMM Access to local management via a VT100 console or a

PCSELV

ETH Access to remote management via Ethernet network SELVLOOPS Loops and remote signaling SELVPWRA/PWRB Power supply SELVPOWER –48V/2A MAXI Power supply SELVOptical CardsTR and REC G.957 Optical Ports STM-1 S1.1-2G, IC1.1-2G, IC1.2-2G,

STM-4 S4.1, L4.1, L4.2Laser class 1No Danger

EOW / AUX Engineering Order Wire SELVERE CardTR and REC G703 STM-1 electrical ports SELVEOW and AUX Engineering Order Wire SELVLAN1 CardETH Ethernet Port SELVGFP150 / 4E/FE CardsETH Ethernet Port SELVE3DS3 CardTR and REC G703 34 or 45 Mbit/s traffic ports SELV21E120, 21E1R8 CardsE1 OUTPUT and E1 INPUT G.703 120 Ω 2 Mbit/s traffic ports SELV21E75 CardE1 INPUT and E1 OUTPUT G.703 75 Ω 2 Mbit/s traffic Ports SELV

The subrack must be mounted only in racks with a bottom part that is closedor fitted with a class V1 or HF1 or better air filter, or that stand on a non-flammable floor.

Safe earth requirement

This equipment must be installed only by skilled personnel. For compliance, the protective earthterminal must be connected to a safe earth with an impedance Z of less than 5 Ohms.

Handling precaution: For any work to be carried out inside the equipment, anantistatic wrist strap must be worn.

1 Safety Extra Low Voltage Circuit

Installation and User Guide - 288 091 808-02Sagem Communication document. Reproduction and disclosure prohibited Page A0-3

ENVIRONMENT

Preservation of the environment as part of a sustainable development logic is an essential concern ofSagem Communication. The desire of Sagem Communication is to operate systems observing theenvironment and consequently it has decided to integrate environmental performances in the life cycleof 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 approvednational 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 theproduct 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 EquipmentWaste, which can have an effect on the environment and human health.


CONTENTS

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

SECTION A : Installation and user guide.......................A0-1 to AA-6

PORTS SECURITY LEVELS...................................................................................................A0-2

ENVIRONMENT.......................................................................................................................A0-3

CONTENTS.................................................................................................................A0-4 to A0-8

SECTION B : Guide d'installation et d'utilisation .............B0-1 à BA-6

1. INSTALLATION AND COMMISSIONING........................................................................................ 1-1

1.1 - GENERALITIES ............................................................................................................................ 1-11.2 - SUBRACK INSTALLATION.............................................................................................................. 1-4

1.2.1 - Generalities ........................................................................................................................ 1-41.2.2 - Installation of access modules ........................................................................................... 1-51.2.3 - Installation of STM-4 modules............................................................................................ 1-61.2.4 - Installation of GFP150 modules ......................................................................................... 1-6

1.3 - CONNECTING PORTS ................................................................................................................... 1-71.3.1 - Connecting on motherboard............................................................................................... 1-81.3.2 - Connecting on the Optical cards ..................................................................................... 1-141.3.3 - Connecting on the ERE card........................................................................................... 1-181.3.4 - Connecting on LAN1, 4E/FE and GFP150 cards............................................................. 1-201.3.5 - Connecting on E3DS3 card.............................................................................................. 1-211.3.6 - Connecting on 21E120, 21E75, 21E1R8 cards ............................................................... 1-22

1.4 - COMMISSIONING ....................................................................................................................... 1-241.4.1 - Communication function description ................................................................................ 1-251.4.2 - Description of DCC transparency function ....................................................................... 1-261.4.3 - Defining parameters for IP address and Ethernet port..................................................... 1-271.4.4 - Using HTTP Web browser .............................................................................................. 1-31

2. OPERATION .................................................................................................................................... 2-1

2.1 - FUNCTIONAL DESCRIPTION .......................................................................................................... 2-12.2 - GENERALITIES ............................................................................................................................ 2-12.3 - OPERATIONAL PARAMETERS........................................................................................................ 2-22.4 - PREDEFINED FUNCTIONS ........................................................................................................... 2-192.5 - ALARMS PROCESSING ............................................................................................................... 2-222.6 - PERFORMANCE PROCESSING..................................................................................................... 2-322.7 - PROCEDURE FOR REPLACING SUBASSEMBLIES ........................................................................... 2-33

2.7.1 - Replacing a card .............................................................................................................. 2-332.7.2 - Replacing the fan module................................................................................................. 2-34

2.8 - PREVENTIVE MAINTENANCE ....................................................................................................... 2-34

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

4. SPECIFICATIONS............................................................................................................................ 4-1


5. STARTUP GUIDE ......................................................................................................................... 5-1

5.1 - INSTALLING THE EQUIPMENT ........................................................................................................ 5-15.2 - CONNECTING TO AN ADR155C.................................................................................................... 5-25.3 - CONFIGURING A PPP PORT......................................................................................................... 5-95.4 - VIEWING THE ROUTING CONFIGURATION..................................................................................... 5-105.5 - BUILDING A POINT-TO-POINT LINK............................................................................................... 5-115.6 - BUILDING A BUS LINK................................................................................................................. 5-125.7 - BUILDING A RING....................................................................................................................... 5-135.8 - MANAGING EQUIPMENT THROUGH THE NETWORK OF A DIFFERENT SUPPLIER ............................... 5-14

6. GFP150 CARD ................................................................................................................................. 6-1

6.1 - GFP150 CARD AND SERVICES PRESENTATION ............................................................................ 6-16.2 - CONFIGURATION AND APPLICATIONS OF THE GFP150 CARDS....................................................... 6-3

6.2.1 - GFP150 card setup ............................................................................................................ 6-36.2.2 - Create a LAN interconnection ............................................................................................ 6-36.2.3 - Implementation of the OAM-CC function (Operation Administration Maintenance -Continuity Check) on the GFP150 card....................................................................................... 6-256.2.4 - Using Quality of Service features of GFP150 card .......................................................... 6-266.2.5 - Using the Multiple Spanning Tree Protocol on the GFP150 card..................................... 6-326.2.6 - Using LCAS on the GFP150 card .................................................................................... 6-40

6.3 - A FEW RULES FOR SET-UP......................................................................................................... 6-436.3.1 - Various configuration rules............................................................................................... 6-436.3.2 - QoS configuration rules.................................................................................................... 6-43

6.4 - APPLICATIONS .......................................................................................................................... 6-436.4.1 - Meshed networks ............................................................................................................. 6-436.4.2 - Protection of channels...................................................................................................... 6-436.4.3 - Degraded mode................................................................................................................ 6-44

6.5 - TECHNICAL CHARACTERISTICS .................................................................................................. 6-446.5.1 - Main characteristics ......................................................................................................... 6-446.5.2 - Ethernet rate / VCG rate .................................................................................................. 6-456.5.3 - Number of VC12 in a VCG............................................................................................... 6-466.5.4 - Number of VC3 in a VCG................................................................................................. 6-46

7. 4E/FE CARD..................................................................................................................................... 7-1

7.1 - 4E/FE CARD AND SERVICES PRESENTATION................................................................................ 7-17.2 - CONFIGURATION AND APPLICATIONS OF THE 4E/FE CARDS .......................................................... 7-1

7.2.1 - 4E/FE card setup ............................................................................................................... 7-17.2.2 - Create a LAN interconnect................................................................................................. 7-27.2.3 - Using LCAS on the 4E/FE card.......................................................................................... 7-8

7.3 - A FEW RULES FOR SET-UP......................................................................................................... 7-117.4 - APPLICATIONS .......................................................................................................................... 7-11

7.4.1 - Protection of channels...................................................................................................... 7-117.4.2 - Degraded mode................................................................................................................ 7-11

7.5 - TECHNICAL CHARACTERISTICS .................................................................................................. 7-117.5.1 - Main characteristics ......................................................................................................... 7-117.5.2 - Ethernet rate / VCG rate .................................................................................................. 7-127.5.3 - Number of VC12 in a VCG............................................................................................... 7-137.5.4 - Number of VC3 in a VCG................................................................................................. 7-14

A. BUILDING A MANAGEMENT NETWORK .....................................................................................A-1

A.1 - PRELIMINARY REMARK ................................................................................................................A-1A.1.1 - Unique address..................................................................................................................A-1A.1.2 - Supervision of PPP link......................................................................................................A-1A.1.3 - Routing protocols ...............................................................................................................A-1A.1.4 - Unnumbered links ..............................................................................................................A-1

A.2 - CONSTRUCTION OF AN IP NETWORK............................................................................................A-1A.2.1 - Static routes.......................................................................................................................A-1A.2.2 - Dynamic routes..................................................................................................................A-4


FIGURES

Figure 1-1 - ADR155C Subrack............................................................................................................ 1-3Figure 1-2 - ADR155C Subrack Installation ......................................................................................... 1-3Figure 1-3 - Connecting motherboard .................................................................................................. 1-8Figure 1-4 - Connecting S4.1, L4.1 and L4.2 Optical cards ............................................................ 1-14Figure 1-5 - Connecting S1.1-2G, IC1.1-2G, IC1.2-2G Optical cards ................................................ 1-14Figure 1-6 - Connecting ERE card..................................................................................................... 1-18Figure 1-7 - Connecting LAN1 card.................................................................................................... 1-20Figure 1-8 - Connecting GFP150 card ............................................................................................... 1-20Figure 1-9 - Connecting 4E/FE card................................................................................................... 1-20Figure 1-10 - Connecting on E3DS3 card........................................................................................... 1-21Figure 1-11 - Connecting 21E120, 21E75, 21E1R8 cards ................................................................. 1-22Figure 1-12 - Commissioning procedure for ADR155C network ........................................................ 1-23Figure 1-13 - Examples of the communication function configuration................................................ 1-25Figure 1-14 - Shelf View" screen of Web browser.............................................................................. 1-33Figure 1-15 - Menu structure .............................................................................................................. 1-35

Figure 2-1 - Synchronization from the 2 MHz external sync input (T3) .............................................. 2-20Figure 2-2 - Synchronization from a 2 Mbit/s port............................................................................... 2-20Figure 2-3 - Remote loopback function (registering alarms on central site)....................................... 2-21

Figure 6-1: Hardware design of the card .............................................................................................. 6-2Figure 6-2 : EPLine service .................................................................................................................. 6-3Figure 6-3 : Configuring the Ethernet interface .................................................................................... 6-4Figure 6-4 : Configuring the VCG (1).................................................................................................... 6-6Figure 6-5 : Configuring the VCG (2).................................................................................................... 6-6Figure 6-6 : Configuring the Ethernet Switch (1) .................................................................................. 6-7Figure 6-7 : Configuring the Ethernet Switch (2) .................................................................................. 6-8Figure 6-8 : Configuring the SDH Cross Connects............................................................................... 6-8Figure 6-9 : Connectivity check ............................................................................................................ 6-9Figure 6-10 : Service EVPLine ........................................................................................................... 6-10Figure 6-11 : Configuring the VCG (1)................................................................................................ 6-11Figure 6-12 : Configuring the VCG (2)................................................................................................ 6-11Figure 6-13 : Configuring the Ethernet Switch................................................................................... 6-12Figure 6-14 : Configuring the SDH Cross Connects........................................................................... 6-13Figure 6-15 : EPLAN service .............................................................................................................. 6-14Figure 6-16 : Configuring the Ethernet interface ................................................................................ 6-15Figure 6-17 : Configuring the VCG (1)................................................................................................ 6-16Figure 6-18 : Configuring the VCG (2)................................................................................................ 6-16Figure 6-19 : Configuring the Ethernet Switch (1) .............................................................................. 6-17Figure 6-20 : Configuring the Ethernet Switch (2) .............................................................................. 6-18Figure 6-21 : EPLAN Service - "bus" mode........................................................................................ 6-19Figure 6-22 : Configuring the VCG (1)................................................................................................ 6-20Figure 6-23 : Configuring the VCG (2)................................................................................................ 6-21Figure 6-24 : Configuring the Ethernet Switch (1) .............................................................................. 6-22Figure 6-25 : Configuring the Ethernet Switch (2) .............................................................................. 6-22Figure 6-26 : EVPLAN Service - "bus" mode...................................................................................... 6-24Figure 6-27 : Example of OAM utilization ........................................................................................... 6-25Figure 6-28 : QoS architecture ........................................................................................................... 6-26Figure 6-29 : Traffic profile ................................................................................................................. 6-27Figure 6-30 : Configuring a srTCM profile .......................................................................................... 6-28Figure 6-31 : Configuring a trTCM profile ........................................................................................... 6-29Figure 6-32 : Reading Traffic Classes parameters............................................................................. 6-29Figure 6-33 : Regulating Traffic Classes WRR/SP parameters ......................................................... 6-30Figure 6-34 : SLA compliance counters ............................................................................................. 6-31


Figure 6-35 : VMAN Port counters...................................................................................................... 6-31Figure 6-36 : MSTP port types............................................................................................................ 6-33Figure 6-37 : MSTP Licence Activation .............................................................................................. 6-34Figure 6-38 : Example of MSTP configuration.................................................................................... 6-35Figure 6-39 : Activating MSTP on the ADR155C 2 and 4 (1) ............................................................. 6-36Figure 6-40 : Activating MSTP on the ADR155C 2 and 4 (2) ............................................................. 6-37Figure 6-41 : MSTI Checking (1) ........................................................................................................ 6-38Figure 6-42 : MSTI Checking (2) ........................................................................................................ 6-39Figure 6-43 : Configuring the VCG (LCAS) (1)................................................................................... 6-41Figure 6-44 : Configuring the VCG (LCAS) (2)................................................................................... 6-41Figure 6-45 : Configuring the SDH cross-connects (LCAS) ............................................................... 6-42

Figure 7-1 : EPLine service .................................................................................................................. 7-2Figure 7-2 : Configuring the Ethernet interface .................................................................................... 7-3Figure 7-3 : Configuring the VCG (1).................................................................................................... 7-5Figure 7-4 : Configuring the VCG (2).................................................................................................... 7-5Figure 7-5 : Configuring the SDH Cross Connects............................................................................... 7-6Figure 7-6 : Connectivity check ............................................................................................................ 7-7Figure 7-7 : Configuring the VCG (LCAS) (1)....................................................................................... 7-9Figure 7-8 : Configuring the VCG (LCAS) (2)..................................................................................... 7-10Figure 7-9 : Configuring the SDH cross-connects (LCAS) ................................................................. 7-10

TABLES

Table 1-1 - Designation of ADR155C slots........................................................................................... 1-5

Table 2-1 - Functional Blocks of ADR155C.......................................................................................... 2-1Tables 2-2 to 2-15 - Configuration parameters..................................................................................... 2-3Tables 2-16 and 2-17 - Commands.................................................................................................... 2-17Table 2-18 - Spécific indicator lights of Motherboard ......................................................................... 2-22Table 2-19 - Spécific indicator lights of LAN1 card............................................................................. 2-22Table 2-20 - Spécific indicator lights of GFP150 card ........................................................................ 2-22Table 2-21 - Spécific indicator lights of 4E/FE card............................................................................ 2-23Table 2-22 - "STATUS" indicator light ................................................................................................ 2-23Table 2-23 - Spécific indicator lights of E3DS3 card .......................................................................... 2-23Table 2-24 - Pushbuttons ................................................................................................................... 2-23Tables 2-25 to 2-29 - Alarms and severity.......................................................................................... 2-24

Table 3-1 - ADR155C Components list ................................................................................................ 3-1Tables 3-2 and 3-3 - Available cables list ............................................................................................. 3-2

Tables 4-1 to 4-5 - ADR155C technical characteristics........................................................................ 4-1

1 - INSTALLATION AND COMMISSIONING

Installation and User Guide - 288 091 808-02 Sagem Communication document. Reproduction and disclosure prohibited Page A1-1

1. INSTALLATION AND COMMISSIONING

1.1 - Generalities

The ADR155C is an optical STM-1/STM-4 add-drop multiplexer used to build STM-1/STM-4point-to-point links, STM-1 or STM-4 rings, or mesh networks with conduct (SNC) or STM-1 line(MSP) protection, so performing the conveyance of PDH links at 2 Mbit/s, 34 or 45 Mbit/s, ofSDH STM-1 links, of 10/100 Mbit/s Ethernet links.

The ADR155C can be used as :

STM-1 terminal multiplexer with maximum capacity of 63 VC12 and capability of 1+1protection,

STM-1 repeater, capability of regenerating 2 VC4,

STM1 multiplexer with insertion/extraction, with maximum capacity of switching of 4 STM-1more 21 VC12,

STM-4 ADD/DROP multiplexer with capacity of 63 VC12 over one AU4 per STM-4 card.

LAN over VC12 or VC3 interconnection point (via LAN1, 4E/FE and GFP150 cards).The GFP150 and 4E/FE data traffics are compatible with those of the GFP150 eXtra card ofthe ADR2500 eXtra.

This equipment can be managed :

by a local terminal with VT100 emulation required on commissioning for communicationparameters configuration (COMM access),

by an HTTP server for local or remote interactive operation using a Web browser,

remotely, by means of a SNMP protocol via an IONOS NMS management network system ;SNMP protocol using also allows the global supervision of the network.

Management network connections are performed via DCC D1-D3 or D4-D12 of the STM1 orSTM-4, via VC12_192K (compatible mode ADR2500C or ADR2500 eXtra) of the STM1 or STM-4 or on Ethernet (ETH) interfaces of the equipment.

The ADR155C is placed in 19" or ETSI racks. It consists of :

a 2U subrack fitted with a Backplane and a Motherboard grouping together the basicfunctions of the equipment : supervision, switching matrix, synchronization system, 21 G.7032 Mbit/s E1 tributaries and a secured 48V DC power supply ; the motherboard can be with75Ω or 120Ω E1 interface according to the model.

a FAN module, consisting of two redundant ventilation units ; this module is optional (see §1.2.2).

an optional Holdover card (inserted in factory) allowing to preserve a rhythm in case offailing of the synchronization source.



four traffic cards, either : IC1.1-2G or IC1.2-2G or S1.1-2G STM1 optical card allowing a VC4 connection or 3

VC3 connections or 63 VC12 connections or a combination of VC3/VC12 connections ERE STM1 electrical card allowing a VC4 connection or 3 VC3 connections or 63 VC12

connections or a combination of VC3/VC12 connections S4.1 or L4.1 or L4.2 STM4 optical card allowing a VC4 connection or 3 VC3

connections or 63 VC12 connections or a combination of VC3/VC12 connections Ethernet 10/100 one port LAN1 card allowing 2 VC3 connections Ethernet 10/100 eight ports GFP150 card allowing up to 63 VC12 or 3 VC3 or a

combination of VC3/VC12 connections in 8 Virtually Concatenated Groups Ethernet 10/100 four ports 4E/FE card allowing up to 63 VC12 or 3 VC3 or a

combination of VC3/VC12 connections in 4 Virtually Concatenated Groups G.703 34/45Mbit/s E3DS3 card allowing one VC3 connection G.703 21x2 Mbit/s 21E120 card allowing 21 VC12 120Ω connections. G.703 21x2 Mbit/s 21E75 card allowing 21 VC12 75Ω connections. G.703 21x2 Mbit/s 21E1R8 card allowing 21 VC12 120Ω connections, with

resynchronizaton function of the E1 flows on 8 channels.

For the connection of the different ports of cards, see § 1.3 - Connecting ports

Remark :

The informations concerning the STM1-1G optical cards that can be inserted, recognized andmanaged therefore by the system, are defined in the User Guide N56717020108 of January2005.



Figure 1-1 - ADR155C Subrack

1

2U

76,2mm

2

SYNCSYNCSYNCSYNC E1 OUTPUTE1 OUTPUTE1 OUTPUTE1 OUTPUT

1

Left uprightsof rack

Two M6x12HM screw

Two M6cage nuts

19" rack mounting ETSI rack mouting

Two M6cage nuts

Two M6x12HM screw

ADR 155C19" rack

2U

2

SYNCSYNCSYNCSYNC E1 OUTPUTE1 OUTPUTE1 OUTPUTE1 OUTPUT

ADR 155CETSI rack

76,2mm

Figure 1-2 - ADR155C Subrack Installation

A B

C M

F

D

E



1.2 - Subrack installation

1.2.1 - Generalities

The ADR155C subrack can be mounted in a 19" or ETSI rack. (see Figure 1-2 - ADR155CSubrack Installation)

The ADR155C package is provided with a mounting kit to adapt the subrack to a 19" or ETSIrack.

This kit contains :

two brackets for adaptation to the rack,

4 screws M3x4,

4 flat washers M3

8 screws CBLXS M3x6 to attach optional cards

The mounting kit for installation of the subrack on the uprights of the rack, containing 4 cagenuts and 4 screws M6x12, is not supplied with the subrack.

The ADR155C subrack consists of :

a motherboard located in the lower part (item M),

four slots (items A to D), designed to accommodate the traffic cards,

a slot located on the left of the subrack designed to accommodate the optional ventilationmodule (item F),

a slot located on the right of the subrack designed to accommodate the Holdover card(item E)

There is no adjustment or configuration to do on the equipment to install. Set-up is operating oncommissioning or by means of built-in operating software.

Dummy covers are provided for empty slots and are supplied with each equipment.

All connections are performed on front panel of the equipment.

Installation in a 19" rack

The ADR155C has, in option, a system of thermal control by ventilation ; during the installation,provide for sufficient space for the ventilation aperture on the left of the subrack, and also for theaeration, at the top and right of the subrack. On the other hand, never hinder the natural airconvection on the right side.

Perform the following operations :

provide a 2U place in the rack for each equipment and a 1U space between equipments.Deflectors are recommended to limit the temperature of the ambient air around theequipment.

secure the attaching brackets for mounting in 19" rack, on either side of the subrack,

clip, on either side of the rack, two M6 cage nuts (item 1),

position the subrack back in front of the rack,

slide the subrack until attaching brackets are in contact with uprights, opposite the 4 cagenuts, and then secure the subrack with 4 M6x12 hex head screws (item 2).



Installation in an ETSI rack

The installation of the subrack in ETSI rack is identical with that in 19" rack.

In this case, use the set of attaching brackets specific for mounting in ETSI rack.

Installation of cards

RECALL : Prior to any operation on the cards, the operator must be provided with anantistatic bracelet.

1.2.2 - Installation of access modules

Slot A GFP150 (*)STM1-2G

ERELAN14E/FE

E3DS321E12021E75

21E1R8

Slot B STM4STM1-2G

ERELAN14E/FE

E3DS321E12021E75

21E1R8

Slot C GFP150 (*)STM1-2G

ERELAN1

4E/FEE3DS321E12021E75

21E1R8

Slot D STM4STM1-2G

ERELAN14E/FE

E3DS321E12021E75

21E1R8

Slot F

FAN

Slot M – CARTE MERE

Slot E

HOLDOVER (**)

Table 1-1 – Designation of ADR155C slots

(*) One GFP150 card max per shelf

(**) Factory option



ADR155C slots are non-dedicated. However, in order to make wiring easier and ensure thehomogeneity among sites, it is advisable to proceed as follows :

position the tributary cards from C slot clockwise

position the agregate cards from D slot counter-clockwise

check the ventilation module presence in its reserved slide if the configuration requires it.This module is mandatory as soon as :

a GFP150 card is inserted in the shelf the shelf is at an ambient temperature out of class 3. 2 of ETS 300019 : between 45°C

and 55°C.This module can only be set out if no GFP150 card is inserted in the shelf.

the ADR155C shelf is provided with the mothercard and, according to the chosen options,with FAN module and Holdover card already inserted.Secure each card through M3 screws of Torx type (6-branch star), using a suited screwdriver

FACOM reference AZX.10X75 Or STANLEY reference 1-67-494

1.2.3 - Installation of STM-4 modules

The use of STM-4 cards presents the following particularities :

The ADD/DROP mode is the only one available (no terminal mode with line protection)

The B and D slots are, in this case, dedicated to STM-4 cards. In case of only one STM-4card utilization, the second slot can however be used by another type of card.

Only one STM-1 channel can be extracted from the STM-4 flow, the three other one being in by-pass ; the choice of this channel is selected by the menu "AU-4 Selection" of the STM-4 card.

1.2.4 - Installation of GFP150 modules

The use of GFP150 cards presents the following particularities :

Only one GFP150 can be installed in an ADR155C shelf either in the A slot or in the C slot ;the presence of FAN module is mandatory.

As soon as a GFP150 card is inserted, the fans of FAN module are automatically started up



1.3 - Connecting ports

The cards can be extracted without intervening on the other cards or on their connections.

The connections to be performed on the equipment depend on the chosen configuration :

On the subrack motherboard strip :

power supply ports : " POWER –48V 2A MAXI "

Remote indication, remote control and station alarm port "LOOPS"

IP address configuration port "COMM" : allows the connection to a VT 100 emulation orhyperterminal

Ethernet management port "ETH".

2Mbit/s G.703 120Ω synchronization port "SYNC"

21x2Mbit/s G.703 75Ω or 120Ω traffic ports "E1 INPUT and E1 OUTPUT".

On the STM-1 optical card :

G.957 STM-1 optical ports "TR" and "REC"

engineering Order Wire port "EOW / AUX"

On the STM-4 optical card :

G.957 STM-4 optical ports "TR" and "REC"

2 engineering Order Wire ports "AUX" and "EOW"

On the STM-1 electrical card :

G.703 STM-1 electrical ports "TR" and "REC"

2 engineering Order Wire ports "AUX" and "EOW"

On the 21E120 and 21E1R8 cards :

G.703 21x2Mbit/s 120Ω traffic ports "E1 OUTPUT" and "E1 INPUT"

On the 21E75 card :

G.703 21x2Mbit/s 75Ω traffic ports "E1 OUTPUT" and "E1 INPUT"

On the E3DS3 card :

G.703 34 ou 45 Mbit/s traffic ports "TR" and "REC"

On the LAN1 card :

Ethernet traffic port "ETH"

On the GFP150 card :

8 Ethernet traffic ports "ETH"

On the 4E/FE card :

4 Ethernet traffic ports "ETH"



Connection requirements :

For a right distribution of cords on either side of the subrack, the connections of slots A andC, the 21x2Mbit/s access ports and synchronization access of the mothercard are orientedleftward. All other connections are oriented rightward.

The run of cords must not hinder the extraction of a module; in particular, connecting cablesof the left subrack half is to be secured to the frame with enough backlash to enable theventilation module (optional) to be extracted during a maintenance operation.

Refer to the list of available cables in chapter 3 - Spare parts and Cables.

1.3.1 - Connecting on motherboard

Figure 1-3 – Connecting motherboard

1.3.1.1 - Power Supply access ports

Connecting Power Supply must be realized by qualified staff.

"PWRA" and/or "PWRB" ports, used when the equipment is powered from one or two 48 Vsources, the power source(s) should be limited to 100 VA.

"PWR" port used when the equipment is powered from a main voltage (230 V AC), via anoptional power block (100-240V//48V - 1.5A).In this case, it is necessary to let OB1 and OB2 of PWRA and PWRB accesses floating inrelation to the ground.

Observe the following connection requirements :

"PWR" and "PWRA" and/or "PWRB" Power supply ports can be connected simultaneouslyprovided that the OB of PWRA/PWRB is not joined to the electrical ground (mechanicalground).

Always connect the equipment side before the energy source side.

The power block must be installed far from any heat source, and no traction must beexercised on its connecting wires.

The used cable to connect the power block to the energy source must have a minimalsection of 1,5 mm² and be qualified <HAR> H03 VV_F ou <HAR> H03 VVH2_F.

The connecting land between the power block and the energy source must be respected.

The connecting electrical installation must be realized according to the present nationalstandard.

PWRA/B PWR



"PWRA"/"PWRB" power supply interface :

Input voltage One or two Safety Extra Low Voltage (SELV) type – 48V sources

Voltage range allowed : - 36 V to - 60 V

Maximum voltage range : - 36 V to - 72 V

Power 100 VA maximum

Connector Male 9-way HE5

65

91

Pin N° Signal name

1 -48B16 OB1

2 -48B17 OB1

3 Reserved8 OB2

4 -48B29 OB2

5 -48B2

NOTA : The shielding of the connector is connected to the equipment ground

"PWR" power supply interface :

Port Connecting transformer 110-240//48V - 1.5A/

Connector Jack (core = OBJ and shield = - 48 VJ).



1.3.1.2 - Remote indication, remote control and station alarm port ("LOOPS")

"LOOPS" Interface :

Ports 4 remote indication inputs for floating contacts (Local user inputs),biased to -48 V internally, active when closed and with electricalisolation (loop current = from 1 to 10 mA),

2 dry loop outputs (common, normally closed and normally open)(Local user outputs) for station alarm or remote control use(maximum current = 100 mA on resistive load). The common pointof each loop is internally connected to OB ; by default, the loop A isnormally open and the loop B is normally closed.

(Schematic diagram of a dry loop)

Connector Female 15-way HE5

9158 1

Pin N° Signal name Comments

1 BREAK B Normally closed contact of dry loop B9 COMMON B Common contact of dry loop B

2 MAKE B Normally open contact of dry loop B10 Break A Normally closed contact of dry loop A

3 COMMON A Common contact of dry loop A11 Make A Normally open contact of dry loop A

4 GND Ground12 R- MON 4 P (OB) User input N°4

5 R-MON 4 N13 R- MON 3 P (OB) User input N°3

6 R- MON 3 N14 R- MON 2 P (OB) User input N°2

7 R- MON 2 N15 R- MON 1 P (OB) User input N°1

8 R- MON 1 N

NOTE : OB is the result of a logical "OR" between signals OBJ, OB1 and OB2 on the "PWR", "PWRA" and"PWRB" power supply interfaces.

1.3.1.3 - Management and Administration ports

"COMM" Interface :

Ports RS232, connecting VT100 standard console or emulation

Bit rate 19200 bauds (8 data bits, no parity bit and 1 stop bit),

Connector Female 9-way HE5

65

91

M C B




1 DCD Connected to DSR6 DSR Data Set Ready (to DCE)*

2 RX Received data (to DCE)*7 RTS Request To Send (from DCE)*

3 TX Transmitted data (from DCE)*8 CTS Clear To Send (to DCE)*

4 DTR Data Terminal Ready (from DCE)*9 RI Ring Indicator (not connected)

5 GND Ground

* The ADR155C is seen as DCE

Connection cable

1

95

61

6

95

Wiring diagram

VT100 or PCside

Male 9-way connector

Equipment side"COMM"

Female 9-way connector

"ETH" Interface :

Port Ethernet management interface operating at 10 Mbit/s in half-duplex or fullduplex mode according to the mode used by theinterlocutor (dynamic adaptation of the Ethernet port on each newlog-in of the interlocutor),

All equipment (PC, Router…) connected on this interface mustnot be configured in 100 Mbit/s forced mode.

If the Ethernet interface doesn't work, force the configurationof the network card of the PC in duplex half mode.

Connector Shielded RJ45 Type.

Pin 1 Pin 8

Front view


1 TX_ETH_TIP Output (hot point)2 TX_ETH_RING Output (cold point)3 RX_ETH_TIP Input (hot point)4 NC Reserved5 NC Reserved6 RX_ETH_RING Input (cold point)

7 and 8 NC Reserved



NOTE : One LED is linked to the "ETH" port :• Off : Incorrect link and Link Down• Flashing : current reception and Link Up• On steady : Correct link and Link Up but no activity.

1.3.1.4 - G.703 2 MHz Synchronization port

"SYNC" Interface

Ports Two G.703 2MHz external synchronization inputs (T3) and twoG.703 2MHz clock outputs (T4) compliant with ITU-T G.703Recommendation (§ 13.3 for input port, § 13.2 for output port)

Impedance 120 Ω balanced

Connector Female 9-way HE5 (120 Ω).

6

5

9

1


1 GND Ground6 TX1 RING (T4-) Output T4-1 (cold point)

2 TX1 TIP (T4+) Output T4-1 (hot point)7 RX2 TIP (T3+) Input T3-2 (hot point)

3 RX1 TIP (T3+) Input T3-1 (hot point)8 RX1 RING (T3-) Input T3-1 (cold point)

4 RX2 RING (T3-) Input T3-2 (cold point)9 TX2 RING (T4-) Output T4-2 (cold point)

5 TX2 TIP (T4+) Output T4-2 (hot point)

NOTA : The shielding of the connector case is connected to the subrack front panel ground

The 75 Ω ohm unbalanced interfaces are obtained by adding a cable which also provides BNCconnectors.

1.3.1.5 - G.703, 21 x 2 Mbit/s traffic port

"E1 INPUT" and "E1 OUTPUT" Interfaces

ports 21 x 2 Mbit/s traffic ports compliant with the ITU-T G.703Recommendation (§ 6.3 for input port, § tab.6 for output port)

Bit rate 2,048 Mbit/s ± 50 ppm,

Code HDB3,

Impedance 75 Ω or120 Ω balanced, according to the model of motherboard

Connector SUB D HD female 44 pins supporting L907 cable (21 ports).

This interface uses two connectors : E1 INPUT connector for inputs (named RX) andE1 OUTPUT connector for outputs (named TX)



15 13044 31

16

Pin N° Ports Signal name Comments

16 GND ground 31 1 TX(RX) 1B Output (Input) 2 Mbit/s (hot point) 1 TX(RX) 1A Output (input) 2 Mbit/s (cold point) 17 2 TX(RX) 2B Output (Input) 2 Mbit/s (hot point) 32 TX(RX) 2A Output (input) 2 Mbit/s (cold point) 2 3 TX(RX) 3B Output (Input) 2 Mbit/s (hot point) 18 TX(RX) 3A Output (input) 2 Mbit/s (cold point) 33 4 TX(RX) 4B Output (Input) 2 Mbit/s (hot point) 3 TX(RX) 4A Output (input) 2 Mbit/s (cold point) 19 5 TX(RX) 5B Output (Input) 2 Mbit/s (hot point) 34 TX(RX) 5A Output (input) 2 Mbit/s (cold point) 4 6 TX(RX) 6B Output (Input) 2 Mbit/s (hot point) 20 TX(RX) 6A Output (input) 2 Mbit/s (cold point) 35 7 TX(RX) 7B Output (Input) 2 Mbit/s (hot point) 5 TX(RX) 7A Output (input) 2 Mbit/s (cold point) 21 8 TX(RX) 8B Output (Input) 2 Mbit/s (hot point) 36 TX(RX) 8A Output (input) 2 Mbit/s (cold point) 6 9 TX(RX) 9B Output (Input) 2 Mbit/s (hot point) 22 TX(RX) 9A Output (input) 2 Mbit/s (cold point) 37 10 TX(RX) 10B Output (Input) 2 Mbit/s (hot point) 7 TX(RX) 10A Output (input) 2 Mbit/s (cold point) 23 11 TX(RX) 11B Output (Input) 2 Mbit/s (hot point) 38 TX(RX) 11A Output (input) 2 Mbit/s (cold point) 8 12 TX(RX) 12B Output (Input) 2 Mbit/s (hot point) 24 TX(RX) 12A Output (input) 2 Mbit/s (cold point) 39 13 TX(RX) 13B Output (Input) 2 Mbit/s (hot point) 9 TX(RX) 13A Output (input) 2 Mbit/s (cold point) 25 14 TX(RX) 14B Output (Input) 2 Mbit/s (hot point) 40 TX(RX) 14A Output (input) 2 Mbit/s (cold point) 10 15 TX(RX) 15B Output (Input) 2 Mbit/s (hot point) 26 TX(RX) 15A Output (input) 2 Mbit/s (cold point) 41 16 TX(RX) 16B Output (Input) 2 Mbit/s (hot point) 11 TX(RX) 16A Output (input) 2 Mbit/s (cold point) 27 TX(RX) 17B Output (Input) 2 Mbit/s (hot point) 42

17 TX(RX) 17A Output (input) 2 Mbit/s (cold point)

12 TX(RX) 18B Output (Input) 2 Mbit/s (hot point) 28








15 GND Ground

NOTA : The shielding of the connector case is connected to the subrack front panel ground



1.3.2 - Connecting on the Optical cards

Each optical module STM-4 provides connection for :

one STM4 optical interface ("TR" transmission port and "REC" reception port)

two 64 Kbit/s accesses, order wire channel "EOW" and auxiliary channel "AUX".

Figure 1-4 - Connecting S4.1, L4.1 and L4.2 Optical cards

Each optical module STM-1 provides connection for :

one STM1 optical interface ("TR" transmission port and "REC" reception port)

one 64 Kbit/s access "EOW/AUX", order wire channel or auxiliary channel according to theconfiguration.

Figure 1-5 - Connecting S1.1-2G, IC1.1-2G, IC1.2-2G Optical cards

1.3.2.1 - Connecting STM-1/STM-4 interfaces

Remove the contact protection connector,

Connect STM-1 or STM-4 interface to front panel connectors :

Transmission TR Connector

Reception REC Connector

STM-4 transmission port

STM-4 reception port





"TR" and "REC" ports :

Interface Type IC 1.1-2G, IC 1.2-2G, S1.1-2G, S4.1, L4.1, L4.2

Bit rate STM-1 : 155.520 Mbit/s ± 20 ppm,STM-4 : 622.08 Mbit/s ± 20 ppm

Standard ITU-T G.957

Encoding Uncoded (NRZ),

Interface Fiber Transmitoptical power

Max. receivedpower

Sensibility at10-10

GaranteedAttenuation

Typicalrange

Connector

IC1.1-2G Single-mode1310nm

-5 to 0 dBm 0 dBm -34 dBm 0 - 28 dB 0 - 65 km SC/PC

IC1.2-2G Single-mode1550nm

-5 to 0 dBm 0 dBm -34 dBm 0 - 28 dB 0 - 80 km SC/PC

S1.1-2G Single-mode1310nm

-15 to -8 dBm -8 dBm - 28 dBm 0 - 12 dB 0 - 15 km SC/PC

S4.1 Single-mode1310nm

-15 to -8 dBm -8 dBm - 28 dBm 0 - 12 dB 0 - 15 km SC/PC

L4.1 Single-mode1310nm

-3 to +2 dBm -8 dBm - 28 dBm 10 - 24 dB 10 - 40 km SC/PC

L4.2 Single-mode1550nm

-3 to +2 dBm -8 dBm - 28 dBm 10 - 24 dB 10 - 80 km SC/PC

1.3.2.2 - Connecting order-wire channels

"EOW" and "AUX" Interfaces :

Port synchronous V.11 (differential),

Bit rate 64 kbit/s,

Optical STM-4 cards connector : Female 15-way HE5.8 1

15 9

Pin N° Signal name Polarity Comments

1 - Not connected9 TB (+)

2 TA (-)Input for data to send over the SDH line and sampled on the risingedge of clock T64 (B-A)

10 TOFPB (+)3 TOFPA (-)

Transmit mode byte sync output indicating the positioning of bit 1and sent on the rising edge of clock T64 (B-A)

11 RB (+)4 RA (-)

Output for data extracted from SDH line and sampled on the fallingedge of clock R64 (B-A)

12 ROFPB (+)5 ROFPA (-)

Receive mode byte sync output indicating the setting of bit 1 andsent on the falling edge of clock R64 (B-A)

13 R64B (+)6 R64A (-)

64 kHz receive clock output

14 T64B (+)7 T64A (-)

64 kHz transmit clock output

15 - Not connected8 Ground



Optical STM-1 cards connector : Shielded RJ45 Type – female 8-way.

Pin 1 Pin 8

Front view

Pin N° Signal name Polarity Comments

1 RB (+)2 RA (-)

Output for data extracted from SDH line and sampled on the fallingedge of clock R64 (B-A)

3 TB (+)6 TA (-)

Input for data to send over the SDH line and sampled on the risingedge of clock T64 (B-A)

4 T64B (+)5 T64A (-)

64 kHz clock accompanying the transmit data T(B-A) . Input incodirectional mode and output in contradirectional master mode.

7 R64B (+)8 R64A (-)

64 kHz clock output accompanying the receive data R(B-A)

Timing diagram for the "EOW/AUX" interface in contra-directional mode (64 kbit/ssynchronous use) :

B8 B1 B2

B8 B1 B2

R64 (B-A)

R (B-A)

ROFP (B-A)

T64 (B-A)

T (B-A)

TOFP (B-A)

(receive clock output)

(output for data receivedfrom STM1/STM4 line)

(receive synchro bytepulse outputOnly for STM4 and ERE)

(transmit clock output)

(input for data to transmitover STM1/STM4 line)

(transmit synchro bytepulse outputOnly for STM4 and ERE)



1.3.2.3 - Connecting with MSP operation (STM-1 cards)

As EOW / AUX port is physically integral with Optical modules, operating the order wire /auxiliary channel with MSP protection requires the use of a "Y" cord electrically connecting thesignals of EOW / AUX connectors.

Optical Working Card

Optical Protection Card

"Y" cord (*) fororder wire / auxiliary

channel operation

EOW / AUXTR REC

EOW / AUXTR REC

Likewise, in order to ensure a good behavior during the changeover from one module to theother, the operator should take care to keep identical configurations on both Optical cards ; incase of modification, automatic recopy is done and a warning message appears.

Only the connections are not identical. There must be no connections on the "Protection"module, as in all the connections are made to the "Working" module.

More over, the management links (PPP over DCC) must be created on the « Working » moduleand not on the « Protect » module.

(*) "Y" CORDD

This cord is gotten by linkage of two Sub-D / RJ45 adapters cords on one "Y" cord.



1.3.3 - Connecting on the ERE card

Figure 1-6 - Connecting ERE card

Each ERE module provides connection for :

one STM1 electrical interface ("TR" transmission port and "REC" reception port)

two 64 Kbit/s accesses, order wire channel "EOW" and auxiliary channel "AUX".

1.3.3.1 - Connecting electrical STM-1 interfaces

"TR" and "REC" ports :

Bit rate 155.520 Mbit/s ± 20 ppm,

Standard ITU-T G.703 § 12,

Encoding CMI

Electrical level 1V ±0,1V c to c

Transmit optical power -5 to 0 dBm

Input Attenuation 12,7 dB in √f at 78MHz

Input adaptation ≥15 dB between 8MHz and 240MHzAttenuation

Connector BNC 75 ohms or1.6/5.6 75 ohms (with BNC - 1.6/5.6 adapter)

1.3.3.2 - Connecting order-wire channels

"EOW" and "AUX" Interfaces :

See § 1.3.2.2 (female 15-way HE5 connector)





1.3.3.3 - Connecting with MSP operation

As EOW and AUX ports are physically integral with Electrical modules, operating the order wireand auxiliary channels with MSP protection requires the use of a "Y" cord electrically connecting,one by one, identically, the signals of EOW and AUX connectors.

EOW TR RECAUX

Electrical Working Card

Electrical Protection Card

"Y" cord fororder wire

channel operation

"Y" cord forauxiliary wire

channel operation

EOW TR RECAUX

Likewise, in order to ensure a good behavior during the changeover from one module to theother, the operator should take care to keep identical configurations on both Electrical cards ; incase of modification, automatic recopy is done and a warning message appears.

Only the connections are not identical. There must be no connections on the "Protection"module, as in all the connections are made to the "Working" module.

More over, the management links (PPP over DCC) must be created on the « Working » moduleand not on the « Protect » module.



1.3.4 - Connecting on LAN1, GFP150 and 4E/FE cards

Figure 1-7 – Connecting LAN1 card

Figure 1-8 - Connecting GFP150 card

Figure 1-9 - Connecting 4E/FE card

"ETH" Interface :

Port Traffic Ethernet interface operating at 10 or 100 Mbit/s in half-duplex or fullduplex mode according to the mode used by theinterlocutor (validated or not autonegotiation),

Connector Ethernet 10 or 100 BaseT - Shielded RJ45 Type.

Pin 8 Pin 1 Pin 1 Pin 8

LAN1 Card front view GFP150 and 4E/FE Cards

LAN card has a direct Ethernet interface.The GFP150 has a direct, crossed or automatic Ethernet interface depending on theconfiguration.4E/FE card has an automatic Ethernet interface



Pin N° Signal name Function(direct interface)

Function(cross interface)

1 TX_ETH_TIP Ethernet output (hot point) Ethernet input (hot point)2 TX_ETH_RING Ethernet output (cold point) Ethernet input (cold point)3 RX_ETH_TIP Ethernet input (hot point) Ethernet output (hot point)4 NC Reserved Reserved5 NC Reserved Reserved6 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

Electrical characteristics compliant with the IEEE 802.3U

1.3.5 - Connecting on E3DS3 card

Figure 1-10 - Connecting on E3DS3 card

"TR" and "REC"ports :

Ports 75 ohms 34/45 Mbit/s Interface compliant to ITU-T G.703(§ 5 and 8) Recommendation and ETS 300 166 allowing 34 Mbit/sor 45Mbit/s plesiochronous stream exclusive connection

Connector BNC 75 ohms or1.6/5.6 75 ohms (with BNC - 1.6/5.6 adapter)

34 or 45 Mbit/s transmission port

34 or 45 Mbit/s reception port



1.3.6 - Connecting on 21E120, 21E75, 21E1R8 cards

2 Mbit/s traffic connections (75Ω or 120Ω according to the card), performed on "E1 INPUT" and"E1 OUTPUT" ports on the 21E120, 21E75, 21E1R8 card are identical with those performed on"E1 INPUT" and "E1 OUTPUT" ports on the front side of the motherboard (see § 1.3.1.5)

Note : on the 21E1R8, the retiming function is supported by the ports #1 to #8

Figure 1-11 – Connecting 21E120, 21E75, 21E1R8 cards

2Mbit/s transmission port

2Mbit/s reception port



Equipment Inventory

- 48 V Power Supply Check

Aggregate optical loopback

LOCAL TEST

Local Test on networkof last équipment ?

no

Link established

Optical measurements

MSP protection check

24 H link Performance

Counters reset

Equipment operational(constitution of installation file)

Tributary Ports continuity check

A and B loops and alarms check

Local transmission test (30 mn) *

Optical connection

Connection of external sync input from of an "Master" equipment (optional)

Configuration Elaboration

- 48 V redundancy Check

yes

Insertion of communication parameters (VT100)

Setting to time and insertion of the test configuration tributary accesses(HTTP browser)

* case of underequipped unitary equipment

Configuration Save

EOW and AUX ports test

Figure 1-12 – Commissioning procedure for ADR155C network



1.4 - Commissioning

This paragraph describes the Equipment commissioning at general way. For more details, seethe chapter 5 "Startup Guide".

The equipment can be operated from a PC fitted with VT100 emulation and HTTP Webbrowser; its minimum configuration is defined in the paragraph 5.2 of "Startup Guide"

A local terminal with VT100 emulation is indispensable during the first commissioning, in orderto be able to access the equipment via the management function ; however, this terminal onlyenables the communication function to be parameterized (definition of the equipment IPaddress).

Procedure.

On the first commissioning, the equipment scans its constitution and considers it as theexpected configuration, in service, monitored. It is thus advisable to insert the traffic cardsbefore power-up, in order to speed up the commissioning.

Switch on the power supply connected to the equipment.

The equipment conducts self-tests : When self-tests have run correctly, the "ON" indicator is lit, In the opposite case, an indicator flashing code defines the faulty self-test (contact the

Hotline).

Parameterize the communication interface, using the VT100 (see § 1.4.3).

Using the HTTP Web browser, (see § 1.4.4). Update the equipment time and date Configure the remote management ports using the Web browser

Connect the 2 Mbit/s, 34/45 Mbit/s, Ethernet, Fast Ethernet, STM-1, STM-4 and SYNCports, according to the required equipment composition,

Connect the AUX and EOW ports required.

Download a predefined configuration or prepare the desired configuration, using the HTTPWeb browser : Create the connections Establish the wished protection (MSP protection, SNC protection ...) Choose the synchronization source, and change its parameters if required. Change, if necessary, the monitoring parameters and the alarms configuration.

The default configuration of the various parameters is provided by § 2.3.

Conduct the tests on STM-n links, complying with the process described in Figure 1-12

From that moment, the equipment is operational.

Operating alarms can signal a wrong connection of interfaces. Check the connection ofports, the alarms corresponding to the connected ports, and correct any problems that mayarise.

Save configuration.

REMARK : It is possible, once the commissioning is performed, to connect additional 2 Mbit/s G.703,E3/DS3, Ethernet,STM1 or STM-4 ports, and to insert or extract powered cards.



1.4.1 - Communication function description

Figure 1-13 – Examples of the communication function configuration

x

xx

ADR

ADR

ADR

FOT C *

D4 - D 12STMnon East

HTTP

SNMP

PPP

ETH

H T PT

S N PM

RPPP

H T PT

S N PM

R

HT

P PP

R

HTTP

SNMP

RPPP

ETH

S N PM

R

PPP

ETH

H T PT

S N PM

R

PPP

ETH

H T PT

S N PM

R RRoutingfunction

E

HTE

P PP

Application

. HTTP server

. SNMP agent for IONOS

Mngt port

. ETH port

. 4 PPP ports (Point to Point Protocol)see details § 1.4.3

Communication function over an ADR 155C

Example 1 : communication over a point to point link of ADR155C

D1 - D3 over STMn D1 - D3 over STMn

Example 2 : communication over an ADR 155C and FOT 155C ring

D4 - D 12

STMnon West

D1 - D 3

STMnon East

D1 - D 3

STMnon East

D1 - D 3

STMnon West

D1 - D 3 STMnon West

IONOS

The TPI can be connected to anyEthernet interface as soon as theparameterezing enables to reachone equipment to be operated

IONOS is necessaryto operate this FOT C

(but the ADR can be operated from the ETH interface of the FOT C

D1 - D 3

on STMntributary

D1 - D 3

on STMnaggregate



The VC12_192K management mode is compatible with those of ADR2500C and ADR2500eXtra ; it is configurable via HTTP.

1.4.2 - Description of DCC transparency function

The transparency functionality of the DCC flows (D1-D3, D4-D12) allows to transport, in an ADRnetwork, the management flows in transparency of another operator by using the DCCr (D1-D3).

In an heterogeneous network of ADR155C, ADR2500C or eXtra and no-ADR equipment :

the ADR equipment management is transported through the management VC12 whenthey must cross a network of no-ADR.

the no-ADR management is transported through the DCCr of the ADR when they mustcross a network of ADR.

The DCCm of ADR155C are not compatible with those of ADR2500C or ADR2500 eXtra ; theirrates are different.

The transparency of the DCC is independent of the protection mechanisms. The operator mustuse a mechanism of routage to protect its path of DCC.

The transparency of the DCCr and DCCm 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 transportedflow.



1.4.3 - Defining parameters for IP address and Ethernet port

Figure 1-13 presents the available resources and various configurations possible for thecommunication function :

1. Connect the "COMM" access to a free "COM" port on the PC with VT100 emulation.

2. Switch on the PC.

3. If it is the first time you run the "Hyperterminal"application on this PC :

successively select, in the Windows desktop, the Start, Programs, Accessories andHyper terminal buttons,

select the icon representing the "Hyperterminal"application : a description window forthe application is displayed.

enter a name and choose an icon for the connection, then validate your choices : a newwindow is displayed.

select the "COM" port on the PC which is connected to the equipment then validate yourchoice. 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 configuration.

save the connection ("Save" command in application File menu).

NOTE : The next time you want to open the "Hyperterminal" application, you will simplyneed to choose the connection icon to connect to the equipment. Once the equipment ispowered up, the operation menu is displayed.

to exit the "Hyperterminal" application, select Exit in the File menu.

4. Open a session and enter your password (to configure the communication function, youneed to have "supervisor" rights)

NOTE : by default, for the initial commissioning procedure, the password is empty.

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 adifferent 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 REBOOToperates itself without affecting the trafic.Error message : "Equipment address is mandatory" : the equipment address is mandatorywhen 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."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 differentsubnetworks.When the IP address exists and is modified, equipment REBOOT is proposed. This REBOOToperates itself without affecting the trafic.

Choice "3" : equipment REBOOT.

This command is used to immediately reboot the application and restart with the parametersalready 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 timeperiod can be configured using the manager).



Choice "5" : Ping.

"IP Address" : Choice of IP address of equipment to be contacted.Round trip time in msNOTE : The Ping command is used to check the accessibility and the return path from theremote equipment by testing both the address of the interface and the address of the equipment.If the address of the port by which the Ping command is generated is different from the addressof the equipment, two commands are generated.

Choice "6" : Trace route.

"IP Address" : choice of IP address of equipment to be contacted.



The screen displays the management routes already defined with their characteristics :

Hops : hop 1, 2, 3…Path used to go from one machine to another.

IP address : IP address of destination equipment (equipment or sub-network).

Delay (ms) : round trip time.

Unit. size : Maximum size of IP packet which can reach the remote equipment.

1.4.4 - Using HTTP Web browser

1.4.4.1 - Web browser configuration

IE 5.0 configuration

NOTE : It is preferable not to have a cache with the IE 5.0; otherwise, you are never sure tohave updated data when the screen opens.

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 for1 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 theoptions to be acknowledged.

IE 5.5 and IE 6.0 configurations

The above configuration can be used.

However, the Automatic cache option with a disk space of 30 Mbytes provides a fasteroperation to display the pages.

With IE 6. 0, it is possible to configure the level of confidentiality, that is to say the choice of thecookies type that is allowed to copy on the target PC. To open the ADRs, it is necessary to letthe parameter of confidentiality of Internet to the default value "Medium" for the access to theWeb sites.

321



With IE6. 0 and a PC equipped of Windows XP SP2, the installed Center of Security modifiesthe manner of which IE displays the HTTP windows. In order to correctly open an ADR, it isnecessary 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 ADRsfor the Upload and the Download. On the warning window , to click on the button "Unblock" : thisaction adds the program tftpd32 in the list of exceptions.

Remark

After an upgrade of the application code, the cache must be cleared as following :

In the Internet Explorer "Tools" menu click "Internet Options / General tab / Temporary Internetfiles 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 bedefined. To list all environment variables, type "Set" in the MS DOS console.

To get a correct display of HTML pages, fonts must not be defined as "large" in displayproperties of the configuration panel.

1.4.4.2 - First commissioning

The PC is connected via Ethernet (the PC's gateway must be in the same subnetwork as theEthernet interface of the ADR).

Start the INTERNET EXPLORER 5.0, 5.5 or 6.0 application

On the Welcome screen, fill in the "Address" field with the IP address of the ADR155Cequipment.

If a screen with a 860 x 600 resolution is used, reduce character to obtain correct pagesdisplay (for example, 'synchronization' page must display 3' 'Apply' buttoms.

The Web browser welcome screen "Welcome to the ADR155C's site" appears.

On the first commissioning, the password is empty; click on Apply to access "Shelf View"screen.

From that moment, the Web browser is operational.



1.4.4.3 - Web browser Presentation

On session opening on the HTTP Web browser, the " Shelf View" screen represents theequipment global view, where each slot is marked with a letter, A, B, C, D, E, F or M formothercard, according to the following screen.

Figure 1-14 –"Shelf View" screen of Web browser

This screen is used to view the equipment status, in particular :

the protection of one STM-1 channel : in normal transmission, the protected card displaysthe indication "Traffic" and the protection card the indication "Prot (protected slot)" ; if thetraffic is switched on the protection card, the rescue card displays the indication "Work(protection slot)" and the protection card the indication "Traffic"

inconsistencies between configuration and composition : each slot includes the name of theexpected card and the name of the inserted card (in the middle, red colored if necessary)

each card presents a vertical border on left (an horizontal border on bottom for FAN andHoldover) which is colored grey if the card is not monitored, red in case of insertion alarm(Missing, Mismatch, Defective). For FAN, the coloration can also reflect the state of "BothFans Failed" and "One Fan Failed" alarms.



The connectors inside in-alarm modules are colored according to the severity of the mostserious alarm

present and configured out of service modules include an icon representing a red cross toindicate this administrative status

present and configured on maintenance modules include an icon representing a caution toindicate this administrative status

Absent modules configured out of service appear as all black panel.

the coloration of LEDs is dynamic. Their meaning is specified to § 2.5

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 islocked by another user, closed green if the writing session is locked the user.This information is automatically refreshed according to a defined frequency in the "Polling"menu.

activate the common functions of the equipment, (such as the synchronization, safety, trafficinformation, …etc.) by clicking on a function in the menu bar located above the equipmentview. This opens a sub-menu; see tree structure of the general menu Figure 1-15 – Menustructure.

access the functionalities related to a module in particular (for example, MSP protection inthe case of an Optical module) : click on the module to be selected, the selection arrow isblinking and its specific menu appears; see tree structure of "card" menus Figure 1-15 –Menu structure

view the own characteristics of a port (connections performed, configuration of connections,alarm states ...), by selecting the relevant connector.

For each function viewed, the configuration parameters, operating commands, activeparameters and alarm states are grouped together on the same screen, with the various actionspossible being accessible or not by the operator according to his/her clearance level.

The upper edge of the Web browser window recalls the equipment name, its IP address, theclearance level acquired and, if required, the slot concerned.



LOGIN

EQUIPMENT

NameDate and Time

Inventories(Hardware/Software)

SecurityManagement

Up and Download(Switching)

Failure Hold Off/On Time

SYNCHRONIZATION

SynchronizationSources

Synchronization T0Synchronization T4

CROSS-CONNECTION

ConfigureDelete

RenameMultiple connections

LAN WizardList

EVENT LOGS

Clear Event LogsRefresh

Open the frame ina new window

CURRENTALARMSRefresh

Open theframe in a

newwindow

"ERE" Menu "Motherboard" Menu

MaintenanceMonitoring

ServiceExpected CardPerformance :

VC12 Near (#1 to 21)VC12 Far (# 1 to 21)

Board Status2M Ports



VC12 Near / VC12 Far #VC3 Near / VC3 Far #VC4 Near / VC4 Far

MST Near / MST Far /RST Near

Board StatusEOW

EOW/AUXSTM's Functional Groups

Protection


Performance :VC12 Near (# 1 to 21)VC12 Far (# 1 to 21)

Board Status2M Ports

ETHLoopsPower

Shelf Overheat

"FAN Menu"FAN" M

"E3DS3" Menu

"LAN1" MenuMonitoring

Expected CardConfigurationBoard Status



VC3 Near / VC3 Far #Board Status

34M/45M Ports

MonitoringService

Expected CardPerformance :

VC3 Near / VC3 Far #Board Status

LAN

"Optical STM-4" Menu



VC12 Near / VC12 Far #VC3 Near / VC3 Far #VC4 Near / VC4 Far # MST Near / MST Far /

RST NearBoard Status

EOWAUX

STM4's FunctionalGroups

AU-4 Selection

SESSION

LoginLogout

Information

"EMPTY" Menu

Expected card

"GFP150" Menu

"21E1R8" Menu



VC12 Near (#1 to 21)VC12 Far (# 1 to 21)

Board StatusRetiming2M Ports

"21E120" Menuor "21E75" Menu

" Optical STM-1" Menu



VC12 Near / VC12 Far #VC3 Near / VC3 Far #VC4 Near / VC4 Far

MST Near / MST Far /RST Near

Board StatusEOW/AUX

STM's Functional GroupsProtection

HELP

"HOLDOVER" Menu

Board Status

MonitoringService


VC12 Near / VC12 Far #VC3 Near / VC3 Far #

Board statusGFP150's Functional

Groups- Global Params

- ETH- Switch- VCG- XCN

- HPA / LPT- OAM CC

- MSTP

"4E/FE" Menu

MonitoringService


VC12 Near / VC12 Far #VC3 Near / VC3 Far #

Board status4E/FE's Functional

Groups- ETH- VCG- XCN

- HPA/LPT

POLLING

Figure 1-15 – Menu structure

2 - OPERATION


2. OPERATION

2.1 - Functional description

The ADR155C is an optical STM-1/STM-4 add-drop multiplexer used to build STM-1/STM-4point-to-point links, STM-1 rings, or mesh networks, so achieving the conveyance of PDH linksat 2 Mbit/s, 34 or 45 Mbit/s, of SDH STM-1 links, of Ethernet links.

The ADR155C can also be connected to an equipment of the synchronous digital hierarchy inaccordance with UIT-T recommendations G.707 and G.783.

The ADR155C modelling in functional blocks is presented below :

SPI : SDH Physical Interface

RST : Regeneration Section Termination OHA : OverHead Access

MST : Multiplex Section Termination

MSP : Multiplex Section Protection

MSA : Multiplex Section Adaptation

SETS : Synchronous EquipmentTiming Source

HPOM : Higher order Path Overhead Monitor

HPC : Higher order Path Connection

SETPI : Synchronous EquipmentTiming Physical Interface

HPT : Higher order Path Termination

HPA : Higher order Path Adaptation

LUG : Lower order path Unequipped Generator

SEMF : Synchronous EquipmentManagement Function

LPOM : Lower order Path Overhead Monitor MCF : MessageCommunication Function

LPC : Lower order Path Connection

LPT : Lower order Path Termination GFP-Frame

LPA Lower order Path Adaptation (VC12)

Lower order Path Adaptation (VC3)

VCAT

PPI : plesiochronous physicalInterface (VC12)

plesiochronous physicalInterface (VC3)

LCAS

Table 2-1 - Functional Blocks of ADR155C

2.2 - Generalities

The ADR155C operation and maintenance are carried out :- either directly on the equipment, through the front panel indicator lights and two engineering

management loops (loops A and B),- or from a PC fitted with Web browser,- or from a network manager, using the SNMP protocol for the network and supervision

aspects, and the included Web browser

2 - OPERATION


The IONOS-NMS management software provides an efficient and comprehensive networkadministration solution for SAGEM systems ADR 155C, ADR 2500C and ADR2500 eXtra (referto 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, SNC-P.

2.3 - Operational parameters

The operational parameters include :

the configuration parameters,

the maintenance commands or operations (these actions are cleared in case of power supplyloss)

the alarms and their severity.

Configuration constraints

When configuring the name (Equipment > Name menu), you are limited to using upper andlower case characters, numbers, the space and the – and _ characters.

Accented characters and certain special characters will not be displayed on the VT100 interface.

Configuration parameters

NOTE :

1) The functional blocks naming, configuration parameters and their default value, noted"XXXXXX", are displayed on Web browser.

2) The default values are indicated when a connection is created.

2 - OPERATION


Configuration parameters per functional blocks Default value


"ALS enable" ("Maintenance" menu on optical cards)

The Automatic Laser Shutdown function can be disabled(equipment global functionality)"ALS" (Automatic Laser Shutdown)

"enable"

RST STM4 : Multiplex Section Regeneration“EBER-B1” (10-4) monitoring ; configurable in "Monitoring" or "NoMonitoring"No consequent actions

" Monitoring"

Path trace received, expected and sent

- "Trace Received" (16 octets) – no configurable

- "Trace Expected" (16 octets)

- "Trace sent" (16 octets)

"UNNAMED RS"+ CRC7

"UNNAMED RS" + CRC7

ou AUTO (*)+ CRC7

"TIMdis" (Trace Identifier Mismatch) enable or disable clicked (no TIM)

"Autodiscovery" enable or disable

Enable : allows to generate automatically the Trace Sent in order to enablean autodiscovery of equipment and networking by a network management

clicked

RST STM1 : Multiplex Section Regeneration“EBER-B1” (10-4) monitoring ; configurable in "Monitoring" or "NoMonitoring"No consequent actions

" Monitoring"

Path trace transmitted (no configurable)

- "Trace sent" (1 octet) 01HMST : Multiplex Section Termination“EBER-B2” (10-3) monitoring ; configurable in "Monitoring" or "NoMonitoring"If EBER-B2 is not monitoring, AIS, SF and MS-RDI consequent actions areinhibited

" Monitoring"

"SD-B2 threshold"SD-B2 threshold : configurable from 10-5 to 10-9

No consequent actions"10-6"

"REI threshold"REI threshold : configurable from 10-4 to 10-9


Table 2-2 – Configuration parameters

(*) AUTO = XXXXXXXX_**Y:01XXXXXXXX corresponds to the IP management address converted in hexadecimalY corresponds to the slot in which the card is inserted

2 - OPERATION



SOH : Section OverHead

Configuration of SOH bytes which are not used in standard or for EOWorderwire conveying.

This function is not available on optical cards.

Configurable bytes on ERE card :Line 1, byte of column 7Line 1, byte of column 8Line 1, byte of column 9Line 2, bytes of columns 8, 9Line 9, bytes of columns 8, 9

"01H""02H""03H""00H""00H"

MSP : Multiplex Section Protection (This function is not available on STM-4 card).

Link type : "1+0" or "1+1" "1+0"

"Card's MSP type"

Choice between « Working » and « Protection » for the selected port

"Card’s MSP Complément"

Definition of the complementary port of the MSP couple"Revertive"

Revertive authorization : return after a WTR time-delay to the working link when the fault (SF or SD) causing the switch has disappeared.

"No"

"Mode "Protection mode : bi-directional / unidirectional "Bidir."

"WTR"Wait Time to Restore (WTR) period : in revertive mode, period followingrestoration of nominal operation ; configurable from 30 to 15mn in one-second steps

"60 s"

"Hold-off time"SF and SD fault persistence : configurable from 0 to 10s in 100ms steps "0 ms"

"Sf/Sd priority"SF/SD priority according to Recommendation G.783 [1994] annex A.1.2.1possible value :"high" or "low" (compatibility with MXA)

"Low"


2 - OPERATION



HPOM : High order Path Overhead MonitorHPT : High order Path Termination“EBER-B3” (10-4) monitoring ; configurable in "Monitoring" or "NoMonitoring"No consequent actions

" Monitoring"

"SD threshold"SD threshold (VC4) : configurable from 10-5 to 10-9




Signal label sent, expected and received (byte C2 of VC4 path overhead) ;"Label" (when VC12 or VC3 connection is created) :

- "Sent", possible values : "01H" (unspecified equipment) or "02H" (TUG structured)- "Expected", possible values : "01H" (unspecified equipment) or "02H" (TUG structured)- "Received". (displayed - hexadecimal value, if unknown)

Tug Structured(02H)

Tug Structured(02H)

Path Trace VC4 - byte J1 (when VC12 or VC3 connection is created)

Mode : 1 byte (Trace = 0 to 255) or 16 bytes (Trace = 15 ASCIIcharacters)

16 bytes

- "Trace Sent" (configurable)

- "Trace Expected" (configurable)

- "Trace Received" (displayed in the same mode as 'Expected')

"UNNAMED VC4" +CRC7

"UNNAMED VC4" +CRC7

"TIMdis" TIM (Trace Identifier Mismatch) enable or disable clicked (no TIM)

LUG : Lower order path Unequipped GeneratorNumber of the unequipped VC12s transmitted in TUG3s(by default no connection)

"FFH"


2 - OPERATION



LPOM : Lower order Path Overhead Monitor“EBER-B3” (10-3) (VC3) or “EBER-V5” (10-3) (VC12) monitoring ;configurable in "Monitoring" or "No Monitoring"No consequent actions

" Monitoring"

"SD threshold"SD threshold : configurable from 10-5 to 10-9

No consequent actions "10-6"



"Label Rec"

Signal label received - Displayed value non configurable

Path trace expected, received for VC3 (J1 Byte) or VC12 (J2 Byte)



"UNNAMED VC" + CRC7


LPC : Lower order Path ConnectionHPC : High order Path ConnectionConnection Switch – "Cross-Connection > Configure or Multipleconnections" Menu (after selected input port)

Not put intoservice

"Name"Identifications of connections (configurable according to M.1400 §13) No name

"Input Port" or "First Input Port"The dropdown list depends on the declared boards in the rack.

"Output Ports" (> Multiple connexions)Choice of the last output port to connect"VC-n type", unidirectional or bidirectional typeConnections of VC3, VC12, VC4


2 - OPERATION



LPC : Lower order Path Connection (Continue)HPC : High order Path ConnectionSNC connections protection VC12 / VC3 / VC4– Protection (> Configure)

"Status" : traffic status.Protection status display (channel used, cause of switchover)

"Revertive" :Revertive authorization (path by path) : return after a WTR time-delay tothe working link when the fault (SF or SD) causing the switch hasdisappeared.

"No"

"WTR"Wait Time to Restore (WTR) period (common to all paths) : in revertivemode, period following restoration of nominal operation ; configurablefrom 30 to 900 in one-second steps

"60 s"

"Hold Off Time"SF and SD fault persistence (path by path) : configurable from 0 to 10s in100ms steps.

"0 ms"

"SNC Type"SNC/I or SNC/N (only the SD_B3 or SD_V5 criteria is taken in account)

SNC/I

"Protection Input Port" Definition of the assistance portThe dropdown list depends on the declared boards in the rack

No protection

LPT : Lower order Path TerminationPlesiochronous access

"EBER-B3" (10-3) (VC3) or "EBER-V5" (10-3) (VC12) monitoring ;configurable in "Monitoring" or "No Monitoring"No consequent actions

" Monitoring"


No consequent actions "10-6"



Signal label (VC3) transmitted, expected and received (C2 Byte); "Label" :- "Sent", "01H" (unspecified equipment) or "04H" (async 34/45M)- "Expected", "01H" (unspecified equipment) or "04H" (async 34/45M)- "Received". (hexadecimal value)

"Async 34M/45M""Async 34M/45M"

Signal label (VC12) transmitted, expected and received (V5 Byte) "Label" :- "Sent",: "000b" no connection or "010b" (asynch Float) if connection (not configurable by the operator)- "Expected", possible value : "001b" (unspecified equipment) or "010b" (asynch Float)- "Received" (received value displayed)

"Async Float"


2 - OPERATION



LPT : Lower order Path Termination (Continue)Plesiochronous access

Path trace expected, received and transmitted for VC3 (J1 Byte) or VC12(J2 Byte)



- "Trace sent" (16 bytes)

"UNNAMED VC"+ CRC7

"UNNAMED VC" + CRC7


LAN1 CardEthernet port configuration (exclusive choice)

"LAN Interface"Choice of the "Automatic" (with autonegotiation) or "Manual" LAN interface :10 Mbps/Half Duplex, 10 Mbps/Full Duplex, 100 Mbps/Half Duplex, 100 Mbps/Full Duplex.In "Automatic" the capabilities represent the local capacities of theequipement that are negotiated with the remote equipment. The result ofthis autonegotiation is visualisable in the Status " field ".In "Manual" no autonegotiation, the "Status" field reflects the operatorconfiguration.In order to have a correct link, it is recommended to configure both localand remote equipment Ethernet interfaces with the same configuration :- "Automatic" on both side or- "Manual" and same duplex/speed configuration on both sideNote : in "Automatic" mode, if the remote equipment is set to "Manual",local interface automatically switches to half duplex.

100Mbps FullDuplex

Flow control (multi point mode only)- LAN towards VC3_# i- VC3_# i towardsVC3_# j or LAN

60 %60 %

Interface configuration- LAN in service / no service- Maximum route Age- LAN interconnection mode (point to point over 2VC3/multipoint)-

Service300 s

multi-point

Signal label (VC3# i) transmitted, expected and received; "Label" :- "Sent" not configurable- "Expected" not configurable- "Received" not configurable

"A8H""A8H"

"SD threshold"SD threshold : configurable from 10-5 to 10-9 for VC3 "10-6"

Path trace J1 transmitted :

Nota : Received Path trace not treated in reception

"UNNAMED VC" + CRC7


2 - OPERATION



GFP150 and 4E/FE CardsFor configuration of these cards, respectively refer to the chapters 6 and7 of the present user guide

Card menu GFP150 > GFP's Functional Groups > ETH > InterfaceSettingsCard menu 4E/FE > 4E/FE's Functional Groups > ETH > InterfaceSettings

"Physical Interface"Choice of the "Automatic" (with autonegotiation) or "Manual" physicalinterface : 10/100 Mbps, Half/Full Duplex, Pause/No PauseIn "Automatic" the capabilities represent the local capacities of theequipement that are negotiated with the remote equipment. The result ofthis autonegotiation is visualisable in the Status " field ".In "Manual" no autonegotiation, the "Status" field reflects the operatorconfiguration.In order to have a correct link, it is recommended to configure both localand remote equipment Ethernet interfaces with the same configuration :- "Automatic" on both side or- "Manual" and same duplex/speed configuration on both sideNote : in "Automatic" mode, if the remote equipment is set to "Manual",local interface automatically switches to half duplex.

100 Mbps FullNo pause

"Connecting Interface"

- GFP150 : Adaptation according to the used cable : "Crossed", "Direct" or"Automatic"

- 4E/FE : Automatic

Automatic

"Link Down Retransmit"

In point to point mode (one ETH + one VCG), "Enable" allows to report oneETH Down (or one VCG Down) on the remote ETH link.

Disable

Card menu GFP150 > GFP's Functional Groups > HPA/LPTCard menu 4E/FE > 4E/FE's Functional Groups > HPA/LPT

"EBER-B3" (10-3) (VC3) or "EBER-V5" (10-3) (VC12) monitoring ;configurable in "Monitoring" or "No Monitoring"No consequent actions

" Monitoring"


No consequent actions

"10-6"



Signal label(VC3# i) sent, expected and received; "GFP mapping" :- "Sent" not configurable- "Expected" not configurable- "Received" not configurable

"1BH (GFP)""1BH (GFP)"


2 - OPERATION



GFP150 and 4E/FE Cards (Continue)Signal label (VC12# i) sent, expected and received « extended signallabel» / « GFP mapping» (octets V5 et K4) :

- "Sent" not configurable- "Expected" not configurable- "Received" not configurable

"101b (V5) /1101b (K4) "

Path trace expected, received and transmitted for VC3 (J1 Byte) or VC12(J2 Byte)



- "Trace sent" (16 bytes)

"UNNAMED VC"+ CRC7

"UNNAMED VC" + CRC7


SETS : Synchronous Equipment Timing SourceSynchronization Sources

Synchronization T0

"Name"

Choice of 2 Mbit/s port number for T2 source(1 port per enabled 2 Mbit/s card)

"1"

"SSM"Use of synchronization status messages (SSM) "True"

"Quality Provided" (when "SSM" is "False")

Quality level of synchronization sources :- "PRC" (Primary Reference Clock),- "SSUT" (Synchronization Supply Unit Transit),- "SSUL" (Synchronization Supply Unit Local),- "SEC" (Synchronization Equipment Clock),- "DNU" (Do Not Use).

T3 : PRCT1 : DNU

T2 : SEC

"T0 Priority"

T0 priority Table, according to enabled sources ;possible values : P1 to P7 (P1 have the most priority)

"P1" for T3_1"Dis" for T3_2

and T2_M

"P2" for others"LOS Severity"Alarm severity associated to the source status .

Minor for T3Warning for T1

and T2"Mode"Synchronization operating mode

Choice between "Automatic" and "Free-run" "Automatic"


2 - OPERATION



SETS : Synchronous Equipment Timing Source (Continue)Synchronization Sources

Synchronization T0"Command"Operator actions : manual synchronization, forced synchronization or clearChoice of the active source

clear

"Revert"Revertive authorization (common to all sources) : return after a WTRtime-delay to the working link when the fault (SF or SD) causing theswitch has disappeared.

"True"

"WTR"Wait Time to Restore (WTR) period : in revertive mode, period followingrestoration of nominal operation ; configurable from 0 to 30mn by one-second step

"60 s"

"Sync Freq Out of Range Severity" Alarm severity associated to the T0 output frequency Warning

Synchronization T4

"Active source"Selected source for T4 "T0"

"Minimum Quality"

Quality level for T4- "PRC" (Primary Reference Clock),- "SSUT" (Synchronisation Supply Unit Transit),- "SSUL" (Synchronisation Supply Unit Local),- "SEC" (Synchronisation Equipment Clock),

"PRC"

"Sase"

SASE mode control (enable or disable) False

T3 source selection for SASE mode (T3-1 or T3-2) T3-1"LOS T4 Severity"Alarm severity associated to the T4 output status. Minor


2 - OPERATION



OHA : OverHead Access" STM-n card > AUX" menu

AUX interface operating mode (F1);Codirectional or Contradirectional MasterOnly contra-directional mode is available on cards STM-4.

Contradirectional

" STM-n card > EOW" menuEOW interface operating mode :Codirectional or Contradirectional MasterOnly contra-directional mode is available on STM-4 cards

Contradirectional

Selection of byte used to convey order wire channel EOW in the SOH,E1E2Line 7, bytes of columns 8, 9 (only on ERE cards)Line 8, bytes of columns 8, 9 (only on ERE cards)Line 9, bytes of columns 8, 9 (only on ERE cards)

E1

" STM-n card > EOW/AUX" menuInterface operating mode :Codirectional or Contradirectional Master ContradirectionalSelection of byte used to convey :

E1, E2 ou F1 F1E3DS3 Card"E3 (34M)" or "DS3 (45M)"

34 or 45 Mbit/s physical interface selection "E3 (34M)"Connecting cable length selection so that transmitted pulse complies totemplate defined in Bellcore GR-489-CORE standard : "Type of cable" (DS3/45Mbit/s mode only

"long" or "short" (length < 225 ft or 70m)"short"

21E1R8 CardRetimingSelection of the Retiming function for the #1 to #8 ports Disable FAN cardOperation mode selection of the FAN module which allows to control theshelf temperature according to the room temperature

"Permanent cooling" :Fan is ON, if Tamb°> 5°C (41°F)Fan is OFF, if Tamb° ≤ 0°C (32°F)

Note : the "Permanent cooling" mode is the default mode when aGFP150 module is in service. This configuration must not be changed.

"Overheat Avoidance" :Fan is ON, if Tamb°> 35°C (95°F)Fan is OFF, if Tamb° ≤ 30°C (86°F)

"OverheatAvoidance"


2 - OPERATION



EquipmentSession – "Session" menu"Login"Login session. Requests for user class.Restriction : only one write login for write at a time"Logout"Exits session subsequent to operator command or time-out"Information"Informations on current session"Equipment > Name" menuConfiguration of equipment name

Empty

“Equipment > Date and Time” menuEquipment date and timePC date and time

DD/MM/YYYYhh:mn:ss

Passwords - "Equipment > Security" menu

Selection of user class level :SupervisorOperatorObserver

Admin

"New Password"One password by user classOnly the administrator may modify password

No password

Authorized managers - "Equipment > Management" menu"Traps Managers Dest"Dest IP"Destination IP address"Community"Authorization for transmission of traps to management : managers list "

0.0.0.0

"Managers List" (10 possible addresses)"N° IP"

IP address entry (10 possible addresses) according to user class.

Choice of a user class by increasing order of rights :- "Observer"- "Operator"- "Supervisor"The class is granted according to the password ; it is displayed.Address of managers and authorized levels.Each manager is associated to a maximum user level.

Ex. : the Supervisor’s password gives access to the Operator class if themaximum level associated to the IP address is Operator.

0.0.0.0

supervisor

Backup and downloadEquipment > Upload/Download/Switching MenuUpload > Database (type of uploaded informations)Backup of shelf configuration (cards, alarms, performances, connections,protection, synchronization)


2 - OPERATION



Equipment (Continue)Upload > Network (type of uploaded informations)Backup of management network parameters (PPP, IP address, routingProtocols)Upload > TFTP ServerPC address configuration on which the equipment is displayed

Upload > Save in FileFile name in which the informations are saved xxxxxxxx.yyy

Download > Database (type of downloaded informations)Restoration of shelf configuration (cards, alarms, performances,connections, protection, synchronization)Download > Network (type of downloaded informations)Restoration of management network parameters (PPP, IP address, routingprotocols)Download > FPGA (type of downloaded informations)Download of whole FPGA codes of all the configurable cards in theequipment..Download > LAN Code (type of downloaded informations)Download application software of LAN1 cardCode n-1 is saved in Flash memory. Switchover to downloaded new codetakes place following a manual operator command.Download > GFP150 Code (type of downloaded informations)Download application software of GFP150 cardCode n-1 is saved in Flash memory. Switchover to downloaded new codetakes place following a manual operator command.Download > Motherboard Code (type of downloaded informations)Download application software of MotherboardCode n-1 is saved in Flash memory. Switchover to downloaded new codetakes place following a manual operator command.It is not possible to do a Download on a code < P5Download > TFTP ServerPC address configuration on which the equipment is displayed

Download > FileFile name from which the informations are loaded xxxxxxxx.yyy

Switching > FPGA (Take effect)Apply default configuration of FPGA codesSwitching > LAN Code (Switch)Switchover of code in flash without application on the LAN1 cardSwitching > GFP150 Code (Switch)Switchover of code in flash without application on the GFP150cardSwitching > LAN Code (Switch and reset)Switchover of code in flash and application on the LAN1 cardSwitching > GFP150 Code (Switch and reset)Switchover of code in flash and application on the GFP150cardSwitching > Motherboard Code (Switch and reset)Switchover of code in flash and application by a Motherboard resetIt is not possible to do a Switching on a code < P5


2 - OPERATION



Equipment (Continue)Card > "Expected card" menu

Configuration of A, B, C, D, F slots. A slot can be configured empty orwith an expected card

Emptyif absent cardInserted card

if present

Card > "Monitoring" menu

Monitoring of cardsA no-monitored card is indicated in the equipment view (greyed frontpanel) ; not monitoring a card inhibits the entire management of thefaults related to this card (card and port)

Monitoring

Subrack Monitoring (Motherboard) Monitoring

Monitoring of portsNot monitoring a port inhibits the entire management of the faults andperformance related to this port

No Monitoringfor LPOM blocks

Monitoringfor others andaccording to

custom

Card > "Service" menu

Putting a card into/out of service(The card is ignored by the management function)

Into Service,if present card

Out of service,if absent card

Alarms

Alarms severityThe severity of each alarm is configurable individually with the followingattributes :

"Critical""Major""Minor""Warning""Critical-inv""Major-inv""Minor-inv" "Warning-inv".

Alarms Persistence configuration

"Equipment > Failure Hold Off/On Time" menuPersistence for the raising : X = 0, 1, 3, 10 or 30sPersistence for the clearing : Y = 0, 1, 3, 10 or 30s

X = 3sY = 3s

DCC Transparency –"Motherboard > ETH > DCC Connection" Menu"DCC Type" : Choice between "D1-D3" and "D4-D12"

Max 4 transparencies No connection

ETH Interface–"Motherboard > ETH > ETH Interface Settings" Menu

"Connecting Interface" : Adaptation according to the used cable :"Direct" or "Automatic"

Automatic


2 - OPERATION



Equipment (Continue)Loops – "Motherboard > Loops" menu

Local Input

Used to configure severity and name of 4 incoming loops

User Input x(x = 1 to 4)

Local Output

Central site (remote indications gathering) No ClickedProceed status from/to (A, B, C or D)

Two remote indication inputs are transmitted by bits 1 to 4 of S1 byte ofSTM-n cards if "enable" configuration

Enable

Routing –"Motherboard > ETH > IP Parameters" Menu

> Global Parameters

Equipment : IP address of equipment management

RIP : routing domain

OSPF : routing area

> Static Routes

Configuration tables of Static routes

Possibility to add or delete routes

Not configured

> Interfaces Configuration

Selecting and putting Ethernet port into serviceEnabled / Disabled (port by port)

On

Selecting and putting PPP1, PPP2, PPP3 or PPP4 ports into service

Enabled / Disabled (port by port)

Type

Off

Numbered

Port addressing (port by port) :

EthernetInterface IP addressSubnet mask

PPP InterfaceInterface IP addressSubnetwork maskDestination IP address (PPP interface only)

135.10.110.010255.255.0.0

0.0.0.00.0.0.00.0.0.0

Management paths (port by port – PPP only) either :DCCr (A, B, C or D)DCCm (A, B, C or D)P#1, P#2

None

Selection of the routing protocol port by port (RIP, OSPF, none) None


2 - OPERATION


Maintenance operation commands

Monitoring commands according to the functional blocks

SPI : SDH Physical Interface Optical cards "Maintenance" menu

"ALS enable" clicked by defaultALS enabled/disabled (equipment global functionality)"Restart STMn Slot X""None" : activated by default"2 sec" : 2s laser restart on operator action"90 sec" : 90s laser restart on operator action

Cards "Maintenance > Loopback" menu"No loopback" : activated by default"Line" : Transparent line loop-back, activated/deactivated"Equipment" : Transparent equipment loop-back, activated/deactivated

MSP : Multiplex Section Protection (This function is not available on STM-4 boards)"Protection > Operation" Menu of STM-1 cardsOperator command for MSP protection

Clear (Automatic mode) activated by defaultLockout of ProtectionForced Switch to WorkingForced Switch to ProtectionManual Switch to WorkingManual Switch to Protection

LPC : Lower order Path ConnectionHPC : High order Path Connection"Cross Connection > Configure > Command" menuOperator command for SNC protection of VC12 / VC3 / VC4 path (per path and in order ofpriority) :

Clear (Automatic mode) activated by defaultManual WorkingManual ProtectionForced WorkingForced ProtectionLockout (lockout of Protection)Swap SNC : swap the working and protection input ports

PPI : PDH Physical InterfaceCards "Maintenance > Loopback" menu

"No loopback" : activated by default"Line" : Transparent line loop-back, activated/deactivated"Equipment" : Transparent equipment loop-back, activated/deactivated

Table 2-16 - Commands

2 - OPERATION


Monitoring commands according to the functional blocks

LAN1 CardLAN statistics (display and reset)VC3 # i statistics (display and reset)Flow control (display and reset)Interface status-(separate graphical SDH and WAN status display)

GFP150 CardLAN #i statistics (display and reset)EoS #i statistic (display and reset)SLA statistic (display and reset)Interface status (LAN and WAN)VC3#i and VC12#i SDH statistics (display and reset)

4E/FE CardEthernet statistics of ETH #i interfaces (display and reset)Ethernet and GFP statistics of VCG #i interfaces (display and reset)Interface status (ETH and VCG)SDH VC3#i and VC12#i statistics (display and reset)

SETS : Synchronous Equipment Timing Source"Synchronization > Synchronization T0 > Command" MenuSynchronization operator command

Clear (Automatic mode) activated by defaultManual (manual synchronization)Forced (forced synchronization on new source)

EquipmentAlarms

Alarm acknowledgements using the front panel push-button(such acknowledgements only act on major and minor output loops ; LED indications remainas long as alarm cause).

Quality"Event Logs" menuAlarms and events logs display> Clear Event LogsAlarms and events logs reset

LAN1RESET of traffic counters of LAN functions ports (port by port) or of indicators of ADR frameswitching function

GFP150RESET of traffic counters of GFP150 function ports (per interface) or of indicators of GFPframe switching function

4E/FERESET of traffic counters of ports per interface

Reset ("Motherboard > ETH > Restart" Menu)Hot reset of the equipment, performed by software(the reset time should be shorter than 30s)

Table 2-17 - Commands

2 - OPERATION


2.4 - Predefined functions

On commissioning, the following mechanisms are implemented automatically :

synchronization,

management of outgoing remote indication loops.

Synchronization

Synchronization of the local and remote equipment is managed in accordance with the availablesynchronization sources, their quality and the priority assigned to each.

The possible synchronization sources include :

standalone operation (holdover* or local oscillator mode),

T1 extracted from one of the incoming STM-n streams (1 to 4 possibilities according to thenumber of Optical cards present in the equipment),

T2 : one 2 Mbit/s G.703 source per declared 2 Mbit/s module, and selected from the various2 Mbit/s G.703 accesses

T3_1 and T3_2 : two external 2 MHz G.703 sources

* 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.

Holdover mode is available when an holdover card is inserted in extension slot. If there is nocard or if it is defective then standalone operation is assume only by local oscillator

NOTE : On creation of an MSP protection, the « Protection » link inherits the configurations ofthe « Working » link and therefore, in particular,those of synchronization.

The Synchronization screen summarizes the status of the timing obtained from thetraffic link under the « Working » interface reference.

The following figures give typical synchronization examples according to equipment connections.

2 - OPERATION


SSM = PRC

ADR155C 1

SSM = PRC

T1-C = T0 = T3 (ADR155C1)T1-C = T0 = T3

ADR155C 2

T0 = T1-C

ADR155C 3

T0 = T1-c

2 MHz externalsync input (T3):- Quality = PRC,- Priority = 1.

STM-n port (T1-C):- Quality = DNU- Priority = 2.

2 MHz clock outputT4= T0 = T3 (ADR155C1)

Internalsynchronization

T0 = T3


2 MHz clock outputT4= T1-N

Synchronizationof other equipments


Figure 2-1 - Synchronization from the 2 MHz external sync input (T3)

SSM = SEC

ADR155C 1

SSM = SEC

T1-C = T0 = T2

ADR155C 2

ADR155C 3

T0 = T1-c

2 Mbit/s port (T2):- Quality = PRC,- Priority = 1.


2 MHz clock outputT4= T0 = T1c West

Internalsynchronization

T0 = T2


2 MHz clock outputT4= T1-N



or T2 (ADR155C1)

T1-C = T0 - T1-c (West)T0 = T1-C West

NOTE : Synchronization is applied to the 2 Mbit/s port of the ADR155C which is enabled first(local ADR155C in the example).

Figure 2-2 - Synchronization from a 2 Mbit/s port

2 - OPERATION


Loops Management

On remote sites, two local outgoing loops (Local user outputs A and B) are activated on theappearance of a local equipment alarm or remote indication loops 3 and 4 (Local user input #3or #4).

The remote loopback function allows an equipment named "central site", to register faultspresent on remote sites.

This function requires each site to transmit to the central site an alarm presence message. Thismessages which corresponds to remote monitoring loopback 1 or 2 (Local user input #1 or #2)is transmitted in the S1 byte. To link this message to equipment's alarms, the outputs of the Aand B loops (Local user outputs A and B) should be connected to remote monitoring loops 1 and2 (Local user input #1 or #2) respectively.

Data chaining in a bus or ring type network architecture is provided by "OR" function validationbetween the data received (Far user inputs #1 et #2) via S1 STM-n West and S1 STM-n East,and local data, for each site in the network.

At the "central site" equipment, "OR" function validation between the data received (Far userinputs #1 and #2) via S1 STM-n West and S1 STM-n East, and local data (Local user input #1 or#2 and local alarm), enables local alarm loopbacks to be activated (Local user outputs A and B).

To configure the remote loopback function, the following parameters should be programmed :"Line remote loopback" and " central site". The Figure 2-3 gives an example of remotemanagement of the local outgoing loops according to the equipment connections.

Figure 2-3 – Remote loopback function (registering alarms on central site)

NOTE 1 : When Local User #1 and #2 gather major / critical and minor alarm informations (localuser outputs A and B) it is necessary to give them a "warning" severity in order to avoidpermanently activation.

NOTE 2 :Status of incoming loops (Local user inputs #1 to #4), far incoming loops (Far userinputs #1 to #2) and outgoing loops (Local user outputs A and B) may be displayed onWeb browser.

#1

#2

#3

#4

A BA B

#1

#2

#3

#4

A B

ADR 155C 2

ADR 155C 3

#1

#2

#3

#4

Localuser inputs

Localuser inputs

Localuser inputs

S1 = received S1* + state oflocal user inputs #1 and #2

Activation ofLocal user

inputs #1 or #2

Local user outputs

Local user outputs

EASTEASTWEST WEST

EAST WEST


Local user outputs

Received West S1

Activation of localuser inputs #1 or #2

folowing activation of local user

outputs A or B( équipment

alarmsor local user

inputs #3 rt #4)

Activation of localuser inputs #1 or #2

folowing activation of local user

outputs A or B( équipment

alarmsor local user

inputs #3 rt #4)


S1 received fromSTMn tributary

Received S1* : gathering ofS1 received from authorisedSTM1 interfaces exceptfrom transmiting interface

2 - OPERATION


2.5 - Alarms processing

Indicator lights and pushbuttons

The following tables give the meanings of the lit LEDs and the actions initiated by using thepushbuttons.

Spécific indicator lights of Motherboard :

Monitoredcomponent

Name Remark Status Meaning

Ethernet Without Green Off Incorrect link and Link Down(management access) Flashing Current activity and Link Up

On Correct link and Link Up butno activity

Motherboard "ON" Green On In service cardFlashing Self-test default

Off Not powered equipment or notrun software

Equipment "ALA M" Red On Major / critical alarm"ALA m" Yellow On Minor alarm

Table 2-18 - Spécific indicator lights of Motherboard

Spécific indicator lights of LAN1 card :

Monitoredcomponent


Ethernet Without Green On Correct LinkOff No link

Without Yellow On Transmission in progressOff No traffic

Interface ETH bite rate10/100 Yellow On 100 Mbit/s

Off 10 Mbit/sInterface ETH type

HALF/FULL Yellow On Full duplexOff Half duplex

Table 2-19 - Spécific indicator lights of LAN1 card

Spécific indicator lights of GFP150 card :

Monitoredcomponent


Ethernet #1 to #8 Without Green On Correct LinkOff No link

Without Yellow On Transmission in progressOff No traffic

Table 2-20 - Spécific indicator lights of GFP150 card

2 - OPERATION


Spécific indicator lights of 4E/FE card :

Monitoredcomponent


Ethernet #1 to #4 Without Left On Correct linkGreen Off No link

Without Right Flashing Traffic on progressYellow Off No traffic

Table 2-21 - Spécific indicator lights of 4E/FE card

"STATUS" indicator light on all cards except the Motherboard and the FAN :

Green LED Red LED MeaningOn Off Card in serviceOn On Card in service and in alarmOff Off Hardware default on card (fuse)Off On Card out of service

Flashing Self-test default

Table 2-22 - "STATUS" indicator light

Spécific indicator lights of E3DS3 card :

Monitoredcomponent


Card "DS3/E3""45/34"

Green On 34 Mbit/s mode activated

Off 45 Mbit/s mode activated

Table 2-23 - Spécific indicator lights of E3DS3 card

Pushbuttons :

Designation Location Role Action initiated"ACK" Motherboard Alarm

acknowledgePressing disables the outgoing alarmloops. The visual alarm is kept.

"INITCONFIG"(*)

Motherboard Configurationreload

"Factory" Configuration reload

Table 2-24 - Pushbuttons

(*) To activate "INIT", keep button pressed for at least 5 seconds. This button isinaccessible (and unused) in normal operation. It is necessary to remove the cover toaccess it.

2 - OPERATION


Defaults 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"connector of the mothercard.An alarm of gravity "minor" activates the minor outgoing loops of the "POWER" connector of themothercard.An alarm of gravity "warning" does not activate any outgoing loop (available on HTTP).

Alarms Description Severity


SPI-LOS Loss Of Signal majorSPI-TF Transmit Fail major

RST : Regenerator Section Termination

RST-LOF Loss Of Frame majorRST-EBER-B1 Bit Error Rate > 10-4 on B1 Byte majorRST-TIM Regenerator Section –Trace Identifier Mismatch minor

MST : Multiplex Section Termination

MST-AIS Alarm Indication Signal warningMST-EBER-B2 Bit Error Rate > 10-3 on B2 Byte majorMST-SD-B2 Signal Degrade –B2 minorMST-REI Remote Error Indication warningMST-RDI Remote Defect Indication warning

MSP : Multiplex Section Protection

PAM Protection Architecture Mismatch minorSCM Selector Control Mismatch minorOTM Operation Type Mismatch minor

MSA : Multiplex Section Adaptation

AU-AIS Administrative Unit – Alarm Indication Signal warningAU-LOP Administrative Unit – Loss Of Pointer major

HPOM : Higher order Path Overhead Monitor

HO-EBER-B3 Bit Error Rate > 10-4 on B3 Byte majorHO-SD (VC4) High Order Path –Signal Degrade warningHO-REI Remote Error Indication warningHO-RDI/G1 High Order Path – Remote Defect Indication warningHO-UNEQ High order Path – Unequipped warningHO-TIM High Order Path –Trace Identifier Mismatch warning

Table 2-25 - Alarms and severity

2 - OPERATION



HPT : Higher order Path Termination

HO-EBER-B3 Bit Error Rate > 10-4 on B3 Byte majorHO-SD (VC4) High Order Path –Signal Degrade warningHO-REI Remote Error Indication warningHO-RDI/G1 High Order Path –Remote Defect Indication warningHO-UNEQ High order Path – Unequipped warningHO-TIM High Order Path –Trace Identifier Mismatch warningHO-PLM High Order Path -Signal Label Mismatch warning

HPA : Higher order Path Adaptation

TU-LOM Tributary Unit - Loss Of Multiframe minorTU-AIS Tributary Unit – Alarm Indication Signal warningTU-LOP (TU3) Tributary Unit - Loss Of Pointer majorTU-LOP (TU12) Tributary Unit - Loss Of Pointer minor

LPOM : Lower order Path Overhead MonitorLO-EBER Bit Error Rate > 10-3 on B3 (VC3) or V5 (VC12)

Bytemajor

LO-SD Signal Degrade – B3 or V5 minorLO-REI Remote Error Indication warningLO-RDI Low order Path -Remote Defect Indication warningLO-UNEQ Low order Path – Unequipped warningLO-TIM Low Order Path - Trace Identifier Mismatch minor

LPT : Lower order Path TerminationLO-EBER Bit Error Rate > 10-3 on B3 (VC3) or V5 (VC12)

Bytemajor

LO-SD Signal Degrade – B3 or V5 minorLO-REI Remote Error Indication warningLO-RDI Low order Path – Remote Defect Indication warningLO-UNEQ Low order Path – Unequipped warningLO-TIM Low Order Path - Trace Identifier Mismatch minorLO-PLM Low order Path – Signal Label Mismatch warningPPI : PDH Physical Interface

PPI-LOS (21 x 2Mor motherboard)

Loss Of Signal minor or warningaccording to custom

PPI-LOS (34 / 45M) Loss Of Signal majorPPI-AIS Alarm Indication Signal warning


2 - OPERATION



SETS : Synchronous Equipment Timing SourceT3 LOS Loss Of Signal on T3 sync input minorT1 LOS Loss Of Signal on T1 sync input warningT2 LOS Loss Of Signal on T2 sync input warningT4 - Failure Failure on T4 synchronization output minorSync Freq Out ofRange Severity

Synchronization rhythm frequency out of phaselocked loop range (*)

warning

Local equipmentLocal user input # 1 Remote indication 1 warningLocal user input # 2 Remote indication 2 warningLocal user input # 3 Remote indication 3 majorLocal user input # 4 Remote indication 4 minorRemote equipmentRemote input # 1 Remote indication 1 major **Remote input # 2 Remote indication 2 minor **Equipment managementPPP#1 to 4 IP intfDOWN

Loss of management link PPP#i minor

Ethernet IP intfDOWN

Loss of Ethernet link minor

LAN FunctionTU-AIS Tributary Unit – Alarm Indication Signal warningTU-LOP Tributary Unit - Loss Of Pointer majorVC3-RDI Low order Path - Remote Defect Indication warningVC3-SD Signal Degrade –B3 minorVC3-UNEQ Low order Path - Unequipped warningVC3-PLM Low order Path - Signal Label Mismatch warningLAN InterfaceDefect

Loss of Ethernet link major


(*) Internal equipment rhythm is then kept in a ±9.2 ppm range

(**) If the equipment configured is declared central office.

2 - OPERATION



GFP150 and 4E/FE FunctionsETH InterfaceDefect

Loss of Ethernet link major

Pause ModeRejected (*)

Pause Mode Rejected major

VCAT loa Loss of Alignment majorGFP lfd Loss of GFP Frame delineation majorGFP locs Los Of Client Signal minorGFP loccs Los Of Client Character Synchronisation minorUPM User Payload Mismatch minorEXM EXtension header Mismatch minorVCAT lom Loss of Multiframe warningVCAT sqm SeQuence Mismatch warningLCAS Member fail(**)

A member of VCG is failed warning

VCG defect (***) All VCG is failed, interrupted traffic majorVCG degraded (**)(***)

Some VCG are failed, degraded traffic minor


(*)This alarm is raised when the "Automatic" mode and the "Pause" capability are selected andthe Pause status = No Pause (the remote equipment has refused the negotiation of Pause).

(**)This alarm is computed only if LCAS is active.

(***)These alarms are indications of state of the path elaborated for the network manager insupplement of faults indications ; of this fact 2 indications can be transmitted in logs for onlyone default.

2 - OPERATION



FAN moduleOne Fan Failed One Fan Failed minorBoth Fans Failed The two Fans Failed major

ShelfOverheat Temperature overtaking major

Power supply48V#1 Missing of 48V#1 input PWRA Sub-D major48V#2 Missing of 48V#2 input PWRB Sub-D major48VJ Missing of 48V input PWR Jack major5V General Power Supply failure 5V Major5V_FAN FAN Power Supply failure 5V major

OthersMessage Daughter board Defective majorMessage Daughter board Mismatch majorMessage Daughter board Missing majorMessage Mother board Defective majorMessage FAN Missing majorMessage Overheat majorMessage No MSTP Licence

(only GFP150 card) major


2 - OPERATION


Correlation of faults

A correlation mechanism is implemented on all faults detected.

This correlation mechanism, implemented on each change of information collected, is used toeliminate faults induced by other faults to facilitate fault finding and fault locating.

The following tables define the faults that are masked for each fault detected in the system..

Key :

X : The fault concerned on the current line is masked by the fault in the currentcolumn.For example : The LOF fault is masked by fault 2 (LOS).

Correlation of STM-n faults

FAULTSFAULTS

1TF

2LOS

3LOF

4TIM

5EBER

-B1

6AIS

7EBER-

B2

8SD-B2

9RDI

10REI

1 TF

2 LOS

3 LOF X

4 TIM X X

5 EBER-B1 (RS-EBER)

X X X

6 AIS (MS-AIS) X X X X

7 EBER-B2 (MS-EBER)

X X X X X

8 SD-B2 X X X X X X

9 RDI (MS-RDI) X X X

10 REI (MS-REI) X X X X

Correlation of MSP faults

FAULTSFAULTS

1PAM

2SCM

3OTM

1 PAM

2 SCM X

3 OTM X

2 - OPERATION


Correlation of AU faults

The AU faults are masked by the STM-n LOS, LOF and AIS (MS-AIS) faults.

The TU-LOM fault is filtered, if there is no configured VC12 connection on this STM-n.

FAULTSFAULTS

1AU-AIS

2AU-LOP

3UNEQ

4TIM

5RDI

6REI

7PLM

8TU-LOM

9EBER

-B3

10SD-B3

1 AU-AIS

2 AU-LOP

3 UNEQ (VC4 UNEQ) X X

4 TIM X X X

5 RDI (VC4 RDI) X X X X

6 REI (VC4-REI) X X X X X

7 PLM (HPT) X X X X

8 TU-LOM X X X X X

9 EBER-B3 (VC4) X X

10 SD-B3 (VC4) X X X

Correlation of TU/VC faults

The TU/VC faults are masked by the STM-n LOS, LOF and AIS (MS-AIS) faults, and by the AUAU-LOP, AU-AIS, UNEQ (VC4 UNEQ), PLM (VC-PLM), TIM (VC4_TIM) and TU-LOM faults.

TU-LOP is masked by the AU PLM and TU-LOM faults.

The TU/VC faults of a not connected input are filtered.

FAULTSFAULTS

1TU-AIS

2TU-LOP

3UNEQ

4TIM

5RDI

6REI

7PLM

8EBER

9SD

1 TU-AIS

2 TU-LOP

3 UNEQ X X

4 TIM X X X

5 RDI X X X X

6 REI X X X X X

7 PLM (LPT) X X X X

8 EBER- X X

9 SD X X X

Correlation of port faults

FAULTSFAULTS

1LOS

2AIS

1 LOS

2 AIS X

2 - OPERATION


Correlation of VCG faults from GFP150 and 4E/FE cards

The LOA, LFD, LOCS, LOCCS, EXM, UPM, DEFECT and DEGRADED alarms are VCGalarms.

The LOM, SQM, LCAS_MemberFail alarms are alarms of member constituting a VCG.

FAULTS

FAULTS

1LOA

2LFD

3LOCS

4LOCCS

5EXM

6UPM

7LOM#i

8SQM#i

9LCAS_

MemberFail#i

10DEFE

CT

11DEGRADED

1 LOA

2 LFD X

3 LOCS X X

4 LOCCS X X

5 EXM X X

6 UPM X X X X

7 LOM#i

8 SQM#i X

9 LCAS_MemberFail#i

10 DEFECT X

11 DEGRADED

Definitions of VCG_DEFECT and VCG DEGRADED synthesized failure indications

Notations in the following paragraphes :

SF Member#i corresponds to at least one of among failures LOM#i, SQM#i, SF_LPT#i or LCASMember 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, TU-LOP, 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 failureindications 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 failure indications israised and 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 israised.

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 SDHbandwidth.

2 - OPERATION


2.6 - Performance processing

Performance processing consists in supervising the following monitoring ports :

for local equipment :

regeneration section (byte B1) ("near end working (protection) RS"),

multiplex section (byte B2) ("near end working (protection) MS"),

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"),

for the remote equipment :

multiplex section (byte M1) ("far end working (protection) MS"),

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 includes the following functions :

calculation of the number of errored blocks (or bit errors) on local and remote faults andmonitoring of the appearance faults over a one second period,

calculation and determination of the ES (Errored Second), SES (Severely Errored Second),BBE (Background Block Error) and UAS (UnAvailable Second) states for each monitoringpoint,

generation for each monitoring point of 15-minute counters and 24-hour counters (BBE, ES,SES and UAS).

Determination of ES, SES and UAS performance states :

For each of the monitoring points, the following states are :- ES (Errored Second) : number of seconds with at least one error detected

in a 1 s period or one fault,- SES (Severely Errored Second) : number of severely errored seconds,

A SES is a second for which the number of errors exceeds a defined threshold or duringwhich at least one fault is detected.

Monitoring point SES declaration thresholdMS (byte B2) (for local) and MS (byte M1) (for remote) 28800 (24 blocks per frame)RS (byte B1) (for local) 9600 (8 blocks per frame)HP – VC4 2400LP - VC3 (for local) 2400LP - VC12 (byte V5) (for local) 600

- UAS (UnAvailable Second) : number of seconds of unavailability,

- BBE (Background Block Error) : number of residual errored blocks excluding SES.

2 - OPERATION


Generation of 15-minute and 24-hour counters :

The result of these calculations is then aggregated for each of the monitoring points in :

24-hour counters (BBE, ES, SES and UAS),

15-minute counters (BBE, ES, SES and UAS).

The last 6 UNAVAILABLE PERIODS are stored and displayed on Web browser.

The performance process is initialized when the equipment is powered up and the monitoringpoint is monitored.

The last 16 non-zero 15-minute counters, the current 15-minute counter, the last non-zero 24-hour counter, the current 24-hour counter and the last 6 unavailable periods are displayed onWeb browser.

2.7 - Procedure for replacing subassemblies

2.7.1 - Replacing a card

Remarks :

Alarms appear whenever a card is extracted from the subrack. In order to prevent feedbackof alarms and ALA 1 and ALA 2 loops, the card should be declared out of service.

Each module can be extracted or inserted without acting on other modules or their wiring.Only the traffic of the concerned module is disturbed.

Procedure :

The procedure described below can apply, unless otherwise specified, to all the cards in theequipment.

1. Put the card concerned "no service" from Web browser.

2. Remove the external connections performed on the card front side.

NOTE : When the external optical fibers are disconnected, reinstall the protectivecovers on connectors.

3. Screw off the TORX screws located on the front side, using the suited screwdriver andunplug the card

4. Extract the card, complying with the measures of protection against electrostatic discharges.

NOTE : For any card handling, the operator must wear an anti-static bracelet welltight around the wrist and earthed.

5. Package the extracted card in an anti-static bag.

6. Take the new card out of its anti-static bag.

2 - OPERATION


7. Carefully insert the card into its cell, complying with the measures of protection againstelectrostatic discharges, and secure it with the TORX screws.

8. Restore connections on the card front side.

NOTE : For the optical STM-n card, remove the protective covers from connectors.

To clean the optical connectors, use a pressurized air aerosol.

9. Configure the card, if necessary, and put it into service.

2.7.2 - Replacing the fan module

The FAN module consists of two redundant fans in order to ensure sufficient ventilation wheneither of them is defective. Fan failures are detected on the motherboard by monitoring thepower consumed; failures are viewed on " Shelf View" screen of Web browser.

Default parameters lead to the following behaviour :

The default configuration of severities of the module is :

Minor : one of two fans is faulty

Major : both fans are faulty.

NOTE : The operation of FAN is not continuous; its initiation is related to theequipment internal temperature and to the operating mode selection.

FAN can be extracted, it can be replaced at any moment without disturbing the traffic.

Procedure :

1. Screw off the TORX screws located on the front side, using the suited screwdriver andunplug the card.

2. Extract the card, complying with the measures of protection against electrostatic discharges.

NOTE : For any card handling, the operator must wear an anti-static bracelet welltight around the wrist and earthed.

3. Package the extracted module in an anti-static bag.

4. Take the new module out of its anti-static bag.

5 Carefully insert the module into its place, complying with the measures of protection againstelectrostatic discharges, and secure it with TORX screws

2.8 - Preventive maintenance

In order to avoid a deterioration in the efficiency of ventilation, it is advised to be careful that the gridsof ventilation and blades of the fans are not fouled. A regular check and, if necessary, a dusting isrecommended.

3 - SPARE PARTS AND CABLES


3. SPARE PARTS AND CABLES

Mnémonic Designation Code N°

ADR155C

ADR155C 75Ω ADR155 75 GENERIC SHELF 252 134 450

ADR155C 75Ω /HOLDOVER

ADR155 75 HOLDOVER GENERIC SHELF 252 134 447

ADR155C 120Ω ADR155 120 GENERIC SHELF 252 134 848

ADR155C 120Ω /HOLDOVER

ADR155 120 HOLDOVER GENERIC SHELF 252 134 830

FAN FAN ADR155C GENERIC 252 124 433

Access Cover COVER 55 101 170

Fan Cover MODULE FAN ADR155C COVER 251 856 367 (*)

CARDS

IC1.1-2G 1XSTM-1 1XAUX/EOW IC1.1 OPTICAL UNIT 251 905 938

IC1.2-2G 1XSTM-1 1XAUX/EOW IC1.2 OPTICAL UNIT 251 905 941

S1.1-2G 1XSTM-1 1XAUX/EOW S1.1 OPTICAL UNIT 251 851 565

S4.1 A155 BLK SC/PC S4.1 OPTIC STM4 ITFE CARD 251 128 619

L4.1 A155 BLK SC/PC L4.1 OPTIC STM4 ITFE CARD 251 128 627

L4.2 A155 BLK SC/PC L4.2 OPTIC STM4 ITFE CARD 251 172 592

ERE A155 BLK BNC ELEC STM1 ITFE CARD 251 137 431

E3DS3 A155 BLK BNC E3DS3 ITFE CARD 251 137 423

21E120 A155 BLK BNC 21E1/120 ITFE CARD 251 137 402

21E75 21 E1 75 OHMS TRIBUTARY UNIT 251 819 348

21E1R8 21E1/8E1 RET/120 BLK A155 ITFE CARD 251 259 985

LAN1 A155 BLK ADRLAN 10/100BT ETH ITFE CARD 251 137 410

GFP150 A155 BLK ADRGFP 10/100 BT ETH ITFE CARD 251 347 772

4E/FE ITFE ETH 10/100 BT 4E/FE ADR155 CARD 252 173 134

Externaltransformer

1.5A - 48V / 100-240V EXT POWER SUPPLY 186 849 742

Table 3-1 - ADR155C Components list

(*) Customization according to the custom



Available cables list

Designation Length Code no.

120 ohms SYNC portSynchronization (1/2 cable) 2,5 m

12 m 251 008 309 251 008 320

SYNC – BNC Synchro 75 Ω (adapter)

(whole cable – one T3 input / one T4 output)

30 cm 251 118 155

120 ohms E1 INPUT or E1 OUTPUT port21x2Mbit/s In or Out on motherboard or 21E120card or 21E1R8 card

Et or ST 21x2 Mbit/s 120 ohms SUBD(1/2 cable)

2,5 m12 m

55 670 741 55 670 743

75 ohms E1 INPUT or E1 OUTPUT port21x2Mbit/s In or Out on motherboard or 21E75card

Et or ST 21x2 Mbit/s 75 ohms SUBD(1/2 cable)

2,5 m12 m

252 005 399 252 005 422

COMM portVT100 Management port 1,8 m 4 980 214

ETH portEthernet port on mother board, LAN1 card,GFP150 card, 4E/FE card : cable FTP category 5

Right cable male – maleCrossover cable male – male

3 m 3 m

55 670 422 55 670 610

LOOPS portRemote indication, remote control and station alarmloops (1/2 cable)

2,5 m 12 m

6 013 6286 013 161

POWER port Power supplyFree extremity cablePAPA cable

3 m3 m

251 065 81755 670 797

Table 3-2 - Available cables list



Available cables list (continue)

Designation Length Code no.

TR or REC ports ( optical cards)

Optical jumper SC-PC/SC-SPC

1,5 m2,5 m3,4 m4,6 m5,8 m7 m

8,2 m9,4 m12 m15 m20 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 254 251 036 262 251 036 275

TR or REC ports ( ERE, E3DS3 75 ohms cards)

½ BNC 75ohms right cable (1 coax.) 2,5 m5m

12 m25 m

55 670 054 55 670 055 55 670 056 55 670 057

AUX or EOW portsSub-D "Y" cableRight cable

251 014 20355 670 253

EOW / AUX portsSub-D "Y" cableSub-D/RJ45 adapter cableRight cable

251 014 203252 100 420252 069 380

Table 3-3 - Available cables list

4 - SPECIFICATIONS


4. SPECIFICATIONS

EQUIPMENT

Optical specificationsInterface type S1.1-2G ; IC1.1-2G ; IC1.2-2G ; S4.1 ; L4.1 ; L4.2Bit rate STM-1 : 155.520 Mbit/s ± 20 ppm

STM-4 : 622.08 Mbit/s ± 20 ppmStandard ITU-T G.957 for single mode interface

Encoding Not encoded (NRZ)Optical fiber Single mode : 1310 nm (IC1.1-2G, S1.1-2G, S4.1, L4.1)

or 1550 nm (IC1.2-2G, L4.2),UIT-T G.652.

Guaranteed attenuation IC1.1-2G, IC1.2-2G : 0 – 28 dB with no externalattenuator S1.1-2G : 0 - 12 dBL4.1, L4.2 : 10 - 24dBS4.1 : 0 - 12dB

Typical range S1.1-2G : 0 - 15 kmIC1.1-2G : 0 - 65 kmIC1.2-2G : 0 - 80 kmS4.1 : 0 - 15kmL4.1 : 10 - 40kmL4.2 : 10 - 80km

Connector SC/PC

Mechanical specifications of ADR155C subrackHeight 2UWidth 19" or ETSIDepth 257 mm rack 19''

243 mm rack ETSIWeight 6 kg approx.Protection Class (IP) Corresponding to the IP of the rack usedConsumption

(see details below)

< 40 W (for an equipped subrack of two Optical cardsand two LAN1 cards)

Table 4-1 - ADR155C technical characteristics

4 - SPECIFICATIONS


EQUIPMENT

Environmental specificationsMechanical ETS 300 119-4 (19") or CEI 297-3 (ETSI)

ETS 300 019-2-3Climatic conditions CEI 721-1 (1993)

ETS300 019 part 1-3, class 3.1, 3.2Operating temperature range - 5 °C à + 45°CExtended operating temperature range(non destructive degraded moderequiring a FAN module)

- 5 °C to + 55°C (the MTBF [Mean Time BetweenFailure] is significantly degraded)

Packaged transportation and storagetemperature

- 40°C to + 70°CETS 300 019 part 1-1 class 1.2

Relative humidity < 85%EMC (Electromagnetic Compatibility)And ESD EN 300386 / ES 201468

Safety NF EN 60950 -1 April 2002(the equipment does not provide the fire envelope)

Energy ETS 300132-2(is VLV equipment)

Predicted reliability (*)

Motherboard 1.51 10-6

21E120 card 0.29 10-6

21E75 card 0.29 10-6

21E1R8 card 0.43 10-6

IC1.1-2G card 0.98 10-6

IC1.2-2G card 0.98 10-6

S1.1-2G card 0.98 10-6

S4.1 card 1.1 10-6

L4.1 card 1.1 10-6

L4.2 card 1.1 10-6

ERE card 0.29 10-6

E3DS3 card 0.21 10-6

LAN1 card 0.52 10-6

GFP150 card 0.77 10-6

4E/FE card 0,42 10-6

Holdover card 0.1 10-6

Background 0.26 10-6

FAN Module 3 10-6


(*) The predicted reliability computations have been realized with the RAM COMMANDERsoftware issue 7.2 according to the UTE C80 810 of july 2000 standard, on the assumptionof specific requirements for the following: ambient temperature 20°C (with ventilationconditions such as the subrack internal middle temperature is less than 40°C), environment(mounted on the ground, fixed and protected), qualification, and component ageing (year ofcomponents production : 2005).

Any changes in the above requirements may entail variations in the results.

4 - SPECIFICATIONS


EQUIPMENT

Path Transfer Time

E1 Port to SDH Port < 0,2 msSDH Port to SDH Port < 0,1 msE3DS3 Port to SDH Port < 0,1 ms


Sub-assemblies consumption * (measured when powered by 48V supply)

Motherboard 10.7 W21E120 card 5.0 W21E75 card 5.0 W21E1R8 card 5.5 WIC1.1-2G card 3.2 WIC1.2-2G card 3.2 WS1.1-2G card 3.2 WS4.1 card 4.0 WL4.1 card 4.0 WL4.2 card 4.0 WERE card 4.9 WE3DS3 card (in DS3 mode) 3.9 WE3DS3 card (in E3 mode) 3.72 WLAN1 card 6.8 WGFP150 card 11 W4E/FE card 4.5 WHoldover card 0.5 WFAN Module 4.43 W


* These power consumptions are typical values and may be used for dissipation evaluation. Itis necessary to add 20% to estimate peak values which determine power rack capacity. Thisallows to take into account the dynamic power variations and the converter efficiencyvariations according to total power supply.

Warning : It is necessary to add another 10% when powered by 72V supply.

POWER BLOCK 100-240//48V 1.5A (OPTIONAL)

Dimensions (without cable and connector) L x l x H = 132 mm x 58 mm x 30 mmOperating temperature 0°C to 40°CStorage temperature -20°C to 85°CInput voltage 100 to 240 VAC / 1,5 AInput frequency 47 to 63 Hzoutput voltage 48 VDC / 1,5 AElectronics protection Short circuit and overloadStandard EN60950 and UL-CSA


4 - SPECIFICATIONS


5 - STARTUP GUIDE


5. STARTUP GUIDE

Introduction

Thank you for acquiring the ADR155c 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 tobe build.

5.1 - Installing the equipmenta) 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 « ON » led comes on steady

5 - STARTUP GUIDE


5.2 - Connecting to an ADR155c

PC minimum requirements

Description Configuration 1 Configuration 2 Configuration 3 Observations

Processor 266 MHz Pentium

Memory 32 MB 64 MB 128 MB

Display 800x600 256 colours (1024x768 recommended)

RS232 serial interface SUB-D straight cable9pts Male / Female

InterfacesEthernet 10 Base T network card RJ45 crossed Ethernet

cable

Operating system Windows 95 / 98 Windows NT4 / 2000 Windows XP

HyperTerminal for Windows

SoftwaresWeb Browser : Internet Explorer1 5.0 (*)

(*) The operating PC can be equipped with Internet Explorer 5.5 or 6.0 (Windows XP delivered issue)

1 Trademark of Microsoft Corporation

5 - STARTUP GUIDE


In order to be managed, the ADR155c subrack must have the Equipment address and the Ethernet port address configured in two different sub-networks.

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 : 19200• Data bits : 8• Parity : None• Stop bits : 1• Flow control : None

Save the connection settings. The next time you will run the HyperTerminal, just click on the connection icon to connect to theequipment.

Press "ENTER" twice on the keyboardThe 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 theexample below, the Equipment address is 192.168.30.30 ).

5 - STARTUP GUIDE


Follow the instructions below to configure the Equipment address

Choose menu 1 andconfirm by pressing"ENTER" key on thekeyboard.

5 - STARTUP GUIDE


The IP address can be input with or without non-significant "0" :192.168.30.30 or 192.168.030.030

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

Answer the questionsand confirm each oneby pressing "ENTER"key on the keyboard.

In this example, theEquipment addressis 192.168.30.30

: Values to be input

5 - STARTUP 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 is135.11.110.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 Placesicon, 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 andconfirm by pressing"ENTER" key on thekeyboard.

5 - STARTUP GUIDE


The IP address can be input with or without non-significant "0" :135.11.110.10 or 135.011.110.010

After you type y to confirm the question Save interface parameters (y/n)? there are a few seconds delay before display of thesentence 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.

Answer the questionsand confirm each oneby pressing "ENTER"key on the keyboard.

In this example, theaddress of the unit'sEthernet port is135.11.110.10

: Values to be input

5 - STARTUP GUIDE


Managing the equipment

Example:

The equipment is managed by an HTTP browser.

Connect the equipment's "ETH" port to the PC's Ethernet card using the RJ45 crossed Ethernet cable The yellow LED of the equipment'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 HTTPbrowser to set the font size)

On the home page, complete the "Address" field with the Equipment address (192.168.30.30)

The window Welcome on the ADR155C'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.

5 - STARTUP GUIDE


5.3 - Configuring a PPP portA PPP (Point to Point Protocol) port of an equipment must be configured when extending a network, as the modification of the Equipment addressand the Ethernet port, using the HTTP browser.

In the example below, the instructions are given for configuring the PPP1 port. Configuration of the PPP2, PPP3 and PPP4 ports is identical to thePPP1 port one.

Connect the equipment's "ETH" port to the PC's Ethernet card using the RJ45 crossed Ethernet cable The yellow LED of the equipment's "ETH" connector must go on.

Run the HTTP browser

In the home page, complete the "Address" field with the Equipment address (192.168.30.30)

The window Welcome on the ADR155C's site appears on screen. By default, there is no Password; click on "Apply"

The window Shelf view appears on screen.

Click on the “ETH” port then on the “Interfaces Configuration” link to configure the equipment's PPP1 port

Click on the “Apply” button, the PPP1port is configured.

5 - STARTUP GUIDE


5.4 - Viewing the routing configuration

Click on the “Routing Table” link to view the equipment's routing configuration.

Example :

5 - STARTUP GUIDE


5.5 - Building a point-to-point linkThis chapter describes the IP configuration of the interfaces for a point-to-point link using an example.

For each equipment, you can configure the Ethernet port, the Equipment address and the four PPP (Point to Point Protocol) software ports fromPPP1 to PPP4. You can assign to each PPP software port one of the five physical ports corresponding to the MNGT port and the slots A, B, C, D as well astwo VC12 channels marked P#1 and P#2.

Example:

Both ADR155c units can be managed by an HTTP browser.

Refer to the chapter Connecting to an ADR155c for managing the equipment by the HTTP browser.

The gateway address matches theaddress of the equipment's Ethernet portin relation to the PC.

Refer to the chapter Connecting toan ADR155c to configure theEthernet port and the Equipmentaddress of each equipment.

Refer to the chapter Configuring aPPP port to configure the PPP portsof each equipment.

5 - STARTUP GUIDE


5.6 - Building a bus linkThis chapter describes the IP configuration of the interfaces for a bus link using an example.


Example:

The three ADR155c units can be managed by an HTTP browser.


Refer to the chapter Connecting to anADR155c to configure the Ethernet port andthe Equipment address of each equipment.

Refer to the chapter Configuring a PPPport to configure the PPP ports of eachequipment.

5 - STARTUP GUIDE


5.7 - Building a ringThis chapter describes the IP configuration of the interfaces for a ring network using an example.


Example:

The three ADR155c units can be managed by an HTTP browser. The management links are secured by the OSPF protocol.


Refer to the chapter Connecting to anADR155c to configure the Ethernet port andthe Equipment address of each equipment.

Refer to the chapter Configuring a PPPport to configure the PPP ports of eachequipment.

5 - STARTUP GUIDE


5.8 - Managing equipment through the network of a different supplierThis 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 ADR155c to configure theEthernet port and the Equipment address of each equipment.

Refer to the chapter Configuring a PPP port to configure the PPPports of each equipment.

Refer to the next page for more details on configuring the PPP3 port ofADR155c N°3 and the PPP1 port of ADR155c N°4.

5 - STARTUP GUIDE


Details on configuring the PPP3 port of ADR155c N°3 and the PPP1 port of ADR155c N°4

Configuring the PPP3 port of ADR155c N°3

1. Configure the PPP3 port with HTTP browserRefer to the chapter Configuring a PPP port for theprocedure

2. Create a connection with the HTTP browser between the P#1port of the mother board and the C#63 port of slot C.Consult the ADR155c help menu to create a connection byclicking on the HELP link of the main window.

Configuring the PPP1 port of ADR155c N°4

1. Configure the PPP1 port with HTTP browserRefer to the chapter Configuring a PPP port for theprocedure

2. Create a connection with the HTTP browser between the P#1port of the mother board and the D#63 port of slot D.Consult the ADR155c help menu to create a connection byclicking on the HELP link of the main window.

5 - STARTUP GUIDE


6 – GFP150 CARD


6. GFP150 CARD

All the services mentioned in this document can be performed between the GFP150 cards from ADR155C butalso between the GFP150 cards and the GFP150 eXtra cards from ADR2500 eXtra.

Only the EPLine and EPLAN services can be interconnected with the EPLine service proposed by a 4E/FEcard.

Only one GFP150 can be installed in an ADR155C shelf either in the A slot or in the C slot ; the presence ofFAN module is mandatory.

6.1 - GFP150 CARD AND SERVICES PRESENTATION

This chapter has for objective to guide the user for the commissioning of the GFP150 card in the ADR155C. Itgives simple examples which should be easily adapted to the needs.

Services provided by GFP150 card in ADR155C are :

• SMART LL – EPLine Service (from P4.1 and P5.1 levels) :

The EPLine service (Ethernet Private Line) allows Ethernet 10/100 BaseT point to point interconnectionthrough 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 card. Rategranularity for each VCG is based either on VC12, or on VC3. With each VCG, it is possible toconcatenate from 1 to 46 VC12 or from 1 to 2 VC3. The sum of the concatenated Ethernet rates, on thewhole of the 8 ETH ports, cannot be above the STM1 payload (about 150Mbit/s).

• AGGREGATION – EVPLine Service (from P5.2 level) :

The EVPLine service (Ethernet Virtual Private Line) allows several Ethernet 10/100 BaseT point to pointinterconnection through a SDH network by using over shared VCG (VC-Group) based on virtualconcatenation (VCAT). These VMAN are separated by Tag VMAN, that adds a level of VLAN in relation tothe possible VLANs of Customers. It is possible to put until 16 aggregation traffic (VMAN) on a VCG. In theGFP150 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 P4.1 and P5.1 levels) :

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

6 – GFP150 CARD


• AGGREGATION – EVPLAN Service (from P5.2 level) :

The EVPLAN service (Ethernet Virtual Private LAN) allows several Ethernet 10/100 BaseT multipoint tomultipoint interconnection through a SDH network by using over shared VCG (VC-Group) based on virtualconcatenation (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 card).It is therefore possible to put until 16 aggregationtraffic (VMAN) on a VCG. In the GFP150 card we can have 64 (63 if the MSTP protection is used) differentVMAN maximum.In this case, each GFP150 card includes a switch function allowing Ethernet 10/100 BaseT multipoint tomultipoint 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 card is based on a traffic differentiation : metering, congestion control andscheduling.

Hardware design

8E/FE TX

To switchfabric

155 Mb/sSwitchSwitchGFP MapperGFP Mapper

Micro ProcessorMicro Processor

Figure 6-1: Hardware design of the card

6 – GFP150 CARD


6.2 - CONFIGURATION AND APPLICATIONS OF THE GFP150 CARDS

6.2.1 - GFP150 card setup

a) Unwrap the card

b) Insert and screw the card in an allowed slot of the ADR155C shelf.

c) Verify the presence of FAN module in its slot.

d) Verify with HTTP configuration manager that the GFP150 pack (Upload/Download > Switchingmenu) is present in the system.

e) In the HTTP configuration manager, select GFP150 as expected card on the slot where it wasinserted

f) Connect the Ethernet cables to the GFP150 card

g) Wait a few seconds and check that the green LED “status” is steadily on.

6.2.2 - Create a LAN interconnection

6.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 ofADR155C. In a first time, one supposes that the rate of the Ethernet traffic exchanged between the 2 sites doesnot exceed 10Mbps. The QoS configuration is explained later in this document in greater details.

EEtthh//VVCC1122

AADDRR 115555CC

AADDRR 115555CC SSDDHH

EEtthheerrnneett 1100//110000MM EEtthheerrnneett 1100//110000MM

Figure 6-2 : EPLine service

6.2.2.1.1 - GFP150 cards configurationLogin on the first ADR155C to open the “Shelfview” HTTP screen. On this screen, click on the GFP150 cardthen on the "GFP's Functional Groups" link.

6 – GFP150 CARD


Configuring the Ethernet interfaceClick on the "ETH" block then on the “Interface Settings” link. By default the Ethernet interface is forced in100Base T full duplex. We choose to keep the default configuration for this example.

Figure 6-3 : Configuring the Ethernet interface

Note : The Ethernet interface of the remote equipment (switch, IP router, PC, …) connected to the GFP150card MUST always be configured the same way. Due to possible interoperability issues with Auto-Negotiation between equipments from different origins, this feature (“Automatic” option) shouldpreferably 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 customerwith one service per port. On these interfaces the provider OAM and BPDU MSTP management frames arefiltered : they are not sent to the customer network.The NNI untagged choice (Network to Network Interface) corresponds to a provider interface without providerVMAN tag (no VLAN aggregation).The NNI tagged choice (Network to Network Interface) corresponds to a provider interface on which aprovider VMAN tag is inserted in the outcoming frames and a provider VMAN tag is treated in the incomingframes.

6 – GFP150 CARD


Link Down Retransmit

The Link Down Retransmit function can only be used in point to point mode on a VMAN constituted of one ETHport 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.

Pause Mode

The Pause function (IEEE 802.3 Flow control) can only be used in point to point mode/full duplex on a VMANconstituted 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 issuspended temporarily

- On detection of traffic obstruction on the VMAN considered in the sense ETH = > VCG, a pause frame istransmitted on the ETH port to ask the remote equipment to stop the transmission of Ethernet frametemporarily.

Warning : When the Pause mode is activated, be careful to configure the CIR and PIR to the maximum of thecapacity of the VCG

Configuring a VCG

Click on the “VCG” block, then on the “List” link. For the selected VCG#1 interface, click on VC#1 and then onthe “Multiple Add Member” link. In the new screen coming up, select “VC12” as type and VC#6 as lastconnection. 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.

GFP 150"LDREnable"

ETH Down Report

Status Down SDHVCG VCG

ETH ETH

Locs + VCG Down

VCG Down Report

VCG Down SDHVCG

VCG Down

GFP 150"LDREnable"

VCG

ETH

GFP 150"LDREnable"

GFP 150"LDREnable" ETH

1

23

4

1

2 23 3

ForcedCut off

Forced Cut off

ForcedCut off

6 – GFP150 CARD


Figure 6-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 defaultoptions for this example. This screen also displays the type of VCG#1 (VC12) and the number of constitutingVC members (6).


6 – GFP150 CARD


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 outcomingframes and a provider VMAN tag is treated in the incoming frames.

Click on the "VCG" block and then on the "Alarms " link. Select interface VCG#1 . Tick option "Monitor " andclick on "APPLY " in order to start monitoring alarms on this port (see Figure 6-9).

Configuring the Ethernet Switch

Click on the “Switch” block, then on the “VMAN Create” link. Enter “2” as new VMAN ID and click on “Apply” inorder 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 10Mbpsfor the CIR and PIR, and 7 for the "User Priority " (maximun priority) (for more information on the notion ofpriority, see the chapter on the QoS). The CBS and EBS values are left to default. Then click on “Add” tocomplete 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, andenter 10Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS valuesare left to default value. Then click on “Add” to complete the addition of this port to VMAN 2.

Figure 6-6 : Configuring the Ethernet Switch (1)

The association of these 2 ports to the same and unique VMAN ID isolates the Ethernet Switching betweenthese 2 ports from the rest of the ports (all the other Ethernet and VCG interfaces). Ethernet traffic forwardedbetween 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 theGFP150 card.

To double check the configuration click on the “VMAN List” link. A table displays what ports are associated witheach VMAN configured on the GFP150 card.

6 – GFP150 CARD



Configuring the SDH cross-connectsClick on the “XCN” block and configure the connections from VC12#1 to VC12#6 of the GFP150 card as usualin order to have end-to-end SDH connectivity with the remote GFP150 card.

Figure 6-8 : Configuring the SDH Cross Connects

6 – GFP150 CARD


Configuring the remote GFP150 cardJust do the configuration on the second ADR155C following the exact same steps again.

Activating the end-to-end Ethernet connectionOnce both ADR155C systems are configured, the ports used by the Point-to-Point can be activated on eachADR155C.

Click on the “ETH” block, then on the “Interface Settings” link. For interface ETH#1 , tick “ifAdminStatus up” andclick on “Apply”.

6.2.2.1.2 - Connectivity checkPerform the following verifications with both GFP150 cards:

1. Click on the "ETH" block, check that the Ethernet ports in use are not highlighted (the given box would bemarked yellow or red depending on alarm severity) ; then click on the "VCG" block and on the "Alarms" link,check that the VCG ports in use are not highlighted (the given box would be marked yellow or reddepending on alarm severity). Otherwise click on the alarmed port to go to the proper screen, where thespecific alarm is displayed (this brings you directly to step 2, 3 or 4 below). Repeat the operation for everyalarmed port.

2. Click on the “ETH” block and select Ethernet interface ETH#1. Verify that the interface is running in100BaseT full duplex and that there is no alarm (the “Fault” option of the Interface Defect alarm isunchecked). Otherwise double-check both the cables and the configuration of the connected Ethernetinterface.

3. Verify that there are no alarms on all the VC's being used. Otherwise double-check end-to-end SDHconfiguration as well as the signal quality over the various links.

4. Click on the “VCG” block then on the “Alarms” link, and select the VCG#1 interface. Once configuration iscomplete 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 6-9 : Connectivity check

6 – GFP150 CARD


Note : This screen can be used to configure the severity of the alarms related to concatenated VC’s.

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 PC’s 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 counters on both ends based on the traffic beingforwarded. Namely the following counters:- Ethernet counters: click on the “ETH” block and then on the “MIB2 Counters” link- GFP counters: click on the “VCG” block and then on the “MIB2/GFP Counters” link- SLA compliance counters: click on the “Switch” block. 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 aredescribed later in this document in greater details.

6.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 equippedof ADR155C by sharing the same VCG for the two traffics (aggregation), this in order to optimize the SDHbandwidth.

One supposes that the Ethernet traffic rate exchanged between the 2 sites does not exceed 10Mbps for eachflow.

EEtthh//VVCC1122SSDDHH


ADR155CADR155C

1 VCG

Figure 6-10 : Service EVPLine

6.2.2.2.1 - GFP150 cards configuration

Configuration of the Ethernet interfaceClick on the "ETH" block then on the “Interface Settings” link. By default the Ethernet interface is forced in100Base T full duplex. Apply the same configuration for all Ethernet ports.

Configuring a VCGClick on the “VCG” block, 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. Clickon “Apply” in order to create the virtually concatenated group of 12 VC12 (VC12#1 to VC12#12) that will beused to transport Ethernet traffic.

6 – GFP150 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 theaggregation, on the VCG1 the frames must be taggedThis screen also displays the type of VCG#1 (VC12) and the number of constituting VC members (12).


6 – GFP150 CARD


Click on the "Alarms " link. Select the interface VCG#1 . Tick "Monitor " option and click on "APPLY " in order tostart monitoring alarms on this port (see Figure 6-9)..


For the first ETH port (ETH1):Click on the “Switch” block, then on the “VMAN Create” link. Enter “2” as new VMAN ID and click on “Apply” inorder to add it. A new window 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 10Mbpsfor the CIR and PIR, and 7 for the "User Priority " (maximun priority) (for more information on the notion ofpriority, see the chapter on the QoS). The CBS and EBS values are left to default values. Then click on “Add” tocomplete 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, enter10Mbps 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):Click on the “Switch” block, then on the “VMAN Create” link. Enter “3” as new VMAN ID and click on “Apply” inorder to add it. A new window comes up in order to associate ports to this VMAN.

Click on the “Add Port” link. Select the Ethernet interface ETH#2, the “trTCM” policing algorithm, enter 10Mbpsfor the CIR and PIR, and 7 for the "User Priority " (maximun priority) (for more oinformation on the notion ofpriority, see the chapter on the QoS). The CBS and EBS values are left to default values. Then click on “Add” tocomplete 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, enter10Mbps 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.

The association of these 2 ports to the same and unique VMAN ID isolates the Ethernet Switching betweenthese 2 ports from the rest of the ports (all the other Ethernet and VCG interfaces). Ethernet traffic forwardedbetween 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 theVCG.

Note : In order to install a point-to-point connection (EVPLine service), there should never be more than 2ports (1 customer UNI Ethernet port and 1 tagged NNI Ethernet or VCG port) in the same VMAN on theGFP150 card.

To check the configuration click on the “VMAN List” link. A table displays the associated ports to eachconfigured VMAN on the GFP150 card.

Figure 6-13 : Configuring the Ethernet Switch

6 – GFP150 CARD


Configuring the SDH cross-connects

Click on the “XCN” block and configure the connections from VC12#1 to VC12#12 of the GFP150 card as usualin order to have end-to-end SDH connectivity with the remote GFP150 card.


Configuring the remote GFP150 card

Just do the configuration on the second ADR155C by following the exact same steps again.

Activating the end-to-end Ethernet connection

Once both ADR155C systems are configured, the ports used by the point-to-point links can be activated oneach ADR155C.

Click on the “ETH” block, then on the “Interface Settings” link. For ETH#1 and ETH#2 interfaces, tick“ifAdminStatus up” and click on “Apply”.

6.2.2.2.2 - Control of the link

Take again the procedure of the paragraph 6.2.2.1.2 - to do controls, by verifying the 2 links.

6 – GFP150 CARD


6.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 sitesand 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 thetotal rate of traffic going in the opposite direction (a.k.a. from the central site to the remote sites) doesn’t go over20Mbps ; 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 separateEthernet interfaces on the central site, and 1 point to point connection between each remote site and the centralsite. In this case configure 3 independent point-to-point connections as described in the previous section.

EEtthh // 66xxVVCC1122

Site central

Site distant 1

Site distant 2


EEtthheerrnneett 1100//110000

Site distant 3EEtthheerrnneett 1100//110000


SSDH



Figure 6-15 : EPLAN service

6.2.2.3.1 - Configuring the GFP150 card of the central siteLogin on the ADR155C of the central site to open the “Shelfview” HTTP screen. On this screen, click on theGFP150 card then on the "GFP's Functional Groups" link.

Configuring the Ethernet interface

Click on the "ETH" block then on the “Interface Settings” link. By default the Ethernet interface is forced in100Base 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 GFP150card MUST always be configured the same way. Due to possible interoperability issues with Auto-Negotiation between equipments from different origins, this feature (“Automatic” option) shouldpreferably not be used.

6 – GFP150 CARD



Configuring the VCGs

Click on the “VCG” block and then on the “List” link. For the selected VCG#1 interface, click on VC#1 and thenon the “Multiple Add Member” link. In the new screen coming up, select “VC12” as type and VC#6 as lastconnection. 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) ; ifthe 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).

6 – GFP150 CARD



Click on the “Settings” link. Verify that VCG#1, VCG#2 and VCG#3 are set with default configuration: “AdminStatus” at “Up”, "Logical Interface NNI " at "untagged", “LCAS” at “Yes” and “FCS” at “No”. We choose to keepthe default options for this example. This screen also displays the type of VCG#1,#2,#3 (VC12) and the numberof constituting VC members (6,6,3).


6 – GFP150 CARD


Click on the "Alarms" link. Select interface VCG#1. Tick option "Monitor " and click on "APPLY " in order to startmonitoring alarms on this port (see Figure 6-9). Repeat with VCG#2 and VCG#3.


Click on the “Switch” block and 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, and enter20Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values are leftto 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, andenter 10Mbps for the CIR, and PIR and 7 for the "User Priority " (maximun priority). The CBS and EBS valuesare 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#2, the “trTCM” policing algorithm, andenter 10Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS valuesare 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#3, the “trTCM” policing algorithm, andenter 5Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values areleft to default. Then click on “Add” to complete the addition of this port to VMAN 2.



6 – GFP150 CARD




Click on the “XCN” block. Configure the connections from VC12#1 to VC12#6 of the GFP150 card as usual inorder 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 card as usual in order to have end-to-endSDH connectivity between the central site and remote site 2.

Configure the connections from VC12#13 to VC12#15 of the GFP150 card as usual in order to have end-to-endSDH connectivity between the central site and remote site 3.

6.2.2.3.2 - Configuring the GFP150 cards of the remote sitesThe GFP150 cards of the remote sites must be configured as if they were in point-to-point mode. Hence, weapply the configuration described in the point-to-point section of this document (§ 6.2.2.1 -). However thepolicing rates (10Mbps or 5Mbps) and the right number of VC12 (6 or 3) must be configured appropriately foreach remote site 1, 2 and 3 (see Figure 6-15). See the topology figure of this example.

Activating the end-to-end Ethernet connections

Once both GFP150 cards at the ends of a connection are configured, the Ethernet interfaces should beactivated.

Click on the “ETH” block and then on the “Interface Settings” link. For interface ETH#1 , tick “ifAdminStatus up”and click on “Apply”.

6.2.2.3.3 - Connectivity checkFor each GFP150 card, perform the following verifications:


6 – GFP150 CARD



3. Verify that there are no alarms on all the VC’s being used. Otherwise double-check end-to-end SDHconfiguration as well as the signal quality over the various links.

4. Click on the “VCG” block and on the “Alarms” link, then select the VCG#1, VCG#2 and VCG#3 on thecentral site and only VCG#1 on a remote site. Once configuration is complete all alarms should disappearafter a few seconds. Otherwise double-check the configuration in the “VCG” functional block on both endsas 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:• Run a “ping” or a file transfer between 2 PC’s 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 counters on both ends based on the traffic beingforwarded.

6.2.2.4 - Bus interconnection : service “EPLAN”

In the network below, we setup an Ethernet 100BaseT LAN spanning over 4 sites connected to an ADR155C.

In this example, sites 2 and 4 play the role of a full bridge: : Ethernet frames can be forwarded between allremote 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 eachADR155C the Ethernet interface connected to the bus is policed at 10Mbps.

SSDDHH


EEtthh // 44xxVVCC1122EEtthh // 44xxVVCC1122

Site n°1

Site n°2

Site n°3


Site n°4

EEtthheerrnneett 1100//110000EEtthheerrnneett 1100//110000

Figure 6-21 : EPLAN Service - "bus" mode

6 – GFP150 CARD


6.2.2.4.1 - Configuring the GFP150 cards of sites 1 and 3The GFP150 cards of sites 1 and 3 must be configured in point-to-point mode following configuration guidelinesof the point-to-point section of this document (§ 6.2.2.1 -).

6.2.2.4.2 - Configuring the GFP150 cards of sites 2 and 4For sites 2 and 4, the configuration of functional blocks VCG, Connection (XCN) and Ethernet Switch is differentfrom the two other sites.

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 onthe “Multiple Add Member” link. In the new screen coming up, select “VC12” as type and VC#6 as lastconnection. 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).


6 – GFP150 CARD


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 defaultoptions for this example. This screen also displays the type of VCG#1 and VCG#2 (VC12) and the number ofconstituting VC members (6).


Click on the "Alarms " link. Select interface VCG#1 . Tick option "Monitor " and click on "APPLY " in order tostart monitoring alarms on this port (see Figure 6-9). Repeat with VCG#2.


Click on the “Switch” block and 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, and enter10Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values are leftto default. Then click on “Add” to complete the addition of this port to VMAN 2.



6 – GFP150 CARD






Click on the “XCN” block. Configure the connections from VC12#1 to VC12#6 of the GFP150 card as usual inorder to have end-to-end SDH connectivity between each middle site (2 or 4) and each edge site (respectively 1or 3, see Figure 6-21).

Configure the connections from VC12#7 to VC12#12 of the GFP150 card as usual in order to have end-to-endSDH connectivity between both middle sites (2 and 4).

6 – GFP150 CARD


Activating the end-to-end Ethernet connections

Once both GFP150 cards at the ends of a connection are configured, the Ethernet and VCG interfaces shouldbe activated.

Click on the “ETH” block and then on the “Interface Settings” link. For interface ETH#1 , tick “ifAdminStatus up”and click on “Apply”.

6.2.2.4.3 - Connectivity checkFor each GFP150 card, perform the following verifications:




4. Click on the “VCG” block and on the “Alarms” link, then select the VCG#1, VCG#2 and VCG#3 on thecentral site and only VCG#1 on a remote site. Once configuration is complete all alarms should disappearafter a few seconds. Otherwise double-check the configuration in the “VCG” functional block on both endsas 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:• Run a “ping” or a file transfer between 2 PC’s 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 counters on both ends based on the traffic beingforwarded.

6 – GFP150 CARD


6.2.2.5 - “ Bus interconnection : service “EVPLAN”

In the network below, we setup two Ethernet 100BaseT LAN spanning over 4 sites connected to an ADR155C.

To the difference of the EPLAN service, the two LAN use the same VCG to circulate, it is possible with theaggregation in the same VCG. For this the VCG ports of the N°1, N°2, N°3 and N°4 equipment must beconfigured in fashion NNI tagged.

In this example, 2 and 4 sites play the role of a full bridge: : Ethernet frames can be forwarded between allremote 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 eachADR155C, the Ethernet interface connected to the bus is policed at 10Mbps.

SSDDHH

EEtthheerrnneett 1100//110000 EEtthheerrnneett 1100//110000



Site n°3Site n°1

Site n°4Site n°2

Eth/12xVC12 Eth/12xVC12

Figure 6-26 : EVPLAN Service - "bus" mode

6 – GFP150 CARD


6.2.3 - Implementation of the OAM-CC function (Operation AdministrationMaintenance - Continuity Check) on the GFP150 card

The OAM function (Operation Administration Maintenance) in the GFP card, is used to supervise the customertraffic. This function consists in the broadcast and receipt of specific messages to supervise customer traffic. Thisallows to know the state of the network, in relation to the progress of this fluxIt is based on the IEEE-802. 1ag] norm . The supervision frames for broadcast and receipt are named framesCC : Continuity Check.

Below an example of utilization of the OAM function:

Probe Source OAM-CC

Probe Sink OAM-CC

Figure 6-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 ADR155C)

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 ADR155C).

In the example of the figure N°1, a source probe is declared in the equipment N°1 and a sink probe in theequipment N°2 on the same VMANi, that allows the monitoring of the VMANi customer traffic betweenequipment N°1 and equipment N°2 in one sense

To supervise the other sense of this VMANi it is necessary to add two supplementary probes, a source probe onthe equipment N°2 and a sink probe on the equipment N°1.

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 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.

Notes:

- The periodic OAM defect, can mean that network capacity for the VCG are not adjusted, and that congestionsappear (example : a VC link loss in a VCG with LCAS).- No OAM probe must be activated on a flow created between a GFP150 card and a 4E/FE card. The providerOAMcc frames are not filtered by the 4E/FE card and are forwarded to the customer network.

NNINNI

UNICE

CE

UNISDH Network

ADR155C N°1 ADR155C N° 2VMANi

6 – GFP150 CARD


6.2.4 - Using Quality of Service features of GFP150 card

6.2.4.1 - QoS functions of the GFP150 card

The GFP150 card provides various QoS functions. These functions format outgoing traffic flows on allinterfaces. 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 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 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 aggregatetraffic 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 theVMAN 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 functionsare configured separately per port.

FromEthernet

Toward SDHswitch fabric

VC3-nV ou VC12-nV

Metering Policing

File TC 0GREEN

YELLOW

RED

GREEN

YELLOW

Compteurs SLA

File TC 1

SCHEDULER

SP

Poids WRR

%Shaping

Ingress Egress

Figure 6-28 : QoS architecture

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).

6 – GFP150 CARD


In the first stage, the temporal characteristics of the actual traffic flow are measured (“metering”). By comparingthem 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 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 andYellow frames can progress.

Metering of the GFP150 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 thatinterface. In the current version of the GFP150 card, an interface can be associated to only one VMAN, henceonly one profile.

Traffic profilesTraffic profiles use the following parameters on the GFP150 card:

Parameter Description Unit srTCM trTCMCIR Committed Information Rate Mbps YES YESPIR Peak Information Rate Mbps NO YESEBS Excess Burst Size KB YES YESCBS Committed Burst Size KB YES YES

Figure 6-29 : Traffic profile

The QoS parameters strictly apply to the Ethernet traffic. The overhead generated by GFP encapsulation is notaccounted 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 burstdetermine its eligibility. Metering is based on a Committed Information Rate (CIR) and two associated burstsizes, a Committed Burst Size (CBS) and an Excess Burst Size (EBS). A packet is set compliant or green if itsrate is less or equal to the CIR or if its excess rate does not exceed the CBS. It is set partially compliant oryellow 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 acommitted 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 isset non compliant or red if its rate exceeds the PIR and its excess rate exceeds the EBS. A packet is setcompliant or green if its rate is less or equal to the CIR or if its excess rate does not exceed the CBS. Otherwiseit is set partially compliant or yellow.

Congestion avoidance and buffer management

The GFP150 card uses a standard algorithm to control the distribution of resources between classes of serviceLP (Low Priority) and SP (Strict Priority) in order to manage congestion phases.

6 – GFP150 CARD


The QOS configuration in the GFP150 holds account of the priority information affected to every aggregatecustomer. The priority affectation to a customer is done according to a SLA (service level agreement), via thefield configuration "User Priority" (between 0 and 7). To a priority data,.(configured in UNI (or 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 card, congestion can happen on transmission on an Ethernet or an Ethernetover 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. There can be more or less transitory phases where the sum of incoming trafficis significantly greater than the bandwidth available on the outbound port. Point-to-multipoint topologiesespecially subject to this type of congestion are those involving an Ethernet port configured at 10Mbps or anEthernet over SDH port configured with a small number of VC’s.

• Regardless of the actual topology, when a large quantity of traffic goes through the policing stage but withthe Yellow color (only partially compliant traffic). There can be more or less transitory phases where theexcess rate is actually too high to be transmitted fast enough over the outbound port. Traffic profilesespecially subject to this type of congestion are those with a large differential between the configured CIRand PIR.

Some repetitive or lasting congestion problems generally require an evolution of the topology network.

6.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 atraffic 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” block 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.

Figure 6-30 : Configuring a srTCM profile

6 – GFP150 CARD


The following screen shows the configuration of a “trTCM” traffic profile on an Ethernet port.

Figure 6-31 : Configuring a trTCM profile

User Priority

The priority affectation to a customer (VMAN) is done via the "User Priority" field configuration (between 0 and7). The values 6 and 7 are the most important values because they use the SP).

Parameters regulating for Classes of Service

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

Figure 6-32 : Reading Traffic Classes parameters

6 – GFP150 CARD


If the operator wants to modify one of these parameters he must disactivate the calculation mode automatic.For this, click on the "Global Params " block then on the "Advanced " link, select the wanted port for the modechange, then pass from ON to OFF the column parameter " Auto ", then one can modify the SP bandwidth.

Figure 6-33 : Regulating Traffic Classes SP parameters

SP Bandwidth % (1-100%) — Translation in percentage of configured bandwidth for Strict Priority waitingqueue.This queue encourages flux latency times that are affected to it, but with a limited queue shaping in order tokeep bandwidth for low priority queue

Reading the SLA counters

The GFP150 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” block and onthe “VMAN List” link. Select the row of the VMAN, click on the “VMAN SLA Counters” link. Then select a port.

6 – GFP150 CARD


Figure 6-34 : SLA compliance counters

The GFP150 card also offers supplementary counters by port/VMAN.To read these counters, click on the"Switch " block then on the "VMANPortCounters " link. In the top window, select the ETH and VCG ports onwhich one wants these counters. The number is limited to 2.In the below window, select the wanted port for the visualization.

Figure 6-35 : VMAN Port counters

6 – GFP150 CARD


6.2.5 - Using the Multiple Spanning Tree Protocol on the GFP150 card

6.2.5.1 - Description of the Multiple Spanning Tree Protocol on the GFP150 card

The GFP150 card enables activation of the "Multiple Spanning Tree Protocol " (MSTP), standard Ethernetprotocol defined in IEEE 802.1S.

MSTP can remove loops in an Ethernet network setup with redundant links. Without MSTP, these loops areforbidden by the Ethernet standard to avoid a "broadcast storm ". With a loop and no MSTP, all broadcastframes or unicast frames with an unknown address are endlessly replicated on all the links to the point wherethe 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 linksare terminated by Ethernet ports or Ethernet over SDH ports.- No MSTP must be activated on a flow created between a GFP150 card and a 4E/FE card. The provider BPDUMSTP frames are not filtered by the 4E/FE card and are forwarded to the customer network.

On the GFP150 card, MSTP can be turned ON/OFF at a global level first. Then, once globally activated, eachport Ethernet or Ethernet over SDH can be included or not in the Spanning Tree. Once a port is configured withMSTP, the protocol controls transmission over this port. Namely, MSTP can block transmission on the portmomentarily or until MSTP converges again following a link loss on an Ethernet port.

The MSTP protocol on the GFP150 card permanently exchanges control packets called "BPDUs " with all otherGFP150 cards running MSTP in the network. These packets are only forwarded on links included in theSpanning Tree by configuration.

Note : In the present configuration, only the VMAN of which the identifying is between 4032 and 4094 can useMSTP. 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 (VMANID from 2 to 4031) can broke the traffic associated to the VMAN without MSTP because this last is automaticallyin 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 theinformation of the BPDUs received from the network as well as the transitions of the operational state of anylocal port (in case of link loss/recovery for example).

Each MSTP port is managed by two different informations “PORT STATE” and “PORT ROLE”.

6 – GFP150 CARD


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.

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 BPDUsthat it continues to manage.

• "BACKUP " : The MSTP protocol decided to block transmission on the port to avoid an Ethernet loop. Thisstate indicates the bridge has received its owner frame.

• "LEARNING " : The port is going to transit to "DISCARDING " or "FORWARDING " state depending on theresult of MSTP convergence. No other Ethernet frame than BPDUs are received or transmitted on that portin 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 ofconvergence towards a Tree topology ("Multiple Spanning Tree ") with a node elected as root of the tree ("RootBridge ").

Figure 6-36 : MSTP port types

2

1

Bridge Z(Root)

1

2

3

4

Bridge B

1

2

3

Bridge A

1

Bridge D

1

Bridge C

1

Bridge E

Blocking

DesignatedPort

DesignatedPort

Root Ports

DesignatedPorts

Root Ports

Root Port

DesignatedPorts

Forwarding frames between Root ports and Designated ports

6 – GFP150 CARD


Controlling MSTP convergence

A specific MSTP cost can be configured on every port (port priority), and on every Bridge (Bridge priority) inorder to control the Tree topology of the network during stable phases. At times where there is no link loss onany port, either Ethernet or Ethernet over SDH. Naturally, redundant links blocked by MSTP during stablephases can be unblocked when a link is lost in the network. Later, when the link failure is fixed and the primarylink comes back up, MSTP re-converges towards the stable topology and blocks back the redundant links.

Transparency of MSTP on the GFP150

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 card uses the address : 01-80-C2-00-00-08.

However, the MSTP implementation on the GFP150 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-00-00-0F) foruse by the protocol. Using a different address does not change the MSTP algorithm at all. It is just a way todistinguish the BPDUs sent by the GFP150 card from BPDUs sent by any other Ethernet bridge (which wouldlogically use the standard address).

The GFP150 cards are useful to interconnect client Ethernet LANs across a network provider’s backbone(Ethernet over SDH). There can be cases where the clients themselves would be running STP between theirremote sites. By using a non standard address only known by the ADR155C, the GFP150 card can transportBPDUs 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 inthe client networks. Moreover, the ADR155C 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 thetopology. It is generally useless to activate the operator MSTP on ports connected to client networks.

6.2.5.2 - MSTP Licence Activation on a GFP150 card

The MSTP utilization by the GFP150 card is submitted to a Licence. To activate this Licence, proceed asfollowing :

1) note the GFP150 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 6-37 : MSTP Licence Activation

6 – GFP150 CARD


Note :

An alarm "No MSTP Licence" of card level is activated if at least one port has a MSTP configuration to ON andif the MSTP licence is not activated.The severity of this alarm is major and no configurable.

6.2.5.3 - Example of MSTP configuration

Use the previous example with a bus topology. Just a redundant link between the remote ADR155C 1 and 3 isadded. The final topology works like a ring.

First the 4 ADR155C should be configured according to the instructions of the bus topology section of thisdocument (*). 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 forthis example.

SSDDHH


EEtthh // 44xxVVCC1122EEtthh // 44xxVVCC1122


EEtthheerrnneett 1100//110000EEtthheerrnneett 1100//110000

Site n°3Site n°1

Site n°4Site n°2

Figure 6-38 : Example of MSTP configuration

6 – GFP150 CARD


Bus configuration

See the bus section in this document. (§ 6.2.2.4 -)

Configuring the redundant link between the ADR155C 1 and 3

Configure the VCG#2 port on ADR155C 1 and 3 with the same instructions as for VCG#2 between ADR155C 2and 4.

In the end, ADR155C 1 and 3 must be connected via VCG#2 configured with 6 VC12 and included in the sameVMAN 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 isrunning.

Activating MSTP on ADR155C 2 and 4

Click on the "MSTP" block then on the "Bridge settings " link of the GFP150 card. Set the "MSTP Procotol "parameter at the "MSTP " value and click on "Apply ".

Figure 6-39 : Activating MSTP on the ADR155C 2 and 4 (1)

6 – GFP150 CARD


The default values of fields of the Bridge Configuration screen are those of the 802.1d norm ; to optimize thetimes 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 the802.1s standard.

Click on the "Port Settings " link. Set ports VCG#1 and VCG#2 at the "Enable " value and leave other field atdefault value, then click on "Apply ".

Figure 6-40 : Activating MSTP on the ADR155C 2 and 4 (2)

Activating MSTP on ADR155C 1 and 3

To activate MSTP on cards n°1 and n°3, repeat previous step.

Activating the redundant link

On ADR155C 1 and 3, we turn ON the VCG#2 interfaces :Click on the “VCG” block of the GFP150 and then on the “Settings” link. Set the “Admin Status” of interfaceVCG#2 to “Up” and click on “Apply”.

6 – GFP150 CARD


Once the two interfaces are activated, MSTP starts exchanging BPDUs across the new link and a new state iscalculated. However, after a few seconds each port of this link goes in "BLOCKING " state thanks to thedifference 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" block then on the "MSTI List" link.

Figure 6-41 : MSTI Checking (1)

6 – GFP150 CARD


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 6-42 : MSTI Checking (2)

6 – GFP150 CARD


6.2.6 - Using LCAS on the GFP150 card

6.2.6.1 - Description of LCAS

The GFP150 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 offailures the VCG continues to forward traffic as long as there is still at least one operational VC.

Without LCAS :• The GFP150 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 SDHbackbone point of view. Once both ends of a VCG are configured with LCAS they start exchanging controlinformation 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 VCGfail, 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 acrossthe 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.

6.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 twodifferent SDH paths. The LCAS option is at “Yes” by default.

Configuring the VCG

Click on the VCG block 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 beused to transport Ethernet traffic.

6 – GFP150 CARD


Figure 6-43 : Configuring the VCG (LCAS) (1)

Click on the “Settings” link. Verify that VCG#1 is set with the default configuration: “Admin Status” at “Up”,“LCAS” at “Yes” and “FCS” at “No”. This screen also displays the type of VCG#1 (VC12) and the number ofconstituting VC members (6).


6 – GFP150 CARD


Click on the "Alarms " link. Select interface VCG#1 . Tick option "Monitor " and click on "APPLY " in order tostart monitoring alarms on this port (see Figure 6-9).


Click on the “XCN” block. Configure the connections from VC12#1 to VC12#6 of the GFP150 card in way where3 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 ADR155C.

Figure 6-45 : Configuring the SDH cross-connects (LCAS)

6 – GFP150 CARD


6.3 - A FEW RULES FOR SET-UP

6.3.1 - Various configuration rules

1. The configuration of the Ethernet interface must be identical between the GFP150 card and thetransmission 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 certainequipment.

2. The changes of configuration of VCG interface (LCAS, FCS) must be done when the interface is "OFF "(AdminStatus ticked "down"). The interface is configured to "ON " (AdminStatus ticked "up") whenconfigurations of the 2 extremities of the link are effective. However, when LCAS is activated on a VCGinterface 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 aredirectly taken into account.

3. For each VCG, it is preferable to configure the FCS parameter to "No ".

6.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 thisinterface is configured in 100BaseT or in Auto negotiation, or under 10Mbit/sec if this interface is configuredin 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).

6.4 - APPLICATIONS

6.4.1 - Meshed networks

In topologies of the type "shared LAN", in multipoint to multipoint (EPLAN or EVPLAN), it is necessary to avoidto create Ethernet loops between 2 GFP150 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 theactivation of MSTP- or to activate the "multiple spanning tree " protocol (MSTP).

6.4.2 - Protection of channels

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

6 – GFP150 CARD


6.4.3 - Degraded mode

When a virtual container (VC3 or VC12) used by the GFP150 card is out of service, transmission folds back onVC3/VC12 left (thanks to the LCAS protocol, when activated). In these conditions, transmission over aninterface 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.

6.5 - TECHNICAL CHARACTERISTICS

6.5.1 - Main characteristics

Main characteristics of the GFP150 card in the ADR155C 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 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 forVC3

• 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) aretransparently forwarded. It deviates from the IEEE recommendation for Ethernet bridges. However, thisdesign choice ensures continuity of the "client STP" across remote client sites. Naturally, if MSTP isactivated on the ADR155C, frames received with the address 01-80-C2-00-00-00 (Mac STP address) onMSTP ports will be transparently forwarded because the MSTP of ADR155C 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 § 6.2.5.1 -).

6 – GFP150 CARD


6.5.2 - Ethernet rate / VCG rate

The goal of this chapter is to help the user when configuring VCG regarding Ethernet rates on GFP150 cardinterfaces.

Concerning Ethernet rates :

• The Ethernet rate configured for each interface of the GFP150 card is corresponding to the payloadavalaible 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 4Bytes FCS).

• Knowing there is 12 intergap Bytes between 2 Ethernet frames, which are outside the payload, and 8preamble Bytes per Ethernet frame, which are also outside the payload, when an Ethernet 100 BaseTinterface is used to the maximum of its capacity (end to end frames at 100Mbit/sec), payload rate in100BaseT 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 for1548 Bytes (MTU) frames.

• Because we don’t control Ethernet frames lengths in a link, which may change from frame to frame, wehave to imagine the most critical case, in order to configure the VCG rate for the link. Note the GFP protocoladds an 8 Bytes header (12 Bytes when the GFP FCS is ON), header taken into account in§ 6.5.3 -and § 6.5.4 -

Note that even if we know how to configure, in the case of 100BaseT, a CIR upper than 1 and under 100Mbit/sec (per 1Mbit/sec step) at the customer Ethernet interface (and in the case of the 10BaseT mode a CIRbetween 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 toobtain an Ethernet rate upper 96Mbit/sec.


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 canconsider 4 cases :1. No VC3 used (neither for VCG, nor by another card in ADR155C) : the number of all VC12 used

must be ≤ 63.2. 1 VC3 is used among all the VCG and/or the other cards in ADR155C : the number of all VC12

used must be ≤ 42.3. 2 VC3 are used among all the VCG and/or the other cards in ADR155C : the number of all VC12

used must be ≤ 21.4. 3 VC3 are used among all the VCG and/or the other cards in ADR155C : No VC12 can be used

Of course, if others VC3 and/or VC12 are used for transporting flows coming from other cards inADR155C, it must be taken into account.

Note than all VCG VC3 based in the GFP150 card can’t use more than 2 VC3.

6 – GFP150 CARD


6.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 EMbit/sec at the customer Ethernet interface is :

N = UPPER_ROUND_NUMBER(E*1.125/Dvc12) and N≤46

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 configurePIR=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 correspondingVCG, to configure Ethernet over SDH interfaces CIR/PIR as CIR=PIR=VCG payload.




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 EMbit/sec at the customer Ethernet interface is :



Note that in this case, the customer Ethernet interface remote rate must equals E and we advise to configurePIR=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 correspondingVCG, to configure Ethernet over SDH interfaces CIR/PIR as CIR=PIR=VCG payload.

7 – 4E/FE CARD


7. 4E/FE CARD

The EPLine service proposed by the 4E/FE card can be interconnected with the EPLine and EPLAN servicesproposed by the GFP150 card of the ADR155C and by the GFP150 eXtra card of the ADR2500 eXtra.

Each ADR155C can include up to four 4E/FE cards which must take place in "A", "B", "C" or "D".slots.

Each "ETH #n" port is necessarily associated to the "VCG #n" port.

In case of management by IONOS-NMS, it will always be necessary to create a VMAN associating an ETH#n toa VCG#n.

7.1 - 4E/FE CARD AND SERVICES PRESENTATION

This chapter has for objective to guide the user for the commissioning of the 4E/FE card. It gives simpleexamples which should be easily adapted to the needs.

Service provided by 4E/FE card allows to build an Ethernet LAN between 2 remote sites :

• An EPLine service (Ethernet Private Line) allowing Ethernet 10/100 BaseT point to point interconnectionthrough a SDH network by using, for each connection, a VCG (VC-Group) based on virtual concatenation(VCAT). It’s possible to obtain up to 4 independant point to point connections per 4E/FE card. Rategranularity for each VCG is based either on VC12, or on VC3. With each VCG, it’s possible to concatenatefrom 1 to 46 VC12 or from 1 to 2 VC3. The sum of the concatenated Ethernet rates, on the whole of the 4ETH ports, can’t be above the STM1 payload (about 150Mbit/s).

Ethernet frames are transported on SDH by using the GFP protocol.

7.2 - CONFIGURATION AND APPLICATIONS OF THE 4E/FE CARDS

7.2.1 - 4E/FE card setup

a) Unwrap the card

b) Insert and screw the card in an allowed slot of the shelf.

c) In the HTTP configuration manager, select 4E/FE as expected card on the slot where it was inserted

d) Connect the Ethernet cables to the 4E/FE card

e) Wait a few seconds and check that the green LED “status” is steadily on.

7 – 4E/FE CARD


7.2.2 - Create a LAN interconnect

Point-to-Point connection : “EPLine” service

In the diagram below, one intends to deport a full duplex LAN Ethernet 100 BaseT between 2 sites equipped ofADR155C. In a first time, one supposes that the rate of the Ethernet traffic exchanged between the 2 sitesdoesn't exceed 10Mbps.

EEtthh//VVCC1122

AADDRR 115555CC

AADDRR 115555CC SSDDHH


Figure 7-1 : EPLine service

7.2.2.1 - 4E/FE cards configuration

Login on the first ADR155C to open the “Shelfview” HTTP screen. On this screen, click on the 4E/FE card thenon the “ETH” block.

7 – 4E/FE CARD


Configuring the Ethernet interface

Click on the “Interface Settings” link. By default the Ethernet interface is forced in 100Base T full duplex. Wechoose to keep the default configuration for this example.


Note : The Ethernet interface of the remote equipment (switch, IP router, PC, …) connected to the 4E/FE cardMUST always be configured the same way. Due to possible interoperability issues with Auto-Negotiation between equipments from different origins, this feature (“Automatic” option) shouldpreferably not be used.

This screen is also used to set the severity associated to the interface defect of that interface.

Logical Interface

Logical Interface UNI (User to Network Interface) : this type of interface corresponds to an interface customerwith one service per port. On these interfaces the provider OAM and BPDU MSTP management frames fromGFP150 or GFP150 eXtra cards are not filtered : they are sent to the customer network. Therefore, no OAM orMSTP must be activated on a flow created between a GFP150 or GFP150 eXtra card and a 4E/FE card.

7 – 4E/FE CARD


Link Down Retransmit

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

Pause Mode

The Pause function (IEEE 802.3 Flow control) is used on a point to point/full duplex link constituted of one ETHport and one VCG port.

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 issuspended temporarily

- On detection of traffic obstruction in the sense ETH = > VCG, a pause frame is transmitted on the ETH portto ask the remote equipment to stop the transmission of Ethernet frame temporarily.

Configuring a VCG

Click on the “VCG” block, then on the “List” link. For the selected VCG#1 interface, click on VC#1 and then onthe “Multiple Add Member” link. In the new screen coming up, select “VC12” as type and VC#6 as lastconnection. 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.

4E/FE"LDREnable"

ETH Down Report

Status Down SDHVCG VCG

ETH ETH

Locs + VCG Down

VCG Down Report

VCG Down SDHVCG

VCG Down

4E/FE"LDREnable"

VCG

ETH

4E/FE"LDREnable"

4E/FE"LDREnable" ETH

1

23

4

1

2 23 3

ForcedCut off

Forced Cut off

ForcedCut off

7 – 4E/FE CARD



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


7 – 4E/FE CARD


Logical Interface NNI (Network to Network Interface), untagged : corresponds to a provider interfacewithout provider VMAN tag (no VLAN aggregation).

Click on the « Alarms » link. Select interface VCG#1 . Tick option « Monitor » and click on « APPLY » in order tostart monitoring alarms on this port (see Figure 7-6).


Click on the “XCN” block and configure the connections from VC12#1 to VC12#6 of the 4E/FE card as usual inorder to have end-to-end SDH connectivity with the remote 4E/FE card.


Configuring the remote 4E/FE card

Just do the configuration on the second ADR155C following the exact same steps again.

Activating the end-to-end Ethernet connection

Once both ADR155C systems are configured, the ports used by the Point-to-Point can be activated on eachADR155C.

Click on the “ETH” block, then on the “Interface Settings” link. For interface ETH#1 , tick “ifAdminStatus up” andclick on “Apply”.

7 – 4E/FE CARD


7.2.2.2 - Connectivity check

Perform the following verifications with both 4E/FE cards:

1. Click on the "ETH" block, check that the Ethernet ports in use are not highlighted (the given box would bemarked yellow or red depending on alarm’s severity) ; then click on the "VCG" block and on the "Alarms"link, check that the VCG ports in use are not highlighted (the given box would be marked yellow or reddepending on alarm’s severity). Otherwise click on the alarmed port to go to the proper screen, where thespecific alarm is displayed (this brings you directly to step 2, 3 or 4 below). Repeat the operation for everyalarmed port.

2. Click on the “ETH” block and select Ethernet interface ETH#1. Verify that the interface is running in100BaseT / full duplex and that there is no alarm (the “Fault” option of the Interface Defect Alarm isunchecked). Otherwise double-check both the cables and the configuration of the connected Ethernetinterface.


4. Click on the “VCG” block then on the “Alarms” link, and select the VCG#1 interface. Once configuration iscomplete 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-6 : Connectivity check

Note : This screen can be used to configure the severity of the alarms related to concatenated VC’s.

7 – 4E/FE CARD


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 PC’s 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 4E/FE counters on both ends based on the traffic beingforwarded. 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

7.2.3 - Using LCAS on the 4E/FE card

7.2.3.1 - Description of LCAS

The 4E/FE card enables activation of the standard protocol « Link Capacity Adjustment System » (LCAS)independently on each of the 4 VCGs.

LCAS is useful to :

• Dynamically add or remove VC members from a VCG without deactivating the VCG (making it a hitlessoperation for traffic)

• Dynamically adjust the available bandwidth when alarms are triggered ON/OFF on the VC members of aVCG. The bandwidth of every VC under failure is subtracted from the VCG’s bandwidth. Hence, in case offailures the VCG continues to forward traffic as long as there is still at least one operational VC.

Without LCAS :

• The 4E/FE card requires deactivation of a VCG before VC members can be added or removed (it forces atraffic interruption)

• A VCG becomes completely broken as soon as an alarm is triggered on at least one VC member. Plus, itbecomes 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 SDHbackbone’s point of view. Once both ends of a VCG are configured with LCAS they start exchanging controlinformation 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 VCGfail, 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 acrossthe 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 – 4E/FE CARD


7.2.3.2 - Example of LCAS configuration

We use again the point-to-point connection example described earlier in this document. The VCs just use twodifferent 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 “MultipleAdd 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 (VC#1 to VC#6) that will be used totransport Ethernet traffic.


Click on the “VCG” link and then on the “Settings” link. Verify that VCG#1 is set with the default configuration:“Admin Status” at “Up”, “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).

7 – 4E/FE CARD



Click on the VCG link and then on the « Alarms » link. Select interface VCG#1 . Tick option « Monitor » andclick on « APPLY » in order to start monitoring alarms on this port (see Figure 7-6).


Click on the “XCN” block. Configure the connections from VC12#1 to VC12#6 of the 4E/FE card in way where 3VC12 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 ADR155C.

Figure 7-9 : Configuring the SDH cross-connects (LCAS)

7 – 4E/FE CARD


7.3 - A FEW RULES FOR SET-UP

1. The configuration of the Ethernet interface must be identical between the 4E/FE card and the transmissionequipment 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. For each VCG, it’s preferable to configure the FCS parameter to « No ».

7.4 - APPLICATIONS

7.4.1 - Protection of channels

The VC12/VC3 containers used by the 4E/FE card can be protected by SNCP mechanism as all otherVC12/VC3.

7.4.2 - Degraded mode

When a virtual container (VC3 or VC12) used by the 4E/FE card is out of service, transmission folds back onVC3/VC12 left (thanks to the LCAS protocol, when activated). In these conditions, transmission over aninterface 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 4E/FE card 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 4E/FE card : 1 to 4

• 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)

7 – 4E/FE CARD


• VCG/VC12-nV and VCG/VC3-nV mixity allowed

• Differential delay between VCG containers VC12/VC3 : 47ms maximum for VC12 and 47ms maximum forVC3

• 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.

7.5.2 - Ethernet rate / VCG rate

The goal of this chapter is to help the user when configuring VCG regarding Ethernet rates on 4E/FE cardinterfaces.

Concerning Ethernet rates :

• The Ethernet rate configured for each interface of the 4E/FE card is corresponding to the payload avalaibleat the Ethernet interface.

• This rate is called MTU (64 to 1548 bytes including 6 Bytes @dest, 6 Bytes @src, 2 Bytes lgd trame, and 4Bytes FCS).

• Knowing there is 12 intergap Bytes between 2 Ethernet frames, which are outside the payload, and 8preamble Bytes per Ethernet frame, which are also outside the payload, when an Ethernet 100 BaseTinterface is used to the maximum of its capacity (end to end frames at 100Mbit/sec), payload rate in100BaseT 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 for1548 Bytes (MTU) frames.

• Because we don’t control Ethernet frames lengths in a link, which may change from frame to frame, wehave to imagine the most critical case, in order to configure the VCG rate for the link. Note the GFP protocoladds an 8 Bytes header (12 Bytes when the GFP FCS is ON), header taken into account in§ 7.5.3 -and § 7.5.4 -

Some normal limitations are to be taken into account :


64 Bytes length frames.• 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’s impossible in this case to obtainan Ethernet rate upper 96Mbit/sec.


64 Bytes length frames.

7 – 4E/FE CARD


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 ADR155C) : the number of all VC12 usedmust be ≤ 63.

2. 1 VC3 is used among all the VCG and/or the other cards in ADR155C : the number of all VC12used must be ≤ 42.

3. 2 VC3 are used among all the VCG and/or the other cards in ADR155C : the number of all VC12used must be ≤ 21.

4. 3 VC3 are used among all the VCG and/or the other cards in ADR155C : No VC12 can be used

Of course, if others VC3 and/or VC12 are used for transporting flows coming from other cards inADR155C, it must be taken into account.

Note than all VCG VC3 based in the 4E/FE card can’t use more than 2 VC3.




In point to point (EPLine service), the minimal number N of VC12 necessary for transmitting a rate ofE Mbit/sec at the customer Ethernet interface is :



Note that in this case, the customer Ethernet interface remote rate must equals E.

Example :

• If we suppose E=20Mbit/sec• We obtain N=UPPER_ROUND_NUMBER(20*1.125/2.176)=UPPER_ROUND_NUMBER(10.34)=11 (≤46)

7 – 4E/FE CARD





In point to point (EPLine service), the minimal number N of VC3 necessary for transmitting a rate ofE Mbit/sec at the customer Ethernet interface is :



Note that in this case, the customer Ethernet interface remote rate must equals E.

Example :

• If we suppose E=60Mbit/sec• We obtain N=UPPER_ROUND_NUMBER(60*1.125/48.384)=UPPER_ROUND_NUMBER(1.395)=2 (≤2)

ANNEX A – BUILDING A MANAGEMENT NETWORK

Installation and User Guide - 288 091 808-02 Sagem Communication document. Reproduction and disclosure prohibited Page AA-1

A. BUILDING A MANAGEMENT NETWORK

This appendix provides a brief description of the rules governing construction of atelecommunications management network based on the IP protocol stack.

A.1 - Preliminary remark

The ADR155c management network is based on the IP protocol stack. Each network node(each ADR155c) integrates an IP router which routes each packet to its destination; thesenetwork nodes are connected together by PPP ( Point to Point protocol) link.

A.1.1 - Unique address

Each ADR has an IP address called an "equipment address" (based on release P3.1). Thisaddress must be configured when the ADR is commissioned. This is the only IP address usedby the management system. The ADR must be declared with this address in the manager. Allinformation (alarms, events) concerning the ADR are then notified to the manager with theequipment address.

A.1.2 - Supervision of PPP link

The PPP links (whatever their physical support: DCCr, DCCm, VC12..) are supervised.

A.1.3 - Routing protocols

The ADR155c has two routing protocols, RIP and OSPF (available as of P3.1)The RIP protocol is limited to 16 "hops" in the network. The OSPF protocol enablesmanagement of large sized networks. The OSPF protocol does not require any specialconfiguration; it is always necessary to ensure that all the network elements are in the same"area".

A.1.4 - Unnumbered links

When creating a PPP link, the operator has two choices: either the link is numbered or it isunnumbered. This is independent of the protocol selected (RIP or OSPF). The unnumberedlinks do not have an IP address and therefore more easily enable construction of a network(since there is no need to define all the IP addresses of all the links).

A.2 - Construction of an IP network

Functionally, there are two types of routes: static and dynamic.

A.2.1 - Static routes

In the ADR155c, the static routes are used to configure routes which are not learned by therouting protocols and located "on the periphery" of the protocol areas or domains: routes tomachines on Ethernet network such as manager, for example.

ANNEX A - BUILDING A MANAGEMENT NETWORK

Installation and User Guide - 288 091 808-02Page AA-2 Sagem Communication document. Reproduction and disclosure prohibited

The static routes, as implemented in the ADR155c, have the following characteristics:

• each route is assigned a metric.• each route is assigned a preference. The preference is used to settle conflicts when routes of

different types (static and dynamic) have the same destination.• preference is given to the static routes with respect to the dynamic routes.• the static routes are always exported by the routing protocols to the other equipment.

Depending on whether the interface which the routes take is in the operational state or not, thestatic routes are set up or removed to avoid assignment of non-valid routes.A maximum of twenty static routes is supported by each ADR

Configuration of static routesIn the static tables context, each network node must have its routing table filled in order tocorrectly route the packets received.

All IP routes of a routing table of a given equipment comprise the following fields:

• «destination @IP» : corresponds to the IP address of the equipment or sub-network (ornetwork) to be reached from the given equipment,

• «subnet mask» : this is the sub-network mask associated to the IP address defined in the«destination @IP» ; all equipment with the IP address part defined by the "1" bits of this fieldwhich corresponds to the same value as the «destination @IP» part defined by this samemask can be reached through this route,

• «next hop @IP» : IP address of next equipment (connected directly with given equipment) towhich the packet will be sent,

• «metric» (also referred to as "cost" or distance): value from 1 to 15 indicating the number ofhops to reach the corresponding equipment at the «destination @IP» address. 16corresponds to infinity for the RIP routing daemon. This field is only used by a possiblerouting daemon to select a preferential route if several different routes exist for the samedestination. It is always possible to configure this field for 1 to simplify if use of the field is notindispensable.

• «interf.» : interface number used to reach the next equipment (whose IP address is «nexthop @IP»).

Note: Declaration of the interface IP addresses results in setting up implicit static routes to theassociated SUBNETs. It is therefore not necessary to define static routes to join twoequipments on a single SUBNET.

Note: The IP addresses of an equipment are the addresses of its interfaces (or ports) whichhave been configured. The manager only knows one IP address per equipment. This iswhy reference is often made to the IP address of an equipment to designate the addressconfigured in the manager database. This is the address of the port by which theequipment normally dialogues with the manager.

Note: To operate an equipment via a PC and an Ethernet interface, the IP address of theoperation PC must be modified so that it belongs to the same SUBNET as the Ethernetinterface used to connect to the network.The HOST 1 number on each SUBNET should be left free, i.e. begin to number theequipment starting with the HOST 2 number. The PC will thus always take an IPaddress such as : NET.SUBNET.1

Note: A default router can be defined (option sometimes available) to which all packets whichcannot be routed by the routing table are transmitted.



The figure below gives an example of an IP network and routing tables associated to two typicalequipments. Note that each port of the on-board routing function corresponds to a differentSUBNET.

Example of a telecommunications management network architecture

Ethernet

140.1.1.2

F2

140.1.0.2 140.1.0.3

Ethernet

F3

F4

F5

140.1.1.4

140.1.1.5NET 140 - 1NET 128.1

Ethernet

NET 160.1

Ethernet

NET 150.1

F8 F9 F10

150.1.1.3 150.1.1.4 150.1.1.5

150.1.1.2

128.1.0.1

F7

F6

150.1.0.3

PPP1 150.1.0.2

128.1.0.2

128.1.0.3

F1

140.1.1.3

Fiber

Fiber Fiber

Manager

Configuration of ADR155C F6

Interfaces

Eth 128.1.0.3Subnet mask 255.255.0.0

PPP1 150.1.0.2Subnet mask 255.255.255.0

PPP2 to PPP4 Nothing

Static routes

Dest @IP Subnet mask Next hop Interface Metric Note

140.1.0.0 255.255.0.0 128.1.0.2 eth 1 Entire NET 140.1150.1.1.0 255.255.255.0 150.1.0.3 ppp1 1 Entire SUBNET 150.1.1



Configuration of ADR155C F8Interfaces

Eth 150.1.1.3Subnet mask 255.255.255.0

PPP1 to PPP4 Nothing

Static routes

Dest @IP Subnet mask Next hop Interface Metric Note

128.1.0.0 255.255.0.0 150.1.1.2 eth 2 Entire NET 128.1140.1.0.0 255.255.0.0 150.1.1.2 eth 3 Entire NET 140.1150.1.0.0 255.255.255.0 150.1.1.2 eth 1 Entire SUBNET 150.1.0

A.2.2 - Dynamic routes

Various theoretical cases for a network are described in the sections below.

A.2.2.1 Network 1

This network is the most simple case of an equipment network (starting with release P3.1), all ofwhich are connected by unnumbered PPP links.

Ethernet

ADR 2

ADR 1

ADR 3

ppp Unnppp Unn

ppp Unn

ppp Unn

ppp Unn

Ethernetsub-network

A RIP or OSPF routing protocol is implemented (RIP only if size of network allows).The Ethernet network forms an IP sub-network; the Ethernet interface is thus assigned anaddress in the sub-network.The equipment addresses can be selected in any given way, but not in the Ethernet sub-network.The breakdown of the number of addresses per equipment thus gives:ADR 1 has two addresses (Ethernet address and equipment address), ADRs 2 and 3 each haveone address (equipment address).



A.2.2.2 Network 2

This network has ADRs (starting with release P3.1) and a P1 or P2 equipment.

Ethernet

ADR 2

ADR 1 ADR 3

ppp Unn

ppp Unn

ppp Unn

ppp Num 1

ppp Num 2

ADR 4

FOTC 1

ppp Num 3

sub-network1

sub-network2

sub-network3

sub-network4

This network comprises:• 1 ADR release P1 or P2 : ADR 4• 3 ADRs release ≥ P3 : ADR 1, 2 and 3• 1 FOTC : FOTC 1

The PPP links respectively connecting ADR 4 and ADR 2 and ADR3 must be numbered links.The PPP links between ADR1,ADR2,ADR3 will be preferentially unnumbered links.

Equipment addressing:The Ethernet network forms an IP sub-network.Each of the numbered PPP links forms an IP sub-network.The addresses of ADR 1, 2, 3 (equipment address) can be selected in any given way (but not inthe Ethernet sub-network).

This leads us to define:• A sub-network per numbered ppp link, with each end of the link having a separate address

(sub-networks 3, 4 and 5)• A sub-network for the virtual interfaces of the ADRs connected by an unnumbered link. (1)• A sub-network for the Ethernet network (2).



A.2.2.3 Networks exceeding the limits in number of RIP « hops »

To exceed the RIP constraints (limited to 16 "hops"), the network can be divided into two routingdomains in accordance with the diagram below:

Example of a network separated into 2 RIP routing domains.

Ethernet

Domain 2

Domain 1ADR 1

ADR 2

ADR 0

The overall equipment network is divided into domains (1 and 2) in which the RIP routing isimplemented.The Ethernet network is there to represent the link with the SNMP manager on the PC not usingthe RIP.The two domains are connected via ADR 1 and ADR 2 (which functionally are border routers).

The link between the two border ADRs can be an Ethernet link, numbered PPP or unnumberedPPP.The RIP is not activated on the interfaces of this link connecting the two domains.

Routing between the two domains is made possible by static routes configured in the ADRs.ADR 1 has static routes to the sub-networks forming domain 2 and ADR 2 has routes to the sub-networks forming domain 1.

The static routes to the sub-networks of a domain (2, for example) in the border ADR of theother domain (ADR 1) can be reduced to a single route to a sub-network combining the sub-networks of the domain (2).This global sub-network must be distinct with respect to the sub-networks of the other domain(1, in the example).

Installation and User Guide / Guide d'Installation et d'Utilisation – 288 091 808-02Sagem Communication document. Reproduction and disclosure prohibitedDocument Sagem Communication. Reproduction et divulgation interdites

En cas de difficultés rencontrées lors de l'installation ou de l'utilisation, n'hésitez 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 métropolitaine/in mainland France : 01 40 70 60 60ou depuis l'étranger/or from abroad : 33 1 40 70 60 60

UN SEUL NUMERO DE FAX :ON A SINGLE FAX NUMBER:

en France métropolitaine/in mainland France : 01 40 70 60 80ou depuis l'étranger/or from abroad : 33 1 40 70 60 80

UN SEUL Email :ON A SINGLE Email address:

[email protected]

N'oubliez pas de vous munir de votre numéro de client qui estinscrit sur votre facture.Don't forget to provide yourself with your customer numberwhich is written on your invoice.

Siège social : 27, rue Leblanc - 75512 PARIS CEDEX 15 - FRANCETél. : +33 1 58 11 77 00 - Fax : +33 1 58 11 77 50http://www.sagem.com

Société Anonyme au capital de 300 272 000 € - 480 108 158 RCS Paris

ADR155C UserGuide

Documents

Transcript of ADR155C UserGuide