Vous êtes sur la page 1sur 110

FlexiHybrid

Operate and Maintain

Issue: 1

Issue date: January 2011

A25000-A0300-J019-01-76P1

Operate and Maintain

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 DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT,
INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT
LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR
THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2011. All rights reserved.

Important Notice on Product Safety


This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the Legal, Safety
and Environmental Information part of this document or documentation set.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit


Von diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal,
Safety and Environmental Information dieses Dokuments oder dieses Dokumentationssatzes.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Table of Contents
This document has 110 pages.
1
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Waste electrical and electronic equipment (WEEE) . . . . . . . . . . . . . . . 11
Types of User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Features Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Security Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2
2.1
2.1.1
2.1.2
2.2
2.3
2.4
2.5
2.6
2.6.1
2.6.2
2.6.3
2.6.4

Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PC Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PC Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Telnet/SSH client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HyperTerminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access rights for users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Level 1 Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Level 2 Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Level 3 Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Level 4 Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15
15
15
15
16
16
17
17
17
17
18
18
18

3
3.1
3.2
3.2.1
3.2.1.1
3.2.2

User interface overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


WEB Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CLI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to use CLI screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menu Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configurable Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19
19
19
20
20
21

Navigation tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5
5.1
5.2
5.3
5.4
5.4.1
5.4.2
5.5
5.5.1
5.5.2
5.6
5.6.1
5.6.1.1

User Interface screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WEB Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CLI Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Number Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reprogramming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

26
26
26
27
28
28
28
29
29
29
30
30
30

Operate and Maintain

5.6.1.2
5.6.2
5.6.2.1
5.6.2.2
5.6.3
5.6.3.1
5.6.3.2
5.6.4
5.6.4.1
5.6.4.2
5.6.5
5.6.5.1
5.6.5.2
5.6.6
5.6.6.1
5.6.6.2
5.6.7
5.6.7.1
5.7
5.7.1
5.7.1.1
5.7.1.2
5.7.2
5.8
5.8.1
5.8.2
5.9
5.9.1
5.9.2
5.10
5.10.1
5.10.2
5.11
5.11.1
5.11.2
5.12
5.12.1
5.12.2
5.13
5.13.1
5.13.2
5.14
5.14.1
5.14.2
5.15
5.15.1
5.15.2

CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Add User Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Delete / Edit User Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
View Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
WEB Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
CLI Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Restore Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
How to store the NE configuration (from the NE to the PC) . . . . . . . . . . 36
How to restore the NE configuration (from the PC to the NE) . . . . . . . . 36
Restore Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
How to restore the Default parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Statistics Data Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Statistics NMS Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
ODU Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Modem Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
BERT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
CW Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
WEB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
CLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.16

Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

6
6.1
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
6.3

6.25
6.26

Upgrading procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Software components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
IDU software upgrade procedure from SVR 1.1 to SVR 3.1 . . . . . . . . . 65
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
FTP File Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Output Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
IDU software upgrade procedure from SVR 1.2, SVR 1.3, SVR 1.4 to SVR
3.1 without HW upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
IDU software upgrade procedure from SVR 1.2, SVR 1.3 or SVR 1.4 to
SVR 3.1 with HW upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
IDU software upgrade procedure from previous SVR 2.0 to SVR 3.1 . . 80
IDU software upgrade procedure from SVR 2.1 to SVR 3.1 (one file). . 82
IDU software upgrade procedure from SVR 2.1 to SVR 3.1 (separated files
without modem hardware change). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
IDU software upgrade procedure from SVR 2.1 to SVR 3.1 (separated files
with modem hardware change) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
IDU software upgrade procedure from SVR 2.2 to SVR 3.1 (one file). . 85
IDU software upgrade procedure from SVR 2.2 to SVR 3.1 (separated files
without modem hardware change). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
IDU software upgrade procedure from SVR 2.2 to SVR 3.1 (separated files
with modem hardware change) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
IDU software upgrade procedure from SVR 3.0 to SVR 3.1 (one file). . 88
IDU software upgrade procedure from SVR 3.0 to SVR 3.1 (separated files)
89
IDU software downgrade procedure from SVR 3.1 to SVR 2.0 . . . . . . . 91
IDU software downgrade procedure from SVR 3.1 to SVR 1.4 . . . . . . . 93
IDU software downgrade procedure from SVR 3.1 to SVR 1.3 . . . . . . . 95
IDU software downgrade procedure from SVR 3.1 to SVR 1.2 . . . . . . . 97
IDU software downgrade procedure from SVR 3.1 to SVR 2.1 without modem hardware change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
IDU software downgrade procedure from SVR 3.1 to SVR 2.1 with modem
hardware change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
IDU software downgrade procedure from SVR 3.1 to SVR 2.2 (one file) .
101
IDU software downgrade procedure from SVR 3.1 to SVR 2.2 (separated
file without modem hardware change) . . . . . . . . . . . . . . . . . . . . . . . . . 102
IDU software downgrade procedure from SVR 3.1 to SVR 2.2 (separated
file with modem hardware change) . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
IDU software downgrade procedure from SVR 3.1 to SVR 3.0 (one file) .
104
IDU software downgrade procedure from SVR 3.1 to SVR 3.0 (separated
file) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
ODU software upgrade procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
FTP File Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

FTP upload procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

6.4
6.5
6.6
6.7
6.8
6.9
6.10
6.11
6.12
6.13
6.14
6.15
6.16
6.17
6.18
6.19
6.20
6.21
6.22
6.23
6.24

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

7.1
7.2
7.3

FTP Upload Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108


Windows FTP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Graphical FTP Client (Filezilla or other FTP programs) . . . . . . . . . . . . 108

Acronyms and abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

List of Figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Figure 11
Figure 12
Figure 13
Figure 14
Figure 15
Figure 16
Figure 17
Figure 18
Figure 19
Figure 20
Figure 21
Figure 22
Figure 23
Figure 24
Figure 25
Figure 26
Figure 27
Figure 28
Figure 29
Figure 30
Figure 31
Figure 32
Figure 33
Figure 34
Figure 35
Figure 36
Figure 37
Figure 38
Figure 39
Figure 40
Figure 41
Figure 42
Figure 43

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

