nera citylink - user manual_2.pdf

7/21/2019 NERA CityLink - User Manual_2.pdf

http://slidepdf.com/reader/full/nera-citylink-user-manual2pdf 1/374

User Manual

CityLink

B4008 Rev. M

© Nera Networks AS

Section I : Equipment Description

Section II : ODU Type I Installation

Section III : ODU Type II Installation

Section IV : ODU Type III Installation

Section V : IDU Installation

Section VI : Preparations for Operation

Section VII : Configuration with NEW-NMS

Section VIII : Fast Ethernet Configuration

Section IX : Troubleshooting

Section X : Appendices



2 B4008 Rev. M

CityLink

This section applies only to CE marked equipment

0889WARNING:Use of this equipment requires a separate

license to be applied for by the operator.

DECLARATION OF CONFORMITY (INFORMAL)

English Hereby, Nera Networks AS, declares that this CityLink is in compliance with theessential requirements and other relevant provisions of Directive 1999/5/EC.

Finnish Nera Networks AS

vakuuttaa täten että CityLink tyyppinen laite on direktiivin 1999/5/EYoleellisten vaatimusten ja sitä koskevien direktiivin muiden ehtojen mukainen.Dutch Hierbij verklaart Nera Networks AS dat het toestel CityLink in overeenstemming is met

de essentiële eisen en de andere relevante bepalingen van richtlijn 1999/5/EGBij deze verklaart Nera Networks AS dat deze CityLink voldoet aan de essentiële eisenen aan de overige relevante bepalingen van Richtlijn 1999/5/EC.

French Par la présente Nera Networks AS déclare que l’appareil CityLink est conforme auxexigences essentielles et aux autres dispositions pertinentes de la directive 1999/5/CE.Par la présente, Nera Networks AS déclare que ce CityLink est conforme aux exigencesessentielles et aux autres dispositions de la directive 1999/5/CE qui lui sont applicables.

Swedish Härmed intygar Nera Networks AS att denna CityLink står I överensstämmelse med de

väsentliga egenskapskrav och övriga relevanta bestämmelser som framgår av direktiv1999/5/EG.Danish Undertegnede Nera Networks AS erklærer herved, at følgende udstyr CityLink overhold-

er de væsentlige krav og øvrige relevante krav i direktiv 1999/5/EFGerman Hiermit erklärt Nera Networks AS, dass sich dieser CityLink in Übereinstimmung mit

den grundlegenden Anforderungen und den anderen relevanten Vorschriften der Rich-tlinie 1999/5/EG befindet“. (BMWi)Hiermit erklärt Nera Networks AS die Übereinstimmung des Gerätes CityLink mit dengrundlegenden Anforderungen und den anderen relevanten Festlegungen der Richtlinie1999/5/EG. (Wien)

Refer to Declaration of Conformity for further details.



B4008 Rev. M 3

CityLink



4 B4008 Rev. M

CityLink



B4008 Rev. M 5

CityLink



6 B4008 Rev. M

CityLink



B4008 Rev. M 7

CityLink

WARNING!

DO NOT remove or insert the

Transmitter Unit with DC power on.

Power to the OutDoor Unit (ODU) is carried on

the coaxial cable between the InDoor Unit

(IDU) and the ODU. Before connecting or

removing the cable, ensure that the primary

power to the IDU has been switched off.

WARNING!

This equipment contains components which are

sensitive to "ESD" (Electro Static Discharge).

It is therefore essential that whenever disassem-

bling the equipment and/or handling PC boards,

special precautions to avoid ESD have to be

made.

These precautions include personnel grounding,

grounding of work bench, grounding of tools and

instruments as well as transport and storage in

special antistatic bags and boxes.

CLASS 1 LASER PRODUCT

IEC825-2: 1993

CAUTION!

The Optical Interface must only be serviced by

qualified personnel, who are aware of the

hazards involved to repair Laser products.

When handling Laser products the following

precautions must be taken:

Never look directly into an open connector

or optical cable

Before disconnecting an optical cable, the

power should be switched off. If this is not

possible, the cable must be disconnected

from the STM-1 output before it is discon-

nected from the STM-1 input.

When the cable is reconnected it must beconnected to the STM-1 input before it is

connected to the STM-1 output.

CAUTION!Exposure to strong high frequency electromag-

netic fields may cause thermal damage to

personnel. The eye (Cornea and lens) is easily

exposed.

Any unnecessary exposure is undesirable and

should be avoided.

In Radio-Relay communication installations,

orderly setup for normal operation, the general

RF radiation level will be well below the safety

limit.

In the antennas and directly in front of them the

RF intensity normally will exceed the danger

level, within limited portions of space.

Dangerous radiation may be found in the

neighbourhood of open waveguide flanges or

horns where the power is radiated into space.

To avoid dangerous radiation the following

precautions must be taken:

During work within and close to the frontof the antenna; make sure that transmitters

will remain turned off.

Before opening coaxial - or waveguide

connectors carrying RF power, turn off

transmitters.

Consider any incidentally open RF

connector as carrying power, until

otherwise proved. Do not look into coaxial

connectors at closer than reading distance

(30 cm). Do not look into an open wave-guide unless you are absolutely sure that

the power is turned off.

Use of controls or adjustments or perform-

ance of procedures other than those specified

herein may result in hazardous radiation

exposure.



8 B4008 Rev. M

CityLink

List of Revisions

Rev. Date What is changed

C 01-10-05 ODU Type II Installation introducedD 01-12-18 ODU Type III Installation introducedE 02-02-28 Section II; 13 & 15GHz ODU included.

Section IV; Additional info on installation added.Section VII Chapter 5.2 Switch Criteria changed.Section IX: Additional info about connectors and interfacesin Appendix 1

F 02-05-07 Fast Ethernet introduced

Section VII; New subchapter 5.1.5 Reconfiguring a 1+0IDU for use in Hot StandBy ConfigurationG 02-09-18 21x2Mbit/s (CityLink ADM) introduced.

Section VIII: Updated bitmaps in Ch. 16.6 and 16.8.H 02-10-07 Frequency tuning of 13GHz Transceiver included (Section II

Chapter 5.0).I Not usedJ 02-12-19 Section V: New chapter 4.0 Installation of 21x2Mbit/s

Tributary Unit

K 03-05-23 Section II: Chapter 5.0; new frequency (Table II-5)Installation of ODU Type I on Type III suspension introducedSection IV: New subchapter: Mounting the transceiver (without antenna) to a column.Section VIII: Changed bitmaps in Ch. 16.1, 16.2, 16.6 and16.8, Changes in Ch. 8.9.1 and 8.9.2. New commandsincluded in Ch. 3.0 and 4.0.Section X: New alarms in Alarm list

L 03-11-25 DMD IDU introduced. ADM STM-1 and DS3/E3 ext.boards

introduced . New optical interfaces (2NYD5392A and2NYD5368A) introduced.

M 04-10-26 New Version of NEW. (Section VII and VIII) Added info about System Configuration (Section I) Added info about IP Routing (Section VII)Section X: Improved description of Power Connector



B4008 Rev. M 9

CityLink

Table of Contents

SECTION I Equipment Description .................. 21

1.0 Introduction ................................................................. 22

2.0 IDU ................................................................................ 24

2.1 IDU Description ................................................... 242.2 Hot Standby IDU Description............................... 262.3 Line Interface Boards .......................................... 282.4 Service Telephone .............................................. 282.5 21x2Mbit/s Extension Board (option) ................... 302.6 ADM STM-1 (X-Connect) Extension Board (option) 302.6 3xDS3/E3 and DS1 Extension Board (option) .... 322.6 Ethernet Extension Board (CityLink Fast Ethernet) 33

3.0 ODU .............................................................................. 34

3.1 ODU Type I Description ...................................... 343.2 ODU Type II Description ..................................... 363.3 ODU Type III Description ..................................... 38

4.0 Management ................................................................ 40

5.0 System Configurations ............................................... 40

5.1 1+0Configuration ................................................. 415.2 Hot Standby Configuration .................................. 425.3 1+1 Frequency Diversity ..................................... 425.4 Hot Standby Configuration – Dual Antenna ......... 43

5.5 Hot Standby Configuration – Dual Baseband ...... 445.6 2+0 Configuration ................................................ 455.7 Space Diversity ................................................... 465.8 Hybrid Space Diversity ........................................ 465.9 Radio Terminal Configurations............................ 485.10 Radio Repeater Configurations ........................... 485.11 Radio Channel Identification ................................ 48



10 B4008 Rev. M

CityLink

4.0 ODU / Antenna Installation,

Hot Standby Equipment and 2+0 Equipment ........... 70

SECTION II Installation of

ODU Type I and Antenna................. 49

1.0 General ........................................................................ 50

1.1 Packing ............................................................... 501.2 Marking ................................................................ 501.3 Transportation ..................................................... 501.4 Radio Equipment Inventory Check ...................... 511.5 Preparation for Installation ................................... 511.6 Handling & Storage ............................................. 51

2.0 Installation Equipment required................................ 52

2.1 Tools ................................................................... 522.1.1 Tools for Antenna Installation .............................. 522.1.2 Tools for IDU- ODU Cable /Connector Mounting. 522.2 Equipment external to the Radio Equipment ....... 53

3.0 ODU / Antenna Installation, 1+0 Equipment ............. 54

3.1 Installation of 0.6m and 0.45m Antenna ............. 543.1.1 Preparing the Suspension for ODU Mounting ..... 543.1.2 Mounting the Antenna to the Suspension ............ 55

3.1.3 Mounting the Branching Support Bracket ............ 563.1.4 Mounting the Rear Travers .................................. 573.1.5 Mounting the Suspension Support Bracket ......... 573.1.6 Mounting the Bend on the Branching Unit ........... 583.1.7 Installation of the Branching Unit ........................ 593.1.8 Attachment of the Sunshield Support .................. 593.1.9 Installation of the Flexible Waveguide ................ 603.1.10 Installation of the Sunshield ................................ 61

3.1.11 Mounting the Suspension/Antenna to a Column or a Wall ............................................ 62

3.1.12 Mounting the ODU to the Antenna Assembly ..... 653.1.13 Pole Mount ......................................................... 673.2 Installation of 1.2m Antenna ............................... 683.2.1 Assembly of Branching Support Bracket ............ 683.2.3 Installation of Branching Unit,

Sun-shield and Flexible Waveguide .................... 69



B4008 Rev. M 11

CityLink

4.1 0.45m and 0.6m Antenna ................................ 704.1.1 Installation of Hot Standby (HSB) and 2+0

Dual Frequency Single Polarization Equipment . 704.1.1.1 Preparing the Suspension for ODU Mounting

and Mounting the Antenna to the Suspension . 70

4.1.1.2 Mounting the Branching Support Bracket ........ 704.1.1.3 Mounting the Rear Travers, Mounting the

Suspension Support Bracket and Mountingthe Feed on the Branching Unit....................... 71

4.1.1.4 Installation of the HSB Branching Unit............. 714.1.1.5 Installation of the Flexible Waveguide ............. 724.1.1.6 Installation of the Sunshield Support Bracket .. 734.1.1.7 Installation of the Sunshield............................. 73

4.1.1.8 Mounting the Suspension/ODU to aColumn or a Wall ............................................ 74

4.1.1.9 Mounting the ODU to the Antenna Assembly .. 744.1.1.10 Pole Mount ...................................................... 754.1.2 Installation of 2+0 Equipment

(Single Frequency Dual polarity) ..................... 764.1.2.1 Preparing the Suspension for ODU Mounting

and Mounting the Antenna to the Suspension . 764.1.2.2 Mounting the Branching Support Bracket, the

Rear Travers, the Suspension Support Bracketand the Feed on the Branching Units ................ 76

4.1.2.3 Installation of the Branching Units ................... 764.1.2.4 Installation of the Flexible Waveguide ............. 774.1.2.5 Installation of the Sunshield............................. 784.1.2.6 Mounting the Suspension/ODU to a

Column or a Wall ............................................ 794.1.2.7 Mounting the ODU to the Antenna Assembly .. 794.1.2.9 Pole Mount ...................................................... 804.2 1.2m Antenna.................................................. 814.2.1 Assembly of Branching Support Bracket ........ 814.2.2 Installation of Branching Unit, Sun-shield and

Flexible Waveguide ......................................... 824.2.2.1 Hot Standby and

2+0 Dual Frequency Single Polarization ......... 824.2.2.2 2+0 Single Frequency Dual Polarization ......... 83



12 B4008 Rev. M

CityLink

5.0 Frequency Tuning at 13GHz &15GHz Transceiver ... 84

6.0 Cable Connections ..................................................... 90

7.0 Antenna Alignment ...................................................... 90

SECTION III Installation of

ODU Type II and Antenna .................. 91

1.0 General ........................................................................ 92


2.0 Installation Equipment required ................................ 94

2.1 Tools ................................................................... 942.1.1 Tools for Antenna Installation .............................. 942.1.2 Tools for IDU- ODU Cable /Connector Mounting. 942.2 Equipment external to the Radio Equipment ....... 95

3.0 ODU Installation .......................................................... 96

3.1 Mounting the ODU to the Pole ............................. 963.2 Cable Connections.............................................. 97

4.0 Antenna and Waveguide Installation ........................ 98

4.1 0.6m Antenna ...................................................... 984.2 1.2m Antenna ...................................................... 994.3 2m Antenna ......................................................... 1004.4 2.4m .................................................................... 1014.5 3m ....................................................................... 102



B4008 Rev. M 13

CityLink

SECTION IV Installation of

ODU Type III and Antenna ............ 103

1.0 General ........................................................................ 104


2.0 Installation Equipment required................................ 1062.1 Tools ................................................................... 1062.1.1 Tools for Antenna Installation and Adjustment .... 1062.1.2 Tools for IDU- ODU Cable /Connector Mounting. 1062.2 Equipment external to the Radio Equipment ....... 107

3.0 ODU / Antenna Installation, 1+0 Equipment ............. 108

3.1 Mounting the Antenna to the Suspension ............ 108

3.2 Mounting the Sunshield ....................................... 1093.3 Mounting the Suspension/Antenna toa Column by using the U-bolts ............................ 110

3.4 Mounting the Suspension/Antenna toa Column by using the Clamps ........................... 111

3.5 Mounting the Transceiver (without Antenna) to a Column ............................ 112

3.6 Mounting the Suspension/Antenna to a Wall ....... 117

3.7 Mounting the ODU to the Antenna Assembly ...... 118

4.0 ODU / Antenna Installation, HSB and 2+0 Equipment 121

4.1 Preparing the Suspension ................................... 1214.2 Mounting the Antenna to the Supension .............. 1224.3 Mounting the Hybrid Frame to the Antenna ......... 1234.3 Mounting the CityLink III ODUs to

the Antenna Assembly ........................................ 125

4.4 Mounting the Transceiver (without Antenna) to the Column ......................... 126

4.5 Mounting the Suspension/Antenna to a Wall ....... 126



14 B4008 Rev. M

CityLink

5.0 Cable Connections ..................................................... 127

6.0 Antenna Alignment ...................................................... 128

6.1 Azimuth and Elevation Adjustment...................... 1286.2 Coarse adjustment.............................................. 128

6.3 Fine adjustment .................................................. 1286.4 Final Control ........................................................ 1296.5 Polarisation alignment ......................................... 129

SECTION V IDU Installation............................... 131

1.0 General ........................................................................ 1321.1 Packing ............................................................... 1321.2 Marking ................................................................ 1321.3 Transportation ..................................................... 1321.4 Radio Equipment Inventory Check ...................... 1331.5 Preparation for Installation................................... 1331.6 Handling & Storage ............................................. 133

2.0 IDU Installation ............................................................ 1342.1. Mounting the IDU in an ANSI (19") or an ETSI Rack ... 1342.2 Cable Installation ................................................. 135

3.0 Hot Standby IDU Installation ...................................... 136

3.1 Mounting the Hot Standby IDUs in a Rack........... 1363.2 Interconnections in a Hot Standby System ......... 137

4.0 Installation of Optional Extension Boards ............... 138

5.0 IDU/ODU Cable Installation........................................ 141

6.0 Change of Fan-Cassette ............................................ 146

SECTION VI Preparations for Operation ........ 147

1.0 General ........................................................................ 148



B4008 Rev. M 15

CityLink

1.1 Equipment required ............................................. 1481.2 Connections ........................................................ 148

2.0 Power on ...................................................................... 148

2.1 NEW-NMS/NEW-Configurator Startup and

connecting to Network Elements ........................ 1492.1.1 Starting NEW-NMS/NEW-Configurator with

Serial Connection (RS-232/ LCT). ...................... 1492.1.2 Starting NEW-NMS/NEW-Configurator with

TCP/IP Connection. ............................................ 1502.2 Initial configuration ............................................... 150

SECTION VII Configuration by NEW Configurator 151

1.0 General ........................................................................ 152

2.0 Element Node.............................................................. 154

2.1 Element Id ........................................................... 1542.2 Available Functions ............................................. 156

2.3 Notifications......................................................... 1572.4 NE Clock Page .................................................... 1592.5 Software Download ............................................. 1602.6 Software Versions ............................................... 161

3.0 Transmission Node..................................................... 163

3.1 Section Termination ............................................ 1633.1.1 Section Termination, SW-version < R2A00 ........ 163

3.1.2 Section Termination, SW-version ³ R2A00 ......... 1643.1.3 SSM - Synchronization Status Message ............. 1723.2 Alarm Indication Signal Insert .............................. 1733.3 Path Trace .......................................................... 176

4.0 Equipment Node ......................................................... 178

4.1 Network Routing.................................................. 1784.2 IP Routing............................................................ 181

4.2.1 General Settings ................................................. 1824.2.2 Active Routes ...................................................... 184



16 B4008 Rev. M

CityLink

4.2.3 Static Routes ...................................................... 1854.2.4 RIP Interfaces ..................................................... 1864.2.5 OSPF Interfaces ................................................. 1874.2.6 OSPF Areas........................................................ 1884.3 Communication Ports ......................................... 189

4.3.1 DCC (Data Communication Channel) ................ 1894.3.2 NI (Network Interface) .......................................... 1914.3.3 LCT ..................................................................... 1934.3.4 Ethernet .............................................................. 1944.3.5 IP Settings ........................................................... 1954.3.6 IP Tunneling ........................................................ 1964.3.7 OSI TP4 Tunneling .............................................. 1974.4 Looping ............................................................... 198

4.4.1 Main Looping ....................................................... 1984.4.2 64 Kbit/s Looping ................................................ 2004.4.3 2 Mbit/s Wayside Looping ................................... 2024.4.4 21x2Mbit/s Looping.............................................. 2054.4.5 DS3/E3 Looping .................................................. 2074.5 In Door Unit (IDU) ................................................ 2104.5.1 IDU Production Data ........................................... 2104.5.2 64 kbit/s Channels .............................................. 2114.5.3 2 Mbit/s Wayside Channel .................................. 2134.5.4 SOH X-Connect .................................................. 2154.5.5 Error Pulse Output .............................................. 2164.5.6 Auxiliary Output Configuration ............................. 2174.5.7 Diagnose ............................................................. 2194.5.8 Self Test .............................................................. 2204.5.9 BER Thresholds ................................................. 2204.5.10OSI Configuration ................................................ 2224.5.11Laser Control ...................................................... 2274.5.12IDU Replace Unit Wizard .................................... 2294.6 Out Door Unit (ODU)........................................... 2304.6.1 Type I ODU ......................................................... 2304.6.2 Type II ODU......................................................... 2354.6.3 Type III ODU........................................................ 2474.6.4 Antenna Data ...................................................... 2524.6.5 ODU Replace Unit Wizard .................................. 253

5.0 CityLink ADM ............................................................... 254



B4008 Rev. M 17

CityLink

5.1 21x2 Mbit/s Extension Board ............................... 2545.1.1 Drop or Continue ................................................. 2545.1.2 PRBS Test - Check ............................................ 2585.1.3 PRBS Test - Generators ..................................... 2605.1.4 Production Data - 21x2Mbit/s Extension board ... 262

5.2 DS3/E3 Extension Board .................................... 2635.2.1 DS3/E3 Configuration ......................................... 2635.2.2 DS3/E3 Frame Structure Configuration .............. 2655.3 ADM STM-1 Extension Board (X-Connect) ......... 2675.3.1 X-Connect Frame Structure Configuration.......... 2675.3.2 X-Connect Configuration ..................................... 268

6.0 Hot Standby ................................................................. 270

6.1 General ............................................................... 2706.1.1 Functionality ........................................................ 2706.1.2 Element ID .......................................................... 2716.1.2 Looping Configuration ......................................... 2736.1.3 Hot Standby Configuration .................................. 2756.1.4 Hot Standby Switching Criteria ............................ 2766.1.4 Reconfiguring a Hot Standby IDU for

use in 1+0 Configuration ..................................... 2786.1.5 Reconfiguring a 1+0 IDU for

use in Hot StandBy Configuration ...................... 278

SECTION VIII CityLink Fast Ethernet Configuration 279

Hyperterminal & Telnet .................................................... 280

1.0 Hyperterminal & Telnet Commands .......................... 280

2.0 How to get this link alive............................................ 281

2.1 How to get this link alive, parameters .................. 2812.2 Testing ................................................................ 281

3.0 Top Level Commands ................................................ 282

3.1 Top Level Commands, Example ......................... 283



18 B4008 Rev. M

CityLink

4.0 Submenu Commands.................................................. 284

4.1 EEB Submenu .................................................... 2844.2 Baseband Submenu ........................................... 2854.3 Modem Submenu (part of IDU) ........................... 2864.4 Radio Submenu (part of ODU)............................ 287

4.4.1 Radio Status, Example ....................................... 2884.4.2 Radio Commands, Example of Error Message .. 2884.5 SU Submenu (part of IDU) .................................. 2894.6 Security Submenu .............................................. 2894.7 Performance Submenu....................................... 2904.8 Configuration Submenu ...................................... 2904.8.1 Management Settings ......................................... 2914.9 Test & Fault Submenu ........................................ 291

4.10 Q1module Submenu ........................................... 292

5.0 Software Upgrade Procedure for

the CityLink Fast Ethernet Device ............................ 293

5.1 How to download a file to the IDU:....................... 2945.1.1 Using the Console FTP Client ............................. 2945.1.2 Using the Internet Explorer .................................. 2955.2 How to download a file to the ODU ..................... 296

NEW Network Management System ............................... 297

6.0 Start NEW-NMS & Connect........................................ 297

7.0 Network Element Configuration ................................ 300

8.0 Element Node.............................................................. 3028.1 Element Id ........................................................... 3028.2 NE Clock ............................................................. 3038.3 Software Versions ............................................... 3048.4 Production Data .................................................. 3058.5 SNMP Agent(s) Settings ..................................... 3068.6 Trap Table ........................................................... 3088.7 MIB II - System Group ......................................... 309

8.8 MIB-II SNMP Group.............................................. 3118.9 Looping ............................................................... 3128.9.1 Main Traffic Loops ............................................... 313



B4008 Rev. M 19

CityLink

8.9.2 Wayside Loops ................................................... 3158.9.3 64 kbit/s Loops .................................................... 316

9.0 In Door Unit (IDU) ....................................................... 317

9.1 64 kbit/s Channels .............................................. 317

9.2 Ethernet Extension Board ................................... 3179.2.1 Ethernet Ports ..................................................... 3189.2.2 2 Mbit/s Ports ...................................................... 3199.3 Wayside Channel ................................................ 3209.4 Auxiliary Output ................................................... 3219.5 BER Thresholds ................................................. 3239.6 Laser Control ...................................................... 325

10.0 Out Door Unit (ODU) .................................................. 327

10.1 Antenna Data ...................................................... 32710.2 Power Settings.................................................... 32810.3 Frequency Settings ............................................. 330

11.0 Performance ................................................................ 332

11.1 G826 Performance.............................................. 33211.2 Port Performance ............................................... 33411.3 Repeater Performance ....................................... 335

12.0 Fault .............................................................................. 336

12.1 NE Alarm Log ...................................................... 336

13.0 Security ........................................................................ 337

13.1 Security Log ........................................................ 337

SNMP & MIB Description ................................................. 338

14.0 General ........................................................................ 338

15.0 Supported MIB’s ......................................................... 338

16.0 MIB Overview ............................................................. 339

16.1 Unit ...................................................................... 34016.2 IDU ...................................................................... 341



20 B4008 Rev. M

CityLink

16.3 ODU .................................................................... 34216.4 Test Manager ...................................................... 34316.5 Performance Manager ........................................ 34416.6 Fault Manager ..................................................... 34516.7 Analogue Value ................................................... 346

16.8 Security Manager ................................................ 346

SECTION IX Troubleshooting ......................... 347

1.0 General ........................................................................ 348

2.0 Description of Alarm LEDs ......................................... 3482.1 IDU Alarm LEDs.................................................. 3482.2 HSB-IDU Alarm LEDs and Switch Indicators ..... 3482.3 LEDs on Line Interface Plug-in Boards ............... 349

3.0 Troubleshooting by NEW-NMS Configurator .......... 349

3.1 Introduction.......................................................... 3493.2 Information Acquisition ........................................ 349

3.2.1 Polling ................................................................. 3493.2.2 Event Notification ................................................ 3503.3 Alarm Presentation.............................................. 3503.4 Visual Alarm Notification...................................... 3513.4.1 Alarms on a Tree node/leaf in the Explorer view . 3513.4.2 Alarms on a Node symbol in the Map view .......... 3523.4.3 Viewing Alarms in the Current Alarms View ........ 353

SECTION X Appendices................................... 355

Appendix I: IDU / HSB-IDU Interface Description.................. 356

Appendix II: ODU Interface Description ................................. 370

Appendix III: Alarm List & Alarm Description.......................... 371



B4008 Rev. M 21

Equipment Description

Equipment

Description

SECTION I



22 B4008 Rev. M

CityLink

1.0 IntroductionCityLink is a super compact SDH radio-relay transmission system with STM-

1 capacity. The equipment is split mounted with one single coaxial cable

between the InDoor Unit (IDU) and the OutDoor Unit (ODU). The ODU and

antenna can be located up to 300 meter apart from the IDU. The equipmentis available in 1+0 (single), 2+0 or 1+1 hot standby configurations. Various

line and tributary interface options are available as plug-in modules. The

equipment is also prepared for 21x2Mbit/s terminal multiplexer functionality.

The network applications foreseen for this equipment are mainly for in-

creased connectivity in urban area as well as closure of fiber optic rings.

Additionally, in the fixed part of mobile networks, this equipment is

suitable.

Built-in supervision enables easy installation and configuration, and sys-

tem status and availability data may be recorded. Advanced management

with standardized use of the Embedded Control Channel (ECC) allows for

easy access to this equipment. Broadband RF design enables easy channel

selection.



B4008 Rev. M 23


Key features• Easy installation

• Frequency agility

• 155 Mb/s Line interface plug-ins available:

Unbalanced 75Ω coaxial

Balanced, Category 5 UTP, 100ΩSingle Mode fiber optic

Multi Mode fiber optic

• SW managed configuration of 32, 64 and 128 TCM modulation

• SW managed configuration of STM-0 or STM-1 capacity

• 21x2Mbits/s terminal multiplexer option

• 3xDS3/E3 and DS1 option

• ADM STM-1 option (STM-1 cross-connect)

• Fast ethernet radio option

• 64kbit/s and 2Mbit/s insert channels• Service Channel / Engineering Orderwire

• Line extensions (2) for Service Channel

• Built-in diagnostics with local and remote loopback

• Available Configurations:

1+0 (Unprotected) (STM-1 & STM-0)

1+1 (Hot Standby) (STM-1 & STM-0)

2+0 Dual frequency, Single Polarisation (DF-SP) (2xSTM-1 & STM-0)

2+0 Single frequency, Dual Polarisation (SF-DP) (2xSTM-1 & STM-0)

• High system gain

• Automatic/Manual Transmitter Power Control (ATPC/MTPC)

• Standardized use of the ECC

• Embedded SNMP (Option)

• 14, 28, 50 & 55 (56) MHz channel arrangements

• 2MHz synchronization interfaces (SETS)

• Interface for local and subnetwork management (LAN or RS-232)



24 B4008 Rev. M

CityLink

2.0 IDU

2.1 IDU Description

Figures X-1 shows the IDU front layout. All the connectors are located on

the front for easy operation. In addition to the line interface, 2Mbit/s

wayside and 64kbit/s data channels are available. As options, a 21x2 Mbit/

s terminal multiplexer, ADM STM-1 (X-Connect) or DS3/E3 can be config-

ured by adding a second circuit board. The IDU is equipped with an

integrated supervisory system for local and remote configuration and

control. The supervisory system communicates with the ODU by use of an

FSK modulated channel on the coaxial cable. The same coaxial cable also

carries power to the ODU. For configuration and management purposes the

IDU is equipped with two LCT interfaces for connection to the PC, one with

RS-232 interface and one LAN TP interface. In addition NI interfaces for

connection to other IDUs or other Nera equipment are provided. A SETS

function is incorporated into the unit, conforming to ITU-T rec. G.823 with

balanced 120Ω interface. The IDU has a connector for alarm input/output

functionality (ALM/AUX). Alarm and warning LEDs are located on right

hand side of front. Located close to the power connector is a power indicating

LED.

Figure I-1 shows a block schematic view of the IDU with various optional line

interface plug-in boards and also a 21x2 Mbit/s Extension Board. In radiotransmit direction, the 155 Mb/s input signal from the line interface board is

fed to the “SORP” ASIC. It performs all the SOH processing and radio

scrambling. Then, the TX FPGA encodes the signal by use of a convolution

code and an optional Reed Solomom code. The signal is then mapped into

a “32TCM”, “64TCM” or “128TCM” constellation, as required. It also

performs the necessary pulse shaping by use of a digital FIR-filter. The signal

is then digitally I-Q modulated, and the 350MHz IF signal is fed to the ODU

interface and applied to the IF coaxial connector. In receive direction the

140MHz IF from the ODU will interface the IDU on the same connector. Thenecessary cable equalizing functions are provided in the ODU interface and

the equalized IF is presented to the coherent demodulator. From the demod-

ulator the signal is fed to the RX FPGA, which perform slope equalization and

receive filtering. Then the “ATDEC” ASIC, performs Trellis decoding, by use

of soft decision and the “Viterbi” algorithm for error correction. The optional

Reed Solomon decoding is performed in the RX FPGA. The decoded signal

is then fed to the SORP ASIC for radio descrambling and SOH processing,

and is finally fed to the line interface board.



B4008 Rev. M 25


Figure I-1 Block schematic view of the IDU

F i l e : I D U - H R Q I . D S F

L A N ( 1 0 B A S E - T )

2 x N I

4 8 V D C

2 M b / s W A Y S I D E

M O D E M T R A N S C E I V E R

C O M M U N I C A T I O N

D C C

R E G U L A T E D

O U T P U T S

A S I C

D C / D C

T R I B U T A R Y

I N T E R F A C E

B L O C K

N O . 2

F P G A

2 1 x 2 M b / s L I N E I N T F C . / A D D - D R O P E X T E N S I O N B D .

M A I N B D .

T X :

F P G A

M A P P E R

E N C O D E R

F I L T E R

" S O R P "

S T M - 1

O V E R H E A D

A N D

R A D I O

P R O C E S S O R

2 M H z S Y N C

O D U

2 x 6 4 K b / s

A L A R M S

L C T

V 1 1 / G . 7 0 3

I N T E R F A C E

I N T E R P O L A T I O N

M O D U L A T I O N

U P C O N V E R S I O N

O D U

I N T E R F A C E

1 2 1

2 1 x 2 M b / s

G . 7 0 3

G . 7 0 3

A L M / A U X

I N T F C .

1 5 5 M b / s

L I N E

I N T E R F A C E

O p t i c a l M M F ~ 2 K m

o r E l e c t r . C A T 5 U T P

o r E l e c t r . G . 7 0 3

T R I B U T A R Y

D A T A

M A P P E R

N O . 1

T R I B U T A R Y

D A T A

M A P P E R

N O . 1

A S I C ' s

S U P E R -

V I S O R Y

S Y S T E M

F I F O B U S

A S I C

" A T D E C "

T R E L L I S

D E C O D E R

H S B I D U I N T F C .

S V C E

P H O N E

I N T

E R F A C E

P H O N E

2 x P H O N E E X T .

" E 1 "

" H 2 "

S Y N C .

I N T E R F A C E

D / A C O N V E R S I O N

D O W N C O N V E R S I O N

A / D C O N V E R S I O N

R X :

F P G A

C A R R I E R R E C .

D E M A P P E R

C L O C K R E C .

D E C O D E R

O S C .

S O U R C E

O

S C .

S O

U R C E

4 x 3 x

8 7 . 5 M H z

9 3 . 3 M H z

2 x

o r O p t i c a l S M F ~ 4 0 K m





26 B4008 Rev. M

CityLink

2.2 Hot Standby IDU Description

Figure X-2 shows the HSB IDU front layout. The connectors on the front

are identical to the ones used on the IDU and is therefore not further

described here. Additionally, a second power connector is added for

power redundancy enabling separate battery courses. Figure I-2 shows a

block schematic view of the IDU with various optional line interface plug-in boards. Interconnection of data and control signals between IDUs (A and

B) and HSB IDU is by means of a connector and special split cable. This

cable is part of the HSB cable kit. In a 1+1 HSB system, all the customer

interfaces are towards the HSB IDU. These signals are disabled on the IDU

in such a configuration. The same alarm and warning LEDs used on IDU is

also used here. Additionally, a second power indicating LED is located

close to the redundant power connector. Also, an array of four LEDs,

located on the right hand side in close proximity to the alarm/warning

LEDs, indicates switching status in transmit and receive direction.



B4008 Rev. M 27


Figure I-2 Block schematic view of the HSB IDU

(shown here with DS3/E3 Extension Board)

File: HSBIDU-HRQE.DRW

LAN (10BASE-T)

2 x NI

48V DC

2Mb/s WAYSIDEDCC

REGULATEDOUTPUTS

ASIC

DC / DC

TRIBUTARYINTERFACE

BLOCK

FPGA

3xE3/DS3 EXTENSION BD.

MAIN BD HSB IDU.

"SORP"

SDH

OVERHEAD ANDRADIO

PROCESSOR

SYNC.2MHz SYNC

2 x 64 Kb/s

ALARMS

LCT

V11/G.703

INTERFACE

3x34/45 Mb/s

G.703INTERFACE

ALM/AUXINTFC.

155 Mb/s

LINEINTERFACE

TRIBUTARYDATA

MAPPERNO. 1

TRIBUTARYDATA

MAPPERNO. 1

ASIC's

SUPER-VISORYSYSTEM

FIFO BUS

IDU A INTFC. (R)

SVCEPHONE

INTERFACE

PHONE

2 x PHONE EXT.

"E1"

"H1"

IDU B INTFC. (P)

Optical MMF ~2Km

or Electr. CAT5 UTPor Electr. G.703

or Optical SMF ~40Km



G.703

1.5 Mb/s WAYSIDE PHY



28 B4008 Rev. M

CityLink

2.3 Line Interface Boards

Six different versions of 155 Mb/s line interface boards are presently

available as plug-in modules. These are:

• Electrical, 75Ω unbalanced interface bd. according to

ITU-T rec. G.703.• CAT-5 UTP electrical interface bd. according to

ATM Forum rec. af-phy-0015.000.

• Multimode Fiber optical interface bd. according to

ANSI rec. T1.646 and T1.105.06 type “SR-0”.

• Singelmode Fiber optical interface bd. according to

ITU-T rec. G.957, type “S-1.1”.

• Singelmode Fiber optical interface bd. according to

ITU-T rec. G.957, type “L-1.1”.

• Singelmode Fiber optical interface bd. according toITU-T rec. G.957, type “L-1.2”.

In a 1+1 HSB system, the line interface board will only be used on the HSB

IDU. All the interface boards have an input signal indicating LED.

2.4 Service Telephone

A service telephone with collective call is provided in both the IDU and

HSB IDU. In a 1+1 HSB system, the customer interface connection must be towards the HSB IDU.

External connection to two other similar equipment can take place via two

RJ-45 ports on the front. Refer to Appendix I for connector pin-out and

description and Figure I-3 for circuit diagram of the service channel

interface. The balanced interfaces have a nominal level of -6dBm and

600Ω impedance. Connect OUT to INP and vice versa.

Service channel signalling is based on collective call. The DTMF-star

sequence is used as collective call to interface with other Nera equipment.

If other equipment connected have a different calling system than DTMF-

star, they may use CALL INP/CALL OUT. Station ground connected to

CALL INP will start transmission of DTMF-star as well as activating a

buzzer. A detected DTMF-star will activate the CALL OUT by opening an

optocoupler to station ground.

For Nera PDH-radio equipped with Service Board 2NF467A, CALL INP

has to be connected to CALL OUT and vice versa.



B4008 Rev. M 29


Figure I-3 “Service Channel CALL" Circuit Diagram

CALL_OUT/CTRL_OUT

CALL_INP/CTRL_INP

2 B A S 1 6

3 1

2110k

1 BSR19APC3Q66Q1

2BYM12232

1k2 1

16 1

3

15 2BSR19A1

1 3 14

1kPC3Q66Q

24 13

-48V

21 +3.3V10k

CTRLINPCALLINP/

212 CTRLOUT10kCALLOUT/

+5V

A control signal can be transferred over the radio hop. Station ground

connected to CTRL INP will set a signalling bit which is detected on the

other side and activates CTRL OUT by opening an optocoupler to station

ground. See Figure I-3. The control signal is used to control PABX-

adapters and to switch off loudspeakers on Nera service boards with

selective call (e.g. 2NF4688, 2NF533B and 2KNF232A). The controlsignal is transferred only if SOH-byte “E1”, “E2” or “F1” is used for

transmission of service channel.

For setup by NEW, refer to Section VII.



30 B4008 Rev. M

CityLink

2.5 21x2Mbit/s Extension Board (option)

In Figure I-4, a block schematic depiction of a 21x2Mbit/s Extension Board

function are given. This function enables twenty-one 2Mbit/s channels to

be multiplexed/demultiplexed, enabling a terminal multiplex function. It is

possible to configure the unit to drop a certain number of 2Mbit/s channels

while delivering the rest as a part of the STM-1 payload in a “drop-and-continue” configuration. In a standard terminal multiplexer configuration,

the plug-in line interface board is omitted. The 2Mbit/s channels conform to

ITU-T rec. G.703, balanced 120Ω. Also provided on the same circuit board

is the option of using one of the 2Mbit/s channels as SETS reference clock

input/output, according to ITU-T rec. G.823.

In a 1+1 HSB system, this interface board will be mounted in the HSB IDU.

In a 1+0 system it will be included in the IDU.

TRIBUTARYINTERFACE

BLOCKNO. 1

ASIC

21x2 Mb/s LINE INTFC./ADD-DROP EXTENSION BD.

1

21

21x2 Mb/sG.703

TRIBUTARYDATA

MAPPERNO. 1

TRIBUTARYDATA

MAPPERNO. 1

ASIC's

To/fromtheIDU'sSDHOverheadandRadio

Processor (SORP)

Figure I-4 Block schematic view of the 21x2Mbit/s Extension Board

2.6 ADM STM-1 (X-Connect) Extension Board (option)

The Extension Bd. ADM STM-1, which is a part of the Indoor unit in the NERA CityLink, is an optional ITU-T standard STM-1 interface implemented

for 155 Mbit/s signal entry and exit in a ring topology. The STM-1 entry signal

into the ring is split and transmitted to line and radio side in parallel. Signals

exiting the ring are received from line and radio side. These are up to 63xVC-

12s from either side and they are protected, i.e. they shall be switched

individually if a break somewhere in the ring occurs. Also, the system will

handle any allowed combination of VC-3s and VC-12s.

In Figure I-5, a block schematic of the STM-1 Extension Board functions isshown. The STM-1Extension Board will interface one STM-1 line signal in

Tx- and Rx-direction. The STM-1 interface is interchangeable in the following



B4008 Rev. M 31


Figure I-5 Block schematic view of the ADM STM-1 Extension Board

TDM1RADIO

TDM1LINE

TDM1LINE

EXTENSIONBOARD

PLD14FPGA

SORPEXT BOARD

LINEINTERFACE

CARD

IDU CONN

way: In a slot in the STM-1Extension Board, a line interface board is inserted.

Presently one type of board is implemented: The plug-in board compliant

with ITU-T G.703 CMI encoded 155 Mbit/s customer interface; 2LN24C. A

green LED, located on the front of the board indicates presence of an input

signal. The line interface board is mounted on the extension board prior to

this being mounted within the IDU cabinet. This means that the line interface board will not be used as a plug-in type board in this application.

SOH processing and line scrambling /descrambling on the STM-1 interface

are performed by the SORP ASIC. The TDM1 ASICs perform insertion,

extraction, signal processing and cross-connection of data in the payload

of the STM-1 frame and also make error and performance measurements on

VC-3 and error measurements on VC-12. The PLD14 FPGA makes perform-

ance measurements on VC-12s embedded in the STM-1 datastreams from

two TDM1 ASICs. The measurement results are used to choose individualVC-12s from the two datastreams in TDM1 ASIC no.1 and TDM1 ASIC no.2.

The selection is done by the SU in TDM1 ASIC no. 3. See Figure I-5.

TDM1 ASIC no 1—— →

PLD14 FPGA——————— →

TDM1 ASIC no 3 ———————— →

TDM1 ASIC no 2 ————————-→

SORP ASIC no 2 ————————— →

Line Interface Board ———————-→



32 B4008 Rev. M

CityLink

2.6 3xDS3/E3 and DS1 Extension Board (option)

DS3 is a 45Mbit/s PDH standard used for the North American marked, E3 is

34Mb/s PDH standard used for the European marked and the DS1 is a

1.5Mbit/s PDH standard used for the North American marked. The 3xDS3/

E3 and DS1 Ext. Bd., which is a part of the Indoor unit in the NERA CityLink,

will perform add-drop of 3xDS3/E3 PDH channels to-from a STM-1 frame. Inadditional it will perform insertion and extraction of 1.5 Mbit/s wayside (DS1/

T1).

InFigure I-6, a block schematic of the 3xDS3/E3 and DS1 Ext. Bd. functions

are shown. The 3xDS3/E3 and DS1 Ext. Bd. will interface three DS3/E3 and

one DS1 line signal in Tx- and Rx-direction. The line interface circuit includes;

cable equalizer, line coding and pulse shaping functions. This is performed

by two Line Interface Unites (LIU), one for DS3/E3 an one for DS1. SOH

overhead and radio processor is located oh the motherboard in the IDU.

The PLD15 FPGA maps the 3xDS3/E3 into three VC3s, then into a VC4 and

then into a STM-1 signal and de-maps in the opposite direction. The STM-

1 signal is locked to a 2.048 MHz input (SETS) coming from the motherboard.

The TDM1 ASIC performs insertion, extraction and cross-connection of

data in the payload of the STM-1 frame. Together, the two TDM1s and PLD15

implement the core of a DS3/E3 add-drop multiplexer. The 1.5 Mbit/s

Wayside (DS1/T1) function is implemented in PLD15 and is independent of

the TDM1 ASICs.

Figure I-6 Block schematic view of the 3xDS3/E3 Extension Board

3xDS3/E3 and T1 EXT. BOARD

48 V

+3.3 V

+1.5 V

TDM1

No. 1

LINE

TDM1

No. 2

RADIO

3xDS3/E3

DC/DC

T1 LIU

PLD15

IDU CONNECTOR



B4008 Rev. M 33


2.6 Ethernet Extension Board (CityLink Fast Ethernet)

In Figure I-7, a block schematic description of an Ethernet Extension Board

(EEB) is given. This function enables 4 separate Ethernet channels 10BASE-

T/100BASE-TX and 4 separate 2Mbit channels conforming to ITU-T rec.

G.703. The EEB will treat all 8 channels separately, meaning that all data

entering on one channel will leave on the same channel on the other side of the radio hop. All channels are full duplex. The four Ethernet and four 2Mbit/

s channels shares the STM-1 data capacity. The 2Mbit channels, if enabled,

will always be guaranteed full bandwidth. The 4 Ethernet channels can be

configured to either equally share the STM-1 data frame, or one channel can

be given priority. The EEB has a limited on board Ethernet package buffer

capacity. This gives the ability to handle short time 100Mbit/s bursts on all

four channels without package loss. Also the EEB supports flow control,

making it possible to configure a 400Mbit full duplex network without

package loss, even though the radio hop is limited to STM-1 data rate.

To from IDU

main board

4x RJ45

Ethernet

4x RJ45

2Mbit

Ethernet to/fromSTM1 and 2Mbit

mapper/demapper

Ethernet

Interface

2/1.5Mbit

Interface

Figure I-7 Block schematic view of the Ethernet Extension Board

2 Mbit/s

Interface

Ethernet to/from

STM1 and 2Mbit/s

mapper/demapper



34 B4008 Rev. M

CityLink

3.0 ODU

3.1 ODU Type I Description

The ODU Type I is an assembly of branching unit and transceiver unit

mounted behind the antenna or on a mounting frame on a pole/column. The

ODU is connected to the IDU with a single coaxial cable. The coaxial cable provides Tx-IF, Rx-IF, signalling and power supply. For flexibility and easy

installation, the coaxial cable is con-

nected to the transceiver through the

branching unit. The transceiver is at-

tached to the branching with a snap on

system. With this solution, the coaxial

cable may remain connected during

transceiver replacement. In 1+0 con-

figuration the branching unit is for a

single transceiver and in Hot Standby

configurations the branching is for dual

transceivers. The ODU and the antenna

are assembled very closely together

making it very compact. Nevertheless

the antenna can be separated from the

ODU by use of a flexible waveguide.

The branching unit contains RF channel filters, circulators and overvoltage

protection. The Hot Standby branching contains in addition a RF switch for

transmit direction and a RF power splitter for the receive direction.

The transceiver unit contains a microwave Tx/Rx module, a synthesised

local oscillator and a transceiver main board, all in a waterproof housing.

The transceiver is based on dual frequency conversion in the transmitter

and triple conversion in the receiver. This radio architecture with high IF

frequencies allows for use of wide band branching filters while stillmaintaining excellent spectrum purity in transmitter and high selectivity

in receiver. The use of wide band branching filters allows for a wide choice

of remote channel frequency selection without changing hardware.

The microwave module is an integrated multi-chip module with GaAs

HEMT MMICs for Power Amplifier and Low Noise Amplifier. The

necessary LO frequencies for the frequency converters are generated in

a low phase noise synthesiser unit. The channel frequency is remotely

programmed from the indoor unit. Transmit/receive IF-chain, control-

circuits, signalling and power supply are integrated on the transceiver main

board.



B4008 Rev. M 35


Figure I-8 Block schematic view of the ODU Type I, 18GHz, in 1+0 configuration

T R A N S C E I V E R

U N I T

1 4 0 M H z

3 5 0 M H z

I F I N / O U T

M / T C O M

D C P W R

B R A N C H I N G

U N I T

T

R A N S C E I V E R M A I N B O A R D

M I C R O W A V E M O D U L E

X N

A N T E N N A

U N I T

P W R

S Y N T H E S

I Z E R

D U P L E X

F R E Q

7 G H z

F I X E D

2 1 0 M H z

P R E -

D I S T

2 G H z

S Y N T H

U H F L O

C A B .

E Q .

I F I N / O U T

U H F L O

C T R

L / M / T C O M / P O W E R

I F L O O P

3 5 0 M H z

U H F

I F

3 5 0 M H z



36 B4008 Rev. M

CityLink

3.2 ODU Type II Description

The Type II of the ODU consists of a weatherproof

box containing the branching system. The ODU

box is mounted on a pole/column behind the anten-

na. The Transceiver unit is a plug-in unit mounted in

the box. In 1+0 configuration the ODU box con-tains a 1+0 branching unit for a single transceiver

and in Hot Standby configurations the ODU box

contains a Hot Standby branching unit and dual

transceivers. The branching unit contains RF chan-

nel filters and the diplexer. The Hot Standby branch-

ing contains in addition an RF switch for transmit

direction and an RF power splitter for the receive

direction.

The transceiver unit contains 7 modules/sub-units;

a microwave transmitter module, a receiver mod-

ule, 3 local oscillators, an IF &controller board and a detector board. The

transceiver is connected to the modem/IDU with a single coaxial cable that

carries Tx-IF, Rx-IF and signalling (MTcom). Power is supplied through

a separate connector (D-sub), and for the split mount case this power is

separated from the coaxial cable in the ODU container (box).

The transceiver utilises a single conversion scheme in the transmitter and

a dual conversion in the receiver. In order to obtain an optimum spectrum

mask, the transmitter chain contains predistortion circuitry at IF before

the microwave upconverter and power amplifier. Narrow channel filters in

the branching unit further reduces the spectrum mask. The second convert-

er in the receive chain allows for an IF loop-back facility for diagnostics

purposes. LO frequencies for the microwave frequency converters are

generated in synthesised DROs. The oscillators are by nature fixed in

frequency, i.e. they can only be remotely programmed within a narrowrange. When necessary, the oscillators can be adjusted within a range of

approx. 200 MHz with a mechanical screw (see Section VII Chapter

4.5.2.3 for guidance). Power supply, transmit/receive IF-chain, signalling

and controller (DSP) for the transceiver are integrated on the IF &control-

ler board.

The branching unit contains narrow RF channel filters and circulators.



B4008 Rev. M 37


M u l t i -

p l e x e r

A G C & C a b l e

e q u a l i z e r

P r e d i s t o

r t i o n &

A G C

S S

B

U p c o n

v e r t e r

P o w e r

A m p l i f i e r

L O , I M D m x r

L o w N o i s e

A m p l i f i e r

I M R M i x e r

F L T R &

A G C

D S

B

M i x e r

F L T R &

A G C

M T -

C o m .

C T R L

I M D D e t .

L O D e t .

D C / D C

T x I F

3 5 0 M H z

R x I F

1 4 0 M H z

M T c

o m 4

8 V

3 5 0 M H z

1 4 0 M H z

T x -

S y n t .

R x -

S y n t .

I F -

S

y n t .

3 5 0 M H z

S y n t h e s i z e r U n i t

X M T R M o d u

l e

R C V R

M o d u l e

1 4 0 M H z

2 1 0 M H z

T x L O

R x L O

3 5 0 M H z

I F l o o p

I F & C T R L B d .

R F o u t

R F i n

Figure I-9 Block schematic view of the ODU Type II, 7GHz, in 1+0 configuration



38 B4008 Rev. M

CityLink

3.3 ODU Type III Description

Type III of the ODU consists of a single

ODU (in 1+0 configuration) mounted

behind the antenna and attached to the

antenna by means of four snap-on

clamps. The ODU is connected to theIDU via a single coaxial cable which

carries transmitter IF, receive IF and

control and monitoring signals, as well

as DC power. In 2+0 and 1+1 hot stand-

by configurations both ODUs are at-

tached by the same snap-on clamps to a

branching hybrid. This hybrid can ei-

ther be bolted directly to the antenna or

via a short length of flexible waveguide.The branching hybrid contains an RF

splitter and combiner.

The ODU consists of a weatherproof housing containing a microwave

transmit/receive module, a synthesised local oscillator module and an IF

and control transceiver main board. The transceiver is based on a dual up-

conversion and triple down-conversion scheme, which allows the use of

wide-band duplex filters and therefore a wide choice of remote channel

frequency selection. To optimise the transmitter spectrum the transmitter

employs pre-distortion at IF as well as cable equalisation to correct for

variable loss and slope in the cable.

The microwave transmit/receive module consists of a multi-chip module

using a set of GaAs HEMT MMICs, both for the transmitter power

amplifier and the low-noise receiver. The required local oscillator signals

are fed from the synthesised local oscillator module and up-converted

using a diode multiplier. The channel frequency is remotely selected viathe IDU. Transmit/receive IF multiplexing, control and monitoring and

power supply functions are all integrated on the transceiver main board.



B4008 Rev. M 39


M A I N B O

A R D

M I C R O W A V E

C O N V E R T E R

2 1 0 M H z

7 - 9 G H z

S Y N T H E Z I S E R

T R A N S C E I V E R

A N T E N N A

D I P L E X E R

D I P L E X E R

D U P L E X

F R E Q .

U H F L O 1 ( L O 2 ) U

H F L O 2 ( L O 1 )

P R E -

D I S T

S L O P E

E Q U A L I S E R

Figure I-10 Block schematic view of the ODU Type III



40 B4008 Rev. M

CityLink

4.0 ManagementAn integrated supervision system makes the CityLink capable of function-

ing as a Network Element (NE) in a managed SDH transmission network.

Management and supervision of the CityLink can be performed in various

ways from very simple alarm monitoring to standardised managementthrough optional built-in NE agents. Standardised use of QECC

, according

to ITU-T Rec. G.784, is provided.

As an option, the CityLink also supports embedded SNMP agent that can

be controlled by SNMP based manager supplied by the service provider.

For element and network management the NEW-NMS (Nera Element vieW

- Network Management System) software provides the full range of manage-

ment functionality; Fault, Performance, Security and Configuration.

The integrated SNMP agent provides interface to higher level Network

Management Systems.

The alternative interfaces available at the IDU are described in Appendix

I; IDU Interface Description.

5.0 System Configurations

CityLink is available in the following configurations:

Frequency Band L6 – 11 GHz 13 – 15 GHz 18 – 23 GHz 26 – 38 GHz

1+0 (Unprotected) OK

1+1 (Hot Standby) OK

1+1 Frequency Diversity OK NA

1+1 (Hot Standby) – Dual Baseband OK OK OK NA

1+1 (Hot Standby) – Dual antenna TBD TBD TBD OK

2+0 Dual frequency – Single polarisation (DF-SP)

OK

2+0 Single frequency – Dual Polarisation(SF-DP)

NA NA 32 TCM only 32 TCM only 1

2+0 Alternating Polarisation (AP) OK 1

1+0 prepared for 2+0 OK

Table I-1 System Configurations



B4008 Rev. M 41


155 Mb/s

SDH/SONETProcessing

STM-1/OC-3Plug-inLine Interface

M o d u l a t o r

D e m o d u l a t o r

D C p o w e r f e e d i n g

& o v e r v o l t a g e

p r o t e c t i o n

Indoor unit (IDU)

Management&

SNMP Agent

Antenna

Transceiver

Branching

Auxtraffic

Management

OptionalPlug-in

Multiplex Unit

Coaxial cable(up to 300 m)

Figure I-11 1+0 System Overview

5.1 1+0Configuration

This system consists of one indoor unit and one outdoor unit interconnected

with a single coaxial cable.

Figure1-11 shows a 1+0 system overview. Each of the shaded area represents

a function or unit. The IDU is a single unit with plug-in STM-1 line interface

and the optional Multiplexer Unit. The ODU is assembled by transceiver and

branching.

Space Diversity and Hybrid Space Diversity is available as specified in the

table below.

Frequency Band L6 – 11 GHz 13 – 15 GHz 18 – 23 GHz 26 – 38 GHz

Space Diversity with IF combining

1+0,1+1 FD, HSB

OK NA NA NA

Hybrid Space Diversity (HSB) OK NA NA NA

Hybrid Space Diversity (1+1 FD) OK OK OK NA

Table I-2 Space Diversity Configurations



42 B4008 Rev. M

CityLink

5.2 Hot Standby Configuration

In Hot Standby configuration the IDU, the transceiver unit, and the coaxial

cable between IDU and ODU are duplicated. The two transceivers share the

same branching unit/hybrid. A switch at radio frequency level, included in

the branching unit 1, allows for switching between the two transmitters. A

Switching Unit is placed between the two IDUs and performs hitlessswitching in the receive direction. The STM-1 line interface and Multiplex

plug-in modules are mounted in this switching unit. Signal interconnection

between the IDUs and the switching unit is by a multi connector and a split

cable.

1) Some ODU types use a passive combiner/splitter at RF level.

