NERA CityLink - User Manual_2.pdf

User Manual CityLink B4008 Rev. M

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

© Nera Networks AS

CityLink This section applies only to CE marked equipment

0889 WARNING: Use of this equipment requires a separate license to be applied for by the operator.

DECLARATION OF CONFORMITY (INFORMAL) English Finnish Dutch

French

Swedish Danish German

Hereby, Nera Networks AS, declares that this CityLink is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC. Nera Networks AS vakuuttaa täten että CityLink tyyppinen laite on direktiivin 1999/5/EY oleellisten vaatimusten ja sitä koskevien direktiivin muiden ehtojen mukainen. 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/EG Bij deze verklaart Nera Networks AS dat deze CityLink voldoet aan de essentiële eisen en aan de overige relevante bepalingen van Richtlijn 1999/5/EC. Par la présente Nera Networks AS déclare que l’appareil CityLink est conforme aux exigences 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 exigences essentielles et aux autres dispositions de la directive 1999/5/CE qui lui sont applicables. 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 direktiv 1999/5/EG. Undertegnede Nera Networks AS erklærer herved, at følgende udstyr CityLink overholder de væsentlige krav og øvrige relevante krav i direktiv 1999/5/EF Hiermit erklärt Nera Networks AS, dass sich dieser CityLink in Übereinstimmung mit den grundlegenden Anforderungen und den anderen relevanten Vorschriften der Richtlinie 1999/5/EG befindet“. (BMWi) Hiermit erklärt Nera Networks AS die Übereinstimmung des Gerätes CityLink mit den grundlegenden Anforderungen und den anderen relevanten Festlegungen der Richtlinie 1999/5/EG. (Wien)

Refer to Declaration of Conformity for further details.

2

B4008 Rev. M

CityLink

B4008 Rev. M

3

CityLink

4

B4008 Rev. M

CityLink

B4008 Rev. M

5

CityLink

6

B4008 Rev. M

CityLink

WARNING!

WARNING!

ˆ DO NOT remove or insert the Transmitter Unit with DC power on.

This equipment contains components which are sensitive to "ESD" (Electro Static Discharge).

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

It is therefore essential that whenever disassembling the equipment and/or handling PC boards, special precautions to avoid ESD have to be made.

CAUTION! Exposure to strong high frequency electromagnetic fields may cause thermal damage to personnel. The eye (Cornea and lens) is easily exposed.

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.

CAUTION!

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. CLASS 1 LASER PRODUCT

In the antennas and directly in front of them the RF intensity normally will exceed the danger level, within limited portions of space.

IEC825-2: 1993

Dangerous radiation may be found in the neighbourhood of open waveguide flanges or horns where the power is radiated into space.

Use of controls or adjustments or performance of procedures other than those specified herein may result in hazardous radiation exposure.

To avoid dangerous radiation the following precautions must be taken:

The Optical Interface must only be serviced by qualified personnel, who are aware of the hazards involved to repair Laser products.

ˆ During work within and close to the front of 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 waveguide unless you are absolutely sure that the power is turned off.

B4008 Rev. M

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 disconnected from the STM-1 input. ˆ When the cable is reconnected it must be connected to the STM-1 input before it is connected to the STM-1 output.

7

CityLink

List of Revisions

8

Rev.

Date

What is changed

C D E

01-10-05 01-12-18 02-02-28

F

02-05-07

G

02-09-18

H

02-10-07

I J

02-12-19

K

03-05-23

L

03-11-25

ODU Type II Installation introduced ODU Type III Installation introduced 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 interfaces in Appendix 1 Fast Ethernet introduced Section VII; New subchapter 5.1.5 Reconfiguring a 1+0 IDU for use in Hot StandBy Configuration 21x2Mbit/s (CityLink ADM) introduced. Section VIII: Updated bitmaps in Ch. 16.6 and 16.8. Frequency tuning of 13GHz Transceiver included (Section II Chapter 5.0). Not used Section V: New chapter 4.0 Installation of 21x2Mbit/s Tributary Unit Section II: Chapter 5.0; new frequency (Table II-5) Installation of ODU Type I on Type III suspension introduced Section IV: New subchapter: Mounting the transceiver (without antenna) to a column. Section VIII: Changed bitmaps in Ch. 16.1, 16.2, 16.6 and 16.8, Changes in Ch. 8.9.1 and 8.9.2. New commands included in Ch. 3.0 and 4.0. Section X: New alarms in Alarm list DMD IDU introduced. ADM STM-1 and DS3/E3 ext.boards introduced . New optical interfaces (2NYD5392A and 2NYD5368A) 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

CityLink

Table of Contents SECTION I Equipment Description .................. 21 1.0

Introduction ................................................................. 22

2.0

IDU ................................................................................ 2.1 IDU Description ................................................... 2.2 Hot Standby IDU Description............................... 2.3 Line Interface Boards .......................................... 2.4 Service Telephone .............................................. 2.5 21x2Mbit/s Extension Board (option) ................... 2.6 ADM STM-1 (X-Connect) Extension Board (option) 2.6 3xDS3/E3 and DS1 Extension Board (option) .... 2.6 Ethernet Extension Board (CityLink Fast Ethernet)

24 24 26 28 28 30 30 32 33

3.0

ODU .............................................................................. 3.1 ODU Type I Description ...................................... 3.2 ODU Type II Description ..................................... 3.3 ODU Type III Description .....................................

34 34 36 38

4.0

Management ................................................................ 40

5.0

System Configurations ............................................... 5.1 1+0Configuration ................................................. 5.2 Hot Standby Configuration .................................. 5.3 1+1 Frequency Diversity ..................................... 5.4 Hot Standby Configuration – Dual Antenna ......... 5.5 Hot Standby Configuration – Dual Baseband ...... 5.6 2+0 Configuration ................................................ 5.7 Space Diversity ................................................... 5.8 Hybrid Space Diversity ........................................ 5.9 Radio Terminal Configurations ............................ 5.10 Radio Repeater Configurations ........................... 5.11 Radio Channel Identification ................................

B4008 Rev. M

40 41 42 42 43 44 45 46 46 48 48 48

9

CityLink

SECTION II Installation of ODU Type I and Antenna ................. 49 1.0

General ........................................................................ 1.1 Packing ............................................................... 1.2 Marking ................................................................ 1.3 Transportation ..................................................... 1.4 Radio Equipment Inventory Check ...................... 1.5 Preparation for Installation ................................... 1.6 Handling & Storage .............................................

50 50 50 50 51 51 51

2.0

Installation Equipment required ................................ 2.1 Tools ................................................................... 2.1.1 Tools for Antenna Installation .............................. 2.1.2 Tools for IDU- ODU Cable /Connector Mounting. 2.2 Equipment external to the Radio Equipment .......

52 52 52 52 53

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 ..... 3.1.2 Mounting the Antenna to the Suspension ............ 3.1.3 Mounting the Branching Support Bracket ............ 3.1.4 Mounting the Rear Travers .................................. 3.1.5 Mounting the Suspension Support Bracket ......... 3.1.6 Mounting the Bend on the Branching Unit ........... 3.1.7 Installation of the Branching Unit ........................ 3.1.8 Attachment of the Sunshield Support .................. 3.1.9 Installation of the Flexible Waveguide ................ 3.1.10 Installation of the Sunshield ................................ 3.1.11 Mounting the Suspension/Antenna to a Column or a Wall ............................................ 3.1.12 Mounting the ODU to the Antenna Assembly ..... 3.1.13 Pole Mount ......................................................... 3.2 Installation of 1.2m Antenna ............................... 3.2.1 Assembly of Branching Support Bracket ............ 3.2.3 Installation of Branching Unit, Sun-shield and Flexible Waveguide ....................

54 54 54 55 56 57 57 58 59 59 60 61

4.0 10

62 65 67 68 68 69

ODU / Antenna Installation, Hot Standby Equipment and 2+0 Equipment ........... 70 B4008 Rev. M

CityLink 4.1 4.1.1

0.45m and 0.6m Antenna ................................ 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 . 4.1.1.2 Mounting the Branching Support Bracket ........ 4.1.1.3 Mounting the Rear Travers, Mounting the Suspension Support Bracket and Mounting the Feed on the Branching Unit ....................... 4.1.1.4 Installation of the HSB Branching Unit ............. 4.1.1.5 Installation of the Flexible Waveguide ............. 4.1.1.6 Installation of the Sunshield Support Bracket .. 4.1.1.7 Installation of the Sunshield............................. 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 .. 4.1.1.10 Pole Mount ...................................................... 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 Suspension . 4.1.2.2 Mounting the Branching Support Bracket, the Rear Travers, the Suspension Support Bracket and the Feed on the Branching Units ................ 4.1.2.3 Installation of the Branching Units ................... 4.1.2.4 Installation of the Flexible Waveguide ............. 4.1.2.5 Installation of the Sunshield............................. 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 .. 4.1.2.9 Pole Mount ...................................................... 4.2 1.2m Antenna .................................................. 4.2.1 Assembly of Branching Support Bracket ........ 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 ......... 4.2.2.2 2+0 Single Frequency Dual Polarization .........

B4008 Rev. M

70 70 70 70 71 71 72 73 73 74 74 75 76 76 76 76 77 78 79 79 80 81 81 82 82 83

11

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 ........................................................................ 1.1 Packing ............................................................... 1.2 Marking ................................................................ 1.3 Transportation ..................................................... 1.4 Radio Equipment Inventory Check ...................... 1.5 Preparation for Installation ................................... 1.6 Handling & Storage .............................................

92 92 92 92 93 93 93

2.0

Installation Equipment required ................................ 2.1 Tools ................................................................... 2.1.1 Tools for Antenna Installation .............................. 2.1.2 Tools for IDU- ODU Cable /Connector Mounting. 2.2 Equipment external to the Radio Equipment .......

94 94 94 94 95

3.0

ODU Installation .......................................................... 96 3.1 Mounting the ODU to the Pole ............................. 96 3.2 Cable Connections.............................................. 97

4.0

Antenna and Waveguide Installation ........................ 4.1 0.6m Antenna ...................................................... 4.2 1.2m Antenna ...................................................... 4.3 2m Antenna ......................................................... 4.4 2.4m .................................................................... 4.5 3m .......................................................................

12

98 98 99 100 101 102

B4008 Rev. M

CityLink

SECTION IV Installation of ODU Type III and Antenna ............ 103 1.0

General ........................................................................ 1.1 Packing ............................................................... 1.2 Marking ................................................................ 1.3 Transportation ..................................................... 1.4 Radio Equipment Inventory Check ...................... 1.5 Preparation for Installation ................................... 1.6 Handling & Storage .............................................

104 104 104 104 105 105 105

2.0

Installation Equipment required ................................ 2.1 Tools ................................................................... 2.1.1 Tools for Antenna Installation and Adjustment .... 2.1.2 Tools for IDU- ODU Cable /Connector Mounting. 2.2 Equipment external to the Radio Equipment .......

106 106 106 106 107

3.0

ODU / Antenna Installation, 1+0 Equipment ............. 3.1 Mounting the Antenna to the Suspension ............ 3.2 Mounting the Sunshield ....................................... 3.3 Mounting the Suspension/Antenna to a Column by using the U-bolts ............................ 3.4 Mounting the Suspension/Antenna to a Column by using the Clamps ........................... 3.5 Mounting the Transceiver (without Antenna) to a Column ............................ 3.6 Mounting the Suspension/Antenna to a Wall ....... 3.7 Mounting the ODU to the Antenna Assembly ......

108 108 109

ODU / Antenna Installation, HSB and 2+0 Equipment 4.1 Preparing the Suspension ................................... 4.2 Mounting the Antenna to the Supension .............. 4.3 Mounting the Hybrid Frame to the Antenna ......... 4.3 Mounting the CityLink III ODUs to the Antenna Assembly ........................................ 4.4 Mounting the Transceiver (without Antenna) to the Column ......................... 4.5 Mounting the Suspension/Antenna to a Wall .......

121 121 122 123

4.0

B4008 Rev. M

110 111 112 117 118

125 126 126 13

CityLink 5.0

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

6.0

Antenna Alignment ...................................................... 6.1 Azimuth and Elevation Adjustment ...................... 6.2 Coarse adjustment.............................................. 6.3 Fine adjustment .................................................. 6.4 Final Control ........................................................ 6.5 Polarisation alignment .........................................

128 128 128 128 129 129

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

General ........................................................................ 1.1 Packing ............................................................... 1.2 Marking ................................................................ 1.3 Transportation ..................................................... 1.4 Radio Equipment Inventory Check ...................... 1.5 Preparation for Installation ................................... 1.6 Handling & Storage .............................................

132 132 132 132 133 133 133

2.0

IDU Installation ............................................................ 134 2.1. Mounting the IDU in an ANSI (19") or an ETSI Rack ... 134 2.2 Cable Installation ................................................. 135

3.0

Hot Standby IDU Installation ...................................... 136 3.1 Mounting the Hot Standby IDUs in a Rack ........... 136 3.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 14

General ........................................................................ 148 B4008 Rev. M

CityLink 1.1 1.2 2.0

Equipment required ............................................. 148 Connections ........................................................ 148

Power on ...................................................................... 2.1 NEW-NMS/NEW-Configurator Startup and connecting to Network Elements ........................ 2.1.1 Starting NEW-NMS/NEW-Configurator with Serial Connection (RS-232/ LCT). ...................... 2.1.2 Starting NEW-NMS/NEW-Configurator with TCP/IP Connection. ............................................ 2.2 Initial configuration ...............................................

148 149 149 150 150

SECTION VII Configuration by NEW Configurator 151 1.0

General ........................................................................ 152

2.0

Element Node .............................................................. 2.1 Element Id ........................................................... 2.2 Available Functions ............................................. 2.3 Notifications ......................................................... 2.4 NE Clock Page .................................................... 2.5 Software Download ............................................. 2.6 Software Versions ...............................................

154 154 156 157 159 160 161

3.0

Transmission Node ..................................................... 3.1 Section Termination ............................................ 3.1.1 Section Termination, SW-version < R2A00 ........ 3.1.2 Section Termination, SW-version ³ R2A00 ......... 3.1.3 SSM - Synchronization Status Message ............. 3.2 Alarm Indication Signal Insert .............................. 3.3 Path Trace ..........................................................

163 163 163 164 172 173 176

4.0

Equipment Node ......................................................... 4.1 Network Routing .................................................. 4.2 IP Routing............................................................ 4.2.1 General Settings ................................................. 4.2.2 Active Routes ......................................................

178 178 181 182 184

B4008 Rev. M

15

CityLink 4.2.3 Static Routes ...................................................... 4.2.4 RIP Interfaces ..................................................... 4.2.5 OSPF Interfaces ................................................. 4.2.6 OSPF Areas ........................................................ 4.3 Communication Ports ......................................... 4.3.1 DCC (Data Communication Channel) ................ 4.3.2 NI (Network Interface) .......................................... 4.3.3 LCT ..................................................................... 4.3.4 Ethernet .............................................................. 4.3.5 IP Settings ........................................................... 4.3.6 IP Tunneling ........................................................ 4.3.7 OSI TP4 Tunneling .............................................. 4.4 Looping ............................................................... 4.4.1 Main Looping ....................................................... 4.4.2 64 Kbit/s Looping ................................................ 4.4.3 2 Mbit/s Wayside Looping ................................... 4.4.4 21x2Mbit/s Looping.............................................. 4.4.5 DS3/E3 Looping .................................................. 4.5 In Door Unit (IDU) ................................................ 4.5.1 IDU Production Data ........................................... 4.5.2 64 kbit/s Channels .............................................. 4.5.3 2 Mbit/s Wayside Channel .................................. 4.5.4 SOH X-Connect .................................................. 4.5.5 Error Pulse Output .............................................. 4.5.6 Auxiliary Output Configuration ............................. 4.5.7 Diagnose ............................................................. 4.5.8 Self Test .............................................................. 4.5.9 BER Thresholds ................................................. 4.5.10 OSI Configuration ................................................ 4.5.11 Laser Control ...................................................... 4.5.12 IDU Replace Unit Wizard .................................... 4.6 Out Door Unit (ODU) ........................................... 4.6.1 Type I ODU ......................................................... 4.6.2 Type II ODU ......................................................... 4.6.3 Type III ODU ........................................................ 4.6.4 Antenna Data ...................................................... 4.6.5 ODU Replace Unit Wizard .................................. 5.0 16

185 186 187 188 189 189 191 193 194 195 196 197 198 198 200 202 205 207 210 210 211 213 215 216 217 219 220 220 222 227 229 230 230 235 247 252 253

CityLink ADM ............................................................... 254 B4008 Rev. M

CityLink 5.1 5.1.1 5.1.2 5.1.3 5.1.4 5.2 5.2.1 5.2.2 5.3 5.3.1 5.3.2 6.0

21x2 Mbit/s Extension Board ............................... Drop or Continue ................................................. PRBS Test - Check ............................................ PRBS Test - Generators ..................................... Production Data - 21x2Mbit/s Extension board ... DS3/E3 Extension Board .................................... DS3/E3 Configuration ......................................... DS3/E3 Frame Structure Configuration .............. ADM STM-1 Extension Board (X-Connect) ......... X-Connect Frame Structure Configuration .......... X-Connect Configuration .....................................

254 254 258 260 262 263 263 265 267 267 268

Hot Standby ................................................................. 6.1 General ............................................................... 6.1.1 Functionality ........................................................ 6.1.2 Element ID .......................................................... 6.1.2 Looping Configuration ......................................... 6.1.3 Hot Standby Configuration .................................. 6.1.4 Hot Standby Switching Criteria ............................ 6.1.4 Reconfiguring a Hot Standby IDU for use in 1+0 Configuration ..................................... 6.1.5 Reconfiguring a 1+0 IDU for use in Hot StandBy Configuration ......................

270 270 270 271 273 275 276 278 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 .................. 281 2.2 Testing ................................................................ 281

3.0

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

B4008 Rev. M

17

CityLink 4.0

Submenu Commands .................................................. 4.1 EEB Submenu .................................................... 4.2 Baseband Submenu ........................................... 4.3 Modem Submenu (part of IDU) ........................... 4.4 Radio Submenu (part of ODU) ............................ 4.4.1 Radio Status, Example ....................................... 4.4.2 Radio Commands, Example of Error Message .. 4.5 SU Submenu (part of IDU) .................................. 4.6 Security Submenu .............................................. 4.7 Performance Submenu ....................................... 4.8 Configuration Submenu ...................................... 4.8.1 Management Settings ......................................... 4.9 Test & Fault Submenu ........................................ 4.10 Q1module Submenu ...........................................

284 284 285 286 287 288 288 289 289 290 290 291 291 292

5.0

Software Upgrade Procedure for the CityLink Fast Ethernet Device ............................ 5.1 How to download a file to the IDU: ....................... 5.1.1 Using the Console FTP Client ............................. 5.1.2 Using the Internet Explorer .................................. 5.2 How to download a file to the ODU .....................

293 294 294 295 296

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

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

7.0

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

8.0

Element Node .............................................................. 8.1 Element Id ........................................................... 8.2 NE Clock ............................................................. 8.3 Software Versions ............................................... 8.4 Production Data .................................................. 8.5 SNMP Agent(s) Settings ..................................... 8.6 Trap Table ........................................................... 8.7 MIB II - System Group ......................................... 8.8 MIB-II SNMP Group.............................................. 8.9 Looping ............................................................... 8.9.1 Main Traffic Loops ...............................................

18

302 302 303 304 305 306 308 309 311 312 313 B4008 Rev. M

CityLink 8.9.2 Wayside Loops ................................................... 315 8.9.3 64 kbit/s Loops .................................................... 316 9.0

In Door Unit (IDU) ....................................................... 9.1 64 kbit/s Channels .............................................. 9.2 Ethernet Extension Board ................................... 9.2.1 Ethernet Ports ..................................................... 9.2.2 2 Mbit/s Ports ...................................................... 9.3 Wayside Channel ................................................ 9.4 Auxiliary Output ................................................... 9.5 BER Thresholds ................................................. 9.6 Laser Control ......................................................

317 317 317 318 319 320 321 323 325

10.0

Out Door Unit (ODU) .................................................. 10.1 Antenna Data ...................................................... 10.2 Power Settings .................................................... 10.3 Frequency Settings .............................................

327 327 328 330

11.0

Performance ................................................................ 11.1 G826 Performance.............................................. 11.2 Port Performance ............................................... 11.3 Repeater Performance .......................................

332 332 334 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 ...................................................................... 340 16.2 IDU ...................................................................... 341

B4008 Rev. M

19

CityLink 16.3 16.4 16.5 16.6 16.7 16.8

ODU .................................................................... Test Manager ...................................................... Performance Manager ........................................ Fault Manager ..................................................... Analogue Value ................................................... Security Manager ................................................

SECTION IX

342 343 344 345 346 346

Troubleshooting ......................... 347

1.0

General ........................................................................ 348

2.0

Description of Alarm LEDs ......................................... 2.1 IDU Alarm LEDs .................................................. 2.2 HSB-IDU Alarm LEDs and Switch Indicators ..... 2.3 LEDs on Line Interface Plug-in Boards ...............

348 348 348 349

3.0

Troubleshooting by NEW-NMS Configurator .......... 3.1 Introduction .......................................................... 3.2 Information Acquisition ........................................ 3.2.1 Polling ................................................................. 3.2.2 Event Notification ................................................ 3.3 Alarm Presentation.............................................. 3.4 Visual Alarm Notification ...................................... 3.4.1 Alarms on a Tree node/leaf in the Explorer view . 3.4.2 Alarms on a Node symbol in the Map view .......... 3.4.3 Viewing Alarms in the Current Alarms View ........

349 349 349 349 350 350 351 351 352 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

20

B4008 Rev. M

Equipment Description

SECTION I Equipment Description

B4008 Rev. M

21

CityLink

1.0

Introduction CityLink is a super compact SDH radio-relay transmission system with STM1 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 equipment is 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 increased 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 system 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.

22

B4008 Rev. M

Equipment Description 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)

B4008 Rev. M

23

CityLink

2.0 2.1

IDU 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 configured 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 radio transmit 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. The necessary cable equalizing functions are provided in the ODU interface and the equalized IF is presented to the coherent demodulator. From the demodulator 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.

24

B4008 Rev. M

Figure I-1

B4008 Rev. M

File: IDU-HRQI.DSF

48V DC

2 x NI

FIFO BUS

LCT LAN (10BASE-T)

ALARMS

2 x PHONE EXT.

PHONE

2 x 64 Kb/s

2Mb/s WAYSIDE

HSB IDU INTFC.

Optical MMF ~2Km or Optical SMF ~15Km or Optical SMF ~40Km or Optical SMF ~80Km or Electr. CAT5 UTP or Electr. G.703

G.703

2MHz SYNC

21x2 Mb/s G.703

21

1

FPGA

155 Mb/s LINE INTERFACE

"E1"

TRIBUTARY INTERFACE BLOCK NO. 2

"H2"

MAIN BD.

ALM/AUX INTFC.

INTERFACE

V11/G.703

DCC

SUPERVISORY SYSTEM

SVCE PHONE INTERFACE

"SORP" STM-1 OVERHEAD AND RADIO PROCESSOR

ASIC

SYNC. INTERFACE

TRIBUTARY DATA MAPPER NO. 1

TRIBUTARY DATA MAPPER NO. 1

ASIC's

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

TRELLIS DECODER

"ATDEC"

ASIC

DC / DC

CARRIER REC. CLOCK REC. DEMAPPER DECODER

FPGA RX:

ENCODER MAPPER FILTER

FPGA TX:

INTERFACE

REGULATED OUTPUTS

ODU

87.5 MHz OSC. SOURCE

MODEM TRANSCEIVER COMMUNICATION

93.3 MHz OSC. SOURCE

2x

DOWNCONVERSION A/D CONVERSION

INTERPOLATION MODULATION D/A CONVERSION UPCONVERSION

4x 3x

ODU

Equipment Description

Block schematic view of the IDU

25

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

26

B4008 Rev. M

