Вы находитесь на странице: 1из 320

HP OpenCall SS7 platform

Operations Guide
For Release 3.1 on Linux
Second Edition

Manufacturing Part Number: 5971-3504


E0103

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

For Release 3.1 on Linux, January 2003

Second Edition

For Release 3.1 on Linux, May 2003

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

2. Installing the HP OpenCall SS7 Software


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Installing Linux for HP OpenCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Definition of the User and Group ocadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Installing HP OpenCall Enablement Kit Components for Linux . . . . . . . . . . . . . . . . . 35
Installing HP OpenCall SS7 3.1 on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Stage 1: Configuring the IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Stage 2: Installing the HP OpenCall SS7 Software . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Stage 3: Validating the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3. Configuring the Platform


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a New Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing a Pre-defined Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

4. Configuring the SS7 Network


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SS7 Monitor Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Information for 2-Host Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Guidelines for Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving the Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checkpointing the Configuration using SS7 Monitor. . . . . . . . . . . . . . . . . . . . . . . . .
Checkpointing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Loading your Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Different Network Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring ANSI Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cluster Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Full Point Code Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Validating SS7 Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Aligning at MTP2 Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Aligning at MTP3 Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting an Application at MTP3 Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

6. Managing and Monitoring the Platform


Starting and Stopping the Platform Management Tools . . . . . . . . . . . . . . . . . . . . . . . . 92
Starting the SS7 Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Stopping the Platform Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Monitoring HP OpenCall SS7 Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Changing the State of HP OpenCall SS7 Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Monitoring the SS7 Network Using the SS7 Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Changing the SS7 Monitor Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Available Network Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Monitoring MTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Configuring GDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Single Entity Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Viewing Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Working with SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Configuring SNMP Traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Displaying a List of Available Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Working with the SNMP TCAP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Configuring the SNMP TCAP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Displaying a List of Available TCAP Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

7. Upgrading the Platform License


Offline Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Online Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Displaying Licensing Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

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

9. Maintaining TSU/TSC Hardware


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing, Removing or Adding a Hardware Component in the Host . . . . . . . . . . . .
Replacing a Fan in a TSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing a TSU AC Power Supply (J3401-60100) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing a TSU DC Power Supply (J3401-60200) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing the TSU Backplane and CPU Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing a LAN Card in a TSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing an Additional TSC in a TSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing a TSC in a TSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing a TSC from a TSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing a TSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing a TSU from a Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing a TSC in a Host Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing a TSC in a Host Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing a TSC from a Host Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing a Four-Port TSC Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Common TSU/TSC Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing the TSU from the Server Cabinet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing and Replacing the TSU Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing and Replacing the Card Cage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Card to a TSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing a Card from a TSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

122
124
126
129
132
135
139
143
145
149
153
157
159
161
164
167
168
168
168
169
171
173
175

10. Configuring TSU/TSC Hardware


Diverting Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

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

11. Expanding Platform Processing Capability


Expanding TCAP Processing Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Offline Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Expanding TCAP Processing Online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Online Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

210
210
211
211

12. Updating TSCs and SS7 Links


Adding Link(s) to a TSC Port (on the Running Configuration) . . . . . . . . . . . . . . . . .
Removing Links from a TSC (on the Running Configuration) . . . . . . . . . . . . . . . . . .
Upgrading TSCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking the TSC is Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting the Serial Number and Number of Links . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Labeling Your Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

214
218
220
220
220
221
222
222

13. Expanding Your Platform: Adding a Back End


Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating FE/BE System by Adding a Back End . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stage 1: Saving Configuration from an FE Host to an Accessible Place . . . . . . . . .
Stage 2: Stopping HP OpenCall SS7 on One of the Hosts . . . . . . . . . . . . . . . . . . . .

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

B. Telecom Signaling Cards (J3527A and J3528A)


Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of Telecom Signaling Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
V.35 Telecom Signaling Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1/T1 Telecom Signaling Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSC Connectors and Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T1 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
V.35 Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Loopback Hoods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection Panels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSC Electrical and Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . .

260
261
262
262
263
266
266
270
271
275
281
283

C. Telecom Signaling Units (J3401A)


Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Physical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
TSU Electrical and Environmental Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

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.

About This Guide


This guide accompanies HP OpenCall SS7 3.1 on Linux.

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:

installing the software

configuring the platform

configuring the SS7 network

starting and stopping the platform

validating the platform

monitoring, managing and maintaining the platform

upgrading the platform license

installing and maintaining TSU/TSC signaling hardware

configuring the platforms TSU/TSC hardware and software

expanding the platform.

xi

Contents and Structure


The contents and structure of this guide are as follows:
Chapter

Contents

Chapter 1, Preparing for


HP OpenCall SS7.

Details the hardware and software pre-requisites that must


be in place before the procedures in this guide can be used.
Also describes the operating conditions of the platform and
provides a guide to installing a platform from scratch.

Chapter 2, Installing the


HP OpenCall SS7
Software.

Describes now to install the HP OpenCall SS7 software.

Chapter 3, Configuring the


Platform.

Describes how to perform the initial configuration of the


platform and start it up.

Chapter 4, Configuring the


SS7 Network.

Describes how to configure the SS7 network from the


platform.

Chapter 5, Validating the


Platform.

Provides procedures for validating the High Availability of


the platform and the operation of SNMP traps.

Chapter 6, Managing and


Monitoring the Platform.

Provides a number of procedures concerned with


monitoring, managing and maintaining the platform.

Chapter 7, Upgrading the


Platform License.

Describes how to upgrade your HP OpenCall SS7 platform


license.

Chapter 8, Installing a
TSU.

Provides procedures for installing a new Telecom Signaling


Unit (TSU) and its associated Telecom Signaling Cards
(TSCs).

Chapter 9, Maintaining
TSU/TSC Hardware.

Describes the maintenance procedures for TSUs and


in-system TSCs, including common procedures that are
referenced from other procedures in this guide.

Chapter 10, Configuring


TSU/TSC Hardware.

Describes how to configure TSUs, TSCs and LAN cards.

Chapter 12, Updating


TSCs and SS7 Links.

Details how to update the SS7 link capacity of the platform.

xii

Chapter

Contents

Chapter 11, Expanding


Platform Processing
Capability.

Describes how you can expand the processing capability of


your platform without changing the hardware.

Chapter 13, Expanding


Your Platform: Adding a
Back End.

Describes how to add a back-end computer dedicated to


application processing.

Appendix A, Tools
Catalog.

Contains a tools reference that lists and describes the tools


that are available with HP OpenCall SS7.

Appendix B, Telecom
Signaling Cards (J3527A
and J3528A).

Contains a detailed description of Telecom Signaling Cards


(TSCs).

Appendix C, Telecom
Signaling Units (J3401A),

Contains a detailed description of the Telecom Signaling


Unit (TSU) which can be used to the accommodate TSCs.

Appendix D, Configuring
the Application Guardian.

Describes how to configure PIC/AG.

xiii

Associated Documentation
The following guides are on the HP OpenCall SS7 3.1 on Linux
CD-ROM:
Table 1

Guides on the HP OpenCall SS7 3.1 on Linux CD-ROM

HP OpenCall SS7
Application Developers
Guide

Describes the HP OpenCall SS7 APIs. In particular, it


describes how to design and develop user applications to run
on ISUP or TUP.

HP OpenCall SS7
Conformance and
Compliance Statements

Outlines platform conformance and compliance to ANSI and


ITU-T protocols.

HP OpenCall SS7
Glossary

Defines terms used in the documentation set.

HP OpenCall SS7
Operations Guide

Describes how to install and configure the platform and SS7


network, how to start, stop and monitor the platform, and how
to use the platform management tools. The guide also includes
SS7 hardware (TSC and TSU) installation and maintenance
procedures, as well as platform expansion procedures.
It contains information on the SS7 Monitor, configuration
files, and the SNMP traps generated by the platform.

HP OpenCall SS7 TSU


and TSC Starter Sheet

Describes the safety regulations and conformance to


international standards for TSUs and TSCs.

HP OpenCall SS7
Troubleshooting Guide

Describes how to troubleshoot an HP OpenCall SS7 platform.

HP OpenCall SS7
Welcome Guide

Describes the main features of the platform.

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

HP OpenCall SS7 Release Notes

This document contains release-specific


information. In particular, it gives details of the
HP Opencall SS7 packages, the servers supported,
the Linux distributions supported and the
associated patches (if any).

HP OpenCall SS7 Software


Installation QuickStart Guide

This guide contains a procedure for installing


HP OpenCall SS7 version 3.1 on Linux from
scratch.
The procedure in this guide applies if the platform
has never had HP OpenCall SS7 installed.

xv

We Welcome Your Comments


Your feedback on these manuals is very important to us.
You can contact us by e-mail at the following address:
opencall_docs@hp.com
You can also mail your comments to:
Hewlett-Packard Company,
OpenCall Business Unit,
38053 GRENOBLE Cedex 9,
France

xvi

Preparing for HP OpenCall SS7


This chapter firstly describes important precautions you should take
when installing HP Opencall SS7 hardware. It then describes the
HP OpenCall SS7 user access, the configuration pre-requisites, the
platforms operating conditions and first time installation guidelines.

Chapter 1

17

Preparing for HP OpenCall SS7


Important Safety Precautions for Hardware Installation

Important Safety Precautions for Hardware


Installation
It is important that you read this section before attempting any of the
hardware installation and maintenance procedures in this guide.

Physical Safety Precautions


The following instructions are important for your safety and for the
functioning of the HP OpenCall SS7 platform. Read the instructions
carefully before attempting the installation.

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

When told to connect a hardware unit to a power supply, for your


safety you must always connect it to a grounded wall outlet.

Chapter 1

Preparing for HP OpenCall SS7


Important Safety Precautions for Hardware Installation
Always use the power cord supplied with the TSU or one with a properly
grounded plug (a DC powered TSU must only be used with the HP
J3401-60201 power cord). If a power cord is not supplied, select the
proper power cord according to your local national electric code. Ensure
that the cable meets your country's standards for safety. For example:

USA - use a UL listed type SVT detachable power cord.

Canada - use a CSA certified detachable power cord.

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.

The server cabinet must be independently grounded so that when


you remove the power cable any static charge passes to ground.
The mat and strap are available in the HP 9300-1155 Workstation
Kit. All components must be placed on an anti-static mat if you have
taken them out of their anti-static bag.

Avoid carpeting and clothing that produce static charges (wool,


nylon, silk) and avoid unnecessary movements.

Do not touch components on the cards. Handle the cards only by


their edges, face plates or extractor levers. When inserting or
removing printed cards, do not touch any other components.

Saving Your Configuration


CAUTION

Chapter 1

Before performing any of the HP OpenCall SS7 hardware procedures in


this guide, save your current configuration using the cfgMgr -copy
command. Save your new configuration using the cfgMgr -copy
command after completing the installation.

19

Preparing for HP OpenCall SS7


User Access for Software Configuration

User Access for Software Configuration


To configure a platform, you must log in as a privileged user. The table
below summarizes the different possibilities:
Table 1-1

Access Permissions

User

Access Level

root

Full access to whole platform,


including HP OpenCall SS7.

ocadmin

Default privileged user for


HP OpenCall SS7.

other user

root can grant privileged access to


HP OpenCall SS7 to other members
of the ocadmin group

Configuration Required
none

Add default environment variables


to the users profile.
Add default environment variables
to the users profile. See
Authorizing Access for Other
Users on page 21.
Configure the users .rhosts file.
There are several references in the
procedures to creating or modifying
the file ~ocadmin/.rhosts.
For other users, the file
~<other_user_name>/.rhosts
should be created or modified
instead. Other users must belong to
the group ocadmin.

The package installation creates:

the user ocadmin

the group ocadmin

the directory /home/ocadmin

These must not be removed.

20

Chapter 1

Preparing for HP OpenCall SS7


User Access for Software Configuration
The appropriate environment variables are also added to both ocadmin
and root profiles.
The HP OpenCall SS7 files and directories are handled when configuring
the platform. The root user must not create or modify any files or
directories belonging to the HP OpenCall SS7 file system layout, except
when using the supported command line tools.

NOTE

All files in the HP OpenCall SS7 configuration directories, and the


directories, must be owned by a member of the group ocadmin.

Most platform commands can be used by the ocadmin user, however,


some require root access. Refer to the Tools Catalog in Appendix A,
Tools Catalog.

Authorizing Access for Other Users


If you want users other than root and ocadmin to have access to the
platform tools or man pages, you must add the default environment
variables to each users profile:
PATH=$PATH:/opt/OC/bin
MANPATH=$MANPATH:/opt/OC/share/man

This is done automatically for the ocadmin and root users.


Any users that you want to access the platform, must be members of the
ocadmin group.

Chapter 1

21

Preparing for HP OpenCall SS7


HP OpenCall SS7 Operating Conditions

HP OpenCall SS7 Operating Conditions


The HP OpenCall SS7 product operates under the conditions and
constraints described below.

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

To prevent unnecessary switchovers, the LANs must be dimensioned so


that peak traffic (< 60% of bandwidth) does not saturate them, as this
would delay the FTC and stack heartbeats and HP Opencall SS7 data
traffic.

NOTE

The LANs must be either Ethernet (100-BaseT) or FDDI.

Only two IP addresses with the same hostname are supported by


HP OpenCall SS7. If you want to add another IP address, you must give
it a new hostname.
Bridges or routers between hosts within the platform are not supported.

22

Chapter 1

Preparing for HP OpenCall SS7


HP OpenCall SS7 Operating Conditions
Figure 1-2

Bridges/Routers Between Hosts

Router
Bridge

Host_1

Host_2

NOTE

In the case of a GDI configuration, each GDI signaling LAN should be on


a separate, dedicated IP subnet.

Inter Back End


LANs

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

Preparing for HP OpenCall SS7


HP OpenCall SS7 Operating Conditions

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.

Date, Time and Synchronizing Clocks


NTP Synchronization
HP OpenCall SS7s High Availability component is compatible with ntp
synchronization, without any special procedures that need to be followed.
Setting the Date and Time
Front-end Hosts HP OpenCall SS7s High Availability component
allows you to change the date and time on front-end hosts, with the
following restrictions:

Perform the clock-jump on the standby user-application, not the


active application.

TCAP, SCCP, and MTP timers set by user-applications and API


timers that are set before the clock jump, are not guaranteed to
function. If your application can recognize a clock jump, it is
recommended (but not required) that you clear the buffers.

Platform Manager The management processes run on the Platform


Manager, which are not highly available, do not support a clock jump.

24

Chapter 1

Preparing for HP OpenCall SS7


First Time Installation Overview

First Time Installation Overview


This table below provides an overview of how to install an
HP OpenCall SS7 platform from scratch. It outlines the different
installation tasks and provides references to the required procedures in
this guide. Once you have carried out these tasks, you will have a fully
operational platform.

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:

An appropriate distribution of the


Linux Operating System.

The relevant components of the


HP Opencall Enablement Kit.

The HP Opencall SS7 3.1 on Linux


software.

References
Refer to Chapter 2, Installing the
HP OpenCall SS7 Software, on
page 27.

At the end of this task, you will have a


platform without SS7 hardware, but with
a pre-defined stubbed configuration.
2

Install the required SS7 hardware (TSUs


and/or TSCs), but do NOT configure the
hardware at this stage.

If you wish to use TSU/TSC


hardware, refer to Stages 1, 2 and 3
in Chapter 8, Installing a TSU, on
page 111.
If you have a TSC-in-System
platform, refer to Installing a TSC in
a Host Server on page 159.

Configure the platform.

Chapter 1

Refer to Chapter 3, Configuring the


Platform, on page 45.

25

Preparing for HP OpenCall SS7


First Time Installation Overview

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

Configure the SS7 network connections.

Refer to Chapter 4, Configuring the


SS7 Network, on page 67.

Validate the platform.

Refer to Chapter 5, Validating the


Platform, on page 85.

Chapter 1

Installing the HP OpenCall SS7


Software
The purpose of this chapter is to describe how to install
HP OpenCall SS7 3.1 on Linux.

Chapter 2

27

Installing the HP OpenCall SS7 Software


Overview

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

If you have a machine on which HP has pre-installed the


HP OpenCall SS7 3.1 on Linux software, you can omit this chapter.

The installation of HP OpenCall SS7 3.1 on Linux consists of three


general phases, dealt with in separate sections of this chapter, as follows:
Phase

Installation Task

Section Reference

Install an appropriate distribution of


the Linux operating system.

Installing Linux for HP OpenCall


on page 32

Install the components of the


HP OpenCall Enablement Kit that
allow HP OpenCall SS7 to be used with
Linux

Installing HP OpenCall Enablement


Kit Components for Linux on
page 35

Install the HP OpenCall SS7 software

Installing HP OpenCall SS7 3.1 on


Linux on page 37

The section that follows gives the prerequisites for the installation.

28

Chapter 2

Installing the HP OpenCall SS7 Software


Prerequisites

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:

Linux: During the configuration of the HP OpenCall SS7 platform,


some Linux system files are modified and several commands are
used for configuration and customization.

HP OpenCall SS7 administration.

Documents
During the installation of HP OpenCall SS7, you should have the
following documents at hand:

Linux Installation Manuals

HP OpenCall SS7 3.1 on Linux Documentation Set

HP OpenCall SS7 3.1 on Linux Release Notes

License codeword for HP OpenCall SS7 3.1 on Linux

Hardware
Installation of the host servers of your platform must be complete before
starting any of the software installation procedures.

NOTE

It is not necessary to have installed the SS7 hardware (TSU/TSC) before


starting this software installation. This is done later.

The minimum physical memory required is:

Chapter 2

256 MB additional memory for a single Local Point Code (LPC)


platform
29

Installing the HP OpenCall SS7 Software


Prerequisites

256 MB additional memory needed for each extra LPC

The virtual memory (VM) required by LPC depends on the number of


Destination Point Codes (DPCs) configured on the network:

24 MB for 50 DPCs:
50 DPCs, 100 routes
50 DPCs (Remote SP), 100 Sub-System Numbers (SSNs)
500 Global Title (GT) entries

27 MB for 200 DPCs:


200 DPCs, 400 routes
200 DPCs (Remote SP), 400 SSNs
2048 GT entries

33 MB for 512 DPCs:


512 DPCs, 1024 routes
512 DPCs (Remote SP), 1024 SSNs
2048 GT entries

52 MB for 1024 DPCs:


1024 DPC, 4096 routes
1024 DPC (Remote SP), 4096 SSNs
4096 GT entries

30

Chapter 2

Installing the HP OpenCall SS7 Software


Prerequisites

ISUP and TUP requirements


The requirements for TUP and ISUP in non distribution mode are as
follows:

100 MB for 1024 DPCs:


1024 DPC, 100,000 circuits configured

The requirements for ISUP configured in CIC-based distribution mode


are calculated as follows:

For each LPC configured with CIC-based distribution: 65 MB

For each application 15 + (Number of configured CICs/1000) MB

Example of the calculation for a single LPC platform hosting 20 primary


applications, 20 secondary applications with the maximum number of
configured CICs (100, 000)
65 + 40 x 15 + 100 = 765 MB

Software
To install the software, you need the following CDs:

Chapter 2

Linux operating system (appropriate distribution)

HP OpenCall Enablement Kit

HP OpenCall SS7 3.1 on Linux software

31

Installing the HP OpenCall SS7 Software


Installing Linux for HP OpenCall

Installing Linux for HP OpenCall


The first phase of software installation is to install a distribution of the
Linux operating system with which the HP OpenCall SS7 software is
compatible. This section provides guidelines for this installation. For
details of the installation procedure, you must refer to the user
documentation for the appropriate distribution of Linux.
Refer to the HP OpenCall SS7 3.1 on Linux Release Notes for an
up-to-date list of the supported distributions of Linux.

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.

In order to install your chosen distribution of Linux, follow the guidelines


given below in conjunction with the user documentation for the relevant
Linux distribution. Note that not all the guidelines may be relevant to all
distributions.

32

Chapter 2

Installing the HP OpenCall SS7 Software


Installing Linux for HP OpenCall
Installation Type

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

Minimum Size (MB)

/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

Select a boot loader of the type LILO.

Host Name

Replace the default hostname with your own choice of hostname.

Firewall

Choose to have no firewall.

User Account

Set up a user account with username ocadmin.

Definition of the User and Group ocadmin


Even when the Network Information Service (NIS) is used to define user
ocadmin and group ocadmin,the ocadmin users home directory must
always be located in a local /home/ocadmin directory not on the
auto-mounted network file system (NFS). In this case, the
HP OpenCall SS7 installer does not create a new ocadmin user and
group but installs the files in the existing user account.
If NIS is not used, HP OpenCall SS7 creates a local ocadmin user and
local ocadmin group on your system.

Chapter 2

33

Installing the HP OpenCall SS7 Software


Installing Linux for HP OpenCall
Packages

Install the following packages from the given sections:

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

Installing the HP OpenCall SS7 Software


Installing HP OpenCall Enablement Kit Components for Linux

Installing HP OpenCall Enablement Kit


Components for Linux
This section describes how to install the components of the HP OpenCall
Enablement Kit that are required in order to use HP OpenCall SS7 3.1
on Linux. You must perform this installation before installing the
HP OpenCall SS7 software.

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.

Step 1. Log in as root.


Step 2. Insert the CD for the HP OpenCall Enablement Kit into your machine,
mount the CD and move to the top level directory of the CD.
For Red Hat 7.3, enter the following commands:
# mount /dev/cdrom /mnt/cdrom -o ro
If you do not specify the -o ro (read-only) option, the following message
is displayed:
/dev/cdrom is write protected, mounting read-only
# cd /mnt/cdrom
For the Debian distribution, enter the following commands:
# mount /dev/cdrom /cdrom
# cd /cdrom

Chapter 2

35

Installing the HP OpenCall SS7 Software


Installing HP OpenCall Enablement Kit Components for Linux
Step 3. Install the relevant components of the kit by entering the following
command:
For Red Hat Linux:
# ./install.sh -re
For Debian:
# sh install.sh -re
An installation wizard runs that automatically detects the Linux
distribution installed on your machine and installs the appropriate kit
components.
Step 4. Unmount and remove the CD.
For Red Hat Linux:
# cd /
# umount /dev/cdrom
For Debian:
# cd /
# umount /cdrom

36

Chapter 2

Installing the HP OpenCall SS7 Software


Installing HP OpenCall SS7 3.1 on Linux

Installing HP OpenCall SS7 3.1 on Linux


This section describes how to install the HP OpenCall SS7 software. The
procedure assumes that:

NOTE

you have installed a supported distribution of Linux on your


machine, as well as the necessary components of the HP OpenCall
Enablement Kit.

you have a clean system on which no HP OpenCall SS7 software has


been previously installed.

If you do not have an appropriate distribution of Linux installed on your


machine (see the HP OpenCall SS7 3.1 on Linux Release Notes for the
compatible distributions), refer back to Installing Linux for
HP OpenCall on page 32.

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

a static IP address and an IP network mask

the default gateway static IP address; if you do not have a gateway,


use the local system IP address.

the domain name server (DNS), if any.

37

Installing the HP OpenCall SS7 Software


Installing HP OpenCall SS7 3.1 on Linux

Stage 1: Configuring the IP Network