WEEE label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Web starting information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CLI starting information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CLI menu type screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configurable screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Number Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reprogramming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Add User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delete User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delete/Edit User Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restore Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restore Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSL Plot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SNR Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tx Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RF Link Performance Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equalizer Taps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Constellation Display (128 QAM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STM Mux/Demux Regenerator Section . . . . . . . . . . . . . . . . . . . . . . . . .
STM Mux/Demux Multiplex Section . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statistics Data Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Payload Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NMS Switch Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ODU Trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modem Trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BERT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CW Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local LIU loop in IDU1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local Modem loop in IDU1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote LIU loop in IDU1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Label fixed on the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11
16
19
20
20
21
26
27
28
29
30
31
32
33
34
35
36
37
41
42
43
44
44
45
45
46
46
47
47
48
49
50
51
53
55
57
59
60
60
61
61
62
63

Operate and Maintain

List of Tables
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6

Structure of this document . . . . . . . . . .


List of symbols and conventions . . . . .
History of changes . . . . . . . . . . . . . . . .
Default parameter values . . . . . . . . . . .
Software current version . . . . . . . . . . .
Components for the upgrade . . . . . . . .

......
......
......
......
......
......

.......
.......
.......
.......
.......
.......

......
......
......
......
......
......

.......9
. . . . . . 10
. . . . . . 11
. . . . . . 37
. . . . . . 63
. . . . . . 65

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Preface

1 Preface
This document provides the information to operate and maintain the FlexiHybrid in
SVR 3.1.

1.1

Intended audience
This document is intended to the Operators in charge to operate and maintain the FlexiHybrid.

1.2

Structure of this document


The document is divided into the following main chapters:
Chapter

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 interface

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

1.3

Title

Structure of this document

Symbols and conventions


The following symbols and mark-up conventions are used in this document:

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Preface

Operate and Maintain

Representation

f DANGER!
f WARNING!
f CAUTION!

Meaning
A safety message indicates a dangerous situation where
personal injury is possible.
The keywords denote hazard levels with the following meaning:
DANGER! - Indicates a hazardous situation which, if not
avoided, will result in death or serious (irreversible) personal
injury.
WARNING! - Indicates a hazardous situation which, if not
avoided, could result in death or serious (irreversible) personal
injury.
CAUTION! - Indicates a hazardous situation which, if not
avoided, may result in minor or moderate (reversible) personal
injury.

w NOTICE:

A property damage message indicates a hazard that may result


in equipment damage, data loss, traffic interruption, and so on.

A note provides important information related to the topic, for


example, not obvious exceptions to a rule or side effects.

A tip provides additional information related to the topic which is


not essential in the context, but given for convenience.

Bold

Italic

typewriter

<angle brackets>

All names of graphical user interface (GUI) objects, such as


windows, field names, buttons, and so on
Example: Select the Full Screen check box and press OK
Terms and abbreviations which are linked to an entry in the
glossary and list of abbreviations respectively.
Important key words
Files, folders and file system paths
Example: /usr/etc/sbin/ftpd.exe
Emphasized words
Input to be typed in a command line or a GUI field.
Examples:
ping -t 192.168.0.1
Enter World in the Domain field
Output from a command, error messages, content of a status
line, and so on
File content, such as program sources, scripts, logs, and settings.

Placeholders, for example as part of a file name or field value.


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

Table 2

10

List of symbols and conventions

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Preface

Representation
[square brackets]

Meaning
A key to be pressed on a PC keyboard, for example [F11].
Keys to be pressed simultaneously are concatenated with a +
sign, for example [CTRL]+[ALT]+[DEL].
Keys to be pressed one after another are concatenated with
spaces, for example [ESC] [SPACE] [M]

>

The greater than symbol > is used to concatenate a series of


GUI items in order to depict a GUI path. This is an abridged presentation of a procedure to be carried out in order to perform an
action or display a window or dialog box.
Examples:
A simple menu path: File > Save as ...
A more complex GUI path:
SURPASS TransNet window > Tools menu >
3R-Matrix Report command > 3R-Matrix Report dialog box

Table 2

List of symbols and conventions (Cont.)

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
Issue
1

Table 3

1.5

Issue date
September 2010

Remarks
1st version

History of changes

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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

WEEE label

11

Preface

Operate and Maintain

The correct disposal and separate collection of waste equipment will help prevent potential 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 Interfaces


The terminal can be accessed through Serial, Ethernet, or Modem interfaces using the
following types:

12

Web Interface (Normal / SSL)


Command Line Interface, CLI (Serial Console/Telnet/SSH)

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

1.7

Preface

Features Overview

Equipment Provisioning
Network Time Protocol (NTP) client
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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

13

Preface

Operate and Maintain

1.8

Security Measures
The 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:

14

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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Start-up

2 Start-up
2.1

PC Connection

2.1.1

Local connection
Local 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

2.1.2

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.

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 equipment again.
How to solve the problem with two particular Ethernet cards
1. 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.

Remote connection
Remote connection from a PC to an equipment can be accomplished via a serial communication 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.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

15

Start-up

Operate and Maintain

2.2

PC Network Configuration

Figure 2

Network connections

To set up a network connection:

2.3

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 settings.
Execute a ping to verify connectivity, by typing ping followed by the target equipment IP address at a command prompt.

Web browser
When 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 browsers default settings.


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

16

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

2.4

Start-up

Telnet/SSH client
When 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 connection.
Windows provides a Windows Standard telnet client that may be accessed through
command prompt. An alternate telnet client may be used.

2.5

HyperTerminal
When 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 users


The 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 Monitor


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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

17

Start-up

Operate and Maintain

2.6.2

User Level 2 Operator


Username: operator
Password: col1ma
User has all the access rights of User Level 1 and has additional rights to edit the following pages:

2.6.3

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

User Level 3 Administrator


Username: administrator
Password: d1scovery
User has all the rights of User Level 2 and has additional rights to the following pages:

2.6.4

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

User Level 4 Integrator


Username: integrator
Password: p1nacate
User has all the rights of User Level 3 and has additional rights to the following pages:

18

Ability to change Model number via the GUI interface


ODU and MODEM Trace Screens

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

User interface overview

3 User interface overview


3.1

WEB Overview
The 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 connection.
To access the web interface:
1.
2.
3.
4.
5.

Open a web browser (browser requirements are stated in section 2.3).


Type the IP address of the equipment in the address bar and press GO.
A popup window will prompt for a user name and password.
Enter a user name and password then press OK.
When authentication is successful, the Starting Information Screen (Figure 3) is displayed.

Figure 3

3.2

Web starting information screen

CLI Overview
The 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.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

19

User interface overview

Operate and Maintain

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

3.2.1
3.2.1.1

CLI starting information screen

How to use CLI screens


Menu Screens
Menu 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

20

CLI menu type screens

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

t
3.2.2

User interface overview

Further references to hotkey in this document will be synonymous with the character
placed in [ ] brackets for the corresponding parameter.

Configurable Screens
Configurable 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:

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

21

User interface overview

Operate and Maintain

1.
2.
3.
4.

Edit the parameter value.


Press the Enter-key.
If update was successful, the message Updated Successfully will be displayed.
If the update failed, a failure message will be displayed.

To perform a Group Update:


1.
2.
3.
4.
5.

22

Edit the parameter value.


Press the Enter-key.
Press the character specified for Update.
If the update was successful, the message Updated Successfully will be displayed.
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.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Navigation tree

4 Navigation tree
The 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
- SNMP
- Syslog Server
- E-mail
- Ethernet Payload
- Ethernet NMS
- VLAN Configuration
- Global VLAN Configuration
- Static VLAN Configuration
- Port Based Forwarding
- QoS Configuration
- Global Settings
- Port Priority
- VLAN p-bit Tag Priority
- DiffServ Priority
- Switch Priority
- Serial Configuration
- Security Configuration
- Device Configuration
- General
- Device Names
- Set Date and Time
- Serial Numbers
- Maintenance
- Reprogramming
- Add User
- Delete User

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

23

Navigation tree

Operate and Maintain

- View Event Log


- Reboot
- Restore Configuration
- Restore Defaults
- Link Configuration
- Authorization
- Configuration Summary
- Radio Link
- APC Configuration
- Link Configuration
- ODU Power
- ODU Channel
- ODU Configuration
- ACM Configuration
- Data Link
- E1/T1 Channel Map
- E1/T1 Ports
- Orderwire
- STM Mux Demux
- STM Trace Message
- Analysis
- Alarms
- Active
- Configuration
- History
- Threshold
- Graphs
- RSL
- Signal/Noise
- Tx Power
- RF Link Performance (not supported)
- Equalizer Taps
- Constellation
- Mux/Demux
- Temperature
- RPS

24

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Navigation tree

- Statistics
- Data Switch
- NMS Switch
- ODU Trace
- Modem Trace
- BERT Mode
- CW Mode
- Loopback
- Logout
- Help

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

25

User Interface screens

Operate and Maintain

5 User Interface screens


5.1

Introduction
Each 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 displays/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 Information
Home > 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:

26

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.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.3

User Interface screens

Status Panel
Home > 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.
Local IDU Information IP Address and Host Name.
Remote IDU Information IP Address and Host Name.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

27

User Interface screens

5.4

Operate and Maintain

Device Information
Navigation 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:

5.4.1

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.

WEB Location
1. Navigate to Administration ? Device Information ? General in the left panel.
2. The read-only terminal information is displayed here.

5.4.2

CLI Location
1. Navigate to Administration ? Device Information ? General Information.
2. The read-only terminal information is displayed here.

28

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.5

User Interface screens

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.

5.5.1

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

WEB Configuration
1. 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 Configuration
1.
2.
3.
4.
5.
6.

Navigate to Administration ? Device Configuration ? Serial Number Information.


All Serial Number related parameters are displayed with current/present values.
SNMP Configuration.
Select a parameter from the MIB section ccmSDIDUSysCfgDevInfoCards.
Use the SNMP GET command to get the value of the required parameter.
The SMNP agent will return the actual value after the operation has been successfully 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 parameter.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

29

User Interface screens

5.6
5.6.1

Operate and Maintain

Maintenance
Reprogramming
Navigation Tree > Administration > Maintenance > Reprogramming

Figure 11

Reprogramming

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.

5.6.1.1

WEB Configuration
1.
2.
3.
4.

5.6.1.2

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 :

Navigate to Administration ? Maintenance ? reprogramming screen.


Select an Image type.
To toggle between images, press the toggle button.
An error event will be indicate through an appropriate error message.

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

30

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

User Interface screens

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.

t
5.6.2

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

Add User Entry


Navigation 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.
2.
3.
4.

User ID Username.
Group ID / Level Specify access level
Password Password for the entered user id.
Confirm Confirm Password entered.

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

5.6.2.1

WEB Configuration
1. 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.6.2.2

CLI Configuration
1. Navigate to Administration ? Maintenance ? User Management ? Add User.
2. Edit each parameter.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

31

User Interface screens

Operate and Maintain

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.

5.6.3

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.

Delete / Edit User Entry


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

32

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.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.6.3.1

User Interface screens

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.
2.
3.
4.
5.
6.

Username Select the username to change his password.


Change Password Enter the new password for the selected user.
Confirm Password Confirm the new password.
Update Update the change in the password in the selected user profile.
Username Select the username to remove his entry.
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.6.3.2

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

t
5.6.4

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

View Event Log


Navigation Tree > Administration > Maintenance > View Event Log

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

33

User Interface screens

Operate and Maintain

Figure 15

5.6.4.1

Event Log

WEB Location
1. 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.6.4.2

CLI Location
1. 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.

34

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.6.5

User Interface screens

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

WEB Configuration
1. Select the device to reboot from the list.
2. Click reboot button.

5.6.5.2

CLI Configuration
1. Navigate to System Screen
2. 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.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

35

User Interface screens

5.6.6

Operate and Maintain

Restore Configuration
Navigation Tree > Administration > Maintenance > Restore Configuration

Figure 17

Restore Configuration

This screen, shown in Figure 17, enables the administrator to store and restore the configuration of the equipment.
The store/restore function is meant for "cloning" the stored equipment configuration.
However, please note:
1. The hardware and software configuration, from which the equipment configuration
is stored, must match the hardware and software configuration of the equipment to
which the configuration is being restored
a) The active software application version must be identical on both the equipment
from which the configuration is stored and the equipment to which the configuration is restored
b) The identical types of modules must be installed on both the equipment from
which the configuration is stored and the equipment to which the configuration
is restored
2. The IP address and Reprogramming screen information is not stored/restored.

5.6.6.1

How to store the NE configuration (from the NE to the PC)


1. Navigate to Administration > Maintenance and click on the Restore Configuration
link on the left panel.
2. Click on the Download The Configuration button. The file name cannot be
changed. Use the default name, otherwise the NE will not recognized it, when you
will try to restore it to the NE.

5.6.6.2

How to restore the NE configuration (from the PC to the NE)


1. Navigate to Administration > Maintenance and click on the Restore Configuration
link on the left panel.
2. Click on the Upload The Configuration button.
3. Click on Browse, select the directory to be used to store the file, select the file and
click on Open.

36

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.6.7

User Interface screens

Restore Defaults
Navigation Tree > Administration > Maintenance > Restore Defaults

Figure 18

Restore Defaults

This screen, shown in Figure 18, enables the administrator to restore the default parameters in the NE.
The default values of the system configuration parameters are listed in Table 4.
Parameter

Default Value

IP Address and DHCP default values


IP Address

0xc0a80001 (192.168.0.1)

IP Netmask

