FlexyHibrit Operate and Maintain

DRAFT

FlexiHybrid

Operate and Maintain

A25000-A0300-F019-02-76P1

Issue: 2 Issue date: February 2010

DRAFT

DRAFT2 A25000-A0300-F019-02-76P1Issue: 2 Issue date: February 2010


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 2010. All rights reserved.

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DRAFT

DRAFT

A25000-A0300-F019-02-76P1Issue: 2 Issue date: February 2010

3


Table of ContentsThis document has 89 pages.

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.4 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.5 Waste electrical and electronic equipment (WEEE) . . . . . . . . . . . . . . . 111.6 Types of User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.7 Features Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.8 Security Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.1 PC Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.1.1 Local connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.1.2 Remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2 PC Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3 Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.4 Telnet/SSH client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.5 HyperTerminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.6 Access rights for users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.6.1 User Level 1 – Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.6.2 User Level 2 – Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.6.3 User Level 3 – Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.6.4 User Level 4 – Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3 User interface overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.1 WEB Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2 CLI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.1 How to use CLI screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2.1.1 Menu Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2.2 Configurable Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4 Navigation tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5 User Interface screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.2 Starting Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.3 Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.4 Device Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.4.1 WEB Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.4.2 CLI Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.5 Serial Number Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.5.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.5.2 CLI Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.6 Reprogramming CPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.6.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.6.2 CLI Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

DRAFT



5.7 Add User Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.7.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.7.2 CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.8 Delete / Edit User Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325.8.1 CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.8.2 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.9 View Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345.9.1 WEB Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345.9.2 CLI Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345.10 System Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.10.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.10.2 CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.11 Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365.11.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365.11.2 CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365.12 Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.13 Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.13.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435.13.2 CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435.14 Statistics – Data Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445.14.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455.14.2 CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455.15 Statistics – NMS Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.15.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.15.2 CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.16 ODU Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.16.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.16.2 CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.17 Modem Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.17.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.17.2 CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525.18 BERT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.18.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.18.2 CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545.19 CW Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555.19.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555.19.2 CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555.20 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565.20.1 WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565.20.2 CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575.21 Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

6 Upgrading procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596.1 Software components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596.2 IDU software upgrade procedure from SVR 1.1 to SVR 2.1. . . . . . . . . . 616.2.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616.2.2 Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616.2.3 Upgrade Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

DRAFT

DRAFT


5


6.2.4 FTP File Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636.2.5 Output Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636.3 IDU software upgrade procedure from SVR 1.2, SVR 1.3, SVR 1.4 and

SVR 2.0 to SVR 2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706.3.1 Flash memory size preliminary check . . . . . . . . . . . . . . . . . . . . . . . . . . 726.4 IDU software upgrade procedure from SVR 1.2, SVR 1.3 or SVR 1.4 to

SVR 2.1 with HW upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746.5 IDU software downgrade procedure from SVR 2.1 to SVR 2.0 . . . . . . . 766.6 IDU software downgrade procedure from SVR 2.1 to SVR 1.4 . . . . . . . 786.7 IDU software downgrade procedure from SVR 2.1 to SVR 1.3 . . . . . . . 816.8 IDU software downgrade procedure from SVR 2.1 to SVR 1.2 . . . . . . . 846.9 ODU software upgrade procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866.10 FTP File Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

7 FTP upload procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877.1 FTP Upload Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877.2 Windows FTP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877.3 Graphical FTP Client (Filezilla or other FTP programs). . . . . . . . . . . . . 87

8 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

DRAFT



