You are on page 1of 116

Commissioning and Maintenance

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

1 (116)

Commissioning and Maintenance

The information in this documentation is subject to change without notice and describes only
the product defined in the introduction of this documentation. This documentation is intended
for the use of Nokia's customers only for the purposes of the agreement under which the
documentation is submitted, and no part of it may be reproduced or transmitted in any form or
means without the prior written permission of Nokia. The documentation has been prepared to
be used by professional and properly trained personnel, and the customer assumes full
responsibility when using it. Nokia welcomes customer comments as part of the process of
continuous development and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products cannot be considered binding
but shall be defined in the agreement made between Nokia and the customer. However, Nokia
has made all reasonable efforts to ensure that the instructions contained in the documentation
are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues
which may not be covered by the documentation.
Nokia's liability for any errors in the documentation is limited to the documentary correction of
errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL
(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or
the information in it.
This documentation and the product it describes are considered protected by copyright
according to the applicable laws.
NOKIA logo is a registered trademark of Nokia Corporation.
Other product names mentioned in this documentation may be trademarks of their respective
companies, and they are mentioned for identification purposes only.
Copyright Nokia Corporation 2002. All rights reserved.

2 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Contents
Contents 3
Summary of changes 7
1

About this document 9

2
2.1
2.2
2.3
2.4
2.4.1
2.4.2
2.4.3
2.5
2.6
2.7
2.8
2.9

Nokia MetroHub Manager 11


Connecting the communication cable 11
Starting Nokia MetroHub Manager 12
Using Help 13
Accessing the MetroHub node online 14
Direct connection via LMP 14
Address connection via Q1 16
Sobriquet connection 17
Accessing the MetroHub node offline file 18
Saving node information in a file 19
Accessing the MetroHub node remotely via NMS 20
Printing 20
Menu overview 20

3
3.1
3.1.1
3.1.2
3.1.2.1
3.1.2.2
3.1.3
3.2
3.3
3.4
3.5
3.5.1
3.5.2
3.5.3

Commissioning Nokia MetroHub 23


Preparing for the commissioning 23
Settings to be added to the site configuration file before commissioning
Nokia MetroHub 24
Obligatory radio settings 26
Nokia FlexiHopper settings 26
Nokia MetroHopper radio settings 27
Node offline file 30
Commissioning process 31
Switching the power on 33
Testing with the commissioning wizard 34
Configuring with the commissioning wizard 36
Configuring the site 37
Check and fine tune hops 39
Commissioning report 41

4
4.1
4.1.1
4.1.2
4.1.2.1
4.1.2.2
4.1.2.3
4.1.2.4
4.1.2.5
4.1.3
4.1.4
4.2

Managing Nokia MetroHub 43


Creating cross-connections with the Manager 43
Cross-connections window 45
Managing cross-connections 46
Cross-connection properties dialog 46
Adding bypass connections 48
Adding cross-connections 48
Modifying a cross-connection 52
Removing a cross-connection 53
Editing cross-connection banks 53
Usability hints for cross-connections 53
Adjusting node settings 54

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

3 (116)

Commissioning and Maintenance

4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.3
4.3.1
4.3.2
4.4

Identifications 54
Service interface 54
Synchronisation 55
Q1 management 57
Programmable alarms 63
Alarm properties 63
Configuration related settings 63
Nokia FlexiHopper and MetroHopper settings (with FXC RRI) 63
FXC E1 and FXC E1/T1 transmission unit settings 64
Check list for mandatory settings 64

5
5.1
5.2
5.3
5.3.1
5.3.2
5.3.3
5.3.4
5.3.5
5.4
5.5
5.6
5.7
5.8
5.9

Maintaining Nokia MetroHub 65


Maintenance procedure 65
Removing the MetroHub cover 65
Preventive maintenance 66
Cleaning 66
Battery 67
Fan 68
Transmission units 68
Lock 68
Testing 69
Temperature monitoring 69
Resetting units 69
Restoring backup settings from a file 71
Copying software banks 72
Configuration report 72

Troubleshooting instructions 75

7
7.1
7.2

Managing alarms 81
Reading and cancelling alarms 81
Service LEDs 85

8
8.1
8.1.1
8.2
8.2.1
8.2.2
8.3
8.4
8.4.1
8.4.2
8.5
8.6

Upgrading 87
Software upgrading 87
Upgrading software 88
Installing/uninstalling the units logically with the Manager 89
Installing a new unit logically with the Manager 89
Uninstalling a unit logically with the Manager 90
Removing units 90
Replacing units 92
Replacing a unit with a unit of the same type 92
Replacing a unit with a unit of a different type 94
Adding units 95
Changing a battery backup unit 95

Appendix A. 97
A.1
Alarm descriptions 97
A.1.1
MetroHub node alarms 97
A.1.2
FXC RRI unit alarms 106
A.1.3
FXC E1/T1 unit alarms 112

4 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

A.1.4

DN99610738
Issue 5-0 en Draft

Radio unit alarms 115

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

5 (116)

Commissioning and Maintenance

6 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Summary of changes

Document

Date

C33525007SE_00

05 Nov 1999

DN99610738 Issue 1-0 en

28 Dec 1999

New document numbering scheme adopted.

DN99610738 Issue 2-0 en

30 May 2000

Updated

DN99610738 Issue 3-0 en

30 Nov 2000

Minor corrections; Chapter 6 added

DN99610738 Issue 4-0 en

09 May 2001

Updated. New: Node offline file. Removed: Site


Configuration File (SCF)

DN99610738 Issue 5-0 en

31 May 2002

Updated

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Comment

Internal Copy

7 (116)

Commissioning and Maintenance

8 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

About this document

About this document


This document describes the commissioning and maintenance of Nokia
MetroHub Transmission Node. The commissioning and maintenance actions are
mainly carried out using the Nokia MetroHub Manager software.
The document contains the following information:

introduction to the node manager software

commissioning the transmission node with the commissioning wizard

managing the node

maintaining the node

managing alarms

upgrading the node.

Refer to the installation documents found in this user manual for instructions on
installing Nokia MetroHub.
For information on release-specific details, for example, compatibilities, special
work instructions, and the list of known bugs and limitations, see the Nokia ITN
C2.0 Integrated Transmission Node release documentation.
Please familiarise yourself with Microsoft Windows before operating Nokia
MetroHub Manager.

Note
Screenshots included are representations only. The actual node manager program
may vary slightly from the shots depicted.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

9 (116)

Commissioning and Maintenance

10 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Nokia MetroHub Manager

Nokia MetroHub Manager


Nokia MetroHub Manager is a PC-based software application used for
controlling and monitoring Nokia MetroHub Transmission Node. This chapter
gives instructions on how to get started with the Manager. It is assumed here that
the user knows how to use the Microsoft Windows 95 or 98 or NT4.0 software.
Nokia MetroHub Manager is delivered on the Nokia SiteWizard CD-ROM. For
instructions on how to install the Manager, see the cover of the CD-ROM.

Note
We recommend that all other Windows applications are closed when you start to
install the Manager. The setup program on the CD-ROM executes
autoinstallation.
After installation the Manager is ready for use (the computer may require
rebooting first).

2.1

Connecting the communication cable


To manage the node locally with MetroHub Manager, the computer must be
connected to the local management port (LMP) of MetroHub on the interface unit
(DIUx) using a communication cable. This LMP cable is a separate sales item
(see the list in Document Note).
Connect the BQ connector of the cable to the LMP port of MetroHub and the
serial connector to the COM port of the PC.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

11 (116)

Commissioning and Maintenance

Communication cable

BQ connector

PC + Nokia MetroHub
Manager software

D9
connector

BQ (male) on the cable

D9 (female) on the cable


5 4

3
1

4
2

= Socket
= Pin

3
1

LMP out
LMP in

4
2

GND
+5 V

Figure 1.

2.2

1
2
3
4
5
6
7
8
9

nc
RD
TD
nc
GND
nc
nc
nc
nc

GND
RD
TD
nc

3 2 1

7 6

= Ground
= Received data
= Transmitted data
= Not connected

Connecting the communication cable and connector pinouts

Starting Nokia MetroHub Manager


This section assumes that Nokia MetroHub Manager has been installed in your
computer.

12 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Nokia MetroHub Manager

To start Nokia MetroHub Manager:


1.

Start Windows.

2.

Click Start, and then point to Programs Nokia Applications

3.

Click the Nokia MetroHub Manager.

When MetroHub Manager is started, an application window appears. Via the


application window you can reach all the other windows in the Manager. No other
windows are initially open.
The MetroHub Manager application window has a toolbar to provide short-cuts
to the frequently needed menu commands. The window also has a status bar
which displays help information on the currently selected menu command.

2.3

Using Help
Nokia MetroHub Manager contains a comprehensive context-sensitive online
Help system which provides you with Help information about how to use all
aspects of the Manager. Help information is available at any time when you are
using the Manager.
To access the Help system, use one of the following methods:

Give the menu command Help Help Topics. Then choose a topic from
the Contents or the Index.

Press the F1 button or the Help button in case of a dialog box. The Manager
shows the context-sensitive Help of the current dialog box or window.

Note
The context-sensitive Help describes only the purpose and the layout of the dialog
or window in question. If you want to find more information about the MetroHub
Manager functions, it can be viewed by pressing the Contents button and then
double-clicking the topic.
The FXC unit related online help is available from HelpTransmission Unit
Managers. The Help covers all the FXC units.
For further information on using online Help, refer to the Microsoft Windows
user manuals.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

13 (116)

Commissioning and Maintenance

2.4

Accessing the MetroHub node online


MetroHub Manager offers two ways to work: online and offline. In the online
mode you can manage an actual node and all changes are made directly to the
node. The offline mode allows you to manage a virtual node. However, note that
you cannot fully manage the node in the offline mode, for example, not all
settings can be done.
Having started MetroHub Manager, select the node that you want to manage by
establishing a connection to the FXC unit acting as the node control unit. This
may be done in three alternative ways:

2.4.1

Direct connection via LMP

To access the MetroHub node using a direct connection:


1.

Select Connection Connect Locally

2.

The Manager connects to the node control unit (any FXC unit in slot 1)
using the fixed LMP address 4080 (default port settings: COM1, speed:
9600; these settings can be changed in the Manager Options dialog box).

Note
Connection Connect Locally menu command can only be used if the local
management port is used.
When the connection to the node has been established, the Equipment window
is automatically opened, see Figure 2. The window contains a picture of the node.
You can select a unit from the picture by clicking it. If an FXC unit or an outdoor
unit is selected, a unit-specific menu will appear before the MetroHub Manager
Tools menu on the menu bar. Outdoor units are managed through FXC RRI units.

Note
Closing the Equipment window causes the connection to the node or file to be
lost.

14 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Nokia MetroHub Manager

Figure 2.

MetroHub Manager Equipment window (Connected to node)

The status of the units is indicated by means of colour coding.

Table 1.

DN99610738
Issue 5-0 en Draft

Colour codes indicating the status of units

Colour code

Status of unit

Dark grey

Empty slot

Diagonal stripes

Physically inserted, logically uninstalled

Light grey

Physically inserted, logically installed


(=operational unit)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

15 (116)

Commissioning and Maintenance

Table 1.

Colour codes indicating the status of units (Continued)

Colour code

Status of unit

Dark grey with a light grey border; type of


unit indicated

Physically removed, logically installed


(=missing unit)

Light grey with a red border; type of unit


indicated

Physically inserted, wrong unit logically


installed (=mismatched unit)

Light grey with a blue border; type of unit


indicated

Software version mismatch. The unit's


software is not compatible with the
master unit's software.

Non-FXC units have to be Installed in order to be operational. By default, the


following units are in use: power supply unit (on the left), power interface panel,
fan unit, and interface unit.
If several nodes are chained via LMPs, the connection must be established as
described in Section 2.4.2.
For information on installing and uninstalling the units logically with the
Manager, see Section 8.2.1.

2.4.2

Address connection via Q1


The MetroHub node can also be accessed via the Nokia Connection Tool.

To access the MetroHub node when you know the Q1 address of the
master FXC unit:

16 (116)

1.

Select Connection Connect... to open the Connect to node dialog box,


see Figure 3.

2.

Define the needed parameters/select a previously configured connection.


Detailed information on using the Nokia Connection Tool is available in
General Communication Service Users Manual.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Nokia MetroHub Manager

Figure 3.

Nokia Connection Tool (Connect to Node dialog)

Fill in the LMP or Q1 address of the equipment to the Q1 Address field,


depending on the connection used.
If the LMP is chained, a unique Q1 address must be selected for the LMP, and the
connection to the node is established with the Connect... option in the Manager.

2.4.3

Sobriquet connection
For information on how to access the MetroHub node when you give the
sobriquet on the command line, see General Communication Service Users
Manual.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

17 (116)

Commissioning and Maintenance

2.5

Accessing the MetroHub node offline file


The offline mode allows you to manage a virtual node. All the information is
saved in a file in your computer and this file represents an image of a real node.
By using this feature it is possible to create a template which may be used to
commission numerous installations with similar configurations. You could also
use this to make changes to an installation while at the office before going to the
field.
To create a new virtual node file, select File New.
When creating a virtual node file for the first time, you must specify the
equipment configuration. When managing an online node, the configuration is
read directly from the equipment.

Note
When in the offline mode, MetroHub Manager does not verify the entered
configuration. The configuration is verified with the actual equipment when it is
sent to the node. If the created configuration does not correspond to the actual
installed equipment, a warning is displayed.
To open an existing file, select File Open....

18 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Nokia MetroHub Manager

Figure 4.

2.6

MetroHub Manager Equipment window (offline mode)

Saving node information in a file


All node information can be saved in a file for later use, regardless of the mode.
To save the information when working online to a node, click each unit once in
the Equipment window so that the information is read and then it can be saved.
The information in the file can then be sent with the Maintenance Restore
Backup Settings command to another node.
MetroHub supports two site configuration file formats, that is, both the extension
.dat (for the node offline file) and the new extension .xml.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

19 (116)

Commissioning and Maintenance

2.7

Accessing the MetroHub node remotely via NMS


Security in MetroHub Manager is governed by the operating environment of the
Manager.
Windows NT4.0

When operating under NMS/10, the user must belong to one of the NMS groups
to be able to use an NMS-compatible manager such as Nokia MetroHub Manager.
Refer to NMS/10 User Guide for the exact privileges accorded to each group.
Windows 95 and 98

MetroHub Manager does not support NMS usage in Windows 95 and 98.

2.8

Printing
You can print information from Equipment, Cross-connections and Alarm
windows. The window must be open to make printing possible.

2.9

Menu overview
All MetroHub Manager functions can be accessed through the application menus.
The main functions under the menus are briefly described in Figure 5.

20 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Nokia MetroHub Manager

Nokia MetroHub Manager


Application
window

File

Creating and managing files


Printing files

Connection

Managing connection to a NE

Configuration

Launching Commissioning Wizard,


Managing Cross-connections,
Identifications, Synchronisation,
Q1 management, Circuit Management

Alarms

Alarms view

Maintenance

Tests, Temperature Monitoring,


Resets, BackUp, Software Copy

FXC
This menu appears
when some transmission
unit is selected

Figure 5.

DN99610738
Issue 5-0 en Draft

Tools

Q1 Tool, Circuit Manager, Reports,


Toolbar, Status Bar, Manager Options

Window

Sizing windows

Help

Online Help

Overview of Nokia MetroHub Manager menus

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

21 (116)

Commissioning and Maintenance

22 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Commissioning Nokia MetroHub

Commissioning Nokia MetroHub


This chapter describes the commissioning process of Nokia MetroHub
Transmission Node.
Commissioning is the process of bringing a newly installed network element into
use. It configures the system for operational use and defines all the system
parameters needed for the system to function.
Nokia MetroHub Manager provides a commissioning wizard that guides the user
through the whole commissioning process. The commissioning process is divided
into two phases: testing and configuration.
A site configuration file containing a valid configuration is needed to configure
the node with the Commissioning Wizard. MetroHub supports two site
configuration file formats, both the extension .dat (for the node offline file) and
.xml (for the site configuration file). It is possible to include all necessary settings
for the configuration in the file. All defined parameters are automatically read
from the file and sent to the node during the commissioning process. The site
configuration file (SCF) with the extension .xml is usually provided by network
transmission planning.
Alternatively, the user can set up Nokia MetroHub completely by proceeding
manually through all the relevant setting menus. In this case, no commissioning
report can be obtained.

3.1

Preparing for the commissioning

To prepare for the commissioning of Nokia MetroHub:

DN99610738
Issue 5-0 en Draft

1.

Check that MetroHub node has been installed correctly, following the
instructions in this user manual.

2.

Check that MetroHub Manager has been installed in your PC.

3.

Check that a valid site configuration file (SCF) exists on the PC hard disk.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

23 (116)

Commissioning and Maintenance

3.1.1

4.

Edit the SCF by adding missing settings (see Section 3.1.1).

5.

Check that you have the cable to connect the PC to the LMP port of
MetroHub (see Section 2.4) before moving to the site to commission the
node locally.

Settings to be added to the site configuration file before


commissioning Nokia MetroHub
There are some settings that need to be added to the SCF before commissioning
Nokia MetroHub. This chapter lists the parameters, which are not supported by
Nokia NetAct transmission planning tools. The missing parameters are added to
the existing site configuration file using transmission node Managers. Some of
these parameters are obligatory and marked in the table with a star (*).

Table 2.

Settings to be added to the SCF before commissioning

Settings
Identifications

Equipment name
Group name
Site location
Node and unit installation information

Cross-connections

Cross-connection label

Q1 Management

Q1 group address
Q1 baud rate
Hybrid switches* (processor, internal and external)
EOC settings*

Synchronisation
Unit

Synchronisation sources*
Unit name and installation information
Interface type*
Interface name
Interface CRC usage*

Radio hop information

Hop name
Hop frequency*
Hop max. TX power*
Hop temporary ID*
Hop mode*
Hop accept channels*

24 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Commissioning Nokia MetroHub

To edit the site configuration file:


1.

Open the Nokia MetroHub Manager. Select File Open.

2.

Select the site to be edited in the Site Selection dialog.

3.

Perform the necessary settings to the units and the node (see Table 2).
Interface settings:

for FXC E1/T1:


-use of interface, CRC usage mode of interface

for FXC RRI:


1) Flexbus settings: use of Flexbus interface, Flexbus capacity,
Flexbus DC
2) Platform interface settings: use of interface, CRC usage mode of
interface
3) Radio settings (see Section 3.1.2 and refer to the user manual of
the corresponding radio).