0xffffff00 (255.255.255.0)

IP Gateway

0xc0a80002 (192.168.0.2)

DHCP Client

FALSE (Disabled)

Serial Port Parameters


Device Selection

CM_SERIAL2SERIAL

Data Baud rate

BAUD_38400

Serial Byte Format

SBF_8N1

SNMP Configuration
Read Community

public

Write Community

private

Trap Community

public

Trap Manager #1

0.0.0.0

Trap Manager #2

0.0.0.0

Trap Manager #3

0.0.0.0

Trap Manager #4

0.0.0.0

Auth Trap Enable FALSE

(Disabled)

Table 4

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Default parameter values

37

User Interface screens

Operate and Maintain

Parameter

Default Value

Trap Version

SNMP_USE_V1_TRAPS

SNMP Mode

SNMP_V1V2V3 or SNMP_V1V2 (non-encrypted


version)

SNMP Auth Password

""

SNMP Priv Password

""

Syslog Server configuration


Syslog Server

0.0.0.0

Syslog Facility

LOCAL_1

Email configuration
SMTP Enable

FALSE (Disabled)

SMTP Server IP

0.0.0.0

SMTP Port

25

Username

""

Password

""

E-Mail #1

""

E-Mail #2

""

E-Mail #3

""

STP NMS Configuration


STP Status

STP_ENABLED

Bridge Priority

BRIDGE_NORMAL

Hello Time

Max Age

20

Forward Delay

15

STP UPL Configuration


STP Status

STP_DISABLED

Bridge Priority

BRIDGE_NORMAL

Hello Time

Max Age

20

Forward Delay

15

Security Configuration
HTTP Access

PLAIN_HTTP

Command Line Interface

CLI_TELNET

Date and Time settings


SNTP Server Address
Table 4

38

0.0.0.0

Default parameter values (Cont.)

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

User Interface screens

Parameter

Default Value

SNTP Server Enable

FALSE (Disabled)

Timezone (eg. GMT -8.0 CA)

Date Format

DF_EUR

STM Mux/Demux parameters


Sonet Medium Type

sdh

Sonet SES Threshold

itu1995

Circuit Identifier

00:00:00:00

SONET Lower Order Path Section


Remote Error Indication

DO_NOT_SEND

Remote Defect Indication

DO_NOT_SEND

Path label expected

transmit message align

ALIGN

transmit message length

16 Bytes

Lower Order path width

2VC12

SONET Higher Order Path Section


Remote Error Indication

DO_NOT_SEND

Remote Defect Indication

DO_NOT_SEND

Path label expected

transmit message align

ALIGN

transmit message length

16 Bytes

High Order path width

STS3CSTM1

SONET Multiplex Line Section


Remote Error Indication

DO_NOT_SEND

Remote Defect Indication

DO_NOT_SEND

SONET Regenerator Section


transmit message align

ALIGN

transmit message length

16 Bytes

Descrambler

TRUE (Enabled)

SDH Rate

STM1

All System User Configurations are defaulted


All alarms are unmasked and all alarm emails are cleared
All Alarm outputs are cleared
All SONET Trace messages will be dafaulted to "DefaultTraceData" and CRC7
check will be
Table 4

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Default parameter values (Cont.)

39

User Interface screens

5.6.7.1

Operate and Maintain

How to restore the Default parameters


1. Navigate to Administration > Maintenance and click on the Restore Defaults link
on the left panel.
2. Click on the Restore button.

40

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.7
5.7.1

User Interface screens

Alarms
Active Alarms
Navigation Tree > Analysis > Alarms > Active Alarm

Figure 19

Active Alarms

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

t
5.7.1.1

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.

WEB Configuration
1. Navigate to Analysis ? Alarms ? Active in the left panel.
2. The Active Alarms information screen is displayed.

5.7.1.2

CLI Configuration
1. Navigate to Analysis ? Alarms ? Active Alarms.
2. The Active Alarms information screen is displayed.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

41

User Interface screens

5.7.2

Operate and Maintain

Alarm History
Navigation Tree > Analysis > Alarms > Alarm History

Figure 20

Alarm History

This screen lists alarms that have occurred and their description, status, and time (see
Figure 20). 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.

42

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.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.8

User Interface screens

Graphs
This menu graphically displays the following parameters:

East RSL
West RSL
East Signal/Noise
West Signal/Noise
East TX power
West TX power
RF Link Performance (not supported)
East Equalizer Taps
West Equalizer Taps
East Constellation
West Constellation
Mux/Demux Regenerator Section/Section Layer
Mux/Demux Multiplex Section/Line Layer
Temperature
Radio Protection Switch

Navigation Tree > Analysis > Graphs > RSL

Figure 21

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

RSL Plot

43

User Interface screens

Operate and Maintain

Navigation Tree > Analysis > Graphs > Signal/Noise

Figure 22

SNR Plot

Navigation Tree > Analysis > Graphs > Tx Power

Figure 23

44

Tx Power

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

User Interface screens

Navigation Tree > Analysis > Graphs > RF Link Perofrmance (not supported)

Figure 24

RF Link Performance Plot

Navigation Tree > Analysis > Graphs > Equalizer Taps

Figure 25

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Equalizer Taps

45

User Interface screens

Operate and Maintain

Navigation Tree > Analysis > Graphs > Constellation

Figure 26

Constellation Display (128 QAM)

Navigation Tree > Analysis > Graphs > Mux/Demux

Figure 27

t
46

STM Mux/Demux Regenerator Section

SEF = not supported; CV = Code Violation according to RFC 3592

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

User Interface screens

Figure 28

STM Mux/Demux Multiplex Section

SEF = not supported; CV = Code Violation according to RFC 3592

Figure 29

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Temperature

47

User Interface screens

Operate and Maintain

Figure 30

5.8.1

RPS

WEB Configuration
1. 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.8.2

CLI Configuration
Not available.

48

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.9

User Interface screens

Statistics Data Switch


Navigation Tree > Analysis > Statistics > Data Switch

Figure 31

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

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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

49

User Interface screens

Operate and Maintain

When the flow control is working, the flow control in the row of the DataSwitchStatistics
screen is always shown as "Symmetric", also if in the Ethernet Payload Configuration
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 DataSwitchStatistics screen is always shown as "Disabled", also if in the Ethernet Payload Configuration menu the flow control has been set as "Disabled" or "Transmit only".

Figure 32

5.9.1

Ethernet Payload Configuration

WEB Configuration
1. 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.9.2

CLI Configuration
1. Navigate to Analysis ? Data Switch Statistics.
2. The Data Switch Statistics screen is displayed.
3. Select the hotkey Clear to clear the data and start accumulating again.

50

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.10

User Interface screens

Statistics NMS Switch


Navigation Tree > Analysis > Statistics > NMS Switch

Figure 33

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

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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

51

User Interface screens

5.10.1

Operate and Maintain

WEB Configuration
1. 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.10.2

CLI Configuration
Navigate to Analysis ? SNMP Switch Statistics.

52

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.11

User Interface screens

ODU Trace
Navigation Tree > Analysis > ODU Trace

Figure 34

ODU Trace

Customer Service may ask the user to use the ODU Trace screen for debugging purposes.
The screen shown in Figure 34 is used to communicate with ODU directly by sending
commands and receiving the responses. The following items are displayed:

t
5.11.1

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.

WEB Configuration
1.
2.
3.
4.

Navigate to Analysis and click on the ODU trace on the left panel.
Enter the command in the text field.
Click send command button.
After few seconds (depending on your network speed) the response from ODU for
the given command will be displayed in the text area.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

53

User Interface screens

Operate and Maintain

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:

5.11.2

1.
2.
3.
4.

Click inside the text area.


Press Ctrl+A and Ctrl+C.
Open notepad (or any text editor) and press Ctrl+V.
Save the file.

CLI Configuration
Not available.

54

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.12

User Interface screens

Modem Trace
Navigation Tree > Analysis > Modem Trace

Figure 35

Modem Trace

Customer Service may ask the user to use the Modem Trace for debugging purposes.
The screen shown in Figure 35 is used to communicate with MODEM directly by sending
commands and receiving the responses. The following items are displayed:

5.12.1

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.

WEB Configuration
1.
2.
3.
4.

Navigate to Analysis and click on the MODEM trace link on the left panel.
Enter the command in the text field.
Click the send command button.
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.

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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

55

User Interface screens

5.12.2

Operate and Maintain

To copy & save the response messages:


1.
2.
3.
4.

Click inside the text area.


Press Ctrl+A and Ctrl+C.
Open notepad (or any text editor) and press Ctrl+V.
Save the file.

CLI Configuration
Not available.

56

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.13

User Interface screens

BERT Mode
Navigation Tree > Analysis > BERT Trace

Figure 36

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

WEB Configuration
To begin testing:
1. Navigate to Analysis and click on the BERT mode on the left panel.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

57

User Interface screens

Operate and Maintain

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, cumulative 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

To copy & save the response messages:

5.13.2

1.
2.
3.
4.

Click inside the text area.


Press Ctrl+A and Ctrl+C.
Open notepad (or any text editor) and press Ctrl+V.
Save the file.

CLI Configuration
Not available.

58

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

5.14

User Interface screens

CW Mode
Navigation Tree > Analysis > CW Trace

Figure 37

CW Mode

This screen allows the user to enable or disable CW mode (see Figure 37).
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.14.1

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

5.14.2

CLI Configuration
Not available.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

59

User Interface screens

5.15

Operate and Maintain

Loopback
Navigation Tree > Analysis > Loopback

Figure 38

Loopback

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

t
5.15.1

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

WEB Configuration
1. Navigate to Analysis ? Loopback.
2. Select the type of loopback (Local LIU (Refer to Figure 39), Local Modem (Refer
to Figure 40) or Remote LIU (Refer to Figure 41)).
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 39

60

Local LIU loop in IDU1

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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

t
5.15.2