Equipment Description 3xE3/DS3 EXTENSION BD. ASIC's

TRIBUTARY DATA MAPPER NO. 1

FPGA

TRIBUTARY INTERFACE BLOCK

3x34/45 Mb/s G.703

TRIBUTARY DATA MAPPER NO. 1

PHY

1.5 Mb/s WAYSIDE

"E1"

SYNC.

2MHz SYNC

INTERFACE

G.703 Optical MMF ~2Km or Optical SMF ~15Km or Optical SMF ~40Km or Optical SMF ~80Km or Electr. CAT5 UTP or Electr. G.703

ASIC

155 Mb/s LINE INTERFACE

"H1"

"SORP" SDH OVERHEAD AND RADIO PROCESSOR

IDU A INTFC. (R) IDU B INTFC. (P)

DCC

2Mb/s WAYSIDE

V11/G.703

2 x 64 Kb/s

INTERFACE

SVCE PHONE INTERFACE

PHONE 2 x PHONE EXT.

ALM/AUX INTFC.

ALARMS LCT LAN (10BASE-T)

SUPERVISORY SYSTEM

FIFO BUS 2 x NI 48V DC

DC / DC

REGULATED OUTPUTS

MAIN BD HSB IDU. File: HSBIDU-HRQE.DRW

Figure I-2

B4008 Rev. M

Block schematic view of the HSB IDU (shown here with DS3/E3 Extension Board)

27

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 to ITU-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 DTMFstar, 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.

28

B4008 Rev. M

Equipment Description 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 PABXadapters and to switch off loudspeakers on Nera service boards with selective call (e.g. 2NF4688, 2NF533B and 2KNF232A). The control signal 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.

1k

2

2

3

BYM122

15

2

BSR19A

2 1

1

10k

2

CALLOUT/ CTRLOUT

BSR19A CALLINP/ CTRLINP

2

BAS16

1

3

1

10k

+5V

1

3 PC3Q66Q

1

1

CALL_INP/ CTRL_INP

1

2 1

3

14

1k

1

10k

2

+3.3V

PC3Q66Q 2 2

CALL_OUT/ CTRL_OUT

16

4

13

-48V

Figure I-3 “Service Channel CALL" Circuit Diagram

B4008 Rev. M

29

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-andcontinue” 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. 21x2 Mb/s LINE INTFC./ADD-DROP EXTENSION BD. ASIC's

ASIC

1 21x2 Mb/s G.703

21

TRIBUTARY INTERFACE BLOCK NO. 1

TRIBUTARY DATA MAPPER NO. 1

TRIBUTARY DATA MAPPER NO. 1

To/from the IDU's SDH Overhead and Radio 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 63xVC12s 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 is shown. 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

30

B4008 Rev. M

Equipment Description 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 performance measurements on VC-12s embedded in the STM-1 datastreams from two TDM1 ASICs. The measurement results are used to choose individual VC-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.

IDU CONN

TDM1 ASIC no 1——→ PLD14 FPGA———————→ TDM1 ASIC no 3 ————————→

TDM1 RADIO

PLD14 FPGA

TDM1 LINE

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

TDM1 LINE EXTENSION BOARD

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

SORP EXT BOARD

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

LINE INTERFACE CARD

Figure I-5 Block schematic view of the ADM STM-1 Extension Board B4008 Rev. M

31

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. In additional it will perform insertion and extraction of 1.5 Mbit/s wayside (DS1/ T1). In Figure 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 STM1 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. 3xDS3/E3 and T1 EXT. BOARD IDU CONNECTOR

TDM1 No. 1 LINE

48 V DC/DC PLD15

TDM1 No. 2 RADIO

+3.3 V +1.5 V T1 LIU

3xDS3/E3

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

B4008 Rev. M

Equipment Description 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 10BASET/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.

4x RJ45 Ethernet

Ethernet Interface

Ethernet to/from STM1 and 2Mbit/s mapper/demapper Ethernet to/from STM1 and 2Mbit mapper/demapper

4x RJ45 2Mbit

To from IDU main board

22/1.5Mbit Mbit/s Interface Interface

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

B4008 Rev. M

33

CityLink

3.0 3.1

ODU 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 connected to the transceiver through the branching unit. The transceiver is attached to the branching with a snap on system. With this solution, the coaxial cable may remain connected during transceiver replacement. In 1+0 configuration 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 still maintaining 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, controlcircuits, signalling and power supply are integrated on the transceiver main board.

34

B4008 Rev. M

Figure I-8

B4008 Rev. M

IF IN / OUT

140 MHz

350 MHz

IF LOOP

350 MHz

UHF LO

UHF LO

210 MHz

PREDIST

CTRL / M/T COM / POWER

350 MHz

CAB. EQ.

SYNTHESIZER

UHF IF

7 GHz FIXED

2 GHz SYNTH

DUPLEX FREQ

TRANSCEIVER UNIT

TRANSCEIVER MAIN BOARD

XN

MICROWAVE MODULE

PWR

BRANCHING UNIT

IF IN / OUT M / T COM DC PWR

ANTENNA UNIT

Equipment Description

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

35

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 antenna. The Transceiver unit is a plug-in unit mounted in the box. In 1+0 configuration the ODU box contains 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 channel filters and the diplexer. The Hot Standby branching 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 module, 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 converter 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 narrow range. 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 &controller board. The branching unit contains narrow RF channel filters and circulators.

36

B4008 Rev. M

Figure I-9

B4008 Rev. M

48V

MTcom

Rx IF 140 MHz

Tx IF 350 MHz

CTRL

140 MHz

IF&CTRL Bd.

DC/DC

MTCom.

Multiplexer

350 MHz

Predistortion & AGC

140 MHz

DSB Mixer

210 MHz

IFSynt.

Synthesizer Unit

FLTR & AGC

IF loop

AGC & Cable equalizer

FLTR & AGC

RxSynt.

TxSynt.

350 MHz

Rx LO

Tx LO

RCVR Module

IMR Mixer

SSB Upconverter

XMTR Module

IMD Det.

LO Det.

Low Noise Amplifier

350 MHz

LO, IMD mxr

Power Amplifier

RF in

RF out

Equipment Description

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

37

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 the IDU 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 standby configurations both ODUs are attached by the same snap-on clamps to a branching hybrid. This hybrid can either 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 upconversion 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 via the IDU. Transmit/receive IF multiplexing, control and monitoring and power supply functions are all integrated on the transceiver main board.

38

B4008 Rev. M

Figure I-10

B4008 Rev. M

DIPLEXER

EQUALISER

SLOPE

MAIN BOARD

PREDIST

210MHz

DUPLEX FREQ.

TRANSCEIVER

SYNTHEZISER 7-9 GHz

MICROWAVE CONVERTER

UHF LO2 (LO1)

UHF LO1 (LO2)

DIPLEXER

ANTENNA

Equipment Description

Block schematic view of the ODU Type III

39

CityLink

4.0

Management An integrated supervision system makes the CityLink capable of functioning 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 management through 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 management 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

1+0 (Unprotected)

OK

1+1 (Hot Standby)

OK

1+1 Frequency Diversity

OK

26 – 38 GHz

NA

1+1 (Hot Standby) – Dual Baseband

OK

OK

OK

NA

1+1 (Hot Standby) – Dual antenna

TBD

TBD

TBD

OK

32 TCM only

32 TCM only 1

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

OK NA

NA

2+0 Alternating Polarisation (AP)

OK 1

1+0 prepared for 2+0

OK

Table I-1

40

18 – 23 GHz

System Configurations

B4008 Rev. M

Equipment Description Space Diversity and Hybrid Space Diversity is available as specified in the table below. L6 – 11 GHz

13 – 15 GHz

18 – 23 GHz

26 – 38 GHz

Space Diversity with IF combining 1+0,1+1 FD, HSB

Frequency Band

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

5.1

Space Diversity Configurations

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.

Aux traffic

SDH/SONET Processing

Management

Management & SNMP Agent

Optional Plug-in Multiplex Unit DC power feeding & overvoltage protection

STM-1/OC-3 Plug-in Line Interface

Modulator Demodulator

155 Mb/s

Transceiver

Branching

Antenna

Coaxial cable (up to 300 m)

Indoor unit (IDU)

Figure I-11

B4008 Rev. M

1+0 System Overview

41

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 hitless switching 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.

155Mbit/s

Aux traffic Management

STM-1/OC-3 Plug-in Line Interface Management & SNMP Agent

SDH/SONET Processing

Management

DC power feeding & overvoltage protection

Optional plug-in Multiplex Unit SDH/SONET Processing

DC power feeding & overvoltage protection

Management

Modulator Demodulator

SDH/SONET Processing

Modulator Demodulator

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

Coaxial cable (up to 300 m)

Transceiver Unit Branching Unit

Antenna unit

Transceiver Unit

Outdoor unit (ODU)

Indoor unit (IDU)

Figure I-12

5.3

1+1 Frequency Diversity and Hot Standby System Overview

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.

42

B4008 Rev. M

Equipment Description 5.4

Hot Standby Configuration – Dual Antenna

155Mbit/s

Aux traffic Management

STM-1/OC-3 Plug-in Line Interface Management & SNMP Agent

SDH/SONET Processing

Management

DC power feeding & overvoltage protection

Optional plug-in Multiplex Unit

Coaxial cable (up to 300 m)

Transceiver Unit Branching Unit

Antenna unit

Branching Unit

Antenna unit

SDH/SONET Processing

DC power feeding & overvoltage protection

Management

Modulator Demodulator

SDH/SONET Processing

Modulator Demodulator

The Hot Standby configuration is for 26-38 GHz also available with duplicated 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.

Transceiver Unit

Outdoor unit (ODU)

Indoor unit (IDU)

Figure I-13

B4008 Rev. M

Hot Standby-Dual Antenna System Overview

43

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

SDH/SONET Processing

Management

Management & SNMP Agent

Aux traffic

SDH/SONET Processing

Management

Management & SNMP Agent

Coaxial cable (up to 300 m)

Transceiver Unit

Branching Unit

STM-1/OC-3 Plug-in Line Interface DC power feeding & overvoltage protection

155 Mb/s

DC power feeding & overvoltage protection

Aux traffic

Modulator Demodulator

STM-1/OC-3 Plug-in Line Interface

Modulator Demodulator

155 Mb/s

Antenna unit

Transceiver Unit

Outdoor unit (ODU)

Indoor unit (IDU)

Figure I-14

44

Hot Standby-Dual Baseband System Overview

B4008 Rev. M

Equipment Description 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 be used. Figure I-15 and Figure I-16 show block diagrams of the 2+0 configurations.

Aux traffic

SDH/SONET Processing

Management

Management & SNMP Agent

Optional Plug-in Multiplex Unit DC power feeding & overvoltage protection

STM-1/OC-3 Plug-in Line Interface

Modulator Demodulator

155 Mb/s

Transceiver

Coaxial cable (up to 300 m)

Branching

H-pol

Antenna

Indoor unit (IDU)

Aux traffic

SDH/SONET Processing

Management

Management & SNMP Agent

Transceiver

Optional Plug-in Multiplex Unit DC power feeding & overvoltage protection

STM-1/OC-3 Plug-in Line Interface

Modulator Demodulator

155 Mb/s

V-pol

Branching Coaxial cable (up to 300 m)

Outdoor unit (ODU)

Indoor unit (IDU)

STM-1/OC-3 Plug-in Line Interface

Aux traffic

SDH/SONET Processing

Management

Management & SNMP Agent

Optional Plug-in Multiplex Unit DC power feeding & overvoltage protection

155 Mb/s

Single Frequency - Dual Polarisation / Alternating Polarisation

Modulator Demodulator

Figure I-15

Indoor unit (IDU)

Aux traffic

SDH/SONET Processing

Management

Management & SNMP Agent

Optional Plug-in Multiplex Unit DC power feeding & overvoltage protection

STM-1/OC-3 Plug-in Line Interface

Modulator Demodulator

155 Mb/s

Coaxial cable (up to 300 m)

Transceiver

Branching

Antenna

Transceiver

Outdoor unit (ODU)

Indoor unit (IDU)

Figure I-16 B4008 Rev. M

Dual Frequency - Single Polarisation 45

CityLink 5.7

Space Diversity

Management

DC power feeding & overvoltage protection

SDH/SONET Processing

Modulator Demodulator

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) Coaxial cable (up to 300 m)

155Mbit/s

Aux traffic Management

STM-1/OC-3 Plug-in Line Interface

Optional plug-in Multiplex Unit

Main Antenna

SD Transceiver Main Branching SD Branching

Management & SNMP Agent

SDH/SONET Processing

SD Transceiver

DC power feeding & overvoltage protection

Management

Modulator Demodulator

WG SDH/SONET Processing

SD Antenna

Indoor unit (IDU)

Figure I-17

5.8

Space Diversity

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. The configuration is available for L6-11 GHz systems.

46

B4008 Rev. M

Management

DC power feeding & overvoltage protection

SDH/SONET Processing

Modulator Demodulator

Equipment Description

Outdoor unit (ODU) Coaxial cable (up to 300 m)

155Mbit/s

Aux traffic Management

STM-1/OC-3 Plug-in Line Interface

Main Antenna

Transceiver

Optional plug-in Multiplex Unit

M ain Branching SD Branching

Management & SNMP Agent

SDH/SONET Processing

Transceiver

DC power feeding & overvoltage protection

Management

Modulator Demodulator

WG SDH/SONET Processing

SD Antenna

Indoor unit (IDU)

Figure I-18

HSB Hybrid Space Diversity

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.

IDU User Interfaces

Figure I-19

IDU

f1 1+1 ODU

Switch

IDU

B4008 Rev. M

1+0 ODU

1+0 ODU

f2

Switch

User Interfaces

IDU

1+1 Hybrid Space Diversity

47

CityLink 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

RS Other MS equipment

MS

Figure I-20

5.10

RRT

RRT

RS MS

RS

MS

MS

Other MS equipment

Configuration Examples

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.

This page is intentionally left blank. 48

B4008 Rev. M

ODU Type I Installation

SECTION II Installation of ODU Type I and Antenna

B4008 Rev. M

49

CityLink

1.0

General This 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 information 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-owned cargo containers should be used.

50

B4008 Rev. M

ODU Type I Installation 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 corresponds to the components required for the installation, i.e. correct antenna and 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 controlled 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 transportation 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 minimise condensation 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 branching and the transceiver must be kept on until mounting of waveguide components and connection of the transceiver to the branching unit.

B4008 Rev. M

51

CityLink

2.0 2.1

Installation Equipment required Tools The tools needed to install the equipment are listed in the following subchapters.

2.1.1

Tools for Antenna Installation • • • •

2.1.2

52

2 pcs Combination Wrench 13 mm 2 pcs Combination Wrench 16 mm 2 pcs Combination Wrench 17 mm 1 pc Torque Wrench 16 mm, 40 - 50 Nm

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

ODU Type I Installation 2.2

Equipment external to the Radio Equipment In addition to the necessary radio equipment & antenna the following items are needed: • • • • • • • • •

B4008 Rev. M

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.

53

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 Loosen this nut one turn.

Bracket Rotate the bracket 1800 by turning this bolt CW.

54

B4008 Rev. M

ODU Type I Installation 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

B4008 Rev. M

55

CityLink 3.1.3

Mounting the Branching Support Bracket

M8x25

BRANCHING SUPPORT BRACKET

56

B4008 Rev. M

ODU Type I Installation 3.1.4

Mounting the Rear Travers

M8x25 REAR TRAVERS

3.1.5

Mounting the Suspension Support Bracket

SUSPENSION SUPPORT BRACKET

M8x25 B4008 Rev. M

57

CityLink 3.1.6

Mounting the Bend on the Branching Unit

M3 STUDS, NUTS AND WASHERS

FEED

O-RING

58

B4008 Rev. M

ODU Type I Installation 3.1.7

Installation of the Branching Unit

BRANCHING UNIT

M8 STUDS, NUTS AND WASHERS

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

3.1.8

Attachment of the Sunshield Support M8x30 SCREW, NUT AND WASHERS

SUNSHIELD SUPPORT M8x30 SCREW, NUT AND WASHERS B4008 Rev. M

59

CityLink 3.1.9

Installation of the Flexible Waveguide M3 ALLEN SCREWS, NUT AND WASHERS

2 O-RINGS

60

O-RING

M3 STUDS, NUT AND WASHERS

R220 FLEXIBLE WAVEGUIDE

B4008 Rev. M

ODU Type I Installation 3.1.10

Installation of the Sunshield M6x25 SCREWS, NUTS, LARGE WASHERS AND WASHERS

(PLACING OF LARGE WASHER)

M4 ALLEN SCREW (FOUND MOUNTED ON THE BRANCHING UNIT)

M4x16 SCREWS, NUTS AND WASHERS

SUNSHIELD

B4008 Rev. M

61

CityLink 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

U-BOLTS (ABZ5479 for column diameter Ø115mm, ABZ5480 for column diameter Ø75mm)

M10 Nuts, washers and lock washers, 4ea Torque: 25-30Nm

62

B4008 Rev. M

ODU Type I Installation 3.1.11.2

Mounting the Suspension/Antenna to a Column by using the Clamps

CLAMPS, 2ea (ABZ5481)

Column diameter: 60-115mm M10 Nuts and washers, 4ea Torque: 35Nm

B4008 Rev. M

63

CityLink 3.1.11.3

Mounting the Suspension/Antenna to a Wall

M10 Expansion bolts (type dependant on the nature of the wall

M10 Nuts and washers

64

B4008 Rev. M

ODU Type I Installation 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.

Protection lid

First remove the nuts using a 5,5mm wrench.

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

B4008 Rev. M

65

CityLink

66

B4008 Rev. M

ODU Type I Installation 3.1.13

Pole Mount

3.1.13.1

Assembly of Branching Support Bracket

CLAMP

M12 (Torque 19 NM)

BRANCHING SUPPORT BRACKET

3.1.13.2

Installation of Branching Unit and Sun-shield

BRANCHING UNIT SUN-SHIELD

M4 M8 Grounding point. See Section V Chapter 5.0 Fig. V-8 B4008 Rev. M

67

CityLink 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

HORIZONTAL GIRDER

VERTICAL GIRDER

BRANCHING SUPPORT BRACKET

HORIZONTAL GIRDER

105mm ± 5

Make sure that the distance between the top of the branching support bracket and the horizontal girder is 105mm ±5mm.

BRANCHING SUPPORT BRACKET

68

B4008 Rev. M

ODU Type I Installation 3.2.3

Installation of Branching Unit, Sun-shield and Flexible Waveguide FLEXIBLE WAVEGUIDE BRANCHING UNIT SUN-SHIELD

M4

M8 ANTENNA FEED 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.

B4008 Rev. M

69

CityLink

4.0

ODU / Antenna Installation, 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 SUPPORT BRACKET

70

B4008 Rev. M

ODU Type I Installation 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

M8x25 STUDS, NUTS AND WASHERS

BRANCHING UNIT

B4008 Rev. M

71

CityLink 4.1.1.5

Installation of the Flexible Waveguide M3 ALLEN SCREWS, NUT AND WASHERS

2 O-RINGS

72

O-RING

M3 STUDS, NUT AND WASHERS

R220 FLEXIBLE WAVEGUIDE

B4008 Rev. M

ODU Type I Installation 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

M6x25 SCREWS, NUTS, LARGE WASHERS AND WASHERS (PLACING OF LARGE WASHER)

M4 ALLEN SCREW (FOUND MOUNTED ON THE BRANCHING UNIT)

M4x16 SCREWS, NUTS AND WASHERS

SUNSHIELD

B4008 Rev. M

73

CityLink 4.1.1.8

Mounting the Suspension/ODU to a Column or a Wall Please refer to Chapter 3.1.11 (this Section).

4.1.1.9

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. Please refer to Chapter 3.1.12 (this Section) for details.

74

B4008 Rev. M

ODU Type I Installation 4.1.1.10

Pole Mount

4.1.1.10.1 Assembly of Branching Support Bracket

CLAMP M12 (Torque 19 NM)

BRANCHING SUPPORT BRACKET

4.1.10.1.2 Installation of Branching Unit and Sunshield

BRANCHING UNIT SUN-SHIELD

M4 M8 Grounding point. See Section V Chapter 5.0 Fig. V-9 B4008 Rev. M

75

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 Suspension Please 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

M8 STUDS, NUTS AND WASHERS

76

B4008 Rev. M

ODU Type I Installation 4.1.2.4

Installation of the Flexible Waveguide M3 ALLEN SCREWS, NUT AND WASHERS

M3 STUDS, NUT AND WASHERS 2 O-RINGS

R220 FLEXIBLE WAVEGUIDE

M3 ALLEN SCREWS, NUT AND WASHERS

O-RING

2 O-RINGS

M3 STUDS, NUT AND WASHERS

B4008 Rev. M

77

CityLink 4.1.2.5

Installation of the Sunshield M6x25 SCREWS, NUTS, LARGE WASHERS AND WASHERS (PLACING OF LARGE WASHER)

M4 ALLEN SCREW (FOUND MOUNTED ON THE BRANCHING UNIT)

78

SUNSHIELDS

M4 ALLEN SCREW (FOUND MOUNTED ON THE BRANCHING UNIT)

B4008 Rev. M

ODU Type I Installation 4.1.2.6

Mounting the Suspension/ODU to a Column or a Wall Please refer to Chapter 3.1.11 (this Section).

4.1.2.7

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. Please refer to Chapter 3.1.12 (this Section) for details.

B4008 Rev. M

79

CityLink 4.1.2.9

Pole Mount

4.1.2.9.1

Assembly of Branching Support Bracket

CLAMP M12 (Torque 19 NM)

BRANCHING SUPPORT BRACKET

4.1.2.9.2

Installation of Branching Units and Sunshields

BRANCHING UNITS SUN-SHIELDS

M4 M8 Grounding point. See Section V Chapter 5.0 Fig. V-9 80

B4008 Rev. M

ODU Type I Installation 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

HORIZONTAL GIRDER BRANCHING SUPPORT BRACKET VERTICAL GIRDER

HORIZONTAL GIRDER

130mm 5 87mm±±3mm

Make sure that the distance between the top of the branching support bracket and the horizontal girder is 130mm ±3mm.

BRANCHING SUPPORT BRACKET

B4008 Rev. M

81

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

FLEXIBLE WAVEGUIDE BRANCHING UNIT

SUN-SHIELD

M4

M8

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 CityLink installations as the ODU, the flexible 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.

82

B4008 Rev. M

ODU Type I Installation 4.2.2.2

2+0 Single Frequency Dual Polarization

FLEXIBLE WAVEGUIDES BRANCHING UNITS SUN-SHIELDS

M4 M8 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 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.

B4008 Rev. M

83

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 are further 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 tuning screws. 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] For 13GHz Transceiver; 3±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: For 15GHz Transceiver; 4±0.5[V] For 13GHz Transceiver; 3±0.5[V] 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).

84

B4008 Rev. M

ODU Type I Installation

VT TX

GND

VT RX

B4008 Rev. M

Tx High

Rx High

Tx Low

Rx Low

85

CityLink Duplex frequency: 490 MHz Channel spacing: 28MHz TX Ch. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

TX Freq. 14417 14445 14473 14501 14529 14557 14585 14613 14641 14669 14697 14725 14753 14781 14809 14837

10L15L01A TX RX DRO Ch. Low 1’ Low 2’ Low 3’ Low 4’ Low 5’ Low 6’ Low 7’ Low 8’ Low 9’ High 10’ High 11’ High 12’ High 13’ High 14’ High 15’ High 16’

RX Freq. 14907 14935 14963 14991 15019 15047 15075 15103 15131 15159 15187 15215 15243 15271 15299 15327

RX DRO Low Low Low Low Low Low Low Low Low Low Low High High High High High

TX Ch. 1’ 2’ 3’ 4’ 5’ 6’ 7’ 8’ 9’ 10’ 11’ 12’ 13’ 14’ 15’ 16’

TX Freq. 14907 14935 14963 14991 15019 15047 15075 15103 15131 15159 15187 15215 15243 15271 15299 15327

