ADR Manual

Altium ADR
Add-Drop Multiplexer
TM
Installation and Operation Manual
PN 567-170201-003 Rev.
Copyright 2001 by DMC Stratex Networks. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, electronic, magnetic, optical, chemical, manual or otherwise, without the prior written permission of DMC Stratex Networks.
Printed in the United States of America. Disclaimer DMC Stratex Networks makes no representation or warranties with respect to the contents hereof and specifically disclaims any implied warranties or merchantability or fitness for any particular purpose. Further, DMC Stratex Networks reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of DMC Stratex Networks to notify any person of such revision or changes.
This equipment has been tested for and meets EMC Directive 89/336/EEC. The equipment was tested using screened cabling. If any other type of cable is used, it may violate compliance. CE Mark This equipment has been designed to meet the requirements of the European Electromagnetic Compatibility Directive 89/336/EEC (currently amended by 92/31/EEC). Operation of the equipment is designed to provide reasonable protection against harmful interference in its electromagnetic environment without introducing intolerable electromagnetic disturbances. Trademarks FibreNex and Altium are trademarks and DMC Net is a registered trademark of DMC Stratex Networks. All other product names are trademarks or registered trademarks of their respective companies.
DMC Stratex Networks 170 Rose Orchard Way San Jose, California 95134-1358 U.S.A. Telephone: (408) 943-0777 Telex: 759597 DIGMIC Fax: (408) 944-1801 www.dmcwave.com DMC Stratex Networks Middlemarch Business Park Siskin Drive Coventry, England CV3-4JA Telephone: + 44-1203-863838 Fax: + 44-1203-530126 DMC Stratex Networks 10 Ang Mo Kio Street 65 #03-13 Techpoint Singapore 569059 Telephone: + 65-484-7780 Fax: + 65-484-7768
Ports Security Level

The following table lists port safety levels for the 19" subrack access.
Connectors on the Front Panel PWRA/PWRB PWR Motherboard SYNC E1 INPUT & E1 OUTPUT MNGT COMM ETH LOOPS ADR ICI 1.x Card TR and REC EOW and AUX ADR ERE Card TR and REC ADR LAN1 Card ETH ADR E3DS3 Card TR and REC ADR 21E120 Card E1 INPUT & E1 OUTPUT G.703 2 Mbit/s Ports SELV 34 or 45 Mbps ports SELV Ethernet Port SELV STM-1 electrical ports SELV G.957 and G.958 STM-1 IC1.1 or IC1.2 Optical Engineering Order Wire
Laser class 1
Function Power supply Power supply
Security Level SELV1 SELV
G.703 2 Mbit/s synchronization Ports G.703 2 Mbit/s Ports Other equipment connection VT100 local supervision Ethernet LAN remote supervision Loops and remote signaling
SELV SELV SELV SELV SELV SELV
No Danger SELV
1. SELV = Safety Extra Low Voltage circuit
Caution:
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. This equipment must be installed only by skilled personnel. For compliance, the protective grounding (earth) terminal must be connected to a safe ground (earth) with an impedance Z of less than 5 Ohms. Before working inside the equipment, wear an antistatic wrist strap.
W arning:
Replacing the lithium battery incorrectly could result in explosion. Only authorized personnel at DMC Stratex Networks Product Support Center may replace this component. Dispose of all used batteries according to manufacturers instructions.
Declaration of Conformity I hereby declare that the product:

Altium ADR
(Name of product, type or model, batch or serial number)
satisfies all the technical regulations applicable to the product within the scope of Council Directives 73/23/EEC, 89/336/EEC and 99/5/EC:
Altium 6GHz STM-1-EN 300 234, ETS 300 385, EN 60 950. Altium 7/8GHz STM-1- EN 300 234, ETS 300 385, EN 60 950. Altium 13 GHz STM-1-EN 300 234, ETS 300 385, EN 60 950. Altium 15GHz STM-1-EN 300 234, ETS 300 385, EN 60 950. Altium 18GHz STM-1-EN 300 430, ETS 300 385, EN 60 950. Altium 23GHz STM-1-EN 300 198, ETS 300 385, EN 60 950. Altium 26GHz STM-1-ETS 300 431, ETS 300 385, EN 60 950. Altium 28GHz STM-1-ETS 300 431, ETS 300 385, EN 60 950. Altium 38GHz STM-1-EN 300 197, ETS 300 385, EN 60950. (Title(s) of regulations, standards, etc.)
All essential radio test suites have been carried out.
NOTIFIED BODY: TUV Produktservice GmbH Address: Ridlerstrasse 65 80339 Munchen Germany (Notified body: 0123) MANUFACTURER or AUTHORISED REPRESENTATIVE: Address: DMC Stratex Networks 170 Rose Orchard Way San Jose CA 95134 USA
This declaration is issued under the sole responsibility of the manufacturer and, if applicable, his authorised representative.
Point of contact:
Stuart Little, +1 408 943 0777 (Tel), +1 408 943 1678 (Fax)
(Name, telephone and fax number)
San Jose, 22 March 2001

(Place, date of issue) (Signature) Stuart Little, Director of Product Marketing (Name and title in block letters)
000-000085-FRM-A
Intended Use of Equipment

The Altium radio is classified under the R&TTE Directive 99/5/EC as a class 2.8 radio (microwave fixed link) product. Point-to-point radio relay equipment is intended to be used for interconnecting typically private and public networks and for interconnecting mobile base stations back to the PSTN point of presence (POP). Altium equipment operates in fixed bands between 6 GHz and 38 GHz and is available in capacity STM-1. For details of where the equipment is intended to be used, refer to the Country matrix below. A licence to operate this apparatus is likely to be necessary and the appropriate regulatory administration should be contacted.
Luxembourg
Netherlands
Switzerland
Germany
Denmark
Portugal
Sweden
Belgium
Norway
Greece
Finland
Austria
France
Ireland
Spain
Italy
Altium 6GHz STM-1 Altium 7/8GHz STM-1 Altium 13GHz STM-1 Altium 15GHz STM-1 Altium 18GHz STM-1 Altium 23GHz STM-1 Altium 26GHz STM-1 Altium 28GHz STM-1 Altium 38GHz STM-1
X X X
X X X X
X X X X X X X X X
X X
X X X X
X X X
X X X X
X X X X X X X X X
X X X X X X
X X X X X X X
X X X X X X X X X
X X X X X X X X
X X X X X X X X X X X X
X X X X X X X X X
X X X X X X X
X X X X X
X X X X X
X X
X X X X X
X X X X X
X X X
X X X
X X
X X
Note: The information contained in this document has been gathered from the relevant government authorities and relates only to European countries participating in the R&TTE Directive.
UK
X X X X X X X X X
Contents
Chapter 1Installation and Commissioning Overview ...................................................................................................................... 11 Subrack Installation ...................................................................................................... 14 Installation of a 19" Rack ......................................................................................... 14 Installation of an ETSI Rack .................................................................................... 14 Installation of Cards ................................................................................................. 15 Connecting Ports ........................................................................................................... 15 Connection Requirements ........................................................................................ 15 Connecting Power Supply Ports .............................................................................. 16 Connection Requirements ................................................................................. 16 Connecting Motherboard Inputs .............................................................................. 19 Remote Indication, Remote Control, and Station Alarm Ports ("LOOPS")...... 19 Management and Administration Ports ........................................................... 110 X24/V11 2 Mbps traffic port ........................................................................... 112 G.703 2 Mbps Synchronization port ............................................................... 115 G.703, 21 x 2 Mbps traffic port ....................................................................... 115 Connecting on the ADR IC1.x Card ...................................................................... 117 Connecting STM-1 interface ........................................................................... 117 Connecting Order-Wire Channels ................................................................... 118 Connecting with MSP Operation..................................................................... 121 Connecting on the ADR ERE Card ........................................................................ 123 Connecting on ADR LAN1 Card ........................................................................... 124 Connecting an ADR E3DS3 Card .......................................................................... 125 Connecting an ADR 21E120 Card ......................................................................... 126 75 W Connecting Strip ........................................................................................... 127 Commissioning ........................................................................................................... 129 Configuration Required .......................................................................................... 131 Using HTTP Navigator .......................................................................................... 136 First Commissioning ....................................................................................... 136 Navigator Presentation .................................................................................... 137 Chapter 2Operations Functional Description ................................................................................................. 21 General .......................................................................................................................... 22 Operational Parameters ................................................................................................. 22 Configuration Parameters ........................................................................................ 22 Predefined Functions .................................................................................................. 211 Synchronization ..................................................................................................... 211 Loops Management ................................................................................................ 214 Alarms Processing ...................................................................................................... 215 LEDs and Pushbuttons ........................................................................................... 215 Defaults and Alarms ............................................................................................... 217 Correlation of Faults .............................................................................................. 219
PN 300-610012-001 Rev. 1c, April 2001
vii
Altium Microwave Radio System
Correlation of STM-1 Faults ........................................................................... 220 Correlation of MSP faults................................................................................ 220 Correlation of AU faults .................................................................................. 220 Correlation of TU/VC Faults........................................................................... 220 Correlation of Port Faults ................................................................................ 221 Correlation of Remote Faults .......................................................................... 221 Performance Processing ............................................................................................. 221 For Local Equipment ............................................................................................. 221 For Remote Equipment .......................................................................................... 221 Determination of ES, SES and UAS Performance States ...................................... 222 Procedure for Replacing Subassemblies ................................................................ 224 Replacing a Card ............................................................................................. 224 Replacing the Fan Module............................................................................... 224 Replacing the Front-Panel Fuse....................................................................... 225 Chapter 3Spare Parts Available Cable List ..................................................................................................... 32 Chapter 4Specifications Equipment ..................................................................................................................... 41 Optical Specifications .............................................................................................. 41 Mechanical Specifications ....................................................................................... 41 Consumption ............................................................................................................ 41 Environmental Specifications .................................................................................. 42 Predicted Reliability* ............................................................................................... 42 Sub-assemblies Consumption .................................................................................. 42 Transformer 110-240//48v 60W/ (OPTIONAL) ...................................................... 43 Appendix AConstructing an IP Network Addressing Plan Overview ..................................................................................................................... Addressing IP .............................................................................................................. Addressing Plan ........................................................................................................... Use of Static Tables ..................................................................................................... Use of RIP Routing Demon ......................................................................................... A1 A2 A3 A4 A6
viii
PN 300-610012-001 Rev. 1c, April 2001
Chapter 1 Installation and Commissioning
Overview
The Altium ADR 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, that performs the conveyance of links at 2 Mbps, 34 or 45 Mbps, Ethernet, and STM-1. The Altium ADR can be used as a: STM-1 terminal multiplexer with maximum capacity of 63 VC12 and capability of 1+1 protection STM-1 repeater, capability of regenerating 2 VC4 STM-1 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 three remote links totaling 3 VC3 used)
The Altium is managed from a HTTP navigator in one of the following ways: Locally, through its dedicated Ethernet interface Remotely From the ProVision Network Management System (the ProVision Systems SNMP protocol also allows global network supervision)
A local terminal with VT100 emulation must be used the first time the system is commissioned to configure the communication parameters. Management network connections are performed through DCC D1 to D3 (or D4 to D12) of the STM-1, through VC12 of the STM-1, or on Ethernet (ETH) or P (MNGT) interfaces of the equipment.
N 56717020103 Rev. 1c, April 2001
11
Altium ADR
The Altium ADR is installed in 19" racks or ETSI frames. The rack consists of: A 2U subrack fitted with a motherboard grouping that includes 21 G.703 2 Mbps access, a backplane, and a secured 48V DC power supply A FAN module, consisting of two redundant ventilation units Five traffic cards, including a:
IC1.1 or IC1.2 STM-1 optical card (ADR IC1.1 or ADR IC1.2 card)
allowing either a VC4 connection, 3 VC3 connections, 63 VC12 connections, or a combination of VC3/VC12 connections
STM-1 electrical card (ADR ERE card) allowing a VC4 connection, 3