List of FiguresFigure 1 WEEE label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 2 Network connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 3 Web starting information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 4 CLI starting information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 5 CLI menu type screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 6 Configurable screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 7 Starting Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 8 Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Figure 9 Device Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 10 Serial Number Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Figure 11 Reprogramming CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 12 Add User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Figure 13 Delete User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Figure 14 Delete/Edit User Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 15 Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Figure 16 System Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Figure 17 Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 18 Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 19 RSL Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 20 SNR Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 21 Tx Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 22 Error Seconds Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 23 Equalizer Taps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 24 Constellation Display (128 QAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Figure 25 STM Mux/Demux Regenerator Section . . . . . . . . . . . . . . . . . . . . . . . . . 41Figure 26 STM Mux/Demux Line Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 27 Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 28 Statistics – Data Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 29 Ethernet Payload Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Figure 30 NMS Switch Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Figure 31 ODU Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 32 Modem Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 33 BERT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Figure 34 CW Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Figure 35 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 36 Local LIU loop in IDU1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 37 Local Modem loop in IDU1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 38 Remote LIU loop in IDU1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 39 Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Figure 40 Command prompt screenshot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

DRAFT

DRAFT


7


List of TablesTable 1 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 2 List of conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . 9Table 3 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Table 4 Software current version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Table 5 Components for the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

DRAFT



DRAFT

DRAFT


9

Operate and Maintain Preface

1 PrefaceThis document provides the information to operate and maintain the FlexiHybrid.

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

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

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

Chapter Title Subject

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

Chapter 2 Start-up Provides the list of the operations and the instructions to enter the FlexiHybrid by the LCT

Chapter 3 User interface overview Provides an overview on the User inter-face

Chapter 4 Navigation tree Provides the tree structure of the LCT

Chapter 5 User Interface screens Provides the information on the LCT menu screens

Chapter 6 Upgrading procedure Provides the information to be used to upgrade the software

Chapter 7 FTP upload procedures Provides the information on the FTP

Chapter 8 Acronyms and abbreviations Lists the acronyms and abbreviations used in this document

Table 1 Structure of this document

Representation Meaning

Bold Text in the graphical user interface (window and wizard titles, field names, buttons, etc.) is represented in bold face.

Example: Click Shutdown and then click OK to turn off the com-puter.

Table 2 List of conventions used in this document

DRAFT


Operate and MaintainPreface

Italic Field values, file names, file extensions, folder and directory names are denoted by italic text.

Examples: Enter 192.168.0.1 in the IP address field. Click OK to produce a .pdf file.

Courier Command and screen output are denoted by courier font.

Example: ping -t 192.168.0.1

<Angle brackets> Place holders for distinct names or values are represented by enclosing them in <angle brackets>. If a file name is involved, italic text will also be used.

Example: The naming convention for the log files is <NEname>.txt, where <NEname> is the name of the NE sending the messages.

Keyboard button Keyboard keys are represented with a surrounding box.

Example: Press Enter .

[Square brackets] Keyboard shortcuts are represented using square brackets.

Example: Press [CTRL+ALT+DEL] to open the Task Manager.

> The “>” symbol is used as short form to define a path through indi-vidual elements of the graphical user interface, e.g., menus and menu commands.

Example: On the Windows taskbar, select Start > Programs > TNMS > Client menu command to start the TNMS Core/CDM Client.

☞ A tip provides additional information related to the topic described.

g A note provides important information on a situation that can cause property damage or data loss.

A note introduced in the text by the keyword NOTICE: describes a hazard that may result in property damage but not in personal injury.

f A safety message provides information on a dangerous situation that could cause bodily injury.

The different hazard levels are introduced in the text by the follow-ing keywords:

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.

Representation Meaning

Table 2 List of conventions used in this document (Cont.)

DRAFT

DRAFT


11


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.

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 Types of User InterfacesThe terminal can be accessed through Serial, Ethernet, or Modem interfaces using the following types:

– Web Interface (Normal / SSL)– Command Line Interface, CLI (Serial Console/Telnet/SSH)

1.7 Features Overview– Equipment Provisioning

• Network Time Protocol (NTP) client

Issue Issue date Remarks

1 October 2009 1st version

2 February 2010 The upgrading procedures have been modified

Table 3 History of changes

DRAFT


Operate and MaintainPreface

• Spanning-Tree Protocol (STP) configuration • Serial port configuration • Security configuration • Feature authorization • Configuration saving/retrieving • Alarm notification configuration • DHCP client for automated NMS network configuration

– Link Provisioning • Modulation, Bandwidth, E1 channels, Ethernet, STM-1

– Status and Monitoring • Automated alarm reporting • SNR, RSL, Errored-Seconds • Event Log • Alarm Log • Remote logging to Syslog server • SNMP TRAPs

– Firmware Upgrade– User Management

DRAFT

DRAFT


13


1.8 Security MeasuresThe software partitions resources and denies access to sensitive information. The design of the software also prevents users from intruding on other users and/or resources on the network. Security measures include:

– Encrypted passwords– Multilevel configuration permissions– Network data encryption– Accounting and logging features provide protection from and information about

access attempts.

DRAFT


Operate and MaintainStart-up

2 Start-up

2.1 PC Connection

2.1.1 Local connectionLocal connection of a PC to an equipment can be accomplished via a serial or network port. The connection requirements are listed below:

Serial

– PC with serial port and DB-9 to HD-15 equipment cable– Serial communications software (e.g. Hyperterm)

Network

– PC with 10/100 Ethernet interface– CAT 5 patch cable for connecting PC to the equipment NMS port– Web browser, or– Telnet or SSH client.

2.1.2 Remote connectionRemote connection from a PC to an equipment can be accomplished via a serial com-munication connection or an internet connection.

The connection requirements are listed below:

– PC with network connection– Remote equipment with routable IP address– Web browser, or– Telnet or SSH client.

!Warning on the Ethernet cards

Sometimes, when the equipment is turned off and turned on, or when the LAN cable of the PC is disconnected and reconnected to the NMS interface of the local equipment, the PC Ethernet card remains in the "Ethernet address capture" state and it is not possible to connect to the local equipment anymore (destination host unreachable). It is necessary to disable and enable the PC Ethernet card in order to reach the local equip-ment again.How to solve the problem with two particular Ethernet cards1. Xircom adapter - Update the driver with the last version.2. Realtek adapter - Enable the "Wake on LAN" feature under the advanced tab of the NIC properties dialog box.

DRAFT

DRAFT


15

Operate and Maintain Start-up

2.2 PC Network Configuration

Figure 2 Network connections

To set up a network connection:

– Access the TCP/IP properties from the control panel network connection menu as shown in Figure 2. Verify the IP address, net mask, gateway, and DNS server set-tings.

– Execute a ping to verify connectivity, by typing “ping” followed by the target equip-ment IP address at a command prompt.

2.3 Web browserWhen accessing software via the web interface, use one of the following web browsers:

– Use Internet Explorer version 5.5 or above– Mozilla Firefox (latest version preferred)

Use the browser’s default settings.

The web interface also requires the use of Sun Java JVM version 1.2.2 or above.

DRAFT


Operate and MaintainStart-up

2.4 Telnet/SSH clientWhen accessing the software via the CLI interface, use a telnet or SSH client. An SSH client is similar to a telnet client except it accesses the target over a protected connec-tion.

Windows provides a Windows Standard telnet client that may be accessed through command prompt. An alternate telnet client may be used.

2.5 HyperTerminalWhen connecting via a HyperTerminal program, use the following settings:

– BaudRate=38400– Parity=none– DataBit=8– StopBit=1

The settings may be reconfigured based on system requirements.

2.6 Access rights for usersThe system has four user access levels for configuring and viewing data through the user interface. User accounts can be added and deleted for different access levels. The five user levels and their corresponding user rights are described below.

2.6.1 User Level 1 – MonitorUsername: monitor

Password: monitor

User has minimum access rights and can only view the following pages:

– Home– General Device Information– Configuration Summary– Active Alarm Status– Alarm History– All Graphs– Data Switch and NMS Switch Statistics

DRAFT

DRAFT


17

Operate and Maintain Start-up

2.6.2 User Level 2 – OperatorUsername: operator

Password: col1ma

User has all the access rights of User Level 1 and has additional rights to edit the follow-ing pages:

– Reboot,– All Radio Link and Data Link Configuration pages– Alarm Configuration page– BERT page– CW Mode– Loopback page

2.6.3 User Level 3 – AdministratorUsername: administrator

Password: d1scovery

User has all the rights of User Level 2 and has additional rights to the following pages:

– All Network Configuration– Serial and Security configuration (NOTE: Level 3 and below does not have the ability

to change the Model number)– All Device Information pages– All Maintenance and Restore Defaults pages– STP Screens

2.6.4 User Level 4 – IntegratorUsername: integrator

Password: p1nacate

User has all the rights of User Level 3 and has additional rights to the following pages:

– Ability to change Model number via the GUI interface– ODU and MODEM Trace Screens

DRAFT


Operate and MaintainUser interface overview

3 User interface overview

3.1 WEB OverviewThe web interface is a feature-filled graphical interface for configuring and monitoring the terminal.

Access to web interface is provided via a web browser and a normal or secure connec-tion.

To access the web interface:

1. Open a web browser (browser requirements are stated in section 2.3).2. Type the IP address of the equipment in the address bar and press GO.3. A popup window will prompt for a user name and password.4. Enter a user name and password then press OK.5. When authentication is successful, the Starting Information Screen (Figure 3) is dis-

played.

Figure 3 Web starting information screen

3.2 CLI OverviewThe CLI provides a text-based interface for configuring and monitoring the terminal.

The CLI is accessed through one of the following:

Using Ethernet interface,

1. Telnet / SSH to the terminal (using IP address of the terminal).2. Enter a user name and password at the login prompt.

Using Serial interface,

1. Establish an RS232 connection using a serial terminal.2. Enter a user name and password at the login prompt.

DRAFT

DRAFT


19

Operate and Maintain User interface overview

Following authentication the ”General Information Screen” is displayed (Figure 4). Switch to the “Main Menu” screen by pressing the M-key. From the “Main Menu,” the user can navigate through various interface screens.

Figure 4 CLI starting information screen

3.2.1 How to use CLI screens

3.2.1.1 Menu ScreensMenu screens are used to navigate between functions. They display a list of navigation choices. Each choice is listed with a character placed within [ ] brackets, or “hotkey.” Press the “hotkey” to switch to the corresponding screen.

For example, in Figure 5, enter ‘a’ / ‘A’, to switch to the “General Information” screen (the “General Information” screen is shown in Figure 4).

Figure 5 CLI menu type screens

DRAFT


Operate and MaintainUser interface overview

☞ Further references to “hotkey” in this document will be synonymous with the charac-ter placed in [ ] brackets for the corresponding parameter.

3.2.2 Configurable ScreensConfigurable screens are used to set various parameters.

Figure 6 shows the “General Network Configuration” screen, which is an example of a configurable screen.

Parameters are listed with their values and a “hotkey.” Press the “hotkey” to configure the corresponding parameter.

For example, enter ‘a’ / ‘A’, to edit IP address, then press “Enter Key”. Some parameters may have a set list of values.

For example, the DHCP Client parameter has two values: Enabled and Disable.

To edit this type of parameter, press the corresponding “hotkey” (in this case “E”), then press the “Space Bar”-key, to scroll through different values.

Once the required value is displayed, press the “Enter”-key. If the parameter is displayed without a “hotkey,” it indicates a read-only parameter.

Figure 6 Configurable screen

☞ All the CLI screens will have the following messages:

Navigation Message: Help message about possible navigation from the screen. This will be displayed at the top left and top right of the screen.

Screen Message: Help message about the screen. This will be displayed on the 24th row.

Access Message: Help message about how to access parameters of the screen. This will be displayed on the 25th (last) row.

☞ The CLI has two different types of parameter updates.

Some parameters are updated individually and others are updated as a group.

To perform an Individual Update:

DRAFT

DRAFT


21

Operate and Maintain User interface overview

1. Edit the parameter value.2. Press the “Enter”-key.3. If update was successful, the message “Updated Successfully” will be displayed.4. If the update failed, a failure message will be displayed.

To perform a Group Update:

1. Edit the parameter value.2. Press the “Enter”-key.3. Press the character specified for “Update.”4. If the update was successful, the message “Updated Successfully” will be dis-

played.5. If the update failed, a failure message will be displayed.

☞ 1. CLI screens should ideally be viewed at 25 rows by 80 columns (25 x 80).2. A window of less than 25x80 will have incomplete content.

DRAFT


Operate and MaintainNavigation tree

4 Navigation treeThe Navigation tree shown describes the location of each user interface screen.

Nested screens are indented under the screen from which they can be accessed.

- Home

- Starting Information

- Status Panel

- Navigation Tree

- Administration

- Network Configuration

- General Network configuration

- SNMP Configuration

- Syslog Configuration

- E-mail Configuration

- STP Data Configuration

- STP NMS Configuration

- QoS Configuration

- Global Settings

- Port Priority

- 802.1Q Tag Priority

- IPv4 ToS Priority

- Serial Configuration

- Security Configuration

- Device Configuration

- Device Information

- Device Names

- Set Date and Time

- Maintenance

- Reprogramming CPU

- Add User

- Delete User/ Edit User Entry

- View Event Log

- Link Configuration

- Authorization

- Configuration Summary

- Data Link

- E1 Channel Map

DRAFT

DRAFT


23

Operate and Maintain Navigation tree

- E1 Ports

- Voice Codec

- STM-1 Channel Map

- STM-1 Ports

- Ring Routing

- Radio Link

- APC Configuration

- Protection Configuration

- ODU TX Mute Configuration

- Link Configuration

- ODU Power

- ODU Channel

- ODU Configuration

- Analysis

- Alarms

- Alarm Threshold

- Alarm Configuration

- Alarm History

- Active Alarms

- Graphs

- RSL

- Signal/Noise

- Tx Power

- Error Seconds

- Equalizer Taps

- Constellation

- Mux/Demux

- Statistics

- Data Switch

- NMS Switch

- ODU Trace

- Modem Trace

- BERT Mode

- CW Mode

- Loopback

- Logout

DRAFT


Operate and MaintainUser Interface screens

5 User Interface screens

5.1 IntroductionEach screen section contains the following components:

– User Access Level - Each screen is labeled with “User Access Level: Level X,” where X refers to the access rights for a particular user.

– Description – Gives a description of the screen and the parameters it dis-plays/edits.

– Web Configuration – Gives details to access parameters through web browser.– CLI Configuration – Gives details to access parameters through CLI Telnet / SSH

session / Hyper terminal.

Read-only pages are the only exception, as they have no specific details for different interfaces.

5.2 Starting InformationHome > Starting Information

Figure 7 Starting Information

Figure 7 shows the starting information screen of the user interface.

This screen provides general information about the equipment, including:

– Device Name – Name of the product.– Host Name – Name of the host.– IP Address – IP Address of the system.– Application Version – Version information of the application.– Chassis Serial Number – Serial number of the product (factory assigned).– System Uptime – Uptime of the System.

DRAFT

DRAFT


25

Operate and Maintain User Interface screens

5.3 Status PanelHome > Status Panel

Figure 8 Status Panel

Figure 8 shows the status panel for 1+0 (left) and 1+1 (right) configurations.

This screen provides the modem and alarm status of the terminal as follows:

– ALARM – Alarm Status • Red LED indicates that an alarm has occurred • Green LED indicates no alarms in the terminal • Click on the LED to view the “Active Alarms” Page.

– East / West MODEM – MODEM Status • NA indicates MODEM is inactive • LOCK Symbol indicates MODEM is locked • UNLOCK Symbol indicates MODEM is unlocked.

– TX Power – Transmitting power of the ODU in dB.– Far End TX Power – Transmitting power of the link partner ODU in dB.– SDIDU RSL – RSL value in dBm.– SIGNAL/NOISE – Signal/Noise value in dB. This value corresponds to Eb/No

(Energy per Bit to Noise ratio). If Modem is unlocked, this value will not be displayed.– East mode – Operation mode of the East Link.– West mode – Operation mode of the West Link.

DRAFT



– Local IDU Information – IP Address and Host Name.– Remote IDU Information – IP Address and Host Name.

DRAFT

DRAFT


27


5.4 Device InformationNavigation Tree > Administration > Device Configuration > Device Information

Figure 9 Device Information

The screen shown in Figure 9 is a read-only information page that provides the user with terminal related information.

The parameters listed on this page are:

– Model Number – Model number of the terminal.– Chassis Serial Number – Chassis Serial Number assigned during manufacturing.– Application Version – Active Application Version information.– Date – Current Date.– Time – Current Time.

5.4.1 WEB Location1. Navigate to Administration → Device Information → General in the left panel.2. The read-only terminal information is displayed here.

5.4.2 CLI Location1. Navigate to Administration → Device Information → General Information.2. The read-only terminal information is displayed here.

DRAFT



5.5 Serial Number Information

Figure 10 Serial Number Information

This screen provides Part number, Revision and serial number information of various cards (see Figure 10). The following cards number are displayed.

– Controller card, Standard I/O card, Power Supply cards, Modem cards, IF cards, ODU and chassis.

5.5.1 WEB Configuration1. Navigate to Administration → Device Information and click on the “Serial Numbers”

link on the left panel.2. The current values of various parameters are displayed here.

5.5.2 CLI Configuration1. Navigate to Administration → Device Configuration → Serial Number Information.2. All Serial Number related parameters are displayed with current/present values.3. SNMP Configuration.4. Select a parameter from the MIB section ccmSDIDUSysCfgDevInfoCards.5. Use the SNMP GET command to get the value of the required parameter.6. The SMNP agent will return the actual value after the operation has been success-

fully completed. A failure will cause the SNMP agent to return an error if the agent cannot get the value or if the user is not authorised to access the selected param-eter.

DRAFT

DRAFT


29


5.6 Reprogramming CPUNavigation Tree > Administration > Maintenance > Reprogramming CPU

Figure 11 Reprogramming CPU

The screen shown in Figure 11 is used to remotely Reprogram / Upgrade the terminal software. This page enables the user to upgrade the Kernel, Application, FPGA, ODU, modes, channel, Boot Loader, ODU and Modem firmware Images.

The options available are listed below. Some options available are based on the type of upgrade to be made.

– Toggle Image button – Will swap the Active and Passive files, i.e. active file will become passive and vice versa.

– Version Information – Will display the version information for both active and passive images. The active/Working image will be indicated by :

5.6.1 WEB Configuration1. Navigate to Administration → Maintenance → reprogramming screen.2. Select an Image type.3. To toggle between images, press the toggle button.4. An error event will be indicate through an appropriate error message.

5.6.2 CLI Configuration1. Navigate to Administration → Maintenance → reprogramming CPU screen.2. Scroll through the file names using the Space Bar key and press the Enter key to

select one. Wait for a few seconds to allow the screen to refresh.

DRAFT



3. To toggle between images,a) press the hotkey for toggle;b) the result will be displayed on the screen;c) an error event wil be indicates through an appropriate error message.

