CityLink & EtherLink ANSI Manual

CityLink &
EtherLink
ANSI
User Manual
User Manual
CityLink /EtherLink
ANSI
B4040 Rev. A
Section I : Introduction
Section II : Installation
Section III : System Startup
Section IV : Configuration
Section V : EtherLink V.1 Configuration
Section VI : Troubleshooting
Section VII : Appendices
© Nera Networks AS
CityLink - EtherLink
List of Revisions
Rev. Date What is changed
A 30-06-05 Initial Version Based B4008 - Rev.M
2 B4040 Rev. A
CityLink
WARNING! WARNING!
r DO NOT remove or insert the This equipment contains components which are
Transmitter Unit with DC power on. sensitive to "ESD" (Electro Static Discharge).
r Power to the OutDoor Unit (ODU) is carried on It is therefore essential that whenever disassem-
the coaxial cable between the InDoor Unit bling the equipment and/or handling PC
(IDU) and the ODU. Before connecting or boards, special precautions to avoid ESD have
removing the cable, ensure that the primary to be made.
power to the IDU has been switched off.
These precautions include personnel ground-
ing, grounding of work bench, grounding of
tools and instruments as well as transport and
CAUTION! storage in special antistatic bags and boxes.
Exposure to strong high frequency electromag-
netic fields may cause thermal damage to
personnel. The eye (Cornea and lens) is easily
exposed.
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 IEC825-2: 1993
level, within limited portions of space.

Use of controls or adjustments or perform-
Dangerous radiation may be found in the ance of procedures other than those specified
neighbourhood of open waveguide flanges or herein may result in hazardous radiation
horns where the power is radiated into space. exposure.
The Optical Interface must only be serviced by
To avoid dangerous radiation the following qualified personnel, who are aware of the
precautions must be taken:
hazards involved to repair Laser products.
r During work within and close to the front When handling Laser products the following
of the antenna; make sure that transmitters
precautions must be taken:
will remain turned off.
r Never look directly into an open connector
r Before opening coaxial - or waveguide or optical cable
connectors carrying RF power, turn off
transmitters.
r Before disconnecting an optical cable, the
power should be switched off. If this is not
r Consider any incidentally open RF
possible, the cable must be disconnected
connector as carrying power, until
from the OC-3 output before it is discon-
otherwise proved. Do not look into coaxial
nected from the OC-3 input.
connectors at closer than reading distance
(30 cm). Do not look into an open wave-
r When the cable is reconnected it must be
guide unless you are absolutely sure that
connected to the OC-3 input before it is
the power is turned off.
connected to the OC-3 output.
B4040 Rev. A 3
This page is intentionally left blank.
4 B4040 Rev. A
CityLink
Table of Contents
SECTION I Equipment Description ................. 15
1.0 Introduction ................................................................. 16
SECTION II Installation .................................... 19
1.0 Installation Flowchart ................................................. 20
2.0 General ........................................................................ 21

2.1 Packing ............................................................... 21
2.2 Marking ................................................................ 21
2.3 Transportation ..................................................... 21
2.4 Radio Equipment Inventory Check ...................... 22
2.5 Preparation for Installation ................................... 22
2.6 Handling & Storage ............................................. 22
3.0 Installation Equipment required ................................ 23

3.1 Tools ................................................................... 23
3.1.1 Tools for Antenna Installation .............................. 23
3.2.1 Tools for IDU- ODU Cable /Connector Mounting. 23
3.3 Equipment external to the Radio Equipment ....... 24
4.0 6-11GHz ODU Installation .......................................... 25

4.1 Mounting the ODU to the Column ....................... 25
4.2 Transceiver attachment ...................................... 26
4.3 Waveguide to Radio ............................................ 27
4.4 Space Diversity with IF-Combining ..................... 28
B4040 Rev. A 5
5.0 18-23GHz ODU Installation ........................................ 30
5.1 General ............................................................... 30
5.2 1+0 Configuration (Integrated Antenna)............... 30
5.2.1 Change of Polarization ........................................ 32
5.3 Hot Standby Configuration .................................. 34
5.3.1 Change of Polarization ........................................ 35
5.3.2 ODU Connectors ................................................ 37
5.4 Remote Mount of the ODU .................................. 38
6.0 IDU Installation ............................................................ 41

6.1 1+0 IDU Installation ............................................. 41
6.1.1 Mounting the IDU in a 19" Rack ........................... 41
6.1.2 Cable Installation ................................................. 42
6.2 Hot Standby IDU Installation ................................ 43
6.2.1 Mounting the Hot Standby IDUs in a Rack ........... 43
6.2.2 Interconnections in a Hot Standby System ......... 44
6.3 Installation of Optional Extension Boards ............ 45
6.4 Change of Fan-Cassette ..................................... 48
7.0 IDU/ODU Cable Installation........................................ 49
8.0 All Indoor Installation .................................................. 51

8.1 1+0 Configuration ................................................ 51
8.1.1 Installation in Rack .............................................. 51
8.1.2 RF Interface ........................................................ 51
8.2 Double Terminal .................................................. 52
8.2.2 RF Interface ........................................................ 52
8.3 Hot Standby ......................................................... 53
8.3.2 RF Interface ........................................................ 53
8.4 Nera Rack Installation (optional) .......................... 54
8.4.1 General ............................................................... 54
8.4.2 Procedure ........................................................... 54
8.4.3 Power & Grounding ............................................. 57
8.4.3.1 Rack Top Connections ...................................... 57
SECTION III Installation of Nera Antenna and

6 B4040 Rev. A
CityLink
SECTION III System Startup ........................... 59
1.0 General Overview ...................................................... 60

1.1 System Capacity Setting(DS3/OC3): ................. 60
1.2 Mode of Operation (1+0, 2+0, HSB): ................... 60
1.3 IDU Settings ........................................................ 60
1.4 ODU Settings (incl Tx/Rx Frequencies) .............. 60
1.5 Equipment Required ........................................... 60
1.6 Connections ........................................................ 61
2.0 Power On ..................................................................... 61

2.1 NEW-NMS/NEW-Configurator Startup and
connecting to Network Elements ........................ 61
2.1.1 Starting NEW-NMS/NEW-Configurator with
Serial Connection (RS-232/ LCT). ...................... 62
TCP/IP Connection. ............................................ 63
2.2 Initial Configuration .............................................. 63
SECTION IV Configuration ............................. 65
1.0 General ........................................................................ 66
2.0 Element Node .............................................................. 68

2.1 Element Id ........................................................... 68
2.2 Available Functions ............................................. 70
2.3 Notifications ......................................................... 71
2.4 NE Clock Page .................................................... 73
2.5 Software Download ............................................. 74
2.6 Software Versions ............................................... 75
3.0 Transmission Node ..................................................... 77

3.1 Transmission Configuration ................................ 77
3.1.3 SSM - Synchronization Status Message ............. 85
3.2 Alarm Indication Signal Insert .............................. 86
3.3 Path Trace .......................................................... 89
B4040 Rev. A 7
4.0 Equipment Node ......................................................... 91
4.1 Management Network Routing ............................ 91
4.2 Management IP Routing ...................................... 94
4.2.1 General Settings ................................................. 95
4.2.2 Active Routes ...................................................... 97
4.2.3 Static Routes ...................................................... 98
4.2.4 RIP Interfaces ..................................................... 99
4.2.5 OSPF Interfaces ................................................. 100
4.2.6 OSPF Areas ........................................................ 101
4.3 Management Communication Ports ................... 102
4.3.1 DCC (Data Communication Channel) ................ 102
4.3.2 NI (Network Interface) .......................................... 104
4.3.3 LCT ..................................................................... 106
4.3.4 Management LAN-Port ........................................ 107
4.3.5 Terminal IP Settings ............................................ 108
4.3.6 IP Tunneling ........................................................ 109
4.3.7 OSI TP4 Tunneling .............................................. 110
4.4 Looping ............................................................... 111
4.4.1 Main Looping ....................................................... 111
4.4.2 64 Kbit/s Looping ................................................ 113
4.4.5 DS3 Looping ....................................................... 115
4.5 In Door Unit (IDU) ................................................ 118
4.5.1 IDU Production Data ........................................... 118
4.5.2 64 kbit/s Channels .............................................. 119
4.5.3 TOH X-Connect .................................................. 121
4.5.4 Error Pulse Output .............................................. 122
4.5.5 Auxiliary Output Configuration ............................. 123
4.5.6 Diagnose ............................................................. 125
4.5.7 Self Test .............................................................. 126
4.5.8 BER Thresholds ................................................. 126
4.5.9 OSI Configuration ................................................ 128
4.5.10 Laser Control ...................................................... 133
4.5.11 IDU Replace Unit Wizard .................................... 135
4.6 DS3 Tributary Card ............................................. 136
4.6.1 DS3 Configuration ............................................... 136
4.6.2 DS3 Frame Structure Configuration ................... 138
4.7 EtherLink V.2 Tributary Card ............................... 140
4.7.1 Node Tree ........................................................... 140
4.7.2 Enabling of Board ................................................ 141
8 B4040 Rev. A
CityLink
4.7.3 Board Configuration - step 1 ............................... 142
4.7.4 Board Configuration - step 2 ............................... 143
4.7.5 Port Configuration ............................................... 144
4.8 6-11GHz ODU ..................................................... 146
4.8.1 RF Power ............................................................ 146
4.8.2 Frequency Settings ............................................. 148
4.8.3 DRO Tuning ........................................................ 150
4.8.4 DRO Tuning Procedure ...................................... 151
4.8.5 Production Data .................................................. 157
4.8.6 Space Diversity ................................................... 158
4.9 18-23GHz ODU ................................................... 161
4.9.1 Frequency Settings ............................................. 161
4.9.2 ODU Transceiver - Power Configuration ............ 163
4.9.3 ODU Production Data ......................................... 165
4.10 Antenna Data ...................................................... 166
4.11 ODU Replace Unit Wizard .................................. 167
5.0 Hot Standby ................................................................. 168

5.1 General ............................................................... 168
5.1.1 Functionality ........................................................ 168
5.1.2 Element ID .......................................................... 169
5.1.2 Looping Configuration ......................................... 171
5.1.3 Hot Standby Configuration .................................. 173
5.1.4 Hot Standby Switching Criteria ............................ 174
5.1.5 Reconfiguring a Hot Standby IDU for
use in 1+0 Configuration ..................................... 176
5.1.6 Reconfiguring a 1+0 IDU for
use in Hot StandBy Configuration ...................... 176
B4040 Rev. A 9
SECTION V EtherLink V.1 Configuration ........ 177
Hyperterminal & Telnet .......................... 178
1.0 Hyperterminal & Telnet Commands .......................... 178
2.0 How to get this link alive ............................................ 179

2.1 How to get this link alive, parameters .................. 179
2.2 Testing ................................................................ 179
3.0 Top Level Commands ................................................ 180

3.1 Top Level Commands, Example ......................... 181
4.0 Submenu Commands .................................................. 182

4.1 EEB Submenu .................................................... 182
4.2 Baseband Submenu ........................................... 183
4.3 Modem Submenu (part of IDU) ........................... 184
4.4 Radio Submenu (part of ODU) ............................ 185
4.4.1 Radio Status, Example ....................................... 186
4.4.2 Radio Commands, Example of Error Message .. 186
4.5 SU Submenu (part of IDU) .................................. 187
4.6 Security Submenu .............................................. 187
4.7 Performance Submenu ....................................... 188
4.8 Configuration Submenu ...................................... 188
4.8.1 Management Settings ......................................... 189
4.9 Test & Fault Submenu ........................................ 189
4.10 Q1module Submenu ........................................... 190
5.0 Software Upgrade Procedure for

the EtherLink V.1 Device ........................................... 191
5.1 How to download a file to the IDU: ....................... 192
5.1.1 Using the Console FTP Client ............................. 192
5.1.2 Using the Internet Explorer .................................. 193
5.2 How to download a file to the ODU ..................... 194
10 B4040 Rev. A
CityLink
NEW Network Management System ..... 195
6.0 Start NEW-NMS & Connect........................................ 195
7.0 Network Element Configuration ................................ 198
8.0 Element Node .............................................................. 200

8.1 Element Id ........................................................... 200
8.2 NE Clock ............................................................. 201
8.3 Software Versions ............................................... 202
8.4 Production Data .................................................. 203
8.5 SNMP Agent(s) Settings ..................................... 204
8.6 Trap Table ........................................................... 206
8.7 MIB II - System Group ......................................... 207
8.8 MIB-II SNMP Group .............................................. 209
8.9 Looping ............................................................... 210
8.9.1 Main Traffic Loops ............................................... 211
8.9.2 Wayside Loops ................................................... 212
8.9.3 64 kbit/s Loops .................................................... 213
9.0 In Door Unit (IDU) ....................................................... 214

9.1 64 kbit/s Channels .............................................. 214
9.2 Ethernet Extension Board ................................... 214
9.2.1 Ethernet Ports ..................................................... 215
9.2.2 1.5Mbit/s Ports .................................................... 216
9.3 Wayside Channel ................................................ 217
9.4 Auxiliary Output ................................................... 218
9.5 BER Thresholds ................................................. 220
9.6 Laser Control ...................................................... 222
10.0 Out Door Unit (ODU) .................................................. 224

10.1 Antenna Data ...................................................... 224
10.2 Power Settings .................................................... 225
10.3 Frequency Settings ............................................. 227
B4040 Rev. A 11
11.0 Performance ................................................................ 229
11.1 G826 Performance .............................................. 229
11.2 Port Performance ............................................... 231
11.3 Repeater Performance ....................................... 232
12.0 Fault .............................................................................. 233

12.1 NE Alarm Log ...................................................... 233
13.0 Security ........................................................................ 234

13.1 Security Log ........................................................ 234
SNMP & MIB Description ....................... 235
14.0 General ........................................................................ 235
15.0 Supported MIBs ......................................................... 235
16.0 MIB Overview ............................................................. 236

16.1 Unit ...................................................................... 237
16.2 IDU ...................................................................... 238
16.3 ODU .................................................................... 239
16.4 Test Manager ...................................................... 240
16.5 Performance Manager ........................................ 241
16.6 Fault Manager ..................................................... 242
16.7 Analogue Value ................................................... 243
16.8 Security Manager ................................................ 243
SECTION VI Troubleshooting........................ 245
1.0 General ........................................................................ 246
2.0 Description of Alarm LEDs ......................................... 246

2.1 IDU Alarm LEDs .................................................. 246
2.2 HSB-IDU Alarm LEDs and Switch Indicators ..... 246
2.3 LEDs on Line Interface Plug-in Boards ............... 247
12 B4040 Rev. A
CityLink
3.0 Troubleshooting by NEW-NMS Configurator .......... 247
3.1 Introduction .......................................................... 247
3.2 Information Acquisition ........................................ 247
3.2.1 Polling ................................................................. 247
3.2.2 Event Notification ................................................ 248
3.3 Alarm Presentation .............................................. 248
3.4 Visual Alarm Notification ...................................... 249
3.4.1 Alarms on a Tree node/leaf in the Explorer view . 249
3.4.2 Alarms on a Node symbol in the Map view .......... 250
3.4.3 Viewing Alarms in the Current Alarms View ........ 251
4.0 Cable Fault ................................................................... 252
SECTION VII Appendices .............................. 253
Appendix I: IDU / HSB-IDU Interface Description................. 254

Power Connector .......................................................... 259
RJ-45 Connectors ......................................................... 259
64kbit/s G.703 Jack, RJ-45 Connector .......................... 260
64kbit/s V.11 Jack, RJ-45 Connector ............................ 260
1.5Mbit/s Wayside Jack, RJ-45 Connector ................... 260
Service Channel Extension 1 and 2 Jacks,
RJ-45 Connector ........................................................... 261
Service Phone Jack, RJ-45 Connector ......................... 262
10Base-T (TP-LAN) Jack, RJ-45 Connector (normal) 262
10Base-T / 100Base-TX Jack, RJ-45 Connector (uplink) . 262
NI1 and NI2, Network Interface Connector Detail .......... 263
IDU to HSB Interface Connector .................................... 263
ALM & AUX Connector Detail ........................................ 264
LCT Connector Detail .................................................... 265
Appendix II: ODU Interface Description ................................ 266

ODU/IDU Interface ........................................................ 266
Branching / Antenna Interface ....................................... 266
Appendix III: Alarm List & Alarm Description ......................... 267
B4040 Rev. A 13
14 B4040 Rev. A
Equipment Description
SECTION I
Introduction
B4040 Rev. A 15
1.0 Introduction
CityLink / EtherLink ANSI is a PTP radio system with capacity up to 300Mbps
and availability in frequency bands from 6GHz to 23GHz. The equipment is
split architecure with one single coaxial cable between the InDoor Unit (IDU)
and the OutDoor Unit (ODU). The equipment can be mounted all indoor or
split mount. If split mounted, the ODU and antenna can be located up to 300
meters 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.
When equipped with Ethernet traffic interfaces, the equipment is called

EtherLink. With DS3- or OC3-interfaces it is called CityLink
Built-in Supervisory allows easy installation, system status and configura-

tion, as well as recorded availability data.
16 B4040 Rev. A
Equipment Description
Key features
• Easy installation
• Frequency bands; 6-23GHz
• 155 Mb/s Line interface plug-ins available:
Unbalanced 75Ω coaxial
Balanced, Category 5 UTP, 100 Ω
Single Mode fiber optic, OC-3
Multi Mode fiber optic, OC-3
• SW managed configuration of 32, 64 and 128 TCM modulation
• 3xDS3 and DS1 option
• 4x10/100BaseT, 1x1000BaseT (EtherLink)
• Slot for 1000BaseX SFP (EtherLink)
• Service Channel / Engineering Orderwire
• Line extensions (2) for Service Channel
• Built-in diagnostics with local and remote loopbacks
• Available Configurations:
1+0 (Unprotected)
1+1 (Hot Standby) (not EtherLink V.1)
2+0 Dual frequency, Single Polarization (DF-SP)
2+0 Single frequency, Dual Polarization (SF-DP)
Space Diversity (not EtherLink V.1)
• High system gain
• Automatic/Manual Transmitter Power Control (ATPC/MTPC)
• Standardized use of the ECC
• Embedded SNMP (Option)
• 10, 20, 30, 40, 50 & 80 MHz channel arrangements
• Interface for local and subnetwork management (LAN or RS-232)
B4040 Rev. A 17
18 B4040 Rev. A
6-11GHz ODU Installation
SECTION II
Installation
B4040 Rev. A 19
1.0 Installation Flowchart
Installation & Commissioning
Inventory all Boxes & Accessories
Review the Accessory Kit, Prepare the site i.e

Grounding, etc; select the proper Power Source
Prepare the IDU & ODU Terminate the Coaxial Cables, Prepare External Interfaces,
Mount Lightening Arrestor
Mount ODU & Antenna in Final Location

Install the ODU & Antenna Point Antenna in General Direction
Ensure that the IDU is not Powered on
Run & Terminate Coax. Cable between IDU & ODU
Mount the ODU onto the Antenna Mounting Bracket
Install IDU
Ground equipment if necessary
Install Poweer Source - Do not Power Up the IDU at this time
Connect all cables
Apply Power Connect and configure the Craft Interface Terminal
Configure Parameters
Confirm Seviceability
for the Local End
Using Loopback Tests
IDU / ODU Loopback Tests the integrgity of the IDU, the interconnecting
cable to the ODU, and the ODU.
Local End Installation Complete

End Loopback Tests
Power Down Local End Link
Turn powerr on at both radio sites
Repeat Procedure at the End Site
Align Antennas &

Commission Radio
Tune for max. Receive Level using AGC Monitor Point at ODU
Confirm Radio Operation Purify Azimuth and Elevation
Measure AGC
Check Path Availability to ensure requirements are met
INSTALLATION
COMPLETED
20 B4040 Rev. A
2.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.
2.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 specifi-
cations" issued for the respective shipment.
2.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.
2.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.
B4040 Rev. A 21
2.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 by e-mail or fax. A short

description of damages, preferably including photographs, should be sent
as soon as possible.
2.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 unpack-
ing of the unit.
2.6 Handling & Storage

It is recommended that components are stored and transported to the
installation site in their original packing cases. If items are unpacked for
storage, they should be handled with care and protected during transpor-
tation by similar protective materials.
The equipment is an electronic device which should be handled with care.

It should be stored in dry, cool conditions, out of direct sunlight. A moisture
absorbing bag is taped inside the transportation unit to minimise conden-
sation 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 moisture in the

interconnection interfaces, the transportation protection lids on the branch-
ing and the transceiver must be kept on until mounting of waveguide
components and connection of the transceiver to the branching unit.
22 B4040 Rev. A
3.0 Installation Equipment required

3.1 Tools
The tools needed to install the equipment are listed in the following sub-
chapters.
3.1.1 Tools for Antenna Installation

Please see information from the antenna vendor.
3.2.1 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)
B4040 Rev. A 23
3.3 Equipment external to the Radio Equipment
In addition to the necessary radio equipment & antenna the following items
are needed:
• Coaxial cable between IDU and ODU.

• 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.
24 B4040 Rev. A
4.0 6-11GHz ODU Installation

