SINAP/IP User s Guide

Transcription

1 SINAP/IP User s Guide Stratus Technologies R

2 Notice The information contained in this document is subject to change without notice. UNLESS EXPRESSLY SET FORTH IN A WRITTEN AGREEMENT SIGNED BY AN AUTHORIZED REPRESENTATIVE OF STRATUS TECHNOLOGIES, STRATUS MAKES NO WARRANTY OR REPRESENTATION OF ANY KIND WITH RESPECT TO THE INFORMATION CONTAINED HEREIN, INCLUDING WARRANTY OF MERCHANTABILITY AND FITNESS FOR A PURPOSE. Stratus Technologies assumes no responsibility or obligation of any kind for any errors contained herein or in connection with the furnishing, performance, or use of this document. Software described in Stratus documents (a) is the property of Stratus Technologies Bermuda, Ltd. or the third party, (b) is furnished only under license, and (c) may be copied or used only as expressly permitted under the terms of the license. Stratus documentation describes all supported features of the user interfaces and the application programming interfaces (API) developed by Stratus. Any undocumented features of these interfaces are intended solely for use by Stratus personnel and are subject to change without warning. This document is protected by copyright. All rights are reserved. No part of this document may be copied, reproduced, or translated, either mechanically or electronically, without the prior written consent of Stratus Technologies. Stratus, the Stratus logo, ftserver, the ftserver logo, and SINAP are registered trademarks of Stratus Technologies Bermuda, Ltd. The Stratus Technologies logo, the Stratus 24 x 7 logo, Stratus Inter-network Services Signaling Gateway, Converged Personalized Services, Mobile Call Convergence, and Converged Wide Area Synchronization are trademarks of Stratus Technologies Bermuda, Ltd. The registered trademark Linux is used pursuant to a sublicense from the Linux Mark Institute, the exclusive licensee of Linus Torvalds, owner of the mark on a world-wide basis. FLEXlm is a registered trademark of Macrovision Corporation. All other trademarks are the property of their respective owners. Manual Name: SINAP/IP User s Guide Part Number: R8071 Revision Number: 03 SINAP/IP Release Number: 1.2 Stratus ft Linux Release Number: 2.2 SINAP/SS7 Release Number: 14.2 Publication Date: May 2006 Stratus Technologies, Inc. 111 Powdermill Road Maynard, Massachusetts Stratus Technologies Bermuda, Ltd. All rights reserved.

3 Contents Preface xi 1. Overview 1-1 SS7-over-IP 1-1 Stream Control Transmission Protocol 1-1 SIGTRAN M3UA - SS7 MTP3-User Adaptation Layer 1-1 Product 1-3 Compliance 1-5 Interoperability 1-5 SINAP/IP Configuration Support Installation 2-1 Prerequisites 2-1 Installation 2-2 Stratus ft Linux Installation 2-2 Prerequisites for Installing SINAP/IP on ft Linux Systems 2-2 Installing M3UAGW RPM on ft Linux Systems 2-2 Installed Components on ft Linux Systems 2-3 Configuring M3UAGW on ft Linux Systems 2-4 M3UAGW Master Directory Structure 2-4 Automatically Restart m3uagw Quick-Start Guide 3-1 Create and Configure SINAP/SS7 Nodes - ITU 3-1 Create and Configure SINAP/SS7 Nodes - ANSI 3-2 Start m3uagw process - ITU/ANSI 3-2 Run Traffic Using tcsend/tcrecv - ITU 3-3 Run Traffic Using tcsend/tcrecv - ANSI 3-3 Contents iii

4 Contents 4. ASP Mode 4-1 IPAS Startup Files 4-1 ITU Software Configuration 4-2 Minimal IPAS Startup File Example for ITU 4-2 ITU MML 4-3 ANSI Software Configuration 4-5 Sample IPAS Startup File for ANSI 4-5 ANSI MML 4-6 Starting the IPAS 4-8 Traffic 4-8 Shutdown 4-10 Operation and Maintenance 4-10 M3UAGW Log Analysis 4-10 M3UAGW Trace Tool 4-12 Monitoring SCTP/M3UA Traffic Using Ethereal 4-13 IPAS On-Line Management 4-14 Essential On-Line Management Operations 4-14 M3UAGW ASP Commands 4-15 ASP Operating Modes 4-17 Two ASP OPC/DPC Failover Configuration 4-17 Two ASP Loadshare Configuration 4-20 Alarms, Events, and Error Messages 4-21 Troubleshooting IPSP Mode 5-1 IPAS IPSP Mode 5-1 ITU Software Configuration 5-2 Minimal IPSP Startup File Examples for ITU 5-2 ITU MML 5-5 ANSI Software Configuration 5-6 IPSP Startup File for ANSI 5-7 ANSI MML 5-7 Operation and Maintenance 5-8 Add a New IPSP Endpoint - Dynamic Registration 5-8 Delete an Existing IPSP Endpoint - Dynamic Registration 5-9 Add a New IPSP Endpoint - Static Registration 5-9 Delete an Existing IPSP Endpoint - Static Registration 5-10 Display Routing Key Information 5-10 M3UAGW IPSP Commands 5-11 Two IPSP Clients Loadshare Configuration - Client Side 5-13 Two IPSP Clients Loadshare Configuration - Server Side 5-14 iv SINAP/IP User s Guide

5 Contents Alarms, Events, and Error Messages 5-15 Troubleshooting Command Reference 6-1 M3UAGW Executable Commands 6-1 m3uagw 6-2 m3uagw_send_cm 6-4 m3uagw_license_update 6-6 m3uagw_trace 6-7 IPAS Commands 6-8 ADD_DPC_KEY 6-10 ADD_IP_CPC 6-12 ADD_IP_ROUTE 6-13 ADD_IP_ROUTE_TO_REMOTE_KEY 6-15 ADD_LOCAL_KEY 6-16 ADD_OPC_KEY 6-18 ADD_REMOTE_KEY 6-20 ALLOW_TRAFFIC_ON_ROUTE 6-22 BIND_UMI_TO_PRIMARY 6-23 CONNECT_ROUTE 6-24 DEBUG_LEVEL 6-25 DELETE_IP_CPC 6-26 DELETE_IP_ROUTE 6-27 DELETE_REMOTE_KEY 6-28 DISABLE_STATISTICS_FOR_NODE 6-29 DISABLE_STATISTICS_ON_ROUTES 6-30 DISPLAY_GATEWAY_VERSION 6-31 DISPLAY_IP_CPCS 6-32 DISPLAY_IP_ROUTE 6-33 DISPLAY_LOCAL_KEY = 6-34 DISPLAY_LOCAL_KEY 6-35 DISPLAY_LOCAL_KEYS 6-36 DISPLAY_REMOTE_KEY 6-37 DISPLAY_REMOTE_KEYS 6-38 DISPLAY_STATISTICS_FOR_NODE 6-39 DISPLAY_STATISTICS_FOR_ROUTE 6-40 DISPLAY_SCTP_PARAMETERS 6-41 DYNAMIC_REGISTRATION 6-42 ENABLE_M3UA_TRACE 6-43 ENABLE_SCTP_TRACE 6-44 ENABLE_STATISTICS_FOR_NODE 6-45 ENABLE_STATISTICS_ON_ROUTES 6-46 GATEWAY_MODE 6-47 INITIAL_TRAFFIC_STATE 6-48 Contents v