☞ A reboot is required after toggling kernel, applications, FPGA, or ODU.

5.7 Add User EntryNavigation Tree > Administration > Maintenance > Add User

Figure 12 Add User

This screen enables the administrators of the terminal to add users to the terminal (see Figure 12).

The options listed on this page are:

1. User ID – Username.2. Group ID / Level – Specify access level3. Password – Password for the entered user id.4. Confirm – Confirm Password entered.

Administrators may not add users with an access level superior to theirs.

5.7.1 WEB Configuration1. Navigate to Administration → Maintenance and click on the “Add User” link on the

left panel.2. Edit fields.3. Click the “Add” button to add a new user.4. Click the “Reset” button to reset page.

5.7.2 CLI Configuration1. Navigate to Administration → Maintenance → User Management → Add User.2. Edit each parameter.

DRAFT

DRAFT


31


3. Scroll through the options for the Level parameter using the Space Bar key and press the Enter key to select one.

4. Press the hotkey for “Update” to add new user.

!The Web and CLI interfaces restricts the maximum number of users to 10. If 10 users exist, an error message will be displayed. Delete an old user to add a new one.

DRAFT



5.8 Delete / Edit User EntryNavigation Tree > Administration > Maintenance > Delete User/Edit User Entry

Figure 13 Delete User

This screen shown in Figure 13 enables the administrators of a terminal to delete users from the terminal. The page also allows a user to change the password of any user whose access level is less than or equal to his own.

– Delete User – Username of user to be removed.– Change Password – Change Password of the selected User.

☞ A user can change his own password and the passwords of users whose access level is equal or less than his own.

DRAFT

DRAFT


33


5.8.1 CLI Configuration

Figure 14 Delete/Edit User Entry

Figure 14 shows the CLI version of the Delete/Edit User Entry screen. The options listed on this page are:

1. Username – Select the username to change his password.2. Change Password – Enter the new password for the selected user.3. Confirm Password – Confirm the new password.4. Update – Update the change in the password in the selected user profile.5. Username – Select the username to remove his entry.6. Delete User – Delete the selected user.

To use this screen:

1. Navigate to Administration → Maintenance → User Management → Edit/Delete User Entry.

2. To change the password, select the username and enter new password, confirm the entered password and press the hotkey to Update new password.

3. To delete a user, select the username and press the hotkey for Delete User.

5.8.2 WEB Configuration1. Navigate to Administration → Maintenance and click on the “Del User” link on the

left panel.2. Select the user to be removed from the drop down menu.3. Click the “Delete” button to remove the user from the terminal.

The default “admin” user cannot be deleted.

☞ To change the password for a particular user, first remove the user from the terminal and then add it again.

DRAFT



5.9 View Event LogNavigation Tree > Administration > Maintenance > View Event Log

Figure 15 Event Log

5.9.1 WEB Location1. Navigate to Administration → Maintenance → View Event Log in the left panel.2. The Event Log description and time parameters are displayed.3. Click the “Clear” button to clear the Event Log.

5.9.2 CLI Location1. To display the read-only Event Log, navigate to Administration → Maintenance →

View Event Log.2. To Clear the Event Log, navigate to Administration → Maintenance and select the

hotkey for Clear Event.

DRAFT

DRAFT


35


5.10 System Reboot

Figure 16 System Reboot

☞ Only the reboot of the Controller Card is error-free.

☞ If the ODUs are squelched, after the reboot the ODUs become active (except for the ODU in standby in protected not diversity configuration).

The screen shown in Figure 16 enables the user to reboot the terminal or certain devices within the terminal. It will display a list of devices and the user can select a device based on the availability and configuration of the devices.

5.10.1 WEB Configuration1. Select the device to reboot from the list.2. Click “reboot” button.

5.10.2 CLI Configuration1. Navigate to System Screen2. Select the Device to reboot using the Space Bar key and press the Enter key to

select.3. Press the hotkey for “Reboot”.4. When confirmation is asked, press “y” to proceed or “n” to cancel.5. A success or failure indicating message will be displayed.

DRAFT



5.11 Active AlarmsNavigation Tree > Analysis > Alarms > Active Alarm

Figure 17 Active Alarms

This screen shown in Figure 17 displays active alarm information including:

– Description – Description (name) of the alarm.– Time - The time at which this particular alarm sets

☞ The last 100 alarms are stored in non-volitile memory and will be available after a power cycle.

5.11.1 WEB Configuration1. Navigate to Analysis → Alarms → Active in the left panel.2. The Active Alarms information screen is displayed.

5.11.2 CLI Configuration1. Navigate to Analysis → Alarms → Active Alarms.2. The Active Alarms information screen is displayed.

DRAFT

DRAFT


37


5.12 Alarm HistoryNavigation Tree > Analysis > Alarms > Alarm History

Figure 18 Alarm History

This screen lists alarms that have occurred and their description, status, and time (see Figure 18). A maximum of 300 alarms can be displayed. If the alarm history exceeds 300 alarms, the oldest alarms will be removed/overwritten.

The following items are displayed on this page:

– Description – Description (name) of the alarm.– Status – Status of alarm (set/reset).– Time - The time at which the particular alarm sets/resets.– Clear History – The button used to clear the Alarm History records.

The current alarm state can be obtained from the SNMP manager by reading an MIB object ccmSDIDUAlarmStatus from the ccmSDIDUAnalysis section. Status will be returned as string, for example

1=I:2=I:3=I:4=I:5=A:6=I:7=I:8=I:9=I:10=I:11=I:

where “I” indicates that the alarm is inactive and “A” indicates the alarmed state.

☞ During link configuration procedures, or module replacement or SFP replacement the Alarm History trace could contain less alarms than those notified in Active Alarm List or via SNMP interface.