4.1 Mounting the ODU to the Column
The ODU can be mounted to a Ø3" (75mm) or a Ø4.5" (115mm) column, see
figure below.
Transceiver
Interface
Column Note! Keep
Ø 3"- Ø 4.5" cover on until
the Transceiv-
er is to be
Column Clamp attached
Waveguide
Flange
Main
Waveguide
Flange
Space Div.
or Main in
dbl Term.
config.
Waveguide Flanges
(Only used for 1+1
Washer M10 or 2+0 Space Div.
Dual Pol. config.)
Nut M10 (x2)
AGC Connector
IDU - ODU Cable (Not used in
Connector, 1+0 system)
N-50 ohm
Ground Connection IDU - ODU Cable
Attach grounding cable Connector, N-50 ohm
(10mm2) to this point (Not used in 1+0 system)
with the M6 Nut and
Washers
AGC Connector
B4040 Rev. A 25
4.2 Transceiver attachment
Hook the top Transceiver hinges

to the Branching Unit and slide the
Transceiver connector flange, to
mate with the corresponding
Branching Unit flange
Secure the Transceiver

to the Branching unit with
the four attached screws Remove cover.
Ensure that the rubber
gasket is attached to
the flange
Note!
Do not remove or attach the Transceiver with DC power on.
26 B4040 Rev. A
4.3 Waveguide to Radio
Tin plated
B4040 Rev. A 27
4.4 Space Diversity with IF-Combining
Main
Space Divercity
Grounding
IF Cables
28 B4040 Rev. A
A Space Diversity system is using two antennas (denoted Main and
Space) mounted apart and connected to one Space Diversity transceiver
to achieve better performance. This requires different wave guide lengths for
the two antennas, which results in different signal propagation delays at the
Main and Space receiver inputs.
To compensate for this effect the transceiver can add delay in one of the
signal paths (normally in the Space path). Optimal receiver performance
requires an accurate delay compensation.
The two antenna signals are combined to get a single received signal for the
demodulation process.
The combiner can operate in automatic mode (controlled by signal quality

criteria derived internally in the transceiver) or in manual mode (user selects
how to combine the signals).
For configuration of Space Diversity IF-Combining, see Section IV, Chapter

4.8.6.
B4040 Rev. A 29
5.0 18-23GHz ODU Installation

5.1 General
For installation of the antenna, please refer to the Antenna Installation guide.
5.2 1+0 Configuration (Integrated Antenna)

Before mounting the ODU to the antenna assembly, it is necessary to remove
the protective hub cover from the antenna feed.
NOTE:
Remove protective hub
cover and warning
labelprior to assembly.
Mount the ODU as shown in the figure below. Be sure to lock all four latches
so that the ODU is properly secured.
Latches
To unlock the latches, push this handle forward
30 B4040 Rev. A
18-23 GHz ODU Installation
Vertical Polarization
Horizontal Polarization
B4040 Rev. A 31
5.2.1 Change of Polarization
In order to change polarization from vertical (factory pre-set) to horizontal,
it will be necessary to rotate the output transition. This is done by loosening
the attachment screws until transistion can rotate freely, rotate the transis-
tion 90 deg. counterclockwise and retightening the attachment screws.
Note!
The installation, maintenance or removal of antenna systems requires
qualified, experienced personnel. These instructions have been written for
such personnel. Antenna systems should be inspected once a year by
qualified personnel to verify proper installation, manintenance and condi-
tion of equipment.
Nera disclaims any liability or responsibility for the results of improper or
unsafe installation practices.
NOTE:
Remove protective hub Interface
cover and warning location
label prior to assembly. pins
O-ring
Transition hub NOTE: O-ring is part of flange
hardware kit supplied.
32 B4040 Rev. A
Location pins on transistion with timing mark
(V) on mounting ring (Vertical Polarization)
Loosen screws (6 places) until transistion can

rotate freely, then rotate transition hub 90 deg.
counter-clockwiseuntil it "locates" in timing recess.
When located, re-tightento a torque of 5Nm (3.69 lb-ft)
Location pins on transistion to line

up with timing mark (H) on mounting
ring (Horizontal Polarization)
B4040 Rev. A 33
5.3 Hot Standby Configuration
HSB solution is available with one or two antennas. For the two antenna
solution, ODU installation is the same as for 1+0. For HSB configuration on
one antenna, a hybrid is used for connecting the two ODUs.
HSB Hybrid:
Before mounting the HSB hybrid to the antenna assembly, it is necessary to

remove the protective hub cover from the antenna feed. If an ODU adapter
plate is mounted on the antenna it should be removed before the HSB hybrid
is mounted on the antenna.
NOTE:
Remove protective hub
cover and warning
labelprior to assembly.
34 B4040 Rev. A
Mount the ODUs as shown in the figure below. Be sure to lock all four latches
so that the ODUs are properly secured.
To unlock the latches, push this

handle forward
5.3.1 Change of Polarization

The hybrid comes pre-configured for vertical polarization of the signal. To
change to horizontal polarization, loosen the antenna interface units and
swap the puck to the one for horizontal. This extra puck is mounted on the
hybrid.
The the spare puck is

mounted here when not
being used
B4040 Rev. A 35
Hybrid, vertical polarization:
Puck for vertical polarization
Positioned for vertical

polarization
Hybrid, horizontal polarization:
Puck for horizontal polarization
Positioned for horizontal

polarization
36 B4040 Rev. A
5.3.2 ODU Connectors
BNC-Connector N-Connector
For AGC measurement For IDU-ODU Cable
Grounding point
B4040 Rev. A 37
5.4 Remote Mount of the ODU (18-23 GHz)
The remote mount is designed to attach the interface module to a vertical
tower pipe of a diameter 1.9" to 4.5"(48 to 115mm). The mount does not
provide any fine azimuth or elevation adjustment.
Note!
The installation, maintenance or removal of antenna systems requires
qualified, experienced personnel. These instructions have been written for
such personnel. Antenna systems should be inspected once a year by
qualified personnel to verify proper installation, manintenance and condi-
tion of equipment.
Nera disclaims any liability or responsibility for the results of improper or

unsafe installation practices.
Warning!
Use protective wear to avoid scin contact with the pre-applied conductive
grease on threads. Keep away from mouth. Wash thoroughly after use with
liberal amounts of liquid soap and rinse with water. Do not store open near
food or food sources. Dispose of empty or partially filled containers
according to governmental regulations for petroleum products. Contents:
oil, clay and zinc dust.
38 B4040 Rev. A
Remote Mount Assembled:
Mount Assembly:
Item Description Qty

1 Remotemount assembly 1
2 Pipe clamp 2*
3 M10x150 hex hd screw, ss 4*
4 M10 flat washer, ss 4*
5 M10 lock washer, ss 4*
6 M10 nut, ss 4*
7 Protective cap 4*
*Part of hardware kit
B4040 Rev. A 39
Fastener Torque Specifications:
Fastener size Torque value in Nm(lb-ft) for each fastener
Size M5 M6 M8 M10 M12 M16
Stainless 4.5 7.7 18.7 39.2 65.1 161
steel (3.3) (5.7) (13.8) (28.9) (48) (118.7)
Galvanised 2.7 4.5 11.1 22 38 95
steel (2) (3.3) (8.1) (16.2) (28) (70.1)
Remote Mount Remote Mount

offset left: offset right:
Rear of Remote Mount Assembly:
UBR Flange hole pattern

(ODU and Frequency
dependant)
40 B4040 Rev. A
IDU Installation
6.0 IDU Installation