This stage describes how to configure the IP network to which your
machine is connected.
Actions
Step 1. Log in as root.
Step 2. Obtain the identifier of the network device (eth0, eth1,...) of the LAN
Ethernet interface by running the command mii-tool (refer to the man
page for this command for more information).
You will use this identifier below for the DEVICE field.
Step 3. Create a network configuration, as follows:
a. Create a systemconfig.conf configuration file from the template
provided by copying it using the command
# cp -p /etc/systemconfig/systemconfig.template.conf
/etc/systemconfig/systemconfig.conf
b. Modify the file /etc/systemconfig/systemconfig.conf (that you
have just created) according to your network configuration. See below
for guidance.
[NETWORK]
HOSTNAME = <hostname>
DOMAINNAME = <domain.name>
# Information for DNS resolution (up to 3 nameservers)
# These lines must be commented out if not used
DNS1 = <IP address for name server 1>
DNS2 = <IP address for name server 2>
# Set up the default Gateway
GATEWAY = <Gateway IP address>
#the following is optional, if not specified will be
DOMAINNAME from above
# SEARCHDOMAINS = janesworld.cluster cluster
[INTERFACE0]
DEVICE = <Ethernet Device> # e.g. eth0
TYPE = static
IPADDR = <IP Address> # e.g. 15.128.10.134
NETMASK = <IP Network Mask> # e.g. 255.255.248.0

38

Chapter 2

Installing the HP OpenCall SS7 Software


Installing HP OpenCall SS7 3.1 on Linux
c. Run the command systemconfigurator to take into account the
network configuration, as follows:
# systemconfigurator --confignet
Step 4. Skip this step for the Debian distribution of Linux.
For the Red Hat 7.3 distribution of Linux, modify the hostname
configuration to replace the fully qualified hostname with a shorter,
non-qualified hostname.
Change the file /etc/sysconfig/network as follows:
Replace:
HOSTNAME = <hostname.domain.name
with
HOSTNAME = <hostname>
Step 5. Configure the host as follows:
a. At the command prompt, enter the hostname using the command
# hostname <hostname>
Note that you must specify the hostname and not the fully qualified
domain name.
b. Modify the file /etc/hosts so that the format of each entry is
<IP address> <host name> <fully qualified domain name>
as in the following example:
127.0.0.1

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

Installing the HP OpenCall SS7 Software


Installing HP OpenCall SS7 3.1 on Linux

# /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

Installing the HP OpenCall SS7 Software


Installing HP OpenCall SS7 3.1 on Linux

Stage 2: Installing the HP OpenCall SS7 Software


This stage describes how to install the HP OpenCall SS7 3.1 on Linux
software from the CD provided and how to check the installation.
Actions
Step 1. Log in as root.
Step 2. Insert the HP OpenCall SS7 3.1 on Linux CD into your machine, mount
the CD and move to the top level directory of the CD.
For Red Hat Linux 7.3, enter the following commands:
# mount /dev/cdrom /mnt/cdrom -o ro
If you do not specify the -o ro (read-only) option, the following message
is displayed:
/dev/cdrom is write protected, mounting read-only
# cd /mnt/cdrom
For the Debian distribution, enter the following commands:
# mount /dev/cdrom /cdrom
# cd /cdrom
Step 3. To install the HP OpenCall SS7 packages from the CD, enter the
following command:
For Red Hat Linux:
# ./install.sh -i (for a SDK installation use the -sdk option)
For Debian:
# sh install.sh -i (for a SDK installation use the -sdk option)
Step 4. Unmount and remove the CD.
For Red Hat Linux:
# cd /
# umount /dev/cdrom

Chapter 2

41

Installing the HP OpenCall SS7 Software


Installing HP OpenCall SS7 3.1 on Linux
For Debian:
# cd /
# umount /cdrom

42

Chapter 2

Installing the HP OpenCall SS7 Software


Installing HP OpenCall SS7 3.1 on Linux
Step 5. Check that the appropriate HP OpenCall SS7 packages have been
installed. For Red Hat Linux , enter:
# rpm -qa | grep hpoc
For Debian, enter:
# dpkg -lhpoc*|grep ii
For an up-to-date list of the required packages, refer to the
HP OpenCall SS7 3.1 on Linux Release Notes. An example list of
packages is given below:
hpoc-ss7-linux-wrapper-0.2-8
hpoc-ss7-nettl-0.2-8
hpocconfiguration-0.2-8
hpocconfiguration-0.2-9
hpocha-0.2-8
hpocisup-0.2-8
hpocsecurity-0.2-8
hpocss7-0.2-8
hpocss7drivers-0.2-8
hpocsupportability-0.2-8
hpoctup-0.2-8
Result
The HP OpenCall SS7 3.1 on Linux packages are now installed on your
machine.

Chapter 2

43

Installing the HP OpenCall SS7 Software


Installing HP OpenCall SS7 3.1 on Linux

Stage 3: Validating the Installation


This stage describes how to validate your installation of
HP OpenCall SS7 3.1 on Linux. It involves loading a pre-defined
configuration (supplied with the software) in order to allow the
validation to be performed. Note that no SS7 hardware is used with this
pre-defined configuration and it is not necessary for the SS7 hardware to
be connected to the platform at this stage.
You must perform the actions below for each host of your platform.
Actions
Step 1. Log in as ocadmin.
Step 2. Generate a pre-defined configuration using the cfgMgr command as
follows:
cfgMgr -resetTemplate 2
Step 3. Install the configuration using the command
cfgInstall from /var/opt/OC/working_config/platform_2
Step 4. Start the SS7 stacks using the command ss7Start.
Step 5. Check that all stacks are active, using the command ocftstatus. Repeat
this action until all processes are active.
Step 6. Once all processes are active, check the SS7 network configuration, as
follows:
a. Start the HP OpenCall SS7 Management tools by entering
ss7MgrStart.
b. From the main menu of the SS7 Monitor, select Monitor Entities and
then MTP.
c. In each sub-menu, check that MTP, Destination/Route and
Link/Linkset are all ACTIVE.

NOTE

44

To continue with the installation of your platform, refer to First Time


Installation Overview on page 25 for a guide to the remaining
installation tasks.

Chapter 2

Installing the HP OpenCall SS7 Software


Installing HP OpenCall SS7 3.1 on Linux
Result
HP OpenCall SS7 3.1 on Linux is successfully installed on your platform.

Chapter 2

45

Installing the HP OpenCall SS7 Software


Installing HP OpenCall SS7 3.1 on Linux

46

Chapter 2

Configuring the Platform


This chapter describes how to configure the HP OpenCall SS7 platform
for the first time and how to modify an existing configuration.
These are off-line configurations.

Chapter 3

45

Configuring the Platform


Overview

Overview
Configuring the HP OpenCall SS7 platform consists of the following:

Creating a new configuration (note that a number of pre-defined


configurations are also available).

Modifying the new configuration to use the correct values for your
system.

Installing the configurationthis moves the new or updated


configuration from the saved state to the running state. Note that
when the configuration is updated for a running system, the modified
configuration files will not be used until the platform has been
stopped and restarted.

Propagating the configurationthis copies the new or modified


configuration onto all systems in the platform, ensuring consistency.

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

Configuring the Platform


Overview

When updating the configuration for a running system, after the


modified configuration files have been installed (and are in a running
state) they will not be used until the platform has been stopped and
restarted.

NOTE

Configuration States
A configuration can be in one of two states:

savedlocated in the directory /var/opt/OC/working_config/

runninglocated in /etc/opt/OC

The table below summarizes what happens to the configuration files in


different situations:
Table 3-1

Configuration File States


Task

Create new configuration


or modify existing saved
configuration

Action

Result

Create configuration

Configuration is in saved
state

Modify configuration

Modified configuration still in


saved state

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

Changes saved to directory

47

Configuring the Platform


Overview
Table 3-1

Configuration File States (Continued)


Task

Modify running
configuration

Action

Result

Modify configuration

Modified configuration is in
running state

Save configuration

Running configuration copied


to saved statedirectory
named so as not to overwrite
any other saved
configurations
Note:
If you do not explicitly save
your modified configuration,
no backup copy of it exists.

48

Propagate configuration

Running configuration copied


to all other systems in
platform

Check configuration

Configuration validated.

Chapter 3

Configuring the Platform


Creating a New Configuration

Creating a New Configuration


This section describes how to create and install a new platform
configuration. Note that HP OpenCall SS7 3.1 on Linux includes a set of
pre-defined configurations. If you wish to use one of these, refer to
Installing a Pre-defined Configuration on page 52.

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

To create a new configuration:


Step 1. Define the Configuration
Before any communication can occur between the host and the network,
the system must be configured: the SS7 network must know which units,
cards, ports and links it is communicating with.
In order to work this out:
a. Draw a map of your system configuration, showing the components.
b. Find out detailed configuration information for each component using
the commands ss7TsuPing and ss7TscPing.
Step 2. Create the new configuration.
a. Run cfgCreate on the Platform Manager

WARNING

Do not create the configuration directly in /etc/opt/OC

Step 3. Run cfgInstall to move the new configuration to running state


Step 4. Configure the hardware.
a. To discover the hardware, use the cfgSs7HwCreate command.

Chapter 3

49

Configuring the Platform


Creating a New Configuration
b. To complete the configuration and create the links, use the cfgSs7Hw
command.
Step 5. To adjust the TCAP, SCCP, and MTP parameters for each stack
(Classname), use the cfgTcap, cfgSccp, and the cfgMtp commands.
Step 6. Make any necessary changes to the system parameters in the sys.*
files.
Step 7. If desired, scale your TCAP performance level using the cfgTcap
command.

NOTE

If you have a 2-host/duplex platform, you must perform Step 8 and


Step 9. Otherwise, go from Step NOTE to Step 10 .

Step 8. Configure the HP OpenCall SS7 LAN to the associated hostIpaddress


using the cfgPlatform -add -ocLan command line. For further
information, see the corresponding man page.
Step 9. Run cfgPropagate -all to propagate the new platform configuration
and the SS7 LAN configuration. Always propagate configurations from
the same host (Platform Manager or Front End).
Step 10. Run cfgCheck on the Platform Manager.
This ensures that all the necessary files are present and, on a 2-host
system, checks that the configuration on both hosts is consistent.
Step 11. Check and load the hardware configuration.
The command ss7HwInit checks that the configuration is valid, and if it
is, loads it. When you run the command, if the configuration is valid, the
following message appears,
Configuration successfully loaded in shared memory

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

Configuring the Platform


Creating a New Configuration
Once you have downloaded the configuration to the TSU, run one or both,
of the following commands to check the status of the TSU and TSCs.

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.

The platform is now ready for operation.

Chapter 3

51

Configuring the Platform


Installing a Pre-defined Configuration

Installing a Pre-defined Configuration


This section describes how to install one of the pre-defined platform
configurations provided with HP OpenCall SS7 3.1 on Linux. The
available configurations are listed and described in the
HP OpenCall SS7 3.1 on Linux Release Notes.

NOTE

If you wish to create your own platform configuration, refer to Creating


a New Configuration on page 49.

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.

Step 1. Log in as ocadmin.


Step 2. Generate the pre-defined configurations using the cfgMgr command
(refer to the man page for this command for more information).
For example, for a 2-host/duplex platform, the command is of the form:
cfgMgr -resetTemplate all -license <codeword> -host1 <host1>
-host2 <host2>
where <codeword> is your license codeword.
Step 3. Choose one of the pre-defined configurations; refer to the
HP OpenCall SS7 3.1 on Linux Release Notes for a list of the available
configurations.
Note the Platform ID of your chosen configuration.
Step 4. Install your chosen configuration using the command:
cfgInstall -from /var/opt/OC/working_config/platform_<id>
If you make a mistake, reset the configuration using the cfgMgr tool.
For more information on cfgInstall and cfgMgr, refer to their man
pages.

52

Chapter 3

Configuring the Platform


Installing a Pre-defined Configuration
Step 5. Configure the hardware.
a. To discover the hardware, use the cfgSs7HwCreate command.
b. To complete the configuration and create the links, use the cfgSs7Hw
command.

NOTE

If you have a 2-host/duplex platform, you must perform Step 6 and


Step 7. Otherwise, go from Step 5 to Step 8 .

Step 6. Configure the HP OpenCall SS7 LAN to the associated hostIpaddress


using the command:
cfgPlatform -add ocLan
For more information, see the corresponding manpage.
Step 7. Run cfgPropagate -all to propagate the new platform configuration
and LAN configuration. Always propagate configurations from the same
host (Platform Manager or Front End).
Step 8. Run cfgCheck on the Platform Manager.
This ensures that all the necessary files are present and, on a 2-host
system, checks that the configuration on both hosts is consistent.
Step 9. Check and load the hardware configuration.
The command ss7HwInit checks that the configuration is valid, and if it
is, loads it.
If the configuration is valid the following message is displayed:
Configuration successfully loaded in shared memory
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 the
problem.

Chapter 3

53

Configuring the Platform


Installing a Pre-defined Configuration
Step 10. Check the links.
Once you have downloaded the configuration to the TSU, run one or both,
of the following commands to check the status of the TSU and TSC(s).
ss7TsuStatus -u <tsuId> -C -L
This command checks the status of the TSU itself, the TSC(s) it contains
and the links belonging to it.
ss7TscStatus -c <tscId> -L
This command checks TSC status.
The platform is now ready for operation.

54

Chapter 3

Configuring the Platform


List of Commands Used in Configuration

List of Commands Used in Configuration


You configure your platform using the following commands:

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

Back up your existing configuration before making any changes to your


platform.

55

Configuring the Platform


Configuring Relocatable IP Addresses using PINS

Configuring Relocatable IP Addresses using


PINS
This IP network high availability feature is integrated in
HP OpenCall SS7 by means of PINS (Plug-In Network Sensor).

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

Re-assignment of the virtual IP addresses to a PINS configured LAN


port on the host where the PINS is active.

Respawning of the PINS process by the FTC when the PINS process
has failed.

Triggering a local or remote LAN switchover upon LAN failure.

Chapter 3

Configuring the Platform


Configuring Relocatable IP Addresses using PINS

Figure 3-1

Broadcast of re-ARP requests to the network to overwrite existing


ARP tables on a remote machine that are still referring to the MAC
address of the previous LAN interface used by the PINS process.

PINS on an HP OpenCall SS7 Platform

Active
Host

Active
Host

Platform
Manager

Active
PINS

Standby
PINS

Application

Application

Private LAN

Floating IP Address

Public LAN

Public LAN

INTERNET

Remote
Application

Requirements for PINS


For PINS to function properly, you must take account of the following:

Chapter 3

57

Configuring the Platform


Configuring Relocatable IP Addresses using PINS

The LANs controlled by PINS should be plugged on independent


switch hubs to avoid Single Point Of Failures.

Two LAN interfaces must be available and configured for PINS


usage.

Neighborhood machines must be able to receive and accept re-ARP


requests. Therefore, network elements (such as switch hubs) that
mask such requests should not be used.

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:

Nic = <ethx> [,priox]


where <ethx> is the Linux distribution name (eth0, eth1, ...) of LAN
access on which a static IP address has been configured.
This is optionally followed by its priority (value 1 for the highest
priority and 2 for the lowest one).
The Nic parameter MUST be set at least one time, and may be
repeated:
Nic = ethx [,priox]
Nic = ethy [,prioy]

IpAddress = <relocatable IP> <floating Ip netmask>


A relocatable IP address associated to the LAN access, together with
its subnet mask.

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

Configuring the Platform


Configuring Relocatable IP Addresses using PINS
'R' for only remote LAN switch (2-host platform only).

CAUTION

All other parameters and sections are reserved for internal use. Do
not change or remove them.

NOTE

For a 2-host platform, the PINS configuration should be installed in


the same way, and at the same time on both hosts, to ensure that the
dual NICs have the same Linux distribution name. For example, if on
one host the 2 NICs are named eth12 and eth14, the 2 NICs on the
second host must be named eth12 and eth14.

Step 2. To activate the PINS process, you must edit the ftc.conf file in the
directory:

- for the running configuration:


/etc/opt/OC/HA

- for saved configurations:


/var/opt/OC/working_config/<platform_id>/HA

Add the following lines to the [pins] section:


[pins]
RunDirectory = /var/opt/OC/logs
RunString = /opt/OC/lbin/pinsrun
ProcessType = HA
ProcessGroup = 0
Step 3. Run cfgPropagate to propagate the configuration.
Step 4. Stop and restart the Front-End platform(s).

Deactivating the PINS Process


Remove the [pins] section from the ftc.conf file then stop and restart
the platform.
The PINS feature is still configured and can be re-activated by repeating
Steps 2 to 4 in the above procedure.

Chapter 3

59

Configuring the Platform


Configuring Relocatable IP Addresses using PINS

Monitoring and Operating PINS


Local Switch
The command:
PINS_localSwitch -h<host> IP_1 <NIC>
requests a local LAN switch to the PINS running on the specified host
(the default is the local host), on the specified LAN access to the specified
NIC. The LAN access and NIC names must be the same as in the
pins.conf file.
Remote Switch
A remote switch can be forced from the Platform Monitor by requesting a
PINS process switch.
PINS HA Status
The floating IP address is available only for the active PINS process as
seen from the Platform Monitor. It can be seen as the alias of a PINS
LAN using the netstat -rn shell command on the host where the active
PINS is located.
The command:
PINS_getState -h<host> IP_1
displays on the standard output the configured NIC states on the
specified host (the default is the local host). The active NIC is marked
with a star ('*')
.

60

Chapter 3

Configuring the Platform


Configuring the Domain Name Server (DNS)

Configuring the Domain Name Server (DNS)


HP OpenCall SS7 supports systems using DNS-based name/address
resolution provided that:

The file /etc/host still contains the primary name/address


resolution scheme, that is, the file /etc/nsswitch exists and
contains the following entry:
hosts: files dns <more>
where <more> stands for additional resolution schemes.
See nsswitch.conf for the list of addition resolution schemes.

Additional resolution schemes:


On Linux any name/address resolution scheme is supported,
provided that the Name Service Caching Daemon nscd is installed,
properly configured and started.
See ncsd.conf for details.
This sample section from the file /etc/ncsc.conf configures host
name / address resolution caching:
enable-cache
positive-time-to-live
negative-time-to-live
suggested size
check-files

yes
3600
20
211
yes

The OC administrator must also activate ncsd on Linux, when the


DNS being used is not on the same physical LAN as the
HP OpenCall SS7 system and is not dedicated to OpenCall DNS
traffic.

The system name returned by uname -n must not be on the Fully


Qualified Domain Name (FQDN)i:
$ uname -n
tarifal
$ uname -n
toto.grenoble.hp.com

Chapter 3

hosts
hosts
hosts
hosts
hosts

(GOOD)
(BAD)

61

Configuring the Platform


Configuring the Domain Name Server (DNS)

127.0.0.1
15.128.130.92
15.128.130.93
15.128.130.94
15.128.130.95

62

The format of the /etc/hosts file contents is shown in the following


example:

localhost
foo
foo1.hp.com
foo2
foo3.hp.com

localhost.localdomain local
foo.grenoble.hp.com
foo1

#
#
#
#
#

OK
OK
BAD
OK
BAD

Chapter 3

Configuring the Platform


Starting and Stopping HP OpenCall SS7

Starting and Stopping HP OpenCall SS7


You can start the HP OpenCall SS7 software either automatically or
manually. However, do not try to start a system manually if you have
already configured an automatic start, as this results in a second
instance of the FTC trying to start.

NOTE

To provide an HA service, you must use an automatic start.

Configuring Automatic Start-up


Step 1. Add the command ss7Start to the end of the file /etc/inittab so that
HP OpenCall SS7 starts after ntp. Uncomment the line as shown below:
hpoc:3456:respawn:/opt/OC/bin/ss7Start -foreground
/var/opt/OC/logs/ss7Start.log 2>&1

>

Step 2. As root, run the command init q so that the file is re-read and the
changes are taken into account.

Starting the Platform Manually


You can also run the ss7start command manually from the command
line. Do this either as ocadmin or as root.

Stopping HP OpenCall SS7


To stop HP OpenCall SS7:
Step 1. If necessary, prevent an automatic restart. This is required for certain
maintenance tasks. See Preventing Automatic Start-up on page 64.
Step 2. Run the command ss7Stop -ftc. This stops the FTC and HA processes
(FTC, SS7 Stack and SS7 Waiter) started by the FTC.

NOTE

Chapter 3

The Platform Management tools stop when you stop HP OpenCall SS7.

63

Configuring the Platform


Starting and Stopping HP OpenCall SS7
Preventing Automatic Start-up
To prevent an automatic ss7Start respawn in inittab:
Step 1. Comment out the line containing the ss7Start command:
hpoc:3456:respawn:/opt/OC/bin/ss7Start -foreground
/var/opt/OC/logs/ss7Start.log 2>&1

>

Step 2. As root, run the command init q to force init to re-read inittab.

64

Chapter 3

Configuring the Platform


Validating the Configuration

Validating the Configuration


This means checking that the platform configuration is valid.
It involves checking the configuration from an OS viewpoint and from an
HP OpenCall SS7 viewpoint.

Checking from an OS Viewpoint


Check the following OS configuration files:

/etc/hosts

~ocadmin/.rhosts

/etc/inittab

Checking from an HP OpenCall SS7 Viewpoint


You can do this using cfgCheck as follows:
cfgCheck [-config <configuration-directory>]

cfgCheck checks the configuration at two levels:

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.

To display on-line help, type:


cfgCheck -help

Chapter 3

65

Configuring the Platform


Validating the Configuration

66

Chapter 3

Configuring the SS7 Network


This chapter describes how to configure the network. The stack must be
running to carry out the configuration described in this chapter.

Chapter 4

67

Configuring the SS7 Network


Introduction

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:

Administratorallowing both configuration and monitoring


(the ss7MgrStart command starts SS7 Monitor in this mode)

Operatorallowing monitoring only

The procedures described in this chapter must be carried out in


Administrator mode. For information on changing between modes, see
Changing the SS7 Monitor Mode on page 95.

NOTE

You can quit the SS7 Monitor at any time by pressing (Q)uit.

SS7 Monitor Interface


The Administrators Monitor Main Menu provides these options:
1. Configure Entities
2. Monitor Entities
3. Single Entity Statistics

68

Chapter 4

Configuring the SS7 Network


Introduction
Moving between
Parameters

Use the following keys to move between parameters:


key

function

move down one parameter

move up one parameter

spacebar

move down one window

backspace

move up one window

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

To enter commands, enter the first letter, that is shown between


parentheses in the display. For example, to (c)heckpoint, enter c. To
choose a menu item, enter the number that appears next to it.

Refresh rate

For some windows there is at least a 2 second delay in refreshing. The


SS7 Monitor polls the state of the signaling units every 15 seconds.

Information for 2-Host Platforms


On a 2-host platform, network configuration is not possible while the
stack processes are synchronizing. The configuration must not be
changed while the platform is executing this process. Use the
ocftstatus command to determine the state of the stack.

Chapter 4

69

Configuring the SS7 Network


Configuring the Network

Configuring the Network


Configuring the network consists of the following steps:
Step 1. Check that the stack is running. See Starting and Stopping
HP OpenCall SS7 on page 63.
Step 2. Start SS7 monitor, by entering ss7MgrStart.
Step 3. From the main menu, choose Configure entities. From this window
you have the following options:
1. lpc
2. MTP
3. SCCP
Step 4. Enter the new configuration. This includes adding links/linksets,
destination point codes, and so on. Refer to the SS7 Monitor on-line help,
and to the Guidelines for Network Configuration for further
information.
Step 5. Save your configuration by entering c to checkpoint.
Step 6. Restart the stack. The configuration loads and MTP activates
automatically.

NOTE

Backup your changes frequently, by entering c for checkpoint.

Guidelines for Network Configuration


Configure your SS7 network entities by building a configuration from the
physical layers of the network, such as links and linksets, to the higher
protocol levels, such as SCCP and global title translations.
You must configure the LPCs first.
You can configure the following entities at a later time. This order is
recommended but not required:

70

Chapter 4

Configuring the SS7 Network


Configuring the Network

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

Destinations/Routesthese are configured from the MTP window

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

You cannot directly modify an LPC on an existing configuration. If you


want to change the LPC, you must create a new network configuration as
described in the section Creating Different Network Configurations on
page 81.

For an explanation of LPC aliases, see the HP Opencall SS7 Application


Developers Guide.
Virtual Point Codes (VPCs) and Virtual Users (VUs)
Virtual Point Codes (VPCs) are non-physical point codes than enable
each SS7 stack to have up to 16 point codes. Virtual Users (VUs) are user
applications that send and receive traffic through the VPCs.
VPCs can be configured using the configure entities | LPC window, and
VUs can be configured using the configure entities | SCCP window.
Alternatively, both VPCs and VUs can be configured using the
ss7oamtool command.

Chapter 4

71

Configuring the SS7 Network


Configuring the Network
MTP
Links/Linksets

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

The following example demonstrates how to configure destinations and


routes.
The example configures a primary and secondary route from LPC 1 to
DPC 3. In the case of the primary route, DPC 3 is both the APC and the
DPC.

Step 1. With the Configure MTP Entities Menu displayed select


Destinations/Routes
72

Chapter 4

Configuring the SS7 Network


Configuring the Network
Step 2. Enter: a 3
Step 3. Enter a d 2
Step 4. Enter a r p 3 3
Step 5. Enter a r s 3 2
SCCP
Peer Point Code

Only an LPC can have a peer point code.

Setting the
concerned
parameter

Use the following table to decide if you need to set the concerned
parameter to y or n.

If you...

...then enter this value

want to broadcast management information to a


particular PC

do not want to broadcast management


information

have a stack configuration of more than 50 DPCs


and do not want your system flooded with
management messages

have a stack configuration of more than 50 DPCs


and still need some management messages

y, but only for APCs. Otherwise you


may flood your system with
management messages

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.

If you have this standard at the DPC...

...then enter this value

ITU-T 88 (Blue Book)

0 (default)

ITU-T 92 (White Book)

ANSI 88

0 (default)

Chapter 4

73

Configuring the SS7 Network


Configuring the Network

If you have this standard at the DPC...

...then enter this value

ANSI 96 - no ISNI

10

Configuring
Global Title
Translations

In the Configure Global Title Translations window, the following


abbreviations are used:

Table 4-1

Global Title Translations


Abbreviation

Meaning

NP

Numbering Plan

TT

Translation Type

NAI

Nature of Address Indicator

DPC

Destination Point Code

SSN

Sub-System Number

Prio

Priority

Under Address a backslash \ can be used as a void character. The


numbers following the backslash are then ignored. For example, 800\
can be used to represent all 800 numbers.
Priority Field

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

If you want the global title translation to be done by a remote node,


configure the remote node (Remote SP) without a remoteUser (SSN). To
modify or remove an SSN, create a new network configuration as
described in the section Creating Different Network Configurations on
page 81.

Chapter 4

Configuring the SS7 Network


Configuring the Network
GDI Stack
The overall procedure for configuring a GDI stack using the SS7 Monitor
is the same as for any other SS7 stack.
Step 1. Configure your LPC and any LPC aliases on the SS7 Stack using the
MTP Entities menu. Refer to Local Point Codes and Aliases on page 71.
Do not configure any of the other values in the MTP or SCCP Entities
menus if you are configuring the stack for GDI. This is because the same
stack cannot support TCAP over GDI and TCAP over SCCP. If you want
to support these different protocols on the same platform it is necessary
to use a multiple-stack configuration.
Step 2. Select GDI from the Configure Entities menu and enter the DGPCs and
IP addresses corresponding to your configuration.

NOTE

Connections may be closed by the SS7 Stack in the case of an IP protocol


error. If this happens the connection is not reactivated automatically.
The HP Opencall GDI Server accepts client connections only if a TCAP
application is connected to SSN 256. Otherwise, the connection is
refused.

Configuring GDI
as a Client

By default, a GDI host is configured as a server. If you want your GDI


host to act as a client, you must edit the file sys.classname.gdi by hand refer to the files comments to help you. You must add the line:
platformMode:

CLIENT;

after the line:


portNumber:

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

Configuring the SS7 Network


Configuring the Network
Configuring ISUP/TUP Applications Online
This section describes how to update an existing ISUP/TUP
configuration without stopping the application.
See also the IsupDynamicConfiguration(3) man page.
Step 1. Use the cfgIsup or the cfgTup command with the -dynamic option.
In dynamic mode, you can do the following:

Add or remove DPC(s). You cannot change the configuration of an


existing DPC. To obtain the same end result, remove the DPC you
want to change, then add a new one with the same name and
modified parameter values.

Add or remove CIC(s), or modify circuit parameters.

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

Configuring the SS7 Network


Configuring the Network
Answer any questions put by the command. When the log file indicates
that both the reload and the dump are complete, the command prompts
you to confirm the changes. When you enter y to do so, the ISUP/TUP
configuration file is up to date and the changes come into use. If you
choose not to confirm your changes, restart the application to restore the
old values.
For an HA configuration (one primary and at least one secondary
application):

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.

Step 5. After reloading the primary application, the secondary application(s)


must be stopped and restarted in order to synchronize it with the
primary application.

Chapter 4

77

Configuring the SS7 Network


Configuring the Network
ISUP CIC-based distribution
For CIC-based distribution, you must assign a set of CIC(s) to each
primary ISUP application instance. To change the CIC(s) currently
assigned to a running application id, you must first remove the CIC(s)
and then add it (or them) to another application.
For example, the range DPC= 3, and CIC [125-256] are currently
assigned to application id 2. This application id is running. To re-assign
this range (DPC=3, CIC [125-256]) to application id 4, proceed as follows:
Step 1. Use the cfgIsup command to remove DPC=3, CIC [125-256] from the
configuration for application id 2.
Step 2. Use ss7IsupReload to reload application id 2.
Step 3. Use the cfgIsup command to add DPC=3, CIC [125-256] to the
configuration for application id 4 using the cfgIsup command.
Step 4. Use ss7IsupReload to reload application id 4.
Step 5. Check that the change is effective using the cfgIsup -view command.
For a description of ISUP CIC-based distribution, see the HP Opencall
SS7 Application Developers Guide.

78

Chapter 4

Configuring the SS7 Network


Saving the Network Configuration

Saving the Network Configuration


Save your network configuration frequently as you work, and every time
you finish the stack configuration. In the context of SS7 Monitor, this is
referred to as checkpointing.
On a 2-host platform the configuration is saved to both SS7 hosts. When
HP OpenCall SS7 starts, it automatically loads the most recently
checkpointed configuration and activates MTP level 3.
You can checkpoint your configuration from with the SS7 Monitor, or
from the command line.

Checkpointing the Configuration using SS7 Monitor


If you made some changes, you are prompted to checkpoint in the
following situations:

when you leave the Configure Entities sub-menu

when you enter the (q)uit command

after several minutes (default value is 5 minutes) of inactivity within


the submenus

You can also checkpoint at anytime by typing C if this option is shown in


your window.

Checkpointing from the Command Line


You can checkpoint from a prompt using the ss7Checkpoint command.

Chapter 4

79

Configuring the SS7 Network


Loading your Network Configuration

Loading your Network Configuration


Loading the
Default
Configuration

By default, when HP OpenCall SS7 starts, it loads the reference


configuration file created by checkpointing. See Saving the Network
Configuration on page 79. If no reference file exists, an empty
configuration file is loaded.

Loading a
Non-Default
Configuration

To load a configuration file other than the reference configuration file,


use the loadconf command, using the -f option to specify the file to
load.

NOTE

All configuration files must be owned by a member of the group ocadmin.

80

Chapter 4

Configuring the SS7 Network


Creating Different Network Configurations

Creating Different Network Configurations


Use this procedure to create and use several identical platform
configurations with different network configurations. This will allow you
to switch easily between the different configurations (mainly for test and
development purposes).
Follow the steps below to configure and save the configurations. Steps 3
to 7 must all be done on the same host.
Step 1. On one host, save your current configuration using the ss7CheckPoint
command.
Step 2. Stop the stack on both hosts
Step 3. On one host, save the installed configuration using the cfgMgr -copy
command.
Step 4. Remove the reference files stored in the directory /etc/opt/OC/SS7
using the command:
rm Saved.<className>.conf.ref Saved.<className>.conf
Step 5. Restart the stack on one host.
Step 6. Configure your new network using the SS7 Monitor.
Step 7. Checkpoint the new configuration.
Step 8. Save the newly checkpointed configuration.
Use the cfgMgr -copy command.
Step 9. Start the other host. The new configuration is now running.
At any later stage, you can switch between the available configurations
using the cfgInstall command.

NOTE

Chapter 4

All files in the HP OpenCall SS7 configuration directories must be


owned by a member of the group ocadmin.

81

Configuring the SS7 Network


Configuring ANSI Routing

Configuring ANSI Routing


This section describes how to configure ANSI Routing.

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.

Full Point Code Routing


The configuration procedure is different depending on whether the
network is already configured.

82

Chapter 4

Configuring the SS7 Network


Configuring ANSI Routing
Configuring Full Point Code Routing
The following procedure explains how to enable Full Point Code routing
in an existing SS7 network configured in cluster routing.
Step 1. Checkpoint your network configuration.
Step 2. Run the cfgMtp command with the -pcRoute option set to full.
Step 3. Stop and restart the stack on both hosts. The checkpointed configuration
is automatically reloaded, but the system is now running in Full Point
Code routing mode.
Step 4. Add all the DPCs and routes that were previously implicitly handled by
DPC with member ID set to 0. For example, if in a remote cluster you
have DPC 2.5.0, 2.5.1 and 2.5.2, you must add DPC 2.5.1 and 2.5.2 (2.5.0
being already declared in the file generated by ss7CheckPoint). You
must also declare the corresponding routes.
Step 5. Checkpoint your configuration again, and propagate it if necessary.
Configuring Full Point Code Routing with no Existing SS7
Network
Step 1. Run the cfgMtp command with the -pcRoute option set to full.
Step 2. Stop and restart the stack on both hosts. The checkpointed configuration
is automatically reloaded, but the system is now running in Full Point
Code routing mode.
Step 3. Use the SS7 Monitor to configure your SS7 network. Define all DPC and
routes one by one.
Step 4. Checkpoint your configuration, and propagate it if necessary.

Chapter 4

83

Configuring the SS7 Network


Validating SS7 Connectivity

Validating SS7 Connectivity


This means checking that alignment is possible at MTP2 and MTP3
levels and that it is possible to connect at MTP3 level.

Prerequisite
Step 1. Connect the TSC cables to the SS7 network.

Aligning at MTP2 Level


Step 1. To align up to MTP2 level, you can use the hardware diagnostic tool.
This tool is described in the HP OpenCall SS7 Troubleshooting Guide.

Aligning at MTP3 Levels


Step 1. Start the SS7 stack(s) using the ss7Start command.
Step 2. Start SS7 Monitor using the ss7MgrStart command.
Step 3. Configure the destinations, linksets, and links.
Step 4. To align at MTP3 level, activate MTP using the SS7 Monitor.
1. In SS7 Monitor (which you started in Step 2), select Monitor
entities, select MTP, and if the MTP state is INACTIVE, select
Activate MTP.
2. After a while, the MTP state should change to ACTIVE.
Step 5. In the monitor entities/lk/lkset menu, check that all links become
active.
In case of problem, refer to the section on traffic problems in the
HP OpenCall SS7 Troubleshooting Guide.

Connecting an Application at MTP3 Level


You can check that it is possible to connect at MTP3 level in either of the
following ways:

84

Chapter 4

Configuring the SS7 Network


Validating SS7 Connectivity

Generate traffic using trafgen. Use the /opt/OC/bin/trafgen


command.

Generate traffic using the MTP tutorials.


MtpClient and MtpServer are the names of the MTP tutorials. They
are located in the /opt/OC/tutorial directory.

If MTP traffic is generated, then the connection was successful.

Chapter 4

85

Configuring the SS7 Network


Validating SS7 Connectivity

86

Chapter 4

Validating the Platform


This chapter describes the platform validation that is not covered in the
other chapters of the guide. In particular, it covers validating the High
Availability (HA) of the platform and checking that SNMP traps have
been configured.

Chapter 5

85

Validating the Platform


Validating High Availability (HA)

Validating High Availability (HA)


Validating HA means ensuring the platform is OK from an HA
viewpoint. This involves:

Checking the state of the stack processes.

Checking the state of the LANs.

Checking the Stack Process States


You do this as follows.
Step 1. Start the SS7 stack(s), using the ss7Start command, on one host at a
time.
Step 2. Look at the process states (displayed by the ocftstatus command).
The possible process states are:

ACTIVE

BOOTING

DOWN

SYNCHRONIZING

UNKNOWN

In Parallel Engine mode, the stacks should be ACTIVE on both hosts.

Checking that the LANs Are OK


You do this as shown below.

86

Chapter 5

Validating the Platform


Validating High Availability (HA)
Figure 5-1

Dual LANs

Step 1. Retrieve information about the LAN interfaces, hostnames, and IP


addresses of the Dual LANs. You can do this by executing the netstat
-i and netstat -in commands.
Step 2. Check LAN1.

Physically disconnect LAN1 from Host A.

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.

Perform a ping on LAN2.

Reconnect LAN1 to Host A.

Wait for the establishment of traffic, then perform a ping on LAN1.

Step 3. Check LAN2 (as is described in step 2 for LAN1).

Chapter 5

87

Validating the Platform


Validating SNMP Traps Operation

Validating SNMP Traps Operation


Validating SNMP operation means checking that SNMP Traps have
been configured and that they have been activated.

Checking That SNMP Traps Have Been Configured


To check that SNMP Traps have been configured for HP OpenCall SS7,
you must:
Step 1. Check that the SNMP master agent has been configured to send SNMP
Traps using the cfgPlatform -view -snmpTrapAgent command.
See Working with SNMP Traps on page 101.

Checking That SNMP Traps Are Active


To check that SNMP Traps are active with HP OpenCall SS7, you must:
Step 1. Check that the SNMP master agent is running (snmpd).
You can do this as follows:
ps -ef | grep snmpd

Step 2. Check that nettl is running.

88

Chapter 5

Validating the Platform


Validating the SNMP TCAP Agent Operation

Validating the SNMP TCAP Agent Operation


Validating SNMP TCAP Agent means checking that SNMP TCAP Agent
has been configured and it has been activated.
There is one SNMP TCAP Agent per stack (className).
This feature is optional and not activated by default.

Checking That the SNMP TCAP Agent Has Been


Configured
To check that the SNMP TCAP Agent has been configured for the
selected stack (className), you must:
Step 1. Check that the SNMP TCAP Agent has been configured using the
cfgPlatform -view -snmpTcapAgent command.
See Configuring the SNMP TCAP Agent on page 103.

Checking That the SNMP TCAP Agent Is Active


To check that the SNMP TCAP Agent is active for a selected stack
(className), you must:
Step 1. Check that the SNMP TCAP Agent is running.
You can do this as follows:
ps -ef | grep ss7TcapSnmpAgent | grep <className>

Chapter 5

89

Validating the Platform


Validating the SNMP TCAP Agent Operation

90

Chapter 5

Managing and Monitoring the


Platform
This chapter contains a number of procedures and information that are
useful for monitoring, managing and maintaining the platform.

Chapter 6

91

Managing and Monitoring the Platform


Starting and Stopping the Platform Management Tools

Starting and Stopping the Platform


Management Tools
NOTE

HP OpenCall SS7 must be running before you can start the platform
management tools.

Starting the SS7 Monitor


To start the SS7 Monitor enter the ss7MgrStart command. You can
monitor and configure the SS7 network using the SS7 Monitor.
SS7 Monitor can run in two modes:

Administratorallowing both configuration and monitoring


(the ss7MgrStart command starts it in this mode)

Operatorallowing monitoring only

Refer to Changing the SS7 Monitor Mode on page 95 for instructions on


changing between these modes.
See the SS7 Monitor on-line help for information on the parameters
displayed.
See Configuring the Network on page 70 for guidelines on configuring
the SS7 network.

Stopping the Platform Management Tools


Use the ss7MgrStop command to stop the platform management tools
and kill any running processes. Enter it with one of the following options:

92

-allStops all management processes.

-selectPrompts you to specify the process(es) to kill.

Chapter 6

Managing and Monitoring the Platform


Monitoring HP OpenCall SS7 Processes

Monitoring HP OpenCall SS7 Processes


To monitor the state of HP OpenCall SS7 processes, use the ocftstatus
command. Processes can be in one of the following states:
Table 6-1

Process States

State

Meaning

Active

Process is handling platform functions

Degraded

Process is on-line, but not performing at optimum level - maintenance may


be required to upgrade service

HotStby

Process is acting as hot standby, ready to take over control of a service

Switching

Process is becoming active

Synchro

Process is synchronizing with the active process. If a switchover happens


during synchronization, no service is provided to existing clients

Stopping

Process is going down

ColdStby

Process is available to become active, but is not synchronized with the


current active process

Booting

Process is rebooting

Down

Process is down

Unknown

No information is available on process state

Chapter 6

93

Managing and Monitoring the Platform


Changing the State of HP OpenCall SS7 Processes

Changing the State of HP OpenCall SS7


Processes
To force a change on an HP OpenCall SS7 process, use the ocftcontrol
command (see the man page).
For instance, you can use the following options:

ki option to kill a defined process

sw option to switch processes

ru option to start and restart a process

Use -c option to select the process.


In 2-host mode, you must also choose the host you want your actions to
apply to.
Check the changes using the ocftstatus command line.

94

Chapter 6

Managing and Monitoring the Platform


Monitoring the SS7 Network Using the SS7 Monitor

Monitoring the SS7 Network Using the SS7


Monitor
To monitor the SS7 network, use the SS7 Monitor. You can do this in
either Operator or Administrator mode.
The Monitor Entities and Single Entity Statistics menu items let you
monitor and get statistics on the SS7 network and about hardware
status. These menus can be accessed in Operator (non-privileged) mode,
as well as in Administrator mode. Refer the SS7 Monitor on-line help for
details on the information provided.
See SS7 Monitor Interface on page 68 for information on syntax and
navigation.

Changing the SS7 Monitor Mode


To switch between the available modes, edit the file
/etc/opt/OC/management/mgtProcessList.conf to comment out the
lines that you do not require:
# To start Administrator SS7 Monitor(s)
$BINPATH/ss7AdmMon -C $CLASSNAME_1 -typeName $TYPENAME_1
# To start Operator SS7 Monitor(s)
#$BINPATH/ss7OpeMon -C $CLASSNAME_1 -typeName $TYPENAME_1

Available Network Entities


Using the Operators interface, you can monitor the following:

Chapter 6

Hardware State

MTP

SCCP

TCAP

GDI

95

Managing and Monitoring the Platform


Monitoring the SS7 Network Using the SS7 Monitor

Monitoring MTP
If you choose MTP from the main menu, you can choose to monitor one of
the following:

MTP

Destinations / Routes

Links / Linksets

Monitoring Overall MTP Layer Traffic


From the Monitor MTP window you can activate, deactivate, and
monitor the overall traffic of the MTP layer of the SS7 stack.
Monitoring Destinations/Routes
From the Monitoring Destinations/Routes window you can activate,
deactivate, and monitor the status of destinations, or individual routes to
one destination. The window shows the states as defined in the
ITU-T/ANSI recommendations.

NOTE

As soon as one route leading to a destination is congested, the


destination is declared congested even if there are other uncongested
routes leading to that destination.

Search

Use the (S)earch function (type S) to find a particular destination point


code.

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

Managing and Monitoring the Platform


Monitoring the SS7 Network Using the SS7 Monitor
Monitoring Links/Linksets
From the Monitoring Links/Linksets window you can activate,
deactivate, inhibit, uninhibit and monitor the status of links to adjacent
DPCs.
You can also monitor overall traffic on the linksets.
Abbreviations used in this window are as follows:

in the column AIOC, A = Active, I = Inhibit, O = Out of Service, C =


Congested, ---- = inactive

Rx %Use = percentage link utilization rate for reception

Tx %Use = percentage link utilization rate for transmission

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

Use the (S)earch function (type S) to find a particular destination point


code.
Linkset/Link Activation Behavior

When the Stack


Starts

The activation behavior of Link/Linkset is automatic if the links have


been configured, that is your links become ACTIVE. If a Signaling Unit
has a status of ONLINE, the link(s) pass from INACTIVE, to
OUT_OF_SERVICE to ACTIVE.
If the Signaling Unit has a status other than ONLINE or STANDBY, the
Signaling Unit is reloaded until it has an ONLINE or STANDBY state,
and then the links will pass through the states as described above.

When the Stacks


Switchover

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

When a destination is out-of-service, because of a network problem


(remote destination not responding to alignment procedure, for example)
you cannot inhibit all the links of a linkset. You must first deactivate the
failed destination.

Chapter 6

97

Managing and Monitoring the Platform


Monitoring the SS7 Network Using the SS7 Monitor
Starting Up After a If a switchover occurs when the MTP is not active, it means that
Switchover
synchronization failed. In this case, stop the synchronization before you
(Active/Standby
re-start. You should:
Mode Only)
1. Stop the synchronization.
2. Activate MTP.
3. Re-start synchronization.

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.

Single Entity Statistics


The following options are available:

MTP

Linkset

Link

SCCP

TCAP

The statistical data for the selected entity is updated every few seconds.

98

Chapter 6

Managing and Monitoring the Platform


Monitoring the SS7 Network Using the SS7 Monitor
MTP
From this window you can see the MTP statistics for the local point code.
Linkset Enter the identifier of the linkset that you want to monitor.
Link Select a link that you want to monitor.
SCCP
Enter S, then enter the entity (select from 1 to 5) and parameters that
you want to monitor:
Example:
(2) Local User

[ 2 <ssn> ]: in this case, enter 2 then the ssn.

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

Managing and Monitoring the Platform


Viewing Logs

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

Managing and Monitoring the Platform


Working with SNMP Traps

Working with SNMP Traps


HP OpenCall SS7 provides an SNMP traps mechanism that can be used
in conjunction with an SNMP manager such as HP Openview. The
HP OpenCall SS7 SNMP agent, ss7SNMPAgent, maps Cause and Action
logs to SNMP traps. The ss7SNMPAgent is a sub-agent of the SNMP
master agent. The way traps are sent is defined in the SNMP master
configuration file.

Configuring SNMP Traps


To set up SNMP traps, do the following:
Step 1. When creating your initial configuration, configure the SNMP agent
process. Use the cfgPlatform command with the -add -snmpTrapAgent
option.
See Checking That the SNMP TCAP Agent Is Active on page 89.
Step 2. If the master agent is running, login as root and stop it with the
command.
/etc/init.d/snmpd stop
Step 3. Edit or add the trapsess and trap2sink fields of the
/etc/snmp/snmpd.conf file to point to the destination for SNMP traps.
Copy this file to all hosts in your platform and add:
trapess <hostname> <community>
trap2sink <hostname> <community>
Step 4. Restart the master agent with the snmpd command:
/etc/init.d/snmp start
Step 5. Stop and restart the stack so that the modifications are taken into
account.
Step 6. In order to work with HP Openview:
a. Copy the following file onto your management station:
/etc/opt/OC/management/OpencallSS7_trapd.conf

Chapter 6

101

Managing and Monitoring the Platform


Working with SNMP Traps
b. On the management station, run the following command:
$OV_BIN/xnmevents -merge OpencallSS7_trapd.conf

