Index

Operating Manual
LCT V5.0 Local Craft Terminal OMN
911-360/02A0500 Issue 1, November 2003
Copyright (C) Siemens Mobile Communications S.p.A. 2003 V.le Piero e Alberto Pirelli, 10 I-20126 Milano
Issued by Customer Documentation Department S.S. 11 Padana Superiore, km 158 I-20060 Cassina de Pecchi MI Technical modifications possible. Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.
LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003
STATUS OF THE MANUAL
STATUS OF THE MANUAL Current: Previous: Issue 1, November 2003 Issue 1, January 2003
In this issue, the indication that the baud rate for the communication with the new equipment is 38400 bps has been added.
R-1
STATUS OF THE MANUAL
LA
N
R-2 LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003
PA
INDEX
INDEX
STATUS OF THE MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R.1 INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.1 LIST OF THE FIGURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.7 LIST OF THE TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.15
GENERAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1

1.1 1.2 1.3 1.4 1.5 Subject and Purpose of the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Local Craft Terminal Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Delivery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4 Related Manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4 List of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4
LCT FUNCTIONS AND FEATURES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

2.1 2.2 2.3 2.3.1 2.4 2.5 2.6 2.6.1 2.6.1.1 2.6.1.2 2.6.1.3 2.6.1.4 2.6.1.5 2.6.2 2.6.3 2.6.4 2.6.5 2.7 2.8 2.8.1 2.8.2 2.8.3 2.9 2.9.1 2.9.2 2.9.2.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 Security Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 Supported Radio Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4 Characteristics of the TCP/IP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Address format for TCP/IP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Host and router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 IP address classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Decimal notation of the IP address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7 Net-Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8 Reserved address values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9 TCP/IP protocol stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10 TCP/IP protocol of the service PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.13 Name solving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.13 Auxiliary utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.14 Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.15 Local Equipment Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.16 LCT - local equipment connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.16 Local map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.16 Testing of the local connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.17 Radio Link Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.18 LCT - radio link connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.18 Routing functions of the NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.20 Routing functions of the SRA Series 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.20
I-1
INDEX
2.9.2.2 2.9.3 2.9.4 2.9.5 2.9.5.1 2.9.5.2 2.9.6 2.9.6.1 2.9.6.2 2.9.6.3 2.9.6.4 2.9.6.5 2.9.6.6 2.10 2.10.1 2.10.2 2.10.2.1 2.10.2.2 2.10.2.3 2.10.3 2.10.4 2.10.5
Routing functions of the SRA L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routing tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection to TMN supervision system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection to TMN supervision system of a SRA Series 3 link . . . . . . . . . . . . . . . . . . . . . Connection to TMN supervision system of a SRA L link . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning and configuration of a radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning of IP addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creation of the link map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of link parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing of the radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples of radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Main problems occurring in the radio link management . . . . . . . . . . . . . . . . . . . . . . . . . . . Validity Conditions of TCP/IP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Validity conditions for IP addresses and Net-Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Net-Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP address - Net-Mask combinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Validity conditions for parameters of the static routing table . . . . . . . . . . . . . . . . . . . . . . . . Validity conditions for the F interface parameters (PC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset of the TCP/IP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.21 2.23 2.23 2.24 2.24 2.25 2.27 2.27 2.28 2.29 2.30 2.30 2.33 2.34 2.34 2.34 2.34 2.36 2.38 2.40 2.40 2.40
SOFTWARE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

3.1 3.2 3.3 3.4 3.5 3.6 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Installation of the SuperTCP program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Installation of Local Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7 Installation of the Equipment Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.12 Updating of the Help On-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.12
CONFIGURATION OF THE SERVICE PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1

4.1 4.2 4.2.1 4.2.1.1 4.2.1.2 4.2.1.3 4.2.2 4.2.2.1 4.2.2.2 4.2.2.3 4.2.3 4.2.3.1 4.2.3.2 4.3 4.3.1 Service PC - Radio Equipment connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Configuration of the LCT - Radio Equipment Connection on F interface . . . . . . . . . . . . . . . 4.1 Configuration of the dial-up connection in Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Installation and configuration of the direct connection via cable . . . . . . . . . . . . . . . . . . . . . . 4.2 Configuration of the remote access service (RAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.11 Creation and configuration of the dial-up connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.16 Configuration of the dial-up connection in Windows 2000. . . . . . . . . . . . . . . . . . . . . . . . . . 4.30 Installation of the direct connection via cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.30 Creation and configuration of the dial-up connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.36 Configuration of the TCP/IP protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.44 Configuration of the dial-up connection in Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.50 Installation of the direct connection via cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.50 Creation and configuration of the dial-up connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.55 Configuration of the Connection to LAN on Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . 4.62 Configuration of the TCP/IP protocol in in Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.63
I-2
INDEX
4.3.2 4.3.3 4.4
Configuration of the TCP/IP protocol in Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.68 Configuration of the TCP/IP protocol in Windows XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.74 Name Solving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.81
LCT - RADIO EQUIPMENT CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1

5.1 5.2 5.2.1 5.2.1.1 5.2.1.2 5.2.2 5.2.2.1 5.2.2.2 5.2.2.3 5.2.3 5.2.4 5.3 5.3.1 5.3.2 5.3.3 5.4 5.4.1 5.4.2 5.5 5.5.1 5.5.2 5.5.2.1 5.5.2.2 5.5.2.3 5.5.2.4 5.5.2.5 5.5.2.6 5.5.2.7 5.6 5.6.1 5.6.2 5.6.3 5.6.3.1 5.6.3.2 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 LCT - Radio Equipment Connection Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Direct connection on F interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Requirements of RS-232C serial cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 Remote connection on F interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 Characteristics of the connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Characteristics and configuration of modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Direct connection on Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5 Remote connection on Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7 Activation of LCT - Radio Equipment Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.8 Activation of the dial-up connection in Windows NT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.9 Activation of the dial-up connection in Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.17 Activation of the dial-up connection in Windows XP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.22 Access to Radio Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.30 Plug-in loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.30 NE opening. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.31 Routing Troubles with the TCP/IP Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.32 Common cases of TCP/IP packet routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.32 Useful commands to solve reachability problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.35 Dial-up monitor window in Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.35 Status window of the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.36 The ipconfig command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.37 The route print command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.38 The route add command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.38 WinTrace utility of the Frontier Technologies software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.39 The tracert command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.40 Troubles in the Dial-up Connection to the Local Equipment . . . . . . . . . . . . . . . . . . . . . . . . 5.41 Local equipment not reacheable using the default local IP address . . . . . . . . . . . . . . . . . . 5.41 Deactivation of the dial-up connection for traffic absence . . . . . . . . . . . . . . . . . . . . . . . . . . 5.41 Detection of the local equipment IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.43 Detection of the local equipment IP address in Windows NT. . . . . . . . . . . . . . . . . . . . . . . . 5.43 Detection of the local equipment IP address in Windows 2000/XP . . . . . . . . . . . . . . . . . . . 5.45
OPERATING GUIDE OF LOCAL CRAFT TERMINAL . . . . . . . . . . . . . . . . . . . . . . . . 6.1

6.1 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.2.5 Functions of Local Craft Terminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 Title bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3 Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3 Displaying area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3 Tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5
I-3
INDEX
6.2.6 6.2.7 6.3 6.3.1 6.3.2 6.3.3 6.4 6.5 6.5.1 6.5.2 6.5.3 6.6 6.6.1 6.6.2 6.7 6.7.1 6.7.2 6.7.3 6.7.4 6.8 6.8.1 6.8.2 6.8.3 6.8.4 6.9 6.9.1 6.9.2 6.9.3 6.10 6.10.1 6.10.2 6.11 6.11.1 6.11.2 6.12 6.12.1 6.12.2 6.12.2.1 6.12.2.2 6.12.3 6.12.4 6.12.5 6.12.6
Scroll bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5 LCT map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5 Local Craft Terminal Start-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 Program start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 Opening of the map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9 Parameters on the control line of the Local Craft Terminal program . . . . . . . . . . . . . . . . . . 6.10 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Open Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Close Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.11 6.11 6.12 6.12
Net-Element Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.13 Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.14 Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.14 Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Field Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Move Map to Top. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Move Map to Bottom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Window Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cascade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Arrange Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Close All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.15 6.15 6.17 6.18 6.18 6.18 6.18 6.18 6.18 6.18 6.19 6.19 6.19 6.19
Menu of Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20 Print to file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.21 NE Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.22 History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.22 Alarms List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.25 Common Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manual setting of date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading/storing of the NE configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storing the configuration on a file (Copy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading of the configuration file (Paste) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inventory data report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Telemeasurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download via FTP of the unit software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.25 6.26 6.27 6.28 6.30 6.32 6.34 6.37 6.40
OPERATING GUIDE OF NETBUILDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1

7.1 7.2 7.2.1 Functions of NetBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3 Title bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4
I-4
INDEX
7.2.2 7.2.3 7.2.4 7.2.5 7.2.6 7.3 7.4 7.4.1 7.4.2 7.4.3 7.4.4 7.4.5 7.4.6 7.4.7 7.5 7.5.1 7.5.2 7.5.3 7.5.3.1 7.5.4 7.5.4.1 7.5.4.2 7.5.4.3 7.6 7.6.1 7.7 7.7.1 7.7.2 7.7.3 7.8 7.8.1 7.8.2 7.8.3 7.9 7.9.1 7.9.2 7.9.2.1 7.9.2.2 7.9.2.3
Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4 Tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5 Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5 Scroll bars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5 Map displaying frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6 Program start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.7 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8 New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8 Open. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8 Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10 Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10 Save As . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10 New Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.12 Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.15 Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.15 Arrange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.15 Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.16 New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.16 Net-Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.17 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.19 Insert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.20 Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.20 Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.20 Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.21 Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.21 Window Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.22 Cascade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.22 Tile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.22 Close All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.22 Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.23 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.23 Using Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.23 About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.23 Menus of the Mouse Right Hand Push-Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.24 Map menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.24 NE menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.25 NE Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.25 NE Cut/Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.25 NE Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.26
I-5
INDEX
LA
N
I-6 LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003
PA
LIST OF THE FIGURES
LIST OF THE FIGURES

Fig. 2.1 Fig. 2.2 Fig. 2.3 Fig. 2.4 Fig. 2.5 Fig. 2.6 Fig. 2.7 Fig. 2.8 Fig. 2.9 Fig. 2.10 Fig. 2.11 Fig. 2.12 Fig. 2.13 Fig. 2.14 Fig. 2.15 Fig. 2.16 Fig. 2.17 Fig. 2.18 Fig. 3.1 Fig. 3.2 Fig. 3.3 Fig. 3.4 Fig. 3.5 Fig. 3.6 Fig. 3.7 Fig. 3.8 Fig. 3.9 Fig. 3.10 Fig. 3.11 Fig. 3.12 Fig. 3.13 Fig. 3.14 Fig. 3.15 Fig. 3.16 Fig. 3.17 Fig. 4.1 Fig. 4.2 Fig. 4.3 Fig. 4.4 Fig. 4.5 Fig. 4.6 Fig. 4.7 Fig. 4.8 Fig. 4.9 Fig. 4.10 Fig. 4.11 Fig. 4.12 Fig. 4.13 Fig. 4.14 Fig. 4.15 Structure of IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7 Example of Net-Mask for Class B IP address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9 TCP/IP protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.11 TCP/IP protocol stack for LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.12 LCT software architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.15 Connection between service PC and local radio equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.16 Radio link structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.19 Radio link structure with repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.19 Routing architecture of the SRA Series 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.20 Example of routing strategy in a SRA L link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.21 Routing architecture of the SRA L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.22 Configurations of SRA Series 3 - TMN connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.24 Configurations of SRA L - TMN connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.25 Local link between the Q-Adapter unit and the Controller units of the station SRA Ls. . . . . . . . . . 2.26 Stack of standard Qx/Q3 protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.26 Example of a stand-alone radio link (SRA L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.31 Example of a Intranet type radio link (SRA L). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.31 Example of a Internet radio link (SRA L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.32 Installation of SuperTCP program (1/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Installation of SuperTCP program (2/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Installation of SuperTCP program (3/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Installation of SuperTCP program (4/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Installation of SuperTCP program (5/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Installation of SuperTCP program (6/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Installation of SuperTCP program (7/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5 Installation of SuperTCP program (8/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5 Installation of SuperTCP program (9/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6 Installation of LCT (1/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8 Installation of LCT (2/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8 Installation of LCT (3/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9 Installation of LCT (4/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9 Installation of LCT (5/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10 Installation of LCT (6/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10 Installation of LCT (7/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11 Installation of LCT (8/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11 Installation and configuration of the direct connection in Windows NT (1/14) . . . . . . . . . . . . . . . . . 4.3 Installation and configuration of the direct connection in Windows NT (2/14) . . . . . . . . . . . . . . . . . 4.4 Installation and configuration of the direct connection in Windows NT (3/14) . . . . . . . . . . . . . . . . . 4.4 Installation and configuration of the direct connection in Windows NT (4/14) . . . . . . . . . . . . . . . . . 4.5 Installation and configuration of the direct connection in Windows NT (5/14) . . . . . . . . . . . . . . . . . 4.5 Installation and configuration of the direct connection in Windows NT (6/14) . . . . . . . . . . . . . . . . . 4.6 Installation and configuration of the direct connection in Windows NT (7/14) . . . . . . . . . . . . . . . . . 4.6 Installation and configuration of the direct connection in Windows NT (8/14) . . . . . . . . . . . . . . . . . 4.7 Installation and configuration of the direct connection in Windows NT (9/14) . . . . . . . . . . . . . . . . . 4.7 Installation and configuration of the direct connection in Windows NT (10/14) . . . . . . . . . . . . . . . . 4.8 Installation and configuration of the direct connection in Windows NT (11/14) . . . . . . . . . . . . . . . . 4.8 Installation and configuration of the direct connection in Windows NT (12/14) . . . . . . . . . . . . . . . . 4.9 Installation and configuration of the direct connection in Windows NT (13/14) . . . . . . . . . . . . . . . 4.10 Installation and configuration of the direct connection in Windows NT (14/14) . . . . . . . . . . . . . . . 4.10 Configuration of the RAS service in Windows NT (1/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.12
I-7
LIST OF THE FIGURES
Fig. 4.16 Fig. 4.17 Fig. 4.18 Fig. 4.19 Fig. 4.20 Fig. 4.21 Fig. 4.22 Fig. 4.23 Fig. 4.24 Fig. 4.25 Fig. 4.26 Fig. 4.27 Fig. 4.28 Fig. 4.29 Fig. 4.30 Fig. 4.31 Fig. 4.32 Fig. 4.33 Fig. 4.34 Fig. 4.35 Fig. 4.36 Fig. 4.37 Fig. 4.38 Fig. 4.39 Fig. 4.40 Fig. 4.41 Fig. 4.42 Fig. 4.43 Fig. 4.44 Fig. 4.45 Fig. 4.46 Fig. 4.47 Fig. 4.48 Fig. 4.49 Fig. 4.50 Fig. 4.51 Fig. 4.52 Fig. 4.53 Fig. 4.54 Fig. 4.55 Fig. 4.56 Fig. 4.57 Fig. 4.58 Fig. 4.59 Fig. 4.60 Fig. 4.61 Fig. 4.62 Fig. 4.63 Fig. 4.64 Fig. 4.65 Fig. 4.66 Fig. 4.67 Fig. 4.68 Fig. 4.69 Fig. 4.70
Configuration of the RAS service in Windows NT (2/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the RAS service in Windows NT (3/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the RAS service in Windows NT (4/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the RAS service in Windows NT (5/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the RAS service in Windows NT (6/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the RAS service in Windows NT (7/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the RAS service in Windows NT (8/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the RAS service in Windows NT (9/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (1/24) . . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (2/24) . . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (3/24) . . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (4/24) . . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (5/24) . . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (6/24) . . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (7/24) . . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (8/24) . . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (9/24) . . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (10/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (11/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (12/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (13/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (14/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (15/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (16/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (17/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (18/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (19/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (20/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (21/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (22/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (23/24) . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows NT (24/24) . . . . . . . . . . . . . . . . Installation of the direct connection in Windows 2000 (1/11). . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of the direct connection in Windows 2000 (2/11). . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of the direct connection in Windows 2000 (3/11). . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of the direct connection in Windows 2000 (4/11). . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of the direct connection in Windows 2000 (5/11). . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of the direct connection in Windows 2000 (6/11). . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of the direct connection in Windows 2000 (7/11). . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of the direct connection in Windows 2000 (8/11). . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of the direct connection in Windows 2000 (9/11). . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of the direct connection in Windows 2000 (10/11). . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of the direct connection in Windows 2000 (11/11). . . . . . . . . . . . . . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows 2000 (1/13) . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows 2000 (2/13) . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows 2000 (3/13) . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows 2000 (4/13) . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows 2000 (5/13) . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows 2000 (6/13) . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows 2000 (7/13) . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows 2000 (8/13) . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows 2000 (9/13) . . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows 2000 (10/13) . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows 2000 (11/13) . . . . . . . . . . . . . . Creation and configuration of the dial-up connection in Windows 2000 (12/13) . . . . . . . . . . . . . .
4.12 4.13 4.13 4.14 4.14 4.15 4.15 4.16 4.17 4.18 4.18 4.19 4.19 4.20 4.20 4.21 4.22 4.22 4.23 4.23 4.24 4.24 4.25 4.25 4.26 4.26 4.27 4.27 4.28 4.28 4.29 4.29 4.31 4.31 4.32 4.32 4.33 4.33 4.34 4.34 4.35 4.35 4.36 4.37 4.38 4.38 4.39 4.39 4.40 4.40 4.41 4.41 4.42 4.42 4.43
I-8
LIST OF THE FIGURES
Creation and configuration of the dial-up connection in Windows 2000 (13/13). . . . . . . . . . . . . . . 4.44 Configuration of the TCP/IP protocol in Windows 2000 (1/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.45 Configuration of the TCP/IP protocol in Windows 2000 (2/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.45 Configuration of the TCP/IP protocol in Windows 2000 (3/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.46 Configuration of the TCP/IP protocol in Windows 2000 (4/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.46 Configuration of the TCP/IP protocol in Windows 2000 (5/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.47 Configuration of the TCP/IP protocol in Windows 2000 (6/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.47 Configuration of the TCP/IP protocol in Windows 2000 (7/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.48 Configuration of the TCP/IP protocol in Windows 2000 (8/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.48 Configuration of the TCP/IP protocol in Windows 2000 (9/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.49 Installation of the direct connection in Windows XP (1/12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.51 Installation of the direct connection in Windows XP (2/12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.51 Installation of the direct connection in Windows XP (3/12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.52 Installation of the direct connection in Windows XP (4/12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.52 Installation of the direct connection in Windows XP (5/12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.52 Installation of the direct connection in Windows XP (6/12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.53 Installation of the direct connection in Windows XP (7/12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.53 Installation of the direct connection in Windows XP (8/12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.53 Installation of the direct connection in Windows XP (9/12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.54 Installation of the direct connection in Windows XP (10/12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.54 Installation of the direct connection in Windows XP (11/12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.54 Installation of the direct connection in Windows XP (12/12). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.55 Creation and configuration of the dial-up connection in Windows XP (1/15) . . . . . . . . . . . . . . . . . 4.56 Creation and configuration of the dial-up connection in Windows XP (2/15) . . . . . . . . . . . . . . . . . 4.56 Creation and configuration of the dial-up connection in Windows XP (3/15) . . . . . . . . . . . . . . . . . 4.57 Creation and configuration of the dial-up connection in Windows XP (4/15) . . . . . . . . . . . . . . . . . 4.57 Creation and configuration of the dial-up connection in Windows XP (5/15) . . . . . . . . . . . . . . . . . 4.57 Creation and configuration of the dial-up connection in Windows XP (6/15) . . . . . . . . . . . . . . . . . 4.58 Creation and configuration of the dial-up connection in Windows XP (7/15) . . . . . . . . . . . . . . . . . 4.58 Creation and configuration of the dial-up connection in Windows XP (8/15) . . . . . . . . . . . . . . . . . 4.58 Creation and configuration of the dial-up connection in Windows XP (9/15) . . . . . . . . . . . . . . . . . 4.59 Creation and configuration of the dial-up connection in Windows XP (10/15) . . . . . . . . . . . . . . . . 4.59 Creation and configuration of the dial-up connection in Windows XP (11/15) . . . . . . . . . . . . . . . . 4.60 Creation and configuration of the dial-up connection in Windows XP (12/15) . . . . . . . . . . . . . . . . 4.60 Creation and configuration of the dial-up connection in Windows XP (13/15) . . . . . . . . . . . . . . . . 4.61 Creation and configuration of the dial-up connection in Windows XP (14/15) . . . . . . . . . . . . . . . . 4.61 Creation and configuration of the dial-up connection in Windows XP (15/15) . . . . . . . . . . . . . . . . 4.62 TCP/IP protocol configuration in Windows NT (1/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.64 TCP/IP protocol configuration in Windows NT (2/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.64 TCP/IP protocol configuration in Windows NT (3/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.65 TCP/IP protocol configuration in Windows NT (4/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.65 TCP/IP protocol configuration in Windows NT (5/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.66 TCP/IP protocol configuration in Windows NT (6/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.66 TCP/IP protocol configuration in Windows NT (7/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.67 TCP/IP protocol configuration in Windows NT (8/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.67 TCP/IP protocol configuration in Windows NT (9/9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.68 TCP/IP protocol configuration in Windows 2000 (1/10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.69 TCP/IP protocol configuration in Windows 2000 (2/10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.70 TCP/IP protocol configuration in Windows 2000 (3/10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.70 TCP/IP protocol configuration in Windows 2000 (4/10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.71 TCP/IP protocol configuration in Windows 2000 (5/10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.71 TCP/IP protocol configuration in Windows 2000 (6/10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.72 TCP/IP protocol configuration in Windows 2000 (7/10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.72 TCP/IP protocol configuration in Windows 2000 (8/10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.73 TCP/IP protocol configuration in Windows 2000 (9/10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.73
I-9
LIST OF THE FIGURES
TCP/IP protocol configuration in Windows 2000 (10/10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.74 TCP/IP protocol configuration in Windows XP (1/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.75 TCP/IP protocol configuration in Windows XP (2/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.76 TCP/IP protocol configuration in Windows XP (3/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.76 TCP/IP protocol configuration in Windows XP (4/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.77 TCP/IP protocol configuration in Windows XP (5/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.77 TCP/IP protocol configuration in Windows XP (6/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.78 TCP/IP protocol configuration in Windows XP (7/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.78 TCP/IP protocol configuration in Windows XP (8/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.79 TCP/IP protocol configuration in Windows XP (9/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.79 TCP/IP protocol configuration in Windows XP (10/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.80 TCP/IP protocol configuration in Windows XP (11/11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.80 Example of hosts file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.82 LCT - radio equipment direct connection on F interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 LCT - radio link direct connection on F interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 RS-232C connecting cable between LCT and radio equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 LCT - radio equipment remote connection on F interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 LCT - radio link remote connection on F interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 LCT - SRA Series 3 direct connection on Ethernet interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6 LCT - SRA Series 3 link direct connection on Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6 LCT - radio equipment remote connection on Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7 LCT - radio link remote connection on Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.8 Activation of the dial-up connection in Windows NT (1/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.10 Activation of the dial-up connection in Windows NT (2/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.11 Activation of the dial-up connection in Windows NT (3/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.11 Activation of the dial-up connection in Windows NT (4/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.12 Activation of the dial-up connection in Windows NT (5/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.12 Activation of the dial-up connection in Windows NT (6/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.13 Activation of the dial-up connection in Windows NT (7/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.13 Activation of the dial-up connection in Windows NT (8/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.14 Activation of the dial-up connection in Windows NT (9/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.14 Activation of the dial-up connection in Windows NT (10/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.15 Activation of the dial-up connection in Windows NT (11/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.15 Activation of the dial-up connection in Windows NT (12/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.16 Activation of the dial-up connection in Windows NT (13/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.16 Closing of the dial-up connection in Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.17 Activation of the dial-up connection in Windows 2000 (1/12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.18 Activation of the dial-up connection in Windows 2000 (2/12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.19 Activation of the dial-up connection in Windows 2000 (3/12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.19 Activation of the dial-up connection in Windows 2000 (4/12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.20 Activation of the dial-up connection in Windows 2000 (5/12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.20 Activation of the dial-up connection in Windows 2000 (6/12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.20 Activation of the dial-up connection in Windows 2000 (7/12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.20 Activation of the dial-up connection in Windows 2000 (8/12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.21 Activation of the dial-up connection in Windows 2000 (9/12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.21 Activation of the dial-up connection in Windows 2000 (10/12) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.21 Activation of the dial-up connection in Windows 2000 (11/12) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.22 Activation of the dial-up connection in Windows 2000 (12/12) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.22 Activation of the dial-up connection in Windows XP (1/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.24 Activation of the dial-up connection in Windows XP (2/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.24 Activation of the dial-up connection in Windows XP (3/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.25 Activation of the dial-up connection in Windows XP (4/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.25 Activation of the dial-up connection in Windows XP (5/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.26 Activation of the dial-up connection in Windows XP (6/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.26 Activation of the dial-up connection in Windows XP (7/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.27
I-10
LIST OF THE FIGURES
Activation of the dial-up connection in Windows XP (8/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.27 Activation of the dial-up connection in Windows XP (9/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.27 Activation of the dial-up connection in Windows XP (10/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.28 Activation of the dial-up connection in Windows XP (11/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.28 Activation of the dial-up connection in Windows XP (12/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.29 Activation of the dial-up connection in Windows XP (13/13) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.29 Example of local map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.30 Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.31 Window of the loading of configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.32 Forcing of Use default gateway on remote network option in Windows NT . . . . . . . . . . . . . . . . . 5.33 Forcing of Use default gateway on remote network option in Windows 2000 . . . . . . . . . . . . . . . 5.34 Forcing of Use default gateway on remote network option in Windows XP . . . . . . . . . . . . . . . . . 5.34 Dial-up monitor window in Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.35 Status window of the connection in Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.36 Status window of the connection in Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.36 The ipconfig command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.37 The route print command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.38 WinTrace utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.39 The tracert command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.40 ping t command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.42 RAS monitor icon in Windows NT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.42 Reset of the dial-up connection in Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.43 Detection of the local equipment IP address in Windows NT (1/3). . . . . . . . . . . . . . . . . . . . . . . . . 5.44 Detection of the local equipment IP address in Windows NT (2/3). . . . . . . . . . . . . . . . . . . . . . . . . 5.44 Detection of the local equipment IP address in Windows NT (3/3). . . . . . . . . . . . . . . . . . . . . . . . . 5.45 User Interface of the Local Craft Terminal program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 Example of window for the selection of a value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4 Example of window for the data entry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5 Programs menu with Radio Management 5.0 folder (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 Program starting-up presentation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 Base window of the Local Craft Terminal program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8 File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.11 Window for the Open Map command of the File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.11 Error message caused by the opening of a map with more than three NEs . . . . . . . . . . . . . . . . . 6.11 Window for the map closing confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.12 Confirmation window for exiting the program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.12 Net-Element menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.13 NE menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.13 NE menu activated pressing the right-hand push-button of the mouse . . . . . . . . . . . . . . . . . . . . . 6.13 NE opening window with Security enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.14 NE opening window with Security disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.14 Options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.15 COLOR SELECTION window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.16 Color window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.16 Color window to define the customized colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.16 FIELD STATUS DISPLAY SELECTION window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.17 Selection of the strings for the signalling of the field status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.17 Window menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.18 Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.19 About Local Craft Terminal window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.19 Menu of window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20 Window for the Print to file command of the file menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20 Unavailability information message window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20 Window for the file over-writing confirmation of the Print to file command . . . . . . . . . . . . . . . . . . . 6.21 Recording file of the window data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.21
I-11
LIST OF THE FIGURES
History menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.22 Recording of the events (1/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.23 Recording of the events (2/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.23 Recording of the events (3/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.24 Recording of the events (4/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.24 Recording of the events (5/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.24 Recording of the events (6/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.24 ALARMS LIST window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.25 Date and time setting (1/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.26 Date and time setting (2/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.27 Date and time setting (3/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.27 Date and time setting (4/4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.27 Storing the configuration on a file (1/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.28 Storing the configuration on a file (2/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.28 Storing the configuration on a file (3/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.28 Storing the configuration on a file (4/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.29 Storing the configuration on a file (5/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.29 Storing the configuration on a file (6/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.29 Loading of the configuration file (1/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.30 Loading of the configuration file (2/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.30 Loading of the configuration file (3/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.31 Loading of the configuration file (4/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.31 Loading of the configuration file (5/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.31 Performance recording (1/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.32 Performance recording (2/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.33 Performance recording (3/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.33 Performance recording (4/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.33 Performance recording (5/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.33 Performance recording (6/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.33 Performance recording (7/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.34 Performance recording (8/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.34 Report of the inventory data (1/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.35 Report of the inventory data (2/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.35 Report of the inventory data (3/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.35 Report of the inventory data (4/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.35 Report of the inventory data (5/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36 Report of the inventory data (6/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.36 Telemeasurement (1/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.37 Telemeasurement (2/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38 Telemeasurement (3/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38 Telemeasurement (4/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38 Telemeasurement (5/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38 Telemeasurement (6/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.38 Telemeasurement (7/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.39 Telemeasurement (8/8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.39 Example of map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3 User interface of the NetBuilder program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4 Programs menu with Radio Management 5.0 folder (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.7 Initial screen of the NetBuilder program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.7 File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8 Window for the Open command of the File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.9 Saving confirmation window for the Close command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10 Window for the Save As command of the File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.11 Saving confirmation window for the Save As command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.11 New Discovery window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.13
I-12
LIST OF THE FIGURES
Fig. 7.11 Fig. 7.12 Fig. 7.13 Fig. 7.14 Fig. 7.15 Fig. 7.16 Fig. 7.17 Fig. 7.18 Fig. 7.19 Fig. 7.20 Fig. 7.21 Fig. 7.22 Fig. 7.23 Fig. 7.24 Fig. 7.25 Fig. 7.26 Fig. 7.27 Fig. 7.28 Fig. 7.29 Fig. 7.30 Fig. 7.31 Fig. 7.32 Fig. 7.33 Fig. 7.34 Fig. 7.35 Fig. 7.36 Fig. 7.37
Messagge of unvalid maximum number of NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.13 Discovery in progress window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.13 Message of failed searching procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.13 Example of NE icon adding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.14 Example of NE icon displacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.14 Confirmation window for the program exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.15 Confirmation window for the map saving at the program exit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.15 Edit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.15 Error window for object copying operation not allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.16 New menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.16 NE insertion window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.17 Error window for name/IP address of NE not set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.18 Error window for NE name duplicated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.18 Error window for NE IP address duplicated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.18 Error window for NE maximum limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.18 Background menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.19 Window for the Insert command of the Background menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.20 Window for the Change command of the Background menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.20 Options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.21 Discovery Option window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.22 Window menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.22 Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.23 About NetBuilder window (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.23 Map sub-menus and menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.24 NE menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.25 Window of the NE properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.25 Confirmation window for NE deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.26
I-13
LIST OF THE FIGURES
LA
N
PA
LIST OF THE TABLES
LIST OF THE TABLES

Tab. 1.1 Tab. 2.1 Tab. 2.2 Tab. 6.1 Tab. 6.2 Tab. 6.3 Tab. 7.1 Tab. 7.2 Functions of the LCT V5.0 software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Characteristics of IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8 Reserved and available Internet addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10 Tool bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5 Default color configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.15 Default configuration of the strings for the signalling of the field statuses . . . . . . . . . . . . . . . . . . . 6.17 Tool bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5 Icons for the description of the elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6
I-15
LIST OF THE TABLES
LA
N
PA
1 - GENERAL INFORMATION
1 GENERAL INFORMATION
1.1 Subject and Purpose of the Manual
This OMN Manual provides the information required for configuration and the management of the equipment relevant to a radio link and/or to the local radio equipment by means of the use of LCT V5.0 software. LCT software consists of the following application programs: Local Craft Terminal: application program that implements the management functions of the equipment of a radio link and/or of the local radio equipment. NetBuilder: graphic tool for the creation/change of the Local Craft Terminal configuration file (map). SuperTCP: this is the application program providing the utilities, with graphical mode, relevant to TCP/IP protocol.
Usually, a radio link is composed by two radio equipment and it can contain up to three radio equipment in case of add-drop configuration. Then, LCT is not able to manage more than three NEs. LCT uses, as management application protocol, the proprietary TNMP protocol implemented on the TCP/IP protocol. It is used the TCP/IP protocol provided by the operating system itself (Windows NT/2000/XP). The system supports two versions of the TNMP protocol: TNMP and extended TNMP. On the contrary of the preceding version, the most recent one (extended TNMP) supports the time references of the events. In case of OSI class equipment (equipment with TNMP protocol implemented on OSI stack), from LCT it is possible to execute only the connection and the management of the local equipment. For every kind of radio equipment, a specific plug-in is provided, which makes the equipment control and configuration possible using Local Craft Terminal. For the using modes of the operative menu, implemented by the plug-in of every equipment, refer to OMN Manual of the plug-in.
1-1
1.2 Local Craft Terminal Functions

Tab. 1.1 lists the functions of LCT V5.0 software. Tab. 1.1 Functions of the LCT V5.0 software Supported operating system: Windows NT 4.0 (Server or Workstation) Windows 2000 (Server or Professional) Windows XP Professional SRA L 8x2 Mbit/s SRA L 16x2 Mbit/s SRA L fully outdoor SRT 1C SRA SRA Series 3 SPS E SRA 4 SRAL XD DualQ-Adapter SRT 1S SRT 1 SRT 1F SPS 155 S-Link Normal SNMP equipment
Supported radio equipment:
Not supported radio equipment: Functions:
Independent updating of the engine (the plugs-in are kept) Independent updating of the single plug-in Millenium compliance NE layer support of: Fault Management Configuration Management Performance Management Security Management LCT NE interface: base TNMP on TCP/IP extended TNMP on TCP/IP GUI interface complying with Microsoft Windows Style Guide NE icons with the indication of the name and of the radio equipment type Summarized signalling of the alarms according to the severity level Configuration of the colours used for the alarm/status signallings Background drawing for local map/link maps Synchronization (date and time relevant of the NE synchronized with the ones relevant to LCT) Alarm support at NE level: Equipment alarms Station alarm input Equipment remote-controls (continued)
1-2
Tab. 1.1
Functions of the LCT V5.0 software (continued) Fault Management: Alarm displaying at NE level Automatic alarm indication List of the active alarms relevant to the NEs NE history report Configuration Management: Configuration of the NEs by means of GUI Displaying of the tree structure relevant to the radio link Copy/paste operations of the NE configuration Download, via FTP, of the unit embedded software for NE with IP protocol Configuration of the NE date and time Performance Management: Performance according to ITU-T G.821/G.826 15 minutes or 24 hours measurement period Manual or scheduled activation of the NE performance log Remote measurements (e.g. RF RX power) with displaying of diagrams or tables in Microsoft Excel Security Management: Support of three user classes with different rights and password Crypthing of the login password Login at NE level Recording on ASCII file and printing of the current GUI window data Help on line for every application program, context sensitive (F1 key) for the NE plugs-in
1-3
1.3 Delivery
LCT V5.0 software is provided on CD-ROM and it is comprised into the equipment delivery. The LCT CD-ROM software contains: the software (Local Craft Terminal and NetBuilder) for Windows NT/2000/XP to execute the management of the equipment relevant to a radio link and/or of the local radio equipment the SuperTCP program the radio equipment software plug-in.
1.4 Related Manuals

The Information concerning LCT are available also into the following Manuals: OMN Manual for System Administrator of NetViewer OMN Manuals relevant to the equipment plug-in; it is foreseen a Manual for each plug-in, that contains the information necessary for the management of the radio equipment, by NetViewer or LCT (if it is supported).
1.5 List of Abbreviations

A/D-RPT Add/Drop Repeater AIS Alarm Indication Signal ALM Alarm AT Asynchronous Transfer BB Base Band BBE Background Block Error BBER Background Block Error Ratio BER Bit Error Ratio BMP Bitmap CDC Carrier Detection Control DCC Data Communication Channel
1-4
DCE Data Communication Equipment DNS Domain Name Server DTE Data Terminal Equipment DTR Data Terminal Ready DUALQ DualQ-Adapter Equipment EB Errored Block ECC Embedded Communication Channel EIA Electronics Industry Association EM-OS Element Management - Operating System ES Errored Second ESR Errored Second Ratio FERF Far End Receive Failure FD Frequency Diversity FTP File Transfer Protocol GND Ground GNE Gateway Network Element GUI Graphical User Interface H/S Hot-Standby HW Hardware I/O Input/Output IANA Internet Assigned Numbers Authority
1-5
IDU Indoor Unit ID Identifier IEEE Institute of Electrical and Electronics Engineers IF Interface IN Input IP Internet Protocol ISO International Organisation for Standardization ITU International Telecommunication Union LAN Local Area Network LCT Local Craft Terminal LLC Logical Link Control LOF Loss of Frame LOP Loss of Pointer MAC Media Access Control MS Multiplex Section MSOH Multiplex Section OverHead NE Network Element NIC Network Interface Card ODU Outdoor Unit OMN Operating Manual OS Operating System
1-6
OSI Open System Interconnection OUT Output PC Personal Computer PDH Plesiochronous Digital Hierarchy PPP Point to Point Protocol QD2 Q Interface Specification of Deutsche Telecom Ag QD2/B3 Q Interface Specification of Deutsche Telecom AG using OSI Protocol Stack Qx Q Interface Specification Qx/B3 Q Interface Specification using OSI Protocol Stack RAS Remote Access Service RF Radio Frequency RIP Routing Information Control RRAS Routing and Remote Access Service RS Regenerator Section RSOH Regenerator Section OverHead RX Reception R/O Read Only R/W Read/Write SDH Synchronous Digital Hierarchy SES Severely Errored Second SESR Severely Errored Second Ratio
1-7
SLIP Single Link Internet Protocol SOH Section OverHead SRA Point-to-Point STM 1 Medium Capacity Access Radio SRA L Point-to-Point PDH Low Capacity Access Radio SRAL XD Point-to-Point PDH Low Capacity Access Radio SRA Series 3 Point-to-Point STM 1 Medium Capacity Access Radio SRA 4 Point-to-Point STM 1 Medium Capacity Access Radio SRT 1C Point-to-Point STM 1 High Capacity Trunk Radio STM Synchronous Transport Module STM-1/4/6 Synchronous Transport Module (155 Mbit/s, 622 Mbit/s, 2.4 Gbit/s) SVR Software Version Release SW Software TCP Transmission Control Protocol TMG TeleMeasure Generator TMN Telecommunications Management Network TNMP Trivial Network Management Protocol TX Transmission UAS Unavailable Second UMN User Manual UNEQ Unequipped VC Virtual Container
1-8
WINS Windows Internet Name Service
1-9
LA
N
1-10 LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003
PA
2 - LCT FUNCTIONS AND FEATURES
2 LCT FUNCTIONS AND FEATURES

2.1 General
The Local Craft Terminal program executes the Element Manager function and it allows the management and the configuration of the equipment relevant to a radio link and/or of the local radio equipment. The graphical interface for the access to the equipment is composed by a map, created through the NetBuilder tool (Operating Guide of NetBuilder). The Local Craft Terminal program can manage maps with a maximum of 3 NEs. LCT uses, as management application protocol, the proprietary TNMP protocol implemented on the TCP/IP protocol. The program supports two versions of the TNMP protocol: base TNMP and extended TNMP. On the contrary of the preceding version (base TNMP), the most recent one (extended TNMP) supports the time references of the events. In case of radio equipment with OSI class (equipment with TNMP protocol implemented on OSI stack), it is possible to execute only the management of the local radio equipment. The Local Craft Terminal program allows performing the following main functions: to open and to display the connection map to the NEs to start-up the connection with the NEs, activating it at the map opening to execute, by means of a periodic polling, the monitoring of the connection and alarm status relevant to the NEs to access to the single NEs, that is to upload the relevant configuration files and operating menus to configure and to check each NE, through the relevant operating menu to manage the safety access (Security) to the NEs, that is to allow the access only for the users authorized through password.
LCT does not know anything before of the equipment to be managed, but it dynamically uploads all the necessary information from the equipment plug-in that constitutes the configuration and control application program. At the map opening, the Local Craft Terminal program automatically acknoledges the present equipment type, if it has been installed the relevant plug-in; if it is present a type of radio equipment and it has not already been installed the relevant plug-in, the Local Craft Terminal program detects its presence but it is not able to acknoledge such an equiment and then to manage it. The operator can execute the installation of a plug-in for each type of radio equipment also after the installation of the Local Craft Terminal program; in such a case, if the Local Craft Terminal program is already running, it is necessary to stop it and, then, to restart the program in such a way to allow the uploading of the new plug-in.
2-1
2.2 Fault Management

LCT manages the diagnostics of the NE pointing out the occurrence of an alarm situation. Different alarm display mode are available: Visual alarm Some visual signalling modes of the alarm situations are available with different detail levels: Colour of the unit Into the NE management windows, the unit with the alarm situation is pointed out by means of a colour changing. Alarm identification wording Into the NE management windows, the system points out all the possible alarm roots, coupling to each root an identification wording that changes its colour if it is present the corresponding alarm situation. List of the alarms It is available the list of all the alarms activated on the NE. History To allow the execution of an analysis and of an evaluation concerning the operation along the time of the NEs, LCT allows executing the recording of the events (alarms, status changes, ...) concerning the NE operation.
2.3 Configuration Management

LCT allows reading the current configuration of a NE and changing it. The main features managed are the following ones: control of the functioning status diagnostic management copy/paste of NE configuration configuration of the system and of the equipment configuration of the operating parameters configuration of the network parameters configuration of the date and of the time (it is significant only in case of network synchronization disabled) hardware/software forcing actions execution of the tests protection management reading of the inventory data, with the possibility to insert notes (e.g.: installation date, repairing date, malfunctioning type, etc.) useful for the maintenance operations.
2-2
2.3.1
Performance Management
LCT collects, displays and records, into a log file, the NE performances, according to the ITU-T G.821/G.826 Recc.. The user can directly require, ask and display the NE performance or run a performance log for successive evaluations. The performances can be exported in such a way to allow the processing and the displaying by means of external tools. It is possible as the recording manual activation as the scheduled one of the NE performance logs. The performances comprises the following data: UAS (Number of Seconds of Unavailability): they are the unavailability seconds of the connection into a defined observation time range. SES (Number of Severely Errored Seconds): they are the seconds when it occurs one of the following conditions: errored block percentage equal to or higher than 30% presence of at least one particular event called defect. ES (Number of Errored Seconds): they are the seconds when there is the presence of at least one errored block. BBE (Number of Background Block Errors): it is the number of the errored blocks into a not SES second. OI (Number of Outage Intensity): it is the number of the unavailability events into a defined observation time range.
Then, LCT makes available a tool (TMG) for the execution of remote measurements on some operating parameters (e.g.: received RF power) of the NE. The TMG tool is integrated with Microsoft Excel, because it saves before the data on ASCII file and then, it runs automatically Excel, in such a way to display the measurement as a graphic diagram and/or as a table.
2.4 Security Management

The Security allows the access to NE only to the authorized users. Each user is characterized by a user class and by a password. The Security configuration (enabling status and password) is specific for each NE and it is stored into the NE memory.. The NE Security has to be enabled if the accesses of two or more managers are possible at the same time (e.g.: Net Viewer and LCT). The system provides the following three different user classes: Read Only: it allows the access to the functions in reading mode only Read Write: it allows the access to the functions as in reading mode as in writing one, with the exception of the functions reserved for the Admin user class Admin: it allows the access to all the functions as in reading mode as in writing one.
2-3
It is possible to set/change the Security configuration by the NE operating menu, only if the access is executed using the Admin user class 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 need for the insertion of the password. The only restriction is that it is not possible to change the settings relevant to the Security (enabling status and password). 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. If the NE security has been disabled, at the next enabling it gets newly the preceding set passwords.
2.5 Supported Radio Equipment

The radio equipment currently supported by LCT are the following ones: SRA Series 3 SRA 4 SRT 1C SRA SRA L 8x2 Mbit/s SRA L 16x2 Mbit/s SRA L fully outdoor SRAL XD SPS E.
Inoltre LCT supporta anche lapparato di routing: DualQ-Adapter.
Every equipment is equipped with a F interface (serial RS-232C) for the connection of the LCT. From the management point of view, the radio equipment can be subdivided into the following groups: IP-TNMP class radio equipment Equipment for the transmission of the management information via radio using the TNMP management application protocol implemented on the TCP/IP protocol (IP stack). The IP class radio equipment are the following ones: SRA Series 3 SRA 4 SRA L 8x2 Mbit/s SRA L 16x2 Mbit/s SRA L fully outdoor SRAL XD. In case of IP class radio equipment, from LCT, it is possible to execute the
2-4
management as of the local radio equipment as of the radio link. For the transmission of the management information, the SRA L provides the following elements: F interface, for the local connection of LCT R channel, for the transmission via radio between SRA L of different stations V-bus, for the transmission on bus (RS-485) between SRA L of the same station D channel, for the transport of the supervision information on a 2 Mbit/s tributary stream in such a way to allow the cross over of different transmission systems (e.g. fiber optic systems) Q channel, for the communication towards other TMN supervision systems (EM-OS, Access Integrator). For the transmission of the management information, the SRAL XD is provided with: F interface, for the local connection to LCT 10 Mbit/s Ethernet Q interface (Q interface) for the connection to the supervision system 10/100 Mbit/s Ethernet V interface (V interface) for the connection among the Controllers of the equipments of the same station and for the connection of the equipment Controller to a supevision system R channel, for the transmission via radio among SRAL XDs of different stations external D channels for the point-to-point connection to another device belonging to a different network/subnetwrok embedded D channels, for the transport of the supervision information on a 2 Mbit/s tributary stream to allow the passing through differnt transmission systems (e.g.: system in optical fiber) For the transmission of the management information, SRA Series 3 and SRA 4 provide the following elements: Ethernet interface, for the connection towards supervision systems, other radio equipment of the same radio station, other TMN supervision systems (EM-OS) F interface, for the local connection of LCT DCC channels, for the transmission via radio of the supervision information. On the SRA Series 3, SRA 4 and SRAL XD it is possible the connection to LCT also on Ethernet interface. OSI class radio equipment Equipment for the transmission of the management information via radio using the TNMP management application protocol implemented on the Qx protocol (OSI stack). The OSI class radio equipment are the following ones: SRT 1C SRA SPS E. In case of OSI class radio equipment, from LCT, it is possible to execute the management of the local radio equipment only. For the transmission of the management information, every OSI radio equipment provides the following elements:
2-5
Ethernet interface for the connection towards other supervision systems (NetViewer, EM-OS) and other OSI radio equipment of the same station F interface, for the local connection of LCT. The OSI radio equipment are equipped with DCC channels for the transmission via radio of the supervision information.
2.6 Characteristics of the TCP/IP Protocol

2.6.1
2.6.1.1
Address format for TCP/IP Protocol

Host and router
Network devices for the TCP/IP protocol are subdivided into: host: device with an application that responds to the TCP/IP protocol router (or gateway): device that manages routing information for various network lines.
2.6.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 to which the host is connected. 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.1): 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. Class B A Class B address has the following structure: the first two bits of the first byte = 10 the remaining six bits of the first byte plus the second byte (14 bits) identify the network the last two bytes (16 bits) identify the sub-network+host field. Class B addresses are most widely used because they allow a compromise between the network number and the sub-network and host number. Class C A Class C address has the following structure: the first three bits of the first byte = 110
2-6
the remaining five bits of the first byte plus the second and the bytes (21 bits) identify the network the last byte (8 bits) identify the sub-network+host field. Class C addresses are used only for networks with a limited number of sub-networks and hosts. There are also Class D and Class E addresses but their use is not provided for in LCT software. If it is present a radio link, the host field identifies the radio equipment and the sub-network field identifies the station. The user can assign to the network field every value. For the radio link, it is advisable to use B class addresses. The limit values of every field with all 0 and all 1 must not be used because they are reserved address values (par. 2.6.1.5). To reduce at the minimum value the possibility to have wrong operating TCP/IP configurations or configurations that could potentially be wrong operating, the LCT software foresees for the IP addresses some unassignable values (par. 2.7). Fig. 2.1 Structure of IP addresses
2.6.1.3
Decimal notation of the IP address

The IP addresses are usually written in decimal notation, which is to say they are written by means of the corresponding decimal value of each of the four bytes composing the IP address. For example, the following Class B IP address: 10000000 00000011 00001001 00000001 is written as: 128.3.9.1 and is translated into the network ID 128.3 and into the host ID (sub-network+host) 9.1. In decimal notation, the value of the first byte allows the immediate identification of the Class to which the address belongs: Class A address: initial value in the range 0 to 127
2-7
Class B address: initial value in the range 128 to 191 Class C address: initial value in the range 192 to 223.
Tab. 2.1 summarizes the main characteristics of several IP address classes. Tab. 2.1 Characteristics of IP addresses Value of the Address Space of the First Byte 0 - 127 128 - 191 192 - 223 Max. Number of Networks* 126 16.384 2.097.152 Max. Number of Hosts* 16.777.124 65.534 254 IP Address Space net.host.host.host net.net.host.host net.net.net.host
Class A B C
* Some address values are reserved and cannot be used (par. 2.6.1.5).
2.6.1.4
Net-Mask
The final field of the IP address consists of two sub-fields: the first one identifies the sub-network while the second one identifies the host. In TCP/IP networks a mask, known as Net-Mask has to be specified for each address. This mask is always composed of four bytes and it is subdivided into two parts (Net-Part and Host-Part). It serves to indicate the configuration of the different fields of the IP address and specifically the configuration of the sub-network+host field. The number of bits for each sub-field is variable and can be different from address to address. However the sum of the two sub-fields must be equal to the sub-network+host field. The Net-Mask allows correct understanding of the IP addresses because it shows how many bits are used to address the sub-network and how many to address the host. The method used to determine the Net-Mask consists of starting from the IP address and encoding, into the Net-Part, the bits relating to the network with all "1" and, into the Host-Part, the bits relating to the sub-network with all "1" and the bits relating to the host with all "0". Cross combinations of the bits relating to the sub-network and to the host (Host-Part) are possible, but their use is not advisable owing to the subsequent difficulty in numbering and reading. Fig. 2.2 shows some Net-Mask examples for the Class B address: 255.255.255.0 255.255.252.0 8 bits to address the sub-network, 8 bits to address the host 6 bits to address the sub-network, 10 bits to address the host
255.255.255.192 10 bits to address the sub-network, 6 bits to address the host.
In the Net-Mask, the bytes relating to the network (Net-Part) are always equal to 255.
2-8
Fig. 2.2
Example of Net-Mask for Class B IP address

Net-Mask = 255.255.255.0 NET-PART Net-Mask IP Address HOST-PART
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 0 X X X X X X X X X X X X X X Y Y Y Y Y Y Y Y Z Z Z Z Z Z Z Z NETWORK ID SUB-NETWORK ID HOST ID
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 0 X X X X X X X X X X X X X X Y Y Y Y Y Y Z Z Z Z Z Z Z Z Z Z NETWORK ID SUB-NETWORK ID HOST ID
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 1 0 X X X X X X X X X X X X X X Y Y Y Y Y Y Y Y Y Y Z Z Z Z Z Z NETWORK ID SUB-NETWORK ID HOST ID
2.6.1.5
Reserved address values

The IP address can be coded by filling fields with a complete set of "1". Such a coding operation defines a multiple transmission signal (broadcast): all "1" in the network field: transmission to all networks all "1" in the host+sub-network field: transmission to all hosts of the network all "1" in the host field: transmission to all hosts of the sub-network.
For example, the IP address = 128.2.255.255 identifies all hosts in the 128.2 network. The IP address can also be encoded filling the various fields with a complete series of "0", identifying in such a way the address as "this network", "this sub-network". For example: the IP address = 128.2.0.0 identifies the current network, namely 128.2 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 such a case, the host will transmit an address with only "0" in the network field and the other hosts will acquire this address as the indication of the subject network.
2-9
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.2 shows which addresses are reserved and which addresses are available if the TCP/IP network has been inserted into an Internet context. Tab. 2.2 Reserved and available Internet addresses Class A Address/Range 0.0.0.0 1.0.0.0 - 126.0.0.0 127.0.0.0 128.0.0.0 128.1.0.0 - 191.254.0.0 191.255.0.0 192.0.0.0 192.0.1.0 - 223.255.254.0 223.255.255.0 224.0.0.0 - 255.255.255.254 255.255.255.255 Status Reserved Available Reserved Reserved Available Reserved Reserved Available Reserved Reserved Broadcast
D, E
2.6.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.3. Fig. 2.4 shows the TCP/IP protocol stack used in the connection between LCT and NEs.
2-10
Fig. 2.3
TCP/IP protocol stack
Key: Name Telnet FTP (File Transfer Protocol) BootP (Bootstrap Protocol) TFTP (Trivial File Transfer Protocol) SNMP (Simple Network Man. Prot.) UDP (User Datagram Protocol) TCP (Transmission Control Protocol) IP (Internet Protocol) ICMP (Internet Control Message Protocol) RIP (Routing Information Protocol) ARP (Address Resolution Protocol) MAC (Media Access Control) LLC (Logical Link Control) PPP (Point to Point Protocol) IPCP (Internet Protocol Conf. Prot.) LCP (Link Connection Protocol) SLIP (Simple Link Internet Protocol)
Standard RFC 854 RFC 959 RFC 951 RFC 783 RFC 1157 RFC 768 RFC 793 RFC 791 RFC 792 RFC 1058 RFC 826 RFC 1042 RFC 1042 RFC 1171 RFC 1171 RFC 1171 RFC 1055
Description Application for network terminal emulation Application for file transfer Application for bootstrap of diskless hosts Single file transfer Application for network management Transport layer at datagram (not reliable) Connection oriented transport layer (reliable) Network layer (for routing) Protocol for routing table distribution IP/Ethernet addresses conversion protocol
Link connection oriented protocol IP remote configuration protocol Link not connection protocol
2-11
Fig. 2.4
TCP/IP protocol stack for LCT
Key: Name Standard Description Telnet RFC 854 Application for network terminal emulation FTP (File Transfer Protocol) RFC 959 Application for file transfer UDP (User Datagram Protocol) RFC 768 Transport layer at datagram (not reliable) TCP (Tranmission Control Protocol) RFC 793 Connection oriented transport layer (reliable) IP (Internet Protocol) RFC 791 Network layer (for routing) ICMP (Internal Control Message Protocol) RFC 792 RIP (Routing Information Protocol) RFC 1058 Protocol for routing table distribution ARP (Address Resolution Protocol) RFC 826 IP/Ethernet addresses conversion protocol PPP (Point to Point Protocol) RFC 1171 Link connection oriented protocol IPCP (Internet Protocol Conf. Prot.) RFC 1171 IP remote configuration protocol LCP (Link Connection Protocol) RFC 1171 SLIP (Simple Link Internet Protocol) RFC 1055 Link not connection protocol TNMP Trivial Network Management Protocol (proprietaty application protocol)
2-12
2.6.3
TCP/IP protocol of the service PC

For the connection to the NEs, the service PC on which it is installed LCT must be equipped with a TCP/IP protocol. It is used the TCP/IP protocol provided by the operating system (Windows NT/2000/XP) on serial RS-232C (PPP protocol) interface. The connection on serial interface needs for the installation of the direct connection mode with a specific driver provided on CD-ROM. The TCP/IP protocol provides the operator with some utilities for the control of the connection between LCT and NE (par. 2.6.5). Utilities with graphic mode, concerning TCP/IP protocol, are provided also by SuperTCP program. If the PC is used for the download of the unit embedded software (Controller and/or Q-Adapter) by means of FTP, it is necessary to install the SuperTCP program. For more detailed information about the installation and the configuration of the TCP/IP protocol please refer to Cap. 3 (Software Installation).
2.6.4
Name solving
LCT identifies the NEs with an univocal IP address. It is possible to use some names instead of the numerical IP addresses. LCT is able to execute autonomously the resolution of the host_names relevant to all the NEs, present into the map, for wich it has been set as the name as the IP address. On the contrary, the use into the map of the name only to identify a NE is possible only if the operating system is able to execute the resolution of the host_names (for instance through a DNS Server or through the system hosts file). In case of name solving through host table, the corrispondence between the name and the IP numeric address must be specified, for each radio equipment, in the hosts file; this file is contained in the %SystemRoot%/System32/Drivers/Etc folder. To open and edit the "hosts" file use an editor program. The file has to be saved in ASCII format without any extensions in such a way that Windows can detect it as a system file. The preset and not modifiable IP address for every local radio equipment is 192.168.255.3. For the creation/change of the host table in Windows NT/2000/XP, the operator must have the administrator access rights for Windows NT/2000/XP.
2-13
2.6.5
Auxiliary utilities
The operator can use the software utilities of the TCP/IP protocol to check the features of the connection between LCT and NE. The TCP/IP protocol of the Windows NT/2000/XP operating system makes the following utilities available as DOS commands: Ping It is possible to send a ping command towards a host in order to verify if the TCP/IP stack of the addressed host is visible and to measure the transmission time in the go and return direction. NetStat This is a typical Windows utility which allows to call statistics all active TCP/IP connections. TraceRT It is possible to send a TraceRT command towards a host in order to verify if the path to reach the addressed host is the intended path and is free from failures and/or conflicts. Route It allows managing the local TCP/IP routing table (route). In particular, the "PRINT" option allows the displaying of the entire routing table. 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 Windows. Such a utility allows opening a virtual terminal in the TCP/IP stack of the specified host. If the operator wants to work with graphical mode utilities instead of DOS command modes, the utilities of the SuperTCP program can also be installed. The SuperTCP program, then, makes available the FTP Client and FTP Server utilities. Such utilities allow the download procedure from remote of the unit embedded software.
2-14
2.7 Software Architecture

The architecture of the LCT software (Fig. 2.5) is a modular type one and it provides the following elements: Local Craft Terminal application program. It implements the LCT engine and the graphical interface (GUI) through which the operator manages the radio equipment. NetBuilder application program It is a graphical tool that allows creating/changing the link map and/or the local one that constitutes the graphical interface for the connection from LCT to the radio equipment. 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 has been installed. The plugs-in are additional parts of the engine that can be installed at every time also later than the engine installation.
Fig. 2.5
LCT software architecture
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 the compatibility 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-15
2.8 Local Equipment Management

2.8.1 LCT - local equipment connection
The connection brtween service PC (LCT) and local equipment is realized through serial RS-232C interface (F interface). It is necessary to use a proper pin-to-pin not-modem cable. Every radio equipment provides the preset IP address 192.168.255.3 (B Class) for the connection towards the service PC (LCT). Fig. 2.6 shows the connection diagram between service PC and local equipment. Fig. 2.6 Connection between service PC and local radio equipment
LOCAL EQUIPMENT
F INTERFACE PIN-TO-PIN NOT MODEM CABLE
SERVICE PC (LCT)
2.8.2
Local map
The local map constitutes the necessary graphical interface for connection from LCT to the local equipment. To create the map, it is necessary to use the proper Net Builder program, which allows: to import a drawing of the map in ".BMP" format, if we want to have a graphical representation of the radio equipment as background. to locate the equipment icons in pre-arranged positions. to assign the relevant name/IP address to the equipment; during definition of the host table. to save the created map in ".MAP" file format with the desired name.
LCT is equipped with the standard map for the connection with the local equipment (LocalNE.map) and with the other following three maps for the different connection modes to the local equipment: LneTnmpE.map: configuration for the connection to the local equipment with extended TNMP protocol LneTnmp.map: configuration for the connection to the local equipment with base TNMP protocol LneAuto.map: configuration for the connection to the local equipment with protocol automatic selection (mode to be used when it is not know the protocol supported by the equipment).
2-16
By default, the LocalNE.map standard map is configured for the use of the extended TNMP protocol. It is advisable to apply to the standard map the configuration of the map relevant to the most frequently used connection mode. If the user wants creating a customized local map, the numeric IP address to be assigned is 192.168.255.3 that constitutes the preset and unchangeable address for the local connection of every equipment. In addition, the NetBuilder program allows to modify the pre-existing map. To realise the background drawing, one of the graphical application programs in Windows must be used which supports the graphical ".BMP" format (e.g.: Paintbrush). The background drawing can be of any type (a geographic map pointing out the location of the various stations, for example). For help on how to use the NetBuilder program please refer to Cap. 7 (Operating Guide of NetBuilder).
2.8.3
Testing of the local connection

After having configured the dial-up connection between LCT and local equipment, the operator has to execute its testing, by means of the software utilities of the TCP/IP protocol. Such a testing 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 service PC, the TCP/IP protocol manages as the serial interface (radio equipment) as the Ethernet interface (for instance: LAN).
For the using modes of the software utilities, refer to the manual of the operating system. The main troubles that can be detected during the connection between service PC and radio equipment on serial RS-232C interface are the following ones: F interface: impossibility to contract with the equipment through the TCP/IP protocol Check the correct configuration of the service PC. Check the PC - equipment serial connection cable. Check that the equipment is turned on and that it has finished the reset operation. F interface: after the 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 restart Windows and the Local Craft Terminal program.
2-17
2.9 Radio Link Management

2.9.1 LCT - radio link connection
In case of radio equipment with IP class (SRA L, SRA Series 3), it is possible to manage from LCT all the radio equipment of a radio link. Usually, a radio link is composed by two NEs of two front-end stations: local terminal and remote terminal (Fig. 2.7). The radio link can be composed by three NEs if between the two local and remote terminals it is present a repeater (Fig. 2.8). In case of SRA L and SRAL XD it is possible to realize a radio link with three NEs, because it is foreseen the following System Type: Repeater with Add/Drop of the tributaries. In case of SRA L, it is possible to realize mixed links, that is with different types of SRA L (for instance: links with one fully outdoor SRA L and one 8x2 Mbit/s SRA L), with the condition that they are compatible at RF level. In case of SRA L and SRAL XD, it is possible to realize mixed links, that is with one SRA L terminal and one SRAL XD terminal, with the condition that they are compatible at RF level The connection between service PC (LCT) and local radio equipment, that acts as gateway, is realized through serial RS-232C interface (F interface). It is necessary to use a proper pin-to-pin not-modem cable. In every point of the radio link, it is possible to insert a router of third parties. The connection of a router can be executed using the F interface.
2-18
Fig. 2.7
Radio link structure
Station 1 NE Terminal A Radio Link

F INT. PIN-TO-PIN NOT M ODEM CABLE COM1/COM2
Station 2 NE Terminal B
Service PC (LCT)
Fig. 2.8 Radio link structure with repeater
Station 1 NE Terminal A Radio Link

F INT. PIN-TO-PIN NOT MODEM CABLE COM1/COM2
Station 2 NE Repeater Radio Link
Station 3 NE Terminal B
Service PC (LCT)
2-19
2.9.2
2.9.2.1
Routing functions of the NEs

Routing functions of the SRA Series 3
Every SRA Series 3 is a device with dual function: the host and the router. This feature is possible because the SRA L is able to identify the destination (the SRA L itself, another SRA Series 3, a router, a PC) on the basis of the IP address and consequently to route the message towards the proper path. As a router, the SRA Series 3 is capable of branching the signal over different routes: toward its own circuits; in this case the SRA Series 3 behaves a host toward a local PC or router, through serial line (F interface) toward a LAN, through Ethernet toward a SRA Series 3 of another station, through radio (DCCM and DCCR channels).
Each SRA Series 3 has a preconfigured local IP address (the same for all SRA Series 3 systems) which allows a local connection through which the operator may assign the IP address. Fig. 2.9 shows the routing architecture diagram of the SRA Series 3. Fig. 2.9 Routing architecture of the SRA Series 3
LAN - Ethernet
To LAN Channels integrated Into the SDH frame DCCM Channel DCCR Channel
F Interface Serial Line
To Local PC
To SRA Series 3 (Front-End Terminal) To Local IP Address

Equipment Configuration Control
2-20
2.9.2.2
Routing functions of the SRA L

Every SRA L is a device with dual function: the host and the router. This feature is possible because the SRA L is able to identify the destination (the SRA L itself, another SRA L, a router, a PC) on the basis of the IP address and consequently to route the message towards the proper path. As a router, the SRA L is capable of branching the signal over different routes: toward its own circuits; in this case the SRA L behaves a host toward a local PC or router, through serial line (F interface) toward a SRA L of the same station, through LAN (V-bus) toward a SRA L of another station, through radio (R and D channels).
SRA Ls of the same station can be interconnected by means of a LAN. The LAN is physically implemented by means a two-wire V-bus (half-duplex) with a daisy-chain structure. Up to a maximum of 32 SRA Ls can be interconnect through a LAN . Each SRA L has a preconfigured local IP address (the same for all systems) which allows a local connection through which the operator may assign the IP address. Fig. 2.10 shows an example for the routing strategy in a SRA L link. Fig. 2.11 shows the routing architecture diagram of the SRA L. Fig. 2.10 Example of routing strategy in a SRA L link
Station 1
Station 2
Station 3
V-Bus
Station 4
Link SRA L IP Address = 138.132.2.0 (Class B) Net-Mask = 255.255.255.0
2-21
Fig. 2.11
Routing architecture of the SRA L
V-bus (LAN)
To V-bus 138.133.2.0 F Interface Serial Line To 138.132.2.3 Local PC To Local IP Address 138.132.2.2 Equipment Configuration Control
To SRA L 2 of the Station 3
Channels Integrated into the Radio Frame: R1 Channel D1 Channel
To SRA L 2 of the Station 1
Channels Integrated into the Radio Frame: R2 Channel D2 Channel
Host + Router (IP Address = 138.132.2.2)
For the IP addresses refer to Fig. 2.10
2-22
2.9.3
Routing tables
In a TCP/IP network, 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: these tables are defined by the network administrator and are fixed in advance. In case of network expansion or change they have to be updated. Dynamic routing tables: these tables are generated by the various network elements with router function on the basis of to 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 as the SRA L as the SRA Series 3 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. The RIP protocol version 1 requires the same Net-Mask in the entire the radio link. Static routing tables are required if routers not supporting the RIP protocol are used inside the radio link. A specific routing table can be created on a NE to exit from the radio link, which via the RIP protocol is recognized by other NEs as the default outlet of the radio link.
2.9.4
Host table
The creation and use of a host table on the service PC, allows using the names instead of the numeric IP addresses to identify the NEs. In the host table, the correspondence between names and numeric IP addresses must be specified for all NEs in the link. The host table can be dynamically defined by means of DNS, if a device with this function is connected to the radio link. The procedure for creation of the host table is described in the Cap. 3 (Software Installation).
2-23
2.9.5
2.9.5.1
Connection to TMN supervision system

Connection to TMN supervision system of a SRA Series 3 link
By means of DualQ-Adapter (Fig. 2.12), it is possible to realize the connection between a SRA Series 3 link and a TMN supervision system (EM-OS). The DualQ-Adapter executes the translation between TCP/IP protocol (SRA Series 3 link) and Qx/Q3 standard protocol (TMN supervision system). For the connection to the supervision system, it is used the Ethernet interface (ISO 8802.3).
Fig. 2.12
Configurations of SRA Series 3 - TMN connection
Station 1
Station 2
DualQ-Adapter
SRA Series 3
SRA Series 3
a) Direct connection
Station 1
Station 2
DualQ-Adapter
SRA Series 3
SRA Series 3
OSI NETWORK
b) Connection through OSI network
2-24
2.9.5.2
Connection to TMN supervision system of a SRA L link

The connection feature between SRA L link and TMN supervision system (EM-OS) is realised by the Q-Adapter unit (Fig. 2.13). Such a unit provides the translation between TCP/IP protocol (SRA L link) and standard Qx/Q3 protocol (TMN supervision system). The Ethernet (ISO 8802.3) interface is used, to connect Q-Adapter unit to EM-OS . As an alternative, the Q-Adapter unit allows connection of the SRA L link to the Access Integrator supervision system or other QD2 managers by means of the QD2 interface. The Q-Adapter unit is connected to the controller of the same SRA L and to the controllers of other SRA Ls in the station through the V-bus (Fig. 2.14). Fully outdoor SRA L is not equipped with the Q-Adapter unit. However, a SRA L fully outdoor can be supervisioned by a TMN system, using the Q-Adapter unit of another SRA L for the connection (SRA L 8x2 Mbit/s or SRA L 16x2 Mbit/s). The following cases are possible: mixed link, composed by a SRA L fully outdoor and by a SRA L 8x2 Mbit/s, the last one is equipped with the Q-Adapter unit connection between a SRA L fully outdoor to another SRA L in the station, via V-bus; the second SRA L is equipped with the Q-Adapter unit.
Fig. 2.15 shows the stack of the standard Qx/Q3 protocol. Fig. 2.13 Configurations of SRA L - TMN connection
Station 1
Station 2
a) Direct connection
Station 1
Station 2
NETWORK OSI
b) Connection through OSI network

The SRA L link can therefore be connected to the supervision systems EM-OS or Access Integrator.
2-25
Fig. 2.14
Local link between the Q-Adapter unit and the Controller units of the station SRA Ls
STATION
Controller
Controller
Controller
Fig. 2.15 Application Layer (7) Presentation Layer (6) Section Layer (5) Transport Layer (4) Network Layer (3) Data Connection Layer (2) Phisical Layer (1)
Stack of standard Qx/Q3 protocol ACSE (X.227) CMISE (X.711, X.712) X.226, ISO 8823 (X.216, ISO 8822) X.225, ISO 8327 (X.215, ISO 8326) X.224, ISO 8073 8073/AD2 (X.214, ISO 8072 classe 4) ISO 8473 (type without connection) ISO 8802.3 CSMA/CD ISO 8802.2 LLC IEEE 802.3 thin Ethernet 10BASE2 line code: Manchester bit-rate: 10 Mbit/s QETH ROSE (X.229)
Channel
2-26
2.9.6
Planning and configuration of a radio link

The TCP/IP parameter validity conditions (par. 2.10) of the LCT software have to be considered when the configuration and planning of the radio link has to be carried out.
2.9.6.1
Planning of IP addresses
For the assignment of IP addresses for the radio link, the link administrator has to proceed as follows. 1. Choose the IP address type to be used for the radio link: Class A Class B Class C.
If Class A is selected, please note that the last 2 bytes of the IP address of all the SRA L systems on a single V-bus must be different, because they are used as MAC addresses on the same bus. For the radio link, it is advisable to use Class B addresses. 2. Assign the network ID of the IP address. During the assignment of the network ID, pay attention to the current radio link type. stand-alone type radio link: it is possible to use any network ID Intranet type radio link: it is necessary to use a network ID that has not been yet assigned, otherwise, there will be conflicts and routing failures between the interconnected networks Internet type radio link: it is necessary to request the IP address assignment from the authorised entity (IANA). 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 the sub-network addressing (station) and hor many for the host addressing (NE or service PC). Identify every station with its relevant IP address, assigning the sub-network ID of the IP addresses. 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. In case of SRA L, every station LAN can contain up to a maximum of 32 SRA L and hence can seize up to 64 different IP addresses (32 IP addresses for the SRA L + 32 IP addresses for the corresponding F interface). In case of SRA L with Q-Adapter unit, it is necessary to assign an IP address also to the V interface of the unit itself.
3.
4. 5.
2-27
The IP addresses of the NEs have to be assigned in steps of two because for every NE an IP address corresponding to the F interface (service PC or router) is automatically added. Such an address is equal to the NE IP address plus one; e.g. in case of Net-Mask = 255.255.255.0: NE IP address = 150.166.32.2 F interface IP address = 150.166.32.3. It is advisable to follow a systematic rule such as using only even IP addresses for the NEs. 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.
An incorrect setting in a static table can cause a wrong routing of management information into the link and hence may endanger operation of the whole radio link. 7. Define, if desired, the host table in such a manner as 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 Cap. 3 (Software Installation).
2.9.6.2
Creation of the link map

The link map constitutes the necessary graphical interface for connection from LCT to the NEs of the link. To create the maps, it is necessary to use the proper NetBuilder program. Such a program has the following features: if it is desired to have a graphical link layout as background, it is possible to import a drawing of the radio link in ".BMP" format positioning of NE icons in pre-arranged positions assignation of the relevant name/IP address to each NE. saving the created map in ".MAP" file format with the desired name.
In addition, the NetBuilder program allows modification of a pre-existing map. To realise the radio link drawing one of the graphical application programs in Windows must be used which supports the graphical ".BMP" format (e.g.: Paintbrush). The radio link drawing can be of any type, for example: a geographic map pointing out location of the various stations a block-diagram pointing out all link interconnections.
When creating the drawing please be careful to leave enough space in the various NE positions to allow for future positioning of the respective icons in order to end up with a clear and neat map. For help on how to use the NetBuilder program please refer to the Cap. 7 (Operating Guide of NetBuilder).
2-28
2.9.6.3
Configuration of 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.10). When the setting of NE link parameters is performed for the first time, it is necessary to isolate the NE itself be from the rest of the link. Otherwise conflicts may occur in the link. The following link parameters can be set through software: Equipment IP address and the corresponding 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. F interface parameters: Communication protocol: PPP or SLIP. Preferably, always set the PPP protocol. The SLIP protocol should be used only if the PC hardware does not support the PPP protocol. The PPP protocol allows the service PC to detect the IP address assigned to the F interface automatically. On the contrary, if the SLIP protocol is used, it is necessary to set the IP address manually on the service PC before connecting it to the radio equipment. Baud-rate: 9600 bps or 19200 bps. Preferably, always set 19200 bps; 9600 bps should be used only if the PC hardware does not support a baud-rate of 19200 bps.
For the connection to SRA 4, SRAL XD or MicroHop, it is necessary to set a baud-rate equal to 38400 bps. Static routing table, if necessary. It is possible to set up to a maximum of three different routings for each NE. For every routing it is necessary to specify the following data: the interface for which the routing is defined. the network IP address and destination gateway address.
In case of SRA L, the setting of the gateway IP address is only necessary in case of routing on a V-bus, because on the V-bus it is necessary to specify the SRA L of destination while this is optional in other cases. In a radio link only a single default routing can be set (multiple transmission to all networks). To assign the default routing, set the IP address = 0.0.0.0. For help on how to use the Local Craft Terminal program refer to the Cap. 6 (Operating Guide of Local Craft Terminal).
2-29
2.9.6.4
Testing of the radio link

After execution of the planning and configuration procedure of the radio link, the link administrator has to carry out, by means of the software utilities of the TCP/IP protocol, its testing to check that: 1. 2. 3. There are no conflicts on the link. All NEs can be reached and answer the connection request. All possible routes of the link are free of routing errors.
For more detailed information about the use of the software utilities refer to the Windows NT/2000/XP handbooks.
2.9.6.5
Examples of radio link

Fig. 2.16, Fig. 2.17 and Fig. 2.18 show three examples of radio link: Stand-alone type link (Fig. 2.16). This is a link without branching towards other link. Intranet type link (Fig. 2.17). This is a link with branching towards other networks. Internet type link (Fig. 2.18). This is a link connected directly to the Internet network.
The example of Fig. 2.16 shows a radio link where a link administrator uses a Class B IP address with Net-Mask = 255.255.255.0, i.e. with the following structure:
1 0 X X X X X X X X X X X X X X Y YYY Y Y Y Y Z Z Z Z Z Z Z Z NETWORK ID SUB-NETWORK ID HOST ID
The example of Fig. 2.17 and Fig. 2.18 shows a SRA L where a link administrator uses a Class B IP address with Net-Mask = 255.255.255.240, i.e. with the following structure:
1 0 X X X X X X X X X X X X X X Y YYY Y Y Y Y Y Y Y Y Z Z Z Z NETWORK ID SUB-NETWORK ID HOST ID
The main characteristics pointed out by the three examples are the following: Use of a router for the connection to another network (Fig. 2.17) or to the Internet network (Fig. 2.18). The router can be installed in the same site of the radio equipment to which it is connected to or even in another site (for example via modem). Use of even IP addresses in steps of two for the radio equipment. The F interface IP address of the radio equipment connected to the PC is equal to the address of the radio equipment itself plus one.
2-30
Fig. 2.16
Example of a stand-alone radio link (SRA L)
SERVICE PC (LCT)
Fig. 2.17
Example of a Intranet type radio link (SRA L)
SERVICE PC (LCT)
2-31
Fig. 2.18
Example of a Internet radio link (SRA L)
SERVICE PC (LCT)
2-32
2.9.6.6
Main problems occurring in the radio link management

F interface: no possibility to negotiate the TCP/IP protocol with the NE. Verify the correct configuration of the service PC. In case the serial interface is used, check the interconnection cable PC - NE. Check whether the NE is on and has completed the reset operation. F interface: after the loading of the map, the NEs are disconnected. Close the Local Craft Terminal program and check whether the TCP/IP protocol is correctly operating. F interface: the operator cannot remember the IP address of the NE. Establish a connection with the NE using the default address (local map) and check the set IP address. As an alternative, execute Ping from DOS to check whether the protocol is operating. The NE will reply signalling its specific IP address. In this case, it will be the default address. F interface: the supervision is lost when changing the NE IP address. Every time an IP address or the system type of the NE is changed, a new start-up of the working session is required (application program and protocol). V-bus: after having executed the connection, it is not possible to "see" the SRA L installed downstream of the bus. Check whether all the hosts on the V-bus belong to the same sub-network. Check whether the V-bus is has the correct terminations. Address planning: using Class A addresses, it is not possible to monitor all the NEs. Check whether for the Class A addresses a Net-Mask is used which is at least equal to 16 (255.255.0.0). "hosts" file: after having updated the "hosts" file, on the map the NEs remain disconnected. The "hosts" file is read by the operating system only during the opening. To activate every possible change on such a file, it is necessary to start Windows and the Local Craft Terminal application again.
2-33
2.10 Validity Conditions of TCP/IP Parameters

2.10.1 General
The TCP/IP 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 (F interface).
To minimize the possible presence fo malfunctioning TCP/IP configurations, the LCT software provides some values that can not be assigned for each some values that can not be assigned for each TCP/IP parameter. The detection for each parameters of the validity conditions and of the not validity ones is based upon the RFC standards and upon the NE particular structure. 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, considered as valid if they are singularly taken into account, can define, if they are combined, some not valid sub-network or host values. The setting of a not valid value is signalled by the software on the video through a negative answer like "out of range". Then it is provided a reset mode of the TCP/IP parameters.
2.10.2
2.10.2.1
Validity conditions for IP addresses and Net-Mask

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.10.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 such IP addresses are reserved ones (e.g. the IP addresses with all "1" are reserved for broadcast). For each Class, it is not valid the IP address having the host field such as to assign to the PC and IP address equal to the broadcast of that network.
Into the radio NE, the IP address of the PC is automatically assigned increasing of 1 the IP address of the radio NE itself.
2-34
Here below there are the validity ranges for the IP addresses with Class A, B and C. Class A
Class A identification bit
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 NETWORK ID SUB-NETWORK+HOST ID
Addressing range: Valid IP address: Valid values:
from 0.0.0.0 up to 127.255.255.255 from 1.0.0.1 up to 126.255.255.253
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 PC of an IP address equal to the broadcast for that network (X.255.255.255).
Class B
Class B identification bit
1 0XXXXXXXXXXXXXXYYYYYYYYYYYYYYYY
NETWORK ID SUB-NETWORK+HOST ID
form 128.0.0.0 up to 191.255.255.255 from 128.1.0.1 up to 191.255.255.253
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" value 255.255: not valid because it is a field with all "1" (reserved for broadcast) value 255.254: not valid because it causes the assignment to the PC of an IP address equal to the broadcast for that network (X.X.255.255).
2-35
Class C
Class C identification bit
1 1 0XXXXXXXXXXXXXXXXXXXXXYYYYYYYY
NETWORK ID SUB-NETWORK+HOST ID
from 192.0.0.0 up to 223.255.255.255 from 192.0.1.1 up to 223.255.255.253
Network field (first three bytes): from 192.0.1 up to 223.255.254 value 192.0.0: not valid because it is a field with all "0" value 223.255.255: not valid because it is a field with all "1" Sub-network + host field (last byte): from 1 up to 253 value 0: not valid because it is a field with all "0" value 255: not valid because it is a field with all "1" (reserved for broadcast) value 254: not valid because it causes the assignment to the PC of an IP address equal to the broadcast for that network (X.X.X.255).
2.10.2.2
Net-Mask
For each Class, only the Net-Mask having all "1" into the Net-Part are valid: Class A: the Net-Mask different from 255.Y.Y.Y are not valid 1 1 1 1 1 1 1 1YYYYYYYYYYYYYYYYYYYYYYYY
Net-Part
Class B: the Net-Mask different from 255.255.Y.Y are not valid 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1YYYYYYYYYYYYYYYY
Net-Part
Class C: the Net-Mask different from 255.255.255.Y are not valid 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1YYYYYYYY
Net-Part
For each Class, only the Net-Mask having contiguous "1" are valid. Examples of not valid Net-Masks having not contiguous "1":
Class A: 255.239.0.0
1 1 1 1 1 1 1 1 1 1 1 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Not contiguity Class B: 255.255.251.0
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1 0 0 0 0 0 0 0 0
Not contiguity
2-36
Class C: 255.255.255.188
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1 1 1 0 0
Not contiguity
For each class, only the Net-Masks, assigning two bits for the sub-network field and for the host one, are valid. Not valid Net-Mask with only one bit for the sub-network field:
Class A: 255.128.0.0
1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Net-Part Class B: 255.255.128.0 Host-Part
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Net-Part Class C: 255.255.255.128 Host-Part
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0
Net-Part Host-Part
Not valid Net-Mask for each class with only one bit for the host field.
Class A, B, C: 255.255.255.254
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0
2-37
2.10.2.3
IP address - Net-Mask combinations

For each Class, the IP address and Net-Mask combinations causing one of the following situations in the IP address are not valid: all "0" in the sub-network field all "0" in the host field all "1" in the host field (broadcast for that network) host field such as to assign to PC address equal to the broadcast for that sub-network.
Here below there are some examples of not valid combinations for the Class A. Combination of IP address = 97.11.48.159 and Net-Mask = 255.255.255.224
IP address = 97.11.48.159 Class A identification bit
0 1 1 0 0 0 0 1 0 0 0 0 1 0 1 1 0 0 11 0 0 0 0 1 0 0 1 1 1 1 1
NETW. ID Net-Mask = 255.255.255.224 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 Net-Part Host-Part SUB-NETWORK ID HOST ID
Applying che mask, it is obtained the host field with all "1" (broadcast for that sub-network). Combination of IP address = 1.0.0.1 and Net-Mask = 255.255.0.0
0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 1
NETW. ID SUB-NETWORK ID HOST ID
Net-Mask = 255.255.0.0
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0
Net-Part Host-Part
Applying the mask, it is obtained a sub-network field with all "0".
2-38
Combination of IP address = 1.0.0.4 and Net-Mask = 255.255.255.252

0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 1 0 0
NETW. ID Net-Mask = 255.255.255.252 SUB-NETWORK ID HOST ID
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 1 1 1 0 0
Net-Part Host-Part
Applying the mask, it is obtained a host field with all "0". Combination of IP address IP = 1.0.128.62 and Net-Mask = 255.255.255.192
0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 00 0 0 0 0 0 0 0 1 1 1 1 1 0
NETW. ID Net-Mask = 255.255.255.192 SUB-NETWORK ID HOST ID
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 0 0 0 0 0 0
Net-Part Host-Part
Applying the mask, it is obtained a host field (111110) such as to assign to PC an IP address equal to the broadcast for that sub-network (all "1" in the host field).
2-39
2.10.3
Validity conditions for parameters of the static routing table

Here below, there is the list of the validity conditions and of the not validity ones for each parameter of the static routing table. Remeber that it is not possible to execute permanent settings for the static routing table until the IP address of the radio NE has not been assigned. Routing interface The setting of the interface devoted to the routing definition does not create special troubles because it is possible to select only the values present into the list displayed on the video. IP address of the destination network Only the IP addresses belonging to Class A, B and C are valid For each Class, the IP addresses, having all "0" or all "1" into the network field, are not valid For each class, the IP addresses equal to the following ones are not valid: default IP address of the PC default IP address of the NE current IP address of the NE IP address of the local sub-network IP address for broadcast of the local sub-network. IP address of the gateway The same validity conditions of the NE IP addresses are valid (par. 2.10.2) For each Class, the current IP address of the NE is not valid.
2.10.4
Validity conditions for the F interface parameters (PC)

The setting of the F interface parameters (link and baud-rate protocol) does not create special troubles because it is possible to select only the values present into the list displayed on the video. Check that the used hardware (PC and, in case of remote connection, modem) supports the executed settings.
2.10.5
Reset of the TCP/IP parameters

It is possible to execute the reset of the TCP/IP parameters assigning the IP address = 0.0.0.0. This operation causes the deleting as of the IP address and of the relevant Net-Mask as the settings into the static routing table. On the contrary, the protocol and the baud-rate relevant to the F interface remains the current ones. Then the reset of the TCP/IP parameters is automatically executed when the following conditions are present: when it is changed the IP address of the NE when during the start-up phase, the system detects some IP address and Net-Mask values or combinations not valid.
2-40
3 - SOFTWARE INSTALLATION
3 SOFTWARE INSTALLATION
3.1 General
LCT software is provided on CD-ROM and it is comprised into the equipment delivery. The CD-ROM of the LCT delivery contains the following elements: LCT engine that comprises: the Local Craft Terminal application program the NetBuilder tool the SuperTCP program the software plug-in of the radio equipment the drivers for the connection via cable for Windows NT/2000/XP.
The LCT application program must not be installed on the same PC where it has already been installed the NetViewer application program. The NetViewer application program implements also the LCT function. It is always possible to obtain the installation floppy-disks of the SuperTCP program and the equipment plug-in from the relevant copy present on CD-ROM. To obtain the version on floppy-disk, it is necessary to assure the use of formatted floppy-disk, completely empty, without label and free from damages clusters and viruses. The image on CD of the floppy-disk #3 of the SuperTCP program is bigger than the maximum capacity of a floppy-disk. To obtain the floppy-disk #3 it is necessary to execute the following procedure: copy all the files from the <...\Tcp.ins\Floppy\Tcp-disk.03 folder, with the exception of the Tuttoc.hlp file, to the floppy-disk #3 copy the Tuttoc.hlp file on a reserve floppy-disk. During the SuperTCP program installation from floppy-disk at the request of the floppy-disk #3, it is necessary to execute the following procedure: insert the floppy-disk #3 when the error message is displayed, insert the reserve floppy-disk provided with the Tuttoc.hlp file when the new error message is displayed at the end of the loading procedure of the Tuttoc.hlp file, insert again the floppy-disk #3.
3-1
3.2 System Requirements

It is not advised the use of a PC with double boot. For the Notebooks and for the PCs with Power Management, such a function has not to be activated. Hardware requirements: CPU Pentium II 400 or higher 64 Mbyte RAM minimum 3 Gbyte Hard-disk minimum 1.4 Mbyte 3.5 floppy-disk drive VGA or higher video card CD-ROM drive (40x) RS-232C serial port Mouse Pin-to-pin not-modem serial cable (necessary in case of connection on F interface only) Ethernet network card (necessary in case of connection on Ethernet interface only Software requirements in Windows NT 4.0: TCP/IP communication protocol installed remote access service (RAS) installed (necessary in case of connection on F interface only); in case of Windows NT Server, we advise you to install the RRAS service instead of RAS service Software requirements in Windows 2000/XP: TCP/IP communication protocol installed
For software installation, it is necessary to use the CD-ROM of the current operating system (Windows NT/2000/XP).
3-2
3.3 Installation of the SuperTCP program

Super TCP program provides utilities relative to TCP/IP protocol It is necessary to install the SuperTCP program on the service PCs, if the operator wants to have at disposal the function for the download of the unit embedded software by means of FTP (function available for IP networks only) The SuperTCP installation is different from the LCT one. Only the utilities of the SuperTCP program are installed, because the software automatically detects the presence of the TCP/IP protocol. The SuperTCP program utilities allow to work under Windows NT/2000/XP in graphic mode. The installation procedure is the following one: During the SuperTCP installation procedure, all application programs must be closed (e.g.: antivirus). Start the setup procedure of the SuperTCP program (file: <CD_drive>:\Frontier\ Tcp.ins\Cd\Setup.exe). The Setup window is displayed (Fig. 3.1). Click on the option: Install your Frontier Product now to execute the installation. AThe Destination Directory window is displayed (Fig. 3.2). It allows to select the destination folder of the program files; by default the folder C:\Program Files\FrontierTech is selected. Click on OK to confirm the selection. If the selected folder is not present on the hard-disk, the warning window of Fig. 3.3 is displayed. Click on Yes to confirm. The system displays a window to advise to close all the actually open application programs (Fig. 3.4). Close all possible open applications and click on OK to continue. The User Identification window for the insertion of user data is displayed (Fig. 3.5). Insert the user name and the company name and click on OK to confirm the settings. The Package Authentication window is displayed (Fig. 3.6). Insert the serial number (Serial Number) and the password (Authentication Key) and click on OK. The system displays the installation starting up window (Fig. 3.7) of the SuperTCP program. Click on OK to start-up the installation. At the end of the installation phase the folder, Frontier Technologies is created and the system displays a warning window to advise to restart the PC (Fig. 3.8). Click on Yes to confirm the PC restart procedure.
When it is requested, it is advisable to execute always the PC restart. After restarting the PC into the Programs menu, it is present the Frontier Technologies folder (Fig. 3.9).
3-3
Fig. 3.1
Installation of SuperTCP program (1/9)
Fig. 3.2
Fig. 3.3
Fig. 3.4
Fig. 3.5
Fig. 3.6
3-4
Fig. 3.7
Fig. 3.8
3-5
Fig. 3.9
3-6
3.4 Installation of Local Craft Terminal

To execute a correct updating from a preceding version, it is possible to use the following two different modes: disinstall the already installed version before executing the installation of the new version; in this case, it is necessary to install again also the plug-in of the radio equipment (par. 3.5) install the new version into the same folder where it has been installed the preceding version; in this case, it is not necessary to install again the plug-in of the radio equipment. In case of LCT removal, it is possible that, at the end of the removal procedure, the removed components are still displayed under the Start menu of Windows. However, the system will remove such components from the Start menu of Windows at the next start-up procedure of the PC. The CD-ROM of the Local Craft Terminal software is an autorun type one. The LCT installation procedure is the following one: Run the LCT setup (file: <CD_drives>:\Setup.exe). If the system does not detect the presence on the PC of the SuperTCP program, it displays an interrogation window (Fig. 3.10). Click on Yes to continue the installation or click on No to exit and to stop the installation. If the system detects the presence of a previous version of LCT, it displays a query window (Fig. 3.11). Click on Yes to continue the installation or click on No to exit and to stop the installation. The window Welcome (Fig. 3.12) opens. Click on Next to continue the installation procedure. The window License Agreement opens (Fig. 3.13). Click on Yes to accept the licence conditions for using the software. The window Choose Destination Location is displayed (Fig. 3.14). It allows to select the destination directory of program files; by default the directory: ...\Program Files\Radio Management\LCT is selected. Click on Next to confirm the selection and continue the installation procedure. The window Setup Status is displayed (Fig. 3.15). This window points out the indication of the installation progress status. After completion of the installation procedure, the final window Install Shield Wizard Complete of the installation program (Fig. 3.16) is displayed. Click on Finish to close the window and exit. The new program folder Radio Management 5.0 is created in Program menu (see Fig. 3.17).
3-7
Fig. 3.10
Installation of LCT (1/8)
Fig. 3.11
3-8
Fig. 3.12
Fig. 3.13
3-9
Fig. 3.14
Fig. 3.15
3-10
Fig. 3.16
Fig. 3.17
3-11
3.5 Installation of the Equipment Plug-In

Once the LCT software has been succesfully installed, we must install the equipment plug-in. To install the plug-in, the LCT program must be already installed. The LCT program can recognize and, then, manage only the radio equipments, whose plug-in has been installed. The installation of the plug-in causes: the capacity for the Local Craft Terminal program to manage the corresponding type of radio equipment the addition of the Help program, corresponding to this radio equipment management application program, in the Help menu of Local Craft Terminal program.
To install the plug-in, we must start the relative installation executable file from CD-ROM or from floppy disk and, then, follow the instructions shown on the video. The installation program automatically copies the plug-in files in the same directory in which the LCT software is installed. The installation procedure of the plug-in is described, in every detail, in the OMN Manual of the plug-in relevant to the corresponding radio equipment. After the plug-in installation, we must exit and then restart the Local Craft Terminal program (if it was already functioning) to apply the changes.
3.6 Updating of the Help On-line

The help on-line of every LCT application programs (LCT components, equipment plugs-in) is installed during the installation procedure of the application program itself. The files of the help on-line are installed into the same folder where it has been installed the LCT software (usually in the English version of Windows: ...\Program Files\Radio Management\LCT). To update a help, the user has to copy the files of the new help into the folder where it has been installed the LCT software, confirming the overwriting over the files of the preceeding help.
3-12
4 - CONFIGURATION OF THE SERVICE PC
4 CONFIGURATION OF THE SERVICE PC

4.1 Service PC - Radio Equipment connection
Several modes are available for the connection between the service PC and the radio equipment: Direct connection through F interface The service PC is connected directly by means of the proper cable to the local radio equipment. Remote connection through F interface A modem is used for the connection between the service PC and the radio equipment. Direct connection through Ethernet interface (available for SRA Series 3, SRA 4 and SRAL XD) Connection through Ethernet interface via router The router is connected in the network, on Ethernet interface, with the service PC and it is connected directly or via modem, on the F interface, with the radio equipment. Connection on Ethernet interface via DualQ-Adapter The DualQ-Adapter is connected in the network, on Ethernet interface, to the service PC and it is direclty or via modem connected, on F interface, to the radio equipment.
In case of radio link, the radio equipment that is connected, directly or through modem/routing device (router/DualQ-Adapter), to the service PC has the gateway function. For more information, refer to Cap. 5 (LCT - radio equipment connection).
4.2 Configuration of the LCT - Radio Equipment Connection on F interface

On the service PC, it is necessary to create the dial-up connection towards the radio equipment on serial RS-232 interface using, durign the modem setting, the direct connection driver provided on the LCT CD-ROM. In case of remote connection through modem, for the operations to be executed on the modems, refer to the relevant manuals.
4-1
4.2.1
Configuration of the dial-up connection in Windows NT

Under Windows NT the service PC must be equipped with the following software components: remote access service (RAS) TCP/IP communication protocol. Otherwise the software must be installed using the Windows NT CD-ROM. If the service PC is provided with Windows NT Server, we advice you to install the RRAS service instead of RAS service. To execute the configuration of the dial-up connection, it is necessary to execute the following operations: installation and configuration of the direct connection via cable configuration of the remote access service (RAS) creation and configuration of the dial-up connection to radio equipment.
4.2.1.1
Installation and configuration of the direct connection via cable

In Control Panel click twice on Modems (Fig. 4.1). If a modem is already installed, it is displayed the Modem Properties window (Fig. 4.2); click on Add. Otherwise, the system pass directly to the next step. It is displayed the Install New Modem window (Fig. 4.3). Select the Dont detect my modem; I well it from a list option and click on Next. It is displayed the window shown in Fig. 4.4. Click on Have Disk. It is displayed the window shown in Fig. 4.5. Insert the installation floppy-disk/CD-ROM. Click on Browse. It is displayed the Locate File window (Fig. 4.6). Select the drive of the installation floppy-disk/CD-ROM and search the directory containing the mdmitv01.inf file. Click on Open.
The mdmitv01.inf file is available on the LCT CD-ROM. In case of installation from floppy-disk, it is necessary to copy the file on a floppy-disk. It is displayed the window shown in Fig. 4.7. Click on OK. It is displayed the window shown in Fig. 4.8. Click on Next to continue. It is displayed the window shown in Fig. 4.9. Select the communication port (usually: COM1) and click on Next to continue. It is displayed the window shown in Fig. 4.10. Click on Finish to finish the installation of the direct connection. It is displayed the window shown in Fig. 4.11 a window contains, into the list of the installed modems, the Radio Equipment Windows NT Direct Connection device.
4-2
Select the Radio Equipment Windows NT Direct Connection option (Fig. 4.11) and click on Properties. It is displayed the Radio Equipment Windows NT Direct Connection window (Fig. 4.12). Set the properties of the direct connection according to the Fig. 4.12, Fig. 4.13 and Fig. 4.14.
For the connection to the new equipment (as SRA 4, SRAL XD or MicroHop), it is necessary to select 38400 as maximum bit rate. Fig. 4.1 To end and exit, click on OK (Fig. 4.12) and, then, click on Close ( Fig. 4.11).
Installation and configuration of the direct connection in Windows NT (1/14)
4-3
Fig. 4.2
Fig. 4.3
4-4
Fig. 4.4
Fig. 4.5
4-5
Fig. 4.6
Fig. 4.7
4-6
Fig. 4.8
Fig. 4.9
4-7
Fig. 4.10
Fig. 4.11
4-8
Fig. 4.12
For the connection to SRA 4, SRAL XD or MicroHop, set 38400.
4-9
Fig. 4.13
Fig. 4.14
4-10
4.2.1.2
Configuration of the remote access service (RAS)

In case of Windows NT Server, we advise you to install the RRAS service instead of RAS service. The configuration mode is identical. Into the Control Panel menu, click twice on Network (Fig. 4.15). It is displayed the Network window (Fig. 4.16). Select Services. It is displayed the window shown in Fig. 4.17. Select Remote Access Service and click on Properties.
If the RAS service is not available it is necessary to execute its installation using the Windows NT CD-ROM. It is displayed the Remote Access Setup window (Fig. 4.18). Click on Add. It is displayed the Add RAS Device window (Fig. 4.19). Select the Radio Equipment Windows NT Direct Connection device and click on OK. It is displayed the Remote Access Setup window (Fig. 4.20). This window shows, into the relevant list, the Radio Equipment Windows NT Direct Connection device. Select the Radio Equipment Windows NT Direct Connection device and click on Configure (Fig. 4.20). It is displayed the Configure Port Usage (Fig. 4.21). Set the parameters according to the Fig. 4.21. Click on OK. It is newly displayed the window shown in Fig. 4.20. Select the Radio Equipment Windows NT Direct Connection device and click on Network. It is displayed the Network Configuration window (Fig. 4.22). Set the network parameters and the TCP/IP ones for the RAS service according to the Fig. 4.22 and Fig. 4.23. Click on OK. It is newly displayed the window shown in Fig. 4.20. To end and exit, click on Continue (Fig. 4.20) and, then, on Close (Fig. 4.17).
4-11
Fig. 4.15
Configuration of the RAS service in Windows NT (1/9)
Fig. 4.16
4-12
Fig. 4.17
Fig. 4.18
4-13
Fig. 4.19
Fig. 4.20
4-14
Fig. 4.21
Fig. 4.22
4-15
Fig. 4.23
4.2.1.3
Creation and configuration of the dial-up connection

Into My Computer, click twice on Dial-Up Networking (Fig. 4.24). It is displayed the Dial-Up Networking window (Fig. 4.25). Click on New. It is displayed the New Phonebook Entry window (Fig. 4.26). Type SDH connection, as Entry name, and select the Use Telephony dialing properties option. Click on OK. It is displayed the windows shown into Fig. 4.27. Fare click su More (Fig. 4.27) and, keeping pressed the mouse push-button, mark the Operator assisted or manual dialing option (Fig. 4.28). Click on More (Fig. 4.27) and select the Edit entry and modem properties (Fig. 4.29). It is displayed the Edit Phonebook Entry window (Fig. 4.30). Set the properties: Basic: according to Fig. 4.30 and Fig. 4.31 Server: according to Fig. 4.32 and Fig. 4.33 Script: according to Fig. 4.34 and Fig. 4.35 Security: according to Fig. 4.36 X.25: according to Fig. 4.37.
For the connection to the new equipment (as SRA 4, SRAL XD or MicroHop) it is necessary to select 38400 mbps in the Modem Configuration window (Fig. 4.31).
4-16
In case of troubles during the connection, select the Use default gateway on remote network option (Fig. 4.33). In this case, remember that the other networks connected to the Ethernet interface of service PC can become unreachable (see Cap. 5 "LCT - RADIO EQUIPMENT CONNECTION"). If a modem is provided, it is necessary to enable the option Enable hardware flow control (Fig. 4.31). Click on More (Fig. 4.27) and select the User preferences (Fig. 4.38) It is displayed the User Preferences window (Fig. 4.39). Set the properties: Dialing: according to Fig. 4.39 Callback: according to Fig. 4.40 Appearance: according to Fig. 4.41 Phonebook: according to Fig. 4.42. Click on More (Fig. 4.27) and select the Logon preferences (Fig. 4.43). It is displayed the Logon Preferences window (Fig. 4.44). Set the properties: Dialing: according to Fig. 4.44 Callback: according to Fig. 4.45 Appearance: according to Fig. 4.46 Phonebook: according to Fig. 4.47. To end and exit, click on OK (Fig. 4.47) and then on Close (Fig. 4.27).
Fig. 4.24
Creation and configuration of the dial-up connection in Windows NT (1/24)
4-17
Fig. 4.25
Fig. 4.26
4-18
Fig. 4.27
Fig. 4.28
4-19
Fig. 4.29
Fig. 4.30
4-20
Fig. 4.31
4-21
Fig. 4.32
Fig. 4.33

In case of troubles during the connection, select the pointed out option. In this case, remember that the other networks connected to the Ethernet interface of the service PC can become unreachable (Cap. 5 (LCT - radio equipment connection)).
4-22
Fig. 4.34
Fig. 4.35
4-23
Fig. 4.36
Fig. 4.37
4-24
Fig. 4.38
Fig. 4.39
4-25
Fig. 4.40
Fig. 4.41
4-26
Fig. 4.42
Fig. 4.43
4-27
Fig. 4.44
Fig. 4.45
4-28
Fig. 4.46
Fig. 4.47
4-29
4.2.2
Configuration of the dial-up connection in Windows 2000

Under Windows 2000 the following software components must be installed on the service PC: TCP/IP communication protocol. Otherwise the software must be installed using the Windows 2000 CD-ROM. For the configuration of the dial-up connection, the following operations are required: installation of the direct connection via cable creation and configuration of the dial-up connection with the radio equipment configuration of the TCP/IP protocol.
4.2.2.1
Installation of the direct connection via cable

In Control Panel click twice on Phone and Modem Options (Fig. 4.48). The system displays the Phone and Modem Options window (Fig. 4.49). Select Modems and then click on Add. The window Add/Remove Hardware Wizard - Install New Modem is displayed (Fig. 4.50). Select the Don't detect my modem, I will select it from a list and click on Next. The window of Fig. 4.51 is displayed; click on Have Disk. The window of Fig. 4.52 is displayed. Insert the installation floppy-disk/CD-ROM and click on Browse. The window Locate File is displayed (Fig. 4.53). Select the drive of the installation floppy-disk/CD-ROM and search the directory containing the mdmitv01.inf file; click on Open.
The mdmitv01.inf file is on CD-ROM. In case of installation from floppy-disk, it is necessary to copy the file on a floppy-disk.. The window of Fig. 4.52 is displayed again. Click on OK to copy the mdmitv01.inf file. The window of Fig. 4.54 is displayed; click on Next to continue. The window of Fig. 4.55 is displayed. Select the communication port (usually: COM 1) and click on Next to continue. The window of Fig. 4.56 is displayed. click on Yes to continue. The window of Fig. 4.57 is displayed. Click on Finish to end the installation procedure for direct connection. The window of Fig. 4.58 is displayed where Radio Equipment + Windows NT Direct Connection appears in the list of installed modems. Click on OK to end and exit.
4-30
Fig. 4.48
Installation of the direct connection in Windows 2000 (1/11)
Fig. 4.49
4-31
Fig. 4.50
Fig. 4.51
4-32
Fig. 4.52
Fig. 4.53
4-33
Fig. 4.54
Fig. 4.55
4-34
Fig. 4.56
Fig. 4.57
4-35
Fig. 4.58
4.2.2.2

Click on Start and select: Settings Network and Dial-up Connections Make New Connection (Fig. 4.59). The system displays the Network Connection Wizard window (Fig. 4.60). Click on Next to continue. The system displays the window shown in Fig. 4.61. Select the Connect directly to another computer option. Click on Next to continue. The system displays the window shown in Fig. 4.62. Select the Guest option. Click on Next to continue. The system displays the equipment selection window (Fig. 4.63). Select the Radio Equipment Windows NT Direct Connection option (Fig. 4.64). Click on Next to continue.. The system displays the window shown in Fig. 4.65. Select the For all users option. Click on Next to continue. The system displays the window shown in Fig. 4.66. Click on Finish to complete and to exit. In Control Panel, click twice on Phone and Modem Options (Fig. 4.67). The system displays the Phone and Modem Options window (Fig. 4.68). Select Modems and then click on Properties.
4-36
The system displays the window shown in Fig. 4.69. Set the properties of the connection as pointed out into the figure. Click on Advanced and then on Change Default References. The system displays the window shown in Fig. 4.70. Set the properties of the connection as pointed out into the figure. Click on Advanced.
For the connection to the new equipment (as SRA 4, SRAL XD or MicroHop), it is necessary to select 38400 as maximum bit rate for the port. The system displays the window shown in Fig. 4.71. Set the properties of the connection as pointed out into the figure. Click on OK to end and confirm the settings. To close all the currently open windows.
Fig. 4.59
Creation and configuration of the dial-up connection in Windows 2000 (1/13)
4-37
Fig. 4.60
Fig. 4.61
4-38
Fig. 4.62
Fig. 4.63
4-39
Fig. 4.64
Fig. 4.65
4-40
Fig. 4.66
Fig. 4.67
4-41
Fig. 4.68
Fig. 4.69
4-42
Fig. 4.70
4-43
Fig. 4.71
4.2.2.3
Configuration of the TCP/IP protocol

In Control Panel, click twice on Network and Dial-up Connections (Fig. 4.72). The system displays the Network and Dial-up Connections window (Fig. 4.73). Click twice on the Radio Equipment Windows NT Direct Connection option. The system displays the window shown in Fig. 4.74. Click on the Properties option and then on Networking. The system displays the window shown in Fig. 4.75. Select Internet Protocol (TCP/IP) and click on the Properties. The system displays the Internet Protocol (TCP/IP) Properties window (Fig. 4.76). Select the properties as pointed out in figure and click on Advanced. Set the protocol properties according to the indications shown in Fig. 4.77, Fig. 4.78, Fig. 4.79 and Fig. 4.80. Click on OK to finish the procedure and to confirm the executed settings.
4-44
Fig. 4.72
Configuration of the TCP/IP protocol in Windows 2000 (1/9)
Fig. 4.73
4-45
Fig. 4.74
Fig. 4.75
4-46
Fig. 4.76
Fig. 4.77
4-47
Fig. 4.78
Fig. 4.79
4-48
Fig. 4.80
4-49
4.2.3
Configuration of the dial-up connection in Windows XP

Under Windows XP the following software components must be installed on the service PC: TCP/IP communication protocol. Otherwise the software must be installed using the Windows XP CD-ROM. For the configuration of the dial-up connection, the following operations are required: installation of the direct connection via cable creation and configuration of the dial-up connection with the radio equipment configuration of the TCP/IP protocol.
4.2.3.1
Installation of the direct connection via cable

In Control Panel click twice on Phone and Modem Options (Fig. 4.81). The system displays the Phone and Modem Options window (Fig. 4.82). Select Modems and then click on Add. The window Add Hardware Wizard - Install New Modem is displayed (Fig. 4.83). Select the Don't detect my modem; I will select it from a list and click on Next. The window of Fig. 4.84 is displayed; click on Have Disk. The window of Fig. 4.85 is displayed. Insert the installation floppy-disk/CD-ROM and click on Browse. The window Locate File is displayed (Fig. 4.86). Select the drive of the installation floppy-disk/CD-ROM and search the directory containing the mdmitv01.inf file; click on Open.
The mdmitv01.inf file is on CD-ROM. In case of installation from floppy-disk, it is necessary to copy the file on a floppy-disk.. The window of Fig. 4.87 is displayed again. Click on OK to copy the mdmitv01.inf file. The window of Fig. 4.88 is displayed; click on Next to continue. The window of Fig. 4.89 is displayed. Select the communication port (usually: COM 1) and click on Next to continue. The window of Fig. 4.90 is displayed. click on Continue Anyway to continue. The window of Fig. 4.91 is displayed. Click on Finish to end the installation procedure for direct connection. The window of Fig. 4.92 is displayed where Radio Equipment Windows NT Direct Connection appears in the list of installed modems. Click on OK to end and exit.
4-50
Fig. 4.81
Installation of the direct connection in Windows XP (1/12)
Fig. 4.82
4-51
Fig. 4.83
Fig. 4.84
Fig. 4.85
4-52
Fig. 4.86
Fig. 4.87
Fig. 4.88
4-53
Fig. 4.89
Fig. 4.90
Fig. 4.91
4-54
Fig. 4.92
4.2.3.2

Click on Start and select: Settings Network Connections. The system displays the Network Connections window (Fig. 4.93). Select Create a New Connection option. The system displays the New Connection Wizard window (Fig. 4.94). Click on Next to continue. The system displays the window shown in Fig. 4.95. Select the Set up an advanced connection option. Click on Next to continue. The system displays the window shown in Fig. 4.96. Select the Connect directly to another computer option. Click on Next to continue. The system displays the window shown in Fig. 4.97. Select the Guest option. Click on Next to continue. The system displays the window for the name selection of the connection (Fig. 4.98). Type the name and click on Next to continue. The system displays the equipment selection window (Fig. 4.99). Select the Radio Equipment Windows NT Direct Connection option (Fig. 4.100). Click on Next to continue. The system displays the window shown in Fig. 4.101. Click on Finish to complete and to exit. In Control Panel, click twice on Phone and Modem Options (Fig. 4.102). The system displays the Phone and Modem Options window (Fig. 4.103). Select Modems and then click on Properties. The system displays the window shown in Fig. 4.104. Click on Advanced (Fig. 4.105) and then on Change Default References. The system displays the window shown in Fig. 4.106. Set the properties of the connection as pointed out into the figure. Click on Advanced.
4-55
For the connection to the new equipment (as SRA 4, SRAL XD or MicroHop), it is necessary to select 38400 as bit rate for the port. The system displays the window shown in Fig. 4.107. Set the properties of the connection as pointed out into the figure. Click on OK to end and confirm the settings. To close all the currently open windows.
Fig. 4.93
Creation and configuration of the dial-up connection in Windows XP (1/15)
Fig. 4.94
4-56
Fig. 4.95
Fig. 4.96
Fig. 4.97
4-57
Fig. 4.98
Fig. 4.99
Fig. 4.100
4-58
Fig. 4.101
Fig. 4.102
4-59
Fig. 4.103
Fig. 4.104
4-60
Fig. 4.105
Fig. 4.106
4-61
Fig. 4.107
4.3 Configuration of the Connection to LAN on Ethernet Interface

The only operation required on the service PC is the TCP/IP protocol configuration for the Ethernet NIC. Under Windows, the Server PC must be equipped with the following software components: Ethernet NIC and corresponding driver TCP/IP communication protocol. Otherwise the software must be installed using the Windows CD-ROM and/or the floppy-disk/CD-ROM with drivers for the NIC. In case of connection via router, refer to the corresponding manual for the operations on the router itself. In case of connection through DualQ-Adapter, for the operations to be executed on the DualQ-Adapter, refer to the relevant OMN Manual.
4-62
4.3.1
Configuration of the TCP/IP protocol in in Windows NT

For the configuration of the TCP/IP protocol in Windows NT, the operator must have the administrator access rights. On the Control Panel click twice on Network (Fig. 4.108). The window Network (Fig. 4.109) appears. Click on Adapters. The list of the NICs present on the PC is displayed (Fig. 4.110). Check under Network Adapters if the Ethernet NIC is present. Click on Protocols.
If the Ethernet NIC is not equipped, it must be installed in Windows NT by the function Add, using the Window NT CD-ROM and/or the floppy-disk/CD-ROM with software drivers for the NIC. The list of the installed protocols (Fig. 4.111) is displayed. Select TCP/IP Protocol and click on Properties.
If the TCP/IP protocol is not available it must be installed using the Windows NT installation CD-ROM. The window Microsoft TCP/IP Properties (Fig. 4.112) is displayed. Set the TCP/IP protocol properties depending on what is shown in Fig. 4.112, Fig. 4.113, Fig. 4.114, Fig. 4.115 and Fig. 4.116.
The IP address, the Subnet Mask of the service PC and the gateway IP address (Fig. 4.112) must therefore be requested from the network administrator. Depending on the Ethernet network configuration, it may be necessary to activate or deactivate the DNS (Fig. 4.114). If the DNS is activated, the network administrator must be asked for the DNS configuration parameters to be inserted. Close the window Microsoft TCP/IP Properties clicking on OK. The window Network (Fig. 4.112) is displayed again. Click on OK to end and confirm the settings.
4-63
Fig. 4.108
TCP/IP protocol configuration in Windows NT (1/9)
Fig. 4.109
4-64
Fig. 4.110
Fig. 4.111
4-65
Fig. 4.112

Assigned by network administrator
Fig. 4.113
4-66
Fig. 4.114

Depending on network configuration
Fig. 4.115
4-67
Fig. 4.116
4.3.2
Configuration of the TCP/IP protocol in Windows 2000

The procedure for the configuration of the TCP/IP protocol in Windows 2000, relevant to the Ethernet NIC, is the following one: On the Control Panel click twice on Network and Dial-up Connections (Fig. 4.117). The window Network and Dial-up Connections (Fig. 4.118) appears. Click by means of the mouse R.H. push-button on the LAN connection icon and then select Properties (Fig. 4.119)
If the LAN connection is not present, it is necessary to create it by means of the Make New Connection feature, using the Windows 2000 CD-ROM and/or the floppy disk/CD-ROM with the software drivers of the Ethernet NIC. The system displays the LAN Properties window (Fig. 4.120). Select Internet Protocol (TCP/IP) and click on Properties.
If the TCP/IP protocol is not available it must be installed using the Windows 2000 installation CD-ROM. The window Internet Protocol (TCP/IP) Properties (Fig. 4.121) is displayed. Set the TCP/IP protocol properties depending on what is shown in Fig. 4.121, Fig. 4.122, Fig. 4.123, Fig. 4.124, Fig. 4.125 and Fig. 4.126.
4-68
The IP address, the Subnet Mask of the service PC and the gateway IP address (Fig. 4.122) must therefore be requested from the network administrator. Depending on the Ethernet network configuration, it may be necessary to activate or deactivate the DNS (Fig. 4.123). If the DNS is activated, the network administrator must be asked for the DNS configuration parameters to be inserted. Fig. 4.117 Close the window Internet Protocol (TCP/IP) Properties clicking on OK. The window LAN Properties (Fig. 4.120) is displayed again. Click on OK to end and confirm the settings.
TCP/IP protocol configuration in Windows 2000 (1/10)
4-69
Fig. 4.118
Fig. 4.119
4-70
Fig. 4.120
Fig. 4.121
(*)
The settings of the parameters depends on the network configuration and they have to be executed by the network administrator.
4-71
Fig. 4.122
(*)
Fig. 4.123
(*)
4-72
Fig. 4.124
(*)
Fig. 4.125
4-73
Fig. 4.126
(*)
4.3.3
Configuration of the TCP/IP protocol in Windows XP

The procedure for the configuration of the TCP/IP protocol in Windows XP, relevant to the Ethernet NIC, is the following one: On the Control Panel click twice on Network and Internet Connections (Fig. 4.127). The window Network and Internet Connections (Fig. 4.128) appears. Click twice on Network Connections. The system displays the Network Connections window (Fig. 4.129). Click by means of the mouse R.H. push-button on the LAN connection icon and then select Properties (Fig. 4.130)
If the LAN connection is not present, it is necessary to create it by means of the Create a new connection feature, using the Windows XP CD-ROM and/or the floppy disk/CD-ROM with the software drivers of the Ethernet NIC. The system displays the Local Area Connection Properties window (Fig. 4.131). Select Internet Protocol (TCP/IP) and click on Properties.
If the TCP/IP protocol is not available it must be installed using the Windows XP installation CD-ROM. The Internet Protocol (TCP/IP) Properties window (Fig. 4.132) is displayed.
4-74
Set the TCP/IP protocol properties depending on what is shown in Fig. 4.132, Fig. 4.133, Fig. 4.134, Fig. 4.135, Fig. 4.136 and Fig. 4.137.
The IP address, the Subnet Mask of the service PC and the gateway IP address (Fig. 4.132) must therefore be requested from the network administrator. Depending on the Ethernet network configuration, it may be necessary to activate or deactivate the DNS (Fig. 4.134). If the DNS is activated, the network administrator must be asked for the DNS configuration parameters to be inserted. Fig. 4.127 Close the window Internet Protocol (TCP/IP) Properties clicking on OK. The Local Area Connection Properties window (Fig. 4.131) is displayed again. Click on OK to end and confirm the settings.
TCP/IP protocol configuration in Windows XP (1/11)
4-75
Fig. 4.128
Fig. 4.129
4-76
Fig. 4.130
Fig. 4.131
4-77
Fig. 4.132
(*)
Fig. 4.133
(*)
4-78
Fig. 4.134
(*)
Fig. 4.135
(*)
4-79
Fig. 4.136
Fig. 4.137
4-80
4.4 Name Solving

LCT identifies every NE with a name and/or with a numeric IP address. LCT is able to execute autonomoulsy the resolution of the host_names relevatn to alla the NEs, present into the map, for wich it has been set as the name as the IP address. On the contrary, the use into the map of the name only to identify a NE, is possible only if the operating is able to execute the resolution of the host_names (for instance through a DNS Server or through the system hosts file). Planning of the host table means definition of the correspondence between name and numeric IP address for every NE. This planning is an operation reserved for the network administrator The procedure to create the host table through hosts file is the following one: Use a common editor program to open the hosts %SystemRoot%/System32/Drivers/Etc system sub-folder. file in the
For every NE, specify the correspondence between the numeric IP address and the associated name. During editing it is necessary to insert a tab or leave a free space between the numeric IP address and the name. Fig. 4.138 shows an example for the hosts file. Exit from the file and save in ASCII format without extension, so that Windows NT/2000/XP can recognize the file as a system file.
It is always possible to update the host table after a compilation error or a change in network. For the creation/change of the host table in Windows NT/2000/XP, the operator must have the administrator access rights.
4-81
Fig. 4.138
Example of hosts file
4-82
5 - LCT - RADIO EQUIPMENT CONNECTION
5 LCT - RADIO EQUIPMENT CONNECTION

5.1 Overview
This chapter describes the forms and the problems concerning the connection and the access, via TCP/IP protocol, of the service PC to the radio equipment. These differ according to: the operative system installed on the service PC (Windows NT/2000/XP) the interface used on the service PC (serial RS-232C or Ethernet).
5.2 LCT - Radio Equipment Connection Mode

5.2.1
5.2.1.1
Direct connection on F interface

Overview
The service PC is directly connected, by a proper cable, to the local radio equipment (Fig. 5.1). In case of radio link, the local radio equipment has the gateway functions (Fig. 5.2).
Fig. 5.1
LCT - radio equipment direct connection on F interface

SERVICE PC (LCT)
RADIO EQUIPMENT
DCE F INTERFACE (RS-232C)
DTE
5-1
Fig. 5.2
LCT - radio link direct connection on F interface
SERVICE PC (LCT) RADIO EQUIPMENT RADIO EQUIPMENT

DCE TERMINAL B TERMINAL A DTE F INT. (RS-232C)
RADIO LINK
5.2.1.2
Requirements of RS-232C serial cable

For the local connection between service PC and the radio equipment, a serial cable is required according to EIA RS-232C standard specifications. It must be a not-modem pin-to-pin cable, equipped with a 9-pin male CANNON connector on the radio equipment side (Fig. 5.3). In this connection, the service PC is considered a DTE unit, while the radio equipment is considered a DCE unit.
Fig. 5.3
RS-232C connecting cable between LCT and radio equipment
NOT USED
NOT USED
RADIO EQUIPMENT (DCE)
PC (DTE)
5-2
5.2.2
5.2.2.1
Remote connection on F interface

Overview
The use of a modem allows to establish a remote connection, using a F interface, between the service PC and the radio equipment (Fig. 5.4). In case of radio link, the radio equipment, connected to the service PC, has the gateway function (Fig. 5.5).
Fig. 5.4
LCT - radio equipment remote connection on F interface

RADIO EQUIPMENT MODEM
RADIO SIDE DCE F INTERFACE (RS-232C) DCE
TELAPHONE LINE
SERVICE PC (LCT) MODEM

PC SIDE DTE DCE
F INT. (RS-232C)
Fig. 5.5
LCT - radio link remote connection on F interface
RADIO EQUIPMENT
RADIO LINK
RADIO EQUIPMENT
DCE DCE F INT. (RS-232C)
RADIO SIDE
MODEM
TERMINAL B
TERMINAL A
TELEPHONE LINE
SERVICE PC (LCT) MODEM

PC SIDE DTE DCE
F INT. (RS-232C)
5-3
The use of the remote connection requires the installation and the configuration in Windows of the modem used to replace the direct connection via cable modem during the configuration procedure (Cap. 4 "CONFIGURATION OF THE SERVICE PC"). For more details about the configuration and use of modems, refer to the respective handbooks.
5.2.2.2
Characteristics of the connection cables

The following is a list of requirements for the connection cables to be used: Connection between radio equipment and modem. Use a standard cable for the DCE - DCE connection, because both radio equipment and modem are DCE units. The cable must be provided, on the radio equipment side, with a 9-pin male CANNON connector. Connection between PC (RS-232C serial port) and modem. Use a standard cable for the DTE-DCE connection, because the PC is a DTE unit and the modem is a DCE unit. Connection between modem and telephone line. The modem interface towards the telephone line is usually terminated with a 8-pin RJ45 standard jack. Some modems have two different interfaces (one for the switched line and one for the dedicated line).
5.2.2.3
Characteristics and configuration of modems

Modem characteristics The modems must be Hayes compatible and must support standard AT commands, with a minimum baud-rate of 19200 bps (transmission speed of radio equipment). This condition represents a restriction for the entire system. In this case, the communication between modem and radio equipment must run at 19200 bps, while a higher baud-rate can be used between modems, depending on the modem characteristics and the quality of the used line. The communication to the new equipment (as SRA 4 or SRAL XD) takes place at 38400 bps. 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 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:
5-4
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, using the AT command: &W (modems use the default configuration at start-up).
5.2.3
Direct connection on Ethernet interface

In case of SRA Series 3, SRA 4 or SRAL XD, it is possible to have the direct connection on Ethernet interface between the service PC and the radio equipment (Fig. 5.6). In case of radio link, the radio equipment connected to the service PC has the gateway function (Fig. 5.7).
5-5
Fig. 5.6
LCT - SRA Series 3 direct connection on Ethernet interface

SRA SERIES 3
SRA Series 3
LAN - ETHERNET
SERVICE PC (LCT)
INTRANET/ INTERNET
Fig. 5.7
LCT - SRA Series 3 link direct connection on Ethernet interface
SRA SERIES 3
SRA Series 3
RADIO LINK
SRA SERIES 3
SRA Series 3
TERMINAL B
TERMINAL A
LAN - ETHERNET
SERVICE PC (LCT)
INTRANET/ INTERNET
5-6
5.2.4
Remote connection on Ethernet interface

Using the DualQ-Adapter or a router (Fig. 5.8) we can implement the connection to a radio equipment from a service PC, inserted in a LAN-Ethernet context (Intranet or Internet). The DualQ-Adapter/router is connected in the network, on Ethernet interface, with the service PC and it is connected, directly or via modem, on F interface, to the radio equipment that has the gateway functions. In case of radio link, the radio equipment connected to the DualQ-Adapter/router has the gateway function (Fig. 5.9) In this application the DualQ-Adapter/router acts as interface converter.
For the connection modes, configuration and use of the DualQ-Adapter/router, refer to the relevant manuals. Fig. 5.8 LCT - radio equipment remote connection on Ethernet interface
RADIO EQUIPMENT
DCE
DUALQ-ADAPTER/ ROUTER
DTE F INT. (RS-232C)
LAN - ETHERNET
SERVICE PC (LCT)
INTRANET/ INTERNET
5-7
Fig. 5.9
LCT - radio link remote connection on Ethernet interface
RADIO EQUIPMENT
RADIO LINK
RADIO EQUIPMENT
DCE
DUALQ-ADAPTER/ ROUTER
DTE F INT. (RS-232C)
TERMINAL B
TERMINAL A
LAN - ETHERNET
SERVICE PC (LCT)
INTRANET/ INTERNET
5.3 Activation of LCT - Radio Equipment Connection

The modes to activate the LCT - radio equipment connection differ according to the interface types: F interface It is necessary to activate the dial-up connection to radio equipment on the service PC, before running the Local Craft Terminal program. Ethernet interface The connection between the service PC and the radio equipment is automatically.
Using the DualQ-Adapter/router for the connection on Ethernet interface, we must activate the connection between router and radio equipment, before running the Local Craft Terminal program.
5-8
5.3.1
Activation of the dial-up connection in Windows NT

The activation procedure of the dial-up connection in Windows NT is the following: If the connection uses a modem, the communication via modem must be activated first. First, check that the connection cable of the PC serial port is disconnected.
The need to begin the operations with the cable disconnected depends on the functioning mode of the Windows NT RAS service. The RAS service, in fact, supports only devices able to manage the Data Terminal Ready signal (CD line), because it needs that, at the beginning, the CD signal is deactivated. The radio equipment do not provide the management of the CD signal (the signal is always activated). In Windows NT Server, if the RRAS service is installed instead of RAS service, we can start the operations with the cable connected. In My Computer, click twice on Dial-Up Networking (Fig. 5.10). The Dial-Up Networking window is displayed (Fig. 5.11). Select Radio connection in Phonebook entry to dial and click twice on Dial. The Connect to Radio connection window is displayed (Fig. 5.12). Click on OK. The Pre-Dial Terminal Screen window is displayed (Fig. 5.13). Now connect the connection cable to the PC serial port. To ensure that the hardware is correctly working, wait for the data stream in the Pre-Dial Terminal Screen window (Fig. 5.14) and, then, click on Continue.
The packages of the TCP/IP protocol start and end with the character (~). The Operator Assisted or Manual Dial window is displayed (Fig. 5.15). Click on OK. The After Dial Terminal window is displayed (Fig. 5.16). Wait for the end of the data stream into the After Dial Terminal window and, then, click on Done.
While the local equipment is transmitting the data, the dial-up connection can not be established. The Connection Complete window is displayed (cfr. Fig. 5.17). Click on OK. When the connection is established, the Dial-Up Networking Monitor window is displayed (Fig. 5.19). Into the tray area (lower corner on the right of the desktop), the monitor RAS icon is displayed (Fig. 5.18). The Dial-Up Networking Monitor window allows to display the information, the details and the preferences concerning the connection on progress (Fig. 5.19, Fig. 5.20, Fig. 5.21). The automatic displaying of the Dial-Up Networking Monitor window is a
5-9
preferential setting. However, it is always possible to open the window clicking twice on the monitor RAS icon (Fig. 5.18). 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.6.2) to the radio equipment (Fig. 5.22) starting up the Local Craft Terminal program. Exiting from the Local Craft Terminal program, the connection must be closed with the following procedure: move the mouse on the monitor RSA icon (Fig. 5.18) and click on its right button the dial-up menu (Fig. 5.23); is displayed; click on Close. Fig. 5.10 Activation of the dial-up connection in Windows NT (1/13)
5-10
Fig. 5.11
Activation of the dial-up connection in Windows NT (2/13)
Fig. 5.12
5-11
Fig. 5.13
Fig. 5.14
5-12
Fig. 5.15
Fig. 5.16
5-13
Fig. 5.17
Fig. 5.18
RAS monitor icon
5-14
Fig. 5.19
Fig. 5.20
5-15
Fig. 5.21
Fig. 5.22
5-16
Fig. 5.23
Closing of the dial-up connection in Windows NT
5.3.2
Activation of the dial-up connection in Windows 2000

The activation procedure of the dial-up connection in Windows 2000 is the following: If the connection uses a modem, the communication via modem must be activated first. In Control Panel, click twice on Network and Dial-up Connections (Fig. 5.24). The system displays the Network and Dial-up Connections window (Fig. 5.25). Through the R.H. push-button of the mouse, click on the icon for the dial-up connection created before (into the example: RADIO) (Fig. 5.25) and, into the displayed pop-up menu, select Properties. The system displays the RADIO Properties window (Fig. 5.26). Select Configure. The system displays the Modem Configuration window (Fig. 5.27). Select the Show terminal window option. Close the open window, clicking on OK. Into the Network and Dial-up Connections window (Fig. 5.25) click twice on the icon of the dial-up connection (into the example: RADIO). The system displays the Connect RADIO window (Fig. 5.28). Select Connect. The system displays the Pre-Dial Terminal Screen window (Fig. 5.29). Wait for to be sure that the hardware works properly, that the system starts up the data stream and then click on Continue.
5-17
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.30). If the operator clicks on Cancel, it is always possible to stop immediately the connection procedure itself. The system displays the Connection Complete window (Fig. 5.31). Click on OK. When the connection is established, into the tray area (lower corner on the right of the desktop), the monitor icon of the connection is displayed (Fig. 5.32). If the operator clicks, through the R.H. push-button of the mouse, on such an icon and selects Status, the system opens the status window of the connection (into the example: RADIO Status) (Fig. 5.33 and Fig. 5.34). Through such a window, it is possible to display information, details and preferences concerning the connection on progress.
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.6) to the radio equipment (Fig. 5.35) starting up the Local Craft Terminal program. Exiting from the Local Craft Terminal program, the connection must be closed with the following procedure: through the R.H. push-button of the mouse, click on the connection monitor icon (Fig. 5.32) and select Disconnect. Fig. 5.24 Activation of the dial-up connection in Windows 2000 (1/12)
5-18
Fig. 5.25
Activation of the dial-up connection in Windows 2000 (2/12)
Fig. 5.26
5-19
Fig. 5.27
Fig. 5.28
Fig. 5.29
Fig. 5.30
5-20
Fig. 5.31
Fig. 5.32
Monitor icon
Fig. 5.33
5-21
Fig. 5.34
Fig. 5.35
5.3.3
Activation of the dial-up connection in Windows XP

The activation procedure of the dial-up connection in Windows XP is the following: If the connection uses a modem, the communication via modem must be activated first. In Control Panel, click twice on Network and dial-up Connections (Fig. 5.36). The system displays the Network Connections window (Fig. 5.37). Through 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.38), select Properties. The system displays the RADIO Properties window (Fig. 5.39). Select Configure. The system displays the Modem Configuration window (Fig. 5.40). Select the Show terminal window option. Close the open window, clicking on OK. Into the Network Connections window (Fig. 5.41) click twice on the icon of the dial-up connection (into the example: RADIO).
5-22
The system displays the Connect RADIO window (Fig. 5.42). Select Connect. The system displays the Pre-Dial Terminal Screen window (Fig. 5.43). Wait for to be sure that the hardware works properly, that the system starts up the data stream and then click on Continue.
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.44). If the operator clicks on Cancel, it is always possible to stop immediately the connection procedure itself. Al 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.45). If the operator selects View status of this connection into the Network Tasks field of the Network Connections window (Fig. 5.45), the system opens the status window of the connection (into the example: RADIO Status) (Fig. 5.46 and Fig. 5.47). Through such a window, it is possible to display information, details and preferences concerning the connection on progress.
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.6) to the radio equipment (Fig. 5.48) starting up the Local Craft Terminal program. Exiting from the Local Craft Terminal program, the connection must be closed with the following procedure: through the R.H. push-button of the mouse, click on the connection monitor icon and select Disconnect.
5-23
Fig. 5.36
Activation of the dial-up connection in Windows XP (1/13)
Fig. 5.37
5-24
Fig. 5.38
Fig. 5.39
5-25
Fig. 5.40
Fig. 5.41
5-26
Fig. 5.42
Fig. 5.43
Fig. 5.44
5-27
Fig. 5.45
Fig. 5.46
5-28
Fig. 5.47
Fig. 5.48
5-29
5.4 Access to Radio Equipment

5.4.1 Plug-in loading
Into the Local Craft Terminal program to activate the equipment management, it is necessary to load the relevant plug-in (activation of the access towards the equipment). The link/local map constitutes the graphical interface for the access to the equipment of the Local Craft Terminal program. At the map opening, the Local Craft Terminal program tries to connect to all the equipment recalled from the map itself. For each equipment, the connection phase is executed according to the following procedure: if an error during the communication is detected (for instance: not existing NE), an icon showing that the NE is not connected is displayed (not intentional disabling status) if the connection is successfully exectued, the program tries to recognize the radio equipment type: if the recognition is successfully executed (NE On-Line) the relevant configuration file is loaded and a pre-defined icon showing the radio equipment type is displayes; then, into the corresponding NE menu, the operating menu that allows the NE configuration and control is added if the recognition is not successfully executed (for instance: radio equipment not supported by LCT), the system displays an icon of unknown equipment showing that the radio equipment type is not supported.
If all the following conditions are present, some connection troubles could occur using the local map (default local IP address = 192.168.255.3): dial-up connection by F interface TCP/IP protocol used also by other interfaces (e.g.: Ethernet for local LAN, ...) local equipment with IP address correctly configured. In this case, it is necessary to create a new map with the effective IP address (par. 5.5.2) of the equipment, because the local map can not be used. LCT cyclically makes an attempt for an automatic connection towards the NEs which are in involuntary disabled status. The voluntary disabling status of a NE is pointed out with a proper icon (Cap. 7 "OPERATING GUIDE OF NETBUILDER"). Fig. 5.49 Example of local map
5-30
5.4.2
NE opening
The opening modes of the radio equipment differ depending on enabled/disabled status of equipment Security: With enabled equipment Security, the program foresees the following three user classes: Read Only: access to the functions in reading mode only Read Write: access to the functions as in reading mode as in writing one, with the exception of the functions reserved to the Admin user class for which it is possible the access in reading mode only Admin: access to all the functions as in reading mode as in writing one With disabled equipment Security, the program foresees also the access to the equipment with the user class; Anonymous this access does not need for the insertion of the password; the only limit is that it is not possible to change the settings relevant to the Security (enabling status and password).
The Security enabling prevents the contemporary access to a NE of more operators with the Admin or Read Write user classes avoiding in such a way conflicts or configuration errors. For the NE Security, the default factory passwords are the following ones: Admin user class: SYSMANAGER Read Write user class: READWRITE Read Only user class: READONLY. By means of the NE operating menu, the operator can set/change the Security configuration only if he accesses the program with the Admin user class. At the login, the system displays the Open NE window (Fig. 5.50) where it is requested the selection of the user class and the insertion of the relevant password. If the NE Security has been disabled, at its new enabling, it get back again the previously set passwords. The Security configuration (enabling status and password) is a specific one for every NE and it is stored into the NE memory. The NE Security has to be enabled if it is possible to have contemporary accesses of two or more managers (for instance: NetViewer and LCT). Fig. 5.50 Login window
At the opening of the radio equipment, the Local Craft Terminal program starts to load the configuration file for the equipment (Fig. 5.51). When the configuration file and the concerning controls have been loaded, if no error has been taken place, the access towards the equipment is activated.
5-31
The dinamic part is added in the equipment menu; this part is the equipment operative menu for configuration and control. Fig. 5.51 Window of the loading of configuration file
5.5 Routing Troubles with the TCP/IP Packets

5.5.1 Common cases of TCP/IP packet routing
The TCP/IP protocol can manage different interfaces (serial line, Ethernet network, ....) according to the network functions present on the service 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 service PC, it is always reachable. In case of troubles, it is possible to force the packet forwarding on the serial 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.52, Fig. 5.53, Fig. 5.54). TCP/IP on Ethernet network only If on the service 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 service 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 or of 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, the relevant serial port of the service 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 service PC has an IP address and a Net-Mask presetted by
5-32
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 addess and by the Net-Mask of the service 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 addess and by the Net-Mask of the service PC network card (for instance: in the case of Ethernet card with IP address = 138.132.140.104 and Net-Mask = 255.255.255.0, the addresses that belong to the sub-network are 138.132.140.X). To route correctly some packets with an IP address not compatible neither with the serial line nor with the Ethernet network, it is necessary to respect the following indications: to forward the packets on the serial line, select the option Use default gateway on remote network into the configuration window of the TCP/IP protocol for the serial line (Fig. 5.52, Fig. 5.53, Fig. 5.54); this configuration affects all the programs that use the TCP/IP protocol (for instance: Internet Explorer, Netscape Communicator, etc.) to forward the packets on the Ethernet network, define and configure a gateway for the Ethernet interface. Fig. 5.52 Forcing of Use default gateway on remote network option in Windows NT
Use default gateway on remote network option
5-33
Fig. 5.53
Forcing of Use default gateway on remote network option in Windows 2000

Fig. 5.54
Forcing of Use default gateway on remote network option in Windows XP

5-34
5.5.2
5.5.2.1
Useful commands to solve reachability problems

Dial-up monitor window in Windows NT
In Windows NT, it is possible to know the IP address of the local equipment, connected to the serial line, by means of the dial-up monitor window. To access to the monitor dial-up window (Fig. 5.55), it is necessary to click on the modem icon present into the tray area (lower right corner of the desktop). Display the details to detect the IP address.
Fig. 5.55
Dial-up monitor window in Windows NT
IP address of the PC.
IP address of the equipment. If it is not pointed out, it can be get from the IP address of the PC substracting one (into the example: if the IP address of the PC is: 139.132.223.121, the IP address of the equipment is: 139.132.223.120).
5-35
5.5.2.2
Status window of the connection

In Windows 2000/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.56, Fig. 5.57). He can access to such a 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.56
Status window of the connection in Windows 2000

IP address of the equipment. If it is not pointed out, it can be get from the IP address of the PC substracting one (into 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.
Fig. 5.57
Status window of the connection in Windows XP
IP address of the equipment. If it is not pointed out, it can be get from the IP address of the PC substracting one (into the example: if the IP address of the PC is: 150.166.153.203, the IP address of the equipment is:150.166.153.202).
IP address of the PC.
5-36
5.5.2.3
The ipconfig command

The ipconfig command allows to detect the IP address and the local equipment (Fig. 5.58). This command is executed by the DOS shell.
Fig. 5.58
The ipconfig command
IP address of the PC on the PC equipment network. To get the IP address of the equipment, subtract 1 (in the example, the IP address of the equipment is: 192.168.255.3).
5-37
5.5.2.4
The route print command

The route print command allows to detect the IP routing parameters (Fig. 5.59). This command is executed by the DOS shell.
Fig. 5.59
The route print command
IP address of the PC on the Ethernet network. IP address of the PC on the PC - equipment network. To get the IP address of the equipment subtract 1 (in the example, the IP address of the equipment is: 192.168.255.3).
This value indicates the PC local interfaces.
5.5.2.5
The route add command

The route add command allows to change the IP routing parameters as, for istance, to force the serial line use for a specific IP address. This command is executed by the DOS shell. The easier mode to use this command is the following one: route add <IP_address_to_reach> <gateway_to_be_used>. For instance, if the IP address of our PC on the PC - equipment network is 160.160.160.161 (and, then, the address of the local equipment is 160.160.160.160) and the address of the remote equipment to be reached on the serial line (and, then, through the local equipment) is 150.150.150.150, it is necessary to use the following command: route add 150.150.150.150 160.160.160.161
5-38
5.5.2.6
WinTrace utility of the Frontier Technologies software

The WinTrace utility is available only if the Frontier Technologies software is installed. This utility allows to detect the route of the packets forwarded to a specific address (Fig. 5.60). To run this utility, it is necessary to execute the following procedure: Start Programs Frontier Technologies WinTrace
Fig. 5.60
WinTrace utility
5-39
5.5.2.7
The tracert command

The tracert command allows to detect the route of the packets forwarded to a specific address (Fig. 5.61). This command is executed by the DOS shell. It is necessary to specify the destination IP address: tracert IP_address.
Fig. 5.61
The tracert command
5-40
5.6 Troubles in the Dial-up Connection to the Local Equipment

5.6.1 Local equipment not reacheable using the default local IP address
If all the following conditions are present: connection to the local equipment on serial line (dial-up connection) presence, at the same time, of at least two interfaces of the PC (e.g.: Ethernet network card and dial-up connection) using the TCP/IP protocol local equipment with IP address correctly configured,
the local equipment can result not reachable using the default local IP address (192.168.255.3). In this case, it is not possible to use the default local map. Then it is necessary to create by means of the Net Builder program (refer to the Cap. 7 "OPERATING GUIDE OF NETBUILDER"), a new map with reference to the real IP address of the local equipment (par. 5.6.3).
5.6.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. The execution of the Local Craft Terminal program causes a permanent data stream on the serial line and, then, it keeps always activated the dial-up connection. To keep always activated the dial-up connection, it is advisable to forward a cyclic ping towards the local equipment, using the following command from DOS prompt (Fig. 5.62): ping -t <IP_address> the <IP_address> is the real IP address of the local equipment (par. 5.6.3) and -t is the cyclic execution option. If in Windows NT, the dial-up connection is interrupted for traffic absence, it is necessary to execute the activation procedure of the dial-up connection again (par. 5.3.1). In this case, it is advisable to execute the following procedure to avoid disconnecting newly the cable from the PC serial port: move the mouse on the RAS monitor icon (Fig. 5.63) in the tray area (lower corner on the right of the desktop) and click on the right push-button the dial-up menu is displayed (Fig. 5.64); start up again the connection procedure selecting Radio connection under Dial.
5-41
Fig. 5.62
ping t command
Fig. 5.63
RAS monitor icon in Windows NT
RAS monitor icon
5-42
Fig. 5.64
Reset of the dial-up connection in Windows NT
5.6.3
5.6.3.1
Detection of the local equipment IP address

Detection of the local equipment IP address in Windows NT
In Windows NT, the detection of the local equipment IP address is possible by means of the RAS monitor window (par. 5.5.2.1). The procedure to be executed is the following one: Activate the dial-up connection on serial line between the PC and the local equipment (par. 5.3.1). After having activated the connection, click on the RAS monitor icon (Fig. 5.65) present into the tray area (lower corner on the right of the desktop). It is displayed the Dial-up Networking Monitor window (Fig. 5.66). Click on Details. It is displayed the Details window (Fig. 5.67). This window shows under TCP/IP, the IP address of the local equipment (Dial-up Server value) and the IP address of the PC F interface (IP Address value).
The detection of the local equipment IP address, after having activated the dial-up connection on serial line (par. 5.3.1), can be executed also by means of the ipconfig (par. 5.5.2.3) and trace print (par. 5.5.2.4) commands from DOS prompt.
5-43
Fig. 5.65
Detection of the local equipment IP address in Windows NT (1/3)
RAS monitor icon
Fig. 5.66
5-44
Fig. 5.67

IP address of the local equipment
5.6.3.2
Detection of the local equipment IP address in Windows 2000/XP

In Windows 2000/XP the operator can know the IP address of the local equipment connected with the serial line through the status window of the connection (par. 5.5.2.2).
5-45
LA
N
5-46 LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003
PA
6 - OPERATING GUIDE OF LOCAL CRAFT TERMINAL
6 OPERATING GUIDE OF LOCAL CRAFT

TERMINAL
6.1 Functions of Local Craft Terminal
The Local Craft Terminal program provides the Element Manager function and allows the management of the equipment relevant to a radio link and/or of the local radio equipment. The graphical interface for the access to the equipment is constituted by a map, created by means of the NetBuilder tool. The Local Craft Terminal program is able to manage maps with a maximum of three NEs. LCT uses, as management application protocol, the TNMP proprietary protocol implemented over the TCP/IP protocol. The system supports two versions of the TNMP protocol: base TNMP and extended TNMP. On the contrary of the preceding version (TNMP), the most recent version (extended TNMP) supports the time references of the events. In case of equipment with OSI class (equipment with TNMP protocol implemented on OSI stack), it is possible to execute from LCT only the connection and the management of the local equipment. The Local Craft Terminal program allows the execution of the following main functions: to open and to display the map for the connection to the NEs to set the connection with the NEs, activating such a connection at the map opening to execute, by means of a cyclic polling, the monitoring of the NEs connection and alarm status to access to the single NE, that is to load the relevant configuration files and operating menus to configure and to control each single NE, through the relevant operating menu to manage the security access (Security) to the NEs, that is to allow the access only to authorized users by means of passwords.
LCT does not know nothing before concerning the equipment to be managed, but it dynamically loads all the necessary information from the equipment plug-in that constitutes the configuration and control application program. At the map opening, the Local Craft Terminal program automatically detects the type of the present equipment, if the relevant plug-in has been installed. If it is present a particular type of radio equipment and the relevant plug-in hasnt been installed, the Local Craft Terminal program detects its presence, but it is not able to recognize it and then to manage it.
6-1
It is possible to execute the installation of a plug-in for every type of radio equipment, also after the installation of the Local Craft Terminal program. In such a case, if the Local Craft Terminal program is already running, it is necessary to exit from the program and then to start-up it again, to allow the loading of the new plug-in.
6.2 User Interface

The Local Craft Terminal program is provided with a Windows typical user interface. The program screen page (Fig. 6.1) consists of the following elements: title bar menu bar status bar displaying area tool bar scroll-bars.
For the functions executed by the push-buttons of the mouse, refer to the default configuration of Windows. Fig. 6.1 User Interface of the Local Craft Terminal program Menu bar Tool bar Title bar Vertical scroll bar
Map
Displaying area NE icon Status bar Horizontal scroll bar
6-2
6.2.1
Title bar
The title bar always displays the name and the icon of the program.
6.2.2
Menu bar
The menu bar displays the following basic program menus: File Options Window Help.
When a map has been opened, the menu bar displays also the Net-Element menu that contains the menus of the NEs present on the map. The menus are Windows type ones. To select an option into a menu, it is necessary to position the mouse on the menu, to press the left-hand push-button of the mouse and, keeping it pressed, to select the desired option; then release the left-hand push-button of the mouse to activate the selected option.
6.2.3
Status bar
The status bar displays messages and informations useful for the operator (the meaning of the menu commands, the status of the program or of the function actually on progress, the details concerning the fields of the configuration and control windows, etc.).
6.2.4
Displaying area
The maps and the windows, opened using a command or selection, are displayed into the displaying area. It is possible to display more windows at the same time, even if they belong to different NEs. The title of a window is always preceeded by the name/IP address of the NE to which it is referred. The fields of the NE configuration and control windows can be of the following two types: read only: files concerning the status and alarm signals or not modifiable parameters read-write: fields concerning modifiable parameters.
Its possible to modify the values of the fields, depending on the user class used to access to the NE: Read Only: it is possible only to read the values of the fields, not to change them Read Write: it is possible to change the values of the fields with the exception of the ones relevant to the windows reserved for the Admin user class Admin: it is possible to change the fields of every window.
Usually, it is possible to execute the following operations on the read-write type fields:
6-3
Data entry (numbers or strings) Position the mouse on the desired field and click; the window FIELD EDITING (Fig. 6.2) is displayed with a box that lists the available values for the selected parameter. Position the mouse on the desired value and click for selection; click on OK button to confirm the selection Data entry (numbers or strings) Position the mouse on the desired field and click; the window FIELD EDITING (Fig. 6.3) is displayed with a box for the data entry. Position the mouse on the box and click for selection; use the keyboard to enter the data into the box and click on OK button to confirm the entry.
At the opening of a window, the values to be displayed into the fields are get by the NE. Some fields can point out, by means of blinking, the modification of their value. It is possible to stop the blinking through the F3 push-button. If the value of a field hasnt been get by the NE yet, the field can not be modified. When the value of a field is modified, the request for modification is sent to the NE. Then the program waits for the NE answer. If the NE rejects the modification, an error message is displayed. If the field is a numeric type one, the program, before sending the request for modification to the NE, executes a check on the validity range of the current parameter. If the value is out of the validity range, an error message is displayed. The messages concerning the windows and the objects inside the windows (fields, push-buttons) are displayed in the status bar. A special management characterizes the action windows used to execute some actions on the NEs and the FIELD EDITING windows used for the writing of the fields. Action windows Every action window is open at the beginning in reading mode (unchangeable fields); two push-buttons are available (Modify and Cancel). If the current user class, connected with the NE, allows it, when the user clicks on Modify push-button, the program executes switching of the action window to writing mode (changeable fields); two push-buttons are available for the execution command and for the interruption of the action (OK and Cancel). It is possible to open in writing mode only one action window at a time for each NE. Then, when an action window has been opened in writing mode, the possibility to modify the fields belonging to other windows of the same NE is disabled. FIELD EDITING windows Each FIELD EDITING window is provided with two push-buttons (OK and Cancel). It is possible to open only one FIELD EDITING window at a time. Then, when a FIELD EDITING window has been opened, the program can execute actions on the window only.
Fig. 6.2
Example of window for the selection of a value
6-4
Fig. 6.3
Example of window for the data entry
6.2.5
Tool bar
The tool bar displays the icons of some push-buttons which act as shortcuts for choosing menu commands directly, without passing through the window menus. Tab. 6.1 shows the available push-buttons.
Tab. 6.1
Tool bar Icon Description
Colors command of the Options menu
Field Status command of the Options menu
Using help command of the Help menu
6.2.6
Scroll bars
The scroll-bars allow vertical and/or horizontal scrolling of the map displaying area.
6.2.7
LCT map
The system represents each equpment of the map by means of an icon and the name/IP address that identifies the equipment type. The Local Craft Terminal program is able to manage maps with a maximum of three NEs and that do not contain sub-maps. The Local Craft Terminal program is provided with the standard map for the connection with the local equipment (LocalNE.map) and with other three maps for the several connection modes with the local equipment: LneTnmpE.map: configuration for the connection with the local equipment with TNMP extended protocol LneTnmp.map: configuration for the connection with the local equipment with TNMP base protocol
6-5
LneAuto.map:
configuration for the connection with the local equipment with automatic selection of the protocol (this mode has to be used when it is not known the protocol supported by the equipment.
By default, the LocalNE.map standard map is configured for the use of the TNMP extended protocol. It is advisable to apply to the standard map the configuration of the map relevant to the more frequently used connection mode. The operator can couple a background drawing with the map. The background drawing (.BMP file) is not contained into the map file but it is always recalled at the map opening as an external connection. The file of the background drawing is coupled with an absolute path or with a relative one according to the folder where the file itself is contained. If the background drawing is into the Map folder of the LCT maps (usually in the English version of Windows: ...\Program Files\Radio Management\LCT\Map) or into one of its sub-folders, the system couples with it a relative path, vice versa the system couples with it an absolute path .
6-6
6.3 Local Craft Terminal Start-Up

Before starting-up the Local Craft Terminal program, it is necessary to check the activation of the connection between the LCT PC and the local radio equipment.
6.3.1
Program start-up
To start-up the LCT program, it is necessary to execute the following command (Fig. 6.4): Start Programs Radio Management 5.0 Local Craft Terminal
Fig. 6.4
Programs menu with Radio Management 5.0 folder (example)
At the program start-up, the system displays the program presentation window (Fig. 6.5) and, after some seconds, the base window (Fig. 6.6). If the user clicks over the presentation window, he can close in advance the presentation window itself and pass immediately to the base window. Fig. 6.5 Program starting-up presentation window
6-7
Fig. 6.6
Base window of the Local Craft Terminal program
6-8
6.3.2
Opening of the map

After having started the Local Craft Terminal program, it is necessary to open the map using the Open Map command of the File menu (refer to par. 6.5). Before opening the map, the Local Craft Terminal program checks its congruence (the map hasnt to contain more than three NEs). Each NE of the map is represented through an icon and the name/IP address that identifies the equipment type. At the map opening, the Net-Element menu is added in the menu bar. Inside this menu, one menu for each NE of the map is created. At the map opening, the program tries to connect to all the enabled NEs. For each NE, the connection phase is executed as described below: if an error during the communication is detected (for instance: not existing NE), an icon showing that the NE is not connected is displayed (not intentional disabling status) if the connection is successfully executed, the program tries to recognize the radio equipment type: if the recognition is successfully executed (NE On-Line), the relevant configuration file is loaded and a pre-defined icon showing the radio equipment type is displayed; then, into the corresponding NE menu, the operating menu that allows the NE configuration and control is added if the recognition is not successfully executed (for instance: radio equipment not supported by LCT), the system displays an icon of unknown equipment showing that the radio equipment type is not supported.
The probable causes of the not executed detection concerning the type of radio equipment can be the following ones: LCT version that does not support the type of radio equipment; incompatibility between the LCT version and the one of the equipment plug-in; absence or wrong installation of the equipment plug-in. If for some reasons the communication between LCT and NE is interrupted, the system automatically disconnects the NE. The program cyclically executes an automatic connection attempt towards the NEs that actually are in the not intentional disabling status. It is always possible to know the cause of the disconnection for a NE. Positioning the cursor on the icon of a disconnected NE, a message is displayed into the status bar showing the reason for the disconnection. The status of a intentional disabling for a NE is signalled through a proper icon (see Cap. 7 "OPERATING GUIDE OF NETBUILDER").
6-9
6.3.3
Parameters on the control line of the Local Craft Terminal program

It is possible to start-up the Local Craft Terminal program by inserting on the control line the following parameters: -map <name_map> At the opening of the map displayed into the <name_map> field, all the not disabled NEs are connected and sequentially opened. -nologo It allows preventing the displaying of the presentation window (logo) at the program starting-up.
Each parameter can be written without distinction in capital letters or in small letters and it can be preceded by the character - or /.
6.4 Security
The Security allows the access to NE only to the authorized users. Each user is characterized by a user class and by a password. The user class defines the access privileges to the NE. The Security configuration (enabling status and password) is specific for each NE and it is stored into the NE memory.. The NE Security has to be enabled if the accesses of two or more managers are possible at the same time (e.g.: Net Viewer and LCT). The system provides the following three different user classes: Read Only: it allows the access to the functions in reading mode only; Read Write: it allows the access to the functions as in reading mode as in writing one, with the exception of the functions reserved for the Admin user class. For such functions, the access is in reading mode only; with details, the Security management is reserved for the Admin user class only Admin: it allows the access to all the functions as in reading mode as in writing one,
For the NE Security, the default passwords defined at factorys are the following ones: Admin user class: SYSMANAGER Read Write user class: READWRITE Read Only user class: READONLY. It is possible to set/change the Security configuration by the NE operating menu, only if the access is executed using the Admin user class. 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 need for the insertion of the password. The only restriction is that it is not possible to change the settings relevant to the Security (enabling status and password). The Security enabling prevents the connection to a NE
6-10
of more operators at the same time with the Admin or Read Write user class, preventing conflicts and configuration errors. If the NE security has been disabled, at the next enabling it gets newly the preceding set passwords.
6.5 File Menu

The File menu (Fig. 6.7) allows to open and to close a map, and to exit from the program. Between the Close Map and Exit commands, the system displays the names of the last four opened maps in such a way to allow a quick selection of the maps themselves. Fig. 6.7 File menu
6.5.1
Open Map
The Open Map command allows opening the LCT map (Fig. 6.8). The files concerning the maps have the .MAP extension. A map is not open, if it contains more than three NEs. In this case, an error message is displayed (Fig. 6.9). The Open Map command is active only when no map has been opened.
Fig. 6.8
Window for the Open Map command of the File menu
Fig. 6.9
Error message caused by the opening of a map with more than three NEs
6-11
6.5.2
Close Map
The Close Map command allows to close the current map. The map closing causes the disconnection of the NEs. At the map closing, the system asks for the confirmation (Fig. 6.10), because this operation causes the disconnection of the NEs. The Close Map command is active only when a map is open.
Fig. 6.10
Window for the map closing confirmation
6.5.3
Exit
The Exit command allows exiting from the program. If a map has been opened, at the program exiting, the system asks for the confirmation (Fig. 6.11). The Exit command is always active.
Fig. 6.11
Confirmation window for exiting the program
6-12
6.6 Net-Element Menu

The Net-Element menu (Fig. 6.12) allows managing the NEs of the map and it is present only if a map is open. This menu contains the NE menus that compose the map. Each NE menu (Fig. 6.13) is specified by the NE name/IP address and it is composed by a pre-defined part, that contains the NE commands, and by a dynamic one that is constituted by the NE operating menu. The dynamic part depends on the type of the radio equipment and it is loaded only at the NE opening (loading of the plug-in for the NE management). For the description of the operating menu refer to the operating guides of the plugs-in relevant to the radio equipment. The NE menu is activated clicking through the R.H. push-button of the mouse on the icon of the desired NE (Fig. 6.14). Fig. 6.12 Net-Element menu
Fig. 6.13
NE menu
Menu with closed NE
Menu with open NE
Fig. 6.14
NE menu activated pressing the right-hand push-button of the mouse
Menu with closed NE
Menu with open NE
6-13
6.6.1
Open
The Open command allows to open the NE and to load the corresponding configuration file. This operation adds the corresponding operating menu for the radio equipment configuration and control to the NE menu. It is possible to open the NE also clicking twice on the relevant icon. The Open command is activated if the NE is On-Line; it is deactivated if the NE is disabled or it is already open. If the NE Security is enabled, the system allows three user classes: Read Only, Read Write and Admin (Fig. 6.15). If the NE Security is disabled (Fig. 6.16), the system allows also the Anonymous user class that does not need for any password and has always the same prerogatives of the Read Write class. If the user selects Synchronization, he can synchronize the date and the time of the NE with the ones of the PC over which LCT is currently running. On the contrary, the synchronization feature is disabled. The system synchronizes the NE only if the user has the rights sufficient for the execution of the synchronization procedure (Read Write or Admin); for instance, with Synchronization check-box selected, and login as Read Only, the system will not synchronize the NE.
Fig. 6.15
NE opening window with Security enabled
Fig. 6.16
NE opening window with Security disabled
6.6.2
Close
The Close command allows closing the NE. This operation causes the closing of all the NE configuration and control windows and the removal of the operating menu from the NE menu. The Close command is activated only if the NE has been opened.
6-14
6.7 Options Menu

The Options menu (Fig. 6.17) allows setting the options used into the configuration and control windows of the NEs. Then, it is provided with the commands (bring at front, bring at background) relevant to the window of the map. Fig. 6.17 Options menu
6.7.1
Colors
The Colors command allows specifying the displaying colour used into the map and to the windows according to the severity level. Into the COLOR SELECTION window (Fig. 6.18), that is opened using the Colors command, it is possible to select the colour to be associated to each level of severity. Two proper columns (Field Sample and Icon Sample) show the displaying layout of the colours for the fields and for the icons. Tab. 6.2 shows the default configuration of the colours.
Tab. 6.2
Default color configuration Severity disconnected normal test warning minor major critical grey green cyan yellow orange red magenta Colour
To change the current configuration of the colours, execute the following procedure: Select Colors in the Options menu (Fig. 6.17); the COLOR SELECTION window is displayed (Fig. 6.18): it shows the actual configuration of the colours. Click twice on the colour to change; the Color window is displayed (Fig. 6.19) that shows the current palettes of the colours (Basic colors and Custom colors). Select the desired colour from the palettes of the colours and click on OK button to confirm. Change eventually other colours executing again for each colour to be changed the operations pointed out at the preceding step. Exit from the COLOR SELECTION window (Fig. 6.18), clicking on OK button to apply and activate the new configuration of the colours.
It is possible also to define some new customized colours not present into the actual palettes of the colours:
6-15
into the Color window, click on Define Custom Colors (Fig. 6.19); it is displayed the map of the colours (Fig. 6.20) set the new colour; then, it is possible to add the new colour into the palette of the customized colours (Custom colors) clicking on Add to Custom Colors.
It is always possible to reset the default configuration of the colours clicking on Default into the COLOR SELECTION window (Fig. 6.18). Fig. 6.18 COLOR SELECTION window
Fig. 6.19
Color window
Fig. 6.20
Color window to define the customized colours
6-16
6.7.2
Field Status
The Field Status command allows specifying the strings of special characters to be used to signal the abnormality statuses of the fields relevant to the parameters into the NE configuration and control windows. Into the FIELD STATUS DISPLAY SELECTION window (Fig. 6.21), that is opened using the Field Status command, it is possible to select the string to be associated to each field status. Click on the box of each field status to display the list of the available strings (Fig. 6.22). It is always possible to reset the default configuration of the strings relevant to the field status signalling clicking on Default. Tab. 6.3 shows the default configuration of the strings for the signalling of the field statuses.
Tab. 6.3
Default configuration of the strings for the signalling of the field statuses Field status generic error not ready not configured unknown out of range -----------???????????? \\\\\\\\\\\ String ############
If some changes have been introduced to the configuration of the strings for the signalling of the field statuses, exit from the FIELD STATUS DISPLAY SELECTION window (Fig. 6.21) clicking on OK button to apply and activate the new configuration. Fig. 6.21 FIELD STATUS DISPLAY SELECTION window
Fig. 6.22
Selection of the strings for the signalling of the field status
6-17
6.7.3
Move Map to Top

The Move Map to Top command allows to bring the window of the map in foreground, above all the actually open windows.
6.7.4
Move Map to Bottom

The Move Map to Bottom command allows to bring the window of the map in background, below all the actually open windows.
6.8 Window Menu

The Window menu ( Fig. 6.23) allows the typical management of the Windows open windows. Fig. 6.23 Window menu
6.8.1
Cascade
The Cascade command manages all the open windows overplacing and displacing them in such a way to let visible the menu bar of each window. The current window is brought in foreground. This function is inhibited when the number of open windows is too high; in fact, in this case the function itself would be really unusable.
6.8.2
Tile
The Tile command manages all the open windows placing them side by side. This function is inhibited when the number of open windows is too high; in fact, in this case the function itself would be really unusable.
6.8.3
Arrange Icons
The Arrange Icons command reduces all the open windows to icon and it orders them starting from the lower left-hand corner.
6.8.4
Close All
The Close All command closes all the open windows.
6-18
6.9 Help Menu

The Help menu (Fig. 6.24) allows displaying the useful information concerning the use of the Local Craft Terminal program and of the managerment application programs relevant to the installed equipment plugs-in. On the equipment windows, the help is a context sensible type one, that is if the user presses the F1 push-button, the system directly opens the help relevant to the current window. Fig. 6.24 Help menu
6.9.1
Contents
The Contents menu is automatically configured and it contains the all the available help files: one help file exists for the Local Craft Terminal program and one help file exists for each type of equipment of which it has been loaded the relevant management application program (plug-in).
6.9.2
Using Help
The Using Help command allows displaying information concerning the help itself.
6.9.3
About
The About command allows displaying information concerning the version actually used of the Local Craft Terminal program (Fig. 6.25).
Fig. 6.25
About Local Craft Terminal window (example)
6-19
6.10 Menu of Window

If the user clicks, by means of the mouse R.H. push-button, into a window, the system opens a menu (Fig. 6.26), that contains the following commands: Print to file Help.
The window menu is not present on the action windows, on the FIELD EDITING windows and on the windows of the external application programs. Fig. 6.26 Menu of window
6.10.1
Print to file
The Print to file command allows to record the contents of the current window on a file, specifying the desired name and path (Fig. 6.27). Usually the Print to file command records the alarm status and the configuration of the current window. However, the Print to file command does not execute a simple hard-copy of the window; in fact, while into the window the program displays a short name of the alarms and of the configuration parameters, it points out into the file the corresponding descriptions (extended names) recorded by means of Print to file. The inventory data are not recorded by means of the Print to file command but by means of the application of inventory data reports (par. 6.12.4). If the user tries to record the inventory data through the Print to file command, the system displays an unavailability information message (Fig. 6.28). If into the destination folder a file with the same name already exists, the system asks to confirm the over-writing operation of the existing file (Fig. 6.29). After its creation, the file is automatically opened, for its displaying and printing, using the base editor (Notepad or WordPad) of the system (Fig. 6.30).
Fig. 6.27
Window for the Print to file command of the file menu
Fig. 6.28
Unavailability information message window
6-20
Fig. 6.29
Window for the file over-writing confirmation of the Print to file command
Fig. 6.30
Recording file of the window data
6.10.2
Help
The Help command allows directly opening the corresponding help of the current window. The Help command has the same function of the F1 key, that is it allows the support of the context-sensible help function.
6-21
6.11 NE Applications
LCT implements into the menu of each NE (Fig. 6.3) the following applications if such function are supported by the NE plug-in: History Alarms List.
6.11.1
History
The History menu allows the recording of the events (alarms, status changes, etc.) concerning the equipment functioning The History menu provides following commands (Fig. 6.31): Rec: it allows executing the recordings of the events. Stop: it allows stopping the current recording; the command is active only when the recording is on progress. View: it allows displaying the events of the current recording; the command is active only when the recording is on progress. Last: it allows recalling the displaying of the last recording executed; the command is active only when at least one recording has been executed.
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 command of the History menu) STOP: automatic closing of the recording at the end of the set recording time. Fig. 6.31 History menu
The recordings are saved on a file to allow possible successive analysis and it is possible to use every text editor to open a recording file and to display its recorded events. To realize a recording, it is necessary to execute the following procedure: Select Rec in the History menu (Fig. 6.31). The HISTORY window (Fig. 6.32) is displayed.
6-22
Click on Browse and specify the file name and the relevant path where the events have to be stored (Fig. 6.33). If a file with the same name already exists in the directory, the confirmation for overwriting the existing file is required (Fig. 6.34). Set the value of Min buffer lenght that is the minimum number of events that can be displayed into the window relevant to the View command. The minimum allowed value is 100. Set beginning and ending date and time of the recording. Start the recording clicking on Start (Fig. 6.32). Into the History menu the Stop and View commands are activated (Fig. 6.31); then, to point out the status of recording on progress, the system displays a small green square on the NE icon (Fig. 6.35) It is always possible when the recording is on progress to execute the following operations: to stop the recording selecting Stop in the History menu (Fig. 6.31) to display the events into the HISTORY window (Fig. 6.36) selecting View in the History menu (Fig. 6.31). At the end of recording period, Stop and View commands into the History menu (Fig. 6.31) become disabled, while Last command becomes active, if it was previously deactivated. Select Last in menu History (Fig. 6.31) to show the events of the last recording (Fig. 6.37) with system base editor (WordPad or Notepad).
Fig. 6.32
Recording of the events (1/6)
Fig. 6.33
6-23
Fig. 6.34
Fig. 6.35
Indication of recording on progress
Fig. 6.36
Fig. 6.37
6-24
6.11.2
Alarms List
The Alarms List application program allows to display every type of alarm and/or fault currently present on the equipment, into a single ALARMS LIST window (Fig. 6.38).
Fig. 6.38
ALARMS LIST window
6.12 Common Applications

LCT program provides the integration of common applications into the operating menus of the NEs. The common application available into the menu of a NE depend as on the equipment type as on the SVR of the relevant plug-in. The common applications available for the several supported equipment types are the following ones: date and time of the NE manual setting loading/storing of the NE configuration file recording on file of the NE performances report of the NE inventory data telemeasurement of a NE operating parameter download via FTP of the unit software.
6-25
6.12.1
Manual setting of date and time

The manual setting of date and time is meaningful only on the NEs for which it has been disabled the synchronization. If for the NE the synchronization has been enabled, the manual setting of date and time will be overwritten at the next synchronization. The function for the date and time manual setting is available for all the supported radio equipment types. The date and time become particulary important during the execution and the analysis of the measures and of the recordings on the equipment. In the case of change of date and/or time the NE performance windows are not significant until the end of the polling operation. Than, is necessary to wait some instants (until the windows refresh), before to proceed to the reading or to the recording of the performances. Execute the following procedure to update date and time: Run, from the NE menu, the application for the date and time setting (usually the Date and Time command). The NE Date and Time window is displayed (Fig. 6.39). In this window, it is possible to check (Ne current time row) and/or update (Ne new time row) the equipment date and time.
The Time Mode parameter points out the timing mode set for the synchronization: Local mode: NE synchronized on the local time of the LCT PC. Set the new date and time into the boxes on the NE new time row. The Apply New Time software push-button is activated (Fig. 6.40). Click on Apply New Time (Fig. 6.40) to apply the date and time displayed in the Ne new time row to the equipment (Ne current time row). The command execution must be confirmed (Fig. 6.41), because the date and time modification affects the performance monitoring. After data and time setting, the push-button Apply New Time is disabled (Fig. 6.42).
It is possible to apply directly on the equipment the current date and time of the local PC clicking on Apply PC Time (Fig. 6.39). The system asks for the confirmation of the command execution (Fig. 6.41), because the change of the date and time affects the performance monitoring. Fig. 6.39 Date and time setting (1/4)
6-26
Fig. 6.40
Date and time setting (2/4)
Fig. 6.41
Fig. 6.42
6.12.2
Loading/storing of the NE configuration file

The loading/storing function of the NE configuration file is available only for some supported radio equipment types. The application menu (usually Edit NE) provides the following commands: Copy: storing the configuration parameters of the equipment on a file Paste: equipment configuration by means of the parameters present into the NE configuration file.
The use of NE configuration files, stored on the PC has two functions: to make available backup copies of the equipment configuration, to allow a quick reset in case of loss of the configuration to make available several base configurations, to make easier and to reduce operations to configure the equipment.
6-27
6.12.2.1
Storing the configuration on a file (Copy)

Select Copy in the application menu (available into the NE menu). The COPY NE CONFIGURATION window (Fig. 6.43) is displayed. Click on Browse and specify the name of the destination file and of the relevant path, where the equipment configuration has to be stored (Fig. 6.44). If into the destination folder it already exists a file with the same name, the system asks for the confirmation before overwriting the existing file (Fig. 6.45). The Start software push-button (Fig. 6.46) is activated in the COPY NE CONFIGURATION window. Click on Start. The software push-button switches from Start to Abort and it starts the storing phase with the displaying of the relevant messages (Fig. 6.47). It is always possible to stop the storing clicking on Abort . At the end of the storing phase, the system deactivates the Abort push-button and the message displaying ends with Finished (Fig. 6.48). Click on Close (Fig. 6.48) to close the COPY NE CONFIGURATION window.
Fig. 6.43
Storing the configuration on a file (1/6)
Fig. 6.44
Fig. 6.45
6-28
Fig. 6.46
Fig. 6.47
Fig. 6.48
6-29
6.12.2.2
Loading of the configuration file (Paste)

Select Paste in the application menu (available into the NE menu) The PASTE NE CONFIGURATION window (Fig. 6.49) is displayed. Click on Browse and specify the name of the source file and the relevant path, where the configuration to be loaded (Fig. 6.50)is stored. The Start software push-button (Fig. 6.51) is activated in the PASTE NE CONFIGURATION window. Click on Start. The software push-button switches from Start to Abort and it starts the loading phase with the displaying of the relevant messages (Fig. 6.52). The user can always stop the operation on progress clicking on Abort. At the end of the loading phase, the system deactivates the Abort push-button and the message displaying ends with Finished (Fig. 6.53). Click on Close (Fig. 6.53) to close the PASTE NE CONFIGURATION window.
Fig. 6.49
Loading of the configuration file (1/5)
Fig. 6.50
6-30
Fig. 6.51
Fig. 6.52
Fig. 6.53
6-31
6.12.3
Performance recording
The measurements of performances that can be recorded on a file changes according to the radio equipment type. It is necessary to have at disposal the Excel program to display, as a table, the performances recorded on file. In the case of change of date and/or time the NE performance windows are not significant until the end of the polling operation. Than, is necessary to wait some instants (until the windows refresh), before to proceed to the reading or to the recording of the performances. The procedure for the performance recording on file is the following one: Run, from the NE menu, the performance recording application. The Performance Monitoring window opens (Fig. 6.54). Set the date and the time for the beginning and the end of the recording. Click on Browse and specify the file name and the relative path where recorded data must be stored (Fig. 6.55). Start the recording procedure clicking on Start; If a file with the same name already exists in the destination folder, the user is asked for the confirmation to overwrite the existing file (Fig. 6.56). At the starting-up of the recording phase, Quando inizia la fase di registrazione, the push-button switches from Start to Show (Fig. 6.57). When the recording procedure is on progress, it is always possible: to stop in advance the searching clicking on Cancel; the user is asked for confirmation of the stopping of the recording procedure (Fig. 6.58) to open Excel and to display the performance data clicking on Show (Fig. 6.59); the push-button Show becomes active only when there are some performance data. At the end of the searching period: the system automatically runs the Excel program to display the performance data through a table (Fig. 6.60) the system displays the EXIT window (Fig. 6.61); click on OK to close the application program for the performance recording. If it is desired, save from Excel the recording data.
Fig. 6.54
Performance recording (1/8)
6-32
Fig. 6.55
Fig. 6.56
Fig. 6.57
Fig. 6.58
Fig. 6.59
6-33
Fig. 6.60
Fig. 6.61
6.12.4
Inventory data report

The report function is available for all the supported equipment type and it allows to report the unit inventory data, storing in a single file. It is possible to use whatever text editor to open the report file and to display the inventory data. The reporting procedure for inventory data of the units is the following: Run, from the NE menu, the application for the report of the inventory data (usually the Report command). The Inventory Data window is displayed (Fig. 6.62). If the file displayed by default into the Inventory file row already exists, the Show push-burron is activated. Click on Browse and specify the file name and the relevant path, where the inventory data have to be stored (Fig. 6.63). Click on Start; if a file with the same name already exists in this folder, the system asks for the confirmation to overwrite the existing file (Fig. 6.64). The software push-button switches from Start to Stop and it starts the storing phase with the displaying of the relevant messages (Fig. 6.65). It is always possible to stop the storing clicking on Stop. At the end of the storing phase (Fig. 6.66): the message displaying stops on Finished the Stop software push-button is deactivated the Show software push-button is activated.
6-34
Fig. 6.62
Click on Show (Fig. 6.66) to display the report on units inventory data (Fig. 6.67) with the system base editor (WordPad or NotePad). Click on Close (Fig. 6.66) to close the window Inventory Data and exit.
Report of the inventory data (1/6)
Fig. 6.63
Fig. 6.64
Fig. 6.65
6-35
Fig. 6.66
Fig. 6.67
6-36
6.12.5
Telemeasurement
It is possible to execute the telemeasurement of some operating parameters particularly meaningful and to detect the data of the measurement on file for possible successive processing operations. According to the radio equipment type, it can change the type of operating parameter involved into the telemeasurement procedure. It is necessary to have at disposal the Excel program to display the graphical diagram showing the outline of the measured parameter according to the time. To execute the telemeasurement it is necessary to execute the following procedure: Run, from the NE menu, the telemeasurement application (the command changes according to the radio equipment type). The window for the remote measurement setting (Fig. 6.68) is displayed. Set the date and the starting and ending time of the recording operation. Click on Browse and specify the file name and the relevant path where to store the recording data (Fig. 6.69). 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.70). The software push-button switches from Start to Show (Fig. 6.71). During the recording, it is always possible: to display the profile in the elapsed time of the measured parameter, clicking on Show (Fig. 6.71) to stop early the recording procedure clicking on Cancel; the system asks for the confirmation about the interruption of the measurement (Fig. 6.72).
If the recording is closed by clicking on Cancel, the data are saved only in text format (ASCII) and, then, is not possible anymore to obtain the grafic/table in Excel. At the end of the recording period: the EXIT window (Fig. 6.72) appears; click on OK to close the telemeasurement application program the system automatically runs the Excel program to show the measured parameter profile in the elapsed time (Fig. 6.73); its also possible to display the same data in table form (Fig. 6.74). Save by means of Excel, if desired, the recording diagram.
The Excel file must be saved by the user; in wrong case remains only the data in text format (ASCII) and, then, is not possible anymore to obtain the grafic/table in Excel. Fig. 6.68 Telemeasurement (1/8)
6-37
Fig. 6.69
Telemeasurement (2/8)
Fig. 6.70
Fig. 6.71
Fig. 6.72
Fig. 6.73
6-38
Fig. 6.74
Fig. 6.75
6-39
6.12.6
Download via FTP of the unit software

For the NE units provided with management embedded software, it is possible to execute the software download via FTP. The embedded software, of the radio equipment units, is loaded on flash memories; usually there are two flash memory banks, called bank 1 and bank 2. One of these banks is active and the other one in standby. The units are provided with the management software already loaded. The download operation consists of the transfer, via FTP (application program of the IP protocol stack), of the file that contains the software from a PC connected into the network to the standby bank of the interested unit. The download via FTP does not cause any functioning stop of the unit that remains always On Line. As transfer application programs, the system uses, according to the unit type, the FTP Client and the FTP Server of SuperTCP, that are provided with the Local Craft Terminal program. For LCT, the download via FTP can be executed only towards NEs that support the IP protocol (IP class radio equipment). The operating management (download command, bank status switching, address setting) of the download operation can be executed by the same PC on which there is the file to be transferred or by every service PC connected into the network. For more detailed information concerning the download procedure of the unit software, refer to the relevant equipment Manuals.
6-40
7 - OPERATING GUIDE OF NETBUILDER
7 OPERATING GUIDE OF NETBUILDER

7.1 Functions of NetBuilder
The NetBuilder program is a graphical tool for Windows ambient: it allows to create/change maps constituting the graphical interface of the Local Craft Terminal program for connection with equipment (NE). For the creation of a map, it is necessary to execute the following procedure: compose the background drawing, using a common graphical Windows application supporting the .BMP graphical format (e.g. Paintbrush) import into NetBuilder the background drawing of the map apply the NE icons in the predefined positions on the drawing assign the corresponding name/IP address, that has to be a univocal, to each NE save the map with the desired name in a .MAP format file.
NetBuilder implements also the function of Discovery (par. 7.4.6), that allows executing an automatic search of the NEs inside a specified range of IP addresses and saving their IP addresses into a map file. The searching dynamics is the following one and the system repeats it for each IP address comprised into the specified range: the system requires for the TCP/IP connection with the IP address through socket if, withing the pre-defined waiting time, the system detects an error of the socket or it does not receive any answer, it retries for a certain number of times according to the searching parameters the system considers the searching procedure as a failed one if all the attempts towards that IP address have had a negative result; vice versa the system considers the search as a successful one and it creates the icon of the detected NE the system start processing the next IP address.
The automatic searching function: can be applied only towards NEs that support the TNMP protocol (base or extended) on TCP/IP can not be applied towards NEs connected through Proxy.
By means of NetBuilder for LCT, it is possible to create a map with max. 3 NEs.
By default, a map, at its creation, is not associated to any background drawing.
7-1
The program is provided with the standard map for the connection with the local equipment (LocalNE.map) and with other three maps for the several connection modes with the local equipment: LneTnmpE.map: configuration for the connection with the local equipment with TNMP base extended protocol; LneTnmp.map: configuration for the connection with the local equipment with TNMP protocol; LneAuto.map: configuration for the connection with the local equipment with automatic selection of the protocol (this mode has to be used when it is not known the protocol supported by the equipment).
By default, the LocalNE.map standard map is configured for the use of the TNMP extended protocol. It is advisable to apply to the standard map the configuration of the map relevant to the more frequently used connection mode. If the user wants creating a customized local map, the numeric IP address to be assigned is 192.168.255.3, that is the preset and unchangeable address for the local connection of every equipment. The background drawing can be of any type (e.g.: geographical map indicating the location of the various stations, a block diagram showing all the radio link interconnections, etc...). During the composition of the drawing, sufficient space must be left in the position of the NEs to allow subsequent positioning of the corresponding icons, in order to obtain a orderly and readable map. In case of an OSI class equipment (equipment with TNMP protocol implemented on OSI stack), from LCT, it is possible only the connection and the management of the local equipment and then the map has to contain the local NE only. Fig. 7.1 shows an example of map.
7-2
Fig. 7.1
Example of map
7.2 User Interface

The NetBuilder program provides a typical of Windows user interface. The program screen (Fig. 7.2) consists of the following elements: title bar menu bar tool bar scroll bars status bar map displaying frame.
Refer to the default configuration of Windows for the functions of the R.H. and L.H. mouse push-buttons.
7-3
Fig. 7.2
User interface of the NetBuilder program Title bar Menu bar Tool bar Map displaying frame Vertical scroll bar
Displaying frame of the map structure
Horizontal scroll bar
Status bar
7.2.1
Title bar
The title bar always displays the program name: NetBuilder.
7.2.2
Menu bar
The menu bar displays the basic program menus: File Edit Options Window Help.
The menus are of the pop-up type. To select a menu option, position the mouse on the menu, click with the left-hand mouse button and keep it pressed to select the desired
7-4
option; then release the left-hand mouse button to activate the selection option.
7.2.3
Tool bar
The tool bar provides some push-buttons that allow the direct execution of a command without passing through the pop-up menus. Tab. 7.1 describes the available push-buttons.
Tab. 7.1
Tool bar Icon Description
New command of the File menu (par. 7.4.1)
Open command of the File menu (par. 7.4.2)
Save command of the File menu (par. 7.4.4)
New Net-Element command of the Edit menu (par. 7.5.3.1) The insertion push-button of the NEs is activated only if it has already been opened at least one map.
7.2.4
Status bar
The status bar displays the operator helping information regarding the operating status of the program and the meaning of menu commands.
7.2.5
Scroll bars
The scroll bars provide vertical and/or horizontal scrolling of the display frames.
7-5
7.2.6
Map displaying frame

The system provides two map displaying frames: a side frame that displays the tree structures of the open maps; if the operator clicks twice on the map icon, it expands hiding the relevant tree structure a main frame for the displaying of the open maps with their background drawings.
Tab. 7.2 shows the default icons used in NetBuilder to represent the NEs on the maps. Tab. 7.2 Icons for the description of the elements Icon NE icon Description
Disabled NE icon
7-6
7.3 Program start-up

To start the NetBuilder program proceed as follows: Click on the Start button, select in the Programs menu the Radio Management 5.0 NetBuilder command (Fig. 7.3). The initial program screen is displayed (Fig. 7.4); it is now possible to create or modify a map.
Fig. 7.3
Programs menu with Radio Management 5.0 folder (example)
Fig. 7.4
Initial screen of the NetBuilder program
7-7
7.4 File Menu

The File menu (Fig. 7.5) allows to open, to save, to close a map and to exit from the program. Between the commands Save As and Exit, the system displays the name of the last four maps that have been opened, to allow a quick selection of the maps themselves. Fig. 7.5 File menu
7.4.1
New
The New command allows to create a new map. A default name is assigned to the new map and this map is not associated to any background drawing. The New command is always active.
7.4.2
Open
The Open command allows to open a preexisting map (Fig. 7.6); the map files have the extension .MAP. The Open command is always active.
7-8
Fig. 7.6
Window for the Open command of the File menu
7-9
7.4.3
Close
The Close command allows to close the current map (map on which the focus is activated). If the operator closes an empty map without background drawing just immediately after its creation (Close command on an empty map created through the New/New Discovery command and not yet saved), the system does not save the map. It is requested to confirm the saving of the possible modifications applied to the map (Fig. 7.7). The Close command is active only if at least one map has been opened.
Fig. 7.7
Saving confirmation window for the Close command
7.4.4
Save
The Save command allows to save the current map (map on which the focus is activated) with the current name. If the operator saves a new map (Save command on a map created through the New command and not yet saved), the program automatically executes the Save As command, because at the first saving procedure of a map, it is necessary to point out its name and the desired path. The Save command is active if at least one map has been opened. If it has been executed at least one change of the map, at the execution of the Save command, the program assign the .BAK extension to the map file with the same name alredy present on the hard-disk .
7.4.5
Save As
The Save As command allows saving the current map (map on which the focus is activated), specifying the desired identification name and path (Fig. 7.8). By default, the destination is the Map sub-folder of the folder where it is installed LCT (usually in the English version of Windows: ...\Program Files\Radio Management\LCT). If a map file with the same name already exists into the destination directory, the system requests the saving confirmation (Fig. 7.9); and it assigns the extension .BAK to the file with the same name.
7-10
The Save As command is active if at least one map has been opened. As the names of the map files as the name of the folder that contains such files must have the format with 8+3 characters (prefix with max. 8 characters and extension with 3 characters). In case of path with sub-folders, the format with 8+3 characters has to be respected for all the folders into the path. If the destination is a sub-folder of the folder where it is installed the LCT program (usually in the Windows english version: C:\Program Files\Radio Management\LCT), the format with 8+3 characters has to be respected on the relevant path vice versa it has to be respected on the absolut path. Different formats could cause troubles and malfunctionings. Fig. 7.8 Window for the Save As command of the File menu
Fig. 7.9
Saving confirmation window for the Save As command
7-11
7.4.6
New Discovery
The New Discovery command allows creating a map in an automatic mode. The automatic search: can be applied only towards NEs that support the TNMP protocol (base or extended) on TCP/IP can not be applied towards NEs connected through Proxy. At the selection of the command, the program displays the New Discovery window (Fig. 7.10). Into such a window, the operator has to point out the name of the map and the searching range (beginning and final IP address); the total number of the IP addresses must not exceed the value 256x256 = 65536, that is the beginning IP address and the final one must belong to the same network . The operator can set also a limit for the number of NEs to be detected through the automatic search, selecting the Max NE check-box and pointing out, into the relevant numeric field, the maximum number of NEs to be detected; by default, the Max NE check-box is not selected. If the operator selects the Max NE check-box but he does not point out, into the relevant numeric field, the max. number of NEs to be detected, the program displays an error message (Fig. 7.11). After the setting of the searching range, click on OK to start-up the searching phase of the NEs. At the start of the automatic search, the program opens the map and displays a window that shows the progress status of the searching procedure (Fig. 7.12). If the searching procedure gets a negative result, the program displays a message that points out that it has not been found any NE (Fig. 7.13); subsequently the map results empty. At the detection of a NE, the program adds into the map the relevant icon pointed out through the IP address (Fig. 7.14). By means of NetBuilder for LCT, it is possible to create and to manage maps with a maximum of three NEs. The system subdivides the search of the NEs into packets of IP addresses. For each packet, the system executes the searching test at the same time for all the IP addresses of the packet. The system displays the icons of the NEs side by side starting from the L.H. side upper corner of the map (Fig. 7.15); the adding order is from L.H. side to R.H. side and from up side to down side. The system considers the filling area without vertical limits while horizontally such an area is limited by the width of the map window at the starting-up of the searching procedure; the icons go on the next line in such a way to be all visible using eventually only the vertical scrolling bar. When the Max NE option has been enabled, the system automatically stops the search when the number of the detected NEs reaches the specified limit; in this case, the system creates a map with the detected NEs until to reach the specified limit (the map contains a number of NEs equal to the value set into the Max NE field). It is always possible to stop the search, clicking on Stop (Fig. 7.12); in such a case, the system creates a map with the NEs detected until to the stop of the search. When the search has been finished and the system has created the map, it is possible to work on the map (to save/close the map, to set a background drawing, to assign the NE names, ...). The system does not couple any background drawing with the default map. The searching duration depends on the set searching range and parameters (par. 7.6.1).
7-12
During the searching phase, all the NetBuilder options are deactivated, with the exception of the Stop one. The New Discovery option is always activated. Fig. 7.10 New Discovery window
Fig. 7.11
Messagge of unvalid maximum number of NEs
Fig. 7.12
Discovery in progress window
Fig. 7.13
Message of failed searching procedure
7-13
Fig. 7.14
Example of NE icon adding
Fig. 7.15
Example of NE icon displacement
7-14
7.4.7
Exit
IThe Exit command allows to exit from the program. If a map has been created or modified but not saved, it is requested the confirmation at the program exit (Fig. 7.16) and at the map saving (Fig. 7.17). The Exit command is always active.
Fig. 7.16
Confirmation window for the program exit
Fig. 7.17
Confirmation window for the map saving at the program exit
7.5 Edit Menu

The Edit menu (Fig. 7.18) makes available all the commands necessary for the operations on the maps and on the NEs. All the commands in Edit menu are disabled if no map is open. The commands of the Edit menu act over the map or over the objects over which it has been activated the focus. Fig. 7.18 Edit menu
7.5.1
Arrange
The Arrange option automatically allows positioning the icons of the NEs over the current map starting from the upper L.H. side corner. The Arrange option is active only if the map contains some NEs.
7-15
7.5.2
Paste
The Paste option allows pasting over the current map the NE that has been previously cut/copied. The Paste option is active only if it has been cut/copied an object. It is not possible to paste an object if the destination map already contains an object of the same type with the name/address equal to the one of the object to be pasted; in this case, the system displays an error window (Fig. 7.19).
Fig. 7.19
Error window for object copying operation not allowed
7.5.3
New
The New sub-menu (Fig. 7.20) allows the insertion of new NEs. The Net-Element option of the New sub-menu is activated if it has been open at least one map; it is deactivated if it has been selected a NE.
Fig. 7.20
New menu
7-16
7.5.3.1
Net-Element
The Net-Element command allows to insert a new NE into the current map. After this command, the system opens the NE properties window (Fig. 7.21). In a LCT map, it is possible to insert up to a maximum of three NEs.
Fig. 7.21
NE insertion window
The NE configuration parameters are the following ones: NE Name It is the name of the NE. Each NE must have an univocal name It is necessary to insert the name if it has not been specified the IP address of the NE (NE Address); however, it is advisable to specify as the name as the IP address of the NE, also if it is sufficient to set only one of the two parameters. NE Address It is the IP address of the NE. Each NE must have an univocal IP address. It is necessary to set the IP address only if it has not been specified the NE name (NE Name); however, it is advisable to specify as the name as the IP address of the NE, also if it is sufficient to set only one of the two parameters.
LCT can autonomously execute the resolution of the host_names only if the user specifies as the name as the IP address of the NE. If the user specifies the name only, the operating system has to be able to execute the resolution of the host_names (for instance through a DNS Server or through the system hosts file). Disabled If the user selects the Disabled check-box, the system sets to disabled the default status of the NE. A disabled NE is marked on the map through an icon with a small cross and with a different colour (Tab. 7.2). By default, the Disabled check-box is not selected. 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. On the contrary, the synchronization is disabled. By default, the Synchronization check-box is not selected. Protocol It is the application protocol for the management of the NEs; it is possible to have the following options:
7-17
TNMP (base TNMP) TNMP EXT (extended TNMP) TMN Autodetect. The management application protocol depends on the type of radio equipment. If the radio equipment supports both the TNMP protocols, set: Protocol: TNMP EXT. If the user does not know the TNMP protocol used by the radio equipment, set Protocol: TNMP Autodetect; the system executes the automatic detection giving priority to the extended TNMP protocol. The use of TNMP Autodetect causes a slowing down of the NE connection procedure to LCT. After the insertion of a new NE, it is possible, through the mouse, to select and to move the relevant icon on the desired point of the map. Click on OK (Fig. 7.21) to confirm the executed settings. In the following cases, the system displays an error window: Fig. 7.22 it is not specified the name/IP address of the NE (Fig. 7.22) on the map, it is already present a NE with the same name (Fig. 7.23) on the map, it is already present a NE with the same IP address (Fig. 7.24) try to insert a new NE into a map that contains already three NEs (Fig. 7.25).
Error window for name/IP address of NE not set
Fig. 7.23
Error window for NE name duplicated
Fig. 7.24
Error window for NE IP address duplicated
Fig. 7.25
Error window for NE maximum limit
7-18
7.5.4
Background
The Background sub-menu (Fig. 7.26) contents the commands to manage the background drawing of the current map. The files of the background drawings must be .BMP format files. The drawings with .BMP format used as map backgrounds must have a common colour palette; on the contrary, it is necessary to increase the desktop colour depth (using the true color mode, it is possible to avoid every problem). As the names of the bitmap files relevant to the background drawings as the name of the folder that contains such files must have a 8+3 character format (prefix of max. 8 characters and extension of 3 characters). In case of path with subfolders, the 8+3 character format has to be respected for all the folders of the path. If the destination is a sub-folder of the folder where it has been installed LCT (usually in the English version of Windows: ...\Program Files\Radio Management\LCT), the 8+3 character format has to be respected on the relevant path, vice versa it has to be respected on the absolute path. Different formats could cause troubles and malfunctionings. The commands of the Background sub-menu are activated if it has been open at least one map, they are deactivated, if it has been selected a NE. It is important to underline that the background drawing (.BMP file) of a map is not present into the map file but it is always recalled at the map opening as an external link. The system couples with the file of the background drawing an absolute path or a relative path according to the folder where it is present the file itself. If the file of the background drawing is present into the Map folder of the LCT maps (usually in the English version of Windows: ...\Program Files\Radio Management\LCT\Map or into one of its sub-folders, the system couples a relative path, on the contrary it couples an absolute path.
Fig. 7.26
Background menu
7-19
7.5.4.1
Insert
The Insert command (Fig. 7.27) allows to insert a background drawing on the current map. This command is active only if the map does not have a background drawing.
Fig. 7.27
Window for the Insert command of the Background menu
7.5.4.2
Delete
The Delete command allows to delete the background drawing on the current map. This command is active only if the map has already a background drawing.
7.5.4.3
Change
The Change command (Fig. 7.28) allows changing the background drawing of the current map. This command is activated only if the map has already a background drawing.
Fig. 7.28
Window for the Change command of the Background menu
7-20
7.6 Options Menu

The Options menu (Fig. 7.29) allows setting the functioning options of NetBuilder. Fig. 7.29 Options menu
7.6.1
Discovery
The Discovery option allows setting the automatic searching parameters of the NEs (par. 7.4.6); at the command selection, the program displays the Discovery Options window (Fig. 7.30), where the user can set the following parameters: Interval between requests: it is the time range (in seconds) between a TCP/IP connection request and the next one. Protocol: is the application protocol for the communication with the NEs; the following options are possible: TNMP (base TNMP) TNMP EXT (extended TNMP) Autodetect. The application protocol for the communication (base TNMP or extended TNMP) depends on the type of radio equipment. If the radio equipment supports both the protocols, set: TNMP EXT. If the operator does not know the protocol used by the radio equipment set Protocol: Autodetect; the automatic detection is executed giving priority to the TNMP extended protocol.
In some cases, the Autodetect use can cause a speed decreasing of the connection procedure of NE to LCT. Request Packet 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 present into the packet: Max hosts: it is the number of IP addresses relevant to each search packet; # of 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 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).
Click on OK (Fig. 7.30) to confirm the executed settings. The Discovery command is always active.
7-21
Fig. 7.30
Discovery Option window
7.7 Window Menu

The Window menu (Fig. 7.31) makes available the typical commands necessary to manage the Windows open windows. Then, it makes available the dynamic list of the open windows and marks the current one. This function allows to reach easily a window, if there are a lot of open windows at the same time. Fig. 7.31 Window menu
7.7.1
Cascade
The Cascade command positions all the open windows over-placing and phasing them in such a way to let visible the relevant menu bar of each one. The current window is positioned at front. This function is inhibited when the number of the open windows is too high; in fact, in this case, the function would be really not usable.
7.7.2
Tile
The Tile command positions all the open windows side by side. This function is inhibited when the number of the open windows is too high; in fact, in this case, the function would be really not usable.
7.7.3
Close All
The Close All command closes all the open windows.
7-22
7.8 Help Menu

The Help menu (Fig. 7.32) allows displaying the useful information concerning the use of the Net Builder program. Fig. 7.32 Help menu
7.8.1
Contents
The Contents command allows opening the Help of the NetBuilder program.
7.8.2
Using Help
The Using Help command allows displaying information concerning the help itself.
7.8.3
About
The About command allows displaying information concerning the version actually used of the NetBuilder program (Fig. 7.33).
Fig. 7.33
About NetBuilder window (example)
7-23
7.9 Menus of the Mouse Right Hand Push-Button

All the functions of the Edit menu (par. 7.5) can be directly recalled selecting the desired object, by means of the mouse, and clicking on its right-hand push button. According to the selected object, the system displays a specific menu. For the functions of the L.H. and R.H. push-buttons of the mouse, refer to the default configuration of Windows.
7.9.1
Map menu
This menu is activated through one of the following mode: positioning the mouse pointer on an empty point of the main map, not used for NE icons and clicking with the right-hand button positioning the mouse pointer on the main map icon into the map tree structure and clicking with the right-hand button.
The map menu (Fig. 7.34) contents the following command: Fig. 7.34 Arrange (par. 7.5.1) Paste (par. 7.5.2) New (par. 7.5.3) Background (par. 7.5.4).
Map sub-menus and menu
7-24
7.9.2
NE menu
The NE menu is activated through one of the following mode: positioning the mouse pointer on the icon of a NE inside the map and clicking with the right-hand button positioning the mouse pointer on the icon of a NE into the map tree structure and clicking with the right-hand button.
The NE menu (Fig. 7.35) contents the following commands: Fig. 7.35 Properties Cut Copy Delete.
NE menu
7.9.2.1
NE Properties
The Properties command allows setting/changing the properties of the selected NE; at the command execution, the system opens the window of the NE properties (Fig. 7.36). The user can execute such a command also clicking twice directly on the NE icon (into the map or into the map tree structure). For the configuration of the NE features, refer to par. 7.5.3.1.
Fig. 7.36
Window of the NE properties
7.9.2.2
NE Cut/Copy
The Cut and Copy commands allow cutting/copying the NE in such a way to paste it, through the Paste command (par. 7.5.2), on another position.
7-25
7.9.2.3
NE Delete
The Delete command allows deleting the NE. The system asks for the execution confirmation of the NE deleting command (Fig. 7.37). The user can execute the delete command of the selected NE also by means of the Canc key of the keyboard.
Fig. 7.37
Confirmation window for NE deleting
7-26
PRINTED in ITALY
LCT V5.0
Local Craft Terminal
Operating Manual (OMN)
911-360/02A0500
Issue 1, November 2003
LCT V5.0 Local Craft Terminal
D.45
D.55
LCT V5.0
Local Craft Terminal Operating Manual (OMN) Operating Manual (OMN)
911-360/02A0500
LCT V5.0 Local Craft Terminal Operating Manual (OMN)

911-360/02A0500 Issue 1, November 2003
D.25
911-360/02A0500
D.30
LCT V5.0 Local Craft Terminal
LCT V5.0 Local Craft Terminal Operating Manual (OMN) 911-360/02A0500 Issue 1, November 2003
D.20
Operating Manual (OMN)

911-360/02A0500 Issue 1, November 2003

Index

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Index

Uploaded by

Copyright:

Available Formats

Operating Manual

LCT V5.0 Local Craft Terminal OMN

911-360/02A0500 Issue 1, November 2003

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

STATUS OF THE MANUAL

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

STATUS OF THE MANUAL

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

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

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

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

CONFIGURATION OF THE SERVICE PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

4.3.2 4.3.3 4.4

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

OPERATING GUIDE OF LOCAL CRAFT TERMINAL . . . . . . . . . . . . . . . . . . . . . . . . 6.1

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

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

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LIST OF THE FIGURES

LIST OF THE FIGURES

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LIST OF THE FIGURES

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LIST OF THE FIGURES

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LIST OF THE FIGURES

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LIST OF THE FIGURES

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LIST OF THE FIGURES

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LIST OF THE FIGURES

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LIST OF THE FIGURES

LIST OF THE TABLES

LIST OF THE TABLES

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LIST OF THE TABLES

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

1.2 Local Craft Terminal Functions

Supported radio equipment:

Not supported radio equipment: Functions:

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

1.4 Related Manuals

1.5 List of Abbreviations

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

WINS Windows Internet Name Service

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

2 - LCT FUNCTIONS AND FEATURES

2 LCT FUNCTIONS AND FEATURES

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

2 - LCT FUNCTIONS AND FEATURES

2.2 Fault Management

2.3 Configuration Management

LCT V5.0 - OMN 911-360/02A0500 - Issue 1, November 2003

2 - LCT FUNCTIONS AND FEATURES

2.4 Security Management