User Interface screens

Figure 40

Local Modem loop in IDU1

Figure 41

Remote LIU loop in IDU1

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

CLI Configuration
1. 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 value
7. If loopback is running, press the hotkey for stop to stop it.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

61

User Interface screens

5.16

Operate and Maintain

Logout
Navigation Tree > Logout

Figure 42

Logout

The page shown in Figure 42 enables the user to logout from the Web Interface.
In the case of Internet Explorer, the logout link will close the browser. For other browsers, the user may have to close and reopen the browser.

62

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

6 Upgrading procedure

A label is sticked on the IDU. This label (shown in Figure 43) contains the P/N, Serial
Number and also (on the right corner on the button) the Software version of the equipment loaded in factory:

7/8 = SVR 2.2


7/9 = SVR 3.0
7/10 = SVR 3.1

Figure 43

Label fixed on the IDU

To upgrade to SVR 3.1 or to downgrade from SVR 3.1 to a previous SVR refer to the
next paragraphs.

6.1

Software components
Table 5 shows the current version for each software upgradeable component. Only the
components, whose version is older than that shown in Table 5, needs to have the
related file uploaded. At the end of the upgrade procedure the active version should be
like those shown in Table 5. 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 3_1 Kernel

0.3.4

kernel.img

No

FlexiHybrid SVR 3_1 Application

2.10.9x

puma_app.img

Yes

FlexiHybrid SVR 3_1 ODU Library

N2-2.10.9

odu.img

Yes

Standard2 Master IO FPGA Standard2


(612-31537)
Master IO (612-315/37)

4101_ST03.03.04

ffpga_4101_ST03.03.04.img

Yes

GigE Master IO
(612-31510)

FPGA GigE Master IO


(612-315/10)

4110_GE03.01.02 ffpga_4110_GE03.01.02.img No

Enhanced2 Master
IO (612-31539)

FPGA Enhanced2
Master IO (612-315/39)

4121_ST03.03.02

GigE Enhanced
Master IO
(612-31516)

FPGA GigE Enhanced


Master IO
(612-315/16)

4130_SG03.01.04 ffpga_4130_SG03.01.04.img Yes

Table 5

ffpga_4121_ST03.03.02.img

Yes

Software current version

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

63

Upgrading procedure

Directory

Operate and Maintain

Component

Reprogramming
Screen Version

16E1 expansion IO
(612-31505)

FPGA 16E1 expansion


IO (612-315/05)

4132_EX03.01.02

opt_io_framer_fw.bz2

42E1 Master IO
(612-31503)

FPGA 42E1 Master IO


(612-315/03)

4142_SP03.03.02

ffpga_4142_SP03.03.02.img Yes

21E1 expansion IO
(612-31506)

FPGA 21E1 expansion


IO (612-315/06)

4163_EX03.01.02

opt_io_framer_fw.bz2

No

Controller
(634-00181)

FPGA Controller
(634-001/81)

v27

cfpga.img

No

Controller2
(634-00191)

FPGA Controller2
(634-001/91)

4501_v7

cfpga.img

No

Modem WB7-56
(612-31530)

Modem East F/W


WB7-56 (612-315/30)

W-1.1.19

east_modem_fw.bz2

No

Modem West F/W


WB7-56 (612-315/30)

W-1.1.19

west_modem_fw.bz2

No

Modem East FPGA


WB7-56 (612-315/30)

18

east_modem_fpga.bz2

No

Modem West FPGA


WB7-56 (612-315/30)

18

west_modem_fpga.bz2

No

Modem East F/W


(612-315/42)

U-3.0.8

east_modem_fw.bz2

Yes

Modem West F/W


(612-315/42)

U-3.0.8

west_modem_fw.bz2

Yes

Modem East FPGA

4700UM_3.1.0

east_modem_fpga.bz2

Yes

4700UM_3.1.0

west_modem_fpga.bz2

Yes

Modem F/W
(612-31542)

Filename

Upgraded
relative to
previous
SVR
No

(612-315/42)
Modem West FPGA
(612-315/42)
FlexiHybrid SVR 3.1

Bootloader

1.3.2

u-boot.bin

No

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

No

Table 5

64

Software current version (Cont.)

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

6.2

Upgrading procedure

IDU software upgrade procedure from SVR 1.1 to SVR 3.1

6.2.1

Step 1: Replace Modem WB14-56 (612-315/02) with the Modem WB7-56 (612315/30).
Step 2: Upgrade 16M to 32M Flash Map.
Step 3: Refer to paragraph 6.2.5.

Requirements
The 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.

t
6.2.2

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.

Software Components
Table 6 shows the components required for the upgrade.
Component

Reprogramming
Screen Version

Filename

32M Compatible Kernel

0.2.0

kernel.img

Intermediate Bootloader

INT.1

u-boot.bin

32M Compatible Bootloader

1.2.0

u-boot.bin

Table 6

6.2.3

Notes

This file performs the


actual 16M to 32M
FLASH map upgrade

Components for the upgrade

Upgrade Procedure
The 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.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

65

Upgrading procedure

Operate and Maintain

6. The following screen is an example of how the reprogramming screen should


appear. ODU FIRMWARE, BOOTLOADED and MODEM FIRMWARE arent
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.

66

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

14. Output messages during transition process can be viewed through serial console.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 nonstandard 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 FileZilla
1. 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 IDU
6. Exit the FTP client.

6.2.5

Output Messages
Connect 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.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

67

Upgrading procedure

Operate and Maintain

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

68

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Upgrading procedure

69

Upgrading procedure

70

Operate and Maintain

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

Step3: Upload SVR 3.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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the Boot (u-boot.bin) from the sub-directory SWSVR3_1\FlexiHybrid SVR
3_1\ through FTP
6. Upload the (kernel.img) from the sub-directory SWSVR3_1\FlexiHybrid SVR 3_1\
through FTP
7. Upload the FPGA of the Controller unit v27 from the sub-directory SWSVR3_1\Controller (634-00181) or the FPGA of the Controller2 unit 4501_v7 from the sub-directory SWSVR3_1\Controller2 (634-00191)\ through FTP
8. Upload the FPGA of the installed Master IO unit from the subdirectory from the subdirectory SWSVR3_1\ through FTP
9. Upload the Application (puma_app.img) from the sub-directory SWSVR3_1\FlexiHybrid SVR 3_1\ through FTP
10. Upload the ODU library (odu.img) from the sub-directory SWSVR3_1\FlexiHybrid
SVR 3_1\ through FTP
11. Upload the FPGA of the installed Expansion unit (opt_io_framer_fw.bz2) from the
sub-directory SWSVR3_1\16E1 expansion IO (612-31505)\ for 16 channel expansion unit, version 3 from the sub-directory SWSVR3_1\21E1 expansion IO (61231506)\ 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 screen
15. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
16. Connect again the FTP client to FlexiHybrid via IP address
17. Repeat all the above steps (6-10) for the other bank. Bank 1 and Bank 2 must be
aligned (same software in both banks)
18. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

71

Upgrading procedure

Operate and Maintain

19. Connect again the FTP client to FlexiHybrid via IP address