10L15U01A TX RX DRO Ch. Low 1 Low 2 Low 3 Low 4 Low 5 Low 6 Low 7 Low 8 High 9 High 10 High 11 High 12 High 13 High 14 High 15 High 16

RX Freq. 14417 14445 14473 14501 14529 14557 14585 14613 14641 14669 14697 14725 14753 14781 14809 14837

RX DRO Low Low Low Low Low Low Low Low Low Low High High High High High High

10L15U01A TX RX DRO Ch. Low 1 Low 2 Low 3 Low 4 Low 5 Low 6 Low 7 High 8 High 9 High 10 High 11 High 12 High 13 High 14 High 15

RX Freq. 14515 14543 14571 14599 14627 14655 14683 14711 14739 14767 14795 14823 14851 14879 14907

RX DRO Low Low Low Low Low Low High High High High High High High High High

10L15U01A TX RX DRO Ch. High 1 High 2 High 3 High 4

RX Freq. 14515 14543 14571 14599

RX DRO Low Low Low Low

Table II-1 Duplex frequency: 420 MHz Channel spacing: 28MHz TX Ch. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

TX Freq. 14515 14543 14571 14599 14627 14655 14683 14711 14739 14767 14795 14823 14851 14879 14907

10L15L01A TX RX DRO Ch. Low 1’ Low 2’ Low 3’ Low 4’ Low 5’ Low 6’ High 7’ High 8’ High 9’ High 10’ High 11’ High 12’ High 13’ High 14’ High 15’

RX Freq. 14935 14963 14991 15019 15047 15075 15103 15131 15159 15187 15215 15243 15271 15299 15327

RX DRO Low Low Low Low Low Low Low High High High High High High High High

TX Ch. 1’ 2’ 3’ 4’ 5’ 6’ 7’ 8’ 9’ 10’ 11’ 12’ 13’ 14’ 15’

TX Freq. 14935 14963 14991 15019 15047 15075 15103 15131 15159 15187 15215 15243 15271 15299 15327

Table II-2 Duplex frequency: 728 MHz Channel spacing: 28MHz TX Ch. 1 2 3 4

TX Freq. 14515 14543 14571 14599

10L15L01A TX RX DRO Ch. Low 1’ Low 2’ Low 3’ Low 4’

RX Freq. 15243 15271 15299 15327

RX DRO High High High High

TX Ch. 1’ 2’ 3’ 4’

TX Freq. 15243 15271 15299 15327

Table II-3

86

B4008 Rev. M

ODU Type I Installation Duplex frequency: 315 MHz Channel spacing: 28MHz TX Ch. 1 2 3 4 5 6 7 8 9

TX Freq. 14662 14690 14718 14746 14774 14802 14830 14858 14886

10L15L01A TX RX DRO Ch. Low 1’ High 2’ High 3’ High 4’ High 5’ High 6’ High 7’ High 8’ High 9’

RX Freq. 14977 15005 15033 15061 15089 15117 15145 15173 15201

RX DRO Low Low Low Low Low Low High High High

TX Ch. 1’ 2’ 3’ 4’ 5’ 6’ 7’ 8’ 9’

TX Freq. 14977 15005 15033 15061 15089 15117 15145 15173 15201

10L15U01A TX RX DRO Ch. Low 1 Low 2 Low 3 Low 4 Low 5 Low 6 High 7 High 8 High 9

RX Freq. 14662 14690 14718 14746 14774 14802 14830 14858 14886

RX DRO Low High High High High High High High High

10L15U01A TX RX DRO Ch. High 1 High 2 High 3 High 4 High 5 High 6 High 7

RX Freq. 14515 14543 14571 14599 14627 14655 14683

RX DRO Low Low Low Low Low Low High

10L15U01A TX RX DRO Ch. Low 1 Low 2 Low 3 Low 4 Low 5 Low 6 Low 7 Low 8 Low 9 Low 10 Low 11 Low 12 Low 13 Low 14 High 15 High 16 High 17 High 18 High 19 High 20 High 21 High 22 High 23 High 24 High 25 High 26 High 27 High 28 High 29 High 30

RX Freq. 14515 14529 14543 14557 14571 14585 14599 14613 14627 14641 14655 14669 14683 14697 14711 14725 14739 14753 14767 14781 14795 14809 14823 14837 14851 14865 14879 14893 14907 14921

RX DRO Low Low Low Low Low Low Low Low Low Low Low Low High High High High High High High High High High High High High High High High High High

Table II-4 Duplex frequency: 644 MHz Channel spacing: 28MHz TX Ch. 1 2 3 4 5 6 7

TX Freq. 14515 14543 14571 14599 14627 14655 14683

10L15L01A TX RX DRO Ch. Low 1’ Low 2’ Low 3’ Low 4’ Low 5’ Low 6’ High 7’

RX Freq. 15159 15187 15215 15243 15271 15299 15327

RX DRO High High High High High High High

TX Ch. 1’ 2’ 3’ 4’ 5’ 6’ 7’

TX Freq. 15159 15187 15215 15243 15271 15299 15327

Table II-5 Duplex frequency: 420 MHz Channel spacing: 14MHz TX Ch. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

TX Freq. 14515 14529 14543 14557 14571 14585 14599 14613 14627 14641 14655 14669 14683 14697 14711 14725 14739 14753 14767 14781 14795 14809 14823 14837 14851 14865 14879 14893 14907 14921

10L15L01A TX RX DRO Ch. Low 1’ Low 2’ Low 3’ Low 4’ Low 5’ Low 6’ Low 7’ Low 8’ Low 9’ Low 10’ Low 11’ High 12’ High 13’ High 14’ High 15’ High 16’ High 17’ High 18’ High 19’ High 20’ High 21’ High 22’ High 23’ High 24’ High 25’ High 26’ High 27’ High 28’ High 29’ High 30’

RX Freq. 14935 14949 14963 14977 14991 15005 15019 15033 15047 15061 15075 15089 15103 15117 15131 15145 15159 15173 15187 15201 15215 15229 15243 15257 15271 15285 15299 15313 15327 15341

RX DRO Low Low Low Low Low Low Low Low Low Low Low Low Low Low High High High High High High High High High High High High High High High High

TX Ch. 1’ 2’ 3’ 4’ 5’ 6’ 7’ 8’ 9’ 10’ 11’ 12’ 13’ 14’ 15’ 16’ 17’ 18’ 19’ 20’ 21’ 22’ 23’ 24’ 25’ 26’ 27’ 28’ 29’ 30’

TX Freq. 14935 14949 14963 14977 14991 15005 15019 15033 15047 15061 15075 15089 15103 15117 15131 15145 15159 15173 15187 15201 15215 15229 15243 15257 15271 15285 15299 15313 15327 15341

Table II-6 B4008 Rev. M

87

CityLink Duplex frequency: 490 MHz Channel spacing: 14MHz TX Ch. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

TX Freq. 14417 14431 14445 14459 14473 14487 14501 14515 14529 14543 14557 14571 14585 14599 14613 14627 14641 14655 14669 14683 14697 14711 14725 14739 14753 14767 14781 14795 14809 14823 14837 14851

10L15L01A TX RX DRO Ch. Low 1’ Low 2’ Low 3’ Low 4’ Low 5’ Low 6’ Low 7’ Low 8’ Low 9’ Low 10’ Low 11’ Low 12’ Low 13’ Low 14’ Low 15’ Low 16’ High 17’ High 18’ High 19’ High 20’ High 21’ High 22’ High 23’ High 24’ High 25’ High 26’ High 27’ High 28’ High 29’ High 30’ High 31’ High 32’

RX Freq. 14907 14921 14935 14949 14963 14977 14991 15005 15019 15033 15047 15061 15075 15089 15103 15117 15131 15145 15159 15173 15187 15201 15215 15229 15243 15257 15271 15285 15299 15313 15327 15341

RX DRO Low Low Low Low Low Low Low Low Low Low Low Low Low Low Low Low Low Low High High High High High High High High High High High High High High

TX Ch. 1’ 2’ 3’ 4’ 5’ 6’ 7’ 8’ 9’ 10’ 11’ 12’ 13’ 14’ 15’ 16’ 17’ 18’ 19’ 20’ 21’ 22’ 23’ 24’ 25’ 26’ 27’ 28’ 29’ 30’ 31’ 32’

TX Freq. 14907 14921 14935 14949 14963 14977 14991 15005 15019 15033 15047 15061 15075 15089 15103 15117 15131 15145 15159 15173 15187 15201 15215 15229 15243 15257 15271 15285 15299 15313 15327 15341

10L15U01A TX RX DRO Ch. Low 1 Low 2 Low 3 Low 4 Low 5 Low 6 Low 7 Low 8 Low 9 Low 10 Low 11 Low 12 Low 13 Low 14 Low 15 Low 16 High 17 High 18 High 19 High 20 High 21 High 22 High 23 High 24 High 25 High 26 High 27 High 28 High 29 High 30 High 31 High 32

RX Freq. 14417 14431 14445 14459 14473 14487 14501 14515 14529 14543 14557 14571 14585 14599 14613 14627 14641 14655 14669 14683 14697 14711 14725 14739 14753 14767 14781 14795 14809 14823 14837 14851

RX DRO Low Low Low Low Low Low Low Low Low Low Low Low Low Low Low Low Low Low Low High High High High High High High High High High High High High

10L13U01A TX RX DRO Ch. High 1 High 2 High 3 High 4 High 5 High 6 High 7 High 8

RX Freq. 12765 12793 12821 12849 12877 12905 12933 12961

RX DRO Low Low Low Low Low Low Low Low

Table II-7 Duplex frequency: 266 MHz Channel spacing: 28MHz TX Ch. 1 2 3 4 5 6 7 8

TX Freq. 12765 12793 12821 12849 12877 12905 12933 12961

10L13L01A TX RX DRO Ch. Low 1’ Low 2’ Low 3’ Low 4’ Low 5’ Low 6’ Low 7’ Low 8’

RX Freq. 13031 13059 13087 13115 13143 13171 13199 13227

RX DRO High High High High High High High High

TX Ch. 1’ 2’ 3’ 4’ 5’ 6’ 7’ 8’

TX Freq. 13031 13059 13087 13115 13143 13171 13199 13227

Table II-8

88

B4008 Rev. M

ODU Type I Installation Duplex frequency: 266 MHz Channel spacing: 14MHz TX Ch. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

TX Freq. 12758 12772 12786 12800 12814 12828 12842 12856 12870 12884 12898 12912 12926 12940 12954 12968

10L13L01A TX RX DRO Ch. Low 1’ Low 2’ Low 3’ Low 4’ Low 5’ Low 6’ Low 7’ Low 8’ Low 9’ Low 10’ Low 11’ Low 12’ Low 13’ Low 14’ Low 15’ Low 16’

RX Freq. 13024 13038 13052 13066 13080 13094 13108 13122 13136 13150 13164 13178 13192 13206 13220 13234

RX DRO High High High High High High High High High High High High High High High High

TX Ch. 1’ 2’ 3’ 4’ 5’ 6’ 7’ 8’ 9’ 10’ 11’ 12’ 13’ 14’ 15’ 16’

TX Freq. 13024 13038 13052 13066 13080 13094 13108 13122 13136 13150 13164 13178 13192 13206 13220 13234

10L13U01A TX RX DRO Ch. High 1 High 2 High 3 High 4 High 5 High 6 High 7 High 8 High 9 High 10 High 11 High 12 High 13 High 14 High 15 High 16

RX Freq. 12758 12772 12786 12800 12814 12828 12842 12856 12870 12884 12898 12912 12926 12940 12954 12968

RX DRO Low Low Low Low Low Low Low Low Low Low Low Low Low Low Low Low

Table II-9

B4008 Rev. M

89

CityLink

6.0

Cable Connections Please refer to Section V Chapter 5.0.

7.0

Antenna Alignment Please refer to Section IV Chapter 6.0.

90

B4008 Rev. M

ODU Type II Installation

SECTION III Installation of ODU Type II and Antenna

B4008 Rev. M

91

CityLink

1.0

General This 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 information 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-owned cargo containers should be used.

92

B4008 Rev. M

ODU Type II Installation 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 corresponds to the components required for the installation, i.e. correct antenna and 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 controlled 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 transportation 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 minimise condensation 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 branching and the transceiver must be kept on until mounting of waveguide components and connection of the transceiver to the branching unit.

B4008 Rev. M

93

CityLink

2.0 2.1

Installation Equipment required Tools The tools needed to install the equipment are listed in the following subchapters.

2.1.1

Tools for Antenna Installation • • • •

2.1.2

94

2 pcs Combination Wrench 13 mm 2 pcs Combination Wrench 16 mm 2 pcs Combination Wrench 17 mm 1 pc Torque Wrench 16 mm, 40 - 50 Nm

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

ODU Type II Installation 2.2

Equipment external to the Radio Equipment In addition to the necessary radio equipment & antenna the following items are needed: • • • • • • • • •

B4008 Rev. M

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.

95

CityLink

3.0 3.1

ODU Installation 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

U-BOLTS

Waveguide Flange type: PDR84 SUN-SHIELD

96

B4008 Rev. M

ODU Type II Installation 3.2

Cable Connections ODU BOTTOM VIEW: Pressure equalizer

AGC Connector

Ground connection. Attach grounding cable (10mm2) to this point with the M6 nut and washers.

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

B4008 Rev. M

97

CityLink

4.0

Antenna and Waveguide Installation

4.1

0.6m Antenna

Shim Copper/ Aluminium Copper side

Alu side

Flange Adapter (NL2007 only)

98

B4008 Rev. M

ODU Type II Installation 4.2

B4008 Rev. M

1.2m Antenna

99

CityLink 4.3

100

2m Antenna

B4008 Rev. M

ODU Type II Installation 4.4

B4008 Rev. M

2.4m

101

CityLink 4.5

3m

317±20

102

B4008 Rev. M

ODU Type III Installation

SECTION IV Installation of ODU Type III and Antenna

B4008 Rev. M

103

CityLink

1.0

General This 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 information 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-owned cargo containers should be used.

104

B4008 Rev. M

ODU Type III Installation 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 corresponds to the components required for the installation, i.e. correct antenna and 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 controlled 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 transportation 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 minimise condensation 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 branching and the transceiver must be kept on until mounting of waveguide components and connection of the transceiver to the branching unit.

B4008 Rev. M

105

CityLink

2.0 2.1

Installation Equipment required Tools The tools needed to install the equipment are listed in the following subchapters.

2.1.1

Tools for Antenna Installation and Adjustment • • • • •

2.1.2

106

2 pcs Combination Wrench M8, 13 mm 2 pcs Combination Wrench M10, 16 mm 2 pcs Combination Wrench M6, 10 mm 1 pc Combination Wrench 10 mm 1 pc Torque Wrench, M16, 24 mm, 120 Nm

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

ODU Type III Installation 2.2

Equipment external to the Radio Equipment In addition to the necessary radio equipment & antenna the following items are needed: • • • • • • • • •

B4008 Rev. M

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.

107

CityLink

3.0 3.1

ODU / Antenna Installation, 1+0 Equipment Mounting the Antenna to the Suspension All the described nuts and washers are included in the antenna assembly and come attached to the antenna. SUSPENSION (3AB5158A) ANTENNA (0,3m 0,45m and 0,6m)

4ea M8 Nuts, washers and lock washers

108

B4008 Rev. M

ODU Type III Installation 3.2

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

M6 Nuts, washers and lock washers (4ea) SUNSHIELD M6 Screws (4ea)

B4008 Rev. M

109

CityLink 3.3

Mounting the Suspension/Antenna to a Column by using the U-bolts

U-BOLTS (ABZ5479 for column diameter Ø115mm, ABZ5480 for column diameter Ø75mm)

M10 Nuts, washers and lock washers, 4ea Torque: 25-30Nm

110

B4008 Rev. M

ODU Type III Installation 3.4

Mounting the Suspension/Antenna to a Column by using the Clamps

CLAMPS, 2ea (ABZ5481)

Column diameter: 60-115mm M10 Nuts and washers, 4ea Torque: 35Nm

B4008 Rev. M

111

CityLink 3.5

Mounting the Transceiver (without Antenna) to a Column STEP 1

Mounting the Brackets on the Frame

Bracket (Kit: ABZ5774)

4ea M8x20 screws 8ea Flat washers 4ea Lock washers 4ea M8 Nuts (Kit:ABZ5774)

Bracket (Kit: ABZ5774)

112

B4008 Rev. M

ODU Type III Installation STEP 2

Attaching the Frame to the Column

4ea M10 Flat washers 8ea M10 Nuts (Kit:ABZ5774)

2ea M10 U-bolts (Kit: ABZ5774)

B4008 Rev. M

113

CityLink STEP 3

Mounting the Sunshields Sunshields (Kit: ABZ5779)

2ea M5x12 screws 8ea M5 flat washers 4ea M5 lock washers 4ea M5 nuts (Kit: ABZ5774)

114

B4008 Rev. M

ODU Type III Installation STEP 4

Mounting the Transceiver

1+0 Configuration

1+1/HSB Configuration

B4008 Rev. M

115

CityLink STEP 5

Mounting the Flexible Waveguide

1+0 Configuration

Mounting flange for flexible waveguide

1+1/HSB Configuration

Mounting flange for flexible waveguide

116

B4008 Rev. M

ODU Type III Installation 3.6

Mounting the Suspension/Antenna to a Wall

M10 Expansion bolts (type dependant on the nature of the wall

Ø10mm Predrilled holes M10 Nuts and washers

B4008 Rev. M

117

CityLink 3.7

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.

Protection lid

First remove the nuts using a 5,5mm wrench.

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

118

B4008 Rev. M

ODU Type III Installation

After adjustment; M16 torque = 110-120Nm For adjustment see Chapter 6.0.

For correct polarisation; see next page

LATCHES (4ea, one in each corner) To unlock the latches, push this handle forward

B4008 Rev. M

119

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). UP

DOWN Waveguide feed with vertical polarisation

Waveguide feed with horizontal polarisation

UP POLARIZATION POLARIZATION

POLARIZATION

POLARIZATION

DOWN ODU orientation for vertical polarisation

120

ODU orientation for horizontal polarisation

B4008 Rev. M

ODU Type III Installation

4.0 4.1

ODU / Antenna Installation, HSB and 2+0 Equipment Preparing the Suspension for HSB and 2+0 Mounting

Loosen this nut one turn. (See also Chapter 6.0)

Bracket Rotate the bracket 1800 by turning this bolt CW.

B4008 Rev. M

121

CityLink 4.2

Mounting the Antenna to the Supension

4ea M8 Nuts and washers

122

B4008 Rev. M

ODU Type III Installation 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

B4008 Rev. M

123

CityLink STEP 2 Note! Mounting sequence is important!

M8 Screws,nuts and washers

M8 Screws,nuts and washers

124

B4008 Rev. M

ODU Type III Installation 4.3

Mounting the CityLink III ODUs to the Antenna Assembly

LATCHES (1 in each corner of each ODU)

B4008 Rev. M

125

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

126

B4008 Rev. M

ODU Type III Installation

5.0

Cable Connections ODU BOTTOM VIEW: IDU - ODU Cable Connector, N-50W For details please see Figure V-7.

Pressure equalizer

AGC Connector. In a 1+1 configuation, this connector is used for interconnection between the two ODUs.

B4008 Rev. M

Ground connection. Attach grounding cable (10mm2) to this point with the M6 nut and washers.

127

CityLink

6.0 6.1

Antenna Alignment Azimuth and Elevation Adjustment

Azimuth Adjustment Torque: 110-120Nm

• Unlock securing nut approx. 1 turn before azimuth adjusting • Adjust azimuth • Lock securing nut after adjustment

Elevation Adjustment • Unlock securing nut approx. 1/2 turn before elevation adjusting • Adjust elevation • Lock securing nut after adjustment

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 until maximum 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.

128

B4008 Rev. M

ODU Type III Installation 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.

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 be mounted 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 realigned according to prior procedures.

Horizontal Polarisation: When the H mark is in upwards position, this shows that the antenna is Horizontal Polarized

Water level

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

B4008 Rev. M

129

CityLink Vertical Polarisation:

When the V mark is in upwards position, this showes that the antenna are Vertical Polarised

Water level

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

130

B4008 Rev. M

IDU Installation

SECTION V IDU Installation

64kb/s 64kb/s SVCE Phone Phone 64kb/s 2Mb/s 2Mb/s SVCE SVCE Phone G.703 Ext. 1 11 G.703Wayside WaysideExt. Ext.

POWER 1

POWER POWER2 POWER

ODU ODU

B4008 Rev. M

-48VDC -48VDC -48VDC

NI NI NI 111 155 Mb/s LINE 155 Mb/s LINE 155 Mb/s LINE RXDIRA

G.703 G.703

PWR PWR1 PWR 2

RXDIRB

INP INP OUT OUT 64kb/s 2MHz 2MHz SVCE SVCE10BaseT 10BaseT 2MHz SVCE 64kb/s 64kb/s V.11 Sync. Sync. Ext. Ext. LAN Sync. 2 2 LAN V.11

IDU- HSB - HSBINTFC INTFC IDU IDU INTFC

CALL CALL CALL

ALM&& &AUX AUX ALM ALM AUX

LCT LCT LCT

NI NI NI 22

TXDIRA TXDIRB

CRITICAL CRITICAL CRITICAL MAJOR MAJOR MAJOR MINOR MINOR MINOR WARNING WARNING WARNING

131

CityLink

1.0

General This 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 information 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-owned cargo containers should be used.

132

B4008 Rev. M

IDU Installation 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 corresponds to the components required for the installation, i.e. correct antenna and 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 controlled 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 transportation 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 minimise condensation during transportation. This is to be removed at installation. No maintenance is required when stored according to particulars above.

B4008 Rev. M

133

CityLink

2.0 2.1.

IDU Installation 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. See Figure 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.

ANSI Rack Adapter

ETSI Rack Adapter

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

64kb/s 64kb/s 2Mb/s SVCE Phone Phone 2Mb/s SVCE G.703 G.703Wayside WaysideExt. 1 1 Ext.

POWER 1

POWER POWER2 POWER

ODU ODU

-48VDC -48VDC

NI NI 11 155 Mb/s LINE 155 Mb/s LINE G.703 G.703

PWR PWR1 PWR 2

RXDIRA

CRITICAL CRITICAL CRITICAL

RXDIRB

MAJOR MAJOR MAJOR

INP INP OUT OUT 2MHz SVCE SVCE10BaseT 10BaseT 64kb/s 64kb/s 2MHz Sync. Ext. V.11 Sync. Ext. 2 2 LAN LAN V.11

MINOR MINOR MINOR

IDU IDU- HSB - HSBINTFC INTFC

CALL CALL CALL

ALM&&AUX AUX ALM ALM AUX

LCT LCT LCT

NI22 NI NI

TXDIRA TXDIRB

WARNING WARNING W ARNING

FLAT WASHER WASHER M6x12

Figure V-2 Mounting the IDU in a Rack 134

B4008 Rev. M

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

B4008 Rev. M

135

CityLink

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 by using 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.

IDU A 64kb/s 64kb/s 2Mb/s 2Mb/s SVCE SVCE Phone Phone G.703 1 1 G.703Wayside WaysideExt. Ext.

POWER 1

POWER POWER2 POWER

ODU ODU

64kb/s 64kb/s 2Mb/s 2Mb/s SVCE SVCE Phone Phone G.703 G.703Wayside WaysideExt. Ext. 1 1

POWER POWER2 POWER

ODU ODU

ALM&&AUX AUX ALM ALM AUX

NI22 NI NI

LCT LCT

TXDIRA TXDIRB

WARNING WARNING

NI NI 11

RXDIRA RXDIRB

INP INP OUT OUT

CRITICAL CRITICAL MAJOR MAJOR MINOR MINOR

IDU IDU- HSB - HSBINTFC INTFC

CALL CALL

ALM ALM&&AUX AUX

NI NI 22

LCT LCT

TXDIRA TXDIRB

WARNING WARNING

