1 - 1553-AOM 901 0153 SoM R8 SP1 PDF

Installation Guide
ServiceOn Microwave Element Manager

User Guide
Copyright
© Ericsson AB 2007 – All Rights Reserved
Disclaimer
No part may be reproduced, disclosed or used except as authorised by

contract or other written permission. The copyright and the foregoing
restriction on reproduction and use extend to all media in which the
information may be embodied.
The information in this work is the property of Ericsson Limited. Except as

specifically authorised in writing by Ericsson Limited, the receiver of this
work shall keep the information contained herein confidential and shall
protect the same in whole or in part from disclosure and dissemination to
third parties. Disclosure and disseminations to the receiver's employees
shall only be made on a strict need to know basis. The information in this
work is subject to change without notice and Ericsson Limited assumes no
responsibility for factual inaccuracies or typographical errors.
Ericsson Limited has used all reasonable endeavours to make sure that the
information contained in this work is accurate at the release date but
reserves the right to make changes, in good faith, to such information from
time to time.
Trademark List
Microsoft MicrosoftMS and MS-DOS are registered

MS and MS-DOS trademarks of the Microsoft Corporation in the
United States of America and other countries.
Windows Windows is a trademark of the Microsoft

Corporation in the United States of America an
other countries.
Adobe Reader Adobe and Reader are either registered

trademarks or trademarks of Adobe Systems
Incorporated in the United States and/or other
countries.
HP-UX HP-UX is a registered trademark of Hewlett-

Packard Company. (HP-UX®) in the United
States and/or other countries.
Sun Microsystems, Inc. Sun, Sun Microsystems, the Sun logo, iForce,
Java, Netra, N1, Solaris, Sun Fire, Sun Ray,
SunSpectrum, Sun StorEdge, SunTone, The
Network is the Computer, all trademarks and
logos that contain Sun, Solaris, or Java are
trademarks or registered trademarks of Sun
Microsystems, Inc. in the United States and
other countries.
Novell Novell, the Novell logo and Groupwise are

registered trademarks and eDirectory and
Nterprise are trademarks of Novell, Inc. in the
United States and other countries. SUSE is a
registered trademark of SUSE LINUX AG, a
Novell business.
AdventNet AdventNet, The oval AdventNet logo, are

trademarks of the AdventNet, Inc.
Ilog ILOG, the ILOG design, CPLEX and all other

logos and product and service names of ILOG
are registered trademarks or trademarks of
ILOG in France, the U.S. and/or other
countries.
NETAPHOR NETAPHOR®, Cyberons®, are trademarks of

SOFTWARE, INC NETAPHOR SOFTWARE, INC.
InfoZoom InfoZoom is a trademark of the humanIT

Software GmbH.
All trademarks are properties of their respective owners

1/1553-AOM 901 015/3 Uen G
3
ServiceOn Microwave Element Manager - Installation Guide
0BIntroduction
Document History
Issue Record
Code Date System Release

1/1553-AOM 901 015/3 Uen D 03-07 R8
1/1553-AOM 901 015/3 Uen PE1 05-07 R8 Patch
1/1553-AOM 901 015/3 Uen E 07-07 R8 SP1
1/1553-AOM 901 015/3 Uen F 09-07 R8 SP1
1/1553-AOM 901 015/3 Uen G 09-07 R8 SP1
4 1/1553-AOM 901 015/3 Uen G

Contents
Contents
1 Introduction 10
1.1 Applicability 10
1.2 Scope 10
1.3 System Requirement 10
1.4 Required Media 10
2 Installing SUSE Linux Enterprise Server 9 Service
Pack 3 12
2.1 System start-up for installation 12
2.2 The boot screen 12
2.3 Language Selection 13
2.4 Installation Settings 13
2.4.1 Mode 14
2.4.2 Keyboard Layout 15
2.4.3 Mouse 15
2.4.4 Partitioning 15
2.4.4.1 Create Boot Partition 15
2.4.4.2 Using LVM 17
2.4.5 Software 22
2.4.6 Boot Configuration 22
2.4.7 Time Zone 22
2.4.8 Language 22
2.4.9 Launching the Installation 22
2.5 Finishing the Installation 22
2.5.1 Root Password 23
2.5.2 Network Configuration 23
2.5.3 Network Services 24
2.5.4 User Authentication 24
2.5.5 Creating Local User Accounts 25
2.5.6 Hardware Configuration 25
2.5.6.1 Monitor Type 25
2.5.6.2 Graphical Card Resolution 25
2.5.7 Printer Setup 26
2.5.8 Start the System 26
2.6 Installation Procedure for tftp package on Linux 26
3 Install ServiceOn Microwave 28
3.1 Double LAN Configuration 28
3.2 Fill System Files 28
3.2.1 DNS Not Present 28
3.2.2 DNS Present 29
3.3 Using the Network Time Protocol 31
3.4 Upgrade Procedure from ServiceOn Microwave R8
(MV36v15.8.3) to ServiceOn Microwave R8 SP1
(MV36v15.9.3) 32
3.4.1 Unistall all SOM Mediation 33
1/1553-AOM 901 015/3 Uen G 5

Contents
3.4.2 Upgrade Database on SOM Font-End server 33

3.4.3 Upgrade SOM Application on Font-End server 34
3.4.4 Install all SOM Mediation instances 35
3.4.5 SOM Client Upgrade Procedure 35
3.4.6 SOM Adapter Server Upgrade Procedure 36
3.5 Load the software 36
3.6 Install ServiceOn Microwave Frameworks 37
3.6.1 Graphical Installation 37
3.6.2 Terminal Installation 37
3.7 Install ServiceOn Microwave 3pp 38
3.8 Install ServiceOn Microwave Core 39
3.8.3 ServiceOn Microwave Configuration 40
3.8.3.1 Stand-Alone configuration 40
3.8.3.2 Distributed configuration 43
3.9 Install ServiceOn Microwave Tools 48
3.10 Install ServiceOn Microwave Plug-ins 49
3.11 Install ServiceOn Microwave PFM-SNMP 51
3.12 Install License Manager 52
3.13 License Management 53
3.14 FTP Configuration 55
3.15 Web Clients Installation 59
3.15.1 Server Side 59
3.15.1.1 Graphical Installation 59
3.15.1.2 Terminal Installation 59
3.15.2 Client Side 59
3.15.2.1 Java Installation 60
3.15.2.2 Web Clients Installation 61
3.15.2.3 Client off line Installation 72
4 Installation via NFS 74
4.1 Set up an installation repository for ServiceOn Microwave: 74
5 ServiceOn Microwave Client applications installation
on Microsoft Terminal Server Machine 76
5.1 Prerequisites 76
5.2 Java application installation 76
5.3 SOM Client application installation 76
5.4 MV36 Ghost application installation 77
6 1/1553-AOM 901 015/3 Uen G

Contents
5.5 TN LCT application installation 77

6 MINI-LINK E Adapter Server Installation 79
6.1 MINI-LINK E Adapter Server Installation: Introduction 79
6.2 MINI-LINK E Adapter server co-located 79
6.2.1 Guest OS installation: Windows XP SP2 installation and
configuration 79
6.2.2 System File Patches 80
6.2.3 Windows XP Security Configuration 80
6.2.4 Configuring DCOM For Windows XP SP2 80
6.2.5 Network Configuration of Windows XP SP2 guest OS 85
6.2.6 3rd party software installation 85
6.2.7 MINI-LINK E Adapter server installation 85
6.2.8 MLEAdapterServer DCOM Configuration 87
6.3 MINI-LINK E Adapter server Stand Alone 88
6.3.1 Operative System installation and configuration: Windows
XP SP2 88
6.3.1.1 System File Patches 89
6.3.1.2 Windows XP Security Configuration 89
6.3.1.3 Configuring DCOM For Windows XP SP2 90
6.3.1.4 Windows Server 2003 SE 95
6.3.2 3rd party software installation 104
6.3.3 MINI-LINK E Adapter server installation 104
6.3.4 MLEAdapterServer DCOM Configuration 106
7 Change Configuration 108
7.1 Change Configuration: Introduction 108
7.1.1 Change Network Configuration 109
7.1.2 Change NFS Client Configuration 112
7.1.3 Change ServiceOn Microwave configuration 113
7.1.4 MINI-LINK E Adapter Server Change Configuration 117
8 Active Directory Management 118
8.1 Overview 118
8.2 Windows Domain Controller Configuration 119
8.2.1 User Configuration 119
8.2.1.1 Create a functional User 119
8.2.1.2 Create a organization Unit 120
8.2.1.3 User profile Creation 120
8.2.1.4 User Creation 120
8.2.1.5 User Configuration 120
8.2.1.6 How to change the User Password 120
8.3 ServiceOn Microwave Server Configuration 121
8.3.1 Prerequisites 121
8.3.2 Configuration of Kerberos engine 122
8.3.2.1 Example of krb5.conf file 122
8.3.2.2 Configuration of additional backup Active Directory Server 122
8.3.3 Configuration of the LDAP client 123
8.3.3.1 Example of ldap.conf file 123
8.3.3.2 Configuration of additional backup Active Directory Server 123
8.4 Configuration of Active Directory in Service 124
8.5 Utility Scripts 125
1/1553-AOM 901 015/3 Uen G 7

Contents
8.5.1 Prerequisites 125

8.5.2 Script ad_deluser.sh 125
8.5.3 Script ad_getusergroup.sh 126
8.5.4 Script ad_ls.sh 126
8.5.5 Script ad_rls.sh 127
8.5.6 Script ad_setusergroup.sh 127
8.5.7 Script ad_sync.sh 128
9 ServiceOn Microwave Standby Installation and
Configuration 129
9.1 Prerequisites 129
9.2 Standby Installation 132
9.2.1 Load the software 132
9.3 ServiceOn Microwave Standby Configuration 133
9.3.1 Primary configuration 134
9.3.2 Standby configuration 135
9.3.3 MINI-LINK E Adapter Stand by Configuration 136
9.4 Manual Synchronization 136
9.5 Switch Primary server to Stand-by server 136
9.5.1 Primary switch 137
9.5.2 Stand-by switch 137
9.5.2.1 Reconfigure ima_inventory data base 138
9.5.2.2 MINI-LINK E Adapter Switch (when MINI-LINK E Adapter
is running on a virtual machine hosted on Linux server of
DSP) 138
9.5.2.3 Reconfigure the Client as Server 139
9.5.3 CSPs Switch 139
9.6 CSP Stand by Configuration and Switch Instruction 141
9.6.1 CSP1 failure 141
9.6.4 MINI-LINK E Adapter server stand-by configuration and
switch in case of virtual machine running on CSP 143
9.6.5 MINI-LINK E Adapter server stand alone switch 144
9.7 Remove Standby Software 144
10 Appendix 146
10.1 MINI-LINK E Physical Subnetwork: Configuration
guideline 146
10.1.1 Pre-requisites 146
10.1.2 Terminal Server 146
10.1.3 Direct Cable 147
10.1.4 Modem 147
10.1.5 Modem Connection Setup 147
10.1.5.1 Example of AT Commands to Call from Modem to MINI-
LINK 148
10.1.5.2 Example of AT Commands to Call from Modem to MINI-
LINK E 148
10.1.6 Modem Connection To MINI-LINK Equipment 148
10.1.6.1 Connection of Modem to MINI-LINK E Equipment; O&M
port 148
8 1/1553-AOM 901 015/3 Uen G

Contents
10.1.6.2 Connection of Modem to MINI-LINK C and MkII Radio 149

10.1.6.3 Connection of Modem to MINI-LINK C and MkII SMM;
BAY/USER 149
10.1.7 Patton Model 2120 Single Port Terminal Server 149
10.1.8 Terminal Emulation Settings 150
10.1.8.1 Example: Hyper Terminal Setting 150
10.1.9 Configuring The TS For A MINI-LINK E Sub-network 152
10.1.10 Connecting The TS To An O&M Port 153
10.1.11 Connecting The TS To The TCP/IP Network 153
10.1.12 Configuring MINI-LINK E Adapter 153
10.1.13 Reconfiguring The TS 153
10.1.14 Cisco Access Server Model 2509 154
10.1.14.1 Connection 154
10.1.14.2 Configuration 154
10.1.14.3 Other Useful Commands 156
10.2 The Server Network.ids File 157
10.3 Change nmcman user password 158
10.4 Free Open Source Products 160
10.4.1 Projects copyrighted by The Apache Software Foundation 162
10.4.2 Projects copyrighted by Free Software Foundation 163
1/1553-AOM 901 015/3 Uen G 9

0BIntroduction
1 Introduction
1.1 Applicability
This Handbook applies to R8 SP1 of ServiceOn Microwave.
1.2 Scope
Purpose of this document is to provide the procedure to install ServiceOn
Microwave on SUSE Linux 9.3 Enterprise SP3.
The ServiceOn Microwave installation is performed via these main steps:
• SUSE Linux 9.3 Service Pack 3 installation (optional).
• ServiceOn Microwave Frameworks installation.
• ServiceOn Microwave 3pp installation.
• ServiceOn Microwave Core installation.
• ServiceOn Microwave Tools installation.
• ServiceOn Microwave Plug-ins installation.
• ServiceOn Microwave Interfaces installation.
• License Manager Installation.
• ServiceOn Microwave Disaster installation (optional)
To keep the scope of these guidelines manageable, certain technical
assumptions have been made. It is assumed that:
• You have some computer experience and are familiar with the common
technical terms.
• You have a basic understanding of Linux system
• You have administrator knowledge of Element Manager Systems
1.3 System Requirement

NOTICE Ensure hardware RAID 1 is enabled and configured prior to installation in
order to supply mirrored disks in case of failure.
For detailed configuration description of the recommended hardware platform

refer to the ServiceOn Microwave Product Catalog Supplement document
(1/2135-EN/LZT 712 0229 Uen)
1.4 Required Media

The ServiceOn Microwave is released with this media support:
• DVD: SUSE Linux 9 Enterprise Service Pack 3 (optional)
• DVD: ServiceOn Microwave Applications (LZY 214 3636/1 R2A)
• ServiceOn Microwave 3pp
10 1/1553-AOM 901 015/3 Uen G

0BIntroduction
• ServiceOn Microwave Frameworks

• ServiceOn Microwave Tools
• ServiceOn Microwave Core
• ServiceOn Microwave Plug-ins
• ServiceOn Microwave Interfaces
• License Manager
• ServiceOn Microwave Disaster
1/1553-AOM 901 015/3 Uen G 11

1BInstalling SUSE Linux Enterprise Server 9 Service Pack 3
2 Installing SUSE Linux Enterprise Server 9

Service Pack 3
NOTICE If you have a system already installed with a SUSE Linux Enterprise Server
9 Service Pack 3 you can skip this section and go directly to section 3.
Anyway you have to check if the system layout is compliant with the below
requirements.
2.1 System start-up for installation

Insert the first SUSE Linux Service Pack 3 CD or DVD into the drive. Then
reboot the computer to start the installation program from the medium in the
drive.
If you experience problems booting from the CD or DVD check if the drive is
correctly reported in the boot sequence and if it is supported by the current
release.
NOTICE If you install SUSE Linux on a 64 bit server (i.e.: target server HP DL 380
G5), you will receive this message “You are about to install 32-bit software
on a 64-bit computer”. In this case you have to press `Continue` to start the
installation phase.
2.2 The boot screen

NOTICE It’s possible that your graphics card it’s not correctly detected by the
installation process or maybe your card doesn’t have enough video RAM; in
this case the system starts a textual installation with a selection proposal
similar to graphics mode.
Figure 2-1 Boot screen
12 1/1553-AOM 901 015/3 Uen G

The boot screen has a number of menu items from which to select. To install the
system, select Ìnstallation` with the arrow keys. This loads YaST and start the
installation.
A few seconds after starting the installation, SUSE Linux loads a minimal Linux
system to run the installation procedure and the system displays some
messages and copyright notices. At this point to start the installation process
you must accept the software license agreement by pressing the Ì Agree`
button. After a few more seconds, the screen should display the graphical
interface that will guide you through the installation.
All YaST screens have a common layout, all the buttons and the entry fields can
be accessed with the mouse or the keyboard.
2.3 Language Selection

YaST and SUSE Linux in general can be configured to use different languages
according to your needs. The language selected at this point is the default used
also for the keyboard layout. If your keyboard layout is different you can change
it in the relative section. In addition YaST uses the language setting to guess a
time zone for your system clock. If your time zone is different you can change it
in the relative section during the installation procedure.
Figure 2-2 Language Seclection
2.4 Installation Settings

After hardware detection, the Ìnstallation Settings` window displays some
information about the hardware recognized and proposes a number of
installation and partitioning options. After selecting any of these items and
configuring them in the corresponding dialog, you are always returned to the
“Installation Settings” window, which is updated accordingly.
1/1553-AOM 901 015/3 Uen G 13

The individual settings used for the ServiceOn Microwave installation are
discussed in the following sections.
In the Ìnstallation Settings` window that appears (Figure 2-3) you can change
the following settings:
• Mode
• Keyboard layout
• Mouse
• Partitioning
• Software
• Booting
• Time zone
• Language
Figure 2-3 Installation Settings
2.4.1 Mode
In this dialog, select a `New Installation`; if your installed system fails to boot,
perhaps because some important system configuration has been corrupted, you
can try to make the system bootable again with `Repair installed system`.
14 1/1553-AOM 901 015/3 Uen G

Figure 2-4 Installation Mode
2.4.2 Keyboard Layout

Select the keyboard layout, if are not sure about your keyboard you can use the
`Keyboard test` field to test if your choice is correct.
2.4.3 Mouse
If YaST failed to detect your mouse automatically you can use this dialog to
manual specify you mouse selection.
2.4.4 Partitioning
With this dialog you can decide how to partition your system disks. In this
section are proposed some guidelines that can be used to correctly partition
your system.
• Never use the partitioning scheme proposed by YaST.
• Start the `Create custom partition setup`.
• Use the Èxpert Partitioner` selection, in this case it allow tweaking the
partition setup in every detail.
• For safety reason it is mandatory to use the Logical Volume manager.
The LVM provides a higher level view of the disk storage; in fact storage
volumes created under the control of the Logical Volume Manager can
be resized and moved around almost at will.
• Make sure that the boot partition, holding the kernel and the initial RAM
disk, must be created outside the LVM control, so you have at least one
physical partition to boot somewhere.
2.4.4.1 Create Boot Partition
Steps to execute:
• Click on the `Partitioning` item.
• The `Suggested portioning` window will appear.
• Select `Create custom partition setup` and then on `Next` button.
• In the `Preparing Hard Disk – Step 1` window select `Custom partitioning
– for experts` and click on the `Next` button.
• From the Èxpert` dialog press `Create` and create a primary partition.
1/1553-AOM 901 015/3 Uen G 15

• From the Èxpert` dialog, delete any partitions if present.
Figure 2-5 Expert Partitioner
If your system has more then one disk the Partitioner procedure asks you on
which disk you like create the partition. The proposal selection is strictly related
to the server hardware but in general, in case of multiple hard disks, the options
should be something like this:
• 1: /dev/hda
• 2: /dev/hdb
Select 1) to create the boot partition on the first disk and click on the ÒK`
button.
The system display which type of partition you can create:
• Primary partition or Extended partition.
Select `Primary partition` and click on the ÒK` button.
Figure 2-6 Boot Partition
16 1/1553-AOM 901 015/3 Uen G

The primary partition must be created with these features:

• Format: Yes.
• File system: Reiser.
• Options: Default.
• Encrypt file system: No.
• File system size: 100 MB. To do that you have to put on the Ènd`
section `+100M` (Figure 2-6). The `Start cylinder` should be correct
already so you don’t have to modify this value.
• Fstab Options: Default
• Mount point: /boot.
To create the partition you have to press the ÒK` button.
2.4.4.2 Using LVM
From the Èxpert` dialog press `Create` and create a primary partition.
If your system has more then one disk the Partitioner procedure asks you on
which disk you like create the partition. The proposal selection is strictly related
to the server hardware but in general, in case of multiple hard disks, the options
should be something like this:
• 1: /dev/hda
• 2: /dev/hdb
• Select 1) to create the LVM partition on the first disk and click on the
ÒK` button. The system display which type of partition you can create:
• Primary partition.
• Extended partition.
Select `Primary partition` and click on the ÒK` button.
Figure 2-7 Logical Volume Manager
1/1553-AOM 901 015/3 Uen G 17