20. Upload the modem Firmware (east_modem_fw.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\Modem WB7-56 (61231530)\ through FTP (see NOTES 2, 3), or from SWSVR3_1\ Modem2(612-31542)
if Unified Modem 2 is used
21. Wait for a while (3-5mins) until the right version of Firmware is refreshed on Reprogramming screen
22. Upload the modem FPGA (east_modem_fpga.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\Modem WB7-56 (61231530)\ through FTP (see NOTES 2, 3), or from SWSVR3_1\ Modem2(612-31542)
if Unified Modem 2 is used
23. Wait for a while (3-5mins) until the right version is refreshed on Reprogramming
screen
24. Upload the modes N2-7A from the sub-directory SWSVR3_1\MODES-N2-V7A\
through FTP
25. Upload the channel CN-1 from the sub-directory SWSVR3_1\Channel_CN-1\
through FTP
26. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
27. Check the Modes box and Channel box and press TOGGLE button
28. Repeat all the above steps (24-25) for the other bank. Bank 1 and Bank 2 must be
aligned
29. Perform a Link Configuration
30. Click on Administration > Maintenance > Re-programming in order to check if the
SVR has been successfully upgraded
31. Upload the E1 channel map from the sub-directory SWSVR3_1\ through FTP
32. Upload the NSN company logo and the product name pictures from the sub-directory SWSVR3_1\NSN_Graphics\ through FTP
33. Refresh the browser in order to see the correct NSN company logo and product
name

72

Note 1: Extra help for FTP client:

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

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

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


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

Note 3: Extra help for downloading modem firmware and FGPA:


When downloading modem FPGA and firmware,sometimes the transfer of file completes in a very short time(in 0.00s), this means the transfer fails,file needs to be
uploaded again.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

73

Upgrading procedure

6.3

Operate and Maintain

IDU software upgrade procedure from SVR 1.2, SVR 1.3,


SVR 1.4 to SVR 3.1 without HW upgrade
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the Boot (u-boot.bin) from the sub-directory SWSVR3_1\FlexiHybrid SVR
3_1\ through FTP
6. Upload the (kernel.img) from the sub-directory SWSVR3_1\FlexiHybrid SVR 3_1\
through FTP
7. Upload the FPGA of the Controller unit from the sub-directory SWSVR3_1\Controller (634-00181) or the FPGA of the Controller2 unit from the sub-directory
SWSVR3_1\Controller2 (634-00191)\ through FTP
8. Upload the FPGA of the installed Master IO unit from the subdirectory from the subdirectory SWSVR3_1\ through FTP
9. Upload the FPGA of the installed Expansion unit (opt_io_framer_fw.bz2) from the
sub-directory SWSVR3_1\16E1 expansion IO (612-31505)\ for 16 channel expansion unit, version 3 from the sub-directory SWSVR3_1\21E1 expansion IO (61231506)\ for 21 channel expansion unit), if any, through FTP
10. Upload the Application (puma_app.img) from the sub-directory SWSVR3_1\FlexiHybrid SVR 3_1\ through FTP
11. Upload the ODU library (odu.img) from the sub-directory SWSVR3_1\FlexiHybrid
SVR 3_1\ 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 screen
15. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
16. Connect again the FTP client to FlexiHybrid via IP address
17. Repeat all the above steps (6, 7, 8, 10, 11, 12) for the other bank. Bank 1 and Bank
2 must be aligned (same software in both banks)
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 address
20. Upload the modem Firmware (east_modem_fw.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\Modem WB7-56 (61231530)\ through FTP (see NOTES 2, 3)
21. Wait for a while (3-5mins) until the right version of Firmware (east_modem_fw.bz2)
is refreshed on Reprogramming screen
22. Upload the modem FPGA (east_modem_fpga.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\Modem WB7-56 (61231530)\ through FTP (see NOTES 2, 3)
23. Wait for a while(3-5mins) until the right version of FPGA is refreshed on Reprogramming screen
24. Upload the modes N2-7A from the sub-directory SWSVR3_1\MODES-N2-V7A\
through FTP

74

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

25. Upload the channel CN-1 from the sub-directory SW7_6\Channel_CN-1\ through
FTP
26. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
27. Check the Modes box and Channel box and press TOGGLE button
28. Repeat all the above steps (24-26) for the other bank. Bank 1 and Bank 2 must be
aligned
29. Perform a Link Configuration
30. Click on Administration > Maintenance > Re-programming in order to check if the
SVR has been successfully upgraded.
31. Upload the E1 channel map from the sub-directory SWSVR3_1\ through FTP
32. Upload the NSN company logo and the product name pictures from the sub-directory SWSVR3_1\NSN_Graphics\ through FTP
33. Refresh the browser in order to see the correct NSN company logo and product
name

Note 1: Extra help for FTP client:

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

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
Host: <ip address 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

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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

75

Upgrading procedure

Operate and Maintain

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 downloaded. You
do not have to toggle modem firmware or FPGA since the modems have only 1 memory
bank.

76

Note 3: Extra help for downloading modem firmware and FGPA:


When downloading modem FPGA and firmware,sometimes the transfer of file completes in a very short time(in 0.00s), this means the transfer fails,file needs to be
uploaded again.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

6.4

Upgrading procedure

IDU software upgrade procedure from SVR 1.2, SVR 1.3 or


SVR 1.4 to SVR 3.1 with HW upgrade
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.

13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.

24.
25.

26.

Switch the old controller 634-00181 with the new one 634-00191
Switch the old master IO board with the new one
Switch WB modem 612-31530 with Unified Modem 612-31542
Start with a powered-on FlexiHybrid connected to a personal computer via IP
address
Open the WEB User Interface of the FlexiHybrid to be upgraded
Click on Administration > Maintenance > Re-programming
Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
Upload the Boot (u-boot.bin) from the sub-directory SWSVR3_1\FLEXIHYBRID
SVR3_1 \ through FTP.
Upload the (kernel.img) from the sub-directory SWSVR3_1\FLEXIHYBRID SVR3_1
\ through FTP
Upload the FPGA the FPGA of the Controller2 unit 4501_v7 from the sub-directory
SWSVR3_1\CONTROLLER2 (634-00191)\ through FTP
Upload the FPGA of the installed Master IO unit from the subdirectory from the subdirectory SWSVR3_1\ through FTP
Upload the FPGA of the installed Expansion unit (opt_io_framer_fw.bz2) from the
sub-directory SWSVR3_1\16E1 EXPANSION IO (612-31505) \ for 16 channel
expansion unit, version 3 from the sub-directory SWSVR3_1\21E1 EXPANSION IO
(612-31506) \ for 21 channel expansion unit), if any, through FTP
Upload the Application (puma_app.img) from the sub-directory SWSVR3_1\FLEXIHYBRID SVR3_1 \ through FTP
Upload the ODU library (odu.img) from the sub-directory SWSVR3_1\FLEXIHYBRID SVR3_1 \ through FTP
Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
Check the Kernel box, Application box, controller FPGA box, Master IO FPGA
box,ODU library box and press TOGGLE button
Reboot the IDU by navigating to the Administration > Reboot screen
When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
Connect again the FTP client to FlexiHybrid via IP address
Repeat steps ( 9 - 14) for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)
When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
Connect again the FTP client to FlexiHybrid via IP address
Upload the modem Firmware (east_modem_fw.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\Modem2 (612-31542) \
through FTP (see NOTES 2, 3)
Wait for a while(3-5mins) until the right version of Firmware (east_modem_fw.bz2)
is refreshed on Reprogramming screen
Upload the modem FPGA (east_modem_fw.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\Modem2 (612-31542) \
through FTP (see NOTES 2, 3)
Wait for a while (3-5mins) until the right version of FPGA is refreshed on Reprogramming screen

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

77

Upgrading procedure

Operate and Maintain

27. Upload the modes N2-7A from the sub-directory SWSVR3_1\MODES-N2-V7A\


through FTP
28. Upload the channel CN-1 from the sub-directory SWSVR3_1\Channel_CN-1\
through FTP
29. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
30. Check the MODEM FPGA box, MODEM FIRMWARE box,Modes box and Channel
box and press TOGGLE button
31. Reboot IDU by navigating to the administration ->Reboot screen
32. Perform a Link Configuration
33. Repeat steps 23-29 for the other bank. Bank 1 and Bank 2 must be aligned
34. Click on Administration > Maintenance > Re-programming in order to check if the
SVR has been successfully upgraded
35. Upload the E1 channel map from the sub-directory SWSVR3_1\ through FTP
36. Upload the NSN company logo and the product name pictures from the sub-directory SWSVR3_1\NSN_Graphics\ through FTP
37. Refresh the browser in order to see the correct NSN company logo and product
name

Note 1: Extra help for FTP client:

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

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

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

78

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

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

Note 3: Extra help for downloading modem firmware and FGPA:


When downloading modem FPGA and firmware,sometimes the transfer of file completes in a very short time(in 0.00s), this means the transfer fails,file needs to be
uploaded again.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

79

Upgrading procedure

6.5

Operate and Maintain

IDU software upgrade procedure from previous SVR 2.0 to


SVR 3.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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the Boot (u-boot.bin) from the sub-directory SWSVR3_1\FLEXIHYBRID
SVR3_1\ through FTP
6. Upload the (kernel.img) from the sub-directory SWSVR3_1\FLEXIHYBRID
SVR3_1\ through FTP
7. Upload the FPGA of the Controller unit v27 from the sub-directory SWSVR3_1\
CONTROLLER (634-00181)\ or the FPGA of the Controller2 unit 4501_v7 from the
sub-directory SWSVR3_1\CONTROLLER2 (634-00191)\ through FTP
8. Upload the FPGA of the installed Master IO unit from the subdirectory from the subdirectory SWSVR3_1\ through FTP
9. Upload the FPGA of the installed Expansion unit (opt_io_framer_fw.bz2) from the
sub-directory SWSVR3_1\16E1 EXPANSION IO (612-31505)\ for 16 channel
expansion unit, version 3 from the sub-directory SWSVR3_1\21E1 EXPANSION IO
(612-31506)\ for 21 channel expansion unit), if any, through FTP
10. Upload the Application (puma_app.img) from the sub-directory SWSVR3_1\FLEXIHYBRID SVR3_1\ through FTP
11. Upload the ODU library (odu.img) from the sub-directory SWSVR3_1\FLEXIHYBRID SVR3_1\ through FTP
12. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
13. Check the Kernel box, the FPGA Controller box and the FPGA Master,Application,
ODU library box and press TOGGLE button
14. Reboot the IDU by navigating to the Administration > Reboot screen
15. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
16. Connect again the FTP client to FlexiHybrid via IP address
17. Repeat steps (6,7,8,10,11,12) for the other bank. Bank 1 and Bank 2 must be
aligned (same software in both banks)
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 address
20. Upload the modem Firmware (east_modem_fw.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\MODEM WB7-56 (61231530)\ through FTP (see NOTES 2, 3)
21. Wait for a while (3-5mins) until the right version of Firmware is refreshed on Reprogramming screen
22. Upload the modem FPGA of the East Modem (and of the West Modem if present)
from the sub-directory SWSVR3_1\MODEM WB7-56 (612-31530)\ through FTP
(see NOTES 2, 3)
23. Wait for a while (3-5mins) until the right version of FPGA is refreshed on Reprogramming screen
24. Upload the modes N2-7A from the sub-directory SWSVR3_1\MODES-N2-V7A\
through FTP

80

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

25. Upload the channel CN-1 from the sub-directory SWSVR3_1\Channel_CN-1\


through FTP
26. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
27. Check the Modes box and Channel box and press TOGGLE button
28. Repeat steps 24-25 for the other bank. Bank 1 and Bank 2 must be aligned
29. Perform a Link Configuration
30. Click on Administration > Maintenance > Re-programming in order to check if the
SVR has been successfully upgraded
31. Upload the E1 channel map from the sub-directory SWSVR3_1\through FTP
32. Upload the NSN company logo and the product name pictures from the sub-directory SWSVR3_1\NSN_Graphics\ through FTP
33. Refresh the browser in order to see the correct NSN company logo and product
name

Note 1: Extra help for FTP client:

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

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

81

Upgrading procedure

Operate and Maintain

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

Note 3: Extra help for downloading modem firmware and FGPA:

6.6

IDU software upgrade procedure from SVR 2.1 to SVR 3.1


(one file)

When downloading modem FPGA and firmware,sometimes the transfer of file completes in a very short time(in 0.00s), this means the transfer fails,file needs to be
uploaded again.

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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the puma_package.img software package from the sub-directory
SWSVR3_1\sb-package\ through FTP (after upload, IDU will reboot automatically)
6. Wait for a while till FlexiHybrid.is reachable again via IP address.Click on Administration > Maintenance > Re-programming in order to refresh the Reprogramming
screen to check if the SVR has been successfully upgraded
7. Repeat step 5 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)

82

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

6.7

Upgrading procedure

IDU software upgrade procedure from SVR 2.1 to SVR 3.1


(separated files without modem hardware change)
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the FPGA of the installed Master IO unit from the subdirectory from the subdirectory SWSVR3_1\ through FTP
6. Upload the Application (puma_app.img) from the sub-directory SWSVR3_1\FlexiHybrid SVR 3_1\ through FTP
7. Upload the ODU library (odu.img) from the sub-directory SWSVR3_1\FlexiHybrid
SVR 3_1\ through FTP
8. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
9. Check the Application box ,ODU library box ,MASTER IO box and press TOGGLE
button
10. Reboot the IDU by navigating to the Administration > Reboot screen
11. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
12. Connect again the FTP client to FlexiHybrid via IP address
13. Repeat steps 5-7 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)

Note 1: Extra help for FTP client:

6.8

IDU software upgrade procedure from SVR 2.1 to SVR 3.1


(separated files with modem hardware change)

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

1. Switch WB modem 612-31530 with Unified Modem 612-31542


2. Start with a powered-on FlexiHybrid connected to a personal computer via IP
address
3. Open the WEB User Interface of the FlexiHybrid to be upgraded
4. Click on Administration > Maintenance > Re-programming
5. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

83

Upgrading procedure

Operate and Maintain

6.
7.
8.
9.
10.
11.
12.
13.
14.
15.

16.
17.

18.
19.
20.
21.
22.
23.

84

Upload the FPGA of the installed Master IO unit from the subdirectory from the subdirectory SWSVR3_1\ through FTP
Upload the Application (puma_app.img) from the sub-directory SWSVR3_1\FlexiHybrid SVR 3_1\ through FTP
Upload the ODU library (odu.img) from the sub-directory SWSVR3_1\FlexiHybrid
SVR 3_1\ through FTP
Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
Check the Application box, ODU library box, MASTER IO FPGA box and press
TOGGLE button
Reboot the IDU by navigating to the Administration > Reboot screen
When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
Connect again the FTP client to FlexiHybrid via IP address
Repeat steps 6-8 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)
Upload the modem Firmware (east_modem_fw.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\Modem2 (612-31542)\
through FTP (see NOTE 2,3)
Wait for a while (3-5mins) until the right version of Firmware is refreshed on Reprogramming screen
Upload the modem FPGA (east_modem_fw.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\Modem2 (612-31542)\
through FTP (see NOTE 2,3)
Wait for a while (3-5mins) until the right version of FPGA is refreshed on Reprogramming screen
Check MODEM FPGA box and MODEM FIRMWARE box and press TOGGLE
button
Reboot the IDU by navigating to the administration > Reboot screen
When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
Connect again the FTP client to FlexiHybrid via IP address
Repeats steps 15-18 for the other bank.Bank1 and Bank2 must be aligned(same
software in both banks)

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

6.9

Upgrading procedure

IDU software upgrade procedure from SVR 2.2 to SVR 3.1


(one file)
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the puma_package.img software package from the sub-directory
SWSVR3_1\sb-package\ through FTP (after upload, IDU will reboot automatically)
6. Wait for a while till FlexiHybrid.is reachable again via IP address.Click on Administration > Maintenance > Re-programming in order to refresh the Reprogramming
screen to check if the SVR has been successfully upgraded
7. Repeat step 5 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)

6.10

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

IDU software upgrade procedure from SVR 2.2 to SVR 3.1


(separated files without modem hardware change)
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the FPGA of the installed Master IO unit from the subdirectory from the subdirectory SWSVR3_1\ through FTP
6. Upload the Application (puma_app.img) from the sub-directory SWSVR3_1\FlexiHybrid SVR 3_1\ through FTP
7. Upload the ODU library (odu.img) from the sub-directory SWSVR3_1\FlexiHybrid
SVR 3_1\ through FTP
8. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
9. Check the Application box, ODU library box, MASTER IO FPGA box and press
TOGGLE button

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

85

Upgrading procedure

Operate and Maintain

10. Reboot the IDU by navigating to the Administration > Reboot screen
11. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
12. Connect again the FTP client to FlexiHybrid via IP address
13. Repeat steps 5-7 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)