VC3 connections, 63 VC12 connections, or a combination of VC3/VC12 connections
Ethernet 10/100 card (ADR LAN1 card) allowing 2 VC3 connections 34/45Mbps card (ADR E3DS3 card) allowing 1 VC3 connections 21 x 2 Mbps card, G.703, (ADR 21E120 card) allowing 21 VC12
connections
12
N 56717020103 Rev. 1c, April 2001
Chapter 1Installation and Commissioning
Figure 1-1. Altium ADR Subrack Installation
N 56717020103 Rev. 1c, April 2001
13
Altium ADR
Subrack Installation
The Altium ADR subrack can be installed in a 19" rack or ETSI frame (see Figure 1-1). The subrack consists of: A motherboard (item M) Four non-dedicated slots (items A to D) to accommodate the traffic cards A slide located on the left of the subrack to accommodate the ventilation module (item V) A power supply (item P)
There is no adjustment or configuration necessary to install the equipment. Set-up is operating on commissioning or by means of built-in operating software. All connections are performed on the front panel, either on the subrack, or on the modules.
Installation of a 19" Rack

The hardware needed to install the ADR 19" subrack (brackets, cage nuts, and attaching screws) are included in its package. The ADR has a thermal control ventilation system; during the installation, provide for sufficient space for the ventilation aperture on the left of the subrack, and also for aeration at the top and right of the subrack. Do not block the natural air convection on the right side. Perform the following operations: 1. Provide a 2U place in the rack for each equipment and a 1U space between equipments. 2. Secure the attaching brackets for mounting in 19" rack, on either side of the subrack. 3. Clip, on either side of the rack, two M6 cage nuts (item 1). 4. Position the 19" subrack back in front of the rack. 5. Slide the 19" subrack until attaching brackets are in contact with uprights, opposite the four cage nuts, and then secure the subrack with four M6x12 hex head screws (item 2).
Installation of 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.
14
N 56717020103 Rev. 1c, April 2001
Installation of Cards
Note: An antistatic bracelet must be worn when working with cards.
The Altium ADR slots are non-dedicated. However, to make wiring easier and ensure the homogeneity among sites: Position the tributary cards from C clockwise. Position the aggregate cards from D counterclockwise. Check the ventilation module presence in its reserved slide. Secure each card with M3 Torx-type (6-branch star) screws using a FACOM reference AZX.10X75 or STANLET reference 1-67-494screwdriver.
Connecting Ports
The connections to be performed on the equipment depend on the configuration chosen: On the power supply card: Poser supply ports: "PWR" or "PWRA" and/or "PWRB"
On the subrack motherboard strip: Remote indication, remote control and station alarm port : "LOOPS" Management ports : "COMM", "ETH" and/or "MNGT" X24/V11 2Mbps traffic port : or "MNGT" 2Mbps.703 synchronization port : "SYNC" 21x2Mbps G.703 traffic ports: "E1 INPUT" and "E1 OUTPUT"
Depending on the traffic modules used Optical or electrical STM-1 ports and order wire channels ports Ethernet port 34 or 45 Mbps traffic ports 21x2Mbps G.703 traffic ports
Connection Requirements
A right distribution of cords on either side of the subrack, the connections of slots A and C, the 21 2Mbps 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.
N 56717020103 Rev. 1c, April 2001
15
Altium ADR
Connecting Power Supply Ports

"PWRA" and/or "PWRB" ports, when the equipment is powered from one or two 4 8V 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.
Connection Requirements
"R" 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 before 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.
Figure 1-2. Connecting Power Supply Ports
"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 Connector 100 VA maximum Male 9-way HE5
5 9
1 6
16
N 56717020103 Rev. 1c, April 2001
Pin N 1 6 2 7 3 8 4 9 5 Note:
Signal Name -48B1 OB1 -48B1 OB1 Reserved OB2 -48B2 OB2 -48B2
The connector shielding is connected to the equipment ground.
"PWR" Power Supply Interface

Port Connector Connecting transformer 110-240//48V 60W/ Jack (core = OB1 and shield = - 48 V1)
N 56717020103 Rev. 1c, April 2001
17
Altium ADR
Figure 1-3. Connecting Motherboard Inputs
18
N 56717020103 Rev. 1c, April 2001
Connecting Motherboard Inputs

Remote Indication, Remote Control, and Station Alarm Ports ("LOOPS")
"LOOPS" Interface
Ports Four 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) Two dry loop outputs (common, normally closed and normally open) (Local user outputs) for station alarm or remote control use (maximum current = 10 0mA on resistive load) Connector Female 15-way HE5
8 15 1 9
Pin N 1 9 2 10 3 11 4 12 5 13 6 14 7 15 8
Signal Name
Comments Normally closed contact of dry loop B
COMMON B MAKE B Break A COMMON A Make A GND R- MON 4 P (OB*) R-MON 4 N R- MON 3 P (OB*) R- MON 3 N R- MON 2 P (OB*) R- MON 2 N R- MON 1 P (OB*) R- MON 1 N
Common contact of dry loop B Normally open contact of dry loop B Normally closed contact of dry loop A Common contact of dry loop A Normally open contact of dry loop A Ground User input N4
User input N3
User input N2
User input N1
Note: OB is the result of a logical "OR" between signals OB1 and OB2 on the "PWR", "PWRA" and "PWRB" power supply interfaces.
N 56717020103 Rev. 1c, April 2001
19
Altium ADR
Management and Administration Ports

"COMM" Interface:
Ports Bit Rate Connector RS232, connecting VT100 standard console or emulation 19200 bauds (8 data bits, no parity bit and 1 stop bit) Female 9-way HE5
5 9 1 6
Pin N 1 6 2 7 3 8 4 9 5
Signal Name DCD DSR RX RTS TX CTS DTR RI GND
Comments Connected to DSR Data Set Ready (to DCE)* Received data (to DCE)* Request To Send (from DCE)* Transmitted data (from DCE)* Clear To Send (to DCE)* Data Terminal Ready (from DCE)* Ring Indicator (not connected) Ground
* The ADR is seen as DCE.
Figure 1-4. Connection Cable
110
N 56717020103 Rev. 1c, April 2001
"ETH" Interface:
Port Ethernet management interface operating at 10 Mbps in half-duplex or full-duplex mode according to the mode used by the interlocutor (dynamic adaptation of the Ethernet port on each new log-in of the interlocutor) RJ48 Type (RJ45 shielded)
Pin 1 Pin 8
Connector
Front view
Pin N 1 2 3 4 5 6 7 and 8 Note:
Signal Name TX_ETH_TIP TX_ETH_RING RX_ETH_TIP NC NC RX_ETH_RING NC
Comments Output (hot point) Output (cold point) Input (hot point) Reserved Reserved Input (cold point) Reserved
Two LEDs are linked to the "ETH" port:
Left LED, "Activity": Right LED, "Link":
Traffic status indicator Link status indicator
"MNGT" Interface (configured in management use) :

Port V.11 synchronous (differential) interconnection possible with other equipment through serial synchronous links used in codirectional mode at 64 Kbps or master contra-directional mode (rate defined by the ADR) 64 Kbps Female 9-way HE5.
5 9 1 6
Bit rate Connector
Pin N 1 6 1
Signal Name GND RXPB GND
Polarity Ground (no connected) (+)
Comments
Input for data received over the P interface and sampled on the rising edge of receive clock RXCLKP (B-A) Ground (no connected)
N 56717020103 Rev. 1c, April 2001
111
Altium ADR
Pin N 6 2 7 3 8 4 9 5
Signal Name RXPB RXPA TXPB TXPA TXCLKPB TXCLKPA RXCLKPB RXCLKPA
Polarity (+) (-) (+) (-) (+) (-) (+) (-)
Comments Input for data received over the P interface and sampled on the rising edige of receive clock RXCLKP (B-A) Output for data sent over the P interface on the falling edge of transmit clock TXCLKP (B-A) Output for transmit clock; in codirectional mode, the transmit clock timing is derived from the equipment's internal timing Receive clock input
*In slave contradirectional mode (coming) TXCLK signals are inputs.
Figure 1-5 shows the timing diagram for the "MNGT" interface in codirectional mode (64 Kbps synchronous use).
Figure 1-5.
MNGT Interface Timing Diagram
X24/V11 2 Mbps Traffic Port

"MNGT" Interface (configured in traffic use):
Port V.11 synchronous (differential), ADR interconnection with data terminal equipments (routers) through 2MHz clock X24/V11 link. The ADR is always seen as DCE. 2048 Kbps Female 9-way HE5 Cable equipped with female 15-way HE5 connector 30 m with recommended 120 ohms twisted pairs cable
Bit rate Connector Standard connection Adapter Guaranteed range
112
N 56717020103 Rev. 1c, April 2001
9-way connector pin out

