lct for flexipacket microwave, rel. 3.4 operating documentation, issue 02.pdf

8/21/2019 lct for flexipacket microwave, rel. 3.4 operating documentation, issue 02.pdf

http://slidepdf.com/reader/full/lct-for-flexipacket-microwave-rel-34-operating-documentation-issue-02pdf 1/387

Operating Manual

LCT 3.4LCT for FlexiPacket Microwave

OMN

911-457/02A0340Issue 1, October 2011



The information in this document is subject to change without notice and describes only the product defined in the introduction of this

documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement

under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the

prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained

personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of

the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or

software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively

and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all

reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia

Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKSBE 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.

LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011



STATUS OF THE MANUAL

R-1LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011

This Manual describes the installation, the configuration and the operating guide of LCT

for FlexiPacket Microwave.


– Current: Issue 1, October 2011

– Previous:




R-2LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

B L A N

K P A G E



INDEX

I-1LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011

INDEX

STATUS OF THE MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R.1

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.1

LIST OF THE FIGURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.7

LIST OF THE TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.17

1 GENERAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1

1.1 Subject and Purpose of the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1

1.2 LCT Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2

1.3 Delivery Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7

1.4 Licenses to Use the Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7

1.5 Related Manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7

1.6 List of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.8

2 LCT FUNCTIONS AND FEATURES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

2.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

2.2 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2

2.3 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4

2.4 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5

2.5 Security of NE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7

2.6 Supported Radio Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8

2.7 LCT Usage Modalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9

2.8 Connection with Priority from LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10

2.9 File Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.102.9.1 Configuration of FTP Server for FlexiPacket Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10

2.10 NAPT functionality on F interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.13

2.11 Characteristics of TCP/IP Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.132.11.1 Address format for TCP/IP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.132.11.1.1 Host and router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.132.11.1.2 IP address classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.132.11.1.3 Decimal notation of the IP address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.152.11.1.4 Net-Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.152.11.1.5 Reserved address values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.162.11.2 TCP/IP protocol stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.172.11.3 TCP/IP protocol of the LCT PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.202.11.4 Name solving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.202.11.5 Auxiliary utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.20

2.12 Validity Conditions of TCP/IP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.21

http://stile.pdf/

http://stile.pdf/



INDEX

I-2LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

2.12.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.212.12.2 Validity conditions for IP addresses and Net-Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.212.12.2.1 IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.212.12.2.2 Net-Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.23

2.12.2.3 IP address - Net-Mask combinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.252.12.3 Validity conditions for parameters of the static routing table . . . . . . . . . . . . . . . . . . . . . . . . 2.262.12.4 Validity conditions for the F interface parameters (PC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.272.12.5 Reset of the TCP/IP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.27

2.13 Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.27

2.14 Local Equipment Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.282.14.1 “LCT - local equipment” connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.282.14.2 Local map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.312.14.3 Testing of the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.31

2.15 Radio Link Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.322.15.1 LCT - radio link “connection” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.32

2.15.2 Routing functions of the NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.342.15.3 Routing tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.342.15.4 Hosts table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.352.15.5 Planning and configuration of a radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.352.15.5.1 Planning of IP addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.352.15.5.2 Creation of the link map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.362.15.5.3 Configuration of the link parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.362.15.5.4 Testing of the radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.372.15.5.5 Examples of radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.372.15.5.6 Main problems occurring in the radio link management . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.39

3 SOFTWARE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

3.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.13.2.1 Requirements for LCT PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

3.3 Installation of Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2

3.4 Installation of LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.23.4.1 Setup procedure of LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.33.4.2 Plug-ins installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.73.4.3 FileZilla FTP Server installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.83.4.4 Online Help installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8

3.4.5 Menu and Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.103.4.6 Maintenance and Remove procedure of LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11

3.5 Legal Log-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.13

4 CONFIGURATION OF THE LCT PC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1

4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1

4.2 Configuration of the LCT - Radio Equipment Connection on F interface . . . . . . . . . . . . . . . 4.14.2.1 Configuration of the dial-up connection in Microsoft Windows Vista . . . . . . . . . . . . . . . . . . . 4.24.2.1.1 Installation of the direct connection via cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2

4.2.1.2 Creation and configuration of the dial-up connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.74.2.1.3 Configuration of the TCP/IP protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.19



INDEX


4.2.2 Configuration of the dial-up connection in Microsoft Windows XP . . . . . . . . . . . . . . . . . . . . 4.254.2.2.1 Installation of the direct connection via cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.254.2.2.2 Creation and configuration of the dial-up connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.304.2.2.3 Configuration of the TCP/IP protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.38

4.3 Configuration of the LCT - Radio Equipment Connection on Ethernet Interface . . . . . . . . . 4.444.3.1 Configuration of the TCP/IP protocol in Microsoft Windows Vista . . . . . . . . . . . . . . . . . . . . 4.444.3.2 Configuration of the TCP/IP protocol in Microsoft Windows XP . . . . . . . . . . . . . . . . . . . . . . 4.48

5 LCT - RADIO EQUIPMENT CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1

5.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1

5.2 LCT - Radio Equipment Connection Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.15.2.1 Direct connection on F interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.15.2.1.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1

5.2.1.2 Requirements of RS-232C serial cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.25.2.2 Remote connection on F interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.35.2.2.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.35.2.2.2 Characteristics of the connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.45.2.2.3 Characteristics and configuration of the modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.55.2.3 Direct connection on Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.65.2.4 Connection via LAN Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7

5.3 Activation of LCT - Radio Equipment Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.85.3.1 Activation of the dial-up connection in Microsoft Windows Vista . . . . . . . . . . . . . . . . . . . . . . 5.85.3.2 Activation of the dial-up connection in Microsoft Windows XP . . . . . . . . . . . . . . . . . . . . . . . 5.11

5.4 Routing Troubles with the TCP/IP Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.195.4.1 Common cases of TCP/IP packet routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.195.4.2 Useful commands to solve reachability problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.225.4.2.1 Status window of the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.225.4.2.2 The “ipconfig” command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.235.4.2.3 The “route print” command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.235.4.2.4 The “route add” command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.245.4.2.5 The “tracert” command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.24

5.5 Troubles in the Dial-up Connection to the Local Equipment . . . . . . . . . . . . . . . . . . . . . . . . 5.245.5.1 Local equipment not reachable using the default local IP address . . . . . . . . . . . . . . . . . . . 5.245.5.2 Deactivation of the dial-up connection for traffic absence . . . . . . . . . . . . . . . . . . . . . . . . . . 5.255.5.3 Detection of the local equipment IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.25

6 OPERATING GUIDE OF LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1

6.1 Features of LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1

6.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.26.2.1 Title bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36.2.2 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36.2.3 Tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36.2.4 Displaying area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.46.2.4.1 Map Tree View frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.76.2.4.2 NE View frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.86.2.4.3 Map View frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8

6.2.4.3.1 Map window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.86.2.4.3.2 Form and dialog windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10



INDEX

I-4LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

6.2.5 Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.12

6.3 Security of NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.13

6.4 NE Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.14

6.5 Statuses of NE and LCT - NE Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.156.5.1 Status transitions of NE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.166.5.2 Management and displaying of the NE status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.17

6.6 Severity Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.18

6.7 File Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.19

6.8 User Settings and Data Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.206.8.1 User data saved in the system user profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.206.8.2 User settings saved in the system All Users profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20

6.9 Start-up of LCT and Login to NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.206.9.1 LCTStart application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.21

6.9.1.1 Start-up of LCTStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.216.9.1.2 “auto.map” map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.226.9.1.3 LCTStart user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.236.9.1.4 Automatic creation of the map for locally connected NE. . . . . . . . . . . . . . . . . . . . . . . . . . . 6.246.9.1.5 “Find NE” functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.256.9.2 Opening of the GUI of LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.266.9.3 Opening of the map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.276.9.4 Opening of NE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.29

6.10 File Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.366.10.1 Open Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.366.10.2 Close Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.386.10.3 Open auto.map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.386.10.4 Exit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.39

6.11 Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.396.11.1 Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.396.11.2 Field Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.42

6.12 Window Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.436.12.1 Cascade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.436.12.2 Close All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.436.12.3 Iconize All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.436.12.4 Move Map to Top. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.436.12.5 Move Map to Bottom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.43

6.13 Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.446.13.1 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.446.13.2 Using Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.446.13.3 Help Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.446.13.4 About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.44

6.14 Pop-Up Menu of NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.456.14.1 Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.456.14.2 Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.45

6.15 Pop-Up Menu of Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.46

6.16 Applications of NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.486.16.1 History Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.48

6.16.2 Local History Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.536.16.3 Commissioning Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.56



INDEX


6.16.4 Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.606.16.5 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.626.16.5.1 Create Service Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.646.16.5.2 Create Pseudo Wire service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.67

6.16.5.3 Create New Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.716.16.5.4 Create Bundling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.736.16.5.5 Delete Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.776.16.5.6 Modify Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.776.16.5.7 Modify Admin Status of Pseudowires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.796.16.5.8 Modify Pseudowires of a service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.816.16.5.9 Modify Bundlings of a service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.836.16.5.10 Create Protection for a service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.85

6.17 Plug-in Common Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.886.17.1 Setting of date and time of NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.886.17.2 Loading/storing of the NE configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.916.17.2.1 Copy NE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.91

6.17.2.2 Paste NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.936.17.3 Recording of the G.821/G.826 performances referred to quarter intervals . . . . . . . . . . . . . 6.956.17.4 Report of the inventory data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1026.17.5 Telemeasurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1056.17.6 Graphic tool for the measure displaying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1086.17.6.1 Chart modality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1086.17.6.1.1 Chart Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1126.17.6.2 Data modality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1196.17.7 FTP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1216.17.8 Table management tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1256.17.9 Configuration of the RF frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1286.17.10 Setting of date and time in the commissioning test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.129

7 OPERATING GUIDE OF NETBUILDER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1

7.1 NetBuilder Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1

7.2 Operating Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3

7.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.47.3.1 Title bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.47.3.2 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.57.3.3 Tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.57.3.4 Displaying area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.67.3.4.1 Map Tree View frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.67.3.4.2 Edit Map View frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.77.3.5 Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8

7.4 Program Start-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.9

7.5 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.107.5.1 New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.107.5.2 Open. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.107.5.3 Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.127.5.4 Open auto.map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.127.5.5 Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.137.5.6 Save As . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.137.5.7 New Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.14

7.5.7.1 Standard Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.157.5.7.2 Smart Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.18



INDEX

I-6LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

7.5.8 Exit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.24

7.6 Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.247.6.1 Arrange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.25

7.6.2 Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.257.6.3 New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.257.6.3.1 Net-Element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.267.6.3.1.1 NE advanced properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.287.6.4 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.297.6.4.1 Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.307.6.4.2 Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.307.6.4.3 Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.317.6.4.4 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.31

7.7 Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.327.7.1 Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.32

7.8 Window Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.33

7.8.1 Cascade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.347.8.2 Tile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.347.8.3 Close All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.34

7.9 Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.347.9.1 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.347.9.2 Using Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.347.9.3 About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.34

7.10 Pop-Up Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.357.10.1 Map pop-up menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.357.10.2 NE pop-up menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.367.10.2.1 NE Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.36

7.10.2.2 Cut NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.377.10.2.3 NE Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.377.10.2.4 NE Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.37

A LICENSES TO USE THE SOFTWARE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.1

A.1 License to Use the LCT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.1

A.2 Licence to Use the Third Party Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.5




LIST OF THE FIGURES

LIST OF THE FIGURES

Fig. 2.1 FTP Publishing Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.11Fig. 2.2 Configuration of the user permissions for FTP Default Site (1/2) . . . . . . . . . . . . . . . . . . . . . . . . . . 2.12Fig. 2.3 Configuration of the user permissions for FTP Default Site (2/2) . . . . . . . . . . . . . . . . . . . . . . . . . . 2.12Fig. 2.4 Structure of IP addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.14Fig. 2.5 Example of Net-Mask for Class B IP address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.16Fig. 2.6 TCP/IP protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.18Fig. 2.7 TCP/IP protocol stack for LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.19Fig. 2.8 LCT software elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.28Fig. 2.9 Connection between LCT PC and local radio equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.29Fig. 2.10 Connection between LCT PC and radio nodes of the same radio station . . . . . . . . . . . . . . . . . . . 2.30Fig. 2.11 Connection between LCT PC and local FlexiPacketRadio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.30

Fig. 2.12 Radio link structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.32Fig. 2.13 Radio link structure with repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.33Fig. 2.14 Example of a stand-alone radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.38Fig. 2.15 Example of a remote radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.38Fig. 3.1 Installation of LCT (1/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4Fig. 3.2 Installation of LCT (2/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5Fig. 3.3 Installation of LCT (3/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5Fig. 3.4 Installation of LCT (4/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6Fig. 3.5 Installation of LCT (5/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6Fig. 3.6 Installation of LCT (6/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6Fig. 3.7 Plug-ins installation (1/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7Fig. 3.8 Plug-ins Installation (2/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7Fig. 3.9 FileZilla FTP Server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8

Fig. 3.10 Online Help installation (1/2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9Fig. 3.11 Online Help installation (2/2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9Fig. 3.12 LCT menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10Fig. 3.13 LCT Services Manager service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11Fig. 3.14 Icon of LCTStart running. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11Fig. 3.15 LCT command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11Fig. 3.16 Maintenance of LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.12Fig. 3.17 Legal log-in window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.13Fig. 4.1 Installation of the direct connection in Microsoft Windows Vista (1/11) . . . . . . . . . . . . . . . . . . . . . . 4.3Fig. 4.2 Installation of the direct connection in Microsoft Windows Vista (2/11) . . . . . . . . . . . . . . . . . . . . . . 4.3Fig. 4.3 Installation of the direct connection in Microsoft Windows Vista (3/11) . . . . . . . . . . . . . . . . . . . . . . 4.4Fig. 4.4 Installation of the direct connection in Microsoft Windows Vista (4/11) . . . . . . . . . . . . . . . . . . . . . . 4.4

Fig. 4.5 Installation of the direct connection in Microsoft Windows Vista (5/11) . . . . . . . . . . . . . . . . . . . . . . 4.5Fig. 4.6 Installation of the direct connection in Microsoft Windows Vista (6/11) . . . . . . . . . . . . . . . . . . . . . . 4.5Fig. 4.7 Installation of the direct connection in Microsoft Windows Vista (7/11) . . . . . . . . . . . . . . . . . . . . . . 4.5Fig. 4.8 Installation of the direct connection in Microsoft Windows Vista (8/11) . . . . . . . . . . . . . . . . . . . . . . 4.6Fig. 4.9 Installation of the direct connection in Microsoft Windows Vista (9/11) . . . . . . . . . . . . . . . . . . . . . . 4.6Fig. 4.10 Installation of the direct connection in Microsoft Windows Vista (10/11) . . . . . . . . . . . . . . . . . . . . . 4.6Fig. 4.11 Installation of the direct connection in Microsoft Windows Vista (11/11) . . . . . . . . . . . . . . . . . . . . . 4.7Fig. 4.12 Creation and configuration of the dial-up connection in Microsoft Windows Vista (1/22). . . . . . . . . 4.9Fig. 4.13 Creation and configuration of the dial-up connection in Microsoft Windows Vista (2/22). . . . . . . . . 4.9Fig. 4.14 Creation and configuration of the dial-up connection in Microsoft Windows Vista (3/22) . . . . . . . . 4.10Fig. 4.15 Creation and configuration of the dial-up connection in Microsoft Windows Vista (4/22) . . . . . . . . 4.10Fig. 4.16 Creation and configuration of the dial-up connection in Microsoft Windows Vista (5/22) . . . . . . . . 4.11Fig. 4.17 Creation and configuration of the dial-up connection in Microsoft Windows Vista (6/22) . . . . . . . . 4.11Fig. 4.18 Creation and configuration of the dial-up connection in Microsoft Windows Vista (7/22) . . . . . . . . 4.12

http://stile.pdf/

http://stile.pdf/



I-8LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

LIST OF THE FIGURES

Fig. 4.19 Creation and configuration of the dial-up connection in Microsoft Windows Vista (8/22) . . . . . . . 4.12Fig. 4.20 Creation and configuration of the dial-up connection in Microsoft Windows Vista (9/22) . . . . . . . 4.13Fig. 4.21 Creation and configuration of the dial-up connection in Microsoft Windows Vista (10/22) . . . . . . 4.13Fig. 4.22 Creation and configuration of the dial-up connection in Microsoft Windows Vista (11/22) . . . . . . 4.14

Fig. 4.23 Creation and configuration of the dial-up connection in Microsoft Windows Vista (12/22) . . . . . . 4.14Fig. 4.24 Creation and configuration of the dial-up connection in Microsoft Windows Vista (13/22) . . . . . . 4.15Fig. 4.25 Creation and configuration of the dial-up connection in Microsoft Windows Vista (14/22) . . . . . . 4.15Fig. 4.26 Creation and configuration of the dial-up connection in Microsoft Windows Vista (15/22) . . . . . . 4.16Fig. 4.27 Creation and configuration of the dial-up connection in Microsoft Windows Vista (16/22) . . . . . . 4.16Fig. 4.28 Creation and configuration of the dial-up connection in Microsoft Windows Vista (17/22) . . . . . . 4.16Fig. 4.29 Creation and configuration of the dial-up connection in Microsoft Windows Vista (18/22) . . . . . . 4.17Fig. 4.30 Creation and configuration of the dial-up connection in Microsoft Windows Vista (19/22) . . . . . . 4.17Fig. 4.31 Creation and configuration of the dial-up connection in Microsoft Windows Vista (20/22) . . . . . . 4.18Fig. 4.32 Creation and configuration of the dial-up connection in Microsoft Windows Vista (21/22) . . . . . . 4.18Fig. 4.33 Creation and configuration of the dial-up connection in Microsoft Windows Vista (22/22) . . . . . . 4.19Fig. 4.34 Configuration of the TCP/IP protocol in Microsoft Windows Vista (1/11). . . . . . . . . . . . . . . . . . . . 4.20

Fig. 4.35 Configuration of the TCP/IP protocol in Microsoft Windows Vista (2/11). . . . . . . . . . . . . . . . . . . . 4.20Fig. 4.36 Configuration of the TCP/IP protocol in Microsoft Windows Vista (3/11). . . . . . . . . . . . . . . . . . . . 4.21Fig. 4.37 Configuration of the TCP/IP protocol in Microsoft Windows Vista (4/11). . . . . . . . . . . . . . . . . . . . 4.21Fig. 4.38 Configuration of the TCP/IP protocol in Microsoft Windows Vista (5/11). . . . . . . . . . . . . . . . . . . . 4.22Fig. 4.39 Configuration of the TCP/IP protocol in Microsoft Windows Vista (6/11). . . . . . . . . . . . . . . . . . . . 4.22Fig. 4.40 Configuration of the TCP/IP protocol in Microsoft Windows Vista (7/11). . . . . . . . . . . . . . . . . . . . 4.23Fig. 4.41 Configuration of the TCP/IP protocol in Windows Vista (8/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.23Fig. 4.42 Configuration of the TCP/IP protocol in Windows Vista (9/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.24Fig. 4.43 Configuration of the TCP/IP protocol in Windows Vista (10/11) . . . . . . . . . . . . . . . . . . . . . . . . . . 4.24Fig. 4.44 Configuration of the TCP/IP protocol in Windows Vista (11/11) . . . . . . . . . . . . . . . . . . . . . . . . . . 4.25Fig. 4.45 Installation of the direct connection in Microsoft Windows XP (1/12) . . . . . . . . . . . . . . . . . . . . . . 4.26Fig. 4.46 Installation of the direct connection in Microsoft Windows XP (2/12) . . . . . . . . . . . . . . . . . . . . . . 4.27Fig. 4.47 Installation of the direct connection in Microsoft Windows XP (3/12) . . . . . . . . . . . . . . . . . . . . . . 4.27Fig. 4.48 Installation of the direct connection in Microsoft Windows XP (4/12) . . . . . . . . . . . . . . . . . . . . . . 4.28Fig. 4.49 Installation of the direct connection in Microsoft Windows XP (5/12) . . . . . . . . . . . . . . . . . . . . . . 4.28Fig. 4.50 Installation of the direct connection in Microsoft Windows XP (6/12) . . . . . . . . . . . . . . . . . . . . . . 4.28Fig. 4.51 Installation of the direct connection in Microsoft Windows XP (7/12) . . . . . . . . . . . . . . . . . . . . . . 4.28Fig. 4.52 Installation of the direct connection in Microsoft Windows XP (8/12) . . . . . . . . . . . . . . . . . . . . . . 4.29Fig. 4.53 Installation of the direct connection in Microsoft Windows XP (9/12) . . . . . . . . . . . . . . . . . . . . . . 4.29Fig. 4.54 Installation of the direct connection in Microsoft Windows XP (10/12) . . . . . . . . . . . . . . . . . . . . . 4.29Fig. 4.55 Installation of the direct connection in Microsoft Windows XP (11/12) . . . . . . . . . . . . . . . . . . . . . 4.30Fig. 4.56 Installation of the direct connection in Microsoft Windows XP (12/12) . . . . . . . . . . . . . . . . . . . . . 4.30Fig. 4.57 Creation and configuration of the dial-up connection in Microsoft Windows XP (1/15) . . . . . . . . . 4.31Fig. 4.58 Creation and configuration of the dial-up connection in Microsoft Windows XP (2/15) . . . . . . . . . 4.32Fig. 4.59 Creation and configuration of the dial-up connection in Windows XP (3/15). . . . . . . . . . . . . . . . . 4.32

Fig. 4.60 Creation and configuration of the dial-up connection in Microsoft Windows XP (4/15) . . . . . . . . . 4.32Fig. 4.61 Creation and configuration of the dial-up connection in Microsoft Windows XP (5/15) . . . . . . . . . 4.33Fig. 4.62 Creation and configuration of the dial-up connection in Microsoft Windows XP (6/15) . . . . . . . . . 4.33Fig. 4.63 Creation and configuration of the dial-up connection in Microsoft Windows XP (7/15) . . . . . . . . . 4.34Fig. 4.64 Creation and configuration of the dial-up connection in Microsoft Windows XP (8/15) . . . . . . . . . 4.34Fig. 4.65 Creation and configuration of the dial-up connection in Microsoft Windows XP (9/15) . . . . . . . . . 4.35Fig. 4.66 Creation and configuration of the dial-up connection in Microsoft Windows XP (10/15) . . . . . . . . 4.35Fig. 4.67 Creation and configuration of the dial-up connection in Microsoft Windows XP (11/15) . . . . . . . . 4.36Fig. 4.68 Creation and configuration of the dial-up connection in Microsoft Windows XP (12/15) . . . . . . . . 4.36Fig. 4.69 Creation and configuration of the dial-up connection in Microsoft Windows XP (13/15) . . . . . . . . 4.37Fig. 4.70 Creation and configuration of the dial-up connection in Microsoft Windows XP (14/15) . . . . . . . . 4.37Fig. 4.71 Creation and configuration of the dial-up connection in Microsoft Windows XP (15/15) . . . . . . . . 4.38

Fig. 4.72 Configuration of the TCP/IP protocol in Microsoft Windows XP (1/10) . . . . . . . . . . . . . . . . . . . . . 4.39Fig. 4.73 Configuration of the TCP/IP protocol in Microsoft Windows XP (2/10) . . . . . . . . . . . . . . . . . . . . . 4.39




LIST OF THE FIGURES

Fig. 4.74 Configuration of the TCP/IP protocol in Microsoft Windows XP (3/10). . . . . . . . . . . . . . . . . . . . . . 4.40Fig. 4.75 Configuration of the TCP/IP protocol in Microsoft Windows XP (4/10). . . . . . . . . . . . . . . . . . . . . . 4.40Fig. 4.76 Configuration of the TCP/IP protocol in Microsoft Windows XP (5/10). . . . . . . . . . . . . . . . . . . . . . 4.41Fig. 4.77 Configuration of the TCP/IP protocol in Microsoft Windows XP (6/10). . . . . . . . . . . . . . . . . . . . . . 4.41

Fig. 4.78 Configuration of the TCP/IP protocol in Microsoft Windows XP (7/10). . . . . . . . . . . . . . . . . . . . . . 4.41Fig. 4.79 Configuration of the TCP/IP protocol in Microsoft Windows XP (8/10). . . . . . . . . . . . . . . . . . . . . . 4.42Fig. 4.80 Configuration of the TCP/IP protocol in Microsoft Windows XP (9/10). . . . . . . . . . . . . . . . . . . . . . 4.42Fig. 4.81 Configuration of the TCP/IP protocol in Microsoft Windows XP (10/10). . . . . . . . . . . . . . . . . . . . . 4.43Fig. 4.82 TCP/IP protocol configuration in Microsoft Windows Vista (1/7) . . . . . . . . . . . . . . . . . . . . . . . . . . 4.45Fig. 4.83 TCP/IP protocol configuration in Microsoft Windows Vista (2/7) . . . . . . . . . . . . . . . . . . . . . . . . . . 4.45Fig. 4.84 TCP/IP protocol configuration in Microsoft Windows Vista (3/7) . . . . . . . . . . . . . . . . . . . . . . . . . . 4.46Fig. 4.85 TCP/IP protocol configuration in Microsoft Windows Vista (4/7) . . . . . . . . . . . . . . . . . . . . . . . . . . 4.46Fig. 4.86 TCP/IP protocol configuration in Microsoft Windows Vista (5/7) . . . . . . . . . . . . . . . . . . . . . . . . . . 4.47Fig. 4.87 TCP/IP protocol configuration in Microsoft Windows Vista (6/7) . . . . . . . . . . . . . . . . . . . . . . . . . . 4.47Fig. 4.88 TCP/IP protocol configuration in Microsoft Windows Vista (7/7) . . . . . . . . . . . . . . . . . . . . . . . . . . 4.48Fig. 4.89 Configuration of the TCP/IP protocol in Microsoft Windows XP (1/9). . . . . . . . . . . . . . . . . . . . . . . 4.49

Fig. 4.90 Configuration of the TCP/IP protocol in Microsoft Windows XP (2/9). . . . . . . . . . . . . . . . . . . . . . . 4.50Fig. 4.91 Configuration of the TCP/IP protocol in Microsoft Windows XP (3/9). . . . . . . . . . . . . . . . . . . . . . . 4.50Fig. 4.92 Configuration of the TCP/IP protocol in Microsoft Windows XP (4/9). . . . . . . . . . . . . . . . . . . . . . . 4.51Fig. 4.93 Configuration of the TCP/IP protocol in Microsoft Windows XP (5/9). . . . . . . . . . . . . . . . . . . . . . . 4.51Fig. 4.94 Configuration of the TCP/IP protocol in Microsoft Windows XP (6/9). . . . . . . . . . . . . . . . . . . . . . . 4.52Fig. 4.95 Configuration of the TCP/IP protocol in Microsoft Windows XP (7/9). . . . . . . . . . . . . . . . . . . . . . . 4.52Fig. 4.96 Configuration of the TCP/IP protocol in Microsoft Windows XP (8/9). . . . . . . . . . . . . . . . . . . . . . . 4.53Fig. 4.97 Configuration of the TCP/IP protocol in Microsoft Windows XP (9/9). . . . . . . . . . . . . . . . . . . . . . . 4.53Fig. 5.1 LCT - radio equipment direct connection on F interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1Fig. 5.2 LCT - radio link direct connection on F interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2Fig. 5.3 RS-232C connecting cable between LCT and radio equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2Fig. 5.4 LCT - radio equipment remote connection on F interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3Fig. 5.5 LCT - radio link remote connection on F interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4Fig. 5.6 LCT - radio equipment direct connection on Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6Fig. 5.7 LCT - radio link direct connection on Ethernet interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6Fig. 5.8 FlexiPacketRadio local connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7Fig. 5.9 LCT - radio equipment connection through LAN Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7Fig. 5.10 LCT - radio link connection through LAN Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.8Fig. 5.11 Activation of the dial-up connection in Microsoft Windows Vista (1/5) . . . . . . . . . . . . . . . . . . . . . . . 5.9Fig. 5.12 Activation of the dial-up connection in Microsoft Windows Vista (2/5) . . . . . . . . . . . . . . . . . . . . . . 5.10Fig. 5.13 Activation of the dial-up connection in Microsoft Windows Vista (3/5) . . . . . . . . . . . . . . . . . . . . . . 5.10Fig. 5.14 Activation of the dial-up connection in Microsoft Windows Vista (4/5) . . . . . . . . . . . . . . . . . . . . . . 5.11Fig. 5.15 Activation of the dial-up connection in Microsoft Windows Vista (5/5) . . . . . . . . . . . . . . . . . . . . . . 5.11Fig. 5.16 Activation of the dial-up connection in Microsoft Windows XP (1/13). . . . . . . . . . . . . . . . . . . . . . . 5.13Fig. 5.17 Activation of the dial-up connection in Microsoft Windows XP (2/13). . . . . . . . . . . . . . . . . . . . . . . 5.13

Fig. 5.18 Activation of the dial-up connection in Microsoft Windows XP (3/13). . . . . . . . . . . . . . . . . . . . . . . 5.14Fig. 5.19 Activation of the dial-up connection in Microsoft Windows XP (4/13). . . . . . . . . . . . . . . . . . . . . . . 5.14Fig. 5.20 Activation of the dial-up connection in Microsoft Windows XP (5/13). . . . . . . . . . . . . . . . . . . . . . . 5.15Fig. 5.21 Activation of the dial-up connection in Microsoft Windows XP (6/13). . . . . . . . . . . . . . . . . . . . . . . 5.15Fig. 5.22 Activation of the dial-up connection in Microsoft Windows XP (7/13). . . . . . . . . . . . . . . . . . . . . . . 5.16Fig. 5.23 Activation of the dial-up connection in Microsoft Windows XP (8/13). . . . . . . . . . . . . . . . . . . . . . . 5.16Fig. 5.24 Activation of the dial-up connection in Microsoft Windows XP (9/13). . . . . . . . . . . . . . . . . . . . . . . 5.16Fig. 5.25 Activation of the dial-up connection in Microsoft Windows XP (10/13). . . . . . . . . . . . . . . . . . . . . . 5.17Fig. 5.26 Activation of the dial-up connection in Microsoft Windows XP (11/13). . . . . . . . . . . . . . . . . . . . . . 5.17Fig. 5.27 Activation of the dial-up connection in Microsoft Windows XP (12/13). . . . . . . . . . . . . . . . . . . . . . 5.18Fig. 5.28 Activation of the dial-up connection in Microsoft Windows XP (13/13). . . . . . . . . . . . . . . . . . . . . . 5.18Fig. 5.29 Forcing of “Use default gateway on remote network” option in Microsoft Windows Vista . . . . . . . 5.20

Fig. 5.30 Forcing of “Use default gateway on remote network” option in Microsoft Windows XP . . . . . . . . . 5.21Fig. 5.31 Status window of the connection in Microsoft Windows Vista . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.22



I-10LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

LIST OF THE FIGURES

Fig. 5.32 Status window of the connection in Microsoft Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.22Fig. 5.33 The “ipconfig” command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.23Fig. 5.34 The “route print” command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.23Fig. 5.35 The “tracert” command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.24

Fig. 5.36 “ping –t” command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.25Fig. 6.1 LCT user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2Fig. 6.2 Displaying of the iconized frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5Fig. 6.3 Displaying with side frame closed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5Fig. 6.4 Displaying of mobile frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6Fig. 6.5 Map Tree View frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7Fig. 6.6 NE frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8Fig. 6.7 NE frame: node pop-up menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8Fig. 6.8 Map View frame. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9Fig. 6.9 Tooltip window on NE (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10Fig. 6.10 Field Editing window: selection of a value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.11Fig. 6.11 Field Editing window: data entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.11

Fig. 6.12 Action window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.12Fig. 6.13 Status bar: information on the NE connection status (example) . . . . . . . . . . . . . . . . . . . . . . . . . . 6.13Fig. 6.14 NE status transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.16Fig. 6.15 NE “unknown” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.18Fig. 6.16 Indication of summarized severity of NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.19Fig. 6.17 LCT Services Manager service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.22Fig. 6.18 Icon of LCTStart running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.22Fig. 6.19 RunLctStart command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.22Fig. 6.20 Example of “auto.map” map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.23Fig. 6.21 LCTStart: pop-up menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.24Fig. 6.22 LCTStart: About window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.24Fig. 6.23 LCTStart: tooltip window for the indication of the activation status . . . . . . . . . . . . . . . . . . . . . . . . 6.24Fig. 6.24 LCTStart: message of NE locally connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.25Fig. 6.25 LCTStart: pop-up menu in case of locally connected NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.25Fig. 6.26 Find NE: setting of the starting NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.25Fig. 6.27 Find NE: message of NE not found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.26Fig. 6.28 LCT: shortcut to open the GUI of LCT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.26Fig. 6.29 LCT: splash screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.27Fig. 6.30 GUI of LCT without open map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.27Fig. 6.31 LCT with open map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.28Fig. 6.32 Command for NE opening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.29Fig. 6.33 Login window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.30Fig. 6.34 Login phase in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.31Fig. 6.35 Window for denied access to NE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.31Fig. 6.36 Login succeeded and NE open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.32

Fig. 6.37 Login window: Admin/Read Write user class and functionality of connection with priority supported andenabled6.33

Fig. 6.38 Login window: selection of connection with priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.34Fig. 6.39 Error window for incorrect value of timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.34Fig. 6.40 Window of confirmation of the connection with priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.35Fig. 6.41 Login window: Read Only user class and functionality of connection with priority supported and

enabled 6.35Fig. 6.42 Login window: functionality of connection with priority not supported or supported but disabled . 6.35Fig. 6.43 File menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36Fig. 6.44 Window for Open Map command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.37Fig. 6.45 Error message for map containing too many NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.37Fig. 6.46 Error message for map containing NEs with different protocols . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38

Fig. 6.47 Error message for map containing sub-maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38Fig. 6.48 Error message for empty map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38




LIST OF THE FIGURES

Fig. 6.49 Window for the confirmation of the map closing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38Fig. 6.50 Window to confirm the exit from LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.39Fig. 6.51 Options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.39Fig. 6.52 Color Selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.41

Fig. 6.53 Color window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.41Fig. 6.54 Field Status Display Selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.42Fig. 6.55 Window menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.43Fig. 6.56 Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.44Fig. 6.57 About Local Craft Terminal window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.45Fig. 6.58 Pop-up menu of NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.45Fig. 6.59 Window pop-up menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.46Fig. 6.60 Print to file: file selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.47Fig. 6.61 Print to file: file over-writing confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.47Fig. 6.62 Print to file: file example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.47Fig. 6.63 Print to file: file example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.47Fig. 6.64 History Report (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.49

Fig. 6.65 History Report: starting window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.50Fig. 6.66 History Report: selection of the output file (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.51Fig. 6.67 History Report: setting of date and time (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.51Fig. 6.68 History Report: confirmation of the file overwriting (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.51Fig. 6.69 History Report: invalid date and time (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.51Fig. 6.70 History Report: recording in progress (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.52Fig. 6.71 History Report: graphic symbol of the recording in progress (example). . . . . . . . . . . . . . . . . . . . . 6.52Fig. 6.72 History Report: event table (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.52Fig. 6.73 History Report: report file (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.53Fig. 6.74 History Report: report file not found (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.53Fig. 6.75 Local History Log (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.54Fig. 6.76 Local History Log: starting window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.54Fig. 6.77 Local History Log: transfer in progress (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.55Fig. 6.78 Local History Log: log displaying (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.55Fig. 6.79 Local History Log: log file (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.55Fig. 6.80 Commissioning Report (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.57Fig. 6.81 Commissioning Report: starting window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.58Fig. 6.82 Commissioning Report: selection of the output file (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.58Fig. 6.83 Commissioning Report: confirm for overwriting the file (example) . . . . . . . . . . . . . . . . . . . . . . . . . 6.58Fig. 6.84 Commissioning Report: NE unreachable via FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.59Fig. 6.85 Commissioning Report: transfer in progress (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.59Fig. 6.86 Commissioning Report: file with performance data not available (example) . . . . . . . . . . . . . . . . . 6.59Fig. 6.87 Commissioning Report: report loaded (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.59Fig. 6.88 Commissioning Report: report file (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.60Fig. 6.89 Alarm List (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.60

Fig. 6.90 Alarm List window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.61Fig. 6.91 Alarm List: tooltip window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.61Fig. 6.92 Alarm List: menu pop-up (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.62Fig. 6.93 Services (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.62Fig. 6.94 Services window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.63Fig. 6.95 Services window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.63Fig. 6.96 Create Service window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.64Fig. 6.97 Create Service window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.65Fig. 6.98 Create Service window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.66Fig. 6.99 Service table window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.66Fig. 6.100 Service table window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.66Fig. 6.101 Service table window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.67

Fig. 6.102 Enable Pseudo Wire push-button (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.67Fig. 6.103 Pseudo Wire window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.68



I-12LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

LIST OF THE FIGURES

Fig. 6.104 Empty value into a field in Pseudo Wire window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.70Fig. 6.105 Empty value into a field in Pseudo Wire window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.70Fig. 6.106 Out of range value into a field in Pseudo Wire window (example) . . . . . . . . . . . . . . . . . . . . . . . . 6.70Fig. 6.107 Pseudo Wire window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.71

Fig. 6.108 Create Service window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.71Fig. 6.109 New Service Level Agreement window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.72Fig. 6.110 Empty value into a Profile name field in New Service Level Agreemen window (example) . . . . . 6.73Fig. 6.111 Enable Advanced push-button (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.73Fig. 6.112 Advanced window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.74Fig. 6.113 Advanced window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.74Fig. 6.114 Empty value into a User-defined field in Advanced window (example) . . . . . . . . . . . . . . . . . . . . . 6.75Fig. 6.115 IP Mapping window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.75Fig. 6.116 Wrong ports selection in the Create Service window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . 6.76Fig. 6.117 Warning window in the Create Service window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.76Fig. 6.118 Service creation failed(example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.76Fig. 6.119 Delete services in the Service table window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.77

Fig. 6.120 Modify Service window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.77Fig. 6.121 Modify Administrative Status (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.78Fig. 6.122 Modify Administrative Status (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.78Fig. 6.123 Pseudowire details popup (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.79Fig. 6.124 Pseudowire details window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.79Fig. 6.125 Pseudowire details window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.80Fig. 6.126 Pseudowire details window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.81Fig. 6.127 Pseudowire details window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.81Fig. 6.128 New Pseudowire window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.82Fig. 6.129 Bundling details popup (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.83Fig. 6.130 Bundling details window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.83Fig. 6.131 Bundling details window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.84Fig. 6.132 Bundling details window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.84Fig. 6.133 New Bundling window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.84Fig. 6.134 Service Protection window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.85Fig. 6.135 Service Protection window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.85Fig. 6.136 Service Protection window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.86Fig. 6.137 Service Protection window - Error message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.86Fig. 6.138 Service Protection window - Error message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.87Fig. 6.139 Service Protection window - Error message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.87Fig. 6.140 Service Protection Details window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.87Fig. 6.141 Timeset: starting window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.89Fig. 6.142 Timeset: manual setting of date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.90Fig. 6.143 Timeset: confirmation for the new date and time of NE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.90Fig. 6.144 Copy NE: starting window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.92

Fig. 6.145 Copy NE: file selection (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.92Fig. 6.146 Copy NE: confirmation of the file overwriting (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.92Fig. 6.147 Copy NE: start of operation (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.93Fig. 6.148 Copy NE: operation running (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.93Fig. 6.149 Copy NE: operation ended (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.93Fig. 6.150 Paste NE: starting window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.94Fig. 6.151 Paste NE: file selection (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.94Fig. 6.152 Paste NE: operation start (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.94Fig. 6.153 Paste NE: operation in progress (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.95Fig. 6.154 Paste NE: operation ended (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.95Fig. 6.155 G.821/G.826 performance recording: configuration window (example) . . . . . . . . . . . . . . . . . . . . 6.98Fig. 6.156 G.821/G.826 performance recording: selection of output file (example) . . . . . . . . . . . . . . . . . . . . 6.98

Fig. 6.157 G.821/G.826 performance recording: date setting (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.98Fig. 6.158 G.821/G.826 performance recording: confirmation for file over-writing (example) . . . . . . . . . . . . 6.99




LIST OF THE FIGURES

Fig. 6.159 G.821/G.826 performance recording: incongruence between start date and time and end of recording(example)6.99

Fig. 6.160 G.821/G.826 performance recording: incongruence between current date and time and end ofrecording (example)6.99

Fig. 6.161 G.821/G.826 performance recording: operation waiting (example) . . . . . . . . . . . . . . . . . . . . . . . . 6.99Fig. 6.162 G.821/G.826 performance recording: operation on progress (example) . . . . . . . . . . . . . . . . . . . 6.100Fig. 6.163 G.821/G.826 performance recording: confirmation for operation stop (example) . . . . . . . . . . . . 6.100Fig. 6.164 G.821/G.826 performance recording: error window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . 6.100Fig. 6.165 G.821/G.826 performance recording: operation ended (example) . . . . . . . . . . . . . . . . . . . . . . . . 6.101Fig. 6.166 G.821/G.826 performance recording: data performance table (example) . . . . . . . . . . . . . . . . . . 6.101Fig. 6.167 G.821/G.826 performance recording: no performance data to read (example) . . . . . . . . . . . . . . 6.102Fig. 6.168 Inventory Report: starting window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.103Fig. 6.169 Inventory Report: file selection (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.103Fig. 6.170 Inventory Report: confirmation for file over-writing (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.103Fig. 6.171 Inventory Report: operation on progress (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.104Fig. 6.172 Inventory Report: operation ended (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.104

Fig. 6.173 Inventory Report: report file (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.105Fig. 6.174 Telemeasure: starting window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.107Fig. 6.175 Telemeasure: file selection (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.107Fig. 6.176 Telemeasure: setting of date and time (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.107Fig. 6.177 Telemeasure: confirmation for file overwriting (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.107Fig. 6.178 Telemeasure: start and stop date and time not congruent (example) . . . . . . . . . . . . . . . . . . . . . 6.107Fig. 6.179 Telemeasure: invalid stop date and time (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.108Fig. 6.180 Telemeasure: operation in progress (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.108Fig. 6.181 Telemeasure: confirmation for exit (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.108Fig. 6.182 Displaying of a measure in Chart modality (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.109Fig. 6.183 Chart modality: zoom of an area (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.109Fig. 6.184 Chart modality: pop-up menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.110Fig. 6.185 Chart modality: selection of the output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.111Fig. 6.186 Chart modality: printing properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.111Fig. 6.187 Chart modality: Zoom In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.112Fig. 6.188 Chart modality: Zoom Out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.112Fig. 6.189 Chart modality: Auto Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.112Fig. 6.190 Chart Properties table: tab Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.113Fig. 6.191 Tab Title: Font Selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.113Fig. 6.192 Tab Title: Title Color window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.114Fig. 6.193 Chart Properties window: Tab Plot - Domain Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.114Fig. 6.194 Chart Properties window: Tab Plot - Range Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.115Fig. 6.195 Tab Plot: Label - Font Selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.115Fig. 6.196 Tab Plot: Label Color window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.116Fig. 6.197 Tab Plot: Tick label font window - Font Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.116

Fig. 6.198 Chart Properties window: Tab Plot - Appearance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.117Fig. 6.199 Tab Appearance: Stroke Selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.117Fig. 6.200 Appearance tab: Outline Color window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.117Fig. 6.201 Appearance tab: Background Color window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.118Fig. 6.202 Chart Properties window: Other tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.118Fig. 6.203 Other tab: Background Color window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.119Fig. 6.204 Displaying of a measure in Data modality (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.119Fig. 6.205 Data modality: tooltip window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.120Fig. 6.206 Data modality: pop-up menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.120Fig. 6.207 Data modality: print properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.121Fig. 6.208 Data modality: selection of the output file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.121Fig. 6.209 FTP Client: Connect To Server window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.122

Fig. 6.210 FTP Client: connection refused . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.123Fig. 6.211 FTP Client: Software Download window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.123



I-14LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

LIST OF THE FIGURES

Fig. 6.212 FTP Client: pop-up menu (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.124Fig. 6.213 FTP Client: window for operation confirmation (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.124Fig. 6.214 FTP Client: file copy (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.124Fig. 6.215 Table in read only mode (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.125

Fig. 6.216 Table in “modify” mode (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.126Fig. 6.217 Add row (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.126Fig. 6.218 Table with row added (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.127Fig. 6.219 Table with deleted (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.127Fig. 6.220 Modify row (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.127Fig. 6.221 Table with row modified (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.128Fig. 6.222 “Frequency Setting” window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.128Fig. 6.223 “Date and Time” window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.129Fig. 7.1 Example of map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2Fig. 7.2 User interface of the NetBuilder program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4Fig. 7.3 Map Tree View frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6Fig. 7.4 Edit Map View frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.7

Fig. 7.5 NetBuilder: start shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.9Fig. 7.6 NetBuilder: starting window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.9Fig. 7.7 File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10Fig. 7.8 Open Map window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.11Fig. 7.9 Message for already loaded map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.11Fig. 7.10 Message of invalid map due to excessive number of NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.12Fig. 7.11 Message of map not loaded due to presence of Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.12Fig. 7.12 Saving confirmation window for the Close command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.12Fig. 7.13 Confirmation for the bitmap copy in the “Background” folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.13Fig. 7.14 Save As window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.14Fig. 7.15 Overwriting confirmation file map window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.14Fig. 7.16 New Discovery menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.14Fig. 7.17 New Discovery window (Standard Discovery). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.16Fig. 7.18 Message for missing map name (Standard Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.16Fig. 7.19 Message for map name already existing (Standard Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . 7.16Fig. 7.20 Message for missing search range (Standard Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.16Fig. 7.21 Message for invalid search range (Standard Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.16Fig. 7.22 Discovery in progress window (Standard Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.17Fig. 7.23 Message of none NE discovered (Standard Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.17Fig. 7.24 Example of NE icon adding (Standard Discovery). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.17Fig. 7.25 Example of NE icon displacement (Standard Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.18Fig. 7.26 Smart discovery of Flexipacket Stations (1+1 and 1+0 links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.20Fig. 7.27 Smart discovery of Flexipacket Stations (FPFM IDU-IDU link) . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.20Fig. 7.28 Smart discovery of Flexipacket Stations (1+0 links) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.20Fig. 7.29 New Discovery window (Smart Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.21

Fig. 7.30 Message for map name insertion not executed (Smart Discovery) . . . . . . . . . . . . . . . . . . . . . . . . 7.21Fig. 7.31 Message for map name already existing (Smart Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.21Fig. 7.32 Message for missing starting IP address (Smart Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.21Fig. 7.33 Message for invalid starting IP address (Smart Discovery). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.22Fig. 7.34 Discovery in progress window (Smart Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.22Fig. 7.35 Message of none NE discovered (Smart Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.22Fig. 7.36 Example of NE icon adding (Smart Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.22Fig. 7.37 Example of NE icon displacement (Smart Discovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.23Fig. 7.38 Confirmation window for the program exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.24Fig. 7.39 Confirmation window for the map saving at the program exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.24Fig. 7.40 Edit menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.24Fig. 7.41 Error window for object copying operation not allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.25

Fig. 7.42 Error window for pasting of NEs exceeding the allowed number . . . . . . . . . . . . . . . . . . . . . . . . . 7.25Fig. 7.43 New Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.25




LIST OF THE FIGURES

Fig. 7.44 NE insertion window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.26Fig. 7.45 Error window for max. limit of NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.26Fig. 7.46 Error window for NE name or/and network address not set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.28Fig. 7.47 Error window for NE name duplicated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.28

Fig. 7.48 Error window for NEs with different protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.28Fig. 7.49 Error window for NE name not compatible with the IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.28Fig. 7.50 Properties window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.28Fig. 7.51 Error window for duplicated NE address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.29Fig. 7.52 Error window for IP address of the NE not valid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.29Fig. 7.53 Background Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.30Fig. 7.54 Open window for the insertion of the background bitmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.30Fig. 7.55 Open window for the modification of the background bitmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.31Fig. 7.56 Background Properties window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.31Fig. 7.57 Options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.32Fig. 7.58 Discovery Options window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.33Fig. 7.59 Add Protocol window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.33

Fig. 7.60 Window Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.33Fig. 7.61 Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.34Fig. 7.62 About NetBuilder window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.35Fig. 7.63 Map pop-up menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.35Fig. 7.64 NE pop-up menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.36Fig. 7.65 Window of the NE properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.36Fig. 7.66 Confirmation window for NE deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.37



I-16LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

LIST OF THE FIGURES



LIST OF THE TABLES


LIST OF THE TABLES

Tab. 1.1 Features used by the specific plugin (FlexiPacket Microwave) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2Tab. 1.2 Features of the LCT software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6Tab. 2.1 Connection and management modalities of the radio from LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9Tab. 2.2 Characteristics of IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.15Tab. 2.3 Reserved and available Internet addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.17Tab. 6.1 Tool bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3Tab. 6.2 Map Tree View frame: objects icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7Tab. 6.3 Default configuration of the colors associated to the severity level . . . . . . . . . . . . . . . . . . . . . . . . 6.40Tab. 6.4 Default configuration of the error statuses of the fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.42Tab. 6.5 Operation symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.126Tab. 7.1 Tool bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5

Tab. 7.2 Map Tree View frame: objects icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6Tab. 7.3 Edit Map View frame: object icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.7

http://stile.pdf/

http://stile.pdf/



LIST OF THE TABLES

I-18LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011



1 - GENERAL INFORMATION

1-1LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011

1 GENERAL INFORMATION

1.1 Subject and Purpose of the Manual

This OMN Manual provides the information required for configuration and the

management of the local radio equipment and of the possible adjacent radio equipment

(e.g.: equipment of a radio link, equipment of a node) by means of the use of LCT

software.

LCT software consists of the following application programs:

– LCT: application that implements the GUI for management of the radio equipment.

– NetBuilder: graphic tool for the creation/change of the map to access the

equipment.

– LCTStart: application that automatically creates a map and allows opening directly

the GUI of LCT on the created map; the map is created when a NE is detected

locally connected to the LCT PC or when a search of NE is executed starting from

a NE with known IP address.

LCT can manage up to three NEs with TNMP protocol or up to 22 NEs with SNMP

protocol.

LCT supports the following NE management application protocols:

– TNMP protocol implemented on TCP/IP

– SNMP protocol implemented on UDP/IP.

For every kind of radio equipment, a specific plug-in is provided, providing to the LCT

application the support for the control and the configuration of the equipment.

A map of LCT cannot contain NEs with different protocols.

A map of LCT can contain two or more connected NEs (up to 22) with different

equiment types.

LCT allows inserting, into a map, NEs with TNMP EXT (extended TNMP) or SNMP

protocol.

However, in order to ensure the compatibility with maps created by means of old

versions of LCT, LCT allows opening and managing maps containing NEs with

TNMP base protocol or with automatic detection of the TNMP protocol (TNMP

Autodetect).

For the usage modes of the operating menu, implemented by the plug-in of every

equipment, refer to OMN Manual of the plug-in.




1-2LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

1.2 LCT Features

The present manual describes all the potentially available features in LCT Engine.

Anyway, only a subset of these features is actually used by FlexiPacket Microwave

plug-in.

In the following table (Tab. 1.1) each feature is briefly described and, next to each one,

there is the indication: "USED" or "NOT USED", in order to make the user aware of

which features are actually used by the specific plugin

Forwarding the contents of the subject Manual to third parties is forbidden

without a written authorization.

The Customer can require a copy of this manual referring out its code (present on

the cover rear-page).

Tab. 1.1 Features used by the specific plugin (FlexiPacket Microwave)

Engine General Functions

Software provided on CD-ROM USED

Software updating without data loss USED

Management of the different NE types through specific NE plugs-in USED

Configuration support at element level (EL) USED

Fault support at element level (EL) USED

Performance support at element level (EL) USED

Security support at element level (EL) USED

GUIJava GUI USED

Graphical display via maps of the node and/or radio link USED

Support of background images (files “.BMP”, “.GIF”, “.JPG“ ) for themaps

USED

NE icon, with:• indication of the NE name• NE type• signaling, through color, of the NE alarm summarized

status

USED

Display of the tree structure relevant to the map USED

Display of the tree structure relevant to the NE menu USED

NE opening through double click on the NE icon USED

Context sensitive Help on-line on LCT and on the NE plugs-in USED

Print to ASCII file of the window contents USED

Common Functions

Support of the element management (Element Manager) USED

Creation and configuration of the map through NetBuildergraphical tool

USED

Detection of the locally conected NE and automatic creation of the

map that contains the local NE and the possible “radio far-end”adjacent NEs NOT USED





Search of the NE starting from NE with known IP address andautomatic creation of the map that contains the found NE and the

possible “radio far-end” adjacent NEs

USED

Configuration of the NE properties, included the configuration ofthe network parameters

USED

Charts of the measurements executed on the NEs USED

Display in NetBuilder of the physical structure and of the treestructure of the map

USED

Drag/drop in NetBuilder of NEs USED

Auto-discovery of the NEs with insertion of the detected NEs into anew map

USED

Standard auto-discovery: automatic search of the NEs accordingto a specific range of IP addresses

USED

Smart autodiscovery: automatic search of the contiguous NEsstarting from the local NE or from a specific IP address

NOT USED

Support of auto-discovery for the NEs with the following protocols:• TNMP EXT on TCP/IP• SNMP on UDP/IP

NOT USEDUSED

Automatic solving of the host-names (the user must have pointedout both the name 2nd the network address of the NEs)

USED

Support of the synchronization via NE Manager (date and time ofthe NEs synchronized to the LCT PC date and time)

USED

Support of the SNTP synchronization USED

Enabling/disabling of the NE synchronization via NE Manager USED

Enabling/disabling of the NE USED

Support of the connection from LCT with priority respect to othersupervision systems

USED

Configuration Management:

Configuration of NEs through GUI USED

Copy/paste of the NE configuration USED

Management of the memory banks of NEs provided withembedded software/firmware

USED

Download, via FTP, of the NE software (embedded and/or

firmware)USED

ntegration of a FTP Client with customized interface for operationsof file transfer from/to NE (e.g.: NE software download)

USED

Management of the commissioning test NOT USED

Management of the inventory data of NE, with the possibility toinsert the user data

USED

Report of the NE inventory data USED

Configuration of NE date and time (meaningful only withsynchronization disabled)

USED

Configuration of the RF power and of the transceiving RF

frequencies

USED

Display of the software versions as of the engine as of the plugs-in USED





1-4LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Performance Management

Long period performances for commissioning test (performance

G.821/G.826 like, RSPI/RPPI, RPS) NOT USED

G.821/G.826 performances:Measure period: 15 minutes and 24 hoursAvailable G.821/G.826 measures:

• BBE• ES• SES• UAS• OI

NOT USED

RSPI/RPPI performance:Measure period: 15 minutes and 24 hoursAvailable RSPI/RPPI measures:

• RLTM• RLTS1, RLTS2, RLTS3, RLTS4• TLTM• TLTS1, TLTS2

USED

RPS performance:Measure period: 15 minutes and 24 hoursAvailable RPS measures:

• PSAC• PSAD• FSRC• FSRD

NOT USED

G.784 performance:Measure period: 15 minutes and 24 hoursAvailable G.784 measures:

• AU-4 PJE+• AU-4 PJE-

NOT USED

ACM performance:Measure period: 15 minutes and 24 hoursAvailable ACM measures:

• ACM Rx• ACM Tx

USED

Collection and report of the long period performance(commissioning Report), via XML file transferred via FTP

NOT USED

Recovery of the performance (referred both to quarters and to 24hours) to the connection of NE

USED

Commissioning Report (report of the long period performance) NOT USED

Recording to file of the NE G.821/G.826 performances referred tothe quarters of an hour

NOT USED

Measurements of RF RX power, with display of charts and tables USED

Fault Management and Alarms

Display of the NE alarm summarized status via different colors USED

Automatic refresh of the alarms of NE USED

Automatic notification of the alarm occurrence USED






Automatic notification of the change relevant to the alarmsummarized status for the NE

USED

Support of the severity management of the single alarms for theequipment

USED

Configuration of the alarm colors associated to the different alarmseverities

USED

Support of the following elements:• equipment alarms• external alarms• remote commands

USEDUSEDNOT USED

Possibility to assign identification names to the externalalarms/remote commands

NOT USED

Alarm List of NE USED

Information concerning the single alarms reported in Alarm List ofNE:

• alarm description• date and time of the alarm event• alarm severity

USED

Counters available in NE Alarm List:• total number of activate alarms• total number of activate alarms for each severity

USED

Recording to file of the NE events (History Report of NE) USED

Events reported in History Report of NE:• connection/disconnection and enabling/disabling events

• NE events• events of the NE configuration change

USED

Information concerning the single events reported in HistoryReport of NE:

• event description• date and time of the event

USED

Collection and log of the queue stored in a NE (Local History Log),by means of XML file transferred via FTP

NOT USED

Events reported in Local History Log of NE:• events of NE (except the reset of NE)• events of change of the NE configuration (except the

change of System Type)

NOT USED

Information on the single events reported in the Local History Logof NE:

• description of the event• date and time of the event

NOT USED

Supported severity levels:• Normal• Not on line• Critical• Major• Minor• Warning

• Indeterminate• Test

USED





1-6LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Tab. 1.2 lists the features of the LCT software.

Security Management:

Security at NE level USED

Enabling/Disabling of NE Security (function reserved to Adminuser class only)

NOT USED

Support of three user classes with different privileges for theSecurity and NE:

• Admin• Read Write• Read Only

USED

Access with Anonymous user class in case of disabled Security ofNE

NOT USED

Cryptic writing of the password USED

Enabling at NE level of the account log NOT USED

Logs and Lists:

All the log and list types support the function of print on file USED

History Report of NE USED

Local History Log of NE NOT USED

Alarm List of NE USED

Report of the inventory data USED

Report of the G.821/G.826 performances of NE referred to aquarter

NOT USED

Commissioning Report of NE NOT USED

LCT ↔ NE Interfaces:

TNMP EXT on TCP/IP NOT USED

SNMP on UDP/IP USED

Tab. 1.2 Features of the LCT software

Operating System: – Microsoft Windows Vista Business Edition orhigher

– Microsoft Windows XP Professional (ServicePack 2 or higher)

Supported Equipment: – FlexiPacket Microwave:• FlexiPacket Radio• FlexiPacket Hub






1.3 Delivery Conditions

The CD-ROM of the LCT delivery contains:

– LCT engine, including:

• LCT application

• LCTStart application

• NetBuilder tool

– Java Runtime Environment

– the software plug-ins of the supported radio equipment

– the drivers for the connection via cable for Microsoft Windows Vista/XP

– help on-line.

1.4 Licenses to Use the Software

LCT is a software product of Nokia Siemens Networks S.p.A. protected by Copyright ©

Nokia Siemens Networks S.p.A. 2009 and all the rights are reserved.

The licenses to use the LCT and the Third Party software products used in LCT and

included in the provision are reported in detail in Appendix A.

1.5 Related Manuals

Other information relevant to LCT are available also in the OMN Manuals of the

equipment plug-in; a Manual is foreseen for each plug-in, containing the information

necessary for the management, from LCT of the radio equipment.

All the Manuals are available in English; they can be also provided in other languages,

depending on the contract clauses.

LCT must not be installed on PCs where the NetViewer system is installed. The

NetViewer system implements also the LCT function.

The list of the NE plug-ins supported by LCT is reported in the Customer Release

Notes.




1-8LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

1.6 List of Abbreviations

A

ABR

Area Border Router

AC

Alternating Current

ACI

Access Integrator

ACSE

Association Control Service Element

A/D

Add/DropADM

Add/Drop Multiplexer

ADMIN

Administrator

AGC

Automatic Gain Control

AIS

Alarm Indication Signal

ALG

Application Level Gateways

ALM

Alarm

ALS

Automatic Laser Shutdown

ANSI

American National Standards Institute

AP

Alternate Pattern

APSAutomatic Protection Switch

AS

Autonomous System

ASBR

Autonomous System Border Route

ASU

Access Sub-Unit

AT

Asynchronous Transfer





ATM

Asynchronous Transfer Mode

ATPC

Automatic Transmission Power ControlAU

Administrative Unit

AU4

Administrative Unit 4

AUG-n

Administrative Unit Group n

AUI

Attachment Unit Interface

AUX

Auxiliary

B

BB

Base Band

BBC

Base Band Control

BBE

Background Block Errors

BBIU

Base Band Interface Unit

BDR

Backup Designated Router

BE

Best Effort

BER

Bit Error Ratio

BG

Border-Gateway

BMPBitmap

BPSK

Binary Phase Shift Keying

BR

Backbone Router

BS

Base Station

BS ID

Base Station Identifier




1-10LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

BSW

Bipolar Switch

BW

BandWidth

C

CC

Co-Channel

CDC

Carrier Detection Control

CDM

Cross Domain Manager

CH

Channel

CID

Connection Identifier

CLI

Command Language Interface

CLNP

ConnectionLess Network Protocol

CMD

Command

CMIS

Common Management Information Services

CMISE

Common Management Information Services Entity

CMX

PDH Cross-Connect Multiplexer

CON

Connected

CORBA

Common Object Request Broker Architecture

COSClass of Service

CP

Cyclic Prefix

CPE

Customer Premises Equipment

CPU

Central Processor Unit

CRC

Cyclic Redundancy Check





CRI

Critical

CS

Convergence Sub–layerCSESP

Consecutive Severely Errored Seconds Protection

CSMA/CD

Carrier Sense Multiple Access/Collision Detect

CSU

Control Switch Unit

CSW

Context Sensitive Windowing

CU

Connector Unit

D

DB

Database

DC

Direct Current

DCC

Data Communication Channel

DCD

Down Channel Descriptor

DCE

Data Communication Equipment

DCN

Data Communication Network

DCOM

Distributed Component Object Model

DDE

Dynamic Data Exchange

DECTDigital Enhanced Cordless Telecommunications

DEM

Demodulator

DR

Designated Router

DHCP

Dynamic Host Configuration Protocol

DIS

Disconnected




1-12LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

DL

Downlink

DNS

Domain Name ServerDSA

Dynamic Service Addition

DTE

Data Terminal Equipment

DTI

Double Tributary Interface

DTR

Data Terminal Ready

E E

Electrical

E1

2.048 Mbit/s Tributary (ETSI Standard)

E3

34.368 Mbit/s Tributary (ETSI Standard)

EC

Equipment Clock

ECC

Embedded Communication Channel

ECU

Embedded Channel Unit

EEPROM

Electrically Erasable Programmable Read Only Memory

EIA

Electronics Industry Association

EM

Element Manager

ENMSEdge Network Management System

EOW

Engineering Order-Wire

ES

End System / Errored Seconds

ETSI

European Telecommunications Standard Institute

EW

Early Warning





EXT

External

F

FD

Frequency Diversity

FDD

Frequency Division Duplexing

FEBE

Far End Block Error

FEC

Forward Error Correction

FEM

Functional Element Manager

FERF

Far End Receive Failure

FESP

Fifteen Minute Errored Seconds Performance

FIFO

First-In-First-Out

FO

Fully Outdoor

FPGA

Field Programmable Gate Array

FSK

Frequency Shift Keying

FSRC

Failed Switch Request Count

FSRD

Failed Switch Request Duration

FTP

File Transfer Protocol

G GMT

Greenwich Mean Time

GND

Ground

GNE

Gateway Network Element

GP

Group

GUIGraphical User Interface




1-14LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

H

HBER

High Bit Error Ratio

HD

High Density

HDB3

High Density Bipolar 3

HDLC

High Level Data Link Control

HEX

Hexadecimal

HF

Hetero FrequencyH-FDD

Half Duplex FDD

HK

HouseKeeping

HL

Hitless

H/S

Hot-Standby

HSBY

Hot-Standby

HTML

HyperText Markup Language

HTTP

HyperText Transmission Protocol

HW

Hardware

I

I/F

Interface

I/O

Input/Output

IANA

Internet Assigned Numbers Authority

I2C

Intel Integrated Circuit Bus

ID

Identifier

IDUIndoor Unit





IEEE

Institute of Electrical and Electronics Engineers

IF

Intermediate FrequencyI/F

Interface

IIS

Internet Information Server

IN

Input

IND

Indicative / Indeterminate

INT

Internal

I/O

Input/Output

IP

Internet Protocol

ISDN

Integrated Services Digital Network

ISO

International Organisation for Standardization

ITMNInstallation Test Manual

ITU

International Telecommunication Union

J

JRE

Java Runtime Environment

L

LAG

Link Aggregation Grouping

LAN

Local Area Network

LAPD

Link Access Protocol-D

LC

Line Clock

LCT

Local Craft Terminal

LEDLight Emitting Diode




1-16LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

LL

Leased Line

LLC

Logical Link ControlLOF

Loss of Frame

LOP

Loss of Pointer

LOS

Loss of Signal

LR

Layer Rate

LSA

Link State Advertisement

LSB

Least Significant Bit

M

MAC

Media Access Control

MAJ

Major

MAU

Media Adapter Unit

MCF

Message Communication Function

MDAC

Microsoft Data Access Components

MEM

Memorization

MIB

Management Information Base

MINMinor

MIS

Mismatch

MOD

Modulator

MRTR

Minimum Reserved Traffic Rate

MS

Master Station / Multiplex Section





MSOH

Multiplex Section OverHead

MSP

Multiplex Section ProtectionMSTR

Maximum Sustained Traffic Rate

MST

Multiplex Section Termination

MSTU

Main Signal Transmission Unit

MTNM

Multi Technology Network Management

MTU

Maximum Transmission Unit for Ethernet

N

NAPT

Network Address Port Translation

ND

Normal Density

NE

Network Element

NEG

NetViewer E-mail Generator

NIC

Network Interface Card

NLB

Network Load Balancing

NML

Network Management Layer

NMS

Network Management System

nrtPSNon Real-Time Polling Service

NSAP

Network Service Access Point

NT

Network

NTP

Network Time Protocol

NURG

Not Urgent




1-18LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

NV

NetViewer

NVCS

NetViewer Cluster Service

O

O

Optical

ODBC

Open DataBase Connectivity

ODU

Outdoor Unit

OEM

Original Equipment Manufacturer

OFDM

Orthogonal Frequency Division Multiplexing

OI

Outage Intensity

OL

Local Oscillator

OMN

Operating Manual

onL

On-Line

ONMS

Optimized Network Management System

OOB

Out Of Band

OS

Operating System

OSI

Open System Interconnection

OPSFOpen Shortest Path First

OUT

Output

OW

Overflow

P

PABX

Private Automatic Branch Exchange

PCPersonal Computer





PDH

Plesiochronous Digital Hierarchy

PDU

Packet Data UnitPHY

Physical

PID

Product Identification Data

PM

Performance Monitoring

PMP

Point-to-Multipoint Protocol

POE

External Operator Post

POL

Local Operator Post

POTS

Plain Old Telephone System (analogue telephony)

PPP

Point-to-Point Protocol

PS

Peripheral Station

PSACProtection Switch Actual Count

PSAD

Protection Switch Actual Duration

PSNT

Public Switched Telephone Network

PW

Power

PWR

Power

Q

QAM

Quadrature Amplitude Modulation

QOS

Quality of Service

QPSK

Quadrature Phase-Shift Keying

R

RRadio




1-20LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

R/O

Read Only

R/W

Read/WriteRAID

Redundant Array of Inexpensive Disk

RAM

Random Access Memory

RAS

Remote Access Service

RDI

Remote Defect Indication

Rep

Repeater

RF

Radio Frequency

RFC

Request for Comments

RFCOH

Radio Frequency Channel OverHead

RIEP

Recapitulary

RIPRouting Information Protocol

RL

Received Level

RLTM

Received Level Tide Mark

RLTS

Received Level Threshold Second

ROSE

Remote Operation Service Element

RPPI

Radio Plesiochronous Physical Interface

RPS

Radio Protection Switching

RPT

Repeater

RRAS

Routing and Remote Access Service

RS

Regenerator Section





RSOH

Regenerator Section OverHead

RSPI

Radio Synchronous Physical InterfaceRST

Regenerator Section Termination

RTM

Radio Transport Module

rtPS

Real-Time Polling Service

RUC

Radio Service Channel

RX

Reception / Receiver

S

ST

System Type

SB

SingleBoard

SCS

Switching Control Signal

SCSI

Small Computer System Interface

SCSU

Switching Control Supervision Unit

SD

Space Diversity

SDH

Synchronous Digital Hierarchy

SDU

Service Data Unit

SEEPSerial E2PROM

SES

Severely Errored Seconds

SF

Service Flow

SFID

Service Flow Identifier

SIU

Slide In Unit




1-22LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

SLA

Service Level Agreement

SLIP

Single Link Internet ProtocolSMA

Synchronous Multiplexer Add/Drop

SMS

Short Message Service

SMTP

Simple Mail Transfer Protocol

SMU

Sector Modem Unit

SNMP

Simple Network Management Protocol

SNTP

Simple Network Time Protocol

SOH

Section OverHead

SONET

Synchronous Optical Network

SPI

SDH Physical Interface / Serial Peripheral Interface

SPSSynchronous Protection Switching

SQL

Structured Query Language

SRA

Synchronous Radio Access

SRA L

System Radio Access at Low capacity

SRT

Synchronous Radio Trunk

SSBIT

Synchronous State Bit

SSH

Secure Shell

SSMB

Synchronous State Message Byte

SSU

Synchronous Source Unit

ST

Subscriber Terminal





STBY

Standby

STI

Single Tributary InterfaceSTM

Synchronous Transport Module

STM-1

Synchronous Transfer Module level 1

SU

Supervisory Unit

SVR

Software Version Release

SW

Software

T

T1

1.544 Tributary (ANSI Standard)

TC

Traffic Class

TCOA

TMF Corba Agent

TCM

Trellis Code Modulation

TCN

Threshold Crossing Notification

TCP

Transmission Control Protocol

TCU

Timing Control Unit

TDD

Time Division Duplexing

TESPTwenty four Hour Errored Seconds Performance

TF

Transmission Frequency

TFM

Tamed Frequency Modulation

TID

Target Identifier

TIM

Trail Identifier Mismatch




1-24LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

TL

Transmitted Level

TL1

Transaction Language 1TLTS

Transmitted Level Threshold Second

TMF

TeleManagement Forum

TMG

TeleMeasure Generator

TMN

Telecommunications Management Network

TNMP

Trivial Network Management Protocol / Telecommunications Network Management

Point

TNMS

Telecommunications Network Management System

TO

Transmission Opportunity

TOS

Type of Service

TP

Termination Point

TP4

Transport Protocol Class 4

TRIB

Tributary

TU

Tributary Unit

TX

Transmission / Transmitter

U

UAS

UnAvailability Seconds

UC

User Service Channel

UCD

Uplink Channel Descriptor

UDP

User Datagram Protocol

UMN

User Manual





UL

Uplink

URG

UrgentUSB

Universal Serial Bus

USW

Unipolar Switch

V

VC

Virtual Container

VCO

Voltage Controlled Oscillator

VLAN

Virtual Local Area Network

W

WAN

Wide Area Network

WAR

Warning

WINS

Windows Internet Name Service

WK

Working

WLBS

Windows Load Balancing Service

WS

Way-Side

WTR

Wait to Restore

X XHTML

Extensible HyperText Markup Language

XML

Extensible Markup Language

XPIC

Cross Polarization Interference Canceller




1-26LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011



2 - LCT FUNCTIONS AND FEATURES


2 LCT FUNCTIONS AND FEATURES

2.1 General

LCT provides the Element Manager function for the management of radio equipment.

The graphical interface for the access to the equipment is constituted by a map which

can be created manually by means of the NetBuilder tool or automatically by the

LCTStart application.

LCT supports the following management application protocols of NE:



LCT can manage maps containing, at most, three NEs with TNMP protocol or 22 NEs

with SNMP protocol.

LCT allows the execution of the following main functions:

– to open and to display the map for the connection to the NEs

– to set the connection with the NEs, activating it at the map opening

– to execute, by means of a cyclic polling, the monitoring of the connection and alarm

status of the NEs

– to access to the single NEs, that is to load the relevant configuration files and

operating menu

– to configure and to control each NE, through the relevant operating menu

– to manage the security access (Security) to the NEs, that is to allow the access

only to authorized users by means of password.

LCT does not know, a priori, nothing concerning the equipment to manage, but it

dynamically loads all the necessary information from the equipment plug-in.At the map opening, LCT automatically detects the type of the equipment, if the relevant

plug-in has been installed. If a radio equipment is present, whose relevant plug-in is not

installed, LCT detects its presence, but cannot recognize and manage it.

It is possible to execute the installation of an equipment plug-in also after the installation

of LCT; in this case, if LCT is already running, it is necessary to exit and then to restart,

so that the new plug-in is loaded.

A map of LCT cannot contain NEs with different protocols.




2-2LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

2.2 Fault Management

LCT manages the diagnostics of NE pointing out the occurrence of an alarm situation.

LCT supports the management of the alarm severity of NE.

The foreseen severity levels are the following ones:

– Normal: correct operating condition (on-line condition and alarm absence).

– Not On Line: disconnection condition.

– Critical: alarm condition that affects the operation and needs an immediate new

corrective action.

– Major: alarm condition that affects the operation and that needs an urgent new

corrective action.

– Minor: alarm condition that affects the operation and that needs a corrective action

to prevent heavier damages.

– Warning: potential alarm condition or potential service prevention, detected before

it can cause effects on the system; the user has to begin an action for an additional

diagnosis (if it is necessary) and to remove the trouble to prevent that it can cause

more serious fails.

– Indeterminate: alarm condition with indeterminate character that does not need

for the execution of diagnosis or of corrective actions.

– Test: test or manual forcing via software condition.

LCT uses different colors to graphically represent the severity level; a specific color,

which the user can modify as he wishes, is associated to each severity level.LCT provides the following information concerning the severity:

– Severity of each single alarm active on the NE.

– Summarized NE severity, that coincides with the alarm with highest severity

among the ones currently active on the NE.

Different visual signals are available to signal alarm conditions at different detail levels:

– Summarized severity of NE.

The modalities of displaying of the summarized severity of NE are the following:

• background color of the NE name on the NE icon in the map frame

• color of the square-shaped indicator before the NE name in the NE frame.

For the determination of the summarized severity of NE, also the disconnectionalarm is considered.

LCT allows inserting NEs with TNMP EXT (extended TNMP) or SNMP protocol into

a map.

In order to ensure the compatibility with maps created using old versions of LCT,

LCT allows however opening and managing maps containing NEs with TNMP

base protocol or with automatic detection of the TNMP protocol (TNMP

Autodetect).

The NE types that support the severity management are pointed out in the

Customer Release Notes.





– Unit alarm

Into the NE management windows, the alarmed unit is highlighted by means of a

colour changing.

– Alarm roots Into the NE management windows, the system points out all the possible alarm

roots, coupling to each root an identification label, which changes its colour if the

corresponding alarm condition is present.

– List of the active alarms

The list of the active alarms at level of a single NE is available; this functionality

includes also the list of the active external alarms.

In order to allow an analysis and an evaluation of the operation of the NEs during the

time, the following applications at level of single NE are available.

– History Report

The History Report application allows executing the recording on file of the events

(alarms, status changes, ...) relevant to the NE operation.

The report file lists all the events occurred on the NE in the period between the start

and the end of the recording.

The recordings are saved to file to allow possible post-processing; it is possible to

use any text editor to open a recording file and display the recorded events.

– Local History Log

The Local History Log application allows recovering and saving to file the log of the

events relevant to the recent history of the NE.

The Controller of a NE keeps in volatile memory the queue of the most recent

events occurred on the NE. The event queue has maximum size of 4000 events

and it is managed in cyclic modality; once reached the maximum size of 4000

events, the addition of a new event causes the deletion of the oldest event.

The event queue is deleted in the following cases:

• start-up of NE

• reset of NE

• change of the System Type of NE.

The transfer of the event queue from NE to LCT is made via FTP, using a

compressed XML file, that is created on-fly by the NE when the request from LCT

arrives.

The event for the change of the System Type is not available in the event queue,

as this event causes the deletion of the event queue.

The NE types that support the Local History Log functionality are pointed out in

the Customer Release Notes.




2-4LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

2.3 Configuration Management

LCT allows reading the current configuration of a NE and changing it.

The main features managed at NE level are the following ones:

– control of the operating status

– diagnostic management

– copy/paste of NE configuration

– configuration of the system and of the equipment

– configuration of the operating parameters

– configuration of the frequency plan

– configuration of the network parameters

– activation of the SNTP synchronization (if supported by NE) or of the

synchronization via NE Manager

– configuration of the date and of the time (it is meaningful only in case of

synchronization disabled)

– hardware/software forcing actions

– management of the tests (loop-back, commissioning test on link radio. ...)

– protection management

– reading of the inventory data, with the possibility to insert notes (e.g.: installation

date, repairing date, malfunctioning type, etc.) useful for the maintenance

operations; LCT allows the recording on log file of the inventory data at single NE

level

– management of the memory banks of NEs provided with software (embedded

and/or firmware) and software download via FTP Client, with customized interface,

embedded in LCT

– displaying of the software version of plug-in and of unit software.

Only for the Q-Adapter unit of the older TNMP/IP Dual Q-Adapter (unit provided

with embedded FTP Client), the software download can be executed via the FTP

Server application of the IIS service of Microsoft Windows.

FTP Client uses the FTP protocol to download/upload the files on NE.





2.4 Performance Management

LCT collects, displays and records, into a log file, the NE performances.

The user can directly require, poll and display the NE performance or run a performancelog for successive evaluations.

The performances can be exported in such a way to allow the processing and the

displaying by means of external tools.

Two intervals for the measurement of the performance are foreseen:

– interval of 15 minutes

– interval of 24 hours.

Both manual and scheduled activation of the NE performance logs is possible.

The following type of performances are available:

– G.821/G.826 performance

They are quality and availability parameters calculated according to the ITU-T

G.821/G.826 recommendation, which allow verifying the efficiency and the quality

of the radio transmission; the performance data are the following ones:

• UAS (Number of Seconds of Unavailability): it provides the unavailability

seconds of the connection into a specified observation period.

• SES (Number of Severely Errored Seconds): it represents the seconds during

which it is present one of the following conditions:

• percentage of errored blocks equal to or higher than 30%• presence of at least a special event called “defect”

• ES (Number of Errored Seconds): it represents the seconds during which it is

present at least one errored block.

• BBE (Number of Background Block Errors): it represents the number of

errored blocks into a not SES second.

• OI (Number of Outage Intensity): it is the number of unavailability events into

a defined observation interval.

– RSPI/RPPI Performance

They are parameters relevant to the RF RX and RF TX field, allowing estimates

and statistics on the RF transmission.

The seconds when the RF RX and RF TX power are under the preset thresholdvalues are counted.

It is possible to set more thresholds for the measurement of the RSPI/RPPI

performance (RLTS and TLTS threshold)

– RPS Performance

They are parameters relevant to the protection circuits, which allows estimates and

statistics on the errors and/or problems relevant to the radio transmission.

– G.784 PerformanceThey are parameters relevant the ADM functionality; the events of positive (AU-4

PJE+) and negative (AU-4 PJE-) justifying of the pointers of the SDH frames are

counted.

The recording to file is available only for the G.821/G.826 performances referred

to quarters.




2-6LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– ACM Performance

They are parameters relevant to the number of seconds spent by the equipment in

each modulation profile.

The measurement points are two: Rx side and Tx Side.

LCT implements also the functionality of recovery of the performances (both referred to

quarters and to day) stored in the NE; the recovery of the performances is made when

the login to NE is executed.

Also long period performances are available, which are generally enabled and collected

for maintenance purposes during the execution of commissioning tests.

The long period performances are made by a set of 192 consecutive quarter intervals of

performance monitoring (performance G.821/G.826 like, RSPI, RPS).

The measures of the long period performances are stored in the non volatile memory of

the Controller of the NE.

The long period performances are collected using a XML file, in compressed format,

which is transferred via FTP when required by LCT.

The XML file always contains a complete set of 192 consecutive intervals of 15 minutes.

The measurement points and parameters depend on System Type; the XML file

contains only the measurement points and parameters relevant to the specific System

type configured on the NE.

The measures of long period performances present, with respect to the normal

performance measurements, the following differences:

– they include 192 quarters intervals instead of 16 intervals

– they do not include the performances referred to the intervals of 24 hours

– they do not include the indication of the intervals with suspected measure intervals,

given that normally the measures are executed during the commissioning and then

all the intervals are considered as reliable

– they include the information on the status and the forcing of the switches used in

the commissioning tests, in such a way to consider an evaluation in

post-processing phase of the results of the commissioning test

– they do not include the measure points of the tributary side.

The Commissioning Report application allows displaying and saving to file the report of

the measures of the long period performances.

Moreover, LCT makes available a tool for the execution of the remote measurement on

some operating NE parameters (e.g.: RF RX power).

The GUI of LCT includes a Java application, able to display, in graphycal mode, the data

of the measures (par. 6.16.6).

Note that, as regards the performance measures:

– the G.826 performance measures are referred to digital paths with bit-rate

equal to or greater than 2 Mbit/s (reference is ITU-T G.826)

– the G.821 performance measures are referred to digital connections with

bit-rate equal to 64 kbit/s (reference is ITU-T G.821)

– the RSPI/RPPI terms refer to the performance measures relevant to the

physical radio interface (RSPI: Radio Synchronous Physical Interface; RPPI:

Radio Plesiochronous Physical Interface)

– the G.784 performance measures regards only the equipment with ADM

functionality.





2.5 Security of NE

The Security of NE allows the access to the NE only after the user authentication

through the insertion of the user class and the relevant password.

The user class defines the access prerogatives toward the NE (functioning monitoring,

setting/change of the operating parameters and/or of the network ones, etc.).

For the NE Security, three different user class are foreseen:

– Read Only: read only access to the functions

– Read Write: access to the functions both in read only and in writing modality,

except for the functions reserved to the Admin user class

– Admin: access all the functions both in read only and in writing modality.

The Security configuration (disabling status and password) is specific for each NE and

it is reported into NE.

It is possible to set/change, by means of the NE operating menu, the configuration of the

NE Security only if the user accesses to the NE with the Admin user class.

When accessing to a NE, the login phase is always executed, during which the system

asks to the user to specify the access user class.

In case of NE with disabled Security, it is possible to access to the NE also with the

Anonymous user class that does not require password and has the same privileges of

the Admin user class, except for the functionality of Security configuration. The Security

enabling prevents the contemporary connection to a NE of more operators with the

Admin or Read Write user class, preventing conflicts and configuration errors.

The performance functionalities supported by each type of NE are pointed out in

the Customer Release Notes.

For the NE Security, the default factory passwords are the following:

– Admin user class: sysmanager

– Read Write user class: readwrite

– Read Only user class: readonly.

For some equipment (e.g.: SRAL XD with SVR 3.8 or higher), the login password

of the Admin users of FTP and Telnet coincides with the password set for the

Admin user class of NE Security.The alignment of the passwords is ensured by an automatic mechanism: each

change to the password of the Admin user class of the NE Security is applied also

to the password of the Admin users of FTP and Telnet.

The Security of NE must be necessarily enabled if:

– more Managers can access at the same time (e.g.: two LCTs)

– the use of NetViewer is foreseen.

If the NE Security is disabled, or its next enabling, it will get again the previously

set passwords.




2-8LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

2.6 Supported Radio Equipment

The radio equipment of TNMP/IP class uses the proprietary management application

protocol TNMP implemented on the TCP/IP protocol (stack IP).

Each radio equipment of TNMP/IP class is provided with its own univocal IP address that

has to be assigned by the network administrator according to the requirements of the

company sub-networks. If the radio network is connected by means of gateway to the

Internet network, the IP addresses have to be assigned by the network administrator

following the indications of the charged international Department.

The FlexiPacketRadio is provided with the following channels for the transmission of thesupervisory data:

– Ethernet interface: the Ethernet traffic is a mix of Ethernet user frames, TDMoE

packet and management traffic

– R channel, reserved for the transmission via radio of the management traffic to the

next hop.

If the map contains both FlexiPacketRadio and FlexiPacketHub, the local connection of

LCT to these equipment is possible only via Ethernet interface, by means of an Ethernet

switch.

Direct connection from LCT to FlexiPacketRadio does nor require an Ethernet switch.

The NE Security of a SNMP equipment is always enabled and cannot be disabled.

SNMP equipment allow more than 1 manager to access in RW mode at the same

time.





2.7 LCT Usage Modalities

LCT can manage any radio equipment reachable via TNMP/IP or SNMP/IP protocol.

Typically, LCT is used:

– for the management a specific radio equipment (local or remote) and of the

possible adjacent radio equipment

– for the management of the equipment of a radio link.

With “adjacent equipment” we mean the equipment directly connected via a network

interface (radio, V-bus, Ethernet, ...) to the subject equipment.

In detail, we define “radio far-end” the adjacent radio equipment connected via a radio

interface. Generally, a radio link is made up by two radio equipment of two front-end

terminal stations; in case of add-drop configuration, there is the insertion of a repeater

between the two front-end stations and, then, the radio link is made up by three

equipment.If LCT is connected to the supervision network of a radio network, it is possible to

manage from LCT any radio equipment with TNMP/IP or SNMP/IP protocol of the

network (up to max. three NEs with TNMP protocol or max. 22 NEs with SNMP/IP

protocol); the radio equipment can be also not adjacent, but they must be visible in the

supervision network from LCT.

The gateway with the supervision network is made up by the radio equipment (GNE)

which LCT is connected to by means of F or Ethernet interface.

Tab. 2.1 reports the possible connection and management modalities for each type of

radio equipment supported by LCT.

Tab. 2.1 Connection and management modalities of the radio from LCT

Equipment

Connection

on F

interface

Connection

on Ethernet

interface

Local

equipment

management

Remote NE

management

Management

of radio link

Automatic

detection

of the local

equipment

Automatic

detection

of “radio

far-end”

NEs

FlexiPacketRadio

FlexiPacketHub




2-10LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

2.8 Connection with Priority from LCT

The possibility to connect from LCT with priority respect to other supervision systems

(e.g.: NetViewer) is foreseen. The connection with priority regards the possibility, for aLCT user, to connect with write permissions to a NE, which an user of another

supervision system (e.g.: NetViewer) is already connected to with write permission,

depriving this user of the writing permissions on NE. The connection with priority is

possible only with NEs for which the functionality is supported and enabled.

The connection with priority foresees a configurable timeout (inactivity interval), after

which the LCT connected with priority is automatically disconnected.

The timeout allows avoiding that a LCT remains connected with priority for long time to

the NE without reason (e.g.: due to oblivion) and that, as consequence, forbids the

connection to the NE with write permissions to other LCTs (which then could not use the

functionality of connection with priority) and/or other supervision systems.

2.9 File Transfer Protocol

LCT basically supports, as file transfer protocol with the NEs, the FTP protocol.

The applications of LCT that use the file transfer via FTP are the following:

– Commissioning Report: collection, via XML, of the long period performances; the

application requires the files directly to the NE

– Local History Log: collection, via XML, of the events relevant to the recent history

of NE; the application requires the files directly to the NE

– FTP Client: upload/download of files from/to the NE; the application receives

information via the FTP Server of the NE, which manages the file download/upload.

2.9.1 Configuration of FTP Server for FlexiPacket Hub

The file upload/download via FTP (from FlexiPacketHub to LCT and viceversa) requires

a proper configuration of an FTP Server on the machine where LCT is running.

The suggested FTP Server to be used is the one included in Windows XP, on the PC

where LCT is installed.

The configuration procedure of the FTP Server is the following:

The connection of LCT with priority can be applied only to the NE with equipment

SVR and plug-in version that implement the support of this functionality (refer to

the Customer Release Notes).

From LCT it is not possible to force the connection with priority to a NE, which

another LCT with write permission is already connected to.

The connection with priority to a NE is meaningful only in case of Security

enabled; therefore the connection with priority with Anonymous user class is not

a foreseen situation.

In case of Security disabled, it is necessary to avoid the situation of contemporaryconnection to a NE of more users with write permissions.





– Verify that, on the machine with LCT, the FTP service (FTP Publishing Service) is

installed and running. To open the services window (Fig. 2.1), select

Administrative Tools > Services in Control Panel.

Fig. 2.1 FTP Publishing Service

– If the FTP Publishing Service is not installed and running, please install and

activate it. There must be one and only one running FTP Server on the PC.

– Create on the FTP Server the user (with corresponding password) that will be used

by the specific plug-in. In case of FlexiPacketHub, please refer to the plug-in

manual for the details about user and password to be configured on FTPServer.

– Assign to the user both the read and the write permissions for the home directory

of Default FTP Site The procedure is the following:• Select Administrative Tools > Internet Information Services in Control

Panel.

• With the right button of the mouse, click Default FTP Site and, in the pop-up

menu that opens, select Properties (Fig. 2.2).

• Select the Home Directory tab (Fig. 2.3) and assign both the read and write

permissions for the home directory (select both the check-boxes Read and

Write of the FTP site directory section).




2-12LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 2.2 Configuration of the user permissions for FTP Default Site (1/2)

Fig. 2.3 Configuration of the user permissions for FTP Default Site (2/2)





2.10 NAPT functionality on F interface

Some equipment (e.g.: SRAL XD with SVR 3.8 or higher) support the NAPT functionality

on F interface, which allows deleting the limitation to reserve, for each installed NE, twoconsecutive IP addresses: one for the NE itself and one for F interface of the LCT

connection (NE automatically assigns to F interface an IP address equal to the one of

the NE plus one). User is allowed to enable/disable NAPT on NE.

If NAPT is supported and enabled, NE shall assign to LCT connecting via F interface an

available address belonging to the NE private network (i.e. 192.168.255.x, being

192.168.255.3 the private NE IP address on F interface).

NE and LCT communicate using only their private IP addresses, which are never

propagated in the public of management network.

Using NAPT functionality allows saving the IP address reserved for the connection of

LCT on F interface: the NE completely masks the private IP address assigned to LCT

on F interface, when LCT communicate with another NE of the “public” network.

2.11 Characteristics of TCP/IP Protocol

2.11.1 Address format for TCP/IP Protocol

2.11.1.1 Host and router

Network devices for the TCP/IP protocol are subdivided into:

– host: device with an application that answers to the TCP/IP protocol

– router (or gateway): device that manages routing information for various network

paths.

2.11.1.2 IP address classification

The TCP/IP networks use a 32-bit (4 bytes) address to identify the host, the sub-network

and the network which the host is connected to. The IP address is not limited to just

identifying a host as such, but it also identifies the connection of a host to the

sub-network and to the network. Therefore, if a device is moved to another sub-network

or network, its IP address must be changed accordingly. IP addresses are classified on

the basis of their format. Generally the following address Classes are used (Fig. 2.4):

– Class A

A Class A address has the following structure:

• the first bit of the first byte = 0

• the remaining seven bits of the first byte identify the network

• the last three bytes (24 bits) identify the sub-network+host field.

Class A addresses are used for networks with a large number of hosts. The

sub-network+host field is a 24-field and therefore 224 hosts can be detected.

The number of networks addressable by Class A addresses is limited.




2-14LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– Class B

A Class B address has the following structure:

• the first two bits of the first byte = 10

• the remaining six bits of the first byte plus the second byte (14 bits) identify

the network

• the last two bytes (16 bits) identify the sub-network+host field.

Class B addresses are most widely used because they allow a compromise

between the network number and the sub-network and host number.

– Class C

A Class C address has the following structure:

• the first three bits of the first byte = 110

• the remaining five bits of the first byte plus the second and the third bytes (21

bits) identify the network

• the last byte (8 bits) identify the sub-network+host field.

Class C addresses are used only for networks with a limited number of

sub-networks and hosts.

There are also Class D and Class E addresses, but their use is not provided for in LCT

software.

For example, in case of radio link, the host field identifies the radio equipment and the

sub-network field identifies the station.

The user can assign to the network field every value.

Fig. 2.4 Structure of IP addresses

For the radio link, it is advisable to use B class addresses.

The limit values of every field with all “0” and all “1” must not be used because

they are reserved address values (par. 2.11.1.5).

To minimize the possibility of wrong operating TCP/IP configurations or

configurations that could potentially work wrong, the LCT software foresees forthe IP addresses some unassignable values (par. 2.13).





2.11.1.3 Decimal notation of the IP address

The IP addresses are usually written in decimal notation, that is they are written by

means of the corresponding decimal value of each of the four bytes composing the IP

address.

For example, the following Class B IP address:

10000000 00000011 00001001 00000001

is written as:

128.3.9.1

and is translated into the network ID 128.3 and into the host ID (sub-network+host) 9.1.

In decimal notation, the value of the first byte allows the immediate identification of the

Class to which the address belongs:

– Class A address: initial value in the range 0 to 127

– Class B address: initial value in the range 128 to 191

– Class C address: initial value in the range 192 to 223.

Tab. 2.2 summarizes the main characteristics of several IP address classes.

* Some address values are reserved and cannot be used (par. 2.11.1.5).

2.11.1.4 Net-Mask

The last field of the IP address consists of two sub-fields: the first one identifies the

sub-network while the second one identifies the host.

In TCP/IP networks a mask, called Net-Mask, has to be specified for each IP address.

This mask is always composed of four bytes and it is subdivided into two parts (Net-Part

and Host-Part). It points out the configuration of the different fields of the IP address and

specifically the configuration of the sub-network+host field.

The number of bits for each sub-field is variable and can be different from address to

address. However the sum of the two sub-fields must be equal to the sub-network+host

field.

The Net-Mask allows correct understanding of the IP addresses because it shows how

many bits are used to address the sub-network and how many to address the host.

The method used to determine the Net-Mask consists of starting from the IP address

and encoding, into the Net-Part, the bits relating to the network with all "1" and, into the

Host-Part, the bits relating to the sub-network with all "1" and the bits relating to the host

with all "0".

Cross combinations of the bits relating to the sub-network and to the host (Host-Part)

are possible, but their use is not advisable because of the subsequent difficulty in

numbering and reading.Fig. 2.5 shows some Net-Mask examples for the Class B address:

Tab. 2.2 Characteristics of IP addresses

Class

Value of the

Address Space

of the First Byte

Max. Number

of Networks*

Max. Number

of Hosts*

IP Address

Space

A 0 - 127 126 16.777.124 net.host.host.host

B 128 - 191 16.384 65.534 net.net.host.host

C 192 - 223 2.097.152 254 net.net.net.host




2-16LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– 255.255.255.0 8 bits to address the sub-network, 8 bits to address the host

– 255.255.252.0 6 bits to address the sub-network, 10 bits to address the host

– 255.255.255.192 10 bits to address the sub-network, 6 bits to address the host.

In the Net-Mask, the bytes relevant to the network (Net-Part) are always equal to 255.

Fig. 2.5 Example of Net-Mask for Class B IP address

2.11.1.5 Reserved address values

The IP address can be coded by filling the different fields with a complete set of "1".

This coding operation defines a multiple transmission signal (broadcast):

– all "1" in the network field: transmission to all networks

– all "1" in the host+sub-network field: transmission to all hosts of the network

– all "1" in the host field: transmission to all hosts of the sub-network.

For example, the IP address = 128.2.255.255 identifies all hosts in the 128.2 network.

The IP address can also be encoded filling the various fields with a complete series of

"0", identifying in such a way the address as "this network", "this sub-network".

For example:

– the IP address = 128.2.0.0 identifies the current network, namely 128.2

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0

1 0 X X X X X X X X X X X X X X Y Y Y Y Y Y Y Y Z Z Z Z Z Z Z Z

Net-Mask = 255.255.255.0

Net-Mask

IP Address

NETWORK ID SUB-NETWORK ID HOST ID

NET-PART HOST-PART

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0

1 0 X X X X X X X X X X X X X X Y Y Y Y Y Y Z Z Z Z Z Z Z Z Z Z

Net-Mask = 255.255.252.0

Net-Mask

IP Address


NET-PART HOST-PART

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0

1 0 X X X X X X X X X X X X X X Y Y Y Y Y Y Y Y Y Y Z Z Z Z Z Z

Net-Mask = 255.255.255.192

Net-Mask

IP Address


NET-PART HOST-PART





– the IP address = 128.2.30.0 (with Net-Mask = 255.255.255.0) identifies the current

sub-network, namely 128.2.30.

The possibility of inserting all “0” in the network field is useful, for example, if a host does

not know its own IP address; in this case, the host will transmit an address with only "0"in the network field and the other hosts will read this address as the indication of the

subject network.

IP addresses corresponding to fields with all “1" or with "all 0" are therefore reserved

addresses.

Therefore the limit values of every field with all “0" and with all “1" must not be used as

network, sub-network and host addresses.

Tab. 2.3 shows which addresses are reserved and which addresses are available if the

TCP/IP network has been inserted into an Internet context.

2.11.2 TCP/IP protocol stack

The TCP/IP protocol is a layered protocol, consisting of:

– application layer

– transport layer

– network layer

– data connection and physical connection layer.

The TCP/IP protocol stack is shown in Fig. 2.6.Fig. 2.7 shows the TCP/IP protocol stack used in the connection between LCT and NEs.

Tab. 2.3 Reserved and available Internet addresses

Class Address/Range StatusA 0.0.0.0

1.0.0.0 - 126.0.0.0127.0.0.0

ReservedAvailableReserved

B 128.0.0.0128.1.0.0 - 191.254.0.0191.255.0.0


C 192.0.0.0192.0.1.0 - 223.255.254.0223.255.255.0


D, E 224.0.0.0 - 255.255.255.254

255.255.255.255

Reserved

Broadcast




2-18LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 2.6 TCP/IP protocol stack

Key:Name Standard Description• Telnet RFC 854 Application for network terminal emulation• FTP (File Transfer Protocol) RFC 959 Application for file transfer• BootP (Bootstrap Protocol) RFC 951 Application for bootstrap of diskless hosts• TFTP (Trivial File Transfer Protocol) RFC 783 Single file transfer• SNMP (Simple Network Man. Prot.) RFC 1157 Application for network management• UDP (User Datagram Protocol) RFC 768 Transport layer at datagram (not reliable)• TCP (Transmission Control Protocol) RFC 793 Connection oriented transport layer (reliable)• IP (Internet Protocol) RFC 791 Network layer (for routing)• ICMP (Internet Control Message Protocol) RFC 792•

RIP (Routing Information Protocol) RFC 1058 Protocol for routing table distribution• ARP (Address Resolution Protocol) RFC 826 IP/Ethernet addresses conversion protocol• MAC (Media Access Control) RFC 1042• LLC (Logical Link Control) RFC 1042• PPP (Point to Point Protocol) RFC 1171 Link connection oriented protocol• IPCP (Internet Protocol Conf. Prot.) RFC 1171 IP remote configuration protocol• LCP (Link Connection Protocol) RFC 1171• SLIP (Simple Link Internet Protocol) RFC 1055 Link not connection protocol





Fig. 2.7 TCP/IP protocol stack for LCT

Key:Name Standard Description • Telnet RFC 854 Application for network terminal emulation• FTP (File Transfer Protocol) RFC 959 Application for file transfer• UDP (User Datagram Protocol) RFC 768 Transport layer at datagram (not reliable)• TCP (Transmission Control Protocol) RFC 793 Connection oriented transport layer (reliable)• IP (Internet Protocol) RFC 791 Network layer (for routing)• ICMP (Internal Control Message Protocol) RFC 792• RIP (Routing Information Protocol) RFC 1058 Protocol for routing table distribution• ARP (Address Resolution Protocol) RFC 826 IP/Ethernet addresses conversion protocol• PPP (Point to Point Protocol) RFC 1171 Link connection oriented protocol

• IPCP (Internet Protocol Conf. Prot.) RFC 1171 IP remote configuration protocol• LCP (Link Connection Protocol) RFC 1171• SLIP (Simple Link Internet Protocol) RFC 1055R Link not connection protocol• TNMP Trivial Network Management Protocol (proprietary application protocol)




2-20LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

2.11.3 TCP/IP protocol of the LCT PC

For the connection to the NEs, the LCT PC must be provided with the TCP/IP protocol.

The TCP/IP protocol provided by the operating system (Microsoft Windows Vista/XP) on

serial RS-232C (PPP protocol) interface is used and/or on Ethernet interface. The

connection on serial interface needs for the installation of the direct connection mode

with a specific driver provided on CD-ROM.

The TCP/IP protocol provides the operator with some utilities for the control of the

connection between LCT and NE (par. 2.11.5).

2.11.4 Name solving

LCT identifies the NEs with an univocal IP address.

Names instead of the numeric IP addresses can be used.

LCT is able to solve the host-names relevant to all the NEs, present into the map, forwhich as the name as the IP address have been set.

On the contrary, the use into the map of the name only to identify a NE is possible only

if the operating system is able to execute the solving of the host-names (for instance,

through a DNS Server or through the system “hosts ” file).

In case of name solving through host table, the correspondence between the name and

the IP numeric address must be specified, for each radio equipment, in the “hosts ” file;

this file is contained in the “%SystemRoot%/System32/Drivers/Etc ” folder. To open and

edit the "hosts " file use an editor program. The file has to be saved in ASCII format

without any extensions so that Microsoft Windows can detect it as a system file.

2.11.5 Auxiliary utilities

The operator can use the software utilities of the TCP/IP protocol to check the features

of the connection between LCT and NE.

The TCP/IP protocol of the Microsoft Windows Vista/XP operating system makes the

following utilities available as Command Prompt commands:

– Ping

It is possible to send a ping command towards a host in order to verify if the TCP/IP

stack of the addressed host is visible and to measure the transmission time in the

go and return direction.

– NetStat

This is a typical Microsoft Windows utility which allows to call statistics all active

TCP/IP connections.

– TraceRT

It is possible to send a TraceRT command towards a host in order to verify if the

path to reach the addressed host is the intended path and is free from failures

and/or conflicts.

– Route

It allows managing the local TCP/IP routing table (route). In particular, the "PRINT"option allows the displaying of the entire routing table.

For the creation/change of the host table in Microsoft Windows Vista/XP, the

operator must have the administrator access rights for Microsoft WindowsVista/XP.





– Ipconfig

It allows checking the configuration of the PC interfaces that use the TCP/IP

protocol.

The TelNet utility with graphical mode is available in Microsoft Windows. Such a utilityallows opening a virtual terminal in the TCP/IP stack of the specified host.

2.12 Validity Conditions of TCP/IP Parameters

2.12.1 Overview

The network parameters that can be configured via software are the following ones:

– IP address of the NE and relevant Net-Mask

– static routing table

– connection parameters between NE and PC in case of connection via F interface.

The setting of each network parameter is bound to the respect of certain validity and

invalidity conditions, based on the RFC standard and on the particular network and on

the particular structure of the network and routing interface of NE. The validity and not

validity condition for the IP addresses and the Net-Masks contents also the

combinations between the two parameters. In fact some values, valid if considered

alone, can define, if combined together, some invalid sub-network or host values. For

some parameters, the setting of an invalid value is not accepted by the software

(signalling on video of “out of range”). Then a reset mode of the TCP/IP parameters is

provided. A wrong setting of the network parameter can cause an error of LCT PC - NEconnection and/or determine routing problems in the propagation of the supervision

information in the radio network (e.g.: it can make a specific NE unreachable).

2.12.2 Validity conditions for IP addresses and Net-Mask

2.12.2.1 IP addresses

– Only the IP addresses belonging to Class A, B and C are valid.

– The IP addresses = 127.X.X.X are not valid because they are reserved for

loop-back.– The IP address = 255.255.255.255 is not valid because it is reserved for "limited

broadcast".

– The IP address = 0.0.0.0 is a particular case of the NE because it is reserved for

the reset of the TCP/IP parameters (refer to par. 2.12.5).

– For each Class, the IP addresses having the following characteristics are not valid:

• all "1" in the network field

• all "0" in the network field

• all "1" in the host+sub-network field

• all "0" in the host+sub-network field

in fact these IP addresses are reserved (e.g. the IP addresses with all "1" are

reserved for broadcast).




2-22LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– For each Class, the IP address having the host field such to assign, to the F

interface for the local connection of the PC, an IP address equal to the broadcast

for that network is not valid.

Here below, there are the validity ranges for the IP addresses with Class A, B and C.

Class A

Addressing range: from 0.0.0.0 up to 127.255.255.255

Valid IP address: from 1.0.0.1 up to 126.255.255.253

Valid values:

– Network field (first byte): from 1 up to 126

• value 0: not valid because it is a field with all "0"

• value 127: not valid because it is a field with all "1" and also because the IP

addresses = IP 127.Y.Y.Y are reserved for loop-back

– Sub-network + host field (last three bytes): from "0.0.1" up to "255.255.253"

• value 0.0.0: not valid because it is a field with all "0"

• value 255.255.255: not valid because it is a field with all "1" (reserved for

broadcast)

• value 255.255.254: not valid because it causes the assignment, to the F

interface of local connection to the PC, of an IP address equal to the

broadcast for that network (X.255.255.255).

Class B

Addressing range: form 128.0.0.0 up to 191.255.255.255


Valid values:

– Network field (first two bytes): from 128.1 up to 191.254

• value 128.0: not valid because it is a field with all "0"

• value 191.255: not valid because it is a field with all "1"

– Sub-network + host field (last two bytes): from "0.1" up to "255.255.253"• value 0.0: not valid because it is a field with all "0"

In case of NAPT not supported or disabled, on a radio NE, the IP address of the Finterface for the local connection of the PC is automatically assigned increasing

of 1 the IP address of the radio NE itself.

In case of NAPT supported and enabled, a radio NE assigns to LCT connecting via

F interface an available address belonging to the NE private network (i.e.

192.168.255.x, being 192.168.255.3 the private NE IP address).

0 X X X X X X X Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y

Class A identification bit

NETWORK ID SUB-NETWORK+HOST ID

1 0 X X X X X X X X X X X X X X Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y

Class B identification bit






• value 255.255: not valid because it is a field with all "1" (reserved for

broadcast)

• value 255.254: not valid because it causes the assignment, to the F interface

of local connection to the PC, of an IP address equal to the broadcast for that

network (X.X.255.255).

Class C

Addressing range: from 192.0.0.0 up to 223.255.255.255


Valid values:– Network field (first three bytes): from 192.0.1 up to 223.255.254



– Sub-network + host field (last byte): from 1 up to 253

• value 0: not valid because it is a field with all "0"

• value 255: not valid because it is a field with all "1" (reserved for broadcast)

• value 254: not valid because it causes the assignment, to the F interface of

local connection to the PC, of an IP address equal to the broadcast for that

network (X.X.X.255).

2.12.2.2 Net-Mask

– For each Class, only the Net-Masks having all "1" into the Net-Part are valid:

• Class A: the Net-Mask different from 255.Y.Y.Y are not valid

• Class B: the Net-Masks different from 255.255.Y.Y are not valid

• Class C: the Net-Mask different from 255.255.255.Y are not valid

1 1 0 X X X X X X X X X X X X X X X X X X X X X Y Y Y Y Y Y Y Y

Class C identification bit


1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y

Net-Part

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y

Net-Part

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y

Net-Part




2-24LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– For each Class, only the Net-Masks having contiguous "1" are valid.

Examples of not valid Net-Masks having not contiguous "1":

– For each class, only the Net-Masks, assigning two bits for the sub-network field

and for the host one, are valid.

Not valid Net-Mask with only one bit for the sub-network field:

Not valid Net-Mask for each class with only one bit for the host field.

1 1 1 1 1 1 1 1 1 1 1 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Not contiguity

Class A: 255.239.0.0

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1 0 0 0 0 0 0 0 0

Not contiguity

Class B: 255.255.251.0

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1 1 1 0 0

Not contiguity

Class C: 255.255.255.188

1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Class A: 255.128.0.0

Net-Part Host-Part

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Class B: 255.255.128.0

Host-PartNet-Part

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0

Class C: 255.255.255.128

Host-Part Net-Part

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0

Class A, B, C: 255.255.255.254





2.12.2.3 IP address - Net-Mask combinations

For each Class, the IP address and Net-Mask combinations causing one of the following

situations in the IP address are not valid:

– all "0" in the sub-network field

– all "0" in the host field

– all "1" in the host field (broadcast for that network)

– host field such as to assign, to the F interface of local connection to the PC, of an

IP address equal to the broadcast for that sub-network.

Here below there are some examples of invalid combinations for the Class A.

– Combination of IP address = 97.11.48.159 and Net-Mask = 255.255.255.224

Applying the mask, the host field with all "1" (broadcast for that sub-network) isobtained.


Applying the mask, a sub-network field with all "0" is obtained.

0 1 1 0 0 0 0 1 0 0 0 0 1 0 1 1 0 0 1 1 0 0 0 0 1 0 0 1 1 1 1 1


NETW. ID SUB-NETWORK ID

IP address = 97.11.48.159

HOST ID

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0

Net-Part

Net-Mask = 255.255.255.224

Host-Part

0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1



IP address = 1.0.0.1

HOST ID

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Net-Part

Net-Mask = 255.255.0.0

Host-Part




2-26LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


Applying the mask, a host field with all "0" is obtained.

– Combination of IP address IP = 1.0.128.62 and Net-Mask = 255.255.255.192

Applying the mask, a host field (111110) is obtained such as to assign, to the F

interface of local connection of the PC, an IP address equal to the broadcast for

that sub-network (all "1" in the host field).

2.12.3 Validity conditions for parameters of the static routingtable

Here below, the list of the validity/invalidity conditions for each parameter of the static

routing table is reported.Remember that it is not possible to execute permanent settings for the static routing

table until the IP address of the radio NE has not been assigned.

– Routing interface

The setting of the interface which the routing is defined to does not create special

troubles because only the values present in the list displayed on the video can be

selected.

– IP address of the destination network

• Only the IP addresses belonging to Class A, B and C are valid

• For each Class, the IP addresses, having all "0" or all "1" into the network

field, are not valid

• For each class, the IP addresses equal to the following ones are not valid:– default IP address of the PC

0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0



IP address = 1.0.0.4

HOSTID

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0

Net-Part

Net-Mask = 255.255.255.252

Host-Part

0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 1 1 1 1 0



IP address = 1.0.128.62

HOST ID

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0

Net-Part

Net-Mask = 255.255.255.192

Host-Part





– default IP address of the NE

– current IP address of the NE

– IP address of the local sub-network

– IP address for broadcast of the local sub-network.

– IP address of the gateway

• The same validity conditions of the NE IP addresses are valid (par. 2.12.2)

• For each Class, the current IP address of the NE is not valid.

2.12.4 Validity conditions for the F interface parameters (PC)

The setting of the F interface parameters (link and baud-rate protocol) does not create

special troubles because it is possible to select only the values present into the list

displayed on the video.

Check that the used hardware (PC and, in case of remote connection, modem) supports

the executed settings.

2.12.5 Reset of the TCP/IP parameters

It is possible to execute the reset of the TCP/IP parameters assigning, to the radio NE,

the IP address = 0.0.0.0.

This operation causes the deleting as of the IP address and of the relevant Net-Mask as

the settings into the static routing table.

On the contrary, the protocol and the baud-rate relevant to the F interface remains the

current ones.

Then the reset of the TCP/IP parameters is automatically executed when the following

conditions are present:

– when it is changed the IP address of the NE

– when during the start-up phase, the system detects some IP address and

Net-Mask values or combinations not valid.

2.13 Software Architecture

The architecture of the LCT software is modular and foresees the following elements

(Fig. 2.8):

– Local Craft Terminal application program.

It implements the LCT engine and the graphical interface (GUI) through which the

operator manages the radio equipment.

– LCTStart application

Application that allows automatizing and speeding up the access to the NEs

through:

• the automatic creation of a map when a NE locally connected to the LCT PC

is detected or when a search of NE is executed starting from a NE with known

IP address

• the direct opening of the GUI of LCT on the created map.




2-28LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– NetBuilder application program

It is a graphical tool that allows creating/changing the link map and/or the local map

that constitutes the graphical interface.

– NE plugs-in The NE plugs-in implement in LCT the Element Manager function for the several

types of equipment. LCT is able to detect and, then, to manage only the NE types

whose plug-in is installed.

The plugs-in are additional parts of the engine that can be always installed, even

after the engine installation.

Fig. 2.8 LCT software elements

The modular architecture of the software provides the following advantages:

– the possibility to add always, to the engine, the support of a NE type by means of

the installation of the relevant plug-in

– the possibility to release later and/or at different times some plugs-in for the support

of new NEs, without needing to update the engine version but ensuring thecompatibility between engine and plug-in only

– the possibility to update the engine version without having to install again the

plugs-in and the additional modules.

2.14 Local Equipment Management

2.14.1 “LCT - local equipment” connection

The connection between LCT PC and local equipment is realized through serialRS-232C interface (F interface) or Ethernet interface (if supported by the radio

equipment).

Each radio equipment is provided with a pre-configured private IP address.

In case of direct connection on F interface, it is necessary to use a proper

pin-to-pin non modem cable; in case of direct connection on Ethernet interface, it

is necessary to use a crossed Ethernet network cable.

NETBUILDER

ENGINE + GUINE

PLUG-IN

LCTSTART





Fig. 2.9 displays only the connection scheme between LCT PC and local equipment.

Fig. 2.9 Connection between LCT PC and local radio equipment

Connection on F interface

Connection on Ethernet interface

From LCT (Fig. 2.10) it is possible to manage more radio nodes (up to three NEs with

TNMP protocol and up to 22 NEs with SNMP protocol) of a same radio station, if

interconnected by a network interface (Ethernet, V-bus, ...).

For all the radio equipment, the private IP address assigned by default in factory

to the F interface is 192.168.255.3 (Net-mask 255.255.255.0).

The private IP address assigned by default in factory to the Ethernet network

interface (is available) of a radio equipment depends on the type of radioequipment (e.g.: for FlexiMetro is 192.168.255.3, for SRAL XD is 10.10.10.10).

Use the private IP address of the radio equipment only in case of univocal

connection from LCT to the local radio equipment (e.g.: direct connection

between LCT and local radio equipment). In all other cases (e.g.: connection from

LCT to more radio nodes of the same station interconnected by a network

interface, connection of LCT to the corporate LAN, ...). In order to ensure the

reachability of a radio equipment, its public IP address must be used.

RADIO EQUIPMENT

DCE DTE

LCT PC

F INT.(RS-232C)

WST

WSTLCTQ - L AN E - L IN K

ALARMS

MCT

MS

D’T

E/

WJ

N/

SYSTEM

I

MEMORY

SRA4

K EY P WR

O

V 1 1 G 7 0 3IN

V 1 1 G 7 0 3IN

STM 2

STM 2OUT

STM 1OUTIN IN

CH.B

CH.BCH.A

OUTSTM 1

OUTIN

CH.A

IN

O UT D AT AE XP .

OUT

ALMCABLE

ALMODU

CABLE ALM

DATAEXP.

ALMODU

CABLE

ICO-CH

D’

PS

O

ODUPWR

I

ODUPWROUTIN

D’

OUT

CO-CH

IN

IF

OPS

CABLEIF

ETHERNET

LCT PC

RADIO EQUIPMENT

WST

WSTLCTQ-LAN E-LINK

ALARMS

MCT

MS

D'T

E/

WJ

N/

SYSTEM

I

MEMORY

SRA4

K E Y P WR

O

V 11 G 7 03IN

V 11 G 7 03IN

STM2

STM2OUT

STM 1OUTIN IN

CH.B

CH.BCH.A

OUTSTM 1

OUTIN

CH.A

IN

O UT D ATA EX P.

OUT

ALMCABLE

ALMODU

CABLE ALM

DATAEXP.

ALMODU

CABLE

ICO-CH

D'

PS

O

ODUPWR

I

ODUPWROUTIN

D'

OUT

CO-CH

IN

IF

OPS

CABLEIF




2-30LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 2.10 Connection between LCT PC and radio nodes of the same radio station

Connection of radio nodes on Ethernet interface

Connection of radio nodes on V-bus

FlexiPacketRadio is provided with only one Giga Ethernet port, used both for the

management traffic and the payload traffic (Ethernet user frames and TDMOE packets).

To avoid the possible loss of traffic payload, use an Ethernet switch for the local

connection of LCT to FlexiPacketRadio (Fig. 2.11).

Fig. 2.11 Connection between LCT PC and local FlexiPacketRadio

LAN - ETHERNET

LCT PC

RADIO

NODE

WST

WSTLCT

Q - L A N E - L I N K

ALARMS

MCT

MS

D'T

E

/

WJ

N/

SYSTEM

I

MEMORY

SRA4

K EY P WR

O

V 1 1 G 7 0 3

IN

V 1 1 G 7 0 3IN

STM2

STM2

OUT

STM1

OUTIN IN

CH.B

CH.BCH.A

OUTSTM1

OUTIN

CH.A

IN

O UT D AT AE XP .

OUT

ALMCABLE

ALMODU

CABLE

ALM

DATAEXP.

ALM

ODU

CABLE

ICO-CH

D'

PS

O

ODUPWR

I

ODUPWROUTIN

D'

OUT

CO-CH

IN

IF

O

PS

CABLE

IF

WST

WSTLCT


ALARMS

MCT

MS

D'T

E

/

WJ

N/

SYSTEM

I

MEMORY

SRA4

K EY P WR

O

V 1 1 G 7 0 3

IN

V 1 1 G 7 0 3IN

STM2

STM2

OUT

STM 1

OUTIN IN

CH.B

CH.BCH.A

OUTSTM 1

OUTIN

CH.A

IN

O UT D AT AE XP .

OUT

ALMCABLE

ALMODU

CABLE

ALM

DATAEXP.

ALM

ODU

CABLE

ICO-CH

D'

PS

O

ODUPWR

I

ODUPWROUTIN

D'

OUT

CO-CH

IN

IF

O

PS

CABLE

IF

WST

WSTLCT


ALARMS

MCT

MS

D'T

E

/

WJ

N/

SYSTEM

I

MEMORY

SRA4

K E Y P W R

O

V 1 1 G 7 0 3

IN

V 1 1 G 7 0 3IN

STM 2

STM 2

OUT

STM1

OUTIN IN

CH.B

CH.BCH.A

OUTSTM1

OUTIN

CH.A

IN

O UT D AT AE XP .

OUT

ALMCABLE

ALMODU

CABLE

ALM

DATAEXP.

ALM

ODU

CABLE

ICO-CH

D'

PS

O

ODUPWR

I

ODUPWROUTIN

D'

OUT

CO-CH

IN

IF

O

PS

CABLE

IF

RADIO

NODE

RADIO

NODE

V-BUS

DUALQ-ADAPTER

(RS-485)

NODE RADIO

NODE RADIO

NODE RADIOETHERNET

LCT PC

LCT PC

PAYLOAD

TRAFFIC

FLEXIPACKETRADIO

SWITCH

Ethernet





2.14.2 Local map

The local map constitutes the graphical interface necessary for connection from LCT to

the local equipment. The map can be manually created with the NetBuilder tool or

automatically created by the LCTStart application.

LCT is provided with the standard maps of connection to the local equipment

(“LOCALNE.map ” and “LOCALNE_SNMP.map ”).

For the use of the NetBuilder program, refer to the Chp. 7 – "OPERATING GUIDE OF

NETBUILDER".

For the operating modality of the LCTStart application, refer to Chp. 6.9.1 – "LCTStart

application".

2.14.3 Testing of the connection

One configured the connection between LCT and local equipment (dial-up connection

on F interface or network connection on Ethernet interface), the operator has to test it,by means of the software utilities of the TCP/IP protocol. This test has the aim to check

that:

– there are not conflicts on the dial-up connection

– the equipment can be reached and it answers correctly to the connection request

– there are not routing errors if, on the LCT PC, the TCP/IP protocol is used on more

interfaces (for instance: serial interface an Ethernet interface).

For the use of the software utilities, refer to the Manual of the operating system.

The main troubles that can be detected during the connection between LCT PC and

radio equipment are the following ones:

– Impossibility to contact the equipment through the TCP/IP protocol

Check the correct configuration of the LCT PC.

Check that the equipment is turned on and that the reset operation is ended. Check

the PC - equipment serial connection cable.

– Loading of the local map, the NE is disconnected

Close the Local Craft Terminal program and check that the TCP/IP protocol has

been correctly activated.

– “hosts ” file: after having updated the “hosts ” file, on the map the NE remains

disconnected

The operating system reads the “hosts ” file at starting-up only. Therefore, to let

every possible change on such a file becoming effective, it is necessary to restartWindows and the Local Craft Terminal program.

By default, the standard map “LOCALNE.map ” contains one NE with the following

configuration:

– protocol: TNMP EXT

– IP address: 192.168.255.3

By default, the standard map “LOCALNE_SNMP.map ” contains one NE with the

following configuration:

– protocol: SNMP

– IP address: 192.168.255.3The IP address 192.168.255.3 is the preset address (10.10.10.10, for SRAL XD ).




2-32LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

2.15 Radio Link Management

2.15.1 LCT - radio link “connection”It is possible to manage the equipment of a radio link via LCT.

Usually, a radio link is composed by two NEs of two front-end stations: local terminal and

remote terminal (Fig. 2.12).

The radio link can be composed by three NEs if between the two local and remote

terminals it is present a repeater (Fig. 2.13).

The connection between LCT PC and local radio equipment, that acts as gateway, is

realized through serial RS-232C interface (F interface) or Ethernet interface (if

supported by the radio equipment).

Fig. 2.12 Radio link structure


In case of SRA L and SRAL XD, it is possible to realize a radio link with three NEs,

because it is foreseen the following System Type: Repeater with Add/Drop of the

tributaries.

LCT supports only the management of the local equipment for the radioequipment of OSI class.

In case of direct connection on F interface, it is necessary to use a proper

pin-to-pin non modem cable; in case of direct connection on Ethernet interface, it

is necessary to use an crossed Ethernet network cable.

In a radio link, in order to ensure the reachability of every equipment from LCT,the public IP addresses of the radio equipment must be used.

NENE

F INT. (PIN-TO-PIN NOT MODEM CABLE)

LCT PC

COM1/COM2

Station 1 Station 2

Terminal A Terminal B

Radio Link






Fig. 2.13 Radio link structure with repeater


ETHERNET

LCT PC

NENE

Station 1 Station 2

Terminal A Terminal B

Radio Link

NE

F INT. (PIN-TO-PIN NOT MODEM CABLE)

LCT PC

COM1/COM2

NE NE

Station 1 Station 2 Station 3

Radio Link Radio LinkTerminal A Repeater Terminal B




2-34LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


2.15.2 Routing functions of the NEs

Each radio equipment is a device with dual function: the host and the router, because it

can identify the destination (itself, another radio equipment, a router, a PC) on the basis

of the IP address and consequently to route the message towards the proper path.

Each radio equipment has a pre-configured local IP address which allows a localconnection through which the operator may assign the IP address to the equipment.

2.15.3 Routing tables

In a TCP/IP network, each element with router function manages the routing according

to routing tables which specify the parameters for every possible route. The routing

tables can be of two different types:

– Static routing tables: fixed tables defined by the network administrator. In case of

network expansion or change they have to be updated.

– Dynamic routing tables: these tables are generated by the different network

elements with router function on the basis of the information acquired by the

network. In case of network expansion or change, these tables are automatically

updated by means of a routing protocol.

For this purpose, the radio equipment support the RIP protocol version 1. Consequently,

every radio equipment is able, depending on information acquired from the link, to obtain

a complete overview of the link structure. Dynamic routing tables are created

automatically, enabling the radio equipment to define a routing over the most suitable

path.

In the presence of expansion, change or failure/interruption of the radio link, each radio

equipment automatically updates the corresponding dynamic routing tables, thus

adapting the tables to the new radio link structure.

ETHERNET

LCT PC

NE NE NE

Station 1 Station 2 Station 3

Radio Link Radio Link

Terminal A Repeater Terminal B





Static routing tables are required if routers not supporting the RIP protocol are used

inside the radio link. A specific static routing table can be created on a NE to exit from

the radio link, which via the RIP protocol is recognized by other NEs as the default exit

of the radio link.

2.15.4 Hosts table

The creation and the use of a hosts table on the service PC allows using the names

instead of the numeric IP addresses to identify the NEs. In the hosts table, the

correspondence between names and numeric IP addresses must be specified for all

NEs in the link.

The hosts table can be dynamically defined by means of DNS, if a device with this

function is connected to the radio link.

The procedure for creation of the host table is described in the Chp. 4 –

"CONFIGURATION OF THE LCT PC".

2.15.5 Planning and configuration of a radio link

2.15.5.1 Planning of IP addresses

For the assignment of IP addresses for the radio link, the link administrator has to

proceed as follows.

1. Choose the IP address type to be used for the radio link:

• Class A

• Class B• Class C.

2. Assign the network ID of the IP address. During the assignment of the network ID,

pay attention to the current radio link type.

• stand-alone type radio link: it is possible to use any network ID

• Intranet type radio link: it is necessary to use a network ID not yet assigned,

otherwise, there will be conflicts and routing failures between the

interconnected networks

The RIP protocol version 1 requires the same Net-Mask all over the radio link.

Some equipment (e.g.: SRAL XD with SVR 3.8 or higher) can support, besides the

RIPv1 native routing protocol, also the OSPF routing protocol. The two protocols

RIPv1 and OSPF are always in alternative on a NE.

The TCP/IP parameter validity conditions (par. 2.12) of the LCT software have to

be considered when configuring and planning the radio link.

For the radio link, it is advisable to use Class B addresses.




2-36LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

• Internet type radio link: it is necessary to request the IP address assignment

from the authorised entity (IANA).

3. Assign the Net-Mask; it must be unique for all the SRA L link to define how many

bits, of the sub-network + host of the IP addresses field, have to be used for thesub-network addressing (station) and how many for the host addressing (NE or

service PC).

4. Identify every station with its relevant IP address, assigning the sub-network ID of

the IP addresses.

5. Identify every NE with its relevant IP address, assigning the host ID of the IP

address, follow the rules listed below addresses with fields coded with all “1" and

all “0", must not be used for a single link element because they are reserved

addresses of a TCP/IP network.

6. Define the static routing tables.

Static routing tables are strictly required for NEs connected to routers not

supporting the RIP protocol.

The information contained in the static routing table of a specific NE can be

acquired via RIP protocol, also from all other NEs in the link.

7. Define, if wished, the host table in such a way to use the names instead of the

numeric IP addresses in order to facilitate the operators task in locating and

identifying the various NEs in the link. For a detailed description of the procedure

for drawing up a host table, please refer to the Chp. 4 – "CONFIGURATION OF

THE LCT PC".

2.15.5.2 Creation of the link map

The link map constitutes the graphical interface necessary for connection from LCT to

the NEs of the link.

The map can be manually created through the NetBuilder tool or automatically created

by the LCTStart application.

For the use of NetBuilder, refer to Chp. 7 – "OPERATING GUIDE OF NETBUILDER".

For the operating modality of the LCTStart application, refer to Chp. 6.9.1 – "LCTStart

application".

2.15.5.3 Configuration of the link parameters

Once the link plan is defined, all link parameters must be assigned to the NEs, taking

into account the validity conditions provided by the software (par. 2.12).

The following link parameters can be set through software:

– Equipment IP address and relevant Net-Mask (the same Net-Mask for all the NEs

of the link), according to the planning of the IP addresses of the radio link.

An incorrect setting in a static table can cause a wrong routing of management

information into the link and then can damage the operation of the whole radio

link.

When the setting of NE link parameters is performed for the first time, it is

necessary to isolate the NE itself from the rest of the link. Otherwise conflicts may

occur in the link.





– F interface parameters (only in case of connection by means of F interface):

• Communication protocol: PPP. The PPP protocol allows the LCT PC to detect

the IP address assigned to the F interface automatically.

• Baud-rate: the value of baud-rate to set depends on the equipment type:

• 38400 bps for SRAL XD, FlexiMetro

• 19200 bps for SRA L, SRA Series 3.

– Static routing table, if necessary. It is possible to set up to a maximum of three

different routings for each NE. For every routing it is necessary to specify the

following data:

• the interface for which the routing is defined.

• the network IP address and destination gateway address.

For the use of the LCT, refer to the Chp. 6 – "OPERATING GUIDE OF LCT".

2.15.5.4 Testing of the radio link

After the execution of the planning and configuration procedures of the radio link, the

link administrator has to test it, by means of the software utilities of the TCP/IP protocol,

to check that:

1. There are no conflicts on the link.

2. All NEs can be reached and answer the connection request.

3. All possible routes of the link are free of routing errors.

For more detailed information about the use of the software utilities refer to the Microsoft

Windows Vista/XP handbooks.

2.15.5.5 Examples of radio link

Fig. 2.14 and Fig. 2.15 show two examples of radio link:

– Stand-alone type link (Fig. 2.14). This is a link without branching towards other link.

– Remote type link (Fig. 2.15). This is a link with branching towards other networks.

The example of Fig. 2.14 shows a radio link where a link administrator uses a Class B

IP address with Net-Mask = 255.255.255.0, i.e. with the following structure:

The example of Fig. 2.15 shows a SRA L where a link administrator uses a Class B IP

address with Net-Mask = 255.255.255.240, i.e. with the following structure:

In a radio link only a single default routing can be set (multiple transmission to all

networks). To assign the default routing, set the IP address = 0.0.0.0.

1 0 X X X X X X X X X X X X X X Y Y Y Y Y Y Y Y Z Z Z Z Z Z Z Z


1 0 X X X X X X X X X X X X X X Y Y Y Y Y Y Y Y Y Y Y Y Z Z Z Z





2-38LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 2.14 Example of a stand-alone radio link

Fig. 2.15 Example of a remote radio link

LCT PC

Q-LAN V-LAN

SRALXD

LCT / W

ST'

TEN

M

MJ

/ C

ODUCABLE

C AU TI O NVbat ter y


ODUCABLE DU

BL

HBA

H

AH

UB LBH D

C CC O

'

'

PS

PS

V-BUS

USER/Dext

2Mbit/ sI/OTRIBUTARIES1-8

ALMs I 0USER/Dext

2Mbit /sI/OTRIBUTARIES9-16

Q - L A N V - L AN

SRALXD

LCT / W

ST'

TEN

M

MJ

/ C

ODUCABLE



ODUCABLE DU

BL

HBA

H

AH

UB LBH D

C CC O'

'

PS

PS

V-BUS

USER/Dext

2Mbit/sI/ OTRIBUTARIES1-8

ALMs I 0USER/Dext

2Mbit/sI /OTRIBUTARIES9-16

LCT PC

STATION ASTATION B

Q - L A N V - L A N

SRALXD

LCT / W

ST'

TEN

M

MJ

/ C

ODUCABLE

C AU TIO NVbat t ery

C AU TIO NVbat t ery

ODUCABLE DU

BL

HBA

H

AH

UB LBH D

C CC O

'

'

PS

PS

V-BUS

USER/Dext

2Mbit/sI/OTRIBUTARIES1-8

ALMs I 0USER/Dext


Q - L A N V - L A N

SRALXD

LCT / W

ST'

TEN

M

MJ

/ C

ODUCABLE

C AU TIO N

Vbat t er y

C AU TIO NVbat t er y

ODUCABLE DU

BL

HBA

H

AH

UB LBH D

C CC O

'

'

PS

PS

V-BUS

USER/Dext


ALMs I 0USER/Dext






2.15.5.6 Main problems occurring in the radio link management

• No possibility to negotiate the TCP/IP protocol with the NE.

Verify the correct configuration of the LCT PC.

Check whether the NE is on and has completed the reset operation. Check the

interconnection cables.

• After the loading of the map, the NEs are disconnected.

Close the Local Craft Terminal program and check whether the TCP/IP protocol is

correctly operating.

• The operator cannot remember the IP address of the NE.

Connect to the NE through F interface, using the default private IP address

(192.168.255.3) and check the set IP address. In alternative, execute a Ping from

LCT PC making sure that the protocol is active. The NE will reply signalling its

specific IP address. In this case, it will be the default address.

• The supervision is lost when changing the NE IP address.

Each time an IP address or the system type of the NE is changed, a restart of theworking session is required (application program and protocol).

• Address planning: using Class A addresses, it is not possible to monitor all

the NEs.

Check whether for the Class A addresses a Net-Mask is used which is at least

equal to 16 (255.255.0.0).

• "hosts " file: after having updated the "hosts " file, on the map the NEs remain

disconnected.

The "hosts " file is read by the operating system only during the opening. To activate

every possible change on this file, it is necessary to restart Microsoft Windows and

the LCT.




2-40LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

B L A N

K P A G E



3 - SOFTWARE INSTALLATION


3 SOFTWARE INSTALLATION

3.1 General

The supply CD-ROM of the LCT contains:

– LCT engine including:

• LCT application program

• LCTStart application

• NetBuilder tool

– Java Runtime Environment

– software plug-ins of the supported radio equipment

– drivers for the connection via cable for Microsoft Windows Vista/XP

– online help.

3.2 System Requirements

3.2.1 Requirements for LCT PC

– Minimum hardware requirements:

• CPU 1,6 GHz

• 512 Mbyte RAM (1 GB suggested) for Microsoft Windows XP,

1 GB RAM for Microsoft Windows Vista

• Minimum Video Resolution: 1024x768

• CD-ROM drive

• Ethernet network card– Software requirements:

• Microsoft Windows Vista Business Edition (or higher) or

Microsoft Windows XP Professional (Service Pack 2 or higher) or

Microsoft Windows 7, 32 and 64 bit OS.

• Microsoft Internet Explorer 7 or higher

• TCP/IP communication protocol installed.

LCT must not be installed on the same PC where NetViewer system is already

installed (NetViewer implements also the LCT function).




3-2LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

3.3 Installation of Java Runtime Environment

In the applications that require the presence of Java Runtime Environment (LCT,

plug-in, ...), the installation of the required environment version is embedded in theinstallation of the applications themselves. In fact, the setup program of an application

check for the presence of the required version of the Java runtime environment; if the

result of the check is negative, the installation of the Java runtime environment

automatically starts.

If, at the end of the installation of Java runtime environment, the restart of the PC is

required, answer no; execute the restart, if required, only at the end of the installation of

the application.

3.4 Installation of LCT

The installation of the LCT engine installs, on the PC, the following applications:

– GUI of LCT

– LCTStart

– NetBuilder

After the installation of the LCT engine, it is possible to install:

– plugs-ins of NE

– FileZilla FTP Server

– Online help

The installation of the LCT plugins installs, on the PC, the following applications:

– FlexiPacketRadio plugin

– FlexiPacket Hub 2200 plugin

– FlexiPacket Hub 1200 plugin

– FlexiPacket Hub 800 packet plugin

– FlexiPacket FirstMile 200 plugin– FlexiPacket MultiRadio packet plugin

After the installation of Java Runtime Environment, do not uninstall possible

other versions of Java Runtime Environment, previoulsy installed on PC.

LCT requires the presence of the Java Runtime Environment.

Java Runtime Environment can be installed, if not already installed, as before

running the setup procedure of LCT as during the installation procedure of LCT

(par. 3.4.1).





3.4.1 Setup procedure of LCT

The setup procedure of LCT is the following one:

– Run the guide of the CD-ROM of LCT (file: “<CD_drive>:\Launch.exe ”).

– The main menu of the guide of the CD-ROM opens (Fig. 3.1).

Click on Install Products.

– The Install Product window appear.(Fig. 3.2).

Click on Install LCT FP MW 3.4.

– If the previous version of LCT is installed, the system displays the Welcome

window of the setup maintenance program. In this case, it is necessary to remove

the previous version of LCT before installing LCT (par. 3.4.6).

– If the previous version of LCT is not installed, the system displays the Welcome

window (Fig. 3.3) of the setup program.

Click on Next to continue the setup procedure.

– The system displays the License Agreement window.

Accept the license conditions for the use of the software. The system activates the

Next push-button. Click on Next to continue the installation procedure.

– The system displays the Choose Destination Location window (Fig. 3.4) for the

selection of the destination folder relevant of LCT; by default, the folder:

C:\Program Files\Nokia Siemens Networks is selected.

Click on Next to confirm the selection and to continue the setup procedure.

– At this point, the setup checks if the required version of the Java runtime

environment is installed on the PC. If the check is not successful, it is necessary to

install the Java runtime environment. The system display the JRE Install window.

Click on OK to start the installation of the Java runtime environment.

If, at the end of the installation of the Java Runtime Environment, the system asks

Before uninstalling a previous version of LCT, it is suggested to make a copy of

the configuration file (map file) and of the data files (log files, report files, ...)

created by the users by means of LCT.

Starting from this version of LCT, the default folders where the user data and theuser settings are saved (par. 6.8) have been changed:

– the user data are saved in the “LCT ” folder relevant to the system use profile

of the user himself:

• “C:\Documents and Settings\<user_names>\Application Data\LCT ” in

Microsoft Windows XP

• “C:\Users\<user_name>\AppData\Roaming\LCT ” in Microsoft Windows

Vista

– the user settings are saved in the “LCT ” folder relevant to the system All

Users profile, in such a way to be reachable and accessible to all users:

• “C:\Documents and Settings\All Users\Application Data\LCT ” in


• “C:\ProgramData\LCT ” in Microsoft Windows Vista.

If a previous version of LCT is already installed, it is necessary to uninstall the

already installed version and reboot the PC before executing the installation of

the new version.




3-4LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

for the execution of the PC reboot, answer No; execute the PC restart at the end

of the installation of LCT.

– After the check/installation of the Java runtime environment, the installation and

configuration of LCT starts.– At the end of the installation, the window of completed installation opens (Fig. 3.5).

Click on Finish.

The final window asking the user for the PC restarting appears (Fig. 3.6).

– After the PC restarting continue with the installation of Plug-ins, FileZilla FTP

Server and Online Help.

Fig. 3.1 Installation of LCT (1/6)

It is recommended to confirm always if the system asks into the final window for

the PC restarting.




3-6LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011








3.4.2 Plug-ins installation

The Plugin-ins installation procedure is the following one:

– Run the guide of the CD-ROM of LCT (file: “<CD_drive>:\Launch.exe ”).

– The main menu of the guide of the CD-ROM opens (Fig. 3.1).

Click on Install Products.

– The Install Product window appear.(Fig. 3.2).

Click on Install Plug-ins.

– The Plugin Installation window appear.(Fig. 3.7).

Click on Select All to install all the plug-ins available.

Then click on Install to continue with the installation.

– At the end of the installation, the window of completed installation opens (Fig. 3.8).

Click on OK to return to the Install Product window (Fig. 3.2)

– Continue with the FileZilla FTP Server installation.

Fig. 3.7 Plug-ins installation (1/2)

Fig. 3.8 Plug-ins Installation (2/2)




3-8LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

3.4.3 FileZilla FTP Server installation

The FileZilla FTP Server installation procedure is the following one:

– Starting from the Install Product window (Fig. 3.2), click on Install Tools.

– The FileZilla FTP Server Installation window appears.(Fig. 3.9).

Click on Next to continue the installation.

– At the end of the installation the Install Product window will be displayed

(Fig. 3.2).

– Continue with the Online Help installation.

Fig. 3.9 FileZilla FTP Server installation

3.4.4 Online Help installation

The Online Help installation procedure is the following one:

– Starting from the Install Product window (Fig. 3.2),

click on Install Online Help.

– The system displays the Welcome window (Fig. 3.10) of the Online Help

installation.

Click on Next to continue the installation procedure.

– If LCT is not installed, a message error opens, and setup program exits.

If LCT is installed the installation procedure starts.

– At the end of the installation, the window of completed installation opens

(Fig. 3.11).

Click on Finish.

It is not possible to install Online Help without the installation of LCT engine and

it will automatically install under LCT installation folder.





Fig. 3.10 Online Help installation (1/2)

Fig. 3.11 Online Help installation (2/2)




3-10LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

3.4.5 Menu and Icons

At the end of installation of all LCT components these menu and icons will be available

on your PC:

– The components of LCT are available into the Nokia Siemens Networks folder,

created into the Start → Programs menu (Fig. 3.12).

– The LCT application is managed by the LCT Services Manager service, which is

installed as service of Microsoft Windows with automatic start-up modality

(Fig. 3.13).

The LCT Services Manager service is run as background process on the start-up

of Microsoft Windows.

When the LCT Services Manager service is running, the icon of the LCT application

is present in the tray area of the desktop (Fig. 3.14).

On the desktop the LCT command is available for the manual start of the LCT

application (Fig. 3.15); this command must be used only if, for any reason, the LCTapplication is stopped.

Fig. 3.12 LCT menu





Fig. 3.13 LCT Services Manager service

Fig. 3.14 Icon of LCTStart running

Fig. 3.15 LCT command

3.4.6 Maintenance and Remove procedure of LCT

After the installation the following procedures are available:

– Repair: restores the already installed components of LCT. This option allows

installing again all the already installed components of LCT, in case of operational

or instability troubles concerning one or more application programs of LCT or incase of error during the setup procedure of LCT.

– Remove: uninstalls all the installed components of LCT. This option allows

removing completely the LCT application program.

The maintenance procedure of LCT is the following one:

Before executing the maintenance of LCT, it is necessary to close all the

application programs of LCT actually in progress.

The uninstallation of LCT does not remove the configuration files (map files,

bitmaps) and the data files (log files, report files, ...) created by the users with the

LCT applications.

Icon of LCT running




3-12LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

1. Run the setup program of LCT (file: “<CD_drive>:\Setup.exe ”).

2. The system displays the Welcome window (Fig. 3.16) that allows selecting the

maintenance procedure type to execute.

Click on Next to confirm the selection and to continue the maintenance procedure.

If the Remove option has been selected, a confirmation for the removal of LCT is

required.

– At the end of the maintenance, the window of completed maintenance opens.

Click on Finish.

The final window asking the user for the PC restarting appears.

Fig. 3.16 Maintenance of LCT

It is possible to run the LCT maintenance also using the typical adding/removing

mode of the application programs in Microsoft Windows (“Add/Remove

Programs” in Control Panel).

If the user asks for the stopping of the application program that is currently on

installation/disinstallation phase, he can always enter into the application

program to close it pressing the “Alt+Tab” keys.

It is recommended to confirm always if the system asks into the final window for

the PC restarting.

Once LCT is removed, it is possible to have still displayed the removed

components into the “Start” menu of Microsoft Windows. However, the system

will remove the components from the “Start” menu of Microsoft Windows at the

next restart of the PC.





3.5 Legal Log-in

At the restart of Client after the installation or after a reboot a legal log-in appear

(Fig. 3.17) .

When a user logs on to the system the solution shall ensure that a message is displayed

informing them that only authorised users are allowed access to the system in

accordance with any legal obligations.

Click OK to proceed.

Fig. 3.17 Legal log-in window




3-14LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011



4 - CONFIGURATION OF THE LCT PC


4 CONFIGURATION OF THE LCT PC

4.1 Overview

The configuration of the LCT PC depends on the modality used for the connection of the

equipment; several modes are available for the connection between the LCT PC and the

radio equipment:

– Direct connection through F interface

The LCT PC is connected directly by means of the proper cable to the local radio

equipment.

– Remote connection through F interface

A modem is used for the connection between the LCT PC and the radio equipment.

– Connection through Ethernet interface

The LCT PC is connected to the equipment via Ethernet LAN (connection modality

possible only if the radio equipment has an Ethernet network interface).

4.2 Configuration of the LCT - Radio EquipmentConnection on F interface

On the LCT PC, it is necessary to create the dial-up connection towards the radio

equipment on serial RS-232 interface using, during the modem setting, the direct

connection driver provided on the CD-ROM of the LCT software.

In case of radio link, the radio equipment that is connected (directly or through

modem/routing device) to the LCT PC has the gateway function.

In case of remote connection through modem, for the operations to execute on

the modems, refer to the relevant Manuals.




4-2LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

4.2.1 Configuration of the dial-up connection in MicrosoftWindows Vista

For the configuration of the dial-up connection, the following operations are required:

– installation of the direct connection via cable (par. 4.2.1.1)

– creation and configuration of the dial-up connection with the radio equipment

(par. 4.2.1.2)

– configuration of the TCP/IP protocol (par. 4.2.1.3).

4.2.1.1 Installation of the direct connection via cable

– In Control Panel (Fig. 4.1) click on Hardware and Sound: the window of Fig. 4.2

opens.

– Click on Phone and Modem Options. The system displays the Phone and

Modem Options window (Fig. 4.3); select Modems and then click on Add.

– The window Add Hardware Wizard - Install New Modem is displayed (Fig. 4.4).Select the Don't detect my modem, I will select it from a list and click on Next.

– The window of Fig. 4.5 is displayed; click on Have Disk .

– The window of Fig. 4.6 is displayed. Insert the CD-ROM of the LCT software and

click on Browse.

– The window Locate File is displayed (Fig. 4.7).

Select the drive CD-ROM and search the directory containing the “mdmitv01.inf

file; click on Open.

– The window of Fig. 4.6 is displayed again. Click on OK to copy the “mdmitv01.inf ”

file.

– The window of Fig. 4.8 is displayed; click on Next to continue.

– The window of Fig. 4.9 is displayed. Select the communication port (usually: COM

1) and click on Next to continue.

– The window of Fig. 4.10 is displayed.

Click on Finish to end the installation procedure for direct connection.

– The window of Fig. 4.11 is displayed where Radio Equipment Windows Direct

Connection appears in the list of installed modems. Click on OK to end and exit.

On the LCT PC, it is required that the TCP/IP communication protocol is installedin Microsoft Windows Vista.

Otherwise, it is necessary to install it, using the CD-ROM of Microsoft Windows

Vista.

In the user account control window displayed during the configuration

procedures, always give the permission to continue.

The “mdmitv01.inf ” file is available on the CD-ROM of the LCT software

(“<CD-ROM_drive>\DRIVERS\Win_XP_Vista ” folder)





Fig. 4.1 Installation of the direct connection in Microsoft Windows Vista (1/11)





4-4LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011






4-6LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011









4.2.1.2 Creation and configuration of the dial-up connection

– In Control Panel (Fig. 4.12) click on Network and Internet: the window of Fig. 4.13

opens.

– Click on Network and Sharing Center: the window of Fig. 4.14 opens.

– Select the item Set up a connection or network : the window of Fig. 4.15 opens.

– Select Set up a dial-up connection (Fig. 4.16) and click on Next: the window of

Fig. 4.17 opens.

– Insert a dummy phone number in the Dial-up phone number field and then click on

Connect: the system attempts to connect and at the end of the procedure it will

display the window of Fig. 4.18.

– Select Set up the connection anyway: the window of Fig. 4.19 opens.

The just created connection has, as default bitrate, the value 19200 kbps. This can beverified in the following way:

– select the Properties command in the pop-up menu of the icon of the dial-up

connection: the window of Fig. 4.20 opens.

– click on Configure... push-button in the General tab of the Dial-up Connection

Properties window: the window of Fig. 4.21 opens. The Maximum Speed

parameter is set to 19200 kbps.

Moreover:

– in Control Panel (Fig. 4.12) click on Hardware and Sound: the window of

Fig. 4.22 opens.

The insertion of the fictitions phone number is necessary only to the creation of

the connection. This number can be deleted later, acting on the window of the

properties of the just created connection.




4-8LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– click on Phone and Modem Options. The Phone and Modem Options window

(Fig. 4.23) is displayed.

– select the Modems tab. The window of Fig. 4.24 is displayed.

– select the Properties push-button: the window of Fig. 4.25 opens.

– select the Modems tab (Fig. 4.26): the set bitrate (19200 kbps) is read only.

– Install a new modem with the same driver and on the same COM port repeating the

steps necessary listed before: when the system displays the message of Fig. 4.27,

confirm selecting Yes.

– At the end of the procedure, the Dial-up Connection Properties window (General

tab) displays both the modems (Fig. 4.28).– Check and configure the modem #2 setting the bitrate 38400 kbps, as in Fig. 4.29.

– Open the Phone and Modem Options window (Fig. 4.30) and select the Modem

tab: two modems are displayed.

– Select the modem #2 and then Properties: the window of Fig. 4.31 is displayed.

– Click on Change settings: the window of Fig. 4.32 is displayed.

– Click on Modem tab: the window of Fig. 4.33 is displayed.

– Configure the Maximum Port Speed parameter to the value 38400.

In this way, there are two configured modems, respectively at 19200 kbps and 38400

kbps. The change of configuration is stored only for the second installed modem (#2):use the dial-up connection, selecting the modem suitable to one’s purposes.

To set other values of bitrate in the dial-up connection, execute this procedure.





Fig. 4.12 Creation and configuration of the dial-up connection in Microsoft Windows Vista

(1/22)


(2/22)




4-10LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


(3/22)


(4/22)






(5/22)


(6/22)




4-12LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


(7/22)


(8/22)






(9/22)


(10/22)




4-14LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


(11/22)


(12/22)






(13/22)


(14/22)




4-16LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


(15/22)


(16/22)


(17/22)






(18/22)


(19/22)




4-18LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


(20/22)


(21/22)






(22/22)

4.2.1.3 Configuration of the TCP/IP protocol

– In Control Panel, click on Network and Internet (Fig. 4.34).


– Click on Manage network connection: the window of Fig. 4.36 opens.

– Click with the right button of the mouse on the dial-up connection Radio

Equipment Windows Direct Connection and select Properties in the pop-up

menu that opens (Fig. 4.37): the window of the connection properties opens (Fig.

4.38).

– Click on Networking: the window of the network properties opens (Fig. 4.39).

– Select Internet Protocol Version 4 (TCP/IPv4) (Fig. 4.40) and then click on the

Properties push-button: the Internet Protocol Version 4 (TCP/IPv4) Properties

window opens (Fig. 4.41).

– Select the properties as pointed out in figure and click on Advanced.

– Set the protocol properties according to the indications shown in Fig. 4.42, Fig. 4.43 and Fig. 4.44.

– Click on OK to finish the procedure and to confirm the settings.




4-20LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 4.34 Configuration of the TCP/IP protocol in Microsoft Windows Vista (1/11)





4-22LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011








Fig. 4.41 Configuration of the TCP/IP protocol in Windows Vista (8/11)




4-24LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011








4.2.2 Configuration of the dial-up connection in MicrosoftWindows XP

For the configuration of the dial-up connection, the following operations are required:

– installation of the direct connection via cable (par. 4.2.2.1)

– creation and configuration of the dial-up connection with the radio equipment

(par. 4.2.2.2)

– configuration of the TCP/IP protocol (par. 4.2.2.3).

4.2.2.1 Installation of the direct connection via cable

– In Control Panel double click on Phone and Modem Options (Fig. 4.45). The

system displays the Phone and Modem Options window (Fig. 4.46); select

Modems and then click on Add.

– The window Add Hardware Wizard - Install New Modem is displayed (Fig. 4.47).

Select the Don't detect my modem; I will select it from a list and click on Next.

– The window of Fig. 4.48 is displayed. Click on Have Disk .

– The window of Fig. 4.49 is displayed. Insert the LCT software CD-ROM and click

on Browse.

In Microsoft Windows XP the TCP/IP communication protocol must be installed

on the LCT PC.

Otherwise the software must be installed using the Microsoft Windows XPCD-ROM.




4-26LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– The window Locate File is displayed (Fig. 4.50).

Select the drive of the installation floppy-disk/CD-ROM and search the directory

containing the “mdmitv01.inf ” file; click on Open.

– The window of Fig. 4.51 is displayed again. Click on OK to copy the “mdmitv01.inf ”

file.

– The window of Fig. 4.52 is displayed; click on Next to continue.

– The window of Fig. 4.53 is displayed. Select the communication port (usually: COM

1) and click on Next to continue.

– The window of Fig. 4.54 is displayed. Click on Continue Anyway to continue.

– The window of Fig. 4.55 is displayed.

Click on Finish to end the installation procedure for direct connection.– The window of Fig. 4.56 is displayed where Radio Equipment Windows Direct

Connection appears in the list of installed modems. Click on OK to end and exit.

Fig. 4.45 Installation of the direct connection in Microsoft Windows XP (1/12)

The “mdmitv01.inf ” is available on the CD-ROM of the LCT software

(“<CD-ROM_drive>:\DRIVERS\Win_XP_Vista ” folder).




4-28LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011








4-30LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011



4.2.2.2 Creation and configuration of the dial-up connection

– Click on Start and select: Settings → Network Connections. The system

displays the Network Connections window (Fig. 4.57). Select Create a New

Connection option.

– The system displays the New Connection Wizard window (Fig. 4.58). Click on

Next to continue.

– The system displays the window shown in Fig. 4.59. Select the Set up an

advanced connection option. Click on Next to continue.

– The system displays the window shown in Fig. 4.60. Select the Connect directly

to another computer option. Click on Next to continue.

– The system displays the window shown in Fig. 4.61. Select the Guest option. Click

on Next to continue.





– The system displays the window for the selection of the connection name

(Fig. 4.62). Type the name and click on Next to continue.

– The system displays the equipment selection window (Fig. 4.63).

– Select the Radio Equipment Windows Direct Connection option (Fig. 4.64).Click on Next to continue.

– The system displays the window shown in Fig. 4.65. Click on Finish to complete

and to exit.

– In Control Panel, double click on Phone and Modem Options (Fig. 4.66).

– The system displays the Phone and Modem Options window (Fig. 4.67). Select

Modems and then click on Properties.

– The system displays the window shown in Fig. 4.68. Click on Advanced (Fig. 4.69)

and then on Change Default References.

– The system displays the window shown in Fig. 4.70. Set the properties of theconnection as pointed out into the figure. Click on Advanced.

– The system displays the window shown in Fig. 4.71. Set the properties of the

connection as pointed out into the figure.

– Click on OK to end and confirm the settings. To close all the currently open

windows.

Fig. 4.57 Creation and configuration of the dial-up connection in Microsoft Windows XP(1/15)

For the connection to the last generation equipment (e.g.: SRAL XD, FlexiMetro)

equipment, it is necessary to set 38400 bps as port rate.




4-32LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 4.58 Creation and configuration of the dial-up connection in Microsoft Windows XP

(2/15)

Fig. 4.59 Creation and configuration of the dial-up connection in Windows XP (3/15)


(4/15)






(5/15)


(6/15)




4-34LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


(7/15)


(8/15)






(9/15)


(10/15)




4-36LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


(11/15)


(12/15)






(13/15)


(14/15)

For the connection to the last generation equipment (e.g.: SRAL XD, FlexiMetro)

equipment, set 38400 bps.




4-38LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


(15/15)

4.2.2.3 Configuration of the TCP/IP protocol

– In Control Panel, double click on Network Connections (Fig. 4.72).

– The Network Connections window (Fig. 4.73) opens. Click with the right button of

the mouse on the RADIO connection and select Properties in the pop-up menu

that opens (Fig. 4.74).

– The window with the connection properties (Fig. 4.75) opens. Click on

Networking.

– The window with the network properties opens (Fig. 4.76). Select PPP and click on

Settings.

– The PPP Settings window (Fig. 4.77) opens. Set the properties according to what

displayed in the figure and click on OK.

– In the window with the network properties (Fig. 4.76) select Internet Protocol

(TCP/IP) and click on Properties.

– The system displays the Internet Protocol (TCP/IP) Properties window

(Fig. 4.78). Select the properties as pointed out in figure and click on Advanced.– Set the protocol properties according to the indications shown in Fig. 4.79,

Fig. 4.80 and Fig. 4.81.

– Click on OK to finish the procedure and to confirm the executed settings.





Fig. 4.72 Configuration of the TCP/IP protocol in Microsoft Windows XP (1/10)





4-40LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011






4-42LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011






4-44LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

4.3 Configuration of the LCT - Radio EquipmentConnection on Ethernet Interface

The LCT PC is interconnected with the equipment via an Ethernet LAN based on the

TCP/IP\ protocol.

The only operation required on the LCT PC is the TCP/IP protocol configuration for the

Ethernet NIC.

4.3.1 Configuration of the TCP/IP protocol in MicrosoftWindows Vista

The configuration procedure of the TCP/IP protocol in Microsoft Windows Vista for an

Ethernet NIC is the following one:

– In the Control Panel click on Network Connections. The window Network

Connections (Fig. 4.82) appears.

– Click by means of the mouse R.H. push-button on the LAN connection icon and,

then, select Properties (Fig. 4.83).

– The system displays the Local Area Network Properties window (Fig. 4.84).

Select Internet Protocol Version 4 (TCP/IPv4) and click on Properties.

– The window Internet Protocol Version 4 (TCP/IPv4) Properties (Fig. 4.85) is

displayed.

– Set the TCP/IP protocol properties depending on what is shown in Fig. 4.85,

Fig. 4.86, Fig. 4.87, Fig. 4.88.

Under Microsoft Windows, the Server PC must be equipped with the following

software components:

– Ethernet NIC and corresponding driver

– TCP/IP communication protocol.

Otherwise the software must be installed using the Microsoft Windows CD-ROM

and/or the floppy-disk/CD-ROM with drivers for the NIC.

The IP address assigned by default in factory to the Ethernet network interface (if

available) of radio equipment depends on the equipment type (e.g.: for FlexiMetro

is 192.168.255.3, for SRAL XD is 10.10.10.10).

In the user account control window displayed during the configuration procedure,

always give the permission to continue.

If the LAN connection is not present, it is necessary to create it by means of the

“Make New Connection” feature, using the Microsoft Windows Vista CD-ROM

and/or the floppy disk/CD-ROM with the software drivers of the Ethernet NIC.

If the TCP/IP protocol is not available it must be installed using the Microsoft

Windows Vista installation CD-ROM.





– Close the window Internet Protocol Version 4 (TCP/IPv4) Properties clicking on

OK. The window LAN Properties (Fig. 4.84) is displayed again.

– Click on OK to end and confirm the settings.

Fig. 4.82 TCP/IP protocol configuration in Microsoft Windows Vista (1/7)


The IP address, the Subnet Mask of the Client PC and the gateway IP address (Fig.

4.85) must therefore be requested from the network administrator.

Depending on the Ethernet network configuration, it may be necessary to activate

or deactivate the DNS (Fig. 4.87); if the DNS is activated, the network

administrator must be asked for the DNS configuration parameters to insert.




4-46LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011



(*) The setting of the parameters depends on the network configuration and they have to be executed by the network administrator.







(*) The setting of the parameters depends on the network configuration and they have to

be executed by the network administrator.






4-48LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


4.3.2 Configuration of the TCP/IP protocol in MicrosoftWindows XP

The configuration procedure of the TCP/IP protocol in Microsoft Windows XP for anEthernet NIC is the following one:

– In Control Panel double click on Network Connections.

– The window Network Connections (Fig. 4.89) appears.

Click by means of the mouse R.H. push-button on the LAN connection icon and

select Properties (Fig. 4.90).

– The system displays the Local Area Connection Properties window (Fig. 4.91).

Select Internet Protocol (TCP/IP) and click on Properties.

– The window Internet Protocol (TCP/IP) Properties (Fig. 4.92) is displayed.

– Set the TCP/IP protocol properties depending on what is shown in Fig. 4.92,

Fig. 4.93, Fig. 4.94, Fig. 4.95, Fig. 4.96 and Fig. 4.97.

If the LAN connection is not present, it is necessary to create it by means of the

“Create a new connection” feature, using the Microsoft Windows XP CD-ROM

and/or the floppy disk/CD-ROM with the software drivers of the Ethernet NIC.

If the TCP/IP protocol is not available it must be installed using the Microsoft

Windows XP installation CD-ROM.







– Close the window Internet Protocol (TCP/IP) Properties clicking on OK. The

window Local Area Connection Properties is displayed again.

– Click on OK to end and confirm the settings.


The IP address, the Subnet Mask of the Client PC and the gateway IP address (Fig.

4.92) must therefore be requested from the network administrator. Depending on

the Ethernet network configuration, it may be necessary to activate or deactivate

the DNS (Fig. 4.94).

If the DNS is activated, the network administrator must be asked for the DNS

configuration parameters to be inserted.




4-50LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011






4-52LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011










4-54LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011



5 - LCT - RADIO EQUIPMENT CONNECTION


5 LCT - RADIO EQUIPMENT CONNECTION

5.1 Overview

This chapter describes the modalities and the problems concerning the connection and

the access, via TCP/IP protocol, of the LCT PC to the radio equipment. These differ

according to:

– the operating system installed on the LCT PC (Microsoft Windows Vista/XP)

– the type of the interface used for the connection (serial RS-232C or Ethernet).

5.2 LCT - Radio Equipment Connection Mode

5.2.1 Direct connection on F interface

5.2.1.1 Overview

The LCT PC is directly connected, by a proper cable, to the local radio equipment

(Fig. 5.1).The local radio equipment has the gateway functions towards possible adjacent NEs

connected through any network interface (radio, Ethernet, V-bus, ...); Fig. 5.2 reports an

example of connection on F interface of LCT to the equipment of a radio link.

Fig. 5.1 LCT - radio equipment direct connection on F interface

For all the radio equipment, the IP address assigned by default in factory to the F

interface is 192.168.255.3.

RADIO EQUIPMENT

DCE DTE

LCT PC

F INT.(RS-232C)

WST

WSTLCT


ALARMS

MCT

MSD'T

E

/WJ

N/

SYSTEM

I

MEMORY

SRA4

K EY P WR

O

V 11 G 7 03IN

V 11 G 7 03IN

STM 2

STM 2OUT

STM 1OUTIN IN

CH.B

CH.BCH.A

OUTSTM 1

OUTIN

CH.A

IN

O UT D AT AE XP .

OUT

ALMCABLE

ALMODU

CABLE ALM

DATAEXP.

ALMODU

CABLE

ICO-CH

D'

PS

O

ODUPWR

I

ODUPWROUTIN

D'

OUT

CO-CH

IN

IF

OPS

CABLEIF




5-2LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 5.2 LCT - radio link direct connection on F interface

5.2.1.2 Requirements of RS-232C serial cable

For the local connection between LCT PC and the radio equipment, a serial cable is

required according to EIA RS-232C standard specifications. It must be a not-modem

pin-to-pin cable, equipped with a 9-pin male CANNON connector on the radio

equipment side (Fig. 5.3).

In this connection, the LCT PC is considered a DTE unit, while the radio equipment is

considered a DCE unit.

Fig. 5.3 RS-232C connecting cable between LCT and radio equipment

LCT PC

F INT.(RS-232C)

DTEDCE

RADIO LINK

RADIOEQUIPMENT

RADIOEQUIPMENT

TERMINAL B TERMINAL A

Q-LAN V-LAN

SRAL XD

LCT/

WST'

TEN

M

MJ

/C

ODUCABLE

CAUTI O NVbatt er y

CAUTI O NVbatt er y

ODUCABLE DU

BL

HB A

H

AH

UB LBH D

C CC O

'

'

PS

PS

V-BUS

USER/Dext

2 Mbit/s I/O TRIBUTARIES1-8

ALMs I 0USER/Dext

2Mbit/sI/O TRIBUTARIES9-16

Q-LAN V-LAN

SRAL XD

LCT/

WST'

TEN

M

MJ

/C

ODUCABLE

CAUTI O NVbat t er y


ODUCABLE DU

BL

HB A

H

AH

UB LBH D

C CC O'

'

PS

PS

V-BUS

USER/Dext


ALMs I 0USER/Dext

2Mbit/s I/O TRIBUTARIES9-16

RADIO EQUIPMENT (DCE) LCT PC (DTE)

NOT

USEDNOT

USED





5.2.2 Remote connection on F interface

5.2.2.1 Overview

The use of a modem allows to establish a remote connection, using a F interface,

between the LCT PC and the radio equipment (Fig. 5.4).

The radio equipment, connected to the LCT PC, has the gateway function towards

possible adjacent NEs connected through any network interface (radio, Ethernet, V-bus,

...); Fig. 5.5 displays an example of remote connection on F interface of LCT to the

equipment of a radio link.

Fig. 5.4 LCT - radio equipment remote connection on F interface

For all the radio equipment, the IP address assigned by default in factory to the F

interface is 192.168.255.3.

RADIO EQUIPMENT

LCT PC

MODEMPC SIDE

MODEMRADIO SIDE

TELEPHONELINE

DCE DCE

DCEDTE

F INT.(RS-232C)

INT. F(RS-232C)

WST

WSTLCTQ-LAN E-LINK

ALARMS

MCT

MS

D'T

E

/

WJ

N/

SYSTEM

I

MEMORY

SRA4

K EY P WR

O

V 11 G 7 03IN

V 11 G 7 03IN

STM 2

STM 2OUT

STM 1OUTIN IN

CH.B

CH.BCH.A

OUTSTM 1

OUTIN

CH.A

IN

O UT D AT AE XP .

OUT

ALMCABLE

ALMODU

CABLE ALM

DATAEXP.

ALMODU

CABLE

ICO-CH

D'

PS

O

ODUPWR

I

ODUPWROUTIN

D'

OUT

CO-CH

IN

IF

OPS

CABLEIF




5-4LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 5.5 LCT - radio link remote connection on F interface

5.2.2.2 Characteristics of the connection cables

The following is a list of requirements for the connection cables to be used:

– Connection between radio equipment and modem.

Use a standard cable for the DCE - DCE connection, because both radio

equipment and modem are DCE units. The cable must be provided, on the radio

equipment side, with a 9-pin male CANNON connector.

– Connection between LCT PC (RS-232C serial port) and modem.Use a standard cable for the DTE-DCE connection, because the LCT PC is a DTE

unit and the modem is a DCE unit.

– Connection between modem and telephone line.

The modem interface towards the telephone line is usually terminated with a 8-pin

RJ45 standard jack.

Some modems have two different interfaces (one for the switched line and one for

the dedicated line).

The use of the remote connection requires the installation and the configuration

in Microsoft Windows of the modem used to replace the “direct connection via

cable” modem during the configuration procedure (Chp. 4 – "CONFIGURATION

OF THE LCT PC").

For more details about the configuration and use of modems, refer to the relevantManuals.

DCE

RADIO LINK

RADIOEQUIPMENT

RADIOEQUIPMENT

TERMINAL B TERMINAL A

LCT PC

MODEMPC SIDE

MODEMRADIO SIDE

TELEPHONE

LINE

DCE

DCEDTE

F INT.

(RS-232C)

F INT.

(RS-232C)

Q-LAN V-LAN

SRALXD

LCT/

WST'

TEN

M

MJ

/C

ODUCABLE

C A U T IO NVbat t er y

C A U T IO NVbat t er y

ODUCABLE DU

BL

HB A

H

AH

UB LBH D

C CC O

'

'

PS

PS

V-BUS

USER/Dext


ALMs I 0USER/Dext


Q - L A N V - L AN

SRALXD

LCT/

WST'

TEN

M

MJ

/C

ODUCABLE



ODUCABLE DU

BL

HB A

H

AH

UB LBH D

C CC O

'

'

PS

PS

V-BUS

USER/Dext


ALMs I 0USER/Dext






5.2.2.3 Characteristics and configuration of the modems

Modem characteristics

The modems must be Hayes compatible and must support standard AT commands,

with a minimum baud-rate of 38400 bps (typical transmission rate of radio equipment).

This condition represents a restriction for the whole system.

In this case, the communication between modem and radio equipment must takeplace

at 38400 bps, while a higher baud-rate can be used between modems, depending on

the modem characteristics and the quality of the used line.

Modem configuration

The modem configuration can be performed:

– by PC, providing the modem with AT commands by means of a terminal emulator

such as the Microsoft Windows HyperTerminal.

– manually, using the modem control panel.

A variety of configurations, pre-defined by the manufacturer, is usually stored in the

modem firmware. These cover a large field of applications.

In this case, it is sufficient to load the most proper configuration according to the type of

used line (switched or dedicated) and to set the following commands:

– on modem, radio side:

• disable every kind of flow control

• disable every type of error correction, compression and auto-request

• if a switched line is used, set the modem to auto-answer mode; this is usually

achieved by setting the AT command: “&S0=1”

– on modem, PC side:

• disable every kind of flow control• disable every type of error correction, compression and auto-request

• if a switched line is used, set the CDC control in such a way that it is ignored

in the current connection and returns to the command mode when the DTR

signal switches from “High” to “Low”; this is usually achieved by setting the AT

command: “&C”

• if a switched line is used, set the DTR control in such a way that it is ignored

in the current connection and returns to the command mode when the DTR

signal changes from “High” to “Low”; this is usually achieved by setting the AT

command: “&D”.

It is recommended to store the default configuration in the modem memory, usingthe AT command: “&W” (modems use the default configuration at start-up).




5-6LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

5.2.3 Direct connection on Ethernet interface

For the radio equipment that supports the TNMP/SNMP protocol on Ethernet network

interface, it is possible to have the direct connection on Ethernet interface between the

LCT PC and the radio equipment (Fig. 5.6).

In this case the connection between LCT PC and the radio equipment must be realized

through a crossed Ethernet network cable.

The radio equipment connected to the LCT PC has the gateway function towards

possible adjacent NEs connected through any network interface (radio, Ethernet, V-bus,

...); Fig. 5.7 displays an example of connection on Ethernet interface of LCT to the

equipment of a radio link.

FlexiPacketRadio is provided with a single Giga Ethernet port, used both for the

management traffic and for the payload traffic (Ethernet user frames and TDMoE

packets).

In order to avoid the possible loss of payload traffic, use an Ethernet switch for the local

connection of LCT to FlexiPacketRadio (Fig. 5.8).

Fig. 5.6 LCT - radio equipment direct connection on Ethernet interface

Fig. 5.7 LCT - radio link direct connection on Ethernet interface

The private IP address assigned by default in factory to the Ethernet interface of

a radio equipment depends on the type of the radio equipment (e.g.: for

FlexiMetro is 192.168.255.3, for SRAL XD is 10.10.10.10).

Use the private IP address of the radio equipment only in case of univocal

connection from LCT to the local radio equipment (e.g.: direct connection

between LCT and the local radio equipment). In all the other cases (e.g.:

connection from LCT to more radio nodes of the same station interconnected by

a network interface, connection of LCT to the corporate LAN, ...), to ensure the

reachability of a radio equipment it is necessary to use its public IP address.

In a radio link, to ensure the reachability of each equipment from LCT, it is

necessary to use the public IP addresses of the radio equipment.

CROSSEDCABLE

LCT PC

DU

BL

HB A

H

AH

UB LBH D

C CC O

'

'

PS

PS

Q -L AN V -L AN

SRALXD

LCT/

WST'

TE N

M

MJ

/C

ODUCABLE

CAUTION

Vbattery

CAUTIONVbattery

ODUCABLE

V-BUS

USER/Dext


ALMs I 0USER/Dext


RADIO EQUIPMENT

ETHERNET

RADIO LINK

TERMINAL ATERMINAL B

LCT PC

RADIO EQUIPMENTRADIO EQUIPMENT

DU

BL

HB A

H

AH

UB LBH D

C CC O

'

'

PS

PS

Q-LAN V-LAN

SRALXD

LCT/W

ST'

TEN

M

MJ

/C

ODUCABLE

CAUTIONVbattery

CAUTIONVbattery

ODUCABLE

V-BUS

USER/Dext


ALMs I 0USER/Dext

2Mbit/sI/OTRIBUTARIES9-16DU

BL

HB A

H

AH

UB LBH D

C CC O

'

'

PS

PS

Q - LA N V - LA N

SRALXD

LCT/W

ST

'

TEN

M

MJ

/C

ODUCABLE

CAUTIONVbattery

CAUTIONVbattery

ODUCABLE

V-BUS

USER/Dext


ALMs I 0USER/Dext


CROSSED

CABLE

ETHERNET





Fig. 5.8 FlexiPacketRadio local connection

5.2.4 Connection via LAN Ethernet interface

For the radio equipment that supports the TNMP/SNMP protocol on Ethernet network

interface, it is possible to have the connection on Ethernet LAN between the LCT PC

and the radio equipment (Fig. 5.9). The radio equipment connected to the LCT PC has

the gateway function towards possible adjacent NEs connected through any network

interface (radio, Ethernet, V-bus, ...); Fig. 5.10 displays an example of connection on

LAN Ethernet of LCT to the equipment of a radio link.

Fig. 5.9 LCT - radio equipment connection through LAN Ethernet

In case of Ethernet LAN, to ensure the reachability of the radio equipment from

LCT, it is necessary to use the public IP addresses of the radio equipment.

Consequently, LCT must be set with an IP address belonging to the same IP

net-mask of the radio equipment.

In a radio link, to ensure the reachability of each equipment from LCT, it is

necessary to use the public IP addresses of the radio equipment.

LCT PC

PAYLOAD

TRAFFIC

FLEXIPACKETRADIO

SWITCH

Ethernet

TERMINAL A

LAN - ETHERNET

INTRANET/ INTERNET

LCT PC

RADIO EQUIPMENT

DU

BL

HB A

H

AH

UB LBH D

C CC O

'

'

PS

PS

Q - LA N V - LA N

SRALXD

LCT/W

ST'

TEN

M

MJ

/C

ODU CABLE

CAUTIONVbattery

CAUTIONVbattery

ODU CABLE

V-BUS

USER/Dext

2 Mbit/s I/O TRIBUTARIES 1-8

ALMs I 0USER/Dext

2 Mbit/s I/O TRIBUTARIES 9-16




5-8LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 5.10 LCT - radio link connection through LAN Ethernet

5.3 Activation of LCT - Radio EquipmentConnection

The modes to activate the LCT - radio equipment connection differ according to the

interface types:

– F interface

It is necessary to activate the dial-up connection to radio equipment on the LCT,

before running the LCT.

– Ethernet interface

The connection between the LCT PC and the radio equipment is automatically.

5.3.1 Activation of the dial-up connection in Microsoft WindowsVista

The activation procedure of the dial-up connection in Microsoft Windows Vista is the

following:

– In Control Panel (Fig. 5.11), double click on Network and Internet: the window of

Fig. 5.12 opens.


– Click on Manage network connection: the window of Fig. 5.14 opens.

If the connection uses a modem, the communication via modem must be

activated first.

RADIO LINK

TERMINAL ATERMINAL B

LAN - ETHERNET

INTRANET/ INTERNET

PC LCT

RADIO EQUIPMENTRADIO EQUIPMENT

DU

BL

HB A

H

AH

UB LBH D

C CC O

'

'

PS

PS

Q - LA N V - LA N

SRALXD

LCT/W

ST'

TEN

M

MJ

/C

ODUCABLE

CAUTIONVbattery

CAUTIONVbattery

ODUCABLE

V-BUS

USER/Dext


ALMs I 0USER/Dext

2Mbit/sI/OTRIBUTARIES9-16DU

BL

HB A

H

AH

UB LBH D

C CC O

'

'

PS

PS

Q - LA N V - LA N

SRALXD

LCT/W

ST

'

TEN

M

MJ

/C

ODUCABLE

CAUTIONVbattery

CAUTIONVbattery

ODUCABLE

V-BUS

USER/Dext


ALMs I 0USER/Dext






– Click with the right button of the mouse on the Radio Equipment Windows Direct

Connection dial-up connection and select Connect in the pop-up menu that

opens: the Connect Dial-up Connection window (Fig. 5.15) opens.

– Type the password in the corresponding field and select Connect.– Follow the instructions displayed on the screen.

– The Connection Complete window is displayed. Click on OK.

– Once established the connection, the “tray area” (bottom right corner of the

desktop) shows the icon of monitor of the connection. Clicking with the right button

of the mouse on this icon and selecting Status, the window of the connection

status opens, by means of which it is possible to display information, details and

preferences regarding the connection in progress.

Fig. 5.11 Activation of the dial-up connection in Microsoft Windows Vista (1/5)

If the dial-up connection between the radio equipment and the PC is interrupting,

should no traffic be on the serial line, it is necessary to keep the dial-upconnection alive in one of the following ways:

– sending a cyclic ping (“ping -t”) (par. 5.5) to the radio equipment (Fig. 5.22)

– start-up LCT.

Exiting from LCT, the connection must be closed with the following procedure:

– through the R.H. push-button of the mouse, click on the connection monitor

icon and select “Disconnect”.




5-10LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011









5.3.2 Activation of the dial-up connection in Microsoft WindowsXP

The activation procedure of the dial-up connection in Microsoft Windows XP is the

following:

– In Control Panel, click twice on Network Connections (Fig. 5.16). The system

displays the Network Connections window (Fig. 5.17).

If the connection uses a modem, the communication via modem must be

activated first.




5-12LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– With the R.H. push-button of the mouse, click on the icon for the dial-up connection

created before (into the example: “RADIO”) and, into the displayed pop-up menu

(Fig. 5.18), select Properties.

– The system displays the RADIO Properties window (Fig. 5.19). Select Configure.– The system displays the Modem Configuration window (Fig. 5.20). Select the

Show terminal window option. Close the open window, clicking on OK.

– Into the Network Connections window (Fig. 5.21) click twice on the icon of the

dial-up connection (into the example: “RADIO”).

– The system displays the Connect RADIO window (Fig. 5.22). Select Connect.

– The system displays the Pre-Dial Terminal Screen window (Fig. 5.23). Wait for to

be sure that the hardware works properly, that the system starts up the data stream

and then click on Continue.

– At the end of the connection procedure, into the Network Connections window,

the “RADIO” icon switches from the “Disconnected” status to the “Connected” one

(Fig. 5.25).

– If the operator selects View status of this connection into the Network Tasks

field of the Network Connections window (Fig. 5.25), the system opens the statuswindow of the connection (into the example: RADIO Status) (Fig. 5.26 and Fig.

5.27). Through such a window, it is possible to display information, details and

preferences concerning the connection on progress.

The packages of the TCP/IP protocol start and end with the character (“~”).

During the connection procedure, the system displays the “Connecting RADIO...”

window (Fig. 5.24). If the operator clicks on “Cancel”, it is always possible to stop

immediately the connection procedure itself.

If the dial-up connection between the radio equipment and the PC is interrupting,

should no traffic be on the serial line, it is necessary to keep the dial-up

connection activated in one of the following ways:

– sending a cyclic ping (“ping -t”) (par. 5.5) to the radio equipment (Fig. 5.28)

– starting up LCT

Exiting from LCT, the connection must be closed with the following procedure:

– through the R.H. push-button of the mouse, click on the connection monitoricon and select “Disconnect”.





Fig. 5.16 Activation of the dial-up connection in Microsoft Windows XP (1/13)





5-14LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011






5-16LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011







5-18LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011







5.4 Routing Troubles with the TCP/IP Packets

5.4.1 Common cases of TCP/IP packet routingThe TCP/IP protocol can manage different interfaces (serial line, Ethernet network, ....)

according to the network functions present on the LCT PC (PC - equipment connection,

Internet connection, company LAN connection, ....).

Then, some routing troubles with the TCP/IP packets can occur.

The most common cases are the following ones:

– TCP/IP on serial line only

If on the service PC the TCP/IP protocol manages only the serial line and it has

been correctly configured, all the sent packets are forwarded on the serial line.

In this case, if the equipment is directly connected to the LCT PC, it is always

reachable. In case of troubles, it is possible to force the packet forwarding on theserial line selecting the option “Use default gateway on remote network” into the

configuration window of the TCP/IP protocol for the serial line (Fig. 5.29, Fig. 5.30).

– TCP/IP on Ethernet network only

If on the LCT PC the TCP/IP protocol manages only the Ethernet network and it

has been correctly configured, all the sent packets are forwarded on the Ethernet

network.

In this case to reach the equipment, it is necessary to configure correctly the

involved gateways.

– TCP/IP as on serial line as on Ethernet network

If on the LCT PC the TCP/IP protocol manages as the serial line as the Ethernet

network, for each sent packet the system has to decide the use of the serial line orof the Ethernet network. In each case, it will be used only one of the two routes.

The choice of the route to be used depends on the IP address of the target, on the

configuration of the TCP/IP protocol and on the equipment connected to the serial

line.

If on the serial line, it is connected an equipment with IP address X.X.X.X, in case

of NAPT not supported or disabled, the relevant serial port of the LCT PC will have

an IP address equal to the one of the equipment plus 1 and a Net-Mask that

depends on the class of its own IP address (on the contrary, it does not depend on

the equipment Net-Mask). The Ethernet card of the LCT PC has an IP address and

a Net-Mask set by the user.

A packet with IP address X.X.X.X is forwarded:

• on the serial line, if it belongs to the sub-network defined by the IP address

and by the Net-Mask of the LCT PC serial port (For instance: in the case of

serial port with IP address = 150.160.170.181 and Net-Mask = 255.255.0.0,

the addresses that belong to the sub-network are 150.160.X.X)

• on the Ethernet network, if it belongs to the sub-network defined by the IP

address and by the Net-Mask of the LCT PC network card (for instance: in the

case of Ethernet card with IP address = 138.132.140.104 and Net-Mask =

255.255.255.0, the addresses that belong to the sub-network are

138.132.140.X).

To route correctly some packets with an IP address not compatible neither with the

serial line nor with the Ethernet network, it is necessary to respect the following

indications:




5-20LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

• to forward the packets on the serial line, select the option “Use default

gateway on remote network” into the configuration window of the TCP/IP

protocol for the serial line (Fig. 5.29, Fig. 5.30); this configuration affects all

the programs that use the TCP/IP protocol (for instance: Microsoft Internet

Explorer)

• to forward the packets on the Ethernet network, define and configure a

gateway for the Ethernet interface.

Fig. 5.29 Forcing of “Use default gateway on remote network” option in Microsoft Windows

Vista

In case of NAPT enabled, NE shall assign to LCT connecting via F interface an

available address belonging to the NE private network (i.e. 192.168.255.x, being

192.168.255.3 the private NE IP address).

NE and LCT communicate using only their private IP addresses, which are never

propagated in the public of management network.

“Use default gateway on remote network” option





Fig. 5.30 Forcing of “Use default gateway on remote network” option in Microsoft Windows

XP

“Use default gateway on

remote network” option




5-22LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

5.4.2 Useful commands to solve reachability problems

5.4.2.1 Status window of the connection

In Microsoft Windows Vista/XP the operator can know the IP address of the local

equipment connected with the serial line through the status window of the connection

(Fig. 5.31, Fig. 5.32). He can access to this window through the connection icon present

into the “tray area” (lower R.H. corner of the desktop), or through the following path:

Control Panel → Network Connections → View status of this connection.

Fig. 5.31 Status window of the connection in Microsoft Windows Vista

Fig. 5.32 Status window of the connection in Microsoft Windows XP

IP address of the PC.

IP address of the equipment.In case of NAPT not supportedor disabled, if it is not pointedout, it can be get from the IP

address of the PC subtractingone (in the example: if the IP

address of the PC is:143.29.176.173, the IP address

of the equipment is:143.29.176.172).

IP address of the PC.

IP address of the equipment.In case of NAPT not supported ordisabled, if it is not pointed out, itcan be get from the IP address ofthe PC substracting one (into the

example: if the IP address of the PCis: 150.166.153.203, the IP address

of the equipmentis:150.166.153.202).





5.4.2.2 The “ipconfig” command

The “ipconfig” command allows, in Microsoft Windows, displaying the configuration of all

the PC interfaces that support the TCP/IP protocol (Fig. 5.33). This command is

executed by Command Prompt.

Fig. 5.33 The “ipconfig” command

5.4.2.3 The “route print” commandThe “route print” command allows, in Microsoft Windows displaying the IP routing

parameters (Fig. 5.34). This command is executed by Command Prompt.

Fig. 5.34 The “route print” command

IP address of the PC on the connection by means of Finterface. To get the IP address of the equipment, subtract 1

(in the example, the IP address of the equipment is:192.168.255.3).

This value indicates the PClocal interfaces.

IP address of the PC on theEthernet network.

IP address of the PC on connection by means of F interface.

To get the IP address of the equipment subtract 1 (in theexample, the IP address of the equipment is: 192.168.255.3).




5-24LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

5.4.2.4 The “route add” command

The “route add” command allows, in Microsoft Windows, changing the IP routing

parameters as, for instance, to force the serial line use for a specific IP address. This

command is executed by Command Prompt. The easiest mode to use this command is

the following one:

“route add <IP_address_to_reach> <gateway_to_use>”.

For instance, if the IP address of our PC on the PC - equipment network is

160.160.160.161 and the address of a remote equipment to be reached on the serial line

(and, then, through the local equipment) is 150.150.150.150, it is necessary to use the

following command:

“route add 150.150.150.150 160.160.160.161”

5.4.2.5 The “tracert” command

The “tracert” command allows, in Microsoft Windows, detecting the route of the packets

forwarded to a specific address (Fig. 5.35). This command is executed by Command

Prompt. It is necessary to specify the destination IP address: “tracert IP_address”.

Fig. 5.35 The “tracert” command

5.5 Troubles in the Dial-up Connection to theLocal Equipment

5.5.1 Local equipment not reachable using the default local IPaddress

If all the following conditions are present:

– connection to the local equipment on serial line (dial-up connection)

– presence, at the same time, of at least two interfaces of the PC (e.g.: Ethernet

network card and dial-up connection) using the TCP/IP protocol

– local equipment with IP address correctly configured,

the local equipment can result not reachable using the default local IP address(192.168.255.3).





In this case, it is not possible to use the default local map. Then it is necessary to create

by means of the Net Builder program (refer to the Chp. 7 – "OPERATING GUIDE OF

NETBUILDER"), a new map with reference to the real IP address of the local equipment

(par. 5.5.3).

5.5.2 Deactivation of the dial-up connection for traffic absence

The dial-up connection between the local equipment and the PC can be interrupted if

there is not traffic on the serial line.

To keep always active the dial-up connection, it is advisable to forward a cyclic ping

towards the local equipment, using the following command from Command Prompt (Fig.

5.36):

“ping -t <IP_address>”

The “<IP_address>” is the real IP address of the local equipment (par. 5.5.3) and “-t” is

the cyclic execution option.

Fig. 5.36 “ping –t” command

5.5.3 Detection of the local equipment IP address

In Microsoft Windows Vista/XP the operator can know the IP address of the localequipment connected with the serial line through the status window of the connection

(par. 5.4.2.1).

The execution of LCT causes a permanent data stream on the serial line and then

it keeps always the dial-up connection active.




5-26LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

B L A N

K P A G E



6 - OPERATING GUIDE OF LCT


6 OPERATING GUIDE OF LCT

6.1 Features of LCT

LCT provides the Element Manager function for the management of the radio

equipment.

The graphical interface for the access to the equipment is constituted by a map which

can be created manually by means of the NetBuilder tool or automatically by the

LCTStart application.

LCT supports the following management application protocols of NE:



LCT is able to manage maps which contain, at most, three NEs with TNMP protocol or

22 NEs with SNMP protocol.

LCT allows the execution of the following main functions:

– to open and to display the map for the connection to the NEs

– to set the connection with the NEs, activating such a connection at the map

opening

– to execute, by means of a cyclic polling, the monitoring of the NEs connection andalarm status

– to access to the single NE, that is to load the relevant configuration files and

operating menus

– to configure and to control each single NE, through the relevant operating menu

– to manage the security access (Security) to the NEs, when applicable, that is to

allow the access only to authorized users by means of passwords.

At the map opening, LCT automatically detects the type of the present equipment, if the

relevant plug-in has been installed. If it is present a particular type of radio equipment

and the relevant plug-in is not installed, LCT detects its presence, but it is not able to

recognize it and then to manage it.It is possible to execute the installation of an equipment plug-in also after the installation

of LCT; in this case, if LCT is already running, it is necessary to exit from the program

and then to start-up it again, to allow the loading of the new plug-in.

LCT allows inserting NEs with TNMP EXT (extended TNMP) or SNMP protocol into

a map.

A map of LCT cannot contain NEs with different protocols (TNMP and SNMP).

In order to ensure the compatibility with maps created using old versions of LCT

(versions before LCT V6.0), LCT allows however opening and managing maps

containing NEs with TNMP base protocol or with automatic detection of the TNMP

protocol (TNMP Autodetect).




6-2LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

6.2 User Interface

LCT is provided with a Microsoft Windows typical user interface.

The GUI (Fig. 6.1) consists of the following elements:

– Title bar (par. 6.2.1)

– Menu bar (par. 6.2.2)

– Tool bar (par. 6.2.3)

– Displaying area (par. 6.2.4):

• Map Tree View frame (par. 6.2.4.1)

• NE View frame (par. 6.2.4.2)

• Map View frame (par. 6.2.4.3)

– Status bar (par. 6.2.5)

Fig. 6.1 LCT user interface

It is not possible to run more times at the same time, from a single session of LCT,

the same network Java application program (e.g.: two Alarm lists).

It is not possible to open more sessions of LCT on the same PC.

In order to obtain the best LCT interface visualization, it is suggested to set

Windows XP Style.

Using Windows Classic Style some fields will not be shown correctly.

Screenshot in this manual are indicative

Status bar

NE Viewframe

Title bar

Menu bar

Tool bar

Keys for frameexpansion/closing

Map Viewframe

Keys forframe

expansion/ closing

Map TreeViewframe

Map





6.2.1 Title bar

The title bar always displays the name and the icon of the program.

6.2.2 Menu bar

The menu bar displays the following basic program menus:

– File Menu (par. 6.10)

– Options Menu (par. 6.11)

– Window Menu (par. 6.12)

– Help Menu (par. 6.13)

The menus are of pull-down type.

LCT allows accessing to the menus through shortcut from keyboard; the implemented

fast-access mechanism is the following:

– pressing the key of the underlined letter of a menu together with or after the Alt key,

the corresponding menu directly opens on the menu bar

– pressing only the Alt key, the focus moves to the menu bar and the first menu (File

menu) is selected without being opened; in this situation:

• acting on the Left/Right arrow keys, it is possible to move the selection among

the menus

• pressing the Enter key or one of the two Up/Down arrow keys, the currently

selected menu opens

• pressing the key of the underlined letter of a menu, the corresponding menu

opens

– with a menu open, pressing the key of the underlined letter of menu item, the

corresponding item is directly selected and the associated operation is executed

(command, opening of a submenu, ...); this modality is implemented on all the

pop-up menus of the application.

6.2.3 Tool bar

The tool bar provides some push-buttons that allow the direct execution of a command

without passing through the pull-down menus of the menu bar.

A tooltip window is available on each push-button, indicating the function associated to

the push-button itself.

The following Table gives a description of the available push-buttons.

Tab. 6.1 Tool bar

Icon Description

Colors command of the Options menu (par. 6.11.1)

Field Status command of the Options menu (par. 6.11.2)

Contents command of the Help menu (par. 6.13.1)




6-4LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

6.2.4 Displaying area

The displaying area is a frame structure that includes:

– a side frame subdivided, on its time, in two sub-frames:

• Map Tree View frame (par. 6.2.4.1); it is the upper frame used to display the

tree structure of the map• NE View frame (par. 6.2.4.2); it is the lower frame where the operating menu

for the management of the selected NE is displayed.

– a main frame or map frame (par. 6.2.4.3), pointed out by Map View tab, where the

map and the dialog window are displayed

The main frame and the side frame can be resized in width. Inside the side frame, the

two Map Tree View and NE View frame can be resized in height.

Each one of the two Map Tree View and NE View frames has a title bar, with the name

of the frame and the two following push-buttons:

– Push-button

The push-button allows iconizing the frame; the frame icon is displayed on a

side bar (Fig. 6.2).

The side bar with the frame icons is displayed only if at least a frame is currently

reduced to icon.

To re-open the frame, click on the corresponding icon present on the side bar.

The side frame is closed (Fig. 6.3) if both the Map Tree View and NE View frames

are iconized.

– Push-button

The push-button allows separating the frame from the GUI window; the frame

becomes a mobile and independent window (Fig. 6.4), which can be resized and

moved to any position of the desktop.

If the mobile window is closed, the frame is automatically re-inserted and

re-hooked to the side frame of the GUI window.

Help Wizard command of the Help menu (par. 6.13.3)

Tab. 6.1 Tool bar

Icon Description

Colors command of the Options menu (par. 6.11.1)





Fig. 6.2 Displaying of the iconized frame

Fig. 6.3 Displaying with side frame closed




6-6LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.4 Displaying of mobile frame

Map Tree View Frame

Frame NE View





6.2.4.1 Map Tree View frame

The Map Tree View frame (Fig. 6.5) displays the tree structure of the network; the root

is the current map and the leaves are the single NEs, which are identified by the name

assigned in the map file.

The system represents each object of the tree structure with a specific icon.

A pop-up menu is available on each NE (par. 6.14).

The operations to select the map objects into the Map View frame and into Map Tree

View one are equivalent, because they affect both the frames; the selection of an object

into the Map Tree View causes also the selection of the same object into the map frame

and vice versa.

The selection of a NE causes the detailed displaying of the NE into the NE View frame.

The following operation can be executed by means of a double click on the icon:

– double click on the NE icon:

• commands the opening of the NE and, then, the loading of the operating

menu of NE into the NE View frame; according to the set option, NE is opened

with the highest possible user class or in read-only modality (default option)

• in the Map View frame, the map window containing the NE is brought in

foreground, with the focus on the NE itself

– double click on the map icon: the tree structure of the map expands/collapses inthe Map Tree View.

Fig. 6.5 Map Tree View frame

Tab. 6.2 Map Tree View frame: objects icons

Icon Description

NE icon




6-8LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

6.2.4.2 NE View frame

The NE View frame (Fig. 6.6) displays the management menu of the selected NE, that

contains the menu options of the NE plug-in and the items relevant to the application

programs of NE (if supported by the NE).

The NE menu is a tree menu, whose root is the NE name coupled with the indicator of

summarized severity, composed by a square; the color of the indicator points out the

summarized severity of all the active alarms.

The NE menu is visible and accessible only when the NE has been opened (par. 6.9.4);

on the contrary, the system points out, into the NE frame, only the NE name associated

to the severity indicator. A double click on the icon of a closed NE directly opens the NE,

with the displaying of the login window (par. 6.9.4).

On the NE icon, it is available also a pop-up menu (par. 6.14), that is equivalent to the

one available on the NE icon into the Map View frame and into the Map Tree View frame.

Each node of the NE menu is equipped with a pop-up menu (Fig. 6.7) with the

Expand/Collapse command that allows expanding/closing the node.

Fig. 6.6 NE frame

Fig. 6.7 NE frame: node pop-up menu

6.2.4.3 Map View frame

The Map View frame (Fig. 6.8) displays:

– Map window (par. 6.2.4.3.1)

– Form and dialog windows (par. 6.2.4.3.2)

6.2.4.3.1 Map window

The map window displays in graphic modality the map (Fig. 6.8) that contains the NEs





to manage. Each NE is represented by an icon, which identifies the type of equipment,

under which the name of the NE itself is reported.

The background color of the name of the NE points out the summarized severity of all

the active alarms on the NE.

LCT is provided with the standard maps of connection to the local equipment


On each NE of the map, a pop-up menu (par. 6.14) and a tooltip window (Fig. 6.9) are

available. The tooltip window of a NE displays the IP address of the NE. In case of

disconnected NE, the tooltip window displays the indication of network address not

available.

The selection of a NE issues the displaying with details of the NE into the NE frame.

The selection operations of the NEs into the Map View frame and into the Map Tree

View frame are equivalent, because they affect both the frames; the selection of a NE

into the Map Tree frame causes also the selection of the same element into the Map

Tree View frame and vice versa. A double click on the icon of a closed NE directly opens

the NE, with the displaying of the login window (par. 6.9.4).

The user can associate a background image to the network map (e.g.: a geographical

map with pointed out the places where there are the stations, a block diagram that points

out all the interconnections, ...). Please note that the background images (“.bmp ”, “.gif ”

or “.jpg ” file) of a map is not present into the map file, but the system always recalls it as

an external link at the map opening.

Fig. 6.8 Map View frame

By default, the standard map “LOCALNE.map” contains one NE with the following

configuration:


– IP address: 192.168.255.3

By default, the standard map “LOCALNE_SNMP.map” contains one NE with the


– protocol: SNMP

– IP address: 192.168.255.3

The IP address 192.168.255.3 is the preset address (10.10.10.10, for SRAL XD ).




6-10LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.9 Tooltip window on NE (example)

6.2.4.3.2 Form and dialog windows

The system displays into the map frame all the form and dialog windows that open on

the GUI after any action.

The fields of the form windows relevant to the NEs can be of two types:

– read only: fields concerning the status and alarm signals or not modifiable

parameters

– read-write: fields concerning changeable parameters.

It’s possible to modify the values of the fields, depending on the effective user class used

to access to the NE:

– Read Only: it is possible only to read the values of the fields, but not to change

them

– Read Write: it is possible to change the values of the fields with the exception of

the ones relevant to the windows reserved for the Admin user class

– Admin: it is possible to change the fields of any window.

Usually, it’s possible to execute the following operations on the read-write type fields:

– Selection of a value

Move the mouse on the desired field and click twice. The window Field Editing

(Fig. 6.10) is displayed with a box that lists the available values for the selected

parameter. Move the mouse on the desired value and click for selection; click on

OK button to confirm the selection.

– Data entry (numbers or strings)

Move the mouse on the desired field and click twice; the window Field Editing

(Fig. 6.11) is displayed with a box for the data entry. Move the mouse on the box

and click for selection; use the keyboard to enter the data into the box and click onOK button to confirm the entry.





At the opening of a window, the values to be displayed into the fields are get by the NE.

Some fields can point out, by means of blinking, the modification of their value. It is

possible to stop the blinking through the “F3” push-button.

If the value of a field has not been get by the NE yet, the field can not be modified.

When the value of a field is modified, the request for modification is sent to the NE. Then

the program waits for the NE answer. If the NE rejects the modification, an error

message is displayed. If the field is a numeric type one, the program, before sending the

request for modification to the NE, executes a check on the validity range of the current

parameter. If the value is out of the validity range, an error message is displayed.

A special management characterizes the action windows used to execute some actions

on the NE and the Field Editing windows used for the writing of the fields:

– Field Editing windows (Fig. 6.10, Fig. 6.11)

Each Field Editing window is provided with two push-buttons (OK and Cancel).

It is possible to open only one Field Editing window at a time. Then, when a Field

Editing window has been opened, the program can execute actions on the window

only.

– Action windows (Fig. 6.12)

Every action window is open at the beginning in “reading” mode (unchangeable

fields); two push-buttons are available (Modify and Cancel).

If the current user class for the connection with the NE allows it, clicking on Modify

push-button, the program executes switching of the action window to “writing”

mode (changeable fields); two push-buttons are available for the execution

command and for the interruption of the action (OK and Cancel).

It is possible to open only one action window at a time in “writing” mode for each

NE. Then, when an action window has been opened in “writing” mode, the

possibility to modify the fields belonging to other windows of the same NE is

disabled.

Fig. 6.10 Field Editing window: selection of a value

Fig. 6.11 Field Editing window: data entry




6-12LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.12 Action window

6.2.5 Status bar

The status bar displays messages and information useful for the operator (the meaning

of the menu commands, the status of the program or of the function actually on

progress, the details concerning the fields of the configuration and control windows,

etc...).

When, in the Map View frame, the cursor of the mouse passes over the icon of a NE on

the status bar an information about the connection status with the subject NE is

displayed (Fig. 6.13):

– the current user class for the access to the NE is displayed if the NE is on-line and

open and has the Security enabled

– the status of not connection is displayed (off-line or disconnected) if the NE is not

on-line

– the message “Another Read Write manager is already logged to this NE” is

displayed if another manager is currently connected to NE with exclusive write

permissions (not valid for SNMP equipment).





Fig. 6.13 Status bar: information on the NE connection status (example)

6.3 Security of NE

The Security of NE allows the access to the NE only after the user authentication

through the insertion of the user class and the relevant password.

The NE Security defines the access privileges towards the NE (operation monitoring,

setting/change of the operating parameters and/or of the network ones, ...).

For the NE Security, three user classes are foreseen:

– Read Only: access to the functions in read only modality

– Read Write: access to the functions both in reading and in writing modality,

except for the functions reserved to the Admin user class

– Admin: access to all the functions both in reading and in writing modality.

In case of enabled NE Security, also the Anonymous user class is enabled, that

does not require any password and has the same privileges of the Admin user

class, except for the function relevant to the Security configuration.

The NE Security has to be necessarily enabled:

– more Managers can access at the same time (e.g.: two LCTs)

– if the use of NetViewer is foreseen.


of the Admin users of FTP and Telnet coincides with the password set for the

Admin user class of NE Security.

The alignment of the passwords is ensured by an automatic mechanism: each

change to the password of the Admin user class of the NE Security is applied also

to the password of the Admin users of FTP and Telnet.




6-14LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

The Security configuration (disabling status and password) is specific for each NE and

is stored in the NE.

It is possible to set/change, by means of the NE operating menu, the configuration of the

NE Security only if the user accesses to the NE with the Admin privileges.

When the access to a NE takes place, the login phase is always executed. Into such a

phase, the system asks to the user for specifying the access user class.

In case of NE with disabled Security, it is possible to access to the NE also with the

Anonymous user class that does not require password and has the same privileges of

the Admin user class, except for the functionality of Security configuration. The Security

enabling prevents the connection to a NE of more operators at the same time with the

Admin or Read Write user class, preventing conflicts and configuration errors.

For the equipment, the passwords of the Security of NE, predefined by default, are only

the following ones:

– Admin user class: sysmanager

– Read Write user class: readwrite

– Read Only user class: readonly.

6.4 NE Synchronization

LCT supports the management of two different synchronization modalities:

– the management of synchronization via NE Manager, which allows synchronizing

the NEs on the date and time of the LCT PC

– the management of the equipment which support the synchronization by means of

SNTP protocol.

Synchronization via NE Manager

The synchronization of each NE via NE Manager can be enabled or disabled by LCT orby NetBuilder.

LCT manages the synchronization via NE Manager according to the following modes:

– LCT synchronizes each NE that is directly connected with the LCT itself and for

which the following conditions are present:

• enabled NE synchronization

• Admin/Read Write privileges of LCT on the NE

• NE Security enabled.

– LCT synchronizes the NE on the local time of the LCT PC.

– LCT synchronizes the NE at the connection time. During the connection procedure,

the system does not execute the synchronization if the difference between the LCT

time and the NE one is lower than or equal to 3 seconds.

If the NE Security is disabled, it will get again the previously set passwords when

enabled again.

The NE Security of a SNMP equipment is always enabled and it is not possible todisable it. SNMP equipment allow more than 1 manager to access in RW mode at

the same time.





– LCT synchronizes the NE within 5 minutes from the time when the system changes

the date and time of the LCT PCT.

– First time the synchronization of a connected NE is enabled, LCT immediately

synchronizes the NE; on the contrary, the NE is synchronized at the end of thesynchronization time relevant to the NE (24 hours).

– LCT synchronizes, every 24 hours, all the connected NEs.

– In synchronization procedure, LCT takes into account of the delays inserted by the

network. In fact, for each NE, the Server calculates the time used by a message to

reach the NE and compensates the effective time, by means of the so obtained

value, forwarding to the NE a synchronism time increased by a number of seconds

equal to the half of the time that passes between the forwarding to the NE of a “Get

Request” and the arrival of the corresponding answer from the NE.

SNTP synchronization

On the NEs that support the SNTP synchronization (refer to Customer Release Notes),

LCT allows setting the following SNTP synchronization parameters:

– the IP address of the Time Server

– the wished time zone

– the indication of the daylight saving time.

6.5 Statuses of NE and LCT - NE Connection

The possible connection status of a NE to LCT is one of the following:

– disconnected

– connected

– off-line

– on-line.

As regards the connection status of NE to Server, the following items must be

highlighted:

– Status transitions of NE (par. 6.5.1)

– Management and displaying of the NE status (par. 6.5.2)

The SNTP synchronization and the synchronization via NE Manager are in

alternative.

Over a NE that supports the SNTP synchronization, the operator can choose the

type of synchronization to use: SNTP synchronization or synchronization via NE

Manager.If the SNTP synchronization ia already active on a NE, it is not possible to activate

the synchronization via NE Manager when you execute the login to the NE.




6-16LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

6.5.1 Status transitions of NE

The following diagram shows the NE status transitions:

– At the map opening, all the NEs present in the map are considered disconnected(disconnected status) and LCT tries to communicate with all the NEs.

– All the NEs that communicate correctly with LCT pass to the intermediate

connection status (connected status) while the others remain in disconnection

status (disconnected status).

– When the login is successfully executed from LCT to a NE, NE switches to on-line

status; vice versa if the login fails, NE switches to off-line status.

– LCT tries cyclically an automatic reconnection towards that are in the same

disconnected status. Therefore, if the communication towards LCT (involuntary

disabling status) is restored, a NE automatically changes from the disconnected

status to the connected status.– If for any reason the communication between LCT and NE falls, that ones

automatically switches to the disconnected status.

Fig. 6.14 NE status transitions

communication

NEdisconnected

NEconnected

NEoff-line

NEon-line

Login and profile loading OK

Login and

profileloading failed

Acknowledgement

of NE OK(LCT - NEcommunication)

Loss of

LCT - NEcommunication

Absence of LCT - NE

Loss of

LCT - NEcommunication

Login andprofile

loading OK

Loss ofLCT - NEcommunication





6.5.2 Management and displaying of the NE status

The visualization modality and the management possibility of every NE depends on the

current status:

– disconnected

It is displayed the generic NE icon.

The NE severity indicators are of grey color.

– connected

It is displayed the icon that identifies the equipment type.


– off-line

It is displayed the icon that identifies the equipment type.


– on-lineIt is displayed the icon that identifies the equipment type.

The color of the NE severity indicators points out the effective summarized severity

of all the activated alarms on the NE.

In this condition, the operating menu for the management of the NE is available.

If the connection is set to a NE, whose plug-in is not installed, the icon of “unknown”

equipment is displayed, indicating that this equipment type is not supported by LCT

(Fig. 6.15). In this case if the user opens the NE, only the Warning Message option is

displayed and the tree menu for the NE management is not loaded. Clicking on Warning

Message, a warning message is displayed, signalling that LCT cannot support the NE,

as the corresponding plug-in is not installed and, then, it is necessary to install the

plug-in (Fig. 6.15).




6-18LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.15 NE “unknown”

LCT executes a periodic polling to monitor the connection and alarm status (severity) of

the NE.

The possible severity values for an on-line NE are the following ones:

– normal

– indeterminate

– test

– warning

– minor

– major

– critical.

6.6 Severity Management

LCT supports the management of the alarm severity of NE.

The foreseen severity levels are the following ones:

– Normal: correct functioning condition (on-line condition and alarm absence).

– Not On Line: disconnection condition.

NE “unknown”





– Critical: alarm condition that involves the operation and needs an immediate new

corrective action.

– Major: alarm condition that involves the operation and needs an urgent new

corrective action.– Minor: alarm condition that involves the operation and needs the starting-up of a

corrective action to prevent higher damages.

– Warning: potential alarm condition or potential service prevention, detected before

it can cause effects on the system; the user has to start-up an action for an

additional diagnosis (if it is necessary) and to remove the trouble to prevent that it

can cause more serious fails.

– Indeterminate: alarm condition with indeterminate character that does not need

for the execution of diagnosis or of corrective actions.

– Test: test or manual forcing via software condition.

LCT uses different colors to graphically represent the severity level; a specific color,

which the user can modify as he wishes (par. 6.11.1) is associated to each severity

level.

LCT provides the following information concerning the severity:

– severity of each single alarm active on the NE

– summarized severity of a single NE, that coincides with the alarm with the highest

severity among the ones currently active on the NE.

The modalities of displaying of the summarized severity of NE are the following

(Fig. 6.16):

– background color of the NE name on the NE icon in the map frame

– color of the square-shaped indicator before the NE name in the NE frame.

For the determination of the summarized severity of NE, also the disconnection alarm is

considered.

Fig. 6.16 Indication of summarized severity of NE

6.7 File Transfer Protocol

LCT basically supports, as file transfer protocol with the NEs, the FTP protocol.

The applications of LCT that use the file transfer via FTP are the following:

– Commissioning Report (par. 6.16.3): collection, via XML, of the long period

performances; the application requires the files directly to the NE

– Local History Log (par. 6.16.2): collection, via XML, of the events relevant to therecent history of NE; the application requires the files directly to the NE

The color of the squareindicator points out

the summarizedseverity of NE

The background colorof the NE name pointsout the summarized

severity of NE




6-20LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– FTP Client (par. 6.17.7): upload/download of files from/to the NE; the application

receives information via the FTP Server of the NE, which manages the file

download/upload.

6.8 User Settings and Data Saving

6.8.1 User data saved in the system user profile

By default, all the files created by a user with the LCT applications (log files, report files,

...) are saved in the “LCT ” folder relevant to the system user profile of the user himself:

– “C:\Documents and Settings\<user_names>\Application Data\LCT ” in Microsoft

Windows XP

– “C:\Users\<user_name>\AppData\Roaming\LCT ” in Microsoft Windows Vista.

In detail:

– the files created by means of the following applications:

• Telemeasurement

• Print to file

• Inventory Report

• History Report

• G.821/G.826 performance recording

are saved in the “...\LCT\Rec ” sub-folder

– the files created by means of the Commissioning Report application are saved in

the “...\LCT\Rec\PmComm_Rec ” sub-folder– the files created by means of the Copy NE application are saved in the

“...\LCT\Appl\NCFG_REC ” sub-folder.

6.8.2 User settings saved in the system All Users profile

By default, all the configuration files created by a user with the NetBuilder (map files and

relevant background bitmaps) are saved in the “LCT ” folder relevant to the system All


– “C:\Documents and Settings\All Users\Application Data\LCT ” in Microsoft

Windows XP

– “C:\ProgramData\LCT ” in Microsoft Windows Vista.

In detail, the map files are saved in the “...\LCT\Map ” sub-folder, while the background

bitmaps are saved in the “...\LCT\Background ”.

6.9 Start-up of LCT and Login to NE

To run LCT and, then, access to the NEs to manage, the following operations must be

executed:

– Opening of the GUI of LCT (par. 6.9.2)– Opening of the map (par. 6.9.3)





– Opening of NE (par. 6.9.4)

LCT includes also the LCTStart application (par. 6.9.1), which provides an additional

modality to create and access the map with respect to the standard one of LCT.

To allow the start-up and the operation of LCT, the following conditions are required:– active connection (on F interface or on Ethernet interface) between LCT PC and

local NE

– Java Runtime Environment 1.6.0 installed.

6.9.1 LCTStart application

The LCTStart application allows automatizing and speeding up the access to the map

(avoiding the use of NetBuilder), as it allows the automatic creation of the map in the

following cases:

– when a NE locally connected to the LCT PC is detected

– when a NE research is executed (“Find NE” functionality) starting from a NE with

known IP address.

The LCTStart application can manage the NEs connected to the LCT PC for Local

Management via F interface (serial RS-232) and/or Ethernet interface.

6.9.1.1 Start-up of LCTStart

The LCTStart application is managed by the LCT Services Manager service, which is

installed as service of Microsoft Windows with automatic start-up modality (Fig. 6.17).

The LCT Services Manager service is run as background process on the start-up ofMicrosoft Windows.

When the LCT Services Manager service is running, the icon of the LCTStart application

is present in the tray area of the desktop (Fig. 6.18).

On the desktop the RunLCTStart command is available for the manual start of the

LCTStart application (Fig. 6.19); this command must be used only if, for any reason, the

LCTStart application is stopped.




6-22LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.17 LCT Services Manager service

Fig. 6.18 Icon of LCTStart running

Fig. 6.19 RunLctStart command

6.9.1.2 “auto.map” map

The map automatically created by the LCTStart application (Fig. 6.20) is stored in the

“auto.map ” file of the default “Map ” folder:

– “C:\Documents and Settings\All Users\Application data\LCT\Map ” in Microsoft

Windows XP– “C:\ProgramData\LCT\Map ” in Microsoft Windows Vista.

The “auto.map ” file is generated the first time the LCTStart application automatically

creates a map.

Only the last map created by the LCTStart application is kept in memory; when the

LCTStart application creates a new map, the “auto.map ” file is overwritten.

The “auto.map ” map contains at most NEs:

– the found NE (local NE or starting NE in case of “Find NE” functionality)

– the possible “radio far-end” NEs connected to the found NE.

Icon of LCTStart running





“Radio far-end” NEs stand for the NEs connected to the subject NEs via radio interface.

The research of the “radio far-end” NEs is possible only for equipment with TNMP EXT

protocol that supports the auto-discovery functionality (refer to Customer Release

Notes).

Fig. 6.20 Example of “auto.map” map

6.9.1.3 LCTStart user interface

The LCTStart application has a pop-up menu (Fig. 6.21) that opens clicking on the right

button of the mouse on the icon of the application.

The pop-up menu contains, by default, the following commands:

– Enable

Enables the functionality for the automatic creation of the map for locally connected

NE. By default this functionality is enabled and then, the corresponding command

in LCTStart is inactive.

– Disable

Disables the automatic creation of the map for locally connected NE.This

command is active by default.

– Find NE

Starts the functionality for the automatic creation of the map by means of the

research of NE starting from a NE with known IP address. In case of FlexiPacket

NE, the FlexiPacket station layout is applied.

– About

Displays the current version of the LCTStart application (Fig. 6.22).

Moving the cursor of the mouse over the icon of the LCTStart application, a tooltip

window opens (Fig. 6.23) which points out the activation status of the functionality of

automatic creation of the map for the locally connected NE.

When the GUI of LCT is open without a loaded map, the active commands of LCTStartare About and Disable (or Enable).




6-24LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

When a map is open on the GUI of LCT, all the functionalities of the LCTStart application

are disabled and the commands of the pop-up menu are inactive, except for the About

command.

Fig. 6.21 LCTStart: pop-up menu

Fig. 6.22 LCTStart: About window

Fig. 6.23 LCTStart: tooltip window for the indication of the activation status

Enabled

Disabled

6.9.1.4 Automatic creation of the map for locally connected NE

When the LCTStart application detects a NE locally connected to the LCT PC, it:

– searches the NEs adjacent to the local NE and automatically creates the new

“auto.map ” map

– displays a message to notify that the local NE is ready for the connection from LCT

(Fig. 6.24)





– adds the IP address of the local NE to the pop-up menu (Fig. 6.25).

In this case, if the GUI of LCT is not open, clicking on the IP address of the local NE or

via a double click on the icon of the LCTStart application, you issue the directly opening

of the GUI of LCT on the new created map.

Fig. 6.24 LCTStart: message of NE locally connected

Fig. 6.25 LCTStart: pop-up menu in case of locally connected NE

6.9.1.5 “Find NE” functionality

To create automatically a map by means of the search of a NE with known address, it

is necessary to proceed in the following way:

– Select Find NE in the pop-up menu.

In the window that opens (Fig. 6.26) specify the IP address of the starting NE and

click on OK to start the research.

– If the NE is found, also the “radio far-end” NEs are searched too and the new

“auto.map ” map is automatically created.

When the starting NE is FlexiPacketHub equipment, each element of the station is

searched too.

In this case:

• if the GUI of LCT is closed, it is automatically opened with displayed the new

created map

• if the GUI of LCT is already open, it stays on the current status (the new

created map is not displayed).

– If the specified NE is not found, an error message is displayed (Fig. 6.27) and no

new map is created.

– If the specified IP address refers to FlexiPacket Hub or FlexiPacket FirstMile the

created "auto.map" includes all the FlexiPacket NEs directly and/or remotely

connected to the IDU the Find NE is applied to. Further more the distribution of the

NEs is that described in par. 7.5.7.2, that is FlexiPacket station layout is applied to

"auto.map" too.

Fig. 6.26 Find NE: setting of the starting NE




6-26LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.27 Find NE: message of NE not found

6.9.2 Opening of the GUI of LCT

To open the GUI of LCT, it is necessary to execute the following shortcut (Fig. 6.28):

Start → Programs → Nokia Siemens Networks → LCT

The opening of LCT GUI occurs after the displaying of a splash screen (Fig. 6.29), which

automatically closes after same seconds.

By default, the GUI of LCT is opened without any map loaded (Fig. 6.30).

The GUI of LCT can be automatically opened also from the LCTStart application; in this

case, the new created “auto.map ” map is automatically opened (par. 6.9.1).

Fig. 6.28 LCT: shortcut to open the GUI of LCT

On the first start-up of the GUI of LCT, it is necessary to wait for some seconds

before the window of the GUI is displayed.





Fig. 6.29 LCT: splash screen

Fig. 6.30 GUI of LCT without open map

6.9.3 Opening of the map

.

The opening of the map causes (Fig. 6.31):

The maps of LCT must satisfy the following requirements:

– to contain at most three NEs with TNMP protocol or at most 22 NEs with

SNMP protocol

– not to contain sub-maps

– not to contain NEs with different protocols (NEs with TNMP protocol and NE

with SNMP protocol)

– not to have a map Security.




6-28LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– the displaying of the map tree structure in the Map Tree View frame

– the displaying of the map in graphic modality in the Map View frame.

At the map opening, LCT tries to connect to all the NEs to setup the connection

(par. 6.6):

– if the connection fails, an icon showing that the NE is disconnected is displayed

– if the connection is successful, LCT tries to recognize the radio equipment type:

• if the recognition is successful, the relevant configuration file is loaded and a

pre-defined icon showing the radio equipment type is displayed

• if the recognition fails (for instance: radio equipment not supported by LCT),

the system displays an icon of “unknown” equipment showing that the radio

equipment type is not supported.

If, for any reason, the communication between LCT and NE is interrupted, the system

automatically disconnects the NE.

LCT cyclically executes an automatic connection attempt towards the NEs that are in

disconnected status. It is always possible to know the cause of the disconnection for a

NE. Positioning the cursor on the icon of a disconnected NE, a message is displayed

into the status bar showing the reason for the disconnection.

LCT executes a periodic polling to monitor the connection status of the NE.

Fig. 6.31 LCT with open map

The probable causes of the not executed detection concerning the type of radio

equipment can be the following ones:

– LCT version that does not support the type of radio equipment

– incompatibility between the LCT version and the one of the equipment

plug-in

– absence or wrong installation of the equipment plug-in.





6.9.4 Opening of NE

The manual command to open a NE (Fig. 6.32) can be executed on any frame (Map

View frame, Map Tree View frame, NE View frame), selecting Open in the pop-up menu

of the NE (par. 6.14) or by a double click directly on the NE icon.

Fig. 6.32 Command for NE opening

When the opening of a NE is commanded, the login window is displayed (Fig. 6.33),

where it is necessary to specify the user class to access to the NE and the relevant

password:

– if the Security of NE is enabled, it is possible to login to the NE with one of the

following user class:

• Read Only

• Read Write

• Admin

– if the Security of NE is disabled, you can login to the NE also via the Anonymous

user class, which does not require the password and has the same privileges of the

Admin user class, except for the functionality of Security configuration.

In case of connection with writing permissions from LCT to a NE via F interface,

if you stops the connection without closing the NE, the NE effectively releases the

connection of the user with writing permissions only after a timeout of some

minutes (the value of the timeout depends on the type of equipment) and, then, a

new access with writing permissions to the NE menu is possible only at the expiry

of the timeout; in case of attempt of access with writing permissions to the NE

before the expiry of the timeout, the access is denied and the message of “user

with writing permissions already connected to NE” is displayed.




6-30LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.33 Login window

NE Security enabled

NE Security disabled

In the login window the following information is displayed:

– enabling status of the NE Security

– a message to warning that an user with write permissions is already connected to

NE.

The login phase consists in a series of operations that allow accessing to the NE and

opening the menu for the management of the NE on the basis of the System Type and

of the Equipment Type of the NE.





Fig. 6.34 Login phase in progress

If the login fails, an error message is displayed and the NE remains in off-line status.

Fig. 6.35 Window for denied access to NE

If the login is successful, the NE is opened and the menu for the management of the NE

is loaded in the NE frame.




6-32LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.36 Login succeeded and NE open

Connection with priority

The possibility to connect from LCT with priority respect to other supervision systems

(e.g.: NetViewer) is foreseen.

The connection with priority regards the possibility, for a LCT user, to connect with writepermissions to a NE, which an user of another supervision system (e.g.: NetViewer) is

already connected to with write permission, forbidding to this one the writing

permissions on the NE.

The connection with priority is possible only with NEs for which the functionality is

supported and enabled.

The connection with priority foresees a configurable timeout (inactivity interval), after

which the LCT connected with priority is automatically disconnected.

The timeout allows avoiding that a LCT remains connected with priority for long time to

the NE without reason (e.g.: due to oblivion) and that, as consequence, forbids the

connection to the NE with write permissions to other LCTs (which then could not use the

functionality of connection with priority) and/or other supervision systems.

The login window is displayed with different layout depending on the user class of login

and on the support/enabling of the function of connection with priority; the followingsituations can occur:

The connection of LCT with priority can be applied only to the NE with equipment

SVR and plug-in version that implement the support of this functionality (refer to

the Customer Release Notes).

The connection with priority to a NE is meaningful only in case of Security

enabled; therefore the connection with priority with Anonymous user class is not

a foreseen situation.

In case of Security disabled, it is necessary to avoid the situation of contemporary

connection to a NE of more users with write permissions.





1. Admin/Read Write user class and functionality of connection with priority supported

by the NE and enabled

If no user is already connected to the NE with write permissions, in the login

window the fields relevant to the connection with priority are inactive; in this case it

is possible to execute the connection with write permission to the NE and a request

of connection with priority has no meaning.

If, differently, an other user with writing permissions but without priority (e.g.: user

of NetViewer connected with Admin or Read Write user class) is already connected

to the NE, in the login window the Priority required check-box of request of the

connection with priority is active. In this case, it is necessary to force a connection

with priority to connect to the NE with write permission, which is accepted by the

NE. Then, the NE sends a notification message to the first user and waits for about

15 seconds in order to allow to the first user disconnecting and, possible,

reconnecting with Read Only user class; once elapsed the waiting period, the NE

automatically stops the connection with the first user if this one results connected

yet to the NE with writing permissions.

Fig. 6.37 Login window: Admin/Read Write user class and functionality of connection with

priority supported and enabled

No user connected to the NE with write priority

If an user of another LCT is already connected to the NE with writing permissions,

it is not possible to force, from LCT, the connection with priority (in the window

of login, the fields relevant to the functionality of connection with priority are

inactive).

Note that a connection to the NE with writing permissions from LCT is always

seen as a connection with priority.

The NE refuses a request of connection with priority if other five users are already

connected to the NE.




6-34LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

One user already connected to the NE with write permission

If the Priority required check-box is selected, the Priority Timeout entry-box

activates, allowing the setting of the inactivity timeout, after which the LCT

connected with priority will be automatically disconnected.

Fig. 6.38 Login window: selection of connection with priority

The timeout is expressed in hours and, by default, a timeout of 1 hour is set and

the maximum value is 48 hours.

If the value of timeout is not correct (setting of a value greater than 48 hours or

typing of not numeric characters), an error window is displayed when the request

of connection with priority is confirmed.

Fig. 6.39 Error window for incorrect value of timeout

The confirmation for the connection with priority is always required. When an user

with write permissions executes from LCT a login with priority request, a warning

window is displayed, in order to inform that the currently connected other user with

write permission is going to be disconnected and then will loose his permissions.





Fig. 6.40 Window of confirmation of the connection with priority

2. Read Only user class and functionality with priority supported by the NE and

enabled

In the login window, the fields relevant to the connection with priority are inactive,

as the possible request of a connection with priority by an user with read only

permission is not meaningful.

Fig. 6.41 Login window: Read Only user class and functionality of connection with priority

supported and enabled

3. Functionality of connection with priority not supported by the NE or supported butnot enabled

In the login window, the fields relevant to the connection with priority are masked.

In this case, if an user is already connected to the NE with write permission, from

LCT only the connection with Read Only user class is possible.

Fig. 6.42 Login window: functionality of connection with priority not supported or

supported but disabled

Synchronization via NE Manager

In the login window, the Synchronization check-box is available for the management

of the synchronization via NE Manager on the NE (par. 6.4). There can be the following

situations:




6-36LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– Synchronization check-box active and selected: the activation of the

synchronization via NE Manager of the NE is explicitly required; in this case, the

NE is synchronized only if you have the sufficient rights for the synchronization

(Read Write or Admin privileges) (ex.: with the Synchronization check-box

selected and login with the Read Only user class, the NE will not be synchronized).

– Synchronization check-box active and not selected: the activation of the

synchronization via NE Manager of the NE is not required; in this case, if the NE

supports the SNTP synchronization, it is however possible to activate the SNTP

synchronization by means of the plug-in forms

– Synchronization check-box inactive and not selected: it is not possible to require

the activation of the synchronization via NE Manager of the NE, because on the NE

the SNTP synchronization is already active (situation possible only if the NE

supports the SNTP synchronization).

6.10 File Menu

File menu (Fig. 6.43) allows opening and closing a map and exiting from LCT.

File menu has the following options:

– Open Map (par. 6.10.1) – Close Map (par. 6.10.2)

– Open auto.map (par. 6.10.3)

– Exit (par. 6.10.4)

The name of the last opened maps are displayed between the Close Map and Exit

command, in order to allow a fast selection of the maps themselves.

Fig. 6.43 File menu

6.10.1 Open Map

The Open Map command allows opening the map of LCT (Fig. 6.44); the map files have

“.map ” extension.

From LCT, it is possible to open only one map at a time.

By default the map files are saved in the “Map ” folder reachable an accessible to alla

users:

By default the “Synchronization” check-box is selected if the synchronization via

NE Manager of the NE is enabled by NetBuilder. Vice versa, the “Synchronization”

check-box is, by default, not selected.





– “C:\Document and Settings\All Users\Application Data\LCT\Map ” in Microsoft

Windows XP

– “C\ProgramData\LCT\Map ” in Microsoft Windows Vista.

An error message is displayed in the following cases:

– if the map you wish to open contains more NEs than the maximum allowed

number: at most three NEs with TNMP protocol or at most 22 NEs with SNMP

protocol (Fig. 6.45)

– if the map you wish to open contains NEs with different protocols (Fig. 6.46): NEs

with TNMP protocol and NEs with SNMP protocol

– if the map already contains sub-maps (Fig. 6.47)

– if the map is empty and then it does not contain any NE (Fig. 6.48).

These cases can occur when you attempt to open, from LCT, maps created by means

of the NetBuilder tool from other supervision systems (e.g.: Cell LCT or old versions ofNetViewer).

The Open Map command is active only when no map is open.

Fig. 6.44 Window for Open Map command

Fig. 6.45 Error message for map containing too many NEs

The maps of LCT must satisfy the following requirements:

– to contain at least one NE

– to contain at most three NEs with TNMP protocol or at most 22 NEs with

SNMP protocol

– not to contain sub-maps

– not to contain NEs with different protocols (NEs with TNMP protocols and NE

with SNMP protocol)

– not to have map Security.




6-38LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.46 Error message for map containing NEs with different protocols

Fig. 6.47 Error message for map containing sub-maps

Fig. 6.48 Error message for empty map

6.10.2 Close Map

The Close Map command allows closing the currently used map.

The closure of the map causes the disconnection of the NEs.

A confirmation for the closure of the map is required (Fig. 6.49), as this operation

involves the disconnection of the NEs.

The Close Map command is active only when a map is open.

Fig. 6.49 Window for the confirmation of the map closing

6.10.3 Open auto.map

The Open auto.map command allows opening directly the map created by the LCTStart

application (“auto.map ” file of the “Map ” folder).

For the LCTStart application, the following modalities are foreseen for the creation of a

map:

– automatic creation of a map when a NE locally connected to the LCT PC is

detected

– creation of a map via research of the NEs starting from a NE with known IP address

(“Find NE” functionality).

Only the last map created by the LCTStart application is stored in memory; when the

LCTStart application creates a new map, the “auto.map ” file is overwritten.





The Open auto.map command opens always the current “auto.map ” file, which is the

last map created by the LCTStart application.

The Open auto.map command is inactive if the “auto.map ” map file is not present in the

“Map ” folder.

6.10.4 Exit

The Exit command allows exiting from LCT. When a map is open, a confirmation for the

exit from LCT is required (Fig. 6.50). The Exit command is always active.

Fig. 6.50 Window to confirm the exit from LCT

6.11 Options Menu

The Options menu (Fig. 6.51) allows setting the modality to visually signal the status

and the event in the GUI window of LCT.

The Options menu has the following options:

– Colors (par. 6.11.1)

– Field Status (par. 6.11.2)

Fig. 6.51 Options menu

6.11.1 Colors

The Colors option allows displaying and specifying the colors used by LCT for the status

and fault signals in the different graphic symbols. The Color Selection window(Fig. 6.52) for the management of the colors, which opens after the selection of the

Colors option, displays the current configuration of the color associated to the severity

levels managed by LCT; two proper columns (Field Sample and Icon Sample) show

the displaying layout of the colors for the fields and the icons. It is possible to modify the

color associated to each severity level. The following table reports the default

pre-defined configuration of the colors associated to the severity levels.




6-40LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

To change the current configuration of the colors, execute the following procedure:

– In the Color Selection window, double click on the box of the color you wish to

change; the Color window (Fig. 6.53) opens to set the color.

The Color window provides the following three different modes for the setting of

the colors:

• Swatches tab: the user can select the desired color on the displayed sample

color palette

• HSB tab: the user can set the desired color according to the HSB scheme; the

system always reports the correspondence into the RGB scheme of the set

color according to the HSB scheme

• RGB tab: the user can set the desired color according to the RGB scheme.

Click on OK to confirm the setting of the color.

– Change eventually other colors executing again, for each color to change, theoperations pointed out in the previous step.

– Exit from the Color Selection window, clicking on OK button to apply and activate

the new configuration of the colors.

It is always possible to reset the default configuration of the colors clicking on Default

into the Color Selection window.

The OK push-button allows closing the Color Selection window and saving the made

changes in permanent way.

The Cancel push-button allows closing the Color Selection window without having

saved the made changes, which are lost.

Into the RGB scheme, each color can be get by the combination of the three main color

components: Red, Green and Blue. According to the RGB scheme, each type of every

one of the three main colors is represented by a number ranging from 0 up to 255. For

instance, the black color is represented by the RGB value “0 0 0” (R=0, G=0, B=0), while

the white color is represented by the RGB value “255 255 255” (R=255, G=255, B=255).

The RGB scheme can represent more than 16 millions of different colors. RGB is an

additive scheme because red, green and blue are additive colors (e.g.: the white color

is created by mixing red, blue and green). HSB means Hue, Saturation and Brightness.

According to this scheme, every color is represented by three numbers. The first number

is the hue; its value ranges from 0 up to 360 degrees. Each degree represents a different

color. At 0 (or 360) degrees, there is the red color and then, at the increasing of the

degrees, there are the other colors (for instance the yellow is at 120 degrees, the green

at 180 degrees and the blue at 240 degrees) up to the magenta. In such a way, it ispossible to represent all the possible colors

Tab. 6.3 Default configuration of the colors associated to the severity level

Severity Color

Not On Line grey

Indeterminate white

Normal green

Test blue

Warning yellow

Minor orange

Major red

Critical magenta





Fig. 6.52 Color Selection window

Fig. 6.53 Color window

“Switches” tab

“HSB” tab




6-42LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

“RGB” tab

6.11.2 Field Status

The Field Status command allows specifying the strings of special characters to be

used to signal the error statuses of the fields relevant to the parameters into the NE

windows. Into the Field Status Display Selection window (Fig. 6.54), that is opened

using the Field Status command, it is possible to select the string to associate to each

field status. Click on the box of each field status to display the list of the available strings.

It is always possible to reset the default configuration of the signalling strings relevant to

the field error status clicking on Default.

The following Table shows the default configuration of the strings for the signalling of the

field error statuses.

The OK push-button allows closing the Field Status Display Selection window and

saving the made changes in permanent way.

The Cancel push-button allows closing the Field Status Display Selection window

without having saved the made changes, which are lost.

Fig. 6.54 Field Status Display Selection window

Tab. 6.4 Default configuration of the error statuses of the fields

Field status String

Generic error ############

Not ready

Not configured ------------

Unknown ????????????

Out of range ////////////





6.12 Window Menu

Window menu (Fig. 6.55) provides the following commands for the management of the

windows open into the map frame:

– Cascade (par. 6.12.1)

– Close All (par. 6.12.2)

– Iconize All (par. 6.12.3)

– Move Map to Top (par. 6.12.4)

– Move Map to Bottom (par. 6.12.5)

Fig. 6.55 Window menu

6.12.1 Cascade

The Cascade command manages all the open windows over-placing and displacing

them, in such a way to let visible the menu bar of each window; the current by selected

window is placed in foreground.

This function is inhibited when the number of the open windows is too high; in fact, in

this case, the function would be really not usable.

6.12.2 Close All

The Close All command closes all the open windows, except for the network map

window.

6.12.3 Iconize All

The Iconize All command iconizes all the open NE windows and orders them starting

from the lower left-hand corner.

6.12.4 Move Map to Top

The Move Map to Top command allows bringing the window of the network map in

foreground, in front of all the other open windows.

6.12.5 Move Map to Bottom

The Move Map to Bottom command allows bringing the window of the network map in

background behind all the other open windows.




6-44LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

6.13 Help Menu

Help menu (Fig. 6.56) allows displaying the useful information and instruction

concerning and the using modes of LCT and of the plugs-in for the management of NEs.On the windows, the help is a context-sensible, that is pressing the "F1" push-button,

the help directly opens on the page of the topic relevant to the current window.

The Help menu provides the following options:

– Contents (par. 6.13.1)

– Using Help (par. 6.13.2)

– Help Wizard (par. 6.13.3)

– About (par. 6.13.4)

Fig. 6.56 Help menu

6.13.1 Contents

The Contents command runs the help system that contains the help of LCT and the

ones of the installed equipment plugs-in.

6.13.2 Using Help

The Using Help command allows displaying information concerning the help itself.

6.13.3 Help Wizard

The Help Wizard command allows opening the step-by-step procedure for the line-up

of the equipment.

6.13.4 About

The About command allows displaying information concerning the currently used

version and build of LCT (Fig. 6.57).





Fig. 6.57 About Local Craft Terminal window (example)

6.14 Pop-Up Menu of NE

The pop-up menu of NE (Fig. 6.58) can be activated clicking with the right button of the

mouse on the icon of the NE and has the following options:

– Open (par. 6.14.1)

– Close (par. 6.14.2).

Fig. 6.58 Pop-up menu of NE

6.14.1 Open

The Open command allows opening the NE and loading the tree menu for the NE

management into the NE View frame. The Open command is active if the NE is closed

and connected (NE in connected or off-line status).

It is possible to command the opening of a NE also by a double click directly on the icon

of a NE in any frame (Map View frame, Map Tree View frame, NE View frame).

The opening of the NE is an operation controlled by the Security of NE (par. 6.9.4); whenthe opening of a NE is commanded, the login window is always displayed, where it is

necessary to specify the user class to access the NE.

6.14.2 Close

The Close command allows closing the NE.

This operation closes all the NE configurated and control windows and removes the

operating menu from the View frame.

The Close command is active only if the NE is open (NE on-line) and it is available only

for Map View frame and NE View frame.




6-46LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

6.15 Pop-Up Menu of Window

Some windows also provide option to export the information to text file(.txt) and csv

file (.csv); in these windows a pop-up menu is available (Fig. 6.59) containing the Printto file command.

The user can open the window pop-up menu clicking through the mouse R.H.

push-button inside the application window or inside a window for the

control/configuration of a NE.

Fig. 6.59 Window pop-up menu

To Print to file option allows to record on a file the information shown in the current

window (with path and name) (Fig. 6.60).

The Print to file command does not execute a simple hard-copy of the window; in fact,

while into the window the program displays a short name of the alarms and of the

configuration parameters, it points out into the file the corresponding descriptions

(extended names) recorded by means of Print to file.

If a file with the same name already exists into the destination folder, the system asks

to confirm the over-writing of the existing file (Fig. 6.61).

After its creation, the file is automatically opened, for its displaying and printing, using

the base editor (Notepad or WordPad) of the system (Fig. 6.62).

If no data to record is available in the Print to file command, a warning message

(Fig. 6.63) is displayed instead of the window for the file selection.

The window pop-up menu is not present on the action windows and on the Field

Editing windows.

The “Print to file” command is present only on the windows for which the

recording to file of the displayed information is foreseen.

By default, the text files are saved in the “...\LCT\Rec ” folder of the system user

profile:

– “C:\Documents and Settings\<user_name>\Application Data\LCT\Rec ” in


– “C:\Users\<user_names>\AppData\Roaming\LCT\Rec ” in MicrosoftWindows Vista.

The “Print to file” command is not available in the windows of the applications

that implement the recording to file of reports or logs (History Report, Local

History Log, report of inventory data, ...).





Fig. 6.60 Print to file: file selection

Fig. 6.61 Print to file: file over-writing confirmation

Fig. 6.62 Print to file: file example

Fig. 6.63 Print to file: file example




6-48LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

6.16 Applications of NE

LCT implements in the menu of each NE the following applications:

– History Report (par. 6.16.1)

– Local History Log (par. 6.16.2)

– Commissioning Report (par. 6.16.3)

– Alarm List (par. 6.16.4)

– Services (par. 6.16.5)

The applications available for a NE depend on (refer to Customer Release Notes):

– the equipment type

– the equipment SVR

– the version of the plug-in for the equipment management.

6.16.1 History Report

The History Report application (Fig. 6.64) allows executing the recording on file of theevents (alarms, status changes, ...) relevant to the NE operation.

The report file lists all the events occurred on the NE in the period between the start and

the end of the recording.

The recordings are saved to file to allow a possible post-processing; it is possible to use

any text editor to open a recording file and display the recorded events.

The Last push-buttons allows displaying by means of the basic system editor (WordPad

and Notepad) the report file of the last executed recording.

To prevent troubles during the editing of the writing fields of the NE application

programs (History Report, Performance Report, ...), it is necessary to set the

language of the currently used keyboard according with the language set in

Regional Options of Microsoft Windows; as an alternative, it is advisable to install

only the keyboard of the same language set in Regional Options of MicrosoftWindows, avoiding the installation of more keyboards with different languages.

Into the recording file, the system signals, by means of a proper string, the event

that has caused the closing of the recording:

– NE x.x.x.x. DISCONNECTED:

interruption of the recording for NE disabling/disconnection

– STOP BY USER: stop the recording caused by manual command executed

by the operator

– STOP: automatic closing of the recording at the end of the set recording

time.





Fig. 6.64 History Report (example)

The procedure to execute the History Report is the following one:

– Run the History Report tool from plug-in of NE.

– The History Report window opens (Fig. 6.65). Click on Browse and specify the

name of the file and the relevant path where save the report (Fig. 6.66).

– Set the Max buffer lenght. This value sets the maximun number of rows shown in

the history report for each NE.

– Set the start (Initial Time) and stop (Stop Time) date and time for the recording.

The following conditions must be respected:

• start date and time of recording must be previous to the end date and

time of recording

• the end date and time of recording must be later than or equal to currentdate and time of PC.

To facilitate the insertion of the date, a calendar is suggested subdivided in months,

from which it is possible to directly select the wished date (Fig. 6.67). The field for

the insertion of the date is however always editable

The Now push-button allows setting automatically, as start date of recording, the

current date and time of PC.

– Start the recording clicking on Start (Fig. 6.65). If a file with the same name already

exists in the destination folder, the overwriting of the existing file is required

(Fig. 6.68).

The Start push-button deactivates while the Stop and Show push-buttons become

active (Fig. 6.70); furthermore, to signal the status of recording in progress, a greenlittle square is displayed on the NE icon (Fig. 6.71).

By default, the history report files are saved in the “...\LCT\Rec ” folder of the

system user profile:



– “C:\Users\<user_name>\AppData\Roaming\LCT\Rec ” in Microsoft Windows

Vista.

By default, the system assigns, as name of the destination file of the report, the

NE name plus the extension “.hsy ”. If the NE name contains some special

characters that can not be used into the names of files and/or folders of Microsoft

Windows, it is necessary to change the name of the destination file (e.g. removing

all the special characters). For instance, the special characters that can not be

used into the names of files and/or folders of Microsoft Windows are the following

ones:

\ / : * ? “ < > |




6-50LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– During the recording phase, it is possible to execute the following operations:

• Stop of the recording in progress

It is always possible to stop the recording in progress clicking on Stop. The

initial status is restored (Start push-button active and Stop and Show

push-buttons inactive).

• Displaying of the line of the recording in progress

Clicking on Show, it is possible to open the event table for the displaying of

the line of the recording in progress (Fig. 6.72); the push-button changes from

Show to Hide. In the event table, the events are reported in table format as

soon as they are recorded, included the events of start and stop of recording.

The following information is recorded for each event:• #Evt: row progressive index

• Date & Time: date and time of the event with reference to the NE date

and time

• Event Description: description of the event.

It is possible to display the events in alphabetic/numeric increasing ( ) or

decreasing ( ) order for each column, clicking on the column heading.

Clicking on Hide the event table closes; the push-button changes from Hide

to Show.

– At the end of the recording period, the initial status is automatically restored (Start

push-button active and Stop and Show push-buttons inactive).

Clicking on Last, it is possible to display the last report file of the recording

(Fig. 6.73) using the basic system editor (WordPad or Notepad); if no report file is

present, an error message is displayed (Fig. 6.74).

Fig. 6.65 History Report: starting window (example)

If the start and stop date and time are not congruent, an error window is displayed

(Fig. 6.69) and the recording does not start.

History Report application remains in recording status for all the set interval even

if the NE disconnects. Therefore, if NE reconnects before the end of the recording,

the History Report application restarts to display and record the events.





Fig. 6.66 History Report: selection of the output file (example)

Fig. 6.67 History Report: setting of date and time (example)

Fig. 6.68 History Report: confirmation of the file overwriting (example)

Fig. 6.69 History Report: invalid date and time (example)




6-52LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.70 History Report: recording in progress (example)

With event table closed

With event table opened

Fig. 6.71 History Report: graphic symbol of the recording in progress (example)

Fig. 6.72 History Report: event table (example)

Symbol of NE withrecording in progress





Fig. 6.73 History Report: report file (example)

Fig. 6.74 History Report: report file not found (example)

6.16.2 Local History Log

The Local History Log application (Fig. 6.75) allows recovering and saving to file the log

of the events relevant to the recent history of the NE.

The Controller of a NE keeps in volatile memory the queue of the most recent eventsoccurred on the NE. The event queue has a size of maximum 4000 events and it is

managed in cyclic modality; once reached the maximum size of 4000 events, the

addition of a new event causes the deletion of the oldest event.

The event queue is deleted in the following cases:

– start-up of NE

– reset of NE

– change of the System Type of NE.

The transfer of the event queue from NE to LCT is made via FTP protocol ( par. 6.7),

using a compressed XML file, that is created on-fly by the NE when the request from

LCT arrives.

The event for the change of the System Type is not available in the event queue,

as this event causes the deletion of the event queue.




6-54LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.75 Local History Log (example)

The procedure for the execution of the Local History Log is the following one:

– Run from plug-in of NE the Local History Log tool.

– The Local History Log window opens (Fig. 6.76).

Click on Start to transfer via FTP the events stored on the NE.

It is always possible, in any moment, to stop the transfer of the event queue and

close the Local History Log application clicking on Close.

During the transfer phase, the Start push-button is inactive (Fig. 6.77).

– At the end of the transfer phase, in the Local History Log window (Fig. 6.78) the

events contained in the event queue of the NE (max. 4000 events) are displayed

in table format.

For each event, the following information is displayed:

• #Evt: row progressive index

• Date & Time: date and time of the event with reference to the NE date and

time

• Event Description: description of the event.

It is possible to display the events in alphabetic/numeric increasing ( ) or

decreasing ( ) order for each column, clicking on the column heading.

– Click on Show to display the log (Fig. 6.79) using the basis system editor

(WordPad or Notepad) and then save the log to file with the wished name.

Fig. 6.76 Local History Log: starting window (example)

The saving to file of the log must be executed by means of the editor used to open

the log.





Fig. 6.77 Local History Log: transfer in progress (example)

Fig. 6.78 Local History Log: log displaying (example)

Fig. 6.79 Local History Log: log file (example)




6-56LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

6.16.3 Commissioning Report

The Commissioning Report application (Fig. 6.80) allows displaying and saving to file

the report of the measures of the long period performances.

The measures of the long period performances are generally enabled and collected for

maintenance purposes during the execution of commissioning tests.

The long period performances are made by a set of 192 consecutive quarter intervals of

performance monitoring (performance G.821/G.826 like, RSPI, RPS).

The measures of the long period performances are stored in the non volatile memory of

the Controller of the NE.

Two different recording modalities of the long period performances are possible:

– “From Start Time” modality

Starting from the starting date and time of the recording (“Start Time”), which is

manually set, 192 consecutive quarter intervals are stored; when the last one of the

192 intervals is recorded, the recording automatically stops and the file that collects

the performance measures is created.

– “Last Quarters” modality

Starting from when it is enabled and until i t is disabled, there is the continue storing

of the last 192 quarter intervals; once reached the maximum size of 192 intervals,

the storing of a new interval causes the deletion of the oldest interval.

The file that collects the performance measures is created on-fly when the request

arrives from LCT.

The measures of the long period performances are collected using a XML file in

compressed format, which is transferred via FTP (par. 6.7) when the request arrives

from LCT.

The XML file always contains a complete set of 192 consecutive quarter intervals.The points and the parameters of the measure depend on the System Type; the XML

file contains only the points and the parameters of the measure, relevant to the specific

System Type configured on NE.

The measures of long period performances present, with respect to the normal

performance measurements, the following differences:

– they include 192 quarters intervals instead of 16 intervals

– they do not include the performances referred to the intervals of 24 hours

– they do not include the indication of the intervals with suspected measure intervals,

given that normally the measures are executed during the commissioning and then

all the intervals are considered as reliable

– they include the information on the status and the forcing of the switches used in

the commissioning tests, in such a way to consider an evaluation in

post-processing phase of the results of the commissioning test

– they do not include the measure points of the tributary side.

The XML file of the measures of the long period performance contains also the following

information in the heading:

– general information regarding the NE (IP address, System Type, ...)

– reference to the version of the format of the XML file

– number of the intervals where meaningful data are present (they are always the

first intervals); if the request of transfer via FTP arrives from LCT before the





recording of the 192 intervals is completed, the XML file is created adding,

replacing the missing intervals, some intervals with not meaningful data (the XML

file always contains a complete set of 192 intervals)

– the configuration parameters of the recording:

• recording modality: “Last Quarters” or “From Start Time”

• start date and time of recording

• date and time of generation of the XML file.

Fig. 6.80 Commissioning Report (example)

The procedure for the execution of the Commissioning Report is the following one:

– Run from the plug-in of NE the Commissioning Report tool.

– The PmCommReport window opens (Fig. 6.81).

Click on Browse and specify the name of the file and the relevant path where save

the report (Fig. 6.82).

– Click on Start to transfer via FTP the measures of the long period performances

stored into the NE; if a file with the same name already exists in the folder, a

confirmation for overwriting the existing file is required (Fig. 6.83). It is always

possible, in any moment, to stop the transfer of the long period performance

measures and close the Commissioning Report tool clicking on Close (Fig. 6.85).

The intervals with not meaningful data are not displayed by the Commissioning

Report tool.

By default, the commissioning report files are saved in the

“...\LCT\Rec\PmComm_Rec ” folder of the system user profile:

– “C:\Documents and Settings\<user_name>\Application Data\LCT\Rec\

PmComm_Rec ” in Microsoft Windows XP

– “C:\Users\<user_name>\AppData\Roaming\LCT\Rec\PmComm_Rec ” in

Microsoft Windows Vista.


NE name plus the extension “.txt ”. If the NE name contains some special





ones:

\ / : * ? “ < > |




6-58LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

If the XML file with the performance data is not available on the NE, an error

message is displayed (Fig. 6.86).

During the transfer, the Start and Show push-buttons are inactive.

– At the end of the transfer, in the PmCommReport window, the Show push-button

becomes active (Fig. 6.87).

Click on Show to display the report (Fig. 6.88) using the basic system editor

(WordPad or Notepad).

Fig. 6.81 Commissioning Report: starting window (example)

Fig. 6.82 Commissioning Report: selection of the output file (example)

Fig. 6.83 Commissioning Report: confirm for overwriting the file (example)

If the NE is unreachable via FTP, an error window opens (Fig. 6.84).





Fig. 6.84 Commissioning Report: NE unreachable via FTP

Fig. 6.85 Commissioning Report: transfer in progress (example)

Fig. 6.86 Commissioning Report: file with performance data not available (example)

Fig. 6.87 Commissioning Report: report loaded (example)




6-60LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.88 Commissioning Report: report file (example)

6.16.4 Alarm List

The NE Alarm List application (Fig. 6.89) manages the displaying in table format of all

the possible alarm and/or anomalous functioning situations currently present on the NE,

external alarms included.

For each alarm, the system displays the following information (Fig. 6.90):

– Index: row progressive index.

– Time Stamp: date and time of the alarm event with reference to the NE date and

time; the date and time points out the time when the event has occurred on the NE.

– Severity: severity associated to the alarm (information available only for the

equipment that support this function).

– Alarm Description: description of the alarm root.

Fig. 6.89 Alarm List (example)





Fig. 6.90 Alarm List window (example)

Into the status bar of the window of the Alarm List application program, the system points

out information concerning the single severity summarizations. For each severity, the

system reports the following elements:

– a LED for the severity identification; each severity is coupled with a specific color

– the total number of the activated alarms on the NE with this severity.

If, for a specific severity, no any alarm is active, the system displays 0 into the

corresponding field.

On every field of the single severity summarizations, a tooltip window is available

(Fig. 6.91) that points out the information reported into the field.

In the Alarm List application, for the signalling of the alarm severity the configuration of

the LCT colors is used (par. 6.11.1); each change to the configuration of the LCT colors

has immediate effects when confirmed.

Fig. 6.91 Alarm List: tooltip window (example)

In the pop-up menu of the Alarm List table (Fig. 6.92), it is also available the Print to file

command (par. 6.15) that allows exporting the displayed information onto text file or csv

file.

If the conditions do not allow the complete displaying of the table, the vertical and/or

horizontal scrolling bars are automatically displayed.

It is possible to display the alarms through an increasing ( ) or decreasing ( )

alphabetic/numerical order for each column, clicking on the column heading.




6-62LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.92 Alarm List: menu pop-up (example)

6.16.5 Services

The Services application (Fig. 6.93) allows creation, modification and deletion of thefollowing services:

– CESoP for E1 or STM-1 traffic with associated Pseudowires and bandwith profiles

– E-Line services for Ethernet traffic with associated Bundlings and bandwith profiles

Fig. 6.93 Services (example)

The procedure to execute the Services tool is the following one:

– Run the Services tool from plug-in of NE.

– The Services window opens (Fig. 6.94).

The Service tool is available for FlexiPacketHub, FlexiPacketFirstMile and

FlexiPacketMultiRadio (packet) equipments.





Fig. 6.94 Services window (example)

The application table displays the list of the existing services for the selected NE.

Each service present in the equipment corresponds to a row in the table.

The Services window contains following push-buttons:

– Create: opens the creation service window.

– Modify: Clicking on the Modify push-button, it is possible to modify the Description

and the Profile fields of a service.

– Delete: deletes the selected services.

– Close: closes the Services application

Placing the mouse over a selected row (yellow highlighted), a tooltip summarizing all theparameters and related values of that service appears (Fig. 6.95).

Fig. 6.95 Services window (example)




6-64LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

6.16.5.1 Create Service Table

Through the Create Service window (Fig. 6.96), it is possible to create CESoP or E-Line

services respectively for E1 or STM1 and Ethernet traffic.

Services are UNI to NNI, UNI to UNI, NNI to NNI depending on selected ports.

To create a service, click on the Create push-button in the Services window (Fig. 6.95).

The following window is displayed.

Fig. 6.96 Create Service window (example)

The fields that user can fill are:

– Description: the description for the creating service (Not required)

– Service type: a drop down list for the selection of the service type for the creating

service (Required)

– Service VLAN ID: numeric value that will be used to tag egress traffic for thecreating service (Required when enabled)

– Profile name: field shows the profile associated to a specific service (Required)

– Profile name: a drop down list for the selection of the profile for the creating

service (Required)

– Services CoS: a field that shows the service PHB Scheduling Class associated to

the selected profile– First/Second Port : a radio button for the selection of the first/second interface port

type for the creating service (Required)

– Module: a drop down list for the selection of the module for the creating service

(Required)

– Port: a drop down list for the selection of the port number for the creating service

(Required)

The Create Service window (Fig. 6.96) also contains the following push-buttons:

– Pseudo Wire: enabled only if the service type is CESoP

– New: opens a window for the creation af a new Profile

– Modify: opens a window for the modification of the selected profile

End to end service configuration, via LCT, is done by configuring the same

Service VLAN ID on all the service segments created in the crossed network

elements.





– Advanced: opens a window for insert Bundling values; enabled only for UNI ports

if the service type is E-Line

– Protection: opens a window for insert Protection values; enabled only if the

service port configuration is UNI to NNI or NNI to UNI– Create: performs the operations to create the service on the selected NE;

– Cancel: closes without doing any operation.

If a FPH 1200 or FPH 2200 SVR 5.0 is loaded by LCT, the following Create Service

window is displayed (Fig. 6.97):


An Apply Customer Priority (ACP) check box is displayed under the Service type drop

down list.

This feature allow the user to route traffic with different priorities over the same service,

all sharing the service's BW.

The check box is not selected by default and it is only available for the E-Line services:

selecting the CESoP value in the drop down list of the service type, the check box

becomes disabled.

For NNI-NNI service the check box is always disabled (Fig. 6.98).

The E-line service uses an Ethernet module including LAGs (if LAGs are created

and configured) on UNI side, and an Ethernet module including LPGs (if LPGs are

created and configured) on NNI side.




6-66LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


In the Service Table also the ACP column will be displayed: its value will be Enabled

or Disabled depending on the service type (Fig. 6.99).

Fig. 6.99 Service table window (example)

The selected row tooltip shows this values if included (Fig. 6.100).


Print to file command is available for this table. User can export to text file or csv file.

The text format is shown in Fig. 6.101.






6.16.5.2 Create Pseudo Wire service

Selecting CESoP as Service Type it is necessary the creation of Pseudowires

associated to the service (Fig. 6.102).

Fig. 6.102 Enable Pseudo Wire push-button (example)

Clicking on the Pseudowire push-button, the following window is displayed (Fig. 6.103).




6-68LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.103 Pseudo Wire window (example)

Fields that the user can fill are:

– Description: the description for the creating Pseudowire (Not required)

– Destination IP address: the IP address involved in the creating Pseudowire

(Required)

– Administrative status: the administrative status for the creating Pseudowire

– CE-Vlan ID: numeric value that will be used to tag egress traffic for the associated

service

– Local UDP port/Remote UDP port (only if CESoPSN encapsulation is selected):

the fields show the port number to associate to the current Pseudo Wire.

– Local ECID/Remote ECID (only if MEF8 encapsulation is selected): the fields

show the Emulated Circuit Identifier to associate to the current Pseudo Wire.

The MEF8 encapsulation feature is active only for Flexi Packet equipments

specified in Product Feature List document.





Checking the Advanced settings check-box (Fig. 6.103) the following field will be

enabled:

CE-CoS (it's always disabled and with 6 as default value and is enabled only if the

CESoPSN encapsulation is selected)

CE-IP DSCP (that it assigns various levels of service to the network traffic)

Payload size (disabled for MEF8 encapsulation and with 256 as default value)

Differential clock

Next hop MAC (allowed values are Dynamic or Static).

Jitter buffer size field

Inactivity threshold

Destination IP address, CE-Vlan ID, Local UDP port/ Local ECID, Remote UDP

port/ Remote ECID fields are mandatory.

If some of these values are missing, clicking on the Insert push-button generates an

error message (Fig. 6.104).

A service object in a single FlexiPacket equipment is terminated by a UNI and a

NNI ports on the two sides, or is terminated by a couple of NNI ports, one at each

side.

The UNI/NNI ports available to terminate a service depend on the slaveconfiguration of the equipment:

– TDM access cards, as the 16xE1, 8xE1, 4xSTM-1 access cards, provide only

UNI ports to terminate CESoP services.

Therefore, there are respectively 16, 8, 4 UNI ports per module that can be

involved in CESoP UNI2NNI services.

The total number of available ports depends on the number of modules of

each type. In case the STM-1 access card is present, each STM-1 data flow

contains 63x2Mbit/s tributaries (VC12 containers, according to SDH

hierarchy) that can be independently mapped to the pseudowires.

– Ethernet access card provides UNI or NNI ports, so they are available to

create UNI2NNI services or NNI2NNI services.

In addition to the pluggable Ethernet modules, A-2200 provide also 4

Ethernet ports in the chassis, that can be used to terminate services. In place

of the Ethernet ports, at NNI side it is also possible to select the LPG objects,

if previously created.

If there is no possible additional bundling on a port, i.e. all the traffic is already

mapped to existing services, that port if filtered out from the port choice list in

service creation.

As consequence, when adding services to an equipment, the port choice list

gradually can become empty.

When a port is assigned to a service with a port type(UNI or NNI), it is no morepresent in the port choice list of the other type (NNI or UNI respectively).

To change the port type it is necessary to delete all the services on that port.




6-70LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.104 Empty value into a field in Pseudo Wire window (example)

Fig. 6.105 Empty value into a field in Pseudo Wire window (example)

If user inserts into Local UDP port or Remote UDP port field a number that it is out of

range, an error message is displayed (Fig. 6.104).

Fig. 6.106 Out of range value into a field in Pseudo Wire window (example)

Clicking the Insert push-button the Pseudowire is inserted into the local table. Selecting

one row and placing the mouse over it, a tooltip with all the Pseduowire is displayed.

(Fig. 6.107).

After the insert operation all fields are reinitialized to the default value.

The UNI ports involved in the previous Pseudowires are not available for new one. They

are removed from the drop down list.

The UNI ports that are already used, are not more visible in the Port dorp down list

because they are not reusable.

It is possible to create more than one Pseudowires for the same CESoP service.





NNI port and CE-VLAN ID must be unique for the transport service containing

Pseudowires, so they are fixed after the first insert operation.

It is possible to remove one Pseudowire selecting it in the table and clicking the Remove

push-button.

Fig. 6.107 Pseudo Wire window (example)

6.16.5.3 Create New Profile

The section Service Level Agreement allows the customization of Bandwidth Profiles.

This customization is local to the client PC only. (Fig. 6.108)

Placing the mouse over the information icon all the values of the selected profile are

displayed. (Fig. 6.108)





6-72LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

To create a new profile click on the New push-button in the Service Level Agreement

section on the Create Service window (Fig. 6.108). The following window is displayed.

Fig. 6.109 New Service Level Agreement window (example)


– Profile name: the name of the new profile (Required).

– Service CoS: a drop down list with the available Service CoS for the new profile.

In the Symmetric and Asymmetric sections the fields have the same values.

To enable fields of the Asymmetric section check the Asymmetric check box.

Fields that the user can fill in the Symmetric and Asymmetric sections are:

– CIR (Committed Information Rate).– EIR (Excess Information Rate).

– Committed burst size.

– Excess burst size.

It is possible to write the values in all that fileds. Alternatively the user can increase or

decrease the values clicking on corresponding arrows. The arrow's step for CIR and EIR

changes depending on their own values.

Clicking on the OK push-button the creation of the profile is performed.

An error message is displayed if the Profile name is missing (Fig. 6.110).





Fig. 6.110 Empty value into a Profile name field in New Service Level Agreemen window

(example)

In the Service Level Agreement section, a click on the Modify push-button opens the

Modify Service Level Agreement window where the user can modify the selected

profile (Fig. 6.107).

The user can delete a custom profile already created, selecting the corresponding

profile in the Profile name drop down list and click the Delete push-button in the

Service Level Agreement section..

6.16.5.4 Create Bundling

Selecting E-Line as Service Type it is possible to create the bundlings associated to the

creating service (Fig. 6.111).

Fig. 6.111 Enable Advanced push-button (example)

Clicking on the Advanced push-button, the following window is displayed (Fig. 6.112).

Default profiles (Bronze, Silver, Gold, 1xE1_8fr, 4xE1_8fr, 8xE1_8fr, 16xE1_8fr,

VoIP, Video_LD and Video_HD) cannot be modified or deleted.




6-74LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.112 Advanced window (example)

From VLAN manipulation drop down list, the user can select 2 values: Preservation or

Translation. It is possible to choose different settings in the CE Vlan ID and Ethertype

sections.

Selecting the User-defined option the CE-Cos field will be enabled.

Clicking the Insert button, the creating bundling is inserted into the local table.

Only unique VLAN manipulation type is allowed for each service.

It is possible to create only one Translation bundling while Preservation bundlings can

be more than one.The drop down list is enabled only before the first bundling creation.

The Insert button becomes disable when no more insertion will be allowed.Selecting a row and placing a mouse over it, a tooltip summarizing all values related to

the selected bundling is displayed (Fig. 6.113).

Fig. 6.113 Advanced window (example)

If the user selects the User-defined option but does not fill the corresponding field, after

clicking the Insert push-button, an error message will be displayed (Fig. 6.114).





Fig. 6.114 Empty value into a User-defined field in Advanced window (example)

The IP Mappings push button becomes enabled only selecting ARP or IP in the

Ethertype section.

Clicking on the IP Mappings push button the following window is displayed (Fig. 6.115).

Fig. 6.115 IP Mapping window (example)


– Source IP address

– Source IP mask

– Destination IP address

– Destination IP mask

– DSCP (Any or User Defined)

– IP protocol

The user can remove bundlings already created, selecting the corresponding row and

click the Remove push-button in the Advanced window (Fig. 6.113).

If the user select Translation value as VLAN manipulation type, only the User-defined

and CE-Cos fields are enabled.

In UNI to UNI service, the user can insert bundlings for each UNI port and Advanced

buttons are both enabled.

The selection of the VLAN Manipulation type in one UNI port forces the choice of theVLAN Manipulation type for the other port.

At the end of the creation of all bundlings involved in the service the user can close the

window clicking the Close push button (Fig. 6.113).

On the Create Service window the user can click the create push button to perform the

service creation.

If the first and the second port selected are equals an error message will be displayed

(Fig. 6.116).

UNI management ports configuration is a risky operation beacuse a wrong

configuration can cause traffic loss e. g. mismatch between tagged and untagged

data traffic.




6-76LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.116 Wrong ports selection in the Create Service window (example)

The Admin Status of the creating service is chosen by the user before performing the

service creation by a question dialog (Fig. 6.117).

Fig. 6.117 Warning window in the Create Service window (example)

During the service creation the Create Service window is closed and a progress bar is

shown. If the creation fails an error message is displayed (Fig. 6.118).

Fig. 6.118 Service creation failed(example)





6.16.5.5 Delete Services

To delete one or more services, the user has to select one or more rows in the Service

table (Fig. 6.94) and click the Delete push-button.

Confirmation is required (Fig. 6.119).

Fig. 6.119 Delete services in the Service table window (example)

6.16.5.6 Modify Services

It is possible to modify a service previously created (E-line or CESoP).

Selecting one service the Modify push-button is enabled.Clicking the Modify push-button the Modify Service window is displayed (Fig. 6.120).

The user can modify only Description and Profile.

The new profile associated to the service must have the same Service CoS.

Fig. 6.120 Modify Service window (example)

Clicking the Apply push button, the changes will be performed and, on success,

displayed in the services table.

Modify Administrative Status of a service

It is possible to modify the Admin Status of the service.

In the Services table window selecting a row and right clicking, a popup menu is shown




6-78LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

and the user can select Disable Admin Status or Enable Admin Status (Fig. 6.121).

Fig. 6.121 Modify Administrative Status (example)

Clicking Disable Admin Status or Enable Admin Status in the popup menu, a

confirmation is requested (Fig. 6.122).

Fig. 6.122 Modify Administrative Status (example)

Successful change is visible on the Services table window.





6.16.5.7 Modify Admin Status of Pseudowires

For the CESoP services it is possible to change the Admin Status of their Pseudowires;

in the right popup menu the user can select Pseudowire details (Fig. 6.123) to open a

window that shows all the pseudowires of the selected service (Fig. 6.124).

Fig. 6.123 Pseudowire details popup (example)

Fig. 6.124 Pseudowire details window (example)

In the Pseduowire details table window selecting a row and right clicking, a popup

menu is shown and the user can select Disable Admin Status or Enable Admin

Status (Fig. 6.125).




6-80LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


Clicking Disable Admin Status or Enable Admin Status in the popup menu, a

confirmation is requested.Successful change is visible on the Pseudowire details table window.





6.16.5.8 Modify Pseudowires of a service

In the Pseudowire details table window (Fig. 6.124) it is possible to add or remove

Pseudowires for a service.

Selecting a row in the Pseudowire details table, the Remove push-button is enabled

(Fig. 6.126).


Clicking the Remove push-button, a confirmation window is displayed (Fig. 6.127)

before the pseudowire removal.





6-82LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Clicking the Insert push-button to add a new pseudowire for the service, the New

Pseudowire window is displayed (Fig. 6.128).

Fig. 6.128 New Pseudowire window (example)





6.16.5.9 Modify Bundlings of a service

For the E-Line services it is possible to view all their Bundlings; in the right popup menu

the user can select Bundling details (Fig. 6.129) to open a window that shows all the

bundlings of the selected service.

Fig. 6.129 Bundling details popup (example)

In the Bundling details table window (Fig. 6.130) it is possible to add or remove

Bundlings for a service.

Selecting a row in the Bundling details table, the Remove push-button is enabled

(Fig. 6.131).

Fig. 6.130 Bundling details window (example)

The Bundling details window (Fig. 6.130) refers to a service with configured bundligs.

If the VLAN manipulation is Preservation, bundlings can be more than one.

If the VLAN manipulation is Translation, there is only one bundling for a service.




6-84LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011


Clicking the Remove push-button, a confirmation window is displayed (Fig. 6.132)

before the bundling removal.


Clicking the Insert push-button to add a new bundling for the service, the New Bundling

window is (Fig. 6.133).

Fig. 6.133 New Bundling window (example)





6.16.5.10 Create Protection for a service

It is possible to create a protection for the creating service.

To create a protection, it is necessary to push the Protection button, available both for

E-Line and CESoP Service Type. The Service Protection window is displayed:

(Fig. 6.134)

Fig. 6.134 Service Protection window (example)

In the Protection type drop down list (Fig. 6.134), the user can select 3 values: None

(-), Monitored or Protected.

The selection of the Monitored protection type enables the left part of the window

containing the following fields (Fig. 6.135:

– MEP ID local main (Maintenance End Point Identifier): is the measurement point

identifier for the local port involved into the service main path; this value must be

unique for MA. MEP

– MEP ID remote main: is the measurement point identifier for the remote portinvolved into the service main path; this value must be unique for MA. MEP;

– MA name main (Maintenance Association): is the name that identifies a set of

MEPs configured on the main path; it is used to verify the integrity of a single

service instance. This value must be unique on the network.

– CCI (Continuity Check Interval): is the configured time between two Continuity

Check Message messages; these messages are periodically transmitted by a MEP

in order to assure the continuity over the MA it belongs to.





6-86LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

The selection of the Protected protection type enables also the rigth part of the window

containing the following fields (Fig. 6.136):

– MEP ID local stand-by: is the measurement point identifier for the local port

involved into the service stand by path; this value must be unique for MA. MEP– MEP ID remote stand-by: is the measurement point identifier for the remote port

involved into the service stand by path; this value must be unique for MA. MEP

– MA name stand-by: is the name that identifies a set of MEPs configured on the

stand by path; it is used to verify the integrity of a single service instance. This value

must be unique on the network

– Reversion time out (enabled only if Revertive mode is selected): is the time

interval the connection has to wait, before switching from the stand-by path to the

main path after its recovery

– Service VLAN ID: is the Stand-by path Service VLAN ID

– Module: is the module containing the stand-by port

– Port: is the Stand-by port (1200 and 2200 SVR5.0 Final)

It is also possible to create a protection with an LPG: all the available LPGs are

contained into the port drop down list. There is not a correlation with the module, so

every LPGs are available indipendently from the selected module. LPGs can be used

for more than one service.


All the fields are required. If the user does not fill all of them, after clicking the OK

push-button, an error message will be displayed.

For the Monitored protection type MEP ID local main and MEP ID remote name must

be different, otherwise an error message will be displayed (Fig. 6.137):

Fig. 6.137 Service Protection window - Error message





Likewise, the Protected protection type requires that MEP ID loacal stand-by must be

different from MEP ID remote stand-by.

If MA name main and MA name stand-by are equal, an error message will be

displayed (Fig. 6.138).


The stand-by port must be different from UNI port previously selected, otherwise an

error message will be displayed (Fig. 6.139).


For the protected services it is possible to view the protection details; in the right popup

menu there is the item Protection details.

Clicking on this item a window that shows all the protection details will be displayed

(Fig. 6.140).

If a service has a protection created with a LPG inside, in the Service Protection

Details window (Fig. 6.140) it will appears the specific LPG into the Port drop down list

and the Module drop down list will be empty because the LPG is indipendent from the

modules.

Fig. 6.140 Service Protection Details window




6-88LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

6.17 Plug-in Common Applications

LCT provides the integration of common applications in the NE plugs-in.

The common applications available for a NE depend on (refer to Customer ReleaseNotes):

– the equipment type

– the equipment SVR

– the version of the plug-in for the equipment management.

The common applications available for the several supported equipment types are the

following ones:

– Setting of date and time of NE (par. 6.17.1)

– Loading/storing of the NE configuration file (par. 6.17.2)

– Recording of the G.821/G.826 performances referred to quarter intervals(par. 6.17.3)

– Report of the inventory data (par. 6.17.4)

– Telemeasurement (par. 6.17.5)

– Graphic tool for the measure displaying (par. 6.17.6)

– FTP Client (par. 6.17.7)

– Table management tool (par. 6.17.8)

– Configuration of the RF frequency (par. 6.17.9)

– Setting of date and time in the commissioning test (par. 6.17.10)

6.17.1 Setting of date and time of NE

For the NE that support it, it is available the function for the manual setting of the NE

date and time.

The date and time become particularly important during the execution and the analysis

of the measures and of the recordings on the equipment.

The manual setting of the date and time relevant to a NE can be executed only by

the user with the writing privileges on the NE.

The manual setting of date and time is meaningful only on NEs for which any

modality of network synchronization has been disabled.

If the synchronization (via NE Manager or SNTP Server) is enabled on a NE, the

manual setting of date and time will be overwritten at the next synchronization.

If the SNTP synchronization is used on a NE, the manual setting of date and time

is inhibited also it you have administrator privileges on the NE.





Execute the following procedure to update date and time:

– Run, from the NE menu, the tool for the date and time setting.

– The system displays the Timeset window (Fig. 6.141) with the setting field of the

date and time. This window always displays points out the following information:

• current date and time of the NE (Current time field)

• timing mode set for the network synchronization (Time Mode field).

– The system provides two different setting modes of the date and time:

• PC date and time

Select the PC Time radio button to apply to the NE the current date and time

of the local LCT PC.• Manual date and time

Select the New Time radio button to set manually the NE date and time.

When the user selects the New Time radio button, the system allows typing

into the manual insertion fields of the date and time (Fig. 6.142).

To make easier the date and time insertion, the system provides a calendar

subdivided into months from which the user can directly selects the desired

date. However, the user can always type into the date insertion field.

– Click on OK to apply the new date and time to the NE.

The system requires for a confirmation of the command execution (Fig. 6.143)

because the change of the NE date and time affects the monitoring of the

performances. When you confirm the application of the new date and time to the NE, the Timeset

window automatically closes.

Fig. 6.141 Timeset: starting window

In the case of change of date and/or hour the NE performance windows are not

significant until the end of the polling operation. Than, is necessary to wait some

instants (until the windows refresh), before reading or recording the

performances.




6-90LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.142 Timeset: manual setting of date

Fig. 6.143 Timeset: confirmation for the new date and time of NE





6.17.2 Loading/storing of the NE configuration file

The copy/paste function of the NE configuration file is available for the NE that support it:

– Copy NE (par. 6.17.2.1): storing the configuration parameters of the equipment ona file

– Paste NE (par. 6.17.2.2): equipment configuration by means of the parameters

present into the NE configuration file.

According to the NE type, the Copy and Paste commands are available as:

– push-buttons of a NE configuration window

– options of a NE menu.

The use of NE configuration files, stored on the PC or on a central archive, has two

functions:

– to make available backup copies of the equipment configuration, to allow a quick

configuration restore in case of loss of the configuration

– to make available several base configurations, to make easier and to reduce

operations to configure the network equipment.

6.17.2.1 Copy NE

The procedure for the memorization on file of the NE configuration is the following one:

– From the NE plug-in, run the Copy NE application program.

The COPY NE CONFIGURATION window (Fig. 6.144) is displayed.

– Click on Browse and specify the name of the destination file and of the relevant

path, where the equipment configuration has to be stored (Fig. 6.145).

If into the destination folder it already exists a file with the same name, the system

asks for the confirmation before overwriting the existing file (Fig. 6.146)

The Start software push-button (Fig. 6.147) is activated in the COPY NE

CONFIGURATION window.

The operations for the loading/storing of the NE configuration can be executed

only if the user has the writing privileges on the NE.

The parameters included in the NE recording file depend on the equipment type.

By default, the NE configuration files are saved in the “...\LCT\Appl\NCFG_REC ”

folder of the system user profile:

– “C:\Documents and Settings\<user_name>\Application Data\LCT\Appl\

NCFG_REC ” in Microsoft Windows XP

– “C:\Users\<User_name>|AppData\LCT\Appl\NCFG_REC ” in Microsoft

Windows Vista.




6-92LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– Click on Start. The software push-button switches from Start to Abort and it starts

the storing phase with the displaying of the relevant messages (Fig. 6.148).

It is always possible to stop the storing clicking on Abort.

– At the end of the storing phase, the system deactivates again the Abortpush-button and the message displaying ends with Finished (Fig. 6.149).

– Click on Close (Fig. 6.149) to close the COPY NE CONFIGURATION window.

Fig. 6.144 Copy NE: starting window (example)

Fig. 6.145 Copy NE: file selection (example)

Fig. 6.146 Copy NE: confirmation of the file overwriting (example)





Fig. 6.147 Copy NE: start of operation (example)

Fig. 6.148 Copy NE: operation running (example)

Fig. 6.149 Copy NE: operation ended (example)

6.17.2.2 Paste NE

The procedure for the uploading of the NE configuration file is the following one:

– From the NE plug-in, run the Paste NE application program. The PASTE NE

CONFIGURATION window (Fig. 6.150) opens.

– Click on Browse and specify the name of the source file and the relevant path,

where the configuration to be loaded (Fig. 6.151) is stored.

The Start software push-button (Fig. 6.152) is activated in the PASTE NE

CONFIGURATION window.




6-94LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– Click on Start. The software push-button switches from Start to Abort and it starts

the loading phase with the displaying of the relevant messages (Fig. 6.153).

The user can always stop the operation on progress clicking on Abort.

– At the end of the loading phase, the system deactivates again the Abortpush-button and the message displaying ends with Finished (Fig. 6.154).

– Click on Close (Fig. 6.154) to close the PASTE NE CONFIGURATION window.

Fig. 6.150 Paste NE: starting window (example)

Fig. 6.151 Paste NE: file selection (example)

Fig. 6.152 Paste NE: operation start (example)





Fig. 6.153 Paste NE: operation in progress (example)

Fig. 6.154 Paste NE: operation ended (example)

6.17.3 Recording of the G.821/G.826 performances referred toquarter intervals

For the NE that support it, it is available the function for the recording on file of the

G.821/G.826 performances referred to the quarter intervals.

The measurements of G.821/G.826 performances referred to quarter intervals that can

be recorded on a file change according to the radio equipment type.

The G.821/G.826 performances recorded on file can be displayed by means of a

software tool.

The Controller of a NE keeps in memory the G.821/G.826 performance data of the last

4 hours (16 quarter intervals). The storing of the intervals is continue and cyclic; once

reached the maximum size of 16 intervals, the storing of a new interval causes thedeletion of the oldest interval.

In the case of change of date and/or hour the NE performance windows are in a

not congruent status until the end of the polling cycle. Than, is necessary to wait

some instants (until the windows refresh), before reading or recording

performances.

A user can start at the same time up to seven recording sessions for the recording

of the performances referred to quarter intervals.




6-96LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

The procedure for the G.821/G.826 performance recording on file is the following one:

– Run, from the NE plug-in, the tool for the recording on file of the performances

– The window for the management of the performance recording to file opens

(Fig. 6.155).

Set the recording parameters:

• Click on Browse to specify possibly the name of the file and the relevant path

where storing the performance data (Fig. 6.156).

• In the Period field set the start (Initial Time) and stop (Stop Time) date and

time for the recording.



time of recording

• the end date and time of recording must be later than or equal to current

date and time of PC.

To facilitate the insertion of the date, a calendar is suggested subdivided in

months, from which it is possible to directly select the wished date

(Fig. 6.157). The field for the insertion of the date is however always editable.

• Enable/disable (Retrieve performance history check-box) the recovery ofthe performance data of the last four hours stored in the NE.

It is possible to exit from the tool for the recording clicking on Close.

– Start the recording procedure clicking on Start; if a file with the same name already

exists in the destination folder, the user is asked for the confirmation to overwrite

the existing file (Fig. 6.158).

An error window opens and the set configuration is not accepted in the following

cases:

• date and time of start of recording equal to or later than the date of stop of

recording (Fig. 6.159)

• date and time of end of recording previous to the current date and time of the

PC (Fig. 6.160).

The recording sessions of the performance referred to quarters started on a NE

closed, with consequent loss of the performance data, in case of disconnection

(even if temporary) of the NE.


NE name plus the extension “.prf ”. If the NE name contains some special





ones:

\ / : * ? “ < > |

By default, the performance recording files are saved in the “...\LCT\Rec ” folder

of the system user profile:



– “C:\Users\<User_name>|AppData\Roaming\LCT\Rec ” in Microsoft Windows

XP.





– After the execution of the Start command, the collection of the performance starts,

with displaying of the log file (Log field) and deactivation of the configuration fields

and of the Close push-button.

All the quarter periods of performance detection are reported in the log file; for each

period, the presence or absence of the performance data is pointed out. If the

Retrieve performance history check-box is selected, the collection of the

performance starts with the recovery of the performance data of the last 4 hours

stored in the NE. Note that:

• if the start date of recording is equal to or previous to the current date and time

of PC, the performance collection immediately starts at the end of each

quarter; the push-button switches from Start to Stop (Fig. 6.162).

• if the start date and time of recording is later than the date and time of PC, the

collection is preceded by a waiting phase:

• at the beginning, the push-button switches from Start to Change

(Fig. 6.161); in this waiting phase, clicking on Change, it is possible to

modify the set recording configuration• then, at the set date and time, the procedure of performance collection

automatically starts at the end of each quarter; the push-button will

switch from Change to Stop (Fig. 6.162).

– During the recording, it is possible to execute the following operations:

• Stop of recording

Clicking on Stop, it is possible to stop the recording in advance; the

confirmation of the anticipated stop of the recording is required (Fig. 6.163).

The push-button switches from Stop to Start and the configuration fields and

the Close push-buttons becomes active again.

• Displaying of the performance data.

Clicking on View, it is possible to display, via the basic editor of the system(WordPad or Notepad), the collected performance data.

If, with recording running, the user attempts to close the application window, an

error window opens (Fig. 6.164) to points out that it is necessary to stop the

operation via the Stop push-button before exiting from the application.

– At the end of the recording period, the push-button changes fromStop to Start and

the configuration fields and the Close push-button become active again

(Fig. 6.165).

Clicking on View, it is possible to display (Fig. 6.166), via the basic editor of the

system (WordPad or Notepad), the collected performance data.

If no performance data has not been collected, the View push-button results

inactive and the “No data to read” wording is displayed in the Log field (Fig. 6.167).




6-98LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.155 G.821/G.826 performance recording: configuration window (example)

Fig. 6.156 G.821/G.826 performance recording: selection of output file (example)

Fig. 6.157 G.821/G.826 performance recording: date setting (example)





Fig. 6.158 G.821/G.826 performance recording: confirmation for file over-writing (example)

Fig. 6.159 G.821/G.826 performance recording: incongruence between start date and time

and end of recording (example)

Fig. 6.160 G.821/G.826 performance recording: incongruence between current date and

time and end of recording (example)

Fig. 6.161 G.821/G.826 performance recording: operation waiting (example)




6-100LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.162 G.821/G.826 performance recording: operation on progress (example)

Fig. 6.163 G.821/G.826 performance recording: confirmation for operation stop (example)

Fig. 6.164 G.821/G.826 performance recording: error window (example)





Fig. 6.165 G.821/G.826 performance recording: operation ended (example)

Fig. 6.166 G.821/G.826 performance recording: data performance table (example)




6-102LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.167 G.821/G.826 performance recording: no performance data to read (example)

6.17.4 Report of the inventory data

NE Inventory Report function is available for the NE that foreseen such a feature, it

allows to report the inventory data of all the unit, storing in a single file.

It is possible to use whatever text editor to open the report file and to display the

inventory date.

The procedure for inventory data of the units is the following one:

– Run, from the NE plug-in, the Inventory Report tool.

– The Inventory Data window is displayed (Fig. 6.168). Click on Browse and

specify the file name and the relevant path, where the inventory data have to be

stored (Fig. 6.169).

By default, the inventory files are saved in the “...\LCT\Rec ” folder of the system

user profile:

– “C:\Documents and Settings\<User_name>\Application Data\LCT\Rec ” in



XP.


NE name plus the extension “.inv ”. If the NE name contains some special





ones:

\ / : * ? “ < > |





– Click on Start, if a file with the same name already exists in this folder, the system

asks for the confirmation to overwrite the existing file (Fig. 6.170). The push-button

switches from Start to Stop and the storing phase starts with the displaying of the

relevant messages (Fig. 6.171).

It is always possible to stop the storing clicking on Stop.

– At the end of the storing phase (Fig. 6.172): click on View (Fig. 6.172) to display

the report on units inventory data (Fig. 6.173) with the system base editor

(WordPad or Notepad).

– Click on Close (Fig. 6.172) to close the window Inventory Data and exit.

Fig. 6.168 Inventory Report: starting window (example)

Fig. 6.169 Inventory Report: file selection (example)

Fig. 6.170 Inventory Report: confirmation for file over-writing (example)




6-104LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.171 Inventory Report: operation on progress (example)

Fig. 6.172 Inventory Report: operation ended (example)





Fig. 6.173 Inventory Report: report file (example)

6.17.5 Telemeasurement

It is possible to execute the telemeasurement of some operating parameters particularly

meaningful and to detect the data of the measurement on file for possible successive

processing operations.

According to the radio equipment type, the type of operating parameter involved into the

telemeasurement procedure changes (normally it is possibile to execute the RX RF

power telemeasure).

To execute the telemeasurement it is necessary to execute the following procedure:

– Run, from the NE menu, the telemeasurement tool (the command changes

according to the radio equipment type).

– The window for the remote measurement setting (Fig. 6.174) is displayed.

Set the date and the starting and ending time of the recording operation.

– Click on Browse and specify the file name and the relevant path where to store the

recording data (Fig. 6.175).

By default, the telemeasure file are saved in the “...\LCT\Rec ” folder of the system

user profile:

– “C:\Documents and Settings\<user_name>\Application Data\LCT\Rec ” inMicrosoft Windows XP


XP.




6-106LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

– Set the start (Initial Time) and stop (Stop Time) date and time for the recording.



time of recording

• the end date and time of recording must be later than or equal to current

date and time of PC.To facilitate the insertion of the date, a calendar is suggested subdivided in months,

from which it is possible to directly select the wished date (Fig. 6.176). The field for

the insertion of the date is however always editable

The Now push-button allows setting automatically, as start date of recording, the

current date and time of PC.

– Begin the recording clicking on Start; if a file with the same name already exists in

this folder, the system asks for the confirmation to overwrite the existing file

(Fig. 6.177). The software push-button switches from Start to Show (Fig. 6.180).

– During the recording, it is always possible:

• to display the profile in the elapsed time of the measured parameter, clicking

on Show (Fig. 6.180)

• to stop early the recording procedure clicking on Cancel; the system asks for

the confirmation about the interruption of the measurement (Fig. 6.181).

From the recording application, it is possible to run a specific displaying tool

(par. 6.17.6), which displays the trend of the measure on the basis of the recorded

data.

To start the tool, before the end of the recording, select the Show push-button in

the recording window. The tool automatically starts when the final recording instant

is reached.

By default, the system assigns, as name of the file for the telemeasurement

recording, the NE name plus the extension specifying the ODU where the

measure is executed (in the example “odA”). If the NE name contains some

special characters that can not be used into the names of files and/or folders ofMicrosoft Windows, it is necessary to change the name of the destination file (e.g.

removing all the special characters). For instance, the special characters that can

not be used into the names of files and/or folders of Microsoft Windows are the

following ones:

\ / : * ? “ < > |

If the start and stop date and time are not congruent, an error window is displayed

(Fig. 6.178) and the recording does not start.

If the end date and time is older than the current date and time of the PC, an error

window is displayed (Fig. 6.179) and the recording does not start.





Fig. 6.174 Telemeasure: starting window (example)

Fig. 6.175 Telemeasure: file selection (example)

Fig. 6.176 Telemeasure: setting of date and time (example)

Fig. 6.177 Telemeasure: confirmation for file overwriting (example)

Fig. 6.178 Telemeasure: start and stop date and time not congruent (example)




6-108LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.179 Telemeasure: invalid stop date and time (example)

Fig. 6.180 Telemeasure: operation in progress (example)

Fig. 6.181 Telemeasure: confirmation for exit (example)

6.17.6 Graphic tool for the measure displaying

A graphic tool is embedded in LCT for the display of the measurement data, which is

used for the application of execution of the remote measurements (par. 6.17.5).

This graphic tool allows displaying the data of a measure in two different modalities:

– Chart modality (par. 6.17.6.1): displaying in graphic format.

– Data modality (par. 6.17.6.2): displaying in table format.

6.17.6.1 Chart modality

In this modality the graphic is displayed that shows the trend during the time of the

measure of the RF RX field (expressed in dBm).





Fig. 6.182 Displaying of a measure in Chart modality (example)

It is possible to zoom a portion of the graphic (Fig. 6.183) selecting by means of the

mouse, through dragging, the interested area.

Fig. 6.183 Chart modality: zoom of an area (example)

Clicking the right button of the mouse on the graphic, a pop-up menu opens.




6-110LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.184 Chart modality: pop-up menu

The following items are present in the pop-up menu:

– Properties

It causes the opening of a new panel (par. 6.17.6.1.1) which allows

setting/modifying the displaying properties of the graph.





– Save As

It allows saving the graphic of an image of “.PNG ” format.

The window opens where specifying the name of the file and the relevant path

where saving the image of the graphic.

Fig. 6.185 Chart modality: selection of the output file

– Print

It allows printing directly the graphic.

The window opens for the setting of the printing properties and the selection of the

print to use.

Fig. 6.186 Chart modality: printing properties

– Zoom In

It allows executing one of the following zoom-in operations on the graphic:

• Both Axes: zoom-in of all the graphic

• Domain Axis: zoom-in only of the axis relevant to the time intervals

• Range Axis: zoom-in only of the axis relevant to the RF RX field.




6-112LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.187 Chart modality: Zoom In

– Zoom Out

It allows executing on the graph one of the following operations of zoom-out:

• Both Axes: zoom-out of all the graphic

• Domain Axis: zoom-out only of the axis relevant to the time intervals

• Range Axis: zoom-out only of the axis relevant to the RF RX field.

Fig. 6.188 Chart modality: Zoom Out

– Auto Range

It allows executing one of the following operations of restoring of the automatic

displaying (starting displaying):

• Both Axes: restore of the automatic displaying of all the graphic

• Domain Axis: restore of the automatic displaying only of the axis relevant to

the time intervals

• Range Axis: restore of the automatic displaying only for the axis relevant to

the RF RX field.

Fig. 6.189 Chart modality: Auto Range

6.17.6.1.1 Chart PropertiesThe Chart properties panel is a tab window that allows customizing the displaying of

the graphic.

To close the Chart Properties window and make the settings/changes effective, it is

necessary to click on OK.

The Cancel push-button allows closing the Settings window, without saving the

executed settings/changes, which are lost.





Tab Title

The Title tab allows setting/modifying the appearance of the title of the graph.

Fig. 6.190 Chart Properties table: tab Title

The Show Title check-box allows enabling/disabling the displaying of the title.

The Text text-box allows setting/modifying the text of the title.

The Font field allows setting/modifying the font attributes of the title; clicking on Select

the window opens for the selection of the font attributes (font type, font size, font

thickness).

Fig. 6.191 Tab Title: Font Selection window

The Color field allows setting/modifying the color of the title, clicking on Select thewindow opens for the selection of the color of the title.




6-114LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.192 Tab Title: Title Color window

Tab Plot

The Plot tab allows setting/modifying the appearance of the graphic. The Plot tab is

made by a panel that contains, on its turn, three tabs:

– Domain Axis/Range Axis tab

The Domain Axis tab allows customizing the appearance of the axis relevant to

the time reference.

The Range Axis tab allows customizing the appearance of the axis relevant to the

RF RX field.

The two tabs are equal, except for the Range tab of the Other section that is

available only for the Range Axis tab.

Fig. 6.193 Chart Properties window: Tab Plot - Domain Axis





Fig. 6.194 Chart Properties window: Tab Plot - Range Axis

Tab Other - Ticks

Tab Other - Range

• General section

The Label text-box allows inserting/modifying the axis label.

The Font field allows setting/modifying the font attributes of the axis label;

clicking on Select, the window for the selection of the font attributes opens.

Fig. 6.195 Tab Plot: Label - Font Selection window




6-116LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

The Paint field allows setting/modifying the color of the axis label; clicking on

Select the window for the selection of the color opens.

Fig. 6.196 Tab Plot: Label Color window

• Section Other

The Other section contains: the Ticks tab and, only for the axis relevant to

the RF RX field, the Range tab.

• Ticks tab

The Show tick labels check-box allows enabling/disabling the

displaying on the axis of the tick mark labels.

The Show tick marks check-box allows enabling/disabling the

displaying on the axis of the tick marks.

The Tick label font field allows setting/modifying the font attributes of

the tick mark labels of the axis; clicking on Select the window for the

selection of the font attributes (font type, font size, font thickness).

Fig. 6.197 Tab Plot: Tick label font window - Font Selection

• Range tab

The Range tab allows setting/modifying the interval of the RF RX field

displayed on the graph.

With Auto-adjust range check-box selected, the interval is

automatically determined on the basis of the data of the measure.

With Auto-adjust range check-box unselected, it is possible to

set/modify manually both the minimum value (Minimum range value)and the maximum value (Maximum range value) of the range.





– Appearance tab

The Appearance tab allows customizing the appearance of the area of the

graphic.

Fig. 6.198 Chart Properties window: Tab Plot - Appearance

The Outline stroke field allows setting/modifying the thickness of the border of the

graph area; clicking on Select the window for the selection of the border thickness

opens.

Fig. 6.199 Tab Appearance: Stroke Selection window

The Outline paint field allows setting/modifying the color of the border of the graph

area; clicking on Select the window for the selection of the border color opens.

Fig. 6.200 Appearance tab: Outline Color window

The Background paint field displays and allows setting/modifying the background

color of the graph area; clicking on Select the window opens for the selection of




6-118LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

the background color.

Fig. 6.201 Appearance tab: Background Color window

The Orientation combo-box allows modifying the orientation of the graph:

• Vertical (default option): on the vertical axis is reported the RF RX field and

on the horizontal axis is reported the time intervals.

• Horizontal: on the vertical axis are reported the time intervals and on the

horizontal axis is reported the RF RX field.

Tab Other

The Other tab allows setting/modifying the displaying properties of the graph.

Fig. 6.202 Chart Properties window: Other tab

The Draw anti-aliased check-box allows enabling/disabling the anti-alias option, which

allows make more smooth the borders in the displaying of the graph. The Background

paint field allows setting/modifying the background color of the graph displaying

window; clicking on Select the window for the selection of the background color opens.





Fig. 6.203 Other tab: Background Color window

6.17.6.2 Data modality

In this modality, the data of the measures are displayed in table format.

The table is structured in three columns:

– Index: row progressive index.

– Time: date and time of data recording

– RX Field: value of the RF RX field expressed in dBm.

Fig. 6.204 Displaying of a measure in Data modality (example)

When the cursor of the mouse is placed on a selected row, a tooltip window opens,

reporting the information of the whole row in table format.




6-120LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.205 Data modality: tooltip window (example)

Clicking with the right button of the mouse on the table, a pop-up menu opens.

Fig. 6.206 Data modality: pop-up menu

In the pop-up menu there are the following items:

– Print to file

It allows saving the data of the measure into an ASCII file.

– Print

It allows printing directly the table. The window opens for the setting of the printing

properties and of selection of the printer to use.





Fig. 6.207 Data modality: print properties

– Save as

It allows saving the data of the measures into a file of “.csv ” format, suitable for the

post-processings (e.g.: creation of a graph) by means of a calculation sheet

application.

The window opens where specifying the name of the file and the relevant path

where saving the data of the measure.

Fig. 6.208 Data modality: selection of the output file

6.17.7 FTP Client

LCT integrates a FTP Client with customized interface, which allows the

reception/transmission of file from/to NE via FTP protocol (par. 6.7).

The FTP Client application is run when the “FTP Transfer” command is issued from a

NE plug-in.

For LCT, the download via FTP can be executed only towards NE that support the

IP protocol (e.g.: IP class radio equipment).




6-122LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Connection to NETo establish the connection to a NE via FTP Client, the login with administrator

privileges of NE is required (as “User Name” set “Admin”).

Some NE plug-in implements the functionality of automatic passing of the login

parameters to the FTP Client when the software download is commanded.

If FTP Client is commanded without the login parameters (or if the passed parameters

are wrong), the login window opens (Fig. 6.209) where it is necessary to manually set

the parameters required for the FTP connection. In case of connection via FTP protocol,

the Connection Mode field displays the connection modality used (“Active” o

“Passive”), which depends on FTP Server of the NE.

If the connection to the FTP Server of the NE does not succeed (e.g.: wrong password)

an error message is displayed (Fig. 6.210).

Fig. 6.209 FTP Client: Connect To Server window

Connection via FTP

Only for the Q-Adapter unit of the older TNMP/IP Dual Q-Adapter (unit provided

with embedded FTP Client), the software download can be executed via the FTP

Server application of the IIS service of Microsoft Windows.

For more detailed information concerning the download procedure via FTP Serverof the Microsoft Windows, refer to the equipment technical documentation.

For more detailed information concerning the download procedure of the NE

software, refer to the equipment technical documentation.

The software download via embedded FTP Client of LCT is not supported for the

SRT 1C, SRA 1 and SPS E equipment.

In order to execute the software download on these equipment, it is possible to

use the FTP Client tool of Microsoft Windows or a FTP Client tool of Third Parties.

The “User Name” and “Password” login parameters are “case sensitive”.


of the Admin user of FTP coincides with the password set for the Admin user

class of the NE Security.

Each change executed to the password of the Admin user class of the NE Security

is applied also to the password of the Admin user of FTP.





Fig. 6.210 FTP Client: connection refused

FTP Client graphical interface

After that the connection to NE has been established, the Software Download window

(Fig. 6.211) opens, which is subdivided in two areas:

– Left area: Tree of the local PC.

The content (files and folders) of the default system folder of the local PC is

displayed. The lower bar of the area reports the number of objects contained in the

tree.

– Right area: Tree of NE.

The content of the folder that contains the files of the software currently loaded on

the NE is displayed. The lower bar of the area reports the number of objects

contained in the tree.

In the status bar of the software download window, three fields are available:

– the first field displays the last executed operation or possible error messages

– the second field points out the type of protocol currently used for the file transfer:

FTP

– the third field points out the currently used connection (“Active” or “Passive”); this

indication is present only in case of connection via FTP protocol.

Fig. 6.211 FTP Client: Software Download window (example)

Connection with FTP protocol

Operation from FTP Client

From FTP Client, the typical copy, paste, delete operations on files/folders of Microsoft

Windows Explorer are allowed.

In particular, from FTP Client the following commands are available (Fig. 6.212):

– Copy: accessible from pop-up menu or via “Control” + “C” key combination

– Paste: accessible from pop-up menu or via “Control” + “V” key combination

– Delete: accessible from pop-up menu or via “Del” key




6-124LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

The Copy and Delete commands support the multiple selection.

The confirmation for the execution of each command is always required (Fig. 6.213).

From FTP Client, the file moving option is not supported; in fact, when a file is selected

and dragged from the local PC to the NE or vice versa, this file is not copied and pasted.

During the copy of a file, a window (Fig. 6.214) opens reporting the information about

the source and destination of the copied file and the progression bar.

Fig. 6.212 FTP Client: pop-up menu (example)

Fig. 6.213 FTP Client: window for operation confirmation (example)

Fig. 6.214 FTP Client: file copy (example)

For the “Paste” command, no check is executed on the overwriting of files with

the same name. If a file having the same name of another file already present intoin the destination folder is pasted, the file is overwritten (without any confirmation

request or displaying of warning message) and old file is lost.





6.17.8 Table management tool

In LCT, a modality for the management of the tables is implemented, common to the

tables of the different applications of NE plug-in.

This modality allows the user operating on a generic table by adding, deleting and

modifying rows.

Multiple selection of rows is not allowed; it is possible to operate only on one row at a

time.

Here below, the modalities with which a user can operate on a generic table are

described:

– The table opens in read-only mode

Fig. 6.215 Table in read only mode (example)

– Click on Modify to pass to “modify” mode and then to operate on the table.

In this mode, a column without heading is displayed next to the Index column,reporting, by means of graphic symbols, the operation executed on each row.

– Click on Reset to either make the table empty (if possible) or reset all the fields to

Default values. The specific behavior of the Reset button is specialized by each

pug-in.

This tool is specialized by the plug-in using it: in fact, the name of the columns in

the table and the specific operations performed on the NE by the different buttons

of the generic tool are different for each plug-in. For a detailed description about

the meaning of each table column, please refer to the corresponding plug-in

manual.




6-126LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 6.216 Table in “modify” mode (example)

– In “modify” mode, the following operations are possible on the table:

• Add row

To add a row, click on Add. In the editing window that opens, edit the fields

of the row and then click on Confirm.

Fig. 6.217 Add row (example)

The added row is characterized by the symbol and is highlighted with

green background.

Tab. 6.5 Operation symbols

Symbol Description

Row not modified

Row added

Row deleted

Row modified





Fig. 6.218 Table with row added (example)

• Delete row

To delete a row, select the row and then click on Delete.

The deleted row is identified by the symbol and is highlighted with yellow

background.

Fig. 6.219 Table with deleted (example)

• Modify row

To modify a row, select a row and then on Modify. In the editing window that

opens, modify the fields of the row and then click on Confirm.

Fig. 6.220 Modify row (example)




6-128LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

The modified row is identified by the symbol and is highlighted with yellow

background.

Fig. 6.221 Table with row modified (example)

– The not modified rows of the table are identified by the symbol and are not

highlighted (white background).

– To apply, and then make permanent, the changes executed on the table, click on

Apply Changes.

– To discard the changes executed on the table, click on Undo Changes.

6.17.9 Configuration of the RF frequency

LCT implements the application of the setting of the operating RF frequencies for the

equipment of the SRA L family.

Fig. 6.222 “Frequency Setting” window

Continuous frequency modality





Frequency Plan modality

6.17.10 Setting of date and time in the commissioning test

LCT implements the application for the setting of the date and time parameters in the

test of Timed Switching.

Fig. 6.223 “Date and Time” window (example)

For the setting modalities, refer to the equipment Manuals.

For the setting modalities, refer to the equipment Manuals.




6-130LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

B L A N

K P A G E



7 - OPERATING GUIDE OF NETBUILDER


7 OPERATING GUIDE OF NETBUILDER

7.1 NetBuilder Features

NetBuilder is a graphic tool for the creation/modification of the maps of LCT, which

constitute the graphic interface for the access to the radio equipment (NEs).

To create a map, it is advisable to execute the following procedure:

– create the image to use as background of the map (optional), using a common

graphical application (e.g. Paint) supporting the “.bmp ” , “.gif ” or “.jpg ” graphical

format

– import in NetBuilder the background bitmap of the map

– put on the background bitmap, in the proper positions, the icons of the NEs

– assign to each NE the corresponding name, which must be univocal

– set the network parameters for each NE; the network IP address must be univocal

– save the map created to a file with “.map ” format with the wished name.

NetBuilder implements also the Discovery function, which allows executing an

automatic search of the NEs and adding the discovered NEs in a new map.

The system allows two different automatic searching modes:

– automatic search of the NEs within a specified range of IP addresses

– automatic search of the contiguous NEs, starting from a specified NE, and

developing in cascade; it can be applied only to NEs that support the automatic

detection of the contiguous NEs.

NetBuilder is provided with the standard maps of connection with the local equipment


By means of NetBuilder for LCT, it is possible to create a map that satisfies the

following requirements:

– to contain at least one NE

– containing, at most, three NEs with TNMP protocol or 22 NEs with SNMPprotocol

– containing no sub-maps

– containing no NEs with different protocols (NEs with TNMP protocol and NEs

with SNMP protocol)

– having no map Security.

By default, no background bitmap is associated to a map, when it is created.




7-2LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

The background bitmap can be of any type (e.g.: geographical map indicating the

location of the various stations, a block diagram showing all the radio link

interconnections, etc...). During the creation of the bitmap, sufficient space must be left

in the position of the NEs to allow subsequent positioning of the corresponding icons, in

order to obtain a orderly and readable map. The following Figure shows an example of

map.

Fig. 7.1 Example of map

By default, the standard map “LOCALNE.map ” contains one NE with the following

configuration:


– IP address: 192.168.255.3By default, the standard map “LOCALNE_SNMP.map ” contains one NE with the


– protocol: SNMP

– IP address: 192.168.255.3

The IP address 192.168.255.3 is the preset address (10.10.10.10, for SRAL XD ).

NetBuilder allows inserting, into a map, NEs with TNMP EXT (extended TNMP) or

SNMP protocol.


In order to ensure the compatibility with maps created by means of old versions

of LCT (versions older than LCT V6.0), NetBuilder allows however opening and

managing maps containing NEs with TNMP base protocol or with automaticdetection of the TNMP protocol (TNMP Autodetect).





7.2 Operating Limits

Here below, there is the list of the current limits to be respected during the creation of

the maps in NetBuilder:

– Name of the map file (completed with

“relative” or “absolute” path): no blanks are allowed

– Max. number of NEs with TNMP protocol: 3

– Max. number of NEs with SNMP protocol:22

– Saving of the map background modalities:mode with max.

256 colors

– Maximum dimension of the background bitmap

(in “.bmp ”, “.gif” or “.jpg ” format) inserted into

a map: 64 Mbyte

By default, all the configuration files created by a user with the NetBuilder (map files and

relevant background bitmaps) are saved in the “LCT ” folder relevant to the system All


– “C:\Documents and Settings\All Users\Application Data\LCT ” in Microsoft

WIndows XP

– “C:\ProgramData\LCT ” in Microsoft WIndows Vista.

In detail, the map files are saved in the “ ...\LCT\Map ” sub-folder, while the background

bitmaps are saved in the “...\LCT\Background ”.

NetBuilder checks the following limits:

– max. number of NEs with TNMP protocol in each map (max. 3 NEs)

– max. number of NEs with SNMP protocol in each map (max. 22 NEs)

The limits on the background bitmaps are not checked by NetBuilder, but they must be

however respected during the creation of the maps in order to ensure a correct operation

of LCT.

Here below, there are the rules to be used in the configuration of the NE name:

– Allowed characters: alphanumeric charactersA...Z

,a...z

,0...9

plus the followingspecial characters < > ; , : . - _ [ + * ] \ | ! $ % & / ( ) = ? ^

– Allowed length: min. 1, max. 31 characters

A map of LCT cannot contain NEs with different protocols (NEs with TNMP

protocol and NEs with SNMP protocol).




7-4LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

7.3 User Interface

NetBuilder provides a Microsoft Windows typical user interface.

The GUI of NetBuilder (Fig. 7.2) consists of the following elements:

– Title bar (par. 7.3.1)

– Menu bar (par. 7.3.2)

– Tool bar (par. 7.3.3)

– Map displaying frame (par. 7.3.4)

– Status bar (par. 7.3.5).

The frames of the displaying area can be resized; each frame is provided with vertical

and/or horizontal scrolling bars, which are activated when the displayed window

exceeds the frame dimensions.

Fig. 7.2 User interface of the NetBuilder program

7.3.1 Title bar

The title bar always displays the name and the program icon.

Status bar

Title bar Menu bar Tool bar

Map Tree View

Edit Map frame





7.3.2 Menu bar

The menu bar displays the basic program menus:

– File Menu (par. 7.5)

– Edit Menu (par. 7.6)

– Options Menu (par. 7.7)

– Window Menu (par. 7.8)

– Help Menu (par. 7.9).

The menus are of the pull-down type.

7.3.3 Tool bar

The tool bar provides some push-buttons that allow the direct execution of a command,without using the pop-up menus.

The following table describes the available push-buttons.

The push-button for the insertion of NE is active only if at least one map is open.

Tab. 7.1 Tool bar

Icon Description

New option of the File menu (par. 7.5.1)

Open option of the File menu (par. 7.5.2)

Save option of the File menu (par. 7.5.5)

New → Net-Element option of the Edit menu(par. 7.6.3.1)




7-6LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

7.3.4 Displaying area

The displaying area is a frame structure that includes:

– a side frame (par. 7.3.4.1), identified by the Map Tree View tab, where the treestructures of the open maps are displayed

– a main frame or map frame (par. 7.3.4.2), identified by the Edit Map View tab,

where are displayed the open maps with their background bitmaps.

The main frame and the side frame can be resized in width.

7.3.4.1 Map Tree View frame

The MapTree View frame (Fig. 7.3) displays the tree structure of the open maps. In the

tree structure of a map, the root is the main map and the leaves are the single NEs.

Fig. 7.3 Map Tree View frame

Each object of the maps is represented by a specific icon (Tab. 7.2).

For each object, the name assigned in the map file is reported.

Each node and leaf of the tree (map, NE) has a pop-up menu (par. 7.10).

To select an object, click on the corresponding icon.

The operations for the selection of the map objects in the Edit Map View frame and in

the Map Tree View frame are equivalent, as they have effect on both the frames; the

selection of an object in the Map Tree View frame causes also the selection of the same

object in the Edit Map View frame and vice versa.

By means of a double click on the icons of the objects, the following operations are

executed:

– double click on the icon of NE: in the Edit Map View frame, the window of the object

properties is directly opened and the map window which contains the object isbrought in foreground (if open), with the focus on the object

Tab. 7.2 Map Tree View frame: objects icons

Icon Description

Map icon

NE icon

The pop-up menu that open over the icons of the objects in the Edit Map View

frame are identical to those that open over the icons of the objects of the Map TreeView frame.





– double click on the map icon: in the Map Tree View frame, the tree structure of the

map expands/hides and, in the Edit Map View frame, the map window is brought

in foreground.

7.3.4.2 Edit Map View frame

The Edit Map View frame (Fig. 7.4) displays the window of the open maps with their

background bitmaps.

For each NE, the name assigned in the map file is reported. The Edit Map View frame

is the area where the operations on the maps and on the objects contained in the maps

are executed.

Fig. 7.4 Edit Map View frame

Each map object is represented by a specific icon (Tab. 7.3).

The following Table reports the icons used in NetBuilder to represent the objects on the

maps.

To select an object, click on the corresponding icon.

The operations for the selection of the map objects in the Edit Map View frame and inthe Map Tree View frame are equivalent, as they have effect on both the frames; the

Tab. 7.3 Edit Map View frame: object icons

Icon Description

NE icon

The pop-up menus that open on the object icons in the Edit Map View frame are

identical to those that open on the element icons in the Map Tree View frame.

Map window

NE




7-8LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

selection of an object in the Map Tree View frame causes also the selection of the same

object in the Edit Map View frame and vice versa.

In an open map window, clicking with the right button of the mouse on a free area of the

window, the pop-up menu of the map opens.

By means of a double click on the icon, the window with the object properties directly

opens.

In the Edit Map View frame, the multiple selection of more NEs is possible too. To

execute a multiple selection, click on the icon of each object to select keeping pressed

the “Shift” key.

The multiple selection allows executing an editing command (cut, copy, paste, delete)

on more objects at the same time.

7.3.5 Status bar

The status bar displays messages and information useful for the operator (meaning of

the menu commands, status of the program, ...).





7.4 Program Start-Up

To start the NetBuilder proceed as follows:

– Execute the following shortcut (Fig. 7.5):

Start → Programs → Nokia Siemens Networks → LCT → NetBuilder.

– The starting window of the program opens (Fig. 7.6); it is now possible to create or

modify a map.

Fig. 7.5 NetBuilder: start shortcut

Fig. 7.6 NetBuilder: starting window




7-10LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

7.5 File Menu

The File menu (Fig. 7.7) allows opening, creating, importing, closing a map and exiting

from the program.The File menu has the following options:

– New (par. 7.5.1)

– Open (par. 7.5.2)

– Close (par. 7.5.3)

– Open auto.map (par. 7.5.4)

– Save (par. 7.5.5)

– Save As (par. 7.5.6)

– New Discovery (par. 7.5.7)

– Exit (par. 7.5.8)

Between the New Discovery and Exit command, the names of the last four opened

maps are displayed, in order to allow a fast selection of the map itself.

Fig. 7.7 File menu

7.5.1 New

The New command allows to create a new map.

A default name is assigned to the new map and this map is not associated to any

background bitmap.

The New command is always active.

7.5.2 Open

The Open command allows opening a new map, selecting it among the available ones

(Fig. 7.8).

The map files have “.map ” extension.

By default, map files are saved in the “...\LCT\Map ” folder relevant to the system All

Users profile (folder reachable an accessible to all users):


Windows XP





– “C:\ProgramData\LCT\Map ” in Microsoft Windows Vista.

If the map you want to open is already opened, NetBuilder displays a warning message

(Fig. 7.9).

An error message is displayed in the following cases:– the map you wish to open contains one or more NE over the max. allowed number:

max. three NEs with TNMP protocol or max. 22 NEs with SNMP protocol

(Fig. 7.10)

– the map you wish to open is a map provided with Security (Fig. 7.11).

These cases can occur when you attempt to open, from LCT, maps created by

NetBuilder tool from other supervision system (e.g.: Cell LCT or old NetViewer version).

It is possible to open from NetBuilder up to 16 maps at the same time.

The Open command is always active.

Fig. 7.8 Open Map window

Fig. 7.9 Message for already loaded map

From NetBuilder of LCT, it is possible to open and manage only maps that

satisfies the following requirements:– to contain at least one NE

– containing, at most, three NEs with TNMP protocol or one NE with SNMP

protocol

– containing no sub-maps

– containing no NEs with different protocols (NEs with TNMP protocol and NEs

with SNMP protocol)

– having no map Security.




7-12LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 7.10 Message of invalid map due to excessive number of NEs

Fig. 7.11 Message of map not loaded due to presence of Security

7.5.3 Close

The Close command allows closing the selected map (map where the focus is active).

The system asks for the confirmation of the saving of the possible changes made to the

map (Fig. 7.12).

If a background bitmap not present in the default “...\LCT\Background ” folder is

associated to the map, when the map is closed the system asks if you wish to copy the

background bitmap into the default “...\LCT\Background ” folder or not (Fig. 7.13).

The Close command is active only if at least one map is open.

Fig. 7.12 Saving confirmation window for the Close command

7.5.4 Open auto.map

The Open auto.map command allows opening directly the map created by means ofthe LCTStart application (“auto.map ” file of the default “...\LCT\Map ” folder). For the

LCTStart application, the following modalities are foreseen for the creation of a map:

– automatic creation of a map when a NE connected locally to the LCT PC is

detected

– creation of a map by means of the search of the NEs starting from a NE with known

IP address (“Find NE” functionality).

Only the last map created by LCTStart application is kept in memory; when the LCTStart

application creates a new map, the old “auto.map ” file is overwritten.

If you wish to save the map created by the LCTStart application, it is necessary to open,

from NetBuilder, the “auto.map ” map and, then, execute a Save As command(par. 7.5.6).

If the user closes an empty map just created and without a background bitmap

(“Close” option on an empty map created with the “New”/“New Discovery” option

and not saved yet), the system does not save this map.





The Open auto.map command opens always the current “auto.map ” file, which is the

last map created by the LCTStart application.

The Open auto.map command is inactive if the “auto-map ” map file is not present in the

default “...\LCT\Map ” folder.

7.5.5 Save

The Save option allows saving the selected map (map on which it is activated the focus)

with the current name.

The Save command is active only if at least one map is open.If at least one change has been made to the map, at the execution of the Save

command, the program assigns the “.bak ” extension to the map file with the same name

already present on the hard-disk.


associated to the map, when the map is closed the system asks if you wish to copy the

background bitmap into the default “...\LCT\Background ” folder or not (Fig. 7.13).

Fig. 7.13 Confirmation for the bitmap copy in the “Background” folder

7.5.6 Save As

The Save As command allows saving the current map (map where the focus is active),

specifying the desired identification name and path (Fig. 7.14).

By default, map files are saved in the “...\LCT\Map ” folder relevant to the system All

Users profile (folder reachable an accessible to all users):


Windows XP– “C:\ProgramData\LCT\Map ” in Microsoft Windows Vista.

If a map file with the same name already exists into the destination directory, the system

requests the saving confirmation (Fig. 7.15) and it assigns the extension “.bak ” to the file

with the same name.

If a background bitmap not present in the default “...\LCT\Background ” folder (or in its

sub-folder) is associated to the map, when the map is closed the system asks if you wish

to copy the background bitmap into the default “...\LCT\Background ” folder or not

(Fig. 7.13).

If the user saves a new map (“Save” option on a map created with the “New”

option and that has not saved yet), the program automatically executes the “Save

As” command, because it is necessary to specify the map name at the first

saving.

Do not assign the “auto.map ” name to the maps created by NetBuilder, which is

the name predefined and not modifiable of the map automatically created by theLCTStart application.




7-14LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

The Save As command is active if at least one map is open.

Fig. 7.14 Save As window

Fig. 7.15 Overwriting confirmation file map window

7.5.7 New Discovery

The New Discovery sub-menu allows executing an automatic search of the NEs based

on the set option, with the creation of a new map and the insertion of the detected NEs

into the new map. The system allows two different modes for the execution of the

automatic search (Fig. 7.16):

– Standard Discovery (par. 7.5.7.1)

– Smart Discovery (par. 7.5.7.2).

Fig. 7.16 New Discovery menu





7.5.7.1 Standard Discovery

The Standard Discovery automatic search allows executing the automatic search of the

NEs within a specified range of IP addresses; it can be applied to all the NEs that support

the TNMP EXT protocol on TCP/IP or the SNMP protocol on UDP/IP.

The dynamic searches are the following ones and they are repeated for each IP address

within the specified range:

– the system requires for the TCP/IP (TNMP EXT) or UDP/IP (SNMP) connection

with IP address

– if within the preset waiting time, the system detects a socket error or it does not

receive any answer, it retries for a certain number of times according to the

searching parameters

– the system considers the search procedure as failed if all the attempts to this IP

address have had a negative result; vice versa the system considers the search as

successful and it creates the icon of the detected NE

– the system continues processing the next IP address.

On the New Discovery → Standard Discovery command selection, the program

displays the New Discovery window (Fig. 7.17) where the map name and the searching

range (starting and ending IP address) must be specified; the total number of the IP

addresses must not be greater than 256x256 = 65536, that is the starting IP address

and the ending one have to belong to the same network.

After the setting of the search parameters, click on OK to start the search of the NEs.

In the following cases, the system displays an error window:

– the map name has not been specified (Fig. 7.18)

– an already existing name has been specified for the map (Fig. 7.19)

– the search range has not been specified (Fig. 7.20)

– an invalid search range has been specified (Fig. 7.21).

When the system starts the automatic search, it opens the map and displays a window

that shows the progress status of the search (Fig. 7.22). If the search has a negative

result, the system displays a message that points out that no NE has been found

(Fig. 7.23); therefore, the map results empty. When the system finds a NE, it adds the

relevant icon marked by the IP address (Fig. 7.24) into the map.

The system subdivides the search of the NEs into packets of IP addresses. For each

packet, the system executes the searching test at the same time for all the IP addresses

of the packet.

If the range of the specified IP addresses is too large, the search can take a lot of

time.

The search automatically stops when the maximum number of NEs, which a map

can contain, is reached.

A map of LCT can contain, at most, three NEs with TNMP protocol or 22 NEs with

SNMP protocol.






7-16LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

The system displays the icons of the NEs side by side starting from the L.H. side upper

corner of the map (Fig. 7.25); the adding order is from L.H. side to R.H. side and from

up side to down side.

It is always possible to stop the search, clicking on Stop (Fig. 7.22); in this case, the

system creates a map with the NEs detected until to the stop of the search. When the

search ends and the system has created the map, it is possible to work on the map (to

save/close the map, to insert a background bitmap, ...).

No background bitmap is associated, by default, to the created map.

The searching time depends on the set searching range and parameters (par. 7.7.1).

During the search, all the NetBuilder commands are inactive, except Stop. The

Standard Discovery command is always activated.

Fig. 7.17 New Discovery window (Standard Discovery)

Fig. 7.18 Message for missing map name (Standard Discovery)

Fig. 7.19 Message for map name already existing (Standard Discovery)

Fig. 7.20 Message for missing search range (Standard Discovery)

Fig. 7.21 Message for invalid search range (Standard Discovery)





Fig. 7.22 Discovery in progress window (Standard Discovery)

Fig. 7.23 Message of none NE discovered (Standard Discovery)

Fig. 7.24 Example of NE icon adding (Standard Discovery)




7-18LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 7.25 Example of NE icon displacement (Standard Discovery)

7.5.7.2 Smart Discovery

The Smart Discovery automatic search starts from a specified NE and it develops in

cascade to the contiguous NEs; the search procedure stops when it finds a NE that does

not allow the automatic detection of the contiguous NEs.

At the New Discovery → Smart Discovery command, the system opens the New

Discovery window (Fig. 7.29), for the setting of the search parameters:

– Name of the map

Specify, in the Map Name field, the name to associate to the map where the

discovered NEs will be inserted; the map is automatically created at the start of the

automatic search.

– Start IP address

The following options are possible:

• Start from local NE radio-button selected: the search is executed starting

from the NE locally connected to the machine where LCT is installed (LCTPC). It is not applicable to FlexiPacket NEs.

The Smart Discovery automatic search can be applied to the following NE types:

– NEs which support the TNMP EXT protocol on TCP/IP and implement the

functionality of automatic detection of contiguous NEs

– NEs which support the SNMP protocol on UDP/IP; for each NE SNMP, the

automatic detection of the contiguous NEs is based on the analysis of the

“ipRouteTable” of the equipment MIB.

– From LCT 3.4 onwards the Smart Discovery can be applied to

FlexiPacketHub, FlexiPacket FirstMile, FlexiPacketRadio and FlexiPacket

MultiRadio NEs too. In this case the discovery is based on the analysis of a

specified table of the equipment MIB and on the LLDP protocol respectively





• Start from radio-button selected: the search is executed starting from the IP

address specified manually in the field next to the radio-button.

After the setting of the search parameters, click on OK to start the search phase of the

NEs; the system displays an error window in the following cases:– the map name has not been specified (Fig. 7.30)

– an already existing name has been specified for the map (Fig. 7.31)

– the starting IP address has not been specified in case of search with Start from

option (Fig. 7.32)

– an invalid starting IP address has been specified in case of search with Start from

option (Fig. 7.33).

When the system starts the automatic search procedure, it opens the map and displays

a window that shows the progress status of the search procedure (Fig. 7.34).

If the search procedure has a negative result, the system displays a message that points

out that no NE has been found (Fig. 7.35); therefore, the map results empty.

When the system finds a NE, it adds into the map the relevant icon, marked by the IP

address (Fig. 7.36).

The system displays the icons of the NEs side by side starting from the upper L.H. side

corner of the map (Fig. 7.37); the adding order is from L.H. side to R.H. side and from

up to down.

It is always possible to stop the search, clicking on Stop (Fig. 7.34); in this case, the

system creates a map with the NEs detected up to the stop of the searching procedure.

At the end of the search procedure and after the creation of the map, the user can work

on the map (to save/to close the map, to insert a background bitmap, ...).

By default, the system does not assign any background bitmap to the created map.

In case of FlexiPacket Hub or FlexiPacket FirstMile NEs, smart discovery creates a map

with the IDU the discovery started from all the ODUs and, in case of IDU-IDU link

between FPFM NEs, the IDUs directly connected to it.

The NEs are distributed as foreseen by the usual FlexiPacket Station layout.

For each Ethernet link, the information of the associated IDU's module and port is

displayed.

The radio link is indicated by an arrow. If one or more LPGs have been configured, they

are indicated by means of a red box surrounding the involved radio NEs (Fig. 7.26).

These graphical objects cannot be modified, only the NEs may be moved, but it's not

advisable to do it.If remote ODUs and IDUs are reachable, they are discovered too.

The remote stations show, besides the IDU, only the ODUs involved in the radio links

pointing to the first one (Fig. 7.26 and Fig. 7.27).

Starting from the first station the discovery stops after each possible remote station is

The search automatically stops when the maximum number of NEs, which a map

can contain, is reached.


SNMP protocol.






7-20LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

discovered compatibly with LCT max NEs limits.

For "remote station" we intend the one reachable by means of a single hop (Radio link)

between a FPR or FPMR of the first station and its peer or directly by an Ethernet link

from the local IDU (IDU-IDU connection) (Fig. 7.28).

Fig. 7.26 Smart discovery of Flexipacket Stations (1+1 and 1+0 links

Thanks to LLDP protocol also the ODUs remotely connected to the active Radio NEs

are found.

The radio link is indicated by an arrow (Fig. 7.28).

Fig. 7.27 Smart discovery of Flexipacket Stations (FPFM IDU-IDU link)

Fig. 7.28 Smart discovery of Flexipacket Stations (1+0 links)

The duration of the search procedure depends on the set parameters (par. 7.7.1) and

on the number of NEs in cascade that support the automatic detection of the contiguous

NEs. During the searching procedure, all the NetBuilder commands are deactivated,

except Stop. The Smart Discovery command is always active.





Fig. 7.29 New Discovery window (Smart Discovery)

Discovery with “Start from local NE” option

Discovery with “Start from” option

Fig. 7.30 Message for map name insertion not executed (Smart Discovery)

Fig. 7.31 Message for map name already existing (Smart Discovery)

Fig. 7.32 Message for missing starting IP address (Smart Discovery)




7-22LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Fig. 7.33 Message for invalid starting IP address (Smart Discovery)

Fig. 7.34 Discovery in progress window (Smart Discovery)

Fig. 7.35 Message of none NE discovered (Smart Discovery)

Fig. 7.36 Example of NE icon adding (Smart Discovery)





Fig. 7.37 Example of NE icon displacement (Smart Discovery)




7-24LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

7.5.8 Exit

The Exit command allows exiting from the program.

If a map is open, the confirmation of the exit from the program (Fig. 7.38) is required. If

a map has been opened but not saved, the confirmation for the map saving (Fig. 7.39)

is required too. This confirmation is not required if the open map is a new empty map

where no operation has been executed.

The Exit command is always active.

Fig. 7.38 Confirmation window for the program exit

Fig. 7.39 Confirmation window for the map saving at the program exit

7.6 Edit Menu

Edit menu (Fig. 7.40) contains the following commands regarding the map objects.

Edit menu has the following options:

– Arrange (par. 7.6.1)

– Paste (par. 7.6.2)

– New (par. 7.6.3)

– Background (par. 7.6.4)

The commands of the Edit menu are inactive if at least a map is not open.

The commands of the Edit menu operate on the map or on the NE, which the focus is

active on.

Fig. 7.40 Edit menu

If the open map is a new map not saved yet where some operations have been

executed, the program automatically executes the “Save As” command, as you

must specify the map name the first time you save it.





7.6.1 Arrange

The Arrange option allows positioning automatically the icons of the NE on the current

map starting from the upper L.H. side corner.

The Arrange option is active only if the map contains some NE.

7.6.2 Paste

The Paste option allows pasting the NE that has been previously cut/copied on the

current map. Even a multiple selection of NEs can be pasted.

The Paste option is active only if a NE has been cut/copied.

It is not possible to paste an NE if the destination map already contains an NE with the

name/address equal to the one of the NE to be pasted; in this case, the system displays

an error window (Fig. 7.41).

It is not possible to paste one or more NEs if the destination map, as consequence ofthis operation, will contain a number of NEs exceeding the allowed limit; in this case, an

error window is displayed (Fig. 7.42).

To prevent duplication errors relevant to the name/address of the NE, it is not possible

to paste on a map some NE copied from the same map.

Fig. 7.41 Error window for object copying operation not allowed

Fig. 7.42 Error window for pasting of NEs exceeding the allowed number

7.6.3 New

The New sub-menu (Fig. 7.43) contains the command for the insertion of new NEs into

the map:– Net-Element (par. 7.6.3.1)

The Net-Element command of the New sub-menu is active if at least one map is open;

it is inactive if a NE is selected.

Fig. 7.43 New Menu




7-26LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

7.6.3.1 Net-Element

The Net-Element command allows inserting a new NE into the current map. After this

command, the system opens the NE properties window (Fig. 7.44).

If the Net-Element command is executed on a map that already contains the max.

allowed number of NEs (max. three NEs with TNMP protocol or max. 22 NEs with SNMP

protocol), an error window is displayed (Fig. 7.45)..

Fig. 7.44 NE insertion window

Fig. 7.45 Error window for max. limit of NEs

The NE configuration parameters are the following ones:

– NE Name

It is the name of the NE, which must be univocal.

It is recommended to enter both the name and the network address for each NE.

If only the network address is entered, the network address itself is assumed as NE

name.

If only the name is entered, the system will attempt however to resolve the

host-name (for example, via a Server DNS or the “hosts” system file).


SNMP protocol.



The name of a NE can be, at most, 31 characters long.

Blank spaces cannot be used when assigning the NE names.





– Synchronization

The user can, selecting the Synchronization check-box, synchronize the date and

time of the NE with the local date and time of the LCT PC (proprietary

synchronization mode). On the contrary, the synchronization via NE Manager is

disabled. By default, the Synchronization check-box is not selected.

Some equipment (refer to Customer Release Notes) support also the

synchronization via SNTP protocol.

The SNTP synchronization and the synchronization via NE Manager are in

alternative.

– Protocol

It is the application protocol for the management of the NEs; it is possible to have

the following options:

• TNMP EXT: TNMP extended on IP

• SNMP: SNMP on IP.

The management application protocol depends on the type of radio equipment.

– Addresses

It allows setting/displaying the network parameters of the NE.

To set the network parameters, open the configuration window (par. 7.6.3.1.1)

clicking on Settings.

Click on OK to confirm the executed settings.

In the following cases, the system displays an error window:

– neither the name or the network address of the NE are specified (Fig. 7.46)– in the map a NE with the same name (or IP address) is already present (Fig. 7.47)

– the new NE has a protocol different from that of the NEs already present in the map

(Fig. 7.48)

– the name of the NE is incompatible with the advanced settings (Fig. 7.49); this

condition occurs when an IP address different from that already set in the Address

field is set as NE Name.

The characters “*” and “?” are special characters (wildcard) used in the search

queries of the report applications; therefore, it is suggested not to use these

characters in the NE names (even if it is possible to use them).

If the SNTP synchronization ia already active on a NE, it is not possible to activate

the synchronization via NE Manager when you execute the login to the NE; in this

case, the enabling of the “Synchronization” check-box is not meaningful.

NetBuilder allows inserting, into a map, NEs with TNMP EXT (extended TNMP) or

SNMP protocol.

In order to ensure the compatibility with maps created by means of old versionsof LCT (versions older than LCT V6.0), NetBuilder allows however opening and

managing maps containing NEs with TNMP base protocol or with automatic

detection of the TNMP protocol (TNMP Autodetect).




7-28LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Once a new NE has been inserted, it is possible, using the mouse, to select and move

the relevant icon in the wished point of the map.

Fig. 7.46 Error window for NE name or/and network address not set

Fig. 7.47 Error window for NE name duplicated

Fig. 7.48 Error window for NEs with different protocol

Fig. 7.49 Error window for NE name not compatible with the IP address

7.6.3.1.1 NE advanced properties

For the NE, it is necessary to set the IP address ( IP Address) (Fig. 7.50), which must

be univocal.

It is recommended to enter both the name and the IP address for each NE.

If only the IP address is entered, the IP address itself is assumed as NE name.

If only the name is entered for a NE, the system will attempt however to resolve the

host-name (for example, via a Server DNS or the “hosts ” system file).

Click on OK to confirm the set configurations. An error window is displayed in the following cases:

– an invalid IP address is set (Fig. 7.51)

– a map of the NE with the same IP address is already present (Fig. 7.52)

Fig. 7.50 Properties window





Fig. 7.51 Error window for duplicated NE address

Fig. 7.52 Error window for IP address of the NE not valid

7.6.4 Background

Background menu contains the commands to manage the background bitmaps of the

map.

Background menu (Fig. 7.53) has the following options:

– Insert (par. 7.6.4.1)

– Delete (par. 7.6.4.2)

– Change (par. 7.6.4.3)

– Properties (par. 7.6.4.4)

For the background bitmaps, the following formats are supported:

– .bmp

– .jpg (.jpeg )

– .gif

The commands of the Background menu are inactive if a NE is selected.

Up to version V6.7 of LCT, for the background bitmaps only the “ .bmp ” format

was supported.

The bitmaps used as map backgrounds must have a common color palette; on the

contrary, it is necessary to increase the desktop color depth (using the “True

Color” mode, there is no problem).

By default, the background bitmaps are contained in the “...\LCT\Background ”

folder relevant to the system All Users profile (folder reachable and accessible to

all users):

– “C:\Document and Settings\All Users\Application Data\LCT\Background ” in

Microsoft WIndows XP

– “C:\Program Data\LCT\Background ” in Microsoft Windows Vista.


associated to the map , when the map is closed the system asks if you wish to

copy the background bitmap into the default “...\LCT\Background ” folder or not

(Fig. 7.13).




7-30LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

The Background commands operate on the current map (map where the focus is

active).

Note that the background bitmap of a map is not contained into the map file, but it is

always recalled at the map opening as an external link to a file.

Fig. 7.53 Background Menu

7.6.4.1 Insert

The Insert command allows inserting a background bitmap into the current map,

selecting among the available ones (Fig. 7.54).

By default, the “Background ” sub-folder of “LCT ” folder relevant to the system All Users

profile (folder reachable and accessible to all users) is set as folder containing the

background bitmaps; it is however possible to insert bitmaps contained in other folders.

The command Insert is active only if the map is without background.

Fig. 7.54 Open window for the insertion of the background bitmap

7.6.4.2 Delete

The Delete command allows deleting the background bitmap of the current map.

The command is active only if the map has already a background.





7.6.4.3 Change

The Change command allows changing the background bitmap of the current map

selecting among the available ones (Fig. 7.55).

By default, the “Background ” sub-folder of “LCT ” folder relevant to the system All Users

profile (folder reachable and accessible to all users) is set as folder containing the

background bitmaps; it is however possible to insert bitmaps contained in other folders.

The command Change is active only if the map has already a background.

Fig. 7.55 Open window for the modification of the background bitmap

7.6.4.4 Properties

The Properties command allows displaying the properties (filename, size,...) of the

background bitmap (Fig. 7.56).

The command is active only if the current map has already a background.

Fig. 7.56 Background Properties window




7-32LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

7.7 Options Menu

The Options menu (Fig. 7.57) includes the option for the configuration of the

parameters of automatic discovery of NEs:

– Discovery (par. 7.7.1)

Fig. 7.57 Options menu

7.7.1 Discovery

The Discovery command allows setting the parameters for the automatic search of the

NEs; the command is followed by the opening of the Discovery Options window(Fig. 7.58), where the user can set the following parameters:

– Protocol

They are the management application protocols used for the automatic search of

NEs; the following protocols are available:

• TNMP EXT: search of NEs with TNMP extended protocol on TCP/IP

• SNMP: search of NEs both with SNMP protocol on UDP/IP

The protocols used by the automatic search are listed in the list box. To add a

protocol, click on Add; the Add Protocol window (Fig. 7.59) opens, where it is

possible, to select the protocol to add. The Add key is active only if at least one

protocol to add is available. To remove a protocol, it is necessary to select it in the

list-box and then click on Remove. The Remove key activates when a protocol isselected in the list-box. The automatic search is executed giving priority to the first

protocol in the list; it is possible to change the order of the protocols by means of

the Up and Down keys. If only one protocol is present in the list-box, the Up and

Down keys are inactive. In the list-box it is possible to select only one protocol at

a time (the multiple selection of more protocols is not allowed).

– Interval between requests

It is the time range (in seconds) between a TCP/IP connection request and the next

one.

– Connect parameters

The NE search is subdivided into packets of IP addresses; for each packet, the

search test is executed at the same time for all the IP addresses of the packet:• Simultaneous connections: it is the number of IP addresses relevant to

each search packet

• # attempts: it is the number of attempts, inside each single packet of IP

addresses, to be executed for each IP address for whom the NE searching

test fails.

– TNMP connect timeout

It is the maximum waiting time of a TCP/IP connection; it is possible to set manually

(Customize) the maximum waiting time (expressed by seconds) or, alternatively,

to set the default one of the TCP/IP driver (Default socket timeout). If the default

value is set, we can verify that the automatic search does not succeed in loading

the NEs; in this case, it is necessary to increase the value of the TNMP connecttimeout parameter.





Click on OK to apply and activate the settings.

Options option is always active.

Fig. 7.58 Discovery Options window

Fig. 7.59 Add Protocol window

7.8 Window Menu

The Window menu (Fig. 7.60) makes available the typical commands necessary to

manage the Microsoft Windows open windows.

The Window menu has the following options:

– Cascade (par. 7.8.1)

– Tile (par. 7.8.2)

– Close All (par. 7.8.3)

Then, it makes available the dynamic list of the open windows and marks the current

one. This function allows to reach easily a window, if there are a lot of open windows at

the same time.

Fig. 7.60 Window Menu




7-34LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

7.8.1 Cascade

The Cascade command positions all the open windows over-placing and phasing them

in such a way to let visible the relevant menu bar of each one. The current window is

positioned at front.



7.8.2 Tile

The Tile command positions all the open windows side by side.



7.8.3 Close All

Close All command closes all the opened windows; this closes all the maps.

7.9 Help Menu

The Help menu (Fig. 7.61) allows displaying the useful information concerning the use

of the NetBuilder.

The Help menu has the following options:

– Contents (par. 7.9.1)

– Using Help (par. 7.9.2)

– About (par. 7.9.3)

Fig. 7.61 Help Menu

7.9.1 ContentsThe Contents command allows opening the Help of the NetBuilder.

7.9.2 Using Help

The Using Help command allows displaying information concerning the help itself.

7.9.3 About

The About command allows displaying information concerning the currently used

version and build of NetBuilder (Fig. 7.62).





Fig. 7.62 About NetBuilder window (example)

7.10 Pop-Up Menu

A specific pop-up menu is available on each object of NetBuilder (map, NE):

– Map pop-up menu (par. 7.10.1)

– NE pop-up menu (par. 7.10.2)

7.10.1 Map pop-up menu

This pop-up menu is activated through one of the following mode:

– positioning the mouse pointer on an empty point of the main map, not used for

icons of NE.

– positioning the mouse pointer on the main map icon into the map tree structure and

clicking with the right-hand button.

The Map pop-up menu (Fig. 7.63) makes available the same functions of the Edit menu

(par. 7.6):

– Arrange (par. 7.6.1)

– Paste (par. 7.6.2)

– New (par. 7.6.3)

– Background (par. 7.6.4).

Fig. 7.63 Map pop-up menus




7-36LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

7.10.2 NE pop-up menu

The NE pop-up menu is opened in one of the following ways:

– clicking with the right-hand button of the mouse on the icon of the NE in the mapframe

– clicking with the right-hand button of the mouse on the icon of the NE in the network

frame

The NE pop-up menu (Fig. 7.64) has the following options:

– Properties (par. 7.10.2.1)

– Cut (par. 7.10.2.2)

– Copy (par. 7.10.2.4)

– Delete (par. 7.10.2.4)

Fig. 7.64 NE pop-up menu

7.10.2.1 NE Properties

The Properties option allows setting/changing the properties of the selected NE

(par. 7.6.3.1); at the command execution, the system opens the window of the NE

properties (Fig. 7.65). The user can execute this command also clicking twice directlyon the NE icon (in the map frame or in the network frame).

Fig. 7.65 Window of the NE properties

Starting from LCT V6.0, NetBuilder allows inserting, into a map, NEs with TNMP

EXT (extended TNMP) or SNMP protocol.


In order to ensure the compatibility with maps created by means of old versions

of LCT (versions older than LCT V6.0), NetBuilder allows however opening and

managing maps containing NEs with TNMP base protocol or with automatic

detection of the TNMP protocol (TNMP Autodetect).





7.10.2.2 Cut NE

The Cut command allows cutting the NE in order to paste it, through the Paste

command (par. 7.6.2), to another position of the same map or to another map.

7.10.2.3 NE Copy

The Copy command allows copying the NE in order to paste it to another position

through the Paste command (par. 7.6.2) in another map.

In order to prevent errors due the duplication of name/IP address of NE, it is not possible

to paste on the same map NEs copied from the same map.

7.10.2.4 NE Delete

The Delete command allows deleting the NE.The system asks for the execution confirmation of the NE deleting command (Fig. 7.66).

Fig. 7.66 Confirmation window for NE deletion




7-38LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

B L A N

K P A G E



A - LICENSES TO USE THE SOFTWARE

A-1LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011

A LICENSES TO USE THE SOFTWARE

A.1 License to Use the LCT

Here below the license to use the LCT is reported.

The license is available also on file (file “License.txt ”), in the folder “LCT\Licenses ”.




A-2LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

General Terms and Conditions for Granting the Use of Software Products of

NetViewer NME Suite

Copyright (c) Nokia Siemens Networks 2008 - All rights reserved

1. Software Licence

1.1 Nokia Siemens Networks grants to the Customer the nonexclusive,

non-transferable licence to use the software products in object code form, as delivered

in unchanged format (the "Software"). The NetViewer Server Software, or NCT Software

or LCT LinkViewer Software may be stored only in one hardware system unit while the

other SW components can be installed as required and defined by the installation

manuals.

1.2 All rights, title and interest in and to the Software and Documentation, other than

those expressly granted to Customer herein, shall remain vested in Nokia Siemens

Networks or its third party licensors. Customer shall not, and shall prevent others from,

copying, translating, modifying, creating derivative works, disassembling, reverse

engineering, decompiling, encumbering or otherwise using the Software and

Documentation except as specifically authorized hereunder or by compulsory law.

1.3 The Customer must ensure at all time that the Software, the copies and

Documentation will not be made available to third parties. The Customer may disclose

the Software, the copies and Documentation to own employees only on a need to know

basis and only if such employees are bound to confidentiality by their labour contracts

or otherwise.

2. Warranty

2.1 Nokia Siemens Networks warrants that the Software as originally delivered to

Customer will work substantially in accordance with the specifications set out in the

Documentation for a period specified in the schedule attached hereto from the date of

delivery, when used in accordance with the instructions given by Nokia Siemens

Networks. In case of incompliance with the aforementioned warranty, Nokia Siemens

Networks shall use reasonable efforts to correct the error. The prerequisite for such error

correction is that the error can be reproduced, and that it occurs in the last correction

level of Software supplied to the Customer. Nokia Siemens Networks will be given all

documentation and information required for the error recovery.

2.2 The foregoing shall be the sole liability of Nokia Siemens Networks and the sole

remedy of Customer for warranty. Nokia Siemens Networks expressly disclaims all

other warranties, whether express or implied, including, without limitation, warranties or

representations of workmanship, merchantability, fitness for a particular purpose,

durability, or that the operating of the Software will be error free. In addition to the

warranties given by Nokia Siemens Networks, no other warranty shall be given and any

warranty of third party suppliers of Nokia Siemens Networks is hereby expressly

disclaimed.

3. Prices, Conditions of Payment

3.1 The payments for Software licences are due with receipt of the invoice byCustomer.





In any case the Customer is not entitled to use the Software before payment is received

by Nokia Siemens Networks.

3.2 For any services requested by Customer and rendered by Nokia Siemens Networks

and without or exceeding the scope of a valid Maintenance Contract, Nokia Siemens

Networks may charge to Customer and Customer shall pay to Nokia Siemens Networks

the then current list prices.

4. Licence Termination

4.1 The licence granted herein shall become effective upon delivery of the Software to

Customer.

4.2 Nokia Siemens Networks may forthwith terminate the licence granted herein upon

written notice to Customer (a) if any payments due to Nokia Siemens Networks are not

paid by Customer within thirty (30) days of the date on which payment is due; (b) ifCustomer becomes bankrupt, makes an assignment for the benefit of its creditors, or if

its assets vest or become subject to the rights of any trustee, receiver or other

administrator; (c) if bankruptcy, reorganization or insolvency proceedings are instituted

against Customer and not dismissed within 15 days; or (d) if Customer breaches a

material provision of this Agreement and such breach is not rectified within 30 days of

receipt of notice of the breach from Nokia Siemens Networks.

4.3 Upon termination of the licences granted herein, Customer shall at Nokia Siemens

Networks option either return or destroy all copies of the Software and Documentation,

whereby in case of destruction Customer shall forward immediately after destruction a

certificate to Nokia Siemens Networks confirming that all copies have been destroyed.All obligations of Customer accrued prior to termination, and those obligations relating

to confidentiality and non-use, shall survive termination.

5. Collateral Agreements, Export Licences, Jurisdiction

5.1 Collateral agreements shall not be binding unless effected in writing.

5.2 The export of the software and documentation may be subject to authorization see

delivery notes and invoices.

5.3 This contract shall be governed by the laws of Italy without regard to its conflicts of

law rules. This AGREEMENT and the conduct of the parties hereto shall be governed by the laws

of the Republic of Italy. By opening this package you consent to the jurisdiction of the

courts of the Republic of Italy for final, binding resolution of any dispute arising from this

AGREEMENT, or any action by you, in contract, or otherwise, in violation of the rights

and obligations set forth herein. Any judgment of such court shall be entitled to be

enforced in any court of appropriate jurisdiction.

5.4 All disputes arising out of or in connection with the present Agreement including its

validity, shall exclusively and finally be settled as specified in the contract.

5.5 The foregoing terms and conditions shall be subject to an individual agreement inwriting reached by the parties




A-4LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

6. Trademarks

6.1 Every mark is trademarks or registered trademarks of their respective owners.

7. Third Party Code

7.1 The product contains, among other things, embedded Open Source Software,

licensed under an Open Source Software License and developed by third parties. These

embedded Open Source Software files are protected by copyright. Your rights to use the

Open Source Software beyond the mere execution of Nokia Siemens Networks

program, is governed by the relevant Open Source Software license conditions.

7.2 Your compliance with those license conditions will entitle you to use the Open

Source Software as foreseen in the relevant license. In the event of conflicts between

Nokia Siemens Network license conditions and the Open Source Software license

conditions, the Open Source Software conditions shall prevail with respect to the OpenSource Software portions of the software. The Open Source Software is licensed

royalty-free

7.3 You can request the corresponding source code from NOKIA SIEMENS

NETWORKS by paying a fee for the physical act of transferring the copy. Please send

your specific request, together with a receipt indicating the date of purchase, within three

years of your purchase, together with the software release number to Nokia Siemens

Networks SpA; http://www.nokiasiemensnetworks.com.

7.4 NOKIA SIEMENS NETWORKS provides no warranty for the Open Source

Software programs contained in this device, if such programs are used in any mannerother than the program execution intended by NOKIA SIEMENS NETWORKS. The

licenses listed in the <Product

Name>_<Version>_THIRDPARTYLICENSEREADME.txt file define the warranty, if

any, from the authors or licensors of the third party software. NOKIA SIEMENS

NETWORKS specifically disclaims any warranties for defects caused by altering any

Open Source Software program or the product’s configuration. You have no warranty

claims against NOKIA SIEMENS NETWORKS in the event that the Open Source

Software infringes the intellectual property rights of a third party. Technical support, if

any, will only be provided for unmodified software.

7.5 Additional copyright notices and licence terms applicable to portions of the Software

are set forth in the <Product Name> <Version> THIRDPARTYLICENSEREADME.txtfile.

YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT, UNDERSTAND

IT AND AGREE TO BE BOUND BY ITS TERMS AND CONDITIONS. YOU FURTHER

AGREE THAT IT IS THE COMPLETE AND EXCLUSIVE STATEMENT OF THE

AGREEMENT BETWEEN YOU AND NOKIA SIEMENS NETWORKS, WHICH

SUPERSEDES ANY PROPOSAL OR PRIOR AGREEMENT, ORAL OR WRITTEN,

AND ANY OTHER COMMUNICATIONS BETWEEN YOU AND NOKIA SIEMENS

NETWORKS RELATED TO THE LICENSED SOFTWARE. THIS AGREEMENT IS

WRITTEN IN THE ENGLISH LANGUAGE ONLY. YOU CONSENT TO SUCHEXCLUSIVE USE OF THE ENGLISH LANGUAGE.





A.2 Licence to Use the Third Party Products

Here below the licenses to use all the Third Party products used in LCT and included

into the basic provision are reported.The licenses are available also on file (file “LCT_8.0_ThirdPartyLicenseReadme.txt ”) in

the folder “LCT\Licenses ”.




A-6LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

DO NOT TRANSLATE OR LOCALIZE.

The following softwares may be included in this product:

Infobus 1.2 (infobus.jar)

The InfoBus Technology

Release 1.2

License Agreement

SUN MICROSYSTEMS, INC. (``SUN'') AND LOTUS DEVELOPMENT CORPORATION

(``LOTUS'') ARE WILLING TO LICENSE INFOBUS(tm) SOFTWARE (``SOFTWARE'')

TO YOU ("CUSTOMER") ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF

THE TERMS CONTAINED IN THIS LICENSE AGREEMENT ("AGREEMENT"). READ

THE TERMS AND CONDITIONS OF THE AGREEMENT CAREFULLY BEFORE

SELECTING THE "ACCEPT" BUTTON AT THE BOTTOM OF THIS PAGE. BYSELECTING THE "ACCEPT" BUTTON YOU AGREE TO THE TERMS AND

CONDITIONS OF THE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY

ITS TERMS, SELECT THE "DO NOT ACCEPT" BUTTON AT THE BOTTOM OF THIS

PAGE AND THE INSTALLATION PROCESS WILL NOT CONTINUE.

1. License to Distribute. Customer is granted a royalty-free, non-transferable right to

reproduce and use the Software for the purpose of developing applications which run in

conjunction with the Software. Customer may not modify the Software (including any

APIs exposed by the Software) in any way.

2. Restrictions. Software is confidential copyrighted information of Lotus and title to allcopies is retained by Lotus and/or its licensors. Except to the extent enforcement of this

provision is prohibited by applicable law, if at all, Customer shall not decompile,

disassemble, decrypt, extract, or otherwise reverse engineer Software. Software is not

designed or intended for use in on-line control of aircraft, air traffic, aircraft navigation or

aircraft communications; or in the design, construction, operation or maintenance of any

nuclear facility. Customer warrants that it will not use or redistribute the Software for

such purposes.

3. Trademarks and Logos. This Agreement does not authorize Customer to use any Sun

or Lotus name, trademark or logo. Customer acknowledges that Sun owns the Java

trademark and all Java-related trademarks, logos and icons including the Coffee Cup

and Duke (``Java Marks'') and agrees to: (i) comply with the Java Trademark Guidelinesat http://java.sun.com/trademarks.html; (ii) not do anything harmful to or inconsistent

with Sun's rights in the Java Marks; and (iii) assist Sun in protecting those rights,

including assigning to Sun any rights acquired by Customer in any Java Mark.

4. Disclaimer of Warranty. Software is provided ``AS IS,'' without a warranty of any kind.

ALL EXPRESS OR IMPLIED REPRESENTATIONS AND WARRANTIES, INCLUDING

ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

PURPOSE OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED.

5.Limitation of Liability. IN NO EVENT WILL LOTUS, SUN OR ITS LICENSORS BE

LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL,INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES HOWEVER





CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY ARISING OUT OF

THE DOWNLOADING OF, USE OF, OR INABILITY TO USE, SOFTWARE, EVEN IF

SUN OR LOTUS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

6. Termination. Customer may terminate this Agreement at any time by destroying all

copies of Software. This Agreement will terminate immediately without notice from Sun

or Lotus if Customer fails to comply with any provision of this Agreement. Upon such

termination, Customer must destroy all copies of Software. Sections 4 and 5 above shall

survive termination of this Agreement.

7. Export Regulations. Software, including technical data, is subject to U.S. export

control laws, including the U.S. Export Administration Act and its associated regulations,

and may be subject to export or import regulations in other countries. Customer agrees

to comply strictly with all such regulations and acknowledges that it has the responsibility

to obtain licenses to export, re-export, or import Software. Software may not be

downloaded, or otherwise exported or re-exported (i) into, or to a national or resident of,Cuba, Iraq, Iran, North Korea, Libya, Sudan, Syria or any country to which the U.S. has

embargoed goods; or (ii) to anyone on the U.S. Treasury Department's list of Specially

Designated Nations or the U.S. Commerce Department's Table of Denial Orders.

8. Restricted Rights. Use, duplication or disclosure by the United States government is

subject to the restrictions as set forth in the Rights in Technical Data and Computer

Software Clauses in DFARS 252.227-7013(c) (1) (ii) and FAR 52.227-19(c) (2) as

applicable.

9. Governing Law. Any action related to this Agreement will be governed by California

law and controlling U.S. federal law. No choice of law rules of any jurisdiction will apply.

10. Severability. If any of the above provisions are held to be in violation of applicable

law, void, or unenforceable in any jurisdiction, then such provisions are herewith waived

or amended to the extent necessary for the Agreement to be otherwise enforceable in

such jurisdiction. However, if in Sun's or Lotus' opinion deletion or amendment of any

provisions of the Agreement by operation of this paragraph unreasonably compromises

the rights or increase the liabilities of Sun, Lotus or their licensors, Sun and Lotus

reserve the right to terminate the Agreement.

Commons-net 1.0.0 (commons-net-1.0.0.jar)

The Apache Software License, Version 1.1

Copyright (c) 2001 The Apache Software Foundation. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are

permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of

conditions and the following disclaimer.




A-8LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

2. Redistributions in binary form must reproduce the above copyright notice, this list

of conditions and the following disclaimer in the documentation and/or other

materials provided with the distribution.

3. The end-user documentation included with the redistribution, if any, must includethe following acknowledgment: "This product includes software developed by the

Apache Software Foundation (http://www.apache.org/). Alternately, this

acknowledgment may appear in the software itself, if and wherever such third-party

acknowledgments normally appear.

4. The names "Apache" and "Apache Software Foundation" and "Apache Commons"

must not be used to endorse or promote products derived from this software

without prior written permission. For written permission, please contact

[email protected].

5. Products derived from this software may not be called "Apache", nor may "Apache"

appear in their name, without prior written permission of the Apache Software

Foundation.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES

OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE

DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR

ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT

LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF

USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED

AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE

POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on behalf of

the Apache Software Foundation. For more information on the Apache Software

Foundation, please see <http://www.apache.org/>.

CUP Parser Generator 10J (java_cup.jar)

CUP Parser Generator Copyright Notice, License, and Disclaimer Copyright 1996-1999

by Scott Hudson, Frank Flannery, C. Scott Ananian

Permission to use, copy, modify, and distribute this software and its documentation for

any purpose and without fee is hereby granted, provided that the above copyright notice

appear in all copies and that both the copyright notice and this permission notice and

warranty disclaimer appear in supporting documentation, and that the names of the

authors or their employers not be used in advertising or publicity pertaining to

distribution of the software without specific, written prior permission.

The authors and their employers disclaim all warranties with regard to this software,

including all implied warranties of merchantability and fitness. In no event shall the

authors or their employers be liable for any special, indirect or consequential damagesor any damages whatsoever resulting from loss of use, data or profits, whether in an





action of contract, negligence or other tortious action, arising out of or in connection with

the use or performance of this software.

This is an open source license. It is also GPL-Compatible (see entry for "Standard ML

of New Jersey"). The portions of CUP output which are hard-coded into the CUP source

code are (naturally) covered by this same license, as is the CUP runtime code linked

with the generated parser.

Java is a trademark of Sun Microsystems, Inc. References to the Java programming

language in relation to JLex are not meant to imply that Sun endorses this product.

FoxTrot 3.0.beta.1 (foxtrot.jar)

Copyright (c) 2002, Simone Bordet & Marco Cravero

All rights reserved.



– Redistributions of source code must retain the above copyright notice, this list

of conditions and the following disclaimer.

– Redistributions in binary form must reproduce the above copyright notice, this

list of conditions and the following disclaimer in the documentation and/or

other materials provided with the distribution.

– Neither the name of Foxtrot nor the names of the contributors may be used to

endorse or promote products derived from this software without specific prior

written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND

CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE

DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE

LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR

CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY

THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE

USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH

DAMAGE.




A-10LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

JAVA ADVANCED IMAGING API, VERSION 1.1.2 (jai_core.jar, jai_codec.jar)

-Sun Microsystems, Inc.

Binary Code License Agreement

JAVA ADVANCED IMAGING API, VERSION 1.1.2

READ THE TERMS OF THIS AGREEMENT AND ANY PROVIDED SUPPLEMENTAL

LICENSE TERMS (COLLECTIVELY "AGREEMENT") CAREFULLY BEFORE

OPENING THE SOFTWARE MEDIA PACKAGE. BY OPENING THE SOFTWARE

MEDIA PACKAGE, YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU

ARE ACCESSING THE SOFTWARE ELECTRONICALLY, INDICATE YOUR

ACCEPTANCE OF THESE TERMS BY SELECTING THE "ACCEPT" BUTTON AT

THE END OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL THESE TERMS,

PROMPTLY RETURN THE UNUSED SOFTWARE TO YOUR PLACE OF PURCHASE

FOR A REFUND OR, IF THE SOFTWARE IS ACCESSED ELECTRONICALLY,SELECT THE "DECLINE" BUTTON AT THE END OF THIS AGREEMENT.

1. LICENSE TO USE. Sun grants you a non-exclusive andnon-transferable license for

the internal use only of the accompanying software and documentation and any error

corrections provided by Sun (collectively "Software"), by the number of users and the

class of computer hardware for which the corresponding fee has been paid.

2. RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all

associated intellectual property rights is retained by Sun and/or its licensors. Except as

specifically authorized in any Supplemental License Terms, you may not make copies of

Software, other than a single copy of Software for archival purposes. Unlessenforcement is prohibited by applicable law, you may not modify , decompile, or reverse

engineer Software. Licensee acknowledges that Software is not designed or intended

for use in the design, construction, operation or maintenance of any nuclear facility. Sun

Microsystems, Inc. disclaims any express or implied warranty of fitness for such uses.

No right, title or interest in or to any trademark, service mark, logo or trade name of Sun

or its licensors is granted under this Agreement.

3. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from

the date of purchase, as evidenced by a copy of the receipt, the media on which

Software is furnished (if any) will be free of defects in materials and workmanship under

normal use. Except for the foregoing, Software is provided "AS IS". Your exclusive

remedy and Sun's entire liability under this limited warranty will be at Sun's option toreplace Software media or refund the fee paid for Software.

4. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS AGREEMENT, ALL

EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,

INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A

PARTICULAR PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO

THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

5. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW , IN NO

EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE,

PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTALOR PUNITIVE DAMAGES, HOWEVER CAUSED REGARDLESS OF THE THEORY





OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO

USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF

SUCH DAMAGES. In no event will Sun's liability to you, whether in contract, tort

(including negligence), or otherwise, exceed the amount paid by you for Software under

this Agreement. The foregoing limitations will apply even if the above stated warranty

fails of its essential purpose.

6. Termination. This Agreement is effective until terminated. You may terminate this

Agreement at any time by destroying all copies of Software. This Agreement will

terminate immediately without notice from Sun if you fail to comply with any provision of

this Agreement. Upon Termination, you must destroy all copies of Software.

7. Export Regulations. All Software and technical data delivered under this Agreement

are subject to US export control laws and may be subject to export or import regulations

in other countries. You agree to comply strictly with all such laws and regulations and

acknowledge that you have the responsibility to obtain such licenses to export,re-export, or import as may be required after delivery to you.

8. U.S. Government Restricted Rights. If Software is being acquired by or on behalf of

the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any

tier), then the Government's rights in Software and accompanying documentation will be

only as set forth in this Agreement; this is in accordance with 48 CFR 227.7201 through

227.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2.101 and

12.212 (for non-DOD acquisitions).

9. Governing Law. Any action related to this Agreement will be governed by California

law and controlling U.S. federal law. No choice of law rules of any jurisdiction will apply.

10. Severability. If any provision of this Agreement is held to be unenforceable, this

Agreement will remain in effect with the provision omitted, unless omission would

frustrate the intent of the parties, in which case this Agreement will immediately

terminate.

11. Integration. This Agreement is the entire agreement between you and Sun relating

to its subject matter. It supersedes all prior or contemporaneous oral or written

communications, proposals, representations and warranties and prevails over any

conflicting or addition al terms of any quote, order, acknowledgment, or other

communication between the parties relating to its subject matter during the term of this

Agreement. No modification of this Agreement will be binding, unless in writing andsigned by an authorized representative of each party.




A-12LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

JAVA ADVANCED IMAGING, VERSION 1.1.2

SUPPLEMENTAL LICENSE TERMS

These supplemental license terms ("Supplemental Terms") add to or modify the terms

of the Binary Code License Agreement (collectively, the "Agreement"). Capitalized

terms not defined in these Supplemental Terms shall have the same meanings ascribed

to them in the Agreement. These Supplemental Terms shall supersede any inconsistent

or conflicting terms in the Agreement, or in any license contained within the Software.

1. Software Internal Use and Development License Grant. Subject to the terms and

conditions of this Agreement, including, but not limited to Section 3 (Java Technology

Restrictions) of these Supplemental Terms, Sun grants you a non-exclusive,

non-transferable, limited license to reproduce internally and use internally the binary

form of the Software, complete and unmodified, for the sole purpose of designing,

developing and testing your Java applets and applications ("Programs").

2. License to Distribute Software. In addition to the license granted in Section 1

(Software Internal Use and Development License Grant ) of these Supplemental Terms,

subject to the terms and conditions of this Agreement, including but not limited to,

Section 3 (Java Technology Restrictions) of these Supplemental Terms, Sun grants you

a non-exclusive, non-transferable, limited license to reproduce and distribute the

Software in binary code form only, provided that you (i) distribute the Software complete

and unmodified and only bundled as part of your Programs, (ii) do not distribute

additional software intended to replace any component(s) of the Software, (iii) do not

remove or alter any proprietary legends or notices contained in the Software, ( iv) only

distribute the Software subject to a license agreement that protects Sun's interestsconsistent with the terms contained in this Agreement, and (v) agree to defend and

indemnify Sun and its licensors from and against any damages, costs, liabilities,

settlement amounts and/or expenses (including attorneys' fees) incurred in connection

with any claim, lawsuit or action by any third party that arises or results from the use or

distribution of any and all Programs and/or So ftware.

3. Java Technology Restrictions. You may not modify the Java Platform Interface ("JPI",

identified as classes contained within the "java" package or any subpackages of the

"java" package), by creating additional classes within the JPI or otherwise causing the

addition to or modification of the classes in the JPI. In the event that you create an

additional class and associated API(s) which (i) extends the functionality of the Java

platform, and (ii) is exposed to third party software developers for the purpose ofdeveloping additional software which invokes such additional API, you must promptly

publish broadly an accurate specification for such API for free use by all developers.

You may not create, or authorize your licensees to create additional classes, interfaces,

or subpackages that are in any way identified as "java", "javax", "sun" or similar

convention as specified by Sun in any naming convention designation.

4. Java Runtime Availability. Refer to the appropriate version of the Java Runtime

Environment binary code license (currently located at

http://www.java.sun.com/jdk/index.html) for the availability of runtime code which may

be distributed with Java applets and applications.

5. Trademarks and Logos. You acknowledge and agree as between you and Sun that





Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all

SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks,

logos and other brand designations ("Sun Marks"), and you agree to comply with the

Sun Trademark and Logo Usage Requirements currently located at

http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to

Sun's benefit.

6. Source Code. Software may contain source code that is provided solely for reference

purposes pursuant to the terms of this Agreement. Source code may not be

redistributed unless expressly provided for in this Agreement.

7. Termination for Infringement. Either party may terminate this Agreement immediately

should any Software become, or in either party's opinion be likely to become, the subject

of a claim of infringement of any intellectual property right.

For inquiries please contact: Sun Microsystems, Inc., 4150

Network Circle, Santa Clara, California 95054, U.S.A

(LFI#143342/Form ID#011801)

JFreeChart 1.0.0 (jfreechart-1.0.0.jar)

GNU LESSER GENERAL PUBLIC LICENSE

Version 2.1, February 1999

Copyright (C) 1991, 1999 Free Software Foundation, Inc.

59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Everyone is permitted to copy and distribute verbatim copies

of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL. It also counts as the successor of

the GNU Library Public License, version 2, hence the version number 2.1.]

Preamble

The licenses for most software are designed to take away your freedom to share and

change it. By contrast, the GNU General Public Licenses are intended to guaranteeyour freedom to share and change free software--to make sure the software is free for

all its users.

This license, the Lesser General Public License, applies to some specially

designated software packages--typically libraries--of the Free Software Foundation and

other authors who decide to use it. You can use it too, but we suggest you first think

carefully about whether this license or the ordinary General Public License is the better

strategy to use in any particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use, not price. Our

General Public Licenses are designed to make sure that you have the freedom todistribute copies of free software (and charge for this service if you wish); that you




A-14LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

receive source code or can get it if you want it; that you can change the software and

use pieces of it in new free programs; and that you are informed that you can do these

things.

To protect your rights, we need to make restrictions that forbid distributors to deny

you these rights or to ask you to surrender these rights. These restrictions translate to

certain responsibilities for you if you distribute copies of the library or if you modify it.

For example, if you distribute copies of the library, whether gratis or for a fee, you

must give the recipients all the rights that we gave you. You must make sure that they,

too, receive or can get the source code. If you link other code with the library, you must

provide complete object files to the recipients, so that they can relink them with the

library after making changes to the library and recompiling it. And you must show them

these terms so they know their rights.

We protect your rights with a two-step method: (1) we copyright the library, and (2)we offer you this license, which gives you legal permission to copy, distribute and/or

modify the library.

To protect each distributor, we want to make it very clear that there is no warranty for

the free library. Also, if the library is modified by someone else and passed on, the

recipients should know that what they have is not the original version, so that the original

author's reputation will not be affected by problems that might be introduced by others.

Finally, software patents pose a constant threat to the existence of any free program.

We wish to make sure that a company cannot effectively restrict the users of a free

program by obtaining a restrictive license from a patent holder. Therefore, we insist thatany patent license obtained for a version of the library must be consistent with the full

freedom of use specified in this license.

Most GNU software, including some libraries, is covered by the ordinary GNU

General Public License. This license, the GNU Lesser General Public License, applies

to certain designated libraries, and is quite different from the ordinary General Public

License. We use this license for certain libraries in order to permit linking those libraries

into non-free programs.

When a program is linked with a library, whether statically or using a shared library,

the combination of the two is legally speaking a combined work, a derivative of the

original library. The ordinary General Public License therefore permits such linking onlyif the entire combination fits its criteria of freedom. The Lesser General Public License

permits more lax criteria for linking other code with the library.

We call this license the "Lesser" General Public License because it does Less to

protect the user's freedom than the ordinary General Public License. It also provides

other free software developers Less of an advantage over competing non-free

programs. These disadvantages are the reason we use the ordinary General Public

License for many libraries. However, the Lesser license provides advantages in certain

special circumstances.

For example, on rare occasions, there may be a special need to encourage thewidest possible use of a certain library, so that it becomes a de-facto standard. To





achieve this, non-free programs must be allowed to use the library. A more frequent

case is that a free library does the same job as widely used non-free libraries. In this

case, there is little to gain by limiting the free library to free software only, so we use the

Lesser General Public License.

In other cases, permission to use a particular library in non-free programs enables a

greater number of people to use a large body of free software. For example, permission

to use the GNU C Library in non-free programs enables many more people to use the

whole GNU operating system, as well as its variant, the GNU/Linux operating system.

Although the Lesser General Public License is Less protective of the users' freedom,

it does ensure that the user of a program that is linked with the Library has the freedom

and the wherewithal to run that program using a modified version of the Library.

The precise terms and conditions for copying, distribution and modification follow.

Pay close attention to the difference between a work based on the library and a "workthat uses the library". The former contains code derived from the library, whereas the

latter must be combined with the library in order to run.


TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License Agreement applies to any software library or other program which

contains a notice placed by the copyright holder or other authorized party saying it may

be distributed under the terms of this Lesser General Public License (also called "this

License"). Each licensee is addressed as "you".

A "library" means a collection of software functions and/or data prepared so as to be

conveniently linked with application programs (which use some of those functions and

data) to form executables.

The "Library", below, refers to any such software library or work which has been

distributed under these terms. A "work based on the Library" means either the Library

or any derivative work under copyright law: that is to say, a work containing the Library

or a portion of it, either verbatim or with modifications and/or translated straightforwardly

into another language. (Hereinafter, translation is included without limitation in the term

"modification".)

"Source code" for a work means the preferred form of the work for makingmodifications to it. For a library, complete source code means all the source code for all

modules it contains, plus any associated interface definition files, plus the scripts used

to control compilation and installation of the library.

Activities other than copying, distribution and modification are not covered by this

License; they are outside its scope. The act of running a program using the Library is

not restricted, and output from such a program is covered only if its contents constitute

a work based on the Library (independent of the use of the Library in a tool for writing

it). Whether that is true depends on what the Library does and what the program that

uses the Library does.

1. You may copy and distribute verbatim copies of the Library's complete source




A-16LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

code as you receive it, in any medium, provided that you conspicuously and

appropriately publish on each copy an appropriate copyright notice and disclaimer of

warranty; keep intact all the notices that refer to this License and to the absence of any

warranty; and distribute a copy of this License along with the Library.

You may charge a fee for the physical act of transferring a copy, and you may at your

option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Library or any portion of it, thus forming

a work based on the Library, and copy and distribute such modifications or work under

the terms of Section 1 above, provided that you also meet all of these conditions:

a) The modified work must itself be a software library.

b) You must cause the files modified to carry prominent notices stating that you

changed the files and the date of any change.

c) You must cause the whole of the work to be licensed at no charge to all third

parties under the terms of this License.

d) If a facility in the modified Library refers to a function or a table of data to be

supplied by an application program that uses the facility, other than as an

argument passed when the facility is invoked, then you must make a good

faith effort to ensure that, in the event an application does not supply suchfunction or table, the facility still operates, and performs whatever part of its

purpose remains meaningful.

(For example, a function in a library to compute square roots has a purpose

that is entirely well-defined independent of the application. Therefore,

Subsection 2d requires that any application-supplied function or table used by

this function must be optional: if the application does not supply it, the square

root function must still compute square roots.)

These requirements apply to the modified work as a whole. If identifiable sections of

that work are not derived from the Library, and can be reasonably considered

independent and separate works in themselves, then this License, and its terms, do not

apply to those sections when you distribute them as separate works. But when you

distribute the same sections as part of a whole which is a work based on the Library, the

distribution of the whole must be on the terms of this License, whose permissions for

other licensees extend to the entire whole, and thus to each and every part regardless

of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written

entirely by you; rather, the intent is to exercise the right to control the distribution of

derivative or collective works based on the Library.

In addition, mere aggregation of another work not based on the Library with the Library(or with a work based on the Library) on a volume of a storage or distribution medium





does not bring the other work under the scope of this License.

3. You may opt to apply the terms of the ordinary GNU General Public License

instead of this License to a given copy of the Library. To do this, you must alter all the

notices that refer to this License, so that they refer to the ordinary GNU General Public

License, version 2, instead of to this License. (If a newer version than version 2 of the

ordinary GNU General Public License has appeared, then you can specify that version

instead if you wish.) Do not make any other change in these notices.

Once this change is made in a given copy, it is irreversible for that copy, so the

ordinary GNU General Public License applies to all subsequent copies and derivative

works made from that copy.

This option is useful when you wish to copy part of the code of the Library into a

program that is not a library.

4. You may copy and distribute the Library (or a portion or derivative of it, under

Section 2) in object code or executable form under the terms of Sections 1 and 2 above

provided that you accompany it with the complete corresponding machine-readable

source code, which must be distributed under the terms of Sections 1 and 2 above on a

medium customarily used for software interchange.

If distribution of object code is made by offering access to copy from a designated

place, then offering equivalent access to copy the source code from the same place

satisfies the requirement to distribute the source code, even though third parties are not

compelled to copy the source along with the object code.

5. A program that contains no derivative of any portion of the Library, but is designed

to work with the Library by being compiled or linked with it, is called a "work that uses

the Library". Such a work, in isolation, is not a derivative work of the Library, and

therefore falls outside the scope of this License.

However, linking a "work that uses the Library" with the Library creates an executable

that is a derivative of the Library (because it contains portions of the Library), rather than

a "work that uses the library". The executable is therefore covered by this License.

Section 6 states terms for distribution of such executables.

When a "work that uses the Library" uses material from a header file that is part of

the Library, the object code for the work may be a derivative work of the Library eventhough the source code is not. Whether this is true is especially significant if the work

can be linked without the Library, or if the work is itself a library. The threshold for this

to be true is not precisely defined by law.

If such an object file uses only numerical parameters, data structure layouts and

accessors, and small macros and small inline functions (ten lines or less in length), then

the use of the object file is unrestricted, regardless of whether it is legally a derivative

work. (Executables containing this object code plus portions of the Library will still fall

under Section 6.)

Otherwise, if the work is a derivative of the Library, you may distribute the object codefor the work under the terms of Section 6. Any executables containing that work also fall




A-18LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

under Section 6, whether or not they are linked directly with the Library itself.

6. As an exception to the Sections above, you may also combine or link a "work that

uses the Library" with the Library to produce a work containing portions of the Library,

and distribute that work under terms of your choice, provided that the terms permit

modification of the work for the customer's own use and reverse engineering for

debugging such modifications.

You must give prominent notice with each copy of the work that the Library is used

in it and that the Library and its use are covered by this License. You must supply a copy

of this License. If the work during execution displays copyright notices, you must include

the copyright notice for the Library among them, as well as a reference directing the user

to the copy of this License. Also, you must do one of these things:

a) Accompany the work with the complete corresponding machine-readable

source code for the Library including whatever changes were used in the work(which must be distributed under Sections 1 and 2 above); and, if the work is

an executable linked with the Library, with the complete machine-readable

"work that uses the Library", as object code and/or source code, so that the

user can modify the Library and then relink to produce a modified executable

containing the modified Library. (It is understood that the user who changes

the contents of definitions files in the Library will not necessarily be able to

recompile the application to use the modified definitions.)

b) Use a suitable shared library mechanism for linking with the Library. A

suitable mechanism is one that (1) uses at run time a copy of the library

already present on the user's computer system, rather than copying library

functions into the executable, and (2) will operate properly with a modifiedversion of the library, if the user installs one, as long as the modified version is

interface-compatible with the version that the work was made with.

c) Accompany the work with a written offer, valid for at least three years, to give

the same user the materials specified in Subsection 6a, above, for a charge

no more than the cost of performing this distribution.

d) If distribution of the work is made by offering access to copy from a

designated place, offer equivalent access to copy the above specified

materials from the same place.

e) Verify that the user has already received a copy of these materials or that youhave already sent this user a copy.

For an executable, the required form of the "work that uses the Library" must include

any data and utility programs needed for reproducing the executable from it. However,

as a special exception, the materials to be distributed need not include anything that is

normally distributed (in either source or binary form) with the major components

(compiler, kernel, and so on) of the operating system on which the executable runs,

unless that component itself accompanies the executable.

It may happen that this requirement contradicts the license restrictions of other

proprietary libraries that do not normally accompany the operating system. Such acontradiction means you cannot use both them and the Library together in an executable





that you distribute.

7. You may place library facilities that are a work based on the Library side-by-side

in a single library together with other library facilities not covered by this License, and

distribute such a combined library, provided that the separate distribution of the work

based on the Library and of the other library facilities is otherwise permitted, and

provided that you do these two things:

a) Accompany the combined library with a copy of the same work based on the

Library, uncombined with any other library facilities. This must be distributed

under the terms of the Sections above.

b) Give prominent notice with the combined library of the fact that part of it is a

work based on the Library, and explaining where to find the accompanying

uncombined form of the same work.

8. You may not copy, modify, sublicense, link with, or distribute the Library except as

expressly provided under this License. Any attempt otherwise to copy, modify,

sublicense, link with, or distribute the Library is void, and will automatically terminate

your rights under this License. However, parties who have received copies, or rights,

from you under this License will not have their licenses terminated so long as such

parties remain in full compliance.

9. You are not required to accept this License, since you have not signed it.

However, nothing else grants you permission to modify or distribute the Library or its

derivative works. These actions are prohibited by law if you do not accept this License.

Therefore, by modifying or distributing the Library (or any work based on the Library),

you indicate your acceptance of this License to do so, and all its terms and conditionsfor copying, distributing or modifying the Library or works based on it.

10. Each time you redistribute the Library (or any work based on the Library), the

recipient automatically receives a license from the original licensor to copy, distribute,

link with or modify the Library subject to these terms and conditions. You may not

impose any further restrictions on the recipients' exercise of the rights granted herein.

You are not responsible for enforcing compliance by third parties with this License.

11. If, as a consequence of a court judgment or allegation of patent infringement or

for any other reason (not limited to patent issues), conditions are imposed on you

(whether by court order, agreement or otherwise) that contradict the conditions of thisLicense, they do not excuse you from the conditions of this License. If you cannot

distribute so as to satisfy simultaneously your obligations under this License and any

other pertinent obligations, then as a consequence you may not distribute the Library at

all. For example, if a patent license would not permit royalty-free redistribution of the

Library by all those who receive copies directly or indirectly through you, then the only

way you could satisfy both it and this License would be to refrain entirely from

distribution of the Library.

If any portion of this section is held invalid or unenforceable under any particular

circumstance, the balance of the section is intended to apply, and the section as a whole

is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property




A-20LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

right claims or to contest validity of any such claims; this section has the sole purpose

of protecting the integrity of the free software distribution system which is implemented

by public license practices. Many people have made generous contributions to the wide

range of software distributed through that system in reliance on consistent application

of that system; it is up to the author/donor to decide if he or she is willing to distribute

software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence

of the rest of this License.

12. If the distribution and/or use of the Library is restricted in certain countries either

by patents or by copyrighted interfaces, the original copyright holder who places the

Library under this License may add an explicit geographical distribution limitation

excluding those countries, so that distribution is permitted only in or among countries not

thus excluded. In such case, this License incorporates the limitation as if written in the

body of this License.

13. The Free Software Foundation may publish revised and/or new versions of the

Lesser General Public License from time to time. Such new versions will be similar in

spirit to the present version, but may differ in detail to address new problems or

concerns.

Each version is given a distinguishing version number. If the Library specifies a version

number of this License which applies to it and any later version, you have the option of

following the terms and conditions either of that version or of any later version published

by the Free Software Foundation. If the Library does not specify a license version

number, you may choose any version ever published by the Free Software Foundation.

14. If you wish to incorporate parts of the Library into other free programs whose

distribution conditions are incompatible with these, write to the author to ask for

permission. For software which is copyrighted by the Free Software Foundation, write

to the Free Software Foundation; we sometimes make exceptions for this. Our decision

will be guided by the two goals of preserving the free status of all derivatives of our free

software and of promoting the sharing and reuse of software generally.

NO WARRANTY

15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO

WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLELAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT

HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT

WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT

NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND

FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY

AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY

PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,

REPAIR OR CORRECTION.

16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO

IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAYMODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE





LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,

INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR

INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF

DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY

YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH

ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN

ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Libraries

If you develop a new library, and you want it to be of the greatest possible use to the

public, we recommend making it free software that everyone can redistribute and

change. You can do so by permitting redistribution under these terms (or, alternatively,

under the terms of the ordinary General Public License).

To apply these terms, attach the following notices to the library. It is safest to attach

them to the start of each source file to most effectively convey the exclusion of warranty;

and each file should have at least the copyright line and a pointer to where the full notice

is found.

<one line to give the library's name and a brief idea of what it does.>

Copyright (C) <year> <name of author>

This library is free software; you can redistribute it and/or modify it under the terms

of the GNU Lesser General Public License as published by the Free SoftwareFoundation; either version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY

WARRANTY; without even the implied warranty of MERCHANTABILITY or

FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public

License for more details.

You should have received a copy of the GNU Lesser General Public License along

with this library; if not, write to the Free Software Foundation, Inc., 59 Temple

Place, Suite 330, Boston, MA 02111-1307 USA

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your school, if any,

to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the

names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the library ̀ Frob' (a library

for tweaking knobs) written by James Random Hacker.

<signature of Ty Coon>, 1 April 1990

Ty Coon, President of Vice

That's all there is to it!




A-22LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

JCommon 1.0.0 (jcommon-1.0.0.jar)


Version 2.1, February 1999

Copyright (C) 1991, 1999 Free Software Foundation, Inc.

59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Everyone is permitted to copy and distribute verbatim copies

of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL. It also counts as the successor of

the GNU Library Public License, version 2, hence the version number 2.1.]

Preamble

The licenses for most software are designed to take away your freedom to share andchange it. By contrast, the GNU General Public Licenses are intended to guarantee

your freedom to share and change free software--to make sure the software is free for

all its users.

This license, the Lesser General Public License, applies to some specially

designated software packages--typically libraries--of the Free Software Foundation and

other authors who decide to use it. You can use it too, but we suggest you first think

carefully about whether this license or the ordinary General Public License is the better

strategy to use in any particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use, not price. OurGeneral Public Licenses are designed to make sure that you have the freedom to

distribute copies of free software (and charge for this service if you wish); that you

receive source code or can get it if you want it; that you can change the software and

use pieces of it in new free programs; and that you are informed that you can do these

things.

To protect your rights, we need to make restrictions that forbid distributors to deny

you these rights or to ask you to surrender these rights. These restrictions translate to

certain responsibilities for you if you distribute copies of the library or if you modify it.

For example, if you distribute copies of the library, whether gratis or for a fee, you

must give the recipients all the rights that we gave you. You must make sure that they,too, receive or can get the source code. If you link other code with the library, you must

provide complete object files to the recipients, so that they can relink them with the

library after making changes to the library and recompiling it. And you must show them

these terms so they know their rights.

We protect your rights with a two-step method: (1) we copyright the library, and (2)

we offer you this license, which gives you legal permission to copy, distribute and/or

modify the library.

To protect each distributor, we want to make it very clear that there is no warranty for

the free library. Also, if the library is modified by someone else and passed on, therecipients should know that what they have is not the original version, so that the original





author's reputation will not be affected by problems that might be introduced by others.

Finally, software patents pose a constant threat to the existence of any free program.

We wish to make sure that a company cannot effectively restrict the users of a free

program by obtaining a restrictive license from a patent holder. Therefore, we insist that

any patent license obtained for a version of the library must be consistent with the full

freedom of use specified in this license.

Most GNU software, including some libraries, is covered by the ordinary GNU

General Public License. This license, the GNU Lesser General Public License, applies

to certain designated libraries, and is quite different from the ordinary General Public

License. We use this license for certain libraries in order to permit linking those libraries

into non-free programs.

When a program is linked with a library, whether statically or using a shared library,

the combination of the two is legally speaking a combined work, a derivative of theoriginal library. The ordinary General Public License therefore permits such linking only

if the entire combination fits its criteria of freedom. The Lesser General Public License

permits more lax criteria for linking other code with the library.

We call this license the "Lesser" General Public License because it does Less to

protect the user's freedom than the ordinary General Public License. It also provides

other free software developers Less of an advantage over competing non-free

programs. These disadvantages are the reason we use the ordinary General Public

License for many libraries. However, the Lesser license provides advantages in certain

special circumstances.

For example, on rare occasions, there may be a special need to encourage the

widest possible use of a certain library, so that it becomes a de-facto standard. To

achieve this, non-free programs must be allowed to use the library. A more frequent

case is that a free library does the same job as widely used non-free libraries. In this

case, there is little to gain by limiting the free library to free software only, so we use the

Lesser General Public License.

In other cases, permission to use a particular library in non-free programs enables a

greater number of people to use a large body of free software. For example, permission

to use the GNU C Library in non-free programs enables many more people to use the

whole GNU operating system, as well as its variant, the GNU/Linux operating system.

Although the Lesser General Public License is Less protective of the users' freedom,

it does ensure that the user of a program that is linked with the Library has the freedom

and the wherewithal to run that program using a modified version of the Library.

The precise terms and conditions for copying, distribution and modification follow.

Pay close attention to the difference between a work based on the library and a "work

that uses the library". The former contains code derived from the library, whereas the

latter must be combined with the library in order to run.

GNU LESSER GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR

COPYING, DISTRIBUTION AND MODIFICATION




A-24LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

0. This License Agreement applies to any software library or other program which

contains a notice placed by the copyright holder or other authorized party saying it may

be distributed under the terms of this Lesser General Public License (also called "this

License"). Each licensee is addressed as "you".

A "library" means a collection of software functions and/or data prepared so as to be

conveniently linked with application programs (which use some of those functions and

data) to form executables.

The "Library", below, refers to any such software library or work which has been

distributed under these terms. A "work based on the Library" means either the Library

or any derivative work under copyright law: that is to say, a work containing the Library

or a portion of it, either verbatim or with modifications and/or translated straightforwardly

into another language. (Hereinafter, translation is included without limitation in the term

"modification".)

"Source code" for a work means the preferred form of the work for making

modifications to it. For a library, complete source code means all the source code for all

modules it contains, plus any associated interface definition files, plus the scripts used

to control compilation and installation of the library.

Activities other than copying, distribution and modification are not covered by this

License; they are outside its scope. The act of running a program using the Library is

not restricted, and output from such a program is covered only if its contents constitute

a work based on the Library (independent of the use of the Library in a tool for writing

it). Whether that is true depends on what the Library does and what the program that

uses the Library does.

1. You may copy and distribute verbatim copies of the Library's complete source

code as you receive it, in any medium, provided that you conspicuously and

appropriately publish on each copy an appropriate copyright notice and disclaimer of

warranty; keep intact all the notices that refer to this License and to the absence of any

warranty; and distribute a copy of this License along with the Library.

You may charge a fee for the physical act of transferring a copy, and you may at your

option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Library or any portion of it, thus forming

a work based on the Library, and copy and distribute such modifications or work underthe terms of Section 1 above, provided that you also meet all of these conditions:

a) The modified work must itself be a software library.

b) You must cause the files modified to carry prominent notices stating that you

changed the files and the date of any change.

c) You must cause the whole of the work to be licensed at no charge to all third

parties under the terms of this License.

d) If a facility in the modified Library refers to a function or a table of data to be

supplied by an application program that uses the facility, other than as anargument passed when the facility is invoked, then you must make a good





faith effort to ensure that, in the event an application does not supply such

function or table, the facility still operates, and performs whatever part of its

purpose remains meaningful.

(For example, a function in a library to compute square roots has a purpose that is

entirely well-defined independent of the application. Therefore, Subsection 2d

requires that any application-supplied function or table used by this function must

be optional: if the application does not supply it, the square root function must still

compute square roots.)

These requirements apply to the modified work as a whole. If identifiable sections of

that work are not derived from the Library, and can be reasonably considered

independent and separate works in themselves, then this License, and its terms, do not

apply to those sections when you distribute them as separate works. But when you

distribute the same sections as part of a whole which is a work based on the Library, the

distribution of the whole must be on the terms of this License, whose permissions forother licensees extend to the entire whole, and thus to each and every part regardless

of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written

entirely by you; rather, the intent is to exercise the right to control the distribution of

derivative or collective works based on the Library.

In addition, mere aggregation of another work not based on the Library with the Library

(or with a work based on the Library) on a volume of a storage or distribution medium

does not bring the other work under the scope of this License.

3. You may opt to apply the terms of the ordinary GNU General Public License

instead of this License to a given copy of the Library. To do this, you must alter all the

notices that refer to this License, so that they refer to the ordinary GNU General Public

License, version 2, instead of to this License. (If a newer version than version 2 of the

ordinary GNU General Public License has appeared, then you can specify that version

instead if you wish.) Do not make any other change in these notices.

Once this change is made in a given copy, it is irreversible for that copy, so the

ordinary GNU General Public License applies to all subsequent copies and derivative

works made from that copy.

This option is useful when you wish to copy part of the code of the Library into aprogram that is not a library.

4. You may copy and distribute the Library (or a portion or derivative of it, under

Section 2) in object code or executable form under the terms of Sections 1 and 2 above

provided that you accompany it with the complete corresponding machine-readable

source code, which must be distributed under the terms of Sections 1 and 2 above on a

medium customarily used for software interchange.

If distribution of object code is made by offering access to copy from a designated

place, then offering equivalent access to copy the source code from the same place

satisfies the requirement to distribute the source code, even though third parties are notcompelled to copy the source along with the object code.




A-26LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

5. A program that contains no derivative of any portion of the Library, but is designed

to work with the Library by being compiled or linked with it, is called a "work that uses

the Library". Such a work, in isolation, is not a derivative work of the Library, and

therefore falls outside the scope of this License.

However, linking a "work that uses the Library" with the Library creates an executable

that is a derivative of the Library (because it contains portions of the Library), rather than

a "work that uses the library". The executable is therefore covered by this License.

Section 6 states terms for distribution of such executables.

When a "work that uses the Library" uses material from a header file that is part of

the Library, the object code for the work may be a derivative work of the Library even

though the source code is not. Whether this is true is especially significant if the work

can be linked without the Library, or if the work is itself a library. The threshold for this

to be true is not precisely defined by law.

If such an object file uses only numerical parameters, data structure layouts and

accessors, and small macros and small inline functions (ten lines or less in length), then

the use of the object file is unrestricted, regardless of whether it is legally a derivative

work. (Executables containing this object code plus portions of the Library will still fall

under Section 6.)

Otherwise, if the work is a derivative of the Library, you may distribute the object code

for the work under the terms of Section 6. Any executables containing that work also fall

under Section 6, whether or not they are linked directly with the Library itself.

6. As an exception to the Sections above, you may also combine or link a "work that

uses the Library" with the Library to produce a work containing portions of the Library,

and distribute that work under terms of your choice, provided that the terms permit

modification of the work for the customer's own use and reverse engineering for

debugging such modifications.

You must give prominent notice with each copy of the work that the Library is used

in it and that the Library and its use are covered by this License. You must supply a copy

of this License. If the work during execution displays copyright notices, you must include

the copyright notice for the Library among them, as well as a reference directing the user

to the copy of this License. Also, you must do one of these things:

a) Accompany the work with the complete corresponding machine-readable

source code for the Library including whatever changes were used in the work

(which must be distributed under Sections 1 and 2 above); and, if the work is

an executable linked with the Library, with the complete machine-readable

"work that uses the Library", as object code and/or source code, so that the

user can modify the Library and then relink to produce a modified executable

containing the modified Library. (It is understood that the user who changes

the contents of definitions files in the Library will not necessarily be able to

recompile the application to use the modified definitions.)

b) Use a suitable shared library mechanism for linking with the Library. A

suitable mechanism is one that (1) uses at run time a copy of the library





already present on the user's computer system, rather than copying library

functions into the executable, and (2) will operate properly with a modified

version of the library, if the user installs one, as long as the modified version

is interface-compatible with the version that the work was made with.

c) Accompany the work with a written offer, valid for at least three years, to give

the same user the materials specified in Subsection 6a, above, for a charge

no more than the cost of performing this distribution.

d) If distribution of the work is made by offering access to copy from a

designated place, offer equivalent access to copy the above specified

materials from the same place.

e) Verify that the user has already received a copy of these materials or that you

have already sent this user a copy.

For an executable, the required form of the "work that uses the Library" must include

any data and utility programs needed for reproducing the executable from it. However,

as a special exception, the materials to be distributed need not include anything that is

normally distributed (in either source or binary form) with the major components

(compiler, kernel, and so on) of the operating system on which the executable runs,

unless that component itself accompanies the executable.

It may happen that this requirement contradicts the license restrictions of other

proprietary libraries that do not normally accompany the operating system. Such a

contradiction means you cannot use both them and the Library together in an executable

that you distribute.

7. You may place library facilities that are a work based on the Library side-by-side

in a single library together with other library facilities not covered by this License, and

distribute such a combined library, provided that the separate distribution of the work

based on the Library and of the other library facilities is otherwise permitted, and

provided that you do these two things:

a) Accompany the combined library with a copy of the same work based on the

Library, uncombined with any other library facilities. This must be distributed

under the terms of the Sections above.

b) Give prominent notice with the combined library of the fact that part of it is a

work based on the Library, and explaining where to find the accompanyinguncombined form of the same work.

8. You may not copy, modify, sublicense, link with, or distribute the Library except as

expressly provided under this License. Any attempt otherwise to copy, modify,

sublicense, link with, or distribute the Library is void, and will automatically terminate

your rights under this License. However, parties who have received copies, or rights,

from you under this License will not have their licenses terminated so long as such

parties remain in full compliance.

9. You are not required to accept this License, since you have not signed it.

However, nothing else grants you permission to modify or distribute the Library or itsderivative works. These actions are prohibited by law if you do not accept this License.




A-28LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Therefore, by modifying or distributing the Library (or any work based on the Library),

you indicate your acceptance of this License to do so, and all its terms and conditions

for copying, distributing or modifying the Library or works based on it.

10. Each time you redistribute the Library (or any work based on the Library), the

recipient automatically receives a license from the original licensor to copy, distribute,

link with or modify the Library subject to these terms and conditions. You may not

impose any further restrictions on the recipients' exercise of the rights granted herein.

You are not responsible for enforcing compliance by third parties with this License.

11. If, as a consequence of a court judgment or allegation of patent infringement or

for any other reason (not limited to patent issues), conditions are imposed on you

(whether by court order, agreement or otherwise) that contradict the conditions of this

License, they do not excuse you from the conditions of this License. If you cannot

distribute so as to satisfy simultaneously your obligations under this License and any

other pertinent obligations, then as a consequence you may not distribute the Library atall. For example, if a patent license would not permit royalty-free redistribution of the

Library by all those who receive copies directly or indirectly through you, then the only

way you could satisfy both it and this License would be to refrain entirely from

distribution of the Library.

If any portion of this section is held invalid or unenforceable under any particular

circumstance, the balance of the section is intended to apply, and the section as a whole

is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property

right claims or to contest validity of any such claims; this section has the sole purposeof protecting the integrity of the free software distribution system which is implemented

by public license practices. Many people have made generous contributions to the wide

range of software distributed through that system in reliance on consistent application

of that system; it is up to the author/donor to decide if he or she is willing to distribute

software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence

of the rest of this License.

12. If the distribution and/or use of the Library is restricted in certain countries either

by patents or by copyrighted interfaces, the original copyright holder who places the

Library under this License may add an explicit geographical distribution limitationexcluding those countries, so that distribution is permitted only in or among countries not

thus excluded. In such case, this License incorporates the limitation as if written in the

body of this License.

13. The Free Software Foundation may publish revised and/or new versions of the

Lesser General Public License from time to time. Such new versions will be similar in

spirit to the present version, but may differ in detail to address new problems or

concerns.

Each version is given a distinguishing version number. If the Library specifies a version

number of this License which applies to it and any later version, you have the option offollowing the terms and conditions either of that version or of any later version published





by the Free Software Foundation. If the Library does not specify a license version

number, you may choose any version ever published by the Free Software Foundation.

14. If you wish to incorporate parts of the Library into other free programs whose

distribution conditions are incompatible with these, write to the author to ask for

permission. For software which is copyrighted by the Free Software Foundation, write

to the Free Software Foundation; we sometimes make exceptions for this. Our decision

will be guided by the two goals of preserving the free status of all derivatives of our free

software and of promoting the sharing and reuse of software generally.

NO WARRANTY

15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO

WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE

LAW.

EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERSAND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY

OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED

TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND

PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE

DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR

OR CORRECTION.

16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO

IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY

MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BELIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,

INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR

INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF

DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY

YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH

ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN

ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.


How to Apply These Terms to Your New Libraries

If you develop a new library, and you want it to be of the greatest possible use to the

public, we recommend making it free software that everyone can redistribute and

change. You can do so by permitting redistribution under these terms (or, alternatively,

under the terms of the ordinary General Public License).

To apply these terms, attach the following notices to the library. It is safest to attach

them to the start of each source file to most effectively convey the exclusion of warranty;

and each file should have at least the copyright line and a pointer to where the full notice

is found.

<one line to give the library's name and a brief idea of what it does.>Copyright (C) <year> <name of author>




A-30LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

This library is free software; you can redistribute it and/or modify it under the terms

of the GNU Lesser General Public License as published by the Free Software

Foundation; either version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY

WARRANTY; without even the implied warranty of MERCHANTABILITY or

FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public

License for more details.

You should have received a copy of the GNU Lesser General Public License along

with this library; if not, write to the Free Software Foundation, Inc., 59 Temple

Place, Suite 330, Boston, MA 02111-1307 USA

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your school, if any,to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the

names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the library ̀ Frob' (a library

for tweaking knobs) written by James Random Hacker.

<signature of Ty Coon>, 1 April 1990

Ty Coon, President of Vice

That's all there is to it!

Log4J 1.1.3 (log4j.jar)

Apache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and

distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyright

owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other entities that

control, are controlled by, or are under common control with that entity. For the

purposes of this definition, "control" means (i) the power, direct or indirect, to cause

the direction or management of such entity, whether by contract or otherwise, or

(ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii)

beneficial ownership of such entity.





"You" (or "Your") shall mean an individual or Legal Entity exercising permissions

granted by this License.

"Source" form shall mean the preferred form for making modifications, including but

not limited to software source code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or

translation of a Source form, including but not limited to compiled object code,

generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made

available under the License, as indicated by a copyright notice that is included in

or attached to the work (an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that is

based on (or derived from) the Work and for which the editorial revisions,annotations, elaborations, or other modifications represent, as a whole, an original

work of authorship. For the purposes of this License, Derivative Works shall not

include works that remain separable from, or merely link (or bind by name) to the

interfaces of, the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including the original version of

the Work and any modifications or additions to that Work or Derivative Works

thereof, that is intentionally submitted to Licensor for inclusion in the Work by the

copyright owner or by an individual or Legal Entity authorized to submit on behalf

of the copyright owner. For the purposes of this definition, "submitted” means any

form of electronic, verbal, or written communication sent to the Licensor or itsrepresentatives, including but not limited to communication on electronic mailing

lists, source code control systems, and issue tracking systems that are managed

by, or on behalf of, the Licensor for the purpose of discussing and improving the

Work, but excluding communication that is conspicuously marked or otherwise

designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of

whom a Contribution has been received by Licensor and subsequently

incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License,

each Contributor hereby grants to You a perpetual, worldwide, non-exclusive,

no-charge, royalty-free, irrevocable copyright license to reproduce, prepare

Derivative Works of, publicly display, publicly perform, sublicense, and distribute

the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each

Contributor hereby grants to You a perpetual, worldwide, non-exclusive,

no-charge, royalty-free, irrevocable (except as stated in this section) patent license

to make, have made, use, offer to sell, sell, import, and otherwise transfer the

Work, where such license applies only to those patent claims licensable by such

Contributor that are necessarily infringed by their Contribution(s) alone or by

combination of their Contribution(s) with the Work to which such Contribution(s)

was submitted. If You institute patent litigation against any entity (including a

cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution




A-32LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

incorporated within the Work constitutes direct or contributory patent infringement,

then any patent licenses granted to You under this License for that Work shall

terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or DerivativeWorks thereof in any medium, with or without modifications, and in Source or

Object form, provided that You meet the following conditions:

a) You must give any other recipients of the Work or Derivative Works a copy of

this License; and

b) You must cause any modified files to carry prominent notices stating that You

changed the files; and

c) You must retain, in the Source form of any Derivative Works that You

distribute, all copyright, patent, trademark, and attribution notices from the

Source form of the Work, excluding those notices that do not pertain to anypart of the Derivative Works; and

d) If the Work includes a "NOTICE" text file as part of its distribution, then any

Derivative Works that You distribute must include a readable copy of the

attribution notices contained within such NOTICE file, excluding those notices

that do not pertain to any part of the Derivative Works, in at least one of the

following places: within a NOTICE text file distributed as part of the Derivative

Works; within the Source form or documentation, if provided along with the

Derivative Works; or, within a display generated by the Derivative Works, if

and wherever such third-party notices normally appear. The contents of the

NOTICE file are for informational purposes only and do not modify the

License. You may add Your own attribution notices within Derivative Worksthat You distribute, alongside or as an addendum to the NOTICE text from the

Work, provided that such additional attribution notices cannot be construed as

modifying the License.

You may add Your own copyright statement to Your modifications and may provide

additional or different license terms and conditions for use, reproduction, or

distribution of Your modifications, or for any such Derivative Works as a whole,

provided Your use, reproduction, and distribution of the Work otherwise complies

with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any

Contribution intentionally submitted for inclusion in the Work by You to the Licensorshall be under the terms and conditions of this License, without any additional

terms or conditions. Notwithstanding the above, nothing herein shall supersede or

modify the terms of any separate license agreement you may have executed with

Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names,

trademarks, service marks, or product names of the Licensor, except as required

for reasonable and customary use in describing the origin of the Work and

reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing,

Licensor provides the Work (and each Contributor provides its Contributions) on an

"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,





either express or implied, including, without limitation, any warranties or conditions

of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A

PARTICULAR PURPOSE. You are solely responsible for determining the

appropriateness of using or redistributing the Work and assume any risks

associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort

(including negligence), contract, or otherwise, unless required by applicable law

(such as deliberate and grossly negligent acts) or agreed to in writing, shall any

Contributor be liable to You for damages, including any direct, indirect, special,

incidental, or consequential damages of any character arising as a result of this

License or out of the use or inability to use the Work (including but not limited to

damages for loss of goodwill, work stoppage, computer failure or malfunction, or

any and all other commercial damages or losses), even if such Contributor has

been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work orDerivative Works thereof, You may choose to offer, and charge a fee for,

acceptance of support, warranty, indemnity, or other liability obligations and/or

rights consistent with this License. However, in accepting such obligations, You

may act only on Your own behalf and on Your sole responsibility, not on behalf of

any other Contributor, and only if You agree to indemnify, defend, and hold each

Contributor harmless for any liability incurred by, or claims asserted against, such

Contributor by reason of your accepting any such warranty or additional liability.


APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following boilerplate notice,

with the fields enclosed by brackets "[]” replaced with your own identifying

information. (Don't include the brackets!) The text should be enclosed in the

appropriate comment syntax for the file format. We also recommend that a file or

class name and description of purpose be included on the same "printed page" as

the copyright notice for easier identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this

file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the

License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR

CONDITIONS OF ANY KIND, either express or implied. See the License for the specific

language governing permissions and limitations under the License.




A-34LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

Xerces J 2.2.0 (xercesImpl.jar, xmlParserAPIs.jar)

The Apache Software License, Version 1.1

Copyright (c) 2000 The Apache Software Foundation. All rights reserved.



1. Redistributions of source code must retain the above copyright notice, this list of

conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list

of conditions and the following disclaimer in the documentation and/or other

materials provided with the distribution.

3. The end-user documentation included with the redistribution, if any, must includethe following acknowledgment:

This product includes software developed by the Apache Software Foundation

(http://www.apache.org/).

Alternately, this acknowledgment may appear in the software itself, if and wherever

such third-party acknowledgments normally appear.

4. The names "Apache" and "Apache Software Foundation" must not be used to

endorse or promote products derived from this software without prior written

permission. For written permission, please contact [email protected].

5. Products derived from this software may not be called "Apache", nor may "Apache"

appear in their name, without prior written permission of the Apache Software

Foundation.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES

OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE

DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR

ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT

LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF

USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED

AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE

POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on behalf of

the Apache Software Foundation. For more information on the Apache Software

Foundation, please see <http://www.apache.org/>.

Portions of this software are based upon public domain software originally written at the

National Center for Supercomputing Applications, University of Illinois,

Urbana-Champaign.





Web Works Help API 4.0.5 (wwh4api.dll)

WEBWORKS HELP API

REDISTRIBUTION AGREEMENT

BEFORE PROCEEDING WITH THE INSTALLATION AND/OR USE OF THIS

SOFTWARE, CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS OF

THIS LICENSE AGREEMENT AND LIMITED WARRANTY (The "Agreement").

BY INSTALLING OR USING THIS SOFTWARE YOU INDICATE YOUR ACCEPTANCE

OF THIS AGREEMENT. IF YOU DO NOT ACCEPT OR AGREE WITH THESE TERMS,

YOU MAY NOT INSTALL OR USE THIS SOFTWARE!

PREAMBLE

This Agreement pertains to the WebWorks Help API only and is not valid for any other

software, product, or technology that is owned, marketed, or distributed by QuadralayCorporation.

LICENSE

The WebWorks Help API (Application Programming Interface), including

documentation, source code, object code and/or additional materials (the "Software") is

owned by Quadralay Corporation. This Agreement does not provide you with title or

ownership of Product, but only a right of limited use as outlined in this license

agreement. Quadralay Corporation hereby grant you a non-exclusive, royalty free

license to use the Software as set forth below:

1. Integrate the WebWorks Help API with your Applications, subject to the

redistribution terms below.

2. Modify or adapt the WebWorks Help API in whole or in part for the

development of Applications based on the Software.

3. Use portions of the WebWorks Help API source code or WebWorks Help API

Demo Programs in your own products and libraries.

REDISTRIBUTION RIGHTS

You are granted a non-exclusive, royalty-free right to reproduce and redistribute the

WebWorks Help API in part or entirety in conjunction with software products that you

develop and/or market (the Applications).

RESTRICTIONS

Without the expressed, written consent of Quadralay Corporation, you may NOT: rent,

lease, or sell the WebWorks Help API or any portion of this Software on its own, without

integrating it into your Applications.

SELECTION AND USE

You assume full responsibility for the selection of the WebWorks Help API to achieve

your intended results and for the installation, use and results obtained from the

Software.

LIMITED WARRANTY

THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KINDEITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE




A-36LCT 3.4 - OMN

911-457/02A0340 - Issue 1, October 2011

IMPLIED WARRANTIES MERCHANTIBILITY AND FITNESS FOR A PARTICULAR

PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE

PRODUCT IS WITH YOU. SHOULD THE PRODUCT PROVE DEFECTIVE, YOU

ASSUME THE COST OF ALL NECESSARY SERVICING OR ERROR CORRECTION.

QUADRALAY CORPORATION DOES NOT WARRANT THAT THE FUNCTIONS

CONTAINED IN THE SOFTWARE WILL MEET YOUR REQUIREMENTS OR THAT

THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR

FREE.

No oral or written information given by Quadralay Corporation shall create a warranty.

LIMITATION OF REMEDIES AND LIABILITY.

IN NO EVENT SHALL QUADRALAY CORPORATION, OR ANY OTHER PARTY WHO

MAY HAVE DISTRIBUTED THE SOFTWARE AS PERMITTED ABOVE, BE LIABLE

FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL, OR

CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USETHE SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA

BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD

PARTIES OR FAILURE OF THE SOFTWARE TO OPERATE WITH ANY OTHER

PRODUCTS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF

THE POSSIBILITY OF SUCH DAMAGES.

snmp_if 17.20.6.6

(c) Copyright Siemens S.p.A. 2006

This software is based on SNMP++v3.0n from Jochen Katz:

Copyright (c) 2000 Jochen Katz

This software is based on SNMP++2.6 from Hewlett Packard::

Copyright (c) 1996 Hewlett-Packard Company

ATTENTION: USE OF THIS SOFTWARE IS SUBJECT TO THE FOLLOWING TERMS.

Permission to use, copy, modify, distribute and/or sell this software and/or its

documentation is hereby granted without fee. User agrees to display the above

copyright notice and this license notice in all copies of the software and any

documentation of the software. User agrees to assume all liability for the use of the

software; Hewlett-Packard and Jochen Katz and Siemens S.p.A. make norepresentations about the suitability of this software for any purpose. It is provided

"AS-IS" without warranty of any kind, either express or implied. User hereby grants a

royalty-free license to any and all derivatives based upon this software code base.




SNMP++v3.0n

SNMP++v3.0n

-----------------------------

Copyright (c) 2000 Jochen Katz

This software is based on SNMP++2.6 from Hewlett Packard:

Copyright (c) 1996

Hewlett-Packard Company




copyright notice and this license notice in all copies of the software and anydocumentation of the software. User agrees to assume all liability for the use of the

software; Hewlett-Packard and Jochen Katz make no representations about the

suitability of this software for any purpose. It is provided "AS-IS" without warranty of any

kind, either express or implied. User hereby grants a royalty-free license to any and all

derivatives based upon this software code base.

Karlsruhe, Germany, Mon Jan 15 11:46:36 MET 2001

Copyright (c) 1999

Hewlett-Packard Company




copyright notice and this license notice in all copies of the software and any

documentation of the software. User agrees to assume all liability for the use of the

software; Hewlett-Packard makes no representations about the suitability of this

software for any purpose. It is provided "AS-IS" without warranty of any kind,either

express or implied. User hereby grants a royalty-free license to any and all derivatives

based upon this software code base.