sinap/ss7 user’s guide -...

Part Number: R8051-17

January 2005

SINAP/SS7 User’s Guide

Stratus Technologies R8051-17

SINAP/SS7 User’s Guide

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, Continuum, Continuous Processing, StrataLINK, StrataNET, DNCP, SINAP, and FTX are registered trademarks of Stratus Technologies Bermuda, Ltd. The Stratus Technologies logo, the ftServer logo, Stratus 24 x 7 with design, The World’s Most Reliable Servers, The World’s Most Reliable Server Technologies, ftGateway, ftMemory, ftMessaging, ftStorage, Selectable Availability, XA/R, SQL/2000, The Availability Company, RSN, and MultiStack are trademarks of Stratus Technologies Bermuda, Ltd.

Hewlett-Packard, HP, and HP-UX are registered trademarks of Hewlett-Packard Company. Sun, Solaris, Netra, and SunFire are trademarks or registered trademarks of Sun Microsystems, Inc. SPARC is a registered trademark of SPARC International, Inc UNIX is a registered trademark of X/Open Company, Ltd., in the U.S.A. and other countries. The registered trademark Linux(R) 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/SS7 User’s Guide

Part Number: R8051 Revision Number: 17 Updated for SINAP/SS7 Release Number: 14.2 Publication Date: January 2005

Stratus Technologies, Inc. 111 Powdermill Road Maynard, Massachusetts 01754-3409

© 2005 Stratus Technologies Bermuda, Ltd. All rights reserved.

Contents

Preface xxixAudience xxixRevision Information xxixManual Organization xxxNotation Conventions xxxiSyntax Notation xxxiiRelated Manuals xxxiii

A Note on the Contents of Stratus Manuals xxxivAccessing Documentation xxxivCommenting on the Documentation xxxiv

Contacting the CAC xxxiv

1. Introduction 1-1

2. Performing Basic Tasks 2-1Using the MultiStack Product 2-1Starting SINAP/SS7 and Logging In 2-2

Starting the System Using the start_sinap Script File 2-2Restarting the System with Script Files 2-10Automatically Starting and/or Restarting from a UNIX Initialization File 2-11

Starting Client Applications 2-12Starting a Client Application Using the startappl Script File 2-12 Automatically Starting a Client Application with the Utility Monitor 2-13

Using Command Line Parameters 2-14Using sinap_utlmon Environment Variable File 2-15

Accessing the User Interfaces 2-15Bringing Up the Terminal Handler 2-15Using Terminal Handler Operation Modes 2-18

Keyboard Shortcuts 2-20Keystroke 2-20

Executing MML Commands from a Login Window 2-21

Contents v

Contents

Man Page Format 2-23Sample Script File 2-24

Displaying Man Pages 2-24Listing Active Processes 2-26Displaying Process Versions of SINAP/SS7 Processes 2-27

Man Page Format 2-28Enabling and Disabling Printing 2-28

Menu Selection Mode 2-29MML Command Format 2-29Man Page Format 2-29

Configuring the SINAP/SS7 Software 2-29Using a Script File to Configure Network Components 2-30Re-creating Existing Configurations Using static2mml 2-30

Stopping the SINAP/SS7 System 2-32

3. Software Configuration 3-1Configuration Requirements 3-1Link Performance Recommendations 3-9Configuring the Terminal Handler 3-10

Defining Privilege Levels for MML Commands 3-10Defining Menu Options in the Menu Definition File 3-11

Menu Definition Operators 3-11Terminal Handler Screen Partitions 3-23

Creating Network Components 3-26Creating an Own Point Code 3-31

MML Command Format 3-33Creating a Link Set 3-34

MML Command Format 3-37Man Page Format 3-37

Creating a Combined Link Set (ANSI Only) 3-37MML Command Format 3-38Man Page Format 3-38

Creating a Link 3-39MML Command Format 3-42Man Page Format 3-42

Creating a Route Set 3-42MML Command Format 3-46Man Page Format 3-46

Creating a Concerned Point Code 3-46MML Command Format 3-48Man Page Format 3-48

Creating a Duplicate Concerned Point Code 3-48MML Command Format 3-50Man Page Format 3-50

vi SINAP/SS7 User’s Guide R8051-17

Creating a Remote Subsystem Number 3-50MML Command Format 3-51Man Page Format 3-51

Creating a Fictitious Originating Point Code 3-51MML Command Format 3-53Man Page Format 3-53

Creating a Global Title Translation (GTT) Entry for a Node 3-53Global Title Format 3-54Alternate SCCP Routing 3-56Using Hexadecimal Values in GTT Strings 3-58Steps to Create a GTT Entry 3-58MML Command Format 3-64Man Page Format 3-65

Enabling Partial Global Title Translations (all Variants) 3-65Configuring Network Components 3-67

Configuring a Link 3-68MML Command Format 3-70Man Page Format 3-70

Configuring a Link Set 3-70MML Command Format 3-72Man Page Format 3-72

Configuring a Route Set 3-72MML Command Format 3-74Man Page Format 3-74

Initializing Route Sets with a Prohibited Status (CCITT only) 3-74Enabling the Prohibited Route Set Status Feature 3-75

Initializing Remote SSNs in the Prohibited State (CCITT only) 3-75Configuring Load Control Parameters for a TCAP Application 3-76

How Load Control Processes Messages 3-77Load Control Persistence 3-77

Considerations for Implementing Load Control 3-77Issuing Load Control MML Commands 3-78Configuring Load Control Functionality 3-82


Configuring Multiple Link Congestion Levels 3-88Variant Differences 3-88Congestion States 3-88Implementing CCITT and China Multiple Link Congestion Functionality 3-89Measuring Congestion 3-92

Displaying Link Congestion Information 3-93Notifying the Application of Congestion 3-94Congestion Notification Options 3-95Link Congestion Thresholds 3-95

Contents vii

Contents

The MTP Restart Process 3-96MTP Restart Processing Overview 3-97Enabling MTP Restart Functionality 3-98

MTP Restart Processing for CCITT and China Variants 3-98MTP Restart Processing for the ANSI Variant 3-99Message Processing During MTP Restart 3-100Performing MTP Restart on a SINAP Node 3-100Performing MTP Restart on an Adjacent Node 3-102Displaying MTP Restart System Information 3-103Completing MTP Restart 3-105

MTP Time-Controlled Changeover 3-105Overview of MTP TCCO Processing 3-106

Short-Term Processor Outage 3-106Long-Term Processor Outage 3-106

Implementing the TCCO Feature 3-106MTP Time-Controlled Diversion 3-107

Implementing TCD in the ANSI Network Variant 3-108Disabling MTP Level 3 Point Code Discrimination (CCITT) 3-108MTP Eight-bit SLS Processing 3-109

Determining Which SLS Processing Scheme to Use 3-109Determining a Local Processor Outage Condition 3-110Connection-Oriented Services 3-111

The Stages of Connection-Oriented Communication 3-112Activating Connection-Oriented Services 3-112

Defining ISDN User Part (ISUP) Functionality 3-113Handling SNM Messages with Nonzero SLCs 3-113Enabling Random SLS Generation 3-114

Random Link Selection 3-114Defining UPU Messages 3-115Defining XUDT and XUDTS Messages 3-116

XUDT MSU Segment Sizes 3-117Validating the XUDT Message Segment Size 3-118Enabling Processing of Subsystem Status Tests in XUDT Messages 3-118Setting the Hop Counter in Incoming XUDT Messages 3-1191996 ITU-T SCCP XUDT/XUDTS Importance Parameter Support 3-119

Enabling Loopback Detection (CCITT) 3-120Enabling Transfer-Restricted Message Handling 3-120

RSR/RSP in Response to TFR/TFP 3-121Configuring Alarm Messages to Write to the System Log Files 3-122

Operating Systems Error Log Files 3-122The Alarm Severity Level Environment Variable 3-123

4. System Operation and Maintenance 4-1

viii SINAP/SS7 User’s Guide R8051-17

Displaying Information for Network Components 4-1Displaying Link Information 4-3

Menu Selection Mode 4-4MML Command Format 4-4Man Page Format 4-4Sample Display 4-5

Displaying Link Set Information 4-7Menu Selection Mode 4-7MML Command Format 4-7Man Page Format 4-7Sample Display 4-8

Displaying Combined Link Set Information 4-8Menu Selection Mode 4-8MML Command Format 4-8Man Page Format 4-9Sample Display 4-9

Displaying Route Set Information 4-10Menu Selection Mode 4-10MML Command Format 4-10Man Page Format 4-11Sample Displays 4-11Sample Displays 4-11

Displaying Own Point Code Information 4-14Menu Selection Mode 4-14MML Command Format 4-14Man Page Format 4-14Sample Display 4-14

Displaying Concerned Point Codes 4-15Menu Selection Mode 4-15MML Command Format 4-15Man Page Format 4-16Sample Display 4-16

Displaying Fictitious Originating Point Code Information 4-17Menu Selection Mode 4-17MML Command Format 4-17Man Page Format 4-18

Displaying Remote SSNs for a Remote Point Code 4-18Menu Selection Mode 4-18MML Command Format 4-18Man Page Format 4-18Sample Display 4-18

Displaying the MTP and SCCP System Tables 4-19Menu Selection Mode 4-19MML Command Format 4-20Man Page Format 4-20

Contents ix

Contents

Sample Displays 4-21Displaying Global Titles for a Node 4-26


Displaying Signaling Link Selection Assignments for an Application 4-28Displaying Local Subsystem Numbers (SSNs) Status 4-30


Changing Network Components 4-32Changing a Link 4-33


Changing a Link Set 4-34Menu Selection Mode 4-35MML Command Format 4-35Man Page Format 4-35

Changing the Route Set 4-35Menu Selection Mode 4-36MML Command Format 4-36Man Page Format 4-37

Changing a Concerned Point Code 4-37Menu Selection Mode 4-37MML Command Format 4-38Man Page Format 4-38

Changing the Duplicate Concerned Point Code Number 4-38Menu Selection Mode 4-38MML Command Format 4-39Man Page Format 4-39

Adding and Deleting a Remote Subsystem for a Point Code 4-39Menu Selection Mode 4-39MML Command Format 4-39Man Page Format 4-40

Changing Timers and Link Congestion Threshold Settings 4-40Menu Selection Mode 4-40MML Command Format 4-40Man Page Format 4-42

Changing the GTT Entries for a Node 4-42Menu Selection Mode 4-42MML Command Format 4-42

x SINAP/SS7 User’s Guide R8051-17

Man Page Format 4-46Change SLS Processing Scheme 4-47


Adding and Deleting Links Dynamically 4-47Deleting Network Components 4-47

Deleting Links Dynamically 4-49Deleting a Link From a Link Set 4-50


Deleting a Link Set 4-50Menu Selection Mode 4-50MML Command Format 4-50Man Page Format 4-50

Deleting a Combined Link Set 4-50Menu Selection Mode 4-51MML Command Format 4-51Man Page Format 4-51

Deleting a Route Set 4-51Menu Selection Mode 4-51MML Command Format 4-51Man Page Format 4-51

Deleting an Own Point Code 4-51Menu Selection Mode 4-52MML Command Format 4-52Man Page Format 4-52

Deleting a Concerned Point Code (CPC) 4-52Menu Selection Mode 4-52MML Command Format 4-52Man Page Format 4-52Menu Selection Mode 4-53MML Command Format 4-53Man Page Format 4-53

Deleting a Fictitious Originating Point Code 4-53Menu Selection Mode 4-53MML Command Format 4-53Man Page Format 4-54

Deleting all Subsystems at a Remote Node 4-54Menu Selection Mode 4-54MML Command Format 4-54Man Page Format 4-54

Deleting a GTT Entry for a Node 4-54Menu Selection Mode 4-54

Contents xi

Contents


Removing a Link, Link Set, or Route Set from Service 4-57Putting a New Link into Service 4-57Handling SINAP/SS7 Measurements 4-58

Reporting Measurement Considerations 4-61Saving the Report to a File and Printing It 4-62Reporting MTP Measurements 4-62

Linkset Measurements 4-62Menu Selection Mode 4-63MML Command Format 4-63Man Page Format 4-65Sample Reports 4-65

Reporting SCCP Measurements 4-65Menu Selection Mode 4-65MML Command Format 4-66Man Page Format 4-67Sample Report 4-67

Reporting TCAP Measurements 4-67Menu Selection Mode 4-67MML Command Format 4-67Man Page Format 4-68Sample Report 4-69

Reporting Measurements for All MTP, SCCP, and TCAP Subsystems 4-69

Linkset Measurements 4-69Menu Selection Mode 4-70MML Command Format 4-70Man Page Format 4-71Sample Report 4-72

Retrieving Oldest 15- or 30-Minute Node Measurements 4-73Linkset Measurements 4-73Menu Selection Mode 4-74MML Command Format 4-74Sample Report 4-75Man Page Format 4-77

Displaying Latest 5-Minute Node Network Management Measurements 4-77

Menu Selection Mode 4-77MML Command Format 4-77Sample Report 4-77Man Page Format 4-78

Starting On-Demand Measurements 4-78Menu Selection Mode 4-78MML Command Format 4-78

xii SINAP/SS7 User’s Guide R8051-17

Man Page Format 4-78Sample Output 4-79

Stopping On-Demand Measurements 4-80Menu Selection Mode 4-80MML Command Format 4-80Man Page Format 4-80

Start Writing Measurements to the Measurement Log File 4-80Menu Selection Mode 4-80MML Command Format 4-80Man Page Format 4-80

Stop Writing Measurements to the Measurement Log File 4-81Menu Selection Mode 4-81MML Command Format 4-81Man Page Format 4-81

Dumping MTP Routing and Management Tables to the Static Table File 4-81

Menu Selection Mode 4-81MML Command Format 4-81Sample Output 4-82Man Page Format 4-82

Backing Up Databases 4-82Backing Up the Node Static Database 4-82


Backing Up an Application to Disk or Tape 4-83Menu Selection Mode 4-83MML Command Format 4-83Man Page Format 4-83

Displaying the Number of Days in the Backup Cycle 4-83Menu Selection Mode 4-83MML Command Format 4-83Sample Display 4-84Man Page Format 4-84

Changing the Interval for Automatic Node Backup 4-84Menu Selection Mode 4-84MML Command Format 4-84Man Page Format 4-84

Restoring Databases 4-84Restoring the Node Static Database from Disk 4-85


Restoring an Application Static Database from Disk or Tape 4-86Menu Selection Mode 4-86

Contents xiii

Contents


Using the rclog File to Restore an Existing Database Configuration 4-87

Purging and Deleting Files 4-87Displaying the Number of Days in the Purge Cycle for All Log Files 4-88


Changing the Interval for Purging Log Files 4-90Menu Selection mode 4-90MML Command Format 4-90Man Page Format 4-91

Deleting a File from Disk 4-91Menu Selection Mode 4-91MML Command Format 4-91Man Page Format 4-91

Using the BITE Monitor 4-92BITE Limitations 4-92Default Log Size and Location 4-92Starting the BITE Monitor 4-93


Displaying Monitor IDs 4-96Menu Selection Mode 4-96MML Command Format 4-96Man Page Format 4-96Sample Display 4-97

Stopping the BITE Monitor 4-97Menu Selection Mode 4-98MML Command Format 4-98Man Page Format 4-98

Reconfiguring bitu to Run in the Real-Time or the Time-Share Mode 4-98

Implementing Signaling Link Test Messages 4-99Sending a Signaling Link Test Message to a Link 4-99


Enabling Automatic Periodic Link Testing 4-100Accessing SLT and SRT Timers 4-101

xiv SINAP/SS7 User’s Guide R8051-17

Enabling Periodic Link Testing 4-103Disabling Automatic Periodic Link Testing 4-105

Using the Load Control Facility 4-105Enabling Load Controls for an Application 4-106

Menu Selection Mode 4-108MML Command Format 4-108Man Page Format 4-109Sample Command Usage 4-109

Invoking Load Controls for an Application 4-109Menu Selection Mode 4-110MML Command Format 4-110Man Page Format 4-111Example Command Usage 4-111

Displaying Load Control Statistics for an Application 4-112Menu Selection Mode 4-114MML Command Format 4-114Man Page Format 4-115Sample Command Usage 4-115

Disabling Load Controls for an Application 4-115Menu Selection Mode 4-118MML Command Format 4-118Man Page Format 4-119Sample Command Usage 4-119

Deactivating Load Controls for an Application 4-119Menu Selection Mode 4-120MML Command Format 4-120Man Page Format 4-121Sample Command Usage 4-121

Maintaining Connection-Oriented Services 4-121Maintaining Information on Active Connections 4-122

Checking LRM and LRN Status 4-122Inactive Connections and Releasing LRNs 4-124UNIX Command Format 4-124Sample Usage 4-125Displaying and Changing Connection-Oriented Timers 4-126

Downloading Link Configuration Changes in the /etc/SS7links File 4-128

5. Alarms, Events, and Error Messages 5-1Alarm Format 5-2Alarm Notification and Severity 5-2Alarms and Software Notebook Events 5-3

Displaying Alarm History Log Entries 5-3Menu Selection Mode 5-3

Contents xv

Contents

MML Command Format 5-3Man Page Format 5-4Sample Display 5-5

Node Management Software Notebook Events and Messages 5-5Displaying Software Notebook Log Entries 5-6


MTP Alarms 5-8Nondata Primitives 5-8

System Log File 5-8Normal Messages Written to the System Log File 5-8Abnormal Messages Written to the System Log File 5-8Default Messages 5-9

Handling Events 5-10Setting Up the Trouble Treatment Table 5-11Adding an Event or Changing Its Treatment 5-16

Using the I_TROUBLE_NOT IPC Alarm Fields 5-16Trouble Management Events 5-18

User-Supplied Error Messages and Events 5-19

6. Troubleshooting 6-1Basic Troubleshooting Guidelines 6-1Verifying Physical and Logical Board Assignments 6-1Verifying All Processes Are Running 6-2

Using the sy Utility for Troubleshooting 6-2Using gathersy for Troubleshooting 6-3Checking Link Status 6-3

Menu Selection Mode 6-3MML Command Format 6-4

Checking Link Set Status 6-7Menu Selection Mode 6-7MML Command Format 6-7

Checking Route Set Status 6-8Menu Selection Mode 6-8MML Command Format 6-9

Checking the Accessibility of a Remote SSN 6-10Checking the Availability of a Local SSN 6-11

Menu Selection Mode 6-11MML Command Format 6-11

Checking the Status of the Application 6-12Using the BITE Subsystem 6-14

Initiating BITE Monitors 6-16

xvi SINAP/SS7 User’s Guide R8051-17

Starting the BITE Log Analysis Program 6-16Menu Selection Mode 6-17MML Command Format 6-17

Using Log Analysis Commands 6-18Relational Operators and Keywords 6-18Displaying and Analyzing a Log File Trace Dump (DISPLAY Com-mand) 6-21Finding Records that Fit All Specified Criteria (FIND Command) 6-28Selecting Records That Satisfy Any Specified Condition (SELECT Command) 6-29Obtaining Summary Count of Records Matching Specified Criteria (SUMMARY Command) 6-30

Exiting the Log Analysis Program 6-31

Appendix A. Network Information and Planning Forms A-1

Appendix B. SINAP/SS7 Environment Variables B-1Defining SINAP/SS7 Environment Variables B-1

Enabling Environment Variables B-1Disabling Environment Variables B-2

The SINAP Environment File B-2sinap_env_var.sh (for Bourne Shell) B-2

Appendix C. SINAP/SS7 MML Command Summary C-1

Appendix D. CCITT Configuration Parameters D-1Configuration Limitations D-2CCITT Point Code Formats D-2MTP Timers and Thresholds D-2SCCP Timers D-4

SCCP Extended Unitdata (XUDT) Message Timers D-5SCCP Connection-Oriented Timers D-5

MTP Restart D-6MTP Time-Controlled Changeover D-8Time-Controlled Diversion (TCD) D-8

Contents xvii

Contents

Appendix E. ANSI Configuration Parameters E-1Configuration Limitations E-1ANSI Point Code Formats E-2

Network, Cluster, and Member Routing E-2Remote SSNs E-3Route Sets E-4Dynamic Route Provisioning E-4

MTP Timers and Thresholds E-5SCCP Timers E-8Combined Link Sets E-8Fictitious Originating Point Codes (FOPCs) E-9MTP Restart E-10MTP Time-Controlled Changeover E-10MTP Time-Controlled Diversion (TCD) E-11MTP Eight-bit SLS Processing E-11ISUP Services Feature E-12

Activating the ISUP Services Feature E-12

Appendix F. TTC Configuration Parameters F-1Configuration Limitations F-1Point Code Formats F-1Timers and Thresholds F-2

Link Testing F-3Route Testing F-3

Time-Controlled Changeover (TCCO) F-4MTP Time-Controlled Diversion F-4Activating and Deactivating TTC Applications F-4Differences in TTC and CCITT Network Variants F-5Unsupported SINAP/SS7 Administrative Features F-6

Appendix G. NTT Configuration Parameters G-1Configuration Limitations G-2NTT Point Code Format G-2Creation of Own Point Code G-3Timers and Thresholds G-4Link Congestion Thresholds G-5

Link Testing G-6Setting SLS Bits in the MSU Routing Label G-6Link Set and Route Statuses G-7Time-Controlled Changeover (TCCO) G-8

xviii SINAP/SS7 User’s Guide R8051-17

MTP Time-Controlled Diversion G-8Activating and Deactivating NTT Applications G-8Activating the NTT Version of ISUP Services G-9Differences in NTT, TTC, and CCITT Network Variants G-10

Appendix H. China Configuration Parameters H-1Configuration Limitations H-2China Point Code Formats H-2MTP Timers and Thresholds H-3SCCP Timers H-6

SCCP Extended Unitdata (XUDT) Message Timers H-6Required Environment Variables H-7MTP Restart H-7MTP Time-Controlled Changeover H-8MTP Time-Controlled Diversion H-9Activation of China ISUP Services H-9Unsupported SINAP/SS7 Features H-9

Appendix I. List of Alarm and Event Messages I-1SINAP/SS7 Alarms I-2Alarms and Events: Category NM_EVENT I-3Alarms and Events: Category BI_EVENT I-11Alarms and Events: Category SC_EVENT I-12Alarms and Events: Category L3_EVENT I-15Alarms and Events: Category DR_EVENT I-31Alarms and Events: Category CA_EVENT I-34Alarms and Events: Category BK_EVENT I-41Alarms and Events: Category GW_EVENT I-42Terminal Handler Errors I-47Terminal Handler Alarms I-48Load Control UNIX Error Messages I-84

I-84

Contents xix

Contents

xx SINAP/SS7 User’s Guide R8051-17

Figures

Figure 2-1. The start_sinap Script File 2-4Figure 2-2. The startappl Script File 2-13Figure 2-3. SINAP/SS7 Menu Hierarchy 2-17Figure 2-4. Sample MML Command Log File 2-23Figure 2-5. Sample Configuration Script Files 2-24Figure 2-6. Output from the display process version Command 2-28Figure 2-7. The stop_sinap Script File 2-35Figure 3-1. Menu Organization for Sample Menu Definition File 3-18Figure 3-2. SINAP/SS7 Terminal Screen Partitions 3-24Figure 3-3. Screen Layout for a Specific Command 3-25Figure 3-4. Sample Network Configuration for National Network 0 3-27Figure 3-5. Commands for Creating the Sample Configuration 3-28Figure 3-6. SINAP System Main Menu 3-29Figure 3-7. Network Commands Menu 3-29Figure 3-8. Create Commands Menu for CCITT and China Variants 3-30Figure 3-9. Create Commands Menu for the ANSI Variant 3-30Figure 3-10. Create Commands Menu for the TTC and NTT Variants 3-31Figure 3-11. Network Commands Menu 3-68Figure 3-12. Configure Commands Menu 3-68Figure 3-13. Stages of Load Control 3-81Figure 4-1. Display Commands Menu for CCITT and China Variants 4-2Figure 4-2. Display Commands Menu for the ANSI Variant 4-2Figure 4-3. Display Commands Menu for the TTC and NTT Variants 4-3Figure 4-4. Sample DISPLAY-LINK Screen Without Loopback Status 4-5Figure 4-5. Sample DISPLAY-LINK Screen With Loopback Status 4-6Figure 4-6. Sample #L3,port Command Output 4-6Figure 4-7. Sample DISPLAY-LSET Command Output 4-8Figure 4-8. Sample DISPLAY-CLSET Command Output 4-9Figure 4-9. Sample DISPLAY-RSET Command Output for CCITT 4-11Figure 4-10. Alternate Sample DISPLAY-RSET Command Output for CCITT 4-12Figure 4-11. Sample DISPLAY-RSET Command Output for ANSI 4-13Figure 4-12. Sample DISPLAY-OSP Command Output 4-15Figure 4-13. Sample DISPLAY-CPC Command Output 4-17Figure 4-14. Sample DISPLAY-REMSSN Command Output 4-19Figure 4-15. Sample Output: Level-2 MTP Timers 4-21Figure 4-16. Sample Output: Level-3 MTP Timers 4-22Figure 4-17. Sample Output: MTP Thresholds 4-22Figure 4-18. Sample Output: SCCP Timers 4-23Figure 4-19. Sample Output: ISUP Timers 4-24

Figures xxi

Figures

Figure 4-20. Sample Output: SCCP SCOC Timers 4-25Figure 4-21. Sample Output: SLT Timers 4-25Figure 4-22. Sample Output: SRT Timers 4-25Figure 4-23. Sample DISPLAY-GTT Command Output 4-27Figure 4-24. Sample #STA,gtt Command Output 4-28Figure 4-25. Sample DISPLAY-SUBSYSTEM Command Output 4-31Figure 4-26. Change Commands Menu for the CCITT/China Variants 4-32Figure 4-27. Change Commands Menu for the ANSI Variant 4-32Figure 4-28. Change Commands Menu for the TTC and NTT Variants 4-33Figure 4-29. Delete Commands Menu for the CCITT/China Variants 4-48Figure 4-30. Delete Commands Menu for the ANSI Variant 4-48Figure 4-31. Delete Commands Menu for the TTC and NTT Variants 4-49Figure 4-32. Measurements Commands Menu 4-59Figure 4-33. Report Measurements Menu 4-60Figure 4-34. Report Sample Screen 4-60Figure 4-35. Sample REPORT-MMTP Output Display 4-65Figure 4-36. Sample REPORT-MSCCP Output Display 4-67Figure 4-37. Sample REPORT-MTCAP Output Display 4-69Figure 4-38. Sample REPORT-MALL Output Display 4-72Figure 4-39. Retrieve Measurements Menu 4-74Figure 4-40. Sample RETRIEVE-NOM Command Output 4-76Figure 4-41. Sample 5-Minute Management Report 4-77Figure 4-42. Enable/Disable Measurements Command Menu 4-78Figure 4-43. Sample START-MEASURE Command Output 4-79Figure 4-44. Sample DUMP-TABLE Command Output 4-82Figure 4-45. Sample DISPLAY-BACKUP Command Output 4-84Figure 4-46. Display Backup or Log Purge Day Menu 4-88Figure 4-47. Sample DISPLAY-PURGEDAY Command Output 4-89Figure 4-48. Change Backup or Log Purge Day Menu 4-90Figure 4-49. BITE Monitor Commands Menu 4-93Figure 4-50. Sample START-MON Command Output 4-95Figure 4-51. Sample DISPLAY-MON Command Output 4-97Figure 4-52. Sample SINAP/SS7 Terminal Handler MML Command Screen 4-102Figure 4-53. Sample Screen Output for Enabled Periodic Link Testing 4-104Figure 4-54. Load Control Commands Menu 4-108Figure 4-55. Sample DISPLAY-LOAD-CONTROL Command Output 4-112Figure 4-56. Sample #sc,lrm Command Output 4-122Figure 4-57. Sample #sc,lrn Command Output 4-123Figure 4-58. Sample #sc.lrn,1 Command Output 4-123Figure 4-59. Sample release_lrn Command Output 4-125Figure 4-60. Sample release_lrn 25 Command Output 4-126Figure 5-1. Sample Alarm Format 5-2Figure 5-2. Sample treat.tab File 5-15Figure 6-1. DISPLAY-LINK Command Sample 6-4Figure 6-2. DISPLAY-LSET Command Sample 6-7

xxii SINAP/SS7 User’s Guide R8051-17

Figure 6-3. #13,lst sy Command Displaying Link Set Status 6-8Figure 6-4. DISPLAY-RSET Command Sample 6-9Figure 6-5. #13,lst sy Command Displaying Route Set Status 6-10Figure 6-6. #sc,ssn sy Command Sample 6-10Figure 6-7. DISPLAY-SUBSYSTEM Command Displaying Local SSN 6-11Figure 6-8. DISPLAY-SUBSYSTEM Command 6-12Figure 6-9. Displaying All Registered Processes 6-13Figure 6-10. Displaying Application Information 6-14Figure 6-11. BITE Trace Points 6-15Figure 6-12. Log Analysis Menu 6-17Figure 6-13. BITE Log Analysis Command Sample 6-22Figure 6-14. Sample IPC Data Record 6-22Figure 6-15. Display Log Record File Sample 6-24Figure 6-16. MSU Data Record Sample 6-25Figure 6-17. Sample BITE Log for Inactivity Test Message 6-26Figure 6-18. Sample BITE Log for Data Acknowledgment Message 6-27Figure 6-19. Sample FIND Command Argument 6-28Figure 6-20. Sample SELECT Command Argument 6-29Figure 6-21. Sample SUMMARY Command Argument 6-30Figure H-1. China Point Codes in Relationship to ANSI Point Codes H-3

Figures xxiii

Figures

xxiv SINAP/SS7 User’s Guide R8051-17

Tables

Table 0-1. Worldwide CAC Telephone Numbers xxxvTable 2-1. Start-Up Commands for SINAP/SS7 2-3Table 2-2. start_sinap Script Command Tasks 2-9Table 2-3. Terminal Handler Keyboard Shortcuts 2-20Table 2-4. send_cm Command Formats 2-22Table 2-5. man Command Arguments 2-25Table 2-6. SINAP/SS7 Process Labels 2-26Table 2-7. static2mml Command Arguments 2-31Table 2-8. stop_sinap Command Options 2-33Table 2-9. stop_sinap Script Commands 2-37Table 3-1. Configuration Requirements and Limitations 3-1Table 3-2. Menu Definition Operators 3-12Table 3-3. Description of Line Fields for Command Screens 3-25Table 3-4. CREATE-OSP Command Arguments 3-32Table 3-5. CREATE-LSET Command Arguments 3-35Table 3-6. CREATE-CLSET Command Arguments 3-38Table 3-7. CREATE-LINK Command Arguments 3-39Table 3-8. CREATE-RSET Command Arguments 3-45Table 3-9. CREATE-CPC Command Arguments 3-47Table 3-10. CREATE-DUCPC Command Arguments 3-49Table 3-11. CREATE-REMSSN Command Arguments 3-50Table 3-12. Global Title Address Components 3-55Table 3-13. GTI Values and Global Title Formats 3-55Table 3-14. CREATE-GTT Command Arguments 3-60Table 3-15. CONFIGURE-LINK Command Arguments 3-69Table 3-16. CONFIGURE-LSET Command Arguments 3-71Table 3-17. CONFIGURE-RSET Command Arguments 3-73Table 3-18. Load Control MML Commands 3-79Table 3-19. SETUP-LOAD-CONTROL Command Format 3-83Table 3-20. Environment Variables for CCITT and China Link Congestion 3-90Table 3-21. Congestion Thresholds 3-96Table 3-22. MTP Restart Timers 3-103Table 3-23. SLS Processing Scheme 3-109Table 3-24. Environment Variables for LRNs 3-112Table 3-25. New Unavailability-Cause Values for UPU Messages 3-115Table 3-26. Alarm Severity Levels 3-123

Tables xxv

Tables

Table 4-1. DISPLAY-LINK Command Arguments 4-4Table 4-2. DISPLAY-LSET Command Arguments 4-7Table 4-3. DISPLAY-CLSET Command Arguments 4-9Table 4-4. DISPLAY-RSET Command Arguments 4-10Table 4-5. DISPLAY-CPC Command Arguments 4-16Table 4-6. DISPLAY-REMSSN Command Arguments 4-18Table 4-7. DISPLAY-SYSTAB Command Arguments 4-20Table 4-8. SLD Command Formats 4-29Table 4-9. DISPLAY-SUBSYSTEM Command Arguments 4-31Table 4-10. CHANGE-LINK Command Arguments 4-34Table 4-11. CHANGE-LSET Command Arguments 4-35Table 4-12. CHANGE-RSET Command Arguments 4-37Table 4-13. CHANGE-CPC Command Arguments 4-38Table 4-14. CHANGE-DUCPC Command Arguments 4-39Table 4-15. CHANGE-REMSSN Command Arguments 4-40Table 4-16. CHANGE-SYSTAB Command Arguments 4-41Table 4-17. CHANGE-GTT Command Arguments 4-44Table 4-18. DELETE-GTT Command Arguments 4-55Table 4-19. REPORT-MMTP Command Arguments 4-63Table 4-20. REPORT-MSCCP Command Arguments 4-66Table 4-21. REPORT-MTCAP Command Arguments 4-68Table 4-22. REPORT-MALL Command Arguments 4-70Table 4-23. BACKUP-APPL Command Arguments 4-83Table 4-24. RESTORE-NODE Command Arguments 4-86Table 4-25. RESTORE-APPL Command Arguments 4-87Table 4-26. Log Type Descriptions 4-89Table 4-27. CHANGE-PURGEDAY Command Arguments 4-91Table 4-28. START-MON Command Arguments 4-94Table 4-29. Displayed Data Fields for the START-MON Command 4-96Table 4-30. -c and -p Options for bitu 4-99Table 4-31. Link Testing Timer Default Values 4-103Table 4-32. ENABLE-LOAD-CONTROL Command Arguments 4-108Table 4-33. INVOKE-LOAD-CONTROL Command Arguments 4-110Table 4-34. Column Information for Load Control Applications 4-113Table 4-35. DISPLAY-LOAD-CONTROL Command Arguments 4-114Table 4-36. DISABLE-LOAD-CONTROL Command Arguments 4-118Table 4-37. EXIT-LOAD-CONTROL Command Arguments 4-120Table 4-38. SCCP Connection-Oriented Timers 4-126Table 5-1. errno Values 5-3Table 5-2. REPORT-ALARM Command Arguments 5-4Table 5-3. REPORT-NBOOK Command Arguments 5-7Table 5-4. MTP Alarms 5-8

xxvi SINAP/SS7 User’s Guide R8051-17

Table 5-5. Treatment Table File Parameters 5-12Table 5-6. I_TROUBLE_NOT_IPC Data Fields and Descriptions 5-17Table 6-1. Relational Operators 6-18Table 6-2. Keywords for Searching Log File Records 6-19Table 6-3. FIND Command Arguments 6-28Table 6-4. SELECT Command Arguments 6-29Table 6-5. SUMMARY Command Arguments 6-30Table C-1. MML Command Summary C-1Table D-1. MTP Level-2 Timers (Q.701 – Q.704 Bluebook) D-2Table D-2. MTP Level-3 Timers (Q.701 – Q.704 Bluebook) D-3Table D-3. MTP Thresholds D-3Table D-4. SCCP Timers D-4Table D-5. SCCP Connection-Oriented Timers D-6Table E-1. MTP Level-2 Timers (ANSI Recommendation T1.111.3) E-5Table E-2. MTP Level-3 Timers (ANSI Recommendation T1.111.4) E-6Table E-3. MTP Thresholds (ANSI Recommendation T1.111.4) E-7Table E-4. SCCP Timers (ANSI Recommendation T1.112.4) E-8Table E-5. MML Commands for FOPC E-9Table F-1. CCITT Timers Not Supported by TTC F-2Table F-2. CCITT Timers Assigned Default Values in TTC F-2Table F-3. TTC Timer Default Settings F-3Table G-1. CCITT Timers Not Supported by NTT G-4Table G-2. CCITT Timers Assigned Default Values in NTT G-4Table G-3. Display Routeset Screen Status Descriptions G-7Table H-1. MTP Level-2 Timers (Q.701 – Q.704 Bluebook) H-4Table H-2. MTP Level-3 Timers (Q.701 – Q.704 Bluebook) H-4Table H-3. MTP Thresholds H-5Table H-4. SCCP Timers (Q.714 Bluebook) H-6Table I-1. Event Categories Generating Alarms I-2Table I-2. Alarm Formats I-3Table I-3. Alarm Formats I-48

Tables xxvii

Tables

xxviii SINAP/SS7 User’s Guide R8051-17

Preface

The SINAP/SS7 User’s Guide (R8051) documents the Stratus Intelligent Network Applications Platform (SINAP) SS7 product. The guide describes the functional capabilities of the SINAP system and contains procedures for configuring, operating, maintaining, and troubleshooting the system. It also includes information for the variants of the SINAP/SS7 system that adhere to standards set by the following:

• International Telecommunications Institute Standards Division (ITU-T) (formerly known as the Consultative Committee on International Telegraphy and Telephony [CCITT])

• American National Standards Institute (ANSI)

• Telecommunications Technology Committee (TTC) of Japan

• China (adhering to standards set by the People’s Republic of China and ITU-T)

Although CCITT has been renamed ITU and its standards are referred to as ITU-T Recommendations, SINAP/SS7 documentation continues to refer to the standards as CCITT standards to ensure continuity with the software.

Sample data included in examples, screens, and reports throughout this manual generally reflect the CCITT network variant of the SINAP/SS7 system. See the appropriate appendix within this manual for information on specific configuration parameters for ANSI, TTC, and China network variants. For information on designing and developing an application to run under the SINAP/SS7 system, see the SINAP/SS7 Programmer’s Guide (R8052).

AudienceThis manual is intended for system administrators, operators, and other personnel responsible for the configuration, operation, and maintenance of the SINAP/SS7 system. This manual assumes the reader has a good working knowledge of the SS7 protocol and the UNIX operating system and utilities.

Revision InformationThis manual has been revised with miscellaneous corrections to existing text for the SINAP/SS7 14.2 release, and the enhancement of Partial GTT support for ANSI, China, and TTC variants (ss7-2684). In addition the following documentation bugs were fixed: ss7doc-103, ss7doc-105, and ss7doc-107.

Preface xxix

Manual Organization

Manual OrganizationThis manual is divided into the following chapters and appendixes. The manual also contains an index.

Chapter 1, ‘‘Introduction,” provides a brief overview of the product and the manual. It describes the terminology used in this document.

Chapter 2, ‘‘Performing Basic Tasks,” describes how to perform such basic tasks as starting and stopping SINAP/SS7 and application processes, accessing the user interface, and configuring the SINAP/SS7 software using script files.

Chapter 3, ‘‘Software Configuration,” provides procedural information on configuring the individual components of the SINAP/SS7 system.

Chapter 4, ‘‘System Operation and Maintenance,” describes procedures for operating and maintaining the system.

Chapter 5, ‘‘Alarms, Events, and Error Messages,” contains the format of system alarm messages and provides information on the SINAP/SS7 trouble treatment table and the alarm and event log files.

Chapter 6, ‘‘Troubleshooting,” describes procedures for identifying, isolating, and resolving problems that might occur during system operation.

Appendix A, ‘‘Network Information and Planning Forms,” contains blank planning forms you can photocopy and use as required in planning and designing your SINAP/SS7 configuration.

Appendix B, ‘‘SINAP/SS7 Environment Variables,” lists and describes variables you define to activate or establish operating characteristics for various SINAP/SS7 features.

Appendix C, ‘‘SINAP/SS7 MML Command Summary,” lists and describes all SINAP/SS7 MML commands. The chart includes a brief description of each command, the command format, and the alternate and man page format.

Appendix D, ‘‘CCITT Configuration Parameters,” provides information on configuring parameters specific to the CCITT network variant of the SINAP/SS7 system.

Appendix E, ‘‘ANSI Configuration Parameters,” provides information on configuring parameters that are specific to the ANSI network variant of the SINAP/SS7 system.

Appendix F, ‘‘TTC Configuration Parameters,” provides information on configuring parameters specific to the Japanese TTC network variant of the SINAP/SS7 system.

Appendix G, ‘‘NTT Configuration Parameters,” contains information on configuring parameters specific to the Japanese NTT network variant of the SINAP/SS7 system.

xxx SINAP/SS7 User’s Guide R8051-17

Notation Conventions

Appendix H, ‘‘China Configuration Parameters,” provides information on configuring parameters specific to the Chinese network variant of the SINAP/SS7 system.

Appendix I, ‘‘List of Alarm and Event Messages,” lists and describes all SINAP/SS7 and UNIX alarm and event messages along with recommended actions to take to recover from the errors.

Notation ConventionsThis manual uses the following notation conventions.

• Monospace represents text that would appear on your display screen (such as commands, functions, code fragments, and names of files and directories). For example:

The alternative format for change-remssn is change-remssn.

• Monospace italic represents terms to be replaced by literal values. In the following example, the user must replace the monospace-italic term with a literal value. For example:

The nmtr program has the following syntax (where filename is the name of the file to be converted).

• Monospace bold represents user input in examples and figures that contain both user input and system output (which appears in monospace). For example:

• Italics introduces or defines new terms. For example:

The Terminal Handler accepts commands in Man-Machine Language (MML).

• Boldface emphasizes words in text. For example:

You must create a link set before you provision its member links.

• When you need to press a key on the keyboard to perform an action, the keys are indicated in SMALL CAPS, for example:

Press CTRL P to go to the next page or RETURN to exit the screen.

MML as built is CREATE-CPC:Specify local subsystem number: LSSN=253LSSN=253Specify point codes for the remote node:(pc# or pc#1&pc#2... up to pc#10)RPC=3003LSSN=253,RPC=3003

Preface xxxi

Syntax Notation

N O T EThere is an implied pressing of RETURN at the end of each command and menu response that you enter.

• The dollar sign ($) and the number sign (#) are standard default prompt signs that have a specific meaning at the UNIX 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.

• When the full path name of a command appears in an example (for example, /etc/fsck), you must enter the command exactly as it appears.

Syntax Notation This manual uses the format conventions for documenting commands as shown in the following example.

CREATE-REMSSN:PC=pc,SSN=ssn[&ssn];

The following chart explains the notation used in command formats.

Notation Meaning

< > Angled brackets enclose terms in a command line that you must replace with literal values pertinent to your own service. In the following example, you must type in the following command line and replace the generic “service“ with the name of your service:

mv slpi_<service> slpi_<service>.old

[ ] Square brackets enclose command argument choices that are optional. For example:

cflow [-r] [-ix] [-i] [-d num] files

xxxii SINAP/SS7 User’s Guide R8051-17

Related Manuals

Related ManualsRefer to the following Stratus manuals for related documentation.

• The SINAP Products Glossary (R8010) contains definitions for terms and acronyms used across the line of SINAP products.

• SINAP/SS7 Programmer’s Guide (R8052) provides information on designing and developing an application to run under the SINAP/SS7 system and also contains information on testing and debugging an application.

• SINAP/SS7 ISDN User Part (ISUP) Guide (R8053) provides information on designing and developing ISUP applications to run on the SINAP/SS7 system.

• The SINAP/MultiStack Technical Overview (R8055) contains an overview of the SINAP/SS7 product and lists the national and international standards to which the product complies.

• SINAP/SS7 Installation Guide (R8060) provides instructions for installing the SINAP/SS7 software on the HP-UX and the Solaris operating system.

• The SINAP/SNMP MIB Guide (R8065) for detailed information on SNMP application installation, configuration, and operation.

| The vertical bar separates mutually exclusive arguments from which you choose one. For example:

command [arg1 | arg2]

You may use either arg1 or arg2 when you issue the command.

... Ellipsis indicates that you can have many arguments on a single command line. For example,

command [arg1, arg2, arg3,...]

$ In sample commands, the dollar sign is sometimes used for the shell command prompt. Your system prompt might differ. Although a prompt is sometimes shown at the beginning of a command line as it would appear on your screen, you do not type it.

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.

Notation Meaning

Preface xxxiii

Contacting the CAC

A Note on the Contents of Stratus ManualsStratus manuals document subroutines and commands of the user interface. Any other commands and subroutines contained in the operating system are intended solely for use by Stratus personnel and are subject to change without warning.

Accessing DocumentationSINAP product documentation is provided on CD-ROM. You can request a documentation CD-ROM in either of the following ways:

• Call the CAC (see ‘‘Contacting the CAC”).

• If your system is connected to the Remote Service Network (RSN), add a call using the Site Call System (SCS). See the scsac(1) man page for more information.

When requesting a documentation CD-ROM, please specify the product and platform documentation you desire, as there are several documentation CD-ROMs available.

Commenting on the Documentation

To provide corrections and suggestions for improving this documentation, send email to [email protected]. If it is possible, please include the title and part number from the Notice page and the page numbers.

This information will assist Stratus Publications in making any needed changes to the documentation. Your assistance is most appreciated.

Contacting the CACIf you need assistance, contact your local systems engineer, or telephone the Stratus Customer Assistance Center (CAC) that services your area. If you cannot reach the center that services your area, contact the CAC in the United States.

Table 0-1 lists the CAC telephone numbers, all of which are available 24 x 7. For the most current list of CAC telephone numbers, see the following Web site: http://www.stratus.com/support/cac.

xxxiv SINAP/SS7 User’s Guide R8051-17

Contacting the CAC

* For the countries of Belgium, Denmark, Luxembourg, The Netherlands, Norway, and Sweden, you can also use the following toll-free number to call after hours: 00800-000-99999. Your call will be directed to Phoenix Support Coordination.

N O T E S1. The plus sign (+) indicates that an international

access code is required. The access code for

Table 0-1. Worldwide CAC Telephone Numbers

Customer Assistance Center (CAC) Telephone Numbers

North America, Central America, and South America

800-221-6588 (toll-free within USA or Canada)

800-828-8513 (toll-free within USA or Canada)

+1-978-461-7200 (Maynard, MA; for local and international direct)

+1-602-852-3200 (Phoenix, AZ; for local and international direct)

Australia 1800-025-046 (toll-free within Australia)

Belgium* +32 2-512-63-70 (Dutch language)

+32 2-512-77-06 (French language)

France +33 (0) 1-41-20-37-08

Germany +49 (0) 6196-472518

Hong Kong 800-900-938 (toll-free within Hong Kong)

Italy +39 02-467440-216

Japan 0120-725530

Mexico +52 55-5553-4792

The Netherlands* +31 (0) 346-582-112

New Zealand 0800-443-051 (toll-free within New Zealand)

People’s Republic of China

+86 139-010-39512 (Beijing)

+86 21-63877700 (Shanghai)

Singapore 1800-2727482 (toll-free within Singapore)

South Africa +27 11-2675-709

Spain +34 91-383-4294

United Kingdom +44 (0) 1784-246056

Preface xxxv

Contacting the CAC

international calls varies from country to country; in the United States, it is 011.

2. When you call from within the same country as the CAC office, be sure to include any necessary long distance or STD call prefix. If you use an international telephone number within the same country, you must replace the country code with the necessary prefix. For example, within the United States, callers dial 1-800-221-6588.

3. The telephone numbers in the preceding list are for CACs operated by Stratus. If you receive service from a distributor of Stratus products, contact your distributor for instructions about obtaining assistance.

xxxvi SINAP/SS7 User’s Guide R8051-17

Chapter 1 Introduction1-

The SINAP/SS7 User’s Guide (R8051) documents the SINAP/SS7 user interface and contains instructions on using the screens and reports to set up and maintain a SINAP/SS7 system. The manual contains troubleshooting guidelines to use in analyzing, isolating, and resolving problems. It also contains other reference material to assist administrators in configuring, operating, and maintaining the SINAP/SS7 system.

The SINAP/SS7 product is a network-services development and implementation platform. The SINAP/SS7 software provides the Signaling System Number 7 (SS7) communications protocol, along with tools to aid in the development, testing, and implementation of applications that provide network services in an SS7 network. SINAP/SS7 comes in two sizes. The SINAP (unistack) product supports a single SS7 node, while the MultiStack product provides the ability to run up to four SINAP nodes on a single Stratus system, where each node is a single instance of SINAP and is configured as a separate point code in the same network or in different networks.

The SINAP/SS7 system functions as an end point, such as a service control point (SCP), node within the Advanced Intelligent Network (AIN). The SINAP/SS7 system can also function as an adjunct processor (AP) or service node (SN). The SINAP/SS7 system is designed to support multiple enhanced service applications, such as 800 number translation, simultaneously while providing optimal performance for individual applications.

The SINAP/SS7 system implements the SS7 protocol to provide communications between applications and network elements, such as remote SCPs or signaling transfer points (STPs). Client applications residing on the SINAP/SS7 system initiate queries to the SS7 network and respond to queries from other network elements. Typically, these queries are in the form of Transaction Capabilities Application Part (TCAP) messages. However, applications can also be configured to interface to the SS7 network at the Message Transfer Part (MTP) or the Signaling Connection Control Part (SCCP) layers. In addition, the SINAP/SS7 system provides capabilities designed to simplify a customer’s development, testing, implementation, and troubleshooting of new applications.

Throughout this document, SINAP/SS7 refers to either the SINAP or MultiStack product, whichever is running on your system. SINAP node and SINAP stack refer to a single instance of the SINAP product running on your system. With MultiStack you can have multiple SINAP stacks on your system; with SINAP, you can have only one SINAP stack. SINAP variant or network variant refers to the type of SS7 protocol (ANSI, CCITT, TTC, NTT, or China) configured to run on a particular SINAP node.

Introduction 1-1

Introduction

Although the name of the International Telegraph and Telephone Consultative Committee (CCITT) was changed to the International Telecommunications Union (ITU) and its standards are now referred to as ITU-T recommendations, the SINAP and MultiStack products continue to refer to this protocol version as CCITT.

This document uses the generic term UNIX to refer to all supported varieties of UNIX, such as the HP-UX and Solaris operating systems. Differences between the varieties are noted in the text. In addition to HP-UX and Solaris, the Stratus ft Linux operating system is now supported.

The SINAP/MultiStack Technical Overview (R8055) contains a detailed description of the SINAP/SS7 product, its subsystems, and its features. It is highly recommended that you read this overview and have a firm understanding of the functionality before you use the SINAP/SS7 product and this manual.

1-2 SINAP/SS7 User’s Guide R8051-17

Chapter 2 Performing Basic Tasks2-

This chapter provides procedures and information on performing basic SINAP/SS7 tasks common to most users. The main sections of this chapter include:

• Starting the system and logging in

• Starting system and client applications with script files

• Accessing the user interfaces

• Displaying UNIX online manual help pages (man pages)

• Listing active processes

• Displaying process versions

• Enabling and disabling printing options

• Configuring the system software

• Stopping the system

N O T EIf you have not configured the nodes, the network and Transaction Capabilities Application Part (TCAP) variants and links, and the appropriate environment variables before starting the SINAP/SS7 software, see the SINAP/SS7 Installation Guide (R8060) for details on performing these tasks. Appendix A, ‘‘Network Information and Planning Forms,” contains blank network information and planning forms for you to photocopy and use in planning your network configuration.

Using the MultiStack ProductWhen you configure a SINAP node, you must define a unique login account and home directory for the node. The SINAP software creates a symbolic link between the node’s home directory and the sinap_master directory in which the SINAP software is installed. When you activate a node, the system starts a separate set of SINAP processes for that node. These processes execute in the node’s home directory. (For example, if you configure four nodes, there

Performing Basic Tasks 2-1

Starting SINAP/SS7 and Logging In

will be four separate sets of SINAP processes, each executing in the home directory of that node’s login account.)

You use a separate SINAP login window to manage each node. When you log in to a SINAP node, you specify the node you want to log in to by specifying the login name assigned to that node. For example, if you have four SINAP nodes with user names of sinap0, sinap1, sinap2, and sinap3, and you want to log in to the third SINAP node, you simply log in to SINAP as sinap2.

Starting SINAP/SS7 and Logging InBefore you can provision (configure) and define the SINAP/SS7 nodes and network, you must log in to the UNIX system as the user for the SINAP node you are configuring. Then you can start the SINAP/SS7 system. You can use a script file to activate each SINAP/SS7 node, or you can automatically start the system from the UNIX initialization file (/etc/inittab). The following subsections describe the different methods of starting the SINAP/SS7 system.

Starting the System Using the start_sinap Script FileThe start_sinap script uses the SINAP_HOME environment variable, and several commands the script executes use other SINAP/SS7 environment variables. Stratus recommends that you log in as the node user (for example, sinap0, sinap1, sinap2, or sinap3) before executing this script. If another user executes it, you must ensure that the user sets up the same environment variables. The SINAP environment file, $SINAP_HOME/Bin/sinap_env.[csh or sh], contains a complete list of all available environment variables and their corresponding values, if applicable.

N O T E S1. Depending on the network variant used, you may want to

define additional environment variables to activate specific SINAP/SS7 features on each configured node. You must define these variables before you start the SINAP/SS7 software.

2. To activate other environment variables, you must edit the SINAP environment file by uncommenting the appropriate environment variable and setting the variable to the correct value, if applicable.

3. See Appendix B, ‘‘SINAP/SS7 Environment Variables,” for more information on defining environment variables.



If you are running the MultiStack product, you must execute the start_sinap script file for each SINAP node to be activated. At a UNIX prompt, execute the following command to start the SINAP/SS7 system.

start_sinap

When you see the message All SINAP Subsystems Started on the console or in the SINAP/SS7 error log, you can start client application processes.

You can optionally specify one of three modes of operation in the SINAP/SS7 start-up script. You can specify a verbose mode, a test environment mode, or a combination of both verbose and test modes, by entering one of the start-up commands listed in Table 2-1.

Table 2-1. Start-Up Commands for SINAP/SS7

N O T EIn a production environment, Stratus recommends using the start_sinap script without the verbose or test mode options.

Figure 2-1 shows the start_sinap script.

Operation Mode Description

start_sinap -v Verbose mode. The SINAP/SS7 system displays information on the terminal screen as it executes each command in the script.

start_sinap -t Test environment mode. The SINAP/SS7 system displays information on the terminal screen as it starts each of its processes.

start_sinap -tv Test environment and verbose modes. Starts the SINAP/SS7 system using both modes.



Figure 2-1. The start_sinap Script File

::##################### start_sinap script #######################

#### only echo line if in verbose mode###echo_verbose (){ if [ $verbose -eq 1 ] then echo $1 fi}

test_env=0verbose=0respawn=0sinap_master=/etc/sinap_master

echo "<<<<<<<<<<<<<<<<<<<< STARTING SINAP... >>>>>>>>>>>>>>>>>>>>"

# Check OS typesunos=0linuxos=0

uname -a | grep SunOS > /dev/nullif [ $? -eq 0 ]then sunos=1fi

uname -a | grep Linux > /dev/nullif [ $? -eq 0 ]thenlinuxos=1fi

# Move to the executable directorycd $SINAP_HOME/Bin

# Save start_sinap options in file for subsequent restartrm -f .start_sinap_options



Figure 2-1. (Continued) The start_sinap Script File

echo $1 > .start_sinap_options

# Check for -t (test environment) and -v (verbose) optionsif [ $# -gt 0 ]then if [ $1 = "-t" ] then test_env=1 fi if [ $1 = "-v" ] then verbose=1 fi if [ $1 = "-tv" ] then test_env=1 verbose=1 fi if [ $1 = "-r" ] then respawn=1 fifi

if [ $respawn -eq 1 ]then#################### Start of Respawn Mode #####################

# Start the SS7 Daemon Process( nohup ss7dmn >> $HOME/ss7dmn.out 2>&1# If SINAP is running then stop nmcl, which make nmnp stop SINAP...if [ $sunos -eq 0 -a $linuxos -eq 0 ]thena=`ps -ef | grep "[ ]nmcl *$" | grep "$LOGNAME " | awk '{ print $2 }'`elsea=`ps -eo pid,ruser,fname | grep "[ ]nmcl *$" | grep "$LOGNAME " | awk '{ print $1 }'`fiif [ -n "$a" ]then echo "ss7dmn process died. Stopping SINAP..." kill -9 $afiexit 0 ) &ss7dmn_pid=$!

# If ss7dmn is not running after 5 second, quit the starting sequence# this usually happens when the SINAP license is not validsleep 5




if [ $sunos -eq 0 -a $linuxos -eq 0 ]thena=`ps -ef | grep ss7dmn | grep "$LOGNAME " | grep -v grep | awk '{ print $2 }'`elsea=`ps -eo pid,ruser,fname | grep ss7dmn | grep "$LOGNAME " | awk '{ print $1 }'`fiif [ -z "$a" ]then echo "ss7dmn process died. SINAP stopped. Please check messages in ss7dmn.out..." exit 0fi

# Start the Node Management Parent Process( nohup nmnp nmnp.p3f 0x3 -i >> $HOME/nmnp.out 2>&1# If nmnp dies and SINAP is running, then stop# other children processes of sinapinit1, which will respawn...echo "nmnp process died. Stopping SINAP..."# ss7-1056: kill ss7dmn unconditionally to allow respawnkill -9 $ss7dmn_pidexit 0 ) &

sleep 20

# The DRDA Daemon Processes are started in startappl.sh,# invoked by nmnp after the nmnp children are spawned...

# Wait for both ss7dmn and nmnp children processes to exit...wait

# Return to sinapinit1 script...exit 0

##################### End of Respawn Mode ######################fi

if [ $test_env -eq 1 ]then echo_verbose "-t option set: Running in test environment..."else echo_verbose "No -t option: Running in customer environment..."fi

echo_verbose "-v option set: Running in verbose mode..."

# Verify that SINAP is not running before starting




if [ $sunos -eq 0 ]thena=`ps -ef | grep "[ ]ss7dmn *$" | grep "$LOGNAME "`elsea=`ps -eo pid,ruser,fname | grep "[ ]ss7dmn *$" | grep "$LOGNAME " | awk '{ print $1 }'`fiif [ -n "$a" ]then echo "SINAP is running. Run stop_sinap before proceeding." exit 1fi

# Re-executing the stop_sinap procedure...echo_verbose "Re-executing the stop_sinap procedure..."

if [ $verbose -eq 1 ]then stop_sinap -velse stop_sinap -sfi

# Starting the ss7 daemon (ss7dmn)...echo_verbose "Starting the ss7 daemon (ss7dmn)..."

( nohup ss7dmn >> $HOME/ss7dmn.out 2>&1# If SINAP is running then stop nmcl, which makes nmnp stop SINAP...if [ $sunos -eq 0 -a $linuxos -eq 0 ]thena=`ps -ef | grep "[ ]nmcl *$" | grep "$LOGNAME " | awk '{ print $2 }'`elsea=`ps -eo pid,ruser,fname | grep "[ ]nmcl *$" | grep "$LOGNAME " | awk '{ print $1 }'`fiif [ -n "$a" ]then echo "ss7dmn process died. Stopping SINAP..." echo "Killing process nmcl..." kill -9 $afiexit 0 ) &

# If ss7dmn is not running after 5 second, quit the starting sequence# this usually happens when the SINAP license is not validsleep 5




The start_sinap process checks the SS7 daemon (SS7dmn) to see if the SINAP/SS7 system is already running. If the SINAP/SS7 system is running, the system displays the following message:

SINAP is running. Run stop_sinap before proceeding.

# Starting SINAP as background process...echo_verbose "ss7 daemon (ss7dmn) is started..."echo_verbose "Starting SINAP as background process..."

if [ $verbose -eq 0 ]then sleep 2fi

if [ $test_env -eq 0 ]then ( nohup nmnp nmnp.p3f 0x3 >> $HOME/nmnp.out 2>&1 # If nmnp dies when SINAP is running, issue warning... # ss7-1290 : Send the following error messages to $HOME/nmnp.out # when SINAP is starting up in non-verbose mode. echo "Node Management Parent Process (nmnp) died...." >> $HOME/nmnp.outexit 0 ) &

else ( nmnp nmnp.p3f 0x3 # If nmnp dies when SINAP is running, issue warning... echo "Node Management Parent Process (nmnp) died...." echo "Please restart SINAP at next opportunity..."

exit 0 ) &fi

echo_verbose "SINAP Node Manager parent process (nmnp) started..."

# Starting drda_daemon process in startappl.sh...echo_verbose "Starting drda_daemon process in startappl.sh..."

# Give all processes a chance to start up...sleep 20

echo "<<<<<<<<<<<<<<<<<<<<<< SINAP STARTED >>>>>>>>>>>>>>>>>>>>>>"exit 0



The script then terminates. This prevents the SINAP/SS7 system from terminating itself if it has already been started. The call to the stop_sinap script is made when the check indicates the SINAP/SS7 system is not running. This ensures that all memory structures were flushed.

The commands in the start_sinap script perform the tasks described in Table 2-2.

Table 2-2. start_sinap Script Command Tasks

Under normal conditions, start_sinap does not produce output, but creates the following.out files in the home directory of the user executing the script. That is, if the SINAP/SS7 user is running the script, these files appear in the user’s $SINAP_HOME directory for the node.

• nmnp.out

• drda_daemon.out

• ss7dmn.out

• nohup.out

Typically, the drda_daemon.out and ss7dmn.out files are empty when created. The nohup.out file logs the SS7dmn error messages instead of logging the messages to SS7dmn.out if the SINAP/SS7 system is started with the -t (test environment) option. The nmnp.out file usually contains the following lines:

LOAD: Read 96740 bytes from /home/sinap0/Bin/shm/pri/IPCTBL_loadLOAD: K_IPCTBL load successfulLOAD: Read 57660 bytes from

Command Task Description

nmnp Starts the Node Management parent process (nmnp), which brings up the SINAP/SS7 system. The file, nmnp.p3f, contains the remaining SINAP/SS7 subsystems that must be started.

sleep Provides sufficient time for the SINAP/SS7 system to become operational before starting the SS7 driver daemon process.

drda_daemon Reroutes retrieved messages from the board and the SS7 driver when a link fails. It has access to shared memory routing information that the SS7 driver does not have. This process is started by the startappl script. The drda_daemon process executes in the background.

ss7dmn Starts the SS7 daemon and is the first SINAP/SS7 process to be started. It reads the /etc/SS7links file at system start up and whenever you execute the sinap_update command.



/home/sinap0/Bin/shm/pri/TREAT_loadLOAD: K_TREAT load successfulLOAD: Read 1955512 bytes from /home/sinap0/Bin/shm/pri/STATIC_loadLOAD: K_STATIC load successfulSCOC:restart startedSCOC:restart DONE

N O T E These are sample values and might not be the same as the ones on your machine.

The load files, STATIC_load, IPCTBL_load, and TREAT_load, contain static information about the network configuration, network processes, and error handling. In addition, the SINAP/SS7 system sends any errors to the error log.

A start-up script, called Bin/startappl, allows client applications to start automatically when you start the SINAP/SS7 system. For further information on startappl, see the section on starting client applications later in this chapter.

For information about stopping the SINAP/SS7 system, see the section on stopping the SINAP/SS7 system later in this chapter.

Restarting the System with Script FilesTo restart the SINAP/SS7 system using script files, log in as the user and issue the restart command from a UNIX prompt. The restart command executes the stop_sinap script file, then executes the start_sinap script file.

In a MultiStack environment, you must issue the restart command for each SINAP node to be restarted.

See ‘‘The MTP Restart Process’’ in Chapter 3, which describes the MTP restart process, for information about avoiding routing problems that might occur when restarting a node.



Automatically Starting and/or Restarting from a UNIX Initialization FileDuring the SINAP/SS7 installation process, the installation script displays the following prompt asking whether you want to start the SINAP/SS7 system from the UNIX initialization file (/etc/inittab).

If you answered y (yes) in response to this prompt during the installation process, the following line appends to the /etc/inittab file.

0$SINAP_INDEX:234:respawn:$SINAP_HOME/Bin/sinapinit > /dev/null

This command line in the /etc/inittab file instructs the UNIX system to automatically restart or respawn SINAP/SS7 processes whenever the SINAP/SS7 system shuts down. If you stop the system using the stop_sinap script, UNIX respawns SINAP/SS7 processes immediately after the script finishes executing.

N O T EIf you do not want UNIX to restart the SINAP/SS7 system automatically from the UNIX initialization file, you can edit the /etc/inittab file, using any UNIX-compatible editor, and change the respawn parameter to off.

See the description of inittab in the UNIX documentation at your site.

See ‘‘The MTP Restart Process’’ in Chapter 3, which describes the MTP restart process, for information about avoiding routing problems that might occur when restarting a node.

Do you wish to start SINAP from inittab (default:n)[y,n,?,q]


Starting Client Applications

Starting Client ApplicationsThis section describes how to start a client application using the startappl script file and how to automatically start a client application using the SINAP/SS7 Utility Monitor.

Starting a Client Application Using the startappl Script FileThe startappl script file allows client applications to automatically start up whenever you start the SINAP/SS7 system using the start_sinap script file. The node management parent executes this script after all the required child processes for node management, the Built-In Test Environment (BITE), MTP, and Signaling Connection Control Part (SCCP) subsystems are started and running.

To automatically start an application using the startappl script file, edit the file bin/startappl, shown in Figure 2-2, using any UNIX-compatible editor, such as vi, and add the start-up commands required for the application.

If you want to start up multiple applications with this script file, add the start-up commands required for each application to be started.



Figure 2-2. The startappl Script File

:# Start the driver daemon processes.# If they die, stop SINAP...

( nohup drda_daemon 1 >> $HOME/drda_daemon.out 2>&1# If SINAP is running then stop nmcl, which make nmnp stop SINAP...uname -a | grep SunOS > /dev/nullif [ $? -eq 0 ]then a=`ps -eo pid,ruser,fname | grep "[ ]nmcl *$" | grep "$LOGNAME " |awk '{ print $1 }'`else a=`ps -ef | grep "[ ]nmcl *$" | grep "$LOGNAME " | awk '{ print $2}'`fiif [ -n "$a" ]then echo "drda_daemon died. Stopping SINAP..." kill -9 $afiexit 0 ) &

############## NOTE: The above lines are needed to start the driver daemon process(es).# Proper SINAP operation depends upon this being done at the right time.######### This script provides the client applications the possibility# to be started automatically during the SINAP startup time.# It will always be executed by Node Parent after all the# required child processes of Node Management, and BITE, MTP and# SCCP subsystems have been started and running in stable condition.## Note: This script should be edited by client application management# to include proper setups of system parameters for applications if# required, as well as executables of client applications to be# started.##############exit



Automatically Starting a Client Application with the Utility MonitorThe SINAP/SS7 Utility Monitor program sinap_utlmon starts, monitors, and restarts processes by executing user-defined command line arguments. For example, you can specify the start-up commands required to start an application for the Utility Monitor to execute. You can specify multiple commands, including their associated arguments or parameters. The Utility Monitor starts each specified command and, after waiting one second, executes a kill(2) command with a parameter of 0 to determine if the command is still running. If it is, sinap_utlmon keeps the command alive by restarting it, if it exists. Otherwise, it considers the command “unrunnable” and continues to process other commands.

After starting all specified commands, sinap_utlmon saves the command environment in the sinap_utlmon.dat environment file in the directory, $SINAP_HOME/bin. The Utility Monitor continues to monitor and process commands and restart any failed commands.

The Utility Monitor detects command failures in two ways. First if a command exits, sinap_utlmon normally receives a SIGCHLD (child death) signal. Otherwise, sinap_utlmon sends a kill(2) command periodically to detect if a child process is still alive. After starting all specified commands, sinap_utlmon saves the command environment in the sinap_utlmon.dat environment file in the directory, $SINAP_HOME/bin. The Utility Monitor checks the status of all children, then sends a health response to the SINAP/SS7 system. If the SINAP/SS7 system does not receive the health response, it starts another instance of sinap_utlmon.

Using Command Line ParametersYou can start sinap_utlmon using command line parameters to define the start-up commands required to start an application.

N O T E S1. You must be logged in as root to run sinap_utlmon

and allow the management of processes started by an extinct instance of itself.

2. You cannot use sinap_utlmon to keep a process alive that forks to disassociate itself from its parent.

Since sinap_utlmon uses exec (2) to create specified processes, you must specify the full path name for sinap_utlmon along with the commands and associated arguments to be executed using the following format. The full path name for sinap_utlmon and all commands must be used, such as:

$SINAP_HOME/Bin/sinap_utlmon [command argument [^ command] ... ]

Use a caret character (^) to delimit commands. Use a space to separate each required argument within a command.


Accessing the User Interfaces

N O T EIf a sinap_utlmon.dat environment file already exists when you start the Utility Monitor using command line parameters, sinap_utlmon ignores the command line parameters and processes the commands contained in the environment file.

Using sinap_utlmon Environment Variable FileYou can start sinap_utlmon without specifying the commands to run on the command line and enter start-up commands and parameters required to start an application in the sinap_utlmon.dat environment file. The Utility Monitor reads the contents of the environment file and processes the commands.

When you start sinap_utlmon using command line parameters, the environment file sinap_utlmon.dat contains the execution environment of a sinap_utlmon instance. This file contains the process identifier (PID) of the instance on the first line, followed by a line for each command that is being maintained. For each command entered, the file contains its PID, a caret (^), the command and its arguments separated by spaces, and another caret (^).

N O T EWhen you enter commands in the environment file and start sinap_utlmon without command line parameters, you must set the PID of the sinap_utlmon instance and PIDs of each command to 0.

Accessing the User InterfacesThe SINAP/SS7 system provides two user interfaces: the Terminal Handler and the UNIX MML command interface. The following subsections describe the basic operations of the Terminal Handler interface and the UNIX MML command interface, which uses the send_cm command.

Bringing Up the Terminal HandlerThe Terminal Handler interface is part of the Node Management subsystem and provides two ways to perform system operations, maintenance, and diagnostic tasks. Specifically, the Terminal Handler allows you to configure the SINAP/SS7 system, debug problems, and create and print reports. You can use the Terminal Handler in either of two ways:

• Menu selection mode—This method uses menus and interactive screens to build and execute task commands. You select a task from a menu and follow subsequent menus and screen prompts to enter information which results in the generation of the MML command to perform the task.



• Free-form MML command mode—This method bypasses the menus and allows you to enter MML commands from the Terminal Handler command line.

You access either method from within the Terminal Handler. To start the Terminal Handler, log in as:

sysopr[account ID number]

Log in to the appropriate sysopr account with the same ID as the SINAP node you are using. (See the section at the beginning of this chapter that describes login procedures.)

N O T ELogging in as sysopr automatically brings up the Terminal Handler because the.profile for the user sysopr runs the Terminal Handler.

The Terminal Handler’s SINAP System Main Menu appears. Figure 2-3 shows the main menu and the hierarchical structure of its submenus.



Figure 2-3. SINAP/SS7 Menu Hierarchy

S I N A P S y s t e m M a i n M e n u1 . S y s t e m C o m m a n d s2 . N e t w o r k C o m m a n d s3 . A p p l i c a t i o n C o m m a n d s4 . B I T E C o m m a n d s5 . E X I T M e n u ( R e t u r n t o U N I X )

S y s t e m C o m m a n d sB a c k u p N o d e

( B A C K U P - N O D E )R e s t o r e N o d e

( R E S T O R E - N O D E )C h a n g e B a c k u p o r P u r g e D a y

( C H A N G E - B K U P D A Y )D i s p l a y B a c k u p o r P u r g e D a y

( C H A N G E - P U R G E D A Y )D e l e t e F i l e

( D E L E T E - F I L E )R e a d T r e a t m e n t T a b l e

( R E A D - T R E A T )R e p o r t A l a r m

( R E P O R T - A L A R M )R e p o r t S o f t w a r e N o t e b o o k

( R E P O R T - N B O O K )S e t P r i n t e r D e f a u l t

( S E T - P R I N T E R )

N e t w o r k C o m m a n d sC r e a t e

( C R E A T E )C o n f i g u r e

( C O N F I G U R E )C h a n g e

( C H A N G E )D i s p l a y

( D I S P L A Y )D e l e t e

( D E L E T E )D u m p T a b l e

( D U M P - T A B L E )M e a s u r e m e n t s

( f o r e x a m p l e ,R E T R I E V E - N O M ,S T A R T - M E A S U R E ,S T O P - M W R I T E )

A p p l i c a t i o n C o m m a n d sD i s p l a y S S N

( D I S P L A Y - S U B S Y S T E M )B a c k u p A p p l i c a t i o n

( B A C K U P - A P P L )R e s t o r e A p p l i c a t i o n

( B A C K U P - A P P L )L o a d C o n t r o l

( f o r e x a m p l e ,S E T U P - L O A D - C O N T R O L ,D I S A B L E - L O A D - C O N T R O L )

B I T E C o m m a n d sM o n i t o r C o m m a n d s

( f o r e x a m p l e ,S T A R T - M O N , S T O P - M O N )

S c e n a r i o C o m m a n d s( f o r e x a m p l e ,S T A R T - S C E N , S T O P - M O N )

S t a r t D e b u g( f o r e x a m p l e ,S T A R T - D B G )

T e s t L i n k( T E S T - L I N K )

L o g A n a l y s i s( f o r e x a m p l e , F I N D ,S E L E C T )

D i s p l a y P r o c e s s V e r s i o n( D I S P L A Y - P R O C E S S -V E R S I O N )

(RESTORE-APPL)



On the SINAP System Main Menu, MML commands are grouped into four submenus.

• System Commands

• Network Commands

• Application Commands

• BITE Commands

Figure 2-3 shows the relationship of the four submenus to the main menu and provides either the MML command associated with the task, or, in cases where there are multiple commands, provides an example of a type of command for that task.

The SINAP processes must be running on the node for the Terminal Handler to run. If these processes are not running, the following error message appears when you try to log in:

For HP-UX, Solaris, or Stratus ft Linux operating systems:

-)?ERR):CASL:2 TH,2-shmat error (PSYSTEM)FILE=nmthmain.c, LINE=376, ERROR: nmth_register(), errno=2 (No such file or directory) Please check if SINAP is running or needs to be started!

If you are connected to the system via a Telnet connection, the connection closes and the screen clears. (Depending on the type of Telnet client you are using, there might be no display at all.) If this happens, you can log in again using the following command:

su - sysopr[account ID number]

su to the appropriate sysopr account with the same ID as the SINAP node you are using. Logging in as sysopr[account ID number] or issuing the su - sysopr[account ID number] command also brings up the Terminal Handler with the SINAP/SS7 menus.

Using Terminal Handler Operation ModesThe Terminal Handler contains two modes of operation: the menu selection mode and the free-form MML command mode.

When you log in to the SINAP/SS7 system as sysopr, the Terminal Handler System Main Menu appears. You can remain in the menu selection mode and use the menus to create, configure, display, and modify SINAP/SS7 components.

Alternatively, press CTRL-F to access the free-form MML command mode and enter MML commands directly from the command line as shown in the following example. You use a colon (:) to delimit a command from its arguments and you must use a semicolon (;) to terminate a command.

For example: delete-link:link=lnk01;



The Terminal Handler accepts three types of input:

• Menu selection options

• Prompt responses

• Display confirmation

Select tasks from the menus by entering the number corresponding to the task option on the menu. Do not press the Enter key after entering the number. (Pressing Enter sends a partially built command to the SINAP/SS7 system and generates an error.)

Depending on the task you select from the menus, the system might prompt you for information. Enter the information and press Enter to commit it to the system. The system processes the information you enter and uses it to build the MML commands. When all selections are made, the completed command displays on the screen on the MML Send Menu. If correct, you press Enter again to send the MML command to the system to execute.

N O T EActivating the environment variable SINAP_MML_ALT_NUMERIC_CONVERSION allows you to enter MML values for command arguments in decimal, octal, or hexadecimal notation (and any combination thereof) as follows with one exception—you must use decimal notation for argument values that define time, data, or link speed. Notation Command Argument Value Hexadecimal 0x or 0X, followed by the value Decimal Value only (no prefix required) Octal 0, followed by the value



Keyboard ShortcutsUse the keyboard shortcuts shown in Table 2-3 to move around within the Terminal Handler.

Table 2-3. Terminal Handler Keyboard Shortcuts

N O T EAt certain points, the Terminal Handler prompts you to enter a value, determined by a particular script that is running. The prompts have the format, KEYWORD=, where KEYWORD is a particular value related to the task being performed. You must enter the value and press RETURN. In this case, only the Ctrl-C keystroke works to exit the screen. If you press Ctrl-C, the Terminal Handler returns to the previous menu.

After a command executes and the Terminal Handler displays the results, the following prompt appears:

? Hit (Q or q) to quit displaying response

The Terminal Handler accepts only a Q, q, or CTRL-R (to redraw the screen) at this prompt. If you press Enter after typing one of these responses, the system re-executes the command.

Other sections in this guide describe procedural information for using the Terminal Handler menus, screens, and MML commands to configure and maintain SINAP/SS7 system components. See Appendix C, ‘‘SINAP/SS7 MML Command Summary,” for a summary of MML commands and command syntax.

Keystroke Action

Ctrl-B

Ctrl-P

Ctrl-R

Ctrl-F

Ctrl-C

RETURN

?

Return to the SINAP/SS7 main menu.

Return to the previous menu.

Redraw a screen.

Toggle between menu selection mode and free-form mode.

Exit a script.

Send a command to the Command Management process for execution.

Display a help screen with all commands.



Executing MML Commands from a Login WindowThe send_cm command enables you to execute MML commands from a SINAP/SS7 login window at the UNIX prompt instead of from the Terminal Handler. The send_cm command sends the MML commands to the Command Management process (nmcm) for execution.

N O T EActivating the environment variable SINAP_MML_ALT_NUMERIC_CONVERSION allows you to enter MML values for command arguments in decimal, octal, or hexadecimal notation (and any combination thereof) as follows with one exception—you must use decimal notation for argument values that define time, data, or link speed. Notation Command Argument Value Hexadecimal 0x or 0X, followed by the value Decimal Value only (no prefix required) Octal 0, followed by the value

You can execute the send_cm command using any of the formats described in Table 2-4. (Note that the SINAP/SS7 system must be running in order to issue this command.)



Table 2-4. send_cm Command Formats

You can interrupt execution of the send_cm command in the following two ways:

• Press the CTRL and C keys simultaneously.

• Issue the UNIX kill command (this may cause the nmcm to display an error message).

When send_cm terminates, you return to the level from which you invoked send_cm (for example, the UNIX prompt or a SINAP/SS7 login window). The send_cm command terminates automatically in the following cases:

• If the nmcm encounters an error or a return code other than 1

• If the nmcm does not respond to an MML command within 30 seconds

N O T EIf there is a problem with executing the command, you can look up error messages associated with the send_cm command in the MML Command Log file located in $SINAP_HOME/Logs/system. This file contains a record of all MML commands entered through any of the user interface options and any error messages associated with unsuccessfully executed commands. You can use the error message

Command Format Description

send_cm Executes the command in an interactive mode that accepts commands entered through standard input (typically, the keyboard). Enter the MML commands to be executed, then press the CTRL and D keys simultaneously to terminate the interactive session and exit send_cm.

send_cm file_name Executes a script file that contains MML commands (where file_name is the name of the script file). The send_cm command executes all commands in the script file, then terminates automatically. In the file, each MML command must be on a separate line and must end with a semicolon.

send_cm -s "mml_command;" Executes a single MML command (where "mml_command;" specifies the MML command to execute). The MML command must be enclosed in quotation marks and must end with a semicolon. The send_cm command executes the specified MML command, then terminates automatically. To execute another MML command, you must issue the send_cm command again.



descriptions to help resolve the problem. The system starts a new log file each day and names the file using the format, CMD MMDD, where MM represents the month and DD represents the day of the month. For example, CMD0815.

Figure 2-4 shows sample commands in an MML Command Log file.

Figure 2-4. Sample MML Command Log File

Man Page FormatThe man page format of the send_cm command is send_cm.

N1,M1,XC,XC 1998-01-15 10:31:11START-DBG:ENT=(,,NM,DM,MSG=I_DEBUG,CMD;input command is not recognized by the system

*N1,M1,NM,TH 1998-01-15 11:12:41REPORT-MALL:DATE=95-08-08, TIME=11:30MTP30 measurement not available

*N1,M1,NM,TH 1998-01-15 16:14:41CONFIGURE-LSET:LINKSET=lset1,STATE=INACTIVE;error field <LLINKSET> - label invalid

*N1,M1,NM,TH 1998-01-15 16:15:13DISPLAY_LSET:LINKSET=ALL;command completed

*N1,M1,NM,TH 1998-01-15 16:16:24CONFIGURE-LSET:LINKSET=lset1,STATE= ACTIVE;command completed


Displaying Man Pages

Sample Script FileFigure 2-5 shows a script file that contains sample MML commands for configuring the SINAP/SS7 system. You can create a similar script file and use it within the send_cm command to create and modify your SINAP/SS7 configuration.

Figure 2-5. Sample Configuration Script Files

Displaying Man PagesHelp documentation for specific SINAP/SS7 tasks and procedures is available online in the form of UNIX online manual pages. In common usage, manual pages are referred to as man pages. Man pages are available to provide task descriptions and further information about using the product. A man page is available for each help topic.

To display SINAP/SS7 man pages, issue the man command at the UNIX prompt. If installed, the man pages are located in the directory, $SINAP_HOME/man. (This discussion is described in the man page, displ-man.)

N O T EAlthough most SINAP/SS7 man pages describe Terminal Handler commands, the man command itself is a UNIX command. The Terminal Handler does not provide a shell feature. Therefore, to display a SINAP/SS7 man page, you must exit the Terminal Handler and return to the UNIX prompt to issue the man command.

The SINAP/SS7 installation process automatically appends the path name of the SINAP/SS7 man-page directory to the MANPATH variable. However, to ensure you can access UNIX man

CREATE-OSP:NETWORK=NAT10,SPC=2730; CREATE-LSET:LINKSET=LSET1,ADPC=3003,ACTLINK=2,LOADLINK=2; CREATE-LINK:LINK=LNK0,PORTNUM=0,LINKSET=LSET1,SLC=0,PRIORITY=0,SPEED=64K; CREATE-LINK:LINK=LNK1,PORTNUM=1,LINKSET=LSET1,SLC=1,PRIORITY=1,SPEED=64K; CREATE-RSET:ROUTESET=RSET1,DPC=3003,ROUTES=LSET1,LOADSHR=ENABLE; CREATE-CPC:LSSN=253,RPC=3003; CREATE-CPC:LSSN=254,RPC=3003; CREATE-DUCPC:LSSN=253,RPC=3003; CREATE-DUCPC:LSSN=254,RPC=3003; CREATE-REMSSN:PC=3003,SSN=253&254; CONFIGURE-LSET:LINKSET=LSET1,STATE=ACTIVE; CONFIGURE-RSET:ROUTESET=RSET1,STATE=ACTIVE;


Displaying Man Pages

pages, check the PATH and MANPATH variables and verify that they include the following path names:

PATH /usr/binMANPATH /usr/share/man

If your PATH and MANPATH variables include these path names, you can issue the following command to display a man page.

man command

command is the name of the SINAP/SS7 command for the man page to be displayed. For example:

man configure_link

You can also specify the abbreviated form of the command name. For example:

man cfg-link

If you did not set the PATH and MANPATH variables, use the following format for the man command:

/usr/bin/man -M /home/sinap/man/variant command

Table 2-5 defines the arguments for the man command.

Table 2-5. man Command Arguments

Argument Description

-M Specifies the path name of the SINAP/SS7 man-page directory (the default is $SINAP_HOME/man).

variant The SINAP/SS7 version you are using (CCITT, ANSI, TTC, NTT, or China). The man pages are installed in the specified subdirectory below man1. For example, if you are using the CCITT version of the SINAP/SS7 system, you would specify /home/sinap/man/ccitt for the -M option of the man command.

command The name of the SINAP/SS7 command for which you want to display a man page.


Listing Active Processes

N O T EIf your SINAP/SS7 root directory is not /home/sinap, your SINAP/SS7 man-page directory will be different.

Listing Active ProcessesEach SINAP/SS7 process has a unique label. To determine whether a particular SINAP/SS7 process is active, you must display a list of active system processes and then check the command’s output to see if any SINAP/SS7 processes are listed.

To display a full listing of all active processes on the system, issue the following command from the UNIX prompt on HP-UX systems:

ps -eaf |grep sinap |more

The above does not list SINAP processes on Solaris and Stratus ft Linux systems, so on Solaris and Stratus ft Linux systems, instead do:

ps -eo pid,ruser,fname |grep sinap |more

Table 2-6 contains a listing of SINAP/SS7 processes and their labels.

Table 2-6. SINAP/SS7 Process Labels (Page 1 of 2)

BITE Subsystem Processes bibp BITE Parent Process

biid BITE Inbound Data Distribution

bilf Log File Process

bimi Man-Machine Interface (MML)

bitu Link Test User Part Process

bila BITE Log Analysis (exists only if you open the BITE analysis process)

MTP Subsystem Processes l3cb Changeback Process

l3co Changeover Process

l3cr Controlled Rerouting Process

l3dt Message Distribution Process

l3fr Forced Rerouting Process

l3la Link Availability Control Process

l3ls Link Set Control Process

l3mp MTP Management Parent Process


Displaying Process Versions of SINAP/SS7 Processes

Displaying Process Versions of SINAP/SS7 ProcessesThe display process version command displays the version of each process registered with the SINAP/SS7 system, including SINAP/SS7 subsystems and any registered user processes. You can access this command only from the user interface, called the Terminal Handler. Open the Terminal Handler and use the menu selection mode to access the BITE Commands menu from the SINAP System Main Menu. You cannot use the display process version command in the free-form mode. (See a later section of this chapter for information on the Terminal Handler.)

Figure 2-6 shows the output for the command on a system running all the SINAP/SS7 management processes.

l3mt MTP Level-3 Management Process

l3rc Signaling Routing Process

l3rt Message Routing Function

Node Management Processesnmc1 Client Management Process

nmcm Command Management Process

nmdm Deferred Message Process

nmds Disk I/O Server Process

nmip IPC Handler Process

nmmc Measurement Collection Process

nmni SS7 Network Interface Process

nmnp Node Management Parent Process

nmth Terminal Handler Process (exists only if you turn on sysopr)

nmtm Trouble Management Process

SCCP Management Processscmg SCCP Management Process

scoc SCCP Connection Oriented Control Process

Table 2-6. SINAP/SS7 Process Labels (Page 2 of 2)


Enabling and Disabling Printing

Figure 2-6. Output from the display process version Command

Man Page FormatThe man page format for the display process version command is displ-pvers.

Enabling and Disabling PrintingThe SINAP/SS7 system can be configured to print reports from the output of the Display and Report commands. To enable the automatic print options, you must activate the environment variable, SINAP_MML_PRINT_RESPONSE, before starting the SINAP/SS7 system. (See Appendix B for environment variable information.)

When printing is enabled, the Set Printer Default menu automatically appears as part of the Terminal Handler script. Conversely, if you do not want to print and, therefore, do not want the Print Options menu to display, you can disable the print commands by disabling the SINAP_MML_PRINT_RESPONSE environment variable and restarting the system. (See Appendix B, ‘‘SINAP/SS7 Environment Variables,” for environment variable information.)

N1, M1, NM, PP,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, NM, CL,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, NM, DS,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, NM, TM,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, NM, CM,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, NM, NI,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, NM, DM,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, NM, MC,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, NM, IP,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, BI, PP,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, BI, MI,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, BI, LF,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, BI, ID,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, BI, TU,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, L3, PP,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, L3, MT,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, L3, DT,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, L3, RT,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, L3, CO,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, L3, FR,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, L3, LS,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, L3, CR,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, L3, RC,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, L3, LA,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, L3, CB,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, SC, MG,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04 N1, M1, SC, SO,1: appl_ver=CCITT, proc_ver=Rel 14.0.0.0_05AL 02/04/04


Configuring the SINAP/SS7 Software

Menu Selection ModeSelect the Set Printer Default option from the System Commands menu. The Set Printer Default menu appears.

Select the appropriate option and respond to the system prompts to enable or disable the print function. The menu also offers options for printing to a default or specified terminal or printer and printing to a file.

Refer to Appendix B, ‘‘SINAP/SS7 Environment Variables,” for information about setting the SINAP_MML_PRINT_RESPONSE environment variable to enable the automatic printing feature in MML commands that includes the PRINT argument.

MML Command FormatThe MML command format is as follows:

SET-PRINTER:PRINT=print;

The print argument specifies whether commands and responses are printed, as well as displayed at the terminal. Specify YES to print to the default printer, NO for no printing, or specify the printer ID of the printer to be used for printing reports.

Man Page FormatThe man page format for SET-PRINTER is set-printer.

Configuring the SINAP/SS7 SoftwareYou can configure SINAP/SS7 network elements using script files or using the static2mml command. Both options are described in the following subsections.

Set Printer Default

1. Print Default2. Print Enabled3. Print Disabled4. Print to Specified Printer5. Print to Filename

< PRINT >



Using a Script File to Configure Network ComponentsYou can use the send_cm command to configure the SINAP/SS7 network components using a script file. Enter the command using the following format:

send_cm file_name

This command executes a script file that contains MML commands, where file_name is the name of the script file. The send_cm command executes all commands in the script file, then terminates automatically. In the file, each MML command must be on a separate line and must end with a semicolon. See the information on executing MML commands from a login window earlier in this chapter for more information on using the send_cm command.

N O T EThe file_name could be the name of the Recent Change Command Log file (rclog). The rclog contains all changes that have been made to the SINAP/SS7 database since the system was started.

Re-creating Existing Configurations Using static2mmlThe static2mml command enables you to save and re-create an existing SINAP/SS7 configuration. This command examines the specified SINAP/SS7 configuration, creates a list of the MML commands required to re-create this configuration, and writes this list to the specified output. You can then use this output list of commands as input to the send_cm command or the rclog file, each of which can be used to execute the commands and re-create the existing configuration.

Enter the static2mml command in the following format:

static2mml $SINAP_HOME/Bin/shm/pri/input_file [> output_file]



Table 2-7 defines the arguments for the static2mml command.

Table 2-7. static2mml Command Arguments

N O T EIf you are running the MultiStack product, the static2mml command needs to be executed repeatedly for each node configured at the system.

The following sample command creates a list of the MML commands required to re-create the SINAP/SS7 configuration defined in the file ain_config. Output is written to the file mml.txt, located in the user Smith’s home directory (/usr/smith).

static2mml /home/sinap/Bin/shm/pri/ain_config > /usr/smith/mml.txt

The following is an example of the contents of mml.txt. The following sample is for display purposes only. The contents of your file might be different, depending on your SINAP/SS7 configuration.

CREATE-OSP:NETWORK=NAT10,SPC=2730; CREATE-LSET:LINKSET=LSET1,ADPC=3003,ACTLINK=2,LOADLINK=2; CREATE-LINK:LINK=LNK0,PORTNUM=0,LINKSET=LSET1,SLC=0,PRIORITY=0,SPEED=64K; CREATE-LINK:LINK=LNK1,PORTNUM=1,LINKSET=LSET1,SLC=1,PRIORITY=1,SPE

Arguments Description

input_file Specifies the file that contains the SINAP/SS7 configuration to be saved. This file is typically named STATIC_load and is located in the $SINAP_HOME/Bin/shm/pri directory.

Note: The file may have been renamed to something other than STATIC_load. Also, you may have to change the file’s access rights to provide static2mml with read access to the file.

output_file Specifies the name of a file to which command output is to be written. If you do not include this parameter in the static2mml command line, command output is written to standard output (typically, the terminal).


Stopping the SINAP/SS7 System

ED=64K; CREATE-RSET:ROUTESET=RSET1,DPC=3003,ROUTES=LSET1,LOADSHR=ENABLE; CREATE-CPC:LSSN=253,RPC=3003; CREATE-CPC:LSSN=254,RPC=3003; CREATE-DUCPC:LSSN=253,RPC=3003; CREATE-DUCPC:LSSN=254,RPC=3003; CREATE-REMSSN:PC=3003,SSN=253&254; CONFIGURE-LSET:LINKSET=LSET1,STATE=ACTIVE; CONFIGURE-RSET:ROUTESET=RSET1,STATE=ACTIVE;

N O T E S1. In the ANSI and China network variants of the SINAP/SS7

system, whenever you specify network or cluster routing for a destination point code by issuing MML commands from the Terminal Handler, the system stores the Xs (that specify network or cluster routing) in the destination point code (DPC) as zeros. For example, if you specified the DPC 254-X-X (network routing) or 254-052-X (cluster routing), the system would store the number as 254-0-0 or 254-052-0.

2. Before using the output file you specified in the static2mml command as input to the rclog file or input to the send_cm command to re-create an existing configuration, you must change the 0s to Xs in the DPC (of the CREATE_RSET command). For example, you would change 254-0-0 to 254-X-X and you would change 254-052-0 to 254-052-X, as shown in the following two examples:

CREATE-RSET:ROUTESET=RSET1,DPC=254-X-X,ROUTES=LSET;

CREATE-RSET:ROUTESET=RSET1,DPC=254-052-X,ROUTES=LSET1;

Stopping the SINAP/SS7 SystemUse the stop_sinap script file to stop the SINAP/SS7 system. This script stops all processes registered with the SINAP/SS7 system.

At a UNIX prompt, execute the following command to stop the SINAP/SS7 system. In a MultiStack environment, you must issue this command for each node to be stopped:

stop_sinap



N O T EBefore executing the stop_sinap script, terminate all active client applications or the SINAP/SS7 system might return warning messages.

You can optionally specify one of three modes of operation in the SINAP/SS7 stop_sinap script. You can specify a verbose mode, a test environment mode, or a combination of both verbose and test modes. Enter one of the following commands to specify a mode of operation for stopping the SINAP/SS7 system:

stop_sinap -v

stop_sinap -t

stop_sinap -tv

Table 2-8 describes the operation modes you can specify within the stop_sinap command.

Table 2-8. stop_sinap Command Options

Operation Mode Description

stop_sinap -v Verbose mode. The SINAP/SS7 system displays information on the terminal screen as it executes each command in the script.

stop_sinap -t Test environment mode. The SINAP/SS7 system displays information on the terminal screen as it stops each of its processes.

stop_sinap -tv Test environment and verbose modes. Stops the SINAP/SS7 system using both modes.



Figure 2-7 shows the commands in the stop_sinap script file.

:####################### stop_sinap script ######################

#### only echo line if in verbose mode# (if in verbose mode, can’t be in start mode, so don’t need that check)###echo_verbose() if [ $verbose -eq 1 ] then echo $1 fi}

#### always echo line except in start mode

echo_nostart(){ if [ $start -eq 0 ] then echo $1 fi}test_env=0verbose=0start=0

# Check for -t (test), -v (verbose) and -s (called from start_sinap)if [ $# -gt 0 ]then if [ $1= “-t” ] then test_env=1 fi if [ $1= “-v” ] then verbose=1 fi if [ $1= “-tv” ] then test_env=1 verbose=1 fi if [ $1= “-s” ] then start=1 fifi



"`

Figure 2-7. The stop_sinap Script File

Figure 2-7. (Continued) The stop_sinap Script File

# Only display "STOPPING SINAP..." if not called from start_sinapecho_nostart ">>>>>>>>>>>>>>>>>>>> STOPPING SINAP... <<<<<<<<<<<<<<<<<<<<"echo_verbose "-v option set: Running in verbose mode..."

# Check OS typesunos=0linuxos=0

uname -a | grep SunOS > /dev/nullif [ $? -eq 0 ]thensunos=1fi

uname -a | grep Linux > /dev/nullif [ $? -eq 0 ]thenlinuxos=1fi

# Verify that SINAP is running before startingif [ $sunos -eq 0 -a $linuxos -eq 0 ]then a=`ps -ef | grep "[ ]nmcl *$" | grep "$LOGNAME "`else a=`ps -eo pid,ruser,fname | grep "[ ]nmcl *$" | grep "$LOGNAMEfiif [ -z "$a" ]then echo_nostart "SINAP has already been stopped." echo_verbose "Re-executing stop procedure anyways..." # Fall through to perform stop processing again...fi

# Moving to the executable directory...echo_verbose "Moving to the executable directory..."cd $SINAP_HOME/Bin

# Stop SINAP...

# Stopping all registered SINAP processes...echo_verbose "Stopping all registered SINAP processes..."



Figure 2-7. (Continued) The stop_sinap Script File

$SINAP_HOME/Bin/sinap_pidclean# ss7-1528: Remove the occurances of FTXif [ $? -eq 0 ]then echo_nostart "Used SINAP ipc table to stop SINAP processes..." echo_nostart "Now using the process table to stop SINAP processes..."else echo_verbose "Could not use SINAP ipc table to stop SINAP processes..."fi

# Ensure all SINAP processes except drda_daemon and ss7dmn are killed...$SINAP_HOME/Bin/sinap_pidclean -a

# Stopping all links and devicesecho_verbose "All registered SINAP processes stopped..."echo_verbose "Stopping all links and devices..."$SINAP_HOME/Bin/drda_stop_linksecho_verbose "All links and devices stopped..."sleep 2

# Stopping SINAP drda_daemon process...echo_verbose "Stopping SINAP drda_daemon process..."$SINAP_HOME/Bin/sinap_pidclean -decho_verbose "SINAP drda_daemon process stopped..."

# Removing SINAP shared memory segments...echo_verbose "Removing SINAP shared memory segments..."$SINAP_HOME/Bin/remove_shmecho_verbose "SINAP shared memory segments removed..."

# Stopping SINAP ss7dmn process...echo_verbose "Stopping SINAP ss7dmn process..."$SINAP_HOME/Bin/sinap_pidclean -secho_verbose "SINAP ss7dmn process stopped..."

# Give all processes a chance to clean up...sleep 2

# Final remove_shm call to make sure IPCTBL is goneecho_verbose "Final SINAP shared memory cleanup..."$SINAP_HOME/Bin/remove_shm

# Only display "SINAP STOPPED" if not called from start_sinapecho_nostart ">>>>>>>>>>>>>>>>>>>>>> SINAP STOPPED <<<<<<<<<<<<<<<<<<<<<<"

exit 0



Table 2-9 describes the commands in the stop_sinap script.

Table 2-9. stop_sinap Script Commands

Command Description

sinap_pidclean Kills all processes registered with the SINAP/SS7 system and deletes their queue IDs

drda_stop_links Stops all active links in the network

sleep Ensures the SS7 driver daemon terminates before the script continues

remove_shm Deletes the shared memory the SINAP/SS7 system allocated



N O T EIf, during SINAP/SS7 installation, you requested that the SINAP/SS7 system be started from the file, /etc/inittab (the UNIX initialization file), then the SINAP/SS7 system processes are automatically restarted once the stop_sinap script has finished executing. To stop the SINAP/SS7 system, you must first edit the /etc/inittab file and change the SINAP/SS7 entry shown in the following example from respawn to off. Then, execute stop_sinap script.

0$SINAP_INDEX:234:respawn:$SINAP_HOME/Bin/sinapinit > /dev/null


Chapter 3 Software Configuration3-

This chapter describes the configuration requirements and limitations for SINAP/SS7 software.

Configuration Requirements Table 3-1 shows the requirements and limitations for the basic SINAP configuration parameters. See the appropriate appendix for additional configuration parameters specific to the CCITT, ANSI, TTC, NTT, and China network variants of the SINAP/SS7 software.

You must configure a unique set of links, link sets, and route sets for each SINAP node running on a module (a single system). Two nodes cannot use the same physical communication path.

Table 3-1. Configuration Requirements and Limitations (Page 1 of 9)

Item Limitation or Support

Maximum number of signaling links 128 per SINAP module. The total for all nodes must not exceed 128.

Note: You can only configure 128 links on the Continuum Series 400 systems equipped with PA-8500 or PA-8600 processors and on Stratus ft Linux systems.

Maximum IOA cards per Continuum Series 400 & 400-CO systems with PA-8000 processor

PA-8500 and PA-8600 processors

U403 = 8 cards (4 Links per card) U420 = 4 cards (8 Links per card)

U403 = 8 cards (4 Links per card) U420 = 8 cards (8 Links per card)U916 = 8 cards (32 Links per card)

Maximum IOA cards per Netra 20/T4†or SunFire V480 system

U915 or U916 = 3 cards (32 Links per card)

Maximum IOA cards per Stratus ft Linux T30 platform (ftServer T30 including NEBS compliance)

U918 = 4 cards (32 Links per card)

Software Configuration 3-1

Configuration Requirements

Network variants supported on U403, U420 cards:CCITT / ANSI / China / TTC / NTT Yes

Network variants supported on U916, U915 cards:CCITT / ANSI

China / TTC / NTT

Yes

No

Network variants supported on U918 cards:CCITT / ANSI

China / TTC / NTT

Yes

No

Link operating speeds supported:CCITT / ANSI / China

TTC / NTT

4.8, 9.6, 19.2, 38.4, 56, 64 kbit/sIf you are creating an ARTIC synchronous link, you must specify a link speed of 0 if you connect to a modem or other device that provides external clocking.

Supports baud rates of 4800, 48,000, or 64,000.

Maximum number of link sets 16 per node (a module with 4 nodes can have a maximum of 64)

Maximum number of links per link sets 16

Maximum number of routes per route set:CCITT / TTC / NTT / China

ANSI

8

4

Maximum number of route sets 2048 per node (a module with 4 nodes can have a maximum of 8192)

Maximum number of load-shared routes 2

Load sharing for route sets supported:CCITT / TTC / NTT / China

ANSI

Yes

No

Maximum number of destination point codes (DPCs)

2048 per node (a module with 4 nodes can have a maximum of 8192)





Maximum number of DPCs reachable by one link set


Maximum number of concerned point codes (CPCs)

64 per local SSN (Up to 512 can be accommodated with a special patch. Contact the CAC for more information.) Note: The TTC and NTT network variants support CPCs only if the environment variable TTC_WITH_NSTATE is defined.

Maximum number of duplicate concerned point codes (DUCPCs):CCITT / ANSI / China

TTC / NTT

1 per local SSN

No

Distributed logical point codes (DLPCs) supported:CCITT / ANSI / China

TTC / NTT

Yes, if DLPC is configured on the SINAP node via the /etc/config_sinap script.

No

Maximum number of logical point codes (LPCs) allowed for registered processes:CCITT / ANSI / China

TTC / NTT

16 per node in addition to own signaling point code (only if DLPC feature is configured on the node via the /etc/config_sinap script.)

No

Application failure detection with notification to backup DLPC application supported:CCITT / ANSI / China

TTC / NTT

Yes (only if DLPC feature is configured on the node via the /etc/config_sinap script.)

No

Maximum number of applications registered with SINAP


Maximum number of processes registered with the SINAP node that can run concurrently

255 per node

Instances per application 16 instances per application





drda_daemon processes 1 per node (a module with 4 nodes can have a maximum of 4)

Maximum number of links per combined link set (CLS)ANSI

CCITT / TTC / NTT / China

32 links (2 link sets) per CLS

Not supported

Combined link sets supported:CCITT / TTC / NTT / China

ANSI

No

Yes - 4 per node (a module with 4 nodes can have a maximum of 16)

Signaling Connection Control Part (SCCP) message modes supported:

CCITT / China

TTC / NTT / ANSI

Note: Connectionless: Class 0 (unsequenced) and Class 1 (sequenced), Connection-oriented: Class 2 and Class 3

Class 0, 1, 2, 3

Class 0, 1

XUDT and XUDTS message handling supported:CCITT / China

TTC / NTT / ANSI

Yes

No

SCCP addresses supported for destination point code (DPC) and originating point code (OPC):CCITT

TTC / NTT

ANSI / China

14-bit point code format



Global title translation (GTT) supported:CCITT / TTC / NTT / ANSI / China Yes

Partial GTT supported:CCITT/TTC/ NTT / ANSI / China Yes, if the environment variable

PARTIAL_GTT is defined.





SCCP backup routing for GTT only supported:CCITT

TTC / NTT / ANSI / China

Yes, if the environment variable GTT_WITH_BACKUP_DPC_SSN=1 is defined.

No

Global title (GT) addressing supported:CCITT / TTC / NTT / ANSI / China Yes

Connection-oriented features (COF) supported:CCITT / China

TTC / NTT / ANSI

Yes

No

Number of link-congestion levels supported:CCITT / China

ANSI / TTC / NTT

Three optional congestion levels:• International one congestion onset and

one congestion abatement

• National multiple states with congestion priority option

• National multiple congestion states without congestion priority

(Default is international one congestion onset and one congestion abatement if no environment variable is set to define link congestion levels)

National multiple congestion states with congestion priority automatically implemented

ISUP service features supported:CCITT / NTT / China / ANSI

TTC

Yes, if ISUP_FEATURE environment variable is defined (see the SINAP/SS7 ISDN User Part (ISUP) Guide (R8053)

Not supported





MTP signaling point restart supported:CCITT and China

TTC / NTT

ANSI

Yes, if MTP_WHITE_BOOK_RESTART environment variable is defined. Default is CCITT 1988 network processing.

No

Yes, if MTP_ANSI92_RESTART environment variable is defined. Default is ANSI 1990 network processing with no restart processing.

MTP user part unavailable (UPU) messages and user flow control (UFC) supported:CCITT / ANSI / China

TTC / NTT

Yes

No

Fictitious originating point code (FOPC) supported:CCITT / TTC / NTT / China

ANSI

No

Yes

Signaling network messages (SNM) with non-zero SLCs supported:CCITT/China

TTC / NTT

ANSI

Yes (MTP_WHITE_BOOK_SLC environment variable must be defined)

No

Yes (no need to set an environment variable)

MTP time-controlled changeover (TCCO) supported:CCITT/China

TTC/NTT

ANSI

Yes, CCITT 1988 TCCO is the default. To implement CCITT 1993 TCCO processing, define the environment variable MTP_WHITE_BOOK_TCCO.

Yes (automatically implemented)

Yes, ANSI 1990 TCCO is the default. (Implemented automatically if MTP restart is enabled; otherwise, you must set the environment variable MTP_ANSI92_TCCO)





Time-controlled diversion (TCD) supported:CCITT / TTC / NTT / China

ANSI

Yes (Implemented automatically; no environment variable must be set)

Yes (Implemented automatically if MTP restart is enabled; otherwise, you must set the environment variable MTP_ANSI92_TCD)

Remote processor outage control (POC) supported:CCITT / ANSI / China

TTC / NTT

Yes

No

Local processor outage control (POC) supported:CCITT / TTC / NTT / ANSI / China No

Preventive cyclic retransmission (PCR) supported:CCITT / TTC / NTT / ANSI / China No

International network indicator supported:CCITT / TTC / NTT / China

ANSI

Yes

No

Loopback detection supported:CCITT

TTC / NTT / ANSI / China

Yes, if the environment variable LOOPBACK_DISPLAY is set.

No

Transfer-restricted message handling supported:CCITT

TTC / NTT / China

Yes, if the environment variable MTP_WHITE_BOOK_TFR is defined.

No





Transfer-restricted message handling supported: (cont.)ANSI Yes, implemented automatically (according to

1992 ANSI Standards); no environment variable needs to be set. To configure the node according to the1988 ANSI standards, set the environment variable MTP_ANSI88_RSR_RST. See the section, “RSR/RSP in Response to TFR/TFP,” later in this chapter for more information.

Even distribution of messages by routing solely on SLS and DPC supported:CCITT / China

TTC / NTT / ANSI

Yes, if the MTP_SLS4_LOAD_SHARE environment variable is defined before starting or restarting the SINAP/SS7 system.

No

Selection of 5-bit or 8-bit Signaling Link Selection (SLS) processing schemes for all incoming and outgoing traffic supported:CCITT / TTC / NTT / China

ANSI

No

Yes (Specified using the CHANGE_SLSTYPE command; default is 5-bit processing)

Custom Application Distribution (CAD) supported:CCITT / ANSI

TTC / NTT / China

Yes

No

Maximum number of ServiceKey values per application (CAD):ANSI / CCITT

TTC / NTT / China

64

No

Maximum number of ServiceKeys supported for a specific SSN/OPC criteria (CAD):ANSI / CCITT

TTC / NTT / China

256

No




Link Performance Recommendations

Link Performance RecommendationsTo improve the SINAP/SS7 system performance, Stratus recommends the following:

• When assigning links to a link set, make sure the number of links in the link set can be evenly divided into the number 16, for example, 1 link per link set or 2, 4, 8, or 16 links per link set. This method of link assignment makes the best use of the signaling link selection (SLS) algorithm, which facilitates load sharing among the links in the link set.

When the number of links in the link set cannot be divided evenly into 16, the SLS algorithm assigns some links more SLS values than other links. This uneven assignment of SLS values has the potential to cause some links in the link set to become severely congested and to possibly fail. For example, if there are 10 links in a link set, links 1 through 6 are each assigned two SLS values and links 7 through 10 are each assigned only one SLS value. If the link set is passing 1600 messages per second, links 1 through 6 will each be assigned approximately 200 outbound messages per second. The uneven SLS distribution will cause severe congestion (and possible failure) of links 1 through 6.

Maximum number of fallback applications supported for a specific SSN/OPC criteria (CAD):ANSI / CCITT

TTC / NTT / China

1 (Value specified for ServiceKey must be 0)

No

Maximum number of SSNs per application (Enhanced Distribution and CAD):CCITT / ANSI

TTC / NTT / China

32

No

Maximum number of OPCs per application (Enhanced Distribution and CAD):CCITT / ANSI

TTC / NTT / China

128

No

Dynamic change of OSPCCITT / TTC

ANSI / NTT / China

Only if OSP_UPDATE_ENABLED environment variable defined

No

† Note that Sun Microsystems refers to this model as either “Netra 20 Server” or “Netra T4”, but it is referred as “Netra 20/T4” in SINAP documentation to avoid the confusion.




Configuring the Terminal Handler

Configuring the Terminal HandlerThe Terminal Handler is the user interface, which provides a way to generate SINAP/SS7 Man Machine Language (MML) commands. You configure the terminal handler separately for each SINAP node you are running.

The interface offers two operating modes: the menu selection mode, which contains a system of interactive menus and prompts, and the free-form mode, in which you enter a command at a command line. In the menu selection mode you select a series of menu options and enter information as prompted to create and issue a command. The Terminal Handler appends the options you choose and the information you enter to an MML command fragment until the command is complete.

The UNIX .login or .profile file (in the $SINAP_HOME/Sysopr directory), or .bash_profile (if bash is set for the SINAP user login on Stratus ft Linux systems), contains two environment variables related to the SINAP/SS7 menus: SINAP_MML and SINAP_MDF. The SINAP_MML environment variable maintains the MML command and displays the command as the Terminal Handler builds it. By displaying the MML command fragment as the command is being built, the SINAP/SS7 system lets you view the syntax for commonly used commands. In this way, you can build commands using free-form mode, or complete an MML command fragment started with the menu system. The menu system interprets any keystrokes that do not select a menu system option or function as free-form input.

Defining Privilege Levels for MML CommandsFor each node, the SINAP/SS7 system maintains a global MML definition file (mmlverb) that defines the list of MML commands it recognizes. This file also maintains the privilege level associated with each MML command and its destination process in the SINAP/SS7 system. When users log in to the Terminal Handler, they are assigned privilege levels based on their user classes (defined in .profile or .login, or .bash_profile (if bash is set for the SINAP user login on Stratus ft Linux systems)). Thus, users can send only those MML commands that have privilege levels less than or equal to their privilege levels.

To specify privilege levels for a node, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file and assign a value between 0 and 255 before starting the SINAP node.

SINAP_MML_LEVEL=<VALUE>

No privilege level is associated with MML commands sent to application processes. Application processes are defined only in the menu definition file (MDF), so this restriction does not apply to them. See “Defining Options in the Menu Definition File” for an explanation of this function.

Following is an entry from the mmlverb file. Note that you can edit the values in the Level field to change the permission level of a command. The Destination field contains information about the node, module, process, and application.



In this example, the commas represent the current node and module, NM represents the Network Management subsystem, and CM represents the Command Management process of node management.

Command Level DestinationBACKUP-NODE 5 ,,NM,CM

Defining Menu Options in the Menu Definition FileTo build menus for the Terminal Handler to display, you specify menu options in the Menu Definition File (MDF). The MDF uses a predefined set of operators in a sequence of menu definitions. This set of operators lets you tailor menu operations to accommodate changing operating methods and changing menu progression. Each user on a SINAP node must define a set of operators when configuring the node.

The SINAP_MDF environment variable is set to $SINAP_HOME/Sysopr/sinap_variant/mml/mdf at the UNIX .login or .profile, or .bash_profile (if bash is set for the SINAP user login on Stratus ft Linux systems) file under the $SINAP_HOME/Sysopr directory when a SINAP node is configured using /etc/config_sinap, where sinap_variant can be ansi, ccitt, china, ntt, or ttc.

The first menu defined in the MDF is the main menu (the menu that appears when you enter the menu system). The SINAP/SS7 system provides one MDF that can generate all defined MML commands. However, a menu system that includes all available commands might not be appropriate for all classes of users. For example, a user responsible for statistics collection might only be interested in menus that generate the MML commands for collecting statistics. To provide for this user, you can copy the supplied MDF and modify it, or create a new MDF. You can also modify the user’s privilege level. There can be more than one MDF with an individual definition assigned to a class of users.

Menu Definition OperatorsMenu definition operators allow the system administrator to control menu progression, operation, and menu operator interaction. Each menu operator begins at the first column in a line and is entirely contained within that line. The menu definition operators are described in alphabetical order in Table 3-2.

• MENU.BEGIN

• MENU.END

• MENU.HELP

• MENU.NAME

• OPTION

• OP.BUILD

• OP.DEST



• OP.ENDREQ

• OP.HELP

• OP.MENU

• OP.SCRIPT

• # (Comment operator)

Table 3-2. Menu Definition Operators (Page 1 of 6)

Operator Description

MENU.BEGIN The MENU.BEGIN operator marks the beginning of the option definition portion of the menu and specifies the menu title that appears on the screen above the menu options. The MENU.BEGIN operator follows the MENU.HELP operator in the MDF.

Format: MENU.BEGINmenu_title

The menu_title argument is a quoted string of up to 50 characters.

Man page format: menubegin

MENU.END The MENU.END operator marks the end of the option definition portion of the menu. The MENU.BEGIN and the MENU.END operators enclose the option definition portion of the menu. The MENU.END operator follows the last OP operator of the last option defined on the menu.

Man page format: menuend



MENU.HELP The MENU.HELP operator specifies the file containing help information relevant to the menu. The MENU.HELP operator follows the MENU.NAME operator. If you want to use help files, you must create your own and store them in $SYSOPR_HOME/sinap_variant/help, where sinap_variant can be ansi, ccitt, china, ntt, or ttc. You must also create your own script files and store them in $SYSOPR_HOME/sinap_variant/script. Help and script file names are limited to 14 characters.

Format: MENU.HELPhelp_filename

The help_filename argument specifies the help file to be used with this menu. Specify the help file as the file name without the path name. The help file is limited to eight lines of text. Each line can contain a maximum of 76 characters.

Man page format: menuhelp

MENU.NAME The MENU.NAME operator names a menu and is the first entry of each menu defined in the MDF.

Format: MENU.NAMEmenu_name

The menu_name argument specifies the name of a particular menu. It must begin with an alphabetic character and be followed by up to nine alphanumeric characters that uniquely identify this particular menu in the MDF.

Man page format: menuname

OPTION The OPTION operator begins an option definition block within a menu definition and specifies the text that appears on the screen to describe the option. The key that invokes the defined option is implicitly assigned by where the option definition is in the option definition portion of the menu. For example, the second option definition is assigned the second option key. The OPTION operator precedes the OP operators that define the option in the MDF.

Format: OPTIONdescription

The description argument is a quoted string of up to 50 characters that describes the option being defined.

Man page format: option





OP.BUILD The OP.BUILD operator appends a text string to the MML command being built and follows the OP.DEST operator in the MDF.

Format: OP.BUILDappend_string

The append_string argument is a quoted string of up to 50 characters that specifies the string to be appended to the MML command being built.

Man page format: opbuild

OP.DEST The OP.DEST operator designates the destination address for the recipient of MML commands generated when you define a menu option. The OP.DEST operator follows the OP.HELP operator in the MDF. This command is not required.

Format: OP.DESTdestination

Note: The OP.DEST operator is the only way you can specify the destination of MML commands that the menu system sends to the application processes. These MML commands should be different from the SINAP/SS7 MML commands. For an example of how this command is used, see the SINAP/SS7 Programmer’s Guide (R8052).

The following code fragment shows how a script file new_cmd.scr builds a command called NEW-CMD. When the command is built, it is sent to the destination you specified in the OP.DEST field of the script file.

The destination argument specifies the destination address of the process to receive the MML commands in the format: node,module,subsystem,process. (Commas are included in the format.) If you omit the node and module specification, the system assumes the current Terminal Handler node and module.



OPTION “New Command Script” OP.HELP new_cmd.help OP.DEST ,,TCAP,SEND OP.BUILD “NEW-CMD:” OP.SCRIPT new_cmd.scr

AB

CD

E



OP.DEST(cont.)

Option definition block. See the description of the OPTION operator in this chapter.

Name of the help file for the new command; you must create this help file and store it in $SYSOPR_HOME/sinap_variant/help where sinap_variant can be CCITT, ANSI, China, NTT, or TTC.

Names under which application and process are registered. Name of the new command. Name of the script file associated with the new command. See the

description of OP.SCRIPT.

Man page format: opdest

OP.ENDREQ The OP.ENDREQ indicates the end of required parameters and appends a semicolon (;) to the MML commands. This operator sends the MML command any time after the required parameters and before all the optional parameters are set.

Format: OP.ENDREQ

All required arguments are grouped at the beginning of the command, while all optional arguments are grouped at the end of the command. The Terminal Handler appends a semicolon to the end of the MML command to terminate it before sending it out. The OP.ENDREQ operator follows the OP.SCRIPT operator in the MDF. The OP.ENDREQ command is required.

The following code fragment shows how the REPORT-ALARM command is defined in the SINAP/SS7 menu definition file. Here, the OP.ENDREQ signals the end of all optional parameters and appends a semicolon to the MML command.

Man page format: opendreq



A

B

CDE

OPTION “Report Alarm” OP.HELP rptalarm.help OP.BUILD “REPORT-ALARM:”OP.SCRIPT date.scr OP.ENDREQ



OP.HELP The OP.HELP operator specifies the file containing help information relevant to the option topic. The OP.HELP operator follows the OPTION operator in the MDF.

Format: OP.HELPfile_name

The file_name argument is the name of the help file containing the relevant help information. Specify this name without the path name. If you want to use help files, you must create your own and store them in $SYSOPR_HOME/sinap_variant/help where sinap_variant can be ansi, ccitt, china, ntt, or ttc. The help file is limited to eight lines of text. Each line can contain a maximum of 76 characters.

Man page format: ophelp.

OP.MENU The OP.MENU operator specifies the next menu name. A user can specify the current menu, allowing the menu system to re-enter the screen. The menu system maintains a trail of menus and the status of the MML command fragment when it leaves a menu. This information lets a user move backwards through the selected menu progression and return to the MML fragment relevant to a previous screen. The OP.MENU operator follows the OP.ENDREQ operator in the MDF.

Format: OP.MENUmenu_name

The menu_name argument is the name of the target menu, assigned when you use the MENU.NAME operator, or one of the following predefined menu names:

- EXITMENU—Exits the Terminal Handler. The Terminal Handler asks for confirmation before exiting.- NULLMENU—Indicates that no other menus follow. The Terminal Handler remains in the current menu after executing any script specified with the OP.SCRIPT operator. Use this menu with options whose purpose is to run a utility script.- SENDMENU —The Terminal Handler uses this menu internally. Do not use this name as a value for menu_name.

Man page format: opmenu





The following example illustrates the power of an MDF. The example generates four MML commands.

• DISPLAY-LINK

• DISPLAY-LSET

• DISPLAY-RSET

• DISPLAY-SYSTAB

One way to accomplish this task is to provide an initial menu that differentiates between system table requests and other types of display requests, and follow that menu with independent submenus that collect parameters. These submenus then end on a common menu that determines print options. This menu organization is shown in Figure 3-1.

OP.SCRIPT The OP.SCRIPT operator invokes a user-supplied UNIX script file. You can invoke a script that reads input from the menu operator, combines with the current MML command fragment in SINAP_MML, and returns a new MML command fragment in SINAP_MML. In this way, a script customizes the qualification of input and provides flexibility in the way MML commands generate. The OP.SCRIPT operator follows the OP.BUILD operator in the MDF file name.

Format: OP.SCRIPTfile_name

The file_name argument specifies the name of the file (excluding the path name) that contains the required UNIX shell script. You must create your own script files and store them in $SYSOPR_HOME/sinap_variant/script where sinap_variant can be ansi, ccitt, china, ntt, or ttc. Script file names are limited to 14 characters.

Man page format: opscript

# (Comment operator)

The comment operator (#) provides descriptive text in the MDF. The comment begins with the number sign character (#) in the first column and extends to the end of the line.

Format: # text

The text argument is any descriptive text.

Man page format: comoper





.

Figure 3-1. Menu Organization for Sample Menu Definition File

The MDF to generate the commands for a typical menu is shown in the following program sample:

#Sample MDF File

#

#EXITMENU, NULLMENU, and SENDMENU are reserved names.

#EXITMENU is used to exit from the Terminal Handler.

#NULLMENU is used to indicate no menu follows (menu option used

#for running script).

Display Network Information

1. Timers and Thresholds

2. Link, Link Set, Route Set

3. Exit Menu

Timers and Thresholds

1. Display Timer

2. Display Threshold

Link, Link Set, Route Set

1. Display Link

2. Display Link Set

3. Display Route Set

Print Options

1. Display on Terminal Only

2. Display on Terminal and Printer



#SENDMENU is used to the Terminal Handler to indicate

#MML command send menu.

#

# ====Primary Menu - Display

MENU.NAME DISPLSCRN

MENU.HELP displscrn.hlp

MENU.BEGIN “Display Network Information”

# ++++Specify Timer and Threshold

OPTION “Timers and Thresholds”

OP.HELP tithopt.hlp

OP.BUILD “DISPLAY”

OP.MENU TITHSCRN

# ++++Specify Link, Link Set, Route Set Option

OPTION “Link, Link Set, Route Set”

OP.HELP tithopt.hlp

OP.BUILD “DISPLAY”

OP.MENU LLRSCRN

# ++++Specify Quit Option

OPTION “Exit Menu (RETURN to UNIX)”



OP.HELP exit.hlp

Op.MENU EXITMENU

MENU.END

# ====Timer and Threshold Screen

MENU.NAME TITHSCRN

MENU.HELP tithscrn.hlp

MENU.BEGIN “Timers and Thresholds”

# ++++Specify Timer Option

OPTION “Display Timer”

OP.HELP timeropt.hlp

OP.BUILD “TIMER=”

# Invoke Script to Read, Validate and Append Timer Field

OP.SCRIPT parsethresh

OP.MENU PRINTSCRN

MENU.END

# ====Link, Link Set, and Route Set Screen

MENU.NAME LLRSCRN

MENU.HELP llrscrn.hlp



MENU.BEGIN “Link, Link Set, and Route Sets”

# ++++Specify Link Options

OPTION “Display Link”

OP.HELP linkopt.hlp

OP.BUILD “-LINK:LINK=”

# Invoke Script to Read, Validate and Append Link Field

OP.SCRIPT parselink

OP.MENU PRINTSCRN

# ++++Specify Link Set Option

OPTION “Display Link Set”

OP.HELP lsetopt.hlp

OP.BUILD “-LSET:LINKSET=”

# Invoke Script to Read, Validate and Append Link Set Field

OP.SCRIPT parselset

OP.MENU PRINTSCRN

# ++++Specify Route Set Option

OPTION “Display Route Set”

OP.HELP rsetopt.hlp



OP.BUILD “-RSET:ROUTESET=”

# Invoke Script to Read, Validate and Append Route Set Field

OP.SCRIPT parserset

OP.MENU PRINTSCRN

MENU.END

# ====Print Screen

MENU.NAME PRINTSCRN

MENU.HELP printscrn.hlp

MENU.BEGIN “Print Options”

# ++++Specify Terminal Only Option

OPTION “Display on Terminal Only”

OP.HELP termopt.hlp

OP.BUILD “,PRINT=NO”

#

#OP.MENU not specified. Terminal Handler switches automatically

#to the MML command send menu when this option is selected.

#

# ++++Specify Terminal and Printer Option



OPTION “Display on Terminal and Printer”

OP.HELP termprtopt.hlp

OP.BUILD “,PRINT=YES”

#OP.MENU not specified. Terminal Handler switches automatically

#to the MML command send menu when this option is selected.

MENU.END

Terminal Handler Screen PartitionsThe Terminal Handler screen contains 24 lines. The SINAP/SS7 system partitions the lines into dedicated sections. Sections are defined for the SINAP/SS7 banner, MDF-defined menu, MML command fragment, alarm and event notification area, and diagnostic, prompt, and response area. Figure 3-2 shows how these areas map to the 24-line screen.



Figure 3-2. SINAP/SS7 Terminal Screen Partitions

The screen areas contain the following information:

• Line 1 —SINAP/SS7 banner information

• Line 2—Section separator

• Lines 3 through 13—MDF-defined menu areas

• Line 14 —Section separator

• Lines 15 through 17—MML command fragment display

• Line 18—Section separator

• Lines 19 through 23—Alarm and event notification area

• Line 24—User prompt and diagnostic area

Line 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 >MML Command Fragment 16 17 18 19 20 21

? Diagnostic, Prompt and Response Area

22 23 24

SINAP USERID, LEVEL nn mode

MDF-Defined Title1. MDF-Defined Option 12. MDF-Defined Option 23. MDF-Defined Option 3 . . .

Alarm/Event Notification Area



Once you issue an MML command, a screen containing information about the command appears. Figure 3-3 shows a sample informational screen for the DISPLAY-LINK command.

Figure 3-3. Screen Layout for a Specific Command

The screen areas in Figure 3-3 contain the information described in Table 3-3.

Table 3-3. Description of Line Fields for Command Screens (Page 1 of 2)

Line Number Description

Line 1 SINAP/SS7 banner information, including the node, module, process, and application names, the user ID, permission level, and the mode. In Figure 3-3, the node is N1, the module is M1, and the process running is the Node Management process. The sysopr user with permission level 5 is issuing the DISPLAY-LINK command. The Terminal Handler is in menu mode.

Line 2 Section separator

SINAP N1,M1,NM,TH,1 User: sysopr, Level: 5 Menu Mode

N1,M1,NM,CM 2004-03-02 13:23:14M DISPLAY-LINK:LINK=ALL; ok command completed

Display Link:

LinkName Link LSetName LSet SLC Port Speed ADPC State Status ErrorLink0 0 lset1 0 0 0 64000 3003 ACTIV iabclrnt 0Link1 1 lset1 0 1 1 64000 3003 ACTIV iabclrnt 0

--Link Status Legend--i - installed I - not installeda - available A - not availableb - not remotely blocked B - remotely blockedc - not congested C - congestedl - not locally inhibited L - locally inhibitedr - not remotely inhibited R - remotely inhibitedn - link normal U - status unavailable F - link failedt - no periodic link test T - periodic link test active

?Hit (Q or q) to quit displaying response


Creating Network Components

Creating Network Components To provision the SINAP/SS7 system, you first create the necessary components, such as links, link sets, and route sets, using the CREATE commands from the Terminal Handler.

Some components must be created before others. To configure your network, create the network components in the following order:

1. Own signaling point (OSP) code

2. Link set

3. Combined link set (nodes with ANSI network variant only)

4. Links

5. Route set

6. Concerned point code (CPC)

N O T ECPCs are not supported for the TTC and NTT network variants unless the TTC_WITH_NSTATE environment variable is set.

7. Duplicate concerned point code (DUCPC) (not used for the TTC and NTT network variants)

8. Remote subsystem numbers (SSN)

9. Global title translation (GTT)

10. Fictitious originating point code (FOPC) (nodes with ANSI network variant only)

Lines 3–5 MML response header area. In Figure 3-3, the header indicates the Command Management process of Node Management is the source responding to the DISPLAY-LINK command.

Line 6 Section separator

Lines 7–23 MML response data. In Figure 3-3, the area shows the data returned by the DISPLAY-LINK command with the ALL argument.

Line 24 Diagnostic and user prompt area

Table 3-3. Description of Line Fields for Command Screens (Page 2 of 2)

Line Number Description



N O T EThe link sets, links, and route sets you create through the Create Commands menu are initially in an inactive state. You must activate these commands through the Configure Commands menu (using the Configure Link, Configure Linkset, and Configure Routeset commands).

Figure 3-4 shows a sample configuration for National Network 0 (NAT10). The example shows one node (OxAAA) with an own signaling point (OSP) code of 2730 connected to an adjacent node (OxBBB) with a point code of 3003. The remote SSNs for the adjacent OxBBB node are 253 and 254. The nodes are connected by one route (rset1), one link set (lset1), and two links in the link set (lnk1 and lnk2).

N O T ESamples used in this manual are for the CCITT network variant unless otherwise noted.

Figure 3-4. Sample Network Configuration for National Network 0

SPC = OxAAA (2730)SSN = 253, 254

SPC = OxBBB (3003)

Network: NAT10

lnk2

lnk1lset1

rset1



The commands in Figure 3-5 set up this configuration at signaling point code (SPC) 2730 (or hex AAA). Note that the CONFIGURE-LINK command executes automatically when the CONFIGURE-LSET command is issued.

Figure 3-5. Commands for Creating the Sample Configuration

The remainder of this section describes the process required to configure the sample shown in Figure 3-4. Screen samples illustrate each step.

From the Create Commands menu, the Terminal Handler provides interactive prompts to help you create commands to configure each component, including all necessary argument values.

CREATE-OSP:NETWORK=NAT10,SPC=2730;CREATE-LSET:LINKSET=lset1,ADPC=3003,ACTLINK=2,LOADLINK=2;CREATE-LINK:LINK=LNK1,PORTNUM=0,LINKSET=lset1,SLC=0,PRIORITY=1,SPEED=64K; CREATE-LINK:LINK=LNK2,PORTNUM=1,LINKSET=lset1,SLC=1,PRIORITY=2,SPEED=64K; CREATE-RSET:ROUTESET=rset1,DPC=3003,ROUTES=lset1,LOADSHR=DISABLE;CREATE-CPC:LSSN=253,RPC=3003; CREATE-CPC:LSSN=254,RPC=3003;CREATE-DUCPC:LSSN=253,RPC=3003; CREATE-DUCPC:LSSN=254,RPC=3003;CREATE-GTT:GTT=4,TT=1,NP=0,NOAI=1,LADDR=18005551212, HADDR=18005554444, DPC=3003,SSN=2,NADDR=15;CREATE-REMSSN:PC=3003,SSN=253&254;CONFIGURE-LSET:LINKSET=lset1,STATE=ACTIVE;CONFIGURE-RSET:ROUTESET=rset1,STATE=ACTIVE;



To create the sample National Network 0, start from the SINAP System Main Menu, shown in Figure 3-6, and perform the following steps to access the Create Commands menu.

Figure 3-6. SINAP System Main Menu

N O T EDo not press RETURN when making a selection from a menu or a prompt. This sends an incomplete command to the system. Press RETURN only after entering a value in answer to a prompt with the format KEYWORD=, where KEYWORD is a particular value related to the task being performed.

1. Enter 2 from the SINAP System Main Menu to select Network Commands. The Network Commands menu appears, as shown in Figure 3-7.

Figure 3-7. Network Commands Menu

SINAP N1,M1,NM,TH,1 User: sysopr, Level: 5 Menu Mode SINAP System Main Menu1. System Commands2. Network Commands3. Application Commands4. BITE Commands5. Exit Menu

>

?

SINAP N1,M1,NM,TH,1, User: sysopr, Level: 5 Menu mode

Network Commands 1. Create 2. Configure 3. Change 4. Display 5. Delete 6. Dump Table 7. Measurements



2. Enter 1 to display the Create Commands menu. The Create Commands menu appears. The menu options differ depending on the network variant you are using. The next three figures show the menu options for each network variant. Figure 3-8 shows the menu options for the CCITT and China network variants.

Figure 3-8. Create Commands Menu for CCITT and China Variants

Figure 3-9 shows the menu options for the ANSI network variant. It offers additional options for creating a combined link set and a Fictitious Originating Point Code (FOPC).

Figure 3-9. Create Commands Menu for the ANSI Variant

Figure 3-10 shows the Create Commands menu options for the TTC and NTT network variants. The TTC network variant does not support the Create Duplicate Point Code option.

Create Commands 1. Create Link 2. Create Linkset 3. Create Routeset 4. Create Own Point Code 5. Create Concerned Point Code 6. Create Duplicate Point Code 7. Create Remote SSN 8. Create Global Title

< CREATE

Create Commands 1. Create Link 2. Create Linkset 3. Create Combined Linkset 4. Create Routeset 5. Create Own Point Code 6. Create Concerned Point Code 7. Create Duplicate Point Code 8. Create Remote SSN 9. Create Fictitious Originating Point Code A. Create Global Title

< CREATE



Figure 3-10. Create Commands Menu for the TTC and NTT Variants

3. Press CTRL-P at the prompt to return to the previous menu. Press CTRL-B at the prompt to return to the SINAP System Main Menu.

Each option on the Create Commands screen is described in a following section. The CCITT network variant is used in all examples, unless noted otherwise. Differences in network variants are noted.

Creating an Own Point Code The first step in setting up network components is to define a node by creating an own signaling point (OSP) code.

Perform the following steps to create an OSP:

1. From the Create Commands menu, enter the number for the Create Own Point Code option. The CREATE-OSP screen appears. The Terminal Handler prompts you to specify the CREATE-OSP command arguments. The OSP shown in the following sample screen

Create Commands 1. Create Link 2. Create Linkset 3. Create Routeset 4. Create Own Point Code 5. Create Concerned Point Code 6. Create Remote SSN 7. Create Global Title

< CREATE



shows entries created for the sample network configuration in Figure 3-4. User entries are

in bold type.

2. When prompted, enter the appropriate values for your network and press RETURN after each entry. Table 3-4 describes the CREATE-OSP command arguments.

Table 3-4. CREATE-OSP Command Arguments


NETWORK The network name for which the point code is configured. Enter 2 or 3 to specify a national network. Enter 0 or 1 to specify an international network. For the TTC and NTT network variant, the only menu choice is 0 (National Network 0), which creates the value, TTCNAT, in the MML command line. Specify NETWORK=TTCNAT when entering the MML command in the free-form mode.

Note: The 4-bit service indicator (SI) of the service information octet (SIO) can accommodate up to 16 Message Transfer Part (MTP) users or services such as SCCP, Integrated Services Digital Network User Part (ISUP), or Telephone User Part (TUP) under one network. If you have more than 16 services, specify both international or national network options, as appropriate, to act as an expansion option.

For example, if you specify 2 (NAT10) and you have 18 services, you can select 3 (NAT11) as an expansion option for services 17 and 18.

SPC The signaling point code (SPC). When you issue an MML command that requires you to specify a point code, you must use the appropriate point code format for the type of stack you are running. See the appropriate appendix for your network variant.

MML as built is CREATE-OSP:Specify network name, possible choices are: 0 - INAT00 (International Network 0) 1 - INAT01 (International Network 1) 2 - NAT10 (National Network 0) 3 - NAT11 (National Network 1)Choice=2NETWORK=NAT10Specify signalling point code (0-16383): SPC=2730

NETWORK=NAT10,SPC=2730< CREATE-OSP:



3. The Terminal Handler processes your entries and prompts you to issue the CREATE-OSP command with the values you specified. Press RETURN to send the MML command to the system, as shown in the following sample screen.

4. The SINAP/SS7 system creates the OSP and redisplays the command with a message confirming the command successfully executed. The following sample response screen is shown here, but not shown again in this chapter. Enter Q or q to quit displaying the response.

5. Press CTRL-P to return to the Create Commands menu or CTRL-B to return to the SINAP System Main Menu.

MML Command FormatThe MML command format for the CREATE-OSP command is:

CREATE-OSP:Network=network,SPC=spc;

See Table 3-4 for a description of the arguments.


MML Send Menu

< CREATE-OSP:NETWORK=NAT10,SPC=2730;

? Hit Enter to Send MML Command

SINAP N1,M1,NM,TH,1, User: sysopr, Level: 5 Display response

N1,M1,NM,CM 1998-01-15 06:36:19M CREATE-OSP:NETWORK=NAT10,SPC=2730; command completed




N O T EThe SINAP user can define OSP_UPDATE_ENABLED environment variable so as to change the existing OSP without deleting all network elements (or MMLs as shown at Figure 3-5 as example). This feature is support for the CCITT and TTC network variants only. If OSP_UPDATE_ENABLED is not defined and OSP already exists, this command returns an error message because only one OSP can exist at any one time. To enable this feature, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node. This environment variable has no value assigned to it. The SINAP node only verifies the existence of the variable. OSP_UPDATE_ENABLED=1

W A R N I N GFor OSP_UPDATE_ENABLED feature: MSU’s will be discarded due to the failure of MTP discrimination check if the MSUs sent by the remote node do not have a DPC corresponding to the new OSP just being changed. Also, SS7 links will not come into service due to the failure of SLT, if the DPC configured for the link-set at the adjacent node is not the same as the new OSP.

Man Page Format

The alternative and UNIX online manual page (man page) format for CREATE-OSP is crte-osp.

Creating a Link SetAfter you define a node, you can define the required link sets. A link set is a set of signaling links directly connecting two signaling points. Later, you will populate the sets with the member links.

Perform the following steps to create a link set:

1. From the Create Commands menu, enter the number designating Create Linkset. The CREATE-LSET screen appears. The Terminal Handler prompts you to specify the CREATE-LSET command arguments. The link set shown in the following sample screen shows entries created for the sample network configuration in Figure 3-4. User entries are



in bold type.

2. When prompted, enter your network configuration values and press RETURN after each entry. Table 3-5 describes the CREATE-LSET command arguments.

Table 3-5. CREATE-LSET Command Arguments (Page 1 of 2)


LINKSET The name of the link set

ADPC The point code for the adjacent node. When you issue an MML command that requires you to specify a point code, you must use the appropriate point code format for the type of stack you are running. See the appendix for your network variant for more information about own point codes.

TYPE(ANSI only)

The link set type. This prompt only applies to the ANSI network variant.

Specify one of the following values; A, E, or F for the specific signaling link connection for the link set.

A specifies access link (A-link) pairs that connect signaling points in the network to their home STP pair.

E specifies extended access links (E-link) that provide a link to any other STP pair in the signaling network in addition to the A-link.

F specifies fully associated links (F-link) that allow the links to communicate directly with each other from point to point.

MML as built is CREATE-LSET:Specify link set name: LINKSET=lset1LINKSET=lset1Specify Signalling Point Code of the adjacent node (0-16383)ADPC=3003LINKSET=lset1,ADPC=3003Specify number of links that are to be load shared across (1-16)LOADLINK=2LINKSET=lset1,ADPC=3003,LOADLINK=2Specify number of links to be activated (1-16)should be greater than or equal to LOADLINKACTLINK=2LINKSET=lset1,ADPC=3003,LOADLINK=2,ACTLINK=2



3. The Terminal Handler processes your entries, displays the completed command on your screen, and prompts you to issue the CREATE-LSET command. Press RETURN to send the displayed MML command to the system, as shown in the following sample screen.

.

4. The SINAP/SS7 system creates the link set, displays the message again, and confirms successful execution. Enter Q or q to quit displaying the response.

TYPE(ANSI only) (cont.) If the Distributed Logical Point Code (DLPC) feature is configured

on the SINAP node, you can also configure the following link types:

B specifies bridge links that connect STP pairs.

D specifies diagonal links which connect STP pairs that function at different hierarchical levels (for example, local and regional STP pairs)

For DLPC configuration, F links are not allowed. For more detailed information, see the SINAP/SS7 ISDN User Part (ISUP) Guide (R8053).

LOADLINK The number of links within linkset or combined linkset to be load shared. The TTC and NTT network variants support a maximum of 8 links per link set. All other variants support 16 links.

ACTLINK The number of links to be activated. The TTC and NTT network variants support a maximum of 8 links per link set. All other variants support 16 links.

Table 3-5. CREATE-LSET Command Arguments (Page 2 of 2)



MML Send Menu

< CREATE-LSET:LINKSET=lset1,ADPC=3003,LOADLINK=2,ACTLINK=2;





MML Command FormatThe MML command format for the CREATE-LSET command differs slightly for the various network variants.

The CCITT, China, and TTC network variant format is:

CREATE-LSET:LINKSET=linkset,ADPC=adpc,LOADLINK=loadlink, ACTLINK=actlink;

The ANSI network variant format is:

CREATE-LSET:LINKSET=linkset,ADPC=adpc,TYPE=type,LOADLINK= loadlink,ACTLINK=actlink;

See Table 3-5 for descriptions of the MML command arguments.

Man Page FormatThe alternative and man page format for CREATE-LSET is crte-lset.

Creating a Combined Link Set (ANSI Only)A combined link set is a load-sharing collection of one or more link sets. The CREATE-CLSET command is supported by SINAP ANSI network variant only.

Perform the following steps to create a combined link set:

1. From the Create Commands menu, enter the number for Create Combined Linkset. The CREATE-CLSET screen appears. The Terminal Handler prompts you to specify the arguments for your network configuration. The combined link set shown in the following sample screen shows entries created for the sample network configuration in Figure 3-4. User entries are in bold type.

MML as built is CREATE-CLSET:Specify combined link set name: CLSET=clsta CLSET=clstaSpecify Member Linkset 1LSET1=lset1 CLSET=clsta,LSET1=lset1Specify Member Linkset 2LSET2=lset2 CLSET=clsta,LSET1=lset1,LSET2=lset2



2. When prompted, enter your network configuration values and press RETURN after each entry. Table 3-6 describes the CREATE-CLSET command arguments.

Because a combined link set requires a pair of link sets, make sure a pair already exists before provisioning the combined link set.

3. The Terminal Handler processes your entries and prompts you to issue the CREATE-CLSET command with the values you defined. Press RETURN to send the CREATE-CLSET command to the system.

4. The SINAP/SS7 system creates the combined link set, displays the command again, and confirms successful execution. Enter Q or q to quit displaying the response.


MML Command FormatThe MML command format for the CREATE-CLSET command is:

CREATE-CLSET:CLSET=clset,LSET1=linkset1,LSET2=linkset2;


Man Page FormatThe alternative and man page format for CREATE-CLSET is crte-clset.

Table 3-6. CREATE-CLSET Command Arguments


CLSET The name of the combined link set

LSET1 The first link set member

LSET2 The second link set member


MML Send Menu

< CREATE-CLSET:CLSET=clsta,LSET1=lset1,LSET2=lset2;




Creating a LinkA link is a signaling link directly connecting two signaling points. Create member links for the link sets you previously defined.

Perform the following steps to create a link:

1. From the Create Commands menu, enter the number for Create Link. The CREATE-LINK screen appears. The Terminal Handler prompts you to specify the CREATE-LINK command arguments. The link shown in the following sample screen shows entries created for the sample network configuration shown in Figure 3-4. User entries are in bold type.

2. When prompted, enter your network configuration values and press RETURN after each entry. Table 3-7 describes the CREATE-LINK command arguments.

Table 3-7. CREATE-LINK Command Arguments (Page 1 of 2)


LINK The name of the link

PORTNUM The port number. This can be a number from 0 through 127.

LINKSET The name of the link set with which the link is associated. This value must already exist.

SLC The signaling link code (SLC) for the link. Valid values for the CCITT, ANSI, and China network variants are 0–15. Valid values for the TTC and NTT network variants are 0–7.

Note: The SLC value must match the SLC value on the STP to which the link(s) connect or the link(s) will not align.

MML as built is CREATE-LINK:Specify link name: LINK=lnk1LINK=lnk1Specify port number (0-127): PORTNUM=0LINK=lnk1,PORTNUM=0Specify link set name: LINKSET=lset1LINK=lnk1,PORTNUM=0,LINKSET=lset1Specify Signalling Link Code (0-15): SLC=0LINK=lnk1,PORTNUM=0,LINKSET=lset1,SLC=0Specify priority of the link (0-15): PRIORITY=1LINK=lnk1,PORTNUM=0,LINKSET=lset1,SLC=0,PRIORITY=1Specify link speed (0,4800,9600,19200,38400, 56000 or 56K, 64000 or 64K): SPEED=64KLINK=lnk1,PORTNUM=0,LINKSET=lset1,SLC=0,PRIORITY=1,SPEED=64K



Because any link is defined by its link set and the link code within it, the link set must exist before you can provision its member link(s). A link is inactive when created.

N O T EThe port number is the device listed in the /etc/SS7links file for the particular input/output adapter subsystem (IOA) card. For example, the following sample entry indicates the T1/E1 card in bay 2, slot 3, channel (time slot) 6 has a port number of 5 (this

PRIORITY The unique priority assigned to the link. The valid values for the CCITT, ANSI, and China network variants are 0–15, with 0 being the highest priority. The valid values for the TTC and NTT network variants are 0–7.

Determine the priority of the link by considering its importance. Because traffic is sent over each link according to its priority, higher priority links take precedence. When links are load shared, traffic is distributed evenly over the links.

SPEED The transmission rate for the link. For the TTC and NTT network variants, you must define the link’s speed as 0, 4800, 48000, 48K, 64000, or 64K baud. For all other variants, you must define the link’s speed as 0, 4800, 9600, 19200, 38400, 56000, 56K, 64000, or 64K baud.

If you are creating an ARTIC synchronous link, you must specify a link speed of 0 if you are connecting to a device that provides external clocking, such as a modem. Otherwise, specify a baud rate up to 64000.

Table 3-7. CREATE-LINK Command Arguments (Page 2 of 2)




information is added during link configuration via /etc/config_sinap "l" option):

device = /dev/rsd/ss7_0203006 wan = /dev/rsd/wan_0203006 jitter = PH_BYPASS signalling = PH_SIG_MOS loopback = PH_NO_LOOPBACK carrier = PH_LC_CEPT distance = PH_DX_PQ_SHORT format = PH_FRM_CRC_4 coding = PH_LC_HDB3 master_clock = PH_MASTER_CLOCK prmclk = PH_CLOCK_PORT_1 bkupclk1 = PH_CLOCK_PORT_2 bkupclk2 = PH_CLOCK_PORT_3 bkupclk3 = PH_CLOCK_PORT_4;link = 5 device = /dev/rsd/ss7_0203006 slot = 6;

This link and its partner on the remote node must be configured with the same signaling link code (SLC) value. If they do not have the same SLC value, the two links cannot communicate.

The device file information is saved in the /etc/SS7links file. To review the device file information, enter the following command at the UNIX prompt:

cat /etc/SS7links

3. The Terminal Handler processes your entries and prompts you to issue the CREATE-LINK

command with the values you defined. Press RETURN to send the CREATE-LINK command to the system, as shown in the following sample screen.


MML Send Menu

< CREATE-LINK:lnk1,PORTNUM=0,LINKSET=lset1,SLC=0,PRIORITY=1,SPEED=64K;




4. The SINAP/SS7 system creates the link, displays the command again, and confirms successful execution. Enter Q or q to quit displaying the response.


6. Repeat the procedure described in steps 1 through 5 to provision additional required links, such as lnk2.

MML Command FormatThe MML command format for the CREATE-LINK command is:

CREATE-LINK:LINK=link,PORTNUM=portnum,LINKSET=linkset,SLC= slc,PRIORITY=priority,SPEED=speed;


Man Page FormatThe alternative and man page format for CREATE-LINK is crte-link.

Creating a Route SetA route set contains up to eight routes for CCITT/TTC/NTT/China network variants and up to four routes for the ANSI variant. Each route defining a path over which the SINAP/SS7 system can pass traffic to a particular node, according to its destination point code (DPC).

N O T EFor the ANSI variant, this can also be a combined link set (CLS) of a configured route (2 link sets of a route), and up to the same number of link sets as can be configured for the CCITT/TTC/NTT/China variants (8) for four routes of the CREATE-RSET command.

Designate routes by defining the link set to be used for the first part of each route. Because route set provisioning requires valid routes (link sets), you must provision the link sets before adding them to the route. Before using CREATE-RSET, provision at least one link for the link set you are designating as a route.

The status of any newly created route set is blocked. No traffic can pass over a blocked route. Therefore, after creating a route set, you must activate the route set through the Configure Commands menu (using the Configure Routeset option).

N O T E S1. In the CCITT or China network variants of the SINAP/SS7

system, MTP-boundary users can ensure even distribution



of messages by routing solely on the signaling link selection (SLS) and destination point code (DPC). To enable the SLS and DPC routing set, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before (re)starting the SINAP node.

MTP_SLS4_LOAD_SHARE=1

2. In the CCITT network variant, whenever a new route set is created and configured for a remote signaling point in the network (and not for an adjacent point code), the route set should be initialized to the PROHIBITED state. To ensure proper initialization, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before (re)starting the SINAP node.

RST_CONFIG_INIT_PROHIBIT=1

If the MTP_SLS4_LOAD_SHARE environment variable is not set, the default action for CCITT, TTC, NTT, and CHINA variants is to support 16 links per link set, with a random choice of link set when load sharing. This ensures even distribution, but not sequentiality.

Note that this option does not affect the TCAP or SCCP user. It also does not affect the ISUP user, as link set selection and link selection over a possible 16 links per link set is done transparently to the user by the SINAP ISUP code.

Perform the following steps to create a route set:

1. From the Create Commands menu, enter the number for Create Routeset. The CREATE-RSET screen appears. The Terminal Handler prompts you to specify the CREATE-RSET command arguments. The route set shown in the following sample screen shows entries created for the sample network configuration in Figure 3-4. User entries are



in bold type.

MML as built is CREATE-RSET:Specify route set name: ROUTESET=rset1ROUTESET=rset1Specify signalling point code of this route set (0-16383):DPC=3003ROUTESET=rset1,DPC=3003Specify routes used to reach the destination:(LSET or LSET1&LSET2... up to 8 routes)ROUTES=lset1ROUTESET=rset1,DPC=3003,ROUTES=lset1Specify load sharing enabled [Y/N]:nROUTESET=rset1,DPC=3003,ROUTES=lset1,LOADSHR=DISABLE



2. When prompted, enter your network configuration values and press RETURN after each entry. Table 3-8 describes the CREATE-RSET command arguments.

3. The Terminal Handler processes your entries and prompts you to issue the CREATE-RSET command with the values you defined. Press RETURN to send the CREATE-RSET command to the system, as shown in the following sample screen.

Table 3-8. CREATE-RSET Command Arguments


ROUTESET The route set name. Use a label containing up to 15 characters.

ROUTES The routes that a message uses to reach its destination. Specify routes by listing one or more link sets to be used for the first hop of each route. To define a link set, use the label you assigned when creating the link set. You can create a list of up to eight routes (CCITT/TTC/NTT/China) or 4 routes (ANSI) separated by ampersands (&). For example, LSET1&LSET2&LSET3. The order of the routes indicates priority, with the first being the highest priority.

For the ANSI network variant of the SINAP/SS7 system, note that only one linkset containing type A links and one link set containing type F links can be used.

if the Distributed Logical Point Code (DLPC) feature is configured on the SINAP node, you can also configure B-links and D-links, but F-links are not allowed. For more information on implementing the DLPC feature, see the SINAP/SS7 ISDN User Part (ISUP) Guide (R8053).

DPC The signaling point code for the route set. When you issue an MML command that requires you to specify a destination point code, you must use the appropriate point code format for the network variant configured for the node. See the appropriate appendix for information on the point code format for your network variant.

LOADSHR The status of load sharing. Enter y to enable load sharing, or n if you do not want to enable load sharing. LOADSHR only applies to the CCITT, TTC, NTT, and China network variants.



4. The SINAP/SS7 system creates the route set, displays the command again, and confirms successful execution. Enter Q or q to quit displaying the response.


MML Command FormatThe MML command format for the CREATE-RSET command is:

CREATE-RSET:ROUTESET=routeset,DPC=dpc,ROUTES=routes[&routes],LOADSHR=loadshr;


Man Page FormatThe alternative and man page format for CREATE-RSET is crte-rset.

Creating a Concerned Point CodeA concerned point code (CPC) is a point code which defines the relationship between a remote point code and an application subsystem number (SSN) on the local SINAP node. It is used to notify SS7 of a failure or a coordinated changeover notification for a particular subsystem.

N O T EThe TTC and NTT network variant does not support CPCs unless the TTC_WITH_NSTATE environment variable is defined before starting the SINAP/SS7 system. See Appendix B for instructions for setting environment variables.

Perform the following steps to create a CPC using the CREATE-CPC command:

1. From the Create Commands menu, enter the number for Create Concerned Point Code. The CREATE-CPC screen displays. The Terminal Handler prompts you to specify the


MML Send Menu

< CREATE-RSET:rset1,DPC=3003,ROUTES=lset1,LOADSHR=DISABLE;




CREATE-CPC command arguments. The CPC shown in the following sample screen shows entries created for the sample network configuration previously shown in Figure 3-4. User entries are in bold type.

2. When prompted, enter your network configuration values and press RETURN after each entry. Table 3-9 describes the CREATE-CPC command arguments.

3. The Terminal Handler processes your entries and prompts you to issue the CREATE-CPC command with the values you defined. Press RETURN to send the CREATE-CPC command to the system, as shown in the following sample screen.

Table 3-9. CREATE-CPC Command Arguments


LSSN The local subsystem number (LSSN).

RPC The replicate point code (RPC). When you issue an MML command that requires you to specify a point code, you must use the appropriate point code format for the type of stack you are running (CCITT, ANSI, TCC, NTT or China network variants). See the appropriate appendix for the point code format for the network variant you are using.

Note: You can create a list of up to 64 remote point codes separated by ampersands (&). You can enter up to 25 point codes at a time.

MML as built is CREATE-CPC:Specify local subsystem number: LSSN=253LSSN=253Specify point codes of the remote node (at most 64 PCs):(pc# or pc#1&pc#2... up to pc#25) 25 at a timeRPC=476&477&478&479&480&481&482&483&484&485&486&487&488



N O T EIf you created many CPCs, the system may truncate the entries (all entries may not appear on the display). To see all CPC values, use the DISPLAY-CPC command.

4. The SINAP/SS7 system creates the CPC, displays the command again, and confirms successful execution. Enter Q or q to quit displaying the response.


MML Command FormatThe MML command format for the CREATE-CPC command is:

CREATE-CPC:LSSN=ssn,RPC=pc[&pc];


Man Page FormatThe alternative and man page format for CREATE-CPC is crte-cpc.

Creating a Duplicate Concerned Point CodeA duplicate concerned point code (DUCPC) is a duplicate point code for a specified subsystem of the local node. Only one DUCPC per local subsystem number (LSSN) is allowed. It acts as a backup of the primary application and takes over processing when the primary application goes out of service. The TTC and NTT network variants do not support DUCPCs.

Perform the following steps to create a DUCPC:

1. From the Create Commands menu, enter the number for Create Duplicate Point Code. The CREATE-DUCPC screen appears. The Terminal Handler prompts you for the CREATE-DUCPC command arguments. The DUCPC shown in the following screen

SINAP N0,M1,NM,TH,1 User: sinap0, Level: 5 Display response

N0,M1,NM,CM 1999-10-16 18:39:35M CREATE-CPC:LSSN=253,RPC=476&477&478&479&480&481&48 ok command completed




contains values for the sample network configuration in Figure 3-4. User entries are in bold type.

2. When prompted, enter your network configuration values and press RETURN after each entry. Table 3-10 describes the CREATE DUCPC arguments.

3. The Terminal Handler processes your entries and prompts you to issue the CREATE-DUPC command with the values you defined. Press RETURN to send the CREATE-DUPC command to the system, as shown in the following sample screen.

4. The SINAP/SS7 system creates the DUCPC, displays the command again, and confirms successful execution. Enter Q or q to quit displaying the response.


Table 3-10. CREATE-DUCPC Command Arguments


LSSN The local subsystem number (LSSN) for the DUCPC

RPC The replicate point code (RPC) of the DUCPC. When you issue an MML command that requires you to specify a point code, you must use the appropriate point code format for the type of stack you are running. See the appendix that describes your network variant.

MML as built is CREATE-DUCPC:Specify local subsystem number: LSSN=253LSSN=253Specify replicate point code: RPC=3003LSSN=253,RPC=3003


MML Send Menu

< CREATE-DUCPC:LSSN=253,RPC=3003;




MML Command FormatThe MML command format for the CREATE-DUCPC command is:

CREATE-DUCPC:LSSN=ssn,RPC=pc;


Man Page FormatThe alternative and man page format for CREATE-DUCPC is crte-ducpc.

Creating a Remote Subsystem NumberCreating a remote subsystem number (SSN) enables the Node Management subsystem to maintain the status of remote subsystems.

Follow these steps to create a remote SSN:

1. From the Create Commands menu, enter the number for Create Remote SSN. The CREATE-REMSSN screen appears. The Terminal Handler prompts you to specify the CREATE-REMSSN command arguments. The remote subsystems shown in the following sample contain entries for the sample network configuration in Figure 3-4. User entries are in bold type.

2. When prompted, enter your network configuration values and press RETURN after each entry. Table 3-11 describes the CREATE-REMSSN arguments.

Table 3-11. CREATE-REMSSN Command Arguments


PC The point code (PC) for the remote node. When you issue an MML command that requires you to specify a point code, you must use the appropriate point code format for the type of stack you are running. See ‘‘Creating an Own Point Code” for the correct point code formats for the various network variants.

SSN The remote SSN. You can list up to 10 subsystem numbers separated by ampersands (&).

MML as built is CREATE-REMSSN:Specify point code of remote node: PC=3003PC=3003Specify subsystem numbers of the remote subsystem(ssn# or ssn#1&ssn#2... upto ssn#10)SSN=253&254PC=3003,SSN=253&254



3. The Terminal Handler processes your entries and prompts you to issue the CREATE-REMSSN command with the values you defined. Press RETURN to send the CREATE-REMSSN command to the system, as shown in the following sample screen.

4. The system creates the remote SSN with the specified point code and SSNs. The Terminal Handler displays the command again and confirms successful execution. Enter Q or q to quit displaying the response.


MML Command FormatThe MML command format for the CREATE-REMSSN command is:

CREATE-REMSSN:PC=pc,SSN=ssn[&ssn];


Man Page FormatThe alternative and man page format for CREATE-REMSSN is crte-remssn.

Creating a Fictitious Originating Point CodeAny stack with the network variant (MTP/SCCP) defined as ANSI supports the fictitious originating point code (FOPC). The CCITT, TTC, NTT, and China network variants do not support FOPCs.

An FOPC defines the originating point code (OPC) the SINAP/SS7 system uses in MTP routing labels in place of the calling party’s OPC. Using an FOPC allows the SINAP/SS7 system to set the OPC fields in the MTP routing label to any OPC, including the label’s node’s OSP. This functionality is typically used in handover processing, where one application process hands off processing to another application process. For more information, see the SINAP/SS7 Programmer’s Guide (R8052).


MML Send Menu

< CREATE-REMSSN:PC=3003,SSN=253&254;




If an FOPC already exists, this command returns an error message because only one FOPC can exist at any one time. To create a new FOPC, first delete the existing FOPC. (See the sections on displaying and deleting FOPC information in Chapter 4 of this manual.)

Before you start the SINAP/SS7 system, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file.

ANSI_SINAP_FOPC=YES

After starting the SINAP/SS7 system, perform the following steps to create an FOPC:

1. From the Create Commands menu, enter the number for Create Fictitious Originating Point Code. The system displays the CREATE-FOPC screen.

The Terminal Handler prompts you to specify the SPC to use as the FOPC, using the format: FOPC=Network-Cluster-Member where:

Network = a number in the range 1–254 Cluster = a number in the range 1–255 Member = a number in the range 1– 255

The FOPC shown in the following sample screen contains entries for the sample network configuration in Figure 3-4. User entries are in bold type.

2. When prompted, enter the appropriate point code for your network configuration and press RETURN after the entry.

MML as built is CREATE-FOPC:Specify the signalling point code <Network-Cluster-Member>Network: 1-254Cluster: 1-255Member : 1-255SPC=1-1-1SPC=1-1-1



3. The Terminal Handler processes your entries and prompts you to issue the CREATE-FOPC command with the values you defined. Press RETURN to send the CREATE-FOPC command to the system, as shown in the following screen.

4. The system creates the FOPC with the specified values. The Terminal Handler displays the command again and confirms successful execution. Enter Q or q to quit displaying the response.


MML Command FormatThe MML command format for the CREATE-FOPC command is:

CREATE-FOPC:FOPC=Network-Cluster-Member;

Man Page FormatThe alternative and man page format for CREATE-FOPC is crte-fopc.

Creating a Global Title Translation (GTT) Entry for a NodeA global title (GT) is a type of address, such as a series of dialed digits, that does not itself contain the addressing information necessary to route a message signaling unit (MSU) to its destination. Instead, SCCP must perform global title translation (GTT), a process that translates the global title into addressing information that can then be used to route a message to its destination.

N O T E S1. By default, global title values for the LADDR, HADDR, and

NADDR address components are displayed in strings of up to 28 decimal (0 - 9) characters in length. Hexadecimal characters (0 - 9 and A - F) can be used in place of the decimal characters by uncommenting the following environment variable in the


MML Send Menu

< CREATE-FOPC:SPC=1-1-1;




$SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

HEX_GLOBAL_TITLE=1

2. If you want to bypass GTT by the SINAP/SS7 SCCP and implement global title addressing capability at the user application program instead, uncomment the environment variable, BYPASS_SINAP_GLOBAL_TITLE_TRANSLATION in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting or restarting the SINAP node. This allows the SINAP node to pass messages containing a GT to the user application without actually translating the GT at the SCCP layer.

For SCCP to perform GTT, you must provide information about how you want each global title translated. You do this by creating global title entries using the CREATE-GTT command. Each entry describes a particular global title and specifies how it should be translated. You can define a maximum of 4000 global title entries. You can specify a global title to be translated into a DPC, SSN, a new global title, or any combination thereof. The global title entry is stored in a segment of shared memory known as the GTT table.

N O T EThe GTT table is not a table in the true sense of the word; it is simply a storage area for global title entries.

SCCP performs GTT when the address indicator of the SCCP’s called party address of an inbound or outbound message is set to indicate routing on GT.

Global Title FormatA global title consists of several different types of address components, each defining a particular characteristic of the global title. The global title format, as defined by the global title indicator (GTI), determines the address components that are included in a global title.



Table 3-12 describes the address components that make up a global title. See the appropriate documentation for your network variant for more information on GTT components.

Table 3-13 lists the global title format associated with each GTI value. Note that the global title formats differ slightly between the network variants.

Table 3-12. Global Title Address Components

Address Component Description

Global Title Indicator (GTI)

Indicates the global title format. The GTI value specifies which address components are included in the global title.

Translation Type (TT) Directs the MSU to the appropriate global title translation function.

Numbering Plan (NP) Indicates the numbering plan used for the global title’s address information (for example, ISDN/Telephony, ISDN/Mobile, or data).

Encoding Scheme (ES) The part of the numbering plan that indicates the type of encoding, if any, that is used. The SINAP/SS7 system uses the ES to determine whether the global title address information is an odd (ES=1) or even (ES=2) number of BCD digits.

Nature-of-Address Indicator (NOAI)

Indicates the type of number used in the global title (for example, a subscriber number, a national significant number, or an international number). Not used for the ANSI network variant. Note: The default valid range for this indicator is 1 through 4. Setting the GTT_BYPASS_NOAI_CHECK environment variable expands the range to 0 through 127.

Table 3-13. GTI Values and Global Title Formats

CCITT, China, TTC, and NTT Global Title Formats

ANSI Global Title Formats

GTI Value Global Title Contents

GTI Value Global Title Contents

0 No global title 0 No global title

1 NOAI only 1 TT, NP, and ES†

2 TT only 2 TT only

3 TT, NP, and ES

4 TT, NP, ES, and NOAI



The CREATE-GTT command creates a global title entry describing a global title and how it should be translated.

The following list describes how the CREATE-GTT command arguments (see tables) correspond to the global title’s address components:

• The GTI, nature-of-address indicator (NOAI), translation type (TT), and numbering plan (NP) arguments define the address components included in the global title, as determined by the GTI. For example, a global title with a GTI of 1 contains the NOAI and LADDR address components. A global title with a GTI of 4 contains the TT, NP, NOAI, and LADDR address components.

• The LADDR and HADDR arguments define the global title’s address information.

• The DPC, SSN, and NADDR arguments define alternate DPC, SSN, and/or global title address information that replaces the original global title.

• (For the CCITT network variant only) The DPC2 and SSN2 arguments define the new DPC and SSN information if the original SCCP is unavailable.

To perform GTT, the SINAP/SS7 system compares the global title in the SCCP called-party address to global title entries. If the global title matches one of the entries, SCCP translates the global title into a new DPC, a new SSN, and/or new address information, based on the information in that entry.

A match occurs when all the global title’s address components are the same as the values in a particular global title entry. To compare the address information in a global title to the address information in a global title entry, both sets of address information must be the same length. For example, the string 180055512 (which is 9 digits long) would not match the global titles in the range, 1800555111 to 1800555444 (which are each 11 digits long).

Alternate SCCP RoutingThe CCITT network variant has the optional ability to route global title-related MSUs to an alternate or “backup” SCCP if the “primary” one is unavailable.

Two types of GTTs can result in MSUs being sent to the backup DPC and/or SSN. The two GTT types are:

• RouteOnGT

• RouteOnSSN

RouteOnGT is a type of translation where the global title is translated into another global title that requires a further GTT at a remote DPC’s SCCP. For RouteOnGT, the status of any remote subsystems would usually be immaterial. To prevent testing the availability of the remote

† The global title formats for ANSI GTI 1 and CCITT/China/TTC/NTT GTI 3 are identical.



subsystems, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

GLOBAL_TITLE_SSN_NO_CHECK=1

RouteOnSSN is a type of translation where the global title is locally translated into a remote DPC and SSN. For RouteOnSSN, the availability status of the remote subsystem is important and the MML should create the appropriate remote subsystem entries.

During normal system operation, the SINAP/SS7 system translates the global title either to another global title for translation at a remote primary DPC (RouteOnGT) or to MSUs for processing at a remote primary DPC (RouteOnSSN). If the primary is not operational, the SINAP/SS7 system attempts to route the information to the backup DPC or SSN (DPC2 or SSN2).

To specify an alternate SCCP, specify the DPC2 and/or the SSN2 parameters. When the DPC parameter is specified (is not NONE), you can specify the DPC2 parameter to define a different DPC for backup routing. Similarly, when the SSN parameter is specified, you can use the SSN2 parameter to define a different SSN for backup routing.

To enter the parameters using the Terminal Handler, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

GTT_WITH_BACKUP_DPC_SSN=1

N O T EIt is not necessary to set this environment variable if entry of all new fields is sent via send_cm. Use the existing syntax for CREATE-GTT, but add the SSN2= and the DPC2= fields to the entry.

To input the command through send_cm, use the existing syntax for CREATE-GTT, but add the fields SSN2= and DPC2= to the entry to specify the alternate SCCP. For example,

send_cm -s ”CREATE-GTT:GTI=4,TT=8,NP=7,NOAI=2,LADDR=500000, HADDR=999999,SSN=254,SSN2=253,DPC=2730,DPC2=2731;”

N O T E S1. This command must be entered on one line only.



2. Because the parsing is position-independent, you can use a different order of keywords, for example:

send_cm -s “CREATE-GTT:GTI=4,TT=8,NP=7,NOAI=2,LADDR=500000,HADDR=999999,DPC=2730,SSN=254, DPC2=2731,SSN2=253;”

3. Values for the LADDR, HADDR, and NADDR global title address components can be displayed in either decimal or hexadecimal character formats. If the HEX_GLOBAL_TITLE environment is not set, then decimal is the default character format. If the variable is set, then hexadecimal is the active character format. Refer to the section “Using Hexadecimal Values in GTT Strings” for more information.

The sample command above indicates to the SINAP/SS7 system that, for this global title, if the SCCP for DPC 2730 is out of service, the global title must be translated at the designated remote SCCP, DPC 2731. Also, if the global title has been locally translated and DPC 2730/SSN 254 is out of service, the results of the global title will be transferred to DPC 2731/SSN 253.

For backward compatibility, it is not necessary to specify the DPC2 or SSN2 fields if this feature is not desired.

If the primary and secondary SCCPs are both unavailable, the SINAP/SS7 system returns a NOTICE error message.

Using Hexadecimal Values in GTT StringsThe SINAP/SS7 system provides an optional feature that allows you to use hexadecimal values (A through F) in addition to numeric values (0 through 9) in GTT strings. To enable this feature, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

HEX_GLOBAL_TITLE=1

If you do not activate this environment variable, you will only be able to use numeric digits in GTT strings.

Steps to Create a GTT EntryFollow these steps to create a GTT entry for a node:

1. From the Create Commands menu, enter the number for Create Global Title. The CREATE-GTT screen appears. The Terminal Handler prompts you for the CREATE-GTT



command arguments. The global title indicators shown in the following sample screen are entries for the sample network configuration in Figure 3-4. User entries are in bold type.

2. Enter appropriate values for your network configuration using the CREATE-GTT command argument values described in Table 3-14. Press RETURN after each entry.

MML as built is CREATE-GTT:Specify Global Title Indicator: GTI=4GTI=4Specify Translation Type: TT=1GTI=4,TT=1Specify Numbering Plan: NP=0GTI=4,TT=1,NP=0Specify Nature Of Address Indicator: NOAI=1GTI=4,TT=1,NP=0,NOAI=1Specify Low Address Information: LADDR=18005551212GTI=4,TT=1,NP=0,NOAI=1,LADDR=18005551212Specify High Address Information [Default=NONE]: HADDR=18005554444GTI=4,TT=1,NP=0,NOAI=1,LADDR=18005551212,HADDR=18005554444Specify Replacement Destination Point Code [Default=NONE]: DPC=3003GTI=4,TT=1,NP=0,NOAI=1,LADDR=18005551212,HADDR=18005554444,DPC=3003Specify Replacement Subsystem Number [Default:NONE]: SSN=2GTI=4,TT=1,NP=0,NOAI=1,LADDR=18005551212,HADDR=18005554444,DPC=3003,SSN=2Specify Replacement Address Information [Default=NONE]: NADDR=NONEGTI=4,TT=1,NP=0,NOAI=1,LADDR=18005551212,HADDR=18005554444,DPC=3003,SSN=2,NADDR= NONE



Table 3-14. CREATE-GTT Command Arguments (Page 1 of 4)


GTI Specifies the global title indicator. The value of this argument indicates the addressing components included in the global title. The global title formats associated with each value differ slightly between network variants as indicated:

CCITT/TTC/NTT/China Global Title Formats:

GTI ValueGlobal Title Contents0No global title1NOAI only2TT only3TT and NP4TT, NP, and NOAI

ANSI Global Title Formats:

GTI ValueGlobal Title Contents0No global title1TT and NP*2TT only* The global title formats for ANSI GTI 1 and CCITT/China/TTC/NTT GTI 3 are identical.

TT Specifies the translation type, which directs the message to the appropriate global title-translation function. Valid values are in the range 0 through 254. For the CCITT, China, TTC, and NTT network variants, include this argument if the GTI is 2, 3, or 4. For the ANSI network variant, include this argument if the GTI is 1 or 2.

NP Specifies the numbering plan used for the address information in the global title (for example, ISDN/Telephony, data, or ISDN/Mobile). Include this argument if the GTI is 3 or 4 for the CCITT, China, TTC, and NTT network variants or if the GTI is 1 for the ANSI network variant. Valid values are in the range 0 through 14.



NOAI Specifies the nature-of-address indicator, which identifies the type of number used in the global title (for example, subscriber, national significant, or international). Include this argument if the GTI is 1 or 4 for the CCITT, China, TTC, and NTT network variants.

If the GTT_BYPASS_NOAI_CHECK environment variable is not defined for a node, the valid values are in the range of 1 through 4. If the GTT_BYPASS_NOAI_CHECK environment variable is defined for a node, the valid range is from 0 through 127. The variable must be defined for each node in a SINAP/SS7 environment.

For the ANSI network variant, do not specify a value for this field.

LADDR Specifies the low address (starting values) of a range of global titles. If you do not specify haddr, the global title’s address information must exactly match the laddr value in order to match the global-title entry. If you specify haddr, the laddr value specifies the low address (the start) of a range of global titles, and any global title between laddr and haddr will match this global-title entry.

Define this argument as a string of decimal digits (if the environment variable HEX_GLOBAL_TITLE is not set) or hexadecimal characters (if the environment variable HEX_GLOBAL_TITLE is set) whose length does not exceed 28 character positions in length.

The value of laddr must be less than or equal to the value of haddr. If you specify a GTI of 2, you must define the global title’s address information as an even number of digits (for example, 100000 or 9999).

In addition, the address information in the global title must be the same length as this value; otherwise, SCCP cannot compare the two values.





HADDR Specifies the high address (the end) of a range of global titles. A match on this global-title entry occurs with any global title whose address information (including its length) matches an address in the range laddr to haddr.


The value of haddr must be greater than or equal to the value of laddr. If you specify a GTI of 2, you must define the global title’s address information as an even number of digits (for example, 155555 or 100000).

For the global title translation to be valid (that is, for SCCP to have addressing information with which to replace the original global title), you must include at least one of the following three arguments in the CREATE-GTT command line:

DPC Specifies the DPC to substitute for the original DPC. If you omit this argument, SCCP does not replace the DPC during translation. Format this field appropriately for the variant you are using. Valid values are 1 through 16383. See the appendix which describes your network variant.

SSN Specifies the SSN to substitute for the original SSN. If you omit this argument, SCCP does not replace the SSN during translation. Valid values are in the range of 2 to 255.





NADDR Specifies address information to substitute for any address information included in the global title.


• If you specify this argument, SCCP replaces address information in the global title and sets the routing-indicator bit of the SCCP called-party address to 0 to specify routing on global title.

• If you omit this argument, SCCP does not replace address information in the global title during translation. In addition, SCCP sets the routing-indicator bit of the SCCP called-party address to 1 to specify routing on DPC/SSN.

For the CCITT variant only, you can optionally include one or both of the following arguments to provide “backup” or alternate SCCP routing if the primary SCCP is unavailable.

DPC2 Specifies the DPC to use if the primary SCCP is unavailable. Valid values are 1 through 16383.

DPC2=<backup DPC>or DPC2=NONE

SSN2 Specifies the SSN to use if the primary SCCP is unavailable. Valid values are 2 through 255.

SSN2=<backup SSN>orSSN2=NONE





3. The Terminal Handler processes your entries and prompts you to issue the CREATE-GTT command with the values you defined. Press RETURN to send the CREATE-GTT command to the system, as shown in the following sample screen.

4. The SINAP/SS7 system creates the GTT with the specified values. The Terminal Handler displays the command again and confirms successful execution. Enter Q or q to quit displaying the response.


MML Command FormatThe MML command formats for CREATE-GTT with GTI values 1–4 for the CCITT network variant include backup SCCP routing capability and are as follows:

CREATE-GTT:GTI=1,NOAI=noai,LADDR=laddr [,HADDR=haddr] {,DPC=dpc |,DPC2=dpc2|,SSN=ssn |,SSN2=ssn2|,NADDR=naddr};

CREATE-GTT:GTI=2,TT=tt,LADDR=laddr [,HADDR=haddr] {,DPC=dpc |,DPC2=dpc2|,SSN=ssn |,SSN2=ssn2|,NADDR=naddr};

CREATE-GTT:GTI=3,TT=tt,NP=np,LADDR=laddr [,HADDR=haddr] {,DPC=dpc |,DPC2=dpc2|,SSN=ssn |,SSN2=ssn2|,NADDR=naddr};

CREATE-GTT:GTI=4,TT=tt,NP=np,NOAI=noai,LADDR=laddr [,HADDR=haddr] {,DPC=dpc |,DPC2=dpc2|,SSN=ssn |,SSN2=ssn2|,NADDR=naddr};


MML Send Menu

< CREATE-GTT:GTI=4,TT=1,NP=0,NOAI=1,LADDR=18005551212,HADDR=18005554444,DPC=3003,DPC2=3004,SSN=2,SSN2=3,NADDR=NONE;




The MML command formats for CREATE-GTT with GTI values 1–4 for the China, TTC, and NTT network variants are as follows:

CREATE-GTT:GTI=1,NOAI=noai,LADDR=laddr [,HADDR=haddr] {,DPC=dpc | ,SSN=ssn | ,NADDR=naddr};

CREATE-GTT:GTI=2,TT=tt,LADDR=laddr [,HADDR=haddr] {,DPC=dpc | ,SSN=ssn | ,NADDR=naddr};

CREATE-GTT:GTI=3,TT=tt,NP=np,LADDR=laddr [,HADDR=haddr] {,DPC=dpc | ,SSN=ssn | ,NADDR=naddr};

CREATE-GTT:GTI=4,TT=tt,NP=np,NOAI=noai,LADDR=laddr [,HADDR=haddr] {,DPC=dpc | ,SSN=ssn | ,NADDR=naddr};

The MML command format for the CREATE-GTT GTI values 1–2 are as follows for the ANSI network variant:

CREATE-GTT:GTI=1,TT=tt,NP=np,LADDR=laddr,HADDR=haddr,DPC=dpc,SSN=ssn,NADDR=naddr;

CREATE-GTT:GTI=2,TT=tt,LADDR=laddr,HADDR=haddr,DPC=dpc,SSN= ssn,NADDR=naddr;


Man Page FormatThe alternative and man page format for CREATE-GTT is crte-gtt.

Enabling Partial Global Title Translations (all Variants)Normally, the SINAP node uses all the address digits to perform global title translation procedures. However, if you define the PARTIAL_GTT environment variable on the SINAP node, the node uses only the first few digits (as specified in the environment variable) to perform global title translations.

If you set the PARTIAL_GTT environment variable to enable partial global title translations on the node, you also must define the following environment variables:

MAX_PGTT_DIGITS=<value> Specifies the maximum number of digits (between 1 and 28 digits) to use in global title translations. The default is 6 digits.

MIN_PGTT_DIGITS=<value> Specifies the minimum number of digits to use in global title translations. The default is 3 digits.



If the partial global title translation feature is enabled on the SINAP node, the node tries to translate the incoming address against the addresses stored in the Global Title Translation (GTT) table. First, the node compares the incoming address and the first entry specified in the maximum number of digits (MAX_PGTT_DIGITS) environment variable. Then the SINAP node reduces the number of digits to the minimum number of digits as specified in the MIN_PGTT_DIGITS environment variable. The node uses the following rules to perform partial global title translations:

1. If the number of digits in the address to be translated is more than or equal to the value specified by the MAX_PGTT_DIGITS environment variable, the comparison is made starting from MAX_PGTT_DIGITS to MIN_PGTT_DIGITS as previously described.

2. If the number of digits in the address to be translated lies between the values specified by the MAX_PGTT_DIGITS and MIN_PGTT_DIGITS environment variables, the comparison is made starting from the number of digits in the address (not MAX_PGTT_DIGITS) to the MIN_PGTT_DIGITS.

3. If the number of digits in the address to be translated is less than the value specified by the MIN_PGTT_DIGITS environment variable, then absolute translation (not partial translation) occurs. That is, the node compares the address against the global title stored in the GTT table for the exact match.

The SINAP node validates the settings for the MAX_PGTT_DIGITS and MIN_PGTT_DIGITS environment variables using the following rules:

1. The value of MAX_PGTT_DIGITS must be between 1 and the value defined by the MAX_GLOBAL_TITLE environment variable which specifies the maximum number of digits that can be in the global title (28 digits). If no value is defined for MAX_PGTT_DIGITS or the specified value is out of the valid range, the SINAP node uses the default value (6 digits).

2. The value of MIN_PGTT_DIGITS must not be less than 1 or more than the value specified by the MAX_PGTT_DIGITS environment variable. If the value is greater than MIN_PGTT_DIGITS and MAX_PGTT_DIGITS is less than 3 (the default value of MIN_PGTT_DIGITS), the SINAP node sets MIN_PGTT_DIGITS to 1. Otherwise, the node sets MIN_PGTT_DIGITS to the default value (3).

You can use the following sy command utility to print the minimum and maximum values of partial global titles stored in the shared memory.

#STA,pgtt

The sy utility displays information similar to the following:

PARTIAL GTT Maximum digits=<value> PARTIAL GTT Minimum digits=<value>

When partial global title translation is not activated, the normal GTT process replaces the original global title with the translated addressing information (which is usually a new global


Configuring Network Components

title or some combination of SSN and DPC) in the outgoing message. This functionality is controlled by the NADDR argument.

When the PARTIAL_GTT environment variable is set and NADDR information is present in the translated address, the original global title is not replaced but included in the outgoing message with the Routing Indicator set to ROUTE_ON_GT.

N O T EThe presence of NADDR information is only used as a flag to indicate the manner in which the global title is to be routed. Its actual value is ignored.

When the PARTIAL_GTT environment variable is set and NADDR information is not present in the translated address, then normal DPC / SSN routing is assumed as previously described. The outgoing message is sent with the values resulting from the partial global title translation and the Routing Indicator set to ROUTE_ON_PC_SSN.

N O T EIn this instance, only LADDR is used in the translation process; HADDR is ignored.

Configuring Network Components Once you have created links, link sets, and route sets, activate them through the Configure Commands menu.

N O T EAfter provisioning the SINAP/SS7 system, you should use BACKUP-NODE to save your configuration. See ‘‘Backing Up Databases’’ in Chapter 4 for more information.



From the Network Commands menu shown in Figure 3-11, access the Configure Commands menu by entering the number for Configure.

Figure 3-11. Network Commands Menu

The Configure Commands menu appears, as in Figure 3-12. This menu contains options for configuring (activating and deactivating) links, link sets, and route sets.

Figure 3-12. Configure Commands Menu

Enter the number that corresponds to the action you want to perform. The options are described in detail in the sections which follow.

Configuring a LinkOnce you have created a link using the CREATE-LINK command, you can configure (activate) links individually or as a link set. Activate an individual link using the Configure Link option from the Configure Commands menu, or activate the links comprising a link set using the Configure Linkset option, described in the next section.

Perform the following steps to configure a link:

1. From the Configure Commands menu, enter the number for Configure Link. The CONFIGURE-LINK screen appears. The Terminal Handler prompts you to specify the CONFIGURE-LINK command arguments. The link shown in the following sample


Network Commands 1. Create 2. Configure 3. Change 4. Display 5. Delete 6. Dump Table 7. Measurements

Configure Commands 1. Configure Link 2. Configure Linkset 3. Configure Routeset

< CONFIGURE



contains entries created for the sample network configuration shown in Figure 3-4. User entries are in bold type.

2. Enter the appropriate values for your network configuration and press RETURN after each entry. Table 3-15 describes the CONFIGURE-LINK command arguments.

N O T EYou can use the CONFIGURE-LINK command to deactivate a link by setting the link STATE to INACTIVE.

Table 3-15. CONFIGURE-LINK Command Arguments


LINK The name of the link to activate.

STATE The link state. You can choose active, inactive, inhibit, or uninhibit for the ANSI, CCITT, and China network variants. For the TTC and NTT network variant, you can choose active or inactive only.

MML as built is CONFIGURE-LINK:Specify link name: LINK=lnk1LINK=lnk1Specify link state, possible choices are: 1 - ACTIVE 2 - INACTIVE 3 - INHIBIT 4 - UNINHIBITChoice=1LINK=lnk1,STATE=ACTIVE



3. The Terminal Handler processes your entries and prompts you to issue the CONFIGURE-LINK command with the values you defined. Press RETURN to send the command to the system, as shown in the following sample screen.

4. The SINAP/SS7 system configures the link with the specified values. The Terminal Handler displays the command again and confirms successful execution. Enter Q or q to quit displaying the response.

5. Press CTRL-P to return to the Configure Commands menu or CTRL-B to return to the SINAP System Main Menu.

MML Command FormatThe MML command format for the CONFIGURE-LINK command is:

CONFIGURE-LINK:LINK=link,STATE=state;

Refer to Table 3-15 for descriptions of the MML command arguments.

Man Page FormatThe alternative and man page format for CONFIGURE-LINK is cfr-link.

Configuring a Link SetAfter creating a link, you activate the link by either configuring the individual links or by configuring a link set.

Perform the following steps to configure a link set:

1. From the Configure Commands menu, enter the number for Configure Linkset. The CONFIGURE-LSET screen appears. The Terminal Handler prompts you to specify the CONFIGURE-LSET command arguments. The link set in the following sample screen contains entries for the sample network configuration in Figure 3-4. User entries are in bold


MML Send Menu

<CONFIGURE-LINK:LINK=lnk1,STATE=ACTIVE;




type.

2. Enter the appropriate values for your network configuration using the CONFIGURE-LSET command arguments described in Table 3-16. Press RETURN after each entry.

3. The Terminal Handler processes your entries and prompts you to issue the CONFIGURE-LSET command with the values you defined. Press RETURN to send the command to the system, as shown in the following sample screen.

4. The SINAP/SS7 system activates the link set, displays the command again, and confirms successful execution. Enter Q or q to quit displaying the response.

When you execute the CONFIGURE command, the SINAP/SS7 system activates the maximum number of member links.

Table 3-16. CONFIGURE-LSET Command Arguments


LINKSET The name of the link set you want to provision.

STATE The state of the linkset. You can choose active or inactive. (the SINAP/SS7 system does not pass traffic over inactive link sets; newly created link sets are designated inactive until provisioned.)

MML as built is CONFIGURE-LSET:Specify linkset name: LINKSET=lset1LINKSET=lset1Specify linkset state, possible choices are: 1 - ACTIVE 2 - INACTIVEChoice=1LINKSET=lset1,STATE=ACTIVE


MML Send Menu

<CONFIGURE-LSET:LINKSET=lset1,STATE=ACTIVE;




For example, if the CREATE-LSET command specifies eight links to activate, but only six links are provisioned for the link set, the SINAP/SS7 system activates all six. If you provision 12 links, the SINAP/SS7 system activates 8 links and leaves the other 4 inactive.

N O T EYou can also use the CONFIGURE-LSET command to deactivate a link set, which deactivates the individual links within that link set.


MML Command FormatThe MML command format for the CONFIGURE-LSET command is:

CONFIGURE-LSET:LINKSET=linkset,STATE=state;


Man Page FormatThe alternative and man page format for CONFIGURE-LSET is cfr-lset.

Configuring a Route SetYou can activate a route set using the CONFIGURE-RSET command.

N O T EIn the CCITT network variant, whenever a new route set is created and configured for a remote signaling point in the network (and not for an adjacent point code), the route set should be initialized to the PROHIBITED state. To ensure proper initialization, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.


Perform the following steps to configure a route set:

1. From the Configure Commands menu, enter the number for Configure Routeset. The CONFIGURE-RSET screen appears. The Terminal Handler prompts you to specify the CONFIGURE-RSET command arguments. The route set shown in the following sample screen contains entries for the sample network configuration in Figure 3-4. User entries are



in bold type.

2. Enter the appropriate values for your network configuration using CONFIGURE-RSET command arguments described in Table 3-17. Press RETURN after each entry.

3. The Terminal Handler processes your entries and prompts you to issue the CONFIGURE-RSET command with the values you defined. Press RETURN to send the command to the system, as shown on the following sample screen.

4. The SINAP/SS7 system activates the route set, displays the command again, and confirms successful execution. Enter Q or q to quit displaying the response.


Table 3-17. CONFIGURE-RSET Command Arguments


ROUTESET The name of the route set to be provisioned.

STATE The state of the route set. You can choose ACTIVE or BLOCK. (The SINAP/SS7 system does not pass traffic over inactive route sets; newly created route sets are designated inactive until provisioned.)

MML as built is CONFIGURE-RSET:Specify routeset name: ROUTESET=rset1ROUTESET=rset1Specify routeset state, possible choices are: 1 - ACTIVE 2 - BLOCKChoice=1ROUTESET=rset1,STATE=ACTIVE


MML Send Menu

<CONFIGURE-RSET:ROUTESET=rset1,STATE=ACTIVE;




MML Command FormatThe MML command format for the CONFIGURE-RSET command is:

CONFIGURE-RSET:ROUTESET=routeset,STATE=state;


Man Page FormatThe alternative and man page format for CONFIGURE-RSET is cfr-rset.

Initializing Route Sets with a Prohibited Status (CCITT only)Normally, in the CCITT network variant, when you create and activate a route set through the CONFIGURE-RSET command (and links are already aligned), the SINAP node sets the destination state to DPC accessible. Also, the node does not send an RST message until it receives a Transfer Prohibited (TFP) message or a Transfer Restricted (TFR - National Option) message from the remote node.

However, an optional feature in the SINAP/SS7 system allows you to create and configure route sets for nonadjacent signaling points that are initialized with a prohibited status (DPC not accessible) instead of the normal allowed status (DPC accessible). You activate this feature by setting an environment variable.

If you create and configure a new route set to a nonadjacent signaling point when the SINAP node is not performing MTP restart, the SINAP node sets the route set state to the prohibited state (DPC not accessible). The SINAP node also sends out Signaling Route Set Test (RST) messages to the adjacent STPs for the prohibited destination(s) associated with the newly configured route sets.

If you create and configure new route sets while the SINAP node is performing MTP restart, the newly configured route sets are set to the allowed (DPC accessible) state. In this case, it is the responsibility of the adjacent STPs to send the appropriate TFP, TFR, and/or Transfer Allowed (TFA) messages to the SINAP node during the MTP restart procedure.

N O T E S1. This feature applies only if the newly created and

configured route set is for a remote, nonadjacent signaling point in the network. This feature does not apply to an adjacent point code (a signaling point that is connected directly through a link set to the SINAP node).

2. For an adjacent signaling point (including adjacent STPs), the route set status should be allowed. There is no need to set a prohibited route set status for an adjacent signaling point.



Enabling the Prohibited Route Set Status FeatureTo activate this feature, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.


If this environment variable is not defined, the SINAP node initializes newly configured route sets for nonadjacent signaling points to the allowed (DPC accessible) state.

Initializing Remote SSNs in the Prohibited State (CCITT only)The SINAP/SS7 system provides the capability to initialize remote subsystems in a prohibited state and enable a SINAP node to pass User-Out-of-Service (UOS) messages to the local application. In addition, the SINAP node executes Subsystem Status Test (SST) procedures until it receives a Subsystem Allowed (SSA) message from the remote point code. Upon receipt of an SSA message, the SINAP node sends a User-In-Service (UIS) message to the local application. This feature is supported in the CCITT network variant only.

To enable this feature, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

REMSSN_INIT_PROHIBIT=1

This environment variable has no value assigned to it. The SINAP node only verifies the existence of the variable. When this environment variable is defined, the SINAP node sets the remote SSN status to prohibited when:

• The remote SSN is created using the CREATE-REMSSN MML command

• SCCP management (SCMG) receives an MTP_RESUME primitive from MTP L3RC after a SINAP MTP restart occurs.

When a remote SSN status is set to prohibited, SCCP management (SCMG) performs Subsystem Status Test (SST) procedures for the prohibited SSN and sends User-Out-of-Service (UOS) messages to local applications associated with the remote SSN. When the SINAP node receives SSA messages for other remote SSNs, the node sets the status of those remote SSNs to allowed and sends User-In-Service (UIS) messages to the local applications associated with the concerned remote SSNs. Note that the SINAP node sends SSTs to all prohibited remote SSNs until the node receives SSA messages from those SSNs. This results in the generation of additional network traffic.

If you do not define the REMSSN_INIT_PROHIBIT environment variable, all subsystems are marked as allowed when the SINAP node initially starts up. Also, the node does not send a UIS message to the local application when a subsystem comes up on a remote system for the first time after a local restart. These procedures comply with ITU-T Recommendation Q.714 which requires that subsystems be initialized to the allowed state.


Configuring Load Control Parameters for a TCAP Application

Configuring Load Control Parameters for a TCAP ApplicationThe SINAP/SS7 system can be configured to implement load control for a TCAP application during periods of extreme network congestion to maximize the throughput of completed TCAP transactions by minimizing the number of transaction time outs on the network. Load control is a response to extreme conditions and the intent is to minimize message loss due to time outs. Load control changes the priority of incoming messages and deliberately discards some messages that initiate a TCAP transaction.

During normal SS7 network operation, an application processes messages in the order in which they arrive. However, when the network is extremely congested, the application might not be able to handle all its incoming messages. Therefore, it is important for the application to complete existing transactions before initiating new ones. To accomplish this, the SINAP/SS7 load control function assigns processing precedence to messages that are part of an existing transaction (called continuation messages).

Load control can be invoked by operator command or programmatically (forced load control) but normally goes into effect due to monitored conditions being met (automatic load control). Load control is optional. It is set up on an application basis and each application can have its own load control parameters. Once set up, load control can be enabled or disabled on a system-wide, application, or instance basis. Load control can take place on a group basis for an application as a whole, or on an individual basis for each separate instance. The setup and enablement parameters for a subsystem are persistent. They are retained in the static database and only need to be reissued when a change is called for.

You configure an application for load control by defining the application’s load control operating characteristics. These operating characteristics specify how the SINAP/SS7 system performs load control processing, and define such parameters as the maximum level of network congestion considered acceptable for the application.

After configuring the application, you enable load control, which causes the SINAP/SS7 system to begin monitoring the application’s congestion level. There are two options for specifying when load control should begin.

The first option involves evaluating the MSU delay count and the input queue length. Each incoming message is given a time stamp that indicates the time of its arrival. The SINAP/SS7 system uses this time stamp to evaluate the length of time between the message arrival and when the application places a response on the output queue. This length of time, as well as the input queue length, is optionally considered in calculating the congestion level. When the congestion level exceeds the threshold level defined by the application’s load control operating characteristics (hereafter called overload conditions), the SINAP/SS7 system begins load control processing.

The second option for determining load control onset involves disabling the use of MSU delay counts and considering only the input queue length versus the threshold. Incoming MSUs are not time stamped. See ‘‘Configuring Load Control Functionality” later in this chapter for more information.



How Load Control Processes MessagesEach application has an input queue in which the SINAP/SS7 system places incoming messages. This input queue functions as a first-in, first-out (FIFO) queue. To perform load control processing, the SINAP/SS7 system creates a second input queue for the application. This queue is a last-in, first-out (LIFO) queue.

The SINAP/SS7 system evaluates the messages currently in the application’s input queue and places on the application’s LIFO queue all incoming messages that initiate a new transaction. The SINAP/SS7 system continues to place continuation messages (those that are part of an existing transaction) on the application’s input queue.

The application processes the messages in its input queue first. When all these messages are processed, the application begins processing the messages on its LIFO queue (those that initiate new transactions). If the LIFO queue becomes full, the SINAP/SS7 system discards the oldest message on the queue to make room for a new incoming message. Messages are also discarded from the LIFO queue when they exceed the given timeout period that has been configured.

The SINAP/SS7 system continues to perform load control processing until the application processes all messages on its input and LIFO queues, or until you terminate load control. When both queues are empty, the SINAP/SS7 system terminates load control processing for the application. Because the application is still configured and enabled for load control, the SINAP/SS7 system continues to monitor the application for overload conditions. When the application again experiences overload conditions, the SINAP/SS7 system invokes load control processing for the application.

Load Control PersistenceLoad control is persistent and once it is set up for an SSN or application it stays set up even when the application is terminated or the SINAP/SS7 system is restarted. The only way to remove the load control setting for such an application is to delete it by using an MML command (see ‘‘Using the Load Control Facility’’ in Chapter 4) or a CASL function (see the sections describing load control in the SINAP/SS7 Programmer’s Guide (R8052)).

Alarms of major levels are always issued for all cases of load control and abatement. Alarms are issued separately for instances if individual load control is in effect.

Considerations for Implementing Load Control Any application that interfaces to the SINAP/SS7 system at the TCAP boundary can implement load control functionality. You can configure and enable an application for load control by issuing MML commands from the SINAP/SS7 Terminal Handler, or by including CASL function calls in the application (typically, in the application’s control process).

N O T E S1. Load control cannot be implemented by an application that

has one process performing both control and data



processing, and another process with one or more instances also performing data processing at the same time. To implement load control, an application must have a separate control process, or it must have a process with several instances, one of which performs control processing.

2. An application should implement load control only in response to extreme network congestion. Using load control does not guarantee incoming messages will not be lost.

Application developers can develop an application that calls certain CASL functions to implement load control for an application. You can also use a combination of MML commands and CASL functions to implement load control for an application. For example, an application can contain certain CASL functions to configure the application for load control but not to enable load control processing. In this case, you would issue the MML command, ENABLE-LOAD-CONTROL, to enable load control processing for the application.

You can also change the application’s load control characteristics by issuing the SETUP-LOAD-CONTROL command.

See the SINAP/SS7 Programmer’s Guide (R8052) for more information on programming the CASL functions used to implement load control for an application.

Issuing Load Control MML CommandsYou must enter all load control MML commands and argument values in UPPERCASE letters, otherwise, the SINAP/SS7 system cannot execute the command. If you issue a load control MML command with an incorrect argument value, the Terminal Handler returns an error message and does not execute the command.

Most load control MML commands have SSN and INSTANCE arguments that specify the application and instance, respectively, on which the command executes. Some commands also accept the value ALL for SSN and INSTANCE. Specifying ALL for SSN executes the command on all applications configured for load control. Specifying ALL for INSTANCE, or omitting INSTANCE from the command line, executes the command on all instances of the specified application. Table 3-18 lists and describes the load control MML commands.

N O T EApplications which use enhanced message distribution use the application name instead of an SSN in the SSN argument.



Issue the MML SETUP-LOAD-CONTROL command to configure an application for load control. Several of the command’s arguments define the various thresholds that determine the application’s maximum allowable congestion level. Other arguments specify how the SINAP/SS7 system performs load control processing for the application.

You cannot configure individual application instances for load control because, by default, the SETUP-LOAD-CONTROL command affects all instances of the application. However, when you enable load control, you can enable it for a subset of the application’s instances, thereby selectively implementing load control processing for specific application instances.

To configure and implement load control for an application, issue load control MML commands in the following order:

1. Issue the SETUP-LOAD-CONTROL command to configure the application for load control and to define load control operating characteristics. Issue a separate command for each application you are configuring for load control.

2. Issue the ENABLE-LOAD-CONTROL command to initiate load control operation. This command causes the SINAP/SS7 system to begin monitoring the application for overload conditions.

3. Optionally, you can issue the DISPLAY-LOAD-CONTROL command to display load control statistics.

4. Issue the DISABLE-LOAD-CONTROL command to completely terminate load control operation. The SINAP/SS7 system does not return to the load control monitoring stage.

Table 3-18. Load Control MML Commands

MML Commands Description

SETUP-LOAD-CONTROL Configures load control.

ENABLE-LOAD-CONTROL Initiates load control operation.

INVOKE-LOAD-CONTROL Activates load control processing regardless of network congestion status.

DISPLAY-LOAD-CONTROL Displays load control statistics.

DISABLE-LOAD-CONTROL Deactivates load control processing.

EXIT-LOAD-CONTROL Terminates load control operation; however, after the command executes, the load control is still enabled. To completely terminate load control, execute DISABLE-LOAD-CONTROL.



N O T EStratus recommends that you do not use the INVOKE-LOAD-CONTROL command to activate load control because it performs load control regardless of network congestion. Stratus also recommends that you do not use the EXIT-LOAD-CONTROL command to deactivate load control, because you can only use this command if you used INVOKE-LOAD-CONTROL to activate load control for an application.



Figure 3-13 shows the various stages of load control.

Figure 3-13. Stages of Load Control

SINAP disables load control processing when the queues

are emptied.

SINAP monitors applications for overload conditions.

Load control operation is terminated completely.

SINAP monitors applications for overload conditions.

When overload conditions are detected, SINAP begins load

control processing.

Issue the command: DISABLE-LOAD-CONTROL

Issue the command: ENABLE-LOAD-CONTROL

Issue the command: SETUP-LOAD-CONTROL

YesNo



Configuring Load Control FunctionalityPerform the following steps to set up the load control process:

1. From the SINAP System Main Menu, enter the number for Application Commands. The Application Commands menu appears.

2. From the Application Commands menu, enter the number for Load Control. The Load Control Commands menu appears, as shown in the following sample screen.

3. From the Load Control Commands menu, enter the number for Setup Load Control. The SETUP-LOAD-CONTROL screen appears. This command configures an application for load control and defines load control operating characteristics. You must issue a separate SETUP-LOAD-CONTROL command for each application you want to configure.

The Terminal Handler prompts you to specify the arguments for the SETUP-LOAD-CONTROL command. The following sample SETUP-LOAD-CONTROL screen displays entries for the sample network configuration shown previously in Figure 3-4. User entries are in bold type.

Load Control Commands

1.Setup Load Control2.Enable Load Control3.Disable Load Control4.Invoke Load Control5.Exit Load Control6.Display Load Control

MML as built is:SETUP_LOAD_CONTROLSpecify subsystem number (2-255) or application:SSN=SSN=254Specify type (G=GROUP, I=INDIV, D=DELETE):TYPE=SSN=254,TYPE=GROUPSpecify threshold (1-10000):THRESHOLD=SSN=254,TYPE=GROUP, THRESHOLD=150Specify delay (0-10000):DELAY=SSN=254,TYPE=GROUP, THRESHOLD=150, DELAY=2500Specify count (1-10000):COUNT=SSN=254,TYPE=GROUP,THRESHOLD=150,DELAY=2500,COUNT=50Specify abate delay (1-10000):ABATEDELAY=SSN=254,TYPE=GROUP,THRESHOLD=150,DELAY=2500,COUNT=50,ABATEDELAY=1500



4. When prompted, enter the appropriate values for your network configuration using SETUP-LOAD-CONTROL command arguments described in Table 3-19.

Table 3-19. SETUP-LOAD-CONTROL Command Format (Page 1 of 3)


SSN Specifies the SSN (in the range 2 to 255) of the application you are configuring for load control. The application need not be running when you issue the SETUP-LOAD-CONTROL command.

If the application is registered for enhanced message distribution, enter the 2- to 4-character application name instead of the SSN. A CASL function encodes the application name as a zero-filled, right-justified, U32 integer with a value greater than 255. See the SINAP/SS7 Programmer’s Guide (R8052) for more information.

TYPE Specifies how the SINAP/SS7 system evaluates the network congestion levels of individual application instances to determine if the application is experiencing overload conditions. Specify one value:

• GROUP (load control group-type operation) specifies that the SINAP/SS7 system treat all of the application’s instances as a single entity. The SINAP/SS7 system activates load control processing only when all the application’s instances are experiencing overload conditions. For example, if an application has 10 instances, and only 3 of the 10 are experiencing overload conditions, the SINAP/SS7 system does not activate load control processing for any of the instances; all 10 instances must be experiencing overload conditions. Note: Stratus recommends specifying GROUP, which causes the SINAP/SS7 system to evaluate the application’s network congestion based on the combined congestion levels of each of the application’s instances. If you plan to allow individual application instances to enable, disable, invoke, and exit load control, you must specify INDIV. To use GROUP, the type of inbound load distribution can be configured to specify either round-robin load distribution or least-utilized load distribution. See the description of ca_register() in the SINAP/SS7 Programmer’s Guide (R8052) for more information.



TYPE(cont.)

• INDIV (load control individual-type operation) specifies that the SINAP/SS7 system is to treat each of the application’s instances as a separate entity. The SINAP/SS7 system activates load control processing for an application instance whenever that instance experiences overload conditions. To use INDIV, the application’s inbound load distribution type must be set to specify round-robin load distribution. (See the description of ca_register() in the SINAP/SS7 Programmer’s Guide (R8052) for more information about this structure.)

• DELETE removes load control functionality from the application. You cannot remove load control functionality from individual application instances.

THRESHOLD Specifies the maximum number of messages allowed on the application’s input queue. The SINAP/SS7 system activates load control processing when the number of messages on the input queue meet or exceed this value, and the values of the DELAY and COUNT arguments are met or exceeded. Specify a value between 1 and the value you specified for the max_msu_input_que field of the register_req_t structure (not to exceed 10000). (See the description of ca_register() in the SINAP/SS7 Programmer’s Guide (R8052) for more information about this structure.)

DELAY Specifies the amount of time, in milliseconds, within which the application must process an incoming message (in the range 1 through 10000). There are two ways to determine the onset of load control:

1.The SINAP/SS7 system activates load control processing when the number of incoming messages specified by the COUNT argument has not been processed within this amount of time, and the number of messages on the application’s input queue meets or exceeds the value of the THRESHOLD argument. Note that message processing time is measured from the time an incoming message arrives on the input queue to the time the application places a response on the output queue.





DELAY(cont.)

2.You can disable use of MSU delay counts and use only the input queue length versus the threshold to determine load control onset. When you use this method, incoming MSUs are not time-stamped. To disable MSU delay counts, set both DELAY and COUNT to zero. Setting only one of them to zero results in an error in specifying the nonzero field. ABATEDELAY must be sent to a positive value. Using the sysopr menu for SETUP-LOAD-CONTROL and specifying zero for DELAY automatically forces the COUNT to zero.

Note: To make use of the time stamp applied to incoming messages (which the SINAP/SS7 system uses to monitor an application for overload conditions), an application must use the same t_block_t structure for the response as was used by the incoming message; otherwise, the time stamp is rendered useless.

COUNT Specifies the maximum number of consecutive outbound messages (in the range 1 through 10000) that the application is allowed. This argument can be used to determine the onset of load control in two ways:

1.The SINAP/SS7 system activates load control processing when the number of messages on the application’s output queue meet or exceeds the value of this argument, and the number of messages on the application’s input queue meets or exceeds the value of the THRESHOLD argument.

2.To disable MSU delay counts and determine load control onset only by the input queue length versus the threshold, set COUNT to zero. DELAY must also be set to zero or else an error will occur specifying the nonzero field.

ABATEDELAY Specifies the maximum amount of time, in milliseconds, that an incoming message can spend on the LIFO queue during load control processing (in the range 1 through 10000). When the SINAP/SS7 system extracts a message from the LIFO queue, it compares the length of time the message has been on the queue to the value of this argument. If the message’s time on the queue meets or exceeds this value, the SINAP/SS7 system discards all the messages on the LIFO queue, because they have been on the queue too long.

When using only the input queue length and not MSU delay counts to determine load control onset, ABATEDELAY must be set to a positive value.





Press RETURN after each entry.

In the sample screen for the SETUP-LOAD-CONTROL command, an application whose SSN is 254 was configured for load control.

For the SINAP/SS7 system to invoke load control processing for the sample application, all the application’s instances must be experiencing overload conditions (TYPE = GROUP). Load control processing begins when there are 150 or more incoming messages on the input queue (THRESHOLD =150) and there are more than 50 outbound messages (COUNT=50) that were not processed within 2,500 milliseconds (DELAY = 2500). The maximum time an incoming message can spend on the LIFO queue during load control processing is 1500 milliseconds (ABATEDELAY=1500).

5. Once you enter the appropriate values for your network configuration, the Terminal Handler processes the entries and prompts you to issue the completed MML command with the values you defined.

The following sample MML command screen shows the entries from the previous sample configuration. Press RETURN to send the completed command to the system.

6. The SINAP/SS7 system activates load control, displays the command again, and confirms successful execution. Enter Q or q to quit displaying the response.

7. Press CTRL-P to return to the Load Control Commands menu or CTRL-B to return to the SINAP System Main Menu.

Once load control is set up for your system, you can also perform the following tasks:

• To initiate load control operation, you must issue the ENABLE-LOAD-CONTROL command after issuing SETUP-LOAD-CONTROL. The section on load control in Chapter 4 provides instructions for this task.

• To modify an application’s existing load control operating characteristics, issue the SETUP-LOAD-CONTROL command and specify new values for the appropriate command arguments.


MML Send Menu

SETUP-LOAD-CONTROL:SSN=254,TYPE=GROUP,THRESHOLD=150,DELAY=2500,COUNT=50,ABATEDELAY=1500;




• To remove load control functionality from an application, issue the SETUP-LOAD-CONTROL command and specify the value, DELETE, for the TYPE argument. For example, the following command removes load control functionality from the sample application whose SSN is 254:

SETUP-LOAD-CONTROL:SSN=254,TYPE=DELETE;

The values specified for command arguments are stored in a static database and remain in effect until you change them, or until you reinitialize the system. The command’s THRESHOLD, DELAY, and COUNT arguments define the application’s maximum allowable level of network congestion. The LIFO queue that the SINAP/SS7 system creates for load control processing is the same size as the application’s input queue. (See the description of ca_register() in the SINAP/SS7 Programmer’s Guide (R8052) for information on this structure.)

The application’s current state has the following effects on the load control operating characteristics defined by the SETUP-LOAD-CONTROL command:

• If you are configuring an application for load control and the application is currently active, the load control operating characteristics take effect when the SETUP-LOAD-CONTROL command finishes executing. The SINAP/SS7 system implements load control for the application without disrupting the application’s normal processing.

• If you are configuring an application for load control and the application is not currently active, load control operating characteristics take effect when the application registers with the SINAP/SS7 system. (See the description of ca_register() in the SINAP/SS7 Programmer’s Guide (R8052) for information about application registration.)

• If you are modifying the load control operating characteristics of an application that is already configured for load control, the new characteristics take effect when the SETUP-LOAD-CONTROL command finishes executing. If the SINAP/SS7 system is currently performing load control processing for the application, the SINAP/SS7 system validates the new characteristics without disrupting active load control processing.

• If you remove load control from an application for which the SINAP/SS7 system is currently performing load control processing, the SINAP/SS7 system extracts messages from the application’s LIFO queue in FIFO fashion and appends them to the application’s input queue. The SINAP/SS7 system discards messages that have been on the application’s LIFO queue longer than the time defined by the SETUP-LOAD-CONTROL command’s ABATEDELAY argument. The SINAP/SS7 system also discards any messages that would cause the application’s input queue to overflow.

MML Command FormatThe MML command format for the SETUP-LOAD-CONTROL command is:

SETUP-LOAD-CONTROL:SSN=SSN,TYPE=TYPE,THRESHOLD=THRESHOLD, DELAY=DELAY, COUNT=COUNT,ABATEDELAY=ABATE-DELAY;

The SETUP-LOAD-CONTROL command arguments are described in Table 3-19.


Configuring Multiple Link Congestion Levels

N O T ESpecifying argument values that are too low can cause unpredictable load control behavior.

Man Page FormatThe abbreviated and man page form of SETUP-LOAD-CONTROL is setup-lc.

Configuring Multiple Link Congestion LevelsThe SINAP/SS7 network variants provide congestion handling in different ways, depending on the network variant. This section describes how to configure the CCITT, China, ANSI, NTT, and TTC network variants to handle network congestion.

Variant DifferencesIn the CCITT and China network variants, you must configure the system to implement multiple link congestion levels by defining several environment variables in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before you start the SINAP/SS7 system. They are described in “Implementing CCITT and China Multiple Link Congestion Functionality” later in this chapter.

For the CCITT and China network variants, you can implement up to 4 multiple link congestion levels (0–3). Options allowed include:

• International one congestion onset and one congestion abatement

• National multiple congestion states with congestion priority option

• National multiple congestion states without congestion priority

N O T EThe default value is international one congestion onset and one congestion abatement if no environment variable is set to define link congestion levels.

The ANSI, TTC, and NTT variants support multiple congestion levels (0–3) with message priority. The message priority is set within the client applications. The system automatically implements multiple congestion levels—you do not need to define any environment variables to implement multiple congestion levels.

Congestion StatesMultiple link congestion states enable the SINAP/SS7 system to maintain up to four levels of signaling link congestion (0, 1, 2, and 3), and to set a link’s congestion status according to these



levels. The system uses the same congestion onset, abatement, and discard levels in all variants of the SINAP/SS7 system.

The SINAP/SS7 system implements multiple link congestion levels on a system-wide basis so that when you specify the thresholds for each link-congestion level, the SINAP/SS7 system monitors each of its configured links for these thresholds. A link’s congestion status indicates the level of congestion that the link is experiencing based on the number of messages on the link’s SS7 driver queue. When the number of messages on the queue exceeds the number of messages allowed for a particular congestion level, the SINAP/SS7 system increases the value of the link’s congestion status to indicate that the link is becoming congested. As the link becomes less congested, the SINAP/SS7 system decrements the value of the link’s congestion status.

N O T EIf the message priority level (set within the application) is not less than the congestion discard level set for a DPC, the message is sent. If the message priority level is less than the discard level, the system discards the message. The default message priority level is 0. (See the SINAP/SS7 Programmer’s Guide (R8052) for information on changing the message priority within an application.)

In all network variants of the SINAP/SS7 system you can display and change the settings of threshold values by issuing the MML commands, DISPLAY-SYSTAB and CHANGE-SYSTAB, respectively. You can also display the settings of congestion onset, abatement, and discard tables by using the SINAP/SS7 system utility, sy, from any SINAP/SS7 login window. These processes are described in Chapter 4, ‘‘System Operation and Maintenance.”

Implementing CCITT and China Multiple Link Congestion FunctionalityIf you want to implement multiple link congestion functionality on your CCITT or China SINAP/SS7 system, you must set the environment variable for this function before running the SINAP/SS7 software. You can do this by uncommenting the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file and setting it to one of the options listed in Table 3-20 before starting the SINAP node.

CCITT_CONGESTION_OPTION=<VALUE>



The system will then implement congestion handling when it is needed according to the values you defined. See Appendix B, ‘‘SINAP/SS7 Environment Variables,” for more information on setting environment variables.

Table 3-20. Environment Variables for CCITT and China Link Congestion

Value Type of Link-Congestion Handling to Use

INTERNATIONAL_1_CONGESTION The international signaling network option that provides a single congestion onset threshold and a single congestion abatement threshold.

If you do not define the CCITT_CONGESTION_OPTION environment variable, the CCITT and China network variants implement this option as the default method of handling link congestion, which supports a single congestion onset (CONON1) threshold and a single congestion abatement (CONAB1) threshold.

NAT_MUL_CONG_WITH_PRIO The national signaling network option that allows multiple signaling link congestion levels with message priority. Available to both the CCITT and China network variants, this option allows client applications to set message priority based on multiple congestion levels (0–3). This option uses these thresholds:

• Congestion Onset (CONON1, CONON2, CONON3)

• Congestion Abatement (CONAB1, CONAB2, CONAB3)

• Congestion Discard (CONDIS1, CONDIS2, CONDIS3)



NAT_MULT_CONG_WO_PRIO The national signaling network option that allows multiple signaling link congestion levels without message priority.

Available only in the CCITT network variant, this option allows the SINAP/SS7 system to maintain up to four levels of link congestion (0–3) and to set a link’s congestion status according to these levels. If you specify this option, you must also specify values for the following additional environment variables:

• CONGESTION_STATUS—Specifies the level of link congestion (0, 1, 2, or 3) that your SS7 network supports. (Level 0 is the lowest; level 3 is the highest.) The value 2 specifies that SINAP supports three levels of link congestion (0, 1, and 2). The value 3 specifies that SINAP supports all four levels of link congestion (0, 1, 2, and 3). The default value is set to 3.

• CONGESTION_INITIAL_VALUE—Defines the initial link congestion level that the SINAP/SS7 system uses to determine the occurrence of congestion on a link. When the number of MSUs on the link’s SS7 driver queue exceeds the congestion onset threshold for the link congestion level defined by this environment variable, SINAP considers the link to be congested with this level. Valid values are 1, 2, or 3. The default value is set to 1. This value should not be greater than the value of the variable CONGESTION_STATES.

• CONGESTION_TX_TIMER—Defines the interval in seconds between congestion onset measurements. The valid range for this value is 1 through 255 seconds (the default is 1). When this timer expires, the SINAP/SS7 system counts the number of messages on the link’s SS7 driver queue and if the number of messages exceeds the value of the congestion onset threshold, the SINAP/SS7 system increments the link’s congestion status by 1.





Measuring Congestion When a link is not congested, the link’s congestion status is 0. The SINAP/SS7 system considers a link congested when the number of messages on the link’s SS7 driver queue exceeds the congestion-onset threshold for the congestion level defined by the environment variable, CONGESTION_INITIAL_VALUE. For example, if CONGESTION_INITIAL_VALUE is set to the value 2 (congestion level 2), the SINAP/SS7 system compares the number of messages on the link’s queue to the value of the CONON2 table. As long as the number of messages on the queue is less than the value of CONON2, the link is not considered congested. When the number of messages exceeds this threshold, the link is considered congested. For example, if the value of CONON2 is 110, the link becomes congested when the number of messages on its queue exceeds 110. When this happens, the SINAP/SS7 system sets the link’s congestion status to the value specified by the command, CONGESTION_INITIAL_VALUE, and starts the timers, CONGESTION_TX_TIMER and CONGESTION_TY_TIMER.

When the CONGESTION_TX_TIMER timer expires, the SINAP/SS7 system measures the number of messages on the link’s SS7 driver queue. If the number of messages on the queue exceeds the value of the next higher level’s congestion-onset threshold (specified in the appropriate CONON table), the SINAP/SS7 system increments the link’s congestion status by 1 and restarts the CONGESTION_TX_TIMER timer. For example, if a link’s congestion status is currently 1, and the number of messages on its queue exceeds the value of the CONON2 table, the SINAP/SS7 system increments the link’s congestion status from 1 to 2.

When the CONGESTION_TY_TIMER timer expires, the SINAP/SS7 system measures the number of messages on the link’s SS7 driver queue. If the number of messages on the queue is less the value of the next lower level’s congestion abatement threshold (specified in the appropriate CONAB table), the SINAP/SS7 system decrements the link’s congestion status by 1 and restarts the CONGESTION_TY_TIMER timer. For example, if a link’s congestion status is currently 3 and the number of messages on its queue is less than the value of the CONAB2 table, the SINAP/SS7 system decrements the link’s congestion status from 3 to 2.

NAT_MULT_CONG_WO_PRIO (cont.)

• CONGESTION_TY_TIMER—Defines the interval in seconds between congestion abatement measurements. The valid range for this value is 1 through 255 seconds (the default is 1). When this timer expires, SINAP counts the number of MSUs on the link’s SS7 driver queue. If the number of MSUs on the queue is less than the value of the congestion abatement threshold, SINAP decrements the link’s congestion status by 1.





The SINAP/SS7 system continues to count messages and restart the congestion timers until the number of messages on the link’s SS7 driver queue is less than the congestion abatement threshold defined by CONAB1. When the number of messages on the link’s queue drops below this value, the SINAP/SS7 system no longer considers the link congested.

N O T EThe information in the “Measuring Congestion” section is for the National Multiple Congestion States without Congestion Priority option (NAT_MUL_CONG_WO_PRIO) described in Table 3-20.

Displaying Link Congestion InformationYou can use the SINAP/SS7 utility (sy) to display the settings of congestion onset, abatement, and discard tables using the following steps:

1. To invoke the sy utility, type the following command at the UNIX prompt ($) in any SINAP/SS7 login window:

$ sy

The system displays the following prompt:

VERSION=Rel 14.0.0.0_05AL 02/04/04, SINAP_VARIANT=CCITTcurrent time is Tue Feb 24 17:36:06 2004type ‘?’ for command listEnter cmd>

2. To display the current settings of the link congestion environment variable, issue the following sy command:

Enter cmd> #SYS

N O T EThe pound sign (#) is part of the command.



If the multiple link congestion states feature is implemented, the second bit of the systems_options line will be set, as shown in boldface in the following sample display. If the feature is not implemented, the values of the variables are insignificant.

Enter cmd> #SYS SYSTEM table: node=N2, module=M1, home=/home/sinap2,master=/opt/sinap_master print_flag=0, printer=, l3seq=0x02fc system_options=0x00000002 extended_system_options=0x00000000 congestion_option=3 congestion status=3 congestion_initial_value=1 congestion_tx_timer=1 congestion_ty_timer=1

3. To display the settings of the congestion onset, abatement, and discard tables, issue the following command:

#STA,ST,MTP

The following example shows sample threshold settings:

Enter cmd> #STA,ST,MTP static SYSTEM table:MTP THRESHOLDS:CONON1 value=80CONAB1 value=50CONON2 value=110CONAB2 value=90CONON3 value=140CONAB3 value=120CONDIS1 value=130CONDIS2 value=170CONDIS3 value=210

Notifying the Application of Congestion The SINAP/SS7 system notifies an application that a link is congested by sending a message to the application’s interprocess communications (IPC) queue. The application can then either stop sending messages or reduce the number of messages it sends, until the congestion level returns to normal. The SINAP/SS7 system sends a message after the application has sent eight outgoing messages over a congested link; in addition, the SINAP/SS7 system writes a message to its alarm log.

The message can be either of the following:



• If an application is registered to receive input at the SCCP or TCAP boundary, the SINAP/SS7 system sends the application an I_N_PCSTATE_INDIC message.

• If an application is registered to receive input at the MTP boundary, the SINAP/SS7 system sends the application an I_MTP_STATUS message.

Congestion Notification OptionsThe environment variable CONG_EVENT_REPORT_OFF controls the congestion report for every 1 out of 8 outbound messages per Q.704 section 11.2.3.1 via IPC messages, M_message_for_congested_[link,route,destination], from CASL to L3RC to notify MTP3 users via I_MTP_STATUS primitives.

Under heavy traffic with congested link/linkset/routeset, these IPC messages may prevent the other significant IPC messages from processing. Setting this variable CONG_EVENT_REPORT_OFF to 1 or a non-zero value will disable this report.

The environment variable CONG_STATUS_CHANGE_LOGGING is used to enable or disable SINAP alarm logging for link/linkset/routeset(DPC) congestion status change. Setting this variable to 1 or a non-zero value will enable the logging of the congestion status change in the SINAP alarm log file. Otherwise this feature will not be enabled.

Link Congestion ThresholdsThe thresholds for each link congestion level are defined by separate sets of system tables. Congestion onset (CONON) tables define the upper threshold for a particular link congestion level. Congestion abatement (CONAB) tables define the lower threshold. Congestion discard (CONDIS) tables define the threshold before messages are discarded.

• CONON1, CONAB1, and CONDIS1 define the congestion-level-1 thresholds.



N O T E The value of each congestion onset table (CONON1, CONON2, and CONON3) should be greater than its corresponding congestion abatement table (CONAB1, CONAB2, and CONAB3).

Table 3-21 lists each congestion table and its default value.


The MTP Restart Process

N O T EIn the CCITT network variant, if you do not implement the national signaling network option (multiple link-congestion states with or without congestion priority), the SINAP/SS7 system defaults to the international signaling network option, which has only one congestion onset and one abatement level. The SINAP/SS7 system then uses the threshold levels for CONON1 and CONAB1 to determine a link’s congestion status.

The MTP Restart ProcessThe Message Transfer Part (MTP) restart process enables the MTP at a signaling point that has just become available to bring sufficient signaling links into the available state to handle expected traffic and to stabilize its routing before user traffic is restarted to the signaling point. The MTP restart process helps prevent routing problems that can occur after the system resumes sending user traffic following a failure due to invalid routing information or too many parallel activities, such as link activation or changeback. MTP restart ensures that the system has sufficient signaling links available to handle the expected traffic volume and the route to the signaling point is stable. A signaling point is unavailable if all connected links are unavailable. It becomes available when at least one link connected to the signaling point becomes available.

MTP restart is supported by the CCITT, ANSI, and China network variants and adheres to the 1993 ITU-T recommendations for MTP and the 1992 ANSI standards for MTP. The TTC network variant does not support MTP restart functionality.

Table 3-21. Congestion Thresholds

Threshold Default Value

CONON1 80

CONON2 110

CONON3 140

CONAB1 50

CONAB2 90

CONAB3 120

CONDIS1 130

CONDIS2 170

CONDIS3 210



Because MTP restart requires links to other nodes in the SS7 network, MTP restart functionality does not apply to the operation of a single node. If, for any reason (such as testing or performing local loopback procedures), you operate a single SINAP node, you should not enable the MTP restart feature.

You activate the MTP restart process by enabling specific environment variables for the network variant you are configuring. This section describes the MTP restart process and discusses the following topics:

• An overview of MTP processing

• Enabling MTP restart functionality

See Chapter 4, ‘‘System Operation and Maintenance,” for information about displaying MTP restart information and changing system table timer and link congestion threshold settings.

MTP Restart Processing OverviewIf the MTP restart environment variable is set, the SINAP/SS7 system performs MTP restart (also called signaling point restart control) whenever you activate the SINAP/SS7 system on a node. The MTP restart procedure can be applied when a SINAP node is the restarting signaling point or when a node adjacent to the SINAP node is the restarting signaling point. The process provides time for the node’s links and routes to come into service before the node begins sending user traffic over them. Throughout MTP restart, the node activates and unblocks its links using normal signaling link management (SLM) procedures. This ensures a smooth flow of traffic through the network.

During MTP restart, the node does not pass user traffic between its applications and the applications running on other nodes. Instead, the node exchanges network-status information with its adjacent nodes using the following types of messages:

• Signaling link test management (SLTM)

• Signaling link test acknowledgment (SLTA)

• Traffic restart allowed (TRA)

• Transfer prohibited (TFP)

• Transfer restricted (TFR)

• Transfer allowed (TFA)

• Transfer restart waiting (TRW) (ANSI only)

These messages indicate the availability of the links and routes between the nodes. Once MTP restart ends, the MTP informs each of its user parts (that is, applications) that they can begin passing user traffic.



Several timers define time limits for MTP restart activities. The timers and values differ between the network variants and are described in the following sections. To change these timer values, see Chapter 4.

Enabling MTP Restart FunctionalityThe SINAP/SS7 system performs the following major steps to execute MTP restart:

• Initiates MTP restart processing

• Processes messages during MTP restart

• Completes MTP restart

The CCITT, China, and ANSI network variants support MTP restart functionality, but are activated by different environment variables and differ slightly in their timer values and functionality. The major differences between the variants are as follows:

• The ANSI network variant has a larger set of timers and protocols concerning messages received, timer expiration, and timer stoppage.

• The ANSI network variant contains the traffic restart waiting (TRW) message.

The following sections describe how to run MTP restart on each network variant.

MTP Restart Processing for CCITT and China VariantsTo implement the MTP restart feature on your system, uncommenting the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

MTP_WHITE_BOOK_RESTART=1

If the environment variable is not defined, MTP restart is not performed when the SINAP/SS7 system is started or restarted on the node.

At the beginning of the MTP restart process, the SINAP/SS7 system activates the L3T20 timer and marks all concerned routes ALLOWED. The L3T20 timer defines the maximum amount of time allowed to complete all MTP restart activities. The L3T21 timer defines the amount of time to stop sending traffic to another node because that node is performing MTP restart. (See ‘‘Changing Timers and Link Congestion Threshold Settings’’ in Chapter 4 for information about these timers.)

While the MTP restart process is active, the SINAP/SS7 node and its adjacent nodes monitor all of the TFA, TFP, and TFR messages they exchange. The SINAP/SS7 system and its adjacent nodes use the information in these messages to mark those routes available or unavailable and to update the MTP routing tables. The MTP restart procedure works effectively only if the status of the links and routes remains fairly stable.



During MTP restart, the SINAP/SS7 system handles incoming and outgoing messages as follows:

• The SINAP/SS7 system performs normal processing of SLTM and SLTA messages, which have a service indicator (SI) of 0001. (The SI consists of bits 0 through 3 of the service information octet (SIO) field.)

• The SINAP/SS7 system only processes signaling network management (SNM) message types: TRA, TFP, TFR, and TFA. The SINAP/SS7 system discards all other SNM message types, such as:

— Changeover and changeback message (CHM)

— Signaling-data-link-connection-order message (DLM)

— Emergency-changeover message (ECM)

— Signaling-traffic-flow-control message (FCM)

— Management inhibit message (MIM)

— Signaling-route-set-test message (RSM)

— User part flow control (UFC) message groups

— SNM messages have a service indicator (SI) of 0000.

• The SINAP/SS7 system discards all incoming and outgoing MTP messages whose SI is not 0000 or 0001.

• The SINAP/SS7 system discards all incoming and outgoing messages (user traffic) for all types of applications: TCAP, SCCP, and ISDN User Part (ISUP).

MTP Restart Processing for the ANSI VariantTo enable the SINAP/SS7 system to perform MTP restart (based on the 1992 edition of ANSI standards) on a particular node, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

MTP_ANSI92_RESTART=1

You need not assign a value to the environment variable. The Node Management parent (nmnp) process only validates the existence of the environment variable.

N O T E S1. You should be familiar with the fundamental operation of

the ANSI MTP restart process as indicated in Section 9 of the ANSI T1.111.4 Standards. MTP restart does not apply



to the operation of a single node. If you are running a single SINAP node, do not enable the MTP restart feature because this feature requires links to other nodes in the SS7 network.

2. If you do not define this variable, the ANSI restart functionality is not implemented and the network processing is based on the 1990 ANSI Standards for MTP, which do not include restart functionality.

MTP restart can be applied in two different ways: using a SINAP node as the restarting signaling point, or using a node adjacent to the SINAP node as the restarting signaling point. Both options are described in the following sections. Only a full restart can be performed; the ANSI network variant does not support a partial restart.

ANSI MTP Level 3 timers define the maximum amount of time that the restart signaling point or its adjacent signaling points can take to perform specific MTP restart tasks. You can access these timers by executing the MML command, CHANGE-SYSTAB. (See Chapter 4, ‘‘System Operation and Maintenance,” for more information.)

Message Processing During MTP RestartThe signaling point carries out link activation procedures on as many other unavailable links as possible. When the first link goes into the in-service state at Level 2 or another route becomes available, the restarting signaling point begins accepting only the SNM message types: TFP, TFR, TFA, TRA, TRW, CBD, and CBA that have a service indicator (SI) of 0000 and SLT and SLTA messages with an SI of 0010. It discards any other SNM message types.

Note that while a SINAP node is restarting, user traffic (for example, SCCP and TCAP traffic) is discarded. When an adjacent node is restarting, user traffic to and from the adjacent destination is discarded.

Performing MTP Restart on a SINAP NodeIf the environment variable, MTP_ANSI92_RESTART is defined and all links from this SINAP node are unavailable, the node initiates a full MTP restart.

If the environment variable is defined, the interval for which the SINAP node is unavailable is set to persist for at least the time period defined in timer T27 (2 through 5 seconds). This ensures adjacent points are aware that the restarting node is unavailable.

The node attempts to bring a predetermined number of links in each of its link sets into the available state. Links that are transmitting or receiving processor outage status units become ineffective because SINAP does not support local processor outage (LPO). In this case, MTP restart operations resume after timer T27 expires. Messages buffered in MTP Level 2 during the period of unavailability on those transmitting or receiving links are discarded unless the messages were buffered for a period less than the interval defined in timer T1. The SINAP node carries out link activation procedures on as many other unavailable links as possible.



When the first link goes into the in-service state at Level 2, the restarting node processes any TFP, TFR, TRA, and TRW messages. The SINAP node starts T22 and T26 timers either when the first signaling link goes into the in-service state at Level 2, or when the first signaling link becomes available at Level 3.

When the restarting node receives a TRW message before user traffic restarts on the link(s) to the signaling point that sent the TRW message, timer T25 starts. Traffic cannot restart on that link set until the restarting node receives a TRA message or the timer expires.

When the first signaling link of a signaling link set is available, the restarting node immediately restarts the MTP message traffic terminating at the far end of the link set. The node also sends a TRW message to the signaling point at the far end of the link set.

When timer T26 expires, the node restarts timer T26 and sends a TRW message to the adjacent signaling points connected by an available link.

Level 3 management stops timer T22 when sufficient links are available to carry the expected signaling traffic. When timer T22 expires or is stopped, the restarting SINAP node starts timer T23. During the T23 period, the signaling point receives additional TFP, TFR, TRA, TRW, CBD, and CBA messages. After TRA messages are received from all available links or Level 3 management determines that sufficient TRA messages were received and traffic can be handled, timer T23 is stopped.

N O T E S1. The SINAP/SS7 system counts the number of available

links. When at least 50% of the load-sharing links are available, the SINAP/SS7 system stops timer T22 and starts T23. Timer T23 stops when all of the expected TRA messages are received for all available link sets.

2. Although ANSI does not support partial restart, you can simulate a partial restart by assigning a small value to T22 and T23 timers.

3. There are no requirements in ANSI Standard T1.111.4 that address the issue of a “restart within a restart.” Consequently, behavior of the SINAP node under these conditions is undefined if a restart within a restart occurs. If you know that all links in the linksets will experience a “restart within a restart,” (for example, in the unlikely event when all links bounce during the restart process) then you should manually restart the SINAP node by executing the command restart at the terminal where the SINAP node was originally started. You can then manually restart any user applications which did not automatically restart during the SINAP start up.



C A U T I O NIf a “restart within a restart” continues to occur, inform the SS7 network engineer or architect to investigate potential reasons for these occurrences as they may be indications that significant link/link problems exist in the network.

When timer T23 stops or expires, timer T26 stops. The restarting node sends TRA messages to adjacent signaling points and starts user traffic by sending users MTP-RESUME primitives for all accessible destinations. The node also starts timer T29 for all signaling points to which a TRA message was sent.

If the first link in a previously unavailable link set becomes available while T23 or T24 is running, the restarting node sends a TRW message to the point at the far end of the link.

The SINAP/SS7 system does not support ANSI timers T24 and T30, which are timers for an STP.

Performing MTP Restart on an Adjacent NodeThe SINAP/SS7 system considers the MTP of an adjacent signaling point restarting when the first link in a direct link set is in the in-service state at Level 2 or another route becomes available. At this point, the SINAP node processes TRW, TRA, TFP, TFR, and TFA messages from the restarting signaling point. Timer T28 starts at this point or when the first signaling link becomes available at MTP Level 3.

N O T EThis changeback procedure is executed at the end of the adjacent MTP restart procedure.

If the SINAP node receives a TRW message from the adjacent restarting signaling point while timer T28 is running or before T28 starts, the node starts timer T25 and stops T28 if it is running. If the node receives a TRW message from the adjacent restarting signaling point while timer T25 is running, the node restarts timer T25.

When the first link in a link set to the adjacent restarting point becomes available, the SINAP node sends a TRA message to the adjacent restarting signaling point.

After the SINAP node receives a TRA message from the adjacent restarting point, the SINAP node stops T25 or T28 (whichever is running) and restarts traffic on the link set to the adjacent restarting point. The node sends MTP-RESUME primitives to users concerning the adjacent restarting point and any destinations made accessible by it.

When timer T28 expires, the SINAP node restarts traffic on the link set to the adjacent restarting point if a TRA message was not sent to it. If one was sent, the node starts T25, completes sending TFP and TFR messages, and sends a TRA message. Then, unless a TRW message was



received from the adjacent restarting point without a subsequent TRA message, the SINAP node stops timer T25 and restarts traffic on the link set to the adjacent restarting point.

If timer T25 expires, the node restarts traffic on the link set to the adjacent restarting signaling point. After traffic restarts, if the node does not receive a TRA message from the adjacent restarting point, the node restarts timer T29. If the node receives an unexpected TRA or TRW message from an adjacent restarting signaling point, the node returns a TRA message to the adjacent restarting point originating the unexpected message and starts timer T29.

A received TRW or TRA message is not unexpected if T22 or T23 is running and a direct link is in-service at Level 2 to the point originating the message, or if T25, T28, T29, or T30 is running for the signaling point that originated the message.

Displaying MTP Restart System InformationSeveral MTP level-3 (L3) timers define the maximum amount of time the MTP restart node or its adjacent nodes can take to perform specific MTP restart tasks. You access these timers through the MML command, CHANGE-SYSTAB, which you can execute through the SINAP/SS7 Terminal Handler or the SINAP/SS7 UNIX command, send_cm. See the discussion on “Changing Timers and Link Congestion Threshold Settings” in Chapter 4 for more information on CHANGE-SYSTAB.

Table 3-22 describes the MTP L3 timers related to MTP restart. (In the table, an adjacent node is any node next to the node performing MTP restart.) The timer values specified are the default values. Using CHANGE-SYSTAB, you can set any values allowed by the standards for your network variant.

Table 3-22. MTP Restart Timers (Page 1 of 2)

MTP L3 Timer

Default Value(in Milliseconds)

Description

L3T19 67000 ms CCITT network variant only. Supervisory timer used to keep track of the TFP, TFR, and TRA messages passed between the MTP restart node and adjacent nodes. (This timer helps ensure that these messages do not ping-pong between the nodes.)

L3T20 59000 ms (CCITT and China)63000 ms (ANSI)

Set by the MTP restart node to define the amount of time within which MTP restart activities should be completed.

L3T21 63000 ms (CCITT and China)90000 ms (ANSI)

Set by an adjacent node to define the amount of time within which the MTP restart node is expected to finish MTP restart.

The following timers are used by the ANSI network variant only:



The SINAP/SS7 sy utility provides the following information about MTP restart:

• The sy command, #L3,RES, displays MTP restart information, such as:

— The own_sp_restarting flag (which indicates whether this SINAP/SS7 node is currently executing MTP restart)

— The number of active link sets

— The T22, T23, T26, and T27 timers

— The number of TRA messages received (for the ANSI variant)

— TRW messages (for the TTC variant)

— The L3T20 timer ID (for CCITT variant)

L3T22 60000 ms Defining the period (at the restarting signaling point) to wait for signaling links to become available

L3T23 60000 ms Defining the period (at the restarting signaling point) to wait to receive all TRA messages after timer T22 starts

L3T25 30000 ms Defining the period (at the restarting signaling point) to wait for a TRW message

L3T26 12000 ms Defining the period to wait before repeating the TRW message

L3T27 2000 ms Defining the minimum duration of unavailability for a full restart. The value in parentheses is the lower bound to use for long propagation delay signaling routes (such as routes using satellite sections).

L3T28 35000 ms At the signaling point adjacent to the restarting signaling point, defining the period to wait for the TRW message

L3T29 60000 ms Starting when a TRA is sent in response to an unexpected TRA or TRW message

Table 3-22. MTP Restart Timers (Page 2 of 2)

MTP L3 Timer

Default Value(in Milliseconds)

Description


MTP Time-Controlled Changeover

• The following sy commands display timer values and include information about the MTP restart timers:

#L3,LST #L3,TIM #STA,ST,L3

N O T EIn addition to displaying timer information, the first command (#L3,LST) displays a flag for each active link set. The flag indicates whether the node connected by the link set is executing MTP restart.

Completing MTP RestartMTP restart ends when one of the following events occurs:

• The designated timers expire.

• (CCITT/China) when the SINAP/SS7 node receives TRA messages over more than half of all currently activated link sets.

• (ANSI) when the SINAP/SS7 node receives a TRA message on all available link sets.

At the completion of MTP restart, the SINAP/SS7 node sends a TRA message to each of its adjacent nodes to indicate it is ready to accept user traffic. The SINAP/SS7 system informs each of its local MTP user parts that restart has ended by sending each user part an MTP-RESUME primitive that indicates the accessibility of each adjacent node. The SINAP/SS7 node can then resume passing user traffic for its MTP user parts.

N O T EIf MTP restart is enabled, the SINAP/SS7 system does not send the MTP-RESUME primitive until timer L3T20 expires or until MTP restart ends. If MTP restart is not enabled, the SINAP/SS7 system sends a primitive whenever a link set or route set comes into service.

MTP Time-Controlled ChangeoverThe SINAP/SS7 system supports time-controlled changeover (TCCO) procedures for all network variants. TCCO supports handling of long-term or short-term processor outages or changeover orders received from the remote end during the MTP Level 3 T1 timer period.

This section provides an overview of TCCO processing for both short- and long-term outages and describes the environment variable you need to define before starting TCCO on your system.



Overview of MTP TCCO ProcessingThe SINAP/SS7 system implements TCCO procedures and starts the MTP T1 timer under the following conditions:

• When the SINAP/SS7 system receives a remote processor outage (either short- or long-term) on a link at the remote end and it is not possible to exchange changeover messages because doing so might cause a link failure.

• No signaling path exists between the two ends of the unavailable link so the exchange of changeover messages is impossible.

• A signaling link currently carrying traffic was marked inhibited either locally or remotely.

In each case, the Level 3 changeover control (TCOC) function receives the message, signaling link unavailable, from the link availability control (TLAC) function. When TCOC receives this message, the SINAP/SS7 system initiates changeover or TCCO activities.

Short-Term Processor OutageA short-term processor outage is one that terminates before the MTP T1 timer expires. If the SINAP/SS7 system receives a changeover order for the unavailable link from the remote end during the T1 timer period, the system initiates normal changeover procedures, completes TCCO procedures, and sends a changeover acknowledgment (COA) to the remote end.

Long-Term Processor OutageA long-term remote processor outage occurs when the MTP Level 3 TCCO T1 timer expires. To avoid sending old messages when the remote processor outage state terminates, the SINAP/SS7 system discards MTP Level 2 messages in the retransmission buffer and synchronizes sequence numbers.

N O T EThe SINAP/SS7 system flushes old messages and synchronizes MTP Level 2 sequence numbers by failing the link when T1 expires (a long-term processor outage condition). This puts the link out of service, flushes old messages, synchronizes sequence numbers, and starts the initial alignment procedure.

If a changeover order is received for the unavailable link after the T1 timer expires, the concerned signaling point responds with an emergency changeover acknowledgment (ECA).

Implementing the TCCO FeatureYou must define the appropriate environment variable to enable TCCO functionality.


MTP Time-Controlled Diversion

For the CCITT or China network variants, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

MTP_WHITE_BOOK_TCCO=1

You need not assign a value to the variable. The SINAP/SS7 system simply verifies that the variable exists. You must define this environment variable before you start or restart the SINAP node to implement TCCO functionality based on the 1993 ITU-T recommendations for MTP. If you do not define it, the system defaults to TCCO procedures based on the 1988 recommendations.

For the ANSI network variant, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

MTP_ANSI92_TCCO=1

You need not assign a value to the variable. The SINAP/SS7 system simply verifies that the variable exists. You must define this environment variable before you start or restart the SINAP node to implement TCCO functionality based on the 1992 ANSI standards for MTP. If you do not define it, the system defaults to TCCO procedures based on the 1990 standards.

MTP Time-Controlled Diversion In the CCITT, TTC, and China network variants, the time-controlled diversion (TCD) functionality is implemented automatically and is transparent to the user. That is, there are no environment variables to be set. The ANSI network variant requires that an environment variable be set, as described later in this section.

The SINAP/SS7 system implements a TCD process when the signaling point at the far end of the link made available is currently inaccessible from the signaling point initiating the changeback order. The SINAP/SS7 system also performs TCD when the concerned signaling point is accessible, but there is no signaling route to it using the same outgoing signaling link(s) or one of the same signaling links from which traffic is diverted.

TCD is primarily used at the end of MTP restart when an adjacent signaling point becomes available. TCD is intended to delay changeback to avoid missequencing messages to destination points after a remote point code restarts.

Traffic diversion can be performed at the discretion of the signaling point initiating changeback, as follows:

• On a destination basis for each traffic flow

• On an alternative signaling link basis for all destinations previously diverted on the alternative signaling link


Disabling MTP Level 3 Point Code Discrimination (CCITT)

• Simultaneously for a number of alternative signaling links or for all alternative signaling links

A signaling point can also apply TCD for changeback between different link sets, instead of using the sequence control procedure, to avoid possible message missequencing or problems with multiple, parallel changebacks.

When changeback is initiated after MTP restart, the adjacent signaling point stops traffic to the point where it is restarting and diverts traffic to alternative links for an interval defined by timer T3. After that interval, the adjacent signaling point starts traffic on the links made available. The time delay minimizes the probability of out-of-sequence message delivery to the destination point(s).

Implementing TCD in the ANSI Network VariantTo enable TCD based on 1992 ANSI standards, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

MTP_ANSI92_TCD=1

If you do not define this variable, the system defaults to TCD functionality based on the 1990 ANSI standards.

The Node Management node parent (nmnp) process validates the existence of the value specified in this environment variable and stores the value in shared memory in the static tables.

Do not enable the TCD feature via the environment variable MTP_ANSI92_TCD if the MTP_ANSI92_RESTART environment variable is already set. The restart procedure defined by the MTP_ANSI92_RESTART environment variable automatically engages TCD. Enabling the ANSI 92 TCD process via the environment variable MTP_ANSI92_TCD causes TCD to occur unconditionally for any link coming into service. This delays the changeback completion 500 ms per link. (500 ms is the default value for the T3 timer.) If this delay is unacceptable, do not enable the TCD feature via the environment variable.

Disabling MTP Level 3 Point Code Discrimination (CCITT)An environment variable (DISABLE_MTP_DISCRIMINATION) can be set which disables MTP Level 3 point code discrimination and allows any MSU received by the SINAP node (regardless of destination point code (DPC) to be routed to the appropriate application process.

When this variable is uncommented in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file, the node discards all SCCP management and MTP management messages with a DPC that is not equal to own point code. MTP and SCCP messages containing a DPC that is equal to own point code are handled according to the 1993 ITU-T Recommendations for MTP and SCCP.


MTP Eight-bit SLS Processing

N O T EThis feature is only applicable to the CCITT network variant.

MTP Eight-bit SLS ProcessingIn the ANSI network only you can optionally select eight-bit SLS Processing for a National Network (based on 1996 ANSI standards T1.111.4 and T1.111.5) using the MML command CHANGE-SLSTYPE. See ‘‘Change SLS Processing Scheme’’ in Chapter 4, Appendix C, ‘‘SINAP/SS7 MML Command Summary,” and Appendix E, ‘‘ANSI Configuration Parameters,” for more detailed information on this command. After starting the SINAP node, you can enter the CHANGE-SLSTYPE at any time via the sysopr to change the SLS scheme to either 8-bit or 5-bit processing. This initial default after the SINAP software is installed and started is the 5-bit processing scheme. You can also specify either an 8-bit or 5-bit SLS processing scheme in the initial load MML file by adding one of the following lines to the file:

CHANGE-SLSTYPE:TYPE=8;

or

CHANGE-SLSTYPE:TYPE=5;

You can place the MML command anywhere in the file. However, since it is a global definition, you should place it following the CREATE-OSP line (see the man page for CHANGE-SLSTYPE for further details).

Determining Which SLS Processing Scheme to UseBefore implementing the 8-bit SLS processing scheme, you should consider the SS7 network in which the SINAP node resides to determine whether to implement an 8-bit or 5-bit SLS processing scheme. Use the guidelines contained in the following chart to determine which scheme to use.

Table 3-23. SLS Processing Scheme

Use This SLS Scheme When...

8-bit • All network components (including STPs and SPs behind the STPs) support the 8-bit scheme.

• The majority of components in the network support the 8-bit scheme and the remainder can accept (without any anomalies) an 8-bit SLS but use the 5-bit scheme.

Note: The 8-bit SLS processing scheme is backward compatible with the 5-bit scheme (per 1996 ANSI standard T1.111.5).


Determining a Local Processor Outage Condition

Whenever you add or remove components from the network, consider whether the changes require you to change the SLS processing scheme, then make the changes as necessary through sysopr.

N O T EAutomatic switchover between the 5-bit and 8-bit scheme is not reliable and is not implemented in the SINAP/SS7 software. This is because an SLS in an incoming message with a format of (binary) 000xxxxx is ambiguous. The format could represent a 5-bit or 8-bit SLS. In addition, if a counter is used to implement automatic switchover in a system where all traffic is loadshared, there would be an excessive potential switchover error of 12.5% (32/256 x 100). Also, certain components in the SS7 network may be down (for example, periodic maintenance) and the SINAP node cannot discern whether these components use the 5-bit or 8-bit scheme.

Determining a Local Processor Outage Condition You can activate heartbeat messages between MTP Level 2 and Level 3 on a SINAP node to determine whether a local processor outage (LPO) has occurred on the node. When you activate these messages, MTP Level 2 sends a heartbeat message to MTP Level 3 and expects MTP Level 3 to respond with an I'm Alive heartbeat message within two seconds. If MTP Level 3 fails to return five heartbeat messages in a row within 10 seconds, MTP Level 2 considers the link to be in an LPO condition. In this case, the SINAP node notifies the link's remote end of the processor outage.

N O T EHeartbeat messages are exchanged on a link-by-link basis for all activated links on the node. Turning this feature on may compromise the performance of the SINAP node.

To activate the exchange of heartbeat messages between MTP Level 2 and Level 3, perform the following tasks:

5-bit • The majority of the network components support an 8-bit scheme but the remainder of the components cannot accept an 8-bit SLS.

• None of the network components supports an 8-bit scheme.

Table 3-23. SLS Processing Scheme


Connection-Oriented Services

1. Change the timer L3T17 from its default setting (800 ms) to an odd number in the range 800-1500 ms using the MML command CHANGE-SYSTAB.

If you stop the node after changing the L3T17 timer value, the heartbeat message exchange automatically begins when you restart the SINAP node. If you do not stop the node after changing the timer value, you must perform Step2.

2. Change the state of the links over which the heartbeat messages are to be exchanged from ACTIVE to INACTIVE, then back to ACTIVE using the MML command CONFIGURE-LINK.

The heartbeat message exchange between MTP Level 2 and Level 3 begins immediately.

To deactivate the exchange of heartbeat messages, repeat Steps 1 and 2, but set the L3T17 value to an even number in the range 800-1500 ms).

Connection-Oriented ServicesThis section describes the SINAP/SS7 connection-oriented feature (COF), which provides SCCP class-2 and class-3 connection-oriented services.

• Class 2 provides basic connection-oriented services.

• Class 3 provides connection-oriented services with flow control.

Currently, you can implement connection-oriented services only in SINAP/SS7 configurations that use the CCITT and the China network variants for their network protocol and possibly (although not necessarily) for their TCAP protocol. Since the TTC standards do not define the use of connection-oriented services, the TTC variant of the SINAP/SS7 system does not support this feature. Although the ANSI standards do support connection-oriented services, this feature is not supported by the ANSI variant of the SINAP/SS7 system.

Connection-oriented services enable an application to establish and maintain a connection or logical communication path with another application for the purpose of exchanging small and large messages. A small message contains no more than 256 bytes of user data, the maximum amount of user data that fits in a single message. A large message contains between 257 and 8192 bytes of user data, which is more data than can fit in a single message. Therefore, the user data in a large message must be divided into multiple segments, each of which is then transported over the SS7 network in a single message. At the destination, the user data in each of these messages is reassembled to form the original user data, which consisted of a single block of data.

To use connection-oriented services, an application running on the SINAP/SS7 system (the local application) must assign values to the following data fields in its CA_REG global variable. These values tell the SINAP/SS7 system that the application will use connection-oriented services rather than connectionless services:

• max_user_data_size—The maximum number of user data blocks in bytes


Connection-Oriented Services

• max_connections—The maximum number of connections for this process

The third data field, connections_are_owned, is for internal use by the SINAP/SS7 system and should not be modified.

See the SINAP/SS7 Programmer’s Guide (R8052) for more information.

N O T EUsing connection-oriented functionality (COF) in an SS7 network can be computationally expensive. This potential problem is not specific to the SINAP/SS7 system, but universal to SS7 networks.

The Stages of Connection-Oriented Communication The process of communicating via connection-oriented services consists of the following stages:

• The connection-establishment stage occurs when two applications obtain a unique connection ID and establish a connection. During this stage, the local and remote applications do not communicate directly. Instead, the applications communicate via IPC messages.

• The data-transfer stage occurs when the applications communicate with each other directly via the connection they established earlier. During this stage, the local application can call CASL functions (ca_put_sc() and ca_get_sc()) to send messages to and retrieve messages from the remote application.

• The connection-release stage occurs when the connection and its associated resources are released.

Activating Connection-Oriented ServicesTo activate connection-oriented services on a SINAP/SS7 node, you must uncomment the environment variables described in Table 3-24 in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

Table 3-24. Environment Variables for LRNs (Page 1 of 2)

Environmental Variable Description

SINAP_TOTAL_LR_MEMS=nnnn Defines the number of local reference memory (LRM) structures specified by nnnn (up to 2000).


Defining ISDN User Part (ISUP) Functionality

Defining ISDN User Part (ISUP) FunctionalityThe CCITT, NTT, China, and ANSI network variants support the Integrated Services Digital Network User Part (ISUP) signaling functions required to support circuit switched services for voice and nonvoice connections to an integrated services digital network.

The SINAP/SS7 system implements ISUP functionality by activating the environment variable ISUP_FEATURE. For more detailed information, see the SINAP/SS7 ISDN User Part (ISUP) Guide (R8053).

Handling SNM Messages with Nonzero SLCsThe CCITT, China, and ANSI network variants support handling SNM messages with nonzero SLCs.

In the ANSI network variant, the SINAP/SS7 system automatically implements this feature. There is no need to define an environment variable.

The 1988 ITU (CCITT) Recommendations for MTP require that all MTP level-3 SNM messages use a signaling link code (SLC) of 0. The 1993 ITU Recommendations for MTP contain the ability to use a nonzero SLC value for any SNM message that is not related to a

SINAP_USER_LR_MEMS=nnnn Defines the maximum number of connections (up to 2000), specified by nnnn, that an application can have open at any time.

Note: Every connection requires an LRM; therefore, regardless of the value specified for SINAP_USER_LR_MEMS, the SINAP/SS7 system will not establish more connections than the number of LRMs defined by SINAP_TOTAL_LR_MEMS.

SINAP_TOTAL_LR_NUMS=nnnn Allocates the number of LRNs specified by nnnn (up to 5000). To accommodate the amount of time an LRN is frozen after use, Stratus recommends allocating more LRNs than LRMs.

SINAP_LRN_FREEZE_TIMEOUT=nnnn Specifies the number of seconds (up to 1800) before an unused local reference number (LRN) is released and can be assigned to another LRM structure.

Table 3-24. Environment Variables for LRNs (Page 2 of 2)

Environmental Variable Description


Enabling Random SLS Generation

signaling link, such as a signaling route management (SRM) message. To activate this feature on a CCITT or a China network variant of SINAP/SS7 node, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

MTP_WHITE_BOOK_SLC=1

You need not assign a value to the variable. The SINAP/SS7 system simply verifies that the variable exists. For instructions on defining variables, see the discussion on defining SINAP/SS7 environment variables in Appendix B.

If this environment variable is not defined for CCITT and China network variants, the SINAP/SS7 system discards any incoming SNM messages whose SLC is not 0. If the variable is defined, the SINAP/SS7 system allows incoming SNM messages to have an SLC value other than 0.

Enabling Random SLS GenerationSINAP, by default, conforms to the ANSI T1.111.4 standard (1988) and uses a default SLS of zero for the Route Set Congestion Test (RCT) message. However, always sending the RCT message on the same link within the same link set that the TFC was received on always results in the RCT message testing the same network path, which might or might not be congested. If traffic is not evenly distributed this might result in over-controlling (which will occur when the RCT message is routed on the path that is more likely to be congested) or under-controlling (which will occur when the RCT message is routed on the path that is more likely to not be congested).

Random Link SelectionTo smooth out this effect, SINAP provides a feature for the user to enable the generation of a random signaling link selection (SLS) for RCT. The random SLS is placed in the SLS field of the outgoing RCT message.

To enable this feature, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

MTP_RCT_LOAD_SHARING_SLS=YES

N O T EThis feature is available for ANSI users only. Setting the environment variable has no effect for other NSP variants.


Defining UPU Messages

Defining UPU Messages User part unavailable (UPU) functionality is supported by the CCITT, China, and ANSI network variants. The TTC network variant does not support UPU messages.

UPU functionality is part of MTP level-3 signaling-traffic flow control. This feature enables MTP to send a UPU message to an origination user part (that is, an application) when the SINAP/SS7 system cannot deliver an incoming message to its destination. The origination application can then arrange to stop sending messages to that destination until it becomes available again.

The SINAP/SS7 system now supports several new UPU message unavailability-cause reasons. They explain why MTP could not deliver a message to its destination. Table 3-25 describes the meaning of these new messages.

To activate UPU functionality on a particular SINAP/SS7 node, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

MTP_USER_FLOW_CTL=1

You need not assign a value to the variable. The SINAP/SS7 system simply verifies that the variable exists. For instructions on defining variables, see the discussion on defining SINAP/SS7 environment variables in Appendix B.

If this environment variable is not defined, the SINAP/SS7 system does not generate a UPU message when it cannot deliver an incoming message, even if the destination user part is unavailable. If it is defined, the SINAP/SS7 system generates a UPU message when it receives an incoming message that it cannot deliver. See the SINAP/SS7 Programmer’s Guide (R8052) for details on how SINAP handles incoming UPU messages and requirements for applications.

For ISUP messages, no UPU will be sent if ISMG is running, even if no ISUP application is registered.

To overcome this ISUP limitation, a new feature, controlled by a SINAP environment variable called “ISUP_UPU_FEATURE”, is introduced. ". When the user sets ISUP_UPU_FEATURE to 1 in sinap_env.[sh|csh], the feature will be activated. At the same time, SINAP will implicitly

Table 3-25. New Unavailability-Cause Values for UPU Messages

Unavailability-Cause Value Numeric Values Description

UPU:unknown 0 Unknown reason

UPU:unequipped remote user 1 The user part is not equipped.

UPU:inaccessible remote user 2 The user part is equipped but not accessible.


Defining XUDT and XUDTS Messages

activate the environment variable called "MTP_USER_FLOW_CTL". If the user wants "MTP_USER_FLOW_CTL" only, please do not specify "ISUP_UPU_FEATURE".

When the feature is activated, SINAP will send User Part Unavailability (UPU) message to each remote point code from incoming ISUP messages when the ISUP user application is down. If both ISMG and SCRs are down, the UPU message will contain the cause of UNEQUIPPED, if ISMG is up but SCR is down, the UPU message will contain the cause of INACCESSIBLE. The UPU message will be only sent once for the same remote point codes.

The ANSI variant of SINAP/SS7 is based on T1.111 (1990/1992), which does not have "Unavailability cause" field (added in 1996 T1.111) in the UPU message. As shown at 15.17.2/T1.111.4 (1992), these four bits are coded "0000" as Spare field in UPU.

This new feature be automatically disabled for DLPC/LPCR configuration, even if we have the environment variable ISUP_UPU_FEATURE set. This is because in DLPC/LPCR configuration, SINAP will be acting as an STP. Hence, we can send TFP message to the remote ends to stop ISUP traffic flow.

Defining XUDT and XUDTS MessagesSINAP/SS7 networks configured for CCITT or China support the following two types of messages that might be exchanged by applications running in your network:

• Extended unitdata (XUDT) messages carry segmented message data for connectionless protocol classes, 0 and 1. The message sends data with or without optional parameters. XUDT message segments are those message signaling unit (message) segment sizes that are smaller than the default or maximum segment size used to exchange messages in the SINAP/SS7 system.

• The SINAP/SS7 system sends extended unitdata service (XUDTS) messages to the originating SCCP application when an XUDT message with optional parameters cannot be delivered to its destination because of an error. An XUDTS message is sent only when the return on error option is set in the XUDT message.

Applications can exchange XUDT messages if they register with CASL at the SCCP XUDT or TCAP XUDT boundary. However, applications can still use the existing API to exchange unitdata (UDT) messages even if they are registered at the SCCP XUDT or TCAP XUDT boundary.

The mechanism for determining whether the message type is UDT or XUDT differs for applications registering at the SCCP and TCAP boundaries. An application registering at the SCCP boundary specifically builds a message of the type, UDT or XUDT, and sets the desired message size. An application registering at the TCAP boundary uses the total size of all components to decide the message type.



XUDT functionality segments messages up to 2048 bytes long into multiple XUDT message segments up to a maximum of 16. The maximum segment size (including the length of the data and address parameter fields in the MSU) depends on the network variant you are using.

All XUDT messages that are segments of the same message are assigned the same unique identification number or local reference number (LRN). Each time an LRN is released, it cannot be reused on a node-wide basis for a minimum period of time defined by the SCCP freeze timer, SCTX. This timer defines the time period during which an LRN assigned to multiple segments of the same message is frozen.

N O T EThe SINAP/SS7 system automatically provides the freeze timer value in the current software release and does not implement any changes you might make to the SCCP SCTX timer. (See Chapter 4 for information on displaying and changing the XUDT timer values.)

The message reassembly process must receive all segments and reassemble the message within the time period specified in the SCCP reassembly timer, SCTY. There is one SCTY timer per node. All segments of an XUDT message must be received and reassembled before the SCTY timer expires. The default value is 1 second. If the message is not reassembled in the allowed time period, the SINAP/SS7 system discards the message and sends an XUDTS message to the originating application if the XUDT message had the return message on error field checked. This error message indicates that the message was not delivered because of an error. The XUDTS message contains the first segment of the XUDT message. The SINAP/SS7 system handles XUDTS messages and XUDT messages in the same manner.

You can display the XUDT timer values using the following MML command:

DISPLAY-SYSTAB:TABID=SCCPTM,TIMER=SCTY;

You can also use the send_cm command to issue the command.

You can change an SCCP XUDT timer value through the Terminal Handler using the MML command, CHANGE-SYSTAB. See Chapter 4 for more information on displaying and changing the XUDT timer values.

XUDT MSU Segment SizesThe system guarantees that each MSU segment generated for an XUDT message is the same size, except for the last segment. You can use the default segment size for your network variant, or define a smaller size.

Issue the following sy command to view the default XUDT MSU segment size for your system:

#sta,xudt



The SINAP/SS7 system uses the maximum segment size as the default for the network variant being used. For CCITT, the maximum segment size is 254 bytes. For China, the maximum segment size is 251 bytes. Both sizes include the data and address fields.

You can define a segment size that is smaller than the maximum (default) size by uncommenting the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file and setting it to the desired value before starting the SINAP node.

SINAP_XUDT_SEGMENT_SIZE=<VALUE>

N O T EThe SINAP/SS7 system uses the default segment size unless you define the SINAP_XUDT_SEGMENT_SIZE environment variable, or if you specify a segment size greater than the maximum allowed for your variant.

Validating the XUDT Message Segment SizeThe nmnp process validates the value specified in the SINAP_XUDT_SEGMENT_SIZE environment variable shared memory static tables.

Enabling Processing of Subsystem Status Tests in XUDT MessagesFor the CCITT network variant only, you can define an environment variable that activates the option that allows a SINAP node to receive and process an SCCP subsystem test (SST) in an extended unitdata (XUDT) message. If the subsystem (SSN) specified in the XUDT message is in an allowed state, the SINAP node sends a subsystem allowed (SSA) message to the original calling address.

To activate this option, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

CCITT_XUDT_SCMG=1

You do not need to specify a value for the variable. The SINAP/SS7 system only verifies the existence of the variable.

If you do not define this environment variable, the SINAP/SS7 system discards any XUDT SCCP management (SCMG) messages it receives because SCMG messaging is normally handled only by UDT messages.



Setting the Hop Counter in Incoming XUDT MessagesIn the CCITT network variant, SINAP/SS7 applications registered at the TCAP boundary have access to the hop counter value in an outgoing SCCP XUDT message. However, the hop counter value received in an XUDT message is not normally passed up to the TCAP application to use.

For the CCITT network variant only, you can define an environment variable that activates the option that allows a SINAP node to pass the hop counter value received in an XUDT message up to the TCAP application to use.

To activate this option, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

TCRELAY=1

You do not need to specify a value for the variable. The SINAP/SS7 system only verifies the variable has a value.

If you do not define this environment variable, the SINAP/SS7 system will not pass the hop counter value received in an UXDT message up to the TCAP application to use.

1996 ITU-T SCCP XUDT/XUDTS Importance Parameter SupportTo enable 1996 ITU-T SCCP Importance Parameter (1996 ITU-T Q.713 3.19) support in XUDT/XUDTS messages (CCITT only), define the following environment variable before starting the SINAP/SS7 system:

SCCP_ITU96_IMPORTANCE_PARM

For user application registering at SS7_INPUT_BOUNDARY_SCCPX boundary, a field - importance_parm - has been added at mblock.h sccp_ctrl_t data structure as U8 data type to represent for the 3-bit Importance values. Since 0 is also a valid Importance value, the MSB of importance_parm is used as a flag to indicate if Importance parameter is included and the 3 LSBs of importance_parm arethe Importance values.

For user application registering at SINAP SS7_INPUT_BOUNDARY_TCAPX boundary, a field - importance_parm - has been added at tblock.h tc_dhp_t data structure, which has the similar representation/usage as the importance_parm at mblock.h sccp_ctrl_t.

To access or set the values of the Importance Parameter at the XUDT message received or to be sent, the user application must access or set the importance_parm field at the corresponding m_block_t or t_block_t data structure accordingly.


Enabling Loopback Detection (CCITT)

Enabling Loopback Detection (CCITT)For the CCITT network variant only, when the loopback detection environment variable is defined, the SINAP/SS7 system can detect when a remote link is in a loopback mode. During a signaling link test (SLT), normally run after MTP Level 2 alignment, if the SINAP/SS7 system receives signaling test messages (SLTMs) from the remote link that are identical to the SLTMs it sent to that link for all signaling link test attempts, and no correct signaling link test acknowledgment (SLTA) message is received, the SINAP/SS7 system sets a loopback diagnostic indicator to allow display of the loopback status on the DISPLAY-LINK screen.

N O T EThe loopback detection feature is active only during the signaling link test procedure.

To enable the loopback detection feature, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

LOOPBACK_DISPLAY=1

It is not necessary to assign a value to the variable. The SINAP/SS7 system only verifies the existence of the variable. If you do not define the environment variable, the SINAP/SS7 system does not perform loopback detection and does not display the loopback status on the DISPLAY-LINK screen.

Enabling Transfer-Restricted Message Handling For the CCITT network variant, when the SINAP node receives a transfer-restricted (TFR) message, the node starts the MTP Level 3 T10 timer and does not send a signaling route set restricted (RSR) test message immediately. An RSR is sent to the signaling transfer point referring to the destination declared restricted by the TFR message every T10 period until a transfer-allowed (TFA) message is received.

To use the transfer-restricted (national network) option, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

MTP_WHITE_BOOK_TFR=1

You do not need to assign a value to the variable, the SINAP/SS7 system simply verifies the existence of the variable.

When the MTP_WHITE_BOOK_TFR option is defined, the Display Routeset (DISPLAY-RSET) command, accessed through sysopr, displays the following additional status states for the selected route sets and routes:


Enabling Transfer-Restricted Message Handling

For Route Set Status: R - DPC restricted P - DPC prohibited

For Route Status: R - Transfer restricted P - Transfer prohibited

The following sample output shows a situation where LSET1 route is restricted (status of "R") and LSET2 route is prohibited (status of "P"). The status of the resulting RSET3 route set (or DPC=3003) is "Rbc," where "R" indicates that DPC is accessible, but restricted.

For the ANSI network variant, the SINAP/SS7 system can process both the transfer-restricted (national network) and transfer-controlled (U.S. networks), but does not allow the transfer-controlled (international networks).

Neither the TTC nor China network variants support transfer-restricted message handling. The TTC and NTT variants support transfer-controlled (with congestion priorities) procedures. The China variant supports the transfer-controlled (international network).

RSR/RSP in Response to TFR/TFPFor the ANSI network variant default setting, when the SINAP/SS7 system receives a TFR or TFP message, it waits until the MTP Level 3 T10 timer expires before sending a signaling route set test for restricted or prohibited destination (RSR or RSP) message. This behavior conforms

Display Route Set: .....RSet Name = RSET3, DPC = 3003, CPC Count of LSSN = 0State = ACTIVE, Status = Rbc, Load Sharing = YESRouteName Priority StatusLSET1 1 aRlrLSET2 2 aPlr--Route Set Status Legend-- a - DPC accessible A - DPC not accessible R - DPC restricted

P - DPC prohibited b - route set not blocked B - route set blocked c - route set not congested C - route set congested --Route Status Legend-- a - link set available A - link set not available x - transfer allowed R - transfer restricted

P - transfer prohibited l - link set not congested L - link set congested r - route not congested R - route congested


Configuring Alarm Messages to Write to the System Log Files

to 1992/1996 ANSI and ITU-T specifications. However, there is a deviation in the 1988 ANSI Standard, where an RSR or RSP is responded to immediately after the TFR or TFP is received by the receiving node, and then after every T10 period. If this behavior is desired, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

MTP_ANSI88_RSR_RST=1

You do not need to assign a value to the variable. The SINAP/SS7 system simply verifies the existence of the variable.

Configuring Alarm Messages to Write to the System Log FilesThe SINAP/SS7 system logs its alarms and error messages to an error log file and to the console.

The SINAP/SS7 device driver uses the UNIX System V, Release 4 STREAMS (the UNIX device driver) with a UNIX kernel-utility routine (cmn_err()) to log SS7 device-driver error messages.

The process is described in the following sections.

Operating Systems Error Log FilesThe SINAP/SS7 software logs error messages to the /var/adm/syslog directory (HP-UX operating systems), or the /var/adm directory (Solaris operating systems), or the /var/log directory (Stratus ft Linux operating systems). The operating system uses the openlog(), syslog(), and closelog() commands to control entries to the system log (syslog.log for HP-UX and messages for Solaris and Stratus ft Linux systems). Refer to the operating system man pages for these commands for complete details on how they operate.

N O T E S1. The HP-UX operating system does not back up the system

error log file, syslog.log under the /var/adm/syslog directory. Instead, the SINAP node runs a shell script, /etc/bkup_syslog, at one minute to midnight. This timing ensures that the date associated with the saved file and its name is the same date on which the entries were created. The script copies the contents of syslog.log to syslog.log.YYMMDD. In addition, it removes any syslog.log.YYMMDD files older than the number of days passed as an argument to bkup_syslog. Default time is ten days.

2. The Solaris operating system does not back up the system error log file, messages under the /var/adm directory. Instead, the SINAP node runs a shell script,



/etc/bkup_syslog, at one minute to midnight. This timing ensures that the date associated with the saved file and its name is the same date on which the entries were created. The script copies the contents of messages to messages.YYMMDD. In addition, it removes any messages.YYMMDD files older than the number of days passed as an argument to bkup_syslog. Default time is ten days.

3. The Stratus ft Linux operating system does not back up the system error log file, messages under the /var/log directory. Instead, the SINAP node runs a shell script, /etc/bkup_syslog, at one minute to midnight. This timing ensures that the date associated with the saved file and its name is the same date on which the entries were created. The script copies the contents of messages to messages.YYMMDD. In addition, it removes any messages.YYMMDD files older than the number of days passed as an argument to bkup_syslog. Default time is ten days.

The Alarm Severity Level Environment VariableTo log SINAP/SS7 alarms to the error log files, uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

SINAP_CONSOLE_ALARM_LEVEL=<VALUE>

For <VALUE>, specify one of the values in Table 3-26 to indicate the severity of those alarms you want to log: CRITICAL, MAJOR, MINOR, or NOTICE. The SINAP/SS7 system logs those error messages in the Emsg file with a severity level equal to, or greater than, this value. (These error messages might be the result of a problem with either hardware or software.)

Table 3-26. Alarm Severity Levels

Field Description

CRITICAL Indicates a condition causing a severe disruption of service. This condition requires immediate attention. If you specify this value, make sure to specify the value, CRITICAL, for the severity field of the message’s syntax as it is defined in the Emsg file.



MAJOR Indicates a condition causing a serious disruption of service. If you specify this value, make sure to specify the value, NONRECOVERABLE_L or NONRECOVERABLE_LP, for the severity field of the message’s syntax as it is defined in the Emsg file.

MINOR A condition that is not likely to cause a serious disruption of service. If you specify this value, make sure to specify the value, RECOVERABLE_L or RECOVERABLE_LP, for the severity field of the message’s syntax as it is defined in the Emsg file.

NOTICE Indicates a service-affecting condition; this message is provided for informational purposes only. If you specify this value, make sure to specify the value, INFO_L or INFO_LP, for the severity field of the message’s syntax as it is defined in the Emsg file.

Table 3-26. Alarm Severity Levels

Field Description


Chapter 4 System Operation and

Maintenance4-

This chapter describes the most common tasks you perform to operate and maintain the SINAP/SS7 network. The main sections of this chapter include:

• Displaying Information for Network Components

• Changing Network Components

• Deleting Network Components

• Removing a Link, Link Set, or Route Set From Service

• Putting a New Link into Service

• Handling SINAP/SS7 Measurements

• Backing Up Databases

• Restoring Databases

• Purging and Deleting Files

• Using the BITE Monitor

• Implementing Signaling Link Test Messages

• Using the Load Control Facility

• Maintaining Connection-Oriented Services

• Downloading Link Configuration Changes in the /etc/SS7links File

For each task, the section describes the task, gives instructions for using the Terminal Handler to create the associated command, provides the MML command line entries, and includes sample screen output displays, as appropriate. All descriptions, menus, and samples are based on the CCITT network variant. Any differences for the other variants are noted.

See Chapter 2, ‘‘Performing Basic Tasks,” for instructions on using the Terminal Handler and UNIX command line interfaces and on using the man pages for online help.

Displaying Information for Network Components This section describes how to display configuration information for the network components. You access most of the commands through the Display Commands menu, which is an option of

System Operation and Maintenance 4-1

Displaying Information for Network Components

the Network Commands menu. The Display Commands menu shown in Figure 4-1 shows the choices for the CCITT and China variants.

Figure 4-1. Display Commands Menu for CCITT and China Variants

For the ANSI network variant, the menu also contains options to display combined link sets and fictitious originating point codes (FOPC). Descriptions for the ANSI commands are included in this chapter in the order they appear on this menu.

Figure 4-2 shows the ANSI network variant Display Commands menu.

Figure 4-2. Display Commands Menu for the ANSI Variant

Display Commands 1. Display Link 2. Display Linkset 3. Display Routeset4. Display Own Point Code5. Display Concerned Point Code6. Display Remote SSN7. Display System Tables8. Display Global Titles

< DISPLAY

Display Commands 1. Display Link 2. Display Linkset 3. Display Combined Linkset4. Display Routeset5. Display Own Point Code6. Display Concerned Point Code7. Display Remote SSN8. Display System Table9. Display Fictitious Originating Point CodeA. Display Global Titles



The TTC and NTT network variants do not support combined link sets, duplicate point codes, or fictitious originating point codes. Figure 4-3 shows the Display Commands menu for the TTC and NTT network variants.

Figure 4-3. Display Commands Menu for the TTC and NTT Variants

In this chapter, the description of system tables explains how to use the sy utility command to display information about the MTP restart system and link congestion.

This chapter also describes two additional display commands not included on the Display Commands menu:

• Signaling link assignments for an application, using the sy utility command

• Local subsystem numbers, accessed through the Application Commands menu (an option of the SINAP System Main Menu)

The display tasks are described in the following subsections, generally following the order of the Display Commands menu.

To print the displayed information, see the section, ‘‘Enabling and Disabling Printing’’ in Chapter 2, which describes how to enable or disable the print functions.

Displaying Link InformationThe Display Link (DISPLAY-LINK) command displays and prints the signaling link information for one link or all configured links.

For the CCITT network variant, when the loopback detection environment variable LOOPBACK_DISPLAY is defined, you can display loopback status for one link or all links, using the DISPLAY-LINK screen. To display the loopback status for one link, when prompted, enter the appropriate link number to be displayed. To display the loopback status of all links, press RETURN. The loopback status is indicated by x (no loopback) or X (loopback

Display Commands 1. Display Link 2. Display Linkset 3. Display Routeset4. Display Own Point Code5. Display Concerned Point Code6. Display Remote SSN7. Display System Tables8. Display Global Titles

< DISPLAY



based on SLTM detected). See ‘‘Enabling Loopback Detection (CCITT)’’ in Chapter 3 for more information. See also the sample display later in this section.

Menu Selection ModeFrom the Display Commands menu, select the Display Link option. The DISPLAY-LINK screen appears. Respond to the on-screen prompts to enter the name of the specific link you want to display, or press RETURN to display all configured links.

MML Command FormatThe MML command format for the DISPLAY-LINK command is:

DISPLAY-LINK:LINK=link, PRINT=print , FILE=file ;

The DISPLAY-LINK command arguments are described in Table 4-1.

Man Page FormatThe alternative and UNIX online manual (man) page format for DISPLAY-LINK is displ-link.

Table 4-1. DISPLAY-LINK Command Arguments


link Specifies the link to display. To display all links, set the value of link to ALL. To specify a particular link for display, use the label you assigned to the link when creating it.

print Specifies whether the response should be printed, as well as displayed at the terminal. Specify YES for printing to the default printer, NO for no printing, or printer ID for printing to a specific printer.

file The name of the file you want the report saved to. The file is saved by default into the $SINAP_HOME/sysopr directory. If you want the file saved into another location, include the file path in the filename specification.



Sample DisplayThe sample output of the DISPLAY-LINK command shown in Figure 4-4 displays information about all configured links but does not display Loopback status. The user entries are in bold type.

Figure 4-4. Sample DISPLAY-LINK Screen Without Loopback Status

N O T ELowercase status flags indicate positive status and uppercase status flags represent negative status. For example:

a indicates that the link is available. A indicates the that link is not available.

The sample output of the DISPLAY-LINK command shown in Figure 4-5 includes loopback status in the information about all configured links for a node configured with the CCITT network variant.

M DISPLAY-LINK:LINK=ALL; ok command completed

DISPLAY LINK:

LinkName Link LSetName LSet SLC Port Speed ADPC State Status ErrorLink0 0 lset1 0 0 0 64000 3003 ACTIV iabclrnt 0Link1 1 lset1 0 1 1 64000 3003 ACTIV iabclrnt 0Link2 2 lset1 0 2 2 64000 3003 ACTIV iabclrFt 0Link3 3 lset1 0 3 3 64000 3003 ACTIV iabclrFt 0

--Link Status Legend--i - installed I - not installeda - available A - not availableb - not remotely blocked B - remotely blockedc - not congested C - congestedl - not locally inhibited L - locally inhibitedr - not remotely inhibited R - remotely inhibitedn - link normal U - status unavailable F - link failedt - no periodic link test T - periodic link test active



Figure 4-5. Sample DISPLAY-LINK Screen With Loopback Status

You can also display the loopback status for a link (CCITT network variant only) using the sy command #L3, port without setting the LOOPBACK_DISPLAY environment variable. In the sy output shown in Figure 4-6, the SLTM Loopback Detected parameter would be set to a nonzero value if a loopback condition had been detected.

Figure 4-6. Sample #L3,port Command Output

M DISPLAY-LINK:LINK=ALL; ok command completed

DISPLAY LINK:

LinkName Link LSetName LSet SLC Port Speed ADPC State Status ErrorLink0 0 lset1 0 0 0 64000 3003 ACTIV iabclrntx 0Link1 1 lset1 0 1 1 64000 3003 ACTIV iabclrntx 0

--Link Status Legend--i - installed I - not installeda - available A - not availableb - not remotely blocked B - remotely blockedc - not congested C - congestedl - not locally inhibited L - locally inhibitedr - not remotely inhibited R - remotely inhibitedn - link normal U - status unavailable F - link failedt - no periodic link test T - periodic link test activex - no loopback X - loopback based on SLTM detected

?Hit (Q orq) to quit displaying response

Enter cmd>#L3,portL3SD port data:

0:L3MT_State=PROV_IN,lnk_set=0, install_timer=1048577 SLTM Loopback Detected=01:L3MT_state=PROV_IN,lnk_set=0,slc=1,install_timer=1048578



Displaying Link Set InformationThe Display Linkset (DISPLAY-LSET) command displays and prints the configuration for a specified link set or all configured link sets.

Menu Selection ModeSelect the Display Linkset option from the Display Commands menu. The DISPLAY-LSET screen appears. To display information about a specific link set, respond to the system prompts and enter the link set name, or press RETURN to display all configured link sets.

MML Command FormatThe MML command format for the DISPLAY-LSET command is:

DISPLAY-LSET:LINKSET=linkset, PRINT=print , FILE=file ;

Table 4-2 describes the arguments for the DISPLAY-LSET command.

Man Page FormatThe alternative format and man page format for DISPLAY-LSET is displ-lset.

Table 4-2. DISPLAY-LSET Command Arguments


linkset Specifies the link set to display. To display all links, set the value of linkset to ALL. To specify a particular link set for display, use the label you assigned to the link set when creating it.

print Specifies whether the response should be printed, as well as displayed at the terminal. Specify YES for printing to the default printer, NO for no printing, or the printer ID for printing to a specific printer.




Sample DisplayThe sample output of the DISPLAY-LSET command shown in Figure 4-7 displays information about all configured link sets. User entries are in bold type.

Figure 4-7. Sample DISPLAY-LSET Command Output

Displaying Combined Link Set InformationThe Display Combined Linkset (DISPLAY-CLSET) command is only available on a stack configured with the ANSI network variant. The DISPLAY-CLSET command displays and prints configuration information for a combined link set.

Menu Selection ModeSelect the Display Combined Linkset option from the Display Commands menu. The DISPLAY-CLSET screen appears. Respond to on-screen prompts to enter the specific link set name you want to display, or press RETURN to display all combined link sets currently configured.

MML Command Format The MML Command format for the DISPLAY-CLSET command is:

DISPLAY-CLSET:CLSET=clset,[PRINT=print],[FILE=file];

M DISPLAY-LSET:LINKSET=ALL;command completed

Display Link Set:LSet Name = LSET1, LSet = 0, ADPC = 3003, DPC Count = 1Active Links = 4, Loaded Links = 4, State = ACTIVE, STATUS = Ave

LinkName LINK SLC Priority AvailableLNKA00 0 0 0 YESLNKA02 2 2 1 YESLNKA03 3 3 2 YESLNKA04 4 4 3 YES

--Link Set Status Legend--a - available A - not availablev - active V - not activee - not emergency E - emergency



Table 4-3 describes the arguments for the DISPLAY-CLSET command.

Man Page FormatThe alternative format and man page format for DISPLAY-CLSET is displ-clset.

Sample DisplayThe sample output of the DISPLAY-CLSET command shown in Figure 4-8 displays configuration information about the combined link set, clsta. User entries are in bold type.

Figure 4-8. Sample DISPLAY-CLSET Command Output

Internal information (SLS mapping) for ANSI combined link set MTP3 and Outbound Routing can be displayed from the sy utility. These are helpful in diagnosing CLS problems with Stratus’s Customer Assistance Center (CAC) and are automatically executed as part of gathersy.

Table 4-3. DISPLAY-CLSET Command Arguments


clset Specifies the combined link set to display. To display all combined link sets, set the value of clset to ALL. To specify a particular combined link set for display, use the label you assigned when creating it.



M DISPLAY-CLSET:CLSET=clsta; ok command completed

Display Combined Link Set:

CLsetName CLset # Lset1 Name Lset2 Name Typeclsta 0 lset1 lset2 A



The following sy commands display this internal information:

Displaying Route Set InformationThe Display Routeset (DISPLAY-RSET) command displays and prints the static configuration and status of routes used to reach specified destination point codes (DPCs). The priority and status of the link sets also appears. Note that the DISPLAY-RSET command only appears route set information from the static configuration and does not display route sets that have been dynamically provisioned.

Menu Selection ModeSelect the Display Routeset option from the Display Commands menu. The DISPLAY-RSET screen displays. Respond to the on-screen prompts to display the route sets by destination point code or by route set.

MML Command FormatThe MML command format for the DISPLAY-RSET command is:

DISPLAY-RSET:ROUTESET=routeset, PRINT=print , FILE=file ;

Table 4-4 describes the arguments for the DISPLAY-RSET command.

#ORT,CLS Display outbound routing combined link set table.

#L3,CLS Display MTP shared data for all combined link sets.

#L3,CLS,x Display MTP shared data for a specific combined link set x.

Table 4-4. DISPLAY-RSET Command Arguments


routeset Specifies the route set to display. To display all route sets, set the value of routeset to ALL. To specify a particular route set for display, use the label you assigned to the route set when creating it.





Man Page FormatThe alternative format and man page format for DISPLAY-RSET is displ-rset.

Sample DisplaysThe sample output of the DISPLAY-RSET command shown in Figure 4-9 for the CCITT network variant displays the values configured for all route sets.

Figure 4-9. Sample DISPLAY-RSET Command Output for CCITT

Sample DisplaysThe sample output of the DISPLAY-RSET command shown in Figure 4-9 for the CCITT network variant shows the route set values when the RST_CONFIG_INIT_PROHIBIT environment variable has been set.

M DISPLAY-RSET:ROUTESET=ALL; command completed

Display Route Set:

RSet Name = RSET3, DPC = 3003, CPC Count of LSSN = 0 State = ACTIVE, Status = Rbc, Load Sharing = YES

RouteName Priority Status LSET11 1 aRlr LSET2 2 aPlr

--Route Set Status Legend-- a - DPC accessible A - DPC not accessible R - DPC restricted

P - DPC prohibited b - route set not blocked B - route set blocked c - route set not congested C - route set congested --Route Status Legend-- a - link set available A - link set not available x - transfer allowed R - transfer restricted

P - transfer prohibited l - link set not congested L - link set congested r - route not congested R - route congested



Figure 4-10. Alternate Sample DISPLAY-RSET Command Output for CCITT

The sample output of the DISPLAY-RSET for the ANSI network variant shown in Figure 4-11 displays the values configured for all route sets.


Display Route Set:

RSet Name = RSET1, DPC = 3003, CPC Count of LSSN = 0 State = ACTIVE, Status = Abc, Load Sharing = YES

RouteName Priority Status LSET1 1 AXlr LSET2 2 AXlr





--Route Set Status Legend-- a - DPC accessible A - DPC not accessible b - route set not blocked B - route set blocked c - route set not congested C - route set congested --Route Status Legend-- a - link set available A - link set not available x - transfer allowed X - transfer not allowed l - link set not congested L - link set congested r - route not congested R - route congested



Figure 4-11. Sample DISPLAY-RSET Command Output for ANSI

N O T E S1. The load sharing status appears on the screen for the

CCITT, China, TTC, and NTT network variants, which support load sharing.

2. In the CCITT, China, TTC, and NTT network variants, the statuses R (transfer restricted) and P


Display Route Set:

RSet Name = RSET1, DPC = 229-150-000, Routing Method = MEMBER State = ACTIVE, Status = abc0, STP = YES

RouteName Status CLSET11 axl0r0

RSet Name = RSET2, DPC = 229-151-000, Routing Method = MEMBER State = ACTIVE, Status = abc0, STP = YES


RSet Name = RSET3, DPC = 229-155-023, Routing Method = MEMBER State = ACTIVE, Status = abc0, STP = NO


--Route Set Status Legend-- a - DPC accessible A - DPC not accessible R - DPC restricted

P - DPC prohibited b - route set not blocked B - route set blocked c0 - route set not congested Cx - route set congested level x --Route Status Legend-- a - link set available A - link set not available x - transfer allowed R - transfer restricted

P - transfer prohibited

l0 - link set not congested Lx - link set congested level x r0 - route not congested Rx - route congested level x



(transfer prohibited) are displayed only if the environment variable MTP_WHITE_BOOK_TFR has been defined on the node.

3. The routing method for the route set appears on the screen for the ANSI and China variants. See Chapter 3 for a description of routing methods.

4. The STP field is displayed only in the ANSI network variant. If the route set connects to an STP, STP=YES appears. If the route set connects to a switch, STP=NO appears.

5. The route set and link set statuses displayed vary and depend on the network variant configured on the node.

6. The China network variant does not display the CPC Count of LSSN field. To view the CPCs associated with LSSNs, you must issue the following sy command:

#STA,cpc

Displaying Own Point Code InformationThe Display Own Point Code (DISPLAY-OSP) command displays and prints the Own Signaling Point (OSP) code information for a node.

Menu Selection ModeSelect the Display Own Point Code option from the Display Commands menu. The DISPLAY-OSP screen displays the command. Press RETURN to enter the command.

MML Command FormatThe MML command format for the DISPLAY-OSP command is:

DISPLAY-OSP: PRINT=print ;

The print argument specifies whether the response should be printed, as well as displayed at the terminal. Specify YES for printing to the default printer, NO for no printing, or the printer ID for printing to a specific printer.

Man Page FormatThe alternative format and man page format for DISPLAY-OSP is displ-osp.

Sample DisplayThe sample output of the DISPLAY-OSP command shown in Figure 4-12 displays the own point code configuration for the network, INAT00.



Figure 4-12. Sample DISPLAY-OSP Command Output

Displaying Concerned Point CodesThe Display Concerned Point Code (DISPLAY-CPC) command displays and prints the concerned point codes (CPCs) of a local subsystem number (SSN). This command also displays the CPC with the replicate system (duplicated remote point code), if applicable.

Menu Selection ModeSelect the Display Concerned Point Code option from the Display Commands menu. The DISPLAY-CPC screen appears. Respond to the system prompts to enter the name of the point code you want to display, or press RETURN to display all configured CPCs.

MML Command FormatThe MML command format for the DISPLAY-CPC command is:

DISPLAY-CPC:SSN=ssn, PRINT=print , FILE=file ;

Table 4-5 describes the arguments for the DISPLAY-CPC command.

M DISPLAY-OSP:;command completed

Display Own Point Code:

Network = INAT00, Own SPC = 2730



Man Page FormatThe alternative format and man page format for DISPLAY-CPC is displ-cpc.

Sample DisplayThe sample output of the DISPLAY-CPC command shown in Figure 4-13 displays all CPC information configured for all local subsystems. User entries are in bold type.

Table 4-5. DISPLAY-CPC Command Arguments


ssn Specifies the local subsystem number to display. To display all local subsystems, set the value of ssn to ALL.





Figure 4-13. Sample DISPLAY-CPC Command Output

Displaying Fictitious Originating Point Code InformationThe Display Fictitious Originating Point Code (DISPLAY-FOPC) command is only available on a node configured with an ANSI network variant. This command displays and prints the FOPC currently configured. It returns an error message if the environment variable, ANSI_SINAP_FOPC, is not defined (see ‘‘Creating a Fictitious Originating Point Code’’ in Chapter 3).

N O T EOnly one FOPC can exist at any one time on a node.

Menu Selection ModeFrom the Display Commands menu, select the Display Fictitious Originating Point Code option to access the DISPLAY-COMMANDS screen. Respond to the system prompts to select the FOPC to view.

MML Command FormatThe MML command format for the DISPLAY-FOPC command is:

DISPLAY-FOPC;

M DISPLAY-CPC:SSN=ALL;command completed

Display concerned point code:

Local SSN = 224Duplicated RPC = NILConcerned RPCs:3003

Local SSN = 253Duplicated RPC = 3003Concerned RPCs:3003

Local SSN = 254Duplicated RPC = NILConcerned RPCs:3003



This command has no arguments.

Man Page FormatThe alternative format and man page format for DISPLAY-FOPC is displ-fopc.

Displaying Remote SSNs for a Remote Point CodeThe Display Remote SSN (DISPLAY-REMSSN) command displays and prints the remote subsystem numbers (SSNs) associated with a point code.

Menu Selection ModeSelect Display Remote SSN from the Display Commands menu. The DISPLAY-REMSSN screen appears. Respond to the system prompts and enter the name of a specific remote point code, or press RETURN to display all of them.

MML Command FormatThe MML command format for the DISPLAY-REMSSN command is:

DISPLAY-REMSSN:PC=pc, PRINT=print , FILE=file ;

Table 4-6 describes the arguments for the DISPLAY-REMSSN command.

Man Page FormatThe alternative format and man page format for DISPLAY-REMSSN is displ-remssn.

Sample DisplayThe sample output of the DISPLAY-REMSSN command shown in Figure 4-14 displays the remote SSNs configured for, and associated with, the point code, 3003. User entries are in bold type.

Table 4-6. DISPLAY-REMSSN Command Arguments


pc Specifies the remote point code to display. Use the value ALL to display all the point codes.





Figure 4-14. Sample DISPLAY-REMSSN Command Output

Displaying the MTP and SCCP System Tables The Display System Tables (DISPLAY-SYSTAB) command displays and prints the values of timers and thresholds in the Message Transfer Part (MTP), Signaling Connection Control Part (SCCP), and signaling link or route test system tables for your network variant. For more information about timers and thresholds, see the appendixes for each variant and the sections describing the SINAP/SS7 features.

You can display the following timers and thresholds:

• MTP L2 timers

• MTP L3 timers (including MTP restart, time controlled changover (TCCO), and time controlled diversion (TCD))

• MTP thresholds

• SCCP timers (includes the Extended Unitdata (XUDT) SCTX freeze timer and the SCTY message reassembly timer for CCITT and China network variants)

• SCCP Integrated Services Digital Network User Part (ISUP) timers (for CCITT and ANSI network variants only)

• SCCP connection-oriented control (SCOC) timers

• Signaling link test (SLT) timers (for CCITT, ANSI, and China network variants only)

• Signaling route test (SRT) timers (for TTC and NTT network variants only)

Menu Selection ModeSelect the Display System Tables option from the Display Commands menu. The DISPLAY-SYSTAB screen appears. Respond to the system prompts and enter the type of system table you want to display.

DISPLAY-REMSSN:PC=ALL;command completed

Display Remote SSN:

Point Code = 3003Remote SSNs: 251 253 254



MML Command FormatThe MML command formats for the DISPLAY-SYSTAB commands are:

DISPLAY-SYSTAB:TABID=tabid,TIMER=timer, PRINT=print , FILE=file ; DISPLAY-SYSTAB:TABID=tabid,THRESHOLD=threshold, PRINT=print ,FILE=file ;

Table 4-7 describes the arguments for the DISPLAY-SYSTAB command.

Man Page FormatThe alternative format and man page format for DISPLAY-SYSTAB is displ-systab.

Table 4-7. DISPLAY-SYSTAB Command Arguments


tabid Specifies one of the following timer types to display:

L2TM—for level-2 MTP timersL3TM—for level-3 MTP timersMTPTH—for MTP thresholdsSCCPTM—for SCCP timersISUPTM—for ISUP timers (CCITT and ANSI only)SCOCTM—SCCP SCOC timersSLTTM—for SLT timers (CCITT, ANSI, and China only)SRTTM—for SRT timers (TTC and NTT only)

timer Specifies the timer to display. To specify a timer, use its label, or use the value, ALL, to display all timers. For possible timer labels, see the appropriate appendix for the SINAP/SS7 variant installed on your system.

threshold Specifies the threshold to display. To specify a threshold, use its label, or use the value, ALL, to display all thresholds. For possible threshold labels, see the appropriate appendix for the SINAP/SS7 variant installed on your system.





Sample DisplaysThis section contains a sample of each kind of timer and threshold you can display.

Figure 4-15 shows sample system output that illustrates links running at 64 Kbps. It is the sample output of DISPLAY-SYSTAB:TABID=L2TM,TIMER=ALL. This command displays all level-2 MTP timers. Notice that the last timer, L2T4E, represents a level-2 MTP emergency proving period.

Figure 4-15. Sample Output: Level-2 MTP Timers

Figure 4-16 shows sample output for DISPLAY-SYSTAB:TABID=L3TM,TIMER=ALL. This command displays all level-3 MTP timers. Notice that the last timer, RECONABT, is a remote congestion abatement timer.

Display L2 Timer:

L2 Timer Value in msL2T1 40000L2T2 100000L2T3 1000L2T4N 8500L2T5 80L2T6 4500L2T7 1300L2T4E 500



Figure 4-16. Sample Output: Level-3 MTP Timers

Figure 4-17 shows sample output of DISPLAY-SYSTAB:TABID=MTPTH, THRESHOLD=ALL. This command displays all MTP thresholds. The sample is from a stack configured with a CCITT network variant and with the International one congestion onset and one congestion abatement option.

Figure 4-17. Sample Output: MTP Thresholds

Display L3 Timer: L3 Timer Value in ms L3T1 500 L3T2 2000 L3T3 500 L3T4 500 L3T5 500 L3T6 500 L3T8 1000 L3T10 30000 L3T12 800 L3T13 800 L3T14 2500 L3T15 2000 L3T16 2000 L3T17 800 L3T19 67000 L3T20 59000 L3T21 63000 L3T22 180000 L3T23 180000 RECONABT 1400

Display MTP Threshold:

MTP Threshold ValueCONON1 80CONAB1 50



Figure 4-18 shows sample output of DISPLAY-SYSTAB:TABID=SCCPTM, TIMER=ALL. This command displays all SCCP timers, except SCCP connection-oriented (SCOC) timers. SCOC timers display using the TABID=SCOCTM command shown in Figure 4-20.

Figure 4-18. Sample Output: SCCP Timers

N O T E S1. For Level-2 MTP, Level-3 MTP, SCCP timer settings, and

MTP thresholds, see ‘‘Changing Timers and Link Congestion Threshold Settings.” Note that these values are the same for all links on the local system, regardless of baud rate.

2. The current software release of the SINAP/SS7 system automatically provides the XUDT freeze timer value and does not implement any changes you make using the CHANGE-SYSTAB command.

Display SCCP Timer:

SCCP Time Value in msSCT1 30000SCT2 40000SCT3 10000SCTX 60000SCTY 1000



If ISUP is used, Figure 4-19 provides a sample output of DISPLAY-SYSTAB:TABID= ISUPTM,TIMER=ALL. This command displays all the ISUP timers. For additional information on ISUP, see the SINAP/SS7 ISDN User Part (ISUP) Guide (R8053).

Figure 4-19. Sample Output: ISUP Timers

Display ISUP Timer: ISUP Timer Value in sec IST1 30 IST2 180 IST4 480 IST5 480 IST6 10 IST7 25 IST8 12 IST9 10 IST12 35 IST13 480 IST14 35 IST15 480 IST18 35 IST19 480 IST20 35 IST21 480 IST22 35 IST23 480 ISTCCR 120 IST27 240



To display the SCCP connection-oriented (SCOC) timers, use the command, DISPLAY-SYSTAB:TABID=SCOCTM,TIMER=ALL. Figure 4-20 shows the display of the SCOC timers.

Figure 4-20. Sample Output: SCCP SCOC Timers

Figure 4-21 shows sample output of DISPLAY-SYSTAB:TABID=SLTTM,TIMER=ALL. This command displays the SLT timers.

Figure 4-21. Sample Output: SLT Timers

Figure 4-22 shows sample output of DISPLAY-SYSTAB:TABID=SRTTM,TIMER=ALL. This command displays the SRT timers used for the TTC and NTT network variants only.

Figure 4-22. Sample Output: SRT Timers

Display SCOC Timer:

SCOC Time Value in secSTias 90STiar 270STguard 720STconest 15STreset 15STrel 15STrelint 60STrelrep 20

Display SLT Timer:

SLT Time Value in secSLTT1 8SLTT2 60

Display SRT Timer:

SRT Time Value in secSRTT10 10SRTT20 60



Displaying Global Titles for a Node The Display Global Titles (DISPLAY-GTT) command displays all global title entries configured for your SINAP/SS7 node. Each global title entry specifies how SCCP routing control should translate an incoming or outgoing title into a replacement DPC, SSN, and/or global title.

The CCITT network variant can be configured with an alternate or “backup” SSN and/or DPC to use when the initially specified (primary) SSN or DPC is unavailable. See ‘‘Creating a Global Title Translation (GTT) Entry for a Node’’ in Chapter 3 for more information on this feature. These entries, if specified in the CREATE-GTT process, will display when you issue the DISPLAY-GTT command. You do not need to set an environment variable to simply display the GTT entries, including SSN2 and DPC2.

N O T EValues for the LADDR, HADDR, and NADDR global title address components can be displayed in either decimal or hexadecimal character formats. If the HEX_GLOBAL_TITLE environment is not set, then decimal is the default character format. If the variable is set, then hexadecimal is the active character format. Refer to the section “Using Hexadecimal Values in GTT Strings” in Chapter 3 for more information.

Menu Selection ModeSelect the Display GTT option from the Display Commands menu. The DISPLAY-GTT screen appears. Press RETURN to access the MML Send Menu, and display a list of global titles.

N O T EThere is no option to print global titles information.

MML Command FormatThe DISPLAY-GTT command has no arguments.

Man Page FormatThe alternative format and man page format for DISPLAY-GTT is displ-gtt.



Sample DisplayThe sample output of the DISPLAY-GTT command shown in Figure 4-23 displays global-title entries for a sample CCITT configuration.

Figure 4-23. Sample DISPLAY-GTT Command Output

N O T EBecause the sample display is for the CCITT network variant, the line containing 253 and 2731 represents the backup SSN and DPC for this GTT. If the backup SSN and/or DP are not specified, they do not display. The other variants do not display the backup or alternate items.

DISPLAY-GTTcommand completed Global Title Translation Entries:

GTI TT NP NOAI Global Title(Low/High/New) SSN DPC

4 87 2 500000 254 2730 999999 253 2731

Hit (Q orq) to quit displaying response



You can display GTT entries from sy also. The sample shown in Figure 4-24 is the output of the #STA,gtt command. (If dpc2 or ssn2 have not been specified, they will not display.)

Figure 4-24. Sample #STA,gtt Command Output

Displaying Signaling Link Selection Assignments for an Application You can display information about an application’s load distribution type, such as round-robin, least-utilized, or signaling link assignments (SLS) distribution, by issuing the #SLD command through the SINAP/SS7 utility (sy).

Perform the following steps to display SLS assignments for an application using the sy utility.

1. Start the sy utility by entering the following command from the UNIX command line of a SINAP/SS7 login window (that is, any window through which you have logged in as the user, sinap):

sy

2. Enter the sy #SLD command to display SLS assignments for an application using one of the following command formats:

#SLD,SIO,sio_number#SLD,SSN,ssn_number#SLD,APPL,appl_name

Enter cmd>#STA,gttGlobal Title Translation Entries:

*********translation entry**********next: 0x00000000prev: 0x00000000state: 3gti: 4tt; 8es: 2np: 7noai 2laddr:50000haddr:999999pci: 1 pc: 2730 (0x0aaa) dpc2: 2731 (0x0aab)ssni:2 ssn: 254 ssn2: 253naddr: <NONE>



Table 4-8 describes these command formats using examples for an application that uses SLS load distribution. However, you can also issue these commands to display the load-distribution information for an application that uses round-robin or least-utilized load distribution. Note that the pound sign (#) is part of the #SLD command.

Table 4-8. SLD Command Formats (Page 1 of 2)


#SLD,SIO,sio_number Display the SLS assignments for an application registered with a service information octet (SIO) (where sio_number is the SIO number). For example, the following command specifies an application that registered with an SIO of 5:

#SLD,SIO,5

The command output indicates that the application has two instances with SLS assignments as follows: application instance 2 is assigned SLS codes 0 through 7, and instance 1 is assigned SLS codes 8 through 15.

SIO 5: instance count = 2

SLS Distribution = 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1

#SLD,SSN,ssn_number To display the SLS assignments for an application registered with a subsystem number (SSN) (where ssn_number is the SSN of the application). For example, the following command specifies an application registered with an SSN of 254:

#SLD,SSN,254 The command output indicates that the application has five instances with SLS assignments as follows: application instance 5 is assigned SLS codes 0, 1, and 4; instance 4 is assigned SLS codes 3, 10, and 11; instance 3 is assigned SLS codes 2, 8, and 9; instance 2 is assigned SLS codes 5, 6, and 7; and instance 1 is assigned SLS codes 12, 13, 14, and 15.

SSN 254: instance count = 5




In the sample command outputs in Table 4-8, the first line of the #SLD command output identifies the application and the number of active application instances. The second line (SLS Distribution) displays the SLS code assigned to each of the application’s instances. Each position in this line corresponds to an SLS code (0 through 15). The number of the application instance assigned this SLS code appears in this position. For example, an SLS distribution of 5, 5, 4, 3... indicates that application instance 5 is assigned SLS codes 0 and 1, application instance 4 is assigned SLS code 2, application instance 3 is assigned SLS code 3, and so on.

Displaying Local Subsystem Numbers (SSNs) StatusThe Display SSN (DISPLAY-SUBSYSTEM) command displays and prints the provisioned subsystem numbers and the current status of a subsystem in relation to the SCCP.

Menu Selection ModeSelect the Display SSN option on the Application Commands menu to access the DISPLAY-SUBSYSTEM command. Respond to the system prompts and enter the value of the SSN to display, or press RETURN to display all SSNs.

#SLD,APPL,appl_name Display the SLS assignments for an application registered using its name instead of its SSN (where appl_name is the name of the application). Use this format for applications that implement enhanced message distribution (for example, if an application is one of several applications that use the same SSN). For example, the following command specifies a load control application named DB12.

#SLD,APPL,DB12

The command output indicates that the application has three instances with SLS assignments as follows: application instance 3 is assigned SLS codes 0, 1, 2, 8, and 9; instance 2 is assigned SLS codes 5, 6, 7, 10, and 11; and instance 1 is assigned SLS codes 3, 4, 12, 13, 14, and 15.

APPL DB12: instance count = 3


Table 4-8. SLD Command Formats (Page 2 of 2)




MML Command FormatThe MML command format for the DISPLAY-SUBSYSTEM command is:

DISPLAY-SUBSYSTEM:SSN=ssn, PRINT=print , FILE=file ;

Table 4-9 describes the arguments for the DISPLAY-SYSTAB command.

Man Page FormatThe alternative format man page format for DISPLAY-SUBSYSTEM is displ-subsystem.

Sample DisplayThe sample output of the DISPLAY-SUBSYSTEM command shown in Figure 4-25 displays the SSN numbers for all configured SSNs. User entries are in bold type.

Figure 4-25. Sample DISPLAY-SUBSYSTEM Command Output

Table 4-9. DISPLAY-SUBSYSTEM Command Arguments


ssn Defines the SSN of the subsystem to be displayed as a decimal number between 1 and 255. Specify the value ALL to display all subsystems.


M DISPLAY-SUBSYSTEM:SSN=ALL;command completed

Display local subsystem:local ssn=41 state=ALLOWEDlocal ssn=42 state=ALLOWEDlocal ssn=43 state=ALLOWEDlocal ssn=44 state=ALLOWED


Changing Network Components

Changing Network ComponentsThis section describes how to change the configuration of network components through the Change Commands menu, which is accessed on the Network Commands menu. Each network variant offers slightly different menu options.

The Change Commands menu offers the choices shown in Figure 4-26 for the CCITT and China network variants.

Figure 4-26. Change Commands Menu for the CCITT/China Variants

The ANSI network variant contains the additional options to change combined link sets and to change Fictitious Originating Point Codes (FOPC). These options are described in this chapter. The Change Commands menu for the ANSI network variant is shown in Figure 4-27.

Figure 4-27. Change Commands Menu for the ANSI Variant

Change Commands:1. Change Link2. Change Linkset3. Change Routeset4. Change Concerned Point Code5. Change Duplicate Point Code6. Change Remote SSN7. Change System Table8. Change Global Title

<CHANGE>

Change Commands:1. Change Link2. Change Linkset3. Change Routeset4. Change Concerned Point Code5. Change Duplicate Point Code6. Change Remote SSN7. Change System Table8. Change Global Titles9. Change SLS Type

<CHANGE>



N O T EThere is no option available on the CCITT variant menu to change the OSP. To make a change to OSP, it could be done by either delete all network elements from the network (including DELETE-OSP) followed by CREATE-OSP with a new OSP, or just CREATE-OSP without deleting any network elements if the OSP_UPDATE_ENABLED environment variable is defined when SINAP node is started.

N O T EThere are no options available on the ANSI variant menu to change either the combined link set or the fictitious originating point code. To make a change to either one, you must first delete the one you want to change (DELETE-CLSET or DELETE-FOPC) and then create a new one to replace it (CREATE-CLSET or CREATE-FOPC).

The TTC and NTT network variants do not support duplicate point codes, combined link sets, or fictitious originating point codes. Figure 4-28 shows the Change Commands menu for the TTC and NTT network variants.

Figure 4-28. Change Commands Menu for the TTC and NTT Variants

The following subsections describe the change tasks, in the order listed on the ANSI network variant Change Commands menu.

Changing a LinkThe Change Link (CHANGE-LINK) command sets or resets the periodic signaling link test (SLT) mode for an existing point code.

Change Commands 1. Change Link 2. Change Linkset 3. Change Routeset4. Change Own Point Code5. Change Concerned Point Code6. Change Remote SSN7. Change Global Titles

< CHANGE >



For the TTC and NTT network variants, the command sets or resets the signaling route test (SRT) which corresponds to the signaling link test (SLT) in the CCITT, China, and ANSI network variants.

Menu Selection ModeSelect the Change Link option on the Change Commands menu to set or reset the SLT (or SRT) for a point code. The CHANGE-LINK screen appears. Respond to the system prompts and specify the name of the configured point code that you are setting or resetting, or ALL to change all.

MML Command FormatThe MML command format for the CHANGE-LINK command is:

CHANGE-LINK:LINK=link,PERIODIC_SLT= slt;

For the TTC and NTT network variants, use the command format:

CHANGE-LINK:LINK=link,PERIODIC_SLT=srt;

Table 4-10 describes the arguments in the CHANGE-LINK command.

Man Page FormatThe alternative format and man page format for CHANGE-LINK is chg-link.

Changing a Link Set The Change Linkset (CHANGE-LSET) command sets or resets a link set to or from the emergency mode. In emergency mode, a link set displays an emergency alignment flag.

N O T EThis command does not apply to the TTC and NTT network variants because it implements link alignment in a different way. See Appendixes F and G for more information.

Table 4-10. CHANGE-LINK Command Arguments


link Specifies the link name of the link to be changed.

slt (srt) Specify YES to set the link to periodic SLT (SRT) mode. Specify NO to deselect periodic SLT (SRT) mode.



Menu Selection ModeSelect the Change Linkset option from the Change Commands menu. The CHANGE-LSET screen appears. Respond to the system prompts to set or reset a link set’s emergency mode flag setting.

MML Command FormatThe MML command format for the CHANGE-LSET command is:

CHANGE-LSET:LINKSET=linkset,EMERGENCY=emergency;

Table 4-11 describes the arguments for the CHANGE-LSET command.

Man Page FormatThe alternative format and man page format for CHANGE-LSET is chg-lset.

Changing the Route SetThe Change Routeset (CHANGE-RSET) command changes the content of a route set. You can add, delete, or exchange the priority of a route. You can also enable or disable load sharing between two routes.

N O T EWhen you specify the CHANGE-RSET command with the DELROUTE argument, only the route (link set) is removed from the route set. The link set remains provisioned to the node. The SINAP/SS7 system does not allow you to delete a route if doing so makes a destination point code (DPC) unreachable.

If you remove a route from a route set that is carrying traffic, the SINAP/SS7 system reroutes that traffic to the new current route using controlled rerouting. If you add a route to a route set with a higher priority than the current route, the SINAP/SS7 system reroutes the traffic to the newly added current route.

Table 4-11. CHANGE-LSET Command Arguments


linkset Specifies the link set to be changed. To specify the link set, use the label you assigned to it when creating it.

emergency Specifies whether the emergency flag should be set or reset. Possible values are YES to set the emergency flag, or NO to reset the emergency flag.Note: The emergency alignment flag overrides the normal provisioning of a link. Thus, a link is ready for alignment so that traffic can start immediately.



Menu Selection ModeSelect the Change Routeset option from the Change Commands menu. The CHANGE-RSET screen appears. Respond to the system prompts to specify the route set name and the type of operation you are performing on it, such as adding, deleting, or exchanging a route set, or enabling/disabling load sharing functionality.

MML Command Format The MML command formats for the CHANGE-RSET command operations are:

To add a route set:

CHANGE-RSET:ROUTESET=routeset,ADDROUTE=route,PRIORITY= priority;

To delete a route set:

CHANGE-RSET:ROUTESET=routeset,DELROUTE=route; To exchange a route set:

CHANGE-RSET:ROUTESET=routeset,XROUTE1=route,XROUTE2=route; To enable or disable load sharing:

CHANGE-RSET:ROUTESET=routeset,LOADSHR=loadshr;

N O T E S1. The LOADSHR argument applies to the CCITT, China,

NTT, and TTC variants. The ANSI network variant does not support load sharing for route sets.

2. Because the ANSI network variant supports combined link sets, you can exchange a combined link set in any of the following conditions:

• Exchange a single route with a combined link set.

• Exchange a combined link set with another combined link set.

• Exchange a combined link set (which has a direct link set) with a normal combined link set.



Table 4-12 describes the arguments for the CHANGE-RSET command.

Man Page FormatThe alternative format and man page format for CHANGE-RSET is chg-rset.

Changing a Concerned Point Code The Change Concerned Point Code (CHANGE-CPC) command updates the list of concerned point codes (CPCs) (remote point codes that are concerned with the availability of a local SSN) by adding or deleting them for a specific local SSN.

Menu Selection ModeSelect the Change Concerned Point Code option from the Change Command menu. The CHANGE-CPC screen appears. Respond to the system prompts to add or delete a point code for a specific SSN.

Table 4-12. CHANGE-RSET Command Arguments


routeset Specifies the route set to which changes apply. To specify the route set, use the label you assigned to it when creating it.

route Specifies the route to be added with ADDROUTE, deleted with DELROUTE, or exchanged with XROUTE1 and XROUTE2. Specify a route using the label you assigned to the link set when creating it.

For ANSI and China variants of the SINAP/SS7 system, if the route being added uses a type F link set, specify the link set label; for type A or type E link sets, specify the combined link set label.

priority Specifies the priority of the new or modified route. The value of priority is a decimal value between 1 and 8 where 1 is the highest priority route. If the value of priority is more than 1 higher than the highest numerical priority currently in the route set, then the route’s priority is reduced to 1 plus the highest numerical value. This argument is only valid when you are adding a route.

loadshr Specifies whether load sharing between two routes is enabled or disabled. Possible values are ENABLE or DISABLE. This parameter applies only to the CCITT, China, NTT, and TTC variants of the SINAP/SS7 system.



MML Command FormatThe MML command formats for the CHANGE-CPC command add and delete operations are:

CHANGE-CPC:LSSN=ssn,ADDRPC=pc;CHANGE-CPC:LSSN=ssn,DELRPC=pc;

Table 4-13 describes the arguments for the CHANGE-CPC command.

Man Page FormatThe alternative format and man page format for CHANGE-CPC is chg-cpc.

Changing the Duplicate Concerned Point Code NumberThe Change Duplicate Concerned Point Code (CHANGE-DUCPC) command changes the point code of the replicate for a specific local SSN. The new point code must already exist in the CPC table. The SINAP/SS7 system retains the point code of the previous replicate in the CPC table, but does not retain its status as a replicate.

To delete the point code of the previous replicate, use the CHANGE-CPC command after issuing the CHANGE-DUCPC command.

N O T EThe TTC network variant does not support duplicate point codes (DUCPCs) and, therefore, does not support the CHANGE_DUCPC command.

Menu Selection ModeSelect the Change Duplicate Point Code option from the Change Commands menu. The CHANGE-DUCPC screen appears. Respond to the system prompts to change the duplicate point code for a specific local SSN.

Table 4-13. CHANGE-CPC Command Arguments


ssn Specifies the SSN of the local subsystem.

pc Specifies the point code to be added with ADDRPC or deleted with DELRPC. You can create a list of up to 512 point codes, separated by ampersands (&).




CHANGE-DUCPC:LSSN=ssn,NEWRPC=pc;

Table 4-14 describes the arguments for the CHANGE-DUCPC command.

Man Page FormatThe alternative format and man page format for CHANGE-DUCPC is chg-ducpc.

Adding and Deleting a Remote Subsystem for a Point CodeThe Change Remote SSN (CHANGE-REMSSN) command adds or deletes remote subsystems for a specific point code. Before it is accessible, a remote subsystem must be defined to a node.

Menu Selection ModeSelect the Change Remote SSN option from the Change Commands menu. The CHANGE-REMSSN screen appears. Respond to the system prompts to add or delete an SSN to a specific point code. You must specify the point code of the remote node to which to add or delete an SSN. The point code must be in the required format for your system’s network variant. Refer to the appropriate appendix for your network variant for more information on point code formats.

MML Command FormatThe MML command format for the CHANGE-REMSSN command is:

CHANGE-REMSSN:PC=pc,ADDSSN=ssn;CHANGE-REMSSN:PC=pc,DELSSN=ssn;

Table 4-14. CHANGE-DUCPC Command Arguments


ssn Specifies the SSN of the local subsystem.

pc Specifies the new replicate point code. You can specify only one point code. Use the point code format appropriate for the version of the SINAP/SS7 system installed on your system. See the specific appendix for your network variant for more information on specific point code formats.



Table 4-15 describes the arguments for the CHANGE-REMSSN command.

Man Page FormatThe alternative format and man page format for CHANGE-REMSSN is chg-remssn.

Changing Timers and Link Congestion Threshold SettingsThe Change System Table (CHANGE-SYSTAB) command changes the values of timers and thresholds in the system tables. You can change the settings for the following types of timers and thresholds:

• MTP Level 2 timers

• MTP Level 3 timers (includes MTP restart, TCCO, and TCD)

• MTP thresholds

• SCCP timers (includes SCTX freeze timer and SCTY message reassembly timers for the CCITT and China network variants)

• ISUP timers (CCITT and ANSI only)

• SCCP SCOC timers

• SLT timers (CCITT, ANSI, and China only)

• SRT timers (TTC and NTT only)

Menu Selection ModeSelect the Change System Table option on the Change Commands menu to change timer and/or threshold values in the system tables. You must specify the type of timer or threshold you are changing.

MML Command FormatThe MML command formats for the CHANGE-SYSTAB command are as follows:

CHANGE-SYSTAB:TABID=tabid,TIMER=timer,NEWTIME=time;

Table 4-15. CHANGE-REMSSN Command Arguments


pc Specifies the point code of the remote node. Use the point code format that is appropriate for the version of the SINAP/SS7 system installed on your system. See the appendixes for more information on the point code formats used in the CCITT, ANSI, TTC, and China variants of the SINAP/SS7 system.

ssn Specifies the SSN to be added with ADDSSN or deleted with DELSSN. You can create a list of up to 10 SSNs separated by ampersands (&).



CHANGE-SYSTAB:TABID=tabid,THRESHOLD=threshold,NEWLEVEL=level;

Table 4-16 describes the arguments for the CHANGE-SYSTAB command.

C A U T I O NThe value of a congestion-abatement threshold should be less than its corresponding congestion-onset threshold. Otherwise, unpredictable behavior might result. For example, if you specify a value of 30 for CONON1, the value of CONAB1 should be less than 30.

Table 4-16. CHANGE-SYSTAB Command Arguments


tabid Specifies the system table being changed. Possible choices are:

• L2TM—for Level-2 MTP timers

• L3TM—for Level-3 MTP timers

• MTPTH—for MTP thresholds

• SCCPTM—for SCCP timers

• ISUPTM—for ISUP timers (CCITT and ANSI only)

• SCOCTM—SCCP SCOC timers

• SLTTM—for SLT timers (CCITT, ANSI, and China only)

• SRTTM—for SRT timers (TTC and NTT only)

timer Specifies the timer being changed. Specify a timer using a label of up to eight characters. See the appropriate appendix for the timer settings for the variant of the SINAP/SS7 system installed at your site.

time Specifies a decimal value for the time, followed by one or two characters to indicate the units. For example, to specify 1500 milliseconds, use the notation 1500ms; to specify 2 minutes and 30 seconds, use the notation 150s; to specify 2 minutes, use the notation 2m.

threshold Specifies the threshold being changed. Use a label to specify thresholds. See the appropriate appendix for the threshold settings for the variant of the SINAP/SS7 system installed at your site.

level Specifies the number of units, in decimals, being applied to the threshold. Allowed values are in the range 0 through 4096.



The following example shows a sample command for changing the value of the STRELINT timer, an SCCP connection-oriented timer:

CHANGE-SYSTAB:TABID=SCOCTM,TIMER=STrelint,NEWTIME=40S;

Man Page FormatThe alternative format and man page format for CHANGE-SYSTAB is chg-systab.

Changing the GTT Entries for a NodeThe Change Global Title (CHANGE-GTT) command changes the value of a specific global title entry.

Menu Selection ModeSelect Change Global Titles on the Change Commands menu to change a global title value.

MML Command FormatFor the China, TTC, NTT, and ANSI network variant, the MML command format for the CHANGE-GTT command is as follows:

CHANGE-GTT:OLD_GTI=gti,OLD_TT=np,OLD_NOAI=noai,OLD_LADDR=laddr,GTI=gti,TT=tt,NP=np,NOAI=noai,LADDR=laddr [,HADDR=haddr] {,DPC=dpc|,SSN=ssn|,NADDR=naddr};

N O T EValues for the LADDR, HADDR, and NADDR global title address components can be entered in either decimal (0 - 9) or hexadecimal (0 - 9 and A - F) character formats. If the HEX_GLOBAL_TITLE environment is not set, then decimal is the default character format. If the variable is set, then hexadecimal is the active character format. See ‘‘Creating a Global Title Translation (GTT) Entry for a Node’’ in Chapter 3 for more information.

For the global title translation to be valid (that is, for SCCP to have addressing information with which to replace the original global title) you must include at least one of the following three arguments in the CHANGE-GTT command line: dpc, ssn, or naddr.

For the CCITT variant only, you can optionally provide backup or alternate SCCP routing for GTT by including the dpc2 or ssn2 arguments. If the global title requires translation at a remote node and the primary SCCP is unavailable, the SINAP/SS7 system diverts the relevant MSUs to the “secondary” SCCP. If neither SCCP is available, the SINAP/SS7 system returns a NOTICE indication.



N O T E S1. To make the backup feature work, a DPC must be specified

to use DPC2 and an SSN must be specified to use SSN2. The dpc2 and ssn2 arguments have the same validation criteria as DPC and SSN.

2. For this feature to work, remote systems must keep the SINAP/SS7 system informed about their status in existing messages, such as SSA and SSP.

3. If the remote subsystem status is immaterial for RouteOnGT translations (where the local GTT results in a new global title that must be translated at a remote SCCP), the environment variable GLOBAL_TITLE_SSN_NO_CHECK must be set.

For the CCITT network variant, the MML command format for the CHANGE-GTT command is as follows:

CHANGE-GTT:OLD_GTI=gti,OLD_TT=np,OLD_NOAI=noai,OLD_LADDR=laddr,GTI=gti,TT=tt,NP=np,NOAI=noai,LADDR=laddr [,HADDR=haddr]{,DPC=dpc|,SSN=ssn|,NADDR=naddr}{DPC2=dpc2} {SSN2=ssn2};



Table 4-17 describes the argument for the CHANGE-GTT command.

Table 4-17. CHANGE-GTT Command Arguments (Page 1 of 3)


OLD_xxx Specifies the existing global title entry to be replaced.

GTI Specifies the global title indicator. The value of this argument indicates the addressing components included in the global title. The global title formats associated with each value differ slightly between network variants as indicated:

CCITT/TTC/China Global Title Formats:

GTI Value Global Title Contents0 No global title1 NOAI only2 TT only3 TT and NP4 TT, NP, and NOAI


GTI Value Global Title Contents0 No global title1 TT and NP*2 TT only* The global title formats for ANSI GTI 1 and CCITT/China/TTC/NTT GTI 3 are identical.

TT Specifies the translation type, which directs the message to the appropriate global-title-translation function. Valid values are in the range 0 through 254. For the CCITT, China, TTC, and NTT network variants, include this argument if the GTI is 2, 3, or 4. For the ANSI network variant, include this argument if the GTI is 1, 2, 3, or 4.

NP Specifies the numbering plan used for the address information in the global title (for example, ISDN/Telephony, data, or ISDN/Mobile). Include this argument if the GTI is 3 or 4 for the CCITT, China, TTC, and NTT network variants or if the GTI is 1 for the ANSI network variant. Valid values are in the range 0 through 14.



NOAI Specifies the nature-of-address indicator, which identifies the type of number used in the global title (for example, subscriber, national significant, or international). (Not used for the ANSI network variant.) Note: The default value range for this indicator is from 1 through 4. Setting the GTT_BYPASS_NOAI_CHECK environment variable expands the range from 1 through 127.

LADDR Specifies the low address (starting values) of a range of global titles. If you do not specify haddr, the global title’s address information must exactly match the laddr value in order to match the global-title entry. If you specify haddr, the laddr value specifies the low address (the start) of a range of global titles, and any global title between laddr and haddr will match this global-title entry.




HADDR Specifies the high address (the end) of a range of global titles. A match on this global-title entry occurs with any global title whose address information (including its length) matches an address in the range laddr to haddr.


The value of haddr must be greater than or equal to the value of laddr. If you specify a GTI of 2, you must define the global title’s address information as an even number of digits (for example, 155555 or 100000).





Man Page FormatThe alternative format and man page format for CHANGE-GTT is chg-gtt.

For the global title translation to be valid (that is, for SCCP to have addressing information with which to replace the original global title), you must include at least one of the following three arguments in the CHANGE-GTT command line: DPC, SSN, NADDR.

DPC Specifies the DPC to substitute for the original DPC. If you omit this argument, SCCP does not replace the DPC during translation. Format this field appropriately for the variant you are using. Valid values are 1 through 16383. See the appendix that describes your network variant.

SSN Specifies the SSN to substitute for the original SSN. If you omit this argument, SCCP does not replace the SSN during translation. Valid values are in the range of 2 to 255.

NADDR Specifies address information to substitute for any address information included in the global title.


• If you specify this argument, SCCP replaces address information in the global title and sets the routing-indicator bit of the SCCP called-party address to 0 to specify routing on global title.

• If you omit this argument, SCCP does not replace address information in the global title during translation. In addition, SCCP sets the routing-indicator bit of the SCCP called-party address to 1 to specify routing on DPC/SSN.

For the CCITT variant only, you can optionally include one or both of the following arguments to provide “backup” or alternate SCCP routing if the primary SCCP is unavailable. A DPC must be specified to use DPC2 and SSN must be specified to use SSN2.

DPC2 Specifies the destination point code (DPC) to use for this global title entry if the primary SCCP is unavailable. Valid values are 1 through 16383. An entry of NONE specifies no backup DPC.

SSN2 Specifies the SSN to use for this global-title entry if the primary SCCP is unavailable. Valid values are 2 through 255. An entry of NONE specifies no backup SSN.




Deleting Network Components

Change SLS Processing SchemeThe Change SLS Processing (CHANGE-SLSTYPE) command changes the signaling link selection (SLS) processing scheme for all incoming and outgoing traffic to either an 8-bit or 5-bit scheme (the default is 5-bit).

Menu Selection ModeSelect Change SLS Type on the Change Commands menu (for the ANSI network variant) to change the SLS processing scheme. Respond to the system prompt by entering wither 8 to specify 8-bit processing or 5 to specify 5-bit processing.

MML Command FormatFor the ANSI network variant, the MML command format for the CHANGE-SLSTYPE command is as follows:

CHANGE-SLSTYPE:TYPE=numeric_slstype;

Man Page FormatThe alternative format and man page format for CHANGE-SLSTYPE is chg-slstype.

Adding and Deleting Links DynamicallyYou can add a new SINAP/SS7 link to the system or modify an existing SINAP/SS7 link during SINAP/SS7 operation (referred to as dynamic configuration). Perform this task using the MML command line format. See the SINAP/SS7 Installation Guide (R8060).

Deleting Network ComponentsThis section describes how to delete network components. You can access the commands through the Delete Commands menu (an option of the Network Commands menu).



The Delete Commands menu for the CCITT and China network variants is shown in Figure 4-29.

Figure 4-29. Delete Commands Menu for the CCITT/China Variants

The ANSI network variant contains additional options to delete combined link sets and fictitious originating point codes (FOPC). Figure 4-30 shows the Delete Commands menu for the ANSI network variant.

Figure 4-30. Delete Commands Menu for the ANSI Variant

Delete Commands:1. Delete Link2. Delete Linkset3. Delete Routeset4. Delete Own Point Code5. Delete Concerned Point Code6. Delete Duplicate Point Code7. Delete Remote SSN8. Delete Global Title

<DELETE>

Delete Commands:1. Delete Link2. Delete Linkset3. Delete Combined Linkset4. Delete Routeset5. Delete Own Point Code6. Delete Concerned Point Code7. Delete Duplicate Point Code8. Delete Remote SSN9. Delete Fictitious Originating Point CodeA. Delete Global Title

<DELETE>



The TTC and NTT network variants do not support duplicate concerned point codes, combined link sets, or fictitious originating point codes. Figure 4-31 shows the Delete Commands menu for the TTC and NTT network variants.

Figure 4-31. Delete Commands Menu for the TTC and NTT Variants

The following subsections describe the deletion tasks in the order shown on the ANSI network variant Delete Commands menu, including instructions for deleting an own point code. See the menus in Figures 4-15 through 4-17 for the deletion tasks for each network variant.

Deleting Links DynamicallyPerform the following steps to delete a link while the SINAP/SS7 system is running. You must use both the Terminal Handler and a UNIX text editor to effect the deletion.

1. From the Terminal Handler, if applicable, issue the CONFIGURE-LSET command to deactivate the link set to which the link belongs.

2. Issue the CONFIGURE-LINK command to deactivate the link you are deleting.

3. Issue the DELETE-LINK command to remove the link from SINAP/SS7 service.

4. Exit the Terminal Handler and return to the UNIX prompt. To do this, press CTRL B to display the SINAP System Main Menu. Select option 5 to exit the Terminal Handler and return to the UNIX prompt.

5. Using a text editor, modify the /etc/SS7links file to remove the entry for the link you just deleted. Issue the following command from a UNIX prompt to download the link configuration changes onto the system.

sinap_update

The deleted link is no longer available for the SINAP/SS7 system use.

Delete Commands 1. Delete Link 2. Delete Linkset 3. Delete Routeset4. Delete Own Point Code5. Delete Concerned Point Code6. Delete Remote SSN7. Delete Global Title

< DELETE >



Deleting a Link From a Link SetThe Delete Link (DELETE-LINK) command deletes a signaling link from a link set. The link must be inactive to be deleted. If the link being removed is the last link in the link set, and a route set is still using the link set as a route, the SINAP/SS7 system does not delete the link.

Menu Selection ModeAccess the DELETE-LINK command from the Delete Commands menu.

MML Command FormatThe MML command format for the DELETE-LINK command is as follows:

DELETE-LINK:LINK=link;

The link argument of the command specifies the link to be deleted. When specifying a link, use the label you assigned to the link when creating it. This label can be up to eight characters long.

Man Page FormatThe alternative format and man page format for DELETE-LINK is dlt-link.

Deleting a Link SetThe Delete Linkset (DELETE-LSET) command deletes a link set. If the link set being deleted is still used as a route for any route set, the SINAP/SS7 system does not delete the link set. Additionally, the SINAP/SS7 system does not delete the link set if any of its member links are provisioned, and the system issues an error message.

Menu Selection ModeAccess the DELETE-LSET command from the Delete Commands menu.

MML Command FormatThe MML command format for the DELETE-LSET command is as follows.

DELETE-LSET:LINKSET=linkset;

The linkset argument of the command specifies the link set to be deleted. When specifying the link set, use the label you assigned to the link when creating it. This label can be up to eight characters long.

Man Page FormatThe alternative format and man page format for DELETE-LSET is dlt-lset.

Deleting a Combined Link SetCombined link sets apply only to stacks configured with the ANSI network variant. The CCITT, TTC, NTT, and China variants do not support combined link sets.



The Delete Combined Linkset (DELETE-CLSET) command disassociates a combined link set from its member link sets. If the combined link set being deleted is still used as a route for any route set, the SINAP/SS7 system does not delete the combined link set. Additionally, the SINAP/SS7 system does not delete the link set if any of its member links are provisioned.

Menu Selection ModeYou can access the DELETE-CLSET command from the Delete Commands menu.

MML Command FormatThe MML command format for the DELETE-CLSET command is as follows:

DELETE-CLSET:CLSET=clset;

The clset argument of the command specifies the combined link set to be deleted. When specifying the link set, use the label you assigned to the link set when creating it. This label can be up to eight characters long.

Man Page FormatThe alternative format and man page format for DELETE-CLSET is dlt-clset.

Deleting a Route SetThe Delete Routeset (DELETE-RSET) command deletes a route set. You cannot delete a route set if the destination point code still exists as a concerned point code, or as the remote subsystem.

Menu Selection ModeAccess the DELETE-RSET command from the Delete Commands menu.

MML Command FormatThe MML command format for the DELETE-RSET command is as follows:

DELETE-RSET:ROUTESET=routeset;

The routeset argument specifies the route set to be deleted. When specifying the route set, use the label you assigned to it when creating it.

Man Page FormatThe alternative format and man page format for DELETE-RSET is dlt-rset.

Deleting an Own Point CodeThe Delete Own Point Code (DELETE-OSP) command deletes the own signaling point (OSP) code for the network. Use this command only when all other network elements are deleted from the network.



N O T EThe current OSP (PC or/and NI) can be changed by just executing CREATE-OSP, if the OSP_UPDATE_ENABLED environment variable is defined when SINAP node is started, without deleting any network elements from the network (including DELETE-OSP).

Menu Selection ModeAccess the DELETE-OSP command from the Delete Commands menu.

MML Command FormatThe MML command format for the DELETE-OSP command is as follows:

DELETE-OSP;

Man Page FormatThe alternative format and man page format for DELETE-OSP is dlt-osp.

Deleting a Concerned Point Code (CPC)The Delete Concerned Point Code (DELETE-CPC) command deletes all remote point codes from a specified local subsystem. To delete an individual point code for a particular SSN, use CHANGE-CPC.

Menu Selection ModeAccess the DELETE-CPC command from the Delete Commands menu.

MML Command FormatThe MML command format for the DELETE-CPC command is as follows:

DELETE-CPC:LSSN=ssn;

The ssn argument specifies the SSN of the local subsystem.

Man Page FormatThe alternative format and man page format for DELETE-CPC is dlt-cpc. Deleting a Duplicate Concerned Point Code (DUCPC)

The Delete Duplicate Point Code (DELETE-DUCPC) command deletes a replicate for a local subsystem. However, the system retains the previous replicate code as a CPC.

N O T E S1. The TTC and NTT variants do not support duplicate

concerned point codes.



2. To remove the original point code, you must use the CHANGE-CPC command. If the replicate code does not exist, you receive an error message.

Menu Selection ModeAccess the DELETE-DUCPC command from the Delete Commands menu.

MML Command FormatThe MML command format for the DELETE-DUCPC command is as follows:

DELETE-DUCPC:LSSN=ssn;

The ssn argument specifies the SSN of the local subsystem associated with the DUCPC being deleted.

Man Page FormatThe alternative format and man page format for DELETE-DUCPC is dlt-ducpc.

Deleting a Fictitious Originating Point CodeFictitious originating point codes (FOPCs) apply only to stacks with the network variant defined as ANSI. The CCITT, TTC, and China variants do not support FOPCs.

The Delete Fictitious Originating Point Code (DELETE-FOPC) command deletes the FOPC currently defined for use. Only one FOPC can exist at any one time.

This command returns an error message if the environment variable, ANSI_SINAP_FOPC, is not defined (see CREATE-FOPC).

N O T ETo create a new FOPC, you must first issue the DELETE-FOPC command to delete the existing FOPC. Then, you can issue the CREATE-FOPC command to create a new FOPC.

For more information about an FOPC, see the section that describes how to create an FOPC.

Menu Selection ModeAccess the DELETE-FOPC command from the ANSI Delete Commands menu.

MML Command FormatThe MML command format for the DELETE-FOPC command is as follows:

DELETE-FOPC;




Man Page FormatThe alternative format and man page format for DELETE-FOPC is dlt-fopc.

Deleting all Subsystems at a Remote NodeThe Delete Remote SSN (DELETE-REMSSN) command deletes all subsystem monitoring at a remote node.

N O T ETo delete an individual remote subsystem number, use CHANGE-REMSSN.

Menu Selection ModeAccess the DELETE-REMSSN command from the Delete Commands menu.

MML Command FormatThe MML command format for the DELETE-REMSSN command is as follows:

DELETE-REMSSN:RPC=pc;

The pc argument specifies the point code of the remote node.

Man Page FormatThe alternative format and man page format for DELETE-REMSSN is dlt-remssn.

Deleting a GTT Entry for a NodeThe Delete Global Title (DELETE-GTT) command deletes a global title entry.

Menu Selection ModeAccess the DELETE-GTT command from the Delete Commands menu.

MML Command FormatThe MML command formats for the DELETE-GTT command for the CCITT, China, and TTC network variants are as follows:

DELETE-GTT:GTI=1,NOAI=noai,LADDR=laddr; DELETE-GTT:GTI=2,TT=tt,LADDR=laddr; DELETE-GTT:GTI=3,TT=tt,NP=np,LADDR=laddr; DELETE-GTT:GTI=4,TT=tt,NP=np,NOAI=noai,LADDR=laddr;



The MML command formats for DELETE-GTT command for the ANSI network variant are as follows:

DELETE-GTT:GTI=1,TT=tt,NP=np,LADDR=laddr; DELETE-GTT:GTI=2,TT=tt,LADDR=laddr;

N O T EValues for the LADDR, HADDR, and NADDR global title address components can be displayed in either decimal or hexadecimal character formats. If the HEX_GLOBAL_TITLE environment is not set, then decimal is the default character format. If the variable is set, then hexadecimal is the active character format. Refer to the section “Using Hexadecimal Values in GTT Strings” in Chapter 3 for more information.

Table 4-18 describes the arguments for the DELETE-GTT command.

Table 4-18. DELETE-GTT Command Arguments (Page 1 of 3)


gti Specifies the global title indicator. The value of this argument indicates the addressing components included in the global title. The global title formats associated with each value differ slightly between network variants as indicated:

CCITT/TTC/China Global Title Formats:

GTI Value Global Title Contents0 No global title1 NOAI only2 TT only3 TT and NP4 TT, NP, and NOAI


GTI Value Global Title Contents0 No global title1 TT and NP*2 TT only* The global title formats for ANSI GTI 1 and CCITT/China/TTC/NTT GTI 3 are identical.



tt Specifies the translation type, which directs the message to the appropriate global-title-translation function. Valid values are in the range 0 through 254. For the CCITT, China, TTC, and NTT network variants, include this argument if the GTI is 2, 3, or 4. For the ANSI network variant, include this argument if the GTI is 1, 2, 3, or 4.

np Specifies the numbering plan used for the address information in the global title (for example, ISDN/Telephony, data, or ISDN/Mobile). Include this argument if the GTI is 3 or 4 for the CCITT, China, TTC, and NTT network variants or if the GTI is 1 for the ANSI network variant. Valid values are in the range 0 through 14.

noai Specifies the nature-of-address indicator, which identifies the type of number used in the global title (for example, subscriber, national significant, or international). (Not used for the ANSI network variant.)

Note: The default value range for this indicator is from 1 through 4. Setting the GTT_BYPASS_NOAI_CHECK environment variable expands the range from 1 through 127.

laddr Specifies the low address (starting values) of a range of global titles. If you do not specify haddr, the global title’s address information must exactly match the laddr value in order to match the global-title entry. If you specify haddr, the laddr value specifies the low address (the start) of a range of global titles, and any global title between laddr and haddr will match this global-title entry.







Removing a Link, Link Set, or Route Set from Service

Man Page FormatThe alternative format and man page format for DELETE-GTT is dlt-gtt.

Removing a Link, Link Set, or Route Set from ServiceTo take a link, link set, or route set out of service, perform the actions described for that component using commands accessed from the Configure Commands menu:

• To remove a link from service in the network, perform these steps:

a. Deactivate the link using the CONFIGURE-LINK command.

b. Logically remove the link from the network using the DELETE-LINK command.

• To block a route set, use the CONFIGURE-RSET command. Use this command to stop all traffic to the destination you specified.

• To restrict traffic on just one link set, deactivate the link set using the CONFIGURE-LSET command.

Putting a New Link into ServiceThis section describes the steps you must perform to put a new link into service. See Chapter 3, ‘‘Software Configuration,” for more information on creating the links.

1. If a new link is required for the new link set, provision it using the CREATE-LSET command, accessed from the Create Commands menu.

2. Create the new link using the CREATE-LINK command, accessed from the Create Commands menu.

For the CCITT variant only, you can optionally include one or both of the following arguments to provide “backup” or alternate SCCP routing if the primary SCCP is unavailable.

dpc2 Specifies the DPC to use if the primary SCCP is unavailable.

DPC2=<backup DPC>or DPC2=NONE

ssn2 Specifies the SSN to use if the primary SCCP is unavailable.

SSN2=<backup SSN>orSSN2=NONE




Handling SINAP/SS7 Measurements

3. Activate the newly created link using the CONFIGURE-LSET or CONFIGURE-LINK command, accessed from the Configure Commands menu. Either command readjusts the status of member links in a link set based on the priority of the links and the defined active link count of the link set at creation.

4. If you created a new link in step 1, add it to a new or existing route definition using one of the following methods:

a. To add a new route set definition, use the CREATE-RSET command (Create Commands menu). To activate the new route set, configure it (change its state to ACTIVE) using the CONFIGURE-RSET command (Configure Commands menu).

b. Use CHANGE-RSET to add the new link set to an existing route set definition (Change Commands menu).

Handling SINAP/SS7 MeasurementsYou can use the measurement-reporting commands to access the MTP, SCCP, and TCAP statistical information that the SINAP/SS7 system maintains while it is active. When you issue a measurement-reporting command, you specify the time period you want the report to cover using the start and stop arguments in the commands. The command generates a report presenting the statistics gathered for that time period. You can generate a report for a particular time period, such as a day, a week, a month, or longer.

The environment variable SINAP_ALT_MEASUREMENT_INTERVAL supports 5-minute, 15-minute and 30-minute reporting intervals. To define the reporting interval for measurement reports, uncomment this environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file and set it to one of the following measurement intervals before starting the SINAP node.

N O T E S1. All measurement reports (REPORT-MALL,

REPORT-MTP, REPORT-MSSCP, and REPORT-MTCAP) reflect the measurement interval specified in the environment variable SINAP_ALT_MEASUREMENT_ INTERVAL.

2. Commenting-out the SINAP_ALT_MEASUREMENT_ INTERVAL environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh]

Value Measurement Interval

0 or 30 30 minutes

1 or 15 15 minutes

2 or 5 5 minutes



environment file will not disable the measurement interval feature. This action will only cause the measurement interval to revert to the default 30 minute interval.

You can save a measurement report to a file by specifying the file name and location using the Print to Filename argument. You can then print and view particular reports when needed. See ‘‘Enabling and Disabling Printing’’ in Chapter 2 for information on activating the print options in the SINAP/SS7 system.

To include on the measurement reporting printout the name of the sysopr window from which the MML command was issued (called the TTY), uncomment the following environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

SINAP_MML_PRINT_TTYNAME=1

This section describes all the measurement-reporting capabilities of the SINAP/SS7 system. Measurement-reporting tasks include:

• Reporting measurements

• Retrieving measurements

• Starting and stopping on-demand measurements

• Starting and stopping writing to a log file

• Dumping log files at specified intervals

You can issue commands directly from the UNIX prompt or use the Terminal Handler menus and prompts.

Using the Terminal Handler menu selection mode, select the Measurements Commands option from the Network Commands menu to display the measurements commands, shown in Figure 4-32.

Figure 4-32. Measurements Commands Menu

Measurements Commands:1. Report Measurements2. Retrieve Measurements3. Start On Demand Measurement4. Stop On Demand Measurement5. Start Write Log File6. Stop Write Log File



The Report Measurements menu offers options shown in the sample menu in Figure 4-33.

Figure 4-33. Report Measurements Menu

For each option on the menu, you can define the time period the report covers, generate a report that presents the statistics or measurements gathered, save the report to a file, and print a copy of the report.

When you select one of the measurement-reporting options from the Report Measurements menu, the MML build screen appears, prompting you to enter a start date and time and an end date and time for your report. All measurements from the specified time period are retrieved and included in the report. The sample screen in Figure 4-34 includes sample entries to create the MML command for a report for the time period of 12:00 AM on January 15, 1998 through 12:00 AM on January 16, 1998. User entries are in bold type.

Figure 4-34. Report Sample Screen

Report Measurements:1. Report MTP Measurements2. Report SCCP Measurements3. Report TCAP Measurements4. Report ALL Measurements

MML as built isREPORT-MALL:

Date is specified as [CC]YY-MM-DDSpecify start date: DATE=1998-01-15DATE=1998-01-15Time is specified as HH:MMSpecify start time [where MM is 00 or 30 only]: TIME=00:00DATE=1998-01-15,TIME=00:00Date is specified as [CC]YY-MM-DDSpecify end date: DATE:1998-01-16DATE=1998-01-15,TIME=12:00,DATE=1999-01-16Time specified as HH:MMSpecify end time [where MM is 00 or 30 only]: TIME=00:00



You specify the time and date information using these guidelines:

• For the start and end date, use the format [CC]YY-MM-DD where [CC]YY is the century and the year, for example, 1998. Optionally, you can enter only a two-digit year, for example, 98. MM is the month, for example, 01 for January. DD is the date, for example, 15. Include hyphens between the values, as in 1998-01-15, or optionally, 98-01-15.

Valid values for the year arguments include:

—CC = 19 or 20

—YY = 80 through 99 for century 19, or 0 through 38 for century 20

—MM = 01 through 12

—DD = 01 through 31

To generate a report for today’s measurements, you can enter the value, TODAY, as the date argument instead of using the format [CC]YY-MM-DD. If you do not specify an end date, the end date is the same as the start date.

• For the start and end time, use the format HH:MM where HH is the hour and MM is the minutes. Include a colon between the values. If no end time is specified, the command generates a report for a 30-minute period, beginning at the specified start time. For example, if you specify 12:00 as the start time and do not specify an end time, the command generates a report for the 30-minute time period between 12:00 and 12:30.

Valid values for the start and end times are:

• HH = 1 through 24

• MM = Either 00 or 30

Reporting Measurement ConsiderationsWhen you issue commands to generate a measurement report, consider the following:

• Measurements are only generated while the SINAP system is active. If you issue a measurement-reporting command for a period of time during which the SINAP system was inactive, the command generates an empty measurement report.

If the SINAP system was active for any amount of time during the specified time period, the measurement report will contain data, but it will not be obvious from the data how much of the time the SINAP system was active. If the measurement report contains MTP statistics, you can determine the amount of time that the SINAP system was active from the L2 Serv field of the MTP measurements section. The L2 Serv field shows the amount of time (in seconds) that the SINAP system was active during the time period covered by the measurement report. For example, suppose you generate an MTP measurement report for a 24-hour period of time during which the SINAP system was active for only 12 hours.



Although the report appears to contain data for the specified 24-hour time period, the L2 Serv field indicates that the SINAP system was only active for 12 of the 24 hours.

• A blank measurement report indicates that there is no measurement data for the specified time interval. This indicates one of the following conditions: the SINAP system was not running during the specified time period, the SINAP system was running but the measurement-collection process was turned off, or the log file containing those measurements was deleted from the $SINAP_HOME/Logs/system directory.

• If you issue one of the measurement-reporting commands and specify an invalid period of time, the command returns an error message.

Saving the Report to a File and Printing ItYou can save the measurement report to a file and print it using the following instructions:

1. Display the measurement report you want to save using the appropriate command.

2. After displaying the measurements report, the terminal handler displays a prompt asking whether you want to quit. Press CTRL-P to invoke the Print Options menu.

3. Select the Print to Filename option. The Terminal Handler asks you to specify a name in the FILE= field.

4. Specify a file name and press RETURN. The file saves by default into the $SINAP_HOME/sysopr directory. If you want to save it to another location, include the file path in the file name specification. For example, specifying the file path, FILE=$SINAP_HOME/mtp-1230, writes the measurement file, mtp-1230, to the home directory of the SINAP/SS7 login account, $SINAP_HOME.

5. The MML Send Menu displays the new file name specification. Press RETURN to execute the command. The Terminal Handler confirms the execution.

The following sections describe how to report measurements for each MTP, SCCP, and TCAP subsystem, as well as for all systems.

Reporting MTP MeasurementsThe Report MTP Measurements (REPORT-MMTP) command creates a report on MTP-related information.

Linkset MeasurementsOptional information on average traffic is included in the report when you enable an environment variable. This information can be used to help administer SS7 link capacity.

If you set the environment variable MTP_LINKSET_MEASUREMENT=YES, the REPORT-MMTP (and REPORT-MALL) report displays the number of octets and MSUs transmitted and received per second on all links configured for a link set according to the measurement interval (5-minute, 15-minute, or 30-minute) specified by the environment variable SINAP_ALT_MEASUREMENT_INTERVAL. These reports also include the peak octet



and MSU values within the specified measurement interval for the reporting period (day, week, month).

If you do not define the environment variable MTP_LINKSET_MEASUREMENT, the number of octets and MSUs transmitted and received per second and the peak octet and MSU values are not reported.

Optional fields on REPORT-MMTP (and REPORT-MALL) measurement:

Number of MSUs:

Number of Octets/Sec:

Number of MSUs/Sec:

Peak Value of Octets:

Peak Value of MSUs:

Menu Selection ModeAccess the REPORT-MMTP command from the Report Measurements menu.

MML Command Format The MML command format for the REPORT-MMTP command is:

REPORT-MMTP:DATE=date,TIME=time, PRINT=print , FILE=file ;

Table 4-19 describes the argument for the REPORT-MMTP command

Table 4-19. REPORT-MMTP Command Arguments (Page 1 of 2)


date For the start and end date, use the format [CC]YY-MM-DD where [CC]YY is the century and the year, for example, 1998. Optionally, you can enter only a two-digit year, for example, 98. MM is the month, for example, 01 for January. DD is the date, for example, 15. Include hyphens between the values, as in 1998-01-15, or optionally, 98-01-15.

Valid values for the year arguments include:• CC = 19 or 20

• YY = 80 through 99 for century 19, or 0 through 38 for century 20

• MM = 01 through 12

• DD = 01 through 31




time Specifies the start and end time of the requested measurement taking period based on the 24-hour timekeeping system (00:00 hours is midnight). The value of this argument is a four-decimal number in the format HH:MM where HH is the hour and MM is the minute(s). MM is either 00 or 30 only. Include the colon (:) in the start time and end time. If no end time is specified, the command generates a report for a 30-minute period, beginning at the specified start time.



Number of MSUs

Displays the number of MSUs transmitted and received on all links configured for a link set in 30-minute blocks during the reporting interval specified in the MML command. If you do not define the environment variable MTP_LINKSET_MEASUREMENT, the Number of MSUs are not reported.

Number of Octets/Sec

Displays the number of octets transmitted and received per second on all links configured for a link set in 30-minute blocks during the reporting interval specified in the MML command. If you do not define the environment variable MTP_LINKSET_MEASUREMENT, the Number of Octets/Sec are not reported.

Number of MSUs/Sec

Displays the number of MSUs transmitted and received per second on all links configured for a link set in 30-minute blocks during the reporting interval specified in the MML command. If you do not define the environment variable MTP_LINKSET_MEASUREMENT, the Number of MSUs/Sec are not reported.

Peak Value of Octets

Displays the peak value of octets transmitted and received on all links configured for a link set in 30-minute blocks during the reporting interval specified in the MML command. If you do not define the environment variable MTP_LINKSET_MEASUREMENT, the peak value of octets is not reported.

Peak Value of MSUs

Displays the peak value of MSUs transmitted and received on all links configured for a link set in 30-minute blocks during the reporting interval specified in the MML command. If you do not define the environment variable MTP_LINKSET_MEASUREMENT, the peak value of MSUs is not reported.

Table 4-19. REPORT-MMTP Command Arguments (Page 2 of 2)




Man Page FormatThe alternative format and man page format for REPORT-MMTP is rept-mmtp.

Sample ReportsThe sample report shown in Figure 4-35 displays measurement data of REPORT-MMTP for a 30-minute time period beginning at 8:30 AM on June 24:

Figure 4-35. Sample REPORT-MMTP Output Display

N O T EIf you have not defined the environment variable MTP_LINKSET_MEASUREMENT, then the following fields are not displayed in the MTP 30-minute measurement report. The number of MSUs, number of Octets/Second, number of MSUs/Second, Peak Value of Octets, and the Peak Value of MSUs.

Reporting SCCP MeasurementsThe Report SCCP Measurements (REPORT-MSCCP) command reports on SCCP-related measurements.

Menu Selection ModeAccess the REPORT-MSCCP command from the Report Measurements menu.

MTP 30 minute measurements: 06/24, 08:30

Link Name L3 Unava L3 Cong L3 TX L3 RX L2 Serv L2 SU Err LNK0 84 0 1147584 900678 11797 0 Number of MSUs: 58104 58107 Number of Octets/Sec: 637 500 Number of MSUs/Sec: 31 31 Peak Value of Octets: 4 5 Peak Value of MSUs: 6 7

SP MSU Discarded

Destination Occurrences Duration 3003 0 83



MML Command Format The MML command format for the REPORT-MSCCP command is:

REPORT-MSCCP:DATE=date,TIME=time, PRINT=print , FILE=file ;

Table 4-20 describes the arguments for REPORT-MSCCP command.

Table 4-20. REPORT-MSCCP Command Arguments








time Specifies the start and end time of the requested measurement-taking period based on the 24-hour timekeeping system (00:00 hours is midnight). The value of this argument is a four-decimal number in the format HH:MM where HH is the hour and MM is the minute. MM is 00 or 30 only. Include the colon (:) in the start time and end time. If no end time is specified, the command generates a report for a 30-minute period, beginning at the specified start time.





Man Page FormatThe alternative format and man page format for REPORT-MSCCP is rept-msccp.

Sample ReportThe sample output of REPORT-MSCCP shown in Figure 4-36 displays an SCCP report for a 30-minute report interval beginning at 8:30 AM on June 24. User entries are in bold type.

Figure 4-36. Sample REPORT-MSCCP Output Display

Reporting TCAP MeasurementsThe Report TCAP Measurements (REPORT-MTCAP) command reports on TCAP-related measurements.

Menu Selection ModeAccess the REPORT-MTCAP command from the Report Measurements menu.

MML Command Format The MML command format for the REPORT-MTCAP command is:

REPORT-MTCAP:DATE=date,TIME=time, PRINT=print , FILE=file ;

REPORT-MSCCP:DATE=TODAY,TIME=08:30;command completedSCCP Measurements: 06/24, 08:30

PC Not Available = 0Network Configuration = 0SSN Not Available = 0Unequipped User = 0Syntax Error = 0Unknown Reason = 0

SSN Message Sent Message Received254 0 0



Table 4-21 describes the arguments for the REPORT-MTCAP command.

Man Page Format The alternative format and man page format for REPORT-MTCAP is rept-mtcap.

Table 4-21. REPORT-MTCAP Command Arguments








time Specifies the start and end time of the requested measurement taking period based on the 24-hour timekeeping system (00:00 hours is midnight). The value of this argument is a four-decimal number in the format HH:MM where HH is the hour and MM is the minute. MM is 00 or 30 only. Include the colon (:) in the start time and end time. If no end time is specified, the command generates a report for a 30-minute period, beginning at the specified start time.





Sample ReportThe sample output of REPORT-MTCAP shown in Figure 4-37 displays a TCAP report for a 30-minute interval beginning at 8:30 AM on June 24.

Figure 4-37. Sample REPORT-MTCAP Output Display

Reporting Measurements for All MTP, SCCP, and TCAP SubsystemsThe Report Measurements (REPORT-MALL) command reports the results of all measurements related to the MTP, SCCP, and TCAP subsystems.


If you set the environment variable MTP_LINKSET_MEASUREMENT=YES, the REPORT-MALL (and REPORT-MMTP) report displays the number of octets and MSUs transmitted and received per second on all links configured for a link set according to the measurement interval (5-minute, 15-minute, or 30-minute) specified by the environment variable SINAP_ALT_MEASUREMENT_INTERVAL. These reports also include the peak octet and MSU values within the specified measurement interval for the reporting period (day, week, month).


Optional fields on REPORT-MALL (and REPORT-MMTP) measurement:

Number of MSUs:


Number of MSUs/Sec:


REPORT-MTCAP:DATE=TODAY,TIME=08:30; command completed

Report TCAP Measurements:

TCAP Measurements: 06/24, 8:30

SSN Comp Sent Comp Rcvd Local Reject Return Error254 0 0 0 0



Peak Value of MSUs:

Menu Selection ModeAccess the REPORT-MALL command from the Report Measurements menu.

MML Command Format The MML command format for the REPORT-MALL command is:

REPORT-MALL:DATE=date,TIME=time, PRINT=print , FILE=file ;

Table 4-22 describes the arguments for the REPORT-MALL command.

Table 4-22. REPORT-MALL Command Arguments (Page 1 of 2)








time Specifies the start and end time of the requested measurement taking period based on the 24-hour timekeeping system (00:00 hours is midnight). The value of this argument is a four-decimal number in the format HH:MM where HH is the hour and MM is the minute(s). MM is either 00 or 30 only. Include the colon (:) in the start time and end time. If no end time is specified, the command generates a report for a 30-minute period, beginning at the specified start time.




Man Page Format The alternative format and man page format for REPORT-MALL is rept-mall.


Number of MSUs

Displays the number of MSUs transmitted and received on all links configured for a link set in 30-minute blocks during the reporting interval specified in the MML command. If you do not define the environment variable MTP_LINKSET_MEASUREMENT, the Number of MSUs are not reported.

Number of Octets/Sec

Displays the number of octets transmitted and received per second on all links configured for a link set in 30-minute blocks during the reporting interval specified in the MML command. If you do not define the environment variable MTP_LINKSET_MEASUREMENT, the Number of Octets/Sec are not reported.

Number of MSUs/Sec

Displays the number of MSUs transmitted and received per second on all links configured for a link set in 30-minute blocks during the reporting interval specified in the MML command. If you do not define the environment variable MTP_LINKSET_MEASUREMENT, the Number of MSUs/Sec are not reported.

Peak Value of Octets

Displays the peak value of octets transmitted and received on all links configured for a link set in 30-minute blocks during the reporting interval specified in the MML command. If you do not define the environment variable MTP_LINKSET_MEASUREMENT, the peak value of octets is not reported.

Peak Value of MSUs

Displays the peak value of MSUs transmitted and received on all links configured for a link set in 30-minute blocks during the reporting interval specified in the MML command. If you do not define the environment variable MTP_LINKSET_MEASUREMENT, the peak value of MSUs is not reported.

Table 4-22. REPORT-MALL Command Arguments (Page 2 of 2)




Sample ReportThe sample output of REPORT-MALL shown in Figure 4-38 displays the measurements for all subsystems for the 30-minute time period starting at 8:30 AM on June 24:

Figure 4-38. Sample REPORT-MALL Output Display

M REPORT-MALL:DATE=TODAY,TIME=08:30; command completed

Report MTP 30 minute measurements:MTP 30 minute measurements: 06/24, 08:30


SP MSU Discarded


Report SCCP Measurements:

SCCP Measurements: 06/24, 08:30

PC Not Available = 0Network Configuration = 0SSN Not Available = 0Unequipped User = 0Syntax Error = 0Unknown Reason = 0

SSN Message Sent Message Received254 0 0


TCAP Measurements: 06/24, 08:30

SSN Comp Sent Comp Rcvd Local Reject Return Error 254 0 0 0 0



N O T EIf you have not defined the environment variable MTP_LINKSET_MEASUREMENT, then the following fields are not displayed in the MTP 30-minute measurement report: The number of MSUs, number of Octets/Second, number of MSUs/Second, Peak Value of Octets, and the Peak Value of MSUs.

Retrieving Oldest 15- or 30-Minute Node MeasurementsThe Retrieve Oldest 15 or 30 min Measurement (RETRIEVE-NOM) command retrieves the oldest 15- or 30-minute node network management measurement report. After it appears, the report is deleted. The output for this command is similar to the output for REPORT-MALL. (See the previous section on reporting measurements for MTP, SCCP, and TCAP.)

The SINAP/SS7 system collects statistical information on the number of times and the length of time that destination point codes (DPCs) are inaccessible during a 30-minute period. The SINAP/SS7 system keeps track of the route set used to access individual DPCs by applying a timestamp (time received) to each route set. The SINAP/SS7 system also maintains two structures, rcMeasData and routeSetMeasurements, for each route set. The structures contain inaccessibility information.

N O T EWhen the SINAP/SS7 system first starts, the system marks each route set as inaccessible and sets the timestamp of each route set to the time that the SINAP/SS7 system was started. When the route set first becomes accessible, the SINAP/SS7 system uses this timestamp to measure the length of time that route set was initially inaccessible.

During each 30-minute measurement period, the SINAP/SS7 l3rc process collects inaccessibility data for each route set and stores this data in static memory in the route set’s rcMeasData structure. At the end of the measurement period, the contents of rcMeasData are written to the route set’s routeSetMeasurements structure, which is stored in shared memory. The SINAP/SS7 system reinitializes the rcMeasData structure’s fields to zero and begins collecting inaccessibility data for the next 30-minute measurement period.


If you set the environment variable MTP_LINKSET_MEASUREMENT=YES, the REPORT-MMTP and REPORT-MALL report displays the number of octets and MSUs



transmitted and received per second on all links configured for a link set according to the measurement interval (5-minute, 15-minute, or 30-minute) specified by the environment variable SINAP_ALT_MEASUREMENT_INTERVAL. These reports also include the peak octet and MSU values within the specified measurement interval for the reporting period (day, week, month).


Optional fields on REPORT-MMTP and REPORT-MALL measurement:

Number of MSUs:


Number of MSUs/Sec:


Peak Value of MSUs:

Menu Selection ModeFrom the Network Commands/Measurements Commands menu, select the Retrieve Measurements (RETRIEVE-NOM) option. The Retrieve Measurements menu appears as shown in Figure 4-39.

Figure 4-39. Retrieve Measurements Menu

Select the Retrieve Oldest 15 or 30 min Measurement option from the menu to view the measurement data for the selected time period.

MML Command Format The MML command format for the RETRIEVE-NOM command is:

RETRIEVE-NOM;

The RETRIEVE-NOM command has no arguments.

Retrieve Measurements

1. Retrieve Oldest 15 or 30 min Measurement2. Retrieve Latest 5 min Measurement

<RETRIEVE>



N O T ETo display the measurements for a particular DPC, issue the REPORT-MMTP command or the REPORT-MALL command and specify the current date and time. The SINAP/SS7 system displays the DPC’s inaccessibility measurements for the preceding 30 minutes. The first column, Destination, indicates the DPC whose measurements are displayed. The second and third columns indicate the number of times and the total amount of time, respectively, that the DPC was inaccessible during the preceding 30 minutes.

Sample ReportThe sample screen shown in Figure 4-40 displays the 30-minute network management measurement report for the RETRIEVE-NOM command.



Figure 4-40. Sample RETRIEVE-NOM Command Output

N O T EIf you have not defined the environment variable MTP_LINKSET_MEASUREMENT, then the following fields are not displayed in the MTP 30-minute measurement report: the number of MSUs, number of Octets/Second, number of

M RETRIEVE-NOM; command completed

Report MTP 30 minute measurements: MTP 30 minute measurements: 12/14, 00:00 - 12/14, 00:30


SP MSU Discarded


Report SCCP Measurements:

SCCP Measurements: 12/14, 00:00 - 12/14, 00:30

PC Not Available = 0 Network Configuration = 0 SSN Not Available = 0 Unequipped User = 0 Syntax Error = 0 Unknown Reason = 0


TCAP Measurements: 12/13, 23:30 - 12/14, 00:00

SSN Comp Sent Comp Rcvd Local Reject Return Error 254 0 0 0 0



MSUs/Second, Peak Value of Octets, and the Peak Value of MSUs.

Man Page Format The alternative format and man page format for RETRIEVE-NOM is rtrv-nom.

Displaying Latest 5-Minute Node Network Management MeasurementsThe Retrieve Latest 5-Min Measurement (RETRIEVE-SMR) command retrieves the most recently completed five-minute node network management measurement report, including the beginning and ending times of the period. After the report appears, it is deleted. You cannot save or print the output. If there are any five-minute measurements older than the ones being retrieved, they are also deleted.

Menu Selection ModeSelect the Retrieve Latest 5 min Measurement option from the Retrieve Measurements menu to view the network management report for the last 5-minute time period.

MML Command Format The MML command format for the RETRIEVE-SMR command is:

RETRIEVE-SMR;

The RETRIEVE-SMR command has no arguments.

Sample ReportThe output shown in Figure 4-41 displays sample a 5-minute network management report.

Figure 4-41. Sample 5-Minute Management Report

M RETRIEVE-SMR;command completed

Report MTP 5-minute measurements:MTP 5 minute measurements: 11/17. 19:12

Adjacent SP Unavailable3003 299

0 00 00 00 00 0



Man Page Format The alternative format and man page format for RETRIEVE-SMR is rtrv-smr.

Starting On-Demand Measurements The start on-demand measurements (START-MEASURE) command starts writing on-demand measurements to the measurement logs in the directory $SINAP_Home/Logs/system and reports the data that is collected by the measurement collection process.

Menu Selection ModeFrom the Measurements Commands menu, select the start on-demand measurements option. The Enable/Disable Measurements menu appears as shown in Figure 4-42.

Figure 4-42. Enable/Disable Measurements Command Menu

This menu allows you to enable or disable the collection of measurements for the signaling information fields (SIF) and service information octets (SIO) that were either transmitted or received by the network.

MML Command Format The MML command format for the START-MEASURE command is:

START-MEASURE:MEASURE=measure;

The measure argument specifies whether received or transmitted octets are being measured:

• OCTXMT—SIF and SIO octets transmitted

• OCTRCV—SIF and SIO octets received

Man Page FormatThe alternative format and man page format for START-MEASURE is sta-measure.

Enable/Disable Measurements

1. Enable or Disable SIO/SIF octets transmitted2. Enable or Disable SIO/SIF octets received

<START-MEASURE>



Sample Output The report shown in Figure 4-43 is a sample of the measurement collection process started by the START-MEASURE command:

Figure 4-43. Sample START-MEASURE Command Output

Description Level Units Duration Activation

Duration of Link in the MTP 2 seconds/SL 30 minute PermanentIn-Service State

Number of Signal Units in MTP 2 events/SL 30 minute PermanentError

Duration of SL MTP 3 seconds/SL 30 minute PermanentUnavailability

NumOctets ber of SIF and MTP 3 octets/SL 30 minute On DemandSIO Transmitted

Number of SIF and SIO MTP 3 octets/SL 30 minute On DemandOctets Received

MSUs discarded Due to SL MTP 3 MSUs/SL 30 minute PermanentCongestion

Duration of Adjacent SP MTP 3 seconds/SP 5 minute PermanentInaccessible

MSUs Discarded Due to a MTP 3 MSUs/SP 5 minute PermanentRouting Data Failure

Routing Failure-Point Code SCCP messages 30 minute PermanentNot Available

Routing Failure-Network SCCP messages 30 minute PermanentRouting Failure-Subsystem SCCP messages 30 minute Permanent

UnavailableRouting Failure-Unequipped SCCP messages 30 minute Permanent

UserSyntax Error Detected SCCP messages 30 minute PermanentRouting Failure-Reason SCCP messages 30 minute Permanent

UnknownTotal Messages Sent SCCP msgs/appl 30 minute PermanentTotal Messages Received SCCP msgs/appl 30 minute PermanentTotal TCAP Components Sent TCAP comp/appl 30 minute PermanentTotal TCAP Components TCAP comp/appl 30 minute Permanent

ReceivedTCAP Local Rejects TCAP rej/appl 30 minute PermanentTCAP Return Errors TCAP err/appl 30 minute Permanent

Key:SL = Signaling Link SP = Signaling PointSIF = Signaling Information Field SIO = Service Information Octet



Stopping On-Demand MeasurementsThe stop on-demand measurements (STOP-MEASURE) command stops writing measurements to the measurement logs in the directory $SINAP_HOME/Logs/system.

Menu Selection ModeSelect the Stop On-demand Measurements option from the Measurements menu. The Enable/Disable Measurements screen appears. Specify that you want to disable the measurement of SIO and SIF octets that are either received or transmitted.

MML Command Format The MML command format for the STOP-MEASURE command is:

STOP-MEASURE:MEASURE=measure;

The measure argument specifies whether received or transmitted octets are being measured:

• OCTXMT—SIF and SIO octets transmitted

• OCTRCV—SIF and SIO octets received

Man Page FormatThe alternative format and man page format for STOP-MEASURE is stop-measure.

Start Writing Measurements to the Measurement Log FileThe Start Write Log File (START-MWRITE) command initiates writing measurements to the measurement logs in the directory $SINAP_HOME/Logs/system.

Menu Selection ModeSelect the Start Write Log File option from the Measurements Commands menu to begin logging measurements. Respond to the system prompts to create the MML command for this task.

MML Command FormatThe MML command format for the START-MWRITE command is:

START-MWRITE;


Man Page FormatThe alternative format and man page format for START-MWRITE is sta-mwrite.



Stop Writing Measurements to the Measurement Log FileThe Stop Write Log File (STOP-MWRITE) command stops writing measurements to the measurement logs in the directory $SINAP_Home/Logs/system.

Menu Selection ModeSelect the Stop Write Log File option from the Measurements Commands menu to stop logging measurements. Respond to the system prompts to create the MML command for this task.

MML Command FormatThe MML command format for the STOP-MWRITE command is:

STOP-MWRITE;

The STOP-MWRITE command has no arguments.

Man Page FormatThe alternative format and man page format for STOP-MWRITE is stop-mwrite.

Dumping MTP Routing and Management Tables to the Static Table FileThe Dump Table (DUMP-TABLE) command dumps (saves) the contents of the MTP routing and management tables to the static table file, $SINAP_HOME/cm_display/static_table, in binary format. The Stratus Customer Assistance Center (CAC) can use this file to aid in problem analysis.

Menu Selection ModeSelect the Dump Table option from the Network Commands menu to save the MTP tables to the table file. Respond to the system prompts to create the MML command for this task.

MML Command FormatThe MML command format for the DUMP-TABLE command is:

DUMP-TABLE;



Backing Up Databases

Sample OutputThe report shown in Figure 4-44 displays a sample output of the DUMP-TABLE command.

Figure 4-44. Sample DUMP-TABLE Command Output

Man Page FormatThe alternative format and man page format for DUMP-TABLE is dump-table.

Backing Up DatabasesThis section provides information on the following topics:

• Backing up the node static database

• Backing up an application to disk or tape

• Displaying the number of days in the SINAP/SS7 backup cycle

• Changing the interval for automatic node backup

Using the menu selection mode to issue the commands, you perform backup activities using the Systems Commands menu and the Application Commands menu.

Backing Up the Node Static DatabaseThe Backup Node (BACKUP-NODE) command backs up the current node static database and writes it to $SINAP_HOME/Bin/shm/pri/STATIC_load.

Menu Selection ModeSelect the Backup Node option from the System Commands menu to begin backup activities. Respond to the system prompts to select the file to back up and the location to which to save it.

MML Command FormatThe MML command format for the BACKUP-NODE command is:

BACKUP-NODE;


M DUMP-TABLE; oktable dumped in file:home/sinap/cm_display/static-table


Backing Up Databases

Man Page FormatThe alternative format and the man page format for BACKUP-NODE is bkup-node.

Backing Up an Application to Disk or TapeThe Backup Application (BACKUP-APPL) command copies the contents of the source file into the destination file.

Menu Selection ModeSelect the Backup Application option from the Application Commands menu to back up the application’s source file. Respond to the system prompts to specify both the file to be backed up and the location to which to save it.

MML Command FormatThe MML command format for the BACKUP-APPL command is:

BACKUP-APPL:SOURCE=source,DESTINATION=destination;

Table 4-23 describes the arguments for the BACKUP-APPL command.

Man Page FormatThe alternative format and man page format for BACKUP-APPL is bkup-appl.

Displaying the Number of Days in the Backup CycleThe Display Backup or Purge Day (DISPLAY-BKUPDAY) command displays the number of days in the SINAP/SS7 node database backup cycle.

Menu Selection ModeSelect the Display Backup or Purge Day option from the System Commands menu to display the number of days in the backup cycle. Respond to the system prompts to create the MML command for this task.

MML Command Format The MML command format for the DISPLAY-BKUPDAY command is as follows:

DISPLAY-BKUPDAY;

Table 4-23. BACKUP-APPL Command Arguments


source Specifies the source device and path name.

destination Specifies the destination device and path name.


Restoring Databases


Sample DisplayThe output shown in Figure 4-45 is a sample of the DISPLAY-BKUPDAY command showing the automatic backup cycle set to occur daily:

Figure 4-45. Sample DISPLAY-BACKUP Command Output

Man Page Format The alternative format and man page format for DISPLAY-BKUPDAY is displ-bkday.

Changing the Interval for Automatic Node BackupThe Change Backup or Purge Day (CHANGE-BKUPDAY) command changes the number of days in the SINAP/SS7 node database backup cycle.

Menu Selection ModeSelect the Change Backup or Purge Day option from the System Commands menu to change the interval between backups. Respond to the system prompts to designate the number of days in the automatic backup cycle.

MML Command Format The MML command format for the DISPLAY-BKUPDAY command is:

CHANGE-BKUPDAY:DAYS=days;

The days argument specifies the number of days for which the system performs automatic node backup. Enter a number in the range of 1 through 365.

Man Page Format The alternative format and man page format for CHANGE-BKUPDAY is chg-bkupday.

Restoring DatabasesThis section provides information on performing the following tasks:

• Restoring the node static database from disk

DISPLAY-BKUPDAY;command completedBKUPDAY=1


Restoring Databases

• Restoring an application static database from disk or tape

• Using the rc_log to restore an existing database configuration

In the menu selection mode, use the System Commands menu and the Application Commands menu to perform the tasks in the following sections. See ‘‘Accessing the User Interfaces’’ in Chapter 2 for more information about the menus.

Restoring the Node Static Database from DiskThe Restore Node (RESTORE-NODE) command restores the current node static database from disk.

Menu Selection ModeSelect the Restore Node option from the System Commands menu to restore the static database for the current node. Respond to the system prompts to specify the file to be restored.

MML Command FormatThe MML command format for the RESTORE-NODE command is:

RESTORE-NODE:FROM=source,RCLOG=rclog;

Table 4-24 describes the arguments for the RESTORE-NODE command.


Restoring Databases

Man Page FormatThe alternative format and man page format for RESTORE-NODE is rsy-node.

Restoring an Application Static Database from Disk or TapeThe Restore Application (RESTORE-APPL) command restores an application from disk or tape.

Menu Selection ModeSelect the Restore Application option from the Application Commands menu to restore an application from a backup disk or tape. Respond to the system prompts to specify the file to be restored.

Table 4-24. RESTORE-NODE Command Arguments


source Specifies the source of data that will restore the current node database. Specify one of the following values:PRIMARY - the primary disk copySECONDARY - the secondary disk copy

rclog Specifies whether the restoration procedure will use the Recent Change Command log. This argument is valid only if the restoration is from the primary disk copy. Possible values are YES and NO. If you specified secondary as the value for the source argument, you must specify NO for rclog. This argument is useful if memory is corrupted while you are provisioning the SINAP/SS7 system. The restoration procedure uses the Recent Change Command log to restore the most recent changes made to the database.

Note: The RESTORE-NODE command terminates all SINAP/SS7 applications. Before executing the command, the SINAP/SS7 system displays the following warning:

***WARNING: ANY running SINAP applications will be terminated***

The system prompts you to specify whether you want to continue with the command. If you enter y (yes), the system executes the command. If you enter n (no), the SINAP/SS7 system returns to the command display without executing the command. If a client application is using the SS7 links, you must stop it before executing the RESTORE-NODE command. MTP level-3 and SCCP management stops and restarts.


Purging and Deleting Files

MML Command FormatThe MML command format for the RESTORE-APPL command is:

RESTORE-APPL:SOURCE=source,DESTINATION=destination;

Table 4-25 describes the arguments for the RESTORE-APPL command.

Man Page FormatThe alternative format and man page format for RESTORE-APPL is rst-appl.

Using the rclog File to Restore an Existing Database ConfigurationYou can use the rclog file in two ways to restore an existing static database configuration.

• Method #1—Issue the following send_cm command from a UNIX prompt:

send_cm filename

For filename, specify the name of the rclog file to use.

• Method #2—Copy the configuration into the rclog file and then execute the start_sinap startup script. The start_sinap script reads the rclog file to determine the SINAP/SS7 database configuration.

N O T EFor very large configurations, Stratus recommends using method 2 to restore databases with rclog. This is because method 1 might take a while to execute because the send_cm command must send each command in the rclog file to the Terminal Handler and wait for a response before continuing.

Purging and Deleting FilesThis section describes procedures for displaying and changing the number of days the system retains a log file on disk before it deletes the file. The purge day is the day files are deleted from the system. This section also includes procedures for deleting a file from disk.

Table 4-25. RESTORE-APPL Command Arguments


source Specifies the source device from which the application is being restored.

destination Specifies the complete path name of the destination device and path name.



In the menu selection mode, access these purge and delete commands through the System Commands menu.

Displaying the Number of Days in the Purge Cycle for All Log FilesUse the Display Backup or Purge Day (DISPLAY-PURGEDAY) command to display the number of days a log file remains on disk before it is deleted. You can display the backup or purge day intervals for individual log files, or you can display the backup or purge day intervals for all log files.

Menu Selection ModeFrom the Systems Commands menu, select the Display Backup or Log Purge Day option. The Display Backup or Log Purge Day menu appears as shown in Figure 4-46.

Figure 4-46. Display Backup or Log Purge Day Menu

Select the option for the type of log file you want to view. The system displays the purge day interval setup for that type of log.

N O T EThe ANSI network variant contains no option to display All Log Purge Days.

MML Command FormatThe MML command format for the DISPLAY-PURGEDAY command is:

DISPLAY-PURGEDAY:LOG=logfile;

Display Backup or Log Purge Day

1. Backup Node Day2. Alarm Log Purge Day3. 5 min Measurements Log Purge Day4. 15 or 30 min Measurements Log5. MML Command Log Purge Day6. Software Notebook Log Purge Day7. Monitor Log Purge Day8. All Log Purge Days



The logfile argument specifies one of the logs types for which to display the purge day intervals. The types are listed in Table 4-26.

Man Page FormatThe alternative format for DISPLAY-PURGEDAY is DISPL-PDAY. The man page format for DISPLAY-PURGEDAY is displ-pday.

Sample Display The sample output of the DISPLAY-PURGEDAY command shown in Figure 4-47 displays the purge day intervals set for all logs.

Figure 4-47. Sample DISPLAY-PURGEDAY Command Output

Table 4-26. Log Type Descriptions

Log Type Description

Backup Node Day Days in backup cycle

ALARM Alarm history log

COMMAND Recent Change Command log

MEASUREMENT05 Five-minute Measurement Data log

MEASUREMENT30 30-minute Measurement Data log

NOTEBOOK Software Notebook

MONITOR BITE Monitor log

ALL All log files

DISPLAY-PURGEDAY:LOG=ALL;command completed

ALARMLOG= 7COMMDLOG= 7MESURE05= 7MESURE30= 7NBOOK = 7MONITOR = 7



Changing the Interval for Purging Log FilesThe Change Backup or Purge Day (CHANGE-PURGEDAY) command changes the number of days that a log file remains on disk before it is purged (deleted) from the system. This purge log file is submitted to UNIX during SINAP/SS7 installation.

Menu Selection modeSelect the Change Backup or Purge Day option from the System Commands menu to access the Change Backup or Log Purge Day menu (Figure 4-48).

Figure 4-48. Change Backup or Log Purge Day Menu

Select the log file you want to change from the menu and respond to the system prompts to specify new values and issue the MML command for this task.

N O T EThe ANSI network variant contains no option to change all the log purge days.

MML Command FormatThe MML command format for the CHANGE-PURGEDAY is:

CHANGE-PURGEDAY:LOG=logfile,DAYS=days;

Change Backup or Log Purge Day

1. Backup Node Day2. Alarm Log Purge Day3. 5 min Measurements Log Purge Day4. 15 or 30 min Measurements Log5. MML Command Log Purge Day6. Software Notebook Log Purge Day7. Monitor Log Purge Day8. All Log Purge Days



Table 4-27 describes the arguments for CHANGE-PURGEDAY command.

Man Page FormatThe alternative format and man page format for CHANGE-PURGEDAY is chg-purgeday.

Deleting a File from DiskThe Delete File (DELETE-FILE) command deletes a file, such as an application file or a log file, from the disk.

Menu Selection ModeAccess the DELETE-FILE command from the Systems Command menu and respond to the system prompts to delete a file.

MML Command FormatThe MML command format for the DELETE-FILE command is:

DELETE-FILE:FILE=filename;

The filename argument specifies the full path name of the file to be deleted.

Man Page FormatThe alternative format and man page format for DELETE-FILE is dlt-file.

Table 4-27. CHANGE-PURGEDAY Command Arguments


logfile Specifies one of the following types of log files to be changed. • BKUPDAY—number of days in database backup cycle• ALARM—for the Alarm History log • COMMAND—for the Recent Change Command log • MEASUREMENT05—for five-minute Measurement Data log • MEASUREMENT30—for 30-minute Measurement Data log• NOTEBOOK—for the Software Notebook

• MONITOR—for the BITE Monitor log

days Specifies the number of days (1 through 365) to retain a log file.


Using the BITE Monitor

Using the BITE MonitorThis section provides information on the following topics:

• BITE limitations

• Default log size and location

• Starting and stopping the Built-In Test Environment (BITE) monitor processes

• Reconfiguring BITE processes to run in real-time or time-share modes

• Displaying monitor IDs

• Stopping BITE monitor processes

See Chapter 6, ‘‘Troubleshooting,” for information on using the BITE monitor to isolate and resolve problems.

BITE LimitationsYou should be aware of the following restrictions when using the BITE Monitor and Log Analysis programs. These restrictions apply to each SINAP node and are not system-wide.

• A maximum of eight monitors can exist at any one time.

• A maximum of eight entities can be specified in a single BITE Monitor command.

• The processes BI,LF and BI,ID cannot be monitored.

• The Node Manager (NM) and Terminal Handler (TH) processes cannot be monitored for input if DISPLAY is ON.

• The log file name is checked against file names used in active monitors.

• Only the Node Manager and Terminal Handler processes can turn on the DISPLAY option.

• BITE operates on the node that is currently active in the SINAP/SS7 login window.

Default Log Size and LocationThe default size of a BITE log file is 200K bytes. The maximum size allowed is 1,000K bytes. The default location for BITE log files is $SINAP_HOME/Logs/bite.

The [Node] and [Module] names, if omitted, indicate the local node and module. The [instance] number, if omitted, indicates all the instances at the command time.



Starting the BITE MonitorThe BITE facility operates on the node that is currently active in the SINAP login window. There are two ways to initiate a BITE monitor process:

• Manually—You initiate a BITE monitor process manually by issuing the MML START-MON command through the SINAP/SS7 Terminal Handler.

• Automatically—When an application initially registers with the SINAP/SS7 system, you can specify certain values that automatically start the BITE monitor process along with the application. The application can also include a function call to disable a BITE monitor process. The BITE process then runs continuously in the application’s background until needed. See the SINAP/SS7 Programmer’s Guide (R8052) for more information.

The Start Monitor (START-MON) command initiates monitoring for specified entities from any SINAP/SS7 process. If no errors are detected, the command returns a monitor ID.

Menu Selection ModeUsing the menu selection mode, start the BITE monitor by selecting the BITE Commands option from the SINAP System Main Menu. The BITE Commands menu appears. Start the BITE monitor by selecting the Monitor Commands option from the BITE Commands menu. The BITE Monitor Commands menu appears, as shown in Figure 4-49.

Figure 4-49. BITE Monitor Commands Menu

Select the Start Monitor option and respond to the system prompts to build the MML command that starts the BITE process.


START-MON:ENT= (entity)[(&entity)][,DISP=Y/N] ,LOG=filename [(size)] [,CONT=Y/N];

BITE Monitor Commands

1. Start Monitor2. Stop Monitor3. Display Monitor Ids

<



Table 4-28 describes the arguments for the START-MON command.

Table 4-28. START-MON Command Arguments (Page 1 of 2)


entity Specifies the type of message (IPC, SS7, or link) and process or link entities (up to 8) to be monitored.

The format of entity is TYPE,ID0,ID1,ID2,ID3,ID4,[R/W].

If TYPE is IPC or SS7, ID0 represents the node name, ID1 represents the module name, ID2 represents the application name, ID3 represents the process name, and ID4 represents the instance number. However, ID2 and ID3 are required, and ID0, ID1, and ID4 are optional. The default node name is the name of the current node. The default module name is the current local module. If you omit the ID4 parameter, the SINAP/SS7 system monitors all current instances. Any instance created after the command is executed is not monitored.

If TYPE is LNK, ID0 represents the link number. ID1, ID2, ID3, and ID4 are not present.

To monitor different paths using the same log file, you can specify more than one entity by separating each with an ampersand (&).The R and W arguments are optional. Specifying R indicates a monitoring read; specifying W indicates a write operation. If you omit either option, the SINAP/SS7 system assumes both read and write operations are desired.

DISP Determines whether the monitored events should be displayed on the operator terminal. Fields displayed include the application name and process name of the message originator, the application name and process name of the message’s destination, the message type, the last time stamp, data size, and first eight bytes of data. You must enter either Y or N.

filename Specifies the log file name in which the monitored events are logged. the SINAP/SS7 system writes all log files to the directory, Logs/bite. If the storage capacity is exceeded, the SINAP/SS7 system discontinues the log activity and sends an alarm to Trouble Management. The default size for this log is 200K bytes.

filename(cont.)

In addition to the limitation that the Logs/bite partition imposes for all BITE log files, there is a default size limit for each log file. If a log file reaches the limit, the SINAP/SS7 system automatically closes it and sends an alarm to Trouble Management. You can override this default by using the size parameter after filename. Specify the size as a number of K bytes.



Man Page FormatThe alternative format and man page format for START-MON is sta-mon.

Sample DisplayThe output of START-MON shown in Figure 4-50 displays a sample of the data fields described in Table 4-29.

Figure 4-50. Sample START-MON Command Output

size Specifies the size of the log file as a number of K bytes.

CONT Specifies whether continuous logging should be enabled. Normally, the BITE stops monitor output to a log file when the file size surpasses 200K. The CONT argument allows you to specify that data beyond 200K should be saved. When the BITE log file reaches its limit and CONT is specified, the file is renamed to a backup file and a new logging file is opened. The backup file is of the format filename.bak. The system deletes any previous backup file with the same name.

Logging continues until you stop it with the STOP-MON command.To use this argument, you must specify a value for filename. The default value for this argument is N.

Table 4-28. START-MON Command Arguments (Page 2 of 2)


START-MON:ENT=(IPC,,,NM,CL),DISP=Y;

----time---- --orig--- --dest--- --msg_type--- --size--- ------data----

NM,CL,OK0007:51:34:105 NM,CL1 NM,CM1 RUOK 000R0107:51:34:105 NM,CM1 NM,CL1 IMOK 000W0207:52:34:103 NM,CL1 NM,CM1 RUOK 000R0307:52:34:103 NM,CM1 NM,CL1 IMOK 000W



Displaying Monitor IDsThe Display Monitor ID (DISPLAY-MON) command displays current, active BITE monitors. Current active monitor commands appear with the monitor ID assigned to each monitor. Use this command to get a monitor ID for each active monitor. You can then use this ID in the STOP-MON command.

Menu Selection ModeSelect the Display Monitor ID option from the BITE Commands menu and respond to the system prompts to display the monitor IDs.


DISPLAY-MON;

The command has no arguments.

Man Page FormatThe alternative format and man page format for DISPLAY-MON is displ-mon.

Table 4-29. Displayed Data Fields for the START-MON Command

Data Field Description

time The last time stamp during monitoring.

orig The originator application name and process name. In the sample display, Node Management is the application name, and the Node Management Client Management and Command Management processes represent the process names.

dest The destination application name and process name. In the sample display, the Node Management is the application name, and the Node Management Client Management and Command Management processes represent the process names.

msg_type The type of message being sent, for example, RUOK and IMOK. In the example, because health check operations are enabled, health check messages appear in the field.

size The data size for the M_Block or I_Block. Because no messages are being transmitted in the example, this field is blank.

data The first eight bytes of the message; in the sample display, they do not exist.



Sample Display The sample output of DISPLAY-MON shown in Figure 4-51 lists one current active BITE monitors.

Figure 4-51. Sample DISPLAY-MON Command Output

Stopping the BITE MonitorThe Stop Monitor (STOP-MON) command disables a BITE monitor process. Stopping the BITE monitor requires a series of commands that you can issue on the UNIX command line or through the Terminal Handler.

These commands disable a BITE monitor process:

1. Issue the MML DISPLAY-MON command and note the ID of the BITE monitor process you want to stop.

2. Issue the MML STOP-MON command and specify the monitor’s ID for the command’s ENT argument.

Using the Terminal Handler, you can disable a BITE monitor process while an application is running or after it has stopped.

N O T EIf the application’s registration parameters are set such that the SINAP/SS7 system initiates a BITE monitor process automatically when the application is activated (fmon_ss7 or fmon_ipc set to 1 in the application program), you must disable the monitor process before restarting the application. Otherwise, when the application is restarted, the SINAP/SS7 system will automatically initiate a new monitor process without stopping the first monitor process. To disable automatic activation of a BITE monitor process, fmon_ss7 and fmon_ipc must be set to 0 within the application program. See the SINAP/SS7 Programmer’s Guide (R8052) for more information on BITE.

DISPLAY-MON;current active monitors:

1 ENT=(SS7,,,CLIENT_APPL,PROCESS_1,1),DISP=N,LOG=LOGFILE;



Menu Selection ModeTo stop the BITE monitor from running, select the Display Monitor ID command from the BITE Monitor Commands menu. When the monitor list appears, note the ID of the monitor you want to stop. From the BITE Monitor Commands menu, select the Stop Monitor option and respond to the system prompts to specify the particular BITE monitor you are stopping.

MML Command FormatThe MML command format for the STOP-MON command is:

STOP-MON:ENT=monitor_id;

The monitor_id argument specifies the entity to be stopped. Use the value the START_MON command returns for this argument, or use the DISPLAY_MON command to review all active monitor IDs.

Man Page FormatThe alternative format and man page format for this command is stop-mon.

Reconfiguring bitu to Run in the Real-Time or the Time-Share ModeTo run the BITE Link Test User Part (bitu) process in real-time or time-share mode, you must reconfigure the class and priority of the bitu process in the bite.p3f file. To reconfigure the BITE process, perform the following steps:

1. Log in to UNIX with super-user privileges.

2. Edit the $HOME_SINAP/Bin/bite.p3f file so that the TU bitu line looks like one of the following examples, depending on whether you want to run the process in real-time or time-share mode. Use any standard text editor, such as vi, to edit the file.

• To reconfigure the bitu process to run in real time, edit the TU bitu command line so that the TU bitu line looks like this:

TU bitu -c RT -p 20

• To reconfigure the bitu process to run in time-share mode, edit the TU bitu command line so that the TU bitu line looks like this:

TU bitu -c TS -p 20

Table 4-30 describes the -c and -p options.


Implementing Signaling Link Test Messages

Implementing Signaling Link Test MessagesThis section contains information on performing the following tasks:

• Sending a signaling link test message to a link

• Enabling automatic periodic link testing

• Disabling automatic periodic link testing

Perform these tasks using the BITE Commands and Network Commands menus.

Sending a Signaling Link Test Message to a LinkThe Test Link (TEST-LINK) command tests a signaling link via the test user process (bitu) of the BITE system.

N O T E S1. See the appropriate standards document for the procedure,

depending on the SINAP/SS7 network variant (CCITT, ANSI, China, TTC, or NTT) installed on your system.

Table 4-30. -c and -p Options for bitu

Option Description

-c Specifies the class of scheduling policies to follow: real-time (RT) or time-share (TS). The real-time scheduling policy allows you to control the scheduling of processes by the priority you assign to them. The time-share scheduling policy attempts to allocate central processor unit (CPU) time equitably among processes.

-p Indicates the priority to assign to the bitu process. In the real-time class, a process with a higher priority is given CPU time before processes in other classes. In the time-share class, the priority of a process is one of several factors used to determine when the process will run. Typically, a process with a higher priority is given CPU time before lower-priority processes in this class. On HP-UX operating system, refer to the man page of rtprio for the details of real-time priority. On Solaris operating system, refer to the man page of priocntl for the details of real-time priority. On Stratus ft Linux operating system, refer to the man page of sched_setscheduler for the details of real-time priority (not yet implemented for Stratus ft Linux SINAP bitu). Refer to the man page of setpriority for the details of time-share priority for all systems.



2. Test links in the ANSI, CCITT, and China network variants use the Signaling Link Test (SLT) message. In the NTT and TTC network variants, test links use the Signaling Route Test (SRT) message. Although the procedures and functionality of the SLT and SRT messages are similar, some differences do exist. These are explained in the appropriate standards document.

Menu Selection ModeFor the CCITT, ANSI, and China network variants, select the Test Link option from the BITE Commands menu to test a signaling link. For the TTC and NTT network variants, select the Test Route option. Respond to the system prompts to specify the link to be tested.

MML Command FormatThe MML command format for the TEST-LINK command is:

TEST-LINK:LINK=link;

The link argument specifies the link to be tested. When specifying a link, use its label, such as lnk1.

Executing this command sends a link test message to the specified link. The SINAP/SS7 system sends the command response back to the originator if the link test acknowledgment is received, or times out while receiving the link test acknowledgment.

Man Page FormatThe alternative format and man page format for TEST-LINK is tst-link.

Enabling Automatic Periodic Link TestingPeriodic link testing enables you to configure the SINAP/SS7 system to continually send test messages over a specific link.

The SINAP/SS7 system tests a link by sending a signaling link test (SLT) message over the link. The link’s remote endpoint responds by sending an acknowledgment message to the SINAP/SS7 system. TTC and NTT send a signaling route test acknowledgment (SRTA) message; all other variants send a signaling link test acknowledgment (SLTA) message. If the SINAP/SS7 system receives the acknowledgment message within a specified amount of time, the link passes. Otherwise, the link fails and the SINAP/SS7 system restarts it.

Periodic link testing does not disrupt normal SS7 traffic over a link, nor does it replace the link-alignment testing that the SINAP/SS7 system performs automatically when a link is initialized.



N O T EUnlike other stacks which exchange SLT messages during link initialization, the TTC and NTT stacks do not exchange SRT messages during link initialization.

For the CCITT network variant, the SLT message is considered successful only if the received SLTA meets the following criteria:

• The Signaling Link Code (SLC) identifies the physical signaling link on which the SLTA message was received

• The OPC identifies the signaling point at the other end of the link

• The test pattern is correct

In the CCITT network variant, you can define the SLTM_WITH_NAT10_FOR_G500 environment variable to enable a feature which allows the SINAP node to respond to an SLT with an SLTA only when the received SLT contains the value NAT10 (0x02) in its subservice field (SSF).

When this environment variable is not defined, the SINAP node responds to all received SLT messages with SLTA messages.

The remainder of this section provides instructions for accessing SLT and SRT timers and enabling periodic link testing. The following descriptions are written from the CCITT, ANSI, and China perspective, with TTC and NTT equivalents included in parentheses.

Accessing SLT and SRT TimersTwo timers, SLTT1 and SLTT2 (SRTT10 and SRTT20), specify the time intervals for periodic link testing:

• The SLTT1 (SRTT10) timer specifies the time period within which the SINAP/SS7 system must receive an SLTA (SRTA) message from the link’s remote endpoint in response to an SLT (SRT) message. If the SINAP/SS7 system does not receive an SLTA (SRTA) message from the remote endpoint within the specified interval, the SLTT1 (SRTT10) timer expires, causing the SINAP/SS7 system to send a second SLT (SRT) message. If the remote endpoint again fails to respond before the timer expires, the link fails and the SINAP/SS7 system restarts it.

• The SLTT2 (SRTT20) timer specifies the amount of time between each SLT (SRT) message. When the SLTT2 (SRTT20) timer expires, the SINAP/SS7 system sends an SLT (SRT) message over the link being tested.

You can display and change the timer settings using the TIMER argument within the commands, DISPLAY-SYSTAB and CHANGE-SYSTAB. In the menu selection mode, access these commands by selecting the Display or Change option from the Network Commands menu.



The example shown in Figure 4-52 displays the option (in boldface) as it appears on a SINAP/SS7 Terminal Handler MML command screen:

Figure 4-52. Sample SINAP/SS7 Terminal Handler MML Command Screen

N O T EThe TTC network variant screen displays the values for the SRT timers instead of the SLT values.

Displaying Current SLT or SRT Timer SettingsTo display the current setting of an SLT or SRT timer, issue the MML command, DISPLAY-SYSTAB, and specify the timer you want to display. For example:

DISPLAY-SYSTAB:TABID=SLTTM,TIMER=SLTT1;

or:

DISPLAY-SYSTAB:TABID=SRTTM,TIMER=SRTT10;

Changing Timer SettingsTo change the setting of the SLT or SRT timer, issue the MML command, CHANGE-SYSTAB, and specify the table ID, timer, and the time value to be assigned to the NEWTIME argument. For example,

CHANGE-SYSTAB:TABID=SLTTM,TIMER=SLTT1,NEWTIME=time; CHANGE-SYSTAB:TABID=SLTTM,TIMER=SLTT2,NEWTIME=time;

CHANGE-SYSTAB:TABID=SRTTM,TIMER=SRTT10,NEWTIME=time; CHANGE-SYSTAB:TABID=SRTTM,TIMER=SRTT20,NEWTIME=time;

MML as built is CHANGE-SYSTAB:Specify system table to be modified: 2 : MTP L2 Timers 3 : MTP L3 Timers M or m : MTP Threshold S or s : SCCP Timers T or t : SLT Timers Choice=



You can also include the unit of measure for the time value using an uppercase M (for minutes) or S (for seconds). For example, in the following commands, the time value 1M specifies 1 minute, and 20S specifies 20 seconds.

CHANGE-SYSTAB:TABID=SLTTM,TIMER=SLTT1,NEWTIME=1M; CHANGE-SYSTAB:TABID=SLTTM,TIMER=SLTT2,NEWTIME=20S;

Table 4-31 lists the default values and the range of valid values for the timers.

Enabling Periodic Link TestingTo enable periodic link testing for a SINAP/SS7 link, issue the following MML commands:

1. Issue the MML command, DISPLAY-SYSTAB, to display the current value of the SLTT1 or SLTT2 (SRTT10 or SRTT20) timer. In the menu selection mode, select the Display option from the Network Commands menu and respond to the system prompts to specify the type and the name of the timer.

2. If the current value of the timer is inappropriate, issue the MML command, CHANGE-SYSTAB, to set the timer to the desired time interval for periodic link testing. In the menu selection mode, select the Change option from the Network Commands menu and respond to the system prompts to change the timer interval.

3. Issue the MML command, CHANGE-LINK, as shown in the following example, where link specifies the name of the link for which periodic link testing is to be enabled. For value, specify YES to enable periodic link testing; specify NO to disable periodic link testing. If you specify YES, the SINAP/SS7 system begins periodic link testing of the specified link. (For TTC and NTT, the argument is PERIODIC_SRT instead of PERIODIC_SLT.)

CHANGE-LINK:LINK=link,PERIODIC_SLT=value;

N O T EAn error occurs if you attempt to set the PERIODIC_SLT (PERIODIC_SRT) argument to its current value. For example, if the PERIODIC_SLT argument has already been set to YES, and you specify YES for this argument when you issue the

Table 4-31. Link Testing Timer Default Values

Timer Default Value Range of Valid Values

SLTT1 8 seconds 4–12 seconds

SLTT2 60 seconds 30–90 seconds

SRTT10 10 seconds ------

SRTT20 60 seconds 30–90 seconds



CHANGE-LINK command, an error occurs. To correct the problem, you must reissue the command, specifying a different value for PERIODIC_SLT.

In the menu selection mode, select Change from the Network Commands menu and Change Link from the Change Commands menu and respond to the system prompts to access the link information.

4. Optionally, you can issue the MML command, DISPLAY-LINK, to verify periodic link testing has been enabled for the link. In the menu selection mode, select Display from the Network Commands menu and Display Link from the Display Commands menu and respond to the system prompts.

If periodic link testing has been enabled, the link’s Status column includes the value, T-periodic link test active, as shown in Figure 4-53:

Figure 4-53. Sample Screen Output for Enabled Periodic Link Testing

5. Optionally, you can use the BITE facility to monitor the results of periodic link testing. To do this, set the ENT argument of the MML command, START-MON, as shown in the following example. The START-MON command initiates monitoring. See ‘‘Starting the BITE Monitor” earlier in this chapter.

START-MON:ENT=(SS7,,,BI,TU)&(IPC,,,BI,TU)...;

When the SLTT2 (SRTT20) timer expires, the following types of messages are generated for each link for which periodic link testing has been enabled. You can use the BITE facility’s log-analysis commands to retrieve these messages.

• An inbound IPC MML request from the l3mt process to the bitu process to send an SLT message

LinkName Link LSetName LSet SLC Port Speed ADPC State Status LNK1 1 LSET1 0 1 1 64000 2730 ACTIV iabclrnT

--Link Status Legend--i - installedI - not installeda - availableA - not availableb - not remote blockedB - remote blockedc - not congested C - congested

l - not local inhibitedL - local inhibitedr - not remote inhibitedR - remote inhibitedn - link normalU - status unavailable F - link failed t - no periodic link testT - periodic link test active


Using the Load Control Facility

• An outbound SS7 SLT (SRT) message

• An inbound SS7 SLTA (SRTA) message

• An outbound IPC MML response from the bitu process to the l3mt process

If the adjacent SPC is sending SLT (SRT) messages periodically, the following types of messages generate:

• An inbound SS7 SLT (SRT) message

• An outbound SS7 SLTA (SRTA) message

Disabling Automatic Periodic Link TestingTo terminate periodic link testing, issue the CHANGE-LINK command, specifying NO for the PERIODIC_SLT (PERIODIC_SRT) argument as shown in the following MML command example:

CHANGE-LINK:LINK=link,PERIODIC_SLT=NO;

Using the menu selection mode, build this command by selecting the Change Link option from the Change Commands menu and respond to the system prompts.

Using the Load Control FacilityThe load control facility monitors a TCAP application’s congestion level and activates load control processing automatically when the application experiences overload conditions. For the SINAP/SS7 system to implement load control processing, load control must be enabled at each of the following levels.

• System—The SINAP/SS7 system is enabled to perform load control processing.

• Application—A particular application is enabled to perform load control processing.

• Instance—Individual application instances are enabled to perform load control processing.

After configuring load control parameters for an application using the SETUP-LOAD-CONTROL command, you must issue the ENABLE-LOAD-CONTROL command to initiate load control operation. By default, the ENABLE-LOAD-CONTROL command and the ca_enable_locon() function automatically enable load control at the system and instance levels. To enable load control at the application level, issue the ENABLE-LOAD-CONTROL command and specify the application for which you want to enable load control.

When load control is enabled (at all levels), monitoring of the input and output queues takes effect. When a threshold is exceeded for the length of the input FIFO queue and, if optionally specified, a running count of consecutive output MSUs is delayed beyond a time limit, load control begins. The specified conditions must be met by all instances of a subsystem if group load control was specified at setup. The threshold, delay time, and count limit are all parameters



set using the SETUP-LOAD-CONTROL command (see ‘‘Configuring Load Control Parameters for a TCAP Application’’ in Chapter 3).

If you disable load control at the system level, you cannot enable load control for a particular application until you first re-enable load control at the system level by performing these steps:

• To disable load control at the system level issue the DISABLE-LOAD-CONTROL command with SSN=ALL.

• To re-enable load control at the system level issue the ENABLE-LOAD-CONTROL command with SSN=ALL.

Likewise, if you disable load control for specific application instances, you must also explicitly re-enable load control for those instances. Enabling load control at the application level does not supersede the load control enablement settings for individual application instances. For example, if you disable load control for instances 1, 3, and 5 of an application whose specified SSN is 254, you must explicitly re-enable load control for those instances. Enabling load control for SSN 254 does not enable load control for instances 1, 3, and 5.

Enabling Load Controls for an ApplicationTwo commands activate load controls for an application:

• ENABLE-LOAD-CONTROL

• INVOKE-LOAD-CONTROL

Stratus recommends using the ENABLE-LOAD-CONTROL command. You can issue this command on the UNIX command line or through the Terminal Handler.

The ENABLE-LOAD-CONTROL command initiates load control operation for the specified application. Issuing this command causes the SINAP/SS7 system to begin monitoring the application for overload conditions. During this monitoring stage, load control is active. However, the SINAP/SS7 system does not actively perform load control processing until overload conditions occur.

The INVOKE-LOAD-CONTROL command activates load control processing even if no overload condition exists. For this reason, Stratus recommends not using this command to enable load control processing in a production environment.

For the SINAP/SS7 system to perform load control processing, load control must be enabled at the system, application, and instance levels (see the following list). By default, the ENABLE-LOAD-CONTROL command automatically enables load control at the system and instance levels. You issue the ENABLE-LOAD-CONTROL command to complete the enablement process and enable load control at the application level (that is, you enable load control for a specific application). However, if you disable load control at the system or instance level, you cannot complete the enablement process by simply enabling load control at the application level; instead, you must first re-enable load control at the level for which it was



disabled (system or instance). (For more information, see ‘‘Disabling Load Controls for an Application” later in this chapter.)

• Enabling load control at the system level initiates load control operation for all applications configured for load control. To enable load control at the system level, issue the following command:

ENABLE-LOAD-CONTROL:SSN=ALL;

• Enabling load control at the application level initiates load control operation for all instances of a specific application. To enable load control at the application level, issue the following command as shown in the following example. Specify the SSN of the application (for example, 254) as the value of the SSN argument and specify the value, ALL, for the INSTANCE argument, or omit INSTANCE from the command line:

ENABLE-LOAD-CONTROL:SSN=254,INSTANCE=ALL;

N O T EApplications using enhanced distribution use the application name instead of an SSN.

• Enabling load control at the instance level initiates load control operation for one or more instances of a specific application. To enable load control at the instance level, issue the ENABLE-LOAD-CONTROL command. Specify the SSN of the application as the value of the SSN argument and specify the number of the application instance as the value of the INSTANCE argument. To use this form of the ENABLE-LOAD-CONTROL command, the application must be configured for individual-type operation (see the description of the SETUP-LOAD-CONTROL command’s TYPE argument in ‘‘Configuring Load Control Functionality’’ in Chapter 3).

You cannot configure individual application instances for load control. However, you can enable load control for a subset of the application’s instances, thereby selectively implementing load control processing for specific application instances. For example, suppose you configure an application for load control and then enable load control for instances 1, 3, and 5 only. If all of the application’s instances begin experiencing overload conditions, the SINAP/SS7 system is able to perform load control processing for instance 1, 3, and 5 only.



Menu Selection ModeIn the menu selection mode, select the Load Control option from the Application Commands menu. The Load Control Commands menu appears as shown in Figure 4-54.

Figure 4-54. Load Control Commands Menu

Select the Enable Load Control option to start load control functionality and respond to the system prompts to build and issue the ENABLE-LOAD-CONTROL command.

MML Command FormatThe MML command format for the ENABLE-LOAD-CONTROL command is:

ENABLE-LOAD-CONTROL:SSN=SSN [,INSTANCE=INSTANCE[&INSTANCE...]];

Table 4-32 describes the arguments for the ENABLE-LOAD-CONTROL command.

Table 4-32. ENABLE-LOAD-CONTROL Command Arguments (Page 1 of 2)


SSN Specifies the SSN (in the range 2 to 255) of the application for which you want to enable load control. The application must be configured for load control; however, it need not be running.

Specify ALL (SSN=ALL) to enable load control for all applications configured for load control. You must also specify ALL for the INSTANCE argument, or omit the INSTANCE argument from the ENABLE-LOAD-CONTROL command line.

Note: If the application is registered to use enhanced message distribution, you must specify the 2- to 4-character application name such as DB12, instead of the subsystem number in the SSN field. A CASL function encodes the application name as a zero-filled, right-justified, U32 integer with a value greater than 255. See the SINAP/SS7 Programmer’s Guide (R8052) for more information.

Load Control Commands

1. Setup Load Control2. Enable Load Control3. Disable Load Control4. Invoke Load Control5. Exit Load Control6. Display Load Control



Man Page FormatThe alternative format and man page format for ENABLE-LOAD-CONTROL is enable-lc.

Sample Command UsageThe following command enables load control for all applications configured for load control:

ENABLE-LOAD-CONTROL:SSN=ALL;

The following commands enable load control for all instances of the application whose SSN is 254:

ENABLE-LOAD-CONTROL:SSN=254;ENABLE-LOAD-CONTROL:SSN=254,INSTANCE=ALL;

The following command enables load control for instances 1, 3, and 5 of the application whose SSN is 254:

ENABLE-LOAD-CONTROL:SSN=254,INSTANCE=1&3&5;

Invoking Load Controls for an ApplicationThe Invoke Load Control (INVOKE-LOAD-CONTROL) command causes the SINAP/SS7 system to start load control processing for the specified application, even if the application is not experiencing overload conditions. The SINAP/SS7 system continues to perform load

INSTANCE Specifies the number of the application instance for which you want to enable load control. For the value of this argument, you can specify an instance number, or the keyword ALL.

If you specify SSN=ALL, you can omit the INSTANCE argument from the command line, which is the same as specifying INSTANCE=ALL. Specify an instance number to enable load control for a specific application instance. You must have specified the value INDIV for the SETUP-LOAD-CONTROL command’s TYPE argument, and the instance must be running.

You can specify up to 16 instances, using an ampersand (&) to separate each instance (for example, INSTANCE=1&3&5). At least one of these instances must be running.

Specify ALL (INSTANCE=ALL) to enable load control for all instances of the application. The application need not be running.

Table 4-32. ENABLE-LOAD-CONTROL Command Arguments (Page 2 of 2)




control processing for the application until you issue the DISABLE-LOAD-CONTROL or EXIT-LOAD-CONTROL command, or terminate the application.

N O T EStratus does not recommend using the INVOKE-LOAD-CONTROL command for normal operation in a production environment. Instead, use the ENABLE-LOAD-CONTROL command, which allows the SINAP/SS7 system to activate load control processing automatically when the application experiences overload conditions.

Menu Selection ModeAccess the INVOKE-LOAD-CONTROL command from the Load Control Commands menu and respond to the system prompts.

MML Command FormatThe MML command format for the command is:

INVOKE-LOAD-CONTROL:SSN=SSN [,INSTANCE=INSTANCE[&INSTANCE]];

Table 4-33 describes the arguments for the INVOKE-LOAD-CONTROL command.

Table 4-33. INVOKE-LOAD-CONTROL Command Arguments (Page 1 of 2)


SSN Specifies the SSN (in the range 2 to 255) of the application for which you want the SINAP/SS7 system to begin performing load control processing. The application must be configured for load control and it must be running.

Specify ALL (SSN=ALL) to enable load control for all applications configured for load control. If you do not specify the INSTANCE argument, this command is executed on all instances of the application, regardless of whether you specified the value GROUP or INDIV for the SETUP-LOAD-CONTROL command’s TYPE argument.

Note: If the application is registered to use enhanced message distribution, you must specify the 2- to 4-character application name such as DB12 instead of the subsystem number in the SSN field. A CASL function encodes the application name as a zero-filled, right-justified, U32 integer with a value greater than 255. See the SINAP/SS7 Programmer’s Guide (R8052) for more information.



Man Page FormatThe alternative format and man page format for INVOKE-LOAD-CONTROL is invoke-lc.

Example Command UsageThe following commands begin performing load control processing for all instances of the application whose SSN is 254:

INVOKE-LOAD-CONTROL:SSN=254;INVOKE-LOAD-CONTROL:SSN=254,INSTANCE=ALL;

The following command begins performing load control processing for instances 1, 3, and 5 of the application whose SSN is 254.

INVOKE-LOAD-CONTROL:SSN=254,INSTANCE=1&3&5;

INSTANCE Specifies the number of the application instance for which you want the SINAP/SS7 system to begin performing load control processing. For the value of this argument, you can specify an instance number, or the keyword, ALL. You can also omit the INSTANCE argument. In this case, load control processing is initiated for all instances of the application, regardless of whether you specified the value, GROUP, or INDIV, for the SETUP-LOAD-CONTROL command’s TYPE argument.

Specify an instance number if you want the SINAP/SS7 system to begin performing load control processing for a specific application instance. You must have specified the value, INDIV, for the SETUP-LOAD-CONTROL command’s TYPE argument, and the instance must be running.

You can specify up to 16 instances, using an ampersand (&) to separate each instance (for example, INSTANCE=1&3&5). At least one of the instances must be running.

INSTANCE(cont.)

Specify ALL (INSTANCE=ALL) if you want the SINAP/SS7 system to begin performing load control processing for all instances of the application. The application must be running, but individual application instances need not be running. You can specify ALL regardless of whether you specified the value as GROUP or INDIV for the SETUP-LOAD-CONTROL command’s TYPE argument.

Table 4-33. INVOKE-LOAD-CONTROL Command Arguments (Page 2 of 2)




Displaying Load Control Statistics for an ApplicationThe Display Load Control (DISPLAY-LOAD-CONTROL) command displays load control statistics similar to the sample display shown in Figure 4-55 for the specified application. User entries are in bold type.

Figure 4-55. Sample DISPLAY-LOAD-CONTROL Command Output

The sample shows that the application whose SSN is 249 has two instances configured for load control. The first instance (1) has a process identification number (PID) of 16762. This instance is currently active and is enabled for load control. The second instance (3) has a PID of 16765. This instance is currently active and is not enabled for load control. Likewise, the application whose SSN is 255 has three instances configured for load control (1, 5, and 12). Their PIDs are 5547, 10001, and 17729, respectively.

DISPLAY-LOAD-CONTROL:SSN=ALL;command completed

System enabled for Load Control

SSN Type Thresh Delay Count Abate Notify State Inst PID246 INDIV 150 2500 50 1500 Y E N 0 248 GROUP 150 2500 50 1500 N D N 0249 INDIV 150 2500 50 1500 N E R 2 1 E A 16762 3 D R 16765251 GROUP 125 2000 30 1000 Y D R 5252 GROUP 125 2000 30 1000 Y E R 5253 GROUP 100 1500 25 750 N E A 10254 GROUP 100 1500 20 750 Y E F 3255 INDIV 125 2000 30 1000 Y E R 3 1 E R 5547 5 E F 10001 12 D R 17729

--Load Control Status Legend--D = Load Control Disabled E = Load Control EnabledN = Not Running R = Running w/o Load ControlA = Automatic Load Control F = Forced Load Control



Information similar to that in the sample screen is displayed for each application configured for load control. Table 4-34 describes the information displayed in each column. Table 4-34. Column Information for Load Control Applications (Page 1 of 2)

Column Description

SSN Displays the SSN value you assigned to the SETUP-LOAD-CONTROL command arguments.

Type Displays the TYPE value you assigned to the SETUP-LOAD-CONTROL command arguments.

Thresh Displays the THRESHOLD value you assigned to the SETUP-LOAD-CONTROL command arguments.

Delay Displays the DELAY value you assigned to the SETUP-LOAD-CONTROL command arguments.

Count Displays the COUNT value you assigned to the SETUP-LOAD-CONTROL command arguments.

Abate Displays the ABATEDELAY value you assigned to the SETUP-LOAD-CONTROL command arguments.

Notify Indicates whether the application or application instance is to be notified when load control is initiated and terminated and load control processing is activated and deactivated.

State Indicates whether load control is currently enabled and active. The Load Control Status Legend at the bottom of the screen describes the values that appear in this column.

Note: In the legend, the term Automatic Load Control indicates that you issued the ENABLE-LOAD-CONTROL command for an application or application instance, which allows the SINAP/SS7 system to activate load control processing automatically when the application experiences overload conditions. The term Forced Load Control indicates you issued the command INVOKE-LOAD-CONTROL for an application or application instance, which causes the SINAP/SS7 system to begin performing load control processing, even when the application is not experiencing overload conditions.

Inst Identifies the number of instances of the application that are configured for load control.



Menu Selection ModeAccess the DISPLAY-LOAD-CONTROL command from the Load Control Commands menu and respond to the system prompts.

MML Command FormatThe MML command format for the DISPLAY-LOAD-CONTROL command is:

DISPLAY-LOAD-CONTROL:SSN=SSN [,PRINT=PRINT],[FILE=file];

Table 4-35 describes the arguments for the DISPLAY-LOAD-CONTROL command.

PID Used only when an application is configured for load control individual-type operation (see the description of the SETUP-LOAD-CONTROL command’s TYPE argument in this guide). In this case, the PID column indicates the process identification (PID) number that the SINAP/SS7 system assigned to each application instance, and the Notify column indicates the number of each instance.

Table 4-35. DISPLAY-LOAD-CONTROL Command Arguments (Page 1 of 2)


SSN Specifies the SSN (in the range 2 to 255) of the application whose load control statistics you want to display. The application must be configured for load control; however, the application need not be running.

Specify ALL (SSN=ALL) to display statistics for all applications configured for load control. Note: If the application is registered to use enhanced message distribution, you must specify the 2- to 4-character application name such as DB12 instead of the subsystem number in the SSN field. A CASL function encodes the application name as a zero-filled, right-justified, U32 integer with a value greater than 255. See the SINAP/SS7 Programmer’s Guide (R8052) for more information.

Table 4-34. Column Information for Load Control Applications (Page 2 of 2)

Column Description



Man Page FormatThe alternative format and man page format for DISPLAY-LOAD-CONTROL is display-lc.

Sample Command UsageThe following command displays load control statistics for all instances of the application whose SSN is 254. It also sends command output to the system’s default printer.

DISPLAY-LOAD-CONTROL:SSN=254,PRINT=YES;

The following command output displays on the terminal only:

DISPLAY-LOAD-CONTROL:SSN=254,PRINT=NO;

The following command displays load control statistics for all instances of all applications configured for load control. It also sends command output to the printer LASER.

DISPLAY-LOAD-CONTROL:SSN=ALL,PRINT=LASER;

Disabling Load Controls for an ApplicationThe SINAP/SS7 system automatically terminates load control processing when the application finishes processing all MSUs on its input queue and on the last-in, first-out (LIFO) queue created at the onset of load control processing. However, load control is persistent, and once set up for an SSN or application it stays even when the application terminates or SINAP is restarted. To remove load control settings for an application, use one of the following commands:

PRINT Specifies whether to send command output to both a printer and the terminal. This argument is optional. Specify one of the following values:

• YES sends command output to the terminal and to the system’s default printer.

• NO sends command output to the terminal only.

• PRINTER_ID sends command output to the terminal and to the specified printer.


Table 4-35. DISPLAY-LOAD-CONTROL Command Arguments (Page 2 of 2)




• Issue the DISABLE-LOAD-CONTROL command to terminate load control completely. The SINAP/SS7 system does not return to monitoring the application for overload conditions. To reactivate load control, you must re-enable load control for the application.

• Issue the SETUP-LOAD-CONTROL command with TYPE=DELETE to reconfigure the application and remove load control functionality. The application continues to execute. However, it is no longer configured for load control.

N O T EWhen you use either of these methods to terminate load control, the SINAP/SS7 system extracts MSUs from the application’s LIFO queue in first-in, first-out (FIFO) fashion and appends them to the application’s input queue. The SINAP/SS7 system discards any MSUs that would cause the input queue to overflow.

The Disable Load Control (DISABLE-LOAD-CONTROL) command or ca_disable_locon() terminates load control completely at the system, application, or instance level. SINAP does not return to monitoring the application for overload conditions. To reactivate load control, you must re-enable load control for the application. You can access this command through the DISABLE option of the load control menu.

You can disable load control at the system level, the application level, or the instance level in the following ways:

• Disabling load control at the system level terminates load control operation for all applications configured for load control. In the case of a critical situation this allows an operator or control program to disable load control for all applications by using a single command or function call. To disable load control at the system level, issue the DISABLE-LOAD-CONTROL command or ca_disable_locon() and specify the value ALL for the SSN argument.

N O T EAfter disabling load control at the system level, you must re-enable load control at the same level before you can enable load control for an individual application. (You re-enable load control at the system level by issuing the ENABLE-LOAD-CONTROL command and specifying the value ALL for the SSN argument.)

• Disabling load control at the application level terminates load control operation for all instances of a specific application. To disable load control at the application level, issue the DISABLE-LOAD-CONTROL command or ca_disable_locon(). Specify the SSN of the application as the value of the SSN argument and specify the value ALL for the INSTANCE argument, or omit INSTANCE from the command line.



• Disabling load control at the instance level terminates load control operation for one or more instances of an application. To disable load control at the instance level, issue the DISABLE-LOAD-CONTROL command or ca_disable_locon(). Specify the SSN of the application as the value of the SSN argument and specify the number of the application instance as the value of the INSTANCE argument. To use this form of the DISABLE-LOAD-CONTROL command or ca_disable_locon(), the application must be configured for individual-type operation. (See the description of the ca_disable_locon() TYPE argument in this guide.)

N O T E S1. For an instance, disabling load control at any level disables

load control for that instance.

2. When an application stops running, load control cancels the disablement settings of individual application instances.

3. After disabling load control for specific application instances, you must re-enable load control for those same instances. Enabling load control at the application level does not override the enablement settings for individual application instances. For example, the following command disables load control for instances 1, 3, and 5 of the application whose SSN is 254.

DISABLE-LOAD-CONTROL:SSN=254:INSTANCE=1&3&5

4. Issuing the command, ENABLE-LOAD-CONTROL:SSN=254, (which enables load control for all instances of SSN 254) does not re-enable load control for instances 1, 3, and 5 of SSN 254. To re-enable load control for those instances, you must issue the following command.

ENABLE-LOAD-CONTROL:SSN=254:INSTANCE=1&3&5

If you issue the DISABLE-LOAD-CONTROL command or ca_disable_locon() while the SINAP/SS7 system is performing load control processing for an application, the SINAP/SS7 system extracts MSUs from the application’s LIFO queue in FIFO fashion and appends them to the application’s input queue. The SINAP/SS7 system discards MSUs that have been on the application’s LIFO queue longer than the time defined by the SETUP-LOAD-CONTROL command or ca_disable_locon() ABATEDELAY argument. (See ‘‘Configuring Load Control Parameters for a TCAP Application’’ in Chapter 3 and the SINAP/SS7 Programmer’s Guide (R8052) for how to configure load control parameters for an application.) The SINAP/SS7 system also discards any MSUs that would cause the application’s input queue to overflow.



Menu Selection ModeSelect the Disable Load Control option from the Load Control Commands menu to disable load control for the system, application, or instance. Respond to the system prompts to specify the SSN or application for which you are terminating load control.

MML Command FormatThe MML command format for the DISABLE-LOAD-CONTROL command is:

DISABLE-LOAD-CONTROL:SSN=SSN [,INSTANCE=INSTANCE[&INSTANCE...]];

Table 4-36 describes the arguments for the DISABLE-LOAD-CONTROL command.

Table 4-36. DISABLE-LOAD-CONTROL Command Arguments


SSN Specifies the SSN (in the range 2 to 255) of the application for which you want to disable load control. The application need not be running. Specify ALL (SSN=ALL) to disable load control for all applications configured for load control. You must also specify ALL for the INSTANCE argument, or omit the INSTANCE argument from the DISABLE-LOAD-CONTROL command line.


INSTANCE Specifies the number of the application instance for which you want to disable load control. For the value of this argument, you can specify an instance number, or the keyword, ALL.

If you specify SSN=ALL, you can omit the INSTANCE argument from the command line, which is the same as specifying INSTANCE=ALL.

Specify an instance number to disable load control for a specific application instance. You must have specified INDIV for the SETUP-LOAD-CONTROL command’s TYPE argument, and the instance must be running. You can specify up to 16 instances, using an ampersand (&) to separate each instance (for example, INSTANCE=1&3&5). At least one of these instances must be running.

INSTANCE(cont.)

Specify ALL (INSTANCE=ALL) to disable load control for all instances of the application. The application need not be running.



Man Page FormatThe alternative format and man page format for DISABLE-LOAD-CONTROL is disable-lc.

Sample Command UsageThe following command disables load control for all applications configured for load control. (For important information about disabling load control for all applications, see the description section earlier in this command description.)

DISABLE-LOAD-CONTROL:SSN=ALL;

The following commands disable load control for the application whose SSN is 254:

DISABLE-LOAD-CONTROL:SSN=254;DISABLE-LOAD-CONTROL:SSN=254,INSTANCE=ALL;

The following command disables load control for instances 1, 3, and 5 of the application whose SSN is 254. (For important information about disabling load control for specific application instances, see the description section earlier in this command description.)

DISABLE-LOAD-CONTROL:SSN=254,INSTANCE=1&3&5;

Deactivating Load Controls for an ApplicationThe Exit Load Control (EXIT-LOAD-CONTROL) command deactivates load control processing for the specified application.

N O T EYou can issue this command only if you used the INVOKE-LOAD-CONTROL command to invoke load control processing for the application; otherwise, an error occurs. After this command executes, load control is still enabled. Therefore, the SINAP/SS7 system returns to monitoring the application for overload conditions. To completely terminate load control operation, you must issue the DISABLE-LOAD-CONTROL command.

Executing the EXIT-LOAD-CONTROL command while the SINAP/SS7 system is performing load control processing causes the SINAP/SS7 system to extract MSUs from the LIFO queue in FIFO fashion and append them to the application’s input queue. The SINAP/SS7 system discards MSUs that have been on the LIFO queue longer than the time defined by the SETUP-LOAD-CONTROL command’s ABATEDELAY argument. The SINAP/SS7 system also discards any MSUs that would cause the input queue to overflow.



N O T EWhen you use the EXIT-LOAD-CONTROL command to deactivate load control processing, the SINAP/SS7 system does not check for overload conditions until it processes the next incoming MSU. If this functionality is unacceptable for your application, then do not issue the INVOKE-LOAD-CONTROL command to activate load control processing for the application.

Menu Selection ModeAccess the EXIT-LOAD-CONTROL command from the Load Control Commands menu and respond to the system prompts to stop load control for a specific application.

MML Command Format The MML command format for the EXIT-LOAD-CONTROL command is:

EXIT-LOAD-CONTROL:SSN=SSN [,INSTANCE=INSTANCE[&INSTANCE]];

Table 4-37 describes the arguments for the EXIT-LOAD-CONTROL command.

Table 4-37. EXIT-LOAD-CONTROL Command Arguments (Page 1 of 2)


SSN Specifies the SSN (in the range 2 to 255) of the application for which you want to deactivate load control processing. The application must be running. If you do not specify the INSTANCE argument, the command is executed on all instances of the application, regardless of whether you specified the value GROUP or INDIV for the SETUP-LOAD-CONTROL command’s TYPE argument



Maintaining Connection-Oriented Services

Man Page FormatThe alternative format and man page format for EXIT-LOAD-CONTROL is exit-lc.

Sample Command UsageThe following commands deactivate load control processing for all instances of the application whose SSN is 254:

EXIT-LOAD-CONTROL:SSN=254;EXIT-LOAD-CONTROL:SSN=254,INSTANCE=ALL;

The following command deactivates load control processing for instances 1, 3, and 5 of the application whose SSN is 254:

EXIT-LOAD-CONTROL:SSN=254,INSTANCE=1&3&5;

Maintaining Connection-Oriented ServicesConnection-oriented services enable an application to establish and maintain a connection with another application for the purpose of exchanging data. A connection is a logical communication path associated with both applications. The CCITT and China network variants support connection-oriented services.

To use connection-oriented services, a CCITT or China network variant application running on the SINAP/SS7 system (the local application) must assign certain values to specific fields in its CA_REG global variable. These values tell the SINAP/SS7 system that the application will use connection-oriented services rather than connectionless services.

INSTANCE Specifies the number of the application instance for which you want to deactivate load control processing. For the value of this argument, you can specify an instance number, or the keyword ALL.

Specify an instance number to deactivate load control processing for a specific application instance. You must have specified the value INDIV for the SETUP-LOAD-CONTROL command’s TYPE argument, and the instance must be running. You can specify up to 16 instances, using an ampersand (&) to separate each instance (for example, INSTANCE=1&3&5). At least one instance must be running.

Specify ALL (INSTANCE=ALL) to deactivate load control processing for all application instances. The application must be running, but individual application instances need not be running. You can specify ALL regardless of whether you specified the value as GROUP or INDIV for the SETUP-LOAD-CONTROL command’s TYPE argument.

Table 4-37. EXIT-LOAD-CONTROL Command Arguments (Page 2 of 2)



Chapter 3, ‘‘Software Configuration,” provides a complete description of the connection-oriented features and describes how to configure the SINAP/SS7 environment variables to activate these services. These variables must be activated before starting the SINAP/SS7 system.

Maintaining Information on Active Connections The SINAP/SS7 system stores information on active connections in a segment of shared memory designated the local reference memory (LRM). The LRM is an array of sccp_lrm_t structures, each containing information about a single active connection between a local and remote application. The LRM entry contains information such as the SSN of the local and remote applications, the connection ID, and the state of the connection.

Each LRM entry is assigned a local reference number (LRN), defined as an sccp_lrn_t structure, which serves as an index into the LRM array. When a connection is established, the connection ID is assigned to an LRN to tie the connection to a particular entry in the LRM array. A single LRM exists for each connection. The LRM contains two LRNs: a single source (or local) LRN and a destination (or remote) LRN.

N O T EThe sccp_lrm_t and sccp_lrn_t structures are internal to the SINAP/SS7 system. They are defined in the sccp.h include file.

Checking LRM and LRN StatusThe sy utility displays LRM and LRN information which can be used to identify an active connection. The example in Figure 4-56 shows the sy command that dumps the LRM and the command’s output.

Figure 4-56. Sample #sc,lrm Command Output

$ #sc,lrm

SCCP LRM Table (active entries):LRM#1 state:8 conn_id:1 OPC:2730 class:3 init_credit:4 credit:8 sls:1 ak_used:0 ed_used:0 source_lrn:0d.0003 dest_lrn:0x04000d ssn:233 grey_book:0LRM#2 state:7 conn_id:2 OPC:2730 class:3 init_credit:8 credit:8 sls:11 ak_used:0 ed_used:0 source_lrn:0d.0004 dest_lrn:0x03000d ssn:234 grey_book:0Total LRM’s 1025, LRM’s used 2



The sy utility also displays information about LRNs, which is used to identify an active connection. The example in Figure 4-57 shows the sy command that displays information about all active (connected) LRNs.

Figure 4-57. Sample #sc,lrn Command Output

The example in Figure 4-58 shows the sy command that displays information about a specified active LRN (LRN 1).

Figure 4-58. Sample #sc.lrn,1 Command Output

N O T E S1. In the above sample, the LRN#n field indicates the index

used to identify this particular LRN structure within the array of LRN structures.

2. The 0d.000n field indicates the actual LRN value used in messages sent over this connection.

3. The CONN_ID=n field indicates the connection identifier for the connection. If this value is 0, the connection identifier is not being used.

4. The frozen(delta)=n field indicates the time (in seconds) remaining on the LRN’s Tguard timer. This value is 0 while the connection is active.

$ #sc,lrn

sccp lrn Table (active entries):LRN#1, 0d.0001, CONN_ID=1, frozen(delta)=0LRN#2, 0d.0002, CONN_ID=2, frozen(delta)=0Total LRN’s 2500, Connected LRN’s 2, Frozen LRN’s 0

$ #sc,lrn,1

sccp lrn Table (active entries):LRN#1, 0d.0001, CONN_ID=1, frozen(delta)=0



Inactive Connections and Releasing LRNs Applications using a connection might not immediately be aware that the connection was released. Therefore, when a connection is released, the connection’s LRN remains unavailable (or frozen) for a certain amount of time. During this time period, which is defined by the STGUARD timer, the LRN cannot be assigned to another connection. Freezing an LRN ensures that an LRN being used for one connection is not reassigned to another connection before either application realizes the original connection has been released. For example, suppose two applications are communicating over a connection identified by a particular LRN. Now suppose the connection is released and, before either application realizes the connection has gone away, the connection’s LRN is reassigned to another connection. In this case, either application might attempt to send a response over a connection that no longer exists.

After the amount of time specified by STGUARD, the LRN becomes available and can be assigned to another connection. Note that a connection’s LRN is frozen even when the connection is subsequently released by the local application or refused by the remote application.

A connection’s LRN is not released when the connection is released. Instead, the LRN is frozen for the amount of time defined by the STGUARD timer. During this time period, the LRN cannot be assigned to another connection, even if it means that the connection cannot be established because no more LRNs are available.

You use the release_lrn command to release frozen LRNs so they can be assigned to other connections. The command can also display LRN statistics, such as the total number of LRNs available, the number of LRNs currently being used, and the number of frozen LRNs.

To issue the release_lrn command, you must be logged in to UNIX as root with super-user privileges or you must be logged in as sinap. You issue the command at the UNIX command prompt.

C A U T I O NIssue the release_lrn command only in emergency situations, when it would otherwise be necessary to reboot the SINAP/SS7 system. For example, issue the command if the system experiences a number of link set failures, each of which results in a frozen LRN.

UNIX Command FormatThe release_lrn command can only be executed at the UNIX prompt by a user with SINAP/SS7 execution privileges. The command format is:

release_lrn [number_of_lrns]



The release_lrn command has the argument, number_of_lrns, which specifies the number of LRNs to release, from 1 to the maximum number of LRNs. To display the current LRN statistics, specify the value 0, or omit this argument from the command line.

• If the value you specify is greater than the total number of LRNs allocated for the SINAP/SS7 node, the command releases all currently frozen LRNs.

• If the value you specify is less than the total number of frozen LRNs, the command releases the LRNs with the least amount of time remaining on their STGUARD timer. This means that LRNs that have been frozen the longest are released first.

Sample UsageThe sample in Figure 4-59 shows one use of the release-lrn command to provide LRN table statistics.

Figure 4-59. Sample release_lrn Command Output

In the sample, the fields in the command output have the following meanings:

• The Total LRN’s field indicates the total number of LRNs allocated for all applications running on the SINAP/SS7 node.

• The Connected LRN’s field indicates the number of LRNs currently assigned to active connections.

• The Frozen LRN’s field indicates the number of frozen LRNs. These LRNs currently are not assigned to an active connection but are not yet available to assign to another connection.

$ release_lrn

SCCP LRN Table StatisticsTotal LRN’s 2500, Connected LRN’s 0, Frozen LRN’s 26



The sample shown in Figure 4-60 releases 25 frozen LRNs. Note that the LRN statistics are displayed before and after the LRNs are released.

Figure 4-60. Sample release_lrn 25 Command Output

Displaying and Changing Connection-Oriented Timers After the environment variables for connection-oriented services are enabled, start the SINAP/SS7 system. The system can now connect one application to another application to exchange data. The SCCP connection-oriented timers define the amount of time allowed to perform a specific connection-oriented task (for example, the timer, STCONEST defines the amount of time allowed to establish a connection between applications). Table 4-38 presents information about the SCCP connection-oriented timers.

N O T EIn the table, the column labeled “ITU-T (CCITT) Timers” presents the name of the timer as it is referred to in the 1993 ITU-T (CCITT) recommendation for SCCP. Note that both the CCITT and China network variants use the ITU-T timers. The column labeled “SCCP Timer Name” presents the name of the corresponding SINAP/SS7 timer.

Table 4-38. SCCP Connection-Oriented Timers

ITU-T (CCITT and China variants) Timer

SCCP Timer Name

Range of Valid Values

Description

T(conn est) STCONEST 1–2 minutes Connection establishment timer

$ release_lrn 25

SCCP LRN Table StatisticsTotal LRN’s 2500, Connected LRN’s 0, Frozen LRN’s 26 ** CAUTION ** Releasing frozen LRN’s before expiration of guard timer

SCCP LRN Table Statistics after the thawTotal LRN’s 2500, Connected LRN’s 0, Frozen LRN’s 1



39

* The value of the STIAR timer must be greater than the value of the STIAS timer.

The SINAP/SS7 system tables store the values of the SCCP connection-oriented timers. You access these system tables via the MML commands, DISPLAY-SYSTAB and CHANGE-SYSTAB. For detailed information about these commands, see ‘‘Displaying the MTP and SCCP System Tables” and ‘‘Changing Timers and Link Congestion Threshold Settings” in this chapter.

When you issue the DISPLAY-SYSTAB or CHANGE-SYSTAB command to access an SCCP connection-oriented timer, specify the value, SCCPTM, for the TABID argument and specify the SCCP timer name (from the preceding table) for the TIMER argument. The following examples show sample commands for accessing SCCP connection-oriented timers.

T(iar) STIAR 3–6 minutes Inactivity timer for inbound messages. The value of the STIAR timer must be greater than the STIAS timer.

T(ias) STIAS* 1–2 minutes Inactivity timer for outbound messages. The value of the STIAS timer must be less than the value of the STIAR timer.

T(reset) STRESET 10–20 seconds

Amount of time to wait for a reset confirm message

T(rel) STREL 10–20 seconds

Amount of time to wait for a release complete message after a disconnect

T(interval) STRELINT 0–60 seconds Total amount of time to repeat the release message

T(repeat rel) STRELREP 0–20 seconds Amount of time between each repeated release message

T(guard) STGUARD 8–16 minutes Amount of time to hold an LRN before assigning it to another connection

Table 4-38. SCCP Connection-Oriented Timers

ITU-T (CCITT and China variants) Timer

SCCP Timer Name


Description


Downloading Link Configuration Changes in the /etc/SS7links File

• To display the values of all SCCP connection-oriented timers, issue the command:

DISPLAY-SYSTAB:TABID=SCCPTM:TIMER=ALL;

• To change the value of the STRELINT timer, issue the command:

CHANGE-SYSTAB:TABID=SCCPTM:TIMER=STRELINT:NEWTIME=40S;

Downloading Link Configuration Changes in the /etc/SS7links File

You can change the link configuration after the initial configuration, but you should be aware of some potential problems. For example, if you remove a link from the SS7links file, it is removed from the entire system. Or, if you add links, you must first install the appropriate hardware for the links, then issue the appropriate UNIX commands to run the installation procedures for the hardware.

If you add, modify, or delete SINAP/SS7 links after setting up your initial configuration, the changes will not take effect until you reboot the system or issue the sinap_update command to update SINAP/SS7 link configuration information.

The sinap_update command instructs the ss7dmn process to read the /etc/SS7links file, which contains SINAP/SS7 link configuration information. Execute the sinap_update command from a UNIX prompt.

See Chapter 2, ‘‘Performing Basic Tasks,” for information about the ss7dmn process and the commands to start and update the SINAP/SS7 system configuration.

Refer to SINAP/SS7 Installation Guide (R8060) for detailed information about how to manually configure SS7 links for specific SS7 card and operating system.


Chapter 5 Alarms, Events, and Error

Messages5-

The SINAP/SS7 system issues alarms and events. An event is an unusual occurrence that might or might not result in an error. Trouble Management logs every software event in the Software Notebook and every hardware or network event in the Alarm History log. The category and subcategory of the event determine the file to which an event is logged.

N O T EAlarms and events can also be configured to be logged to the system log file: For the HP-UX operating system: /var/adm/syslog/syslog.log. For Solaris operating system: /var/adm/messages. For Stratus ft Linux operating system: /var/log/messages.

An alarm is an error message that results from a particular command or system event. Alarms are identified according to the SINAP/SS7 components that detect them.

See Appendix I, “List of Alarm and Event Messages,” for a listing of SINAP/SS7 alarm and event messages.

N O T ETTC does not support the use of the following SCCP Management (SCMG) messages: Subsystem Out-of-Service Request (SOR), Subsystem Out-of-Service Grant (SOG), Subsystem Allowed (SSA), Subsystem Prohibited (SSP), and Subsystem Status Test (SST). Therefore, TTC does not support the generation of the alarms arising from receipt of the messages. Because TTC does not use SST messages, it does not support the following alarm:

SCMG: Error sending SST to PC: %d errno: %d/n

Alarms, Events, and Error Messages 5-1

Alarm Format

Alarm FormatAn alarm consists of the following components:

• Originator information specifies the entity that detected the alarm. In Figure 5-1, the first line contains the data N1, M1, NM, TM. This indicates that the process on the default node (N1) and default module (M1) of Trouble Management (TM) within Node Management (NM) detected the alarm.

• Alarm information gives the date and time of the alarm, its class, severity, and color. In Figure 5-1, the first alarm has a class of 4. It is a critical alarm requiring immediate action, and its color is 4 or red. (See Table 5-5 later in this chapter for information about alarm classes, severity, and colors.)

• Alarm data is in the form of an ASCII string that explains why the alarm was generated. In Figure 5-1, the last line of the second alarm contains the line, Health check timeout, pid = 471, indicating that the alarm was sent because of a health check time out for process ID 471.

Figure 5-1 shows two sample alarms.

Figure 5-1. Sample Alarm Format

Alarm Notification and Severity All processes that are registered to receive a specific alarm category and type receive alarm notification. By default, SINAP/SS7 alarm messages are written to the following file (where mmdd is the system date):

$SINAP_HOME/Logs/system/ALMmmdd

N1,M1,NM,TM, 1992-08-17 11:46:25, Class = 4, Critical Alarm - Immediate Action Required, Color = 4 **** Process NM,NI (pid=5667) died..., signal=9

Trouble Notification: N1,M1,NM,TM, 1992-07-23 21:57:11, Class = 2, Minor Alarm - Repairs Required, Color = 2 Health check timeout, pid = 471


Alarms and Software Notebook Events

Alarms and Software Notebook EventsTo determine which subsystem is reporting an alarm, check the errno values for an accompanying error message. Table 5-1 describes possible values for errno, the category of this errno number, and where to find an explanation of it.

See Appendix C of the SINAP/SS7 Programmer’s Guide (R8052) for a list and explanation of these types of errors. For ISUP errors, see the SINAP/SS7 ISDN User Part (ISUP) Guide (R8053).

Displaying Alarm History Log EntriesThe MML Report Alarm (REPORT-ALARM) command allows you to view a report for the hardware alarms and the responses to those alarms that occurred on a specific date.

Menu Selection ModeSelect the Report Alarm option from the Systems Commands menu and respond to the system prompts to specify the date for which you want to view the Alarm History Log.

MML Command FormatThe MML command format for the REPORT-ALARM command is:

REPORT-ALARM:DATE:DATE=[CC]YY-MM-DD, FILE=file ;

Table 5-1. errno Values

errno Range Category

1 through 256 UNIX system and driver errors

1000 through 6999 CASL errors, including:• Network Management errors—1000 through 1999

• CASL errors—2000 through 2999

• TCAP errors—3000 through 3999

• SCCP errors—4000 through 4999

• MTP errors—5000 through 5999

• BITE errors—6000 through 6999

7000 through 7999 Client application errors

8000 through 8999 ISUP errors



Table 5-2 describes the arguments for the REPORT-ALARM command.

Man Page FormatThe alternative format and man page format for REPORT-ALARM is report-alarm.

Table 5-2. REPORT-ALARM Command Arguments


[CC]YY Specifies the century and year, for example, 1998. The century is an optional entry and valid values are either 19 or 20. Year ranges are 80–99 when Century=19, and 00 through 38 when Century=20. For example, you can enter a two-digit year, 98, or, optionally, the complete year, 1998.

MM Specifies the month, for example, 01. Valid values are 01 through 12.

DD Specifies the day, for example, 15. Valid values are 01 through 31.




Sample DisplayThe following sample displays output for the REPORT-ALARM command for January 15, 1998.

Node Management Software Notebook Events and MessagesThe Node Management Software Notebook is a log of software events and error messages. The SINAP_LOG_SIZE environment variable defines the size of the Software Notebook (and the Alarm Log) in bytes. The default value is 1,000,000 bytes.

You can access the Software Notebook using the MML commands, REPORT-NBOOK, REPORT-ALARM, and REPORT-MALL. See Chapter 4, ‘‘System Operation and Maintenance,” for a description of how to handle log measurements and change log purge days. See Appendix I, “List of Alarm and Event Messages,” for a description of errors, messages, and suggested solutions.

The following sample program logs an error message to the Software Notebook.

/**Application should define its own category and*sub-category. This is for demonstration purposes*only.*/sprintf(buff,”sending event of death of a

M REPORT-ALARM:DATE=1998-01-15;command completed

Report Alarm:

Trouble Notification:

N0,M1,NM,TM, 1998-01-15 00:03:04Class=1, Notification-For Information Purposes, Color=1Backup Node command issued.

Trouble Notification:

N0,M1,NM,TM, 1998-01-15 00:03:06,Class=1, Notification-For Information Purposes, Color=1Backup Node command issued



child(%d)”,fsend_event);ret_code=ca_put_event(CA_EVENT

,ca_proc_notice_event,sw_event,0’,0,&child_key,buff);

if(ret_code==RET_ERR){

(void sprintf(buff,Error in sending event death of a childpid=%d/n”

,fsend_event);{

Include/event.h contains CA_EVENT, CA_PROC_NOTICE_EVENT, and SW_EVENT.

N O T EType provides a classification of the event. Three event types are defined: Hardware, Software, and Network. The type is used by trouble management to determine where to log the event. Hardware and network event types are logged to the Alarm Log file and software types are logged to the Software Notebook.

Displaying Software Notebook Log EntriesThe Report Software Notebook (REPORT-NBOOK) command allows you to view a report of the Software Notebook Log for a specific date.

Menu Selection ModeSelect the Report Software Notebook option from the Systems Commands menu and respond to the system prompts to specify the date for which you want to view the Software Notebook.

MML Command FormatThe MML command format for the REPORT-NBOOK command is:

REPORT-NBOOK:DATE:DATE=[CC]YY-MM-DD, FILE=file ;



Table 5-3 describes the arguments for the REPORT-NBOOK command.

Man Page FormatThe alternative format and man page format for REPORT-NBOOK is report-nbook.

Sample DisplayThe following sample displays output for the REPORT-NBOOK command for January 15, 1998.

Table 5-3. REPORT-NBOOK Command Arguments


[CC]YY Specifies the century and year, for example, 1998. The century can be either 19 or 20. Year ranges are 80–99 for Century=19, and 00 through 38 for Century=20. For example, you can enter a two-digit year, 98, or, optionally, the complete year, 1998.

MM Specifies the month, for example, 01.

DD Specifies the day, for example, 15.


M REPORT-NBOOK:DATE=1998-01-15;command completed

Report Notebook:

msg_type=533 time=00:03:04 id=2 index=4 msec=440originator ipc key: ,,,,0category=1 subcat=1 type=2 state=0 code=0ipc key(culprit): NO,M1,CM,1Backup Node command issued

msg_type=533 time=00:03:06 id=2 index=4 msec=340originator ipc key: ,,,,0category=1 subcat=1 type=2 state=0 code=0ipc key(culprit): NO,M1,NODE,BKUP,1Backup Node command issued


System Log File

MTP AlarmsMTP alarms appear in the two formats shown in Table 5-4. For a description of these forms and an explanation of the related events, see the include file, mtpevents.h, in the $SINAP_HOME/Include directory.

Table 5-4. MTP Alarms

Nondata PrimitivesIf the SCCP or TCAP sends a nondata primitive, use the appropriate ANSI recommendations to determine the problem and decode the messages.

System Log FileThe SINAP/SS7 system writes some of its messages to the UNIX system log file. While some of the messages are normal, others indicate a potential problem with the SINAP/SS7 system or UNIX. The following three sections describe normal, abnormal, and default messages.

Normal Messages Written to the System Log FileThe following messages are normal:

SS#7 Device Driver: %s

This message appears during UNIX system start up. The %s represents a variable string value.

ALL SINAP SUBSYSTEMS STARTED

This message appears every time the SINAP/SS7 system restarts.

Abnormal Messages Written to the System Log FileThe following messages are abnormal and indicate serious problems. Certain kernel information is required to resolve it. Contact the Stratus Customer Assistance Center (CAC)

MTP Process Alarm Format

MTP level-3 management Process

l3mt module #, state # - input # error,

All other MTP level-3 processes MTP3 state event: sub: #, state: #, code: 0x#


System Log File

immediately. Note that %d represents an integer value; %s represents a text string. The 1st %d is the node index and the 2nd is the UCOMM index.

“drlminit(): Cannot allocate dr_ums[%d][%d].rwlock” “sinapinit(): Cannot allocate drld_sio[%d][%d].rwlock” “sinapinit(): Cannot allocate drld_ssn[%d][%d].rwlock”

Default MessagesThe UNIX operating system generates default alarm messages. The following alarm messages are logged to the UNIX system log file (/var/adm/syslog/syslog.log for HP-UX operating systems; /var/adm/messages for Solaris operating systems; /var/log/messages for Stratus ft Linux operating systems) by default because these messages are defined in the SINAP/SS7 error message files. These messages are listed exactly as they appear in the log file for either type of system, or on the console where %s is a character string that contains information related to the error.

The UNIX operating system uses openlog(), syslog(), and closelog() to control the system logs. (See the operating system man pages for these functions for additional information.)

N O T EThe first two lines in the following messages indicate that a critical process has been terminated. The system closes all SINAP/SS7 processes (including your application).

“SINAP ESSENTIAL PROCESS %s DIEDSINAP WILL BE RESTARTED”

“ALL SINAP SUBSYSTEMS STARTED ”

“SINAP CRITICAL ALARM >>REASON: %s”

“SINAP MAJOR ALARM >>REASON: %s”

“SINAP MINOR ALARM >>REASON: %s”

“SINAP ALARM >>REASON: %s”

Depending on how you set the SINAP_CONSOLE_ALARM_LEVEL environment variable, some of these messages may not be logged to the UNIX system log file. SINAP/SS7 logs only


Handling Events

those alarms that have an alarm severity level equal to or greater than the value you specify for the SINAP_CONSOLE_ALARM_LEVEL environment variable.

For example, if you set the SINAP_CONSOLE_ALARM_LEVEL environment variable to MAJOR, the SINAP/SS7 system would not log MINOR ALARM and SINAP/SS7 ALARM messages. The SINAP/SS7 system would log only those alarms that have an alarm severity level equal to or greater than MAJOR. In this case, only MAJOR and CRITICAL alarm messages would be logged.

For more information on alarm severity levels, see the section in Chapter 3 on defining the alarm severity levels.

Handling EventsTrouble Management handles events according to information in the trouble treatment table (treat.tab). You create this table by editing the file, $SINAP_HOME/Library/treat.tab.


Handling Events

Setting Up the Trouble Treatment Table This section describes the format and contents of the trouble treatment table (treat.tab). You can edit this file and define the category and subcategory treatments the Trouble Management process implements when it receives individual events.

The treat.tab file has the following format:

TREAT_BEGINCATEGORY=category SUBCATEGORY=subcategory FREQ_COUNT=freq_count FREQ_WINDOW=freq_window ALARM_TYPE=alarm_type ALARM_COLOR=alarm_color ALARM_TRIGGER=alarm_trigger TERM_PROCESS_TRIGGER=term_process_trigger TERM_SUBSYS_TRIGGER=term_subsys_trigger SCRIPT_PATH=script_path SCRIPT_TRIGGER=script_trigger NEW_EVENT=new_category,new_subcategory NEW_EVENT_TRIGGER=new_event_trigger SUBCAT_END SUBCATEGORY=subcategory

.

.

. SUBCAT_ENDCAT_ENDCATEGORY=category SUBCATEGORY=subcategory

.

.

.TREAT_END

N O T EYou can specify comments in the treat.tab file by enclosing them with a slash and asterisk (for example, /* information */).


Handling Events

Table 5-5 lists and describes the parameter definitions contained in the treat.tab file. To disable any action within a subcategory, do not specify it or any of its associated actions.

Table 5-5. Treatment Table File Parameters (Page 1 of 3)

Parameter Description

CATEGORY Defines the alarm category. Categories are defined on a system-wide basis. Each value for the CATEGORY field has a unique meaning to the system. The value you assign to CATEGORY can be any number from 1 through 30 or a label. A label is a constant (#define value) that you create in your own include file. The trouble treatment table can contain multiple categories. However, you must specify each category in ascending order; for example, category 2 cannot precede category 1.

SUBCATEGORY Specifies the classification of an event within a category. The value you assign to SUBCATEGORY can range from 1 through 30 or be a label. There can be multiple subcategories in the file, but you must specify each subcategory in ascending order. For example, subcategory 2 cannot precede subcategory 1.

Within a subcategory definition, you must combine certain actions. For example, to specify frequency monitoring, you must use the FREQ_COUNT and FREQ_WINDOW fields. To specify alarms, you must use the ALARM_TYPE, ALARM_COLOR, and ALARM_TRIGGER fields. To specify script files, you must use both the SCRIPT_PATH and SCRIPT_TRIGGER fields. To specify secondary events, you must use both the NEW_EVENT and NEW_EVENT_TRIGGER fields.

FREQ_COUNT Specifies the count of events to occur within the time specified by FREQ_WINDOW before the SINAP/SS7 system triggers an alarm. You must assign either an integer value or a label to FREQ_COUNT.

FREQ_WINDOW Defines the interval, in seconds, in which to count events before the SINAP/SS7 system triggers an event. You must assign either an integer value or a label to FREQ_WINDOW.


Handling Events

ALARM_TYPE Specifies the type or class of alarm the SINAP/SS7 system is to send to all processes registered to receive this alarm class. Possible values are • REG_CRITICAL (Critical Alarms) Severe,

service-affecting conditions that require immediate attention. These alarms are automatically written to the UNIX system log and system console.

• REG_MAJOR (Major Alarms) Caused by hardware and software conditions that indicate a serious disruption of service.

• REG_MINOR (Minor Alarms) Indicates trouble conditions that do not have a serious effect on customer services.

• REG_NOTICE (Notice Alarms) Indicates a server-affecting situation. Provided for informational purposes only.

ALARM_COLOR Identifies the severity of the alarm. Possible values are RED, YELLOW, GREEN, and WHITE, which correspond to the numbers displayed in the alarm (4 through 1, respectively).

ALARM_TRIGGER Specifies one of the following types of alarm to trigger:

• SINGLE_EVENT triggers an alarm on a single event.

• FREQ_MON triggers an alarm when the frequency count is exceeded within the time specified by FREQ_WINDOW.

TERM_PROCESS_TRIGGER Specifies when to terminate the process that has sent the alarm. Possible values are SINGLE_EVENT and FREQ_MON.

TERM_SUBSYS_TRIGGER The field specifies when to terminate the subsystem with the offending process. Possible values are SINGLE_EVENT and FREQ_MON.

SCRIPT_PATH Defines the path name of a user-defined script file. Trouble Management spawns a shell to call a script you have defined. You can use scripts for any purpose you define; however, you should not program real-time actions using the script. The name of the script can be up to 31 characters long.

SCRIPT_TRIGGER The field specifies when to trigger the script. Possible values are SINGLE_EVENT and FREQ_MON.




Handling Events

NEW_EVENT Specifies the category and subcategory for the new event the SINAP/SS7 system generates upon receiving the specified trigger. You can specify a new event with a new category and subcategory. The new event contains the ASCII string from the original event and goes to Trouble Management. Trouble Management limits the daisy chaining of events to a predefined limit of 32. This limit is imposed to prevent event messages from circulating in an endless loop.

NEW_EVENT_TRIGGER The field specifies when to trigger the new event. Possible values are SINGLE_EVENT and FREQ_MON.




Handling Events

Figure 5-2 shows an example of the file used to create a trouble treatment table.

Figure 5-2. Sample treat.tab File

#include <caslinc.h> /*SINAP Include Files */#include <dr_incl.h> /* SINAP Driver Include File */

/* User defined include files should be included here */ /* Explicit path names are required for files not in */ /* /home/sinap/Include */

/* Define treatment for Client Application Z (assigned number 23) */

TREAT_BEGIN CATEGORY=CLIENT_Z

/* Subcategory */

SUBCATEGORY=CLIENTZ_SUB1

/* Generate trigger after 3 events in 10 seconds */ FREQ_COUNT=3 FREQ_WINDOW=10

/* Trigger Minor Alarm after a Single Event */ ALARM_TYPE=REG_MINOR ALARM_COLOR=YELLOW ALARM_TRIGGER=SINGLE_EVENT

/ * Generate New Event (CLIENT_Z, CLIENTZ_SUB2) Upon Frequency Mon.Trigger */ NEW_EVENT=CLIENT_Z, CLIENTZ_SUB2 NEW_EVENT_TRIGGER=FREQ_MON

SUBCAT_END

/* Subcategory CLIENTZ_SUB2 */

SUBCATEGORY=CLIENTZ_SUB2

/* Trigger Critical Alarm after a Single Event */ ALARM_TYPE=REG_CRITICAL ALARM_COLOR=RED ALARM_TRIGGER=SINGLE_EVENT

/* Terminate Subsystem */

TERM_SUBSYS_TRIGGER=SINGLE_EVENT

/* Execute User Script */

SCRIPT_PATH="/usr/client/zdir/restartz" SCRIPT_TRIGGER=SINGLE_EVENT

SUBCAT_END CAT_ENDTREAT_END


Using the I_TROUBLE_NOT IPC Alarm Fields

Adding an Event or Changing Its TreatmentThe following steps show how to add an event or change the way the SINAP/SS7 system treats it:

1. Edit the treat.tab file in $SINAP_HOME/Library to add an event or change the way the SINAP/SS7 system treats it.

2. Use the nmtr program to convert treat.tab to an intermediate format called tm_treat.lod. The nmtr program has the following syntax (where filename is the name of the file to be converted).

nmtr [-I] filename

The -I argument installs the tm_treat.lod file in the directory $SINAP_HOME/Bin/shm/pri and renames the file to TREAT_load. If you do not use this argument, you must copy the file manually to the directory and rename it TREAT_load.

3. Invoke the SINAP/SS7 MML command, READ-TREAT, to inform the system to read the file and implement the changes. You can enter this command directly into the system using the MML command format or entered interactively using the menu selection mode. Using the menu selection mode, select the Read Treatment Table option from the Systems Commands menu and respond to the system prompts. The READ-TREAT command tells the SINAP/SS7 system to read the TREAT_load file into the trouble treatment table.

N O T EWhen you invoke READ-TREAT, the SINAP/SS7 system reinitializes any counters (that is, accumulation of events per time period) to 0.

Using the I_TROUBLE_NOT IPC Alarm FieldsThis section describes how to send and receive alarms using the I_TROUBLE_NOT function. Each time an I_TROUBLE_NOT event message arrives, the current process will be interrupted by a signal. The SINAP/SS7 system displays the event on the screen and prints it to standard output. The sample program, alarm.c, provides an example of how to register and receive events using I_TROUBLE_NOT. This program is included in the SINAP software.

The SINAP/SS7 system and user applications can generate I_TROUBLE_NOT events. For user events, see the following section, “User-Supplied Error Messages and Events.” The remainder of this section describes the SINAP I_TROUBLE_NOT events.

The sample program alarm.c shows how a user application can register for and receive SINAP/SS7 alarms.



Appendix I, “List of Alarm and Event Messages,” contains categories, descriptions, sources, and actions for all SINAP/SS7 alarm and event messages. Also see SINAP/SS7 Programmer’s Guide (R8052) for descriptions of the header portion of the I_TROUBLE_NOT function, specifically the event notification functions, ca_get_msg(), ca_put_msg(), and the user event function, ca_put_event().

Table 5-6 contains the fields and descriptions for the variable ASN.1 data portion of the I_TROUBLE_NOT IPC data processed by $SINAP_HOME/Samples/ccitt/alarm.c alarm_notification_decode() function as an example .

Table 5-6. I_TROUBLE_NOT_IPC Data Fields and Descriptions (Page 1 of 2)


pbyte Reference count into the variable data. The sample program, alarm.c, provides the use and meaning for this parameter.

psourceid The IPC key in ASCII that consists of node, module, application, and process. Node and module represent the user-configured node name and module name, respectively. The sinap.h file defines the application and process names required to build the IPC key for the field, psourceid. See ca_register() in the SINAP/SS7 Programmer’s Guide (R8052) for more information about these fields.

ptime The time in ASCII text at which the I_TROUBLE_NOT IPC alarm is reported.

paddhdr Additional header that is always set to NULL for SINAP-generated I_TROUBLE_NOT alarms. Data will only be valid when defined by the user’s IPC’s generating I_TROUBLE_NOT events.

pevent Alarm notification text based on the following alarm types and their accompanying alarm notification text:

• Critical “Critical Alarm - Immediate Action Required”

• Major “Major Alarm - Services May be Affected”

• Minor “Minor Alarm - Repairs Required”

• Notice “Notification - For Information Purposes”

See Appendix I, “List of Alarm and Event Messages” for a complete list of event categories and messages.



For an example of the ASCII data found for the SINAP/SS7 processes, see the output of the sy command, #IPC.

Trouble Management EventsAll I_EVENTS sent to nmtm (Trouble Management) are logged in either the Software Notebook or Alarm Notebook, depending on event type.

The following sample shows how to use the src/nm/nmtmmain.c - event_processing() function to log a trouble management event:

/* Determine Where to Log Event IPC */ if (dio_event.event_ipc.event.type == SW_EVENT)

{

/* Log in Software Notebook */

(void) strcpy((char *) dio_event.disk_io.fname,"SWN");

}

else

{

/* Log in Alarm Log File */

(void) strcpy((char *) dio_event.disk_io.fname,"ALM");

}

color Alarm notification messages appear in the color designated for that type of alarm. Alarm color values (alarm_color) are defined by alarm_type as follows:

• Critical alarm = red

• Major alarm = yellow

• Minor alarm = yellow

• Notice alarm = white

ptext Text description of the error as defined by SINAP. See Appendix I, “List of Alarm and Event Messages” for descriptions of event and alarm messages.

pclass See Chapter 4 of the SINAP/SS7 Programmer’s Guide (R8052) for descriptions of class.

Table 5-6. I_TROUBLE_NOT_IPC Data Fields and Descriptions (Page 2 of 2)



User-Supplied Error Messages and Events

After the I_EVENT is logged, the function notification() is called. It looks at the treat_tab or sets up default actions if there is no treat_tab. notification(), then logs the alarm to the ALARM log.

Using the src/nm/nmtmmain.c - notification() function, log an alarm as follows:

(void) strcpy((char *) dio_alarm.disk_io.fname,"ALM");

Then generate the I_TROUBLE_NOT IPC that is sent to all processes registered for that IPC.

User-Supplied Error Messages and EventsA client application process can send events and error messages as I_TROUBLE_NOT messages to Node Management’s Trouble Management process. Upon receiving an event, Trouble Management logs the event to disk and determines how to respond to it, based on the event category and subcategory specified in the event. You set the treatment for a particular category and subcategory combination in the trouble treatment table.

Because all user events are software events, they are logged in the Software Notebook. You can program events for all categories and subcategories. The only exceptions are the hardcoded alarms that are generated when you have not specified treatment for a particular category and subcategory in an event, or when event daisy chaining exceeds the predefined limit.


User-Supplied Error Messages and Events


Chapter 6 Troubleshooting6-

This chapter provides some basic guidelines for troubleshooting the SINAP/SS7 system. It also describes how to use some administrative commands, the sy utility, and the Built-In Test Environment (BITE) monitor and log analysis facilities to isolate and resolve problems.

For additional information and samples for troubleshooting, contact the Customer Assistance Center (CAC).

Basic Troubleshooting GuidelinesBefore message signaling units (MSUs) can be sent and received, at least one link, one link set, one local subsystem number (SSN), and one remote SSN must be in the “available” state. When troubleshooting your system, Stratus recommends using a bottom-up approach. That is, you should check the status of links, link sets, route sets, subsystems (remote and local), and applications to verify that they are active and available.

You can use the Terminal Handler DISPLAY commands (described in this chapter and previously in Chapter 4, ‘‘System Operation and Maintenance”) to check the status of these network elements. You can also use the SINAP/SS7 utility, sy, to display the internal status and verify the availability of network elements. See Appendix C, ‘‘SINAP/SS7 MML Command Summary,” for frequently used sy commands.

When you are confident that these pieces of the system are operating properly, then you can investigate further using BITE to determine whether or not an application is sending and receiving message signaling units (MSUs).

Verifying Physical and Logical Board AssignmentsThe /etc/SS7links file contains board assignment information that must match the corresponding operating system configuration file. For the HP-UX and Solaris operating systems, compare the /etc/SS7links contents with the /etc/dncp/comm/opersonality.conf and /etc/orse/orsdinfo file. These files are ASCII text files that can be viewed, modified, or printed using any UNIX text editor.

Troubleshooting 6-1

Verifying All Processes Are Running

Verifying All Processes Are RunningThe first step is to verify that all processes and applications are running properly. Issue the following command to list the active SINAP/SS7 processes on HP-UX systems:

ps -eaf | grep sinap | more

The above does not list SINAP processes on Solaris and Stratus ft Linux systems, so on Solaris and Stratus ft Linux platforms, instead use:

ps -eo pid,ruser,fname | grep sinap | more

Before any data can be transmitted—that is, before MSUs can be sent and received—at least one of each of the following components must be configured and active:

• Link

• Link set

• Route set

• Remote SSN

• Local SSN

• Application

If one or more components is not responding, begin the troubleshooting process.

First, check on the status of required SINAP components in the order listed above to make sure each is in an “available” state. If all components are available, the system should send and receive MSUs. Otherwise, use the BITE system for further diagnosis.

You can then view the current status of the system components by using the DISPLAY commands from the Terminal Handler, by hooking up a datascope to your machine to locate an equipment problem, or by using the SINAP/SS7 utility, sy and gathersy.

Using the sy Utility for TroubleshootingThe sy utility allows display of most internal tables and structures in the SINAP/SS7 system. It can be used to make sure all SINAP components, such as links and link sets, are available. To run sy, log in to the SINAP/SS7 account on the node that you want to troubleshoot, then run sy.

If the SINAP node is running, the following system information appears, for example:

$ syVERSION=Rel 6.1.0.3 05/21/98, SINAP_Variant=TTCcurrent time is Fri May 31 05:13:34 1998type “?” for command listEnter cmd>



You can then enter a sy command at the command line, followed by parameters separated by commas. Enter a “?” to see the complete list of sy commands. See Appendix C, ‘‘SINAP/SS7 MML Command Summary,” for the most commonly used sy commands.

An example of a sy command is:

Enter cmd>#ipc,0

N O T ECase is not important when entering commands.

If the SINAP node is not running, the following output appears:

$ sy-(?ERR):CASL:2 SY, 2-HPUX erro (PSYSTEM)-(?ERR):bi_register() errno=2

SY-SY: cannot register, ret=2

Using gathersy for TroubleshootingThe gathersy tool runs sy and puts the output into a file. The trace information is stored as ASCII text in the output file, problemx.x. The Stratus helpdesk personnel request the output from this file whenever you require their support to assist in defining a problem.

You can run a gathersy trace by entering the following commands from a UNIX prompt:

cd $SINAP_HOME/Bingathersy problemx.x

A gathersy trace runs in the background for approximately two minutes before generating any output. Print the problemx.x file to examine the results.

Checking Link StatusBegin troubleshooting your system by ensuring at least one link is active. To determine link status, issue the DISPLAY-LINK command from the Terminal Handler. (Chapter 2, ‘‘Performing Basic Tasks,” describes using the two modes of operation for the Terminal Handler.)

Menu Selection ModeFrom the SINAP System Main Menu, select Network Commands to view the Network Commands menu. From the Network Commands menu, select the Display option to view the

Troubleshooting 6-3


Display Commands menu. Select the Display Link option and follow the screen prompts to display link information.

MML Command FormatThe DISPLAY-LINK command has the following MML command format:

DISPLAY-LINK:LINK=ALL

The command produces a display similar to that shown in Figure 6-1.

Figure 6-1. DISPLAY-LINK Command Sample

The status legend displays under the Status column heading. A status of all lowercase letters indicates normal functioning. A status of I indicates that the SINAP/SS7 system cannot recognize the IOA boards and most likely it is not loaded. A status of U indicates that the MTP Level 3 is unable to communicate with Level 2 and a status request is pending. A status of A means that the link is not available because MTP level 3 is unable to establish communication with remote Level 3.

In the sample figure, link0 and link1 have a status of iabclrnt, indicating that these links are active and running normally. However, link2 and link3 have a status of iAbclrFt, and are thus unavailable or unaligned. This indicates that MTP Level 2 is not communicating with the remote subsystem. To determine why, you must hook up a datascope or run sy to get a Level 2 trace.

To check the link status using the sy utility, start sy and issue the command:

#ucomm, <port number>

SINAP N1,M1,NM,TH,2 User:sysopr, Level: 5 Display Response N1,M1,NM,CM 1998-01-08 15:56:24M DISPLAY-LINK:LINK=ALL; ok command completed

LinkName Link LSetName LSet SLC Port Speed ADPC State Status ErrorLink0 0 lset1 0 0 0 64000 3003 ACTIV iabclrnt 0Link1 1 lset1 0 1 1 64000 3003 ACTIV iabclrrnt 0Link2 2 lset1 0 2 2 64000 3003 ACTIV iAbclrFt 0Link3 3 lset1 0 3 3 64000 3003 ACTIV iAbclrFt 0

--Link Status Legend--i - installed I - not installeda - available A - not availableb - not remotely blocked B - remotely blockedc - not congested C - congestedl - not locally inhibited L - locally inhibitedr - not remotely inhibited R - remotely inhibitedn - link normal U - status unavailable F - link failedt - no periodic link test T - periodic link test activex - no loopback X - loopback based on SLTM detected



If the ucomm board on port 2 is not installed properly, the following sample displays the output of this command:

$syEnter cmd>#ucomm,2Enter cmd> SY-SY(0002):recvd I_L2_TRAC_RESP from N0,M1,L3,MT,1

====UCOMM 0 trace

Note the mismatched ucomm number. You requested ucomm 2 and received ucomm 0. This indicates there is a problem with ucomm 2.

If the ucomm 2 board is present and correctly installed, but the link has failed, the system response will be similar to the following sample display:

$syEnter cmd>#ucomm,2Enter cmd> SY-SY(0002):recvd I_L2_TRAC_RESP from n0,M1,L3,MT,1

====UCOMM 2 traceTC :state=IN_SERVICE M_startRC :state=IDLE M_startIAC :state=IDLE M_startTC :state=IN_SERVICE M_send_SIOIAC :state=NOT_ALIGNED M_SIOSIAC :state=NOT_ALIGNED M_SIOTC :state=IN_SERVICE M_send_SINIAC :state=ALIGNED M_SIOIAC :state=ALIGNED M_SIOSLSC :state=INITIAL_ALIGNMENT M_alignment_not_possibIOM2 : M_alignment_not_possibRC :state=IN_SERVICE M_stopTC :state=IN_SERVICE M_send_SIOSTC :state=IN_SERVICE M_normal

The sample trace indicates the system sent an SIO, but never received an SIN or SIE in return. This means that the problem is probably on the other end of the link.

Troubleshooting 6-5


If the board is present, installed correctly, and the link is operational, the sy trace response will be similar to the following sample display:

$syEnter cmd>#ucomm,0Enter cmd> SY-SY(0002):recvd I_L2_TRAC_RESP from n0,M1,L3,MT,1

====UCOMM 0 traceTC :state=IN_SERVICE M_startRC :state=IDLE M_startIAC :state=IDLE M_startTC :state=IN_SERVICE M_send_SIOIAC :state=NOT_ALIGNED M_SIOSTC :state=IN_SERVICE M_send_SINIAC :state=ALIGNED M_SIOIAC :state=ALIGNED M_SINIAC :state=PROVING M_SINIAC :state=PROVING M_T4_expiredLSC :state=INITIAL_ALIGNMENT M_alignment_completeTC :state=IN_SERVICE M_send_FISUIOM2 : M_alignment_completeLSC :state=ALIGNED_READY M_MSU_FISU_receivedLSAC :state=ACTIVAT_RESTORING M_in_serviceTC :state=IN_SERVICE M_send_MSULSAC :state=ACTIVAT_RESTORING M_SLT_successfulIOM2 : M_in_serviceLSAC :state=ACTIVE M_sig_link_loaded

The sy trace summary for an operational link appears as follows:

own_PC=0xe71501, ni=128discrim_discard_cnt=7, rx_cong_discard_cnt=0tx_cong_discard_cnt=0, tx_size_discard_cnt=0

LSC_state=IN_SERVICE ,LSAC_state=ACTIVE ,IAC_state=IDLE

POC_state=IDLE ,RC_state=c ,TC_state=IN_SERVICE

L3_ALIVE_COUNTER = 61SMALL_GET = 0 ,SMALL_RET - 0LARGE_GET = 2187 ,LARGE_RET - 2210Queue: IOM2 LSC LSAC IAC POC TC RCCount: 0 0 0 0 0 0 0Active Timer Queue: (empty)



If a link is in a normal state, the LSAC_state should be ACTIVE. TC and RC should both have a state of IN_SERVICE.

Checking Link Set StatusUsually, when one link in a link set is active, the link set appears to be active. You can check the status of a link set by issuing the DISPLAY-LSET command from the Terminal Handler.

Menu Selection ModeSelect Display Linkset from the Display Commands menu and follow the prompts to display all link sets.

MML Command FormatThe DISPLAY-LSET command has the following MML command format to display all link sets:

DISPLAY-LSET:LINKSET=ALL

The command produces a display similar to that shown in Figure 6-2.

Figure 6-2. DISPLAY-LSET Command Sample

In the output in the sample, the line:

LSet Name = lset1, LSet = 0, ADPC = 3003, DPC Count = 1

SINAP N1,M1,NM,TH,2 User:sysopr, Level: 5 Display Response N1,M1,NM,CM 1998-01-28 15:56:24M DISPLAY-LSET:LINKSET=ALL; ok command completedLSet Name = lset1, LSet = 0, ADPC = 3003, DPC Count = 1Active Links = 4, Loaded Links = 4, State = ACTIVE, STATUS = ave

LinkName LINK SLC Priority Availablelink0 0 0 0 YESlink1 1 1 1 YESlink2 2 2 2 NOlink3 3 3 3 NO

--Link Set Status Legend--a - available A - not availablev - active V - not activee - not emergency E - emergency


Troubleshooting 6-7


indicates that lset1 has an adjacent destination point of 3003 and that the number of destination point codes you can reach from this link set is 1 (DPC Count = 1). Additionally, the line:

Active Links = 4, Loaded Links = 4, State = ACTIVE, STATUS = ave

indicates that there are four active and loaded links. The link set status (ave) indicates that the link set is available, active, and not in emergency state. See the Link Set Status Legend on the screen.

You can use the sy command #13,lst command to display link set status. The #13,lst command is especially useful because it shows the status of every link configured on the link set, as well as the link set status. Figure 6-3 shows output from this command.

Figure 6-3. #13,lst sy Command Displaying Link Set Status

Checking Route Set StatusAfter confirming that the link set is available, check the status of the route set by issuing the DISPLAY-RSET command.

Menu Selection ModeSelect the Display Routeset option from the Display Commands menu and follow the prompts to display all route sets.

$syEnter cmd>#l3,lst L3SD linkset:

0:dpc=3003,LLSC_st=ACTIVE,TSRC_st=IDLE ,actv_lnks=4,load_lnks=4activated=1,avail=1,cong=0,emer=0,off=0,dur=0,time=0 priority: 0 1 2 3 N N N N N N N N N N N Nnorm_lnk: 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 curr_lnk: 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 dest_cnt=1:PC3003(rt#=0,rst#=0)

LNK0:ucomm=0,st=ACTIVE,TLAC_st=AVAIL,TCOC_st=IDLE ,TCBC_st=IDLET1=0,T2=1441794,T3=1376257,T4=1376260,T5=1376261 T12=0,T13=0,T14=0,T22=0,T23=0 failed=0,TSRC_loaded=1,cong=0,inh=0,uninh_start=0 loc_req=0,TSRC_unav=0,loc_inh=0,rem_inh=0,mgmt_req=0 rem_blocked=0,coc=0,coc_in_prog=0,cbc_in_prog=0 loc_BSNT_retv=1,rem_BSNT_retv=0,TCOC_msg=0,TLAC_msg=0 loc_BSNT=123,rem_BSNT=0,off=0,dur=0,time=717699611

LNK1: .....LNK2: .....LNK3: .....



MML Command FormatThe DISPLAY-RSET command has the following MML command format:

DISPLAY-RSET:DPC=ALL

Figure 6-4 illustrates the DISPLAY-RSET command.

Figure 6-4. DISPLAY-RSET Command Sample

In the display, note that the state of the route set is ACTIVE and the status for destination point code 3003 is abc (a indicates that the destination point code [DPC] is available; b and c indicate that the route set is not blocked or congested). Thus DPC 3003 can send and receive message signaling units (MSUs).

The fact that the route set is active indicates that at least one link set and link are active and aligned.

The DISPLAY-RSET command does not display the concerned point code (CPC) count of local subsystem number (LSSN) that displays for the CCITT variant.

SINAP N1,M1,NM,TH,2 User:sysopr, Level: 5 Display Response N1,M1,NM,CM 1998-01-28 16:26:24DISPLAY-RSET:DPC=ALL; okcommand completed

DISPLAY ROUTE SETRSet Name = rset1, DPC = 255-255-255 Routing Method = Member (ANSI)DPC = 3003, CPC Count of LSSN = 0 (CCITT only)State = ACTIVE, Status = abc, Load Sharing = YESRoute Name Priority Statuslset1 1 axlr

--Route Set Status Legend--a - DPC accessible A - DPC not accessibleb - route set not blocked B - route set blockedc - route set not congested C - Route set congested

--Route Status Legend--

a - link set available A - link set not availablex - transfer allowed X - transfer not allowedl - link set not congested L - link set congestedr - route not congested R - route congested

Troubleshooting 6-9


You can use the sy command #13,lst to display route set status, as shown in Figure 6-5.

Figure 6-5. #13,lst sy Command Displaying Route Set Status

In the ANSI network variant, you must use the sy command, #sc,ssn, to view the number of CPCs associated with local subsystem numbers. (This command is described in the following section.)

Checking the Accessibility of a Remote SSN Though the remote point code is accessible, the remote node might not be. To determine whether the remote node is accessible (and thereby, whether messages can be sent), use the sy utility command #sc,ssn as illustrated in Figure 6-6.

Figure 6-6. #sc,ssn sy Command Sample

The sample indicates that MSUs can be sent to subsystem number (SSN) 253 at point code 3003 because the value of state is ALLOWED for this DPC and SSN. The other SSNs do not appear because they are not defined for that remote SSN.

Sometimes, an SSN can be in the PROHIBIT state. Before the SSN can be in the ALLOWED state, the Signaling Connection Control Point (SCCP) must receive a SUBSYSTEM AVAILABLE notice from Message Transfer Part (MTP) Level 3 of the remote node. However, you may need to restart the SINAP/SS7 system because this will set all configured SSNs to the ALLOWED state.

$ s yE n t e r c m d > # l 3 , r s t ⇐ p r e s s ↵L 3 S D r o u t e s e t :

0 : d p c = 3 0 0 3 , A C C E S S I B L E , c u r r _ r o u t e s = 0 , 0 ,l o a d _ s h a r e = 1b l o c k e d = 0 , c o n g _ s t a t = 0 , c o n g _ c n t = 0 , T 6 = 0 , r e f # = 0, s n d _ a c k = 0

s t a t e s : T F R C = 0 , T C R C = 0 , T S R C = 0R T 0 : l s = 0 ( A V A I L ) , r o u t = A V A I L , t r _ s t a t = T R _ A L L O W E DT 1 6 = 0 , T 1 0 = 0 , R S R T _ a c t v = 0 , r t _ c o n g = 0 , l s _ c o n g = 0

Enter cmd>#sc,ssnSCCP remote SSNs:DPC3003:sls=6,state=ALLOWED,tid=0,pc_level=0 253, sls=1, state=ALLOWED, ttyp=0, tid=0



N O T EWhen a remote SSN goes into the PROHIBIT state, the SINAP/SS7 system receives a subsystem prohibit message from the remote node.

Checking the Availability of a Local SSNHaving ensured that the remote SSN is accessible, check whether the local SSN is available, that is, whether messages can be sent and received. The local SSN is available when the SSN is properly registered (equipped) with the SINAP/SS7 system and is in an allowed state. Issue the DISPLAY-SUBSYSTEM command to check availability.

Menu Selection ModeFrom the SINAP System Main Menu, select Application Commands. Select the Display SSN option from the Application Commands menu and follow the prompts to display all subsystem numbers.

MML Command FormatThe DISPLAY-SUBSYSTEM command has the following MML command format:

DISPLAY-SUBSYSTEM:SSN=ALL;

It provides output similar to the sample shown in Figure 6-7.

Figure 6-7. DISPLAY-SUBSYSTEM Command Displaying Local SSN

In the display, the line:

ALL others are UNEQUIPPED

SINAP N1,M1,NM,TH,2 User:sysopr, Level: 5 Display Response N1,M1,NM,CM 1998-01-28 16:39:24DISPLAY-SUBSYSTEM:SSN=ALL; okcommand completed

Display local subsystem:local ssn=254 state=PROHIBITEDAll others are UNEQUIPPED

Troubleshooting 6-11


indicates that if any MSUs are received by SINAP for an SSN other than SSN 254, the SINAP/SS7 system will discard them; that is, they are UNEQUIPPED. Also, SSN 254 cannot receive MSUs because it is in the PROHIBITED state (was previously in service but is now out of service) and needs to send a USER_IN_SERVICE (UIS) message to the SCCP. Thus, an SSN must be registered (EQUIPPED) and in the ALLOWED state before it can receive MSUs.

For example, to register SSN 250 use the CREATE-CPC or CHANGE-CPC command (see Table C-1.) to add SSN 250 for DPC 3003. Now, reissue the DISPLAY-SUBSYSTEM command from the Terminal Handler. The display appears as shown in Figure 6-8. See the SINAP/SS7 Programmer’s Guide (R8052) for more information.

Figure 6-8. DISPLAY-SUBSYSTEM Command

The display indicates that SSN 250 is now defined to the system and ready to receive MSUs. This means that remote SSN 253 and local SSN 250 can now exchange MSUs.

Checking the Status of the ApplicationTo view all applications (processes) registered with the SINAP/SS7 system, use the sy command #IPC,0. Figure 6-9 shows a sample display.

SINAP N1,M1,NM,TH,2 User:sysopr, Level: 5 Display Response N1,M1,NM,CM 1998-01-28 16:39:24DISPLAY-SUBSYSTEM:SSN=ALL; okcommand completed

Display local subsystem:local ssn=254 state=PROHIBITEDlocal ssn=250 state=ALLOWEDAll others are UNEQUIPPED



Figure 6-9. Displaying All Registered Processes

You can then look at specific application information for any entry by using that application number in the #ipc <application number> command. This allows you to check

Enter cmd>#ipc,0 1:N1,M1,NM,PP,1 pid=1626 2:N1,M1,NM,CL,1 pid=1656 3:N1,M1,NM,DS,1 pid=1660 4:N1,M1,NM,TM,1 pid=1662 5:N1,M1,NM,CM,1 pid=1661 6:N1,M1,NM,NI,1 pid=1663 7:N1,M1,NM,IP,1 pid=1658 8:N1,M1,NM,DM,1 pid=1659 9:N1,M1,NM,MC,1 pid=166410:N1,M1,BI,PP,1 pid=166611:N1,M1,BI,MI,1 pid=167112:N1,M1,BI,LF,1 pid=167213:N1,M1,BI,ID,1 pid=167314:N1,M1,BI,TU,1 pid=167415:N1,M1,L3,PP,1 pid=167616:N1,M1,L3,MT,1 pid=168717:N1,M1,L3,DT,1 pid=168818:N1,M1,L3,RT,1 pid=168919:N1,M1,L3,RC,1 pid=169020:N1,M1,L3,LA,1 pid=169121:N1,M1,L3,CO,1 pid=169222:N1,M1,L3,FR,1 pid=169423:N1,M1,L3,CR,1 pid=169524:N1,M1,L3,CB,1 pid=169325:N1,M1,L3,LS,1 pid=169626:N1,M1,SC,MG,1 pid=170727:N1,M1,SC,SO,1 pid=171430:N1,M1,TC1,RECV,1 pid=179231:N1,M1,SY,SY,1 pid=1811Enter cmd>


Using the BITE Subsystem

information such as how the SSN is registered. To see information about application 28, enter the command #ipc,28. Figure 6-10 displays sample information for this command.

Figure 6-10. Displaying Application Information

Using the BITE SubsystemSuppose you confirm that all the requisite components are available, but MSUs still cannot be processed. You can use the BITE subsystem to further investigate the problem to determine whether an application is receiving and responding to inquiries, and whether or not the driver is sending anything.

The BITE subsystem provides the following services:

• Provides intrusive and nonintrusive testing

• Monitors various IPC paths and displays and/or logs them

• Monitors incoming and outgoing SS7 messages and displays and/or logs them

• Accumulates statistics and displays and/or logs them

• Simulates the network, using scenarios that users create

The BITE subsystem has the following limitations:

• A maximum of eight active monitors can exist at any given time.

• A maximum of eight entities can be specified in a monitor command.

• The bilf and biid processes cannot be monitored.

• The nmth process cannot be monitored for input if the DISPLAY setting is set to ON.

• Only the first seventy (70) characters of the monitor command are echoed in the MML response.

• The log file name is checked against the file names used in active monitors.

• No processes, except nmth, can turn on the DISPLAY option.

Enter cmd>#ipc,28IPC process table entry 28:key=N1,M1,TC1,RECV,1, key.ipc_index=28, bfence=0x1,

entry=28, link=255, pid=19226, h_timer_id=0index=(1,1,6,1,1) fsignal=0, fcmd=1, fss7=1fhealth=0, fparent=0, app_ver=CCITT, proc_ver=Rel2.1failure_option=NO+ACTIONsio_ssn_ind=2, sio_ssn=250ss7_input_boundary=TCAP, ss7_primitive=CTRL_DAT



You can configure the BITE subsystem to best suit your needs. See “Using the BITE Monitor” in Chapter 4 for more information. The BITE defaults are:

• Default log size is set at 200K bytes. Maximum is 1,000K bytes.

• Log file is always created in the $SINAP_HOME/Logs/bite directory.

• [Node], [Module] names, if omitted, indicate local node and module.

• [Instance] number, if omitted, indicates all instances at the time of the command.

BITE traces the data at the link level (or between driver and client as described in the next paragraph). The trace point is located in the STREAMS driver at the point the data is received from Level 2. All data traveling between Level 2 and Level 3 is captured. Each message being traced is copied, and the copy is sent to BITE for logging. Because FISU and LSSU do not always travel between Level 2 and Level 3, the trace does not show any FISUs, and shows only the LSSUs that are sent to Level 3.

BITE traces data moving between the driver and the client application. This includes both IPC and SS7 data (MSUs). Whenever the client application issues a read or write, the data is copied to a buffer and sent to BITE. Figure 6-11 shows the BITE trace points.

Figure 6-11. BITE Trace Points

C lie n t A p p lic a t io n

c a _ g e t_ tcc a _ p u t_ tc

c a _ g e t_ m s uc a _ p u t_ m s u

c a _ g e t_ m s gc a _ p u t_ m s g

D r iv e r

M a k e a c o p yo f th e M S U

fo r B IT E

M a k e a c o p yo f th e IP Cm e s s a g efo r B IT E

IO A S u b s y s te m L e v e l 2

B IT EL o g g in gP ro c e s s

S S 7 D a ta

IP C D a ta

L N K D a ta



BITE provides a monitor facility and a log analysis program to help you troubleshoot network problems.

• The BITE Monitor facility enables you to monitor applications, processes, SS7 links, and IPC paths. During a monitor session, information is collected and written to a BITE log file, which you can then analyze using the BITE Log Analysis program. You use the MML commands START-MON and STOP-MON, respectively, to initiate and terminate a BITE monitor process. These commands can be entered directly using the MML command format, or issued using the menu selection mode to access the BITE Commands menu from the SINAP System Main Menu.

• The BITE Log Analysis program processes information logged by BITE. This program provides several commands for finding, displaying, and selecting particular records in a log file, and for printing the results.

These facilities are described in more detail in the following sections.

Initiating BITE MonitorsThe BITE monitor facility provides an in-depth look at the system’s status. This means you can check an application’s status at the SS7 level. For example, suppose you confirm that your SINAP/SS7 configuration is functioning, but MSUs are not being processed. You can use BITE to further investigate the problem and to determine whether the application is receiving and responding to inquiries and whether the SS7 driver is sending information.

You initiate a BITE monitor process by issuing the MML command, START-MON, specifying the entities to be monitored and the types of operations for which you want to collect information (read or write, or both). The monitor process keeps track of the specified entities in order to collect the specified information, which it writes to a BITE log. To terminate the monitoring session, you issue the MML STOP-MON command. For more information on starting and stopping BITE monitors, see ‘‘Using the BITE Monitor’’ in Chapter 4.

N O T EYou can use BITE Log Analysis commands to display and extract records and obtain summary information from the BITE log that contains all the record data collected during the monitoring session.

Starting the BITE Log Analysis Program The BITE Log Analysis program contains command options that allow you to display and analyze information in a BITE log. You can start this program by issuing commands directly using the MML command line formats, or by using the menu selection mode.



The records contained in a BITE log appear in the order in which they were received during the monitoring session. These records are in I_Block format, with SS7 M_Block structures embedded in the I_Block structure. BITE monitor logs can contain interprocess communication (IPC), SS7, and link (LNK) messages.

• If the log contains IPC messages, see the SINAP/SS7 iblock.h include file to decode the message type. You can then use the appropriate .h file to decode the message structure.

• If the log contains SS7 or LNK messages, use the SINAP/SS7 mblock.h include file to determine the message type and structure. You may also need to refer to the appropriate CCITT or ANSI recommendations to decode messages. However, the BITE Log Analysis program performs most of this decoding for you.

Menu Selection ModeSelect the Log Analysis option from the BITE Commands menu.

MML Command FormatType bila at the UNIX prompt of a SINAP/SS7 login window (that is, any window through which you have logged in as the user, sinap).

Using either method, the SINAP/SS7 system activates the BITE Log Analysis program and displays the Log Analysis menu, as shown in Figure 6-12.

Figure 6-12. Log Analysis Menu

********************** BITE LOG ANALYSIS **********************The Syntax of the MML Command is:

COMMAND:PARAMETER=[OPERATION]VALUE,...;

The Log Analysis Commands are:

– FIND

– SELECT

– SUMMARY

– DISPLAY

– QUIT

Enter the Log Analysis MML Command, or enter ‘help’ for more information:



To issue a Log Analysis command, use the keyboard to type the command directly on the command line or type help to display help information.

Be aware of the following considerations as you issue BITE Log Analysis commands.

• You must enter the complete command line for the command you want to execute (for example, enter display:file=log_0529 and not simply display). Unlike the Terminal Handler, the BITE Log Analysis program does not build a command based on your input to specific prompts. (For a description of command’s syntax, see the command description later in this chapter.)

• You can type the command in lowercase letters (for example, find:file=log0529); you need not use uppercase letters (for example, FIND:FILE=LOG0529).

• The semicolon (;) at the end of the command is optional; you need not include it in the command line.

Using Log Analysis Commands This section provides information on the relational operators and keywords you can use with all of the Log Analysis commands. It also describes each of the following Log Analysis commands, including the command syntax and man page format.

• DISPLAY

• FIND

• SELECT

• SUMMARY

• QUIT

Relational Operators and KeywordsAll log analysis commands except the DISPLAY command accept a relational operator for any of its arguments. For example, in the key_value argument of the FIND command, you can use the value, 2&&4. This indicates that all records for OPC 2, 3, and 4 are to be extracted. In addition, you must use these relational operators when specifying the key_value argument. For descriptions of these commands and keywords, see the following two tables.

Table 6-1 shows a list of available relational operators.

Table 6-1. Relational Operators

Operator Notation

Equal To =

Not Equal To ~=



The = and ~= operators compare numeric values or ASCII strings. Note that ASCII strings must be enclosed in quotation marks ("). The >=, <=, <, and > operators compare numeric values. The && operator compares an inclusive range of two numeric values. The | operator compares a set of specific numeric values.

To locate particular records in a log file, you can include one of the keywords listed in Table 6-2 in the Log Analysis command. The Log Analysis program searches the log file for records that match the specified criteria. For example, to find all records in the log file LOGSS710 that begin at 12:00, end at 1:30, and contain an SIO of 3, include the FILE, BT, ET, and SIO keywords in the FIND command line as follows:

FIND:FILE=LOGSS710 BT=12:00:00,ET=1:30:00,SIO=3;

Table 6-2 lists the keywords available for searching for a record in a log file.

Greater Than >

Less Than <

Greater Than or Equal To >=

Less Than or Equal To <=

Range &&

A Set of Specific Numbers |

Table 6-2. Keywords for Searching Log File Records (Page 1 of 2)

Keyword Meaning

General Keywords (for searching all records)

BT Begin Time (use last I_Block time stamp)

ET End Time (use last I_Block time stamp)

FILE Log File Name

OFILE Output File Name

I_Block Keywords (for searching I_Block records)

MSG I_Block Message Type

REF I_Block Reference Number

Table 6-1. Relational Operators

Operator Notation



MON I_Block Monitor ID

SCEN I_Block Scenario ID

O_ENT I_Block Originator Entity – Specify as (NNAME,MNAME,ANAME,PNAME,INST)

D_ENT I_Block Destination Entity – Specify as (NNAME,MNAME,ANAME,PNAME,INST)

M_Block Keywords (for searching M_Block records)

TIME M_Block Time Stamp

CA_LNK M_Block CASL Control Physical Link ID

CA_SRC M_Block CASL Control Source Field

CA_SND M_Block CASL Control Message Sender

CA_CNT M_Block CASL Control Lost M_Block Count

M_Block Keywords (for searching M_Block records – continued)

SC_MSG M_Block SCCP Message Type

SC_PRO M_Block SCCP Protocol

MT_MSG M_Block MTP Control Message ID

MT_SEQ M_Block MTP Control Sequence Number

MT_SID M_Block MTP Sender ID

MT_SZ M_Block MTP Message Size

BIB M_Block L2 BIB-BSN

FIB M_Block L2 FIB-FSN

LI M_Block L2 LI

SIO M_Block SIO

DPC M_Block DPC

OPC M_Block OPC

SLS M_Block SLS

HO1 M_Block H0-H1 Code

Table 6-2. Keywords for Searching Log File Records (Page 2 of 2)

Keyword Meaning



Displaying and Analyzing a Log File Trace Dump (DISPLAY Command) The DISPLAY command displays each record’s field, starting with the I_Block header, and followed by the data contents.

Menu Selection ModeSelect the Display option from the Log Analysis Commands menu and respond to the system prompts to display the record fields.

MML Command FormatThe MML command format for the DISPLAY command is:

DISPLAY:FILE=logfile;

The logfile argument specifies the BITE log to display. Be sure to include the complete path name of the log file in the logfile argument. Otherwise, the command returns an error.

If the record is an IPC message, the data is displayed in hexadecimal format. If the record data is an SS7 message (M_Block), then the display is further broken down to the L2, SIO, DPC, OPC, SLS, and MTP message types, and hexadecimal data dumps (SCCP and TCAP message contents).

• If the log contains IPC messages, see the SINAP/SS7 iblock.h include file to decode the message type. You can then use the appropriate .h file to decode the message structure.

• If the log contains SS7 or LNK messages, use the SINAP/SS7 mblock.h include file to determine the message type and structure. You may also need to refer to the appropriate CCITT or ANSI Recommendations to decode messages; however, the Log Analysis program performs most of this decoding for you.

Saving the BITE Log FileOnce the file is displayed in the Log Analysis program, you can save it to a system file by entering the following command at the Log Analysis prompt (:). For filename, specify the path name of the system file to which you want to save the BITE log. If you do not specify a full path name, the system saves the file to the default BITE log directory, $SINAP_HOME/Logs/bite.

s filename

N O T EUntil the BITE log is saved to a system file, you can only examine it by means of BITE Log Analysis commands. Once you save the log to a system file, you can examine it by using any of the system’s standard display utilities (for example, vi, page, or cat).



Sample Log File DisplaysFigure 6-13 shows a sample display of the log file test1.23sep, which is located in the default directory for BITE log files ($SINAP_HOME/Logs/bite).

Figure 6-13. BITE Log Analysis Command Sample

Figure 6-14 shows a sample IPC data record. (See the SINAP/SS7 iblock.h include file for a description of the fields in the I_Block, in which the IPC data is stored.)

Figure 6-14. Sample IPC Data Record

************************** BITE LOG ANALYSIS **************************The Syntax of the MML Command is:

COMMAND:PARAMETER=[OPERATION]VALUE,...;DISPLAY:file=/user/sinap/Logs/bite/test1.23sep

******************** DISPLAY LOG RECORD FILE ********************IPC Data: Record= 0001 Timestamp Index= 2Time: 18:32:14:156 Tsid= 02 ( Appl= BI, Proc= LF )Time: 18:32:14:156 Tsid= 01 ( Appl= BI, Proc= MI ) Transaction: MSG= 0X00000003 REF= 5 MON= 2 SCEN= 0 Originator: NODE= N1 MOD= M1 APPL= BI PROC= MI INST= 1 Destination: NODE= N1 MOD= M1 APPL= NM PROC= TH INST= 1 Message: MORE= 0 LEN= 201 RET CODE= 29IPC data: e1 80 16 0b 4e 31 2c 4d 31 2c 42 49 2c 4d 49 16 - a...N1,M1,BI,MI. 14 31 39 39 38 2d 31 31 2d 30 33 20 20 31 38 3a - .1998-11-03 18: 33 32 3a 31 34 16 00 02 01 06 16 32 53 54 41 52 - 32:14......2STAR 54 2d 4d 4f 4e 3a 45 4e 54 3d 28 49 50 43 2c 4e - T-MON:ENT=(IPC,N 31 2c 4d 31 2c 42 49 2c 4d 49 29 2c 44 49 53 50 - 1,M1,BI,MI),DISP 3d 59 2c 4c 4f 47 3d 69 70 63 2e 6c 6f 67 02 01 - =Y,LOG=ipc.log.. 1d 16 4c 2d 2d 2d 2d 74 69 6d 65 2d 2d 2d 2d 20 - ..L----time---- 2d 2d 2d 6f 72 69 67 2d 2d 2d 20 2d 2d 2d 64 65 - ---orig--- ---de 73 74 2d 2d 2d 20 2d 2d 6d 73 67 5f 74 79 70 65 - st--- --msg_type 2d 2d 20 73 69 7a 65 20 2d 2d 2d 2d 2d 2d 2d 2d - -- size -------- 2d 2d 64 61 74 61 2d 2d 2d 2d 2d 2d 2d 2d 2d 16 - --data---------. 00 16 00 16 00 00 00 f3 80 16 0c 20 20 42 49 2c - .......s... BI, 20 20 4d 49 2c 4f 4b 00 00 - MI,OK..******************** DISPLAY LOG RECORD FILE ********************



Figure 6-15 shows the format of an MSU data record with UDT and SCCP messages. Each record contains up to eight timestamp fields. The Log Analysis program displays the last logged time first and the first logged time last, and it extracts the records according to the last logged time. For a description of the fields in the M_Block, which contains the MSU data, see the SINAP/SS7 mblock.h include file.



Figure 6-15. Display Log Record File Sample

The screen for an MSU data record with UDT and SCCP messages continues giving a breakdown of the message components, as shown in Figure 6-16.

******************** DISPLAY LOG RECORD FILE ********************MSU data: Record= 0001 Timestamp Index= 3Time: 17:54:49:156 Tsid= 04 ( Appl= , Proc= )Time: 17:54:49:156 Tsid= 06 ( Appl= , Proc= )Time: 17:54:49:000 Tsid= 07 ( Appl= , Proc= ) Transaction: MSG= 0X00000105 REF= 0 MON= 1 SCEN= 0 Originator: NODE= N1 MOD= M1 APPL= BI PROC=_LNK INST= 0 Destination: NODE= N1 MOD= M1 APPL= BI PROC= 0 INST= 0 Message: MORE= 0 LEN= 300 RET CODE= 0M_BLOCK header: BITE_Control: CMD= 0 QUAL= 0 LINK= 0 PID1= 0 PID2= 0 RW= 0 MON= 0 CASL_Control: LOST CNT= 00 PID= 0 LINK= 0x0000 SENDER= 0 IBLK= 0 RW= R MON= 1 SSN_SIO= 0 TCAP_Control: MSG= 0 TRANS= 00 ABORT TYPE= 0 ABORT CAUSE= 0 SCCP_Control: CTRL= 0 SRC= 0 DEST= 0 SLS5= 0x00 ERROR= 0 PRIO= 0SEQ= 0 MTP_Control: MSGID= 0x11 SEQID= 00 MSGTYPE= 5 SENDID= 170 MSGSIZE= 124 MTP user data: (HEX) 00 00 12 22 20 00f4 a0 SS#7 data: L2: BIB= 179 FIB= 181 LI= 63 SIO= 0x03 (NI= 00, SI= 03) SCCP DPC= 01-119-03(3003) OPC= 01-085-02(2730) SLS= 06Message Block: (HEX) Length= 116-------------- 09 80 03 07 0b 04 43 bb 0b fd 04 43 aa 0a fe 64 - ......C;.}.C*.~d 62 62 48 04 00 1e 00 ab 6c 5a a1 2b 02 01 66 06 - bbH....+lZ!+..f. 02 83 01 f2 22 aa 0b 84 09 01 00 21 0a 08 60 06 - ...r"*.....!..`. 99 11 84 07 02 00 21 06 02 21 42 84 06 07 00 01 - ......!..!B..... 03 22 04 df 45 01 17 a1 2b 02 01 67 06 02 83 01 - ."._E..!+..g.... f2 22 aa 0b 84 09 01 00 21 0a 08 60 06 99 11 84 - r"*.....!..`.... 07 02 00 21 06 02 21 42 84 06 07 00 01 03 22 04 - ...!..!B......". df 45 01 17 - _E..



Figure 6-16. MSU Data Record Sample

Message Breakdown: ------------------ SCCP Message: Unidata (UDT): Message Type= 0x09 Protocol class: (M), Value=0x80 Return=1000, Class (COS)=0000 Called address offset=0x03, Calling address offset=0x07 Data offset=0x0b Called party address: (V), Length= 4, Value=0x43bb0bfd Address indicator: National ind.=0, Routing=1, Globaltitle=000 PC ind=1, PC= 0xbbb (3003), SSN ind=1, SSN=0xfd(253) Calling party address: (V), Length= 4, Value=0x43aa0afe Address indicator: National ind.=0, Routing=1, Globaltitle=000 PC ind=1, PC= 0xaaa (2730), SSN ind=1, SSN=0xfe(254) TCAP Message: Total Message Length= 0x64(100) Message Type Tag= BEGIN Message Length= 0x62(98) Transaction Information: Originating ID tag= 0x48 Transaction ID length= 0x04 Transaction ID= 0x00 0x1e 0x00 0xab Component Portion Tag= 0x6c Comp Portion Length= 0x5a(90) Component Type Tag= INVOKE Component Length= 0x2b(43) Component Information: Invoke ID: Tag= 0x02 Len= 0x01 ID= 0x66 Operation Code: Tag= 0x06 Len= 0x02 Code= 0x83 0x01 Parameter Code Tag= 0xf2 Parm Code Length= 0x22(34) Parameters: (HEX) aa 0b 84 09 01 00 21 0a 08 60 06 99 11 84 07 02 00 21 06 02 21 42 84 06 07 00 01 03 22 04 df 45 01 17 Component Type Tag= INVOKE Component Length= 0x2b(43) Component Information: Invoke ID: Tag= 0x02 Len= 0x01 ID= 0x67 Operation Code: Tag= 0x06 Len= 0x02 Code= 0x83 0x01 Parameter Code Tag= 0xf2 Parm Code Length= 0x22(34)

Parameters: (HEX) aa 0b 84 09 01 00 21 0a 08 60 06 99 11 84 07 02 00 21 06 02 21 42 84 06 07 00 01 03 22 04 df 45 01 17



Figure 6-17 shows the BITE log file record for an inactivity test message.

Figure 6-17. Sample BITE Log for Inactivity Test Message

******************** DISPLAY LOG RECORD FILE ********************MSU data: Record= 0001 Timestamp Index= 0Time: 16:54:48:980 Tsid= 04 ( Appl= , Proc= )Time: 16:54:48:980 Tsid= 06 ( Appl= , Proc= )Time: 16:54:48:900 Tsid= 09 ( Appl= , Proc= )Time: 16:54:48:870 Tsid= 05 ( Appl= , Proc= )Time: 16:54:48:870 Tsid= 03 ( Appl= , Proc= )

Transaction: MSG= 0X00000105 REF= 0 MON= 1 SCEN= 0 Originator: NODE= N1 MOD= M1 APPL= SO PROC= SO INST= 1 Destination: NODE= N1 MOD= M1 APPL=_DRV PROC=_DRV INST= 1 Message: MORE= 0 LEN= 195 RET CODE= 0M_BLOCK header: BITE_Control: CMD= 0 QUAL= 0 LINK= 0 PID1= 0 PID2= 0 RW= 0 MON= 0 CASL_Control: LOST CNT= 00 PID= 0 LINK= 0x0080 SENDER= 13115 IBLK= 0 RW= W MON= 1 SSN_SIO= 0 TCAP_Control: MSG= 0 TRANS= 00 ABORT TYPE= 0 ABORT CAUSE= 0 SCCP_Control: CTRL= 4 SRC= 3 DEST= 4 SLS5= 0x00 ERROR= 0 PRIO= 0 SEQ= 0 MTP_Control: MSGID= 0x10 SEQID= 00 MSGTYPE= 0 SENDID= 0 MSG SIZE= 19 MTP user data: (HEX) 10 0e 00 00 00 00 00 00SS#7 data: L2: BIB= 0 FIB= 0 LI= 0 SIO: (NI= 02, SI= 03) DPC= 01-085-02(2730) OPC= 01-085-02(2730) SLS= 14Message Block: (HEX)-------------- 10 01 00 0c 09 00 0c 03 00 00 08 - ...........Message Breakdown:------------------ Message Type= 0x10 SC_INACTIVITY_TEST (IT) Length= 11 Destination local ref= 0x01000c Source local ref= 0x09000c Protocol class= 0x03 Sequencing/segmenting: Seq.Num P(S)=0, Seq.Num P(R)=0, More=0



Figure 6-18 shows the BITE log file record for a data acknowledgment message.

Figure 6-18. Sample BITE Log for Data Acknowledgment Message

******************** DISPLAY LOG RECORD FILE ********************MSU data: Record= 0002 Timestamp Index= 0Time: 08:44:24:990 Tsid= 04 ( Appl= , Proc= )Time: 08:44:24:990 Tsid= 06 ( Appl= , Proc= )Time: 08:44:25:010 Tsid= 09 ( Appl= , Proc= )Time: 08:44:24:990 Tsid= 05 ( Appl= , Proc= )Time: 08:44:24:990 Tsid= 03 ( Appl= , Proc= )

Transaction: MSG= 0X00000105 REF= 0 MON= 5 SCEN= 0 Originator: NODE= N1 MOD= M1 APPL=_DRV PROC=_DRV INST= 1 Destination: NODE= N1 MOD= M1 APPL=S23S PROC=SEND INST= 1 Message: MORE= 0 LEN= 194 RET CODE= 0M_BLOCK header: BITE_Control: CMD= 0 QUAL= 0 LINK= 0 PID1= 0 PID2= 0 RW= 0 MON= 0 CASL_Control: LOST CNT= 00 PID= 0 LINK= 0x0080 SENDER= 15734 IBLK= 0 RW= R MON= 5 SSN_SIO= 233 TCAP_Control: MSG= 0 TRANS= 00 ABORT TYPE= 0 ABORT CAUSE= 0 SCCP_Control: CTRL= 15 SRC= 3 DEST= 6 SLS5= 0x00 ERROR= 0 PRIO= 0 SEQ= 0 MTP_Control: MSGID= 0x18 SEQID= 00 MSGTYPE= 0 SENDID= 0 MSG SIZE= 18 MTP user data: (HEX) 10 06 00 00 00 00 00 00SS#7 data: L2: BIB= 0 FIB= 0 LI= 0 SIO: (NI= 02, SI= 03) DPC= 01-085-02(2730) OPC= 01-085-02(2730) SLS= 06Message Block: (HEX)-------------- f0 06 00 0c 00 02 01 02 - p.......Message Breakdown:------------------ Message Type= 0xf0 SC_DATA_ACK_NEC Length= 10 Destination local ref= 0x06000c Sequencing/segmenting: Seq.Num P(S)=0, Seq.Num P(R)=1, More=0 Data:Pointer=0x01, Length= 2, Data message: 00 00 - ..



Finding Records that Fit All Specified Criteria (FIND Command)The FIND command extracts the records from a log file that satisfies all criteria specified in the command’s arguments.

Menu Selection ModeSelect the FIND option on the BITE Log Analysis Commands menu and respond to the system prompts to find specific records from a log file.

MML Command FormatThe MML command format for the FIND command is:

FIND:FILE=logfile,OFILE=file,key=key_value;

Table 6-3 describes the arguments for the FIND command.

Sample Log File ExtractionThe sample shown in Figure 6-19 extracts all the records in the LOGSS710 log file that begin at 12:20, end at 2:30, have a DPC of 1-1-8, an OPC of 1-1-8, and contain an SIO of 3. The records that meet these criteria are written to the file called TSTSUM.

Figure 6-19. Sample FIND Command Argument

Table 6-3. FIND Command Arguments


logfile Specifies the name of the log file to open by searching the Logs/bite directory for the appropriate log file.

file Specifies the name of the file to which extracted records are saved.

key Specifies a key word from the fields in the log file record. For permissible values, see Table 6-2.

key_value Specifies the value to search for in the MSU; for example, a beginning and ending time range (BT and ET), destination point code (DPC), and signaling information octet (SIO). The value of key_value is dependent on the value of key. You can specify more than one key and key_value.

FIND:FILE=LOGSS710,OFILE=TSTSUM,BT=12:20:00,ET=2:30:00,DPC=1-1-8,OPC=1-1-8,SIO=3;



Selecting Records That Satisfy Any Specified Condition (SELECT Command)The SELECT command extracts the records from a log file that satisfy any of the criteria specified in the command’s arguments.

Menu Selection ModeSelect the Select option on the BITE Log Analysis Commands menu and respond to the system prompts to find records containing any part of the requested criteria.

MML Command FormatThe MML command format for the SELECT command is:

SELECT:FILE=logfile,OFILE=file,key=key_value;

Table 6-4 describes the arguments for the SELECT command.

Sample Log File ExtractionThe sample shown in Figure 6-20 extracts all records from the LOGSS710 log file that have a DPC of 1-1-8, or an OPC of 1-1-8. The records that meet either of these criteria are written to the TSTSUM file.

Figure 6-20. Sample SELECT Command Argument

Table 6-4. SELECT Command Arguments


logfile Specifies the name of the log file to open.


key Specifies a key word from the fields in the log file record. Valid values are listed in Table 6-2.

key_value Specifies the value to search for in the MSU. For example, a beginning and ending time range (BT and ET), destination point code (DPC), and signaling information octet (SIO). The value of key_value is dependent on the value of key. You can specify more than one key and key_value.

SELECT: FILE=LOGSS710,OFILE=TSTSUM,DPC=1-1-8,OPC=1-1-8



Obtaining Summary Count of Records Matching Specified Criteria (SUMMARY Command)The SUMMARY command counts the records in the specified log file. A record is counted if it contains the values specified in the command’s arguments.

Menu Selection ModeSelect the SUMMARY option on the BITE Log Analysis Commands menu to summarize records with specified values.

MML Command FormatThe MML command format for the SUMMARY command is:

SUMMARY:FILE=logfile,OFILE=file,key=key_value;

Table 6-5 describes the arguments for the SUMMARY command.

Sample Record ExtractionThe sample shown in Figure 6-21 extracts all records from the record log called LOGSS710, using the key values, MSG and CA_LNK, and writes these records to a file called TSTSUM.

Figure 6-21. Sample SUMMARY Command Argument

Table 6-5. SUMMARY Command Arguments


logfile Specifies the name of the log file to open.


key Specifies a key word from the fields in the log file record. Valid values are listed in Table 6-2.

key_value Specifies the value to search for in the MSU. For example, a beginning and ending time range (BT and ET), destination point code (DPC), and signaling information octet (SIO). The value of key_value is dependent on the value of key. You can specify more than one key and key_value.

SUMMARY:FILE=LOGSS710,OFILE=TSTSUM,MSG=X105,CA_LNK=32;******************** LOG FILE SUMMARY File:TSTSUM *******************FILE/home/sinap/Logs/bite/LOGSS710Total records: 2 MSG: 2CA_LNK: 1

EOF



Exiting the Log Analysis Program The QUIT command terminates the BITE log analysis program and returns you to the SINAP/SS7 login window from which you accessed the program.

Menu Selection ModeSelect the Quit option on the BITE Log Analysis Commands menu.

MML Command FormatYou can specify the QUIT command in any of the following formats:

• QUIT:;

• QUIT:

• QUIT


Appendix ANetwork Information and

Planning FormsA-

Photocopy these blank network information and planning forms as needed to use in planning your network before entering configuration information in the SINAP/SS7 database.

Network Information and Planning Forms A-1

Network Information and Planning Forms

A-2 SINAP/SS7 User’s Guide R8051-17


Link Information for Node:

Link Set ** Type ADPC** Combined

Link Set Member Link Sets

Link Port # Priority Link Set

Name SLC Speed

** ANSI network variant only



SINAP Node:

OPC: *FOPC:

Application Name SSN

* ANSI Variant Only



Application Routing for Node:

Route Sets

Route Set Name

DPC or**Routing Method

Routes(Lset or Lset and **Clset)

Concerned Point Codes

Local SSN ConcernedPoint Code

Duplicate ConcernedPoint Code

** ANSI network variant only



Remote Subsystems for Node:

Point Code:

Remote SSNs

Point Code:

Remote SSNs



G l o b a l T i t l e T r a n s l a t i o n ( G T T )

G lo b a l T i t l e I n d ic a t o r ( G T I ) :

T r a n s la t i o n T y p e ( T T ) :

N u m b e r i n g P la n ( N P ) :

N a t u r e - o f - A d d r e s s I n d ic a t o r ( N O A I ) :

L o w A d d r e s s I n f o r m a t i o n ( L A D D R ) :

H ig h A d d r e s s I n f o r m a t io n ( H A D D R ) :

R e p la c e m e n t D e s t in a t io n P o in t C o d e ( D P C ) ( O p t io n a l ) :

B a c k u p D e s t in a t io n P o in t C o d e ( D P C 2 ) ( O p t io n a l ) :

R e p la c e m e n t S u b s y s t e m N u m b e r ( S S N ) ( O p t io n a l ) :

B a c k u p S u b s y s t e m N u m b e r ( S S N 2 ) ( O p t io n a l ) :

R e p la c e m e n t A d d r e s s I n f o r m a t i o n ( N A D D R ) :


Appendix B SINAP/SS7 Environment

VariablesB-

This section lists and describes the environment variables for the SINAP/SS7 system and explains how to define them on the UNIX system.

Defining SINAP/SS7 Environment VariablesEnvironment variables define and activate operating characteristics on the SINAP node. The SINAP environment file $SINAP_HOME/Bin/sinap_env_var.[sh|csh] contains all SINAP/SS7 environment variables. Although most of the environment variables are disabled (commented out), some are activated (uncommented) during software configuration when you use the /etc/config_sinap script to configure the SINAP node.

N O T EYou must activate all environment variables to be enabled on a SINAP node before you start or restart the SINAP node.

Enabling Environment VariablesTo activate an environment variable, do the following:

1. Stop SINAP.

2. Uncomment the relevant line(s) in the $SINAP_HOME/Bin/sinap_env.[sh|csh] file for that variable. The lines usually appear as follows:

<variable-name>=<value>export <variable-name>

3. Log off and then log back into your SINAP account.

4. Use the env command to verify the new environment variable is set.

5. Start SINAP.

Note that for many of the environment variables, you do not need to assign values. The description associated with each environment variable in the SINAP environment file provide the valid setting(s), if required, for the variable.

SINAP/SS7 Environment Variables B-1

The SINAP Environment File

Disabling Environment VariablesTo deactivate an environment variable, do the following:

1. Stop SINAP.

2. Comment out the relevant line(s) in the $SINAP_HOME/Bin/sinap_env.[sh|csh] file for that variable. The lines usually appear as follows:

<variable-name>=<value>export <variable-name>

3. Log off and then log back into your SINAP account.

4. Use the env command to verify the environment variable is no longer set.

5. Start SINAP.

The SINAP Environment FileThis section provides the contents of the SINAP Environment file ($SINAP_HOME/Bin/sinap_env_var.sh) for the Bourne shell.

N O T EThe sinap_env_var.[sh|csh] files is a template, which is copied to $SINAP_HOME/Bin/sinap_env.[sh|csh] when the SINAP node is created via /etc/config_sinap "a" option.

sinap_env_var.sh (for Bourne Shell)#Environment Variable Description#==================================================##MANPATH /usr/share/man Enables the display of OS and # SINAP/MultiStack man pages. The # Installation script creates .login # and .profile files for sinap and # sysopr users and appends the SINAP # man page directory name to the # MANPATH variable for each user.## Variable is set through /etc/config_sinap #PATH /usr/ucb Ensures you can display both OS and # SINAP/MultiStack man pages.

#SINAP_ALT_MEASUREMENT_INTERVAL Specifies the reporting interval for # measurement reports (REPORT-MALL, # REPORT_MTP, REPORT_MSCCP, and # REPORT_MTCAP). Valid reporting

B-2 SINAP/SS7 User’s Guide R8051-17


# intervals are: # Value Measurement Interval (Minutes)# ----- -----------------------------# 0 or 30 30# 1 or 15 15# 2 or 5 5# # If set to 0 or not defined, SINAP uses # a 30-minute measurement interval.#SINAP_ALT_MEASUREMENT_INTERVAL=<value>#export SINAP_ALT_MEASUREMENT_INTERVAL

#SINAP_CONSOLE_ALARM_LEVEL Specifies the severity level of alarms that# SINAP/Multistack logs to the system error# log file. Valid alarm values are:## Value Description of Condition# ------- --------------------------------# CRITICAL Causes severe service disruption# and requires immediate attention# (be sure to specify 'critical' # in the Severity field of the # message format as defined in the # Emsg file).## MAJOR Causes serious service disruption.# Be sure to specify either # 'NONRECOVERABLE_L' or# NONRECOVERABLE_LP - the problem # cannot resolve itself and no # acceptable alternative exists # to address situation - in the # Severity field of the message # format as defined in Emsg file.# # MINOR Is not likely to cause a serious# service disruption (be sure to # specify INFP_L or INFO_LP in the# severity field of the message # format as defined in Emsg file). ## NOTICE Message is provided for # informational purposes only.##SINAP_CONSOLE_ALARM_LEVEL=<value> #export SINAP_CONSOLE_ALARM_LEVEL

#SINAP_HEALTH_INTERVAL Specifies the time interval (in seconds) # for sending health-check requests # (default is 60 sec.).#SINAP_HEALTH_INTERVAL=<value> # Variable is set through /etc/config_sinap

#SINAP_HEALTH_TIMEOUT Defines the interval (in seconds) within



# which a process must respond to a # health-check request. If two consecutive# health-check requests fail, the process# is considered to have failed and trouble# management takes control (default is # 60 sec.) #SINAP_HEALTH_TIMEOUT=<value> # Variable is set through /etc/config_sinap

#SINAP_HOME Specifies the path name of your SINAP # account. For example, /home/sinap. #SINAP_HOME=<value># Variable is set through /etc/config_sinap

#SINAP_HOME/Bin Adds the directory $SINAP_HOME/Bin# to your PATH environment ## Variable is set through /etc/config_sinap

#SINAP_MML_LEVEL Defines the privilege level for # executing MML commands through the # Terminal Handler. Valid range is 0-255# (default is 5).#SINAP_MML_LEVEL=<value>#export SINAP_MML_LEVEL

#SINAP_LOG_SIZE Defines the size (in bytes) of the # Software Notebook and Alarm Log. The # MML report commands such as REPORT-ALARM # and REPORT-MALL) use this variable # (default value is 1000000 bytes).#SINAP_LOG_SIZE=<value># Variable is set through /etc/config_sinap

#SINAP_MDF Defines the path name of the Terminal # Handler's Menu Definition file.#SINAP_MDF=<value>#export SINAP_MDF

#SINAP_MODULE Specifies the module name assigned to a # SINAP/MultiStack system (default is M1). # You define this variable when you # configure the SINAP node using the # etc/config_sinap script.#SINAP_MODULE=<name># Variable is set through /etc/config_sinap

#SINAP_NODE Specifies the name assigned to a SINAP # node within a module (default is N1). # You define this variable when you # configure the SINAP node using the # etc/config_sinap script.#SINAP_NODE=<name># Variable is set through /etc/config_sinap



#SINAP_VARIANT Defines the network variant of the # SINAP node installed on the system. # Valid values are CCITT, ANSI, TTC, # NTT, and China. You define this# variable on the SINAP node using # the etc/config_sinap script. #SINAP_VARIANT=<value># Variable is set through /etc/config_sinap

#ENHANCED MESSAGE DISTRIBUTION#=============================

#DISCARDS_PER_ALARM Specifies the number of MSUs the # SINAP node discards before generating # an alarm.#DISCARDS_PER_ALARM=<value>#export DISCARDS_PER_ALARM

#UDTS_NO_OPC Specifies whether or not the SINAP # node generates a unitdata service # (UDTS) message when the MSU's # Originating Point Code (OPC)is not # valid for the Specified Subsystem # Number (SSN).#UDTS_NO_OPC=1#export UDTS_NO_OPC

#NETWORK VARIANT FEATURES#=============================

#ANSI_SINAP_FOPC (ANSI only). Activates the fictitious # Originating Point Code (FOPC) feature. #ANSI_SINAP_FOPC=YES#export ANSI_SINAP_FOPC

#TTC_WITH_NSTATE (TTC, NTT only). Enables applications # to support Concerned Point Codes # (CPCs), which are responsible for # sending User-in-Service(UIS) messages # and User-Out-of-Service (UDS) messages.#TTC_WITH_NSTATE=1#export TTC_WITH_NSTATE

#CCITT_CONGESTION_OPTION (CCITT and China only). Specifies one of # the following methods used to handle link # congestion: ## INTERNATIONAL_1_CONGESTION # NAT_MUL_CONG_WITH_PRIO# NAT_MUL_CONG_WO_PRIO##INTERNATIONAL_1_CONGESTION Specifies the international signaling # network option (the default), which # provides a single congestion onset # threshold and abatement threshold.



##CCITT_CONGESTION_OPTION=INTERNATIONAL_1_CONGESTION#export CCITT_CONGESTION_OPTION

#NAT_MUL_CONG_WITH_PRIO Specifies the national signaling network # option, multiple signaling link congestion # levels with congestion priority. In the# CCITT and China network variants, this # option allows client applications to # set congestion priority based on multiple # congestion levels (0-3). This option uses# these thresholds:## Congestion Onset (CONON1, CONON2, CONON3)# Congestion Abatement (CONAB1, CONAB2, # CONAB3)# Congestion Discard (CONDIS1, CONDIS2, # CONDIS3)## NOTE: ANSI, TTC, and NTT network variants# automatically implements this national # signaling network option (no environment # variable is required).##CCITT_CONGESTION_OPTION=NAT_MUL_CONG_WITH_PRIO#export CCITT_CONGESTION_OPTION

#NAT_MUL_CONG_WO_PRIO Defines the national signaling network # option, multiple signaling link congestion # levels without congestion priority. For the # CCITT and China network variants, this # option allows the SINAP node to define up # to four levels (0-3) of link congestion # and to set a link's congestion status # according to those levels. When you set # this option, you must also specify # values for all the following environment # variables:## CONGESTION_STATUS# CONGESTION_INITIAL_VALUE# CONGESTION_TX_TIMER# CONGESTION_TY_TIMER##CCITT_CONGESTION_OPTION=NAT_MUL_CONG_WO_PRIO#export NAT-MUL_CONG_WO_PRIO

#CONGESTION_STATUS Specifies the level (0,1,2, or 3) of link# congestion supported. The value 2 specifies# that the SINAP node supports three levels # (0, 1, and 2) of link congestion. The value# 3 specifies support for all four link # congestion levels (0, 1, 2, and 3). # #



#CONGESTION_STATUS=<value>#export CONGESTION_STATUS

#CONGESTION_INITIAL_VALUE Defines the link congestion threshold# used to determine the occurrence# of congestion on a link. The Valid range # is 1-3. #CONGESTION_INITIAL_VALUE=<value>#export CONGESTION_INITIAL_VALUE

#CONGESTION_TX_TIMER Defines the interval in seconds between# congestion onset measurements. valid range# is 1-255 (default is 1). When this timer # expires, the SINAP node counts the number # of MSUs on the link's SS7 driver queue.# If the number of MSUs exceeds the value # of the congestion onset threshold, the # SINAP node increments the link's # congestion status by 1. #CONGESTION_TX_TIMER=<value>#export CONGESTION_TX_TIMER

#CONGESTION_TY_TIMER Defines the interval in seconds between# congestion abatement measurements. The# Valid range is 1-255 (default is 1).#CONGESTION_TY_TIMER=<value>#export CONGESTION_TY_TIMER

#RST_CONFIG_INIT_PROHIBIT (CCITT only). Allows a newly created and # configured route set to be initialized# in the PROHIBITED state instead of the # ALLOWED state. This feature applies only # if the new route set being created and # configured is for a remote signaling # point in the network and not for an # adjacent point code (a signaling point # that is connected directly through a # link set to the SINAP node). For an # adjacent signaling point (including # adjacent STPs), the route set status # should be ALLOWED. ## The interaction of this feature with MTP # restart is as follows:# # If the SINAP node is performing MTP restart,# the new route sets configured during the# restart are set to the ALLOWED state. The# Adjacent STPs are responsible for sending # the appropriate Transfer Prohibited (TFP), # Transfer Restricted (TFR), or Transfer# Allowed (TFA) messages to the SINAP node # during the restart procedure.## If you use send_cm or sysopr to create



# and configure a new route set to a # nonadjacent signaling point when SINAP # is not performing MTP restart, the route # set state is set to PROHIBITED.## Also, the SINAP node sends signaling # Route Set Test (RST) messages to the # adjacent STPs for prohibited destinations # for which the new route sets were # configured. The node sends the RST # messages every timer T10 seconds until # the STPs send TFA messages to the# SINAP node.#RST_CONFIG_INIT_PROHIBIT=1#export RST_CONFIG_INIT_PROHIBIT

#LPC_ROUTING (CCITT, ANSI, China only). Enables the # Distributed Logical Point Code (DLPC) # feature that supports distributed ISUP # applications on two SINAP nodes. The # two ISUP applications are Logical Point# Codes (LPCs) that appear to the SS7 # network as a pair of Signaling Transfer # Points (STPs). Note that use of this # feature requires significant application # modifications. #LPC_ROUTING#export LPC_ROUTING

#MTP ENHANCED FUNCTIONALITY#=============================

#MTP_ANSI88_RSR_RST (ANSI only). Enables Transfer-Restricted # (TFR) message handling on the SINAP node # based on 1988 ANSI standards for MTP. # The node responds immediately to TFR or # TFP messages by sending Signaling Route # Set Restricted or Prohibited (RSR or RSP)# messages without waiting for the T10 # timer to expire.#MTP_ANSI88_RSR_RST=1 #export MTP_ANSI88_RSR_RST

#MTP_ANSI92_MANAGEMENT_INHIBIT (ANSI only). Enables management inhibiting# based on the 1992 ANSI Standards for MTP. # This variable allows a SINAP node to repeat# a Link-Forced Uninhibit(LFU) message once# when the far end does not respond to the # first LFU request message with a Link # Uninhibit Acknowledgement (LUN) message.# If the SINAP node does not receive a LUN # message from the far end, it discontinues # the request, then sends a Link Uninhibit # Acknowledgment (LUA) message and starts # traffic on previously inhibited links. If



# you do not define this variable, the SINAP # node implements management inhibiting # based on 1988 ANSI Standards for MTP.#MTP_ANSI92_MANAGEMENT_INHIBIT=1#export MTP_ANSI92_MANAGEMENT_INHIBIT

#MTP_ANSI92_RESTART (ANSI only). Enables the MTP restart # feature which provides an orderly process # for activating the SINAP node's links and # routes when you start or restart the node. # This features is based on the 1992 ANSI # standards for MTP.#MTP_ANSI92_RESTART=1#export MTP_ANSI92_RESTART

#MTP_ANSI92_TCCO (ANSI only). Enables MTP timed-controlled # changeover (TCCO) functionality when the # SINAP node receives a processor outage # indication on a link at the remote end.# This feature is based on the 1992 ANSI# standards for MTP.# #MTP_ANSI92_TCCO=1#export MTP_ANSI92_TCCO

#MTP_ANSI92_TCD (ANSI only). Enables use of the MTP # Time-Controlled Diversion (TCD) feature, # based on the 1992 ANSI standards for MTP.# TCD is applied when the signaling point # made available at the far end of the link # is currently inaccessible from the signaling# point initiating the changeback order. If # you do not define this variable, the SINAP# node implements TCD functionality based on # the 1990 ANSI standards for MTP.#MTP_ANSI92_TCD=1#export MTP_ANSI92_TCD

#MTP_LINK_DOWN_AFTER_LPO_ENDS Causes MTP processing to bring a link # down after a Local Processor Outage (LPO). # You must use normal link-level recovery # procedures to bring the link back into # service.#MTP_LINK_DOWN_AFTER_LPO_ENDS=1#export MTP_LINK_DOWN_AFTER_LPO_ENDS

#MTP_LINKSET_MEASUREMENT Enables the REPORT-MMTP and REPORT-MALL# reports to display the number of octets# and MSUs transmitted and received per# second on all links configured for a# link set in 30-minute blocks during the# reporting interval specified in the MML# command. The reports also include the# peak octet and MSU values within the # 30-minute interval for the reporting



# period (day, week, month). #MTP_LINKSET_MEASUREMENT=YES#export MTP_LINKSET_MEASUREMENT

#MTP_RCT_LOAD_SHARING_SLS (ANSI only).Enables the generation of # random Signaling Link Selections (SLSs) # for outbound Route Set Congestion Test# (RCT) messages. If you do not define # this variable, the SINAP node implements # processing based on the 1988 ANSI standards# for MTP. Note that always sending the RCT # message on the same link within the same # link set on which the TFC was received # always results in the RCT message testing # the same network path, which may or may not # be congested.#MTP_RCT_LOAD_SHARING_SLS=YES#export MTP_RCT_LOAD_SHARING_SLS

#MTP_SLS4_LOAD_SHARE (CCITT,China). Ensures message sequencing # by routing messages solely on the # Signaling Link Selection (SLS) and # Destination Point Code (DPC). For example,# if a Telephone User Part (TUP) user employs # the Circuit Identification Code (CIC) for # the SLS value for all messages pertaining# to that circuit, all messages go out over # the same link to a particular DPC, even# when loadsharing over two link sets. This# ensures all messages remain in sequence.# However, when loadsharing over link sets,# you can only use 8 links in each link set.# For multiple DPCs and more than 8 links per# link set, you might achieve an even load# distribution, but there is no guarantee.# # If you do not define this variable, the # SINAP node supports 16 links per link set, # with a random choice of link sets when# loadsharing. This ensures even distribution,# but not message sequencing. Note that # enabling this option has no affect on TCAP,# SCCP, or ISUP users. #MTP_SLS4_LOAD_SHARE=1#export MTP_SLS4_LOAD_SHARE

#MTP_USER_FLOW_CTL Sends a User Part Unavailable (UPU) # message to the originating user part # when it receives an incoming message # that it cannot deliver. This feature # is based on the 1993 edition of the# 1993 ITU-T recommendations for MTP. If # you do not define this variable, the# SINAP node implements user flow control# procedures based on the 1988 ITU-T



# recommendations for MTP. For the China # network variant, you must define this # variable.#MTP_USER_FLOW_CTL=1#export MTP_USER_FLOW_CTL

#MTP_WHITE_BOOK_RESTART Enables the MTP restart feature that # provides the orderly process for # activating a node's links and routes # when you start the SINAP node. This# feature is based on the 1993 ITU-T# recommendations for MTP. For the China# network variant, you must define this# variable. #MTP_WHITE_BOOK_RESTART=1#export MTP_WHITE_BOOK_RESTART

#MTP_WHITE_BOOK_SLC Allows the SINAP node to accept certain # types of Signaling Network Management # (SNM) messages that use a Signaling Link# Code (SLC) value other than 0. This feature# is based on the 1993 ITU-T recommendations# for MTP. For CCITT and China network # variants, if you do not define this # variable, the SINAP node implements SLS # procedures based on the 1988 ITU-T# recommendations for MTP. For the ANSI# network variant, this feature is # automatically activated. There is no # need to define this variable.#MTP_WHITE_BOOK_SLC=1#export MTP_WHITE_BOOK_SLC

#MTP_WHITE_BOOK_TCCO (CCITT and China). Enables use of the # MTP Timed-Controlled Changeover (TCCO)# functionality when a processor outage# indication is received on a link at the# remote end. This feature is based on the# 1988 ITU-T recommendations for MTP. If# you do not define this variable, the# SINAP node implements TCCO procedures # based on the 1988 ITU-T recommendations. #MTP_WHITE_BOOK_TCCO=1#export MTP_WHITE_BOOK_TCCO

#MTP_WHITE_BOOK_TFR (CCITT only). Implements the transfer # restricted (national network) message # handling option that is based on 1993 # ITU-T Recommendations for MTP.#MTP_WHITE_BOOK_TFR=1#export MTP_WHITE_BOOK_TFR

#SLTM_NOT_REQUIRED When this environment variable is # defined, the SINAP node does not # initiate a signaling link test message



# (SLTM) or for the TTC network variant, # signaling route test message (SRTM). #SLTM_NOT_REQUIRED=1#export SLTM_NOT_REQUIRED

#SLTM_OPC_CHECK Checks the Originating Point Code (OPC) # in the MTP routing label of the # received Signaling Link Test # message (SLTM) to ensure it matches # the adjacent Destination Point Code # (DPC) to which the link (indicated# by the Signaling Link Code (SLC) of the# SLTM is connected.#SLTM_OPC_CHECK=1#export SLTM_OPC_CHECK

#SLTM_WITH_NAT10_FOR_G500 (CCITT only). Allows the SINAP node to # send a Signaling Link Test Acknowledgment # (SLTA) message in response to a Signaling# Link Test (SLT) message ONLY when the SLT # message contains the value NAT10 in the# subservice field (SSF).#SLTM_WITH_NAT10_FOR_G500=1#export SLTM_WITH_NAT10_FOR_G500

#LOOPBACK_DISPLAY (CCITT only). Enables the SINAP node to# detect when a remote link is in a # loopback mode. In this case, the SINAP # node sets a loopback diagnostic indicator# to display the loopback status on the # DISPLAY-LINK screen.#LOOPBACK_DISPLAY=1#export LOOPBACK_DISPLAY

#DISABLE_MTP_DISCRIMINATION (CCITT only). Disables MTP Level 3 point # code discrimination and allows any MSU# received by the SINAP node (regardless# of Destination Point Code (DPC) to be# routed to the appropriate application# process). The SINAP node discards all # SCCP management MTP management messages# with a DPC that is not equal to own point# code. The SINAP node handles MTP and SCCP # messages with a DPC equal to own point code# according to the 1993 ITU-T recommendations # for MTP and SCCP.#DISABLE_MTP_DISCRIMINATION=1#export DISABLE_MTP_DISCRIMINATION

#SCCP ENHANCED FUNCTIONALITY#============================##RESPONSE_WITHOUT_SSN_CONFIGURED Specifies that the SCCP outbound routing# control of the SINAP node should retain



# all outbound messages that contain remote# SSNs (REMSSNs) that are not configured# on the SINAP node or REMSSNs that are# configured, but not in the ALLOWED # state. If you do not define this # variable, the SINAP node discards all# these outbound messages. #RESPONSE_WITHOUT_SSN_CONFIGURED=1#export RESPONSE_WITHOUT_SSN_CONFIGURED

#REMSSN_INIT_PROHIBIT (CCITT only). Enables the SINAP node to # set the remote SSN status to PROHIBITED# when the remote SSN is created using# the CREATE-REMSSN MML command or when# SCCP Management (SCMG) receives an# MTP-RESUME primitive from MTP_L3RC# after a SINAP MTP restart occurs. #REMSSN_INIT_PROHIBIT=1#export REMSSN_INIT_PROHIBIT

#SCMG_SSP_SST_HANDLING_DISABLED Disables handling of the SCCP management# messages Subsystem Prohibited (SSP) and # Subsystem Test (SST) messages.#SCMG_SSP_SST_HANDLING_DISABLED=1#export SCMG_SSP_SST_HANDLING_DISABLED

#CCITT_XUDT_SCMG (CCITT only). Allows a SINAP node to # receive and process an SCCP Subsystem# Test (SST) in an Extended Unitdata # (XUDT) message. If the SSN specified in # the XUDT message is in the ALLOWED state, # the SINAP node sends a Subsystem Allowed # (SSA) message to the original calling# calling address. If you do not define this# variable, the SINAP node discards any XUDT# SCCP Management (SCMG) messages it receives# because SCMG messages are normally handled# only by Unitdata (UDT) messages.#CCITT_XUDT_SCMG=1#export CCITT_XUDT_SCMG

#TCAP ENHANCED FUNCTIONALITY#===========================##BYPASS_SINAP_GLOBAL_TITLE_TRANSLATION Implements Global Title (GT) addressing# capabilities, instead of Global Title # Translation (GTT). GT addressing # capabilities allow the SINAP node to # pass GT messages without actually # translating the GT. # #BYPASS_SINAP_GLOBAL_TITLE_TRANSLATION=1#export BYPASS_SINAP_GLOBAL_TITLE_TRANSLATION

#GLOBAL_TITLE_SSN_NO_CHECK This variable bypasses the availability



# check of the remote SSN in the SCCP # called party address field of the # outbound message and enables a SINAP # node to send messages to an STP with the# outbound MSU's SCCP called party address# (including SSN, global title, and routing# indicator set to "route on global title")# if the SSN is unknown (SSN=0).#GLOBAL_TITLE_SSN_NO_CHECK=1#export GLOBAL_TITLE_SSN_NO_CHECK

#GTT_BYPASS_NOAI_CHECK Expands the value range for the Nature # of Address (NOAI) indicator field in # global title entries. Valid values for# NOAI can be within the range 1-127.# If you do not define the variable, # the value specified for NOAI can only# be in the range of 1-4.#GTT_BYPASS_NOAI_CHECK=1#export GTT_BYPASS_NOAI_CHECK

#GTT_WITH_BACKUP_DPC_SSN Enables a SINAP node to route MSUs # containing global title information # to an alternate SCCP at a remote node # if the primary SCCP is unavailable. If # both primary and secondary SCCPs are# unavailable, the SINAP node returns a # NOTICE error message.#GTT_WITH_BACKUP_DPC_SSN=1#export GTT_WITH_BACKUP_DPC_SSN

#HEX_GLOBAL_TITLE Enables the use of hexadecimal values# (A-F) in the global title string. If# you do not define this variable, you can# only use decimal numbers (0-9) in global # title strings.# #HEX_GLOBAL_TITLE=1#export HEX_GLOBAL_TITLE

#PARTIAL_GTT Enables the use of partial # Global Title Translation by setting a # maximum and minimum number of digits.# If you do not define this variable, # full GTT will take place. # # When you set this option, you can also# specify values for the following # environment variables:## MAX_PGTT_DIGITS # MIN_PGTT_DIGITS # #PARTIAL_GTT#export PARTIAL_GTT



#MAX_PGTT_DIGITS # Specifies the maximum number of partial # global title digits when PARTIAL_GTT is# set. Valid range is from 1 to # MAX_GLOBAL_TITLE (up to 28 digits). # the default is 6.#export MAX_PGTT_DIGITS=<value>

#MIN_PGTT_DIGITS# Specifies the minimum number of partial # global title digits when PARTIAL_GTT is# set. If the digits in the address to be# translated is less than MIN_PGTT_DIGITS# then full GTT will take place. The # default is 3. #export MIN_PGTT_DIGITS=<value>

#SINAP_XUDT_SEGMENT_SIZE (CCITT, China only). Defines a size for # the message segments that make up an # Extended Unitdata (XUDT) message that # is smaller than the maximum size allowed# (the default) for the network variant # configured on the SINAP node.## Valid values Network Variant# ------------ ------------------------- # 0 - 254 CCITT (default=254 bytes)# 1 - 251 ANSI (default=251 bytes)#SINAP_XUDT_SEGMENT_SIZE=<value>#export SINAP_XUDT_SEGMENT_SIZE

#TCAP_MAX_SIZE_ORIG_TID_ONLY Defines the value of the origination # transaction ID which must be four bytes # long (the maximum allowable size).#TCAP_MAX_SIZE_ORIG_TID_ONLY=1#export TCAP_MAX_SIZE_ORIG_TID_ONLY

#TCRELAY (CCITT only). Enables a SINAP node to # pass the hop counter value received in # an XUDT message to a TCAP application.#TCRELAY=1#export TCRELAY

#INTERPROCESS COMMUNICATIONS#===========================

#GUARANTEED_IPC Ensures that critical Interprocess # Communications (IPC) messages are # delivered to their destinations, even # during period of heavy system load. # Defining this variable changes the# retry_count parameter within the CASL# ca_put_msg() function as follows:



## If retry_count value is 0, the SINAP# node considers the IPC message to be# noncritical and the node does not # generate a critical alarm if it cannot# deliver the message. Instead. the node# returns an error to the user with errno# typically set to EAGAIN.## If retry_count value is greater than 0,# the SINAP node considers the IPC message# to be critical and it makes every effort# to deliver the message, including # restarting the node if necessary. The# ca_put_msg() function call generates a# critical alarm and returns an error only# if the node cannot deliver the message # due to an error condition other than # EAGAIN (for example, the called process # no longer exists.#GUARANTEED_IPC=1#export GUARANTEED_IPC

#MML COMMAND ENHANCEMENTS#========================#SINAP_MML_ALT_NUMERIC_CONVERSION Allows entry of MML values for command# arguments in decimal, octal, or # hexadecimal notation.# # Notation Command Argument Value# -------- ---------------------------# Hexadecimal 0x or 0X, followed by value# Decimal Value only (no prefix needed) # Octal 0, followed by the value#SINAP_MML_ALT_NUMERIC_CONVERSION=1 #export SINAP_MML_ALT_NUMERIC_CONVERSION

#SINAP_MML_PRINT_RESPONSE Enables the automatic printing feature # in MML commands that includes the PRINT # argument. If you specify a printer in the# PRINT argument of an MML command, the# specified printer automatically prints # the command and all its output. The # feature remains active until you exit # the login session. You can specify a # different printer within a login session # by changing the printer defined in the# PRINT argument of the MML command. #SINAP_MML_PRINT_RESPONSE=1#export SINAP_MML_PRINT_RESPONSE

#SINAP_MML_PRINT_TTYNAME Allows the TTY name to be printed on the# printed output of a measurement-# reporting command. The TTY name # identifies the sysopr window from which



# the MML command was issued.#SINAP_MML_PRINT_TTYNAME=1#export SINAP_MML_PRINT_TTYNAME

#CONNECTION-ORIENTED SERVICES#=============================#SINAP_LRN_FREEZE_TIMEOUT Defines the number of seconds (up to # 1800) before an unused LRN is released# and can be assigned to another LRM # structure. #SINAP_LRN_FREEZE_TIMEOUT=<value>#export SINAP_LRN_FREEZE_TIMEOUT

#SINAP_TOTAL_LR_MEMS Defines the number of Local Reference # Memory (LRM) structures specified (up # to 2000).#SINAP_TOTAL_LR_MEMS=<value>#export SINAP_TOTAL_LR_MEMS

#SINAP_TOTAL_LR_NUMS Allocates the total number (up to 5000) # of LRNs that can be assigned to LRM # structures.#SINAP_TOTAL_LR_NUMS=<value>#export SINAP_TOTAL_LR_NUMS

#SINAP_USER_LR_MEMS Defines the maximum number of connections# (up to 2000) each application can have# open at any given time.#SINAP_USER_LR_MEMS=<value>#export SINAP_USER_LR_MEMS

#ISUP Services Feature#======================

#ISUP_FEATURE Activates a standard-specific or # country-specific version of the ISUP# services feature on a SINAP node.## For the ANSI network variant, the only # valid ISUP version is: # ANSI## For the CCITT network variant, valid# ISUP versions are:# ACIF_G500# BELGIUM# CCITT# FRANCE1# GERMANY# ITALY# ITU97# MEXICO# NETHERLANDS# Q767



# SPAIN# SWEDEN# TAIWAN

## For the China network variant, the# valid ISUP version is:# CHINA

# For the NTT network variant, valid ISUP# versions are:# NTT# NTT_IC#ISUP_FEATURE=<VERSION>#export ISUP_FEATURE

#ISUP_DBL_SEIZE_BITS (ANSI only). Enables you to set a value # in the range 0-3 for the Double Seizing# Control Indicator field of the Circuit # Group Characteristics Indicator parameter# in the Circuit Validation Response (CVR)# message. The SINAP node uses this value# for all configured circuits on the node.# If you do not define this variable or you# specify a value outside the valid range,# the SINAP node uses the default value # (0x00) for the Double Seizing Control# Indicator.#ISUP_DBL_SEIZE_BITS=<value>#export ISUP_DBL_SEIZE_BITS

#ISUP_REL_NO_ADD_ACC (ANSI only). Disables the Automatic # Congestion Control (ACC) parameter in a# Release (REL) message.#ISUP_REL_NO_ADD_ACC=1#export ISUP_REL_NO_ADD_ACC

#ISUP_CQR_TRANS_FOR_UCIC (ANSI only). Causes the state for any # unequipped circuits reported in a Circuit# Query Response (CQR) message to be # transient. Also prevents the circuits from# going into the transient (maintenance)# state when certain outage conditions exist# (for example, when the ISUP application or # its process manager is not running). If # you do not define this variable, the SINAP # node reports the state "unequipped" in a # CQR message. This action applies to all # unequipped circuits, not just those # managed by the application.#ISUP_CQR_TRANS_FOR_UCIC=1#export ISUP_CQR_TRANS_FOR_UCIC

#ISUP_NO_UCIC_REPLIES (ANSI only). Prohibits the SINAP node from



# sending Unequipped Circuit Identification # Code (UCIC) messages to remote nodes in # response to messages destined for # unequipped or unconfigured circuits. This# affects all unequipped circuits, not just # those managed by the application. Normally,# the SINAP node sends UCIC messages to # remote nodes for unequipped circuits.#ISUP_NO_UCIC_REPLIES=1#export ISUP_NO_UCIC_REPLIES

#ISUP_GENERIC_NAME (ANSI only). Enables use of the Generic # Name Parameter in the Initial Address # Message (IAM).#ISUP_GENERIC_NAME=1#export ISUP_GENERIC_NAME

#ISUP_CGBA_PER_2CGB (ANSI only). Activates the feature (based # on ANSI 1992 standards) that returns a # Circuit Group Block Acknowledgement (CGBA) # message to the originator of the Circuit# Group Block (CGB) message whenever two # CGB messages are received within a 5 # second timer period. #ISUP_CGBA_PER_2CGB=YES#export ISUP_CGBA_PER_2CGB

#ISUP_RSC_BLO_PER_EXP (ANSI only).Enables the SINAP node to # return a Blocking (BLO) message immediately # after returning the Reset Circuit (RSC) # message and handle the sending of BLO # messages based on timer T12 and T13 # timeouts.#ISUP_RSC_BLO_PER_EXP=1#export ISUP_RSC_BLO_PER_EXP

#ALLOW_GR317_REV4_CAUSE_VALUES (ANSI only) Allows cause values 25 and 26, which # are supported in GR-317 Rev. 4, when a SINAP # node is configured for ANSI 92.##ALLOW_GR317_REV4_CAUSE_VALUES#export ALLOW_GR317_REV4_CAUSE_VALUES

#FIRMWARE_HEARTBEAT=1 Used to enable the U916 firmware heartbeat#export FIRMWARE_HEARTBEAT mechanism. To enable this, please uncomment# the following two lines.##FIRMWARE_HEARTBEAT=1#export FIRMWARE_HEARTBEAT

#DO_RPQDUMP=1 Used to enable the generation of an rpqdump file#export DO_RPQDUMP when the ss7dmn detects a board failure. To# enable, please uncomment the following two lines.##DO_RPQDUMP=1



#export DO_RPQDUMP=1

#CONG_EVENT_REPORT_OFF=1 This variable controls the congestion report for every #export CONG_EVENT_REPORT_OFF 1 out of 8 outbound messages per Q.704 section 11.2.3.1 # via IPC messages, M_message_for_congested_[link,route,# destination], from CASL to L3RC to notify MTP3 users# via I_MTP_STATUS primitives. Under heavy traffic with # congested link/linkset/routeset, these IPC messages# may prevent the other significant IPC messages from# processing. Setting this variable to 1 or a non-zero# value will disable this report.#CONG_EVENT_REPORT_OFF=1#export CONG_EVENT_REPORT_OFF#SGS_SRST_ROUTING (CCITT only). Enable the MTP L3 inbound # processing of SRST messages, i.e. RCT, RST# and RSR, at L3DT which forwards them to IP# gateway process, e.g. IPMT or IPSG which# acts like STP. Also, the other feature is# to turn off the DPC validation after# inbound GTT, if this env var and the other# one, DISABLE_MTP_DISCRIMINATION, are both# defined.#SGS_SRST_ROUTING=1#export SGS_SRST_ROUTING ##OSP_UPDATE_ENABLED (CCITT Only). Enable the ability to change # own point code, without SINAP stop/start# or activating/deactivating SINAP MMLs#OSP_UPDATE_ENABLED=1#export OSP_UPDATE_ENABLED##ISUP_UPU_FEATURE This enables UPU message to be sent to# each remote point code, for any incoming # ISUP message, when ISUP application is# down.#ISUP_UPU_FEATURE=1#export ISUP_UPU_FEATURE##SCCP_ITU96_IMPORTANCE_PARM (CCITT Only). Enable the ability to handle# the 1996 ITU-T Q.71x optional Importance# parameter included in SCCP XUDT/XUDTS MSUs.#SCCP_ITU96_IMPORTANCE_PARM=1#export SCCP_ITU96_IMPORTANCE_PARM

#CONG_STATUS_CHANGE_LOGGING=1 This variable is to enable or disable Sinap alarm # logging for link/linkset/routeset(DPC) congestion# status change. Setting this variable to 1 or a non-zero# value will enable the logging of the congestion status # change in Sinap alarm log file. Otherwise this# feature will not be enabled.#CONG_STATUS_CHANGE_LOGGING=1#export CONG_STATUS_CHANGE_LOGGING


Appendix CSINAP/SS7 MML Command

SummaryC-

The following chart lists and describes the SINAP/SS7 Man Machine Language (MML) commands and includes the alternate and UNIX online manual page (man page) command format for each command, if applicable. This chart is intended to serve as a quick reference guide to the MML commands. For detailed descriptions of how to execute commands using the Terminal Handler menus and/or the command line, and for descriptions of how to use the BITE subsystem, see the SINAP/SS7 User’s Guide (R8051).

The offline Built-In Test Environment (BITE) Log Analysis commands and sy utility commands are listed at the end of the chart. These commands can only be run from the command line, not from the Terminal Handler.

Table C-1. MML Command Summary (Page 1 of 28)

MML Command Description

Alternate/Man Page Command

#IPC,LPC When the DLPC feature is configured on the SINAP node, the command lists all the registered logical point codes (LPCs). If DLPC is not configured, the command produces the error message This node is not provisioned for DLPC capabilities.

Issue the command from a SINAP login window.

Format: #IPC,LPC

#IPC,LPC

#L3,RC Traces delivery of internal messages within the MTP layers. When the DLPC feature is configured on the SINAP node, the command traces communications between MTP Level 3 routing control (L3RC) and the ISUP manager.

#L3,RC

SINAP/SS7 MML Command Summary C-1

SINAP/SS7 MML Command Summary

BACKUP-APPL Backup the application (copy from the source to the destination storage device).

Terminal Handler menu: Application Commands

Format: BACKUP-APPL:SOURCE=source, DESTINATION=Destination;

BKUP-APPL

BACKUP-NODE Backup the node (backup the existing node static database to disk).

Terminal Handler menu: System Commands

Format: BACKUP-NODE;

BKUP-NODE

CHANGE-BKUPDAY Change the backup day (change the number of days for automatic node backup).


Format: CHANGE-BKUPDAY:DAYS=days;

CHG-BKDAY

CHANGE-CLSET Change the combined link set.

Terminal Handler menu: CHANGE command on Network Commands menu

Format:CHANGE-CLSET:LINKSET=linkset,EMERGENCY=yes;

CHG-CLSET

CHANGE-CPC Change the concerned point code (CPC) (add or delete an individual remote point code).


Format: CHANGE-CPC:LSSN=ssn,ADDRPC=pc[&pc]; CHANGE-CPC:LSSN=ssn,DELRPC=pc[&pc];

CHG-CPC




C-2 SINAP/SS7 User’s Guide R8051-17


CHANGE-DUCPC (Not supported in TTC network variant)

Change the duplicate concerned point code (DUCPC).


Format: CHANGE DUCPC:LSSN=ssn,NEWRPC=pc;

CHG-DUCPC

CHANGE-GTT Change the global title (replace an existing global title entry with a new one). The user must select at least one of the three fields. The number of fields in this command changes with the values entered. (The HADDR field is optional.) Refer to the section on global title format in Chapter 3 for more information on global title values.)


Format: CHANGE-GTT:OLD_GTI=gti,OLD_TT=tt,OLD_NP=np,OLD_NOAI=noai, OLD_LADDR=laddr,GTI=gti,TT=tt, NP= np,NOAI=noai,LADDR=laddr [,HADDR=haddr] {,DPC=dpc | ,SSN=ssn| ,NADDR=naddr}[SSN2=ssn2][DPC2=dpc2];

CHG-GTT

CHANGE-LINK Change a link.


Format:CHANGE-LINK:LINK=pc,PERIODIC_SLT= slt;

For the TTC network variant, use the command format: CHANGE-LINK:LINK=pc, PERIODIC_SLT= srt;

CHG-LINK

CHANGE-LSET Change the link set (emergency alignment flag).


Format: CHANGE-LSET:LINKSET=linkset, EMERGENCY=emergency;

CHG-LSET






CHANGE-PURGEDAY Change the purgeday (the number of days the log file remains on disk before it is deleted).


Format: CHANGE-PURGEDAY:LOG=logfile,DAYS=days;

CHG-PDAY

CHANGE-REMSSN Change the remote subsystem number (SSN) (add or delete remote SSNs for a specified point code).


Format: CHANGE-REMSSN:PC=pc,ADDSSN=ssn; CHANGE-REMSSN:PC=pc,DELSSN=ssn;

CHG-REMSSN

CHANGE-RSET Change the route set (add, delete, or exchange the priority of a route; enable or disable load sharing between two route sets).


Format: CHANGE-RSET:ROUTESET=routeset,ADDROUTE=route,PRIORITY=priority; CHANGE-RSET:ROUTESET=routeset,DELROUTE=route;CHANGE-RSET:ROUTESET=routeset,XROUTE1=route,XROUTE2=route; CHANGE-RSET:ROUTESET=routeset,LOADSHR=loadshr;

CHG-RST

CHANGE-SYSTAB Change the system table timers and thresholds.


Format: CHANGE-SYSTAB:TABID=tabid,TIMER=timer,NEWTIME=time; CHANGE-SYSTAB:TABID=tabid,THRESHOLD= threshold,NEWLEVEL=level;

CHG-SYSTAB






CONFIGURE-LINK Configure a link (activate or deactivate a link state).

Terminal Handler menu: CONFIGURE command on Network Commands menu

Format: CONFIGURE-LINK;LINK=link,STATE=state;

CFR-LINK

CONFIGURE-LSET Configure a link set (activate or deactivate a link set).


Format: CONFIGURE-LSET:LINKSET=linkset,STATE= state;

CFR-LSET

CONFIGURE-RSET Configure the route set (activate/deactivate a route set).


Format: CONFIGURE-RSET:ROUTESET=routeset, STATE=state;

CFR-RSET

CHANGE-SLSTYPE (ANSI network variant only)

Change the Signaling Link Selection (SLS) type (5-bit or 8-bit) used for all incoming and outgoing traffic.


Format:CHANGE-SLSTYPE:TYPE=numeric_slstype;

Where numeric_slstype is 8 or 5.

CHG-SLSTYPE

CREATE-CLSET (ANSI network variant only)

Create a combined link set (that is, two link sets that communicate with a mated pair of signaling transfer points [STPs]).

Terminal Handler menu: CREATE command on Network Commands menu

Format:CREATE-CLSET:CLSET=clset,LSET1= linkset1,LSET2=linkset2;

CRTE-CLSET






CREATE-CPC Create Concerned Point Code (associate a remote point code with a local subsystem).


Format: CREATE-CPC:LSSN=ssn,RPC=pc[&pc];

CRTE-CPC

CREATE-DUCPC (Not supported in TTC network variant)

Create a duplicate concerned point code (assign one of the concerned point codes as the replicate for a specified local subsystem).


Format: CREATE-DUCPC:LSSN=ssn, RPC=pc;

CRTE-DUCPC

CREATE-FOPC (ANSI network variant only)

Create a fictitious originating point code to be used in place of the calling party’s originating point code [OPC].


Format: CREATE-FOPC:FOPC=network- cluster-member;

CRTE-FOPC

CREATE-GTT Create a global title translation (define a duplicate point code [DPC], subsystem number [SSN], and/or address information that replaces the original global title entry.)


Format: CREATE-GTT:GTI=1,NOAI=noai,LADDR=laddr [,HADDR=haddr]{,DPC=dpc|,SSN=ssn|, NADDR=naddr}; CREATE-GTT:GTI=2,TT=tt, LADDR=laddr, [ , HADDR=haddr]{,DPC=dpc|,SSN=ssn|, NADDR=naddr};

CRTE-GTT






CREATE-GTT(cont.)

CREATE-GTT:GTI=3, TT=tt,NP=np, LADDR=laddr,[,HADDR=haddr] {,DPC=dpc|,SSN=ssn|,NADDR=naddr}; CREATE-GTT:GTI=4, TT=tt, NP=np,NOAI=noai,LADDR=laddr,[,HADDR=haddr]{,DPC=dpc|,SSN=ssn|, NADDR=naddr};

CREATE-LINK Create a link.


Format: CREATE-LINK:LINK=link,PORTNUM= portnum,LINKSET=linkset, SLC=slc,PRIORITY=priority,SPEED=speed;

CRTE-LINK

CREATE-LSET Create a link set.


Format for the CCITT network variant: CREATE-LSET:LINKSET=linkset,ADPC=adpc,LOADLINK=loadlink, ACTLINK=actlink;

Format for the ANSI network variant: CREATE-LSET:LINKSET=linkset,ADPC=adpc,TYPE=type,LOADLINK=loadlink,ACTLINK= actlink;

CRTE-LSET

CREATE-OSP Create the own signaling point code (for specified network).


Format: CREATE-OSP:NETWORK=network,SPC=spc;

CRTE-OSP






CREATE-REMSSN Create Remote Subsystem.


Format: CREATE-REMSSN:PC=pc,SSN=ssn[&ssn];

CRTE-REMSSN

CREATE-RSET Create a route set.


Format: CREATE-RSET:ROUTESET=routeset, DPC=dpc,ROUTES=routes[&routes],LOADSHR= loadshr;

CRTE-RSET

DELETE-CLSET (ANSI network variant only)

Delete the combined link set.

Terminal Handler menu: DELETE command on Network Commands menu

Format: DELETE-CLSET:CLSET=clset;

DLT-CLSET

DELETE-CPC Delete the concerned point code (CPC) (delete all remote point codes for specified local subsystem). Use CHANGE-CPC to delete an individual concerned point code (CPC).

Terminal Handler menu: DELETE command on Network Commands menu.

Format: DELETE-CPC:LSSN=ssn;

DLT-CPC

DELETE-DUCPC (Not supported in TTC network variant)

Delete the duplicate concerned point code (DUCPC).

Terminal Handler menu: DELETE command on Network Commands menu.

Format: DELETE-DUCPC:LSSN=ssn;

DLT-DUCPC

DELETE-FILE Delete a file from disk.

Terminal Handler menu: System Commands.

Format: DELETE-FILE:FILE=filename;

DLT-FILE






DELETE-FOPC (ANSI network variant only)

Delete a fictitious originating point code.


Format: DELETE-FOPC:FOPC=network- cluster-member;

DLT-FOPC

DELETE-GTT Delete a global title translation (GTT). See “Global Title Formats” in Chapter 3 for an explanation of the values for this command.


Format for the CCITT, China, and TTC variants:DELETE-GTT:GTI=1,NOAI=noai,LADDR=laddr; DELETE-GTT:GTI=2,TT=tt,LADDR=laddr; DELETE-GTT:GTI=3,TT=tt,NP=np,LADDR= laddr; DELETE-GTT:GTI=4,TT=tt,NP=np,NOAI= noai,LADDR=laddr;

Format for the ANSI variant:DELETE-GTT:GTI=1,TT=tt,NP=np,LADDR= laddr; DELETE-GTT:GTI=2,TT=tt,LADDR=laddr;

DLT-GTT

DELETE-LINK Delete a link.


Format: DELETE-LINK: LINK=link;

DLT-LINK

DELETE-LSET Delete a link set.


Format: DELETE-LINK: LINK=link;

DLT-LSET






DELETE-OSP Delete an own signaling point code (OSP) from the network (all other network elements must already be deleted).


Format: DELETE-OSP;

DLT-OSP

DELETE-REMSSN Delete a remote subsystem number (SSN) (stop monitoring for all subsystems at a specified remote node).


Format: DELETE-REMSSN:RPC=pc;

DLT-REMSSN

DELETE-RSET Delete a route set.


Format: DELETE-RSET:ROUTESET=routeset;

DLT-RSET

DISABLE-LOAD- CONTROL

Disable load control (deactivate load control processing).

Terminal Handler menu: DELETE command on Load Control menu

Format: DISABLE-LOAD-CONTROL:SSN=ssn [,INSTANCE=[&instance]];

DISABLE-LC

DISPLAY-BKUPDAY Display the backup day (number of days in node database backup cycle).

Terminal Handler menu: DISPLAY command on System Commands menu

Format: DISPLAY-BKUPDAY;

DISPL-BKDAY






DISPLAY-CLSET (ANSI network variant only)

Display the combined link set.


Format: DISPLAY-CLSET:CLSET=clset[,PRINT=print];

DISPL-CLSET

DISPLAY-CPC Display the concerned point code (CPC) for a local subsystem.


Format: DISPLAY-CPC:SSN=ssn[,PRINT=print];

DISPL-CPC

DISPLAY-FOPC (ANSI network variant only)

Display the fictitious originating point code.


Format: DISPLAY-FOPC:FOPC=network-cluster-member;

DISPL-FOPC

DISPLAY-GTT Display the global titles.


Format: DISPLAY-GTT;

DISPL-GTT

DISPLAY-LINK Display a link.


Format: DISPLAY-LINK:LINK=link[,PRINT=print];

DISPL-LINK

DISPLAY-LSET DIsplay a link set.


Format: DISPLAY-LSET:LINKSET=linkset [,PRINT=print];

DISPL-LSET






DISPLAY-LOAD- CONTROL

Display load control statistics for a specified application.

Terminal Handler menu: DISPLAY command on Load Control menu

Format: DISPLAY-LOAD-CONTROL:SSN=ssn [,PRINT=print];

DISPLAY-MON Display active BITE monitor IDs.

Terminal Handler menu: BITE Commands

Format: DISPLAY-MON;

DISPL-MON

DISPLAY-OSP Display the own signaling point code (OSP).


Format: DISPLAY-OSP:[PRINT=print];

DISPL-OSP

DISPLAY-PROCESS- VERSION

Display the version of a process.

This command is available only through the Terminal Handler BITE COMMANDS menu.

DISPL-PVERS

DISPLAY-PURGEDAY Display the purgeday (the number of days a log file remains on disk before it is deleted).


Format: DISPLAY-PURGEDAY:LOG=logfile;

DISPL-PDAY

DISPLAY-REMSSN Display the remote subsystem numbers (SSN) for a specified remote point code).


Format: DISPLAY-REMSSN:PC=pc[,PRINT=print];

DISPL-REMSSN






DISPLAY-RSET Display the route set.


Format: DISPLAY-RSET:DPC=dpc[,PRINT=print]; DISPLAY-RSET:ROUTESET=routeset[,PRINT= print];

DISPL-RSET

DISPLAY-SCEN Display the scenario (that is, the current active scenario with scenario ID BITE assigned to it).

Terminal Handler menu: SCENARIO command on the BITE Commands menu.

Format: DISPLAY-SCEN;

DISPL-SCEN

DISPLAY-SUBSYSTEM Display the current status of the subsystem.


Format: DISPLAY-SUBSYSTEM:SSN=ssn;

DISPL-SUBSYS

DISPLAY-SYSTAB Display the system table for Message Transfer Part [MTP] and Signaling Connection Control Point [SCCP] timer values and MTP threshold values.


Format:DISPLAY-SYSTAB;TABID=tabid, TIMER=timer[,PRINT=print]; DISPLAY-SYSTAB;TABID=tabid,THRESHOLD=threshold[,PRINT=print];

DISPL-SYSTAB

DUMP-TABLE Dump the contents of the MTP routing and management tables to the static table file in binary format.

Terminal Handler menu: Network Commands

Format: DUMP-TABLE;

DUMP-TABLE






ENABLE-LOAD- CONTROL

Enable load control (automatically activate load control processing for specified application when overload conditions occur).

Terminal Handler menu: DISPLAY command on Load Control menu

Format: ENABLE-LOAD-CONTROL:SSN=ssn[,INSTANCE=[&instance]];

EXIT-LOAD-CONTROL Exit load control (deactivate load control processing for specified application). This command can be used only if load control processing was initiated using INVOKE-LOAD-CONTROL.

Terminal Handler menu: EXIT option on the Load Control menu

Format:EXIT-LOAD-CONTROl:SSN=ssn [,INSTANCE=[&instance]];

INVOKE-LOAD- CONTROL

Invoke load control processing for a specified application even if no overload condition exists.

Terminal Handler menu: INVOKE command on the Load Control menu

Format: INVOKE-LOAD-CONTROL:SSN=ssn [,INSTANCE=[&instance]];

LPCR_cmd When the DLPC feature is configured on the SINAP node, this command manipulates a specified remote point code to change its status from active to standby (or from standby to active), reset its circuit status, or dump the circuit states into a file.

Issue the command from a SINAP login window.

Format: LPCR_cmd -r <pc> [-asRDV -i instance]

LPC_cmd






READ-TREAT Read the file containing the trouble Treatment Table.


Format: READ-TREAT;

READ-TREAT

REPORT-ALARM Report the contents of the Alarm History file.


Format: REPORT-ALARM:DATE=date[,PRINT=print];

RPT-ALARM

REPORT-MALL Report MTP, SCCP, and TCAP subsystem measurements for a specified time period.

Terminal Handler menu: 1. MEASUREMENTS command on Network Commands menu2. REPORT MEASUREMENTS command on Measurement Commands menu

Format: REPORT-MALL: DATE=CCYY-MM-DD,TIME=HH:MM, DATE=CCYY-MM-DD,TIME=HH:MM,FILE=file [,PRINT=print];

Note: For CCYY-MM-DD, CC=century (19 or 20), YY=year (38 through 99), MM=month (1 through 12), DD=day (1 through 31). For HH:MM, HH=hour (1 through 24), MM=minutes (00 through 59).

RPT-MALL






REPORT-MMTP Report MTP measurements for a specified time period.

Terminal Handler menu:1. MEASUREMENTS command on Network Commands menu2. REPORT MEASUREMENTS command on Measurement Commands menu

Format: REPORT-MMTP:DATE=CCYY-MM-DD,TIME=HH:MM, DATE=CCYY-MM-DD,TIME=HH:MM,FILE=file [,PRINT=print];


RPT-MMTP

REPORT-MSCCP Report SCCP subsystem measurements for a specified time period.

Terminal Handler menu: 1. MEASUREMENTS command on Network Commands menu2. REPORT MEASUREMENTS command on Measurement Commands menu

Format: REPORT-MSCCP:DATE=CCYY-MM-DD,TIME=HH:MM, DATE=CCYY-MM-DD,TIME=HH:MM,FILE=file [,PRINT=print];


RPT-MSCCP






REPORT-MTCAP Report TCAP subsystem measurements for a specified time period time.

Terminal Handler menu: 1. MEASUREMENTS command on Network Commands menu2. REPORT MEASUREMENTS command on Measurements Commands menu.

Format: REPORT-MTCAP:DATE=CCYY-MM-DD,TIME=HH:MM,DATE=CCYY-MM-DD,TIME=HH:MM,FILE=file [,PRINT=print];


RPT-MTCAP

REPORT-NBOOK Report the contents of the Software Notebook.


Format: REPORT-NBOOK:DATE=date,[,PRINT=print];

RPT-NBOOK

RESTORE-APPL Restore an application database from disk or tape.


Format: RESTORE-APPL:SOURCE=source, DESTINATION=destination;

RST-APPL

RESTORE-NODE Restore node static database (primary or secondary copy) from disk.


Format: RESTORE-NODE: FROM=source,RCLOG=rclog;

RST-NODE






RETRIEVE-NOM Retrieve and display the oldest 30-minute Node Network Management Measurement report.

Terminal Handler menu:1. MEASUREMENTS command on Network Commands menu2. RETRIEVE MEASUREMENTS command on Measurement Commands menu.

Format: RETRIEVE-NOM;

RTRV-NOM

RETRIEVE-SMR Retrieve and display the most recent 5-minute Node Network Management Measurement report.

Terminal Handler menu: 1. MEASUREMENTS command on Network Commands menu2. RETRIEVE MEASUREMENTS command on Measurement Commands menu

Format: RETRIEVE-SMR;

RTRV-SMR

SETUP-LOAD-CONTROL Set up load control (define an application’s load control threshold and operating characteristics).

Terminal Handler menu: SETUP command on Load Control menu

Format: SETUP-LOAD-CONTROL:SSN=ssn,TYPE=type,THRESHOLD=threshold,DELAY=delay,COUNT=count,ABATEDELAY= abatedelay;

SETUP-LC

send_cm Sends an MML command to the Command Management Process (nmcm) for execution. Allows you to execute MML commands from a SINAP login window (at the UNIX command level). Use this command to execute MML commands interactively, to execute a script file, or to issue single MML commands.

Format: send_cm (interactive mode; accepts commands via keyboard input) send_cm file_name send_cm -s “mml_command;”

send_cm






SET-PRINTER Prints all commands and responses to a terminal or specified printer.


Format: SET-PRINTER:PRINT=print;

SET-PRINTER

sinap_update Used to update link configuration information without rebooting the SINAP/SS7 system.

START-DBG Send a debug message to a specified process.


Format: START-DBG:ENT=(entity),MSG=message;

STA-DBG

START-MEASURE Start on-demand measurements for signaling information field (SIF) and service information octets (SIO) transmitted or received.

Terminal Handler menu: MEASUREMENTS command on the Network Commands menu

Format: START-MEASURE:MEASURE=measure;

STA-MEAS

START-MON Start the BITE monitor for specified entities from any SINAP process.

Terminal Handler menu: MONITOR command on the BITE Commands menu

Format: START-MON:ENT=(entity)[,DISP=Y/N] [,LOG=filename [(size)] [,CONT=Y/N]];

STA-MON

START-MWRITE Start writing measurements to the measurement logs in the logs/system directory.

Terminal Handler menu: MEASUREMENTS command on Network Commands menu

Format: START-MWRITE;

STA-MWRITE






START-SCEN Start a BITE scenario execution (network simulation).

Terminal Handler menu: SCENARIO command on BITE Commands menu

Format: START-SCEN:ENT=(entity),FILE=filename;

STA-SCEN

start_sinap Execute the start_sinap script file that starts the SINAP/SS7 system on each node to be activated.

Issue this command from a UNIX operating system prompt and specify one of three start up modes:

1) Verbose - Displays information on the terminal as commands execute 2) Test-Environment - Displays information on the terminal as processes execute

3) Test-Environment and Verbose - Combines test-environment and verbose modes to display (on the terminal) commands and processes as they execute

Format: start_sinap start_sinap -v start_sinap -t start_sinap -tv

start_sinap

static2mml Save and re-create an existing SINAP/SS7 configuration in a specified input file (typically STATIC_load) and write the command output to a specified output.

Issue this command at the UNIX operating system prompt.

Format: static2mml$SINAP_HOME/Bin/shm/pri/input_file [ > output_file]

static2mml






STOP-MEASURE Stop on-demand measurements (SIF and SIO octets transmitted or SIF and SIO octets received).


Format: STOP-MEASURE:Measure=measure;

STOP-MEAS

STOP-MON Stop the BITE monitor for specified entity.

Terminal Handler menu: MONITOR command on BITE Commands menu

Format: STOP-MON:ENT=monitor ID;

STOP-MON

STOP-MWRITE Stop writing measurements to the measurement logs in Logs/system.


Format: STOP-MWRITE;

STOP-MWRITE

STOP-SCEN Stop a specified BITE scenario execution.

Terminal Handler menu: SCENARIO command on BITE Commands menu

Format: STOP-SCEN:ENT=scenario_id;

STOP-SCEN

stop_sinap Run the stop_sinap script file that stops the SINAP/SS7 system on each node to be stopped.

Issue this command from a UNIX operating system prompt.

Format: stop_sinap

stop_sinap

TEST-LINK Send a signaling link test message (SLTM) to a specified link. (TTC and NTT send signaling route test (SRT) messages)


Format: TEST-LINK:LINK=link;

TEST-LINK






TEST-ROUTE Perform a signaling route test for a specified route. (NTT and TTC only.) For additional information see the man page for TEST-ROUTE.

Terminal Handler menu: BITE commands.

Format: TEST-ROUTE:DPC=dpc,AB=ab; Note that ab corresponds to the A/B indicator in Q.707.

BITE Log Analysis Commands These commands can only be run from the command line.

(Before using these commands, start the BITE Log Analysis (bila) program.)

bila Starts the offline BITE Log Analysis program.

Format: bila

bila

bidb Starts the Database Builder program which is a menu-driven interface used to build different types of MSU messages for different types of applications and scenarios. The bidb is used to construct a test MSU for the scenario-execution application to send to the test application. Use the message_file option to specify the path name of a file to which an existing MSU has already been saved.

Format: bidb[message-file]

bidb

DISPLAY:FILE Display records from a specified BITE log file.

Format: DISPLAY:FILE=logfile;

BDISPLAY

FIND:FILE Extracts records from a specified BITE log file that satisfies all criteria specified within the command arguments. You can specify multiple keys and key values.

Format: FIND:FILE=logfile, OFILE= file,key=key_value;

BFIND






SELECT:FILE Extracts records from a specified BITE log file that satisfies any criteria specified within the command arguments. You can specify multiple keys and key values.

Format: SELECT:FILE=logfile, OFILE= file,key=key_value;

BSELECT

SUMMARY:FILE Counts records in a specified BITE log file that satisfies the criteria specified within the command arguments. You can specify multiple keys and key values.

Format: SUMMARY:FILE=logfile, OFILE= file,key=key_value

BSUMMARY

QUIT Exits the BITE Log Analysis program.

Formats: QUIT or QUIT:; or QUIT:

BQUIT

Frequently-Used sy Utility Commands

? Displays all available commands for the sy utility.

#APPL Displays application tables.

#BI,MDx Displays the BITE monitor table entry. Options for x include:

• 0 - Display all.

• aname,pname,text - Send the text to the aname or pname process. text = “TRACE[,n]” for trace dump for last n (specify number of events) events.

#DIST,x Displays distribution information. Substitute optional appl_id for x to display distribution information for a specific application table.

#IPC,x Checks the status of an application. This command displays IPC process table entry x. Use x=0 to list all currently-running processes that are registered with the SINAP/SS7 system.

For x, indicate the table entry to list. For example, if you enter the command, #IPC,3, you will see a list of the third entry in the interprocess communications (IPC) table.

#IRT Displays the inbound routing table.






#KEY,aname[,pname [,inst]]

Displays an IPC key table.

#lc,x Displays load control information. Options for x include SSN_number to display the information for a specific subsystem, or 0 to display information for all SSNs.

#LCD,SSN_number Displays load control debug information for a specific SSN.

#L3,CLS Displays MTP shared data for all combined linksets.

#L3,CLS,x Displays MTP shared data for a specific combined linkset x.






#L3,x Displays MTP shared data. Options for x include:

• dt - Displays the discrimination table entries.

• lst[,optional linkset_#] - Displays timer values and includes information about the MTP restart timers: L3T19, L3T20, and L3T21. Displays values for the ANSI network variant timers: L3T22, L3T23, L3T24, L3T25, L3T26, L3T27, L3T28, L3T29, and L2T30.

In addition to displaying timer information, the command: #L3,lst displays a flag for each active link set. The flag indicates whether the node connected by the link set is executing MTP restart.

• port[,optional linkset_#]- Displays all ports or the port for a specified link set number.

• res - Displays MTP restart information, such as the own_sp_restarting flag (which indicates whether this SINAP/SS7 node is currently executing MTP restart), the number of active link sets, the number of TRA messages received, and the L3T20 timer ID.

• rst[,optional n-c-m DPC_#] - Displays Routeset information, such as the accessibility and availability of the DPC.

• spf - Displays signaling point routing failure reports.

• tim - Displays timer values and includes information about the MTP restart timers L3T19, L3T20, and L3T21. In addition, displays values for the ANSI network variant timers: L3T22, L3T23, L3T24, L3T25, L3T26, L3T27, L3T28, L3T29, and L2T30.

#ORT,CLS Displays the outbound routing combined link set table.

If you selected the 8-bit signaling link selection (SLS) processing scheme using the CHANGE-SLSTYPE command, then combined link set signaling link code (SLC) values are also displayed. If you did not select 8-bit SLS processing, the 5-bit SLS SLC values are displayed.






#ORT,LS Displays the outbound routing link set table.

For the ANSI network variant, if you select the 8-bit signaling link selection (SLS) processing scheme using the CHANGE-SLSTYPE command, the 8-bit combined link set signaling link code (SLC) values are also displayed. If you did not select 8-bit SLS processing, then 5-bit SLS SLC values are displayed for link sets.

#ORT,{RS or DPC#} Displays the outbound routing signaling route set test signal (RST) table for a specified route set or duplicate point code.

Q Close the sy utility and quit all operations.

#sc,x,n Displays SCCP shared memory information. Options for x include:

• appl[,optional local SSN_number] - Displays all application tables or the application table for a specified local SSN.

• cpc[,optional local SSN_number] - Displays all concerned point codes (CPCs) or the CPCs for a specified local SSN.

• dump - Dumps all SCCP shared memory information.

• lrm - Displays the local reference memory (LRM) and the command’s output.

• lrn[,optional LRN_number] - Displays information about all active LRNs or the information for a specific LRN (n).

• SSN[,optional DPC_number] - Determines whether all or a specified duplicate point code is accessible and, thereby, whether messages can be sent.






#SLD,x Displays information about an application’s load distribution (round-robin, least-utilized, or signaling link selection [SLS] distribution). Options for x include one of the following three #SLD command formats:

• APPL,appl_name - Displays the SLS assignments for an application that registered using its name instead of its SSN (where appl_name is the name of the application). Use this format for applications that implement enhanced message distribution (for example, if an application is one of several applications that use the same SSN). For example, the command, #SLD,APPL,DB12, specifies a load control application named DB12.

• SIO,sio_number - Displays the SLS assignments for an application that registered with a service information octet (SIO) (where sio_number is the SIO number). For example, the #SLD,SIO,5 command specifies an application that registered with an SIO of 5.

• SSN,subsystem_number - Displays the SLS assignments for an application that registered with a subsystem number (SSN) where ssn_number is the SSN of the application. For example, the #SLD,SSN,254 command specifies an application that registered with an SSN of 254.






#STA,x,n Displays the static tables. Options for x include:

• cls - Displays combined link set tables.

• cpc[,optional SSN_number] - Displays tables for all concerned point codes (CPCs) or for a specified SSN.

• cr,index - Displays the cluster address table.

• dt - Displays the discrimination table.

• gtt - Displays the Global Title Translation entries.

• lc[,optional SSN_number] - Displays all LC tables or those for a specified SSN.

• lst - Displays link set tables.

• mr,index - Displays the member address table.

• ncpc[,optional NETWORK_number] - Displays all network concerned point codes (CPC) or those for a specified network.

• nr - Displays the network address table.

• rssn - Displays the remote SSN table.

• st,x - Displays timer values. Options for x include: L2, L3, SCCP, Q707, MTP, PURGE, and ALL.

sy Invokes the sy utility.

#sys Displays the current settings of the shared memory system table.

#UCOMM,x Displays trace and status for UCOMM. Specify UCOMM number for x.

Z Displays structure sizes.





Appendix DCCITT Configuration

ParametersD-

This appendix describes the configuration limitations and configuration parameters for configuring the International Telecommunications Union Standards Division (ITU-T) network variant of the SINAP/SS7 system. The ITU-T was previously known as the Consultative Committee on International Telegraphy and Telephony (CCITT).

N O T EAlthough the CCITT name was changed to ITU and the standards are referred to as ITU-T standards, the SINAP/SS7 documentation continues to refer to the standards as the CCITT standards to avoid confusion in the various manuals.

This appendix includes the following sections that describe features and procedures unique to the CCITT network variant:

• ‘‘Configuration Limitations”

• ‘‘CCITT Point Code Formats”

• ‘‘MTP Timers and Thresholds”

• ‘‘SCCP Timers”

• ‘‘MTP Restart”

• ‘‘MTP Time-Controlled Changeover”

• ‘‘Time-Controlled Diversion (TCD)”

You activate or define many features through environment variables. The use of environment variables also defines whether you adhere to the 1988 or 1993 edition of the ITU-T recommendations for MTP. See Appendix B, ‘‘SINAP/SS7 Environment Variables,” for more information.

CCITT Configuration Parameters D-1

Configuration Limitations

Configuration LimitationsPlease reference Table 3-1 for configuration limitations specific to the CCITT network variant of SINAP/SS7 software.

CCITT Point Code FormatsThe CCITT signaling point codes are defined as 14-bit binary codes. All point codes must be within the number range 1-16383, for example, 10005.

MTP Timers and ThresholdsTable D-1 lists the MTP Level-2 timer settings, Table D-2 MTP Level-3 timer settings, and Table D-3 MTP threshold values.

Key: s = second, ms = millisecond, min = minute, Kbps = kilobits per second

Table D-1. MTP Level-2 Timers (Q.701 – Q.704 Bluebook)

Timer Description Range

L2T1 Alignment Ready 40-50 s at 64Kbps 500-600 s at 4.8 Kbps

L2T2 Not Aligned 5-105 s: Low = 5-50s High = 70-150 s

L2T3 Aligned 1-1.5 s

L2T4N Proving Period Timer 7.5-9.5 s at 64Kbps 100-200 s at 4.8Kbps (For nominal values, see Q.703, Section 12.3.)

L2TE 400-600 ms at 64Kbps 6-8 s at 4.8Kbps (For nominal values, see Q.703, Section 12.3.)

L2T5 Sending SI “B” Interval

L2T6 Remote Congestion 4.5 s

L2T7 Excessive Delay 1.3 s

D-2 SINAP/SS7 User’s Guide R8051-17

MTP Timers and Thresholds

In the table, an adjacent node is any node adjacent to the node performing MTP restart.

The MTP link congestion thresholds are shown in Table D-3. The threshold values are not link dependent—they apply to all links on the local system.

Table D-2. MTP Level-3 Timers (Q.701 – Q.704 Bluebook)


L3T1 Delay to avoid message missequencing on changeover 500-1200 ms

L3T2 Waiting for changeover acknowledgment 700-1200 ms

L3T3 Time-controlled diversion delay to avoid missequencing on changeback

500-1200 ms

L3T4 Waiting for changeback acknowledgment (1st attempt) 500-1200 ms

L3T5 Waiting for changeback acknowledgment (2nd attempt) 500-1200 ms


500-1200 ms

L3T10 Waiting to repeat signaling route set test message 30-60 s

L3T13 Waiting for force uninhibit 800-1500 ms

L3T19 Supervisory timer used to keep track of the TFP, TFR, and TRA messages passed between the MTP restart node and adjacent nodes. (This timer helps ensure these messages do not ping-pong between the nodes.)

67 to 69 seconds

L3T20 Set by the MTP restart node to define the amount of time within which all MTP restart activities should be completed.

59 to 61 seconds

L3T21 Set by an adjacent node to define the amount of time within which the MTP restart node is expected to finish MTP restart.

63 to 65 seconds

Table D-3. MTP Thresholds (Page 1 of 2)

Threshold Description

CONON0, CONON1, CONON2, and CONON3

Local Congestion Onset Levels 0-3. Defines the upper thresholds for link congestion (applies to all links on the local system). The value for each congestion onset level should be greater than its corresponding congestion abatement level. Default values are:Level Default*CONON0 0 CONON1 80 CONON2 110 CONON3 140


SCCP Timers

* Congestion-level-0 thresholds (CONAN0 and CONAB0) are preconfigured as zero (0) and cannot be changed.

N O T EIf multiple congestion levels are not configured, the SINAP/SS7 system implements the two-level international signaling network option for link congestion. In this case, only congestion onset level 1 (CONAN1) and congestion abatement level 1 (CONAB1) are used.

SCCP TimersSCCP timer settings are shown in Table D-4 and Table D-5.

CONAB0, CONAB1, CONAB2, and CONAB3

Local Congestion Abate. Defines the lower thresholds for link congestion (applies to all links on the local system). The value for each congestion abatement level should be less than its corresponding congestion onset level. Default values are:Level Default*CONAB0 0 CONAB1 50 CONAB2 90 CONAB3 120

Table D-4. SCCP Timers

Timer Description Default

SCT1 Status Information. Time to wait between subsystem status test and requests for remote prohibited subsystems.

5-60 s

SCT2 Coordinated State Change. Timer for subsystem-out-of-service-grant (SOG) after transmission of subsystem-go-out-of-service request to replicate subsystem.

5-60 s

SCT3 Ignore Subsystem Status Test. Time to wait after receiving a subsystem-out-of-service grant (SOG) and actually going out of service.

5-60 s

SCTX XUDT freeze timer that defines the time period during which an LRN assigned to multiple segments of the same message is frozen.

60 s

Table D-3. MTP Thresholds (Page 2 of 2)



SCCP Timers

SCCP Extended Unitdata (XUDT) Message TimersXUDT message timers define the time periods and reassembly periods for handling XUDT messages. XUDT messages are composed of MSU segments that are smaller than the default or maximum message size allowed for messages exchanged in the SINAP/SS7 network. See Chapter 3, ‘‘Software Configuration,” for how to define the segment sizes for XUDT messages.

The SCCP system tables in shared memory contain two XUDT timers:

• SCTX timer - This is the freeze timer that defines the time period during which an LRN assigned to multiple segments of the same message is frozen. The timer specifies the time period during which a released LRN cannot be reused on any node. The default value is 60 seconds.

N O T ECurrently, the SINAP/SS7 system uses the default value only. Subsequent releases will allow modification of the timer value.

• SCTY timer - This is the message reassembly timer that specifies the time period during which the message reassembly process receives and reassembles the XUDT message segments. There is one SCTY timer per node. The default value is 1 second.

SCCP Connection-Oriented TimersSCCP connection-oriented timers define the amount of time allowed to perform specific connection-oriented tasks (for example, the timer STCONEST defines the amount of time allowed to establish a connection). Table D-5 presents information about the SCCP connection-oriented timers. For detailed information about these timers, see ITU-T Recommendation Q.713.

N O T EIn the table, the column labeled “Q.713 Timer” presents the name of the timer as it is referred to in ITU-T Recommendation Q.713, and the column labeled “SCCP Timer Name” presents the name of the corresponding SINAP/SS7 timer.

SCTY XUDT reassembly timer that specifies the time period during which the message reassembly process receives and reassembles the XUDT message segments.

1 s

Table D-4. SCCP Timers



MTP Restart

6

The SINAP/SS7 system tables store the values of the SCCP connection-oriented timers. You access these system tables by means of the MML commands DISPLAY-SYSTAB and CHANGE-SYSTAB. For detailed information about these commands, see the discussions on ‘‘Displaying the MTP and SCCP System Tables” and ‘‘Changing Timers and Link Congestion Threshold Settings’’ in Chapter 4 in this guide.

MTP Restart You must determine whether you want to initiate a full or partial MTP restart on your system, then define the proper environment variable, as follows.

• To enable the SINAP/SS7 system to perform full MTP restart on a particular node, define the environment variable MTP_WHITE_BOOK_RESTART on that node before starting the SINAP/SS7 system. You need not assign a value to the variable. The SINAP/SS7 system simply verifies the variable exists.

If the variable is defined, the MTP restart process performs whenever you start the SINAP/SS7 system on the node. If the MTP_WHITE_BOOK_RESTART variable is not defined, MTP restart is not performed when the SINAP/SS7 system is started on the node.

Table D-5. SCCP Connection-Oriented Timers

Q.713 Timer

SCCP Timer Name


Description

T(conn est) STCONEST 1 - 2 minutes Connection establishment timer

T(iar) STIAR 3 - 6 minutes Inactivity timer for inbound messages

T(ias) STIAS†

† The value of the STIAS timer must be greater than the value of the STIAR timer.

1 - 2 minutes Inactivity timer for outbound messages (Timer value must be less than the value of the STIAR timer.)

T(reset) STRESET 10 - 20 seconds Amount of time to wait for a reset confirm message

T(rel) STREL 10 - 20 seconds Amount of time to wait for a release complete message after a disconnect

T(interval) STRELINT 0 - 60 seconds Total amount of time to repeat the release message

T(repeat rel) STRELREP 0 - 20 seconds Amount of time between each repeated release message

T(guard) STGUARD 8 - 16 minutes Amount of time to hold an LRN before assigning it to another connection


MTP Restart

If the variable is defined, MTP restart is performed whenever the SINAP/SS7 system is started.

• If a full restart is not required, you can perform a partial restart on a node. To enable partial restart, define the environment variable, MTP_PARTIAL_RESTART, before starting the SINAP/SS7 system. For instructions on defining variables, see Appendix B, ‘‘SINAP/SS7 Environment Variables.“

At the beginning of the MTP restart process, the SINAP/SS7 system activates the L3T20 timer and marks all concerned routes ALLOWED. The L3T20 timer defines the maximum amount of time allowed to complete all MTP restart activities. The L3T21 timer defines the amount of time to stop sending traffic to another node because that node is performing MTP restart. (See “‘‘Changing Timers and Link Congestion Threshold Settings’’ in Chapter 4 for information about these timers.)




• The SINAP/SS7 system only processes signaling network management (SNM) message types: TRA, TFP, TFR, and TFA. The SINAP/SS7 system discards all other SNM messages types, such as:

• Changeover and changeback message (CHM)

• Signaling-data-link-connection-order message (DLM)

• Emergency-changeover message (ECM)

• Signaling-traffic-flow-control message (FCM)

• Management inhibit message (MIM)

• Signaling-route-set-test message (RSM)

• User part flow control (UFC) message groups

SNM messages have a service instance (SI) of 0000.




• The SINAP/SS7 system discards all incoming and outgoing messages (user traffic) for all types of applications: TCAP, SCCP, and ISDN User Part (ISUP).

MTP Time-Controlled ChangeoverThe CCITT network variant supports time-controlled changeover (TCCO) procedures for the SINAP/SS7 system. TCCO supports handling of long-term or short-term processor outages or changeover orders received from the remote end during the MTP Level 3 T1 timer period.

You must define the appropriate environment variable to enable TCCO functionality.

For the CCITT, TTC, or China network variants, define the environment variable:

MTP_WHITE_BOOK_TCCO

You need not assign a value to the variable. The SINAP/SS7 system simply verifies that the variable exists. You must define this environment variable before you start or restart the SINAP node to implement TCCO functionality based on the 1993 ITU-T recommendations for MTP. If you do not define it, the system defaults to TCCO procedures based on the 1988 recommendations. To implement TCCO automatically each time you start or restart a CCITT-configured SINAP node, add the variable to the $SINAP_Home/Bin/sinap_env[csh or sh] file.

Time-Controlled Diversion (TCD)In the CCITT network variant, the time-controlled diversion (TCD) functionality is implemented automatically and is transparent to the user. That is, there are no environment variables to be set.

See ‘‘MTP Time-Controlled Diversion’’ in Chapter 3 for a complete description of TCD.


Appendix EANSI Configuration

ParametersE-

This appendix describes the configuration limitations and the configuration parameters required to configure the ANSI network variant of the SINAP/SS7 system. This appendix includes the following sections that describe features and procedures unique to the ANSI network variant::


• ‘‘ANSI Point Code Formats”



• ‘‘Combined Link Sets”

• ‘‘Fictitious Originating Point Codes (FOPCs)”



• ‘‘MTP Time-Controlled Diversion (TCD)”

• ‘‘MTP Eight-bit SLS Processing”

• ‘‘ISUP Services Feature”

You activate or define many features through environment variables. See Appendix B, ‘‘SINAP/SS7 Environment Variables,” for more information on the variables and how to set them.

Configuration LimitationsPlease reference Table 3-1 for configuration limitations specific to the ANSI network variant of SINAP/SS7 software.

ANSI Configuration Parameters E-1

ANSI Point Code Formats

ANSI Point Code FormatsThe ANSI signaling point codes are defined as 24-bit binary codes that contain three fields separated by dashes: network-cluster-member where:

• network

• cluster

• member

The following sections describe the network, cluster, member routing method and how to use it when specifying remote SSNs and route sets.

Network, Cluster, and Member RoutingEach node in an SS7 network has a unique point code by which the node is identified. The format of this point code is network-cluster-member, where network is the ID of the network to which the node belongs, cluster is the ID of the network cluster to which the node belongs, and member is the node’s unique point code within the network cluster.

Certain SS7 resources that you configure through the SINAP/SS7 system are associated with a specific node in the network [for example, route sets and remote subsystem numbers (SSNs)]. To configure these resources, you must specify the node’s point code. When you specify the node’s point code, you typically use the complete point code, such as 254-56-2. However, to communicate with a group of nodes within the same network ID or cluster ID, without provisioning route sets for every member node within that network or cluster ID, you can specify the network ID only or both the network ID and the cluster ID. Substitute an X for the other ID(s) to indicate that the ID can have any acceptable values. This procedure gives you the flexibility to perform routing based on the network, cluster, and the member.

N O T EConfiguring member routing for individual nodes does not automatically provision network or cluster routing. If you require a SINAP node to accept and process MTP Level 3 transfer cluster messages such a transfer cluster allowed (TCA, transfer cluster prohibited (TCP), or transfer cluster restricted (TCR) from an STP, you must provision network or cluster routing for the cluster ID using the MML commands CREATE-RSET and CONFIGURE-RSET.

The following list describes how the SINAP/SS7 system passes traffic using each of these point-code formats.

• If you specify a point code that contains the network ID only and substitute an X for the cluster and member values (for example, 254-X-X), the SINAP/SS7 system passes traffic to the specified network; the destination can be any node in any cluster in this network (for

E-2 SINAP/SS7 User’s Guide R8051-17


example, 254-056-002, 254-090-006, 254-080-006, and so on). When the SINAP node receives queries from any node in this network, it uses network routing to pass traffic to that node.

• If you specify a point code that contains both the network ID and the cluster ID (for example, 254-056-X), the SINAP/SS7 system passes traffic to the specified network cluster; the destination can be any node in this network cluster (for example, 254-56-2, 254-56-8, 254-56-16, and so on). When the SINAP node receives queries from any node in this network cluster, it uses cluster routing to pass traffic to that node.

• If you specify a complete point code (for example, 254-56-2), the SINAP node passes traffic directly to the specified node using member routing. For example, specifying the point code, 254-56-2, causes the SINAP node to route traffic directly to that node.

The following subsections describe how you can use these point code formats when specifying remote SSNs and route sets. It also presents information about dynamic route provisioning, which enables the SINAP/SS7 system to automatically provision route sets in order to update its routing tables.

Remote SSNsWhen you configure the SINAP/SS7 system, you must specify a remote SSN for each application with which the SINAP/SS7 system will communicate. The remote SSN indicates the application’s SSN and the point code of the node on which the application is running. If you are unsure of the node’s complete point code, you can specify a partial point code, as described previously. For more information about specifying a remote SSN, see the descriptions in an earlier chapter for creating and configuring a remote SSN.

If you specify a point code that contains the network ID only, the SINAP/SS7 system can communicate with any application that has the specified SSN, as long as the application is running on a node in the specified network. If you specify a point code that contains both the network ID and the cluster ID, the SINAP/SS7 system can communicate with any application that has the specified SSN, as long as the application is running on a node in the specified network cluster. If you specify a complete point code, the application must be running on the specified node.

The following command examples illustrate how to specify a remote SSN using the various point-code formats.

• Entering the following command enables the SINAP/SS7 system to communicate with applications that have an SSN of 234 and are running on any node in network 254 (such as 254-56-2, 254-90-6, 254-80-6, and so on).

CREATE-REMSSN:PC=254-X-X,SSN=234;



• Entering the following command enables the SINAP/SS7 system to communicate with applications that have an SSN of 234 and are running on any node in the specified cluster (56) in network 254 (for example, 254-56-2, 254-56-8, 254-56-16, and so on).

CREATE-REMSSN:PC=254-56-X,SSN=234;

• Entering the following command enables the SINAP/SS7 system to communicate with a specific application (234) running on a specific member node (2) in a specific cluster (56) in network 254.

CREATE-REMSSN:PC=254-56-2,SSN=234;

Route SetsA route set consists of up to eight routes, each defining a path over which the SINAP/SS7 system can pass traffic to a particular node. You use the MML command, CREATE-RSET, to create a route set. The value you specify for this command’s DPC parameter indicates the point code of the destination node (called the destination point code (DPC)). The point-code format that you use for the DPC value indicates the type of routing (network, cluster, or member) that the SINAP node is to use to pass traffic. (Creating a route set is described in chapter 3 of this manual.)

By defining a route set that uses network or cluster routing, you enable the SINAP/SS7 system to pass traffic to nodes without knowing their specific point codes. You also enable the SINAP/SS7 system to use the same route set to pass traffic to multiple nodes. For example, if you define a route set that uses network routing (for example, DPC=254-X-X), the SINAP node can use that route set to pass traffic to any of the nodes in that network. For example, DPC=254-56-2, DPC=254-30-6, and so on. Similarly, the SINAP node can use a route set that uses cluster routing (for example, DPC=254-56-X) to pass traffic to any of the nodes in that cluster. For example, DPC=254-56-2, DPC=254-56-10, and so on.

The SINAP/SS7 system uses a route set that uses member routing (for example, DPC=254-56-4) to pass traffic only to the specified node.

Dynamic Route ProvisioningDynamic route provisioning enables the SINAP/SS7 system to create a new route set for the express purpose of marking it unavailable. This is necessary because the SINAP/SS7 system designates a node as UNAVAILABLE by making the route set to the node unavailable. However, in cases where the only access to a particular node is through a route set that uses network or cluster routing, the SINAP/SS7 system cannot mark that node UNAVAILABLE without also marking other nodes in the network or network cluster UNAVAILABLE. To avoid this problem, the SINAP/SS7 system’s dynamic route provisioning creates for the node a route set that uses member routing. The SINAP/SS7 system then marks this route set UNAVAILABLE to indicate that the node cannot accept traffic. When the SINAP/SS7 system receives a transfer allowed (TFA) message from the node, the SINAP/SS7 system marks the dynamically provisioned route set ALLOWED to indicate that the node is available.



For example, suppose the only access to the node whose point code is 254-56-2 is through a route set that uses network routing (that is, DPC=254-X-X). If the node cannot accept traffic, the SINAP/SS7 system must dynamically provision a route set that uses member routing (that is, DPC=254-56-2) and mark that route set UNAVAILABLE; otherwise, the SINAP/SS7 system would have to mark the original route set UNAVAILABLE, which would prohibit traffic to all nodes in network 254.

The SINAP/SS7 system performs dynamic route provisioning only when MTP Level 3 receives one of the following management messages. The SINAP/SS7 system does not perform dynamic route provisioning when passing traffic over a route set that uses network or cluster routing.

• For a route set that uses network or cluster routing, the SINAP/SS7 system dynamically provisions a member-routing route set whenever MTP Level 3 receives a transfer allowed (TFA), transfer prohibited (TFP), or transfer restricted (TFR) message.

• For a route set that uses network routing, the SINAP/SS7 system dynamically provisions a cluster-routing route set whenever MTP Level 3 receives a transfer cluster allowed (TCA), transfer cluster prohibited (TCP), or transfer cluster restricted message TCR).

N O T EThe MML command DISPL_RSET only displays only route sets in the static configuration. It does not display route sets that have been dynamically provisioned.

MTP Timers and ThresholdsTable E-2 lists the MTP Level-2 timer settings and Table E-3 lists the MTP Level-3 timer settings. Table E-4 lists the MTP threshold values.

Table E-1. MTP Level-2 Timers (ANSI Recommendation T1.111.3) (Page 1 of 2)

Timer Description Value/Range

L2T1 Aligned/Ready 13 s

L2T2 Not Aligned 11.8 s

L2T3 Aligned Range 11.8 s

L2T4N Proving Period (Normal) 2.3 s

L2T4E Proving Period (Emergency) 0.6 s

L2T5 Sending SIB Interval 80 ms

L2T6 Remote Congestion Range 5 s (64 Kbps) 8-12 s (4.8 Kbps)



Key: s = second, ms = millisecond, Kbps = kilobits per second

L2T7 Excessive Delay of Acknowledgment 2 s (64 Kbps) or 4-6 s (4.8 Kbps)



L3T1 Delay to avoid message missequencing on changeover 500 ms

L3T2 Waiting for changeover acknowledgment 2000 ms

L3T3 Time-controlled diversion delay to avoid missequencing 500 ms

L3T4 Waiting for changeback acknowledgment (1st attempt) 500 ms

L3T5 Waiting for changeback acknowledgment (2nd attempt) 500 ms


500 ms

L3T10 Waiting to repeat signaling route set test message 30,000 ms

L3T12 Waiting for uninhibit acknowledgment 1500 ms

L3T13 Waiting for force uninhibit 1500 ms

L3T14 Waiting for inhibit acknowledgment 3000 ms

L3T15 Waiting to repeat signaling route set test message 2000 ms

L3T16 Waiting for route set congestion status update 2000 ms

L3T17 Delay to avoid oscillation of initial alignment failure and link restart

800 ms

L3T20 Waiting to repeat local inhibit test 90,000 ms

L3T21 Waiting to repeat remote inhibit test 90,000 ms

L3T22 Defining the period (at the restarting signaling point) to wait for signaling links to become available

60,000 ms

L3T23 Defining the period (at the restarting signaling point) to wait to receive all traffic restart allowed (TRA) messages after timer T22 starts

60,000 ms





Key:s = second Kbps = kilobits per second ms = millisecond min = minute

The MTP link congestion thresholds are shown in the following table. The threshold values are not link dependent—they apply to all links on the local system.

L3T25 Defining the period (at the signaling point adjacent to the restarting signaling point) to wait for a TRW message

30,000 ms

L3t26 Defining the period (at the restarting signaling point) to wait before repeating the TRW message

12,000 ms

L3T27 Defining the minimum duration of unavailability for a full restart. The value in parenthesis is the lower bound to use for long propagation delay signaling routes (such as routes using satellite sections).

2000 ms

L3T28 At the signaling point adjacent to the restarting signaling point, defining the period to wait for the TRW message

35,000 ms

L3T29 Starting when a TRA is sent in response to an unexpected TRA or transfer restart waiting (TRW) message

60,000 ms

Table E-3. MTP Thresholds (ANSI Recommendation T1.111.4)


CONON1 Congestion Onset, level 1



CONAB1 Congestion Abate, level 1



CONDIS1 Congestion Discard, level 1






SCCP Timers

N O T E S1. Congestion threshold-level-0 values (CONON0, CONAB0,

and CONDIS0) are preconfigured as zero (0) and cannot be changed.

2. Use caution when adjusting timers. See the appropriate ANSI T1.111 Recommendation for information about setting congestion thresholds and adjusting timers.

SCCP TimersSCCP timer settings are shown in Table E-5.

Combined Link SetsThe ANSI network variant of the SINAP/SS7 system supports combined link sets (CLS) (two link sets that access a mated pair of signaling transfer points (STPs)). Because there is only one home-mated pair of STPs for each signaling point, there can only be one combined link set defined with type A links. A maximum of four combined link sets can be defined. Each combined link set must contain member link sets with the same type links defined.

You cannot change combined link sets. Instead, you must delete (DELETE-CLSET) the combined link set you are changing and create a new one (CREATE-CLSET) with the new values you want to implement.

N O T EIn a CLS, changeover messages (COO) and changeback acknowledgment (CBA) messages should use the direct link set, if available, and not just any choice of links in the CLS.

Table E-4. SCCP Timers (ANSI Recommendation T1.112.4)



30 s

SCT2 Coordinated State Change. Timer for subsystem-out-of-service-grant (SOG) after transmission of subsystem-out-of-service request.

30 s

SCT3 Ignore Subsystem Status Test. Delay between receiving a subsystem-out-of-service grant (SOG) and actually going out of service.

30 s


Fictitious Originating Point Codes (FOPCs)

For more information on combined link sets and link types, see those sections in Chapters 3 and 4 of this manual.

Fictitious Originating Point Codes (FOPCs)Configuring a fictitious originating point code (FOPC) enables the SINAP/SS7 system to set the MTP routing label’s originating point code (OPC) field to an OPC that is different from the calling-party’s OPC. The FOPC defines the OPC that the SINAP/SS7 system is to use in place of the calling-party’s OPC. This functionality is typically used in handover processing. Using the FOPC, the SINAP/SS7 system can set the MTP routing label’s OPC field to any OPC, including the local SINAP/SS7 node’s Own Signaling Point (OSP).

N O T EOnly one FOPC can exist on a node.

You must set the ANSI_SINAP_FOPC environment variable to YES to activate the FOPC feature. Refer to Appendix B, “SINAP/SS7 Environment Variables,” for more information on how to set the variable.

You cannot change FOPCs. Instead, you must delete (DELETE-FOPC) the combined link set you are changing and create a new one (CREATE-FOPC) with the new values you want to implement.

Table E-6 lists the MML commands to create, display, or delete an FOPC.

To create the FOPC you want the SINAP/SS7 system to use in place of the calling party’s OPC (where network-cluster-member defines the OPC), enter the following MML command:

CREATE-FOPC:FOPC=network-cluster-member

Table E-5. MML Commands for FOPC

Command Description

CREATE-FOPC Defines the FOPC you want the SINAP/SS7 system to use. Select this option through the CREATE command on the Network Commands menu.

DISPLAY-FOPC Displays an existing FOPC. Select this option through the DISPLAY command on the Network Commands menu.

DELETE-FOPC Deletes an existing FOPC. Select this option through the DELETE command on the Network Commands menu.


MTP Restart

For example: CREATE-FOPC:FOPC=254-053-001;

MTP RestartTo enable the SINAP/SS7 system to perform MTP restart (based on the 1992 edition of ANSI standards) on a particular node, define the following environment variable before starting the SINAP/SS7 system:

MTP_ANSI92_RESTART=

You need not assign a value to the variable, as the Node Management Parent (nmnp) process only validates the existence of the environment variable. To enable MPT restart automatically each time the node is started, define the variable in the SINAP environment file $SINAP_HOME/Bin/sinap_env.[chs or sh].

MTP restart can be applied in two different ways: using a SINAP node as the restarting signaling point, or using a node adjacent to the SINAP node as the restarting signaling point. Both options are described in the following sections. Only a full restart can be performed; the ANSI network variant does not support a partial restart.

ANSI MTP Level 3 timers define the maximum amount of time the restart signaling point or its adjacent signaling points can take to perform specific MTP restart tasks. You can access these timers by executing the MML command, CHANGE-SYSTAB. (See “Changing the System Table Timer and Link Congestion Threshold Settings” for more information.)

If a link becomes available during the period a SINAP node is unavailable, the management function initiates a full restart if the environment variable MTP_ANSI92_RESTART is defined.

See the description of MTP restart in Chapter 3 for more information.

MTP Time-Controlled ChangeoverThe ANSI network variant supports time-controlled changeover (TCCO) procedures for the SINAP/SS7 system. TCCO supports handling of long-term or short-term processor outages or changeover orders received from the remote end during the MTP Level 3 T1 timer period.

You must define the appropriate environment variable to enable TCCO functionality for your ANSI network variant. For the ANSI network variant, define the environment variable:

MTP_ANSI92_TCCO

You must define this environment variable to implement TCCO functionality based on the 1992 ANSI standards for MTP. If you do not define it, the system defaults to TCCO procedures based on the 1990 standards.


MTP Time-Controlled Diversion (TCD)

See the description of MTP time-controlled changeover in Chapter 3 for more information.

MTP Time-Controlled Diversion (TCD)The ANSI network variant implements an MTP time-controlled diversion (TCD) process when the signaling point at the far end of the link made available is currently inaccessible from the signaling point initiating the changeback order. The SINAP/SS7 system also performs TCD when the concerned signaling point is accessible, but there is no signaling route to it using the same outgoing signaling link(s) or one of the same signaling links from which traffic is diverted.

The ANSI network variant enables TCCO automatically if MTP restart is enabled.

However, if MTP restart is not enabled, you can still implement TCD by defining the following environment variable before starting the SINAP/SS7 system:

MTP_ANSI92_TCD

If you do not define this variable, the system defaults to TCD functionality based on the 1990 ANSI standards. To have the TCD feature defined each time you start the SINAP/SS7 system, add the variable to the $SINAP_HOME/Bin/sinap_env.[csh or sh] file.

C A U T I O NIf the MTP_ANSI92_RESTART environment variable is set, do not enable the TCD functionality. The ANSI 1992 restart process, when enabled, automatically invokes the TCD process. Enabling the ANSI 1992 TCD process via the environment variable MTP_ANSI92_TCD causes TCD to occur unconditionally for every link coming into service. This delays the changeback completion 500 ms per link. (500 ms is the default value for the T3 timer.)

This feature is fully described in the section ‘‘MTP Time-Controlled Diversion’’ in Chapter 3.

MTP Eight-bit SLS ProcessingIn the ANSI network variant, you can select either an 8-bit or 5-bit signaling link selection (SLS) scheme for all incoming and outgoing traffic. See “MTP Eight-bit Processing” in Chapter 3 of this manual for detailed information on this feature.


ISUP Services Feature

ISUP Services FeatureIf the ISUP services feature environment variable ISUP_FEATURE=ANSI is defined, you can use the following ISUP services features:

• The ISUP Services Support Library (ISSL) is the API that provides the functions and data structures for developing ISUP applications. An application can use either the archive or shared object library version of the standard library.

• The archive library, libissl.a, is located in $SINAP_MASTER/Library and $SINAP_HOME/Library/libissl.a, where $SINAP_Home is the root directory for your installation.

• The shared object library is also called the SINAP Dynamic Linked Library (DLL). The SINAP DLL that contains the ISUP services functions is libissl.sl (HP-UX operating systems) or libissl.so (Solaris operating system), stored in $SINAP_MASTER/Library and $SINAP_HOME/Library.

See “SINAP/SS7 Libraries” in the SINAP/SS7 Programmer’s Guide (R8052) and the SINAP/SS7 ISDN User Part (ISUP) Guide (R8053) for more information.

• An environment variable, ISUP_CGBA_PER_2CGB=YES, which activates the feature that returns a circuit group block acknowledgment (CGBA) message to the originator of the CGB message whenever two CGB messages are received within a 5-second timer period.

• An environment variable, ISUP_REL_NO_ADD_ACC, which disables the addition of the automatic congestion control (ACC) parameter to a release (REL) message when the level of available buffer resources falls below an internal threshold at the time an REL message is sent.

• The $SINAP_HOME/Include directory that contains additional ISUP services files, including issl.h and issl_sit.h.

• Sample programs showing how to use the ISUP services functions in applications to enable them to send and receive ISUP messages.

• ISUP services timers that define time-out values for performing various tasks.

• The BITE subsystem and sy utility that log and display ISUP messages.

Activating the ISUP Services Feature By default, the ISUP services feature is turned off. To activate the ISUP services feature, you must define the following environment variable.

ISUP_FEATURE=ANSI

Additionally, when the ISUP services feature is selected, set the ISUP_CGBA_PER_2CGB=YES environment variable to activate the feature (based on ANSI 1992 standards) that returns a circuit group block acknowledgment (CGBA) message to the originator of the circuit group block (CGB) message whenever two CGB messages are received within a 5-second timer period. If the SINAP/SS7 system receives the second CGB message



after the timer expires, it discards the first CGB message received and waits to receive the second CGB message within the 5-second timer interval, then sends the CGBA message.

When this environment variable is not set, the SINAP/SS7 system uses ANSI 1988 processing. In this case, the SINAP/SS7 system waits to receive the second CGB message before the timer expires and then sends the CGBA message. If the SINAP/SS7 system receives the second CGB message after the timer expires, the node discards the first CGB message. The node starts the timer and waits to receive the second CGB message before sending the CGBA message to the originator of the CGB message.


Appendix FTTC Configuration ParametersF-

This appendix describes the configuration limitations for the Telecommunications Technology Committee of Japan (TTC) network variant of the SINAP/SS7 system. The TTC network variant is similar to the CCITT variant with some exceptions, which are listed at the end of this appendix. The TTC stack adheres to the standards documented in the 1994 JT-Q.700 recommendations.

This appendix includes the following sections that describe features and procedures unique to the TTC network variant:


• ‘‘Point Code Formats”

• ‘‘Timers and Thresholds”

• ‘‘Time-Controlled Changeover (TCCO)”

• ‘‘MTP Time-Controlled Diversion”

• ‘‘Activating and Deactivating TTC Applications”

• ‘‘Differences in TTC and CCITT Network Variants”

• ‘‘Unsupported SINAP/SS7 Administrative Features”

You activate or define many features through environment variables. Refer to Appendix B, ‘‘SINAP/SS7 Environment Variables,” for more information on the variables and how to set them.

Configuration LimitationsPlease reference Table 3-1 for configuration limitations specific to the TTC network variant of SINAP/SS7 software.

Point Code FormatsThe TTC signaling point codes are defined as 16-bit binary codes. All point codes must be within the number range 1-65535, for example, 10005.

TTC Configuration Parameters F-1


Timers and ThresholdsAlthough most Message Transfer Part (MTP) and Signaling Connection Control Point (SCCP) timers and thresholds used in TTC are the same as those used in CCITT, some differences exist.

Some CCITT timers are not supported by TTC because of differences in the way link testing is performed. Table F-1 lists the CCITT timers not supported by TTC.

If you specify one of these unsupported timers in the DISPLAY-SYSTAB or CHANGE-SYSTAB command, an error results.

N O T EFor information on using the DISPLAY-SYSTAB or CHANGE-SYSTAB commands, refer to the sections on displaying the MTP and SCCP system tables in Chapter 4 of this manual.

TTC does not use all the CCITT timers provided, but does assign some timers default values. They include the MTP-L2, MTP-L3, and SCCP Management (SCMG) timers listed in Table F-2.

Table F-1. CCITT Timers Not Supported by TTC

SS7 Layer Timers Not Supported by TTC

MTP-L2 L2T4 (normal proving)

MTP-L3 L3T5, L3T7, L3T11 through L3T14, L3T17 through L3T24 (Since TTC does not implement signaling point restart control (TPRC), it does not support TPRC timers: L3T18, L3T19, L3T20, and L3T21.)

SCMG SCT1 (status information), SCT2 (coordinated state change), and SCT3 (ignore SST)

Table F-2. CCITT Timers Assigned Default Values in TTC (Page 1 of 2)

SCMG, MTP-L2, MTP-L3 Timers

Default Value (Milliseconds)

Congestion-Onset, Abatement, and Discard Thresholds

Default Value (Number of Messages)

SCT1 30000 CONON1 80

L2T1 15000 CONON2 110

L2T2 5000 CONON3 140

L2T3 3000 CONAB1 50

L2T4N 3000 CONAB2 90

F-2 SINAP/SS7 User’s Guide R8051-17


Link TestingTTC uses signaling route test (SRT) timers for link testing, which correspond to the signaling link timers (SLT) used by CCITT. TTC uses the following SRT timers. Table F-3 lists each SRT timer’s default setting, range of valid values, and the related timer used by other stacks.

* TTC provides access to the periodic SRT timer, SRTT20, even though the TTC JT-Q.707 recommendation does not define periodic SRT or using the SRTT20 timer.

TTC does not exchange SRT messages during link initialization, unlike other stacks which exchange SLT messages.

Route TestingThe TTC and NTT network variants offers the ability to also test indirect routes (those destinations that are not directly adjacent to the SINAP node) as well as direct routes. To do this use the TEST-ROUTE option on the Sysopr BITE commands menu. When prompted for the DPC enter the point code of the destination to be tested. When prompted for the A/B (plane) value, enter either 0 (which nominally corresponds to the part of the route between the SINAP node and the "uppermost" STP1) or 1 (which nominally corresponds to the part of the route between the SINAP node and the "lower" STP2). STP1 and STP2 are arbitrary symbols, for

L2T4E 3000 CONAB3 120

L2T5 200 CONDIS1 130

L2T6 3000 CONDIS2 170

L2T7 2000 CONDIS3 210

L3T15 2000

L3T16 2000

Table F-3. TTC Timer Default Settings

TTC Timer Name

Default Setting


Description Related Timer

SRTT10 10 seconds Awaiting SRTA SLTT1

SRTT20* 60 seconds 30 - 90 seconds Periodic SRT SLTT2

Table F-2. CCITT Timers Assigned Default Values in TTC (Page 2 of 2)






Time-Controlled Changeover (TCCO)

example only. The SRT message is transmitted to the selected STP. An SRA may be received from the remote destination over either linkset connected to the STPs. For additional information see the TEST-ROUTE man page.

Time-Controlled Changeover (TCCO)For the TTC network variant, the SINAP/SS7 system automatically implements TCCO functionality based on 1988 ITU-T recommendations for MTP. There are no environment variables to set

MTP Time-Controlled Diversion In the TTC network variant, the time-controlled diversion (TCD) functionality is implemented automatically and is transparent to the user. That is, there are no environment variables to be set.

Activating and Deactivating TTC ApplicationsSCMG manages the SCCP and TCAP applications registered with the SINAP/SS7 system. After registering, an application must send a user-in-service (UIS) message to SCCP management (SCMG) to indicate it is ready to begin processing. In addition, before withdrawing from the SS7 network and terminating completely, an application must send a user-out-of-service (UOS) message to SCMG to indicate it wants to stop processing.

For TCAP and SCCP applications, you can use the environment variable TTC_WITH_NSTATE to specify who (the application or CASL) is responsible for sending the UIS and UOS messages (N_STATE_REQ SCMG_UIS and N_STATE_REQ SCMG_UOS, respectively) to SCMG.

• If you do not define the TTC_WITH_NSTATE environment variable, the CASL automatically sends UIS and UOS messages on behalf of the application.

N O T EAccording to the TTC JT-Q recommendations, not defining the variable is the preferred method of handling UIS/UOS messages.

• A UIS message is sent to SCMG when the application calls the ca_register() function to register; a UOS message is sent to SCMG when the application calls the ca_withdraw() function to withdraw from the SS7 network. If TTC_WITH_NSTATE is not defined, SCMG ignores UIS and UOS messages sent by the application.

• If you define the TTC_WITH_NSTATE environment variable, the application is responsible for sending UIS and UOS messages to SCMG. For an example of how to code your application to send these messages, see the functions send_nstate_uis_to_sccp() and send_nstate_uos_to_sccp() in the


Differences in TTC and CCITT Network Variants

TCAP sample program tcsend.c or in the SCCP sample program scsend.c. (Both sample programs are located in the $SINAP_HOME/Samples/ttc directory.)

N O T EYou must define the TTC_WITH_NSTATE environment variable at UNIX command level before you start the SINAP/SS7 system. You need not assign a value to the variable; the SINAP/SS7 system simply verifies that the variable exists. For instructions on how to define environment variables, see Appendix B, ‘‘SINAP/SS7 Environment Variables,” in this guide.

• Concerned point code (CPC) functionality, defined with the CREATE-CPC MML command, will not be allowed unless the TTC_WITH_NSTATE environment variable is defined.

Differences in TTC and CCITT Network VariantsThe TTC network variant is very similar to the CCITT variant. This section lists the major differences, including features TTC does not support.

• To test the availability of links and routes, the TTC stack performs signaling route testing (SRT); the other stacks perform signaling link testing (SLT).

• Unlike CCITT, which supports three separate options for link-congestion handling, TTC supports a single option: the national signaling network option using multiple link-congestion levels with message priority. Note that the TTC stack implements this link-congestion-handling option by default; you need not perform any action to implement it.

• TTC’s implementation of message handling discrimination differs from that of CCITT due to differences in point-code formats.

• TTC’s implementation of the initial alignment control (IAC) procedures differs from CCITT. TTC does not distinguish between normal and emergency link-alignment procedures. Link alignment and proving is always considered an emergency, and the SINAP/SS7 system discards any messages for starting or stopping emergency link-activation procedures. During link alignment and proving, TTC transmits link status signaling units (LSSUs) periodically (every 24 milliseconds) instead of continuously. In addition, TTC uses only SIO (out of alignment) and SIE (emergency alignment) LSSUs; it does not use SIN (normal alignment) LSSUs.

• TTC’s handling of link activity control (LSAC) differs from that of CCITT because TTC does not distinguish between normal and emergency link-activation procedures. When TTC receives a message containing notification of an emergency or emergency cease, it discards the message rather than sending it to the LSAC.


Unsupported SINAP/SS7 Administrative Features

• TTC does not implement transfer restricted control (RTRC) functionality, nor does it support the use of transfer restricted (TFR) signals. In addition, TTC does not implement signaling-point-restart control (TPRC) functionality.

• The MTP level-2 (MTP-L2) transmission control (TC) and reception control (RC) components for TTC and CCITT differ slightly. For example, when there are no MSUs to transmit, TTC transmits fill-in signaling units (FISUs) periodically (every 24 milliseconds); CCITT transmits FISUs continuously. In addition, there are minor differences in how TTC and CCITT handle sequence numbers for retransmission after an error occurs.

• The TTC stack does not currently support the following SCCP functionality:

• Intermediate (transfer) node functions

• TTC does not support duplicate concerned point codes (DUCPCs). This includes the following commands:

• CREATE-DUCPC

• CHANGE-DUCPC

• DELETE-DUCPC

• TTC does not support user flow control (UFC) or user part unavailable (UPU) messages, which are part of the MTP user flow-control functionality.

• TTC does not support MTP restart.

• TTC does not support the ISUP services feature.

• TTC does not support the loopback detection feature.

Unsupported SINAP/SS7 Administrative FeaturesThe SINAP/SS7 system provides to the network variants some administrative features the JT-Q recommendations do not describe. However, the TTC network variant does not support the following additional features:

• Processor outage control (POC)

• Several SCCP management (SCMG) messages, including:

• Subsystem out-of-service request (SOR)

• Subsystem out-of-service grant (SOG)

• Subsystem allowed (SSA)

• Subsystem prohibited (SSP)

• Subsystem status test (SST)

In the TTC network variant, if the SINAP/SS7 system receives one of the above messages, it generates an alarm.



• The following alarm for SST messages (since TTC does not use SST messages):

“SCMG: Error sending SST to PC: %d errno: %d/n”


Appendix GNTT Configuration ParametersG-

This appendix describes the configuration limitations and parameters for the Japanese Nippon Telephone and Telegraph (NTT) network variant of the SINAP/SS7 system. The NTT network variant is similar to the TTC network variant with some exceptions which are listed at the end of this appendix. The NTT stack adheres to the standards documented in the NTT-Q700 Specifications NTT-Q701-b, NTT-Q702-a, NTT-Q703-a NTT-Q704-b, and NTT-Q707-b.

This appendix includes the following sections that describe features and procedures unique to the NTT network variant:


• ‘‘NTT Point Code Format”

• ‘‘Creation of Own Point Code”

• ‘‘Timers and Thresholds”

• ‘‘Link Congestion Thresholds”

• ‘‘Setting SLS Bits in the MSU Routing Label”

• ‘‘Link Set and Route Statuses”

• ‘‘Time-Controlled Changeover (TCCO)”


• ‘‘Activating and Deactivating NTT Applications”

• ‘‘Activating the NTT Version of ISUP Services”

• ‘‘Differences in NTT, TTC, and CCITT Network Variants”

You activate or define many features through environment variables. See Appendix B, ‘‘SINAP/SS7 Environment Variables,” for more information on the variables and how to set them.

NTT Configuration Parameters G-1


Configuration LimitationsPlease reference Table 3-1 for configuration limitations specific to the NTT network variant of SINAP/SS7 software.

NTT Point Code FormatSignaling point codes in the NTT network variant, like TTC point codes, are defined as 16-bit binary codes. All point codes must be within the number range 1-65535 (for example, 1005).

In the SINAP/SS7 system, you enter and display point codes in binary format. However, for incoming transfer-prohibited (TFP), transfer-restricted (TFR), and transfer-allowed (TFA) messages, the SINAP node internally treats destination point codes (DPCs) and origination point codes (OPCs) specified in these messages as having three fields separated by hyphens and arranged in the format M-S-U, which is similar to the ANSI point code format (network-cluster-member):

• M = Main number area - A 5-bit code (a decimal value in the range 0-31 that identifies the main number area to which the node belongs.

• S = Subnumber area - A 4-bit code (a decimal value in the range 0-15) that identifies the subnumber area to which the node belongs

• U = Unit number - A 7-bit code (a decimal value in the range 0-127) that defines the node ID.

Incoming TFP, TFR, and TFA messages can specify the following three types of destinations:

• M-x-x

• M-S-x

• M-S-U

The x character represents a wildcard that is used to specify wide-ranging destinations such as subnumber area. These destinations points can be wide-ranging and can specify multiple destination points (up to 13) as affected destinations if the value specified in the message’s Coding field is 0000 or 0001. When the Coding field value is 0010 - 1111, the node receiving the TFP, TFR or TFA message processes the unique point code that matches the M-S-U code specified in the message.

The following chart describes the actions the receiving node takes based on the value contained in the TFP, TFR or TFA message.

Coding Field Value Action Taken by the Receiving Node

0000 Processes all point codes that have the same M code as the receiving node

G-2 SINAP/SS7 User’s Guide R8051-17

Creation of Own Point Code

If the receiving node finds no matching M-x-x, M-S-x, or M-S-U codes, the node issues an error message.

Note that you must configure all destinations (route sets) contained within an M-x-x and M-S-x region using the CREATE-RSET MML command.

For outbound route set test (RST) messages sent in response to TFP, TFR, or TFA messages, the message’s Coding field contains the value 0010 which defines a specific point code.

Note that NTT differs from the TTC variant in that the TTC procedures for handling TFP and TFA messages do not consider the M-S-U codes and the processing of individual point codes based on the Coding field in the messages.

Creation of Own Point CodeIn the NTT network variant, when you create the SINAP node’s own point code using the CREATE-OSP MML command, you must specify TTCNAT for the network indicator. This entry sets the four-bit Subservice field (SSF) to 0000. The TTC variant also uses this network indicator.

0001 Processes all point codes that have the same M and S codes as the receiving node

0010-1111 Processes a unique point code that matches the M-S-U code specified in the TFP, TFR or TFA message

Coding Field Value Action Taken by the Receiving Node



Timers and ThresholdsAlthough most Message Transfer Part (MTP) and Signaling Connection Control Point (SCCP) timers and thresholds used in the NTT network variant are the same as those used in the TTC network variant, some differences exist.

The NTT network variant (like the TTC variant) does not support the CCITT timers listed in Table G-1 because of differences in the way link testing is performed.

If you specify one of these unsupported timers in the DISPLAY-SYSTAB or CHANGE-SYSTAB command, an error results.

N O T EFor information on using the DISPLAY-SYSTAB or CHANGE-SYSTAB commands, see the sections on displaying the MTP and SCCP system tables in Chapter 4 of this manual.

NTT does not use all the CCITT timers provided, but does assign some timers default values. They include the MTP-L2, MTP-L3, and SCCP Management (SCMG) timers listed in Table G-2.

Table G-1. CCITT Timers Not Supported by NTT

SS7 Layer Timers Not Supported by NTT

MTP-L2 L2T4 (normal proving)

MTP-L3 L3T5, L3T7, L3T11 through L3T14, L3T17 through L3T24 (Since NTT does not implement signaling point restart control (TPRC), it does not support TPRC timers: L3T18, L3T19, L3T20, and L3T21.)

SCMG SCT1 (status information), SCT2 (coordinated state change), and SCT3 (ignore SST)

L3-T16 Signaling route congestion (signaling route congestion tests not supported)

Table G-2. CCITT Timers Assigned Default Values in NTT (Page 1 of 2)





SCT1 30000 CONON1 80

L2T1 15000 CONON2 110

L2T2 5000 CONON3 140


Link Congestion Thresholds

Link Congestion ThresholdsThe NTT network variant supports the National Signaling Network link congestion option (multiple congestion-handling levels 0-3 with congestion priority). The SINAP/SS7 system automatically implements this option. The initial value for the congestion-onset threshold is set to 2. However, you can change the initial congestion-onset threshold, by defining the following environment variable:

CONGESTION_INITIAL_VALUE=<n>

The valid value for <n> is a number in the range1 through 3. You can also change the congestion threshold values (that is, the number of MSUs NEWLEVEL=nnnn in the buffer for each congestion threshold level) using the CHANGE-SYSTAB MML command:

L2T3 3000 CONAB1 50

L2T4N 3000 CONAB2 90

L2T4E 3000 CONAB3 120

L2T5 200 CONDIS1 130

L2T6 3000 CONDIS2 170

L2T7 2000 CONDIS3 210

L3TC 20000

Table G-2. CCITT Timers Assigned Default Values in NTT (Page 2 of 2)






Setting SLS Bits in the MSU Routing Label

Link TestingLike the TTC network variant, NTT uses signaling route test (SRT) timers for link testing, which correspond to the signaling link timers (SLT) used by CCITT. The NTT network variant uses the SRT timers listed in the following chart. The chart shows each SRT timer’s default setting, range of valid values, and the related timer used by other network variants.

* NTT, like the TCC network variant, does not exchange SRT messages during link initialization, unlike other stacks which exchange SLT messages.

Setting SLS Bits in the MSU Routing LabelIn the TTC and NTT network variants, you can set the SLS bits into the routing label of the MSU, using the macro NTT_CA_SET_LABEL.

N O T EThe NTT and TTC network variants both use the macros TTC_CA_GET_DPC, TTC_CA_GET_OPC, TTC_CA_GET_SLS, TTC_CA_GET_SLC and TTC_CA_GET_PRIO (including TTC_PRIO_MASK). The sample programs in $SINAP_HOME/samples/ttc use the macro CA_SET_LABEL, which is set to TTC_CA_SET_LABEL (by default). For the NTT variant, the sample programs must use NTT_CA_SET_LABEL. For the TTC variant, the sample programs can use CA_SET_LABEL or TTC_CA_SET_LABEL.

NTT Timer Name Default Setting


Description Related Timer

SRTT10 10 seconds Awaiting SRTA

SLTT1

SRTT20* 60 seconds 30 - 90 seconds Periodic SRT

SLTT2


Link Set and Route Statuses

Link Set and Route StatusesThe SINAP/SS7 system maintains the signaling route statuses based on the direct signaling link statuses and transfer statuses the node receives from the adjacent signal relay station on the status of intermediate signaling links and signal (relay) stations beyond the direct signaling link set.

The NTT network variant implements the following four signaling link set statuses:

• Completely Normal• Normal• Subnormal• Abnormal

On the Display Linkset (DISPLAY-LSET) screen, the link set statuses appear as described in the following chart.:

The NTT variant uses the following signaling route statuses.

• Available • Unavailable• Restricted• Prohibited

On the Display Routeset (DISPLAY-RSET) screen, these statuses appear in the Route Set Status field and the Route Status field as described in Table G-3.

Link Set Status Description

a - available Displayed when the link status is Completely Normal, Normal, or Subnormal

A - not available Displayed when the link status is Abnormal

Table G-3. Display Routeset Screen Status Descriptions (Page 1 of 2)

Route Set Status Route & Transfer Statuses Description

a - DPC accessible a - link set availablex - transfer allowed

Displayed when all links in the link set are available (linkset state is completely normal)—SINAP node received a transfer-allowed (TFA) message from the adjacent node


Time-Controlled Changeover (TCCO)

Time-Controlled Changeover (TCCO)The SINAP/SS7 system automatically implements time-controlled changeover (TCCO) functionality. You do not need to set any environment variables.

MTP Time-Controlled Diversion In the NTT network variant, the time-controlled diversion (TCD) functionality is implemented automatically and is transparent to users. That is, there are no environment variables to be set.

Activating and Deactivating NTT ApplicationsSCCP management (SCMG) manages the SCCP and TCAP applications registered with the SINAP/SS7 system. After registering, an application must send a user-in-service (UIS) message to SCCP management (SCMG) to indicate it is ready to begin processing. In addition, before withdrawing from the SS7 network and terminating completely, an application must send a user-out-of-service (UOS) message to SCMG to indicate it wants to stop processing.

a - DPC accessible n - link set normalx - transfer allowed

Displayed when all but one of the links in the link set (for example, 2 out of 3 links) are available)—linkset is in normal state and SINAP node received a TFA message from the adjacent node

R - DPC restricted s - link set subnormalR - transfer restricted

Displayed when only one of the links in the link set (for example 1 out of 3 links) is available—SINAP node received a transfer-restricted (TFR) message from the adjacent node

A - DPC prohibited A - link set abnormalP - transfer prohibited

Displayed when one of the links in the link set is in service—SINAP node received a transfer-prohibit (TFP) message from the adjacent node

Table G-3. Display Routeset Screen Status Descriptions (Page 2 of 2)

Route Set Status Route & Transfer Statuses Description


Activating the NTT Version of ISUP Services

For TCAP and SCCP applications, you can use the environment variable TTC_WITH_NSTATE to specify who (the application or CASL) is responsible for sending the UIS and UOS messages (N_STATE_REQ SCMG_UIS and N_STATE_REQ SCMG_UOS, respectively) to SCMG.

• If you do not define the TTC_WITH_NSTATE environment variable, the CASL automatically sends UIS and UOS messages on behalf of the application. This is the preferred method.

• A UIS message is sent to SCMG when the application calls the ca_register() function to register; a UOS message is sent to SCMG when the application calls the ca_withdraw() function to withdraw from the SS7 network. If TTC_WITH_NSTATE is not defined, SCMG ignores UIS and UOS messages sent by the application.

• If you define the TTC_WITH_NSTATE environment variable, the application is responsible for sending UIS and UOS messages to SCMG. For an example of how to code your application to send these messages, see the functions send_nstate_uis_to_sccp() and send_nstate_uos_to_sccp() in the TCAP sample program tcsend.c or in the SCCP sample program scsend.c. (Both sample programs are located in the $SINAP_HOME/Samples/ttc directory.)

N O T EYou must define the TTC_WITH_NSTATE environment variable at UNIX command level before you start the SINAP/SS7 software. You need not assign a value to the variable; the SINAP/SS7 system simply verifies that the variable exists. For instructions on how to define environment variables, see Appendix B, ‘‘SINAP/SS7 Environment Variables,” in this guide.

• Concerned point code (CPC) functionality, defined with the CREATE-CPC MML command, is not enabled unless you define the TTC_WITH_NSTATE environment variable.

Activating the NTT Version of ISUP Services To activate the NTT version of ISUP services you must define the following environment variable before you start the SINAP/SS7 software:

ISUP_FEATURE=NTT

To have the SINAP/SS7 system automatically activate the NTT version of ISUP services each time you start or restart the SINAP node, define the environment variable in the SINAP environment file $SINAP_HOME/Bin/sinap_env[.csh or .sh]

Note that the version of ISUP services defined must agree with the network variant defined for the node. Therefore, if the NTT network variant is configured on the SINAP node, you can only


Differences in NTT, TTC, and CCITT Network Variants

specify the ISUP services version NTT in the ISUP_FEATURE environment variable. For more information on ISUP, see the SINAP/SS7 ISDN User Part (ISUP) Guide (R8053).

Differences in NTT, TTC, and CCITT Network VariantsThe NTT network variant is very similar to the TTC network variant (which is similar to the CCITT variant). This section lists the major differences, including features NTT does not support.

• To test the availability of links and routes, the NTT, like the TTC network variant performs signaling route tests (SRTs); the other variants perform signaling link tests (SLTs).

• Note that the NTT network differs from the TTC network variant in that the maximum number of destination point codes that you can specify in the TTC variant is 1-16 whereas in the NTT variant you can specify 1-13 DPCs. Also, the TTC variant does not implement transfer-restricted (TFR) messages.

• Unlike CCITT, which supports three separate options for link-congestion handling, NTT (like TTC) supports a single option: the national signaling network option that implements multiple link-congestion levels with message priority. The SINAP/SS7 system implements this option automatically. You do not need to set any environment variables to activate it.

• The NTT implementation of message handling discrimination differs from that of CCITT due to differences in point-code formats.

• The NTT implementation of the initial alignment control (IAC) procedures differs from CCITT. The NTT variant, like the TTC variant, does not distinguish between normal and emergency link-alignment procedures. Link alignment and proving is always considered an emergency, and the SINAP node discards any messages for starting or stopping emergency link-activation procedures. During link alignment and proving, the node transmits link-status signaling units (LSSUs) periodically (every 24 milliseconds) instead of continuously. Also, the NTT variant uses only out-of-alignment (SIO) and emergency-alignment (SIE) LSSUs; it does not use normal alignment (SIN) LSSUs.

• In the NTT variant, handling of link activity control (LSAC) differs from that of CCITT in that NTT (like TTC) does not distinguish between normal and emergency link-activation procedures. When NTT receives a message containing notification of an emergency or emergency cease, it discards the message rather than sending it to the LSAC.

• The NTT network variant does not implement transfer restricted control (RTRC) functionality or signaling-point-restart control (TPRC) functionality.

• The MTP level-2 (MTP-L2) transmission control (TC) and reception control (RC) components for NTT and CCITT differ slightly. For example, when there are no MSUs to transmit, NTT transmits fill-in signaling units (FISUs) periodically (every 24 milliseconds); CCITT transmits FISUs continuously. In addition, there are minor differences in how NTT and CCITT handle sequence numbers for retransmission after an error occurs.



• The NTT network variant, like the TTC variant, does not currently support the following features:

— SCCP intermediate (transfer) node functions

— User flow control (UFC) or user part unavailable (UPU) messages, which are part of the MTP user flow-control functionality

— MTP restart

— Loopback detection

— Duplicate concerned point codes (DUCPCs) and the following commands associated with DUCPCs:

• CREATE-DUCPC• CHANGE-DUCPC• DELETE-DUCPC)

— Processor outage control (POC); the SINAP node generates an alarm if it receives a POC message

— Several SCCP management (SCMG) messages, which includes the following messages:

• Subsystem out-of-service request (SOR)• Subsystem out-of-service grant (SOG)• Subsystem allowed (SSA)• Subsystem prohibited (SSP)• Subsystem status test (SST)

The SINAP node generates an alarm if it receives any SCMG messages

— The following alarm for SST messages: SCMG: Error sending SST to PC: %d errno: %d/n


Appendix HChina Configuration

ParametersH-

This appendix describes the limitations and parameters required to configure the China network variant of the SINAP/SS7 system. It also describes administrative considerations for this variant.

The China network variant is the version of the SS7 protocol defined by the People’s Republic of China (P.R.C.) in the following specifications and standards:

• Technical Specifications of Signaling System No. 7 for the National Telephone Network of China (Temporate Provisions) GF001-9001, Ministry of Posts and Telecommunications, P.R.C., August 1990.

• Supplemental stipulation about implementing the Technical Specifications of Signaling System No. 7 for the National Telephone Network of China. P.R.C. 1991.10

• Technical Specification of SCCP. Directorate General of Telecommunication of Ministry of Posts and Telecommunication, P.R.C., October 1994.

• Technical Specification of TCAP. Directorate General of Telecommunication of Ministry of Posts and Telecommunication, P.R.C., October 1994.

The China variant adheres to standards in the 1988 edition of CCITT recommendations (sometimes called blue book standards) and contains MTP enhancements that comply with standards defined in the 1993 edition of the ITU-T specifications of Signaling System 7 (SS7), which are sometimes called white book standards.

Operationally, the China SS7 network variant is very similar to the CCITT network variant except that it uses the ANSI-style point code format and the ANSI-style message signaling unit (MSU) data structure.

This appendix includes the following sections that describe features and procedures unique to the China network variant:


• ‘‘China Point Code Formats”



China Configuration Parameters H-1


• ‘‘SCCP Extended Unitdata (XUDT) Message Timers”

• ‘‘Required Environment Variables”




• ‘‘Activation of China ISUP Services”

• ‘‘Unsupported SINAP/SS7 Features”

You activate or define many features through environment variables. The use of environment variables also defines whether you adhere to the 1988 or 1933 edition of the ITU-T recommendations for MTP. See Appendix B, “SINAP/SS7 Environment Variables,” for more information.

Configuration LimitationsPlease reference Table 3-1 for configuration limitations specific to the China network variant of SINAP/SS7 software.

China Point Code FormatsThe China originating point codes (OPC) and destination point codes (DPC) are defined in almost the same manner as ANSI point codes.

ANSI point codes are 24-bit binary codes divided into three fields of 8-bit components, separated by hyphens (xxx-yyy-zzz). In ANSI, the three fields represent:

network-cluster-member

The China equivalent of the ANSI point-code components is shown in the following chart:

This document refers to the China point-code components in terms of the ANSI equivalents, namely, network-cluster-member.

Figure H-1 illustrates the relationship of China point codes to ANSI point codes.

ANSI Point Code Component

China Equivalent

network main signaling area

cluster sub-signaling area

member signaling point code

H-2 SINAP/SS7 User’s Guide R8051-17


Figure H-1. China Point Codes in Relationship to ANSI Point Codes

The valid values for China are slightly different from those in ANSI. Valid values for the China variant are:

• Network is a network ID number between 0 and 255.

• Cluster is a network cluster ID number between 0 and 255 or an X if network routing is already defined.

• Member is a cluster member ID number between 0 and 255 or X if network routing or cluster routing is defined.

For example, 255-X-X specifies main signaling area (network) routing and 255-13-X specifies signaling area (cluster) routing. When all three fields are filled in, for example, 255-13-134, signaling point routing (member) is specified.

N O T EAlthough 0 is a valid value for network, cluster, or member routing, the SINAP/SS7 system reserves the point code 0-0-0 for internal use. All other point code combinations within the range of 0 - 255 are valid. For example, the point codes, 0-0-1, 0-1-0, and 255-255-255 are all valid.

MTP Timers and ThresholdsThe China variant uses the timers and thresholds that follow the CCITT standards. Table H-1 lists the MTP Level-2 timer settings, MTP Level-3 timer settings, and MTP threshold values.

DPC

SignalingPoint Code

Sub-signalingArea

Main SignalingArea

(Member)8 bits

(Cluster)8 bits

(Network)8 bits

China:

ANSI:

SignalingPoint Code

Sub-signalingArea

Main SignalingArea

(Member)8 bits

(Cluster)8 bits

(Network)8 bits

China:

ANSI:

OPC

SLS

4 bits

4 bits

24 bits

24 bits



Key: s = secondms = millisecond min = minute Kbps = kilobits per second

Table H-1. MTP Level-2 Timers (Q.701 – Q.704 Bluebook)


L2T1 Alignment Ready 40-50 s at 64Kbps 500-600 s at 4.8 Kbps

L2T2 Not Aligned 5-105 s: Low = 5-50s High = 70-150 s

L2T3 Aligned 1-1.5 s

L2T4N Proving Period Timer 7.5-9.5 s at 64Kbps 100-200 s at 4.8Kbps (For nominal values, see Q.703, Section 12.3.)

L2TE 400-600 ms at 64Kbps 6-8 s at 4.8Kbps (For nominal values, see Q.703, Section 12.3.)

L2T5 Sending SI “B” Interval 80 - 120 ms

L2T6 Remote Congestion 4.5 s

L2T7 Excessive Delay 1.3 s

Table H-2. MTP Level-3 Timers (Q.701 – Q.704 Bluebook) (Page 1 of 2)


L3T1 Delay to avoid message missequencing on changeover 500-1200 ms

L3T2 Waiting for changeover acknowledgment 700-1200 ms


500-1200 ms

L3T4 Waiting for changeback acknowledgment (1st attempt) 500-1200 ms

L3T5 Waiting for changeback acknowledgment (2nd attempt) 500-1200 ms


500-1200 ms

L3T10 Waiting to repeat signaling route set test message 30-60 s



The MTP link congestion thresholds are shown in Table H-3. The threshold values are not link dependent—they apply to all links on the local system.

* Congestion-level-0 thresholds (CONAN0 and CONAB0) are preconfigured as zero (0) and cannot be changed.

N O T EIf multiple congestion levels are not configured, the SINAP/SS7 system implements the two-level international signaling network option for link congestion, which includes congestion onset level 1 (CONAN1) and congestion abatement level 1 (CONAB1).

L3T13 Waiting for force uninhibit 800-1500 ms

Table H-3. MTP Thresholds


CONON0 CONON1 CONON2 CONON3

Local Congestion Onset Levels 0-3. Defines the upper thresholds for link congestion (applies to all links on the local system). The value for each congestion onset level should be greater than its corresponding congestion abatement level. Default values are:Level Default*CONON0 0 CONON1 80 CONON2 110 CONON3 140

CONAB0 CONAB1 CONAB2 CONAB3

Local Congestion Abate. Defines the lower thresholds for link congestion (applies to all links on the local system). The value for each congestion abatement level should be less than its corresponding congestion onset level. Default values are:Level Default*CONAB0 0 CONAB1 50 CONAB2 90 CONAB3 120

Table H-2. MTP Level-3 Timers (Q.701 – Q.704 Bluebook) (Page 2 of 2)



SCCP Timers

SCCP TimersSCCP timer settings are shown in Table H-4.

SCCP Extended Unitdata (XUDT) Message TimersXUDT message timers define the time periods and reassembly periods for handling XUDT messages. XUDT messages are composed of MSU segments that are smaller than the default or maximum message size allowed for messages exchanged in the SINAP/SS7 network. See Chapter 3, ‘‘Software Configuration,” for how to define the segment sizes for XUDT messages.

The SCCP system tables in shared memory contain two XUDT timers:

• SCTX timer - This is the freeze timer that defines the time period during which an LRN assigned to multiple segments of the same message is frozen. The timer specifies the time period during which a released LRN cannot be reused on any node. The default value is 60 seconds.

N O T ECurrently, the SINAP/SS7 system uses the default value only. Subsequent releases will allow modification of the timer value.

• SCTY timer - This is the message reassembly timer that specifies the time period during which the message reassembly process receives and reassembles the XUDT message segments. There is one SCTY timer per node. The default value is 1 second.

Table H-4. SCCP Timers (Q.714 Bluebook)



5-60 s

SCT2 Coordinated State Change. Timer for subsystem-out-of-service-grant (SOG) after transmission of subsystem-go-out-of-service request to replicate subsystem.

5-60 s

SCT3 Ignore Subsystem Status Test. Time to wait after receiving a subsystem-out-of-service grant (SOG) and actually going out of service.

5-60 s

SCTX XUDT freeze timer that defines the time period during which an LRN assigned to multiple segments of the same message is frozen.

60 s

SCTY XUDT reassembly timer that specifies the time period during which the message reassembly process receives and reassembles the XUDT message segments.

1 s


Required Environment Variables

Required Environment VariablesAlthough you can activate many features for the China network variant, such as time-controlled changeover (TCCO), time-controlled diversion (TCD), connection-oriented features (COF), ISUP services, and global title translation (GTT), the MTP features, signaling point restart and user part flow control, are required in the China variant. To activate these features, uncomment the MTP_WHITE_BOOK_RESTART and MTP_USER_FLOW_CTRL environment variables in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node.

• MTP_WHITE_BOOK_RESTART enables the MTP restart feature that provides the orderly process for activating a node’s links and routes when the SINAP/SS7 system is started on the node.

• MTP_USER_FLOW_CTL sends a user part unavailable (UPU) message to the origination user part whenever an incoming message is received that cannot be delivered.

For more information on setting these environment variables, refer to Appendix B, ‘‘SINAP/SS7 Environment Variables.” See Chapter 3, ‘‘Software Configuration,” and Chapter 4, ‘‘System Operation and Maintenance,” for more information about the other available features.

MTP Restart The CCITT network variant allows you to activate the optional MTP restart feature. You must determine whether you want to initiate a full or partial MTP restart on your system, then define the proper environment variable, as follows.

• To enable the SINAP/SS7 system to perform full MTP restart on a particular node, uncomment the MTP_WHITE_BOOK_RESTART environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP node. You need not assign a value to the variable. The SINAP/SS7 system simply verifies the variable exists.

If the variable is defined, the MTP restart process performs whenever you start the SINAP/SS7 system on the node. If the MTP_WHITE_BOOK_RESTART variable is not defined, MTP restart is not performed when the SINAP/SS7 system is started on the node. If the variable is defined, MTP restart is performed whenever the SINAP/SS7 system is started.

• If a full restart is not required, you can perform a partial restart on a node. To enable partial restart, uncomment the MTP_PARTIAL_RESTART environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP/SS7 system. For instructions on defining variables, see Appendix B, ‘‘SINAP/SS7 Environment Variables.“



At the beginning of the MTP restart process, the SINAP/SS7 system activates the L3T20 timer and marks all concerned routes ALLOWED. The L3T20 timer defines the maximum amount of time allowed to complete all MTP restart activities. The L3T21 timer defines the amount of time to stop sending traffic to another node because that node is performing MTP restart. (See ‘‘Changing Timers and Link Congestion Threshold Settings’’ in Chapter 4 for information about these timers.)




• The SINAP/SS7 system only processes signaling network management (SNM) message types: TRA, TFP, TFR, and TFA. The SINAP/SS7 system discards all other SNM messages types, such as:

• Changeover and changeback message (CHM)

• Signaling-data-link-connection-order message (DLM)

• Emergency-changeover message (ECM)

• Signaling-traffic-flow-control message (FCM)

• Management inhibit message (MIM)

• Signaling-route-set-test message (RSM)

• User part flow control (UFC) message groups

SNM messages have a service instance (SI) of 0000.


The SINAP/SS7 system discards all incoming and outgoing messages (user traffic) for all types of applications: TCAP, SCCP, and ISDN User Part (ISUP).

MTP Time-Controlled ChangeoverThe China network variant supports time-controlled changeover (TCCO) procedures for the SINAP/SS7 system. TCCO supports handling of long-term or short-term processor outages or changeover orders received from the remote end during the MTP Level 3 T1 timer period.


MTP Time-Controlled Diversion

To enable TCCO functionality for your China network variant, uncomment the MTP_WHITE_BOOK_TCCO environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP/SS7 system. For instructions on defining variables, see Appendix B, ‘‘SINAP/SS7 Environment Variables.“

You need not assign a value to the variable. The SINAP/SS7 system simply verifies that the variable exists. You must define this environment variable before you start or restart the SINAP node to implement TCCO functionality based on the 1993 ITU-T recommendations for MTP. If you do not define it, the system defaults to TCCO procedures based on the 1988 recommendations.

MTP Time-Controlled Diversion In the China network variant, the time-controlled diversion (TCD) functionality is implemented automatically and is transparent to the user. That is, there are no environment variables to be set.

See “Time-Controlled Diversion” in Chapter 3 for a complete description of TCD.

Activation of China ISUP ServicesTo activate the China version of ISUP services, uncomment the ISUP_FEATURE=CHINA environment variable in the $SINAP_HOME/Bin/sinap_env.[csh or sh] environment file before starting the SINAP/SS7 system. For instructions on defining variables, see Appendix B, ‘‘SINAP/SS7 Environment Variables.“

Note that the version of ISUP services defined must agree with the network variant defined for the node. Therefore, if the China network variant is configured on the SINAP node, you can only specify the ISUP services version China in the ISUP_FEATURE environment variable. For more information on ISUP, see the SINAP/SS7 ISDN User Part (ISUP) Guide (R8053).

Unsupported SINAP/SS7 FeaturesThe China network variant does not support several SINAP/SS7 features, including:

• Fictitious own point code (FOPC)

• Combined link sets (CLS)

• Transfer-restricted message handling

• Loopback detection feature


Unsupported SINAP/SS7 Features


Appendix IList of Alarm and Event

MessagesI-

This appendix contains a list of the alarm event text messages the SINAP/SS7 system can generate. The alarms are listed in order of alarm category, subcategory, and event type.

This list does not classify the alarms by the default severity types used by the SINAP/SS7 system (alarm_types CRITICAL, MAJOR, MINOR, NOTICE). Alarm severity is determined by definitions in the SINAP/SS7 Trouble Treatment tables. Many SINAP/SS7 customers customize the SINAP/SS7 treatment tables making any severity list inaccurate and obsolete. The goal of this list is to provide a list of the descriptive text found in SINAP/SS7 alarms and to provide enough information about the alarms for customers to make reasonable decisions concerning customization of the SINAP/SS7 treatment tables. See ‘‘Handling Events’’ in Chapter 5 of this manual for more information on customizing the Trouble Treatment table.

This list does not contain the entire alarm text that is logged in the alarm or software notebook logs. This list only shows the descriptive text portion of the alarm. The remainder of the alarm information logged is in a standard format.

In some cases, the alarm actions instructs you to call the Stratus Customer Assistance Center (CAC) for help in resolving the problem. See the Preface of this manual for information about accessing this service.

Chapter 5, ‘‘Alarms, Events, and Error Messages,” of this manual provides more information about alarm formats, alarm text, categories, and events.

List of Alarm and Event Messages I-1

SINAP/SS7 Alarms

SINAP/SS7 AlarmsTable I-1 lists and describes the event categories that can generate alarms.

The event subcategories are too numerous to list in this document. See the event.h include file for more information on event subcategories.

The event types are:

• Hardware

• Software

• Network

The event type is used by Trouble Management to determine the log file in which the event alarm is logged. Hardware and network types are logged to the Alarm Log file and software events are logged to the Software Notebook. The SINAP/SS7 alarms listed in the next section are documented in the format shown in Table I-2

Table I-1. Event Categories Generating Alarms

Event Category Description

NM_EVENT Node Management Event Category

BI_EVENT BITE Event Category

SC_EVENT SCCP Management Event Category

L3_EVENT MTP Management Event Category

DR_EVENT Driver Event Category

CA_EVENT Internal (CASL, TCAP generated) Event Category

BK_EVENT Backup Event Category

GW_EVENT IP Gateway Event Category

LPCR_EVENT Distributed Logical Point Code (LPCR) Event Category (ISUP manager-generated alarms and events). For a listing of the ISUP manager alarms and events, see the SINAP/SS7 ISDN User Part (ISUP) Guide (R8053).

I-2 SINAP/SS7 User’s Guide R8051-17

Alarms and Events: Category NM_EVENT

.

Alarms and Events: Category NM_EVENTThis section contains the error messages for the category, NM_EVENT.

Table I-2. Alarm Formats

Message printf format of the message text contained in the alarm

Description Short description of the error.

Action Action to take to respond to the error message. This is just a short recommended action and in many cases action is totally dependent on the customer's specific network environment.

Source The SINAP/SS7 source code file name that contains the message. In some cases the SS7 message is also listed. Using the SS7 message, the network variant specifications can be used to further define the meaning and action for the reported SINAP/SS7 event.

Event The category/subcategory/type assigned to the message. See the SINAP/SS7 include file event.h for definition of the labels used.

Message NMCM: send I_NMCM_ALIVE failed

Description Failed to send an alive message to parent process.

Action The IPC message queue may be full. Check the queue for the Node Management parent process (nmcm).

Source nmcmmain.c

Event NM_EVENT / NMCM_RESET_EVENT / SW_EVENT

Message NMCM: get NP key failed

Description Failed to get IPC key of NM parent

Action The IPCTBL_load variable may not be current. Verify it to make sure it is current.

Source nmcmmain.c




Message NMCM: get CM key failed

Description Failed to get the Communication Management key of NM parent

Action The key for Node Management command management process (NMCM) may be missing, causing possible registration problems. Verify the IPC table to make sure it contains the CM key.

Source nmcmmain.c


Message NMCM: shmat() K_MTP_DISPLAY failed

Description Failed to attach shared memory segment MTP_DISPLAY.

Action Contact the CAC.

Source nmcmmain.c


Message NMCM: registration failed

Description Failed to register client process with the SINAP/SS7 system.


Source nmcmmain.c


Message NMCM: executing rclog failed

Description Recent Change log (rclog) is not available.

Action Check the contents of the Recent Change log. Each line should be an MML command that ends with a semicolon(;). Also check the directory and file permissions of the Recent Change log for read and write permission.

Source nmcmmain.c




Message NMCM: generating purgeday file failed

Description While generating purgeday data file, failure occurred.

Action The NM disk server returned an error while generating the purgeday file. Check the directory and file permissions of the purgeday file for read and write permission.

Source nmcmmain.c


Message NMCM: generating bkupday file failed

Description While generating the bkupday data file, failure occurred.

Action The NM disk server returned an error while generating the backup file. Check the directory and file permissions of the backup file for read and write permission.

Source nmcmmain.c


Message NMCM: unexpected cm_init return code

Description Failure occurred during CM initialization.

Action nmcm program fault. Contact the CAC.

Source nmcmmain.c


Message NMCM: ca_get_msg() for mml failed

Description Failed to receive an MML reply message from IPC queue due to can UNIX or CASL error.

Action Check the UNIX or CASL errno and take appropriate action if possible. Otherwise call the CAC.

Source nmcmmain.c

Event NM_EVENT / NMCM_ACCU_EVENT / SW_EVENT



Message NMCM: Unexpected IPC message recvd (type = %d)

Description IPC message with illegal message type was received.

Action Use the MML START_MON command to determine the message originator.

Source nmcmmain.c


Message Unexpected alarm clock went off

Description UNIX system alarm (SIGALRM) expired.

Action No action required.

Source nmnplibr.c

Event NM_EVENT / NMCM_ALARM_EVENT / SW_EVENT

Message ca_get_msg(I_MTP_CHANGE_ACK) failed

Description Getting message from client process's IPC queue for I_MTP_CHANGE_ACK failed.

Action Check application code.

Source nmcmchan.c (I_MML_RESP, MML_IA_ERR)


Message link has not been provisioned

Description Link configuration problem.

Action Check the SINAP/SS7 system configuration.





Message periodic slt flag already in requested state

Description Attempt to change link SLT flag to the current state.




Message ca_get_msg(I_MTP_CHANGE_ACK) failed

Description Getting message from client process's IPC queue for I_SCCP_CHANGE_ACK failed.

Action Check the IPC queue for nmcm. Verify that the nmcm is still running by using the ps command. If the problem persists, restart the SINAP/SS7 system.

Source nmcmchan.c, nmcmcrea.c, nmcmdele.c (I_MML_RESP, MML_IA_ERR)


Message ca_get_msg(I_SCCP_CHANGE_ACK) failed

Action Check the IPC queue for nmcm. Verify that the nmcm is still running by using the ps command. If the problem persists, restart the SINAP/SS7 system.

Source nmcmchan.c, nmcmcrea.c, nmcmdele.c (I_MML_RESP, MML_IA_ERR)


Message new data is provisioned, but ca_get_key() failed

Description Failed to get IPC key for a process.

Action Check IPC key.

Source nmcmclib.c (I_MML_RESP, MML_IA_ERR)




Message IPC get key failed

Description Getting the IPC key for a process was failed.

Action Verify that the process named is still running by using the ps command. Start the process named.



Message static data provisioned, but watchdog timer can't be set

Description nmdm sent a command to MTP and attempted to call ca_put_msg_def() to set the watchdog timer. The call to ca_put_msg_def() failed. Call the CAC.

Action Call the CAC.



Message static data provisioned, but get PN_SCMG key failed

Description nmdm tried to get IPC key of scmg but it failed.

Action Verify that the scmg is still running by using the ps command. Call the CAC.



Message Static link is provisioned, but IPC get key failed

Description IPC key of nmcm could not be identified.

Action Verify that the nmcm is still running by using the ps command. Call the CAC.





Message SCCP is not informed about the changes due to IPC error

Description Failed to send change message to SCCP via IPC queue.

Action Verify that the scmg is still running by using the ps command. Call the CAC.



Message ack from mtp is FAILED

Description Acknowledgment timer from MTP has expired.

Action Check the results of the last command issued. The command to the MTP may have been successful but because of process priorities, the ack timer may have expired before the ack was received. In other words, the ack from MTP may have arrived successfully but it was after the ack timer expired.


Event NM_EVENT / NMCM_INFO_EVENT / SW_EVENT

Message mtp response timeout

Description nmcm did not receive any response from MTP.

Action Ensure that the l3mp is still running by using the ps command.



Message ack from mtp is FAILED

Description A negative response to the MML command was received from MTP.

Action Check status of the SINAP/SS7 system. Restart the SINAP/SS7 system if necessary.





Message unknown ack from mtp

Description An unknown response to the MML command was received from MTP.

Action If this persists, run gathersy and call CAC.



Message sccp response timeout

Description Acknowledge signal from SCCP has timed out.

Action Check scmg process (ps -ef) for CPU usage and call CAC.



Message unexpected ack from sccp

Description Unexpected ack received from SCCP.

Action If this persists, run gathersy and call CAC.

Source nmcmclib.c


Message cannot ca_get_key() for CM

Description A process can not get IPC key.

Action Verify that the nmcm is still running by using the ps command. If it is not, restart the SINAP/SS7 system.

Source nmcmmain.c (I_MML_RESP, MML_IA_ERR)

Event NM_EVENT / NMCM_ALRM_EVENT / SW_EVENT


Alarms and Events: Category BI_EVENT

Alarms and Events: Category BI_EVENTNo alarms are generated in this release of the SINAP/SS7 system for BI_EVENT.

Message cannot ca_get_key() for DS


Action Verify that the NMDS is still running by using the ps command. If it is not, restart the SINAP/SS7 system.

Source nmcmmain.c (I_MML_RESP, MML_IA_ERR)

Event NM_EVENT / NMCM_ALRM_EVENT / SW_EVENT

Message cm_put_msg() to NMDS failed or timeout

Description An error occurred receiving the IPC message reply.

Action Verify that the NMDS is still running by using the ps command. Determine whether the NMDS is in heavy traffic. To do so, you can check MTP measurements, or CPU time for NM processes. If it is not, restart the SINAP/SS7 system.

Source nmcmcrea.c (I_MML_RESP, MML_INV_DATA)


Message NMCL_INVALID_BOUNDARY

Description Indicates an attempt to register duplicate data processes at different boundaries. For example, one process registers at the SCCP boundary and another at the SCCPX boundary.

Action Correct the user application and try again

Source CASL

Event None


Alarms and Events: Category SC_EVENT

Alarms and Events: Category SC_EVENTThis section describes the alarms in the category, SC-EVENT.

Message SCMG:Error sending SST to PC: %d errno: %d\n

Description Unable to send SST to PC due to UNIX or CASL error during ca_put_msu().

Action Check the UNIX or CASL errno and take appropriate action if possible. Otherwise call the CAC.

Source scmg-ssmg.c

Event SC_EVENT / SC_SUBCAT_ROUTING_FAILURE / NET_EVENT

Message SCCP Mgmt. MSU (connectionless) invalid NI and/or DPC, NI=%d, DPC=0x%05X\n

Description Indicates that the National Indicator (NI) or the Destination Point Code (DPC) are not equal to own NI or Point Code (PC). MSU was discarded.

Action Correct the network configuration to ensure that management messages are not sent to this node.

Source scmg-ssmg.c

Event SC_EVENT / SC_SUBCAT_INVALID_DPC / NET_EVENT

Message SCCP MGMT. MSU (Connection Oriented) invalid NI and/or DPC, NI=%d, DPC=0x%05X\n


Action Correct the network configuration to ensure that management messages are not sent to this node.

Source sccp-msu.c

Event SC_EVENT / SC_SUBCAT_INVALID_DPC / NET_EVENT



Message SC_CTRL_SCTY_TIMEOUT_ERR

Description Indicates that a routing entry remained in the XUDT routing table for a length of time exceeding the reassembly time limit.

Action Correct the user application and try again.

Source CASL

Event None

Message SC_RET_ERR_MSG_TRANS

Description Indicates an error in message transport.


Source CASL

Event None

Message SC_RET_ERR_LOC_PROC

Description Indicates an error in local processing.


Source CASL

Event None

Message SC_RET_NO_REASSEMBLY

Description Indicates that the message reassembly cannot be performed.


Source CASL

Event None



Message SC_RET_SCCP_FAIL

Description Indicates SCCP failure.


Source CASL

Event None

Message TC_ERR_INV_LEN_OF_CONTENTS [3041]

Description Indicates that the set of components exceeds the limits of the XUDT data parameter.


Source CASL

Event None

Message TC_ERR_INV_EXTND_DATA_PTR [3042]

Description Indicates that the tblock has an invalid pointer to the extended data buffer.


Source CASL

Event None


Alarms and Events: Category L3_EVENT

Alarms and Events: Category L3_EVENTThis section describes the alarms in the category, L3_EVENT.

Message ucomm %d: Link in service

Description Informational message to indicate link is restored to service.


Source iom2.c (M_IN_SERVICE)

Event L3_EVENT / L2_MIN_LINK_IN_SERVICE / NET_EVENT

Message ucomm %d: Link failed, alignment failed

Description The link failed because the SINAP/SS7 system did not receive a response to the link test message.

Action Network problems may be indicated. Determine cause of SLT message failure. Take appropriate network problem determination actions.

The SLT may also fail because the remote is performing an MTP restart procedure. Under these circumstances, it is possible, in accordance with the governing ANSI 1992 standard (ANSI network variant only), that an SLT message (with SI=0001) received at the remote is discarded by the remote. In this case, no action is required.

Source iom2.c (M_ALIGNMENT_NOT_POSSIBLE)

Event L3_EVENT / L2_MIN_LINK_FAILED / NET_EVENT link event = L2_LF_ALIGNMENT_FAILED

Message ucomm %d: Link failure, abnormal BSNR and BIBR

Description The link failed because the SINAP/SS7 system received abnormal BSNR or BIBR.

Action Network problems may be indicated. Determine cause of abnormal BSNR or BIBR. Take appropriate network problem determination actions.

Source iom2.c (M_ABNORMAL_FIBR_BSNR)

Event L3_EVENT / L2_MIN_LINK_FAILED / NET_EVENT link event = L2_LF_ABNORMAL_FIBR_BSNR



Message ucomm %d: Link failure, delay of remote ack

Description The link failed because the SINAP/SS7 system did not receive any response from remote node within T7 timer time.

Action Network problems may be indicated. Take appropriate network problem determination actions.

Source iom2.c (M_T7_EXPIRED)

Event L3_EVENT / L2_MIN_LINK_FAILED / NET_EVENT link event = L2_LF_EXCESSIVE_DEL_ACK

Message ucomm %d: Link failure, excessive at the remote end

Description The link failed because the SINAP/SS7 system received SIB from remote end or T6 timer expired.

Action Network problems may be indicated. Take appropriate network problem determination actions.

Source iom2.c (M_T6_EXPIRED)

Event L3_EVENT / L2_MIN_LINK_FAILED / NET_EVENT link event = L2_LF_EXCESSIVE_CONGESTION

Message ucomm %d: Link failure, SUERM error

Description The link failed because the Signaling Unit Error Rate Monitor count has exceeded the threshold.

Action Link should be checked for errors possibly with datascope. Take appropriate network problem determination actions.

Source iom2.c (M_SUERM_ERROR)

Event L3_EVENT / L2_MIN_LINK_FAILED / NET_EVENT link event = L2_LF_SUERM_ERROR



Message ucomm %d: Link failure, cable disconnect

Description Link failure occurred for ucomm %d.

Action Check cable connection. If problem continues, connect a datascope and check data set lead status. Take appropriate network problem determination actions.

Source iom2.c (M_DSR_FAILURE)

Event L3_EVENT / L2_MIN_LINK_FAILED / HW_EVENT

Message MSU discarded in Ucomm %d

Description UCOMM driver failed to deliver an MSU to remote because UCOMM transmission buffers were full.

Action Check link status. Check MSU contents. Take appropriate network problem determination actions.

Source iom2.c (M_MESSAGE_DISCARDED)

Event L3_EVENT / L2_MESSAGE_DISCARDED / NET_EVENT

Message ucomm %d: Invalid MSU size on the transmission path. MSU is discarded

Description The SINAP/SS7 system received an invalid MSU from the remote.

Action If problem continues, connect a datascope and check incoming MSUs. Take appropriate network problem determination actions.

Source iom2.c (M_INVALID_MSU_SIZE)

Event L3_EVENT / L2_MIN_INVALID_MSU_SIZE / SW_EVENT

Message link_set %d available \n

Description Link set is restored to service.


Source l3mtmeas.c

Event L3_EVENT / L3MT_NET_LS_AVAILABLE / NET_EVENT



Message link_set %d unavailable \n

Description Link set failure occurred for link set %d. All links for the link set are failed.

Action Links associated with link set should be checked for failure and appropriate action taken.

Source l3mtmeas.c

Event L3_EVENT / L3MT_NET_LS_UNAVAILABLE / NET_EVENT

Message link_set %d, link with SLC %d available

Description Link in link set is restored to service.


Source l3mtmeas.c

Event L3_EVENT / L3MT_NET_LINK_AVAILABLE / NET_EVENT

Message link_set %d, link with SLC %d unavailable

Description Link failure occurred in link set %d.

Action Link should be checked for failure and appropriate action taken.

Source l3mtmeas.c

Event L3_EVENT / L3MT_NET_LINK_UNAVAILABLE / NET_EVENT

Message link set %d, link %d, inhibit denied

Description Unable to set link in link set to INHIBIT.


Source l3mtutil.c (M_INHIBIT_DENIED)

Event L3_EVENT / L3MT_NET_INHIBIT_DENIED / NET_EVENT



Message link set %d, link %d, inhibit request timeout

Description Inhibit request for link in link set timed out.


Source l3mtutil.c (M_INHIBIT_REQUEST_TIMEOUT)

Event L3_EVENT / L3MT_NET_INHIBIT_TIMEOUT / NET_EVENT

Message link set %d, link %d link inhibited

Description Link in link set is set to INHIBIT.


Source l3mtutil.c (M_LINK_INHIBITED)

Event L3_EVENT / L3MT_NET_LINK_INHIBITED / NET_EVENT

Message link set %d, link %d link uninhibited

Description Link in link set is set to UNINHIBIT.


Source l3mtutil.c (M_LINK_UNINHIBITED)

Event L3_EVENT / L3MT_NET_LINK_UNINHIBITED / NET_EVENT

Message link set %d, link %d uninhibit timeout

Description Unable to set link in link set to INHIBIT.


Source l3mtutil.c (M_UNINHIBITED_TIMEOUT)

Event L3_EVENT / L3MT_NET_UNINHIBIT_TIMEOUT / NET_EVENT



Message link set %d, link %d uninhibit not possible

Description Unable to set link in link set to UNINHIBIT.


Source l3mtutil.c (M_UNINHIBITING_NOT_POSSIBLE)

Event L3_EVENT / L3MT_NET_UNINHIBIT_NOT_POSSIBLE / NET_EVENT

Message link set %d, link %d link remotely inhibited

Description Link in link set is set to INHIBIT by remote.


Source l3mtutil.c (M_LINK_REMOTELY_INHIBITED)

Event L3_EVENT / L3MT_NET_LINK_REMOTE_INHIBIT / NET_EVENT

Message link set %d, link %d link remotely uninhibited

Description Link in link set is set to UNINHIBIT by remote.


Source l3mtutil.c (M_LINK_REMOTE_UNINHIBIT)

Event L3_EVENT / L3MT_NET_LINK_REMOTE_UNINHIBIT / NET_EVENT

Message BSNT retrieval timeout, ls %d, link %d

Description BSNT retrieval timer expired on indicated link set and link.

Action Ensure that indicated link set and link are available.

Source l3co.c (M_BSNT_TIMEOUT)

Event L3_EVENT / L3CO_HW_BSNT_RETRIEVAL_TIMEOUT / HW_EVENT



Message First CBA timer expired ls %d, link %d

Description First CBA timer has expired on indicated link set and link at change back.

Action Check link set and link status.

Source l3cb.c (M_L3_T4_EXPIRED)

Event L3_EVENT / L3CB_NET_FIRST_CBA_TIMEOUT / NET_EVENT

Message Second CBA timer expired ls %d, link %d

Description Second CBA timer has expired on indicated link set and link at change back.


Source l3cb.c(M_L3_T5_expired)

Event L3_EVENT / L3CB_NET_SECOND_CBA_TIMEOUT / NET_EVENT

Message sls field non-zero, H0H1=0x%x from ucomm %d

Description Illegal SLS field in M_BLOCK.

Action Check switch side SLS field configuration. Determine why switch is sending illegal SLS.

Source l3dt.c

Event L3_EVENT / L3DT_IN_EVENT_SLC / NET_EVENT

Message Second CBA timer expired ls %d, link %d

Description Second CBA timer has expired on indicated link set and link at change back.


Source l3cb.c(M_L3_T5_expired)

Event L3_EVENT / L3CB_NET_SECOND_CBA_TIMEOUT / NET_EVENT



Message spare field non-zero, H0H1=0x%x from ucomm %d

Description Spare field must be zero.

Action Check switch side configuration. Determine why switch is sending data in the spare field.

Source l3dt.c

Event L3_EVENT / L3DT_IN_EVENT_SPARE / NET_EVENT

Message unsupported SNM msg, H0H1=0x%x from ucomm %d

Description Unsupported SNM message was received.

Action Check switch side configuration. Determine why switch is sending unsupported SNM message.

Source l3dt.c

Event L3_EVENT / L3DT_ST_EVENT_MSU / NET_EVENT

Message Own SP restarting - H0H1=0x%x from ucomm %d discarded

Description During the MTP restart procedure only certain incoming SNM MSUs (SI=0000) (for CCITT/China: TFP, TFC, TFA, and TRA; for ANSI: TFP, TFC, TFA, TRA, TRW, CBD, and CBA) are allowed in compliance with the governing standards. All other SNM MSUs are rejected in compliance with the standards.


Source 13dt.c (main)




Message MTP3 state event: sub: 0x%x(Wrong SLC), state: %d, code: 0x%x

Description Default action taken for given state. This message displays when an MTP Level 3 SNM message with a wrong SLC is received.

Action No action required unless otherwise determined in mtpevents.h.

Source 13dt.c,

Events L3_EVENT / L3CB_ST_EVENT / SW_EVENTL3_EVENT / L3CO_ST_EVENT / SW_EVENTL3_EVENT / L3CR_ST_EVENT / SW_EVENTL3_EVENT / L3DT_IN_EVENT_LS / SW_EVENTL3_EVENT / L3DT_IN_EVENT_DPC / SW_EVENTL3_EVENT / L3DT_IN_EVENT_SLC / SW_EVENTL3_EVENT / L3DT_ST_EVENT_MAIN / SW_EVENTL3_EVENT / L3FR_ST_EVENT / SW_EVENTL3_EVENT / L3LA_ST_EVENT / SW_EVENTL3_EVENT / L3RC_ST_EVENT_LINK / SW_EVENTL3_EVENT / L3RC_ST_EVENT_MAIN / SW_EVENTL3_EVENT / L3RC_IN_CONFIGURE_RS / SW_EVENTL3_EVENT / L3RC_IN_CHANGE_RS / SW_EVENTL3_EVENT / L3RC_IN_CHANGE_DEST / SW_EVENT

Message MSU discarded at SS7 Driver(CCITT and TTC NSP variants)

Description Unable to route MSU therefore MSU was discarded. Routing failure reason is further explained by the alarm state field reported in alarm or by the L3_EVENT_T errno field.

Action Check link status. Additional actions may be taken depending on the L3_EVENT_T errno (alarm state) field.

Source l3mtutil.c (M_dr_event)

Event L3_EVENT / L3DR_NET_EVENT / NET_EVENT



Message MSU for unprovisioned dpc %d-%d-%d at driver(ANSI and China NSP variants)

Description Unable to route MSU because of an L3_DR_NO_ROUTING_FOR_DPC (0x02) error, therefore the MSU was discarded.




Message MSU for inaccessible dpc %d-%d-%d at driver(ANSI and China NSP variants)

Description Unable to route MSU because of an L3_DR_INACCESSIBLE_DPC 0x02 error, therefore the MSU was discarded.




Message MSU for held lset %d for dpc %d-%d-%d at driver(ANSI and China NSP variants)

Description Unable to route MSU because of an L3_DR_NEWROUTE_HELD 0x03 error, therefore the MSU was discarded.






Message MSU for held ucomm %d for dpc %d-%d-%d at driver(ANSI and China NSP variants)

Description Unable to route MSU because of an L3_DR_NEWLINK_HELD 0x04 error, therefore the MSU was discarded.




Message MSU for offline ucomm %d for dpc %d-%d-%d at driver(ANSI and China NSP variants)

Description Unable to route MSU because of an L3_DR_DISCARDED_OFFLINE error, therefore the MSU was discarded.




Message MSU for unknown error at driver

Description Unable to route MSU because of an unknown error, default case will be executed, therefore the MSU was discarded




Message no link for COx, ls %d, link %d, alt %d

Description Failed to find link to send to Changeover or Changeover Acknowledgment.


Source l3rt.c

Event L3_EVENT / L3RT_NET_EVENT / NET_EVENT



Message no link for ECx, ls %d, link %d, alt %d

Description Failed to find link to send to Emergency Changeover or Emergency Changeover Acknowledgment.


Source l3rt.c


Message no link for INH for ls %d, link %d

Description Failed to find link to send link Inhibit message.


Source l3rt.c


Message no link for RST to Route Set 0x%x

Description No link available for route set to destination.


Source l3rt.c


Message congested dpc %d (0x%x)(CCITT and TTC NSP variants)

congested dpc %d-%d-%d(ANSI and China NSP variants)

Description The link to indicated DPC is congested. MSU was discarded.

Action Check link status. Determine congestion cause.

Source l3mtutil.c (M_MESSAGE_FOR_CONGESTED_DESTINATION)

Event L3_EVENT / L3CA_NET_EVENT / NET_EVENT



Message CASL discard MSU: inaccessible %d(0x%x)(CCITT and TTC NSP variants)

CASL discard MSU: inaccessible dpc %d-%d-%d(ANSI and China NSP variants)

Description Unable to route MSU due to DPC inaccessible. MSU was discarded.

Action Check status of route set, link set, and links in the link set. Take appropriate action to correct routing failure. Check configuration.

Source l3mtutil.c (M_MESSAGE_RECEIVED_FOR_INACCESIBLE_SP)


Message CASL discard MSU: no routing data for dpc %d(0x%x)(CCITT and TTC NSP variants)

CASL discard MSU: no routing data for dpc %d-%d-%d(ANSI and China NSP variants)

Description CASL received and discard MSU, because the SINAP/SS7 system does not have routing data for indicated DPC. This is a SINAP/SS7 configuration problem.


Source l3mtutil.c (M_NO_ROUTING_DATA_FOR_MESSAGE)


Message msg_id=0x%x discarded when linkset=%d adjacent_sp_restarting

Description When an adjacent signaling point is restarted and the MTP restart procedure for any variant is enabled, the adjacent signaling point may discard certain types of MSUs in compliance with the governing standards. If the SINAP node attempts to transmit these MSUs, this message results.


Source l3rt.c




Message 5-bit SLS Map unbalanced

Description The 5-bit SLS Map Signaling Link Code (SLC) frequencies differ by more than one.

Action No action is required if the SINAP node is running in an SS7 network that conforms only to ANSI 1988 standards, or if the node is running in a network that does not loadshare traffic.

If the SINAP node is running in an SS7 network that loadshares traffic and conforms to ANSI 1992 / ANSI 1996 standards, contact Stratus’ Customer Assistance Center (CAC).

(Note: This alarm does not necessarily mean loadshared traffic will not be evenly distributed.)

Source l3rt.c

Event L3_EVENT

Message 8-bit SLS Map unbalanced

Description The 8-bit SLS Map Signaling Link Code (SLC) frequencies differ by more than one.

Action No action is required if the SINAP node is running in an SS7 network that conforms only to ANSI 1988 standards, or if the node is running in a network that does not loadshare traffic.

If the SINAP node is running in an SS7 network that conforms to ANSI 1992 / ANSI 1996 standards and that loadshare traffic and 8-bit SLS processing is or will be required, contact Stratus’ Customer Assistance Center (CAC).

(Note: This alarm does not necessarily mean loadshared traffic will not be evenly distributed.)

Source l3rt.c

Event L3_EVENT



Message route_set %d inaccessible

Description The route set is inaccessible because one of the following events occurred:

• All signalling link sets for this route set have failed

• All signaling route sets associated with the route set have become inactive

• The route set is blocked, the DPC associated with this route set is down, or the SINAP node received a TFP for the point code

Action Check the link set status to determine if any TFP messages were received and the appropriate action taken.

Source l3mtmeas.c

Event L3_MT_NET_ROUTE_SET_INACCESSIBLE

Message route_set %d accessible

Description The route set specified by %d is accessible for a node.

Action No action is required.

Source l3mtmeas.c

Event L3_MT_NET_ROUTE_SET_ACCESSIBLE

Message unsupported TTC h0_h1:0x%x to DPC: (%d)0x%x(TTC NSP variant)

Description Unsupported TTC SNM messages

Action Check why the SNM h0_h1 message was received.

Source l3rt.c




Message MTP Mgmt: MSU with invalid NI and/or DPC, NI=%d, DPC: %d(0x%05X)(CCITT and TTC NSP variants)

MTP Mgmt: MSU with invalid NI and/or DPC, NI=%d, DPC: %d-%d-%d(All other NSP variants)


Action Correct the network configuration to ensure that management messages are sent and received accordingly.

Source l3dt.c


Message link %d congestion status changed from %d to %d

Description Link congestion status changed.


Source l3rclink.c (M_driver_congestion status)


Message linkset %d congestion status changed from %d to %d

Description Linkset congestion status changed.


Source l3rclink.c (M_driver_congestion status)



Alarms and Events: Category DR_EVENT

Alarms and Events: Category DR_EVENTThis section describes the events in the category, DR-EVENT.

Message dpc %d (0x%x) congestion status changed from %d to %d(CCITT and TTC NSP variants)

dpc %d-%d-%d congestion status changed from %d to %d(ANSI and China NSP variants)

Description Routeset (DPC) congestion status changed.


Source l3rclink.c (M_driver_congestion status),l3rcrout.c (M_transfer_controlled)


Message L2 MTP Loaded and Running on UCOMM (%d)

Description L2 MTP loaded as UCOMM firmware for %d=ucomm device number. GIC event GIC_STATUS_PHY_UP received.


Source drmf.c

Event DR_EVENT / DR_EVENT_LVL1 / HW_EVENT

Message Link Down (%d, %d)

Description Link is down for %d=device number. GIC event GIC_STATUS_PHY_DOWN received.

Action Check link status. Check status of IOA hardware using UNIX hwmaint command.

Source dr_main.c

Event DR_EVENT/ DR_EVENT_LVL1 / HW_EVENT



Message Insufficient Resources

Description Allocation of SINAP/SS7 driver resource failed. Unable to allocate a block of kernel memory or initialize a basic lock.

Action Check kernel memory usage. Verify MINARMEM and MINASMEM kernel tuning parameters. See the UNIX documentation for your site for more information.

Source dr_distmux.c, dr_locon.c

Event DR_EVENT / DR_EVENT_LVL2 / SW_EVENT

Message MTP L3 Insufficient Resources

Description Allocation of SINAP/SS7 Driver resource failed. Unable to allocate a streams message block.

Action Check kernel streams usage. Verify STRTHRESH kernel tuning parameter. See the UNIX documentation at your site for more information.

Source l3dr.c

Event DR_EVENT / DR_EVENT_LVL2 / SW_EVENT

Message Lost MSU, Process Not Found (SSN %d)

Description Driver attempted to deliver an MSU to a receiving application for SSN but application was not found.

Action TCAP user application is no longer registered with the SINAP/SS7 system. Determine why user application may have failed.

Source drld.c

Event DR_EVENT / DR_EVENT_LVL3 / NET_EVENT

Message Lost MSU, Process Not Found (SIO %d)

Description Driver attempted to deliver an MSU to a receiving application for SIO but application was not found.

Action MTP user application is not longer registered with the SINAP/SS7 system. Determine why user application may have failed.

Source drld.c




Message Lost MSUs (SIO %d PID %d)

Description Incoming MSUs for SIO were discarded because inbound driver buffer for process PID is full.

Action Check user application ca_register parameter max_msu_input_que. Increase input queue depth in registration parameters.

Source drld.c


Message Lost MSUs (SSN %d PID %d)

Description Incoming MSUs for SSN were discarded because inbound driver buffer for process PID is full.

Action Check user application ca_register parameter max_msu_input_que. Increase input queue depth in registration parameters.

Source drld.c


Message %s Load Control %s for SSN %d

Description Load control state and action for SSN group.


Source dr_locon.c


Message %s Load Control %s for SSN %d Instance %d

Description Load control state and action for SSN instance.


Source dr_locon.c



Alarms and Events: Category CA_EVENT

Alarms and Events: Category CA_EVENTThis section describes the events in the category, CA-EVENT.

Message **** Process %s,%s (pid=%d) issued exit(%d)

Description SINAP/SS7 process issued exit.

Action If the process is a critical SINAP/SS7 process, the SINAP/SS7 system will be automatically restarted. No action required.

Source cappmain.c

Event CA_EVENT / CA_PROC_MAJOR_EVENT / SW_EVENT

Message **** Process %s,%s (pid=%d) died..., signal=%d

Description Process died as a result of receiving signal %d.

Action Determine why process received signal. See signal.h or SINAP/SS7 s7signal.h for the text description of the signal reported.

Source cappmain.c


Comment If the process IPC key is a valid for the PID, the subcategory will be reported as CA_PROC_FAILED.

Message Process %s,%s (pid=%d) died..., signal=%d (core dump)

Description Process died as a result of receiving signal %d and created a core file.

Action Determine why process received signal. See signal.h or SINAP/SS7 s7signal.h for the text description of the signal reported. (Note: If the process IPC key is valid for the PID, the subcategory is reported as A_PROC_FAILED.)

Source cappmain.c




Message add_child(%s): executable filename too long

Description The child process name you are tying to use is longer than MAX_FILENAME. See the SINAP/SS7 include file sinap.h for the current value for MAX_FILENAME for this release of the SINAP/SS7 system.

Action Rename the child process to a name that is less than the maximum length of MAX_FILENAME.

Source cappmain.c


Message add_child(%s): Couldn't find table slot

Description You can not add a child process because there is no slot available in the SINAP/SS7 child slot table. All slots are in use.

Action Decrease number of child processes. Currently the maximum number of child processes allowed in the SINAP/SS7 system is 32 (NCHILD).

Source cappmain.c


Message add_child(%s): no executable file specified

Description Your application attempted to execute a non-executable file.

Action Check the file for executable rights.

Source cappmain.c


Message add_child(%s): Process Table full

Description You can not add a child process because the child process table is full.

Action This is an UNIX configuration problem. Verify NPROC and MAXUP kernel tuning parameters. See the UNIX documentation at your site for more information.

Source cappmain.c




Message fork() failed: errno=%d

Description An attempt to start a child process failed. An UNIX error returned at fork().

Action Check the UNIX errno and take appropriate action.

Source cappmain.c


Message execv() failed: errno=%d

Description An attempt to start a child process failed. An UNIX error returned at execv().

Action Check the UNIX errno and take appropriate action.

Source cappmain.c


Message handle_msg(): Restart for unknown child (pid=%d)

Description An unknown child process died.


Source cappmain.c


Message delete_child(%d): entry inactive or child executing.

Description Your application tried to delete an inactive process or the process is executing its child process.

Action Check the status of the application's child process.

Source cappmain.c

Event CA_EVENT / CA_PROC_MINOR_EVENT / SW_EVENT

Message add_child(%s): Process Table full



Message main(): No Child Process

Description A SINAP/SS7 parent process could not detect its children processes.

Action Get a list of processes (ps -ef) and call CAC.

Source cappmain.c


Message main(): unknown child (pid=%d) died

Description A SINAP/SS7 process was notified of the death of one of its children but could not determine which one.

Action Get a list of processes (ps -ef) and call CAC

Source cappmain.c


Message delete_child(%d): number out of range

Description Your application tried to delete a child process that does not exist.

Action Check the status of the application's child process.

Source cappmain.c


Message handle_msg(): Unexpected IPC msg recvd (type=0x%x)

Description An unknown IPC message was received by a parent process.

Action Check application code which issued the IPC message.

Source cappmain.c

Event CA_EVENT / CA_PROC_NOTICE_EVENT / SW_EVENT



Message NMDM catches unexpected signal - SIGHUP

Description SINAP/SS7 process NMDM received an unexpected signal.

Action Check status of NMDM process. Call the CAC.

Source cadefmsg.c

Event CA_EVENT / CA_PROC_NOTICE_EVENT / SW_EVENT

Comment Same message is also reported for unexpected signals: SIGINT, SIGILL, SIGTRAP, SIGSABRT, SIGEMT, SIGFPE, SIGBUS, SIGSYS, SIGIPE, SIGUSR1, SIGUSR2, SIGPOLL, SIGVTALRM, SIGPROF, SIGXCPU, SIGXFSZ

Message %s,errno=%d Err in sending msg to proc=%x

Description An UNIX or CASL error occurred when attempting to send an IPC to another process.

Action Check the UNIX or CASL errno and take appropriate action.

Source cadefmsg.c

Event CA_EVENT / CA_SUBCAT / SW_EVENT

Comment errno != EINTR || errno != EAGAIN

Message ca_dfm_init() - Err in malloc

Description malloc() for IBLK_MSG_T failed.


Source cadefmsg.c


Message ca_dfm_main() - Err from ca_get_msg()

Description An UNIX or CASL error returned at ca_get_msg().

Action Check the UNIX or CASL errno and take appropriate action if possible. Otherwise contact the CAC.

Source cadefmsg.c




Comment errno != EINTR || errno != EAGAIN

Message ca_dfm_process_msgs() - could not insert an entry

Description The nmcm process cannot process any more deferred message requests.

Action Make sure a user application is not sending too many deferred message requests (ca_put_msg_def).

Source cadefmsg.c


Message ca_dfm_process_msgs() - unknown msg type

Description A SINAP/SS7 user application tried to send an invalid message type in ca_put_msg_def().

Action Check ca_put_msg_def() call to make sure message types are valid as specified in iblock.h

Source cadefmsg.c


Message ca_dfm_restart() - could not insert entry

Description The SINAP/SS7 system could not handle all the ca_cancel_def() calls.

Action Make sure an application is not sending too many ca_cancel_def() requests.

Source cadefmsg.c


Message IPC Failed: %s,%s->%s,%s - msg_type = 0x%x, errno = %d, #%d

Description A process failed to send an IPC to trouble management. The error message displays the text value of the IPC key for the sending process and the receiving process. The IPC message type is also displayed.

Message ca_dfm_main() - Err from ca_get_msg()



Action The IPC message queue may be full. Check the queue for the processes reported in the error message. Verify that the sending and receiving processes are still running by using the ps command. If the problem persists, restart the SINAP/SS7 system.

Source camgment.c

Event CA_EVENT / CA_IPC_FAILED / SW_EVENT

Message CA_ERR_XMAX_SIZE [2108]

Description Indicates that the size of the XUDT data parameter exceeds the maximum of 2048, or the number of segments exceeds 16. The number of segments is determined by dividing the data size by the segment size, which is specified in the SINAP_XUDT_SEGMENT_SIZE environment variable.


Source CASL

Event None

Message CA_ERR_REG_REACOUNT

Description Indicates that zero was specified for the value in the reassembly_count field of the registration parameter structure, register_reg_t.


Source CASL

Event None

Message IPC Failed: %s,%s->%s,%s - msg_type = 0x%x, errno = %d, #%d


Alarms and Events: Category BK_EVENT

Alarms and Events: Category BK_EVENTThis section describes the events in the category, BK-EVENT.

Message auto node backup NODE-BKUP cannot register

Description Automatic node backup is not working.

Action Restart the automatic backup program again. If the condition persists, restart the SINAP/SS7 system. Call the CAC.

Source nmnpnbkp.c

Event BK_EVENT / BK_INFO_EVENT / SW_EVENT

Message Backup Node command issued

Description This message is informational and requires no action.


Source nmnpnbkp.c


Message cannot get key for NM-CM



Source nmnpnbkp.c


Message cannot get key for NMCM



Source nmnpnbkp.c



Alarms and Events: Category GW_EVENT

Alarms and Events: Category GW_EVENTThis section describes the events in the category, GW-EVENT used in the SGC.

Message SCIPGW: SG Error. Received service message with no association for SSN:<ssn>.

Description The SGC has received a service message for which it has no acknowledged routing key. The SSN value can be 0 (no SSN in incoming message) or 1-255. The message is intentionally dropped by the SGC.

Action If seen only transitorily when shutting down the SGC say, none. If persistent the SG is consistently sending message to the wrong address. Investigate the SG or SGS and repair that accordingly.

Source sccallbacks.c

Event SW_EVENT

Message SCIPGW: shmat() failed, errorno: %d.

Description The SGC could not attach to or deattach from an SHM segment (PSYSTEM).

Action Check that SINAP is running. If not, start it; otherwise, call the CAC.

Source scmain.c

Event SW_EVENT

Message SCIPGW: Cannot ascertain local host.

Description The Gateway is unable to ascertain the local host that was specified in the configuration file.

Action Check the Gateway configuration file for errors and the TCP/IP configuration. Use ping from the remote box as necessary to confirm the host name.

Source scmain.c



Event SW_EVENT

Message SCIPGW: Could not initialize TALI timers.

Description The Gateway could not initialize the SS7 over IP timers.

Action Add more dynamic memory for the Gateway via a System Administrator. Contact Stratus CAC if the problem persists.

Source scmain.c

Event SW_EVENT

Message SCIPGW: TALI_CreateSession Failed with error

Description The Gateway could not create an SS7 over IP session.

Action Check the SS7 over IP configuration. Add more dynamic memory for the Gateway via a System Administrator. Contact Stratus CAC if the problem persists.

Source scmain.c

Event SW_EVENT

Message SCIPGW: Error sending MSU to SS7.

Description The Gateway could not send the message that was received from the SS7 over IP interface to the SS7 network.

Action Check the SS7 configuration (MML). If all else fails, contact the Stratus CAC.


Event SW_EVENT

Message SCIPGW: A TALI route to the destination is reachable.

Description An SS7 over IP route has been established.

Action None


Message SCIPGW: Cannot ascertain local host.



Event SW_EVENT

Message SCIPGW: An unknown route became available.

Description An SS7 over IP route which is unknown in the configuration file becomes available.

Action Check the Gateway configuration. Contact the Stratus CAC if the problem persists.


Event SW_EVENT

Message SCIPGW: A TALI route to destination is unreachable.

Description Lost connection to another SS7 over IP Server/Client.

Action Check the SS7 over IP clients and IP Network. Restart the SS7 over IP clients and Servers as necessary. Use ping to check the status of the IP network. If this message appears after prohibiting traffic on a route, no action is required.


Event SW_EVENT

Message SCIPGW: An unknown route became unavailable.

Description An SS7 over IP route, which is not identified in the configuration file, has become unavailable.

Action None. Contact the Stratus CAC if the problem persists.


Event SW_EVENT

Message SCIPGW: A TALI route to the destination is reachable.



Message SCIPGW: No TALI connection available to PC.

Description An MSU incoming from the SS7 network has no known SS7 over IP Destination.

Action Check the Gateway and SS7 network configuration.


Event SW_EVENT

Message SCIPGW: Error Sending TALI SCCP Message.

Description The SCCP message could not be sent.

Action Check the Gateway configuration. Contact the Stratus CAC if the problem persists.


Event SW_EVENT

Message SCIPGW: ca_get_msu_failed.

Description An MSU could not be retrieved.

Action Check the Gateway and SS7 network configuration. Contact the Stratus CAC if the problem persists.


Event SW_EVENT



Message SCIPGW: Insufficient Memory to create CPC list.

Description There is insufficient memory to create the CPC list. The CPC list is part of the SCIPGW database.

Action Provision more memory.


Event SW_EVENT

Message SCIPGW: Insufficient Memory to add to CPC list.

Description There is insufficient memory to add to the CPC list. The CPC list is part of the SCIPGW database.

Action Provision more memory.


Event SW_EVENT

Message SCIPGW: TALI route: <n> is congested.

Description The Round Trip Time (RTT) between the issuance of a moni on an IP connection and the receipt of a mona has exceeded the congestion onset time.

Action If received after an alarm indicating the TALI route is unavailable, None. Otherwise, check the IP Networks Traffic Loading. If the load cannot be reduced then alter the IP Congestion congestion onset and abate values using the CHANGE_IP_CONG_ONSET and CHANGE_IP_CONG_ABATE values until the congestion abates (see next alarm). If this action does not relieve the congestion contact Stratus CAC.


Event SW_EVENT


Terminal Handler Errors

Terminal Handler ErrorsThis is a list of SINAP/SS7 alarms that can be returned to the SINAP/SS7 Terminal Handler (sysopr login). The action list for this list is very brief as in most cases the error and the cause of the error are obvious.

A majority of the errors indicate an error in either the format of the MML command or the MML command configuration request. The action directive to “Check SINAP Configuration” indicates that the requested configuration command can not be completed and the SINAP/SS7 configuration related to the configuration command and error messages should be checked. The

Message SCIPGW: TALI route: <n> is uncongested.

Description A previous IP congestion condition (see the above alarm) has abated.

Action None, but see the above alarm and investigate the source of the initial congestion.


Event SW_EVENT

Message SCIPGW: Could not allocate RST timer memory.

Description There is insufficient memory to start an RST timer, consequently future RSTs will not be performed. The consequence of this is that traffic may not flow to the appropriate point code (the TALI route is unusable for that point code).

Action Preferably shutdown the SGC and add more dynamic memory. Processing need not be interrupted, however this is an unsafe mode should the PC via backup routes become unreachable. Adding more memory is recommended.

Source scss7ip.c

Event SW_EVENT

Message SCIPGW: Broken Pipe.

Description The peer node has abruptly closed the socket causing a Broken Pipe signal on the next transmit attempt.

Action Check the peer node/IP network for correct operation.

Source scmain.c

Event SW_EVENT


Terminal Handler Alarms

action directive to Check MML Command Parameters indicates that the MML command, or some parameter of the MML command, is invalid. You should review the MML command for errors.

The SINAP/SS7 alarms are documented in the format shown in Table I-3.

Table I-3. Alarm Formats

Terminal Handler AlarmsThis section contains charts depicting the alarms generated by the Terminal Handler. Each alarm contains the text of the alarm message, a description of the alarm, the recommended action, the source, and the actual event that generated the alarm.

Message printf format of the message text found in the alarm.

Description Short description of the error.

Action Action to take to respond to the error message. This is just a short recommended action and in many cases action is totally dependent on the customer's specific network environment.

Source The SINAP/SS7 source code file name which contains the message. In some cases the SS7 message is also listed. Using the SS7 message, the network variant specifications can be used to interpret and resolve the SINAP/SS7 event.

Event The category/subcategory/type assigned to the message. See the SINAP/SS7 include file event.h for definition of the labels used.

Message ducpc still exists

Description Duplicate concerned point code still exists.


Source nmcmchan.c (I_MML_RESP, MML_INV_DATA)

Event NM_EVENT / NULL / SW_EVENT

Message unknown parameter from command parsing

Description Invalid parameter found parsing an MML command.

Action Check MML command. Correct MML command parameters.

Source nmcmchan.c (I_MML_RESP, MML_INV_PNAME)




Message ducpc is not yet provisioned

Description Duplicate concerned point code not provisioned.




Message concerned pc has not been provisioned

Description Concerned point code not provisioned.




Message rpc is not a cpc

Description Remote point code is not a concerned point code.




Message pc has not been provisioned

Description Point code has not been provisioned.




Message unknown parameter from command parsing



Message no remssn provisioned

Description No remote SSN provisioned.




Message maximum number of routes has been reached

Description Maximum number of routes that can be configured in a route set (MAX_ROUTE_PER_RS) already has been configured. See the SINAP/SS7 include file sinap.h for the current value of MAX_ROUTE_PER_RS for this release of the SINAP/SS7 system.




Message delroute is the last route in routeset

Description The route being deleted is the last one in the route set.




Message delroute is not a route

Description Attempt to delete a route that is not a member of the named route set.




Message priority too big

Description Priority in the MML is greater than current maximum priority plus one. The allowed priorities are 0-15.



Action Check the SINAP/SS7 system configuration or MML command parameters.



Message addroute is already a route

Description Named link set was found already defined in the route.




Message xroute1 is not a route

Description Link set was not found in route set.




Message xroute2 is not a route

Description Link set was not found in route set.




Message field name unknown

Description Invalid parameter given in a change routes MML command.

Action Check MML command parameters.



Message priority too big



Message command completed

Description MML command successfully completed.


Source nmcmchan.c (I_MML_RESP, MML_CMD_OK)


Message routeset to adjacent dpc is not yet provisioned

Description Configuration problem.


Source nmcmconf.c (I_MML_RESP, MML_INV_DATA)


Message requested state already exists

Description Configuration problem.


Source nmcmconf.c (I_MML_RESP, MML_INV_DATA)


Message not enough free entry in static_sccptab_pool

Description Unable to create the concerned point code.

Action Call CAC.



Message PORTNUM already assigned to other link

Description Attempted to configure a link to a PORTNUM that is already configured to another link.






Message Linkset already has maximum links provisioned

Description Attempt to provision more than maximum links allowed (MAX_LINK_PER_LS) for a link set. See the SINAP/SS7 include file sinap.h for the current value of MAX_LINK_PER_LS for this release of the SINAP/SS7 system.




Message Same SLC had been provisioned in the linkset

Description Attempt to configure an SLC on a link set that already has the same SLC configured.




Message Other link in the linkset has same priority

Description Attempt to configure a link to a priority already defined for another link.




Message SPEED is not compatible within linkset

Description The SPEED parameter is not compatible with the SPEED parameters already configured for other links.



Message PORTNUM already assigned to other link




Message data in linkset table incompatible

Description Link set parameters are incompatible with parameters configured for other link sets.




Message Discrimination table has not been provisioned

Description Attempt to use a discrimination table that has not been provisioned.




Message ADPC already assigned to other link set

Description Attempt to assign a ADPC to a link set when the ADPC is already assigned to another link set.




Message Static link set table overflow

Description No available entries in the static load link set table. Maximum number of link sets have been configured.

Action Check the SINAP/SS7 system configuration. If the problem persists, call the CAC.


Message SPEED is not compatible within linkset




Message Discrimination Table already provisioned

Description CREATE-OSP was attempted on a SINAP/SS7 node that was already defined.

Action Select DISPLAY-OSP to confirm that the OSP already exists.

Source nmcmcrea.c


Message static_sccptab_pool overflow

Description Unable to add a remote SSN. No available entries in the static load SCCP table. Maximum number of remote SSNs have been configured.

Action Check the SINAP/SS7 system configuration. Call the CAC.



Message DPC had been associated with other routeset

Description Attempt to assign a DPC to a route set for a DPC that is already assigned to another route set.




Message route (linkset) does not have link provisioned

Description No link is provisioned for the route.



Message Static link set table overflow




Message routeset table overflow

Description No available entries in the static load route set table. Maximum number of route sets have been configured.

Action Check the SINAP/SS7 system configuration. Call the CAC.



Message no cpc provisioned for the lssn

Description There is no concerned point code provisioned for the local SSN.




Message ducpc still exists, command not allowed

Description Attempt to delete a concerned point code when the duplicate concerned point code still exists. Command not allowed.




Message ducpc does not exist

Description The duplicate concerned point code does not exist.




Message route (linkset) does not have link provisioned



Message ducpc is already provisioned

Description Attempt to add a concerned point code when the duplicate concerned point code already exists. Command not allowed.




Message link is active, cannot be deleted

Description Attempt to delete a link that is still configured to be active.




Message the linkset of this link is a route

Description Attempt to delete the last link in the link set and the link set is a route of a route set. Command not allowed.




Message linkset static state is ACTIVE

Description Attempt to delete a link that is still active.






Message the linkset is still a route of a routeset

Description Attempt to delete a last link set that is the last route of a route set. Command not allowed.




Message link(s) still provisioned to this linkset

Description Attempt to delete a link set that still has links provisioned in the link set.




Message network element still provisioned to this node

Description Attempt to delete an OSP network where there are still other elements configured to the OSP (for example, route set, link sets).




Message remote pc is not provisioned

Description Attempt to delete a remote SSN that is not provisioned.






Message routeset static state is ACTIVE

Description Attempt to delete a route set that is still configured active.




Message pc is still a concerned pc to certain lssn

Description Attempt to delete a route set and the point code is a concerned point code of another local SSN.




Message the remssn for this pc still exists

Description Attempt to delete a route set and the remote SSN for the point code still exists.




Message direct linkset still active

Description Attempt to delete a route set and the link set is still configured to be active.






Message SSN not provisioned

Description Configuration display text that indicates SSN not provisioned for the concerned point code.


Source nmcmdisp.c (I_MML_RESP, MML_CMD_OK)


Message RSET not provisioned

Description Configuration display text that indicates a route set is not provisioned for the remote SSN.




Message LINK not provisioned

Description Configuration display text that indicates no link is provisioned.




Message cannot obtain L3MT key

Description Cannot get the IPC key for L3MT.

Action Verify that the l3mt is still running by using the ps command. If it is not, restart the SINAP/SS7 system.

Source nmcmdisp.c (I_MML_RESP, MML_CMD_ERR)




Message cannot obtain display info. from L3MT

Description No reply from L3MT (no IPC returned).

Action Verify that the l3mt is still running by using the ps command. If it is not, restart the SINAP/SS7 system.

Source nmcmdisp.c (I_MML_RESP, MML_CMD_ERR)


Message LINK SET not provisioned

Description Configuration display text that indicates no link set is provisioned.




Message ROUTE SET not provisioned

Description Configuration display text that indicates no route set is provisioned.




Message unknown system table

Description Attempt to display a system table but the system table name and number are out of range.

Action Check MML command parameters.

Source nmcmdisp.c (I_MML_RESP, MML_INV_DATA)




Message Conflict in instance numbers - cannot setup Load Control

Description Attempt to configure load control for an instance that is already configured for load control.

Action Check SINAP/SS7 load control configuration.

Source nmcmloco.c (I_MML_RESP, EBUSY)


Message Driver cannot allocate memory for Load Control

Description Call the CAC.


Source nmcmloco.c (I_MML_RESP, ENOMEM)


Message Critical error: Driver Load Control inconsistency

Description Call the CAC.


Source nmcmloco.c (I_MML_RESP, EDOM)


Message Setup abate delay not in range

Description Attempt to configure invalid load control abate delay parameter.

Action Check load control abate delay value.

Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_BAD_ABDELAY)




Message Setup count not in range

Description Attempt to configure invalid load control count parameter.

Action Check load control count value.

Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_BAD_COUNT)


Message Setup delay not in range

Description Attempt to configure invalid load control delay parameter.

Action Check load control delay value.

Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_BAD_DELAY)


Message Specified instance number not in range

Description Attempt to configure invalid load control instance parameter.

Action Check load control instance number value.

Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_BAD_INST)


Message Setup notify parameter invalid

Description Attempt to configure invalid load control notify parameter.

Action Check load control notify value.

Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_BAD_NOTIFY)


Message Specified subsystem not in range

Description Attempt to configure load control for a subsystem that is out of range.

Action Check load control subsystem value.

Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_BAD_SSN)




Message Setup threshold not in range

Description Attempt to configure load control threshold that is out of range.

Action Check load control threshold value.

Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_BAD_THRESH)


Message Setup type not group, individual, or delete

Description Incompatible load control arguments specified.


Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_BAD_TYPE)


Message Setup type individual but distribution LEAST_UTILIZED

Description Incompatible load control arguments specified.


Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_DIST_WRONG)


Message Specified instance is disabled

Description Specified instance is disabled.


Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_INST_DISABLE)




Message Specified instance is not running

Description Instance is not running.

Action Check that application is running.

Source nmcmloco.c (I_MML_RESP,)


Message Forced Load Control not in effect for instance

Description Forced load control not presently in use.


Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_INST_NOT_FORCE)


Message This subsystem is not currently running

Description The subsystem is not currently running.


Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_NOTRUN)


Message Load Control not enabled

Description Load control not enabled.


Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_NOT_ENABLE)


Message Forced Load Control not in effect for subsystem

Description Forced load control not presently in use.

Action Check SINAP/SS7 status of load control.

Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_NOT_FORCE)




Message Instance specified when not individual Load Control

Description Specified an instance for load control that is configured for a group.


Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_NOT_INDIV)


Message Load Control not setup for this subsystem

Description Load control not configured.


Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_NOT_SETUP)


Message Load Control cannot be setup, this subsystem not TCAP

Description Load control can only be utilized with TCAP.


Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_NOT_TCAP)


Message Threshold value is greater than input queue length

Description Load control threshold value larger than max_msu_input_que depth specified in ca_register().

Action Check SINAP/SS7 load control configuration and ca_register() parameters in application.

Source nmcmloco.c (I_MML_RESP, CA_ERR_LC_THRESHOLD)




Message Driver Load Control error, errno = %d

Description Unknown error returned from driver in response to load control MML command.

Action Call the CAC.

Source nmcmloco.c (I_MML_RESP, MML_INV_DATA)


Message input command is not recognized by the system

Description Invalid MML command detected in parse routine.

Action Check MML command and command parameters.

Source nmcmmain.c (I_MML_RESP, MML_INV_CC)


Message error field field_name - field_description where field_name and field_description can be any MML command field name and description

Description MML parameter error detected.

Action Check MML command and command parameters.

Source nmcmmain.c (I_MML_RESP, MML_INV_DATA)


Message cannot open file to send report

Description Unable to open temporary file for MML command reply data for display in response to user command.

Action Check the directory and file permissions of the current directory file for read and write permission.

Source nmcmclib.c (I_MML_RESP, MML_FILE_ERR)




Message cannot write file to send report

Description Unable to write temp file for MML command reply data for display in response to user command.


Source nmcmdisp.c (I_MML_RESP, MML_FILE_ERR)


Message cannot close report file

Description Unable to close temp file for MML command reply data for display.


Source nmcmdisp.c (I_MML_RESP, MML_FILE_ERR)


Message MTP30 measurement not available

Description Could not retrieve the 30-minute MTP measurement statistics.

Action Check the directory and file permissions of the measurements file for read and write permission.

Source nmcmmeas.c (I_MML_RESP, MML_INV_DATA)


Message MTP30 record read error



Source nmcmmeas.c (I_MML_RESP, MML_FILE_ERR)




Message cannot write MTP30 report

Description Could not write 30-minute MTP measurement statistics report to a file.


Source nmcmcrea.c (I_MML_RESP, MML_FILE_ERR)


Message MTP5 measurement not available

Description MTP measurement statistics is not available for the time specified.

Action Retry when the measurements become available.



Message MTP5 record read error





Message cannot write MTP5 report

Description Could not write 5-minute MTP measurement statistics report to a file.






Message SCCP measurement not available

Description Could not retrieve the SCCP measurement statistics.




Message SCCP record read error

Description Could not retrieve the SCCP measurement statistics.




Message cannot write SCCP report

Description Could not write SCCP measurement statistics report to a file.




Message TCAP measurement not available

Description Could not retrieve the TCAP measurement statistics.






Message TCAP record read error

Description Could not retrieve the TCAP measurement statistics.




Message cannot write TCAP report

Description Could not write TCAP measurement statistics report to a file.




Message cannot read 30 minute file header

Description Could not retrieve the 30-minute measurement statistics.




Message cannot read 5 minute file header







Message cannot read 30 MIN file header





Message no data to retrieve

Description No measurements data collected to be retrieved.




Message file header error

Description Could not retrieve the measurement statistics.




Message record unavailable or retrieved







Message 5 minute file header read error





Message no record to retrieve





Message cannot open measurement file

Description Could not open the measurement statistics file.




Message cannot regenerate purgeday ascii file\n

Description Unable to regenerate purgeday ASCII file.


Source nmcmmisc.c (I_MML_RESP, MML_INV_DATA)




Message File name too large

Description Unable to delete named file because filename size is greater than MAX_FILENAME. See the SINAP/SS7 include file sinap.h for the current value for MAX_FILENAME for this release of the SINAP/SS7 system.

Action Check the filename and correct the name to a size smaller than MAX_FILENAME.



Message Err in getting TM key

Description Unable to get the Trouble Management IPC key.

Action Verify that the nmtm is still running by using the ps command. If the problem persists, restart the SINAP/SS7 system.

Source nmcmmisc.c (I_MML_RESP, MML_CMD_ERR)


Message Err in waiting for I_TM_UPDATE_ACK

Description A UNIX or CASL error was returned at ca_get_msg() for trouble management IPC I_TM_UPDATE_ACK used to tell nmtm to update the treatment table.




Comment errno !== ENOMSG || errno !== EINTR



Message No response from the TM

Description No reply to IPC for nmtm to update treatment tables.




Message Err in sending IPC msg to TM

Description Error in sending IPC for nmtm to update treatment tables.




Message Err in getting DS key

Description Unable to get the disk server IPC key.

Action Verify that the nmds is still running by using the ps command. If the problem persists, restart the SINAP/SS7 system.



Message Err in sending msg to DS

Description Error in sending a message to Disk Server.






Message No response from DS

Description No reply to a message sent to the Disk Server.




Message Error from DS process and Error from DS

Description Error in sending a message to Disk Server.




Message Err in opening alarm log file

Description Unable to open the alarm log for the requested date.

Action Check the directory and file permissions of the alarm log file for read and write permission. Check that the alarm log file exists for the requested date.



Message Err in reading alarm file

Description Unable to read the alarm log for the requested date.

Action Check the directory and file permissions of the alarm log file for read and write permission.

Source nmcmmisc.c (I_MML_RESP, MML_FILE_ERR)




Message Data buffer invalid len=%d

Description Alarm log record read is larger than the maximum size allowed for an IPC message block (MAX_IBLK_DATA_SZ). Data in the alarm log file is invalid. See the SINAP/SS7 include file iblock.h for the value of MAX_IBLK_DATA_SZ for this release of the SINAP/SS7 system.

Action Check that the correct file is being used. Check the contents of the file for correct data.



Message Data buffer != sizeof(event_t),errno=size

Description Alarm log record read is larger than the maximum size allowed for an IPC I_EVENT message block. Data in the alarm log file is invalid.




Message Unknown iblk msg type=(%d)

Description Alarm log record read is was not an IPC I_EVENT message block. Data in the alarm log file is invalid.






Message Err in opening note book

Description Unable to open the note book file for the requested date.

Action Check the directory and file permissions of the note book file for read and write permission. Check that the note book log file exists for the requested date.



Message Err in note book alarm file

Description Unable to read the note book file for the requested date.

Action Check the directory and file permissions of the note book file for read and write permission.



Message Err in opening report file

Description Unable to open temporary file for MML command reply data for display in response to user command.

Action Check the directory and file permissions of the application files for read and write permission.

Source nmcmnbkp.c (I_MML_RESP, MML_CMD_ERR)


Message can't open file to send report

Description Unable to open the report file.

Action Check the directory and file permissions of the report file for read and write permission. Check that the report log file exists for the requested date.





Message Err in writing to report file

Description Unable to write the report book file.

Action Check the directory and file permissions of the note book file for read and write permission.



Message Err in putting event

Description Unable to send the notification to nmcm for backup node operation.

Action If problem persists, call the CAC.



Message rclog not allowed if restoring from SECONDARY

Description Can not restore when using secondary rclog.




Message Err in opening rclog file

Description Unable to open the rclog file.

Action Check the directory and file permissions of the rclog file for read and write permission.





Message *** err in getting MTP mgmt ipc key

Description Unable to get L3MP IPC key.

Action Verify that the l3mp is still running by using the ps command. If the problem persists, restart the SINAP/SS7 system.



Message could not send MTP restart to MTP mgmt

Description ca_put_msg() failed on IPC message to l3mp.

Action Verify that the l3mp is still running by using the ps command. If the problem persists, restart the SINAP/SS7 system.



Message err in getting SCCP mgmt ipc key

Description Unable to get SCMG IPC key.

Action Verify that the scmg is still running by using the ps command. If the problem persists, restart the SINAP/SS7 system.



Message could not send SCCP restart to SCCP mgmt

Description ca_put_msg() failed on IPC message to scmg.

Action Verify that the scmg is still running by using the ps command. If the problem persists, restart the SINAP/SS7 system.





Message Err in copying files

Description Error backing up application files.

Action Check the directory and file permissions of the application files for read and write permission.



Message NM,MC exited

Description NM,MC normally terminated.

Action This message is informational and requires no action.

Source nmmcmain.c, nmmcsubs.c


Message NM,MC exited due to signal %d

Description Indicated signal terminated NM,MC.

Action Determine why process received signal. See signal.h or SINAP/SS7 s7signal.h for the text description of the signal reported.



Message Cannot send I_MTP_MEAS_REQ to MTP mgmt

Description A process can not send I_MTP_MEAS_REQ.

Action Ensure that the L3MP is still running by using the ps command.





Message Cannot find MTP management

Description A process can not find MTP management.




Message MTP delayed response to I_MTP_MEAS_REQ

Description MTP measurements response was delayed.

Action Determine whether the L3MP is in heavy traffic. To do so, you can check MTP measurements, or CPU time for L3 processes.



Message L3RC delayed response to I_MTP_MEAS_REQ

Description MTP measurements response was not issued.




Message MTP not responding to I_MTP_MEAS_REQ







Message L3RC not responding to I_MTP_MEAS_REQ





Message I_MON_DATA received in non-monitor mode

Description The SINAP/SS7 system received monitor data in non monitor mode.

Action If you receive this message only once, you can ignore it. The monitor function was probably terminated before the last monitor message was received. However, if you receive this message more than once, contact the CAC.

Source nmthmain.c, nmthsubs.c


Message FILE=%s, LINE=%u, ERR: %s, errno=%d (%s)\n

Description Fatal error reported from source file at line number.Error message that can be expected:

nmthmain.c:"getenv(\"SINAP_NODE\") returns NULL"nmthmain.c:"getenv(\"SINAP_MODULE\") returns NULL"nmthmain.c:"nmth_register()"nmthmain.c:"shmget()","shmat()","fork()","execlp()"

Action Please check if the SINAP/SS7 system is running or needs to be started! Error with SINAP_NODE or SINAP_MODULE indicates a problem with the SINAP/SS7 user profiles.

Source nmthmain.c



Load Control UNIX Error Messages

Load Control UNIX Error MessagesThis section contains the error messages for UNIX load control.

Message Not enough space

Description More memory is needed to execute the load control function.

Action Kill unneeded processes and retry.

Source /sys/errno.h

Event UNIX_EVENT / ENOMEM

Message Mount device busy

Description The application instances configured for load control are inconsistent with those registered with the SINAP/SS7 system.

Action Check load control configuration and SINAP/SS7 application registration database.

Source /sys/errno.h

Event UNIX_EVENT / EBUSY

Message Math arg out of domain of func

Description The load control driver has encountered a critical error.


Source /sys/errno.h

Event UNIX_EVENT / EDOM


Index

IndexIndex-

#APPL command, C-23#BI,MD command, C-23#DIST,x command, C-23#IRT command, C-24#KEY command, C-24#L3,CLS, C-24#L3,LST, 3-105#lc command, C-24#LCD command, C-24#ORT,CLS command, C-25#ORT,LS command, C-26#sc command, C-26#STA,pgtt, 3-66#UCOMM command, C-28$SINAP_HOME/bin, 2-14$SINAP_HOME/Bin/shm/pri, 2-31$SINAP_HOME/Bin/sinap_env, 2-2,

3-43, 4-58, 4-59, B-1$SINAP_HOME/Bin/sinap_envr, 3-10,

3-54, 3-57, 3-58, 3-72, 3-75, 3-89, 3-98, 3-99, 3-107, 3-108, 3-114, 3-115, 3-118, 3-119, 3-120, 3-122, 3-123, 4-58, H-7, H-9

$SINAP_HOME/Logs/system, 2-22$SINAP_HOME/man/man1, 2-24/etc/config_sinap, B-1/etc/inittab, 2-2, 2-11

editing to stop SINAP/MultiStack, 2-38/etc/SS7links, 3-40, 3-41/home/sinap, 2-261996 ITU-T, 3-1198-bit SLS processing, 3-109, C-25, C-26

Aabatement table

definition, 3-95displaying settings, 3-93

abnormal messages, 5-8access link (A-link), 3-35accessing SLT and SRT timers, 4-101, 4-102activating

link sets, 3-70, 3-72

links, 3-68, 3-70load control, 3-79, 3-80, 4-106, 4-109, 4-111network components, 3-67route sets, 3-72, 3-74

activating the NTT version of ISUP services, G-9

active processes, listing, 2-26, 2-27, 6-2adding

CPC for an LSSN, 4-37, 4-38events, 5-16links, dynamically, 4-47remote SSN, 4-39

adjacent node, 3-103Adjunct Processor (AP), 1-1Advanced Intelligent Network (AIN), 1-1Alarms

event categories that generate, I-2severity level, I-1

CRITICAL, I-1MAJOR, I-1MINOR, I-1NOTICE, I-1

alarmsBI_EVENT category, I-11checking errno values to determine

subsystem reporting, 5-3components, 5-1–5-2default file, 5-2default messages, 5-9–5-10definition, 5-1–5-2History Log, 5-3–5-5Log Files, 3-122MTP formats, 5-8notification, 5-2severity level, 5-9

defining, 3-123, 3-124user-supplied, 5-17

A-link, 3-35alternate SCCP routing, 3-63, 4-28, 4-43, 4-46,

4-56American National Standards Institute

(ANSI), xxixANSI, 2-25

Index 1

Index

ANSI Configuration Parameters, E-1ANSI network variant, xxx

Change Commands menu, 4-32combined link sets, E-8, E-9configuration requirements and limitations

table, 3-1Delete Commands menu, 4-48Display Commands menu, 4-2dynamic route provisioning, E-4, E-5FOPCs, E-9handling SNM messages, 3-113implementing the TCCO feature, 3-106,

E-10, E-11ISUP services, 3-113load control, 3-88MTP link congestion thresholds, E-7MTP restart process, 3-96, 3-105

features specific to ANSI, 3-99MTP timer settings, E-5, E-7network, cluster, and member

routing, 2-32, E-2, E-3Point Code Format, E-2remote SSNs, E-3, E-4route sets, E-4SCCP timer settings, E-8time-controlled diversion, 3-108, E-11UPU messages, 3-115

ANSI Point Code Formats, E-2ANSI_SINAP_FOPC, 3-52, 4-17, 4-53, E-9Application Commands menu, 2-18, 3-82, 4-3applications

backing up, 4-83checking status, 6-12deleting file from disk, 4-91registration limitations, 3-3restoring from disk or tape, 4-86, 4-87

archive library, E-12ARTIC synchronous link, 3-40

Bbacking up

application’s source file, 4-83node static database, 4-82

Backup Application command, 4-83, C-2

backup cyclechanging interval, 4-90, 4-91changing the number of days, 4-84displaying interval, 4-88, 4-89displaying number of days, 4-83, 4-84

Backup Node command, 4-82, C-2BACKUP-APPL command, 4-83, C-2BACKUP-NODE command, 3-67, 4-82, C-2basic SINAP/MultiStack environment

variables, B-2BI_EVENT, I-2, I-11BI_EVENT category alarms, I-11bidb command, C-22bila command, 6-17, C-22bin/startappl, 2-10, 2-12BITE monitor, C-12bitu process, 4-98

running in real-time or time-share mode, 4-98

BK_EVENT, I-41blocking route sets, 4-57board assignments, verifying, 6-1Built-In Test (BITE) Subsystem

Commands menu, 2-18, 4-93defaults, 6-15limitations, 6-14Link Test User Part process, running in

real-time or time-share mode, 4-98

Log Analysis program, 6-16commands, C-22–C-23DISPLAY command, 6-21exiting, 6-31FIND command, 6-28limitations, 6-16operators and keywords for

commands, 6-18–6-20QUIT command, 6-31SELECT command, 6-28–6-29starting, 6-16–6-17SUMMARY command, 6-29–6-30using commands, 6-18–6-20

log file, 6-16counting records, 6-29–6-30default size and location, 6-16displaying, 6-21

2 SINAP/SS7 User’s Guide R8051-17

Index

extracting records that meet all criteria, 6-28

extracting records that meet any criteria, 6-28–6-29

sample displays, 6-22–6-27saving, 6-21

monitor, 6-16–6-17displaying current and active, 4-96starting, 4-93, 4-96stopping, 4-97, 4-98

Monitor Commands menu, 4-93process labels, 2-26reconfiguring the operation mode of

processes, 4-98services, 6-14stopping a monitor process, 4-97, 4-98testing signaling links, 4-99

Built-In Test Environment (BITE), 2-12BYPASS_SINAP_GLOBAL_TITLE_TRANS

LATION, 3-54

CCA_EVENT, I-2, I-34ca_put_msg_def, I-39ca_put_msg_def(), I-8ca_put_msu(), I-12ca_register(), 3-84, 3-87CAC, xxxivcalled party address, 3-54CBA, 3-100CBA timer, I-21CBD, 3-100CCITT, 2-25CCITT network variant, xxx

alternate SCCP routing, 3-56, 3-58Change Commands menu, 4-32configuration requirements and limitations

table, 3-1connection-oriented services, 3-111, 3-113,

4-121Delete Command menu, 4-48differences compared to NTT, G-10differences compared to TTC, F-5, F-6differences compared toNTT, G-11Display Commands menu, 4-2

environment variables for link congestion, 3-89, 3-92

handling SNM messages, 3-113implementing the TCCO feature, 3-106,

D-8, E-11ISUP services, 3-113link congestion thresholds, 3-96load control, 3-88MTP link congestion thresholds, D-3MTP restart process, 3-96, 3-105, D-6, D-8

features specific to CCITT, 3-98, 3-99MTP timer settings, D-2, D-3point code format, D-2SCCP timer settings, D-4, D-6UPU messages, 3-115XUDT and XUDTS messages, 3-116,

3-120CCITT Point Code Formats, D-2Change a Link command, C-3Change Backup Day command, 4-84, C-2Change Backup or Purge Day command, 4-84,

4-90, 4-91Change Combined Link Set command, C-2Change Commands menu, 4-32, 4-33Change Concerned Point Code command, 4-37,

4-38, C-2compared to DELETE-CPC

command, 4-52Change Duplicate Concerned Point Code

command, 4-38, 4-39, C-3Change Global Title command, 4-42, 4-46, 4-47,

C-3Change Link command, 4-33, 4-34Change Link Set command, 4-34, 4-35, C-3Change Purge Day command, 4-90, 4-91, C-4Change Remote SSN command, 4-39, C-4Change Route Set command, 4-35, 4-37, C-4Change SLS Type command, C-5Change System Table command. See

CHANGE-SYSTAB commandCHANGE-BKUPDAY command, 4-84, C-2CHANGE-CLSET command, C-2CHANGE-CPC command, 4-37, 4-38, C-2

compared to DELETE-CPC command, 4-52

Index 3

Index

CHANGE-DUCPC, F-6CHANGE-DUCPC command, 4-38, 4-39, C-3CHANGE-GTT, 4-43CHANGE-GTT command, 4-42, 4-46, 4-47, C-3CHANGE-LINK command, 4-33, 4-34, C-3CHANGE-LSET command, 4-34, 4-35, C-3Changeover and Changeback (CHM)

message, 3-99, H-8CHANGE-PURGEDAY command, 4-90, 4-91,

C-4CHANGE-REMSSN command, 4-39, C-4CHANGE-RSET command, 4-35, 4-37, C-4CHANGE-SLSTYPE, 3-109CHANGE-SLSTYPE command, 4-47, C-5, C-25CHANGE-SYSTAB, 3-100CHANGE-SYSTAB command, 3-89, 4-40, 4-42,

C-4accessing MTP L3 timers with, 3-103using to access an SCCP

connection-oriented timer, 4-127using to change SLT/SRT timer

settings, 4-102, 4-103changing

concerned point code, 4-37, 4-38content of route sets, 4-35, 4-37emergency mode flag setting for link

sets, 4-34, 4-35event treatment, 5-16links, 4-33, 4-34number of days in node database backup

cycle, 4-84remote SSN, 4-39SLT and SRT timers, 4-102, 4-103value of a global title, 4-42, 4-46, 4-47values of timers and thresholds, 4-40, 4-42

checkingaccessibility of a remote SSN, 6-10application status, 6-12availability of a local SSN, 6-11–6-12link set status, 6-7–6-8link status, 6-3–6-4LRN and LRM, 4-122, 4-123route set status, 6-8–6-9

child death signal, 2-14China, 2-25

China network variant, xxxiChange Commands menu, 4-32configuration requirements and limitations

table, 3-1connection-oriented services, 3-111, 3-113,

4-121Delete Commands menu, 4-48Display Commands menu, 4-2environment variables for link

congestion, 3-89, 3-92handling SNM messages, 3-113implementing the TCCO feature, 3-106,

E-11load control, 3-88MTP restart process, 3-96, 3-105

features specific to China, 3-98, 3-99network, cluster, and member

routing, 2-32point code format, H-2UPU messages, 3-115XUDT and XUDTS messages, 3-116,

3-118China Point Code Format, H-2client applications

-supplied alarms and events, 5-17closelog(), 5-9cluster routing, E-3cn, 2-37combined link set, 3-37Combined Link Set (CLS), 3-42combined link sets

creating, 3-37, 3-38deleting, 4-50displaying configuration information, 4-8,

4-9general information, E-8, E-9

Combined Link Sets (CLS), H-9Command Management process (nmcm), 2-21Commands

BACKUP-NODE, 3-67CHANGE-SLSTYPE, 4-47CHANGE-SYSTAB, 3-89, 3-100CONFIGURE, 3-71Configure Link, 3-27Configure Linkset, 3-27


Index

Configure Routeset, 3-27CONFIGURE-LSET, 3-28, 3-72CONGESTION_INITIAL_VALUE, 3-92CREATE-CLSET, 3-38CREATE-CPC, 3-47, 3-48CREATE-DUCPC, 3-48, 3-49, 3-50CREATE-FOPC, 3-53CREATE-GTT, 3-54, 3-56, 3-57, 3-58,

3-59, 3-62, 3-64, 3-65CREATE-LINK, 3-39, 3-41, 3-68, 3-70CREATE-LSET, 3-34, 3-35, 3-36, 3-37,

3-70, 3-71, 3-72CREATE-OSP, 3-31, 3-32, 3-33CREATE-REMSSN, 3-50, 3-51CREATE-RSET, 3-42, 3-43, 3-45DISABLE-LOAD-CONTROL, 3-79, 3-81DISPLAY-CPC, 3-48DISPLAY-LINK, 3-17DISPLAY-LOAD-CONTROL, 3-79DISPLAY-LSET, 3-17DISPLAY-RSET, 3-17, 4-11DISPLAY-SYSTAB, 3-17, 3-89ENABLE-LOAD-CONTROL, 3-79, 3-81,

3-86EXIT-LOAD-CONTROL, 3-79, 3-80INVOKE-LOAD-CONTROL, 3-79, 3-80SETUP-LOAD-CONTROL, 3-78, 3-79,

3-81, 3-82, 3-85, 3-86, 3-87comment (#) menu operator, 3-17Communication Management key, I-4CONAB (congestion abatement), 3-95CONAB1, H-5CONAN1, H-5Concerned Point Code (CPC), 3-46, C-2, C-8,

C-11, C-26concerned point code (CPC)

adding/deleting from an SSN, 4-37, 4-38changing duplicate, 4-38, 4-39creating, 3-46, 3-48creating duplicate, 3-48, 3-50deleting all from an SSN, 4-52deleting duplicate, 4-52displaying and printing information, 4-15,

4-17viewing the number associated with an

LSSN, 6-10concerned point codes

configuration limitations, 3-3Concerned Point Codes (CPC), C-28CONDIS (congestion discard), 3-95configuration

re-creating existing, 2-30, 2-32requirements and limitations table, 3-1

CONFIGURE command, 3-71Configure Commands men, 3-67Configure Commands menu, 3-42, 3-68Configure Link command, 3-68, 3-70, C-5

using to remove a link from service, 4-57using when deleting links

dynamically, 4-49Configure Link command, 3-27Configure Link Set command, 3-70, 3-72, C-5

using when deleting links dynamically, 4-49

Configure Linkset command, 3-27Configure Route Set command, 3-72, 3-74, C-5

using to take a route set out of service, 4-57Configure Routeset command, 3-27CONFIGURE-LINK command, 3-68, 3-70, C-5


dynamically, 4-49CONFIGURE-LINK screen, 3-68CONFIGURE-LSET command, 3-28, 3-70,

3-72, C-5using when deleting links

dynamically, 4-49CONFIGURE-RSET, 3-74CONFIGURE-RSET command, 3-72, 3-74, C-5

using to take a route set out of service, 4-57configuring

link sets, 3-70, 3-72links, 3-68, 3-70load control, 3-82, 3-88network components, 3-67route sets, 3-72, 3-74the Terminal Handler, 3-10

CONG_EVENT_REPORT_OFF, 3-95CONG_STATUS_CHANGE_LOGGING, 3-9

5

Index 5

Index

congestion abatement (CONAB), 3-95congestion discard (CONDIS), 3-95Congestion level thresholds, H-5Congestion Notification Options, 3-95congestion onset (CONON), 3-95congestion tables, 3-95

displaying and changing settings, 3-89displaying settings, 3-93

CONGESTION_INITIAL_VALUE, 3-92CONGESTION_INITIAL_VALUE

command, 3-92CONGESTION_TY_TIMER timer, 3-92connection, 3-111, 4-121

releasing frozen LRNs to create a new, 4-124, 4-126

connection-establishment stage, 3-112connection-oriented feature, 3-111Connection-Oriented Features (COF), H-7connection-oriented services, 3-111, 3-113,

4-121releasing frozen LRNs, 4-124, 4-126timers, 4-126, 4-128

connection-oriented timers, 4-126, 4-128connection-release stage, 3-112CONON (congestion onset), 3-95Consultative Committee on International

Telegraphy and Telephony (CCITT), xxix

continuation messages, 3-76CPC. See concerned point codesCreate a Global Title Translation

command, C-6Create Combined Link Set command, 3-37,

3-38, C-5Create Commands menu, 3-27, 3-28, 3-29, 3-30,

3-31, 3-33, 3-38, 3-46, 3-48, 3-51, 3-53, 3-64

Create Concerned Point Code command, 3-46, 3-48, C-6

Create Duplicate Concerned Point Code command, 3-48, 3-50, C-6

Create Fictitious Originating Point Code command, 3-51, 3-53, C-6, E-9

creating FOPC to use in place of calling party’s OPC, E-9

Create Link command, 3-39, 3-42, C-7Create Link Set command, 3-34, 3-37, C-7Create Own Signaling Point Code

command, 3-31, 3-34, C-7Create Remote Subsystem command, 3-50,

3-51, C-8Create Route Set command, 3-42, 3-46, C-8

defining to use network, cluster, or member routing, E-4

CREATE_RSET, 2-32CREATE-CLSET command, 3-37, 3-38, C-5CREATE-CLSET screen, 3-37CREATE-CPC command, 3-46, 3-47, 3-48, C-6CREATE-CPC screen, 3-46CREATE-DUCPC, F-6CREATE-DUCPC command, 3-48, 3-49, 3-50,

C-6CREATE-DUCPC screen, 3-48CREATE-FOPC, 4-17CREATE-FOPC command, 3-51, 3-53, C-6, E-9

creating FOPC to use in place of calling party’s OPC, E-9

CREATE-FOPC screen, 3-52CREATE-GTT command, 3-53, 3-54, 3-56, 3-57,

3-58, 3-59, 3-62, 3-64, 3-65, 4-26, 4-55, C-6, C-7

address components, 3-54, 3-56creating, 3-58, 3-64man page format, 3-65MML command format, 3-64

CREATE-GTT screen, 3-58CREATE-LINK command, 3-39, 3-41, 3-42,

3-68, 3-70, C-7CREATE-LINK screen, 3-39CREATE-LSET command, 3-34, 3-35, 3-36,

3-37, 3-70, 3-71, 3-72, C-7CREATE-LSET screen, 3-34, 3-70CREATE-OSP command, 3-31, 3-32, 3-33, 3-34,

C-7CREATE-OSP screen, 3-31CREATE-REMSSN, 3-75CREATE-REMSSN command, 3-50, 3-51, C-8CREATE-REMSSN screen, 3-50CREATE-RSET comand, 3-45CREATE-RSET command, 3-42, 3-43, 3-45,


Index

3-46, C-8defining to use network, cluster, or

member routing, E-4CREATE-RSET screen, 3-43creating

combined link sets, 3-37, 3-38concerned point code, 3-46, 3-48duplicate concerned point code, 3-48, 3-50fictitious originating point code, 3-51, 3-53global title translation, 3-53, 3-58, 4-26, 4-55

address components, 3-54, 3-56MML command and man page

format, 3-64steps, 3-58, 3-64

link sets, 3-34, 3-37links, 3-39, 3-42network components, 3-26, 3-27

sample configuration, 3-27, 3-28network components with a script

file, 2-30own signaling point code, 3-31, 3-34remote subsystem number (SSN), 3-50,

3-51route sets, 3-42, 3-46trouble treatment table, 5-10

Creating a combined link set, 3-37Creating an FOPC, 3-52creating route sets, 3-42

Ddata acknowledgment message, 6-27database

backup, 4-82restoring configuration, 4-87

data-transfer stage, 3-112deactivating

link sets, 4-57load control, 4-119, 4-121

decimal notation, 2-19, 2-21default

alarm file, 5-2alarm messages, 5-9–5-10BITE log file size and location, 6-16

definingenvironment variables, B-1

menu options in the Menu Definition File, 3-11

Delete Combined Link Set command, 4-50, C-8Delete Commands menu, 4-47, 4-49Delete Concerned Point Code command, 4-52,

C-8compared to CHANGE-CPC

command, 4-52Delete Duplicate Concerned Point Code

command, 4-52, C-8Delete Fictitious Originating Point Code

(DELETE-FOPC) command, 4-53Delete Fictitious Originating Point Code

command, 4-53, C-9, E-9Delete File command, 4-91, C-8Delete Global Title Translation

command, 4-54, 4-57, C-9Delete Link command, 4-50, C-9


dynamically, 4-49Delete Link Set command, 4-50, C-9Delete Own Signaling Point Code

command, 4-51, C-10Delete Remote Subsystem command, 4-54,

C-10Delete Route Set command, 4-51, C-10DELETE-CLSET command, 4-50, C-8DELETE-CPC command, 4-52, C-8

compared to CHANGE-CPC command, 4-52

DELETE-DUCPC, F-6DELETE-DUCPC command, 4-52, C-8DELETE-FILE command, 4-91, C-8DELETE-FOPC command, 4-53, C-9, E-9DELETE-GTT command, 4-54, 4-57, C-9DELETE-LINK command, 4-50, C-9


dynamically, 4-49DELETE-LSET command, 4-50, C-9DELETE-OSP command, 4-51, C-10DELETE-REMSSN command, 4-54, C-10DELETE-RSET command, 4-51, C-10deleting

Index 7

Index

combined link sets, 4-50concerned point codes from an SSN,

all, 4-52CPC for an LSSN, 4-37, 4-38duplicate concerned point code, 4-52file from disk, 4-91FOPC, 4-53global title, 4-54, 4-57link sets, 4-50links from a link set, 4-50links, dynamically, 4-47, 4-49own signaling point code, 4-51remote SSN, 4-39remote SSNs from a node, all, 4-54route sets, 4-51

Destination Point Code (DPC), 2-32, 3-42, H-2, I-12, I-30

destination point code (DPC)definition, E-4

destination point codes. See DPCdifferences in NTT, TTC, and CCITT network

variants, G-10Disable Load Control command, 3-79, 3-80,

4-115, 4-119, C-10DISABLE_MTP_DISCRIMINATION, 3-108DISABLE-LOAD-CONTROL command, 3-79,

3-80, 3-81, 4-115, 4-119, C-10disabling

environment variables, B-2load control, 4-115, 4-119periodic link testing, 4-105printing, 2-28, 2-29

discard table, 3-95displaying settings, 3-93

DISPLAYFILE command, C-22

Display Backup Day command, 4-83, 4-84, C-10Display Combined Link Set command, 4-8, 4-9,

C-11DISPLAY command, 6-21Display Commands menu, 4-1Display Concerned Point Code command, 4-15,

4-17, C-11Display Fictitious Originating Point Code

command, 4-17, 4-18, C-11, E-9

Display Global Titles command, 4-26, 4-27, C-11

Display Link command, 4-3, 4-5, 6-3–6-4, C-11Display Link Set command, 4-7, 4-8, 6-7–6-8,

C-11Display Load Control command, 3-79, 3-80,

4-112, 4-115, C-12Display Monitor ID command, 4-96, C-12Display Own Signaling Point Code

command, 4-14, 4-15, C-12Display Process Version command, 2-27, 2-28,

C-12Display Purge Day command, 4-88, 4-89, C-12Display Remote Subsystem Number

command, 4-18, 4-19, C-12Display Route Set command, 4-10, 4-14,

6-8–6-9, C-13Display Scenario command, C-13Display Subsystem Number command, 4-30,

4-31, 6-11–6-12, C-13Display System Tables command. See

DISPLAY-SYSTAB commandDISPLAY-BKUPDAY command, 4-83, 4-84,

C-10DISPLAY-CLSET command, 4-8, 4-9, C-11DISPLAY-CPC command, 3-48, 4-15, 4-17,

C-11DISPLAY-FOPC, 4-17DISPLAY-FOPC command, 4-17, 4-18, C-11,

E-9DISPLAY-GTT command, 4-26, 4-27, C-11displaying

Alarm History Log Entries, 5-3–5-5combined link set information, 4-8, 4-9concerned point code information, 4-15,

4-17configuration information for network

components, 4-1congestion table settings, 3-93current and active BITE monitors, 4-96fictitious originating point code

information, 4-17, 4-18global titles, 4-26, 4-27link information, 4-3, 4-5link set information, 4-7, 4-8


Index

links, loopback detection, 4-3load control statistics for an

application, 4-112, 4-115load distribution type, 4-28, 4-30man pages, 2-24, 2-26number of days in the node database

backup cycle, 4-83, 4-84own signaling point code

information, 4-14, 4-15process versions, 2-27, 2-28remote SSN information, 4-18, 4-19route set information, 4-10, 4-14signaling link assignments, 4-30signaling link selection assignments, 4-28SLT and SRT timers, 4-102Software Notebook Log entries, 5-6–5-7SSNs, 4-30, 4-31

displaying man pages, 2-24DISPLAY-LINK, 3-120DISPLAY-LINK command, 3-17, 4-3, 4-5,

6-3–6-4, C-11DISPLAY-LOAD-CONTROL command, 3-79,

3-80, 4-112, 4-115, C-12DISPLAY-LSET command, 3-17, 4-7, 4-8,

6-7–6-8, C-11DISPLAY-MON command, 4-96, C-12DISPLAY-OSP command, 4-14, 4-15, C-12DISPLAY-PROCESS-VERSION

command, 2-27, 2-28, C-12DISPLAY-PURGEDAY command, 4-88, 4-89,

C-12DISPLAY-REMSSN command, 4-18, 4-19,

C-12DISPLAY-RSET command, 3-17, 4-10, 4-11,

4-14, 6-8–6-9, C-13DISPLAY-SCEN command, C-13DISPLAY-SUBSYSTEM command, 4-30,

4-31, 6-11–6-12, C-13DISPLAY-SYSTAB command, 3-17, 3-89,

4-19, C-13formats, 4-20man page format, 4-20menu selection mode, 4-19sample displays, 4-21, 4-25using to access an SCCP

connection-oriented timer, 4-127using to display SLT/SRT timer

settings, 4-102using to display XUDT timer values, 3-117

DLL, E-12DNCP Series 400 platform, configuration

limits, 3-1documentation

notation conventions, xxxirelated, xxxiiirevision information, xxixviewing, xxxiv

downloading link configuration changes in /etc/SS7links file, 4-128

DPC, 3-2, 3-54, 3-62, 3-63configuration limitations, 3-2

DR_EVENT, I-2, I-31drda_daemon, 2-9drda_daemon processes, 3-4drda_daemon.out, 2-9drda_stop_links, 2-37DUCPC, 3-49DUCPU

configuration limitations, 3-3Dump Table command, 4-81, 4-82, C-13dumping MTP routing and management tables

to the static table file, 4-81, 4-82DUMP-TABLE command, 4-81, 4-82, C-13Duplicate Concerned Point Code (DCPC), C-3Duplicate Concerned Point Code

(DUCPC), 3-48, C-8, F-6duplicate concerned point code (DUCPC)

changing for a local SSN, 4-39changing the DUCPC number, 4-38, 4-39creating, 3-48, 3-50deleting, 4-52

duplicate concerned point codesSee DUCPU

dynamic configuration, 4-47dynamic linked library, E-12dynamic route provisioning, E-4, E-5

EE-link, 3-35

Index 9

Index

emergency alignment flag, 4-34setting and resetting for link sets, 4-34, 4-35

Emergency-Changeover (ECM) message, 3-99, H-8

Enable Load Control command, 3-78, 3-79, 4-106, 4-109, C-14

ENABLE-LOAD-CONTROL command, 3-78, 3-79, 3-81, 3-86, 4-106, 4-109, C-14

enablingenvironment variables, B-1load control, 4-106, 4-109periodic link testing, 4-103, 4-105printing, 2-28, 2-29

Enabling partial global title translations, 3-65Encoding Scheme (ES), 3-55end point, 1-1enhanced message distribution

load control, 3-78, 3-83, 4-107Environment variabels

SINAP_MML_ALT_NUMERIC_CONVERSION, 2-19, 2-21

ENvironment variablesLOOPBACK_DISPLAY, 4-6

Environment VariablesTTC_WITH_NSTATE, 3-46

Environment variablesANSI_SINAP_FOPC, 3-52, 4-17, 4-53BYPASS_SINAP_GLOBAL_TITLE_TR

ANSLATION, 3-54CONGESTION_INITIAL_VALUE, 3-92GLOBAL_TITLE_SSN_NO_CHECK, 3-5

7, 4-43GTT_BYPASS_NOAI_CHECK, 3-55,

3-61, 4-45GTT_WITH_BACKUP_DPC_SSN, 3-57HEX_GLOBAL_TITLE, 3-58, 3-61, 3-62,

3-63, 4-26, 4-42, 4-45, 4-46, 4-55, 4-56

INTERNATIONAL_1_CONGESTION, 3-90

ISUP_CGBA_PER_2CGB, E-12ISUP_FEATURE=, E-12ISUP_FEATURE=CHINA, H-9ISUP_REL_NO_ADD_ACC, E-12LOOPBACK_DISPLAY, 4-3

MAX_PGTT_DIGITS, 3-65, 3-66MIN_PGTT_DIGITS, 3-65, 3-66MTP_ANSI92_RESTART, 3-99MTP_LINKSET_MEASUREMENT, 4-62,

4-64, 4-69, 4-73MTP_PARTIAL_RESTART, H-7MTP_SLS4_LOAD_SHARE, 3-43MTP_USER_FLOW_CTRL, H-7MTP_WHITE_BOOK, 4-14MTP_WHITE_BOOK_RESTART, 3-98,

H-7MTP_WHITE_BOOK_TCCO, H-9NAT_MUL_CONG_WITH_PRIO, 3-90NAT_MUL_CONG_WO_PRIO, 3-93NAT_MULT_CONG_WO_PRIO, 3-91,

3-92PARTIAL_GTT, 3-4, 3-65, 3-67REMSSN_INIT_PROHIBIT, 3-75RST_CONFIG_INIT_PROHIBIT, 3-43

, 3-75RST_CONFIG-INIT_PROHIBIT, 4-11,

4-12SINAP_ALT_MEASUREMENT_INTERV

AL, 4-58, 4-62, 4-69, 4-74SINAP_HOME, 2-2SINAP_LOG_SIZE, 5-5SINAP_MML_PRINT_RESPONSE, 2-28

, 2-29SINAP_MML_PRINT_TTYNAME, 4-59SINAP_XUDT_SEGMENT_SIZE, I-40SLTM_WITH_NAT10_FOR_G500, 4-10

1TTC_WITH_NSTATE, 3-26

environment variablesANSI_SINAP_FOPC=YES

, 3-52basic, B-2CCITT_CONGESTION_OPTION, 3-90defining, B-1DISABLE_MTP_DISCRIMINATION, 3-

108disabling, B-2enabling, B-1for defining LRNs and LRMs, 3-112GTT_WITH_BACKUP_DPC_SSN, 3-4,


Index

3-5LOOPBACK_DISPLAY, 3-7, 3-120MTP_ANSI88_RSR_RST, 3-7, 3-122MTP_ANSI92_RESTART, 3-6MTP_ANSI92_TCCO, 3-6MTP_ANSI92_TCD, 3-7, 3-108MTP_SLS4_LOAD_SHARE, 3-8MTP_WHITE_BOOK_RESTART, 3-6MTP_WHITE_BOOK_SLC, 3-6MTP_WHITE_BOOK_TCCO, 3-6MTP_WHITE_BOOK_TFR, 3-7RST_CONFIG_INIT_PROHIBIT, 3-72

, 3-75, 3-89, 3-98SINAP_LRN_FREEZE_TIMEOUT, 3-11

3SINAP_MDF, 3-10SINAP_MML, 3-10SINAP_TOTAL_LR_MEMS, 3-112SINAP_TOTAL_LR_NUMS, 3-113SINAP_USER_LR_MEMS, 3-113SINAP_XUDT_SEGMENT_SIZE, 3-118TTC_WITH_NSTATE, 3-3

errno values, 5-3error messages

checking errno values to determine subsystem reporting alarm, 5-3

relation to alarms, 5-1relation to events, 5-1user-supplied, 5-17See also alarms

/etc/SS7links filedownloading link configuration changes

in, 4-128Event categories

Backup Event (BK_EVENT), I-41BITE Event (BI_EVENT), I-2, I-11Driver Event (DR_EVENT), I-2, I-31Internal (CASL, TCAP generated) Event

(CA_EVENT), I-2, I-34MTP Management Event

(L3_EVENT), I-2, I-15Node Management Event

(NM_EVENT), I-2, I-3SCCP Management Event

(SC_EVENT), I-2, I-12

TALI Gateway Event (GW_EVENT), I-2Events

types, I-2events, 5-1

adding and changing treatment, 5-16categories generating alarms, I-2handling by trouble management, 5-10subcategories, I-2user-supplied, 5-17

executing MML commands from a login window/UNIX prompt, 2-21, 2-24

Exit Load Control command, 3-79, 3-80, 4-119, 4-121, C-14

exiting the BITE Log Analysis program, 6-31EXIT-LOAD-CONTROL command, 3-79,

3-80, 4-119, 4-121, C-14extended access link (E-link), 3-35

FFictitious Originating Point Code

(FOPC), 3-26, 3-30, 3-51, 4-53, E-1fictitious originating point code (FOPC)

configuring, E-9, E-10creating, 3-51, 3-53deleting, 4-53displaying and printing information, 4-17,

4-18environment variables

ANSI_SINAP_FOPC=YES, 3-52Fictitious Originating Point Codes (FOPC), 4-2Fictitious Own Point Code (FOPC), H-9Fields

HADDR, C-3Service Information Octet (SIO), H-8

FIFO (first-in, first-out) queue, 3-77files, deleting from a disk, 4-91FIND

FILE command, C-22FIND command, 6-28first-in, first-out (FIFO) queue, 3-77F-link, 3-35F-links, 3-45FOPC, 3-51, 3-53FOPC. See fictitious originating point code

Index 11

Index

forms, network information and planning, A-1, A-3, A-5, A-6, A-8

free-form mode in the Terminal Handler, 2-16, 3-10

freeze timer, D-5, H-6FTX system, 1-2fully associated links (F-link), 3-35Functions

ca_register(), 3-84, 3-87

GG.703

configuration limitations, 3-1Global Title (GT), 3-53global title addressing

components, 3-54, 3-56Global Title Indicator (GTI), 3-54, 3-55global title translation

alternate SCCP routingGTT_WITH_BACKUP_DPC_SSN

variable, 3-5Global Title Translation (GTT), 3-26, 3-53, H-7

RouteOnGT, 3-56RouteOnSSN, 3-56

global title translation (GTT)alternate SCCP routing, 3-63, 4-28, 4-43,

4-46, 4-56changing value, 4-42, 4-46, 4-47creating a GTT entry, 3-53, 3-58, 3-64, 4-26,

4-55deleting, 4-54, 4-57displaying, 4-26, 4-27man page format, 3-65MML command format, 3-64

Global Title Translation (GTT) table, 3-66GLOBAL_TITLE_SSN_NO_CHECK, 3-57,

4-43GTT. See global title translationGTT table, 3-54GTT_BYPASS_NOAI_CHECK, 3-55, 3-61,

4-45, 4-56GTT_WITH_BACKUP_DPC_SSN, 3-5, 3-57GW_EVENT, I-2

HHADDR, 3-56heartbeat messages

local processor outage, 3-110HEX_GLOBAL_TITLE, 3-58, 3-61, 3-62,

3-63, 4-26, 4-42, 4-45, 4-46, 4-55, 4-56hexadecimal notation, 2-19, 2-21hop counter, 3-119HP-UX, 2-18, 4-99, 5-1, 5-9, 6-1, E-12HP-UX system

error log files, 3-122log file, 5-1

I#IPC,0 command, 6-12, C-23I_N_PCSTATE_INDIC, 3-95I_TROUBLE_NOT, 5-19Importance Parameter, 3-119inactivity test message, 6-26Initializing route sets with a Prohibited

status, 3-74Input/Output Adapter (IOA), 3-40instances per application, 3-3Integrated Services Digital Network User Part

(ISUP), 3-32Integrated Services Digital Network User Part.

See ISUPInternational Telecommunications Institute

Standards Division (ITU-T), xxixInternational Telecommunications Union

(ITU), 1-2International Telegraph and Telephone

Consultative Committee (CCITT), 1-2INTERNATIONAL_1_CONGESTION, 3-90interprocess communications (IPC)

data record sample, 6-22queue, 3-94

Invoke Load Control command, 3-79, 3-80, 4-106, 4-109, 4-111, C-14

INVOKE-LOAD-CONTROL command, 3-79, 3-80, 4-106, 4-109, 4-111, C-14

invoking load control, 4-106, 4-109, 4-111IPC key, I-7, I-8IPC. See interprocess communications


Index

IPCTBL_load, 2-10ISDN User Part (ISUP), 3-99, H-8ISUP, 3-43ISUP encoding and decoding, functions, 3-113ISUP services

activating the ISUP services feature, E-12ISUP Services Support Library (ISSL), E-12ISUP services version

for NTT network variant, G-9ISUP_FEATURE=CHINA, H-9

JJapanese NTT network variant, xxxJapanese TTC network variant, xxx

KKernel tuning parameters

MAXUP, I-35MINARMEM, I-32MINASMEM, I-32NPROC, I-35STRTHRESH, I-32

keyboard shortcuts for the Terminal Handler, 2-20

kill (2) command, 2-14

L#L3,TIM command, 3-105#L3,LST command, 3-105, C-25#L3,RES command, 3-104L3_EVENT, I-2, I-15L3T20 timer ID, 3-104LADDR, 3-56last-in, first-out (LIFO) queue, 3-77libissl.a archive library, E-12LIFO (last-in, first-out) queue, 3-77link congestion, 3-88

changing congestion table settings, 3-89displaying congestion table settings, 3-89,

3-93environment variables

CONGESTION_INITIAL_VALUE, 3-92

for CCITT and China, 3-89, 3-92

INTERNATIONAL_1_CONGESTION, 3-90

NAT_MUL_CONG_WITH_PRIO, 3-90

NAT_MULT_CONG_WO_PRIO, 3-91, 3-92

levels and states, 3-88, 3-89measuring, 3-92, 3-93network variant differences, 3-88notifying application of congestion, 3-95thresholds, 3-95, 3-96

ANSI network variant, E-7CCITT network variant, D-3NTT network variant, G-4TTC network variant, F-2

link congestion thresholdsin NTT network variant, G-5

link operating speeds, 3-2link sets, 3-34

changing emergency mode flag setting, 4-34, 4-35

checking status, 6-7–6-8combined, 3-37

creating, 3-37, 3-38deleting, 4-50

configuring (activating), 3-70, 3-72creating, 3-34, 3-37deactivating, 4-57deleting, 4-50deleting a link, 4-50displaying information, 4-7, 4-8displaying information for combined, 4-8,

4-9number per set, 3-36number that can be load shared, 3-36removing from service, 4-57restricting traffic on one, 4-57

link sets, configuration limitations, 3-2links, 3-39

adding/deleting dynamically, 4-47changing, 4-33, 4-34checking status, 6-3–6-4configuring (activating), 3-68, 3-70creating, 3-39, 3-42deleting dynamically, 4-49deleting from a link set, 4-50

Index 13

Index

displaying information, 4-3, 4-5downloading configuration changes in

/etc/SS7links file, 4-128downloading configuration changes onto

the system, 4-49new, putting into service, 4-57number per link set, 3-36number that can be load shared per

set, 3-36periodic testing. See periodic link testingport number, 3-39priority, 3-40removing from service, 4-57signaling, testing with BITE, 4-99speed, 3-40testing by SINAP/MultiStack, 4-100testing for the TTC network variant, F-3,

G-6updating configuration information, 4-128

listing active processes, 2-26, 2-27, 6-2Load control, 3-76load control, 3-76, 3-78, 4-105, 4-106

Commands menu, 4-108deactivating, 4-119, 4-121disabling, 4-115, 4-119displaying statistics for an

application, 4-112, 4-115enabling, 4-106, 4-109enhanced message distribution, 3-78invoking, 4-109, 4-111MML commands, 3-78, 3-80setting up, 3-82, 3-88stages, 3-81

Load Control Commands menu, 3-86Load Control Persistence, 3-77load distribution, displaying type, 4-28, 4-30load files, 2-10load-shared routes, configuration

limitations, 3-2local application, 3-111, 4-121local processor outage (LPO)

heartbeat messages, 3-110Local Reference Memory (LRM), C-26local reference memory (LRM)

checking (dumping), 4-122, 4-123

environment variables for defining, 3-112local reference number (LRN)

checking (dumping), 4-122, 4-123environment variables for defining, 3-112releasing frozen, 4-124, 4-126

local SSNadding/deleting concerned point code

from, 4-37, 4-38checking availability, 6-11–6-12displaying, 4-30, 4-31

Local Subsystem Number (LSSN), 3-47, 3-48, 3-49

Log Analysis commandsDISPLAY, 6-21FIND, 6-28QUIT, 6-31relational operators and

keywords, 6-18–6-20SELECT, 6-28–6-29SUMMARY, 6-29–6-30

log filesAlarm History, 5-3changing number of days before

deletion, 4-90deleting from disk, 4-91searching, 6-19–6-20system, 5-8–5-10

logging in, 2-2logical board assignments, verifying, 6-1login name

examples, 2-2long-term remote processor outage, 3-106loopback detection, 3-120, 4-3

LOOPBACK_DISPLAY, 3-7LOOPBACK_DISPLAY, 3-120, 4-3, 4-6LPC Routing, 3-35LRM. See local reference memoryLRN. See local reference number

Mman command, 2-24, 2-25Man Machine Language (MML)

commandsappending text strings to, 3-14


Index

executing from a login window/UNIX prompt, 2-21, 2-24

load control, 3-78, 3-80mode, 2-16privilege levels, defining, 3-10sample script file, 2-24

definition file, 3-10designating MML command recipient

address, 3-14Menu Definition File, 3-11

man page, 2-23displaying, 2-24

man pagesdisplaying, 2-24, 2-26

Management Inhibit (MIM) message, 3-99, H-8Man-Machine Interface (MML), 2-26Man-Machine Language (MML), xxxiMANPATH, 2-24manuals

notation conventions, xxxirelated, xxxiiirevision information, xxixviewing, xxxiv

MAX_PGTT_DIGITS, 3-65, 3-66MDF. See Menu Definition FileMeasurement reports

REPORT-MALL, 4-58, 4-62, 4-69, 4-73REPORT-MMTP, 4-62, 4-63, 4-69REPORT-MSSCP, 4-58REPORT-MTCAP, 4-58REPORT-MTP, 4-58

measurementsCommands menu, 4-59handling, 4-58, 4-61log file, 4-80

initiating writing measurements to, 4-80stop writing to, 4-81

reportsconsiderations, 4-61, 4-62entering date and time information, 4-60,

4-61latest 5-minute node network

management, 4-77MTP, 4-62, 4-65MTP,SCCP, and TCAP, 4-69, 4-72oldest 15- or 30-minute node network

management, 4-73, 4-77on-demand, 4-78, 4-80saving and printing, 4-62saving to a file, 4-59SCCP, 4-65, 4-67TCAP, 4-67, 4-69

measuring link congestion, 3-92, 3-93member routing, E-3Menu

Load Control Commands, 3-86Menu Definition File (MDF)

defining menu options, 3-11menu definition operators, 3-11

# (Comment Operator), 3-17MENU.BEGIN, 3-12MENU.END, 3-12MENU.HELP, 3-13MENU.NAME, 3-13OP.BUILD, 3-14OP.DEST, 3-15OP.ENDREQ, 3-15OP.HELP, 3-16OP.MENU, 3-16OP.SCRIPT, 3-17OPTION, 3-13

menu organization, 3-17, 3-18sample, 3-17, 3-23

menu definition operators, 3-11# (Comment Operator), 3-17MENU.BEGIN, 3-12MENU.END, 3-12MENU.HELP, 3-13MENU.NAME, 3-13OP.BUILD, 3-14OP.DEST, 3-15OP.ENDREQ, 3-15OP.HELP, 3-16OP.MENU, 3-16OP.SCRIPT, 3-17OPTION, 3-13

menu selection mode in the Terminal Handler, 2-15, 3-10

MENU.BEGIN menu operator, 3-12MENU.END menu operator, 3-12MENU.HELP menu operator, 3-13MENU.NAME menu operator, 3-13

Index 15

Index

MenusConfigure Commands, 3-42, 3-67Create Commands, 3-27, 3-28, 3-29, 3-30,

3-33, 3-38, 3-46, 3-48, 3-51, 3-53, 3-64

Network Commands, 3-29SINAP System Main, 3-29, 3-31, 3-33, 3-37,

3-51, 3-53, 3-82menus

Application Commands, 2-18, 3-82, 4-3beginning, 3-12BITE commands, 2-18, 4-93BITE Monitor commands, 4-93Configure Commands, 3-68Create Commands, 3-28, 3-31Delete Commands, 4-47, 4-49Display Commands, 4-1ending, 3-12help for a specific menu, 3-13help options for an option topic, 3-16invoking a user-supplied UNIX script

file, 3-17Load Control Commands, 4-108Menu Definition File, 3-11Menu Definition File sample, 3-17, 3-23menu definition operators, 3-11naming, 3-13Network Commands, 2-18, 3-68options, 3-13Report Measurements, 4-60specifying next menu name, 3-16System Commands, 2-18

MessageSignaling Link Test (SLTM), C-21Signaling Route Set Test (RST), 3-74Transfer Restart Waiting (TRW), 3-97

message processing during MTP restart, 3-100message signaling units (MSUs), 6-1

sample data record, 6-23–6-24Message Transfer Part (MTP), 1-1, 3-32, C-13

alarm formats, 5-8link congestion thresholds

ANSI network variant, E-7CCITT network variant, D-3NTT network variant, G-4

TTC network variant, F-2management table, dumping to static table

file, 4-81, 4-82measurements, reporting, 4-62, 4-65

all for MTP, SCCP, and TCAP, 4-69, 4-72overview, 3-96, 3-97process labels, 2-26restart process, 3-96, 3-105

completing, 3-105displaying information, 3-93, 3-105for ANSI, 3-99for CCITT, D-6, D-8for CCITT and China, 3-98, 3-99message processing, 3-100messages used, 3-97MTP_ANSI92_RESTART, 3-99MTP_WHITE_BOOK_RESTART, 3-9

8performing on a SINAP node, 3-100,

3-102performing on adjacent node, 3-102,

3-103variant differences, 3-98

routing table, dumping to static table file, 4-81, 4-82

time-controlled changeover. See time-controlled changeover (TCCO)

time-controlled diversion. See time-controlled diversion (TCD)

timer settingsANSI network variant, E-5, E-7CCITT network variant, D-2, D-3NTT network variant, G-4, G-6TTC network variant, F-2, F-3

timer, conditions under which implemented, 3-106

MessagesChangeover and Changeback

(CHM), 3-99, H-8Emergency-Changeover (ECM), 3-99, H-8I_N_PCSTATE_INDIC, 3-95Management Inhibit (MIM), 3-99, H-8Reset (RST), 3-74SCCP Management (SCMG), 5-1Signaling Link Test (SLT), 4-100


Index

Signaling Link Test Acknowledgment (SLTA), 3-97

Signaling Link Test Management (SLTM), 3-97

Signaling Network Management (SNM), 3-99

Signaling Route Test (SRT), 4-100, C-21Signaling-Data-Link-Connection-Order

(DLM), 3-99Signaling-Data-Link-Connection-order

(DLM), H-8Signaling-Route-Set-Test (RSM), 3-99,

H-8Signaling-Traffic-Flow-Control

(FCM), 3-99, H-8Subsystem Allowed (SSA), 3-75, 5-1Subsystem Out-of-Service Grant

(SOG), 5-1Subsystem Out-of-Service Request

(SOR), 5-1Subsystem Prohibited (SSP), 5-1Subsystem Status Test (SST), 5-1Traffic Restart Allowed (TRA), 3-97Traffic Restart Waiting (TRW)

message, 3-98Transfer Allowed (TFA), 3-74, 3-97, 3-98,

3-100Transfer Prohibited (TFP), 3-74, 3-97, 3-98,

3-100Transfer Restricted (TFJ), 3-98Transfer Restricted (TFR), 3-74, 3-97,

3-100User Part Flow Control (UFC), 3-99, H-8User Part Unavailable (UPU), F-6, H-7User-In-Service (UIS), 3-75User-Out-of-Service (UOS), 3-75

messageseven distribution of

MTP_SLS4_LOAD_SHARE, 3-8messages written to the system log file

abnormal, 5-8default, 5-9–5-10normal, 5-8

MIN_PGTT_DIGITS, 3-65, 3-66MML

command log file, 2-22, 2-23sample commands, 2-24

MML command interface, 2-15MML command mode, 2-18MML command screen, 3-86MML commands

CHANGE-GTT, 4-43CHANGE-SLSTYPE, 3-109CREATE-FOPC, 4-17, 4-53DELETE-FOPC, 4-53menu grouping, 2-18negative responses to, I-9REPORT-ALARM, 5-5REPORT-MALL, 5-5REPORT-NBOOK, 5-5START_MON, I-6unknown responses to, I-10

MMl commandsDISPLAY-FOPC, 4-17

MML. See Man Machine LanguageMML Send Menu, 2-19mmlverb file, 3-10monitoring using BITE, 4-93MSUs. See message signaling unitsMTP, 2-12, 3-51, I-9

restart process, 3-6MTP L3RC, 3-75MTP Level 3 SNM message, I-23MTP restart, 3-74, I-22MTP restart process, 2-10, 2-11, 3-96MTP routing labels, 3-51MTP_ANSI88_RSR_RST, 3-8, 3-122MTP_ANSI92_TCCO, 3-6, 3-107, E-10MTP_ANSI92_TCD, 3-7, 3-108, E-11MTP_DISPLAY, I-4MTP_LINKSET_MEASUREMENT, 4-62, 4-64,

4-69, 4-73MTP_PARTIAL_RESTART, H-7MTP_RESUME, 3-75MTP_SLS4_LOAD_SHARE, 3-8, 3-43, 3-72,

3-75, 3-89MTP_USER_FLOW_CTL, H-7MTP_USER_FLOW_CTRL, H-7MTP_WHITE_BOOK, 4-14MTP_WHITE_BOOK_RESTART, H-7

Index 17

Index

MTP_WHITE_BOOK_SLC, 3-6MTP_WHITE_BOOK_TCCO, 3-6, 3-107, D-8,

H-9MTP_WHITE_BOOK_TFR, 3-7MTP-RESUME, 3-105MultiStack product, 1-1

NN_STATE_REQ SCMG_UIS, F-4, G-9N_STATE_REQ SCMG_UOS, F-4, G-9NAT_MUL_CONG_WITH_PRIO, 3-90NAT_MUL_CONG_WO_PRIO, 3-93NAT_MULT_CONG_WO_PRIO, 3-91, 3-92National Indicator (NI), I-12, I-30Nature-of-Address Indicator (NOAI), 3-55,

3-56Netra 20/T4 platform, configuration limits, 3-1Network Commands menu, 2-18, 3-29, 3-68network components, 3-26

activating, 3-67creating, 3-26, 3-27creating with a script file, 2-30displaying configuration information, 4-1sample configuration, 3-27, 3-28See also own point code, link set,

combined link set, links, route set, concerned point code, duplicate concerned point code, remote subsystem number, global title translation, and FOPC

network congestion. See link congestionnetwork information and planning forms, A-1,

A-3, A-5, A-6, A-8network routing, E-3Network variant

ANSI, xxxCCITT, xxxChina, xxxiNTT (Japanese), xxxTTC (Japanese), xxx

Network, cluster, and member routing, E-1network, cluster, and member routing for the

ANSI network variant, E-2, E-3Nippon Telephone and Telegraph, G-1

NM_EVENT, I-2, I-3nmnp, 2-9

process, 3-108nmnp.out, 2-9nmnp.p3f, 2-9node database backup cycle

changing number of days, 4-84displaying number of days in, 4-83, 4-84

Node ManagementNode Parent process, 3-108process labels, 2-27Software Notebook, 5-5

Node Management command management process (NMCM), I-4

Node Management parent (nmnp) process, 3-99Node Management parent process (nmcm), I-3node network management measurement report

retrieving 5-minute report, 4-77, 4-78retrieving oldest 15- or 30-minute, 4-73,

4-77node static database

backing up, 4-82restoring from disk, 4-85, 4-86

nohup.out, 2-9nondata primitives, 5-8NTT, 2-25, G-1NTT network variant, G-9

configuration requirements and limitations table, 3-1

differences compared to CCITT, G-10, G-11

link congestion thresholds, G-4, G-5MTP timer settings, G-4point code format, G-2SCCP timer settings, G-4setting SLS bits in MSU routing

labels, G-6signaling link set statuses, G-7signaling link statuses, G-7signaling route statuses, G-7time-controlled changeover (TCCO), G-8time-controlled diversion (TCD), G-8timer settings, G-4, G-6unsupported features, G-11UOS and UIS messages, G-8, G-9


Index

user-in-service (UIS) message, G-8user-out-of-service (UOS) message, G-8

NTT Point Code Format, G-2Numbering Plan (NP), 3-55, 3-56

Ooctal notation, 2-19, 2-21on-demand measurements

starting, 4-78, 4-79stopping, 4-80

onset table, 3-95displaying settings, 3-93

OP.BUILD menu operator, 3-14OP.DEST menu operator, 3-14OP.ENDREQ menu operator, 3-15openlog(), 5-9operation modes

test-environment mode, 2-3verbose mode, 2-3

operators and key words for BITE log analysis commands, 6-18–6-20

OP.HELP menu operator, 3-16OP.MENU menu operator, 3-16OP.SCRIPT menu operator, 3-17OPTION menu operator, 3-13Originating Point Code (OPC), 3-51, H-2OSP. See own signaling point code.out, 2-9overload conditions, 3-76Own Signaling Point (OSP) cod, 3-31Own Signaling Point (OSP) code, 3-27, C-10,

C-12own signaling point code (OSP)

creating, 3-31, 3-34deleting, 4-51displaying and printing, 4-14, 4-15

PPARTIAL_GTT, 3-4, 3-65, 3-67PCI cards, supported, 3-1periodic link testing, 4-100

accessing, displaying, and changing SLT/SRT timers, 4-101, 4-103

disabling, 4-105

enabling, 4-103, 4-105monitoring the results of, 4-104

physical board assignments, verifying, 6-1Point Code (PC), 3-50, I-12, I-30point code format

CCITT network variant, D-2China network variant, H-2NTT network variant, G-2TTC network variant, F-1

port number, 3-40Primitives

MTP-RESUME, 3-105printing

concerned point code information, 4-15, 4-17

enabling and disabling, 2-28, 2-29fictitious originating point code

information, 4-17, 4-18measurements

reports, 4-62own signaling point code

information, 4-14, 4-15remote SSN information, 4-18, 4-19

privilege levels for MML commands, defining, 3-10

process identifier (PID), 2-15processes

configuration limitations, 3-3displaying versions, 2-27, 2-28list of, 2-26, 2-27listing active, 6-2

processor outagelong-term, 3-106short-term, 3-106

Processor outage control (POC), F-6purge commands, accessing, 4-88purge day, 4-87

changing interval, 4-90, 4-91displaying interval, 4-88, 4-89

Q? command, C-23Q command, C-26QUIT command, 6-31, C-23

Index 19

Index

Rrandom link selection, 3-114rclog, 2-30rclog file, 4-86

using to restore database configuration, 4-87

rcMeasData, 4-73Read Trouble Treatment Table command, 5-16,

C-15READ-TREAT command, 5-16, C-15Recent Change Command Log file, 2-30, 4-86


Recent Change log (rclog), I-4re-creating existing configurations, 2-30, 2-32release_lrn command, 4-124, 4-126releasing frozen LRNs, 4-124, 4-126remote node, checking accessibility, 6-10remote point code, deleting all from an

SSN, 4-52remote processor outage, 3-106remote SCP, 1-1remote SSN, 3-50, E-3, E-4

adding/deleting, 4-39checking accessibility, 6-10creating, 3-50, 3-51deleting all from a node, 4-54displaying and printing information, 4-18,

4-19Remote Subsystem Number (SSN), 3-26, 3-50,

C-10Remote Subsystem Numbers (SSN, C-12remove_shm, 2-37removing

links, link sets, and route sets from service, 4-57

Replicate Point Code (RPC), 3-47, 3-49Report Alarm command, 5-3–5-5, C-15Report Measurements

command, 4-69, 4-72, C-15menu, 4-60

Report MTP Measurements command, 4-62, 4-65, C-16

Report SCCP Measurements command, 4-65,

4-67, C-16Report Software Notebook command, 5-6–5-7,

C-17Report TCAP Measurements command, 4-67,

4-69, C-17REPORT-ALARM command, 5-3–5-5, C-15reporting

all measurements related to MTP, SCCP, and TCAP, 4-69, 4-72

MTP measurements, 4-62, 4-65SCCP measurements, 4-65, 4-67TCAP measurements, 4-67, 4-69

REPORT-MALL, 4-62, 4-69, 4-73REPORT-MALL command, 4-69, 4-72, C-15REPORT-MMTP, 4-62, 4-63, 4-69REPORT-MMTP command, 4-62, 4-65, C-16REPORT-MSCCP command, 4-65, 4-67, C-16REPORT-MTCAP command, 4-67, 4-69, C-17REPORT-NBOOK command, 5-6–5-7, C-17Reset (RST) message, 3-74restart, 2-10restarting SINAP/MultiStack, 2-10, 2-11

with a script file, 2-10Restore Application command, 4-86, 4-87, C-17Restore Node command, 4-85, 4-86, C-17RESTORE-APPL command, 4-86, 4-87, C-17RESTORE-NODE command, 4-85, 4-86, C-17restoring

applications from disk or tape, 4-86, 4-87database configuration, 4-87node static database from disk, 4-85, 4-86

restricting traffic on one link set, 4-57Retrieve Latest 5-Min Measurement

command, 4-77, 4-78, C-18Retrieve Oldest 15- or 30-Minute Measurement

command, 4-73, 4-77, C-18RETRIEVE-NOM command, 4-73, 4-77, C-18RETRIEVE-SMR command, 4-77, 4-78, C-18retrieving node network management

measurement reportlatest 5-minute, 4-77, 4-78oldest 15- or 30-minute, 4-73, 4-77

route sets, E-4and dynamic route provisioning, E-4, E-5blocking, 4-57


Index

changing the content, 4-35, 4-37checking status, 6-8–6-9configuring (activating), 3-72, 3-74creating, 3-42, 3-46deleting, 4-51displaying configuration

information, 4-10, 4-14removing from service, 4-57

route sets, configuration limitations, 3-2RouteOnGT, 3-56RouteOnSSN, 3-56routes, configuration limitations, 3-2routeSetMeasurement, 4-73routing capabilities

ensuring sequentialityMTP_SLS4_LOAD_SHARE, 3-8

routing for the ANSI network variant, E-2, E-3RSP message, 3-122RSR message, 3-122RST_CONFIG_INIT_PROHIBIT, 3-43RST_CONFIG-INIT_PROHIBIT, 4-11,

4-12

S#sc,lrm command, 4-122#sc,lrn command, 4-123#sc,lrn,1 command, 4-123#sc,ssn command, 6-10#SLD command, 4-28, 4-30, C-27#SLD,APPL,appl_name command, 4-30#SLD,SIO,sio_number command, 4-29#SLD,SSN,ssn_number command, 4-29#STA,ST,L3 command, 3-105, C-28#STA,ST,MTP command, 3-94#sta,xudt command, 3-117#sys command, 3-93, C-28saving

BITE log file, 6-21measurement report, 4-62

SC_EVENT, I-2, I-12SCCP, 3-43, 3-51, 3-53, 3-54, 3-62, 3-63, 3-99, H-8SCCP management (SCMG), 3-75SCCP Management (SCMG) message, 5-1SCCP management (SCMG) message, F-6

SCCP. See Signaling Connection Control PartSCMG, 3-75SCMG messages not supported by TTC, 5-1Screens

CONFIGURE-LINK, 3-68CREATE-CLSET, 3-37CREATE-CPC, 3-46CREATE-DUCPC, 3-48CREATE-FOPC, 3-52CREATE-GTT, 3-58CREATE-LINK, 3-39CREATE-LSET, 3-34, 3-70CREATE-OSP, 3-31CREATE-REMSSN, 3-50CREATE-RSET, 3-43MML command, 3-86SETUP-LOAD-CONTROL, 3-82, 3-83Terminal Handler, 3-23

script file, using to create network components, 2-30

SCTX timer, D-5, H-6SELECT

FILE command, C-23SELECT command, 6-28–6-29Send a Debug Message command, C-19send_cm, 2-21, 2-22, 2-23, 2-24, 2-30, 3-57send_cm command, C-18

accessing MTP L3 timers with, 3-103using to display XUDT timer values, 3-117

Service Control Point (SCP), 1-1Service Indicator (SI), 3-32, 3-99, 3-100Service Information Octet (SIO), 3-32, 3-99,

C-27, H-8Service Information Octets (SIO), C-19Service Instance (SI), H-8Service Node (SN), 1-1Set Printer command, 2-29, C-19Set Up Load Control command, 3-78, 3-79,

3-82, 3-88, C-18SET-PRINTER command, 2-29, C-19SETUP-LOAD-CONTROL command, 3-78,

3-79, 3-81, 3-82, 3-85, 3-86, 3-87, 3-88, C-18

SETUP-LOAD-CONTROL screen, 3-82, 3-83short-term processor outage, 3-106

Index 21

Index

SIGCHLD signal, 2-14Signaling Connection Control Part

(SCCP), 1-1, 2-12, F-2, F-3, G-4, G-6alternate routing for CCITT, 3-56, 3-58connection-oriented timers, 4-126, 4-128management messages not supported by

TTC, 5-1process labels, 2-27reporting all measurements for MTP,

SCCP, and TCAP, 4-69, 4-72reporting measurements, 4-65, 4-67timer settings

ANSI network variant, E-8CCITT network variant, D-4, D-6

Signaling Connection Control Point (SCCP), C-13

Signaling Information Field (SIF), C-19signaling link assignments (SLS),

displaying, 4-30Signaling Link Code (SLC), 3-39, 3-41, 4-101,

I-28signaling link code (SLC), C-25, C-26signaling link code (SLC) for MTP SNM

messages, 3-113Signaling Link Management (SLM), 3-97signaling link selection assignments (SLS),

displaying, 4-28signaling link set statuses

in NTT network variant, G-7used in NTT network variant, G-7

signaling link statusesused in NTT network variant, G-7

signaling link test (SLT)setting or resetting, 4-33, 4-34test messages, sending, 4-99testing with BITE, 4-99timers, accessing, displaying, and

changing, 4-101, 4-103Signaling Link Test (SLT) message, 4-100Signaling Link Test (SLTM) message, C-21signaling link test acknowledgment

(SLTA), 4-100Signaling Link Test Acknowledgment (SLTA)

message, 3-97Signaling Link Test Management (SLTM)

message, 3-97signaling links, configuration limitations, 3-1signaling network

managementmessages with nonzero SLCs, 3-6

Signaling Network Management (SNM)message types, H-8

Signaling Network Management (SNM) message, 3-99

Signaling Point Code (SPC), 3-28, 3-32signaling point restart

activating, H-7control, 3-97

Signaling Route Set Test (RST) message, 3-74signaling route statuses

used in NTT network variant, G-7signaling route test (SRT)

setting or resetting, 4-34timers, accessing, displaying, and

changing, 4-101, 4-103Signaling Route Test (SRT) message, 4-100,

C-21signaling route test acknowledgment

(SRTA), 4-100Signaling Transfer Point (STP), C-5Signaling Transfer Points (STP), 1-1Signaling Unit Error Rate Monitor count, I-16Signaling-Data-Link-Connection-Order

(DLM) message, 3-99Signaling-Data-Link-Connection-order (DLM)

message, H-8Signaling-Route-Set-Test (RSM)

message, 3-99, H-8Signaling-Traffic-Flow-Control (FCM)

message, 3-99, H-8SINAP

product, 1-1SINAP Dynamic Linked Library (DLL), E-12SINAP node

performing MTP restart on, 3-100, 3-102performing MTP restart on adjacent

node, 3-102, 3-103SINAP System Main Menu, 3-29, 3-31, 3-33,

3-37, 3-51, 3-53, 3-82SINAP/MultiStack root directory, 2-26


Index

SINAP_ALT_MEASUREMENT_INTERVAL, 4-58, 4-62, 4-69, 4-74

SINAP_CONSOLE_ALARM_LEVEL, 3-123and default alarm messages, 5-9

SINAP_HOME, 2-2SINAP_LOG_SIZE, 5-5SINAP_LRN_FREEZE_TIMEOUT=nnnn, 3-

113sinap_master, 2-1SINAP_MML_ALT_NUMERIC_CONVERSIO

N, 2-19, 2-21SINAP_MML_PRINT_RESPONSE, 2-28,

2-29SINAP_MML_PRINT_TTYNAME, 4-59SINAP_TOTAL_LR_MEMS=nnnn, 3-112SINAP_TOTAL_LR_NUMS=nnnn, 3-113sinap_update command, 4-49, 4-128SINAP_USER_LR_MEMS=nnnn, 3-113sinap_utlmon, 2-14, 2-15sinap_utlmon.dat, 2-14SINAP_XUDT_SEGMENT_SIZE, 3-118, I-40SLC (signaling link code) for MTP SNM

messages, 3-113SLC for MTP SNM messages, 3-113sleep, 2-9, 2-37SLS (signaling link assignments),

displaying, 4-30SLS (signaling link selection assignments),

displaying, 4-28SLS Processing

5-bit, 3-109, 3-1108-bit, 3-109, 3-110

SLS(signaling link selection assignments)setting SLS bits in NTT network

variant, G-6SLT, 3-100SLT. See signaling link testSLTA, 3-100SLTA (signaling link test

acknowledgment), 4-100SLTM Loopback Detected parameter, 4-6SLTM_WITH_NAT10_FOR_G500, 4-101SLTT1 and SLTT2 timers, 4-101SNM message types, 3-100SNM. See Messages, 3-99

Software Notebook. See Node Management Software Notebook

SOG (subsystem out-of-service grant) message, 5-1

Solaris, 2-18, 3-122, 4-99, 5-1, 5-9, 6-1, E-12SOR (subsystem out-of-service request)

message, 5-1Specifying signaling link connection for the

link set, 3-35SRT. See signaling route testSRTA (signaling route test

acknowledgment), 4-100SRTT10 and SRTT20 timers, 4-101SS7, 1-1SS7 protocol types

ANSI, 1-1CCITT, 1-1China, 1-1TTC, 1-1

ss7dmn, 2-9ss7dmn.out, 2-9SSA (subsystem allowed) message, 5-1SSN, 3-54SSN (subsystem number), displaying, 4-30SSP (subsystem prohibited) message, 5-1SST (subsystem status test) message, 5-1Standards

ANSIT1.111.5, 3-109

Start a BITE Scenario command, C-20Start Monitor command, 4-93, 4-96, 6-16, C-19Start On-Demand Measurements

command, 4-78, 4-79, C-19Start Write Log File command, 4-80, C-19START_MON, I-6start_sinap, 2-2, 2-3, 2-10start_sinap command, C-20


start_sinap script file, 2-2, C-20using to restore database

configuration, 4-87startappl, 2-12, 2-13START-DBG command, C-19starting

Index 23

Index

BITE Log Analysis program, 6-16–6-17BITE monitor, 4-93, 4-96, 6-16measurements to the measurement

log, 4-80on-demand measurements, 4-78, 4-79Terminal Handler, 2-18

starting SINAP/MultiStack, 2-2, 2-10START-MEASURE command, 4-78, 4-79, C-19START-MON command, 4-93, 4-96, 6-16, C-19START-MWRITE command, 4-80, C-19START-SCEN command, C-20startup commands, 2-3static table file, dumping MTP routing and

management tables to, 4-81, 4-82STATIC_load, 2-10static2mml, 2-29, 2-30, 2-31, 2-32static2mml command, 2-32, C-20STCONEST timer, 4-126STGUARD timer, 4-127STIAR timer, 4-127STIAS* timer, 4-127Stop a BITE Scenario command, C-21Stop Monitor command, 4-97, 4-98, 6-16, C-21Stop On-Demand Measurements

command, 4-80, C-21Stop Write Log File command, 4-81, C-21stop_sinap, 2-10, 2-11, 2-32, 2-37, 2-38stop_sinap command, C-21stop_sinap script file, C-21STOP-MEASURE command, 4-80, C-21STOP-MON command, 4-97, 4-98, 6-16, C-21STOP-MWRITE command, 4-81, C-21stopping

BITE monitor, 4-97, 4-98on-demand measurements, 4-80SINAP/MultiStack, 2-32, 2-38writing to measurement log file, 4-81

STOP-SCEN command, C-21STREL timer, 4-127STRELINT timer, 4-127STRELREP timer, 4-127STRESET timer, 4-127Structures

t_block_t, 3-85Subservice Field (SSF), 4-101

Subservice field (SSF), 4-101Subsystem allowed (SSA), F-6Subsystem Allowed (SSA) message, 3-75, 5-1Subsystem Number (SSN), 3-46, C-4subsystem number (SSN), displaying, 4-30Subsystem out-of-service grant (SOG), F-6Subsystem Out-of-Service Grant (SOG)

message, 5-1Subsystem out-of-service request (SOR), F-6Subsystem Out-of-Service Request (SOR)

message, 5-1Subsystem prohibited (SSP), F-6Subsystem Prohibited (SSP) message, 5-1Subsystem Status Test (SST), 3-75Subsystem status test (SST), F-6Subsystem Status Test (SST) message, 5-1subsystem status test (SST) message, 5-1Subsystem-Go-Out-of-Service request, H-6Subsystem-Out-of-Service-Grant (SOG), H-6SUMMARY

FILE command, C-23SUMMARY command, 6-29–6-30SunFire V480 platform, configuration

limits, 3-1sy command, 3-93, C-28sy command #L3, port, 4-6sy debugger, 3-93, 4-28

commands, C-23–C-28sy utility, 3-66syslog(), 5-9sysopr, 2-16, 3-85, I-47System Commands menu, 2-18system log file, 5-8–5-10system tables, changing, 4-40, 4-42

Tt_block_t, 3-85T1/E1 (G703) links

configuration limitations, 3-1TCAP, 3-43, 3-99, H-8TCCO

MTP_ANSI92_TCCO, 3-6MTP_WHITE_BOOK_TCCO, 3-6

TCCO. See time-controlled changeover


Index

TCDMTP_ANSI92_TCD, 3-7

TCD. See time-controlled diversionTCRELAY, 3-119Telecommunications Technology Committee

(TTC) of Japan, xxixTelephone User Part (TUP), 3-32Telnet, 2-18Terminal Handler, 2-18, 2-20, 3-10

building menus. See MDFconfiguring, 3-10Create Commands menu, 3-28, 3-31exiting, 4-49free-form mode, 3-10keyboard shortcuts, 2-20Menu Definition File. See MDFmenu selection mode, 2-15, 3-10MML command mode, 2-16screen partitions, 3-23, 3-26starting, 2-15, 2-18types of input, 2-19

Display confirmation, 2-19Menu selection options, 2-19Prompt responses, 2-19

using operation modes, 2-18, 2-19terminal handler, 3-28, 3-31, 3-37, 3-39, 3-43,

3-51, 3-52, 3-53, 3-64Terminal Handler screen, 3-23Terminal Handler System Main Menu, 2-18Terrminal Handler

keyboard shortcuts, 2-20Test Link command, 4-99, C-21Test Route command, C-22TEST-LINK command, 4-99, C-21TEST-ROUTE command, C-22TFR

handlingMTP_ANSI88_RSR_RST, 3-7MTP_WHITE_BOOK_TFR, 3-7

thresholdschanging values, 4-40, 4-42displaying and printing values, 4-19, 4-20levels for link congestion, 3-95, 3-96sample displays, 4-21, 4-25

Time-Controlled Changeover (TCCO), E-1,

H-7MTP_WHITE_BOOK_TCCO, H-8

time-controlled changeover (TCCO), 3-105, E-10

long-term processor outage, 3-105for ANSI network variant, E-10for CCITT network variant, D-8for NTT network variant, G-8for TTC network variant, F-4

MTP_WHITE_BOOK_TCCO, D-8short-term processor outage, 3-105

for ANSI network variant, E-10for CCITT network variant, D-8for NTT network variant, G-8for TTC network variant, F-4

Time-Controlled Diversion (TCD), E-1, H-7, H-9

time-controlled diversion (TCD), 3-107, E-11, G-8

implementing, 3-108timer settings

MTPfor ANSI network variant, E-5, E-7for CCITT network variant, D-2, D-3for NTT network variant, G-4, G-6for TTC network variant, F-2, F-3, G-4

SCCPfor ANSI network variant, E-8for CCITT network variant, D-4, D-6for NTT network variant, G-4, G-6for TTC network variant, F-2, F-3

TimersCONGESTION_TX_TIMER, 3-92CONGESTION_TY_TIMER, 3-92

timerschanging values, 4-40, 4-42displaying and printing values, 4-19, 4-20MTP, conditions under which

implementation occurs, 3-106sample displays, 4-21, 4-25settings. See timer settingsSLTT1 and SLTT2, 4-101SRTT10 and SRTT20, 4-101

timestamp, 4-73TPRC (signaling point restart control), 3-97TRA, 3-100

Index 25

Index

TRA message, 3-105Traffic Restart Allowed (TRA) message, 3-97Traffic Restart Waiting (TRW) message, 3-98Transaction Capabilities Application Part

(TCAP), 1-1, 2-1reporting all measurements for MTP,

SCCP, and TCAP, 4-69, 4-72reporting measurements, 4-67, 4-69

Transfer Allowed (TFA) message, 3-74, 3-97, 3-98, 3-100

Transfer Prohibited (TFP) message, 3-74, 3-97, 3-98, 3-100

Transfer Restricted (TFJ) message, 3-98Transfer Restricted (TFR) message, 3-74, 3-97,

3-100Translation Type (TT), 3-55, 3-56TREAT_load, 2-10TREAT_load file, 5-16treat.tab, 5-10

using to add/change an event or its treatment, 5-16

Trouble Managementand handling of events, 5-10defining category treatments to implement

upon receiving events, 5-11trouble treatment table, 5-10

and events, 5-10contents, 5-12–5-14creating, 5-10file parameters, 5-12–5-14format and contents, 5-11sample file, 5-15using to add/change an event or its

treatment, 5-16Trouble Treatment tables, I-1troubleshooting, 6-1TRW, 3-100TRW message, 3-97TTC, 2-25TTC network variant

administrative features not supported by, F-6

Change Commands menu, 4-33configuration requirements and limitations

table, 3-1

Delete Commands menu, 4-49differences compared to CCITT, F-5, F-6Display Commands menu, 4-3implementing the TCCO feature, F-4link congestion thresholds, F-2link testing, F-3, G-6load control, 3-88MTP restart process, 3-96, 3-105point code format, F-1SCMG messages not supported by, 5-1timer settings, F-2, F-3UOS and UIS messages, F-4, F-5

TTC_WITH_NSTATEusing to specify who sends UOS and UIS

messages, F-4, F-5, G-9TTC_WITH_NSTATE environment

variable, 3-26, 3-46

UU403 PCI card, 3-1U420 PCI card, 3-1U915 PCI card, 3-1U916 PCI card, 3-1UIS (user-in-service) message, F-4, G-8UNIX, xxix, 1-2, 2-11, 2-22, 2-24, 2-32

initialization file, 2-2, 2-11UNIX system alarms

SIGALRM, I-6UOS (user-out-of-service) message, F-4, G-8updating link configuration information, 4-128UPU messages, 3-115User Flow Control (UFC), F-6user part flow control, H-7User Part Flow Control (UFC) message, 3-99,

H-8User Part Unavailable (UPU) message, F-6User Part Unavailable (UPU) messages, H-7user part unavailable messages, 3-115User-In-Service (UIS) message, 3-75user-in-service (UIS) message, F-4, G-8User-Out-of-Service (UOS) message, 3-75user-out-of-service (UOS) message, F-4, G-8user-supplied alarms and events, 5-17Utility Monitor, 2-14, 2-15


Index

V/var/adm/syslog file, 5-1vi editor, 2-12

XXUDT and UXDTS messages

hop counter, XUDT messages, 3-119XUDT and XUDTS messages, 3-116, 3-118

MSU segment size, XUDT messages, D-5, H-6

XUDT routing table, I-13

ZZ command, C-28

Index 27

sinap/ss7 user’s guide -...

Documents