Installation Instructions

Installation Instructions
1 of 62
http://cpistore.internal.ericsson.com/alexserv?ID=243&DB=22939-2219...
INSTALLATION INSTR.
1531-CSH 109 085 Uen A
IPWorks 6.0
Copyright
Copyright Ericsson AB 2008. All rights reserved.
Disclaimer
No part of this document may be reproduced in any form without the written permission of the copyright owner.
The contents of this document are subject to revision without notice due to continued progress in methodology, design and
manufacturing.
Ericsson shall have no liability for any error or damage of any kind resulting from use of this document.
Trademark List
Copyright 1996-2003 Internet Software Consortium. Portions Copyright 1996-2001 Nominum, Inc. Copyright
1995-2003 by Internet Software Consortium. Copyright 1996, 1998-2000 The Regents of the University of California.
Copyright 2001-2003, Networks Associates Technology, Inc. Portions Copyright 2001-2003, Cambridge Broadband
Ltd. Copyright 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. Copyright
2003-2004, Sparta, Inc. Copyright 1995-1998 Eric Young ([email protected]). Other product and company names
mentioned herein may be the trademarks of their respective owners.
UNIX
A registered trademark of The Open Group.
Solaris
A registered trademark of Sun Microsystems, Inc.
SPARC
A registered trademark of SPARC International, Inc.
Java
Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc.
MySQL
A trademark of MySQL AB.
BIND
Copyright 2004 Internet Systems Consortium, Inc. ("ISC").
ISC DHCP Copyright 2004 by Internet Systems Consortium, Inc. ("ISC").
Netsnmp
Copyright 1989, 1991, 1992 by Carnegie Mellon University.
Open SSL
Copyright 1998-2004 The OpenSSL Project.
UnixODBC Copyright 1989, 1991 Free Software Foundation, Inc.
Tomcat
Copyright 1999, 2000 The Apache Software Foundation.
SUDO
Copyright 1994-1996,1998-2005 Todd C. Miller ([email protected]).
Contents
1
1.1
1.2
1.3
Introduction
Scope
Target Groups
Conventions
2
2.1
2.2
2.3
2.4
Installation Prerequisites
Users
System Requirements
Mirror the Local Disk
Build Environment
3
3.1
3.2
Installation Preparations
IPWorks CD Load Modules
Installation and Uninstallation
4
4.1
4.2
4.3
4.4
Installation Instructions for Different Configurations

Installation Procedure for Single Configuration
Installation Procedure for Medium Configuration
Installation Procedure for Legacy Configuration
Installation Procedure for Entry Configuration
12/8/2016 8:24 AM
2 of 62
5
5.1
5.2
5.3
5.4
5.5
Installation Verification
Verifying the DNS Service
Verifying the ENUM Service
Verifying the DHCPv4 Service
Verifying the Web Application
Verifying Sudo
6
6.1
6.2
6.3
6.4
6.5
Appendix
Displaying IPWorks Component Version Information
Launching the IPWorks Control Panel
Launching the IPWorks Command Line Interface
Launching the Web User Interface
Starting and Stopping the IPWorks Components
Reference List
12/8/2016 8:24 AM
3 of 62
1 Introduction
This document provides the installation instructions for IPWorks 6.0 on Solaris
systems.
1.1 Scope
This is the installation guide for IPWorks 6.0.
Additional information for any configuration that can be done after the initial installation is available in System
Administration Guide, Reference [1], and Control Panel User Guide, Reference [2]. Instructions to harden the security of
IPWorks are in Solaris Security Hardening for IPWorks 6.0, Reference [3] and Security Hardening for IPWorks 6.0
Application Components, Reference [4].
1.2 Target Groups

This document is intended for installation personnel.
1.3 Conventions
Table 1 describes the typographical conventions used in this document.
Table 1
Typographical Conventions
Convention
Description
Example
User Input
A command that must be entered in a Command Line

Interface (CLI) exactly as written.
cd home
Command Variables
Command variables, the values of which must be supplied <home_directory>

by the user.
GUI Objects
GUI objects, such as menus, fields, and buttons.
On the File menu, click Exit .
Key Combinations
Key combinations.
Press Ctrl+X to delete the selected

value. (1)
Output Information
Text displayed by the system.
System awaiting input
System Elements
Command and parameter names, program names, path

names, Uniform Resource Locators (URLs), and directory
names.
The files are located in

/usr/home/bin.
Omission Character
Ellipsis is used to show an omission in a list or a sequence. &mldr;
(1) The plus (+) sign indicates that the user must press the keys simultaneously.
Table 2 specifies the prompt expressions for different programs.
Table 2
Program Prompt Expressions
Program
Prompt
shell
ipwcli
IPWorks>
12/8/2016 8:24 AM
4 of 62
mysql
mysql>
2 Installation Prerequisites
This section states the prerequisites for installing IPWorks 6.0. Before installing components on any host system, decide if
the network topology, memory resources, and processor speed of the host are suitable. Base this decision on the functional
and system requirements of each component the user intends to install.
2.1 Users
The person installing IPWorks 6.0 must have knowledge of the following:
Sun Solaris and Sun Cluster installation and configuration
Intermediate UNIX skills for the installation process and root privileges
Concepts, terminologies, and abbreviations of telecommunication, such as TCP/IP, packet data networks, Domain
Name System (DNS), Dynamic Host Configuration Protocol (DHCP), and Electronic Numbering (ENUM)
2.2 System Requirements

Solaris 10 is the required operating system. The minimum software group for Solaris 10 installation is the entire distribution
and OEM support (64-bit).
Table 3 specifies the requirements of each component when the IPWorks components are installed on separate server
machines.
Table 3
Minimum System Requirements
Component Name
Minimum System Requirements
DNS Server
Sun 500-MHz UltraSPARC processor running Solaris 10, 256 MB RAM

and 50 MB disk space
DHCPv4 Server

DHCPv6 Server

ASDNS Monitor

and 2 MB disk space
ERH SS7 Manager

and 2 MB disk space with SS7 stack
DNS-ALG

Storage Server, MySQL Database, Tomcat Servlet

Engine and Web Application

ENUM Server
Sun Netra 240, 2*1.5 GHz UltraSPARC IIIi processors running Solaris
10, 8 GB RAM
Data Nodes
10, 8 GB RAM
12/8/2016 8:24 AM
5 of 62
SQL Node
10, 8 GB RAM
Management Node
10, 8 GB RAM
Note:
To increase the application availability, it is recommended that each Sun Netra 240 have two local disks
to create a mirror.
If more than one component is installed on the same system, requirements are greater and thus a
system with higher performance capabilities is needed.
2.3 Mirror the Local Disk

This section uses an example to describe how to mirror the local disk for single machine.
Table 4 is a partition example for single machine (Sun Netra 240).
Table 4
Partition Example for Single Machine
Slice
Mount Point
Size (MB)
123575
swap
16384
overlap
3
4
5
6
7
unassigned
32
Only the partition / and swap will be mirrored.

Perform all steps mentioned below with root user permissions. Avoid any steps other than those suggested in this
document. Any errors resulting from not following the recommended steps are beyond the scope of the document.
1. Ensure that the following prerequisites are satisfied:
Solaris 10 is installed.
RAID setup has not been done on the machine.
The machine has at least two hard disks.
The IPWorks installation disk is inserted into the CD drive and mounted.
The partition table is set up as described in Table 4.
2. Use the df command to identify the system disk containing the / mount point.
# df /
12/8/2016 8:24 AM
6 of 62
/ (/dev/dsk/c0t0d0s0 ): 1040744 blocks 367878 files

In this example, the system disk is c0t0d0.
3. Use the format command to identify a free disk.
# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@1c,600000/scsi@2/sd@0,0
1. c0t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
/pci@1c,600000/scsi@2/sd@1,0
Specify disk (enter its number):
Enter CTRL-D to cancel the format command. Do NOT enter a disk number as requested.
The user has already identified c0t0d0 as the system disk in this example, so c0t1d0 is the disk available for use as
the mirror disk.
4. Use the create_mirror_disk script to create the partitions on the mirror disk.
# cd /cdrom/cdrom0/solaris/utils
# ./create_mirror_disk -m <mirror-disk> -t <mirror-type>
Where , there are two types:
<mirror-disk> identifies the second disk to be used as the mirror disk.
<mirror-type> identifies the type of machine to be mirrored. The types are:
single : Single machine like Protocol Server or Storage Server without Sun Cluster.
medium : Storage Server with Sun Cluster.
For example, if the first disk is c0t0d0 and the second disk is c0t1d0, the machine is in single machine environment:
# ./create_mirror_disk -m c0t1d0 t single
---------------------Checking Prerequisites
---------------------Checking Mirror Disks...Not Present
Root Disk...Your boot disk is c0t0d0.
------------------------------------Making new partitions for mirror disk
------------------------------------fmthard: New volume table of contents now in place.
------------------------Creating new metadevices
------------------------d11: Concat/Stripe is setup
d10: Mirror is setup
d21: Concat/Stripe is setup
d20: Mirror is setup
----------------------Configuring new vfstab
----------------------Done
----NOTE
----Please run "init 0" and configure OBP
Run commands
12/8/2016 8:24 AM
7 of 62
ok?
ok?
ok?
ok?
nvalias bootdisk /pci@1c,600000/scsi@2/disk@0,0

nvalias mirrordisk /pci@1c,600000/scsi@2/disk@1,0
setenv boot-device bootdisk mirrordisk
Boot
5. Make a careful note of the commands listed at the end of the output from the create_mirror_disk script. These are
the commands the user needs to run in step 6 to restart the system.
6. Run init 0 from the system console and enter the commands reported by create_mirror_disk script. For example:
# init 0
ok? nvalias bootdisk /pci@1c,600000/scsi@2/disk@0,0
ok? nvalias mirrordisk /pci@1c,600000/scsi@2/disk@1,0
ok? setenv boot-device bootdisk mirrordisk
ok? boot
7. Use the attach_mirror_disk script to complete the disk mirroring:
# ./attach_mirror_disk t <mirror-type>
Where <mirror-type> identifies the type of machine to be mirrored, there are two types:
single : Single machine like Protocol Server or Storage Server without Sun Cluster.
medium : Storage Server with Sun Cluster.
For example, in single machine:
# ./attach_mirror_disk t single
-----------------------Finishing Disk Mirroring

-----------------------d20: submirror d22 is attached
d10: submirror d12 is attached
----------------------Disk Mirroring Finished
Once the attach_mirror_disk script has finished, the RAID 1 setup is complete and the background synchronization
of the first and second disks begins.
8. Use the metastat command to check that all the created mirrors are being synchronized.
# metastat -c
The system may take several hours to synchronize all the data to the newly created mirrors. The user can carry on
with the IPWorks installation procedures while the synchronization is in progress but the synchronization activity will
affect the performance of the system.
The user can repeat step 8 at any time to check if the synchronization is still in progress.
2.4 Build Environment

Table 5 shows the build environment for different configuration types and node types.
Table 5
Build Environment for Different Configuration Types
Configuration Type
Node Type
Solaris 10(1)
Local Disk Mirror(2) Sun Cluster(3)
Single Configuration
Storage Server
Protocol Server
12/8/2016 8:24 AM
8 of 62
Medium Configuration
Legacy Configuration
Entry Configuration
Storage Server
Protocol Server
Storage Server
Protocol Server
Storage Server
Protocol Server
(1) Refer to Solaris Installation Instructions, Reference [5].

(2) Refer to Section 2.3.
(3) Refer to Sun Cluster Installation Instructions, Reference [6].
3 Installation Preparations
This section describes the preparations that are required prior to the installation.
3.1 IPWorks CD Load Modules

IPWorks 6.0 delivery CD-ROM contains load modules for IPWorks installation. The CD layout has a separate directory for
each module under the directory /cdrom/cdrom0/solaris. The directory name of each load module is shown in Table 6.
The modules are installed with root privileges. It is not mandatory to install all the modules on every machine. Choose
optional modules per user requirements and network configurations.
Table 6 shows IPWorks 6.0 CD load modules and the dependency between the load modules. Mandatory load modules must
be installed on every IPWorks machine.
Table 6
IPWorks 6.0 CD Load Modules
Load Module Load Module Load