6 Contents IS_SERVER 6-49 LOCAL_SCTP_PORT 6-50 M3UA_AUDIT_TIMER 6-51 M3UA_CONGESTION_TIMER 6-52 M3UA_MAX_RETRANSMISSIONS 6-53 M3UA_RETRANSMISSION_TIME 6-54 M3UA_SG_TO_SGP_DISTRIBUTION_MODE 6-55 M3UA_SWITCHOVER_COUNT 6-56 OUTPUT_FILE 6-57 PRIMARY_LOCAL_HOST 6-58 PROHIBIT_TRAFFIC_ON_ROUTE 6-59 RECONNECT_TIMER 6-60 SCTP_ASSOC_MAX_RETRANS 6-61 SCTP_BUNDLING_TIME 6-62 SCTP_FRAGMENTATION_ALLOWED 6-63 SCTP_HEARTBEAT 6-64 SCTP_HIGH_CONG_LEVEL 6-65 SCTP_LOW_CONG_LEVEL 6-66 SCTP_MAX_ENDPOINTS 6-67 SCTP_MAX_RX_BUFFERS 6-68 SCTP_MAX_TX_BUFFERS 6-69 SCTP_NO_CONG_LEVEL 6-70 SCTP_PATH_MAX_RETRANS 6-71 SCTP_RTO_ALPHA 6-72 SCTP_RTO_BETA 6-73 SCTP_RTO_INIT 6-74 SCTP_RTO_MAX 6-75 SCTP_RTO_MIN 6-76 SECONDARY_LOCAL_HOST 6-77 SHUTDOWN 6-78 SINAP_APPLICATION_NAME 6-79 SINAP_QUEUE_SIZE 6-80 UMI_PORT Glossary 7-1 vi SINAP/IP User s Guide

7 Contents Appendix A. SINAP/IP Reliability A-1 Virtual Network Device (VND) A-1 SCTP Multi-Homing A-2 SCTP Multi-Home Failover Sample - IPAS Setup A-5 Operational Configurations A-5 Non-Multi-Homed IPAS A-5 Multi-Homed IPAS A-5 Multi-SGP Equipped IPAS A-6 Multi-Route Equipped IPASes A-7 Combining VND and SCTP A-9 Appendix B. Alarms B-1 Alarm Description Formats B-1 Alarm Descriptions and Actions B-1 Index Index-1 Contents vii

8 Figures Figures Figure 1-1. M3UA Architecture 1-2 Figure 1-2. SINAP/IP in the Network 1-5 Figure 4-1. SINAP/IP ASP Basic Configuration 4-1 Figure 4-2. Sample ITU ASP Configuration 4-2 Figure 4-3. IPAS ITU Startup Config File 4-2 Figure 4-4. IPAS Node ITU MML 4-4 Figure 4-5. SS7 SEP Node ITU MML 4-4 Figure 4-6. Sample ANSI ASP Configuration 4-5 Figure 4-7. IPAS ANSI Startup Config File 4-5 Figure 4-8. IPAS Node ANSI MML 4-6 Figure 4-9. SS7 SEP Node ANSI MML 4-7 Figure Sample m3uagw_trace Output 4-13 Figure OPC/DPC IPAS with Override 4-18 Figure Sample Startup Configuration File for IPAS-A 4-18 Figure Sample Startup Configuration File for IPAS-B 4-19 Figure Sample Startup Configuration File for IPAS-A: Loadsharing 4-20 Figure Sample Startup Configuration File for IPAS-B: Loadsharing 4-21 Figure 5-1. SINAP/IP IPSP Basic Configuration 5-1 Figure 5-2. Sample ITU IPSP Configuration 5-2 Figure 5-3. IPSP ITU Client Startup Configuration File - Dynamic Registration 5-2 Figure 5-4. IPSP ITU Server Startup Configuration File - Dynamic Registration 5-3 Figure 5-5. IPSP ITU Client Startup Configuration File - Static Figure 5-6. viii SINAP/IP User s Guide Registration 5-3 IPSP ITU Server Startup Configuration File - Static Registration 5-3 Figure 5-7. IPSP Client Node ITU MML 5-5 Figure 5-8. IPSP Server Node ITU MML 5-6 Figure 5-9. Sample ANSI IPSP Configuration 5-6 Figure IPSP Client Node ANSI MML 5-7 Figure IPSP Server Node ANSI MML 5-8 Figure Sample Loadshare Configuration Files - Client 5-14 Figure Sample Loadshare Configuration File - Server 5-15 Figure A-1. SCTP Multi-Home Failover A-3 Figure A-2. SCTP Multi-Home Failover Sample Configuration A-4 Figure A-3. One IP Route: Multi-Homed Example A-6

9 Figures Figure A-4. IPAS to Multiple SGPs in One SG Example A-7 Figure A-5. Multiple SGs and IPASes example A-8 Figure A-6. SCTP and VND Provide Reliable Transport A-9 Figures ix

10 Tables Tables Table 1-1. SINAP/IP Configuration Support 1-6 Table B-1. Alarm Formats B-1 x SINAP/IP User s Guide

11 Preface The SINAP/IP User s Guide (R8071) describes how to use the Stratus Internet Protocol Application Server (IPAS), which allows SINAP/SS7applications to communicate over IP to a signaling gateway or an IP-enabled signaling endpoint. This document is intended for SINAP/SS7 application developers and SS7-over-IP network administrators who want to use the Internet Protocol Application Server for their applications in their networks. Users should have a background in developing SINAP/SS7 applications or some familiarity with SS7-over-IP Networks. Revision Information This document is a revision. The major enhancement in SINAP/IP 1.2 is support for SINAP/SS Notation Conventions This document uses the following notation conventions. Warnings, Cautions, and Notes Warnings, cautions, and notes provide special information and have the following meanings:! WARNING A warning indicates a situation where failure to take or avoid a specified action could cause bodily harm or loss of life.! CAUTION A caution indicates a situation where failure to take or avoid a specified action could damage a hardware device, program, system, or data. Preface xi