9 pts Pins MNGT Designation GND 6 2 7 3 8 4 9 5 RXPB RXPA TXPB TXPA TXCLKPB TXCLKPA RXCLKPB RXCLKPA I I O O O O O O (+) (-) (+) (-) (+) (-) (+) (-) X24/ V11 direct. Polarity Nom X24/ V11 G T(B) T(A) R(B) R(A) S(B) S(A) I(B) I(A) Comments 15 pts Pins corresp 8 11 4 9 2 13 6 12 5
Ground (not connected) Input for data received and sampled on either edge of S(B-A) according to V11 length cable Output for data sent on the rising edge of transmit clock S (B-A) This clock signal is used by the terminal to transmit T(B-A) and sample R(B-a) and sample T(B-A) This correct connection indication is permanently forced to active the ADR 155C.
15-way connection adaptation pin out

15 pts Pins 1 9 2 10 3 11 4 12 5 13 6 14 7 15 8 G Ground X24 Designation SHIELD T(B) T(A) C(B) C(A) R(B) R(A) I(B) I(A) S(B) S(A) X/B(B) X/B(A) Transmit (+) Transmit (-) Control (-) Control (-) Receive (+) Receive (-) Indication (-) Indication (-) Signal element timing Signal element timing Byte timing Byte timing Not connected 2MHz clock giving junction rate Optional circuit not connected Circuit forced to Active LOS detection circuit not used by the ADR 155C Function Comments
N 56717020103 Rev. 1c, April 2001
113
Altium ADR
G.703 2 Mbps Synchronization port

"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) 120 balanced, Female 9-way HE5 (120 )
5 9 6 1
Impedance Connector
Pin N 1 6 2 7 3 8 4 9 5 Note:
Signal Name GND TX1 RING (T4-) TX1 TIP (T4+) RX2 TIP (T3+) RX1 TIP (T3+) RX1 RING (T3-) RX2 RING (T3-) NC NC
Comments Ground Output T4-1 (cold point) Output T4-1 (hot point) Input T3-2 (hot point) Input T3-1 (hot point) Input T3-1 (cold point) Input T3-2 (cold point) Reserved Reserved
The shielding of the connector case is connected to the subrack front panel ground.
G.703, 21 x 2 Mbps traffic port

"E1 INPUT" and "E1 OUTPUT" Interface
ports 21 x 2 Mbps traffic ports compliant with the ITU-T G.703 Recommendation ( 6.3 for input port, tab.6 for output port) 2,048 Mbps 50 ppm HDB3 120 balanced SUB D HD female 44 pins supporting L907 cable (21 ports)
Bit rate Code Impedance Connector
This interface uses two connectors : E1 INPUT connector for inputs (named RX) and E1 OUTPUT connector for outputs (named TX)
15 30 44 1 16 31
114
N 56717020103 Rev. 1c, April 2001
Pin N 16 31 1 17 32 2 18 33 3 19 34 4 20 35 5 21 36 6 22 37 7 23 38 8 24 39 9 25 40 10 26 41
Ports
Signal Name GND
Comments ground Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point)
TX(RX) 1B TX(RX) 1A
TX(RX) 2B TX(RX) 2A
TX(RX) 3B TX(RX) 3A
TX(RX) 4B TX(RX) 4A
TX(RX) 5B TX(RX) 5A
TX(RX) 6B TX(RX) 6A
TX(RX) 7B TX(RX) 7A
TX(RX) 8B TX(RX) 8A
TX(RX) 9B TX(RX) 9A
10
TX(RX) 10B TX(RX) 10A
11
12
13
14
15
16
TX(RX) 16B
N 56717020103 Rev. 1c, April 2001
115
Altium ADR
Pin N 11 27 42 12 28 43 13 29 44 14 30 15
Ports
Signal Name TX(RX) 16A
Comments Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Output (Input) 2 Mbps (hot point) Output (input) 2 Mbps (cold point) Ground
17
18
19
20
21
TX(RX) 21B TX(RX) 21A GND
NOTA :The shielding of the connector case is connected to the subrack front panel ground
Connecting on the ADR IC1.x Card

Each ADR IC1.x module provides connection for: An STM-1 optical interface ("TR" transmission port and "REC" reception port) Two order wire channels at 64 Kbps (named "EOW" and "AUX"), which, by default, are conveyed in E1 and F1 bytes of the SOH, respectively ; others SOH bytes can be selected for carrying EOW orderwire. See details on table 2-6.
Connecting STM-1 interface

Remove the contact protection connector, Connect STM-1 interface to front panel FC/PC connectors: Transmission: Reception: TR Connector REC Connector
"TR" and "REC" ports:

Interface type Bit rate Standards Encoding Optical fiber* IC 1.1 = L 1.1 + S 1.1 or IC 1.2 = L 1.2 + S 1.2 155.520 Mbps 20 ppm ITU-T G.957/G.958 Not encoded (NRZ) Single mode (1300 nm (IC1.1) or 1550 nm (IC1.2), ITU-T G.652)
Transmit optical power -5 to 0 dBm
116
N 56717020103 Rev. 1c, April 2001
Max. receive power Sensibility at 10-10 Typical range Connector

*
0 dBm - 34 dB 0 - 60 km (IC1.1) or 0 - 90 km (IC1.2) all ceramic FC/PC
Guaranteed attenuation 0 - 28 dB with no external attenuator
It is possible to use a multi-mode optical fiber with diameter smaller than or equal to 62.5 microns. The optical budget is then reduced to 25 % of the optical budget obtained with a mono-mode optical fiber. The transmission optical fiber is mono-mode type and the reception optical fiber is multi-mode type.
Connecting Order-Wire Channels

"EOW" and "AUX" Interface:
Portt Bit rate synchronous V.11 (differential) 64 Kbps
N 56717020103 Rev. 1c, April 2001
117
Altium ADR
Figure 1-6. Connecting ADR IC1.x Card Inputs
118
N 56717020103 Rev. 1c, April 2001
Connector
Female 15-way HE5

8 15 1 9
Pin N 1 9 2 10 3 11 4 12 5 13 6 14 7 15 8
Signal Name TB TA TOFPB TOFPA RB RA ROFPB ROFPA R64B R64A T64B T64A -
Polarity Not connected (+) (-) (+) (-) (+) (-) (+) (-) (+) (-) (+) (-) Not connected Ground
Comments
Input for data to send over the STM-1 line and sampled on the rising edge of clock T64 (B-A) Transmit mode byte sync output indicating the positioning of bit 1 and sent on the rising edge of clock T64 (B-A) Output for data extracted from STM-1 line and sampled on the falling edge of clock T64 (B-A) Receive mode byte sync output indicating the setting of bit 1 and sent on the falling edge of clock T64 (B-A) 64 kHz receive clock output
64 kHz transmit clock output
Figure 1-7 shows the timing diagram for the "EOW/AUX" interface in contra-directional mode (64 Kbps synchronous use).
N 56717020103 Rev. 1c, April 2001
119
Altium ADR
Figure 1-7.
EOW/AUX Interface Timing Diagram
Connecting with MSP Operation

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.
120
N 56717020103 Rev. 1c, April 2001
Figure 1-8.
Y Cord
Likewise, in order to ensure a good behavior 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.
N 56717020103 Rev. 1c, April 2001
121
Altium ADR
Connecting on the ADR ERE Card
Figure 1-9. Connecting ADR ERE Card Inputs Each ADR ERE module provides connection for: An STM-1 electrical interface ("TR" transmission port and "REC" reception port) Two order wire channels at 64 Kbps (named "EOW" and "AUX"), which, by default, are conveyed in E1 and F1 bytes of the SOH, respectively ; others SOH bytes can be selected for carrying EOW orderwire. See details on table 2-6.
"TR" and "REC" ports:

Bit rate Standard Encoding Electrical level Tnsmit optical power Attenuation Input adaptation Attenuation Connector 155.520 Mbps 20 ppm ITU-T G.703 12, CMI 1V 0,1V c to c -5 to 0 dBm 12,7 dB in f at 78MHz 15 dB between 8MHz and 240MHz BNC 75 ohms 1.6/5.6 75 ohms (with BNC - 1.6/5.6 adapter)
"EOW" and "AUX" Interface:

See Connecting Order-Wire Channels on page 1-18 and Connecting with MSP Operation on page 1-21.
122
N 56717020103 Rev. 1c, April 2001
Connecting an ADR LAN1 Card
Figure 1-10. Connecting ADR LAN1 Card Input
"ETH" Interface :
Port Traffic Ethernet interface operating at 10 or 100 Mbps in half-duplex or full- duplex mode according to the mode used by the interlocutor (manual or dynamic adaptation of the Ethernet port on each new log-in of the interlocutor) Ethernet 10 or 100 BaseT - RJ48 Type (Shielded RJ45)
Pin 1 Pin 8
Connector
Front view
N 56717020103 Rev. 1c, April 2001
123
Altium ADR
Pin N 1 2 3 4 5 6 7 and 8 Note:
Signal Name TX_ETH_TIP TX_ETH_RING RX_ETH_TIP NC NC RX_ETH_RING NC
Comments Ethernet output (hot point) Ethernet output (cold point) Ethernet input (hot point) Reserved Reserved Ethernet input (cold point) Reserved
Two LEDs are linked to the "ETH" interface:
Left LED, "Activity": Traffic status indicator Right LED, "Link": Link status indicator
Electrical characteristics compliant with the IEEE 802.3U
124
N 56717020103 Rev. 1c, April 2001
Connecting an ADR E3DS3 Card
Figure 1-11. Connecting an ADR E3DS3 Card Input
"TR" and "REC" Ports :

Ports 75 ohms 34/45 Mbps Interface compliant to ITU-T G.703 (5 and 8) Recommendation and ETS 300 166 allowing 34 Mbps or 45Mbps plesiochronous stream exclusive connection BNC 75 ohms 1.6/5.6 75 ohms (with BNC - 1.6/5.6 adapter)
Connector
N 56717020103 Rev. 1c, April 2001
125
Altium ADR
Connecting an ADR 21E120 Card