Q1 transmission control bus settings:

Q1 address, Q1 bus speed, Q1 hybrid switches and EOC channel


settings

Synchronisation related settings:

synchronisation sources and loop bits in case of a loop network

Identification-related settings and other settings:

4.

DN99610738
Issue 5-0 en Draft

Node ID (equipment and site name)

Node installation information (power units, DIU and fan unit)

Transmission unit names and installation dates (in the corresponding


transmission unit's menu).

Save the file with File Save As... command.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

25 (116)

Commissioning and Maintenance

3.1.2

Obligatory radio settings

3.1.2.1

Nokia FlexiHopper settings

Note
Familiarise yourself with the Nokia FlexiHopper with FXC RRI User Manual,
before setting Nokia FlexiHopper radio settings.

To set the obligatory settings for Nokia FlexiHopper radio:


1.

Click the appropriate FXC RRI unit in the Equipment View window. A
unit-specific menu appears.

2.

Select the Settings / Outdoor Unit command on the FXC RRI menu
corresponding to the Nokia FlexiHopper radio. The Settings dialog opens.
See Figure 6.

Figure 6.

26 (116)

Nokia FlexiHopper settings for the outdoor unit in FXC RRI

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Commissioning Nokia MetroHub

3.1.2.2

3.

Set the Tx frequency. Use the Tx frequency provided by radio frequency


planning.

4.

Set the maximum Tx Power. This value is also provided by radio frequency
planning. The value is dependent on the frequency band. For example, for
a 38 GHz frequency band radio, the maximum allowed value is 16 dBm.
For more information refer to Nokia FlexiHopper with FXC RRI User
Manual, Product Description.

5.

Set the Tx power ON.

6.

Set the ALCQ (Adaptive Level Control with Quality measure) OFF. If
needed, the ALCQ can be switched on after the hop is commissioned and
the fine-alignment of the antenna is performed. The Rx input level,
determined by the radio frequency planning, must also be correct.

7.

For the ALCQ to function, you must set the ALCQ set point value (dB).
This value can be calculated by radio frequency planning. For more
information refer to Nokia FlexiHopper with FXC RRI User Manual,
Product Description.

8.

Set Interleave Status, if needed. Possible values for the interleave status are
Off, Depth 2 and Depth 4. Depth 4 is recommended. The status must be
the same at both ends of the hop. For more information, refer to Nokia
FlexiHopper with FXC RRI User Manual, Product Description.

9.

Click the OK button.

Nokia MetroHopper radio settings

Note
Familiarise yourself with the Nokia MetroHopper with FXC RRI User Manual,
before setting Nokia MetroHopper radio settings.

To set the obligatory settings for Nokia MetroHopper radio:

DN99610738
Issue 5-0 en Draft

1.

Click the appropriate FXC RRI unit in the Equipment View window. A
unit-specific menu appears.

2.

Select the Settings / Outdoor Unit command on the FXC RRI menu
corresponding to the Nokia MetroHopper radio. The Settings dialog box
opens. See Figure 7.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

27 (116)

Commissioning and Maintenance

Figure 7.

3.

28 (116)

Nokia MetroHopper's RF settings page for the outdoor unit in FXC


RRI

Click the Commissioning Settings page. This page is only visible in the
node file mode. A dialog opens, see Figure 8.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Commissioning Nokia MetroHub

Figure 8.

DN99610738
Issue 5-0 en Draft

Nokia MetroHopper's Commissioning settings page for the outdoor


unit in FXC RRI

4.

Set the Hop Mode. One end of the hop must be set as the master and the
other end as the slave.

5.

Set the Temporary Hop ID. This value must be the same for both the
master and the slave.

6.

Use the Select All button to select all channels in the Automatic Channel
Selection.

7.

Click the Apply button.

8.

Click the RF Settings page to view the RF page again.

9.

Set the Interleave Status, if needed. The status must be the same at both
ends of the hop.

10.

Set the Forced Synchronising Master, if needed. This check box is only
enabled, if you set the Hop Mode as the master in step 4.

11.

Click the OK button.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

29 (116)

Commissioning and Maintenance

3.1.3

Node offline file


A node offline file, containing a valid configuration, can also be used to
commission Nokia MetroHub with the Commissioning Wizard, if a valid site
configuration file cannot be obtained from transmission network planning. The
user creates the node offline file and includes all the necessary settings for the
configuration in the file, as provided by transmission network planning. All
defined parameters are automatically read from the node offline file and sent to
the node during the commissioning process.
The node offline file can be used for two purposes. It can be used in the
commissioning process and later as a backup file. It is recommended to use the
node offline file (with the extension .dat) as the backup file and not the site
configuration file (with the extension .xml).
You can create the file offline and send it to the node during the commissioning
process. This allows more network set up to be done off site. You can also use the
node offline file as a backup file. However, if you want to create a separate
backup file, you can save the settings after the node has been successfully
commissioned and it is functioning in the desired way.

To create a node offline file:


1.

Select File New.

2.

Install the desired FXC units, radios and optional second power supply and
battery backup units in Equipment View.

3.

Perform the necessary settings to the units and the node.


Cross-connections

Create the cross-connections in the Cross-connections window.


Create the bypass cross-connections first and then the other crossconnections.

Activate the cross-connections before creating the settings.

Synchronisation related settings:

synchronisation sources and loop bits in case of a loop network.

Interface settings:

30 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Commissioning Nokia MetroHub

For FXC E1/T1 Use of interface, CRC usage mode of interface

For FXC RRI Flexbus settings (use of Flexbus interface, Flexbus


capacity), Platform Interface settings (use of interface, CRC usage
mode of interface) and radio settings. For more information on radio
settings see Section 3.1.2 and refer to the user manual of the
corresponding radio.

Q1 transmission control bus settings:

Q1 address, Q1 bus speed, Q1 hybrid switches and EOC channel


settings

Identification-related settings and other settings:

4.

3.2

Node ID (equipment name and site name)

Node installation information (date, time and person)

Cabinet unit installation dates (power units, DIU and fan unit)

Transmission unit names and installation dates (in the corresponding


transmission unit menu)

EAC programmable alarms

Save the node offline file with File Save as... command.

Commissioning process

To commission the MetroHub node with the commissioning wizard:

DN99610738
Issue 5-0 en Draft

1.

Start MetroHub Manager (see Section 2.2).

2.

Establish a connection to the node (see Section 2.4)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

31 (116)

Commissioning and Maintenance

3.

Choose Configuration Commissioning Wizard from the menu bar.

Note
The units must not contain modified settings (such as cross-connections) when
running the commissioning wizard.
Nokia delivers all units with factory settings. If you have already
configured the units, you need to restore the factory settings. Select Maintenance
Reset.... You can select to restore all units at the same time by clicking the
Select All button (see Figure 28). After that you can run the commissioning
wizard.
4.

Run all MetroHub tests (see Section 3.4).

5.

Check the results of the tests from the Testing box and fill in the required
fields.

6.

Click Next to open the Site Selection dialog box (see Figure 12).

7.

Browse the node offline file (with the extension .dat) or the site
configuration file (with the extension .xml). Select a site from the site list
displayed if you are using the site configuration file.

8.

Click Next to open the Accept Site Selection dialog box (see Figure 14).
Verify that the selected site is the correct one.

Note
The program then performs the node configuration check.
9.

10.

32 (116)

Click Next to accept the selected node offline file and the site, and to send
node settings to the node.

The End dialog will appear if no FXC RRI units are used (See
Figure 16).

The Check and fine-tune radio hops dialog opens, if radios are
included in the configuration (see Figure 15). Click Next when the
required hop statuses are OK. The End dialog opens (see Figure 16).

Check the Commissioning Report, give the file a name and store it on the
disk by clicking the Finish button.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Commissioning Nokia MetroHub

COMMISSIONING PROCESS
User

Manager SW

Start MetroHub Manager


Create site configuration file
or node offline file
Connect to the node
Start commissioning wizard

All units are installed logically and


the Manager reads the equipment
configuration from the node.
Testing phase

Run MetroHub tests:


- cross-connections
- fan
- heating
- external alarm
- battery

- FXC unit test for


each installed unit
+connected OU

Check the test report and


give the battery serial
number if applicable
Node sets default settings

Configuration phase
Select and accept the node
site configuration file or offline file
to send node settings to the node
Node settings are performed
- FXC unit settings
- OU settings
Check radio hops
Commissioning report created
Check commissioning report
and store it into a file

Figure 9.

3.3

Commissioning process

Switching the power on


To switch the power on:

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

33 (116)

Commissioning and Maintenance

Turn the stand-by switch to "ON" position in the power supply unit
(DSUx). If there is a redundant power supply in the cabinet, switch it on
also.

The green LED will be lit in the power supply unit in five seconds.
The interface unit (DIUx) LED will be red until the software of the FXC unit
acting as the node control unit starts up totally and updates the DIUx LED state.
This typically takes less than 30 seconds.

Note
The node is not ready and it cannot be accessed with the node Manager until the
red state changes.
If the power supply unit LED turns fixed yellow after the power supplys standby switch is turned to "ON" position, and the units do not start up, the power
supply has detected too low a temperature in the units (<-10C/14F) and the cold
start logic has started unit heating (see Product Description). The operating
voltages will be connected when the units are heated up. The heating typically
takes a few minutes.

3.4

Testing with the commissioning wizard


Once the commissioning wizard has been opened by choosing Configuration
Commissioning Wizard, the Welcome dialog box appears, showing the tests to
be run, see Figure 10.
The testing phase contains activities which ensure that the hardware is
functioning properly. In this phase all feasible tests are run in the MetroHub node
and also in the transmission units found in the node.
You do not need to perform any other actions than start the testing process. All
tests are run as default. Although you can select which tests to run, site acceptance
requires that all tests are completed successfully.
The tests run at this phase are: cross-connections test, fan test, heating test, battery
test, and EAC interface tests.

34 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Commissioning Nokia MetroHub

Figure 10.

Welcome dialog box

After the tests have been selected, the Manager program executes them, and the
results are shown in the Testing dialog box, see Figure 11.

Note
Running the tests takes less than three minutes.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

35 (116)

Commissioning and Maintenance

Figure 11.

Testing dialog box

If a battery unit is used, its serial number can be given in this dialog box.
The test results are gathered in the commissioning report. See Section 3.5.3 for
more information about the commissioning report.
For more information on the tests, see the Product Description.

3.5

Configuring with the commissioning wizard


The configuration phase contains activities needed to make the node functioning
in the network. These activities include the node ID, Q1 and synchronisation
settings for the node, unit-specific settings for the transmission units, radio
parameters, and cross-connections.

36 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Commissioning Nokia MetroHub

3.5.1

Configuring the site


After the testing phase, the commissioning wizard continues with site
configuration.
The Site Selection dialog box opens, see Figure 12. In this dialog you can browse
the node offline file or the site configuration file.

Figure 12.

Site Selection dialog box

The Browse button opens a standard open dialog where you can look for the
appropriate file, with the extension .xml or .dat. The default search criteria is .xml.
If you select a valid xml file, a standard dialog opens (see Figure 13) where you
can select the appropriate site.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

37 (116)

Commissioning and Maintenance

Figure 13.

Site selection open dialog box

In the dialog box shown in Figure 14 you can check that the selected site is the
correct one. Some of the selected file data is shown to the user.

38 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Commissioning Nokia MetroHub

Figure 14.

Accept Site Selection dialog box

By clicking the Next button, you accept the selected file. The Manager compares
the file equipment configuration against the node configuration. If there are
differences, you are notified about them with the following message: Fix the
configuration and restart the commissioning process.
After the configuration is correct, all the settings are sent to the node and units.
The MetroHub Manager takes care of the node level settings and the integrated
FXC unit managers take care of the FXC unit related settings and possible OU
settings.

3.5.2

Check and fine tune hops


In the following dialog box, Check Hops, (see Figure 15) you can monitor
possible radio hops and fine-tune them. Only FXC RRI units are enabled. The
MetroHub Manager polls each unit, and updates the status of the radio outdoor
units to the dialog box.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

39 (116)

Commissioning and Maintenance

Figure 15.

Check Hops dialog box

Click Next and the polling ends. The End dialog box opens. You can view a
commissioning report there, see Figure 16.

40 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Commissioning Nokia MetroHub

3.5.3

Commissioning report
A Commissioning Report is gathered containing the test results and the node
configuring information (node settings, the settings of each unit, crossconnections). The report is shown to the user. Click Finish to end the wizard. This
report is protected and stored into a file, if a file name is given. This file can be
used, for example, for site acceptance. Note that the file is a text file with the
extension .cmr and has to be opened with a text editor.

Note
After the first end of the hop is commissioned, the hop status in the Check Hops
dialog box and in the commissioning report is shown as Not ready or Trying, no
far-end found. See Figure 15.
A complete commissioning report can be obtained after the far-end of the hop has
been commissioned.

Figure 16.

DN99610738
Issue 5-0 en Draft

Last page of the Commissioning Wizard

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

41 (116)

Commissioning and Maintenance

42 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing Nokia MetroHub

Managing Nokia MetroHub


This chapter contains information on:

4.1

creating cross-connections with the Manager

adjusting node settings

configuring related settings

Creating cross-connections with the Manager


If there is no cross-connection file available for commissioning the MetroHub
node, the cross-connections have to be created manually with the MetroHub
Manager.
A cross-connection defines how the signals are routed between FXC units in a
node. Cross-connections are created into banks. The node contains two crossconnection banks. The state of a cross-connection bank can be active or inactive.
Only the cross-connections that are in the active bank are in use in the node. If
you want to start using the cross-connections in the inactive bank, you must
activate that bank manually. Note that adding new cross-connections or editing
existing cross-connections is only possible in an inactive bank.

Note
Export the cross-connections in the inactive bank to a file before power reset, as
the inactive bank will be cleared from the node memory. Later, the same file can
be imported to the inactive bank to restore the cross-connections.

Note
Create the bypass cross-connections before creating other cross-connections.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

43 (116)

Commissioning and Maintenance

Exporting a cross-connection file

To create and export a cross-connection file with the MetroHub


Manager:
1.

Open the Manager and start the file mode by File New.

2.

Install the appropriate FXC units and radio outdoor units (OU) in the
Equipment window.

Note
When you are using the commissioning wizard and the node offline file, the
configuration must match with the configuration you give in the node offline file
for the site (TRE Unit and MWR Hop information).
3.

Open the Cross-connections window.

4.

Create all needed connections into an inactive bank.

5.

Select File Export File. (Notice that you must have the Crossconnections window active before this exporting can be done.)

6.

Save the exported file in a desired location.

Importing a cross-connection file

To import a cross-connection file:

44 (116)

1.

Connect to the node or open a file.

2.

Select Configuration Cross-connections and the Cross-connections


window opens.

3.

Select the inactive bank.

4.

Select File Import File...

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing Nokia MetroHub

5.

Select the desired file in the dialog that opens. Click the Open button and
the file is imported to the inactive bank.

Note
Cross-connections can only be imported to the inactive bank.

4.1.1

Cross-connections window
You can edit cross-connections and banks only through the Cross-connections
window.

To open the Cross-connections window:


1.

Create an online access to the node or an offline access to the file.

2.

Click Configuration Cross-connections... on the menu.

The Cross-connections window is divided into two parts. The upper window
includes a cross-connection list view and on the right-hand side of the window
you can find, for example, the buttons for Add, Remove and Modify
connections. The lower window includes a cross-connections graphic view.
Cross-connections list view

There is a list view for both the active bank and the inactive bank. The list view
shows cross-connection related information in text format. A connection is
always presented in one row. You can select several connections in the list. The
view also provides a pop-up menu to carry out certain functionality for the
selected cross-connection(s). It also provides buttons to carry out crossconnection related or bank related operations.
Cross-connections graphic view

You can use the graphic view to create cross-connections and also to show how
the selected connection in the cross-connections list view progresses from one
FXC unit to another. The graphic view shows only one connection at a time.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

45 (116)

Commissioning and Maintenance

Figure 17.

4.1.2

Cross-connections window

Managing cross-connections
Cross-connections can be added, modified and removed.

4.1.2.1

Cross-connection properties dialog

Complete details about the selected cross-connection are shown in the Properties
dialog. To open the Cross-connection Properties dialog, select an active or
inactive bank and right-click the desired cross-connection to open a pop-up menu,
and choose 'Properties'.
While managing a real node (NE), for the protected cross-connection selected in
the active bank, the dialog also displays the condition bit status for Condition 1
and/or Condition 2. In such a case, a Refresh button is also available to refresh
the condition bit status (see Figure 18). Note that once the condition bit status is
read, the status is also displayed in the list-view of the Cross-connections
window for one or more cross-connections having the same condition/s (see
Figure 19). The condition bit status can also be read for selected crossconnections in the Refresh pop-up menu. The Refresh pop-up menu, which is
available for the cross-connections active bank, refreshes the condition bit status
for all the protected cross-connections in the bank.

46 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing Nokia MetroHub

DN99610738
Issue 5-0 en Draft

Figure 18.

Cross-connection Properties dialog

Figure 19.

List view of the cross-connections window

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

47 (116)

Commissioning and Maintenance

4.1.2.2

Adding bypass connections

Bypass connections are always bi-directional and the granularity is 2M. These
connections are only available for FXC RRI units.
A fast and easy way to add bypass cross-connections is via the graphical view in
the Cross-connections window. Refer to Section 4.1.2.3 for more information.
4.1.2.3

Adding cross-connections

All different types of cross-connections supported by the node can be created


through the Add Cross-connection wizard. The Cross-connection wizard guides
you through the different steps involved with adding a new cross-connection into
an active bank. You can also create cross-connections in the graphical view of the
Cross-connections window. Both of these methods are described in this section.
The cross-connection types are explained in the Product Description. According
to the Cross-connection type only the required controls are enabled in the dialog.
If you forget to set some setting when adding a new connection, you are informed
about a missing setting.
Method 1

The following is an example of how to create a protected cross-connection with


the Add Cross-connection wizard.

To add a cross-connection:

48 (116)

1.

Click Configuration Cross-connections. In the dialog that opens,


select Inactive bank.

2.

Select Add and the Cross-connection wizard opens.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing Nokia MetroHub

Figure 20.

DN99610738
Issue 5-0 en Draft

Add cross-connection wizard Tx1/Rx1 (FXC RRI) page

3.

Select the reliable port by clicking the interface symbol (Tx1/Rx1).

4.

Give the cross-connection a name (label).

5.

Select 'protected bi-directional' as the cross-connection type.

6.

Select the granularity. Click Next.

7.

Select the protected (Tx2/Rx2) port in the dialog that opens and click Next.

8.

Select the protecting port (Tx/Rx). Click Next.

9.

In the dialog that opens (see Figure 21), select the conditions:

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

49 (116)

Commissioning and Maintenance

Select an FXC unit.

Select an interface in the FXC unit.

Select a time slot in the FXC unit.

Select a bit in the FXC unit.

Set the polarity.

Click the OK button. The Condition dialog closes.

Note
Local (valid inside the 2 Mbit/s signal) or Global (valid inside the whole node)
common conditions are not supported in MetroHub protected cross-connections.
If you need to create several protected connections with common condition
data, you can store the condition data by clicking Set As Default. The data
is saved for the duration of the session and it is always taken into use by
default for new protected connections.

Figure 21.

50 (116)

Condition dialog box (enabled only for protected PDH crossconnections)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing Nokia MetroHub

The information displayed in the last page of the wizard provides an overview of
the new cross-connection to be created and also seeks certain parameters (if
required) depending on the selected cross-connection type in the first termination
point page of the wizard. The arrows drawn in the space between termination
point buttons indicate the direction of the cross-connection and its type.
Figure 22 illustrates how the information is displayed when the desired Flexbus,
channel and platform interface of an FXC RRI unit is selected on the first page of
the Add Cross-connection wizard.

Figure 22.

DN99610738
Issue 5-0 en Draft

Add cross-connection wizard's last page: overview

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

51 (116)

Commissioning and Maintenance

Method 2

A fast and easy way to add cross-connections is via the graphical view in the
Cross-connections window . You can select the unit, physical interface and
granularity as shown in Figure 23.

To add a cross-connection in the graphic view:


1.

Press down the left mouse button to select an interface.

2.

Drag the line to the second termination point and release the mouse button.

3.

A pop-up menu is displayed where you can select the granularity.

Figure 23.

4.1.2.4

Selecting interface and granularity in the graphic view

4.

The Cross-connection wizard opens.

5.

On the first page, select the cross-connection type.

6.

On the second page of the Cross-connection wizard you select the correct
channel and click Next.

7.

In case of an FXC RRI unit, select the desired channel.

8.

Click Finish.

Modifying a cross-connection

Already existing cross-connections can be modified.

52 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing Nokia MetroHub

To change some of the settings of an existing connection, click Modify in the


Cross-connection view. Note that in the connection mode only connections in
the inactive bank can be edited.
This opens the Modify Cross-connection wizard. The layout of this wizard is
exactly the same as in the Add Cross-connection wizard.
You can also modify cross-connections via a pop-up menu. Right-click the
selected cross-connection in the inactive bank.
4.1.2.5

Removing a cross-connection

To permanently remove a cross-connection from a bank, first select the


connection or connections you wish to delete. Then click Remove in the Crossconnection view.
Before removing the cross-connections, you will be asked if you want to go ahead
with the removal.
You can also remove cross-connections via a pop-up menu. Right-click the
selected cross-connection in the inactive bank.

4.1.3

Editing cross-connection banks


Cross-connection banks can be activated, copied, and cleared.
Activating a bank

Click Activate in the Cross-connection view. This activates the inactive bank.
Copying a bank

Click Copy in the Cross-connection view. This creates a copy of the crossconnections from an active bank to inactive bank. This is useful, if you want to
create another cross-connection bank with only minor differences from the
original.
Clearing a bank

Click Remove in the Cross-connection view. This removes all cross-connections


from the inactive bank.

4.1.4

Usability hints for cross-connections


Editing active cross-connections

The easiest way to edit an active cross-connection bank is to take a copy to an


empty non-active bank and edit the connections there and to activate the edited
bank.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

53 (116)

Commissioning and Maintenance

Control connections in the Cross-connections view

Controls, for example, the Q1 EOC channel and MCB/LCB bits, are shown in the
Cross-connections window as reserved capacity. These are also marked and seen
as uni-directional connections, even though they are bi-directional by nature. It is
only a way of marking.
It should be noted that control connections are just indicating the reservation of
the cross-connection capacity, so they cannot be removed or edited in the Crossconnections window. They are reserving the capacity from both banks.
When these settings are created, the cross-connection capacity reservation is
checked from both the active and inactive bank, if the setting is created to the
E1/T1 interface. In case of FXC RRI units, the capacity reservation is checked
only from the active bank.

4.2

Adjusting node settings

4.2.1

Identifications
You can adjust the identifications settings for the managed node. The installation
date can be set for all different units. Additionally, for the battery unit, all other
ID information, including code, version, and serial number, can be set with the
Manager's Identifications dialog box. For the whole node it is possible to set the
name, site name, group name and site location. Node Installation data consists of
the date and time of the installation and the name of the person who performed it.

To adjust identifications settings

4.2.2

1.

Connect to the node or file.

2.

Select the Configuration Identifications... menu command to open the


Identifications dialog box.

3.

Select which identifications data you want to adjust and fill in the required
information.

Service interface
You can adjust the settings of the LMP and the Q1 port. These settings are baud
rate, Q1 address and Q1 group address. Under this menu it is also possible to
adjust timeouts.

54 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing Nokia MetroHub

The timeout settings concern the temporary settings of the whole node. These
include, for example, interface loops and forced controls.

To adjust service interface settings


1.

Connect to a node or open a node file.

2.

Select the Configuration Service Interface... menu command to open


the Service Interface dialog window.

3.

Select either Port Settings or Timeouts.

4.

Adjust the settings or press the Default Rate buttons to set the default
values stored in the node.

The default baud rate is 9600 bit/s for LMP and 2400 for Q1. The default address
is 1 for the ports.
The supported baud rates for LMP are 4800115 200 bit/s.

Note
Supported remote Q1 connection rates are 240019 200 bit/s.

4.2.3

Synchronisation
You can adjust the synchronisation settings of a managed node.

To adjust synchronisation settings

DN99610738
Issue 5-0 en Draft

1.

Connect to the node or file.

2.

Select the Configuration Synchronisation... menu command to open


the Synchronisation dialog window.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

55 (116)

Commissioning and Maintenance

Figure 24.

3.

Synchronisation dialog

Select the network topology according to the network type you are building
(chain or loop).
When Loop is selected, any interface with the Far end alarm active, is not
accepted as a synchronisation source. However, if Chain is selected, these
interfaces are also accepted.
You can set up to four synchronisation priorities. For each priority you
need to select a timing source.

Rx Clock type requires also a unit and an interface to be chosen.

When Sync Input is selected, only FXC E1 or FXC E1/T1 units can
be selected for the source, and the interface is fixed to 4.

When Internal timing is selected, all subsequent priorities will be


disabled.

The display of the used synchronisation source can be updated with the
Refresh button.

56 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing Nokia MetroHub

To adjust synchronisation loop bit settings

4.2.4

1.

Click the Loop Bits tab in the Synchronisation dialog window to open the
Loop Bits dialog window.

2.

Select Add or Modify.

3.

Select one of the timing options.

4.

Select the unit and interface for the loop bit.

5.

Select the desired settings for MCB (Master Clock Bit) in the master group
and LCB (Loop Control Bit) in the loop group.

Q1 management
You can adjust the Q1 management settings of a MetroHub node. These settings
are done to enable remote management when used.
Setting up Q1

In order to get MetroHub under Q1 management, the user must set up a Q1


hybrid. The hybrid controls the Q1 signal flow inside MetroHub and in E1, T1
and Flexbus interfaces. Hybrid implementation is illustrated in Figure 25.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

57 (116)

Commissioning and Maintenance

Q1_OH1

MetroHub

FB1
Q1_EOC_1-16

16 platform
interfaces

+
Q1_OH2

External

Q1-1

switch

FB2
FXC RRI

Q1-2

...

E1_1

Q1_EOC_1

Processor

Q1_EOC_2

switch

E1_2
Q1_EOC_3

E1_3
E1_4

LMP-1

+
Q1 Port

Q1_EOC_4

LMP
FXC E1
FXC E1/T1

LMP-2

Node control
unit processor

= Bidirectional
summing point

Figure 25.

Q1 hybrid implementation

Hybrid switches

There are three hybrid switches: Processor, Internal (not shown in Figure 25) and
External. You can only set their usage on or off.
Hybrid switches are recommended to be left in the default values: Processor
switch on, External switch on, and Internal switch off (see Figure 26).

58 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing Nokia MetroHub

When the Processor and External switches are on (closed), MetroHub is set up so
that it can be reached locally from Q1-1 and Q1-2 interfaces. To enable remote
management, a transmission channel for Q1 has to be created. This channel is
called EOC, Embedded Operations Channel. This channel can be embedded into
any E1 or T1 time-slot in FXC E1 and FXC E1/T1 units and in any platform
interface or into the radio overhead in FXC RRI unit. This is done by first creating
the EOC channel and then closing the EOC switch.

Note
When there is a need for routing the incoming Q1 EOC channel to the External
Q1-1 or Q1-2 interfaces, the Processor switch is required to be in ON position. So
in order to create the Q1 management connection between an external piece of
equipment and an EOC channel via Nokia MetroHub, the Hub itself will be
connected under the same Q1 channel management.
Q1 EOC in the payload

In FXC E1, FXC E1/T1 and FXC RRI transmission units it is possible to use part
of the payload signal to carry Q1 management data.

To adjust Q1 management settings

DN99610738
Issue 5-0 en Draft

1.

Connect to the node or open the node file.

2.

Select the Configuration Q1 Management... menu command to open


the Q1 Management dialog window.

3.

You can set up EOCs by selecting Add EOC... menu command from the
pop-up menu.

4.

Select the unit to be configured.

5.

Select the interface to be configured. In FXC E1 and FXC E1/T1 there are
four interfaces to choose from, in FXC RRI there are up to 16 platform
interfaces available.

6.

Select a time-slot for Q1 management.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

59 (116)

Commissioning and Maintenance

Select a sampling rate and bit(s) for the Q1 channel. If 64 kbit/s sampling rate is
selected, the whole time-slot is reserved for Q1 and no bit selection is required. If
a lower sampling rate is selected, the bits inside the selected time-slot have to be
selected. The sampling rate options are 64, 32, 16 and 8 kbit/s in time-slots 131
and 16, 8 and 4 kbit/s in time-slot 0. In case of timeslot 0, only the bits 58 are
allowed for EOC usage.

Note
It is recommended that the sampling rate is at least four times higher than the baud
rate used in the Q1 port.
After the EOC has been created, the switch (Q1_EOC_# in Figure 25) has to be
closed to connect the hybrid to the EOC. The MetroHub Manager does this
automatically, by setting the corresponding In Use state to ON in the EOC
Settings window.
Q1 EOC in the radio overhead

In FXC RRI there are two possibilities for Q1 channel, the EOC in the payload
which was described in the previous section and EOC in the radio overhead which
is described below.

To set EOC in the radio overhead


1.

Connect to the node or open the node file.

2.

Select the Configuration Q1 Management... menu command to open


the Q1 Management dialog window.

3.

You can set up EOCs by selecting Add EOC... menu command from the
pop-up menu.

4.

Select a FXC RRI unit to be configured.

Select either Overhead 1 or 2, depending on the selected Flexbus. Overhead 1


corresponds to Flexbus 1 and Overhead 2 corresponds to Flexbus 2. After this
selection has been made, no further configurations for sampling rate are required
because the sampling rate is fixed so that it is always at least 64 kbit/s. If EOC is
created to the radio overhead it is always connected to a hybrid, which means that
the Q1_OH# switch is closed.
The advantage of using the overhead channel for Q1 is that it does not waste
payload.

60 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing Nokia MetroHub

Q1 management in star, chain and point-to-point networks

The Q1 network management channel has a bus structure, so the EOC (Embedded
Operations Channel) can be distributed in multiple directions. Figure 26 presents
the setting of the EOC channel coming in from E1 in slot 1 and leaving via
different FXC RRI units to other sites.

Figure 26.

Setting of EOC and Q1 switches

If the managed area is divided to different Q1 buses (see Product Description, Q1


management) or the Q1 channel is otherwise forwarded over the MetroHub, the
EOC channel is just cross-connected as normal data towards other equipment.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

61 (116)

Commissioning and Maintenance

Q1 management; application examples

MetroHub #1

MetroHub #2

RRI

BSC

RRI
FB1

FB2

Q1
(A) in radio overhead or
(B) inside a 2 Mbit signal

E1
RRI

IF1

E1

Q1 in
2 Mbit/s

DIUA
X.25

Flexbus
Q1 cable
E1

NMS
FIU 19
Figure 27.

Examples of Q1 network connections

To set Q1 inside MetroHub #1 and towards FIU 19 via DIUx


1.

Set Defaults and Hybrid switches as instructed earlier in this section.

2.

Set the Unit (e.g. 1), Interface (e.g. 1), Time slot (e.g. 20), Sampling rate
(e.g.16 kHz) and Bits (e.g. 7-8)

To set Q1 transport to next MetroHub


1.

Set the interface as instructed in this section.

2.

(A) Q1 in radio overhead. Set the Unit (e.g. 2) and Interface (e.g. OVH1)
(B) Q1 inside a 2 Mbit/s signal. Set the Unit (e.g. 2), Interface (e.g.10) and
Time slot (e.g. 25).

62 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing Nokia MetroHub

To set Q1 inside MetroHub #2


1.

Set Defaults and Hybrid switches as instructed in this section.

2.

Q1 via overhead. Set the Unit (e.g. 3) and Interface (e.g. OVH2).
Q1 via 2 Mbit/s signal. Set the Unit (e.g. 3), Interface (e.g. 2), Time slot
(e.g. 25), Sampling rate (e.g.16 kHz) and Bits (e.g. 7-8).

4.2.5

Programmable alarms
You can view and modify the settings for user-specific alarm inputs and control
outputs.

4.2.6

Alarm properties
You can view and modify the settings for node-level faults.

Note
You can find the FXC unit and interface-related settings under the FXC menu
which appears when you click an FXC unit in the Equipment window.

4.3

Configuration related settings


All mandatory transmission unit settings are provided by the node offline file. For
information on more advanced settings, see the related transmission unit online
Help under MetroHub Manager Help.
To access the FXC unit and radio outdoor unit menus, click the FXC unit or
outdoor unit to be managed in the Equipment window. The required menu
appears in the menu bar (in front of the Tools menu).

4.3.1

Nokia FlexiHopper and MetroHopper settings (with FXC RRI)


Nokia FlexiHopper with FXC RRI User Manual and Nokia MetroHopper with
FXC RRI User Manual describe the settings related to the outdoor units of these
radios.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

63 (116)

Commissioning and Maintenance

4.3.2

FXC E1 and FXC E1/T1 transmission unit settings


For details on FXC E1 and FXC E1/T1 unit related settings, see the transmission
unit online Help under the MetroHub Manager Help.

4.4

Check list for mandatory settings


In order to get a MetroHub transmission site running and integrated into the
network, i.e. connected to the NMS, the following mandatory settings have to be
implemented to the node:
Management-related settings:

LMP speed

Q1 address, Q1 bus speed

Q1 hybrid switch and EOC channel settings

Transmission connection related settings:

Use of interfaces, CRC usage, mode of interface (only FXC E1/T1)

If an FXC RRI is used, the Flexbus capacity and Flexbus DC power status.
For details on further radio settings, refer to the user manual of the
corresponding radio.

Synchronisation source

Cross-connections

Identification-related settings (none of these are mandatory but strongly


recommended to be filled in):

64 (116)

Node ID (equipment name and site name)

Node installation information (date, time and person)

Cabinet unit installation dates (power units, DIUx, fan unit)

Transmission unit names and installation dates (in the corresponding


transmission unit menu)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Maintaining Nokia MetroHub

Maintaining Nokia MetroHub


In general, the MetroHub units require very little maintenance. If a unit is faulty,
it must be sent to a Nokia Service Centre for repairing.
Only the fan unit and the battery unit are objects of regular maintenance. They can
be subjected to preventive maintenance actions or there are internal tests that can
be run, using the MetroHub Manager.

WARNING
Read carefully Section Safety notes for the power system in the Installation
document before performing any maintenance tasks.

5.1

Maintenance procedure
The general maintenance procedure is the following:

5.2

1.

Check the tools needed for the type of maintenance. You should always
have the MetroHub key, antistatic wrist strap and Nokia MetroHub
Manager PC and the PC-cable with you.

2.

Keep the units in their delivery package until installation.

3.

Perform the maintenance actions as specified in this document.

4.

After installation, keep some of the packing material for sending units to
be serviced. Recycle the remaining material.

Removing the MetroHub cover


The cabinet internal maintenance requires removing of the MetroHub cover.
Before removing the cover, the following environmental restrictions must be
considered:

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

65 (116)

Commissioning and Maintenance

Rain or snow must not be allowed to fall on the internal surfaces of the
equipment. The internal surfaces are the front panels, cables and
connectors.

The cover must not be removed in environments where dust can be blown
into the cabinet.

Note
Removing the cover issues an alarm.

To remove the cover

5.3

1.

Open the lock at the bottom of MetroHub with the key.

2.

Push the cover from both sides and lift until the locking guides at the side
of the cover come out from the locking recesses.

3.

Remove the cover.

4.

Place the cover on the floor or hang it to the hook at the side of the cabinet.
Use the safety strap to secure the cover to the hook.

Preventive maintenance
This section describes the preventive maintenance measures recommended to be
done for different units and the lock.

5.3.1

Cleaning
If needed, clean the MetroHub cover with a mild detergent, using a sponge or a
soft brush. Strong dissolvents must not be used.
To clean the mechanics, use a clean cloth, vacuum cleaner or compressed air. If
a vacuum cleaner or compressed air is used, the air flow must not be excessive. A
damp cloth and a mild detergent can be used.

66 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Maintaining Nokia MetroHub

5.3.2

Battery
The battery life time depends on the environment, and the rate and depth of
discharging. To find out the performance of the battery, you can run an automatic
test, see Product Description/Node internal tests. In extremely humid
environment, however, the battery is recommended to be replaced every three
years. For instructions on changing the battery unit, refer to Section 8.6.

WARNING
Danger of explosion if the battery is incorrectly replaced. Replace only with
the same or equivalent type recommended by the manufacturer. Dispose of
used batteries according to the manufacturers instructions.

WARNING
If the optional battery unit is used, switching off the AC does not switch off
MetroHub.

WARNING
Do not handle the battery cable carelessly, or open plastic parts of the
battery unit. There is a hazardous energy level present even if the battery is
disconnected from the power interface panel (DIPx).

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

67 (116)

Commissioning and Maintenance

Caution
The battery cable connector must be disconnected from the DIPx during
maintenance.

Note
Dispose of the used battery unit by handing it in at a collection point. Never
dispose of old batteries as domestic waste.

Note
Switch AC on once to start MetroHub when you start to use the internal battery
unit.
The surface of the battery unit and the metal net above it should be checked
occasionally to make sure that there is no dirt which can obstruct cooling.

5.3.3

Fan
The fan life time depends on the environment and running hours. To find out the
performance of the fan, you can run an automatic test, see Product
Description/Node internal tests. As an alternative to this, in an extreme climate
the fan is recommended to be replaced every five years.
In hot temperatures (approx. 50C/122F), a broken fan should be replaced within
75 minutes.

5.3.4

Transmission units
The oscillator of the FXC RRI unit is recommended to be tuned every 10 years.
The oscillators accuracy will then always be in the range +/ 10 ppm. If tuning
is not done, no traffic cuts will occur but signal jitter may increase.
The FXC RRI unit has to be sent to a Nokia service centre for tuning.

5.3.5

Lock
Lubricate the lock with lubricating oil. If the cabinet is used in temperatures
below 0C (32F) lubricate the lock with lubricating anti-freeze oil or use both
anti-freeze oil and lubricating oil.

68 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Maintaining Nokia MetroHub

5.4

Testing
You can perform several tests on a MetroHub node with the MetroHub Manager.
By these tests the condition of hardware can be verified. See the Product
Description for details.

To perform a test
1.

Open a connection to a node.

2.

Select the Maintenance Tests menu command to open the Testing


dialog box.

3.

Select the test(s) to be performed.

4.

Start the test(s) by clicking the Start button.

5.

Wait for the test(s) to be performed.

The results of the test(s) will be displayed in the corresponding Results text
box(es).
Table 4 provides tips for troubleshooting if internal tests fail.

5.5

Temperature monitoring
The temperature information of the node can be viewed in the Manager by
clicking Maintenance Temperature Monitoring.

5.6

Resetting units
In the Resets dialog in the MetroHub Manager you can select the type of reset and
the targeted units. The reset dialog is only accessible in the connected mode and
factory settings are only allowed in LMP connections. Hardware type resets are
possible for all units, whereas factory default settings cannot be reset for the
outdoor units using this dialog.
To open the reset dialog select Maintenance Resets...
If you select all units, the resets are executed in the following order:

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

69 (116)

Commissioning and Maintenance

1.

Reset of the outdoor units (not factory default settings).

2.

Reset of the FXC units.

3.

Waiting for the master unit to recover.

4.

Reset of the node.

5.

Waiting for the node to recover.

6.

The initial value for LMP speed is restored.

Figure 28.

Resets dialog

For more information about resets refer to the Product Description document.

70 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Maintaining Nokia MetroHub

5.7

Restoring backup settings from a file


It is possible to save node and/or unit settings into a backup file (both extensions
.xml and .dat). It is recommended to use the node offline file (extension .dat) and
not the site configuration file (extension .xml) as the backup file.
When the file is opened in this dialog, the manager type and unit configuration is
checked. If the file contains correct data for the unit, the settings can be sent to the
selected unit and/or node. The backup dialog is only accessible in the connected
mode.
To open the backup dialog select Maintenance Restore Backup Settings.

Note
Before restoring the settings at the node level, the node must be in the factory
defaults state.

Figure 29.

DN99610738
Issue 5-0 en Draft

Backup dialog

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

71 (116)

Commissioning and Maintenance

5.8

Copying software banks


It is possible to copy a software bank from a unit to another. The unit type is
checked so that for example copying from FXC RRI to E1 is not possible.
To open the software copy dialog select Maintenance Software Copy....

Figure 30.

5.9

Software copy dialog

Configuration report
The configuration report contains all the configuration information of Nokia
MetroHub (see Figure 31).

To create a configuration report:

72 (116)

Select Tools Reports Configuration Report.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Maintaining Nokia MetroHub

Figure 31.

Configuration report

You can also modify the contents of the configuration report. Click the Options
button and the Configuration Report Options dialog opens (see Figure 32).
Select what to include in the report.
The following options exist:

DN99610738
Issue 5-0 en Draft

Refresh node before report. When selected, configuration data is refreshed


from the node before the configuration report is prepared.

Power, Fan. When selected, the information on the FXC units in the cabinet
is included in the report.

Detailed Unit Identification. When not selected, the hardware/software


configuration part of the report does not contain information on the
hardware and software versions.

Synchronisation. When not selected, all information about node


synchronisation is excluded.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

73 (116)

Commissioning and Maintenance

Q1 Management and Service IF. When not selected, the report excludes
information on Q1 management and service interface of the node.

Cross-connections. When not selected, the report excludes information on


cross-connections.

D-bus allocation. When not selected, the report excludes information on Dbus allocation. (Valid only in Nokia UltraSite BTS Hub Manager).

EAC and Alarm Config. When not selected, the report excludes
information on EACs and alarm configuration.

Line IF (LIF) and Platform IF (PIF). When not selected, the report excludes
information on LIF and PIF from the report.

Radio Settings. When not selected, the report excludes information on


outdoor units (radios) of the FXC RRI units.

Note that these selections are not saved when you close the Configuration
Report dialog.
The configuration report is saved as a text file with the extension .cnr and has to
be opened with a text editor.

Figure 32.

74 (116)

Configuration Report Options dialog

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Troubleshooting instructions

Troubleshooting instructions
This chapter gives some advice on how to locate possible faults in the operation
of Nokia MetroHub. The instructions are presented in Tables 3 and 4. If none of
the given instructions resolve the problem, the fault is most probably in the
MetroHub backplane and you must change the cabinet.

Note
Detailed descriptions of MetroHub alarms are presented in Appendix A.

Table 3.

Troubleshooting tips for setting up MetroHub

Problem

Cause

Action

No power to
MetroHub

1) Fault in the site mains


power supply

1) Check the site mains power