6.1 1+0 IDU Installation
6.1.1 Mounting the IDU in a 19" Rack
Position the IDU in the rack and secure it by using four screws. See Figure
II-1.
POWER 1 64kb/s
64kb/s
64kb/s 2Mb/s
2Mb/s SVCE
SVCE Phone
Phone
NI
NI
NI 111
G.703
G.703Wayside
Wayside
WaysideExt.
Ext.
1 11
Ext.
155 Mb/s
155 LINE
Mb/s LINE
RXDIRA CRITICAL
CRITICAL
CRITICAL
POWER
POWER2
POWER G.703
G.703
PWR RXDIRB MAJOR
MAJOR
MAJOR
PWR1
PWR INP
INP OUT
OUT MINOR
MINOR
MINOR
2 TXDIRA WARNING
WARNING
WARNING
-48VDC
-48VDC
-48VDC 64kb/s
64kb/s 2MHz
2MHz SVCE
SVCE10BaseT
10BaseT IDU -- HSB
IDU- HSBHSB INTFC
INTFC
INTFC NI222
NI
NI TXDIRB
ODU
ODU CALL
CALL
CALL ALM&&
ALM
ALM &AUX
AUX
AUX LCT
LCT
LCT
V.11 Sync. Ext.
V.11 Sync.
Sync. Ext.
2 22 LAN
Ext. LAN
LAN
FLAT WASHER
WASHER
M6x12
Figure II-1 Mounting the IDU in a Rack
B4040 Rev. A 41
6.1.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, 8ft (2.5m) long, included in the grounding
kit. Refer to Figures VII-1 and VII-2 (Section VII, 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 7.0 (this
Section) for further details.
NOTE!
Max torque = 44.5 in/lbs (5Nm) when mounting the IDU/ODU cable.
❒ Route and secure the power cable. The CityLink requires DC power
(-40.0 to -60.0V) via a 2-pin connector. Refer to Figure VII-7 (Section VII,
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 VII, Appendix 1 for
wiring details.
42 B4040 Rev. A
IDU Installation
6.2 Hot Standby IDU Installation
(2+0 IDU installation is similar to 1+0 IDU installation, see Ch. 6.1)
6.2.1 Mounting the Hot Standby IDUs in a Rack

Position the IDUs in the rack and secure them by using four screws. See
Figure II-2.
IDU A HSB-IDU
POWER 1 64kb/s
64kb/s
64kb/s 2Mb/s
2Mb/s SVCE
SVCE Phone
Phone
Phone
NI
NI
NI111
G.703
G.703
G.703Wayside
Wayside
WaysideExt.
Ext.
1 1
Ext.
155
155 Mb/s
Mb/s LINE
LINE
LINE
RXDIRA CRITICAL
CRITICAL
CRITICAL
POWER
POWER2
POWER G.703
G.703
PWR RXDIRB MAJOR
MAJOR
MAJOR
PWR1
PWR INP
INP OUT
OUT MINOR
MINOR
MINOR
2 TXDIRA WARNING
WARNING
WARNING
-48VDC
-48VDC 64kb/s 2MHz
64kb/s
64kb/s SVCE10BaseT
2MHz SVCE
SVCE 10BaseT
10BaseT IDU -- HSB
IDU- HSBHSB INTFC
INTFC
INTFC NI 222
NI
NI TXDIRB
ODU
ODU Sync. Ext.
Ext. CALL
CALL
CALL ALM
ALM&&
&AUX
AUX
AUX LCT
LCT
LCT
V.11
V.11
V.11 Sync.
Sync. Ext.2 22 LAN
LAN
POWER 1 64kb/s
64kb/s 2Mb/s
2Mb/s SVCE
SVCE Phone
Phone NI
NI 11
G.703
G.703Wayside
WaysideExt. 11
Ext.
155
155 Mb/s
Mb/s LINE
LINE
RXDIRA CRITICAL
CRITICAL
POWER
POWER 2 G.703
G.703
PWR RXDIRB MAJOR
MAJOR
PWR 1 INP
INP OUT
OUT MINOR
MINOR
2 TXDIRA WARNING
WARNING
-48VDC
-48VDC 64kb/s 2MHz
64kb/s 2MHz SVCE
SVCE10BaseT
10BaseT IDU
IDU- HSB
- HSBINTFC
INTFC NI
NI 22 TXDIRB
ODU CALL
CALL ALM
ALM&&AUX
AUX LCT
LCT
V.11 Sync.
V.11 Sync. Ext.
Ext.
2 2 LAN
LAN
POWER 1 64kb/s
64kb/s
64kb/s 2Mb/s
2Mb/s SVCE
SVCE
SVCE Phone
Phone
NI
NI
NI111
G.703
G.703Wayside
WaysideExt.
Ext.
1 11
Ext.
155
155
155 Mb/s
Mb/s
Mb/s LINE
LINE
LINE
RXDIRA CRITICAL
CRITICAL
CRITICAL
POWER
POWER2
POWER G.703
G.703
PWR RXDIRB MAJOR
MAJOR
MAJOR
PWR1
PWR INP
INP OUT
OUT MINOR
MINOR
MINOR
2 TXDIRA WARNING
WARNING
WARNING
-48VDC
-48VDC 64kb/s 2MHz SVCE
64kb/s 2MHz
2MHz SVCE10BaseT
10BaseT IDU
IDU
- HSB
IDU -- HSBINTFC
INTFC
INTFC NI
NI
NI 222 TXDIRB
ODU
ODU Sync. Ext.
Ext. CALL
CALL
CALL ALM&&
ALM
ALM &AUX
AUX
AUX LCT
LCT
LCT
V.11 Sync.
V.11 Sync. Ext.
2 2 LAN
LAN
IDU B
FLAT WASHER
WASHER
M6x12
Figure II-2 Mounting the Hot Standby IDUs in a 19" Rack
B4040 Rev. A 43
6.2.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 cable connectors are marked respectively IDU A,
HSB-IDU and IDU B and this indicates which IDU they shall be connected
to. See Figure II-3.
Y-Cable
IDU A
HSB IDU
IDU B
Figure II-3 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 opera-
tion.
44 B4040 Rev. A
IDU Installation
6.3 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 pre-
cautions 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.
B4040 Rev. A 45
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.
46 B4040 Rev. A
IDU Installation
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.
Step 7
Remount the lid.
B4040 Rev. A 47
6.4 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.
48 B4040 Rev. A
IDU/ODU Cable Installation
7.0 IDU/ODU Cable Installation

Both ends of the cable must be terminated with N-male connectors. Cable
length limitations are dependent upon cable type used. See Technical
Description for further details.
• 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 44.5 in/lbs (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.
• It is recommend to use a lightening arrestor at ODU.
B4040 Rev. A 49
Antenna
ODU
2a
1a
1 2b
2c
IDU A
3c HSB-IDU
4
IDU B
Tower
3b
Structure
Equipment
Earthing Bar
Buried Earthing Network
Item Description Part No. Remarks

1 Coax Cable See Table V-1, Supplied as Cable Kit,
1a Cable Tie -2a & -2b cable with ties (2 per m).
2a Connector, N-male, straight for ODU
2b Connector, N-male, angle for IDU See Table V- Supplied as Connector Kit.
2c Grounding Kit for coax cable 2a & -2b
3a Grounding Cable for ODU
3b Grounding Cable for IDU UWA7 Supplied as separate kit UWA7.
3c Grounding Jumper Cable IDU/SW
4 DC Power Supply Cable UWCxx Included in IDU connection kit and HSB
IDU interconnection kit.
Figure II-4 Coax Cable Arrangement, Mandatory Items
50 B4040 Rev. A
All Indoor Installation
8.0 All Indoor Installation

8.1 1+0 Configuration
8.1.1 Installation in Rack
WARNING
POWER
STATIO N
ULRIKEN
TRANSCEIVER EQUIPMENT
STM-1 CRITI CAL
CODE NL2000 MAJOR/MINOR
DIRECTION KATTNAKKEN WARNING

POWER ON
POWER 1 64kb/s 2Mb/s

64kb/s
64kb/s 2Mb/s SVCE
2Mb/s Phone
SVCE Phone
Phone NI111
NI
NI
G.703
G.703Wayside
WaysideExt.
Ext.
1 1
155
155 Mb/s
Mb/s LINE
LINE
RXDIRA CRITICAL
CRITICAL
CRITICAL
POWER
POWER2
POWER G.703
G.703
PWR RXDIRB MAJOR
MAJOR
MAJOR
PWR1
PWR INP
INP OUT
INP OUT
OUT MINOR
MINOR
MINOR
2 TXDIRA WARNING
WARNING
WARNING
-48VDC
-48VDC
-48VDC 2MHz
64kb/s 2MHz
64kb/s
64kb/s SVCE10BaseT
2MHz SVCE
SVCE 10BaseT
10BaseT IDU
IDU - HSB
- HSB INTFC
INTFC NI222
NI
NI TXDIRB
ODU
ODU V.11 Sync. Ext. CALL
CALL
CALL ALM&&
ALM
ALM &AUX
AUX
AUX LCT
LCT
LCT
V.11
V.11 Sync.
Sync. Ext. 2 22 LAN
Ext. LAN
LAN
Figure II-5 All Indoor 1+0 Rack Installation
8.1.2 RF Interface
Figure II-6 RF-Interface All Indoor, 1+0
B4040 Rev. A 51
8.2 Double Terminal
WARNING WARNING
POWER POWER
STA TION
ULRIKEN
EQUIPMENT STM-1 CRITI CAL
TRANSCEIVER TRANSCEIVER
CODE NL2000 MAJOR/MINOR

POWER ON
POWER 1 64kb/s
64kb/s 2Mb/s
64kb/s 2Mb/s SVCE
SVCE Phone
Phone
Phone NI 1
G.703
G.703Wayside
G.703 WaysideExt. 11
Ext.
155
155Mb/s
Mb/sLINE
LINE
RXDIRA CRITICAL
CRITICAL
CRITICAL
POWER
POWER2
POWER G.703
G.703
PWR RXDIRB MAJOR
MAJOR
MAJOR
PWR1
PWR INP
INP OUT
OUT MINOR
MINOR
MINOR
2 WARNING
WARNING
WARNING
TXDIRA
-48VDC
-48VDC 64kb/s
64kb/s 2MHz SVCE
64kb/s 2MHz SVCE10BaseT
10BaseT IDU
IDU- HSB
- HSBINTFC
INTFC NI
NI222
NI TXDIRB
ODU
ODU CALL
CALL ALM&&AUX
ALM AUX LCT
LCT
LCT
V.11 Sync.
V.11 Sync. Ext. 2 2 LAN
Ext. LAN
POWER 1 64kb/s
64kb/s 2Mb/s
64kb/s 2Mb/s SVCE
2Mb/s SVCE Phone
SVCE Phone
Phone NI
NI 11
G.703
G.703Wayside
G.703 WaysideExt.
Wayside 1 11
Ext.
Ext.
155
155Mb/s
Mb/sLINE
LINE
RXDIRA CRITICAL
CRITICAL
CRITICAL
POWER
POWER2
POWER G.703
G.703
G.703
PWR RXDIRB MAJOR
MAJOR
MAJOR
PWR1
PWR INP
INP OUT
INP OUT
OUT MINOR
MINOR
MINOR
2 TXDIRA
WARNING
WARNING
WARNING
-48VDC
64kb/s 2MHz
64kb/s SVCE10BaseT
10BaseT IDU- HSB
IDU - HSBINTFC
INTFC NI222
NI
NI TXDIRB
ODU
ODU Sync. Ext.
Ext. CALL
CALL ALM
ALM&&AUX
AUX LCT
LCT
LCT
V.11
V.11 Sync. 2 2 LAN
LAN
Figure II-7 All Indoor Double Terminal Rack Installation
8.2.2 RF Interface
Figure II-8 RF-Interface All Indoor, Double Terminal [2x (1+0)]
52 B4040 Rev. A
8.3 Hot Standby
WARNING WARNING
POWER POWER
STA TION
ULRIKEN
EQUIPMENT
STM-1 CRITI CAL
TRANSCEIVER TRANSCEIVER CODE NL2000 MAJOR/MINOR

POWER ON
POWER 1 64kb/s 2Mb/s SVCE

64kb/s 2Mb/s
2Mb/s SVCE Phone
SVCE Phone
WaysideExt.
Ext. NI11
NI
G.703Wayside
G.703 Wayside 1 11
Ext.
155
155 Mb/s
Mb/s LINE
LINE
RXDIRA CRITICAL
CRITICAL
CRITICAL
POWER2
POWER
POWER G.703
G.703
PWR RXDIRB MAJOR
MAJOR
MAJOR
PWR INP OUT
INP OUT
PWR 1 MINOR
MINOR
MINOR
2 WARNING
WARNING
WARNING
TXDIRA
-48VDC 64kb/s 2MHz
64kb/s 2MHz SVCE 10BaseT
SVCE10BaseT
10BaseT IDU
IDU
IDU --HSB
HSB
- HSB INTFC
INTFC
INTFC NI22
NI TXDIRB
ODU -48VDC 64kb/s LCT
ODU Sync. Ext.
Ext. CALL
CALL ALM&&AUX
ALM AUX LCT
LCT
V.11 Sync.
V.11 Sync. 2 22 LAN
Ext. LAN
LAN

64kb/s 2Mb/s SVCE
SVCE Phone
Phone NI11
NI
G.703Wayside
G.703 WaysideExt.
Ext.
1 1
155
155 Mb/s
Mb/s LINE
LINE
RXDIRA CRITICAL
CRITICAL
POWER G.703
G.703
POWER 2 RXDIRB MAJOR
MAJOR
PWR
PWR 1 INP OUT
INP OUT MINOR
MINOR
2 TXDIRA WARNING
WARNING
-48VDC
-48VDC 64kb/s 2MHz
64kb/s 2MHz SVCE
SVCE10BaseT
10BaseT IDU
IDU - HSB
- HSB INTFC
INTFC NI22
NI TXDIRB
ODU CALL
CALL ALM&&AUX
ALM AUX LCT
LCT
V.11 Sync.
V.11 Sync. Ext.
Ext.
2 2 LAN
LAN

64kb/s 2Mb/s SVCE Phone
SVCE Phone
Phone NI111
NI
NI
G.703Wayside
G.703 WaysideExt.
Ext.
1 1
155155 Mb/s
Mb/s LINE
LINE
RXDIRA CRITICAL
CRITICAL
CRITICAL
POWER
POWER2
POWER G.703
G.703
RXDIRB MAJOR
MAJOR
MAJOR
PWR
PWR1
PWR INP OUT
INP OUT MINOR
MINOR
MINOR
2 TXDIRA
WARNING
WARNING
WARNING
-48VDC
-48VDC 2MHz SVCE
64kb/s 2MHz
SVCE 10BaseT
10BaseT IDU
IDU
IDU -- HSB
- HSBHSB INTFC
INTFC
INTFC NI222
NI
NI TXDIRB
ODU
ODU Sync. Ext.
Ext. CALL
CALL
CALL ALM&&&AUX
ALM
ALM AUX
AUX LCT
LCT
LCT
V.11 Sync.
V.11 Sync. 2 22 LAN
Ext. LAN
LAN
Figure II-9 All Indoor Hot Standby Rack Installation

8.3.2 RF Interface
Figure II-10 RF-Interface Left: All Indoor, HSB on one antenna

Right: All Indoor, HSB on two antennas
B4040 Rev. A 53
8.4 Nera Rack Installation (optional)
8.4.1 General
The rack can be fixed to the floor by 4 bolts and anchoring plugs. Alignment
is done by the adjustable feet.
Rack top can be fixed to the wall by two support brackets, bolts and anchoring
plugs.
Use of support bars enable installation away from wall.
The following material are required:

Qty 1 Screw & Bracket Kit MSK5371
Qty 1 Support Bar ....... MJK46
Tools required: See List of Tools in Installation Planning
8.4.2 Procedure
Securing to floor
1. Place the rack upright, without the adjustable feet, and position it accord-
ing to a layout plan.
2. Put marks through the holes, remove the rack and drill holes in the floor.
3. Put expansion plugs in the holes and hammer gently into place.
4. Mount the adjustable feet (nominal height 28 mm) and place the rack into
position.
5. Insert the screws and washers and align the rack to correct vertical position
by adjusting the feet. Then tighten the screws.
Support of rack top

1. Mount the two support brackets on top of the rack.
2. The rack may be installed directly to the wall. A support bar on wall may
be used to place the rack away from any skirting board and enables
installation of other racks in a row. The position of support brackets is
adjustable.
3. If the rack is installed away from wall, extended support is needed. Use the
support bar and brackets to make a frame which can be secured to the wall.
4. Back-to-back installation may either be done by bracket to bracket
mounting or by use of support bar to enable installation of other racks in
a row and securing to wall.
54 B4040 Rev. A
Support Bar can be made to frame by cutting to required length
and connected by support brackets
449 mm
Support Bar MJK46 (L= 225)
Support Bracket MBB708
Rack Top
75.5 449 75.5
A A 26.5
F F 30
A = Positions of adjustable feet (405 x 209)

F = Positions of anchoring bolts(measures)
143.5
F F
A A
Rack Bottom
Figure II-11 Securing of Rack (Top view)
B4040 Rev. A 55
Support Bar MJK46
Part of ScrewKit MSK5371
Support Bracket MBB708

(Part of screwkit)
2227
7ft
Wall
Rack Side View
Adjustable feet
Part of ScrewKit MSK5371
Figure II-12 Securing of Rack (Side view)
56 B4040 Rev. A
8.4.3 Power & Grounding
8.4.3.1 Rack Top Connections
External Earth
min 10mm2
4mm2
+ -
+ - + -
+ -
External Power cables from
DC Distribution Fuses (10A)
Subrack A PWR1
Subrack A PWR2
Subrack B PWR1
2
Subrack B PWR2
2
AUX Subrack 6mm
Subrack A 6mm
Subrack B 6mm
Figure II-13 Rack Top Power Connections
B4040 Rev. A 57
58 B4040 Rev. A
System Startup
SECTION III
System Startup
B4040 Rev. A 59
1.0 General Overview

This section assumes that the radio terminal has been installed according to
the guidelines in Section II.
1.1 System Capacity Setting

System capacity is normally preset to ordered capacity from the factory. If
modifications are needed, please see Section IV - Configuration, chapter 4.6,
for ODU configuration options. This section includes TX/RX frequency
setting, and by selecting a 10MHz channel plan, the terminal will be
configured for DS3/50Mbps operation. Enabling one of the DS3 or ethernet
ports is also needed. See Section IV - Configuration.
1.2 Mode of Operation (1+0, 2+0, HSB)

Mode of operation is normally preset to ordered system solution from the
factory, If modfications are needed, please see Section IV - Configuration
for ODU HSB configuration options. See Section IV- Configuration , chapter
5, for IDU HSB configuration options.
1.3 IDU Settings

See Section IV - Configuration, chapters 4.8 & 4.9, to change ODU
configurations (incl. frequency changes).
1.4 ODU Settings (incl Tx/Rx Frequencies)

See Section IV - Configuration, chapter 2, 3 and 4, to change IDU configu-
rations.
1.5 Equipment Required

• Voltmeter for AGC voltage monitoring (with cable to connect to
BNC-connector)
• Cable for connection between AGC monitoring point and voltmeter.
60 B4040 Rev. A
System Startup
1.6 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 utilizing bytes in
the Transport Overhead.
• NI-1 and/or NI-2 connectors for interface to other Nera equipment.
• 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.
2.1 NEW-NMS/NEW-Configurator Startup and

connecting to Network Elements
The NEW-NMS/NEW-Configurator (Nera Element vieW-Network Manage-
ment 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
B4040 Rev. A 61
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.

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 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).
62 B4040 Rev. A
System Startup
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!
User ID: admin
The program does not know the IP-address of the network element so the
connection must be manually established. To configure a TCP/IP connec-
tion to the network element, select Communication from the 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 config-
urations 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 mouse button context menu.
Follow the Wizard instructions.
All the configuration settings are described in Section IV; Configuration.
B4040 Rev. A 63
64 B4040 Rev. A
Configuration
SECTION IV
Configuration
B4040 Rev. A 65
1.0 General
This section assumes that the System Startup described in Section III 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 property-

sheets. The property-sheets are modeless, so configuration of several
different modules can be displayed simultaneously.
To open the configuration property-sheets:

Press the Right mouse-button on the Network Element node/leaf you want
to view/change the current configurations. A dynamic menu pops up. Open
the Configuration sub-menu and select the configuration-specific menu
item.
The configuration property sheets can also be launched by selecting/

marking an NE node/leaf in the Explorer View and then selecting the
configuration-specific menu item under the Edit sub menu in the Configu-
ration menu.
The property-sheets are divided into two categories by means of function-

ality:
Configuration Property sheets with Multiple Settings:

The program retrieves the current settings from the NE when the property-
sheet is opened. No message is sent to the element and no data is modified
in NEWs data structure before the user presses one of the property-sheet
buttons:
Figure IV-1 Buttons on Configuration property sheets with

multiple settings
Buttons:
Get: Retrieves the current settings from the NE.
Set: Sends the current settings to the NE.
Close: Closes the property-sheet without saving or setting any data
Help: Displays help for the active property-page.
.
66 B4040 Rev. A
Configuration
· To change the settings:
1 Get the current settings from the NE by pressing Get.
The current NE settings are automatically retrieved when the property-
sheet is opened.
2 Alter the settings.
3 Press Set to send the changes to the NE.
Configuration Property sheets with Single Interactive Settings:

The program retrieves the current NE settings when the property-sheet is
opened. Has no Get, Set or Save buttons; All functional buttons are placed
in the property-pages. A message is sent to the Network Element immediately
when a control is changed or a button is pressed.
Property-sheet buttons:
Figure IV-2 Buttons on Configuration property sheets with

single interactive settings
Buttons:
Close: Closes the property-sheet.
All property-pages have an information field at the bottom reflecting the

current status of the data shown in the property-page and the date and time
the property sheet data was retrieved from the network element.
Figure IV-3 Configuration property sheet information field
B4040 Rev. A 67
2.0 Element Node

2.1 Element Id
The CityLink Element Id property sheet shows some main information about
the Network Element like name, type, serial number and different addresses.
The fields with white background can be altered by users with proper user
privileges. The gray fields are non editable.
The Element Id configuration sheet can be opened from the 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 IV-4 Element ID Configuration Sheet
68 B4040 Rev. A
Configuration
Fields: Description:
Serial number: The serial number of the NE. (Not editable)
NE type: The type of NE. (Not editable)
Name: The name of the NE (max. 32 characters)
Section address: The section address of the NE. (1-254)
NE address: The NE address (1-128). Used for identification of
NEs within a section.
MAC address: The Media Access Control address of the NE.
Used for OSI-Management. (Not editable)
NSAP address: The Network Service Access Point address of the NE.
Used for OSI-Management.
IP address The Internet Protocol address of the NE.
Hot standby: This field is checked if the NE is a hot standby element.
To change the settings:

1 First, get the current settings from the NE by pressing Get.
(The settings are automatically retrieved from the NE when the
property-sheet is opened.)
2 Alter the settings you want to change.
B4040 Rev. A 69
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 IV-5 Available Functions Configuration Sheet
Automatic transmitted ATPC is a function for effectively reducing
power control (ATPC) interference probabilities..
IP stack The NE has an integrated IP stack.
Synchronous equipment Synchronous equipment timing source is
timing source (SETS) available. Not available.
Simple network management An SNMP management agent is available.
protocol (SNMP)
64 Kbit/s channels Two 64 Kbit/s channels can be inserted into
the OC-3 Transport Overhead (TOH ).
2.0Mbit/s wayside channel One 2.0Mbit/s wayside channel can be insert-
ed into the OC-3 Transport Overhead (TOH ).
Alarm auxiliary function A unit containing an auxiliary alarm unit
and an auxiliary output unit is available.
70 B4040 Rev. A
Configuration
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

and then selecting Edit Notifications from the Configuration menu.
Figure IV-6 Notifications Configuration Sheet
B4040 Rev. A 71
Fields: Choices: Description:
Event s
Alarm When checked, Alarm notifications will be
sent from the NE to the program.
Security When checked, Security notifications will
be sent from the NE to the program.
Switching When checked, Switching notifications will
be sent from the NE to the program.
Alarm (When the Alarm Events is disabled,

severity these functions are inactive)
Critical When checked, Alarm notifications will be
sent from the NE to the program if Critical
alarms occur.
Major When checked, Alarm notifications will be
sent from the NE to the program if Major
alarms occur.
Minor When checked, Alarm notifications will be
sent from the NE to the program if Minor
alarms occur.
Warning When checked, Alarm notifications will be
sent from the NE to the program if Warnings
occur.
72 B4040 Rev. A
Configuration
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

and then selecting Edit NE Clock from the Configuration menu.
Figure IV-7 NE Clock Configuration Sheet
The NE's Clock: The Date and Time retrieved from the
Network Element.
Difference from The difference between the PC clock and the
Network Element Clock.
B4040 Rev. A 73
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

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.
74 B4040 Rev. A
Configuration
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 Down-
load) 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 Configura-

tion context menu of the Element node in the Explorer view. The sheet can
also be invoked by selecting (highlighting) the Element node in the Explorer
view and then selecting Edit SW Versions from the Configuration menu.
Figure IV-8 SW Version Configuration Sheet
B4040 Rev. A 75
SW Component Name of the software

Bank Software location
Revision Software revision
Status Idle:Software is not being executed.
Active:Software is being executed.
Loading: SW is downloading to this bank.
Invalid: Incomplete or invalid SW; SW bank
has not been used or a SW download has
failed.
Not contact with unit: The IDU does not
have contact with the unit containing this SW.
To activate a memory bank:

1 Select the unused bank (status: Idle) by clicking the left mouse button.
2 Press the Set Active button
The NE will be reset and when it starts, the application code of the chosen
bank will be executed.
76 B4040 Rev. A
Configuration
3.0 Transmission Node

3.1 Transmission Configuration
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.
An IDU may support different interface cards for different markets. This
includes Ethernet, OC-/STM-1, DS3/E3 and 21x2Mbps tributary cards. Each
element will, however, only support one extension board at a time. From the
Transmission Configuration sheet the user can enable SONET or SDH
standards and the functionality of the specific tributary card. The 21x2Mbit/
s tributary card assumes a frame structure which contains 63 E1s. To enable
this board, select the termination to be Lower Order Path Termination -
LOPT. If the DS3/E3 Extension Board or the STM-1 Extension Board is
mounted, the frame structure must be set explicitly.
The Transmission Configuration configuration sheet can be opened from

the Configuration context menu of the Transmission node in the Explorer
view. The sheet can also be invoked by selecting (highlighting) the Trans-
mission node in the Explorer view and then selecting Edit Transmission
Configuration from the Configuration menu.
Figure IV-9 Transmission Configuration Configuration Sheet
B4040 Rev. A 77
Transmission Standard The Transmission System used. Legal values are:
• SDH
• SONET
Termination Enabling The type of termination this element shall

support. Legal values are:
• RST
• MST
• Lower Order Path Termination - LOPT
• Enable X-Connect (available only if X-
Connect Extension Board is equipped)
• Enable DS3/E3 (available only if DS3/E3
Extension Board is equipped)
Note: If this setting is changed and applied to
the element, the equipment will perform a soft-
ware reset.
Element Type The type of «timing element» were 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 X-
Connect Extension Board is present.
78 B4040 Rev. A
Configuration
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 cant 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.
B4040 Rev. A 79
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
arent 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: 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.
80 B4040 Rev. A
Configuration
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 SONET 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 IV-10 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 IV-10 Transmission Configuration, RST
B4040 Rev. A 81
MST:
The equipment will monitor and regenerate B1-, M1 REI- and B2-parity.
Figure IV-11 shows how the dialog looks when this setting is applied.
Figure IV-11 Transmission Configuration, MST
Lower Order Path Termination - LOPT (SDH only):

This configuration is not used in North America.
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 parity. Figure IV-12 shows how the dialog looks when this setting
is applied.
Figure IV-12 Transmission Configuration, LOPT
82 B4040 Rev. A
Configuration
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 IV-13 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/
SONET structure may be configured from the Frame Structure page.
Figure IV-12 Transmission Configuration, Enable DS3/E3
B4040 Rev. A 83
Enable 21x2:
This functionality is only available with new target software. To enable the
21x2 functionality, select Enable 21x2 from the Termination enabling
combo box and press the SET button. The SDH structure may be config-
ured from the Frame Structure page.
Figure IV-15 Transmission Configuration, Enable 21x2
84 B4040 Rev. A
Configuration
3.1.3 SSM - Synchronization Status Message
The SSM sheet is used to monitor the received S1-byte in the two OC-3
directions; LINE and RADIO.
The SSM - Synchronization Status Message configuration sheet can be

opened from the Transmission Configuration sheet by clicking the SSM
Dialog button on this sheet.
Note: The SSM Dialog button will only be visible for Administrator users
in the Transmission Configuration sheet.
Figure IV-16 The SSM Configuration Sheet
Direction From which OC-3 direction the S1 byte is monitored.
This can be either Line or Radio
Last change Will show the last time the specific S1 byte changed its
value.
S1 byte The current content of the specific S1 byte.
Description An interpretation of the S1 byte. These can be:
B4040 Rev. A 85
S1 byte SONETsynchronizationqualityleveldescription
0000 Quality unknown (existing sync network)
0001 Reserved
0010 G.811
0011 Reserved
0100 G.812 transit
0101 Reserved
0110 Reserved
0111 Reserved
1000 G.812 local
1001 Reserved
1010 Reserved
1011 Synchronous equipment timing source (SETS)
1100 Reserved
1101 Reserved
1110 Reserved
1111 Do not use for synchronization
3.2 Alarm Indication Signal Insert

(For advanced users)
The Path Trace functionality and the AIS (Alarm Indicator Signal) function-
ality are used for verifying that the received OC-3 frames are the desired
receive frames (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
SOH, 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 OC-3 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.
86 B4040 Rev. A
Configuration
Figure IV-17 AIS Insert Configuration Sheet
Fields: Subfields: Description:
Insert AIS when An AIS is inserted when the Viterbi HBER

Viterbi HBER threshold is exceeded. (See Chapter 4.5.8
thresholdexceeded for setting of BER threshold.)
Insert AIS when An AIS is inserted when there is a mismatch

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

RF ID mismatch between the RF ID set in the Path Trace
sheet and RF ID bit set on this sheet.
The RF ID functionality is only available at
the Radio node.
AIS remove delay 1 - 200 seconds
Section
trace (J0) Not used The Section Trace String is not used.
Fixedbyte The Section Trace String is one byte ( =8 bit)
long.
B4040 Rev. A 87
Fields: Subfields: Description:
User message The 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 SOH. If mismatch, AIS will be
inserted if the Insert AIS when trace mismatch
box is checked. The Expected field normally con-
tains the same values as the Trace string in the Path
trace property sheet at the transmit end of the path.
Received: The ASCII string or fixed byte in received J0 in
SOH.
Status: The status of the Section Trace:
• OK: Expected and received Regenerator
Section Trace are identical.
• TIM-S alarm: (Section Trace
Identifier Mismatch) Mismath between
expected and received Section Trace.
• LOF error: Loss of frame alarm on received
OC-3 signal. Thus, J0 is not available. Alarm
status, OK or TIM-S alarm will be latched.
• CRC error: CRC error in received Regenerator
Section Trace. (Only in User Message mode)
• Invalid: Not valid User Message received.
RF ID: (The RF ID functionality is only available at the

Radio node)
Notused/Used: RF_ID MS3 bit on/off
Expected: The value to be compared with the RF ID byte in
the received TOH. If mismatched, AIS will be in-
serted 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.
88 B4040 Rev. A
Configuration
3.3 Path Trace
(For advanced users)
The Path Trace functionality and the AIS (Alarm Indicator Signal) function-
ality are used to test that the received OC-3 frames are desired receive frames
(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 SOH, 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 OC-3 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 IV-18 Path Trace Configuration Sheet
B4040 Rev. A 89
Fields: Subfields Description:

Section
trace string
Enabled When checked the specific Trace
String is sent in the J0 byte.
Fixedbyte The Section Trace
String is one byte ( =8bit) long.
User message The 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.
RFID
Not used/Used RF_ID MS3 bit on/off
Two bit combination.
90 B4040 Rev. A
Configuration
4.0 Equipment Node

4.1 Management 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 initialized 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 Configura-
tion 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 Configura-
tion menu.
B4040 Rev. A 91
Figure IV-19 Routing Table Configuration Sheet,

Active Tab (top) and Initial Tab (bottom)
92 B4040 Rev. A
Configuration
Auto/Manual If Auto, the router may update the entry in the active
routing table automatically based on shortest path/
lowest weight. If Manual, the entry is never changed by
the router and fixed route configuration is used.
Section The Section number of the addressed NE (1-128).
NE The NE address of the destination NE. If this number is
255, section routing is used. That means that this routing
entry is used for all NEs in the specified section.
Possible values: 1...62 (and broadcast address 255).
Port The communication port of which the messages are to be
routed through. Possible values:
• NI1
• NI2
• DCC Line
• DCC Radio
• OSI TP4 tunnel 1 (Server)
• OSI TP4 tunnel 2 (Server)
• OSI TP4 tunnel 1 (Client)
• OSI TP4 tunnel 2 (Client)
• TCP/IP tunnel 1 (Server)
• TCP/IP tunnel 2 (Server)
• TCP/IP tunnel 1 (Client)
• TCP/IP tunnel 2 (Client)
Weight A computed weight that gives an indication of the
communication capacity to the destination network
element. A high number denotes a longer response time.
Buttons:
Add: Displays the Add Routing Entry dialog box where a new
initial routing entry can be configured.
Edit: Displays the Edit Routing Entry dialog box where the
selected initial routing entry can be configured.
Delete: Deletes the selected routing entries.
Add to static: Copies the selected routing entries to the initial routing
table.
B4040 Rev. A 93
4.2 Management 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 Value
Inject default route into stub area YES
Router dead interval 40 sec
Hello interval 10 sec
Retransmit delay 1 sec
Retransmit interval 5 sec
Authentication 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.
94 B4040 Rev. A
Configuration
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 IV-20 IP Routing Configuration Sheet,General Settings
B4040 Rev. A 95
Property page controls:
OSPF Protocol: Select parameter settings for OSPF routing protocol.

Enable: Enables the NE to handle OSPF routing.
Redistribute RIP: Allows OSPF to redistribute routing
information from RIP v2 routing
protocol.
Redistribute Static: Allows OSPF to redistribute static
routing information.
Default Cost: Setting of default cost value used for
OSPF protocol.
The Redistribute options allow the OSPF protocol to pass

the routing information of other routing protocols.
For information to be passed between the OSPF and RIP
protocols, the current NE must have both protocols enabled.
RIP Protocol: Select parameter settings for RIP routing protocol.

Enable: Enables the NE to handle RIP routing.
Redistribute OSPF: Allows RIP to redistribute routing infor-
mation from OSPF routing protocol.
Redistribute Static: Allows RIP to redistribute static routing
information.
Default Metric: Setting of default metric value used for
RIP protocol.
The Redistribute options allow the RIP protocol to pass the

routing information of other routing protocols.
For information to be passed between the OSPF and RIP
protocols, the current NE must have both protocols enabled.
IP Configurable List of interfaces available on the current NE 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).
96 B4040 Rev. A
Configuration
4.2.2 Active Routes
Monitor active routes for current NE from this page.
Figure IV-21 IP Routing Configuration Sheet, Active Routes
B4040 Rev. A 97
4.2.3 Static Routes
Edit static routes regarding IP Routing using this page.
Figure IV-22 IP Routing Configuration Sheet, Static Routes
Add: Add a new static route to the list using the appearing dialog.
Edit: Select a row and press Edit to open the Edit Static Route dialog.
In this dialog the settings for the selected route may be changed.
Delete: Deletes the selected row(s) from the list.
Note! Changes to the Static Routes are not transferred to the NE before Set
is pressed.
98 B4040 Rev. A
Configuration
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 IV-23 IP Routing Configuration Sheet, RIP Interfaces

Add: Add a new RIP interface to the list using the appearing dialog.
Edit: Select a row and press Edit to open the Edit RIP Interface dialog.
In this dialog the settings for the selected interface may be
changed.
Note! Changes to the RIP Interfaces are not transferred to the NE before Set
is pressed.
B4040 Rev. A 99
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 IV-24 IP Routing Configuration Sheet, OSPF Interfaces

Add: Add a new OSPF interface to the list using the appearing dialog.
Edit: Select a row and press Edit to open the Edit OSPF Interface
dialog. In this dialog the settings for the selected interface may be
changed.
Note! Changes to the OSPF Interfaces are not transferred to the NE before
Set is pressed.
100 B4040 Rev. A

Configuration
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 IV-25 IP Routing Configuration Sheet, OSPF Interfaces

Add: Add a new OSPF area to the list using the appearing dialog.
Note! Use Edit dialog to add new network ranges to existing areas.
Edit: Select a row and press Edit to open the Edit OSPF Area dialog.
In this dialog the settings for the area which the row belongs to may
be changed.
If a network range row is selected, only the network range is deleted.
In all other cases, the entire area is deleted.
Note! Changes to the OSPF areas are not transferred to the NE before Set
is pressed.
B4040 Rev. A 101

4.3 Management Communication Ports
4.3.1 DCC (Data Communication Channel)
The CityLink DCC (Data Communication Channel) is used to communicate
between the Supervisory Unit of the Network Element and Supervisory Units
of other Network Elements through the TOH of the OC-3 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.
Figure IV-26 DCC Tab in Communication Ports Configuration Sheet
102 B4040 Rev. A

Configuration

Enabled Switches the DCC communication ports
on/off.
Channel: The Channel where the DCC are
inserted in the TOH.
Ch. 1-Ch XX CityLink has only one channel. This
field will always be Ch. 1 at CityLink.
Direction
Line DCC Line is inserted the line side of the
radio.
Radio DCC Radio is inserted the radio side of
the radio.
Timeslot: Shows which timeslot in the TOH the
DCC channels use. The user can change
the used timeslot by pressing TOH. The
SONET Frame Transport Overhead
Dialog box will appear.
Stack
Nera NERA Stack.
Nera stack is always enabled on the
radio side (DCC Radio).
QECC QECC Stack
TCP/IP TCP/IP Stack
LAPD Data link layer for the QECC protocol.
For more information refer to ITU-T
G.784 and ITU-T Q.921.
Network side Server for the LAPD requests.
User side Client for the LAPD requests.
PPP: (Point to Point Protocol) Data link
layer for the TCP/IP protocol.
(currently not implemented)
Active mode (currently not implemented)
Demand dial (currently not implemented)
Direct mode (currently not implemented)
Passive mode (currently not implemented)
B4040 Rev. A 103

4.3.2 NI (Network Interface)
The Network Interface ports (NI-1 and NI-2) are used to connect the
Supervisory Unit of the Network Element to Supervisory Units of other Nera
Network Elements. The NI ports can be set to a variety of different config-
urations.
Note: For EtherLink V.1, the NI 2 port can be Enabled only if the Ethernet
function is Disabled, and vice versa.

Press the NI tab to view/change the NI settings. The sheet can also be
menu.
Figure IV-27 NI Tab in Communication Ports Configuration Sheet
104 B4040 Rev. A

Configuration

Enabled Enables the NI port
Function CityLink The functionality of the NI port.
NL29xNI The baud rate and stack are
NL29xQx grayed/whitened to indicate which
PDH Synchronous settings are necessary for the
PDH Asynchronous different functionalities.
V.11 contra dir master
V.11 contra dir slave
V.11 co dir
Q1V.11
NL29x V.11 contra
dir slave
Baudrate The baud rate (symbols/second) of
the NI port. If the field is grayed, no
baud rate is necessary to set.
1200 to 200000 Baud
Stack
Nera NERA Stack.
OSI OSI Stack
LAPD Data link layer for the QECC
protocol. For more information
refer to ITU-T G.784 and ITU-T
Q.921.
Network side Server for the LAPD requests.
User side Client for the LAPD requests.
PPP: (Point to Point Protocol) Data link
layer for the TCP/IP protocol.
(currently not implemented)
Active mode (currently not implemented)
Demand dial (currently not implemented)
Direct mode (currently not implemented)
Passive mode (currently not implemented)
B4040 Rev. A 105

4.3.3 LCT
The LCT port is the serial port (RS-232) that can be used to communicate with
a PC executing NEW-NMS. In this sheet the baud rate of the LCT port can
be changed.
WARNING!
If you are communicating with the NE through the LCT (Serial) port and you
change the LCT baud rate you will loose contact with the NE until you
configure the NEW-NMS communication settings to the same baud rate as
the NE baud rate.

Press the LCT tab to view/change the LCT settings. The sheet can also be
menu.
Figure IV-28 LCT Tab in Communication Ports Configuration Sheet

Baudrate: 1200 - 115200 Baud rate. The default baud rate is 115200.
106 B4040 Rev. A

Configuration
4.3.4 Management LAN-Port
The Management LAN-port can be Enabled only if the NI 2 port is Disabled,
and vice versa. See chapter 4.3.2.

Press the Ethernet tab to view/change the LAN-port 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 IV-29 Ethernet Tab in Communication Ports Configuration Sheet

Enabled Toggles Ethernet on/off
Stack OSI TP4 OSI Stack
TCP/IP TCP/IP Stack. Must be selected if IP
Tunneling is enabled.
B4040 Rev. A 107

4.3.5 Terminal 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.
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 Configura-
tion menu.
Figure IV-30 IP Settings Tab in Communication Ports Configuration Sheet

IP address Shows the Internet Protocol (IP) address of the NE.
Subnet mask Type the Subnet Mask number obtained from your
network administrator. This number, combined with
the IP address, identifies which network your NE is on.
Defaultgateway 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.
108 B4040 Rev. A

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

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 IV-31 IP Tunneling Tab in Comm. Ports Configuration Sheet

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.
B4040 Rev. A 109

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.

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 Communi-
cation Ports from the Configuration menu.
Figure IV-32 OSI TP4 Tunneling Tab in Comm. Ports Configuration Sheet

Enabled: On/Off Toggles OSI Tunneling on/off
Remote section address: Shows the section address of the NE
addressed though OSI TP4 Tunnel
Remote NE address: Shows the SU address of the NE
addressed though OSI TP4 Tunnel
Remote NSAP address: 0 to 20 bytes
110 B4040 Rev. A

Configuration
4.4 Looping
The loop settings are divided into three categories: Main traffic looping,
64kbit/s looping and DS3 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 IV-33 Looping Configuration Sheet
B4040 Rev. A 111

Loop buttons: One button for each loop where the arrow indicates
which way the signal is looped. The color of the loop
arrows describes the status of the loop:
Blue: The status of the loop is unknown. Loop informa-
tion has not been retrieved from the NE, or a loop message
has just been sent to the NE and the GUI (Graphical User
Interface) is waiting for a response from the NE. (The
loop settings have not been confirmed by the NE). Note
that the loop cannot be toggled when the status is unknown.
Black: The loop is off (inactive)
Red: The loop is on (active)
Loops will be Displays the time of which all main traffic loops in the NE
automatically will be cleared. This time is set by the user when activating
cleared after: a loop.
The following main traffic loops are available:

1. Modem Loop IDU, far end
2. Modem Loop IDU, near end
3. IF Loop, near end
4. ODU Loop, near end
5. 64 kb/s loop, far end
6. Ethernet Traffic Loops (EtherLink - use MAC-destination address
FFFF FFFF FFFF - broadcast)
1. EtherLink 50/100 (one port enabled): The traffic is looped back to
this port.
2. EtherLink 150/300: Traffic is looped from port 1 to
port 4, port 2 to port 5
(electrical gigE-port) and 3 to
port 6 (SFP)
7. T1-Loops on Ethernet Tributary Card (EtherLink v.1 only)
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.
112 B4040 Rev. A

Configuration
4.4.2 64 Kbit/s Looping
context menu of the Equipment node in the Explorer view. Press the 64 Kbit/
s Looping tab to view/change the looping settings. The sheet can also be
invoked by selecting the Equipment node in the Explorer view and then
Figure IV-34 Looping Configuration Sheet. 64kbit/s Tab
B4040 Rev. A 113

Fields:
· Blue: The status of the loop is unknown. Loop informa-
tion has yet not been retrieved from the NE, or a loop
message has just been sent to the NE and the GUI is
waiting for a response from the NE. (The loop settings
have not yet been confirmed by the NE). Note that the
loop cannot be toggled when the status is unknown.
· Black: The loop is off (inactive)
· Red: The loop is on (active)
· Grey: The corresponding 64kbit/s channel is not enabled.
The different 64Kbit/s loops: (Figure IV-34 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:
114 B4040 Rev. A

Configuration
4.4.5 DS3 Looping
The DS3 extension board includes three PDH ports, each of which supports
looping. The board supports Far End Loop, Near End Loop, PRBS insertion
and PRBS verification. The loops are available when the PDH Ports on the
DS3 board 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 directions. An error is detected when the signal differs from the
expected PRBS signal.
The DS3 board 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 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.
The Looping Configuration Property sheet can be opened from the Config-
uration context menu of the Equipment node in the Explorer view. The sheet
can also be invoked by selecting (highlighting) the Equipment node in the
Explorer view and then selecting Edit Looping from the Configuration
menu .
B4040 Rev. A 115

Figure IV-35 Looping Configuration Sheet, DS3

Loop buttons: One button for each loop where the arrow indicates which way
the signal is looped. The color 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)
116 B4040 Rev. A

Configuration
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.
B4040 Rev. A 117

4.5 In Door Unit (IDU)
4.5.1 IDU Production Data
The IDU production data property sheet shows the production serial
numbers and the production and test dates of the IDU. Only an 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 IV-36 IDU Production Data Configuration Sheet
Article code: The Article Code
Serial no: The Serial number.
HW revision: Hardware revision
Production date: The date when the article was produced.
Test date: The date when the article was tested.
FATdate: The date when the Factory Acceptance Test was
found to be satisfactory.
118 B4040 Rev. A

Configuration
4.5.2 64 kbit/s Channels
Two 64 kbit/s channels can be inserted into the TOH. Each of the 64 kbit/s
channels will occupy one byte of the TOH frame. Press the SOH Frame
button to select which bytes of the TOH 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

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 IV-37 64 kbit/s Channels Configuration Sheet
B4040 Rev. A 119

Fields: Choices: Description
Status:
Enabled Enables the 64 kbit/s Channel.
Disabled Disables the 64 kbit/s Channel.
Type: Choose linecode for 64 kbit/s Channel.

V.11 Contra (Channel V.11)
G.703 Co (Channel G.703)
G.703 Contra (Channel G.703)
Direction: Choose the direction the 64 kbit/s Rx

Channel should be extracted from.
Line 64 kbit/s Rx is inserted from
line SOH frames.
Radio 64 kbit/s Rx is inserted from
radio SOH frames.
Timeslot: Shows which timeslot in the SOH the

64 kbit/s Rx Channel occupy.
120 B4040 Rev. A

Configuration
4.5.3 TOH X-Connect
Two 64kbit/s (one TOH timeslot) cross-connections can be set up. The
cross-connections bypass the SONET processing so that the TOH time-
slots are sent from the Line receive unit directly to the Radio transmit unit.
The TOH X-Connect configuration sheet can be opened from the Config-
uration context menu of the IDU node in the Explorer view. The sheet can also
be invoked by selecting (highlighting) the IDU node in the Explorer view and
then selecting Edit X-Connect from the Configuration menu.
Figure IV-38 TOH X-Connect Configuration Sheet
Enabled/Disabled Switches TOH X-Connect on/off
Line timeslot The time slot to bypass the Sonet processing.
Radio timeslot The destination time slot.
B4040 Rev. A 121

4.5.4 Error Pulse Output
For test purposes.
The baseband processing gives 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 Config-
be invoked by selecting the IDU node in the Explorer view and then selecting
Edit Error Pulse Output from the Configuration menu.
Figure IV-39 Error Pulse Output Configuration Sheet

Enabled/Disabled Toggles Error Pulse Output On/Off
Source Only one source
at a time.
FEC radio The output pin reflects the error
correction activity.
B1 line The output pin reflects the B1-parity
errors on the Line Receive side.
B2 line The output pin reflects the B2-parity
B1 radio The output pin reflects the B1-parity
B2 radio The output pin reflects the B2-parity
122 B4040 Rev. A

Configuration
4.5.5 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 Config-
then selecting Edit Auxiliary Output from the Configuration menu.
Figure IV-40 Auxiliary Output Configuration Sheet

Controls: Choices: Description:
Output control Manual Control Set the usage of the aux.output
radio buttons or pin. (This will be disabled if the
Alarm Trigger CityLink does not support
alarm triggers.)
Manual relay Closed or Open If the aux. output is set to
status radio manual control, these buttons
buttons will be enabled, and can be used
to manually control the state of
the relay.
B4040 Rev. A 123

Equipment tree Displays and selects the alarms
available for alarm triggers.
This will be disabled if the aux.
output is set to manual control.
Alarm trigger list Displays the alarm triggers
configured. This will be dis-
abled if the aux. output is set to
manual control.
Add alarm button Adds the currently selected
alarm in the equipment tree to
the alarm trigger list. If there is
no selection, or if the selected
tree node doesnt correspond to
an alarm, nothing happens.
Disabled if the output is on
manual control.
Remove Removes the currently selected
alarm button alarm from the alarm trigger list.
manual control.
Alarm triggered Closed or Open If the aux. output is set to alarm
radio buttons triggered control, these buttons
will be enabled, and can be used
to control the state of the relay
when the alarm conditions are
raised.
Buttons:
Get: Press this button to retrieve the current settings from the NE.
dialog box is opened).
Set: Press this button to update the element with any changes made to
any of the Auxiliary Output pages in the dialog box.
Close: Closes the dialog box.
Help: Press this button to get help on the current property sheet. For help
on an item, click at the top of the dialog box, then click the item.
124 B4040 Rev. A

Configuration
4.5.6 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 IV-41 Diagnose Configuration Sheet

Module Status Comments
CPLD OK/Not OK A write/read test sequence was performed
at last reset/startup.
RTC OK/Low bat/ A write/read test sequence was performed
Not running at last reset/startup.
LCD OK/Not OK A write/read test sequence was performed
DRAM OK/Not OK A write/read test sequence was performed
SRAM OK/Not OK A write/read test sequence was performed
Code FLASH OK/Not OK A write/read test sequence was performed
Boot FLASH OK/Not OK A write/read test sequence was performed
Viterbi Decoder OK/Not OK A write/read test sequence was performed
at last startup.
SORP OK/Not OK A write/read test sequence was performed
at last startup.
B4040 Rev. A 125
4.5.7 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 OC-3 traffic will be terminated.
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 IV-42 Self Test Dialog Box
4.5.8 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 Default value Alarm severity

HBER Indicator for BER > 1e-3 MAJOR
LBER Indicator for LBER > 1e-6 MINOR
EW-BER Indicator for EW-BER > 1e-10 WARNING
126 B4040 Rev. A

Configuration
Internal proportions: HBER > LBER > EW
The BER Threshold configuration sheet can be opened from the Configu-
ration 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 IV-43 BER Threshold Configuration Sheet

HBER 1.0·10-3 - 1.0·10-10 Error bit rate
A Major alarm is generated when the Viterbi
error rate exceeds the HBER threshold value.
AIS is inserted when the HBER threshold
value is exceeded.
LBER 1.0·10-3 - 1.0·10-11 Error bit rate
A Minor alarm is generated when the Viterbi
error rate exceeds the LBER threshold value.
EW 1.0·10-3 - 1.0·10-12 Error bit rate.
A Warning is generated when the Viterbi
error rate exceeds the Error Warning
threshold value.
B4040 Rev. A 127

4.5.9 OSI Configuration
The OSI configuration has to be set to get OSI traffic on your LAN, routed
through the Nera network.
4.5.9.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 IV-44 OSI Configuration Sheet, Line Coding Tab
NI1: The line coding for the NI1 interface. Can be NRZ or NRZI.
NI2: The line coding for the NI2 interface. Can be NRZ or NRZI.
DCC Line: The line coding for the DCC Line interface.
Can be NRZ or NRZI.
DCC Radio: The line coding for the DCC Radio interface.
Can be NRZ or NRZI.
128 B4040 Rev. A

Configuration
4.5.9.2 OSI Parameters
Configure the OSI parameters for the different communication channels.
To enable OSI for the different channels, do this at the appropriate commu-
nication ports configuration page. Link state protocol buffer size applies to
all channels.
Figure IV-45 OSI Configuration Sheet, Parameters Tab
B4040 Rev. A 129

Fields: Subfield: Description:
NSAP Address Area ID Subnet address.

Host ID End system address.
End Selector Type of service. Always 01.
Link state Transmitted buffer length size of IS

protocol hello-packets.(512-1492 bytes)
buffer size
Parameters MTU size Maximum Transmission Unit size.

(512-1497 bytes)
DefaultMetric Cost of path.
LAPD Role: Client/Server role
The two ends of a communications line
must be configured with the opposite
roles in order to communicate!
OSI Enabled This control is checked if OSI is
enabled for the respective interface.
This is set in the NI or DCC Commu-
nication Ports Configuration pages
130 B4040 Rev. A

Configuration
4.5.9.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 IV-46 OSI Configuration Sheet, Routing Table Tab
Host Id End system address.
Metric Cost of path.
B4040 Rev. A 131

4.5.9.4 OSI Interface Information
There will be one line in the table for each channel enabled for OSI.
Figure IV-47 OSI Configuration Sheet, Interface Information Tab
Id Numbering of interfaces in the network
InterfaceName Network user
Media Type of media
Status Indication of connection status (Up or Down)
MTU Size Maximum transmission unit size
132 B4040 Rev. A

Configuration
4.5.10 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 Configura-
tion 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 IV-48 Laser Control Configuration Sheet
B4040 Rev. A 133

Fields: Buttons: Description:
ALS:
Enabled/Disabled Toggles ALS On/Off
Waiting Time (1.0 - 5.0 minutes ) Specifies waiting
time before the laser is turned on. If
section of operation is connected and
optical signal from far end is present,
laser will remain on, if not laser will
be turned off after 2 seconds.
Get Retrieves Laser Control settings
from the NE.
Set Sends Laser Control settings to the NE.
Restart (2 Seconds) Manually restart the laser for
2 seconds.
90 seconds for testing purposes.
Manual
Control: (ALS disabled or not implemented)
On Manually turn the laser on.
Off Manually turn the laser off.
Status: Shows the status of the Laser Unit.
134 B4040 Rev. A

Configuration
4.5.11 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 IV-49 The IDU Replace Unit Wizard
B4040 Rev. A 135

4.6 DS3 Tributary Card
4.6.1 DS3 Configuration
The DS3 functionality allows the operator to connect two Virtual Containers
(VC) in different ports. The connections are identified by using the back-
ground color of the ports together with the KLM address of the virtual
container. The background color 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 IV-50. 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 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 port does not support traffic
looping, but does however support test looping. DS3 looping is only
available on the connected when the port has been configured to add/drop
traffic.
The DS3 Configuration sheet can be opened from the Configuration context
menu of the DS3 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 .
136 B4040 Rev. A

Configuration
Figure IV-50 DS3 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.
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.
B4040 Rev. A 137

4.6.2 DS3 Frame Structure Configuration
The operator may configure the frame structure on the three ports. Each port
consists of three TUG-3s ( 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 IV-51 Virtual Containers
138 B4040 Rev. A

Configuration
Figure IV-52 DS3 Frame Structure Configuration Sheet
Buttons:
VC-3: Sets the current structure to VC-3.
VC-12: Sets the current structure to VC-12.
Get: Press this button to retrieve the current settings from the
NE. (The settings are automatically retrieved from the
NE when the dialog box is opened).
Set: Press this button to send the settings to the NE.
Help: Press this button to get help on the current property sheet. For
help on an item, click at the top of the dialog box, then click
the item.
SDH: This button indicates that the transmission standard is set to
SDH.
SONET: This button indicates that the transmission standard is set to
SONET.
B4040 Rev. A 139

4.7 EtherLink V.2 Tributary Card
For EtherLink V.1; please refer to Section V.
4.7.1 Node Tree
Figure IV-53 EtherLink V.2 Node Tree
140 B4040 Rev. A

Configuration
4.7.2 Enabling of Board
Right click on transmission → configuration → transmission configuration
Figure IV-54 EtherLink V.2 Transmission Configuration
B4040 Rev. A 141

4.7.3 Board Configuration - step 1
Figure IV-55 EtherLink V.2 Node Tree
Right click on Gigabit Ethernet Extension Board → configuration

and then
→ Board Configuration
→ Board Status
→ Port Configuration
or → Port Status
142 B4040 Rev. A

Configuration
4.7.4 Board Configuration - step 2
Figure IV-56 EtherLink V.2 Board Configuration
B4040 Rev. A 143

• Operation Mode:
For selection between 2 + 0 (Radio + Line) and 1+0 (Radio) configurations
• Buffering Strategy :
For selection between Maximum Throughput and QoS
• If QoS buffering strategy is selected:

• QoS Scheduling Mode:
for selection between strict priority or fair queuing.
• TOS Mapping:
6 bit DSCP is represented by 64 decimal values which can each be mapped
into four traffic queues
• VLAN user priority/Port priority:
3 bit VLAN user priority is represented by 8 decimal values which can
each be mapped into four traffic queues.
4.7.5 Port Configuration
Figure IV-57 EtherLink V.2 Port Configuration
144 B4040 Rev. A

Configuration
All ports can be individually configured
• Enable port:
Enable/Disable the port
• Port Speed:
Auto,10/100 half/full duplex for fast Ethernet prots, and in addition for
port 5; 1000 full duplex. Port 6, SFP, is 1000 Base-X only
• Ingress rate limits :
stepwise from 500 kbps to 83 Mbps and not limited (100 Mbps or link
capacity) for fast Ethernet ports and stepwise from 500kbps to 250 Mbps
and not limited (link capacity) for gigabit ports.
• LLF:
Enable/disable link loss forwarding.
• If Buffer Strategy is QoS in the Board Configuration window:
• Flow control:
Enable/Disable for ports 1 to 5. This is available only when the ingress
rate is set to not limited.
• Port priority:
The individual port priority mechanism is a two step process. Firstly,
each port is mapped into the 8 decimal values representing VLAN user
priority. The port queuing will then become equal to the corresponding
VLAN priority which is set in the board configuration window. Port
priority and its mapping via VLAN user priority, will be set independ-
ently from the enabling/disabling of the Enable VLAN user priority
selector.
• Enable VLAN user priority Enable/Disable the VLAN user priority.
While enabled, incoming packets with a particular VLAN user priority
value (0, .., 7) will be queued according to the VLAN settings in the
board configuration window.
• Enable IP TOS priority - Enable/Disable the IP/TOS priority. While
enabled, incoming packets with a particular TOS setting (0, .., 63) will
be queued according to the IP/TOS settings in the board configuration
window.
B4040 Rev. A 145

4.8 6-11GHz ODU
4.8.1 RF Power
The XCVR Unit provides a set of RF power control functions:
RF input alarm thresholds can be set such that an alarm is raised when
the input level exceeds the upper or lower limits.
ATPC (Automatic Transmitter Power Control) is a function for effec-
tively reducing the interference probability in the network. When ATPC
is enabled, the output power from the transmitter is automatically
controlled according the received input power on the other side of the
hop. The ATPC alarm is generated if the ATPC regulation loop fails.
This alarm can be optionally delayed.
If ATPC is not enabled, the transmitted output level can be set. The
transmitter can also be muted.
The RF Power property sheet is used to display/configure the RF Power

control settings.
Figure IV-58 RF Power Configuration Sheet
146 B4040 Rev. A

Configuration
Fields:
Mute output power: When checked the output power is muted.
Maximum output level (dBm): The transmitters 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.
B4040 Rev. A 147

4.8.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 IV-59 Frequency Configuration Sheet
148 B4040 Rev. A

Configuration
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: OC-3 or OC-1.
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.
B4040 Rev. A 149

4.8.3 DRO Tuning
The XCVR Units 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.
Figure IV-60 DRO Tuning Configuration Sheet
DRO Tuning Mode:
• Disabled: DRO Tuning mode is disabled for both DROs
• TX Tuning: Enables DRO Tuning mode for TX DRO
• RX Tuning: Enables DRO Tuning mode for RX DRO
Status TX: Displays information concerning frequency lock
and screw direction for TX DRO
Status RX: Displays information concerning frequency lock
and screw direction for RX DRO
150 B4040 Rev. A

Configuration
4.8.4 DRO Tuning Procedure
Note! To Access the tuning screws, remove the sealing screws and washers.
After the tuning, the sealing washer (Nera article code: 97W35A-C6) must
be replaced to ensure proper sealing.
Tx Tuning
Alarm LED
Rx Tunin
g
Figure IV-61 DRO Tuning Procedure
B4040 Rev. A 151

4.8.4.1 Frequency Setting
Highlight the actual Transceiver unit to be tuned. Right click and choose
Configuration and Frequency.
Transceiver Unit Ch.1
Figure IV-62 Selecting in Explorer View the Transceiver to be tuned
See Chapter 4.8.2 for setting of frequency.
152 B4040 Rev. A

Configuration
4.8.4.2 DRO Tuning
Highlight the actual Transceiver unit to be tuned. Right click and choose
Configuration and DRO Tuning
Transceiver Unit Ch.1
Figure IV-64 Selecting DRO tuning from the Explorer View
Tx tuning

Select Tx tuning in the DRO Tuning Mode field. Press the Set button.
B4040 Rev. A 153
Figure IV-66 DRO Tuning Configuration Sheet, Tx tuning
The red arrow indicates which way to adjust the DRO. In addition The Alarm
LED 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.
154 B4040 Rev. A

Configuration
Rx Tuning

Select Rx tuning in the DRO Tuning Mode field. Press the Set button.
B4040 Rev. A 155

Figure IV-68 DRO Tuning Configuration Sheet, Rx tuning
The red arrow indicates which way to adjust the DRO. In addition The Alarm
LED 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.
156 B4040 Rev. A

Configuration
4.8.5 Production Data
The different boards/units contain some production information. This
information is displayed in the Production Data property sheet.
Figure IV-69 Production Data Configuration Sheet
Article code: Uniquely identifies the type of board/unit.
Serial no.: The serial number of the board/unit.
HW revision: The hardware revision.
Production date: When the production process was completed for
this board/unit.
Test date: When this product was tested by the factory test-
department.
Message info field: Displays status of data exchange between GUI and
NE.
B4040 Rev. A 157

4.8.6 Space Diversity
A Space Diversity system is using two antennas (denoted Main and
Space) mounted apart and connected to one Space Diversity transceiver
to achieve better performance. This requires different wave guide lengths for
the two antennas, which results in different signal propagation delays at the
Main and Space receiver inputs.
To compensate for this effect the transceiver can add delay in one of the
signal paths (normally in the Space path). Optimal receiver performance
requires an accurate delay compensation.
The two antenna signals are combined to get a single received signal for the
demodulation process.
The combiner can operate in automatic mode (controlled by signal quality

criteria derived internally in the transceiver) or in manual mode (user selects
how to combine the signals).
4.8.6.1 Configuration
Figure IV-70 Space Diversity Configuration Sheet
158 B4040 Rev. A

Configuration
Combiner mode: Auto: The transceiver selects which signal to
use.Disables Channel(s) used combo box.
Manual: The user selects which signal to use.
Enables Channel(s) used combo box.
Channel(s) used: Main, Space or Combined.
When Combiner mode is set to Manual, the user
may choose which signal to use.
When Combiner mode is set to Auto, it shows
whether the Main, or combined signal is used.
Note that the Automatic Gain Control level (AGC
level), that can be measured on the front of the
Transceiver, gives the level of the channel when
manually set to Space, while the level of the
Main channel is given when in automatic mode
or manually set to Main channel.
Automatic adjustment: Opens Automatic Space Delay Calculation
dialog and starts the coherent delay calculation
routine in the modem card.
NB! The routine uses the delay value currently
set on the transceiver as starting point for its
measurements and the coherent calculations. To
achieve the best result it is recommended that
the approximate delay is selected and set on the
transceiver before starting the mentioned routine.
Delay (ns): Add the specified delay to the Space signal
path. The valid range depends on the software
version on the transceiver.
4.8.6.2 Automatic Space Delay Calculation

To simplify installation of a Space Diversity system, an automatic space
delay calculation routine is implemented on the modem board. This routine
attempts to calculate the optimal delay for the given system based on
measurements from the modem board and transceiver unit.
Note! The routine uses the delay value currently set on the transceiver as
starting point for its measurements and the coherent calculations. To
achieve the best result it is recommended that the approximate delay is
selected and set on the transceiver before starting the automatic space delay
calculation routine.
B4040 Rev. A 159

Figure IV-71 Space Delay Calculation
The graph in the dialog displays the calculated Delay Compensation Value
as a function of the delay (in nanoseconds), and is updated each time a new
delay value is set in the transceiver. The delay currently used in the
calculation is displayed above the graph.
The optimal delay is normally found at the graphs minmum. The valid range
for the delay is -6 to 130 ns.
Zooming: Zoom in on details by left-clicking and dragging the

mouse. Zoom out by right-clicking.
Graph coordinates: If the cursor is positioned over a valid delay on the
graph, the coordinates for that delay are displayed in
a popup window:
160 B4040 Rev. A

Configuration
4.9 18-23GHz ODU
4.9.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 correspond-
ing Tx and Rx frequency must be set in the opposite NE.
Note! Dual Frequency - Single Polarization (DF-SP) requires two channels

in order to transmit 2xOC-3. 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.
B4040 Rev. A 161

Frequency Select the desired frequency plan. The frequency
plan plan must correspond to your transceiver.
Coding The coding function used in the modulator/
demodulator. These coding functions may 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 freq-
uency plan
Duplex Distance (MHz) The distance between the TX and the RX carrier
frequency.
Innermost Spacing (MHz)The distance between the highest selectable freq-
quency in the lower half of the plan and the lowest
selectable frequency in the upper half og the plan.
TX Frequency (GHz) The used TX Carrier frequency
RX Frequency (GHz) The used RX Carrier frequency
TX (min) (GHz) TX Lower sideband frequency for this frequency
plan
TX(max)(GHz) TX Upper sideband frequency for this frequency
plan
RX (min) (GHz) RX Lower sideband frequency for this frequency
plan
RX(max)(GHz) RX Upper sideband frequency for this frequency
plan

1. Get the current settings from the Network element by pressing Get. (The
settings are automatically retrieved from the NE when the property-sheet
is opened)
2. Alter the settings by clicking the frequency band you want to transmit
your TX data. The RX frequency is automatically updated since the
duplex Distance is fixed.
3. Press Set to send the changes to the NE.
162 B4040 Rev. A

Configuration
4.9.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

then selecting Edit Power from the Configuration menu.
Figure IV-73 Power Configuration Sheet
B4040 Rev. A 163

Fields: Denomination: Description:
RF input level dBm The upper threshold value for when

warning, high to generate an RF input level
warning (Alarm no. 1504)
RF input level dBm The lower threshold value for when warn-
ing, low to generate an RF input level
warning (Alarm no. 1504)
ATPC dBm Set the power level to use when an

alarm level ATPC alarm occurs.
ATPC dBm The wanted input level when ATPC

reference level is activated.
Mute Mutes the output power. No output

outputpower power is sent.
Maximum dBm Maximum output power for

outputpower transmitting
Manual dBm The output power level used when

output level ATPC is not activated
ATPC status ATPC Disabled/ Enabled
ATPCmode ATPC can operate in four different modes:

Automatic Regulation: The trans-
ceiver automatically regulates the
transmitter power
Minimum Output: A min. amount of
power is used for transmitting.
Maximum Output: A max. amount of
power is used for transmitting.
Freeze Output Power: A fixed amount
of power is used for transmitting.
ATPC Seconds The ATPC alarm can be delayed from

alarm delay 1 to 15 seconds.
164 B4040 Rev. A

Configuration
4.9.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 administra-
tor 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
menu. Availability of data in these fields depends on the actual ODU and
installation.
Figure IV-74 ODU Production Data Configuration Sheet
Article code: The article code
Serial no: The serial number.
HW revision: Hardware revision
Sales order: The purchase order.
Production date: The date when the article was produced.
Test date: The date when the article was tested.
FAT date: The date when the Factory Acceptance Test was
SAT date: The date when the Site Acceptance Test was
B4040 Rev. A 165
4.10 Antenna Data
This sheet shows some main characteristics of the antenna. Only the
Antenna code can be altered. The antenna data is stored in a database file.
The Antenna Data configuration sheet can be opened from the Configura-
tion 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 IV-75 Antenna Data Configuration Sheet
Antenna code The antenna code. Unique code for each antenna type.
Gain The antenna gain (dB). Gain is a measurement of the
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.
166 B4040 Rev. A

Configuration
4.11 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 IV-76 The ODU Replace Unit Wizard
B4040 Rev. A 167

5.0 Hot Standby

5.1 General
A CityLink Hot Standby system consists of two InDoor Units connected to
an IDU Switch and two OutDoor Units connected to the a HSB branching
unit. The IDU switch performs switching in the Rx direction, while the
branching unit has an RF-switch in the Tx direction.
Figure IV-77 Hot Standby Explorer view
5.1.1 Functionality
The IDU switch will perform most of the normal tasks of an IDU, with the two
IDUs maintaining modem functionality. Thus, configuration of line inputs,
wayside channels etc will be handled on the switch, while modem-specific
functionality (e.g Viterbi error pulses) is found on the IDU. Some function-
ality, like auxiliary outputs, are found in both places.
168 B4040 Rev. A

Configuration
5.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

and then selecting Edit Element ID from the Configuration menu.
Figure VIIII-78 Element ID Configuration Sheet
B4040 Rev. A 169

Serial number: The serial number of the NE. (Not editable)
NE type: The type of NE. (Not editable)
Name: The name of the NE (max. 32 characters)
Section address: The section address of the NE. (1-254)
NE address: The NE address (1-128). Used for identification of
NEs within a section.
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)

1 First, get the current settings from the NE by pressing Get.
property-sheet is opened.)
170 B4040 Rev. A

Configuration
5.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.
5.1.2.1 HSB Main Looping

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
Figure IV-79 HSB Looping Configuration Sheet
B4040 Rev. A 171

Fields:
Blue: The status of the loop is unknown. Loop informa-
tion has not been retrieved from the NE, or a loop message
has just been sent to the NE and the GUI is waiting for a
response from the NE. (The loop settings have not been
confirmed by the NE). Note that the loop cannot be toggled
when the status is unknown.
Black: The loop is off (inactive)
Loops will be Displays the time of which all main traffic loops in the NE
automatically will be cleared. This time is set by the user when activating
cleared after: a loop.
The different main traffic loops

(from left to right in the respective blocks in Figure IV-79):
• 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:
5.1.2.2 HSB 64kbit/s Looping

Please refer to Chapter 4.4.2 (this Section).
172 B4040 Rev. A

Configuration
5.1.3 Hot Standby Configuration
The Hot Standby configuration sheet shows the switching configurations
for the HSB-IDU.
The Hot Standby configuration sheet can be opened from the Configuration
context menu of the HSB-IDU node in the Explorer view. The sheet can also
be invoked by selecting (highlighting) the HSB-IDU node in the Explorer
view and then selecting Edit Hot Standby from the Configuration menu.
Figure IV-80 Common Tab in Element ID Configuration Sheet
Fields: Description
Auto / manual: Select between automatic or manual hot standby switching
Active branch: 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 Bi-
directional.
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.
B4040 Rev. A 173

5.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 Config-
uration 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 IV-81 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.
174 B4040 Rev. A

Configuration
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.
B4040 Rev. A 175

5.1.5 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.
5.1.6 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 opera-
tion.
176 B4040 Rev. A

EtherLink V.1 Configuration
SECTION V
B4040 Rev. A 177

Hyperterminal & Telnet

1.0 Hyperterminal & Telnet Commands
• First time configuration with hyper-terminal to IDU's LCT-
port.
Settings on com port; 9600, 8, 1, none.
Terminal emulation; VT100.
• Normal operation via IP.
Telnet session to IP-address on management port or one of the four
ethernet ports.
Figure V-1 Starting up and logging in
Login as admin with the password; adminpasswd
Note!
User ID: admin
178 B4040 Rev. A

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 ports 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 ports 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 1.5Mb/s or connect with computers on the LAN.
2 (1 .5 ) M b /s c ir cu it 1 - 4 2 (1 .5 ) M b /s c ir cu it 1 - 4
Ethernet Ethernet
CityLink IDU
CityLink IDU
Fast
Extension Fast
Extension
E Board
th e r n e t EBoard
th e r n e t
LAN 1 T rib u ta r y T rib u ta r y LAN 1
(EEB) (EEB)
M o d u le M o d u le
LAN 2 LAN 2
LAN 3 L AN 3
LAN 4 LAN 4
Figure V-2 Radio Connection
2.2 Testing
• How to verify transmission quality and capacity ?
One way to do this is to set up two computers and do a file transfer
(FTP) between them over the hop.
One PC working as FTP-server and one as FTP-client, check the

time for transfer of the file and calculate throughput.
Do not have any HUBs connected during this test.
Stability of the equipment and hop will be easiest monitored on

BER test with pattern-generator on a 1.5Mb/s.
B4040 Rev. A 179

3.0 Top Level Commands

After logon you should have this text on your screen;
Welcome to CityLink.
Copyright (c) Nera ASA.
CityLink>
Then type help and press enter:
Welcome to CityLink.
Copyright (c) Nera ASA.
CityLink> help
Help:
The following commands are available:
Command Function
alarms lists alarms
cls clear screen
enter enter submenu
env list environment variables
exit exit submenu
gettime display system timezone, time and date
help get help on commands
list list available commands
ping ping the specified host
quit quit shell
reboot shutdown the system and reboot
settime set system timezone, time and date
tracert trace route to target
Use "help <command>" to get help on specific command.
Example for usage of "Help":
CityLink> help gettime

gettime: display system timezone, time and date
Usage: gettime
CityLink>
180 B4040 Rev. A

3.1 Top Level Commands, Example
CityLink (radio)> alarms
Active alarms:
TIME ID NAME CLASS STATE
Modem.
2001.11.19 11.04.50 1104 E-WARNING WARNING Raised
2001.11.19 11.04.50 1103 LBER MINOR Raised
2001.11.19 11.04.50 1102 HBER MAJOR Raised
Baseband
2001.11.19.11.04.50 32808 LOS_RR MAJOR Raised
2001.11.19.11.04.50 32809 LOF_RR MAJOR Raised
2001.11.19.11.04.50 32811 MS-AIS_INSERT_RR MAJOR Raised
EEB
2001.11.19.11.04.50 32785 ETHERNET_PORT_2 INFO Raised
PerfManager
2001.11.19.11.15.01 3000 G826-15MIN-B1 WARNING Raised
2001.11.20.00.00.01 3003 G826-24HOUR-B1 WARNING Raised
CLIServer
2001.11.20.14.35.20 32782 CONSOLE_USER_LOGGED_IN INFO Raised
B4040 Rev. A 181

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 Function
autopartition enable / disable autopartition
eebstatus show GT-48350 link/partition status
get2mbport get 2MBit E1/T1 port state (from SW Version R1C0
this command has been replaced by gettribport)
getethmode get Ethernet ports speed and duplex mode
gettribmode get tributary E1/T1 ports mode
gettribport get tributary E1/T1 port state
getethport get Ethernet port state
getflowctrl get flow control for Ethernet port
listportmib list the MIB-statistics of a port
selectpriport select priority Ethernet port
set2mbport set 2MBit E1/T1 port state (from SW Version R1C0
this command has been replaced by settribport)
182 B4040 Rev. A

setethmode set Ethernet port speed and duplex mode
settribmode set tributary E1/T1 ports mode
settribport set tributary E1/T1 port state
setethport set Ethernet port state
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 Function
get64kg703 get g703 enable/disable
get64kv11 get v11 enable/disable
getlaser get current laser state
getwayside get wayside enable/disable
resetbaseband reset eeb module
set64kg703 set g703 enable/disable
set64kv11 set v11 enable/disable
setlaser sets the laser state
setwayside set wayside enable/disable
startlaser starts the laser
B4040 Rev. A 183

4.3 Modem Submenu (part of IDU)
validberlevels
BER = Bit Error Ratio, Number of errored bits divided on total number
of bits.
High BER = 1x10-3
Low BER = 1x10-6
Early Warning (BER) = 1x10-9
Modem submenu commands

Command Function
getberlevels get HBER, LBER and ER levels
getfirindex get current fir tap index
getserfindex get current serf set index
resetmodem reset modem
setberlevels set HBER, LBER and EW levels
setfirindex set current fir tap index
setserfindex set current serf set index
tempcomp get temperature compensation data
validberlevels 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 fre-
quency plan used on the system, because then these setting will be correct.
184 B4040 Rev. A

4.4 Radio Submenu (part of ODU)
Configuration of ODU
Set frequency, normally done during installation. However, this will be
necessary to set for spare parts.
Radio submenu commands:

Command Function Usage
Security
Level
downloadodusw transfer ODU SW No pa-
rameters master
from IDU to ODU
drotuning get/set ODU DRO drotuning [disable | tx | rx] master
tuning mode/status
getatpc get Automatic- No parameters passive
PowerControl settings
getfrequency get tx and No parameters passive
rx frequency
getmutestate get radio mute state No parameters passive
getrfpower get rf output No parameters passive
and input power
getrfwarning get RfInputLevel- No parameters passive
Warning up and
down
radiostatus display all No parameters passive
radio settings
reloadfreq transfer current No parameters master
frequency settings
to ODU
setatpc set Automatic- setatpc <state | rxref | almoutlevel | almdelay> master
PowerControl state: state <enable | disable>
functions rxref: rxref <level in dBm>
almoutlevel: almoutlevel <level in dBm>
almdelay: almdelay <delay in seconds>
setfrequency set tx and setfrequency <txfreq> <rxfreq> master
rx frequency
setmutestate set radio mute state setmutestate < on | off> master
setrfpower set rf output power setrfpower <OutputPower in dBm> master
setrfwarning set RfInputLevel- inputwarning <WarningLevelUp> master
Warning up and <WarningLevelDown>
down
B4040 Rev. A 185

4.4.1 Radio Status, Example
CityLink (radio)> radiostatus
Radio Configuration
Tx Frequency = 23198000 kHz ODU:RF input = -113.00 dBm
Rx Frequency = 22190000 kHz ODU:RF output = 14.00
Last FrqShift = Ok dBm
Tx Frequency Min = ODU:+48V = 48.00 V
23086000 kHz Radio Muted =0
Tx Frequency Max = 23534000 kHz Loop status =0
Rx Frequency Min = Loop capability =3
22078000 kHz Transceiver S/N = 96
Rx Frequency Max = 22526000 kHz Radio Type =1
Duplex Distance = 1008000 kHz Transceiver Type = 10
Rf Output Power = 15 dBm Boot Code Version = 1A0
Rf Output Power Max = 18 dBm App. Code Version = 4D2
Rf Output Power Min = 8 dBm App. Code Date = 2001-
Rf Input Warning Low = -60 dBm 12-04 17:04:55
Rf Input Warning Up = -35 dBm
ATPC state =0 Radio Alarms.
ATPC Rx Ref Level = -10 dBm Alarm : 1502 LOS_RF_INPUT
ATPC alm Out Level = 15 dBm Alarm : 1504 RF_INPUT_WARNING
ATPC alarm Delay = 12 sec.
4.4.2 Radio Commands, Example of Error Message

CityLink (radio)> setfrequency 22190000 23198000
Frequency out of range!
TxFrequency: 23198000 kHz

RxFrequency: 22190000 kHz
TxFreq.Min : 23086000 kHz
TxFreq.Max : 23534000 kHz
RxFreq.Min : 22078000 kHz
RxFreq.Max : 22526000 kHz
DuplexDistance: 1008000 kHz
CityLink (radio)> setfrequency 23198000 22190000
186 B4040 Rev. A

4.5 SU Submenu (part of IDU)
Important issues for maintenance and troubleshooting could be to investi-
gate RF-input level and DC-level in ODU.
SU submenu commands:
Command Function
getanaloge list analogue sensor measurements
getauxinput list aux port inputs signals and configuartion
getauxoutput list aux port outputs signals and configuration
getfan get fan status
setauxinput configure aux port inputs signals
setauxoutput configure aux port outputs signals
4.6 Security 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 Function
adduser make a new user account
changename change «current user» description name
changepwd change «current user» password
changesnmppwd change SNMP password (community string)
deleteuser delete user account
getiprange list secure IP ranges
getlog list security log
getsnmppwd list SNMP password (community strings)
getuser list users
resetlog resetlog deletes all entries in security log
resetsecurity reset security to factory settings
setiprange set secure IP range
setusername set User description name
setuserpwd set User password
who list users logged on
B4040 Rev. A 187

4.7 Performance Submenu
The Performance submenu shows the quality on your received signal from
opposite Citylink.
Perform submenu commands:
Command Function
getfec list FEC counter
getg826 list G.826 performance values
getpulses list error pulses
getthreshold list G.826 Thresholds
performstatus list all performance parameters available
resetfec reset FEC counter
resetg826 reset G.826 performance values
resetpulses reset error pulses
setthreshold set G.826 Thresholds
4.8 Configuration Submenu

Configuration of the CL Element
Set system type.
Set section and station address, name etc...
Important to execute command "setinterface" in order to enable
management via IP.
Config submenu commands:

Command Function
addroute Adds routes to the routing table
authenticate Authenticates access keys to enable licensed functionallity
deleteroute Deletes routes from the routing table
eebni Sets or gets state on EEB network interface
getsysmode Gets the system operation mode
inventory Prints inventory data
listnetconfig Lists the network configuration
listroute Lists the routing table
listsysconfig Lists current system configuration
setantennatype Sets the antennatype
setgateway Sets the default gateway
setinterface Sets the IP address and netmask of an interface
setsectionaddr Sets the section address
setstationaddr Sets the station address
setstationname Sets the station name
setsysconfig Sets system configuration
188 B4040 Rev. A

setsysmode Sets the system operation mode
snmpagent Enables or disables the SNMP agent
stationinfo Lists Station/Section info
updatesw Updates the system software
4.8.1 Management Settings

CityLink (config)> setinterface help
Usage: setinterface <if#> < [<ipaddress> <netrmask>] | [<disable>]>
if# : Interface no (1-5)
ipaddress : IP Address
netmask : Subnet Mask
disable : Disable Interface if#
CityLink (config)> setinterface 02 192.168.1.1 255.255.248.0
CityLink (config)> setgateway 192.168.7.15
CityLink (config)> listnetconfig
Network interfaces.
# Address Netmask Description
01 192.168.0.32.1 255.255.255.255 Management port
02 192.168.1.1 255.255.248.0 EEB interface 1
03 Disabled EEB interface 2
Default gateway : 192.168.7.15
4.9 Test & Fault Submenu

Test submenu commands:
Command Function
getloop get current looping state
setloop toggle looping state on/off
Fault submenu commands:

Command Function
alarmlog lists alarmlog entries
clearalarm clears an alarm
maskalarm masks an alarm
raisealarm raises an alarm
unmaskalarm unmasks an alarm
B4040 Rev. A 189

4.10 Q1module Submenu
Q1module submenu commands:
Command Function
listinterface List the nnp interfaces
listroutes Lists the nnp routing table
setaddress Set the Q1 address of the element
190 B4040 Rev. A

5.0 Software Upgrade Procedure for

the EtherLink V.1 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 V-3
B4040 Rev. A 191

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 V-4 Downloading using the Console FTP Client
192 B4040 Rev. A

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 V-5 Downloading using the Internet Explorer
B4040 Rev. A 193

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 V-6
194 B4040 Rev. A

NEW Network Management System

The management and supervision of EtherLink V.1 may be performed in
various ways depending on the actual application.
• NERAs NEW-NMS can work as an SNMP-manager and control and
supervise the radio-relay (described in the following chapters).
• The EtherLink V.1 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 V-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).
B4040 Rev. A 195

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 double 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.
196 B4040 Rev. A