DRAFT



5.13 GraphsNavigation Tree > Analysis > Graphs > RSL

Figure 19 RSL Plot

Navigation Tree > Analysis > Graphs > Signal/Noise

Figure 20 SNR Plot

Navigation Tree > Analysis > Graphs > Tx Power

DRAFT

DRAFT


39


Figure 21 Tx Power

Navigation Tree > Analysis > Graphs > Error Seconds

DRAFT



Figure 22 Error Seconds Plot

Navigation Tree > Analysis > Graphs > Equalizer Taps

Figure 23 Equalizer Taps

Navigation Tree > Analysis > Graphs > Constellation

DRAFT

DRAFT


41


Figure 24 Constellation Display (128 QAM)

Navigation Tree > Analysis > Graphs > Mux/Demux

Figure 25 STM Mux/Demux Regenerator Section

DRAFT



Figure 26 STM Mux/Demux Line Section

Figure 27 Temperature

This screen graphically displays the following parameters:

DRAFT

DRAFT


43


– East RSL– West RSL– East Signal/Noise– West Signal/Noise– East TX power– West TX power– East Error second count– West Error second count.– East Equalizer Taps– West Equalizer Taps– East Constellation– West Constellation– Mux/Demux– Temperature

For parameters 1-8, the last 24 hours of data will be plotted with the parameter along the Y-axis (vertical) and time along the X-axis (horizontal) as in Figure 20.

Equalizer Taps and Constellations are plotted as shown in Figure 21 and Figure 22.

5.13.1 WEB Configuration1. Navigate to Analysis and click on the “Graphs” link on the left panel.2. Based on the ODU operation mode configuration, the number of graphs displayed

will differ. For example, if the ODU operation is East-West, all 8 parameters’ graphs will be accessible. If the ODU operation mode is not East-West, only 4 (either East or West) graphs will be accessible.

3. Select any one link to view the graph of that parameter.4. The X-axis time range can be selected (from 1,2,4,12 or 24). If 1 hour is selected, it

will plot the graph using last hour of data.5. When the mouse is moved over the graph area, the corresponding value at the

mouse point will be displayed under the graph area. This enables the user to easily read X and Y values.

5.13.2 CLI ConfigurationNot available.

DRAFT



5.14 Statistics – Data SwitchNavigation Tree > Analysis > Statistics > Data Switch

Figure 28 Statistics – Data Switch

This screen indicates:

– STP Status– Port Speed– PortDuplex– FlowControl– Rx Bytes– Rx Bytes/sec– TX Bytes– TX Bytes/sec– Rx Frames– Rx Frames/sec– TX Frames– TX Frames/sec– Errors– Errors/sec– Collisions– Collisions/sec

DRAFT

DRAFT


45


for Port 1, Port 2 (Port 3 and Port 4 also for Gigabit Master IO Module), CPU, Radio Link (East) and Radio Link (West) of the Data Switch, as shown in Figure 28.

☞ When the flow control is working, the flow control in the row of the DataSwitchSta-tistics screen is always shown as "Symmetric", also if in the Ethernet Payload Con-figuration menu the flow control has been set as "Symmetric", "Receive only" or "Transmit only" (as shown in the following Ethernet Payload Configuration screen).

When the flow control is not working, the flow control in the row of the DataSwitch-Statistics screen is always shown as "Disabled", also if in the Ethernet Payload Con-figuration menu the flow control has been set as "Disabled" or "Transmit only".

Figure 29 Ethernet Payload Configuration

5.14.1 WEB Configuration1. Navigate to Analysis → Statistics → Data Switch link on the left panel.2. The Data Switch Statistics screen is displayed.3. Press the “Clear” button to clear the data and start accumulating again.

5.14.2 CLI Configuration1. Navigate to Analysis → Data Switch Statistics.

DRAFT



2. The Data Switch Statistics screen is displayed.3. Select the hotkey “Clear” to clear the data and start accumulating again.

DRAFT

DRAFT


47


5.15 Statistics – NMS SwitchNavigation Tree > Analysis > Statistics > NMS Switch

Figure 30 NMS Switch Statistics

This screen indicates:

– STP Status– Port Speed– PortDuplex– FlowControl– Rx Bytes– Rx Bytes/sec– TX Bytes– TX Bytes/sec– Rx Frames– Rx Frames/sec– TX Frames– TX Frames/sec– Errors– Errors/sec– Collisions– Collisions/sec

DRAFT



for Port 1, Port 2, CPU, Radio Link (East) and Radio Link (West) of the NMS Switch, as shown in Figure 30.

5.15.1 WEB Configuration1. Navigate to Analysis → Statistics and click on the “NMS Switch” link on the left

panel.2. Press the “Clear” button to clear the data and start accumulating again.

5.15.2 CLI ConfigurationNavigate to Analysis → SNMP Switch Statistics.

DRAFT

DRAFT


49


5.16 ODU TraceNavigation Tree > Analysis > ODU Trace

Figure 31 ODU Trace

Customer Service may ask the user to use the ODU Trace screen for debugging pur-poses.

The screen shown in Figure 31 is used to communicate with ODU directly by sending commands and receiving the responses. The following items are displayed:

– ODU selection – To select East or West ODU.– Status messages – To enable/disable status messages.– Text field – To enter a command to ODU.– Send command button – By pressing this button, the command entered in the text

field is sent to the ODU.– Text Area – To display the response message from ODU.

☞ The ODU Trace Screen is available only for some ODU types.

5.16.1 WEB Configuration1. Navigate to Analysis and click on the “ODU trace” on the left panel.2. Enter the command in the text field.3. Click “send command” button.4. After few seconds (depending on your network speed) the response from ODU for

the given command will be displayed in the text area.

DRAFT



5. Each time a new response message is received, it is appended at the end of the text field. Use the scroll bar to see all the messages.

☞ The ODU may generate unsolicited messages without any command being sent from this screen. These messages are also appended in the text area.

☞ To copy & save the response messages:

1. Click inside the text area.2. Press Ctrl+A and Ctrl+C.3. Open notepad (or any text editor) and press Ctrl+V.4. Save the file.


DRAFT

DRAFT


51


5.17 Modem TraceNavigation Tree > Analysis > Modem Trace

Figure 32 Modem Trace

Customer Service may ask the user to use the Modem Trace for debugging purposes.

The screen shown in Figure 32 is used to communicate with MODEM directly by sending commands and receiving the responses. The following items are displayed:

– MODEM selection – To select East or West MODEM.– Status message – To enable/disable status messages.– Text field – To enter a command to MODEM.– Send command button – By pressing this button the command entered in the text

field is sent to the MODEM.– Text Area – To display the response messages from MODEM.

5.17.1 WEB Configuration1. Navigate to Analysis and click on the “MODEM trace” link on the left panel.2. Enter the command in the text field.3. Click the “send command” button.4. After a few seconds (depending on your network speed) the response from MODEM

for the given command is displayed in the text area.5. Each time a new response message is received, it is appended at the end of the text

field. Use the scroll bar to see all the messages.

DRAFT



☞ The MODEM may generate unsolicited messages without any command being sent from this screen. These messages are also appended in the text area




DRAFT

DRAFT


53


5.18 BERT ModeNavigation Tree > Analysis > BERT Trace

Figure 33 BERT Mode

☞ The BERT mode cause a loss of payload, make sure that no traffic are loaded on the MW link.

This screen is used to communicate with the MODEM directly by sending a command and receiving the response (see Figure 33). The following items are displayed:

– East/West Enable/Disable - To select East/West and Enable/Disable.– “Clear” button - Send the “clear” command to the MODEM.– Insert Bit Error - Insert a bit error– Text Area - To display the response messages from MODEM.– Cumulative Bits - Total number of bits– Cumulative Bit Error - Total number of error bits– Bit Error Rate - Percentage of error bits

To use the BERT functions, the BERT mode has to be independently enabled at both ends of the link because there is no separate NMS stream when operating in BERT mode. To this concern two PCs willbe used, one connected directly to the NMS port of each equipment.

5.18.1 WEB ConfigurationTo begin testing:

1. Navigate to Analysis and click on the “BERT mode” on the left panel.

DRAFT



2. Enable one of the BERT modes.a) Click on one command. (East Enable or West Enable).b) After a few seconds (depending on your network speed) the response from MODEM for the given command will be displayed in the text area.c) Enabling this mode will generate random data over the link causing the other SDIDU to trigger the buzzer thus generating noise.

3. Enable the other BERT mode. This should silence the buzzer noise.4. Send the “Clear” command to both equipments to reset the cumulative bits, cumu-

lative bit errors, and bit error rate counters.a) Click on the “Clear” button.b) After a few seconds (depending on your network speed) the response from MODEM for the given command will be displayed in the text area.

5. Every time the response message is received it is appended at the end of the text field. Use the scroll bar to see all the messages.

6. To insert an error and see whether the modem catches it, click on the “Insert Bit Error” button.

To stop testing:

1. Disable one of the SDIDU's BERT mode.a) Click on one command. (East Disable or West Disable),b) This will cause the SDIDU to generate buzzer noise.

2. Disable the other SDIDU's BERT mode, this should silence the buzzer noise.

Number of Bits, Bit Errors, and BER will be accumulated until the BERTs are disabled, or the SDIDUs are power cycled and will clear the BERT mode.