• Format: Do not format.

• File system ID: 0x8E Linux LVM.
• File system size: the entire disk storage (default). Then in this case you
don’t have to modify the `Start` and Ènd` cylinder on the `Size`
selection.
To create the partition you have to press the ÒK` button.
If your system has more then one disk you have to create on the other disk (for
example /dev/hdb) another LVM partition. To do that from the Èxpert` dialog
press `Create`, select the second disk and after select the `Primary partition`.
• Format: Do not format.
• File system ID: 0x8E Linux LVM.
• File system size: the entire disk storage (default). Then in this case you
don’t have to modify the `Start` and Ènd` cylinder on the `Size`
selection.
Figure 2-8 Logical Volume Manager
From the Èxpert` dialog press `LVM` and create the `Volume Group`:
• Volume Group Name = vg00.
• Physical Extent Size = 4M.
• Use Old LVM1 Compatible Metadata Format: No.
To create the volume group you have to click the ÒK` button.
18 1/1553-AOM 901 015/3 Uen G

Figure 2-9 Volume Group
If your system has more then one disk, for example /dev/hda and /dev/hdb, you
have to create another `Volume Group`, then from the `Logical Volume
Manager` dialog use the Àdd group` selection:
• Volume Group Name = vg01.
• Physical Extent Size = 4M.
• Use Old LVM1 Compatible Metadata Format: No.
To create the volume group you have to click the ÒK` button.
From the `Logical Volume Manager` add the first created LVM partition
(dev/hda) to the first volume group (vg00). To do that select the `/dev/hda`
device, the `vg00` volume group and then press Àdd Volume`.
1/1553-AOM 901 015/3 Uen G 19

If your system has more then one disk, for example /dev/hda and /dev/hdb, you
have to put the remaining device together with the lasting volume group. To do
that select the `vg01` volume group, `/dev/hdb` device and the press Àdd
Volume`.
When you have associate the last device to the volume group you can press the
`Next` button
Finally create all the `Logical Volumes` with these features:
• File system type: see Table 2-1
• File system name: swap, tmp, usr, var, opt, home, root
• File system size: see Table 2-1
• File system volume group: see Table 2-1
20 1/1553-AOM 901 015/3 Uen G

• File system stripes: 1

• File system mount point: related to file system name
One Logical Disk System
Volume Group File System Logical Volume Size Mount Pount
Name
vg00 Swap swap 2⋅RAM Swap
vg00 Reiser var 20 GB /var
vg00 Reiser tmp 1 GB /tmp
vg00 Reiser home 1 GB /home
vg00 Reiser usr 3 GB /usr
vg00 Reiser root 1 GB /
vg00 Reiser opt 25 GB /opt
Two Logical Disk System
Volume Group File System Logical Volume Size Mount Pount
Name
vg00 Swap swap 2⋅RAM Swap
vg00 Reiser var 20 GB /var
vg00 Reiser tmp 1 GB /tmp
vg00 Reiser home 1 GB /home
vg00 Reiser usr 3 GB /usr
vg00 Reiser root 1 GB /
vg01 Reiser opt 25 GB /opt
Table 2-1 File System (RAM=Physical Memory)
For example if your system have only one disk, to create the `/opt` file system
you have to select the `vg00` volume group, press the Àdd` button and put on
the `Create Logical Volume` dialog the above values.
1/1553-AOM 901 015/3 Uen G 21

Figure 2-13 Logical Volume
Remember that, using the LVM, the partition size can be changed using YaST
when the system it’s already installed and configured without affecting the file
system integrity. Click `Next` and then `Next` to exit back to YaST.
2.4.5 Software
SUSE Linux contains a number of software packages for various application
purposes. As it would be burdensome to select the needed packages one by
one, SUSE Linux offers three system types with various installation scopes. For
Service On Microwave you can select the `Default System`; this system type
include the KDE desktop together with must of the KDE programs and the
CUPS printer server.
2.4.6 Boot Configuration

During the installation YaST propose a boot configuration for your system.
Normally leave these settings unchanged. If you want to change the YaST
configuration edit the boot loader with attention after you have read the
documentation. In the worst case the system can result unbootable.
2.4.7 Time Zone

In this dialog you can select the `Time Zone` for your server. You can choose
between `local time` and ÙTC`, the selection depends on how the hardware
clock (BIOS) is set in your machine. If it is set to GMT you can use the UTC
format as Time Zone.
2.4.8 Language
The language was already selected at the beginning of the installation, however
at this step you can change this setting here.
2.4.9 Launching the Installation

When satisfied with the installation settings, click Àccept` in the suggestion
window to begin the installation. Confirm with `Yes, install` in the green dialog
that opens. Follow the on screen installation instructions, replacing CDs when
required.
The installation takes between fifteen and thirty minutes, depending on the
system performances and the software selected.
As soon as all packages are installed, YaST boots into the new Linux system.
2.5 Finishing the Installation

After completing the basic system setup and the installation of all selected
packages you have to finish the installation provides:
• Root password mandatory
• Network configuration mandatory
• User authentication mandatory
• Users accounts skip
• Graphical configuration mandatory
22 1/1553-AOM 901 015/3 Uen G

• Printer configuration skip
2.5.1 Root Password

The root account should be used only for system administration maintenance
and repair. Logging in as root for daily works is rather risky, single mistake could
lead to irretrievable loss of many system files. For verification purpose the
password for root must be entered twice and system also advice you if the
entered password is to simple.
Figure 2-14 Root Password
2.5.2 Network Configuration

Normally in this dialog you have to configure only the network interface. For
ServiceOn Application the system should be reachable with a static addressing
(DHCP disabled). To do that change the `Network interfaces` configuration to
enable the relative dialog.
1/1553-AOM 901 015/3 Uen G 23

Figure 2-15 Network Configuration
At this stage you have to contact the IT department responsible to know how to
complete the network interface configuration; the minimal configuration is
composed by:
• Server IP address
• Server netmask
• Server host name
• Server domain name
• Name server addresses (leave it empty if not available)
• Domain servers search (leave it empty if not available)
• Default gateway
Do not test the internet connection at this stage, if you want an internet access
you can setup the system after when the system is up and running.
NOTICE In case of multiple LAN cards configure just one of them to complete the
Linux installation. Before the ServiceOn Microwave installation the LAN card
configuration will be completed.
2.5.3 Network Services

The `Service Configuration` dialog can be skipped because with the Service On
Applications we don’t use any kind of these services (CA Management and
LDAP authentication).
2.5.4 User Authentication

The use accounts are managed using the local /etc/passwd file, NIS and LDAP
clients are disabled. If for some reason the user accounts are managed centrally
by a NIS or LDAP server you can modify the default value and setup the right
values for the relative servers.
Figure 2-16 User Authentication
24 1/1553-AOM 901 015/3 Uen G

2.5.5 Creating Local User Accounts

You can skip this dialog because the Ùser Account` creation is a part of
ServiceOn Microwave customization. Click `Next` and `Yes` in warning
message box.
Click `Next` to the Release Notes window to proceed with the installation.
2.5.6 Hardware Configuration
2.5.6.1 Monitor Type
With this dialog you can specify the monitor directly connected to the ServiceOn
Microwave server. In this case you have to choose from a list of available
monitor model.
Figure 2-17 Monitor Type
2.5.6.2 Graphical Card Resolution
In this section you have to specify the graphical resolution for your environment.
For Service On Microwave application it is recommended to have a minimal
resolution of 1280x1024 pixels with a minimal color depth of 65536.
These settings are used only by the hardware directly connected to the server. If
the user is connected to the ServiceOn Applications via a X Emulator like
Exceed or Go-Global or via an Explorer connection, the local settings on the PC
is used.
1/1553-AOM 901 015/3 Uen G 25

