Tekelec EAGLE 5 User Manual

Integrated signaling system
Hide thumbs Also See for EAGLE 5:
Table of Contents

Advertisement

Tekelec EAGLE® 5
Integrated Signaling System
SIGTRAN User Guide
910-5346-001 Revision A
September 2008

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the EAGLE 5 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Tekelec EAGLE 5

  • Page 1 Tekelec EAGLE® 5 Integrated Signaling System SIGTRAN User Guide 910-5346-001 Revision A September 2008...
  • Page 2 Information in this documentation is subject to change without notice. Unauthorized use, copying, or translation of this documentation can result in civil or criminal penalties. Any export of Tekelec products is subject to the export controls of the United States and the other countries where Tekelec has operations.
  • Page 3: Table Of Contents

    When to transition to an SS7-over-IP SIGTRAN network ............2-11 Chapter 3. Tekelec solutions ..................... 3-1 Overview ............................ 3-1 EAGLE 5 ISS ..........................3-1 IPLIMx, IPGWx and IPSG applications ................3-2 Tekelec Integrated Application Solutions (IAS) ................ 3-3 910-5346-001 Revision A, September 2008...
  • Page 4 Configure Congestion Window Minimum (CWMIN) parameter ........5-23 Chapter 6. Implementation ....................6-1 Hardware requirements ....................... 6-1 EAGLE 5 ISS ........................6-1 Integrated Message Feeder (IMF) ..................6-2 Converting non-IPSG-M2PA Linksets to IPSG-M3UA Linksets ..........6-2 Converting IPGWx M3UA Application Servers to IPSG-M3UA Linksets ....... 6-3 IPGWx to IPSG-M3UA Conversion Example 1 ..............
  • Page 5 Four IPGWx pairs (two SS7IPW pairs and two IPGWI pairs) .......... A-7 Eight IPGWx cards, two mates, three linksets ..............A-8 Four IPGWx cards, one linkset for end office ..............A-9 Unsupported Scenarios ....................... A-9 Appendix B. References ....................B-1 Tekelec internal references ......................B-1 910-5346-001 Revision A, September 2008...
  • Page 6 Table of Contents SIGTRAN User Guide External References ........................B-1 Glossary ........................Glossary-1 Index ..........................Index-1 910-5346-001 Revision A, September 2008...
  • Page 7 Figure 5-2. SIGTRAN: Failover at 0.8 erlang..............5-14 Figure 5-3. SIGTRAN: Every link at 0.4 erlang and 800 MSU/s........5-14 Figure 5-4. EAGLE 5 ISS: Failover at 0.8 erlang and 1600 MSU/s........5-15 Figure 5-5. Unihoming versus multihoming................ 5-18 Figure 5-6. Mated Signal Transfer Point redundancy............5-19 Figure 6-1.
  • Page 8 List of Figures SIGTRAN User Guide 910-5346-001 Revision A, September 2008...
  • Page 9 Table 5-10. IPLIMx and IPGWx connectivity data............. 5-11 Table 5-11. IPSG Connectivity Data..................5-12 Table 5-12. CTP Configuration Data Descriptions for Tekelec EAGLE 5 ISS....5-22 Table 6-1. EAGLE 5 ISS IP signaling maximum capacities by card and application... 6-2 910-5346-001 Revision A, September 2008...
  • Page 10 List of Tables SIGTRAN User Guide viii 910-5346-001 Revision A, September 2008...
  • Page 11: Chapter 1. Introduction

    IP-based functions and applications. Tekelec is prepared to take customers through this process at their own pace by offering expertise and tested products that will assist in achieving this goal.
  • Page 12: Audience

    This document examines the reasons for transitioning to an SS7-over-IP (SSoIP) network, the considerations that go into planning and dimensioning, and helpful information for implementing the network. This document does not attempt to provide a beginning-to-end solution for such a transition; contact your Tekelec Sales Representative to discuss your specific needs.
  • Page 13: Manual Conventions

    Tekelec products are a part of the SS7-over-IP solution. This section describes how the EAGLE 5 Integrated Signaling System (ISS) functions as a gateway to internet networks; and the Integrated Application Solution (IAS) , which provides several network management and performance tools including IP traffic monitoring through the Integrated Message Feeder (IMF) .
  • Page 14: Customer Care Center

    The Tekelec Customer Care Center offers a point of contact for product and service support through highly trained engineers or service personnel. The Tekelec Customer Care Center is available 24 hours a day, 7 days a week at the following locations: •...
  • Page 15: Related Publications

    Availability (LA) releases, Tekelec may publish a documentation subset tailored to specific feature content or hardware requirements. Documentation Bulletins announce a new or updated release. The Tekelec EAGLE 5 ISS documentation set is released on an optical disc. This format allows for easy searches through all parts of the documentation set.
  • Page 16: Locate Product Documentation On The Customer Support Site

    Support Site Locate Product Documentation on the Customer Support Site To view or download product documentation, log into the Tekelec Customer Support site at: https://support.tekelec.com/index.asp Log in with your user name and password. (Click on Need an Account? if you need to register).
  • Page 17: Chapter 2. Ss7-Over-Ip Networks

    SS7-over-IP networks SS7-over-IP networks overview ......................... 2-1 SS7 limitations ..............................2-2 Role of SIGTRAN .............................. 2-2 SCTP (Stream Control Transmission Protocol) ..................2-3 M2PA (MTP2 User Peer-to-Peer Adaptation Layer) protocol ..............2-4 M3UA (MTP Level 3 User Adaptation Layer) protocol ................2-5 SUA (SCCP User Adaptation) protocol ......................
  • Page 18: Ss7 Limitations

    (PSTN) signaling over IP networks. A set of signaling transport protocols has been developed out of the group’s work. For the purposes of this document, the protocols are collectively called the “ SIGTRAN” protocols or suite. The SIGTRAN architecture used by Tekelec includes the following protocols. The figure shows their location in the protocol stack: •...
  • Page 19: Sctp (Stream Control Transmission Protocol)

    SS7 messages over IP networks. Tekelec deviations The following sections summarize the most important deviations from the IETF RFCs that Tekelec has made. Refer to the Tekelec protocol compliance matrices for details; see Tekelec internal references .
  • Page 20: M2Pa (Mtp2 User Peer-To-Peer Adaptation Layer) Protocol

    • Connection behavior when a stream becomes congested A lack of consensus on the IETF SIGTRAN mailing list regarding these issues resulted in Tekelec supporting a maximum of two streams: a control stream and a data stream. SCTP timer Based on experiences in the field, Tekelec has deviated from some RFC-recommended timer settings, especially related to retransmission, to better accommodate signaling networks.
  • Page 21: M3Ua (Mtp Level 3 User Adaptation Layer) Protocol

    SS7 link; there are no 16-link-per-linkset restrictions. Each M3UA-connected IP endpoint can be addressed by an SS7 point code unique from the signaling gateway’s point code. Tekelec offers two types of topologies M3UA: IPGWx using routing keys, and IPSG using IPSG-M3UA links.
  • Page 22: Sua (Sccp User Adaptation) Protocol

    SS7-over-IP signaling transport SIGTRAN User Guide At the Signaling Gateway, M3UA indicates to remote MTP3 users at IP end points when an SS7 signaling point is reachable or unreachable, or when SS7 network congestion or restrictions occur. NOTE: IPGW and IPSG M3UA links cannot be in the same link set at the same time. However, the EAGLE allows IPGW and IPSG-M3UA link sets to have separate routes to the same AS, aiding in cutover.
  • Page 23: From Ss7 Message To Ip Packet

    Signaling End Point (SEP) or another Signaling Gateway, which may be separate physical devices or integrated in any combination. For example, the EAGLE 5 ISS can perform the functions of a Signal Transfer Point in addition to those of a Signaling Gateway.
  • Page 24: Reasons To Transition To An Ss7-Over-Ip Sigtran Network

    Reasons to transition to an SS7-over-IP SIGTRAN SIGTRAN User Guide network Figure 2-5. Communication inside the WAN The Source Host (Signaling Gateway) builds a packet with a destination IP address. A router on the LAN converts the packet to the WAN protocol and places it on the WAN. Each router on the WAN looks at the destination IP address and determines the port to which it forwards the packet.
  • Page 25: Increased Capacity

    Data traffic including Short Message Service (SMS) can run more efficiently over SIGTRAN . For example, SMS data is saturating some SS7 networks. Using devices such as the Tekelec EAGLE 5 ISS with its gateway functions, operators can have a Short Message Service Center communicate directly to Home Location Registers (HLR) and Mobile Switching Centers (MSCs) using SIGTRAN .
  • Page 26: Type Of Network Change

    Implementing SS7-over-IP on an SS7 system creates a converged IP network that allows quick, cost-effective implementation of IP-based services using existing network elements. The Tekelec EAGLE 5 ISS with its Signaling Transfer Point and Signaling Gateway functions offers a reliable solution for this transition.
  • Page 27: Diversity

    SIGTRAN User Guide When to transition to an SS7-over-IP SIGTRAN network • Full accelerated replacement with a short transition period based on cost, efficiency, and fault management: even if complete transition is desired, it is unrealistic to expect to instantaneously cut over unless the subscriber base is very small.
  • Page 28 When to transition to an SS7-over-IP SIGTRAN SIGTRAN User Guide network 2-12 910-5346-001 Revision A, September 2008...
  • Page 29: Chapter 3. Tekelec Solutions

    Tekelec is the IP signaling leader and the first to recognize the value of IP Signaling by developing the TALI protocol (RFC 3094) in 1998. Tekelec was first to market with an IP Signaling solution (IPLIMx application) in 2000, and has years of IP signaling deployment experience.
  • Page 30: Iplimx, Ipgwx And Ipsg Applications

    EAGLE 5 ISS SIGTRAN User Guide Using the EAGLE 5 ISS to structure the network provides a predictable and reliable architecture with all required interfaces. It is easily scalable to cover huge core networks, with an independent control layer that allows expansion on different parts of the network independent of each other.
  • Page 31: Tekelec Integrated Application Solutions (Ias)

    SS7 variant support across a single IP connection. Tekelec Integrated Application Solutions (IAS) The Tekelec IAS platform, integrated with EAGLE 5 ISS, provides tools to capture network traffic data and convert it into useful business intelligence for troubleshooting, managing traffic, roamers, services, and revenues.
  • Page 32: Integrated Message Feeder (Imf)

    The IMF is an integrated site collector that provides integrated data acquisition in conjunction with the EAGLE 5 ISS. IMF connects to the EAGLE 5 ISS via Ethernet and monitors signaling links on the EAGLE 5 ISS including LSL, ATM HSL, SE HSL, M2PA and M3UA.
  • Page 33: Chapter 4. Transition Planning

    Resolve high-level network design Determine any issues by looking at the current network design compared to the new network architecture. Consider the protocols to be used, specific Tekelec implementations, mated-pair redundancy and link engineering, unihoming versus multihoming, and IP redundancy.
  • Page 34: Collect Network Information

    M2PA (MTP2 User Peer-to-Peer Adaptation Layer) protocol • M3UA (MTP Level 3 User Adaptation Layer) protocol • SUA (SCCP User Adaptation) protocol Be aware of Tekelec-specific implementations or deviations and how they will impact your new network. Read about these implementations: • Protocol deviations —...
  • Page 35: Table 4-1. M2Pa And M3Ua Configuration Parameter Data

    To gather the information required to determine configuration parameters of the M2PA and M3UA association(s) between an EAGLE 5 ISS node and each Signaling End Point (SEP), a spreadsheet per EAGLE 5 ISS node can be very helpful. Every node connected by a SIGTRAN link should appear as a row in the spreadsheet, with the headings listed in the table along the top row.
  • Page 36: Analyze Data

    The percentage of SCCP Class 1 traffic expected to be sent to this node Peak MSU/s The planned number of MSU/s expected to be sent to this node from all EAGLE 5 ISSs in worst-case conditions Max Assoc The maximum number of associations that this node supports to this EAGLE 5 ISS See also: •...
  • Page 37: Refine Timers And Parameters

    SIGTRAN User Guide Transition guidelines • System verification • Chapter 7 Troubleshooting Refine timers and parameters Refine timers and parameters 910-5346-001 Revision A, September 2008...
  • Page 38 Transition guidelines SIGTRAN User Guide 910-5346-001 Revision A, September 2008...
  • Page 39: Chapter 5. Dimensioning

    Dimensioning About bandwidth, throughput, transaction units, and TPS ................. 5-1 Transactions versus transaction units and TPS ................... 5-2 Scalability ................................5-2 Link equivalency ............................5-2 Hardware and software requirements ......................5-4 System capacity ............................5-5 Achieving IP Signaling Applications’ Advertised Capacity ................5-5 Factors affecting advertised capacity ......................
  • Page 40: Transactions Versus Transaction Units And Tps

    Not all MSUs are the same, and not all configurations are the same. Rather than to continue to engineer product capacity for the worst case and thereby penalizing customers who are not using worst-case scenarios, Tekelec is providing the Transaction Unit (TU) model to allow customers flexibility in how to use application or card capacity.
  • Page 41: Table 5-2. Eagle Link Equivalency For Ipsg

    SIGTRAN User Guide Scalability ATM <->Low speed link M2PA<-> ATM <->Low speed link M3UA<-> ATM <->Low speed link + MTP Msu/ Msu/ Msu/ 2000 4000 4000 2000 4000 4000 1800 4000 4000 1800 4000 4000 1800 4000 4000 1800 4000 4000 1800 4000...
  • Page 42: Hardware And Software Requirements

    5000 5000 5000 5000 Hardware and software requirements For SS7-over-IP networks, Tekelec uses two cards to achieve IP connectivity • Single-slot EDCM (SSEDCM) card • EPM-based Ethernet (E5-ENET) card Either of these cards can be loaded with the IPLIMx or IPGWx application, but IPSG can be loaded only on the E5-ENET card: •...
  • Page 43: System Capacity

    SIGTRAN User Guide Achieving IP Signaling Applications’ Advertised Capacity Each of these cards has a different maximum capacity for the number of TPSs that they will support. The older SSEDCM supports up to 2,000 TPS, while the E5-ENET card supports up to 4,000 TPS (5,000 TPS using IPSG).
  • Page 44: Factors Affecting Advertised Capacity

    A wide variety of factors determine the processing resources required by IP applications to manage a given traffic load, and cause the processing of each MSU to be more expensive. For example, the EAGLE 5 ISS provides a feature that enables support of Class-1 Global Title traffic. When the feature is enabled and a...
  • Page 45: Table 5-5. Base Transaction Unit Cost Per Msu Sif Size

    SIGTRAN User Guide Achieving IP Signaling Applications’ Advertised Capacity Base transaction unit rules The base transaction unit rules are applied to establish the base transaction unit costs: Sufficient IP TPS is assigned to the linkset to which the IPGWx signaling link is assigned. (IPGWx only) The traffic is not monitored via the E5IS feature .
  • Page 46: Adjusted Transaction Unit

    Capacity Adjusted transaction unit The adjusted transaction unit is the value calculated and tested by Tekelec that represents additional cost per base transaction unit when the configuration deviates from the base configuration. The table shows adjusted configuration scenarios and their TU values for IPGWx (M3UA), IPLIMx (M2PA) and IPSG (M3UA and M2PA) .
  • Page 47: Table 5-8. Calculating Tps

    SIGTRAN User Guide Achieving IP Signaling Applications’ Advertised Capacity Determine which application will carry the traffic (IPGWx, IPLIMx or IPSG). Determine the type of card that will host the application (SSEDCM or E5-ENET). Determine the adapter protocol type of the association(s) that will carry the traffic (in the table, the adapter is always M3UA).
  • Page 48: Functionality Of Configurable Sctp Buffer Sizes Per Association

    Once the needed throughput is established, calculate the number of cards required to support this need (see Calculate the number of cards required Rules for Integrated Datafeed using STC cards Tekelec internal references contains additional rules related to Integrated Datafeed (for IMF using STC cards). Follow the guidelines and consult the tables in Tekelec internal references •...
  • Page 49: System Constraints Affecting Total Ip Signaling Capacity

    Application Servers per system Associations per Application Server Ethernet interfaces per card Unihomed connection on either interface, multihomed using both interfaces EAGLE 5 ISS Hardware Redundancy Model Capacity (TPS) 2000/4000 MSU/s 2000/4000 MSU/s 2.5/5K is the goal Failure mode (80%)
  • Page 50: Table 5-11. Ipsg Connectivity Data

    Application Servers per system Associations per Application Server Ethernet interfaces per card Unihomed connection on either interface, multihomed using both interfaces EAGLE 5 ISS Hardware Redundancy Model Capacity (TPS) 5000 MSU/s 5000 MSU/s 2.5/5K is the goal 5-12 910-5346-001 Revision A, September 2008...
  • Page 51: Sigtran Engineering Guidelines

    SIGTRAN User Guide SIGTRAN engineering guidelines Feature M2PA M3UA Notes Failure mode (80%) 4000 MSU/s 4000 MSU/s Capacity growth required at this point Multihoming support Connection model Server Server SS7 routing Peer to peer Traditional least-cost based Supports lossless Supports network management Number of DTA Point Codes Number of internal point codes per network...
  • Page 52: Figure 5-1. Sigtran: Every Ip Link At 0.4 Erlang

    SIGTRAN engineering guidelines SIGTRAN User Guide Figure 5-1. SIGTRAN: Every IP link at 0.4 erlang If the linkset to STP2 fails, another linkset to STP1 now carries 0.8 erlang. For an card with a maximum of 2,000 TU per card, 80% is 1,600 TU. Figure 5-2.
  • Page 53: Calculate The Number Of Cards Required

    SIGTRAN User Guide SIGTRAN engineering guidelines Figure 5-4. EAGLE 5 ISS: Failover at 0.8 erlang and 1600 MSU/s Calculate the number of cards required Below are examples of calculations to determine how many cards are needed. These are somewhat simplified;...
  • Page 54: Ipgwx Congestion Management Options

    IPGWx congestion management options SIGTRAN User Guide • Average MSU size is 100 bytes/MSU over M3UA • Less than 5 connections per IP SSEDCM card • Monitoring is required Calculation: • During normal operation, each Signal Transfer Point should handle 5000 MSU/s •...
  • Page 55: Unihoming Versus Multihoming

    Redundancy and link engineering The EAGLE 5 ISS can be deployed with completely redundant IP network paths, each of which must be capable of sustaining the worst-case traffic load; or a redundancy model that relies on a mate Signal Transfer Point for IP path redundancy, although this option is less robust (and less expensive).
  • Page 56: Choosing A Redundancy Method For M2Pa Links

    If a completely redundant IP network path is not available, then a redundancy model that relies on a mate Signal Transfer Point for IP path redundancy is supported by Tekelec. This model is less robust but also less expensive. 5-18...
  • Page 57: Ipgwx Mateset

    Mated : Two IPGWx or IPSG linksets are allowed in a mateset by using the matelsn linkset parameter. The limitation of this approach is that each linkset can have only one card. This configuration for IPGWx is supported to be backward compatible with previous EAGLE 5 ISS software versions. IPGWx status sharing Each IPGWx and IPSG card supports up to 50 IP connections, each of which can be available or unavailable for SS7 traffic.
  • Page 58: Signaling Link Selection (Sls) Routing

    From the SS7-over-IP perspective, there are two types of nodes: SS7-over-IP-related nodes (which are IP- equipped nodes involved in the overall signaling solution, such as the EAGLE 5 ISS, IP Service Control Points , Media Gateway Controllers and Media Gateways , and any management platforms doing work directly related to the SS7-over-IP solution);...
  • Page 59: Retransmission Concept

    RTO: Time to wait before the current retransmit attempt is declared a failure. This time is dynamic because it is a moving average of the network. • RMAX: Upper bound of calculated RTO (10 ms to 1,000 ms); the default is 800; Tekelec suggests 3 * RMIN 5-21 910-5346-001 Revision A, September 2008...
  • Page 60: Table 5-12. Ctp Configuration Data Descriptions For Tekelec Eagle 5 Iss

    Retransmission concept SIGTRAN User Guide • RMIN: Lower bound of calculated RTO (10 ms to 1,000 ms). The default is 120; Tekelec suggests the greater of (1.2 * average RTT) or (10 ms + average RTT). • CWMIN: Minimum Congestion Window Size (1,500 to 192K); the default is 3K RFC timer setting With an exponential timer setting, the RTO value is doubled for each retransmit attempt.
  • Page 61: Configure Congestion Window Minimum (Cwmin) Parameter

    5 seconds LIN timer setting Tekelec has implemented a more aggressive timer method called Linear (LIN), in which the RTO between attempts is constant. Tekelec recommends this setting to detect a failure more quickly than the RFC method. With the LIN timer setting, the time to declare the association down is at least...
  • Page 62 Retransmission concept SIGTRAN User Guide to be used. As a general rule, setting CWMIN to a value equal to half of the traffic rate in an RTT interval should allow adequate retransmit-recovery time while preventing excessive load to the peer: CWMIN = (Bytes/Sec * RTT) / 2 bytes NOTE: Setting CWMIN to a value much higher than MTU will result in periodic intermediate node overloads.
  • Page 63: Chapter 6. Implementation

    Sales Representative. EAGLE 5 ISS An EAGLE 5 ISS fully configured for SS7-over-IP consists of at least one IPLIMx, IPLIMx, or IPSG application. The applications can be installed on either an SSEDCM (if IPLIMx or IPGWx) or an E5-ENET card.
  • Page 64: Integrated Message Feeder (Imf)

    IPx cards. Only M2PA links that are RFC 4165 compliant can be monitored. A minimum of two STC cards are required per system to turn on the monitoring feature in the EAGLE 5 ISS.
  • Page 65: Converting Ipgwx M3Ua Application Servers To Ipsg-M3Ua Linksets

    • The connected AS’s maximum supported number of connections and attached Signaling Gateways Examples of typical deployments and possible conversion strategies are listed below, but contact your Tekelec sales representative to assist in planning an actual conversion. Since this feature does not initially provide any automated IPGWx-to-IPSG conversion functionality, it is highly recommended that ProComm scripts or other automated EAGLE provisioning functionality be used to further mitigate risk.
  • Page 66 Converting IPGWx M3UA Application Servers to SIGTRAN User Guide IPSG-M3UA Linksets Figure 6-1. PGWx to IPSG-M3UA Conversion Strategy Example 1 The IPGWx deployment shown in #1 of Figure "PGWx to IPSG-M3UA Conversion Strategy Example 1" has the following attributes: • Each STP in the mated pair of STPs utilizes a single IPGWx card to provide connectivity to AS1 910-5346-001 Revision A, September 2008...
  • Page 67: Ipgwx To Ipsg-M3Ua Conversion Example 2

    SIGTRAN User Guide Converting IPGWx M3UA Application Servers to IPSG-M3UA Linksets • Each IPGWx card hosts a single M3UA association referenced by AS1 • AS1 is referenced by a single DPC-only Routing Key with DPC=X in each STP The configuration shown in #2 of Figure "PGWx to IPSG-M3UA Conversion Strategy Example 1 is a result of the following steps: •...
  • Page 68 Converting IPGWx M3UA Application Servers to SIGTRAN User Guide IPSG-M3UA Linksets Figure 6-2. IPGWx to IPSG-M3UA Conversion Strategy Example 2 910-5346-001 Revision A, September 2008...
  • Page 69: Ipgwx To Ipsg-M3Ua Conversion Example 2A

    SIGTRAN User Guide Converting IPGWx M3UA Application Servers to IPSG-M3UA Linksets It should be noted that the IPGWx deployment shown in #1 of has the following attributes: Figure 6-2 • Each STP in the mated pair of STPs utilizes two IPGWx cards to provide connectivity to AS1 •...
  • Page 70: Figure 6-3. Ipgwx To Ipsg-M3Ua Conversion Strategy Example 2A

    Converting IPGWx M3UA Application Servers to SIGTRAN User Guide IPSG-M3UA Linksets Figure 6-3. IPGWx to IPSG-M3UA Conversion Strategy Example 2A 910-5346-001 Revision A, September 2008...
  • Page 71: Configuration

    Configure the IPSG application This section provides a basic overview of the steps involved to provision the IPSG application for M3UA. For detailed procedures, see the Database Administration Manual - IP7 Secure Gateway of your current EAGLE 5 ISS documentation suite.
  • Page 72: Configure The Ipsg Application On The Same Card

    Configuration SIGTRAN User Guide Define capacity and use alarm (ent-ls). ent-ls:lsn=ls1201:apc=10-10-10:lst=a:adapter=m3ua:ipsg=yes:rcontext=1:slktps=100 Tell the EAGLE 5 ISS that this is a SIGTRAN M3UA link (ent-slk). Enter route (ent-rte). Allow and open the SCTP association (chg-assoc). Activate signaling link (act-slk). Configure the IPSG Application on the Same Card The following series of commands may be used to provision an IPSG-M2PA link on the same card, assuming the card, IP addresses and hosts are already configured.
  • Page 73: Configure The Iplimx Application

    Configure the IPLIMx application This section provides a basic overview of the steps involved to provision the IPLIMx application for M2PA. For detailed procedures, see the Database Administration Manual - IP7 Secure Gateway of your current EAGLE 5 ISS documentation suite.
  • Page 74: Configure The Ipgwx Application

    (and are recommended by Tekelec) for IPGWx APCs. Private point codes are used for internal routing within the EAGLE 5 ISS and are not known outside of the EAGLE 5 ISS. By making APCs private, it is possible to have a point code value indicated as private and still have the same point code value (as not private) available for network configuration.
  • Page 75 SIGTRAN User Guide Configuration Define bandwidth and use alarm (ent-ls). Tell the EAGLE 5 ISS that this is a SIGTRAN M3UA link (ent-slk). Enter SEP point codes (ent-dstn). Enter route (ent-rte). 6-13 910-5346-001 Revision A, September 2008...
  • Page 76 Configuration SIGTRAN User Guide Define the IP settings for the Ethernet port (chg-ip-lnk). Associate an IP address to a host name that will be used in configuring the association (entip- host). Define the network devices that the DCM card will access (chg-ip-card). Enter an Application Server Process and bind an SCTP association with it (ent-assoc).
  • Page 77: Refine Timers And Parameters

    70 ms for SSEDCMs and 120 ms for E5-ENETs. Refine RTO parameter After an association is established, the EAGLE 5 ISS pass command should be used to get the true RTT as experienced by the association. 6-15...
  • Page 78: System Verification

    ASSOCRTT command complete System verification Once you have finished configuring the EAGLE 5 ISS for SS7-over-IP, use the following steps to verify that it is correct. For details on the commands, see the EAGLE 5 ISS Command Manual. Verify network connectivity Is the IPLIM/IPGWx card IS-NR (In-service Normal)? rept-stat-card:mode=full:loc=<IP CARD location>...
  • Page 79: Verify Iplimx Configuration

    SIGTRAN User Guide System verification Are there errors on the Ethernet Interfaces? Are there collisions? CRC errors? Alignment errors? Retransmits? pass:loc=<IP card location>:cmd=netstat -d 0 <For Ethernet Interface A> pass:loc=<IP card location>:cmd=netstat -d 1 <For Ethernet Interface B> Are there checksum errors? pass:loc=<IP card location>:cmd="netstat -p sctp Change the SCTP checksum if there are errors, rtrv-sg-opts will show you what checksum is set at;...
  • Page 80: Verify Ipgwx Configuration

    System verification SIGTRAN User Guide rept-stat-ls:lsn=<IPLIM linkset> What is the status of the SLKs? rept-stat-slk:loc=<ip card location>:port=<SS7 port> What is the status of the adjacent point code? rept-stat-rte:mode=full:dpc=<adjacent point code Verify IPGWx configuration Is there an IPGWx application in the system? rtrv-card Is the IP-LNK table data filled properly? Duplex? 10 or 100 Mbps? Auto=no? IP address Correct? Subnet Mask Correct?
  • Page 81 SIGTRAN User Guide System verification rept-stat-ls:lsn=<IPLIM linkset> What is the status of the adjacent point code? rept-stat-rte:mode=full:dpc=<adjacent point code What is the status of the far-end point code? rept-stat-rte:mode=full:dpc=<far-end point code> 6-19 910-5346-001 Revision A, September 2008...
  • Page 82 System verification SIGTRAN User Guide 6-20 910-5346-001 Revision A, September 2008...
  • Page 83: Chapter 7. Troubleshooting

    Troubleshooting General troubleshooting ............................. 7-1 Verify UIMs and UAMs ............................. 7-2 Is the card configured correctly? ........................7-2 Connection does not become established ......................7-3 Connection bounces and is unstable ........................7-3 AS/PC in route key does not become available or ACTIVE (IPGWx only) ............7-3 IP destination is not informed of SS7 destination status changes;...
  • Page 84: Verify Uims And Uams

    Verify UIMs and UAMs SIGTRAN User Guide • ualog/asplog/linkinfo pass command to retrieve logs of events in stack and control messages transmitted or received • msucount pass command to display traffic counts of MSUs that have been transmitted, received, rerouted, or discarded, and the discard reason Verify UIMs and UAMs If there are any Unsolicited Information Messages (UIMs) or Unsolicited Alarm Messages (UAMs) occurring related to the SIGTRAN configuration, refer to the Corrective Maintenance section in the EAGLE...
  • Page 85: Connection Does Not Become Established

    SIGTRAN User Guide Connection does not become established Connection does not become established Card up and stable? rept-stat-card Association status? rept-stat-assoc Network connectivity ? netstat -I rept-stat-card:mode=full Errors (collisions, etc.) on the network interface? netstat -d 0/1t Far end reachable? ping traceroute Near end and far end use same SCTP CRC?
  • Page 86: Ip Destination Is Not Informed Of Ss7 Destination Status Changes; Network Management Is Not Working Correctly (Ipgwx Only)

    IP destination is not informed of SS7 destination status SIGTRAN User Guide changes; network management is not working correctly (IPGWx only) Routing key provisioned for AS? rtrv-appl-rtkey Network appearance/routing context required and matched? rtrv-appl-rtkey ualog AS/ASP activated at far end? aslog ualog SS7 APC/SAPC and associated route exists in the same network (and group code) as the PC?
  • Page 87: Traffic Not Load-Balanced Properly

    SIGTRAN User Guide Traffic not load-balanced properly assocrtt, sctp Is IPTPS set correctly for IPGWx ? rept-stat-iptps rtrv-ls Is an interface set to half-duplex somewhere in the path to the far end, causing excessive retransmissions? rtrv-ip-lnk sctp Traffic not load-balanced properly Source traffic has uneven SLS distribution? All cards in linkset or mateset do not host a connection to the IP Application Server (IPGWx only)? rtrv-assoc...
  • Page 88 Association SIGTRAN User Guide sctp -a 910-5346-001 Revision A, September 2008...
  • Page 89: Appendix A. Additional Deployment Scenarios

    Additional Deployment Scenarios IPLIM/M2PA deployment scenarios ......................... A-1 Simple M2PA A-link configuration (3,000 TPS) ..................A-1 High-throughput M2PA A-link configuration (30,000 TPS) ..............A-2 High-throughput M2PA C-link configuration (30,000 TPS) ..............A-3 IPLIM/M2PA deployment scenarios ......................... A-3 Simple M2PA A-link configuration (3,000 TPS) ..................A-3 High-throughput M2PA A-link configuration (30,000 TPS) ..............
  • Page 90: Figure A-1. Sg Connected To Ip Sep Via Two M2Pa Links

    IPLIM/M2PA deployment scenarios SIGTRAN User Guide Figure A-1. SG connected to IP SEP via two M2PA links High-throughput M2PA A-link configuration (30,000 TPS) The following figure shows a Signaling Gateway (SG) connected to an IP-based SEP via eleven M2PA links, one per IPLIMx card.
  • Page 91: Iplim/M2Pa Deployment Scenarios

    SIGTRAN User Guide IPLIM/M2PA deployment scenarios High-throughput M2PA C-link configuration (30,000 TPS) The following figure shows two mated Signaling Gateways connected to an IP-based SEP. The C-links between the Signaling Gateways and the A-links to the IP signaling end point of the M2PA type. Enough C-links are provisioned to handle the case where one Signaling Gateways loses all connectivity to X.
  • Page 92: High-Throughput M2Pa A-Link Configuration (30,000 Tps

    IPLIM/M2PA deployment scenarios SIGTRAN User Guide Figure A-4. SG connected to IP SEP via two M2PA links High-throughput M2PA A-link configuration (30,000 TPS) The following figure shows a Signaling Gateway (SG) connected to an IP-based SEP via eleven M2PA links, one per IPLIMx card.
  • Page 93: High-Throughput M2Pa C-Link Configuration (30,000 Tps

    Figure A-7. IPGWx active/standby configuration • Active/standby configurations should be implemented at the IP Signaling Points (IPSPs) rather than at the EAGLE 5 ISS. • All DCMs assigned to an IPGWx mateset should host connections to nodes comprising an Application Server and should loadshare traffic in the absence of failures.
  • Page 94: Two-Pair Ipgwx

    IPGW/M3UA deployment scenarios SIGTRAN User Guide Two-pair IPGWx Figure A-8. Two-Pair IPGWx for Maximum TPS • Two IPGWx cards are deployed as a mateset. No more than two cards for each application are allowed. • Each card has one signaling link, represented by a hatched line. Each IPGWx signaling link is alone in a linkset, represented by an ellipse.
  • Page 95: Four Ipgwx Pairs (Two Ss7Ipw Pairs And Two Ipgwi Pairs

    SIGTRAN User Guide IPGW/M3UA deployment scenarios Four IPGWx pairs (two SS7IPW pairs and two IPGWI pairs) Figure A-9. Four IPGWx pairs (two SS7IPW pairs and two IPGWI pairs) • There are four IPGWx matesets, each comprised of two linksets (a combined linkset). •...
  • Page 96: Eight Ipgwx Cards, Two Mates, Three Linksets

    IPGW/M3UA deployment scenarios SIGTRAN User Guide Eight IPGWx cards, two mates, three linksets Figure A-10. Eight IPGWx cards, two mates, three linksets • Eight IPGWx cards are present, each having a single signaling link. IPGW1 and IPGW2 have their links assigned to distinct linksets.
  • Page 97: Four Ipgwx Cards, One Linkset For End Office

    The EAGLE 5 ISS is operating in End Office Mode. This means that the IPSPs are IP-attached remote user- parts that share the true and secondary point codes of EAGLE 5 ISS (PC=A). In order to route from the inbound LIMs to the outbound IPGWx cards, an internal point code (IPC) is used.
  • Page 98: Figure A-12. Unsupported Deployment Scenario: Combined Linksets (1

    IPGW/M3UA deployment scenarios SIGTRAN User Guide Figure A-12. Unsupported deployment scenario: Combined linksets (1) The following figure shows that the route to IPGWx linksets 1 and 2 are combined for AS1; and linksets 2 and 3 are combined for AS2. Combined linksets are not supported. Figure A-13.
  • Page 99: Appendix B. References

    TK149-SIGTRAN IPLIM and IPGW Provisioning Student Guide, Rev. 4.1, Tekelec, 2007 External References Database Administration - IP7 Secure Gateway Manual of your current EAGLE 5 ISS documentation set. Log in here to locate the manual for your specific release: https://support.tekelec.com/index.asp http://tools.ietf.org/wg/sigtran/...
  • Page 100 External References SIGTRAN User Guide http://www.microsoft.com/technet/prodtechnol/ Quality of Service Technical White Paper windows2000serv/plan/qosover2.mspx http://www.skywayradio.com/tech/linux/bandwidth.html Linux Bandwidth http://www.iec.org/online/tutorials/ss7_over/index.html SS7 over IP Signaling Transport & SCTP 910-5346-001 Revision A, September 2008...
  • Page 101 A data acquisition system similar to Sentinel. Intelligent Peripheral Internet Protocol Tekelec's Internet Protocol to SS7 Interface IPGWx Point-to-multipoint MTP-User signaling (e.g. ISUP, TCAP) over IP capability. Typicallyused for A link connectivity which require routing keys. Far End not required to support MTP3.
  • Page 102 (originating point code), the identification of the node receiving the message (destination point code), and the signaling link selector which the EAGLE 5 ISS uses to pick which link set and signaling link to use to route the message.
  • Page 103 E5-ENET 3-2 , 5-5 , 5-6 average message size 5-10 E5IS feature EAGLE 5 ISS bandwidth 1-1 , 2-2 , 2-9 , 2-11 , 3-1 End Office mode , 4-3 , 4-4 , 5-1 , 5-17 , 5-18 , EPM-based Ethernet (E5-ENET) card...
  • Page 104 SIGTRAN User Guide Media Gateway Controllers memory 5-10 message buffers IETF 2-2 , 2-3 Message Signaling Unit (MSU) Message Transfer Part (MTP) IMT interface capacity Integrated Application Solution (IAS) Mobile Switching Center (MSC) Integrated Message Feeder (IMF) Mobile Switching Centers (MSCs) Internet Engineering Task Force (IETF) 5-2 , 5-5 , 5-6 , 5-10 , 5-13 , 1-1 , 2-9...
  • Page 105 5-17 1-1 , 1-2 , 2-2 , 2-4 SCTP association 3-2 , A-1 , A-3 Tekelec solution 5-20 SCTP buffering Tekelec SS7-over-IP solution SCTP buffers 5-10 throughput 2-9 , 5-2 , 5-8 , 5-20 SCTP endpoint 2-3 , 5-21 total transaction unit value...
  • Page 106 SIGTRAN User Guide Index-4 910-5346-001 Revision A, September 2008...

Table of Contents