03 - Server Installation Guide

MINI-LINK Manager 6.
Server Application Installation
E
Copyright
© Ericsson AB 2003 - All Rights Reserved
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing.
Ericsson shall have no liability for any error or damages of any kind resulting
from the use of this document.
8/1553-AOM 901 015/1 Uen B --

MINI-LINK Manager 6.1
Contents
1 MINI-LINK MANAGER Server Application Installation 1

1.1 Requirements 1
1.2 Roadmap 2
1.3 Configuration Of Mini-Link Manager 31
1.4 MINI-LINK Medium Capacity Adaptation Configuration 36
1.5 MINI-LINK HC Adaptation Configuration 36
1.6 MINI-LINK TN Adaptation Configuration 37
1.7 NERA NEW Adaptation Configuration 38
1.8 SNMP MANAGER Adaptation Configuration (SNMP
MANAGER) 39
1.9 SNMP Interface Configuration 39
1.10 TL1 Interface Configuration 41
1.11 BNSI Interface Configuration 41
1.12 FTP Interface Configuration 41
1.13 Local Manager Installation 41
1.14 Uninstall MINI-LINK MANAGER Server 41
1.15 Upgrade NETMAN4.0 To MINI-LINK MANAGER 6.1 44
1.16 Upgrade NETMAN 4.0 Launching MLE Adapters
Stand-alone Installation 44
1.17 Upgrade MINI-LINK MANAGER 5.1 To MINI-LINK
MANAGER 6.1 45
1.18 Ericsson Local Support Information 46
1.19 Appendices 46
8/1553-AOM 901 015/1 Uen B --

8/1553-AOM 901 015/1 Uen B --

1 MINI-LINK MANAGER Server Application

Installation
1.1 Requirements
1.1.1 MINI-LINK MANAGER Distribution Package
Before installing MINI-LINK MANAGER check the content of your MINI-LINK

MANAGER distribution package. It should contain the following items:
• The installation CDs for MINI-LINK MANAGER 6.1 and all third party
products:
CD \ordered item MINI-LINK MINI-LINK MINI-LINK

MANAGER MANAGER MANAGER
Server Client Centralised DB
application application server
MINI-LINK X X X
MANAGER 6.1 CD
(LZY 214 1950/2)
IMA/MINI-LINK X X X
MANAGER 3rd
party products CD
(LZY 214 1456/3)
Users O&M Manual X X X
(LZY 214 1948/2)
NetOp Host 7.5 XOpt
(LXA 119 282/2)
NetOp Guest 7.5 XOpt XOpt
(LXA 119 279/2)
Microsoft Windows XOpt XOpt
2000 Server
(LXA 119 023/1)
Microsoft XOpt
Windows 2000
Professional(LXA
119 041/1)
Microsoft SQL XOpt X
Server Std Edition
(LXA 119 054)
8/1553-AOM 901 015/1 Uen B -- 1

• Software key; a device that is put on the parallel port of each server/client
• MINI-LINK MANAGER User manual
• Software license agreement
The MINI-LINK MANAGER is available in 3 versions: MINI-LINK MANAGER

Client Application, MINI-LINK MANAGER Server Application and MINI-LINK
MANAGER Centralized Database Server. For each version, options that
increase the functionality are available. These options are made available by
use of specific software keys and licenses.
1.1.2 Software Key Installation
Included with MINI-LINK MANAGER is a software key. MINI-LINK MANAGER

requires the use of a software key to protect against illegal duplication of the
software. The “key”is actually a physical device, which is fitted transparently
on the computers parallel port. Depending on what license is obtained the
customer will receive different MINI-LINK MANAGER software and hardware
bundles.
To install a software key:
• Power off the computer and all peripheral devices prior to installing the
software key; it is sensitive to static electricity.
• Remove any connections to your computer parallel port.
• Secure the software key in the parallel port and tighten the screws.
• If you had any equipment connected to your parallel port, connect to the
back of the software key.
Warning!
Do not remove the software key from your node while MINI-LINK MANAGER
is running. If you do so, MINI-LINK MANAGER must be restarted and the
software key may be damaged.
Note: It is not recommended to attach any other device to the parallel port
that passes huge amounts of data (for example scanner, disc). A
printer though seems OK to attach to the parallel port.
1.2 Roadmap
The correct installation order for MINI-LINK MANAGER Server Application
is as follows:
2 8/1553-AOM 901 015/1 Uen B --

1. Windows 2000 Server installation with SP3
2. Windows 2000 Server installation and configuration
3. 3rd party software (required by adaptations, interfaces and local managers)
4. Microsoft SQL Server 2000 and Service Pack 3 (required only if you want
to install a MINI-LINK Medium Capacity adaptation otherwise the MSDE
2000 will be installed as default)
5. MINI-LINK MANAGER Server Application installation
6. MINI-LINK MANAGER Server Application configuration
7. Adaptations and interfaces configuration
8. Local manager installation
The design of this roadmap is intended to show which installation steps you will
need to execute depending of the amount of features you want on the server. If
you have Windows 2000 Server already installed, go directly to the Windows
2000 Server configuration chapter. This chapter prepares the server computer
for a MINI-LINK MANAGER Server Application installation.
Look through the roadmap above of what components you need in your system.
Then look through the Adaptation requirements, the Interface requirements and
the Local Manager requirements to identify the options you need to add to the
basic MINI-LINK MANAGER Server Application installation.
Feel free to make notes of what chapters you will have to use to make the
custom installation desired. Then you should not have to refer to any other
installation sections in this manual.
Gather all the TCP/IP address information before you begin installation of 3rd
party software and MINI-LINK MANAGER itself. This should be inserted in the
host files of all connected computers on the network.
Note: All third party products must be installed before the installation of
MINI-LINK MANAGER; otherwise proper configuration will not be
possible.
If you are using MINI-LINK MANAGER with the default MSDE 2000 DB
and you want to install a MINI-LINK Medium Capacity Adaptation you
will need to run an upgrading procedure, from MSDE to Microsoft SQL
Server 2000 Standard Edition, as described in the appendix section.
1.2.1 3rd Party Software Requirements
In order to make the installation easy and smooth you have to make sure that
you have the right hardware as well as the right software installations, especially
WINDOWS 2000, see Windows 2000 Server installation instructions below.
8/1553-AOM 901 015/1 Uen B -- 3

Furthermore you should make sure to install all necessary 3rd party software
products before you start with the MINI-LINK MANAGER installation.
MINI-LINK MANAGER Option 3rd party software required

MINI-LINK Medium Capacity Microsoft SQL Server 2000 Standard
Adaptation: Edition and Service Pack 3
Portions of MINI-LINK E Adapter:
• Pervasive Software
• Greenleaf Software
• SNMP Research International
NERA NEW Adaptation up to R5, NetOp 7.5
R6, R7A, R7B:
NERA NEW Adaptation from R7C: NERA New R7C client (with automatic
upgrade of Internet Explorer 5.5 to
Internet Explorer 6.0, if asked).
SNMP Manager Adaptation: Internet Explorer 5+, installed with
Windows 2000
MINI-LINK BAS Adaptation: Internet Explorer 5+, installed with
Windows 2000
MINI-LINK HC Adaptation: Internet Explorer 5+, installed with
Windows 2000
MINI-LINK TN Adp Internet Explorer 5.5 installed
SNMP Interface: (Does not require 3rd party software)
TL1 Interface: (Does not require 3rd party software)
BNSI Interface: (Does not require 3rd party software)
FTP Interface: (Does not require 3rd party software)
1.2.2 Mappings
When installing a MINI-LINK MANAGER Server Application use the above table
to find what additional installations of third party products you have to make
depending on your adaptation choices. Do likewise with the following sections
containing information for interfaces and local managers.
Instruction: Determine what components to install by looking at the leftmost

column. Then work yourself through the table from top left to bottom right and
install the required third party products as stated by the rightmost column.
Installation of the Core Components is mandatory for a new installation (but not
when installing more options at a later time). If you are installing components
that require the same third party product then of course you do not need to
install that third party product more than once, however, additional configuration
may be needed.
4 8/1553-AOM 901 015/1 Uen B --

The time for installation of the required local manager software is after the
installation of MINI-LINK MANAGER Server . Check the overview above to see
when it will have to be done. You should have installed all needed 3rd party
software prior to MINI-LINK MANAGER installation according to this roadmap
otherwise you might face a reinstallation of MINI-LINK MANAGER and all 3rd
party software and / or local managers.
For installation procedures of any local managers please refer to their

corresponding installation guides.
1.2.3 Windows 2000 Server
1.2.3.1 Basic Server Requirements
Make sure that you have the correct equipment run Windows 2000 Server and
the MINI-LINK MANAGER platform. See the following specifications for the
hardware requirements (Ericsson specifications):
Central Processor Unit Intel Pentium III 1,266 MHz