Figure 2-18 Graphical Resolution
NOTICE If during the installation process the monitor and the graphical card
configuration fails, you can configure everything after the first textual login. to
do that:
Switch to run level 3 (# init 3)

Configure the X-Server (# SaX2)
Switch to run level 5 (# init 5)
2.5.7 Printer Setup

You can skip this dialog, if you want to install a printer directly usable from
ServiceOn Microwave server you can set up this feature when the system it’s
already installed and configured by the use of YaST.
2.5.8 Start the System

Into the installation completed window click `Finish to exiting setup and finally
starting the system.
2.6 Installation Procedure for tftp package on Linux

This part provides instruction about how to install the package tftp on a Linux
machine before ServiceOn Microwave installation (both on Front End and
Mediation servers).
Before SOM Installation, insert in the drive the media you used to install Linux
and perform the actions hereafter depicted.
Tftp Installation Procedure

1. Open the YAST Application then select Install and Remove Software
26 1/1553-AOM 901 015/3 Uen G

2. In the Install and Remove Software window select as Filter 'Search' and edit in
the Search box the string tftp, then press the Search button. The system will find
the required package.
3. In the right panel the result of the research will be visualised (Figure 2-19).
4. Select the tftp - Trivial File Transfer Protocol row then press Accept button to
perform installation (Figure 2-19).
5. Once the package installation has been performed the window is automatically
closed.
6. The tftp package is now installed and it is possible to start SOM Installation
according to 3 Install ServiceOn Microwave.
Figure 2-19 TFTP Package Installation
1/1553-AOM 901 015/3 Uen G 27

2BInstall ServiceOn Microwave
3 Install ServiceOn Microwave
After the first login you have to install the ServiceOn Microwave, the product
installation is composed by eight sub products:
- ServiceOn Microwave 3pp - ServiceOn Microwave Plug-ins
- ServiceOn Microwave Frameworks - ServiceOn Microwave Interface
- ServiceOn Microwave Tools - License Manager
- ServiceOn Microwave Core - ServiceOn Microwave Disaster
3.1 Double LAN Configuration

If you have multiple LAN cards it’s strictly recommended to setup just one LAN
on the server and you must ensure that it is the “eth0” card. All the others LAN
cards must be disabled to avoid ServiceOn Microwave installation failure.
3.2 Fill System Files

Before load the software you have to check and modify some system files. The
steps that must be performed are quite different if your ServiceOn Microwave
structure uses a DNS or not to correctly translate the host names and the
addresses (see section 2.5.2).
3.2.1 DNS Not Present

• Hosts file: this file (/etc/hosts) is a simple text file that associates IP
address and hostnames, one line per IP address. For each host a single
line should be present with the following information:
IP_address fully_qualified_hostname aliases
Figure 3-1 ServiceOn Microwave Structure
28 1/1553-AOM 901 015/3 Uen G

In this case the /etc/hosts file must contains these rows:

172.16.245.167 gexs13.it.marconicomms.com gexs13
• Nsswitch.conf file: this file (/etc/nsswitch.conf) is used to

configure which services are to be use to determine information such as
hostnames, password files and group files. Its basic syntax is:
Database name-service-to-search
Then edit the file and change the hosts line to read:
hosts: files dns
Which means, for programs that want to resolve an address, they should
use first the /etc/hosts file.
• Host.conf: this file (/etc/host.conf) is analogous to the previous

(/etc/nsswitch.conf) but it performs similar tasks for different
functions. Then edit the file and change the order line to read:
order hosts, bind
• Resolv.conf file: this file (/etc/resolv.conf) is used by the

resolver, a set of routines C library that provides access to the Internet
Domain Name System. In this case the file must be empty because the
system doesn’t use any DNS and the names are resolved on the local
machine.
3.2.2 DNS Present
• Hosts file: this file (/etc/hosts) is a simple text file that associates IP
address and hostnames, one line per IP address. For each host a single
line should be present with the following information:
IP_address canonical_hostname aliases
In this case the file should be modified in order to store only the name and
the IP address of the local machine. Then using the data reported on Figure
3-1 the files should be modified in this way:
o gexs13
o gexs12
o gexs14
• Nsswitch.conf file: this file (/etc/nsswitch.conf) is used to

configure which services are to be use to determine information such as
hostnames, password files and group files. Its basic syntax is:
Database name-service-to-search
1/1553-AOM 901 015/3 Uen G 29

Then edit the file and change the hosts line to read:
hosts: dns files
Which means, for programs that want to resolve an address, they should
use first the DNS.
• Host.conf: this file (/etc/host.conf) is analogous to the previous

(/etc/nsswitch.conf) but it performs similar tasks for different
functions. Then edit the file and change the order line to read:
oder bind, hosts
• Resolv.conf file: this file (/etc/resolv.conf) is used by the

resolver, a set of routines C library that provides access to the Internet
Domain Name System. In this case the file should be filled with the
values necessary to retrieve the DNS information (see section 2.5.2).
Figure 3-2 DSN structure
In this case the /etc/resolv.conf file must contain these rows:

nameserver 172.16.247.1
search it.marconicomms.com
NOTICE In case of primary DNS failure it possible observe a reduction of system

performances. This why any DNS command waits the timeout to switch from
primary to secondary DNS system. In this case if the fault is repetitive you
can change the resolve priority in the /etc/resolv.conf file
30 1/1553-AOM 901 015/3 Uen G

3.3 Using the Network Time Protocol

To correctly synchronize all the ServiceOn Microwave servers it’s recommended
set-up the Network Time Protocol (NTP).
• This can be configured by YaST->Network Services->NTP Client. In the
NTP server field fill in the IP address.
Figure 3-3 NTP Client Configuration
• In order to support additional NTP servers as backup, additional NTP

sources can be set using the "Complex Configuration" setup.
Figure 3-4 NTP Client Complex Configuration
• In the “Complex NTP Client Configuration” window, click the “Add”

button and then select the “Server” item and click “Next”.
1/1553-AOM 901 015/3 Uen G 31

• In the “NTP Server” field fill in the IP address of another NTP server and
click “OK”.
• In the “Complex NTP Client Configuration” click the “Finish” button.
3.4 Upgrade Procedure from ServiceOn Microwave R8

(MV36v15.8.3) to ServiceOn Microwave R8 SP1
(MV36v15.9.3)
NOTICE If you have never installed ServiceOn Microwave R8, you can skip this
section and go directly to section 3.5, else you have to follow the below
software upgrade instructions.
NOTICE Before to start the Upgrade procedure, the SOM R8 system must be
updated with the MV36v15.8.3 Patch 005 (all Core patches: Patch 001,
Patch 002, Patch 003, Patch 004, Patch 005 must be installed).
NOTICE Before to start the Upgrade procedure, you have also install the TFTP
package from SUSE 9 SP3 - CD3, both on Front-End and Mediation servers,
as described in par. 2.6 Installation Procedure for tftp package on Linux.
NOTICE Before to start the Upgrade procedure, you have to stop SOM R8 processes
on each SOM Mediation server and then also on SOM Front-End server,
applying the procedure below:
Login as root and run the commands:

csh
source /etc/mv36.cshrc
Shut
as described in section 4.9 of the System Administration and Configuration
Guide - ServiceOn Microwave Element Manager.
The Upgrade Procedure from ServiceOn Microwave R8 (MV36v15.8.3) to

ServiceOn Microwave R8 SP1 (MV36v15.9.3) is below reported. It depends on
the SOM configuration and on the current running Ingres version, and in
particular:
• in case of distributed SOM configuration (Front-End and Mediation
servers) refer to sections 3.4.1, 3.4.2, 3.4.3, 3.4.4, 3.4.5.
• in case of stand-alone SOM configuration (only one Front-End) refer to
sections 3.4.2, 3.4.3, 3.4.5.
32 1/1553-AOM 901 015/3 Uen G

3.4.1 Unistall all SOM Mediation
NOTICE If you don’t have SOM Mediation, you can skip this section and go directly to
section 3.4.2, else you have to follow the below software upgrade
instructions for each SOM Mediation of the system.
• Remove all the old component (Ingres included), in particular:

LIMA;
ServiceOn Microwave Plug-ins;
ServiceOn Microwave Tools;
ServiceOn Microwave Core;
ServiceOn Microwave 3pp (Ingres included);
ServiceOn Microwave Frameworks.
3.4.2 Upgrade Database on SOM Font-End server
1. Clear temporary files for backup if already exist

rm –r /tmp/mv36tmp
rm /tmp/mv36_aux_give.log
2. Backup of SOM DataBase
Login as nmcman and run the command:
csh -f $NCS/script/mv36Backup /opt/mv36/core/data/data/ini/mv36Backup.ini
the backup file will be saved in $NCS/../../hist/dbBackup/[dbBackFile]
ALERT The backup DB must be done on the SOM Front End Server, else the data
will be lost.
3. Check running Ingres version

Login as nmcman and run the command:
rpm -aq | grep ServiceOn-Microwave-Ingres
NOTICE If the ingres version is ServiceOn-Microwave-Ingres-9.0.4-2, skip this section

and go directly to section 3.4.3, else you have to follow the below software
upgrade instructions.
4. Stop Ingres processes

Login as root and run the command:
/etc/init.d/ingresII stop
5. Remove ServiceOn-Microwave-Ingres-9.0.4-1
Login as root and run the command:
rpm -e ServiceOn-Microwave-Ingres-9.0.4-1
6. Install ServiceOn-Microwave-Ingres-9.0.4-2
Login as root and put the SOM DVD in the DVD ROM drive. Move to the
repository where the RPM packages are located (typically
/media/cdrecorder/suse/i586) and install the required software using the `rpm`
1/1553-AOM 901 015/3 Uen G 33

command:
rpm -ihv ServiceOn-Microwave-Ingres-9.0.4-2.i586.rpm
The previous operations can be executed also using Yast SW installation,

selecting ServiceOn Microwave 3PP package and check ServiceOn Microwave-
Ingres to install it.
7. Run script upd_ingres.csh
csh
cd $NCS/script
csh -f upd_ingres.csh $NCS/../../hist/dbBackup/[dbBackFile]
where [dbBackFile] is the backup file created in the step above.

If the last message showed is:
exit state = 0
it means the db restore procedure has been completed successfully.
3.4.3 Upgrade SOM Application on Font-End server

1. Remove all the old component, leaving only the new Ingres 9.04-2 previously
installed, in particular:
LIMA;
ServiceOn Microwave PFM-SNMP;
ServiceOn Microwave Plug-ins with MV36emCLIENTS;
ServiceOn Microwave Tools;
ServiceOn Microwave Core;
ServiceOn Microwave 3pp (except Ingres);
ServiceOn Microwave Frameworks.
2. Install SOM R8 SP1 using the SW application contained in LZY 214 3636/1
R2A according to installation procedure described in the following paragraphs; in
particular:
ServiceOn Microwave Frameworks as described in 3.6;
ServiceOn Microwave 3pp as described in 3.7, except Ingres;
ServiceOn Microwave Core (as Upgrade leaving the basic configured settings)
as described in 3.8;
NOTICE This step contains even the ServiceOn-Microwave Core Configuration, as

described in 3.8.3.
ServiceOn Microwave Tools as described in 3.9;

ServiceOn Microwave Plug-ins with MV36emCLIENTS as described in 3.10 and
in 3.15.1;
ServiceOn Microwave PFM-SNMP as described in 3.11;
34 1/1553-AOM 901 015/3 Uen G

LIMA as described in 3.12.

3. Reboot SOM Server machine.
4. Restart SOM R8 SP1.
To do this login as root and run the commands:
csh
Shut
3.4.4 Install all SOM Mediation instances
NOTICE If you don't have SOM Mediation, you can skip this section and go directly to
next section, else you have to follow the below software upgrade instructions
for each SOM Mediation of the system.
1. Install SOM R8 SP1 using the SW application contained in LZY 214 3636/1
R2A according to installation procedure described in the following paragraphs; in
particular:
ServiceOn Microwave Frameworks as described in 3.6;
ServiceOn Microwave 3pp as described in 3.7 (Ingres included);
ServiceOn Microwave Core (as Upgrade leaving the basic configured settings)
as described in 3.8;
NOTICE This step contains even the ServiceOn-Microwave Core Configuration, as

described in 3.8.3.
ServiceOn Microwave Tools as described in 3.9 (except Mosquito);

ServiceOn Microwave Plug-ins as described in 3.10 (MV36emCLIENTS not
included);
LIMA as described in 3.12.
2. Reboot SOM server machine
3. Restart SOM R8 SP1.
To do this login as root and run the commands:
csh
Shut
3.4.5 SOM Client Upgrade Procedure

The Upgrade procedure for SOM Client is reported below:
1. Using “ADD or remove Programs”, remove SOMR8-Client item

2. Using “ADD or remove Programs”, remove J2SE Runtime Environment 5.0
Update 10 item
1/1553-AOM 901 015/3 Uen G 35

3. Remove the C:/Ericsson/SOM folder

4. Install Java and SOM R8 SP1 Client referring to the “Clients Side” installation
procedure, as described in 3.15 paragraph.
3.4.6 SOM Adapter Server Upgrade Procedure

The Upgrade procedure for SOM Adapter Server is reported below:
1. Stop the MINI-LINK E Adapter Server Application if started (according to the

Operator Guide description).
2. Using "ADD or remove Programs", remove J2SE Runtime Environment 5.0
Update 10 item.
3. Using "ADD or remove Programs", remove the "MINI-LINK XML Agent" item.
4. Install Java and SOM MINI-LINK E Adapter Server referring to the “Clients Side”
installation procedure, as described in 3.15.
3.5 Load the software

At this stage you have to add the Software Source Media containing the
ServiceOn Microwave software. To do that login as root and before starting the
YaST control center, put the DVD (LZY 214 3636/1 R2A) with the right
applications on the relative box. From YaST select `Software`, `Change Source
of Installation` and finally add a DVD resource.
Figure 3-5 Software Source Media
36 1/1553-AOM 901 015/3 Uen G

3.6 Install ServiceOn Microwave Frameworks

The ServiceOn Microwave Frameworks is a software collection used by
ServiceOn Core and ServiceOn Plug-ins to correctly work. The software
collection is packed with:
• ServiceOn-Microwave-FICO
• ServiceOn-Microwave-SOOCOM
• ServiceOn-Microwave-COM-EM
To install the ServiceOn Microwave Frameworks you can use the graphical
installation via YaST or install everything using a terminal session as root. It’s
mandatory to install all the products reported on the software collection.
3.6.1 Graphical Installation

From the KDE desktop start YaST and after putting the root password, select
the Ìnstall and Remove Software` dialog. Inside this dialog select as filter
`Package Groups`, choose the `ServiceOn Microwave Frameworks` and mark
all the packages.
Figure 3-6 ServiceOn Microwave Frameworks
Finally you have to press the Àccept` button to install your software selection;
remember that at this stage the ServiceOn Microwave DVD must be insert in the
DVD ROM drive.
3.6.2 Terminal Installation

Login as root and put the ServiceOn Microwave DVD in the DVD ROM drive.
Move to the repository where the RPM packages are located (typically
command:
• rpm –i ServiceOn-Microwave-FICO-1.5-1.i586.rpm
• rpm –i ServiceOn-Microwave-SOOCOM-3.4.2-2.i586.rpm
• rpm –i ServiceOn-Microwave-COM-EM-1.2.0-1.i586.rpm
1/1553-AOM 901 015/3 Uen G 37

3.7 Install ServiceOn Microwave 3pp

The ServiceOn Microwave 3pp is a software collection used by ServiceOn Core
and ServiceOn Plug-ins to correctly work. The software collection is packed
with:
• ServiceOn-Microwave-MICO
• ServiceOn-Microwave-MICO_Multithread
• ServiceOn-Microwave-Ingres
• ServiceOn-Microwave-Java
• ServiceOn-Microwave-net-snmp
• ServiceOn-Microwave-xerces-c
• ServiceOn-Microwave-COM-3PP
To install the ServiceOn Microwave 3pp you can use the graphical installation
via YaST or install everything using a terminal session as root. Its mandatory to
install all the products reported on the software collection.

`Package Groups`, choose the `ServiceOn Microwave 3pp` and mark all the
packages.
Figure 3-7 ServiceOn Microwave 3pp
remember that at this stage the SOM DVD must be insert in the DVD ROM
drive.

command:
38 1/1553-AOM 901 015/3 Uen G

• rpm –i ServiceOn-Microwave-Ingres-9.0.4-2.i586.rpm
• rpm –i ServiceOn-Microwave-Java-1.5.0-11.i586.rpm
• rpm –i ServiceOn-Microwave-MICO-2.3-1.i586.rpm
• rpm –i ServiceOn-Microwave-MICO_Multithread-2.3-1.i586.rpm
• rpm –i ServiceOn-Microwave-net-snmp-5.3.0.1-1.i586.rpm
• rpm –i ServiceOn-Microwave-xerces-c-2.6.0-1.i586.rpm
• rpm –i ServiceOn-Microwave-COM-3PP-1.2.0-1.i586.rpm
3.8 Install ServiceOn Microwave Core

The ServiceOn Microwave Core is the main application that provides element
manager functionality as described on the international standards. The software
is packed with:
• MV36 Core
To install the ServiceOn Microwave Core you can use the graphical installation
via YaST or install everything using a terminal session as root.

`Package Groups`, chose the `ServiceOn Microwave Core` and mark the
MV36Core package.
Figure 3-8 ServiceOn Microwave Core
drive.
1/1553-AOM 901 015/3 Uen G 39


command:
• rpm –i MV36Core-15.09-03.i586.rpm
3.8.3 ServiceOn Microwave Configuration
3.8.3.1 Stand-Alone configuration
Figure 3-9 Stand-Alone Configuration
After the first step of the installation procedure you have to start the MV36
wizard facility to automatically perform the setup and configuration phase.
Login as root on the DSP-CSP box and execute these commands:
• cd /opt/mv36/core/utilsv2 [Return]
• sh coresm –wizard [Return]
The configuration phase requires some interaction. Here follows the capture of a
typical Stand-Alone installation.
• Select the installed Cores to configure.
Core 2 Software Manager (Operation: wizard)
Here follows the list of compatible Cores currently installed on

GESX0339
1) MV36Core-15.09-03
2) Exit
On which core do you want to operate on? 1
• Select the Server type.
40 1/1553-AOM 901 015/3 Uen G

You selected MV36Core-15.09-03
----- Installation Profile Selection ----
1. DSP
2. CSP
Select option [1..2] : 1
• Build the LANconfig file. This file contains the options selected by user
during the preliminary operations. It will drive the configuration
procedure using the information concerning managed equipments and
server description.
Check of Lanconfig File ...

Rebuilding default setup information ...
Rebuild of custom setup for MV36Core-15.09-03 from official one

Removing previous setup information ...
Creating basic.cfg ...
Creating advanced.cfg ...
Creating mv36_inst.cfg ...
Creating mv36_remove.cfg ...
Genearation of automatic configuration options
MV36_SG_MODE is NOT_A_SERVICE_GUARD
Creation of LANconfig file
@@@@@@ MV36 MultiServer configuration @@@@@@

== Please insert information on DSP node ==
Enter the name of node : <DSP Name>
Enter the IP address of node : <DSP IP>
Enter the … of users for DSP : <DSP Max. Users>
Enter the … Network Element to manage : <Max. Managed NEs>
Enter … of Communication Server [0-5] : 0
Where:
o DSP Name: it’s the server hostname, see section 2.5.2
o DSP IP: it’s the server IP address, see section 2.5.2
o DSP Max. Users: Parallel users logged on the system (≤ 30)
o Max. Managed NEs: Max. managed Network Elements (≤ 6000)
o Number of Communication Server: 0 (Stand-Alone)
• Accept Basic configuration settings
Accept Basic configuration settings.
Basic Installation Information for MV36Core-15.09-03:
(*) Installation Type new
1/1553-AOM 901 015/3 Uen G 41

(*) MV36 Language UK

(*) Advanced Settings Default(NOT_A_SERVICE_GUARD)
Version 15.9.3
Installation Path /
Installation Profile DSP
(*) LANconfig Information:
DSP: <DSP Name>

CSPs:
Note: Setup information marked with (*) can be customized by user
1) Accept these settings

2) Change Basic Settings (Nat and Inst Type)
3) Change Advanced Settings
4) Change Lanconfig
5) [ --- setup not changed during this session ]
Select Option [1-4]: 1
• Configuration Phase and Switch.
Computing MV36core-15.09-03 status - Please wait ...
Area Severity
INSTALL_UTILS NOT_CONFIGURED
MV36_BASE_ENV NOT_CONFIGURED
MV36_DATA NOT_CONFIGURED
MV36_SYSTEM NOT_CONFIGURED
MV36_LANCONFIG NOT_CONFIGURED
MV36_NAT_CUSTOM NOT_CONFIGURED
MV36_NFS NOT_CONFIGURED
MV36_INGRES_DB NOT_CONFIGURED
MV36_INTEGRATORS NOT_CONFIGURED
MV36_USERS NOT_CONFIGURED
SERVICE_GUARD NOT_CONFIGURED
MV36core-15.09-03 is not properly configured - Starting Automatic configuration

of MV36core-15.09-03
When the configuration phase is terminated you have to switch to activate the new
installed and configured ServiceOn Microwave release.
Core 2 Switch Utility

-------------------------
Currently working: None

Target core: MV36Core-15.09-03 on /
Do you want to continue [y/n]? y
At the end of switch phase MV36 is ready to run and you can start to install
the ServiceOn Microwave Tools (3.9).
42 1/1553-AOM 901 015/3 Uen G

3.8.3.2 Distributed configuration
Figure 3-10 Distributed Configuration
DSP configuration
Login as root on the DSP box and execute these commands:
typical Multi-Server DSP installation.
• Select the installed Cores to configure.
Here follows the list of compatible Cores currently installed on GESX0339
1) MV36Core-15.09-03
2) Exit
1. DSP
2. CSP
1/1553-AOM 901 015/3 Uen G 43

server description.
Computing MV36Core-15.09-03 status - Please wait ...



Enter the … users for DSP : <DSP Max. Users>
Enter the … Element to manage : <DSP Max. Managed NEs>
Enter … Communication Server (CSP)[0-5] : 1-5
Enter the name of node : <CSP Name 1>
Enter … of node gexs14 : <CSP IP 1>
Enter the … Element to manage : <CSP 1 Max. Managed NEs>
. . .
Enter … node gexs14 : <CSP IP 5>
LANconfig file saved in /opt/mv36/core/utilsv2
Check of MV36Core-15.09-03 setup

Setup information for MV36Core-15.09-03 is OK.
---- Type <RETURN> to continue ----

Where:
o DSP Name: it’s the DSP server hostname, see section 2.5.2
o DSP IP: it’s the DSP server IP address, see section 2.5.2
o DSP Max Users. : Parallel users logged on the system (≤ 30)
o DSP Max. Managed NEs: Max. managed Network Elements by
DSP server (≤ 6000)
o Number of Communication Server: [1-5] (Distributed)
o CSP Name 1: it’s the CSP 1 server hostname, see section 2.5.2
o CSP IP 1: it’s the CSP 1 server IP address, see section 2.5.2
o CSP 1 Max. Managed NEs: Max. managed Network Elements by
CSP 1 server (≤ 8000)
…
44 1/1553-AOM 901 015/3 Uen G


• Accept Basic configuration settings.

Version 15.9.3
Installation Path /
Installation Profile DSP
DSP: <DSP Name>

CSPs: <DSP Name>

4) Change Lanconfig
Area Severity


-------------------------
1/1553-AOM 901 015/3 Uen G 45


CSP Configuration
Login as root on the CSP box and execute these commands:
typical Multi-Server CSP installation.
• Select the installed Cores to configure
Here follows the list of compatible Cores currently installed on GESX0339
1) MV36Core-15.09-03
2) Exit
1. DSP
2. CSP
server description.
Computing MV36Core-15.09-03 status - Please wait ...


46 1/1553-AOM 901 015/3 Uen G



Enter the … users for DSP : <DSP Max. Users>
Enter the … Element to manage : <DSP Max. Managed NEs>
Enter … Communication Server (CSP)[0-5] : 1-5
Enter … of node gexs14 : <CSP IP 1>
. . .
Enter … node gexs14 : <CSP IP 5>
LANconfig file saved in /opt/mv36/core/utilsv2
Check of MV36Core-15.09-03 setup

Setup information for MV36Core-15.09-03 is OK.
---- Type <RETURN> to continue ----

Where:
o DSP Name: it’s the DSP server hostname, see section 2.5.2
o DSP IP: it’s the DSP server IP address, see section 2.5.2
o DSP Max Users. : Parallel users logged on the system (≤ 30)
o DSP Max. Managed NEs: Max. managed Network Elements by
DSP server (≤ 6000)
o Number of Communication Server: [1-5] (Distributed)
…
• Accept Basic configuration settings.

Version 15.9.3
Installation Path /
Installation Profile CSP
1/1553-AOM 901 015/3 Uen G 47

DSP: <DSP Name>

CSPs: <DSP Name>

4) Change Lanconfig
Area Severity


-------------------------

3.9 Install ServiceOn Microwave Tools

The ServiceOn Microwave Tools is a software collection used by ServiceOn
Microwave Core and ServiceOn Plug-ins to work correctly. The software
collection is packed with:
• WATCHDOG
48 1/1553-AOM 901 015/3 Uen G
• Mosquito
• ServiceOn-Microwave-Utility
To install the ServiceOn Microwave Tools you can use the graphical installation
via YaST or install everything using a terminal session as root. Its mandatory to
install all the products reported on the software collection.

`Package Groups`, chose the `ServiceOn Microwave Tools` and mark all the
packages.
Figure 3-11 ServiceOn Microwave Tools
drive.

/media/cdrecorder/suse/noarch for Mosquito and /media/cdrecorder/suse/i586
for Watchdog and Utility) and install the required software using the `rpm`
command:
• rpm –i ServiceOn-Microwave-Watchdog-1.1.3-1.i586.rpm
• rpm –i Mosquito-3.3-5.noarch.rpm
• rpm –i ServiceOn-Microwave-Utility-1.1.3-1.i586.rpm
3.10 Install ServiceOn Microwave Plug-ins

The ServiceOn Microwave Plug-ins is a software collection plugged on
ServiceOn Microwave Core. The software collection is composed by a list of
software packages able to manage different network elements.
1/1553-AOM 901 015/3 Uen G 49

To install the ServiceOn Microwave Plug-ins you can use the graphical
installation via YaST or install everything using a terminal session as root. In this
case you have to install only the packages for the network elements installed on
the ServiceOn Microwave Core.
NOTICE At this stage you can install everything but not the MV36emCLIENTS
package. This package in fact should be installed during the Clients install
and configuration.
NOTICE In case of distributed configuration, the MINI-LINK HC, DRS and ETU plug-
ins have not to be installed on the SOM Mediation servers.

`Package Groups`, chose the `ServiceOn Microwave Plug-ins` and mark the
desired plug-ins to install.
Figure 3-12 ServiceOn Microwave Plug-ins
drive.

Login as root and put the SOM DVD in the DVD ROM drive. Move on the
command.
50 1/1553-AOM 901 015/3 Uen G

3.11 Install ServiceOn Microwave PFM-SNMP

The PFM-SNMP is the Practical Fault Management Simple Network
Management Protocol used to export data between the ServiceOn Microwave
Core and a Higher Level Management System.
Figure 3-13 ServiceOn Microwave PFM-SNMP
To install the ServiceOn Microwave PFM-SNMP you can use the graphical
installation via YaST or install everything using a terminal session as root.
In case of distributed configuration, is not required to install the ServiceOn
Microwave PFM-SNMP on the Mediation Servers.

`Package Groups`, chose the `ServiceOn Microwave Interfaces` and mark the
PFM-SNMP package.
1/1553-AOM 901 015/3 Uen G 51

Figure 3-14 ServiceOn Microwave PFM-SNMP graphical installation

repository where the RPM package is located (typically
command:
• rpm –i MV36pfmSNMP-11.6.1-1.i586.rpm
3.12 Install License Manager

The License Manager is a software used by ServiceOn Microwave Core to
correctly license the defined environment. The software is packed with:
• LiMa
To install the License Manager you can use the graphical installation via YaST
or install everything using a terminal session as root.

`Package Groups` , choose Èricsson Tools` and select the LiMa package.
52 1/1553-AOM 901 015/3 Uen G

Figure 3-15 ServiceOn Microwave LiMa
drive.

Login as root and put the SOM DVD in the DVD ROM drive. Move on the
command:
• rpm –i LiMa-2.3-8.i386.rpm
3.13 License Management

The license management has the goal to avoid the installation and execution of
unauthorized copies of products on platforms different from the one they’re sold
for. The software protection mechanism is the basic feature offered by the
Licensing Management. The license cycle can be resumed in the following
steps:
• Retrieve the host fingerprint (Figure 3-16). The host fingerprint is a
sequence of bytes used to authenticate the host. In case of distributed
systems (DSP + CSP) you have to retrieve the host fingerprint for all the
nodes. The host fingerprint can be retrieved in different way:
o From a system with ServiceOn Microwave and License Manager
already installed:
Login as root
/opt/ericsson/LIMA/bin/lima –l
LiMa Command Line Tool v. 2.3

(c) 2006 Marconi/Ericsson
Build ID: Linux_2.6.5-7.97-bigsmp_06349-Fri15Dec-1255 (distro LiMa v.
2.3.8)
Host Fingerprint: 0018717A6216
1/1553-AOM 901 015/3 Uen G 53

Follows list of installed licenses: SOMR8
o From a system where ServiceOn Microwave isn’t installed:

Login as root
/sbin/ifconfig –a | grep eth | awk ‘{gsub(“:”,””,$NF) ; print $1 “” $NF}’ | head –
n1
eth00018717A6216
Figure 3-16 Host fingerprint management
• Send the host fingerprint to Ericsson’s License Center and receive for
every fingerprint a License Key File (LKF) (Figure 3-17).
Figure 3-17 LKF Management
• Install the LKF files (Figure 3-18), remember that every file is associated
to a specified fingerprint and then you have to install the LKF file to the
associated host. To install the LKF file it’s mandatory have installed the
ServiceOn Microwave package and the License Manager:
Login as root
/opt/ericsson/LIMA/bin/lima –i <LKF>
54 1/1553-AOM 901 015/3 Uen G

Figure 3-18 Licensed System
NOTICE If you have request a license from Ericsson factory you can unlock for one
month the system, waiting the official LKF file.
To do that:
• Login as root
• /opt/ericsson/LIMA/bin/lima –u SOMR8
o MV36 Core package: rpm –qa | grep MV36
3.14 FTP Configuration
In order to use 3GPP Services and to support the Backup NE and the software
download towards the network elements, these steps must be executed:
1. Create the “swdownload” functional user (DSP & CSPs)

Login as root
useradd –g nmc –d /home/swdownload –s /bin/csh –c “Software download
functional user” –m swdownload [Return]
2. Define password for “swdownload” functional user (DSP & CSPs)

Login as root
passwd swdownload [Return]
Changing password for swdownload.

New password: <PASSWORD>
Re-enter new password: <PASSWORD>
Password changed
1/1553-AOM 901 015/3 Uen G 55

Where <PASSWORD> is the password chosen for the swdownload user. In

case of distributed configuration the “swdownload” user password must be the
same for all the ServiceOn Microwave servers.
3. Modify ownership for “swdownload” home directory (DSP & CSPs)

Login as root
chmod -R 775 ~swdownload [Return]
4. Enable the vsftp service (DSP & CSPs)
o Edit the file “/etc/xinetd.d/vsftpd” and modify the parameter

“disable” from “yes” to “no”
Login as root
cd /etc/xinetd.d [Return]
vi vsftpd [Return]
#
#
service ftp
{
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/sbin/vsftpd
# server_args =
# log_on_success += DURATION USERID
# log_on_failure += USERID
# nice = 10
disable = no
}
o Edit the “vsftpd” daemon configuration file for “swdownload”

functional user:
Login as root
vi /etc/vsftpd.conf
Change these rows:
#local_enable=YES ⇒ local_enable=YES
#local_umask=022 ⇒ local_umask=022
#write_enable=YES ⇒ write_enable=YES
o Restart the vsftp service

/etc/init.d/xinetd restart [Return]
56 1/1553-AOM 901 015/3 Uen G

5. Edit the “mv36.ini” file (DSP only) and modify the Mv36FtpAddress, the
Mv36FtpUserName, the Mv36FtpPassword and the Mv36FtpRootPath
entries in this way:
o Standalone
Login as root
csh
vi $NCS/data/ini/mv36.ini
Mv36FtpAddress=192.192.192.192
⇓ ⇓ ⇓ ⇓ ⇓ ⇓
Mv36FtpAddress=<DSP IP Address>
Where:
<DSP IP Address> is the DSP IP address towards the
network elements.
Mv36FtpUserName=anonymous
⇓ ⇓ ⇓ ⇓ ⇓ ⇓
Mv36FtpUserName=swdownload
Mv36FtpPassword=mv36
⇓ ⇓ ⇓ ⇓ ⇓ ⇓
Mv36FtpPassword=<PASSWORD>
Where:
<PASSWORD> is the password for the “swdownload” user.
Mv36FtpRootPath=/srv/ftp
⇓ ⇓ ⇓ ⇓ ⇓ ⇓
Mv36FtpRootPath=/home/swdownload
Where:
</home/swdownload> is the location where storing the software
o Multi Server
Login as root on the DSP server
csh
vi $NCS/data/ini/mv36.ini
1/1553-AOM 901 015/3 Uen G 57

Mv36FtpAddress=192.192.192.192
⇓ ⇓ ⇓ ⇓ ⇓ ⇓
Mv36FtpAddress1=<DSP IP Address>
Mv36FtpAddress2=<CSP1 IP Address>
Where:
<DSP IP Address> is the DSP IP address towards the
network elements.
<CSP1 IP Address> is the CSP1 IP address towards
the network elements.
The CSP order is the same used during the LANConfig
creation (see 3.8.3.2).
Mv36FtpUserName=anonymous
⇓ ⇓ ⇓ ⇓ ⇓ ⇓
Mv36FtpUserName=swdownload
Mv36FtpPassword=mv36
⇓ ⇓ ⇓ ⇓ ⇓ ⇓
Mv36FtpPassword=<PASSWORD>
Where:
<PASSWORD> is the password for the “swdownload” user.
Mv36FtpRootPath=/srv/ftp
⇓ ⇓ ⇓ ⇓ ⇓ ⇓
Mv36FtpRootPath=/home/swdownload
Where:
</home/swdownload> is the location where storing the software
58 1/1553-AOM 901 015/3 Uen G

3.15 Web Clients Installation

3.15.1 Server Side
In order to support the web installation of single software components on the
Windows XP PC, on the server side you have to install a specified package to
support this feature. The MV36emCLIENTS is a software collection used to
install the client side for every plug-in plugged on the Core. To install the
MV36emCLIENTS you can use the graphical installation via YaST or install
everything using a terminal session as root. In a distributed environment the
MV36emCLIENTS package must be installed only on the DSP server.
3.15.1.1 Graphical Installation
`Package Groups`, chose the `ServiceOn Microwave Plug-ins` and select the
MV36emCLIENTS package.
Figure 3-19 ServiceOn Microwave Clients
remember that at this stage the SOM DVD must be insert on the DVD ROM
drive.
3.15.1.2 Terminal Installation
Login as root and put the SOM DVD on the DVD ROM drive. Move on the
command:
• rpm –i MV36emCLIENTS-1.0.0-1.i586.rpm
3.15.2 Client Side

Before install the packages you have to update the hosts file
(C:\WINDOWS\system32\drivers\etc) and add the entries for all the ServiceOn
Microwave servers (DSP and CSPs) with the right hostnames and IP
addresses.
1/1553-AOM 901 015/3 Uen G 59

3.15.2.1 Java Installation
On the Client side (Windows XP PC) you have to check if Java Runtime
Environment (JRE 1.5.011) is correctly installed and configured.
The package can be downloaded from http://java.sun.com or from the
ServiceOn Microwave DVD (D:\windows_packages).
Move the package (jre-1_5_11-windows-i586-p.exe) on a safe place and install
it with a double click on the icon file (Figure 3-20).
Figure 3-20 JRE Installation
Select Àccept` to install the Java package, at the end of the process you have
to press `Finish` to exit from the installation process (Figure 3-21).
60 1/1553-AOM 901 015/3 Uen G

Figure 3-21 JRE Installation Completed
3.15.2.2 Web Clients Installation
From the Windows PC XP client start Internet Explorer and on the Àddress Bar`
put the DSP server address with the ServiceOn Microwave GUI port (30305):
• http://<DSP server address>:30305
Figure 3-22 Web Clients Installation
1/1553-AOM 901 015/3 Uen G 61

On the Internet Explorer window select the Ìnstallation` link to open the
software installation page. This page allows the user to install these types of
software:
• LCT Traffic Node
• ServiceOn EM Ghost
• MINI-LINK E Adapter Server
• ServiceOn Microwave Client
Figure 3-23 Software Selection
Install LCT Traffic Node
• Select the LCT Traffic Node

• Accept the digital signature to display the window wizard and press the
“Next” button
62 1/1553-AOM 901 015/3 Uen G

Figure 3-24LCT Traffic Node Installation
• Click on the “Next” button to proceed the installation
1/1553-AOM 901 015/3 Uen G 63

Figure 3-25 LCT Traffic Node Introduction Selection
• Click on the “Next” button to continue the installation, until “Install

Complete” option.
64 1/1553-AOM 901 015/3 Uen G

Figure 3-26 LCT Traffic Node Installation complete
• At the end of the installation process click “Done” button to complete the
procedure
1/1553-AOM 901 015/3 Uen G 65

• Click “Finish” button to exit the wizard.
Install MINI-LINK E Adapter Server
CAUTION In case of MINI-LINK E Adapter Server installation on a virtual machine

hosting Windows XP, is recommended to follow the MINI-LINK E Adapter
Server installation procedure reported in 6.2, copying the
Setup_SOMR8MLEadapter.exe executable file from D:\windows_packages\
(where D is the logical drive letter associated to the DVD ROM unit
containing the ServiceOn Microwave Application media) to the virtual
machine where the MINI-LINK E Adapter should be installed
• Select the MINI-LINK E Adapter Server.

`Next` button.
66 1/1553-AOM 901 015/3 Uen G

Figure 3-27 MINI-LINK E Adapter Server Installation
• Click on the `Next` button to install the desired feature on PC.
Figure 3-28 MINI-LINK E Adapter Server Feature Selection
• Press the `Finish` button to terminate the installation process.
1/1553-AOM 901 015/3 Uen G 67

Figure 3-29 MINI-LINK E Adapter Server Installation Complete
Install ServiceOn EM Ghost
• Select the ServiceOn EM Ghost link.

• Execute the relative msi file.
Figure 3-30 ServiceOn EM Ghost Installation
• Click on the `Next` button.
68 1/1553-AOM 901 015/3 Uen G

Figure 3-31 ServiceOn EM Ghost Installation Wizard
• If desired change the installation path and press the `Next` button.
Figure 3-32 ServiceOn EM Ghost Installation Path
• Finally press Ìnstall` to complete the procedure.
1/1553-AOM 901 015/3 Uen G 69

Figure 3-33 ServiceOn EM Ghost Install Confirmation
• Exit from the installation process by pressing the `Next` button.
Figure 3-34 ServiceOn EM Ghost Installation Finish
Install ServiceOn Microwave Client
70 1/1553-AOM 901 015/3 Uen G

• Select the ServiceOn Microwave Client.

`Next` button.
Figure 3-35 ServiceOn Microwave Client Installation
• Click on the `Next` button to install the desired feature on PC.
Figure 3-36 ServiceOn Microwave Client Feature Selection
• Press the `Finish` button to terminate the installation process
1/1553-AOM 901 015/3 Uen G 71

Figure 3-37 ServiceOn Microwave Client Installation Complete
3.15.2.3 Client off line Installation
If the PC Client at installation time isn’t connected with the ServiceOn

Microwave server (DSP) you can install the Clients off line.
In this case you have to put the ServiceOn Microwave DVD on the DVD drive,
copy the packages from the window_packages directory and start the
installation.
To start the installation you have to select the associated `Setup` file,
`Setup_SOMR8Client.exe`.
Note Due to changes in the security model of DCOM in Microsoft Windows XP
SP2, you need to give MINI-LINK E Adapter Server remote access
permission to the clients, including opening up the firewall.
To configure the clients using a script, do the following on all clients running
Microsoft Windows XP with SP2:
• On the client, open a command prompt and change directory to the
MINI-LINK E Adapter Client installation folder.
Note The MINI-LINK E Adapter Client installation folder is usually
C:\Ericsson\IMA\MINI-LINK\EadapterClient
• At the command prompt, type:

ConfigureXPSP2 /v:1.6 {<ip-address>[/<subnet-mask>]}...
where:
<ip-address> The IP address of a MINI-LINK E Adapter Server that

should be allowed to access this client.
<subnet-mask> The subnet mask used to identify a subnet with one or

more MINI-LINK E Adapter Servers that should be
allowed to access this client.
72 1/1553-AOM 901 015/3 Uen G

1/1553-AOM 901 015/3 Uen G 73

3BInstallation via NFS
4 Installation via NFS
In this section is presented how install ServiceOn Microwave via a Network File
System (NFS). This option is very useful if your server doesn’t have a DVD-
ROM reader (only a CD-ROM) or if you program to create a centralized server
to store the software and use it as Installation Repository.
Figure 4-1 Installation Repository
4.1 Set up an installation repository for ServiceOn

Microwave:
• Copy the installation DVD in a directory of your choice (e.g.
/usr/local/dist/SOM).
• Start YaST and export via NFS the directory (Network Services ⇒ NFS
Server ⇒ Start NFS server ⇒ Next ⇒ Add directory).
74 1/1553-AOM 901 015/3 Uen G

3BInstallation via NFS
Figure 4-2 NFS Exports
• Make a network bootable CD; to do that login on the “Installation

Repository” server and as root execute these steps:
mkdir /tmp/bootcd [Return]

mkdir /tmp/bootcd/boot [Return]
cp –ar /usr/local/dist/SOM/boot/* /tmp/bootcd/boot [Return]
Under /tmp/bootcd/boot remove everything apart root, loader and directory.yast
cp /usr/local/dist/SOM/content* /tmp/bootcd/boot [Return]
cp –ar /usr/local/dist/SOM/media.1 /tmp/bootcd [Return]
Edit the file /usr/local/dist/SOM/boot/loader/isolinux.cfg in this way:
Default somnet
# net inst
label somnet
kernel linux
append initrd=initrd ramdisk_size=65536 splash=silent showpts
install=nfs://<IP address Repository Server> /usr/local/dist/SOM
# memory test
label memtest
kernel memtest
implicit 0
gfxboot bootlogo
display message
prompt 1
timeout 200
readinfo 2
framebuffer 1
notice 2
• Create the ISO image:
cd /tmp/ [Return]
mkisofs –r –o ./bootcd.iso –b boot/loader/isolinux.bin –c boot.cat –no-emul-boot
–boot-load-size 4 –boot-info-table ./bootcd [Return]
Use your favorite CD recording program to bourn the resulting /tmp/bootcd.iso
image
• Boot from CD-ROM reader the server where you want install ServiceOn
Microwave and press somnet to start the procedure via NFS.
1/1553-AOM 901 015/3 Uen G 75

4BServiceOn Microwave Client applications installation on Microsoft Terminal Server Machine
5 ServiceOn Microwave Client applications

installation on Microsoft Terminal Server
Machine
In this section are reported the instructions to install SOM client and all the
needed SW on Microsoft Terminal Server machine.
5.1 Prerequisites
• Windows 2003 SP1 installed.
• Microsoft Terminal Server installed and configured
From the SOM DVD copy the "Windows Package" folder on your Terminal
Server Machine (under C:, for example)
5.2 Java application installation
• Add Remove program, Add New Program

• Choose CD or Floppy
• Next and Browse the folder "Windows Package"
• Select Files of type: All Files
• Select, jre-1_5_0_11-windows-i586-p.exe and click on Open button
• Click Next
• Leave Typical setup selection and click Accept
• In Installation completed window click Finish button.
• Click Next in the "After Installation" window and Finish in "Finish Admin
Install" window, to complete the installation
5.3 SOM Client application installation

• Select, Setup_SOMR8Client.exe and click on Open button
• Click Next
76 1/1553-AOM 901 015/3 Uen G

• In SOMR8-Client - InstallShield Wizard window, click Next

• Leave the default selection and click Next
• Click Next in the "LMT Maintenance Terminal Setup" window
• Select "I accept the terms of the license agreement" and click OK
• Insert the User Name and Company name and click Next
• Leave the default "Setup type" as Complete and click
• Click Install in the "LMT Maintenance Terminal Setup" window
• Click Finish in the "LMT Maintenance Terminal Setup" window
• In SOMR8-Client - InstallShield Wizard window, click Finish
5.4 MV36 Ghost application installation

• Select, mv36ghost_010202.msi and click on Open button
• Click Next
• Click Next in MV36Ghost_1.2.2 Setup window
• In the next window, Leave the default destination Folder and click Next
and then Install
• Click Next in MV36Ghost_1.2.2 Setup window and then Finish
5.5 TN LCT application installation

• Select, Setup_LCT_TN.exe and click on Open button
• Click Next
• Click Next in LCT TN -InstallShield Wizard window
• Click Next in welcome window
• In MINI-LINK Craft 1.0 window click Next and then Next leaving the
default settings
• Click Next leaving the default "Shortcut Folder" and then Next
1/1553-AOM 901 015/3 Uen G 77

• In Pre-Installation Summary window click Install

• Click OK on RegSvr32 window
• In Installation Complete window, Click Done, selecting "No, Restart my
system later" item
• Click on Finish button in LCT TN - InstallShield Wizard window
• Restart the machine
78 1/1553-AOM 901 015/3 Uen G

5BMINI-LINK E Adapter Server Installation
6 MINI-LINK E Adapter Server Installation
6.1 MINI-LINK E Adapter Server Installation: Introduction

The ServiceOn Microwave Server Application also includes MINI-LINK E
Adapter software. It is software necessary to act as an interface to MINI-LINK C
and MINI-LINK E. This chapter can be skipped if those equipments type are not
part of the network.
This software can due to load distribution reasons be installed either on the
same server as the ServiceOn Microwave Server (Co-located installation) or on
separate hardware platforms connected to the ServiceOn Microwave Server
(Stand Alone Installation).
The following paragraphs describe the procedure to install and configure the
MINI-LINK E Adapter server SW.
6.2 MINI-LINK E Adapter server co-located

MINI-LINK E Adapter software can be installed on Windows XP OS. To install it
on the same ServiceOn Microwave server platform running on Linux OS, it is
necessary to create a virtual machine hosting Windows XP.
At this stage you are free to use any virtual machine package able to host
Windows XP as guest operating system.
When then virtual machine is ready to startup proceeding with the installation of
the guest OS from CD.
6.2.1 Guest OS installation: Windows XP SP2 installation and configuration

Insert the Windows XP installation CD and boot the virtual machine.
The installation program shall start automatically, if this does not happen, apply
specific computer procedure to start the Windows XP Professional installation
from CD-ROM drive. The Regional and Language Settings window will appear
during Windows XP Professional installation. Set to English (United States) and
clicking on Customize button and choose the Date tab. Set the Short Data
Format to MM/dd/YYYY. If the customer does not use "United States"
measurement system change it to "Metric" clicking on Customize button. Select
the appropriate Time Zone. Set the Computer Name with the name length Max
8 characters.
If the Windows XP installation CD already contains the Service Pack 2 the
following options windows will be displayed.
When the Help to protect your PC window will appear, select Not Right Now
option and click Next.
Define at least one user name that will be used as computer administrator.
--------------------------------------------------------------------------------
Caution!
The password for this user is empty. Modify it at the first log-on.
--------------------------------------------------------------------------------
1/1553-AOM 901 015/3 Uen G 79

6.2.2 System File Patches

If the Windows XP Professional installed has a patch level different from Service
Pack 2, it must be updated.
After the installation is complete, restart your computer as required and then:
• A window will appear to choose the Help to protect your PC installation
configuration. Choose the not-recommended option (No right Now).
• Login the computer to fin
6.2.3 Windows XP Security Configuration

Login as local administrator and apply the following steps:
• Disable the windows Firewall:
o From Start->Settings->Control Panel and Switch to Class
View from the left frame.
o Open Windows Firewall and select the not-recommended option
Off.
• Disable the windows Security Center alert:
o From Start->Settings->Control Panel, open the Security
Center.
o From the left frame select Change the way Security
Center alerts me.
o Uncheck all the Alarm Settings check box present.
o Close all windows.
• Disable the Automatic Update:
o From Start button, right click on My Computer icon and
choose Properties from the menu.
o Select the Automatic Update tab and set Turn off
Automatic Updates.
o Click Ok to apply the changes.
• Turn off the Welcome screen:
o From Start->Settings->Control Panel, open the User Account.
o Click on Change the way users log on or off.
o Disable both the checkbox and click on Apply Options button.
6.2.4 Configuring DCOM For Windows XP SP2

In order to configure DCOM using Windows XP Service Pack 2 on MINI-LINK
Manager Client, follow these steps:
80 1/1553-AOM 901 015/3 Uen G

• Go to Start -> Run and type DCOMCnfg and click on OK.
Figure 6-1 DCOM
• Click on Component Services under the Console Root to expand it.

• Click on Computers under Component Services to expand it.
• Right click on My Computer in the pane on the right and select
Properties.
Figure 6-2 Component Services
• Go to the COM Security tab and note these are the four permission
configurations to be edited:
Figure 6-3 Computer Properties
1/1553-AOM 901 015/3 Uen G 81

• Click on Edit Limits... button in the Access Permissions area.

Add in Group or user names list ANONYMOUS LOGON and Everyone groups,
do the following:
a. Click Add.
b. In the Select Users or Groups dialog box, click Advanced.
c. In the second Select Users or Groups dialog box, click Find Now.
d. In the list, at the bottom of the dialog box, select ANONYMOUS LOGON.
e. Click OK to close both the "Select Users or Groups" dialog boxes.
f. Verify that Local Access and Remote Access are checked for allow
column.
Figure 6-4Access Permission
Repeat the previous steps from a to f for Everyone group.
82 1/1553-AOM 901 015/3 Uen G

• Clibk OK Button on the Access Permission window

• Click on Edit Limits... button in the Launch and Activation Permissions
area.
do the following:
a. Click Add.
d. In the list, at the bottom of the dialog box, select Everyone.
f. Verify that Local Launch, Remote Launch, Local Activation and Remote
Activation are checked for allow column.
The remote boxes for the user labeled Everyone must be checked in this dialog.
1/1553-AOM 901 015/3 Uen G 83

Figure 6-6 Launch Permission
Repeat the previous steps from a to f for ANONYMOUS LOGON group.
Figure 6-7Launch Permission
• For each user (or group) make sure that both the Local Allow and
Remote Allow checkboxes are both checked.
84 1/1553-AOM 901 015/3 Uen G

Access Permissions per user:
Figure 6-8 Permission
Launch and Activation permissions per user:
6.2.5 Network Configuration of Windows XP SP2 guest OS

Based on the host operative system network configuration it is necessary to
require the customer one or more extra IP addresses to assign to the Windows
XP virtual machine.
To assign those IP address to the network adapters in Windows XP SP2 guest
OS it necessary to control the Virtual Network device and the physical Network
device association, especially when the host server has been configured to act
against two different sub-networks.
6.2.6 3rd party software installation

It is required to install the Sun Java Runtime Environment (JRE) Standard
Edition 5.0 present on the ServiceOn Microwave Application media following the
steps below.
• Insert the ServiceOn Microwave Application media in the DVD ROM unit
and execute the setup:
D:\windows_packages\jre-1_5_0_11-windows-i586-p.exe
(Where D is the logical drive letter associated to the DVD ROM unit)
• Accept the Licensing terms leaving the default choice “Typical
installation”
• Wait to the application installation and select End to complete it.
6.2.7 MINI-LINK E Adapter server installation

To start the MINI-LINK E Adapter installation program follow the steps below.
• Execute the MINI-LINK E Adapter server setup:
D:\windows_packages\Setup_SOMR8MLEadapter.exe
(Where D is the logical drive letter associated to the DVD ROM unit).
1/1553-AOM 901 015/3 Uen G 85

• Click on the `Next` button to Wizard window to display the desired feature
to install on the PC (Figure 6-10).
Figure 6-10 MINI-LINK E Adapter server installation wizard
• The “MINI-LINK E Adapter Server” feature is selected. Press the `Next`

button to install it.
Figure 6-11 MINI-LINK E Adapter server software selection
• Wait for the files installation.
86 1/1553-AOM 901 015/3 Uen G

Figure 6-12 MINI-LINK E Adapter server installation
• At the end of the installation process click “Finish” button to complete the
procedure.
Figure 6-13 MINI-LINK E Adapter server installation finish
6.2.8 MLEAdapterServer DCOM Configuration

6. Go to Start -> Run and type DCOMcnfg and click on OK.
7. In the Component Services window, expand Component Services-
>Computers->My Computer->DCOM Config.
8. Right-click on MLEAdapterServer and then click Properties on the shortcut
menu. The MLEAdapterServer Properties dialog box opens.
9. On the Security tab, under Launch and Activation Permissions, select
Customize, and then click Edit. The Launch Permission dialog box opens.
1/1553-AOM 901 015/3 Uen G 87

10. Add in Group or user names list ANONYMOUS LOGON and Everyone
groups, do the following:
a. Click Add.
d. In the list, at the bottom of the dialog box, select ANONYMOUS
LOGON.
e. Click OK to close both Select Users and Groups dialog boxes.
Repeat the steps for Everyone group.
11. In the Permissions for list, select the Allow Local Launch, Remote Launch,
Local Activation and Remote Activation check boxes.
12. Click OK to close the Launch Permission dialog box.
13. Click OK to close the MLEAdapter Properties dialog box.
6.3 MINI-LINK E Adapter server Stand Alone

MINI-LINK E Adapter software can be installed on a separated server either with
Windows XP Professional SP2 or Windows Server 2003 SE. The OS installation
and configuration is reported by the paragraph below.
See the following specifications for the hardware requirements (Ericsson
specifications) to be sure to have the correct equipment on which run the
Operative System and the MINI-LINK E Adapter stand-alone.
The platform specifications described below serves as a general hardware
recommendation for the server HW platform, which will host the MINI-LINK E
Adapter Server stand alone:
Central Processor Unit Unit Intel Pentium 4 > 2 GHz
Primary memory 512 MByte
Un-removable media 20 GByte disk
Removable media CD-ROM drive
Screen VGA Monitor (800x600)
DCN connection 10/100 BaseT LAN
Operating System software Microsoft Windows XP SP2 or Windows

Server 2003 SP1
The exact hardware platform highly depends on the need for performance,
availability, history log, number of adaptations, number of applications and so
on. For more exact specifications of the hardware platform, please contact your
Ericsson representative.
6.3.1 Operative System installation and configuration: Windows XP SP2

Insert the Windows XP installation CD and boot the machine.
The installation program shall start automatically, if this does not happen, apply
specific computer procedure to start the Windows XP Professional installation
from CD-ROM drive.
88 1/1553-AOM 901 015/3 Uen G

The Regional and Language Settings window will appear during Windows XP
Professional installation. Set to English (United States) and clicking on
Customize button and choose the Date tab. Set the Short Data Format to
MM/dd/YYYY. If the customer does not use "United States" measurement
system change it to "Metric" clicking on Customize button.
Select the appropriate Time Zone.
Computer names must contain only alphanumeric characters (no special
character is allowed).
If the Windows XP installation CD already contains the Service Pack 2 the
following options windows will be displayed.
When the Help to protect your PC window will appear, select Not Right Now
option and click Next.
Define at least one user name that will be used as computer administrator.
Caution!
The password for this user is empty. Modify it at the first log-on.
6.3.1.1 System File Patches
If the Windows XP Professional installed has a patch level different from Service
After the installation is complete, restart your computer as required and then:
• A window will appear to choose the Help to protect your PC
installation configuration. Choose the not-recommended option (No right
Now).
• Login the computer to finalize the installation.
6.3.1.2 Windows XP Security Configuration
Login as local administrator and apply the following steps:

• Disable the windows Firewall:
o From Start->Settings->Control Panel and Switch to Class
View from the left frame.
o Open Windows Firewall and select the not-recommended option
Off.
• Disable the windows Security Center alert:
o From Start->Settings->Control Panel, open the Security
Center.
o From the left frame select Change the way Security
Center alerts me.
o Uncheck all the Alert Settings check box present.
o Close all windows.
• Disable the Automatic Update:
1/1553-AOM 901 015/3 Uen G 89

o From Start button, right click on My Computer icon and

choose Properties from the menu.
o Select the Automatic Update tab and set Turn off
Automatic Updates.
o Click Ok to apply the changes.
• Turn off the Welcome screen:
o From Start->Settings->Control Panel, open the User Account.
o Click on Change the way users log on or off.
o Disable both the checkbox and click on Apply Options button.
6.3.1.3 Configuring DCOM For Windows XP SP2
In order to configure DCOM using Windows XP Service Pack 2 on MINI-LINK

Manager Client, follow these steps:
• Go to Start -> Run and type DCOMCnfg and click on OK.
Figure 6-14 DCOM
• Click on Component Services under the Console Root to expand it.

• Click on Computers under Component Services to expand it.
• Right click on My Computer in the pane on the right and select
Properties.
• Go to the COM Security tab and note these are the four permission
90 1/1553-AOM 901 015/3 Uen G

• Click on Edit Limits... button in the Access Permissions area.

do the following:
a. Click Add.
d. In the list, at the bottom of the dialog box, select ANONYMOUS LOGON.
column.
1/1553-AOM 901 015/3 Uen G 91

92 1/1553-AOM 901 015/3 Uen G

• Clibk OK Button on the Access Permission window

• Click on Edit Limits... button in the Launch and Activation Permissions
area.
do the following:
a. Click Add.
f. Verify that Local Launch, Remote Launch, Local Activation and Remote
Activation are checked for allow column.
The remote boxes for the user labeled Everyone must be checked in this dialog.
1/1553-AOM 901 015/3 Uen G 93

• For each user (or group) make sure that both the Local Allow and
Remote Allow checkboxes are both checked.
Access Permissions per user:
94 1/1553-AOM 901 015/3 Uen G

Launch and Activation permissions per user:
6.3.1.4 Windows Server 2003 SE
Check the Windows Server 2003 Standard Edition installation package if it

contains one CD-ROM disc.
• Most new servers that are recommended in the above documentation,

have the ability to boot on the installation CD for Windows Server 2003
Standard Edition directly.
• If this is the case, just power on the server and insert the CD in the CD-
ROM drive.
• The installation program shall start automatically.
• For Workgroup or Domain choose a domain if it is already present,

otherwise choose Workgroup and then insert the PC in the existing
domain.
• The Windows Server 2003 family does not include Setup boot floppy
disks, therefore the procedure indicated in the article at the following
link must be followed:
http://support.microsoft.com/default.aspx?scid=kb;en-us;810562, for
Start Windows Server 2003 Setup from MS-DOS.
• Besides Create a Boot Floppy with a Windows Server 2003-Based

Computer or Create a Boot Floppy Without a Windows Server 2003-
Based Computer, the procedure indicated in the article at the link must
be followed: http://support.microsoft.com/default.aspx?scid=kb;en-
us;325879#3.
1/1553-AOM 901 015/3 Uen G 95

Note Windows Server 2003 Standard Edition must be installed on C partition and
on the system directory WINDOWS. Check if the Regional and Language
and Language Option is set to English (United States) in the Regional and
Language Settings window during Windows Server 2003 Standard Edition
installation.
During the Windows Server 2003 Standard Edition installation, in the Windows
Setup dialog box, the following must be done:
1. For Licensing Mode select Per Server with Number concurrent connections
with number 10.
2. For Network Settings selects Typical.
3. For Workgroup or Domain choose a domain if it is already present,
otherwise choose Workgroup and then follow the instructions in Section
5.4.11.
At first logon the Windows Server 2003 Standard Edition Configure your Server
dialog appears.
Choose to configure the server later and uncheck the option Show this message
at system start-up.
Computer Name
Computer names must contain only alphanumeric characters (no special
character is allowed).
Dr Watson
Initialise DrWatson by starting a DOS prompt and type:
drwtsn32 -i
Then start the DrWatson control window by typing:
drwtsn32
In the window that appears, tick the top three boxes under Options and leave
the rest. Set the log directory to C:\WINDOWS (substitute C:\ for the appropriate
drive letter); for default the log directory is C:\Document and
Settings\Administrator\Local Settings\Application Data\Microsoft\Dr Watson.
Windows Enable Network COM+ Access

In Windows Server 2003 Standard Edition "Enable network COM+ access"
must be installed to use distributed applications on the network.
To install "Enable network COM+ access" service Open Windows Components
wizard, from Add/Remove Programs, check Add/Remove Windows
Components. In Components, click Application Server (but do not select or clear
its check box), and then click Details; select "Enable network COM+ access"
check box, and click OK and after click Next and insert the Windows Server
2003 Standard Edition Installation CD to let the program access the needed
files.
96 1/1553-AOM 901 015/3 Uen G

Configuring The Server On The Network

Before continuing with the server configuration, the following information shall be
received from the local network administrator:
1. The Domain Controller (DC) the server will have to join
2. The DNS server installed into the domain
3. The IP address and subnet mask to be configured for the server
Note that the MINI-LINK E Adapter Server IP address must be static one.
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.
Check of Windows 2003 SP1 installation

If the Windows Server 2003 installed has a patch level different from Service
Windows 2003 SP1 Configuration Procedure

The updated security model of Microsoft Windows 2003 Server SP1, some
configurations must be changed:
Internet Explorer 6.0

1. Launch Internet Explorer Browser.
2. Click on Internet Option under the Tool menu.
3. Select Security tab.
Figure 6-23 Explorer Options
1/1553-AOM 901 015/3 Uen G 97

4. Select Trusted Sites.

5. Click on Sites&mldr; button.
6. Uncheck Require server verification (https:) for all sites in this zone.
Windows 2003 Security Configuration

1. Login as local administrator and apply the following settings:
2. Disable the windows Firewall:
From Start->Settings->Control Panel and Switch to Class View from the left
frame.
Open Windows Firewall and select the not-recommended option Off.
3. Disable the Automatic Update:
Right click on My Computer icon stands on the desktop and choose
Properties from the menu.
Select the Automatic Update tab and set Turn off Automatic Updates.
Click Ok to apply the changes.
Allow Remote Access for Anonymous Logon and Remote Activation for
Groups and Users
In order to configure DCOM using Windows 2003 Server Service Pack 1 on
MINI-LINK Manager Server, follow these steps:
1. Go to Start -> Run and type DCOMCnfg and click on OK.
Figure 6-24 DCOM
2. Click on Component Services under the Console Root to expand it.

3. Click on Computers under Component Services to expand it.
4. Right click on My Computer in the pane on the right and select Properties.
98 1/1553-AOM 901 015/3 Uen G

5. Go to the COM Security tab and note these are the four permission
6. Click on Edit Limits... button in the Access Permissions area.

Add in Group or user names list ANONYMOUS LOGON and Everyone
a. Click Add.
LOGON.
e. Click OK to close both the “Select Users or Groups” dialog boxes.
column.
1/1553-AOM 901 015/3 Uen G 99

Figure 6-27 Access Permission
7. Click OK button on the Access Permission window.

8. Click on Edit Limits... button in Launch and Activation Permissions area.
100 1/1553-AOM 901 015/3 Uen G

Add in Group or user names list ANONYMOUS LOGON and Everyone

a. Click Add.
e. Click OK to close both the “Select Users or Groups” dialog boxes.
f. Verify that Local Launch, Remote Launch, Local Activation and
Remote Activation are checked for allow column.
9. Click OK button on the Launch Permission window.
1/1553-AOM 901 015/3 Uen G 101

Data Execution Prevention (DEP): disable procedure

1. Right click on My Computer desktop icon and select Properties from the
menu.
2. In the System Properties window select the “Advanced” tab.
3. In the Startup and Recovery section click on the Settings button.
Figure 6-31 System Properties
4. In the Startup and Recovery window click on the Edit button to modify the
startup options manually.
Figure 6-32 Startup and Recovery
102 1/1553-AOM 901 015/3 Uen G

5. In the notepad window appears the Boot.ini file information. Replace the
"/NoExecute" option "OptOut" with "alwaysoff". Save the changes and Re-
Start the server.
Figure 6-33 Boot.ini File
6. When the server is back verify the DEP feature is disabled.

7. Right click on the My Computer desktop icon and select Properties from
the menu.
8. In the System Properties window select the “Advanced” tab.
9. In the Performance section click on the Settings button.
Figure 6-34 System Properties
10. In the Performance Setting window select the Data Execution Prevention
tab to check it is completely greyed out.
1/1553-AOM 901 015/3 Uen G 103

Figure 6-35 Performance Options
6.3.2 3rd party software installation

It is required to install the Sun Java Runtime Environment (JRE) Standard
Edition 5.0 present on the ServiceOn Microwave Application media following the
steps below.
1. Insert the ServiceOn Microwave Application media in the DVD ROM unit
and execute the setup:
D:\windows_packages\jre-1_5_0_11-windows-i586-p.exe
(Where D is the logical drive letter associated to the DVD ROM unit)
2. Accept the Licensing terms leaving the default choice “Typical installation”
3. Wait to the application installation and select End to complete it.
6.3.3 MINI-LINK E Adapter server installation

To start the MINI-LINK E Adapter installation program follow the steps outlined
below.
• Execute the MINI-LINK E Adapter server setup:

D:\windows_packages\Setup_SOMR8MLEadapter.exe
(Where D is the logical drive letter associated to the DVD ROM unit).
104 1/1553-AOM 901 015/3 Uen G

• Click on the `Next` button to Wizard window to display the desired

feature to install on the PC.
Figure 6-36 MINI-LINK E Adapter server installation wizard
• The “MINI-LINK E Adapter Server” feature is selected. Press the `Next`

button to install it.
Figure 6-37 MINI-LINK E Adapter server software selection
1/1553-AOM 901 015/3 Uen G 105

• Wait for the files installation.
Figure 6-38 MINI-LINK E Adapter server installation
• At the end of the installation process click “Finish” button to complete the
procedure.
Figure 6-39 MINI-LINK E Adapter server installation finish
6.3.4 MLEAdapterServer DCOM Configuration

1. Go to Start -> Run and type DCOMcnfg and click on OK.
2. In the Component Services window, expand Component Services-
>Computers->My Computer->DCOM Config.
3. Right-click on MLEAdapterServer and then click Properties on the shortcut
menu. The MLEAdapterServer Properties dialog box opens.
106 1/1553-AOM 901 015/3 Uen G

4. On the Security tab, under Launch and Activation Permissions, select

Customize, and then click Edit. The Launch Permission dialog box opens.
5. Add in Group or user names list ANONYMOUS LOGON and Everyone
a. Click Add.
LOGON.
e. Click OK to close both Select Users and Groups dialog boxes.
f. Repeat the steps for Everyone group.
6. In the Permissions for list, select the Allow Local Launch, Remote Launch,
Local Activation and Remote Activation check boxes.
7. Click OK to close the Launch Permission dialog box.
8. Click OK to close the MLEAdapter Properties dialog box.
1/1553-AOM 901 015/3 Uen G 107

6BChange Configuration
7 Change Configuration
7.1 Change Configuration: Introduction

Scope of this section is describe the steps that must be performed to change the
ServiceOn Microwave configuration when the system is shipped to customer
site and the client need to change the network configuration for correctly
manage the servers into the company network.
Figure 7-1 Initial Configuration
Then in this case we suppose for example that all the ServiceOn servers
(DSP/CSP) are shipped on the customer network with this network
configuration:
• DSP
Name: DSPold
IP address: 1.1.1.1
• CSP - 1
Name: CSP1old
IP address: 2.2.2.2
• CSP – 2
Name: CSP2old
IP address: 3.3.3.3
• CSP – 3
Name: CSP3old
IP address: 4.4.4.4
In this case to correctly manage the ServiceOn servers on the company network
the customer need change the server names and the addresses. The proposal
values are only an example to correctly show all the needed steps.
108 1/1553-AOM 901 015/3 Uen G

• DSP
Name: DSPnew
IP address: 172.16.245.25
• CSP - 1
Name: CSP1new
IP address: 172.16.245.26
• CSP – 2
Name: CSP2new
IP address: 172.16.245.27
• CSP – 3
Name: CSP3new
IP address: 172.16.245.28
Figure 7-2 Final Configuration
7.1.1 Change Network Configuration

These steps must be executed on all ServiceOn Microwave servers, then the
DSP and the CSPs. Before change the network configuration you have to stop
the ServiceOn Microwave and the relative data base (Ingres). To do that login
as root and execute these steps:
• Stop MV36 by typing:
/etc/init.d/soo_mv36 stop [Return]
• Check if MV36 is correctly stopped by typing:
ps –unmcman | grep mv36_sys | wc –l [Return]
The command output must be equal to “0”
• Stop the data base by typing:
/etc/init.d/ingresII stop [Return]
• Check if the data base is stopped by typing:
/etc/init.d/ingresII check [Return]
1/1553-AOM 901 015/3 Uen G 109

The command output must show all the servers in a not active state
To change the network configuration login as root on the server and start YaST.
• Select Network Devices.
• Select Network Card.
• Change the Already configured devices.
• Select Edit. In the Network address setup window you have to choose a
Static address setup and fill the relative fields (IP address and Netmask)
with the correct values. Then ask to the system administrator if you don’t
know what add at this point. In this case we suppose to configure the
DSP server with these values:
IP address: 172.16.245.26
Netmask: 255.255.255.0
Hostname: DSP_new
Domain: domain.test
Default Gateway: 172.16.245.254
Name Server: No DNS server, using /etc/hosts
Figure 7-3 Network Address Setup
• Select Host name and name server and put the selected host name and
the domain. In this case DSPnew and domain.test. If in the company
network is present a DNS system you can add the DNS reference on the
relative fields to correctly solve the address with an external system.
110 1/1553-AOM 901 015/3 Uen G

Figure 7-4 Hostname & DNS
• Select OK and after Routing. In the routing configuration window insert

the Default gateway information, in this case 172.16.245.254.
Figure 7-5 Routing
• Select OK.
• Select Next.
• Select Finish and Close the YaST control center window.
At this point all the ServiceOn Microwave servers must be connected on the
company network then try to login from an external system from see if they are
reachable and after try to do the reverse process to see if it’s possible contact
the company network.
Remember to update the system files with the new network topology, see 3.1.
1/1553-AOM 901 015/3 Uen G 111

7.1.2 Change NFS Client Configuration

The CSP servers to correctly run the ServiceOn application mount via NFS the
/opt/mv36/core/nmc file system. In this case on all CSPs you have to modify the
Host name of the NFS server; in our example from DSPold to DSPnew.
Figure 7-6 NFS Layout
To do that login as root and start the YaST control center.

• Select Network Services.
• Select NFS Client.
• Select Edit and put on the Host name of the NFS server the correct
value, in this case DSPnew.
Figure 7-7 NFS Client Configuration
• Select OK.
112 1/1553-AOM 901 015/3 Uen G

• Select Finish and Close the YaST control center window.
7.1.3 Change ServiceOn Microwave configuration

Changing the host name and the IP address has an impact on the ServiceOn
Microwave normal execution. Then at this point isn’t possible have the system
up and running. To solve this issue you have to reconfigure the system to load
the new environment. To do that you can use the change_configuration utility;
the service must be executed on all the ServiceOn servers (DSP/CSPs).
In order to correctly change the ServiceOn configuration its mandatory run the
change_configuration script on the DSP server first Its also mandatory execute
the change_configuration script on the CSPs even if the communication server
configuration it’s not changed.
• DSP
Login as root
cd /opt/soo/tools [Return]
./change_configuration [Return]
************************************************************
* *
* Change Configuration for ServiceOn Microwave *
* *
************************************************************
Check if Ingres 2006 is correctly Installed and Configured

Ingres 2006 detected
Check if Ingres 2006 is running

Ingres 2006 isn't running
Check if MV36 is correctly Installed and Configured

MV36 detected
Check if MV36 is running

MV36 isn't running
Managing IPs and names:
- 1 - Checking Host Role

is a DSP
- 2 - Defining old/new values
Old Name 1 = DSPold

Old IP 1 = 1.1.1.1
New Name 1 = DSPnew
New IP 1 = 172.16.245.25
Old Name 2 = CSP1old

Old IP 2 = 2.2.2.2
New Name 2 = CSP2new
New IP 2 = 172.16.245.26
1/1553-AOM 901 015/3 Uen G 113

Old Name 3 = CSP2old

Old IP 3 = 3.3.3.3
New IP 3 = 172.16.245.27
Old Name 4 = CSP3new

Old IP 4 = 4.4.4.4
New IP 4 = 172.16.245.28
Summarised Values:
------------------
Old Name: DSPold

New name: DSPnew
Old IP: 1.1.1.1
New IP: 172.16.245.25
Old Name: CSP1old

New name: CSP1new
Old IP: 2.2.2.2
New IP: 172.16.245.26
Old Name: CSP2old

New name: CSP2new
Old IP: 3.3.3.3
New IP: 172.16.245.27
Old Name: CSP3old

New name: CSP3new
Old IP: 4.4.4.4
New IP: 172.16.245.2t
Are you sure? (Y/N)Y
At this point if the values are correct you can type Y to automatically
start the reconfiguration process.
Reconfiguring Ingres with these parameters
- 1 - Modify files
OK
- 2 - Modify config.dat
OK
- 3 - Modify symbol
OK
- 4 - Reconfigure NET
OK
- 5 - Flush Log files

OK
114 1/1553-AOM 901 015/3 Uen G

Reconfiguring MV36 with these parameters
- 1 - Flush spool files

OK
- 2 - Flush log files

OK
- 3 - Modify user files

OK
- 4 - Modify mv36_nm.ini
OK
- 5 - Modify LANconfig
OK
- 6 - Modify mv36_sys_md
OK
- 7 – Restart NSD daemon

OK
- 8 – Regen DB.properties
OK
/etc/init.d/ingresII start [Return]

su nmcman [Return]
csh [Return]
source /etc/mv36.cshrc [Return]
./UpdateNodeName.csh [Return]
• CSP
Login as root
./change_configuration [Return]
************************************************************
* *
* Change Configuration for ServiceOn Microwave *
* *
************************************************************



MV36 detected

MV36 isn't running
1/1553-AOM 901 015/3 Uen G 115

Managing IPs and names:

is a CSP
- 2 - Defining old/new values
Old Name = CSP1old

Old IP = 2.2.2.2
New Name = CSP1new
New IP = 172.16.245.26
Summarised Values:
------------------
Old Name: CSP1old

New name: CSP1new
Old IP: 2.2.2.2
New IP: 172.16.245.26
At this point if the values are correct you can type Y to automatically start the
reconfiguration process.
Reconfiguring Ingres with these parameters
- 1 - Modify files
OK
- 2 - Modify config.dat
OK
- 3 - Modify symbol
OK
OK
- 5 - Flush Log files

OK
- 1 - Flush spool files

OK
- 2 - Flush log files

OK
- 3 - Modify user files

OK
OK
If you have already run the configuration script to execute the utility again you
have to remove these files:
• /opt/in gres/files/.configured
• /opt/mv36/core/nmc/instnmc/MV36v15.8.1/data/.configured
116 1/1553-AOM 901 015/3 Uen G

7.1.4 MINI-LINK E Adapter Server Change Configuration

If the IP address of the MINI-LINK E Adapter Server (co-located or stand-alone)
changes, the right actions must be implemented on the DSP server that
manages it.
To do that:
• Login as nmcman on DSP server
• csh [Return]
• source /etc/mv36.cshrc [Return]
• cd $NCS/script [Return]
• ./updNeAddress.csh <IP Orig> <IP Dest> [Return]
Where:
• <IP Orig> is the old MINI-LINK E Adapter Server IP address
• <IP Dest> is the new MINI-LINK E Adapter Server IP address
1/1553-AOM 901 015/3 Uen G 117

7BActive Directory Management
8 Active Directory Management
This section must be used if your ServiceOn Microwave system it’s integrated in
a Microsoft Active Directory environment; the scope is support the system
administrators to develop a single sign on mechanism on ServiceOn Microwave
using MS Windows Active Directory as centralized workplace to store user
authentication tokens such as login name, password and user profiles (Figure
8-1).
Figure 8-1 ServiceOn Microwave & Active Directory
8.1 Overview
ServiceOn Microwave offers a mechanism of centralized user administration,
allowing managing users by Windows Active Directory Servers.
The principle is to integrate ServiceOn Microwave user administration in generic
user administration, performing administration tasks such as user
creation/removal, definition of the password and definition of user profiles in a
centralized manner by using an Active Directory Server. ServiceOn Microwave
users can benefit of this because once a user is setup, he/she can login on all
enabled servers.
The principle is:
• Define the user within Active Directory Server.
• Configure a set of ServiceOn Microwave servers to work with Active
Directory Server. This requires a special configuration, by default
ServiceOn Microwave is not enabled to work with Active Directory
Servers.
118 1/1553-AOM 901 015/3 Uen G

• Once a user attempts to login on such remote ServiceOn Microwave

server, the server performs transparent authentication to remote Active
Directory Server and if the user is authorized, he/she is automatically
configured to work with that server. The automatic configuration, if
required, involves:
1. Creation of the Linux user if not already present.
2. Creation of the ServiceOn Microwave user (in the database) if not already
present.
3. Update user profile from the one configured on Active Directory server.
• In such way the user can login by using the same password and profile
on all configured ServiceOn Microwave servers.
• An offline script is available on ServiceOn Microwave server to perform
automatic synchronization of Active Directory server with local host
configuration. In ServiceOn Microwave this can be used to remove
(purge) users configured on ServiceOn Microwave server but no more
present in remote Active Directory server.
• The configuration allows managing fault scenarios, allowing configuring
ServiceOn Microwave servers to work with more than one Active
Directory server.
8.2 Windows Domain Controller Configuration

• Install Active Directory on Windows 2003 Server Enterprise edition
• Configure DNS service
• Configure to work as NTP server (should be the default)
• Configure ServiceOn Microwave Users in Active Directory (8.2.1)
• Optionally a backup Active Directory Server can be configured
• Other settings to be specified, the default ones should be enough to
work with SOM.
8.2.1 User Configuration

The following procedure documents how to configure users with an Active
Directory server as ServiceOn Microwave users.
All the following steps must be executed on the domain controller.
Log on the domain controller as administrator, open the user management
window (Start->Programs->Administrative Tools->Active Directory Users and
computers), click on the SOM organizational unit and add the ServiceOn
Microwave userids to the proper groups.
8.2.1.1 Create a functional User
The functional user is used by ServiceOn Microwave to access remote Active

Directory server in order to perform queries to get user profiles.
The default name used by ServiceOn Microwave is somldap; the name can be
changed by editing the /opt/mv36/core/data/data/ini/som_AD.cfg file on the DSP
host and changing the value of the variable somldapuser.
1/1553-AOM 901 015/3 Uen G 119

The functional user is mandatory and is created as a member of the Users

group (default group) on the domain controller.
8.2.1.2 Create a organization Unit
The default organizational unit name is SOM; the name can be changed by
editing the /opt/mv36/core/data/data/ini/som_AD.cfg file on the DSP host.
To create the Organizational Unit, right click on the domain item on the left of the
panel and select New->Organizational Unit.
All users and groups are defined within this organizational Unit.
8.2.1.3 User profile Creation
Within the ServiceOn Microwave organizational unit (SOM), create the following
groups to reflect user profiles:
Group name Group Scope Group Type
ReadOnly Global Security
ReadWrite Global Security
Nmc Global Security
User profiles mapping is stored on SOM hosts in
/opt/mv36/core/data/data/ini/som_AD_groups.cfg file on the DSP host.
The file specifies the mapping between an Active Directory group name and the
internal profile number used by ServiceOn Microwave to describe the user
profile.
8.2.1.4 User Creation
Within the ServiceOn Microwave organizational unit (SOM), create the new
users and assign them to only one of the groups defined in the previous step.
Important note: Current implementation supports up to 8 characters for the
user name.
Important note: An active directory userid will not have a valid profile in Service
On Microwave Application if one of the following conditions occurs:
• account does not belong to one of the groups defined in SOM
organizational unit
• account belongs to more than one group defined in SOM organizational
unit
8.2.1.5 User Configuration
Once logged in at least one time on local ServiceOn Microwave host, an

administrator can open the SOUP window to setup user configuration relevant
to the particular ServiceOn Microwave (configuration that cannot be shared on
all servers, working domain and working time)
8.2.1.6 How to change the User Password
Currently user password can be changed in different ways:

• By Windows domain administrators using the user management tools
offered by Windows Servers
120 1/1553-AOM 901 015/3 Uen G

• The user can change his/her password by logging in into Windows and
using the facilities offered by Windows to change user password. This is
possible only if the user is defined within the Active Directory domain.
1. Login to Windows with your domain userid.
2. Press CTRL, ALT, DELETE keys.
3. On the window that will appear click the "Change Password".
• From a ServiceOn Microwave server already configured to work with
Active Directory server, the user can open a terminal session and use
the kpasswd command.
1. Login on Linux with your domain userid.
2. Open a terminal session.
3. On the window the will appear type “kpasswd <User Name> [Return]”.
8.3 ServiceOn Microwave Server Configuration

The following configuration has been tested on SuSe Linux 9 Enterprise
systems (SLES).
The setup of Linux server is limited to the DSP host, CSP hosts does not require
any additional configuration.
8.3.1 Prerequisites
• Kerberos packages must be installed.

• Openldap packages must be installed.
• Remote Active Directory server must be reachable (ping).
• Remote Active Directory server must be known by DNS
• Linux host must be known by DNS.
• The Linux host can be in the same domain of Active Directory server,
but this is not mandatory. The important thing is that DNS is setup
properly.
• Linux host local time must be aligned with the one of remote Active
Directory server. In order to setup automatic alignment, the NTP client
on Linux host can be enabled to work connected to remote AD server.
This can be configured by YaST->Network Services->NTP Client. In the
NTP server field fill in the IP address of the domain controller (which is
by default a NTP server).
• In order to support additional NTP servers as backup, additional NTP
sources can be set using the "Complex Configuration" setup:
In the “Complex NTP Client Configuration” window, click the “Add” button and
then select the “Server” item and click “Next”.
In the “NTP Server” field fill in the IP address of another NTP server and click
“OK”.
In the “Complex NTP Client Configuration” click the “Finish” button.
• The configuration described below leads to a Linux host configured to
use Kerberos and LDAP exclusively with the defined Active Directory
1/1553-AOM 901 015/3 Uen G 121

server. More complex configurations can be managed manually by

system administrators.
• To manage failures of Active Directory servers, more DNS servers must
be configured by adding a "nameserver" line to the file /etc/resolv.conf
for each additional backup DNS server. In order to speedup DNS
operation in case of failures, the following line can be added at the end
of the /etc/resolv.conf file:
options timeout:1
Note Standard SLES 9 installation already includes all required software
8.3.2 Configuration of Kerberos engine

The Kerberos engine is used by ServiceOn Microwave to authenticate remote
Active Directory users. In order to configure it:
• Login a root.
• Copy the /opt/mv36/core/data/data/init/krb5.tmpt template to
/etc/krb5.conf file and chmod to 644 the file.
• Edit the /etc/krb5.conf file:
Replace HOSTNAME with the name (full domain name) of the domain
controller.
Replace the name of the domain SOMTEST.LOC with the Windows domain
used for ServiceOn Microwave Active Directory users.
8.3.2.1 Example of krb5.conf file

[libdefaults]
default_realm = SOMTEST.LOC
clockskew = 300
[realms]
SOMTEST.LOC = {
kdc = gexs15.it.marconicomms.com
admin_server = gexs15.it.marconicomms.com
kpasswd_server = gexs15.it.marconicomms.com
}
[domain_realm]
.somtest.loc = SOMTEST.LOC
[logging]
kdc = FILE:/var/log/krb5/krb5kdc.log
admin_server = FILE:/var/log/krb5/kadmind.log
default = SYSLOG:NOTICE:DAEMON
[appdefaults]
pam = {
ticket_lifetime = 1d
renew_lifetime = 1d
forwardable = true
proxiable = false
retain_after_close = false
minimum_uid = 0
try_first_pass = true
}
8.3.2.2 Configuration of additional backup Active Directory Server
The line “kdc =” in section realms can contain more hostnames (fully qualified,
separated by space), in order to setup backup Active Directory servers and to
manage properly failures versus a particular server. When more servers are
configured, the Linux client tries to connect to each one starting from the first
122 1/1553-AOM 901 015/3 Uen G

one and passing to the next after a timeout configured by the kdc_timeout
setting expires. The parameter should be configured in section libdefaults and
the default value is 3 seconds. For example if the backup active directory server
is “gexs13.it.marconicomms.com” and the timeout limit is set to 1 second, this is
the resulting krb5.conf file:
[libdefaults]
default_realm = SOMTEST.LOC
clockskew = 300
kdc_timeout = 1
[realms]
SOMTEST.LOC = {
kdc = gexs15.it.marconicomms.com gexs13.it.marconicomms.com
admin_server = gexs15.it.marconicomms.com
kpasswd_server = gexs15.it.marconicomms.com
}
[domain_realm]
.somtest.loc = SOMTEST.LOC
[logging]
kdc = FILE:/var/log/krb5/krb5kdc.log
admin_server = FILE:/var/log/krb5/kadmind.log
default = SYSLOG:NOTICE:DAEMON
[appdefaults]
pam = {
ticket_lifetime = 1d
renew_lifetime = 1d
forwardable = true
proxiable = false
retain_after_close = false
minimum_uid = 0
try_first_pass = true
}
See krb5.conf(5) man page to learn more.
8.3.3 Configuration of the LDAP client

LDAP is used to retrieve the ServiceOn Microwave profile for users defined
remotely in then Active Directory domain.
• Copy the /opt/mv36/core/data/data/init/ldap.tmpt template to
/etc/ldap.conf
• Edit the /etc/ldap.conf
Replace the HOSTNAME with the name (full domain name) of the domain
controller.
Replace SOMTEST and LOC in BASE line to reflect the Windows domain used
for ServiceOn Microwave users.
• Copy the /etc/ldap.conf to /etc/openldap/ and chmod to 644 the file (the
2 files must be always kept aligned).
8.3.3.1 Example of ldap.conf file

BASE dc=SOMTEST, dc=LOC
URI ldap://gexs15.it.marconicomms.com
HOST gexs15.it.marconicomms.com
8.3.3.2 Configuration of additional backup Active Directory Server
As already shown in Kerberos configuration section, it's possible to configure

additional LDAP servers to provide continuity of service in case of LDAP servers
failures. The URI and HOST lines can contain a space separated list of host to
1/1553-AOM 901 015/3 Uen G 123

be contacted as LDAP servers. Also in this case the TIMELIMIT variable can be
used to setup the timeout to use when trying to connect. In this case to setup a
LDAP backup server on gexs13.it.marconicomms.com with a timeout of 1
second, the ldap.conf must be setup in this way:
BASE dc=SOMTEST, dc=LOC

URI ldap://gexs15.it.marconicomms.com ldap://gexs13.it.marconicomms.com
HOST gexs15.it.marconicomms.com gexs13.it.marconicomms.com
TIMELIMIT = 1
See ldap.conf(5) man page to learn more.
8.4 Configuration of Active Directory in Service

In order to enable Active Directory users in ServiceOn Microwave, the following
configuration steps must be performed by nmcman user on each DSP host that
is enabled to work with Active Directory services:
• Edit the /opt/mv36/core/data/data/ini/som_AD.cfg file and change the
default settings if required. In particular open the file with and editor and
replace the following parameters according your configuration:
use_AD must be set to the string "true" in order to enable the use of active
directory.
somdomain is the domain used for SOM AD users, expressed in LDAP
notation. If your domain suffix is MLM.ZONE.DF do the following:
Replace:
dc=SOMTEST with dc=MLM
dc=LOC with dc=ZONE
Add:
dc=DF
So instead the line “dc=SOMTEST, dc=LOC” you will have a line similar to this
one “dc=MLM, dc=ZONE, dc=FD”.
somldapuser is the functional user configured in remote LDAP server (the
domain controller) that is used by SOM to query remote AD server (the domain
controller).
somgroup specifies the AD organizational Unit where all SOM users and
groups are defined. (Defaults to SOM).
ad_passwordfile is the name of the file where the somldapuser's password is
stored (see below).
Specify the somldapuser's password with the following command:
login as root
echo -n "password" >
/opt/mv36/core/data/data/ini/ad_pfile
chmod 600 /opt/mv36/core/data/data/ini/ad_pfile
separator parameter specifies the character to be used as separator to specify

alternate somusers query paths (see below). Defaults to TAB (\t) but can be
124 1/1553-AOM 901 015/3 Uen G

customized with other characters that are not used in Active Directory Domains
within organization unit names.
somusers parameter specifies the set of Active Directory organizational units to
be queried for ServiceOn Microwave users. The field is a list of zero or more
LDAP queries that can be used to restrict search of ServiceOn Microwave users
in Active Directory domains. The syntax for each LDAP query is as usual, ie a
comma separated list of ou=ORGNAME entries that are processed in order to
locate specific organization and sub-organizations within Active Directory
directory.More queries can be added (performing a sort of "OR" search within
Active Directory domain) by separating.This allows different actions such as:
Query the whole Active Directory domain (default, if the field is left
empty).
Restrict the search to a given organization unit.
Example:
ou=NetworkManagement
can be used to specify a toplevel organization unit
ou=Italy,ou=NetworkManagement
can be used to specify a sub-organization unit
Search in different organization units.
Example:
ou=NetworkManagement ou=ElementManagement
ou=Italy,ou=NMS
Note here the white space is a TAB (\t) used as separator to
specified alternate organization and sub organizations to search
within.
Note When editing the som_AD.cfg file, it's very important to use the proper case
of characters and to avoid white space within fields (if not required).
The proper configuration of these files can be verified using the ad_rls.sh
command (8.5.5).
8.5 Utility Scripts

Here follows a list of useful scripts to be used to manage Active Directory users
with SOM.
8.5.1 Prerequisites
• All commands must be executed by root user.

• The SOM environment must be loaded with a source /etc/mv36.cshrc
command.
• Linux client must be configured (8.3).
8.5.2 Script ad_deluser.sh

Utility to remove an Active Directory user from local SOM
The script performs the following actions:
1/1553-AOM 901 015/3 Uen G 125

• Remove Unix user (unless –dbonly is set)

• Remove user from database
Usage:
ad_deluser.sh <user> [-dbonly]
The optional '-dbonly' argument restricts removal of user from database.
Exit codes:
0 on success
1 on error
8.5.3 Script ad_getusergroup.sh

Returns the group for user specified as first argument,
Usage:
ad_getusergroup.sh <user> [exitcodesmapping]
Exit codes:
0 on success unless exitcodesmapping specified
1 on generic error
2 if user not found
exidcodesmapping are optional arguments of type

UserProfile=exitcode
This can be used to specify alternate exit codes depending on the se profile.
This is useful when calling this script from within executables
Example:
ReadOnly=5 ReadWrite=6 can be used to return a 5 or a 6 if the user
belongs to ReadOnly or ReadWrite.
Note that exit codes 0,1,2 are reserved and cannot be used (mapping will be
ignored)
8.5.4 Script ad_ls.sh

Utility to list Active Directory users configured to work on local SOM. No
additional arguments are required.
Output is a list of type:

username groupid groupname
Example:
supernmc 11 (ReadOnly)
INVALID as group if is returned if group cannot be computed consistently.
126 1/1553-AOM 901 015/3 Uen G

Exit codes:
0 on success
1 on error
8.5.5 Script ad_rls.sh

Returns the list of SOM users / groups / computesr configured on remote Active
Directory Server
Usage:
ad_rls [person|group|computer]
Optional arguments person, group or computer restrict the output to list of
people, to a list of groupe or to a list of computers.
Note: computers are not used by SOM, but computers defined within the
configured organization unit (see som_AD.cfg file) are listed by ad_rls script.
Called without arguments, returns the list of all persons, groups and
computers.
Output is a list of type:

person: username (comma separated list of groups of
which is member)
group: groupname (comma separated list of users
memberos of this group)
computer: computername
Exit codes:
0 on success
1 on error
8.5.6 Script ad_setusergroup.sh

Utility to prepare a AD user to work with local SOM:
• Adds Unix user if required
• Regenerates the user home dir if required
• Adds or refresh the user/group information in SOM database
Usage:
ad_setusergroup.sh <user> [<group>]
Exit codes:
0 on success
1 on error
If the group is not specified, it's set to its Active Directory.
1/1553-AOM 901 015/3 Uen G 127

8.5.7 Script ad_sync.sh

Utility to synchronize Active Directory users configured to work on local
ServiceOn Microwave with users stored in Active Directory server.
If launched with -n argument, shows only actions to be performed but does
nothing.
If launched with -f argument, removes all Active Directory users from data base.
Usage:
ad_sync.sh [-f] [-n]
Exit codes:
0 on success
1 on error
Limitation on current release:

Current version performs only presence synchronization (but this is the most
useful operation, the real purpose of the script): if the user is not present on
remote AD server, it's removed from local server.
This can be used to perform periodic housekeeping of local configured Unix
users vs. the ones actually configured on remote AD server.
128 1/1553-AOM 901 015/3 Uen G

8BServiceOn Microwave Standby Installation and Configuration
9 ServiceOn Microwave Standby Installation

and Configuration
ServiceOn Microwave Standby is a geographical redundancy solution to recover

a site.
This paper is not intended to explain ServiceOn Microwave Core but how to
install and configure this backup server solution. Target of this paper is to allow
a network/system administrator to install and maintain the product.
Backup server otherwise called as geographical redundancy or cold stand-by is
an Active/Stand-by protection.
Basics scenarios (Figure 9-1) are defined having two sites involved on the
solution:
• One site defined as active (or primary) located in the main place;
• A second site defined as stand-by used as protection in case of
unrecoverable disaster of first.
Figure 9-1 Basic Scenario
The synchronizations are executed periodically using `rsync` software; `rsync` is

an open source utility that provides fast incremental file transfer. Activity is
configurable and automatically handled by the `cron` mechanism.
The eventual recovery on the stand-by system due to a failure of the active (or
primary) system is to be done manually; no automatic detection of the failure is
provided.
More complex scenarios can foresee more than one Stand-By server.
In the product is also provided a facility to switch ServiceOn Microwave Core
CSP after the disaster recovery on the standby servers.
9.1 Prerequisites
The system to correctly work needs some extra packages to be installed on the
target servers (primary and standby). The software automatically checks the
1/1553-AOM 901 015/3 Uen G 129

dependences and then asks to install the missing packages. The packages
required by ServiceOn Microwave Standby are:
• Perl 5.8.3
• Rsync 2.6.2
Primary and Stand-By server must to be present in /etc/hosts or known by DNS:
• DSP see Figure 9-2.
Figure 9-2 Network Naming Capability (DSP)
• CSP see Figure 9-3
Figure 9-3 Network Naming Capability (CSP)
• Terminal PC see Figure 9-4
Figure 9-4 Network Naming Capability (Terminal PC)
130 1/1553-AOM 901 015/3 Uen G

Between Primary and Stand-By server it's mandatory to maintain the systems in
synchronism using the NTP service. The NTP Client can be set-up using the
YaST control center (Figure 9-5), in this case you can use a internal system or a
public NTP server to synchronize your servers.
Figure 9-5 Setting NTP Client
ServiceOn Microwave Database Backups (on the Primary server) must be

performed using the `cron` mechanism. To do that on the target systems
(primary and standby) you have to edit the `mv36Backup.ini` file in this way:
• Login as nmcman
• source /etc/mv36.cshrc
• vi $NCS/data/ini/mv36Backup.ini
#
# Automatic Backup operation enable (OFF=0, ON=1)
#
mv36BackupEnable=1
# First Automatic Backup time [hh.mm] (0.00 .. 7.59); (null) to disable
#
mv36BackupTime-1=0.00
#
# Second Automatic Backup time [hh.mm] (8.00 .. 15.59); (null) to
disable
#
mv36BackupTime-2=null
#
# Third Automatic Backup time [hh.mm] (16.00 .. 23.59); (null) to disable
#
mv36BackupTime-3=null
1/1553-AOM 901 015/3 Uen G 131

# Automatic Backup period [day] (1 .. 30)

#
mv36BackupPeriod=1
#
# Local repository
# The local directory in which ASCII CPIO backup files are stored.
#
Location=/opt/mv36/core/data/../../hist/dbBackup
• Logout as nmcman
9.2 Standby Installation

NOTICE The Standby software must be loaded and installed on the target servers,
primary, standby and on all CSP nodes.
9.2.1 Load the software

At this stage you have to add the Software Source Media containing the
ServiceOn Microwave Standby software. To do that login as root and before
starting the YaST control center, put the DVD (LZY 214 3636/1 R2A) with the
right applications on the relative box.
From YaST select Software, Change Source of Installation and finally add a
DVD resource.
Figure 9-6 Software Source Media

From the KDE desktop starts YaST and after putting the root password selects
`Package Groups`, choose the `ServiceOn Microwave Disaster` and mark the
`ServiceOn Microwave Standby` package.
132 1/1553-AOM 901 015/3 Uen G

Figure 9-7 Install the Software
remember that at this stage the ServiceOn Microwave Standby DVD must be
insert on the DVD ROM drive.

Login as root and put the ServiceOn Microwave CD on the DVD ROM drive.
Move on the repository where the RPM packages are located (typically
command:
• rpm –i ServiceOn-Microwave-Standby-01.00.06-1.i586.rpm
9.3 ServiceOn Microwave Standby Configuration
Figure 9-8 Configuration Example
1/1553-AOM 901 015/3 Uen G 133

9.3.1 Primary configuration
• Login as root
• Configuring the system (Figure 9-8):
cd /opt/DUAL/bin
./DUAL.install.sh server
DUAL installation/switch procedure

==================================
no crontab for root
no crontab for root
Configure the DUAL Client alignment:

------------------------------------------------
Hourly 00
Every_30_minutes 30
Every_15_minutes 15
Every_10_minutes 10
Daily HH:MM
Insert the synchronization period:
10
Define the Environment:

-----------------------
gexs84 is the server
Enter the name of the DUAL Client:
gexs85
gexs85 is the client
Insert the Mail Address to send the logs [default NO Mail]:
<RETURN>
• Start the system:
/etc/init.d/DUAL.server.sh start
2006/12/15 18:34 gexs84 DUAL.server.pl 17746 N Start DUAL Server
ERICSSON-Marconi: Geographical Redundancy solution

+------+ _____________
| DUAL | _/_|[][][][][] | - -
+------+ ( By GMR/IP | - -
_____||________=--OO-------OO--=_________
MV36_ingres.01 MV36 Ingres Checkpoint directory

MV36_ingres.02 MV36 Ingres Data directory
MV36_ingres.03 MV36 Ingres Dump directory
MV36_ingres.04 MV36 Ingres Journal directory
MV36_ingres.05 MV36 Ingres Work directory
MV36_ingres.06 MV36 Ingres Transaction Log
MV36_history MV36 History
MV36_software MV36 Software
MV36_users MV36 Users
MV36_spool MV36 Spool
2006/12/15 18:34 gexs84 DUAL.server.pl 17746 N DUAL Server
started - pid 17755
• Verify the system status
/etc/init.d/DUAL.server.sh status
ERICSSON-Marconi: Geographical Redundancy solution

+------+ _____________
134 1/1553-AOM 901 015/3 Uen G

| DUAL | _/_|[][][][][] | - -
+------+ ( By GMR/IP | - -
_____||________=--OO-------OO--=_________
MV36_ingres.01 MV36 Ingres Checkpoint directory

MV36_ingres.02 MV36 Ingres Data directory
MV36_ingres.03 MV36 Ingres Dump directory
MV36_ingres.04 MV36 Ingres Journal directory
MV36_ingres.05 MV36 Ingres Work directory
MV36_ingres.06 MV36 Ingres Transaction Log
MV36_history MV36 History
MV36_software MV36 Software
MV36_users MV36 Users
MV36_spool MV36 Spool
• If are present also these ingres DBs:
IMA_INVENTORY
mltnequipment_v001
cd /opt/DUAL/conf
Create the “ingresdb” file and append these rows:
IMA_INVENTORY
mltnequipment_v001
9.3.2 Standby configuration
• Login as root
• Stop ServiceOn Microwave and the Data Base:
/etc/init.d/soo_mv36 stop
• Configuring the system:
cd /opt/DUAL/bin
./DUAL.install.sh client
DUAL installation/switch procedure

==================================
no crontab for root
no crontab for root
Configure the DUAL Client alignment:

------------------------------------------------
Hourly 00
Every_30_minutes 30
Every_15_minutes 15
Every_10_minutes 10
Daily HH:MM
Insert the synchronization period:
10
Define the Environment:

-----------------------
Enter the name of the DUAL Server:
gexs84
gexs84 is the server
gexs85 is the client
Insert the Mail Address to send the logs [default NO Mail]:
<RETURN>
1/1553-AOM 901 015/3 Uen G 135

9.3.3 MINI-LINK E Adapter Stand by Configuration
If on DSP is configured a MINI-LINK E adapter running on a virtual machine

hosted on Linux server, it's needed to configure the system in order to backup
the MINI-LINK E Adapter data. To do that, follow the 2.3.4.1 paragraph (MINI-
LINK E Adapter Backup Data) of the System Administration and Configuration
Guide
9.4 Manual Synchronization

Its mandatory execute the manual synchronization after the first installation and
configuration to see if the Client is able to correctly acquire all the data from the
Server side.
To manual align the Stand-By server with the Primary server, on the Stand-By
server run as root:
• Login as root
csh
cd $NCS/script
./KILLALL.sh
• Start the manual synchronization:
cd /opt/DUAL/bin/
./DUAL.client.pl
9.5 Switch Primary server to Stand-by server

Two situations require a switch from the Primary server to the Stand-by server
(Figure 9-9):
• A planned switches due to a maintenance reason, so the switch is
completely under control of the System Administrator.
• A disaster recovery due to a definitive lost of the Primary server, in this
case the System Administrator can control only the Stand-by server from
the point of view of the switch.
The procedure of switch is manual in all systems involved in the management,
this means the stand-by server, the workstations servers and finally also the
terminals.
136 1/1553-AOM 901 015/3 Uen G

Figure 9-9 Switch Example
9.5.1 Primary switch
• Login as root
• Stop the Server:
/etc/init.d/DUAL.server.sh stop
csh
cd $NCS/script
./KILLALL.sh
• Reconfigure the Server as Client
cd /opt/DUAL/bin
./DUAL.install.sh client
9.5.2 Stand-by switch
• Login as root
• Start the Data Base:
/etc/init.d/ingresII start
1/1553-AOM 901 015/3 Uen G 137

9.5.2.1 Reconfigure ima_inventory data base

su nmcman
csh
cd /opt/DUAL/bin
./UpdateNodeName.csh
Exit
Exit
9.5.2.2 MINI-LINK E Adapter Switch (when MINI-LINK E Adapter is running on a
virtual machine hosted on Linux server of DSP)
In order to use the new MINI-LINK E Adapter server running on the Stand-by
DSP ( the new Primary one) it's needed perform the following two main steps:
1. Restore the MINI-LINK E Adapter data previously backed up following the

2.3.4.2 paragraph (MINI-LINK E Adapter Restore Data) of the System
Administration and Configuration Guide. Note that the files backed up
under /opt/mv36/core/nmc/hist/cdl folder on the primary DSP are
automatically copied under the same directory on the Stand-by DSP during
the manual or automatic synchronization.
2. Reconfigure the MINI LINK E Adapter Server ip address and MINI-LINK E
NE ip addresses as reported below:
• Login as root on Stand-by DSP (the new Primary)
• Stop ServiceOn Microwave (if started)
su nmcman
csh
cd $NCS/script
./updNeAddress.csh <IP Orig> <IP Dest>
Exit
Exit
• Start ServiceOn Microwave:
/etc/init.d/soo_mv36 start
138 1/1553-AOM 901 015/3 Uen G

9.5.2.3 Reconfigure the Client as Server
cd /opt/DUAL/bin
./DUAL.install server
• Start the Server:
/etc/init.d/DUAL.server.sh start
NOTICE The switch procedure doesn’t align the users at Linux level. Then the system
administrator has the responsibility to keep the systems aligned from the
user point of view.
NOTICE If HC NEs are configured on SoM server it is necessary to modify, on the

real equipment, the TRAP Destination related to the usr/pwd used to
discover the HC, specifying as TRAP Destination the IP Addr of the actual
DSP (gexs85) instead of the IP Addr of previous DSP (gexs84).
NOTICE If ETU NEs are configured on SoM server it is necessary to modify, on the
real equipment, the TRAP Destination related to the usr/pwd used to
discover the ETU, specifying as TRAP Destination the IP Addr of the actual
DSP (gexs85) instead of the IP Addr of previous DSP (gexs84)
9.5.3 CSPs Switch
• Login as root
• Stop the Data Base and ServiceOn Microwave:
• Switch the CSP server to the new Primary:
/opt/DUAL/bin/CSP_disaster_switch



MV36 detected

MV36 isn't running
Managing Names:
1/1553-AOM 901 015/3 Uen G 139

is a CSP
Old DSP Name = gexs84

New DSP Name = gexs85
Summarised Values:
------------------
Old Name: gexs84

New name: gexs85
Managing IP:
- 1 - Check IP Connectivity for new DSP
Check if gehp214 is reachable

----------------------------------
gehp214 OK
IP for gehp214: 172.16.174.230
----------------------------------
- 2 - Check IP for old DSP
Retrieve IP for gehp212

----------------------------------
gehp212 OK
IP for name: 172.16.174.228
----------------------------------
Reconfiguring NFS with these parameters:
- 1 - Modify NFS Client
OK
Reconfiguring Ingres with these parameters:
OK
OK
- 2 - Remove lock files
OK
- 3 – Restart NSD daemon
OK
• Start the Data Base and ServiceOn Microwave:
/etc/init.d/ingresII start
140 1/1553-AOM 901 015/3 Uen G

9.6 CSP Stand by Configuration and Switch Instruction
Described instructions are assuming the following scenario (Figure 9-10):
• 1 primary DSP (DSP1) + 3 primary CSP Servers (CSP1, CSP2, CSP3)

• 1 standby DSP (DSP2) + 1 standby CSP Server (CSP4)
Figure 9-10 Scenario Example
For the typical Standby solution instructions just follow the chapter 9.
At the end of overall system configuration, the following extra step is needed:
• Copy
/opt/mv36/core/nmc/instnmc/MV36v15.9.3/data/ini/mv36_sys.md.i
ni file from CSP3, CSP2 and CSP1 to three different temporary folders
on CSP4.
9.6.1 CSP1 failure

In this case CSP1 is subject to failure.
The following steps are foreseen:
• Stop SOM on DSP1;
• Disconnect CSP1 from the network;
• Connect CSP4 to the network, rename current mv36_sys.md.ini file in
/opt/mv36/core/nmc/instnmc/MV36v15.9.3/data/ini/ folder, and substitute
it with the one previously copied from CSP1, paying attention to not
modify file permission settings;
• Apply Standby solution procedure described in the par. 9.5.3 “CSPs
Switch” on CSP4, in order to point the Standby CSP to the DSP (CSP4
to DSP1);
1/1553-AOM 901 015/3 Uen G 141

• Modify /opt/mv36/core/nmc/instnmc/MV36v15.9.3/data/config/LANConfig
file on DSP1, substituting name and IP address of CSP1 with CSP4
ones;
• Start SOM on DSP1 and CSP4.
NOTICE The FTP server configuration parameters present in the mv36.ini file should
be modified considering the new running CSP4 after the switch.
9.6.2 CSP2 failure

The following steps need to be executed:
• Connect CSP4 to the network and substitute mv36_sys.md.ini
(previously copied from CSP2) in
/opt/mv36/core/nmc/instnmc/MV36v15.9.3/data/ini/ folder, paying
attention to not modify file permission settings;
• Apply Standby solution procedure described in the par. 9.5.3 “CSPs
Switch” on CSP4, in order to point the Standby CSP to the DSP (CSP4
to DSP1);
ones;
9.6.3 CSP3 failure

The following steps need to be executed:
• Connect CSP4 to the network and substitute mv36_sys.md.ini
(previously copied from CSP3) in
/opt/mv36/core/nmc/instnmc/MV36v15.9.3/data/ini/ folder, paying
attention to not modify file permission settings;
• Apply Standby solution procedure described in the par. 9.5.3 "CSPs
Switch" on CSP4, in order to point the Standby CSP to the DSP (CSP4
to DSP1);
ones;
142 1/1553-AOM 901 015/3 Uen G

9.6.4 MINI-LINK E Adapter server stand-by configuration and switch in case

of virtual machine running on CSP
If on CSP is configured a MINI-LINK E adapter running on a virtual machine
hosted on Linux server, it's needed to configure the system in order to backup
the MINI-LINK E Adapter data needed in case of CSP machine failure. To do
that, apply the 2.3.4.1 paragraph (MINI-LINK E Adapter Backup Data) of the
System Administration and Configuration Guide to the specific MINI-LINK E
Adapter Server icon.
Then to restore the previously backed-up MINI-LINK E adapter server data on
the new CSP (in the example, CSP4), it's needed perform the following two
main steps:
1. Restore the MINI-LINK E Adapter data previously backed up following the

2.3.4.2 paragraph (MINI-LINK E Adapter Restore Data) of the System
Administration and Configuration Guide.
2. Reconfigure the MINI LINK E Adapter Server ip address and MINI-LINK E
NE ip addresses as reported below:
• Login as root on DSP
• Stop ServiceOn Microwave ( if started)
su nmcman
csh
cd $NCS/script
Exit
Exit
be modified considering the new running CSPs after the switch.
1/1553-AOM 901 015/3 Uen G 143

9.6.5 MINI-LINK E Adapter server stand alone switch

In a general configuration it's possible to backup and restore, when needed, the
MINI-LINK E Adapter data from a server where the MINI-LINK E Adapter server
is running to another one performing the following main steps:
1. Backup the MINI-LINK E Adapter data. To do that, follow the 2.3.4.1

paragraph (MINI-LINK E Adapter Backup Data) of the System
Administration and Configuration Guide
2. Restore the MINI-LINK E Adapter data previously backed-up on the new
MINI-LINK E Adapter server following the 2.3.4.2 paragraph (MINI-LINK E
Adapter Restore Data) of the System Administration and Configuration
Guide.
3. If the MINI-LINK E Adapter server machine changes the ip address, it's
needed to reconfigure the MINI LINK E Adapter Server ip address and
MINI-LINK E NE ip addresses as reported below:
• Login as root on DSP
• Stop ServiceOn Microwave (if started)
su nmcman
csh
cd $NCS/script
Exit
Exit
9.7 Remove Standby Software

In order to remove the package, repeat these operations on all servers (remove
order is free):
• Disable the Daemons:
cd /opt/DUAL/bin
./DUAL.install remove
• Remove the package:

rpm -e ServiceOn-Microwave-Standby<version>
cd /opt
rm -rf DUAL
144 1/1553-AOM 901 015/3 Uen G

1/1553-AOM 901 015/3 Uen G 145

9BAppendix
10 Appendix
10.1 MINI-LINK E Physical Subnetwork: Configuration

guideline
10.1.1 Pre-requisites
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.
10.1.2 Terminal Server

A terminal server connects a MINI-LINK E sub-network to a LAN.
Using a terminal server, MINI-LINK E Adapter Server can connect to a MINI
LINK E sub-network using an IP address and a port number.
A terminal server is only needed if more than one sub-network is present.
How many terminal servers that are needed depends on the design of the data
communication network and how many ports the terminal servers have; each
port on a terminal server should not handle more than 200 identities (or 100
hops).
The maximum distance between the terminal server and the MINI-LINK network
is approximately 15 meters. If longer, it can be connected via a modem.
The terminal server must support:
• One or more RS-232 asynchronous serial interfaces
• Raw TCP connections
• Timeout on inactive connections
Configure the serial interfaces of the terminal server to the following settings:
• 1200 bps
• 8 data bits
• 1 stop bit
• no parity
• no flow control
Configure the following settings (or equivalent) if they are available in the
terminal server:
• Timeout on inactive connections after 1 minute
• Send a carriage return as a CR followed by a NULL
• Refuse to negotiate full duplex
• Allow all protocols to connect
146 1/1553-AOM 901 015/3 Uen G

9BAppendix
• Allow all protocols to establish outgoing connections

• Allow both incoming and outgoing traffic
• Disable char string for termination of the connection on the serial
interface
See Also:
Modem, Patton Model 2120 Single Port Terminal Server, Direct Cable
10.1.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
MINI-LINK E Adapter Server.
NOTICE The maximum distance between the terminal server and the MINI-LINK
network is approximately 15 meters.
10.1.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.
10.1.5 Modem Connection Setup

The PC is connected to the modem via the serial communication port, and the
modem is connected to the MINI-LINK equipment according Table 10-1, Table
10-2 and Table 10-3.
Figure 10-1 MINI-LINK Supervision via Modems
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:
1. 1200 bits/s
2. 8 data bits
3. 1 stop bit
4. no parity
5. no flow control
NOTICE The AT commands in two following tables are examples of how the modems
can be configured. Refer to the documentation that came with the modem
for details.
1/1553-AOM 901 015/3 Uen G 147

9BAppendix
10.1.5.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).
AT&W0 Save configuration.
NOTICE The saved configuration is reloaded at modem power-up, and needs

therefore only to be done once
10.1.5.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
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.
AT&W0 Save configuration.
NOTICE The saved configuration is reloaded at modem power-up, and needs

therefore only to be done once
10.1.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 14 on page 279). For
connection between PC and modem, use a standard RS 232C cable. Consult
the modem manual for detailed instructions.
10.1.6.1 Connection of Modem to MINI-LINK E Equipment; O&M port
148 1/1553-AOM 901 015/3 Uen G

9BAppendix
Connection of 25-pin RS 232C (or V.24) Connection to MINI-LINK E

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

connector radio
Pin Name Note Name Pin
2 TD, Transmit Data To modem RS 232C from radio P1:5 or P3:B02
3 RD, Received Data From modem RS 232C to radio P1:18 or P3:B04
7 SG, Signal Ground - 0V P2:6 or P3:C02
Table 10-2 Connection of Modem to MINI-LINK C and MkII Radio
10.1.6.3 Connection of Modem to MINI-LINK C and MkII SMM; BAY/USER
Connection of 25-pin Connection to MINI-LINK C and MkII SMM; BAY/USER

RS 232C (or V.24)
connector
Pin Name Note Name 1+0; Pin 1+1; Pin
2 TD, To RS 232C 9 5
Transmit modem from radio
Data
3 RD, From RS 232C 28 18
Received modem to radio
Data
7 SG, Signal - 0V 11 17
Ground
Table 10-3 Connection of Modem to MINI-LINK C and MkII SMM; BAY/USER
10.1.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.
Refer to:
Operator Guide - ServiceOn Microwave Element Manager
1/1553-AOM 901 015/3 Uen G 149

9BAppendix
Figure 10-2 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).
NOTICE The PC may need to be turned off before connecting the PC cable to a serial
port. If in doubt, turn off the PC while connecting the PC cable to the serial
port.
10.1.8 Terminal Emulation Settings

Using the following parameters, configure the terminal emulation software to
establish a connection to the TS.
a. Bite rate 9600
b. Parity None
c. Data bits 8
d. Stop bits 1
e. Flow control None
10.1.8.1 Example: Hyper Terminal Setting
• Start a HyperTerminal session. The HyperTerminal is easiest found on

the Start menu: Start > Programs > Accessories > HyperTerminal >
HyperTerminal.
• If the Connection Description dialog box does not open, click New
Connection on the File menu.
• In the Name box, type a name for the new connection, for example TS.
150 1/1553-AOM 901 015/3 Uen G

9BAppendix
Figure 10-3 Connection Description
• Click OK.
• In the Connect using list, select the serial port to use (typically COM1 or
COM2).
Figure 10-4 Connect
• Click OK.
• In the COM Properties dialog box, specify these Port settings:
a. Bite rate 9600
b. Parity None
c. Data bits 8
d. Stop bits 1
e. Flow control None
1/1553-AOM 901 015/3 Uen G 151

9BAppendix
Figure 10-5 Properties
• Click OK.
If no connection is established:
a. On the File menu, click Properties.
b. In TS Properties dialog box, click the Settings tab.
Figure 10-6 TS Properties
c. Select the Windows Keys option.

d. In the Emulation list, select VT100.
e. Click OK.
f. If no connection is established at this point try rebooting [power cycle]
the terminal server.
10.1.9 Configuring The TS For A MINI-LINK E Sub-network

The terminal server is set to factory default values. It is necessary to change
some values to fit the MINI-LINK E sub-network.
152 1/1553-AOM 901 015/3 Uen G

9BAppendix
To change default values:

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
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>
NOTICE 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 receive buffer length:
TS> configure eia232 interface rxbuflen 255
6. Set the local port number [0-65535]:
TS> configure eia232 rawtcp_telnet locport <port-number>
7. Disable char string for termination of the connection on the serial interface:
TS> configure eia232 rawtcp_telnet sestermchar 00
8. Disable DHCP:
TS> configure system dhcpena no
9. Set the IP address to the terminal server:
TS> configure system ipaddrcfg <IP-address>
10. Set the IP address to the terminal server:
TS> configure system subnetcfg <IP-address>
11. Save the image:
TS> configure activate
Reboot (power cycle) the terminal server. The new configuration is now active.
10.1.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.
10.1.11 Connecting The TS To The TCP/IP Network

Connect the TS to the TCP/IP network using the 10BASE-T LAN interface.
10.1.12 Configuring MINI-LINK E Adapter

Configure the subnetwork parameters by means of the autodiscovery for MINI-
LINK E facility in ServiceOn Microwave Element Manager.
Refer to:
Configuration and Administration guide
10.1.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
1/1553-AOM 901 015/3 Uen G 153

9BAppendix
shall be able to work. However, from now on it is more convenient to use a

Telnet session for configuration (if needed).
• On the Start menu, click Run.
• In the Open box, type Telnet IP_address, where IP_address is the IP
address of the TS.
• Click OK.
The PC and the TS must in this case be connected via a LAN connection.
10.1.14 Cisco Access Server Model 2509
Figure 10-7 Cisco Access Server Model 2509
10.1.14.1 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
subnetworks. (The octopus cable is not included, and must be ordered
separately).
Figure 10-8 8-pin RJ-45 Connector for Connection to MINI-LINK Equipment
The AUX port on the Cisco terminal server can be used for a ninth MINI-LINK
subnetwork.
Figure 10-9 pin RJ-45 Connector for a Ninth MINI-LINK Sub-network
10.1.14.2 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.
154 1/1553-AOM 901 015/3 Uen G

9BAppendix
The Cisco Access Server has to be installed and given a specific IP address
before the configuration can be done. Two passwords for the server must be
known. See the Cisco manuals for further instructions on these procedures.
Log on to the server to configure the Cisco Access 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 shall 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
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-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:
1/1553-AOM 901 015/3 Uen G 155

9BAppendix
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.
8. Configure the selected line:
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
cisco(config)# exit
cisco# write memory
13. Close the Telnet connection:
cisco# exit
10.1.14.3 Other Useful Commands
Here are a few more useful commands for the Cisco Access Server. They are
all used in the Telnet session window.
? It gets all available commands.
156 1/1553-AOM 901 015/3 Uen G

9BAppendix
Show It shows the entered settings.
Running-config It shows the entered settings.
reload It reboots the Cisco Access Server.
show line 5 It checks the configuration for line 5.
Refer to:
Cisco Manuals
ServiceOn Microwave Client applications installation on Microsoft Terminal Server Machine
Below is reported the installation instructions to install SOM client and all the needed SW on Microsoft
Terminal Server machine.
Preset: Windows 2003 SP1 installed. Microsoft Terminal Server installed and configured
From the SOM DVD copy the "Windows Package" folder on your Terminal Server Machine (under C:, for
example)
10.2 The Server 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.
Following list example shows how the parameters are structured in each record.
ID -> Type -> Sub-net ID -> Site ID -> Hop Side ID -> Hop
ID -> Far Hop Side ID -> Traffic Rate -> Description
The different parameters in example are separated by a tabulation character (-

>). The parameters are defined in the following Table
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
1/1553-AOM 901 015/3 Uen G 157

9BAppendix
Parameter Description
Traffic Rate Max 10 char
Description Max 255 char
Table 4 Parameters in the MINI-LINK E Adapter Server Network List File
See Also:
Terminal Server
10.3 Change nmcman user password
• Define password for “nmcman” functional user (DSP & CSPs)

Login as root
passwd nmcman [Return]
Changing password for nmcman.

New password: <PASSWORD>
Re-enter new password: <PASSWORD>
Password changed
Where <PASSWORD> is the password chosen for the nmcman user. In

case of distributed configuration the “nmcman” user password must be
the same for all the ServiceOn Microwave servers.
• Change the Ingres NET password (DSP only)
1. Login as ingres
2. netutil [Return]
158 1/1553-AOM 901 015/3 Uen G

9BAppendix
Figure 10-11 Netutil
3. Press <TAB>
4. Press <F1>
5. Write “Edit” [Return]
Figure 10-12 Netutil Change password
6. Write the <PASWORD> for nmcman user
7. Confirm the <PASWORD> for nmcman user
1/1553-AOM 901 015/3 Uen G 159

9BAppendix
8. Press <F1>
9. Write “Save” [Return]
10. Press <F1>
11. Write “End” [Return]
10.4 Free Open Source Products
The ServiceOn Microwave product includes the following free open source
products:
• IIOP.NET
Copyright © 2003-2004 ELCA; Licensed under the LGPL, Version 2.1
A copy of the source code can be downloaded from the site:
http://sourceforge.net/project/showfiles.php?group_id=80227&package_id=8247
8
• Castor
Copyright © 1999-2005
http://www.garshol.priv.no/download/xmltools/vendor/ExoLab.html, Intalio Inc.,
and Contributors; Licensed under the Apache License, Version 2.0.
A copy of the source code can be downloaded from the site.
http://www.castor.org/
• JfreeChart
Copyright © 2005-2007 by Object Refinery Limited and Contributors.
JFreeChart is written by David Gilbert with contributions from a diverse
community of developers.
A copy of the source code can be downloaded from the following site:
http://www.jfree.org/jfreechart/
• JZLIB
Copyright 1998-2004 JCraft, Inc. Licensed under the BSD style License.
http://www.jcraft.com/jzlib/index.html
• JAXB
This project is part of Project Metro and is in the Glassfish community at
java.net. It's released under theCommon Development and Distribution License
(CDDL) v 1.0.
160 1/1553-AOM 901 015/3 Uen G

9BAppendix
A copy of the source code can be downloaded from the site:

https://jaxb.dev.java.net/servlets/ProjectDocumentList?folderID=7256&expandF
older=7256&folderID=3952
• Ingres2006
Copyright © 2006 Ingres Corporation. Licensed under the LGPL, Version 2.
A copy of the code can be downloaded from the site:
http://www.ingres.com/products/ingres-2006.php
• Net-Snmp
Copyright 1989, 1991, 1992 by Carnegie Mellon University Derivative Work -
1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of
California
Copyright (c) 2001-2003, Networks Associates Technology, Inc.
Copyright (c) 2001-2003, Cambridge Broadband Ltd.

http://sourceforge.net/project/showfiles.php?group_id=12694&package_id=1157
1&release_id=431945
• MICO
Copyright 1996-2006 MICO Project
All libraries are covered by the GNU Library General Public License (LGPL),
Code generated by the IDL compiler is not copyrighted, everything else is
covered by the GNU General Public License (GPL)
A copy of the code can be downloaded from the following site:
http://www.mico.org/down.html
• HSQLDB
HSQLDB is written by Michael J. Cannon, Fred Toussi, Blaine Simpson; it is
licensed under the BSD License.
http://sourceforge.net/project/showfiles.php?group_id=23316
• Jasper Reports
Copyright © 2006 JasperSoft Corporation
http://www.jasperforge.org/index.php?option=com_docman&Itemid=248&mosm
sg=Not+authorized
• TrayIcon
TrayIcon is written by Jan Struyf 1999
http://jeans.studentenweb.org/java/trayicon/trayicon.html
1/1553-AOM 901 015/3 Uen G 161

9BAppendix
• XMLDB
Copyright (C) 2001-2006 Pete Ryland
http://xmldb.sourceforge.net/dls/#top
• Quartz Enterprise Job Scheduler

Copyright 2000-2005 - OpenSymphony
http://opensymphony.com/quartz/download.action
10.4.1 Projects copyrighted by The Apache Software Foundation
• Jakarta Commons HttpClient

Licensed under the terms of the Apache License, version 2.0
http://jakarta.apache.org/commons/httpclient/
• Logging package
A copy of the source code can be downloaded from the following site
http://jakarta.apache.org/commons/logging/
• Commons Collection
http://jakarta.apache.org/commons/collections/
• XML-RPC
http://ws.apache.org/xmlrpc/
• Jakarta Commons Lang

http://jakarta.apache.org/commons/lang/
• Log4j
http://logging.apache.org/log4j/docs/
162 1/1553-AOM 901 015/3 Uen G

9BAppendix
• Xerces Java Parser

http://xerces.apache.org/xerces-j/
• Apache FTP Server

http://incubator.apache.org/ftpserver/downloads.html
10.4.2 Projects copyrighted by Free Software Foundation
• JacORB
Licensed under the terms of the GNU LGPL, version 2
http://www.jacorb.org/download.html
• GNU Getopt in Java

Licensed under the terms of the GNU GPL, version 2
http://www.urbanophile.com/arenn/hacking/download.html
NOTICE The source code of the listed products can be downloaded on the web sites
indicated or requested to Ericsson AB.
See Also:
Free Open Source Products
1/1553-AOM 901 015/3 Uen G 163

1 - 1553-AOM 901 0153 SoM R8 SP1 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

1 - 1553-AOM 901 0153 SoM R8 SP1 PDF

Загружено:

Авторское право:

Доступные форматы

Installation Guide

ServiceOn Microwave Element Manager

© Ericsson AB 2007 – All Rights Reserved

No part may be reproduced, disclosed or used except as authorised by

The information in this work is the property of Ericsson Limited. Except as

Microsoft MicrosoftMS and MS-DOS are registered

Windows Windows is a trademark of the Microsoft

Adobe Reader Adobe and Reader are either registered

HP-UX HP-UX is a registered trademark of Hewlett-

Novell Novell, the Novell logo and Groupwise are

AdventNet AdventNet, The oval AdventNet logo, are

Ilog ILOG, the ILOG design, CPLEX and all other

NETAPHOR NETAPHOR®, Cyberons®, are trademarks of

InfoZoom InfoZoom is a trademark of the humanIT

All trademarks are properties of their respective owners

Code Date System Release

1/1553-AOM 901 015/3 Uen PE1 05-07 R8 Patch

1/1553-AOM 901 015/3 Uen E 07-07 R8 SP1

1/1553-AOM 901 015/3 Uen F 09-07 R8 SP1

1/1553-AOM 901 015/3 Uen G 09-07 R8 SP1

4 1/1553-AOM 901 015/3 Uen G

1/1553-AOM 901 015/3 Uen G 5

3.4.2 Upgrade Database on SOM Font-End server 33

6 1/1553-AOM 901 015/3 Uen G

5.5 TN LCT application installation 77

1/1553-AOM 901 015/3 Uen G 7

8.5.1 Prerequisites 125

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

10.1.6.2 Connection of Modem to MINI-LINK C and MkII Radio 149

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

1.3 System Requirement

For detailed configuration description of the recommended hardware platform

1.4 Required Media

10 1/1553-AOM 901 015/3 Uen G

• ServiceOn Microwave Frameworks

1/1553-AOM 901 015/3 Uen G 11

2 Installing SUSE Linux Enterprise Server 9

2.1 System start-up for installation

2.2 The boot screen

Figure 2-1 Boot screen

12 1/1553-AOM 901 015/3 Uen G

2.3 Language Selection

Figure 2-2 Language Seclection

2.4 Installation Settings

1/1553-AOM 901 015/3 Uen G 13

Figure 2-3 Installation Settings

14 1/1553-AOM 901 015/3 Uen G

Figure 2-4 Installation Mode

2.4.2 Keyboard Layout

2.4.4.1 Create Boot Partition

1/1553-AOM 901 015/3 Uen G 15

• From the `Expert` dialog, delete any partitions if present.

Figure 2-5 Expert Partitioner

Figure 2-6 Boot Partition

16 1/1553-AOM 901 015/3 Uen G

The primary partition must be created with these features:

2.4.4.2 Using LVM

Figure 2-7 Logical Volume Manager

The primary partition must be created with these features:

1/1553-AOM 901 015/3 Uen G 17

• Format: Do not format.

Figure 2-8 Logical Volume Manager

18 1/1553-AOM 901 015/3 Uen G