ADR155C Installation and User Guide
ADR155C Installation and User Guide
ADD-DROP MULTIPLEXER
MULTIPLEXEUR ADD-DROP
à 155 Mbit/s COMPACT
ADR 155C
N56717020103
S
COMPACT 155 Mbit/s
ADD-DROP MULTIPLEXER
ADR 155C
) The 19" subrack must be mounted only in racks with a bottom part that is
closed or fitted with a class V1 or HF1 or better air filter, or that stand on a
non-flammable floor..
) Handling precaution: For any work to be carried out inside the equipment, an
antistatic wrist strap must be worn.
Lithium Battery
1
Safety Extra Low Voltage Circuit
1.1 - General
The ADR 155C is an optical STM-1 add-drop multiplexer used to build STM-1 point-to-point
links, STM-1 rings, or mesh networks with conduct (SNC) or line (MSP) protection, so
performing the conveyance of links at 2 Mbit/s, 34 or 45 Mbit/s, Ethernet, STM-1.
The ADR 155C can be used as:
STM-1 terminal multiplexer with maximum capacity of 63 VC12 and capability of 1+1
protection,
STM-1 repeater, capability of regenerating 2 VC4,
STM1 multiplexer with insertion/extraction, with maximum capacity of 4 STM-1 and
insertion/extraction of 21 VC12,
LAN interconnection point (in exclusive function up to 3 remote links totalling 3 VC3 used).
This equipment is managed from a HTTP navigator:
either locally, via its dedicated Ethernet interface
or remotely by teleoperation
or from the IONOS-ANM network manager; in this last case, using the SNMP protocol also
allows global network supervision.
Using a local terminal with VT100 emulation is necessary on the first commissioning, for the
configuration of communication parameters.
Management network connections are performed via DCC D1 to D3 (or D4 to D12) of the
STM1, via VC12 of the STM1 or on Ethernet (ETH) or P (MNGT) interfaces of the equipment.
The ADR155C is placed in 19" racks or ETSI frames. It consists of:
a 2U subrack fitted with a motherboard grouping together the basic functions of the
equipment, among them 21 G.703 2 Mbit/s access, a backplane and a secured 48V DC
power supply,
an ADRFAN module, consisting of two redundant ventilation units,
four traffic cards, either :
IC1.1 or IC1.2 STM1 optical card (ADR IC1.1 or ADR IC1.2 card) allowing a VC4
connection or 3 VC3 connections or 63 VC12 connections or a combination of VC3/VC12
connections
STM1 electrical card (ADR ERE card) allowing a VC4 connection or 3 VC3 connections
or 63 VC12 connections or a combination of VC3/VC12 connections
Ethernet 10/100 card (ADR LAN1 card), allowing 2 VC3 connections
34/45Mbit/s card (ADR E3DS3 card), allowing 1 VC3 connections
21 x 2 Mbit/s card, G.703, (ADR21E120 card), allowing 21 VC12 connections.
A
V
M
C
Left uprights
of rack
ADR 155C
ADR 155C
ETSI RACK
19" SUBRACK
76,2 mm
76,2 mm
2U
2U
SYNC E1 OUTPUT
SYNC E1 OUTPUT
2 2
Two M6x12 Two M6x12
1 HM screw 1 HM screw
Two M6 Two M6
cage nuts cage nuts
19" rack mounting ETSI rack mouting
The ADR 155C subrack can be installed in 19" rack or ETSI frame (see Figure 1-1). It consists
of:
a motherboard located in the lower part (item M),
four non-dedicated slots (items A to D), designed to accommodate the traffic cards,
a slide located on the left of the subrack designed to accommodate the ventilation module
(item V),
a power supply (item P).
There is no adjustment or configuration to do on the equipment to install. Set-up is operating on
commissioning or by means of built-in operating software.
All connections are performed on front panel, either on the subrack, or on the modules.
Installation of cards
RECALL: Prior to any operation on the cards, the operator must be provided with an
antistatic bracelet.
ADR155C slots are non-dedicated. However, in order to make wiring easier and ensure the
homogeneity among sites, it is advisable to proceed as follows:
position the tributary cards from C clockwise
position the agregate cards from D counter-clockwise
check the ventilation module presence in its reserved slide,
secure each card through M3 screws of Torx type (6-branch star), using a suited screwdriver
FACOM reference AZX.10X75
Or STANLET reference 1-67-494
Connection requirements :
For a right distribution of cords on either side of the subrack, the connections of slots A and
C, the 21 2Mbit/s accesses and synchronization access are oriented leftward. All other
connections are oriented rightward.
The run of cords must not hinder the extraction of a module; in particular, connecting
cables of the left subrack half is to be secured to the frame with enough backlash to
enable the ventilation module to be extracted during a maintenance operation.
"PWRA" and/or "PWRB" ports, when the equipment is powered from one or two 48 V
sources, the power source(s) should be limited to 100 VA.
. "PWR" port when the equipment is powered from a mains voltage (230 V AC), via an
optional 110-240//48V 60W/ transformer.
"PWR" and "PWRA" and/or "PWRB" Power supply ports can be connected simultaneously.
The power cord or the 110-240//48V 60W/ transformer must not be connected to the primary
source prior to being connected to the equipment.
The 110-240//48V 60W/ transformer must be mounted far from any heat source, and no
traction must be exerted on its connecting wires.
POWER
- 48V
2A MAX
"PWR" Jack type connector
ADR-155C
Figure 1-2 – Connecting power supply ports
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
5 1
9 6
LOOPS
8 1
15 9
1 : Break B
2 : Make B 9 : Common B
3 : Common A 10 : Break A
4 : Gnd 11 : Make A
"SYNC" 5 : R-MON 4 N 12 : R-MON 4 P (OB)
6 : R-MON 3 N 13 : R-MON 3 P (OB)
5 1 7 : R-MON 2 N 14 : R-MON 2 P (OB)
9 6 8 : R-MON 1 N 15 : R-MON 1 P (OB)
1 : GND Schematic diagram
2 : TX1_TIP 6 : TX1_RING of a dry loop
3 : RX1_TIP 7 : RX2_TIP
4 : RX2_RING 8 : RX1_RING MC B
5 : RESERVED 9 : RESERVED
"MNGT"
1 : TX_ETH_TIP 5 : NC
5 1 2 : TX_ETH_RING 6 : RX_ETH_RING
9 6 3 : RX_ETH_TIP 7 : NC
COMM 4 : NC * 8 : NC
1 : GND
5 1
2 : RXPA 6 : RXPB Right LED : link status
3 : TXPA 7 : TXPB 9 6 ON : correct link
Ports 4 remote indication inputs for floating contacts (Local user inputs),
biased to -48 V internally, active when closed and with electrical
isolation (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),
Connector Female 15-way HE5
8 1
15 9
"COMM" Interface:
5 1
9 6
Wiring diagram
1 1
6 6
9
5 9
5
"ETH" Interface:
Front view
7 TXPB (+) Output for data sent over the P interface on the falling edge of
3 TXPA (-) transmit clock TXCLKP (B-A)
8 TXCLKPB (+) Output for transmit clock; in codirectional mode, the transmit clock
4 TXCLKPA (-) timing is derived from the equipment's internal timing
TXCLKP (B-A)
(codirectional transmit
clock output)
TXP (B-A)
(output for data transmitted B8 B1 B2
over P interface)
RXCLKP (B-A)
(receive clock input)
RXP (B-A)
(input for data received B8 B1 B2
over the P interface)
"SYNC" Interface
Ports Two G.703 2MHz external synchronization inputs (T3) and one
G.703 2MHz clock output (T4) compliant with ITU-T G.703
Recommendation (§ 10.3 for input port, § tab.10 for output port)
Impedance 120 Ω balanced,
Connector Female 9-way HE5 (120 Ω).
5 1
9 6
NOTA : The shielding of the connector case is connected to the subrack front panel ground
This interface uses two connectors : E1 INPUT connector for inputs (named RX) and
E1 OUTPUT connector for outputs (named TX)
15 1
30 16
44 31
NOTA : The shielding of the connector case is connected to the subrack front panel ground
ADR IC1
Version 1
ADR IC1.1
LED STATUS 8 1
Green Red 15 9
NC: Reserved
Version 2
10 TOFPB (+) Transmit mode byte sync output indicating the positioning of bit 1
3 TOFPA (-) and sent on the rising edge of clock T64 (B-A)
11 RB (+) Output for data extracted from STM-1 line and sampled on the
4 RA (-) falling edge of clock T64 (B-A)
12 ROFPB (+) Receive mode byte sync output indicating the setting of bit 1 and
5 ROFPA (-) sent on the falling edge of clock T64 (B-A)
Timing diagram for the "EOW/AUX" interface in contra-directional mode (64 kbit/s synchronous
use):
T64 (B-A)
(transmit clock output)
T (B-A) B8 B1 B2
(input for data to transmit
over STM1 line)
TOFP (B-A)
(transmit synchro byte
pulse output)
R64 (B-A)
(receive clock output)
R (B-A)
(output for data received B8 B1 B2
from STM1 line)
ROFP (B-A)
(receive synchro byte
pulse output)
As EOW and AUX ports are physically integral with ADR IC1.x, operating the order wire and
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.
Likewise, in order to ensure a good behaviour during the changeover from one module to the
other, the operator should take care to keep identical configurations on both ADR IC1.x cards ;
in case 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.
ADR ERE
LED STATUS 8 1
Green Red 15 9
NC: Reserved
ADR LAN1
LED STATUS
HALF/FULL
Green Red
Yellow LED : Ethernet interface type
ON OFF Card in service (Half or Full Duplex)
ON ON Card in alarm
OFF OFF Hardware default (fuse) ON : Full duplex
OFF ON Card out of service
Flashing Autotest default
ETH 10/100
Contact 1 Contact 8
Yellow LED : Ethernet interface bite rate
"ETH" Interface :
Front view
ADR E3DS3
STATUS DS3 E3
TR REC 45 34
2 Mbit/s traffic connections, performed on "E1 INPUT" and "E1 OUTPUT" ports on the
ADR21E120 card are identical with those performed on "E1 INPUT" and "E1 OUTPUT" ports
on the front side of the motherboard (see § 1.3.2.5)
ADR 21E120
LED STATUS
"E1 OUTPUT" and "E1 INPUT"
Green Red
15 1
30 16
ON OFF Card in service 44 31
ON ON Card in alarm
OFF OFF Hardware default (fuse)
OFF ON Card out of service 16 : GND
Flashing Autotest default 1 : Tx(Rx) 1A 17 : Tx(Rx) 2B 31 : Tx(Rx) 1B
2 : Tx(Rx) 3B 18 : Tx(Rx) 3A 32 : Tx(Rx) 2A
3 : Tx(Rx) 4A 19 : Tx(Rx) 5B 33 : Tx(Rx) 4B
4 : Tx(Rx) 6B 20 : Tx(Rx) 6A 34 : Tx(Rx) 5A
5 : Tx(Rx) 7A 21 : Tx(Rx) 8B 35 : Tx(Rx) 7B
6 : Tx(Rx) 9B 22 : Tx(Rx) 9A 36 : Tx(Rx) 8A
7 : Tx(Rx) 10A 23 : Tx(Rx) 11B 37 : Tx(Rx) 10B
8 : Tx(Rx) 12B 24 : Tx(Rx) 12A 38 : Tx(Rx) 11A
9 : Tx(Rx) 13A 25 : Tx(Rx) 14B 39 : Tx(Rx) 13B
10 : Tx(Rx) 15B 26 : Tx(Rx) 15A 40 : Tx(Rx) 14A
11 : Tx(Rx) 16A 27 : Tx(Rx) 17B 41 : Tx(Rx) 16B
12 : Tx(Rx) 18B 28 : Tx(Rx) 18B 42 : Tx(Rx) 17A
13 : Tx(Rx) 19A 29 : Tx(Rx) 20B 43 : Tx(Rx) 19B
14 : Tx(Rx) 21B 30 : Tx(Rx) 21A 44 : Tx(Rx) 20A
15 : GND
5 1
9 6
SYNC
15 1
30 16
44 31
E1 OUTPUT
15 1
30 16
44 31
E1 INPUT
t 21
Por
t1
Por
t1
Por
Tx
LOCAL TEST
Equipment Inventory
- 48 V power Check
- 48 V redundancy Check
* case of underequipped
Local transmission test (30 mn) *
unitary equipment
Optical connection
Configuration Elaboration
yes
Link established
Optical measurements
Counters reset
24 H link Performance
Equipment operational
(constitution of installation file)
Configuration Save
1.4 - Commissioning
NOTE: The equipment can be operated from a PC fitted with VT100 emulation and HTTP navigator;
its minimum configuration is defined in section 1.4.1.
A local terminal with VT100 emulation is indispensable during the first commissioning, in
order to be able to access the equipment via the management function; however, this
terminal only enables the communication function to be parameterized.
Procedure.
On the first commissioning, the equipment scans its constitution and considers it as the
expected configuration, in service, monitored. It is thus advisable to insert the traffic cards
before power-up, in order to speed up the commissioning.
REMARK: The first commissioning is normally made in factory.
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.1).
Using the HTTP navigator, (see § 1.4.3).
Update the equipment time and date
Connect the 2 Mbit/s, 34/45 Mbit/s, Ethernet, STM1 or SYNC ports, according to the
required equipment composition,
Connect the AUX and EOW ports required.
Download a predefined configuration or prepare the desired configuration, using the HTTP
navigator:
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 configuration parameters and the alarm configuration.
The default configuration of the various parameters is provided by § 2.1.1.
Conduct the tests on STM-1 links, complying with the process described in Figure 1-10.
From that moment, the equipment is operational.
Operating alarms can signal a wrong connection of interfaces. Check the connection of
ports, the alarms corresponding to the connected ports, and correct any problems that may
arise.
Save configuration.
REMARK: It is possible, once the commissioning is performed, to connect additional 2 Mbit/s G.703,
E3/DS3, Ethernet or STM1 ports, and to insert or extract powered cards.
IONOS ANM
D1 - D3
D1 - D3
STM1
STM1
on West
on East
D1 - D3 STM1
HTTP on East
E P
ADR T
H
R P
P
D1 - D3 STM1
SNMP on West
IONOS ANM in necessary
to operate this FOT C D1 - D3 D1 - D3 D1 - D3
(but the ADR cannot be on STM1 STM1 STM1
operated from the ETH tributary on East on West
interface of the FOT C
PP P
FOT C * S H
D1 - D3
N T
on STM1
aggregate M R T
ADR
E P P P
T
H
R P
P
ETH
SNMP
1
Registered trademark of Microsoft Corporation
2
Registered trademark of Nescape Communications Corporation
Installation and User Guide - N56717020103
No reproduction or communication without the written consent of SAGEM SA Page A1-25
1 - INSTALLATION AND COMMISSIONING
Open a session and enter your password (to setup the communication function, it is
indispensable to have "supervisor" rights).
NOTE : By default, on the first commissioning, the password is empty.
To select a command, type the command number in "Choice ?" text zone, and press "ENTER"
key to validate your choice.
The screen displays the 5 communication interfaces possible, with their characteristics, and
proposes to change each of them by turns. These interfaces are:
- an Ethernet port –ETH
- 4 PPP (Point to Point Protocol) ports – PPP1 to PPP4 - Each PPP is either :
one DCCr channel (D1 to D3) of an STM1 frame
one DCCm channel (D4 to D12) of an STM1 frame
(DCC are named DCCr/m-A, DCCr/m-B, DCCr/m-C or DCCr/m-D according to the number
and position of ADR IC1.x (or ADR ERE) modules in the equipment),
one VC12 channel among 2 (P#1 and P#2 channels of the motherboard supported by two
VC12 (TU12) of an ADR IC1.x or ADR ERE module)
the MNGT port (V11, local)
Each interface is defined by its characteristics:
"Port" : physical port "ETH", "PPP1" to "PPP4"
"Admin" or interface state: "ON" (interface active) or "OFF" (interface inactive)
"@ IP" : IP address
"subnet mask" : subnetwork mask (the finest mask is 255.255.255.252)
"@ IP of dest" : destination IP address (for PPP ports only)
"Path" : management path chosen for the PPP ports (DCCr, DCCm, P#1, P#2 or MNGT)
"RIP" : management routing self-adaptability to the network structure validated or not (limited to
16 hops without gateway)
Setup is backed up port by port.
The screen displays the already defined management routes with their characteristics:
"No" : reference of the route
The routing domain value tells the RIP routing function which autonomous system is belongs to.
Only routing tables coming from the same routing domain shall be taken into account when the
routing function establishes its current routing table. Routing domain processing is deactivated if
routing domain value is set to 0. Routing tables will then be learnt whatever routing tag is
received.
This screen is used to view the routing table, to list the dynamic and/or static routes and also
the interface configurations
Note : For the PPP interfaces using a VC12 management channel, SOH field indicates either
connected VC12 at matrix level or '…' if no VC12 has been connected ; in the example
above, P#1 is connected to A#1, P#2 isn't connected.
On session opening on the HTTP navigator, the "ADR155C shelf view" represents the
equipment global view, where each slot is marked with a letter, A, B, C, D or M according to
Figure 1-1.
LOGIN
2. OPERATION
2.2 - General
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 HTTP navigator,
- or from a network manager, using the SNMP protocol.
Configuration parameters
NOTE : The functional blocks naming, configuration parameters and their default value, noted
"XXXXXX", are displayed on HTTP navigator.
"TIMdis" TIM (Trace Identifier Mismatch) enable or disable Clicked (no TIM)
LUG : Lower order path Unequipped Generator
Number of the unequipped VC12s transmitted in TUG3s "FFH"
(by default no connection)
LPOM : Lower order path overhead monitor
Signal label (VC12) received:
- "Label Rec".
Signal label (VC3) received:
- "Label Rec".
SD threshold : configurable from 10-5 to 10-9 for VC3
configurable from 10-5 to 10-9 for VC12
"SD threshold" "10-6"
LPC : Lower order Path Connection
Connection switch Not put into
service
Connection name (configurable according to M.1400 §13) No name
Type : bi-directional / unidirectional MONO
SNC protection
Type SNC/I
Protection mode MONO
Revertive authorization (path by path) : return after a WTR time-delay to
the working link when the fault (SF or SD) causing the switch has
disappeared.
"Revertive" "no"
Wait Time to Restore (WTR) period (common to all paths): in revertive
mode, period following restoration of nominal operation ; configurable
from 0 to 15mn in one-second steps
"WTR" "1 mn"
"Overhead Avoidance" :
Fan is ON, if T°> 35°C (95°F), fan is OFF, if T° ≤30°C (86°F)
Equipment
Session
Equipment Name Empty
Synchronization
The synchronisation of the local equipment and remote equipment is managed according to the
available synchronization sources, their quality and the priority they are allocated.
The synchronization sources possible are:
standalone operation (local oscillator),
T1 extracted from one of the incoming STM1 streams (1 to 4 possibilities according to the
number of ADRIC1.x cards present in the equipment),
T2 : one 2 Mbit/s G.703 source per declared 2 Mbit/s module, and selected from the various
2 Mbit/s G.703 accesses
T3 : two external 2 MHz G.703 sources
2 MHz external
sync input (T3):
- Quality = PRC,
- Priority = 1.
STM-1port (T1-C): STM-1port (T1-C):
- Quality = DNU - Quality = DNU
- Priority = 2. - Priority = 2.
ADR155C 1 ADR155C 2
ADR155C 3 Synchronization
of other equipments
SSM = PRC
T0 = T1-c
Synchronization
of other equipments
Figure 2-1 - Synchronization from the 2 MHz external sync input (T3)
ADR155C 3 Synchronization
of other equipments
SSM = SEC
T0 = T1-c
Synchronization
of other equipments
NOTE : Synchronization is applied to the 2 Mbit/s port of the ADR155C which is enabled first
(local ADR155C in the example).
Loops Management
On remote sites, two local outgoing loops (Local user outputs A and B) are activated on the
appearance of a local equipment alarm or remote indication loops 3 and 4 (Local user input #3
or #4).
The remote loopback function allows an equipment named "central site", to register faults
present on remote sites.
This function requires each site to transmit to the central site an alarm presence message. This
messages 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 A
and B loops (Local user outputs A and B) should be connected to remote monitoring loops 1
and 2 (Local user input #1 or #2) respectively.
Data chaining in a bus or ring type network architecture is provided by "OR" function validation
between the data received (Far user inputs #1 et #2) via S1 STM1 West and S1 STM1 East,
and local data, for each site in the network.
At the "central site" equipment, "OR" function validation between the data received (Far user
inputs #1 and #2) via S1 STM1 West and S1 STM1 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 following figure gives an example of remote
management of the local outgoing loops according to the equipment connections.
NOTE 2: Status of incoming loops (Local user inputs #1 to #4), far incoming loops (Far user
inputs #1 to #2) and outgoing loops (Local user outputs A and B) may be displayed on
HTTP navigator.
LEDs :
Monitored Designation Comment Status Meaning
item
Motherboard "ON" Green On In service card
Flashing Self-test default
Off Not powered equipment or not
run software
"ALA M" Red On Major alarm
"ALA m" Yellow On Minor alarm
Ethernet "Activity" Left On On tranmission
(management port Off No traffic
or ADR LAN card) "Link" Right On Correct Link
Off No link
Traffic cards "STATUS" See table below
ADR E3DS3 card "DS3-45/ On 34 Mbit/s mode activated
E3-34" Off 45 Mbit/s mode activated
"STATUS" LEDs on ADR IC 1.x, ADR ERE, ADR LAN, ADR E3DS3 and
ADR 21E120 cards :
Green LED Red LED Meaning
On Off Card in service
On On Card in service and in alarm
Off Off Hardware default on card (fuse)
Off On Card out of service
Flashing Self-test default
Pushbuttons :
Designation Location Role Action initiated
"ACK" Front panel Alarm Pressing disables the outgoing alarm
acknowledge loops. The visual alarm is kept.
"INIT Motherboard Configuration "Factory" Configuration reload
CONFIG"* reload
*: To activate "INIT", keep button pressed for at least 5 seconds. This button is
inaccessible (and unused) in normal operation. It is necessary to remove the cover to
access it.
Correlation of faults
A correlation mechanism is implemented on all faults detected.
This correlation mechanism, implemented on each change of information collected, is used to
eliminate 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 current
column.
For example: The LOF fault is masked by fault 2 (LOS).
FAULTS 1 2 3 4 5 6
FAULTS TF LOS LOF AIS SD-B2 RDI
1 TF
2 LOS
3 LOF X
4 AIS (MS-AIS) X X
5 SD-B2 X X X
6 RDI (MS-RDI) X X X
FAULTS 1 2 3
FAULTS PAM SCM OTM
1 PAM
2 SCM X
3 OTM X
Correlation of AU faults
The AU faults are masked by the STM1 LOS, LOF and AIS (MS-AIS) faults.
The TU-LOM fault is filtered, if there is no configured VC12 connection on this STM1.
FAULTS 1 2 3 4 5 6 7 8
FAULTS AU-AIS AU-LOP UNEQ RDI SLM TU-LOM TIM SD-B3
1 AU-AIS
2 AU-LOP
3 UNEQ (VC4 UNEQ) X X
4 RDI (VC4 RDI) X X X X
5 SLM X X X X
6 TU-LOM X X X X X
7 TIM X X X
8 SD-B3 (VC4) X X X
FAULTS 1 2 3 4 5 6
FAULTS TU-AIS TU-LOP LP-UNEQ LP-RDI LP-SLM LP-SD
1 TU-AIS
2 TU-LOP
3 LP-UNEQ X X
4 LP-RDI X X X
5 LP-SLM X X X
6 LP-SD X X
FAULTS 1 2
FAULTS LOS AIS
1 LOS
2 AIS X
Alarms appear whenever a card is extracted from the subrack. In order to prevent feedback
of M/m 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 the
equipment.
1. Put the card concerned "no service" from HTTP navigator.
2. Remove the external connections performed on the card front side.
NOTE: When the external optical fibers are disconnected, reinstall the protective
covers on connectors.
3. Screw off the TORX screws located on the front side, using the suited screwdriver and
unplug 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 well
tight 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.
7. Carefully insert the card into its cell, complying with the measures of protection against
electrostatic discharges, and secure it with the TORX screws.
8. Restore connections on the card front side.
NOTE: For the optical STM1 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.
Procedure:
1. Screw off the TORX screws located on the front side, using the suited screwdriver and
unplug 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 well
tight 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 against
electrostatic discharges, and secure it with TORX screws
1. Disconnect the power cable or the 110-240//48V 60W/ transformer from the primary power
source.
2. Screw off the fuse-holder from the power supply front panel.
3. Replace the defective fuse with an equivalent fuse, namely:
4A quick-break fuse (HA214A)
Dimensions length: 20mm ± 0.5
diameter: 5.2 mm +0.1/-0.2
4. Screw the fuse-holder.
5. Reconnect the power cable or the 110-240//48V 60W/ transformer to the primary power
source
3. SPARE PARTS
Traffic card
External transformer
ETH port
Ethernet port on mother board or ADRLAN1 card
Right cable male – male *
Right cable male – male * 1.5 m 55 670 421
Crossover cable male – male ** 3m 55 670 422
Right cable male – female 3m 55 670 610
Right cable male – female 1.5 m 55 670 423
3m 55 670 424
LOOPS port 2.5 m 6 013 628
Remote indication, remote control and station alarm 5m 6 013 261
loops 12 m 6 013 161
25 m 6 013 262
POWER port 1.5 m 55 670 796
Power supply 3m 55 670 797
4. SPECIFICATIONS
EQUIPMENT
Optical specifications
Interface type IC1.1 = L1.1 + S1.1 or IC1.2 = L1.2 + S1.2
Bit rate 155.520 Mbit/s ± 20 ppm
Standard ITU-T G.957/G.958
Encoding Not encoded (NRZ)
Optical fiber Single-mode (1 300 nm (IC1.1) or 1 550 nm (IC1.2),
ITU-T G.652)
* : It is possible to use a multi-mode optical fiber
whose diameter is smaller than or equal to 62.5
microns
Guaranteed attenuation 0 - 28 dB with no external attenuator
Typical range 0 - 60 km (IC1.1) or 0 - 90 km (IC1.2)
Connector All-ceramic FC/PC
Mechanical specifications
Height 2U
Width 19" or ETSI
Depth 300 mm
Weight 6 kg approx.
Protection Class (IP) Corresponding to the IP of the rack used
Consumption < 40 W (to a equipped subrack of two cards
(see details below) ADR IC1.x and two cards ADR LAN)
Environmental specifications
Mechanical ETS 300 119-4 (19") or CEI 297-3 (ETSI)
ETS 300 019-2-3
Climatic conditions CEI 721-1 (1993)
ETS300 019 part 1-3, class 3.1, 3.2
Operating temperature range - 5 °C à + 45°C
Extended operating temperature - 25 °C to + 55°C (the MTBF [Mean Time Between
range Failure] is significantly degraded)
Packaged transportation and - 40°C to + 70°C
storage temperature
Relative humidity < 85%
ESD NF EN 50081-1,
NF EN 50082-1 June 1992
and ETS 300 386-1 1994
EMC (Electromagnetic NF EN 55022 (1994)
Compatibility) + Additive A1 02/1996 equipment Class B
Safety NF EN 60950 and UTE C 92130
(the equipment does not provide the fire envelope)
Energy ETS 300132-2
(is VLV equipment)
Predicted reliability *
Motherboard 3.4 10-6
ADR 21E120 card 0.75 10-6
ADR1 IC1.x card 2.6 10-6
ADR ERE card 1.2 10-6
ADR E3DS3 card 0.75 10-6
ADRLAN1 card 2.25 10-6
Background 0.33 10-6
Power supply 1.25 10-6
ADRFAN Module 2.5 10-6
* The predicted reliability computations are based on the CNET's 1993 issue (RDF 93) of the
Reliability Data Manual, on the assumption of specific requirements for the following:
ambient temperature 25°C (with ventilation conditions such as the subrack internal middle
temperature is less than 40°C), environment (mounted on the ground, fixed and protected),
qualification, and component ageing. Any changes in the above requirements may entail
variations in the results.
* These power consumptions are typical values and may be used for dissipation evaluation. It
is necessary to add 20% to estimate peak values which determine power rack capacity. This
allows to take into account the dynamic power variations and the converter efficiency
variations according to total power supply.
Warning : It is necessary to add another 10% when powered by 72V supply.
This annex summarizes the rules for constructing a TMN based on the IP protocols suite.
A.1 - Preamble
The IP protocols suite enables the transport of data in a transmission network in the form of
packets between two points in the network.
According to the ISO model, IP is the network layer protocol. It is therefore responsible for the
packet routing of each node, so that the packets can be routed correctly via the network.
The protocols "below" IP correspond to the link and physical layers: they set up the links
between two consecutive network nodes.
The protocols "above" IP, TCP and UDP, are the transport layer protocols: they enable end-to-
end data transmission between two remote points on the network. The protocols based on
TCP/UDP are application oriented: they offer services such as file transfer (TFTP over UDP,
FTP over TCP), equipment management (SNMP), messaging (SMTP), etc...
The figure below describes the stacking of the main protocols that can be used in a network
node.
To download To OS
HTTP Server mechanism functions
TCP UDP
ICMP IP
Ethernet EOC
IP protocol suite
Note: The MAC protocol is linked to the Ethernet physical port (point-multipoint media) and
PPP protocol is linked to the physical ports for the point-to-point links (optical, radio,
V11 , etc...)
A.2 - Addressing IP
All IP routes of a given equipment routing table contains the following fields:
Rem : The declaration of interface IP addresses induces the establishment of implicit static
routes to associated SUBNETs. So, it is not necessary to define static routes to join two
equipments of the same SUBNET.
Rem : The equipment IP addresses are the addresses of its configured interfaces (or ports).
The manager knows only one IP address per equipment. So, IP address of an
equipment is frequently used to refer to the address filled in the manager database.
This is the address of the port through which the equipment interacts normally with
manager.
Rem : To operate an equipment via a PC and an Ethernet interface, it is necessary to change
the IP address of the operating PC for the PC to belong to the same SUBNET as the
Ethernet interface that is used to be connected to the network.
It is advisable to leave HOST 1 number free on each SUBNET, i.e., to start numbering
the equipments from HOST 2 number. Thus, the PC will always take an IP address of
this type: NET.SUBNET.1
Note: If it is possible to define a default router (option sometimes available), to which any
packet may be transmitted which cannot be routed using the routing table.
The following figure shows an example of an IP network and routing tables associated with two
equipment types. It shall be noted that each port of the onboard routing function corresponds to
a different SUBNET.
140.1.1.3
F3
140.1.0.2 140.1.0.3 140.1.1.2
Fiber 140.1.1.4
SNMPC F1 F2
128.1.0.1 Ethernet
128.1.0.2 F4
Ethernet 140.1.1.5
NET 128.1 128.1.0.3
NET 140 - 1 F5
F6
PPP1 150.1.0.2
Fiber Fiber
SUBNET 150.1.0
150.1.0.3
F7
150.1.1.2
Ethernet Ethernet SUBNET 150.1.1
ADR155C F6 Configuration
Interfaces
Eth 128.1.0.3
Sub network Mask 255.255.0.0
PPP1 150.1.0.2
Sub network Mask 255.255.255.0
Static routes
Dest @IP Subnet mask Next hop Interface Metric Remark
ADR155C F8 Modification
Interfaces
Eth 150.1.1.3
Sub network Mask 255.255.255.0
Static routes
Dest @IP Subnet mask Next hop Interface Metric Remark
"RIP" is a routing demon which makes it possible to dispense with part of the static routing
tables.
The network must be divided into "AUTONOMOUS SYSTEMS" or "AS", each with a different
"NET" number.
Each AS is an RIP routing domain and must be limited to a length of 15 hops max. between two
equipment pieces requiring to exchange packets within this AS. The maximum distance is taken
into account to include the worst case security.
These ASs are mutually independent (within RIP), and are linked via isolated networks each
constituting a single link (Ethernet or point-to-point). Each isolated network has its own "NET"
number.
The equipment interfaces belonging to an isolated network must be filtering (RIP filtering option
activated on these interfaces), i.e., they prohibit export of automatic updates of RIP routing
tables. These equipment pieces with a filtering interface are designated "border".
Within an AS, all equipment pieces must have their RIP routing demon activated.
Within each AS, each link between two equipment pieces is described by a specific "SUBNET"
value.
The routings from one AS to another AS, via an isolated network, are described using static
routes.
In the example given above, "NET" 128.1 corresponds to an isolated network and "NETs" 160.1
and 150.1 correspond to ASs in which RIP is activated.