This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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
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
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
I-9LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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
2-1LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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:
– TNMP protocol implemented on TCP/IP
– SNMP protocol implemented on UDP/IP.
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.
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.
2-13LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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-17LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
– 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
2-21LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
– 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
– 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 IP address: from 128.1.0.1 up to 191.255.255.253
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
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.
2-29LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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.
2-31LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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 ).
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.
• 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
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:
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
– 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.71 Creation and configuration of the dial-up connection in Microsoft Windows XP
(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.
5-5LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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).
– 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”.
5-19LCT 3.4 - OMN911-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
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
5-25LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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
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
6-19LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
– 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
6-21LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
– 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
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.
6-39LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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.
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
6-45LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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
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
6-53LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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.
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
6-63LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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).
6-69LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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.
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).
6-85LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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.
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.
Fig. 6.136 Service Protection window (example)
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
– 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 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.
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”.
For some equipment (e.g.: SRAL XD with SVR 3.8 or higher), the login password
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.
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-125LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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
7-7LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
– 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.
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.
7-25LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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;
7-27LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
– 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
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.
A-3LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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.
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
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.
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
A-7LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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
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
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
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
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
A-13LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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
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
A-15LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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.
GNU LESSER GENERAL PUBLIC LICENSE
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
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
A-17LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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
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
A-19LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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-21LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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.
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
A-23LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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
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
A-25LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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-27LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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.
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
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)
A-31LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
"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
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,
A-33LCT 3.4 - OMN911-457/02A0340 - Issue 1, October 2011
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.
END OF TERMS AND CONDITIONS
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.
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.
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 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
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 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