06 Administrator Guide

MINI-LINK Manager 6.
Administrator Guide
E
Copyright
© Ericsson AB 1996-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.
9/1553-AOM 901 015/1 Uen A --

MINI-LINK Manager 6.1
Contents
1 Administrator Guide 1
1.1 Introduction 1
1.2 System Configuration 1
1.3 Users And Security 6
1.4 Security Configuration 12
1.5 Backup 15
1.6 Backup/Restore of MINI-LINK MANAGER Database 16
1.7 Backup/Restore of Customised Pictures 19
1.8 Backup And Restore Of The Mini-Link E Adapter Database 21
1.9 Centralized DB Administration 34
1.10 PM and FM Database Settings 38
1.11 Cold Standby 44
1.12 System Shutdown 50
9/1553-AOM 901 015/1 Uen A --

9/1553-AOM 901 015/1 Uen A --

1 Administrator Guide
1.1 Introduction
The Administrator guide describes the working procedures for the typical
system administrator user. For access to the operations in this chapter you will
have to be logged in as MINI-LINK MANAGER System Administrator.
Note: Many operations are performed using the System Configuration Utility
(SCU). Whenever configuration changes have been made using this
utility, MINI-LINK MANAGER must be restarted in order for the changes
to take affect.
1.2 System Configuration
1.2.1 Configure IMA Network
Refer to the MINI-LINK MANAGER Client Application Installation Guide or

MINI-LINK MANAGER Server Application Installation Guide.
1.2.2 IMA Database Settings
From the frame "Database settings" of the "System Settings" tab, you can
decide how many NEs IMA Database can support and select a new destination
path used for the Backup and the Restore features. The default path used for
the Backup and the Restore features is "…\Ericsson\IMA\Backup". But if you
want, you can change this path clicking on the Browse button and selecting the
new directory. The following picture shows for example the new Backup/Restore
directory as "D:\New Backup Directory". The default size of the IMA database
supports 1000 NEs. To change the size of the IMA database do as follows:
1 Backup current IMA DB on the MINI-LINK MANAGER Server (optional).

Refer to Section 1.5 on page 15.
2 In the IMA Network Explorer, select the MINI-LINK MANAGER Server,

right-mouse click and select menu item Properties.
3 Select the System Settings tab and enter the new max number of NEs
(1-10000) in the new max size field. In the figure below the database size is
changed from max 1000 NEs to max 10000 NEs.
4 Push OK.
5 In the information window that pops up push OK.
6 Shut down the MINI-LINK MANAGER Server as described in Operator

Guide.
9/1553-AOM 901 015/1 Uen A -- 1

7 Delete the \Ericsson\Ima\pdb\IMA.db database file on the MINI-LINK

Manager Server.
8 Start the MINI-LINK MANAGER Server.
9 You can verify that the database size has actually changed by opening the
MINI-LINK MANAGER Server Properties dialog again and check that the
Current max size now also has changed.
10 Restore the IMA DB from backup (optional).
Figure 1 System Settings
1.2.3 Configure Alarm Auto Sync Mode
By default, a MINI-LINK MANAGER Server automatically performs alarm

synchronization for all NE(s) where automatic alarm synchronization is
enabled (see Configuration Guide). This behavior permits the operator to
avoid performing manually alarm synchronization whenever a NE enters the
state "alarm synchronization needed". The alarm Auto Sync mode can be
changed in the following way:

right-click with mouse and select menu item Properties.
2 Select the System Settings tab.
3 When Enabled is checked the auto alarm sync function is enabled. Then a
delay can be entered that is the number of seconds the IMA Server waits
2 9/1553-AOM 901 015/1 Uen A --

before alarm synchronization is started. The value should be in the range

0-900 seconds. The default is 1 second.
4 When you are done with the changes push OK.
6 Stop and then start the MINI-LINK Manager Server.
1.2.4 Configure Alarm Acknowledgement Mode 1.
MINI-LINK MANAGER supports three modes for alarm acknowledgement:
• Alarm disappears from alarm list when clearedmeans that an alarm

will disappear from the alarm list when it has cleared even if it have
not been acknowledged by an operator yet. MINI-LINK MANAGER will
then automatically acknowledge the alarm. An operator may manually
acknowledge an alarm before it has cleared but this is not required for the
alarm to disappear.
• Alarm disappears from alarm list when acknowledged and cleared

means that the alarm disappears from the alarm list when it has been
cleared and also acknowledged by an operator.
• Alarm disappears from alarm list when acknowledged twice and

cleared means that an alarm must be acknowledged at least once after it
has cleared even if it already has been acknowledged. Alarm must always
be acknowledged twice.
9/1553-AOM 901 015/1 Uen A -- 3

The automatically acknowledge circuit alarms when all related

equipment alarms have been acknowledged option is not meaningful for
the MINI-LINK Manager product. The Alarm acknowledgement mode can
be changed in the following way:

right-click with mouse and select menu item Properties.
2 Select the System Settings tab.
3 Select the desired alarm acknowledgement mode.
4 Push OK.
6 Stop and then start the MINI-LINK MANAGER Server.
1.2.5 Automatic Alarm Printing
For automatic printouts of alarms do as follows:
4 9/1553-AOM 901 015/1 Uen A --

Figure 4 Automatic alarm printing
Table 1 Automatic Alarm Printing

1 Shutdown IMA
In the IMA startup window, select the menu item Options:Shutdown
IMA.
2 Start the System Configuration Utility
From the Windows 2000 taskbar, select Start:Programs:IMA:System
configuration
3 Open the Alarm Configuration dialog
Select menu item Configure:Alarms in the System Configuration Utility
window.
4 Enable one or many alarm printers in the SCU:Alarm configuration
window
For each alarm printer push the Modify button and select printer device
to use and alarm areas to print.
5 Push the OK button in the Alarm Configuration window.
6 Save the configuration
Select File:Save menu item in the SCU window.
7 Start IMA.
All subsequent alarms will now be printed on the selected printers.
9/1553-AOM 901 015/1 Uen A -- 5

1.2.6 Change of Host Name
When changing the host name all MINI-LINK MANAGER configuration data will
be lost, follow these steps to change the host name:
• Uninstall MINI-LINK Manager EM, according to the Server Installation