6.11

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

IDU software upgrade procedure from SVR 2.2 to SVR 3.1


(separated files with modem hardware change)
1. Switch WB modem 612-31530 with Unified Modem 612-31542
2. Start with a powered-on FlexiHybrid connected to a personal computer via IP
address
3. Open the WEB User Interface of the FlexiHybrid to be upgraded
4. Click on Administration > Maintenance > Re-programming
5. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
6. Upload the FPGA of the installed Master IO unit from the subdirectory from the subdirectory SWSVR3_1\ through FTP
7. Upload the Application (puma_app.img) from the sub-directory SWSVR3_1\FlexiHybrid SVR 3_1\ through FTP
8. Upload the ODU library (odu.img) from the sub-directory SWSVR3_1\FlexiHybrid
SVR 3_1\ through FTP
9. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
10. Check the Application box, ODU library box, MASTER IO FPGA box and press
TOGGLE button
11. Reboot the IDU by navigating to the Administration > Reboot screen
12. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
13. Connect again the FTP client to FlexiHybrid via IP address
14. Repeat steps 6-8 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)

86

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

15. Upload the modem Firmware (east_modem_fw.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\Modem2 (612-31542)\
through FTP (see NOTE 2,3)
16. Wait for a while (3-5mins) until the right version of Firmware (east_modem_fw.bz2)
is refreshed on Reprogramming screen
17. Upload the modem FPGA (east_modem_fw.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\Modem2 (612-31542)\
through FTP (see NOTE 2,3)
18. Wait for a while (3-5mins) until the right version of FPGA (east_modem_fw.bz2) is
refreshed on Reprogramming screen
19. Check MODEM FPGA box and MODEM FIRMWARE box and press TOGGLE
button
20. Reboot the IDU by navigating to the administration > Reboot screen
21. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
22. Connect again the FTP client to FlexiHybrid via IP address
23. Repeats steps 15-18 for the other bank.Bank1 and Bank2 must be aligned(same
software in both banks)

Note 1: Extra help for FTP client:

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

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

87

Upgrading procedure

Operate and Maintain

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

t
6.12

Note 3: Extra help for downloading modem firmware and FGPA:


When downloading modem FPGA and firmware,sometimes the transfer of file completes in a very short time(in 0.00s), this means the transfer fails,file needs to be
uploaded again.

IDU software upgrade procedure from SVR 3.0 to SVR 3.1


(one file)
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the puma_package.img software package from the sub-directory
SWSVR3_1\sb-package\ through FTP (after upload, IDU will reboot automatically)
6. Wait for a while till FlexiHybrid.is reachable again via IP address.Click on Administration > Maintenance > Re-programming in order to refresh the Reprogramming
screen to check if the SVR has been successfully upgraded
7. Repeat step 5 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)

88

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

6.13

Upgrading procedure

IDU software upgrade procedure from SVR 3.0 to SVR 3.1


(separated files)
1. If WB modem 612-31530 is used, replace it with Unified Modem 2 612-31542
2. Start with a powered-on FlexiHybrid connected to a personal computer via IP
address
3. Open the WEB User Interface of the FlexiHybrid to be upgraded
4. Click on Administration > Maintenance > Re-programming
5. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
6. Upload the FPGA of the installed Master IO unit from the subdirectory from the subdirectory SWSVR3_1\ through FTP
7. Upload the Application (puma_app.img) from the sub-directory SWSVR3_1\FlexiHybrid SVR 3_1\ through FTP
8. Upload the ODU library (odu.img) from the sub-directory SWSVR3_1\FlexiHybrid
SVR 3_1\ through FTP
9. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
10. Check the Application box, ODU library box, MASTER IO FPGA box and press
TOGGLE button
11. Reboot the IDU by navigating to the Administration > Reboot screen
12. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
13. Connect again the FTP client to FlexiHybrid via IP address
14. Repeat steps 6-8 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)
15. Upload the modem Firmware (east_modem_fw.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\Modem2 (612-31542)\
through FTP (see NOTE 2,3)
16. Wait for a while (3-5mins) until the right version of Firmware is refreshed on Reprogramming screen
17. Upload the modem FPGA (east_modem_fw.bz2) of the East Modem (and of the
West Modem if present) from the sub-directory SWSVR3_1\Modem2 (612-31542)\
through FTP (see NOTE 2,3)
18. Wait for a while (3-5mins) until the right version of FPGA is refreshed on Reprogramming screen
19. Check MODEM FPGA box and MODEM FIRMWARE box and press TOGGLE
button
20. Reboot the IDU by navigating to the administration > Reboot screen
21. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
22. Connect again the FTP client to FlexiHybrid via IP address
23. Repeats steps 15-18 for the other bank.Bank1 and Bank2 must be aligned(same
software in both banks)

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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

89

Upgrading procedure

Operate and Maintain

5. Exit
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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.
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 downloaded. 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.

90

Note 3: Extra help for downloading modem firmware and FGPA:


When downloading modem FPGA and firmware,sometimes the transfer of file completes in a very short time(in 0.00s), this means the transfer fails,file needs to be
uploaded again.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

6.14

Upgrading procedure

IDU software downgrade procedure from SVR 3.1 to SVR


2.0
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the Boot (u-boot.bin) from the sub-directory SW7_4\FlexiHybrid SVR 1_3\
through FTP
6. Upload the Kernel 0.3.1 from the sub-directory SW7_4\FlexiHybrid SVR 1_3\
through FTP
7. 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 (612315/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
10. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
11. Check the Application box and ODU library box and FPGA Master box and press
TOGGLE button
12. Reboot the IDU by navigating to the Administration > Reboot screen
13. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
14. Connect again the FTP client to FlexiHybrid via IP address
15. Repeat all the above steps (7-10) for the other bank. Bank 1 and Bank 2 must be
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)
17. Wait for a while until the right version of Firmware W-1.1.3v18t15c is refreshed on
Reprogramming screen
18. Upload the modem FPGA 1710 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. Wait for a while until the right version of FPGA 1710 is refreshed on Reprogramming
screen
20. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
21. 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
22. Upload the modes N2-1B from the sub-directory SW7_6\MODES-N2-V1B\ through
FTP
23. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
24. Check the Modes box and press TOGGLE button

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

91

Upgrading procedure

Operate and Maintain

25. Repeat all the above steps (22-23) for the other bank. Bank 1 and Bank 2 must be
aligned
26. Perform a Link Configuration

Note 1: Extra help for FTP client:

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

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

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

92

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

6.15

Upgrading procedure

IDU software downgrade procedure from SVR 3.1 to SVR


1.4
Controller2 (634-001/91) is not supported with SVR 1.4
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the Boot (u-boot.bin) from the sub-directory SW7_4\FlexiHybrid SVR 1_3\
through FTP
6. Upload the Kernel 0.3.1 from the sub-directory SW7_4\FlexiHybrid SVR 1_3\
through FTP
7. Upload the FPGA of the installed Master IO unit from the sub-directory SW7_5\
through FTP (Note: Standard2 Master IO (612-315/37), Enhanced2 Master IO (612315/39) and GigE Enhanced Master IO (612-315/16) are not supported with SVR
1.4)
8. 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 NOTES 2, 3)
9. Wait for a while (3-5mins) until the right version of Firmware W-1.1.2.10 is refreshed
on Reprogramming screen
10. Upload the modem FPGA 1610 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 NOTES 2, 3)
11. Wait for a while (3-5mins) until the right version of FPGA 1610 is refreshed on Reprogramming screen
12. Upload the Application 2.0.12x from the sub-directory SW7_5\FlexiHybrid SVR 1_4\
through FTP
13. Upload the ODU library N2-2.0.12v3 from the sub-directory SW7_5\FlexiHybrid
SVR 1_4\ through FTP
14. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
15. Check the Kernel box, Application box, controller FPGA box, Master IO FPGA box,
ODU library box and press TOGGLE button
16. Reboot the IDU by navigating to the Administration > Reboot screen
17. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
18. Connect again the FTP client to FlexiHybrid via IP address
19. Repeat steps 6,7,12,13,14 for the other bank. Bank 1 and Bank 2 must be aligned
(same software in both banks)
20. Connect again the FTP client to FlexiHybrid via IP address
21. Upload the modes N2-1B from the sub-directory SW7_5\MODES-N2-V1B\ through
FTP
22. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
23. Check the Modes box and press TOGGLE button
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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