source and fuses. Replace if
needed. Measure with multimeter
that the DIPx has the operating
voltage. Make sure the polarity is
correct when using DC mains.

2) Broken power cable

2) Replace power cable.

3) Power supply unit


switch in stand-by position

3) Turn the switch ON.

4) Power interface units


and/or power supply units
fixing screws are loose

4) Tighten the loose screws.

5) Cold start active

5) Wait until the units are warmed up


to the operational temperature range
and the power supply unit LED turns
from yellow to green.

5) Yellow LED in
power supply unit

6) Overheat in power
supply unit

6) Wait for power supply unit to cool


down. Check also that the fan is
functioning.

6) Power supply
LED steady
yellow

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

Alarm

75 (116)

Commissioning and Maintenance

Table 3.
Problem

MetroHub is
powered but the
manager
connection cannot
be established

-48V DC or +55V
DC output failure in
power interface unit

76 (116)

Troubleshooting tips for setting up MetroHub (Continued)

Cause

Action

Alarm

7) Power supply unit


broken

7) Replace power supply unit.

7) Possible alarm
Fault in power
supply, no lights
on power supply
unit or the LED is
red.

8) Power interface unit


broken

8) Replace the unit.

9) Short circuit in one of


the units

9) Pull the units out one by one until


the power comes back on. Start from
the FXCs and proceed to the fan,
and finally replace the interface unit.
Re-install the units one by one and
replace the faulty unit(s).