RXDIRA

CRITICAL CRITICAL MAJOR MAJOR MAJOR

NI NI NI11 155 Mb/s LINE 155 Mb/s LINE G.703 G.703

PWR PWR1 PWR 2

RXDIRB

INP INP OUT OUT SVCE10BaseT 2MHz SVCE 10BaseT 64kb/s 2MHz 64kb/s Sync. Ext. LAN Ext. 2 2 LAN V.11 Sync. V.11

-48VDC -48VDC

CALL CALL CALL

155 Mb/s LINE 155 Mb/s LINE

2MHz SVCE SVCE10BaseT 10BaseT 64kb/s 64kb/s 2MHz Sync. Ext. Ext. 2 2 LAN LAN V.11 V.11 Sync.

64kb/s 64kb/s 2Mb/s 2Mb/s SVCE SVCE Phone Phone G.703 WaysideExt. Ext. 1 1 G.703Wayside

CRITICAL CRITICAL CRITICAL MAJOR MAJOR MAJOR MINOR MINOR MINOR

IDU HSBINTFC IDU - -HSB IDU HSB INTFC

G.703 G.703

PWR PWR 1 2

-48VDC -48VDC

POWER 1

RXDIRA RXDIRB

INP INP OUT OUT 2MHz SVCE SVCE10BaseT 10BaseT 64kb/s 64kb/s 2MHz 2 2 LAN Sync. Ext. Ext. LAN V.11 V.11 Sync.

-48VDC -48VDC

POWER POWER 2

NI NI 111 155 Mb/s LINE 155 Mb/s LINE G.703 G.703

PWR PWR1 PWR 2

POWER 1

ODU

HSB-IDU

IDU IDU- HSB - HSBINTFC INTFC

CALL CALL

ALM ALM&&AUX AUX

LCT LCT LCT

TXDIRA TXDIRB

NI NI 222

MINOR MINOR MINOR WARNING WARNING WARNING

IDU B

M6x12

FLAT WASHER WASHER

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

IDU A

HSB-IDU

64kb/s 2Mb/s SVCE G.703 Wayside Ext. 1

Phone

NI 1 155 Mb/s LINE CRITICAL

POWER

MAJOR

PWR

MINOR WARNING

ODU

64kb/s V.11

-48VDC

SVCE 10BaseT Ext. 2 LAN

64kb/s 2Mb/s SVCE G.703 Wayside Ext. 1

POWER 1

POWER2 POWER

2MHz Sync.

IDU - HSB INTFC

CALL

ALM & AUX

LCT

Phone

NI 2

NI 1 155 Mb/s LINE G.703

PWR PWR1

ODU

64kb/s V.11

-48VDC

RXDIRA

CRITICAL

RXDIRB

MAJOR

INP OUT

MINOR

2 2MHz Sync.

SVCE 10BaseT Ext. 2 LAN

64kb/s 2Mb/s SVCE G.703 Wayside Ext. 1

IDU - HSB INTFC

CALL

ALM & AUX

LCT

Phone

NI 2

TXDIRA TXDIRB

WARNING

NI 1 155 Mb/s LINE CRITICAL

POWER

MAJOR

PWR

MINOR WARNING

ODU

-48VDC

64kb/s V.11

2MHz Sync.

SVCE 10BaseT Ext. 2 LAN

IDU - HSB INTFC

CALL

ALM & AUX

LCT

NI 2

IDU B FLAT WASHER WASHER M6x12

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

B4008 Rev. M

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. Y-Cable

IDU A HSB IDU IDU B

Figure V-5 Interconnections in a Hot Standby System

WARNING! If the Y-cable connectors marked with IDU A and IDU B are swapped, the IDUs must always be rebooted after this operation.

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

B4008 Rev. M

137

CityLink

4.0

Installation of Optional Extension Boards 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.

Step 1 Remove the four screws that holds the lid

Step 2 Use a flat screwdriver to carefully remove the lid.

138

B4008 Rev. M

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.

B4008 Rev. M

139

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

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.

140

B4008 Rev. M

IDU Installation

5.0

IDU/ODU Cable Installation Both 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. Cable Type

DC resistance R

FSJ1-50A

16.3 Ω/km

If the length is 100 m minimum voltage to IDU must be

If the length is 200 m minimum voltage to IDU must be

If the length is 300 m minimum voltage to IDU must be

90 m (-40.5 V)* 100 m (-40.7 V) Dev. 0.2V

Bending radius 25 mm

200 m (-43.5 V)

See Note 1

300 m (-46.0 V)

LDF1-50 See Note 2

8,48 Ω/km

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

LCF14-50J See Note 3 LCF38-50J See Note 4

9.6 Ω/km

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

75 mm 300 m (- 42.5 V) 40 / 120 mm single / rptd 300 m (-42.9 V)

5.0 Ω/km

50 / 95 mm single / rptd

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

Table V-1

Cable length limitation due to different DC resistance

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) can not be used. Only the cable type LCF38-50 with solid copper inner conductor must be used (RFS part no. 152 225 11). IDU to ODU Coax Cable 1 2 3 4 5 6

Cable Kit 100 m LCF14-50 Cable Kit 150 m LCF14-50 Cable Kit 200 m LCF14-50 N-Connector Kit Preparation Tool for LCF14 For cable run 200 –300 m: Cable & Connector Kit 300 m LCF38-50

7

Extra Connector Kit

8

Preparation Tool for LCF38

Table V-2

B4008 Rev. M

100 m ¼” Coax Cable including 200 Cable Ties 150 m ¼” Coax Cable including 300 Cable Ties 200 m ¼” Coax Cable including 400 Cable Ties Connectors for IDU & ODU and Cable Grounding Easy cable preparation for connector attachment

85W5147-100 85W5147-150 85W5147-200 87K5148-N 85W5147-TL

300 m 3/8” Coax Cable including 600 Cable Ties and Connectors for ODU & IDU including jumper cable and Cable Grounding Kit Connectors for ODU & IDU including jumper cable and Cable Grounding Kit Easy cable preparation for connector attachment

85W5011-K300 87K5013-1A 85W5011-TL

Selected Coax Cables and Connector Kits

141

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.

142

B4008 Rev. M

IDU Installation Antenna

ODU

Grounding point. (See Figure V-8)

2a

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

3a 1

1a

2b

1 2c

IDU A

3c Tower Structure

HSB-IDU IDU B

4

3b Equipment Earthing Bar

Buried Earthing Network

Item

Description

Part No.

Remarks

1 1a 2a 2b 2c 3a 3b 3c 4

Coax Cable Cable Tie Connector, N-male, straight for ODU Connector, N-male, angle for IDU Grounding Kit for coax cable Grounding Cable for ODU Grounding Cable for IDU Grounding Jumper Cable IDU/SW DC Power Supply Cable

See Table V-1, -2a & -2b

Supplied as Cable Kit, cable with ties (2 per m).

See Table V2a & -2b

Supplied as Connector Kit.

UWA7

Supplied as separate kit UWA7.

UWMK5051

Included in IDU connection kit and HSB IDU interconnection kit.

Figure V-6

B4008 Rev. M

Cable Arrangement, Mandatory Items

143

CityLink BOTTOM OF BRANCHING UNIT

OUTDOOR UNIT ODU

N - CONNECTOR female, chassis

SEALING 75N06D-1

BOTTOM OF BRANCHING UNIT

N - CONNECTOR male, cable

APPLY SEALING COMPOUND HERE

PROTECTION SLEEVE

HOSE CLAMP 97Z6A-5 N - CONNECTOR

PROTECTION SLEEVE 97E12A-1 HOSE CLAMP

NOTE: (NOTE 1) ALL CODED ITEMS ARE INCLUDED IN KIT ABZ278

CABLE CONNECTION 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.

Figure V-7 144

Coax Cable Connection B4008 Rev. M

IDU Installation WARNING! Do not use the Branching Unit's sealing screw for grounding purpose.

Attach grounding cable (10mm2) to this point with the M8 nut and washers. Figure V-8

Branching Unit Grounding Point

WARNING! Do not use the Branching Unit's sealing screws for grounding purpose.

Attach grounding cable (10mm2) to this point with the M6 nut and washers. Figure V-9 B4008 Rev. M

Hot Standby and 2+0 DF-SP Branching Unit Grounding Point 145

CityLink

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.

This page is intentionally left blank. 146

B4008 Rev. M

Preparations for Operation

SECTION VI Preparations for Operation

B4008 Rev. M

147

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 • •

1.2

Voltmeter for AGC voltage monitoring (with cable to connect to BNC-connector) Cable for connection between AGC monitoring point and voltmeter.

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 on Apply 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.

148

B4008 Rev. M

Preparations for Operation 2.1

NEW-NMS/NEW-Configurator Startup and connecting to Network Elements The NEW-NMS/NEW-Configurator (Nera Element vieW-Network Management 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: admin Password: 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 automatically 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

B4008 Rev. M

149

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: admin Password: adminpasswd It 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 connection to the network element, select Communication from the Configuration 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)

150

B4008 Rev. M

Configuration with NEW-Configurator

SECTION VII Configuration by NEW Configurator

B4008 Rev. M

151

CityLink

1.0

General This 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 View which can be launched by selecting Explore Net from the View menu. Configuration of Network Elements is achieved using a set of propertysheets. 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 Configuration menu. The property-sheets are divided into two categories by means of functionality: Configuration Property sheets with Multiple Settings: The program retrieves the current settings from the NE when the propertysheet 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: Set: Close: Help:

Retrieves the current settings from the NE. Sends the current settings to the NE. Closes the property-sheet without saving or setting any data Displays help for the active property-page.

. 152

B4008 Rev. M

Configuration with NEW-Configurator • To change the settings: 1 Get the current settings from the NE by pressing Get. The current NE settings are automatically retrieved when the propertysheet 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 immediately 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. 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.

Figure VII-3 Configuration property sheet information field

B4008 Rev. M

153

CityLink

2.0 2.1

Element Node 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 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 Element Id from the Configuration menu.

Figure VII-4 Element ID Configuration Sheet

154

B4008 Rev. M

Configuration with NEW-Configurator Fields:

Description:

Serial number: NE type: Name: Section address: NE address:

The serial number of the NE. (Not editable) The type of NE. (Not editable) The name of the NE (max. 32 characters) The section address of the NE. (1-254) The NE address (1-128). Used for identification of NEs within a section. The Media Access Control address of the NE. Used for OSI-Management. (Not editable) The Network Service Access Point address of the NE. Used for OSI-Management. The Internet Protocol address of the NE. This field is checked if the NE is a hot standby element.

MAC address: NSAP address: IP address Hot standby:

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. 3 Press Set to send the changes to the NE.

B4008 Rev. M

155

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 equipment 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

Fields: Automatic transmitted power control (ATPC) IP stack Synchronous equipment timing source Simple network management protocol (SNMP) 64 Kbit/s channels 2 Mbit/s wayside channel Alarm auxiliary function

Description: ATPC is a function for effectively reducing interference probabilities.. The NE has an integrated IP stack. Synchronous equipment timing source is (SETS) available. An SNMP management agent is available. Two 64 Kbit/s channels can be inserted into the STM-1 Section Overhead (SOH ). One 2Mbit/s wayside channel can be inserted into the STM-1 Section Overhead (SOH ). A unit containing an auxiliary alarm unit and an auxiliary output unit is available.

STM-1 156

B4008 Rev. M

Configuration with NEW-Configurator 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 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 Notifications from the Configuration menu.

Figure VII-6

B4008 Rev. M

Notifications Configuration Sheet

157

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 severity Critical

Major Minor

Warning

158

(When the Alarm Events is disabled, these functions are inactive) When checked, Alarm notifications will be sent from the NE to the program if Critical alarms occur. When checked, Alarm notifications will be sent from the NE to the program if Major alarms occur. When checked, Alarm notifications will be sent from the NE to the program if Minor alarms occur. When checked, Alarm notifications will be sent from the NE to the program if Warnings occur.

B4008 Rev. M

Configuration with NEW-Configurator 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 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 NE Clock from the Configuration menu.

Figure VII-7 NE Clock Configuration Sheet

Fields:

Description:

The NE's Clock:

The Date and Time retrieved from the Network Element. The difference between the PC clock and the Network Element Clock.

Difference from

B4008 Rev. M

159

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 can also be invoked by selecting (highlighting) the Element node in the Explorer view and then selecting Edit SW Download from the Configuration 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.

160

B4008 Rev. M

Configuration with NEW-Configurator 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 SW Download) 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 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 SW Versions from the Configuration menu.

Figure VII-8 SW Version Configuration Sheet

B4008 Rev. M

161

CityLink Fields:

Description:

SW Component Bank Revision Status

Name of the software Software location Software revision 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.

162

B4008 Rev. M

Configuration with NEW-Configurator

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 configuration of 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 the Configuration menu.

Figure VII-9 Section Termination Configuration Sheet

Fields:

Description:

Regular channels: Protection channels: Regular co. channels: Protection co. channels: Channels: Channel Termination

The Number of Regular Channels. The Number of Protection Channels. The Number of Regular Co. Channels. The Number of Protection Co. Channels. List of NE Channels with the channel properties. Name of the channel. MS (Multiplexer section) or RS (Regenerator Section) (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.

To change the settings: 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. B4008 Rev. M

163

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 includes the 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 Transmission node in the Explorer view and then selecting Edit Transmission Configuration from the Configuration menu.

Figure VII-10 Section Termination Configuration Sheet

164

B4008 Rev. M

Configuration with NEW-Configurator Fields:

Description:

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 XConnect 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 software 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 its output. 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 XConnect Extension Board is present.

B4008 Rev. M

165

CityLink

166

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 to enter 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 the Clock Priority list view. This field will only be enabled whenever the Element 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

Configuration with NEW-Configurator Clock Quality This is the third column in the Clock Priority list view. This field will only be enabled whenever the Element 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 content of 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 the Clock 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 the Clock Priority list view. This field presents the currently active clock. The field is updated 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:

B4008 Rev. M

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

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 168

B4008 Rev. M

Configuration with NEW-Configurator 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-12 Transmission Configuration, MST Lower Order Path Termination - LOPT: With this configuration the SDH structure is assumed to have a VC-12 mapping and the the equipment will monitor and regenerate B1, M1 REI, B2 and BIP-2 pulses. Figure VII-13 shows how the dialog looks when this setting is applied.

Figure VII-13 Transmission Configuration, LOPT B4008 Rev. M

169

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.

Figure VII-14 Transmission Configuration, Enable X-Connect 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-15 Transmission Configuration, Enable DS3/E3 170

B4008 Rev. M

Configuration with NEW-Configurator 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 configured from the “Frame Structure” page.

Figure VII-16 Transmission Configuration, Enable 21x2

B4008 Rev. M

171

CityLink 3.1.3

SSM - Synchronization Status Message The SSM sheet is used to monitor the received S1-byte in the two STM1 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-17 The SSM Configuration Sheet

Fields:

Description:

Direction

From which STM-1 direction the S1 byte is monitored. This can be either Line or Radio Will show the last time the specific S1 byte changed it’s value. The current content of the specific S1 byte. A human readable interpretation of the S1 byte. These can be:

Last change S1 byte Description

172

B4008 Rev. M

Configuration with NEW-Configurator S1 byte 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111

3.2

SDH synchronization quality level description Quality unknown (existing sync network) Reserved G.811 Reserved G.812 transit Reserved Reserved Reserved G.812 local Reserved Reserved Synchronous equipment timing source (SETS) Reserved Reserved Reserved Do not use for synchronization

Alarm Indication Signal Insert (For advanced users) The Path Trace functionality and the AIS (Alarm Indicator Signal) functionality 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.

B4008 Rev. M

173

CityLink

Figure VII-18 AIS Insert Configuration Sheet

Fields:

Insert AIS when Viterbi HBER threshold exceeded

An AIS is inserted when the Viterbi HBER threshold is exceeded. (See Chapter 4.4.9 for setting of BER threshold.)

Insert AIS when trace mismatch

An AIS is inserted when there is a mismatch between the Trace String set in the Path Trace sheet and Trace String set on this sheet.

Insert AIS when RF ID mismatch

An AIS is inserted when there is a 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)

174

Subfields: Description:

Not used

The Regenerator Section Trace String is not used. Fixed byte The Regenerator Section Trace String is one byte ( =8 bit) long. B4008 Rev. M

Configuration with NEW-Configurator 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 contains the same values as the Trace string in the Path 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:

B4008 Rev. M

(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 inserted if the Insert AIS when RF ID mismatch box is checked. The Expected field normally contains 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. 175

CityLink 3.3

Path Trace (For advanced users) The Path Trace functionality and the AIS (Alarm Indicator Signal) functionality 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) the one of the Transmission Radio and Line Tx nodes in the Explorer view and then selecting Edit Path Trace from the Configuration menu.

Figure VII-19 Path Trace Configuration Sheet

176

B4008 Rev. M

Configuration with NEW-Configurator 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 Trace String 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.

B4008 Rev. M

177

CityLink

4.0 4.1

Equipment Node 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 Configuration 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 the Configuration menu.

178

B4008 Rev. M

Configuration with NEW-Configurator

Figure VII-20 Routing Table Configuration Sheet, Active Tab (top) and Initial Tab (bottom)

B4008 Rev. M

179

CityLink Fields:

Description:

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. The Section number of the addressed NE (1-128). 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). 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) A computed weight that gives an indication of the communication capacity to the destination network element. A high number denotes a longer response time.

Section NE

Port

Weight

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.

180

B4008 Rev. M

Configuration with NEW-Configurator 4.2

IP Routing Static Routes Maximum 20 static routes can be configured on a Nera OSPF router. Active Routes An Nera OSPF router supports approximately 200 active routes. OSPF areas It is not recomended to have more than 25 OSPF routers per OSPF area. Each area may export up to 8 address ranges. Fixed configuration options The Nera OSPF implementation is not a dedicated router implementation and as such some parameters that would normally be configurable are fixed. For interoperability with other equipment it is however sometimes important that the configuration of external equipment match these values. Name Inject default route into stub area Router dead interval Hello interval Retransmit delay Retransmit interval Authentication

Value YES 40 sec 10 sec 1 sec 5 sec NO

Limitations This implementation supports a basic implementation of OSPF v.2 (RFC 2823). It does not support virtual links and MD5 authentication. Other options This implementation supports a rudimentary mechanism for distribution of static and RIP2 routes. The implementation also supports exporting routes to RIP2.

B4008 Rev. M

181

CityLink 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 the Rip Interfaces and OSPF Interfaces property pages.

Figure VII-21 IP Routing Configuration Sheet,General Settings

182

B4008 Rev. M

Configuration with NEW-Configurator 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 information 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 for the OSPF Interfaces: 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).

B4008 Rev. M

183

CityLink 4.2.2

Active Routes Monitor active routes for current NE from this page.

Figure VII-22 IP Routing Configuration Sheet, Active Routes

184

B4008 Rev. M

Configuration with NEW-Configurator 4.2.3

Static Routes Edit static routes regarding IP Routing using this page.

Figure VII-23

IP Routing Configuration Sheet, Static Routes

Property page controls: Add: Edit:

Add a new static route to the list using the appearing dialog. 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.

B4008 Rev. M

185

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

Property page controls: Add: Edit:

Add a new RIP interface to the list using the appearing dialog. 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. Delete: Deletes the selected row(s) from the list. Note! Changes to the RIP Interfaces are not transferred to the NE before ‘Set’ is pressed.

186

B4008 Rev. M

Configuration with NEW-Configurator 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

Property page controls: Add: Edit:

Add a new OSPF interface to the list using the appearing dialog. 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. Delete: Deletes the selected row(s) from the list. Note! Changes to the OSPF Interfaces are not transferred to the NE before ‘Set’ is pressed.

B4008 Rev. M

187

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. Delete: Deletes the selected row(s) from the list. 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.

188

B4008 Rev. M

Configuration with NEW-Configurator 4.3 4.3.1

Communication Ports 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 Explorer view and then selecting Edit Communication Ports from the Configuration menu.

Fields:

Choices:

Description:

Figure VII-27 DCC Tab in Communication Ports Configuration Sheet

B4008 Rev. M

189

CityLink Enabled Channel: Ch. 1-Ch XX

Switches the DCC communication ports on/off. The Channel where the DCC are inserted in the SOH. CityLink has only one channel. This field will always be ‘Ch. 1’ at CityLink.

Direction Line Radio Timeslot:

DCC Line is inserted the line side of the radio. DCC Radio is inserted the radio side of the radio. 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

QECC TCP/IP LAPD

Network side User side PPP:

Active mode Demand dial Direct mode Passive mode

190

NERA Stack. Nera stack is always enabled on the radio side (DCC Radio). QECC Stack TCP/IP Stack Data link layer for the QECC protocol. For more information refer to ITU-T G.784 and ITU-T Q.921. Server for the LAPD requests. Client for the LAPD requests. (Point to Point Protocol) Data link layer for the TCP/IP protocol. (currently not implemented) (currently not implemented) (currently not implemented) (currently not implemented) (currently not implemented)

B4008 Rev. M

Configuration with NEW-Configurator 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. The Communication Ports configuration sheet can be opened from the Configuration context menu of the Equipment node in the Explorer view. 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 Configuration menu.

Figure VII-28 NI Tab in Communication Ports Configuration Sheet

B4008 Rev. M

191

CityLink Fields: Enabled Function

Choices: CityLink NL29x NI NL29x Qx PDH Synchronous PDH Asynchronous V.11 contra dir master V.11 contra dir slave V.11 co dir Q1 V.11 NL29x V.11 contra dir slave

Baudrate

1200 to 200000

Description: Enables the NI port The functionality of the NI port. The baud rate and stack are grayed/whitened to indicate which settings are necessary for the different functionalities.

The baud rate (symbols pr. second) of the NI port. If the field is grayed, no baud rate is necessary to set. Baud

Stack Nera OSI LAPD

Network side User side PPP:

Active mode Demand dial Direct mode Passive mode

192

NERA Stack. OSI Stack Data link layer for the QECC protocol. For more information refer to ITU-T G.784 and ITU-T Q.921. Server for the LAPD requests. Client for the LAPD requests. (Point to Point Protocol) Data link layer for the TCP/IP protocol. (currently not implemented) (currently not implemented) (currently not implemented) (currently not implemented) (currently not implemented)

B4008 Rev. M

Configuration with NEW-Configurator 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. The Communication Ports configuration sheet can be opened from the Configuration context menu of the Equipment node in the Explorer view. Press the LCT tab to view/change the LCT 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.

Figure VII-29 LCT Tab in Communication Ports Configuration Sheet

B4008 Rev. M

Fields:

Choices:

Description:

Baudrate:

1200 - 115200

Baudrate. The default baudrate is 115200.

193

CityLink 4.3.4

Ethernet In the CityLink Radio the Ethernet port can be Enabled only if the NI 2 port is Disabled, and vice versa. See chapter 4.3.2. The Communication Ports configuration sheet can be opened from the 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.

Figure VII-30 Ethernet Tab in Communication Ports Configuration Sheet

194

Fields:

Choices:

Enabled Stack

Description:

Toggles Ethernet on/off OSI TP4 OSI Stack TCP/IP TCP/IP Stack. Must be selected if IP Tunneling is enabled.

B4008 Rev. M

Configuration with NEW-Configurator 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. The Communication Ports configuration sheet can be opened from the Configuration context menu of the Equipment node in the Explorer view. Press the IP Settings 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 Configuration menu.

Figure VII-31 IP Settings Tab in Communication Ports Configuration Sheet

Fields:

Description:

IP address Subnet mask

Shows the Internet Protocol (IP) address of the NE. Type the Subnet Mask number obtained from your network administrator. This number, combined with the IP address, identifies which network your NE is on. 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 functionality will be limited to the local subnet unless a route is specified with the TCP/IP route command.

Default gateway

B4008 Rev. M

195

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 tunnels to other NEs. The IP tunnel must only be set up at one side of the tunnel. The Communication Ports configuration sheet can be opened from the Configuration context menu of the Equipment node in the Explorer view. 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.