Indoor unit (IDU)

Outdoor unit (ODU)


Antenna unit

SDH/SONETProcessing


M o d u l a t o r


D C p o w e r f e e d i n

g


p r o t e c t i o n

Management

Transceiver Unit

BranchingUnit

SDH/SONETProcessing

M o d u l a t o r




p r o t e c t i o n

Management

Transceiver Unit

Optionalplug-in

Multiplex UnitAux

traffic

Management

Management&

SNMP Agent

SDH/SONETProcessing

155Mbit/s

Figure I-12 1+1 Frequency Diversity and Hot Standby System Overview

5.3 1+1 Frequency Diversity

A 1+1 Frequency Diversity system contains duplicated IDU and ODU and

a 1+1 FD branching. (Dual polarised branching can also be used.). A

switching Unit is placed between the two IDUs and performs hitless

switching in the receive direction. The interface units are mounted in the

switching unit. Signal interconnection between the IDUs and the switching

unit is by a multi connector and a split cable.



B4008 Rev. M 43


5.4 Hot Standby Configuration – Dual Antenna

The Hot Standby configuration is for 26-38 GHz also available with duplicat-

ed antenna. There is no Tx-switch at radio frequency level and the standby

transmitter is muted. Both receivers are active and selection of receive signal

is performed by the IDU-switch. This configuration gives better system gain

as no HSB-hybrid loss is added.

Indoor unit (IDU)

Outdoor unit (ODU)


Antenna unit

SDH/SONETProcessing


M o d u l a t o r




p r o t e c t i o n

Management Transceiver Unit

BranchingUnit

SDH/SONETProcessing

M o d u l a t o r




p r o t e c t i o n

Management

Optionalplug-in

Multiplex UnitAux

traffic

Management

Management&

SNMP Agent

SDH/SONETProcessing

155Mbit/s

BranchingUnit

Transceiver Unit

Antenna unit

Figure I-13 Hot Standby-Dual Antenna System Overview



44 B4008 Rev. M

CityLink

5.5 Hot Standby Configuration – Dual Baseband

A special variant of the Hot Standby system is the Dual baseband option.

In this configuration both IDUs are equipped with STM-1 line interface units.

The switching unit is not used in this configuration. The feature enables line

protection when used with muxes with dual/protected interfaces

Outdoor unit (ODU)


Antenna unit

Transceiver Unit

BranchingUnit

Transceiver Unit

155 Mb/s

SDH/SONETProcessing


M o d u l a t o r




p r o t e c t i o n

Management&

SNMP Agent

Auxtraffic

Management

155 Mb/s

SDH/SONETProcessing

STM-1/OC-3

Plug-inLine Interface

M o d u l a t o r




p r o t e c t i o n

Indoor unit (IDU)

Management&

SNMP Agent

Aux

traffic

Management

Figure I-14 Hot Standby-Dual Baseband System Overview



B4008 Rev. M 45


5.6 2+0 Configuration

The 2+0 system can be used in two types of configuration, using one or two

polarisations. Single Frequency – Dual Polarisation (SF-DP) and Alternating

Polarisation (AP) utilise both polarisations in order to double the capacity.

Dual Frequency – Single Polarisation (DF-SP) requires two channels in order

to transmit 2xSTM-1. With this configuration, adjacent channels cannot beused. Figure I-15 and Figure I-16 show block diagrams of the 2+0 configu-

rations.

155 Mb/s

SDH/SONETProcessing


M o d u l a t o r




p r o t e c t i o n

Indoor unit (IDU)

Management&

SNMP Agent

SDH/SONETProcessing


M o d u l a t o r




p r o t e c t i o n

Indoor unit (IDU)

Management&

SNMP Agent

Outdoor unit (ODU)


Antenna

Transceiver

Branching

Auxtraffic

Management

Auxtraffic

Management

OptionalPlug-in

Multiplex Unit

OptionalPlug-in

Multiplex Unit

Transceiver

Branching

Coaxial cable

(up to 300 m)

H-pol

V-pol155 Mb/s

Figure I-15 Single Frequency - Dual Polarisation / Alternating

Polarisation

SDH/SONETProcessing

M

o d u l a t o r



& o

v e r v o l t a g e

p r o t e c t i o n

Indoor unit (IDU)

Management&

SNMP Agent

SDH/SONETProcessing

M o d u l a t o r


D

C p o w e r f e e d i n g


p r o t e c t i o n

Indoor unit (IDU)

Management&

SNMP Agent

Outdoor unit (ODU)


Antenna

Transceiver

Branching

Transceiver

Auxtraffic

Management

Auxtraffic

Management

OptionalPlug-in

Multiplex Unit

OptionalPlug-in

Multiplex Unit



155 Mb/s

155 Mb/s

Figure I-16 Dual Frequency - Single Polarisation



46 B4008 Rev. M

CityLink

5.7 Space Diversity

Space diversity with IF combining is available in the frequencies from L6 to

11GHz. It can be used in combination with all other configurations. The figure

below shows a 1+1 Frequency Diversity or HSB system.

Outdoor unit (ODU)

Main Antenna

Main Branching

SD Antenna

SDTransceiver

SD Branching

SDTransceiver

Indoor unit (IDU)

SDH/SONETProcessing

M o d u l a t o r


D C p o w e r f e e d i n

g


p r o t e c t i o n

Management

SDH/SONETProcessing

M o d u l a t o r




p r o t e c t i o n

Management


WG


Optionalplug-in

Multiplex UnitAux

traffic

Management

Management

&SNMP Agent

SDH/SONET

Processing

155Mbit/s

Figure I-17 Space Diversity

5.8 Hybrid Space Diversity

Hybrid Space Diversity using standard XCVRs without IF combining is

available for 1+1 FD and HSB.

In HSB configuration the splitter in the receiver branch is omitted and each

receiver is connected to separate antennas. The transmitters are using the

main antenna. Waveguide is needed from the ODU to the SD antenna. Theconfiguration is available for L6-11 GHz systems.



B4008 Rev. M 47


Outdoor unit (ODU)

Main

Antenna

Main Branching

SD

Antenna

Transceiver

SD Branching

Transceiver

Indoor unit (IDU)

SDH/SONETProcessing

M o d u l a t o r




p r o t e c t i o n

Management

SDH/SONETProcessing

M o d u l a t o r

D e m o d

u l a t o r


& o v e r v

o l t a g e

p r o t e c t i o n

Management


WG


Optionalplug-in

Multiplex UnitAux

traffic

Management

Management&

SNMP Agent

SDH/SONETProcessing

155Mbit/s

In 1+1 system hybrid diversity is implemented by using two antennas at one

of the sites. At this site one channel is connected to each antenna. In principle

it is two 1+0 ODU operating at differnet frequencies. At the other site normal

1+1 FD system is used.

Figure I-18 HSB Hybrid Space Diversity

User Interfaces

IDU

IDU

Switch

1+0ODU

1+0ODU

IDU

IDU

Switch

User Interfaces1+1

ODU

f1

f2

Figure I-19 1+1 Hybrid Space Diversity



48 B4008 Rev. M

CityLink

This page is intentionally left blank.

5.9 Radio Terminal Configurations

The radio channel can be configured with RS- or MS-termination according

to ITU-T Rec.G.783.

Figure 1-20 shows examples of various configurations. MST configuration

requires the optional SETS function.

RRT RRT RRTRRT

RS RS RS

MS MSMS

MS Other MSequipment

Other MSequipment

Figure I-20 Configuration Examples

5.10 Radio Repeater Configurations

A radio repeater is built by using two terminals. The interface between the

terminals is at STM-1. The repeater can be configured with RS-termination

according to ITU-T Rec. G.783.

5.11 Radio Channel Identification

The radio channel is identified by two allocated bits in the media specific byte

