Академический Документы
Профессиональный Документы
Культура Документы
Operations Guide
For Release 3.1 on Linux
Second Edition
Notice
The information contained in this document is subject to change without
notice.
Hewlett-Packard makes no warranty of any kind with regard to this
material, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. Hewlett-Packard
shall not be liable for any errors contained herein, or for incidental or
consequential damages in connection with the furnishing, performance
or use of this material.
2003 Copyright Hewlett Packard Development Company, L.P.
Reproduction, adaptation or translation without prior written
permission is prohibited, except as allowed under the copyright laws.
Printing History
First Edition
Second Edition
Hewlett-Packard Company
OpenCall Business Unit
38053 GRENOBLE Cedex 9
France
ii
Contents
Preface
1. Preparing for HP OpenCall SS7
Important Safety Precautions for Hardware Installation . . . . . . . . . . . . . . . . . . . . . . .
Physical Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Anti-Static Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Access for Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Authorizing Access for Other Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP OpenCall SS7 Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disk-buffered I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS Administration Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Battery Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Date, Time and Synchronizing Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
First Time Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
18
19
19
20
21
22
22
23
23
23
24
24
25
46
47
49
52
iii
Contents
List of Commands Used in Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Relocatable IP Addresses using PINS . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of PINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HA Functionality of PINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements for PINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PINS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deactivating the PINS Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitoring and Operating PINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Domain Name Server (DNS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and Stopping HP OpenCall SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Automatic Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the Platform Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping HP OpenCall SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Validating the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking from an OS Viewpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking from an HP OpenCall SS7 Viewpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
56
56
56
57
58
59
59
61
63
63
63
63
65
65
65
iv
68
68
69
70
70
78
78
78
79
80
81
81
81
83
83
83
83
83
Contents
5. Validating the Platform
Validating High Availability (HA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the Stack Process States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking that the LANs Are OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Validating SNMP Traps Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking That SNMP Traps Have Been Configured . . . . . . . . . . . . . . . . . . . . . . . . .
Checking That SNMP Traps Are Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Validating the SNMP TCAP Agent Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking That the SNMP TCAP Agent Has Been Configured . . . . . . . . . . . . . . . . .
Checking That the SNMP TCAP Agent Is Active . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
86
86
88
88
88
89
89
89
8. Installing a TSU
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Contents
Stage 1: Installing Cards in the TSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stage 2: Installing the Telecom Signaling Unit in the Server Rack . . . . . . . . . . . . . .
Stage 3: Connecting the TSU to the Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cabling Recommendations for 2-Host Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stage 4: Checking and Configuring the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113
115
117
117
118
120
120
120
122
124
126
129
132
135
139
143
145
149
153
157
159
161
164
167
168
168
168
169
171
173
175
vi
Contents
Restoring the Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSU Configuration: Installing TSU(s) in a New Platform . . . . . . . . . . . . . . . . . . . . .
TSU Configuration: Adding Another TSU to an Existing Platform . . . . . . . . . . . . . .
TSU Configuration: Replacing a TSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSU Configuration: Removing a TSU from a Platform . . . . . . . . . . . . . . . . . . . . . . . .
TSC Configuration: Installing an Additional TSC in a TSU . . . . . . . . . . . . . . . . . . . .
TSC Configuration: Replacing a TSC in a TSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSC Configuration: Removing a TSC from a TSU . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring alarm propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSC Configuration: Installing a TSC in a Host Server . . . . . . . . . . . . . . . . . . . . . . . .
TSC Configuration: Replacing a TSC in a Host Server . . . . . . . . . . . . . . . . . . . . . . . .
TSC Configuration: Removing a TSC from a Host Server. . . . . . . . . . . . . . . . . . . . . .
LAN Configuration: Replacing a LAN Card in a TSU . . . . . . . . . . . . . . . . . . . . . . . . .
Adding and Activating Links on the SS7 Network . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring TSC Chained Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example of alarm propagation configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
183
184
186
189
190
192
196
197
198
199
201
202
203
204
205
207
210
210
211
211
214
218
220
220
220
221
222
222
224
225
228
230
vii
Contents
Stage 3: Connecting the BE Computer to the FE Hosts and Testing the Connections
232
Stage 4: Adding the BE Computer to the Software Configuration and Propagating the
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Stage 5: Updating the HP OpenCall SS7 LAN Configuration, and Propagating the
LAN Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Stage 6: Restarting HP OpenCall SS7 on the Idle Host . . . . . . . . . . . . . . . . . . . . . . 241
Stage 7: Loading the Changes on the Other Host. . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Stage 8: Migrate Your Applications from the FE to the BE Computer . . . . . . . . . . 246
A. Tools Catalog
Graphical Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SS7 Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Line Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Web-based Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Result. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
250
250
251
256
256
258
260
261
262
262
263
266
266
270
271
275
281
283
viii
Contents
D. Configuring the Application Guardian
Configuration Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Global Name for Plug-In Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Naming Convention for Plug-In Server Names . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Application Guardian engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Guardian engine Internal Parameters . . . . . . . . . . . . . . . . . . . . . . . . .
HA Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pre-Defined Plug-Ins (AG_x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Entries in /etc/services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Any Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Plug-In Using the Active/Standby Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Plug-In Implementing PCA Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the User Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Including the Plug-In Processes in the HP OpenCall Environment . . . . . . . . . . . . . .
The Application Guardian engine Run String . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Declaring the Application Guardian engine Process as HA or Not . . . . . . . . . . . . .
296
296
296
297
297
297
298
298
298
298
300
300
300
300
301
302
302
302
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
ix
Contents
Preface
This guide deals with all operational aspects of the HP OpenCall SS7
platform and signaling hardware, from how to install the software and
hardware to configuration, monitoring and maintenance.
Purpose
The guide is intended for operators concerned with the installation,
configuration, monitoring and maintenance of an HP OpenCall SS7
platform and SS7 signaling hardware.
Refer to this guide for help with:
xi
Contents
Chapter 8, Installing a
TSU.
Chapter 9, Maintaining
TSU/TSC Hardware.
xii
Chapter
Contents
Appendix A, Tools
Catalog.
Appendix B, Telecom
Signaling Cards (J3527A
and J3528A).
Appendix C, Telecom
Signaling Units (J3401A),
Appendix D, Configuring
the Application Guardian.
xiii
Associated Documentation
The following guides are on the HP OpenCall SS7 3.1 on Linux
CD-ROM:
Table 1
HP OpenCall SS7
Application Developers
Guide
HP OpenCall SS7
Conformance and
Compliance Statements
HP OpenCall SS7
Glossary
HP OpenCall SS7
Operations Guide
HP OpenCall SS7
Troubleshooting Guide
HP OpenCall SS7
Welcome Guide
xiv
The following guides are available but are not on the HP OpenCall SS7
3.1 on Linux CD-ROM:
Table 2
Other Documents
Title
Contents
xv
xvi
Chapter 1
17
WARNING
Ensure that the hardware you are working with (TSU, SIU or
host server) is disconnected from the power supply during
installation until you are told to connect to a power source.
To avoid personal injury and damage to the product, power to the unit
must remain switched off during installation until it is necessary to
switch the power on. This means that the units power cable and network
cables must remain disconnected until you are instructed to make the
connections. Follow the instructions in the procedures carefully.
This equipment is disconnected from the power supply by removing the
power cord from the power outlet. It is therefore important to locate the
unit close to a power outlet that is easily accessible.
For your safety, never remove the cover of a TSU, SIU or server while the
unit is connected to a power source or to a telecommunication network.
Always replace the cover before switching on the power to the unit. The
terms POWER OFF and POWER ON are used to instruct you when to
switch the power off and on respectively.
WARNING
18
Chapter 1
Anti-Static Precautions
The HP OpenCall SS7 platform contains electrical components which
can be damaged by static electricity. To avoid damage:
CAUTION
Use an anti-static mat and wear a grounding wrist strap attached to the
chassis of the server cabinet when removing and inserting components.
Chapter 1
19
Access Permissions
User
Access Level
root
ocadmin
other user
Configuration Required
none
20
Chapter 1
NOTE
Chapter 1
21
LAN Environment
Inter-host LANs
The two LANs must be configured on separate IP subnets, and they must
be isolated from any external network using bridges or routers:
Figure 1-1
Isolated LANs
Router
Bridge
Host_1
Host_2
NOTE
22
Chapter 1
Router
Bridge
Host_1
Host_2
NOTE
There are no such restrictions on the type of LAN used between Back
End hosts.
Swapping
An operational host must not swap. Main memory must be dimensioned
so that all applications can run using only physical memory.
Disk-buffered I/O
Buffered file I/O cannot be used because it causes the host to stop
occasionally for an undetermined time to flush the buffers to disk.
If an application requires disk-buffered I/O, then it must be run on a
back end (BE), with HP OpenCall SS7 on a front end (FE).
OS Administration Constraints
The following OS administration constraints apply.
Copying Very Large Files
Avoid copying very large files (larger than tens of MBs) as this slows
down the platform and may provoke a switchover.
Chapter 1
23
Battery Backup
Battery backup of the platform is not supported. Architectures must be
configured so that an /etc/shutdown is performed when it is
re-powered.
24
Chapter 1
During the installation, you should refer back to this table as a guide to
the installation tasks.
NOTE
Task
1
Task Description
Install the software. This includes:
References
Refer to Chapter 2, Installing the
HP OpenCall SS7 Software, on
page 27.
Chapter 1
25
Task
4
Task Description
Configure the SS7 hardware.
References
If you have TSU/TSC hardware, refer
to Stage 4: Checking and
Configuring the Hardware on
page 121.
If you have a TSC-in-System
platform, refer to TSC
Configuration: Installing a TSC in a
Host Server on page 199.
26
Chapter 1
Chapter 2
27
Overview
This chapter describes how to install the HP OpenCall SS7 software on a
clean system on which no version of HP OpenCall SS7 has been
previously installed. At the end of the installation, you will have a
platform that uses a pre-defined configuration without SS7 hardware
(you will later reconfigure the platform for full operational use).
NOTE
When installing a new platform from scratch, please refer to First Time
Installation Overview on page 25 for guidance.
NOTE
Installation Task
Section Reference
The section that follows gives the prerequisites for the installation.
28
Chapter 2
Prerequisites
The prerequisites for the installation of HP OpenCall SS7 3.1 on Linux
are as follows:
Skills
To perform the installation, you need a good knowledge of the following
areas:
Documents
During the installation of HP OpenCall SS7, you should have the
following documents at hand:
Hardware
Installation of the host servers of your platform must be complete before
starting any of the software installation procedures.
NOTE
Chapter 2
24 MB for 50 DPCs:
50 DPCs, 100 routes
50 DPCs (Remote SP), 100 Sub-System Numbers (SSNs)
500 Global Title (GT) entries
30
Chapter 2
Software
To install the software, you need the following CDs:
Chapter 2
31
NOTE
Once you have completed the installation described in this section, you
must install the relevant components of the HP OpenCall Enablement
Kit. This is described in Installing HP OpenCall Enablement Kit
Components for Linux on page 35.
NOTE
If you have an HP server on which Linux has been pre-installed for use
with HP OpenCall, you must omit this section and continue to the
installation of the HP OpenCall SS7 software, described in Installing
HP OpenCall SS7 3.1 on Linux on page 37.
32
Chapter 2
For the Red Hat 7.3 distribution, select an installation of type Server.
Disk Partitioning
You must partition your hard disk and assign mount points to the
partitions as shown below:
Mount Point
Partition ID
Type
/boot
Linux
ext2
50
Linux Swap
Swap
1500
(At least twice the RAM size)
Linux
ext2
500
/usr
Linux
ext2
3000
/var
Linux
ext2
1500
/opt
Linux
ext2
300
/home
Linux
ext2
Boot Loader
Host Name
Firewall
User Account
Chapter 2
33
Section
Packages
Application/System
sysstat
Comments
ucd-snmp-utils
Development/Languages
gcc-objc
tclx
Development/System
kernel-source
Optional
Development/Libraries
ucd-snmp-devel
Optional
Development/Tools
ElectricFence
Optional
dmalloc
Optional
System Environment/Daemons
rsh-server
openssh-server
apache
System Environment/Shells
pdksh
Environment/Kernel
kernel-debug
Optional
kernel-bigmem
Optional
nscd
Check the HP OpenCall SS7 3.1 on Linux Release Notes for the
up-to-date list of packages.
Post-Installation
Commands
Once you have completed the Linux installation and rebooted your
machine, you must login as root and then activate rlogin/rsh by
entering the following commands:
#
#
#
#
34
chkconfig
chkconfig
chkconfig
chkconfig
rlogin on
rsh on
ntp on
nscd on
Chapter 2
NOTE
You must follow the procedure in this section only if you have a
supported distribution of Linux installed on your machine in accordance
with the recommendations provided in Installing Linux for
HP OpenCall on page 32.
NOTE
The procedure provided below assumes that you are installing from CD.
For any other method of installation, you are responsible for adapting
the procedure appropriately.
Chapter 2
35
36
Chapter 2
NOTE
Before starting the HP OpenCall SS7 installation, you must have a static
IP address and a static hostname. You must have the following:
Chapter 2
a fully qualified domain name; if you do not have a domain name, use
localdomain
37
38
Chapter 2
localhost
localhost.localdomain
10.20.30.40
opencall
opencall.hp.com
You will have to move the domain name from the second column to
the third column and create a new line with the IP address of the
management LAN for all the systems belonging to the platform (the
HA LAN IP address is not needed)
c. For Red Hat Linux, reboot the system or restart the following
services:
# /etc/init.d/network restart
# /etc/init.d/xinetd restart
Chapter 2
39
# /etc/init.d/nscd restart
d. For Debian, reboot the system or restart the following services:
# /etc/init.d/networking restart
# /etc/init.d/inetd restart
# /etc/init.d/nscd restart
e. Log in as ocadmin.
f. Edit the file /home/ocadmin/.rhosts and replace its contents with
entries of the form
<hostname> ocadmin
for all hosts of your HP OpenCall SS7 platform.
Ensure that all rights for this file are correct, using the command
chmod 600 /home/ocadmin/.rhosts.
Result
The IP network is now configured.
40
Chapter 2
Chapter 2
41
42
Chapter 2
Chapter 2
43
NOTE
44
Chapter 2
Chapter 2
45
46
Chapter 2
Chapter 3
45
Overview
Configuring the HP OpenCall SS7 platform consists of the following:
Modifying the new configuration to use the correct values for your
system.
To perform these tasks, use the cfg* commands. For a list of these
commands, see List of Commands Used in Configuration on page 55.
46
Chapter 3
NOTE
Configuration States
A configuration can be in one of two states:
runninglocated in /etc/opt/OC
Action
Result
Create configuration
Configuration is in saved
state
Modify configuration
Install configuration
Existing running
configuration (if any) moved
to saved statedirectory
named so as not to overwrite
any other saved
configurations
New configuration moved to
running state
Save As configuration
Chapter 3
47
Modify running
configuration
Action
Result
Modify configuration
Modified configuration is in
running state
Save configuration
48
Propagate configuration
Check configuration
Configuration validated.
Chapter 3
This procedure assumes that you have installed the HP OpenCall SS7
software and you have installed (but not configured) the SS7 hardware.
If you are installing a new platform from scratch, please refer to First
Time Installation Overview on page 25 for guidance.
NOTE
WARNING
Chapter 3
49
NOTE
and the system transfers the configuration data from the shared memory
block to the appropriate hardware and software components, ensuring
that the host and the TSU have the same configuration.
If the configuration is invalid, an error message appears describing what
the problem is.
Step 12. Check the links.
50
Chapter 3
ss7TsuStatus -u <tsuId> -C -L
This checks the status of the TSU itself, the TSC(s) it contains and
the links belonging to it.
ss7TscStatus -c <tscId> -L
This checks TSC status.
Chapter 3
51
NOTE
NOTE
This procedure assumes that you have installed the HP OpenCall SS7
software and you have installed (but not configured) the SS7 hardware.
If you are installing a new platform from scratch, please refer to First
Time Installation Overview on page 25 for guidance.
52
Chapter 3
NOTE
Chapter 3
53
54
Chapter 3
cfgCreate
cfgSs7HwCreate
cfgSs7HwUpdate
cfgCheck
cfgInstall
cfgPropagate
cfgMgr
cfgPlatform
cfgSs7Hw
cfgMtp
cfgSccp
cfgTcap
cfgIsup
cfgTup
For the syntax and description of each command, refer to the man page.
NOTE
Chapter 3
55
Description of PINS
PINS manages a single floating IP address and re-maps the address to
one of the four LAN ports on one of the hosts in a 2-host platform. The
floating IP address is used by remote applications communicating with a
local application. This enables the IP network to view the 2-host
platform as a single IP host. PINS monitors the state of the LAN port
associated with the virtual IP address. If the LAN where the virtual IP
address is mapped fails, PINS re-assigns the IP address to another LAN
port on the same front-end host when available (local LAN switch), or on
the other host after a PINS process switchover (remote LAN switch).
PINS provides high availability for an IP address over any LAN except
M3UA and OpenCall LANs (also referred to as HA LANs). PINS uses
ARP (Address Resolution Protocol) to broadcast an update request (of the
Internet address translation tables) to the network neighborhood.
Whereas a local LAN switch is transparent to remote applications, a
remote LAN switch requires the remote application to reconnect to the
platform and to re-initiate any on-going transactions.
HA Functionality of PINS
PINS is an active/standby process managed by the Fault Tolerance
Controller (FTC). Within the HA mechanism supported by the platform,
the behavior of the PINS process includes:
56
Respawning of the PINS process by the FTC when the PINS process
has failed.
Chapter 3
Figure 3-1
Active
Host
Active
Host
Platform
Manager
Active
PINS
Standby
PINS
Application
Application
Private LAN
Floating IP Address
Public LAN
Public LAN
INTERNET
Remote
Application
Chapter 3
57
PINS Configuration
You configure PINS as follows:
Step 1. On the Platform Manager, edit the file /etc/opt/OC/PINS/pins.conf
(for the running configuration) by following the template provided in this
file.
In the section [IP_1], add the following parameters:
LanSwitch = <value>
where <value> can be:
'L' for local LAN switch. (1-host platform only).
'LR' for both local and remote LAN switch. (2-host platform only).
58
Chapter 3
CAUTION
All other parameters and sections are reserved for internal use. Do
not change or remove them.
NOTE
Step 2. To activate the PINS process, you must edit the ftc.conf file in the
directory:
Chapter 3
59
60
Chapter 3
yes
3600
20
211
yes
Chapter 3
hosts
hosts
hosts
hosts
hosts
(GOOD)
(BAD)
61
127.0.0.1
15.128.130.92
15.128.130.93
15.128.130.94
15.128.130.95
62
localhost
foo
foo1.hp.com
foo2
foo3.hp.com
localhost.localdomain local
foo.grenoble.hp.com
foo1
#
#
#
#
#
OK
OK
BAD
OK
BAD
Chapter 3
NOTE
>
Step 2. As root, run the command init q so that the file is re-read and the
changes are taken into account.
NOTE
Chapter 3
The Platform Management tools stop when you stop HP OpenCall SS7.
63
>
Step 2. As root, run the command init q to force init to re-read inittab.
64
Chapter 3
/etc/hosts
~ocadmin/.rhosts
/etc/inittab
Local System
At this level, it checks for consistency within a system.
Global Platform
At this level, it checks for consistency between all the systems in the
platform.
Chapter 3
65
66
Chapter 3
Chapter 4
67
Introduction
NOTE
This chapter assumes that the HP OpenCall SS7 software and hardware
have been installed, and that the platform and hardware have been
configured. If you are installing a new platform from scratch, please refer
to First Time Installation Overview on page 25 for guidance.
The first time you start your SS7 stack, the network configuration file is
empty. Use the SS7 Monitor to create and save your network
configuration. You can also use it to monitor the network.
The SS7 Monitor starts automatically when you start the platform
management tools using ss7MgrStart.
SS7 Monitor can run in two modes:
NOTE
You can quit the SS7 Monitor at any time by pressing (Q)uit.
68
Chapter 4
function
spacebar
backspace
Selecting a choice from the menu displays a window for that choice. Each
window has a corresponding help window, which gives information about
the data requested. All windows have a common format.
You can enter commands using the function keys or a mouse. Commands
and error messages are displayed on the window.
Commands
Refresh rate
Chapter 4
69
NOTE
70
Chapter 4
Linksets/Links
Configure your linksets and then your linksthese are configured
from the MTP window. Before you can configure Links and Linksets
you must install and configure the hardware.
MTP Parameters
SCCP
Refer to the SS7 Monitor on-line help for detailed information about each
parameter. However, the sections below contain guidelines for the
different entities.
Local Point Codes and Aliases
You must set the platform Local Point Code (LPC) and aliases in the SS7
Monitor before doing anything else.
NOTE
Chapter 4
71
The Signaling Link Code (SLC) value for ANSI, ITU-T, and the Chinese
standard must be between 0 and 15. For TTC, the SLC value must be
between 0 and 7.
With a TTC system, you need to define whether the linkset is configured
as A or B. A linkset defined as A accepts all even SLSs. A linkset defined
as B accepts all odd SLSs.
Destinations/
Routes
Before you can configure destinations and routes, at least one route must
be configured for each destination.
Only one destination may be configured as a gateway (STP used to
interconnect national and international networks).
For information on cluster and full point code routing in the ANSI
standard, see Configuring ANSI Routing on page 82.
Example for
Configuring
Destinations and
Routes
Chapter 4
Setting the
concerned
parameter
Use the following table to decide if you need to set the concerned
parameter to y or n.
If you...
SCCP Standard
used at DPC
Use this parameter to tell the LPC what SCCP standard mode is in use at
the DPC. The syntax of how to do this is in the procedures and examples
that follow.
0 (default)
ANSI 88
0 (default)
Chapter 4
73
ANSI 96 - no ISNI
10
Configuring
Global Title
Translations
Table 4-1
Meaning
NP
Numbering Plan
TT
Translation Type
NAI
DPC
SSN
Sub-System Number
Prio
Priority
You can prioritize your global title translations. This means that if one
destination is no longer preferred (for example, it becomes inaccessible)
then the destination with the next highest priority is contacted.
You can prioritize up to ten destinations for one global title translation. 0
has the highest priority and 100 has the lowest priority.
To change the default value, edit the file sys.<className>.sccp.
NOTE
74
Chapter 4
NOTE
Configuring GDI
as a Client
CLIENT;
ha_ss7gdi_1;
ISUP/TUP
This section provides offline and online procedures for configuring
ISUP/TUP applications. It also provides a procedure for changing the
circuit(s) assigned to a running ISUP application (ISUP CIC-based
distribution).
Configuring ISUP/TUP Applications Offline To configure an
ISUP/TUP application offline, use the cfgIsup or the cfgTup command
with the -static option.
Chapter 4
75
Step 2. Identify the application you want to update (for example, using the ps
command) and the host on which it is running. Note that you can have
several instances of the same application running on the same platform,
but that only one of these instances is the primary application. If
possible, identify the primary application and carry out steps 4 and 5
below on the host running the primary.
NOTE
If you are not able to identify the primary, choose any application
instance and proceed as below.
Step 3. Start nettl (using startnettl as root) on the host running the
application, and open a log window (using wlog).
Step 4. On the host running the application, start the ss7IsupReload or
ss7TupReload command, as appropriate, giving the application
identifier as an argument:
For ISUP
prompt$ ss7IsupReload -appID <appID>
For TUP
prompt$ ss7TupReload -appID <appID>
76
Chapter 4
Primary application
Only the primary application can be configured dynamically with the
ss7IsupReload command
Secondary application
A secondary application cannot be configured dynamically with the
ss7IsupReload command. If attempted, an error message is
displayed.
Chapter 4
77
78
Chapter 4
Chapter 4
79
Loading a
Non-Default
Configuration
NOTE
80
Chapter 4
NOTE
Chapter 4
81
Cluster Routing
The configuration procedure is different depending on whether the
network is already configured.
Configuring Cluster Routing in an Existing SS7 Network
Step 1. Checkpoint your configuration using the checkpointing tool.
Step 2. Run the cfgMtp command with the -pcRoute option set to cluster.
Step 3. Stop and restart the stack on both hosts. The checkpointed configuration
is loaded automatically.
Some DPC creations are refused because when Full Point Code routing is
disabled, there can be only 1 DPC (N.C.0) in a remote cluster DPC. This
does not matter as DPC N.C.0 can stand for any DPC. You dont have to
add anything to the configuration.
If your Full Point Code routing configuration does not have a DPC N.C.0
in the remote clusters (for example, if you have N.C.1, N.C.2 and N.C.3)
all DPCs are refused and you have to reconfigure N.C.0.
Step 4. Checkpoint your configuration again, then propagate it if necessary.
Configuring Cluster Routing with no Existing SS7 Network
Step 1. Run the cfgMtp command with the -pcRoute option set to cluster.
Step 2. Use the SS7 Monitor, to configure your SS7 network. In remote clusters
only the N.C.0 DPC is allowed.
82
Chapter 4
Chapter 4
83
Prerequisite
Step 1. Connect the TSC cables to the SS7 network.
84
Chapter 4
Chapter 4
85
86
Chapter 4
Chapter 5
85
ACTIVE
BOOTING
DOWN
SYNCHRONIZING
UNKNOWN
86
Chapter 5
Dual LANs
Check that neither SS7 stack goes down and that no split brain
symptom occurs. For more information on the split brain symptom,
see the HP Opencall SS7 Troubleshooting Guide.
Chapter 5
87
88
Chapter 5
Chapter 5
89
90
Chapter 5
Chapter 6
91
HP OpenCall SS7 must be running before you can start the platform
management tools.
92
Chapter 6
Process States
State
Meaning
Active
Degraded
HotStby
Switching
Synchro
Stopping
ColdStby
Booting
Process is rebooting
Down
Process is down
Unknown
Chapter 6
93
94
Chapter 6
Chapter 6
Hardware State
MTP
SCCP
TCAP
GDI
95
Monitoring MTP
If you choose MTP from the main menu, you can choose to monitor one of
the following:
MTP
Destinations / Routes
Links / Linksets
NOTE
Search
Test
Use the (T)est function (type T) to test the route in the TTC standard.
The local host sends a SRT and expects the return of an SRA. The return
notification will display, for example:
*** Routing test successful on route DPC, RPC ***
or
***Error: Routing test failed on route DPC, RPC ***
This testing function is not available for the ITU-T nor ANSI standards.
If you try to test these standards, you will see an error message.
You cannot access the route while it is being tested.
96
Chapter 6
Link Inhibit
The link inhibit command works for ANSI and ITU-T stacks, but is not in
the TTC standard. If you use TTC, you will see an error
(ILLEGAL_OA_OPERATION) if you try to inhibit a link.
Search
If the Signaling Unit must pass from STANDBY to ACTIVE in the case
of a HP OC SS7 host switchover, the links are not impacted and remain
ACTIVE.
NOTE
Chapter 6
97
Configuring GDI
The GDI configuration screen allows you to configure the remote hosts
which are authorized to connect to a particular HP OpenCall SS7 stack
using GDI. Connection attempts from a non-authorized hosts are
refused.
A GDI remote host is identified by its DGPC (Distant GDI Point Code)
and by one or two IP addresses. The DGPC is a logical local identifier.
The remote IP address and the corresponding LAN must be configured
on the remote client.
NOTE
To connect to a the TCAP application, you must use SSN 256. SSN 256 is
reserved in the SS7 stack for GDI. You cannot manually change this
using the SCCP configuration menu.
MTP
Linkset
Link
SCCP
TCAP
The statistical data for the selected entity is updated every few seconds.
98
Chapter 6
TCAP
From this window you can see the TCAP statistics for the local point
code.
GDI
From this window you can see the GDI statistics for the local point code.
Chapter 6
99
Viewing Logs
When working with HP OpenCall SS7, it is often useful to display the
systems logs. This lets you see immediately that all is well, or take
appropriate action if there is a problem.
To view logs alone make sure nettl is running, then enter the wlog
command.
To include Cause and Action in the display, if these are available, use the
wlog -extended command.
100
Chapter 6
Chapter 6
101
102
Chapter 6
Chapter 6
103
104
Chapter 6
Chapter 7
105
The features you can access when using HP OpenCall SS7 depend on
your license. When you first configure HP OpenCall SS7, you also
configure the license. Subsequently, it is possible to update your license
to access more functionality.
This chapter provides offline and online procedures on how to enter or
upgrade the license on an HP OpenCall SS7 3.1 platform. Below these
procedures is a description of how to display the platforms current
license information.
106
Chapter 7
Offline Procedure
This procedure allows you to enter your platform license or upgrade your
platform license offline (with no traffic).
Step 1. Save a back-up of the current configuration using the cfgMgr -copy
command.
Step 2. Display your current license using the cfgPlatform -view -license
command. Note this license keyword for future reference. You will need it
if you wish to perform a rollback.
Step 3. Chose one of substeps below, depending on the changes you wish to
make.
a. If you are installing or reinstalling your platform:
Execute the cfgPlatform -license command with the -install
and static options.
b. If you are upgrading your platform:
Execute the cfgPlatform -license command with the -upgrade
and static options.
The system displays the new license information and generates a new
platform license keyword. The new keyword incorporates all the
additional features and capacity with the previous features and
capacity.
Make a note of the updated keyword and keep it for future reference.
Step 4. Propagate the new license to all the systems in your platform using the
cfgPropagate command.
Chapter 7
107
Online Procedure
This procedure allows you to upgrade your platform license online (with
traffic). You can only carry out this upgrade procedure on a running
stack.
Step 1. Save a back-up of the current configuration using the cfgMgr -copy
command.
Step 2. Display your current license using the cfgPlatform -view -license
command. Note this license keyword for future reference. You will need it
if you wish to perform a rollback.
Step 3. Upgrade your license.
Execute the cfgPlatform -license command with the -upgrade and
dynamic options.
The system displays the new license information and generates a new
platform license keyword. The new keyword incorporates all the
additional features and capacity with the previous features and capacity.
At this stage, the license configuration files are not updated.
Step 4. Note the updated keyword and keep it for future reference.
Step 5. Load and save the configuration changes using the command
ss7License -reload
The license configuration files are now overwritten and a platform
restart will retain the new configuration.
108
Chapter 7
Chapter 7
DISABLED
DISABLED
ENABLED
ENABLED
DISABLED
DISABLED
109
110
Chapter 7
Installing a TSU
This chapter describes how to install a Telecom Signaling Unit (TSU)
and its associated Telecom Signaling Cards (TSCs).
Chapter 8
111
Installing a TSU
Overview
Overview
The installation procedures in this chapter are concerned with adding a
Telecom Signaling Unit (TSU) to a new or existing (running) platform.
You can add a new TSU to a running platform without disturbing the
traffic.
If you wish to perform maintenance on an existing Telecom Signaling
Unit, refer to Chapter 9, Maintaining TSU/TSC Hardware.
WARNING
112
Description
Section Reference
Chapter 8
Installing a TSU
Overview
NOTE
Chapter 8
113
Installing a TSU
Stage 1: Installing Cards in the TSU
When adding a new Telecom Signaling Unit to your platform, you must
first install the Telecom Signaling Cards and additional LAN card (if
required) into your unit. Note that the PCI slots available for the
different types of cards are as follows:
Card Type
PCI Slots
V.35 TSC
1 to 5
E1/T1 TSC
1, 3 and 5
LAN Card
L1
NOTE
NOTE
Slot L0 in the TSU is occupied by the system CPU card, which also
provides a LAN connection to the host. This card is supplied with the
TSU and cannot be removed. You only need to install an additional LAN
card (in slot L1) if the TSU is to be connected to the hosts in a 2-host
platform.
If you need to add an additional LAN card to your host server(s) in order
to connect to the new TSU, refer to Replacing, Removing or Adding a
Hardware Component in the Host on page 124.
114
Chapter 8
Installing a TSU
Stage 1: Installing Cards in the TSU
WARNING
Chapter 8
115
Installing a TSU
Stage 2: Installing the Telecom Signaling Unit in the Server Rack
NOTE
116
Chapter 8
Installing a TSU
Stage 2: Installing the Telecom Signaling Unit in the Server Rack
To install your TSU in a server cabinet, follow the steps below:
Step 1. Install the ear brackets and handles on the front of the TSU.
Step 2. Install the cable guide for the TSU at the back of the unit.
Step 3. Install the sliding rails. The rails that you need depend on the type of
server rack in which the TSU is to be installed. For a Rosebowl I rack,
you need the rails with HP Part Number J3401-80202. For a Rosebowl II
or Seismic rack, you need the rails with HP Part Number J3401-80203.
a. Attach the captive nuts to the holes on each side of the server cabinet
at the height that you wish to install the TSU.
b. Screw the rail guides to the captive nuts in the cabinet, so that the
hole is at the rear of the cabinet (or at the front of the cabinet if you
have a CO cabinet). Install the rail guides with the lip side pointing
inwards. Note that for the rails with HP Part Number J3401-80203,
you must put the wedge and washer between the rails and the server
cabinet (not shown in Figure 8-1).
c. Attach the rails to each side of the TSU, with the lip facing away from
the box and with the stop at the rear of the box. To do this, align the
four holes on the rail with the four holes along the side of the TSU
and secure the rails to the box using the small screws provided.
Step 4. Slide the rails on the TSU into the rail guides in the cabinet and push
the TSU into the cabinet until the TSU is in place.
Step 5. Install the TSUs optional connection panel in the cabinet:
a. Check that you have the correct connection panel:
b. Secure the connection panel to the cabinet at the same level as the
TSU.
Chapter 8
117
Installing a TSU
Stage 3: Connecting the TSU to the Platform
NOTE
This does NOT involve connecting the TSCs to the signaling network
(which must be left as the last task before the TSU is put into service).
NOTE
For full details of the TSC connectors and cables required, refer to TSC
Connectors and Cables on page 266.
Connection Procedures
In order to work through the connection procedures in this section, you
may need to refer to the diagram in Figure 8-2 below. This shows the
connectors on the rear panel of the TSU. These include the TSC
connectors (for connection to the signaling network), the LAN card
connectors (for host connections), as well as the power supply connectors.
Figure 8-2
118
Chapter 8
Installing a TSU
Stage 3: Connecting the TSU to the Platform
NOTE
All the steps described below apply to both 1-host and 2-host platforms,
unless marked as 2-host only.
Connect to the
Host(s)
Step 1. Using the 1.5 m LAN cable (HP Part Number: 5063-1358), connect TSU
slot L0 to the platform host contained in the same server cabinet as the
TSU.
Step 2. 2-host only: Using the 6.5 m LAN cable (HP Part Number: 5063-1359),
connect TSU slot L1 to the other platform host. Refer to Cabling
Recommendations for 2-Host Platforms on page 120 for advice on
making host connections in a 2-host platform.
Step 3. Label the cables, stating what they are (LAN) and where they connect to
(L0, L1).
Connect the TSC
Cables
The TSC cables connect the TSCs to the signaling network. At this stage,
you can connect the TSC cables at the platform end but must NOT
connect them at the network end. To do this:
Step 1. Connect the cables to the TSU. If you are using the optional connection
panel, connect the network end of the cables to the rear of the connection
panel.
Step 2. Label the cables, stating what they are (E1, T1, V.35) and where they
connect to (TSC1, TSC2 and so on).
CAUTION
Connect to the
Power Supply
Chapter 8
119
Installing a TSU
Stage 3: Connecting the TSU to the Platform
The HSC/PCI LAN cards use the same slots in the two systems; that
is, they have the same hardware path.
The HSC/PCI LAN ports connected to the same TSU have the same
hardware path on the two hosts.
On each system, half of the TSUs are connected to the LAN port
provided by the SS7 interface controller card of the TSU. The other
half are provided by the LAN port on the add-on LAN card.
When these recommendations are followed, the TSU Ids are set in the
order that the LANs are discovered by the auto-discovery function.
Figure 8-3
120
Chapter 8
Installing a TSU
Stage 4: Checking and Configuring the Hardware
At this stage, your TSU should be connected to the platform host(s) and
be powered on. The TSC cables should NOT yet be connected to the
signaling network.
Chapter 8
121
Installing a TSU
Stage 4: Checking and Configuring the Hardware
122
Chapter 8
Maintaining TSU/TSC
Hardware
This chapter details the maintenance procedures that you may need to
perform on your TSU or your TSC-in-system server.
Chapter 9
121
Overview
The maintenance procedures provided in this chapter are listed in the
table below along with references to the relevant sections.
Description
Section Reference
122
Chapter 9
Description
Section Reference
NOTE
Some of the above procedures refer to other procedures. For easy access,
these sub-procedures have been collected together in the last section of
this chapter, Common TSU/TSC Procedures on page 168.
WARNING
Chapter 9
123
NOTE
NOTE
Although this procedure does not disturb the traffic on a 2-host platform,
it stops all the traffic of a 1-host platform.
Chapter 9
For a 2-host platform, check the synchronization of the stacks using the
ocftstatus command on any host.
Results
All hardware elements are active, and the stack(s) are up. On 2-host
platform, both hosts are active.
Rollback
Chapter 9
125
A faulty fan should be replaced as soon as possible. The TSU can operate
without one fan, but to maximize the life of the TSU you must replace
the faulty fan without delay.
NOTE
You can replace a fan without powering off the TSU or removing the TSU
from the server cabinet.
Before you can replace a fan, you need to remove the frontplate of the
TSU. Figure 9-1 and Figure 9-2 below show the front view of the TSU
with and without the frontplate, respectively.
Figure 9-1
126
Chapter 9
NOTE
Chapter 9
Make sure that you use a replacement fan of the correct size (60 mm or
80 mm), and that you install it the right way up and the right way around
(with the arrow at the front).
127
128
Chapter 9
CAUTION
CAUTION
The following procedure involves disconnecting the TSU from the SS7
network. The HP OpenCall SS7 platform will therefore lose network
links. However, depending on the platform, it may be possible for the
traffic that uses these links to be redirected via other links. Do this in
consultation with the personnel responsible for operating the platform.
WARNING
Chapter 9
129
Chapter 9
Chapter 9
Perform the above procedure again to reinstall the old power supply.
131
CAUTION
CAUTION
The following procedure involves disconnecting the TSU from the SS7
network. The HP OpenCall SS7 platform will therefore lose network
links. However, depending on the platform, it may be possible for the
traffic that uses these links to be redirected via other links. Do this in
consultation with the personnel responsible for operating the platform.
WARNING
132
Chapter 9
Chapter 9
133
134
Perform the above procedure again to reinstall the old power supply.
Chapter 9
CAUTION
CAUTION
The following procedure involves disconnecting the TSU from the SS7
network. The HP OpenCall SS7 platform will therefore lose network
links. However, depending on the platform, it may be possible for the
traffic that uses these links to be redirected via other links. Do this in
consultation with the personnel responsible for operating the platform.
WARNING
The steps of this procedure apply to both 1-host and 2-host platforms,
unless otherwise stated.
You should be logged in as ocadmin on the active host.
Step 1. If the platform has more than one TSU, divert the traffic from the TSU
that you are going to work on. To do this, refer to the Diverting Traffic
on page 182.
If you have a 1-host platform with only one TSU, stop HP OpenCall SS7
by running the ss7Stop -all command. As a result, all traffic will be
stopped.
Step 2. Take anti-static precautions by wearing the grounding wrist strap.
Step 3. Power off the TSU.
Chapter 9
135
136
Chapter 9
If you are not satisfied with the new configuration, perform the rollback
steps now.
Step 20. If you have a 2-host platform, propagate the updated configuration. To do
this, carry out one of the following:
Rollback
Chapter 9
137
138
Chapter 9
NOTE
Slot L0 in the TSU is occupied by the system CPU card, which also
provides a host LAN connection. This card is supplied with the TSU and
cannot be removed. If there is a problem with this card, call your HP
representative.
CAUTION
The following procedure involves disconnecting the TSU from the SS7
network. The HP OpenCall SS7 platform will therefore lose network
links. However, depending on the platform, it may be possible for the
traffic that uses these links to be redirected via other links. Do this in
consultation with the personnel responsible for operating the platform.
WARNING
Chapter 9
139
140
Chapter 9
Chapter 9
141
Step 15. Reconnect the TSC cables to the rear panel of the TSU in order to
reconnect to the signaling network.
Step 16. If you have diverted the traffic from this TSU, you can now restore the
traffic to the TSU. To do this, refer to Restoring the Traffic on page 183.
If you have stopped HP OpenCall SS7 on the hosts, you can now restart
it. To do this, run the ss7Start command.
142
Chapter 9
CAUTION
The following procedure involves disconnecting the TSU from the SS7
network. The HP OpenCall SS7 platform will therefore lose network
links. However, depending on the platform, it may be possible for the
traffic that uses these links to be redirected via other links. Do this in
consultation with the personnel responsible for operating the platform.
WARNING
Chapter 9
143
144
Chapter 9
CAUTION
The following procedure involves disconnecting the TSU from the SS7
network. The HP OpenCall SS7 platform will therefore lose network
links. However, depending on the platform, it may be possible for the
traffic that uses these links to be redirected via other links. Do this in
consultation with the personnel responsible for operating the platform.
WARNING
Chapter 9
145
146
Chapter 9
Chapter 9
147
Step 17. If you have diverted the traffic from this TSU, you can now restore the
traffic to the TSU. Refer to Restoring the Traffic on page 183.
If you have stopped HP OpenCall SS7 on the hosts, you can now restart
it. To do this, run the ss7Start command.
148
Chapter 9
CAUTION
The following procedure involves disconnecting the TSU from the SS7
network. The HP OpenCall SS7 platform will therefore lose network
links. However, depending on the platform, it may be possible for the
traffic that uses these links to be redirected via other links. Do this in
consultation with the personnel responsible for operating the platform.
WARNING
149
150
Chapter 9
Chapter 9
151
152
Chapter 9
Replacing a TSU
This section describes how to replace a faulty TSU. It is possible to
replace a faulty TSU on a running platform without disturbing the
traffic.
CAUTION
WARNING
Chapter 9
153
154
Chapter 9
Chapter 9
155
156
Chapter 9
CAUTION
The following procedure involves disconnecting the TSU from the SS7
network. The HP OpenCall SS7 platform will therefore lose network
links. However, depending on the platform, it may be possible for the
traffic that uses these links to be redirected via other links. Do this in
consultation with the personnel responsible for operating the platform.
WARNING
All software steps in this procedure must be performed on the same host,
on the running configuration.
You should be logged onto the active host as ocadmin.
Step 1. If the platform has more than one TSU, divert the traffic from the TSU
that you are going to remove. To do this, refer to Diverting Traffic on
page 182.
If you have a 1-host platform with only one TSU, stop HP OpenCall SS7
by running the ss7Stop -all command. As a result, all traffic will be
stopped.
Step 2. Remove the link(s) associated with the TSU from the stack. In the SS7
Monitor screen, select
Configure Entities|Config MTP|Config lk/lkset
and remove the link(s) you have diverted the traffic from.
Press "C" to checkpoint the modifications.
Write down the linkIds, SLCs and destination point codes of the links
you have removed.
Chapter 9
157
158
Chapter 9
CAUTION
CAUTION
During this procedure, it is necessary to shut down the platform. You will
therefore disturb the traffic handled by the platform.
WARNING
Except for Step 3, which must be done as root, all the following steps
should be done while logged in as ocadmin.
Step 1. Stop HP OpenCall SS7. To do this, run the ss7Stop -all command.
Step 2. Take anti-static precautions by wearing the grounding wrist strap.
Step 3. As root, shutdown host A.
Step 4. Power off the host server.
Step 5. Remove the cover of the host server.
Step 6. Install the new TSC in the host server. Refer to your server
documentation for help with this.
Step 7. Replace the cover of the host server.
Step 8. Power on the host server and wait until it has booted.
Chapter 9
159
160
Chapter 9
CAUTION
CAUTION
During this procedure, it is necessary to shut down the platform. You will
therefore disturb the traffic handled by the platform.
WARNING
Except for Step 3, which must be done as root, all the following steps
should be done while logged in as ocadmin.
Step 1. Stop HP OpenCall SS7. To do this, run the ss7Stop -all command.
Step 2. Take anti-static precautions by wearing the grounding wrist strap.
Step 3. As root, shutdown host A.
Step 4. Power off the host server.
Step 5. Remove the network cables from the TSC that is to be replaced and
disconnect the TSC cables at the network end.
Step 6. Remove the cover of the host server.
Step 7. Remove the old TSC and install the new card in its place. Refer to your
server documentation for help with this.
Step 8. Replace the cover of the host server.
Chapter 9
161
162
Chapter 9
Chapter 9
163
CAUTION
CAUTION
During this procedure, it is necessary to shut down the platform. You will
therefore interrupt the traffic handled by the platform.
WARNING
Except for Step 4, which must be done as root, all the following steps
should be done while logged in as ocadmin.
Step 1. If there is traffic on the TSC that is to be removed, divert the traffic from
this TSC. To do this, refer to Diverting Traffic on page 182.
If there is no traffic on the TSC that is to be removed, simply deactivate
the links associated with this TSC. To do this, run SS7 Monitor, select
Monitor Entities|Monit MTP|Monit lk/lkset and follow the
instructions to deactivate the links.
Step 2. Remove the link(s) associated with the TSC (that you want to remove)
from the stack, as follows:
a. Execute the cfgSs7Hw -view command to display the configuration
and find the links to be removed.
b. In the SS7 Monitor screen, follow the path
Configure Entities|Config MTP|Config lk/lkset
164
Chapter 9
then find the SLC corresponding to the link identifiers and remove
the link(s).
Press C to checkpoint the modifications.
Make a note of the link identifiers, the SLCs and the DPCs of the
links you have removed.
Step 3. Stop HP OpenCall SS7 by running the ss7Stop -all command.
Step 4. As root, shutdown host A.
Step 5. Power off the host server.
Step 6. Take anti-static precautions by wearing the grounding wrist strap.
Step 7. Remove the TSC cables from all TSCs and disconnect the cables at the
network end.
Step 8. Remove the cover of the host server.
Step 9. Remove the TSC from the host server. Refer to your server
documentation for help with this.
Step 10. Replace the cover of the host server.
Step 11. Power on the host server and wait until it has booted.
Step 12. Reconnect the TSC cables to the remaining TSCs, but do NOT connect
them at the network end yet.
Step 13. Use the command ss7TscPing -v to check that the TSC is no longer
present.
Step 14. Configure the hardware. To do this, refer to TSC Configuration:
Removing a TSC from a Host Server on page 203. During this procedure
you will reconnect the TSC cables to the network.
Rollback
Chapter 9
165
166
Chapter 9
NOTE
CAUTION
During this procedure, the traffic handled by the TSC will be disturbed.
You can, however, avoid disruption of traffic by diverting this traffic to
another TSC.
Step 1. Divert the traffic from the TSC that you are going to work on. To do this,
refer to Diverting Traffic on page 182.
Step 2. Remove the old 4-port TSC cable.
Step 3. Connect the new 4-port TSC cable to the TSC and to the network.
Step 4. You can now restore the traffic to the TSC. To do this, refer to Restoring
the Traffic on page 183.
Rollback
Chapter 9
167
168
Chapter 9
Chapter 9
169
170
Chapter 9
NOTE
Card Type
PCI Slots
V.35 TSC
1 to 5
E1/T1 TSC
1, 3 and 5
LAN Card
L1
If you wish to add a card to your TSU, you should begin the installation
by referring to the section in this guide for adding the relevant card type.
If you are installing TSCs and/or a LAN card in a new TSU, refer to
Stage 1: Installing Cards in the TSU on page 114.
If you are adding or replacing a TSC in an existing TSU, refer to
Replacing a TSC in a TSU on page 145 or Installing an Additional
TSC in a TSU on page 143.
If you are adding or replacing a LAN card in an existing TSU, refer to
Replacing a LAN Card in a TSU on page 139.
CAUTION
Chapter 9
171
Step 2. Insert the card as follows (also refer to Figure 9-6 below)
a. Remove the slot protector from the relevant slot on the card cage
backplane.
b. Slide the card into the slot. Press firmly on both ends of the card at
the same time to make sure it is firmly seated in the connector.
c. Screw the card bracket to the cage.
172
Chapter 9
NOTE
Chapter 9
PCI Slots
V.35 TSC
1 to 5
E1/T1 TSC
1, 3 and 5
LAN Card
L1
If you wish to remove a card from your TSU, you should begin by
referring to the section in this guide for removing the relevant card type.
173
CAUTION
174
Chapter 9
Step 3. If you are going to leave the vacated slot empty, replace the card holder
bracket(s):
a. Slide the bracket into the keyhole standoff in the chassis.
b. Secure the bracket to the card cage by replacing and tightening the
screw on the top of the bracket.
Checking LEDs
To check that installed hardware is functioning correctly, refer to the
LEDs. These are as follows:
Chapter 9
TSU LEDs
175
TSC LEDs
These appear on the end-plate of each TSC and can be viewed on the
rear panel of the TSU. They indicate the status of the TSC and are
fully described below.
Once you have powered on the TSU, use the above LEDs to determine
whether each of the individual components (TSU, TSCs and LAN cards)
is operating correctly. The LEDs are interpreted as described below.
The TSU features the following four LEDs which appear on both the
front and back of the unit:
TSU LEDs
Power
Status
Fault
Fan Fail
Table 9-1 below indicates the meanings of these LEDs in their different
states.
Table 9-1
LED
ACTIVE TSU
without
configuration
ACTIVE
TSU
Fan
failed
Power
On
On
On
On
Status
Off
On
On
Off
Fault
Flashing
On
Off
On
Fan Fail
Off
Off
Off
Flashing
176
Chapter 9
NOTE
Power - ON
Status - ON
Fault - ON
If the TSU is powered on, but not configured, the Fault LED should be
ON.
If the Status and Fault LEDs do not appear in the above ON-ON
combination, their exact behavior can be used to determine the current
operational state of the TSU. Table 9-2 below details how to interpret
this behavior.
Table 9-2
LED
Fault
TSU State
Meaning
Status
Off
Off
Not responding
Off
Flashing slowly
Not responding
Off
Flashing rapidly
Not responding
Off
On
Active
TSU is operational
On
Off
Not responding
Flashing slowly
or rapidly
Off
Not responding
No firmware on TSU
Flashing slowly
Flashing slowly
Not responding
Chapter 9
177
LED
Fault
Flashing slowly
TSC LEDs
TSU State
Meaning
Degraded
Status
+
On
Each of the TSCs features a number of LEDs on its end-plate: V.35 TSCs
each have two LEDs and E1/T1 TSCs each have six LEDs. These are as
follows:
L1 LED (all TSC types): Indicates the status of the PCI base card.
L2 LED (E1/T1 TSC only): Indicates the status of the TSC itself.
The positions of these LEDs are indicated in Figure B-1 on page 262
(V.35 TSC) and Figure B-2 on page 264 (E1/T1 TSC).
Table 9-3 below indicates the meanings of these LEDs in their different
states.
Table 9-3
LED
Status
L1
On
Reset TSC
Reset TSC
L2
On
TSC active
N/A
Amber
TSC failed
N/A
On
Cable connected
and at least one
link is configured
N/A
P0/P1/P2/P3
178
Chapter 9
Table 9-4 below indicates the meanings of these LEDs in their different
states.
Table 9-4
LED
Meaning
On
Off
On or
flashing
Off
On
Off
LNK
ACT
100
It is therefore important to check that the LNK LED is ON and that the
ACT LED flashes occasionally. If this is not the case, consult the
troubleshooting lists below.
The LNK LED does not light:
Check all connections at the card and the host LAN card.
Make sure the host LAN card has its configuration set to
autoregulate the speed.
Make sure that you have the correct cabling, as supplied with the
TSU, between the card and the host.
Chapter 9
179
180
Chapter 9
10
Chapter 10
181
Diverting Traffic
Many of the procedures described in Chapter 9, Maintaining TSU/TSC
Hardware, require you to divert the traffic before starting. This
procedure describes how to do so.
Use these procedures when the traffic is low as performance is affected,
although the connection is maintained. Otherwise, you will concentrate
too much traffic on the remaining links and they will become congested.
For example, if you plan to deactivate half of your links, they should be
loaded at less than 40%. You should also take care not to deactivate too
many links at a time as the diverted traffic may overload the remaining
links, even if they were initially loaded at less than 40%.
CAUTION
If you stop a hardware element that handles all your SS7 links on the
platform, you will lose your traffic.
Actions
182
Chapter 10
NOTE
Checks
Step 1. Check that there is no congestion on the other links.
Step 2. Check that no DPCs are out of service. If you deactivate all the links to a
DPC, it will go of service and all traffic to it will be lost.
Result
All the links corresponding to the hardware elements you need to stop
are now deactivated. The traffic that used to be supported by them is
shared among the remaining links
Chapter 10
183
NOTE
The steps below should be carried out on both 1-host and 2-host
platforms.
All steps of this procedure must be carried out on the active host, on a
saved configuration.
You should log in as ocadmin.
Step 1. Select the saved configuration that will be modified.
Use the cfgMgr -view command to get a list of saved configurations.
Step 2. Create the configuration using the cfgSs7HwCreate command and
specify the path of the hardware file for the selected configuration.
Step 3. Configure the TSC using the cfgSs7Hw command. The relevant options
of this command are given below.
1. Configure the TSCs using the -modify -tsc option. All parameters
of the new TSCs are automatically detected or set by default, except
the owner parameter when there is more than one stack. Configure
this parameter now. If necessary, change the other parameters (for
example, clockSource, coding, etc.).
184
Chapter 10
Chapter 10
185
NOTE
The steps below should be carried out on both 1-host and 2-host
platforms.
All steps of this procedure must be carried out on the active host, on the
running configuration.
You should log in as ocadmin.
Step 1. Update the running configuration using the cfgSs7HwUpdate command
(which performs a hardware auto-discovery of the new hardware
elements).
Step 2. Configure the TSCs discovered in the new TSU using the cfgSs7Hw
command in update mode. The relevant options of this command are
given below.
1. Configure the TSCs using the -modify -tsc option. All parameters
of the new TSCs are automatically detected or set by default, except
the owner parameter when there is more than one stack. Configure
this parameter now. If necessary, change the other parameters (for
example, clockSource, coding, etc.).
2. Create and configure the links using the -add -link options.
186
Chapter 10
If you are not satisfied with the new configuration, perform the rollback
steps now. Refer to the Rollback section below.
Step 9. If you have a 2-host platform, propagate the updated configuration. To do
this, carry out one of the following:
Rollback
Chapter 10
188
Chapter 10
The steps below should be carried out on both 1-host and 2-host
platforms.
NOTE
All steps of this procedure must be carried out on the active host, on the
running configuration.
You should log in as ocadmin.
Step 1. Check the state of the links using the SS7 Monitor. To do this, follow the
path Monitor Entities|Monit MTP|Monit lk/lkset.
The links should be active.
Step 2. If you are satisfied with this new configuration, make it the running
configuration by carrying out one of the following:
If you are not satisfied with the new configuration, perform the rollback
steps now. Refer to the Rollback in the section Replacing a TSU on
page 153.
Step 3. If you have a 2-host platform, propagate the updated configuration. To do
this, carry out one of the following:
Chapter 10
189
NOTE
The steps below should be carried out on both 1-host and 2-host
platforms. You should be logged in as ocadmin on the active host.
190
Chapter 10
Chapter 10
191
NOTE
The steps below should be carried out on both 1-host and 2-host
platforms.
192
Chapter 10
If you are not satisfied with the new configuration, perform the rollback
steps now. Refer to the Rollback below.
Step 5. If you have a 2-host platform, propagate the updated configuration. To do
this, carry out one of the following:
Rollback
Step 1. Deactivate the added link(s) on the stack. In the SS7 Monitor screen,
select Monitor Entities|Monit MTP|Monit lk/lkset and deactivate
the link(s).
Chapter 10
193
Step 4. If the platform has more than one TSU, divert the traffic from the TSU
that you are going to work on. To do this, refer to Diverting Traffic on
page 182.
If you have a 1-host platform with only one TSU, stop HP OpenCall SS7
by running the ss7Stop -all command. As a result, all traffic will be
stopped.
Step 5. Take anti-static precautions by wearing the grounding wrist strap.
Step 6. Power off the TSU.
Step 7. Remove all cables from the rear panel of the TSU and disconnect the
TSC cables at the network end.
Step 8. Slide the TSU out on its rails until it blocks.
Step 9. Remove the cover of the TSU, as described in Removing and Replacing
the TSU Cover on page 168.
Step 10. Remove the card cage from the TSU, as described in Removing and
Replacing the Card Cage on page 170.
Step 11. Remove the new TSC. Refer to Removing a Card from a TSU on
page 173 for help with this.
Note that you may need to remove other TSCs in order to gain access to
the relevant slot. If this is the case, do not forget to replace them!
Step 12. Re-insert the card cage into the TSU, as described in Removing and
Replacing the Card Cage on page 170.
Step 13. Replace the cover of the TSU, as described in Removing and Replacing
the TSU Cover on page 168.
Step 14. Slide the TSU on its rails back into the cabinet.
194
Chapter 10
Chapter 10
195
NOTE
The steps below should be carried out on both 1-host and 2-host
platforms. You should be logged in as ocadmin on the active host.
Step 1. Check the state of the links using the SS7 Monitor. To do this, follow the
path Monitor Entities|Monit MTP|Monit lk/lkset.
The links should be active.
Step 2. If you are satisfied with the new configuration, make it the running
configuration by carrying out one of the following:
If you are not satisfied with the new configuration, perform the rollback
steps now. Refer to the Rollback in the section Replacing a TSC in a
TSU on page 145.
Step 3. If you have a 2-host platform, propagate the updated configuration. To do
this, carry out one of the following:
196
Chapter 10
If you are not satisfied with the configuration, perform the rollback steps
now. Refer to the Rollback in the section Removing a TSC from a TSU
on page 149.
Step 6. If you have a 2-host platform, propagate the updated configuration. To do
this, carry out one of the following:
Chapter 10
197
198
Chapter 10
Chapter 10
199
If you are not satisfied with the new configuration, perform the rollback
steps now. Refer to the Rollback section below.
Step 6. Connect the TSC cables at the network end.
Step 7. Restart HP OpenCall SS7 by running the command ss7Start.
Step 8. Add the link(s) to the stack. In the SS7 Monitor screen, select
Configure Entities|Config MTP|Config lk/lkset and add the new
link(s).
Press "C" to checkpoint the modifications.
Step 9. Activate the link(s). In the SS7 Monitor screen, select
Monitor Entities|Monit MTP|Monit lk/lkset, then activate the
link(s).
Rollback
Step 2. Stop HP OpenCall SS7 by running the command ss7Stop -all and shut
down the platform.
Step 3. Take anti-static precautions by wearing the grounding wrist strap.
Step 4. Power off the host server.
Step 5. Remove the network cables from the TSC and disconnect them at the
network end.
Step 6. Remove the cover of the host server.
Step 7. Remove the new TSC from the host. Refer to your server documentation
for help with this.
Step 8. Replace the cover of the host server.
Step 9. Power on the host server and wait until it has booted.
200
Chapter 10
Chapter 10
201
If you are not satisfied with the new configuration, perform the rollback
steps now. Refer to the Rollback in the section Replacing a TSC in a
Host Server on page 161.
Step 3. Reconnect the TSC cables to the signaling network.
Step 4. Restart HP OpenCall SS7 by running the ss7Start command.
202
Chapter 10
If you are not satisfied with the configuration, perform the rollback steps
now. Refer to the Rollback in the section Removing a TSC from a Host
Server on page 164.
Step 6. Reconnect all TSC cables to the network.
Step 7. Restore the traffic, as described in Restoring the Traffic on page 183.
Chapter 10
203
If you are not satisfied with the new configuration, perform the rollback
steps now. Refer to the Rollback in the section Replacing a LAN Card
in a TSU on page 139.
Step 3. If you have a 2-host platform, propagate the updated configuration. To do
this, carry out one of the following:
204
Chapter 10
Chapter 10
205
206
Chapter 10
If both TSCs are to take their clocks from the SS7 network, set
the clock source to external for both TSCs.
If one of the two TSCs is to act as the clock source, set the clock
source to internal for this TSC and to external for the other TSC.
2. For the TSC that is connected directly to the network, configure the
two ports used so that they are internally connected on the TSC.
Each port must be connected to the other port by setting the Port
Source parameter in the Port Configuration screen.
For example, for the system shown in the above diagram, this
configuration for
TSC A would be as follows:
For Port 0, set Port Source to be 2 (so that the output for Port 0 is
taken from Port 2 via an internal connection on the TSC).
For Port 2, set Port Source to be 0 (so that the output for Port 2 is
taken from Port 0 via an internal connection on the TSC).
3. Create the links for the two TSCs. For each link, you must specify a
name, a TSC, a port and a timeslot.
For example, for the system shown in the above diagram, you would
create the following links:
Chapter 10
207
NOTE
In order to have alarms from the E1 network propagate to TSC B, but not
to have the alarms from the TSC B propagate to the E1 network, use the
following commands and settings:
1. cfgSs7Hw -modify -port 0 -tsc <id-A> -portChaining
enable -chainOnPort 2 -chainAlarm enable
2. cfgSs7Hw -modify -port 2 -tsc <id-A> -portChaining
enable -chainOnPort 0 -chainAlarm disable
208
Chapter 10
11
Chapter 11
209
CAUTION
This procedure for static TCAP expansion assumes that the target LPCs
(SS7 stacks) are NOT running (on either host, in the case of a 2-host
platform). If this is not the case, use the dynamic TCAP expansion
procedure in Expanding TCAP Processing Online on page 211.
Offline Procedure
Step 1. Save a back-up of the current configuration using the cfgMgr -copy
-toDir command.
Step 2. Modify the level of the TCAP processing capacity using the cfgTcap
-tune -static command.
Step 3. Repeat Step 2 for the other LPCs, if required.
Step 4. Propagate your changes using the cfgPropagate command.
NOTE
210
Once you have completed the above procedure, you can start the LPCs
(SS7 stacks).
Chapter 11
NOTE
Before following the procedures in this chapter, you must assess the
feasibility of your planned expansion. You will need to determine
whether it is possible to expand the TCAP processing capacity from the
current level to the desired level. However, you do not need to be
concerned with the details of the process redistribution, as the tools will
automatically determine this for you. If you first need to add a CPU to
your platform, refer to your server documentation to see how to do this.
By following the procedures below, it is only possible to expand the TCAP
processing capacity corresponding to one LPC at any one time. If you
wish to change the performance level for more than one LPC, you must
follow the complete procedure for each LPC separately and apply the
change to the running system before proceeding to the next change.
Online Procedure
CAUTION
Chapter 11
This procedure for dynamic TCAP expansion assumes that the target
LPC (SS7 stack) is running (on both hosts, in the case of a 2-host
platform). If this is not the case, use the static TCAP expansion
procedure in Expanding TCAP Processing Offline on page 210.
211
212
Chapter 11
12
Chapter 12
213
Link Limitations
TSC type
NOTE
Maximum
number of
links per TSC
Maximum
number of links
per port
TSCs
available
with links...
V.35
2 or 4
E1
16
16
2, 4, 8 or 16
T1
16
16
2, 4, 8 or 16
The maximum number of links that you can use on your system depends
on the platform license you have purchased.
If your license does not support the new total number of links that you
want to use on a TSC, you will need to upgrade the platform license
before adding links to your system (refer to Chapter 7, Upgrading the
Platform License, on page 105).
You can view the global platform license information using the
cfgPlatform -view license command.
Each TSC has a maximum number of links that it can maintain - this
number is determined when the TSC is ordered. If your required number
of links exceeds this maximum, it may be possible to upgrade the link
capability of the TSC: To do this, refer to Upgrading TSCs on page 220.
You can view your TSCs link capability using the ss7HwInfo -c
<tsc-id> command.
If it is not possible to enhance the link capability of your TSC, you will
need to add another TSC before you can add links.
214
Chapter 12
You do not need to power off the system in order to add links. You can
also perform this upgrade without disturbing traffic, except if you need
to modify a port configuration, in which case you will have to divert
traffic from the TSC concerned.
NOTE
Chapter 12
215
If you are not happy with the new configuration, perform the rollback
steps now. Refer to the Rollback section below.
Step 8. If you have a 2-host platform, propagate the updated configuration. To do
this, carry out one of the following:
Rollback
Step 1. Deactivate the added link(s) on the stack. In the SS7 Monitor screen,
select Monitor Entities|Monit MTP|Monit lk/lkset and deactivate
the link(s).
Step 2. Remove the added link(s) from the stack. In the SS7 Monitor screen,
select Configure Entities|Config MTP|Config lk/lkset and remove
the link(s).
Press "C" to checkpoint the modifications.
216
Chapter 12
c. If you have diverted the traffic from the TSC, restore it now, as
described in Restoring the Traffic on page 183.
Step 4. If you connected an additional port to the network in Step 1 of the main
procedure, disconnect the cable at the network end.
Chapter 12
217
NOTE
You do not need to power off the system in order to remove links. You can
also perform this update without disturbing traffic (apart from the traffic
on the removed links).
218
Chapter 12
If you are not happy with the new configuration, perform the rollback
steps now. Refer to the Rollback section below.
Step 7. If you have a 2-host platform, propagate the updated configuration. To do
this, carry out one of the following:
Step 8. If you have removed the last link of a port, remove the network cables
connected to this port. Note that you can view the ports using the
cfgSs7Hw -view command.
Only perform this rollback when instructed to do so in Step 6 above.
Rollback
Step 1. Rollback the configuration changes by carrying out either one of the
following:
Step 2. Add the removed link(s) to the stack. In the SS7 Monitor screen, select
Configure Entities|Config MTP|Config lk/lkset and add the new
link(s).
Press "C" to checkpoint the modifications.
Step 3. Activate the link(s). In the Stack Monitor screen, select
Monitor Entities|Monit MTP|Monit lk/lkset and type A.
Chapter 12
219
Upgrading TSCs
Every TSC is limited in terms of the number of links to the SS7 network
that it can handle. This limit is chosen when ordering the TSC. However,
it is possible to upgrade the card to permit a larger number of links. This
can be done without changing the TSC or removing it from the platform.
This section describes how to upgrade a TSC by increasing the number of
SS7 links that it can handle.
Example 12-1
ss7HwInfo Output
If you execute the command without options as follows:
ss7HwInfo
220
Chapter 12
0000087H3772
00004120
000000E68645
16
SS7
00
FRU Number
: 0000087H3427
Manufacturer ID : 196G000000
ROS Level and ID : 2.2
NOTE
If you are prompted for a platform license, configure and propagate this
using the cfgPropagate command.
ss7TscUpgrade Parameters
Parameter
Name
Function
-c
tscId
-p
licenseCodeword
Chapter 12
221
Troubleshooting
The following table lists the error messages that can be obtained when
using the ss7TscUpgrade command, with their corresponding meanings.
Error messages are generated if any of the parameters are missing or out
of range.
Table 12-3
Meaning
Corrupted codeword
222
Chapter 12
Chapter 12
P/N Label
E1/T1
J3527-60002
E1/T1
J3527-60004
E1/T1
J3527-60008
E1/T1
16
J3527-60016
V35
J3528-60002
V35
J3528-60004
223
224
Chapter 12
13
Chapter 13
223
Overview
The procedure in this chapter describes how to expand a 2-host platform
by adding a Back End on which all user applications will run, leaving the
Front End for SS7 stack processing only. The new computer becomes the
Back End, leaving the two original computers to be the Front End.
This procedure requires an advanced knowledge of
HP OpenCall SS7 configuration and must only be carried out by
suitably qualified personnel.
NOTE
The procedure presented does not cover all possible scenarios and is
provided for guidance only. It may therefore be necessary to adapt the
procedure for your particular configuration requirements.
NOTE
You will need to log on to each host as root when performing this
procedure.
224
Chapter 13
NOTE
This procedure assumes that in the final system all the computers of the
platform will be connected together via LAN switches. For High
Availability, two LAN switches are used, with each computer connected
to each switch.
NOTE
Chapter 13
225
After
Before
Back End
NEW Computer
Applications: Running
LANs
Switch
Front End
Switch
Switch
Switch
LAN
LAN
Front End
LAN
LAN
LAN
LAN
LAN
LAN
Host
Host
Host
Host
Applications: Running
HP OC SS7: Running
Applications: Running
HP OC SS7: Running
HP OC SS7: Running
HP OC SS7: Running
LAN
LAN
LAN
LAN
LAN
LAN
LAN
LAN
226
Chapter 13
NOTE
The type of LAN connections used to connect the Front End to the Back
End depends on your platform and your requirements.
This procedure assumes that the FE and BE computers will be connected
together via LAN switches (no broadcasting). Two switches are required
for High Availability of the LAN connections. Using this method, only
two LAN ports are required on each FE computer, for a highly available
connection.
NOTE
Chapter 13
227
Purpose
To back up the current configuration.
Actions
Step 1. Save the following files from the host to an accessible place:
/var/opt/OC/HA/ocLan.conf
/etc/hosts
/home/ocadmin/.rhosts
Use the command cp -p to maintain the same access rights.
Step 2. Use the command cfgMgr -copy -toDir to save a back-up of the
HP OpenCall SS7 configuration in a safe place.
228
Chapter 13
Front End
Switch
LAN
Host
LAN
Host
Applications: Running
HP OC SS7: Running
LAN
Switch
Applications: Running
HP OC SS7: Running
LAN
LAN
LAN
Rollback
Remove the saved configuration.
Chapter 13
229
Purpose
To stop HP OpenCall SS7 on either of the hosts in order to prepare this
host for the LAN connections to the BE computer.
Actions
Step 1. Stop all user applications on the host that is to be stopped.
Step 2. Before shutting down, prevent the host from auto-restarting
HP OpenCall SS7, as follows.
a. Comment out the hpoc line in /etc/inittab.
b. Execute the command init q.
Step 3. Perform a graceful stop, using the command ss7Stop -all.
230
Chapter 13
Front End
Switch
LAN
Switch
Host
Host
LAN
LAN
LAN
Applications: Running
HP OC SS7: Running
LAN
LAN
Rollback
Step 1. Re-enable auto-restart of HP OpenCall SS7 on the host, as follows.
a. Uncomment the hpoc line in the file /etc/inittab.
b. Execute the command init q.
HP OpenCall SS7 will now automatically restart.
Step 2. Restart all user applications.
Chapter 13
231
Purpose
To connect the BE computer to the FE hosts via LAN switches and test
the connections.
Actions
Step 1. On the BE computer, insert the hostnames and IP addresses of both FE
hosts into the /etc/hosts file.
Step 2. On each FE host, insert the hostname and IP addresses of the BE
computer in the /etc/hosts file.
Step 3. Connect the LAN cables from the BE host to the two switches, one LAN
cable to each switch
Step 4. Test the LAN connections just installed by running /bin/ping on both
the FE hosts and the BE computer, using their respective IP addresses.
Step 5. Insert <hostname> ocadmin into the file /home/ocdamin/.rhosts on
both FE hosts, where <hostname> is the system name of the BE
computer.
Also ensure that this entry and the equivalent entries for both FE hosts
are present in the ~ocadmin/.rhosts file on the BE computer.
232
Chapter 13
Back End
NEW Computer
Applications: Not Running
LANs
Switch
Switch
LAN
Front End
LAN
Host
LAN
Host
LAN
LAN
LAN
Applications: Running
HP OC SS7: Running
LAN
LAN
Chapter 13
233
234
Chapter 13
Purpose
To add the BE computer to the running configuration and to propagate
this new configuration to the other computers of the platform.
Actions
Step 1. On the idle FE host, add the BE computer to the HP OpenCall SS7
running platform configuration using the command:
cfgPlatform -add -backEnd
See the MAN pages for more details.
Step 2. Propagate the modified running platform configuration to the other FE
host and to the BE computer using the command cfgPropagate (do not
use any of the options, see the MAN page for more details).
NOTE
Chapter 13
235
Back End
NEW Computer
Applications: Not Running
LANs
Switch
Switch
LAN
Front End
LAN
Host
LAN
Host
LAN
LAN
LAN
Applications: Running
HP OC SS7: Running
LAN
LAN
236
Chapter 13
NOTE
Chapter 13
237
Purpose
To add the BE computer to the Opencall SS7 LAN configuration, and
propagate this new LAN configuration.
Actions
Step 1. On the idle host, use the command cfgPlatform -view -system to
obtain the current HP OpenCall SS7 LANconfiguration. See the MAN
page for more details.
Note carefully the LAN number and associated IP addresses you have
used for each host.
Step 2. On the idle FE host, add the BE computer to the HP OpenCall SS7 LAN
configuration.
NOTE
For each HP OpenCall SS7 LAN, use the command below to define the
LAN connection between the two FE hosts, and the new BE host.
cfgPlatform -add -ocLan
See the MAN page for further details.
Step 3. Propagate the modified HP OpenCall SS7 LAN configuration to the
other FE host and to the BE computer using the cfgPropagate -ocLan
command. See the MAN page for more details.
238
Chapter 13
Back End
NEW Computer
Applications: Not Running
LANs
Switch
Switch
LAN
Front End
LAN
Host
LAN
Host
LAN
LAN
LAN
Applications: Running
HP OC SS7: Running
LAN
LAN
Chapter 13
239
240
Chapter 13
Purpose
To restart HP OpenCall SS7 on the idle FE host.
Actions
Step 1. Re-enable autostart of HP OpenCall SS7 on the idle FE host, as follows.
a. Uncomment the hpoc line in the file /etc/inittab.
b. Execute the command init q.
HP OpenCall SS7 will now automatically restart.
Step 2. Restart the user applications on this host.
Chapter 13
241
Back End
NEW Computer
Applications: Not Running
Switch
LANs
Switch
LAN
LAN
Front End
Host
LAN
Host
Applications: Running
HP OC SS7: Running
LAN
LAN
Applications: Running
HP OC SS7: Running
LAN
LAN
LAN
242
Chapter 13
Chapter 13
243
Purpose
To load the new HP OpenCall SS7 LAN configuration on the other FE
host by restarting HP OpenCall SS7.
Actions
Step 1. Stop all user applications on the host that is to have HP OpenCall SS7
stopped.
Step 2. Before stopping HP OpenCall SS7, prevent the host from auto-restarting
HP OpenCall SS7, as follows.
a. Comment out the hpoc line in /etc/inittab.
b. Execute the command init q.
Step 3. Perform a graceful stop, using the command ss7Stop -all.
Step 4. Restart HP OpenCall SS7 on the idle FE host. To do this, re-enable
autostart of HP OpenCall SS7 on the idle FE host, as follows.
a. Uncomment the hpoc line in the file /etc/inittab.
b. Execute the command init q.
HP OpenCall SS7 will now automatically restart.
Step 5. Restart the user applications on this host.
244
Chapter 13
Rollback
None.
Chapter 13
245
Purpose
To move application processing from the FE hosts to the BE computer.
Actions
Your system now includes a fully installed and configured Back End
computer.
Your applications are still running on the FE hosts and you must now
migrate these applications to the BE computer. You must decide for
yourself exactly how this will be done.
246
Chapter 13
Back End
NEW Computer
Applications: Running
Switch
LANs
Switch
LAN
LAN
Front End
Host
LAN
Host
HP OC SS7: Running
LAN
LAN
HP OC SS7: Running
LAN
LAN
LAN
Rollback
None.
Chapter 13
247
248
Chapter 13
Tools Catalog
This appendix contains a catalog of the different tools available for use
with HP OpenCall SS7.
Appendix A
249
Tools Catalog
Graphical Tools
Graphical Tools
The graphical tool described in this section can be used to configure and
monitor HP OpenCall SS7.
SS7 Monitor
The SS7 Monitor is used to configure and monitor the SS7 network.
Figure A-1
Start and stop the SS7 Monitor using the ss7MgrStart and ss7MgrStop
commands.
250
Appendix A
Tools Catalog
Command Line Tools
cfgCheck
cfgCreate
cfgInstall
cfgMgr
Manages configurations
cfgPatch
cfgPropagate
cfgSs7HwCreate
cfgSs7HwUpdate
cfgPlatform
Appendix A
Comment
251
Tools Catalog
Command Line Tools
Table A-1
Command
cfgSs7Hw
cfgMtp
cfgSccp
cfgTcap
cfgIsup
cfgTup
Table A-2
Command
Comment
Comment
ss7Start
ss7Stop
Table A-3
Command
ss7MgrStart
ss7MgrStop
ocftcontrol
ocftstatus
252
Comment
Appendix A
Tools Catalog
Command Line Tools
Table A-4
Command
Function
loadconf
ss7CheckPoint
Table A-5
isupgenITU
ss7IsupReload
Table A-6
Command
ISUP Commands
Command
isupgenANSI
Comment
Function
Comment
TUP Commands
Function
Comment
tupgen
ss7TupReload
Table A-7
Command
ss7Diag
ss7HwAccept
ss7HwInfo
ss7HwInit
ss7HwLoad
Appendix A
Comment
253
Tools Catalog
Command Line Tools
Table A-7
Command
Function
ss7HwReplace
ss7HwRollback
ss7TcapTune
ss7TscPing
Pings TSC
ss7TscStatus
ss7TscUpgrade
ss7TsuPing
ss7TsuStatus
Table A-8
Command
cleanttl
nlog
nmsg
ss7SNMPAgent
ss7HwTrace
254
Comment
Comment
You must be root to
use this command
Enter the
-displayTrapDoc
option to list all
available traps
Appendix A
Tools Catalog
Command Line Tools
Table A-8
Command
Function
Comment
ss7TcapSnmpAgent
Enter the
-displaytext or
-displayhtml option
to list the TCAP
managed objects.
startnettl
Starts logging.
stopnettl
Stops logging.
wlog
wmsg
Table A-9
Command
tcxgen
trafgen
Table A-10
Command
Other Commands
Function
collectInfo
ss7License
ss7oamtool
Appendix A
Comment
Comment
Intended primarily for
use by HP support
personnel.
255
Tools Catalog
Command Line Tools
Table A-10
Command
whichPathFor
256
Comment
Appendix A
Tools Catalog
Web-based Management Tools
Appendix A
257
Tools Catalog
Web-based Management Tools
On Linux:
a. Uninstall previous installation of the Java plug-in, if applicable:
rm -fr $HOME/.netscape/java
rm $HOME/.netscape/plugin.so
b. Make sure the path variable is set to point to jre-1.3.1_03 bin.
c. Set the NPX_PLUGIN_PATH environment variable in the ENV file
for the Netscape 4 browser:
export NPX_PLUGIN_PATH=<jre>/plugin/i386/nsz
d. Start (or restart) your Netscape browser.
e. Close and restart your Netscape browser again, that is, restart the
browser a second time.
f. Enable Java and the Java plug-in for the browser
For more details on the installation go to http://java.sun.com/
Step 4. To initialize the web monitoring service:
a. Make sure the C++ library version libstdc++libc6.1-1.so is
available.
b. To start Tomcat, enter:
tomcat4 start
c. To make sure that the tomcat process has started, check the tomcat
log file /var/tomcat4/logs/catalina.out and look for the following
lines:
Starting service Tomcat-Standalone
Apache Tomcat/4.1.
d. If the start command returns an error report, or if the tomcat process
has not started, check the JAVA_HOME variable in the
/etc/tomcat4/tomcat4.conf file. This variable should point to the
correct JDK installation path on the given host.
258
Appendix A
Tools Catalog
Web-based Management Tools
e. To access the HP OpenCall web monitoring service, enter the
following URL:
http://<hostname>.<domain_name>:8080/hp/opencall/
monitoring/home/home.jsp
Result
The web monitoring service is now available on your browser.
Appendix A
259
Tools Catalog
Web-based Management Tools
260
Appendix A
Appendix B
259
Function
The Telecom Signaling Card (TSC) provides the means of connecting an
HP OpenCall SS7 platform to the signaling network. These cards can be
accommodated in either:
a host server with a PCI bus that can take TSCs directly. This is
referred to as TSC-in-system.
260
Appendix B
V.35 Cards
These are TSCs that communicate using the V.35/V.36 standard
(DTE or DCE). The choice of cable determines whether the card uses
the DTE or DCE interface type.
These cards have 4 DTE ports or 4 DCE ports, and 4 SS7 links.
DTE/DCE can operate at 48.5 (TTC standard only), 56 or 64 kbits/s.
E1/T1 Cards
These are TSCs that communicate using the E1 or T1 standard
(standard G.703). The choice of cable determines whether the card
uses the E1 or T1 interface type.
These cards have 4 E1 ports or 4 T1 ports, and can support up to 16
SS7 links.
NOTE
Appendix B
Do not mix card types in a single Telecom Signaling Unit or host server.
If you wish to use V.35, E1 and T1 TSCs with your platform, you must
install each card type in a separate TSU.
261
Physical Description
Ready-to-install V.35 and E1/T1 TSCs comprise a 32-bit V.35 or E1/T1
universal telecom signaling PMC card mounted on a full-length PCI
adapter card. The PMC card implements the physical line interface to
the SS7 network.
The physical details of each type of TSC are described below.
V.35 PMC
L1 LED
AdapterCard
L2 LED
120-pinConnector
L1 LED
262
Appendix B
The V.35 TSC has four ports. You can assign a single SS7 link to each of
these ports. The card is available with 2 or 4 links.
Part Numbers
The part number of a V.35 TSC depends on the number of links that it
supports, as follows:
HP Part
Number
Upgrading the
Number of Links
Number of
Links
J3528-60002
J3528-60004
Appendix B
263
LEDs
The E1/T1 TSC has 4 ports and is available with 2, 4, 8 or 16 links. You
can assign up to 16 links to any one port. Each link can be assigned to
any valid timeslot, on any port.
Part Numbers
The part number of an E1/T1 TSC depends on the number of links that it
supports, as follows:
HP Part Number
264
Number of Links
J3527-60002
J3527-60004
J3527-60008
J3527-60016
16
Appendix B
An E1/T1 TSC is supplied with a defined number of SS7 links that it can
support, as detailed in the above table. The number of links supported
can be increased to a maximum of 16. This upgrade can be performed
without removing the card from the platform.
Refer to Adding and Activating Links on the SS7 Network on page 205
for information on upgrading the TSC link capability.
Appendix B
265
Description
Section Reference
E1
T1
V.35
Loopback
E1 Connections
This section describes the connections required to connect an E1/T1 TSC
to the signaling network, when the E1 protocol is to be used.
The E1 cable assembly connects to the E1/T1 TSC by means of a 36-pin
male connector, shown in Figure B-3.
266
Appendix B
The cable assembly provides four ports to the network. These ports may
interface to the network using either four RJ-45 connectors or eight BNC
connectors (grounded or ungrounded). The RJ-45 and BNC connector
types are illustrated in the figures below.
Figure B-4
Appendix B
267
BNC Connector
E1 Connector
Pinouts
The pinouts for the three types of E1 cable assembly are provided in the
tables below. Each table lists the pins of the relevant port connector(s)
and for each port gives the corresponding pins on the 36-pin TSC
connector.
Table B-1
RJ-45 Pin
I/O
(Input/
Output)
Port
0
Port
1
Port
2
Port
3
01
35
31
25
21
RX1-x
02
36
32
26
22
RX2-x
03, 06
16
12
FGND-x
04
33
29
23
19
TX1-x
05
34
30
24
20
TX2-x
Table B-2
BNC
Conductor
Port
0
268
Signal
Name
Port
1
Port
2
Signal
Name
I/O
(Input/
Output)
Port
3
Appendix B
BNC
Conductor
I/O
(Input/
Output)
RX Inner
35
31
25
21
RX1-x
TX Inner
33
29
23
19
TX1-x
FGND
TX2-x
RX2-x
TX and RX
Outer
Housing,
20, 22, 24, 26, 30, 32, 34, 36
Table B-3
BNC
Connector
E1 Cable
Specification
Signal
Name
Signal
Name
I/O
(Input/
Output)
Port
0
Port
1
Port
2
Port
3
RX Inner
35
31
25
21
RX1-x
RX Outer
36
32
26
22
RX2-x
TX Inner
33
29
23
19
TX1-x
TX Outer
34
30
24
20
TX2-x
16
12
FGND
Impedance
E1 balanced 120 ohms
E1 unbalanced 75 ohms
Appendix B
269
The table below lists the corresponding cable assemblies and their HP
part numbers.
Table B-4
E1 Cable Assemblies
Cable Assembly
Network
Connectors
Cable
Assembly HP
Part Number
8 BNC
(2 per port)
5063-1330
8 BNC
(2 per port)
5063-1331
RJ-45 Balanced
4 RJ-45
(1 per port)
5063-1338
T1 Connections
This section describes the connections required to connect an E1/T1 TSC
to the signaling network, when the T1 protocol is to be used.
The T1 cable assembly connects to the E1/T1 TSC by means of a 36-pin
male connector, shown in Figure B-3 on page 267.
The cable assembly then provides four ports that interface to the
network using four RJ-45 connectors. The RJ-45 connector type is
illustrated in Figure B-4 on page 267.
270
Appendix B
The pinouts for the T1 cable assembly are provided in the table below.
The table lists the pins of the port connector and for each port gives the
corresponding pins on the 36-pin TSC connector.
Table B-5
RJ-45
Pin
T1 Cable
Specification
Signal
Name
I/O
(Input/
Output)
Port
0
Port
1
Port
2
Port
3
35
31
25
21
RX1-x
36
32
26
22
RX2-x
3, 6
16
12
04
FGND-x
33
29
23
19
TX1-x
34
30
24
20
TX2-x
T1 Cable Assembly
Network
Connectors
Cable Assembly
RJ-45
4 RJ-45
(1 per port)
Cable Assembly
HP Part Number
5063-1339
V.35 Connections
This section describes the connections required to connect a V.35 TSC to
the signaling network.
The V.35 cable assembly connects to the V.35 TSC by means of a 120-pin
male D-shell connector, shown in Figure B-6 below.
Appendix B
271
There are two types of V.35 cable assembly that can be used. One
provides a DTE protocol connection and the other provides a DCE
protocol connection.
A V.35 cable assembly provides four ports to the network. These ports
interface to the network using four 34-pin female DCE connectors or four
34-pin male DTE connectors. These are illustrated below in Figure B-7
and Figure B-8 respectively.
Figure B-7
272
Appendix B
V.35 Connector
Pinouts
The pinouts for the V.35 DTE and DCE cable assemblies are provided
below in Table B-7 and Table B-8 respectively. Each table lists the pins of
the relevant port connector and for each port gives the corresponding
pins on the 120-pin TSC connector.
Table B-7
DTE Pin
Appendix B
Signal
Name
Port
0
Port
1
Port
2
Port
3
110
50
10
114
54
120
I/O
(Input/
Output)
Shield
70
GND
66
RTSx
60
15
75
CTSx
98
38
22
82
DSRx
94
34
26
85
CDx
112
52
68
DTRx
118
58
62
TXDxA
273
DTE Pin
Table B-8
I/O
(Input/
Output)
Signal
Name
96
36
24
84
RXDxA
119
59
63
TXDxB
97
37
25
85
RXDxB
116
56
64
TCLKOxA
108
48
12
72
RXCLKxA
117
57
05
65
TCLKOxB
109
49
13
73
RXCLKxB
102
42
18
78
TCLKIxA
AA
103
43
19
79
TCLKIxB
DCE Pin
Signal
Name
I/O (Input/
Output)
Port 0
Port 1
Port 2
Port 3
120
60
15
75
CTSx
114
54
66
RTSx
114
54
66
RTSx
94
34
26
85
CDx
98
38
22
82
DSRx
96
36
24
84
RXDxA
118
58
62
TXDxA
97
37
25
85
RXDxB
E
F
H
274
Appendix B
DCE Pin
Signal
Name
I/O (Input/
Output)
119
59
63
TXDxB
108
48
12
72
RXCLKxA
V (and Y)
116
56
64
TCLKOxA
109
49
13
73
RXCLKxB
X (and AA)
117
57
05
65
TCLKOxB
Y (and V)
116
56
64
TCLKOxA
AA (and X)
117
57
05
65
TCLKOxB
The table below lists the corresponding cable assemblies and their HP
part numbers.
Table B-9
Cable
Assembly
Cable Assembly
HP Part Number
DTE
4 DTE
(1 per port)
5063-1362
DCE
4 DCE
(1 per port)
5063-1332
Loopback Hoods
Loopback hoods are used in the hardware validation procedure to
connect the output of a TSC network port to the input of the same TSC
network port. This allows a TSC to be operated and tested without direct
connection to the network. There are two general types of loopback hood:
Appendix B
275
5063-1340
V.35 DTE
5063-1334
V.35 DCE
5063-1335
Note that Cable Loopback Hoods are not supplied for E1/T1 BNC
cables, since loopback is easily accomplished with these cables.
Card Loopback Hoods: These connect directly to the TSC (to the
TSC end-plate connector on the rear panel of the TSU) and can
therefore be used to test the operation of the TSC in isolation from
the TSC network cables. These hoods are available in two types, for
the different types of card, and are supplied with the cards:
Loopback Hood Type
Loopback Pinouts
HP Part Number
E1/T1
5063-1346
V.35
5063-1336
The pinouts for the above loopback hoods are given in the tables that
follow. Each table details the pair of pins of the relevant connector that
must be connected together.
Table B-10
From
276
To
Signal
Pin
TXDxA
TCLKIxA
Signal
Pin
RXDxA
Appendix B
From
To
TXDxB
RXDxB
RCLKIxA
TCLKxB
RCLKIxB
RTSx
CTSx
CDx
DTRx
DSRx
TCLKIxB
AA
TCLKOxA
Table B-11
From
To
Signal
Pin
Signal
Pin
RXDxA
TXDxA
RXDxB
TXDxB
RCLKxA
TTExA
RCLKxB
TTExB
RTSx
CTSx
DSRx
DTRx
Table B-12
From
Appendix B
To
Signal
Pin
DTR0A
112
Signal
Pin
DSR0A
98
CD0A
94
277
From
DTR0B
113
DSR0B
99
CD0B
95
GND
110
ID0_P1
92
RXD0A
96
TXCLK10A
102
RXD0B
97
TXCLK10B
103
RXD012V
104
TXCLK1012V
91
TXD0A
118
TXD0B
119
TXD012V
105
RTS0A
114
CTS0A
101
TXCLK0A
116
RXCLK0A
108
TXCLK0B
117
RXCLK0B
109
TXCLK0012V
111
RXCLK012V
106
DTR1A
52
DSR1A
38
CD1A
34
DSR1B
39
CD1B
35
GND
50
RXD1A
36
TXCLK11A
42
RXD1B
37
TXCLK11B
43
DTR1B
278
To
53
TXD1A
58
TXD1B
59
Appendix B
From
RXD112V
44
TXCLK1112V
31
54
CTS1A
40
RTS1B
55
CTS1B
41
TXCLK1A
56
RXCLK1A
48
TXCLK1B
57
RXCLK1B
49
TXCLK0112V
51
RXCLK112V
46
DTR2A
DSR2A
22
CD2A
26
DSR2B
23
CD2B
27
GND
10
RXD2A
24
TXCLK12A
18
RXD1B
25
TXCLK12B
19
RXD212V
16
TXCLK1212V
30
TXD112V
45
RTS1A
DTR2B
Appendix B
To
TXD2A
TXD2B
TXD212V
17
RTS2A
CTS2A
20
RTS2B
CTS2B
21
TXCLK2A
RXCLK2A
12
TXCLK2B
RXCLK2B
13
TXCLK0212V
11
RXCLK212V
279
From
To
DTR3A
68
DTR3B
69
DSR3A
82
CD3A
86
DSR3B
83
CD3B
87
GND
70
RXD3A
84
TXCLK13A
79
RXD3B
85
TXCLK13B
79
RXD312V
76
TXCLK1312V
90
TXD3A
62
TXD3B
77
TXD312V
77
RTS3A
66
CTS3A
80
RTS3B
67
CTS3B
81
TXCLK3A
64
RXCLK3A
72
TXCLK3B
65
RXCLK3B
73
TXCLK0312V
71
RXCLK312V
61
Table B-13
From
280
To
Notes
Signal
Pin
Signal
Pin
TX1x
RX1x
TX2x
RX2x
Cable ID poll
Cable ID sense
No cable ID resistor
required
Appendix B
Table B-14
From
Signal
To
Pin
Signal
Pin
ID0
GND0
18
ID1
10
GND1
14
ID2
27
GND2
ID3
28
GND3
TX1_0
33
RX1_0
35
TX2_0
34
RX2_0
36
TX1_1
29
RX1_1
31
TX2_1
30
RX2_1
32
TX1_2
23
RX1_2
25
TX2_2
24
RX2_2
26
TX1_3
19
RX1_3
21
TX2_3
20
RX2_3
22
Connection Panels
To aid installation and maintenance, all cabling between a TSC and the
signaling network can be routed via an optional connection panel in the
server cabinet in which the TSCs are located (the TSCs are housed either
directly in the server or in one or more Telecom Signaling Units located
in the server cabinet).
The connection panel contains a number of sockets of a certain type, each
corresponding to one TSC port. The TSC cables connect to the sockets of
the panel from where they are connected to the network.
Appendix B
281
Connection Panels
Connection
Panel HP
Product Number
Connection
Panel HP Part
Number
12
J3844A
J3844-80100
BNC Grounded
12
J3845A
J3845-80100
BNC
Ungrounded
12
J5980A
J5980-80100
V.35
J3848A
J3848-80100
Connector
Type
Number
of Ports
RJ-45 Grounded
282
Appendix B
Appendix B
283
Environmental
Requirements
Parameter
Temperature
Operational
Range
Non-Operational Range
0C to 55C
Storage: 0C to 60C
Shipping: -40C to 70C
Humidity
(Non-Condensing)
284
5% to 95%
Storage: 5% to 80%
Shipping: 5% to 100%
Appendix B
Appendix C
285
Function
The Telecom Signaling Unit (TSU) provides accommodation for the
following PCI cards:
CPU Card
The CPU card is supplied pre-installed in the TSU and provides a
LAN connection to the host computer.
LAN Card
A LAN card can be installed to provide the connectivity to a second
host computer, for example, in a 2-host system.
a 1-host platform based around a host server which does not have an
internal PCI bus (and therefore cannot accommodate Telecom
Signaling Cards directly)
286
Appendix C
Physical Description
The Telecom Signaling Unit is an external chassis that can accommodate
PCI cards. The cards are mounted in a removable card cage which
incorporates the PCI backplane and a CPU card. The backplane has
seven slots:
For K-class servers, this host card is an HSC dual-port card allowing
up to two TSUs per HSC slot.
For A-, L- and N-class servers, this host card is a single or quad-port
PCI card, allowing up to four TSUs per PCI slot.
NOTE
Do not mix Telecom Signaling Card (TSC) types in a single TSU. If you
want to use more than one TSC type with your platform, install each
TSC type in a separate TSU.
NOTE
Appendix C
287
Part Numbers
HP Part Number
TSU Cabinet
Power Supply
J3401-60003
AC powered
J3401-60004
DC powered
The dimensions of the TSU cabinet are given in the table below.
Table C-2
TSU Dimensions
Height
Width
Depth
86.89 mm (3.421)
431.80 mm (17)
464.21 mm (18.28)
The following figures show the front view of the TSU, the unit with the
frontplate removed, and the back view of the TSU. The status LEDs on
the front and back are described in Checking the Hardware
Installation on page 121.
Figure C-1
288
Appendix C
Figure C-3
Appendix C
289
Input Voltage
Outputs
Primary
AC:
100-127/200-240 V AC
50-60 Hz
(auto-ranging)
+5 V @ 24 A (min)
+12 V @ 1.75 A (min)
Compliance with
Standards
UL1950
CSA22.2 #950
VDE0805
EN60950
IEC950
EN55022A
FCC Class A
290
Appendix C
A DC powered TSU can operate in the voltage range -48 V to -60 V. The
power supply requirements for a TSU operating from a DC supply are
presented in the table below.
Table C-4
Input Current
Input Voltage
Outputs
+5 V @ 24 A (min)
+12 V @ 1.75 A (min)
Compliance with
Standards
UL1950
CSA22.2 #950
VDE0805
EN60950
IEC950
EN55022A
FCC Class A
FTZ1046/84
Figure C-4 below shows the DC power supply connector and the
connector pinout. This is the connector at the TSU end of the power
supply cable.
WARNING
Appendix C
The power supply cable has been evaluated for use as an internal
wire only and must be installed in a cabinet for the system to
retain its safety regulatory markings.
291
Figure C-5
Table C-5
292
Pin
DC Return
DC
DC Return
Appendix C
Environmental
Requirements
Pin
DC
Not Used
2,3,5,6.
Parameter
Temperature
Humidity
(Non-Condensing)
Appendix C
Operational Range
Non-Operational
Range
0C to 50C
-40C to 70C
293
294
Appendix C
Appendix D
295
Configuration Basics
Global Name for Plug-In Process
The same name should be used for the plug-in process in different
configuration steps. This is called the plug-in global name and it must
be unique on the platform.
296
Appendix D
Overview of Configuration
Prerequisites
Before configuring Application Guardian, HP OpenCall SS7 must have
been installed.
PIC/AG is installed during the installation of HP OpenCall SS7. See
Chapter 2 Installing the HP OpenCall SS7 Software.
Configuration Steps
Configuring the HP OpenCall Application Guardian contains the
following steps:
Step 1. Configure Application Guardian engine for a particular plug-in.
Step 2. Configure the entries in /etc/services file, if needed.
Step 3. Configure the plug-in, if needed.
Step 4. Include the plug-in processes in the HP OpenCall environment.
Detailed information is given in the following sections.
Appendix D
297
HA Parameters
These parameters define ports (peer-to-peer and FTC) and heartbeats
(frequency, time-out period, etc.).
On a 2-host platform, the HeartBeatWithPeer parameter must be set to
YES for each Application Guardian engine process so that the
corresponding standby process is started correctly.
298
Appendix D
Appendix D
299
6639/tcp
6640/tcp
6641/tcp
6642/tcp
6784/tcp
6785/tcp
6786/tcp
6787/tcp
#
#
#
#
#
#
#
#
HP
HP
HP
HP
HP
HP
HP
HP
Opencall
Opencall
Opencall
Opencall
Opencall
Opencall
Opencall
Opencall
Plugin
Plugin
Plugin
Plugin
Plugin
Plugin
Plugin
Plugin
If other plugins are added, more tcp ports must be defined by the user.
For example:
Any Plug-In
For all plug-ins:
ha_plugin_1
12345/tcp
12346/tcp
300
12347/tcp
Appendix D
Appendix D
301
where:
trace
-c <file>
-E
-N
302
Appendix D
NOTE
Appendix D
The process class name should be the <plug-in global name> (see Global
Name for Plug-In Process on page 296), that is, the same as used in
configuring the Application Guardian engine. This should also be the
name under which the user plug-in process will appear the ocftstatus
command.
303
304
Appendix D
Index
A
activating
SNMP Traps, 88, 89
ACTIVE state
process, 86
administrator
Stack Monitor interface, 68
aligning
MTP2, 83
MTP3, 83
ANSI
full point code routing, 81
anti-static
kit, 19
precautions, 19
application
buffered I/O, 23
memory usage, 23
assigning CIC(s)
, 77
B
Back End , 225
battery backup , 24
BOOTING state
process, 86
bridge, isolating the LANs, 22
buffered file I/O, limitations of use, 23
C
cables, 266
E1, 269, 270
T1, 271
V.35, 275
card
cage, 135 , 169 , 287
cfgCheck, 50, 55, 251
cfgCreate , 55, 251
cfgInstall, 55 , 251
cfgIsup , 252
cfgMgr, 251
cfgModify, 55 , 212
cfgMtp , 252
cfgPatch, 251
cfgPlatform , 251
cfgPropagate , 55, 251
cfgSccp, 252
cfgSs7Hw, 251
cfgSs7HwCreate, 55, 251
cfgSs7HwUpdate, 55, 251
cfgTcap, 252
cfgTup, 252
checking
LANs, 86
the configuration, 50, 51
checkpointing
a new stack configuration, 68, 78
manually, 78
CIC-based distribution, 77
cleanttl, 254
clock-jump, 24
collectInfo, 255
commands
ss7MgrStart, 92
tcxgen, 255
trafgen, 255
conditions
operating, 22
Configuration, 61
configuration, 120
safeguarding, 19
SNMP Traps, 88, 89
validation, 65
configuring
checking the configuration, 51
GDI, 74
PINS, 58
Configuring DNS
Domain Name Server, 61
congested route, destination, 96
connection
MTP3 level, 83
connection panels, 115, 281
connections, 117
E1, 266
LAN, 118, 287
T1, 270
TSC to network, 118
TSU to host, 118
V.35, 271
connectivity
SS7, 83
connector, 266
BNC, 268
loopback hoods, 275
305
Index
RJ-45, 267
TSC (E1/T1), 267
TSC (V.35), 271
TSU rear panel, 117
V.35 (DCE), 272
V.35 (DTE), 272
copying large files, 23
CPU card , 113, 135, 286, 287
D
daisy-chaining, 205
DCE , 261, 272
deactivating
PINS, 59
destination
configuring as gateway, 72
out-of-service, 97
dimensioning main memory, 23
DOWN state
process, 86
Drop and Insert feature
TSC chained links, 205
DTE , 261 , 272
duplex platforms
cabling recommendations, 118
E
E1 cards, 261 , 263
cable assembly, 270
connections, 266
ports, 264
electrical specifications, 283, 290
environmental specifications, 283 , 290
expansion
to FE/BE system by adding a BE, 225
F
failed destination , 97
fans, 126, 176 , 289
files
copying, 23
limitations on size for copying, 23
Front End , 225
FTC
stopping using ss7Stop, 63
306
G
gateway, configuring, 72
GDI
configuring, 74
H
HA
validating, 86
HA processes
stopping using ss7Stop, 63
HA status
PINS, 60
High Availability, 24
hosts
front-end, 24
HP Opencall SS7
installation, 65
I
inhibit links, 97
installation
cards into a new TSU, 113
checking, 175
connecting up TSU/TSCs, 117
LAN card into TSU, 114
OS, 65
TSC into host server, 159
TSC into TSU, 114, 143, 149 , 164
TSU into server cabinet, 115
IP address
relocatable, 56 , 61
ISUP CIC-based distribution, 77
isupgenANSI, 253
isupgenITU, 253
L
LAN
card in TSU, 286
checking, 86
connections, 118 , 287
dimensioning, 22
duplex cabling recommendations, 118
installing card in TSU, 114
LEDs, 178
replacing card, 139
Index
supported types, 22
LEDs, 175
LAN card, 178
TSC, 177
TSU, 176
license
entering or upgrading, 107
link
adding to a TSC or TSU, 214
configuring, 72
E1/T1, 264
inhibit, 97
licenses, 214
number per port, 214
number per TSC, 214
upgrading, 263, 265
utilization rate, 97
V.35, 263
linkset
configuring, 72
Linkset/Link Activation Behavior, 97
loadconf, 252
local switch
PINS, 59
loopback hoods, 275
LPC
changing, 71
peer point code, 72
M
maintenance procedures, 121
installing a new TSC in a host server, 159
installing a new TSC in a TSU, 143, 149, 164
replacing a LAN card, 139
replacing a TSC in a TSU, 145, 161
replacing a TSU, 153
replacing a TSU fan, 126
replacing TSU AC power supply, 129
replacing TSU backplane and CPU card,
135
aligning, 83
MTP3
aligning, 83
connecting, 83
N
network
connecting national and international, 72
destination out-of-service, 97
running different configurations, 80
network configuration
saving, 74
nlog, 254
nmsg, 254
O
ocftcontrol, 252
ocftstatus, 252
online
TCAP expansion, 211
operating
PINS, 59
OS
installation, 65
out-of-service, 97
P
path
modification to enable other users, 21
pinouts
E1 BNC connector (grounded), 268
E1 BNC connector (ungrounded), 269
E1 RJ-45 connector, 268
E1/T1 RJ-45 cable loopback, 280
E1/T1 TSC card loopback, 280
T1 RJ-45 connector, 270
V.35 DCE cable loopback, 276
V.35 DCE connector, 274
V.35 DTE cable loopback, 276
V.35 DTE connector, 273
V.35 TSC card loopback, 277
PINS
configuration, 58
deactivating, 59
description, 56
functionality, 56
HA status, 60
local switch, 59
monitoring, 59
307
Index
operating, 59
remote switch, 60
requirements, 57
platform management workstation, 24
port
E1/T1, 264
V.35, 263
power
battery backup, 24
process to run when repowering, 24
power supply
replacing (TSU AC), 129
replacing (TSU DC), 132
TSC, 283
TSU (AC), 290
TSU (DC), 290
TSU DC connector, 292
precautions
anti-static, 19
safeguarding configuration, 19
safety, 18
process
states, 86
R
relocatable IP address, 56 , 61
remote switch
PINS, 60
route
congestion, 96
router
isolating the LANs, 22
S
SCCP
timers, 24
SLC
number, 71
SNMP Traps
activating, 88, 89
configuring, 88, 89
validating, 88 , 89
SS7 connectivity , 83
SS7 Monitor
configure global title translation, 73
configure links, 72
308
Index
switch
local (PINS), 59
remote (PINS), 60
synchronizing clocks, 24
SYNCHRONIZING state
process, 86
T
T1 cards, 261, 263
cable assembly, 271
connections, 270
ports, 264
TCAP
dynamic process expansion, 211
static process expansion, 210
timers, 24
tcxgen tool, 255
Telecom Signaling Card (TSC) , 259
adding in a TSU, 143, 149, 159 , 164
adding link(s), 214
adding to a TSU, 192, 196 , 199
cable assemblies, 270, 271, 275
chained links
Drop and Insert feature, 205
connectors, 266
E1/T1, 261, 263
environmental requirements, 283
function, 260
installing in TSU, 114
labeling your upgrade, 220
LEDs, 177
number of links, 220
on-site upgrade, 220
power supply, 283
replacing in a TSU, 145, 161
serial number, 220
upgrade, 220
upgrade troubleshooting, 220
V.35, 261, 262
Telecom Signaling Unit (TSU) , 285
adding to the platform, 184, 186 , 190, 197,
202
backplane, 135
cabinet, 288
card cage, 135, 169, 287
checking the configuration, 51
CPU card, 135, 286, 287
E1 configuration example, 51
environmental requirements, 293
Index
W
whichPathFor, 255
wlog, 254
310