93

Upgrading procedure

Operate and Maintain

Note 1: Extra help for FTP client:

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

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
Host: <ip address 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

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

94

Note 3: Extra help for downloading modem firmware and FGPA:


When downloading modem FPGA and firmware,sometimes the transfer of file completes in a very short time(in 0.00s), this means the transfer fails,file needs to be
uploaded again.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

6.16

Upgrading procedure

IDU software downgrade procedure from SVR 3.1 to SVR


1.3
Controller2 (634-001/91) is not supported with SVR 1.3
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the Boot (u-boot.bin) from the sub-directory SW7_4\FlexiHybrid SVR 1_3\
through FTP
6. Upload the Kernel 0.2.3 from the sub-directory SW7_4\FlexiHybrid SVR 1_3\
through FTP
7. Upload the FPGA of the installed Master IO unit from the sub-directory SW7_4\
through FTP (Note: Standard2 Master IO (612-315/37), Enhanced2 Master IO (612315/39) and GigE Enhanced Master IO (612-315/16) are not supported with SVR
1.3)
8. Upload the modem Firmware W-1.1.2.2 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 NOTES 2, 3)
9. Wait for a while (3-5mins) until the right version of Firmware W-1.1.2.1 is refreshed
on Reprogramming screen
10. Upload the modem FPGA 1110 of the East Modem (and of the West Modem if
present) from the sub-directory SW7_9\Modem WB7-56 (612-31530)\FPGA downgrade SVR 1.3_1.2\ through FTP (see NOTES 2, 3)
11. Wait for a while (3-5mins) until the right version of FPGA 1110 is refreshed on
Reprogramming screen
12. Upload the Application 2.0.6x from the sub-directory SW7_4\FlexiHybrid SVR 1_3
through FTP
13. Upload the ODU library N2-2.0.6 from the sub-directory SW7_4\FlexiHybrid SVR
1_3 through FTP
14. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
15. Check the Application box and ODU library box and press TOGGLE button
16. Check the Kernel box and the FPGA Master box and press TOGGLE button
17. Reboot the IDU by navigating to the Administration > Reboot screen
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 address
20. Repeat steps 6,7,12,13 for the other bank. Bank 1 and Bank 2 must be aligned
(same software in both banks)
21. Click on Administration > Maintenance > Re-programming in order to check if the
SVR has been successfully downgraded
22. Upload the modes N2-1B from the sub-directory SW7_4\MODES-N2-V1B\ through
FTP
23. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
24. Check the Modes box and press TOGGLE button
25. Repeat the above steps 22, 24 for the other bank. Bank 1 and Bank 2 must be
aligned

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

95

Upgrading procedure

Operate and Maintain

26. Perform a Link Configuration

Note 1: Extra help for FTP client:

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

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
Host: <ip address 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

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.
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 to be
lighted with a permanent yellow/orange color.
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 downloaded. You
do not have to toggle modem firmware or FPGA since the modems have only 1 memory
bank.

96

Note 3: Extra help for downloading modem firmware and FGPA:


When downloading modem FPGA and firmware,sometimes the transfer of file completes in a very short time(in 0.00s), this means the transfer fails,file needs to be
uploaded again.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

6.17

Upgrading procedure

IDU software downgrade procedure from SVR 3.1 to SVR


1.2
Controller2 (634-001/91) is not supported with SVR 1.2
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the Boot (u-boot.bin) from the sub-directory SW7_3\ SRA4 HC SVR 1_2\
through FTP
6. Upload the Kernel 0.2.3 from the sub-directory SW7_3\ SRA4 HC SVR 1_2\ through
FTP
7. Upload the FPGA of the installed Master IO unit from the sub-directory SW7_3\
through FTP (Note: Standard2 Master IO (612-315/37), Enhanced2 Master IO (612315/39) and GigE Enhanced Master IO (612-315/16) are not supported with SVR
1.2)
8. Upload the modem FPGA 1110 of the East Modem (and of the West Modem if
present) from the sub-directory SW7_9\Modem WB7-56 (612-31530)\ FPGA downgrade SVR 1.3_1.2\ through FTP (see NOTES 2, 3)
9. Wait for a while (3-5mins) until the right version of FPGA 1110 is refreshed on Reprogramming screen
10. 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 NOTES 2, 3)
11. Wait for a while (3-5mins) until the right version of Firmware W-1.1.2.1 is refreshed
on Reprogramming screen
12. Upload the Application 2.0.P8_1x from the sub-directory SW7_3\ SRA4 HC SVR
1_2\ through FTP
13. Upload the ODU library N2-2.0.P8_1 from the sub-directory SW7_3\ SRA4 HC SVR
1_2\ through FTP
14. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
15. Check the Application box and ODU library ,the Kernel box and the FPGA Master
box and press TOGGLE button
16. Reboot the IDU by navigating to the Administration > Reboot screen
17. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
18. Connect again the FTP client to FlexiHybrid via IP address
19. Repeat all the above steps ( 6, 7, 12, 13) for the other bank. Bank 1 and Bank 2 must
be aligned (same software in both banks)
20. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
21. Connect again the FTP client to FlexiHybrid via IP address
22. Click on Administration > Maintenance > Re-programming in order to check if the
SVR has been successfully downgraded
23. Upload the modes N2-1B from the sub-directory SW7_3\MODES-N2-V1B\ through
FTP
24. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

97

Upgrading procedure

Operate and Maintain

25. Check the Modes box and press TOGGLE button


26. Repeat all the above steps (23-24) for the other bank. Bank 1 and Bank 2 must be
aligned
27. Perform a Link Configuration

Note 1: Extra help for FTP client:

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

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

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

t
98

Note 3: Extra help for downloading modem firmware and FGPA:

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

When downloading modem FPGA and firmware,sometimes the transfer of file completes in a very short time(in 0.00s), this means the transfer fails,file needs to be
uploaded again.

6.18

IDU software downgrade procedure from SVR 3.1 to SVR


2.1 without modem hardware change
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the FPGA of the installed Master IO unit from the sub-directory
SW7_7_2.1.1\ through FTP
6. Upload the Application 2.4.13x from the sub-directory SW7_7_2.1.1\FlexiHybrid
SVR 2_1_1\ through FTP
7. Upload the ODU library N2-2.4.13 from the sub-directory SW7_7_2.1.1\FlexiHybrid
SVR 2_1_1\ through FTP
8. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
9. Check the Application box and ODU library box and FPGA Master box and press
TOGGLE button
10. Reboot the IDU by navigating to the Administration > Reboot screen
11. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
12. Connect again the FTP client to FlexiHybrid via IP address
13. Repeat all the above steps (5-8) for the other bank. Bank 1 and Bank 2 must be
aligned (same software in both banks)

6.19

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

IDU software downgrade procedure from SVR 3.1 to SVR


2.1 with modem hardware change
1. Switch Unified Modem 612-31542 with WB modem 612-31530

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

99

Upgrading procedure

Operate and Maintain

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