Figure V-8 Adding IP Address
B4040 Rev. A 197

7.0 Network Element Configuration

Configuration of Network Elements is achieved using a set of property-
sheets. The property-sheets are modeless, so configuration of several
different modules can be displayed simultaneously.
· To open the configuration property sheets:

Select the object you want to view or change either from the Explorer View
or a Map View. Select a Configuration command either from the context
sensitive menu (right mouse-button) or from the Configuration Edit menu.
The property-sheets are divided into two categories by means of function-

ality:
Figure V-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 are sent to the element
and no data is modified in programs data structure before the user presses
one of the property-sheet buttons:
Buttons:
Set: Applies the current settings in the Network Element (NE).
Get: Retrieves the current settings of the Network Element (NE).
Close: Closes the property-sheet without saving or setting any data.

1 First, get the current settings from the NE by pressing Get. (The
settings are automatically retrieved from the NE when the property-
sheet is opened).
198 B4040 Rev. A

Configuration Property sheets with Single Interactive Settings:
The program retrieves the current NE settings when the property-sheet is
opened. There are 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 V-10 Buttons on Configuration property sheets with

single active settings
Buttons:
Close: Closes the property-sheet.
All property-pages have an information field at the bottom reflecting the

current status of the data shown in the property-page with the date and time
the property sheet data that was retrieved from the Network Element.
Figure V-11 Configuration property sheet information field
B4040 Rev. A 199