1) Bad or poorly
connected LMP cable

1) Check the cable and verify that it


is properly connected.

2) Wrong COM port


settings in MetroHub
Manager

2) Choose right COM port settings in


Tools/Options menu, Defaults: port:
COM1, speed: 9600.

3) SW problems in PC

3) Restart PC: At that point it might


be useful to restart MetroHub as well
by turning the power switch off and
after a few seconds back on if you
are setting up a new node. Note: Do
NOT restart a MetroHub which is
already operating in a network, or
you may cause severe traffic cuts!

4) FXC master broken

4) Change the FXC master.

5) DIUx interface unit is


broken.

5) Change DIUx interface unit.

1) -48V DC or +55V DC
fuse blown in power
interface unit.

1) Replace the fuse.

2) -48V DC or +55V DC
wire loose on the screw
type connector in the
power interface unit.

2) Reassemble loose wires.

3) Power interface unit


broken

3) Replace the unit.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

All LEDs are off or


blinking

DN99610738
Issue 5-0 en Draft

Troubleshooting instructions

Table 4.

Troubleshooting instructions for MetroHub internal tests

Problem

Cause

Action

Cross-connections
test fails (only in
commissioning
wizard)

Fault in some FXC unit

Remove the unit, starting from the


right hand side, and redo the test
until you find the faulty unit. To test
the master FXC, change it to another
slot while using another card as the
master.