☞ The MODEM may generate unsolicited messages without any command being sent from this screen. These messages are also appended in the text area




DRAFT

DRAFT


55


5.19 CW ModeNavigation Tree > Analysis > CW Trace

Figure 34 CW Mode

This screen allows the user to enable or disable CW mode (see Figure 34).

When set to CW mode, the modem generates a tone rather than a modulated signal. This mode is used for non-operational purposes, such as calibration and pointing.

5.19.1 WEB ConfigurationSelect required mode (East/West) and press the “Enable” or “Disable” button. A status message will be displayed to indicate success/failure. When CW mode is enabled, the transmitter status in the “status panel” (Right side panel) will display “CW Mode”.


DRAFT



5.20 LoopbackNavigation Tree > Analysis > Loopback

Figure 35 Loopback

This screen enables the user to start or stop Loop Back (see Figure 35).

☞ The Remote LIU loopback will be implemented on the remote equipment (not on the local equipment as the other loopbacks).

5.20.1 WEB Configuration1. Navigate to Analysis → Loopback.2. Select the type of loopback (Local LIU (Refer to Figure 36), Local Modem (Refer

to Figure 37) or Remote LIU (Refer to Figure 38)).3. If Local or Remote LIU is selected then select the LIU type from the drop down

option.4. Select the duration of the loopback.5. Press the start Button to start loopback.6. If loopback is running, press the stop button to stop it.

Figure 36 Local LIU loop in IDU1

☞ Alarm BERT/LB/CW Test Mode is active in IDU1 after the loop activation in IDU1.

DRAFT

DRAFT


57


Figure 37 Local Modem loop in IDU1

Figure 38 Remote LIU loop in IDU1

☞ Alarm BERT/LB/CW Test Mode is active in IDU2 after the loop activation in IDU1.

5.20.2 CLI Configuration1. Navigate to Analysis → LoopBack.2. Select the type of loopback (Local LIU, Local Modem or Remote LIU) by pressing

appropriate hotkey and the space bar.3. If Local or Remote LIU is selected then select the LIU type.4. Select the duration of the loopback by pressing appropriate hotkey and the space

bar.5. To start loopback, press the hotkey for Start.6. To revert to the previous value, press the “Esc” key while editing the value7. If loopback is running, press the hotkey for stop to stop it.

DRAFT



5.21 LogoutNavigation Tree > Logout

Figure 39 Logout

The page shown in Figure 39 enables the user to logout from the Web Interface.

In the case of Internet Explorer, the logout link will close the browser. For other brows-ers, the user may have to close and reopen the browser.

DRAFT

DRAFT


59

Operate and Maintain Upgrading procedure

6 Upgrading procedure

6.1 Software componentsTable 4 shows the current version for each software upgradeable component. Only the components, whose version is older than that shown in Table 4, needs to have the related file uploaded. At the end of the upgrade procedure the active version should be like those shown in Table 4. The table shows also the Directory, which stores the SW component file.

Directory Component Reprogramming Screen Version

Filename Upgraded relative to previous

SVR

FlexiHybrid SVR 2_1 Kernel 0.3.3 kernel.img Yes

FlexiHybrid SVR 2_1 Application 2.4.13x puma_app.img Yes

FlexiHybrid SVR 2_1 ODU Library N2-2.4.13 odu.img Yes

Standard Master IO(612-31501)

FPGA Standard Master IO (612-315/01)

4100_STD_71 ffpga_4100_STD_71.img Yes (Not released in SVR 2.0)

Standard2 Master IO(612-31537)

FPGA Standard2 Master IO (612-315/37)

4101_STD_07 ffpga_4101_STD_07.img Yes

GigE Master IO(612-31510)

FPGA GigE Master IO (612-315/10)

4110_GE_19 ffpga_4110_GE_19.img Yes

Enhanced Master IO(612-31515)

FPGA Enhanced Master IO (612-315/15)

4120_STM_39 ffpga_4120_STM_39.img Yes (Not released in SVR 2.0)

Enhanced2 Master IO(612-31539)

FPGA Enhanced2 Master IO (612-315/39)

4121_STM_06 ffpga_4121_STM_06.img Yes

GigE Enhanced Master IO (612-31516)

FPGA GigE Enhanced Master IO (612-315/16)

4130_SGE_8 ffpga_4130_SGE_8.img Not sup-ported in all previous SVR

16E1 expansion IO (612-31505)

FPGA 16E1 expansion IO (612-315/05)

21 opt_io_framer_fw.bz2 No

42E1 Master IO (612-31503)

FPGA 42E1 Master IO (612-315/03)

4142_SP_20 ffpga_4142_SP_20.img Yes

21E1 expansion IO (612-31506)

FPGA 21E1 expansion IO(612-315/06)

3 opt_io_framer_fw.bz2 No

Table 4 Software current version

DRAFT


Operate and MaintainUpgrading procedure

Controller (634-00181)

FPGA Controller (634-001/81)

v27 cfpga.img No

Controller2 (634-00191)

FPGA Controller2 (634-001/91)

4501_v7 cfpga.img Yes

Modem WB7-56(612-31530)

Modem East F/W WB7-56 (612-315/30)

W-1.1.19 east_modem_fw.bz2 Yes

Modem West F/W WB7-56(612-315/30)

W-1.1.19 west_modem_fw.bz2 Yes

Modem East FPGA WB7-56 (612-315/30)

18 east_modem_fpga.bz2 Yes

Modem West FPGA WB7-56 (612-315/30)

18 west_modem_fpga.bz2 Yes

FlexiHybrid SVR 2_1 Bootloader 1.3.2 u-boot.bin Yes

- E1/T1 channel map N/A e1t1channel_map.csv No

Channel_CN-1 Channel CN-1 channel.img No

MODES-N2-V7A Modes N2-7A modes.img Yes

Directory Component Reprogramming Screen Version

Filename Upgraded relative to previous

SVR

Table 4 Software current version (Cont.)

DRAFT

DRAFT


61


6.2 IDU software upgrade procedure from SVR 1.1 to SVR 2.1– Replace Modem WB14-56 (612-315/02) with the Modem WB7-56 (612-315/30).– Upgrade 16M to 32M Flash Map.

6.2.1 RequirementsThe following set of conditions needs to be verified before upgrading from 16MB flash map to 32MB flash map:

1. Power should not fail during transition from 16MB flash map to 32MB flash map.2. IDU controller card should have 32MB Flash.

☞ If the intermediate U-Boot Image (Version - INT.1) is uploaded to IDU having 16MB Flash, transition will not happen and IDU will boot normally.

6.2.2 Software ComponentsTable 5 shows the components required for the upgrade.

6.2.3 Upgrade ProcedureThe following set of procedures MUST be followed to upgrade from 16MB flash map to 32MB flash map. Refer to paragraph 6.2.4 FTP File Transfers for help with FPT.

1. Open the WEB User Interface to the IDU that you are upgrading.2. Navigate to the Administration > Maintenance > Reprogramming screen.3. Load bank 2 with the current Application, ODU Library, FPGA, Modes and Channels

files if they are not there already.4. Toogle the Application, ODU Library, FPGA, MODES and CHANNELS to bank 2 on

the Reprogramming Screen.☞ If the fpga.img file loaded is for an Enhanced Master IO Card such as 27-STM24,

the FPGA bank 2 will appear as N/A.There is no need to toggle the FPGA to bank 2 before starting the upgrade in this case.

5. Load the current Kernel into bank 1 and toggle to it.

Component Reprogramming Screen Version

Filename Notes

32M Compatible Kernel 0.2.0 kernel.img

Intermediate Bootloader INT.1 u-boot.bin This file performs the actual 16M to 32M FLASH map upgrade

32M Compatible Bootloader 1.2.0 u-boot.bin

Table 5 Components for the upgrade

DRAFT



6. The following screen is an example of how the reprogramming screen should appear. ODU FIRMWARE, BOOTLOADED and MODEM FIRMWARE aren’t required to be changed.

7. Reboot the Controller Card by navigating to the Administration > Reboot screen.8. After the IDU reboots, upload Intermediate U-Boot Image “u-boot.bin” (Version -

INT.1) sing FTP.9. Upload Kernel Image “kernel.img” (Version - 0.2.0) through FTP to bank 2.10. Toggle the Kernel Image to bank 2.11. The following screen is an example of how your Reprogramming Screen is

REQUIRED to look before starting the FLASH remapping step. In other words, the RED Dots shall be on bank 2 for the Application, ODU Library, FPGA, MODES and CHANNELS.

12. Make sure the version number of U-Boot image is INT.1 and version number of active kernel bank 2 image is 0.2.0.

13. Reboot the Controller Card by navigating to the Administration > Reboot screen.

DRAFT

DRAFT


63


14. Output messages during transition process can be viewed through serial con-sole.Example output messages are shown in paragraph 6.2.5 Output Messages.

15. Transition process requires at least 15 minutes to complete.Access the WEB User Interface or ping the IDU to make sure IDU has booted up.

16. Upload new U-Boot Image “u-boot.bin” (Version - 1.2.0) through FTP.17. Make sure the version number of U-Boot image is 1.2.0.18. Reboot the Controller Card by navigating to the Administration > Reboot screen.

6.2.4 FTP File Transfers☞ The FileZilla FTP client may cause FTP upload errors as it sometimes uses non-

standard commands for uploading files. We have tested NcFTP and have had good results. While NcFTP is command-line based, it can be scripted to ease upgrading of IDUs.