Displaying a List of Available Traps


To list the available traps, enter the following command:
ss7SNMPAgent -displayTrapDoc.
Logs can be one of the following types: Informative, Warning, Minor
and Major.

102

Chapter 6

Managing and Monitoring the Platform


Working with the SNMP TCAP Agent

Working with the SNMP TCAP Agent


The ss7TcapSnmpAgent is a proxy agent. It provides access to the TCAP
managed objects (only for GET operations) of an SS7 stack of the
HP OpenCall platform. In a multi-stack environment, one
ss7TcapSnmpAgent can be started for each SS7 stack.

Configuring the SNMP TCAP Agent


To set up the SNMP TCAP Agent, do the following:
Step 1. When creating your initial configuration, configure the SNMP TCAP
Agent process. Use the cfgPlatform command with the -add
-snmpTcapAgent options.
See Checking That the SNMP TCAP Agent Has Been Configured on
page 89.
Step 2. If the master agent is running, login as root and stop it with the
command:
/etc/init.d/snmpd stop
Step 3. Edit or add (if missing) the master agentx field if the
/etc/snmp/snmpd.conf file to point to the destination for SNMP traps.
Copy this file to all hosts in your platform.
Step 4. Restart the master agent with the snmpd command:
/etc/init.d/snmp start
Step 5. Stop and restart the stack so that the modifications are taken into
account.
Step 6. In order to work with HP Openview:
a. Copy the following file onto your management station:
/etc/opt/OC/management/OpencallSS7_trapd.conf
b. On the management station, run the following command:
$OV_BIN/xnmevents -merge OpencallSS7_trapd.conf

Chapter 6

103

Managing and Monitoring the Platform


Working with the SNMP TCAP Agent

Displaying a List of Available TCAP Objects


To list the available TCAP Objects, enter the following command:
ss7TcapSnmpAgent -classname <classname> - snmpIndex<number>
-displayText or -displayHtml.

104

Chapter 6

Upgrading the Platform License


This chapter describes how to upgrade your platform license. Online and
offline procedures are presented.

Chapter 7

105

Upgrading the Platform License

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

Upgrading the Platform License


Offline Procedure

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

Upgrading the Platform License


Online Procedure

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

Upgrading the Platform License


Displaying Licensing Information

Displaying Licensing Information


To display licensing information, enter the following command:
hostname $ cfgPlatform -view -license
This returns a display like this:
Keyword: Type: PLATFORM
Licensing disabled option is: OFF
License Serial Number: 00000000
Links Number: Maximum of 64
State of features:
Application Guardian is
Application Message Dispatcher is
BackEnd is
High Availability is
Generic Data Interface is
Software Development Kit is

Chapter 7

DISABLED
DISABLED
ENABLED
ENABLED
DISABLED
DISABLED

109

Upgrading the Platform License


Displaying Licensing Information

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

Before attempting the installation, refer to the HP OpenCall SS7


TSU and TSC Starter Sheet. This provides important
information, including regulatory information and conformance
statements.
Also read the safety notices in Important Safety Precautions for
Hardware Installation on page 18. Failure to do so may result in
damage to your hardware or to yourself.

The TSU/TSC installation procedure is described in the following stages,


where each stage is detailed in a dedicated section:
Stage

112

Description

Section Reference

Install your Telecom Signaling


Cards and LAN card into the TSU.

Stage 1: Installing Cards in the TSU on


page 114

Install the Telecom Signaling Unit


into a server cabinet.

Stage 2: Installing the Telecom Signaling


Unit in the Server Rack on page 116

Connect the TSU to the host(s).

Stage 3: Connecting the TSU to the


Platform on page 118

Check and configure the hardware.

Stage 4: Checking and Configuring the


Hardware on page 121

Chapter 8

Installing a TSU
Overview

NOTE

Chapter 8

If you are installing a TSU in a new platform, perform Stages 1, 2 and 3,


and then to continue with your platform installation refer to First Time
Installation Overview on page 25 for a guide to the remaining
installation tasks.

113

Installing a TSU
Stage 1: Installing Cards in the TSU

Stage 1: Installing Cards in the TSU


NOTE

This section describes how to install cards into a new TSU.


If you wish to add an additional TSC to an existing TSU, or replace a
TSC or LAN card in an existing TSU, refer to Chapter 9, Maintaining
TSU/TSC Hardware.

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

Do not mix different Telecom Signaling Card types in a single TSU. To


use more than one TSC type with your platform, you must install each
TSC type in a separate TSU.

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

Ensure that the TSU is powered OFF before installing cards.

Install the cards as described in the procedure below:


Step 1. Before handling the cards, take anti-static precautions by wearing a
grounding wrist strap.
Step 2. Remove the cover of the Telecom Signaling Unit, as described in
Removing the TSU Cover on page 168.
Step 3. Remove the card cage from the TSU, as described in Removing the Card
Cage on page 170.
Step 4. If you need to install an additional LAN card, insert the card into slot L1
in the TSU, as described in Adding a Card to a TSU on page 171.
If you wish to install a TSC in slot 5 (which is adjacent to slot L1), do this
(as described in Step 4) before securing the card brackets again.
Do NOT connect the LAN cards to the hosts yet.
Step 5. To install a TSC into the TSU, insert the TSC into an appropriate slot in
the TSU, as described in Adding a Card to a TSU on page 171.
Do NOT connect the network cables yet.
Step 6. Re-insert the card cage into the TSU, as described in Replacing the Card
Cage on page 171.
Step 7. Replace the cover of the TSU, as described in Replacing the TSU Cover
on page 169.

Chapter 8

115

Installing a TSU
Stage 2: Installing the Telecom Signaling Unit in the Server Rack

Stage 2: Installing the Telecom Signaling Unit


in the Server Rack
This section describes how to install your Telecom Signaling Unit (with
cards installed) into a server cabinet.
In order to work through the procedures of this installation, you will
need to refer to the diagram in Figure 8-1 below.
Figure 8-1

Sliding Rails, Brackets and Handles

NOTE

The installation described in this section also refers to an optional


connection panel. This is a metal panel that can be attached inside the
server cabinet to provide a convenient connection interface to the TSCs
within the TSU. Refer to Connection Panels on page 281.

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:

BNC grounded connection panels have round connector holes


with a flat top.

BNC ungrounded connection panels have larger round connector


holes with a flat top.

RJ-45 connection panels have square connector holes.

V.35 connection panels have rectangular connector holes.

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

Stage 3: Connecting the TSU to the Platform


This section describes the connections that must be made to the TSU
(installed in a cabinet server) in order to check the installation.

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.

The subsections below describe the connection procedure and provide


cabling recommendations for connecting more than one TSU to the hosts
of a 2-host platform.

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

TSU Rear Panel Connectors (AC Powered TSU)

Chapter 8

Installing a TSU
Stage 3: Connecting the TSU to the Platform

It is not possible to have a dual LAN connection between a TSU and a


single server.

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)

To connect the TSU to the platform 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

Do NOT connect the TSC cables at the network end yet.

Connect to the
Power Supply

Now power on the TSU by connecting it to a suitable power outlet. The


unit can be powered from an AC or DC supply. Refer to TSU Electrical
and Environmental Specifications on page 290 for details of the
required power supply.

Chapter 8

119

Installing a TSU
Stage 3: Connecting the TSU to the Platform

Cabling Recommendations for 2-Host Platforms


The cabling recommendations below allow you to determine your TSU Id
settings. The diagram in Figure 8-3 shows an example for two TSUs.

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

Cabling Recommendations for Two TSUs

Chapter 8

Installing a TSU
Stage 4: Checking and Configuring the Hardware

Stage 4: Checking and Configuring the


Hardware
NOTE

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.

Checking the Hardware Installation


Follow the procedure below to check that the hardware you have
installed is operating correctly.
Step 1. Power on the TSU.
Step 2. Check the LEDs on the TSU and the TSCs. See Checking LEDs on
page 175 for information on the LEDs and their meaning.
Step 3. Check that the TSU and TSCs are reachable by running ss7TsuPing -v
(as root or as ocadmin) on one of the hosts.

Configuring the Hardware


Once you have checked your hardware installation, you must define the
configuration for your TSU. This includes details of the TSU, TSCs, ports
and links. The configuration must then be installed on the host(s).
This is described in the sections TSU Configuration: Installing TSU(s)
in a New Platform on page 184 and TSU Configuration: Adding
Another TSU to an Existing Platform on page 186 - choose the
appropriate configuration procedure, depending on whether you are
installing the TSU in a new or existing system.
As part of this procedure, you will connect the TSC cables 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

Maintaining TSU/TSC Hardware


Overview

Overview
The maintenance procedures provided in this chapter are listed in the
table below along with references to the relevant sections.
Description

Section Reference

How to add, replace or remove a hardware


component of a host server (such as a CPU,
LAN card etc).

Replacing, Removing or Adding a


Hardware Component in the Host on
page 124

How to replace a faulty fan in a TSU.

Replacing a Fan in a TSU on page 126

How to replace an AC power supply in a


TSU

Replacing a TSU DC Power Supply


(J3401-60200) on page 132

How to replace a DC power supply in a TSU

Replacing a TSU DC Power Supply


(J3401-60200) on page 132

How to replace a faulty TSU card cage that


contains the PCI backplane and CPU card.

Replacing the TSU Backplane and CPU


Card on page 135

How to replace an add-on LAN card (for a


2-host platform) in a TSU.

Replacing a LAN Card in a TSU on


page 139

How to add a new Telecom Signaling Card


to a TSU.

Installing an Additional TSC in a TSU on


page 143

How to replace a Telecom Signaling Card in


a TSU.

Replacing a TSC in a TSU on page 145

How to remove a Telecom Signaling Card


from a TSU (without replacing it).

Removing a TSC from a TSU on page 149

How to replace a Telecom Signaling Unit.

Replacing a TSC in a TSU on page 145

How to remove a Telecom Signaling Unit


from a platform.

Removing a TSU from a Platform on


page 157

How to add a new Telecom Signaling Card


to a host server.

Installing a TSC in a Host Server on


page 159

How to replace a Telecom Signaling Card in


a host server.

Replacing a TSC in a Host Server on


page 161

122

Chapter 9

Maintaining TSU/TSC Hardware


Overview

Description

Section Reference

How to remove a Telecom Signaling Card


from a host server (without replacing it).

Removing a TSC from a Host Server on


page 164

How to replace a 4-port TSC cable that


connects a Telecom Signaling Card to the
SS7 network.

Replacing a Four-Port TSC Cable on


page 167

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

It is important that you read the safety and anti-static notices


provided in Important Safety Precautions for Hardware
Installation on page 18 before attempting to follow any of the
maintenance procedures described in this chapter. Failure to do
so may result in damage to your hardware or to yourself.
Also ensure that you save your platform configuration, as
described in Saving Your Configuration on page 19.

Chapter 9

123

Maintaining TSU/TSC Hardware


Replacing, Removing or Adding a Hardware Component in the Host

Replacing, Removing or Adding a Hardware


Component in the Host
This procedure describes how to proceed if you want to replace a
hardware component of a host (card, disk array, PDU, CPU, and so on). It
can be used for any actions requiring the shutdown of 1 host.

NOTE

This procedure does not apply to replacing, adding or removing TSCs in a


host server. For these procedures, refer to the relevant sections in this
chapter.

NOTE

Although this procedure does not disturb the traffic on a 2-host platform,
it stops all the traffic of a 1-host platform.

In this procedure, host A is stopped, and host B is the remaining host if


the platform is 2-host. Except for Step 3, which must be done as root, all
the following steps should be done while logged in as ocadmin.
Step 1. Carry out the following checks for 2-host platforms.
a. Check the state of the hardware on host B. Run ss7TsuPing -v and
check the state of the LANs of host B, and the state of the TSUs (if
wrongly configured, traffic will be lost when you stop the host).
b. Check the stacks on both hosts are active. You can do this using the
ocftstatus command.
Step 2. Stop HP Opencall on host A: ss7Stop -all.
Step 3. As root, shutdown host A.
Step 4. Replace, remove or add the hardware component:
a. Power off host A.
b. Replace, remove or add the hardware element. See the server
documentation.
c. Power on host A.
124

Chapter 9

Maintaining TSU/TSC Hardware


Replacing, Removing or Adding a Hardware Component in the Host
d. Check the installation of the hardware element. See the server
documentation
Step 5. Start HP OpenCall SS7 on host A by running the command ss7Start.
Note that the Destination Point Code platform must also be running.
Step 6. Check the state of the hardware by running ss7TsuPing -v on a
front-end host. In particular, check the state of the LANs for TSC-in-TSU
platforms, and the state of the TSCs for TSC-in-system platforms.
Checks

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

Repeat the procedure, reversing your actions in Step 4.

Chapter 9

125

Maintaining TSU/TSC Hardware


Replacing a Fan in a TSU

Replacing a Fan in a TSU


CAUTION

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

TSU with Frontplate

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a Fan in a TSU
Figure 9-2

TSU with Frontplate Removed to Show Fans

To replace a fan, follow the procedure below:


Step 1. Remove the frontplate of the TSU, as follows:
a. Unscrew and remove the two screws on either side of the frontplate.
You will need a Philips screwdriver.
b. Pull the frontplate away from the chassis.
Step 2. Disconnect the fans connector. If you are replacing a fan for the power
supply section (fan 1 or 2), you must disconnect the connectors for both
fans 1 and 2.
Step 3. Unscrew and remove the four screws that hold the fan in place. You will
need a Philips screwdriver.
Step 4. Remove the fan.
Step 5. Insert the replacement fan.

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

Maintaining TSU/TSC Hardware


Replacing a Fan in a TSU
Step 6. Replace and tighten the four screws.
Step 7. Reconnect the fans connector (if you have replaced fan 1 or 2, remember
to reconnect the connectors for both fans 1 and 2).
Step 8. Replace and secure the frontplate.
Step 9. Make sure that the Fan Fault warning LED goes off.

128

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a TSU AC Power Supply (J3401-60100)

Replacing a TSU AC Power Supply


(J3401-60100)
A procedure is presented below for replacing an AC power supply in a
TSU. It is possible to replace a TSU power supply on a running platform
without disturbing the traffic.

CAUTION

This procedure should be performed by HP support personnel. If you


wish to perform the procedure yourself, first contact 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

Be sure to power off the TSU when instructed to do so.

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 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 ss7Stop -all. 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.
Step 4. Disconnect all cables from the rear panel of the TSU and from the SS7
network.

Chapter 9

129

Maintaining TSU/TSC Hardware


Replacing a TSU AC Power Supply (J3401-60100)
Step 5. Remove the TSU from the server cabinet, as described in Removing the
TSU from the Server Cabinet on page 168.
Step 6. Remove the cover of the TSU, as described in Removing the TSU Cover
on page 168.
Step 7. Remove the cover of the power supply unit.
Step 8. Disconnect the power connector (the large white connector) from the
power supply unit.
Step 9. Disconnect the J10 connector which is behind the front panel of the TSU.
Step 10. Disconnect and remove the on/off power input module from the rear
panel. To do this, you will have to remove the wires that connect the
module to the power supply unit.
Step 11. Unscrew the two screws on the rear power supply bracket with a Philips
screwdriver.
Step 12. Remove the power supply unit; slide the power supply bracket forward
towards the frontplate to disconnect the keyhole standoffs, then lift it off.
Step 13. Insert the new power supply unit; line up the keyhole standoffs on the
bottom of the new power supply bracket with those on the cage and slide
the power supply into place.
Step 14. Secure the two screws on the rear power supply bracket with a Philips
screwdriver.
Step 15. Connect and install the new on/off power input module on the rear panel.
To do this, you will have to connect the module to the power supply unit
(to help you, both the wires and the screw terminals are labelled).
Step 16. Reconnect the J10 connector.
Step 17. Reconnect the (white) power connector to the power supply unit.
Step 18. Replace the cover of the power supply unit.
Step 19. Replace the cover of the TSU, as described in Replacing the TSU Cover
on page 169.
Step 20. Insert the TSU back into the server cabinet, as described in Stage 2:
Installing the Telecom Signaling Unit in the Server Rack on page 116.
Step 21. Reconnect all cables to the rear panel of the TSU, but do NOT reconnect
any TSC cables at the network end yet.
130

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a TSU AC Power Supply (J3401-60100)
Step 22. Power on the TSU and check the LEDs on the TSU and the TSCs. See
Checking LEDs on page 175 for information on the LEDs and their
meaning.
Step 23. Reconnect the TSC cables at the network end.
Step 24. 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, you can now restart it. To do this,
run the ss7Start command.
Rollback

Chapter 9

Perform the above procedure again to reinstall the old power supply.

131

Maintaining TSU/TSC Hardware


Replacing a TSU DC Power Supply (J3401-60200)

Replacing a TSU DC Power Supply


(J3401-60200)
A procedure is presented below for replacing a DC power supply in a
TSU. It is possible to replace a TSU power supply on a running platform
without disturbing the traffic.

CAUTION

This procedure should be performed by HP support personnel. If you


wish to perform the procedure yourself, first contact 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

Be sure to power off the TSU when instructed to do so.

You should be logged in as ocadmin.


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 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.

132

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a TSU DC Power Supply (J3401-60200)
Step 4. Disconnect all cables from the rear panel of the TSU and from the SS7
network.
Step 5. Remove the TSU from the server cabinet, as described in Removing the
TSU from the Server Cabinet on page 168.
Step 6. Remove the cover of the TSU, as described in Removing the TSU Cover
on page 168.
Step 7. Remove the cover of the power supply unit.
Step 8. Disconnect the power connector (the large white connector) from the
power supply unit.
Step 9. Disconnect the power supply connector that is attached to the fan board
J8 connector.
Step 10. Disconnect and remove the on/off power input module from the rear
panel. To do this, you will have to remove the wires that connect the
module to the power supply unit.
Step 11. Unscrew the two screws on the rear power supply bracket with a Philips
screwdriver.
Step 12. Remove the power supply unit; slide the power supply bracket forward
towards the frontplate to disconnect the keyhole standoffs, then lift it off.
Step 13. Insert the new power supply unit; line up the keyhole standoffs on the
bottom of the new power supply bracket with those on the cage and slide
the power supply into place.
Step 14. Secure the two screws on the rear power supply bracket with a Philips
screwdriver.
Step 15. Connect and install the new on/off power connector on the rear panel. To
do this, you will have to connect the module to the power supply unit (to
help you, both the wires and the screw terminals are labelled).
Step 16. Reconnect the power supply connector J8 that is attached to the fan
board.
Step 17. Reconnect the (white) power connector to the power supply unit.
Step 18. Replace the cover of the power supply unit.
Step 19. Replace the cover of the TSU, as described in Replacing the TSU Cover
on page 169.

Chapter 9

133

Maintaining TSU/TSC Hardware


Replacing a TSU DC Power Supply (J3401-60200)
Step 20. Insert the TSU back into the server cabinet, as described in Stage 2:
Installing the Telecom Signaling Unit in the Server Rack on page 116.
Step 21. Reconnect all cables to the rear panel of the TSU, but do NOT reconnect
any TSC cables at the network end yet.
Step 22. Power on the TSU and check the LEDs on the TSU and the TSCs. See
Checking LEDs on page 175 for information on the LEDs and their
meaning.
Step 23. Reconnect the TSC cables at the network end.
Step 24. 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, you can now restart it. To do this,
run the ss7Start command.
Rollback

134

Perform the above procedure again to reinstall the old power supply.

Chapter 9

Maintaining TSU/TSC Hardware


Replacing the TSU Backplane and CPU Card

Replacing the TSU Backplane and CPU Card


The TSUs backplane and CPU card form part of the card cage. Replacing
the backplane and CPU card therefore involves replacing the card cage
kit. It is possible to replace a TSU card cage on a running platform
without disturbing the traffic.

CAUTION

This procedure should be performed by HP support personnel. If you


wish to perform the procedure yourself, first contact 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

Be sure to power off the TSU when instructed to do so.

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

Maintaining TSU/TSC Hardware


Replacing the TSU Backplane and CPU Card
Step 4. Disconnect all cables from the rear panel of the TSU and from the SS7
network.
Step 5. Remove the TSU from the server cabinet, as described in Removing the
TSU from the Server Cabinet on page 168.
Step 6. Remove the cover of the TSU, as described in Removing the TSU Cover
on page 168.
Step 7. Remove the card cage from the TSU, as described in Removing the Card
Cage on page 170.
Step 8. Transfer the TSCs and add-on LAN card (if present) from the existing
card cage to the replacement card cage. Refer to Removing a Card from
a TSU on page 173 and Adding a Card to a TSU on page 171 for help
with this procedure.
a. Transfer the add-on LAN card (if present) in slot L1 to slot L1 in the
replacement card cage.
b. Transfer the TSCs to their equivalent slots in the replacement card
cage.
Step 9. Insert the new card cage into the TSU, as described in Replacing the
Card Cage on page 171.
Step 10. Replace the cover of the TSU, as described in Replacing the TSU Cover
on page 169.
Step 11. Insert the TSU back into the server cabinet, as described in Stage 2:
Installing the Telecom Signaling Unit in the Server Rack on page 116.
Step 12. Reconnect all cables to the rear panel of the TSU, but do NOT connect
any TSC cables at the network end yet.
Step 13. Power on the TSU and wait until the TSU has booted (approximately 2
minutes).
Step 14. Use the command ss7TsuPing -v -u <TSU_ID> to check that you can
reach the TSU that you are working on.
Step 15. Run the hardware replacement command ss7HwReplace. If the tool
returns an error, refer to the HP OpenCall SS7 Troubleshooting Guide.
When asked if you wish to load the updated configuration, answer yes.

136

Chapter 9

Maintaining TSU/TSC Hardware


Replacing the TSU Backplane and CPU Card
Do not accept changes now - move to another window to continue or quit
the tool - if you accept the changes, no rollback will be available.
Step 16. Reconnect the TSC cables at the network end.
Step 17. 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, you can now restart it. To do this,
run the ss7Start command.
Step 18. 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 19. If you are satisfied with this new configuration, make it the running
configuration by carrying out one of the following:

run the command ss7HwAccept

accept the updated configuration in the ss7HwReplace window.

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

answer affirmatively in the ss7HwAccept or ss7HwLoad window

execute the cfgPropagate command

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 work on. 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. Take anti-static precautions by wearing the grounding wrist strap.
Step 3. Power off the TSU.
Step 4. Disconnect all cables from the rear panel of the TSU and from the SS7
network.

Chapter 9

137

Maintaining TSU/TSC Hardware


Replacing the TSU Backplane and CPU Card
Step 5. Remove the TSU from the server cabinet, as described in Removing the
TSU from the Server Cabinet on page 168.
Step 6. Remove the cover of the TSU, as described in Removing the TSU Cover
on page 168.
Step 7. Remove the card cage from the TSU, as described in Removing the Card
Cage on page 170.
Step 8. Transfer the TSCs and add-on LAN card (if present) back to the former
card cage. Refer to Removing a Card from a TSU on page 173 and
Adding a Card to a TSU on page 171 for help with this procedure.
a. Transfer the add-on LAN card (if present) in slot L1 to slot L1 in the
former card cage.
b. Transfer the TSCs to their equivalent slots in the former card cage.
Step 9. Insert the card cage into the TSU, as described in Replacing the Card
Cage on page 171.
Step 10. Replace the cover of the TSU, as described in Replacing the TSU Cover
on page 169.
Step 11. Insert the TSU back into the server cabinet, as described in Stage 2:
Installing the Telecom Signaling Unit in the Server Rack on page 116.
Step 12. Reconnect all cables to the rear panel of the TSU, but do NOT connect
any TSC cables at the network end yet.
Step 13. Power on the TSU and wait until the TSU has booted (approximately 2
minutes).
Step 14. Rollback the configuration changes by carrying out either of the
following:

run the command ss7HwRollback

reject the updated configuration in the ss7HwReplace window.

Step 15. Reconnect the TSC cables at the network end.


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, you can now restart it. To do this,
run the ss7Start command.

138

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a LAN Card in a TSU

Replacing a LAN Card in a TSU


This section describes how to replace an add-on LAN card (HP Part
Number: D5013-60002), located in slot L1 in the TSU, which is used in a
2-host platform. It is possible to add a LAN card in a TSU on a running
platform without disturbing the traffic.

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

Be sure to power off the TSU when instructed to do so.

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 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.
Step 4. Remove all cables from the rear panel of the TSU.

Chapter 9

139

Maintaining TSU/TSC Hardware


Replacing a LAN Card in a TSU
Step 5. Slide the TSU out on its rails until it blocks.
Step 6. Remove the cover of the TSU, as described in Removing the TSU Cover
on page 168.
Step 7. Remove the card cage from the TSU, as described in Removing the Card
Cage on page 170.
Step 8. Remove the old LAN card from slot L1 and install the new card in its
place. Refer to Removing a Card from a TSU on page 173 and Adding a
Card to a TSU on page 171 for help with this procedure.
Note that if there is a TSC installed in slot 5, you will need to remove it
before you can gain access to slot L1. Do not forget to replace it!
Step 9. Re-insert the card cage into the TSU, as described in Replacing the Card
Cage on page 171.
Step 10. Replace the cover of the TSU, as described in Replacing the TSU Cover
on page 169.
Step 11. Slide the TSU on its rails back into the cabinet.
Step 12. Reconnect all cables to the rear panel of the TSU, but do NOT connect
any TSC cables at the network end yet.
Step 13. Power on the TSU and wait until the TSU has booted (approximately 2
minutes).
Step 14. Use the command ss7TsuPing -v to see the new MAC address of the
replacement LAN card.
Step 15. Run the hardware replacement command ss7HwReplace. If the tool
returns an error, refer to the HP OpenCall SS7 Troubleshooting Guide.
When asked if you wish to load the updated configuration, answer
affirmatively.
Do not accept changes now - move to another window to continue or quit
the tool - if you accept the changes, no rollback will be available.
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, you can now restart it. To do this,
run the ss7Start command.

140

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a LAN Card in a TSU
Step 17. Configure the hardware. To do this, refer to LAN Configuration:
Replacing a LAN Card in a TSU on page 204.
Rollback

You should be logged in as ocadmin on the active host.


You should only perform this rollback when instructed to do so in the
procedure LAN Configuration: Replacing a LAN Card in a TSU on
page 204.
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 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.
Step 4. Remove all cables from the rear panel of the TSU.
Step 5. Slide the TSU out on its rails until it blocks.
Step 6. Remove the cover of the TSU, as described in Removing the TSU Cover
on page 168.
Step 7. Remove the card cage from the TSU, as described in Removing the Card
Cage on page 170.
Step 8. Remove the replacement LAN card from slot L1 and re-install the former
card in its place. Refer to Removing a Card from a TSU on page 173
and Adding a Card to a TSU on page 171 for help with this procedure.
Note that if there is a TSC installed in slot 5, you will need to remove it
before you can gain access to slot L1. Do not forget to replace it!
Step 9. Re-insert the card cage into the TSU, as described in Replacing the Card
Cage on page 171.
Step 10. Replace the cover of the TSU, as described in Replacing the TSU Cover
on page 169.
Step 11. Slide the TSU on its rails back into the cabinet.

Chapter 9

141

Maintaining TSU/TSC Hardware


Replacing a LAN Card in a TSU
Step 12. Reconnect the power and LAN cables in the rear panel of the TSU but do
NOT connect the TSC cables (that connect to the signaling network) yet.
Step 13. Power on the TSU and wait until the TSU has booted (approximately 2
minutes).
Step 14. Rollback the configuration changes by carrying out either of the
following:

run the command ss7HwRollback

reject the updated configuration in the ss7HwReplace window.

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

Maintaining TSU/TSC Hardware


Installing an Additional TSC in a TSU

Installing an Additional TSC in a TSU


This section describes how to add an additional Telecom Signaling Card
into a TSU. The new TSC must of the same type as the other TSCs in the
TSU. It is possible to add a TSC to a TSU on a running platform without
disturbing the traffic.

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

Be sure to power off the TSU when instructed to do so.

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 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 2. Take anti-static precautions by wearing the grounding wrist strap.
Step 3. Power off the TSU.
Step 4. Remove all cables from the rear panel of the TSU and disconnect the
TSC cables at the network end.
Step 5. Slide the TSU out on its rails until it blocks.
Step 6. Remove the cover of the TSU, as described in Removing the TSU Cover
on page 168.

Chapter 9

143

Maintaining TSU/TSC Hardware


Installing an Additional TSC in a TSU
Step 7. Remove the card cage from the TSU, as described in Removing the Card
Cage on page 170.
Step 8. Insert the new TSC into a vacant slot. Refer to Adding a Card to a TSU
on page 171 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 9. Re-insert the card cage into the TSU, as described in Replacing the Card
Cage on page 171.
Step 10. Replace the cover of the TSU, as described in Replacing the TSU Cover
on page 169.
Step 11. Slide the TSU on its rails back into the cabinet.
Step 12. Reconnect all cables to the rear panel of the TSU, but do NOT connect
any TSC cables at the network end yet. If you are using the optional
connection panel, you will need to make the TSC connections via this
panel.
Label the new TSC cables, stating what they are (E1, T1, V.35) and
where they connect to (e.g. TSC5).
Step 13. Power on the TSU and wait until the TSU has booted (approximately 2
minutes).
Step 14. Check the LEDs on the TSU and the TSCs. See Checking LEDs on
page 175 for information on the LEDs and their meaning.
Step 15. Configure the hardware. To do this, refer to TSC Configuration:
Installing an Additional TSC in a TSU on page 192. As part of this
procedure, you will connect the TSC cables to the network and restore
the diverted traffic (if necessary).

144

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a TSC in a TSU

Replacing a TSC in a TSU


This section describes how to replace a Telecom Signaling Card in a TSU.
The replacement TSC must be of the same type as the other TSCs in the
TSU. It is possible to replace a TSC in a TSU on a running platform
without disturbing the traffic.

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

Be sure to power off the TSU when instructed to do so.

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 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 2. Take anti-static precautions by wearing the grounding wrist strap.
Step 3. Power off the TSU.
Step 4. Remove all cables from the rear panel of the TSU and disconnect the
TSC cables at the network end.
Step 5. Slide the TSU out on its rails until it blocks.
Step 6. Remove the cover of the TSU, as described in Removing the TSU Cover
on page 168.

Chapter 9

145

Maintaining TSU/TSC Hardware


Replacing a TSC in a TSU
Step 7. Remove the card cage from the TSU, as described in Removing the Card
Cage on page 170.
Step 8. Remove the old TSC and install the new card in its place. Refer to
Removing a Card from a TSU on page 173 and Adding a Card to a
TSU on page 171 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 9. Re-insert the card cage into the TSU, as described in Replacing the Card
Cage on page 171.
Step 10. Replace the cover of the TSU, as described in Replacing the TSU Cover
on page 169.
Step 11. Slide the TSU on its rails back into the cabinet.
Step 12. Reconnect all cables to the rear panel of the TSU, but do NOT connect
any TSC cables at the network end yet.
Step 13. Power on the TSU and wait until the TSU has booted (approximately 2
minutes).
Step 14. Use the command ss7TsuPing -v -u <TSU_ID> to check that you can
reach the replacement TSC.
Step 15. Run the hardware replacement command ss7HwReplace. If the tool
returns an error, refer to the HP OpenCall SS7 Troubleshooting Guide.
When asked if you wish to load the updated configuration, answer
affirmatively.
Do not accept changes now - quit the tool or move to another window to
continue - if you accept the changes, no rollback will be available.
Step 16. Reconnect the TSC cables to the signaling network.
Step 17. If you have diverted the traffic from the 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, you can now restart it. To do this,
run the ss7Start command.
Step 18. Configure the hardware. To do this, refer to TSC Configuration:
Replacing a TSC in a TSU on page 196.

146

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a TSC in a TSU
Rollback

You should only perform this rollback when instructed to do so in the


procedure TSC Configuration: Replacing a TSC in a TSU on page 196.
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 work on. To do this, refer to Restoring the Traffic
on page 183.
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.
Step 4. Remove all cables from the rear panel of the TSU and disconnect the
TSC cables at the network end.
Step 5. Slide the TSU out on its rails until it blocks.
Step 6. Remove the cover of the TSU, as described in Removing the TSU Cover
on page 168.
Step 7. Remove the card cage from the TSU, as described in Removing the Card
Cage on page 170.
Step 8. Remove the replacement TSC and install the old card back in its place.
Refer to Removing a Card from a TSU on page 173 and Adding a Card
to a TSU on page 171 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 9. Re-insert the card cage into the TSU, as described in Replacing the Card
Cage on page 171.
Step 10. Replace the cover of the TSU, as described in Replacing the TSU Cover
on page 169.
Step 11. Slide the TSU on its rails back into the cabinet.
Step 12. Reconnect the power and LAN cables to the rear panel of the TSU but do
NOT reconnect the TSC cables to the TSCs yet.
Step 13. Power on the TSU and wait until the TSU has booted (approximately 2
minutes).

Chapter 9

147

Maintaining TSU/TSC Hardware


Replacing a TSC in a TSU
Step 14. Use the command ss7TsuPing -v -u <TSU_ID> to check that you can
reach the TSC that you have re-installed.
Step 15. Reconnect the TSC cables.
Step 16. Rollback the configuration changes by carrying out either of the
following:

run the command ss7HwRollback

reject the updated configuration in the ss7HwReplace window.

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

Maintaining TSU/TSC Hardware


Removing a TSC from a TSU

Removing a TSC from a TSU


This section describes how to remove a Telecom Signaling Card from a
TSU (without replacing the card). It is possible to remove a TSC from a
TSU on a running platform without disturbing the traffic.

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

Be sure to power off the TSU when instructed to do so.

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 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 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
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.
Chapter 9

149

Maintaining TSU/TSC Hardware


Removing a TSC from a TSU
Step 3. Take anti-static precautions by wearing the grounding wrist strap.
Step 4. Power off the TSU.
Step 5. Remove all cables from the rear panel of the TSU and disconnect the
TSC cables at the network end.
Step 6. Slide the TSU out on its rails until it blocks.
Step 7. Remove the cover of the TSU, as described in Removing the TSU Cover
on page 168.
Step 8. Remove the card cage from the TSU, as described in Removing the Card
Cage on page 170.
Step 9. Remove the relevant TSC from the TSU. 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 10. Re-insert the card cage into the TSU, as described in Replacing the Card
Cage on page 171.
Step 11. Replace the cover of the TSU, as described in Replacing the TSU Cover
on page 169.
Step 12. Slide the TSU on its rails back into the cabinet.
Step 13. Reconnect the power and LAN cables in the rear panel of the TSU.
Step 14. Power on the TSU and wait until the TSU has booted (approximately 2
minutes).
Step 15. Reconnect the remaining TSC cables to the rear panel of the TSU, but do
NOT connect them at the network end yet.
Step 16. Use the command ss7TsuPing -v to check that the TSC is no longer
present.
Step 17. Configure the hardware. To do this, refer to TSC Configuration:
Removing a TSC from a TSU on page 197. During this procedure, you
will reconnect the TSC cables to the network and restore the diverted
traffic (if necessary).

150

Chapter 9

Maintaining TSU/TSC Hardware


Removing a TSC from a TSU
Rollback

You should only perform this rollback when instructed to do so in the


procedure TSC Configuration: Removing a TSC from a TSU on
page 197.
You should be logged onto the active host as ocadmin.
Step 1. Power off the TSU.
Step 2. Remove all cables from the rear panel of the TSU.
Step 3. Slide the TSU out on its rails until it blocks.
Step 4. Remove the cover of the TSU, as described in Removing the TSU Cover
on page 168.
Step 5. Remove the card cage from the TSU, as described in Removing the Card
Cage on page 170.
Step 6. Re-insert the removed TSC into the TSU. Refer to Adding a Card to a
TSU on page 171 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 7. Re-insert the card cage into the TSU, as described in Replacing the Card
Cage on page 171.
Step 8. Replace the cover of the TSU, as described in Replacing the TSU Cover
on page 169.
Step 9. Slide the TSU on its rails back into the cabinet.
Step 10. Reconnect the power and LAN cables in the rear panel of the TSU.
Step 11. Reconnect the TSC cables to the rear panel of the TSU, but do NOT
connect them at the network end yet.
Step 12. Power on the TSU and wait until the TSU has booted (approximately 2
minutes).
Step 13. Use the command ss7TsuPing -v to check that you can reach the TSC
that you have re-installed.
Step 14. Rollback the platform configuration changes by running the command
ss7HwRollback.
Step 15. Reconnect the TSC cables at the network end.

Chapter 9

151

Maintaining TSU/TSC Hardware


Removing a TSC from a TSU
Step 16. If you have stopped HP OpenCall SS7, you can now restart it. To do this,
run the ss7Start command.
Step 17. Add the removed link(s) back to the stack. In the SS7 Monitor screen,
select Configure Entities|Config MTP|Config lk/lkset and add the
link(s).
Press C to checkpoint the modifications.
Step 18. If you have diverted the traffic from the TSU, you can now restore the
traffic to the TSU. To do this, refer to Restoring the Traffic on page 183.
Otherwise, reactivate the link(s). In the SS7 Monitor screen, select
Monitor Entities|Monit MTP|Monit lk/lkset, then activate the
link(s).

152

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a TSU

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

The following procedure involves disconnecting the existing 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

Be sure to power off the TSU when instructed to do so.

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 replace. 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. Take anti-static precautions by wearing the grounding wrist strap.
Step 3. Power off the faulty TSU.
Step 4. Disconnect all cables from the rear panel of the faulty TSU.
Step 5. Remove the TSU from the server cabinet, as described in Removing the
TSU from the Server Cabinet on page 168.
Step 6. Remove the covers of both TSUs, as described in Removing the TSU
Cover on page 168.

Chapter 9

153

Maintaining TSU/TSC Hardware


Replacing a TSU
Step 7. Remove the card cages from both TSUs, as described in Removing the
Card Cage on page 170.
Step 8. Remove the TSCs and any add-on LAN card from the faulty TSU and
transfer them to the equivalent slots in the replacement TSU. Refer to
Removing a Card from a TSU on page 173 and Adding a Card to a
TSU on page 171 for help with this.
Step 9. Re-insert the card cage into the new TSU, as described in Replacing the
Card Cage on page 171.
Step 10. Replace the cover of the new TSU, as described in Replacing the TSU
Cover on page 169.
Step 11. Slide the rails on the new TSU into the rail guides in the server cabinet
and push the TSU into the cabinet until it is in place.
Step 12. Reconnect all cables to the rear panel of the TSU, but do NOT connect
any TSC cables at the network end yet.
Step 13. Power on the TSU and wait until the TSU has booted (approximately 2
minutes).
Step 14. Use the command ss7TsuPing -v to check that you can reach the
replacement TSU and that it has a new MAC address.
Step 15. Run the hardware replacement command ss7HwReplace. If the tool
returns an error, refer to the HP OpenCall SS7 Troubleshooting Guide.
When asked if you wish to load the updated configuration, answer yes.
Do not accept changes now - move to another window to continue or quit
the tool - if you accept the changes, no rollback will be available.
Step 16. Use the command ss7TsuStatus -L -u <TSU_ID> to verify that the
replacement TSU is active and that the links are floating.
Step 17. Reconnect the TSC cables at the network end.
Step 18. If you have diverted the traffic from the 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, you can now restart it. To do this,
run the ss7Start command.
Step 19. Configure the hardware. To do this, refer to TSU Configuration:
Replacing a TSU on page 189.

154

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a TSU
Rollback

You should only perform this rollback when instructed to do so in the


procedure TSU Configuration: Replacing a TSU on page 189.
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 replace. 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. Take anti-static precautions by wearing the grounding wrist strap.
Step 3. Power off the new TSU.
Step 4. Disconnect all cables from the rear panel of the new TSU.
Step 5. Remove the TSU from the server cabinet, as described in Removing the
TSU from the Server Cabinet on page 168.
Step 6. Remove the covers of both TSUs, as described in Removing the TSU
Cover on page 168.
Step 7. Remove the card cages from both TSUs, as described in Removing the
Card Cage on page 170.
Step 8. Remove the TSCs and any add-on LAN card from the new TSU and
transfer them to the equivalent slots in the former TSU. Refer to
Removing a Card from a TSU on page 173 and Adding a Card to a
TSU on page 171 for help with this.
Step 9. Re-insert the card cage into the former TSU, as described in Replacing
the Card Cage on page 171.
Step 10. Replace the cover of the former TSU, as described in Replacing the TSU
Cover on page 169.
Step 11. Slide the rails on the former TSU into the rail guides in the server
cabinet and push the TSU into the cabinet until it is in place.
Step 12. Reconnect all cables to the rear panel of the TSU, but do NOT connect
any TSC cables at the network end yet.
Step 13. Power on the TSU and wait until the TSU has booted (approximately 2
minutes).

Chapter 9

155

Maintaining TSU/TSC Hardware


Replacing a TSU
Step 14. Rollback the configuration changes by carrying out either of the
following:

run the command ss7HwRollback

reject the updated configuration in the ss7HwReplace window.

Step 15. Reconnect the TSC cables at the network end.


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, you can now restart it. To do this,
run the ss7Start command.

156

Chapter 9

Maintaining TSU/TSC Hardware


Removing a TSU from a Platform

Removing a TSU from a Platform


This section describes how to remove a TSU from a running platform
(without replacing the TSU). It is possible to remove a TSU from a
running platform without disturbing the traffic.

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

Be sure to power off the TSU when instructed to do so.

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

Maintaining TSU/TSC Hardware


Removing a TSU from a Platform
Step 3. Power off the TSU and remove all cables from the rear panel of the TSU.
Also disconnect the TSC cables at the network end.
Step 4. Remove the TSU from the server cabinet. To do this, refer to Removing
the TSU from the Server Cabinet on page 168.
Step 5. Configure the hardware. To do this, refer to TSU Configuration:
Removing a TSU from a Platform on page 190.
Rollback

You should only perform this rollback when instructed to do so in the


procedure TSU Configuration: Removing a TSU from a Platform on
page 190.
Step 1. Insert the TSU back into the server cabinet.
Step 2. Reconnect all cables to the rear panel of the TSU:
a. Connect the TSU to a platform host using a LAN cable via Slot L0
and if the platform is 2-host, connect the TSU to the other host using
a LAN cable via Slot L1. For information on LAN cabling, refer to
Cabling Recommendations for 2-Host Platforms on page 120.
b. Connect the TSC cables to the TSU but do NOT connect them at the
network end yet.
Step 3. Power on the TSU.
Step 4. Use the command ss7TsuPing -v to check that the TSU is no longer
present.
Step 5. Rollback the platform configuration changes by running the command
ss7HwRollback.
Step 6. Reconnect the TSC cables at the network end.
Step 7. Add the removed link(s) back to the stack. In the SS7 Monitor screen,
select Configure Entities|Config MTP|Config lk/lkset and add the
link(s).
Press C to checkpoint the modifications.
Step 8. Activate the added link(s). In the SS7 Monitor screen, select
Monitor Entities|Monit MTP|Monit lk/lkset, then activate the
link(s).

158

Chapter 9

Maintaining TSU/TSC Hardware


Installing a TSC in a Host Server

Installing a TSC in a Host Server


This section describes how to add a Telecom Signaling Card into a
TSC-in-system server. The new TSC must be of the same type as any
other TSCs in the server.

CAUTION

When following this procedure, it is important to refer to your server


documentation when carrying out tasks that are specific to the host
server.

CAUTION

During this procedure, it is necessary to shut down the platform. You will
therefore disturb the traffic handled by the platform.

WARNING

Be sure to power off the host server when instructed to do so.

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

Maintaining TSU/TSC Hardware


Installing a TSC in a Host Server
Step 9. Use the command ss7TscPing -v to check that you can reach the new
TSC.
Step 10. Connect the TSC cables to the TSC, but do NOT connect them at the
network end yet.
Step 11. Label the new TSC cables, stating what they are (E1, T1, V.35) and
where they connect to (e.g. TSC1, TSC2).
Step 12. If you are installing a TSC in an existing platform, now configure the
hardware. To do this, refer to TSC Configuration: Installing an
Additional TSC in a TSU on page 192. During this procedure you will
connect the TSC cables to the network.
If you are installing a TSC in a new platform, to continue with your
platform installation refer to First Time Installation Overview on
page 25 for a guide to the remaining installation tasks.

160

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a TSC in a Host Server

Replacing a TSC in a Host Server


This section describes how to replace a Telecom Signaling Card in a
TSC-in-system server. The replacement TSC must be of the same type as
any other TSCs in the server.

CAUTION

When following this procedure, it is important to refer to your server


documentation when carrying out tasks that are specific to the host
server.

CAUTION

During this procedure, it is necessary to shut down the platform. You will
therefore disturb the traffic handled by the platform.

WARNING

Be sure to power off the host server when instructed to do so.

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

Maintaining TSU/TSC Hardware


Replacing a TSC in a Host Server
Step 9. Power on the host server and wait until it has booted.
Step 10. Use the command ss7TscPing -v to check that you can reach the
replacement TSC.
Step 11. Reconnect the TSC cables to the TSC but do NOT connect them at the
network end yet.
Step 12. Run the hardware replacement command ss7HwReplace. If the tool
returns an error, refer to the HP OpenCall SS7 Troubleshooting Guide.
When asked if you wish to load the updated configuration, answer yes.
Do not accept changes now - quit the tool or move to another window to
continue - if you accept the changes, no rollback will be available.
Step 13. Configure the hardware. To do this, refer to TSC Configuration:
Replacing a TSC in a Host Server on page 202. During this procedure,
you will reconnect the TSC cables to the network.
Rollback

You should only perform this rollback when instructed to do so in the


procedure TSC Configuration: Replacing a TSC in a Host Server on
page 202.
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 by running 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 and disconnect the TSC cables
at the network end.
Step 6. Remove the cover of the host server.
Step 7. Remove the replacement TSC and re-install the old card in its place.
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.

162

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a TSC in a Host Server
Step 10. Use the command ss7TscPing -v to check that you can reach the TSC
that you have re-installed.
Step 11. Reconnect the TSC cables.
Step 12. Rollback the configuration changes by carrying out either of the
following:

run the command ss7HwRollback

reject the updated configuration in the ss7HwReplace window.

Step 13. Restart HP OpenCall SS7 by running the ss7Start command.

Chapter 9

163

Maintaining TSU/TSC Hardware


Removing a TSC from a Host Server

Removing a TSC from a Host Server


This section describes how to remove a Telecom Signaling Card from a
TSC-in-system server (without replacing the card).

CAUTION

When following this procedure, it is important to refer to your server


documentation when carrying out tasks that are specific to the host
server.

CAUTION

During this procedure, it is necessary to shut down the platform. You will
therefore interrupt the traffic handled by the platform.

WARNING

Be sure to power off the host server when instructed to do so.

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

Maintaining TSU/TSC Hardware


Removing a TSC from a Host Server

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

You should only perform this rollback when instructed to do so in the