Fan test fails

1) Fan not rotating

1) Check and remove blocking


obstacles in the fan or change the
fan.

1) Fan LED is red


during the test

2) Fan not rotating at


correct speed

2) Check and remove blocking


obstacles in the fan or change the
fan.

2) Fan LED is red


and blinking
during the test

3) Fault in power supply


unit; some output is out of
range

3) Replace the unit.

3) Fault in power
supply

4) Short circuit in fan


supply voltage

4) In case of one power supply:


Remove the fan. If the alarm
disappears, install a new fan. If that
does not help, try to change the
power supply unit. In case of two
power supplies: Remove the fan. If
the power supply alarm disappears,
install a new fan. If this does not
help, remove the first power supply
unit. If this does not help, put it back
and remove the other one. Change
the broken power supply unit.

4) Power supply
unit has the alarm
Fault in power
supply. In case of
two power supply
units: Fault in
power supply unit
and Loss of
backup power
supply alarms are
oscillating.

1) The heating element of


(one) FXC unit is broken.

1) Replace the unit.

1) Unit function
degraded
(indicated by the
faulty unit)

2) Fault in power supply


unit

2) Change the broken power supply


unit.

2) Fault in power
supply

Heating test fails

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

Alarm

77 (116)

Commissioning and Maintenance