Guide and Client Installation Guide.
• Uninstall MSDE (Control Panel->Add/Remove Programs "MS SQL Server

Desktop Engine").
• Change the host name (Control Panel->Network).
• Reboot computer.
• Install MSDE, see client/server installation guides.
• Install MINI-LINK MANAGER EM (no need to reinstall Windows2000 or IMA

3rd party products), see client/server installation guides.
1.3 Users And Security

The MINI-LINK MANAGER has a flexible and powerful handling of users and
security. It is possible to modify almost any aspect of users and security.
At installation, MINI-LINK MANAGER generates two default user categories

and four default user identities.
Table 2 Default User Categories (User Groups)

Category Description
IMA OPERATORS The IMA OPERATORS category allows for operating
the system from the IMA Explorer and the IMA
WorkSpace applications. For more information of
typical operator actions, refer to the OPERATOR
GUIDE.
IMA The IMA CONFIGURATORS category allows
CONFIGURATORS for operating the system and also for modifying
configuration parameters of the network data objects
and for developing new maps. Fore more information
of configuration actions, refer to the CONFIGURATOR
GUIDE.
6 9/1553-AOM 901 015/1 Uen A --

Table 3 Default User Identities

User Name Login Initial Category Description
Name password membership
GUEST SYSTEM guest guest No category The guest user
has no security
privileges.
ADMINISTRATOR admin admin IMA CONFIGU- The admin user has
RATORS all security privileges
enabled, including
the privilege to create
other users
IMA OPERATOR opera opera IMA As defined by
OPERATORS user category IMA
OPERATORS.
IMA config config IMA CONFIGU- As defined by
CONFIGURATOR RATORS user category IMA
CONFIGURATORS.
Note: Please make sure that the default passwords are changed after the
installation.
1.3.1 MINI-LINK E Adapter User Categories
MINI-LINK E Adapter has three user categories:
• System Administrator - The System Administrator is responsible for

installing and configuring the system. After the system is set up, the System
Administrator will only log in to change equipment in the system and for
periodical maintenance. Only one System Administrator at a time can
beconnected to a MINI-LINK E Adapter Server.
It is only the System Administrator who can change the contents

of MINI-LINK E Adapter Server. The changes made by the Syste
Administrator affect the Network List in MINI-LINK E Adapter Server.
• Control Operator - The Control Operator has all the privileges necessary to
operate the MINI-LINK network from MINI-LINK E Adapter Client.
The Control Operator can change most parameters for his personal view of
the system and view all the system parameters.
The Control Operator procedures are described in the online Help that
comes with the software.
• View Operator - The View Operator always works with the parameters for
his personal view of the system, but is not able to save any changes. The
View Operator can view most of the system parameters.
9/1553-AOM 901 015/1 Uen A -- 7

The View Operator procedures are described in the online Help that comes
with the software.
1.3.1.1 Setting The Passwords
The System Administrator and Control Operator categories are protected by

passwords. To prevent unauthorized access to the system, new passwords
must be set for the System Administrator and Control Operator categories:
1. On the Config menu, click Login.
2. Select the System Administrator option.
3. In the Old password box, type 1111.
4. In the New password box, type a new password.
5. In the Confirm box, type the new password again, to verify that it is correct.
6. Click Save.
7. Repeat this procedure for the Control Operator user category.
1.3.2 Security Area
A Security Area is a logical group of items (NE, Adaptations, Sub-Networks),

which can be accessed or handled by different users, according to their
Group (IMA Operator or IMA Configurator, notice that an Administrator is a
user belonging to Configurator group with all applications enabled). A user
shall access all the items belonging to the Security Areas configured for him
in the System Configuration (selecting from the menu "Configure" and then
"Security"). Security Areas can be assigned to a map as well. There are 16
possible values for the Security Areas, A through P. The number and name of
the security areas is predefined by the system.
Also note that Security Area is something completely different from alarm area
(also known as subnetwork). Network elements in different subnetworks (alarm
areas) can still belong to the same Security Area.
The Items of the network included in MINI-LINK Manager can be grouped in

Security areas. Security can be configured to limit different users write and
execute access towards network items.
Each user can be granted access to a list of security areas. The network items
that can be assigned to a security area are the following:
• Network Elements
• Adaptations
• Workspace Pictures
• Workspace Maps
8 9/1553-AOM 901 015/1 Uen A --

Possible values for the security areas are described in the table below:
Table 4 Security Area access rights

None Read only for all Operators. Configurators have no security
limitation and can read write and execute commands.
All No security limit for Operators or Configurators.

A...P User must have specific security level between A and P.
Figure 5 Security Configuration — User Profile
The Security Area for a Network Element can be set by right clicking on its icon
in the Nework Explorer (System tab) and selecting "Properties".
9/1553-AOM 901 015/1 Uen A -- 9

Figure 6 Security Area for a Network Element
It is important to outline the fact that the user can set (even if he belongs
to the "IMA Configurator" Group) the Security Area of a NE only within the
ones configured for him in the user profile dialog. For the same reason a user
cannot create a NE and set for it a Security Area different from those listed
in his properties.
When a user logs into MINI-LINK Manager application, he will see the NEs
belonging to Security Areas not within his scope, with the state in which they
were left by their configurator.
The table below shows the default security configuration for the IMA users.
Table 5 Security Area

User
Name Category Security area
GUEST No category None
SYSTEM ADMINITSTRATOR IMA CONFIGURATORS A-P, IMA OPERATOR and
IMA CONFIGURATOR
IMA OPERATOR IMA OPERATORS IMA OPERATOR
IMA CONFIGURATOR IMA CONFIGURATORS IMA CONFIGURATOR
In the following table you can see an example of a customized network security
setting. The table illustrates which NE the different users have access to
depending on the user and the NE security area.
10 9/1553-AOM 901 015/1 Uen A --

Table 6 Example Of Database Security

User NE/Security area
Name Cate- Se- 001 002 003 004 005 006 007 008 009
gory curity A B K M All None A A M
area
OP 1 Opera- A X X X X
tor
OP 2 Opera- A+B X X X X X
tor
OP 3 Opera- K+M X X X X
tor
OP 4 Opera- None X
tor
Con- Config. A X X X X X
fig 1
Con- Config A+B X X X X X X
fig 2
Con- Config K+M X X X X X
fig 3
Con- Config None X X
fig 4
Ad- Config A..P X X X X X X X X X
min
1.3.2.1 Security in Pictures and Maps
Pictures and maps can also be assigned a security area. Users that are not
authorized to the security area defined for the picture will not be able to open it
in IMA WorkSpace. To change security area for a picture do as follows:
1 Start IMA WorkSpace and switch to configure mode.
2 Open the desired picture.
3 Right-mouse click on the picture and select the PropertyWindow menu item.
4 Select in the ComboBox CFixPicture object.
5 Enter value for the SecurityArea.
6 Close the property window and save the picture.
9/1553-AOM 901 015/1 Uen A -- 11

1.4 Security Configuration

This chapter explains how to perform basic users and security tasks. All
configurations are made via the System Configuration Utility (SCU). To open
the security configuration window, do as follows:
1 Start IMA if not already started
Select menu item Programs:IMA:IMA
2 Start the System Configuration Utility
Select menu item Programs:IMA:System configuration
3 Open the security configuration window
In the SCU window menu, select menu item Configure:Security
1.4.1 Create, Modify or Delete User Accounts
To create, modify or delete a user account in the IMA, select menu item
Edit:User Accounts from the security configuration window. The following
dialog will be displayed:
Figure 7 Create, modify or delete User accounts
Note the following when creating or modifying user account:
• Make sure that one of the user category IMA OPERATORS or IMA
CONFIGURATORS is added to the Group list.
12 9/1553-AOM 901 015/1 Uen A --

• Add one or more security areas for the user. For more information of
security areas refer to Section 1.2 on page 1.
• You can also add one or more applications that the user is authorized to
launch. Normally the default configuration when adding the user to one of
the predefined user categories will authorize the correct applications.
• If you would like the user to be able to shutdown IMA make sure that you
add "iFIX - System Shutdown", "Background Task Exit" and "Workspace
Runtime Exit" to the applications list.
Figure 8 User Profile
1.4.1.1 Using Windows 2000 Security
As an option, the Security Configuration program lets you specify an operator’s

Windows 2000 user name and password as their IMA login name and password.
This feature synchronizes the user accounts and lets you take advantage of
your existing Windows 2000 user accounts when logging into IMA.
1.4.2 Import and Export of Security Configuration
The Security Configuration utility allows you to import and export your
security configuration. Exporting the configuration creates by default a
security configuration file, SECURITY.RPT, in the security path (default
C:\ERICSSON\IMA\LOCAL). This file contains the following information:
• Whether security is enabled or disabled.
• Security area names.
• Defined group and user accounts.
After you create a security configuration file, you can copy it to another computer
and import the data. Importing a configuration file does one of the following:
9/1553-AOM 901 015/1 Uen A -- 13

• Replaces the existing security configuration with the one defined in the
configuration file;
or
• Merges the unique group and user accounts from the configuration file into
the existing security configuration. Any account with a user name or a login
name that matches an existing account is ignored.
By exporting and importing a security configuration, you can cut your

development time creating user and group accounts particularly when you want
to create many similar accounts on multiple IMA Servers and IMA Clients.
For example, suppose you want to create the same user account on fifty IMA
Servers and IMA Clients. Instead of creating same account fifty times, you
can do as follows:
1 Create one user account on an IMA Server or IMA Client.
2 Export the user account.
3 Import the user account into the remaining 49 IMA Servers and IMA Clients.
Note: The password must be re-entered on all Import MINI-LINK MANAGER

nodes for all user accounts and the password must also be the same
as on the MINI-LINK MANAGER export node.
1.4.3 Distributed Security Using a File Server
Using a file server, you can eliminate the need to copy security files to multiple
computers. The simplest way to share your security files is to enter your file
server path as the local node security path. Do this by selecting menu item
Edit:Configuration from the security configuration window. The following
dialog will be displayed.
14 9/1553-AOM 901 015/1 Uen A --

Figure 9 Distributed security using a file server
Change Security Path to the file server location (for example G:\IMA\GLOBAL).
Keep the Backup Path to your local node in case of file server failure. For
more information refer to the FIX Electronic books, chapter Implementing
Security->Intrduction->Protecting Remote Nodes.
1.5 Backup
It is recommended to make backup of your system whenever your configuration
has been changed.
There are currently three available MINI-LINK MANAGER products:
• MINI-LINK MANAGER Server Application
• MINI-LINK MANAGER Client Application
• MINI-LINK MANAGER Centralized DB
The following chapters describing backup instructions are given for each
product.
1.5.1 MINI-LINK MANAGER Server Application
To backup your MINI-LINK MANAGER Server Application do as follows:
9/1553-AOM 901 015/1 Uen A -- 15

Table 7 MINI-LINK MANAGER Server Application

No What When
1 Backup your IMA database Every time the IMA configuration is
Refer to Section 1.6 on page 16 how to changed. E.g. new network elements,
backup your IMA database. new sub networks, new description texts
etc.
2 Backup your security configuration Every time the security configuration is
If the security configuration has been changed.
customized, save your security configuration.
Refer to Section 1.4.2 on page 13.
3 Backup your customized pictures Every time new pictures are created.
Refer to Section 1.7 on page 19 how to
backup customized pictures.
1.5.2 MINI-LINK MANAGER Client Application
To backup your MINI-LINK MANAGER Client Application, do as follows:
Table 8 MINI-LINK MANAGER Client Application

No What When
1 Backup your security configuration. Every time the security configuration is
If the security configuration has been changed.
customized, save your security configuration.
2 Backup your customized pictures. Every time new pictures are created.
Refer to Section 1.7 on page 19 how to
backup customized pictures.
1.5.3 MINI-LINK MANAGER Centralized DB
To backup your MINI-LINK MANAGER DB Server, do as follows:
Table 9 MINI-LINK MANAGER Centralized DB

No What When
1 Backup your IMA DB Server. At least monthly.
1.6 Backup/Restore of MINI-LINK MANAGER Database

The MINI-LINK MANAGER always saves its configuration and monitoring
data automatically and continuously into the MINI-LINK MANAGER database.
Users can backup the current state of MINI-LINK MANAGER for later use. It is
16 9/1553-AOM 901 015/1 Uen A --

recommended that you back up the MINI-LINK MANAGER database after the
MINI-LINK MANAGER Server configuration has been changed and then copy
all the files located in the backup-directory to another disk or media. Users can
also clear and restore the MINI-LINK MANAGER Server database.
Perform following steps in MINI-LINK MANAGER to operate on the MINI-LINK

MANAGER database:
Figure 10 Backup/Restore of MINI-LINK MANAGER database
9/1553-AOM 901 015/1 Uen A -- 17

Table 10 Backup/Restore of MINI-LINK MANAGER database

1 Select System view properties for the MINI-LINK MANAGER ServerSelect the System tab.
Select a Server, right-mouse click and select menu item Database.
2 Operate on the database.
The user is able to operate Backup, Clear and Restore functionality manually by select
menu item:
Backup: The configuration data from the MINI-LINK MANAGER database is saved to
the \Ericsson\IMA\backup\ directory for default or to the possible directory selected in the
Server node property page as described in the Section 1.2.2 on page 1.
Clear: The MINI-LINK MANAGER database is cleared. (This operation cannot be
activated while any adaptation is running). It is important to understand that the clear
command will clear the network configuration as well as the FM, PM and inventory data.
If NM is installed, the NM database is also cleared. It is recommended to do a backup
before clearing the database, in order to make it possible to restore the database to
its previous state.
Restore: The configuration data from the backup directory is restored. This operation
cannot be activated while any adaptation, SNMP service and "Sql Server Agent" is running.
In order to stop SNMP service, go to Settings->Control Panel, click on Administrative Tools
and select Services. From the Services dialog choose "SNMP" and select Stop from the
right click menu. In order to stop "Sql Server Agent" Sql Server Service Manager must
be opened selecting its icon from the left side of the taskbar, the server name must be
selected from the servers list box and "Sql Server Agent" from the service listbox, then
the Stop button pressed. After the restore is competed check the MINI-LINK MANAGER
Alarm History for the node to see status messages about the restore operation.
Note: If the database to restore contains more NEs than MINI-LINK MANAGER is
configured for the NEs will be restored in ascending order until the max number is
reached. The exceeding NEs will not be restored. To restore the whole database first
follow the Configure MINI-LINK MANAGER database size instructions (Section 1.2.2 on
page 1) before performing the restore operation.
Note: The file format for the automatically saved configuration file also contains alarm
information, which is not the case for the file that the user stores on demand. The two
file types cannot be interchanged.
Only backup and restore on the same MINI-LINK MANAGER node is supported. It is
not possible to move a backup from one MINI-LINK MANAGER server and restore it
on another MINI-LINK MANAGER server.
It is not possible execute Backup on the same MINI-LINK MANAGER Server from two or
more MINI-LINK MANAGER Clients simultaneously.
If a backup is already started on an MINI-LINK MANAGER Server the following warning
message will be showed for each MINI-LINK MANAGER Client that calls a new Backup
for the MINI-LINK MANAGER Database (see Figure 11 on page 19 Backup Warning
Message).
It’s not possible execute Restore on the same MINI-LINK MANAGER Server from two or
more MINI-LINK MANAGER Clients simultaneously.
If a restore is already started on a MINI-LINK MANAGER Server the following warning
message will be showed for each MINI-LINK MANAGER Client that calls a new Backup for
the IMA Database (see Figure 12 on page 19 Restore Warning Message).
18 9/1553-AOM 901 015/1 Uen A --

Figure 11 Backup Warning Message
Figure 12 Restore Warning Message
1.6.1 Automatic Backup
MINI-LINK MANAGER is automatically performing a backup every night at

02:00. It is important to note that if a previously backed up configuration must
be preserved, the files in the backup directory must be moved elsewhere.
Otherwise they will be overwritten by the next automatic backup.
1.7 Backup/Restore of Customised Pictures

It is possible save your customized pictures. Copy the pictures from MINI-LINK
MANAGER installation directory \PIC (for example myown.grf) to a backup
directory.
Restore the customized pictures by copy the pictures from the backup directory
to the MINI-LINK MANAGER installation directory \PIC (for example myown.grf).
To get a complete backup of the customized pictures the Map association also
has to be saved.
Perform following steps in MINI-LINK MANAGER to backup Map associations:
9/1553-AOM 901 015/1 Uen A -- 19

Figure 13 Backup/Restore of customised pictures
Table 11 Backup/Restore of customised pictures

1 Select System view properties for the MINI-LINK MANAGER
serverSelect the System tab.
Select a Server, right-mouse click and select menu item Map
Associations.
2 Operate on Map Associations
The user is able to operate Backup, Clear and restore functionality
manually by select menu item:
Backup the association data from current MINI-LINK
MANAGER is saved to the \Ericsson\IMA\Backup\node name
backupimaPersistant.mdb file.
Clear the associations are cleared.
Restore the association data from the \Ericsson\IMA\Backup\node
namebackupimaPersistant.mdb file are restored.
20 9/1553-AOM 901 015/1 Uen A --

1.8 Backup And Restore Of The Mini-Link E Adapter

Database
The backup and restore utilities of SQL Server are an important safeguard for
protecting mission critical data stored in SQL Server databases. These utilities
allow the complete restoration of data after a wide range of problems such as
media failure, user errors, or permanent loss of a server.
The backup utilities of SQL Server allow you to back up the mini_link database,
as well as the master and msdb system databases.
1.8.1 Backup Devices
SQL Server backs up databases, transaction logs, and files to backup devices.
You can back up single or multiple databases to a single backup device, the
difference depends on whether tape or disk devices are used:
• Backup of multiple databases is the default configuration for tape devices.
• Backup of single databases is the default configuration for disk devices.
However, for simplicity, only one backup device is created to hold all three
databases: master, msdb, and mini_link. Even if only one device is used, it is
no problem to restore one, two, or all three databases from the device.
1.8.1.1 Disk Backup Devices
Disk backup devices are regular operating system files on hard disks, or other
disk storage media, and referring to these devices is the same as referring to
any other file. You can define disk backup devices on a server local disk or on a
remote disk on a shared network resource. The device can be as large or small
as you need; the maximum file size is the same as the free disk space available.
Note: It is not recommended to back up to a file that resides on the same

physical disk as the database. If the disk device fails, there is no way
to recover the database since the backup is located on the same
failed disk.
If you are going to back up over the network to a disk or to a remote

computer, use the Universal Naming Convention (UNC) in the form
\\Servername\\Sharename\\Path\\File to specify the location. As with any file,
you must set the permissions needed to read and write to the file for the user
account used by SQL Server. Because backing up over a network can be
subject to error, verify the backup operation after completion.
1.8.1.2 Tape Backup Devices
Tape devices are used in the same way as disk devices, with the exception that:
9/1553-AOM 901 015/1 Uen A -- 21

• The tape device must be physically connected to the computer running

SQL Server. Backing up to remote tape devices is not supported.
• If the tape backup device is filled during the backup operation, but more
data needs to be written, SQL Server prompts for a new tape and continues
the backup operation.
1.8.1.3 Creating Backup Devices
You should create a backup device for the mini_link, master, and msdb
databases.
To create a backup device:
1. Start SQL Server Enterprise Manager.
2. Expand your Windows NT-server.
3. Expand the Management folder.
4. Right-click Backup.
5. On the short-cut menu, click New Backup Device.
6. In the Name box, type a name for the device, for example:
MINI-LINK_E_Adapter_backup_device.
7. Do one of the following:
Select the Tape drive name option if you want to use a tape drive as backup
media, and then select the tape device to use from the list.
- or -
Select the File name option if you want to use a disk drive as backup media,
and then type the name of the file used by the disk backup device (or click
the browse (...) button to select the file).
8. Click OK.
1.8.2 Database Consistency Checker
If a database becomes corrupt, it may still be possible to back it up. There

may not even be a warning message about the fault. If the consistency of the
database is not checked before making a backup, you risk backing up a corrupt
database that will not be possible to restore after a failure. Therefore, it is very
important to check the consistency before backups.
Note: An SQL script that checks the consistency is included in the MINI-LINK
E Adapter delivery. See the procedures in section , for information on
how to include this script in scheduled backup jobs.
22 9/1553-AOM 901 015/1 Uen A --

Use these extensions of the DBCC utility to manually check the consistency of
a database:
• dbcc checkdb database_name with NO_INFOMSGS
This extension validates the integrity of everything in the database and

verifies the database consistency.
• dbcc checkalloc database_name with NO_INFOMSGS
This extension checks the allocation and use of all pages in the specified
database.
1.8.3 SQL Server Agent
The SQL Server Agent is used to set up and schedule backup jobs. Once the
SQL Server Agent is set up and activated, it takes care of all scheduled jobs,
such as backup handling.
1.8.3.1 Activating the SQL Server Agent Automatically
The SQL Server Agent must be activated (started) before it can take care of
the scheduled jobs. You can make the SQL Server Agent start automatically,
when the operating system starts, and also have it automatically restarted if
it stops unexpectedly.
To activate the SQL Server Agent automatically when the operating system
starts:
2. Right-click your Windows NT-server.
3. On the shortcut menu, click Properties.
4. Select the General tab.
5. Under Autostart policies when the operating system starts, select the
Autostart SQL Server Agent checkbox.
6. Click OK.
To restart the SQL Server Agent automatically if it stops unexpectedly:
3. Expand the Management folder.
4. Right-click SQL Server Agent.
5. On the shortcut menu, click Properties.
9/1553-AOM 901 015/1 Uen A -- 23

6. Click the Advanced tab.
7. Select the Auto restart SQL Server Agent if it stops unexpectedly.
8. Click OK.
1.8.4 Creating SQL Server Agent Jobs
You can set up SQL Server to back up the databases completely or

incrementally. Incremental (or differential) backups record only the changes that
have been made to the database since the last complete backup-not just the
changes made after the last incremental backup.
To make the task of creating SQL Server Agent jobs as easy as possible, some
SQL scripts are included in the MINI-LINK E Adapter delivery. This collection
of scripts includes scripts for checking the consistency of the databases as
well as scripts for doing the actual backup jobs. All scripts are stored in the
EAdapter-path\EAdapterServer\DatabaseScript folder, where EAdapter-path is
where MINI-LINK E Adapter is installed. The scripts are described in Table 12
on page 24.
Table 12 SQL Scripts Included in the MINI-LINK E Adapter Delivery

Script name Description
MoveToArchive.sql It prevents the number of log records
from growing in an uncontrolled way.
Check_db.sql It checks the consistency of the
database.
Complete_backup.sql It makes a complete backup of the
mini_link database, and the master
and msdb system databases.
Incremental_backup.sql It makes a differential backup of the
mini_link database.
What script you need and when, is described in the following sections.
1.8.4.1 Creating a Job to Move Logs to Archive
To keep the database log records from growing in an uncontrolled way, you
are recommended to set up a job to move log records to an archive. The
MoveToArchive.sql SQL script will move logs to the archive according to the
rules in Table 13 on page 25.
24 9/1553-AOM 901 015/1 Uen A --

Table 13 Rules for Moving Logs to the Archive

Maximum number Maximum number of
of days before a log log records before the
record is moved to oldest log records are
archive moved to archive
(1)
Alarm Log 30 200 000
AGC Log 30 200 000
Performance Log 30 200 000
(1) The most recent alarm records for each terminal are never moved to archive.
To keep the archive from growing to large, archived log records are deleted from
the archive according to the rules in Table 14 on page 25.
Table 14 Rules for Deleting Logs from the Archive

Maximum number Maximum number of
of days before a log log records before
record is deleted from the oldest log records
the archive are deleted from the
archive
Alarm Log 30 200 000
AGC Log 365 500 000
Performance Log 365 500 000
The following procedures show how to set up a job for moving database log
records to the archive.
Step 1: Setting General Properties for Archiving Log Records
To set general properties for archiving log records:
3. Expand Management.
4. For SQL Server 7.0:
Right-click SQL Server Agent, and then click New Job.
For SQL Server 2000:
Expand SQL Server Agent, right-click Jobs, and then click New Job.
5. In the Name box, type MoveToArchive.
6. Select the Enabled check box.
9/1553-AOM 901 015/1 Uen A -- 25

7. Select the Target local server option.
8. In the Category list, select Database Maintenance.
9. In the Owner list, select sa.
10. In the Description box, type a descriptive text, for example Move log records
to archive.
Step 2: Setting Up Log Record Archiving
To set up log record archiving:
1. Click the Steps tab.
2. Click New.
3. In the Step name box, type MoveToArchive.
4. In the Type list, select Transact-SQL Script (TSQL).
5. In the Database list, select mini_link.
6. Click Open.
7. In the Open dialog box, browse to the folder containing the backup scripts
and double-click the file MoveToArchive.sql.
This loads the SQL script into the Command box.
9. In the On success action list, select Quit the job reporting success.
10. Click OK.
Step 3: Scheduling Log Record Archiving
To schedule log record archiving:
1. Click the Schedules tab.
2. Click New Schedule.
3. In the Name box, type MoveToArchive.
5. Select the Recurring option
6. Click Change.
7. Select the Daily option to do the job on a daily basis.
26 9/1553-AOM 901 015/1 Uen A --

8. Select the Occurs once at option and type or select the time when it will be
done, for example 00:00, to do the job once at the specified time.
9. Click OK.
1.8.4.2 Creating a Job for Complete Backups
The following procedures will help you set up a job for complete backups,
including consistency checks of the databases, and scheduling.
Step 1: Setting General Properties for Complete Backups
To set general properties for complete backups:
4. Expand SQL Server Agent, right-click Jobs, and then click New Job.
5. In the Name box, type Complete backup.
8. In the Owner list, select sa.
9. In the Description box, type a descriptive text, for example Complete

backup of master, msdb, and mini_link databases.
Step 2: Checking the Databases before Complete Backups
To check the databases before complete backups:
2. Click New.
3. In the Step name box, type Check database.
5. In the Database list, select master.
6. Click Open.
and double-click the file Check_db.sql.
9/1553-AOM 901 015/1 Uen A -- 27

9. In the Output file box, enter the complete path and file name of the log file:
[drive:]/[path]db_compl_backup.log
10. Select the Overwrite option.
11. Click OK.
Step 3: Setting Up Complete Backups
To set up complete backups:
1. Click New.
2. In the Step name box, type Complete backup.
5. Click Open.
and double-click the file Complete_backup.sql.
[drive:]/[path]db_compl_backup.log
10. Select the Append option.
11. Click OK.
Step 4: Scheduling Complete Backups
To schedule complete backups:
3. In the Name box, type Complete backup.
5. Select the Recurring option.
28 9/1553-AOM 901 015/1 Uen A --

6. Click Change.
Note: It is recommended to do complete backups on a weekly basis,

for example on Sunday nights when normal operations are not
disturbed.
7. Select the Weekly option to make backups on a weekly basis.
8. Type or select 1 in the Every week(s) box to make backups every week.
9. Select the Sun check box to make backups on Sundays.
done, for example 02:00 AM, to make backups once at the specified time.
11. Click OK.
1.8.4.3 Creating a Job for Incremental Backups
The following procedures will help you set up a job for incremental backups.
Step 1: Setting General Properties for Incremental Backups
To set general properties for incremental backups:
4. Expand SQL Server Agent, right-click Jobs, and then click New Job.
5. In the Name box, type Incremental backup.
8. In the Owner list, select sa
9. In the Description box, type a descriptive text.
Step 2: Checking the Databases before Incremental Backups
To check the databases before incremental backups:
2. Click New.
3. In the Step name box, type Check database.
9/1553-AOM 901 015/1 Uen A -- 29

6. Click Open.
and double-click the file Check_db.sql.
[drive:]/[path]db_inc_backup.log
10. Select the Overwrite option.
11. Click OK.
Step 3: Setting Up Incremental Backups
To set up incremental backups:
1. Click New.
2. In the Step name box, type Incremental backup.
5. Click Open.
and double-click the file Incremental_backup.sql.
[drive:][path]db_inc_backup.log
10. Select the Append option.
11. Click OK.
Step 4: Scheduling Incremental Backups
To schedule incremental backups:
30 9/1553-AOM 901 015/1 Uen A --

3. In the Name box, type Incremental backup.
5. Select the Recurring option.
6. Click Change.
Note: It is recommended to do incremental backups every night, except

for Sundays when a complete backup should be done.
7. Select the Weekly option to make backups on a weekly basis.
8. Type or select 1 in the Every week(s) box to make backups every week.
9. Select the check boxes for all weekdays except Sundays (Sun) to make
backups every day, except Sundays.
done, for example 02:00 AM, to make backups once at the specified time.
11. Click OK.
1.8.5 Recovering Databases from Backups
1.8.5.1 Restoring the mini_link Database
Restoring the mini_link database from backup can be done using either a
complete backup or a combination of a complete backup and an incremental
backup.
As described in Section, you are recommended to take complete backups every

Sunday night, while incremental backups should be taken every night, except
Sundays. Restoring a database on a Wednesday should then be done from the
complete backup made last Sunday plus the incremental backup from Tuesday
night. All data from the time the last incremental backup was done (Tuesday
night) to the time the database failed will be lost.
To restore the mini_link database:
3. Expand Databases, right-click the database, point to All Tasks, and then
click Restore Database.
4. In the Restore as database list, select mini_link.
5. Select the Database option.
6. In the Show backups of database list, select mini_link.
9/1553-AOM 901 015/1 Uen A -- 31

7. In the First backup to restore list, select the backup set to restore.
8. In the Restore list, select the backup to restore.
9. Click OK.
1.8.5.2 Restoring the msdb Database
The system administrator must have exclusive use of the msdb database to be
able to restore the database. This means that no connections, other than the
system administrator ones, are allowed.
Note: When using SQL Server 2000, the msdb database can only be restored
from backups created on SQL Server 2000. Restore of backups of
this database made on SQL Server 7.0 or earlier is not supported in
SQL Server 2000.
The msdb database might contain MINI-LINK MANAGER server

scheduled jobs. Restoring this database might cause consistency
problems in MINI-LINK MANAGER server batch operations.
To restore the msdb database:
4. In the Restore as database list, select msdb.
6. In the Show backups of database list, select msdb.
7. Click OK.
1.8.5.3 Restoring and Rebuilding the master Database
You must start SQL Server in single user mode to be able to restore a damaged
master database. This means that only one user can connect to the server.
Also, make sure that the MSSQLServer service is stopped. SQL Server may
not be able to start if the master database is severely damaged. However, there
are two methods to restore the master database to a usable state:
• Restoring from a current backup
• Rebuilding completely, using the Rebuild Master utility
32 9/1553-AOM 901 015/1 Uen A --

Caution!
You should always keep a current backup of the master database-rebuilding the
database causes all previously stored data to be permanently lost.
If the master database is accessible, and at least partly usable, then it is

possible to restore the master database like any other database. On the other
hand, if you cannot start SQL Server due to severe damage to the master
database, then it is not possible to restore the database immediately. The
reason for this is that the SQL Server needs to be running to be able to restore
any database. In this case, you will need to rebuild the master database, using
the Rebuild Database utility, and then restore the database from backups as
normal.
1.8.5.3.1 Restoring the Master Database
To restore the master database:
1. From a command prompt, enter sqlservr.exe -m to start SQL Server in

single-user mode.
5. In the Restore as database list, select master.
7. In the Show backups of database list, select master.
8. Click OK.
1.8.5.3.2 Rebuilding the Master Database
Caution!
You should always keep a current backup of the master database-rebuilding the
database causes all previously stored data to be permanently lost.
To rebuild the master database:
9/1553-AOM 901 015/1 Uen A -- 33

1. Shut down SQL Server.
2. Click the Start button and click Run.
3. Browse to the SQLServer-path\Microsoft SQL Server\80\Tools\Binn folder

and double-click the Rebuildm.exe file.
Note: SQLServer-path is where SQL Server is installed, for example,

C:\Program Files.
4. Click Browse.
5. Browse to the \Data folder on the SQL Server compact disc or in the shared
network directory from which SQL Server was installed, then click OK.
6. Click Settings.
7. Verify or change the character set, sort order, and Unicode collation used
for the master database and all other databases, then click OK.
8. Click Rebuild.
The Rebuild Master utility reinstalls the master database.
9. Restore the master database from a previous backup according to Section

1.8.5.3.1 on page 33.
1.9 Centralized DB Administration

This functionality is used to configure the parameters MINI-LINK MANAGER
needs for backup/restore and alarm administration regarding the Centralized
DB.
1.9.1 Centralized DB Administration - Backup/Restore
At installation the backup of all MINI-LINK MANAGER DBs is configured to be

executed every month to a default device C:\………... To modify both scheduled
parameters and device, use the MINI-LINK MANAGER Administration tool.
34 9/1553-AOM 901 015/1 Uen A --

Figure 14 Centralized DB administration - backup/restore tab
Table 15 Centralized DB Administration - Backup/Restore Tab

Field Description
Backup It starts the backup of data stored into Centralized DB in the device specified
in the Device Panel.
Restore It starts the restore from the device specified in the Device Panel.
Scheduling It allows to modify the scheduling of database backup launching the form
shown in Configure Scheduling dialog box.
Info It allows displaying a simple form - Info Job Scheduling - in which information
about the last and the next run of the backup job are displayed.
Browse It allows modifying the device where backup/restore are executed.
DeviceType It allows choosing between a "Disk" device and a "Tape" device where to
do the Backup.
Set Device It sets the device in the Centralized Database.
Exit It closes the Centralized DB Administrator.
Figure 15 Centralized DB administration Info Job Scheduling
9/1553-AOM 901 015/1 Uen A -- 35

This form executes when Database Administrator wants to set-up a scheduling

period for the Backup of the Centralized DB. It is launched when it is clicked the
Scheduling… button in the Centralized DB Server Administrator application. It
allows to select the start date and time and to choose the backup execution
interval.
Figure 16 Centralized DB administration scheduling
Table 16 Centralized DB Administration Scheduling

Field Description
Period It allows to choose the period in which it is possible to do the schedule.
Every n days, every week or monthly.
Starting Time It allows to set the start time.
Starting Date It allows to set the starting date.
Apply It allows to confirm the setting of all parameters.
Cancel It allows to erase the selection and setting of all parameters. Subsequently
it exits.
OK It allows to confirm the setting of all parameters. Subsequently it exits.
The following form executes when Database Administrator wants to set-up a

device or folder where storing the backups of the Centralized DB.
36 9/1553-AOM 901 015/1 Uen A --

Figure 17 Centralized DB administration device selection
Table 17 Centralized DB Administration Device Selection

Field Description
OK The Selected folder is chosen as backup/restore folder where storing
database backups.
Cancel It closes the window without modify the folder of backup/restore.
New Folder It allows to set a new folder.
1.9.2 Centralized DB Administration - DB Capacity Alarm
This panel allows the administrator to set a capacity threshold for each DB.
Whenever the DB capacity goes over the threshold, an alarm is raised. The
alarm is sent over the network to the configured MINI-LINK MANAGER Server.
9/1553-AOM 901 015/1 Uen A -- 37

Figure 18 Centralized DB administration - DB capacity alarm
Table 18 Centralized DB Administration - DB Capacity Alarm

Field Description
MINI-LINK MANAGER Holds the server name where the alarms are sent when the
Server Name centralized database capacity is larger than the threshold configured
in "Capacity Threshold" field.
Test Connection Tests connection to the centralized database.
Capacity Threshold Holds the capacity the database can reach before MINI-LINK
MANAGER operator is noticed via an alarm.
Save Save the current setting regarding the MINI-LINK MANAGER
Server Name and Capacity Threshold fields.
Exit Close the Centralized DB Administrator.
1.10 PM and FM Database Settings

When PM- and FM-data is received, MINI-LINK MANAGER stores the data in
the MINI-LINK MANAGER database. Over time, the database keeps growing.
To avoid that the database grow too much and causes performance problems,
MINI-LINK MANAGER is monitoring the size and deletes a configurable amount
of old PM- and FM-data when another configurable limit is reached. By default,
the maximum size allowed is 300 MB but this setting is also configurable.
The following table describes the settings that can be altered

to fit your needs. The settings are stored in the registry under
HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\IMA\Application\.
38 9/1553-AOM 901 015/1 Uen A --

Table 19 PM and FM Database Settings

Registry Path Default Description
PM\PM_DB_MAX_MB 300 The maximum size allowed in MB. Do not
set the size over 1800.
PM\PM_DB_SAVE_DAYS 40 MINI-LINK MANAGER will delete all PM
data older than 40 days.
FM\FM_DB_MAX_MB 300 The maximum size allowed in MB.
FM\FM_DB_SAVE_DAYS 40 Do not set the size over 1800. MINI-LINK
MANAGER will delete all FM data older
than 40 days.
300 MB will save approximately 700 000 records depending of which

adaptations that is running. For performance reasons, it is recommended that
you keep the database as small as possible.
The automatic deletion of data is performed at noon and midnight. At these

times a check is made to see if the thresholds are crossed. First of all, all data
older than DB_SAVE_DAYS will be deleted from the database. After that, the
amount of data larger than DB_MAX_MB plus an extra 10% will be deleted
from the database.
1.10.1 Centralized Database Configuration and Statistics
When System Administrator starts MINI-LINK MANAGER Network Explorer, the

interface for centralization from the System Tab can be started by right clicking
on the MINI-LINK MANAGER Server icon and choosing the Centralization
sub menu. Form here it is possible to choose the "Configure" and "Statistics"
commands.
9/1553-AOM 901 015/1 Uen A -- 39

Figure 19 Centralized DB configuration and statistics
1.10.1.1 Centralized DB Configuration
This property page is shown when System Administrator wants to set-up the
centralization for a specific database by clicking on the "Configure" command of
the Centralization menu. The database is selected choosing the corresponding
tab. For all databases the configuration panel is the same, and offers the
functionalities to set the centralized database, activate the task and define the
scheduling.
40 9/1553-AOM 901 015/1 Uen A --

Figure 20 Centralized DB Configuration
In the Inventory and Config databases it is necessary that both the DB server
and Centralized Database are active and connected to each other. This
is necessary to activate the first phase of the alignment of data. If in the
configuration phase this condition is not true it is necessary to reconfigure the
scheduling of the export when both servers are active and connected to each
other in order to have a correct databases realignment.
Table 20 Centralized DB Configuration

Field Description
FM/PM/Inventory/Con- The Tab panel permits to configure the data exports for the specific
fig database.
Centralized DB Server The Input box permits to hold the centralized DB Server name.
Remote DB Button to test connection towards the centralized database.
Enable Flag that enables the data-exporting task.
Disable Flag that disables the data-exporting task.
Period Shows the current frequency settings.
Start Date Shows the start date for scheduling.
Scheduling Allows to modify the scheduling of the data-exporting task.
1.10.1.2 Centralized DB Configuration Scheduling
This form executes when System Administrator wants to set-up a scheduling

period for the data-exporting tasks. It is launched when it is clicked the
Scheduling… button in the Configure property page. It allows to select the
start date and time and to choose the task execution interval.
9/1553-AOM 901 015/1 Uen A -- 41

Figure 21 Scheduling of Centralized DB Configuration
Table 21 Scheduling of Centralized DB Configuration

Field Description
Period Allows to choose the period in which it is possible to do the schedule. Every
n minutes, every hour or daily.
Starting Time Set the start time.
Starting Date Allows to set the starting date.
Cancel Allows to erase the settings all parameters in the panel. Subsequently exits.
OK Allows to confirm the setting all parameters in the tables. Subsequently
exits.
1.10.1.3 Centralized DB Statistics
This dialog is shown when System Administrator or the Operator wants to see
some statistics for specific database by clicking on the "Statistics" command of
Centralization menu. The database is selected choosing the corresponding tab.
For all databases the statistics panel is the same.
42 9/1553-AOM 901 015/1 Uen A --

Figure 22 Centralized DB statistics
Table 22 Centralized DB Statistics

Field Description
FM/PM Tab panel that allows to select the specific database for which the
statistics are shown.
Centralized DB Server Shows the centralized DB Server name.
Last Alignment Date Shows the value of last alignment date.
Task Status Shows the task status value:
Idle if no exporting-data for the database is running on the server,
Active otherwise.
Non Aligned Records Shows the number of non-aligned records.
1.10.1.4 Align FM
This form is shown when System Administrator wants to align the FM local
MINI-LINK MANAGER database with the centralized one. This happens by
clicking on the "Align FM" command of Centralization menu.
Figure 23 Centralized DB - align FM
9/1553-AOM 901 015/1 Uen A -- 43

1.10.1.5 Align PM
This form is shown when System Administrator wants to align the PM local
MINI-LINK MANAGER database with the centralized one. This happens by
clicking on the "Align PM" command of Centralization menu.
Figure 24 Centralized DB - align PM
1.11 Cold Standby
1.11.1 Overview
MINI-LINK MANAGER Cold Standby can be used to protect the main site from
devastating failure such as fire or more simply a total power loss. Another site
can be used to host a stand-by MINI-LINK MANAGER server. This stand-by
MINI-LINK MANAGER server is activated only in the case if something fatal has
happened to the site where the main server is installed, or to the main server
itself. The main server is also called the working server.
44 9/1553-AOM 901 015/1 Uen A --

Figure 25 Overview
1.11.2 Principles
It is based on a redundant NMS configuration, providing two servers dedicated

to manage the same area of the network. These servers could be hosted in
different sites and connected via a DCN. During normal operation, data stored
on the working server is automatically transferred to the standby server. The
data transfer is realized as follows:
• Automatic backups of data on the working server (02:00 every night).
• Automatic transfer of backups to the standby server.
• Automatic loading of backups onto the standby server (03:00 every night).
Caution!
Since no continuous replication is made it is important to realize that some data
can be lost when switching over to the standby MINI-LINK MANAGER server.
Any configuration activity taken place between the last backup and the switch
over to the standby server will be lost. Possible re-entering or discovery of
data may be needed.
9/1553-AOM 901 015/1 Uen A -- 45

This type of node redundancy is categorized as "cold" standby, as the standby

server has to be taken into operation manually. A typical switch over time from
the working server to the standby server is approximately 15 minutes.
Note: On the stand-by server the SNMP service must be stopped because of
the automatic restore done during the night. In order to stop SNMP
service, go to Settings->Control Panel click on Administrative Tools and
select Services. From the Services dialog choose "SNMP" and select
Stop from the right click menu.
1.11.3 Summary of Examples
The following illustration demonstrates the relationship between nodes when

configuring cold standby. The illustration is a summary of the examples in
this chapter:
Local & logical Node Name(computer name) : IMACL1

Remote Node Name: IMAS, Primary Node: IMASRV1
Hostfile:
127.0.0.1 localhost
150.132.165.17 IMAS IMASRV1
#(primary server)
#150.132.165.16 IMAS IMASRV2
#(cold standby server)
46 9/1553-AOM 901 015/1 Uen A --

Local Node Name(computer Local Node Name(computer name):

name): IMASRV2
IMASRV1 Local Logical Name: IMAS
Local Logical Name: IMAS
Hostfile: Hostfile:
127.0.0.1 localhost 127.0.0.1 localhost 1
127.0.0.1 IMAS 127.0.0.1 IMAS
150.132.165.16 IMASRV2 150.132.165.17 IMASRV1
C:\Ericsson\ima\backup is C:\Ericsson\ima\backup is shared as
shared as backup backup
1.11.4 Installation Instructions on the Servers (Primary and Cold Standby)
Follow the succeeding steps to implement a Cold Standby solution:
• Start the System Configuration Utility From the Windows 2000 taskbar,
select Start:Programs:MINI-LINK MANAGER:System configuration.
• Open the Local Startup Definition window. Select menu item

Configure:Local Startup in the System Configuration Utility window.
• Set the Logical name (that is “IMAS”).
• Add the logical name to the host file of each Server as local host, that is
127.0.0.1 IMAS local host.
• A backup catalogue (folder) that contains database data must be shared

on both Servers, with read rights to the other Server, in order to make the
data available. This share must be permanent because if a switch over
is performed, the roles of the Servers will be switched after the original
Server is fixed. The former backup MINI-LINK MANAGER Server becomes
primary.
• In MINI-LINK MANAGER Explorer on the cold standby Server, right click

on the logical node name in the tree, i.e. the logical name for the cold
standby Server.
• Click Properties, then the Cold Standby tab.
• Check the “Enable this Server as cold standby Server” check box, and
set the main Server name (primary Server name, i.e. “IMASRV1” ) in the
text input box. This will enable the standby Server to restore the backup
data made by the primary.
1.11.5 Configuration of the MINI-LINK MANAGER Client
On the WP computer, add both Servers IP-addresses to the hosts file. But it
is important to put a (#) just before the backup node (cold standby Server)
9/1553-AOM 901 015/1 Uen A -- 47

IP-address. This is to have the IP address for the cold standby Server present
but not use it.
The lines should read like this:
150.132.165.17 IMAS IMASRV1 #(main Server name)

#150.132.165.16 IMAS IMASRV2 #(cold standby Server
name)
Do like this:
• Start the System Configuration Utility From the Windows 2000 taskbar, by
clicking Start -> Programs -> IMA -> System configuration.
• Open the Network Configuration select menu item Configure -> Network in
the System Configuration Utility window.
• Add the logical name in the Remote Node Name text input box.
• Select the added name and choose “Configure…”
• The Remote Node Configuration dialog box appears.
• Under Redundancy, Check the Enable Logical Node Names checkbox.
• Add the Primary Node name, but do not enter the node name of the Backup
Node. Leave this field blank.
1.11.6 How to Switch Over When Primary Server Fails
To switch over from the failed Server to the cold standby Server, just perform
the following steps:
• On the MINI-LINK Manager Client computers Hostfile, change the lines

with the IP addresses by deleting the (#) from the cold standby Server IP
address and add it to the primary Server IP address.
• The lines in the Hostfile should now read like this:
150.132.165.17 IMAS IMASRV1 #(main Server name)

#150.132.165.16 IMAS IMASRV2 #(cold standby Server
name)
• Start the System Configuration Utility From the Windows 2000 taskbar,
select Start -> Programs -> IMA-> System configuration.
• Open the Network Configuration and Select menu item Configure ->
Network in the System Configuration Utility window.
• Select the logical name and choose “Configure…”.
48 9/1553-AOM 901 015/1 Uen A --

• The Remote Node Configuration dialog box appears.
• Change the Primary Node name to the new primary Server, that is the
previous cold standby Server.
• Remember to leave the “backup node” field blank.
• Save the changes and shut down MINI-LINK MANAGER.
• Restart the MINI-LINK MANAGER Client computer.
• Restart the MINI-LINK MANAGER.
• Restart the MINI-LINK MANAGER.
Start IMA Explorer on the MINI-LINK Manager Client.
• Right click on the logical node name in the tree, i.e. the logical name for the
cold standby Server, to which the adaptations are added.
• Click Properties.
• Click the Cold Standby tab.
• Uncheck the “Enable this Server as cold standby Server” check box.
• Start the adaptations and PM and FM on the adaptations.
• The alarm information is now sent from the cold standby Server.
After the problems with the primary Server has been fixed, do the following:
• Start IMA Explorer on the primary Server.
• Right click on the logical node name in the tree, that is the logical name for
the primary Server, to which the adaptations are added.
• Click Properties, then the Cold Standby tab.
• Check the “Enable this Server as cold standby Server” check box.
• Set the main Server name (as the cold standby Server name, that is
“IMASRV2”) in the text input box.
There is no need to switch back. The earlier cold standby Server is now the
primary Server, and the earlier primary Server is now considered the cold
standby Server. Remember, the Servers are IMASRV1 and IMASRV2, but the
MINI-LINK MANAGER Client is only interested in the logical name given for the
teamed Servers, as their configuration is exactly the same.
9/1553-AOM 901 015/1 Uen A -- 49

1.12 System Shutdown
1.12.1 Shutdown of a MINI-LINK MANAGER Server Application
To Stop MINI-LINK MANAGER, right-click on the MINI-LINK MANAGER Startup

Manager and select the “Stop IMA” menu option from the pop-up menu.
Figure 26 Stop MINI-LINK MANAGER
Note: If there are tasks configured in the Task Configuration in System

Configuration Utility, you should use the Windows 2000 Task Manager
to check if they still are running after shutting down MINI-LINK
MANAGER, and terminate them if so. Problems during start of
MINI-LINK MANAGER may be the result if such tasks are allowed
to continue running. Start the Windows 2000 Task Manager (by
right-mouse clicking on the task bar) and look for any of the following
tasks: tl1.exe, emm.exe, iigcn.exe and iigcc.exe. You have to terminate
them manually after shutting down MINI-LINK MANAGER.
1.12.2 Shutdown of a MINI-LINK MANAGER Client Application
If MINI-LINK MANAGER is configured to start as a service, you stop MINI-LINK

MANAGER by stopping a service named Fix:
1 Start the Control Panel in My Computer.
2 Select Services.
3 Select Fix in the list 4.
4 Push Stop.
If MINI-LINK MANAGER not is configured as a service, you stop MINI-LINK

MANAGER in the MINI-LINK MANAGER Startup window by selecting Options:
Shutdown IMA.
Figure 27 Shutdown MINI-LINK MANAGER
50 9/1553-AOM 901 015/1 Uen A --

06 Administrator Guide

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

06 Administrator Guide

Transféré par

Droits d'auteur :

Formats disponibles

MINI-LINK Manager 6.

© Ericsson AB 1996-2003 - All Rights Reserved

9/1553-AOM 901 015/1 Uen A --

9/1553-AOM 901 015/1 Uen A --

9/1553-AOM 901 015/1 Uen A --

1.2 System Configuration

1.2.1 Configure IMA Network

Refer to the MINI-LINK MANAGER Client Application Installation Guide or

1.2.2 IMA Database Settings

1 Backup current IMA DB on the MINI-LINK MANAGER Server (optional).

2 In the IMA Network Explorer, select the MINI-LINK MANAGER Server,

5 In the information window that pops up push OK.

6 Shut down the MINI-LINK MANAGER Server as described in Operator

9/1553-AOM 901 015/1 Uen A -- 1

7 Delete the \Ericsson\Ima\pdb\IMA.db database file on the MINI-LINK

8 Start the MINI-LINK MANAGER Server.

10 Restore the IMA DB from backup (optional).

Figure 1 System Settings

1.2.3 Configure Alarm Auto Sync Mode

By default, a MINI-LINK MANAGER Server automatically performs alarm

1 In the IMA Network Explorer, select the MINI-LINK MANAGER Server,

2 Select the System Settings tab.

2 9/1553-AOM 901 015/1 Uen A --

before alarm synchronization is started. The value should be in the range

4 When you are done with the changes push OK.

5 In the information window that pops up push OK.

6 Stop and then start the MINI-LINK Manager Server.

Figure 2 System Settings

1.2.4 Configure Alarm Acknowledgement Mode 1.

MINI-LINK MANAGER supports three modes for alarm acknowledgement:

• Alarm disappears from alarm list when clearedmeans that an alarm

• Alarm disappears from alarm list when acknowledged and cleared

• Alarm disappears from alarm list when acknowledged twice and

9/1553-AOM 901 015/1 Uen A -- 3

The automatically acknowledge circuit alarms when all related

1 In the IMA Network Explorer, select the MINI-LINK MANAGER Server,

2 Select the System Settings tab.

3 Select the desired alarm acknowledgement mode.

5 In the information window that pops up push OK.

6 Stop and then start the MINI-LINK MANAGER Server.

Figure 3 System Settings

1.2.5 Automatic Alarm Printing

For automatic printouts of alarms do as follows:

4 9/1553-AOM 901 015/1 Uen A --

Figure 4 Automatic alarm printing

Table 1 Automatic Alarm Printing

9/1553-AOM 901 015/1 Uen A -- 5

1.2.6 Change of Host Name

• Uninstall MINI-LINK Manager EM, according to the Server Installation

• Uninstall MSDE (Control Panel->Add/Remove Programs "MS SQL Server

• Change the host name (Control Panel->Network).

• Install MSDE, see client/server installation guides.

• Install MINI-LINK MANAGER EM (no need to reinstall Windows2000 or IMA

1.3 Users And Security

At installation, MINI-LINK MANAGER generates two default user categories

Table 2 Default User Categories (User Groups)

6 9/1553-AOM 901 015/1 Uen A --

Table 3 Default User Identities

1.3.1 MINI-LINK E Adapter User Categories

MINI-LINK E Adapter has three user categories:

• System Administrator - The System Administrator is responsible for

It is only the System Administrator who can change the contents

9/1553-AOM 901 015/1 Uen A -- 7

1.3.1.1 Setting The Passwords