(minimum)
Primary memory 640 MB RAM (minimum)
Additional memory 256 MB RAM (minimum)
(required if MINI-LINK E Adapter
Server Application is installed on the
same server)
Un-removable media 9 GB disk (minimum)
Removable media CD-ROM and 3.5" diskette drive
Mouse 3 button Microsoft Win compatible
Keyboard Microsoft Windows compatible
Screen 1280x1024 High Colour resolution
(16bit) (17")
DCN connection 10/100 Base-T LAN
Operating System software Microsoft Windows 2000 Server
(SP3)
Parallel port on mother board
Note: If parallel port is not present on motherboard and a separate PCI card
adapter is being used, execute the installation procedure described in
Section 1.2.9 on page 18 before continuing with normal installation
procedure.
8/1553-AOM 901 015/1 Uen B -- 5

1.2.3.2 Verify the Contents of Windows 2000 Server Package
Check the Windows 2000 installation package if it contains one CD-ROM disc
and one floppy disk.
• Most new servers that are recommended in the above documentation, have
the ability to boot on the installation CD for Windows 2000 directly.
• If this is the case, just power on the server and insert the CD in the
CD-ROM drive.
• The installation program should start automatically.
• If this does not happen, then the server does not have that ability, or it is
due to a setting in the server BIOS.
• If it still does not boot on the CD, you might have to boot on four floppy
disks, which should be included with Windows 2000.
• If the disks are not included, or if the floppy disks are missing, you have
to create them.
• The disks have to be created on a PC where you can use a CD-ROM drive.
• Insert the CD and locate the \BootDisk folder.
• If you are accessing the CD from a character based interface (DOS) then
use the makeboot.exe program by entering makeboot a:.
• If you are accessing the CD from a Windows based computer, open a DOS
prompt window and enter: makeboot a:.
• You will be guided through the creation of the four floppy disks. Start the
installation by inserting the Windows 2000 Installation disk 1 and boot on it.
Note: You must install Windows 2000 on C partition and you do not change
the system directory WINNT. Check if the Regional Option is set
to English (United States) in the Regional Settings window during
Windows 2000 installation. If not, modify it with the Customize button
leaving the default date format: mm/dd/yyyy. During the Windows
2000 installation the Terminal Server must not be installed.
At first logon the "Windows 2000 Configure your Server" dialog appears.
Choose to configure your server later and uncheck the option "Show this
message at system start-up".
1.2.3.3 Booting Troubles
If the Windows 2000 system will not boot up because the boot files are corrupt
or missing, use the Windows 2000 Boot Disk. Insert the Boot Disk in drive A:\
and reboot your system. Make sure your computer BIOS is setup to read A: at
boot time. If and when the system has booted up and Windows 2000 is started,
6 8/1553-AOM 901 015/1 Uen B --

copy the three files (BOOT.INI, NTDETECT.COM and NTLDR) back from A:\ to
C:\ by dragging and dropping the files with My Computer.
1.2.3.4 Partitioning the Hard Drive or Logical Drive on RAID Set
Begin installation of Microsoft Windows 2000 Server with the creation of the
partition(s). It is recommended to only have one partition on the server. Since
the recommendation is to have just one partition on the drive, that partition will
automatically become a boot partition.
If a RAID solution is to be used, with multiple hard drives in a RAID set, you will
have to configure and initialise the logical drive before you proceed. Instructions
on how to do this should be included in the shipment of the server.
Caution!
If you intend not to follow the recommendations about hard disk partitioning,
please note that MINI-LINK MANAGER can only be installed on the C:\ partition
or possibly the D:\ partition. You must not use partitions with drive letters E:\
to Z:\.
1.2.3.5 Computer Name (Max 8 Characters)
In order for MINI-LINK MANAGER to work properly, the computer name must
not consist of more than 8 characters. Otherwise the internal communication
will be corrupt.
Computer names and nodes aliases must contain only alphanumeric characters
(any special character is allowed).
1.2.3.6 Page File
An increase of the page file size is required. Go to Control Panel -> System ->
Performance and choose Page file size. Minimum should be as automatically
stated in the text input field (with 768 MB RAM in the server). Maximum should
be twice the size of physical RAM (with 768 MB RAM in the server, it should be
1536). Close all the windows. Windows 2000 might require a reboot after this
(if the page file is smaller than before).
1.2.3.7 DrWatson
Initialise DrWatson by starting a DOS prompt and type:
˙ drwtsn32 -i
Then start the DrWatson control window by typing:
8/1553-AOM 901 015/1 Uen B -- 7

˙ drwtsn32
In the window that appears, tick the top three boxes under Options and leave
the rest. Set the log directory to C:\winnt (substitute c: for the appropriate
drive letter).
1.2.3.8 Windows SNMP Service
The Windows SNMP service should be installed. Make sure by going

to Settings->Control Panel->Network And Dial-up Connections, then in
Advanced menu select "Optional the Networking Components"->Verify that
the "Management and Monitoring Tools" is checked. Otherwise, check it
and click Next and insert the Windows 2000 Server Installation CD to let the
program access the files needed. The other thing about SNMP is that with the
installation of Windows SNMP service, the SNMP Trap service will also appear
in the Services applet in the Control Panel. This service must have Startup type
manual. In order to do it open the Services applet in the Control Panel, double
click on the SNMP Trap service and change its Startup Type to Manual. Then
press OK to confirm the operation.
1.2.3.9 Configuring the Server On The Network
Before you continue the server configuration you should receive from the local
network administrator the following informations:
• The Domain Controller (DC) the server will have to join
• The DNS server installed into the domain
• The IP address and subnet mask to be configured for the server
Note that both, a Domain Controller and a DNS server, must be present on the
network to ensure that MINI-LINK MANAGER Server works properly.
If a DNS server is not present, then the MINI-LINK MANAGER Server could be
configured to be a DNS server.
This can be done in two ways either you configure MINI-LINK MANAGER
Server as a DC and during the procedure described in the DC section you
promote it to be also a DNS server, or you must follow the procedure outlined
in the section "DNS".
If a Domain Controller does not exist on the network then the MINI-LINK
MANAGER Server could be configured as a Domain Controller. If this is the
case then the MINI-LINK MANAGER server IP address must be a static one.
Refer to "Domain Controller" section to configure MINI-LINK MANAGER Server
as a DC.
If the equipments are accessed through a router a Gateway IP, a DNS Host IP,
and a DNS IP are required. When Windows is installed and ready to use, test
the connection by using the PING command, and try to ping the equipment or
other computers.
8 8/1553-AOM 901 015/1 Uen B --

1.2.3.10 Domain Controller
A Domain Controller must exist on the network otherwise the MINI-LINK

MANAGER Server must be configured as a Domain Controller.
For W2K domain controller installation a static IP address is needed. If a

DNS server is not present it must be installed too. The following steps must
be followed:
1. During the W2K installation the computer must configured as member of

workgroup.
2. When the W2K installation is finished, launch the command dcpromo.
3. The Wizard window then asks to install Active directory, just press Next.
4. In the next window choose "Domain controller for a new domain" and
press Next.
5. In the next window choose "Create a new domain tree" and press Next.
6. In the next window choose "Create a new forest for domain trees" and
press Next.
7. In the next window indicate "Full DNS name for new domain", insert the
name with a dot "name." and press Next.
8. In the next window indicate "Domain netbios name" leaving the default
name.
9. In the next two windows the location is showed. Leave the default value.
10. In "Active directory installation Wizard" Windows message appears, press

Ok.
11. In "Active directory installation Wizard" select yes, install and configure
DNS on this computer (recommended).
12. In the next window choose "Permission compatible with pre W2K servers"
and press Next.
13. In the next window indicate the Administrator password for domain
management and press Next.
14. In the Summary window press Next.
8/1553-AOM 901 015/1 Uen B -- 9

15. If the installation asks you to insert W2K disk please insert the 2000 Server
CD rom.
16. Press finish and on the next window press Restart.
The installation will start and after the system reboot the machine is ready.
Note: The above-mentioned Active Directory installation refers only to the

basic installation required to promote on of the MINI-LINK Manager
servers to be a DC in a stand-alone domain. If your system has to be
integrated in an Enterprise Network careful planning and configuration
has to be made. Refer to the local network administrator for these.
The machine name cannot be changed after DC installation.
When a MINI-LINK MANAGER Server machine is configured as a

Domain Controller, the Network ID tab will show as a machine name
"hostname.DOMAIN", even if the machine name is always "hostname".
When a MINI-LINK MANAGER Server machine is configured as a

Domain Controller, the Domain Name cannot be changed, because
MINI-LINK MANAGER could not work properly.
1.2.3.11 DNS
If the MINI-LINK MANAGER Server Application is to be installed on a PC

different from the PC configured as domain controller, the DNS of the MINI-LINK
MANAGER Server PC must be configured to provide name resolution.
The prerequisite is that a Domain Controller PC exists on the network. On this

PC, the other computers, including the MINI-LINK MANAGER Server PC, must
be inserted in its "Active Directory Users and Computers" and registered with
their names under the "Computers" belonging to the domain of the DC.
The PCs participating to the network of the DC PC, including the MINI-LINK
MANAGER Server PC, must be first configured as Member of WORKGROUP,
with static IP addresses and with DNS Server addresses the IP address of the
DC PC. Then they must join to the domain defined on the DC PC.
1.2.3.12 System File Patches
You will use Windows 2000 Service Pack 3 to update the system files on the
computer. Those can be found on the MINI-LINK MANAGER CD:
• Log in as a WINDOWS 2000 administrator. Insert the MINI-LINK

MANAGER 3PP CD into your CD-ROM drive. If the MINI-LINK MANAGER
installation program starts up automatically, push cancel and then select to
exit the installation program.
• From the Start menu, select run.
10 8/1553-AOM 901 015/1 Uen B --

• To install Windows 2000 Service Pack 3 type: D:\servi-

cepacks\W2kSP3\W2KSP3.exe (substitute D for the appropriate letter of
your CD-ROM drive).
• To ensure that the system always has the latest system files installed, this
operation will have to be repeated several times.
• When asked to restart the computer, choose to restart immediately.
1.2.3.13 Internet Explorer 5.5
In order for MINI-LINK MANAGER to work properly, Microsoft Internet Explorer

(IE5.5) must be installed. The most important installation option we will add is
the Microsoft Virtual Machine, which is needed to be able to access the Local
Managers for HP routers, hubs and switches.
• Log in as an WINDOWS 2000 administrator. Insert the Internet

Explorer CD (MINI-LINK MANAGER 3PP CD) into your CD-ROM drive.
Start D:\Iexplorer5.5_SP2\Ie5setup.exe (substitute D for the
appropriate letter of your CD-ROM drive).
• You will be prompted if you agree to the End User License Agreement.
• Select to Accept and push the Next button.
• Choose the Install MINI-LINK MANAGER, or Customise your Web Browser

option. Press Next.
• In the Component Options, select the Microsoft Virtual Machine component

and press Next to start the installation.
• Do not change anything else in the list.
When installation is done click Finish to reboot. The first time the computer has
rebooted after installation of IE5, some additional automatic configuration will
take place. Just wait for it to finish.
1.2.3.14 IIS Admin Service
During the WIN2K operating system installation choose do not to install the IIS
(Internet Information Services). If these Windows Admin Services are already
installed, please de-install them from the Add-Remove Programs, checking in
Add/Remove Windows Components, Internet Information Services (IIS).
1.2.3.15 Windows 2000 Server Installation Complete!
By now Windows will have rebooted (a couple of times) and you will have a
basic Windows 2000 Server up and running.
8/1553-AOM 901 015/1 Uen B -- 11

1.2.4 Windows 2000 Server Configuration
1.2.4.1 Regional Settings
For MINI-LINK MANAGER to function correctly must be set in the following

manner: Settings->Control Panel-> Regional Options: Tab "General"
Select "English (United States)".
Figure 1 Regional Options General
1.2.4.2 Services File
If you want to install NETMAN Server Application on the same MINI-LINK

MANAGER server machine you must edit the C:\WINNT\sys-
tem32\drivers\etc\services file and change the SNMP port from the
default value 161 to a new one available.
Next step is installing the third party products.
1.2.5 NetOp 7.5
This software is needed for NERA NEW up to R7B (Server), so you can skip
this section if you do not use NERA equipment in your network.
In this chapter you will learn how to install NetOp, which is used for screen
integration of Windows NT2000 machines. NetOp Host is installed on a
12 8/1553-AOM 901 015/1 Uen B --

machine you need to supervise via remote control, and NetOp Guest is installed
on a machine that you will use for surveillance.
1.2.5.1 NetOp 7.5 Host
This installation takes place on a Windows NT 4.0 Server or Workstation when

remote windows screen integration of that machine is needed. To Install NetOp
7.5 as a Windows NT Host:
• Login with a user with administrator privileges on the Windows NTNT

machine.
• Insert the NetOp CD-ROM into the CD-ROM drive.
• If the main installation menu does not appear automatically,
− From the Start menu, select run.
− Type D:\Setup (substitute D for the appropriate letter of your CD-ROM

drive).
• Select the desired language, for example English.
• In the next installation menu select Installation.
• Then select Install NetOp.
• In the Welcome window push the Next button.
• Push Yes if you agree to the software license agreement.
• In the Registration window enter "Licensed to" and the "Serial number"
found on the NetOp license certificate. Then push the Next button.
• Push Next in the Choose Destination Location window.
• In the Select Program Folder window push the Next button.
• Push Next to Start copying files.
• In the Setup complete window, push the Finish button.
• Exit the main installation menu by pushing Exit.
• To start the NetOp 7.5 Host, do the following:
• Start the program Start/Programs/NetOp Remote Control/Host.
• In the Configuration window that pops up answer No to the question "Do

you want NetOp to help you create a serial communication profile now?".
• In the Communication Profile list box select TCP/IP by checking the box
beside it.
8/1553-AOM 901 015/1 Uen B -- 13

• Then push the Wait for Call button to enable NetOp guests to connect
to the host.
The installation of NetOp 7.5 Host is now finished.
1.2.5.2 NetOp 7.5 Guest
This software is needed for: NERA NEW up to R7B (Client).
This installation takes place on a Windows NT 4.0Windows NT Server or

Workstation that shall access NetOp hosts for screen integration. To Install
NetOp 7.5 as a Windows NT2000 Guest:
• Follow the same installation procedures (step 1 to 13) as for the installation
of NetOp 7.5 to create a Windows NTNT Host, see section above.
To make IMA able to launch NetOp do the following:
• Make sure that NetOp 7.5 Host software is installed and running on host
computer.
• Start the program Start/Programs/NetOp Remote Control/Guest.
• In the Configuration window that pops up answer No to the question "Do

you want NetOp to help you create a serial communication profile now?"
• Select Configuration/Communication Profiles from the menu.
• In the Communication Profile Setup window check the TCP/IP check box
and then push the Close button.
• Make a connection to the remote NetOp host using the host IP-address
and the TCP/IP protocol.
• Push Ok in the Information window that pops up and then close the NetOp
Guest program.
1.2.6 NERA NEW R7C Client
This software is needed for NERA NEW Adaptation from R7C (Server).
To install NERA New R7C client:
1. Insert “NEW-NMS” CD into the CD-Player.
2. Open the CD-Drive and run the “Setup.exe” program.
3. If Internet Explorer 6.0 is not installed, the “Microsoft Internet Explorer 6.0
not found” appears. Then:
• Click Yes button to start installation of Microsoft Internet Explorer 6.0.
14 8/1553-AOM 901 015/1 Uen B --

• In “Windows update: Internet Explorer and Internet Tools” select I accept

the agreement and click on Next button.
• Click Next button in the following window.
• Click Finish button to complete installation and restart the PC.
• After the PC restart and the installation completion redo the steps 1 and 2.
4. Click Next button to start with the setup of NEW_NMS application.
5. Type a User Name and a Company Name.
6. Click Next button to continue installation, or click Browse button to change

the pre-defined Destination Folder.
7. Select “NEW-NMS Client” and click Next button.
8. Click Yes if you want to add a program shortcut on the PC desktop.
9. Click Next button to continue installation.
10. Click Finish button to complete installation and restart the PC.
1.2.7 Installation of Microsoft SQL Server 2000 Standard Edition
Microsoft SQL Server 2000 Standard Edition and Service Pack 3 must be
installed before MINI-LINK MANAGER 6.1 if you want to install also a MINI-LINK
Medium Capacity Adaptation. If you are using MINI-LINK MANAGER with
the default MSDE 2000 DB and you want to install a MINI-LINK Medium
Capacity Adaptation you will need to run an upgrading procedure, from MSDE
to Microsoft SQL Server 2000 Standard Edition, as described in the appendix
section.
1.2.7.1 Installing Microsoft SQL Server 2000
To install SQL Server 2000:
1. Insert the Microsoft SQL Server 2000 compact disk into the CD-ROM drive.
2. Click Run on the Start menu and browse the CD to find a file called
Autorun.exe. Double-click this file.
3. Click SQL Server 2000 Components.
4. Click Install Database Server.
5. Click Next in the Welcome dialog box.
6. Select Local Computer in the Computer Name dialog box.
7. Select Create a new instance of SQL Server, or install Client Tools in the
Installation Selection dialog box.
8/1553-AOM 901 015/1 Uen B -- 15

8. Click Next in the User Information dialog box.
9. Accept the Software License Agreement.
10. Select Server and Client Tools in the Installation Definition dialog box.
11. Click Next in the Instance Name dialog box to install a SQL 2000 Default
instance.
12. You are recommended to make a Custom installation.
13. Click Next in the Select Components dialog box.
14. In the Services Accounts dialog box, select Use the same account for each
service. Auto Start SQL Server Service. Under Service Settings, select
Use the local system account.
15. In the Authentication Mode dialog box, select Mixed Mode (Windows
Authentication and SQL Server Authentication) and check Blank Password
for the sa login.
16. In the Collation Settings dialog box, select the Collation designator option
and select Latin1_General in the list. Under Sort Order, select Case
sensitive and Accent sensitive.
17. Click Next in the Network Libraries dialog box.
18. Click Next in the Start Copying Files dialog box.
19. Select Per-Seat licensing mode in the Choose Licensing Mode dialog box
(with a devices number not equals to zero) and click Continue.
20. Click Finish in the Setup Complete dialog box.
1.2.7.2 Installing Service Pack 3 for SQL Server 2000
To download and install Service Pack 3 for SQL Server 2000:
1. Connect to the Microsoft SQL Server downloads at http://www.mi-

crosoft.com/sql/downloads/2000/sp3.asp
2. Download the self-extracting service pack executable file (SQL2KSP3.exe)
for the database components.
3. Copy the SQL2KSP3.exe file to the computer running SQL Server 2000.
4. Execute the SQL2KSP3.exe file.
5. The self-extraction program will prompt you for the name of the directory
in which you want the service pack files placed. For example, if you have
created a directory named C:\2000sp3, copy the file SQL2KSP3.exe
to your SQL Server computer, execute it, and provide the name of the
C:\2000sp3 directory when prompted.
16 8/1553-AOM 901 015/1 Uen B --

6. Read the instructions in the readme.htm file that is located in the folder
where you extracted the service pack, then double-click the Setup.bat
file to start the installation.
7. In the Welcome dialog box, click Next.
8. In the Software License Agreement dialog box, click Yes.
9. In the Instance Name dialog box, click Next.
10. In the Connect to Server dialog box, select Windows Authentication, then
click Next.
11. Select Ignore the security threat warning [...], then click OK.
12. Select Upgrade Microsoft Search [...], then click OK.
An error reporting window appears.
13. In the Start Copying Files dialog box, click Next.
14. In the Setup dialog box, click OK to confirm that you should do backups of
the master and msdb databases after installing of the service pack.
15. In the Setup Complete dialog box, click Finish.
16. Restart your computer and make sure that SQL Server is running before
continuing with the rest of the installations.
8/1553-AOM 901 015/1 Uen B -- 17

1.2.8 Installation of MINI-LINK MANAGER
All MINI-LINK MANAGER options shall be installed in the same directory.

Installing different options into different directories may lead to undesirable
effects.
Note: You must have local administrator privileges in the WINDOWS 2000
environment to be able to install MINI-LINK MANAGER Server
Application.
Before you begin installing MINI-LINK MANAGER make sure that all
third party products that are needed according to sections 6 to 13
have been installed.
The installation software makes it possible for the user to specify what different
options to install.
Specifically the MINI-LINK MANAGER 6.1 installation program allows

installing the MINI-LINK E Adapters (that is, the formerly called NETMAN
Server/Client/Proxy Agent) directly from the MINI-LINK MANAGER CD avoiding
a separate Adapters installation.
The set-up integration (that is, installing the Adapters together with MINI-LINK
MANAGER, see Section 1.2.10 on page 23) consists of launching the Adapters
installations in silent mode.
Furthermore the MINI-LINK E Adapters set-ups can be also launched in normal

mode from the MINI-LINK MANAGER installation program main window,
without installing MINI-LINK MANAGER (that is, MINI-LINK E Adapters
stand-alone installation, see Section 1.2.11 on page 26).
1.2.9 PCI Parallel Port Adapter Installation
This is only needed where parallel port is not present on motherboard and a
separate PCI card adapter is being used.
18 8/1553-AOM 901 015/1 Uen B --

Note: Sentinel System Driver can work with a PCI parallel port adapter under
the Windows 2000 operating system. The Sentinel System Driver
(SSD5.39.2-p01) can be configured to work with the following PCI
Parallel Port adapters:
CyberParallel PCI - Single Fast ECP/EPP Parallel Port
Part Number: JJ-P00112
http://www.siig.com/
Intek21 PCI High-Speed ECP/EPP Parallel Port
Model TK9902
http://www.intek21.com
Follow the steps below:
1. Copy all the files and folders from IMA/MINI-LINK Manager installation CD
to the new folder created (that is: C:\install).
2. Associate a new folder path with a drive letter "B:" running the command
below. The example refers "C:\install" folder. Please replace it with the
one you created.
subst b: C:\install
3. Change directory to "B:\Fix2.5".
4. Double click on "Setup.exe" to run the iFix setup application.
5. 5. The following pop up message box will be showed. Click Ok to proceed.

The iFix installation will start showing the installation welcome window.
Please, do not click any button.
6. Launch the Windows Explorer application, copy the B:\Fix 2.5\sim\Sen-

tinelDriver \sentinel.sys file and paste it on C:\winnt\system32\drivers
folders replacing the existing one.
7. Perform the following steps to determine the resource used by the adapter:
8/1553-AOM 901 015/1 Uen B -- 19

Note: We assume as an example that you installed the SIIG CyberParallel

PCI Card. If you installed the other adapter the settings may
change accordingly.
a From the Control Panel, double-click the System icon to open the System
Properties page.
b Click the Hardware tab and then the Device Manager button to open the
Device Manager.
c Click the + sign next to Ports (COM & LPT) to expand the tree.
d Double-click on SIIG CyberParallel PCI Card (LPT1) to open the property

sheet for the Cyber PCI adapter.
e Click on the Resources tab to see the resources used by the adapter.
f The value circled in red in the SIIG CyberParallel PCI Card properties page
above is the address of the parallel port.
8. Perform the following steps to configure the Sentinel System Driver to use
the port:
20 8/1553-AOM 901 015/1 Uen B --

a Run the C:\Program Files\Rainbow Technologies\Sentinel System

Driver\SetupSysDriver.exe.
b Click the Configure Driver button as can be seen in the picture below:
c The following dialog will be displayed. Click the Add button.
d The following dialog will be displayed. Enter the I/O address of the PCI
parallel port adapter into the "Bus Address" field.
8/1553-AOM 901 015/1 Uen B -- 21

e Click the OK button and the following dialog will appear:
f Click the OK button and the following dialog appears. It shows that a User
Created port has been added at address 1088.
g Click the OK button to close the dialog, click the "Start NT parallel driver"
to start the driver and open the File menu and choose Exit to close the
Sentinel System Driver Configuration Utility.
h The Sentinel System Driver should now be configured to use the

CyberParallel PCI adapter.
22 8/1553-AOM 901 015/1 Uen B --

9. Coming back to the iFix installation procedure, continue by clicking the

Next button on the welcome window.
10. Click Next to install on the default path.
11. Click Next button to install the iFix "Typical" setup type and wait for the
component installation.
12. On "Node Information" window, insert the server name as "Nodename"

(remember up to 8 characters) end select Standalone as "Node Type".
Click OK when ready to continue.
13. Click Yes button on the question "Do you want Enable Scada Support?"
14. Click No button on the question "Would you like to register the product
online now?"
15. Select "Yes, I want to restart my computer now" and click finish button.
16. The installation will proceed according to the installation guide.
During the installation an information window warns the set-up will skip the
iFix application installation.
1.2.10 Installing MINI-LINK MANAGER Server Application Together With

The MINI-LINK E Adapters
To start the MINI-LINK MANAGER INSTALL program follow the steps outlined
here:
1. Log in as a user with administrator rights.
8/1553-AOM 901 015/1 Uen B -- 23

2. Insert the MINI-LINK MANAGER SW 6.1 CD into your CD-ROM drive.
3. If the installation program does not start automatically: from the Start
menu, select run.
4. Type D:\imasetup.exe (substitute D for the appropriate letter of your

CD-ROM drive).
5. From the Menu select MINI-LINK Manager 6.1 menu choice. This will start
MINI-LINK MANAGER setup.
6. In the MINI-LINK MANAGER Install Welcome window, continue by pushing

the Next button. The Choose Destination Location window appears.
7. Accept the default and press Next.
8. When ready push Next to continue to the Select Components window.
9. A MINI-LINK MANAGER Server Application, a MINI-LINK MANAGER

Client Application or a MINI-LINK MANAGER DB Server Application can
be selected.
10. Continue by pushing on the MINI-LINK MANAGER Server Application

button.
11. If the Microsoft SQL Server 2000 Standard Edition has not been detected a
warning message will appear:
If you want to use MINI-LINK E Adapter Server Application on the same

server press YES to exit from the setup and to install Microsoft SQL Server
2000 Standard Edition. Press NO to continue.
The Select Components window appears.
12. Now you can choose either the whole package of Adaptations and
Interfaces or click on the Change button to select parts of the packages.
The choice "Core components" have no sub-component window. You

must either install them completely or not at all. The Core Components
are selected by default. If you already have a MINI-LINK MANAGER
installation and you only want to add applications or options then you have
to deselect the Core Components.
13. The normal installation choices, about the sub-components to be installed

(adaptations, interfaces), are selected by default.
Note: Be careful if you unintentionally deselect a component in the Select

Components window. Selecting the same component again will
then select all sub-components. (Any changes will be reset.)
14. Push the Continue button.
15. Push the Next button.
24 8/1553-AOM 901 015/1 Uen B --

16. If it has been selected the MINI-LINK Medium Capacity Adaptation to be

installed, another Select Components window appears.
In this window it is possible to check the MLE Adapter Installation, that

consists of two set-ups programs (the MINI-LINK E Adapter Server and the
MINI-LINK E Adapter SNMP Proxy) launched sequentially in silent mode
with MINI-LINK E adapter Client.
Note: If no previous Netman Server, Proxy, Client version has been

detected, the MINI-LINK E Client Adapter set-up is launched
anyway in silent mode also if no MINI-LINK E Adapter installation
has been selected in the Select Components window (that is,
no explicit selection is needed during IMA setup to install the
MINI-LINK E Client Adapter).
If a previous installation of MINI-LINK E Adapter Server or MINI-LINK E

Adapter Client (Netman Server or Netman Client) has been detected a
message will appear: "It is requested to upgrade it to MLE Adapter Server.
You can exit from setup and upgrade it or continue and upgrade it at the
end of this installation."
If you choose to continue MLM Server installation, before MINI-LINK E

Adapter Client, a warning message will appear: "A previous Netman Server
and Proxy Agent version are already installed. MINI-LINK E Adapter Client
can’t be installed."
17. Push the Next button.
18. NEs and Subnet number size Window is displayed.
19. Leave the default value of 1000 NEs unless your license states otherwise.
20. Choose the max number of sub-network your MINI-LINK MANAGER

installation should handle (default value is 256).
21. If MINI-LINK MANAGER is already installed, you will get a control question.
Choose Yes if you are upgrading. You will get this question only if you have
selected core components.
22. Push the Next button to start with the installation of the following software:
DAO, ADO and TCL 8.0.4, and MINI-LINK Adapters in silent mode if you
have choosen Medium Capacity Adp.
If MINI-LINK Adapters installation fails, a window will show the exit error
code, click Next to continue.
Note: THE AUTOMATIC INSTALLATION STARTS AND ALL IMA/MINI-LINK

MANAGER SOFTWARE WILL BE INSTALLED. THIS CAN TAKE
SEVERAL MINUTES (25 MIN).
23. Press Finish to reboot the computer.
8/1553-AOM 901 015/1 Uen B -- 25

24. Once the MINI-LINK MANAGER Server installation program has

finished, the PC is rebooted. At PC start-up, in order to configure the
MINI-LINK MANAGER databases, the "Post-Install" procedure is launched
automatically.
Note: The MINI-LINK E Client Adapter set-up is launched anyway during

the installation also if no MINI-LINK E Adapter installation has been
selected in the Select Components window (that is, no explicit selection
is needed during MINI-LINK MANAGER setup to install the MINI-LINK
E Client Adapter).
Caution!
Do not remove the MINI-LINK Manager Software user account
(IMA_USER/netman) or change its password while the MINI-LINK Manager
software is installed, or the MINI-LINK Manager software will not work properly.
At the end of the installation the snmpd.cnf file located in the

C:\MINI-LINK\MXMCommon\Emanate folder is modified automatically. In fact
the last line of the file must contain the actual server IP Address.
In case this modification fails the line will contain default ip address (127.0.0.1).
Therefore the line will look as follows and the ip address has to be modified
manually:
....
transportEntry TargetComputer2 1 snmpUDPDomain 127.0.0.1:0

255.255.255.255:0 1500 \ nonVolatile
Replace with:
....
transportEntry TargetComputer2 1 snmpUDPDomain <your IP>:0

255.255.255.255:0 1500 \ nonVolatile
To modify the file use Notepad or any other text editor be careful to drag the
file into an open editor instance since the default open command for this file
extension will not activate the "open with" dialog.
1.2.11 MINI-LINK E Adapters Stand-Alone Installation
The MINI-LINK E Adapters installation, stand-alone mode, from the MINI-LINK

MANAGER Server set-up program consists of launching, from the MINI-LINK
26 8/1553-AOM 901 015/1 Uen B --

MANAGER CD and without installing MINI-LINK MANAGER Server Application,

the MINI-LINK E Adapter programs.
If it has been selected from the MINI-LINK MANAGER program main window,
MINI-LINK E Adapter, then E-Adapter Server will be installed, and no explicit
selection is needed during MINI-LINK MANAGER setup to install the MINI-LINK
E Client Adapter.
Note: It is recommended to perform the Mini-Link E Adapters installation in

stand-alone mode only on a computer running Microsoft Windows 2000
Server Service Pack 3 operative system with Microsoft SQL Server
2000 Standard Edition with Service Pack 3.
1.2.11.1 Installing MINI-LINK E Adapter Server
To start the MINI-LINK E Adapter installation program follow the steps outlined
here:
1. Insert the MINI-LINK MANAGER installation CD in the CD-ROM drive and

when it starts (it is auto-running) select from the program main window to
install MINI-LINK E Adapter.
2. If a previous version of MINI-LINK E Adapter Server is installed on the PC,

you will be asked to uninstall the previous version during the installation
process. If this is the case make sure that the MINI-LINK E Adapter Server
is shut down before installing the new version. If the MINI-LINK E Adapter
Server is not shut down, the installation program cannot uninstall the
previous version. See Section 1.2.11.3 on page 30 for instructions on how
to shut down the MINI-LINK E Adapter Server. However, all data (such as
the database log files, configuration files, and network list files) is backed
up to a temporary directory and then converted to the new version.
Caution!
You will not be able to supervise the network while the database log files (Alarm,
Performance, and AGC) are converted. This can take some time depending
on the amount of records in each log file. You are therefore recommended to
remove old log records so that only the most recent log records are converted.
On a 266 MHz computer with 128 MB RAM, the conversion of 200,000 records
takes about 8 minutes.
3. Welcome
This is the Welcome window for the Server Setup program. Click Next
to continue.
8/1553-AOM 901 015/1 Uen B -- 27

4. The Choose Destination Location window appears. Accept the default

and press Next.
Caution!
Ericsson recommends to never change the proposed default directory.
Furthermore client installation drive must be the same as MINI-LINK
Manager one.
5. SNMP Configuration window appears.
Click Next to continue.
6. SNMP Configuration
To the question do you want to add computers receving SNMP trap

messages? Click Yes and then press Next.
7. SNMP Configuration window appears.
Enter the IP-Address of the MINI-LINK MANAGER Server on which the

corresponding MINI-LINK Medium Capacity Adaptation is installed.
8. Start Copying Files
Check all the parameters you have entered. If all settings are correct click
Next to start the installation. If something is wrong click Back until you
reach the correct window and change the information.
9. Check if Database Exists.
If a MINI-LINK database already exists on the machine this dialog is shown.

If you want to use the existing database choose “Use the current database”
selection and click Next to continue. Otherwise, if you want to create a
new database, choose “Create a new database” selection and click Next
to continue.
10. Ericsson recommends to install the database script MoveToArchive (as

described in the Administration Guide in Section Creating a Job to Move
Logs to Archive) to prevent the number of records in the database to grow
uncontrolled and thereby reduce performance and click OK to continue.
11. Setup Complete
It is recommended to read the ReadMe file. It contains the latest information

on the program. Click Finish to exit the setup program.
12. Restart the computer
28 8/1553-AOM 901 015/1 Uen B --

Choose yes I want to restart the computer now. Wait for the machine to
restart. If you are installing a IMA server after restart login again and
complete the installation with ML E Adapter Client setup.
After restart login again and complete the installation with the ImaPostInstall
procedure that automatically starts at the login.
1.2.11.2 Installing MINI-LINK E Adapter Client
To start the MINI-LINK E Client Adapter Client installation program insert the
MINI-LINK MANAGER installation CD in the CD-ROM drive and when it starts
(it is auto-running) select from the program main window to install MINI-LINK
E Adapter Client.
Note: MINI-LINK E Adapter Client is installed on every PC (including the

MINI-LINK E Adapter Server PC) that will be used for network overview
with the MINI-LINK E Adapter system.
If a previous version of MINI-LINK E Adapter Client is installed on the PC, all

your data is stored in a temporary directory and then converted to the new
version. This means that you will not lose any of your data.
1. Welcome
This is the Welcome screen for the Client Setup program. Click Next
to continue.
2. Choose Destination Location
Caution!
Ericsson recommends to never change the proposed default directory.
Furthermore client installation drive must be the same as MINI-LINK
Manager one.
If you want to change the directory click the Browse button. Click Next
to continue.
3. Start Copying Files
Check all the parameters you have entered. If all settings are correct click
Next to start the installation. If anything is wrong click Back until you reach
the correct window and change the information.
4. Setup Complete
It is recommended to read the ReadMe file. It contains the latest information

on the program. Click Finish to exit the setup.
8/1553-AOM 901 015/1 Uen B -- 29

1.2.11.3 Shut-down of MINI-LINK E Adapters Stand-Alone Programs
Caution!
The MINI-LINK E Adapter Server must be running at all times. If not, the
entire MINI-LINK E Adapter system, including all connected clients, will be
shut down. Note that the traffic in the MINI-LINK network is not affected, only
the supervision.
A MINI-LINK E Adapter Client can be shut down when it is not used. If a

System Administrator Client has an unsaved server network list, you will be
prompted to save it before exiting. Shutting down a MINI-LINK E Adapter Client
does not affect the MINI-LINK E Adapter Server.
Note: Shutting down the MINI-LINK E Adapter Server may take several
minutes if there are many terminals in the Network List and the Include
Start and Stop check box is selected in the Configure Data Collection
dialog box (see Configuration guide and MINI-LINK Medium Capacity
Adaptation Guide).
To shut down the MINI-LINK E Adapter Server:
1. In Windows 2000: Click Start > Settings >Control Panel >Administrative

Tools > Services
2. In the Service list, click MINI-LINK E Adapter Server.
3. Click Stop.
4. Click OK.
5. Click Close.
Note: You must close the dialog box if you intend to remove the MINI-LINK E
Adapter Server from the system, for example, if you are upgrading to a
newer version of the MINI-LINK E Adapter Server.
If you start up the MINI-LINK E Adapter Server with the same, default network
file (for example Network.ids) that was loaded at the last MINI-LINK E
Adapter Server shut-down, then the following will happen:
1. The MINI-LINK E Adapter Server will get the last known severity for all
terminals in the network file.
2. The MINI-LINK E Adapter Proxy Agent will start.
30 8/1553-AOM 901 015/1 Uen B --

1.3 Configuration Of Mini-Link Manager

Do not start MINI-LINK MANAGER just yet. Some configuration needs to be
done before MINI-LINK MANAGER is started.
1.3.1 Accounts for Windows 2000 User to start up MINI-LINK MANAGER
Windows 2000 (Professional or Server) allows you to create personal accounts

and to place them in user groups achieving the different levels of access rights.
Depending on which groups an account belongs to, the role of that user is
defined and access rights given to the disk resources and applications. The
MINI-LINK MANAGER platform requires that a user of Windows 2000 is defined
in global groups, which means that a domain controller needs to be present
on the network.
Start Computer Management (Settings->Control Panel->Administrative

tools->Computer Management). Select Local User and Groups to see existing
or define new user groups and accounts. In order to work properly, a Windows
2000 user, who starts up MINI-LINK MANAGER, must be a domain users and
must be included in the Administrator group of the local machine.
If user account cannot be administrator on Windows 2000 system the following

procedure must be followed in order to ensure correct operation.
Warning!
This section includes information about modifying your system registry. Using
the registry editors incorrectly may cause your system to become unbootable. It
is strongly recommended that you run RDISK /S to update Windows NT repair
information and create an emergency repair disk. RDISK is not a replacement
for a full back up. If you do not fully understand the instructions on editing
your systems registry we recommend that you consult your local systems
administrator for assistance.
The steps are as follows:
1. Log into Win2K as a user with Administrative rights. Click on Start/Run

and in the run line type regedt32 and hit enter. This will bring up the
registry editor.
2. Select the HKEY_CLASSES_ROOT window.
3. Make sure the HKEY_CLASSES_ROOT folder is selected and click

Security then Permissions. This will bring up the "Permissions for
HKEY_CLASSES_ROOT" dialog.
8/1553-AOM 901 015/1 Uen B -- 31

4. If the user or group you want to login as is not in the Name list then you can
add them by clicking Add and selecting the username or groupname (notice
that you can select everyone instead, then this procedure will work for all
users defined on the domain) from the domain and clicking Add then OK.
5. You should now see your user or group (or everyone) in the Name list. Now
click Advanced, which will display the "Access Control Settings" dialog.
6. Select the user or group (or everyone) from the list and click View/Edit.
This will display the "Permission Entry" dialog, which shows the available
permissions.
7. Under the "Allow" column, put a check in the "Set Value" Permission. If
there is already a check, please double check that the correct user or group
has been selected in the Name box.
8. Click OK for each dialog.
9. Repeat also for HKEY_LOCAL_MACHINE\Software\Ericsson steps above.
10. Close the registry editor.
11. Now, by "My Computer", make sure the Dynamics directory (that is
C:\Dynamics) is selected.
12. Open the contextual menu with the right-click and select "Properties" and
then the tab "Security".
13. Click Advanced and in the "Access Control Settings" dialog, check "Reset
permission on all child objects and enable propagation of inheritable
permissions" and click OK.
14. Click Yes in dialog that will be displayed.
15. Repeat the last four steps for Ericsson directory (that is C:\Ericsson).
16. Close "My Computer".
Now you can log on as the user or group specified and access MINI-LINK
MANAGER.
Note: Each time a user with administrative rights creates maps, the steps
executed above for the security assignments in C:\Dynamics must be
performed also on the directory C:\Ericsson\IMA\pic, in order to allow
a user not in the administrator group to access those maps when he
logs onto the PC in a later session.
1.3.2 Shared Directories
If the clients connected to the server are intended to use the pictures and the
maps that are stored on the server, it will be necessary to share the directory
that contains this information. Enable sharing on the C:\Ericsson\IMA folder
(substitute C: for the partition where you installed MINI-LINK MANAGER;
32 8/1553-AOM 901 015/1 Uen B --

default name for the share will be IMA; replace IMA for <share> or any other
name you have chosen in what follows). Then you can map network drives on
the clients for <share>\pic accessing pictures and map information, and
<share>\local accessing security information.
1.3.3 Enable Autostart of MINI-LINK MANAGER
Auto start of MINI-LINK MANAGER must always be enabled for a MINI-LINK

MANAGER Server.
Follow the procedure below:
1. Choose from the start menu: Programs > IMA > System Configuration.
2. Under Configure menu, select Local Startup. Check the boxes Continue
running after Logoff and Start FIX at system boot.
1.3.4 Configuring Tasks
You need to configure some tasks that MINI-LINK MANAGER uses to start
the adaptations or interfaces.
Note: Options might be required before you proceed. Please refer to each
configuration guide for the various adaptations, interfaces for more
configurations required.
Caution!
Do not remove the first task already present into the task list and below
reported: %C:\DYNAMICS\SUMQDEL.EXE -F1:00:00
• Start the System Configuration program, which you will find in the
MINI-LINK MANAGER program group.
• Select Configure: Tasks
• Push the ? button and locate the file needed.
• Select "Start up Mode" to be Background.
• Select the Add button.
• Push the Ok button.
• When you return to the MINI-LINK MANAGER System configuration

window, choose "Save" in the File menu and then exit.
• Reboot the server.
8/1553-AOM 901 015/1 Uen B -- 33

According to the export interfaces installed during the setup program, you need
also to configure the tasks:
• SNMP Interface
− c:\dynamics\AlarmUserQ.exe, (Enter /nqueue1 /s9999 at the Command

Line)
− c:\ericsson\IMA\snmp_proxy.exe
• TL-1 Interface
− c:\dynamics\AlarmUserQ.exe
Note: If AlmUserQ.EXE is already used, make a copy (that is,

AlmUserQTL1.exe) of the file and use the copy instead. Enter
/nqueue3 /s9999 at the Command Line.
− c:\ericsson\ima\TL1\tl1.exe
• BNSI interface
− c:\dynamics\AlarmUserQ.exe
Note: If AlmUserQ.EXE is already used, make a copy (that is,

AlmUserQBnsi.exe) of the file and use the copy instead. Enter
/nqueue2 /s9999 at the Command Line.
− c:\ericsson\ima\bnsi\emm.exe
According to the Remote Software Download functionality for MINI-LINK HC

Adaptation, you need also to configure the task:
• c:\ericsson\IMA\RSU\Tools\MLEHC\TFTP.exe
According to the AlarmWatchDog functionality, you need also to configure the

task:
AlarmWatchDog c:\ericsson\ima\bin\AlmPeak.exe
1.3.5 Configuring Automatic Login File
The System Configuration program allows a specified operator to automatically

log in when the specified node starts up. In order to do it follow the procedure
below:
1. Start MINI-LINK MANAGER using IMA Startup Manager icon in System

tray.
2. Wait until IMA is running.
3. Choose from the start menu: Programs > IMA > Login.
34 8/1553-AOM 901 015/1 Uen B --

4. Click Log out.
5. Type admin for user and admin for password then click log in again.
6. Choose from the start menu: Programs > IMA > System Configuration.
7. From the Configure menu, choose Security.
8. From the Edit menu, choose Edit > AutoLogin.
9. Select a node and press Modify, choosing as Application User, System

Administrator.
10. Save and close the System Configuration program.
Warning!
Never use the IMA Startup icon in Program > IMA > IMA Startup if you need to
make it run after logoff.
1.3.6 Configure MINI-LINK MANAGER Network
Perform the following steps on your MINI-LINK MANAGER Server if it is used

as a workplace to connect to available MINI-LINK MANAGER Servers:
1 Open the System Configuration Utility program, which you will find in the
MINI-LINK MANAGER folder.
2 Select menu item Configure: Network...
3 Add desired remote MINI-LINK MANAGER Servers, for example LNT009.
Note: Always use the computer name of the remote MINI-LINK

MANAGER Server.
4 Push OK.
5 Select menu item File:Save to save your MINI-LINK MANAGER.scu file.
6 Select menu item File:Exit to Exit SCU configuration.
7 Stop and then start MINI-LINK MANAGER.
8/1553-AOM 901 015/1 Uen B -- 35

Figure 2 Configure MINI-LINK MANAGER network
1.4 MINI-LINK Medium Capacity Adaptation Configuration

General configuration of MINI-LINK MANAGER when using the MINI-LINK
Medium Capacity Adaptation is performed according to descriptions in
CONFIGURATION GUIDE and MINI-LINK Medium Capacity Adaptation Guide.
1.5 MINI-LINK HC Adaptation Configuration

General configuration of MINI-LINK MANAGER when using the MINI-LINK HC
Adaptation is performed according to descriptions in Configuration Guide.
1.5.1 Configuration
The MINI-LINK HC SNMP Agent has to be configured to send traps to the

IP-address of the MINI-LINK MANAGER Server. This is done launching the
Local Craft Tool (LCT) of each MINI-LINK HC equipment via WEB browser.
Log in to the MINI-LINK HC terminal that you want to configure following the
procedure below:
• Start your browser and type in the Address bar, the IP Address of the
specific MINI-LINK HC terminal.
• When the applet is loaded into the browser, you can log in to the LCT from
the Login window using these values:
36 8/1553-AOM 901 015/1 Uen B --

User Name: Administrator
Password: Administrator
Access Level: Administrator
• In the Link Manager window displayed select Setup -> DCN -> Interfaces
and press the SNMPv3 tab.
• Under Registered Managers press the Add button to add the MINI-LINK
MANAGER Server to the list of the defined SNMPv3 Managers.
• In the SNMPv3 New Manager window type the following:
Name: <name of the MINI-LINK MANAGER Server>_< password for the

SNMP user>
IP Address:<IP Address of the MINI-LINK MANAGER Server>
Group: V3Control
Password:<password for the SNMP user>
Confirm Password:<password for the SNMP user>
• Under Send traps, select yes to allow the equipment to send notifications
(trap messages) to the manager.
• Press OK to return to the Interfaces window.
• Close the Interfaces window.
• Close the LCT.
1.6 MINI-LINK TN Adaptation Configuration

General configuration of MINI-LINK MANAGER when using the MINI-LINK TN
Adaptation is performed according to descriptions in Configuration Guide and
MINI-LINK TN Adaptation Guide. The following additional configuration must
be done:
1.6.1 Installation
The MINI-LINK TN Adaptation is installed automatically during the MINI-LINK

MANAGER installation if the adaptation sub component MINI-LINK TN is
selected.
8/1553-AOM 901 015/1 Uen B -- 37

1.6.2 Additional Installation
All external software associated with this adaptation should have been installed
according to the roadmap. To find out what external software to install please
check the roadmap.
1.6.3 Configuration
The MINI-LINK TN SNMP Agent has to be configured to send traps to the

IP-address of the MINI-LINK MANAGER Server. This is done launching the
Local Craft Tool (LCT) of each MINI-LINK TN equipment via WEB browser.
Log in to the MINI-LINK TN terminal that you want to configure following the
procedure below:
1. Start your browser and type in the Address bar, the IP Address of the
specific MINI-LINK TN terminal.
2. You can log in to the LCT from the Login window using these values:
User Name: control_user

Password: ericsson
3. Click on the Configuration Tab and choose Configuration.
4. Press the Advanced Configuration button showed on the bottom

part of the frame.
5. In the Advanced Configuration frame fill the following fields:
Enable No- Set the Check Box

tifications:
SNMP < IP Address of the IMA Server>
Manager:
Port: SNMP port (by default is 161)
Version: set V3 Option Box
Then click on the Apply button and press the Save button showed on
the top-right corner of the frame.
6. Press Yes when the Save_Configuration Dialog appears.
7. Close the LCT.
1.7 NERA NEW Adaptation Configuration

General configuration of MINI-LINK MANAGER when using the Nera New
Adaptation is performed according to descriptions in Configuration Guide.
38 8/1553-AOM 901 015/1 Uen B --

1.8 SNMP MANAGER Adaptation Configuration (SNMP

MANAGER)
The installation of the SNMP Manager is done automatically during the
MINI-LINK MANAGER installation.
1.8.1 Change the SNMP Directory Into A Shared Directory
On the MINI-LINK MANAGER Server, the SNMP directory needs to be shared

across the network. This has to be done to enable remote configuration with
the SNMP Manager Configuration tool and MINI-LINK MANAGER MIB Admin.
This is done in the following way in the Windows 2000 Explorer:
• Go to C:\Ericsson\IMA\SNMP.
• Push the right mouse button and choose Sharing….
• Select Shared As and set Share name to ’SNMPAD’.
• User Limit should be Maximum Allowed.
• If you are a user that is going to configure the SNMP Manager, check under
Permissions… that the Type of access is set to Full Control.
• Press OK.
1.8.2 Configuration of Trap Destination for SNMP Proxy Agent
The systems monitored through the SNMP Manager Adaptation should be

configured to send traps to the MINI-LINK MANAGER Server on port 162.
1.9 SNMP Interface Configuration

The SNMP Interface configuration is installed automatically during the
MINI-LINK MANAGER installation if the adaptation sub component SNMP
Interface is selected.
1.9.1 Additional Installation
The SNMP Interface needs the Windows SNMP service installed. This should
have been done in the Windows 2000 configuration section in this manual,
according to the roadmap.
1.9.2 Stop the Windows 2000 SNMP Service

1 Start the Control Panel in My Computer and open Administrative Tools.
8/1553-AOM 901 015/1 Uen B -- 39

2 Select Services.
3 Select SNMP in the list.
4 Push Stop in the Services window. The list should read Stopped for SNMP
after a few seconds. If not, consult the Windows NT documentation.
5 Push Close in the Services window.
1.9.3 Configure Trap Destinations
In order to configure the SNMP Export Interface to send traps to other systems
you must configure trap destinations as follow:
1 Start the Control Panel in My Computer and open Administrative Tools.
2 Select Services.
3 Select SNMP Service in the list and then Properties…
4 Select Traps. Use the dialog to specify the computers that will receive traps.
This is done in the following way:
5 Community Name is chosen from the list or written in the text field. This is
the SNMP "pass-word" used when the traps are sent, for example, public.
Note: The community name must match the community name specified
in the NE Properties window/Address tab.
6 Push Add to List next to the field Community Name.
7 Push Add next to Trap Destinations to specify host names for all servers
that correspond to the given Community Name give a host name (if it is
known in your network) or SNMP address, for example 150.132.152.21.
8 Choose another Community Name if necessary and give a new group of

servers, and so on…
9 Push OK.
10 Please restart SNMP services.
11 Push Close in the Network window.
Caution!
If you have installed on MINI-LINK Manager Server also MINI-LINK E Adapter
Server set SNMP EMANATE Adapter for NT service to Manual.
40 8/1553-AOM 901 015/1 Uen B --

1.10 TL1 Interface Configuration

The TL1 Interface configuration is installed automatically during the MINI-LINK
MANAGER installation if the adaptation sub component TL1 Interface is
selected.
1.11 BNSI Interface Configuration

The BNSI Interface configuration is installed automatically during the MINI-LINK
MANAGER installation if the adaptation sub component BNSI Interface is
selected.
1.12 FTP Interface Configuration

The FTP Interface configuration is installed automatically during the MINI-LINK
MANAGER installation if the adaptation sub component FTP Interface is
selected.
1.13 Local Manager Installation

Now is the time for installation of the required local manager software. You
should have installed all needed 3rd party software prior to MINI-LINK
MANAGER Server Application installation according to the roadmap; section
3. For installation procedures on any local managers please refer to their
correspondent installation guides.
1.14 Uninstall MINI-LINK MANAGER Server

If the MINI-LINK MANAGER Server is configured to replicate inventory data
or config data to a MINI-LINK MANAGER Centralized Database, you must
follow the Section 1.14.1 on page 41 to disable the replication on the server.
Otherwise you can follow directly the Section 1.14.2 on page 42.
1.14.1 Disabling Replication on the MINI-LINK MANAGER Server
Presets:
Enterprise Manager SQL Server 2000 Client Tool has to be installed on a

machine that is situated on the same intranet of the MINI-LINK MANAGER
6.1 Server to uninstall.
On the MINI-LINK MANAGER 6.1 Server SQL Server 2000 service has to be
started and MINI-LINK MANAGER 5.1 Applications must be closed.
8/1553-AOM 901 015/1 Uen B -- 41

1.14.1.1 Enterprise Manager Configuration
1. From the start menu open SQL Server 2000 Enterprise Manager tool.
Under the Tree view right-click on the "SQL Server Group" and click on the
"New SQL Server Registration…" menu item.
2. Click Next on the "Welcome" window and then select the Server from the
list box that contains the MINI-LINK MANAGER 6.1 Server to uninstall. If
the name of the pc is not present, you can edit the name in the "Available
servers" edit box.
3. Click the Add -> button and then click Next.
4. Select SQL Server login as Authentication mode and click Next.
5. Insert the "sa" login and password (blank for default) and then click Next.
6. Click Next in the "Select SQL Server Group" window.
The last dialog appears to advise that the process is completed successfully.
Then, click Finish on the back dialog.
If the Server is registered, a new Server node is added under the "SQL Server
Group" node.
1.14.1.2 Removing the Replications
This chapter describes how to remove the replication from the server just
registered.
1. Select the Server node and open the Tools menu. Click, under the voice
"Replication", the "Disabling Publishing…" menu item.
2. Click the Next button in the "Welcome" dialog and select the Yes option on
the second wizard dialog. Then click the Next button.
If there is one publication on the server the last wizard dialog appears and then
you can click the Finish button. So the replication is removed.
If there is more than one publication, a tree view appears that shows all the
publications active (for IMA_INVENTORY or IMA_CONFIG database). Select
the publication and click Next until the wizard ends. Then click Finish.
1.14.2 Uninstall MINI-LINK MANAGER Server Procedure
Follow these steps to uninstall MINI-LINK MANAGER:
1. Shutdown MINI-LINK MANAGER. Make sure that Clients are not accessed
to this server.
2. Go into the Control Panel and open the "Add/Remove Programs" window.
Click on the Change/Remove button of the IMA program.
42 8/1553-AOM 901 015/1 Uen B --

3. Click Yes and confirm.
4. A dialog with no title appears. With the message "You must restart your
computer before reinstalling iFIX ". Click OK.
5. If a dialog asks to you to remove the shared files, answer clicking on the
No to All button.
6. Click OK at the end of un-installation.
Wait some minutes for the un-installation of other programs.
Note: The MINI-LINK MANAGER Server un-install program deinstall

the MINI-LINK E Adapter Client (default installed together with
MINI-LINK MANAGER Server setup).
The MINI-LINK E Adapter Server (the formerly called Netman

Server/ProxyAgent) will be also un-installed (if selected during
MINI-LINK MANAGER Server setup program).
7. If you want to remove the programs Adobe, DAO or TCL 8.0.4 click on
their Change/Remove button.
8. Reboot your PC.
Note: If you want to install newly MINI-LINK MANAGER Server without

the old configuration data, delete all folders under the path
C:\Ericsson\IMA\ except for the NE_Backups folder and the Erion
folder (if they are present).
If this server has been configured to receive alarms from one of

the Centralized DB servers, make sure that an alternative server
is configured to receive threshold alarms.
1.14.3 Uninstall MINI-LINK E Adapters Stand-Alone Programs
To remove the MINI-LINK E Adapter programs from the system:
1. Click the Start button.
2. Point to Settings, then click Control Panel.
3. Double-click Add/Remove Programs.
4. Select the programs you want to remove:
MINI-LINK E Adapter Server 1.3
MINI-LINK E Adapter Client 1.3
8/1553-AOM 901 015/1 Uen B -- 43

Note: If the MINI-LINK E Adapter Server is not shut down, the installation
program cannot uninstall the program. See Section 1.2.11.3 on
page 30 for instructions on how to shut down the MINI-LINK E
Adapter Server.
5. Click Add/Remove to remove it.
This will remove all files that were added in the installation. Any files added to
the MINI-LINK E Adapter directories after installation will have to be removed
manually by deleting them in Windows NT Explorer.
1.15 Upgrade NETMAN4.0 To MINI-LINK MANAGER 6.1

In order to upgrade Netman 4.0 to MINI-LINK MANAGER 6.1 the HW/SW
requirements for Netman 4.0 and MINI-LINK MANAGER 6.1 should be satisfied.
Netman 4.0 system (Server/Client/Proxy Agent) must be installed on a Server

PC equipped with Windows 2000 (SP2) operating system and Microsoft SQL
Server 2000 Standard Edition. If this server has the HW/SW characteristics
needed to install MINI-LINK MANAGER (according to section Section 1.2.3.1
on page 5), the upgrading procedure will install MINI-LINK MANAGER 6.1
system that integrates the MINI-LINK E Adapter system (that is, MINI-LINK E
Adapter Server/SNMP Proxy/Client). Follow the procedure below:
• Stop the Netman Server service (stopping it, the MINI-LINK Netman Proxy
Agent service will be stopped automatically).
• From SQL Server Service Manager start-up icon stop the SQL Server
service then exit from it.
• Install the Service Pack 3 of Microsoft SQL Server 2000 Standard Edition.
• Run MINI-LINK MANAGER 6.1 setup program according to Section 1.2.8

on page 18.
During the IMA/MLM installation, if Medium Capacity Adaptation has been

choosen and a previously Netman 4.0 installation has been found, the following
message boxes are shown:
"A previous Netman Client version is already installed. It is requested to

upgrade it to MINI-LINK E Adapter Client. You can exit from setup and upgrade
it or continue and upgrade it at the end of this installation. Do you want to exit
from setup?" (if the MINI-LINK E Adapter Client installation has been choosen).
1.16 Upgrade NETMAN 4.0 Launching MLE Adapters

Stand-alone Installation
In order to upgrade Netman 4.0 to MINI-LINK E Adapters the HW/SW
requirements for Netman 4.0 and MINI-LINK E Adapters should be satisfied.
44 8/1553-AOM 901 015/1 Uen B --

Netman 4.0 system (Server/Client/Proxy Agent) must be installed on a Server

PC equipped with Windows 2000 (SP2) operating system and Microsoft SQL
Server 2000 Standard Edition. If this server has the HW/SW characteristics
needed to install MINI-LINK MANAGER (according to section Section 1.2.3.1
on page 5), the upgrading procedure will install MINI-LINK MANAGER 6.1
system that integrates the MINI-LINK E Adapter system (that is, MINI-LINK E
Adapter Server/SNMP Proxy/Client). Follow the procedure below:
• Stop the Netman Server service (stopping it, the MINI-LINK Netman Proxy
Agent service will be stopped automatically).
• From SQL Server Service Manager start-up icon stop the SQL Server
service then exit from it.
• Install the Service Pack 3 of Microsoft SQL Server 2000 Standard Edition.
• Run MINI-LINK MANAGER 6.1 setup program according to Section 1.2.8

on page 18.
Choose MINI-LINK E Adapter or MINI-LINK E Adapter Client.
• During the MINI-LINK E Adapter Server installation program choose to

"Use the Current Database" in order to save the Netman 4.0 database.
• When the set-up of MINI-LINK E Adapter Server, MINI-LINK E Adapter

SNMP Proxy and MINI-LINK E Adapter Client have been completed, edit
the "C:\Winnt\system32\drivers\etc\services" file modifying the SNMP
PORT (see Section 1.2.4.2 on page 12) from the default value 161, used
by Netman Proxy Agent, to a new available one.
• Configure the E Adapter SNMP Proxy Agent to send traps to MINI-LINK

MANGER editing the file SNMPD.cnf according to the MINI-LINK Medium
Capacity Adaptation Guide.
• Start and configure MINI-LINK MANAGER according to Section 1.3 on

page 31.
• Start the E Adapter Server service (starting it, the MINI-LINK E Adapter
SNMP Proxy Agent service should be started automatically)
• Configure the adaptations and the interfaces supported by MINI-LINK

MANAGER according to Section 1.4 on page 36, Section 1.7 on page 38,
Section 1.8 on page 39, Section 1.9 on page 39, Section 1.10 on page
41,Section 1.11 on page 41 and Section 1.12 on page 41.
1.17 Upgrade MINI-LINK MANAGER 5.1 To MINI-LINK

MANAGER 6.1
The updating procedure from MINI-LINK MANAGER 5.1 to MINI-LINK
MANAGER 6.1 uses the Backup/Restore facilities provided by MINI-LINK
MANAGER.
8/1553-AOM 901 015/1 Uen B -- 45

To do it follows these steps:
• If MINI-LINK MANAGER 5.1 SP2 is not installed install it following the

relative SP2 installation procedure.
• If Microsoft SQL Server 2000 is installed, before the backup operation install
the Service Pack 3. If MSDE2000 is installed, upgrade MSDE to Microsoft
SQL Server 2000 (SP3) as described in Section 1.19.2 on page 47.
• Backup the MINI-LINK MANAGER 5.1 SP2 database from MINI-LINK

MANAGER Network Explorer according to MINI-LINK Manager
administration guide par 7.6.
• Wait until the message "Backup completed" is displayed. Save and store
the backup directory in a different path from C:\Ericsson\ima.
• Stop MINI-LINK MANAGER.
• Uninstall MINI-LINK MANAGER 5.1 SP2 as described in Section 1.14.2

on page 42.
• Install MINI-LINK MANAGER 6.1 as described in Section 1.2.8 on page 18.
• Replace the new backup directory with the previous saved directory.
• Start MINI-LINK MANAGER.
• Restore the MINI-LINK MANAGER database from IMA Network Explorer

according to MINI-LINK Manager administration guide par 7.6.
• Wait until the message "Restore completed" is displayed.
1.18 Ericsson Local Support Information

The MINI-LINK MANAGER help information contains also a MINI-LINK
MANAGER Help Desk page, which by default shows the 2nd line
support e-mail address. In order to give to the customer the Ericsson
Local Support information, you need to add that info by editing
theC:\Ericsson\IMA\Help\Local_support.txt text file (where C: is the
drive where you installed IMA). The MINI-LINK MANAGER Help Desk page will
automatically show all the info contained by this text file.
1.19 Appendices
1.19.1 Changing Computer Name
If the computer name is changed after MINI-LINK MANAGER is installed a

reinstallation of MINI-LINK MANAGER is necessary. Before proceeding, please
check Windows 2000 Server Configuration section.
46 8/1553-AOM 901 015/1 Uen B --

Complete the network configuration putting the new node name on the Domain
Controller and DNS server.
1.19.2 Upgrade MSDE To Microsoft SQL Server 2000 Standard Edition
The updating procedure from MSDE (Microsoft SQL Server Desktop Engine) to
Microsoft SQL Server 2000 database server uses the Backup/Restore facilities
provided by MINI-LINK MANAGER. To do it follow these steps:
• Uninstall MSDE2000.
• Install MSDE2000 SP3. See note below.
• Launch AttachSQLDatabases.exe file you can find it in MLM 6.1 CD in

the directory D:\DBUtils (substitute D for the appropriate letter of your
CD-ROM drive).
• Backup the MINI-LINK MANAGER database from MINI-LINK MANAGER

Network Explorer according to MINI-LINK Manager administration guide,
Paragraph 7.6.
• Wait until the message "Backup completed" is displayed.
• Stop MINI-LINK MANAGER.
• From SQL Server Service Manager start-up icon stop both services: SQL
Server and SQL Server Agent, then exit from it.
• Uninstall MSDE from Start->Settings -> Control Panel->Add/Remove

Programs.
• Run the script C: \Ericsson\Ima\bin\Delete DB File to remove old db files,

that is, the MSDE data and log files with *.mdf and *.ldf extensions.
• Refer to Section 1.2.7.1 on page 15 and Section 1.2.7.2 on page 16 to

install Microsoft SQL Server 2000 Standard Edition and Service Pack 3.
• Run the file C: \Ericsson\Ima\bin\ImaPostInstall.exe to configure all

MINI-LINK MANAGER databases: FM, PM, Inventory and Config.
• Start MINI-LINK MANAGER.
• Restore the MINI-LINK MANAGER database from IMA Network Explorer

according to MINI-LINK Manager administration guide, Paragraph 7.6.
• Wait until the message "Restore completed" is displayed.
Note: From MLM 6.1 CD copy msde2000 folder content to C:\MSDE

( for example) and launch the following command from
DOS prompt : Setup.exe /Settings C:\MSDE\Setup.ini /I
C:\MSDE\Setup\SqlRun01.msi /L*v C:\MSDE_setup.log.
8/1553-AOM 901 015/1 Uen B -- 47

1.19.3 MINI-LINK E Adapters Operational Considerations
If a terminal server (see Section 1.19.4 on page 48) is used to access

MINI-LINK sub-networks there must be an operational LAN/WAN (Local
Area Network/Wide Area Network) supporting TCP/IP (Transmission Control
Protocol/Internet Protocol) between MINI-LINK E Adapter Client and MINI-LINK
E Adapter Server. Minimum bandwidth is 64 kbit/s and the LAN/WAN must
allow SNMP traffic.
There must also be an operational LAN/WAN supporting TCP/IP between the

terminal server and MINI-LINK E Adapter Server, or a serial link between the
MINI-LINK network and MINI-LINK E Adapter Server.
The bandwidth depends on the number of sub-networks connected to the

terminal server. A bandwidth of minimum 19.2 kbit/s is recommended.
1.19.4 Requirements For The MINI-LINK E-Adapters Network
Requirements for the MINI-LINK network:
• All MINI-LINK equipment in a network that is supervised by MINI-LINK E

Adapter, must be installed and set up with the MSM program.
• All MINI-LINK equipment in the network must be connected via the

communication channels for control and supervision.
Possible ways of connecting MINI-LINK E Adapter to a network are listed in the

following sections. For further information on the actual setup of the network,
see the documentation for the equipment used.
1.19.4.1 Terminal Server
The terminal server provides the connection between the serial interface of
a MINI-LINK network and the MINI-LINK E Adapter Server workstation. A
terminal server is only needed if more than one sub-network is present.
Ericsson recommends:
• Cisco Access Server Model 2509 (provides 8 asynchronous RS 232C ports)
or
• Cisco Access Server Model 2511 (provides 16 asynchronous RS 232C

ports)
Both models can be equipped with LAN or WAN interfaces for most data
network standards, such as Ethernet, Token Ring, X.25, ISDN, and so on.
The number of terminal servers depends on the design of the data

communication network. At least one Model 2509 is required per 800 hops.
48 8/1553-AOM 901 015/1 Uen B --

Note: You will find the configuration procedure for Cisco Access Server Model
2509 in Section 1.19.4.14 on page 57.
The maximum distance between the terminal server and the MINI-LINK network
is approximately 15 meters (see Section 1.19.4.3 on page 49). If longer, it can
be connected via a modem (see Section 1.19.4.4 on page 49).
1.19.4.2 Single Port Terminal Server
A single port terminal server is used for building a communication channel

between a MINI-LINK E subnetwork and MINI-LINK E Adapter via a TCP/IP
network. See Section 1.19.4.7 on page 52 for information on how to configure
the Patton Model 2120 Single Port Terminal Server.
1.19.4.3 Direct Cable
Sub-networks can be directly connected to the serial communication port on

the PC.
The MINI-LINK network should be connected with a straight cable from the
MINI-LINK element cabling to the V.24 spider connection cabling connected
to the terminal server.
Note: The maximum distance between the terminal server and the MINI-LINK
network is approximately 15 meters.
1.19.4.4 Modem
If the terminal server cannot be installed sufficiently close to the MINI-LINK

network to allow direct connection of the RS 232C cabling, an asynchronous
modem can be used. Modems can also be used to connect the MINI-LINK E
Adapter Server to MINI-LINK sub-networks.
1.19.4.5 Setup of a Modem Connection
The PC is connected to the modem via the serial communication port, and the
modem is connected to the MINI-LINK equipment according to Table 3 on page
51,Table 4 on page 51 and Table 5 on page 52.
M o d e m B P S T N M o d e m A
M IN I- L IN K e q u ip m e n t
Figure 3 MINI-LINK Supervision via Modems
8/1553-AOM 901 015/1 Uen B -- 49

The calling and modem configurations must be done outside the MINI-LINK E
Adapter Server, with terminal-emulation software such as Telnet.
The main requirements for the modems are:
• 1200 bits/s
• 8 data bits
• 1 stop bit
• no parity
• no flow control
Note: The AT commands in Table 1 on page 50 and Table 2 on page 50 are

examples of how the modems can be configured. Please refer to the
documentation that came with your modem for details.
Table 1 Example of AT Commands to Call from Modem to MINI-LINK

Modem A -> MINI-LINK
Command Function
AT&F0 Load factory default values from ROM
ATS0=2 Automatic answer after two signals
AT&D0 Ignore DTR (MINI-LINK does not support DTR)
AT&E3 No modem initiated flow control
AT&E14 Data compression disabled
AT$SB1200 Set serial port baud rate to 1200 bits/s.
AT$MB1200 Set modem baud rate to 1200 bits/s.
ATQ1 Suppress result codes (no OK answer after this
command).
(1)
AT&W0 Save configuration.
(1) The saved configuration is reloaded at modem power-up, and needs therefore only to be
done once.
Table 2 Example of AT Commands to Call from Modem to MINI-LINK E

Modem B -> MINI-LINK E Adapter Server
Command Function
AT&F0 Load factory default values from ROM
AT&D0 Ignore DTR to be able to exit the Terminal
program without disconnecting.
AT&E3 No modem initiated flow control
50 8/1553-AOM 901 015/1 Uen B --

Table 2 Example of AT Commands to Call from Modem to MINI-LINK E

AT&E14 Data compression disabled
AT$SB1200 Set serial port baud rate to 1200 bits/s.
AT$MB1200 Set modem baud rate to 1200 bits/s.
(1)
AT&W0 Save configuration.
(1) The saved configuration is reloaded at modem power-up, and needs therefore only to be
done once.
1.19.4.6 Modem Connection to MINI-LINK Equipment
The tables below give guiding information on how to connect the modem
to MINI-LINK equipment (cable to Modem A in Figure 3 on page 49). For
connection between PC and modem, use a standard RS 232C cable. Consult
the modem manual for detailed instructions.
Table 3 Connection of Modem to MINI-LINK E Equipment; O&M port

Connection of 25-pin RS 232C (or V.24) connector Connection to MINI-LINK E
equipment;O&M port
Pin Name Note Name Pin
2 TD, Transmit To modem O&M_RD_104 2
Data
3 RD, Received From modem O&M_RD_103 3
Data
7 SG, Signal — 0V 5
Ground
Table 4 Connection of Modem to MINI-LINK C and MkII Radio

Connection of 25-pin RS 232C (or V.24) connector Connection to MINI-LINK C and
MkII radio
Pin Name Note Name Pin
2 TD, Transmit To modem RS 232C from P1:5 or P3:B02
Data radio
3 RD, Received From modem RS 232C to radio P1:18 or P3:B04
Data
7 SG, Signal — 0V P2:6 or P3:C02
Ground
8/1553-AOM 901 015/1 Uen B -- 51

Table 5 Connection of Modem to MINI-LINK C and MkII SMM; BAY/USER

Connection of 25-pin RS 232C (or V.24) Connection to MINI-LINK C and MkII SMM;
connector BAY/USER
Pin Name Note Name 1+0; Pin 1+1; Pin
2 TD, Transmit To modem RS 232C 9 5
Data from radio
3 RD, From modem RS 232C to 28 18
Received radio
Data
7 SG, Signal — 0V 11 17
Ground
1.19.4.7 Patton Model 2120 Single Port Terminal Server
The Patton Model 2120 Single Port Terminal Server (TS) is used for building a
communication channel between a MINI-LINK E sub-network and MINI-LINK E
Adapter via a TCP/IP network. The main function of the TS is to convert signals
between the V24/RS232 and TCP/IP standards.
For more information, see the User Guide included in the delivery.
Figure 4 Overview
The configuration of the TS is done by connecting it to a PC with terminal

emulation software, such as HyperTerminal. After the configuration is
completed, the TS is connected to the O&M port on MINI-LINK E equipment.
Using the gender changer, connect the RS232 cable on the TS to an unused
serial port on the PC (typically COM1 or COM2).
52 8/1553-AOM 901 015/1 Uen B --

Note: Your model of PC may need to be turned off before you connect the
PC cable to a serial port. If in doubt, turn off your PC while connecting
the PC cable to the serial port.
1.19.4.8 Terminal Emulation Settings
Using the following parameters, configure your terminal emulation software

to establish a connection to the TS.
Bite rate 9600

Parity None
Data bits 8
Stop bits 1
Flow control None
Example: HyperTerminal Settings
1. Start a HyperTerminal session. The HyperTerminal is easiest found on

the Start menu: Start > Programs > Accessories > HyperTerminal >
HyperTerminal.
2. If the Connection Description dialog box does not open, click New
Connection on the File menu.
3. In the Name box, type a name for the new connection, for example TS.
Figure 5 Connection Description
4. Click OK.
5. In the Connect using list, select the serial port to use (typically COM1 or
COM2).
8/1553-AOM 901 015/1 Uen B -- 53

Figure 6 Connect
6. Click OK.
7. In the COM Properties dialog box, specify these Port settings:
Bite rate 9600

Parity None
Data bits 8
Stop bits 1
Flow control None
Figure 7 COM 1 Properties
54 8/1553-AOM 901 015/1 Uen B --

8. Click OK.
If no connection is established:
1. On the File menu, click Properties.
2. In TS Properties dialog box, click the Settings tab.
Figure 8 TS Properties
3. Select the Windows Keys option.
4. In the Emulation list, select VT100.
5. Click OK.
6. If no connection is established at this point try rebooting [power cycle]

the terminal server.
1.19.4.9 Configuring The TS For A MINI-LINK E Subnetwork
The terminal server is set to factory default values. It is necessary to change

some values to fit the MINI-LINK E subnetwork.
1. Set the data rate to 1200 baud:
TS> configure eia232 interface datarate 1200
2. Set the RS-232 Physical Port on the serial interface:
TS> configure eia232 interface dtedce DTE
8/1553-AOM 901 015/1 Uen B -- 55

3. Set the period of time (in minutes) that the TS will close an inactive
connection to the serial interface:
TS> configure eia232 interface inactiveto number_of_minutes
Note: This time must be longer than the polling time set in MINI-LINK
E Adapter.
4. Set the protocol to rawtcp:
TS> configure eia232 interface protocol rawtcp
5. Set the local port number [0-65535]:
TS> configure eia232 rawtcp_telnet locport port_number
6. Disable char string for termination of the connection on the serial interface:
TS> configure eia232 rawtcp_telnet sestermchar 00
7. Disable DHCP:
TS> configure system dhcpena no
8. Set the IP address to the terminal server:
TS> configure system ipaddrcfg IP_address
9. Set the IP address to the terminal server:
TS> configure system subnetcfg IP_address
10. Save the image:
TS> configure activate
Reboot [power cycle] the terminal server. The new configuration is now active.
1.19.4.10 Connecting The TS To An O&M Port
Connect the RS232 cable on the TS to the O&M port on MINI-LINK equipment.
1.19.4.11 Connecting the TS to the TCP/IP Network
Connect the TS to the TCP/IP network using the 10BASE-T LAN interface.
1.19.4.12 Configuring MINI-LINK E Adapter
Configure the subnetwork parameters in MINI-LINK E Adapter. For more

information, see MINI-LINK Medium Capacity Adaptation Guide, section
"Adding all Sub-Networks in the MINI-LINK network".
56 8/1553-AOM 901 015/1 Uen B --

1.19.4.13 Reconfiguring the TS
Once the TS has been configured and installed the initial HyperTerminal speed
is no longer appropriate. It must be changed to 1200 bits/s if the serial interface
should be able to work. However, from now on it is more convenient to use a
Telnet session for configuration (if needed).
1. On the Start menu, click Run.
2. In the Open box, type Telnet IP_address, where IP_address is the IP

address of the TS.
3. Click OK.
The PC and the TS must in this case be connected via a LAN connection.
1.19.4.14 Cisco Access Server Model 2509
1
0
A S Y N C 1 -8 A U I S E R IA L 0 S E R IA L 1 O n /o ff P o w e r
C O N S O L E A U X s w itc h
Figure 9 Cisco Access Server Model 2509
1.19.4.15 Connection
For connection to the ASYNC 1-8 port, use the octopus cable with a connector
for the ASYNC 1-8 port in one end and eight 8-pin RJ-45 connectors in the
other. The RJ-45 connectors can be connected to (up to) eight MINI-LINK
sub-networks. (The octopus cable is not included, and must be ordered
separately).
Table 6 8-pin RJ-45 Connector for Connection to MINI-LINK Equipment

Pin no Signal Figure
1
2
8
1
3 RXD
4 RXD/GND
5 TXD/GND
6 TXD
7
8
8/1553-AOM 901 015/1 Uen B -- 57

The AUX port on the Cisco terminal server can be used for a ninth MINI-LINK
sub-network.
Table 7 8-pin RJ-45 Connector for a Ninth MINI-LINK Sub-network

Pin no Signal Figure
1
2
8
1
3 RXD
4 RXD/GND
5 TXD/GND
6 TXD
7
8
Note: Cisco Access Server model 2511 has two identical ASYNC ports
(ASYNC 1-8 and ASYNC 9-16), and can be used for 16 MINI-LINK
sub-networks.
1.19.4.16 Configuration
Before the Cisco Access Server can be used, each port used must be
configured to provide the characteristics required by the MINI-LINK Networks.
The Cisco Access Server has to be installed and given a specific IP address
before the configuration can be done. You also have to know the two passwords
for the server. See the Cisco manuals for further instructions on these
procedures.
To configure the Cisco Access Server you have to log on to the server. This is
done by starting a Telnet session with the Access Server. The session can be
started from any workstation on the same LAN/WAN as the Access Server.
The actions below are performed from any workstation with access to the
Access Server (either via LAN, WAN or modem).
The password1 and password2 in Step 3 and Step 5 should be replaced with
valid passwords. See the Cisco Manuals. The cisco> prompt shows that a view
connection is established and the cisco# prompt shows that the configuration
mode is entered.
1. Start the application that provides a Telnet connection. The Telnet program
is easiest found on the Start menu:
Start > Programs > Accessories > Telnet
58 8/1553-AOM 901 015/1 Uen B --

2. Establish a Telnet connection to the Cisco Access Server administration

port by entering the IP address or the host name of the Cisco Access
Server.
3. Enter the Access Server password:
Password: password1
4. Enable the configuration authority:
cisco> enable
5. Enter the configuration password:
Password: password2
Figure 10 The Telnet Window
6. To start changing the configurations, enter:
cisco# conf terminal
Configure a Line for MINI-LINK Connection
It is now possible to configure individual Access Server ports. In the

example below port number 5 on the Access Server is configured for a
piece of MINI-LINK equipment.
Repeat Step 7 to Step 9 for every port used for MINI-LINK connections.
7. Select the line to configure:
cisco(config)# line 5
Line 5 represents Port 4005 for the Access Server. This port number
is entered in the MINI-LINK E Adapter Server installation program, see
Section 1.2.11 on page 26.
8. Configure the selected line:
8/1553-AOM 901 015/1 Uen B -- 59

cisco(config-line)# speed 1200
cisco(config-line)# parity none
cisco(config-line)# stopbits 1
cisco(config-line)# databits 8
cisco(config-line)# flowcontrol NONE
cisco(config-line)# no exec
cisco(config-line)# no exec-banner
cisco(config-line)# telnet transparent
cisco(config-line)# telnet refuse-negotiations
cisco(config-line)# transport input all
cisco(config-line)# transport output all
cisco(config-line)# modem InOut
The commands above may be entered in any order.
9. When all parameters are set, exit the config-line mode:
cisco(config-line)# exit
Configure a Time-out
The Access Server needs to have a time-out if there is no traffic from the
MINI-LINK E Adapter Server. In this case all connections between the
MINI-LINK network and the MINI-LINK E Adapter Server are removed in the
Access Server. This ensures that the MINI-LINK E Adapter Server is able
to reconnect.
10. Select all tty lines:
cisco(config)# line tty 1 8
11. Set the time-out to one minute:
cisco(config-line)# session-timeout 1
Save and Exit
12. Exit the configuration mode. Type and save the configuration in both the
running and boot memory:
cisco(config-line)# exit
60 8/1553-AOM 901 015/1 Uen B --

cisco(config)# exit
cisco# write memory
13. . Close the Telnet connection:
cisco# exit
1.19.4.17 Other Useful Commands
Here are a few more useful commands for the Cisco Access Server. They are
all used in the Telnet session window.
? Gets all available commands.

Show Shows the settings you have entered.
running-config Shows the settings you have entered.
reload Reboots the Cisco Access Server.
show line 5 Checks the configuration for line 5.
1.19.5 Communication Parameters
The communication parameters control how MINI-LINK E Adapter Server

communicates with the MINI-LINK network or sub-networks. Normally the
default values of the parameters are suitable for most networks and therefore
need not to be changed. However, should problem occur with lost connections
(status No Conn) to MINI-LINK terminals, the parameters can be optimised
using a utility application. This situation normally appears only in large networks
(1500-2000 terminals).
Caution!
You should not modify the communication parameters if you do not have good
knowledge about MINI-LINK networks.
To change the communication parameters:
1. In the MINI-LINK E Adapter Server installation directories, locate and

double-click the regpar.exe file.
2. Under Network parameters, set the values of the parameters described in

Table 8 on page 62.
Note: The values can be changed in run-time and have immediate impact.
Click Default to reset the network parameters to their default values.
8/1553-AOM 901 015/1 Uen B -- 61

Table 8 Network Parameters

Parameter Description Recommended [Default]
value
Background Poll Interval The time between 45 [15] seconds
background polling each
terminal. A larger value
will decrease the load on
MINI-LINK E Adapter Server,
which reduces the risk of
losing sub-networks.
Performance Poll Interval The time between polling 45 [30] seconds
each terminal for performance
data. A larger value
will decrease the load on
MINI-LINK E Adapter Server,
which reduces the risk of
losing sub-networks.
AGC Poll Interval The time between polling 45 [30] seconds
each terminal for AGC data.
A larger value will decrease
the load on MINI-LINK
E Adapter Server, which
reduces the risk of losing
sub-networks.
3. In the Sub-network ID list under Sub-network parameters, select the ID

of the sub-network you want to change communication parameters for.
You can also select All subnets to apply the same settings for all your
sub-networks.
4. Set the values of the parameters in Table 9 on page 62.
Note: The MINI-LINK E Adapter Server has to be restarted before changes of

these parameters are activated. Click Default to reset the sub-network
parameters to their default values.
Table 9 Sub-Network Parameters

Parameter Description Recommended [Default]
value
Front end connection test The interval between polling 180 [60] seconds
interval the front end terminal. A
larger value will decrease the
load on MINI-LINK E Adapter
Server, which reduces the
risk of losing sub-networks.
62 8/1553-AOM 901 015/1 Uen B --

Table 9 Sub-Network Parameters

Max allowed response time The response time from the 60 [30] seconds
from front end terminal front end terminal, before
outstanding commands time
out. A larger value will allow
a longer time for MINI-LINK
E Adapter Server to receive
and handle responses.This
reduces the risk of time-outs
that cause the connection to
be regarded as lost.
No of attempts to contact the The number of attempts 3 [3] attempts
front end terminal to connect to the front end
terminal, when the connection
fails. A larger value will allow
a longer time for MINI-LINKE
Adapter Server to receive
and handle responses. This
Max allowed response time The response time from 60 [15] seconds
from terminals in the network MINI-LINK terminals, before
outstanding commands time
out. A larger value will allow
a longer time for MINI-LINK
E Adapter Server to receive
and handle responses. This
5. Click OK to apply the settings and close the application.
-or-
Click Cancel to close the application without applying the settings.
-or-
Click Reset to reset all values to the settings they had when you opened
the application.
1.19.6 The Network.Ids File
The Network.ids file holds information about all managed MINI-LINK terminals.
The .ids extension shows that the file is a MINI-LINK E Adapter Server Network
List.Example 1 on page 64 shows how the parameters are structured in each
record.
8/1553-AOM 901 015/1 Uen B -- 63

ID -> Type -> Sub-net ID -> Site ID -> Hop Side ID -> Hop ID -> Far Hop Side ID
-> Traffic Rate -> Description
Example 1 Record Structure in the MINI-LINK E Adapter Server Network

List File
The different parameters in Example 1 on page 64 are separated by a tabulation

character (->). The parameters are defined in Table 10 on page 64.
Table 10 Parameters in the MINI-LINK E Adapter Server Network List File

Parameter Description
ID Equipment ID (Mandatory)
Type Max 10 char (Mandatory)
Sub-net ID Integer (Mandatory)
Site ID Max 64 char
Hop Side ID Max 64 char
Hop ID Max 64 char
Far Hop Side ID Max 64 char
Traffic Rate Max 10 char
Description Max 255 char
1.19.7 The Client Network.Id File
The client Network List files hold information about MINI-LINK E Adapter Client
Network Lists. The .id extension shows that the file is a MINI-LINK E Adapter
Client Network List.
ID -> Type -> Sub-net ID -> Grouping
Example 2 Record Structure in the MINI-LINK E Adapter Client Network

List File
The different parameters in Example 2 on page 64 are separated by a tabulation

character (->). The parameters in Example 2 on page 64 are defined in Table
11 on page 64.
Table 11 Parameters in the MINI-LINK E Adapter Client Network List File

Parameter Description
ID Equipment ID (Mandatory)
Type Max 10 char (Mandatory)
Sub-net ID Integer (Mandatory)
Grouping Max 64 char
64 8/1553-AOM 901 015/1 Uen B --

03 - Server Installation Guide

Uploaded by

Document Information

Original Title

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

03 - Server Installation Guide

Uploaded by

Copyright:

Available Formats

MINI-LINK Manager 6.

Server Application Installation

© Ericsson AB 2003 - All Rights Reserved

8/1553-AOM 901 015/1 Uen B --

1 MINI-LINK MANAGER Server Application Installation 1

8/1553-AOM 901 015/1 Uen B --

8/1553-AOM 901 015/1 Uen B --

1 MINI-LINK MANAGER Server Application

1.1.1 MINI-LINK MANAGER Distribution Package

Before installing MINI-LINK MANAGER check the content of your MINI-LINK

CD \ordered item MINI-LINK MINI-LINK MINI-LINK

8/1553-AOM 901 015/1 Uen B -- 1

• MINI-LINK MANAGER User manual

• Software license agreement

The MINI-LINK MANAGER is available in 3 versions: MINI-LINK MANAGER

1.1.2 Software Key Installation

Included with MINI-LINK MANAGER is a software key. MINI-LINK MANAGER

To install a software key:

• Remove any connections to your computer parallel port.

2 8/1553-AOM 901 015/1 Uen B --

1. Windows 2000 Server installation with SP3

2. Windows 2000 Server installation and configuration

3. 3rd party software (required by adaptations, interfaces and local managers)

5. MINI-LINK MANAGER Server Application installation

6. MINI-LINK MANAGER Server Application configuration

7. Adaptations and interfaces configuration

8. Local manager installation

1.2.1 3rd Party Software Requirements

8/1553-AOM 901 015/1 Uen B -- 3

MINI-LINK MANAGER Option 3rd party software required

Instruction: Determine what components to install by looking at the leftmost

4 8/1553-AOM 901 015/1 Uen B --

For installation procedures of any local managers please refer to their

1.2.3 Windows 2000 Server

1.2.3.1 Basic Server Requirements

Central Processor Unit Intel Pentium III 1,266 MHz

8/1553-AOM 901 015/1 Uen B -- 5

1.2.3.2 Verify the Contents of Windows 2000 Server Package

• The installation program should start automatically.

• Insert the CD and locate the \BootDisk folder.

1.2.3.3 Booting Troubles

6 8/1553-AOM 901 015/1 Uen B --

1.2.3.4 Partitioning the Hard Drive or Logical Drive on RAID Set

1.2.3.5 Computer Name (Max 8 Characters)

1.2.3.6 Page File

Initialise DrWatson by starting a DOS prompt and type:

Then start the DrWatson control window by typing:

8/1553-AOM 901 015/1 Uen B -- 7

1.2.3.8 Windows SNMP Service

The Windows SNMP service should be installed. Make sure by going

1.2.3.9 Configuring the Server On The Network

• The Domain Controller (DC) the server will have to join

• The DNS server installed into the domain

• The IP address and subnet mask to be configured for the server

8 8/1553-AOM 901 015/1 Uen B --

1.2.3.10 Domain Controller

A Domain Controller must exist on the network otherwise the MINI-LINK

For W2K domain controller installation a static IP address is needed. If a

1. During the W2K installation the computer must configured as member of

2. When the W2K installation is finished, launch the command dcpromo.

10. In "Active directory installation Wizard" Windows message appears, press

14. In the Summary window press Next.

8/1553-AOM 901 015/1 Uen B -- 9