Table 4.
Problem

External alarm test


fails

External control
test fails

Battery connection
test fails with one
power supply

78 (116)

Troubleshooting instructions for MetroHub internal tests (Continued)

Cause

Action

Alarm

3) Short circuit in the


heating circuitry.

3) Remove FXC units one by one


and redo the test in between. When
you find the shorted FXC unit,
replace it. If you have two power
supply units, check if either one of
them works alone. If it does, replace
the shorted power unit.

3) This may be
the situation if the
Fault in the power
supply unit alarm
is also active or in
the case of two
power supplies
Fault in power
supply and Loss
of backup power
supply alarms are
oscillating.

Fault in internal circuitry or


the user has connected
external circuits to EAC
connector. Note: this test
should be done without
external circuitry
connected to EAC
connector.

Remove external alarm connections


from EAC connector. Redo the test.
If the test still fails, replace the DIUx.

Unit function
degraded

Fault in internal circuitry or


the user has connected
external circuits to EAC
connector. Note: this test
should be done without
external circuitry
connected to EAC
connector.

Remove external alarm connections


from EAC connector. Redo the test.
If the test still fails, replace the DIUx.

Unit function
degraded

1) Battery not connected


or battery damaged.

1) Connect the battery or change it if


it is damaged.

2) Battery fuse blown or


missing.

2) Install a fresh fuse in the battery.

3) Battery type sensor or


temperature sensor not
connected

3) Measure that the sensors are


connected and repair connections if
needed.

4) Break in AC supply

4) Wait until AC is available and the


battery is recharged.

5) Fault in power supply


unit

5) Replace the power supply unit.

6) Fault in power interface


unit

6) Replace the power interface unit.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

(from DIUx)

(from DIUx)

5) Fault in power
supply

DN99610738
Issue 5-0 en Draft

Troubleshooting instructions

Table 4.

Troubleshooting instructions for MetroHub internal tests (Continued)

Problem

Cause

Action

Battery connection
test fails with two
power supplies

1-4) As above

1-4) As above

5) Fault in one of the


power supply units.

5) Remove the redundant power


supply and redo the test. If the test
still fails, fault is in the master power
supply, otherwise the fault is in the
redundant power supply. Replace
the faulty power supply.

6) Fault in power interface


unit

6) Replace the power interface unit.

1-6) The same as in


battery connection test.

1-6) The same as in battery


connection test

7) Low battery voltage

7) Wait until the battery has been


recharged and the voltage is over 48
V.

Battery capacity
test fails (only in
maintenance self
tests). Note: this
test is not allowed
when there is no
AC power supply to
MetroHub or less
than a day has
passed since the
last AC cut.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

Alarm

79 (116)

Commissioning and Maintenance

80 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing alarms

Managing alarms
Nokia MetroHub Manager can monitor a number of different alarms generated by
Nokia MetroHub. The Manager is able to provide you with the following
information about any alarm that has occurred in the node (see Figure 33):

Severity classification of alarm:


-

7.1

Critical (***) = critical alarm is used to indicate a fault situation


which requires immediate measures to be taken. A critical alarm
indicates possible service degradation.
Major (**) = major alarm is used to indicate a fault situation which
requires some measures to be taken during normal working hours.
Minor (*) = minor alarm is used to indicate a fault situation which
does not require any measures to be taken by the user. The alarm is
cancelled when the fault situation is over.
Warning (w) = warning can be used to give the user information of
some event. Warning is not an alarm, and it does not indicate a fault.
The warning is not cancelled.

Location the location column shows in which unit the alarm is located.

Description a brief description of the alarm.

Time Stamp date and time when the alarm was detected.

Activation in the alarm history view, indicates if an alarm is active or


cancelled.

Reading and cancelling alarms


The unit alarm status in Equipment View is only visible when the Alarms
window is open and alarm polling is on.
To open the Alarms window, click Alarms View. The window opens and a list
of active alarms, the node structure view and the filter view are shown. To open
the alarm history view, click the Options button and in the Alarms Options
window select the View tab and tick the Alarm History View box.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

81 (116)

Commissioning and Maintenance

Active Alarms

To keep the list of active alarms updated, enable alarm monitoring by clicking
Options... Monitoring. The most critical alarms of the FXC units are shown
as bell symbols in the node structure view. The bell symbols show the colour
corresponding to the highest severity of the alarms present in the unit in question.
For example, if the most severe alarm is a critical alarm, the bell symbol is red.
When monitoring is enabled, the LED states are also updated in the Equipment
window.
You can change the time delay for the monitoring, click Options... and in the
Alarm Options window, click on the Monitoring tab and select the desired time
interval.
Filtering

In the filter view you can select different filtering options. For example, if you
only want to be notified about critical and major alarms, select only the
appropriate boxes.

Note
If the alarm(s) and the alarm history of a unit cannot be read, the state is Missing
unit in the Equipment view.

Caution
Avoid setting the alarm monitoring delay to a very small value when monitoring
a network element remotely. This places a strain on the Q1 bus resources and
causes delays for other activities.

82 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing alarms

Figure 33.

Alarms window

You can refresh both the active alarms and the alarm history by clicking the
Refresh All button in the Alarms window.
The Alarms window lists the alarm details as described previously. The alarms
are also colour-coded and their state shown symbolically as given in the following
table.

Table 5.

Colour codes of the alarms

Severity

Symbol

Colour

Critical (***)

Red

Major (**)

Orange

Minor (*)

Yellow

Warning (W)

Blue

The Location field indicates which unit or interface is producing the alarm.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

83 (116)

Commissioning and Maintenance

Table 6.

Location field

Unit

Interface

i-RRI

LIF 1...16
Flexbus 1...2

i = slot

MetroHopper
FlexiHopper

i-E1/T1

IF 1...4

Node
DIU
EAC

Input 1...10
Output 1...4

PWR 1...2
Battery
Fan
Sync setup
Hw setup
Node temperature control

You can sort the alarms by clicking on the column heading in the window. To sort
the alarms in reverse order, click a heading a second time. By default the alarms
are listed by Time.
Alarm History

Past alarms, which have occurred in the network element, are shown in the Alarm
History window (i.e. the alarm polling history). The alarm history view contains
a header that shows the location and time of the last refresh, that is, when the
currently shown events were last read.
The Activation field lists if an alarm is active or if it has been cancelled.
You can sort the alarm history by clicking the column heading in the window.
Every time the column is clicked, the sort order is reversed.
Note that the alarm history is saved as a text file with the extension .alr and has to
be opened with a text editor.
Alarm descriptions and fault codes

Alarm descriptions and fault codes are listed in Appendix A.

84 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Managing alarms

7.2

Service LEDs
In addition to the alarms that a network element can produce, most units also have
a three-colour LED indicator. These indicators display the current state of the
equipment as a quick on-site reference.

Table 7.

Transmission unit three-colour status LED

Indicator

Static

GREEN

Operation

Slow flashing

Fast flashing

Upon Masters command

Software is downloading

1);

no alarms active

YELLOW

Major or minor alarm


active

Upon Masters
command; major or
minor alarm(s) active

Software is downloading

RED

Critical alarm active

Upon Masters
command; critical alarms
active

Software is downloading

1)

Table 8.

Flexbus DC LEDs on FXC RRI

LED

Situation

No light

No power feed or Tx signal

Flashing GREEN

DC power feed to the outdoor unit active, Tx signal not active

Steady GREEN

DC power feed to the outdoor unit and Tx signal active

Table 9.

DN99610738
Issue 5-0 en Draft

When the Q1 Master unit sends the Functional Entity


Indication Command (3 kHz)

Power supply unit LED

LED

Situation

Steady GREEN

In service, output voltages OK

Flashing YELLOW

ON/standby switch in stand-by position, input voltage OK

Steady YELLOW

MetroHub in cold start state, only heating / over-heat case /


remote shut-down

Steady RED

Fault, output voltage(s) not OK

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

85 (116)

Commissioning and Maintenance

Table 10.
LED

Situation

Steady GREEN

In service

Steady YELLOW

No control from management bus

Steady RED

Fault

Flashing RED

Unit operation degraded

Table 11.

86 (116)

Fan unit LED (located on the side of the cabinet)

Interface unit LED

LED

Situation

Steady GREEN

In service

Steady YELLOW

External alarm on

Steady RED

Fault

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Upgrading

Upgrading
This chapter describes how to upgrade or alter a Nokia MetroHub configuration.

8.1

Software upgrading
The user controls the switch to a new software version with Nokia Q1 commands
via the client equipment. Any Q1 master unit may download the software. The
compatibility application in the master equipment helps the user to select the
correct software package. Before starting to use the new software packet, the
transmission unit checks its integrity and applicability (software/hardware
compatibility).
The transmission unit software is downloaded to the memory without disturbing
the transmission unit's traffic. Warm-starting the transmission unit activates the
new software. This causes a brief traffic cut in the transmission unit.
After the software package is activated, the unit automatically resets and the new
software begins running.
To support the software upgrade process, each hardware unit in the network
element contains two or more software slots. Each slot can contain a software
package, but only one of these slots may be active at a time. Software, which is
in the active state, is the currently running software in the unit. In the most
common situation, one slot contains the active software while others are either
empty or inactive.
If new software is sent to the unit, it is placed into one of the non-active slots. The
old software version remains in the transmission unit's memory. The downloaded
software is accepted only if it is valid.
Download software to a transmission unit and activate the new software with the
MetroHub Manager (see Section 8.1.1).

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

87 (116)

Commissioning and Maintenance

8.1.1

Upgrading software

To upgrade software to a unit


1.

Start the MetroHub Manager and establish a connection to the node.

2.

In the Equipment window, click the FXC unit or radio outdoor unit to be
upgraded. The FXC menu will appear in the menu bar (in front of the Tools
menu). This menu contains the Unit Software menu, offering further
options for managing the software. Select the desired unit. The Software
Management window opens.

Figure 34.

88 (116)

Software management window (FXC RRI)

3.

Select the unit to which the software is to be downloaded.

4.

Click the button, marked with three dots, at the end of the row.

5.

A standard open file dialog opens. Browse through the available files and
select the file to be downloaded.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Upgrading

6.

Click the Open button.

7.

In the Software Management window, click Download.

8.

To activate the software, click Activate when the software has


downloaded.

The download process can take some time depending on the speed of the
connection to the unit.
Software download does not cause a traffic interruption, but it slows the
management connection to the node. Activation of the new software causes a
brief traffic cut in the transmission unit.

8.2

Installing/uninstalling the units logically with the


Manager

8.2.1

Installing a new unit logically with the Manager

To install a unit logically:


1.

Open a node file (.dat) or an SCF file (.xml).

2.

Right-click the desired unit to access the Equipment window pop-up


menu.

3.

Select the Install Unit pop-up menu command.

4.

Select the type of unit to be installed.

The installed unit(s) can now be used.

To install a unit logically in the connected mode:


You can only install a unit(s) that is physically present in the connected mode.

DN99610738
Issue 5-0 en Draft

1.

Insert a new unit(s) into MetroHub.

2.

Connect to a node.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

89 (116)

Commissioning and Maintenance

3.

Right-click the desired unit to access the Equipment window's pop-up


menu.

4.

Select the Install Unit pop-up menu command.

Note
You may also insert a new unit(s) when you have already established a connection
to the node. In that case, to make the unit appear in the Equipment window, you
need to select Refresh from the Equipment window pop-up menu.

8.2.2

Uninstalling a unit logically with the Manager


You can logically uninstall a selected unit(s).

To uninstall a unit logically


1.

Connect to a node or open a node file.

2.

Point to the unit(s) to be uninstalled and click the right mouse button to
access the Equipment window pop-up menu.

3.

Select the Uninstall Unit pop-up menu command.

The unit(s) can no longer be used, and you can physically remove the unit(s).

