Database Administration - SEAS User's Guide describes the procedures that can be performed from the Signaling Engineering and Administration Center (SEAC) or a Signaling Network Control Center (SNCC) to configure the EAGLE. These procedures contain these items:

• A brief description of the procedure
• A reference to the EAGLE procedure in either Database Administration - SS7 User's Guide, Database Administration - GWS User's Guide, or Database Administration - GTT User's Guide that contains more information on that procedure.
• A flowchart showing the order that the tasks must be performed.
• A list of any EAGLE command parameters that SEAS does not support.

It is possible for two or more users to make changes to the same database element at any time during their database administration sessions. It is strongly recommended that only one user at a time make any changes to the database.

For those tasks that are compatible with SEAS, the flowchart contains a description of the task to be performed. For those tasks that are not compatible with SEAS, the flowchart uses the EAGLE command and parameters with the SEAS FLOW-THRU command to describe the task to be performed. If more information on the EAGLE commands is needed, go to the Commands User's Guide to find the required information.

The SEAS can be configured over Telnet as well as SSH.

The SEAS Forwarder Script allows the EAGLE SEAS client to connect, via SSH, to the SEAS server running this script. Refer to GitHub site to download the SEAS Forwarder Script.

For installation instructions on SEAS Forwarder Script, refer to SEAS Installation .

Procedures that contain the following requirements cannot be performed from the SEAS interface:

• Procedures that use a removable cartridge or removable media (with the E5-MASP) cannot be performed from the SEAC or SNCC because the removable cartridge or removable media can only be inserted or removed at the EAGLE’s location.
• Procedures that require using security administration commands because the EAGLE does not allow security administration commands to be executed from the SEAS interface.
• Procedures that require SEAS terminals to be placed out of service. This would not allow the SEAS interface to communicate with the EAGLE, so these procedures cannot be performed from the SEAS interface.
• Procedures that use EAGLE commands that have no SEAS equivalent commands to perform all the steps in the procedure, or that reference other procedures not included in this manual. To perform these procedures, go to either Database Administration - SS7 User's Guide, Database Administration - GWS User's Guide, or Database Administration - GTT User's Guide and perform these procedures using the SEAS FLOW-THRU command with the EAGLE commands.

The following is a list of the procedures contained in Database Administration - SS7 User's Guide, Database Administration - GWS User's Guide, or Database Administration - GTT User's Guide that are not included in this manual because they cannot be performed using SEAS commands.

Database Administration Manual - SS7

• These procedures in Chapter 2, “Configuring Destination Tables”
  • Changing the DPC Quantity
  • Changing the Format of ITU National Point Codes
  • Activating the ITU National and International Spare Point Code Support Feature
  • Adding a Point Code to the Self-Identification of the EAGLE
  • Adding a Secondary Point Code
  • Removing a Secondary Point Code
  • Changing the Group Code Assigned to an ITU National Point Code
  • Changing the Proxy Point Code Quantity
• These procedures in Chapter 3, “SS7 Configuration”
  • Enabling the Large System # Links Controlled Feature
  • Using Proxy Point Codes and Secondary Point Codes when Adding a Linkset
  • Activating the SLS Bit Rotation by Incoming Linkset Feature
  • Verifying the New Adjacent Point Code or New Secondary Point Code for a Linkset
  • Using the MULTGC Parameter when Changing the Attributes of a Linkset
  • Configuring an ITU Linkset with a Secondary Adjacent Point Code (SAPC)
  • Removing a Route
  • Changing Level 2 Timers
  • Changing Level 3 Timers
  • Changing a Signaling Link Test Message
  • Configuring Circular Route Detection
  • Configuring the TFA/TFR Pacing Rate
  • Configuring the Frequency of RST Messages on Low Priority Routes
  • Adding Remote Loopback Points
  • Removing Remote Loopback Points
  • Changing Remote Loopback Points
  • Configuring the EAGLE for Random SLS Generation
  • Configuring the Options for the TDM Global Timing Interface
  • Configuring the Restricted Linkset Option
  • Configuring the Options for Handling TFCs on ITU-I and ITU-N Networks
  • Changing the High-Capacity Card Temperature Alarm Thresholds
  • Activating the MTP Origin-Based Routing Feature
  • Configuring the MTP Origin-Based Routing SCCP OPC Option
  • Adding an Exception Route Entry
  • Removing a Route Exception Entry
  • Changing a Route Exception Entry
  • Activating the Circular Route Auto-Recovery Feature
  • Turning the Circular Route Auto-Recovery Feature Off
  • Activating the Enhanced Far-End Loopback Detection Feature
  • Turning the Enhanced Far-End Loopback Detection Feature Off
  • Activating the Multiple Linksets to Single Adjacent PC (MLS) Feature
  • Configuring the ITU Linkset NI Mapping Options
  • Configuring the Option for Handling Message Priorities for Messages Crossing into ITU-I and ITU-N
  • Activating the 6-Way Load Sharing on Routesets Feature