2 Mbps traffic connections, performed on "E1 INPUT" and "E1 OUTPUT" ports on the ADR 21E120 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)
Figure 1-12. Connecting an ADR 21E120 Card Input
126
N 56717020103 Rev. 1c, April 2001
75 Connecting Strip
The 75 connecting strip is supplied with element attaching in 19" rack.. Secure connecting strip on the rack uprights, above or under the ADR shelf, Plug in respectively 'E1 INPUT', 'E1 OUTPUT' and 'SYNC' connectors on the connectors (120 ) with the same name in the ADR 155C shelf, Make 75 connections:
(TX) 1 to 21 transmission port : connecting strip upper line, (RX) 1 to 21 reception port : connecting strip lower line, SYNC (TX and RX) port : two connectors on the right side of the
connecting strip.
Figure 1-13. 75 Connecting Strip
N 56717020103 Rev. 1c, April 2001
127
Altium ADR
Figure 1-14. Commissioning Procedure for Altium ADR Network
128
N 56717020103 Rev. 1c, April 2001
Commissioning
Note: The equipment can be operated from a PC fitted with VT100 emulation and HTTP navigator; its minimum configuration is defined in the following section.
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 configured.
Procedure
1. 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.
Note: The first commissioning is normally made in the factory.
2. 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). 3. Configure the communication interface, using the VT100. 4. Using the HTTP navigator, update the equipment time and date. 5. Connect the 2 Mbps, 34/45 Mbps, Ethernet, STM-1 or SYNC ports, according to the required equipment composition, 6. Connect the AUX and EOW ports if required. 7. 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 configure its parameters if
required.
Change, if necessary, the configuration parameters and the alarm

configuration.The default configuration of the various parameters is provided in Table 2-1. 8. Conduct the tests on STM-1 links, complying with the process described in Figure 1-10. 9. From that moment, the equipment is operational. 10. 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. 11. Save configuration.
N 56717020103 Rev. 1c, April 2001
129
Altium ADR
Note:
It is possible, once the commissioning is performed, to connect additional 2 Mbps G.703, E3/ DS3, Ethernet or STM-1 ports, and to insert or extract powered cards.
Figure 1-15. Communication Function Configuration Examples
130
N 56717020103 Rev. 1c, April 2001
Configuration Required
The minimum configuration proposed for the operating PC is as follows:
Description Processor Memory Display Interface Operating system Applications
Configuration 1 266 MHz Pentium 32 MB
Configuration 2
64 MB
800x600, 256 colors (1024x768 recommended) Serial RS232 interface Ethernet 10 base T network card Windows 95/98 HyperTerminal for Windows HTTP navigator: Internet Explorer1 5.0 or Netscape Communicator2 4.5 Windows NT4
1. Registered trademark of Microsoft Corporation 2. Registered trademark of Netscape Communications Corporation
Configuration of the Communication Function

Figure 1-11 presents the available resources and various configurations possible for the communication function : 1. Connect "COMM" port of the equipment to a "COM" port not used on the PC with VT100 emulation, 2. Power the PC on, 3. Start the Hyper Terminal application. 4. on the first use, connect "COMM" port of the equipment to a "COM" port not used on the PC, 5. power the PC on. 6. select, in succession, from Windows desktop, the Start, Programs, Accessories and HyperTerminal command buttons, 7. choose the icon representative of the HyperTerminal application. A description window for the connection appears. 8. give a name for the connection and validate your choices. A new window appears 9. Choose that PC "COM" port which is connected to the equipment and validate your choice,
N 56717020103 Rev. 1c, April 2001
131
Altium ADR
10. a new window appears; configure the port parameters as indicated below and validate the programming : Bits per second: Data bits: Parity: Stop bits : Flow control: 19200, 8, no parity 1 none
11. Save the connection (Save command in the application File menu).
Note: On the next opening of "HyperTerminal" application, choosing the connection icon will be enough to be logged on the equipment. On the equipment power-up, the operating menu appears.
To exit the "HyperTerminal" application, select Quit command from File menu. 12. 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.
The following menu appears:
13. To select a command, type the command number in "Choice ?" text zone, and press "ENTER" key to validate your choice.
132
N 56717020103 Rev. 1c, April 2001
Choice "1" : Configuration of communication interface,
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) portsPPP1 to PPP4 - Each PPP is either:
One DCCr channel (D1 to D3) of an STM-1 frame One DCCm channel (D4 to D12) of an STM-1 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" : sub network 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)
N 56717020103 Rev. 1c, April 2001
133
Altium ADR
"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. Choice "2" : Configuration of static routes,
The screen displays the already defined management routes with their characteristics: "No" : reference of the route "destination @ IP" : destination IP address (equipment or sub network) "subnet mask" : sub network mask "next hop @ IP" : IP address of the next equipment (connected on line with the given equipment) "interface" : interface used to reach the next equipment "cost" : or "metric", number of hops to reach the destination. From this screen, it is possible to change the existing routes, to delete them or to create new ones (the static routing is necessary for an interconnection with a contiguous network).
134
N 56717020103 Rev. 1c, April 2001
Choice "3" : Display of routing domain
The routing domain value tells the RIP routing function which autonomous system it 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 the routing domain value is set to 0. Routing tables will then be learnt whatever routing tag is received. Choice "4" : Display of routing information,
N 56717020103 Rev. 1c, April 2001
135
Altium ADR
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.
Choice "5" : equipment REBOOT, This command is used to perform immediate application REBOOT and to restart with the parameters already stored in the equipment . Choice "6" : Logout With the configuration being complete, this command closes the current session. An automatic session exit is performed after a few minutes of inactivity (time configurable from the manager).
Using HTTP Navigator