Figure VII-32 IP Tunneling Tab in Comm. Ports Configuration Sheet

Fields:

Choices: Description:

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

B4008 Rev. M

Configuration with NEW-Configurator 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 NE address are used for set up of IP tunnels to other NEs. The Communication Ports configuration sheet can be opened from the Configuration context menu of the Equipment node in the Explorer view. 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 Communication Ports from the Configuration menu.

Figure VII-33 OSI TP4 Tunneling Tab in Comm. Ports Configuration Sheet

Fields:

Choices: Description:

Enabled: On/Off Remote section address: Remote NE address: Remote NSAP address: B4008 Rev. M

Toggles OSI Tunneling on/off Shows the section address of the NE addressed though OSI TP4 Tunnel Shows the SU address of the NE addressed though OSI TP4 Tunnel 0 to 20 bytes 197

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 invoked by selecting (highlighting) the Equipment node in the Explorer view and then selecting Edit Looping from the Configuration menu.

Figure VII-34 Looping Configuration Sheet

198

B4008 Rev. M

Configuration with NEW-Configurator Fields:

Description:

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 (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) Displays the time of which all main traffic loops in the NE will be cleared. This time is set by the user when activating a loop.

Loops will be automatically cleared after:

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.

B4008 Rev. M

199

CityLink 4.4.2

64 Kbit/s Looping The Looping configuration sheet can be opened from the Configuration 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

200

B4008 Rev. M

Configuration with NEW-Configurator Fields: 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 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 help on an item, click at the top of the dialog box, then click the item.

B4008 Rev. M

201

CityLink 4.4.3

2 Mbit/s Wayside Looping The Looping configuration sheet can be opened from the Configuration 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 also be invoked by selecting (highlighting) the Equipment node in the Explorer view and then selecting Edit Looping from the Configuration menu.

Figure VII-36 Looping Configuration Sheet, Wayside Tab

202

B4008 Rev. M

Configuration with NEW-Configurator Fields: 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 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.

B4008 Rev. M

203

CityLink PRBS Settings: PRBS Generator:

PRBS Check:

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. 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 is one 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: Close: Help:

204

Resets the PRBS Counter (includes the PRBS Rate) Closes the property sheet. 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

Configuration with NEW-Configurator 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. The Looping configuration sheet can be opened from the Configuration 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 Configuration menu.

Figure VII-37 Looping Configuration Sheet, 21x2Mbit/s Tab

B4008 Rev. M

205

CityLink Fields:

Description:

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 checkboxes. If the user clicks a cell that isn’t checked, a Loop Timer dialog will be launched (see Figure VII38). 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

206

B4008 Rev. M

Configuration with NEW-Configurator To change the settings:

.

1 First, double-click the desired cell in the Looping type column. A combobox with the available loops will be shown over the cell. 2 Select a looping type from the combobox’s drop down list. Click anywhere outside the cell in question to apply the setting 3 Click on the ON/OFF checkbox of the loop item in question. A Loop Timer dialog will be launched (see Figure VII-38). 4 In the Loop Timer dialog set the desired expire time for the loop item in question and close this dialog by clicking the OK button. 5 The checkbox of the loop item in question will now have been checked. The Remaining time cell of the loop item in question will be updated every 5th second with the remaining time of the loop. 6 To clear a loop just click the checked checkbox of the loop item in question. Note: Every altered setting to any item in the list will be applied the target immediately.

4.4.5

DS3/E3 Looping The DS3/E3 card includes three PDH ports, each of which supports looping. The card supports Far End Loop, Near End Loop, PRBS insertion and PRBS verification. The loops are available when the PDH Ports on the DS3/E3 card have been configured to add or drop traffic. A PRBS signal can be inserted on all three PDH ports instead of the regular traffic. The incoming PRBS signal can then be checked in order to verify the quality of the communication path. To check the quality of the signal, a PRBS counter is configured to count the errors on one of the PDH Ports in one of the DS3/E3 directions. An error is detected when the signal differs from the expected PRBS signal. The DS3/E3 card has one PRBS generator that can be muxed into either inbound or outbound direction on one or more ports simultaneously. The PRBS generator can be inverted. For E3 the PRBS polynom is 223 - 1 and for DS3 the PRBS polynom is 215 -1. The PRBS checker is available at one of the PDH ports in either inbound or outbound direction and can also check inverted PRBS signals.

B4008 Rev. M

207

CityLink The Looping Configuration Property sheet can be opened from the Configuration 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 .

Figure VII-39

Looping Configuration Sheet, DS3/E3

Property page controls: 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)

208

B4008 Rev. M

Configuration with NEW-Configurator 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.

B4008 Rev. M

209

CityLink 4.5 4.5.1

In Door Unit (IDU) 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 administrator can change the settings. This sheet is also used for calibrating the Optical Line interface. Calibration 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

Fields:

Description:

Article code: Serial no: HW revision: MAC address:

The Article Code The Serial number. Hardware revision The Media Access Control address of the NE. The date when the article was produced. The date when the article was tested. The date when the Factory Acceptance Test was found to be satisfactory.

Production date: Test date: FAT date:

210

B4008 Rev. M

Configuration with NEW-Configurator 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 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 64 kbit/s Channels from the Configuration menu.

Figure VII-41 64 kbit/s Channels Configuration Sheet

B4008 Rev. M

211

CityLink Fields:

Choices:

Description

Enabled Disabled

Enables the 64 kbit/s Channel. Disables the 64 kbit/s Channel.

Status:

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: Line Radio

Timeslot:

212

Choose the direction the 64 kbit/s Rx Channel should be extracted from. 64 kbit/s Rx is inserted from line SOH frames. 64 kbit/s Rx is inserted from radio SOH frames. Shows which timeslot in the SOH the 64 kbit/s Rx Channel occupy.

B4008 Rev. M

Configuration with NEW-Configurator 4.5.3

2 Mbit/s Wayside Channel A 2 Mbit/s channel can be inserted in the SOH in either line-direction or radiodirection. 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 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 2 Mbit/s Wayside from the Configuration menu.

Figure VII-42

2 Mbit/s Wayside Channel Configuration Sheet

Fields:

Options: Description:

Status

Enabled Disabled

Direction Line Radio

B4008 Rev. M

Enables the Wayside Channel Disables the Wayside Channel Choose the direction the Wayside Rx channel should be extracted from. The Wayside channel is extracted from line SOH. When the rate is set to DS1, the Line direction is not available. The Wayside channel is extracted from radio SOH.

213

CityLink Rate

E1 DS1 Coding

HDB3 AMI B8ZS Sensitivity

-30dB -36dB Cable Length

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. 2 Mbit/s 1.5 Mbit/s 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. Only available for E1 Only available for DS1 Only available for DS1 This field is only available when the NE is equipped with the DS3/E3 Extension Board and the DS1 rate is selected Only available for DS1 Only available for DS1 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

214

Press this button to view which timeslots in the SOH the Wayside channel occupies.

B4008 Rev. M

Configuration with NEW-Configurator 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 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 X-Connect from the Configuration menu.

Figure VII-43

B4008 Rev. M

SOH X-Connect Configuration Sheet

Fields:

Description:

Enabled/Disabled Line timeslot Radio timeslot

Switches SOH X-Connect on/off The time slot to bypass the SORP. The destination time slot.

215

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

216

Figure VII-44

Error Pulse Output Configuration Sheet

Fields:

Choices:

Enabled/Disabled Source

Toggles Error Pulse Output On/Off Only one source at 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.

Description:

B4008 Rev. M

Configuration with NEW-Configurator 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 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 Auxiliary Output from the Configuration menu.

Figure VII-45

B4008 Rev. M

Auxiliary Output Configuration Sheet

Controls:

Choices:

Description:

Output control radio buttons

Manual Control or Alarm Trigger

Manual relay status radio buttons

Closed or Open

Set the usage of the aux.output pin. (This will be disabled if the CityLink does not support alarm triggers.) If the aux. output is set to manual control, these buttons will be enabled, and can be used to manually control the state of the relay. 217

CityLink Controls:

Choices:

Equipment tree

Alarm trigger list

Add alarm button

Remove alarm button

Alarm triggered radio buttons

Closed or Open

Description: Displays and selects the alarms available for alarm triggers. This will be disabled if the aux. output is set to manual control. Displays the alarm triggers configured. This will be disabled if the aux. output is set to manual control. 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. Removes the currently selected alarm from the alarm trigger list. Disabled if the output is on manual control. If the aux. output is set to 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.

Buttons: 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 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.

218

B4008 Rev. M

Configuration with NEW-Configurator 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. Press Get 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

Module

Diagnose Configuration Sheet

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 at last reset/startup. DRAM OK/Not OK A write/read test sequence was performed at last reset/startup. SRAM OK/Not OK A write/read test sequence was performed at last reset/startup. Code FLASH OK/Not OK A write/read test sequence was performed at last reset/startup. Boot FLASH OK/Not OK A write/read test sequence was performed at last reset/startup. 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

219

CityLink 4.5.8

Self Test The Self Test function uses a two step procedure for testing the IDU. The first test sets a CMI loop, while the second test sets an IF loop. For both loops, a PRBS is created in the SORP and errors are counted and synchronization losses are registered as the signal returns from the loops. Press Test to start the Self Test. WARNING! When performing a Self Test the STM-1 traffic will be destroyed. The Self Test dialog box can be opened from the Configuration context menu of the IDU node in the Explorer view. The dialog box can also be invoked by selecting (highlighting) the IDU node in the Explorer view and then selecting Edit Self Test from the Configuration menu.

Figure VII-47

4.5.9

Selt Test Dialog Box

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 decide when alarms are generated. The threshold values can be changed by the user. Alarm Id HBER LBER EW-BER

220

Default value Indicator for BER > 1e-3 Indicator for LBER > 1e-6 Indicator for EW-BER > 1e-10

Alarm severity MAJOR MINOR WARNING B4008 Rev. M

Configuration with NEW-Configurator Internal proportions: HBER > LBER > EW The BER Threshold configuration sheet can be opened from the Configuration context menu of the Radio node under 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 the Configuration menu.

Figure VII-48

BER Threshold Configuration Sheet

Fields: Choices:

Description:

HBER

Error bit rate A Major alarm is generated when the Viterbi error rate exceeds the HBER threshold value. AIS is inserted when the HBER threshold value is exceeded. Error bit rate A Minor alarm is generated when the Viterbi error rate exceeds the LBER threshold value. Error bit rate. A Warning is generated when the Viterbi error rate exceeds the Error Warning threshold value.

1.0·10-3 - 1.0·10-10

LBER 1.0·10-3 - 1.0·10-11

EW

B4008 Rev. M

1.0·10-3 - 1.0·10-12

221

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

Fields:

OSI Configuration Sheet, Line Coding Tab

Description:

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.

222

B4008 Rev. M

Configuration with NEW-Configurator 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

B4008 Rev. M

OSI Configuration Sheet, Parameters Tab

223

CityLink Fields:

Subfield:

Description:

NSAP Address

Area ID Host ID End Selector

Subnet address. End system address. Type of service. Always 01.

Link state protocol buffer size Parameters

224

Transmitted buffer length size of IS hello-packets.(512-1492 bytes)

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 Communication Ports Configuration pages

B4008 Rev. M

Configuration with NEW-Configurator 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

B4008 Rev. M

OSI Configuration Sheet, Routing Table Tab

Fields:

Description:

Host Id Metric

End system address. Cost of path.

225

CityLink 4.5.10.4

OSI Interface Information There will be one line in the table for each channel enabled for OSI.

226

Figure VII-52

OSI Configuration Sheet, Interface Information Tab

Fields:

Description:

Id InterfaceName Media Status MTU Size

Numbering of interfaces in the network Network user Type of media Indication of connection status (Up or Down) Maximum transmission unit size

B4008 Rev. M

Configuration with NEW-Configurator 4.5.11

Laser Control 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 enabled or 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 Configuration context menu of the Optical Line node under the IDU node in the Explorer view. The sheet can also be invoked by selecting (highlighting) the Optical Line node under the IDU node in the Explorer view and then selecting Edit Laser Control from the Configuration menu.

Figure VII-503

B4008 Rev. M

Laser Control Configuration Sheet

227

CityLink Fields:

Buttons:

Description:

ALS: Enabled/Disabled Waiting Time

Toggles ALS On/Off (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: On Off Status:

228

(ALS disabled or not implemented) Manually turn the laser on. Manually turn the laser off. Shows the status of the Laser Unit.

B4008 Rev. M

Configuration with NEW-Configurator 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 the IDU (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

B4008 Rev. M

The IDU Replace Unit Wizard

229

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 duplex distance is fixed the Rx frequency will be automatically set. The corresponding Tx and Rx frequency must be set in the opposite NE. Note! Dual Frequency - Single Polarisation (DF-SP) requires two channels 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 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 Frequency from the Configuration menu.

Figure VII-55

230

Frequency Configuration Sheet

B4008 Rev. M

Configuration with NEW-Configurator Fields:

Description:

Frequency plan Coding

Select the desired frequency plan. The frequency plan must correspond to your transceiver. The coding function used in the modulator/ demodulator. These coding functions may be selectable depending on frequency plan: TCM (Trellis coded modulation) and TCM + 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 frequency plan Duplex Distance (MHz) The distance between the TX and the RX carrier frequency. Innermost Spacing (MHz)The distance between the highest selectable freqquency 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

• To change the settings:

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.

B4008 Rev. M

231

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 effectively 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

232

Power Configuration Sheet

B4008 Rev. M

Configuration with NEW-Configurator Fields:

Denomination: Description:

RF input level warning, high

dBm

The upper threshold value for when to generate an RF input level warning (Alarm no. 1504)

RF input level warning, low

dBm

The lower threshold value for when to generate an RF input level warning (Alarm no. 1504)

ATPC alarm level

dBm

Set the power level to use when an ATPC alarm occurs.

ATPC reference level

dBm

The wanted input level when ATPC is activated.

Mute output power Maximum output power

dBm

Maximum output power for transmitting

Manual output level

dBm

The output power level used when ATPC is not activated

ATPC status

ATPC Disabled/ Enabled

ATPC mode

ATPC can operate in four different modes: Automatic Regulation: The transceiver 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 alarm delay

B4008 Rev. M

Mutes the output power. No output power is sent.

Seconds

The ATPC alarm can be delayed from 1 to 15 seconds.

233

CityLink 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 administrator can change the settings. The ODU Production Data 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 Production Data from the Configuration menu.

Figure VII-57

Fields:

Description:

Article code: Serial no: HW revision: Sales order: Production date: Test date: FAT date:

The article code The serial number. Hardware revision The purchase order. The date when the article was produced. The date when the article was tested. The date when the Factory Acceptance Test was found to be satisfactory. The date when the Site Acceptance Test was found to be satisfactory.

SAT date: 234

ODU Production Data Configuration Sheet

B4008 Rev. M

Configuration with NEW-Configurator 4.6.2

Type II ODU

4.6.2.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 effectively 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-58

B4008 Rev. M

RF Power Configuration Sheet

235

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 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. Message info field: Displays status of data exchange between GUI and NE.

236

B4008 Rev. M

Configuration with NEW-Configurator 4.6.2.2

Frequency Settings 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 matched against 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).

Figure VII-59

B4008 Rev. M

Frequency Configuration Sheet

237

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, 64TCM 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. Message info field: Displays status of data exchange between GUI and NE.

238

B4008 Rev. M

Configuration with NEW-Configurator 4.6.2.3

DRO Tuning The XCVR Unit’s DRO Tuning property sheet is used to enable and disable DRO Tuning mode for the individual XCVR unit. The tuning of the DRO frequency is performed manually on the XCVR unit. See Chapter 4.6.2.2.

Disabled Tx tuning Rx tuning

Figure VII-60

Fields: DRO Tuning Mode: • Disabled: • TX Tuning: • RX Tuning: Status TX: Status RX:

B4008 Rev. M

DRO Tuning Configuration Sheet

Description: DRO Tuning mode is disabled for both DRO’s Enables DRO Tuning mode for TX DRO Enables DRO Tuning mode for RX DRO Displays information concerning frequency lock and screw direction for TX DRO Displays information concerning frequency lock and screw direction for RX DRO

239

CityLink 4.6.2.3

DRO Tuning Procedure

Tx Tuning

Rx Tuning

Figure VII-61

240

DRO Tuning Procedure

B4008 Rev. M

Configuration with NEW-Configurator 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

Figure VII-62 Selecting in Explorer View the Transceiver to be tuned

Figure VII-63

Frequency Configuration Sheet

See Chapter 4.6.2.2 for setting of frequency.

B4008 Rev. M

241

CityLink 4.6.2.3.2

DRO Tuning Highlight the actual Transceiver unit to be tuned. Right click and choose Configuration and DRO Tuning

Figure VII-64

Selecting DRO tuning from the Explorer View

Tx tuning

Disabled Tx tuning Rx tuning

Figure VII-65

DRO Tuning Configuration Sheet

Select Tx tuning in the DRO Tuning Mode field. Press the Set button. 242

B4008 Rev. M

Configuration with NEW-Configurator

Figure VII-66

DRO Tuning Configuration Sheet, Tx tuning

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.

B4008 Rev. M

243

CityLink Rx Tuning

Disabled Tx tuning Rx tuning

Figure VII-67

DRO Tuning Configuration Sheet

Select Rx tuning in the DRO Tuning Mode field. Press the Set button.

244

B4008 Rev. M

Configuration with NEW-Configurator

Figure VII-68

DRO Tuning Configuration Sheet, Rx tuning

The red arrow indicates which way to adjust the DRO. In addition, the Alarm LED on 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.

B4008 Rev. M

245

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.

Figure VII-69

Fields:

Production Data Configuration Sheet

Description:

Article code: Serial no.: HW revision: Production date:

Uniquely identifies the type of board/unit. The serial number of the board/unit. The hardware revision. When the production process was completed for this board/unit. Test date: When this product was tested by the factory testdepartment. Message info field: Displays status of data exchange between GUI and NE.

246

B4008 Rev. M

Configuration with NEW-Configurator 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 effectively 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

B4008 Rev. M

Power Configuration Sheet

247

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 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. Message info field: Displays status of data exchange between GUI and NE.

248

B4008 Rev. M

Configuration with NEW-Configurator 4.6.3.2

Frequency Settings 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 matched against 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).

Figure VII-71

B4008 Rev. M

Frequency Configuration Sheet

249

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. Message info field: Displays status of data exchange between GUI and NE.

250

B4008 Rev. M

Configuration with NEW-Configurator 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 administrator can change the settings. The ODU Production Data 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 Production Data from the Configuration menu.

Figure VII-72

Fields:

Description:

Article code: Serial no: HW revision: Sales order: Production date: Test date: FAT date:

The article code The serial number. Hardware revision The purchase order. The date when the article was produced. The date when the article was tested. The date when the Factory Acceptance Test was found to be satisfactory. The date when the Site Acceptance Test was found to be satisfactory.

SAT date: B4008 Rev. M

Production Data Configuration Sheet

251

CityLink 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 Configuration 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 Configuration menu.

Figure VII-73

Fields:

Antenna Data Configuration Sheet

Description:

Antenna code Gain

The antenna code. Unique code for each antenna type. 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. 252

B4008 Rev. M

Configuration with NEW-Configurator 4.6.5

ODU Replace Unit Wizard The Replace Unit Wizard simplifies the process of replacing an ODU. The wizard copies configuration data from “old” ODU to the “new” ODU. The wizard describes each step in the replacement process.

Figure VII-74

B4008 Rev. M

The ODU Replace Unit Wizard

253

CityLink

5.0

CityLink ADM

5.1

21x2 Mbit/s Extension Board

5.1.1

Drop or Continue The Drop or Continue sheet is used to drop or remove a 2Mbit/s stream(E1). The 21x2Mbit/s extension board supports 21 physical 2Mbit/s ports. The user can assign any VC-12, out of the 63 available in the STM1 structure, to a specific 2Mbit/s port on this board. From which direction the drop is to be taken must also be configurated. The Drop or Continue configuration sheet can be opened from the Configuration context menu of the 21x2 Extension board node in the Explorer view. The sheet can also be invoked by selecting (highlighting) the 21x2 Extension board node in the Explorer view and then selecting Edit Drop or Continue from the Configuration menu. Note: Even though the 21x2Mbit/s extension board is present in the equipment this dialog will not be shown if the 21x2Mbits/s extension board isn’t enabled. This enabling must be done in the Section Termination dialog which can be opened from the Configuration context menu of the Transmission node in the Explorer view.

Figure VII-75 254

The Drop or Continue Configuration Sheet B4008 Rev. M

Configuration with NEW-Configurator Fields:

Description:

Port Number

The physical port number on the 21x2Mbit/s extension board. VC-12 Number The VC-12 number that the 2Mbit/s PDH stream attached to the Port Number shall be routed to/from (the numbers in the parenthesis is the VC-12 given in KLM notation). It is possible to re-use a given VC-12 as long as the Direction is different. Direction This parmeter indicates which direction the VC-12 is to be routed to/from. It can either be line or radio. Configured Check this to add a drop or uncheck it to remove a drop. If the checkbox is checked a new dialog will be launched. This dialog is used to select the VC-12 Number and the Direction. This dialog is explained in chapter 4.13.1.1. Note1: If the user, by means of the VC-12 Selector Dialog, specifies a VC-12 and a direction that is already in use, the setting will not be applied! Note2: If one attempts to remove a dropped VC-12 that is in use by the clock synchronization in the Section Termination, the removing will be rejected!

Buttons: Clear selected item(s): With the mouse one can select one or several items in the listview. When items are selected, this button will be enabled. Click the button if you wish to uncheck the selected items. Modifications that leads to a mismatch between the dialog settings and the settings on the NE will be tagged with a «dirty» token; *. 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. B4008 Rev. M

255

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 an item in the Drop or Continue dialog.

Figure VII-76

The VC-12 Selector Dialog Box

Fields:

Description:

VC-12 # K

The VC-12 number. It must be in the interval [1,63]. The first of the three numbers in the KLM numbering 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 numbering 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 numbering 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.

256

B4008 Rev. M

Configuration with NEW-Configurator 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 direction, and protection traffic in opposite direction around the ring, and traffic is selected at each end of the path. So, SNCP supports multiple rings, and offers suitable solution for access and metro network 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.

B4008 Rev. M

257

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 the Configuration context menu of the 21x2 Extension board node in the Explorer view. The sheet can also be invoked by selecting (highlighting) the 21x2 Extension board node in the Explorer view and then selecting Edit PRBS Test from the Configuration menu.

Figure VII-77

258

The PRBS Test Check Configuration Sheet

B4008 Rev. M

Configuration with NEW-Configurator Fields:

Description:

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 doubleclick 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. 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 the same 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. 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!

B4008 Rev. M

259

CityLink 5.1.3

PRBS Test - Generators The PRBS Test - Generators sheet is used to set up which of the dropped 2Mbit/s tributaries that shall generate PRBS. All tributaries can insert PRBS simultaneously. The PRBS Test - Generators configuration sheet can be opened from the Configuration context menu of the 21x2 Extension board node in the Explorer view. The sheet can also be invoked by selecting (highlighting) the 21x2 Extension board node in the Explorer view and then selecting Edit PRBS Test from the Configuration menu.

Figure VII-78

260

The PRBS Test Generators Configuration Sheet

B4008 Rev. M

Configuration with NEW-Configurator Fields:

Description:

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 setting the 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 be inserted in the direction(s) specified by Direction. Insert inverted PRBS If this checkbox is checked all checked tributaries in the list will be inserted inverted PRBS. If not checked it’s assumed to not be inverted. 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!

B4008 Rev. M

261

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 the Production Data configuration sheet. Only an administrator can change the settings. The Production Data configuration sheet can be opened from the Configuration 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.

262

Fields:

Description:

Article Code Serial no. HW revision Production date Test date

The Article Code of the card/unit. The Serial number of the card/unit. Hardware revision of the card/unit. The date when the article was produced. The date when the article was tested.

B4008 Rev. M

Configuration with NEW-Configurator 5.2