procedure TSC Configuration: Removing a TSC from a Host Server on
page 203.
Step 1. Stop HP OpenCall SS7 by running the command ss7Stop -all and shut
down the platform.
Step 2. Power off the host server.

Chapter 9

165

Maintaining TSU/TSC Hardware


Removing a TSC from a Host Server
Step 3. Take anti-static precautions by wearing the grounding wrist strap.
Step 4. Remove the cover of the host server.
Step 5. Re-insert the removed TSC into the host server. Refer to your server
documentation for help with this.
Step 6. Replace the cover of the host server.
Step 7. Reconnect the TSC cables to the TSC, but do NOT connect at the
network end yet.
Step 8. Power on the host server and wait until it has booted.
Step 9. Use the command ss7TscPing -v to check that you can reach the TSC
that you have re-installed.
Step 10. Rollback the platform configuration changes by running the command
ss7HwRollback.
Step 11. Reconnect the TSC cables at the network end.
Step 12. Restart HP OpenCall SS7 on the host. To do this, run the ss7Start
command.
Step 13. Add the removed link(s) back to the stack. In the SS7 Monitor screen,
select Configure Entities|Config MTP|Config lk/lkset and add the
link(s).
Press C to checkpoint the modifications.
Step 14. Reactivate the links associated with the TSC using the SS7 Monitor. To
do this, select Monitor Entities|Monit MTP|Monit lk/lkset and
follow the instructions to activate the links. If all links of a linkset have
been deactivated, you must activate the linkset.
If you diverted traffic from the TSC, the links will then handle the traffic
as before.

166

Chapter 9

Maintaining TSU/TSC Hardware


Replacing a Four-Port TSC Cable

Replacing a Four-Port TSC Cable


This section describes how to replace a 4-port TSC cable that connects a
Telecom Signaling Card to the SS7 network.

NOTE

The replacement cable must be identical in type to the cable being


removed.

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

Follow the above procedure.

167

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures

Common TSU/TSC Procedures


This section contains the TSU/TSC procedures that are referenced from
other procedures in the manual (from Chapter 8, Installing a TSU, and
Chapter 9, Maintaining TSU/TSC Hardware.)
The procedures provided in this section are listed below.

Removing the TSU from the Server Cabinet on page 168

Removing and Replacing the TSU Cover on page 168

Removing and Replacing the Card Cage on page 170

Adding a Card to a TSU on page 171

Removing a Card from a TSU on page 173

Checking LEDs on page 175

Removing the TSU from the Server Cabinet


For some of the procedures described in this guide, you have to remove
the TSU from the server cabinet. To do this, follow the procedure below:
Step 1. Ensure that the TSU is powered off.
Step 2. Ensure that all cables have been removed from the rear panel of the
TSU.
Step 3. Slide the TSU on its rails until it blocks.
Step 4. Push the two springs on the side of the rails (that hold the TSU in) and
slide the TSU off the rail guide.

Removing and Replacing the TSU Cover


For some of the procedures described in this guide, you have to remove
the TSU cover.
This section describes how to remove and then replace the cover.
Removing the TSU Cover
When working through this procedure, refer to Figure 9-3 below.

168

Chapter 9

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures
Step 1. Unscrew the four captive screws on the sides of the cover with a Philips
screwdriver.
Step 2. Slide the cover back one centimeter to loosen it from the groove, then lift
it off.
Figure 9-3

Removing the TSU Cover

Replacing the TSU Cover


Step 1. Place the cover on the top of the unit, one centimeter behind the
frontplate, then slide it forward so that the grooves at the rear of the unit
are attached.
Step 2. Tighten the four captive screws on the cover of the unit.

Chapter 9

169

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures

Removing and Replacing the Card Cage


For some of the procedures described in this guide, you have to remove
the card cage from inside the TSU.
This section describes how to remove and then replace the card cage.
Removing the Card Cage
When working through this procedure, refer to Figure 9-4 below.
Step 1. Disconnect the power supply connector (the large white connector) from
the power supply unit.
Step 2. Disconnect the fan board connector J9 (the large black connector on the
ribbon cable at the front of the card cage).
Step 3. Unscrew the four captive screws at the back of the card cage (and
accessible from the TSU rear panel), then slide the cage towards the
frontplate of the unit and lift the cage out.
Figure 9-4

170

Removing the Card Cage

Chapter 9

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures
Replacing the Card Cage
Step 1. Insert the card cage back into the TSU and tighten the four captive
screws at the back to the chassis.
Step 2. Reconnect the (white) power supply connector to the power supply unit.
Step 3. Reconnect the fan board connector J9.

Adding a Card to a TSU


Note that the PCI slots available in a TSU for the different types of cards
are as follows:

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

Ensure that you are taking anti-static precautions


by wearing the grounding wrist strap before
handling the cards.

171

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures
The following procedure forms a common part of other procedures in this
guide concerned with inserting different card types into a TSU.
Step 1. Remove the card holder brackets as follows (also refer to Figure 9-5
below):
a. Remove the appropriate card holder bracket screw(s).
b. Slide the bracket sideways towards the front of the chassis to detach
the keyhole standoff on the bottom of the card cage.
Figure 9-5

Removing the Card Holder Brackets

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

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures
Figure 9-6

Inserting the Card

Step 3. 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.

Removing a Card from a TSU


Note that the different types of cards that the PCI slots in a TSU can
accommodate are as follows:
Card Type

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

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures

If you are removing a TSC, 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 removing a LAN card, refer to Replacing a LAN Card in a


TSU on page 139.

Ensure that you are taking anti-static precautions by wearing the


grounding wrist strap before handling the cards.

CAUTION

The following procedure forms a common part of other procedures in this


guide concerned with removing different card types from a TSU.
Step 1. Remove the card holder brackets as follows (also refer to Figure 9-5
below):
a. Remove the appropriate card holder bracket screw(s).
b. Slide the bracket sideways towards the front of the chassis to detach
the keyhole standoff on the bottom of the card cage.
Figure 9-7

174

Removing the Card Holder Brackets

Chapter 9

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures
Step 2. Remove the card as follows (also refer to Figure 9-6)
a. Unscrew the card bracket from the cage.
b. Slide the card out of the slot. Pull firmly on both ends of the card at
the same time.
c. Place a slot protector in the relevant slot on the card cage backplane.
Figure 9-8

Removing the Card

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

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures
These appear on the front panel of the unit and are repeated on the
rear panel. They indicate the status of the TSU and are fully
described below.

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.

LAN Card LEDs


These appear on the end-plate of each LAN card and can be viewed
on the rear panel of the TSU. They indicate the status of the LAN
card 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

TSU LEDs - Interpretation


TSU without
HP OpenCall SS7
firmware

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

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures
Therefore at this stage, if your TSU is operating correctly, the four LEDs
should show the following states:

NOTE

Power - ON

Status - ON

Fault - ON

Fan Fail - OFF

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

TSU Status and Fault LEDs - Interpretation

LED
Fault

TSU State

Meaning

Status

Off

Off

Not responding

Performing the power-on


self-test, or rebooting

Off

Flashing slowly

Not responding

Starting the TSU firmware

Off

Flashing rapidly

Not responding

Firmware started, TSU is


configuring TSCs

Off

On

Active

TSU is operational

On

Off

Not responding

Power-on self-test has


failed

Flashing slowly
or rapidly

Off

Not responding

No firmware on TSU

Flashing slowly

Flashing slowly

Not responding

Fatal software error

Chapter 9

177

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures
Table 9-2

TSU Status and Fault LEDs - Interpretation (Continued)

LED
Fault
Flashing slowly

TSC LEDs

TSU State

Meaning

Degraded

At least one element of the


TSU has a problem; e.g. a
TSC is out-of-service

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.

P0-P3 LEDs (E1/T1 TSC only): Indicate port status.

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

TSC LEDs - Interpretation


Meaning for
E1/T1

Status

Meaning for V.35

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

For an unconfigured TSC, only the L2 LED should be ON.


LAN Card LEDs

Each LAN card has three LEDs:

178

LNK: Indicates the state of the connection to the host.

Chapter 9

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures

ACT: Indicates whether data is being sent/received.

100: Indicates the speed of the connection.

Table 9-4 below indicates the meanings of these LEDs in their different
states.
Table 9-4
LED

LAN Card LEDs


Status

Meaning

On

The card and the host LAN card are


receiving power. The cable connection
between adapter and host is OK.

Off

The cable connection between the card


and the host is faulty, or the driver
configuration is faulty.

On or
flashing

The card is sending or receiving network


data. The frequency of the flashing
depends on the amount of traffic.

Off

The card is not sending or receiving data.

On

The card is operating at 100 Mbit/s.

Off

The card is operating at 10 Mbit/s.

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.

Try another port on 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.

The ACT LED does not light:

Chapter 9

179

Maintaining TSU/TSC Hardware


Common TSU/TSC Procedures

The card may not be transmitting or receiving. Refer to your LAN


card documentation for help.

In addition, the 100 LED will be ON if the card is functioning properly.

180

Chapter 9

10

Configuring TSU/TSC Hardware


This chapter contains the procedures for the software configuration of
TSUs, TSCs and LAN cards. To carry out the necessary hardware
operations, start with the relevant procedure in Chapter 8, Installing a
TSU, or Chapter 9, Maintaining TSU/TSC Hardware.

Chapter 10

181

Configuring TSU/TSC Hardware


Diverting Traffic

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

All the steps should be done while logged in as as ocadmin.


They must be done on the active host.
Step 1. Find the MTPL2 link identifiers (linkId) for the elements you need to
stop using the cfgSs7Hw -view command.
Step 2. Find the corresponding SLCs and linksets. To do this, in the SS7
Monitor, select Monitor Entities|Monit MTP|Monit lk/lkset. For
each linkId, there is a corresponding SLC and DPC.
If you do not need to deactivate all the links of a linkset (or to a DPC), the
connection with this destination point code is not lost. The traffic is
shared among the remaining links of the linkset. Otherwise, you lose the
traffic unless there is a secondary route to this DPC (see Monitor
Entities|Monit MTP|Monit dst/rout).
Step 3. Deactivate the links. Run SS7 Monitor, and select Monitor
Entities|Monit MTP|Monit lk/lkset and follow the instructions to
deactivate the links.

182

Chapter 10

Configuring TSU/TSC Hardware


Diverting Traffic

When deactivating the links, you lose any messages


that were being exchanged at the exact moment of
the deactivation

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

Restoring the Traffic


To restore the traffic on the deactivated links, reactivate them using the
SS7 Monitor. They will handle the traffic as before.
To do this, select Monitor Entities|Monit MTP|Monit lk/lkset and
follow the instructions to activate the links.
If all links of a linkset have been deactivated, you must activate the
linkset.

Chapter 10

183

Configuring TSU/TSC Hardware


TSU Configuration: Installing TSU(s) in a New Platform

TSU Configuration: Installing TSU(s) in a New


Platform
This section contains the software configuration steps that you must
perform when installing TSU(s) in a new platform.
A new platform is one that has no SS7 hardware.
To upgrade a platform with configured TSU(s), seeTSU Configuration:
Adding Another TSU to an Existing Platform on page 186.
Before you perform this installation, you must have completed
the procedure in Chapter 8, Installing a TSU, on page 111.
The procedure below assumes that the TSU and associated TSCs have
been installed, and that the TSU has been connected to the platform and
is powered on. Note that the TSCs must NOT be connected to the
network at this stage.

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

Configuring TSU/TSC Hardware


TSU Configuration: Installing TSU(s) in a New Platform
2. Create and configure the links using the -add -link options.
3. Once you have finished, execute the cfgSs7Hw -view command to
display the configuration. Write down the new link identifiers for the
link configurations in the stack.
Step 4. Load the platform configuration using the cfgInstall command.
Step 5. If you have a 2-host platform, propagate the updated configuration. To do
this, execute the cfgPropagate command.
Step 6. Start the SS7 stack using the ss7Start command.
Step 7. 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 8. Connect the TSC cables from the rear panel of the TSU (or the optional
connection panel) to the signaling network.
Step 9. Activate the link(s). In the SS7 Monitor screen, select
Monitor Entities|Monit MTP|Monit lk/lkset, then activate the
link(s).
All elements at the network end should be configured and activated, so
that the links can be aligned.
Step 10. 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.

Chapter 10

185

Configuring TSU/TSC Hardware


TSU Configuration: Adding Another TSU to an Existing Platform

TSU Configuration: Adding Another TSU to an


Existing Platform
This section describes how to add a TSU to a running platform without
disturbing the traffic (the platform already has SS7 hardware).
To install TSUs on a platform that has no SS7 hardware, see TSU
Configuration: Installing TSU(s) in a New Platform on page 184.
Before you perform this installation, you must have completed
with the procedure in Chapter 8, Installing a TSU, on page 111.
The procedure below assumes that the TSU and associated TSCs have
been installed, and that the TSU has been connected to the platform and
is powered on. Note that the TSCs must NOT be connected to the
network at this stage.

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

Configuring TSU/TSC Hardware


TSU Configuration: Adding Another TSU to an Existing Platform
3. Once you have finished, execute the cfgSs7Hw -update -view
command to display the configuration. Write down the new link
identifiers for the link configurations in the stack.
Step 3. Load the changes by running the command ss7HwLoad.
Do not accept changes now - quit the tool or move to another window - if
you accept the changes now, no rollback will be available.
Step 4. 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 5. Connect the TSC cables from the rear panel of the TSU (or the optional
connection panel) to the signaling network.
Step 6. Activate the link(s). In the SS7 Monitor screen, select
Monitor Entities|Monit MTP|Monit lk/lkset, then activate the
link(s).
All elements at the network end should be configured and activated, so
that the links can be aligned.
Step 7. 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 8. If you are satisfied with the new configuration, make it the running
configuration by carrying out one of the following:

run the command ss7HwAccept

accept the updated configuration in the ss7HwLoad window.

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

answer affirmatively in the ss7HwAccept or ss7HwLoad window

execute the cfgPropagate command

Only perform this rollback when instructed to do so in Step 8 above.


187

Configuring TSU/TSC Hardware


TSU Configuration: Adding Another TSU to an Existing Platform
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.
Step 3. Rollback the configuration changes by carrying out one of the following:

run the command ss7HwRollback

reject the updated configuration in the ss7HwLoad window.

Step 4. Disconnect the TSU from the host.

188

Chapter 10

Configuring TSU/TSC Hardware


TSU Configuration: Replacing a TSU

TSU Configuration: Replacing a TSU


This section contains the software configuration steps that you must
perform when replacing a TSU in an existing (running) system. To
perform this installation, you must start with the procedure
Replacing a TSC in a TSU on page 145.
The procedure below assumes that the TSU and associated TSCs have
been installed, and that the TSU has been connected to the platform and
is powered on. Note that the TSCs must NOT be connected to the
network at this stage.

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:

run the command ss7HwAccept

accept the updated configuration in the ss7HwReplace window.

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

answer affirmatively in the ss7HwAccept or ss7HwLoad window

execute the cfgPropagate command

189

Configuring TSU/TSC Hardware


TSU Configuration: Removing a TSU from a Platform

TSU Configuration: Removing a TSU from a


Platform
This section contains the software configuration steps that you must
perform when removing a TSU from a platform (without replacing the
TSU). To remove a TSU, you must start with the procedure
Removing a TSU from a Platform on page 157.
The procedure below assumes that the links associated with the TSU
have been removed from the stack, and that the TSU has been powered
off and disconnected from the platform.

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. Update the configuration using the cfgSs7HwUpdate command (which


performs a hardware auto-discovery for the hardware elements
removed).
Step 2. Check the updated configuration using the cfgSs7Hw -update -view
command.
If you are not satisfied with the configuration, go back to the steps
concerned with removing links (see the procedure Removing a TSU from
a Platform on page 157) and updating the configuration until you are
satisfied with the configuration.
Step 3. Load the configuration changes by running the command ss7HwLoad. Do
not accept the changes now - quit the tool or move to another window to
continue - if you accept the changes now, no rollback will be available.
Step 4. Check that the TSU has been removed from the configuration. Do this by
running the command ss7TsuStatus from a host.
Step 5. If you are satisfied with the new configuration, make it the new running
configuration by carrying out one of the following:

190

run the command ss7HwAccept

accept the updated configuration in the ss7HwLoad window.

Chapter 10

Configuring TSU/TSC Hardware


TSU Configuration: Removing a TSU from a Platform
If you are not satisfied with the configuration, perform the rollback steps
now. Refer to the Rollback in the section Removing a TSU from a
Platform on page 157.
Step 6. If you have a 2-host platform, propagate the updated configuration. To do
this, carry out one of the following:

Chapter 10

answer affirmatively in the ss7HwAccept or ss7HwLoad window

execute the cfgPropagate command

191

Configuring TSU/TSC Hardware


TSC Configuration: Installing an Additional TSC in a TSU

TSC Configuration: Installing an Additional


TSC in a TSU
This section contains the software configuration steps that you must
perform when installing an additional TSC in a TSU. To perform this
installation, you must start with the procedure Installing an
Additional TSC in a TSU on page 143.
The procedure below assumes that the TSU has been powered on again
after installation of the TSC. Note that the TSC must NOT be connected
to the network at this stage.

NOTE

The steps below should be carried out on both 1-host and 2-host
platforms.

The following procedure must be performed on the active host, on the


running configuration. You should be logged in as ocadmin.
Step 1. Update the configuration using the cfgSs7HwUpdate command (which
performs a hardware auto-discovery of the new hardware elements).
Step 2. Configure the new TSC 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.
3. Once you have finished, execute the cfgSs7Hw -update -view
command to display the configuration. Write down the new link
identifiers for the link configurations in the stack.
Step 3. Load the changes by running the command ss7HwLoad.
Do not accept changes now - quit the tool or move to another window - if
you accept the changes now, no rollback will be available.

192

Chapter 10

Configuring TSU/TSC Hardware


TSC Configuration: Installing an Additional TSC in a TSU
Step 4. If you are satisfied with the new configuration, make it the running
configuration by carrying out one of the following:

run the command ss7HwAccept

accept the updated configuration in the ss7HwLoad window.

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:

answer affirmatively in the ss7HwAccept or ss7HwLoad window

execute the cfgPropagate command

Step 6. Connect the TSC cables at the network end.


Step 7. If you have diverted the traffic from the 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, you can now restart it. To do this,
run the ss7Start command.
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).
Step 10. 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.
Only perform this rollback when instructed to do so in Step 4 above.

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

Configuring TSU/TSC Hardware


TSC Configuration: Installing an Additional TSC in a TSU
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.
Step 3. Rollback the configuration changes by carrying out one of the following:

run the command ss7HwRollback

reject the updated configuration in the ss7HwLoad window.

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

Configuring TSU/TSC Hardware


TSC Configuration: Installing an Additional TSC in a TSU
Step 15. Reconnect the power and LAN cables in the rear panel of the TSU but do
NOT reconnect the TSC cables yet.
Step 16. Power on the TSU and wait until the TSU has booted (approximately 2
minutes).
Step 17. Use the command ss7TsuPing -v -u to check that you can reach the
new TSC.
Step 18. Reconnect the TSC cables to the rear panel of the TSU and at the
network end.
Step 19. If you have diverted the traffic from the 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, you can now restart it. To do this,
run the ss7Start command.

Chapter 10

195

Configuring TSU/TSC Hardware


TSC Configuration: Replacing a TSC in a TSU

TSC Configuration: Replacing a TSC in a TSU


This section contains the software configuration steps that you must
perform when replacing a TSC in a TSU. To perform this installation,
start with the procedure Replacing a TSC in a TSU on
page 145.
The procedure below assumes that the TSU has been powered on again
after installation of the TSC. Note that the TSC must NOT be connected
to the network at this stage.

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:

run the command ss7HwAccept

accept the updated configuration in the ss7HwReplace window.

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

answer affirmatively in the ss7HwAccept or ss7HwLoad window

execute the cfgPropagate command

Chapter 10

Configuring TSU/TSC Hardware


TSC Configuration: Removing a TSC from a TSU

TSC Configuration: Removing a TSC from a


TSU
This section contains the software configuration steps that you must
perform when removing a TSC from a TSU (without replacing the TSC).
To remove a TSC, you must start with the procedure Removing
a TSC from a TSU on page 149.
The procedure below assumes that the links associated with the TSC
have been removed from the stack, that the TSC has been removed from
the TSU and that the TSU is powered on again.
Step 1. Update the running platform configuration using the cfgSs7HwUpdate
command (which performs a hardware auto-discovery of the hardware
elements removed).
Step 2. Check the updated configuration using the cfgSs7Hw -update -view
command.
If you are not satisfied with the configuration, go back to the steps
concerned with removing links and updating the configuration until you
are satisfied with the configuration.
Step 3. Load the configuration changes by running the command ss7HwLoad. Do
not accept the changes now - quit the tool or move to another window to
continue - if you accept the changes now, no rollback will be available.
Step 4. Check that the TSC has been removed from the configuration. Do this by
running the command ss7TsuStatus -c from the active host.
Step 5. If you are satisfied with the new configuration, make it the new running
configuration by carrying out one of the following:

run the command ss7HwAccept

accept the updated configuration in the ss7HwLoad window.

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

Configuring TSU/TSC Hardware


TSC Configuration: Removing a TSC from a TSU

answer affirmatively in the ss7HwAccept or ss7HwLoad window

execute the cfgPropagate command

Step 7. Reconnect the TSC cables to the network.


Step 8. If you have diverted the traffic from the 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, you can now restart it. To do this,
run the ss7Start command.

Configuring alarm propagation


Figure 10-1 shows

198

Chapter 10

Configuring TSU/TSC Hardware


TSC Configuration: Installing a TSC in a Host Server

TSC Configuration: Installing a TSC in a Host


Server
This section contains the software configuration steps that you must
perform when installing a TSC in a TSC-in-system server. To perform
this installation, you must start with the procedure Installing a
TSC in a Host Server on page 159.
The procedure below assumes that the host server has been powered on
again after installation of the TSC. Note that the TSC must NOT be
connected to the network at this stage.
The following procedure must be performed on the active host, on the
running configuration. You should be logged in as ocadmin.
Step 1. Update the configuration using the cfgSs7HwUpdate command (which
performs a hardware auto-discovery of the new hardware elements).
Step 2. Configure the new TSC 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.
3. Once you have finished, execute the cfgSs7Hw -update -view
command to display the configuration. Write down the new link
identifiers for the link configurations in the stack.
Step 3. Load the changes by running the command ss7HwLoad.
Do not accept changes now - quit the tool or move to another window - if
you accept the changes now, no rollback will be available.
Step 4. Using the command ss7TscStatus on a front-end host, check that all
TSCs are active.
Step 5. If you are satisfied with the new configuration, make it the running
configuration by carrying out one of the following:

Chapter 10

199

Configuring TSU/TSC Hardware


TSC Configuration: Installing a TSC in a Host Server

run the command ss7HwAccept

accept the updated configuration in the ss7HwLoad window.

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

Only perform this rollback when you are instructed to do so in Step 7


above.
Step 1. Rollback the configuration changes by carrying out one of the following:

run the command ss7HwRollback

reject the updated configuration in the ss7HwLoad window.

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

Configuring TSU/TSC Hardware


TSC Configuration: Installing a TSC in a Host Server
Step 10. Restart HP OpenCall SS7 by running the command ss7Start.

Chapter 10

201

Configuring TSU/TSC Hardware


TSC Configuration: Replacing a TSC in a Host Server

TSC Configuration: Replacing a TSC in a Host