(MS#3) in the SOH. The channel identification can be configured by the user.



B4008 Rev. M 49

ODU Type I Installation

Installation of

ODU Type I and Antenna

SECTION II



50 B4008 Rev. M

CityLink

1.0 GeneralThis section assumes that pre-planning of the link has been performed, i.e.

path budgeting & survey to ensure good line-of sight between the two link

ends.

1.1 Packing

Any sensitive product, i.e. IDU and Printed Circuit Boards, are packed in

special antistatic handling bags or boxes.

It is therefore essential that whenever unpacking or disassembling the

equipment and or handling printed circuit boards etc., special precautions

to avoid ESD (Electro Static Discharge) should be taken, such as using

wrist grounding or corresponding protection.

The equipment is packed in sealed plastic bags which are equipped with

required moisture protection.

All equipment is further packed in special designed cases prepared for

transportation.

Dimensions and weight of each case are specified in the "Packing

specifications" issued for the respective shipment.

1.2 Marking

Marking is done according to customers requirements. If such informa-

tion is unavailable, the equipment is marked in the following way:

Customer address

Contract No.

Site Name (if known)Case No.

1.3 Transportation

The transport containers are prepared for shipment by air, truck, railway

and sea, suitable for handling by fork-lift trucks and slings.

The cargo must be kept dry during transport and storage.

For sea-transport, deck-side shipment is not permitted and carrier-ownedcargo containers should be used.



B4008 Rev. M 51


1.4 Radio Equipment Inventory Check

Look for damage on the cases. Ensure that correct quantities of goods have

arrived, according to the packing list in each package/unit.

Check also that the part description on the outside of each box corre-

sponds to the components required for the installation, i.e. correct antennaand frequency, ODU frequency band and sub-band, IDU configuration.

Report any damages or missing items to Nera ASA by e-mail or fax. A short

description of damages, preferably including photographs, should be sent

as soon as possible.

1.5 Preparation for Installation

Complete the required civil works. Transport all the equipment to site.Unpack the equipment and inspect for damage during transit to site and

make sure that the correct quantities of goods have arrived.

Units with static discharge protection should not be unpacked until the

equipment installation takes place. Ensure you are grounded at a control-

led ESD point before and during insertion, and during any subsequent

unpacking of the unit.

1.6 Handling & Storage

It is recommended that components are stored and transported to the

installation site in their original packing cases. If items are unpacked for

storage, they should be handled with care and protected during transpor-

tation by similar protective materials.

The equipment is an electronic device which should be handled with care.

It should be stored in dry, cool conditions, out of direct sunlight. A

moisture absorbing bag is taped inside the transportation unit to minimisecondensation during transportation. This is to be removed at installation.

No maintenance is required when stored according to particulars above.

To avoid damage to the sealing components and unwanted moist in the

interconnection interfaces, the transportation protection lids on the branch-

ing and the transceiver must be kept on until mounting of waveguide

components and connection of the transceiver to the branching unit.



52 B4008 Rev. M

CityLink

2.0 Installation Equipment required

2.1 Tools

The tools needed to install the equipment are listed in the following sub-

chapters.

2.1.1 Tools for Antenna Installation

• 2 pcs Combination Wrench 13 mm



• 1 pc Torque Wrench 16 mm, 40 - 50 Nm

2.1.2 Tools for IDU- ODU Cable /Connector Mounting

• 1 Hacksaw, fine-toothed

• 1 Soldering Iron, 50-150W

• Solder 36/37 RMA flux core

• Cloth

• 1 Knife

• 1 Flat file, fine

• 1 Wire brush

• 1 Tape rule (or caliper)

• 1 Heat gun, 1000W• 1 Cutting pliers

for hexagon coupling nut :

• 1 Wrench 1/2" (13mm)

• 1 Wrench 9/16" (15mm)

• 1 Wrench 11/16" (18mm)

• 1 Wrench 13/16" (21mm)



B4008 Rev. M 53


2.2 Equipment external to the Radio Equipment

In addition to the necessary radio equipment & antenna the following

items are needed:

• Coaxial cable between IDU and ODU. See Section V, chapter 5 for

advise on which cable to use.• At least two N-type connectors suitable for termination of the

selected coaxial cable.

• Suitable waveguide & flanges between antenna and branching unit if

remote mount option is used.

• Cable to ground the ODU.

• Cable to ground the IDU.

• Cable to power the IDU.

• Cable to connect the PC, running the configuration & set-up program,

to the IDU.• Cable ties to secure cable runs.

• Cables for user interfaces.



54 B4008 Rev. M

CityLink

3.0 ODU / Antenna Installation, 1+0 Equipment

3.1 Installation of 0.6m and 0.45m Antenna

3.1.1 Preparing the Suspension for ODU Mounting

Bracket

Loosen this nut one turn.

Rotate the bracket 1800 byturning this bolt CW.



B4008 Rev. M 55


3.1.2 Mounting the Antenna to the Suspension

All the described nuts and washers are included in the antenna assembly

and come attached to the antenna.

4ea M8 Nuts and washers



56 B4008 Rev. M

CityLink

3.1.3 Mounting the Branching Support Bracket

M8x25

BRANCHINGSUPPORTBRACKET



B4008 Rev. M 57


REAR TRAVERS

M8x25

M8x25

SUSPENSIONSUPPORTBRACKET

3.1.4 Mounting the Rear Travers

3.1.5 Mounting the Suspension Support Bracket



58 B4008 Rev. M

CityLink

FEED

3.1.6 Mounting the Bend on the Branching Unit

M3 STUDS,NUTS ANDWASHERS

O-RING



B4008 Rev. M 59


3.1.8 Attachment of the Sunshield Support

Grounding point.See Section V Chapter 5.0 Fig. V-8

3.1.7 Installation of the Branching Unit


BRANCHINGUNIT

SUNSHIELDSUPPORT

M8x30SCREW,NUT ANDWASHERS

M8x30 SCREW,NUT ANDWASHERS



60 B4008 Rev. M

CityLink

3.1.9 Installation of the Flexible Waveguide

M3 STUDS,NUT AND

WASHERS

2 O-RINGS

M3 ALLENSCREWS,NUT ANDWASHERS

R220 FLEXIBLE

WAVEGUIDE

O-RING



B4008 Rev. M 61


3.1.10 Installation of the Sunshield

SUNSHIELD

M4x16 SCREWS,NUTS ANDWASHERS

M6x25 SCREWS,NUTS, LARGE WASH-ERS AND WASHERS

M4 ALLEN SCREW(FOUND MOUNTEDON THE BRANCHINGUNIT)

(PLACING OFLARGE WASHER)



62 B4008 Rev. M

CityLink

U-BOLTS(ABZ5479 for columndiameter Ø115mm,

ABZ5480 for

columndiameter Ø75mm)

3.1.11 Mounting the Suspension/Antenna to a Column or a Wall

3.1.11.1 Mounting the Suspension/Antenna to a Column by

using the U-bolts

M10 Nuts, washers and lockwashers, 4eaTorque: 25-30Nm



B4008 Rev. M 63


3.1.11.2 Mounting the Suspension/Antenna to a Column by

using the Clamps

CLAMPS, 2ea(ABZ5481)

M10 Nuts and washers, 4eaTorque: 35Nm

Column diameter:60-115mm



64 B4008 Rev. M

CityLink

M10 Expansionbolts (typedependant onthe nature of thewall

M10 Nuts and washers

3.1.11.3 Mounting the Suspension/Antenna to a Wall



B4008 Rev. M 65


3.1.12 Mounting the ODU to the Antenna Assembly

Before mounting the ODU to the antenna assembly, it is necessary to

remove the protection lid from the antenna feed. See below.

First remove the nuts usinga 5,5mm wrench.

Then remove the set screwsusing a 1,5 mm allen key.

Protection lid



66 B4008 Rev. M

CityLink



B4008 Rev. M 67


BRANCHING

SUPPORTBRACKET

CLAMP

3.1.13 Pole Mount

3.1.13.1 Assembly of Branching Support Bracket

3.1.13.2 Installation of Branching Unit and Sun-shield

M8

M4

BRANCHING UNIT

SUN-SHIELD

M12 (Torque 19 NM)




68 B4008 Rev. M

CityLink

1 0 5 m m ±

5

3.2 Installation of 1.2m Antenna

This chapter only descibes how to install the CityLink branching support

bracket and the branching unit. For further instructions please refer to the

handbook supplied with the antenna (H2602; Installation Procedure for

1.2m Antenna).

For installation of the transceiver, see Chapter 3.1.7.

3.2.1 Assembly of Branching Support Bracket


HORIZONTALGIRDER

VERTICALGIRDER

HORIZONTAL

GIRDER

BRANCHINGSUPPORT

BRACKET

Make sure that the distance between the top of the branching support

bracket and the horizontal girder is 105mm ±5mm.



B4008 Rev. M 69


3.2.3 Installation of Branching Unit,

Sun-shield and Flexible Waveguide

NOTE!

Most antennas are delivered with a bimetallic shim. This MUST NOT be

mounted for 18-26GHz equipment as the ODU, the flexible waveguide

and the antenna all have aluminium waveguide connectors. Flexible

waveguides for 13-15GHz have silver plated brass flanges and the

bimetallic shim MUST be used (copper side facing flex-wg).

Mount gasket(s) between the antenna feed and the flexible waveguide

and also gasket(s) between the flexible waveguide and the branching

unit. If the installation is placed in a very corrosive environment, further protection can be achieved by adding silicon rubber.

M4 M8

BRANCHING UNIT

SUN-SHIELD

FLEXIBLEWAVEGUIDE

ANTENNAFEED

FLEXIBLEWAVEGUIDE



70 B4008 Rev. M

CityLink


Hot Standby Equipment and 2+0 Equipment

4.1 0.45m and 0.6m Antenna

4.1.1 Installation of Hot Standby (HSB) and

2+0 Dual Frequency Single Polarization Equipment

4.1.1.1 Preparing the Suspension for ODU Mounting and

Mounting the Antenna to the Suspension

Please refer to Chapters 3.1.1 and 3.1.2 (this Section).

4.1.1.2 Mounting the Branching Support Bracket

M8x25

BRANCHING

SUPPORTBRACKET



B4008 Rev. M 71


4.1.1.3 Mounting the Rear Travers, Mounting the Suspension

Support Bracket and Mounting the Feed on the

Branching Unit

Please refer to Chapters 3.1.4 to 3.1.6 (this Section).

4.1.1.4 Installation of the HSB Branching Unit

BRANCHING UNIT

M8x25STUDS,NUTS

ANDWASHERS



72 B4008 Rev. M

CityLink

4.1.1.5 Installation of the Flexible Waveguide

M3 STUDS,NUT AND

WASHERS

2 O-RINGS

M3 ALLENSCREWS,NUT AND

WASHERS

R220 FLEXIBLEWAVEGUIDE

O-RING



B4008 Rev. M 73


4.1.1.6 Installation of the Sunshield Support Bracket

Please refer to Chapter 3.1.8 (this Section).

4.1.1.7 Installation of the Sunshield

SUNSHIELD

M4x16 SCREWS,NUTS ANDWASHERS

M6x25 SCREWS, NUTS,LARGE WASHERS ANDWASHERS

M4 ALLEN SCREW(FOUND MOUNTED

ON THE BRANCHINGUNIT)

(PLACING OFLARGE WASHER)



74 B4008 Rev. M

CityLink

4.1.1.8 Mounting the Suspension/ODU to a Column or a Wall


4.1.1.9 Mounting the ODU to the Antenna Assembly


remove the protection lid from the antenna feed. Please refer to Chapter

3.1.12 (this Section) for details.



B4008 Rev. M 75


4.1.1.10 Pole Mount

4.1.1.10.1 Assembly of Branching Support Bracket

4.1.10.1.2 Installation of Branching Unit and Sunshield

BRANCHING

SUPPORTBRACKET

CLAMP

M8

M4

BRANCHING UNIT

SUN-SHIELD

M12 (Torque 19 NM)




76 B4008 Rev. M

CityLink

4.1.2 Installation of 2+0 Equipment

(Single Frequency Dual polarity)

4.1.2.1 Preparing the Suspension for ODU Mounting and

Mounting the Antenna to the SuspensionPlease refer to Chapters 3.1.1 and 3.1.2 (this Section).

4.1.2.2 Mounting the Branching Support Bracket, Mounting the

Rear Travers, Mounting the Suspension Support

Bracket and Mounting the Feed on the Branching Units

Please refer to Chapters 3.1.3 to 3.1.6 (this Section).


4.1.2.3 Installation of the Branching Units



B4008 Rev. M 77


4.1.2.4 Installation of the Flexible Waveguide

M3 STUDS,NUT ANDWASHERS

2 O-RINGS


R220 FLEXIBLEWAVEGUIDE

O-RING


M3 STUDS,NUT ANDWASHERS

2 O-RINGS



78 B4008 Rev. M

CityLink

4.1.2.5 Installation of the Sunshield

M6x25 SCREWS,

NUTS, LARGE WASH-

ERS AND WASHERS

M4 ALLEN SCREW

(FOUND MOUNTED

ON THE BRANCHING

UNIT)

(PLACING OF

LARGE WASHER)

M4 ALLEN SCREW

(FOUND MOUNTEDON THE BRANCHING

UNIT)SUNSHIELDS



B4008 Rev. M 79


4.1.2.6 Mounting the Suspension/ODU to a Column or a Wall


4.1.2.7 Mounting the ODU to the Antenna Assembly


remove the protection lid from the antenna feed. Please refer to Chapter

3.1.12 (this Section) for details.



80 B4008 Rev. M

CityLink

4.1.2.9.2 Installation of Branching Units and Sunshields

M8

M4

BRANCHING UNITS

SUN-SHIELDS


4.1.2.9 Pole Mount

4.1.2.9.1 Assembly of Branching Support Bracket

BRANCHING

SUPPORTBRACKET

CLAMP

M12 (Torque 19 NM)



B4008 Rev. M 81


4.2 1.2m Antenna

This chapter only descibes how to install the CityLink branching support

bracket and the branching unit. For further instructions please refer to the

handbook supplied with the antenna (H2602; Installation Procedure for

1.2m Antenna).

For installation of the transceiver, see Chapter 4.1.5.

4.2.1 Assembly of Branching Support Bracket

8 7 m

m ±

5


HORIZONTALGIRDER

VERTICALGIRDER

HORIZONTALGIRDER

BRANCHINGSUPPORT

BRACKET

Make sure that the distance between the top of the branching support

bracket and the horizontal girder is 130mm ±3mm.

1 3 0 m m

± 3 m m



82 B4008 Rev. M

CityLink

4.2.2 Installation of Branching Unit, Sun-shield and Flexible

Waveguide

4.2.2.1 Hot Standby and 2+0 Dual Frequency Single Polarization

FLEXIBLEWAVEGUIDE

BRANCHING UNIT

M4M8

SUN-SHIELD

NOTE!

Most antennas are delivered with a bimetallic shim. This MUST

NOT be mounted for CityLink installations as the ODU, theflexible waveguide and the antenna all have aluminium waveguide

connectors.

Mount gasket(s) between the antenna feed and the flexible

waveguide and also gasket(s) between the flexible waveguide

and the branching unit. If the installation is placed in a very

corrosive environment, further protection can be achieved by

adding silicon rubber.

Grounding point.See Section V Chapter 5.0Fig. V-9



B4008 Rev. M 83


4.2.2.2 2+0 Single Frequency Dual Polarization

FLEXIBLE

WAVEGUIDES

BRANCHING UNITS

M4

M8

SUN-SHIELDS

Grounding point.See Section V Chapter 5.0

Fig. V-9

NOTE!

Most antennas are delivered with a bimetallic shim. This MUST

NOT be mounted for 18-26GHz equipment as the ODU, the

flexible waveguide and the antenna all have aluminium

waveguide connectors. Flexible waveguides for 13-15GHz have

silver plated brass flanges and the bimetallic shim MUST beused (copper side facing flex-wg).

Mount gasket(s) between the antenna feed and the flexible

waveguide and also gasket(s) between the flexible waveguide

and the branching unit. If the installation is placed in a very

corrosive environment, further protection can be achieved by

adding silicon rubber.



84 B4008 Rev. M

CityLink

5.0 Frequency Tuning at 13GHz &15GHz Transceiver This chapter gives a short description of how to set and change frequency

channel on the transceiver. To perform this operation it is necessary to

remove the cover and mount the transceiver to a branching connected to

an IDU. A PC (where Nera software NEW is installed) and power arefurther connected to the IDU. A voltage meter and a screwdriver must also

be available.

• Switch on the power at the system

• Set wanted frequency in New.

Tables II-1 to II-9 give the relation between selected channel, duplex, TX

High/Low and RX High/Low. The illustration on the next page gives an

overview of the tuning voltage connectors (VT TX and VT RX) and tuningscrews.

WARNING!

This equipment contains components which are sensitive to

"ESD" (Electro Static Discharge). It is therefore essential that

whenever disassembling the equipment and/or handling PC

boards, special precautions to avoid ESD have to be made.

This includes personnel grounding, grounding of work bench,grounding of tools and instruments. For the tuning process,

it is also recommended to use a ceramic screw driver.

• Measure the tuning voltage VT TX continuously while adjusting the

tuning screw. First turn the tuning screw CCW as far as it goes. Then

adjust it CW until VT TX reaches the correct voltage:

For 15GHz Transceiver; 4±0.5[V]


• Measure the tuning voltage VT RX continuously when adjusting the

tuning screw. First turn the tuning screw CCW as far as it goes. Then

adjust it CW until VT TX reaches the correct voltage:



After tuning VT TX and VT RX to the correct voltage, the transceiver is

configured to the correct frequency channel. Inspect the gasket and

replace the cover with use of correct torque (1.25Nm).



B4008 Rev. M 85


GND VT TX

Rx HighTx High

Rx LowTx Low

VT RX



86 B4008 Rev. M

CityLink

Duplex frequency: 490 MHzChannel spacing: 28MHz

10L15L01A 10L15U01A

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX

DRO

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX

DRO1 14417 Low 1’ 14907 Low 1’ 14907 Low 1 14417 Low

2 14445 Low 2’ 14935 Low 2’ 14935 Low 2 14445 Low

3 14473 Low 3’ 14963 Low 3’ 14963 Low 3 14473 Low

4 14501 Low 4’ 14991 Low 4’ 14991 Low 4 14501 Low5 14529 Low 5’ 15019 Low 5’ 15019 Low 5 14529 Low


8 14613 Low 8’ 15103 Low 8’ 15103 Low 8 14613 Low

9 14641 Low 9’ 15131 Low 9’ 15131 High 9 14641 Low

10 14669 High 10’ 15159 Low 10’ 15159 High 10 14669 Low

11 14697 High 11’ 15187 Low 11’ 15187 High 11 14697 High

12 14725 High 12’ 15215 High 12’ 15215 High 12 14725 High






10L15L01A 10L15U01A

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX

DRO

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX


2 14543 Low 2’ 14963 Low 2’ 14963 Low 2 14543 Low3 14571 Low 3’ 14991 Low 3’ 14991 Low 3 14571 Low4 14599 Low 4’ 15019 Low 4’ 15019 Low 4 14599 Low

5 14627 Low 5’ 15047 Low 5’ 15047 Low 5 14627 Low

6 14655 Low 6’ 15075 Low 6’ 15075 Low 6 14655 Low

7 14683 High 7’ 15103 Low 7’ 15103 Low 7 14683 High




11 14795 High 11’ 15215 High 11’ 15215 High 11 14795 High12 14823 High 12’ 15243 High 12’ 15243 High 12 14823 High





10L15L01A 10L15U01A

TXCh.

TXFreq.

TXDRO

RXCh.

RXFreq.

RXDRO

TXCh.

TXFreq.

TXDRO

RXCh.

RXFreq.

RXDRO

1 14515 Low 1’ 15243 High 1’ 15243 High 1 14515 Low2 14543 Low 2’ 15271 High 2’ 15271 High 2 14543 Low3 14571 Low 3’ 15299 High 3’ 15299 High 3 14571 Low4 14599 Low 4’ 15327 High 4’ 15327 High 4 14599 Low

Table II-1

Table II-2

Table II-3



B4008 Rev. M 87


Duplex frequency: 315 MHz

Channel spacing: 28MHz

10L15L01A 10L15U01A

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX

DRO

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX

DRO

1 14662 Low 1’ 14977 Low 1’ 14977 Low 1 14662 Low

2 14690 High 2’ 15005 Low 2’ 15005 Low 2 14690 High

3 14718 High 3’ 15033 Low 3’ 15033 Low 3 14718 High

4 14746 High 4’ 15061 Low 4’ 15061 Low 4 14746 High5 14774 High 5’ 15089 Low 5’ 15089 Low 5 14774 High

6 14802 High 6’ 15117 Low 6’ 15117 Low 6 14802 High






10L15L01A 10L15U01A

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX

DRO

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX


2 14529 Low 2’ 14949 Low 2’ 14949 Low 2 14529 Low

3 14543 Low 3’ 14963 Low 3’ 14963 Low 3 14543 Low

4 14557 Low 4’ 14977 Low 4’ 14977 Low 4 14557 Low

5 14571 Low 5’ 14991 Low 5’ 14991 Low 5 14571 Low


8 14613 Low 8’ 15033 Low 8’ 15033 Low 8 14613 Low


11 14655 Low 11’ 15075 Low 11’ 15075 Low 11 14655 Low

12 14669 High 12’ 15089 Low 12’ 15089 Low 12 14669 Low

13 14683 High 13’ 15103 Low 13’ 15103 Low 13 14683 High

14 14697 High 14’ 15117 Low 14’ 15117 Low 14 14697 High15 14711 High 15’ 15131 High 15’ 15131 High 15 14711 High















Table II-4

Table II-6


10L15L01A 10L15U01A

TXCh.

TXFreq.

TXDRO

RXCh.

RXFreq.

RXDRO

TXCh.

TXFreq.

TXDRO

RXCh.

RXFreq.

RXDRO

1 14515 Low 1’ 15159 High 1’ 15159 High 1 14515 Low2 14543 Low 2’ 15187 High 2’ 15187 High 2 14543 Low3 14571 Low 3’ 15215 High 3’ 15215 High 3 14571 Low4 14599 Low 4’ 15243 High 4’ 15243 High 4 14599 Low5 14627 Low 5’ 15271 High 5’ 15271 High 5 14627 Low6 14655 Low 6’ 15299 High 6’ 15299 High 6 14655 Low7 14683 High 7’ 15327 High 7’ 15327 High 7 14683 High

Table II-5



88 B4008 Rev. M

CityLink


10L15L01A 10L15U01A

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX

DRO

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX

DRO



5 14473 Low 5’ 14963 Low 5’ 14963 Low 5 14473 Low

6 14487 Low 6’ 14977 Low 6’ 14977 Low 6 14487 Low

7 14501 Low 7’ 14991 Low 7’ 14991 Low 7 14501 Low

8 14515 Low 8’ 15005 Low 8’ 15005 Low 8 14515 Low

9 14529 Low 9’ 15019 Low 9’ 15019 Low 9 14529 Low

10 14543 Low 10’ 15033 Low 10’ 15033 Low 10 14543 Low

11 14557 Low 11’ 15047 Low 11’ 15047 Low 11 14557 Low


14 14599 Low 14’ 15089 Low 14’ 15089 Low 14 14599 Low

15 14613 Low 15’ 15103 Low 15’ 15103 Low 15 14613 Low

16 14627 Low 16’ 15117 Low 16’ 15117 Low 16 14627 Low17 14641 High 17’ 15131 Low 17’ 15131 High 17 14641 Low

18 14655 High 18’ 15145 Low 18’ 15145 High 18 14655 Low19 14669 High 19’ 15159 High 19’ 15159 High 19 14669 Low












Table II-7



10L13L01A 10L13U01A

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX

DRO

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX

DRO

1 12765 Low 1’ 13031 High 1’ 13031 High 1 12765 Low

2 12793 Low 2’ 13059 High 2’ 13059 High 2 12793 Low

3 12821 Low 3’ 13087 High 3’ 13087 High 3 12821 Low4 12849 Low 4’ 13115 High 4’ 13115 High 4 12849 Low

5 12877 Low 5’ 13143 High 5’ 13143 High 5 12877 Low


8 12961 Low 8’ 13227 High 8’ 13227 High 8 12961 Low

Table II-8



B4008 Rev. M 89



10L13L01A 10L13U01A

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX

DRO

TX

Ch.

TX

Freq.

TX

DRO

RX

Ch.

RX

Freq.

RX

DRO1 12758 Low 1’ 13024 High 1’ 13024 High 1 12758 Low

2 12772 Low 2’ 13038 High 2’ 13038 High 2 12772 Low

3 12786 Low 3’ 13052 High 3’ 13052 High 3 12786 Low



8 12856 Low 8’ 13122 High 8’ 13122 High 8 12856 Low


11 12898 Low 11’ 13164 High 11’ 13164 High 11 12898 Low


14 12940 Low 14’ 13206 High 14’ 13206 High 14 12940 Low15 12954 Low 15’ 13220 High 15’ 13220 High 15 12954 Low16 12968 Low 16’ 13234 High 16’ 13234 High 16 12968 Low

Table II-9



90 B4008 Rev. M

CityLink

6.0 Cable ConnectionsPlease refer to Section V Chapter 5.0.

7.0 Antenna AlignmentPlease refer to Section IV Chapter 6.0.



B4008 Rev. M 91

ODU Type II Installation

Installation of

ODU Type II and Antenna

SECTION III



92 B4008 Rev. M

CityLink



ends.

1.1 Packing










transportation.



1.2 Marking



Customer address

Contract No.


1.3 Transportation







B4008 Rev. M 93
































94 B4008 Rev. M

CityLink


2.1 Tools


chapters.

2.1.1 Tools for Antenna Installation




• 1 pc Torque Wrench 16 mm, 40 - 50 Nm





• Cloth

• 1 Knife


• 1 Wire brush

• 1 Tape rule (or caliper)

• 1 Heat gun, 1000W• 1 Cutting pliers


• 1 Wrench 1/2" (13mm)

• 1 Wrench 9/16" (15mm)

• 1 Wrench 11/16" (18mm)

• 1 Wrench 13/16" (21mm)



B4008 Rev. M 95




items are needed:














96 B4008 Rev. M

CityLink

3.0 ODU Installation

3.1 Mounting the ODU to the Pole

The ODU can be mounted to a Ø75mm or a Ø115mm pole, see figure

below.

2 x M10 NUTS AND

WASHER

SUN-SHIELD

U-BOLTS

Waveguide Flange type:PDR84



B4008 Rev. M 97


ODU BOTTOM VIEW:

3.2 Cable Connections

Pressureequalizer

AGC Connector

IDU - ODU Cable Connector, N-50WFor details please see Figure V-7.

Ground connection. Attach ground-ing cable (10mm2) to this point withthe M6 nut and washers.



98 B4008 Rev. M

CityLink

4.0 Antenna and Waveguide Installation

4.1 0.6m Antenna

Shim Copper/ Aluminium

Copper side Alu side

Flange Adapter (NL2007 only)



B4008 Rev. M 99


4.2 1.2m Antenna



100 B4008 Rev. M

CityLink

4.3 2m Antenna



B4008 Rev. M 101


4.4 2.4m



102 B4008 Rev. M

CityLink

4.5 3m

317±20



B4008 Rev. M 103

ODU Type III Installation

Installation of

ODU Type III and Antenna

SECTION IV



104 B4008 Rev. M

CityLink



ends.

1.1 Packing










transportation.



1.2 Marking



Customer address

Contract No.


1.3 Transportation







B4008 Rev. M 105
































106 B4008 Rev. M

CityLink


2.1 Tools


chapters.

2.1.1 Tools for Antenna Installation and Adjustment

• 2 pcs Combination Wrench M8, 13 mm



• 1 pc Combination Wrench 10 mm

• 1 pc Torque Wrench, M16, 24 mm, 120 Nm





• Cloth

• 1 Knife


• 1 Wire brush

• 1 Tape rule (or caliper)• 1 Heat gun, 1000W

• 1 Cutting pliers


• 1 Wrench 1/2" (13mm)

• 1 Wrench 9/16" (15mm)

• 1 Wrench 11/16" (18mm)

• 1 Wrench 13/16" (21mm)



B4008 Rev. M 107




items are needed:














108 B4008 Rev. M

CityLink

3.0 ODU / Antenna Installation, 1+0 Equipment

3.1 Mounting the Antenna to the Suspension

All the described nuts and washers are included in the antenna assembly

and come attached to the antenna.

4ea M8 Nuts, washersand lock washers

SUSPENSION (3AB5158A)

ANTENNA(0,3m 0,45m and 0,6m)



B4008 Rev. M 109


3.2 Mounting the Sunshield

The Sunshield, screws, nuts and washers are found in the kit AZZ5495.

M6 Nuts, washersand lock washers(4ea)

M6 Screws (4ea)

SUNSHIELD



110 B4008 Rev. M

CityLink

U-BOLTS(ABZ5479 for columndiameter Ø115mm,

ABZ5480 for columndiameter Ø75mm)

3.3 Mounting the Suspension/Antenna to a Column by

using the U-bolts

M10 Nuts, washers and lockwashers, 4eaTorque: 25-30Nm



B4008 Rev. M 111


CLAMPS, 2ea(ABZ5481)

M10 Nuts and washers, 4eaTorque: 35Nm

Column diameter:60-115mm

3.4 Mounting the Suspension/Antenna to a Column by

using the Clamps



112 B4008 Rev. M

CityLink

STEP 1 Mounting the Brackets on the Frame

4ea M8x20 screws8ea Flat washers4ea Lock washers4ea M8 Nuts(Kit:ABZ5774)

Bracket(Kit: ABZ5774)

Bracket(Kit: ABZ5774)

3.5 Mounting the Transceiver

(without Antenna) to a Column



B4008 Rev. M 113


STEP 2 Attaching the Frame to the Column

2ea M10 U-bolts(Kit: ABZ5774)

4ea M10 Flat washers8ea M10 Nuts(Kit:ABZ5774)



114 B4008 Rev. M

CityLink

STEP 3 Mounting the Sunshields

Sunshields(Kit: ABZ5779)

2ea M5x12 screws8ea M5 flat washers

4ea M5 lock washers4ea M5 nuts(Kit: ABZ5774)



B4008 Rev. M 115


STEP 4 Mounting the Transceiver

1+0 Configuration

1+1/HSB Configuration



116 B4008 Rev. M

CityLink

STEP 5 Mounting the Flexible Waveguide

1+0 Configuration

1+1/HSB Configuration

Mounting flange for flexible waveguide

Mounting flange for flexible waveguide



B4008 Rev. M 117


M10 Expansionbolts (type

dependant onthe nature of thewall

M10 Nuts and washers

3.6 Mounting the Suspension/Antenna to a Wall

Ø10mm Pre-drilled holes



118 B4008 Rev. M

CityLink

3.7 Mounting the ODU to the Antenna Assembly


remove the protection lid from the antenna feed. See below.

First remove the nuts usinga 5,5mm wrench.

Then remove the set screwsusing a 1,5 mm allen key.

Protection lid



B4008 Rev. M 119


LATCHES (4ea, one

in each corner)

After adjustment;

M16 torque = 110-120Nm

For adjustment seeChapter 6.0.

To unlock the latches,

push this handle forward

For correct

polarisation;

see next

page



120 B4008 Rev. M

CityLink

Polarization

The electrical field is always orthogonal to the two opposing sides of the

two broad sides of the rectangular waveguide.

It is important to mount the ODU to the antenna with the right orientation.

The arrows on the ODU's handle shall indicate the polarisation (vertical or

horizontal).

P O L A RI Z AT I O N

P O L A RI Z AT I O N

POLARIZATION POLARIZATION

UP

DOWNWaveguide feed with

horizontal polarisation

Waveguide feed with

vertical polarisation

ODU orientation for

vertical polarisationODU orientation for

horizontal polarisation

UP

DOWN



B4008 Rev. M 121


Bracket

Loosen this nut one turn.

(See also Chapter 6.0)

Rotate the bracket 1800 by

turning this bolt CW.


HSB and 2+0 Equipment

4.1 Preparing the Suspension for HSB and 2+0 Mounting



122 B4008 Rev. M

CityLink

4ea M8 Nuts and washers

4.2 Mounting the Antenna to the Supension



B4008 Rev. M 123


4.3 Mounting the Hybrid Frame to the Antenna

STEP 1

Note! Mounting sequence is important!

2ea M8 Set screws, nuts,washers and lock washers



124 B4008 Rev. M

CityLink

M8 Screws,nuts and washers

STEP 2

Note! Mounting sequence is important!

M8 Screws,nuts and washers



B4008 Rev. M 125


4.3 Mounting the CityLink III ODUs to the Antenna Assembly

LATCHES (1 in eachcorner of each ODU)



126 B4008 Rev. M

CityLink

4.4 Mounting the Transceiver

(without Antenna) to the Column

Please refer to Chapter 3.5 (this Section).

4.5 Mounting the Suspension/Antenna to a Wall

Please refer to Chapter 3.6 (this Section).



B4008 Rev. M 127


5.0 Cable Connections

ODU BOTTOM VIEW:

Pressure equalizer

AGC Connector.In a 1+1 configuation,this connector is usedfor interconnectionbetween the two ODUs.

Ground connection. Attachgrounding cable (10mm2) tothis point with the M6 nut andwashers.

IDU - ODU Cable Connector, N-50WFor details please see Figure V-7.



128 B4008 Rev. M

CityLink

6.0 Antenna Alignment

Azimuth Adjustment

• Unlock securing nut approx. 1 turnbefore azimuth adjusting

• Adjust azimuth

• Lock securing nut after adjustment

Elevation Adjustment

• Unlock securing nut approx. 1/2 turnbefore elevation adjusting

• Adjust elevation

• Lock securing nut after adjustment

6.1 Azimuth and Elevation Adjustment

Torque: 110-120Nm

Torque: 110-120Nm

6.2 Coarse adjustment.Adjust both antennas to correct direction as possible by using magnetic

compass or optical sight.

6.3 Fine adjustment

Fine adjustment is achieved by setting up a connection between the

antennas. When the connection is established a readout of the AGC voltage

can be used to align the antennas. Loosen the antenna in both elevation and

azimuth according to figure and adjust both azimuth and elevation untilmaximum signal is recived. Try a few times in each direction. The antenna

should be turned so much that the first sidelobes are seen, thereby ensure

that the antenna is aligned on the mainlobe.

When the antenna is aligned in both azimuth and elevation the polarization

of the feed shall be realigned.

Finally ensure that all bolts and nuts are properly mounted and tighten.

The same procedure shall than be repeated on the opposite antenna.



B4008 Rev. M 129


6.5 Polarisation alignment

Align the antenna approximately in both elevation and azimuth. Then use

a water level to align the polarisation of the antenna feed to correct

polarisation according to figures below. Loosen the six M8 nuts that are

securing the feed to the reflector and rotate the feed according to readout

of the water level. When the feed is in correct alignment, tighten the six

M8 nuts properly (do not overtight the nuts). Then the ODU can bemounted and the antenna has to be aligned. If the antenna has to be rotated

several degrees in azimuth or elevation, the polarisation has to be rea-

ligned according to prior procedures.

Use these stud screws for aligning the feed with water level.

When the H mark is in upwards position, this

shows that the antenna is Horizontal Polarized

Water level

Horizontal Polarisation:

6.4 Final Control

When all adjustments are performed, check that the input level agrees with

the calculated level. If the input level is to low, realign the antenna once

more. Finally ensure that all bolts and nuts are properly mounted and

tighten.



130 B4008 Rev. M

CityLink

Use these stud screws for aligning the feed with water level.

When the V mark is in upwards position, this

showes that the antenna are Vertical Polarised

Water level

Vertical Polarisation:



B4008 Rev. M 131

IDU Installation

SECTION V V V V V

IDU Installation

ODU-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt.1

Phone

64kb/sV.11

2MHzSync.

SVCEExt. 2

10BaseTLAN

IDU - HSB INTFCCALL ALM & AU X LCT

NI 2

NI1

CRITICAL

MAJOR

MINOR

WARNING

POWER

155Mb/s LINE

PWR INP

G.703

OUT

-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt.2

10BaseTLAN

IDU-HSBINTFCC ALL A LM & AUX LCT

NI2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER 2

155 Mb/s LINE

PWRINP

G.703

OUT1

2

RXDIRA

RXDIRB

TXDIRATXDIRB

POWER 1

ODU-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt.1

Phone

64kb/sV.11

2MHzSync.

SVCEExt. 2

10BaseTLAN

IDU- HSB INTFCCALL ALM& AUX LCT

NI2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER

155Mb/sLINE

PWR



132 B4008 Rev. M

CityLink



ends.

1.1 Packing










transportation.



1.2 Marking



Customer address

Contract No.


1.3 Transportation







B4008 Rev. M 133

IDU Installation



























134 B4008 Rev. M

CityLink

Figure V-2 Mounting the IDU in a Rack

Figure V-1 Mounting the Mechanical Adapters for ANSI or ETSI Rack

ODU-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt. 2

10BaseTLAN

IDU - HSBINTFCCALL ALM & AUX LCT

NI 2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER

155 Mb/s LINE

PWR INP

G.703

OUT

-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt. 2

10BaseTLAN

IDU-HSBINTFCCALL ALM &AUX LCT

NI 2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER2

155 Mb/sLINE

PWRINP

G.703

OUT1

2

RXDIRA

RXDIRB

TXDIRATXDIRB

POWER1

ODU-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt.2

10BaseTLAN

IDU- HSBINTFCCALL ALM & AUX LCT

NI2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER

155 Mb/sLINE

PWR

ETSI Rack Adapter

M6x12

WASHERFLAT WASHER

ANSI Rack Adapter

2.0 IDU Installation

2.1. Mounting the IDU in an ANSI (19") or an ETSI Rack

Mount the relevant mechanical adapters provided in the IDU package by

using the M3-6mm TORX screws also provided in the IDU package. The

long adapters are for ETSI Rack, while the short are for ANSI Rack. SeeFigure V-1.

Position the IDU in the rack and secure it by using the four M6-12mm

screws provided in the IDU package. See Figure V-2.



B4008 Rev. M 135

IDU Installation

2.2 Cable Installation

Route, secure if necessary with cable ties, and terminate ground cable

between the IDU safety ground post and a nearby local safety ground

point. Use the 6mm2 cable (2.5m long) included in the grounding kit.

Refer to Figures X-1 and X-2 (Section X, Appendix 1) for the IDU

safety ground post location.

Route, secure if necessary with cable ties, the terminated IDU/ODU

cable and connect to the ODU port of the IDU. See Chapter 5.0 (this

Section) for further details.

NOTE!

Max torque = 5Nm when mounting the IDU/ODU cable.

Route and secure the power cable. The CityLink requires DC power

(-40,5 to -57V) via a 2-pin connector. Refer to Figure X-7 (Section

X, Appendix 1) for a pinout of the connectors. It is recommended to

use the supplied power cable, UWMK5051. The cable is left un-

connected in one end. The black conductor must be connected to 0V

(station gnd) and the blue conductor must be connected to -48V. After

connecting the cable to the power supply, measure polarity on power

connector terminals.

Dependent on the purchased configuration of the IDU, route and attach

all cables except the power cable. Refer to Section X, Appendix 1 for

wiring details.



136 B4008 Rev. M

CityLink

Figure V-4 Mounting the Hot Standby IDUs in an ETSI Rack

3.0 Hot Standby IDU Installation(2+0 IDU installation is similar to ordinary IDU installation, see Ch. 2.0)

3.1 Mounting the Hot Standby IDUs in a Rack

Mount the relevant mechanical adapters provided in the IDU package byusing the M3-6mm TORX screws also provided in the IDU package.See

Figure V-1 (Chapter 2.1).

Position the IDUs in the rack and secure them by using the four M6-12mm

screws provided in each IDU package. See Figures V-3 & V-4.

Figure V-3 Mounting the Hot Standby IDUs in an ANSI Rack

ODU-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt.2

10BaseTLAN

IDU-HSB INTFCCALL ALM & AUX LCT

NI 2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER

155 Mb/s LINE

PWR INP

G.703

OUT

-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt.1

Phone

64kb/sV.11

2MHzSync.

SVCEExt. 2

10BaseTLAN

IDU-HSB INTFCCALL ALM &AUX LCT

NI2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER2

155 Mb/s LINE

PWRINP

G.703

OUT1

2

RXDIRA

RXDIRB

TXDIRATXDIRB

POWER1

ODU-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt. 2

10BaseTLAN

IDU -HSB INTFCCALL ALM & AUX LCT

NI 2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER

155 Mb/s LINE

PWR

ODU-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt.2

10BaseTLAN


NI 2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER

155 Mb/s LINE

PWR INP

G.703

OUT

-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt.1

Phone

64kb/sV.11

2MHzSync.

SVCEExt. 2

10BaseTLAN


NI2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER 2

155 Mb/s LINE

PWRINP

G.703

OUT1

2

RXDIRA

RXDIRB

TXDIRATXDIRB

POWER 1

ODU-48VDC

64kb/s

G.703

2Mb/s

Wayside

SVCE

Ext. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt. 2

10BaseTLAN

IDU - HSB INTFCCALL ALM & AUX LCT

NI 2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER

155 Mb/s LINE

PWR INP

G.703

OUT

-48VDC

64kb/s

G.703

2Mb/s

Wayside

SVCE

Ext. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt. 2

10BaseTLAN


NI 2

NI1

CRITICAL

MAJOR

MINOR

WARNING

POWER 2

155 Mb/sLINE

PWRINP

G.703

OUT1

2

RXDIRA

RXDIRB

TXDIRATXDIRB

POWER 1

ODU-48VDC

64kb/s

G.703

2Mb/s

Wayside

SVCE

Ext. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt.2

10BaseTLAN

IDU- HSB INTFCCALL ALM & AUX LCT

NI2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER

155 Mb/s LINE

PWR

ODU-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt. 2

10BaseTLAN


NI 2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER

155 Mb/s LINE

PWR

ODU-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt. 2

10BaseTLAN


NI 2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER

155 Mb/s LINE

PWR

ODU

-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt. 1

Phone

64kb/s

V.11

2MHz

Sync.

SVCE

Ext. 2

10BaseT

LAN

IDU - HSB INTFC

CALL ALM & AUX LCT

NI 2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER

155 Mb/s LINE

PWR

-48VDC

64kb/sG.703

2Mb/sWayside

SVCEExt. 1

Phone

64kb/sV.11

2MHzSync.

SVCEExt. 2

10BaseTLAN

IDU-HSB INTFCCALL ALM & AUX LCT

NI 2

NI 1

CRITICAL

MAJOR

MINOR

WARNING

POWER2

155Mb/sLINE

PWRINP

G.703

OUT1

2

RXDIRA

RXDIRB

TXDIRATXDIRB

POWER1

IDU A

IDU B

HSB-IDU

M6x12WASHER

FLAT WASHER

IDU A HSB-IDU

IDU B

M6x12

WASHERFLAT WASHER



B4008 Rev. M 137

IDU Installation

3.2 Interconnections in a Hot Standby System

Interconnections between the IDUs in a Hot Standby system are done by

means of a Y-cable. The cabel connectors are marked respectively IDU A,

HSB-IDU and IDU B and this indicates which IDU they shall be connected

to. See Figure V-5.

Figure V-5 Interconnections in a Hot Standby System

IDU A

IDU B

HSB IDU

Y-Cable

WARNING!

If the Y-cable connectors marked with IDU A and IDU B areswapped, the IDUs must always be rebooted after this opera-

tion.

NOTE!

Max torque = 5Nm when mounting the IDU/ODU cable.



138 B4008 Rev. M

CityLink

4.0 Installation of Optional Extension Boards

Step 1

Remove the four screws that holds the lid

Step 2

Use a flat screwdriver to carefully remove the lid.

WARNING!

This equipment contains components which are sensitive to "ESD"

(Electro Static Discharge). It is therefore essential that whenever

disassembling the equipment and/or handling PC boards, special pre-cautions to avoid ESD have to be made.

This includes personnel grounding, grounding of work bench,

grounding of tools and instruments.



B4008 Rev. M 139

IDU Installation

Step 3

Remove screws and bushings (2ea) from the spacers and also the three

screws from the IDU front as shown below.

Step 4

Remove the blindplates from the front of the IDU.



140 B4008 Rev. M

CityLink

Step 6

Mount the new front using the three screws removed in Step 4 (only two

screws for the 21x2Mbit/s Extension Board).

Step 7

Remount the lid.

Step 5

Mount the extension board. Press the extension board towards the IDU's

front and push the rear edge downwards until you are able to mount the

screws and bushings in the spacers.



B4008 Rev. M 141

IDU Installation

5.0 IDU/ODU Cable InstallationBoth ends of the cable must be terminated with N-male connectors. We

recommend to use cables with outer conductor of solid corrugated

copper.

For other cable types, the cable and all necessary installation materials must

be arranged by the purchaser.

Cable length limitations are dependent upon cable type used. The table

below show limtations for some cables. Cable lenghts include cable ties.See

Table V-1.

Table V-1 Cable length limitation due to different DC resistance

Table V-2 Selected Coax Cables and Connector Kits

Cable Type

DCresistance R

If the length is 100 m minimum voltage to

IDU must be


IDU must be


IDU must be

Bendingradius

90 m (-40.5 V)*

100 m (-40.7 V) Dev. 0.2V200 m (-43.5 V)

FSJ1-50A

See Note 1

16.3 Ω/km

300 m (-46.0 V)

25 mm

180 m (-40.5 V)*200 m (- 40.8 V) Deviation 0.3 V LDF1-50

See Note 2 8,48 Ω/km

300 m (- 42.5 V)

75 mm

160 m (-40.5 V)*200 m (-41.1 V) Deviation 0.6 VLCF14-50J

See Note 3 9.6 Ω/km

300 m (-42.9 V)

40 / 120 mmsingle / rptd

LCF38-50JSee Note 4

5.0 Ω/km 50 / 95 mmsingle / rptd

*) Standard (ETSI) specified minimum supply voltage to IDU is –40,5 V

IDU to ODU Coax Cable

1 Cable Kit 100 m LCF14-50 100 m ¼” Coax Cable including 200 Cable Ties 85W5147-1002 Cable Kit 150 m LCF14-50 150 m ¼” Coax Cable including 300 Cable Ties 85W5147-1503 Cable Kit 200 m LCF14-50 200 m ¼” Coax Cable including 400 Cable Ties 85W5147-2004 N-Connector Kit Connectors for IDU & ODU and Cable Grounding 87K5148-N5 Preparation Tool for LCF14 Easy cable preparation for connector attachment 85W5147-TL

For cable run 200 –300 m:6 Cable & Connector Kit

300 m LCF38-50300 m 3/8” Coax Cable including 600 Cable Tiesand Connectors for ODU & IDU including jumpercable and Cable Grounding Kit

85W5011-K300

7 Extra Connector Kit Connectors for ODU & IDU including jumper cableand Cable Grounding Kit

87K5013-1A

8 Preparation Tool for LCF38 Easy cable preparation for connector attachment 85W5011-TL

Notes:1. Not selected as standard stock item.

2. Standard cable kits are available as 100 m and 200 m

3. Standard cable kits are available as 100 m, 150 m and 200 m

4. Standard cable kits are available as 250 m and 300 m. Standard version of

LCF38-50 (6.7Ω/km) cannot be used. Only the cable type LCF38-50 with solid

copper inner conductor must be used (RFS part no. 152 225 11).



142 B4008 Rev. M

CityLink

• Avoid excessive bending. Run the cable where it is reasonable well

protected and will not rub against sharp edges or overly abrasive

surfaces.

• The N-connectors should be tightened to the IDU and ODU according

to the manufacturers installation instructions (provided with the

connectors) but with a max torque of 5Nm on the IDU.• Leave enough slack in the cable termination to the ODU to allow

antenna re-positioning.

• The cable connection to the ODU should be made weatherproof

using the cable connector weatherproof sleeve provided in the

installation kit. See Figure V-7.

See Figure V-6 for Cable Arrangement.



B4008 Rev. M 143

IDU Installation

Figure V-6 Cable Arrangement, Mandatory Items

Item Description Part No. Remarks1 Coax Cable

1a Cable Tie

See Table V-1,

-2a & -2b

Supplied as Cable Kit,

cable with ties (2 per m).

2a Connector, N-male, straight for ODU

2b Connector, N-male, angle for IDU

2c Grounding Kit for coax cable

See Table V-

2a & -2b

Supplied as Connector Kit.

3a Grounding Cable for ODU

3b Grounding Cable for IDU

3c Grounding Jumper Cable IDU/SW

UWA7 Supplied as separate kit UWA7.

4 DC Power Supply Cable UWMK5051 Included in IDU connection kit and HSB

IDU interconnection kit.

NOTE 1Weather protec-tion kit ABZ278(See Figure V-7)

Grounding point. (See Figure V-8)

ODU

Antenna

EquipmentEarthing Bar

Buried Earthing Network

IDU B

IDU A

3a

4

1

1

3b

3c

2b

2a

Tower Structure

2c

1a

HSB-IDU



144 B4008 Rev. M

CityLink

Figure V-7 Coax Cable Connection

CABLE CONNECTION

OUTDOOR UNIT ODU

BOTTOM OFBRANCHING UNIT

PROTECTIONSLEEVE97E12A-1

N - CONNECTOR

SEALING75N06D-1

HOSE CLAMP97Z6A-5

BOTTOM OFBRANCHING UNIT

PROTECTIONSLEEVE

N - CONNECTORfemale, chassis

N - CONNECTORmale, cable

HOSE CLAMP

APPLY SEALINGCOMPOUND HERE

(NOTE 1)

1. Slide the Protection Sleeve and the Hose Clamp over the connector and onto the cable.

2. Connect the cable to the ODU. Press the protection sleeve over the connector and tighten the

connector by hand (using the sleeve gives a good hand-grip when tightening).

3. Pull the protection sleeve backwards and apply Sealing Compound (Plast 2000) onto the top end of

the sleeve. Press the sleeve upwards and over the connector until it stops into the groove around the

ODU connector‘s nut and washer.

4. Adjust the clamp diameter with a screwdriver and slide in the clamp between the sleeve and the

ODU‘s cooling ribs and place it over the connector head.Tighten the clamp with a screwdriver.

NOTE: ALL CODED ITEMS AREINCLUDED IN KIT ABZ278



B4008 Rev. M 145

IDU Installation

Figure V-8 Branching Unit Grounding Point

Attach grounding cable (10mm2) to this

point with the M8 nut and washers.

Figure V-9 Hot Standby and

2+0 DF-SP Branching Unit Grounding Point

Attach grounding cable (10mm2) to this

point with the M6 nut and washers.

WARNING!

Do not use the Branching Unit's sealing screws for groundingpurpose.

WARNING!

Do not use the Branching Unit's sealing screw for grounding

purpose.



146 B4008 Rev. M

CityLink

This page is intentionally left blank.

6.0 Change of Fan-Cassette

Fan cassette (if equipped) is located on the right hand side of the IDU. The

cassette may be replaced on live unit, without traffic interrupt. Withdraw old

cassette by pulling on knob on front of unit and replace with new unit.

Some combinations of circuit boards requires the use of fan-cassette in order

to control heat. In case a fan-cassette is to be installed in a unit not previously

having one, a blind front cover will have to be unscrewed and discarded

before installing a new cassette.



B4008 Rev. M 147

Preparations for Operation

Preparations

for Operation

SECTION VI



148 B4008 Rev. M

CityLink

1.0 General

This section assumes that the radio terminal has been installed according

to the guidelines in Sections II - V.

1.1 Equipment required• Voltmeter for AGC voltage monitoring (with cable to connect to

BNC-connector)

• Cable for connection between AGC monitoring point and voltmeter.

1.2 Connections

See Appendix I for a more detailed description of connectors.

Verify the following:• Correct line interface plug-in board is installed.

• Cable for main traffic is connected.

• Connection of IDU safety ground. Use min. 10 mm2 cable.

• Coaxial cable between IDU and ODU is connected.

• Cable between IDU and the PC running the configuration & set-up

program is connected. NOTE: RJ-45 modular plugs used on patch

cables etc. must mechanically comply with Federal Communications

Commission - Part 68 (FCC-68).

Optionally the following connections may be used:

• ALM/AUX connector for parallel alarm inputs and outputs.

• 2x64kbit/s connector for 64kbit/s serial channels utilising bytes in

the Section Overhead.

• NI-1 and/or NI-2 connectors for interface to other Nera equipment.

• 2Mbit/s WAYSIDE connectors for interface to 2Mbit/s wayside

traffic channel utilising bytes in the Section Overhead.

• 2MHz SYNC connectors for synchronisation purposes.• Handset and extension connectors.

• LAN Interface connectors.

2.0 Power onApply power to the IDU by connecting the power cable. The radio link

start-up procedure and self-diagnostics will start to execute.

When power is applied to the IDU the system will perform self test, this

will take a few seconds.



B4008 Rev. M 149

Preparations for Operation

2.1 NEW-NMS/NEW-Configurator Startup and

connecting to Network Elements

The NEW-NMS/NEW-Configurator (Nera Element vieW-Network Man-

agement System/ -Configurator) program must be installed on a PC

satisfying the following minimum requirements:

• NT4.0/Win95/Win98 operating system

• Pentium 133MHz processor

• 32MB memory

• 200MB disk size

• 1 COM port

• CD-ROM drive

Follow carefully the program installation instructions to make sure the

program is successfully installed.

The element viewer can monitor the Network Elements (NEs) using a

serial connection (RS-232) or a TCP/IP connection (or both for different

network elements). Apply all external connections to the PC before the program is started.

A serial connection must be used the first time the network manager/

configurator is connected to the CityLink, because the IP address must be

set in the CityLink, before a TCP/IP connection can be established.

2.1.1 Starting NEW-NMS/NEW-Configurator with

Serial Connection (RS-232/ LCT).

Apply the serial cable to one of the serial ports of the PC and the LCT port

of the CityLink. Start the program. A Log on dialog box pops up. Log on

to the network with your user id and password.

Note!NEW-NMS' security system has initially one user account:

User ID: adminPassword: adminpasswd

It is strongly recommended to change this password!

The program has an auto discover function which automatically discovers

NEs connected to the serial ports of the PC when starting. If some NEs are

connected to the serial ports of the PC, the network topology is automat-ically discovered and presented in the Explorer view. Press Add to include

discovered elements in the network topology of the program. The auto

discover function can also be manually executed by selecting Discover



150 B4008 Rev. M

CityLink

from the File menu. When discovering the network manually, the program

looks for NEs at the open ports listed in the Communication dialog box

(select Communication from the Configuration menu).

2.1.2 Starting NEW-NMS/NEW-Configurator with

TCP/IP Connection.

(Assumes the TCP/IP address is configured in the CityLink )

Apply Ethernet connections to both the CityLink and PC. Start the

program. A Log on dialog box pops up. Log on to the network with your

user id and password.

Note!

NEW-NMS' security system has initially one user account:

User ID: adminPassword: adminpasswdIt is strongly recommended to change this password!

The program does not know the IP-address of the network element so the

connection must be manually established. To configure a TCP/IP connec-

tion to the network element, select Communication from the Configu-

ration menu. Press the Add button and type the IP address of the NE in

the address field of the dialog box which pops up. Press OK to save the

changes, and OK to close the Communication Configuration dialog box.Select Discover from the File menu. Press Add to include discovered

elements in the network topology of the program. The accepted network

elements will be discovered and presented in the Explorer view.

2.2 Initial configuration

When the program has established contact with the CityLink, some

configurations must be set before antenna alignment can be performed.

A Configuration Wizard will guide you through the initial configurations.

Start the Wizard by selecting the network element in the Explorer view.

Then select Configuration > Wizard from the right mousebutton context

menu. Follow the Wizard instructions.

All the configuration settings are described in Section VII; Configuration.

You are now ready to proceed with antenna alignment. Please refer to

Section IV Chapter 6.0 (ODU Type I & III) or the installation manual for the actual antenna (ODU Type II)



B4008 Rev. M 151

Configuration with NEW-Configurator

Configuration byNEW Configurator

SECTION VII



152 B4008 Rev. M

CityLink

1.0 GeneralThis section assumes that the Preparations for Operation described in

Section VI has been performed for the complete radio link hop.

Configuration of the Network Elements is done from the Explorer Viewwhich can be launched by selecting Explore Net from the View menu.

Configuration of Network Elements is achieved using a set of property-

sheets. The property-sheets are modeless, so configuration of several

different modules can be displayed simultaneously.

To open the configuration property-sheets:

Press the Right mouse-button on the Network Element node/leaf you

want to view/change the current configurations. A dynamic menu pops up.Open the Configuration sub-menu and select the configuration-specific

menu item.

The configuration property sheets can also be launched by selecting/

marking an NE node/leaf in the Explorer View and then selecting the

configuration-specific menu item under the Edit sub menu in the Config-

uration menu.

The property-sheets are divided into two categories by means of function-ality:

Configuration Property sheets with Multiple Settings:

The program retrieves the current settings from the NE when the property-

sheet is opened. No message is sent to the element and no data is modified

in NEW’s data structure before the user presses one of the property-sheet

buttons:

Figure VII-1 Buttons on Configuration property sheets with

multiple settings

Buttons:

Get: Retrieves the current settings from the NE.

Set: Sends the current settings to the NE.Close: Closes the property-sheet without saving or setting any data

Help: Displays help for the active property-page.

.



B4008 Rev. M 153


••••• To change the settings:

1 Get the current settings from the NE by pressing Get.

The current NE settings are automatically retrieved when the property-

sheet is opened.

2 Alter the settings.

3 Press Set to send the changes to the NE.

Configuration Property sheets with Single Interactive Settings:

The program retrieves the current NE settings when the property-sheet is

opened. Has no Get, Set or Save buttons; All functional buttons are placed

in the property-pages. A message is sent to the Network Element imme-

diately when a control is changed or a button is pressed.

Property-sheet buttons:

Figure VII-2 Buttons on Configuration property sheets with

single interactive settings

Buttons:

Close:Closes the property-sheet.Help: Displays help for the active property-page.

Figure VII-3 Configuration property sheet information field

All property-pages have an information field at the bottom reflecting the

current status of the data shown in the property-page and the date and time

the property sheet data was retrieved from the network element.



154 B4008 Rev. M

CityLink

2.0 Element Node

2.1 Element Id

The CityLink Element Id property sheet shows some main information

about the Network Element like name, type, serial number and different

addresses. The fields with white background can be altered by users with proper user privileges. The gray fields are non editable.

The Element Id configuration sheet can be opened from the Configura-

tion context menu of the Element node in the Explorer view. The sheet

can also be invoked by selecting (highlighting) the Element node in the

Explorer view and then selecting Edit Element Id from the Configura-

tion menu.

Figure VII-4 Element ID Configuration Sheet



B4008 Rev. M 155


Fields: Description:

Serial number: The serial number of the NE. (Not editable)

NE type: The type of NE. (Not editable)

Name: The name of the NE (max. 32 characters)

Section address: The section address of the NE. (1-254)NE address: The NE address (1-128). Used for identification of

NEs within a section.

MAC address: The Media Access Control address of the NE.

Used for OSI-Management. (Not editable)

NSAP address: The Network Service Access Point address of the NE.

Used for OSI-Management.

IP address The Internet Protocol address of the NE.

Hot standby: This field is checked if the NE is a hot standby element.

To change the settings:

1 First, get the current settings from the NE by pressing Get.

(The settings are automatically retrieved from the NE when the

property-sheet is opened.)

2 Alter the settings you want to change.




156 B4008 Rev. M

CityLink

2.2 Available Functions

The available functions property sheet shows the functions available at the

network element. All these functions are additional CityLink functions.

The user has paid extra to get these functions. Contact your Nera equip-

ment supplier to order functions. You will get an encrypted authentication

string in return.

The Available Functions configuration sheet can be opened from the

Configuration context menu of the Element node in the Explorer view.

The sheet can also be invoked by selecting (highlighting) the Element

node in the Explorer view and then selecting Edit Available Functions

from the Configuration menu.

Figure VII-5 Available Functions Configuration Sheet


Automatic transmitted ATPC is a function for effectively reducing

power control (ATPC) interference probabilities..

IP stack The NE has an integrated IP stack. Synchronous equipment Synchronous equipment timing source is

timing source (SETS) available.

Simple network management An SNMP management agent is available.

protocol (SNMP)

64 Kbit/s channels Two 64 Kbit/s channels can be inserted into

the STM-1 Section Overhead (SOH ).

2 Mbit/s wayside channel One 2Mbit/s wayside channel can be inserted

into the STM-1 Section Overhead (SOH ).

Alarm auxiliary function A unit containing an auxiliary alarm unitand an auxiliary output unit is available.

STM-1



B4008 Rev. M 157


2.3 Notifications

The NE can send notifications to NEW when specific events occur. When

using notifications, NEW gets new information faster than if only polling

is used. Polling should however be used in addition to notifications. The

NE keeps individual notification settings for each NEW that is logged on

to the NE, such that the settings made from one NEW only apply to that NEW. Note that the settings will be reset to default when NEW logs on to

the NE or when the IDU is reset.

A notification is enabled when the corresponding checkbox is checked ( ).

The Notifications configuration sheet can be opened from the Configu-

ration context menu of the Element node in the Explorer view. The sheet


Explorer view and then selecting Edit Notifications from the Config-

uration menu.

Figure VII-6 Notifications Configuration Sheet



158 B4008 Rev. M

CityLink

Fields: Choices: Description:

Event s

Alarm When checked, Alarm notifications will be

sent from the NE to the program.

Security When checked, Security notifications will be sent from the NE to the program.

Switching When checked, Switching notifications will

be sent from the NE to the program.

Alarm (When the Alarm Events is disabled,

severity these functions are inactive)

Critical When checked, Alarm notifications will be

sent from the NE to the program if Critical

alarms occur.

Major When checked, Alarm notifications will be

sent from the NE to the program if Major

alarms occur.

Minor When checked, Alarm notifications will be

sent from the NE to the program if Minor

alarms occur.

Warning When checked, Alarm notifications will be

sent from the NE to the program if Warningsoccur.



B4008 Rev. M 159


2.4 NE Clock Page

The NE Clock sheet lets you synchronize the Network Element Date/Time

with the NEW-NMS / PC Date/Time. (The NE Clock is set to the same

date/time as the PC Clock).

The NE Clock configuration sheet can be opened from the Configurationcontext menu of the Element node in the Explorer view. The sheet can

also be invoked by selecting (highlighting) the Element node in the

Explorer view and then selecting Edit NE Clock from the Configura-

tion menu.

Fields: Description:The NE's Clock: The Date and Time retrieved from the

Network Element.

Difference from The difference between the PC clock and the

Network Element Clock.

Figure VII-7 NE Clock Configuration Sheet



160 B4008 Rev. M

CityLink

2.5 Software Download

CityLink Application software can be downloaded through the NEW-NMS/

NEW-Configurator program.

The SW Download configuration can be started from the Configuration

context menu of the Element node in the Explorer view. The sheet canalso be invoked by selecting (highlighting) the Element node in the

Explorer view and then selecting Edit SW Download from the Config-

uration menu.

To download new NE application code:

1. The process of downloading starts with selecting the file containing

the application code. The file has extension: .bin. When a .bin-file is

selected, a dialog box will appear.

2. Verify that the correct version of the code file is chosen. Press Cancel

if wrong code file is chosen.

3. Press Start Download

4. Wait until the download is finished.

New application software is now downloaded at the NE. Now the NE must

start to use the new software. The new software will not start to execute

until it is activated. This is done from the SW Version property sheet.



B4008 Rev. M 161


2.6 Software Versions

The SW versions property sheet shows the software revisions and their

status. The IDU contains two application code memory banks for both the

SU (IDU) and the Transceiver (ODU). Both the IDU and the ODU use

application code from one bank, while the other bank is available for SW

download. New software can be downloaded (see Chapter 2.5 SWDownload) in the unused bank while the IDU or ODU is executing the code

of the other bank. The user may also select which bank to execute the

application from if both banks contain valid software.

The ODU contains an application code software bank in addition to the two

banks in the IDU. The ODU software is copied from the active IDU bank

to the ODU bank during the ODU boot process.

The SW Versions configuration sheet can be opened from the Configu-ration context menu of the Element node in the Explorer view. The sheet


Explorer view and then selecting Edit SW Versions from the Config-

uration menu.

Figure VII-8 SW Version Configuration Sheet



162 B4008 Rev. M

CityLink


SW Component Name of the software

Bank Software location

Revision Software revision

Status Idle:Software is not being executed.

Active:Software is being executed.

Loading: SW is downloading to this bank.

Invalid: Incomplete or invalid SW; SW bank

has not been used or a SW download has

failed.

Not contact with unit: The IDU does not

have contact with the unit containing this SW.

To activate a memory bank:1 Select the unused bank (status: Idle) by clicking the left mouse button.

2 Press the Set Active button

The NE will be reset and when it starts, the application code of the chosen

bank will be executed.



B4008 Rev. M 163


3.0 Transmission Node

3.1 Transmission Configuration (Section Termination)

3.1.1 Section Termination, SW-version < R2A00

The CityLink Section Termination sheet shows the channel configurationof the network element. For CityLink systems, the number of the different

channel settings is fixed. Only the Channel Termination can be changed.

The Section Termination configuration sheet can be opened from the

Configuration context menu of the Transmission node in the Explorer

view. The sheet can also be invoked by selecting (highlighting) the

Transmission node in the Explorer view and then selecting Edit Section

Termination from theConfiguration menu.


Regular channels: The Number of Regular Channels.

Protection channels: The Number of Protection Channels.

Regular co. channels: The Number of Regular Co. Channels.

Protection co. channels: The Number of Protection Co. Channels.

Channels: List of NE Channels with the channel properties.Channel Name of the channel.

Termination MS (Multiplexer section) orRS (Regenerator Sec-

tion) (Double-click the field to edit).

The MS and RS are parts of the STM-1 Section

overhead. Together MS and RS form the total SOH.

Figure VII-9 Section Termination Configuration Sheet


1. Get the current settings from the NE by pressing Get.

2. Alter the settings you want to change. To change the Termination

settings, double-click in the appropriate cell in the list. A Combo-box

where you can select RS or MS is then displayed

3. Press Set to send the changes to the NE.



164 B4008 Rev. M

CityLink

3.1.2 Transmission Configuration, SW-version ≥≥≥≥≥ R2A00

The Transmission Configuration sheet is used to set the transmission

standard and termination on the element. When the applied termination is

different from RST, the sheet is also used to configure the SETS functionality.

A CityLink element may support different extension boards. This includesthe DS3/E3 Extension Board, the STM-1 Extension Board or the 21x2Mbit/

s tributary board. Each element will, however, only support one extension

board at a time. From the Transmission Configuration sheet the user can

enable the functionality of the specific extension board. The 21x2Mbit/s

extension board assumes a frame structure which contains 63 E1s. To enable

this board, select the termination to be Lower Order Path Termination -

LOPT. If the DS3/E3 Extension Board or the STM-1 Extension Board is

mounted, the frame structure must be set explicitly.

The Transmission Configuration configuration sheet can be opened from

the Configuration context menu of the Transmission node in the Explorer

view. The sheet can also be invoked by selecting (highlighting) the Trans-

mission node in the Explorer view and then selecting Edit Transmission

Configuration from theConfigurationmenu.

Figure VII-10 Section Termination Configuration Sheet



B4008 Rev. M 165



Termination Enabling The type of termination this element shall

support. Legal values are:

• RST

• MST• Lower Order Path Termination - LOPT

• Enable X-Connect (available only if X-

Connect Extension Board is equipped)

• Enable DS3/E3 (available only if DS3/E3

Extension Board is equipped)

Note: If this setting is changed and applied to

the element, the equipment will perform a soft-

ware reset.

Transmission Standard The Transmission System used. Legal values are:

• SDH

• SONET

Element Type The type of «timing element» we’re supposed to

be. This is important in a network where SETS is

applied. Legal values are:

• SEC

• SSU Local (G.812 Local)

• SSU Transit (G812 Transit)

• PRC

SSU Clock Source This field will only be enabled whenever the

Element Type is set to either SSU (G.812

Local) or SSU (G.812 Transit). The SSU is an

external clock regenerator or filter that will remove jitter from

the clock on its input. It will then output a regenerated clock on itsoutput. The SSU is connected to the element via the

2MHz synch RJ-45 plug on the front of the IDU.

The clock source can be one of the following:

• LINE

• RADIO

• Any dropped 2Mbit/s

• LINE EXT

The last option will only be available if the X-

Connect Extension Board is present.



166 B4008 Rev. M

CityLink

SSU Squelch Level This field will only be enabled whenever the

Element Type is set to either SSU (G.812 Local) or

SSU (G.812 Transit). If the quality of the clock source

changes to a quality that is below this «quality

squelch» level, the 2MHz synch output to the SSU

will be squelched. This in turn will cause the SSU toenter holdover mode (or free-running), i.e. the clock

quality it sends to the 2MHz synch input will have a

G.812 quality (ref. ITU-T Recommendation G.812)

that is based upon the internal oscillator in the SSU.

Legal squelch levels are:

• Better or equal G.813

• Better or equal G.812 Local

• Better or equal G.812 Transit

• Equal G.811

Clock Priority This is the first column in theClock Priority list view.

This field will only be enabled whenever theElement

Type is set to SEC. This is just a number specifying

the priority of the rows where 1 is the higher priority.

The user can not change anything in this column.

Clock Source This is the second column in the Clock Priority list

view. This field will only be enabled whenever the

Element Type is set to SEC. If e.g. the user double

clicks the first cell in this column, a combobox will be

shown over the cell. The user can than select from

where the clock to this priority list item shall be taken.

This can also be done for the 2nd and 3rd cell in this

column. The 4th cell, on the other hand, is the internal

oscillator which will be used whenever the element is

in holdover mode. This cell can’t be altered. Legal

values are:

• LINE

• RADIO

• 2MHz Synch

• LINE EXT

Note: Only one of the priority list items can be

configured to take its clock source from a 2Mbit/s

tributary at the time. This is due to HW constraints.



B4008 Rev. M 167


Clock Quality This is the third column in the Clock Priority list view. This

field will only be enabled whenever theElement Type is set

to SEC. If the Clock Source field for a specific priority list

item is set to either STM-1 LINE or STM-1 RADIO, the

corresponding cell in this column will be set to SSM and

will be grayed out (i.e. disabled). This means that the contentof the S1-byte (located in the MSOH) will inform the element

of which clock quality the traffic in the specific directions is

clocked with. If theClock Source field for a specific priority

list item is set to be taken from the 2MHz Synch input, or it

is to be taken from a 2Mbit/s tributary, their clock quality

aren’t embedded in the traffic in any way. This means

that the user will have to set their clock qualities manually.

In these cases, the cell in question in this column will be

enabled and the user can set the quality. Legal values are:• G.813

• G.812 Local

• G.812 Transit

• G.811

In addition to these, SSM will also be present in the list but

can not be selected.

Note: Ref. ITU-T for more information regarding the

different G.8xx recommendations.

Enabled This is the fourth column in the Clock Priority list view.

This field will only be enabled whenever the Element Type

is set to SEC. If a specific priority list item has this cell

checked it will be present in the clock priority scheme. If

not it is ignored.

Active Priority This is the fifth column in theClock Priority list view. This

field presents the currently active clock. The field isupdated each time the “GET” button is pressed.

Note: If the user, by means of the Drop or Continue dialog, removes any of

the tributaries in the list above, they will automatically be removed from

the list!

Buttons:

SSM Dialog: This button will only be visible when the in user level of the

logged in user is equal to or greater than Administrator. It

will spawn a new dialog that will poll for the SSM in both

radio- and line direction of the STM-1 traffic.



168 B4008 Rev. M

CityLink

Get: Click this button to retrieve the current settings from the

NE. Any modifications done to the GUI elements will be

lost and the «dirty» token will be removed.

Set: Click this button to send the settings to the NE. Any

modifications done to the GUI elements will be applied

the NE and the «dirty» token will be removed.Close: Click this button to close the property sheet.

Help: Press this button to get help on the current property sheet.

For help on an item, click at the top of the dialog box,

then click the item.

A brief description of the different terminations:

RST:

This is the default setting on the element when delivered from the factory.

With this configuration the SDH structure is ignored, i.e. it can be anything because the virtual containers will not be accessed. The equipment will

monitor and re-generate B1 pulses. M1 REI and B2 will only be monitored.

Figure VII-11 shows the Transmission Configuration dialog when this

setting is applied.

Note: When the element is RST, all the SETS elements of the dialog are

disabled. This is because SETS only is used when the element is configured

as MST or Lower Order Path Termination - LOPT. Even though the SETS

functionality is disabled, the user can see the last applied MST settings.

Figure VII-11 Transmission Configuration, RST



B4008 Rev. M 169


Figure VII-12 Transmission Configuration, MST

MST:

With this configuration the SDH structure is ignored, i.e. it can be anything

because the virtual containers will not be accessed. The equipment will

monitor and regenerate B1-, M1 REI- and B2-pulses. Figure VII-12 shows

how the dialog looks when this setting is applied.

Figure VII-13 Transmission Configuration, LOPT

Lower Order Path Termination - LOPT:

With this configuration the SDH structure is assumed to have a VC-12mapping and the the equipment will monitor and regenerate B1, M1 REI, B2

and BIP-2 pulses.Figure VII-13shows how the dialog looks when this setting

is applied.



170 B4008 Rev. M

CityLink

Enable X-Connect:

To enable the X-Connect functionality, select “Enable X-Connect” from the

“Termination enabling” combo box and press the “SET” button. The SDH

structure may be configured from the “Frame Structure” page.

Enable DS3/E3:

To enable the DS3/E3 functionality, select “Enable DS3/E3” from the“Termination enabling” combo box and press the “SET” button. The SDH

structure may be configured from the “Frame Structure” page.

Figure VII-14 Transmission Configuration, Enable X-Connect

Figure VII-15 Transmission Configuration, Enable DS3/E3



B4008 Rev. M 171


Enable 21x2:

This functionality is only available with new target software. To enable the

21x2 functionality, select “Enable 21x2” from the “Termination enabling”

combo box and press the “SET” button. The SDH structure may be config-

ured from the “Frame Structure” page.

Figure VII-16 Transmission Configuration, Enable 21x2



172 B4008 Rev. M

CityLink


Direction From which STM-1 direction the S1 byte is monitored.

This can be either Line or Radio

Last change Will show the last time the specific S1 byte changed it’s

value.

S1 byte The current content of the specific S1 byte.Description A human readable interpretation of the S1 byte. These can

be:

3.1.3 SSM - Synchronization Status Message

The SSM sheet is used to monitor the received S1-byte in the two STM-

1 directions; LINE and RADIO.

The SSM - Synchronization Status Message configuration sheet can be

opened from the Section Termination sheet by clicking the SSM Dialog button on this sheet.

Note: The SSM Dialog button will only be visible for Administrator

users in the Section Termination sheet.

Figure VII-17The SSM Configuration Sheet



B4008 Rev. M 173


3.2 Alarm Indication Signal Insert

(For advanced users)

The Path Trace functionality and the AIS (Alarm Indicator Signal) function-ality are used for verifying that the received STM-1 frames are the frames we

want to receive (correct routing, frequency alignment...). This is done by

either inserting a fixed byte or a user defined ASCII string in the J0 slot in the

RSOH, or a two bit RF ID symbol at the transmit end. This is done from the

path trace sheet. The RF ID functionality is only available at the Radio side.

The radio that receives the STM-1 frames must have the same Trace string

(J0) or RF ID defined in the AIS insert sheet. If there is a mismatch, an AIS

can be inserted. An AIS can also be inserted if the HBER threshold is

exceeded.

The AIS Insert configuration sheet can be opened from the Configuration

context menu of both the Transmission Radio and Line Rx nodes in the

Explorer view. The sheet can also be invoked by selecting (highlighting)

one of the Transmission Radio and Line Rx nodes in the Explorer view

and then selecting Edit AIS Insert from the Configuration menu.

S1 byte SDH synchronization quality level description

0000 Quality unknown (existing sync network)

0001 Reserved

0010 G.811

0011 Reserved

0100 G.812 transit0101 Reserved

0110 Reserved

0111 Reserved

1000 G.812 local

1001 Reserved

1010 Reserved

1011 Synchronous equipment timing source (SETS)

1100 Reserved

1101 Reserved1110 Reserved

1111 Do not use for synchronization



174 B4008 Rev. M

CityLink

Fields: Subfields: Description:

Insert AIS when An AIS is inserted when the Viterbi HBER

Viterbi HBER threshold is exceeded. (See Chapter 4.4.9threshold exceeded for setting of BER threshold.)

Insert AIS when An AIS is inserted when there is a mismatch

trace mismatch between the Trace String set in the Path Trace

sheet and Trace String set on this sheet.

Insert AIS when An AIS is inserted when there is a mismatch

RF ID mismatch between the RF ID set in the Path Trace

sheet and RF ID bit set on this sheet.The RF ID functionality is only available at

the Radio node.

AIS remove delay 1 - 200 seconds

Regenerator

section

trace (J0) Not used The Regenerator Section Trace String is not

used.

Fixed byte The Regenerator Section Trace String is one

byte ( =8 bit) long.

Figure VII-18 AIS Insert Configuration Sheet



B4008 Rev. M 175


Fields: Subfields: Description:

User message The Regenerator Section Trace String is a user de-

(ASCII) fined message ASCII (sixteen bytes =128bits long)

Expected: The ASCII string or fixed byte to be compared with

received J0 in RSOH. If mismatch, AIS will be

inserted if the Insert AIS when trace mismatch

box is checked. The Expected field normally con-

tains the same values as the Trace string in thePath

trace property sheet at the transmit end of the path.

Received: The ASCII string or fixed byte in received J0 in

RSOH.

Status: The status of the Regenerator Section Trace:

•

OK: Expected and received Regenerator Section Trace are identical.

• RS-TIM alarm: (Regenerator Section Trace

Identifier Mismatch) Mismath between

expected and received RS Trace.

• LOF error: Loss of frame alarm on received

STM-1 signal. Thus, J0 is not available. Alarm

status, OK or RS-TIM alarm will be latched.

• CRC error: CRC error in received Regenerator

Section Trace. (Only in User Message mode)• Invalid: Not valid User Message received.

RF ID: (The RF ID functionality is only available at the

Radio node)

Not used/Used: RF_ID MS3 bit on/off

Expected: The value to be compared with the RF ID byte in

the received SOH. If mismatch, AIS will be in-

serted if the Insert AIS when RF ID mismatch

box is checked. The Expected field normallycontains the same values as the RF ID value in the

Path Trace property sheet at the transmit end of

the path.

Received: The received RF ID value.

Status: The status of the RF ID:

• OK: Expected and received RF ID values are

identical.

• RF-ID alarm: Mismatch between expected and

received RF ID values.

• Invalid: Not valid RF ID value received.



176 B4008 Rev. M

CityLink

Figure VII-19 Path Trace Configuration Sheet

3.3 Path Trace

(For advanced users)

The Path Trace functionality and the AIS (Alarm Indicator Signal) function-

ality are used to test that the received STM-1 frames are the frames we want

to receive (correct routing, frequency alignment. . . . ). This is done by either

inserting a fixed byte or an user defined ASCII sting in the J0 slot in the RSOH,or a two bit RF ID symbol at the transmit end. This is done from the path trace

sheet. The RF ID functionality is only available at the Radio side. The radio

that receives the STM-1 frames must have the same Trace string (J0) or RF

ID defined in the AIS insert sheet. If there is a mismatch, an AIS can be

inserted. An AIS can also be inserted if the HBER threshold is exceeded.

The Path Trace configuration sheet can be opened from the Configuration

context menu of both the Transmission Radio and Line Tx nodes in the

Explorer view. The sheet can also be invoked by selecting (highlighting) theone of theTransmission Radio and Line Tx nodes in the Explorer view and

then selecting Edit Path Trace from the Configuration menu.



B4008 Rev. M 177


Fields: Subfields Description:

Regenerator section

trace string

Enabled When checked the specific Trace

String is sent in the J0 byte.

Fixed byte The Regenerator Section TraceString is one byte ( =8bit) long.

User message The Regenerator Section Trace

(ASCII) String is a user defined message

ASCII (sixteen bytes =128bits long)

Trace string Specifies the data (Fixed byte or

User Message) to be inserted into

the J0 byte.

RF ID

Not used/Used RF_ID MS3 bit on/off

Two bit combination.



178 B4008 Rev. M

CityLink

4.0 Equipment Node

4.1 Network Routing

The active and initial routing tables map incoming messages that are

addressed to other NEs, to different communication ports.

The active routing table is used by the IDU to route messages to other NEs,

using the best path detected. The IDU regularly searches for connected

NEs through all enabled communication ports to detect any changes in the

network topology. This table is initialised with the initial routing entries

when the IDU is rebooted (and when the initial routing table is configured

by the user) and then evolves towards an optimal routing table.

The initial routing table is used after the IDU has been booted. This table

is used as a starting point for the routing mechanism, and will thus, if

properly set, decrease the time the NE uses to create a sufficient active

routing table. Initial routing entries can be manually added and active

routing entries can be copied to the initial table.

The Routing Table configuration sheet can be opened from the Config-

uration context menu of the Equipment node in the Explorer view. The

sheet can also be invoked by selecting (highlighting) the Equipment node

in the Explorer view and then selecting Edit Routing Table from theConfiguration menu.



B4008 Rev. M 179


Figure VII-20Routing Table Configuration Sheet,

Active Tab (top) and Initial Tab (bottom)



180 B4008 Rev. M

CityLink


Auto/Manual If Auto, the router may update the entry in the active

routing table automatically based on shortest path/

lowest weight. If Manual, the entry is never changed by

the router and fixed route configuration is used.

Section The Section number of the addressed NE (1-128).NE The NE address of the destination NE. If this number is

255, section routing is used. That means that this routing

entry is used for all NEs in the specified section.

Possible values: 1...62 (and broadcast address 255).

Port The communication port of which the messages are to be

routed through. Possible values:

• NI1

• NI2

• DCC Line

• DCC Radio

• OSI TP4 tunnel 1 (Server)

• OSI TP4 tunnel 2 (Server)

• OSI TP4 tunnel 1 (Client)

• OSI TP4 tunnel 2 (Client)

• TCP/IP tunnel 1 (Server)

• TCP/IP tunnel 2 (Server)

• TCP/IP tunnel 1 (Client)• TCP/IP tunnel 2 (Client)

Weight A computed weight that gives an indication of the

communication capacity to the destination network

element. A high number denotes a longer response time.

Buttons:

Add: Displays the Add Routing Entry dialog box where a new

initial routing entry can be configured.

Edit: Displays the Edit Routing Entry dialog box where the

selected initial routing entry can be configured.

Delete: Deletes the selected routing entries.

Add to static: Copies the selected routing entries to the initial routing

table.



182 B4008 Rev. M

CityLink

Figure VII-21 IP Routing Configuration Sheet,General Settings

4.2.1 General Settings

The general settings page allows the user to control the general use of the

OSPF and RIP 2 protocols for the selected NE. Enabling of protocols on

specific interfaces are performed in theRip Interfaces andOSPF Interfaces

property pages.



B4008 Rev. M 183


Property page controls:

OSPF Protocol: Select parameter settings for OSPF routing protocol.

Enable: Enables the NE to handle OSPF routing.

Redistribute RIP: Allows OSPF to redistribute routing

information from RIP v2 routing protocol.

Redistribute Static: Allows OSPF to redistribute static

routing information.

Default Cost: Setting of default cost value used for

OSPF protocol.

The “Redistribute” options allow the OSPF protocol to pass

the routing information of other routing protocols.

For information to be passed between the OSPF and RIP protocols, the current NE must have both protocols enabled.

RIP Protocol: Select parameter settings for RIP routing protocol.

Enable: Enables the NE to handle RIP routing.

Redistribute OSPF: Allows RIP to redistribute routing infor-

mation from OSPF routing protocol.

Redistribute Static: Allows RIP to redistribute static routing

information.

Default Metric: Setting of default metric value used for

RIP protocol.

The “Redistribute” options allow the RIP protocol to pass the

routing information of other routing protocols.

For information to be passed between the OSPF and RIP

protocols, the current NE must have both protocols enabled.

IP Configurable List of interfaces available on the current NE forthe OSPFInterfaces: and RIP protocols (IP enabled interfaces).

Interfaces may be enabled for IP in the Communication Ports

page for the specific interface (e.g. NI interface on CityLink).



184 B4008 Rev. M

CityLink

4.2.2 Active Routes

Monitor active routes for current NE from this page.

Figure VII-22 IP Routing Configuration Sheet, Active Routes



B4008 Rev. M 185


4.2.3 Static Routes

Edit static routes regarding IP Routing using this page.

Figure VII-23 IP Routing Configuration Sheet, Static Routes


Add: Add a new static route to the list using the appearing dialog.

Edit: Select a row and press ‘Edit’ to open the ‘Edit Static Route’ dialog.In this dialog the settings for the selected route may be changed.

Delete: Deletes the selected row(s) from the list.

Note! Changes to the Static Routes are not transferred to the NE before ‘Set’

is pressed.



186 B4008 Rev. M

CityLink

4.2.4 RIP Interfaces

Edit RIP Interfaces for current NE from this page.

Note!

In order to edit the ‘RIP areas’ settings, the RIP protocol must be disabled

in the General Settings page.

Figure VII-24 IP Routing Configuration Sheet, RIP Interfaces


Add: Add a new RIP interface to the list using the appearing dialog.

Edit: Select a row and press ‘Edit’ to open the ‘Edit RIP Interface’ dialog.

In this dialog the settings for the selected interface may be

changed.


Note! Changes to the RIP Interfaces are not transferred to the NE before ‘Set’

is pressed.



B4008 Rev. M 187


4.2.5 OSPF Interfaces

Edit OSPF Interfaces for current NE from this page.

Note!

In order to edit the ‘OSPF Interfaces’ settings, the OSPF protocol must be

disabled in the General Settings page.

Figure VII-25 IP Routing Configuration Sheet, OSPF Interfaces


Add: Add a new OSPF interface to the list using the appearing dialog.

Edit: Select a row and press ‘Edit’ to open the ‘Edit OSPF Interface’

dialog. In this dialog the settings for the selected interface may be

changed.


Note! Changes to the OSPF Interfaces are not transferred to the NE before

‘Set’ is pressed.



188 B4008 Rev. M

CityLink

4.2.6 OSPF Areas

Edit settings for ‘OSPF areas’ for current NE from this page.

Note!

In order to edit the ‘OSPF Areas’ settings, the OSPF protocol must be

disabled in the General Settings page.

Figure VII-26 IP Routing Configuration Sheet, OSPF Interfaces

Property page controls:Add: Add a new OSPF area to the list using the appearing dialog.

Note! Use ‘Edit’ dialog to add new network ranges to existing areas.

Edit: Select a row and press ‘Edit’ to open the ‘Edit OSPF Area’ dialog.

In this dialog the settings for the area which the row belongs to may

be changed.


If a network range row is selected, only the network range is deleted.

In all other cases, the entire area is deleted.

Note! Changes to the OSPF areas are not transferred to the NE before ‘Set’

is pressed.



B4008 Rev. M 189


4.3 Communication Ports

4.3.1 DCC (Data Communication Channel)

The CityLink DCC (Data Communication Channel) is used to communicate

between the Supervisory Unit of the Network Element and Supervisory Units

of other Network Elements through the SOH of the STM-1 traffic.

There are two DCC ports. DCC Line at the line side and DCC Radio at the radio

side. The DCC Radio is always enabled. Nera Stack will always be enabled

at DCC Radio.

The Communication Ports configuration sheet can be opened from the

Configuration context menu of the Equipment node in the Explorer view.

Press the DCC tab to view/change the DCC settings. The sheet can also

be invoked by selecting (highlighting) the Equipment node in the Explor-er view and then selecting Edit Communication Ports from the

Configuration menu.


Figure VII-27 DCC Tab in Communication Ports Configuration Sheet



190 B4008 Rev. M

CityLink

Enabled Switches the DCC communication ports

on/off.

Channel: The Channel where the DCC are

inserted in the SOH.

Ch. 1-Ch XX CityLink has only one channel. This

field will always be ‘Ch. 1’ at CityLink.

Direction

Line DCC Line is inserted the line side of the

radio.

Radio DCC Radio is inserted the radio side of

the radio.

Timeslot: Shows which timeslot in the SOH the

DCC channels use. The user can change

the used timeslot by pressing SOH. The

SDH Frame Section Overhead Dialog

box will appear.

Stack

Nera NERA Stack.

Nera stack is always enabled on the

radio side (DCC Radio).

QECC QECC Stack

TCP/IP TCP/IP Stack LAPD Data link layer for the QECC protocol.

For more information refer to ITU-T

G.784 and ITU-T Q.921.

Network side Server for the LAPD requests.

User side Client for the LAPD requests.

PPP: (Point to Point Protocol) Data link

layer for the TCP/IP protocol.

(currently not implemented)

Active mode (currently not implemented)Demand dial (currently not implemented)

Direct mode (currently not implemented)

Passive mode (currently not implemented)



B4008 Rev. M 191


4.3.2 NI (Network Interface)

The CityLink NI (Network Interface) ports (NI-1 and NI-2) are used to connect

the Supervisory Unit of the Network Element to Supervisory Units of other

Network Elements. The NI ports on the front panel of the CityLink IDU are

used to connect the Network Elements. The NI ports can be set to a variety

of different configurations.

The NI 2 port, in the CityLink Radio, can be Enabled only if the Ethernet

function is Disabled, and vice versa.



Press the NI tab to view/change the NI settings. The sheet can also be

invoked by selecting (highlighting) the Equipment node in the Explorer

view and then selecting Edit Communication Ports from the Config-

uration menu.

Figure VII-28 NI Tab in Communication Ports Configuration Sheet



192 B4008 Rev. M

CityLink


Enabled Enables the NI port

Function CityLink The functionality of the NI port.

NL29x NI The baud rate and stack are

NL29x Qx grayed/whitened to indicate which

PDH Synchronous settings are necessary for thePDH Asynchronous different functionalities.

V.11 contra dir master

V.11 contra dir slave

V.11 co dir

Q1 V.11

NL29x V.11 contra

dir slave

Baudrate The baud rate (symbols pr. second)

of the NI port. If the field is grayed,

no baud rate is necessary to set.

1200 to 200000 Baud

Stack

Nera NERA Stack.

OSI OSI Stack

LAPD Data link layer for the QECC

protocol. For more information

refer to ITU-T G.784 and ITU-TQ.921.

Network side Server for the LAPD requests.

User side Client for the LAPD requests.

PPP: (Point to Point Protocol) Data link

layer for the TCP/IP protocol.

(currently not implemented)

Active mode (currently not implemented)

Demand dial (currently not implemented)

Direct mode (currently not implemented)Passive mode (currently not implemented)



B4008 Rev. M 193


Fields: Choices: Description:Baudrate: 1200 - 115200 Baudrate. The default baudrate is 115200.

4.3.3 LCT

The LCT port is the serial port (RS-232) that can be used to communicate with

a PC executing NEW-NMS. In this sheet the baud rate of the LCT port can

be changed.

WARNING!If you are communicating with the NE through the LCT (Serial) port and you

change the LCT baud rate you will loose contact with the NE until you

configure the NEW-NMS communication settings to the same baud rate

as the NE baud rate.



Press the LCT tab to view/change the LCT settings. The sheet can also be


view and then selecting Edit Communication Ports from the Config-

uration menu.

Figure VII-29 LCT Tab in Communication Ports Configuration Sheet



194 B4008 Rev. M

CityLink

4.3.4 Ethernet

In the CityLink Radio the Ethernet port can be Enabledonly if the NI 2 port

is Disabled, and vice versa. See chapter 4.3.2.


Configuration context menu of the Equipment node in the Explorer view.Press the Ethernet tab to view/change the Ethernet settings. The sheet can

also be invoked by selecting (highlighting) the Equipment node in the

Explorer view and then selecting Edit Communication Ports from the

Configuration menu.


Enabled Toggles Ethernet on/off

Stack OSI TP4 OSI Stack

TCP/IP TCP/IP Stack. Must be selected if IP

Tunneling is enabled.

Figure VII-30 Ethernet Tab in Communication Ports Configuration Sheet



B4008 Rev. M 195


4.3.5 IP Settings

The IP Settings sheet lets you view the IP address of the NE and configure

the subnet mask and default gateway. The IP address can be set in the

Element Id property sheet.

Fields: Description:IP address Shows the Internet Protocol (IP) address of the NE.

Subnet mask Type the Subnet Mask number obtained from your

network administrator. This number, combined with

the IP address, identifies which network your NE is on.

Default gateway For each adapter, type the correct IP address of the

default gateway used for forwarding packets to other

networks or subnets. This address should be provided

by the network administrator and is required for nodes

on internetworks. If this is not provided, IP functionalitywill be limited to the local subnet unless a route is

specified with the TCP/IP route command.

Figure VII-31 IP Settings Tab in Communication Ports Configuration Sheet



Press the IP Settings tab to view/change the NI settings. The sheet can


Explorer view and then selecting Edit Communication Ports from the

Configuration menu.



196 B4008 Rev. M

CityLink

4.3.6 IP Tunneling

A connection can be set up between two NEs through another network,

using the Internet Protocol. This is called IP Tunneling. Two connections,

IP Tunnel 1 and IP Tunnel 2, can be configured. Ethernet must be enabled

with TCP/IP Stack in order to use IP tunnels. Internet Protocol (IP)-

address, Section address and NE address are used for set up of IP tunnelsto other NEs. The IP tunnel must only be set up at one side of the tunnel.



Press the IP Tunneling tab to view/change the IP Tunneling settings. The

sheet can also be invoked by selecting (highlighting) the Equipment node

in the Explorer view and then selecting Edit Communication Ports

from the Configuration menu.


Enabled On/Off Toggles IP Tunneling on/off.

Remote section address The section address of the NE addressed

through the IP tunnel.

Remote NE address The NE address of the NE addressed

through the IP tunnel.Remote IP address The Internet Protocol (IP) address of

the NE addressed through the IP tunnel.

Figure VII-32 IP Tunneling Tab in Comm. Ports Configuration Sheet



B4008 Rev. M 197


4.3.7 OSI TP4 Tunneling

A connection can be set up between two NEs through another network,

using the OSI protocol. This is called OSI Tunneling. Two connections,

OSI TP4 Tunnel 1 and OSI TP4 Tunnel 2, can be configured. Ethernet must

be enabled with OSI Stack in order to use OSI TP4 Tunneling.

Network Service Access Point (NSAP)- address, Section address and NEaddress are used for set up of IP tunnels to other NEs.



Press the OSI TP4 Tunneling tab to view/change the OSI TP4 Tunneling

settings. The sheet can also be invoked by selecting (highlighting) the

Equipment node in the Explorer view and then selecting Edit Com-

munication Ports from the Configuration menu.


Enabled: On/Off Toggles OSI Tunneling on/off

Remote section address: Shows the section address of the NE

addressed though OSI TP4 Tunnel

Remote NE address: Shows the SU address of the NEaddressed though OSI TP4 Tunnel

Remote NSAP address: 0 to 20 bytes

Figure VII-33 OSI TP4 Tunneling Tab in Comm. Ports Configuration Sheet



198 B4008 Rev. M

CityLink

4.4 Looping

The loop settings are divided into five categories: Main traffic looping,

2Mbit/s Wayside traffic looping, 64kbit/s looping, 21x2Mbit/s looping and

DS3/E3 looping.

4.4.1 Main Looping

The Looping configuration sheet can be opened from the Configuration

context menu of the Equipment node in the Explorer view. Press the

Main tab to view/change the Main looping settings. The sheet can also be


view and then selecting Edit Looping from the Configuration menu.

Figure VII-34 Looping Configuration Sheet



B4008 Rev. M 199



Loop buttons: One button for each loop where the arrow indicates

which way the signal is looped. The colour of the loop

arrows describes the status of the loop:

Blue: The status of the loop is unknown. Loop informa-tion has not been retrieved from the NE, or a loop message

has just been sent to the NE and the GUI (Graphical User

Interface) is waiting for a response from the NE. (The

loop settings have not been confirmed by the NE). Note

that the loop cannot be toggled when the status is unknown.

Black: The loop is off (inactive)

Red: The loop is on (active)

Loops will be Displays the time of which all main traffic loops in the NE

automatically will be cleared. This time is set by the user when activatingcleared after: a loop.

The different main traffic loops (from left to right in Figure 34):

• 4. SORP, LT output to LR input loop, far-end (IDU)

• 1. SORP LR output to LT input loop, near-end (IDU)

• 14. IF loop, near-end (IDU)

• 15. IF loop, near-end (ODU)

• 16. RF loop, near-end (ODU)

Buttons:

Close: Closes the property sheet.

Help: Press this button to get help on the current property sheet page. For

help on an item, click at the top of the dialog box, then click the item.



200 B4008 Rev. M

CityLink

4.4.2 64 Kbit/s Looping


context menu of the Equipment node in the Explorer view. Press the 64

Kbit/s Looping tab to view/change the looping settings. The sheet can

also be invoked by selecting the Equipment node in the Explorer view and

then selecting Edit Looping from the Configuration menu.

Figure VII-35 Looping Configuration Sheet. 64kbit/s Tab



B4008 Rev. M 201


Fields:




••••• Blue: The status of the loop is unknown. Loop informa-tion has yet not been retrieved from the NE, or a loop

message has just been sent to the NE and the GUI is

waiting for a response from the NE. (The loop settings

have not yet been confirmed by the NE). Note that the

loop cannot be toggled when the status is unknown.

••••• Black: The loop is off (inactive)

••••• Red: The loop is on (active)

••••• Grey: The corresponding 64kbit/s channel is not enabled.

The different 64Kbit/s loops: (Figure VII-35 describes the loops)

• 40. 64Kbit/s G.703 (near end)

• 41. 64Kbit/s G.703 (far end)

• 42. 64Kbit/s V.11 (near end)

• 43. 64Kbit/s V.11 (far end)

Buttons:

Close: Closes the property sheet.Help: Press this button to get help on the current property sheet page. For




202 B4008 Rev. M

CityLink

4.4.3 2 Mbit/s Wayside Looping


context menu of the Equipment node in the Explorer view. Press the 2

Mbit/s Wayside tab to view/change the looping settings. The sheet can


Explorer view and then selecting Edit Looping from the Configura-tion menu.

Figure VII-36 Looping Configuration Sheet, Wayside Tab



B4008 Rev. M 203


Fields:




••••• Blue: The status of the loop is unknown. Loop informa-tion has yet not been retrieved from the NE, or a loop

message has just been sent to the NE and the GUI is

waiting for a response from the NE. (The loop settings

have not yet been confirmed by the NE). Note that the

loop cannot be toggled when the status is unknown.

••••• Black: The loop is off (inactive)

••••• Red: The loop is on (active)

••••• Grey: The corresponding 2Mbit/s channel is not enabled.

The different wayside loops: (Figure VII-36 describes the loops)

• 30. Wayside near end loop.

• 32. Wayside far end loop.



204 B4008 Rev. M

CityLink

PRBS Settings:

PRBS Generator: Generates a PRBS signal that can be inserted into the

transmit direction of the wayside channel.

Arrow buttons: Press a button to insert the PRBS

signal from the generator to the wayside channel.

There is one button for normal PRBS insert and one button for inverted PRBS insert. Red=enabled,

black=disabled, blue=unknown status,

grey=wayside disabled.

PRBS Check: Counts PRBS errors (An error is detected when the

signal differs from the expected PRBS signal).

Errors can be counted at the receive direction of the

wayside channel.

Arrow buttons: Press a button to enable the error

detection for the desired traffic direction. There isone button for normal PRBS check and one button

for inverted PRBS check. Red=enabled,

black=disabled, blue=unknown status,

grey=wayside disabled.

Count: The total number of deviations detected

between the received signal and expected PRBS

signal.

Rate: The number of deviations detected between

the received signal and expected PRBS signal per

second.

Reset button. Resets the cumulative counter.

Status:

· OK : Error check is valid.

· 2Mbit/s Wayside disabled: Wayside channel

is not enabled (See the 2Mbit/s Wayside property

sheet).

· Counter overflow: The error check is not valid because the counter has exceeded its limit (=232)

and wrapped around.

Sync loss: The error check is not valid due to sync

loss on the PRBS sequence.

Buttons:

Reset: Resets the PRBS Counter (includes the PRBS Rate)


Help: Press this button to get help on the current property sheet page.

For help on an item, click at the top of the dialog box, then

click the item.



B4008 Rev. M 205


4.4.4 21x2Mbit/s Looping (IDU: EMDK42A, 21x2Mbit/s

Extension board: 2NCS635A)

It is possible to set loops on each individual dropped 2Mbit/s. These loops

are further explained later in this chapter. It is only possible to set one kind

of loop at the time on a specific 2Mbit/s tributary.


context menu of the Equipment node in the Explorer view. Press the

21x2Mbit/s tab to view/change the tributary looping settings. The sheet

can also be invoked by selecting (highlighting) the Equipment node in the

Explorer view and then selecting Edit Looping from the Configura-

tion menu.

Figure VII-37 Looping Configuration Sheet, 21x2Mbit/s Tab



206 B4008 Rev. M

CityLink


2Mbit/s The physical port number on the 21x2Mbit/s tributary

board.

Loop type The user can select between three different loops.

Legal values are:• None

• 2Mbit-In → 2Mbit-Out Near End

• TMX→ DXC Near End

• 2Mbit-Out → 2Mbit-In Far End

Remaining time This is a status field for the remaining time the loop

will be present. When the time has expired, i.e. the

loops is switched off, this field will be set to Loop

cleared.

ON/OFF This column will contain cells that functions as check- boxes. If the user clicks a cell that isn’t checked, a

Loop Timer dialog will be launched (see Figure VII-

38). The user can set the duration of the loop from this

dialog. If the Loop type is None for a specific loop

item, the user can’t check this loop item’s checkbox.

Note: If the user, by means of the Drop or Continue dialog, removes any

of the tributaries in the list above, they will automatically be removed

from the list! This means that the number of loop items in the list (eight

in the figure above) will not be constant, but will be the same as in the

Drop or Continue dialog.

Figure VII-38 The Loop Timer Dialog Box



208 B4008 Rev. M

CityLink

The LoopingConfiguration Property sheet can be opened from the Config-

uration context menu of the Equipment node in the Explorer view. The sheet

can also be invoked by selecting (highlighting) the Equipment node in the

Explorer view and then selecting Edit Looping from the Configuration

menu .


Loop buttons: One button for each loop where the arrow indicates which way

the signal is looped. The colour of the loop arrows describes

the status of the loop:

Blue: The status of the loop is unknown. Loop information

has not been retrieved from the NE, or a loop message

has just been sent to the NE and the GUI is waiting for

a response from the NE. (The loop settings have not

been confirmed by the NE). Note that the loop cannot

be toggled when the status is unknown.

Black:The loop is off (inactive)Red: The loop is on (active)

Figure VII-39 Looping Configuration Sheet, DS3/E3



B4008 Rev. M 209


PRBS Generator: Generates a PRBS signal that can be inserted into one

or both directions of the PDH Port.

Arrow buttons: Press a button to insert the PRBS

signal from the generator to the PDH

Port. Red=enabled, black=disabled,

blue=unknown status.Inverted: When checked, the generated PRBS

signal is inverted.

PRBS Check: Counts PRBS errors. Errors can be counted on one of

the PDH ports in one of the DS3/E3 directions at a time.

Arrow buttons: Press a button to enable the error

detection for the desired traffic

direction. Red=enabled, black=

disabled, blue=unknown status.Inverted: When checked, an inverted PRBS

signal is expected.

Count: The total number of deviations

detected between the received

signal and expected PRBS signal.

Rate: The number of deviations detected

between the received signal and

expected PRBS signal per second.

Reset button: Resets the cumulative counter.

Status: • OK: Error check is valid.

• Counter overflow: The error check

is not valid because the counter

has exceeded its limit (=232) and

wrapped around.

• Sync loss: The error check is not

valid due to sync loss on the PRBS

sequence.

Message info field: Displays status of data exchange between GUI and

NE. Loop status is updated regularly (5 second

interval) as long as this property sheet is open.



210 B4008 Rev. M

CityLink


Article code: The Article Code

Serial no: The Serial number.

HW revision: Hardware revision

MAC address: The Media Access Control address of

the NE.

Production date: The date when the article was produced.

Test date: The date when the article was tested.

FAT date: The date when the Factory AcceptanceTest was found to be satisfactory.

4.5 In Door Unit (IDU)

4.5.1 IDU Production Data

The IDU production data property sheet shows the production serial

numbers and the production and test dates of the IDU. Only an administra-

tor can change the settings.

This sheet is also used for calibrating the Optical Line interface. Calibra-

tion is only needed when the optical unit is beginning to get old.

The IDU Production Data configuration sheet can be opened from the

Configuration context menu of the IDU node in the Explorer view. The

sheet can also be invoked by selecting (highlighting) the IDU node in the

Explorer view and then selecting Edit Production Data from the

Configuration menu.

Figure VII-40 IDU Production Data Configuration Sheet



B4008 Rev. M 211


4.5.2 64 kbit/s Channels

Two 64 kbit/s channels can be inserted into the SOH. Each of the 64 kbit/s

channel will occupy one byte of the SOH frame. Press the SOH Frame button

to select which bytes of the SOH that are used by the 64 kbit/s Channels.

One channel is the V.1l. This channel has to be of type V.11 Contra. The

other is the G.703 Channel. This channel can be either G.703 Co or G.703 Contra. Both channels can be retrieved from and inserted into the

line and radio side independently.

The 64 kbit/s Channels configuration sheet can be opened from the



Explorer view and then selecting Edit 64 kbit/s Channels from the

Configuration menu.

Figure VII-41 64 kbit/s Channels Configuration Sheet



212 B4008 Rev. M

CityLink

Fields: Choices: Description

Status:

Enabled Enables the 64 kbit/s Channel.

Disabled Disables the 64 kbit/s Channel.

Type: Choose linecode for 64 kbit/s Channel.

V.11 Contra (Channel V.11)

G.703 Co (Channel G.703)

G.703 Contra (Channel G.703)

Direction: Choose the direction the 64 kbit/s Rx

Channel should be extracted from.

Line 64 kbit/s Rx is inserted from

line SOH frames.

Radio 64 kbit/s Rx is inserted from

radio SOH frames.

Timeslot: Shows which timeslot in the SOH the

64 kbit/s Rx Channel occupy.



B4008 Rev. M 213


4.5.3 2 Mbit/s Wayside Channel

A 2 Mbit/s channel can be inserted in the SOH in either line-direction or radio-

direction. The 2 Mbit/s channel will occupy 33 bytes (32 bytes data + 1 byte

alignment information) of the SOH. Press the SOH Frame button to view

which bytes of the SOH that are used by the 2 Mbit/s Wayside Channel. The

2 Mbit/s channel uses the Rx and Tx connection at the front panel of the IDU.Rx is received data and Tx is sent data.

The 2 Mbit/s Wayside configuration sheet can be opened from the Configu-

ration context menu of theIDU node in the Explorer view. The sheet can also be

invoked by selecting theIDU node in the Explorer view and then selectingEdit

2 Mbit/s Wayside from theConfiguration menu.

Figure VII-42 2 Mbit/s Wayside Channel Configuration Sheet

Fields: Options: Description:Status Enabled Enables the Wayside Channel

Disabled Disables the Wayside Channel

Direction Choose the direction the Wayside Rx channel

should be extracted from.

Line The Wayside channel is extracted from line

SOH. When the rate is set to DS1, the Line

direction is not available.

Radio The Wayside channel is extracted from radio

SOH.



214 B4008 Rev. M

CityLink

Rate Choose the rate of the Wayside channel.

This field is only available when the NE

supports DS1 Wayside functionality. If not,

the rate is assumed to be E1.

E1 2 Mbit/s

DS1 1.5 Mbit/sCoding Choose the coding of the Wayside channel.

This field is only available when the NE

supports DS1 Wayside functionality. If not,

the coding is assumed to be of type HDB3.

HDB3 Only available for E1

AMI Only available for DS1

B8ZS Only available for DS1

Sensitivity This field is only available when the NE is

equipped with the DS3/E3 Extension Boardand the DS1 rate is selected

-30dB Only available for DS1

-36dB Only available for DS1

Cable Length This field is only available when the NE is

equipped with the DS3/E3 Extension Board

and the DS1 rate is selected

133-266 feet

266-399 feet

399-533 feet

533-655 feet

-7.5dB CSU

-15dB CSU

-22dB CSU

Buttons:

SOH frame Press this button to view which timeslots in the SOHthe Wayside channel occupies.



B4008 Rev. M 215


4.5.4 SOH X-Connect

Two 64kbit/s (one SOH timeslot) cross-connections can be set up. The

cross-connections bypass the SORP so that the SOH time-slots are sent

from the Line receive unit directly to the Radio transmit unit.

The SOH X-Connect configuration sheet can be opened from the Config-uration context menu of the IDU node in the Explorer view. The sheet can also

be invoked by selecting (highlighting) theIDU node in the Explorer view and

then selectingEdit X-Connect from theConfiguration menu.

Figure VII-43 SOH X-Connect Configuration Sheet


Enabled/Disabled Switches SOH X-Connect on/off

Line timeslot The time slot to bypass the SORP.

Radio timeslot The destination time slot.



216 B4008 Rev. M

CityLink


Enabled/Disabled Toggles Error Pulse Output On/Off

Source Only one sourceat a time.

FEC radio The output pin reflects the FEC on

the Viterbi asic.

B1 line The output pin reflects the B1 on

the Line Receive side of the SORP.

B2 line The output pin reflects the B2 on the

Line Receive side of the SORP.

B1 radio The output pin reflects the B1 on the

Radio Receive side of the SORP.B2 radio The output pin reflects the B2 on the

Radio Receive side of the SORP.

4.5.5 Error Pulse Output

For test purposes.

The SORP and Viterbi asics give error pulses when they recognize errors. The

number of error pulses per second is a measurement of the quality of the

received signals. These error pulses can be sent out on the ALM/AUX port.

The Error Pulse Output configuration sheet can be opened from the

Configuration context menu of the IDU node in the Explorer view. The sheet

can also be invoked by selecting the IDU node in the Explorer view and then

selecting Edit Error Pulse Output from the Configuration menu.

Figure VII-44 Error Pulse Output Configuration Sheet



B4008 Rev. M 217


4.5.6 Auxiliary Output Configuration

The auxiliary output function must be enabled in the Available Functions

property sheet (see Chapter 2.2, this Section) to use the function.

There are four configurable auxiliary output pins in the ALM/AUX port.

The pins are connected to a relay, which can either be controlled manually,

or triggered automatically on a user selectable set of alarms.The Auxiliary Output Configuration sheet can be opened from the



Explorer view and then selecting Edit Auxiliary Output from the

Configuration menu.

Figure VII-45 Auxiliary Output Configuration Sheet

Controls: Choices: Description:

Output control Manual Control Set the usage of the aux.output

radio buttons or pin. (This will be disabled if the

Alarm Trigger CityLink does not support

alarm triggers.)

Manual relay Closed or Open If the aux. output is set to

status radio manual control, these buttons

buttons will be enabled, and can be usedto manually control the state of

the relay.



218 B4008 Rev. M

CityLink


Equipment tree Displays and selects the alarms

available for alarm triggers.

This will be disabled if the aux.

output is set to manual control.

Alarm trigger list Displays the alarm triggersconfigured. This will be dis-

abled if the aux. output is set to

manual control.

Add alarm button Adds the currently selected

alarm in the equipment tree to

the alarm trigger list. If there is

no selection, or if the selected

tree node doesn’t correspond to

an alarm, nothing happens.Disabled if the output is on

manual control.

Remove Removes the currently selected

alarm button alarm from the alarm trigger list.

Disabled if the output is on

manual control.

Alarm triggered Closed or Open If the aux. output is set to alarm

radio buttons triggered control, these buttons

will be enabled, and can be used

to control the state of the relay

when the alarm conditions are

raised.

Buttons:

Get: Press this button to retrieve the current settings from the NE.


dialog box is opened).Set: Press this button to update the element with any changes made to

any of the Auxiliary Output pages in the dialog box.

Close: Closes the dialog box.

Help: Press this button to get help on the current property sheet. For help

on an item, click at the top of the dialog box, then click the item.



B4008 Rev. M 219


4.5.7 Diagnose

The Diagnose function retrieves data about memory, boot errors and warnings,

boot version and number of resets of the SU of the NE. PressGet to retrieve the

data from the NE. The diagnose tests are performed at IDU reset. (Note that the

Viterbi decoder and SORP1 are only tested at cold reset)

The Diagnose configuration sheet can be opened from the Configuration

context menu of the IDU node in the Explorer view. The sheet can also be

invoked by selecting (highlighting) the IDU node in the Explorer view and

then selecting Edit Diagnose from the Configuration menu.

Figure VII-46 Diagnose Configuration Sheet

Module Status Comments

CPLD OK/Not OK A write/read test sequence was performed

at last reset/startup.

RTC OK/Low bat/ A write/read test sequence was performed

Not running at last reset/startup.

LCD OK/Not OK A write/read test sequence was performed


DRAM OK/Not OK A write/read test sequence was performedat last reset/startup.

SRAM OK/Not OK A write/read test sequence was performed


Code FLASH OK/Not OK A write/read test sequence was performed


Boot FLASH OK/Not OK A write/read test sequence was performed


Viterbi Decoder OK/Not OK A write/read test sequence was performed

at last startup.

SORP OK/Not OK A write/read test sequence was performed

at last startup.



B4008 Rev. M 221



HBER 1.0·10-3 - 1.0·10-10 Error bit rate

A Major alarm is generated when the Viterbi

error rate exceeds the HBER threshold value.

AIS is inserted when the HBER thresholdvalue is exceeded.

LBER 1.0·10-3 - 1.0·10-11 Error bit rate

A Minor alarm is generated when the Viterbi

error rate exceeds the LBER threshold value.

EW 1.0·10-3 - 1.0·10-12 Error bit rate.

A Warning is generated when the Viterbi

error rate exceeds the Error Warning

threshold value.

Figure VII-48 BER Threshold Configuration Sheet

Internal proportions: HBER > LBER > EW

The BER Threshold configuration sheet can be opened from the Configu-

ration context menu of theRadio nodeunder the IDU node in the Explorer view.

The sheet can also be invoked by selecting (highlighting) the Radio node

under the IDU node in the Explorer view and then selecting Edit BER Threshold from theConfiguration menu.



222 B4008 Rev. M

CityLink

4.5.10 OSI Configuration

The OSI configuration has to be set to get OSI traffic on your LAN, routed

through the Nera network.

4.5.10.1 OSI Line Coding

Choose the scheme for the encoding of the binary data stream in the

communication channels. The two ends of a communications line must be

configured with the same Line Encoding in order to communicate!

Figure VII-49 OSI Configuration Sheet, Line Coding Tab


NI1: The line coding for the NI1 interface. Can be NRZ or NRZI.

NI2: The line coding for the NI2 interface. Can be NRZ or NRZI.

DCC Line: The line coding for the DCC Line interface.

Can be NRZ or NRZI.

DCC Radio: The line coding for the DCC Radio interface.

Can be NRZ or NRZI.



B4008 Rev. M 223


4.5.10.2 OSI Parameters

Configure the OSI parameters for the different communication channels.

To enable OSI for the different channels, do this at the appropriate

Communication ports configuration page. Link state protocol buffer size

apply to all channels.

Figure VII-50 OSI Configuration Sheet, Parameters Tab



224 B4008 Rev. M

CityLink

Fields: Subfield: Description:

NSAP Address Area ID Subnet address.

Host ID End system address.

End Selector Type of service. Always 01.

Link state Transmitted buffer length size of IS

protocol hello-packets.(512-1492 bytes)

buffer size

Parameters MTU size Maximum Transmission Unit size.

(512-1497 bytes)

Default Metric Cost of path.

LAPD Role: Client/Server role

The two ends of a communications line

must be configured with the opposite

roles in order to communicate!

OSI Enabled This control is checked if OSI is

enabled for the respective interface.

This is set in the NI or DCC Commu-

nication Ports Configuration pages



B4008 Rev. M 225


4.5.10.3 OSI Routing Table

This page shows the OSI Routing Table contained in the IDU. The list

shows Host Id and Metric for all entries in the table. To get an updated

Routing Table, press the Get Button.

Figure VII-51 OSI Configuration Sheet, Routing Table Tab


Host Id End system address.

Metric Cost of path.



226 B4008 Rev. M

CityLink

Figure VII-52 OSI Configuration Sheet, Interface Information Tab

4.5.10.4 OSI Interface Information

There will be one line in the table for each channel enabled for OSI.


Id Numbering of interfaces in the network

InterfaceName Network user

Media Type of media

Status Indication of connection status (Up or Down)MTU Size Maximum transmission unit size



228 B4008 Rev. M

CityLink

Fields: Buttons: Description:

ALS:

Enabled/Disabled Toggles ALS On/Off

Waiting Time (1.0 - 5.0 minutes ) Specifies waiting

time before the laser is turned on. If

section of operation is connected and

optical signal from far end is present,

laser will remain on, if not laser will

be turned off after 2 seconds.

Get Retrieves Laser Control settings

from the NE.

Set Sends Laser Control settings to the NE.

Restart (2 Seconds) Manually restart the laser for 2 seconds.

Restart (90 Seconds) Manually restart the laser for

90 seconds for testing purposes.

Manual

Control: (ALS disabled or not implemented)

On Manually turn the laser on.

Off Manually turn the laser off.

Status: Shows the status of the Laser Unit.



B4008 Rev. M 229


4.5.12 IDU Replace Unit Wizard

The Replace Unit Wizard simplifies the process of replacing an IDU. The

wizard copies configuration data from “old” IDU to the “new” IDU.

Note:

• The NEW program must be directly connected to the LCT port on theIDU (serial communication).

• The “old” NEs configuration data is copied to the “new” IDU,

including Element ID. Thus the addresses of the “new” IDU

become equal to the addresses of the “old” IDU.

• Available Functions data is not copied. The “new” IDU may have

other optional functions available than the “old” IDU.

The wizard describes each step in the replacement process.

Figure VII-54 The IDU Replace Unit Wizard



230 B4008 Rev. M

CityLink

4.6 Out Door Unit (ODU)

4.6.1 Type I ODU

4.6.1.1 Frequency Settings

The Duplex Distance between the Rx and Tx band is fixed. The user can set

the Tx frequency by clicking on the frequency slots. Since the duplexdistance is fixed the Rx frequency will be automatically set. The corre-

sponding Tx and Rx frequency must be set in the opposite NE.

Note! Dual Frequency - Single Polarisation (DF-SP) requires two chan-

nels in order to transmit 2xSTM-1. With this configuration, adjacent

channels can not be used.

NEW NMS/Configurator receives the frequency plan from the NE.

When no NE is connected (off-line), no frequency plan will be shown.

The output power is automatically muted when the frequency setting is

executed.

The Frequency configuration sheet can be opened from the Configura-

tion context menu of the ODU node in the Explorer view. The sheet can

also be invoked by selecting (highlighting) the ODU node in the Explorer

view and then selecting Edit Frequency from the Configurationmenu.

Figure VII-55 Frequency Configuration Sheet



B4008 Rev. M 231



Frequency Select the desired frequency plan. The frequency

plan plan must correspond to your transceiver.

Coding The coding function used in the modulator/

demodulator. These coding functions may beselectable depending on frequency plan:

TCM (Trellis coded modulation) andTCM + RS

(Trellis coded modulation and Reed Solomon).

Modulation The modulation scheme used with this frequency

plan

Data Rate The data rate(s) supported by this frequency plan.

The available data rates may also be dependent on

radio type, radio software version and coding.

Channel Spacing (MHz) The distance between the channels in this freq-uency plan

Duplex Distance (MHz) The distance between the TX and the RX carrier

frequency.

Innermost Spacing (MHz)The distance between the highest selectable freq-

quency in the lower half of the plan and the lowest

selectable frequency in the upper half og the plan.

TX Frequency (GHz) The used TX Carrier frequency

RX Frequency (GHz) The used RX Carrier frequency

TX (min) (GHz) TX Lower sideband frequency for this frequency

plan

TX (max) (GHz) TX Upper sideband frequency for this frequency

plan

RX (min) (GHz) RX Lower sideband frequency for this frequency

plan

RX (max) (GHz) RX Upper sideband frequency for this frequency

plan


1. Get the current settings from the Network element by pressing Get. (The

settings are automatically retrieved from the NE when the property-sheet

is opened)

2. Alter the settings by clicking the frequency band you want to transmit

your TX data. The RX frequency is automatically updated since the

duplex Distance is fixed.

3. Press Set to send the changes to the NE.



232 B4008 Rev. M

CityLink

4.6.1.2 ODU Transceiver - Power Configuration

The Transceiver Power Configuration sheet lets the user set some Output

Power settings, some RF Input warning thresholds and ATPC settings.

ATPC (Automatic Transceiver Power Control) is a function for effective-

ly reducing the interference probability in your network. The output power from the transceiver is automatic controlled. If the regulation loop for the

ATPC stops functioning, an alarm is generated. This alarm can be delayed.

The output power is automatically muted when the frequency setting is

executed.

The Power configuration sheet can be opened from the Configuration

context menu of the ODU node in the Explorer view. The sheet can also

be invoked by selecting (highlighting) the ODU node in the Explorer view

and then selecting Edit Power from the Configuration menu.

Figure VII-56 Power Configuration Sheet



B4008 Rev. M 233


Fields: Denomination: Description:

RF input level dBm The upper threshold value for when

warning, high to generate an RF input level

warning (Alarm no. 1504)

RF input level dBm The lower threshold value for when

warning, low to generate an RF input level

warning (Alarm no. 1504)

ATPC dBm Set the power level to use when an

alarm level ATPC alarm occurs.

ATPC dBm The wanted input level when ATPC

reference level is activated.

Mute Mutes the output power. No output

output power power is sent.

Maximum dBm Maximum output power for

output power transmitting

Manual dBm The output power level used whenoutput level ATPC is not activated

ATPC status ATPC Disabled/ Enabled

ATPC mode ATPC can operate in four different modes:

Automatic Regulation: The trans-

ceiver automatically regulates the

transmitter power

Minimum Output: A min. amount of power is used for transmitting.

Maximum Output: A max. amount of

power is used for transmitting.

Freeze Output Power: A fixed amount

of power is used for transmitting.

ATPC Seconds The ATPC alarm can be delayed from

alarm delay 1 to 15 seconds.



234 B4008 Rev. M

CityLink

Figure VII-57 ODU Production Data Configuration Sheet

4.6.1.3 ODU Production Data

The ODU production data property sheet shows the production serial

numbers and the production and test dates of the ODU. Only an adminis-

trator can change the settings.

The ODU Production Data configuration sheet can be opened from theConfiguration context menu of the ODU node in the Explorer view. The

sheet can also be invoked by selecting (highlighting) the ODU node in the


Configuration menu.


Article code: The article code

Serial no: The serial number.


Sales order: The purchase order.



FAT date: The date when the Factory Acceptance Test was

found to be satisfactory.SAT date: The date when the Site Acceptance Test was

found to be satisfactory.



236 B4008 Rev. M

CityLink

Fields:

Mute output power: When checked the output power is muted.

Maximum output level (dBm): The transmitter’s maximum output power.

Manual Transmit Output Power (MTPC): ATPC is disabled. Constant

manual output level is used.Automatic Transmit Output Power (ATPC): ATPC is enabled. Output

level is automatically adjusted using the specified ATPC settings.

Alarm Thresholds:

• RF-INPUT-WARNING, high (dBm): If the RF input level exceeds

this value the ”RF-INPUT-WARNING” alarm is raised.

• RF-INPUT-WARNING, low (dBm): If the RF input level goes

below this value the ”RF-INPUT-WARNING” alarm is raised.

MTPC:

• Manual output level (dBm): The output power used when ATPC isdisabled.

ATPC:

• Reference input level (dBm): The desired input level. If ATPC is

enabled on the transmitter across the hop, that transmitter will regulate

its output power such that the received input level at this receiver is

equal to the reference level.

• Default output level (dBm): The output power to be used if the ATPC

regulation loop fails. (The ”ATPC” alarm is raised).

• Alarm delay (s): The delay (in seconds) before the ATPC alarm is

raised after the ATPC regulation loop fails.


NE.



B4008 Rev. M 237



The Frequency property sheet displays the frequency settings for the

transceiver unit. Available frequency plans and their parameters are stored

in a table in the NEW-NMS database. If the wanted frequency plan cannot

be found in the combo box, please contact Nera for upgrading the database

table. When frequency data is retrieved from the NE, the data are matchedagainst frequency plans stored in your database system. If a match is found

the appropriate frequency plan is selected, otherwise a frequency plan can

be selected from the combo box.

To change the frequencies:

1. Select a frequency plan from the combo box.

2. Select a TX frequency by pressing a button in the frequency plan. The

RX frequency will be calculated from TX frequency and the duplex

distance.3. Send the new settings to the NE. (Press the Set button in the property

sheet). A message box will be displayed asking whether to apply the

contrary frequencies to the other side of the hop (if the remote NE is

present in NEW).




240 B4008 Rev. M

CityLink

Figure VII-61 DRO Tuning Procedure

T x T un ing

R x T un ing

4.6.2.3 DRO Tuning Procedure



B4008 Rev. M 241


4.6.2.3.1 Frequency Setting

Highlight the actual Transceiver unit to be tuned. Right click and choose

Configuration and Frequency.

Transceiver Unit Ch1

See Chapter 4.6.2.2 for setting of frequency.

Figure VII-62 Selecting in Explorer View the Transceiver to be tuned




242 B4008 Rev. M

CityLink

4.6.2.3.2 DRO Tuning

Highlight the actual Transceiver unit to be tuned. Right click and choose

Configuration andDRO Tuning

Tx tuning

Disabled

Rx tuning

Tx tuning

Select Tx tuning in the DRO Tuning Mode field. Press the Set button.

Figure VII-64 Selecting DRO tuning from the Explorer View

Figure VII-65 DRO Tuning Configuration Sheet



B4008 Rev. M 243


The red arrow indicates which way to adjust the DRO. In addition, the

Alarm LED on the front of the Transceiver will blink when the DRO must

be turned clockwise. If the Alarm LED is OFF, the DRO must be turned

counter-clockwise. When the Alarm LED is ON, the Synthesizer is in

lock. Press the Set button to update the window.

Figure VII-66 DRO Tuning Configuration Sheet, Tx tuning



244 B4008 Rev. M

CityLink

Rx Tuning

Disabled

Tx tuning

Rx tuning

Select Rx tuning in the DRO Tuning Mode field. Press the Set button.

Figure VII-67 DRO Tuning Configuration Sheet



246 B4008 Rev. M

CityLink

4.6.2.4 Production Data

The different boards/units contain some production information. This

information is displayed in the Production Data property sheet.


Article code: Uniquely identifies the type of board/unit.

Serial no.: The serial number of the board/unit.HW revision: The hardware revision.

Production date: When the production process was completed for

this board/unit.

Test date: When this product was tested by the factory test-

department.


NE.

Figure VII-69 Production Data Configuration Sheet



B4008 Rev. M 247


4.6.3 Type III ODU

4.6.3.1 RF Power

The XCVR Unit provides a set of RF power control functions:

• RF input alarm thresholds can be set such that an alarm is raised when

the input level exceeds the upper or lower limits.• ATPC (Automatic Transmitter Power Control) is a function for effec-

tively reducing the interference probability in the network. When ATPC

is enabled, the output power from the transmitter is automatically

controlled according the received input power on the other side of the

hop. The ”ATPC” alarm is generated if the ATPC regulation loop fails.

This alarm can be optionally delayed.

• If ATPC is not enabled, the transmitted output level can be set. The

transmitter can also be muted.

The RF Power property sheet is used to display/configure the RF Power

control settings.

Figure VII-70 Power Configuration Sheet



248 B4008 Rev. M

CityLink

Fields:

Mute output power: When checked the output power is muted.

Maximum output level (dBm): The transmitter’s maximum output

power.

Manual Transmit Output Power (MTPC): ATPC is disabled. Constantmanual output level is used.

Automatic Transmit Output Power (ATPC): ATPC is enabled. Output

level is automatically adjusted using the specified ATPC settings.

Alarm Thresholds:

• RF-INPUT-WARNING, high (dBm): If the RF input level exceeds

this value the ”RF-INPUT-WARNING” alarm is raised.

• RF-INPUT-WARNING, low (dBm): If the RF input level goes

below this value the ”RF-INPUT-WARNING” alarm is raised.

MTPC:• Manual output level (dBm): The output power used when ATPC is

disabled.

ATPC:

• Reference input level (dBm): The desired input level. If ATPC is

enabled on the transmitter across the hop, that transmitter will regulate

its output power such that the received input level at this receiver is

equal to the reference level.

• Default output level (dBm): The output power to be used if the ATPC

regulation loop fails. (The ”ATPC” alarm is raised).

• Alarm delay (s): The delay (in seconds) before the ATPC alarm is

raised after the ATPC regulation loop fails.


NE.



B4008 Rev. M 249



The Frequency property sheet displays the frequency settings for the

transceiver unit. Available frequency plans and their parameters are stored

in a table in the NEW-NMS database. If the wanted frequency plan cannot

be found in the combo box, please contact Nera for upgrading the database

table. When frequency data is retrieved from the NE, the data are matchedagainst frequency plans stored in your database system. If a match is found

the appropriate frequency plan is selected, otherwise a frequency plan can

be selected from the combo box.

To change the frequencies:

1. Select a frequency plan from the combo box.

2. Select a TX frequency by pressing a button in the frequency plan. The

RX frequency will be calculated from TX frequency and the duplex

distance.3. Send the new settings to the NE. (Press the Set button in the property

sheet). A message box will be displayed asking whether to apply the

contrary frequencies to the other side of the hop (if the remote NE is

present in NEW).




250 B4008 Rev. M

CityLink

Fields:

Frequency Plan:

• Selected plan: The currently selected frequency plan. The graphical

presentation of the plan contains channel buttons that can be used to set

the TX and RX frequencies for the selected channel in the list.• Modulation: modulation method: 32TCM or 128 TCM.

• Channel spacing: The distance in MHz between two consecutive

channels.

• Data rate: STM-1 or STM-0.

Current Setting:

• TX frequency (GHz): The Transmitter frequency.

• RX frequency (GHz): The Receiver frequency.

Transceiver limits: The frequency band limits of the transceiver.

Status: Frequency status:• OK: Frequency settings are OK.

• Frequency shifting: The frequencies are changed on both sides of the

hop. If no connection is established within 10 seconds the frequencies

will be reverted.


NE.



B4008 Rev. M 251


4.6.3.3 Production Data

The ODU production data property sheet shows the production serial

numbers and the production and test dates of the ODU. Only an adminis-

trator can change the settings.

The ODU Production Data configuration sheet can be opened from theConfiguration context menu of the ODU node in the Explorer view. The

sheet can also be invoked by selecting (highlighting) the ODU node in the


Configuration menu.

Figure VII-72 Production Data Configuration Sheet


Article code: The article code

Serial no: The serial number.


Sales order: The purchase order.



FAT date: The date when the Factory Acceptance Test was

found to be satisfactory.SAT date: The date when the Site Acceptance Test was

found to be satisfactory.



252 B4008 Rev. M

CityLink

Figure VII-73 Antenna Data Configuration Sheet

4.6.4 Antenna Data

This sheet shows some main characteristics of the antenna. Only the

Antenna code can be altered. The antenna data are stored in a database file.

The Antenna Data configuration sheet can be opened from the Configu-

ration context menu of the Antenna node in the Explorer view. The sheetcan also be invoked by selecting (highlighting) the Antenna node in the

Explorer view and then selecting Edit Antenna from the Configura-

tion menu.

Fields: Description:Antenna code The antenna code. Unique code for each antenna type.

Gain The antenna gain (dB). Gain is a measurement of the

antenna's ability to transform electrical signals to

electromagnetic waves.

Diameter The physical antenna diameter. [meter]

Polarization The polarization direction of the antenna.

Front/Back ratio Front/Back Ratio. Ratio between the gain in forward

direction and the gain in backward direction.

Frequency range The frequency range where the antenna can be expected

to operate successfully.



256 B4008 Rev. M

CityLink

5.1.1.1 VC-12 Selector

This dialog is used to select a specific VC-12 from the 63 available in the

STM-1 payload. In addition to the VC-12 number, the direction from

which the specific VC-12 is routed to/from is also specified.

This dialog will be launched immediately after the user has checked anitem in the Drop or Continue dialog.


VC-12 # The VC-12 number. It must be in the interval [1,63].

K The first of the three numbers in the KLM number-

ing scheme. The number must be in the interval [1,3].

Note that the user can either enter the K number directly or use the up/down buttons to traverse the

number range.

L The second of the three numbers in the KLM num-

bering scheme. The number must be in the interval

[1,7]. Note that the user can either enter the L

number directly or use the up/down buttons to traverse

the number range.

M The third of the three numbers in the KLM number-

ing scheme. The number must be in the interval [1,3].

Note that the user can either enter the M number

directly or use the up/down buttons to traverse the

number range.

Drop From Line If selected, the VC-12 will be routed to/from the line

interface of the NE.

Drop From Radio If selected, the VC-12 will be routed to/from the

radio interface of the NE.

Figure VII-76 The VC-12 Selector Dialog Box



B4008 Rev. M 257


Sub Network SNCP performs path protection switching (called

Connection dedicated protection) which manages all traffics by

Protection - SNCP a path. Working traffic is transmitted in one direc-

tion, and protection traffic in opposite direction

around the ring, and traffic is selected at each end of

the path. So, SNCP supports multiple rings, andoffers suitable solution for access and metro net-

work where hub node terminates most various

traffics. SNCP can also transmit signal to only one

direction, west or east, and the products can be used

as 1+0 Linear ADM mode as well as SNCP mode.

Buttons:

OK: Click this button to close the dialog and apply the setting.

Cancel: Click this button to close the dialog without applying the setting.



258 B4008 Rev. M

CityLink

5.1.2 PRBS Test - Check

The PRBS Test - Check sheet is used to set up which of the dropped

2Mbit/s tributaries that shall check a given PRBS. Only one 2Mbit/s

tributary can perform this test at the time.

The PRBS Test - Check configuration sheet can be opened from theConfiguration context menu of the 21x2 Extension board node in the


the 21x2 Extension board node in the Explorer view and then selecting

Edit PRBS Test from the Configuration menu.

Figure VII-77 The PRBS Test Check Configuration Sheet



B4008 Rev. M 259



2Mbit/s The physical port number on the 21x2Mbit/s tributary board.

Direction Used to set from which Direction the tributary board shall

check PRBS. To change the setting, the user must double-

click the Direction cell in question. When this happens, acombobox will be displayed in the cell and the user can

select a new setting for the cell.

Inverted If this checkbox is checked, it will be assumed that the

received PRBS is inverted. If not checked, it’s assumed to

not be inverted.

Clear If this checkbox is checked the Count cell will be cleared

when Set button is clicked.

Check Only one tributary can be set to check PRBS at the time. This

means that only one item in the list above can be active at thesame time. In the figure above this is item-1. Item-2 through

item-8 aren’t active. If e.g. the radio button in item-1 in the

figure is clicked (the one that is active), it will be cleared. In

this case none of the tributaries will check PRBS.

Count This cell will contain the number of error pulses. It’s a 2^16

bits wrap-around counter. If the Status cell is Sync Loss,

this counter will not count but instead be set to «—». If the

Status cell is No Sync Loss, this counter will count errors.

Status The status of the counter.



from the list!



B4008 Rev. M 261



2Mbit/s The physical port number on the 21x2Mbit/s

tributary board.

Direction Used to set in which Direction the tributary

board shall insert a PRBS. To change the settingthe user must double click the Direction cell in

question. When this happens, a combobox will

be displayed in the cell and the user can select a

new setting for the cell. Legal values are:

• 2Mbit/s

• STM-1

• 2Mbit/s & STM-1

• Both off

Insert If this checkbox is checked a PRBS will beinserted in the direction(s) specified by

Direction.

Insert inverted PRBS If this checkbox is checked all checked tribu-

taries in the list will be inserted inverted PRBS.

If not checked it’s assumed to not be inverted.



from the list!



262 B4008 Rev. M

CityLink

5.1.4 Production Data - 21x2Mbit/s Extension board

(2NCS635A)

Production data for the 21x2Mbit/s extension board, displayed on a separate

page in theProduction Data configuration sheet. Only an administrator can

change the settings.

The Production Data configuration sheet can be opened from the Con-

figuration context menu of the IDU- or Switch node in the Explorer view.

The sheet can also be invoked by selecting (highlighting) the IDU- or

Switch node in the Explorer view and then selecting Edit Production

Data from the Configuration menu. Then the production data is located

under the Tab named 21x2Mbit/s Extension Board.

Fields: Description:Article Code The Article Code of the card/unit.

Serial no. The Serial number of the card/unit.

HW revision Hardware revision of the card/unit.

Production date The date when the article was produced.

Test date The date when the article was tested.



B4008 Rev. M 263


5.2 DS3/E3 Extension Board

5.2.1 DS3/E3 Configuration

The DS3/E3 functionality allows the operator to connect two Virtual Contain-

ers (VC) in different ports. The connections are identified by using the

background colour of the ports together with the KLMaddress of the virtual

container. The background colour of a virtual container identifies the source

port, while the KLM address identifies the source address.

As an example consider the marked VCs in Figure VII-79. The VC on the Line

Port is connected with the VC having a KLM address of 1,2,1 on the Radio

Port. While the VC on the Radio Port is connected with the VC having a KLM

address of 1,1,1 on the Line Port.

SNCP functionality is available on the DS3/E3 Port and is identified with asplit cell.

Traffic Looping is achieved by connecting VCs on the same port and is only

available for the line - and radio port. The DS3/E3 port does not support traffic

looping, but does however support test looping. DS3/E3 looping is only

available on the connected when the port has been configured to add/drop

traffic.

The DS3/E3 Configuration sheet can be opened from the Configurationcontext menu of theDS3/E3 Extension Board node in the Explorer view. The

sheet can also be invoked by selecting (highlighting) theDS3/E3 Extension

Board node in the Explorer view and then selecting Edit DS3/E3 from the

Configuration menu .



264 B4008 Rev. M

CityLink

Buttons:

SNCP: Press this button to establish an SNCP connection. The SNCP

functionality will apply to the same virtual container on all

ports. SNCP is available on the DS3/E3 Port.

Source: To establish a connection, select a virtual container from one

of the ports. Press this button to set the selected container as

the source.

Destination: Select a virtual container from one of the ports and press this

button to set the selected container as the destination.

Disconnect: Select a virtual container which already has an establishedconnection. Press this button to remove the connection.

Cancel: Press this button to undo the current operation.

Get: Press this button to retrieve the current settings from the

NE. (The settings are automatically retrieved from the

NE when the dialog box is opened).

Set: Press this button to send the settings to the NE.


Help: Press this button to get help on the current property sheet. For

help on an item, click at the top of the dialog box, then click

the item.

Figure VII-79 DS3/E3 Configuration Sheet



B4008 Rev. M 265


5.2.2 DS3/E3 Frame Structure Configuration

The operator may configure the frame structure on the three ports. Each port

consists of three TUG-3’s ( SDH Multiplex Structure). Each TUG-3 contains

either a VC-3 structure or a VC-12 structure. The virtual containers on the

ports are identified using KLM notation:

Figure VII-80 Virtual Containers



266 B4008 Rev. M

CityLink

Figure VII-81 DS3/E3 Frame Structure Configuration Sheet

Buttons:

VC-3: Sets the current structure to VC-3.VC-12: Sets the current structure to VC-12.

Get: Press this button to retrieve the current settings from the

NE. (The settings are automatically retrieved from the

NE when the dialog box is opened).

Set: Press this button to send the settings to the NE.


Help: Press this button to get help on the current property sheet. For

help on an item, click at the top of the dialog box, then click

the item.SDH: This button indicates that the transmission standard is set to

SDH.

SONET: This button indicates that the transmission standard is set to

SONET.



B4008 Rev. M 267


5.3 ADM STM-1 Extension Board (X-Connect)

5.3.1 X-Connect Frame Structure Configuration

The operator may configure the frame structure on the three ports. For more

info, please refer to Chapter 5.2.2 (this Section)

The Frame Structure Configuration property page is available from the

Transmission Configuration property sheet. Select “Enable X-Connect”

from the “Termination Enabling” combo box in the “Termination and SETS”

property page. The Transmission Configuration property sheet can be

opened from the Configuration context menu of thetransmission node in the

Explorer view. The sheet can also be invoked by selecting (highlighting) the

transmission node in the Explorer view and then selecting Edit Transmis-

sion Configuration from theConfiguration menu .

Figure VII-82 Frame Structure Configuration Sheet

Buttons:

VC-3: Sets the current structure to VC-3.

VC-12: Sets the current structure to VC-12.



268 B4008 Rev. M

CityLink

Figure VII-83 X-Connect Frame Structure Configuration Sheet

5.3.2 X-Connect Configuration

The X-connect functionality allows the operator to connect two Virtual

Containers (VC) in different ports. The connections are identified by using

the background colour of the ports together with the KLM address of the

virtual container. The background colour of a VC identifies the source port,

while the KLM address identifies the source address.

As an example consider the marked VCs in the figure below. The VC on the

Line Port is X-connected with the virtual container having a KLM address

of 1,2,1 on the Radio Port. While the VC on the Radio Port is X-connected

with the VC having a KLM address of 1,1,1 on the Line Port.

SNCP functionality is available on the Line Port and is identified with a split

cell.

Looping is achieved by connecting VCs on the same port (Traffic Looping).

The X-ConnectConfiguration sheet can be opened from the Configuration

context menu of theX-Connect Extension Board node in the Explorer view.

The sheet can also be invoked by selecting (highlighting) the X-Connect

Extension Board node in the Explorer view and then selecting Edit X-

Connect from theConfiguration menu .



B4008 Rev. M 269


Buttons:

SNCP: Press this button to establish an SNCP connection. The SNCP

functionality will apply to the same virtual container on all

ports. SNCP is available on the Line Port.

Source: To establish a connection, select a virtual container from one

of the ports. Press this button to set the selected container asthe source.

Destination: Select a virtual container from one of the ports and press this

button to set the selected container as the destination.

Disconnect: Select a virtual container which already has an established

connection. Press this button to remove the connection.

Cancel: Press this button to undo the current operation.



270 B4008 Rev. M

CityLink

Figure VII-84 Hot Standby Explorer view

6.0 Hot Standby

6.1 General

A CityLink Hot Standby system consists of two InDoor Units connected to

an IDU Switch and two OutDoor Units connected to the a HSB branching

unit. The IDU switch performs switching in the Rx direction, while the branching unit has an RF-switch in the Tx direction.

6.1.1 Functionality

The IDU switch will perform most of the normal tasks of an IDU, with the two

IDUs maintaining modem functionality. Thus, configuration of line inputs,

wayside channels etc will be handled on the switch, while modem-specific

functionality (e.g Viterbi error pulses) is found on the IDU. Some function-

ality, like auxiliary outputs, are found in both places.



B4008 Rev. M 271


6.1.2 Element ID

The CityLink Element ID property sheet shows some main information about

the Network Element like name, type, serial number and different addresses.

The enabled fields can be altered by users with proper user privileges.

The Element ID configuration sheet can be opened from the Configurationcontext menu of the Element node in the Explorer view. The sheet can also

be invoked by selecting (highlighting) the Element node in the Explorer view

and then selecting Edit Element ID from the Configuration menu.

Figure VII-85 Element ID Configuration Sheet



272 B4008 Rev. M

CityLink


Serial number: The serial number of the NE. (Not editable)

NE type: The type of NE. (Not editable)

Name: The name of the NE (max. 32 characters)

Section address: The section address of the NE. (1-254)NE address: The NE address (1-128). Used for identification of

NEs within a section.

MAC address: The Media Access Control address of the NE.

Used for OSI-Management. (Not editable)

NSAP address: The Network Service Access Point address of the NE.

Used for OSI-Management.

IP address The Internet Protocol address of the NE.

1+1 Hot Standby: Select this option in order to set up a hot standby

element. A list of choices are displayed in the droplist;Standard,SD Combiner (Space Diversity Combiner),

SD Hybrid (Space Diversity Hybrid) and

Dual Antenna.

1+1 Freq. Diversity: Select this option in order to set up a frequency

diversity element. A list of choices are displayed in the

droplist; Standard, SD Combiner (Space Diversity

Combiner) andSD Hybrid (Space Diversity Hybrid)


1 First, get the current settings from the NE by pressing Get.


property-sheet is opened.)