1. Start with a powered-on IDU.2. Use an FTP client and connect to the IDU via IP address

a) If using the Windows FTP client, open a DOS window and change directory to the directory containing the 1.4.11a files.1. Enter command “ftp <ipaddress of SDIDUTM>”2. When prompted enter username “integrator” and password “p1nacate”3. Set to binary mode by entering “bin”4. Upload the appropriate filesby entering “put <filename>”5. Exit

b) If using a graphical FTP client such as FileZilla1. Use the following parameters to connect:

– Host: <ipaddress of SDIDUTM>– Username “integrator”; password “p1nacate”

2. Connect to IDU (see FTP client Help)3. Set tobinary mode (see FTP client Help)4. Set timeout detection to 999 seconds (see FTP client Help)5. Copy the appropriate files from the PC to the IDU6. Exit the FTP client.

6.2.5 Output MessagesConnect a serial port to the serial console of controller card. The following output should occur if the FLASH remap takes place. If your controller card has only a 16M FLASH part, the controller will boot normally using uboot image INT.1.

In the cae of the controller card only having a 16M FLASH, the 1.1.x uboot.img (ex: 1.1.27) should be uploaded to continue normal operation.

DRAFT



An example output message during transition from 16MB flash map to 32MB flash map is the following:

DRAFT

DRAFT


65


DRAFT



DRAFT

DRAFT


67


– Upload SVR 2.1.

1. Start with a powered-on FlexiHybrid connected to a personal computer via IP address

2. Open the WEB User Interface of the FlexiHybrid to be upgraded3. Click on Administration > Maintenance > Re-programming4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address5. Upload the Boot 1.3.2 from the sub-directory SW7_7\FlexiHybrid SVR 2_1_1\

through FTP6. Upload the Kernel 0.3.3 from the sub-directory SW7_7\FlexiHybrid SVR 2_1_1\

through FTP7. Upload the FPGA of the Controller unit v27 from the sub-directory SW7_7\Controller

(634-00181) or the FPGA of the Controller2 unit 4501_v7 from the sub-directory SW7_7\Controller2 (634-00191)\ through FTP

8. Upload the FPGA of the installed Master IO unit from the subdirectory from the sub-directory SW7_7\ through FTP

9. Upload the Application 2.4.13x from the sub-directory SW7_7\FlexiHybrid SVR 2_1_1\ through FTP

10. Upload the ODU library N2-2.4.13 from the sub-directory SW7_7\FlexiHybrid SVR 2_1_1\ through FTP

11. Upload the FPGA of the installed Expansion unit (version 21 from the sub-directory SW7_7\16E1 expansion IO (612-31505)\ for 16 channel expansion unit, version 3 from the sub-directory SW7_7\21E1 expansion IO (612-31506)\ for 21 channel expansion unit), if any, through FTP

12. Click on Administration > Maintenance > Re-programming in order to refresh the Reprogramming screen

13. Check the Application box and ODU library box, the Kernel box, the FPGA Controller box and the FPGA Master box press TOGGLE button

14. Reboot the IDU by navigating to the Administration > Reboot screen15. When the FlexyHybrid is reachable again via IP address, click on Administration >

Maintenance > Re-programming16. Connect again the FTP client to FlexiHybrid via IP address17. Repeat all the above steps (6-11) for the other bank. Bank 1 and Bank 2 must be

aligned (same software in both banks)

DRAFT



18. When the FlexyHybrid is reachable again via IP address, click on Administration > Maintenance > Re-programming

19. Connect again the FTP client to FlexiHybrid via IP address20. Upload the modem Firmware W-1.1.19 of the East Modem (and of the West Modem

if present) from the sub-directory SW7_7\Modem WB7-56 (612-31530)\ through FTP (see NOTE 2)

21. Upload the modem FPGA 18 of the East Modem (and of the West Modem if present) from the sub-directory SW7_7\Modem WB7-56 (612-31530)\ through FTP (see NOTE 2)

22. Upload the modes N2-7A from the sub-directory SW7_7\MODES-N2-V7A\ through FTP

23. Upload the channel CN-1 from the sub-directory SW7_6\Channel_CN-1\ through FTP


25. Check the Modes box and Channel box and press TOGGLE button26. Repeat all the above steps (22-24) for the other bank. Bank 1 and Bank 2 must be

aligned27. Perform a Link Configuration28. Click on Administration > Maintenance > Re-programming in order to check if the

SVR has been successfully upgraded29. Upload the E1 channel map from the sub-directory SW7_7\ through FTP30. Upload the NSN company logo and the product name pictures from the sub-direc-

tory SW7_7\NSN_Graphics\ through FTP31. Refresh the browser in order to see the correct NSN company logo and product

name

☞ Note 1: Extra help for FTP client:

a) If using the Windows FTP client, open a DOS window and change directory to the directory containing the SVR files.1. Enter command "ftp <ipaddress of FlexiHybrid>".2. When prompted enter username "integrator" and password "p1nacate"3. Set to binary mode by entering "bin"4. Upload the appropriate files by entering "put <filename>"5. Exit


– Host: <ipaddress of FlexiHybrid >– Username "integrator"; password "p1nacate"

2. Connect to FlexiHybrid (See FTP client Help)3. Set to binary mode (see FTP client Help)4. Set timeout detection to 999 seconds (see FTP client Help)5. Uncheck Use multiple connections to transfer files box

☞ Note 2: Extra help for downloading modem firmware and FPGA:

There are two steps that occur internally on the system when you ftp the modem firmware and FPGA onto the FlexiHybrid.

1. The ftp process places the firmware or FPGA on the FlexiHybrid.

DRAFT

DRAFT


69


2. The FlexiHybrid system software copies the file onto the modem.

Step (1) above completes and the FlexiHybrid keeps the ftp connection open. Your ftp client may time out and can give you some type of "connection closed" error message.

At this time, step (1) is complete and the file is being copied to the modem. If you restart the FlexiHybrid, the copy process will get killed; and, you will have no firmware or FPGA in the modem.

Please do the following to upload modem firmware and FPGA.

Please upload the modem firmware or FPGA via ftp to the FlexiHybrid (step 1 above). Step (2) can take 5-8 minutes. DO NOT reboot the FlexiHybrid during this time.

While step (2) is taking place the modem LED will turn off (wait ~5 minutes). You will know when the download to the modem completes when the modem LED starts blinking again.

When this occurs, the download is complete. If you refresh the Reprogramming screen, you will see the new firmware or FPGA version listed in the EAST or WEST MODEM FIRMWARE or FPGA row depending on the firmware or FPGA you down-loaded. You do not have to toggle modem firmware or FPGA since the modems have only 1 memory bank.

Warning: Ethernet ports could shutdown during FTP modem transfer if the feature shutdown on link failure of the Ethernet ports is enable.

DRAFT



6.3 IDU software upgrade procedure from SVR 1.2, SVR 1.3, SVR 1.4 and SVR 2.0 to SVR 2.1Before following the next steps, the Flash memory partition must be verified (see para-graph 6.3.1 for further details).1. Start with a powered-on FlexiHybrid connected to a personal computer via IP

address2. Open the WEB User Interface of the FlexiHybrid to be upgraded3. Click on Administration > Maintenance > Re-programming4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address5. Upload the Boot 1.3.2 from the sub-directory SW7_7\FlexiHybrid SVR 2_1_1\

through FTP6. Upload the Kernel 0.3.3 from the sub-directory SW7_7\FlexiHybrid SVR 2_1_1\

through FTP7. Upload the FPGA of the Controller unit v27 from the sub-directory SW7_7\Controller

(634-00181) or the FPGA of the Controller2 unit 4501_v7 from the sub-directory SW7_7\Controller2 (634-00191)\ through FTP

8. Upload the FPGA of the installed Master IO unit from the subdirectory from the sub-directory SW7_7\ through FTP

9. Upload the Application 2.4.13x from the sub-directory SW7_7\FlexiHybrid SVR 2_1_1\ through FTP

10. Upload the ODU library N2-2.4.13 from the sub-directory SW7_7\FlexiHybrid SVR 2_1_1\ through FTP

11. Upload the FPGA of the installed Expansion unit (version 21 from the sub-directory SW7_7\16E1 expansion IO (612-31505)\ for 16 channel expansion unit, version 3 from the sub-directory SW7_7\21E1 expansion IO (612-31506)\ for 21 channel expansion unit), if any, through FTP


13. Check the Application box and ODU library box, the Kernel box, the FPGA Controller box and the FPGA Master box press TOGGLE button

14. Reboot the IDU by navigating to the Administration >Reboot screen15. When the FlexyHybrid is reachable again via IP address, click on Administration >


aligned (same software in both banks)18. When the FlexyHybrid is reachable again via IP address, click on Administration >

Maintenance > Re-programming19. Connect again the FTP client to FlexiHybrid via IP address20. [Only for protected system Hot Stand-by (1+1) In case of unprotected system skip

to step 21]:a) It is recommended to disable the command "Power ODU after Switch" in Protec-

tion Configuration menu.b) Navigate to Protection Configuration and verify which ODU is online.c) It is recommended to disable the command "APS Switch" in Protection Config-

uration menu.d) Upgrade the modem in stand-by see steps 21 and 22 (following NOTE 2).

DRAFT

DRAFT


71


e) Switch to the other modem by Switch Transmitting ODU.f) Upgrade other modem previously active, see steps 21 and 22 (following NOTE

2).g) Set again the needed protection parameters.