Server
This section contains the software configuration steps that you must
perform when replacing a TSC in a TSC-in-system server. To perform
this installation, start with the procedure Replacing a TSC in a
Host Server on page 161.
The procedure below assumes that the host server has been powered on
again after installation of the TSC. Note that the TSC must NOT be
connected to the network at this stage.
The following procedure must be performed on the active host, on the
running configuration. You should be logged in as ocadmin.
Step 1. Check that all TSCs are active. Do this on the active host using the
command ss7TscStatus -L.
Step 2. If you are satisfied with the new configuration, make it the running
configuration by carrying out one of the following:

run the command ss7HwAccept

accept the updated configuration in the ss7HwReplace window.

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

Configuring TSU/TSC Hardware


TSC Configuration: Removing a TSC from a Host Server

TSC Configuration: Removing a TSC from a


Host Server
This section contains the software configuration steps that you must
perform when removing a TSC from a TSC-in-system server (without
replacing the TSC). To remove a TSC, you must start with the
procedure Removing a TSC from a Host Server on page 164.
The procedure below assumes that the links associated with the TSC
have been removed from the stack, that the TSC has been removed from
the host server and that the TSU is powered on again.
The following procedure must be performed on the active host, on the
running configuration. You should be logged in as ocadmin.
Step 1. Update the running platform configuration using the cfgSs7HwUpdate
command (which performs a hardware auto-discovery of the hardware
elements removed).
Step 2. Check the updated configuration using the cfgSs7Hw -update -view
command.
Step 3. Load the configuration changes by running the command ss7HwLoad. Do
not accept the changes now - quit the tool or move to another window to
continue - if you accept the changes now, no rollback will be available.
Step 4. Check that the TSC has been removed from the configuration. Do this by
running the command ss7TscStatus -L on the active host.
Step 5. If you are satisfied with the new configuration, make it the new running
configuration by carrying out one of the following:

run the command ss7HwAccept

accept the updated configuration in the ss7HwLoad window.

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

Configuring TSU/TSC Hardware


LAN Configuration: Replacing a LAN Card in a TSU

LAN Configuration: Replacing a LAN Card in


a TSU
This section contains the software configuration procedure that you must
perform when replacing a LAN card in slot L1 of a TSU.
The procedure below assumes that the TSU has been powered on again
after installation of the LAN card and that the TSU LANs have been
connected to the platform hosts.
The steps of this procedure must be performed on the active host, on the
running configuration. You should be logged 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 the new configuration, make it the running
configuration by carrying out one of the following:

run the command ss7HwAccept

accept the updated configuration in the ss7HwReplace window.

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

answer affirmatively in the ss7HwAccept or ss7HwLoad window

execute the cfgPropagate command

Chapter 10

Configuring TSU/TSC Hardware


Adding and Activating Links on the SS7 Network

Adding and Activating Links on the SS7


Network
This section describes how to add and activate links on the SS7 network
when a new TSC is introduced into the HP OpenCall SS7 system.
The procedure below assumes that the TSC has been installed,
configured, validated and connected to the SS7 network, and that the
appropriate links have been created using the cfgSs7Hw -add -link
command.
Step 1. Add the link(s) to the stack.
From the SS7 Monitor screen, select Configure Entities |
Configure MTP | Configure Link/Linksets and add the new link(s).
Step 2. Activate the link(s).
In the SS7 Monitor screen, select Monitor Entities | Monitor MTP |
Link | Linksets, then type A.

Chapter 10

205

Configuring TSU/TSC Hardware


Configuring TSC Chained Links

Configuring TSC Chained Links


The Drop Insert feature is the ability to connect two E1/T1 TSCs in a
daisy chain arrangement in which one of the TSCs is directly connected
to the SS7 network. This allows the platform to increase the number of
timeslots that it can use.
This section describes how to configure the SS7 links for E1/T1 TSCs
that have been connected together in a daisy chain, and explains how to
configure alarm propagation. See Example of alarm propagation
configuration
The procedure below assumes that the TSCs have already been
physically connected together as required. An example arrangement is
shown in the figure below. You can chain together two TSCs only.
Figure 10-1

206

Example of Chained TSCs

Chapter 10

Configuring TSU/TSC Hardware


Configuring TSC Chained Links
Step 1. Create an initial hardware configuration using the cfgSs7HwCreate
command (which performs a hardware auto-discovery of the new
hardware elements).
Step 2. Configure the TSC using the cfgSs7Hw command. This command allows
you enable or disable chaining and alarm propagation when the TSC E1
ports are created or modified.
See the cfgSs7Hw manpage for details of command options and the
Example of alarm propagation configuration in the next section.
To configure the TSC:
1. Select the clock source for each of the TSCs. This can be set to be
internal or external:

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

a link LINK_A01 for Port 0 on TSC A, which maps to timeslot 1.

a link LINK_B15 for Port 1 on TSC B, which maps to timeslot 5.

207

Configuring TSU/TSC Hardware


Configuring TSC Chained Links
Step 3. 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 4. Activate the link(s). In the SS7 Monitor screen, select
Monitor Entities|Monit MTP|Monit lk/lkset, then activate the
link(s).
Step 5. 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.

Example of alarm propagation configuration


In the configuration shown in Figure 10-1, TSC 0 is chained so that Port
0 is chained to Port 2, and Port 2 is chained to Port 0.

NOTE

Alarm propagation is only possible on E1 TSCs. In the default


configuration, alarm propagation is disabled.

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

Expanding Platform Processing


Capability
This chapter describes how to expand your platforms processing
capability without any change of hardware.

Chapter 11

209

Expanding Platform Processing Capability


Expanding TCAP Processing Offline

Expanding TCAP Processing Offline


This section describes how to expand the TCAP processing capacity on
an off-line HP Opencall SS7 platform, in order to optimize performance.
TCAP expansion on a platform with an idle Local Point Code (SS7 stack)
is referred to as static expansion. The procedure in this section allows
you to expand (or contract) the TCAP processing capacity for more than
one LPC at the same time, if required.
Before following the procedure in this section, you must assess the
feasibility of your planned expansion. You need to determine whether it
is possible to expand the TCAP processing capacity from the currently
configured level to the desired level. However, you do not need to be
concerned with the details of the process redistribution, as the tools
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.

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

Expanding Platform Processing Capability


Expanding TCAP Processing Online

Expanding TCAP Processing Online


This section describes how to expand the TCAP processing capacity on a
running HP Opencall SS7 platform, in order to optimize performance.
TCAP expansion on a platform with a running SS7 stack is referred to as
dynamic expansion.
The procedures described in this chapter allow you to expand (or
contract) the TCAP processing capacity for a running Local Point Code
(SS7 stack). This involves first modifying the system configuration and
then applying these modifications to the running system.
This can be carried out using commands, as described in Online
Procedure on page 211.

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

Expanding Platform Processing Capability


Expanding TCAP Processing Online
You can also expand (or contract) the TCAP processing capacity for a
particular LPC from the command line.
Step 1. Save a back-up of the current configuration using the cfgMgr -copy
-toDir command.
Step 2. Prepare the required configuration modifications using the cfgTcap
-tune -dynamic command.
Step 3. Use the ss7TcapTune command to apply the changes to the running
system.
For details of the ss7TcapTune and cfgTcap commands, refer to the
relevant man pages.

212

Chapter 11

12

Updating TSCs and SS7 Links


This chapter contains a number of procedures related to updating the
platform hardware (such as adding and removing links).

Chapter 12

213

Updating TSCs and SS7 Links


Adding Link(s) to a TSC Port (on the Running Configuration)

Adding Link(s) to a TSC Port (on the Running


Configuration)
Each TSC has four ports. Each of these ports connects to one or more
links. The table below shows the link limitations for each TSC type.
Table 12-1

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

Updating TSCs and SS7 Links


Adding Link(s) to a TSC Port (on the Running Configuration)
There is also a maximum number of links for each port. If the existing
ports already have the maximum number of links assigned, you will need
to configure another port before you can add links. This is described in
the following procedure.

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

All software steps in the following procedure must be performed on the


active host on the running configuration.
You should be logged in as ocadmin.
To add link(s) to a port on an existing TSC:
Step 1. If you need to connect another port to the SS7 network in order to add
links, carry out the following (omit this step if you are adding links to an
already connected port):
a. Connect the TSC cable port connector to the network cable.
b. Label the cable, stating what it is (E1, T1, V.35) and where it is
connected to (TSC1, TSC2 etc).
c. Customize the TSC configuration (clockSource, coding, framing,
etc.) according to your network using the cfgSs7Hw -update
-modify -tsc command.
Step 2. Add the new link(s) using the cfgSs7Hw -update -add -link
command.
Make a note of the new link identifiers for the stack configuration.
Step 3. Load the changes:
a. If you have modified the port configuration in Substep c of Step 1,
divert the traffic from the TSC, as described in Diverting Traffic on
page 182.
b. Run the command ss7HwLoad.
Do not accept changes now - quit the tool or move to another window if you accept the changes now, no rollback will be available.

Chapter 12

215

Updating TSCs and SS7 Links


Adding Link(s) to a TSC Port (on the Running Configuration)
c. If you have diverted the traffic from the TSC, restore it now, as
described in Restoring the Traffic on page 183.
Step 4. 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 5. Activate the link(s). In the Stack Monitor screen, select
Monitor Entities|Monit MTP|Monit lk/lkset and type A.
All elements at the network end should be configured and activated, so
that the links can be aligned.
Step 6. 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 7. If you are happy with the new configuration, make it the running
configuration by carrying out either one of the following:

run the command ss7HwAccept

accept the updated configuration in the ss7HwLoad window.

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:

answer affirmatively in the ss7HwAccept or ss7HwLoad window

execute the cfgPropagate command

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

Updating TSCs and SS7 Links


Adding Link(s) to a TSC Port (on the Running Configuration)
Step 3. Rollback the changes:
a. If you have modified the port configuration in Substep c of Step 1 of
the main procedure, divert the traffic from the TSC, as described in
Diverting Traffic on page 182.
b. Rollback the configuration changes by carrying out either one of the
following:

run the command ss7HwRollback

reject the updated configuration in the ss7HwLoad window.

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

Updating TSCs and SS7 Links


Removing Links from a TSC (on the Running Configuration)

Removing Links from a TSC (on the Running


Configuration)
This section describes how to remove links associated with a Telecom
Signaling Card.

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).

All software steps in the following procedure must be performed on the


active host, on the running configuration.
You should be logged in as ocadmin.
Step 1. Deactivate the link(s) that you wish to remove. In the SS7 Monitor
screen, select Monitor Entities|Monitor MTP|Monit lk/lkset and
deactivate the link(s).
Step 2. Remove the 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.
Step 3. Remove the links using the cfgSs7Hw -update -remove -link
command.
Step 4. Load the changes by running the command ss7HwLoad.
Do not accept changes now - quit the tool or move to another window - if
you accept the changes now, no rollback will be available.
Step 5. Check that the links have been removed from the configuration. Use the
command ss7TsuStatus -L for a TSC-in-TSU platform or
ss7TscStatus -L for a TSC-in-system platform.
Step 6. If you are happy with the new configuration, make it the running
configuration by carrying out either one of the following:

218

run the command ss7HwAccept

Chapter 12

Updating TSCs and SS7 Links


Removing Links from a TSC (on the Running Configuration)

accept the updated configuration in the ss7HwLoad window.

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:

answer affirmatively in the ss7HwAccept or ss7HwLoad window

execute the cfgPropagate command

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:

run the command ss7HwRollback

reject the updated configuration in the ss7HwLoad window.

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

Updating TSCs and SS7 Links


Upgrading TSCs

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.

Checking the TSC is Active


Before upgrading your TSC, send your hardware supplier details about
your card. To get these details, the TSC must be active. The
ss7TscStatus command gives information about a specific TSC if you
use the -c option. The example below investigates TSC 10.
$ ss7TscStatus -c 10
giving the following output:
TSC

10, Name: TSC_10, Status: ACTIVE

Slot Number: 2, Type: E1_UNBALANCED, Class Name: Stack_1


If the status of the card is not active then you must activate it.

Getting the Serial Number and Number of Links


Once you have established that you are working with an active TSC, use
the ss7HwInfo command to find out the information your hardware
supplier needs:

Example 12-1

The number of links the card can currently handle

The serial number of the card

The total number of links licensed for your platform

ss7HwInfo Output
If you execute the command without options as follows:
ss7HwInfo

220

Chapter 12

Updating TSCs and SS7 Links


Upgrading TSCs
then, you obtain the following output (note that only part of the output is
shown below):
.......
TSC
1:
Hardware: PCI Adapter
Part Number
:
Serial Number
:
EC Level
:
Links
:
Protocols
:
Limit violation :
.......

0000087H3772
00004120
000000E68645
16
SS7
00

FRU Number
: 0000087H3427
Manufacturer ID : 196G000000
ROS Level and ID : 2.2

Performing the Upgrade


This upgrade is performed using the command ss7TscUpgrade which
must be run on a front-end machine that has a configured connection to
the TSC that is being upgraded. The TSC must be powered on and
accessible to the system. The current operation of the TSC is not affected
by the upgrade.
The user should be logged onto the active host as ocadmin.
If no errors are reported then the new configuration of the TSC can be
accessed via the ss7HwInfo command. Once the upgrade has been
performed, new links can be added to the TSC using the cfgSs7Hw
command.

NOTE

If you are prompted for a platform license, configure and propagate this
using the cfgPropagate command.

ss7TscUpgrade runs with the following parameters:


Table 12-2

ss7TscUpgrade Parameters

Parameter

Name

Function

-c

tscId

The tscId of the TSC card being upgraded

-p

licenseCodeword

The codeword supplied by HP

Chapter 12

221

Updating TSCs and SS7 Links


Upgrading TSCs
The command is executed as follows:
ss7TscUpgrade -c <TSC_ID> -p <codeword>
where <TSC_ID> is the number that identifies the TSC and <codeword>
is the license codeword provided by HP.

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

ss7TscUpgrade Error Messages


Error Message

Meaning

Corrupted codeword

The codeword cannot be decoded correctly.


Check that it has been typed in correctly.

TSC <%d> not configured

No TSC with this identification is configured or


the configuration has not been deployed on the
system.

TSC <%d> inaccessible

Communication with the specified TSC is not


possible.

TSC <%d> has serial number that


does not match in the codeword

The serial number in the licensed codeword


does not match that of the specified TSC card.

TSC has incorrect number of links

The number of links in the TSC card does not


match the number in the codeword.

222

Chapter 12

Updating TSCs and SS7 Links


Upgrading TSCs

Labeling Your Upgrade


The upgrade kit includes a set of labels. Each label corresponds to a
combination of card type and link capability. When you have completed
your upgrade, attach the appropriate label (corresponding to your card
type and new link capability) to the front of the TSC.
Table 12-4
TSC Type

Chapter 12

Upgrade Kit Label Set


No. of Links

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

Updating TSCs and SS7 Links


Upgrading TSCs

224

Chapter 12

13

Expanding Your Platform:


Adding a Back End
This chapter contains the procedure for the addition of a Back End to
create a distributed system.

Chapter 13

223

Expanding Your Platform: Adding a Back End


Overview

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

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End

Creating FE/BE System by Adding a Back End


The procedure below details how to expand a 2-host platform to create a
Front End/Back End architecture by adding a Back End computer.
On completion of this procedure, the original computers will perform SS7
stack processing at the Front End (FE) and the new computer will
perform all application processing at the Back End (BE). This
architecture is illustrated in Figure 13-1.

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

This is an online procedure. Traffic processing will not be interrupted but


will be momentarily disrupted.

Chapter 13

225

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Figure 13-1

Before and After Back End Expansion

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

to/from SS7 Network


via TSUs/TSCs

LAN

LAN

LAN

LAN

LAN

to/from SS7 Network


via TSUs/TSCs

The procedure assumes the following pre-requisites:


Pre-requisites

The new computer that is to become the BE has already been


installed with the operating system, the applications and the
HP OpenCall SS7 software (but is not connected to the platform).

The LAN cards required in the BE computer have already been


installed and configured. This computer requires two LAN ports.
Refer to the note below for important information on LAN
connections.

226

Chapter 13

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End

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

It is your responsibility to decide how to migrate the running


applications from the Front End to the Back End.

227

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End

Stage 1: Saving Configuration from an FE Host to an


Accessible Place
Host
This is done on the host that you normally use to modify and propagate
the configuration.

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

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Result
No change in the configuration.

Front End

Switch

LAN
Host

LAN
Host

Applications: Running
HP OC SS7: Running

LAN

Switch

Applications: Running
HP OC SS7: Running

LAN

LAN

LAN

to/from SS7 Network


via TSUs/TSCs

Rollback
Remove the saved configuration.

Chapter 13

229

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End

Stage 2: Stopping HP OpenCall SS7 on One of the


Hosts
Host
This is done on the host that you normally use to modify and propagate
the configuration.

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

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Result

Front End

Switch
LAN

Switch

Host

Host

Applications: Not Running


HP OC SS7: Not Running

LAN

LAN

LAN

Applications: Running
HP OC SS7: Running

LAN

LAN

to/from SS7 Network


via TSUs/TSCs

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

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End

Stage 3: Connecting the BE Computer to the FE Hosts


and Testing the Connections
Host
This involves work on both FE hosts and on the BE computer.

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

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Result

Back End
NEW Computer
Applications: Not Running

LANs

Switch

Switch

LAN

Front End

LAN

Host

LAN

Host

Applications: Not Running


HP OC SS7: Not Running

LAN

LAN

LAN

Applications: Running
HP OC SS7: Running

LAN

LAN

to/from SS7 Network


via TSUs/TSCs

Chapter 13

233

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Rollback
Step 1. On each FE host, restore the file ~ocadmin/.rhosts file that you backed
up in Stage 1.
Step 2. On each FE host, restore the file etc/rhosts file that you backed up in
Stage 1.
Step 3. Disconnect the BE computer and the FE hosts from the two switches.

234

Chapter 13

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End

Stage 4: Adding the BE Computer to the Software


Configuration and Propagating the Configuration
Host
This is done on the idle host.

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

When propagating, ignore the warning about HP OpenCall LAN


Configuration. This warning is normal.

235

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Result

Back End
NEW Computer
Applications: Not Running

LANs

Switch

Switch

LAN

Front End

LAN

Host

LAN

Host

Applications: Not Running


HP OC SS7: Not Running

LAN

LAN

LAN

Applications: Running
HP OC SS7: Running

LAN

LAN

to/from SS7 Network


via TSUs/TSCs

236

Chapter 13

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Rollback
Step 1. Using the command cfgPlatform -remove -backEnd. to remove the BE
computer from the running configuration. See the MAN pages for more
details.
Step 2. Propagate the modified running configuration to the other FE host and
to the BE computer using the command cfgPropagate. See the MAN
page for more details.

NOTE

Chapter 13

When propagating, ignore the warning about HP OpenCall Lan


Configuration.

237

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End

Stage 5: Updating the HP OpenCall SS7 LAN


Configuration, and Propagating the LAN
Configuration.
Host
This is done on the idle FE host.

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

When specifying the hostnames and the IP addresses of the BE computer


for each LAN, be careful to associate the correct IP address with the
correct LAN. Use the configuration details you noted in the previous
step.

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

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Result

Back End
NEW Computer
Applications: Not Running

LANs

Switch

Switch

LAN

Front End

LAN

Host

LAN

Host

Applications: Not Running


HP OC SS7: Not Running

LAN

LAN

LAN

Applications: Running
HP OC SS7: Running

LAN

LAN

to/from SS7 Network


via TSUs/TSCs

Chapter 13

239

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Rollback
Step 1. On the idle FE host, remove the BE computer from the HP OpenCall SS7
LAN configuration.
For each HP OpenCall SS7 LAN, use the command below to remove the
LAN connection for the BE computer.
cfgPlatform -remove -ocLan -host
See the MAN page for more details.
Step 2. 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.

240

Chapter 13

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End

Stage 6: Restarting HP OpenCall SS7 on the Idle Host


Host
This is done on the idle FE host.

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

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Result

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

to/from SS7 Network


via TSUs/TSCs

242

Chapter 13

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Rollback
Step 1. Stop all user applications on the host.
Step 2. Disable the auto-restart of 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 of HP OpenCall SS7, using the command
ss7Stop -all.

Chapter 13

243

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End

Stage 7: Loading the Changes on the Other Host


Host
This is done on the FE host on which HP OpenCall SS7 that has not yet
been stopped.

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

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Result
No change.

Rollback
None.

Chapter 13

245

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End

Stage 8: Migrate Your Applications from the FE to the


BE Computer
Host
This involves work on all computers of the platform.

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

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End
Result

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

to/from SS7 Network


via TSUs/TSCs

Rollback
None.

Chapter 13

247

Expanding Your Platform: Adding a Back End


Creating FE/BE System by Adding a Back End

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

SS7 Monitor Screen

Start and Stop


Commands

Start and stop the SS7 Monitor using the ss7MgrStart and ss7MgrStop
commands.

250

Appendix A

Tools Catalog
Command Line Tools

Command Line Tools


In addition to the graphical tools listed above, a number of command line
tools are provided with HP OpenCall SS7. Some are complementary to
the graphical tools, providing additional functions. Others provide an
alternative way to carry out the same tasks. In general, if both a
graphical and a command line tool exists, use the graphical tools, as they
provide more rigorous consistency checking and security. Use the
command line version only if the graphical tools are unavailable, or if
you need to work in batch mode.
You can use almost all of the commands as a member of the group
ocadmin. Exceptions are noted in the Comment column.
For detailed information on all of the commands listed in this section,
refer to the man pages.
Table A-1
Command

Platform Configuration Commands


Function

cfgCheck

Checks configuration is coherent

cfgCreate

Creates a new configuration

cfgInstall

Installs a new configuration

cfgMgr

Manages configurations

cfgPatch

Patches an existing configuration

cfgPropagate

Propagates a configuration to all hosts in a platform

cfgSs7HwCreate

Carries out hardware autodiscovery and creates a


hardware configuration.

cfgSs7HwUpdate

Carries out hardware auto-discovery to update an


existing hardware configuration (after a hardware
element has been added or removed)

cfgPlatform

Changes the platform license, adds/removes a BE,


adds/removes AGs, adds/removes an SNMP agent

Appendix A

Comment

251

Tools Catalog
Command Line Tools
Table A-1
Command

Platform Configuration Commands (Continued)


Function

cfgSs7Hw

Creates links and updates the hardware


configuration. Completes the configuration after
autodiscovery.

cfgMtp

Creates or updates an MTP3 configuration

cfgSccp

Creates or updates an SCCP configuration

cfgTcap

Creates or updates a TCAP configuration. In


particular, modifies TCAP parameters, or tunes
TCAP performance.

cfgIsup

Creates or updates an ISUP configuration

cfgTup

Creates or updates a TUP configuration

Table A-2
Command

Comment

Platform Start and Stop Commands


Function

Comment

ss7Start

Starts the SS7 Platform

This must be run


on the Front End.

ss7Stop

Stops the SS7 Platform

This must be run


on the Front End.

Table A-3
Command

Platform Management Commands


Function

ss7MgrStart

Starts the SS7 Monitor

ss7MgrStop

Stops the SS7 Monitor

ocftcontrol

Performs actions on processes by the FTC

ocftstatus

Displays the status of the processes by the FTC

252

Comment

Appendix A

Tools Catalog
Command Line Tools
Table A-4

Stack Related Commands

Command

Function

loadconf

Loads a configuration from an existing file

ss7CheckPoint

Saves the stack configuration to a file.

Table A-5

isupgenITU
ss7IsupReload

Table A-6
Command

Can also be done from


within the SS7
Monitor

ISUP Commands

Command
isupgenANSI

Comment

Function

Comment