8.0 Element Node

8.1 Element Id
The CityLink Element Id property sheet shows main information about the
Network Element like name, type, serial number and different addresses. The
fields with white background can be altered by users with proper user
privileges The gray fields are non-editable.
The Element Id configuration sheet can be opened from the Configuration

and then selecting Edit Element ID from the Configuration menu.
Figure V-12 Element ID Configuration Sheet
Fields: Description
Serial Number: The serial number of the NE. (Not editable)
NE Type: The type of NE. (Not editable)
Name: The name of the NE. (max. 32 characters)
Section Address: The section address of the NE.
NE Address: The NE address. Used to identify NEs within a
section.
MAC Address: The Media Access Control address of the NE. (Not
editable)
IP Address: The Internet Protocol address of the NE.
200 B4040 Rev. A

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

and then selecting Edit NE Clock from the Configuration menu.
Figure V-13 NE Clock Configuration Sheet
The Elements 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
B4040 Rev. A 201

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

tion context menu of the Element node in the Explorer view. The sheet can
view and then selecting Edit SW Versions from the Configuration menu.
Figure V-14 SW Versions Configuration Sheet
SW Component: Software title
Bank: Software location
Revision: Sofware revision. The field will display unknown
if the system has this unit present, but is unable to
retrieve the information from it.
Status: Valid: Complete or valid software.
202 B4040 Rev. A