B4008 Rev. M 273


Figure VII-86 HSB Looping Configuration Sheet

6.1.2.1 HSB Main Looping


context menu of theEquipment node in the Explorer view. Press the Main tab

to view/change the Main looping settings. The sheet can also be invoked

by selecting (highlighting) theEquipment node in the Explorer view and then

selectingEdit Looping from the Configuration menu.

6.1.2 Looping Configuration

When opening the Looping Sheet on a HSB NE, the pages for main, wayside

and 64Kbit looping will apply for both IDUs. If a loop is set on the IDU and

the system switches, the signal will still be looped.



274 B4008 Rev. M

CityLink

Fields:




Blue: The status of the loop is unknown. Loop informa-tion has not been retrieved from the NE, or a loop message

has just been sent to the NE and the GUI is waiting for a

response from the NE. (The loop settings have not been

confirmed by the NE). Note that the loop cannot be toggled

when the status is unknown.

Black: The loop is off (inactive)

Red: The loop is on (active)

Loops will be Displays the time of which all main traffic loops in the NE

automatically will be cleared. This time is set by the user when activatingcleared after: a loop.

The different main traffic loops

(from left to right in the respective blocks in Figure 70):

• 4S. SORP LT output to LR input loop, far-end (IDU Switch)

• 1S. SORP LR output to LT input loop, near-end (IDU Switch)

