FPMR 2.4 Oper Maint

FlexiPacket MultiRadioRel. 2.4

Operate and Maintain

A25000-A1600-B019-01-76P1

Issue: 1 Issue date: October 2011

2 A25000-A1600-B019-01-76P1Issue: 1 Issue date: October 2011


The information in this document 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 Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks 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 are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMEN-TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2011. All rights reserved.

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.

A25000-A1600-B019-01-76P1Issue: 1 Issue date: October 2011

3


Table of ContentsThis document has 67 pages.

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.5 Waste electrical and electronic equipment (WEEE) . . . . . . . . . . . . . . . . 91.6 RoHS compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.7 Safety instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.7.1 RF Energy Health Hazard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.7.2 Protection against Lightning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.7.3 Protection from RF Burns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.7.4 Warning – Turn off all power before servicing . . . . . . . . . . . . . . . . . . . . 12

2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.1 How to enter the FlexiPacket MultiRadio . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1 Alarms Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2 Alarm condition (menu Equipment > System Status) . . . . . . . . . . . . . . 173.3 Display of Alarms (Alarm menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.4 Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4 Test Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.1 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.1.1 LL4 (IDU-ODU cable test loopback) . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.1.2 LL1 (RF loopback) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.1.3 Link Test loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.2 Timed Tx Squelch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

5 Measurement management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.1 Port Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315.1.1 How to check the errors on the Ethernet cable after a long recording of traf-

fic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.1.2 Reset the counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345.2 RF & Others . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

6 Export Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366.1 How to export the report files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

7 Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387.1 RSPI Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387.1.1 Setting of the RSPI Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397.1.2 Displaying of the RSPI Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407.2 ACM Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437.2.1 Displaying of the ACM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437.3 Ethernet Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467.3.1 Displaying of the Ethernet Performances . . . . . . . . . . . . . . . . . . . . . . . 46



8 Administration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498.1 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498.2 Product and Software menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518.2.1 Software Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518.2.2 Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518.2.3 Product Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548.3 License Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558.4 Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568.5 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578.5.1 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578.5.2 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

9 Licence management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609.1 Instructions for fetching license key from CLicS system. . . . . . . . . . . . . 609.2 Support for Target ID swap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609.3 Troubleshooting instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649.4 Contact & Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669.5 How to test SMS connectivity with CLicS system . . . . . . . . . . . . . . . . . . 669.6 Contact information for help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67


5


List of FiguresFigure 1 WEEE label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Figure 2 Open NE screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Figure 3 FlexiPacket MultiRadio - Main view . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 4 System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 5 Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 6 Display of Alarms (1+0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 7 Display of Alarms (1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 8 Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 9 Test Functions (1+0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Figure 10 IDU-ODU Cable Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 11 RF Self Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 12 Link Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 13 Timed Tx Squelch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 14 Measurements menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Figure 15 Ethernet counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 16 LLDP Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Figure 17 Export Data menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 18 Destination directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 19 Exporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 20 Setting of the RSPI Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 21 Displaying of the RSPI Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 22 Displaying of the RSPI Rx Performance (Quarter) . . . . . . . . . . . . . . . . 41Figure 23 Displaying of the RSPI Rx Performance (Daily). . . . . . . . . . . . . . . . . . . 41Figure 24 Displaying of the RSPI Tx Performance (Quarter). . . . . . . . . . . . . . . . . 42Figure 25 Displaying of the RSPI Tx Performance (Daily) . . . . . . . . . . . . . . . . . . . 42Figure 26 Displaying of the ACM Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Figure 27 Displaying of the ACM Rx Performance (Quarter). . . . . . . . . . . . . . . . . 44Figure 28 Displaying of the ACM Rx Performance (Daily) . . . . . . . . . . . . . . . . . . . 44Figure 29 Displaying of the ACM Tx Performance (Quarter) . . . . . . . . . . . . . . . . . 45Figure 30 Displaying of the ACM Tx Performance (Daily) . . . . . . . . . . . . . . . . . . . 45Figure 31 Ethernet performances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Figure 32 Displaying of the Ethernet Performance . . . . . . . . . . . . . . . . . . . . . . . . 47Figure 33 Displaying of the GbE Performance (Quarter) . . . . . . . . . . . . . . . . . . . . 47Figure 34 Displaying of the GbE Performance (Daily) . . . . . . . . . . . . . . . . . . . . . . 48Figure 35 Displaying of the Radio Performance (Quarter). . . . . . . . . . . . . . . . . . . 48Figure 36 Displaying of the Radio Performance (Daily) . . . . . . . . . . . . . . . . . . . . . 48Figure 37 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 38 Account Log Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 39 Equipment Software Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 40 Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 41 Product Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 42 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 43 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 44 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Figure 45 View Last Restore Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59



List of TablesTable 1 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Table 2 List of symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Table 3 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 4 User class default password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Table 5 Not supported configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Table 6 Ingress counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Table 7 Egress counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Table 8 Protection counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Table 9 LLDP counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Table 10 RSPI Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Table 11 Input performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Table 12 Output performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Table 13 Troubleshooting instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64


7

Operate and Maintain Preface

1 PrefaceThis document provides the information to operate and maintain the FlexiPacket Multi-Radio.

1.1 Intended audienceThis document is intended to the Operators in charge to operate and maintain the Flex-iPacket MultiRadio.

1.2 Structure of this documentThe document is divided into the following main chapters:

1.3 Symbols and conventionsThe following symbols and mark-up conventions are used in this document:

Chapter Title Subject

Chapter 1 Preface Provides an introduction to the document and the safety instructions

Chapter 2 Overview Provides the list of the operations and the instructions to enter the FlexiPacket MultiRadio by the WebLCT

Chapter 3 Alarm management Provides the information regarding the alarm management

Chapter 4 Test Functions Provides the list of the tests to be done to verify the correct operation of the FlexiPacket MultiRadio

Chapter 5 Measurement management Provides the information regarding the measurement management

Chapter 6 Export Data Provides the information to download the report files

Chapter 7 Performance management Provides the information regarding the performance management

Chapter 8 Administration tasks Provides the information regarding the tasks normally performed by the Admin-istrator

Chapter 9 Licence management Provide the information regarding the use of the Licence Manager tool to upgrade the licence

Table 1 Structure of this document


Operate and MaintainPreface

Representation Meaning

fDANGER!

fWARNING!

fCAUTION!

A safety message indicates a dangerous situation where personal injury is possible.

The keywords denote hazard levels with the following meaning:

DANGER! - Indicates a hazardous situation which, if not avoided, will result in death or serious (irreversible) personal injury.

WARNING! - Indicates a hazardous situation which, if not avoided, could result in death or serious (irreversible) personal injury.

CAUTION! - Indicates a hazardous situation which, if not avoided, may result in minor or moderate (reversible) personal injury.

w NOTICE: A property damage message indicates a hazard that may result in equipment damage, data loss, traffic interruption, and so on.

g A note provides important information related to the topic, for example, not obvious exceptions to a rule or side effects.

t A tip provides additional information related to the topic which is not essential in the context, but given for convenience.

Bold • All names of graphical user interface (GUI) objects, such as windows, field names, buttons, and so on.Example: Select the Full Screen check box and press OK.

• Terms and abbreviations which are linked to an entry in the glossary and list of abbreviations respectively

• Important key words

Italic • Files, folders, and file system paths.Example: /usr/etc/sbin/ftpd.exe

• Emphasized words

typewriter • Input to be typed in a command line or a GUI field.Examples:ping -t 192.168.0.1Enter World in the Domain field.

• Output from a command, error messages, content of a status line, and so on

• File content, such as program sources, scripts, logs, and settings

<angle brackets> Placeholders, for example as part of a file name or field value.

Examples:<picture name>.png or <ip address>:<port number>

Table 2 List of symbols and conventions


9


Screenshots of the graphical user interface are examples only to illustrate principles. This especially applies to a software version number visible in a screenshot.

1.4 History of changes

1.5 Waste electrical and electronic equipment (WEEE)All waste electrical and electronic products must be disposed of separately from the municipal waste stream via designated collection facilities appointed by the government or the local authorities. The WEEE label (see Figure 1) is applied to all such devices.

[square brackets] A key to be pressed on a PC keyboard, for example [F11].

Keys to be pressed simultaneously are concatenated with a “+” sign, for example [CTRL]+[ALT]+[DEL].

Keys to be pressed one after another are concatenated with spaces, for example [ESC] [SPACE] [M].

> The greater than symbol “>” is used to concatenate a series of GUI items in order to depict a GUI path. This is an abridged pre-sentation of a procedure to be carried out in order to perform an action or display a window or dialog box.

Examples:

A simple menu path: File > Save as ...A more complex GUI path:> Nokia Siemens Networks TransNet window > File menu > Change Password command > Change Password dialog box

x(in card names)

For convenience, card names are sometimes listed with a lower case x variable, in order to concisely represent multiple cards.

Example:

I01T40G-x (is to be interpreted as I01T40G-1 and I01T40G-2)

Representation Meaning

Table 2 List of symbols and conventions (Cont.)

Issue Issue date Remarks

1 October 2011 1st version

Table 3 History of changes



Figure 1 WEEE label

The correct disposal and separate collection of waste equipment will help prevent poten-tial negative consequences for the environment and human health. It is a precondition for reuse and recycling of used electrical and electronic equipment.

For more detailed information about disposal of such equipment, please contact Nokia Siemens Networks.

The above statements are fully valid only for equipment installed in the countries of the European Union and is covered by the directive 2002/96/EC. Countries outside the European Union may have other regulations regarding the disposal of electrical and electronic equipment.

1.6 RoHS complianceFlexiPacket MultiRadio complies with the European Union RoHS Directive 2002/95/EC on the restriction of use of certain hazardous substances in electrical and electronic equipment.

The directive applies to the use of lead, mercury, cadmium, hexavalent chromium, poly-brominated biphenyls (PBB), and polybrominated diphenylethers (PBDE) in electrical and electronic equipment put on the market after 1 July 2006.

Materials usage information on Nokia Siemens Networks Electronic Information Products imported or sold in the People’s Republic of ChinaFlexiPacket MultiRadio complies with the Chinese standard SJ/T 11364-2006 on the restriction of the use of certain hazardous substances in electrical and electronic equip-ment. The standard applies to the use of lead, mercury, cadmium, hexavalent chro-mium, polybrominated biphenyls (PBB), and polybrominated diphenyl ethers (PBDE) in electrical and electronic equipment put on the market after 1 March 2007.

1.7 Safety instructionsIn this paragraph are indicated all the safety rules and the precautionary measures to follow while carrying out operations on the equipment in order to prevent injuries to per-sonnel and/or damages to the equipment components.

t PLEASE READ THESE SAFETY PRECAUTIONS!


11


1.7.1 RF Energy Health Hazard

This symbol indicates a risk of personal injury due to radio frequency exposure.

The radio equipment described in this guide uses radio frequency transmitters.

No one shall be allowed to come in the close proximity of the antenna's front while the transmitter is operating. The antenna will be professionally installed on the outdoor per-manent fix-mounted structures in order to keep it separate from any other antenna and from everybody else.

f WARNING!RF Energy Exposure Limits and Applicable Rules for 6-38 GHz. It is recommended that for each radio equipment deployment site the radio equipment operator refers to the RF exposure rules and precaution for each frequency band and to all other applicable rules and precautions with respect to transmitters, facilities, and operations that may affect the environment due to the RF emissions.Appropriate warning signs must be properly placed and affixed at the equipment site and access entries.

1.7.2 Protection against Lightning

Article 810 of the US National Electric Department of Energy Handbook 1996 specifies that radio and television lead-in cables must have adequate surge protection at or near the point of entry to the building. The code specifies that any shielded cable from an external antenna must have the shield directly connected to a 10 AWG wire that connects to the building ground electrode.

Do not turn on power before reading product documentation. This device has a -48 VDC direct current input.

1.7.3 Protection from RF BurnsIt is dangerous to stare into or stand in front of an active antenna aperture. Do not stand in front of or look into an antenna without first ensuring that the associated transmitter or transmitters are switched off. Do not stare into the waveguide port of an ODU (if appli-cable) when the radio is active.



1.7.4 Warning – Turn off all power before servicing

f WARNING!Turn off all power before servicing.


13

Operate and Maintain Overview

2 OverviewThis manual explains the operations, that an Operator normally can perform by the LCT to detect the normal operating conditions or the malfunctions, if any, of the FlexiPacket MultiRadio.

The manual is divided in:

• Alarm management (Chapter 3) • Test Functions (Chapter 4) • Measurement management (Chapter 5) • Export Data (Chapter 6) • Performance management (Chapter 7) • Administration tasks (Chapter 8) • Licence management (Chapter 9)

To open the Craft Terminal and to enter the FlexiPacket MultiRadio follow the instruc-tions given in Chapter 2.1.

2.1 How to enter the FlexiPacket MultiRadioSteps

1 Open the Web browser.

2 Enter http:\\ NE IP address

3 The Java authentication screen opens.

Figure 2 Open NE screen

4 Enter:

• User name: xxxxxx • Password: xxxxxx

and click on OK.

The following 3 User Classes are available:

• Read Only User: This is the lower Class. Any user of this Class cannot modify whatever parameter in the network element, but registration data for receiving notifications. All the other MIB fields are read only.


Operate and MaintainOverview

• Read & Write User: Any user of this Class may read and write all the MIB fields whose property list is READWRITE, unless: • change IP parameters of the NE; • set date and time; • modify SNMP Community identifiers; • modify Users or other administrative data; • perform software download and restore or bulk commit operations (via FTP);

• Admin User: Any user of this Class has read write access to the complete set of MIB fields. Moreover, this Class can change passwords for itself and for the lower Class Users, and can enable/disable all.

Default values are listed in Table 4.

t After the first launch you can install a shortcut into the desktop through the Java Control Panel.

5 The Main view opens.

Figure 3 FlexiPacket MultiRadio - Main view

User name Password

admin sysmanager

readwrite readwrite

readonly readonly

Table 4 User class default password


15

Operate and Maintain Overview

The System Status menu (shown in Figure 4) gives a summary of the status of the equipment.

• Application typeRead-only field: Full Packet application.

• GbE port operational statusCurrent operational status (up or down) of the GbE interface.

• Radio port operational statusCurrent operational status (up or down) of the Radio interface.

• ODU-ODU port operational statusCurrent operational status (up or down) of the ODU-ODU interface (available only in configurations with 2 FlexiPacket MultiRadios).

• SeverityIt reports the most serious severity for equipment active alarms.

• Connection statusA connected plug icon shows the active connection of the WebLCT to the NE.

Figure 4 System Status


Operate and MaintainAlarm management

3 Alarm managementThe Alarms menu allows checking the status of the equipment alarms and detecting the cause of a possible wrong operation.

The failure and the failure processing are differentiated in 4 failure classes:

• communication problems related to the ports, to the modem and to the Tx power (INTERFACES ALARMS)

• synchronization problems (SYNCHRONIZATION ALARMS) • problems related to the software (SOFTWARE ALARMS) • equipment failures (WHOLE ODU ALARMS)

Any alarm message (raised or cleared alarm) is saved in an alarm log in order to provide an alarm history. Furthermore a list of current alarms is always available and is updated according to the changes in the NE.

3.1 Alarms SeverityFive severity levels are foreseen in order to classify the alarms:

• Critical: indicates that a service affecting condition has occurred (loss of traffic) and an immediate corrective action is required on ODU (e.g. unit substitution); all Physical alarms have critical severity.

• Major: indicates that a service affecting condition has developed (high risk of loss of traffic) and an urgent corrective action is required. Such a severity can be reported, for example, when there is a severe degradation of the functionality of the managed ODU and its full capability should be restored.

• Minor: indicates the existence of a non-service affecting fault condition and that cor-rective action should be taken in order to prevent a more serious (for example, service affecting) fault. Such a severity can be also reported when the detected alarm condition is not currently degrading the functionality of the managed ODU.

• Warning: indicates the detection of a potential or impending service affecting fault, before any significant effects have been felt. Action should be taken to further diagnose (if necessary) and correct the problem in order to prevent it from becoming a more serious service-affecting fault.

• Indeterminate: indicates that the severity level has not been assigned. Test alarms always belong to this category.


17

Operate and Maintain Alarm management

3.2 Alarm condition (menu Equipment > System Status)In the menu Equipment > System Status if no alarm is active in the NE, the Severity field will show a bell icon with GREEN color, but if at least one alarm is active in the NE the bell icon will take the color of the alarm with the highest severity, as shown in the next figure.

Figure 5 Severity



3.3 Display of Alarms (Alarm menu)

Figure 6 Display of Alarms (1+0)

Figure 7 Display of Alarms (1+1)

The NE points out its current status through a LED (round-shaped icon).

The LED colour can be:

• GREEN: no active alarm • RED: active alarm.


19


1 Whole ODU alarms

• System FailureThe FlexiPacket MultiRadio is failed and needs to be replaced. By clicking on the icon a screen opens, showing the alarm root which causes the activation of the System failure alarm.

• Power Supply FailureFailure of the system power supply source or power supply voltage at the NE input low.

• Time ServerThe Time Server has been configured, but it is not reachable.

• Protection FailureOnly if the System Type is 1+1: failure in the protection configuration.

• IDU Continuity Check LossThe FlexiPacket MultiRadio does not receive 3 consecutive CCMs. RDI is also sent back. Available in 1+0 SystemType only.

• OAM RDIState of the RDI bit in the last received CCM (true for RDI=1 or false if none has been received).

2 Synchronization

• Synch failureOne of the synchronization sources is not available.

• SSMIt is shown, only if the SSM has been enabled. The SSM messages are not received from the selected synchronization interface. When multiple interfaces are configured as synchronization sources, this alarm is activated, if the equip-ment does not receive the SSM messages from at least one of the configured synchronization interfaces.

3 Maintenance

• Manual Operation check box.When a loopback has been implemented (or another manual operation is under progress) a check mark will appear in this box.

• Configuration not supportedThis alarm rises when a not supported configuration has been configured (refer to Table 5).By clicking on the icon a screen opens, showing the root of the alarm.



4 System SeverityIf some alarms are active, in this area the LED turns on with the color associated to the alarm with highest severity.

5 Accounting LogThe warning notification “on” means that the accounting log file has been filled in with this percentage.

6 Interfaces Alarms

• GbEth PortOperational status of the GbEth port (up or down when a failure/wrong operation is occurred on the Ethernet interface).

• Radio PortThe alarm is active due to propagation alarm or status of the radio port set to down.Moreover, this alarm can be active due to an Rx failure in the Rx circuits.By clicking on the icon a screen opens, showing the alarm root which causes the activation of the Radio port alarm.

• ODU-ODU portThis alarm raises only with the configuration with two FlexiPacket MultiRadios. Problem on the ODU to ODU interconnection. By clicking on the icon a screen opens, showing the alarm root which causes the activation of the ODU-ODU port alarm.

• ModemAlarm due to propagation.

• Tx powerFailure in the Tx circuits.

System type Hw protection Mode

ANSI bandwidths

ETSI 3.5 MHz bandwidth

1+0 - x x

1+0 Ring - x Not supported

1+1 FD 2 cables CCM based x Not supported

1+1 SD 2 cables CCM based Not supported Not supported

2+0 FD 2 cables CCM based x Not supported

2+0 XPIC 2 cables CCM based x Not supported

Standalone Not supported Not supported

1+1 HSBY 2 cables CCM based x Not supported

Standalone Not supported Not supported

2+0 XPIC 1 cable - Not supported Not supported

1+1 HSBY 1 cable - Not supported Not supported

Table 5 Not supported configurations


21


7 Software Alarms

• Scheduled Action Failure: no scheduled action took place correcly (i.e. the scheduled software download)

• Sw/Hw Mismatch: no compatibility between the software version and the hardware version (the software version requires a different hardware version)

• Software Switch No allowed: not possible to switch the two software banks • Application mismatch for Standby version: the FlexiPacket MultiRadio can

work in 2 different ways according to the type of the installed software: packet (application described in this document) or hybrid. If on the active bank is installed the packet application and for any reason in the stand-by bank is installed the hybrid application, this alarm will become active.

• Protection Configuration Error: configuration problem in 1+1 configuration • P-CCM Configuration Error: configuration problem in 1+1 configuration

3.4 Alarm ListThe Alarm List menu opens a list with all the current alarms with the relevant Raised time, Severity and Alarm Description.

Figure 8 Alarm List

t The Alarm List can be filtered by pressing the relevant icon in the Filter bar. When a filter has been activated, the background of the icon is white.


Operate and MaintainTest Functions

4 Test FunctionsSelect menu Equipment > Operation, Administration and Maintenance.

Figure 9 Test Functions (1+0)

4.1 LoopbacksThe loopbacks are available only in 1+0 configuration:

• LL4: used to test cable connectivity. LL4 can be enabled for a time T (user configu-rable with granularity in seconds), before being automatically disabled by µP.

• LL1: RF loopback. • LsRL3 (in the local station) and RL3 (in the remote station): these 2 loopbacks can

be used to test the radio link.


23

Operate and Maintain Test Functions

Figure 10 IDU-ODU Cable Test

Figure 11 RF Self Test

Figure 12 Link Test

Not more than one loopback can be enabled at a given time. When a loopback is enabled, the system moves to a "test mode" configuration designed for transmitting back traffic.

The differences between the test and the normal are in the L2 switch configuration. When operating in test mode the auto-learning and filtering functions are disabled; the MAC forwarding table is flushed.

During the entire duration of the loopback the FlexiPacket MultiRadio is not reachable for management. Moreover after loopback has been performed, an xml file becomes available containing the result of the counters.



4.1.1 LL4 (IDU-ODU cable test loopback)Check the cable connectivity by using the local loopback.

Steps


25


4.1.2 LL1 (RF loopback)Check the correct operation of the station by using the RF loopback.

Once enabled the FlexiPacket MultiRadio declares the "test mode"; during loopback test the µP is not reachable from local GbE cable and supervision is lost.

The system will save the actual configuration for the involved elements (switch, modem, etc…) for being restored once the procedure is finished.

Test packets are generated by the µP.

The procedure terminates after a configurable time T (default = 10 seconds). Once the previous system configuration is restored, the result of the loopback test is reported and a detailed report file (.xml format) is available.

Steps



4.1.3 Link Test loopbacksRemotely test the radio link by using two loopbacks:

• LsRL3 in the Local Station • RL3 in the Remote Station

t First activate the loopback in the Remote Station and then activate the loopback in the Local Station.

t The time-out set in the Remote Station must be longer than the time-out set in the Local Station.

This test procedure extends local self-test procedure over the radio link. The procedure here described assumes the LCT being able to access both local and remote Flexi-Packet MultiRadio. No User traffic is required to be supported whilst remote test proce-dure is ongoing. Test packets are generated by the µP.

The system will save the actual configuration for the involved elements (switch, modem, etc…) for being restored once the procedure is finished.

The procedure terminates after a configurable time T (default = 10 seconds). Once the previous system configuration is restored, the result of the loopback test is reported and a detailed report file (.xml format) is available.


27


Steps for RL3



Steps for LsRL3


29


4.2 Timed Tx SquelchThere is the possibility to control the temporary turning off of a radio system. The RF Transmitter is automatically turned on again at the expiring of the preset timeout.

To configure the Test enter the suitable value in the Timed Tx Squelch field (60 sec. is shown in the next figure).

Figure 13 Timed Tx Squelch


Operate and MaintainMeasurement management

5 Measurement managementThe Measurements menu provides the following options:

Figure 14 Measurements menu

• Port Counters: Measurements on the Ethernet traffic interface • RF & Others: Reading of the RF Tx - Rx power, number of synchronization switch,

LLDP summary.


31

Operate and Maintain Measurement management

5.1 Port CountersThe Port Counters menu allows to display the statistics information relevant to the 3 ports of the internal Ethernet switch.

Figure 15 Ethernet counters

The counters can be automatically updated by ticking the Poll every check box and by inserting the interval (in second) or manually by clicking on Refresh. The Refresh button is available, only if the Poll every check box is deselected.

Ethernet counter meanings:

Counter Description

InOctets Number of good Ethernet frames received

InUnicast Number of good frames having a Unicast destination MAC address

InBroadcasts Number of good frames having a Broadcast destination MAC address

InMulticasts Number of good frames having a Multicast destination MAC address

InDiscards Counter that counts the number of good, non-filtered frames that normally would have been forwarded, but could not be due to a lack of buffer space

InErrored Total received frames with an Rx errored signal and with a CRC erros

Table 6 Ingress counters



Select the port (GbE, Radio or ODU-ODU in the Reset Countes field and press Reset to reset the relevant counters.

The OAM area contains the number of E-CCM and P-CCM sent messages (only in 1+1 configuration).

The LLDP Counters area contains the Counters of the LLDP protocol (if the protocol has been enabled).

Counter Description

OutOctets Number of good Ethernet frames sent from this MAC

OutUnicast Number of frames sent that have a Unicast destination MAC addresss

OutBroadcasts Number of good frames sent that have a Broadcast des-tination MAC address

OutMulticasts Number of good frames sent that have a Multicast desti-nation MAC address

OutDiscards Counter that counts the number of good frames that were filtered due to egress switch policy rules

OutTotal Number of the send Ethernet frames

Table 7 Egress counters

Counter Description

E-CCM Sent Messages Total number of Continuity Check Messages transmitted (not available in 1+0 system type)

P-CCM Sent Messages Total number of Protection Continuity Check Messages transmitted (only in 1+1/2+0 system type)

Table 8 Protection counters

Counter Description

Port It can be GbE, Radio, ODU-ODU

Valid Received Frames Total number of the valid LLDP frames received on a specific port

Transmitted Frames Total number of the LLDP frames transmitted on a specific port

Agent Discarded Frames Total number of the LLDP frames received on a specific port, and then discarded for any reason

Age-Outs Number Total number of disconnections of the neighbour

Table 9 LLDP counters


33


5.1.1 How to check the errors on the Ethernet cable after a long recording of traffic

Steps

1 Open the "PortCounters" window.

2 You can analyze the Counters of every Ports available: the GbE Port is all about the Ethernet cable.

You can read the row "GbE" and see the value under the column "In Errored" (see next figure).

3 If there is a value other than "0", the ODU has received errors on Ethernet cable (Gigabit Port) compared with a previous reset of the counters (refer to paragraph 5.1.2).



5.1.2 Reset the countersThe values of the counters are valid if you made the reset of the counters of the GbE Port ( or All Ports) at the start of recording.

To reset the counters:

1 Look at the top right of the "Port Counters" window: choose the port you want to reset and then click the "Reset" button (see next figure).

2 After this operation, a warning message appears: "Are you sure you want to reset the Ethernet counters?"; click "Yes".

3 Now all the counters are reset to 0; you can choose to see the new values of the counters:

• only when you want (Unmark "Poll every" at the top left of the "Port Counters" window and click the blue arrow to see the last values of counters);

• or updated automatically every tot seconds (Mark "Poll every" at the top left of the "Port Counters" window and click the blue number of seconds to the step of reading).


35


5.2 RF & OthersBy selecting RF & Others the following dialog box opens:

Figure 16 LLDP Counters

The RF Measurements contains:

• RF Operational Status: status of the Transmitter (Up/Squelched). • Current values of the RF Tx and Rx power levels (the measurement is in dBm); • Temperature: internal temperature of the FlexiPacket Radio;

The Radio Link Status area shows the alarms regarding the radio link.


Operate and MaintainExport Data

6 Export DataThis menu allows to export and to save on the PC the report files.

Figure 17 Export Data menu

6.1 How to export the report filesSteps

1 Select the file or the files to be exported by a tick in the XML file check box and in the relevant stylesheet check box.

t The stylesheets on the grey background are not present.

2 Click on the Start button.

3 Browse in the destination directly of the files.

Figure 18 Destination directory


37

Operate and Maintain Export Data

t The files are automatically saved in the following way:

• <file name>_<NE IPaddress>_FPMR.xmlE.g: performance_10_12_123_55_FPMR.xml

4 Click on Save.

5 The Exporting... screen opens.

Figure 19 Exporting

6 Wait until the exporting is complete (green LED icon for each exported file).

7 Click on Close.

8 To open the previously exported file navigate on the file destination directory and double click on the xml file.


Operate and MaintainPerformance management

7 Performance managementThe basic requirement for performance monitoring is the ability to detect errors and failures while a radio link is in service. For this purpose, block error monitors are defined inside the Radio frame.

Three types of performance are available:

• RSPI Performance • ACM Performance • Ethernet Performance

The system foresees two measuring intervals for the performance data:

• interval of quarters of an hour • interval of 24 hours.

The performance windows display the counting of the performance for the current quar-ter/day and for the previous 16 quarters and four days.

The time measuring unit is the second. The measurement of the quarter of an hour has the tolerance of ±1 second; the measurement of the 24 hours has the tolerance of approximately 10 seconds. It is necessary to consider that it can be present a displace-ment of the measurements due to the tolerance of the quarzs equipped into the different units. The inner time reference is provided by the Controller. Usually, it is enabled, for the NE, the network synchronization. However, the user can set manually the date and time.

The Suspect Period column, present for each record, allows the identification of the intervals into which there have been conditions such as to consider the measured per-formance as suspect and then not correct (maintenance operations, manual forcing etc.).

t View PM file button allows to open the performance.xml file reporting the PM report.

7.1 RSPI PerformanceBasic definitionsRSPI (Radio Section Physical Interface) performances are parameters allowing esti-mates and statistics on the RF transmission.

The parameters are reported in the table.

It is possible to set up to 4 different thresholds for the RF Rx power (RLT Threshold) and 2 threshold for the RF Tx (TLT Threshold).

RF Rx Field Seconds in which the RF Rx power is lower than a settable threshold value

RF Tx Field Seconds in which the RF Tx power is higher than a settable thresh-old value

Table 10 RSPI Performance


39

Operate and Maintain Performance management

The TLT parameters can be applied only if the ATPC management is implemented on the equipment.

7.1.1 Setting of the RSPI ParametersOpen the PM Setting sub-menu in the Performance menu.

The Performance Setting window allows setting the values of the measurement of the RSPI performance:

• TLT1 = Tx Level Threshold #1 • TLT2 = Tx Level Threshold #2 • RLT1 = Rx Level Threshold #1 • RLT2 = Rx Level Threshold #2 • RLT3 = Rx Level Threshold #3 • RLT4 = Rx Level Threshold #4

Figure 20 Setting of the RSPI Parameters



7.1.2 Displaying of the RSPI ParametersOpen the PM View. Click on Quarter for the 15 performance and Day for the 24 hours performance.

Figure 21 Displaying of the RSPI Performance

Figure 22 displays the RF Rx RSPI performance Quarter. For each measurement interval are reported:

• The maximum and minimum values of RF Rx power detected in the interval dis-played in the RLTM column.

• The count of the seconds in which the RF Rx power has been lower than the four preset RLT thresholds displayed in the RLTS column.

t • RLT: Received Level Threshold • RLTM: Received Level Tide Mark • RLTS: Received Level Threshold Second


41


Figure 22 Displaying of the RSPI Rx Performance (Quarter)

Figure 23 displays the RF Rx RSPI performance Daily.

Figure 23 Displaying of the RSPI Rx Performance (Daily)

Figure 24 displays the RF Tx RSPI performance Quarter.

For each measurement interval are reported:

• The maximum and minimum values of RF Tx power detected in the interval dis-played in the TLTM column.

• The count of the seconds in which the RF Tx power has been higher than the four preset TLT thresholds displayed in the TLTS column.

t • TLT: Transmitted Level Threshold • TLTM: Transmitted Level Tide Mark • TLTS: Transmitted Level Threshold Second



Figure 24 Displaying of the RSPI Tx Performance (Quarter)

Figure 25 displays the RF Tx RSPI performance Daily.

Figure 25 Displaying of the RSPI Tx Performance (Daily)


43


7.2 ACM PerformanceThe ACM performance menu shows the total number of seconds, during which the Radio link in Tx side (or in Rx side), a specific modulation profile has been used.

7.2.1 Displaying of the ACM ParametersOpen PM View in the Performance menu.

Figure 26 Displaying of the ACM Performance

t The ACM Colocated ODU area is shown only in the configuration with 2 FlexiPacket MultiRadios.

Select the ACM menu Quarter for the 15 performance and Day for the 24 hours perfor-mance (steps 1 and 2).



The Figure below displays the ACM Rx performance Quarter.

Figure 27 Displaying of the ACM Rx Performance (Quarter)

The Figure below displays the ACM Rx performance Daily.

Figure 28 Displaying of the ACM Rx Performance (Daily)


45


The Figure below displays the ACM Tx performance Quarter.

Figure 29 Displaying of the ACM Tx Performance (Quarter)

The Figure below displays the ACM Tx performance Daily.

Figure 30 Displaying of the ACM Tx Performance (Daily)



7.3 Ethernet PerformanceThe Ethernet performance menu shows the performances of the Ethernet interfaces as shows in the next figure.

Figure 31 Ethernet performances

Ethernet performance meanings:

7.3.1 Displaying of the Ethernet PerformancesOpen PM View in the Performance menu.

Counter Description

InGood Packets Number of good Ethernet frames received

InGood Octets Number of good Ethernet octets received

InErrored Packets Total received frames with an Rx errored signal and with a CRC errors

Table 11 Input performance

Counter Description

OutOctets Number of good Ethernet octets sent

OutDropped Packets Number of good frames that were filtered due to egress switch policy rules

OutGood Packets Number of good Ethernet frames sent

Table 12 Output performance


47


Figure 32 Displaying of the Ethernet Performance

Select the Ethernet menu Quarter for the 15 performance and Day for the 24 hours per-formance (steps 1 and 2).

The Figure below displays the GbE performance Quarter.

Figure 33 Displaying of the GbE Performance (Quarter)



The Figure below displays the GbE performance Daily.

Figure 34 Displaying of the GbE Performance (Daily)

The Figure below displays the Radio performance Quarter.

Figure 35 Displaying of the Radio Performance (Quarter)

The Figure below displays the Radio performance Daily.

Figure 36 Displaying of the Radio Performance (Daily)


49

Operate and Maintain Administration tasks

8 Administration tasksAll the tasks list in this chapter are normally performed by the Administrator.

8.1 SecurityOpen the Security menu (figure below).

Figure 37 Security

If you are logged-in as Administrator the following parameters can be set:

– Admin / Read Write / Read Only: Passwords (Note: the passwords must be not less than 6 characters and not more than 12 characters).

– Authentication Trap: Enable / Disable– To change the user password click on the relevant User Password field.

In the Accounting log threshold settings area two thresholds can be set:

• Threshold 1: the account log file has been filled in with this percentage. Threshold 1 for sending the first warning notification.

• Threshold 2: the account log file has been filled in with this percentage, and it is almost full. Threshold 2 for sending the second major notification.

By pressing the View Accounting Log button the Accounting Log Table opens.


Operate and MaintainAdministration tasks

Figure 38 Account Log Table

This table represents the source for the account log file and can be read by Admin users only.

The table is maintained persistently for being accessed and elaborated.

The table wrap ups when it reaches its maximum size (120 rows).

The warning thresholds are sent out based on the percentage filling of this table.

By pressing the Export XML button the AccountLogFile can be exported and saved on the PC.


51


8.2 Product and Software menu

8.2.1 Software Data ViewSelect “Software Inventory” in menu Product & Software.

This menu shows the following software data:

• check sum, software release and build of the software uploaded on the active memory bank;

• check sum, software release and build of the software uploaded on the standby memory bank;

• version of the software running on each hardware module.

Figure 39 Equipment Software Data View

8.2.2 Software UpgradeFrom WebLCT, the build software can be upgraded without any interruption on the oper-ation.

The upgrade procedure uploads the software build on the standby bank; the system keeps running the pre-existing software on the active bank.

To make active the new build software, it is necessary to execute the switching of the banks. The switching operation runs the new version of the software.

To upgrade the build software, follow the steps.



Steps

1. Click on Product and Software menu.2. Click on SW Upload button.3. Insert User Name = “admin” and Password = Administrator Password.4. Click OK.

Figure 40 Software Upgrade5. Select the file “standby.pec” (previously stored in the PC). 6. Confirm the operation.


53


7. In the Stand-by SW load area a new field appears (SW download), which shows the status of the download (running), as shown in the next figure.

8. Wait until the SW download field disappears from the screen (the download is now complete).

9. In the Switch Loads area two ways to swap the 2 banks are available: a) Click the Switch button in the Immediate Switch field to start with the swap of

the two loads: the standby load becomes active and the active load becomes standby.

b) Click on Schedule button in the Scheduled Switch field to set the date and time of the activation of the standby load.(Click on Delete to cancel the scheduled date).

t The software upgrade can be done also by using any FTP client in binary mode. When you log-in check to be in directory ram 0.

t The Align loads button copies the active bank to the stand-by bank.

t Sw load hybrid packet mismatch alarm in the stand-by SW load areaThe FlexiPacket MultiRadio can work in 2 different ways according to the type of the installed software: packet (application described in this document) or hybrid. If on the active bank is installed the packet application and for any reason in the stand-by bank is installed the hybrid application, this alarm will become active.



8.2.3 Product Inventory DataSelect HW Inventory in the Product & Software menu.

The Hardware Inventory menu shows all the inventory data (memorized into non volatile memories).

Figure 41 Product Inventory Data


55


8.3 License UpgradeThe license is stored into the Memory Hardware.

When a change of the functionalities (subject to license) is required, the NE checks if the fees and the credits allow the new setting.

Select the menu Equipment > Operation, Administration and Maintenance > tab-panel License.

Pressing the “Enter” push-button in the License area, the License Key Modify window opens, where it is possible to insert in SMS format a new license for expanding the software functions. There are four text fields for the four blocks of the license.

t To generate a new license the CLicS application must be used.With this application the new values to be inserted in the four License Key fields are calculated.



The instructions to use the CLicS are given in chapter 9.1 Instructions for fetching license key from CLicS system.

8.4 ResetSelect menu Equipment > System Status.

Figure 42 Reset

Three types of Reset can be activated:

• Software Reset: reboot of the Controller (no traffic impact) • Configuration to default Reset: set of the default configuration of the FlexiPacket

MultiRadio • Hardware Reset: switch off and switch on of the FlexiPacket MultiRadio


57


8.5 Backup and RestoreA backup file, which contains the NE configuration, can be saved on the PC. (Refer to paragraph 8.5.1).

A previous saved backup file can be downloaded to the NE by the Restore menu. (Refer to paragraph 8.5.2).

Select the menu Equipment > Operation, Administration and Maintenance > tab-panel Backup & Restore.

8.5.1 Backup

Figure 43 Backup

Steps

1 Press the Backup button (to create the backup file in the NE).

2 Wait until the Backup status is normal.

3 Press the Get config file from NE button.

4 Click OK on the message “Always allows this action”.

5 Browse in the directory to be used to store the backup file.

6 Save the file by assigning name and extension.



8.5.2 Restore

Figure 44 Restore

Steps

1 Press the Put config file from NE button.

2 Browse in the directories to find the previously saved backup file.

3 Click on Open.

4 Wait until the transfer of the file on the NE has been completed.

5 Click on Restore to activate the new configuration.

t Click on View Last Restore Log button to view the log of the last restore done on the application, if any (refer to Figure 45).


59


Figure 45 View Last Restore Log

In the Result column “not OK”means that the item has not changed.


Operate and MaintainLicence management

9 Licence management

9.1 Instructions for fetching license key from CLicS systemTo use the CLicS system follow the following steps.

1 Send following text message via SMS to CLicS system number +358 40 4800 500. "StockID TargetID". Use single space between StockId and TargetId. Example message J22A3 D24612345.

a StockID is available from CLicS system. CLicS is the web based tool hosted in NOLS portal, CLicS handles license delivery for NSN. User should login to NOLS portal via link “https://online.portal.nokiasiemensnetworks.com” and navigate from Care > CLicS menu. From CLicS home page, click left hand side link "Support for SMS Delivery" to search for the customer's stocks. Right Product and Customer need to be selected to fetch the right license stock. From the search results, note down the license Stock ID.

b Target ID is the device serial number of the Network Element to which License key has to be installed. Target ID is not case sensitive; AB and ab are treated as same.

2 If request is successful, you will receive response text message from CLicS. Message format is" SI - <SALES ITEM DESCRIPTION > Target id - <TARGET ID>, License key- <LICENSE KEY>.

3 If request is not successful, the error messages listed in par. 9.3 can be received.

9.2 Support for Target ID swapTarget IDs can be swapped only if:

• hardware is broken and a replacement license key is needed in new HW. • a wrong target ID has been used.

Only license type that can be swapped is: license & standard key, if a reason for SWAP is met.


61

Operate and Maintain Licence management

By default the function is enabled for NSN Internal users (except PL users and 3rd party users) and disabled for the customers and subcontractor users. Customer users do not have right to swap by default.

Internal Users can swap only active and "on-hold" licences. Cancelled licences are not visible at all in SWAP page.

To check your rights to SWAP, access My Profile > SWAP link.

Global and Product Line Key Users have rights to enable a specific customer to be able to swap license keys.

Search CriteriaWild character can be used only in Customer name on it's own.

Profiled Customer: If certain customers profiled in My Profile, this functionality can be used. Customer name and customer number will then be disabled.

Mandatory search criteria are marked with star (*) character (a value must be entered in at least one of the fields):

• Customer name: a part of customer name and * can be typed, e.g. Bharti* • eChannel Order id: SAP SO number • Customer order id: MLS Purchase Order Number or text typed in SAP SO PO

number field • LAC/serial number: a part of LAC and * can be typed, e.g. FI3206* • Target ID: serial number of network element

Additional search criteria:

• Customer number: SAP customer/ship-to party number • License Type: license and standard key, license and non-standard key • Sales item description: SAP sales item description • LKs created from (dd.mm.yyyy): period beginning from this date • LKs created to (dd.mm.yyyy): period ending to this date • Request source: ALL, SAP or Manual (order entered from SAP or created manually) • Product filter: To be used to make Product search easier. A part of product name

followed by asterix (BSC*) can be typed and then press GO. The below product box shows only the products with BSC in the name.

• Product: Can use the above mentioned filtering, profiled (see 1.1. My Profile) or find the exact product

• Target ID: serial number of network element • Feature Name: name of the feature • Sales item: SAP Sales item, a part of the name with a * wild card can be used.



By pressing the LAC/Serial number link . user is directed to Detailed LK information. User can navigate also from there to the SWAP target IDs.

Key enter some search criteria and press FETCH button.

Press SWAP TARGET IDs.

3. Type e-mail address where the LK needs to be sent to or choose download: For customer Users only download possible.

4. Find the old/wrong Target ID in which needs to be swapped, click checkbox next to it and enter the new/correct Target ID in 'New Target Ids' field. Choose a Reason for Swapping from drop-down menu. Options are: Typing Error, Hardware Broken, Other. When reason Other is chosen, free text needs to be typed.

Capacity can also be added if there is some capacity left.

5. Click SWAP button.

6. A pop up window will appear and if clicked "yes".


63


An e-mail notification is sent to the specified e-mail address (if e-mail function used) and also to all the users who have registered e-mail notification for SWAP in My Profile.



9.3 Troubleshooting instructions

Error Code

Error scenario System Response Corrective instruction

001 Incorrect message format

Error 001: Incorrect message format. Please send message in format "STOCK-ID DEVICE-SERIAL-NUMBER". NSN/CLicS

User should send message again with correct message format. Message format expects at least 2 words. First word is considered as Stock-ID and 20 characters after the first space will be considered as target ID.

002 Requester's mobile number cannot be identified in system

Error 002: Access rights denied for requested mobile number. Please contact NSN Contact / NOLS Support for correcting mobile number in NOLS account. NSN/CLicS

User's mobile number cannot be traced back to a valid NOLS account. If user has existing NOLS account, mobile number update can be requested by email to NOLS Support team. If user does not have NOLS account, request NOLS support for creating new account.

003 Mobile number is valid, but SMS license delivery access missing

Error 003: You do not have sufficient access rights for CLicS SMS service. Please contact NSN Contact Person/CLicS Local key users for access rights. NSN/CLicS

User has a valid NOLS account with correct mobile number. But CLicS tool access or/and CLicS Subcon-tractor role is missing. CLicS Local key user should be able to provide the needed CLicS roles.

004 Stock ID is invalid Error 004: Stock-ID ABC is not valid. Please type the correct Stock-Id. NSN/CLicS

The stock id sent by user is incorrect and does not exist in CLicS. Correct Stock-Id should be noted down from CLicS application web inter-face from left hand menu - "Support for SMS Delivery".

Table 13 Troubleshooting instructions


65


005 User does not have access rights to create licenses from requested stock.

Error 005: You do not have access to license keys from stock ABC. Please contact NSN Contact /CLicS Local key users to get needed access rights. NSN/CLicS

Stock is valid, but user does not have access to the men-tioned stock. Stocks are associated with customers. User should be mapped to the customer to enable access to the stocks belonging to that customer. CLicS Local key users should be contacted for mapping user to needed cus-tomers in CLicS system.

006 Stock does not have any more capacity available for license key creation

Error 006: Stock ABC does not have capacity available for license creation. Please contact NSN for solving the problem. NSN/CLicS

Stock available capacity is zero. This is possible if:

• All ordered licenses are used > more licenses need to be ordered

• Licenses are ordered, but order is cancelled / GI not issued/ GI cancelled. > contact SAP local key users for correcting the problem

007 License generation failed due to system problem

Error 007 - License generation failed. Please contact NSN Contact Person to investigate the problem. NSN/CLicS

License generation failed due to system related problem. This is possible if any system component is down (NAIP, CLicS, and NOLS) or not working. User can try after sometime; it will work if the problem was temporary. CLicS IT Support should be contacted according to support model to troubleshoot the problem.

008 Device Serial number length exceeds limit

Error 008 - Entered Target ID has more than 20 characters, Please check if the target id (device serial number) is correct. NSN/CLicS

CLicS system allows device serial numbers (target id) of maximum length 20 charac-ters. Please type the correct target id.

Error Code


Table 13 Troubleshooting instructions (Cont.)



9.4 Contact & Reference Information • List of countries and operators supported for SMS License delivery - add link here • CLicS Local key user list can be found from

https://inside.nokiasiemensnetworks.com/global/Company/Organization/OPS/Integrated_OEM_and_Digital_Supply/Digital_Delivery_Center/Central_Licensing_System_CLics/Pages/Central_Licensing_System_CLicS.aspx

• NOLS Support desk contact - [email protected] • CLicS IT Support: RMT ticket should be raised to CLicS IT support via one of follow-

ing ways • Key Users are authorized to contact CLicS Application Support directly by

Request Management Tool (RMT) • Key Users may also contact NOLS Support Desk by email (NOLS.Sup-

[email protected]) in order for NOLS Support Desk to create the request by RMT to CLicS Application Support.

9.5 How to test SMS connectivity with CLicS systemSend the following message via SMS to phone number +358404800500:

ABCD 123456789

Test successful: Confirm that you receive an error message response from +358404800500 “Error 002: Access rights denied for requested mobile number. Please contact NSN Contact Person/NOLS Support for creating NOLS account or update mobile number in existing NOLS account”.

or

another error message.

Test failed: If no respnse is received,connectivity test is considered failed Please contact CLicS support / CLics key uesrs and provide following information:

009 Device Serial Number format is invalid

Error 009 - Entered Target ID contains invalid characters, Please check if the target id (device serial number) is correct. NSN/CLicS

The target ID contains char-acters which are not allowed. Allowed characters are ASCII characters within range 0-127. CLicS IT support should be contacted for further details.

No response from CLicS after 15 minutes SMS request is sent (in average response is expected in less than 5 minutes)

User gets no response from CLicS after SMS request is sent

Technical problem contacting BookIT server. CLicS IT support should be contacted for troubleshooting the problem on BookIT server.

Error Code


Table 13 Troubleshooting instructions (Cont.)


67


• time and date of testing • your mobile number and country • local mobile operator used

9.6 Contact information for helpCLicS support and key user organization can be contacted for help:

• [email protected] (+358504872769) / CLicS global key user • [email protected] (+8613501749981) / CLicS global key user • [email protected] (+358466140416) / CLicS application support lead • [email protected] / CLicS application support

Documents

FPMR 2.4 Oper Maint