8.4 Production Data
The production data property sheet presents details about the HW compo-
nents within EtherLink V.1.
The Production Data configuration sheet can be opened from the Config-
uration context menu of the Element node in the Explorer view. The sheet can
menu.
Figure V-15 Production Data Property Sheet
InventoryName: The name of the HW component.
InventorySerialNumber: The serial number of the HW component.
InventoryVersion: The HW component version.
B4040 Rev. A 203

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
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 NEW-NMS.
Please see the EtherLink V.1 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 V-16 Element SNMP Settings Property Sheet
204 B4040 Rev. A

Columns: Description:
IP address The Internet Protocol address of the
NE (not editable).
Set Community: The community string used when
setting information at the element
(set request).
Get Community: The community string used when
retrieving information at the element
(get/getNext request).
Port: Element UDP Port for
Get/Getnext/Set
No. Receivers: Number of Managers set up to receive
traps from this element.(Not used)
· Edit values in the list:

The values of the columns SetCommunity, GetCommunity, Port, and No
Trap receiving Managers can be modified:
1. Double click cell to be edited.
2. Type new value.
3. Click outside cell.
4. To save your settings press Set.
B4040 Rev. A 205

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
and then selecting Edit Trap Table from the Configuration menu.
Figure V-17 Trap Table Configuration Sheet
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
206 B4040 Rev. A

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 V-18 System Info Property Sheet
The MIB II Info configuration sheet can be opened from the Configuration
and then selecting Edit MIB II Information from the Configuration menu.
B4040 Rev. A 207

Sys Description: A textual description of the entity. This value should
include the full name and version identification of the
systems hardware type, software operating-system,
and networking software. It is mandatory that this only
contain printable ASCII characters.
Sys OID: The vendors 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.

In order for the user to change settings the Set Community name must be
configured as described in SNMP Agent(s) settings.
1 First, get the current settings from the NE by pressing Get. (The
settings are automatically retrieved from the NE when the property-
sheet is opened).
208 B4040 Rev. A

8.8 MIB-II SNMP Group
The MIB-II SNMP property page presents the performance of the underlay-
ing SNMP implementation on the managed entity and tracks things such as
the number of SNMP packets sent and received.
A complete description of each field is available by holding the mouse cursor
over wanted item in the dialog and the description found in RFC-1213 will be
displayed.
Figure V-19 MIB-II SNMP Property Sheet
OID Object IDentifier, uniquely defines a managed objects. These
can appear in two forms: numeric (i.e. 1.3.6. 1.2.1.11.1) and
«human readable» (i.e. iso.org.dod.internet.mgmt.mib-
2.snmp.snmpInPkts)
NEW-NMS uses «human readable» form and will display the
above example as snmpInPkts.
Value Value contained in this OID.
B4040 Rev. A 209

8.9 Looping
and then selecting Edit looping from the configuration menu.
The loop settings are divided into three categories: Main Traffic Loops,
1.5Mbit/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.
210 B4040 Rev. A

8.9.1 Main Traffic Loops
Figure V-20 Looping Configuration Sheet

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
Note! FAR end loop will break management traffic to other side.
B4040 Rev. A 211

8.9.2 Wayside Loops
Figure V-21 Looping Configuration Sheet, Wayside Channel Tab
The different 1.5Mbit/s Wayside Loops:

Wayside Loop (far end)
Wayside Loop (near end)
212 B4040 Rev. A

8.9.3 64 kbit/s Loops
Figure V-22 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)
B4040 Rev. A 213

9.0 In Door Unit (IDU)

9.1 64 kbit/s Channels
Two 64 kbit/s channels can be inserted into the SOH. Each of the 64kbit/s
channel will occupy one byte of the SOH frame. Both channels can be
retrieved from and inserted into the line and radio side independently.
The 64 kbit/s Channels configuration sheet can be opened from the
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 V-23 64kbit/s Channels Configuration Sheet

Status: Enabled Enables the 64 kbit/s Channel
Disabled Disables the 64 kbit/s Channel
Direction: Choose the direction the 64 kbit/s Rx channel
should be extracted from.
Line 64 kbit/s Rx is inserted from line SOH frames
Radio 64 kbit/s Rx is inserted from radio SOH frames
9.2 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
214 B4040 Rev. A
9.2.1 Ethernet Ports
Figure V-24 Ethernet Ports Configuration Sheet
portEthStatus This entry enables/disables the port.
portEthFlowCtrl This entry controls flow control setting.
portEthLinkStatus This entry shows the current link status.
portEthPartitionStatus This entry shows the current partiton
status for the port.
portEthLinkSpeed This entry controls the link speed for the
port.
portEthLinkDuplex This entry controls the link duplex mode for
the port.
portEthLinkFailureShutdown This entry controls the Link Failure
Shutdown mode for the port.
When enabled port is forced shutdown
due to SDH alarm or remote ETH-port no
Link.
Note: Port is NOT forced shutdown as
described above if IP management is
enabled on port.
B4040 Rev. A 215

Priority Port Designates the prioritized port.(Guaranteed
100Mb operation.)
Auto Partition Auto partition state for the EEB ethernet
ports.
Note :
Ethernet Port fixed speed / duplex mode setting:
1) Set user terminal equipment speed / duplex mode to Auto.
2) On EtherLink V.1 port; set required link speed.
Note: It is not recommended to use 10Mb Half duplex .
9.2.2 1.5Mbit/s Ports

Configuration of tributary E1/T1 ports (2Mbit/s or 1.5Mbit/s).
Figure V-25 1.5Mbit/s Ports Configuration Sheet
port2MBIndex Tributary E1/T1 port index .
port2MBStatus Presents the status of the tributary E1/T1 port.
216 B4040 Rev. A

9.3 2 Mbps Wayside Channel
Normally not used in NA.
A Wayside channel can be inserted in the TOH in either line-direction or
radio-direction. The Wayside channel will occupy 33 bytes (32 bytes data
+ 1 byte alignment information) of the TOH. 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 V-26 Wayside Channel Configuration Sheet
Fields: Options: Description

Status: Enabled Enables the Wayside Channel
Disabled Disables the Wayside Channel
Direction: Line Wayside Rx is extracted from line TOH
Radio Rx is extracted from radio TOH.
B4040 Rev. A 217

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 Config-
then selecting Edit Auxiliary Output from the Configuration menu.
Figure V-27 Auxiliary Output Configuration Sheet
218 B4040 Rev. A

Output control radio Manual control Set the usage of the auxiliary
buttons: or output pin. (Disabled if the
Alarm triggered CityLink does not support alarm
triggers.)
Manual Relay status Closed or open If the auxiliary output is set to

radio buttons manual control, these buttons
will be enabled, and can be used
to manually control the state of
the relay.
Equipmenttree - 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 doesnt correspond
to an alarm, nothing happens.
manual control.
Remove alarm button - Removes the currently select-

ed alarm from the alarm trigger
list. Disabled if the output is on
manual control.
Alarm triggered relay Closed or Open If the auxiliary output is set to

status radio buttons alarm triggered control, these
buttons will be enabled, and can
be used to control the state of
the relay when the alarm-
conditions are raised.
B4040 Rev. A 219

9.5 BER Thresholds
The Viterbi decoder is a component using a Viterbi low complexity algorithm
for decoding/error correcting the received bit-sequence in the NE. The
viterbi error rate is used as a quality measurement for the radio hop.
When the Viterbi error rate exceeds certain values, alarms are generated. The
threshold values decides when alarms are generated. The threshold values
can be changed by the user.
Alarm Id Default value Alarm severity

HBER Indicator for BER >1exp-3 MAJOR
LBER Indicator for LBER >1exp-6 MINOR
EW-BER Indicator for EW-BER >1exp-10 WARNING
Internal proportions: HBER > LBER > EW
The BER Threshold configuration sheet can be opened from the Configu-
ration 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 V-28 BER Threshold Configuration Sheet
220 B4040 Rev. A


HBER 1.0e - 1.0e
-3 -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.
B4040 Rev. A 221

9.6 Laser Control
Available on EtherLink V.1 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 Configura-
tion 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 V-29 Laser Control Configuration Sheet
222 B4040 Rev. A

Fields: Buttons: Description:
ALS:
Enabled/Disabled Toggles ALS On/Off
Waiting Time (1.0 - 5.0 minutes ) Specifies waiting
time before the laser is turned on. If
section of operation is connected and
optical signal from far end is present,
laser will remain on, if not laser will
be turned off after 2 seconds.
Get Retrieves Laser Control settings
from the NE.
Set Sends Laser Control settings to the NE.
2 seconds.
90 seconds for testing purposes.
Manual
Control: (ALS disabled or not implemented)
On Manually turn the laser on.
Off Manually turn the laser off.
Status Shows the status of the Laser Unit.
B4040 Rev. A 223

10.0 Out Door Unit (ODU)

10.1 Antenna Data
This sheet shows some main characteristics of the antenna. Only the antenna
code can be altered. The antenna data are stored in a database file.
The Antenna Data configuration sheet can be opened from the Configura-
tion 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 V-30 Antenna Data Configuration Sheet
Antenna code The antenna code. Unique code for each antenna type.
Gain The antenna Gain. (dB) Gain is a measurement of the
antennas ability to transform electrical signals to
electromagnetic waves.
Polarization The polarization direction of the antenna.
FB Front/Back Ratio. Ratio between the Gain in forward
direction and Gain in backward direction.
Diameter The physical antenna diameter. [ Meter]
Frequency range The frequency range where the antenna can be
expected to operate successfully.
224 B4040 Rev. A

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 Configu-
ration 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 V-31 Power Settings Configuration Sheet
B4040 Rev. A 225

Fields: Denomination:Description:
RF-INPUT- dBm The upper threshold value for when to

WARNING- generate a RF Input Level Warning
high (Alarm nr. 1504).
RF-INPUT- dBm The lower threshold value for when to

WARNING- generate a RF Input Level Warning
low (Alarm nr. 1504).
Manual dBm The output power level used when ATPC

output level not is activated.
Mute output Mutes the output power. No output power

power is sent.
Maximum dBm Maximum output power for

output power transmitting.
Manual Disable ATPC.

Transmit
Output Power
(MTPC)
Automatic Enable ATPC.

Transmit
Output Power
(ATPC)
Reference dBm The wanted input level when ATPC is

input level activated.
Default dBm Set the Power Level to use when an

output level ATPC alarm occurs.
ATPC alarm seconds The ATPC alarm can be delayed a

delay certain number of seconds.
226 B4040 Rev. A

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 correspond-
ing 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

then selecting Edit Frequency from the Configuration menu.
Figure V-32 Frequency Configuration Sheet
B4040 Rev. A 227

Fields: Denomination: Description:

Frequency plan Choose the wanted frequency plan.
The frequency plan must.
correspond to your transceiver.
TX Frequency MHz The used Tx Carrier frequency.
RX Frequency MHz The used Rx Carrier frequency.
Modulation The modulation scheme used with
this frequency plan.
Data rate OC-3 or OC-1
Channel spacing MHz The distance between the channels
in this frequency plan.
Duplex Distance MHz The distance between the Tx and
the Rx carrier frequency.
Innermost MHz The distance between the highest
spacing frequency in lower half and the low-
est frequency in the upper half of
the frequency plan.
Compensation Digital filters in the Modem Board
filter compensating for RF Filter and
branching characteristics.
TX Frequency MHz Tx Lower sideband frequency for
Band,Min this frequency plan.
TX Frequency MHz Tx Upper sideband frequency for
Band,Max this frequency plan.
RX Frequency MHz Rx Lower sideband frequency for
Band,Min this frequency plan.
RX Frequency MHz Rx Upper sideband frequency for
Band,Max this frequency plan.
Status The result of the last frequency
change operation (unknown, ok,
executing, failed).
Reset Modem When this item is checked the
modem will be reset when applying
selected frequency data. Only to be
used when changing frequency plan.
NOTE!
Both the IDU and the ODU must be rebooted after a change of frequency and/
or Reed Solomon code. This is done by disconnecting and reconnecting
power to the IDU.
228 B4040 Rev. A