• 12S. SORP RT output to RR input loop, near-end (IDU Switch)

• 14A. IF loop, near-end (IDU A)• 15A. IF loop, near-end (ODU A)

• 16A. RF loop, near-end (ODU A)

• 14B. IF loop, near-end (IDU B)

• 15B. IF loop, near-end (ODU B)

• 16B. RF loop, near-end (ODU B)

Buttons:


Help: Press this button to get help on the current property sheet page. For


6.1.2.2 HSB 64Kbit/s Looping


6.1.2.3 HSB Wayside Looping




B4008 Rev. M 277


Automatic Switch Mode

The IDU switch checks the state of both channel A and channel B regularly.

This task decides whether an Rx switch is needed or not. Similarly, the Tx

switching is controlled by the ODU. For the Tx switching to work, the

connected IDU signals the ODU when at least one of the switching criteria

are present on the IDU.

In automatic switch mode the following rule constrain switching:

A channel switch is performed if, and only if, the channel switched to, has

no switch conditions true.

On IDU A and IDU B, a dedicated task is continuously checking whether the

Rx or Tx switch criteria status has changed, and if so, notifies the IDU switch

and ODU about the change.

Currently, bi-directional switching is not implemented in automatic mode.

Switching algorithm

The following algorithm is applied in automatic switching mode:

Compute the total severity factor of each branch (SA, S

B) using the following

formula:

SCenabled1is 1 if the switching criteria “RF Input Alarm” is enabled (checked),

else it is 0. SCactive1 is 1 if the alarm/category “RF Input alarm” is active

(present) on the element, else it is 0.

If SA = S

B, switch to the preferred branch (The preferred branch is set in the

Hot Standby Config page)

If SA > SB, switch to SB if branch A is active.If S

B > S

A, switch to S

A if branch B is active.

Manual Switch Mode

In manual switch mode, bi-directional switching is performed only as a result

of a Q1 message from external management software (e.g. NEW-NMS).

Currently, unidirectional switching is not implemented in manual mode.



278 B4008 Rev. M

CityLink

6.1.4 Reconfiguring a Hot Standby IDU for

use in 1+0 Configuration

An IDU that has been used in a HSB configuration will continue to be

configured as a HSB element until explicitly reconfigured. To do this, first

disconnect the IDU from the switch. Then use NEW-NMS to connect to

the element with a serial cable. NEW-NMS’ explorer view should nowdisplay an equipment tree with a single node. Bring up the Element ID

dialog from the Configuration menu, and disable the Hot Standby check-

box. When the element is next power cycled, it will start up in 1+0 configu-

ration. This can be verified with the Element ID dialog.

6.1.5 Reconfiguring a 1+0 IDU for

use in Hot StandBy Configuration

If the IDU used in a 1+0 is to be prepared for an IDU in a HSB system, it isvery important to do the following procedure :

1.Connect the HSB cable between the IDUs and the switch

2.Power up the HSB IDU

3.Power up the IDU A and IDU B

The IDUs will now be automatically reconfigured as IDUs used in a HSB

system.

WARNING!

If the Y-cable connectors marked with IDU A and IDU B are

swapped, the IDUs must always be rebooted after this opera-

tion.



B4008 Rev. M 279

Fast Ethernet Configuration

CityLink Fast EthernetConfiguration

SECTION VIII



280 B4008 Rev. M

CityLink

Login as admin with the password; adminpasswd

Hyperterminal & Telnet

1.0 Hyperterminal & Telnet Commands• First time configuration with hyper-terminal to IDU's LCT-

port.

– Settings on com port; 9600, 8, 1, none.

– Terminal emulation; VT100.

• Normal operation via IP.

– Telnet session to IP-address on management port or one of the four

ethernet port’s.

Figure VIII-1 Starting up and logging in

Note!

NEW-NMS' security system has initially one user account:User ID: adminPassword: adminpasswd

It is strongly recommended to change this password!



B4008 Rev. M 281


2.1 How to get this link alive, parameters

• Enable IP as described in Chapter 4.8.1 (this Section). Enable IP on

one of the four traffic port’s and do settings from NEW-NMS.

– Frequency on both elements must match (Tx to Rx).

– Maximum output power.

– Tune antennas for maximum Rx-levels.

• Verify that transmission is OK over the hop.

– Enable and test on a 2Mb/s or connect with computers on the LAN.

L A N 1

L A N 2

L A N 3

L A N 4

C i t y L i n k I D U

Fas tE the rne tTr ibutaryModu le

2 (1.5) M b/s c i rcu i t 1 - 4

L A N 1

L A N 2

L A N 3

L A N 4

C i t y L i n k I D U

Fas tE the rne tTr ibutaryModu le

2 (1.5) Mb /s c i rcu i t 1 - 4

EthernetExtension

Board(EEB)

EthernetExtension

Board(EEB)

2.2 Testing

• How to verify transmission quality and capacity ?

– One way to do this is to set up two computers and do a file transfer

(FTP) between them over the hop.

One PC working as FTP-server and one as FTP-client, check the

time for transfer of the file and calculate throughput.

Do not have any HUBs connected during this test.

– Stability of the equipment and hop will be easiest monitored on

BER test with pattern-generator on a 2Mb/s.

2.0 How to get this link aliveWhere to start

– Status?

– Do we want a IP connection to the IDU? If you have NEW-NMS, then

the answer is yes.Enable IP one of the four traffic port’s and do all settings from

NEW-NMS.

Figure VIII-2 Radio Connection



282 B4008 Rev. M

CityLink

3.0 Top Level Commands

After logon you should have this text on your screen;

Welcome to CityLink.

Copyright (c) Nera ASA.CityLink>

Then type help and press enter:

Welcome to CityLink.

Copyright (c) Nera ASA.

CityLink> help

Help:

The following commands are available:

Command Function

alarms lists alarms

cls clear screen

coldstart shutdown the system and make a cold start of the system

enter enter submenu

env list environment variables

exit exit submenu

gettime display system timezone, time and date

help get help on commands

list list available commands

ping ping the specified host

quit quit shell

reboot shutdown the system and reboot

settime set system timezone, time and date

tracert trace route to target

Use "help <command>" to get help on specific command.

Example for usage of "Help":

CityLink> help gettime

gettime: display system timezone, time and date

Usage: gettime

CityLink>



B4008 Rev. M 283


3.1 Top Level Commands, Example

CityLink (radio)> alarms

Active alarms:

TIME ID NAME CLASS STATE

Modem.

2001.11.19 11.04.50 1104 E-WARNING WARNING Raised 2001.11.19 11.04.50 1103 LBER MINOR Raised

2001.11.19 11.04.50 1102 HBER MAJOR Raised

Baseband

2001.11.19.11.04.50 32808 LOS_RR MAJOR Raised

2001.11.19.11.04.50 32809 LOF_RR MAJOR Raised

2001.11.19.11.04.50 32811 MS-AIS_INSERT_RR MAJOR Raised

EEB

2001.11.19.11.04.50 32785 ETHERNET_PORT_2 INFO Raised



PerfManager

2001.11.19.11.15.01 3000 G826-15MIN-B1 WARNING Raised

2001.11.20.00.00.01 3003 G826-24HOUR-B1 WARNING Raised

CLIServer 2001.11.20.14.35.20 32782 CONSOLE_USER_LOGGED_IN INFO Raised



284 B4008 Rev. M

CityLink

4.0 Submenu CommandsThe command structure is top level commands and submenu commands.

Top level commands are also available at submenu levels.

The following submenus are available by typing enter and then submenu:

4.1 EEB Submenu

Configuration of Ethernet module

– Enable LAN ports – Select the important LAN port

– Enable 2Mbit/s ports

Submenu commands:Submenu Function Security

Level

eeb monitor and control of EEB passive

baseband perform baseband module commands passive

modem perform modem module commands passive

radio monitor and control of ODU passive

su monitor and control of SU passive

security perform security administration passive

perform monitor and control of Performance data passive

config Lists and modifies configuration settings passive

test perform test function commands passive

fault Query and manipulate alarms and alarm settings active

q1module Lists and modifies q1 and nnp protocol settings master

EEB submenu commands:

Command Function

autopartition enable / disable autopartition

eebstatus show GT-48350 link/partition status

get2mbport get 2MBit E1/T1 port state (from SW Version R1C0this command has been replaced by gettribport)

getethmode get Ethernet ports speed and duplex mode

gettribmode get tributary E1/T1 ports mode

gettribport get tributary E1/T1 port state

getethport get Ethernet port state

getflowctrl get flow control for Ethernet port

listportmib list the MIB-statistics of a port

selectpriport select priority Ethernet port

set2mbport set 2MBit E1/T1 port state (from SW Version R1C0this command has been replaced by settribport)



B4008 Rev. M 285


4.2 Baseband Submenu

Configuration of IDU

– Enable 2Mbit/s Wayside

– Enable 64kbit/s channels

Baseband submenu commands:

Command Function

get64kg703 get g703 enable/disable

get64kv11 get v11 enable/disable

getlaser get current laser state

getwayside get wayside enable/disable

resetbaseband reset eeb module

set64kg703 set g703 enable/disable

set64kv11 set v11 enable/disablesetlaser sets the laser state

setwayside set wayside enable/disable

startlaser starts the laser

If Flow control is set this will cause a feedback to the “sender” if the port

have to much to do. In this case you will avoid lost or dumped packages and

you may see an improvement of the throughput if “sender” support flow

control!

setethmode set Ethernet port speed and duplex mode

settribmode set tributary E1/T1 ports mode

settribport set tributary E1/T1 port state

setethport set Ethernet port state



286 B4008 Rev. M

CityLink

4.3 Modem Submenu (part of IDU)

validberlevels

– BER = Bit Error Ratio, Number of errored bit’s divided on total number

of bits.

High BER = 1x10-3

Low BER = 1x10-6

Early Warning (BER) = 1x10-9

Settings of FIR and SERF index are set from factory! Do not change them!

Contact Nera to get FIR and SERF index if necessary.

Modem submenu commands

Command Function

getberlevels get HBER, LBER and ER levels

getfirindex get current fir tap index

getserfindex get current serf set index

resetmodem reset modem

setberlevels set HBER, LBER and EW levelssetfirindex set current fir tap index

setserfindex set current serf set index

tempcomp get temperature compensation data

validberlevels show valid HBER, LBER and ER levels

Remember to use NEW-NMS or NEW-Configurator when changing

frequency plan used on the system, because then these setting will be

correct.



B4008 Rev. M 287


4.4 Radio Submenu (part of ODU)

Configuration of ODU

– Set frequency, normally done during installation. However, this will be

necessary to set for spare parts.

Radio submenu commands:Command Function Usage Security

Level

downloadodusw transfer ODU SW No parameters master

from IDU to ODU

drotuning get/set ODU DRO drotuning [disable | tx | rx] master

tuning mode/status

getatpc get Automatic- No parameters passive

PowerControl settings

getfrequency get tx and No parameters passive

rx frequency

getmutestate get radio mute state No parameters passive

getrfpower get rf output No parameters passive

and input power

getrfwarning get RfInputLevel- No parameters passive

Warning up and

down

radiostatus display all No parameters passive

radio settings

reloadfreq transfer current No parameters master frequency settings

to ODU

setatpc set Automatic- setatpc <state | rxref | almoutlevel | almdelay> master

PowerControl state: state <enable | disable>

functions rxref: rxref <level in dBm>

almoutlevel: almoutlevel <level in dBm>

almdelay: almdelay <delay in seconds>

setfrequency set tx and setfrequency <txfreq> <rxfreq> master

rx frequency

setmutestate set radio mute state setmutestate < on | off> master setrfpower set rf output power setrfpower <‘OutputPower in dBm’> master

setrfwarning set RfInputLevel- inputwarning <WarningLevelUp> master

Warning up and <WarningLevelDown>

down



288 B4008 Rev. M

CityLink

4.4.2 Radio Commands, Example of Error Message

CityLink (radio)> setfrequency 22190000 23198000

Frequency out of range!

TxFrequency: 23198000 kHz

RxFrequency: 22190000 kHz

TxFreq.Min : 23086000 kHz

TxFreq.Max : 23534000 kHz

RxFreq.Min : 22078000 kHz

RxFreq.Max : 22526000 kHz

DuplexDistance: 1008000 kHz

CityLink (radio)> setfrequency 23198000 22190000

4.4.1 Radio Status, Example

CityLink (radio)> radiostatus

Radio Configuration

ODU:RF input = -113.00 dBm

ODU:RF output = 14.00 dBm

ODU:+48V = 48.00 VRadio Muted = 0

Loop status = 0

Loop capability = 3

Transceiver S/N = 96

Radio Type = 1

Transceiver Type = 10

Boot Code Version = 1A0

App. Code Version = 4D2

App. Code Date = 2001-12-04 17:04:55

Radio Alarms.

Alarm : 1502 LOS_RF_INPUT

Alarm : 1504 RF_INPUT_WARNING

Tx Frequency = 23198000 kHz

Rx Frequency = 22190000 kHz

Last FrqShift = Ok Tx Frequency Min = 23086000 kHz

Tx Frequency Max = 23534000 kHz

Rx Frequency Min = 22078000 kHz

Rx Frequency Max = 22526000 kHz

Duplex Distance = 1008000 kHz

Rf Output Power = 15 dBm

Rf Output Power Max = 18 dBm

Rf Output Power Min = 8 dBm

Rf Input Warning Low = -60 dBm

Rf Input Warning Up = -35 dBmATPC state = 0

ATPC Rx Ref Level = -10 dBm

ATPC alm Out Level = 15 dBm

ATPC alarm Delay = 12 sec.



B4008 Rev. M 289


4.5 SU Submenu (part of IDU)

Important issues for maintenance and troubleshooting could be to inves-

tigate RF-input level and DC-level in ODU.

SU submenu commands:

Command Functiongetanaloge list analogue sensor measurements

getauxinput list aux port inputs signals and configuartion

getauxoutput list aux port outputs signals and configuration

getfan get fan status

setauxinput configure aux port inputs signals

setauxoutput configure aux port outputs signals

4.6 Security SubmenuIt is important to limit the valid range of IP-addresses to reduce possibility

of “hacking”. It is also recommended to customize the SNMP password

(community strings), also in NEW-NMS.

Security submenu commands:

Command Function

adduser make a new user account

changename change «current user» description namechangepwd change «current user» password

changesnmppwd change SNMP password (community string)

deleteuser delete user account

getiprange list secure IP ranges

getlog list security log

getsnmppwd list SNMP password (community strings)

getuser list users

resetlog resetlog deletes all entries in security log

resetsecurity reset security to factory settingssetiprange set secure IP range

setusername set User description name

setuserpwd set User password

who list users logged on



290 B4008 Rev. M

CityLink

4.7 Performance Submenu

The Performance submenu shows the quality on your received signal from

opposite Citylink.

Perform submenu commands:

Command Function

getfec list FEC counter

getg826 list G.826 performance values

getpulses list error pulses

getthreshold list G.826 Thresholds

performstatus list all performance parameters available

resetfec reset FEC counter

resetg826 reset G.826 performance values

resetpulses reset error pulses

setthreshold set G.826 Thresholds

4.8 Configuration Submenu

Configuration of the CL Element

– Set system type.

– Set section and station address, name etc...

– Important to execute command "setinterface" in order to enable

management via IP.

Config submenu commands:

Command Function

addroute Adds routes to the routing table

authenticate Authenticates access keys to enable licensed functionallity

deleteroute Deletes routes from the routing table

eebni Sets or gets state on EEB network interface

getsysmode Gets the system operation mode

inventory Prints inventory datalistnetconfig Lists the network configuration

listroute Lists the routing table

listsysconfig Lists current system configuration

setantennatype Sets the antennatype

setgateway Sets the default gateway

setinterface Sets the IP address and netmask of an interface

setsectionaddr Sets the section address

setstationaddr Sets the station address

setstationname Sets the station namesetsysconfig Sets system configuration

setsysmode Sets the system operation mode



B4008 Rev. M 291


4.9 Test & Fault Submenu

Test submenu commands:

Command Functiongetloop get current looping state

setloop toggle looping state on/off

Fault submenu commands:

Command Function

alarmlog lists alarmlog entries

clearalarm clears an alarm

maskalarm masks an alarm

raisealarm raises an alarmunmaskalarm unmasks an alarm

4.8.1 Management Settings

CityLink (config)> setinterface help

Usage: setinterface <if#> < [<ipaddress> <netrmask>] | [<disable>]>

if# : Interface no (1-5)

ipaddress : IP Address

netmask : Subnet Mask

disable : Disable Interface if #

CityLink (config)> setinterface 02 192.168.1.1 255.255.248.0

CityLink (config)> setgateway 192.168.7.15

CityLink (config)> listnetconfig

Network interfaces.

# Address Netmask Description

01 192.168.0.32.1 255.255.255.255 Management port

02 192.168.1.1 255.255.248.0 EEB interface 1

03 Disabled EEB interface 2



Default gateway : 192.168.7.15

snmpagent Enables or disables the SNMP agent

stationinfo Lists Station/Section info

updatesw Updates the system software



292 B4008 Rev. M

CityLink

4.10 Q1module Submenu

Q1module submenu commands:

Command Function

listinterface List the nnp interfaces

listroutes Lists the nnp routing table

setaddress Set the Q1 address of the element



B4008 Rev. M 293


5.0 Software Upgrade Procedure for

the CityLink Fast Ethernet Device

1. Download software file to IDU via ftp (1). Note: the filename must be

in 8.3 (xxxxxxxx.eee) format. See Chapter 5.1 (this Section)

2. Log in on console or telnet session to the IDU and in the “config”

submenu issue the command “updatesw [filename]”, where [filename]

is substituted for the name given to the file in step 1.

3. After the file is loaded to flash, reboot the IDU.

Figure VIII-3



294 B4008 Rev. M

CityLink

5.1 How to download a file to the IDU:

[host] : is either the host name for your IDU or the IP address in

xxx.xxx.xxx.xxx format.

5.1.1 Using the Console FTP Client

In a dos prompt go to the folder where your file is stored. Issue thecommand “ftp [host]” and log in with your administrator password. On the

ftp client prompt issue the following commands:

“bin” to enable binary transfers.