address
3. Open the WEB User Interface of the FlexiHybrid to be upgraded
4. Click on Administration > Maintenance > Re-programming
5. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
6. Upload the modem Firmware W-1.1.19 of the East Modem (and of the West Modem
if present) from the sub-directory SW7_9\Modem WB7-56 (612-31530)\ through
FTP (see NOTE 2,3)
7. Wait for a while (3-5mins) until the right version of FPGA 18 is refreshed on Reprogramming screen
8. Upload the modem FPGA 18 of the East Modem (and of the West Modem if present)
from the sub-directory SW7_9\Modem WB7-56 (612-31530)\ through FTP (see
NOTE 2,3)
9. Wait for a while (3-5mins) until the right version of FPGA 18 is refreshed on Reprogramming screen
10. Upload the FPGA of the installed Master IO unit from the sub-directory
SW7_7_2.1.1\ through FTP
11. Upload the Application 2.4.13x from the sub-directory SW7_7_2.1.1\FlexiHybrid
SVR 2_1_1\ through FTP.
12. Upload the ODU library N2-2.4.13 from the sub-directory SW7_7_2.1.1\FlexiHybrid
SVR 2_1_1\ through FTP.
13. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen.
14. Check the Application box and ODU library box and FPGA Master box and press
TOGGLE button.
15. Reboot the IDU by navigating to the Administration > Reboot screen.
16. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
17. Connect again the FTP client to FlexiHybrid via IP address
18. Repeat steps 10-12 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)

100

Note 1: Extra help for FTP client:

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

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

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

t
6.20

Note 3: Extra help for downloading modem firmware and FGPA:


When downloading modem FPGA and firmware,sometimes the transfer of file completes in a very short time(in 0.00s), this means the transfer fails,file needs to be
uploaded again.

IDU software downgrade procedure from SVR 3.1 to SVR


2.2 (one file)
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the puma_package.img software package from the sub-directory SW7_8\
sb-package\ through FTP (after upload, IDU will reboot automatically)
6. Wait for a while till FlexiHybrid.is reachable again via IP address. Click on Administration > Maintenance > Re-programming in order to refresh the Reprogramming
screen to check if the SVR has been successfully upgraded
7. Repeat step 5 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)

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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

101

Upgrading procedure

Operate and Maintain

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

6.21

IDU software downgrade procedure from SVR 3.1 to SVR


2.2 (separated file without modem hardware change)
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the FPGA of the installed Master IO unit from the subdirectory from the subdirectory SW7_8\ through FTP
6. Upload the Application 2.6.11x from the sub-directory SW7_8\FlexiHybrid SVR 2_2\
through FTP.
7. Upload the ODU library N2-2.6.11 from the sub-directory SW7_8\FlexiHybrid SVR
2_2\ through FTP
8. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
9. Check the Application box, ODU library box, MASTER IO FPGA box and press
TOGGLE button
10. Reboot the IDU by navigating to the Administration > Reboot screen
11. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
12. Connect again the FTP client to FlexiHybrid via IP address
13. Repeat steps 5-7 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)

102

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
Host: <ipaddress of FlexiHybrid >
Username "integrator"; password "p1nacate"

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

2.
3.
4.
5.

6.22

Connect to FlexiHybrid (See FTP client Help)


Set to binary mode (see FTP client Help)
Set timeout detection to 999 seconds (see FTP client Help)
Uncheck Use multiple connections to transfer files box

IDU software downgrade procedure from SVR 3.1 to SVR


2.2 (separated file with modem hardware change)
1. Switch Unified Modem 612-31542 with WB modem 612-31530
2. Start with a powered-on FlexiHybrid connected to a personal computer via IP
address
3. Open the WEB User Interface of the FlexiHybrid to be upgraded
4. Click on Administration > Maintenance > Re-programming
5. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
6. Upload the modem Firmware W-1.1.19 of the East Modem (and of the West Modem
if present) from the sub-directory SW7_9\Modem WB7-56 (612-31530)\ through
FTP (see NOTE 2,3)
7. Wait for a while (3-5mins) until the right version of Firmware W-1.1.19 is refreshed
on Reprogramming screen
8. Upload the modem FPGA 18 of the East Modem (and of the West Modem if present)
from the sub-directory SW7_9\Modem WB7-56 (612-31530)\ through FTP (see
NOTE 2,3)
9. Wait for a while (3-5mins) until the right version of FPGA 18 is refreshed on Reprogramming screen
10. Upload the FPGA of the installed Master IO unit from the subdirectory from the subdirectory SW7_8\ through FTP
11. Upload the Application 2.6.11x from the sub-directory SW7_8\FlexiHybrid SVR 2_2\
through FTP
12. Upload the ODU library N2-2.6.11 from the sub-directory SW7_8\FlexiHybrid SVR
2_2\ through FTP
13. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
14. Check the Application box, ODU library box, MASTER IO FPGA box and press
TOGGLE button
15. Reboot the IDU by navigating to the Administration > Reboot screen
16. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
17. Connect again the FTP client to FlexiHybrid via IP address
18. Repeat steps 10-12 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)

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
b) If using a graphical FTP client such as FileZilla

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

103

Upgrading procedure

Operate and Maintain

1. Use the following parameters to connect:


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

t
6.23

Note 3: Extra help for downloading modem firmware and FGPA:


When downloading modem FPGA and firmware,sometimes the transfer of file completes in a very short time(in 0.00s), this means the transfer fails,file needs to be
uploaded again.

IDU software downgrade procedure from SVR 3.1 to SVR


3.0 (one file)
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the puma_package.img software package from the sub-directory SW7_9\
sb-package\ through FTP (after upload, IDU will reboot automatically)

104

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

6. Wait for a while till FlexiHybrid.is reachable again via IP address. Click on Administration > Maintenance > Re-programming in order to refresh the Reprogramming
screen to check if the SVR has been successfully upgraded
7. Repeat step 5 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)

6.24

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

IDU software downgrade procedure from SVR 3.1 to SVR


3.0 (separated file)
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 upgraded
3. Click on Administration > Maintenance > Re-programming
4. Use an FTP client (see NOTE 1) and connect to the FlexiHybrid via IP address
5. Upload the FPGA of the installed Master IO unit from the subdirectory from the subdirectory SW7_8\ through FTP
6. Upload the Application (puma_app.img) from the sub-directory SW7_9\FlexiHybrid
SVR 3_0\ through FTP.
7. Upload the ODU library (odu.img) from the sub-directory SW7_9\FlexiHybrid SVR
3_0\ through FTP
8. Click on Administration > Maintenance > Re-programming in order to refresh the
Reprogramming screen
9. Check the Application box, ODU library box, MASTER IO FPGA box and press
TOGGLE button
10. Reboot the IDU by navigating to the Administration > Reboot screen
11. When the FlexyHybrid is reachable again via IP address, click on Administration >
Maintenance > Re-programming
12. Connect again the FTP client to FlexiHybrid via IP address
13. Repeat steps 5-7 for the other bank. Bank 1 and Bank 2 must be aligned (same
software in both banks)

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.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

105

Upgrading procedure

Operate and Maintain

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
b) If using a graphical FTP client such as FileZilla
1. Use the following parameters to connect:
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

6.25

ODU software upgrade procedure


The FileZilla FTP client may cause FTP upload errors as it sometimes uses nonstandard
commands for uploading files.
1. Rename the ODU software image filename to east_odu_fw.s19.
2. Start with a powered-on IDU
3. 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.s19
3.2 Wait 300 seconds for the ODU software update to complete
4. Log into the IDU web GUI
5. Click on Administration > Maintenance > Re-programming
6. 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 screen
8. Repeat all the steps to replace the west ODU for a fully equipped system type.

6.26

FTP File Transfers


The FileZilla FTP client may cause FTP upload errors as it sometimes uses nonstandard 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

106

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Upgrading procedure

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.

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

107

FTP upload procedures

Operate and Maintain

7 FTP upload procedures


7.1

FTP Upload Procedures


Use an FTP client and connect to the equipment via IP address.

7.2

Windows FTP Client


1.
2.
3.
4.
5.

7.3

Enter the command "ftp <SDIDU IP address>".


Enter the administrator username and password when prompted.
Set the mode to binary by entering "bin".
To upload the file, enter the command "put <filename>".
Exit.

Graphical FTP Client (Filezilla or other FTP programs)


1. Use the following parameters to connect:
a) Host: <SDIDU IP address>
b) Username: Administrator username
c) 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.

108

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

Operate and Maintain

Acronyms and abbreviations

8 Acronyms and abbreviations


AdTPC

Adaptive Power Control

AIS

Alarm Indication Signal

APC

Adaptive Power Control

BER

Bit Error Rate

CLI
Codec
DB
DBm
DSCP
E1
FEC

Command Line Interface


Coder-Decoder
Decibel
Decibel relative to 1 mW
Differentiated Service Code Point
2048 Kb/s Signal
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

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011

109

Acronyms and abbreviations

ODU

Outdoor Unit

PDH

Plesiochronous Digital Hierarchy

QAM

Quadrature Amplitude Modulation

QoS

Quality of Service

QPSK

Radio Frequency

RS

Regenerator Section

RSL

Received Signal Level (in dBm)

RST

Regenerator Section Termination

RX

Regenerator Section Overhead


Receiver

SFP

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

STP

Spanning Tree Protocol

SNMP
SNR
SONET
SSH

Simple Network Management Protocol


Signal-to-Noise Ratio (Energy per bit to Noise ratio, Eb/No)
Synchronous Optical Network
Secure Shell

STM-1

Synchronous Transport Module 1

TCP/IP

Transmission Control Protocol/Internet Protocol

ToS
TX

110

Quadrature Phase Shift Keying

RF

RSOH

Operate and Maintain

Type of Service
Transmitter

A25000-A0300-J019-01-76P1
Issue: 1 Issue date: January 2011