Attribute Prerequisites
Title
Name
Module
per Host
Directory
Name
IPWorks
Common Load
Module
IPWcommon
common
Mandatory None
Backup and
Restore
IPWbackup
backup
Mandatory IPWcommon
Java Runtime
Environment
IPWjre
jre
Mandatory IPWcommon
MySQL
IPWmysql
mysql
Common Line
Interface
IPWcli
cli
Mandatory
(1)
IPWcommon
Optional
IPWcommon,
IPWjre
12/8/2016 8:24 AM
9 of 62
Tomcat Server IPWtomcat
tomcat
Optional
IPWcommon,
IPWjre
Server
Manager
sm
Optional
IPWcommon,
IPWjre
Optional
IPWcommon,
IPWjre,
IPWmysql,
IPWcli
Optional
IPWcommon,
IPWjre,
IPWmysql,
IPWcli, IPWss
Optional
IPWcommon,
IPWjre,
IPWmysql,
IPWcli, IPWss,
IPWtomcat
Optional
IPWcommon,
IPWjre,
IPWsm
ASDNS Monitor IPWasdnsmon asdnsmon Optional
IPWcommon,
IPWjre,
IPWsm
DNS-ALG
Server
Optional
IPWcommon,
IPWjre,
IPWsm
Optional
IPWcommon,
IPWjre,
IPWsm
Optional
IPWcommon,
IPWjre,
IPWmysql,
IPWsm
Optional
IPWcommon,
IPWjre,
IPWmysql,
IPWsm
Optional
IPWcommon,
IPWjre,
IPWsm,
IPWdns, EAB
SS7 Stack
IPWsm
Storage Server IPWss
Statistics
Collection
Process
Web Interface
(2)
DNS Server
IPWcnoss
IPWwebui
IPWdns
IPWdnsalg
DHCPv4 Server IPWdhcpv4
ENUM Server
IPWenum
DHCPv6 Server IPWdhcpv6
ERH Server
IPWerh
ss
cnoss
webui
dns
dnsalg
dhcpv4
enum
dhcpv6
erh
12/8/2016 8:24 AM
10 of 62
SS7 Stack
(3)
Sun Cluster
Agent (5)
EAB SS7
Stack (4)
ss7
IPWscagents scagents
Optional
None
Optional
None
(1) IPWmysql (Innodb Node) is mandatory for the Storage Server, whereas IPWmysql (Mgmt Node), IPWmysql (Data
Node) and IPWmysql (SQL Node) are mandatory for the Protocol Server (Single, Medium and Entry).
(2) Web Interface is installed on the machine hosting the Storage Server if web access to IPWorks is required.
(3) For details on how to install and configure SS7 Stack, refer to SS7 Configuration for IPWorks 6.0, Reference [7].
(4) EAB SS7 Stack includes EABss7017, EABss7019, EABss7020, EABss7022, EABss7023, EABss7024, and EABss7026.
(5) Sun Cluster Agent is exclusively for Sun Cluster Environment.
3.2 Installation and Uninstallation

IPWorks 6.0 delivery CD-ROM contains the IPWorks Installation and Upgrade Tool. For more information on how to
use the IPWorks Installation and Upgrade Tool, refer to Installation and Upgrade Tool User Guide, Reference [8].
3.2.1
Starting the Tool
Use the following procedure to start the tool:

1. Insert the IPWorks 6.0 delivery CD-ROM into the drive.
2. Set the working directory to /cdrom/cdrom0/solaris/utils
3. Start the IPWorks Installation and Upgrade Tool:
# ./ipwsetup
starting ipwsetup...
ipwsetup TOOL INITIALIZING , PLEASE WAIT
3.2.2
Installing an IPWorks Release
To install the load modules,

1. Start the IPWorks Installation and Upgrade Tool as described in Section 3.2.1.
2. Select the INSTALLATION button on the Main Menu to start the IPWorks 6.0 Installation Wizard .
3. Select the load modules in IPWorks 6.0 Installation Wizard .
12/8/2016 8:24 AM
11 of 62
4. Select INSTALL button and press Enter key.

If the tool displays an error message indicating a dependency failure, go back to Step 3 and add the missing
prerequisite load modules to the selection.
3.2.3
Uninstalling an IPWorks Release
Use the following procedure to uninstall an IPWorks release:

1. If the user intends to uninstall the currently active IPWorks release, use the Control Panel to stop all running
IPWorks-related processes.
2. Stop the process of MySQL and Tomcat servlet engine.
For MySQL and Tomcat servlet engine in Sun Cluster, use the following command to stop them:
# scswitch -F -g ipworks_rg &
For MySQL and Tomcat servlet engine not in Sun Cluster:
a. Use the following command to stop the process of MySQL:
# /etc/init.d/ipworks.mysql stop
Ensure the process of MySQL is stopped using the following command:
# ps -ef | grep -v grep | grep mysql
b. Use the following command to stop the Tomcat servlet engine:
# /etc/init.d/ipworks.tomcat stop
Ensure the process of Tomcat is stopped using the following command:
# ps -ef | grep -v grep | grep org.apache.juli
12/8/2016 8:24 AM
12 of 62
3. Start the IPWorks Installation and Upgrade Tool as described in Section 3.2.1.
4. Select the UNINSTALLATION option on the Main Menu.
5. Select an IPWorks release in IPWorks 6.0 Uninstallation Wizard .
6. Select all the load modules to be uninstalled for the selected IPWorks release.
7. Select the UNINSTALL button and press the ENTER key to uninstall the selected load modules.
If the tool displays an error message indicating a dependency failure, go back to Step 6 and add the missing
dependent load modules to the selection (or delete the prerequisite load modules from the selection).
4 Installation Instructions for Different Configurations

This section contains the installation and configuration instructions for the following example networks:
Single configuration consists of one machine for both Storage Server and Protocol Server.
Medium configuration consists of four machines: two Storage Servers and two Protocol Servers.
Legacy configuration consists of three machines: one Storage Server and two Protocol Servers.
Entry configuration consists of three machines: one Storage Server and two Protocol Servers.
Note:
In this section, SS1 and SS2 refer to the Storage Server machines, whereas PS1 and PS2 refer to the Protocol
Server machines.
4.1 Installation Procedure for Single Configuration

This section provides the instructions for a single configuration. The Storage Server and Protocol Server are on the same
machine.
4.1.1
Hardware Prerequisites
The single machine must have the following system configuration:

Sun Netra 240
2 X 1.5 GHz UltraSPARC IIIi processors
8 GB RAM
2 X 146 GB Hard Disk
Interface Cards
1 Ethernet Card with 2 Gigabit Ethernet Ports (one for O&M and one for traffic)
ISR v2 SS7 interface card (if ERH functionality is required)
4.1.2
Setup Diagram
Figure 1 shows the IPWorks modules that can be installed on a single machine.
12/8/2016 8:24 AM
13 of 62
Figure 1
4.1.3
IPWorks Modules on a Single Machine
Installation Overview
Use the IPWorks Installation and Upgrade Tool to install the modules per user requirements, as shown in Table 7.
Table 7
Load Modules for Single Configuration
Load Module Name
Machine
IPWcommon
IPWbackup
IPWjre
IPWmysql (Innodb Node) is mandatory

IPWmysql (Mgmt Node), IPWmysql (Data Node) and
IPWmysql (SQL Node) are mandatory only if ENUM
functionality is required
IPWmysql
IPWcli
IPWtomcat
IPWsm
IPWss
IPWcnoss
12/8/2016 8:24 AM
14 of 62
IPWwebui
IPWdns
Only if DNS functionality is required
IPWasdnsmon
Only if ASDNS functionality is required
IPWdnsalg
Only if DNS-ALG functionality is required
IPWdhcpv4
Only if DHCPv4 functionality is required
IPWenum
Only if ENUM functionality is required
IPWdhcpv6
IPWerh
Only if ERH functionality is required
EAB SS7 Stack
IPWscagents
Table 8 shows the installation procedure for single configuration. The installation is customized by the user and thus
optional steps can be skipped.
Table 8
Installation Procedure for Single Configuration
Step
Action
Description
Installing Load Modules, Table 7 and Section 4.1.4.1
Mandatory
Configuring MySQL InnoDB Master, Section 4.1.4.2
Mandatory
Configuring Storage Server, Section 4.1.4.3
Mandatory
Configuring NDB Cluster Management Node, Section 4.1.4.4 Optional
Configuring NDB Data Node, Section 4.1.4.5
Optional
Configuring NDB SQL Node, Section 4.1.4.6
Optional
Configuring DNS Server, Section 4.1.4.7
Optional
Configuring ENUM Server, Section 4.1.4.8
Optional
Configuring DHCPv6 Server, Section 4.1.4.9
Optional
4.1.4
Machine Installation
This section provides the instructions to set up and configure the machine in the single configuration.
4.1.4.1
Installing Load Modules
12/8/2016 8:24 AM
15 of 62
1. Install the load modules shown in Table 7.

Refer to Section 3.2.2 for details.
2. Verify that the load modules have been installed correctly.
The following command displays the release numbers of the installed load modules:
Machine-1# ipwversion
4.1.4.2
Configuring MySQL InnoDB Master
This section provides the instructions to configure and start the MySQL InnoDB Master in the single configuration.
1. Start the MySQL InnoDB Master.
Machine-1# /etc/init.d/ipworks.mysql start-master-innodb
Starting IPWorks InnoDB Master....
081111 16:16:02 mysqld_safe Logging to '/etc/ipworks/mysql/innodbnode_data/innodbnode.err'.
081111 16:16:02 mysqld_safe Starting mysqld daemon with databases from /etc/ipworks/mysql
/innodbnode_data/
2. Grant all privileges to localhost and machine.
Machine-1# /usr/local/mysql/bin/mysql
mysql> grant all privileges on *.* to 'ipworks'@'localhost' identified by 'ipworks';
Query OK, 0 rows affected (0.00 sec)
mysql> grant all privileges on *.* to 'ipworks'@'<M1 O&M IP>' identified by 'ipworks';
where <M1 O&M IP> is the IP address of the O&M Ethernet interface card.
Note:
Master innodb IP address configured in Slave SQL Node is included in the table mysql.user in the master
innodb database. Otherwise all privileges are granted to this IP address.
3. Verify the privileges.
mysql> select user, host from mysql.user;
+---------+-----------------+
| user
| host
|
+---------+-----------------+
| ipworks | <M1 O&M IP>
|
| root
| <local host>
|
| root
| <hostname>
|
| ipworks | local host
|
| root
| local host
|
+---------+-----------------+
7 rows in set (0.00 sec)
4. Quit the session.
mysql> quit
4.1.4.3
Configuring Storage Server
This section provides the instructions to create the IPWorks databases, start the Storage Server and initialize the Storage
Server database on a single-machine installation.
1. Create the MySQL databases.
Machine-1# /opt/ipworks/IPWss/db/create_mysql_db
Creating Storage Server database ...
12/8/2016 8:24 AM
16 of 62
2. If the ENUM Server is installed, create the ENUM database.

Machine-1# /opt/ipworks/IPWss/db/create_enum_db
Creating NDB ENUM database ...
3. If the DHCPv6 Server is installed, create the DHCPv6 database.
Machine-1# /opt/ipworks/IPWdhcpv6/db/create_dhcpv6_db
Creating DHCPv6 database ...
4. Start the Storage Server.
Machine-1# /etc/init.d/ipworks.ss start
Starting IPWorks Storage Server ...
5. Use the IPWorks Control Panel to check that the Storage Server is running.
6. Initialize the MySQL database.
Machine-1# /opt/ipworks/IPWss/db/init_mysql_db
Storage Server Username: admin
Password: <password>
Password (again): <password>
The installed objects are displayed. The initialization is complete when the following output is displayed.
IPWorks> Login to server successful.

1 object(s) created. Exiting.
Working on 1 object(s).
1 object(s) were updated.
Exiting
Note:
<password> is the password of the admin user.
The Username and Password that this script prompts for are the same used to login to the CLI on
the Storage Server.
4.1.4.4
Configuring NDB Cluster Management Node
This section provides the instructions to configure and start the Management Node of the NDB Cluster on a single-machine
installation.
1. Start the IPWorks Control Panel.
Machine-1# ipwscp
2. Configure Management Node attributes.
Select MySQL Cluster Node > Managment Node > Configuration > Management Node Parameters .
Configure the following parameter:
HostName
<M1 O&M IP Address>
where <M1 O&M IP Address> is the IP address of the machine on which the Management Node is running, for
example, 127.0.0.1.
3. Configure the Data Node common parameters.
Select MySQL Cluster Node > Management Node > Configuration > Data Node Common Parameters .
Configure the following parameters:
Data Memory Size = see Table 9
12/8/2016 8:24 AM
17 of 62
Index Memory Size = see Table 9