DS3/E3 Extension Board

5.2.1

DS3/E3 Configuration The DS3/E3 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 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 a split 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 Configuration context menu of the DS3/E3 Extension Board node in the Explorer view. The sheet can also be invoked by selecting (highlighting) the DS3/E3 Extension Board node in the Explorer view and then selecting Edit DS3/E3 from the Configuration menu .

B4008 Rev. M

263

CityLink

Figure VII-79

DS3/E3 Configuration Sheet

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 established connection. 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. Close: Closes 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. 264

B4008 Rev. M

Configuration with NEW-Configurator 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

B4008 Rev. M

Virtual Containers

265

CityLink

Figure VII-81

DS3/E3 Frame Structure Configuration Sheet

Buttons: VC-3: VC-12: Get:

Set: Close: Help:

SDH: SONET:

266

Sets the current structure to VC-3. Sets the current structure to VC-12. 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). Press this button to send the settings to the NE. Closes the property sheet. 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. This button indicates that the transmission standard is set to SDH. This button indicates that the transmission standard is set to SONET.

B4008 Rev. M

Configuration with NEW-Configurator 5.3 5.3.1

ADM STM-1 Extension Board (X-Connect) 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 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 Transmission Configuration from the Configuration menu .

Figure VII-82

Frame Structure Configuration Sheet

Buttons: VC-3: VC-12:

B4008 Rev. M

Sets the current structure to VC-3. Sets the current structure to VC-12.

267

CityLink 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-Connect Configuration sheet can be opened from the Configuration context menu of the X-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 XConnect from the Configuration menu .

Figure VII-83 268

X-Connect Frame Structure Configuration Sheet B4008 Rev. M

Configuration with NEW-Configurator 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 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 established connection. Press this button to remove the connection. Cancel: Press this button to undo the current operation.

B4008 Rev. M

269

CityLink

6.0 6.1

Hot Standby 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.

Figure VII-84

6.1.1

Hot Standby Explorer view

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 functionality, like auxiliary outputs, are found in both places.

270

B4008 Rev. M

Configuration with NEW-Configurator 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 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 Element ID from the Configuration menu.

Figure VII-85 Element ID Configuration Sheet

B4008 Rev. M

271

CityLink Fields:

Description:

Serial number: NE type: Name: Section address: NE address:

The serial number of the NE. (Not editable) The type of NE. (Not editable) The name of the NE (max. 32 characters) The section address of the NE. (1-254) 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) and SD Hybrid (Space Diversity Hybrid)

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. 3 Press Set to send the changes to the NE.

272

B4008 Rev. M

Configuration with NEW-Configurator 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.

6.1.2.1

HSB 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 invoked by selecting (highlighting) the Equipment node in the Explorer view and then selecting Edit Looping from the Configuration menu.

Figure VII-86

B4008 Rev. M

HSB Looping Configuration Sheet

273

CityLink Fields: Loop buttons:

Loops will be automatically cleared after:

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) Displays the time of which all main traffic loops in the NE will be cleared. This time is set by the user when activating 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: 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.

6.1.2.2

HSB 64Kbit/s Looping Please refer to Chapter 4.4.2 (this Section).

6.1.2.3

HSB Wayside Looping Please refer to Chapter 4.4.3 (this Section).

274

B4008 Rev. M

Configuration with NEW-Configurator 6.1.3

Hot Standby Configuration The Hot Standby configuration sheet shows the switching configurations for the IDU-Switch. The Hot Standby configuration sheet can be opened from the Configuration context menu of the IDU-Switch node in the Explorer view. The sheet can also be invoked by selecting (highlighting) the IDU-Switch node in the Explorer view and then selecting Edit Hot Standby from the Configuration menu.

Figure VII-87

Fields:

Common Tab in Element ID Configuration Sheet

Description

Auto / manual: Active branch:

Select between automatic or manual hot standby switching Select which branch that should be active. Active branch is available in Manual mode only Switching mode: In Bidirectional mode both Tx and Rx direction switches at the same time. In Unidirectional mode Tx and Rx can switch independent of each other. Switching mode can only be set Automatic mode. In Manual mode, the switching mode is always Bidirectional. Status list: Displays the active branch(es) in the TX and RX directions and whether there are RX/TX alarms in any of the branches.

B4008 Rev. M

275

CityLink 6.1.4

Hot Standby Switching Criteria The Hot Standby Switching Criteria page shows the automatic switching criteria for the hot standby element, and enables the user to alter these criteria. The Hot Standby Switching Criteria page can be opened from the Configuration context menu of the IDU-Switch node in the Explorer view. The Hot Standby configuration sheet then appears, and the switching criteria page can be selected. The sheet can also be invoked by selecting (highlighting) the IDU-Switch node in the Explorer view and then selecting Edit Hot Standby from the Configuration menu. Note that setting switching criteria is only allowed on Citylink 2 Hot Standby elements running with IDU software version R3C or higher. Also, the switching mode set in the Hot Standby Config page must be set to Automatic.

Figure VII-88

Hot Standby Switching Criteria

Field descriptions: The page consists of two lists; one for each branch. Each list contains alarm names/categories and a checkbox for each name/category.

276

B4008 Rev. M

Configuration with NEW-Configurator Switching algorithm The following algorithm is applied in automatic switching mode: Compute the total severity factor of each branch (SA, SB) 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 = SB, 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 SB > SA, switch to SA if branch B is active. 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. 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.

B4008 Rev. M

277

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 now display an equipment tree with a single node. Bring up the Element ID dialog from the Configuration menu, and disable the Hot Standby checkbox. When the element is next power cycled, it will start up in 1+0 configuration. 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 is very 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 operation.

278

B4008 Rev. M

Fast Ethernet Configuration

SECTION VIII CityLink Fast Ethernet Configuration

B4008 Rev. M

279

CityLink

Hyperterminal & Telnet 1.0

Hyperterminal & Telnet Commands • First time configuration with hyper-terminal to IDU's LCTport. – 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

Login as admin with the password; adminpasswd

Note! NEW-NMS' security system has initially one user account: User ID: admin Password: adminpasswd It is strongly recommended to change this password!

280

B4008 Rev. M

Fast Ethernet Configuration

2.0

How to get this link alive Where 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.

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.

LAN 1

M o d u le

CityLink IDU

2 (1 .5 ) M b /s c irc u it 1 - 4

Ethernet Fast Extension EBoard th e rn e t T rib u ta ry (EEB)

CityLink IDU

2 (1 .5 ) M b /s c ircu it 1 - 4

Ethernet F a st Extension EBoard th e rn e t T rib u ta ry (EEB)

LAN 1

M o d u le

LAN 2

LAN 2

LAN 3

LAN 3

LAN 4

Figure VIII-2

2.2

LAN 4

Radio Connection

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.

B4008 Rev. M

281

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 alarms cls coldstart enter env exit gettime help list ping quit reboot settime tracert

Function lists alarms clear screen shutdown the system and make a cold start of the system enter submenu list environment variables exit submenu display system timezone, time and date get help on commands list available commands ping the specified host quit shell shutdown the system and reboot set system timezone, time and date trace route to target

Use "help " to get help on specific command. Example for usage of "Help": CityLink> help gettime gettime: display system timezone, time and date Usage: gettime CityLink> 282

B4008 Rev. M

Fast Ethernet Configuration 3.1

Top Level Commands, Example CityLink (radio)> alarms

B4008 Rev. M

Active alarms: TIME

ID

NAME

CLASS

STATE

Modem. 2001.11.19 11.04.50 2001.11.19 11.04.50 2001.11.19 11.04.50

1104 1103 1102

E-WARNING LBER HBER

WARNING MINOR MAJOR

Raised Raised Raised

Baseband 2001.11.19.11.04.50 2001.11.19.11.04.50 2001.11.19.11.04.50

32808 32809 32811

LOS_RR LOF_RR MS-AIS_INSERT_RR

MAJOR MAJOR MAJOR

Raised Raised Raised

EEB 2001.11.19.11.04.50 2001.11.19.11.04.50 2001.11.19.11.04.50

32785 32786 32787

ETHERNET_PORT_2 ETHERNET_PORT_3 ETHERNET_PORT_4

INFO INFO INFO

Raised Raised Raised

PerfManager 2001.11.19.11.15.01 2001.11.20.00.00.01

3000 3003

G826-15MIN-B1 G826-24HOUR-B1

WARNING WARNING

Raised Raised

CLIServer 2001.11.20.14.35.20

32782

CONSOLE_USER_LOGGED_IN INFO

Raised

283

CityLink

4.0

Submenu Commands The 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:

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

4.1

EEB Submenu Configuration of Ethernet module – Enable LAN ports – Select the important LAN port – Enable 2Mbit/s ports

EEB submenu commands: Command autopartition eebstatus get2mbport getethmode gettribmode gettribport getethport getflowctrl listportmib selectpriport set2mbport

284

Function enable / disable autopartition show GT-48350 link/partition status get 2MBit E1/T1 port state (from SW Version R1C0 this command has been replaced by gettribport) get Ethernet ports speed and duplex mode get tributary E1/T1 ports mode get tributary E1/T1 port state get Ethernet port state get flow control for Ethernet port list the MIB-statistics of a port select priority Ethernet port set 2MBit E1/T1 port state (from SW Version R1C0 this command has been replaced by settribport)

B4008 Rev. M

Fast Ethernet Configuration setethmode settribmode settribport setethport

set Ethernet port speed and duplex mode set tributary E1/T1 ports mode set tributary E1/T1 port state set Ethernet port state

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!

4.2

Baseband Submenu Configuration of IDU – Enable 2Mbit/s Wayside – Enable 64kbit/s channels

Baseband submenu commands: Command get64kg703 get64kv11 getlaser getwayside resetbaseband set64kg703 set64kv11 setlaser setwayside startlaser

B4008 Rev. M

Function get g703 enable/disable get v11 enable/disable get current laser state get wayside enable/disable reset eeb module set g703 enable/disable set v11 enable/disable sets the laser state set wayside enable/disable starts the laser

285

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

Modem submenu commands Command getberlevels getfirindex getserfindex resetmodem setberlevels setfirindex setserfindex tempcomp validberlevels

Function get HBER, LBER and ER levels get current fir tap index get current serf set index reset modem set HBER, LBER and EW levels set current fir tap index set current serf set index get temperature compensation data show valid HBER, LBER and ER levels

Settings of FIR and SERF index are set from factory! Do not change them! Contact Nera to get FIR and SERF index if necessary. Remember to use NEW-NMS or NEW-Configurator when changing frequency plan used on the system, because then these setting will be correct.

286

B4008 Rev. M

Fast Ethernet Configuration 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 master

downloadodusw transfer ODU SW No parameters from IDU to ODU drotuning get/set ODU DRO drotuning [disable | tx | rx] master tuning mode/status getatpc get AutomaticNo 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 Automaticsetatpc master PowerControl state: state functions rxref: rxref almoutlevel: almoutlevel almdelay: almdelay setfrequency set tx and setfrequency master rx frequency setmutestate set radio mute state setmutestate < on | off> master setrfpower set rf output power setrfpower master setrfwarning set RfInputLevel- inputwarning master Warning up and down

B4008 Rev. M

287

CityLink 4.4.1

Radio Status, Example CityLink (radio)> radiostatus Radio Configuration Tx Frequency Rx Frequency Last FrqShift Tx Frequency Min Tx Frequency Max Rx Frequency Min Rx Frequency Max Duplex Distance Rf Output Power Rf Output Power Max Rf Output Power Min Rf Input Warning Low Rf Input Warning Up ATPC state ATPC Rx Ref Level ATPC alm Out Level ATPC alarm Delay

4.4.2

= 23198000 kHz = 22190000 kHz = Ok = 23086000 kHz = 23534000 kHz = 22078000 kHz = 22526000 kHz = 1008000 kHz = 15 dBm = 18 dBm = 8 dBm = -60 dBm = -35 dBm =0 = -10 dBm = 15 dBm = 12 sec.

ODU:RF input ODU:RF output ODU:+48V Radio Muted Loop status Loop capability Transceiver S/N Radio Type Transceiver Type Boot Code Version App. Code Version App. Code Date

= -113.00 dBm = 14.00 dBm = 48.00 V =0 =0 =3 = 96 =1 = 10 = 1A0 = 4D2 =2001-12-0417:04:55

Radio Alarms. Alarm : 1502 LOS_RF_INPUT Alarm : 1504 RF_INPUT_WARNING

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

288

B4008 Rev. M

Fast Ethernet Configuration 4.5

SU Submenu (part of IDU) Important issues for maintenance and troubleshooting could be to investigate RF-input level and DC-level in ODU.

SU submenu commands: Command getanaloge getauxinput getauxoutput getfan setauxinput setauxoutput

4.6

Function list analogue sensor measurements list aux port inputs signals and configuartion list aux port outputs signals and configuration get fan status configure aux port inputs signals configure aux port outputs signals

Security Submenu It 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 adduser changename changepwd changesnmppwd deleteuser getiprange getlog getsnmppwd getuser resetlog resetsecurity setiprange setusername setuserpwd who

B4008 Rev. M

Function make a new user account change «current user» description name change «current user» password change SNMP password (community string) delete user account list secure IP ranges list security log list SNMP password (community strings) list users resetlog deletes all entries in security log reset security to factory settings set secure IP range set User description name set User password list users logged on

289

CityLink 4.7

Performance Submenu The Performance submenu shows the quality on your received signal from opposite Citylink.

Perform submenu commands: Command getfec getg826 getpulses getthreshold performstatus resetfec resetg826 resetpulses setthreshold

4.8

Function list FEC counter list G.826 performance values list error pulses list G.826 Thresholds list all performance parameters available reset FEC counter reset G.826 performance values reset error pulses set G.826 Thresholds

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 addroute authenticate deleteroute eebni getsysmode inventory listnetconfig listroute listsysconfig setantennatype setgateway setinterface setsectionaddr setstationaddr setstationname setsysconfig setsysmode 290

Function Adds routes to the routing table Authenticates access keys to enable licensed functionallity Deletes routes from the routing table Sets or gets state on EEB network interface Gets the system operation mode Prints inventory data Lists the network configuration Lists the routing table Lists current system configuration Sets the antennatype Sets the default gateway Sets the IP address and netmask of an interface Sets the section address Sets the station address Sets the station name Sets system configuration Sets the system operation mode B4008 Rev. M

Fast Ethernet Configuration snmpagent stationinfo updatesw

4.8.1

Enables or disables the SNMP agent Lists Station/Section info Updates the system software

Management Settings CityLink (config)> setinterface help Usage: setinterface < [ ] | []> 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 03 Disabled 04 Disabled 05 Disabled

255.255.248.0

EEB interface 1 EEB interface 2 EEB interface 3 EEB interface 4

Default gateway : 192.168.7.15

4.9

Test & Fault Submenu Test submenu commands: Command getloop setloop

Function get current looping state toggle looping state on/off

Fault submenu commands: Command alarmlog clearalarm maskalarm raisealarm unmaskalarm B4008 Rev. M

Function lists alarmlog entries clears an alarm masks an alarm raises an alarm unmasks an alarm 291

CityLink 4.10

Q1module Submenu Q1module submenu commands: Command listinterface listroutes setaddress

292

Function List the nnp interfaces Lists the nnp routing table Set the Q1 address of the element

B4008 Rev. M

Fast Ethernet Configuration

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

B4008 Rev. M

293

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 the command “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

294

Downloading using the Console FTP Client

B4008 Rev. M

Fast Ethernet Configuration 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

B4008 Rev. M

Downloading using the Internet Explorer

295

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

296

B4008 Rev. M

Fast Ethernet Configuration

NEW Network Management System The 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 configuration sheet can be opened from the Configuration menu. Use same community 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).

B4008 Rev. M

297

CityLink Fields:

Description:

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.

298

B4008 Rev. M

Fast Ethernet Configuration

Figure VIII-8 Adding IP Address

B4008 Rev. M

299

CityLink

7.0

Network Element Configuration Configuration of Network Elements is achieved using a set of propertysheets. 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 Edit sensitive menu (right mouse-button) or from the Configuration menu. The property-sheets are divided into two categories by means of functionality:

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: Get: Close: Help:

Applies the current settings in the Network Element (NE). Retrieves the current settings of the Network Element (NE). Closes the property-sheet without saving or setting any data. Displays help for the active property-page.

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 propertysheet is opened). 2 Alter the settings you want to change. 3 Press Set to send the changes to the NE.

300

B4008 Rev. M

Fast Ethernet Configuration 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-10

Buttons on Configuration property sheets with single active settings

Buttons: Close: Closes the property-sheet. Help: Displays help for the active property-page. 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.

Figure VIII-11

B4008 Rev. M

Configuration property sheet information field

301

CityLink

8.0 8.1

Element Node 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 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 Element ID from the Configuration menu.

Figure VIII-12

Element ID Configuration Sheet

Fields:

Description

Serial Number: NE Type: Name: Section Address: NE Address:

The serial number of the NE. (Not editable) The type of NE. (Not editable) The name of the NE. (max. 32 characters) The section address of the NE. The NE address. Used to identify NEs within a section. The Media Access Control address of the NE. (Not editable) The Internet Protocol address of the NE.

MAC Address: IP Address:

302

B4008 Rev. M

Fast Ethernet Configuration 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 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 NE Clock from the Configuration menu.

Figure VIII-13

Fields:

NE Clock Configuration Sheet

Description:

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

B4008 Rev. M

303

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 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 SW Versions from the Configuration menu.

Figure VIII-14

SW Versions Configuration Sheet

Fields:

Description:

SW Component: Bank: Revision:

Software title Software location Sofware revision. The field will display “unknown” if the system has this unit present, but is unable to retrieve the information from it. Valid: Complete or valid software.

Status:

304

B4008 Rev. M

Fast Ethernet Configuration 8.4

Production Data The production data property sheet presents details about the HW components within CityLink Fast Ethernet. The Production Data 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 Production Data from the Configuration menu.

Figure VIII-15

B4008 Rev. M

Production Data Property Sheet

Fields:

Description:

InventoryName: InventorySerialNumber: InventoryVersion:

The name of the HW component. The serial number of the HW component. The HW component version.

305

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 from the 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 NEWNMS. 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 overcome 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

306

Element SNMP Settings Property Sheet

B4008 Rev. M

Fast Ethernet Configuration Columns:

Description:

IP address

The Internet Protocol address of the NE (not editable). The community string used when setting information at the element (set request). The community string used when retrieving information at the element (get/getNext request). Element UDP Port for Get/Getnext/Set Number of Managers set up to receive traps from this element.(Not used)

Set Community:

Get Community:

Port: No. Receivers:

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

B4008 Rev. M

307

CityLink 8.6

Trap Table The trap table presents information about the managers currently registered to receive traps. The Trap Table 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 Trap Table from the Configuration menu.

Figure VIII-17

Fields:

Trap Table Configuration Sheet

Description:

IP Address: IP address of the registered SNMP manager trap Port: Which port is used for sending Traps to managers Last access: Time the agent was last accessed by the SNMP manager

308

B4008 Rev. M

Fast Ethernet Configuration 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.

Figure VIII-18

System Info Property Sheet

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 also be invoked by selecting (highlighting) the Element node in the Explorer view and then selecting Edit MIB II Information from the Configuration menu.

B4008 Rev. M

309

CityLink Fields:

Description:

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 only contain 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., ‘telephone closet, 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.

• To change the settings:

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 propertysheet is opened). 2 Alter the settings you want to change. 3 Press Set to send the changes to the NE.

310

B4008 Rev. M

Fast Ethernet Configuration 8.8

MIB-II SNMP Group The MIB-II SNMP property page presents the performance of the underlaying 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 RFC1213 will be displayed.

Figure VIII-19

Fields:

Description:

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.mib2.snmp.snmpInPkts) NEW-NMS uses «human readable» form and will display the above example as snmpInPkts. Value contained in this OID.

Value

B4008 Rev. M

MIB-II SNMP Property Sheet

311

CityLink 8.9

Looping The Looping 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 looping from the configuration menu. The loop settings are divided into three categories: Main Traffic Loops, 2Mbit/s Wayside traffic looping, and 64kbit/s looping. Loops can be toggled on/off by pressing the loop-buttons placed on top of a schematic bitmap. Only one loop can be active at any given time. The Loop Expire time has to be set to a time later than the current time. This time must not be more than 30 days from the current time. The loop will stay active until the Loop Expire Time is exceeded even if the looping page is closed. When a loop button is pressed, but no response from the NE is received, the loop button is colored blue. When a loop is confirmed on, it is colored red.

312

B4008 Rev. M

Fast Ethernet Configuration 8.9.1

Main Traffic Loops

8.9.1.1

Radio Terminal

Figure VIII-20

Looping Configuration Sheet, Radio Terminal

The different main traffic loops: All main traffic near end loops are swapped (port 1 → port 2, port 3 → port 4). Baseband Loop (far end) - Outgoing line traffic to incoming line traffic. Baseband Loop (near end) - Incoming line traffic to outgoing line traffic. IF Loop IDU IF Loop Transceiver RF Loop Transceiver Ethernet Loop near end with swap E1/T1 loops near end E1/T1 loops far end Note! FAR end loop will break management traffic to other side.

B4008 Rev. M

313

CityLink 8.9.1.2

Line Terminal

Figure VIII-21

Looping Configuration Sheet, 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 end Line RX SORP LT out to LR in loop near end Note! FAR end loop will break management traffic to other side.

314

B4008 Rev. M

Fast Ethernet Configuration 8.9.2

Wayside Loops

Figure VIII-22

Looping Configuration Sheet, Wayside Channel Tab

The different 2 Mbit/s Wayside Loops: Wayside Loop (far end) Wayside Loop (near end)

B4008 Rev. M

315

CityLink 8.9.3

64 kbit/s Loops

Figure VIII-23

Looping Configuration Sheet, 64kbit/s Tab

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)

316

B4008 Rev. M

Fast Ethernet Configuration

9.0 9.1

In Door Unit (IDU) 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 selecting Edit 64 kbit/s Channels from the Configuration menu.

Figure VIII-24 Fields:

Choices:

Description:

Status:

Enabled Disabled

Enables the 64 kbit/s Channel Disables the 64 kbit/s Channel Choose the direction the 64 kbit/s Rx channel should be extracted from. 64 kbit/s Rx is inserted from line SOH frames 64 kbit/s Rx is inserted from radio SOH frames

Direction: Line Radio

9.2

64kbit/s Channels Configuration Sheet

Ethernet Extension Board The main purpose of the Ethernet Extension Board (EEB) is to convert Ethernet to/from STM-1 frames. The EEB also multiplexes 4 E1/T1 channels into the STM-1 frames. The EEB 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 Ethernet Extension Board from the Configuration menu

B4008 Rev. M

317

CityLink 9.2.1

Ethernet Ports

Figure VIII-25

Ethernet Ports Configuration Sheet

Fields:

Description:

portEthStatus portEthFlowCtrl portEthLinkStatus portEthPartitionStatus

This entry enables/disables the port. This entry controls flow control setting. This entry shows the current link status. 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 as described above if IP management is enabled on port. 318

B4008 Rev. M

Fast Ethernet Configuration Priority Port Auto Partition

Designates the prioritized port.(Guaranteed 100Mb operation.) 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 .

9.2.2

2 Mbit/s Ports Configuration of tributary E1/T1 ports (2Mbit/s or 1.5Mbit/s).

B4008 Rev. M

Figure VIII-26

2Mbit/s Ports Configuration Sheet

Fields:

Description:

port2MBIndex port2MBStatus

Tributary E1/T1 port index . Presents the status of the tributary E1/T1 port.

319

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.

Figure VIII-27

Fields: Status:

Wayside Channel Configuration Sheet

Options:

Enabled Disabled Direction: Line Radio

320

Description Enables the Wayside Channel Disables the Wayside Channel Wayside Rx is extracted from line SOH Rx is extracted from radio SOH.

B4008 Rev. M

Fast Ethernet Configuration 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. The sheet 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

B4008 Rev. M