Sets up and releases ISUP calls for test


purposes

Refer to the man page


for full instructions.

Dynamically reloads the ISUP


configuration

Refer to the man page


for full instructions.

TUP Commands
Function

Comment

tupgen

Sets up and releases TUP calls for test


purposes

Refer to the man page


for full instructions

ss7TupReload

Dynamically reloads the TUP configuration

Refer to the man page


for full instructions.

Table A-7
Command

Hardware Related Commands


Function

ss7Diag

Tests and troubleshoots the SS7 links.

ss7HwAccept

Replaces the current hardware


configuration with a loaded configuration.

ss7HwInfo

Displays information on SS7 hardware

ss7HwInit

Initializes SS7 hardware.

ss7HwLoad

Loads a new hardware configuration.

Appendix A

Comment

253

Tools Catalog
Command Line Tools
Table A-7

Hardware Related Commands (Continued)

Command

Function

ss7HwReplace

Automatically updates the hardware


configuration after a hardware
replacement.

ss7HwRollback

Deletes the updated hardware


configuration file and reloads the previous
one.

ss7TcapTune

Dynamically loads the TCAP level modified


using the cfgTcap command.

ss7TscPing

Pings TSC

ss7TscStatus

Displays TSC status

ss7TscUpgrade

Upgrades the number of links on a TSC

ss7TsuPing

Obtains the LAN paths and MAC addresses


the TSU connections to a given host

ss7TsuStatus

Displays TSU status

Table A-8
Command

Log Related Commands


Function

cleanttl

Stops logging and cleans out existing log


files.

nlog

Displays logs without opening a new


window.

nmsg

Displays traces without opening a new


window.

ss7SNMPAgent

Maps logs to SNMP traps

ss7HwTrace

Manages logs and traces for TSCs and


TSUs.

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

Log Related Commands (Continued)

Command

Function

Comment

ss7TcapSnmpAgent

Provides access to the TCAP managed


objects.

Enter the
-displaytext or
-displayhtml option
to list the TCAP
managed objects.

startnettl

Starts logging.

You must be root to use


this command.

stopnettl

Stops logging.

You must be root to use


this command.

wlog

Opens a log window.

wmsg

Opens a trace window.

Table A-9
Command

Traffic Generation Commands


Function

tcxgen

Generates TCAP traffic for test purposes.

trafgen

Generates MTP traffic for test purposes.

Table A-10
Command

Other Commands
Function

collectInfo

Collects information on system,


versioning, configuration and debugging
the platform.

ss7License

Reloads the license after it has been


changed using the cfgPlatform command
with the -license -upgrade -dynamic
options.

ss7oamtool

Provides operation, administration and


management functions on the
HP OpenCall SS7 platform.

Appendix A

Comment

Comment
Intended primarily for
use by HP support
personnel.

255

Tools Catalog
Command Line Tools
Table A-10
Command
whichPathFor

256

Other Commands (Continued)


Function

Comment

Returns absolute path of requested item

Appendix A

Tools Catalog
Web-based Management Tools

Web-based Management Tools


The web-based management tool allow you to monitor the state of
signaling resources (for example: TSU and TSC) and a set of
performance ndicators (for example TCAP tps).
This section explains how to configure and enable the web platform
monitoring service.
Actions
Step 1. Start the Apache server on each of the SS7 hosts.
On RedHat Linux, enter:
service httpd start
On Debian, enter:
apache start
The URL for accessing the web platform monitoring service is:
http://<hostname>/ftm/index.html
Before starting the platform, make sure that the /etc/hosts file on each
of the hosts from which the platform monitoring service needs to be
accessed contains the required entry.
Step 2. Install the JRE 1.3.1_03 (or above) plug-in on the host where the web
browser is running: The JRE plug-in can be downloaded from:
http://java.sun.com/j2se/1.3/download/html
Step 3. After installing the browser, configure the plug-in for your system.
On Windows:
a. Open the Control Panel
b. Click the Java plug-in icon. On the browsers tab, select Netscape
and/or Internet Explorer.
c. Close all open browser windows for the change to take effect.

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

Telecom Signaling Cards


(J3527A and J3528A)
This appendix describes the Telecom Signaling Cards (TSCs) that can be
used to connect an HP OpenCall SS7 platform to the SS7 network.

Appendix B

259

Telecom Signaling Cards (J3527A and J3528A)


Function

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 Telecom Signaling Unit (TSU) which connects to the host and to


the signalling network

a host server with a PCI bus that can take TSCs directly. This is
referred to as TSC-in-system.

A Telecom Signaling Card has four physical ports available for


connection to the network. Each of these ports is assigned to one or more
links. The number of possible links depends on the type of TSC used.

260

Appendix B

Telecom Signaling Cards (J3527A and J3528A)


Types of Telecom Signaling Card

Types of Telecom Signaling Card


There are two types of TSC:

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

Telecom Signaling Cards (J3527A and J3528A)


Physical Description

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 Telecom Signaling Card


The figure below shows the V.35 Telecom Signaling Card mounted on the
adapter card.
Figure B-1

V.35 Telecom Signaling Card

V.35 PMC

L1 LED
AdapterCard
L2 LED

120-pinConnector
L1 LED

262

Appendix B

Telecom Signaling Cards (J3527A and J3528A)


Physical Description
LEDs

Refer to Checking LEDs on page 175 for a description of the LEDs.

Ports and Links

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

A V.35 TSC is supplied with a defined number of links, as detailed above.


This number can be upgraded (up to a maximum of 4) without removing
the card from the platform. Refer to the Adding and Activating Links on
the SS7 Network on page 205 for information on upgrading the TSC link
capability.

E1/T1 Telecom Signaling Card


The figure below shows the E1/T1 Telecom Signaling Card mounted on
the adapter card.

Appendix B

263

Telecom Signaling Cards (J3527A and J3528A)


Physical Description
Figure B-2

E1/T1 Telecom Signaling Card

LEDs

Refer to Checking LEDs on page 175 for a description of the LEDs.

Ports and Links

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

Telecom Signaling Cards (J3527A and J3528A)


Physical Description
Upgrading the
Number of Links

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

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables

TSC Connectors and Cables


This section describes the connectors and cables required to connect a
Telecom Signaling Card to the signaling network. A TSC is connected to
the signaling network from a connector on the end-plate of its PCI
adapter card.
The connectors and cables required depend on the type of TSC (and, in
the case of an E1/T1 card, the telecommunications protocol to be used).
Four sets of connectors are described here:
Connection

Description

Section Reference

E1

To connect an E1/T1 TSC to the network


using the E1 protocol.

E1 Connections on page 266

T1

To connect an E1/T1 TSC to the network


using the T1 protocol.

T1 Connections on page 270

V.35

To connect a V.35 TSC to the network.

V.35 Connections on page 271

Loopback

To connect up a TSC for loopback testing.

Loopback Hoods on page 275

In addition, the optional connection panels that can be used to organize


TSC cabling are described in Connection Panels on page 281.

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

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Figure B-3

TSC 36 Pin Connector (E1/T1)

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

RJ-45 Connector (E1/T1)

267

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Figure B-5

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

E1 RJ-45 Connector Pinouts

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

E1 BNC Connector Pinouts - Grounded

TSC Connector Pin

Port
0

268

Signal
Name

TSC Connector Pin

Port
1

Port
2

Signal
Name

I/O
(Input/
Output)

Port
3

Appendix B

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Table B-2

E1 BNC Connector Pinouts - Grounded

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

E1 BNC Connector Pinouts - Ungrounded

BNC
Connector

E1 Cable
Specification

Signal
Name

TSC Connector Pin

Signal
Name

TSC Connector Pin

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

When constructing an E1 cable assembly, you should follow the


guidelines below:

24 AWG copper conductor, twisted pair telephone cable.

Impedance
E1 balanced 120 ohms
E1 unbalanced 75 ohms

Appendix B

269

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables

DC resistance (single conductor) of 23.7 ohms/1000 meters.

Shunt capacity of 16 pF/foot.

Shield terminated with a frame ground pin.

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

BNC Unbalanced, Grounded

8 BNC
(2 per port)

5063-1330

BNC Unbalanced, Ungrounded

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

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
T1 Connector
Pinouts

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

T1 RJ-45 Connector Pinouts

RJ-45
Pin

T1 Cable
Specification

Signal
Name

TSC Connector Pin

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 cables have an impedance of 100 ohms.


The table below gives the corresponding cable assembly and its HP part
number.
Table B-6

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

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Figure B-6

TSC Connector (V.35)

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

V.35 DTE Connector

Appendix B

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Figure B-8

V.35 DCE Connector

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

V.35 DTE Connector Pinouts

DTE Pin

Appendix B

Signal
Name

TSC Connector Pin

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

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Table B-7

V.35 DTE Connector Pinouts (Continued)

DTE Pin

Table B-8

I/O
(Input/
Output)

Signal
Name

TSC Connector Pin

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

V.35 DCE Connector Pinouts

DCE Pin

Signal
Name

TSC Connector Pin

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

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Table B-8

V.35 DCE Connector Pinouts (Continued)

DCE Pin

Signal
Name

TSC Connector Pin

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

V.35 Cable Assemblies


Network
Connectors

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

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables

Cable Loopback Hoods: These connect to the end of the TSC


cables (to the network end) and can therefore be used to test the
operation of the TSC in conjunction with the TSC network cables.
These hoods are available in three types, for the different types of
cable, and are supplied with the cables:
HP Part
Number

Loopback Hood Type


E1/T1 RJ-45

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

V.35 DTE Cable Loopback Pinout

From

276

To

Signal

Pin

TXDxA

TCLKIxA

Signal

Pin

RXDxA

Appendix B

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Table B-10

V.35 DTE Cable Loopback Pinout (Continued)

From

To

TXDxB

RXDxB

RCLKIxA

TCLKxB

RCLKIxB

RTSx

CTSx

CDx

DTRx

DSRx

TCLKIxB

AA

TCLKOxA

Table B-11

V.35 DCE Cable Loopback Pinout

From

To

Signal

Pin

Signal

Pin

RXDxA

TXDxA

RXDxB

TXDxB

RCLKxA

TTExA

RCLKxB

TTExB

RTSx

CTSx

DSRx

DTRx

Table B-12

V.35 TSC Card Loopback Pinout

From

Appendix B

To

Signal

Pin

DTR0A

112

Signal

Pin

DSR0A

98

CD0A

94

277

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Table B-12

V.35 TSC Card Loopback Pinout (Continued)

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

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Table B-12

V.35 TSC Card Loopback Pinout (Continued)

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

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Table B-12

V.35 TSC Card Loopback Pinout (Continued)

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

E1/T1 RJ-45 Cable Loopback Pinout

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

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables

Table B-14

E1/T1 TSC Card Loopback Pinout

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

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Connection panels are available from HP for the different types of cable
assembly. These are listed in the table below which details the number of
TSC ports supported, along with the HP product number and part
number.
Table B-15

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

A BNC connection panel is illustrated in Figure B-9. The RJ-45


connection panel is similar but with one hole per port.

282

Appendix B

Telecom Signaling Cards (J3527A and J3528A)


TSC Connectors and Cables
Figure B-9

Appendix B

BNC Connection Panel (Example for E1)

283

Telecom Signaling Cards (J3527A and J3528A)


TSC Electrical and Environmental Specifications

TSC Electrical and Environmental


Specifications
This section provides electrical and environmental information for TSCs.
This includes power supply requirements as well as operational and
non-operational environmental requirements.
Power Supply

The power consumption of a TSC is 13.5 W.

Environmental
Requirements

The table below provides the operational and non-operational


environmental requirements for a TSC. If you require any additional
environmental information, contact Hewlett-Packard.
Table B-16

TSC 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

Telecom Signaling Units


(J3401A)
This appendix describes the Telecom Signaling Unit (TSU) which can be
used to the accommodate the Telecom Signaling Cards (TSCs).

Appendix C

285

Telecom Signaling Units (J3401A)


Function

Function
The Telecom Signaling Unit (TSU) provides accommodation for the
following PCI cards:

Telecom Signaling Cards (TSCs)


The TSCs provide the physical connectivity to the signaling network.

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 TSU can be employed as part of:

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)

a 1-host platform requiring more SS7 links than can be provided by a


TSC-in-system server

a 2-host platform (for High Availability).

Up to eight TSUs can be connected to an SS7 platform.

286

Appendix C

Telecom Signaling Units (J3401A)


Physical Description

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:

Five slots are reserved for Telecom Signaling Cards.


The number of TSCs that can be accommodated depends on the type
of cards, as follows:
up to five V.35 cards (in slots 1, 2, 3, 4 and 5), or
up to three E1/T1 cards (in slots 1, 3 and 5).

The other two slots are reserved for:


the TSUs fixed CPU card (slot L0) which also provides a LAN
connection to the host computer.
a LAN card (slot L1) which can be installed to provide a
connection to a second host.

A TSU is connected to a host computer via a dedicated point-to-point


100 BASE-T LAN interface to a 100 BASE-T card on the host:

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

It is not possible to have a dual LAN connection between a TSU and a


single server.

Appendix C

287

Telecom Signaling Units (J3401A)


Physical Description
Power Supplies

A TSU can be run from an AC or DC power supply. Details of these power


supplies are provided in TSU Electrical and Environmental
Specifications on page 290.
The power supply unit of a DC powered TSU is attached to two power
rails for High Availability (so that if one rail fails, power is still
available).

Part Numbers

The part number of a TSU depends on the power supply, as follows:


Table C-1

TSU 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

Telecom Signaling Unit - Front View

Appendix C

Telecom Signaling Units (J3401A)


Physical Description
Figure C-2

Telecom Signaling Unit - Front View with Frontplate Removed

Figure C-3

Telecom Signaling Unit (AC Powered) - Back View

Appendix C

289

Telecom Signaling Units (J3401A)


TSU Electrical and Environmental Specifications

TSU Electrical and Environmental


Specifications
This section provides electrical and environmental information for TSUs.
This includes power supply requirements as well as operational and
non-operational environmental requirements.
AC Power Supply

The power supply requirements for a TSU operating from an AC supply


are presented in the table below.
Table C-3
Input Current

AC Power Supply Specifications for a TSU


100-127 V AC input: 3 A
200-240 V AC input: 1.3 A

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

Telecom Signaling Units (J3401A)


TSU Electrical and Environmental Specifications
DC Power Supply

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

DC Power Supply Specifications for a TSU


for -40 V DC input: 8 A
for -76 V DC input: 3.5 A

Input Voltage

TNV-2 DC: -40 to -72 V DC with dual


input

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

Telecom Signaling Units (J3401A)


TSU Electrical and Environmental Specifications
Figure C-4

DC Power Supply Connector - Side view

Figure C-5

DC Power Supply Connector - Pins

Table C-5

DC Power Supply Connector Pinout


Signal

292

Pin

DC Return

DC

DC Return

Appendix C

Telecom Signaling Units (J3401A)


TSU Electrical and Environmental Specifications
Table C-5

DC Power Supply Connector Pinout (Continued)


Signal

Environmental
Requirements

Pin

DC

Not Used

2,3,5,6.

The table below provides the operational and non-operational


environmental requirements for a TSU. If you require any additional
environmental information, contact Hewlett-Packard.
Table C-6

TSU Environmental Requirements

Parameter
Temperature
Humidity
(Non-Condensing)

Appendix C

Operational Range

Non-Operational
Range

0C to 50C

-40C to 70C

5% to 95% relative humidity

293

Telecom Signaling Units (J3401A)


TSU Electrical and Environmental Specifications

294

Appendix C

Configuring the Application


Guardian
This appendix describes how to configure the HP OpenCall Application
Guardian (Plug-In Container/Application Guardian).

Appendix D

295

Configuring the Application Guardian


Configuration Basics

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.

Naming Convention for Plug-In Server Names


Plug-In servers can be addressed directly using the following format:
<port>@<IP_address>

More generally, the format is as follows:


<first part>@<second part>
The "@" character is the separator between the two parts and is
mandatory. Consequently, it should not appear in either part.
The first part resolves to a port, and it must be unique in /etc/services
(both its name and its number). See also Configuring Entries in
/etc/services on page 300.
The second part must always resolve to the IP address of the local host,
since the plug-in runs on the FE (Front-End) server of the HP OpenCall
platform. The Application Guardian engine configuration allows you to
specify the second part of the name (that is, the IP address part).

296

Appendix D

Configuring the Application Guardian


Overview of Configuration

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

Configuring the Application Guardian


Configuring Application Guardian engine

Configuring Application Guardian engine


This must be done using the cfgPic command. For more details, see the
cfgPic man page.

Application Guardian engine Internal Parameters


Each Application Guardian engine instance needed by a user plug-in
must be configured. These parameters are stored in a configuration file.
This file contains internal setup and configuration information.
There is one such file for each PIC. Therefore, you must choose a
different name for each PIC. The PIC configuration file is defined as:
<plug-in global name>.conf

where <plug-in global name> is as described in Global Name for Plug-In


Process on page 296.
There is an example configuration file in the Plug-In configuration
directory.

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.

Pre-Defined Plug-Ins (AG_x)


In HP OpenCall SS7 3.1 on Linux only supports pre-defined plug-in
(AG_x).
Four (4) plug-in processes are pre-defined. Their plug-in global names
are: AG_1, AG_2, AG_3, and AG_4.
A configuration is proposed to the user. To use these pre-defined plug-ins,
you must supply values for all the mandatory parameters (for example,
the user plug-in shared library path).
Use the command line tool to add and configure the AG plug-in:

298

Appendix D

Configuring the Application Guardian


Configuring Application Guardian engine

cfgPlatform -add -applicationGuardian <AG_id>


To remove an AG plug-in, use the same command with the remove
option:
cfgPlatform -remove -applicationGuardian <AG_id>
For further details, see the man page.
After adding an Application Guardian, enter the following command to
view the configuration:
cfgPlatform -view -applicationGuardian <AG_id>
See the manpage for details of the command line tools and options.

Appendix D

299

Configuring the Application Guardian


Configuring Entries in /etc/services

Configuring Entries in /etc/services


The <port numbers> used in the plug-in name must be registered in the
/etc/services file.
The TCP ports for the pre-defined plug-ins, described in Pre-Defined
Plug-Ins (AG_x) on page 298, are already present in the /etc/services
file.
The following entries are automatically added in the /etc/services file:
ha_ag_1
ha_ag_2
ha_ag_3
ha_ag_4
ha_hb_ag_1
ha_hb_ag_2
ha_hb_ag_3
ha_hb_ag_4

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

# HP Opencall Plugin - FTC HA management port

Plug-In Using the Active/Standby Model


If the plug-in uses the Active/Standby Model and needs peer heartbeats:
ha_hb_ag_1

12346/tcp

# HP Opencall Plugin - peer Plugin Heartbeats port

Plug-In Implementing PCA Server


If the plug-in implements a PCA server:
pca_server_plugin_1

300

12347/tcp

# HP Opencall Plugin PCA server port

Appendix D

Configuring the Application Guardian


Configuring the User Plug-In

Configuring the User Plug-In


This includes configuring any facilities needed by the plug-in and
creating the user plug-ins own configuration file (if it uses one).
This operation completely depends on the nature of the users
application.
It is not described in this guide.

Appendix D

301

Configuring the Application Guardian


Including the Plug-In Processes in the HP OpenCall Environment

Including the Plug-In Processes in the


HP OpenCall Environment
This is done using the cfgPlatform command. For more details, see the
man page.

The Application Guardian engine Run String


During configuration, you specify the Application Guardian engine run
string.
The Application Guardian engine executable run string contains the
following arguments:
/opt/OC/bin/PluginContainer[<trace>] -c <file> [-E] [-N]

where:
trace

Specifies the name of the section in debug.conf to be


used by this Application Guardian engine. The default
name is PlugIn.

-c <file>

Specifies the user plug-in configuration file. The file


name may include the path to access the configuration
file. This argument is mandatory.

-E

If set, exit on initialization error. By default, do not


exit.

-N

If set, the Application Guardian engine Process is not


HA. By default, the process is HA.

Declaring the Application Guardian engine Process


as HA or Not
Each plug-in must be added for startup and configured as a respawnable
(RS) or an active/standby (HA) process.
Note that:

302

A Application Guardian engine process declared as HA (that is, HA


or HN) must be launched without the argument -N in the run string.

Appendix D

Configuring the Application Guardian


Including the Plug-In Processes in the HP OpenCall Environment

A Application Guardian engine process declared as not HA (that is,


RS or RO) must be launched with the argument -N in the run string:
/etc/opt/OC/bin/PluginContainer ........ -N

If a Application Guardian engine process needs a lot of processing


time, you should allocate it to a dedicated processor using the
PreferredProcessor attribute.

You give the configuration file name (and path) as a mandatory


argument (using the -c option) on the Application Guardian engine
executable run string:
/etc/opt/OC/bin/PluginContainer ... -c <conf-file> .....

To enable Application Guardian engine tracing, you must include the


<plug-in global name> in the run string as follows:
/etc/opt/OC/bin/PluginContainer <plug-in global name> ...

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

Configuring the Application Guardian


Including the Plug-In Processes in the HP OpenCall Environment

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

replacing TSU DC power supply, 132


man page, adding PATH to enable access, 21
memory
dimension of main, 23
main and real, 23
monitoring
PINS, 59
MTP
timers, 24
MTP2

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

configure Local Point Code, 70


linkset, 72
monitor SCCP, 97
ss7CheckPoint, 252
ss7Diag, 253
ss7HwAccept, 253
ss7HwInfo, 253
ss7HwInit, 253
ss7HwLoad, 253
ss7HwReplace, 253
ss7HwRollback, 253
ss7HwTrace, 254
ss7IsupReload, 253
ss7License, 255
ss7MgrStart, 92, 252
ss7MgrStop, 252
command options, 92
ss7oamtool, 255
ss7SNMPAgent, 254
ss7Start, 64, 252
ss7Stop, 63, 252
ss7TcapTune, 212 , 253
ss7TscPing, 253
ss7TscStatus, 254
ss7TscUpgrade, 254
ss7TsuPing, 254
ss7TsuStatus, 254
stack
process states, 86
stack configuration
loading, 79
starting
SS7 Monitor, 92
startnettl, 254
states
ACTIVE (process), 86
BOOTING (process), 86
DOWN (process), 86
stack processes, 86
SYNCHRONIZING (process), 86
UNKNOWN (process), 86
statistics
data for entity, 98
status
HA (PINS), 60
stopnettl, 254
STP, configuring gateway, 72
swapping limitations, 23

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

fans, 126, 176, 289


function, 286
installation, 115
installing cards, 113
LAN card, 139
LEDs, 176
loading the configuration, 50
maintenance procedures, 121
PCI slots, 113, 287
power cord, 19, 291
power supplies, 287
rear panel connectors, 117
removing and replacing card cage, 169
removing and replacing cover, 168
removing from server cabinet, 168
replacing, 153
Time, 24
timers
MTP, 24
SCCP, 24
TCAP, 24
trafgen tool, 255
Traps
activating SNMP Traps, 88, 89
configuring SNMP Traps, 88, 89
validating SNMP Traps, 88, 89
TSC-in-system, 260
tupgen, 253
U
uncongested route, 96
UNKNOWN state
process, 86
user
adding PATH to profile, 21
V
V.35 cards, 261 , 262
cable assembly, 275
connections, 271
links, 263
ports, 263
validating
configuration, 65
HA, 86
HP Opencall SS7 installation, 65
OS installation, 65
SNMP Traps, 88, 89
SS7 connectivity, 83
309

Index
W
whichPathFor, 255
wlog, 254

310

Вам также может понравиться