No of Replicas = 1
No of Fragment Log Files = 128
Redo Buffer Size = 8
The configuration file used by the Management Node is /etc/ipworks/mysql/confs/ipworks_mgm_1.conf
Table 9
NDB Cluster Management Node Memory Requirements
Number of Records
Data Memory Required
Index Memory Required
1 Million
up to 3 GB
up to 600 MB
5 Million
up to 3.5 GB
up to 800 MB
8 Million
up to 4 GB
up to 1000MB
Note:
If ENUM and DHCP are installed on the same machine, the number of records in ENUM must not exceed 4
million. Otherwise, the performance of the system cannot be ensured.
4. Add one Data Node to the NDB Cluster.

This Data Node points to the IP address of the machine (M1) on which the Data Node is running.
Select MySQL Cluster Node > Management Node > Configuration > Add SQL/DATA Node .
NodeType = DATA
HostName = <M1 O&M IP Address>
where <M1 O&M IP Address> is the IP address of the host on which the DATA Node runs, for example, 127.0.0.1.
5. Add three SQL Nodes to the NDB Cluster in sequence.
NodeType = SQL
HostName = <M1 O&M IP Address>
where <M1 O&M IP Address> is the IP address of the host on which the NDB Cluster runs, for example, 127.0.0.1.
The first SQL Node points to the IP address of the NDB MySQL Server (M1) and is used for replication from innodb to
the DATA node.
The second SQL Node points to the IP address of the ENUM Server (M1) and is the entry for the ENUM Service to
access the cluster data.
The third SQL Node points to the IP address where the SQL Node is installed. This is the entry for the MySQL NDB
clients (for example, ndb_show_tables) to access the cluster data.
6. Start the NDB Cluster Management Node.
Select MySQL Cluster Node > Management Node > Start .
7. Exit the IPWorks Control Panel.
8. Check that the node has started.
Machine-1# /etc/init.d/ipworks.mysql show-ndb-status
Connected to Management Server at: localhost:1186

Cluster Configuration
---------------------
12/8/2016 8:24 AM
18 of 62
[ndbd(NDB)]
1 node(s)
id=2 (not connected, accepting connect from localhost)
[ndb_mgmd(MGM)] 1 node(s)
id=1 @localhost (mysql-5.1.23 ndb-6.2.15)
[mysqld(API)]
3 node(s)
4.1.4.5
Configuring NDB Data Node
This section provides the instructions to configure and start the Data Node of the NDB Cluster on a single-machine
installation.
Machine-1# ipwscp
2. Configure the Data Node parameters.
Select MySQL Cluster Node > Data Node > Configuration .
NDB Connect String
<M1 O&M IP Address>:1186
example, 127.0.0.1.
The configuration file used by the Data Node is /etc/ipworks/mysql/confs/ipworks_datanode_my.conf.
3. Depending on whether the Data Node is started for the first time, choose one of the following options.
If the Data Node is started for the first time, select MySQL Cluster Node > Data Node > Start Initial .
Note:
This operation is only performed for the first time setup. The operation erases all the NDB data
from the disk.
If the Data Node is not started for the first time, select MySQL Cluster Node > Data Node > Start .
5. Check that the Data Node has started.
The output in the following example shows that the Data Node is connected to the NDB Cluster. The Data Node is
ready only when starting is not displayed in the string against the id=2.
For example:
Connected to Management Server at: localhost:1186

--------------------[ndbd(NDB)]
1 node(s)
id=2 @127.0.0.1 (mysql-5.1.23 ndb-6.2.15, starting,
Nodegroup: 0, Master)
id=1 @localhost (mysql-5.1.23 ndb-6.2.15)
[mysqld(API)]
3 node(s)
id=3 (not connected, accepting connect from 127.0.0.1)
12/8/2016 8:24 AM
19 of 62

4.1.4.6
Configuring NDB SQL Node
This section provides the instructions to configure and start the SQL Node of the NDB Cluster on a single-machine
installation, and to verify the NDB data.
Machine-1# ipwscp
2. Configure the SQL Node parameters.
Select MySQL Cluster Node > SQL Node > Configuration .
Master-Host
<M1 O&M IP Address>
where <M1 O&M IP Address> is the IP address of the machine on which the MySQL InnoDB is running.
If the Master Host value is changed by using the Control Panel after the first correct configuration, the changes take
effect after one of the following:
login to the SQL Node and use the CHANGE MASTER TO MASTER_HOST='New MASTER HOST' statement to reset
the SQL Node Master Host. (recommended)
restart of the SQL Node after deleting the master.info file located in /etc/ipworks/mysql/sqlnode1_data/.
NDB Connect String <M1 O&M IP Address>:1186

example, 127.0.0.1.
ServerID
Port
datadir
3
3307
/etc/ipworks/mysql/sqlnode1_data
where ServerID specifies the server ID for SQL replication process. The value must be an integer greater than 1.
The configuration file used by the NDB SQL Node is /etc/ipworks/mysql/confs/sqlnode1.conf.
3. Go to the IPWorks Control Panel Main Screen and wait for the Data Node status to change to running .
4. Start the SQL Node.
Select MySQL Cluster Node > SQL Node > Start .
Note:
This node starts only when at least one NDB Data Node has successfully started.
6. Check that the SQL Node has started from the Management Server.
Connected to Management Server at: 127.0.0.1:1186

--------------------[ndbd(NDB)]
1 node(s)
id=2 @127.0.0.1 (mysql-5.1.23 ndb-6.2.15, Nodegroup: 0, Master)
id=1 @127.0.0.1 (mysql-5.1.23 ndb-6.2.15)
12/8/2016 8:24 AM
20 of 62
[mysqld(API)]
3 node(s)
id=3 @127.0.0.1 (mysql-5.1.23 ndb-6.2.15)
The above output indicates that an SQL daemon has started.
7. Check the status of the SQL Node connections with the NDB Cluster and Master InnoDB node.
Machine-1# /usr/local/mysql/bin/mysql -P 3307 h localhost -protocol=tcp
mysql> show processlist\G
mysql> show slave status\G
mysql> exit
For example:
Machine-1# /usr/local/mysql/bin/mysql -P 3307 h localhost -protocol=tcp
*********************** 1. row ***********************

Id: 1
User: system user
Host:
db:
Command: Daemon
Time: 1
State: Waiting for event from ndbcluster
Info: NULL
*********************** 2. row ***********************
Id: 2
User: system user
Host:
db: NULL
Command: Connect
Time: 164
State: Waiting for master to send event
Info: NULL
*********************** 1. row ***********************

Slave_IO_State: Waiting for master to send event
Master_Host: localhost
Master_User: ipworks
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: .000009
Read_Master_Log_Pos: 209211
Relay_Log_File: sqlnode.002278
Relay_Log_Pos: 242
Relay_Master_Log_File: .000009
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB: ipworks
Replicate_Ignore_DB:
Replicate_Do_Table:
ipworks.MAPDATA,ipworks.BULKUPDATE,
ipworks.INAPDATA,ipworks.ENUMDNRANGE,ipworks.RTGSCHEDENTRY,
ipworks.ENUMACL,ipworks.ENUMDNSCHED,ipworks.DESTNODE,
ipworks.MAPNODE,ipworks.ENUMZONE,ipworks.ENUMZVREL,
ipworks.CALLSERVER,ipworks.ENUMVIEW,ipworks.ROUTEBYTOD,
ipworks.AINLNPDATA,ipworks.ENUMSERVER,ipworks.COUNTRYCODE,
ipworks.AINTOLLFREEDATA,ipworks.INAPNODE,ipworks.ROUTEBYORIGIN,
ipworks.AINNODE,ipworks.RTGSCHED
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
12/8/2016 8:24 AM
21 of 62
Replicate_Wild_Ignore_Table:
Last_Errno:
Last_Error:
Skip_Counter:
Exec_Master_Log_Pos:
Relay_Log_Space:
Until_Condition:
Until_Log_File:
Until_Log_Pos:
Master_SSL_Allowed:
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master:
Master_SSL_Verify_Server_Cert:
Last_IO_Errno:
Last_IO_Error:
Last_SQL_Errno:
Last_SQL_Error:
1 row in set (0.00 sec)
0
0
209211
525
None
0
No
0
No
0
0
Note:
The fields Master_Log_File and Read_Master_Log_Pos have the same values as those of the Master
InnoDB Server.
mysql> exit
9. Check the status of the Master InnoDB.
Machine-1# /usr/local/mysql/bin/mysql
mysql> show master status;
+--------+----------+--------------+------------------+
| File
| Position | Binlog_Do_DB | Binlog_Ignore_DB |
+--------+----------+--------------+------------------+
| .000009|
209211 |
|
|
+--------+----------+--------------+------------------+
mysql> exit
10. Check if the replication has failed.
Machine-1# /usr/local/mysql/bin/mysql -P 3307 --protocol=tcp
mysql> show slave status \G

&mldr;
Last_Errno: 1051
Last_Error: error Unknown table &mldr;.
If the Last_Error shows some errors, the replication has failed.
mysql> exit
Use the following commands to restart the replication:
Machine-1# /usr/local/mysql/bin/mysql -P 3307 -h localhost --protocol=tcp
mysql> stop slave;
mysql> change master to MASTER_HOST='localhost';
mysql> start slave;
mysql> exit
12/8/2016 8:24 AM
22 of 62
Go to Step 7 and Step 9 to check the NDB Cluster.

11. Check that the ENUM tables have been replicated to the NDB Cluster.
Machine-1# /usr/local/mysql/bin/ndb_show_tables | grep ipworks | grep UserTable
Id
type
33
67
9
91
87
75
79
21
5
63
83
46
71
57
42
51
37
95
13
17
29
25
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
UserTable
4.1.4.7
state
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
logging database schema name

ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
ipworks
def
def
def
def
def
def
def
def
def
def
def
def
def
def
def
def
def
def
def
def
def
def
ENUMDNRANGE
MAPDATA
AINTOLLFREEDATA
INAPNODE
AINNODE
ROUTEBYTOD
RTGSCHED
COUNTRYCODE
AINLNPDATA
INAPDATA
RTGSCHEDENTRY
ENUMVIEW
ROUTEBYORIGIN
ENUMZONE
ENUMSERVER
ENUMZVREL
ENUMDNSCHED
MAPNODE
BULKUPDATE
CALLSERVER
ENUMACL
DESTNODE
Configuring DNS Server
This section provides the instructions to configure the DNS Server and its Server Manager on a single-machine installation,
to start the Server Manager, and to update the DNS Server.
1. Edit the /etc/resolv.conf file to add attributes.
nameserver 127.0.0.1
domain localhost
2. Edit the /etc/nsswitch.conf file to append dns to the hosts entry.
hosts: files dns
Machine-1# ipwscp
4. Use the IPWorks Control Panel to configure the DNS Server Manager parameters as follows:
Select DNS Services > DNS Server Manager > Configuration Parameters .
DNS Server Manager Configuration Parameters

Storage Server Address
127.0.0.1
Storage Server Port
17071
Storage Server Username
admin
Storage Server Password
********
Log Directory
/var/ipworks/logs
Logging Level (0-5)
0
6. Start the IPWorks CLI.
12/8/2016 8:24 AM
23 of 62
Machine-1# ipwcli
7. Create a dnsserver object.
IPWorks> create dnsserver dns1 set dnsname=dns1.iptelco.com;address=<M1 O&M IP
Address>;option="listen-on port 5300 {any;}"
1 object(s) created.
The names dns1 and iptelco.com are used as examples. The user does not need to configure the DNS Server at this
point in the installation procedure.
Note:
If the dnsserver object is not created using ipwcli, a default dnsserver with the same name as
the primary hostname is created, that is, the name displayed by the hostname system command.
Because of network access security, the IP address of ENUM server is configured by using the
Control Panel if the DNS server interacts with the ENUM server. If these two servers are installed
on the same machine, the default value is 127.0.0.1.
8. Create a masterzone object.
IPWorks> create masterzone dns1 iptelco.com
9. Create an arecord object.
IPWorks> create arecord dns1.iptelco.com <M1 Traffic IP Address>
10. Exit the CLI.
IPWorks> exit.
11. Ensure that the /var/run/dnssm.port file does not exist.
Machine-1# rm f /var/run/dnssm.port
12. Use the IPWorks Control Panel to start the DNS Server Manager.
Machine-1# ipwscp
Select DNS Services > DNS Server Manager > Start Server Manager .
Exit the IPWorks Control Panel.
13. Use the IPWorks CLI to update the dnsserver object.
Machine-1# ipwcli
IPWorks> update dnsserver dns1
Result of performing an export is:
Exported configuration for [DnsServer dns1]
Updated the configuration and started 'DNS' server 'dns1'.
IPWorks> exit
14. Verify that the dnsserver has been updated.
Machine-1# dig -p 5300 @<M1 Traffic IP Address> dns1.iptelco.com
The output from the above command contains the following text:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR,
4.1.4.8
Configuring ENUM Server
This section provides the instructions to configure and start the ENUM Server and its Server Manager on a single-machine
installation.
12/8/2016 8:24 AM
24 of 62
Machine-1# ipwscp
2. Configure the ENUM Server parameters as follows:
Select ENUM Services > ENUM Server > Configuration Parameters .
NDB Primary Management Node Address