Auxiliary Output Configuration Sheet

321

CityLink Controls:

Choices:

Description:

Output control radio buttons:

Manual control Set the usage of the auxiliary or output pin. (Disabled if the Alarm triggered CityLink does not support alarm triggers.)

Manual Relay status radio buttons

Closed or open

If the auxiliary output is set to 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. This will 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 selected 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 alarmconditions are raised. 322

B4008 Rev. M

Fast Ethernet Configuration 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 HBER LBER EW-BER

Default value Indicator for BER >1exp-3 Indicator for LBER >1exp-6 Indicator for EW-BER >1exp-10

Alarm severity MAJOR MINOR WARNING

Internal proportions: HBER > LBER > EW The BER Threshold configuration sheet can be opened from the Configuration context menu of the Radio node under 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 the Configuration menu.

Figure VIII-29

B4008 Rev. M

BER Threshold Configuration Sheet

323

CityLink

324

Fields:

Choices:

Description:

HBER

1.0e - 1.0e

-10

Range. A Major alarm is generated when the Viterbi error rate exceeds the High BER threshold value. AIS is inserted when the HBER 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 the Viterbi error rate exceeds the Error Warning threshold value.

-3

B4008 Rev. M

Fast Ethernet Configuration 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 enabled or 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 Configuration context menu of the Optical Line node under the IDU node in the Explorer view. The sheet can also be invoked by selecting (highlighting) 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

B4008 Rev. M

Laser Control Configuration Sheet

325

CityLink Fields:

Buttons:

Description:

ALS: Enabled/Disabled Waiting Time