Note
Some unit-related settings (for example: EOC, synchronisation, crossconnections) are erased when Uninstall is performed on the unit.

8.3

Removing units
WARNING
Read carefully Section Safety notes for the power system in the Installation
document before performing any maintenance tasks.

90 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Upgrading

Detailed instructions on the initial removing of the units from a new uninstalled
cabinet can be found in the Installation document.
The general work order for the removal of Nokia MetroHub units during
operation is given here.

WARNING
Risk of electric shock under the front cover of the power interface unit
(DIPx).

WARNING
Hazardous energy level under the front cover of the power interface unit
(DIPx).

To remove a unit:
1.

Uninstall the unit logically with the MetroHub Manager.

2.

Disconnect the cabling of the unit.

3.

Open the retaining screws of the unit with a T10 Torx driver and remove
the unit physically.

Note
When removing power system units, remove first the power supply unit (DSUx)
in the left slot and only then the power interface panel (DIPx). This order makes
removing easier.
4.

Install shield unit if no other unit is to be installed in the empty slot. Follow
the instructions found in the Installation document.

Note
If the FXC RRI unit is to be removed, shut down the outdoor unit power before
removing the Flexbus cable.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

91 (116)

Commissioning and Maintenance

8.4

Replacing units
Table 12 shows if it is possible to replace units physically when the power is on,
if traffic is affected by the replacing, and if the MetroHub Manager is needed
when changing units.

Table 12.

Replacing of units

Unit

Hot insert/
remove
possible

Traffic
affected

Manager
needed

Power
interface
panel

No

Yes

No

Redundant
power supply

Yes

No

Yes

Power supply
unit

Yes

Yes

No

Fan unit

Yes

No

No

Interface unit

Yes

No

No

Battery unit

Yes

No

Yes

New FXC unit

Yes

No

Yes

Replaced FXC
unit

Yes

Yes

Yes

Note

When added
or inserted into
another slot

User gives
new ID
information

Note
If a master unit is removed, all traffic going through the node is cut.
If a slave unit is removed, only the traffic going through that particular unit is cut.

8.4.1

Replacing a unit with a unit of the same type


If a unit is faulty, for example, you can replace it with another unit of the same
type by removing the faulty unit and then inserting a replacement unit.

92 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Upgrading

After this, use the Restore Backup Settings feature to update the settings of the
replaced unit into the new unit from the previously saved backup file.
If the backup file, node offline file, or site configuration file does not correspond
to the current settings, you have to reconfigure the settings manually.

Note
If the replacement unit has been used previously, it must be set to factory defaults.

To make a backup file:


1.

Click once all the units present in the Equipment view to ensure that all
settings are read from the FXC units.

2.

Create a backup file of all units, select File Save As...

3.

After creating the backup file you can replace the faulty unit.

To replace a slave (other than slot 1) unit:


1.

Remove the slave unit without uninstalling it, and insert the new unit. This
way, the cross-connections and other node settings made to the unit you
want to replace are not removed.

2.

Select Maintenance Restore Backup Settings... and select the backup


file, node offline file (with the extension .dat) or site configuration file
(with the extension .xml). See Figure 29.

3.

Select only the unit to which the settings should be sent.

4.

Click Send.

Note
The Restoring backup settings feature requires that the equipping of the
transmission units in MetroHub matches the node file. You cannot add or remove
units while using the Restore Backup Settings -command

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

93 (116)

Commissioning and Maintenance

To replace the master (slot 1) unit


1.

Remove the master unit without uninstalling it, and insert the new unit. All
node settings are saved in the master unit, thus, in this case the node
settings as well as the master unit settings must be restored from the backup
file.

2.

Reset the node to factory default settings from Maintenance -> Resets...
and after this, install the units with the Install all command.

3.

Select Maintenance -> Restore Backup Settings... and select the backup
file, node offline file (with the extension .dat), or site configuration file
(with the extension .xml). See Figure 29.

4.

Choose Select all so that all settings will be sent.

5.

Click Send.

Note
The Restoring backup settings feature requires that the equipping of the
transmission units in MetroHub matches the node file. You cannot add or remove
units while using the Restore Backup Settings -command

8.4.2

Replacing a unit with a unit of a different type

To replace a unit with a unit of a different type, using the Manager:

94 (116)

1.

Connect to a node or open a node file.

2.

Point to the unit to be replaced and click the left mouse button to access the
Equipment window pop-up menu.

3.

Select the Uninstall Unit pop-up menu command.

4.

The uninstalled unit can no longer be used and it can be physically


removed.

5.

Install a new unit.

6.

Click the Refresh button to read all data from the node. The new unit
should be displayed with diagonal stripes.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Upgrading

7.

Click the right mouse button to access the Equipment window pop-up
menu.

8.

Select the Install Unit pop-up menu command.

Check the settings, and the new unit is ready for use.

8.5

Adding units

To add a unit:

8.6

1.

Remove the shield unit from the slot where you want to add the unit. (This
step is not applicable to the battery unit).

2.

Install the new unit.

3.

Connect the cabling. (The power supply unit does not have a cable.)

4.

Install the unit logically with MetroHub Manager. See Section 8.2.1.

Changing a battery backup unit

To change a battery backup unit:


Note
Ensure that there is no battery capacity test going on when changing the battery.

DN99610738
Issue 5-0 en Draft

1.

Uninstall and replace the old battery.

2.

Install the new battery logically.

3.

Run the battery connection test from Maintenance Tests...

4.

Give new battery identifications from Configuration Identifications...


power folder.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

95 (116)

Commissioning and Maintenance

96 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Appendix A.
A.1

Alarm descriptions
The tables below list the alarms detected by MetroHub Manager and show how
the nodes react to the alarms: classification of alarms and consequences. Each
table also gives a short description of the fault generating the alarm and provides
some guidelines on how to remedy the fault.
The alarms are presented in alphabetical order according to the long alarm names.
The alarm tables give the following information:

A.1.1

Title row shows the alarm name.

Severity shows the severity class of the alarm as it appears in the Node
Manager.

Unit shows the unit indicating the alarm.

Fault code shows both the decimal and hexadecimal fault codes.

Consequence shows whether an indication signal is sent upstream or


downstream.

Meaning gives the possible cause of the alarm.

Instructions give instructions on how to remedy the fault.

Cancelling gives instructions on how the alarm is cancelled.

MetroHub node alarms

Active alarm point


Severity: Major

Unit: EAC input 1...10

Fault code: 240

Consequence:

Meaning: External alarm active; user-defined alarm ON or EAC incorrectly defined.


Instructions: Check that the definition is correct and external circuitry works correctly.
Cancelling:

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

97 (116)

Commissioning and Maintenance

Blocked from use


Severity: Major

Unit: Cross-connection bank

Fault code: 20

Consequence:

Meaning: A cross-connection bank has pending cross-connections. This happens


when a node has a cross-connection terminated in an interface, which is not in use, or
when Flexbus capacity has been reduced so that the interfaces that had crossconnections connected are no longer available. The cross-connections are also set to
pending state if a slave unit with cross-connections is removed without uninstalling it.
In these cases the cross-connection remains in the cross-connection bank, but is not
set in the hardware.
Instructions: Check that all interfaces that have cross-connections created are in use,
or remove cross-connections that are connected to non-existing interfaces, or
increase Flexbus capacity to match the created cross-connections. Reinstall the
removed unit(s).
Cancelling: Automatically cancelled when there are no blocked cross-connections.

Charger alarm
Severity: Major

Unit: Power supply 1/2

Fault code: 13

Consequence: Battery will not be charged.

Meaning: Power supply unit is not capable to charge the battery. As a result, battery
backup power supply will eventually be lost.
Instructions: Change the power supply unit and/or battery. Check that there is no short
circuit connected to power interface units DC output. Check also the cable between
the power interface and the battery.
Cancelling:

Database full
Severity: Warning

SB type: Unit

Fault code: 162

Consequence:

Meaning: Fault management event history database is full. New events are not
recorded into database. This happens when the poller (NMS/BSC) is unable to poll
the unit and thus clear the alarm history.
Instructions: Make sure that polling is working.
Cancelling:

98 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Equipment door open


Severity: Minor

Unit: Node

Fault code: 168

Consequence:

Meaning: Node cover has not been installed.


Instructions: Cover should be closed whenever node is in normal operation to ensure
air flow and environmental protection. Cover moves the "switch" magnet towards DIU
sensor when the cover is installed normally in the correct position.
Cancelling:

Fault in installation of equipment


Severity: Critical

Unit: HW setup

Fault code: 142

Consequence:

Meaning: FE/Unit in cabinet is of wrong type.


Instructions: Uninstall the wrong type unit or run "Install all" command. Also an earlier
type of unit can be changed to the slot.
Cancelling:

Fault in power supply


Severity: Critical

Unit: Power supply 1/2

Fault code: 0

Consequence: Some function may not work in the node.

Meaning: Fault in power supply


Instructions: Some of the power output voltages are not in the defined range. Power
supply has to be changed.
Cancelling:

Fault in unit

DN99610738
Issue 5-0 en Draft

Severity: Critical

Unit: Fan unit

Fault code: 150

Consequence: Cooling of the node not working.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

99 (116)

Commissioning and Maintenance

Fault in unit
Meaning: Fault in the fan
Instructions: Remove the fan and remove possible obstacles. If not applicable, replace
the fan with a new one.
Cancelling:

Frequency error
Severity: Major

Unit: Sync setup

Fault code: 112

Consequence:

Meaning: None of the Rx or external clock sources defined in the timing priority list is
valid, or the Rx source signal in use has its MCB in state "1".
Instructions:
Cancelling:

Loss of backup power supply


Severity: Major

Unit: Power supply 1/2

Fault code: 2

Consequence: Power supply redundancy lost

Meaning: All output voltages OK, redundant supply in alarm


Instructions: Change the redundant supply which has the red LED active.
Cancelling:

Loss of outgoing signal


Severity: Major

Unit: FXC unit

Fault code: 32

Consequence:

Meaning: In the MetroHub signal test, the received signal was lost. Some unit is not
functioning properly.
Instructions: Find the broken unit and replace it.
Cancelling:

100 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Loss of synchronisation signal(s)


Severity: Critical

Unit: Sync setup

Fault code: 125

Consequence:

Meaning: All sync sources from priority list are unavailable.


Instructions:
Cancelling:

Low battery voltage


Severity: Major

Unit: Battery unit

Fault code: 8

Consequence: Battery back-up capability is not good


anymore.

Meaning: Power supply unit has performed the battery test and the result is Average
capacity.
Instructions: Battery capacity has decreased. Check that there has not been an AC
failure within 24 hours to ensure that the battery has been full before testing.
Cancelling:

No connection
Severity: Critical

Unit: Trunet

Fault code: 62

Consequence:

Meaning: Enabling Trunet has failed because the cross-connection capacity required
is not free.
Instructions: Disable Trunet and remove the connections that are using the capacity
needed for Trunet. After performing this action, re-enable Trunet.
Cancelling:

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

101 (116)

Commissioning and Maintenance

Subrack has excessive units


Severity: Major

Unit:
1) HW setup
2) FAN
3) Power supply 1/2
4) Battery

Fault code: 140

Consequence:

Meaning: The unit is not installed.


Instructions: Install the unit.
Cancelling:

Subrack is missing units


Severity:

Unit:

1) Critical

1) HW setup

25) Major

2) DIU
3) FAN
4) Power supply 1/2
5) Battery

Fault code: 139

Consequence:

Meaning: The unit is logically installed, but has been either removed or broken.
Instructions: Uninstall the removed unit or replace the broken unit.
Cancelling:

Synchronising fault in clock recovery


Severity: Major

Unit: Sync setup

Fault code: 124

Consequence:

Meaning: A missing synchronisation input clock signal with a priority on the


synchronisation list.
Instructions:
Cancelling:

102 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Temperature alarm
Severity:

Unit:

1) Critical

1) Node temperature control

23) Major

2) FXC unit
3) Power supply

Fault code: 145

Consequence:

Meaning:
1) Alarm of exceeded ambient temperature range (<-42C or > 52C)
2) Unit temperature is < -12C.
3) Power supply unit has overheated; will be shut off within one minute.
Instructions: 12) Do not cause immediate danger to operation. 3) Overheat case in
power supply. The power cut will last 5-15 minutes.
Cancelling:

Test generator on
Severity: Major

Unit: FXC unit

Fault code: 25

Consequence:

Meaning: User has activated the signal test generator on the unit.
Instructions:
Cancelling: Quit the test.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

103 (116)

Commissioning and Maintenance

Test mode active


Severity: Minor

Unit:
1) Power supply 1
2) DIU
3) Fan unit
4) Battery unit

Fault code: 23

Consequence:

Meaning:
1) Heating test activated by user.
2) External alarm connectors / external control connectors test active
3) User-activated or fan test active
4) User-activated or battery test ongoing
Instructions: Wait for the test to be performed.
Cancelling:

Total loss of power supply


Severity: Minor