11.0 Performance
11.1 G826 Performance
G.826 is an ITU-T quality recommendation for SONET 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
the Explorer view and then selecting Performance Registers from the
Main menu.
Figure V-33 G-826 Performance Configuration Sheet
B4040 Rev. A 229

Time interval The interval of the measurement (15 min., day, month).
Period The sequence number of the performance register.
Register 0 is the running measurement, register 1 is the
latest completed measurement.
SES Severely Errored Seconds. The number of one-second
periods which contains > 30% errored blocks or at least
one Severely Disturbed.
UAS The number of UnAvailable Seconds. A period of un-
available time begins at the onset of 10 consecutive SES
events. These ten seconds are considered to be a part of
the unavailable time. A new period of available time
begins at the onset of ten consecutive non-SES events.
These 10 seconds are considered to be part of available
time.
BBE The number of Background Block Errors. An errored
block not occurring as part of an SES.
ES Errored Second. The number of one second periods
with one or more errored blocks.
Start Time The start time of the measurement period.
Status Status of the counter.
230 B4040 Rev. A

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 is gathered from
the RFC-2108 MIB.
The Port Performance configuration sheet can be opened from the Per-
formance context menu of the IDU node in the Explorer view.
Figure V-34 Port Performance Configuration Sheet
Readable frames Please refer to RFC-2108 MIB.
Readable octets Please refer to RFC-2108 MIB.
Runts Please refer to RFC-2108 MIB.
Late events Please refer to RFC-2108 MIB.
Autopartition Please refer to RFC-2108 MIB.
Total errors Please refer to RFC-2108 MIB.
B4040 Rev. A 231

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.
Figure V-35 Repeater Performance Configuration Sheet
Tx Collisions Please refer to RFC-2108 MIB.
Total Frames Please refer to RFC-2108 MIB.
Total errors Please refer to RFC-2108 MIB.
Total octets Please refer to RFC-2108 MIB.
232 B4040 Rev. A

12.0 Fault
12.1 NE Alarm Log
The NE Alarm Log property sheet displays the settings and content of the
NE alarm log.
The NE Alarm Log configuration sheet can be opened from the 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 V-36 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.
Figure V-37 Number of Records Dialog Box
Controls: Options: Description:

Log full action Wrap or Halt Actions to take when the log is full.
Max. number - The number of entries theNE alarm
of events log can hold.
Number of events - Current number of log entries.
B4040 Rev. A 233

13.0 Security
13.1 Security Log
EtherLink V.1 has an internal security log that can contain up to 1000 events.
To view the local security log, select an EtherLink V.1 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 V-38 Security Log
Security Log Index The index of the Security log
Security log entry text A descriptive text of the event.
Security log entry time The time of the event.
234 B4040 Rev. A

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 MIBs

The EtherLink V.1 embedded application supports the following MIBs
Name Description Defined in

ETHERLINK V.1 Specific management of Nera_Clip.mib
EtherLink V.1 devices.
NERA-MIB General management of Nera.mib
Nera radio equipment.
SNMP-REPEATER-MIB General management/ RFC 2108
monitoring of
repeater units.
RFC1213-MIB (mib2) General management of RFC 1213
network devices.
ETHERLINK V.1-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.
B4040 Rev. A 235

16.0 MIB Overview

The MIB is separated into 8 sub-modules as shown below.
Figure V-39 MIB Overview
236 B4040 Rev. A

16.1 Unit
This unit contains entries related to overall system properties. This includes
system time, status, transmission settings and management addressing
Figure V-40 MIB Sub-modules, Unit
B4040 Rev. A 237

16.2 IDU
This module provides configuration and monitoring of IDU hardware
interfaces. This includes the Ethernet ports, 1.5Mbit/s ports, 64kbit/s ports
and the auxiliary port. The module also contains the global error level limits
for the IDUs data inputs.
Figure V-41 MIB Sub-modules, IDU
238 B4040 Rev. A

16.3 ODU
This module contains the ODU specific control settings and operational
status. The ODU functional capabilities are obtainable through the capa-
bilities sub module.
Figure V-42 MIB Sub-modules, ODU
B4040 Rev. A 239

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 V-43 MIB Sub-modules, Test Manager
240 B4040 Rev. A

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 V-44 MIB Sub-modules, Performance Manager
B4040 Rev. A 241

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
considerably.
Figure V-45 MIB Sub-modules, Fault Manager
242 B4040 Rev. A

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 V-46 MIB Sub-modules, Analogue Value
16.8 Security Manager

This module implements a simple facility to retrieve security related informa-
tion from the system.
Figure V-47 MIB Sub-modules, Security Manager
B4040 Rev. A 243

244 B4040 Rev. A

Troubleshooting
SECTION VI
Troubleshooting
B4040 Rev. A 245

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 Description of Alarm LEDs

2.1 IDU Alarm LEDs
The functions of the alarm LEDs are as follows:
CRITICAL Red Will be activated when one or more
critical alarms are activated
MAJOR Red Will be activated when one or 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
246 B4040 Rev. A

Troubleshooting
2.3 LEDs on Line Interface Plug-in Boards
G.703 Line interface:
Green LED is activated when input signal is present.
Multimode Fiber Line interface:

Singelmode Fiber Line interface:

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 prob-
lems 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.
B4040 Rev. A 247

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 consid-
erably.
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 Color Description

(default)
Normal Green No alarms or warning have been reported
from the NE.
Warning Yellow Indicates the detection of a potential or
impending service-affecting fault, before any
significant affects have been felt. Action
should be taken to further diagnose and
correct the problem in order to prevent it
from becoming a more serious service-
affecting fault.
Minor alarm DarkYellow Indicates the existence of a non-service-
affecting fault condition and that corrective
action should be taken in order to prevent a
more serious fault.
Major alarm Orange Signifies that a service-affecting condition
has occurred and urgent corrective action is
required.
Critical alarm Red The most severe alarm. It signifies that a
service-affecting condition has occurred and
an immediate corrective action is required.
No contact Blue Indicates that no contact is achieved with the
NE. The communication settings should be
checked in order to obtain contact with the
element.
Misconfigured Magenta The NE has not been properly configured.
248 B4040 Rev. A

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 VI-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 VI-1 Example of Explorer View
B4040 Rev. A 249

The Explorer view use the severity colors to indicate alarm events. The alarms
are presented in a hierarchical manner. The color 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 color 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 VI-2 shows an
example of the view.
The Map View shows the Network information in a physical manner. Each
NE is showed as an NE icon. Graphic-files can be added as background
images in the view. NE icons grouped together with bindings form networks.
The NE icons change their severity colors according to the current most
severe alarm of the NE.
Figure VI-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.
250 B4040 Rev. A

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 VI-3 shows an example of the Current Alarms List.
Each alarm is listed as a row in the list as shown in Table VI-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-mouse-
button-click context menu. The filter is then automatically set up to show
only the alarms hierarchically below the node/leaf the alarm list was opened
from.
Figure VI-3 Example of Current Alarms
Fields Description
Severity The severity of the alarm
Alarm text A short description of the alarm
Node The name of the node where the alarm occurred
Table VI-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.
B4040 Rev. A 251

4.0 Cable Fault

If a cable fault is indicated, it indicates that the microprocessor communica-
tions between the IDU and ODU have failed. The fault is most probably with
the cable connection. It may be open or shorted. Disconnect the cable from
the IDU and leave the ODU connected. Measure the DC cable resistance
between the center pin and the outer conductor of the N-type connector
terminating the cable by means of a multi-meter.
If resistance is in the order of some hundreds kW to a few MW:

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 kW:

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.
252 B4040 Rev. A

Appendices
SECTION VII
Appendices
B4040 Rev. A 253

254
SERVICE CHANNEL EXTENSION 1
Connector : RJ-45 8-PIN
Cable : 87W5097-1A
64kbit/s SERVICE CHANNEL (G.703) PHONE

Connector : RJ45 8-PIN LOCAL CRAFT TERMINAL (RS232)

Cable : UWMK3077 Kit : 4CZ5 Connector : D-SUB 9-PIN MALE
Figure VII-1 IDU

Cable : UWMK3123
Slot for optional Line
SAFETY Interface Plug-In Board
GROUND Ref. Fig. X-6
COLLECTIVE CALL
64kb/s SVCE Phone NI 1

G.703 Ext. 1
155 Mb/s LINE
CRITICAL
POWER
MAJOR
PWR MINOR
WARNING
-48VDC 64kb/s SVCE 10BaseT IDU - HSB INTFC NI 2
ODU Ext. 2 LAN CALL ALM & AUX LCT
V.11
ODU INTERFACE Hot Standby Interconnection NETWORK INTERFACE (RS485)

N-TYPE FEMALE Connector : 68-PIN VHDCI receptacle Connector : D-SUB 9-PIN FEMALE
Cable : 87W5066-1A Cable : UWMK3078 , UWMK3079
POWER
Connector : POWER D-SUB 2-PIN 10 BaseT Ethernet
Cable : UWMK5051 Off the shelf standard
ethernet cable ALARM & AUXILLARY FUNCTIONS
64kbit/s SERVICE CHANNEL (V.11) Connector : D-SUB 25-PIN FEMALE
Connector : RJ45 8-PIN Cable : UWMK3076
Cable : UWMK3077
Appendix I: IDU / HSB-IDU Interface Description

Cable : 87W5097-1A
B4040 Rev. A
B4040 Rev. A
Cable : 87W5097-1A
PHONE
64KBIT/S SERVICE CHANNEL (G.703)
Kit : 4CZ5
Connector : RJ45 8-PIN LOCAL CRAFT TERMINAL (RS232)
Cable : UWMK3077 Connector : D-SUB 9-PIN MALE
Slot for optional Line Cable : UWMK3123
Interface Plug-In Board
SAFETY Ref. Fig. X-6
Figure VII-2 HSB-IDU

GROUND
COLLECTIVE CALL
POWER 1 64kb/s SVCE Phone NI 1

G.703 Ext. 1
RXDIRA CRITICAL
POWER 2 RXDIRB MAJOR
PWR
1 MINOR
2 TXDIRA WARNING
-48VDC 64kb/s SVCE 10BaseT IDU - HSB INTFC NI 2 TXDIRB
Ext. 2 LAN CALL ALM & AUX LCT
V.11
Hot Standby Interconnection NETWORK INTERFACE (RS485)

Connector : 68-PIN VHDCI receptacle Connector : D-SUB 9-PIN FEMALE
Cable : 87W5066-1A Cable : UWMK3078, UWMK3079
POWER
Connector : POWER D-SUB 2-PIN 10 BaseT Ethernet
Cable : UWMK5051 Off the shelf standard
ethernet cable ALARM & AUXILLARY FUNCTIONS
64KBIT/S SERVICE CHANNEL (V.11) Connector : D-SUB 25-PIN
Connector : RJ45 8-PIN Cable (1+0): UWMK3076
Cable : UWMK3077
Cable : 87W5097-1A
Appendices
255
256
SERVICE CHANNEL EXTENSION 1 10Base-T/100Base-TX Ethernet
Not used for CityLink Fast Ethernet Off the shelf shielded twisted
pair ethernet cable

Connector : RJ45 8-PIN Not used for CityLink Fast Ethernet TRIBUTARY T1/E1 INTERFACE (2Mbit/s or 1.5Mbit/s)
Cable : UWMK3077 Connector : RJ45 8-PIN
Cable : 87W5097-2A, 10m patch cable

SAFETY Interface Plug-In Board
GROUND Ref. Fig. X-6
POWER 1 64kb/s
64kb/s 2Mb/s
2Mb/s SVCE
SVCE Phone
Phone 10Base-T/100Base-TX T1/E1 NI
NI
NI11
G.703
G.703Wayside
WaysideExt.
Ext.
1 1 SIGNAL SIGNAL
155
155 Mb/s
Mb/s LINE
LINE
RXDIRA CRITICAL
CRITICAL
CRITICAL
POWER
POWER
POWER2 G.703
G.703
PWR RXDIRB MAJOR
MAJOR
MAJOR
INP
INP OUT
OUT
Figure VII-3 EtherLink IDU V.1

PWR1
PWR MINOR
MINOR
MINOR
2 WARNING
WARNING
WARNING
TXDIRA
-48VDC
10BaseT IDU
IDU- HSB
- HSBINTFC
INTFC NI
NI
NI22 TXDIRB
ODU
ODU CALL
CALL ALM
ALM&&AUX
AUX LCT
LCT
LCT
V.11 Sync. Ext.
V.11 Sync. Ext.
2 2 LAN
LAN
ODU INTERFACE COLLECTIVE CALL

Not used for CityLink NETWORK INTERFACE (RS485)
N-TYPE FEMALE Fast Ethernet Not used for CityLink Fast Ethernet
POWER Hot Standby Interconnection

Connector : POWER D-SUB 2-PIN Not used for CityLink Fast Ethernet
Cable : UWMK5051 LOCAL CRAFT TERMINAL (RS232)
Connector : D-SUB 9-PIN MALE
10BaseT Ethernet
64kbit/s SERVICE CHANNEL (V.11) Cable : UWMK3123
Off the shelf standard
Connector : RJ45 8-PIN ethernet cable
Cable : UWMK3077
SERVICE CHANNEL EXTENSION 2 ALARM & AUXILLARY FUNCTIONS

Not used for CityLink Fast Ethernet Connector : D-SUB 25-PIN FEMALE
Cable : UWMK3076
B4040 Rev. A
B4040 Rev. A
Not used for EtherLink
1000Base-X Ethernet
Connector : SFP Plug-In Module, Optical
Cable : MMF or SMF, CAT5E
Connector : RJ45 8-PIN Not used for EtherLink 1000Base-T Ethernet
Cable : UWMK3077 Connector : RJ45
Cable :Off the shelf shielded twisted pair ethernet cable, CAT5E
SAFETY Interface Plug-In Board 10Base-T/100Base-TX Ethernet
GROUND Ref. Fig. X-6 Off the shelf shielded twisted
pair ethernet cable, CAT5
64kb/s 2Mb/s SVCE Phone 1000BASE-X/ 1000BASE-T 10BASE-T/100BASE-TX

NI 1
G.703 Wayside Ext. 1 1000BASE-T
155 Mb/s LINE
CRITICAL
POWER 1 2 3 4
MAJOR
Figure VII-4 EtherLink IDU V.2

PWR MINOR
WARNING
-48VDC 64kb/s 2MHz SVCE 10BaseT IDU - HSB INTFC NI 2
ODU Sync. Ext. 2 LAN CALL ALM & AUX LCT
V.11
ODU INTERFACE COLLECTIVE CALL

Not used for EtherLink NETWORK INTERFACE (RS485)
N-TYPE FEMALE Not used for EtherLink
POWER Hot Standby Interconnection

Connector : POWER D-SUB 2-PIN Not used for EtherLink
Cable : UWMK5051 LOCAL CRAFT TERMINAL (RS232)
Connector : D-SUB 9-PIN MALE
10BaseT Ethernet
64kbit/s SERVICE CHANNEL (V.11) Cable : UWMK3123
Off the shelf standard
Connector : RJ45 8-PIN ethernet cable
Cable : UWMK3077
SERVICE CHANNEL EXTENSION 2 ALARM & AUXILLARY FUNCTIONS

Not used for EtherLink Connector : D-SUB 25-PIN FEMALE
Cable : UWMK3076
Appendices
257
G.703
INP OUT
155 Mbit/s OC-3

G.703, 75W
Connector : DIN47297, 1.0/2.3mm
Cable : UWMH3080
CAT-5 UTP
INP
155 Mbit/s OC-3

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 VII-5 Optional Line Interface Plug-in Boards
SIGNAL DS1-0 DS3/E3-1 DS3/E3-2 DS3/E3-3
0
1
2
3
OUT IN OUT IN OUT IN
Figure VII-6 DS3 Extension Board
258 B4040 Rev. A

Appendices
Power Connector
0V STATION GROUND (FEMALE )
IN DOOR UNIT'S
FRONT VIEW
-48VDC (MALE )
Figure VII-7 IDU Power Connector Pinout
RJ-45 Connectors
With reference to Figure VII-8, 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 Figures VII-1 -4 for
location of 2-by-4 port RJ-45.
IN DOOR UNIT'S
FRONT VIEW
Pin no. 8 Pin no. 1
A B C D
Pin no. 8
Pin no. 1
Figure VII-8 RJ-45 (P5001A-D) connector detail.
B4040 Rev. A 259

64kbit/s G.703 Jack, RJ-45 Connector
Pin. no: Function:

1UA TxD- (Neg. Tx. data)
2UA TxD+ (Pos. Tx. data)
3UA TxC+ (Pos. Tx. clock)
4UA TxC- (Neg. Tx. clock)
5UA RxD+ (Pos. Rx. data)
6UA RxD- (Neg. Rx. data)
7UA RxC+ (Pos. Rx. clock)
8UA RxC- (Neg. Rx. clock)
Table VII-1 64kbit/s G.703 Jack, 8-PIN Pinout
64kbit/s V.11 Jack, RJ-45 Connector
Pin. no: Function:

1LA TxD- (Neg. Tx. data)
2LA TxD+ (Pos. Tx. data)
3LA TxC- (Neg. Tx. clock)
4LA TxC+ (Pos. Tx. clock)
5LA RxD- (Neg. Rx. data)
6LA RxD+ (Pos. Rx. data)
7LA RxC- (Neg. Rx. clock)
8LA RxC+ (Pos. Rx. clock)
Table VII-2 64kbit/s V.11 Jack, 8-PIN Pinout
1.5Mbit/s Wayside Jack, RJ-45 Connector
Pin. no: Function:

1UB IND+ (Pos. Rx. data)
2UB IND- (Neg. Rx. data)
3UB shield
4UB OUTD+ (Pos. Tx. data)
5UB OUTD- (Neg. Tx data)
6UB shield
7UB Not Connected
8UB Not Connected
Table VII-3 1.5Mbit/s Wayside Jack, 8-PIN Pinout
260 B4040 Rev. A

Appendices
Service Channel Extension 1 and 2 Jacks, RJ-45 Connector
Pin. no: Function:

1UC OE1_INP_A
2UC OE1_INP_B
3UC OE1_OUT_A
4UC OE1_OUT_B
5UC CALL_INP
6UC CALL_OUT
7UC CTRL_INP
8UC CTRL_OUT
Table VII-4 Service Channel Extension 1 Jack, 8-PIN Pinout
Pin. no: Function:

1LC OE2_INP_A
2LC OE2_INP_B
3LC OE2_OUT_A
4LC OE2_OUT_B
5LC CALL_INP
6LC CALL_OUT
7LC CTRL_INP
8LC CTRL_OUT
Table VII-5 Service Channel Extension 2 Jack, 8-PIN Pinout
Service Phone Jack, RJ-45 Connector
Pin. no: Function:

1UD Not Connected
2UD Not Connected
3UD TELA
4UD MIC+
5UD MIC-
6UD TELB
7UD Not Connected
8UD LOOP_OE
Table VII-6 Service Phone Handset Connector, 8-PIN Pinout
B4040 Rev. A 261

10Base-T (TP-LAN) Jack, RJ-45 Connector (normal)
Pin. no: Function:

1LD TPTX+ (Pos. Tx. data)
2LD TPTX- (NEG. Tx. data)
3LD TPRX+ (Pos. Rx. data)
4LD Not Connected
5LD Not Connected
6LD TPRX- (Neg. Rx. data)
7LD Not Connected
8LD Not Connected
Table VII-7 10Base-T, 8-PIN Pinout
10Base-T / 100Base-TX Jack, RJ-45 Connector (uplink)

(Used only in Fast Ethernet configuration)
Pin. no: Function:

1LD TPRX+ (Pos. Rx. data)
2LD TPRX- (NEG. Rx. data)
3LD TPTX+ (Pos. Tx. data)
4LD Not Connected
5LD Not Connected
6LD TPTX- (Neg. Tx. data)
7LD Not Connected
8LD Not Connected
Table VII-8 10Base-T / 100Base-TX, 8-PIN Pinout
1000Base-T Jack, RJ-45 Connector