21. Upload the modem Firmware W-1.1.19 of the East Modem (and of the West Modem if present) from the sub-directory SW7_7\Modem WB7-56 (612-31530)\ through FTP (see NOTE 2)


23. Upload the modes N2-7A from the sub-directory SW7_7\MODES-N2-V7A\ through FTP

24. Upload the channel CN-1 from the sub-directory SW7_6\Channel_CN-1\ through FTP


26. Check the Modes box and Channel box and press TOGGLE button27. DO NOT perform any Link Configuration even if the the led Bank is red in Repro-

gramming window on WebLCT28. Repeat all the above steps (22-24) for the other bank. Bank 1 and Bank 2 must be

aligned29. Upload the E1 channel map from the sub-directory SW7_7\ through FTP30. Upload the NSN company logo and the product name pictures from the sub-direc-

tory SW7_7\NSN_Graphics\ through FTP31. Refresh the browser in order to see the correct NSN company logo and product

name32. Verify that in local and remote site the SVR 2.1.1 has been correctly uploaded33. Perform a Link Configuration34. Click on Administration > Maintenance > Re-programming in order to check if the

SVR has been successfully upgraded.


a) If using the Windows FTP client, open a DOS window and change directory to the directory containing the SVR files.1. Enter command "ftp <ip address of FlexiHybrid>"2. When prompted enter username "integrator" and password "p1nacate"3. Set to binary mode by entering "bin"4. Upload the appropriate files by entering "put <filename>"5. Exit


– Host: <ip address of FlexiHybrid >– Username "integrator"; password "p1nacate"


DRAFT





1. The ftp process places the firmware or FPGA on the FlexiHybrid.2. The FlexiHybrid system software copies the file onto the modem.







6.3.1 Flash memory size preliminary checkIn order to perform a correct upgrade to SVR 2.1, the controller flash memory partition must be verified following next steps.

a) Start the Command Line Interface (CLI) login prompt using the Serial Console con-nection or Telnet connection by LAN cable if the IP Address is known.

b) Login with username 'root' and password 'arct1c'.c) At the command prompt type 'df -h' as shown below:

DRAFT

DRAFT


73


Figure 40 Command prompt screenshot

d) If the /dev/mtbblock9 size is 7.0M, the 32M FLASH map is already in place and the upgrade procedure can be executed without any additional procedure. Skip this paragraph and go to paragraph 6.3 to upgrade the SDIDU to SVR 2.1 following the procedure.

e) If the flash partition size is different from 7.0 M follow the procedure concerning the FLASH re-sizing described by the Technical Support Note (TS-MWR-SW-0067) before applying the upgrade to SVR 2.1.

DRAFT



6.4 IDU software upgrade procedure from SVR 1.2, SVR 1.3 or SVR 1.4 to SVR 2.1 with HW upgrade1. Switch the old controller 634-00181 with the new one 634-001912. Switch the old master IO board with the new one3. Start with a powered-on FlexiHybrid connected to a personal computer via IP

address4. Open the WEB User Interface of the FlexiHybrid to be upgraded5. Click on Administration > Maintenance > Re-programming6. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address7. Upload the FPGA of the installed Master IO unit from the subdirectory from the sub-

directory SW7_7\ through FTP8. Click on Administration > Maintenance > Re-programming in order to refresh the

Reprogramming screen9. Check the FPGA Master box and press TOGGLE button10. Upload the FPGA of the installed Expansion unit (version 21 from the sub-directory

SW7_7\16E1 expansion IO (612-31505)\ for 16 channel expansion unit, version 3 from the sub-directory SW7_7\21E1 expansion IO (612-31506)\ for 21 channel expansion unit), if any, through FTP.



aligned (same software in both banks)15. Upload the modem Firmware W-1.1.19 of the East Modem (and of the West Modem

if present) from the sub-directory SW7_7\Modem WB7-56 (612-31530)\ through FTP (see NOTE 2)


17. Click on Administration > Maintenance > Re-programming in order to check if the SVR has been successfully upgraded





2. Connect to FlexiHybrid (See FTP client Help)3. Set to binary mode (see FTP client Help)

DRAFT

DRAFT


75


4. Set timeout detection to 999 seconds (see FTP client Help)5. Uncheck Use multiple connections to transfer files box











DRAFT



6.5 IDU software downgrade procedure from SVR 2.1 to SVR 2.01. Start with a powered-on FlexiHybrid connected to a personal computer via IP

address2. Open the WEB User Interface of the FlexiHybrid to be upgraded3. Click on Administration > Maintenance > Re-programming4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address5. Upload the Boot 1.3.1 from the sub-directory SW7_4\FlexiHybrid SVR 1_3\ through

FTP6. Upload the Kernel 0.3.1 from the sub-directory SW7_4\FlexiHybrid SVR 1_3\

through FTP7. Upload the FPGA of the installed Master IO unit from the sub-directory SW7_6\

through FTP (Note: Standard Master IO (612-315/01), Enhanced Master IO (612-315/15) and GigE Enhanced Master IO (612-315/16) are not supported with SVR 2.0)

8. Upload the Application 2.0.18x from the sub-directory SW7_6\FlexiHybrid SVR 2_0\ through FTP

9. Upload the ODU library N2-2.0.18v2 from the sub-directory SW7_6\FlexiHybrid SVR 2_0\ through FTP


11. Check the Application box and ODU library box and FPGA Master box and press TOGGLE button



aligned (same software in both banks)16. Upload the modem Firmware W-1.1.3v18t15c of the East Modem (and of the West

Modem if present) from the sub-directory SW7_6\Modem WB7-56 (612-31530)\ through FTP (see NOTE 2)



19. When the FlexyHybrid is reachable again via IP address, click on Administration > Maintenance > Re-programming in order to check if the SVR has been successfully downgraded

20. Upload the modes N2-1B from the sub-directory SW7_6\MODES-N2-V1B\ through FTP


22. Check the Modes box and press TOGGLE button23. Repeat all the above steps (20-21) for the other bank. Bank 1 and Bank 2 must be

aligned

DRAFT

DRAFT


77


24. Perform a Link Configuration
















DRAFT



6.6 IDU software downgrade procedure from SVR 2.1 to SVR 1.4☞ Controller2 (634-001/91) is not supported with SVR 1.4


2. Open the WEB User Interface of the FlexiHybrid to be upgraded3. Click on Administration > Maintenance > Re-programming4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address5. Upload the Boot 1.3.1 from the sub-directory SW7_4\FlexiHybrid SVR 1_3\ through



through FTP (Note: Standard2 Master IO (612-315/37), Enhanced2 Master IO (612-315/39) and GigE Enhanced Master IO (612-315/16) are not supported with SVR 1.4)

8. Upload the Application 2.0.12x from the sub-directory SW7_5\FlexiHybrid SVR 1_4\ through FTP

9. Upload the ODU library N2-2.0.12v3 from the sub-directory SW7_5\FlexiHybrid SVR 1_4\ through FTP


11. Check the Application box and ODU library box and press TOGGLE button12. Click on Administration > Maintenance > Re-programming in order to refresh the

Reprogramming screen13. Check the FPGA Master box and press TOGGLE button14. Reboot the IDU by navigating to the Administration > Reboot screen15. When the FlexyHybrid is reachable again via IP address, click on Administration >


aligned (same software in both banks)18. Only for protected system Hot Stand-by (1+1) In case of unprotected system skip to

step 19]:a) It is recommended to disable the command "Power ODU after Switch" in Protec-

tion Configuration menub) Navigate to Protection Configuration and verify which ODU is onlinec) It is recommended to disable the command "APS Switch" in Protection Config-

uration menud) Upgrade the modem in stand-by see steps 21 and 22 (following NOTE 2)e) Switch to the other modem by Switch Transmitting ODUf) Upgrade other modem previously active, see steps 21 and 22 (following NOTE

2)g) Set again the needed protection parameters

19. Upload the modem Firmware W-1.1.2.10 of the East Modem (and of the West Modem if present) from the sub-directory SW7_5\Modem WB7-56 (612-31530)\ through FTP (see NOTE2)

DRAFT

DRAFT


79



21. Connect again the FTP client to FlexiHybrid via IP address22. Upload the modes N2-1B from the sub-directory SW7_5\MODES-N2-V1B\ through

FTP23. Click on Administration > Maintenance > Re-programming in order to refresh the

Reprogramming screen24. Check the Modes box and press TOGGLE button25. Repeat all the above steps (21-22) for the other bank. Bank 1 and Bank 2 must be

aligned26. Verify that in local and remote site the SVR 1.4 has been correctly uploaded27. Perform a Link Configuration


a) If using the Windows FTP client, open a DOS window and change directory to the directory containing the SVR files.1. Enter command "ftp <ip address of FlexiHybrid>".2. When prompted enter username "integrator" and password "p1nacate"3. Set to binary mode by entering "bin"4. Upload the appropriate files by entering "put <filename>"5. Exit











DRAFT



While step (2) is taking place the modem LED will turn off (wait ~5 minutes). You will know when the download to the modem completes when the modem LED starts to be lighted with a permanent yellow/orange color.


DRAFT

DRAFT


81




2. Open the WEB User Interface of the FlexiHybrid to be upgraded3. Click on Administration > Maintenance > Re-programming4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address5. Upload the Boot 1.2.0 from the sub-directory SW7_4\FlexiHybrid SVR 1_3\ through