NDB Secondary Management Node Address

ENUM Server Id
1
ENUM Server Port
53
Enable DNS Resolver
true
DNS Resolver IP Address
127.0.0.1
DNS Resolver UDP Port
5300
Log Destination
file
Log Level
off
Log Directory
/var/ipworks/logs
Name Prefix
enum_server
No. of Logs
1
Log size (1-20) Mb
1
Log start (0-4)
1
ENUM Thread Count
10
Granularity Period for Requests Failed Alarm
10
Threshold Level for Requests Failed Alarm
30
3. Configure the ENUM Server Manager parameters as follows:
Select ENUM Services > ENUM Server Manager > Configuration Parameters .
ENUM Server Manager Configuration Parameters

127.0.0.1
Storage Server Port
17071
admin
********
Log Directory
/var/ipworks/logs
Logging Level (0-5)
0
5. Ensure that the /var/run/enumsm.port file does not exist.
Machine-1# rm f /var/run/enumsm.port
6. (Optional) Use the IPWorks CLI to create an enumserver object.
Machine-1# ipwcli
IPWorks> create enumserver 1 set defaultmtu=1500;address=<M1 O&M IP Address>;enumserverid=1
IPWorks> exit
Note:
If the user omits this step, a default enumserver object is created when starting the ENUM Server
Manager in the IPWorks Control Panel.
7. Use the IPWorks Control Panel to start the ENUM Server Manager.
Machine-1# ipwscp
Select ENUM Services > ENUM Server Manager > Start Server Manager .
8. Use the IPWorks CLI to start the ENUM Server.
Machine-1# ipwcli
IPWorks> start enumserver 1
12/8/2016 8:24 AM
25 of 62
Started 'ENUMSERVER' server '1'

IPWorks> exit
4.1.4.9
Configuring DHCPv6 Server
This section provides instructions to configure the DHCPv6 Server and its Server Manager, to start the Server Manager, and
to update the server.
1. Use the IPWorks Control Panel to configure the DHCPv6 Server Manager parameters as follows:
DHCPv6 Server Manager Configuration Parameters

127.0.0.1
Storage Server Port
17071
admin
********
Log Directory
/var/ipworks/logs
Logging Level (0-5)
0
2. Check if the machine has the IPv6 address enabled.
Machine-1# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,
IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,
IPv4> mtu 1500 index 2
inet 100.0.0.4 netmask ffffff00 broadcast
100.0.0.255
ether 0:3:ba:df:89:7
inet6 ::1/128
bge0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu
1500 index 2
inet6 fe80::203:baff:fedf:8907/10
bge0:1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu
1500 index 2
inet6 3333:3333:3333:3333::104/64
3. Create a new IPv6 interface.
Machine-1# ifconfig <interface-name> inet6 plumb
For example:
Machine-1# ifconfig bge0 inet6 plumb
4. If the IPv6 address is not enabled, or if the user encounters a problem when using ifconfig to create the IPv6
address, edit the file /etc/hostname6.<interface_name> to set the IPv6 address to the IPv6 address of the server.
In the example shown in Step 2, the file /etc/hostname6.bge0 contains the following line:
addif 3333:3333:3333:3333::104/64 up
5. Reboot the machine after changing this file.
6. Create a dhcpv6server object.
Machine-1# ipwcli
IPWorks> create dhcpv6server <DHCPv6 Server Name> -set address=<M1 O&M IP Address>
IPWorks> exit
7. Ensure that the /var/run/dhcpv6.port file does not exist.
12/8/2016 8:24 AM
26 of 62
Machine-1# rm -f /var/run/dhcpv6.port
8. Use the IPWorks Control Panel to start the DHCPv6 Server Manager.
9. Update the dhcpv6server object.
Machine-1# ipwcli
IPWorks> update dhcpv6server <DHCPv6 Server Name>
1 object(s) updated.
IPWorks> exit
4.2 Installation Procedure for Medium Configuration

This section provides the instructions for a medium configuration. The medium configuration consists of at least four
machines: two acting as Sun Cluster for Storage Server and each of the others hosting an NDB Cluster.
4.2.1
Storage Server Host SS1 and SS2 require 2x SUN Netra 240, each with
Dual 1.5 GHz CPU
Dual SE6140 Disk Arrays (4x146G) with 2 Fiber Connections at 15k RPM
8 GB Memory
1 Ethernet Card with 4 Gigabit Ethernet Ports
2 Fiber Channel Interfaces
Protocol Server PS1 and PS2 require 2x SUN Netra 240, each with
Dual 1.5 GHz CPU
Dual 15k RPM, 73 GB disk drives
8 GB Memory
1 Ethernet Card with 3 Gigabit Ethernet Ports
4.2.2
Hardware Diagram and Configuration
The Medium Scenario represents a scenario, where the In-Memory cluster databases are collocated with the Protocol
Servers. This limits the ENUM database size to the RAM memory size of the Protocol Server machine. Figure 2 shows the
hardware diagram for medium configuration.
12/8/2016 8:24 AM
27 of 62
Figure 2
4.2.3
Medium Configuration
Setup Diagram
The medium configuration consists of at least four machines: two for Storage Servers and two for Protocol Servers.
Figure 3 shows the IPWorks modules that can be installed on each of the four machines in the medium configuration.
12/8/2016 8:24 AM
28 of 62
Figure 3
4.2.4
IPWorks Modules in a Medium Configuration
Table 10
Load Modules for Medium Configuration
Load Module Name
Machine-SS
Machine-PS
IPWcommon
IPWbackup
IPWjre
IPWmysql
IPWmysql (Innodb Node)
IPWmysql (Mgmt Node)

IPWmysql (Data Node)
IPWmysql (SQL Node)
IPWcli
IPWtomcat
12/8/2016 8:24 AM
29 of 62
IPWsm
IPWss
IPWcnoss
IPWwebui
IPWdns
IPWasdnsmon
IPWdnsalg
IPWdhcpv4
IPWenum
IPWdhcpv6
IPWerh
EAB SS7 Stack
IPWscagents
Table 11 shows the installation procedure for medium configuration. The installation is customized by the user and thus
Table 11
Installation Procedure for Medium Configuration
Step
Action
Description
Installing Load Modules on SS1, Table 10 and Section 4.2.5.1 Mandatory
Configuring MySQL InnoDB Master on SS1, Section 4.2.5.2
Mandatory
Configuring Storage Server on SS1, Section 4.2.5.3
Mandatory
Installing Load Modules on PS1, Table 10 and Section 4.2.6.1 Mandatory
Configuring NDB Cluster Management Node on PS1, Section

4.2.6.2
Mandatory
Configuring NDB Data Node on PS1, Section 4.2.6.3
Mandatory
Configuring NDB SQL Node on PS1, Section 4.2.6.4
Mandatory
Configuring DNS Server on PS1, Section 4.2.6.5
Mandatory
12/8/2016 8:24 AM
30 of 62
Configuring ENUM Server on PS1, Section 4.2.6.6
Mandatory
10
Configuring DHCPv6 Server on PS1, Section 4.2.6.7
Optional
11
Redo Step 5 to Step 11 on PS2
Mandatory
4.2.5
Sun Cluster Storage Server Installation
This section provides the instructions to set up and configure the machine hosting the Storage Server in the medium
configuration. This is machine SS1 in Figure 3. The instructions also apply to SS2.
For IPWorks 6.0, Sun Cluster is introduced to achieve high availability of data protection and automatic failover of Storage
Server. This section guides the user to install the IPWorks under Sun Cluster manually.
4.2.5.1
Installing Load Modules on Storage Server
Before installing the IPWorks 6.0 on Sun Cluster, ensure there is no previous version installed on this Cluster. Otherwise,
refer to Installation and Upgrade Tool User Guide, Reference [8].
1. Check if Sun Cluster has been successfully configured.
Note:
If the machine is configured on the slave node, the installation is rejected.
2. Clean unused links and make sure all the IPWorks load modules have been successfully removed.
Machine-SS1# pkginfo |grep IPW
The system is clean if there is no output. Otherwise remove the modules first.
Machine-SS1# pkgrm <package name>
Use the following commands to remove unnecessary links on both nodes.
Machine-SS1# cd /cdrom/cdrom0/solaris/utils
Machine-SS1# ./unlink.sh
3. Check if previous resource group exists.
Machine-SS1# scstat | grep ipworks_rg

Resources: ipworks_rg ipworks_lh ipworks_has mysql_res ipwss_res tomcat_res
Group: ipworks_rg
ipw5sc-01
Offline
No
Group: ipworks_rg
ipw5sc-02
Offline
No
4. If previous resource group already exists, use the following commands to remove it.
Machine-SS1#
Machine-SS1#
Machine-SS1#
Machine-SS1#
Machine-SS1#
Machine-SS1#
Machine-SS1#
Machine-SS1#
Machine-SS1#
Machine-SS1#
Machine-SS1#
Machine-SS1#
scswitch -F -g ipworks_rg
scswitch -n -j tomcat_res
scswitch -n -j ipwss_res
scswitch -n -j mysql_res
scswitch -n -j ipworks_has
scswitch -n -j ipworks_lh
scrgadm -r -j tomcat_res
scrgadm -r -j ipwss_res
scrgadm -r -j mysql_res
scrgadm -r -j ipworks_has
scrgadm -r -j ipworks_lh
scrgadm -r -g ipworks_rg
5. Install the load modules shown in Table 10 on machine SS1 to acquire Sun Cluster Redundancy.
During the installation of a common module, it checks whether Sun Cluster and Disk Array have been configured
successfully. If not, the installer cannot install it as the Sun Cluster mode.
12/8/2016 8:24 AM
31 of 62
6. Manually check the /etc/inet/hosts and /etc/inet/ipnodes files on both nodes before registering the Sun Cluster
resource and resource group. Ensure the virtual IP exists and its host name is ipworks.
For example, the hosts file on both machines may be
-------------------------------------------------10.170.4.2
ipw5sc-01 loghost
10.170.4.3
ipw5sc-02
...
10.170.4.50
ipworks
# virtual ip
----------------------------------------------------7. Check if virtual IP has been set successfully.
Machine-SS1# ipwssaddr
Virtual IP must not be used by other hosts that do not belong to this Sun Cluster.
8. Check if the IPMP has been successfully configured.
Machine-SS1# scstat | grep IPMP

-- IPMP Groups -IPMP Group: ipw5sc-01
traffic
IPMP Group: ipw5sc-01
traffic
traffic
traffic
Online
Online
Online
Online
bge1
bge0
bge1
bge0
Online
Online
Online
Online
Two IPMPs have been configured on both nodes.

9. Register the Sun Cluster resource and resource group on the machine, where the user installed the modules initially.
Machine-SS1# cd /cdrom/cdrom0/solaris/utils
Machine-SS1# ./ipw_reg_sscluster
Checking Logical Hostname ipworks..............done
Register Resource Type........................
Register Resource Groups......................
Register Resource Logical Hostname............
Register Resource Filesystem..................
done
done
done
done
sourcing /opt/SUNWscmys/util/mysql_config
MySQL version 5 detected on 5.10/SC3.2
please input the password of MySQL User: root
Password:
Add faulmonitor user (fmuser) with password (fmuser123)
with Process-,Select-, Reload- and Shutdown-privileges
to user table for mysql database for host ipw5sc-02
Add SUPER privilege for fmuser@ipw5sc-02