12 NOTE A note provides important information about the operation of a Stratus system. Typographical Conventions This document uses the following typographical conventions: The italic font introduces or defines new terms. For example: The Terminal Handler accepts commands in Man-Machine Language (MML). The bold font emphasizes words in text. For example: You must create a link set before you provision its member links. The monospace font represents text that would appear on your display screen. The monospace bold font represents text you must type in examples that contain both user input and system output. The monospace italic font represents terms in command lines that are to be replaced by literal values. For example: If you type Display Commands at the prompt, the following output appears: 1. Display Link 2. Display Linkset 3. Display Routeset 4. Display Own Point Code 5. Display Concerned Point Code 6. Display Remote SSN 7. Display System Tables 8. Display Global Titles Enter the following command at the prompt: monitor SERVICE The percent sign (%) and the number sign (#) are standard default prompt signs that have a specific meaning at a command prompt. Although a prompt is sometimes shown at the beginning of a command line as it would appear on the screen, you do not type it. % indicates you are logged in to a user account and are subject to certain access limitations. # indicates you are logged in to the system administrator account and have superuser access. Users of this account are referred to as root. The # prompt sign used in an example indicates the command can only be issued by root. A slash (\) is used as a line-continuation character. Do not type it. xii SINAP/IP User s Guide

13 Syntax Notation This document uses the following format conventions for documenting commands: Square brackets ([ ]) enclose command argument choices that are optional. For example: cflow [-r] [-ix] [-i] [-d num] files The vertical bar ( ) separates mutually exclusive arguments from which you choose one. For example, the following shows two mutually exclusive, but optional, arguments: command [arg1 arg2] The following example shows two mutually exclusive arguments, one of which is required: command arg1 arg2 In either case, you may use either arg1 or arg2 when you type the command. An ellipsis (...) indicates that you can specify the preceding argument as many times as you need to on a single command line. For example: command [arg1 arg2 arg3...] NOTE Dots, brackets, and braces are not literal characters; you should not type them. Any list or set of arguments can contain more than two elements. Brackets and braces are sometimes nested. Getting Help Stratus provides complimentary access to StrataDOC, an online-documentation service that enables you to view, search, download, and print customer documentation. You can access StrataDOC at the following Web site: If you have a technical question, you can find the latest technical information at the Stratus Technical Support Web site: If you are unable to resolve your questions with the help available at this online site, you can contact the Stratus Customer Assistance Center (CAC) or your authorized Preface xiii

14 Stratus service representative. For information about how to contact the CAC, see the following Web site: xiv SINAP/IP User s Guide

15 Chapter 1 Overview1- This chapter provides an overview of SS7-over-IP signaling and the SINAP/IP product. SS7-over-IP The mandate of the IETF Signaling Transport (SIGTRAN) Working Group, a multi-vendor organization, is to develop and standardize protocols to transport SS7 over the Internet Protocol (IP). The main aim of this working group is to address the transport of packet-based mobile/public switched telephone network (PSTN) signaling over IP networks. Stream Control Transmission Protocol SIGTRAN has developed the Stream Control Transmission Protocol (SCTP - RFC2960), which is a reliable transport protocol that functions over IP, a potentially unreliable connectionless packet service. It provides acknowledged, non-duplicated, error-free transmission of MSUs (Message Signaling Units). The detection of duplicate data, data corruption, and loss of data is accomplished by the use of sequence numbers and checksums. For correction of lost or corrupted data, a selective retransmission mechanism is used. As opposed to TCP, SCTP supports congestion detection and multi-homing. SCTP uses the same architecture as MTP2 (Message Transfer Part 2) for providing function and measurements. SIGTRAN M3UA - SS7 MTP3-User Adaptation Layer M3UA stands for Message Transfer Part, Level 3, User Adaptation Layer. It is a protocol for transporting SS7 MTP3 User Part messages and MTP3 network management events on top of Streams Control Transmission Protocol (SCTP) to IP-based application processors. An Application Server Process (ASP) is the IP-based instantiation of an application process or database. A Signaling Gateway (SG) terminates an SS7 connection over MTP1-3 and transports SCCP, ISUP, and other MTP3 User messages over the M3UA/SCTP/IP protocols. An Internet Protocol Signalling Point (IPSP) communicates directly with other IPSPs over M3UA. In Figure 1-1 the legacy SS7 Signaling Endpoint on the far left uses MTP1-3 for sending SCCP and ISUP messages to the network. The Signaling Gateway (SG) does the translation of MTP3 messages into M3UA messages, and uses SCTP/IP to deliver them to the Application Server Process (ASP). At the ASP, M3UA handles the SCCP Overview 1-1

16 SS7-over-IP and ISUP messages. The bottom half of the figure shows how two Internet Protocol Signaling Points (IPSP) communicate with each other directly over M3UA/SCTP/IP. Figure 1-1. M3UA Architecture 1-2 SINAP/IP User s Guide

17 Product Product The SINAP/IP IPAS provides a means for SINAP/SS7 applications to communicate over IP to a Signalling Gateway (SG) without any changes to the applications and with no SS7 links. The Internet Engineering Task Force (IETF), Signaling Transport (SIGTRAN) working group has a number of Request For Comments (RFC) documents that specify protocols and adaptation layers that can be used to carry SS7 traffic over IP. SINAP/IP uses the MTP3 User Adaptation (M3UA; RFC3332) Layer and the Stream Control Transmission Protocol (SCTP2960; RFC3309) to carry the MTP3 user traffic. The exact versions of these documents can be found on the IETF Web site M3UA here replaces the MTP3 layer, while SCTP provides a Carrier Grade Protocol to replace MTP2. IP here replaces MTP1. This version of the Internet Protocol Application Server supports TCAP/SCCP traffic for the ITU and ANSI network variants only. The SINAP/IP IPAS is implemented inside a single program named m3uagw (M3UA Gateway, the package name is M3UAGW). A SINAP/IP IPAS takes SS7 messages from an application and uses M3UA to convert them to IP and vice versa. The installation and operation of m3uagw is described in this document. This release of the SINAP/IP IPAS is supported on Stratus ft Linux 2.2 and on SINAP/SS It is not possible to run the SINAP/IP IPAS without SINAP/SS7. M3UA (RFC3332) describes three major SS7-over-IP network entities: Application Server Process (ASP). This is an entity which can send and receive SS7 traffic over IP. The ASP represents a number of Application Servers (AS). Each AS is assigned a routing key that identifies the application. Some example routing keys are: the DPC alone, the DPC/OPC combination, or the DPC/OPC/SIO combination. SINAP/IP IPAS supports TCAP/SCCP traffic over M3UA. The routing keys used are DPC or OPC/DPC. DPC. The application is identified using the Destination Point Code. This is referred to as the Partial Key throughout this document. A Signaling Gateway (SG) does not look into data in the TCAP layer. This is fine when TCAP traffic originates from the SS7 side, because each PC is associated with one SS7 node. A problem occurs when multiple ASPs in the IP network load share one DPC: when one of the ASPs sends TC-BEGIN, the returning TC-END or TC-CONTINUE may not be routed back to the originating ASP. OPC/DPC. With OPC/DPC Routing Key, the SG further limits traffic distribution to the registered ASP based on the DPC and from a specific OPC. You can Overview 1-3

18 Product configure several ASPs that load share one DPC, with each ASP receiving traffic from a distinct OPC. In this case, since only one ASP is configured for each OPC/DPC routing key, the corresponding TC-END or TC-CONTINUE is guaranteed to be routed back to the originating ASP. With one ASP configured for each OPC/DPC routing key, the override traffic mode will be supported to allow ASP fail over. OPC/DPC routing keys are applicable to SINAP/IP IPAS ASP mode only. You must always configure the appropriate routing key for its associated SG. You can configure DPC key, OPC/DPC keys, or combination of both. Signaling Gateway (SG). An SG converses with the ASPs, converts M3UA messages to and from SS7 MSUs, and sends and receives MSUs over SS7 links. The SG can also route traffic from an ASP to another ASP; in this case no conversion is done. The SG may be implemented as a number of Signaling Gateway Processes (SGPs). Internet Protocol Signaling Point (IPSP). These endpoints communicate directly with one another over M3UA (IP): there are no intermediate SGs or SS7 links. The OPC/DPC routing key is not applicable to IPSP mode. Since IPSP use M3UA in a point-to-point fashion, there is no concept of routing of messages beyond the remote end. Therefore, traffic between the two peer IPSPs is directly based on their point code. SINAP/IP IPAS implements an ASP or an IPSP conforming to RFCs 3332, 2960, 3309 and the M3UA Implementors Guide, subject to the limitations described below. This version of the Internet Protocol Application Server supports TCAP/SCCP traffic for the ITU and ANSI network variants only. NOTE The M3UA Implementor s Guide is available at In order to understand all the applicable commands in Chapter 6, Command Reference, and the operating procedures for the SINAP/IP IPAS, you must be familiar with the terms described in RFC3332 and be knowledgeable about basic entity relationships (for example, multiple SGPs in an SG) and the meaning of multi-homing (see RFC2960). You also need to have a fundamental understanding of SINAP/SS7 operation, because the SINAP/IP IPAS is layered on top of SINAP; the SINAP/SS7application can only be used with SINAP/SS7 running. 1-4 SINAP/IP User s Guide

19 Compliance In Figure 1-2 the circled area shows the possible uses for the SINAP/IP product. Figure 1-2. SINAP/IP in the Network Service Management System(SMS) Intelligent Peripheral (IP) Signaling End Points (e.g. SCP, HLR) TDMSignaling Network Internet Offload Edge Signaling Gateway (Edge-SG) Core Signaling Gateway (Core-SG) Application/ Feature Server (AS/FS) Packet Network SIP Server (Proxy, Re-direct, Registrar) Presence Server Mobile Data Network Elements (e.g., GGSN, SGSN) Mobile Switching Center (MSC) TDMCircuit Switched Network Service Switching Point (SSP) Media Gateway Controller (MGC) Softswitch Media Gateway (MG) Signaling Bearer Media Server (MS) SIP User Agent (Client/ Server) Compliance The SINAP/IP IPAS implements an ASP or an IPSP conforming to RFCs 3332, 2960, 3309 and the M3UA Implementor s Guide Interoperability SINAP/IP IPAS has been tested to interoperate correctly with a Cisco ITP server. Overview 1-5

20 SINAP/IP Configuration Support SINAP/IP Configuration Support Table 1-1 lists the maximum configurations supported by the SINAP/IP IPAS. Table 1-1. SINAP/IP Configuration Support Maximum number of IPASs with the same point code 16 Maximum number of SSNs per IPAS 254 Maximum number of remote OPC per IPAS 128 Maximum number of SGP per IPAS 16 Maximum number of IP addresses per SCTP endpoint Maximum number of SCTP associations to a single endpoint Maximum number of SCTP associations per stack 2, a primary and a secondary for multi-homing 1 may be multi-homed 200 on each of four stacks (each stack 1-2 IP interfaces) 1-6 SINAP/IP User s Guide

21 Chapter 2 Installation2- Prerequisites This section describes the prerequisites for using SINAP/IP: 1. SINAP/SS must be installed and configured (see the SINAP/SS7 Installation Guide (R8060)). 2. A valid SINAP/SS7 license is required (see the SINAP/SS7 Installation Guide (R8060)). 3. A valid SINAP/IP license (with the SINAP/SS7 license) is required. 4. In order to run SINAP/IP, one Stratus ftserver T Series system running the Stratus ft Linux operating system is required. One system for each IPAS is sufficient. 5. At least one IP network, 10-Base T or better, is required. 6. To carry carrier grade traffic, the IP network(s) must be a private one (i.e., no FTP/Telnet sessions running, dedicated to SS7 over IP). For pre-production or demonstration purposes, the IP network may be public. 7. The IP networks must be set up (by a system or network administrator). NOTE The installation and operation of the IP network(s) is outside the scope of this document. 8. At least one Ethernet (or equivalent) card must be present. For multi-homing two separate Ethernet (or equivalent) cards are recommended. 9. If running traffic in ASP mode, a third-party signalling gateway (SG) is required. 10. A knowledge about the configuration of the SGs to be connected to, that is, the number of Signaling Gateway Processes (SGPs) within the target SG and the internal distribution mode (i.e., loadshare, override, or broadcast) is necessary. 11. A knowledge about the M3UA version implemented at the SGs is necessary. If versions other than RFC3332/RFC2960 and the M3UA Implementors guide are supported, then inter-operation is not guaranteed. Installation 2-1

22 Installation Installation This chapter describes the installation of m3uagw on Stratus ft Linux systems. Note that the procedure for installation is similar to that of SINAP/SS7 (see the SINAP/SS7 Installation Guide (R8060)), although no reboot is required (since the package/depot does not contain a kernel file set) and SS7 links are not mandatory. However, the package/depot names contain the name M3UAGW as opposed to the name SINAP. For instructions on setting up CD-ROM drives and other system components, see the Stratus ftserver T 30 Systems: Installation Guide (R002L). Log in as root (superuser) to perform the SINAP/IP installation tasks. Stratus ft Linux Installation The following describes the steps needed for installing SINAP/IP IPAS on an ft Linux system. Prerequisites for Installing SINAP/IP on ft Linux Systems Installing M3UAGW RPM on ft Linux Systems Installed Components on ft Linux Systems Configuring M3UAGW on ft Linux Systems Prerequisites for Installing SINAP/IP on ft Linux Systems Stratus ft Linux 2.2 installed SINAP/SS installed A valid license for SINAP/SS7 A valid license for SINAP/IP M3UAGW 1.0 software rpm IP network ports 5 MB of disk space 20 MB of physical memory Installing M3UAGW RPM on ft Linux Systems 1. Login as root. 2. Check and remove existing installation if present. 3. Copy m3uagw rpm to local directory. 2-2 SINAP/IP User s Guide

23 Stratus ft Linux Installation 4. Invoke rpm -vi rpm Name to install. 5. Verify installation by invoking rpm -qi m3uagw. rpm -qi m3uagw package m3uagw is not installed rpm -vi m3uagw _15be-1.i386.rpm Preparing packages for installation... Starting Preinstall Script... Preinstall script complete m3uagw _15be Postinstall script complete rpm -qi m3uagw Name : m3uagw Relocations: (not relocateable) Version : _15BE Vendor: Stratus Technologies, Inc. Release : 1 Build Date: Tue 11 May :50:14 PM EDT Install Date: Wed 12 May :56:08 PM EDT Build Host: ftlinux2.hw.stratus.com Group : Applications/Communications Source RPM: m3uagw _15be src.rpm Size : License: 2003 Stratus Technologies Bermuda, Ltd. All rights reserved. Signature : (none) Summary : Stratus Technologies M3UA Gateway Product Description : Stratus Technologies M3UA Gateway Product This m3uagw version was built with the following layered product versions: SINAP/SS7 version: _16BE TME-SIGTRAN version: _08BE Installed Components on ft Linux Systems Configuration script - /etc/config_m3uagw M3UAGW master directory - /home/m3uagw_master in ft Linux Executables in /home/m3uagw_master/bin directory m3uagw. The m3ua gateway (IPAS) m3uagw_trace. The gateway tracing tools m3uagw_license_update. The license update program m3uagw_send_cm. The user management client; sends commands to the gateway Installation 2-3

24 M3UAGW Master Directory Structure Samples in /home/m3uagw_master/m3uagw_samples directory README file with release information in /home/m3uagw_master directory Configuring M3UAGW on ft Linux Systems 1. Login as root 2. Invoke /etc/config_m3uagw 3. Run this script to link the m3uagw executables for each SINAP/SS7 node 4. Creates symbolic link to the master copy in /home/m3uagw_master and copies samples to the m3uagw_samples directory The following display (example only) displays, and the prompts (here just a return to select the default) are responded to by the user: [root]# /etc/config_m3uagw Please enter location of m3uagw master directory (default:/home/m3uagw_master) <ENTER> Please enter the SINAP group name (default:sinap) <ENTER> Enter the root directory of the target SINAP node (default:/home/sinap0) CTRL-C to terminate <ENTER> Making links to m3uagw_master in /home/sinap0/bin Creating /home/sinap0/m3uagw_samples directory and samples files Completed configuration for /home/sinap0 Enter the root directory of the target SINAP node (default:/home/sinap0) CTRL-C to terminate /home/sinap1 Making links to m3uagw_master in /home/sinap1/bin Creating /home/sinap1/m3uagw_samples directory and samples files Completed configuration for /home/sinap1 Enter the root directory of the target SINAP node (default:/home/sinap0) CTRL-C to terminate ^C M3UAGW Master Directory Structure The installation process automatically creates the default master copy of the M3UAGW software in the /home/m3uagw_master directory. When you configure M3UAGW through the /etc/config_m3uagw script the executables m3uagw and m3uagw_trace are symbolically linked to (default):/home/m3uagw_master. 2-4 SINAP/IP User s Guide

25 Automatically Restart m3uagw NOTE The accounts the executables are executed from must be in the SINAP/SS7 group. Although /home/sinap_master is assumed by default for the Stratus ft Linux operating system you can specify a different location, for example /usr/home during the installation. The contents of the directory will be (default): /[opt home] /m3uagw_master README /Bin m3uagw m3uagw_trace m3uagw_license_update /m3uagw_samples m3uagw_send_cm Automatically Restart m3uagw The sinap_utlmon utility can be used to monitor and automatically restart m3uagw. Refer to the SINAP/SS7 User s Guide (R8051) for details on sinap_utlmon and how to configure SINAP/SS7 to be restarted upon system reboot. To enable m3uagw to be monitored and restarted by sinap_utlmon: 1. Login as SINAP/SS7 user, e.g. su - sinap0 2. Remove symbolic link for ~/Bin/startappl, e.g. rm ~/Bin/startappl. 3. Copy the startappl from its master copy (should use identical permission), e.g. cp /home/sinap_master/bin/startappl ~/Bin/startappl chmod 777 ~/Bin/startappl 4. Edit ~/Bin/startappl to add sinap_utlmon, m3uagw, and the m3uagw startup configuration file. Use a line similar to the following before the final exit : /home/sinap0/bin/sinap_utlmon /home/sinap0/bin/m3uagw /home/sinap0/asp.cfg Installation 2-5

26 Automatically Restart m3uagw NOTE Full paths to sinap_utlmon, m3uagw and its startup configuration file argument are required. Use the OUTPUT_FILE command to direct m3uagw's console output to a file because the console is not applicable when m3uagw is being restarted. The following is a sample command: OUTPUT_FILE = /home/sinap0/asp.out 5. Test that m3uagw will be started adn restarted by sinap_utlmon. Start or restart SINAP/SS7. Monitor that m3uagw is started correctly by SINAP/SS7 using the SINAP/SS7 command ver and examining the m3uagw log file. 6. Shut down m3uagw, for example, eneter the following command: m3uagw_send_cm -s "SHUTDOWN" Monitor that m3uagw is started correctly by SINAP/SS7 using the SINAP/SS7 ver command and examining the m3uagw log file. 2-6 SINAP/IP User s Guide

27 Chapter 3 Quick-Start Guide3- The quick verification consists of MML (Man-Machine Language) and m3uagw startup configuration files for two IPSP nodes in dynamic registration mode, so you can use two SINAP/SS7 nodes to verify the basic integrity and functionality of the M3UAGW package. The sample files were installed in the $M3UAGW_MASTER/Samples directory and were copied by /etc/config_m3uagw to each node's m3uagw_samples directory. A README file in that directory describes how to set up and run the samples. To perform the M3UAGW sample setup and running procedures, see the relevant following sections: Create and Configure SINAP/SS7 Nodes - ITU Create and Configure SINAP/SS7 Nodes - ANSI Start m3uagw process - ITU/ANSI Run Traffic Using tcsend/tcrecv - ITU Run Traffic Using tcsend/tcrecv - ANSI Create and Configure SINAP/SS7 Nodes - ITU 1. Create two fresh SINAP/SS7 ITU(CCITT) nodes using /etc/config_sinap. One will be used as the IPSP server, the other as the IPSP client. NOTE If a Multi-Stack license is purchased and the system has two Ethernet interfaces available and configured, these two nodes can reside on the same system. Otherwise, two systems are required to run the sample. 2. Make sure that the /etc/ss7links file is empty. 3. Start SINAP/SS7 on both nodes with start_sinap. 4. Run /etc/config_m3uagw for each created node. 5. Log in to the server node and change directory to m3uagw_samples. Quick-Start Guide 3-1

28 Create and Configure SINAP/SS7 Nodes - ANSI 6. Feed the MML to the node by invoking send_cm server-itu.mml. 7. Log in to the client node and change directory to m3uagw_samples. 8. Feed the MML to the node by invoking send_cm client-itu.mml. 9. Verify that no error is reported. Create and Configure SINAP/SS7 Nodes - ANSI 1. Create two fresh SINAP/SS7 ANSI nodes using /etc/config_sinap. One will be used as the IPSP server, the other as the IPSP client. NOTE If a Multi-Stack license is purchased and the system has two Ethernet interfaces available and configured, these two nodes can reside on the same system. Otherwise, two systems are required to run the sample. 2. Make sure that the /etc/ss7links file is empty. 3. Start SINAP/SS7 on both nodes with start_sinap. 4. Run /etc/config_m3uagw for each created node. 5. Log in to the server node and change directory to m3uagw_samples. 6. Feed the MML to the node by invoking send_cm server-ansi.mml. 7. Log in to the client node and change directory to m3uagw_samples. 8. Feed the MML to the node by invoking send_cm client-ansi.mml. 9. Verify that no error is reported. Start m3uagw process - ITU/ANSI 1. Log in to the server node and change directory to m3uagw_samples. 2. Update the SERVER_IP and CLIENT_IP fields in server.cfg to real IP addresses on the system. 3. Start the m3uagw process by invoking m3uagw server.cfg. 4. Log in to the client node and change directory to m3uagw_samples. 5. Update the SERVER_IP and CLIENT_IP fields in client.cfg to real IP addresses on the system. These have to match the server side. 6. Start m3uagw process by invoking m3uagw client.cfg. 7. Verify that the client connects to the server and that no error is reported. 8. Keep both server and client m3uagw windows up to monitor the status. 3-2 SINAP/IP User s Guide

29 Run Traffic Using tcsend/tcrecv - ITU 9. For expected outputs, refer to the sample M3UAGW log file in Chapter 4, ASP Mode. Run Traffic Using tcsend/tcrecv - ITU 1. Log in to the client node and change directory to the samples/ccitt directory. 2. Start tcrecv by invoking tcrecv -l 2 -r 2 -c. 3. In another window, log in to the server node and change directory to the samples/ccitt directory. 4. Start tcsend by invoking tcsend -p l 2 -r 2 -w 10 -q The traffic should start running and no LOCAL_CANCEL messages should appear. Run Traffic Using tcsend/tcrecv - ANSI 1. Log in to the client node and change directory to the samples/ansi directory. 2. Start tcrecv by invoking tcrecv In another window, log in to the server node and change directory to the samples/ansi directory. 4. Start tcsend by invoking tcsend The traffic should start running and no LOCAL_CANCEL messages should appear. Quick-Start Guide 3-3

30 Run Traffic Using tcsend/tcrecv - ANSI 3-4 SINAP/IP User s Guide

31 Chapter 4 ASP Mode4- Figure 4-1 shows the basic configuration for SINAP/IP IPAS connected through a gateway to SINAP/SS7. IPAS ASP should be able to talk to any standard conforming SG. The gateway is used as an example to illustrate the ASP operation. Figure 4-1. SINAP/IP ASP Basic Configuration ftserver ftserver SINAP IPAS IP SS7 To IP Gateway SS7 SINAP SS7 ASP SGP SS7 SEP IPAS Startup Files The IPAS receives its startup configuration from a flat file whose name is specified in the first and only command line argument. The syntax is as follows: m3uagw [file_name ] In this syntax, m3uagw is the name of the M3UA Gateway program that implements the IPAS. If file_name is omitted, the file name is preset to m3uagw_startup; and if this file does not exist, a fatal error is returned. ASP Mode 4-1

32 ITU Software Configuration ITU Software Configuration Figure 4-2 shows a sample minimal configuration for an ITU (CCITT) ASP. Figure 4-2. Sample ITU ASP Configuration tcrecv SSN=2 IPAS SINAP Driver SS7 To IP Gateway tcsend SSN=2 SINAP Driver PC=2665 IP Traffic PC=2667 SS7 Traffic PC=2669 Minimal IPAS Startup File Example for ITU The following startup file is a typical startup file that is used solely for demonstration purposes. A complete description of each command is provided in Chapter 6, Command Reference. Figure 4-3. IPAS ITU Startup Config File GATEWAY_MODE = IPAS PRIMARY_LOCAL_HOST = LOCAL_SCTP_PORT = 2905 M3UA_SG_TO_SGP_DISTRIBUTION_MODE = 1 LOADSHARE ADD_IP_ROUTE = route1 ADD_IP_CPC = ADD_DPC_KEY = LOADSHARE DEBUG_LEVEL = 1 GATEWAY_MODE = IPAS indicates the operation mode of the gateway (IPAS/IPMT). IPAS is the mode currently supported. IPSP also uses IPAS mode. Future releases may include an IPMT (IPAS and IPMT are SINAP/IP terms, not RFC3332). PRIMARY_LOCAL_HOST refers to the local IP address used to connect to the SGP. LOCAL_SCTP_PORT refers to the local SCTP port that will be used to send to and receive on the SGP. 4-2 SINAP/IP User s Guide

33 ITU Software Configuration M3UA_SG_TO_SGP_DISTRIBUTION_MODE declares an SG, assigns an SG ID, and specifies the traffic distribution mode in this SG. ADD_IP_ROUTE = route1 identifies the destination that we will be talking to. The first parameter is the SG. Id., mandatory to enter (this line declares an SGP connection, and the SGP is part of the SG we declared above with SG ID 1 ). The second parameter is the destination system (in hostname or canonical IP address format). The third parameter is the SCTP port of the destination, and the last parameter is a symbolic name for the IP route. NOTE The symbolic name could be used to tag the point code of an adjacent SG, but if so, it must be alphanumeric (for example PC2000). Each ADD_IP_ROUTE line is equivalent to a set of one or more physical paths between m3uagw (ASP) and an SGP. ITU MML ADD_IP_CPC = Specifies the SG ID and one or more concerned point codes (CPCs) reachable through this SG. It is mandatory to have at least one CPC entered that is reachable over IP. The CPCs are the point codes of the ultimate destinations that traffic will reach. Also SINAP/SS7 must be set up correctly so that its MML includes the CPCs identified here. ADD_DPC_KEY = LOADSHARE Specifies the routing context value of the local routing key. This configuration uses DPC key. LOADSHARE is the traffic mode. The second parameter is the routing context value of the routing key. The third parameter is the SG ID. The configuration on the remote SG should match this DPC key configuration. DEBUG_LEVEL = 1. Refers to the level of diagnostic tracing and error reporting that will appear. Debug level 1 is the level preferred by development. Note that it is customary to set DEBUG_LEVEL = 1 here to give some extra view of activity in Demonstration mode. As in SINAP/SS7, MML must be set up correctly at the SINAP/SS7 node where the IPAS is to be run. See the SINAP/SS7 User s Guide (R8051) for information on MML commands. This example is for ITU, International Network (INAT00). It is necessary to configure and activate fake routesets, linksets, and a link (create only). There can be installed active SS7 links at the node where the IPAS runs, but the fake link for IPAS must be on a port that does not exist in the SS7links file for that node. ASP Mode 4-3

34 ITU Software Configuration The remote SSNs and CPCs must be identified correctly. The following shows an example SINAP/SS7 ITU MML for the IPAS node. Note the dummy PORTNUM=0 used to create the fake link for IPAS traffic. Figure 4-4. IPAS Node ITU MML CREATE-OSP:NETWORK=INAT00,SPC=2665; CREATE-LSET:LINKSET=LSET1,ADPC=2669,LOADLINK=1,ACTLINK=1; CREATE-LINK:LINK=LNK0,PORTNUM=0,LINKSET=LSET1,SLC=0,PRIORITY=0, \ SPEED=64K; CREATE-RSET:ROUTESET=RSET1,DPC=2669,ROUTES=LSET1,LOADSHR=ENABLE; CREATE-CPC:LSSN=2,RPC=2669; CREATE-REMSSN:PC=2669,SSN=2; CONFIGURE-LSET:LINKSET=LSET1,STATE=ACTIVE; CONFIGURE-RSET:ROUTESET=RSET1,STATE=ACTIVE; The following shows an example SINAP/SS7 ITU MML for the SS7 SEP (Signaling End Point) node. Note that 2665 is the real concerned point code here, 2667 is the point code of the SG. Figure 4-5. SS7 SEP Node ITU MML CREATE-OSP:NETWORK=INAT00,SPC=2669; CREATE-LSET:LINKSET=LSET1,ADPC=2667,LOADLINK=1,ACTLINK=1; CREATE-LINK:LINK=LNK0,PORTNUM=0,LINKSET=LSET1,SLC=0,PRIORITY=0,SPEED=0; CREATE-RSET:ROUTESET=RSET1,DPC=2667,ROUTES=LSET1,LOADSHR=ENABLE; CREATE-RSET:ROUTESET=RSET2,DPC=2665,ROUTES=LSET1,LOADSHR=ENABLE; CREATE-CPC:LSSN=2,RPC=2665; CREATE-REMSSN:PC=2665,SSN=2; CONFIGURE-LSET:LINKSET=LSET1,STATE=ACTIVE; CONFIGURE-RSET:ROUTESET=RSET1,STATE=ACTIVE; CONFIGURE-RSET:ROUTESET=RSET2,STATE=ACTIVE; 4-4 SINAP/IP User s Guide

35 ANSI Software Configuration ANSI Software Configuration Figure 4-6 Show a sample configuration for an ANSI ASP. Figure 4-6. Sample ANSI ASP Configuration tcrecv SSN=2 PC=2-2-2 IPAS SINAP Driver IP Traffic SS7 To IP Gateway PC=3-3-3 SS7 Traffic PC=4-4-4 tcsend SSN=2 SINAP Driver Sample IPAS Startup File for ANSI The following is a typical startup file that is solely for demonstration purposes. A complete description of each command is provided in Chapter 6, Command Reference. Figure 4-7. IPAS ANSI Startup Config File GATEWAY_MODE = IPAS PRIMARY_LOCAL_HOST = LOCAL_SCTP_PORT = 2905 M3UA_SG_TO_SGP_DISTRIBUTION_MODE = 1 LOADSHARE ADD_IP_ROUTE = route1 ADD_IP_CPC = ADD_DPC_KEY = LOADSHARE DEBUG_LEVEL = 1 The following describes the entry that differs from the ITU example above. ADD_IP_CPC = Identifies the SG ID and one or more concerned point codes (CPCs) reachable via this SG. This is the only difference from the ITU example above. It is mandatory to have at least one CPC entered that is reachable over IP. A CPCs is the point code of the ultimate destination that traffic will reach. Also SINAP/SS7 must be set up correctly so that its MML includes the CPCs identified here. ASP Mode 4-5

36 ANSI Software Configuration ANSI MML As in SINAP/SS7, MML must be set up correctly at the SINAP/SS7 node where the IPAS is to be run. See the SINAP/SS7 User s Guide (R8051) for information on MML Commands. The following example MML file is for ANSI and the National Network (NAT10). It is necessary to configure and activate fake routesets, linksets, and a link (create only). There can be installed active SS7 links at the node where the IPAS runs, but the fake link for IPAS must be on a port that does not exist in the SS7links file for that node. The remote SSNs and CPCs must be identified correctly. Figure 4-8 shows the example SINAP/SS7 ANSI MML for the IPAS node. Note the dummy PORTNUM=0 used to create the fake link for IPAS traffic. Figure 4-8. IPAS Node ANSI MML CREATE-OSP:NETWORK=NAT10,SPC=2-2-2; CREATE-LSET:LINKSET=LSET1,ADPC=4-4-4,TYPE=F,LOADLINK=1,ACTLINK=1; CREATE-LINK:LINK=LNK1,PORTNUM=0,LINKSET=LSET1,SLC=0,PRIORITY=0,SPEED=0; CREATE-RSET:ROUTESET=RSET1,DPC=4-4-4,ROUTES=LSET1; CREATE-CPC:LSSN=2,RPC=4-4-4; CREATE-REMSSN:PC=4-4-4,SSN=2; CONFIGURE-LSET:LINKSET=LSET1,STATE=ACTIVE; CONFIGURE-RSET:ROUTESET=RSET1,STATE=ACTIVE; 4-6 SINAP/IP User s Guide

37 ANSI Software Configuration Figure 4-9 shows the example SINAP/SS7 ANSI MML for the SS7 SEP node. Figure 4-9. SS7 SEP Node ANSI MML CREATE-OSP:NETWORK=NAT10,SPC=4-4-4; CREATE-LSET:LINKSET=LSET1,ADPC=3-3-3,TYPE=A,LOADLINK=1,ACTLINK=1; CREATE-LSET:LINKSET=LSET9,ADPC=9-9-9,TYPE=A,LOADLINK=1,ACTLINK=1; CREATE-LINK:LINK=LNK0,PORTNUM=0,LINKSET=LSET1,SLC=0,PRIORITY=0,SPEED=0; CREATE-LINK:LINK=LNK9,PORTNUM=9,LINKSET=LSET9,SLC=0,PRIORITY=0,SPEED=0; CREATE-CLSET:CLSET=CSET1,LSET1=LSET1,LSET2=LSET9; CREATE-RSET:ROUTESET=RSET1,DPC=3-3-3,ROUTES=CSET1; CREATE-RSET:ROUTESET=RSET2,DPC=2-2-2,ROUTES=CSET1; CREATE-CPC:LSSN=2,RPC=2-2-2; CREATE-REMSSN:PC=2-2-2,SSN=2; CONFIGURE-LSET:LINKSET=LSET1,STATE=ACTIVE; CONFIGURE-RSET:ROUTESET=RSET1,STATE=ACTIVE; CONFIGURE-RSET:ROUTESET=RSET2,STATE=ACTIVE; NOTE Since many ANSI network devices default to 56K link speed, sometimes it is necessary to explicitly specify SPEED=56K for ANSI SS7 links if 56K is the speed used by the SG. The link LNK9, linkset LSET9 and its ADPC and the port number 9 used by LNK9 are all dummies. These are needed because a combined linkset in ANSI requires at least 2 linksets in it. In CSET1, only LSET1 will be activated and used to route traffic. ASP Mode 4-7

38 Starting the IPAS Starting the IPAS Traffic Use the following procedure to start the IPAS: 1. Load the MML according to your preferred method and execute one of the following commands at the node/system where the IPAS is to be run to start SINAP: start_sinap -t start_sinap -tv NOTE Run each IPAS in its own separate window identical to where SINAP/SS7 is started in order to potentially see any SSA and SSP messages arriving at their destination. 2. In the home directory of the IPAS SINAP/SS7 node, enter m3uagw file_name file_name is the name of your IPAS startup file, for example m3uagw_client.cfg. Messages appear as listed in Example 4-1. Note the display of local IP Addresses and ports, the congestion option specified for SINAP, the network indicator (here NI = 0b'0', INAT00), and the CPC that the IPAS is interested in. Use the following procedure to generate and view traffic information. 1. Open another window at the SINAP/SS7 SEP and change directory to the samples/ccitt directory. Do the same for the IPAS. 2. At the IPAS node, enter a command in the following format: tcrecv -ln -rn In this command, the -l argument (the lower-case letter L) specifies the local sub-system number (SSN) for tcrecv and the -r argument specifies the remote SSN. 4-8 SINAP/IP User s Guide

39 Traffic At the SS7 SEP you might see messages similar to the following: SSA RECEIVED FOR SSN 2 AT PC 2665 SSN 2 AT PC 2665 SSN FOUND SSN 2 AT PC 2665 SET ALLOWED Note these messages are generated by SCMG (SCCP Management), signify that the remote end is receiving the SSA over SS7 over IP, and indicate that there are no SS7 links present here. 3. At the SS7 SEP samples/ccitt directory, enter a command in the following format: tcsend -l2 -r2 -p2665 -w20 The -l and -r options refer to the local and remote SSNs respectively. The -p option refers to the point code where the remote SSN is resident. The -w option here instructs tcsend to send 20 MSUs before waiting for replies. When traffic starts to flow, expect to see messages similar to the following: TCAP SEND: TCAP Messages=14200 TBlocks->tx=42600 rx=42600 local cancel=0 TCAP SEND: TCAP Messages=14300 TBlocks->tx=42900 rx=42900 local cancel=0 TCAP SEND: TCAP Messages=14400 TBlocks->tx=43200 rx=43200 local cancel=0 TCAP SEND: TCAP Messages=14500 TBlocks->tx=43500 rx=43500 local cancel=0 TCAP SEND: TCAP Messages=14600 TBlocks->tx=43800 rx=43800 local cancel=0 TCAP SEND: TCAP Messages=14700 TBlocks->tx=44100 rx=44100 local cancel=0 These messages indicate that you have successfully sent TCAP traffic over IP using the SS7 over IP standards M3UA and SCTP. NOTE When re-entering this procedure, that is after stopping either tcsend or tcrecv and restarting them later, note that correct operation will not appear until after SSTs have been responded to by an SSA (same as SINAP). Wait until the SSA about the remote appears at the tcsend window before starting it or until sy #SC,cpc/ssn indicates an allowed remote subsystem. Otherwise, a TC-NOTICE may appear. ASP Mode 4-9

40 Shutdown Shutdown At the IPAS type a Ctrl+C. A graceful shutdown sequence will be executed and the process terminated. Operation and Maintenance The following is a list of IPAS software diagnostics: M3UAGW log analysis M3UAGW trace SINAP/SS7 sy commands Ethereal M3UAGW Log Analysis The following are IPAS commands for M3UAGW log analysis: Set log output file: Use OUTPUT_FILE = file name If not specified, defaults to stdout Set debug level 1-6 Use DEBUG_LEVEL = level Enable M3UA stack trace: Use ENABLE_M3UA_TRACE Enable SCTP stack trace: Use ENABLE_SCTP_TRACE Example 4-1. Sample M3UAGW Log File GATEWAY_MODE: IPAS PRIMARY_LOCAL_HOST LOCAL_SCTP_PORT 2905 M3UA_SG_TO_SGP_DISTRIBUTION_MODE 1 LOADSHARE USING M3UA ASP PROTOCOL ADD_IP_ROUTE[0]: SG Id.:1 ADDRESS: TXPORT:2905 route1 ADD_IP_CPC DEBUG_LEVEL: 1 IPAS license checked out... Local Address 0 is: SINAP/IP User s Guide

41 Operation and Maintenance Local SCTP Port is:2905 Cong opt. is International NI:0 Setting M3UA/SCTP error level to major M3UAGW Version: Rel _15BE 05/11/04 SINAP/SS7 Version: _16BE TME-SIGTRAN Version: _08BE M3UA Protocol Version: 1 Adding Local AS:0 nw_appr:-1 Traffic mode is:2 RC is:2000 Adding SG: 1 with SG Mode: 2 Adding CPC:2669 to SG:1 in M3UA Remote Address: , SCTP Port:2905, No addr:1 Connecting to remote ASP:0 for ASP:1 Connection setup Entering main loop. Route: 0 is connected Sending aspup for asp_id:1 dest_id:0 Received ASP callback for asp_id:1 dest_id:0, state:4 Received ASP callback for asp_id:1 dest_id:0, state:1 ASP Inactive for AS:65535 Static reg. Adding rkey for: Adding association:0 Sending aspac for asp_id:1, dest_id:0 AS:0 AS state:1 for Dest:0 AS:0 inactive at Dest:0 Received ASP callback for asp_id:1 dest_id:0, state:5 Act Sent Sent MTP Resume for:2669 rst:0 Received ASP callback for asp_id:1 dest_id:0, state:2 ASP Active for AS:0 A route to the destination:1 is reachable. Busy flag reset for route:0 Received ASP callback for asp_id:1 dest_id:0, state:2 ASP Active for AS:65535 Busy flag reset for route:0 AS:0 AS state:2 for Dest:0 AS:0 active at Dest:0 Static reg. Adding rkey for: Busy flag reset for route:0 IP IN. SST for 2 SS7 IN. SSN:2 set allowed IP IN. SSA for 2 ASP Mode 4-11

42 Operation and Maintenance <<< The DATA traffic can flow at this point >>> <<< Stop the application and shutdown m3uagw >>> IP IN. SSP for 2 SIGINT Handler invoked. Entering graceful shutdown Sent MTP Pause for:2669 rst:0 Key:0 marked:1 Requesting Deferred AS:0 deactivated Sending aspia for asp_id:1 dest_id:0 Deleting association:0 Delete rkey PC:2663 SSN:0 Sent MTP Pause for:2669 rst:0 Received ASP callback for asp_id:1 dest_id:0, state:6 Inact Sent Received ASP callback for asp_id:1 dest_id:0, state:1 ASP Inactive for AS:65535 Sending ASP Down to:0 Busy flag reset for route:0 Received ASP callback for asp_id:1 dest_id:0, state:3 Received ASP callback for asp_id:1 dest_id:0, state:0 ASP Down for AS:65535 AS:0 AS state:3 for Dest:0 Route: 0 is disconnected Deleting SGP:0 Deleting SG:1 Deleting all CPC from SG:1 Deleting CPC: 2669 Route state reset for route:0 Terminating this process. M3UAGW Trace Tool 1. Log in as the SINAP/SS7 user at the SINAP/SS7 node running IPAS. 2. At the command line, type m3uagw_trace SINAP/IP User s Guide