Lucent Technologies AP-3 User Manual
Lucent Technologies AP-3 User Manual

Lucent Technologies AP-3 User Manual

Avaya ap-3 access point: connection guide
Hide thumbs Also See for AP-3:
Table of Contents

Advertisement

Quick Links

APS (Application Plus Server) 4.1

Users Guide

101-1830-001
Issue 1.0
June 1999

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the AP-3 and is the answer not in the manual?

Questions and answers

Summary of Contents for Lucent Technologies AP-3

  • Page 1: Users Guide

    APS (Application Plus Server) 4.1 Users Guide 101-1830-001 Issue 1.0 June 1999...
  • Page 2 Copyright 1999, Lucent Technologies All Rights Reserved, Printed in U.S.A. Notice Every effort was made to ensure that the information in this book was complete and accurate at the time of printing. However, information is subject to change. Your Responsibility for Your System’s Security Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party, for example, persons other than your company’s employees, agents, subcontractors, or persons working on your com-...
  • Page 3: Table Of Contents

    About This Book Chapter 1 Overview Overview of the APS Environment ....25 101-1830-001 Issue 1.0 101-1830-001 Issue 1.0 ..........17 Audience Statement .
  • Page 4 APS (Application Plus Server) 4.1 Users Guide Communication Protocols......34 Description of APS Hardware ..... . . 36 Description of APS Software .
  • Page 5 APS (Application Plus Server) 4.1 Users Guide Software Upgrades ....... . 77 Chapter 3 Menu Interface Definitions .
  • Page 6 APS (Application Plus Server) 4.1 Users Guide Main Menu ........85 Script Menu.
  • Page 7 APS (Application Plus Server) 4.1 Users Guide Database Menu ........110 Chapter 4 Procedures APS System-wide Tasks .
  • Page 8 APS (Application Plus Server) 4.1 Users Guide Working with Profiles ......134 Importing and Exporting Data .
  • Page 9 Cron Tasks ........161 Using SQL Commands.
  • Page 10 APS (Application Plus Server) 4.1 Users Guide Troubleshooting Software Problems....200 Troubleshooting Hardware Problems ....206 Common Procedures.
  • Page 11 Chapter 7 Errors The Status Log File ....... . 229 What Makes Up an Alarm .
  • Page 12 APS (Application Plus Server) 4.1 Users Guide 505001 ........256 505002 .
  • Page 13 Passive Alarm Monitoring ......337 101-1830-001 Issue 1.0 101-1830-001 Issue 1.0 600013........299 600014.
  • Page 14 APS (Application Plus Server) 4.1 Users Guide EAP-related Errors ....... . 338 TCAP Errors .
  • Page 15 Developing Custom Reports ......377 Glossary, Abbreviations, and Acronyms Index 101-1830-001 Issue 1.0 101-1830-001 Issue 1.0 Relinking with Logging Stub .
  • Page 16 APS (Application Plus Server) 4.1 Users Guide 101-1830-001 Issue 1.0 101-1830-001 Issue 1.0...
  • Page 17: About This Book

    This manual describes the Application Plus Server (APS) 4.1 software platform. Use this manual with applications such as Inbound Call Completion (ICC) 1.1. Audience Statement This documentation is written for the following audiences: Software support staff Platform maintainers Lucent’s applications sales force This guide is not intended for programmers developing custom applications or for the end customer with the exception of the customer as maintainer.
  • Page 18: Purpose Statement

    APS (Application Plus Server) 4.1 Users Guide In general, the audience for this book should have the following experience and expertise: Purpose Statement The purpose of this document is to: This guide does not discuss the Sun hardware components of the APS system.
  • Page 19: Help And Technical Support

    Help and Technical Support You can reach Lucent Octel Messaging Division (OMD) by phone, fax, e-mail, and the Internet. For telephone assistance about APS software: For specific training information: To reach us by e-mail: For documentation: To fax an order: If you have world wide web access go to: 101-1830-001 Issue 1.0 Call 408-922-1822.
  • Page 20: Conventions

    APS (Application Plus Server) 4.1 Users Guide Conventions This book uses the following conventions: The term Sierra refers to a Sierra VPM (voice processing module). The term CA stands for Caller Applications VPM and was formerly known as IMA-CA (Intelligent Messaging Architecture-Caller Applications).
  • Page 21: Related Documents

    Related Documents Electronic Version An electronic version of this document is located inside the Lucent fire wall in Adobe Acrobat format. Go to http://info.dr.lucent.com/~bfthomas/aps/APS.html Other Manuals In this manual, we may refer you to other documents. You may want to locate them and have them at your site.
  • Page 22: Commenting On This Document

    APS (Application Plus Server) 4.1 Users Guide Commenting on This Document To comment on this manual, please direct communications to: Lucent Technologies Octel Messaging Division MS C5-04 1001 Murphy Ranch Road Milpitas, California 95035-3912 email: octeltechpubs@lucent.com telephone: 408-384-2000 Trademarks and Registered Trademarks Adobe is a trademark of the Adobe Systems Incorporated, which may be registered in certain jurisdictions.
  • Page 23 Wizard is a copyright if ISSG, Inc. x25tool is a trademark of Sun Micro Systems, Inc. 101-1830-001 Issue 1.0...
  • Page 24 APS (Application Plus Server) 4.1 Users Guide 101-1830-001 Issue 1.0...
  • Page 25: Chapter 1 Overview

    This chapter provides a high-level description of the APS 4.1 (Application Plus Server) environment, software, and hardware. Overview of the APS Environment The APS 4.1 platform software is the base software upon which other APS application software resides. Currently, the APS 4.1 platform, the ERP 2.0 report handling software, and the ICC 1.1 application are designed to work with each other, but may be ordered separately.
  • Page 26 APS (Application Plus Server) 4.1 Users Guide Figure 1 shows an example of hardware components at an APS site. Figure 1. Example Topology of an APS/ERP Site Sierra/CA Sierra/CA Disk array - Sun A1000 disk array Disk array - Sun MultiPack array HSI card for X.25 links, if X.25 protocol is used LAN switch to connect the ERP system, APS system, and Sierra/CAs...
  • Page 27: Software Constructs

    Software Constructs APS 4.1 platform software uses the following software constructs: Figure 2 shows how software constructs are used together to form an application. Figure 2. APS Programming Constructs Script A Functional Functional Functional 101-1830-001 Issue 1.0 Functional wizards Scripts Profiles Applications Cron tasks...
  • Page 28: Aps 4.1 Environment

    APS (Application Plus Server) 4.1 Users Guide APS 4.1 Environment The APS environment consists of: APS 4.1 APS is a Sun-based Service Creation Environment (SCE) system. APS was created to provide an infrastructure for quick creation of value-added applications. Applications are developed and run from the APS in cooperation with a Sierra/CA voice processing module.
  • Page 29: Aps 4.1 New Features

    APS 4.1 New Features APS 4.1 introduces the following new features: Upgrade to APS 4.1 platform software uses Informix 7.3 database. This upgrade Informix 7.3 provides the following advantages: TCP/IP Interface to APS 4.1 platform software offers the option of using TCP/IP connectivity Sierra/CA between the APS Sun systems and the Sierra/CAs.
  • Page 30: Erp 2.0 New Features

    APS (Application Plus Server) 4.1 Users Guide ERP 2.0 New Features ERP 2.0 introduces the following new features: Inclusion of ERP as Prior to APS 4.1, ERP was considered a custom application for an a Custom APS-based application. ERP currently provides reporting capabilities for Application only the ICC application.
  • Page 31 8. Checks that TCP/IP connectivity is up, if TCP/IP is being used. 9. Starts the APS application manager, which starts any applications 10. Logs informational alarm 600027 that a reboot occurred. 11. Logs informational alarm 600000 to begin system heartbeat. 101-1830-001 Issue 1.0 a.
  • Page 32: Aps 4.0 Features

    APS (Application Plus Server) 4.1 Users Guide APS 4.0 Features The previous version of APS, APS 4.0, introduced these new features in its release in January of 1999: All these features are carried over to APS 4.1. SS7 Interface to HLR APS 4.0 used only the SS7 protocol on a NewNet card to connect to the HLR.
  • Page 33: System Heartbeat

    System Heartbeat The system heartbeat provides a way to continuously monitor the APS platform. The system heartbeat is an informational alarm, alarm 600000, that is logged in the status log file. This alarm is logged every 15 minutes on the quarter hour. If this alarm is not logged, it means that the APS system has stopped functioning for some reason.
  • Page 34: Communication Protocols

    APS (Application Plus Server) 4.1 Users Guide Communication Protocols The communication protocols supported by APS 4.1 include: Figure 3 shows these communication protocols as used in the APS platform. OCL Versions The OCL interface between the APS and the VPM uses the following OCL and VIS versions APS 4.1 now has the ability to talk in OCL to VIS 2.0 on the Sierra/CA over an X.25 or TCP/IP interface using OCL version 1.2.
  • Page 35: Smtp

    Figure 3. APS 4.1 Interfaces SMTP The e-mail interface provided via SMTP (Simple Mail Transfer Protocol) is unchanged in APS 4.1. TCP/IP Interface Communications with external OSS (Operational Systems Support) systems using TCP/IP, modem, or X.25 interfaces are unchanged in APS 4.1.
  • Page 36: Description Of Aps Hardware

    APS (Application Plus Server) 4.1 Users Guide Description of APS Hardware The APS hardware platform consists of Sun systems for one or more APS machines and one Sun system for the ERP machine. Please refer to the configuration note for this release for more details, including product ID numbers.
  • Page 37: Erp System Hardware Configuration

    Other Components in the APS System Storage Components ERP System ERP is available for two sizes of APS sites: Hardware Configuration The ERP machine is based on a single 300-MHz single CPU. The ERP system is connected by a LAN to the APS. ERP uses Solaris 2.6. 101-1830-001 Issue 1.0 One fast-wide, 68-68 pin SCSI cable with power cord...
  • Page 38: Hardware Base For Small Erp Configuration

    APS (Application Plus Server) 4.1 Users Guide Hardware Base for The small ERP configuration uses a Sun Ultra Enterprise 5, Model 2300, Small ERP 300 MHz Server with: Configuration Circuit Cards in an ERP System Other Components in the ERP System Storage Components Hardware Base for Hardware needed for the large configuration of ERP differs from the...
  • Page 39: Description Of Aps Software

    Description of APS Software An APS site requires software for the APS, provided by Lucent Technologies, and software for the Sierra/CA VPM. To process reports, an ERP machine loaded with ERP software is necessary. APS Software APS uses the following software components and provides them as part of the APS 4.1 package.
  • Page 40: Vpm Software

    APS (Application Plus Server) 4.1 Users Guide VPM Software License Information APS software requires a license to operate. The license is controlled by means of a license key. APS performs validation and authentication of the license key when it first starts up. Please see Chapter 2, ‘‘Installing APS,’’for further details.
  • Page 41: Installing Aps

    This chapter contains information about installing the APS 4.1 platform software and the Solaris 2.6 operating system. Installation instructions found in this section discuss: Getting Started Preparing the APS platform for use consists of the following steps: 101-1830-001 Issue 1.0 Getting Started Routine Operations Required Items and Information...
  • Page 42: Routine Operations

    APS (Application Plus Server) 4.1 Users Guide 5. Connect to the Sierra/CA. 6. Connect to the messaging center if necessary. 7. Connect to the SS7 network. 8. Place test calls 9. Test report generation using the application. 10. Soak the installation. After these steps have been completed satisfactorily, your site can begin live operation.
  • Page 43: Required Items And Information

    Required Items and Information Please have the following items and information available to complete the installation procedures. If you do not have the other information, enter place-holder data when you are prompted for such things as IP address and licensing information. Apply the correct data when they become available.
  • Page 44 APS (Application Plus Server) 4.1 Users Guide Netmask for TCP/IP Netmask for PPP Modem, dial-up line, and remote access procedures for remote support personnel so they may dial in to the site 101-1830-001 Issue 1.0...
  • Page 45: Installing New Hardware Systems

    Installing New Hardware Systems New systems require specific hardware to be installed and wired. Once the hardware is set up, you are ready to install the software. Assembling the Sun Hardware Assemble the major hardware components of the APS platform: Setting Up APS Hardware The first step in installing a new system is to assemble the hardware.
  • Page 46: Installing Circuit Cards

    APS (Application Plus Server) 4.1 Users Guide Installing Circuit Check the Sun system to be loaded with APS to make sure that cards are Cards in the correct slots. The correct arrangement of cards in the Sun system is shown in Figure 4. Figure 4.
  • Page 47: Powering Up The A1000

    There should be two disks installed. Figure 5 shows the arrangement of disks in the A1000 disk array. Install the disks as shown. Figure 5. Arrangement of Drives in the Sun A1000 Disk Array Powering Up the Use this procedure to power up the A1000. The A1000, tape drive, and A1000 Sun system must be powered up in a specific sequence, otherwise the system may be unreliable.
  • Page 48: Assembling The Erp Hardware

    APS (Application Plus Server) 4.1 Users Guide 3. Set your screen to match Figure 6. Figure 6. Example Sun Admin Tool Window Assembling the ERP Hardware If you have an ERP system at your site, see ‘‘Assembling the ERP Hardware’’ on page 352. Cabling the ERP System If you have an ERP system at your site, see ‘‘Cabling the ERP System’’...
  • Page 49 Installing APS 5. Enter the IP address of the LAN switch. 6. Enter the IP address of the LAN default gateway. 7. Enter the netmask. 8. Connect the local LAN to the APS’s LAN switch in slot 1. Use the LAN crossover cable (flipped). 9.
  • Page 50: Installing The Software

    APS (Application Plus Server) 4.1 Users Guide Installing the Software Installing the APS Tape This procedure installs a full image of the APS software. Expect this procedure to take about 1 hour and 15 minutes. Note: If you need to restore a Sun system after maintenance such as replacing a hard drive, do not use this procedure.
  • Page 51 6. Choose 7. From the # prompt, enter tar xvf /dev/rmt/0 8. Enter ./install__fs 9. Answer the prompt with the letter y or n. ____________________________________________________________________________ Please Enter the operation to be performed: ____________________________________________________________________________ 10. Answer the prompt “Please enter the operation to be performed.” 11.
  • Page 52 APS (Application Plus Server) 4.1 Users Guide 17. Enter the new machine name. Confirm by entering y. 18. Enter the IP address. Confirm by entering y. 19. Enter the netmask address. Confirm by entering y. 20. Enter the LAN gateway name. Confirm by entering y. 21.
  • Page 53 31. Enter the Informix DBServer key number. 32. Enter the ESQL (embedded system query language) serial 33. Enter the ESQL key number. 34. If you are using X.25 connectivity to the Sierra/CA: 101-1830-001 Issue 1.0 This is available on the Informix software package. number.
  • Page 54: Installing The Erp Tape

    APS (Application Plus Server) 4.1 Users Guide Installing the ERP Tape If your site uses an ERP system, see ‘‘Installing and Administering ERP’’ on page 354. Installing the Application Every application needs specific administration and setup performed. See the documentation that came with your application for these procedures. When you finish installing the application, return to this point and continue.
  • Page 55: Cabling And Configuring Tcp/Ip From The Sierra/Ca Side

    If your site uses TCP/IP protocol to the Sierra/CA, perform these two procedures: If your site uses an X.25 protocol to the Sierra/CA perform these two procedures: Cabling and Use this procedure to set up the TCP/IP connection on the Sierra/CA. Configuring TCP/IP Before beginning, contact the LAN administrator at the site and find out from the Sierra/CA...
  • Page 56 APS (Application Plus Server) 4.1 Users Guide _________________________________________________________ _____________________________________________________________________ 3. From menu 21, choose item 1 to set the STORED IP address and Change the IP and netmask in the rightmost column. These changes will take effect the after the network access card in the Sierra/CA is uploaded or the Sierra/CA is rebooted.
  • Page 57 _____________________________________________________________________ This Server’s Ethernet Address:... 00:C0:94:20:0A:F9 This Server’s IP Address:... 172.16.2.83 IP Net Mask:... 255.255.0.0 Broadcast Address:... 999.16.255.255 Gateway IP Address:... 999.16.0.1 _____________________________________________________________________ 5. From menu 21, choose item 5. _____________________________________________________________________ Host Name Sierra_1 Sierra_2 swaps _____________________________________________________________________ 6. From menu 21, choose item 6. _____________________________________________________________________ Host Name Sierra_1...
  • Page 58: Cabling And Configuring Tcp/Ip

    APS (Application Plus Server) 4.1 Users Guide Cabling and Using this procedure from the APS system, set up the TCP/IP connection. Configuring TCP/IP Perform this procedure for every APS system at the site. from the APS Side Perform this procedure after loading the APS tape and after installing the ICC application.
  • Page 59 Figure 7. Sierra/CA Configuration for a Remotely Located Sierra/CA ____________________________________________________________________________ Menu 18 - X.25 Interface Management Physical Interface Number: 0 Network Type: 1 - Telnet Interface Terminal Type: 1 - DCE - Level 1 Physical - Interface Speed: O - 19200bps Clocking Source: 2 - External - Level 2 Frame - Frame Window Size: 7...
  • Page 60 APS (Application Plus Server) 4.1 Users Guide 7. Connect the SME (synchronous modem eliminator) connector. Figure 9. Cable Connections for an HSI Connection Figure 10. Cable Connections for a Direct Connection The SME connector is labeled VPS on one end and Data Mod on the other end.
  • Page 61: Cabling And Configuring X.25 Links On The Aps Side

    Cabling and This section outlines the configuration procedure for X.25 protocol stack. Configuring It contains detailed step-by-step instructions along with screen examples X.25 Links on the showing configuration settings. APS Side 1. Decide how many links you will be configuring. The first link Table 1.
  • Page 62: Starting The X.25 Tool

    APS (Application Plus Server) 4.1 Users Guide Starting the 2. Log in as super user. Enter X.25 Tool 3. Enter Figure 11. X25tool 9.1, Main Menu 4. From the main menu choose and enter the correct password. x25tool& The X.25 tool main menu displays, as shown in Figure 11. Note that the first link, link 0, has already been configured.
  • Page 63 Installing APS A list of link types displays as shown in Figure 12. Figure 12. Link Types 5. Click on link type dte84. An example Link Editor window for an HSI connection displays as in Figure 13. A Link Editor window for a direct connection shows in Figure 14.
  • Page 64: Using The Link Editor

    APS (Application Plus Server) 4.1 Users Guide Using the Link Editor Figure 13. Link Editor Window for a Co-located Sierra/CA Use the Link Editor to set up the subsequent links. Figure 13 shows the correct settings for the second link, link 1, of an HSI connection.
  • Page 65 Use Figure 14 to enter settings for a Sierra/CA not in the same facility as the APS system. Figure 14. Link Editor Window for a Remotely-located Sierra/CA 6. When finished, click Apply. 101-1830-001 Issue 1.0 When you click Apply, the buttons you need to use on the right become available.
  • Page 66: Lapb/Wan Parameters

    APS (Application Plus Server) 4.1 Users Guide LAPB/WAN 7. From the Link Editor window, choose LAPB/WAN Parameters. Parameters Figure 15. LAPB and WAN Parameters 8. Click OK. This window needs no modifications. The LAPB/WAN Parameters window displays, as shown in Figure 15.
  • Page 67: Addressing

    Installing APS Addressing 9. From the Link Editor window click Addressing. 10. The Addressing Parameters window displays, as shown in Figure 16. Figure 16. Addressing Parameters Window 11. Click OK. This window needs no modifications. 101-1830-001 Issue 1.0...
  • Page 68: Cug And Facilities

    APS (Application Plus Server) 4.1 Users Guide CUG and Facilities 12. From the Link Editor window, click CUG and Facilities. Figure 17. CUG and Facilities Parameters Window 13. Click OK. This window needs no modification. The CUG (closed user group) and Facilities window displays, as shown in Figure 17.
  • Page 69: Link Modes

    Link Modes 14. From the Link Editor window, click Link Modes. Figure 18. Link Mode Parameters Window 15. Click OK. This window needs no modification. 101-1830-001 Issue 1.0 The Link Mode Parameters window displays, as shown in Figure 18. Installing APS...
  • Page 70: Throughput

    APS (Application Plus Server) 4.1 Users Guide Throughput 16. From the Link Editor window, click Throughput. Figure 19. Throughput Window 17. Change your screen to match the values in Figure 19. 18. Click Apply. 19. Click OK. The Throughput window displays, as shown in Figure 19. 101-1830-001 Issue 1.0...
  • Page 71: Timers And Counters

    Timers and 20. From the Link Editor window, click Timers and Counters. Counters Figure 20. Timers and Counters Window 21. Click OK. This window needs no modification. 101-1830-001 Issue 1.0 The Timers and Counters window displays, as in Figure 20. Installing APS...
  • Page 72: Special

    APS (Application Plus Server) 4.1 Users Guide Special 22. From the Link Editor, click Special. Figure 21. Special Parameters Window 23. Click OK. This window needs no modification. The Special Parameters window displays, as in Figure 21. 101-1830-001 Issue 1.0...
  • Page 73: X32 Authentication

    X32 Authentication 24. From the Link Editor, click X32 Authorization. Figure 22. Special Parameters Window 25. Click OK. This window needs no modification. 26. From the Link Editor, click OK to leave the Link Editor window. 101-1830-001 Issue 1.0 The X32 Authorization window displays, as in Figure 22. Installing APS...
  • Page 74: Routing

    APS (Application Plus Server) 4.1 Users Guide Routing 27. From the X25 tool main menu choose Figure 23. Routing Parameters Window 28. Click Add, and then click Top. 29. Change your screen to match the values shown in Figure 23, 30.
  • Page 75 Installing APS Your new link has been correctly configured, as shown in Figure 24. Figure 24. New Link Configured Configure the rest of the X.25 links at your site. Repeat steps 4 through 30 to configure the rest of the links. 101-1830-001 Issue 1.0...
  • Page 76: Modifying The Profiles

    APS (Application Plus Server) 4.1 Users Guide Modifying the Profiles Open the APS interface to modify the profiles to use the correct connectivity. Modify profiles to use a particular server or protocol. The profiles you must modify and how to change them are specified in the application’s users guide.
  • Page 77: Software Upgrades

    Software Upgrades The procedures in this section upgrade your APS system to: This section does not upgrade the Sierra/CA VPM (voice processing module) in any way. Upgrading from APS 3.x to APS 4.1 Upgrading from APS 3.x to APS 4.1 is a custom task. Upgrade teams from Lucent Technologies will accomplish the upgrade for you.
  • Page 78 APS (Application Plus Server) 4.1 Users Guide Figure 25 shows the disks that occupy them the MultiPack disk array. Install disks as shown. Figure 25. Arrangement of Drives in the MultiPack Disk Array Figure 26 shows the arrangement of disks in the A1000 disk array. Install the disks as shown.
  • Page 79: Procedure To Upgrade To Aps 4.1

    Procedure to Expect this procedure to take about 2 hours. Upgrade to APS 4.1 Use this procedure to upgrade your system to APS 4.1. Upgrading from 4GB to 9GB Drives If you are moving to either internal or external 9 gigabyte hard drives, do a full install at this point as described in ‘‘Installing the APS Tape’’...
  • Page 80 APS (Application Plus Server) 4.1 Users Guide 5. Save any other applications that may be present on the APS 6. Gather the information needed by the installation scripts setup 7. Insert the APS 4.1 tape into the drive. 8. Log in as root. 9.
  • Page 81 18. Open a terminal window by selecting Program and then 19. In a terminal window enter 20. Enter the Informix DBServer serial number. 21. Enter the Informix DBServer key number. 22. Enter the ESQL (embedded system query language) serial 23. Enter the ESQL key number. 24.
  • Page 82 APS (Application Plus Server) 4.1 Users Guide 25. After the APS portion of the upgrade, if appropriate, install the 26. Copy in the data that was saved as outlined in steps 3, 4, and 5. 27. Configure the system heartbeat file. See ‘‘Configuring the System 28.
  • Page 83: Menu Interface

    This chapter describes the APS (Application Plus Server) 4.1 menu interface. It discusses each menu and menu item. To reference procedures for using the interface to perform specific tasks, see Chapter 4, ‘‘Procedures.’’ Definitions The list below will familiarize you with the terms used in this chapter. Term Application session Application...
  • Page 84: Aps Menu Interface

    APS (Application Plus Server) 4.1 Users Guide Term APS platform software Functional wizard Profile Script Script group Script session Sierra/CA wizard APS Menu Interface The APS interface is a graphical user interface that enables the programmer or system administrator to operate, administer, maintain and provision the system.
  • Page 85: Main Menu

    Main Menu The APS interface contains five drop-down menus: Menu Script View System Utility Database Figure 27 shows the GUI of the APS main menu. Figure 27. APS GUI, Main Menu 101-1830-001 Issue 1.0 Purpose Use this menu to develop and manage scripts. Use this menu to view log files.
  • Page 86: Script Menu

    APS (Application Plus Server) 4.1 Users Guide Script Menu The script menu contains items for programming scripts, deleting old scripts, and printing scripts. Figure 28 shows the Script menu and its menu items. The following list describes the purpose of each menu item. Menu Item Open Delete...
  • Page 87: Print

    Print Use the Print item in the Script menu to print scripts. A script is composed of a collection of functional wizards. Each functional wizard acts as a logical function in the flow of the script. To examine the logic flow, examine the script. Quit This item closes the APS interface window but allows the scripts and applications to continue running.
  • Page 88: View Menu

    APS (Application Plus Server) 4.1 Users Guide View Menu The View utility provides information useful for system maintenance, troubleshooting, and general status checks of the APS system. The following list describes the purpose of each menu item. Menu Item Gen Log Debug Log Script Information Status Log...
  • Page 89: Debug Log

    Debug Log An application is built by connecting one or more scripts. The functional wizards that comprise the scripts determine the call flow. The Debug log file provides a trace of the call flow for applications. Script Information Log The Script Information log file contains the comment lines of a script. From the View menu select Script Information to display the Script Information log on the screen.
  • Page 90: System Menu

    APS (Application Plus Server) 4.1 Users Guide System Menu The following list describes the purpose of each menu item in the System menu. Menu Item Script Configuration Scripts Control Manager Configurable Parameters Runtime Status Application Manager Logger Manager Script Tracer RMPP Manager SS7 Gateway Figure 30 shows the System menu.
  • Page 91: Script Configuration

    Script Configuration Use the menu item Script Configuration to delete, create, rename, and manage profiles. Before you run an application, each script that comprises it must have at least one profile. The profile must correspond to the OCL configuration of a standalone Sierra/CA or a Sierra/CA cluster. The profile the defines the Sierra/CA’s X.25 address or TCP/IP address.
  • Page 92: Parts Of The Profile Window

    APS (Application Plus Server) 4.1 Users Guide Figure 31 shows a Profile window with all server options disabled. Figure 31. Example Script Profile Window Parts of the Profile Table 4 describes each element in he Profile window. This example Window discussed a current profile, one that is already defined, not how to define Table 4.
  • Page 93 Table 4. Parts of the Profile Window (Continued) Field Network Port Number TCP/IP Enable Logger Host Name Logger Port Number Password Application ID Encryption ID Version ID Start by...Options Number of sessions Max allowed Sessions Server/Protocol enable options Script-type option Auto Restart Type 40 mailbox Buttons...
  • Page 94: Server/Protocol Enable Options

    APS (Application Plus Server) 4.1 Users Guide Server/Protocol When assigning a profile to a script, you must choose one of the Enable Options Server/Protocol Enable buttons. What button you choose depends on the script this profile influences. For example, if the script accesses an OSA server, choose the OSA Server Enable button.
  • Page 95: Tcp/Ip Enable Option

    TCP/IP Enable When selected, the TCP/IP Enable option lets the application use TCP/IP Option protocol instead of X.25. Figure 32 shows a profile window with TCP/IP Enable selected and its options. Figure 32. Profile Window with TCP/IP Enable Chose If TCP/IP Enable is selected, the following options display: SNDBUF - sets the send buffer size (in bytes).
  • Page 96: Smpp Options

    APS (Application Plus Server) 4.1 Users Guide SMPP Options The SMPP (Short Message Peer-to-Peer Protocol) Enable option enables the script to open the connection to specific customer. Figure 33 shows an example of this profile with SMPP selected. Figure 33. Profile Window with SMPP Options When the SMPP Enable option is selected, the following options display on the Profile window.
  • Page 97: Osa Server Options

    OSA Server Options Choose this option if the script uses OSA (Octel System Administration) server wizards. OSA assigns the following parameters: Figure 34 shows an example of an OSA profile window. Figure 34. OSA Enable Options 101-1830-001 Issue 1.0 OSA SERVER HOSTNAME - Name of the host running OSA server.
  • Page 98: Hlr Server Options

    APS (Application Plus Server) 4.1 Users Guide HLR Server Options APS 4.1 does not support this Protocol/ Server Enable option because it no longer supports connections to the HLR through a Microlegend. 101-1830-001 Issue 1.0...
  • Page 99: Ss7 Enable Options

    SS7 Enable Options Choose the SS7 Enable option when the script uses a NewNet card and IS-41 messages. IS-41 messages sit on the SS7 protocol. Figure 35 shows the SS7 Enable options. The following parameters are assigned by the SS7 protocol: Figure 35.
  • Page 100: Disable Option

    APS (Application Plus Server) 4.1 Users Guide Disable Option Use the Disable option for scripts that use none of the other Server/Protocol enable options. Figure 36 shows an example of a profile with no servers or protocols enabled. Note that no additional options are available with Disable chosen.
  • Page 101: Auto Restart Option

    Auto Restart Option Selecting Enable Auto Restart allows a script to restart automatically if the script terminates inappropriately. Disabling Auto Restart means that the script must be restarted manually. Type 40 Mailbox The Type 40 mailbox number is administered on the Sierra/CA, and Number reflected here.
  • Page 102: Buttons

    APS (Application Plus Server) 4.1 Users Guide Buttons Once you have displayed the Profile window, use the buttons at the bottom to manage the script. Table 6 describes the buttons at the bottom of the Profile window. To monitor your script sessions expertly, see ‘‘Monitoring a Script Session’’...
  • Page 103: Scripts Control Manager

    Scripts Control Manager The Scripts Control Manager lets you collect scripts and profiles into a list so that you may start and stop them with one operation rather than separately. Use this menu item to collect scripts and their profiles into a group, and to remove scripts and profiles from a group.
  • Page 104: Application Manager

    APS (Application Plus Server) 4.1 Users Guide Application Manager Use this menu item to: The application manager monitors applications and scripts, and so fundamentally monitors virtual circuits. If one of the virtual circuits shuts down, the application manager restarts it automatically. The application manager should always be running.
  • Page 105 In order to reach the SS7 gateway, APS needs the following information: These data are configured and defined in the aps.cfg SS7 configuration file. Under the System menu, SS7 Gateway item, there are two options: Before APS can connect to the SS7 gateway, it must have the above network information as well as the underlying SS7 stack.
  • Page 106: Utility Menu

    APS (Application Plus Server) 4.1 Users Guide Utility Menu The following list describes the purpose of each menu item. Menu Item Export Import Wizard Backup Printer Configuration System Performance Cron Tasks License Application Figure 37 shows an example of the Utility menu. Figure 37.
  • Page 107: Import

    Import Use this menu item to copy scripts from a diskette to the hard drive of the APS system. Wizard Backup Use this menu item to copy APS files and data to a target peripheral. Printer Configuration The Utility menu of the APS interface provides a printer configuration item to specify the name of the printer you want to use.
  • Page 108: Cron Tasks

    APS (Application Plus Server) 4.1 Users Guide Cron Tasks This menu item: Cron tasks run in the background. Cron tasks perform important functions such as creating log files for call backup data. The Cron Tasks Utility monitors the cron task’s processing status. License You must register your APS software and obtain a license for the number of virtual circuits that you require.
  • Page 109: Application

    The license certificate that comes with the APS software contains these data: Application This menu provides access to all the installed applications. This menu contains a side menu that lists each application loaded on top of APS 4.1, along with their version numbers. You can access all applications on the APS platform from this main menu item.
  • Page 110: Database Menu

    APS (Application Plus Server) 4.1 Users Guide Database Menu The following list describes the purpose of each menu item. Menu Item Dynamic SQL Select SQL The Database menu provides utilities to manage database tables. Before using these items, the database must be open. The Database menu is shown in Figure 40.
  • Page 111: Procedures

    This chapter contains frequently used procedures. Material in this section is arranged functionally into the following categories: 101-1830-001 Issue 1.0 APS System-wide Tasks Application-specific Tasks Working with Scripts, Script Groups, and Applications Working with Profiles Importing and Exporting Data Backing Up Data Registration and Licensing Tasks SS7 Gateway Tasks...
  • Page 112: Aps System-Wide Tasks

    APS (Application Plus Server) 4.1 Users Guide APS System-wide Tasks System-wide tasks affect the APS 4.1 system as a whole. This section describes the following system-wide tasks: Starting the APS Interface Use this procedure to log in to the APS interface from a command window: 1.
  • Page 113: Quitting The Aps Interface

    Note: Exiting the APS interface by closing the APS console shell shuts down all scripts and applications. If selecting Quit fails to close the interface gracefully, only then exit the APS console shell. Start another APS shell and restart applications as soon as possible. Quitting the APS To close the APS interface window: Interface...
  • Page 114: Setting The Status Log File Size

    APS (Application Plus Server) 4.1 Users Guide Setting the Status The size of the status log file is set to 20,000 entries at installation. There Log File Size should be no reason to change it. However, if you find it necessary to reset the file size of the status log file: 1.
  • Page 115: Monitoring System Performance

    3. Enter 4. Choose 5. Check link status again before exiting. Monitoring System Use this procedure to measure how well the Sun system is performing Performance with respect to disk, memory, and processing. To start the APS system performance monitor: 1.
  • Page 116: Replacing A Hard Disk

    APS (Application Plus Server) 4.1 Users Guide Replacing a Hard Use this procedure to replace a failed hard disk in either the Sun system Disk chassis, MultiPack or A1000 array. All drives in an A1000 should be of the same size. 1.
  • Page 117: Application-Specific Tasks

    Application-specific Tasks Application-specific tasks concern the application loaded on top of the APS platform software. Refer to your application’s user guide for specific instruction. 101-1830-001 Issue 1.0 Procedures...
  • Page 118: Working With Scripts, Script Groups

    APS (Application Plus Server) 4.1 Users Guide Working with Scripts, Script Groups, and Applications The many tasks related to scripts are divided into two groups: Managing Scripts, Script Groups, and Applications Working with scripts includes the following tasks: ‘‘Managing Scripts, Script Groups, and Applications’’ on page ‘‘Monitoring Scripts, Script Groups, and Applications’’...
  • Page 119: Creating Script Groups Or Applications

    Creating Script Use this procedure to collect scripts and their associated profiles in a Groups or group. After they are grouped, you can start and stop these scripts and Applications profiles simultaneously. 1. From the APS main menu choose Figure 42. Script Control Manager Window 2.
  • Page 120 APS (Application Plus Server) 4.1 Users Guide Figure 43. Scripts Control Manager Window 3. In the Script Name field, type in a known script name. 4. In the Profile Name field, type in a known profile name. 5. Click Add. 6.
  • Page 121: Starting An Application Automatically

    Starting an After a script starts the very first time, it is “registered” by the application Application manager and will be automatically restarted each time the application Automatically manager starts, if the Auto Restart option is enabled in the profile. Use this procedure to make sure applications start automatically.
  • Page 122: Starting A Script Group Or Application Manually

    APS (Application Plus Server) 4.1 Users Guide Starting a Script Use this procedure to start and stop script groups or applications. Group or 1. On a SunOS command line enter Application Manually 2. From the APS main menu choose 3. In the Group Name field, enter the name of the application to 4.
  • Page 123: Starting A Single Script

    4. Click Start to display the next window. 5. Click Stop to stop all the scripts within the group. 6. Click Done to exit If this procedure does not stop the script group, see ‘‘Shutting Down a Script Group’’ on page 126. To fully stop the APS system, stop scripts in the proper order.
  • Page 124: Stopping A Single Script

    APS (Application Plus Server) 4.1 Users Guide Stopping a Single Use this procedure to stop one script: Script 1. On a SunOS command line enter 2. From the APS main menu choose 3. Choose the desired script. 4. Choose 5. Choose the appropriate profile. 6.
  • Page 125: Deleting A Script From A Script Group

    Deleting a Script To delete a script and its associated profiles from the group: from a Script Group 1. From the APS main menu choose 2. Type in or click on the desired group name. 3. Click Start. 4. Enter the script name and the profile name. 5.
  • Page 126: Shutting Down All Active Sessions

    APS (Application Plus Server) 4.1 Users Guide Shutting Down All Use this procedure to force all script sessions to stop running when they Active Sessions cannot be stopped any other way. Note: 1. From the APS main menu choose 2. Choose a script. 3.
  • Page 127: Monitoring Scripts, Script Groups, And Applications

    Monitoring Scripts, Script Groups, and Applications There are several ways that you can monitor the processing and status of scripts. The following procedures are available to monitor scripts and applications: Creating, Opening, Developing scripts is not the subject of this manual. If you want to create and Deleting Scripts scripts, open and modify existing scripts, or delete scripts, please see: 101-1830-001...
  • Page 128: Starting Scripts In Test Mode

    APS (Application Plus Server) 4.1 Users Guide Starting Scripts in To run a script in test mode: Test Mode 1. From the APS main menu choose 2. Choose the desired script. 3. Choose 4. Choose the appropriate profile. 5. Click Test. 6.
  • Page 129: Monitoring A Script Session

    Monitoring a Script Monitoring a script session can be done with any one of the following Session procedures. See ‘‘Checking an Application’s Runtime Status by Process Level’’ on page 131. See ‘‘Checking an Application’s Runtime Status by Usage Level’’ on page 132.
  • Page 130 APS (Application Plus Server) 4.1 Users Guide Figure 44. Application Manager Monitor List 2. Click Run to display scripts that are currently active. Table 8. Columns in the Application Manger Monitor List Window Columns Program Key No of Instances Mode 3.
  • Page 131: By Process Level

    Checking an This procedure checks the run time status of a script by examining Application’s process ID information: Runtime Status 1. From the APS main menu choose by Process Level 2. Choose the script you want to assess. 3. Choose 4.
  • Page 132: Checking An Application's Runtime Status

    APS (Application Plus Server) 4.1 Users Guide Checking an This procedure checks the runtime status of an application by examining Application’s session usage. Runtime Status 1. From the APS main menu choose by Usage Level 2. Choose the script to assess. 3.
  • Page 133: Debugging Scripts

    Table 9 describes the fields in the Runtime Status window. Table 9. Fields in the Runtime Status Window Field Number of Active Sessions Number of Busy Sessions Number of Idle Sessions Number of Done Sessions Number of Error Sessions Debugging Scripts Information on debugging scripts is included in the Wizard Developer’s Guide from Innovative Systems Services, Inc.
  • Page 134: Working With Profiles

    APS (Application Plus Server) 4.1 Users Guide Working with Profiles This section describes tasks related to profiles: Viewing the Profile You can perform most script administration using the Profile window. Window These steps show you how to view the profile of a script. 1.
  • Page 135: Modifying Profiles

    4. Choose the profile name. 5. In the New Profile Name field, enter the new name for the 6. Click Rename. 7. Click OK. Modifying Profiles This procedure shows you , in a general manner, how to change a profile for a script.
  • Page 136: Creating New Profiles

    APS (Application Plus Server) 4.1 Users Guide Creating New This procedure shows you , in a general manner, how to create a profile Profiles for a script. Profiles are specific to an application . See the application document to set up profiles specifically. To create a profile for a script: 1.
  • Page 137 7. Depending on the purpose of the script, enable the corresponding 8. Click Save to save the profile. 9. Click Done to exit. 101-1830-001 Issue 1.0 server option and fill in the parameters as necessary. See your application’s users guide for complete discussion on how to define profiles for a specific application.
  • Page 138: Importing And Exporting Data

    APS (Application Plus Server) 4.1 Users Guide Importing and Exporting Data There are three procedures available to import and export data to and from the APS software: Importing This procedure imports application-related utilities. After they are Application-specific imported, these utilities display under the View menu’s Application item Utilities or under the Utility menu’s Application item.
  • Page 139: Copying Scripts To A Diskette

    4. Click Cancel to exit. 5. Remove the diskette. Copying Scripts to a The Export utility copies scripts to a diskette or other target. Use this Diskette utility to back up scripts to a diskette. To copy a script to a diskette: 1.
  • Page 140: Backing Up Data

    APS (Application Plus Server) 4.1 Users Guide Backing Up Data The APS platform provides methods for regularly scheduled backups and ad hoc backups. This section describes these methods. Backing Up APS The APS interface provides a menu item that lets you perform a manual Files backup of APS data at any time.
  • Page 141: Registration And Licensing Tasks

    Registration and Licensing Tasks Registration and proper licensing of your software are essential tasks before the software will run properly. Use these two procedures to register and check the licensing of your APS installation: Registering APS Registering the APS software is mandatory. The APS software will not Software run without registration.
  • Page 142: Checking The License

    APS (Application Plus Server) 4.1 Users Guide 5. In the Number of lines for the system field, type 6. In the Number of VPM connected field, enter how many 7. In the Customer Name field, type your company’s name. 8. In the Expiration Time for Demo Licenses field, 9.
  • Page 143 Figure 51. License Check Screen 2. Read this screen and verify that all the information is correct. 3. If you need to change any of the information, see ‘‘Registering 4. Click Run to update the ini file. 5. Click Done to exit 101-1830-001 Issue 1.0 APS Software’’...
  • Page 144: Ss7 Gateway Tasks

    APS (Application Plus Server) 4.1 Users Guide SS7 Gateway Tasks Use these tasks to configure, start, and monitor the SS7 gateway: Please be aware that small changes to the SS7 configuration can have far reaching effects. Also, not having an SS7 connection to HLR can result in no production.
  • Page 145: Changing An Ss7 Configuration File

    Changing an SS7 While it’s unlikely that you will need to create new SS7 configuration Configuration File files, there may be situations where you need to change one. For example, if you need to add destination point codes to the HLR_profile table for your application, you will need to edit the SS7 configuration file.
  • Page 146: Configuring The Ss7 Gateway

    APS (Application Plus Server) 4.1 Users Guide Configuring the SS7 When an APS machine is booted, connections to the SS7 gateway are Gateway made automatically using the configuration file aps.cfg. To load a different configuration file: 1. From the APS main menu choose Figure 52.
  • Page 147: Starting And Stopping The Ss7 Gateway

    Starting and When an APS machine is booted, connections to the SS7 gateway are Stopping the SS7 started automatically. There may be instances when you need to stop and Gateway restart the SS7 gateway manually. The SS7 gateway must be running before communication with HLR via the NewNet card can proceed.
  • Page 148: Administering The Signaling Point Code

    APS (Application Plus Server) 4.1 Users Guide Administering the The signaling point code (SPC) may also be referred to as the Network Signaling Point Indicator or Type or Signaling Point. The SPC is an address on the SS7 Code network. This point code is found in aps.cfg and must match here. Use this procedure to administer the signaling point code.
  • Page 149 Table 10. Fields in the SS7 Gateway Window Field Status Port Number Point Code <network number>-<cluster number>-<member number> (each separated by hyphen). Subsystem No Dev No SP No SAN No 5. Click Start to begin communicating with this protocol, 101-1830-001 Issue 1.0 Description Shows the current status of SS7 Gateway...
  • Page 150: Monitoring Ss7 Gateway

    APS (Application Plus Server) 4.1 Users Guide Monitoring SS7 Use the SS7 tool to Gateway The executable file is located in /export/home0/issg/issg_main/issg_ lib/libss7tools and the file name is ss7tool. A flag specifies what kind of information the user is interested in. A readme file is provided in the same directory and is named ss7tool.readme.
  • Page 151: Displaying The State Of The Ss7 Links

    Figure 54 shows an example of the output of the ss7tool command with the listlinks argument. Figure 54. Example ss7tool Output ____________________________________________________________________________ ss7tool listlinks lset link port prio admst oprst mcnt ___________________________________________________________________________ Displaying the State Use the SS7 tool to display the state of the SS7 links. of the SS7 Links 1.
  • Page 152 APS (Application Plus Server) 4.1 Users Guide 2. Enter these two commands: 3. Enter ? for help. 4. Enter 5. Enter selectinfo to display the current selection of device number, 6. Enter q782 7. Enter ? for to display the mtp command menu. 8.
  • Page 153 Table 12. jtest General Commands (Continued) Command display (cont.) echo help open 101-1830-001 Issue 1.0 Description display [con=<n/i/o>] [log=<n/i/o>] The con argument and options specify the options for the console. The log argument and options specify the options for the log file. To use a log file, it must have been specified when jtest was started.
  • Page 154 APS (Application Plus Server) 4.1 Users Guide Table 12. jtest General Commands (Continued) Command select selectinfo Description Specifies the logical device number, dev#, of the Connect7 card for the jtest session. The syntax of this command is: dev dev# If no argument is given, the current dev# is displayed.
  • Page 155 Table 12. jtest General Commands (Continued) Command pause q782 quit sleep stopbatch 101-1830-001 Issue 1.0 Description Used in script files to suspend execution of the script file. Text, provided in quotes, can be displayed to the console. Execution is resumed by pressing ENTER key. Terminate the script file by pressing ESC.
  • Page 156: Application Manager Tasks

    APS (Application Plus Server) 4.1 Users Guide Application Manager Tasks The application manager is an integral part of APS processing. Use these tasks to start and monitor the application manager: Starting and The application manager monitors applications and scripts, that is, virtual Stopping the circuits.
  • Page 157 2. Click Start to activate the application manager as shown in Figure 57. Application manager has been started 3. Click Stop to turn off the application manager. 4. Click Done to exit. Note: 101-1830-001 Issue 1.0 Figure 57. The application manager’s status reflects the current status of the application manager.
  • Page 158: Runtime Status

    APS (Application Plus Server) 4.1 Users Guide Checking the Use this procedure to see if the application manager is running or not. Application 1. From the APS main menu choose Manager’s Runtime Status Figure 58. Application Manager Process Status window Table 13.
  • Page 159: Logger Manager Tasks

    Logger Manager Tasks The logger manager is essential for monitoring alarms in the APS system. Use these procedures to work with the logger manager process: Starting and The logger manager is always up and running so all errors and events can Stopping the Logger be written to the status log file.
  • Page 160 APS (Application Plus Server) 4.1 Users Guide 2. If the logger manager is not running, Figure 60 displays. Figure 60. Logger Manager Not Running 3. If the logger manager is running, Figure 61 displays. Figure 61. Logger Manager Running 101-1830-001 Issue 1.0...
  • Page 161: Cron Tasks

    Cron Tasks Cron tasks determine when processes such as reports and backups should occur. Refer to these procedures if you need to manage cron tasks: Starting and Use this procedure to start or stop all cron task. Stopping Cron To start cron tasks: Tasks 1.
  • Page 162 APS (Application Plus Server) 4.1 Users Guide 4. When finished editing, a. Press ESC b. Enter :wq to save your edit and exits the screen. Enter :q! to cancel your changes. 101-1830-001 Issue 1.0...
  • Page 163: Monitoring Cron Task Status

    Monitoring Cron Use this procedure to find out what cron tasks are scheduled to be run by Task Status the cron process. This procedure is helpful when troubleshooting cron problems. To check the cron task status: 1. From the APS main menu choose Figure 62.
  • Page 164: Using Sql Commands

    APS (Application Plus Server) 4.1 Users Guide Using SQL Commands APS provides access to the Informix database through the APS menu interface. In this interface, you type in SQL commands. You may use these two procedures to work with the database tables if it becomes necessary to do so: Specific examples of SQL commands are provided in the application documents.
  • Page 165: Executing Sql Queries With Output

    3. Click Cancel or Done to exit. Executing SQL Use this procedure for making queries of the database. Use this procedure Queries With Output for database commands that generate output. To make database queries: 1. From the APS main menu choose 101-1830-001 Issue 1.0 see Informix Error Messages.
  • Page 166 APS (Application Plus Server) 4.1 Users Guide Figure 64. Select All SQL window 2. Type in a valid SQL query. 3. Click Done to exit or Cancel to abandon your query. The Select All SQL window displays as shown in Figure 64. The results of your query display in the bottom part of the window.
  • Page 167: Printing

    Printing The APS platform provides access to printing capabilities. These two procedures describe how to configure and use a printer: Configuring Printers To set your printer configuration: 1. From the APS main menu choose Figure 65. Printer Configuration Window 2. In the Print Command field, type the corresponding command 3.
  • Page 168: Printing A Script

    APS (Application Plus Server) 4.1 Users Guide Printing a Script The Print item in the Script menu enables you to print a script on a network or local printer if one is available. Note: To print a script: 1. From the APS main menu choose 2.
  • Page 169: Viewing Logs And Script Information

    Viewing Logs and Script Information This section contains procedures for viewing these files: Viewing the Status The status log records all errors trapped by the APS platform. Use this Log File procedure to view the status log: 1. From the APS main menu choose 101-1830-001 Issue 1.0 Viewing the Status Log File...
  • Page 170 APS (Application Plus Server) 4.1 Users Guide as shown in Figure 66. The status log window displays Figure 66. Status Log Window 101-1830-001 Issue 1.0...
  • Page 171: Viewing Script Information

    Viewing Script Use this procedure to see the comments embedded in a script. Information To view the script comments: 1. From the APS main menu choose Figure 67. Script Information Window 2. In the Script Name field, type the script’s name. 3.
  • Page 172 APS (Application Plus Server) 4.1 Users Guide 4. Click OK. Figure 69. Example of a Script Information Window 5. Click Done to exit. Script information displays in another window as in Use the scroll bar to review the script’s comments Figure 69 101-1830-001 Issue 1.0...
  • Page 173: Viewing The Debug Log

    Viewing the Debug Use this procedure to see the call flow logic of a script application: 1. From the APS main menu choose 2. In the Script Name field, type the name of the script or Figure 70. Debug Log Window 3.
  • Page 174 APS (Application Plus Server) 4.1 Users Guide 101-1830-001 Issue 1.0...
  • Page 175: Chapter 5 Troubleshooting

    This chapter contains information about: The material in this chapter assumes that the Sierra/CA VPM is accessible to the reader. Troubleshooting procedures for ERP are found in Appendix A, ‘‘Enhanced Reporting Platform,’’the section entitled ‘‘Troubleshooting ERP’’ on page 377. 101-1830-001 Issue 1.0 Troubleshooting Starting and Stopping the Sun System...
  • Page 176: Starting And Stopping The Sun System

    APS (Application Plus Server) 4.1 Users Guide Starting and Stopping the Sun System There are several instances where you may need to stop and restart the APS Sun system: Starting the APS Sun System This procedure starts the APS Sun system from a power off state. 1.
  • Page 177: Starting The Erp Sun System

    Starting the ERP Sun System This procedure starts the ERP Sun system from a power off state. 1. Press the power button on the back of the Sun system. 2. Log in as root with the correct password. 3. In a terminal window, open the APS main menu. Enter The ERP system is up and ready to receive data.
  • Page 178: Graceful Reboot

    APS (Application Plus Server) 4.1 Users Guide Graceful Reboot Gracefully rebooting the APS consists of stopping and then starting software and hardware. 1. Stop all applications and scripts. See 2. Exit the APS main menu. 3. Login as root and enter Hard or Emergency Use this procedure if the software is locked or if the keyboard is not Reboot...
  • Page 179: Shutting Down The Aps Sun System

    7. Wait 15 seconds for the fans and drives to spin down. 8. Press the power button again to restore power. 9. From the APS main menu, examine the status log file. Choose Shutting Down the APS Sun System Use this procedure to gracefully shut down the APS Sun system. 1.
  • Page 180: Shutting Down The Erp Sun System

    APS (Application Plus Server) 4.1 Users Guide Shutting Down the ERP Sun System Use this procedure to gracefully shut down the ERP Sun system. 1. Login as root and enter 2. On a SunOS command line enter 3. At the OK prompt, power off the system with the button on the 4.
  • Page 181: Tracking Aps Problems

    Tracking APS Problems This section contains general guides to use when troubleshooting. General Troubleshooting Troubleshooting always consists of these basic steps: 1. Confirm the problem. 2. Diagnose the problem. 3. Affect the fix or escalate the problem. 4. Test and confirm the fix. 5.
  • Page 182: Starting Two Aps Sessions

    APS (Application Plus Server) 4.1 Users Guide Starting Two APS Sessions To diagnose particularly difficult problems, you can start two APS main menu sessions at the same time. Two APS sessions enable you to monitor several aspects of a trouble. For example, open one interface to run a script in test mode and another interface to observe system performance as this script runs.
  • Page 183: Troubleshooting Connectivity Problems

    Troubleshooting Connectivity Problems The troubleshooting information in this section discusses the following connectivity topics: Connectivity problems can occur between any of the components that make up the APS system. This section describes the symptoms, cause, and solution for the following connectivity problems between: Sierra/CA Passive alarm monitoring system...
  • Page 184: No Connectivity Between Aps Machine And Sierra/Ca

    APS (Application Plus Server) 4.1 Users Guide No Connectivity Between APS Machine and Sierra/CA Failure of the APS to communicate with the Sierra/CA presents particularly limited diagnostic and corrective measures. To further complicate the problem, there may be an Xspan box or PDN (Packet/Public Data Network) located between the APS and the Sierra/CA.
  • Page 185 Resolution To correct this connectivity problem: Each of these items is described below. 101-1830-001 Issue 1.0 Software drivers are missing or not referenced properly The TCP/IP enable portion of the profile for an application has not been administered correctly. X.25 hardware has failed for some reason TCP/IP hardware has failed for some reason Check the physical wiring.
  • Page 186: For Sites That Use X.25

    APS (Application Plus Server) 4.1 Users Guide For Sites That Use X.25 If your site uses X.25 to connect the APS and the Sierra/CA, use the procedures in this section. Check the X.25 1. Make sure that X.25 cables linking the Sierra/CA and the APS Physical Connectivity 2.
  • Page 187: From The Sierra/Ca, Check The Link

    10. Enter x25tool& 11. Choose 12. In the bottom of the window you will see the message: 13. To restart all X.25 links from the APS: If the previous steps do not work, stop and restart the link from the Sierra/CA side using the instructions in the next step.
  • Page 188: Place A Test Call Over The X.25 Link

    APS (Application Plus Server) 4.1 Users Guide 7. Enter the link number you noted in step 4. 8. Enter a 2 to stop the link. 9. Press ENTER to move the cursor to the top of the same screen. 10. Enter the link number again. 11.
  • Page 189: Escalate The Problem

    4. Choose 5. Make sure the link shows as CONNECTED NORMAL. Do an 6. Using a handset, dial the extension to the Sierra/CA. 7. If you hear “Sorry. The service you have requested is not 8. If you hear “Message delivery service has experienced a Escalate the If the above procedures do not correct the problem, escalate the problem.
  • Page 190: For Sites That Use Tcp/Ip

    APS (Application Plus Server) 4.1 Users Guide For Sites That Use TCP/IP If your site uses TCP/IP connectivity to communicate with the Sierra/CA, use these procedures to check that link: Check TCP/IP Do the following steps to make sure that the TCP/IP connection is Physical physically viable.
  • Page 191: Check The Application's Profiles

    Check the Check the application’s profiles that use TCP/IP Enable and make sure Application’s that the TCP/IP connection is set up correctly there. Profiles The application documentation contains the correct settings for profiles that use the TCP/IP Enable button. Refer to that document. Place a Test Call In order to place test calls, you must have: Over the TCP/IP Link...
  • Page 192: Escalate The Problem

    APS (Application Plus Server) 4.1 Users Guide 9. Using a handset, dial the extension to the Sierra/CA. Escalate the If the above procedures do not correct the problem, escalate the problem. Problem If you receive this problem as an escalation: 1.
  • Page 193: Remote User Cannot Connect To Aps Machine

    Remote User Cannot Connect to APS Machine Remember that there are two ways for a remote user to access the APS machine, over the WAN and dialing in through a modem. This section discusses dialing in with a modem. Symptom Remote users trying to access the APS machine with a modem and PPP (point-to-point protocol) may not be able to connect.
  • Page 194 APS (Application Plus Server) 4.1 Users Guide 6. If the problem persists for over an hour, call the APS site and 7. If the above steps do not correct the problem, escalate this have an onsite worker check the APS machine. problem to the next level of support.
  • Page 195: Aps Cannot Connect To Lan/Wan

    APS Cannot Connect to LAN/WAN The APS machine cannot connect to the LAN/WAN and communicate with any of the agents on it. Agents on the LAN that the APS would expect to see are: Symptoms Basis Solution 1. Try to ping yourself. Enter ping <hostname> 2.
  • Page 196: Aps Cannot Communicate With Hlr

    APS (Application Plus Server) 4.1 Users Guide APS Cannot Communicate With HLR In APS 4.1, all communication to the HLR is across the NewNet card. Symptom Basis Solution 1. Check all physical connections, making sure they are snug and 2. Trace the call. See ‘‘Call Tracing TCAP Messages’’ on page 201 3.
  • Page 197 4. Check the links and routes. 5. If the above steps do not correct the situation, escalate this 101-1830-001 Issue 1.0 Open the aps.cfg file and make sure that links and routes are defined correctly. See ‘‘Changing an SS7 Configuration File’’ on page 145 for more details on how to do this, or contact the support line.
  • Page 198: No Prompt When Accessing Aps Over The Modem

    APS (Application Plus Server) 4.1 Users Guide No Prompt When Accessing APS Over the Modem Symptom A remote user dials in. Even though the APS system answers, the remote user never gets a log in prompt in the post dial up window. Basis Resolution If you suspect that the serial port setup in Admintool is incorrect, do the...
  • Page 199 If you suspect that the dial up number is incorrect, do the following: 1. Make sure you typed in the correct number, making no typing 2. Check the number in your communications software if it is 3. Make sure you have the correct number to dial in on. You may 101-1830-001 Issue 1.0 errors.
  • Page 200: Troubleshooting Software Problems

    APS (Application Plus Server) 4.1 Users Guide Troubleshooting Software Problems This section describes the following software problems: Loss of System Heartbeat Symptom Informational alarm 60000 does not occur as it should. Basis System heartbeat logging enables you to see if the APS is down and in a condition that it cannot report itself down.
  • Page 201: Call Tracing Tcap Messages

    Call Tracing TCAP Messages To invoke a trace between the SS7 gateway and the APS platform, use the following procedure at the APS system. This procedure assumes you have only one network interface, “hme0”. 1. Log in as root. 2. Enter 3.
  • Page 202 APS (Application Plus Server) 4.1 Users Guide Error codes for snoop are provided in Table 14. Table 14. TCAP Error Codes Reason Code 0x00 0x01 0x02 0x03 0x04 Meaning Description Not used — Unassigned directory The cellular handset number is not served by the accessed system.
  • Page 203: Cannot Start Application Manager

    Cannot Start Application Manager Symptom Basis There are two reasons APS cannot start the application manager. Solution If there is a problem with the file issg_appmgr_key: 1. From the operating system prompt, delete the file issg_appmgr_ 2. Try to start the application manager again. 3.
  • Page 204 APS (Application Plus Server) 4.1 Users Guide If Informix is not running: 1. Reboot the Sun. 2. If you do not want to reboot the Sun system, see ‘‘Starting the Rebooting causes all software components to load properly. If the Informix database is not running properly, you may suspect that other software activities may at fault.
  • Page 205: Cannot Load Ss7 Drivers

    Cannot Load SS7 Drivers Symptom Basis This problem may be due to: Resolution 1. Make a note of the way Solaris recognizes the card. For example, 2. Modify the SS7 config file aps.cfg to load the driver to dev #2 3.
  • Page 206: Troubleshooting Hardware Problems

    APS (Application Plus Server) 4.1 Users Guide Troubleshooting Hardware Problems For hardware problems related to generic Sun Ultra hardware components, consult your Sun manuals. For hardware problems related to customized components specific to the APS machine, use this section for advice on troubleshooting.
  • Page 207: Common Procedures

    Common Procedures The common procedures discussed in this section are: General Notes about Replacing Cards Use this general procedure to install or remove any circuit card in a APS system. Specific instructions are provided in the section for the specific card.
  • Page 208 APS (Application Plus Server) 4.1 Users Guide 3. Establish an ESD ground. 4. Inspect the new circuit card for damage. 5. Open the chassis of the Sun system. 6. Remove any cables, then remove the present card. 7. Insert the new card and reconnect any cables. 8.
  • Page 209: Replacing The Newnet Card

    Replacing the NewNet Card Lucent Technologies OMD support personnel use this procedure to change the NewNet card. They will need a screwdriver and the correct Sun hardware manuals to remove the card. There are no jumpers or switches to set on the NewNet card. 1.
  • Page 210: Replacing The X.25 Card

    APS (Application Plus Server) 4.1 Users Guide Replacing the X.25 Card Sun support personnel use this procedure to change the X.25 link card in fifteen minutes. They will need a screwdriver and the correct Sun hardware manuals to remove the card. There are no jumpers or switches to set on the X.25 card.
  • Page 211: Cleaning The Tape Drive

    5. Reboot the workstation. See ‘‘Starting the ERP Sun System’’ on 6. Check that ERP is functioning correctly for the next day or two. Cleaning the Tape Drive You should clean the tape drive on the Sun system regularly, keeping track of maintenance information in writing.
  • Page 212 APS (Application Plus Server) 4.1 Users Guide 101-1830-001 Issue 1.0...
  • Page 213: Backing Up And Restoring Data

    This chapter discusses backing up and restoring all data on the Sun system. Note: Note: Backing Up and Restoring the Sun System Use a 125 M 4mm data tape, 24 gigabytes, manufactured by Fuji Film, labeled DG3-125M or an equivalent tape. Do not use the cleaning tape for backup purposes.
  • Page 214: Automatic Backups

    APS (Application Plus Server) 4.1 Users Guide Automatic Backups Backups are performed automatically at 11:00 p.m. You must place a tape in the tape drive anytime prior to the backup time so as not to generate errors. We recommend that you prepare one tape for every day of the week, for example, have a Monday tape, a Tuesday tape, and so on.
  • Page 215: Restoring A Full Or Partial Image

    Restoring a Full or Partial Image Use this procedure to restore data from a tape to the hard drive in the Sun system. This procedure restores the entire hard disk in the APS system using the install_fs command. The install_fs command has options as shown in Figure 76.
  • Page 216: Full System Recovery (No Setup)

    APS (Application Plus Server) 4.1 Users Guide Full System Option 2 on the install_fs menu replaces all data on all hard disks, but Recovery (no setup) does not change any system configuration data that has been set previously. Use this option to restore a machine from a backup tape from that same machine.
  • Page 217: Informix Software Backup And Restore

    Informix Software Backup and Restore The Informix software resides on home1. To back up the Informix software package, use the sys_backup command and make a manual backup as described in ‘‘Making Manual Backups’’ on page 214. To restore the Informix software package specifically, run restore_homes and choose menu option 2, /export/home1.
  • Page 218: Example Output Of

    APS (Application Plus Server) 4.1 Users Guide Example Output of install_fs menu option 1 performs a full restore and prompts for setup install_fs:full information. This is the menu option used when installing a new drive or recovery, (setup) a new site. The example output below shows the procedure used to restore on an A1000-Full recovery with setup, install_fs menu option 1.
  • Page 219 Please Enter the operation to be performed: 1 You selected "Full system installation and setup" Is this correct (yes or no)? y Configuring VTOC for /dev/rdsk/c0t0d0s2 (disk 0) done Configuring VTOC for /dev/rdsk/c0t1d0s2 (disk 1) done Creating File System for root (/dev/rdsk/c0t0d0s0) Creating File System for /var (/dev/rdsk/c0t1d0s1) Installing bootblk on the root drive Restoring the root filesystem from tape...
  • Page 220 APS (Application Plus Server) 4.1 Users Guide You entered 135.9.134.227, Is this correct (yes or no)? y Please Enter the Host PPP Netmask [255.255.255.0]: You entered 255.255.255.0, Is this correct (yes or no)? y ____________________________________________________________________________ 101-1830-001 Issue 1.0...
  • Page 221: Example Output Of

    Example Output of The example output below shows the procedure used to restore on an install_fs:full A1000-Full recovery with no setup, install_fs menu option 2. recovery (no setup) ____________________________________________________________________________ ...boot from CDROM... # tar xvf /dev/rmt/0 x ., 0 bytes, 0 tape blocks x ./aps_enhance, 10381 bytes, 21 tape blocks x ./cmdq_rem.sql, 2203 bytes, 5 tape blocks x ./disk0.vtoc.4GB, 537 bytes, 2 tape blocks...
  • Page 222 APS (Application Plus Server) 4.1 Users Guide Please Enter the operation to be performed: 2 You selected "Full system recovery (no setup)" Is this correct (yes or no)? Y Configuring VTOC for /dev/rdsk/c0t0d0s2 (disk 0) done Configuring VTOC for /dev/rdsk/c0t1d0s2 (disk 1) done Creating File System for root (/dev/rdsk/c0t0d0s0) Creating File System for /var (/dev/rdsk/c0t1d0s1) Installing bootblk on the root drive...
  • Page 223: Example Output Of

    Example Output of The example output below shows the procedure used to restore on an install_fs:partial A1000 partial recovery with setup, install_fs menu option 3. recovery (setup) ____________________________________________________________________________ ...boot from CDROM... # tar xvf /dev/rmt/0 x ., 0 bytes, 0 tape blocks x ./aps_enhance, 10381 bytes, 21 tape blocks x ./cmdq_rem.sql, 2203 bytes, 5 tape blocks x ./disk0.vtoc.4GB, 537 bytes, 2 tape blocks...
  • Page 224 APS (Application Plus Server) 4.1 Users Guide WARNING: this is a destructive installation of software. Proceed with the installation? Please Enter the operation to be performed: 3 You selected "Partial system recovery and setup" Is this correct (yes or no)? y Configuring VTOC for /dev/rdsk/c0t0d0s2 (disk 0) done Configuring VTOC for /dev/rdsk/c0t1d0s2 (disk 1) done Creating File System for root (/dev/rdsk/c0t0d0s0)
  • Page 225 Timezone: 3 You have selected Mountain, Is this correct (yes or no)? y The date and time is currently set to Fri Feb 19 23:56:15 MST 1999 Would you like to change the date and/or time? (yes/no) [no]: Please enter a password for the root user New password: Re-enter new password: passwd (SYSTEM): passwd successfully changed for root...
  • Page 226: Example Output Of Install_Fs, Partial Recovery (No Setup)

    APS (Application Plus Server) 4.1 Users Guide Example Output of The example output below shows the procedure used to restore on an install_fs, partial A1000-partial recovery with no setup, install_fs menu option 4. recovery (no setup) ____________________________________________________________________________ ...boot from CDROM... # tar xvf /dev/rmt/0 x ., 0 bytes, 0 tape blocks x ./aps_enhance, 10381 bytes, 21 tape blocks...
  • Page 227 Creating File System for root (/dev/rdsk/c0t0d0s0) Creating File System for /var (/dev/rdsk/c0t1d0s1) Installing bootblk on the root drive Restoring the root filesystem from tape Restoring the /var filesystem from tape Would you like to restore any of the following filesystems? Please Enter your selection: 4 You selected "/export/home0, /export/home1, and /export/home2"...
  • Page 228 APS (Application Plus Server) 4.1 Users Guide 101-1830-001 Issue 1.0...
  • Page 229: Chapter 7 Errors

    This chapter contains information about: The Status Log File The status log file contains all informational and error messages generated by APS 4.1. The status log file is available in both ASCII and EBCDIC formats. As you work with APS 4.1 you will become very familiar with using and interpreting data in the status log file.
  • Page 230: File Formats

    APS (Application Plus Server) 4.1 Users Guide Besides the ring buffer, the status log file is maintained in another file located in: /export/home0/issg/issg_main/issg_lib/liblogger/issg_logger_seq_file This file keeps adding entries to the end of the file and is deleted hourly. File Formats The status log file may be either: By default, the status log file is a binary file in EBCIDIC format.
  • Page 231: What Makes Up An Alarm

    4. Stop and then restart the logger manager. See ‘‘Starting and What Makes Up an Alarm The following sections explain the message format for each group of alarms, how the alarms are numbered, and the alarm categories common to both groups of alarms. Message Syntax for Alarms Figure 77 shows an example from the status log file.
  • Page 232: Interpreting An Error With Status Log File Codes

    APS (Application Plus Server) 4.1 Users Guide Table 15. Parts of the Status Log File (Continued) status_type module_type error_code status_data0 status_data1 status_data2 status_data3 Interpreting an Error with Status Log File Codes Each entry in the status log file contains the fields: These three parts of the status log file entry provide information about the error that needs further interpretation.
  • Page 233: Status Types

    Status Types Status types denote the severity of the error. Possible status types of errors are listed in Table 16. Table 16. Status Types Error Types WARNING ERROR 101-1830-001 Issue 1.0 Value Description 1 - Minor This is a minor error condition. It indicates a condition that can automatically be corrected by the system.
  • Page 234: Module Types

    APS (Application Plus Server) 4.1 Users Guide Table 16. Status Types (Continued) Error Types INFO Module Types Module types designate the software module, such as Interpreter or Database, that generated the error. Software modules and their module number are listed in Table 17 below. Table 17.
  • Page 235 Table 17. Module Types (Continued) 0005 Value 0006 0007 0008 0009 0010 0011 0012 0013 0014 0015 0016 0017 0018 0019 0020 0021 0022 0023 0024 0025 0026 0027 0028 0029 0100 101-1830-001 Issue 1.0 OCL library Module Type Description Logger Logger library Cron...
  • Page 236: Error Code Ranges

    APS (Application Plus Server) 4.1 Users Guide Table 17. Module Types (Continued) Value 0101 0600 to 0699 Error Code Ranges Table 18 gives the ranges into which error codes are grouped. Table 18. Error Code Ranges Error Code Range 000000 through 300000 501000 through 501999 502000 through 502999 503000 through 503999...
  • Page 237: Errors

    Table 18. Error Code Ranges (Continued) Error Code Range 514000 through 514999 515000 through 515999 516000 through 516999 517000 through 517999 518000 through 518999 519000 through 519999 520000 through 520999 521000 through 521999 522000 through 522999 523000 through 523999 524000 through 524999 600000 through 600009 600010 through 600029, 6000030 through 60033...
  • Page 238: Development Alarms

    APS (Application Plus Server) 4.1 Users Guide Errors This section describes all the error codes. Each error description provides information about The error type What software module generated the error Messages and data the error displays A description of what caused the error How to resolve the error 101-1830-001 Issue 1.0...
  • Page 239: Error Summary

    Development Table 19 summarizes errors that may be found in the status log but reflect Alarms alarm points for debugging software. If you encounter any of the errors found in Table 19, please call the technical support hotline. Table 19. Undefined Error Codes 60000 200000 200002...
  • Page 240 APS (Application Plus Server) 4.1 Users Guide Error Summary Table 20 summarizes the errors described in the rest of this chapter. Table 20. Summary of Error Codes Error 200001 200005 200008 400000 501001 501002 501006 501012 501013 501020 503001 505001 505002 505005 505011...
  • Page 241 Table 20. Summary of Error Codes Error 506006 506007 506011 508001 508002 508003 508004 508005 517003 518003 518004 518005 518006 518007 518010 523000 5230002 5230003 5230005 5230008 5230012 524027 101-1830-001 Issue 1.0 Name Problem opening X.25 circuit VC closed by external devices Problem writing to X.25 circuit Invalid software license Unmatched host name...
  • Page 242 APS (Application Plus Server) 4.1 Users Guide Table 20. Summary of Error Codes Error 600000 600001 600002 600003 600004 600010 600011 600012 600013 600014 600015 600016 600017 600018 600019 600020 600021 600022 600023 600024 600025 600026 600027 600028 600029 Name APS heartbeat APS config file error Too few APS scripts...
  • Page 243 Table 20. Summary of Error Codes Error 600030 600031 600032 600033 600034 600035 600037 600038 600039 600040 600041 700001 700002 700003 700004 700005 700006 700007 700008 101-1830-001 Issue 1.0 Name Backup tape failed to rewind Backup failed to create vtoc Backup failed to tar scripts to tape Backup failed on xxx file...
  • Page 244 APS (Application Plus Server) 4.1 Users Guide 200001 Error Type 3 – Informational Module Type 4 - Interpreter Status Message INFO: (Script: <script name>) Cannot run. Script stopped. Status Data 1 Called by the script runner. Effect No effect. This alarm is informational only. Description Script runner was unable to run the script because the script was stopped.
  • Page 245 200005 Error Type 2 - Error Module Type 4 - Interpreter Status Message ERROR: (Script: <script name>) Failed to open vc. Status Data 1 This error may have either of these messages in the Status Data 1 field: Called by the scheduler. Script runner failed.
  • Page 246 APS (Application Plus Server) 4.1 Users Guide 200008 Error Type 4 - POI, Critical Module Type 1 - Database Status Message POI: Failed to open database issg_db. Return code = [int]. Status Data 1 Called by the Script runner. Effect Failure to open the database results in no production.
  • Page 247 400000 Error Type 2 - Error Module Type 4 - Interpreter Status Message ERROR: Script: <script name> failed to open SMPP connection <integer> Status Data 1 Script runner failed. Effect Service will be affected. Description Script runner was unable to open SMPP connection. The integer at the end of the status message gives the port number Script runner tried to use.
  • Page 248 APS (Application Plus Server) 4.1 Users Guide 501001 Error Type 1 - Warning 2 - Error Module Type 8 - Application Manager Status Message This error can display any of the following Status Messages: Each of these status messages is discussed separately. WARNING: Key file not Status Data 1 found.
  • Page 249 Effect No effect, the system can recover from this error. Description The application manager was unable to find the specified file. Check the file system for any errors. This error causes the application manager to exit. Resolution 1. Restart the script. See ‘‘Starting a Single Script’’ on page 123 or 2.
  • Page 250 APS (Application Plus Server) 4.1 Users Guide Description The application manager was unable to register a script run due to missing issg_appmgr_key. This causes the application manager to exit. Resolution 1. Restart the script. See ‘‘Starting a Single Script’’ on page 123 or 2.
  • Page 251 501002 Error Type 2 - Error Module Type 8 - Application manager Status Message ERROR: Application manager is not running Status Data 1 Script cannot be started without a valid appmgr. Effect Service will be affected. Description The application manager is not started but is trying to start scripts. Start the application manager before attempting to start any script.
  • Page 252 APS (Application Plus Server) 4.1 Users Guide 501006 Error Type 2 - Error Module Type 8 - Application manager Status Message ERROR: Problem spawning a task. Status Data 1 RC=[integer] ERRNO=[integer] Effect Service will be affected. Description The application manager is having a problem spawning a new task. Application manager is responsible for starting all of the tasks.
  • Page 253 501012 Error Type 1 - Warning 2 - Error Module Type 8 - Application manager Status Message This error can have the following Status Messages: This error, regardless of whether it is an error or warning, is treated the same way. Effect Service will be affected.
  • Page 254 APS (Application Plus Server) 4.1 Users Guide 501013 Error Type 1 - Warning 2 - Error Module Type 8 - Application manager Status Message WARNING: Unable to perform write on data file. ERROR: Unable to perform write on data file. Status Data 1 ERRNO=[integer] FILE=[string] Effect...
  • Page 255 501020 Error Type 2 - Error Module Type 8 - Application manager Status Message This error can have the following Status Messages: This error, regardless of its status message, is treated the same way. Effect Service will be affected. Description In this error, the application manager was unable to validate the APS license.
  • Page 256 APS (Application Plus Server) 4.1 Users Guide 503001 Error Type 2 - Error Module Type 1 - Database Status Message ERROR: Unknown database element. Status Data 1 Database contains unknown base element type=[Integer] Effect Service will be affected. Description The database table contains an unknown base element. The supported set of base elements include the following: Resolution 1.
  • Page 257 505001 Error Type 2 - Error Module Type 5 - OCL Status Message ERROR: Unable to send OCL command to the network. Status Data 1 RC = [integer] SOCKET = [integer] OCLPKT = [string] Effect Service will be affected. Description APS is having difficulty sending an OCL command to the VPM through the network.
  • Page 258 APS (Application Plus Server) 4.1 Users Guide 505002 Error Type 2 - Error Module Type 5 - OCL Status Message ERROR: Unable to read OCL data from the network. Status Data 1 RC = [integer] SOCKET = [integer] Effect Service will be affected. Description APS software was unable to read expected OCL data from the network.
  • Page 259 505005 Error Type 4 - POI, Critical Module Type 5 - OCL Status Message POI: Parameter unknown to the ISSG OCL parser. Status Data 1 PARAM_ID=[<integer>] Effect If OCL commands cannot be parsed, there will be no call production. Description The OCL parser software encountered an OCL parameter that it does not know how to parse.
  • Page 260 APS (Application Plus Server) 4.1 Users Guide 505011 Error Type 4 - POI, Critical Module Type 5 - OCL Status Message POI: Unknown parameter encountered by OCL parser. Status Data 1 OCLPRMID=[integer] Effect If OCL commands cannot be parsed, there will be no call production. Description The OCL parser software encountered an OCL parameter that it does not know how to parse.
  • Page 261 506002 Error Type 2 - Error Module Type 100 - X.25 protocol library Status Message ERROR: Problem opening X.25 virtual circuit. Status Data 1 RC=[Integer] ERRNO=[Integer] X25ADDR=[x25 address] Effect Service will be affected. Description The APS software was unable to open an X.25 virtual circuit. This error can have several causes: This problem can happen because of several reasons.
  • Page 262 APS (Application Plus Server) 4.1 Users Guide 506003 Error Type 2 - Error Module Type 100 - X.25 Protocol Library Status Message ERROR: Problem opening X.25 virtual circuit Status Data 1 X25ADDR=[x25 address] X25STREAM=[Integer] Effect Service will be affected. Description This error indicates that the APS software was able to open the connection to the X.25 device driver, but could not convert the X.25 address to a network format.
  • Page 263 506004 Error Type 2 - Error Module Type 100 - X.25 Protocol Library Status Message ERROR: Problem opening X.25 virtual circuit. Status Data 1 ERRNO=[Integer] X25STREAM=[Integer] X25ADDR=[x25 address] Effect Service will be affected. Description This error indicates that the APS software was unable to open a virtual circuit because it was unable to send a CALL REQUEST packet.
  • Page 264 APS (Application Plus Server) 4.1 Users Guide 506005 Error Type 2 - Error Module Type 100 - X.25 protocol library Status Message ERROR: Problem opening X25 virtual circuit. Status Data 1 ERRNO=[Integer] X25STREAM=[Integer] X25ADDR=[x25 address] Effect Service will be affected. Description This error indicates that the APS software was unable to open an virtual circuit because it was unable to receive a CALL REQUEST RESPONSE...
  • Page 265 506006 Error Type 2 - Error Module Type 100 - X.25 protocol library Status Message ERROR: Problem opening X25 virtual circuit Status Data 1 ERRNO=[Integer] X25STREAM=[Integer] X25ADDR=[x25 address] Effect Service will be affected. Description This error indicates that the APS software was unable to open a virtual circuit because it received an improper control packet from the X.25 driver.
  • Page 266 APS (Application Plus Server) 4.1 Users Guide 506007 Error Type 2 - Error Module Type 100 - X.25 protocol library Status Message ERROR: VC closed by external devices. Status Data 1 X25 CALL CLEAR Sent by the external device. Unexpected control packet sent by the external device. Effect Service will be affected.
  • Page 267 506011 Error Type 2 - Error Module Type 100 - X.25 protocol library Status Message ERROR: Problem writing to X25 virtual circuit. Status Data 1 ERRNO=[Integer] VC=[Integer] Effect Service will be affected. Description The APS X.25 protocol library encountered a problem while attempting to write to an X.25 virtual circuit.
  • Page 268 APS (Application Plus Server) 4.1 Users Guide 508001 Error Type 4 - Point of Interest, Critical Module Type 100 - X.25 protocol library Status Message POI: Invalid License Status Data 1 PID=[integer] Effect There is no call production if APS is licensed improperly. Description The license manager was unable to find a valid license for the system.
  • Page 269 508002 Error Type 2 - Error Module Type 100 - X.25 protocol library Status Message ERROR: Unmatched hostname Status Data 1 HNAME_1 = [string] HNAME_2 = [string] Effect Service will be affected. Description The license manager was unable to find a valid license for this system. The hostname specified in the license does not match the system hostname.
  • Page 270 APS (Application Plus Server) 4.1 Users Guide 508003 Error Type 2 - Error Module Type 10 - License manager Status Message ERROR: Unmatched IP address Status Data 1 IP_1 = [string] IP_2 = [string] Effect Service will be affected. Description The license manager was unable to find a valid license for this system.
  • Page 271 508004 Error Type 2 - Error Module Type 10 - License manager Status Message ERROR: License Expired Status Data 1 — Effect Service will be affected. Description The license manager was unable to find a valid license for this system. The demo license that registered this system has expired.
  • Page 272 APS (Application Plus Server) 4.1 Users Guide 508005 Error Type 2 - Error Module Type 10 - License manager Status Message ERROR: Invalid License Key Status Data 1 — Effect Service will be affected. Description The license manager was unable to find a valid license for this system. The license key specified in the license is not valid.
  • Page 273 517003 Error Type 2 - Error Module Type 28 - Registry Status Message ERROR: Open database error Status Data 1 SQLCODE=[Integer] ISAM=[Integer] Effect Service will be affected. Description The dynamic parameter library was unable to open the Informix database to list the parameters. Resolution 1.
  • Page 274 APS (Application Plus Server) 4.1 Users Guide 518003 Error Type 2 - Error Module Type 20 - IS-41 Proxy server Status Message Error in create the socket for process PID = [pid no] Status Data 1 Error: Create socket error Effect Service will be affected.
  • Page 275 518004 Error Type 2 - Error Module Type 20 - IS-41 Proxy server Status Message Error in set socket option for Process PID = [pid no], errno = [error no] Status Data 1 Error: set socket option error Effect Service will be affected. Description System error.
  • Page 276 APS (Application Plus Server) 4.1 Users Guide 518005 Error Type 2 - Error Module Type 20 - IS-41 Proxy server Status Message Error in bind a socket for process PID = [pid no], errno = [error no] Status Data 1 Error: Bind socket error Effect Service will be affected.
  • Page 277 518006 Error Type 2 - Error Module Type 20 - IS-41 Proxy server Status Message Error in listen for process PID = [pid no], errno = [error no] Status Data 1 Error: Listen socket error Effect Service will be affected. Description System error.
  • Page 278 APS (Application Plus Server) 4.1 Users Guide 518007 Error Type 3 - Informational Module Type 20 - IS-41 Proxy server Status Message Error in read packet header from client for process PID = [pid no], errno = [error no], socket = [socket no] Status Data 1 Error: Read packet header error Effect...
  • Page 279 518010 Error Type 2 - Error Module Type 20 - IS-41 Proxy server Status Message Select the fd set fail Status Data 1 Error: select error Effect Service will be affected. Description System error. Resolution 1. Stop and restart the application. See the application users guide 2.
  • Page 280 APS (Application Plus Server) 4.1 Users Guide 523000 Error Type 2 - Error Module Type 26 - IPC Library Status Message ERROR: Unable to create or Attach to IPC MSGQ. Status Data 1 ERRNO=[Integer] RC=[Integer] MQ_ID=[Integer] MODE=[Integer] Effect Service will be affected. Description The IPC library was unable to attach or create the requested IPC subsystem.
  • Page 281 5230002 Error Type 2 - Error Module Type 26 - IPC library Status Message This error can have two status messages: Both of these messages are discussed below. Resolution The resolution for both types of this error is the same. 1.
  • Page 282 APS (Application Plus Server) 4.1 Users Guide Description The IPC library was unable to send data to a message queue because it encountered a problem in the system call. Problem with system Status Data 1 signal. ERRNO=[Integer] SIGNAL=[Integer] Effect Service will be affected. Description: The IPC library uses sigalarm to read incoming data.
  • Page 283 5230003 Error Type 2 - Error Module Type 26 - IPC library Status Message ERROR: Problem receiving data for IPC MSGQ. Status Data 1 ERRNO=[Integer] RC=[Integer] MQ_HANDLE=[Integer] MODE=[Integer] TYPE=[Integer] Effect Service will be affected. Description The IPC library encountered a problem receiving a message from a message queue.
  • Page 284 APS (Application Plus Server) 4.1 Users Guide 5230005 Error Type 2 - Error Module Type 26 - IPC library Status Message ERROR: Problem creating or attaching to SHM. Status Data 1 ERRNO=[Integer] SHM_HD=[Integer] SHM_ID=[Integer] MODE=[Integer] NO_CHUNKS=[Integer] NO_DATUMS=[Integer] DATUM_SZ=[Integer] SHM_SIZE=[Integer] Effect Service will be affected.
  • Page 285 5230008 Error Type 2 - Error Module Type 26 - IPC library Status Message ERROR: Requested SHM Datum size is greater then MAX. Status Data 1 MAX_DATUM_SIZE=[Integer] REQ_DATUM_SIZE=[Integer] CHUNKNO=[Integer] MODE=[Integer] Effect Service will be affected. Description APS software attempted to put more data than is allowed by the IPC library.
  • Page 286 APS (Application Plus Server) 4.1 Users Guide 5230012 Error Type 2 - Error Module Type 26 - IPC library Status Message ERROR: Requested SHM chunk number greater than MAX. Status Data 1 MAX_CHUNK_NO=[Integer] REQ_CHUNK_COUNT=[Integer] MODE=[Integer] Effect Service will be affected. Description APS software attempted to put more data into a chunk than allowed.
  • Page 287 524027 Error Type 2 - Warning 3 - Error 4 - Point of Interest, Critical Module Type 29 - SS7 Status Message INFO: SS7 Card Alarm ERROR: SS7 Card Alarm Status Data 1 SP=[0] GRP=[5]TYPE=[11]MOD=[14]PAR1=[DATA]PARAM2=[DATA] SP=[0] GRP=[5]TYPE=[1]MOD=[132]PAR1=[DATA]PARAM2=[DATA] SP=[0] GRP=[5]TYPE=[1]MOD=[36]PAR1=[DATA]PARAM2=[DATA] Effect If the error is Description This alarm covers three levels of severity and reflects hardware problems...
  • Page 288 APS (Application Plus Server) 4.1 Users Guide To interpret this alarm: 1. Look at the text in the Status 1 line and note the Mod and Type. 2. Using the NewNet reference book, find the alarm. 3. Check the severity for the alarm in the book with the severity in 4.
  • Page 289 600000 Error Type 3 – Informational Module Type 600 - System heartbeat Status Message INFO: APS HEARTBEAT Status Data 1 — Effect Although this is an informational alarm, its absence in the status log file indicates that there is something wrong with the APS system. It may be locked or may have crashed.
  • Page 290 APS (Application Plus Server) 4.1 Users Guide 600001 Error Type 3 – Informational Module Type 600 - System heartbeat Status Message INFO: Cannot check APS script sanity, config file is missing or empty. Status Data 1 Check /export/home0/issg/issg_main/issg_lib/libheartbeat /heartbeat.config Effect Alarm 600000, system heartbeat, is not logged as it should be.
  • Page 291 Errors 2. Use the resulting number from step 2 above (or change an existing entry). If you need to turn off this check for script processes, put 0 (zero) in the configuration file. 101-1830-001 Issue 1.0...
  • Page 292 APS (Application Plus Server) 4.1 Users Guide 600002 Error Type 2 – Error Module Type 600 – System heartbeat Status Message ERROR: TOO FEW APS script processes are running. Status Data 1 — Effect No APS production, or production may not be at full capacity. Description Too few APS script processes are running as compared to the heartbeat.config file.
  • Page 293 5. Alternatively, you could go to each script and view its profile, 6. Stop the script and restart it, observe that all the processes are 7. If these steps do not solve the problem, escalate this problem to 101-1830-001 Issue 1.0 checking and altering the number of sessions.
  • Page 294 APS (Application Plus Server) 4.1 Users Guide 600003 Error Type 2 - Error Module Type 600 - System heartbeat Status Message Application manager (issg_appmgr) is not running Status Data 1 — Effect If the application manager is not running, APS is in production, but the applications and scripts themselves have not started.
  • Page 295 600004 Error Type 4 - Point of Interest Module Type 600 - System heartbeat Status Message ERROR: APS: SS7 logging process is not running Status Data 1 SS7 logging process is not running and should be. Effect No SS7 alarms logged. Description Because the SS7 logging process is not running, no SS7 alarms will be seen.
  • Page 296 APS (Application Plus Server) 4.1 Users Guide 600010 Error Type 3 - Informational Module Type 601 - Auto_Init on reboot Status Message ERROR: APS Reboot_Init started Status Data 1 — Effect No effect. This alarm is informational only. Description This is an informational error, alerting you that the Reboot_Init process has started.
  • Page 297 600011 Error Type 1 - Warning Module Type 601 - Auto_Init on reboot Status Message WARNING: APS Reboot_Init started logger manager Status Data 1 Logger manager was not already started in inittab Effect No effect; the system can recover from this error. Description This error warns you that the Reboot_Init process has started the logger manager.
  • Page 298 APS (Application Plus Server) 4.1 Users Guide 600012 Error Type 4 - Point of Interest Module Type 601 - Auto_Init on reboot Status Message POI: APS: Failed fsck /export/home0 Status Data 1 /export/home0 failed fsck, return code =nn Effect Auto_Init aborts, nothing starts and there is no production. Description An fsck was run on /export/home0 and it came back with a return code not equal to zero, meaning the fsck failed.
  • Page 299 Table 21. fsck Return Codes (Continued) Return Code 4. If the previous steps don’t solve the problem, escalate this 101-1830-001 Issue 1.0 Description A signal was caught during processing Uncorrectable errors detected - terminate immediately For root, same as 0. problem to the next level of support.
  • Page 300 APS (Application Plus Server) 4.1 Users Guide 600013 Error Type 4 - Point of Interest Module Type 601 - Auto_Init on reboot Status Message POI: APS: Failed fsck /export/home1 Status Data 1 /export/home1 failed fsck, return code = 34 Effect Auto_Init aborts, nothing starts and there is no production.
  • Page 301 600014 Error Type 4 - Point of Interest Module Type 601 - Auto_Init on reboot Status Message POI: APS: Failed fsck /export/home2 Status Data 1 /export/home2 failed fsck, return code = 34 Effect Auto_Init aborts, nothing starts and there is no production. Description An fsck was run on /export/home2 and it came back with a return code not equal to zero, meaning the fsck failed.
  • Page 302 APS (Application Plus Server) 4.1 Users Guide 600015 Error Type 1 - Warning Module Type 601 - Disk full Status Message WARNING: APS: <file system name> is 95% full Status Data 1 — Effect Disk I/O may be slower, but not noticeably. Description The file system was checked and is greater than or equal to 95% full.
  • Page 303 600016 Error Type 2 - Error Module Type 601 - Disk full Status Message ERROR: APS: <file system name> is 92% full Status Data 1 — Effect Disk I/O may be slower, but not noticeably. Description The file system was checked and is 90-94% full. Resolution 1.
  • Page 304 APS (Application Plus Server) 4.1 Users Guide 600017 Error Type 1 - Warning Module Type 601 - Disk full Status Message WARNING: APS:<file system name> is 88% full Status Data 1 — Effect Disk I/O may be slower, but not noticeably. Description The file system was checked and is 80-89% full.
  • Page 305 600018 Error Type 3 - Informational Module Type 601 - Disk full Status Message INFO: APS: <file system name> is 75% full Status Data 1 — Effect No effect. This alarm is informational only. Description The file system was checked and is 70-79% full. Resolution 1.
  • Page 306 APS (Application Plus Server) 4.1 Users Guide 600019 Error Type 1 - Warning Module Type 601 - Disk full Status Message WARNING: APS: /var over 95% full Status Data 1 — Effect Disk I/O may be slower, but not noticeably. Description /var was checked and was over 95% full, so the /cron/log file was removed.
  • Page 307 600020 Error Type 4 - Point of Interest Module Type 601 - Disk full Status Message POI: APS: /var is still over 95% full Status Data 1 aborting Reboot_Init Effect Disk I/O may be slower, but not noticeably. Description The system will not come up completely until /var is less than 95% full. /var was checked and was over 95% full, so the /cron/log file was removed, and then it was checked again, and it is still over 95% full, so Reboot_Init was aborted.
  • Page 308 APS (Application Plus Server) 4.1 Users Guide 600021 Error Type 4 - Point of Interest Module Type 601 - Auto_Init on reboot Status Message POI: APS:X25 is not running Status Data 1 x.25 not running, Reboot_Init aborted Effect Auto_Init aborts, nothing starts , and there is no production. Description The X.25 link was checked and it is not running.
  • Page 309 600022 Error Type 4 - Point of Interest Module Type 601 - Auto_Init on reboot Status Message POI: APS: Informix is not running Status Data 1 Informix not running after 30 minutes, aborting Reboot_Init Effect Auto_Init aborts, nothing starts, and there is no production. Description Informix did not come up successfully.
  • Page 310 APS (Application Plus Server) 4.1 Users Guide 600023 Error Type 4 - Point of Interest Module Type 601 - Auto_Init on reboot Status Message POI: APS: cron is not running Status Data 1 Aborting Reboot_Init Effect Auto_Init aborts, nothing starts, and there is no production. Description Checked for cron in the process table, and it is not running.
  • Page 311 600024 Error Type 4 - Point of Interest Module Type 601 - Auto_Init on reboot Status Message POI: APS: Init_app_mgr failed Status Data 1 Aborting Reboot_Init Effect Auto_Init aborts, nothing starts and there is no production. Description Reboot_Init was tried to execute the Init_app_mgr script, and it failed. Resolution 1.
  • Page 312 APS (Application Plus Server) 4.1 Users Guide 600025 Error Type 3 - Informational Module Type 601 - Auto_Init on reboot Status Message INFO: APS: issg_appmgr_pid was removed Status Data 1 value of issg_appmgr_pid was -1, so removed it in order to start app mgr Effect No effect.
  • Page 313 600026 Error Type 4 - Point of Interest Module Type 601 - Auto_Init on reboot Status Message POI: APS: application manager not running Status Data 1 Aborting Init_app_mgr Effect No scripts start, no production. Description The application manager (issg_appmgr) process is not running. Resolution 1.
  • Page 314 APS (Application Plus Server) 4.1 Users Guide 600027 Error Type 3 - Informational Module Type 601 - Auto_Init on reboot Status Message INFO: APS: Reboot_Init/Init_app_mgr finished successfully Status Data 1 — Effect No effect. This alarm is informational only. Description The Reboot_Init and Init_app_mgr scripts have completed successfully.
  • Page 315 600028 Error Type 4 - Point of Interest Module Type 601 - Auto_Init on reboot Status Message POI: APS: No links in service (NORMAL state) Status Data 1 Applications may not run properly. Check X.25 links. Effect If links don’t come into service before the application starts, the application will fail.
  • Page 316 APS (Application Plus Server) 4.1 Users Guide 600029 Error Type 3 - Informational Module Type 600 - APSheartbeat or 601 - Auto_Init on reboot Status Message INFO: APS: 1 x25 link(s) currently up INFO: APS: 1 TCP/IP link(s) currently up Status Data 1 —...
  • Page 317 600030 Error Type 1 - Warning Module Type 605 - Backup failure Status Message ERROR: Tape failed to rewind. Status Data 1 Check to see if tape is in tape drive. Effect No backup made. Description Backup operation has failed. There is no tape in drive. Resolution 1.
  • Page 318 APS (Application Plus Server) 4.1 Users Guide 600031 Error Type 1 - Warning Module Type 605 - Backup failure Status Message ERROR: Failed to create virtual table of contents for disk n. (Disk n can be either 0, 1, or 2.) Status Data 1 Check /var/sys_backup.log for exact error message.
  • Page 319 600032 Error Type 1 - Warning Module Type 605 - Backup failure Status Message ERROR: Failed to tar install scripts to tape. Status Data 1 Check to make sure tape is in tape drive. Effect No backup made. Description Backup operation has failed. Tape was ejected prematurely. Resolution 1.
  • Page 320 APS (Application Plus Server) 4.1 Users Guide 600033 Error Type 1 - Warning Module Type 605 - Backup failure Status Message ERROR: APS: Failed to backup xxx file system. xxx is a file system with a name similar to the example for the root file system below: /dev/dsk/c0t0d0s0 Status Data 1...
  • Page 321 600034 Error Type 2 - Error Module Type 601 - SS7 check Status Message APS: No SS7 links in service Status Data 1 — Effect Outcalls cannot be made to HLR. Inbound calls are deposited to mailboxes, but cannot be delivered. Description There were no SS7 links determined to be in service.
  • Page 322 APS (Application Plus Server) 4.1 Users Guide 600035 Error Type 3 - Informational Module Type 601 - SS7 check Status Message APS: $NUM SS7 link(s) currently in service. Status Data 1 — Effect No effect. This alarm is informational only. Description There are NUM SS7 link(s) found to be in service.
  • Page 323 600037 Error Type 2 - Error Module Type 601 - SS7 check Status Message APS: error when running issg_ss7_stackload Status Data 1 — Effect Outcalls cannot be made to HLR. Inbound calls are deposited to mailboxes, but cannot be delivered. Description There was an error when running the command issg_ss7_stackload process to load the SS7 stack.
  • Page 324 APS (Application Plus Server) 4.1 Users Guide 600038 Error Type 1 - Warning Module Type 601 - SS7 check Status Message APS: SS7 alarm logger is not running Status Data 1 — Effect No SS7 alarms are captured in the status log file. Description An attempt to start the issg_ss7alarm logger failed.
  • Page 325 600039 Error Type 4 - POI Module Type 600 - APSheartbeat or 601 - Auto_Init Status Message When generated by module 600, the status message is: SS7GW HB check failed When generated by module 601, the status message is: APS:SS7 Gateway startup failed Status Data 1 Gateway process not in process table after attempted start, Reboot_Init aborted...
  • Page 326 APS (Application Plus Server) 4.1 Users Guide 600040 Error Type 4 - Point of Interest Module Type 601 - cmdq_rem.sql failed Status Message cmdq_rem.sql failed Status Data 1 Reboot_Init, Aborting Reboot_Init Effect Aborts starting the application manager. All other processes are started. Description There was an error when running the command cmdq_rem.sql to remove the database tables after installing or restoring home2.
  • Page 327 600041 Error Type 4 - Point of Interest Module Type 600- APSheartbeat or 601 - TCP/IP link status Status Message POI: APS: No TCP/IP links in service Status Data 1 Applications may not run properly. Check X.25 links. Effect If links don’t come into service before the application starts, the application will fail.
  • Page 328 APS (Application Plus Server) 4.1 Users Guide 600042 Error Type 1 - Warning 2 - Error 3 - Warning 4 - Point of Interest Module Type 600 - APSheartbeat Status Data 1 The status data filed contains one of these messages: 4 - DB >...
  • Page 329 Resolution Data needs to be removed from the database. 1. Escalate this problem if you are uncertain of how to resize the 2. Contact technical support to determine if you need to drop or 3. If the above step fails, escalate this problem to the next level of 101-1830-001 Issue 1.0 database.
  • Page 330 APS (Application Plus Server) 4.1 Users Guide 700001 Error Type 2 - Error Module Type 100 - TCP/IP errors Status Message ERROR: Unknown host Status Data 1 PID=[%d] errno=[%d] address=[%s] where PID is the process ID, errno is the UNIX error number, and address is the HOST/IP address.
  • Page 331 700002 Error Type 2 - Error Module Type 100 - TCP/IP errors Status Message ERROR: Socket error Status Data 1 PID=[%d] errno=[%d] where PID is the process ID and errno is the UNIX error number. Effect Service will be affected. Description This error occurs when APS is not able to create a socket descriptor.
  • Page 332 APS (Application Plus Server) 4.1 Users Guide 700003 Error Type 2 - Error Module Type 100 - TCP/IP errors Status Message ERROR: Unable to set socket option Status Data 1 PID=[%d] SNDBUF=[%d], errno=[%d] PID=[%d] RCVBUF=[%d], errno=[%d] PID=[%d] KEEPALIVE=[%d], errno=[%d] PID=[%d] LINGER=[%d], errno=[%d] where PID is the process ID, SNDBUF is the send buffer size to be set, RCVBUF is the receive buffer size to be set, KEEPALIVE is the value of KEEPALIVE, LINGER is the value of linger, and errno is the UNIX error...
  • Page 333 700004 Error Type 2 - Error Module Type 100 - TCP/IP errors Status Message ERROR: Connect error Status Data 1 PID=[%d] errno=[%d] address=[%s] where PID is the process ID, errno is the UNIX error number, and address is the HOST/IP address. Effect Service will be affected.
  • Page 334 APS (Application Plus Server) 4.1 Users Guide 700005 Error Type 2 - Error Module Type 100 - TCP/IP errors Status Message ERROR: Read socket error Status Data 1 PID=[%d] attempted to read [%d] bytes from socket [%d] failed errno [%d] where PID is the process ID and errno is the UNIX error number.
  • Page 335 700006 Error Type 2 - Error Module Type 100 - TCP/IP errors Status Message ERROR: Write socket error Status Data 1 pid= [%d] total bytes= [%d] socket= [%d] errno= [%d] where pid is the process ID, total bytes is the total bytes the process attempted to write, socket is the socket number written to, and errno is the UNIX error number.
  • Page 336 APS (Application Plus Server) 4.1 Users Guide 700007 Error Type 1 - Warning Module Type 100 - TCP/IP errors Status Message WARNING: Operation on an unopened socket Status Data 1 Socket is already closed (or never opened) Effect No effect, the system can recover from this error. Description This error occurs when a read or write operation is attempted to a closed socket.
  • Page 337 700008 Error Type 2 - Error Module Type 100 - TCP/IP errors Status Message ERROR: Unable to bind Status Data 1 Unable to bind to port [%d] ERRNO= [%d] where port is the port to bind to and errno is the UNIX system error number.
  • Page 338: Passive Alarm Monitoring

    APS (Application Plus Server) 4.1 Users Guide Passive Alarm Monitoring The APS 4.1 platform supports a passive alarm monitoring feature. With this feature, an application using the APS platform can connect to the APS platform, look at the APS status log file, and report the errors back to the application, filtering and formatting the text as desired.
  • Page 339: Interpreting Eap Errors

    EAP-related Errors EAP (external application processor) errors are errors on the Sierra/CA. Events may occur on the APS that are not perceived as errors until the event reaches the Sierra/CA. This section discusses such errors. The status log file on the Sierra/CA collects EAP-related errors in the VPM.
  • Page 340 APS (Application Plus Server) 4.1 Users Guide Table 22 describes the key fields in the Figure 78. Table 22. Key Fields in an EAP Alarm Offset 08 and 09 18 - 1B Table 23 Describes the task ID portion in Table 22. Table 23.
  • Page 341 Task ID 101-1830-001 Issue 1.0 Errors Release 2.0 and Newer File task 3 X.25 task OCL task ASA task (Aspen System Administration, now OSA, Octel System Administration) SMDI start task Unused SMDI end task IMS task (now GMS, global Messaging Notification System) IMS task Overflow evaluation task Simplified protocol task...
  • Page 342 APS (Application Plus Server) 4.1 Users Guide Table 24 describes the data fields for a status 24-type error. Table 24. Data Fields in Status Code 24 Offset Field Field Description Field Name Value Subcode Data exception error Function error Protocol error Session error Time out error (error value in offset 18-1B is 76)
  • Page 343 Table 24. Data Fields in Status Code 24 (Continued) 18 - 1B 101-1830-001 Issue 1.0 All LUNs (logic unit numbers) for the requested application number are busy. Low LUNs for the requested application number Buffer overflow: LUN will be cleared LUN is cleared Operation time-out: LUN will be cleared...
  • Page 344: Resolving Eap-Related Errors

    APS (Application Plus Server) 4.1 Users Guide Table 24. Data Fields in Status Code 24 (Continued) Resolving EAP-related Errors If you encounter a status-code 24 error: 1. Decode all significant bytes as described in Table 1. 2. For status codes 24 with subcodes 01 through 04, contact the 3.
  • Page 345 101-1830-001 Issue 1.0 a. Make sure that the X.25 link is connected to the main distribution board on the Sierra/CA. Recall that J48 connects to X.25 port 0 and J47 connects to X.25 port 1. b. Notify the EAP administrator that the X.25 link has failed at the physical level, even if connecting the link in step a.
  • Page 346: Tcap Return Error Codes

    APS (Application Plus Server) 4.1 Users Guide TCAP Errors There are three types of TCAP errors that are being implemented as part of the APS 4.1 release. These are These errors are recorded in cmd_jr_log table. All of these are fully implemented except for the Access Denied Reasons. If access is not granted, the call is rescheduled.
  • Page 347: Tcap Non-Requested Specific Errors

    Table 25. TCAP Return Error Codes Error 0x8C 0x8D through 0xFF TCAP errors are also reported in the applications’s journaling log as entry type 5. See the documentation that came with the application. TCAP Access Table 26 provides the error number in hex and a description for the Denied Reasons various reasons that a TCAP was denied access.
  • Page 348 APS (Application Plus Server) 4.1 Users Guide 101-1830-001 Issue 1.0...
  • Page 349: Overview

    Enhanced Reporting Platform This appendix discusses the Enhanced Reporting Platform (ERP) and associated software. This appendix contains the following sections: Overview The Enhanced Reporting Platform (ERP) off-loads report processing from the Application Plus Server. The ERP supports sites with single APS systems or sites with multiple APS systems.
  • Page 350: Advantages Of Erp

    APS (Application Plus Server) 4.1 Users Guide This directory is a repository for all reports. The secondary APSs will not house any reports generated by the ERP, but will hold any reports that APS generates. Batch processing includes creation of a billing report and several call activity reports initiated by cron on a nightly basis.
  • Page 351: Administration

    This cycle is repeated every night shortly after midnight. The tables on the ERP are completely refreshed each time. Administration Administration of the ERP software occurs at installation. During installation, the technician must administer: 101-1830-001 Issue 1.0 Primary and secondary roles of the APSs Hostnames TCP/IP address Addresses for external systems...
  • Page 352: Assembling The Erp Hardware

    APS (Application Plus Server) 4.1 Users Guide Assembling the ERP Hardware Check circuit card placement in the ERP workstation before loading software. ERP software requires that circuit cards in the ERP workstation be in specific slots. Figure 79 shows the card arrangement in a Sun Ultra 5 system.
  • Page 353: Cabling The Erp System

    Cabling the ERP System Cable the ERP, the APS and the LAN switch together. 1. Position the APS system, the ERP system, and the Baystack 2. Attach all power cables. 3. Connect the ERP workstation to the LAN switch in port 1, 4.
  • Page 354: Required Items And Information

    APS (Application Plus Server) 4.1 Users Guide Installing and Administering ERP Installation of the ERP is performed in three parts: Phase I Installation Procedures The ERP tape you are about to load contains the following packages: Required Items and Have the following items and information available to complete the Information installation procedure.
  • Page 355: Loading The Erp System

    Loading the ERP Loading the ERP system is the first part of the installation sequence. System This procedure boots the ERP machine from the CD-ROM, extracts the installation scripts, and asks questions regarding machine administration, such as IP addresses. This part should take about 30 minutes to complete. Loading ERP 1.
  • Page 356: Installing The License Information

    APS (Application Plus Server) 4.1 Users Guide 10. From the # prompt enter ./erp_install_fs 11. Remove the tape at a convenient time. 12. When the install script finishes, at the # prompt, enter 13. Press the STOP+a keys simultaneously. 14. Remove the Solaris CD from the CD-ROM drive. 15.
  • Page 357 Installing the This section installs the C compiler used by ERP. License Information 1. Enter /var/restore_files/c++_lic to run the c++_lic file. You will Figure 81. Messages Prior to License Installation Tool Window __________________________________________________________ The c/c++ license install program will now run. Enter c and c++ license information using the license install program If you don’t have the c and c++ license password at this time, cancel out of the install program by clicking on the “Cancel”...
  • Page 358 APS (Application Plus Server) 4.1 Users Guide 3. The window titled lit: Add license to be installed screen Figure 83. Add License Window 4. Click on Demo license and set it to No. 5. In the Feature Name option, select WS Compiler C SPARC 6.
  • Page 359: Phase Ii Installation Procedures

    10. Work through steps 5 through 9 again, this time selecting the 11. If successful at step 9, click on Close. 12. Go back to main screen. 13. Click on Install. 14. If the first paragraph says that the licenses have been installed, 15.
  • Page 360: Phase Ii Installation Procedures

    APS (Application Plus Server) 4.1 Users Guide Phase II Installation Procedures Both the APS system and the ERP system must be administered after the ERP software tape has been loaded in phase I. Perform phase I prior to the following procedures. The following log files reflect the activities that are performed in this phase.
  • Page 361: Phase Iii Installation Procedures

    9. Log in to the ERP as root 10. At the # prompt, enter /var/erp_install/erp_install_b 11. You will be asked for the following information: You are now ready to perform the phase III install procedures described in ‘‘Phase III Installation Procedures’’ on page 362. 101-1830-001 Issue 1.0 Are there 1, 2, 3, or 4 APSs?
  • Page 362: Configuration File Description

    APS (Application Plus Server) 4.1 Users Guide Phase III Installation Procedures Field technicians use this procedure after Phase I and Phase II installation procedures are complete. Phase III consists of administering reports to run on the ERP and/or the APS(s). This is done by editing an ERP configuration file as well as existing ISSG scripts using a standard editor like vi.
  • Page 363 Enhanced Reporting Platform # APS HOSTNAMES. One entry for each APS system. The entry "APS_PRI_HOSTNAME" # must specify the primary aps and there should be an "APS_SEC_HOSTNAME" # entry for each secondary aps. May be in any order. #APS_PRI_HOSTNAME = aps_primary #APS_SEC_HOSTNAME = aps_secondary #APS_SEC_HOSTNAME = aps_secondary #APS_SEC_HOSTNAME = aps_secondary...
  • Page 364 APS (Application Plus Server) 4.1 Users Guide Figure 85. Example erp.cfg file, APS portion ______________________________________________________________________ ########### start of APS erp.cfg file ########## # list the reports that will be executed by the machine on which # this config file resides. # will execute all reports.
  • Page 365 Table 86. erp.cfg Initialization Parameters (Continued) Key Name LOG_SEV_LEVEL LOG_TRUNCATE REPORT_EXEC There must be an entry here (with comment “#” removed) for each report that is to execute on a given machine. A given report should not be run on both the ERP and APS machines, but if a report will not be run on the ERP, it may (and probably should) run on all APS systems in a multiple-APS configuration.
  • Page 366 APS (Application Plus Server) 4.1 Users Guide testing, but a larger number results in fewer messages going to the log file. LOG_SEV_LEVEL This parameter will influence the quantity of messages that get logged to the log files. It may take one of the following values in order of decreasing severity - LOG_ERR, LOG_WARNING, LOG_NOTICE, LOG_INFO, LOG_DEBUG.
  • Page 367 The report executables that reside on the ERP have the same name as the corresponding report on the APS with the extension “.erp” appended. cmdreport7_gen exists only on the APS because it is not a daily report. Table 87 shows the names and locations of each of the standard report executables on the APS and the corresponding executables on the ERP.
  • Page 368 APS (Application Plus Server) 4.1 Users Guide APS reports cmdreport5 weekly_report cmdreport7_data cmdreport7_gen dir: ~issg/issg_ main/issg_ lib/libbilling/cmd_ billing file: cmd_billing Administering Perform the following steps to administer the ERP system to run reports: Reports 1. Decide which billing and report executables will be run on the 2.
  • Page 369 3. Edit the APS configuration file /export/home0/erp/data/erp.cfg to 4. Edit the ERP configuration file to include the daily reports that 101-1830-001 Issue 1.0 ~issg/issg_main/issg_reports/ or ~issg/issg_main/issg_billing directories on the APS on which the report is run. If a report is to run on the ERP, report output (merged data in the case of multiple-APS) will be placed on the primary APS in its original location.
  • Page 370: Uninstall Procedures

    APS (Application Plus Server) 4.1 Users Guide Uninstall Procedures To uninstall the APS side: 1. Log in as root on the APS machine. 2. Enter To uninstall the ERP side: 1. Log in as root on the ERP machine. 2. Enter /erp_install/erp_uninstall /var/restore_files/erp_aps_uninstall rm /var/restore_files/erp_aps_uninstall 101-1830-001...
  • Page 371: Executing Erp Software

    Executing ERP Software Once configured and administered, the ERP software will run on its own and without intervention. However, remember the following points to ensure that the ERP software runs optimally: 101-1830-001 Issue 1.0 The ERP and APS systems must be time-synchronized. This must be done manually by a site administrator.
  • Page 372: Error Logging

    APS (Application Plus Server) 4.1 Users Guide Error Logging The ERP subsystem has its own logging facility that uses the Solaris syslog daemon. All messages are logged according to the rules below: Log messages have the following format: DATE Mar 31 12:50:51 The HOSTNAME field is the hostname of the machine from which the message came.
  • Page 373 CODE emgr amgr eload crdb admump 101-1830-001 Issue 1.0 Enhanced Reporting Platform PROCESS NAME erpmgr apsmgr erpload cr_erp_db apsdump...
  • Page 374: Backup And Restore Procedures

    APS (Application Plus Server) 4.1 Users Guide Backup and Restore Procedures Backup and restore procedures for the ERP machine may be performed manually at any time. There is no automatic backup schedule for the ERP machine. Backing Up ERP Full Backup Use this procedure to backup the ERP system.
  • Page 375 3. When you see “Initializing Memory” on the screen, press the 4. From the prompt “OK”, enter boot cdrom 5. Ignore the Solaris Installation Program dialogue box. Right click 6. Insert the ERP platform backup tape into the DAT tape drive. 8.
  • Page 376 APS (Application Plus Server) 4.1 Users Guide 12. The system begins to reboot. When you see “Initializing Memory” on the screen, press the Stop+a keys simultaneously. 13. Take the Solaris CD out of the CDROM drive. 14. At the OK prompt, enter boot. You should have a fully functioning ERP system at this point.
  • Page 377: Troubleshooting Erp

    Troubleshooting ERP Because robust failover scenarios are not part of the requirements for this release, this section describes some of the steps that an engineer should take for general troubleshooting and to gather information for ERP support if the ERP behaves erratically. 101-1830-001 Issue 1.0 Inspect the log files on the ERP and call activity report output on...
  • Page 378 APS (Application Plus Server) 4.1 Users Guide Inspect /var/adm/messages (includes cron output). Inspect ~issg/issg_main/issg_out/cron_log. Inspect /export/home2/Online/msgs for Informix logging. 101-1830-001 Issue 1.0...
  • Page 379: Relinking With Logging Stub

    Developing Custom Reports The report executables delivered on the ERP (*.erp filenames in /export/home0/erp/bin/) must be executed on the ERP because they use a logging stub as a substitute for the logger manager available on APS but not available on ERP. Similarly, the executables delivered on the APS (in ~issg/issg_main/issg_reports) as part of the APS installation (not related to ERP installation) must be run on the APS.
  • Page 380 APS (Application Plus Server) 4.1 Users Guide 101-1830-001 Issue 1.0...
  • Page 381: Glossary, Abbreviations, And Acronyms

    Numerics 5ESS Switch A central office switch manufactured by Lucent Technologies that can be integrated with the Lucent Intuity system. A1000 A raid device manufactured by Sun Now OCL, Octel command language Application-programming interface, a set of formalized software commands and routines that can be referenced by an application to access underlying network services.
  • Page 382 APS (Application Plus Server) 4.1 Users Guide BITS Building integrated timing supply. A clock, or a clock with an adjunct, in a building that supplies DS1 and/or composite clock timing reference to all other clocks in that building. Compact disk Call Detail Recording CD-ROM Compact disk-read only memory...
  • Page 383 External application processor, this is what the Sierra calls the APS or ERP system. EBCDIC Extended binary coded decimal interchange code e-mail electronic mail Enhanced Reporting Platform, an APS application that sends report data to another machine for processing. Electrostatic discharge Electronic serial number, an optional field in the SMS invoke parameter.
  • Page 384 APS (Application Plus Server) 4.1 Users Guide Home location register, the database in charge of managing mobile phone subscribers that stores a permanent copy of the subscription information, and some location information, to enable call rout- ing to where the subscriber is located. High speed interface The APS application formerly known as MDS or CMD.
  • Page 385 Interactive voice response, a specialized computer that accepts input from either a telephone key- pad or the caller’s voice, and on the basis of that input, uses synthesized voice or prerecorded mes- sages to offer callers choices on how they can complete the purpose of their call. Journal The record produced in an audit trail.
  • Page 386 APS (Application Plus Server) 4.1 Users Guide Notification gateway Octel command language Octel Messaging Division, a division of the Business Communications Services portion of Lucent Technologies. Operating system Octel system administration Operational system support, the methods and procedures that directly support the daily operation of the telecommunications infrastructure.
  • Page 387 RAID Redundant array of inexpensive disks, several disks in a single housing written to so that if one disk is lost, no data is lost. RMPP Remote mailbox provisioning protocol Ring no answer Regional Service Center, a group of Lucent support engineers SAN number Service access number SCCP...
  • Page 388 APS (Application Plus Server) 4.1 Users Guide System management terminal SMTP Simple mail transfer protocol Snoop A SunOS command to trace TCAP messages Signaling point code SP number Service point number Signaling path indicator System query language Signaling System 7, an out-of-band network signaling standard that enables call-handling informa- tion for traffic over a number of trunks to travel between offices over a separate channel common to the group of trunks served.
  • Page 389 TNPP Telocator network paging protocol User-network interface, the point at which users connect to the network. Visual display editor, the ASCII editor preferred by many who use SunOS and UNIX. Voice information system Voice messaging system, used interchangeably with VPM. Voice processing module, used interchangeably with VPS.
  • Page 390 APS (Application Plus Server) 4.1 Users Guide 101-1830-001 Issue 1.0...
  • Page 391 A1000 powering up raid access denied reasons adding a new HLR point code addressing with X.25 tool administering ERP software hostnames TCP/IP addresses administrative scripts alarms 200001 200005 200008 400000 501001 501002 501006 501012 501013 101-1830-001 Issue 1.0 501020 503001 505001 505002 505005...
  • Page 392 APS (Application Plus Server) 4.1 Users Guide 5230003 5230005 5230008 5230012 524027 600000 600001 600002 600003 600005 600010 600011 600012 600013 600014 600015 600016 600017 600018 600019 600020 600021 600022 600023 600024 600025 600026 600027 600028 600029 600030 600031 600032 600033 600034 600035...
  • Page 393 creating starting starting automatically starting manually stopping APS 4.0 features initialization on reboot packaging passive alarm monitoring Solaris upgrade SS7 interface APS 4.1 backward compatibility communication protocols hardware hardware system logical constructs menu interface new features platform components software system circuit cards hardware base miscellaneous components...
  • Page 394 APS (Application Plus Server) 4.1 Users Guide backups APS data only APS only automatic between different hardware configurations data Informix logs manual media used output redirection sequential time billing report creating busy, idle, done, and error sessions buttons on Profile window cabling ERP to APS TCP/IP...
  • Page 395 Reboot_Init start rm issg_appmgr_key rm issg_logger_cir_file rm issg_logger_seq_file SEQ=ON shutdown -y -i0 -g0 snoop command SQL commands with output SQL commands without output su - informix su -issg sys_backup tar xvf /dev/rmt/0 vi /export/home0/issg/issg_main/issg_ lib/libheartbeat/heartbeat.config vmstat x25tool& compatibility compile errors components APS platform configurable parameters...
  • Page 396 APS (Application Plus Server) 4.1 Users Guide 200007 200009 200014 501005 501007 501009 501011 501014 501015 501016 501017 503000 503002 503003 503005 503007 503008 505003 505004 505006 505007 505008 505009 506001 506008 506009 506010 506012 508006 508007 517000 517001 517004 517005 517008 518017...
  • Page 397 EBCDIC status log electronic version of this book ending an Informix session administration advantages and ICC application backups cabling components configuration file modifications connectivity error logging executing features hardware assembly hardware base hardware installation installation installing number of APSs supported overview platform processing cycle...
  • Page 398 APS (Application Plus Server) 4.1 Users Guide hostnames,administering image restore implementing a passive alarm monitoring system Import item importing data application specific utilities overview scripts incoming scripts Informix manuals quitting restore starting Informix 7.3 advantages initialization on reboot inserting entries to the database installation config file phase I install...
  • Page 399 logger manager overview starting and stopping starting and stopping manually status manual backups manually starting a script group or application measuring system performance menu interface MicroLegend interface modifying cron tasks ERP configuration file profiles module types of alarms monitoring a script with X.25 trace tool script session scripts, script groups and applications, overview...
  • Page 400 APS (Application Plus Server) 4.1 Users Guide Auto Restart Option buttons at bottom description Disable option HLR Server options OSA Server options Script Type option server Enable options SMPP options SS7 Enable options Type 40 Mailbox Number profile window TCP/IP enable option profiles creating deleting...
  • Page 401 creating deleting a script from a script group shutting down starting and stopping starting manually stopping script information viewing Script menu Delete item New item Open item Print item Quit item Script Profile Window script sessions monitoring script tracer Script Type option scripts administrative copying...
  • Page 402 APS (Application Plus Server) 4.1 Users Guide configuring constructs ERP installation tapes installing the application licensing software installation generating reports placing test calls upgrade from 3.x to 4.1 software troubles call tracing TCAP messages can’t load SS7 drivers can’t start application manager loss of system heartbeat software upgrades from 4.0 to 4.1...
  • Page 403 starting starting and stopping support symptoms alarm 60000 does not occur as it should application is not available application not available message applications on APS cannot start callers can’t get through calls will not go through the application can’t access PPP can’t load the SS7 driver can’t open the virtual circuit down mailbox greeting...
  • Page 404 APS (Application Plus Server) 4.1 Users Guide trademarks troubleshooting call tracing TCAP messages can’t load SS7 driversr can’t start application manager cards and cables checking the status of the links cleaning the tape drive common procedures connectivity between APS and HLR connectivity between APS and LAN/WAN connectivity between APS and modem...
  • Page 405 working with profiles X.25 card replacing X.25 link number X.25 links configuring setting up shutting down status X.25 tool addressing CUG and facilities LAPB/WAN parameters link editor link modes routing special starting throughput timers and counter using X.32 authentication X.32 authentication of X.25 tool Xspan box Year 2000...
  • Page 406 APS (Application Plus Server) 4.1 Users Guide 101-1830-001 Issue 1.0...

This manual is also suitable for:

Ap-4Ap-5Ap-6

Table of Contents