8. [Only for protected system Hot Stand-by (1+1) In case of unprotected system skip to step 9]:a) It is recommended to disable the command "Power ODU after Switch" in Protec-

tion Configuration menub) Navigate to Protection Configuration and verify which ODU is onlinec) It is recommended to disable the command "APS Switch" in Protection Config-

uration menud) Upgrade the modem in stand-by see steps 21 and 22 (following NOTE 2)e) Switch to the other modem by Switch Transmitting ODUf) Upgrade other modem previously active, see steps 21 and 22 (following NOTE

2)g) Set again the needed protection parameters

9. Upload the modem Firmware W-1.1.2.1 of the East Modem (and of the West Modem if present) from the sub-directory SW7_4\Modem WB7-56 (612-31530)\ through FTP (see NOTE 2)

10. Upload the modem FPGA 1110 of the East Modem (and of the West Modem if present) from the sub-directory SW7_7\Modem WB7-56 (612-31530)\FPGA down-grade SVR 1.3_1.2\ through FTP (see NOTE 2)

11. Upload the Application 2.0.6x from the sub-directory SW7_4\FlexiHybrid SVR 1_3 through FTP

12. Upload the ODU library N2-2.0.6 from the sub-directory SW7_4\FlexiHybrid SVR 1_3 through FTP


14. Check the Application box and ODU library box and press TOGGLE button15. Check the Kernel box and the FPGA Master box and press TOGGLE button16. Reboot the IDU by navigating to the Administration > Reboot screen17. When the FlexyHybrid is reachable again via IP address, click on Administration >

Maintenance > Re-programming18. Connect again the FTP client to FlexiHybrid via IP address

DRAFT



19. Repeat all the above steps (6-12) for the other bank. Bank 1 and Bank 2 must be aligned (same software in both banks)


21. Connect again the FTP client to FlexiHybrid via IP address22. Repeat all the above steps (16-22) for the other bank. Bank 1 and Bank 2 must be

aligned23. Click on Administration > Maintenance > Re-programming in order to check if the

SVR has been successfully downgraded24. Upload the modes N2-1B from the sub-directory SW7_4\MODES-N2-V1B\ through


Reprogramming screen26. Check the Modes box and press TOGGLE button27. Repeat all the above steps (23-24) for the other bank. Bank 1 and Bank 2 must be

aligned28. Verify that in local and remote site the SVR 1.3 has been correctly uploaded29. Perform a Link Configuration


a) If using the Windows FTP client, open a DOS window and change directory to the directory containing the SVR files.1. Enter command "ftp <ip address of FlexiHybrid>".2. When prompted enter username "integrator" and password "p1nacate"3. Set to binary mode by entering "bin"4. Upload the appropriate files by entering "put <filename>"5. Exit









DRAFT

DRAFT


83




While step (2) is taking place the modem LED will turn off (wait ~5 minutes). You will know when the download to the modem completes when the modem LED starts to be lighted with a permanent yellow/orange color.


DRAFT





2. Open the WEB User Interface of the FlexiHybrid to be upgraded3. Click on Administration > Maintenance > Re-programming4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address5. Upload the Boot 1.2.0 from the sub-directory SW7_3\ SRA4 HC SVR 1_2\ through

FTP6. Upload the Kernel 0.2.3 from the sub-directory SW7_3\ SRA4 HC SVR 1_2\ through

FTP7. Upload the FPGA of the installed Master IO unit from the sub-directory SW7_3\


8. Upload the Application 2.0.P8_1x from the sub-directory SW7_3\ SRA4 HC SVR 1_2\ through FTP

9. Upload the ODU library N2-2.0.P8_1 from the sub-directory SW7_3\ SRA4 HC SVR 1_2\ through FTP


11. Check the Application box and ODU library ,the Kernel box and the FPGA Master box and press TOGGLE button



aligned (same software in both banks)16. Upload the modem FPGA 1110 of the East Modem (and of the West Modem if

present) from the sub-directory SW7_7\Modem WB7-56 (612-31530)\ FPGA down-grade SVR 1.3_1.2\ through FTP (see NOTE 2)

17. Upload the modem Firmware W-1.1.2.1 of the East Modem (and of the West Modem if present) from the sub-directory SW7_3\Modem WB7-56 (612-31530)\ through FTP (see NOTE 2)


19. Connect again the FTP client to FlexiHybrid via IP address20. Click on Administration > Maintenance > Re-programming in order to check if the

SVR has been successfully downgraded 21. Upload the modes N2-1B from the sub-directory SW7_3\MODES-N2-V1B\ through


Reprogramming screen23. Check the Modes box and press TOGGLE button

DRAFT

DRAFT


85


24. Repeat all the above steps (21-22) for the other bank. Bank 1 and Bank 2 must be aligned

25. Perform a Link Configuration
















DRAFT



6.9 ODU software upgrade procedure☞ The FileZilla FTP client may cause FTP upload errors as it sometimes uses nonstan-

dard commands for uploading files.

1. Rename the ODU software image filename to “east_odu_fw.s19”.2. Start with a powered-on IDU3. Use a graphical FTP client such as FileZilla and follow steps described in paragraph

7.3.3.1 Copy the ODU software from the PC to the IDU: east_odu_fw.s193.2 Wait 300 seconds for the ODU software update to complete

4. Log into the IDU web GUI5. Click on Administration > Maintenance > Re-programming6. Check the ODU EST Firmware box and press TOGGLE button.7. Reboot the ODU unit by navigating to the Administration > Reboot screen even if the

new Sw seems active in the reprogramming screen8. Repeat all the steps to replace the west ODU for a fully equipped system type.

6.10 FTP File Transfers☞ The FileZilla FTP client may cause FTP upload errors as it sometimes uses non-

standard commands for uploading files. We have tested NcFTP and have had good results. While NcFTP is command-line based, it can be scripted to ease upgrading. NcFTP is available at: http://www.ncftp.com.

1. Start with a powered-on.2. Use an FTP client and connect to the equipment via IP address.

2.1 If using the Windows FTP client, open a DOS window and change directory to the directory containing the 1.4.11a files.- Enter command "ftp <ipaddress of equipment>"- When prompted enter username "integrator" and password "p1nacate" - Set to binary mode by entering "bin"- Upload the appropriate files by entering “put <filename>”- Exit

2.2 If using a graphical FTP client such as FileZilla- Use the following parameters to connect: 1. Host: <ipaddress of equipment> 2. Username "integrator"; password "p1nacate"- Connect to equipment (See FTP client Help)- Set to binary mode (see FTP client Help)- Set timeout detection to 999 seconds (see FTP client Help)- Copy the appropriate files from the PC to the equipment - Exit the FTP client.

DRAFT

DRAFT


87

Operate and Maintain FTP upload procedures

7 FTP upload procedures

7.1 FTP Upload ProceduresUse an FTP client and connect to the equipment via IP address.

7.2 Windows FTP Client1. Enter the command "ftp <SDIDU™ IP address>".2. Enter the administrator username and password when prompted.3. Set the mode to binary by entering "bin".4. To upload the file, enter the command "put <filename>".5. Exit.

7.3 Graphical FTP Client (Filezilla or other FTP programs)1. Use the following parameters to connect:

a) Host: <SDIDU™ IP address>b) Username: Administrator usernamec) Password: Administrator password

2. Set FTP client to binary mode.3. Set timeout detection to 999 seconds.4. Make sure the “use multiple connections to transer files” option is not used.5. Drag and drop/copy the file from the PC to the equipment.6. Exit the FTP client.

DRAFT


Operate and MaintainAcronyms and abbreviations

8 Acronyms and abbreviationsAdTPC Adaptive Power Control

AIS Alarm Indication Signal

APC Adaptive Power Control

BER Bit Error Rate

CLI Command Line Interface

Codec Coder-Decoder

DB Decibel

DBm Decibel relative to 1 mW

DSCP Differentiated Service Code Point

E1 2048 Kb/s Signal

FEC Forward Error Correction

FPGA Field Programmable Gate Array

GPIO General Purpose Input/Output

HTML Hyper Text Mark-up Language

HTTP Hyper Text Transfer Protocol

IE Internet Explorer

IF Intermediate frequency

IP Internet Protocol

IPv4 Internet Protocol version 4

JVM Java Virtual Machine

LAN Local Area Network

LED Light-emitting diode

LOS Line of Sight

MIB Management Information Base

Modem Modulator-demodulator

MS Multiplex Section

MW Microwave

NE Network Element

NMS Network Management System

NTP Network Time Protocol

DRAFT

DRAFT


89

Operate and Maintain Acronyms and abbreviations

ODU Outdoor Unit

PDH Plesiochronous Digital Hierarchy

QAM Quadrature Amplitude Modulation

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RF Radio Frequency

RS Regenerator Section

RSL Received Signal Level (in dBm)

RST Regenerator Section Termination

RSOH Regenerator Section Overhead

RX Receiver

SFP Compact small form-factor pluggable (Plug In Add Module)

STP Spanning Tree Protocol

SNMP Simple Network Management Protocol

SNR Signal-to-Noise Ratio (Energy per bit to Noise ratio, Eb/No)

SONET Synchronous Optical Network

SSH Secure Shell

STM-1 Synchronous Transport Module 1

TCP/IP Transmission Control Protocol/Internet Protocol

ToS Type of Service

TX Transmitter

FlexyHibrit Operate and Maintain

Documents

Transcript of FlexyHibrit Operate and Maintain