Toggles ALS On/Off (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: On Off Status:

326

(ALS disabled or not implemented) Manually turn the laser on. Manually turn the laser off. Shows the status of the Laser Unit.

B4008 Rev. M

Fast Ethernet Configuration

10.0 10.1

Out Door Unit (ODU) 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 Configuration 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 Configuration menu.

Figure VIII-31

Antenna Data Configuration Sheet

Fields:

Description:

Antenna code Gain

The antenna code. Unique code for each antenna type. The antenna Gain. (dB) Gain is a measurement of the antennas ability to transform electrical signals to electromagnetic waves. The polarization direction of the antenna. Front/Back Ratio. Ratio between the Gain in forward direction and Gain in backward direction. The physical antenna diameter. [ Meter] The frequency range where the antenna can be expected to operate successfully.

Polarization FB Diameter Frequency range

B4008 Rev. M

327

CityLink 10.2

Power Settings ATPC (Automatic Transceiver Power Control) is a function for effectively 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 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 Settings from the Configuration menu.

Figure VIII-32

328

Power Settings Configuration Sheet

B4008 Rev. M

Fast Ethernet Configuration Fields:

B4008 Rev. M

Denomination: Description:

RF-INPUT- dBm WARNINGhigh

The upper threshold value for when to generate a RF Input Level Warning (Alarm nr. 1504).

RF-INPUT- dBm WARNINGlow

The lower threshold value for when to generate a RF Input Level Warning (Alarm nr. 1504).

Manual dBm output level

The output power level used when ATPC not is activated.

Mute output power

Mutes the output power. No output power is sent.

Maximum dBm output power

Maximum output power for transmitting.

Manual Transmit Output Power (MTPC)

Disable ATPC.

Automatic Transmit Output Power (ATPC)

Enable ATPC.

Reference input level

The wanted input level when ATPC is activated.

dBm

Default dBm output level

Set the Power Level to use when an ATPC alarm occurs.

ATPC alarm seconds delay

The ATPC alarm can be delayed a certain number of seconds.

329

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 corresponding 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 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 Frequency from the Configuration menu.

Figure VIII-33

330

Frequency Configuration Sheet

B4008 Rev. M

Fast Ethernet Configuration Fields:

Denomination: Description:

Frequency plan

Choose the wanted frequency plan. The frequency plan must. correspond to your transceiver. MHz The used Tx Carrier frequency. MHz The used Rx Carrier frequency. TCM or TCM+RS The coding scheme The modulation scheme used with this frequency plan. STM-1 or STM-0 MHz The distance between the channels in this frequency plan. MHz The distance between the Tx and the Rx carrier frequency. MHz The distance between the highest frequency in lower half and the lowest frequency in the upper half of the frequency plan. Digital filters in the Modem Board compensating for RF Filter and branching characteristics. MHz Tx Lower sideband frequency for this frequency plan. MHz Tx Upper sideband frequency for this frequency plan. MHz Rx Lower sideband frequency for this frequency plan. MHz Rx Upper sideband frequency for this frequency plan. The result of the last frequency change operation (unknown, ok, executing, failed). When this item is checked the modem will be reset when applying selected frequency data. Only to be used when changing frequency plan.

TX Frequency RX Frequency Coding Modulation Data rate Channel spacing Duplex Distance Innermost spacing Compensation filter TX Frequency Band,Min TX Frequency Band,Max RX Frequency Band,Min RX Frequency Band,Max Status Reset Modem

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.

B4008 Rev. M

331

CityLink

11.0 11.1

Performance G826 Performance G.826 is an ITU-T quality recommendation for SDH networks. The Network Element has several registers for collecting G.826 performance 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

332

G-826 Performance Configuration Sheet

B4008 Rev. M

Fast Ethernet Configuration Fields:

Description:

Time interval Period

The interval of the measurement (15 min., day, month). The sequence number of the performance register. Register 0 is the running measurement, register 1 is the latest completed measurement. Severely Errored Seconds. The number of one-second periods which contains > 30% errored blocks or at least one Severely Disturbed. The number of UnAvailable Seconds. A period of unavailable 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 available time. The number of Background Block Errors. An errored block not occurring as part of an SES. Errored Second. The number of one second periods with one or more errored blocks. The start time of the measurement period. Status of the counter.

SES UAS

BBE ES Start Time Status

B4008 Rev. M

333

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.

334

Figure VIII-35

Port Performance Configuration Sheet

Fields :

Description:

Readable frames Readable octets Runts Late events Autopartition Total errors

Please Please Please Please Please Please

refer refer refer refer refer refer

to to to to to to

RFC-2108 RFC-2108 RFC-2108 RFC-2108 RFC-2108 RFC-2108

MIB. MIB. MIB. MIB. MIB. MIB.

B4008 Rev. M

Fast Ethernet Configuration 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.

B4008 Rev. M

Figure VIII-36

Repeater Performance Configuration Sheet

Fields:

Description:

Tx Collisions Total Frames Total errors Total octets

Please Please Please Please

refer refer refer refer

to to to to

RFC-2108 RFC-2108 RFC-2108 RFC-2108

MIB. MIB. MIB. MIB.

335

CityLink

12.0 12.1

Fault 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 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 NE Log Manager from the Fault menu.

Figure VIII-37

NE Alarm Log Configuration Sheet

When pressing View in the NE Alarm Log Manager, a dialog box is displayed prompting for the number of records to retrieve.

336

Figure VIII-38

Number of Records Dialog Box

Controls: Log full action Max. number of events Number of events

Options: Description: Wrap or Halt Actions to take when the log is full. The number of entries theNE alarm log can hold. Current number of log entries.

B4008 Rev. M

Fast Ethernet Configuration

13.0 13.1

Security 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 Log command either from the context menu or from the Security main menu.

Figure VIII-39

B4008 Rev. M

Security Log

Fields:

Description:

Security Log Index Security log entry text Security log entry time

The index of the Security log A descriptive text of the event. The time of the event.

337

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 NERA-FAST-ETHERNET-MIB Specific management of CityLink Fast Ethernet devices. NERA-MIB General management of Nera radio equipment. SNMP-REPEATER-MIB General management/ monitoring of repeater units. RFC1213-MIB (mib2) General management of network devices.

Defined in Nera_Clip.mib

Nera.mib

RFC 2108

RFC 1213

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.

338

B4008 Rev. M

Fast Ethernet Configuration

16.0

MIB Overview The MIB is separated into 8 sub-modules as shown below.

Figure VIII-40

B4008 Rev. M

MIB Overview

339

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

340

MIB Sub-modules, Unit

B4008 Rev. M

Fast Ethernet Configuration 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

B4008 Rev. M

MIB Sub-modules, IDU

341

CityLink 16.3

ODU This module contains the ODU specific control settings and operational status. The ODU functional capabilities are obtainable through the “capabilities” sub module.

Figure VIII-43

342

MIB Sub-modules, ODU

B4008 Rev. M

Fast Ethernet Configuration 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

B4008 Rev. M

MIB Sub-modules, Test Manager

343

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

344

MIB Sub-modules, Performance Manager

B4008 Rev. M

Fast Ethernet Configuration 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 information for each one. This will reduce the linking between the management software and the agent considerable.

Figure VIII-46

B4008 Rev. M

MIB Sub-modules, Fault Manager

345

CityLink 16.7

Analogue Value This module simply supplies analogue measurements from the agent system. The module is completely independent of the measurements presented and is therefore highly extendable

Figure VIII-47

16.8

MIB Sub-modules, Analogue Value

Security Manager This module implements a simple facility to retrieve security related information from the system.

Figure VIII-48

346

MIB Sub-modules, Security Manager

B4008 Rev. M

Troubleshooting

SECTION IX Troubleshooting

B4008 Rev. M

347

CityLink

1.0

General This 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 2.1

Description of Alarm LEDs 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 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 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 more warnings 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-branch TX DIRB Green Will be on when transmitting on B-branch

348

B4008 Rev. M

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: Green LED is activated when input signal is present. Singelmode Fiber Line interfaces (1310 Nm and 1550 Nm): Green LED is activated when input signal is present. 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 a fault, 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 a specific NE is user definable.

B4008 Rev. M

349

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 classifications are described in the table below. Severity Normal

Colour (default) Green

Description

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 it from becoming a more serious serviceaffecting fault. Minor alarm Dark Yellow Indicates the existence of a non-serviceaffecting 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.

350

B4008 Rev. M

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 and leaves under the Equipment branch concern the physical equipment of the NE.

Figure IX-1 Example of Explorer View B4008 Rev. M

351

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 View Menu. Follow the instructions in the Help file to create a map. Figure IX2 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.

352

B4008 Rev. M

Troubleshooting 3.4.3

Viewing Alarms in the Current Alarms View The Current Alarm View can be opened by selecting Current 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 View and the Map View by selecting Current Alarms from the right-mousebutton-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 Severity Alarm text Node

Description The severity of the alarm A short description of the alarm 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.

B4008 Rev. M

353

CityLink

4.0

Cable Fault If a cable fault is indicated, it indicates that the microprocessor communications 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. Ω to a few MΩ Ω: If resistance is in the order of some hundreds kΩ 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 that would 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.

354

B4008 Rev. M

Appendices

SECTION X Appendices

B4008 Rev. M

355

356

-48VDC

POWER

PWR

64kb/s V.11

2MHz SYNC (Later release)

2MHz Sync.

Phone

CALL

ALM & AUX

COLLECTIVE CALL

IDU - HSB INTFC

Slot for optional Extension Board

10 BaseT Ethernet Off the shelf standard ethernet cable

NI 2

CRITICAL

WARNING

MINOR

MAJOR

LOCAL CRAFT TERMINAL (RS232) Connector : D-SUB 9-PIN MALE Cable : UWMK3123

LCT

NI 1

NETWORK INTERFACE (RS485) Connector : D-SUB 9-PIN FEMALE Cable : UWMK3078 , UWMK3079

ALARM & AUXILLARY FUNCTIONS Connector : D-SUB 25-PIN FEMALE Cable : UWMK3076

Hot Standby Interconnection Connector : 68-PIN VHDCI receptacle Cable : 87W5066-1A

155 Mb/s LINE

Slot for optional Line Interface Plug-In Board Ref. Fig. X-6

SERVICE CHANNEL EXTENSION 2 Connector : RJ-45 8-PIN Cable : 87W5097-1A

SVCE 10BaseT Ext. 2 LAN

64kb/s 2Mb/s SVCE G.703 Wayside Ext. 1

64kbit/s SERVICE CHANNEL (V.11) Connector : RJ45 8-PIN Cable : UWMK3077

POWER Connector : PO WER D-SUB 2-PIN Cable : UWMK5051

ODU INTERFACE N-TYPE FEMALE

SAFETY GROUND

PHONE Connector : RJ-45 8-PIN Kit : 4CZ5

SERVICE CHANNEL EXTENSION 1 Connector : RJ-45 8-PIN Cable : 87W5097-1A

Appendix I:

64kbit/s SERVICE CHANNEL (G.703) Connector : RJ45 8-PIN Cable : UWMK3077

2Mbit/s WAYSIDE CHANNEL Connector : RJ45 8-PIN Cable : 87W5097-2A, 10m patch cable

CityLink

IDU / HSB-IDU Interface Description

Figure X-1 CityLink IDU

B4008 Rev. M

B4008 Rev. M

-48VDC

POWER 2

POWER 1

1 2

PWR

64kb/s V.11

2MHz SYNC (Later release)

2MHz Sync.

Phone

CALL

ALM & AUX

COLLECTIVE CALL

IDU - HSB INTFC

Slot for optional Extension Board

SERVICE CHANNEL EXTENSION 2 Connector : RJ-45 8-PIN Cable : 87W5097-1A

10 BaseT Ethernet Off the shelf standard ethernet cable

RX DIR.A

TX DIR.B

TX DIR.A

RX DIR.B

WARNING

MINOR

MAJOR

CRITICAL

LOCAL CRAFT TERMINAL (RS232) Connector : D-SUB 9-PIN MALE Cable : UWMK3123

LCT

NI 2

NI 1

NETWORK INTERFACE (RS485) Connector : D-SUB 9-PIN FEMALE Cable : UWMK3078 , UWMK3079

ALARM & AUXILLARY FUNCTIONS Connector : D-SUB 25-PIN FEMALE Cable : UWMK3076

Hot Standby Interconnection Connector : 68-PIN VHDCI receptacle Cable : 87W5066-1A

155 Mb/s LINE

Slot for optional Line Interface Plug-In Board Ref. Fig. X-6

PHONE Connector : RJ-45 8-PIN Kit : 4CZ5

SERVICE CHANNEL EXTENSION 1 Connector : RJ-45 8-PIN Cable : 87W5097-1A

SVCE 10BaseT Ext. 2 LAN

64kb/s 2Mb/s SVCE G.703 Wayside Ext. 1

64kbit/s SERVICE CHANNEL (V.11) Connector : RJ45 8-PIN Cable : UWMK3077

POWER Connector : POWER D-SUB 2-PIN Cable : UWMK5051

SAFETY GROUND

64kbit/s SERVICE CHANNEL (G.703) Connector : RJ45 8-PIN Cable : UWMK3077

2Mbit/s WAYSIDE CHANNEL Connector : RJ45 8-PIN Cable : 87W5097-2A, 10m patch cable

Appendices

Figure X-2 CityLink HSB-IDU

357

358

-48VDC

POWER

PWR

64kb/s V.11

2MHz SYNC (Later release)

64kbit/s SERVICE CHANNEL (V.11) Connector : RJ45 8-PIN Cable : UWMK3077

2MHz Sync.

Phone SIGNAL

CALL

Not used for CityLink Fast Ethernet

COLLECTIVE CALL

IDU - HSB INTFC

10Base-T/100Base-TX

Not used for CityLink Fast Ethernet

SERVICE CHANNEL EXTENSION 2

10BaseT Ethernet Off the shelf standard ethernet cable

NI 2

NI 1

WARNING

MINOR

MAJOR

CRITICAL

LOCAL CRAFT TERMINAL (RS232) Connector : D-SUB 9-PIN MALE Cable : UWMK3123

Not used for CityLink Fast Ethernet

NETWORK INTERFACE (RS485)

LCT

SIGNAL

ALARM & AUXILLARY FUNCTIONS Connector : D-SUB 25-PIN FEMALE Cable : UWMK3076

ALM & AUX

T1/E1

TRIBUTARY T1/E1 INTERFACE (2Mbit/s or 1.5Mbit/s) Connector : RJ45 8-PIN Cable : 87W5097-2A, 10m patch cable

10Base-T/100Base-TX Ethernet Off the shelf shielded twisted pair ethernet cable

Hot Standby Interconnection Not used for CityLink Fast Ethernet

155 Mb/s LINE

Slot for optional Line Interface Plug-In Board Ref. Fig. X-6

Not used for CityLink Fast Ethernet

PHONE

Not used for CityLink Fast Ethernet

SERVICE CHANNEL EXTENSION 1

SVCE 10BaseT Ext. 2 LAN

64kb/s 2Mb/s SVCE G.703 Wayside Ext. 1

POWER Connector : PO WER D-SUB 2-PIN Cable : UWMK5051

ODU INTERFACE N-TYPE FEMALE

ODU

SAFETY GROUND

64kbit/s SERVICE CHANNEL (G.703) Connector : RJ45 8-PIN Cable : UWMK3077

2Mbit/s WAYSIDE CHANNEL Connector : RJ45 8-PIN Cable : 87W5097-2A, 10m patch cable

CityLink

Figure X-3 CityLink Fast Ethernet IDU

B4008 Rev. M

Appendices

G.703 INP OUT

155 Mbit/s STM-1 Ω G.703, 75Ω Connector : DIN47297, 1.0/2.3mm Cable : UWMH3080

CAT-5 UTP

INP

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

MM Fiber

INP

1310 nm MMF Optical Interface Connector: MT-RJ Cable: 87W5078-SCxx/MTRJxx/STxx/FCxx

SM Fiber OUT INP

INP

1310 nm SMF and 1550 nm SMF Optical Interface Connector: LC Cable: 87W5080-SCxx/LCxx/FCxx

Figure X-4 B4008 Rev. M

Optional Line Interface Plug-in Boards 359

CityLink Optional Extension Boards 21x2Mbit/s Extension Board: TRIBUTARY

STM1 Extension Board: G.703 INP OUT

Line Extension STM1 / STS-3 (155Mb/s)

DS3/E3 Extension Board: SIGNAL 0 1 2 3

Figure X-5

360

DS1-0

DS3/E3-1

OUT

IN

DS3/E3-2

OUT

IN

DS3/E3-3

OUT

IN

Optional Extension Boards Boards

B4008 Rev. M

Appendices Power Connector

0V STATION GROUND (FEMALE ) IN DOOR UNIT'S FRONT VIEW

-48VDC (MALE ) 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'S FRONT VIEW Pin no. 8

Pin no. 1

U

L

A

B

Pin no. 8

C

D

Pin no. 1

Figure X-7 RJ-45 (P5001A-D) connector detail.

B4008 Rev. M

361

CityLink 64kbit/s G.703 Jack, RJ-45 Connector Pin. no: 1UA 2UA 3UA 4UA 5UA 6UA 7UA 8UA Table X-1

Function: TxD- (Neg. Tx. data) TxD+ (Pos. Tx. data) TxC+ (Pos. Tx. clock) TxC- (Neg. Tx. clock) RxD+ (Pos. Rx. data) RxD- (Neg. Rx. data) RxC+ (Pos. Rx. clock) RxC- (Neg. Rx. clock) 64kbit/s G.703 Jack, 8-PIN Pinout

64kbit/s V.11 Jack, RJ-45 Connector Pin. no: 1LA 2LA 3LA 4LA 5LA 6LA 7LA 8LA

Function: TxD- (Neg. Tx. data) TxD+ (Pos. Tx. data) TxC- (Neg. Tx. clock) TxC+ (Pos. Tx. clock) RxD- (Neg. Rx. data) RxD+ (Pos. Rx. data) RxC- (Neg. Rx. clock) RxC+ (Pos. Rx. clock)

Table X-2 64kbit/s V.11 Jack, 8-PIN Pinout

2Mbit/s Wayside Jack, RJ-45 Connector Pin. no: 1UB 2UB 3UB 4UB 5UB 6UB 7UB 8UB Table X-3 362

Function: IND+ (Pos. Rx. data) IND- (Neg. Rx. data) shield OUTD+ (Pos. Tx. data) OUTD- (Neg. Tx data) shield Not Connected Not Connected 2Mbit/s Wayside Jack, 8-PIN Pinout B4008 Rev. M

Appendices 2.048 MHz SYNC Jack, RJ-45 Connector Pin. no: 1LB 2LB 3LB 4LB 5LB 6LB 7LB 8LB

Function: INP+ (Pos. Rx. pulse) INP- (Neg. Rx. pulse) shield OUTP+ (Pos. Tx. pulse) OUTP- (Neg. Tx pulse) shield Not Connected 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: 1UC 2UC 3UC 4UC 5UC 6UC 7UC 8UC

Function: OE1_INP_A OE1_INP_B OE1_OUT_A OE1_OUT_B CALL_INP CALL_OUT CTRL_INP CTRL_OUT

Table X-5 Service Channel Extension 1 Jack, 8-PIN Pinout Pin. no: 1LC 2LC 3LC 4LC 5LC 6LC 7LC 8LC

Function: OE2_INP_A OE2_INP_B OE2_OUT_A OE2_OUT_B CALL_INP CALL_OUT CTRL_INP CTRL_OUT

Table X-6 Service Channel Extension 2 Jack, 8-PIN Pinout

B4008 Rev. M

363

CityLink Service Phone Jack, RJ-45 Connector Pin. no: 1UD 2UD 3UD 4UD 5UD 6UD 7UD 8UD Table X-7

Function: Not Connected Not Connected TELA MIC+ MICTELB Not Connected LOOP_OE Service Phone Handset Connector, 8-PIN Pinout

10Base-T (“TP-LAN”) Jack, RJ-45 Connector (normal) Pin. no: 1LD 2LD 3LD 4LD 5LD 6LD 7LD 8LD

Function: TPTX+ (Pos. Tx. data) TPTX- (NEG. Tx. data) TPRX+ (Pos. Rx. data) Not Connected Not Connected TPRX- (Neg. Rx. data) Not Connected 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: 1LD 2LD 3LD 4LD 5LD 6LD 7LD 8LD

Function: TPRX+ (Pos. Rx. data) TPRX- (NEG. Rx. data) TPTX+ (Pos. Tx. data) Not Connected Not Connected TPTX- (Neg. Tx. data) Not Connected Not Connected

Table X-9 10Base-T / 100Base-TX, 8-PIN Pinout 364

B4008 Rev. M

Appendices 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. PIN Pos.34 34

PIN Pos. 11

IN DOOR UNIT'S FRONT VIEW Pos.35 35 PIN

Figure X-8

IDU to HSB-IDU Interface Connector

NI1 and NI2, Network Interface Connector Detail PIN 5

PIN 1 IN DOOR UNIT'S FRONT VIEW

PIN 9

PIN 6

Figure X-9 “NI1” and “NI2” D-SUB 9 PIN Pinout NI1 and NI2 D-SUB 9-PIN FEMALE 1 2 3

Signal Name

Signal Description

RxDRxD+ GND

4 5 6 7 8 9

TxD+ TxDRxCRxC+ TxC+ TxC-

Data Input Data Input Signal Ground. Normally this pin shall not be connected. Data Output Data Output Clock Input Clock Input Clock Output Clock Output

Table X-10 “NI1” and “NI2” D-SUB 9-PIN Pinout

B4008 Rev. M

365

CityLink ALM & AUX Connector Detail PIN 13

PIN 1 IDU FRONT VIEW

PIN 25

PIN 14 Figure X-10 “ALM & AUX” D-SUB 25-PIN Pinout ALM & AUX D-SUB 25-PIN FEMALE 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Table X-11

Signal Name

Signal Description

USER1A USER1B USER2A USER2B USER3A USER3B USER4A USER4B ALM1 AGND ALM2 ALM3 AGND AGND ALM4 AGND ALM5 AGND ALM6 ALM7 ALM8 ERRP_V11+ ERRP_V11ERRP_OPEN_COL

Relay output 1A Relay output 1B Relay output 2A Relay output 2B Relay output 3A Relay output 3B Relay output 4A Relay output 4B Alarm input 1 (TTL level) Analog GND* Alarm input 2 (TTL level) Alarm input 3 (TTL level) Analog GND* Analog GND* Alarm input 4 (TTL level) Analog GND* Alarm input 5 (relay input) Analog GND* Alarm input 6 (relay input) Alarm input 7 (relay input) Alarm input 8 (relay input) Error pulses (V.11 output)** Error pulses (V.11 output)** Error pulses open collector output Error pulses opto coupler driver output

ERRP_OPTO

“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. 366

B4008 Rev. M

Appendices LCT Connector Detail

PIN 1

PIN 5 IDU FRONT VIEW

PIN 6

PIN 9

Figure X-11 “LCT” D-SUB 9 PIN male, Pinout LCT D-SUB 9-PIN MALE 1 2 3 4 5 6 7 8 9 Table X-12

B4008 Rev. M

Signal Name

Signal Description

NC RxD TxD GND NC

Not Connected City Link Data Input City Link Data Output Internally connected to pin 6 Signal ground Internally connected to pin 4 Internally connected to pin 8 Internally connected to pin 7 Not connected

“LCT” D-SUB 9-PIN Pinout

367

CityLink 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 connectors and cables , see Table X-13.

J1001

J1002

J1003

J1004

Figure X-12 The 21x2 Mb/s interface connectors from left to right, IDU front view. 1D

6D

IDU FRONT VIEW

1A

6A

Figure X-13 21x2Mbit/s Connector Detail

368

B4008 Rev. M

Appendices Pin no in connec -tor

Colour code of pairs in cable

Connector J1001

Connector J1002

Connector J1003

Connector J1004

2 Mb/s Ch. No

Signal

2 Mb/s Ch. No

Signal

2 Mb/s Ch. No

Signal

2 Mb/s Ch. No

Signal

1A 1B 1C 1D

White / Blue White / Orange

Ch.1 Ch.1 Ch.1 Ch.1

Input, A Input, B Output, A Output, B

Ch.7 Ch.7 Ch.7 Ch.7

Input, A Input, B Output, A Output, B

Ch.13 Ch.13 Ch.13 Ch.13

Input, A Input, B Output, A Output, B

Ch.19 Ch.19 Ch.19 Ch.19

Input, A Input, B Output, A Output, B

2A 2B 2C 2D

White / Green White / Brown

Ch.2 Ch.2 Ch.2 Ch.2

Input, A Input, B Output, A Output, B

Ch.8 Ch.8 Ch.8 Ch.8

Input, A Input, B Output, A Output, B

Ch.14 Ch.14 Ch.14 Ch.14

Input, A Input, B Output, A Output, B

Ch.20 Ch.20 Ch.20 Ch.20

Input, A Input, B Output, A Output, B

3A 3B 3C 3D

Red / Blue Red / Orange

Ch.3 Ch.3 Ch.3 Ch.3

Input, A Input, B Output, A Output, B

Ch.9 Ch.9 Ch.9 Ch.9

Input, A Input, B Output, A Output, B

Ch.15 Ch.15 Ch.15 Ch.15

Input, A Input, B Output, A Output, B

Ch.21 Ch.21 Ch.21 Ch.21

Input, A Input, B Output, A Output, B

4A 4B 4C 4D

Red / Green Red / Brown

Ch.4 Ch.4 Ch.4 Ch.4

Input, A Input, B Output, A Output, B

Ch.10 Ch.10 Ch.10 Ch.10

Input, A Input, B Output, A Output, B

Ch.16 Ch.16 Ch.16 Ch.16

Input, A Input, B Output, A Output, B

5A 5B 5C 5D

Black / Blue Black / Orange

Ch.5 Ch.5 Ch.5 Ch.5

Input, A Input, B Output, A Output, B

Ch.11 Ch.11 Ch.11 Ch.11

Input, A Input, B Output, A Output, B

Ch.17 Ch.17 Ch.17 Ch.17

Input, A Input, B Output, A Output, B

6A 6B 6C 6D

Black/ Green Black / Brown

Ch.6 Ch.6 Ch.6 Ch.6

Input, A Input, B Output, A Output, B

Ch.12 Ch.12 Ch.12 Ch.12

Input, A Input, B Output, A Output, B

Ch.18 Ch.18 Ch.18 Ch.18

Input, A Input, B Output, A Output, B

N.c.

N.c. N.c. N.c. N.c.

N.c. N.c. N.c. N.c.

N.c. N.c. N.c.

Table X-13 Configuration of 21x 2Mbit/s input- and output- signals in connectors and cables • Input, A / Output, A, refers to the positive pulse of the signal. • Input, B / Output, B, refers to the negative pulse of the signal.

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.

B4008 Rev. M

369

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 ❒ ❒ ❒ ❒ ❒ ❒

370

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

Appendices

Appendix III:Alarm List & Alarm Description Alarm Name BASEBAND LOS LOF MS-AIS MS-AIS-INS MS-RDI 2M-WAYSIDE-INP 2M-WAYSIDE-AIS-INP TRELLIS-PLL RT-PLL 2M-SYNC RS-TRACE-MISMATCH LOC BASEBAND DIRECTION RADIO TO LINE LT-PLL 2M-WAYSIDE-OUTP-AIS HBER LBER EW-BER RF-ID MODULATOR IF-MOD DEMODULATOR IF-DEM OPTICAL INTERFACE TX-OUT LASER-OFF BIAS TRANSCEIVER IF-INP RF-OUT LOS-RF-INPUT RF-INPUT-WARNING LO UNIT-ALM ATPC

RF-MUTE LOOPING-IF-EN LOOPING-RF-EN

MISSING_LO_SYNCHRONIZATION LO-TUNING-WARNING HIGH_TEMP_POWER_TRANSISTOR RF_RX_LOW RF_RX_HIGH NO_CALIBRATION_DATA HSB_CABLE_BREAK RF_TX_LOW RF_TX_HIGH IF_TX_LOW IF_TX_HIGH POWER_15 POWER_NEG15 POWER_6 POWER_48

B4008 Rev. M

Description

Id

Severity

1000

MAJOR

1001 1002

MAJOR WARNING

1003 1004

MAJOR WARNING

1005 1006 1007

MINOR WARNING CRITICAL

1008 1009

CRITICAL MINOR

1010 1011

MAJOR CRITICAL

The Line Transmit 155MHz PLL is out of lock. AIS is detected on the Wayside traffic output. Indicator for BER > 1e-3 Indicator for BER > 1e-6 Indicator for BER > 1e-10 Wrong RF-ID received compared to configuration.

1100 1101 1102 1103 1104 1105

CRITICAL WARNING MAJOR MINOR WARNING MAJOR

Loss of IF 350MHz

1200

CRITICAL

Loss Of Signal: - Optical or electrical CMI Loss of Frame Alarm indication signal detected. MS termination only Alarm indication signal is inserted. Remote defect indicator detected. MS termination only 2Mbit wayside input is missing. 2Mbit wayside input AIS detected. Indicates that the Trellis coder is out of lock.(CNF35C Asic) The Sorp 38,88 MHz PLL is out of lock. Selected synchronisation for Line Transmit direction is missing. Mismatch between configured string and received string Loss of clock (SORP)

Loss of INCOMING 140MHz.

1300

CRITICAL

The output power has increased 2dB, or the analoge measurement of PO_MON is outside predefined limits The laser is off. It could be manual shutdown The laser bias is out of limits. Sign of age and degradation

1400

CRITICAL

1401 1402

WARNING WARNING

No IF into transceiver The output power is low No signal into receiver. The RF level is either above the upward fading threshold or The RF level is below the down fading threshold. Local Oscillator is out of lock. The transceiver is not responding The regulation loop for the ATPC is not working. Software generated alarm based on alarm condition on local LOF on Rx and remote LOF on Rx . The RF transmitter is muted. The transceiver looping on IF is enabled The transceiver on RF is enabled. (If near-end and far end depends on the node where alarm is reported) XPIC LO synch missing The LO needs to be tuned

1500 1501 1502 1504

CRITICAL MAJOR MAJOR WARNING

1505 1506 1507

MAJOR MAJOR MINOR

1508 1509 1510

WARNING WARNING WARNING

1511 1512 1513 1514 1515 1516 1517

CRITICAL WARNING WARNING MAJOR MAJOR MAJOR MAJOR

1518 1519 1520 1521 1522 1523 1524 1525

MAJOR MAJOR MAJOR MAJOR WARNING WARNING WARNING WARNING

No calibration data The cable between the ODUs is broken. This will cause the switch to perform the TX-switching.

371

CityLink Alarm Name SYNTH_HEADER SHF_LO UHF_TX_LO UHF_RX_LO DUPLEX_LO VHF_LO TX_SWITCH_MAN OTHER ALM MEN-AT-WORK DROP-IN+48V BELOW+3.3V BELOW+5V BELOW-5V OVER-CURRENT WAYSIDE-LOOP FE WAYSIDE-LOOP NE PRBS-INSERTED LOOPING_EN EVENT-LOG-EXC-LIMIT DOWNLOAD-IN-PROGRESS NEED_FREQUENCY SECURITY-LOG-EXC-LIMIT 64K-LOOPING-1 64K-LOOPING-2 RTC-LOW BATTERY

BELOW+48V BELOW+11V BELOW+15V BELOW-15V MISSING-CALIBRATION-DATA FAN-ALARM DEFAULT_SYSTEM_PARAMETERS DEFAULT_ANALOGE_PARAMETERS FAN2-ALARM HSB-RELAY IDUA-ACTIVE IDUB-ACTIVE HSB-MANUAL CHANNEL-ACTIVE NEED-SW BOOT-MONITOR-IN-USE BOOT-HW-ERROR-DETECTED IDU_A_NEEDS_SW IDU_B_NEEDS_SW HDLC_LOC_A HDLC_LOC_B HDLC_LOC DROP-IN-48V-A DROP-IN-48V-B AUXILIARY ALARMS EXTERN-ALARM-1

EXTERN-ALARM-2 EXTERN-ALARM-3 EXTERN-ALARM-4

372

Description

Software generated. Operator set men at work before doing repairs. The battery supply voltage is dropped below acceptable limit Voltage from the DC-DC converter below limit Voltage from the DC-DC converter below limit Voltage from the DC-DC converter below limit Detects short current on ODU cable. Wayside looping Far End Wayside looping Near End PRBS inserted in wayside Looping enabled Event log has exceeded the capacity threshold Download of software is under progress. A RF unit need to be configured with Tx and Rx frequency. Security log has exceeded the capacity threshold 64 kb channel looping Channel1 64 kb channel looping Channel2 The battery that powers the Real Time clock is low

Voltage from the DC-DC converter below limit Voltage from the DC-DC converter below limit Voltage from the DC-DC converter below limit Voltage from the DC-DC converter below limit Modem or transceiver are missing their calibration data in flash No system configuration stored in NV config, using default (stm1,128TCM,28kHz) No analoge configuration stored in flash, using predefined defaults. IDUswitch/Transceiver relay mismatch Idu A is active in receiving direction Idu B is active in receiving direction The iduswitch is operated manually This ODU is active Board needs SW The transceiver is in boot monitor mode Errors detected by boot code when startup. Reported to app. code Reported from the IDU A Reported from IDU B The IDU switch has no RX-clock on port A The IDU switch has no RX-clock on port B The IDU(either A or B) has no RX-clock The IDU switch power source 1 has a drop The IDU switch power source 2 has a drop

Multipurpose port. Configured as Alarm Output, Alarm Input or Remote Control. External alarm reported if port configured as alarm input. Alarm name configurable from management system. ref External alarm 1 ref External alarm 1 ref External alarm 1

Id 1526 1527 1528 1529 1530 1531 1532

Severity MAJOR MAJOR MAJOR MAJOR MAJOR MAJOR WARNING

2000

WARNING

2001

WARNING

2002 2003 2005 2006 2007 2008 2009 2010 2011 2012 2013

WARNING WARNING WARNING MAJOR WARNING WARNING WARNING WARNING WARNING WARNING MAJOR

2014 2015 2016 2017

2020 2022 2023 2024 2032

WARNING WARNING WARNING WARNING/ MINOR on NL2000 WARNING WARNING WARNING WARNING MAJOR

2034 2035

WARNING CRITICAL

2036

MAJOR

2037 2200 2201 2202 2203 2216 2221 2224 2225

WARNING CRITICAL INFO INFO WARNING INFO MAJOR WARNING MINOR

2226 2227 2228 2229 2230 2231 2232

WARNING WARNING MAJOR MAJOR MAJOR MAJOR MAJOR

2500

WARNING

2501 2502 2503

WARNING WARNING WARNING

B4008 Rev. M

Appendices Alarm Name EXTERN-ALARM-5 EXTERN-ALARM-6 EXTERN-ALARM-7 EXTERN-ALARM-8 OUTPUT-ALARM-1 OUTPUT-ALARM-2 OUTPUT-ALARM-3 OUTPUT-ALARM-4 SEVERITY ALARMS CRITICAL-ALARM

MAJOR-ALARM

MINOR-ALARM

WARNING-ALARM

PERFORMANCE ALARMS G826-THRESHOLD-15MIN-B1

G826-THRESHOLD-15MIN-B2

G826-THRESHOLD-15MIN-REI

G826-THRESHOLD-24Hour-B1

G826-THRESHOLD-24HOUR-B2

G826-THRESHOLD-24HOUR-REI

G826-THRESHOLD-MONTH-B1

G826-THRESHOLD-MONTH_B2

G826-THRESHOLD-MONTH-REI

TRESHOLD-15MIN-OOF

TRESHOLD-24HOUR-OOF

TRESHOLD-MONTH-OOF

HIGHER ORDER POH ALARMS HP-RDI HP-TIM

B4008 Rev. M

Description ref External alarm 1 ref External alarm 1 ref External alarm 1 ref External alarm 1 Output alarm reported if auxilary output port configured as alarm output. ref Output alarm 1 ref Output alarm 1 ref Output alarm 1 For alarm output function If any alarms with severity set to critical, this alarm is raised. This can be combined in the alarm output expression. If any alarms with severity set to major, this alarm is raised. This can be combined in the alarm output expression. If any alarms with severity set to minor, this alarm is raised. This can be combined in the alarm output expression. If any alarms with severity set to warning, this alarm is raised. This can be combined in the alarm output expression. All software generated If the current 15 minute period exceeds the set threshold for B1, this alarm is set(period 1). After a whole period has expired without exceeding the alarm threshold(period 2), the alarm will be cleared when the next period starts(period 3). If the current 15 minute period exceeds the set threshold for B2, this alarm is set. Ref. G826-THRESHOLD-15MINB1 for method of clearing. Only for MS termination. If the current 15 minute period exceeds the set threshold for REI, this alarm is set. Ref. G826-THRESHOLD15MIN-B1 for method of clearing. Only for MS termination. If the current 24 hour period exceeds the set threshold for B1, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1 for method of clearing. If the current 24 hour period exceeds the set threshold for B2, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1 for method of clearing. Only for MS termination. If the current 24 hour period exceeds the set threshold for REI, this alarm is set. Ref. G826-THRESHOLD-15MINB1 for method of clearing. Only for MS termination. If the current month period exceeds the set threshold for month, this alarm is set. Ref. G826-THRESHOLD-15MINB1 for method of clearing. If the current month period exceeds the set threshold for month, this alarm is set. Ref. G826-THRESHOLD-15MINB1 for method of clearing. Only for MS termination. If the current month period exceeds the set threshold for REI, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1 for method of clearing. Only for MS termination. If the current 15 minute period exceeds the set threshold for OOF, this alarm is set. Ref. G826-THRESHOLD15MIN-B1 for method of clearing. If the current 24 hour period exceeds the set threshold for OOF, this alarm is set. Ref. G826-THRESHOLD-15MINB1 for method of clearing. If the current month period exceeds the set threshold for month, this alarm is set. Ref. G826-THRESHOLD-15MINB1 for method of clearing. Description Higher order Path Remote Defect Indicator Higher order Path Trace Identifier Mismatch

Id 2504 2505 2506 2507 2550

Severity WARNING WARNING WARNING WARNING INFO

2551 2552 2553

INFO INFO INFO

2600

NA

2601

NA

2602

NA

2603

NA

3000

WARNING

3001

WARNING

3002

WARNING

3003

WARNING

3004

WARNING

3005

WARNING

3006

WARNING

3007

WARNING

3008

WARNING

3015

WARNING

3016

WARNING

3017

WARNING

5050 5054

WARNING MAJOR

373

CityLink Fast Ethernet Alarms Alarm Name FTP_USER_LOGGED_IN ILLEGAL_DATE_OR_TIME IDU_TEMPERATURE1_HIGH IDU_TEMPERATURE2_HIGH FAN1_MANUAL_STOP FAN2_MANUAL_STOP FAN1_NOT_RUNNING FAN2_NOT_RUNNING I2C_BUS_FAILURE BASEBAND_DEVICE_INIT_FAILURE MODEM_DEVICE_INIT_FAILURE EEB_DEVICE_INIT_FAILURE COMMAND_LINE_INIT_FAILURE CONSOLE_USER_LOGGED_IN TELNET_USER_LOGGED_IN ETHERNET_PORT_1 ETHERNET_PORT_2 ETHERNET_PORT_3 ETHERNET_PORT_4 LOS_2MBIT_PORT_1 LOS_2MBIT_PORT_2 LOS_2MBIT_PORT_3 LOS_2MBIT_PORT_4 AIS_INPUT_2MBIT_PORT_1 AIS_INPUT_2MBIT_PORT_2 AIS_INPUT_2MBIT_PORT_3 AIS_INPUT_2MBIT_PORT_4 AIS_OUTPUT_2MBIT_PORT_1 AIS_OUTPUT_2MBIT_PORT_2 AIS_OUTPUT_2MBIT_PORT_3 AIS_OUTPUT_2MBIT_PORT_4 AIS_INSERT_2MBIT_PORT_1_RX AIS_INSERT_2MBIT_PORT_2_RX AIS_INSERT_2MBIT_PORT_3_RX AIS_INSERT_2MBIT_PORT_4_RX LOC_RT LOC_RR LOC_LT LOC_LR LOS_RR LOF_RR MS-AIS_RR MS-AIS_INSERT_RR MS-RDI_RR LOS_LR LOF_LR MS-AIS_LR MS-AIS_INSERT_LR MS-RDI_LR MS-AIS_INSERT_RT MS-AIS_INSERT_LT RS-TRACE-MISMATCH_RR RS-TRACE-MISMATCH_LR LOOP_MAIN LOOP_WAYSIDE LOOP_64K SW_UPDATE_IN_PROGRESS FREQUENCY_SHIFT

374

Description FTP user logged in Illegal Date or Time SU Temperature 1 (CPU) exceeded high limitWARNING SU Temperature 2 (DC/DC) exceeded high limit SU Fan 1 is set in manual stop SU Fan 2 is set in manual stop SU Fan 1 is not running SU Fan 2 is not running SU internal problem at I2C bus There was a hardware error in the baseband module during startup of the IDU There was a hardware error in the modem module during startup of the IDU There was a hardware error in the ethernet extension board module during startup of the IDU There was a hardware error in the command line interface module during startup of the IDU A user is currently using the command-line interface shell on the IDU via the LCT port A user is currently using the command-line interface shell on the IDU via the telnet EEB Port 1 link lost. EEB Port 2 link lost. EEB Port 3 link lost. EEB Port 4 link lost. EEB LOS port 1. EEB LOS port 2. EEB LOS port 3. EEB LOS port 4. EEB AIS input port 1. EEB AIS input port 2. EEB AIS input port 3. EEB AIS input port 4. EEB AIS output port 1. EEB AIS output port 2. EEB AIS output port 3. EEB AIS output port 4. EEB AIS insert port 1 input. EEB AIS insert port 2 input. EEB AIS insert port 3 input. EEB AIS insert port 4 input. Loss of clock in the RT module of the baseband unit (SORP) Loss of clock in the RR module of the baseband unit (SORP) Loss of clock in the LT module of the baseband unit (SORP) Loss of clock in the LR module of the baseband unit (SORP) Loss of signal on radio receive (RR) Loss of frame on radio receive (RR) Alarm indication signal detected on radio receive (RR) Alarm indication signal is inserted on radio receive (RR) Remote defect indicator detected on radio receive (RR) Loss of signal on line receive (LR): - optical or electrical CMI. Loss of frame on line receive (LR) Alarm indication signal detected on line receive (LR) Alarm indication signal is inserted on line receive (LR) Remote defect indicator detected on line receive (LR) Alarm indication signal is inserted on radio transmit (RT) Alarm indication signal is inserted on line transmit (LT) Mismatch between configured string and received string (RR) Mismatch between configured string and received string (LR) Main traffic looping is active Wayside channel looping is active 64 kb/s channel looping is active A software update is in progress A frequency shift is in progress

Id 32768 32770 32771

Severity NORMAL WARNING

32772 32773 32774 32775 32776 32777 32778

WARNING WARNING WARNING MAJOR MAJOR WARNING MAJOR

32779

MAJOR

32780

MAJOR

32781

WARNING

32782

NORMAL

32783

NORMAL

32784 32785 32786 32787 32788 32789 32790 32791 32792 32793 32794 32795 32796 32797 32798 32799 32800 32801 32802 32803 32804

NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING CRITICAL

32805

CRITICAL

32806

CRITICAL

32807

CRITICAL

32808 32809 32810 32811 32812 32813

MAJOR MAJOR WARNING MAJOR WARNING MAJOR

32814 32815 32816 32817 32818

MAJOR WARNING WARNING WARNING MAJOR

32819 32820

MAJOR MAJOR

32821

MAJOR

32822 32823 32824 32825 32826

WARNING WARNING WARNING WARNING WARNING

B4008 Rev. M

Appendices Alarm Name BELOW_11V_ODU BELOW_3.3V_ODU BELOW_48V_ODU BELOW_-15V_ODU BELOW_15V_ODU BELOW_5V_ODU FAN_ODU FAN2_ODU RX-LO TX-LO RX-LO-TUNING-WARNING TX-LO-TUNING-WARNING NEED-RX-DRO-TUNING NEED-TX-DRO-TUNING IDU-RESTARTED NETWORK-INTERFACE-CHANGED TRIBUTARY ALARMS AIS-1 AIS-2

M AIS-84 SIGNAL-LABEL-MISMATCH-1

SIGNAL-LABEL-MISMATCH-2

M SIGNAL-LABEL-MISMATCH-84 LOS-1 LOS-2

M LOS-84 LP-RDI-1 LP-RDI-2

M

WARNING WARNING WARNING WARNING WARNING MAJOR MAJOR WARNING WARNING WARNING WARNING INFO INFO

Alarm Indication Signal detected in VC-12 #1. Ref: AIS-1

4200 4201

WARNING WARNING

M Ref: AIS-1 Signal Label Mismatch detected on VC-12 #1. Is set when the signal label in the LO-POH is set to unequipped. Ref: SIGNAL-LABEL-MISMATCH-1

M Ref: SIGNAL-LABEL-MISMATCH-1 Loss Of Signal in VC-12 #1. Ref: LOS-1

M M Ref: LP-RDI-1 Low order Path Remote Failure Indication in VC-12 #1. Ref: LP-RFI-1

M

B4008 Rev. M

IDU has been Restarted Changed has been made to the network interface

Id 32827 32828 32829 32830 32831 32832 32833 32834 32835 32836 32837 32838 32839 32840 32841 32842

Ref: LOS-1 Low order Path Remote Defect Indication in VC-12 #1. Ref: LP-RDI-1

LP-RDI-84 LP-RFI-1 LP-RFI-2

LP-RFI-84

Description Voltage from the DC-DC converter below limit Voltage from the DC-DC converter below limit Voltage from the DC-DC converter below limit Voltage from the DC-DC converter below limit Voltage from the DC-DC converter below limit Voltage from the DC-DC converter below limit

M Ref: LP-RFI-1

M 4283 4284

4285

M 4367 4368 4369

M 4451 4452 4453

M 4535 4536 4537

M 4619

Severity WARNING WARNING

M WARNING

WARNING

M WARNING MAJOR MAJOR

M MAJOR WARNING WARNING

M WARNING WARNING WARNING

M WARNING

375