Unit: Power supply 1/2

Fault code: 1

Consequence:

Meaning: Power system using internal back-up


Instructions: The back-up time before shut down depends on the configuration.
Cancelling:

104 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Unit function degraded


Severity:

Unit:

1-5) Major

1) DIU

6) Minor

2) FXC unit
3) EAC input
4) Control output
5) Fan unit
6) Battery unit

Fault code: 126

Consequence:

Meaning: 1) DIU heating test failed


2) Unit heating test failed
3) Alarm input is not working normally.
4) Control output interface is not working normally.
5) Fan performance degraded to 80% of normal.
6) Power supply unit has performed the battery test -> result is Low capacity.
Instructions: Change the unit, although there is no major effect on node operation.
Cancelling:

Version mismatch
Severity: Critical

Unit: HW set up

Fault code: 221

Consequence:

Meaning: Node master unit in slot 1 is not compatible with other FXC-unit(s).
Instructions: Update slave unit SW.
Cancelling: Check that all FXC units are SW and HW compatible. Use the ITN
compatibility table for HW and SW. Change incompatible HW and/or download and
activate compatible SW.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

105 (116)

Commissioning and Maintenance

A.1.2

FXC RRI unit alarms

AIS 2M
Severity: Major

Unit: Platform interface

Fault code: 66

Consequence: FEA alarm (TS0/B3) generated to far end.

Meaning: Alarm signal is received, the received signal has no framing and it is all
ones.
Instructions: The signal is cut somewhere in the network and AIS replacement has
taken place. Follow the 2M signal in the network to find out the place where AIS
replacement has been done. This link is usually faulty or has configuration errors.
Other alarms may cause this alarm because of AIS switching in the receiving direction
as shown in the Consequence field of some alarms.
Cancelling:

Alarm signal received


Severity: Critical

Unit: Flexbus

Fault code: 64

Consequence:
AIS is connected to all received Flexbus channels. This
will cause AIS 2 Mbit/s alarm to all used platform
interfaces that are connected to the alarming Flexbus
interface.

Meaning: OU has lost the frame lock and it has replaced the frame with a pseudo
frame to ensure IU - OU communication.
Instructions: The signal may be faded in the radio path. In this case the OU has the
Loss of incoming radio signal alarm. If this is not active in the OU, check the radios at
both ends of the hop. They must have the right configuration (frequency, interleaving
and tx power on). Check also that the same capacity has been selected for both ends
of the hop.
Cancelling: If the radio signal is faded, it will come back when the fading stops. If the
OU is FlexiHopper, check the maximum tx power setting. If a stronger tx power is
allowed, it will withstand fading better.

106 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Equipment reset
Severity: Warning

Unit: unit

Fault code: 148

Consequence:

Meaning: Unit is starting up after power-on or reset.


Instructions:
Cancelling:

Error rate > 1 E-3


Severity: Critical

Unit:
1) Flexbus
2) Platform interface

Fault code: 99

Consequence:
1) AIS is connected to all received Flexbus channels.
2) AIS is connected to the receiving direction of the
platform interface.
2) FEA alarm (TS0/B3) generated to far end.

Meaning:
1) Received signal bit error rate is worse than 1.0 * 10-3
2) Received platform interface error rate is worse than 1.0 * 10-3
Instructions:
1) -Alarm signal received causes also this alarm
- Signal may be faded in the radio path or antenna alignment has changed.
2) - If the Flexbus where this interface has been connected has the same alarm, see
its instructions.
- If Flexbus does not have this alarm, use loop to equipment for both the platform
interface and the Flexbus. If either of the loops gives this alarm, replace the unit.
Cancelling: If the radio signal is faded, it will be restored when the fading stops. If
antenna alignment has changed, align the antennas according to the instructions in
the radio documentation.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

107 (116)

Commissioning and Maintenance

Error rate > 1 E-6


Severity:

Unit: Platform interface

Major
Fault code: 102

Consequence:

Meaning: Received platform interface error rate is worse than 1.0 * 10-6
Instructions: Most probably radio path fading causes this. If it persists for a long time,
use loop to equipment for both the platform interface and Flexbus. If either of the loops
gives this alarm, replace the unit.
Cancelling:

Far-end alarm
Severity: Major

Unit: Platform interface

Fault code: 179

Consequence:

Meaning: Far end has lost frame alignment.


Instructions: Check the signal flow from the transmit direction of the alarming interface
to the far end.
Cancelling:

Fault in power supply


Severity: Critical

Unit: Flexbus

Fault code: 0

Consequence: AIS is connected to all received Flexbus


channels.

Meaning: Flexbus overcurrent protection circuit has cut off +55 V power feed.
Instructions: Check the OU cabling, remove short circuits and connect the power feed
back with the Manager. Note: it is recommended to switch the DC power feed off
when connecting OU to the Flexbus interface. If the OU is connected to a Flexbus
interface with the DC power feed on, the overcurrent protection may cut the power
feed.
Cancelling:

108 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Loop to equipment
Severity: Major

Unit:
1) Flexbus
2) Platform interface

Fault code: 22

Consequence:
1) AIS is connected to all transmitted Flexbus channels in
the receiving equipment.
2) AIS is connected to the transmit direction of the looped
interface. TX AIS generated.

Meaning:
1) Flexbus loop to equipment is active. The whole transmitted Flexbus signal is
looped back to IU. The IU - OU communication is cut during the loop.
2) Platform interface loop to equipment is active. The whole transmitted platform
interface signal is looped back to the IU.
Instructions:
Cancelling: A loopback will be removed automatically after a control timeout has
expired. A loop can also be removed with the Manager by setting the interface or
Flexbus back to the normal state.

Loop to interface
Severity: Major

Unit:
1) Flexbus
2) Flexbus channel
3) Platform interface

Fault code: 21

DN99610738
Issue 5-0 en Draft

Consequence: 1) AIS is connected to all received


Flexbus channels. 2) AIS is connected to the receiving
direction of the looped channel. 3) AIS is connected to
the receiving direction of the looped interface.

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

109 (116)

Commissioning and Maintenance

Loop to interface
Meaning:
1) Flexbus interface loop is active. The whole received Flexbus signal is looped back
to the OU (or another IU). The IU - OU communication will be cut during the loop.
2) Flexbus channel loop to interface is active. The whole received Flexbus signal is
looped back to the OU (or another IU).
3) Platform interface loop to interface active. The whole received platform signal is
looped back to the OU (or another IU) without regenerating time slot 0.
Instructions:
Cancelling: A loopback will be removed automatically after a control timeout has
expired. A loop can also be removed with the Manager by setting the interface,
channel or Flexbus back to the normal state.

Loss of CRC multiframe alignment


Severity: Critical

Unit: Platform interface

Fault code: 86

Consequence:
AIS is connected to the receiving direction of the
platform interface.
FEA alarm (TS0/B3) generated to far end.

Meaning: Platform interface has lost CRC frame alignment.


Instructions: Check that the other end of the link has CRC in use. Use the same
instructions as in the Loss of frame alignment alarm to locate the fault.
Cancelling:

Loss of frame alignment


Severity: Critical

Unit:
1) Flexbus
2) Platform interface

Fault code: 81

Consequence: 1) AIS is connected to all received


Flexbus channels
2) AIS is connected to the receiving direction of the
platform interface. FEA alarm (TS0/B3) generated to far
end.

110 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Loss of frame alignment


Meaning: 1) IU has lost frame alignment
2) Platform interface has lost frame alignment.
Instructions:
1) Check in the Configuration view that all installed units are present. A faulty OU
may not be present in the view. Try connecting power feed off and back on. If the OU
does not stay present, replace it.
Check that radios are configured correctly (no configuration error or fault in unit
alarms). If the receiving level is good enough, check that:
a) Both ends of the hop are set to the same capacity
b) Flexbus interfaces are in use
c) The OU's interleaving settings are the same at both ends of the hop.
Check with Flexbus loop to equipment if the IU locks to its own signal. If not, replace
the IU.
2) - Check in the Cross-connections view that the right signal is connected to this
interface at both ends of the hop.
Use a platform interface loop to equipment to check that the platform interface locks
to its own transmit signal. If not, replace the unit.
Use Flexbus loop to equipment and check that the platform interface locks to its
own signal. If not, replace the unit.
Cancelling:

Loss of incoming 2M signal


Severity: Critical

Unit: Platform IF

Fault code: 50

Consequence: FEA alarm (TS0/B3) generated to far end


AIS to RX direction.

Meaning: RX clock is missing


Instructions:
Cancelling:

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

111 (116)

Commissioning and Maintenance

A.1.3

FXC E1/T1 unit alarms

AIS 2M
Severity: Major

Unit: E1 interface

Fault code: 66

Consequence: FEA alarm (TS0/B3) generated to far end.

Meaning: Alarm signal is received; the received signal has no framing and it is all
ones.
Instructions: The signal is cut somewhere in the network and AIS replacement has
taken place. Follow the 2M signal in the network to find out the place where AIS
replacement has been done. This link is usually faulty or has configuration errors.
Other alarms may cause this alarm because of AIS switching in the receiving direction
as shown in the Consequence field of some alarms.
Cancelling:

AIS 1.5M
Severity: Major

Unit: T1 interface

Fault code: 73

Consequence: FEA alarm (TS0/B3) generated to far end.

Meaning: Alarm signal is received; the received signal has no framing and it is all
ones.
Instructions: The signal is cut somewhere in the network and AIS replacement has
taken place. Follow the 2M signal in the network to find out the place where AIS
replacement has been done. This link is usually faulty or has configuration errors.
Other alarms may cause this alarm because of AIS switching in the receiving direction
as shown in the Consequence field of some alarms.
Cancelling:

Equipment reset
Severity: Warning

SB type: unit

Fault code: 148

Consequence:

Meaning: Unit is starting up after power-on or reset.


Instructions:
Cancelling:

112 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Error rate > 1 E-3


Severity: Critical

Unit: E1 and T1 interface

Fault code: 99

Consequence: FEA alarm (TS0/B3) generated to far end


AIS to RX direction.

Meaning: Received signal bit error rate is worse than 1.0 * 10-3
Instructions:
Cancelling:

Error rate > 1 E-6


Severity: Minor

Unit: E1 and T1 interface

Fault code: 102

Consequence:

Meaning: Received signal bit error rate is worse than 1.0 * 10-6
Instructions:
Cancelling:

Far-end alarm
Severity: Major

Unit: E1 interface

Fault code: 179

Consequence:

Meaning: Sent by the equipment in the far-end (TS0/B3), and indicates a serious fault
in the received signal of the far-end equipment.
Instructions:
Cancelling:

Loop to equipment
Severity: Major

Unit: E1 and T1 interface

Fault code: 22

Consequence: AIS to TX direction.

Meaning: User has activated an equipment loop


Instructions:
Cancelling:

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

113 (116)

Commissioning and Maintenance

Loop to interface
Severity: Major

Unit: E1 and T1 interface

Fault code: 21

Consequence: AIS to RX direction.

Meaning: User has activated an interface loop


Instructions:
Cancelling:

Loss of CRC multiframe alignment


Severity: Critical

Unit: E1 interface

Fault code: 86

Consequence:
AIS is connected to the receiving direction of the
platform interface.
FEA alarm (TS0/B3) generated to far end.

Meaning: Platform interface has lost CRC alignment.


Instructions: Check that the other end of the link has CRC in use. Use the same
instructions in the loss of frame alignment to locate the fault.
Cancelling:

Loss of frame alignment


Severity: Critical

Unit: E1 and T1 interface

Fault code: 81

Consequence: FEA alarm (TS0/B3) generated to far end


AIS to RX direction.

Meaning:
Instructions:
Cancelling:

114 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft

Loss of incoming 1.5M signal


Severity: Critical

Unit: T1 interface

Fault code: 56

Consequence: Yellow alarm generated to far end AIS to


RX direction.

Meaning:
Instructions:
Cancelling:

Loss of incoming 2M signal


Severity: Critical

Unit: E1 interface

Fault code: 50

Consequence: FEA alarm (TS0/B3) generated to far end


AIS to RX direction.

Meaning:
Instructions:
Cancelling:

Yellow alarm
Severity: Major

Unit: T1 interface

Fault code: 172

Consequence: AIS to RX direction

Meaning: Sent by the equipment in the far-end, and indicates a serious fault in the
received signal of the far-end equipment.
Instructions:
Cancelling:

A.1.4

Radio unit alarms


Details for FlexiHopper and MetroHopper alarms can be found in the
corresponding user manuals: Nokia MetroHopper Radio with FC RRI/FXC RRI
User Manual, Commissioning and Maintenance; and Nokia FlexiHopper
Microwave Radio with FXC RRI User Manual, Commissioning and
Maintenance.

DN99610738
Issue 5-0 en Draft

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

115 (116)

Commissioning and Maintenance

116 (116)

Nokia Corporation
Nokia Proprietary and Confidential

Internal Copy

DN99610738
Issue 5-0 en Draft