Add faulmonitor user (fmuser) with password (fmuser123)
with Process-,Select-, Reload- and Shutdown-privileges
to user table for mysql database for host ipw5sc-01
Add SUPER privilege for fmuser@ipw5sc-01

Create test-database sc3_test_database
Grant all privileges to sc3_test_database for

faultmonitor-user fmuser for host ipw5sc-02
12/8/2016 8:24 AM
32 of 62
Grant all privileges to sc3_test_database for

faultmonitor-user fmuser for host ipw5sc-01
Flush all privileges
Mysql configuration for HA is done

Register Resource Mysql....................... done
Register Resource IPWorks Storage Server...... done
Register Resource Tomcat Web Server........... done
clean rc scripts...
Register finished
The output is done if registration is successful.
The default password of root user is NULL, press Enter key.
Machine-1# ipwversion
4.2.5.2
This section provides the instructions to configure and start the MySQL InnoDB Master in the medium configuration.
1. Start the MySQL InnoDB Master:
Machine-SS1# /etc/init.d/ipworks.mysql start-master-innodb
/innodbnode_data/
2. Grant all privileges to localhost and each Protocol Server.
Machine-SS1# /usr/local/mysql/bin/mysql
mysql> grant all privileges on *.* to 'ipworks'@'<PS1 O&M IP>' identified by 'ipworks';
where <PS1 O&M IP> is the IP address of the O&M Ethernet interface card on machine PS1.
where <PS2 O&M IP> is the IP address of the O&M Ethernet interface card on machine PS2.
3. Verify the privileges:
For example:
+---------+----------------+
| user
| host
|
+---------+----------------+
| ipworks | <PS1 O&M IP>
|
| ipworks | <PS2 O&M IP>
|
| root
| localhost
|
| fmuser | <SS1 hostname> |
| root
| <SS1 hostname> |
| fmuser | <SS2 hostname> |
12/8/2016 8:24 AM
33 of 62
| ipworks | localhost
|
| root
| localhost
|
+---------+----------------+
8 rows in set (0.00 sec)
4. Quit the session:
mysql> quit
4.2.5.3
1. Create the MySQL databases:

Machine-SS1# /opt/ipworks/IPWss/db/create_mysql_db
2. If the ENUM Server is installed, create the ENUM database:
Machine-SS1# /opt/ipworks/IPWss/db/create_enum_db
3. If the DHCPv6 Server is installed, create the DHCPv6 database:
Machine-SS1# /opt/ipworks/IPWdhcpv6/db/create_dhcpv6_db
Machine-SS1# /etc/init.d/ipworks.ss start
5. Use the IPWorks Control Panel on machine SS1 to check that the Storage Server is running.
Machine-SS1# /opt/ipworks/IPWss/db/init_mysql_db
where <password> is the password of the admin user.
The objects are displayed during installation. The initialization is complete when the following output is displayed:

Exiting
Note:
The Username and Password that this script prompts for are the same used to login to the CLI on the
Storage Server.
7. Stop mysql and storage server and then bring the resource group online.
Machine-SS1# /etc/init.d/ipworks.ss stop
Machine-SS1# /etc/init.d/ipworks.mysql stop
Machine-SS1# scswitch -Z -g ipworks_rg
Using scstat to check if the resource group is online.
4.2.6
Protocol Server Installation
This section provides the instructions to set up and configure the machine hosting the NDB Cluster in the medium
configuration. This is machine PS1 in Figure 3. The instructions also apply to PS2.
12/8/2016 8:24 AM
34 of 62
4.2.6.1
Installing Load Modules on Protocol Server
1. Install the load modules shown in Table 10 on machine PS1.

Machine-PS1# ipwversion
4.2.6.2
Configuring NDB Cluster Management Node
This section provides the instructions to configure and start the Management Node of the NDB Cluster in the medium
configuration.
The configuration file used by the Management Node is /etc/ipworks/mysql/confs/ipworks_mgm_1.conf.
Table 12 shows the memory requirements for NDB Cluster Management Nodes.
Table 12
NDB Cluster Management Node Memory Requirements
Number of Records
Data Memory Required
Index Memory Required
1 Million
up to 3 GB
up to 600 MB
5 Million
up to 3.5 GB
up to 800 MB
8 Million
up to 4 GB
up to 1000 MB
Note:
If ENUM and DHCP are installed on the same machine, the number of records in ENUM must not exceed 4
million. Otherwise, the performance of the system cannot be ensured.
1. Start the IPWorks Control Panel on machine PS1.

Machine-PS1# ipwscp
2. Configure the Management Node configuration data.
Select MySQL Cluster Node > Management Node > Configuration > Management Node Parameters .
Configure the following attributes:
HostName
<PS1 O&M IP Address>
where <PS1 O&M IP Address> is the IP address of the machine on which the Management Node is running.
3. Configure the Data Node common parameters.
Select MySQL Cluster Node > Management Node > Configuration > Data Node Parameters .
Data Memory Size see Table 12
Index Memory Size see Table 12
No Of Replicas 1
No Of Fragment Log Files 128
Redo Buffer Size 8
12/8/2016 8:24 AM
35 of 62
4. Add one Data Node to the NDB Cluster.

This Data Node points to the IP address of machine PS1 on which the Data Node is running.
NodeType = DATA
HostName = <PS1 O&M IP Address>
where <PS1 O&M IP Address> is the IP address of the machine on which the Data Node is running.
5. Add three SQL Nodes to the NDB Cluster in sequence.
NodeType = SQL
HostName = <PS1 O&M IP Address>
where <PS1 O&M IP Address> is the IP address of the host on which the NDB Cluster runs, for example, 127.0.0.1.
The first SQL Node points to the IP address of the NDB MySQL Server (PS1) and is used for replication from innodb to
the DATA node.
The second SQL Node points to the IP address of the ENUM Server (PS1) and is the entry for the Enum Service to
access the cluster data.
The third SQL Node points to the IP address where the SQL Node is installed (PS1). This is the entry for the MySQL
NDB clients (for example, ndb_show_tables) to access the cluster data.
6. Start the NDB Cluster Management Node.
8. From the machine containing the Management Node (machine PS1), check that the node has started.
Machine-PS1# /etc/init.d/ipworks.mysql show-ndb-status

--------------------[ndbd(NDB)]
1 node(s)
id=2 (not connected, accepting connect from <PS1 IP Address>)
id=1 @<PS1 IP Address> (mysql-5.1.23 ndb-6.2.15)
[mysqld(API)]
3 node(s)
4.2.6.3
Configuring NDB Data Node
This section provides the instructions to configure and start the Data Node of the NDB Cluster in the medium configuration.
The configuration file used by the NDB Data Node is /etc/ipworks/mysql/confs/ipworks_datanode_my.conf.
Machine-PS1# ipwscp
2. Configure the Data Node parameters.
Select MySQL Cluster Node > Data Node > Configuration .
12/8/2016 8:24 AM
36 of 62
NDB Connect String
<PS1 O&M IP Address>:1186
where <PS1 O&M IP Address> is the IP address of the machine on which the Management Node is running.
3. Depending on whether the Data Node is started for the first time, choose one of the following options.
If the Data Node is started for the first time, select MySQL Cluster Node > Data Node > Start Initial .
Note:
This operation is only performed for the first time setup. The operation erases all the NDB data
from the disk.
If the Data Node is not started for the first time, select MySQL Cluster Node > Data Node > Start .
5. Check that the Data Node has started.
The output in the following example shows that the Data Node is connected to the NDB Cluster. The Data Node is
ready only when starting is not displayed in the string against the id=2.
For example:

--------------------[ndbd(NDB)]
1 node(s)
id=2 @<PS1 IP Address> (mysql-5.1.23 ndb-6.2.15, starting,
[mysqld(API)]
3 node(s)
4.2.6.4
Configuring NDB SQL Node
Configure and start the SQL Node of the first NDB Cluster in the medium configuration.
The configuration file used by the NDB Data Node is /etc/ipworks/mysql/confs/ipworks_datanode_my.conf
Machine-PS1# ipwscp
2. Configure the SQL Node parameters.
Select MySQL Cluster Node > SQL Node > Configuration .
ServerID
Port
datadirectory
3
3307
/etc/ipworks/mysql/sqlnode1_data
where ServerID specifies the server ID for SQL replication process. The value must be an integer greater than 1 and
unique among all the ENUM servers connected to the same Storage Server. This means ENUM server A cannot have
the same SQL Node ServerID as ENUM server B, if A and B are connected to the same Storage Server.
Master-Host
<SC Virtual IP Address>
12/8/2016 8:24 AM
37 of 62
where <SC Virtual IP Address> is the virtual IP address of the MySQL InnoDB.
If the Master Host value is changed by using the IPWorks Control Panel after the first correct configuration, it takes
effect after performing one of the following:
login to the SQL Node and use the CHANGE MASTER TO MASTER_HOST='New MASTER HOST' statement to reset
the SQL Node Master Host. (recommended)
restart of the SQL Node after deleting the master.info file located in /etc/ipworks/mysql/sqlnode1_data/.
NDB Connect String <PS1 O&M IP Address>:1186

where <PS1 O&M IP Address> is the IP address of the machine where the Management Node is running.
3. Go to the IPWorks Control Panel Main Screen and wait for the Data Node status to change to running .
4. Start the NDB SQL Node.
Note:
This node starts only when at least one NDB Data Node has successfully started.
6. Check that the SQL Node has started.

--------------------[ndbd(NDB)]
1 node(s)
id=2 @<PS1 IP Address> (mysql-5.1.23 ndb-6.2.15,
[mysqld(API)]
3 node(s)
The above output indicates that an SQL daemon has started.
7. Check the status of the SQL Node connections with the NDB Cluster and Master InnoDB.
Machine-PS1# /usr/local/mysql/bin/mysql -P 3307 h localhost -protocol=tcp
mysql> exit
For example:
Machine-PS1# /usr/local/mysql/bin/mysql -P 3307 h localhost -protocol=tcp
*********************** 1. row **********************

Id: 1
User: system user
Host:
db:
Command: Daemon
Time: 1
State: Waiting for event from ndbcluster
Info: NULL
12/8/2016 8:24 AM
38 of 62
*********************** 2. row **********************

Id: 2
User: system user
Host:
db: NULL
Command: Connect
Time: 164
State: Waiting for master to send event
Info: NULL
*********************** 1. row ***********************

Master_Host: 10.170.4.50
Master_User: ipworks
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: .000009
Read_Master_Log_Pos: 209211
Relay_Log_File: sqlnode.002278
Relay_Log_Pos: 242
Relay_Master_Log_File: .000009
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB: ipworks
Replicate_Ignore_DB:
Replicate_Do_Table:
ipworks.MAPDATA,ipworks.BULKUPDATE,
ipworks.INAPDATA,ipworks.ENUMDNRANGE,ipworks.RTGSCHEDENTRY,
ipworks.ENUMACL,ipworks.ENUMDNSCHED,ipworks.DESTNODE,
ipworks.MAPNODE,ipworks.ENUMZONE,ipworks.ENUMZVREL,
ipworks.CALLSERVER,ipworks.ENUMVIEW,ipworks.ROUTEBYTOD,
ipworks.AINLNPDATA,ipworks.ENUMSERVER,ipworks.COUNTRYCODE,
ipworks.AINTOLLFREEDATA,ipworks.INAPNODE,ipworks.ROUTEBYORIGIN,
ipworks.AINNODE,ipworks.RTGSCHED
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 209211
Relay_Log_Space: 525
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 0
Last_SQL_Error:
The Master_Host must contain <SC Virtual IP Address>, that is, the Virtual IP address of the Sun Cluster where
the InnoDB server is installed. If not, execute the following command.
mysql> change master to MASTER_HOST='<SC Virtual IP Address>';.
12/8/2016 8:24 AM
39 of 62
The fields Master_Log_File and Read_Master_Log_Pos have the same values as those of the Master InnoDB Server.
mysql> exit
9. Check the status of the Master InnoDB on machine SS1.
mysql> show master status;
+--------+----------+--------------+------------------+
| File
| Position | Binlog_Do_DB | Binlog_Ignore_DB |
+--------+----------+--------------+------------------+
| .000009|
209211 |
|
|
+--------+----------+--------------+------------------+
mysql> exit
10. Check if the replication has failed.
Machine-PS1# /usr/local/mysql/bin/mysql -P 3307 --protocol=tcp
mysql> show slave status \G

&mldr;
Last_Errno: 1051
Last_Error: error Unknown table &mldr;.
If the Last_Error shows some errors, the replication has failed.
Follow the procedure below to restart the replication:
Machine-PS1# /usr/local/mysql/bin/mysql -P 3307 -h localhost --protocol=tcp
mysql> stop slave;
mysql> change master to MASTER_HOST='<SC Virtual IP Address>';
mysql> start slave;
mysql> exit
Perform Step 7 to Step 9 to check the NDB Cluster.
4.2.6.5
This section provides the instructions to configure the DNS Server and its Server Manager in the medium configuration, to
start the Server Manager, and to update the DNS Server.
1. Edit the /etc/resolv.conf file to add nameserver and domain localhost attributes.
domain localhost
hosts: files dns
3. Use the IPWorks Control Panel on machine PS1 to configure the DNS Server Manager parameters.
Machine-PS1# ipwscp
DNS Server Manager Configuration Parameters

<virtual ip of sun cluster>
Storage Server Port
17071
admin
<password>
Log Directory
/var/ipworks/logs
12/8/2016 8:24 AM
40 of 62
Logging Level (0-5)

4. Start the IPWorks CLI from the shell prompt on machine SS1.
Machine-SS1# ipwcli
IPWorks> create dnsserver dns1 set dnsname=dns1.iptelco.com;address=<PS1 O&M IP
Address>;option="listen-on port 5300 {any;}"
The names dns1 and iptelco.com are used as an example. The user does not need to configure the DNS Server at
this point in the installation procedure.
Note:
If the dnsserver object is not created using ipwcli, a default dnsserver with the same name as
the primary hostname is created, that is, the name displayed by the hostname system command.
Because of network access security, the IP address of ENUM server is configured by using the
Control Panel if the DNS server interacts with the ENUM server. If these two servers are installed
on the same machine, the default value is 127.0.0.1.
IPWorks> create arecord dns1.iptelco.com <PS1 Traffic IP Address>
8. Exit the CLI.
IPWorks> exit
Machine-PS1# rm f /var/run/dnssm.port
10. Use the IPWorks Control Panel on machine PS1 to start the DNS Server Manager.
Machine-PS1# ipwscp
11. Use the IPWorks CLI on machine SS1 to update the DNS Server.
Machine-SS1# ipwcli
IPWorks> exit
Machine-PS1# dig -p 5300 @<PS1 Traffic IP Address> dns1.iptelco.com
Example:
; <<>> DiG 9.2.4 <<>> -p 5300 @100.0.0.41
12/8/2016 8:24 AM
41 of 62
dns1.iptelco.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1,
AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;dns1.iptelco.com.
IN A
;; ANSWER SECTION:
dns1.iptelco.com. 86400 IN A 100.0.0.41>
;; AUTHORITY SECTION:
iptelco.com.
86400 IN NS dns1.iptelco.com.
;; Query time: 2 msec
;; SERVER: <PS1 Traffic IP address>#5300(100.0.0.41)
;; WHEN: Tue Nov 28 14:54:43 2006
;; MSG SIZE rcvd: 64
4.2.6.6
Configuring ENUM Server
This section provides the instructions to configure and start the ENUM Server and its Server Manager on the NDB Cluster in
the medium configuration.
Machine-PS1# ipwscp
2. Configure the ENUM Server parameters.
Select ENUM Services > ENUM Server > Configuration Parameters .
NDB Primary Management Node Address

NDB Secondary Management Node Address

ENUM Server Id
1
ENUM Server Port
53
Enable DNS Resolver
true
DNS Resolver IP Address
127.0.0.1
DNS Resolver UDP Port
5300
Log Destination
file
Log Level
fatal
Log Directory
/var/ipworks/logs
Name Prefix
ipworks_enum
No. of Logs
1
Log size (1-20) Mb
1
Log start (0-4)
0
ENUM Thread Count
10
Security Log Directory
/var/ipworks/logs/security
Security Logging Level (0-3)
2
No. of Security Log Files
5
Security Log File Size (1-5)Mb 1
Granularity Period for Requests Failed Alarm (Mnts) 10
Threshold Level for Requests Failed Alarm
30
3. Configure the ENUM Server Manager parameters.
Select ENUM Services > ENUM Server Manager > Configuration Parameters .

Storage Server Port
Log Directory
Logging Level (0-5)

17071
admin
<password>
/var/ipworks/logs
0
12/8/2016 8:24 AM
42 of 62

5. Ensure that the /var/run/enumsm.port file does not exist on machine PS1.
Machine-PS1# rm f /var/run/enumsm.port
6. (Optional) Use the IPWorks CLI on machine SS1 to create an enumserver object.
Machine-SS1# ipwcli
IPWorks> create enumserver 1 set defaultmtu=1500;address=<PS1 O&M IP address>;enumserverid=1
IPWorks> exit
Note:
If the user omits this step, a default enumserver object is created when starting the ENUM Server
Manager in the IPWorks Control Panel.
7. Use the IPWorks Control Panel on machine PS1 to start the ENUM Server Manager.
Machine-PS1# ipwscp
Select ENUM Services > ENUM Server Manager > Start Server Manager .
Machine-SS1# ipwcli
9. Check that an enumserver object has been created on machine SS1.
IPWorks> list enumserver
10. Start the ENUM Server on machine SS1.
Started 'ENUMSERVER' server '1'
11. Exit the CLI.
IPWorks> exit
4.2.6.7
This section provides the instructions to configure and start the DHCPv6 Server and its Server Manager in the medium
configuration.
1. Use the IPWorks Control Panel on machine SS1 to configure the DHCPv6 Server Manager parameters.

Storage Server Port
Log Directory
Logging Level (0-5)

17071
admin
<password>
/var/ipworks/logs
0

Machine-SS1# ifconfig -a
100.0.0.255
12/8/2016 8:24 AM
43 of 62
inet6 ::1/128
1500 index 2
1500 index 2
inet6 3333:3333:3333:3333::104/64
Machine-SS1# ifconfig <interface-name> inet6 plumb
For example:
Machine-SS1# ifconfig bge0 inet6 plumb
address, edit the file /etc/hostname6.<interface-name> to set the IPv6 address to the IPv6 address of the server.
In the example shown above, the file /etc/hostname6.bge0 contains the following line:
addif 3333:3333:3333:3333::104/64 up
Reboot the machine after changing this file.
5. Use the IPWorks CLI on machine SS1 to create a dhcpv6server object.
Machine-SS1# ipwcli
IPWorks> create dhcpv6server <DHCPv6 Server Name> -set address=<PS1 O&M IP Address>
IPWorks> exit
Machine-SS1# rm -f /var/run/dhcpv6.port
7. Use the IPWorks Control Panel on machine SS1 to start the DHCPv6 Server Manager.
Machine-SS1# ipwcli
IPWorks> exit
4.3 Installation Procedure for Legacy Configuration

This section provides the instructions for a legacy configuration. The legacy configuration consists of three machines: one
hosting the Storage Server and each of the other two hosting the Protocol Server. The legacy configuration supports the
previous IPWorks release, which does not include ENUM or NDB Cluster.
4.3.1
The three machines in the legacy configuration must have the following system configuration:
Sun Netra 240
8 GB RAM
12/8/2016 8:24 AM
44 of 62
Interface Cards
1 Ethernet Card with 2 Gigabit Ethernet Ports (one for O&M and the other for traffic)
4.3.2
Setup Diagram
The legacy configuration consists of three machines: one Storage Server and two Protocol Servers.
Figure 4 shows the IPWorks modules that can be installed on each of the three machines in the legacy configuration.
Figure 4
4.3.3
IPWorks Modules in Legacy Configuration
Table 13
Load Modules for Legacy Configuration
Load Module Name
Machine-SS
Machine-PS
IPWcommon
IPWbackup
IPWjre
IPWmysql
IPWcli
IPWtomcat
IPWsm
Only if DHCPv6 functionality is

required
12/8/2016 8:24 AM
45 of 62
IPWss
IPWcnoss
IPWwebui
IPWdns
IPWasdnsmon
IPWdnsalg
IPWdhcpv4
IPWenum
Only if DHCPv6 functionality is
required
IPWdhcpv6
IPWerh
EAB SS7 Stack
IPWscagents
Table 14 shows the installation procedure for legacy configuration. The installation is customized by the user and thus
Table 14
Installation Procedure for Legacy Configuration
Step
Action
Mandatory
Mandatory
Configuring DHCPv6 Server on SS1, Section 4.3.4.4
Optional
Installing Load Modules on PS1, Table 13 and Section 4.3.5.1 Mandatory
Mandatory
Mandatory
4.3.4
Description
Storage Server Installation
This section provides the instructions to set up and configure the machine hosting the Storage Server in the legacy
configuration. This is machine SS1 in Figure 4.
12/8/2016 8:24 AM
46 of 62
4.3.4.1
1. Install the load modules shown in Table 13 on machine SS1.

Machine-SS1# ipwversion
4.3.4.2
This section provides the instructions to configure and start the MySQL InnoDB Master in the legacy configuration.
/innodbnode_data/
2. Grant all privileges to localhost.
mysql> quit
4.3.4.3
This section provides the instructions to create the Storage Server databases in the legacy configuration, to start the
Storage Server and to initialize the Storage Server database.
The objects are displayed during installation. The initialization is complete when the following output is displayed:
12/8/2016 8:24 AM
47 of 62

Exiting
Note:
Storage Server.
4.3.4.4
This section provides the instructions to configure and start the DHCPv6 Server and its Server Manager in the legacy
configuration.
1. Use the IPWorks Control Panel on machine SS1 to configure the DHCPv6 Server Manager parameters as follows:
Storage Server Address <SS1 O&M IP Address>

Storage Server Port 17071
Storage Server Username admin
Storage Server Password <password>
Log Directory /var/ipworks/logs
Logging Level (0-5) 0
Machine-SS1# ifconfig -a
100.0.0.255
inet6 ::1/128
1500 index 2
1500 index 2
inet6 3333:3333:3333:3333::104/64
Machine-SS1# ifconfig <interface-name> inet6 plumb
For example:
Machine-SS1# ifconfig bge0 inet6 plumb
address, edit the file /etc/hostname6.<interface-name> to set the IPv6 address to the IPv6 address of the server.
In the example shown in Step 2, the file /etc/hostname6.bge0 contains the following line:
addif 3333:3333:3333:3333::104/64 up
Reboot the machine after changing this file.
12/8/2016 8:24 AM
48 of 62
5. Create a dhcpv6server object.

Machine-SS1# ipwcli
IPWorks> create dhcpv6server <DHCPv6 Server Name> -set address=<SS1 Traffic IP Address>
IPWorks> exit
Machine-SS1# rm -f /var/run/dhcpv6.port
7. Use the IPWorks Control Panel on machine SS1 to start the DHCPv6 Server Manager.
Machine-SS1# ipwcli
IPWorks> exit
4.3.5
Protocol Server Installation
This section provides the instructions to set up and configure the machine hosting the first of the two Protocol Servers in
the legacy configuration. This is machine PS1 in Figure 4. The instructions also apply to PS2.
4.3.5.1
Installing Load Modules on Protocol Server
1. Install the load modules shown in Table 13 on machine PS1.

The following command displays the release numbers of the installed load modules.
Machine-PS1# ipwversion
4.3.5.2
This section provides the instructions to configure the DNS Server and its Server Manager in the legacy configuration, to
start the Server Manager, and to update the DNS Server.
1. Edit the /etc/resolv.conf file to add the following attributes:
domain localhost
hosts: files dns
3. Use the IPWorks Control Panel on machine PS1 to configure the DNS Server Manager parameters.
Machine-PS1# ipwscp

Storage Server Port
Log Directory
Logging Level (0-5)
<SS1 O&M IP Address>

17071
admin
<password>
/var/ipworks/logs
0
12/8/2016 8:24 AM
49 of 62
Machine-SS1# ipwcli
IPWorks> create dnsserver dns1 set dnsname=dns1.iptelco.com;address=<PS1 O&M IP Address>
The names dns1 and iptelco.com are used as an example. The user does not need to configure the DNS Server at
this point in the installation procedure.
Note:
If the dnsserver object is not created using ipwcli, a default dnsserver with the same name as the
primary hostname is created, that is, the name displayed by the hostname system command.
IPWorks> create arecord dns1.iptelco.com <PS1 Traffic IP Address>
8. Exit the CLI.
IPWorks> exit
Machine-PS1# rm f /var/run/dnssm.port
10. Use the IPWorks Control Panel on machine PS1 to start the DNS Server Manager.
Machine-PS1# ipwscp
11. Update the DNS Server on machine SS1.
Machine-SS1# ipwcli
IPWorks> exit
Machine-PS1# dig @<PS1 Traffic IP Address> dns1.iptelco.com
Example:
; <<>> DiG 9.2.4 <<>> @100.0.0.41

dns1.iptelco.com
;; Got answer:
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1,
AUTHORITY: 1, ADDITIONAL: 0
;dns1.iptelco.com.
IN A
12/8/2016 8:24 AM
50 of 62
;; ANSWER SECTION:
dns1.iptelco.com. 86400 IN A 100.0.0.41>
iptelco.com.
86400 IN NS dns1.iptelco.com.
;; Query time: 2 msec
;; SERVER: <PS1 Traffic IP address>#53(100.0.0.41)
;; WHEN: Tue Nov 28 14:54:43 2006
;; MSG SIZE rcvd: 64
4.4 Installation Procedure for Entry Configuration

This section provides the instructions for an entry configuration. The entry configuration consists of three machines: one
hosting the Storage Server and the other two hosting the Protocol Servers. The entry configuration supports the ENUM
server and MySQL NDB Cluster.
4.4.1
The three machines in the entry configuration must have the following system configurations:
Sun Netra 240
8 GB RAM
Interface Cards
1 Ethernet Card with 2 Gigabit Ethernet Ports (one for O&M and the other for traffic)
4.4.2
Setup Diagram
The entry configuration consists of three machines: one Storage Server and two Protocol Servers. Figure 5 shows the
IPWorks modules that can be installed on each of the three machines in the entry configuration.
12/8/2016 8:24 AM
51 of 62
Figure 5
4.4.3
IPWorks Modules in Entry Configuration
Table 15
Load Modules for Entry Configuration
Load Module Name
Machine-SS
Machine-PS
IPWcommon
IPWbackup
IPWjre
IPWmysql
IPWmysql (Mgmt Node)

IPWmysql (Data Node)
IPWmysql (SQL Node)
IPWcli
IPWtomcat
IPWsm
IPWss
IPWcnoss
IPWwebui
IPWdns
IPWasdnsmon
IPWdnsalg
IPWdhcpv4
IPWenum
IPWdhcpv6
IPWerh
EAB SS7 Stack
IPWscagents
Table 16 shows the installation procedure for entry configuration. The installation is customized by the user and thus
12/8/2016 8:24 AM
52 of 62

Table 16
Installation Procedure for Entry Configuration
Step
Action
Description
Mandatory
Mandatory
Installing Load Modules on PS1, and Section 4.2.6.1
Mandatory
Configuring NDB Cluster Management Node on PS1, Section

4.2.6.2
Mandatory
Configuring NDB Data Node on PS1, Section 4.2.6.3
Mandatory
Configuring NDB SQL Node on PS1, Section 4.2.6.4
Mandatory
Mandatory
Configuring ENUM Server on PS1, Section 4.2.6.6
Mandatory
10
Configuring DHCPv6 Server on PS1, Section 4.2.6.7
Optional
11
Mandatory
Storage Server Installation
4.4.4
This section provides the instructions to set up and configure the machine hosting the Storage Server in the entry
configuration. This is machine SS1 in Figure 5.
4.4.4.1
1. Install the load modules shown in Table 15 on machine SS1.

Machine-SS1# ipwversion
4.4.4.2
This section provides the instructions to start and configure the MySQL InnoDB Master in the entry configuration.
/innodbnode_data/
12/8/2016 8:24 AM
53 of 62
2. Grant all privileges to localhost and each Protocol Server.

Where:
<PS1 O&M IP> is the IP address of the O&M Ethernet interface card on machine PS1.
<PS2 O&M IP> is the IP address of the O&M Ethernet interface card on machine PS2.
mysql> quit
4.4.4.3
This section provides the instructions to create the Storage Server databases in the entry configuration, to start the Storage
Server, to initialize the Storage Server and the ENUM database.
2. If the ENUM Server is installed, create the ENUM database.
Machine-SS1# /opt/ipworks/IPWss/db/create_enum_db
The objects being installed are displayed. The initialization is complete when the following output is displayed:

Exiting
Note:
Storage Server.
12/8/2016 8:24 AM
54 of 62
5 Installation Verification
This section describes the installation verification through the Control Panel, CLI, and Web Application. For more
information, see the following documents:
Control Panel User Guide, Reference [2]
Command Line Interface (CLI) User Guide, Reference [9]
Web Interface User Guide, Reference [10]
5.1 Verifying the DNS Service

To verify that IPWorks was installed properly and is operational using a simple DNS Server configuration, perform the
following steps:
If the Storage Server is not running, the user must start it. For more information on how to start the Storage Server
from the IPWorks Control Panel, refer to Control Panel User Guide, Reference [2].
2. From the shell prompt, start the IPWorks CLI and log into the Storage Server using the command ipwcli. See
Section 6.3 for more information.
3. Create a DNS Server. The IP address used in the command must be the IP address of the machine, where the DNS
Server is running.
For this example, the IP address 10.0.0.1 and server name dns.example.com are used.
IPWorks> create dnsserver dns -set dnsname=dns.example.com -set address=10.0.0.1
The Server Manager periodically updates the Storage Server with the status of the DNS Server. If there is no
corresponding object in the Storage Server, an object for the DNS Server is automatically created in the Storage
Server. The user can set the parameter Sm.CreateServer in the /opt/ipworks/etc/ipworks
/ipworks_sm_defaults.conf file.
4. Create a Master Zone:
IPWorks> create masterzone dns example.com
5. Create an arecord for the zone.
IPWorks> create arecord host.example.com 10.0.0.1
6. Exit the CLI.
IPWorks> exit
7. Use the IPWorks Control Panel to configure the DNS Server Manager Configuration Parameters.
In the Storage Server Address field, enter the <SC Virtual IP Address> for medium configuration, and <SS O&M
IP Address> for other configurations.
In the Storage Server Password field, enter the storage server password.
8. Use the IPWorks Control Panel to start the DNS Server Manager.
9. Use the IPWorks CLI to update the DNS Server configuration:
# ipwcli
IPWorks> update dnsserver -where name=dns
12/8/2016 8:24 AM
55 of 62
IPWorks> exit
10. Use dig to verify that the DNS Server is updated and that the test arecord is returned properly. The entry in the
answer section must match the data entered in Step 5.
# dig @10.0.0.1 host.example.com
A
; <<>> DIG 9.3.0 <<>> @10.0.0.1 host.example.com
;; Got answer:
;; ->>HEADER<<- opcode: QUERY,
status: NOERROR, id: 42528
;; flags: qr aa rd ra; QUERY: 1,
ANSWER: 1, AUTHORITY: 1,
ADDITIONAL: 0
;host.example.com.
IN
;; ANSWER SECTION:
host.example.com.
8640
example.com.
86400
;;
;;
;;
;;
0 IN
IN
10.0.0.1
NS dns.example.com.
Query time: 5 msec

SERVER: 10.0.0.1#53(local-ip-address)
WHEN: Thu Oct 31 13:36:11 2002
MSG SIZE rcvd: 67
11. Use the IPWorks Control Panel to stop the DNS Server Manager.
12. Use the IPWorks CLI to delete the test data:
# ipwcli
IPWorks> delete arecord host.example.com
IPWorks> delete masterzone example.com
IPWorks> delete dnsserver dns
5.2 Verifying the ENUM Service

Use the following procedure to verify that IPWorks was installed properly and is operational using a simple ENUM Server
configuration:
If the Storage Server is not running, the user must start it. For more information on how to start the Storage Server
from the Control Panel, refer to Control Panel User Guide, Reference [2].
2. Use the IPWorks Control Panel to start the NDB Cluster, and to ensure the Management Node, Data Node, and SQL
Node are started.
3. Use the IPWorks Control Panel to check that the ENUM Server Manager is running.
If not, the user must start them.
4. Use the IPWorks CLI to create a DNS Server:
# ipwcli
IPWorks> create dnsserver dnstest -set dnsname=dnstest.example.com -set address=<DNS Server O&M IP
address>;option=listen-on port 5300 {any;}
IPWorks> create masterzone dnstest example.com
IPWorks> create arecord dnstest.example.com <IP address>
Start the DNS Server Manager, then update the dnsserver in the CLI:
12/8/2016 8:24 AM
56 of 62
IPWorks> update dnsserver dnstest

5. Create the enumserver object if it does not already exist:
IPWorks> create enumserver 1 -set defaultmtu=1500;address=<ENUM Server IP
Address>;defaultnaptrorder=10
6. Update the ENUM Server configuration:
IPWorks> create enumzone 1 -set enumzonename="e164.example.com"
IPWorks> create enumdnsched 4.3.2.1.4.3.2.1.0.1.4.4.e164.example.com
-set naptrFlags=nu;naptrOrder=100;naptrPreference=10;naptrService=E2U+SIP;
naptrTxt=!^.*$!sip:[email protected]!
IPWorks> exit
7. Use the following command to verify that the ENUM Server was updated:
# dig @<ENUM Server Traffic IP Address> 4.3.2.1.4.3.2.1.0.1.4.4.e164.example.com
The following output is an example.
; <<>> DiG 9.3.2 <<>> @127.0.0.1 4.3.2.1.4.3.2.1.0.1.4.4.

e164.example.com
; (1 server found)
;; Got answer:
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0,
ADDITIONAL: 0
;4.3.2.1.4.3.2.1.0.1.4.4.e164.example.com. IN A
;; ANSWER SECTION:
4.3.2.1.4.3.2.1.0.1.4.4.e164.example.com. 0 IN NAPTR 100 10
"u" "E2U+SIP" "!^.*$!sip:[email protected]!" .
4.3.2.1.4.3.2.1.0.1.4.4.e164.example.com. 0 IN TXT
"EV=1\010EL=5\010PB=0\010"
;;
;;
;;
;;
Query time: 3 msec

SERVER: 127.0.0.1#53(127.0.0.1)
WHEN: Tue Oct 9 15:33:09 2007
MSG SIZE rcvd: 149
8. Use the following command to verify that the ENUM Server can forward the DNS query:
# dig @<ENUM Server Traffic IP Address> dnstest.example.com
The following output is an example.
; <<>> DiG 9.3.2 <<>> @10.170.4.33 test.example.com

; (1 server found)
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 711
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1,
ADDITIONAL: 0
;test.example.com.
example.com.
86400
IN
IN
SOA
12/8/2016 8:24 AM
57 of 62
dnstest.example.com. root.dnstest.example.com.
2 10800 3600 604800 86400
;;
;;
;;
;;
Query time: 1 msec

SERVER: 10.170.4.33#53(10.170.4.33)
WHEN: Mon Oct 22 13:46:18 2007
MSG SIZE rcvd: 83
9. Use the IPWorks Control Panel to stop the DNS server, DNS Server Manager, ENUM Server, ENUM Server Manager,
and NDB Cluster. Then use the IPWorks CLI to delete the test data.
# ipwcli
IPWorks>
IPWorks>
IPWorks>
IPWorks>
IPWorks>
delete
delete
delete
delete
exit
enumdnsched 4.3.2.1.4.3.2.1.0.1.4.4.e164.example.com
enumzone 1
enumserver 1
dnsserver dnstest
5.3 Verifying the DHCPv4 Service

Use the following procedure to verify that a DHCPv4 Server is correctly installed:
1. Use the IPWorks Control Panel on the DHCPv4 Server system to select the DHCPv4 Server options and start only the
Server Manager of the DHCPv4 Server.
2. Use the IPWorks CLI or Web Application to connect to the Storage Server and check that the dhcpv4server object
was automatically added to the DHCPv4 Server:
IPWorks> list dhcpv4server <server-name>
or
IPWorks> list dhcpv4server -where address=<ip-address>
3. Create a subnet based on the physical subnet where the server is configured and allow unknown clients. For example,
enter the following commands to use the network 10.5.0.0/16:
IPWorks> create subnet -set name="10.5Net" -set address=10.5.0.0 -set masklength=16 -set server=
<server-name>
IPWorks> modify -add option="allow-unknown-clients true"
4. Create a pool for the server. For example, if the subnet is 10.5.0.0, set the pool name to A Pool and use the
address range from 10.5.0.1 to 10.5.0.10 (inclusive) :
IPWorks> create pool -set name="A Pool" -set subnet="10.5Net" -set addressrange=10.5.0.1-10.5.0.10
-set allowedclient=unknown -set server=<server-name>
5. Enter the following commands to view the configuration file used by the server:
IPWorks> select dhcpv4server <server-name>
IPWorks> list dhcpv4server <server-name>
6. Update the server to apply the configuration and start the server:
IPWorks> update dhcpv4server <server-name>
7. Check that the DHCPv4 Server is operational:
IPWorks> show status dhcpv4server <server-name>
8. Log out of the CLI:
IPWorks> exit
9. Use a DHCP test client connected to the network ( 10.5.0.0) to obtain a lease. For a Windows 2000 client, the user
can verify that a lease was obtained from the server using ipconfig /all from the Windows command prompt.
Check that the correct server provided the lease (see the DHCP Server line in the ipconfig /all output).
12/8/2016 8:24 AM
58 of 62
ipconfig /all
5.4 Verifying the Web Application

Use the following procedure to verify that the Web Application has been installed properly and is working:
1. Use a supported web browser to connect to the Web Application using the following URL:
http://<hostname>:8080/ipworks/webapp
where <hostname> is the domain name or IP address of the host on which the Web Application has been installed.
The Login page with the Ericsson logo is displayed.
Note:
The user must start the Storage Server and Tomcat before using the Web Application.
2. When prompted for User Name and Password, enter a valid user name and password (for example, the administrator
account created during installation).
3. Click Login .
The Welcome page appears.
4. Select Search > Object Class > Partition .
5. Click Go . This searches for all of the partitions currently defined.
The Partition Search Results page is displayed in at least one partition found (the active partition).
6. Select Logout > Other Pages .
The verification for the Web Application is completed. Log out of the Web Application.
5.5 Verifying Sudo

User the following command to verify the installation of sudo:
# sudo -V
Sudo version 1.6.8p9
This is the partial output of the version information of sudo. Any error message in this case implies incorrect installation of
sudo.
For more information on errors and how to handle them, refer to Troubleshooting User Guide, Reference [11].
6 Appendix
This section provides the instructions to display the versions of the currently installed IPWorks components, to launch the
management interfaces of IPWorks, to start and stop certain IPWorks components, and to configure SS7.
6.1 Displaying IPWorks Component Version Information

The ipwversion command is available once the IPWcommon load module is installed.
1. Display the product number and software version of each installed component.
# ipwversion
For example:
# ipwversion
Installed IPWorks 6.0 (CSH_109_085_R1A_LSV1)

load modules:
12/8/2016 8:24 AM
59 of 62
IPWcommon
IPWjre
IPWmysql
IPWcli
IPWss
IPWbackup
IPWcnoss
IPWtomcat
IPWwebui
IPWsm
IPWdns
IPWenum
IPWasdnsmon
IPWdnsalg
IPWdhcpv4
IPWdhcpv6
->
->
->
->
->
->
->
->
->
->
->
->
->
->
->
->
CXP_901_3879_R1A_LSV1
CXP_901_3878_R1A_LSV1
CXP_901_3877_R1A_LSV1
CXP_901_3876_R1A_LSV1
CXP_901_3875_R1A_LSV1
CXP_901_3881_R1A_LSV1
CXP_901_3880_R1A_LSV1
CXP_901_3873_R1A_LSV1
CXP_901_3874_R1A_LSV1
CXP_901_3883_R1A_LSV1
CXP_901_3885_R1A_LSV1
CXP_901_3889_R1A_LSV1
CXP_901_3882_R1A_LSV1
CXP_901_3884_R1A_LSV1
CXP_901_3886_R1A_LSV1
CXP_901_3887_R1A_LSV1
2. Display the installed data, time and build number associated with the installed IPWorks 6.0 releases.
# ipwversion history
For example:
# ipwversion history
CSH_109_085_R1A_LSV1 *
Installed Date
Build no
: Aug 4 13:34;
: 1001;
3. Display the installed releases of a specified load module:

# ipwversion <Load Module name>
For example:
# ipwversion IPWcommon
IPWorks 6.0 (CSH_109_085_R1A_LSV1) (* denotes active release)

IPWcommon
-> CXP_901_3879_R1A_LSV1 *
6.2 Launching the IPWorks Control Panel

Launch the IPWorks Control Panel.
1. Login as root.
2. Enter ipwscp.
The IPWorks Control Panel is described in Control Panel User Guide, Reference [2].
6.3 Launching the IPWorks Command Line Interface

To launch the IPWorks CLl:
1. Login as root.
Note:
When logging in to the CLI, select the c shell. Do not use the bash shell.
2. Enter the following command:
# ipwcli
IPWorks> Login: <username>
IPWorks> Password: <password>
12/8/2016 8:24 AM
60 of 62
Login to server successful.

IPWorks>
For example:
# ipwcli
IPWorks> Login: admin
IPWorks> Password:
Login to server successful.
IPWorks>
The CLI is described in Command Line Interface (CLI) User Guide, Reference [9].
Note:
To perform an operation on a Protocol Server from the CLI, first use the Control Panel to start the Server
Manager process of the corresponding IPWorks component (DNS, DHCPv4, DHCPv6, ASDNSMON or
ENUM).
3. Log out of the CLI.
IPWorks> exit
6.4 Launching the Web User Interface

Note:
The user must have started the Storage Server and Tomcat before using the Web User Interface.
Launch the Web User Interface.

1. Use a supported web browser to connect to the Web Application using the following URL:
http://<hostname>:8080/ipworks/webapp
where <hostname> is the domain name or IP address of the host on which the Web Application has been installed.
The Login page with the Ericsson logo is displayed.
2. When prompted for User Name and Password, enter a valid user name and password (for example, the administrator
account created during installation) and click Login .
The Welcome page appears.
The Web Interface is described in the Web Interface User Guide, Reference [10].
Note:
Before performing any operation on a Protocol Server from the Web User Interface, use the Control Panel to
start the Server Manager process of the corresponding IPWorks component.
6.5 Starting and Stopping the IPWorks Components

This section describes how to start and stop the IPWorks Components, including Tomcat, Storage Server, InnoDB, NDB SQL
Node, NDB Management Node, NDB Data Node and NDB Cluster.
6.5.1
Starting Tomcat
Tomcat is a servlet container used to support the service of WebUI. User must start Tomcat before using the Web
Application.
Perform the following commands to start Tomcat on single or legacy configuration.
# cd /etc/init.d/
# ./ipworks.tomcat start
12/8/2016 8:24 AM
61 of 62
6.5.2
Starting and Stopping Storage Server

Start the Storage Server on single-machine, legacy, and entry configuration.
# /etc/init.d/ipworks.ss start
Stop the Storage Server on single-machine, legacy, and entry configuration.
# /etc/init.d/ipworks.ss stop
6.5.3
Starting and Stopping InnoDB

Start InnoDB on single or legacy configuration.
# /etc/init.d/ipworks.mysql start
Stop InnoDB on single or legacy configuration.
# /etc/init.d/ipworks.mysql stop
6.5.4
Starting and Stopping NDB SQL Node

Start the NDB SQL Node.
# ipwscp
Stop the NDB SQL Node.
# ipwscp
Select MySQL Cluster Node > SQL Node > Stop .
Note:
It is recommended to use the method described in Section 6.5.8 to stop the entire NDB cluster instead of
stopping the nodes individually.
6.5.5
Starting and Stopping NDB Management Node

Start the NDB Management Node.
# ipwscp
Stop the NDB Management Node.
# ipwscp
Select MySQL Cluster Node > Management Node > Stop .
Note:
6.5.6
Starting and Stopping NDB Data Node

Start the NDB Data Node.
# ipwscp
Select MySQL Cluster Node > Data Node > Start .
Stop the NDB Data Node.
12/8/2016 8:24 AM
62 of 62
# ipwscp
Select MySQL Cluster Node > Data Node > Stop .
Note:
In the following scenarios, the user must perform the cluster shutdown to stop the Data Node.
A Data Node is in the starting state.
The NDB Cluster has only one Data Node, or <n> Data Nodes with <n>-1 Data Nodes stopped.
6.5.7
Starting and Stopping Sun Cluster Resource Group
Bring the resource group online on Sun Cluster.

# scswitch -Z -g ipworks_rg &
Bring the resource group offline on Sun Cluster.
# scswitch -F -g ipworks_rg &
6.5.8
Stopping NDB Cluster
Start the IPWorks Control Panel and select the following Control Panel menu options:
# ipwscp
Select MySQL Cluster Node > Management Node > Cluster Shutdown .
Reference List
Ericsson Documents
[1] System Administration Guide, 1543-CSH 109 085 Uen.
[2] Control Panel User Guide, 4/1553-CSH 109 085 Uen.
[3] Solaris Security Hardening for IPWorks 6.0, 1/1551-CSH 109 085 Uen.
[4] Security Hardening for IPWorks 6.0 Application Components, 2/1551-CSH 109 085 Uen.
[5] Solaris Installation Instructions for IPWorks 6.0, 1/1531-CSH 109 085 Uen.
[6] Sun Cluster Installation Instructions for IPWorks 6.0, 2/1531-CSH 109 085 Uen.
[7] SS7 Configuration for IPWorks 6.0, 2/1543-CSH 109 085 Uen.
[8] Installation and Upgrade Tool User Guide, 1/1553-CSH 109 085 Uen.
[9] Command Line Interface (CLI) User Guide, 3/1553-CSH 109 085 Uen.
[10] Web Interface User Guide, 2/1553-CSH 109 085 Uen.
[11] Troubleshooting User Guide, 1/1543-CSH 109 085 Uen.
12/8/2016 8:24 AM

Installation Instructions

Uploaded by

Copyright:

Available Formats

Installation Instructions

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation Instructions

Uploaded by

Copyright:

Available Formats

Installation Instructions

1531-CSH 109 085 Uen A

Installation Instructions for Different Configurations

1.2 Target Groups

A command that must be entered in a Command Line

Command variables, the values of which must be supplied <home_directory>

GUI objects, such as menus, fields, and buttons.

On the File menu, click Exit .

Press Ctrl+X to delete the selected

Text displayed by the system.

System awaiting input

Command and parameter names, program names, path

The files are located in

Ellipsis is used to show an omission in a list or a sequence. &mldr;

Program Prompt Expressions

2.2 System Requirements

Minimum System Requirements

Minimum System Requirements

Sun 500-MHz UltraSPARC processor running Solaris 10, 256 MB RAM

Sun 500-MHz UltraSPARC processor running Solaris 10, 256 MB RAM

Sun 500-MHz UltraSPARC processor running Solaris 10, 256 MB RAM

Sun 500-MHz UltraSPARC processor running Solaris 10, 128 MB RAM

ERH SS7 Manager

Sun 500-MHz UltraSPARC processor running Solaris 10, 128 MB RAM

Sun 500-MHz UltraSPARC processor running Solaris 10, 256 MB RAM

Storage Server, MySQL Database, Tomcat Servlet

Sun 500-MHz UltraSPARC processor running Solaris 10, 512 MB RAM

2.3 Mirror the Local Disk

Partition Example for Single Machine

Only the partition / and swap will be mirrored.

/ (/dev/dsk/c0t0d0s0 ): 1040744 blocks 367878 files

Searching for disks...done

nvalias bootdisk /pci@1c,600000/scsi@2/disk@0,0

-----------------------Finishing Disk Mirroring

2.4 Build Environment

Build Environment for Different Configuration Types

Local Disk Mirror(2) Sun Cluster(3)

(1) Refer to Solaris Installation Instructions, Reference [5].

3.1 IPWorks CD Load Modules

IPWorks 6.0 CD Load Modules

Load Module Load Module Load

Tomcat Server IPWtomcat

ASDNS Monitor IPWasdnsmon asdnsmon Optional

Storage Server IPWss

DHCPv4 Server IPWdhcpv4

DHCPv6 Server IPWdhcpv6

3.2 Installation and Uninstallation

Starting the Tool

Use the following procedure to start the tool:

Installing an IPWorks Release

To install the load modules,

4. Select INSTALL button and press Enter key.

Uninstalling an IPWorks Release

Use the following procedure to uninstall an IPWorks release:

4 Installation Instructions for Different Configurations

4.1 Installation Procedure for Single Configuration

The single machine must have the following system configuration:

IPWorks Modules on a Single Machine

Load Modules for Single Configuration

Load Module Name

* 1. row *

* 1. row *