• All the procedures in Chapter 4, “Point Code and CIC Translation Configuration.”
• All the procedures in Appendix A, “E1 Interface.”
• All the procedures in Appendix B, “T1 Interface,” except the “Adding a T1Signaling Link,” procedure. The procedure for configuring T1 signaling links is included in the Adding an SS7 Signaling Link procedure.
• All the procedures in Appendix C, “ATM Signaling Link Configuration,” except the “Adding an ATM High-Speed Signaling Link,” procedure. This procedure issued to configure both ANSIATM and E1 ATM high-speed signaling links. The procedure for configuring ANSI ATM High-Speed signaling links is included in the Adding an SS7 Signaling Link procedure. The EAGLE can also have E1 ATM High-Speed signaling links. The configuration of these signaling links is not supported by SEAS.
• The Configuring the MFC Option procedure located in Appendix D, "Reference Information."

Database Administration Manual - Gateway Screening

• These procedures in Chapter 2, “Gateway Screening (GWS) Overview”
  • Adding a GLS Card
  • Removing a GLS Card
  • Configuring Gateway Screening Stop Action Sets
  • Configuring TLNP Gateway Screening Stop Action Sets
  • Removing Gateway Screening Stop Action Sets
  • Activating the MTP Routed GWS Stop Action Feature
  • Turning the MTP Routed GWS Stop Action Feature Off
• All the procedures in Chapter 13, “Screen Set Configuration”
• All the procedures in Chapter 14, “Calling Name Conversion Facility (CNCF) Configuration”

Database Administration Manual - Global Title Translation

• These procedures in Chapter 2, “Global Title Translation (GTT) Overview”
  • Adding a Service Module
  • Removing a Service Module
  • Configuring the MFC Option
  • Adding a Mapped SS7 Message Translation Type
  • Removing a Mapped SS7 Message Translation Type
  • Changing a Mapped SS7 Message Translation Type
  • Adding a Concerned Signaling Point Code
  • Removing Concerned Signaling Point Codes
  • Provisioning a Solitary Mated Application
  • Provisioning a Load Shared Mated Application
  • Provisioning a Combined Dominant/Load Shared Mated Application
  • Changing the Mated Application Type
  • Changing the Weight and In-Service Threshold Values of a Mated Application
  • Changing the MRNSET and MRN Point Code Values of MAP Entries
  • Provisioning MRN Entries
  • Removing MRN Entries
  • Changing the Relative Cost Values of MRN Entries
  • Changing MRN Entries with the ESWT Parameter
  • Changing the Weight and Threshold Values of MRN Entries
  • Adding a GT Conversion Table Entry
  • Removing a GT Conversion Table Entry
  • Changing a GT Conversion Table Entry
  • Changing the ANSI-ITU-China SCCP Conversion Options
  • Changing the ANSI/ITU SCCP Conversion Options
  • Changing SCCP Class 1 Sequencing Option
  • Changing the SCCP Alarm Thresholds
  • Changing the Transaction-Based GTT Load Sharing Options
  • Adding a Loopset
  • Removing a Loopset
  • Changing the Attributes of a Loopset
  • Configuring the ANSI to ITU-N SCCP Conversion Option
  • Configuring an SCCP Test Message
  • Adding Global Title Modification Information
  • Removing Global Title Modification Information
  • Changing Global Title Modification Information
• These procedures in Chapter 3, “ (GTT) Configuration”
  • Adding a Translation Type
  • Removing a Translation Type
• These procedures in Chapter 4, “Enhanced Global Title Translation (EGTT) Configuration”
  • Adding a GTT Set
  • Removing a GTT Set
  • Changing a GTT Set
  • Adding a GTT Selector
  • Removing a GTT Selector
  • Changing a GTT Selector
  • Changing the Default GTT Mode Options
  • Adding a GTT Action
  • Removing a GTT Action
  • Changing a GTT Action
  • Adding a GTT Action Set
  • Removing a GTT Action Set
  • Changing a GTT Action Set
  • Adding a GTT Action Path
  • Removing a GTT Action Path
  • Changing a GTT Action Path
• All the procedures in Appendix A, “Controlled Feature Activation Procedures”
• All the procedures in Appendix B, “MO SMS B-Party Routing Configuration Procedures"
• All the procedures in Appendix C, “MO SMS Prepaid Intercept on B-Party Configuration Procedures"

This manual is intended for database administration personnel or translations personnel in the Signaling Engineering and Administration Center (SEAC) or the Signaling Network Control Center (SNCC) to create, modify, display, and maintain the EAGLE database, and to configure the EAGLE.

For more information, refer to the following documents:

• Database Administration - SS7 User's Guide
• Database Administration - GWS User's Guide
• Database Administration - GTT User's Guide

The Maintenance and Administration Subsystem (MAS) is the central management point for the EAGLE. The MAS provides user interface, maintenance communication, peripheral services, alarm processing, system disk interface, and measurements. Management and redundancy are provided by use of two separate subsystem processors.

The MAS resides on two separate sets of Maintenance and Administration Subsystem Processor (MASP) cards and a Maintenance Disk and Alarm card (collectively referred to as control cards). The control cards are located in slots 1113 through 1118 of the EAGLE control shelf. The control cards must be E5-based cards.

The data that the EAGLE uses to perform its functions are stored in two separate areas: the fixed disk drives, and the removable media. The following sections describe these areas and data that is stored on them. These areas and their partitions are shown in Figure 1-1.