First Commissioning
The PC is connected via Ethernet. 1. Start the NETSCAPE application 2. On the Welcome screen, fill in the "Address" field with the IP address of the ADR equipment.
Note: With NESCAPE 4.5, the equipment IP address should include no non-significant '0'. Example: "http://135.11.9.30/" instead of "http://135.11.09.30/"
136
N 56717020103 Rev. 1c, April 2001
If a screen with a 860 x 600 resolution is used, reduce character to obtain correct pages display (for example, 'synchronization' page must display 3' 'Apply' buttons. The navigator welcome screen "Welcome to the ADR 155C's site" appears. On the first commissioning, the password is empty; click on Apply to access "ADR 155C shelf view" screen. From that moment, the navigator is operational.
Navigator Presentation
On session opening on the HTTP navigator, the "ADR 155C 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.
This screen is used to view the equipment status, in particular : inconsistencies between configuration and composition: each slot includes the name of the expected card (top, left) and the name of the inserted card (in the middle, red colored if necessary) frame of module is red in the case of insertion alarm (Missing, Mismatch detective) elements inside in-alarm modules are framed red in the case of a major alarm, yellow for a minor alarm, modules configured out of monitoring are represented grayed, present modules configured out of service include a red cross to signal this administrative status, Absent modules configured out of service appear as all blank panel.
N 56717020103 Rev. 1c, April 2001
137
Altium ADR
This screen is also used to: activate the common functions of the equipment, such as the synchronization, safety, traffic information, etc. by clicking on a function in the menu bar; see tree structure of the general menu, Figure 1-12. access the functionalities related to a module in particular (for example, MSP protection in the case of an ADR IC1.x module) : click on the module to be selected, the selection arrow is blinking and its specific menu appears; see the tree structure of "card" menus in Figure 1-12; 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, active parameters and alarm states are grouped together on the same screen, with the various actions possible being accessible or not by the operator according to his/her clearance level. The upper edge of the navigator window recalls the equipment IP address, the clearance level acquired and, if required, the slot concerned.
138
N 56717020103 Rev. 1c, April 2001
Figure 1-16. Menu Structure
N 56717020103 Rev. 1c, April 2001
139
Altium ADR
140
N 56717020103 Rev. 1c, April 2001
Chapter 2 Operations
Functional Description
The Altium ADR is an optical STM-1 add-drop multiplexer used to build STM-1 point-to-point links, STM-1 rings, or mesh networks, allowing the transport of links at 2 Mbps, Ethernet or STM-1. The Altium ADR can also be connected to an equipment of the synchronous digital hierarchy in accordance with ITU-T recommendations G.707 and G.783. The Altium ADR is modeled in functional blocks according to standard G.783 presented below:
SPI: SDH Physical Interface RST: Regeneration Section Termination MST: Multiplex Section Termination MSP: Multiplex Section Protection SETS: Synchronous Equipment Timing Source MSA: Multiplex Section Adaptation HPOM: Higher order Path Overhead Monitor HPC: Higher order Path Connection HPT : Higher order Path Termination HPA: Higher order Path Adaptation LUG: Lower order path Unequipped Generator LPOM: Lower order Path Overhead Monitor SETPI: Synchronous Equipment Timing Physical Interface OHA: OverHead Access
SEMF: Synchronous Equipment Management Function

MCF: Message
Communication Function LPC: Lower order Path Connection LPT: Lower order Path Termination
PN 56717020103 Rev. 1, May 2001
21
Lower order Path Adaptation (VC12) PPI: plesiochronous physical Interface (VC12)
Lower order Path Adaptation (VC3) plesiochronous physical Interface (VC3)
General
The Altium ADR 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.
Operational Parameters
The operational parameters include: The configuration parameters The maintenance commands or operations (these actions are cleared in case of power supply loss) The alarms and their severity
Configuration Parameters
Note: The functional blocks naming, configuration parameters and their default value, noted "XXXXXX", are displayed on HTTP navigator.
Table 2-1. Configuration Parameters

Configuration Parameters for Functional Blocks SPI: SDH Physical Interface The Automatic Laser Shutdown function can be disabled (equipment global functionality) "ALS" (Automatic Laser Shutdown) MST: Multiplex section Termination EBER-B2 monitoring; configurable in "Monitoring" or "No Monitoring" If EBER-B2 is not monitoring, AIS, SF and MS-RDI consequent actions are inhibited SD-B2 threshold: configurable from 10-5 to 10-9 "SD-B2 threshold" " Monitoring" Default Value
"Enable"
"10-6"
22
PN 56717020103 Rev. 1, May 2001
Chapter 2Operations

Configuration Parameters for Functional Blocks SOH: Section Overhead Configuration of SOH bytes, which are not used in standard or for EOW orderwire conveying. Configurable bytes are: Line 1, byte of column 7 Line 1, byte of column 8 Line 1, byte of column 9 Line 2, bytes of columns 8, 9 Line 9, bytes of columns 8, 9 MSP: Multiplex Section Protection Link type: 1+0 or 1+1 Protection mode: bi-directional / unidirectional "Mode " Revertive authorization: return after a WTR time-delay to the working link when the fault (SF or SD) causing the switch has disappeared. "Revertive" Wait Time to Restore (WTR) period: in revertive mode, period following restoration of nominal operation; configurable from 0 to 15mn in one-second steps "WTR" SF/SD priority according to Recommendation G.783 [1994] annex A.1.2.1; possible value:"high" or "low" (compatibility with MXA) "Sf/sd priority" SF and SD fault persistence: configurable from 0 to 10s in 100ms steps "Hold-off time" HPOM: Higher order path overhead monitor Signal label expected and received (byte C2 of VC4 path overhead) ; "Label" : -- "Expected", possible values: "01H" (equipment not specified) or "02H" (TUG mode structure) -- "Received". (Displayed) Path Trace VC4 (bytes J1) Mode: 1 byte (Trace = 0 to 255) or 16 bytes (Trace = 15 ASCII characters) - "Trace Expected" (configurable) - "Trace Received" (displayed in the same mode as 'Expected') "TIMdis" TIM (Trace Identifier Mismatch) enable or disable 16 bytes "UNNAMED VC4" + CRC7 Clicked (no TIM) "1+0" "BIDIR" Default Value
"01" "02" "03" "00" "00"
"OFF"
"1 mn"
"Low" "0 ms"
"02H"
PN 56717020103 Rev. 1, May 2001
23

Configuration Parameters for Functional Blocks HPT: Higher Order Path Termination Signal label transmitted, expected and received (byte C2 of VC4 path overhead) ; "Label": - "Sent", possible values: "01H" (equipment not specified) or "02H" (TUG mode structure) - "Expected", possible values: "01H" (equipment not specified) or "02H" (TUG mode structure) - "Received". (Hexadecimal value, if unknown) SD threshold (VC4): configurable from 10-5 to 10-9 "SD threshold" Path Trace VC4 (bytes J1) Mode: 1 byte (Trace = 0 to 255) or 16 bytes (Trace = 15 ASCII characters) - "Trace sent" (configurable) - "Trace Expected" (configurable) - "Trace Received" (displayed in the same mode) "TIMdis" TIM (Trace Identifier Mismatch) enable or disable LUG: Lower order path Unequipped Generator Number of the unequipped VC12s transmitted in TUG3s (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" LPC: Lower order Path Connection Connection switch Connection name (configurable according to M.1400 13) Type: bi-directional / unidirectional SNC protection Type Protection mode SNC/I MONO Not put into service No name MONO "10-6" "FFH" 16 bytes "UNNAMED VC4" + CRC7 "UNNAMED VC4" + CRC7 Clicked (no TIM) Default Value
"02H" "02H"
"10-6"
24
PN 56717020103 Rev. 1, May 2001
Chapter 2Operations

Configuration Parameters for Functional Blocks 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" SF and SD fault persistence (path by path) : configurable from 0 to 10s in 100ms steps "Hold-off time" "0 ms" LPT: Lower order Path Termination Plesiochronous access 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) Signal label (VC12) transmitted, expected and received (V5 Byte) "Label" : - "Sent",: "000b" no connection or "010b" (asynchronous) if connection (not configurable by the operator) - "Expected", possible value : "001b" equipped without specification or "010b" (asynchronous) - "Received". SD threshold: configurable from 10-5 to 10-9 for VC3 configurable from 10-5 to 10-9 for VC12 "SD threshold" Path Trace transmitted for VC3 (Byte J1) - "Trace sent" for VC12 (1 byte) Path Trace transmitted for VC12 (Byte J2) -- "Trace sent" (1 byte) ADRLAN Card Signal label (VC3# i) transmitted, expected and received; "Label: - "Sent", not configurable - "Expected", not configurable - "Received". "A8H" "A8H" "04H" "04H" Default Value
"1 mn"
"010b"
"10-6"
"UNNAMED VC3" + CRC7
"0x00"
PN 56717020103 Rev. 1, May 2001
25

Configuration Parameters for Functional Blocks Ethernet port configuration (exclusive choice) "Automatic" (or auto-negotiation) with 4 non-exclusive possible operation modes, "Manual: select only one operation mode among the four available operation modes: - 100Mbps Full Duplex - 100Mbps Half Duplex - 10Mbps Full Duplex - 10Mbps Half Duplex Flow control - LAN towards VC3_# i - VC3_# i towardsVC3_# j or LAN Interface configuration - LAN in service / no service - Maximum route Age - Path trace J1 transmitted: "UNNAMED VC3" + CRC7 not configurable and not treated in reception SETS: Synchronous Equipment Timing Source Quality level of synchronization sources ; "Quality" : - "PRC" (Primary Reference Clock), - "SSUT" (Synchronization Supply Unit Transit), - "SSUL" (Synchronization Supply Unit Local), - "SEC" (Synchronization Equipment Clock), - "DNU" (Do Not Use), - "SSMB" (Synchronization Status Message Byte) (synchronization quality carried out in S1 Byte). Use of synchronization status messages (SSM); "SSM" T0 priority Table, according to enabled sources; possible values: 1 to 8 (1 have the most priority) 2 Mbps port number chosen for T2; "T2 Tributary port" (1 port per enabled 2 Mbps card) Revertive authorization (common to all sources): return after a WTR time-delay to the working link when the fault (SF or SD) causing the switch has disappeared. "Revertive" Wait Time to Restore (WTR) period: in revertive mode, period following restoration of nominal operation; configurable from 0 to 30mn by one-second step "WTR" Source selected for T4; "Active source" SASE mode control (enable or disable) T3 source selection for SASE mode (T3-1 or T3-2) T3: PRC T1: SSMB T2: SEC T4: SEC Default Value "Automatic" All operation modes authorized
60 % 60 % Service 300 s "UNNAMED VC3" +

CRC7
"ON" "1" for all sources "1"
"Yes"
"1 mn"
"T0" Disabled T3-1
26
PN 56717020103 Rev. 1, May 2001
Chapter 2Operations

Configuration Parameters for Functional Blocks Quality level for T4 - "PRC" (Primary Reference Clock) - "SSUT" (Synchronization Supply Unit Transit) - "SSUL" (Synchronization Supply Unit Local) - "SEC" (Synchronization Equipment Clock) OHA : OverHead Access EOW interface operating mode: CO (co directional) or CT (contra-directional master) "EOW configuration" Selection of byte used to convey order wire channel EOW in the SOH, E1 E2 Line 7, bytes of columns 8, 9 Line 8, bytes of columns 8, 9 Line 9, bytes of columns 8, 9 AUX interface operating mode (F1); CO (co directional) or CT (contra-directional master) "AUX configuration" MNGT Port Selection of MNGT interface operating mode "Management Use" or "Traffic (M#21)" (X24/V11 traffic data at 2048kbit/s) MNGT port (allocated to management purposes) MNGT port operating mode ; CO (co directional) or CT (contra-directional master) "P port configuration" MNGT port (allocated to traffic data) Selection of physical interface port allocated to 21st motherboard access for traffic "G.703" or "X24/V11" In X24/V11 traffic mode: Selection of "PPI X24 Clock Mode" of data received from DTE "Far 2Mbs Clock" or "SDH Sub network Clock" Selection of "Data Sampling Edge" of data received from DTE "Default Edge" or "Inversed Edge" ADR E3DS3 Card 34 or 45 Mbps physical interface selection "E3 (34M)" or "DS3 (45M)" "E3 (34M)" "G.703" "Management Use" CT E1 Default Value "PRC"
CT
CO
"SDH Sub network Clock" "Default Edge"
PN 56717020103 Rev. 1, May 2001
27

Configuration Parameters for Functional Blocks Connecting cable length selection so that transmitted pulse complies to template defined in Bellcore GR-489-CORE standard : "Type of cable"(DS3/45Mbps mode only "long" or "short" (length < 225 ft or 70m) ADR FAN card Fan operation mode selection "Permanent cooling: Fan is ON, if T> 5C (41F) , fan is OFF, if T 0C (32F) "Overhead Avoidance: Fan is ON, if T> 35C (95F), fan is OFF, if T 30C (86F) Equipment Session Equipment Name Selection of clearance level: Administrator Operator Observer One password by clearance level (Only the administrator may modify password) Authorization to transmit traps to the management: "Traps Managers List" Managers list "Managers List" (10 addresses possible) Authorized maximum clearance (exclusive choice) Equipment date and time Status of slots A, B, C, D expected card configuration Empty Admin "Overhead Avoidance" Default Value
"short"
No password
0.0.0.0 0.0.0.0 Supervisor "01/01/1970" ADR IC1.x, if absent card Inserted card if present
Monitoring Monitoring of modules A no-monitored card is indicated in the equipment view; not monitoring a card inhibits the entire management of the faults related to this card (card and port) Subrack Monitoring (Motherboard) Monitoring of ports Not monitoring a port inhibits the entire management of the faults and performance related to this port Monitoring
Monitoring No Monitoring For LPOM blocks Monitoring For others
28
PN 56717020103 Rev. 1, May 2001
Chapter 2Operations

Configuration Parameters for Functional Blocks Putting a card into/out of service (The card is ignored by the management function) Default Value Into Service, if present card Out of service, if absent card
Alarms Alarm severity The severity of each alarm is configurable individually with the following attributes: major, major reverse, minor, minor reverse, none, none reverse Alarm Persistence Persistence for the appearance: X = 0, 1, 3, 10 or 30s Persistence for the disappearance: Y = 0, 1, 3, 10 or 30s Loops Remote loop indication, for loops 1 and 2, validated or not (use of bits 1 to 4 of byte S1) Central office mode (gathering remote indications) : Yes or no Routing Static routes table Putting ports into service: Ethernet, PPP1, PPP2, PPP3 or PPP4 Enabled / Disabled (port by port) Port addressing (port by port) : Ethernet Interface IP address Subnet mask PPP Interface Interface IP address Subnetwork mask Destination IP address (PPP interface only) Management paths (port by port PPP only) either: MNGT DCCr (A, B, C or D) DCCm (A, B, C or D) P#1, P#2 RIP routing validated or not (port by port) Not configured Disabled Not validated See tables 2-11 and 2-12
X = 3s Y = 3s
No
135.10.110.10 255.255.0.0 0.0.0.0 0.0.0.0 0.0.0.0 Not configured
Not validated
PN 56717020103 Rev. 1, May 2001
29
Table 2-2. Maintenance Operation Commands

Monitoring Commands According to the Functional Blocks SPI: SDH Physical Interface 2s laser restart on operator action 9s laser restart on operator action ALS enabled/disabled (equipment global functionality) Line loopback enabled/disabled (transparent type) Equipment loopback enabled/disabled (transparent type) MSP: Multiplex Section Protection Operator command for MSP protection Clear Lockout of Protection Forced Switch to Working Forced Switch to Protection Manual Switch to Working Manual Switch to Protection LPC: Lower order Path Connection Operator command for SNC protection of VC12 or VC3 path (per path and in order of priority): Clear Lockout of Protection Forced Switch to Working Forced Switch to Protection Manual Switch to Working Manual Switch to Protection PPI: PDH Physical Interface Line loopback enabled/disabled (transparent type) Equipment loopback enabled/disabled (transparent type) ADRLAN Card LAN statistics (display and reset) VC3 # i statistics (display and reset) Flow control (display and reset) Interface status-(separate graphical SDH/WAN status display)
210
PN 56717020103 Rev. 1, May 2001
Chapter 2Operations
Table 2-2. Maintenance Operation Commands

Monitoring Commands According to the Functional Blocks SETS: Synchronous Equipment Timing Source Protection operator command Clear Lockout of Protection Forced Switch Manual Switch to Protection Equipment Alarms Alarm acknowledgements using the front panel push-button (such acknowledgements only act on major and minor output loops ; LED indications remain as long as alarm cause). RESET of alarm and event logs Performance RESET of performance logs 15 mn and 24H ADRLAN RESET of traffic counters of ADRLAN functions ports (port by port) or of indicators of ADRALN frame switching function Reset Hot reset of the equipment, performed by software (the reset time should be shorter than 30s)
Predefined Functions
On commissioning, the following mechanisms are implemented automatically: Synchronization Management of outgoing remote indication loops
Synchronization
The synchronization 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)
PN 56717020103 Rev. 1, May 2001
211
T1 extracted from one of the incoming STM-1 streams (1 to 4 possibilities according to the number of ADRIC1.x cards present in the equipment) T2: one 2 Mbps G.703 source per declared 2 Mbps module, and selected from the various 2 Mbps G.703 accesses T3: two external 2 MHz G.703 sources
The following figures give typical synchronization examples according to equipment connections.
2 MHz external sync input (T3): - Quality = PRC, - Priority = 1.
1 ADR155C 1
Internal synchronization T0 = T3
STM-1port (T1-C): - Quality = DNU - Priority = 2.
2 ADR155C 2
SSM = PRC T0 = T1-C
STM-1port (T1-C): - Quality = DNU - Priority = 2. T1-C = T0 = T3 (ADR155C1)
T1-C = T0 = T3
2 MHz clock output T4= T0 = T3 (ADR155C1)
3 ADR155C 3
Synchronization of other equipments SSM = PRC
T0 = T1-c
2 MHz clock output T4= T1-N Synchronization of other equipments
Figure 2-1. Synchronization from the 2 MHz external sync input (T3)
212
PN 56717020103 Rev. 1, May 2001
Chapter 2Operations
2 Mbit/s port (T2): - Quality = PRC, - Priority = 1. STM-1port (T1-C): - Quality = DNU - Priority = 2. STM-1port (T1-C): - Quality = DNU - Priority = 2. T1-C = T0 - T1-c (West) T0 = T1-C West or T2 (ADR155C1)
1 ADR155C 1
Internal synchronization T0 = T2
ADR155C 2 2 SSM = SEC
T1-C = T0 = T2
2 MHz clock output T4= T0 = T1c West
3 ADR155C 3
Synchronization of other equipments SSM = SEC
T0 = T1-c
2 MHz clock output T4= T1-N Synchronization of other equipments
Figure 2-2. Synchronization from a 2 Mbps port

Note: Synchronization is applied to the 2 Mbps port of the Altium ADR, which is enabled first (local ADR in the example).
PN 56717020103 Rev. 1, May 2001
213
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 message, which corresponds, to the 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 and #2) via S1 STM-1 West and S1 STM-1 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 STM-1 West and S1 STM-1 East, and local data (Local user input #1 or #2 and local alarm), enables local alarm loopback 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.
214
PN 56717020103 Rev. 1, May 2001
Chapter 2Operations
A WEST Received West S1 #1 #2 #3 #4
Activation of local user inputs S1 = received S1* + state of #1 or #2 local user inputs #1 and #2 folowing activation of local user outputs A or B ( quipment alarms or local user inputs #3 rt #4)
B Local user outputs EAST
A WEST
B Local user outputs EAST
#1 #2 #3 #4 Local user inputs Activation of Local user inputs #1 or #2
Local user inputs
2 ADR 155C 2
A EAST S1 = received S1* + state of local user inputs #1 and #2 #1 #2 Received S1* : gathering of S1 received from authorised STM1 interfaces except from transmiting interface #3 #4 Local user inputs
Activation of local user inputs #1 or #2 folowing activation of local user outputs A or B ( quipment alarms or local user inputs #3 rt #4)
B Local user outputs WEST S1 = received S1* + state of local user inputs #1 and #2
S1 received from STM1 tributary
ADR 155C 3 3
Figure 2-3. Remote loopback function (registering alarms on central site)

Note: When Local User #1 and #2 gather major and minor alarm information (local user outputs A and B) it is necessary to give them a non-alarmed severity in order to avoid permanently activation. 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.
Alarms Processing
LEDs and Pushbuttons
The following tables give the meanings of the lit LEDs and the actions initiated by using the pushbuttons. LEDs
Monitored Item Motherboard Designation "ON" Comment Green Status On Meaning In service card
PN 56717020103 Rev. 1, May 2001
215
LEDs
Monitored Item Designation Comment Status Flashing Off "ALA M" "ALA m" Ethernet (Management port or ADR LAN card) "Link" Right "Activity" Red Yellow Left On On On Off On Off Traffic cards ADR E3DS3 card "STATUS" "DS3-45/ E3-34" On Off Meaning Self-test default Not powered equipment or not run software Major alarm Minor alarm On transmission No traffic Correct Link No link See table below 34 Mbps mode activated 45 Mbps mode activated
STATUS" LEDs on ADR IC 1.x, ADR ERE, ADR LAN, ADR E3DS3 and ADR 21E120 Cards
Green LED On On Off Off Flashing Red LED Off On Off On Card in service Card in service and in alarm Hardware default on card (fuse) Card out of service Self-test default Meaning
Pushbuttons Designation "ACK" "INIT CONFIG"* Location Front panel Motherboard Role Alarm acknowledge Configuration reload Action initiated Pressing disables the outgoing alarm loops. The visual alarm is kept. "Factory" Configuration 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.
216
PN 56717020103 Rev. 1, May 2001
Chapter 2Operations
Defaults and Alarms

The tables below give the default values of severity associated with the failures. Table 2-3. Alarms and Severity
Alarms Description Severity
SPI: SDH Physical Interface SPI-LOS SPI-TF Loss Of SignalTransmit Fail Major Major
RST: Regenerator Section Termination RST-LOF Loss Of Frame Major
MST: Multiplex section Termination MST-EBER-B2 MST-SD-B2 MST-AIS MST-RDI Bit Error Rate > 10-3 on B2 Byte Signal Degrade B2 Alarm Indication Signal Remote Defect Indication Major Minor Non-alarmed Non-alarmed
MSP: Multiplex Section Protection PAM SCM OTM Protection Architecture Mismatch Selector Control Mismatch Operation Type Mismatch Minor Minor Minor
MSA: Multiplex Section Adaptation AU-AIS AU-LOP Administrative Unit Alarm Indication Signal Administrative Unit Loss Of Pointer Non-alarmed Major
HPOM: Higher Order path Overhead Monitor HO-RDI/G1 HO-TIM HO-SD (VC4) HO-UNEQ High Order Path Remote Defect Indication High Order Path Trace Identifier Mismatch High Order Path Signal Degrade High order Path Unequipped Non-alarmed Non-alarmed Non-alarmed Non-alarmed
HPT: Higher Order Path Termination HO-SLM HO-SD (VC4) HO-TIM High Order Path -Signal Label Mismatch High Order Path Signal Degrade High Order Path Trace Identifier Mismatch Non-alarmed Non-alarmed Non-alarmed
PN 56717020103 Rev. 1, May 2001
217
Table 2-3. Alarms and Severity

Alarms HO-RDI/G1 HO-UNEQ Description High Order Path -Remote Defect Indication High Order Path Unequipped Severity Non-alarmed Non-alarmed
HPA: Higher Order Path Adaptation TU-LOM TU-AIS TU-LOP (TU3) TU-LOP (TU12) Tributary Unit - Loss Of Multiframe Tributary Unit Alarm Indication Signal Tributary Unit - Loss Of Pointer Tributary Unit - Loss Of Pointer Minor Non-alarmed Major Minor
LPOM: Lower Order path Overhead Monitor LO-SD-B3 (VC3) LO-SD-V5 (VC12) LO-RDI LO-UNEQ Signal Degrade B3 Signal Degrade V5 Low order Path -Remote Defect Indication Low order Path Unequipped Minor Minor Non-alarmed Non-alarmed
LPT: Lower order Path Termination LO-SD-V5 (VC12) Lo-SD-B3 (VC3) LO-SLM LO-RDI LO-UNEQ Signal Degrade V5 Signal Degrade B3 Low order Path Signal Label Mismatch Low order Path Remote Defect Indication Low order Path Unequipped Minor Minor Non-alarmed Non-alarmed Non-alarmed
PPI: PDH Physical Interface PPI-LOS (21 x 2M or motherboard) PPI-LOS (34 / 45M) PPI-AIS Loss Of Signal Loss Of Signal Alarm Indication Signal Minor Major Non-alarmed
SETS: Synchronous Equipment Timing Source T3 LOS T1 LOS T2 LOS T4 - Failure Local equipment Local user inputs # 1 Remote indication 1 Non-alarmed Loss Of Signal on T3 sync input Loss Of Signal on T1 sync input Loss Of Signal on T2 sync input Failure on T4 synchronization output Minor Non-alarmed Non-alarmed Minor
218
PN 56717020103 Rev. 1, May 2001
Chapter 2Operations
Table 2-3. Alarms and Severity

Alarms Local user inputs # 2 Local user inputs # 3 Local user inputs # 4 Remote equipment Far user inputs # 1 Far user inputs # 2 Others Message Message Message Message Message Message Message Daughter board Defective Daughter board Mismatch Daughter board Missing Mother board Defective ADRFAN Missing One Fan failed (ADRFAN module) Both Fans failed (ADRFAN module) Major Major Major Major Major Minor Major Remote indication 1 Remote indication 2 Major * Minor * Description Remote indication 2 Remote indication 3 Remote indication 4 Severity Non-alarmed Major Minor
* If the equipment configured is declared central office.
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 faultfinding and fault locating. The following tables define the faults that are masked for each fault detected in the system.
Note: 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).
PN 56717020103 Rev. 1, May 2001
219
Correlation of STM-1 Faults

Faults 1 TF 2 LOS 3 LOF 4 AIS (MS-AIS) 5 SD-B2 6 RDI (MS-RDI) X X X X X X X X X 1 TF 2 LOS 3 LOF 4 AIS 5 SD-B2 6 RDI
Correlation of MSP faults

Faults 1 PAM 2 SCM 3 OTM X X 1 PAM 2 SCM 3 OTM
Correlation of AU faults
The AU faults are masked by the STM-1 LOS, LOF and AIS (MS-AIS) faults. The TU-LOM fault is filtered, if there is no configured VC12 connection on this STM-1.
Faults 1 2 3 4 5 6 7 8 AU-AIS AU-LOP UNEQ (VC4 UNEQ) RDI (VC4 RDI) SLM TU-LOM TIM SD-B3 (VC4) X X X X X X X X X X X X X X X X X X X X X 1 AU-AIS 2 AU-LOP 3 UNEQ 4 RDI 5 SLM 6 TU-LOM 7 TIM 8 SD-B3
Correlation of TU/VC Faults

TU-AIS, LP UNEQ, LP-RDI and LP-SLM are masked by the STM-1 LOS, LOF and AIS (MS-AIS) faults, and by the AU AU-LOP, AU-AIS, UNEQ (VC4 UNEQ) and TU-LOM faults.
220
PN 56717020103 Rev. 1, May 2001
Chapter 2Operations
TU-LOP is masked by the AU SLM and TU-LOM faults. TU-AIS and TU-LOP faults of a not connected input are filtered.
1 TU-AIS 2 TU-LOP 3 LP-UNEQ 4 LP-RDI 5 LP-SLM 6 LP-SD
Faults 1 2 3 4 5 6 TU-AIS TU-LOP LP-UNEQ LP-RDI LP-SLM LP-SD
X X X X
X X X X X X
Correlation of Port Faults

Faults 1 2 LOS AIS X 1 LOS 2 AIS
Correlation of Remote Faults

LO-REI, LO-RDI, HO-REI and HO-RDI faults of unidirectional connection input are filtered.
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 Remote Equipment

Multiplex section (byte M1) ("far end working (protection) MS"), VC4 tributary paths ("far end High Path Virtual Container")
PN 56717020103 Rev. 1, May 2001
221
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 and monitoring 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 monitoring point 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-second period or one fault SES (Severely Errored Second): number of severely errored seconds
An SES is a second for which the number of errors exceeds a defined threshold or during which at least one fault is detected.
Monitoring point MS (byte B2) (for local) and MS (byte M1) (for remote) RS (byte B1) (for local) HP VC4 LP - VC3 (for local) LP - VC12 (byte V5) (for local) SES declaration threshold 28800 (24 blocks per frame) 9600 (8 blocks per frame) 2400 2400 600
UAS (Unavailable Second): number of seconds of unavailability, BBE (Background Block Error): number of residual errored blocks excluding SES.
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 HTTP navigator. The performance process is initialized when the equipment is powered up and the monitoring point is monitored.
222
PN 56717020103 Rev. 1, May 2001
Chapter 2Operations
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 on HTTP navigator.
PN 56717020103 Rev. 1, May 2001
223
Procedure for Replacing Subassemblies

Replacing a Card
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. The following procedure applies to all the cards in the equipment, unless otherwise specified. 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 STM-1 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.
Replacing the Fan Module

The ADRFAN module consists of two redundant fans in order to ensure sufficient ventilation when either of them is defective. Fan failures are detected on the motherboard by monitoring the power consumed; failures are viewed on "ADR155C shelf view" screen of HTTP navigator. Default parameters lead to the following behavior:
Note:
If ADRFAN module is framed yellow, one of two fans is faulty (minor alarm) If ADRFAN module is framed red, both fans are faulty (major alarm)
The operation of ADRFAN is not continuous; its initiation is related to the equipment internal temperature and to the operating mode selection.
224
PN 56717020103 Rev. 1, May 2001
Chapter 2Operations
ADRFAN can be extracted; it can be replaced at any moment without disturbing the traffic. To replace the fan module: 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
Replacing the Front-Panel Fuse

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 a 4A quick-break fuse (HA214A) 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
PN 56717020103 Rev. 1, May 2001
225
226
PN 56717020103 Rev. 1, May 2001
Chapter 3 Spare Parts
Description ADR155C 19" subrack ADR155C subrack Fan module - ADR FAN Adaptator 22 x 75 ohms 1.0/2.3 19"/ETSI Traffic card IC1.1 STM1 optical card - ADR IC1.1 IC1.2 STM1 optical card - ADR IC1.2 STM1 electrical card - ADR ERE 75 ohms 34/45 Mbps card ADR E3DS3 Ethernet 10/100 card - ADR LAN1 21 x 2Mbit/s 120 ohms card - ADR 21E120 External transformer Transformer 110-240//48V 60W/
Part Number
AM251049868333 AM101360 AM101666
AM101328 AM101329 AM 101670 AM 101668 AM101331 AM101330
AM101669
PN 300-610012-001 Rev. 1c, April 2001
31
Altium ADR
Available Cable List

Designation SYNC port Synchronization Length 2.5 m 5m 12 m 25 m Code no. 251 008 309 251 008 312 251 008 320 251 008 333
E1 INPUT or E1 OUTPUT port 21x2Mbit/s In or Out on motherboard or ADR21E120 Et or ST 21x2 Mbps 120 ohms SUBD 21x2 Mbps 75 ohms 1.0/2.3 right cable MNGT port Management interface cable between two ADR 155C 9 points to 15 points adaptation cable for X24/V11 2,5 m 12 m 2,5 m 12 m 1.5 m 3m 2.5 m 5m 1,8 m 55 670 741 55 670 743 55 670 582 55 670 584 55 670 655 55 670 656 251 025 855 251 025 876 4 980 214
COMM port VT100 Management port ETH port Ethernet port on mother board or ADRLAN1 card Right cable male male * Right cable male male * Crossover cable male male ** Right cable male female Right cable male female LOOPS port Remote indication, remote control and station alarm loops
1.5 m 3m 3m 1.5 m 3m 2.5 m 5m 12 m 25 m 3m 2.5 m 3.4 m 5.8 m 7m 8.2 m 9.4 m 15 m 20 m 25 m
55 670 421 55 670 422 55 670 610 55 670 423 55 670 424 6 013 628 6 013 261 6 013 161 6 013 262 55 670 797 6 491 366 6 491 367 6 491 369 6 491 370 6 491 371 6 491 372 55 670 481 55 670 495 55 670 752
POWER port Power supply TR or REC ports (ADR IC1.x card) FC-PC/FC-PC optical Jumper on ADRIC1.x card
32
PN 300-610012-001 Rev. 1c, April 2001
Chapter 3Spare Parts
Designation TR or REC ports (ADR ERE card) 1,6/5,6 75ohm 155Mbit/s cable (1 coax.)
Length 2.5 m 5m 12 m 25 m 2.5 m 5m 12 m 25 m 2.5 m 5m 12 m 25 m
Code no. 6 013 631 6 013 270 6 013 190 6 013 271 6 013 640 6 013 641 6 013 642 6 013 643 6 013 632 6 013 266 6 013 176 6 013 267
BNC 75ohm 155Mbit/s cable (1 coax.) AUX or EOW ports Auxiliary channel and orderwire channel on ADRIC1.x card
* **
This cable is used for connection to a HUB. This cable is used for direct connection to a computer or a router.
PN 300-610012-001 Rev. 1c, April 2001
33
Altium ADR
34
PN 300-610012-001 Rev. 1c, April 2001
Chapter 4 Specifications
Equipment Optical Specifications Interface type Bit rate Standard Encoding Optical fiber IC1.1 = L1.1 + S1.1 or IC1.2 = L1.2 + S1.2 155.520 Mbps 20 ppm ITU-T G.957/G.958 Not encoded (NRZ) 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 0 - 28 dB with no external attenuator 0 - 60 km (IC1.1) or 0 - 90 km (IC1.2) All-ceramic FC/PC 2U 19" or ETSI 300 mm 6 kg approx. Corresponding to the IP of the rack used < 40 W (to a equipped subrack of two cards ADR IC1.x and two cards ADR LAN)
Guaranteed attenuation Typical range Connector Mechanical Specifications Height Width Depth Weight Protection Class (IP) Consumption (See details below)
PN 300-610012-001 Rev. 1c, April 2001
41
Altium ADR
Equipment Environmental Specifications Mechanical Climatic conditions Operating temperature range Extended operating temperature range Packaged transportation and storage temperature Relative humidity ESD ETS 300 119-4 (19") or CEI 297-3 (ETSI) ETS 300 019-2-3 CEI 721-1 (1993) ETS300 019 part 1-3, class 3.1, 3.2 - 5 C to + 45C - 25 C to + 55C (the MTBF [Mean Time Between Failure] is significantly degraded) - 40C to + 70C < 85% NF EN 50081-1, NF EN 50082-1 June 1992 and ETS 300 386-1 1994 NF EN 55022 (1994) + Additive A1 02/1996 equipment Class B NF EN 60950 and UTE C 92130 (the equipment does not provide the fire envelope) ETS 300132-2 (is VLV equipment) 3.4 10-6 0.75 10-6 2.6 10-6 1.2 10-6 0.75 10-6 2.25 10-6 0.33 10-6 1.25 10-6 2.5 10-6 11.3 W 5.0 W 4.7 W 4.9 W 3.9 W
EMC (Electromagnetic Compatibility) Safety Energy Predicted Reliability* Motherboard ADR 21E120 card ADR1 IC1.x card ADR ERE card ADR E3DS3 card ADRLAN1 card Background Power supply ADRFAN Module
Sub-assemblies Consumption ** (measured when powered by 48V supply) Motherboard ADR 21E120 card ADR1 IC1.1 card ADR ERE card ADR E3DS3 card (in DS3 mode)
442
PN 300-610012-001 Rev. 1c, April 2001
Chapter 4Chapter 4Specifications
Equipment ADR E3DS3 card (in E3 mode) ADRLAN1 card ADRFAN Module Transformer 110-240//48v 60W/ (OPTIONAL) Dimensions (without cable and connector) Operating temperature Storage temperature Input voltage Input frequency output voltage Electronics protection Standard L x l x H = 132 mm x 58 mm x 30 mm 0C to 40C -20C to 85C 90 to 264 VAC 47 to 63 Hz 48 VDC Short circuit and overload EN60950 and UL-CSA 3.72 W 6.8 W 4.43 W
* The predicted reliability computations are based on the CNET's 1993 issue (RDF 93) of the Reliability Data Manual, and assumes specific requirements for the following:
ambient temperature 25C (with ventilation conditions such as a subrack internal middle temperature
of less than 40C)
environment (mounted on the ground, fixed, and protected) qualification component aging
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 percent to estimate peak values, which determine power rack capacity. This takes into account variations in dynamic power and converter efficiency according to total power supply. Another 10 percent should be added to estimate peak values when powered by 72V supply.
PN 300-610012-001 Rev. 1c, April 2001
443
Altium ADR
444
PN 300-610012-001 Rev. 1c, April 2001
Appendix A Constructing an IP Network Addressing Plan
This appendix summarizes the rules for constructing a TMN based on the IP protocols suite.
Overview
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.
PN 300-610012-001 Rev. 1c, April 2001
A1
Altium ADR
HTTP Server
To download mechanism
To OS functions
HTTP
TFTP
SNMP
RIP
TCP
UDP
ICMP
IP
ARP
MAC
PPP
Ethernet
EOC
IP protocol suite
Note:
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...)
Addressing IP
To route packets in a node, IP uses an addressing mechanism: depending on the destination address contained in the packet, it determines by polling its routing table the next router to which it should send the packet, and determines the physical interface over which it should transmit the packet. (The terms "router" and "equipment" will be used interchangeably in the following paragraphs). There are two non-exclusive ways of updating IP routing tables: Use of static routes entered by operator, Use of a routing demon (such as RIP, RIP2, OSPF), which takes charge of dynamic management of routing tables across the network. The IP addresses are coded over 4 bytes and are usually represented in decimal form (e.g.: 135.11.33.115). An IP address is divided into 3 fields: The "NET" field, on the left, The "subnet" field, in the center,
A2
PN 300-610012-001 Rev. 1c, April 2001
Appendix AConstructing an IP Network Addressing Plan
The "host" field, on the right. The length of the first field depends on the class to which the address belongs. The length of the "subnet" and "host" fields is defined by a mask associated with the address. There are three address classes:
Class A: the "NET" field is coded over the first byte; the three other bytes
are reserved for the "SUBNET" and "HOST" fields; class A addresses vary from 1.0.0.0 to 126.255.255.254,
Class B: the "NET" field is coded over the first two bytes; the two other
bytes are reserved for the "SUBNET" and "HOST" fields; class B addresses vary from 128.0.0.0 to 191.255.255.254,
Class C: the "NET" field is coded over the first three bytes; the last byte is
reserved for the "SUBNET" and "HOST" fields; class C addresses vary from 192.0.0.0 to 223.255.255.25 4 ;the maximum number of equipment pieces that can belong to the same class C IP network (having the same "NET") is 254.
Note: Note: Addresses starting with 127 and addresses including "all-1" or "all-0" in the "SUBNET" and "HOST" fields are not permitted. The IP standard authorizes that the "SUBNET" and "HOST" fields can be coded over a number of bits that does not correspond to an byte border; usually this is not implemented for reasons of address legibility and since the majority of RIP routing demon implementations do not support this feature.
The "SUBNET" field is defined by a mask which is written in the form: 255.255.255.0, 255.255.0.0, 255.0.0.0, etc: the number of zero bits from the left of the mask defines the length of the "HOST" field; e.g., for the address 40.2.2.2 associated with mask 255.255.255.0, the "NET" field takes the value 40, the "SUBNET" field the value 2.2 and the "HOST" field the value 2.
Addressing Plan
A global IP network may be sub-divided into N networks, each with a "NET" number. Within each network, each physical link (point-to-point or point-multipoint) has its own "SUBNET" number. Each equipment connected to this link (2 for point-to-point link, N for an Ethernet segment), has its own "HOST" number. Depending on the number of equipment pieces and links, address classes A, B or C are used with "SUBNETS" coded over one or two bytes. To conclude, an IP address and its "SUBNET" mask must be associated with each interface of a network node.
PN 300-610012-001 Rev. 1c, April 2001
A3
Altium ADR
Use of Static Tables

Concerning the use of static tables, each network node must have its routing table completed in order for it to be able to route correctly the received packets. All IP routes of a given equipment routing table contains the following fields: Destination @ip: corresponding to the IP address of the equipment or sub-network (or network) that is targeted from the equipment in question, "Subnet mask: sub-network mask associated with the IP address defined in "destination @ip"; all equipment pieces with this part of their IP address fields defined by "1" bits correspond to the "destination @ip" (defined by this same mask) that can be attained using this route, "Next hop @ip: IP address of the next router (in direct connection with the equipment in question) to which the packet is to be sent, Metric (also named cost or distance): value from 1 to 15, indicating the number of hops required to reach the equipment corresponding to the "destination @ip" address. 16 correspond to infinite for the RIP routing demon. This field may only be used by a routing demon to select a preferential route if there are several different possible routes for a given destination. It is possible to always enter "1" for this field in order to simplify, if this operation is not required, "Interf. interface number used to reach the next router (the IP address of which is "next hop @ip").
Note:
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. 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 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 the manager. To operate equipment via a PC and an Ethernet interface, it is necessary to change the IP address of the operating PC to the same SUBNET as the equipment.
Note:
Note:
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.
A4
PN 300-610012-001 Rev. 1c, April 2001
140.1.1.3 F3 140.1.0.2 140.1.0.3 Fiber 140.1.1.2 F2 Ethernet 140.1.1.4 F4 140.1.1.5
ProVision SNMPC
128.1.0.1
F1 128.1.0.2 Ethernet
NET 128.1
F6
128.1.0.3
NET 140 - 1
F5
PPP1 150.1.0.2 Fiber Fiber
SUBNET 150.1.0
150.1.0.3 F7 Ethernet Ethernet 150.1.1.3 F8 150.1.1.2
SUBNET 150.1.1
150.1.1.5 F10
150.1.1.4 F9
NET 160.1
NET 150.1
Figure A-1. Block diagram of example TMN architecture
PN 300-610012-001 Rev. 1c, April 2001
A5
Altium ADR
Altium ADR F6 Configuration

Interfaces Eth Sub network Mask PPP1 Sub network Mask PPP2 to PPP4 Static Routes Dest @IP 140.1.0.0 150.1.1.0 Subnet mask 255.255.0.0 255.255.255.0 Next hop 128.1.0.2 150.1.0.3 Interface eth ppp1 Metric 1 1 Remark All the NET 140.1 All the SUBNET 150.1.1 128.1.0.3 255.255.0.0 150.1.0.2 255.255.255.0 None
Altium ADR F8 Modification

Interfaces Eth Sub network Mask PPP1 to PPP4 Static Routes Dest @IP 128.1.0.0 140.1.0.0 150.1.0.0 Subnet mask 255.255.0.0 255.255.0.0 255.255.255.0 Next hop 150.1.1.2 150.1.1.2 150.1.1.2 Interface Eth Eth Eth Metric 2 3 1 Remark All the NET 128.1 All the NET 140.1 All the SUBNET 150.1.0 150.1.1.3 255.255.255.0 None
Use of RIP Routing Demon

"RIP" is a routing deamon, 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 a RIP routing domain and must be limited to a length of 15 hops maximum between two equipment pieces requiring exchange of packets within this AS. The maximum distance is taken into account to include the worst-case security. These Autonomous Systems 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.
A6
PN 300-610012-001 Rev. 1c, April 2001
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.
PN 300-610012-001 Rev. 1c, April 2001
A7

ADR Manual

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ADR Manual

Încărcat de

Drepturi de autor:

Formate disponibile

Altium ADR

Installation and Operation Manual

Ports Security Level

Function Power supply Power supply

Security Level SELV1 SELV

SELV SELV SELV SELV SELV SELV

1. SELV = Safety Extra Low Voltage circuit

Declaration of Conformity I hereby declare that the product:

All essential radio test suites have been carried out.

San Jose, 22 March 2001

Intended Use of Equipment

PN 300-610012-001 Rev. 1c, April 2001

Altium Microwave Radio System

PN 300-610012-001 Rev. 1c, April 2001

Chapter 1 Installation and Commissioning

N 56717020103 Rev. 1c, April 2001

STM-1 electrical card (ADR ERE card) allowing a VC4 connection, 3

N 56717020103 Rev. 1c, April 2001

Chapter 1Installation and Commissioning

Figure 1-1. Altium ADR Subrack Installation

N 56717020103 Rev. 1c, April 2001

Installation of a 19" Rack

Installation of an ETSI Rack

N 56717020103 Rev. 1c, April 2001

Chapter 1Installation and Commissioning

N 56717020103 Rev. 1c, April 2001

Connecting Power Supply Ports

Figure 1-2. Connecting Power Supply Ports

"PWRA"/"PWRB" Power Supply Interface

N 56717020103 Rev. 1c, April 2001

Chapter 1Installation and Commissioning

The connector shielding is connected to the equipment ground.

"PWR" Power Supply Interface

N 56717020103 Rev. 1c, April 2001

Figure 1-3. Connecting Motherboard Inputs

N 56717020103 Rev. 1c, April 2001

Chapter 1Installation and Commissioning

Connecting Motherboard Inputs

Comments Normally closed contact of dry loop B

N 56717020103 Rev. 1c, April 2001

Management and Administration Ports

Signal Name DCD DSR RX RTS TX CTS DTR RI GND

* The ADR is seen as DCE.

Figure 1-4. Connection Cable

N 56717020103 Rev. 1c, April 2001

Chapter 1Installation and Commissioning

Pin N 1 2 3 4 5 6 7 and 8 Note:

Signal Name TX_ETH_TIP TX_ETH_RING RX_ETH_TIP NC NC RX_ETH_RING NC

Two LEDs are linked to the "ETH" port:

Left LED, "Activity": Right LED, "Link":

Traffic status indicator Link status indicator

"MNGT" Interface (configured in management use) :

Bit rate Connector

Signal Name GND RXPB GND

Polarity Ground (no connected) (+)

N 56717020103 Rev. 1c, April 2001

Polarity (+) (-) (+) (-) (+) (-) (+) (-)

*In slave contradirectional mode (coming) TXCLK signals are inputs.

MNGT Interface Timing Diagram

X24/V11 2 Mbps Traffic Port

Bit rate Connector Standard connection Adapter Guaranteed range

N 56717020103 Rev. 1c, April 2001

Chapter 1Installation and Commissioning