“hash” to toggle printing `#' for each buffer transferred

“put [filename]” to transfer the file.

“bye” or “quit” to exit the ftp client.

Figure VIII-4 Downloading using the Console FTP Client



B4008 Rev. M 295


5.1.2 Using the Internet Explorer

(This requires downloading the browsing enhancements from Microsoft)

Go to the URL “ftp://[host]” and log in with your administrator password.

Drag the software file from a local folder to the Internet explorer window.

Close Internet explorer to terminate the connection

Figure VIII-5 Downloading using the Internet Explorer



296 B4008 Rev. M

CityLink

5.2 How to download a file to the ODU

1. Download ODU software file to IDU via ftp. Ref. 5.1 above.

2. Log in on console or telnet session to the IDU and in the “radio” submenu

issue the command “downloadodusw”.

3. After the file is downloaded to ODU, ODU is automatically rebooted.

Figure VIII-6



B4008 Rev. M 297


NEW Network Management SystemThe management and supervision of CityLink Fast Ethernet may be

performed in various ways depending on the actual application.

• NERA’s NEW-NMS can work as an SNMP-manager and control and

supervise the radio-relay (described in the follwing chapters).• The CityLink Fast Ethernet may be treated as just another LAN device

and controlled and supervised via the built in SNMP agent (described

directly after the NEW-chapters).

• Interfaces: 10Base-T LAN port or one of the 4 Ethernet ports.

6.0 Start NEW-NMS & Connect

First set master as community name.The SNMP Settings configurationsheet can be opened from the Configuration menu. Use same commu-

nity name as in Chapter 4.6 (this Section) Security Submenu.

Figure VIII-7 Setting Community Name in SNMP Settings

Add IP with SNMP checked or specify Search area and do a discover. For

details regarding adding elements and discover; see the NEW-NMS

manual (B1091).



298 B4008 Rev. M

CityLink


Get: The community string used during discovery of SNMP

elements NOT defined in any search area.

Set: Default Set community string for elements NOT defined

in any search area.SNMP: The UDP port used as destination port for discovery of

SNMP elements.

Trap: UDP port used by NEW-NMS for receiving Traps.

Start Address: Starting IP address of the range to be searched. Format of

the address must be xxx.xxx.xxx.xxx.

Stop Address: Stop IP address of the range to be searched. Stop address

must be equal or greater than start address. Format of the

address must be xxx.xxx.xxx.xxx.

Add an entry to the search area:

1.Press the Add button, an entry is added to the list. By default start address

= «0.0.0.0», stop address = «0.0.0.0», read community = «public», and

write community = «private».

2.To change the default values dobbel click the entry in question and enter

the wanted value.

3.To save your settings press OK.

Remove an entry from the search area:

1.Select the entry from the list.

2.Press the Remove button.

3.To save your settings press OK.



B4008 Rev. M 299


Figure VIII-8 Adding IP Address



300 B4008 Rev. M

CityLink

7.0 Network Element ConfigurationConfiguration of Network Elements is achieved using a set of property-

sheets. The property-sheets are modeless, so configuration of several

different modules can be displayed simultaneously.

••••• To open the configuration property sheets:

Select the object you want to view or change either from the Explorer View

or a Map View. Select a Configuration command either from the context

sensitive menu (right mouse-button) or from the Configuration Edit

menu.

The property-sheets are divided into two categories by means of function-

ality:

Figure VIII-9 Buttons on Configuration property sheets with

multiple settings

Configuration Property sheets with Multiple Settings:

The program retrieves the current settings from the Network Element

(NE) when the property-sheet is opened. No set-messages is sent to the

element and no data is modified in program’s data structure before the user

presses one of the property-sheet buttons:

Buttons:

Set: Applies the current settings in the Network Element (NE).

Get: Retrieves the current settings of the Network Element (NE).

Close: Closes the property-sheet without saving or setting any data.



1 First, get the current settings from the NE by pressing Get. (The

settings are automatically retrieved from the NE when the property-

sheet is opened).





B4008 Rev. M 301


Configuration Property sheets with Single Interactive Settings:

The program retrieves the current NE settings when the property-sheet is

opened. Has no Get or Set buttons; All functional buttons are placed in the

property-pages. A message is sent to the Network Element immediately

when a control is changed or a button is pressed.

Property-sheet buttons:

Figure VIII-11 Configuration property sheet information field

Figure VIII-10 Buttons on Configuration property sheets with

single active settings

Buttons:

Close: Closes the property-sheet.


All property-pages have an information field at the bottom reflecting the

current status of the data shown in the property-page and the date and time

the property sheet data was retrieved from the Network Element.



302 B4008 Rev. M

CityLink

8.0 Element Node

8.1 Element Id

The CityLink Element Id property sheet shows main information about the

Network Element like name, type, serial number and different addresses.

The fields with white background can be altered by users with proper user privileges The gray fields are non-editable.

The Element Id configuration sheet can be opened from the Configura-



Explorer view and then selecting Edit Element ID from the Configu-

ration menu.

Figure VIII-12 Element ID Configuration Sheet

Fields: DescriptionSerial Number: The serial number of the NE. (Not editable)

NE Type: The type of NE. (Not editable)

Name: The name of the NE. (max. 32 characters)

Section Address: The section address of the NE.

NE Address: The NE address. Used to identify NEs within a

section.

MAC Address: The Media Access Control address of the NE. (Not

editable)IP Address: The Internet Protocol address of the NE.



B4008 Rev. M 303


8.2 NE Clock

The NE Clock sheet lets you synchronize the Network Element Date/Time

with the NEW-NMS/PC Date/Time. (The NE Clock is set to the same date/

time as the PC Clock)

The NE Clock configuration sheet can be opened from the Configurationcontext menu of the Element node in the Explorer view. The sheet can


Explorer view and then selecting Edit NE Clock from the Configura-

tion menu.

Figure VIII-13 NE Clock Configuration Sheet


The Element’s Clock: The Date and Time retrieved from the NE.

Difference from The difference between the PC clock and the

NEW-NMS (your PC): NE Clock



304 B4008 Rev. M

CityLink

8.3 Software Versions

The software versions property sheet displays the software revisions and

status of the SU and the available subunits

The SW Versions configuration sheet can be opened from the Configu-

ration context menu of the Element node in the Explorer view. The sheetcan also be invoked by selecting (highlighting) the Element node in the

Explorer view and then selecting Edit SW Versions from the Config-

uration menu.


SW Component: Software title

Bank: Software location

Revision: Sofware revision. The field will display “unknown”

if the system has this unit present, but is unable toretrieve the information from it.

Status: Valid: Complete or valid software.

Figure VIII-14 SW Versions Configuration Sheet



B4008 Rev. M 305


8.4 Production Data

The production data property sheet presents details about the HW compo-

nents within CityLink Fast Ethernet.

The Production Data configuration sheet can be opened from the Con-

figuration context menu of the Element node in the Explorer view. The

sheet can also be invoked by selecting (highlighting) the Element node inthe Explorer view and then selecting Edit Production Data from the

Configuration menu.


InventoryName: The name of the HW component.

InventorySerialNumber: The serial number of the HW component.

InventoryVersion: The HW component version.

Figure VIII-15 Production Data Property Sheet



306 B4008 Rev. M

CityLink

8.5 SNMP Agent(s) Settings

The SNMP Agent(s) property sheet shows the current SNMP settings. The

Element SNMP Settings configuration sheet can be opened from the

Configuration context menu of the Element node in the Explorer view.

The sheet can also be invoked by selecting (highlighting) the Element

node in the Explorer view and then selecting Edit SNMP Settings fromthe Configuration menu. All information presented in the configuration

sheet is set locally and not retrieved from the element.

NOTE! In order for NEW-NMS to manage the SNMP element, the SNMP

Agent settings configured locally must match the settings in the NEW-

NMS. Please see the CityLink Fast Ethernet Agent Configuration.

NEW-NMS is using received traps for keeping an accurate element status.

SNMP Traps are unreliable and no delivery guarantee is given, to over-come this weakness a query for number of traps sent from the SNMP

element must be performed from NEW-NMS at given time intervals. If the

number of traps sent from the element is not equal to the number of traps

received from the element, traps have been lost and alarm synchronization

is needed.

Figure VIII-16 Element SNMP Settings Property Sheet



B4008 Rev. M 307


Columns: Description:

IP address The Internet Protocol address of the

NE (not editable).

Set Community: The community string used when

setting information at the element

(set request).Get Community: The community string used when

retrieving information at the element

(get/getNext request).

Port: Element UDP Port for

Get/Getnext/Set

No. Receivers: Number of Managers set up to receive

traps from this element.(Not used)

••••• Edit values in the list:

The values of the columns SetCommunity, GetCommunity, Port, and

No Trap receiving Managers can be modified:

1. Double click cell to be edited.

2. Type new value.

3. Click outside cell.

4. To save your settings press Set.



308 B4008 Rev. M

CityLink

8.6 Trap Table

The trap table presents information about the managers currently regis-

tered to receive traps.

The Trap Table configuration sheet can be opened from the Configura-


can also be invoked by selecting (highlighting) the Element node in theExplorer view and then selecting Edit Trap Table from the Configu-

ration menu.


IP Address: IP address of the registered SNMP manager

trap Port: Which port is used for sending Traps to managersLast access: Time the agent was last accessed by the SNMP manager

Figure VIII-17 Trap Table Configuration Sheet



B4008 Rev. M 309


8.7 MIB II - System Group

The System Info property page shows some of the MIB-II System Group

attributes. The fields with white background can be altered by users with

proper user privileges. The gray fields are non-editable.

The MIB II Info configuration sheet can be opened from the Configuration

context menu of the Element node in the Explorer view. The sheet can


Explorer view and then selecting Edit MIB II Information from the

Configuration menu.

Figure VIII-18 System Info Property Sheet



310 B4008 Rev. M

CityLink


Sys Description: A textual description of the entity. This value should

include the full name and version identification of the

system’s hardware type, software operating-system,

and networking software. It is mandatory that this onlycontain printable ASCII characters.

Sys OID: The vendor’s authoritative identification of the

network management subsystem contained in the

entity. This value is allocated within the SMI.

enterprises subtree (1.3.6.1.4.1) and provides an easy

and unambiguous means for determining ‘what kind of

box’ is being managed.

Name: The name of the Network Element.

Location: The physical location of this node (e.g., ‘telephonecloset, 3rd floor’).

Contact: The textual identification of the contact person for

this managed node, together with information on how

to contact this person.

Sys Uptime: The time since the network management portion of the

system was last re-initialized.


In order for the user to change settings the Set Community name must be

configured as described in SNMP Agent(s) settings.

1 First, get the current settings from the NE by pressing Get. (The

settings are automatically retrieved from the NE when the property-

sheet is opened).





B4008 Rev. M 311


8.8 MIB-II SNMP Group

The MIB-II SNMP property page presents the performance of the under-

laying SNMP implementation on the managed entity and tracks things such

as the number of SNMP packets sent and received.

A complete description of each field is available by holding the mouse

cursor over wanted item in the dialog and the description found in RFC-1213 will be displayed.

Figure VIII-19 MIB-II SNMP Property Sheet


OID Object IDentifier, uniquely defines a managed objects. These

can appear in two forms: numeric (i.e. 1.3.6. 1.2.1.11.1) and

«human readable» (i.e. iso.org.dod.internet.mgmt.mib-

2.snmp.snmpInPkts)

NEW-NMS uses «human readable» form and will display the

above example as snmpInPkts.

Value Value contained in this OID.



314 B4008 Rev. M

CityLink

8.9.1.2 Line Terminal

The different main traffic loops:

All main traffic near end loops are swapped (port 1→ port 2, port 3→ port

4).

Ethernet Loop near end with swap

E1/T1 loops near end

E1/T1 loops far end

Line TX SORP LR out to LT in loop endLine RX SORP LT out to LR in loop near end

Figure VIII-21 Looping Configuration Sheet, Line Terminal

Note! FAR end loop will break management traffic to other side.



B4008 Rev. M 315


8.9.2 Wayside Loops

The different 2 Mbit/s Wayside Loops:

Wayside Loop (far end)

Wayside Loop (near end)

Figure VIII-22 Looping Configuration Sheet, Wayside Channel Tab



316 B4008 Rev. M

CityLink

The different 64kbit/s loops:

64kbit/s Channel 1 Loop (far end)

64kbit/s Channel 1 Loop (near end)

64kbit/s Channel 2 Loop (far end)

64kbit/s Channel 2 Loop (near end)

8.9.3 64 kbit/s Loops

Figure VIII-23 Looping Configuration Sheet, 64kbit/s Tab



B4008 Rev. M 317


9.2 Ethernet Extension Board

The main purpose of the Ethernet Extension Board (EEB) is to convert

Ethernet to/from STM-1 frames. TheEEB also multiplexes 4 E1/T1 channels

into the STM-1 frames.

TheEEBconfiguration sheet can be opened from the Configuration context

menu of the IDU node in the Explorer view. The sheet can also be invoked by selecting (highlighting) the IDU node in the Explorer view and then

selectingEdit Ethernet Extension Boardfrom the Configuration menu

9.0 In Door Unit (IDU)

9.1 64 kbit/s Channels

Two 64 kbit/s channels can be inserted into the SOH. Each of the 64kbit/s

channel will occupy one byte of the SOH frame. Both channels can be

retrieved from and inserted into the line and radio side independently.The 64 kbit/s Channels configuration sheet can be opened from the

Configuration context menu of the IDU node in the Explorer view. The sheet

can also be invoked by selecting the IDU node in the Explorer view and then

selectingEdit 64 kbit/s Channelsfrom the Configuration menu.


Status: Enabled Enables the 64 kbit/s Channel

Disabled Disables the 64 kbit/s Channel

Direction: Choose the direction the 64 kbit/s Rx channel

should be extracted from.

Line 64 kbit/s Rx is inserted from line SOH frames

Radio 64 kbit/s Rx is inserted from radio SOH frames

Figure VIII-24 64kbit/s Channels Configuration Sheet



318 B4008 Rev. M

CityLink

9.2.1 Ethernet Ports

Figure VIII-25 Ethernet Ports Configuration Sheet


portEthStatus This entry enables/disables the port.

portEthFlowCtrl This entry controls flow control setting.

portEthLinkStatus This entry shows the current link status.

portEthPartitionStatus This entry shows the current partiton

status for the port.

portEthLinkSpeed This entry controls the link speed for the port.

portEthLinkDuplex This entry controls the link duplex mode for

the port.

portEthLinkFailureShutdown This entry controls the Link Failure

Shutdown mode for the port.

When enabled port is forced shutdown

due to SDH alarm or remote ETH-port no

Link.

Note: Port is NOT forced shutdown asdescribed above if IP management is

enabled on port.



B4008 Rev. M 319


9.2.2 2 Mbit/s Ports

Configuration of tributary E1/T1 ports (2Mbit/s or 1.5Mbit/s).


port2MBIndex Tributary E1/T1 port index .

port2MBStatus Presents the status of the tributary E1/T1 port.

Figure VIII-26 2Mbit/s Ports Configuration Sheet

Priority Port Designates the prioritized port.(Guaranteed

100Mb operation.)

Auto Partition Auto partition state for the EEB ethernet

ports.

Note :Ethernet Port fixed speed / duplex mode setting:

1) Set user terminal equipment speed / duplex mode to Auto.

2) On CityLink FastEthernet port sett required link speed.

Note: It is not recommended to use 10Mb Half duplex .



320 B4008 Rev. M

CityLink

9.3 Wayside Channel

A Wayside channel can be inserted in the SOH in either line-direction or

radio-direction. The Wayside channel will occupy 33 bytes (32 bytes data

+ 1 byte alignment information) of the SOH. The Wayside channel use the

Rx and Tx connection at the front panel of the IDU. Rx is received data and

Tx is sent data.The Wayside configuration sheet can be opened from the Configuration

context menu of the IDU node in the Explorer view. The sheet can also be

invoked by selecting (highlighting) the IDU node in the Explorer view and

then selecting Edit Wayside from the Configuration menu.

Fields: Options: Description

Status: Enabled Enables the Wayside Channel

Disabled Disables the Wayside Channel

Direction: Line Wayside Rx is extracted from line SOH

Radio Rx is extracted from radio SOH.

Figure VIII-27 Wayside Channel Configuration Sheet



B4008 Rev. M 321


9.4 Auxiliary Output

There are four configurable auxiliary output pins in the ALM/AUX port.

The pins are connected to a relay, which can either be controlled manually,

or triggered automatically on a user selectable alarm.

The Auxiliary Output Configuration sheet can be opened from the

Configuration context menu of the IDU node in the Explorer view. Thesheet can also be invoked by selecting (highlighting) the IDU node in the

Explorer view and then selecting Edit Auxiliary Output from the

Configuration menu.

Figure VIII-28 Auxiliary Output Configuration Sheet



322 B4008 Rev. M

CityLink


Output control radio Manual control Set the usage of the auxiliary

buttons: or output pin. (Disabled if the

Alarm triggered CityLink does not support alarm

triggers.)

Manual Relay status Closed or open If the auxiliary output is set to

radio buttons manual control, these buttons

will be enabled, and can be used

to manually control the state of

the relay.

Equipment tree - Displays and selects the alarms

available for alarm triggers. Thiswill be disabled if the auxiliary

output is set to manual control.

Alarm trigger list - Displays the alarm triggers

configured. Disabled if the

auxiliary output is set to

manual control.

Add alarm button - Adds the currently selected

alarm in the equipment tree to

the alarm trigger list. If there is

no selection, or if the selected

tree node doesn’t correspond

to an alarm, nothing happens.

Disabled if the output is on

manual control.

Remove alarm button - Removes the currently select-

ed alarm from the alarm trigger

list. Disabled if the output is on

manual control.

Alarm triggered relay Closed or Open If the auxiliary output is set to

status radio buttons alarm triggered control, these

buttons will be enabled, and can

be used to control the state of the relay when the alarm-

conditions are raised.



B4008 Rev. M 323


9.5 BER Thresholds

The Viterbi decoder is a component using a Viterbi low complexity

algorithm for decoding/error correcting the received bit-sequence in the

NE. The viterbi error rate is used as a quality measurement for the radio

hop.

When the Viterbi error rate exceeds certain values, alarms are generated.

The threshold values decides when alarms are generated. The threshold

values can be changed by the user.

Alarm Id Default value Alarm severity

HBER Indicator for BER >1exp-3 MAJOR

LBER Indicator for LBER >1exp-6 MINOR

EW-BER Indicator for EW-BER >1exp-10 WARNING

Internal proportions: HBER > LBER > EW

The BER Threshold configuration sheet can be opened from the Config-

uration context menu of the Radio node under the IDU node in the


the Radio node under the IDU node in the Explorer view and then

selecting Edit BER Threshold from the Configuration menu.

Figure VIII-29 BER Threshold Configuration Sheet



324 B4008 Rev. M

CityLink


HBER 1.0e-3 - 1.0e-10 Range.

A Major alarm is generated when the

Viterbi error rate exceeds the High BER

threshold value. AIS is inserted when theHBER threshold value is exceeded.

LBER 1.0e-3 - 1.0e-11 Range.

A Minor alarm is generated when the

Viterbi error rate exceeds the Low BER

threshold value.

EW 1.0e-3 - 1.0e-12 Range.

A Warning is generated when theViterbi error rate exceeds the Error

Warning threshold value.



B4008 Rev. M 325


9.6 Laser Control

Available on CityLink Fast Ethernet Line Terminal only.

The optical port may or may not have implemented Automatic Laser

Shutdown (ALS). This is a function designed for eye safety purposes,

according to ITU-T rec. G.958. When implemented, ALS may be enabledor disabled.

When ALS is not implemented or enabled the laser must be turned on/off

manually.

When ALS is enabled, the laser automatically will restart after a waiting

time period (selectable), when having previously been turned off. (If the

section of operation is not connected or Loss Of Optical Signal from far

end is detected, the laser will again be turned off after 2 sec.) The waiting period is by default set to 1 minute.

The Laser Control configuration sheet can be opened from the Config-

uration context menu of the Optical Line node under the IDU node in

the Explorer view. The sheet can also be invoked by selecting (highlight-

ing) the Optical Line node under the IDU node in the Explorer view and

then selecting Edit Laser Control from the Configuration menu.

Figure VIII-30 Laser Control Configuration Sheet



326 B4008 Rev. M

CityLink

Fields: Buttons: Description:

ALS:

Enabled/Disabled Toggles ALS On/Off

Waiting Time (1.0 - 5.0 minutes ) Specifies waitingtime before the laser is turned on. If

section of operation is connected and

optical signal from far end is present,

laser will remain on, if not laser will

be turned off after 2 seconds.

Get Retrieves Laser Control settings

from the NE.

Set Sends Laser Control settings to the NE.

Restart (2 Seconds) Manually restart the laser for 2 seconds.

Restart (90 Seconds) Manually restart the laser for

90 seconds for testing purposes.

Manual

Control: (ALS disabled or not implemented)

On Manually turn the laser on.

Off Manually turn the laser off.

Status: Shows the status of the Laser Unit.



B4008 Rev. M 327


10.0 Out Door Unit (ODU)

10.1 Antenna Data

This sheet shows some main characteristics of the antenna. Only the

antenna code can be altered. The antenna data are stored in a database file.

The Antenna Data configuration sheet can be opened from the Configu-ration context menu of the Antenna node in the Explorer view. The sheet

can also be invoked by selecting (highlighting) the Antenna node in the

Explorer view and then selecting Edit Antenna from the Configura-

tion menu.

Figure VIII-31 Antenna Data Configuration Sheet


Antenna code The antenna code. Unique code for each antenna type.Gain The antenna Gain. (dB) Gain is a measurement of the

antennas ability to transform electrical signals to

electromagnetic waves.

Polarization The polarization direction of the antenna.

FB Front/Back Ratio. Ratio between the Gain in forward

direction and Gain in backward direction.

Diameter The physical antenna diameter. [ Meter]

Frequency range The frequency range where the antenna can be

expected to operate successfully.



328 B4008 Rev. M

CityLink

10.2 Power Settings

ATPC (Automatic Transceiver Power Control) is a function for effective-

ly reducing the interference probability in your network. The output power

from the transceiver is automatic controlled. If the regulation loop for the

ATPC stops functioning, an alarm is generated. This alarm can be delayed.

The output power should be muted when the frequency setting is changed.The Power Settings configuration sheet can be opened from the Config-

uration context menu of the ODU node in the Explorer view. The sheet can


view and then selecting Edit Power Settings from the Configuration

menu.

Figure VIII-32 Power Settings Configuration Sheet



B4008 Rev. M 329



RF-INPUT- dBm The upper threshold value for when to

WARNING- generate a RF Input Level Warning

high (Alarm nr. 1504).

RF-INPUT- dBm The lower threshold value for when to

WARNING- generate a RF Input Level Warning

low (Alarm nr. 1504).

Manual dBm The output power level used when ATPC

output level not is activated.

Mute output Mutes the output power. No output power power is sent.

Maximum dBm Maximum output power for

output power transmitting.

Manual Disable ATPC.

Transmit

Output Power

(MTPC)

Automatic Enable ATPC.

Transmit

Output Power

(ATPC)

Reference dBm The wanted input level when ATPC is

input level activated.

Default dBm Set the Power Level to use when an

output level ATPC alarm occurs.

ATPC alarm seconds The ATPC alarm can be delayed a

delay certain number of seconds.



330 B4008 Rev. M

CityLink

10.3 Frequency Settings

The Duplex Distance between the Rx and Tx band is fixed. The user can set

the Tx frequency by clicking on the frequency slots. Since the duplex

distance is fixed the Rx frequency will be automatically set. The corre-

sponding Tx and Rx frequency must be set in the opposite NE.

NEW-NMS/-Configurator receives the frequency plan from the NE.

When no NE is connected (off-line) no frequency plan will be shown.

The output power should be muted when the frequency setting is changed.

The Frequency configuration sheet can be opened from the Configura-

tion context menu of the ODU node in the Explorer view. The sheet can


view and then selecting Edit Frequency from the Configuration

menu.

Figure VIII-33 Frequency Configuration Sheet



B4008 Rev. M 331



Frequency plan Choose the wanted frequency plan.

The frequency plan must.

correspond to your transceiver.

TX Frequency MHz The used Tx Carrier frequency.RX Frequency MHz The used Rx Carrier frequency.

Coding TCM or TCM+RS The coding scheme

Modulation The modulation scheme used with

this frequency plan.

Data rate STM-1 or STM-0

Channel spacing MHz The distance between the channels

in this frequency plan.

Duplex Distance MHz The distance between the Tx and

the Rx carrier frequency.Innermost MHz The distance between the highest

spacing frequency in lower half and the low-

est frequency in the upper half of

the frequency plan.

Compensation Digital filters in the Modem Board

filter compensating for RF Filter and

branching characteristics.

TX Frequency MHz Tx Lower sideband frequency for

Band, Min this frequency plan.

TX Frequency MHz Tx Upper sideband frequency for

Band, Max this frequency plan.

RX Frequency MHz Rx Lower sideband frequency for

Band, Min this frequency plan.

RX Frequency MHz Rx Upper sideband frequency for

Band, Max this frequency plan.

Status The result of the last frequency

change operation (unknown, ok,executing, failed).

Reset Modem When this item is checked the

modem will be reset when applying

selected frequency data. Only to be

used when changing frequency plan.

NOTE!

Both the IDU and the ODU must be rebooted after a change of frequency and/

or Reed Solomon code. This is done by disconnecting and reconnecting

power to the IDU.



332 B4008 Rev. M

CityLink

11.0 Performance

11.1 G826 Performance

G.826 is an ITU-T quality recommendation for SDH networks.

The Network Element has several registers for collecting G.826 perform-

ance data. The G.826 data is divided into three categories; G.826 15min,G.826 Day and G.826 Month and they show the B1 measurements for 16

periods of the category. (4 hours of 15min data, 16 days and 16 months are

available in the NE).

The G-826 Performance configuration sheet can be opened from the

Performance context menu of the Element node in the Explorer view. The

sheet can also be invoked by selecting (highlighting) the Element node in

the Explorer view and then selecting Performance Registers from the

Main menu.

Figure VIII-34 G-826 Performance Configuration Sheet



B4008 Rev. M 333



Time interval The interval of the measurement (15 min., day, month).

Period The sequence number of the performance register.

Register 0 is the running measurement, register 1 is the

latest completed measurement.SES Severely Errored Seconds. The number of one-second

periods which contains > 30% errored blocks or at least

one Severely Disturbed.

UAS The number of UnAvailable Seconds. A period of un-

available time begins at the onset of 10 consecutive SES

events. These ten seconds are considered to be a part of

the unavailable time. A new period of available time

begins at the onset of ten consecutive non-SES events.

These 10 seconds are considered to be part of availabletime.

BBE The number of Background Block Errors. An errored

block not occurring as part of an SES.

ES Errored Second. The number of one second periods

with one or more errored blocks.

Start Time The start time of the measurement period.

Status Status of the counter.



334 B4008 Rev. M

CityLink

11.2 Port Performance

The Repeater port information property sheet presents performance and

error statistics for the individual ports on the Network Element. Each

entry in the table contains information for a single port. The data are

gathered from the RFC-2108 MIB.

The Port Performance configuration sheet can be opened from the

Performance context menu of the IDU node in the Explorer view.

Fields : Description:

Readable frames Please refer to RFC-2108 MIB.

Readable octets Please refer to RFC-2108 MIB.Runts Please refer to RFC-2108 MIB.

Late events Please refer to RFC-2108 MIB.

Autopartition Please refer to RFC-2108 MIB.

Total errors Please refer to RFC-2108 MIB.

Figure VIII-35 Port Performance Configuration Sheet



B4008 Rev. M 335


11.3 Repeater Performance

The Repeater Information Property sheet presents Ethernet performance.

The figures presented are based on the performance of every port on the

Network Element. Each entry in the table contains information about a

single non-trivial repeater.The data are gathered from the RFC-2108 MIB.

The Repeater Performance configuration sheet can be opened from the

Performance context menu of the IDU node in the Explorer view.


Tx Collisions Please refer to RFC-2108 MIB.Total Frames Please refer to RFC-2108 MIB.

Total errors Please refer to RFC-2108 MIB.

Total octets Please refer to RFC-2108 MIB.

Figure VIII-36 Repeater Performance Configuration Sheet



336 B4008 Rev. M

CityLink

12.0 Fault

12.1 NE Alarm Log

The NE Alarm Log property sheet displays the settings and content of the

NE alarm log.

The NE Alarm Log configuration sheet can be opened from the contextmenu of the Element node in the Explorer view. The sheet can also be

invoked by selecting (highlighting) the Element node in the Explorer

view and then selecting NE Log Manager from the Fault menu.

When pressing View in the NE Alarm Log Manager, a dialog box is

displayed prompting for the number of records to retrieve.

Controls: Options: Description:

Log full action Wrap or Halt Actions to take when the log is full.

Max. number - The number of entries theNE alarm

of events log can hold.Number of events - Current number of log entries.

Figure VIII-37 NE Alarm Log Configuration Sheet

Figure VIII-38 Number of Records Dialog Box



B4008 Rev. M 337


13.0 Security

13.1 Security Log

CityLink Fast Ethernet has an internal security log that can contain up to

1000 events. To view the local security log, select a CityLink Fast Ethernet

object (in a map or explorer view), and select the NE Security Logcommand either from the context menu or from the Security main menu.


Security Log Index The index of the Security log

Security log entry text A descriptive text of the event.

Security log entry time The time of the event.

Figure VIII-39 Security Log



338 B4008 Rev. M

CityLink

SNMP & MIB Description

14.0 General• SNMP = Simple Network Management Protocol

– Open internet protocol, requires IP connection.

• MIB = Media Information Base

– File describing all details about the equipment.

– This file must be copied into SNMP-manager

15.0 Supported MIB’s

The CityLink Fast Ethernet embedded application supports the following

MIBs

Name Description Defined in

NERA-FAST-ETHERNET-MIB Specific management Nera_Clip.mib

of CityLink Fast

Ethernet devices.

NERA-MIB General management Nera.mib

of Nera radio

equipment.

SNMP-REPEATER-MIB General management/ RFC 2108

monitoring of

repeater units.

RFC1213-MIB (mib2) General management RFC 1213

of network devices.

NERA-FAST-ETHERNET-MIB purposes:

• To support common management task through SNMP.• To provide network management with an acceptable security level.

• To support industry standard MIB definitions where appropriate.

• To create a modular MIB design to reflect the modularity of the agent

software.

• To facilitate future updates and configuration changes.

• To conform to the established conventions of the “NERA-MIB” MIB.



B4008 Rev. M 339


16.0 MIB OverviewThe MIB is separated into 8 sub-modules as shown below.

Figure VIII-40 MIB Overview



340 B4008 Rev. M

CityLink

16.1 Unit

This unit contains entries related to overall system properties. This

includes system time, status, transmission settings and management

addressing

Figure VIII-41 MIB Sub-modules, Unit



B4008 Rev. M 341


16.2 IDU

This module provides configuration and monitoring of IDU hardware

interfaces. This includes the Ethernet ports, 2Mbit/s ports, 64kbit/s ports

and the auxiliary port. The module also contains the global error level

limits for the IDUs data inputs.

Figure VIII-42 MIB Sub-modules, IDU



342 B4008 Rev. M

CityLink

16.3 ODU

This module contains the ODU specific control settings and operational

status. The ODU functional capabilities are obtainable through the “capa-

bilities” sub module.

Figure VIII-43 MIB Sub-modules, ODU



B4008 Rev. M 343


16.4 Test Manager

This Module provides means to perform test functions on the equipment.

The design provides an extensible way of generating traffic loops on

various interfaces and test points. It is possible at run time to query for

possible loop settings and perform tests without previous knowledge of

the test loops provided by the equipment.

Figure VIII-44 MIB Sub-modules, Test Manager



344 B4008 Rev. M

CityLink

16.5 Performance Manager

The module provides means of access to traffic performance data. The

current design only supports the G826 B1 measurement type but the

layout of the module makes feasible to extend this in future versions.

Figure VIII-45 MIB Sub-modules, Performance Manager



B4008 Rev. M 345


16.6 Fault Manager

This module is an extension to the fault management framework defined

by the “NERA-MIB” specification. It supplies an extension to the previous

fault log which is more configurable than the previous. In addition it

supplies new functionality where a manager can query all supported alarm

types from the equipment and retrieve descriptions and node informationfor each one. This will reduce the linking between the management

software and the agent considerable.

Figure VIII-46 MIB Sub-modules, Fault Manager



B4008 Rev. M 347

Troubleshooting

Troubleshooting

SECTION IX



348 B4008 Rev. M

CityLink

1.0 GeneralThis Section describes two ways of troubleshooting; by means of LEDS

located at the In Door Unit's front panel and by means of NEW-NMS

Configurator.

2.0 Description of Alarm LEDs

2.1 IDU Alarm LEDs

The functions of the alarm LEDs are as follows:

CRITICAL Red Will be activated when one or more

critical alarms are activated

MAJOR Red Will be activated when one or moremajor alarms are activated

MINOR Red Will be activated when one or more

minor alarms are activated

WARNING Orange Will be activated when one or more

warnings are activated

POWER ON Green Will be on when main power is > 39V

2.2 HSB-IDU Alarm LEDs and Switch Indicators

The functions of the alarm LEDs are as follows:

CRITICAL Red Will be activated when one or more

critical alarms are activated

MAJOR Red Will be activated when one or more

major alarms are activated

MINOR Red Will be activated when one or more

minor alarms are activated

WARNING Orange Will be activated when one or morewarnings are activated

PWR 1 Green Will be on when main power is > 39V

PWR 2 Green Will be on when main power is > 39V

The functions of the Switch indicators are as follows:

RX DIRA Green Will be on when receiving on A-branch

RX DIRB Green Will be on when receiving on B-branch

TX DIRA Green Will be on when transmitting on A-branchTX DIRB Green Will be on when transmitting on B-branch



B4008 Rev. M 349

Troubleshooting

2.3 LEDs on Line Interface Plug-in Boards

G.703 Line interface:

Green LED is activated when input signal is present.

Multimode Fiber Line interface:


Singelmode Fiber Line interfaces (1310 Nm and 1550 Nm):


CAT-5 UTP Line interface:

Bicolor LED. Emits red when input signal is present and loss of frame

(LOF) alarm is activated. Emits green when input is normal and LOF is low.

3.0 Troubleshooting by NEW-NMS Configurator

3.1 Introduction

Fault management is the process of locating and correcting network

problems or faults. Fault management is possibly the most important task

in network management. It consists of identifying the occurrence of afault, isolating the cause of the fault and correcting it if possible. The fault

management increases the network reliability by giving the network

operator a tool that quickly detects problems and initiates recovery

procedures.

NEW contains functions for acquisition, presentation and storage of

alarms and events from the network to be managed.

3.2 Information Acquisition

In order to detect faults, information must be gathered from the network.

The state of the network is monitored using two different methods.

3.2.1 Polling

The various network elements should be polled on a regular basis, so that

changes in Network Elements (NE) are detected and network connectivity

is checked. Which NE to poll, the polling rate and what to be polled for aspecific NE is user definable.



350 B4008 Rev. M

CityLink

3.2.2 Event Notification

In addition to polling, some NEs have the ability to spontaneously report

events. The NEW will gather this information in addition to polling. This

feature will decrease the managers response time to network events

considerably.

3.3 Alarm Presentation

In all views, where network information is presented, colors are used to

indicate the alarm severity status of the NEs. To easily identify the status

of the NEs, all alarms are classified according to their severity. Each alarm

severity class has a color. In the different views, the NEs change colors

according to the color of their most severe alarm. The alarm classifica-

tions are described in the table below.

Severity Colour Description

(default)

Normal Green No alarms or warning have been reported

from the NE.

Warning Yellow Indicates the detection of a potential or

impending service-affecting fault, before any

significant affects have been felt. Action

should be taken to further diagnose and

correct the problem in order to prevent itfrom becoming a more serious service-

affecting fault.

Minor alarm Dark Yellow Indicates the existence of a non-service-

affecting fault condition and that corrective

action should be taken in order to prevent a

more serious fault.

Major alarm Orange Signifies that a service-affecting condition

has occurred and urgent corrective action is

required.

Critical alarm Red The most severe alarm. It signifies that a

service-affecting condition has occurred and

an immediate corrective action is required.

No contact Blue Indicates that no contact is achieved with the

NE. The communication settings should be

checked in order to obtain contact with the

element.

Misconfigured Magenta The NE has not been properly configured.



B4008 Rev. M 351

Troubleshooting

3.4 Visual Alarm Notification

There are four different ways of monitoring alarms in NEW. These methods

are described in the following subchapters. The NEW context sensitive help

system offers a more comprehensive support on all features in the NEW

program.

3.4.1 Alarms on a Tree node/leaf in the Explorer view

The Explorer View is opened by selecting Explore Net from the View Menu.

Figure IX-1 shows an example of the Explorer view.

The Explorer View shows the Network information in a logical manner. Each

NE is divided into two main branches; a Transmission branch and an

Equipment branch. The sub-branches and leaves under the Transmission

branch concern the transmission aspects of the NE. The sub-branches andleaves under the Equipment branch concern the physical equipment of the

NE.

Figure IX-1 Example of Explorer View



352 B4008 Rev. M

CityLink

The Explorer view use the severity colours to indicate alarm events. The

alarms are presented in a hierarchical manner. The colour of the most

severe alarm is inherited from the leaf where the alarm was identified, to

all branch leaves up to the section symbol. E.g. the section and NE symbols

will always show the alarm colour of the most severe alarm identified in

the sub-branches in the Explorer view.

By pressing the right mouse button on any nodes/leaves in the Explorer

View and selecting Current Alarms from the context menu, a Current

Alarm List (ref. Appendix III) is opened showing all alarms Hierarchical

below the selected leaf.

3.4.2 Alarms on a Node symbol in the Map view

The Map View is opened by selecting Map Navigator from the ViewMenu. Follow the instructions in the Help file to create a map. Figure IX-

2 shows an example of the view.

The Map View shows the Network information in a physical manner. Each

NE is showed as an NE icon. Graphic-files can be added as background

images in the view. NE icons grouped together with bindings form

networks. The NE icons change their severity colours according to the

current most severe alarm of the NE.

Figure IX-2 Example of Map View

By pressing the right mouse button on a NE icon in the Map View and

selecting Alarms from the context menu, a Current Alarm List (ref.

Appendix III) is opened showing all alarms of the NE.



B4008 Rev. M 353

Troubleshooting

3.4.3 Viewing Alarms in the Current Alarms View

TheCurrent Alarm Viewcan be opened by selectingCurrent Alarms from

the Fault Menu. Figure IX-3 shows an example of the Current Alarms List.

Each alarm is listed as a row in the list as shown in Table IX-1.

The Current Alarms List can also be opened from both the Explorer Viewand the Map View by selecting Current Alarms from the right-mouse-

button-click context menu. The filter is then automatically set up to show

only the alarms hierarchically below the node/leaf the alarm list was

opened from.

Figure IX-3 Example of Current Alarms

Fields Description

Severity The severity of the alarm

Alarm text A short description of the alarmNode The name of the node where the alarm occurred

Table IX-1 Fields in the Current Alarms List

Alarms can also be logged to files. Consult the NEW NMS Manual or the

NEW NMS Help system for further information.



354 B4008 Rev. M

CityLink

4.0 Cable FaultIf a cable fault is indicated, it indicates that the microprocessor communica-

tions between the IDU and ODU have failed. The fault is most probably with

the cable connection. It may be open or shorted. Disconnect the cable from

the IDU and leave the ODU connected. Measure the DC cable resistance between the centre pin and the outer conductor of the N-type connector

terminating the cable by means of a multi-meter.

If resistance is in the order of some hundreds k ΩΩΩΩΩ to a few MΩΩΩΩΩ:

Probably no cable fault.

Replace IDU or ODU, one at the time. If alarm persists, swap the replaced unit

for the original and replace the other unit.

If resistance is less than some hundreds k ΩΩΩΩΩ:Probably cable or connector damage. Check the cable and connectors at both

ends for defects or for reasons that would cause the problem. Remeasure

DC resistance, now with both cable ends disconnected. The resistance

should be “open circuit” and if not replace the entire cable run, terminating

with new N-type connectors.

If resistance is immeasurable (high impedance):

Typically reasons are connectors not terminated correctly or cable cut.

Check the cable and connectors at both ends for defects or for reasons thatwould cause the problem. Remeasure DC resistance, with the outer end

still connected to the ODU. If still immeasurable impedance, replace the

entire cable run, terminating with new N-type connectors.



B4008 Rev. M 355

Appendices

Appendices

SECTION X



356 B4008 Rev. M

CityLink

Appendix I: IDU / HSB-IDU Interface Description

Figure X-1 CityLink IDU

P O

W E R

C o n n e c t o r : P O W E R D - S U B 2 - P I N

C a b l e : U W M K 5 0 5 1

P H O N E

C o n n e c t o r : R J - 4 5 8 - P I N

K i t : 4 C Z 5

H o t S t a n d b y I n t e r c o n n e c t i o n

C o n n e c

t o r : 6 8 - P I N V H D C I r e c e p t a c l e

C a b l e :

8 7 W 5 0 6 6 - 1 A

6 4

k b i t / s S E R V I C E C H A N N E L ( G . 7 0 3

)

C o

n n e c t o r : R J 4 5 8 - P I N

C a

b l e : U W M K 3 0 7 7

L O C A L C R A F T T E R M I N A L ( R S 2 3 2 )

C o n n e c t o r : D - S U B 9 - P I N M

A L E

C a b l e : U W M K 3 1 2 3

S A

F E T Y

G R

O U N D

O D

U I N T E R F A C E

N - T Y P E F E M A L E

A L A R M & A U X I L L A R

Y F U N C T I O N S

C o n n e c t o r : D - S U B 2 5 - P I N F E M A L E

C a b l e : U W M K 3 0 7 6

6 4 k b i t / s S E R V I C E C H A N N E L ( V . 1 1 )

C o n n e c t o r : R J 4 5 8 - P I N

C a b l e : U W M K 3 0 7 7

- 4 8 V D C

6 4 k b

/ s

G . 7 0

3

2 M b / s

W a y s i d e

S V C E

E x t . 1

P h o n e

6 4 k b

/ s

V . 1 1

2 M H z

S y n c .

S V C E

E x t . 2

1 0 B a s e T

L A N

I D U - H S B I N T F C

C A L L

A L M & A U

X

L C T

N I 2

N I 1

C R I T I C A L

M A J O R

M I N O R

W A R N I N G

P O W E R

1 5 5 M b / s L I N E

2 M

b i t / s W A Y S I D E C H A N N E L

C o

n n e c t o r : R J 4 5 8 - P I N

C a

b l e : 8 7 W 5 0 9 7 - 2 A , 1 0 m p a t c h c a b l e

2 M

H z S Y N C

( L a t e r r e l e a s e )

1 0 B a s e T E t h e r n e t

O f f t h e s h e l f s t a n d

a r d

e t h e r n e t c a b l e

S E R V I C E C H A N N E L E X

T E N S I O N 1

C o n n e c t o r : R J - 4 5 8 - P I N

C a b l e : 8 7 W 5 0 9 7 - 1 A


T E N S I O N 2

C o n n e c t o r : R J - 4 5 8 - P I N

C a b l e : 8 7 W 5 0 9 7 - 1 A

S l o t f o r o p t i o n a l L i n e

I n t e r f a c e P l u g - I n B o a r d

R e f . F i g . X - 6

C O L L E C T I V E C A L L

S l o t f o r o p t i o n a l

E x t e n s i o n B o a r d

P W R

N E T W O R K I N T E R F A C E ( R S 4 8 5 )

C o n n e c t o r : D - S U B 9 - P I N

F E M A L E

C a b l e : U W M K 3 0 7 8 , U W M K 3 0 7 9



B4008 Rev. M 357

Appendices

Figure X-2 CityLink HSB-IDU

P O

W E R

C o n n e c t o r : P O W E R D - S U B 2 - P I N

C a b l e : U W M K 5 0 5 1

P H O N E

C o n n e c t o r : R J - 4 5 8 - P I N

K i t : 4 C Z 5


C o n n e c t o r : 6 8 - P I N V H D C I r e c e p t a c l e

C a b l e : 8 7 W 5 0 6 6 - 1 A

6 4

k b i t / s S E R V I C E C H A N N E L ( G . 7 0 3 )

C o

n n e c t o r : R J 4 5 8 - P I N

C a

b l e : U W M K 3 0 7 7

L O C A L C R A F T T E R M I N A L ( R S 2 3 2 )

C o n n e c t o r : D - S U B 9 - P I N M A L E

C a b l e : U W M K 3 1 2 3

S A

F E T Y

G R

O U N D

A L A R M & A U X I L L A R

Y F U N C T I O N S

C o n n e c t o r : D - S U B 2

5 - P I N F E M A L E

C a b l e : U W M K 3 0 7 6

6 4 k b i t / s S E R V I C E C H A N N E L ( V . 1 1 )

C o

n n e c t o r : R J 4 5 8 - P I N

C a b l e : U W M K 3 0 7 7

- 4 8 V D C

6 4 k b / s

G . 7 0 3

2 M b / s

W a y s i d e

S V C E

E x t . 1

P h o n e

6 4 k b / s

V . 1 1

2 M H z

S y n c .

S V C E

E x t . 2

1 0 B a s e T

L A N


C A L L

A L M & A U X

L C T

N I 2

N I 1

C R I T I C A L

M A J O R

M I N O R

W A R N I N G

P O W E R 2

1 5 5 M b / s L I N E

1

2 M

b i t / s W A Y S I D E C H A N N E L

C o

n n e c t o r : R J 4 5 8 - P I N

C a

b l e : 8 7 W 5 0 9 7 - 2 A , 1 0 m p a t c h c a b l e

2 M

H z S Y N C

( L a t e r r e l e a s e )


O f f t h e s h e l f s t a n d

a r d


S E R V I C E C H A N N E L E X T E N S I O N 1

C o n n e c t o r : R J - 4 5 8 - P I N

C a b l e : 8 7 W 5 0 9 7 - 1 A


T E N S I O N 2

C o n n e c t o r : R J - 4 5 8 - P I N

C a b l e : 8 7 W 5 0 9 7 - 1 A



R e f . F i g . X - 6

R X D I R . A

R X D I R . B

T X D I R . A

T X D I R . B


S l o t f o r o p t i o n a l

E x t e n s i o n B o a r d

P O W E R 1

2

P W R

N E T W O R K I N T E R F A C E ( R S 4 8 5 )

C o n n e c t o r : D - S U B 9 - P I N

F E M A L E

C a b l e : U W M K 3 0 7 8 , U W M

K 3 0 7 9



358 B4008 Rev. M

CityLink

O D U

- 4 8 V D C

6 4 k b / s

G . 7 0 3

2 M b / s

W a y s i d e

S V C E

E x t . 1

P h o n e

6 4 k b / s

V . 1 1

2 M H z

S y n c .

S V C E

E x t . 2

1 0 B a s e T

L A N


C A L L

A L M & A U X

L C T

N I 2

N I 1

P O W E R

1 5 5 M b / s L I N E

P W R

1 0 B a s e - T / 1 0 0 B a s e - T X

T 1 / E 1

S I G N A L

S I G N A L

C R I T I C A L

M A J O R

M I N O R

W A R N I N G

P O

W E R

C o

n n e c t o r : P O W E R D - S U B 2 - P I N

C a

b l e : U W M K 5 0 5 1

P H O N E

N o t u s e d f o r C i t y L i n k F a s t E

t h e r n e t


N o t u s e

d f o r C i t y L i n k F a s t E t h e r n e t

N E T W O R K I N T E R F A C E ( R

S 4 8 5 )

N o t u s e d f o r C i t y L i n k F a s t E t h

e r n e t

6 4 k b i t / s S E R V I C E C H A N N E L ( G . 7 0 3

)

C

o n n e c t o r : R J 4 5 8 - P I N

C

a b l e : U W M K 3 0 7 7

L O C A L C R A F T T E R M I N A L ( R S 2 3

2 )

C o n n e c t o r : D - S U B 9 - P I N M A L E

C a b l e : U W M K 3 1 2 3

S A

F E T Y

G R O U N D

O D U I N T E R F A C E

N - T Y P E F E M A L E

A L A R M & A U X I L L A

R Y F U N C T I O N S

C o n n e c t o r : D - S U B

2 5 - P I N F E M A L E

C a b l e : U W M K 3 0 7 6

6 4

k b i t / s S E R V I C E C H A N N E L ( V . 1 1 )

C o n n e c t o r : R J 4 5 8 - P I N

C a b l e : U W M K 3 0 7 7

2 M b i t / s W A Y S I D E C H A N N E L

C

o n n e c t o r : R J 4 5 8 - P I N

C

a b l e : 8 7 W 5 0 9 7 - 2 A , 1 0 m p a t c h c a b l e

2 M H z S Y N C

( L

a t e r r e l e a s e )


O f f t h e s h e l f s t a n d a r d


S E R V I C E C H A N N E L E X T E N S I O N 1

N o t u s e d f o r C i t y L i n k F a s t E t h e r n e t


T E N S I O N 2

N o t u s e d f o r C i t y L i n k F a s t E

t h e r n e t


N o t u s e d f o r C i t y L i n k

F a s t E t h e r n e t



R e f . F i g . X - 6

1 0 B a s e - T / 1 0 0 B a s e

- T X E t h e r n e t

O f f t h e s h e l f s h i e l d

e d t w i s t e d

p a i r e t h e r n e t c a b l e

T R I B U T A R Y T 1 / E 1 I N T E R F A C E ( 2 M b i t / s o r 1 . 5 M b i t / s )

C o n n e c t o r : R J 4 5 8 - P I N

C a b l e : 8 7 W 5 0 9 7

- 2 A , 1 0 m p a t c h c a b l e

Figure X-3 CityLink Fast Ethernet IDU



B4008 Rev. M 359

Appendices

INP

G.703

OUT

INP

MM Fiber

INP

SM Fiber

OUT INP

CAT-5 UTP

INP

Figure X-4 Optional Line Interface Plug-in Boards

155 Mbit/s STM-1

G.703, 75ΩΩΩΩΩ

Connector : DIN47297, 1.0/2.3mm

Cable : UWMH3080

155 Mbit/s STM-1

CAT-5, UTP

Connector: RJ45 (FCC-8 compl.), 8-pin Connector

Cable alt.1: 87W5111-CAT5E02S, 2m straight patch cable

Cable alt.2: 87W5111-CAT5E02C, 2m crossed patch cable

1310 nm SMF and 1550 nm SMF

Optical Interface

Connector: LC

Cable: 87W5080-SCxx/LCxx/FCxx

1310 nm MMF

Optical Interface

Connector: MT-RJ

Cable: 87W5078-SCxx/MTRJxx/STxx/FCxx



360 B4008 Rev. M

CityLink

Figure X-5 Optional Extension Boards Boards

Optional Extension Boards

TRIBUTARY

OUT IN OUT IN OUT IN

DS1-0 DS3/E3-1 DS3/E3-2 DS3/E3-3SIGNAL

0

1

23

Line ExtensionSTM1 / STS-3 (155Mb/s)

G.703

INP OUT

21x2Mbit/s Extension Board:

STM1 Extension Board:

DS3/E3 Extension Board:



B4008 Rev. M 361

Appendices

Pin no. 8Pin no. 1

Pin no. 8 Pin no. 1

Power Connector

0V STATION GROUND

-48VDC

Figure X-6 IDU Power Connector Pinout

RJ-45 Connectors

With reference to Figure X-7, several connector pin-outs will be described.

Note that the upper connector pins are reversed with respect to the lower

connector pins, i.e. the lower plug is “mirrored”. Refer to Figure X-1-3 for

location of 2-by-4 port RJ-45.

IN DOOR UNIT'SFRONT VIEW

Figure X-7 RJ-45 (P5001A-D) connector detail.

A B C D

U

L

IN DOOR UNIT'S

FRONT VIEW

(FEMALE )

(MALE )



362 B4008 Rev. M

CityLink

64kbit/s G.703 Jack, RJ-45 Connector

Pin. no: Function:

1UA TxD- (Neg. Tx. data)2UA TxD+ (Pos. Tx. data)

3UA TxC+ (Pos. Tx. clock)4UA TxC- (Neg. Tx. clock)5UA RxD+ (Pos. Rx. data)6UA RxD- (Neg. Rx. data)7UA RxC+ (Pos. Rx. clock)8UA RxC- (Neg. Rx. clock)

Table X-1 64kbit/s G.703 Jack, 8-PIN Pinout

64kbit/s V.11 Jack, RJ-45 Connector

Pin. no: Function:

1LA TxD- (Neg. Tx. data)2LA TxD+ (Pos. Tx. data)3LA TxC- (Neg. Tx. clock)4LA TxC+ (Pos. Tx. clock)

5LA RxD- (Neg. Rx. data)6LA RxD+ (Pos. Rx. data)7LA RxC- (Neg. Rx. clock)8LA RxC+ (Pos. Rx. clock)

Table X-2 64kbit/s V.11 Jack, 8-PIN Pinout

2Mbit/s Wayside Jack, RJ-45 Connector

Pin. no: Function:

1UB IND+ (Pos. Rx. data)2UB IND- (Neg. Rx. data)3UB shield4UB OUTD+ (Pos. Tx. data)5UB OUTD- (Neg. Tx data)6UB shield7UB Not Connected

8UB Not Connected

Table X-3 2Mbit/s Wayside Jack, 8-PIN Pinout



B4008 Rev. M 363

Appendices

2.048 MHz SYNC Jack, RJ-45 Connector

Pin. no: Function:

1LB INP+ (Pos. Rx. pulse)2LB INP- (Neg. Rx. pulse)

3LB shield4LB OUTP+ (Pos. Tx. pulse)5LB OUTP- (Neg. Tx pulse)6LB shield7LB Not Connected8LB Not Connected

Table X-4 2.048 MHz SYNC Jack, 8-PIN Pinout

Service Channel Extension 1 and 2 Jacks, RJ-45 Connector

Pin. no: Function:

1UC OE1_INP_A2UC OE1_INP_B3UC OE1_OUT_A4UC OE1_OUT_B5UC CALL_INP

6UC CALL_OUT7UC CTRL_INP8UC CTRL_OUT

Table X-5 Service Channel Extension 1 Jack, 8-PIN Pinout

Pin. no: Function:

1LC OE2_INP_A2LC OE2_INP_B3LC OE2_OUT_A4LC OE2_OUT_B5LC CALL_INP6LC CALL_OUT7LC CTRL_INP8LC CTRL_OUT

Table X-6 Service Channel Extension 2 Jack, 8-PIN Pinout



364 B4008 Rev. M

CityLink

Service Phone Jack, RJ-45 Connector

Pin. no: Function:

1UD Not Connected2UD Not Connected

3UD TELA4UD MIC+5UD MIC-6UD TELB7UD Not Connected8UD LOOP_OE

Table X-7 Service Phone Handset Connector, 8-PIN Pinout

10Base-T (“TP-LAN”) Jack, RJ-45 Connector (normal)

Pin. no: Function:1LD TPTX+ (Pos. Tx. data)2LD TPTX- (NEG. Tx. data)3LD TPRX+ (Pos. Rx. data)4LD Not Connected5LD Not Connected

6LD TPRX- (Neg. Rx. data)7LD Not Connected8LD Not Connected

Table X-8 10Base-T, 8-PIN Pinout

10Base-T / 100Base-TX Jack, RJ-45 Connector (uplink)

(Used only in Fast Ethernet configuration)

Pin. no: Function:1LD TPRX+ (Pos. Rx. data)2LD TPRX- (NEG. Rx. data)3LD TPTX+ (Pos. Tx. data)4LD Not Connected5LD Not Connected6LD TPTX- (Neg. Tx. data)7LD Not Connected8LD Not Connected

Table X-9 10Base-T / 100Base-TX, 8-PIN Pinout



B4008 Rev. M 365

Appendices

NI1 and NI2, Network Interface Connector Detail

PIN 1PIN 5

PIN 9 PIN 6

Figure X-9 “NI1” and “NI2” D-SUB 9 PIN Pinout

NI1 and NI2 D-SUB Signal Name Signal Description

9-PIN FEMALE

1 RxD- Data Input2 RxD+ Data Input3 GND Signal Ground.

Normally this pin shall

not be connected.4 TxD+ Data Output5 TxD- Data Output6 RxC- Clock Input7 RxC+ Clock Input8 TxC+ Clock Output9 TxC- Clock Output

Table X-10 “NI1” and “NI2” D-SUB 9-PIN Pinout

IDU to HSB Interface Connector

The connector is 68 pin VHDCI receptacle. This is a shielded connector

type and the screen is terminated to chassis ground.

Pos. 35

Pos. 1Pos. 34

Figure X-8 IDU to HSB-IDU Interface Connector



PIN 34 PIN 1

PIN 35



366 B4008 Rev. M

CityLink

ALM & AUX Connector Detail

Figure X-10 “ALM & AUX” D-SUB 25-PIN Pinout

IDU

FRONT

VIEW

PIN 13 PIN 1

PIN 14PIN 25

ALM & AUX D-SUB Signal Name Signal Description

25-PIN FEMALE

1 USER1A Relay output 1A

2 USER1B Relay output 1B

3 USER2A Relay output 2A4 USER2B Relay output 2B





9 ALM1 Alarm input 1 (TTL level)

10 AGND Analog GND*


12 ALM3 Alarm input 3 (TTL level)13 AGND Analog GND*

14 AGND Analog GND*


16 AGND Analog GND*

17 ALM5 Alarm input 5 (relay input)

18 AGND Analog GND*




22 ERRP_V11+ Error pulses (V.11 output)**

23 ERRP_V11- Error pulses (V.11 output)**

24 ERRP_OPEN_COL Error pulses

open collector output

25 ERRP_OPTO Error pulses opto

coupler driver output

Table X-11 “ALM & AUX” D-SUB 15-PIN Female Pinout

* Analog GND is floating relative scussi GND.

** Selectable from NEW-NMS: B1, B2 or Trellis decoder.

See Section VII Ch.4.4.5.



B4008 Rev. M 367

Appendices

IDUFRONT

VIEW

PIN 5PIN 1

PIN 6 PIN 9

LCT Connector Detail

Figure X-11 “LCT” D-SUB 9 PIN male, Pinout

LCT D-SUB Signal Name Signal Description

9-PIN MALE

1 NC Not Connected

2 RxD City Link Data Input3 TxD City Link Data Output4 - Internally connected to pin 65 GND Signal ground6 - Internally connected to pin 47 - Internally connected to pin 88 - Internally connected to pin 79 NC Not connected

Table X-12 “LCT” D-SUB 9-PIN Pinout



368 B4008 Rev. M

CityLink

1D

1A 6A

6D

Figure X-13 21x2Mbit/s Connector Detail

21x2Mbit/s Extension board G.703 Connector Details

Figures X-12 and X-13 shows the 4 connectors J1001 to J1004 and their

pinout. For location of the 4 connectors on the IDU; see Figur X-5.

For configuration of 21x 2.048 Mb/s input- and output- signals in connec-

tors and cables , see Table X-13.

Figure X-12 The 21x2 Mb/s interface connectors from left to right,

IDU front view.

J1001 J1002 J1003 J1004

IDUFRONTVIEW



B4008 Rev. M 369

Appendices

• Input, A / Output, A, refers to the positive pulse of the signal.

• Input, B / Output, B, refers to the negative pulse of the signal.

Connector J1001 Connector J1002 Connector J1003 Connector J1004Pin no

in

connec

-tor

Colour

code of

pairs in

cable2 Mb/s

Ch. No

Signal 2 Mb/s

Ch. No

Signal 2 Mb/s

Ch. No

Signal 2 Mb/s

Ch. No

Signal

1A Ch.1 Input, A Ch.7 Input, A Ch.13 Input, A Ch.19 Input, A

1B

White /

Blue Ch.1 Input, B Ch.7 Input, B Ch.13 Input, B Ch.19 Input, B

1C Ch.1 Output, A Ch.7 Output, A Ch.13 Output, A Ch.19 Output, A1D White /Orange Ch.1 Output, B Ch.7 Output, B Ch.13 Output, B Ch.19 Output, B


2B

White /Green Ch.2 Input, B Ch.8 Input, B Ch.14 Input, B Ch.20 Input, B

2C Ch.2 Output, A Ch.8 Output, A Ch.14 Output, A Ch.20 Output, A

2D

White /Brown Ch.2 Output, B Ch.8 Output, B Ch.14 Output, B Ch.20 Output, B


3B

Red /

Blue Ch.3 Input, B Ch.9 Input, B Ch.15 Input, B Ch.21 Input, B

3C Ch.3 Output, A Ch.9 Output, A Ch.15 Output, A Ch.21 Output, A

3D

Red /

Orange Ch.3 Output, B Ch.9 Output, B Ch.15 Output, B Ch.21 Output, B

4A Ch.4 Input, A Ch.10 Input, A Ch.16 Input, A N.c.

4B

Red /

Green Ch.4 Input, B Ch.10 Input, B Ch.16 Input, B N.c.4C Ch.4 Output, A Ch.10 Output, A Ch.16 Output, A N.c.

4D

Red /

Brown Ch.4 Output, B Ch.10 Output, B Ch.16 Output, B N.c.


5B

Black /

Blue Ch.5 Input, B Ch.11 Input, B Ch.17 Input, B N.c.5C Ch.5 Output, A Ch.11 Output, A Ch.17 Output, A N.c.

5D

Black /

Orange Ch.5 Output, B Ch.11 Output, B Ch.17 Output, B N.c.


6B

Black/

Green Ch.6 Input, B Ch.12 Input, B Ch.18 Input, B N.c.6C Ch.6 Output, A Ch.12 Output, A Ch.18 Output, A N.c.

6D

Black /

Brown Ch.6 Output, B Ch.12 Output, B Ch.18 Output, B N.c.

Table X-13 Configuration of 21x 2Mbit/s input- and output- signals in

connectors and cables

ADM STM-1 Extension Board Connectors

The type and configuration of connectors used for the 155 Mbit/s customer

line interface on the Extension Board are the same as used for the G.703 CMI

encoded 155 Mb/s customer line interface on the main board in the IDU.



370 B4008 Rev. M

CityLink

Appendix II: ODU Interface Description

ODU/IDU Interface

N-connector female for: Transmit and Receive IF,

Modem/Transceiver communication and power supply.

Branching / Antenna Interface

PBR320 waveguide (38GHz).

PBR220 waveguide (18GHz, 23GHz and 26GHz).

PDR120 waveguide (for 13GHz).

PBR140 waveguide (for 15GHz).

PDR84 waveguide (for 7GHz and 8GHz).

Grounding cable for Branching Unit.



B4008 Rev. M 371

Appendices

Appendix III:Alarm List & Alarm Description

Alarm Name Description Id Severity

BASEBAND

LOS Loss Of Signal:- Optical or electrical CMI

1000 MAJOR

LOF Loss of Frame 1001 MAJOR

MS-AIS Alarm indication signal detected.MS termination only

1002 WARNING

MS-AIS-INS Alarm indication signal is inserted. 1003 MAJOR

MS-RDI Remote defect indicator detected.MS termination only

1004 WARNING

2M-WAYSIDE-INP 2Mbit wayside input is missing. 1005 MINOR

2M-WAYSIDE-AIS-INP 2Mbit wayside input AIS detected. 1006 WARNING

TRELLIS-PLL Indicates that the Trellis coder is out of lock.(CNF35CAsic)

1007 CRITICAL

RT-PLL The Sorp 38,88 MHz PLL is out of lock. 1008 CRITICAL

2M-SYNC Selected synchronisation for Line Transmit direction ismissing.

1009 MINOR

RS-TRACE-MISMATCH Mismatch between configured string and received string 1010 MAJOR

LOC Loss of clock (SORP) 1011 CRITICAL

BASEBANDDIRECTION RADIO TO LINE

LT-PLL The Line Transmit 155MHz PLL is out of lock. 1100 CRITICAL

2M-WAYSIDE-OUTP-AIS AIS is detected on the Wayside traffic output. 1101 WARNING

HBER Indicator for BER > 1e-3 1102 MAJOR

LBER Indicator for BER > 1e-6 1103 MINOR

EW-BER Indicator for BER > 1e-10 1104 WARNING

RF-ID Wrong RF-ID received compared to configuration. 1105 MAJOR

MODULATOR

IF-MOD Loss of IF 350MHz 1200 CRITICAL

DEMODULATOR

IF-DEM Loss of INCOMING 140MHz. 1300 CRITICAL

OPTICAL INTERFACE

TX-OUT The output power has increased 2dB, or the analogemeasurement of PO_MON is outside predefined limits

1400 CRITICAL

LASER-OFF The laser is off. It could be manual shutdown 1401 WARNINGBIAS The laser bias is out of limits. Sign of age and degradation 1402 WARNING

TRANSCEIVER

IF-INP No IF into transceiver 1500 CRITICAL

RF-OUT The output power is low 1501 MAJOR

LOS-RF-INPUT No signal into receiver. 1502 MAJOR

RF-INPUT-WARNING The RF level is either above the upward fading thresholdor The RF level is below the down fading threshold.

1504 WARNING

LO Local Oscillator is out of lock. 1505 MAJOR

UNIT-ALM The transceiver is not responding 1506 MAJOR

ATPC The regulation loop for the ATPC is not working. Softwaregenerated alarm based on alarm condition on local LOFon Rx and remote LOF on Rx .

1507 MINOR

RF-MUTE The RF transmitter is muted. 1508 WARNING

LOOPING-IF-EN The transceiver looping on IF is enabled 1509 WARNING

LOOPING-RF-EN The transceiver on RF is enabled.(If near-end and far end depends on the node wherealarm is reported)

1510 WARNING

MISSING_LO_SYNCHRONIZATION XPIC LO synch missing 1511 CRITICAL

LO-TUNING-WARNING The LO needs to be tuned 1512 WARNING

HIGH_TEMP_POWER_TRANSISTOR 1513 WARNING

RF_RX_LOW 1514 MAJOR

RF_RX_HIGH 1515 MAJOR

NO_CALIBRATION_DATA No calibration data 1516 MAJOR

HSB_CABLE_BREAK The cable between the ODUs is broken. This will causethe switch to perform the TX-switching.

1517 MAJOR

RF_TX_LOW 1518 MAJOR

RF_TX_HIGH 1519 MAJOR

IF_TX_LOW 1520 MAJOR

IF_TX_HIGH 1521 MAJOR

POWER_15 1522 WARNING

POWER_NEG15 1523 WARNING





372 B4008 Rev. M

CityLink


SYNTH_HEADER 1526 MAJOR

SHF_LO 1527 MAJOR

UHF_TX_LO 1528 MAJOR

UHF_RX_LO 1529 MAJOR

DUPLEX_LO 1530 MAJOR

VHF_LO 1531 MAJOR

TX_SWITCH_MAN 1532 WARNING

OTHER ALM

MEN-AT-WORK Software generated. Operator set men at work beforedoing repairs.

2000 WARNING

DROP-IN+48V The battery supply voltage is dropped below acceptablelimit

2001 WARNING

BELOW+3.3V Voltage from the DC-DC converter below limit 2002 WARNING

BELOW+5V Voltage from the DC-DC converter below limit 2003 WARNING

BELOW-5V Voltage from the DC-DC converter below limit 2005 WARNING

OVER-CURRENT Detects short current on ODU cable. 2006 MAJOR

WAYSIDE-LOOP FE Wayside looping Far End 2007 WARNING

WAYSIDE-LOOP NE Wayside looping Near End 2008 WARNING

PRBS-INSERTED PRBS inserted in wayside 2009 WARNING

LOOPING_EN Looping enabled 2010 WARNING

EVENT-LOG-EXC-LIMIT Event log has exceeded the capacity threshold 2011 WARNING

DOWNLOAD-IN-PROGRESS Download of software is under progress. 2012 WARNING

NEED_FREQUENCY A RF unit need to be configured with Tx and Rxfrequency.

2013 MAJOR

SECURITY-LOG-EXC-LIMIT Security log has exceeded the capacity threshold 2014 WARNING

64K-LOOPING-1 64 kb channel looping Channel1 2015 WARNING

64K-LOOPING-2 64 kb channel looping Channel2 2016 WARNING

RTC-LOW BATTERY The battery that powers the Real Time clock is low 2017 WARNING/ MINOR on

NL2000




BELOW-15V Voltage from the DC-DC converter below limit 2024 WARNING

MISSING-CALIBRATION-DATA Modem or transceiver are missing their calibration data in

flash

2032 MAJOR

FAN-ALARM 2034 WARNING

DEFAULT_SYSTEM_PARAMETERS No system configuration stored in NV config, using default(stm1,128TCM,28kHz)

2035 CRITICAL

DEFAULT_ANALOGE_PARAMETERS No analoge configuration stored in flash, using predefineddefaults.

2036 MAJOR

FAN2-ALARM 2037 WARNING

HSB-RELAY IDUswitch/Transceiver relay mismatch 2200 CRITICAL

IDUA-ACTIVE Idu A is active in receiving direction 2201 INFO

IDUB-ACTIVE Idu B is active in receiving direction 2202 INFO

HSB-MANUAL The iduswitch is operated manually 2203 WARNING

CHANNEL-ACTIVE This ODU is active 2216 INFO

NEED-SW Board needs SW 2221 MAJOR

BOOT-MONITOR-IN-USE The transceiver is in boot monitor mode 2224 WARNINGBOOT-HW-ERROR-DETECTED Errors detected by boot code when startup. Reported toapp. code

2225 MINOR

IDU_A_NEEDS_SW Reported from the IDU A 2226 WARNING

IDU_B_NEEDS_SW Reported from IDU B 2227 WARNING

HDLC_LOC_A The IDU switch has no RX-clock on port A 2228 MAJOR

HDLC_LOC_B The IDU switch has no RX-clock on port B 2229 MAJOR

HDLC_LOC The IDU(either A or B) has no RX-clock 2230 MAJOR

DROP-IN-48V-A The IDU switch power source 1 has a drop 2231 MAJOR

DROP-IN-48V-B The IDU switch power source 2 has a drop 2232 MAJOR

AUXILIARY ALARMS

EXTERN-ALARM-1 Multipurpose port. Configured asAlarm Output, Alarm Input or Remote Control.External alarm reported if port configured as alarm input.Alarm name configurable from management system.

2500 WARNING

EXTERN-ALARM-2 ref External alarm 1 2501 WARNING





B4008 Rev. M 373

Appendices






OUTPUT-ALARM-1 Output alarm reported if auxilary output port configured asalarm output.

2550 INFO

OUTPUT-ALARM-2 ref Output alarm 1 2551 INFO



SEVERITY ALARMS For alarm output function

CRITICAL-ALARM If any alarms with severity set to critical, this alarm israised. This can be combined in the alarm outputexpression.

2600 NA

MAJOR-ALARM If any alarms with severity set to major, this alarm israised. This can be combined in the alarm outputexpression.

2601 NA

MINOR-ALARM If any alarms with severity set to minor, this alarm israised. This can be combined in the alarm outputexpression.

2602 NA

WARNING-ALARM If any alarms with severity set to warning, this alarm israised. This can be combined in the alarm output

expression.

2603 NA

PERFORMANCE ALARMS All software generated

G826-THRESHOLD-15MIN-B1 If the current 15 minute period exceeds the set thresholdfor B1, this alarm is set(period 1). After a whole period hasexpired without exceeding the alarm threshold(period 2),the alarm will be cleared when the next periodstarts(period 3).

3000 WARNING

G826-THRESHOLD-15MIN-B2 If the current 15 minute period exceeds the set thresholdfor B2, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1 for method of clearing. Only for MS termination.

3001 WARNING

G826-THRESHOLD-15MIN-REI If the current 15 minute period exceeds the set thresholdfor REI, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1 for method of clearing. Only for MS termination.

3002 WARNING

G826-THRESHOLD-24Hour-B1 If the current 24 hour period exceeds the set threshold forB1, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1

for method of clearing.

3003 WARNING

G826-THRESHOLD-24HOUR-B2 If the current 24 hour period exceeds the set threshold forB2, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1for method of clearing. Only for MS termination.

3004 WARNING

G826-THRESHOLD-24HOUR-REI If the current 24 hour period exceeds the set threshold forREI, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1 for method of clearing. Only for MS termination.

3005 WARNING

G826-THRESHOLD-MONTH-B1 If the current month period exceeds the set threshold formonth, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1 for method of clearing.

3006 WARNING

G826-THRESHOLD-MONTH_B2 If the current month period exceeds the set threshold formonth, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1 for method of clearing. Only for MS termination.

3007 WARNING

G826-THRESHOLD-MONTH-REI If the current month period exceeds the set threshold forREI, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1

for method of clearing. Only for MS termination.

3008 WARNING

TRESHOLD-15MIN-OOF If the current 15 minute period exceeds the set thresholdfor OOF, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1 for method of clearing.

3015 WARNING

TRESHOLD-24HOUR-OOF If the current 24 hour period exceeds the set threshold forOOF, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1 for method of clearing.

3016 WARNING

TRESHOLD-MONTH-OOF If the current month period exceeds the set threshold formonth, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1 for method of clearing.

3017 WARNING

HIGHER ORDER POH ALARMS Description

HP-RDI Higher order Path Remote Defect Indicator 5050 WARNING

HP-TIM Higher order Path Trace Identifier Mismatch 5054 MAJOR



CityLink

Fast Ethernet AlarmsAlarm Name Description Id Severity

FTP_USER_LOGGED_IN FTP user logged in 32768 NORMALILLEGAL_DATE_OR_TIME Illegal Date or Time 32770 WARNINGIDU_TEMPERATURE1_HIGH SU Temperature 1 (CPU) exceeded high

limitWARNING32771

IDU_TEMPERATURE2_HIGH SU Temperature 2 (DC/DC) exceeded high limit 32772 WARNINGFAN1_MANUAL_STOP SU Fan 1 is set in manual stop 32773 WARNINGFAN2_MANUAL_STOP SU Fan 2 is set in manual stop 32774 WARNING

FAN1_NOT_RUNNING SU Fan 1 is not running 32775 MAJORFAN2_NOT_RUNNING SU Fan 2 is not running 32776 MAJORI2C_BUS_FAILURE SU internal problem at I2C bus 32777 WARNINGBASEBAND_DEVICE_INIT_FAILURE There was a hardware error in the baseband module

during startup of the IDU32778 MAJOR

MODEM_DEVICE_INIT_FAILURE There was a hardware error in the modem moduleduring startup of the IDU

32779 MAJOR

EEB_DEVICE_INIT_FAILURE There was a hardware error in the ethernet extensionboard module during startup of the IDU

32780 MAJOR

COMMAND_LINE_INIT_FAILURE There was a hardware error in the command lineinterface module during startup of the IDU

32781 WARNING

CONSOLE_USER_LOGGED_IN A user is currently using the command-line interfaceshell on the IDU via the LCT port

32782 NORMAL

TELNET_USER_LOGGED_IN A user is currently using the command-l ine interfaceshell on the IDU via the telnet

32783 NORMAL

ETHERNET_PORT_1 EEB Port 1 link lost. 32784 NORMALETHERNET_PORT_2 EEB Port 2 link lost. 32785 NORMALETHERNET_PORT_3 EEB Port 3 link lost. 32786 NORMALETHERNET_PORT_4 EEB Port 4 link lost. 32787 NORMALLOS_2MBIT_PORT_1 EEB LOS port 1. 32788 NORMALLOS_2MBIT_PORT_2 EEB LOS port 2. 32789 NORMALLOS_2MBIT_PORT_3 EEB LOS port 3. 32790 NORMALLOS_2MBIT_PORT_4 EEB LOS port 4. 32791 NORMAL AIS_INPUT_2MBIT_PORT_1 EEB AIS input port 1. 32792 WARNING AIS_INPUT_2MBIT_PORT_2 EEB AIS input port 2. 32793 WARNING AIS_INPUT_2MBIT_PORT_3 EEB AIS input port 3. 32794 WARNING AIS_INPUT_2MBIT_PORT_4 EEB AIS input port 4. 32795 WARNING AIS_OUTPUT_2MBIT_PORT_1 EEB AIS output port 1. 32796 WARNING AIS_OUTPUT_2MBIT_PORT_2 EEB AIS output port 2. 32797 WARNING AIS_OUTPUT_2MBIT_PORT_3 EEB AIS output port 3. 32798 WARNING

AIS_OUTPUT_2MBIT_PORT_4 EEB AIS output port 4. 32799 WARNING AIS_INSERT_2MBIT_PORT_1_RX EEB AIS insert port 1 input. 32800 WARNING AIS_INSERT_2MBIT_PORT_2_RX EEB AIS insert port 2 input. 32801 WARNING AIS_INSERT_2MBIT_PORT_3_RX EEB AIS insert port 3 input. 32802 WARNING AIS_INSERT_2MBIT_PORT_4_RX EEB AIS insert port 4 input. 32803 WARNINGLOC_RT Loss of clock in the RT module of the baseband unit

(SORP)32804 CRITICAL

LOC_RR Loss of clock in the RR module of the baseband unit(SORP)

32805 CRITICAL

LOC_LT Loss of clock in the LT module of the baseband unit(SORP)

32806 CRITICAL

LOC_LR Loss of clock in the LR module of the baseband unit(SORP)

32807 CRITICAL

LOS_RR Loss of signal on radio receive (RR) 32808 MAJORLOF_RR Loss of frame on radio receive (RR) 32809 MAJORMS-AIS_RR Alarm indication signal detected on radio receive (RR) 32810 WARNINGMS-AIS_INSERT_RR Alarm indication signal is inserted on radio receive (RR) 32811 MAJORMS-RDI_RR Remote defect indicator detected on radio receive (RR) 32812 WARNINGLOS_LR Loss of signal on line receive (LR): - optical or electrical

CMI.32813 MAJOR

LOF_LR Loss of frame on line receive (LR) 32814 MAJORMS-AIS_LR Alarm indication signal detected on line receive (LR) 32815 WARNINGMS-AIS_INSERT_LR Alarm indication signal is inserted on line receive (LR) 32816 WARNINGMS-RDI_LR Remote defect indicator detected on line receive (LR) 32817 WARNINGMS-AIS_INSERT_RT Alarm indication signal is inserted on radio transmit

(RT)32818 MAJOR

MS-AIS_INSERT_LT Alarm indication signal is inserted on line transmit (LT) 32819 MAJORRS-TRACE-MISMATCH RR Mismatch between configured string and received string 32820 MAJOR

nera citylink - user manual_2.pdf

Documents