Pin. no: Function:
1 MX1+
2 MX1-
3 MX2+
4 MX2-
5 MX3+
6 MX3-
7 MX4+
8 MX4-
Table VII-9 1000Base-T , 8-PIN Pinout (pinout numbering similar to a
connector from Figur VII-7, U
262 B4040 Rev. A
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
PIN
Pos.35
35
Figure VII-9 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 VII-10 NI1 and NI2 D-SUB 9 PIN Pinout
NI1 and NI2 D-SUB Signal Name Signal Description

9-PIN FEMALE
1 RxD- Data Input
2 RxD+ Data Input
3 GND Signal Ground.
Normally this pin shall
not be connected.
4 TxD+ Data Output
5 TxD- Data Output
6 RxC- Clock Input
7 RxC+ Clock Input
8 TxC+ Clock Output
9 TxC- Clock Output
Table VII-10 NI1 and NI2 D-SUB 9-PIN Pinout
B4040 Rev. A 263

ALM & AUX Connector Detail
PIN 13 PIN 1
IDU
FRONT
VIEW
PIN 25 PIN 14
Figure VII-11 ALM & AUX D-SUB 25-PIN Pinout
ALM & AUX D-SUB Signal Name Signal Description

25-PIN FEMALE
1 USER1A Relay output 1A
2 USER1B Relay output 1B
9 ALM1 Alarm input 1 (TTL level)
10 AGND Analog GND*
13 AGND Analog GND*
14 AGND Analog GND*
16 AGND Analog GND*
17 ALM5 Alarm input 5 (relay input)
18 AGND Analog GND*
22 ERRP_V11+ Error pulses (V.11 output)**
23 ERRP_V11- Error pulses (V.11 output)**
24 ERRP_OPEN_COL B1 error pulses
open collector output
25 ERRP_OPTO B1 error pulses opto
coupler driver output
Table VII-11 ALM & AUX D-SUB 15-PIN Female Pinout
* Analog GND is floating relative scussi GND.
** Selectable from NEW-NMS: B1, B2 or Trellis decoder.
See Section IV Ch.4.5.4.
264 B4040 Rev. A
Appendices
LCT Connector Detail
PIN 1 PIN 5
IDU
FRONT
VIEW
PIN 6 PIN 9
Figure VII-12 LCT D-SUB 9 PIN male, Pinout
LCT D-SUB Signal Name Signal Description

9-PIN MALE
1 NC Not Connected
2 RxD City Link Data Input
3 TxD City Link Data Output
4 - Internally connected to pin 6
5 GND Signal ground
9 NC Not connected
Table VII-12 LCT D-SUB 9-PIN Pinout
B4040 Rev. A 265

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

❒ PDR220 waveguide for 18GHz and 23GHz.
❒ PDR84 waveguide for 7GHz and 8GHz.
❒ PDR70 waveguide for L6GHz and U6GHz.
❒ Grounding cable for Branching Unit.
266 B4040 Rev. A

Appendices
Appendix III:Alarm List & Alarm Description

Alarm Name Description Id Severity
BASEBAND
LOS Loss Of Signal: 1000 MAJOR
- Optical or electrical CMI
LOF Loss of Frame 1001 MAJOR
MS-AIS Alarm indication signal detected. 1002 WARNING
MS termination only
MS-AIS-INS Alarm indication signal is inserted. 1003 MAJOR
MS-RDI Remote defect indicator detected. 1004 WARNING
MS termination only
2M-WAYSIDE-INP 2Mbit wayside input is missing. 1005 MINOR
2M-WAYSIDE-AIS-INP 2Mbit wayside input AIS detected. 1006 WARNING
TRELLIS-PLL Indicates that the Trellis coder is out of lock.(CNF35C 1007 CRITICAL
Asic)
RT-PLL The Sorp 38,88 MHz PLL is out of lock. 1008 CRITICAL
2M-SYNC Selected synchronisation for Line Transmit direction is 1009 MINOR
missing.
RS-TRACE-MISMATCH Mismatch between configured string and received string 1010 MAJOR
LOC Loss of clock (SORP) 1011 CRITICAL
BASEBAND
DIRECTION RADIO TO LINE
LT-PLL The Line Transmit 155MHz PLL is out of lock. 1100 CRITICAL
2M-WAYSIDE-OUTP-AIS AIS is detected on the Wayside traffic output. 1101 WARNING
HBER Indicator for BER > 1e-3 1102 MAJOR
LBER Indicator for BER > 1e-6 1103 MINOR
EW-BER Indicator for BER > 1e-10 1104 WARNING
RF-ID Wrong RF-ID received compared to configuration. 1105 MAJOR
MODULATOR
IF-MOD Loss of IF 350MHz 1200 CRITICAL
DEMODULATOR
IF-DEM Loss of INCOMING 140MHz. 1300 CRITICAL
OPTICAL INTERFACE
TX-OUT The output power has increased 2dB, or the analoge 1400 CRITICAL
measurement of PO_MON is outside predefined limits
LASER-OFF The laser is off. It could be manual shutdown 1401 WARNING
BIAS The laser bias is out of limits. Sign of age and degradation 1402 WARNING
TRANSCEIVER
IF-INP No IF into transceiver 1500 CRITICAL
RF-OUT The output power is low 1501 MAJOR
LOS-RF-INPUT No signal into receiver. 1502 MAJOR
RF-INPUT-WARNING The RF level is either above the upward fading threshold 1504 WARNING
or The RF level is below the down fading threshold.
LO Local Oscillator is out of lock. 1505 MAJOR
UNIT-ALM The transceiver is not responding 1506 MAJOR
ATPC The regulation loop for the ATPC is not working. Software 1507 MINOR
generated alarm based on alarm condition on local LOF
on Rx and remote LOF on Rx .
RF-MUTE The RF transmitter is muted. 1508 WARNING
LOOPING-IF-EN The transceiver looping on IF is enabled 1509 WARNING
LOOPING-RF-EN The transceiver on RF is enabled. 1510 WARNING
(If near-end and far end depends on the node where
alarm is reported)
MISSING_LO_SYNCHRONIZATION XPIC LO synch missing 1511 CRITICAL
LO-TUNING-WARNING The LO needs to be tuned 1512 WARNING
HIGH_TEMP_POWER_TRANSISTOR 1513 WARNING
RF_RX_LOW 1514 MAJOR
RF_RX_HIGH 1515 MAJOR
NO_CALIBRATION_DATA No calibration data 1516 MAJOR
HSB_CABLE_BREAK The cable between the ODU’s are broken. This will cause 1517 MAJOR
the switch to perform the TX-switching.
RF_TX_LOW 1518 MAJOR
RF_TX_HIGH 1519 MAJOR
IF_TX_LOW 1520 MAJOR
IF_TX_HIGH 1521 MAJOR
POWER_15 1522 WARNING
POWER_NEG15 1523 WARNING
B4040 Rev. A 267

SYNTH_HEADER 1526 MAJOR
SHF_LO 1527 MAJOR
UHF_TX_LO 1528 MAJOR
UHF_RX_LO 1529 MAJOR
DUPLEX_LO 1530 MAJOR
VHF_LO 1531 MAJOR
TX_SWITCH_MAN 1532 WARNING
OTHER ALM
MEN-AT-WORK Software generated. Operator set men at work before 2000 WARNING
doing repairs.
DROP-IN+48V The battery supply voltage is dropped below acceptable 2001 WARNING
limit
BELOW+3.3V Voltage from the DC-DC converter below limit 2002 WARNING
BELOW+5V Voltage from the DC-DC converter below limit 2003 WARNING
BELOW-5V Voltage from the DC-DC converter below limit 2005 WARNING
OVER-CURRENT Detects short current on ODU cable. 2006 MAJOR
WAYSIDE-LOOP FE Wayside looping Far End 2007 WARNING
WAYSIDE-LOOP NE Wayside looping Near End 2008 WARNING
PRBS-INSERTED PRBS inserted in wayside 2009 WARNING
LOOPING_EN Looping enabled 2010 WARNING
EVENT-LOG-EXC-LIMIT Event log has exceeded the capacity threshold 2011 WARNING
DOWNLOAD-IN-PROGRESS Download of software is under progress. 2012 WARNING
NEED_FREQUENCY A RF unit need to be configured with Tx and Rx 2013 MAJOR
frequency.
SECURITY-LOG-EXC-LIMIT Security log has exceeded the capacity threshold 2014 WARNING
64K-LOOPING-1 64 kb channel looping Channel1 2015 WARNING
64K-LOOPING-2 64 kb channel looping Channel2 2016 WARNING
RTC-LOW BATTERY The battery that powers the Real Time clock is low 2017 WARNING/
MINOR on
NL2000
BELOW-15V Voltage from the DC-DC converter below limit 2024 WARNING
MISSING-CALIBRATION-DATA Modem or transceiver are missing their calibration data in 2032 MAJOR
flash
FAN-ALARM 2034 WARNING

DEFAULT_SYSTEM_PARAMETERS No system configuration stored in NV config, using default 2035 CRITICAL
(stm1,128TCM,28kHz)
DEFAULT_ANALOGE_PARAMETERS No analoge configuration stored in flash, using predefined 2036 MAJOR
defaults.
FAN2-ALARM 2037 WARNING
HSB-RELAY IDUswitch/Transceiver relay mismatch 2200 CRITICAL
IDUA-ACTIVE Idu A is active in receiving direction 2201 INFO
IDUB-ACTIVE Idu B is active in receiving direction 2202 INFO
HSB-MANUAL The iduswitch is operated manually 2203 WARNING
CHANNEL-ACTIVE This ODU is active 2216 INFO
NEED-SW Board needs SW 2221 MAJOR
BOOT-MONITOR-IN-USE The transceiver is in boot monitor mode 2224 WARNING
BOOT-HW-ERROR-DETECTED Errors detected by boot code when startup. Reported to 2225 MINOR
app. code
IDU_A_NEEDS_SW Reported from the IDU A 2226 WARNING
IDU_B_NEEDS_SW Reported from IDU B 2227 WARNING
HDLC_LOC_A The IDU switch has no RX-clock on port A 2228 MAJOR
HDLC_LOC_B The IDU switch has no RX-clock on port B 2229 MAJOR
HDLC_LOC The IDU(either A or B) has no RX-clock 2230 MAJOR
DROP-IN-48V-A The IDU switch power source 1 has a drop 2231 MAJOR
DROP-IN-48V-B The IDU switch power source 2 has a drop 2232 MAJOR
AUXILIARY ALARMS
EXTERN-ALARM-1 Multipurpose port. Configured as 2500 WARNING
Alarm Output, Alarm Input or Remote Control.
External alarm reported if port configured as alarm input.
Alarm name configurable from management system.
EXTERN-ALARM-2 ref External alarm 1 2501 WARNING
268 B4040 Rev. A

Appendices
OUTPUT-ALARM-1 Output alarm reported if auxilary output port configured as 2550 INFO
alarm output.
OUTPUT-ALARM-2 ref Output alarm 1 2551 INFO
SEVERITY ALARMS For alarm output function

CRITICAL-ALARM If any alarms with severity set to critical, this alarm is 2600 NA
raised. This can be combined in the alarm output
expression.
MAJOR-ALARM If any alarms with severity set to major, this alarm is 2601 NA
expression.
MINOR-ALARM If any alarms with severity set to minor, this alarm is 2602 NA
expression.
WARNING-ALARM If any alarms with severity set to warning, this alarm is 2603 NA
expression.
PERFORMANCE ALARMS All software generated
G826-THRESHOLD-15MIN-B1 If the current 15 minute period exceeds the set threshold 3000 WARNING
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).
G826-THRESHOLD-15MIN-B2 If the current 15 minute period exceeds the set threshold 3001 WARNING
for B2, this alarm is set. Ref. G826-THRESHOLD-15MIN-
B1 for method of clearing. Only for MS termination.
G826-THRESHOLD-15MIN-REI If the current 15 minute period exceeds the set threshold 3002 WARNING
for REI, this alarm is set. Ref. G826-THRESHOLD-
15MIN-B1 for method of clearing. Only for MS termination.
G826-THRESHOLD-24Hour-B1 If the current 24 hour period exceeds the set threshold for 3003 WARNING
B1, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1
for method of clearing.
G826-THRESHOLD-24HOUR-B2 If the current 24 hour period exceeds the set threshold for 3004 WARNING
B2, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1
for method of clearing. Only for MS termination.
G826-THRESHOLD-24HOUR-REI If the current 24 hour period exceeds the set threshold for 3005 WARNING
REI, this alarm is set. Ref. G826-THRESHOLD-15MIN-
G826-THRESHOLD-MONTH-B1 If the current month period exceeds the set threshold for 3006 WARNING
month, this alarm is set. Ref. G826-THRESHOLD-15MIN-
B1 for method of clearing.
G826-THRESHOLD-MONTH_B2 If the current month period exceeds the set threshold for 3007 WARNING
G826-THRESHOLD-MONTH-REI If the current month period exceeds the set threshold for 3008 WARNING
REI, this alarm is set. Ref. G826-THRESHOLD-15MIN-B1
for method of clearing. Only for MS termination.
TRESHOLD-15MIN-OOF If the current 15 minute period exceeds the set threshold 3015 WARNING
for OOF, this alarm is set. Ref. G826-THRESHOLD-
15MIN-B1 for method of clearing.
TRESHOLD-24HOUR-OOF If the current 24 hour period exceeds the set threshold for 3016 WARNING
OOF, this alarm is set. Ref. G826-THRESHOLD-15MIN-
TRESHOLD-MONTH-OOF If the current month period exceeds the set threshold for 3017 WARNING
B4040 Rev. A 269

Fast Ethernet Alarms
FTP_USER_LOGGED_IN FTP user logged in 32768 NORMAL
ILLEGAL_DATE_OR_TIME Illegal Date or Time 32770 WARNING
IDU_TEMPERATURE1_HIGH SU Temperature 1 (CPU) exceeded high 32771
limitWARNING
IDU_TEMPERATURE2_HIGH SU Temperature 2 (DC/DC) exceeded high limit 32772 WARNING
FAN1_MANUAL_STOP SU Fan 1 is set in manual stop 32773 WARNING
FAN2_MANUAL_STOP SU Fan 2 is set in manual stop 32774 WARNING
FAN1_NOT_RUNNING SU Fan 1 is not running 32775 MAJOR
FAN2_NOT_RUNNING SU Fan 2 is not running 32776 MAJOR
I2C_BUS_FAILURE SU internal problem at I2C bus 32777 WARNING
BASEBAND_DEVICE_INIT_FAILURE There was a hardware error in the baseband module 32778 MAJOR
during startup of the IDU
MODEM_DEVICE_INIT_FAILURE There was a hardware error in the modem module 32779 MAJOR
during startup of the IDU
EEB_DEVICE_INIT_FAILURE There was a hardware error in the ethernet extension 32780 MAJOR
board module during startup of the IDU
COMMAND_LINE_INIT_FAILURE There was a hardware error in the command line 32781 WARNING
interface module during startup of the IDU
CONSOLE_USER_LOGGED_IN A user is currently using the command-line interface 32782 NORMAL
shell on the IDU via the LCT port
TELNET_USER_LOGGED_IN A user is currently using the command-line interface 32783 NORMAL
shell on the IDU via the telnet
ETHERNET_PORT_1 EEB Port 1 link lost. 32784 NORMAL
LOS_2MBIT_PORT_1 EEB LOS port 1. 32788 NORMAL
AIS_INPUT_2MBIT_PORT_1 EEB AIS input port 1. 32792 WARNING
AIS_OUTPUT_2MBIT_PORT_1 EEB AIS output port 1. 32796 WARNING
AIS_INSERT_2MBIT_PORT_1_RX EEB AIS insert port 1 input. 32800 WARNING
LOC_RT Loss of clock in the RT module of the baseband unit 32804 CRITICAL
(SORP)
LOC_RR Loss of clock in the RR module of the baseband unit 32805 CRITICAL
(SORP)
LOC_LT Loss of clock in the LT module of the baseband unit 32806 CRITICAL
(SORP)
LOC_LR Loss of clock in the LR module of the baseband unit 32807 CRITICAL
(SORP)
LOS_RR Loss of signal on radio receive (RR) 32808 MAJOR
LOF_RR Loss of frame on radio receive (RR) 32809 MAJOR
MS-AIS_RR Alarm indication signal detected on radio receive (RR) 32810 WARNING
MS-AIS_INSERT_RR Alarm indication signal is inserted on radio receive (RR) 32811 MAJOR
MS-RDI_RR Remote defect indicator detected on radio receive (RR) 32812 WARNING
LOS_LR Loss of signal on line receive (LR): - optical or electrical 32813 MAJOR
CMI.
LOF_LR Loss of frame on line receive (LR) 32814 MAJOR
MS-AIS_LR Alarm indication signal detected on line receive (LR) 32815 WARNING
MS-AIS_INSERT_LR Alarm indication signal is inserted on line receive (LR) 32816 WARNING
MS-RDI_LR Remote defect indicator detected on line receive (LR) 32817 WARNING
MS-AIS_INSERT_RT Alarm indication signal is inserted on radio transmit 32818 MAJOR
(RT)
MS-AIS_INSERT_LT Alarm indication signal is inserted on line transmit (LT) 32819 MAJOR
RS-TRACE-MISMATCH_RR Mismatch between configured string and received string 32820 MAJOR
(RR)
RS-TRACE-MISMATCH_LR Mismatch between configured string and received string 32821 MAJOR
(LR)
LOOP_MAIN Main traffic looping is active 32822 WARNING
LOOP_WAYSIDE Wayside channel looping is active 32823 WARNING
LOOP_64K 64 kb/s channel looping is active 32824 WARNING
SW_UPDATE_IN_PROGRESS A software update is in progress 32825 WARNING
FREQUENCY_SHIFT A frequency shift is in progress 32826 WARNING
270 B4040 Rev. A

Appendices
BELOW_11V_ODU Voltage from the DC-DC converter below limit 32827 WARNING
BELOW_3.3V_ODU Voltage from the DC-DC converter below limit 32828 WARNING
BELOW_48V_ODU Voltage from the DC-DC converter below limit 32829
BELOW_-15V_ODU Voltage from the DC-DC converter below limit 32830 WARNING
FAN_ODU 32833 WARNING
FAN2_ODU 32834 WARNING
RX-LO 32835 MAJOR
TX-LO 32836 MAJOR
RX-LO-TUNING-WARNING 32837 WARNING
TX-LO-TUNING-WARNING 32838 WARNING
NEED-RX-DRO-TUNING 32839 WARNING
NEED-TX-DRO-TUNING 32840 WARNING
TRIBUTARY ALARMS
AIS-1 Alarm Indication Signal detected in VC-12 #1. 4200 WARNING
AIS-2 Ref: AIS-1 4201 WARNING

AIS-84 Ref: AIS-1 4283 WARNING
SIGNAL-LABEL-MISMATCH-1 Signal Label Mismatch detected on VC-12 #1. Is set 4284
when the signal label in the LO-POH is set to un-
equipped.
SIGNAL-LABEL-MISMATCH-2 Ref: SIGNAL-LABEL-MISMATCH-1 4285 WARNING

SIGNAL-LABEL-MISMATCH-84 Ref: SIGNAL-LABEL-MISMATCH-1 4367 WARNING
LOS-1 Loss Of Signal in VC-12 #1. 4368 MAJOR
LOS-2 Ref: LOS-1 4369 MAJOR

LOS-84 Ref: LOS-1 4451 MAJOR
LP-RDI-1 Low order Path Remote Defect Indication in VC-12 #1. 4452 WARNING
LP-RDI-2 Ref: LP-RDI-1 4453 WARNING

LP-RDI-84 Ref: LP-RDI-1 4535 WARNING
LP-RFI-1 Low order Path Remote Failure Indication in VC-12 #1. 4536 WARNING
LP-RFI-2 Ref: LP-RFI-1 4537 WARNING

LP-RFI-84 Ref: LP-RFI-1 4619 WARNING
B4040 Rev. A 271

CityLink & EtherLink ANSI Manual

Uploaded by

Copyright:

Available Formats

CityLink & EtherLink ANSI Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CityLink & EtherLink ANSI Manual

Uploaded by

Copyright:

Available Formats

CityLink &

Section III : System Startup

Section V : EtherLink V.1 Configuration

Section VII : Appendices

Rev. Date What is changed

A 30-06-05 Initial Version Based B4008 - Rev.M

In Radio-Relay communication installations,

level, within limited portions of space.

This page is intentionally left blank.

SECTION I Equipment Description ................. 15

1.0 Introduction ................................................................. 16

SECTION II Installation .................................... 19

1.0 Installation Flowchart ................................................. 20

2.0 General ........................................................................ 21

3.0 Installation Equipment required ................................ 23

4.0 6-11GHz ODU Installation .......................................... 25

6.0 IDU Installation ............................................................ 41

7.0 IDU/ODU Cable Installation........................................ 49

8.0 All Indoor Installation .................................................. 51

SECTION III Installation of Nera Antenna and

SECTION III System Startup ........................... 59

1.0 General Overview ...................................................... 60

2.0 Power On ..................................................................... 61

SECTION IV Configuration ............................. 65

1.0 General ........................................................................ 66

2.0 Element Node .............................................................. 68

3.0 Transmission Node ..................................................... 77

5.0 Hot Standby ................................................................. 168

SECTION V EtherLink V.1 Configuration ........ 177

Hyperterminal & Telnet .......................... 178

1.0 Hyperterminal & Telnet Commands .......................... 178

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

3.0 Top Level Commands ................................................ 180

4.0 Submenu Commands .................................................. 182

5.0 Software Upgrade Procedure for

NEW Network Management System ..... 195

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

7.0 Network Element Configuration ................................ 198

8.0 Element Node .............................................................. 200

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

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

12.0 Fault .............................................................................. 233

13.0 Security ........................................................................ 234

SNMP & MIB Description ....................... 235

14.0 General ........................................................................ 235

15.0 Supported MIBs ......................................................... 235

16.0 MIB Overview ............................................................. 236

SECTION VI Troubleshooting........................ 245

1.0 General ........................................................................ 246

2.0 Description of Alarm LEDs ......................................... 246

4.0 Cable Fault ................................................................... 252

SECTION VII Appendices .............................. 253

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

Appendix II: ODU Interface Description ................................ 266

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

This page is intentionally left blank.

When equipped with Ethernet traffic interfaces, the equipment is called

Built-in Supervisory allows easy installation, system status and configura-

This page is intentionally left blank.

1.0 Installation Flowchart

15.0 Supported MIBs ......................................................... 235

Hook the top Transceiver hinges

Secure the Transceiver

Figure II-6 RF-Interface All Indoor, 1+0

Figure II-8 RF-Interface All Indoor, Double Terminal [2x (1+0)]