Go to primary content
Oracle® Communications EAGLE SIGTRAN User's Guide
Release 46.6
E97352 Revision 1
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

Configure the IPGWx Application

This section provides a basic overview of the steps involved to provision the IPGWx application for M3UA. For detailed procedures, see Database Administration - IP7 User's Guide of your current EAGLE documentation suite.

  1. Enable the feature with the part number and feature access key (FAK) (enable-ctrl-feat).

    IPGWx IP TPS implies a true system limit. Each IPGWx linkset will have a configurable “linkset IP TPS," and the total of all the provisioned linkset IP TPS values must be less than or equal to the IPGWx system IP TPS.

  2. To help manage IPGWx system IP TPS, view the system-wide IP TPS usage (rept-stat-iptps).
  3. Declare the E5-ENET or E5-ENET-B to be ipgwx (ent-card).
  4. Enter the virtual point code (ent-dstn).

    To create a virtual IPGWx SS7 link, first create an SS7 linkset and an Adjacent Point Code (APC).

    The adjacent node functionality for an IPGWx linkset is performed by the IPGWx software to provide SS7-to-IP interworking. For this reason, IPGWx APCs are referred to as “adjacent” point codes. Syntaxes that are normally not allowed for point codes, such as 0-0-1, are allowed for virtual adjacent point codes to minimize depletion of point code space. In addition, beginning with EAGLE 34.0, private point codes can be utilized (and are recommended by Oracle Communications) for IPGWx APCs. Private point codes are used for internal routing within the EAGLE and are not known outside of the EAGLE. By making APCs private, it is possible to have a point code value indicated as private and still have the same point code value (as not private) available for network configuration.

  5. Define bandwidth and use alarm (ent-ls).
  6. Tell the EAGLE that this is a SIGTRAN M3UA link (ent-slk).
  7. Enter SEP point codes (ent-dstn).
  8. Enter route (ent-rte).
  9. Define the IP settings for the Ethernet port (chg-ip-lnk).
  10. Associate an IP address to a host name that will be used in configuring the association (entip- host).
  11. Define the network devices that the DCM card will access (chg-ip-card).
  12. Enter an Application Server Process and bind an SCTP association with it (ent-assoc).
  13. Define the IP settings for the Ethernet port (chg-ip-lnk).
    Enter an Application Server Process and bind an SCTP association with it (ent-assoc)

    Multihomed end points are SCTP associations configured with both the LHOST and ALHOST parameters specified. In this case, the LHOST represents an IP address corresponding to one of the network interfaces (A or B) of the IP application card, while the ALHOST represents an IP address corresponding to the other network interface of the same IP application card.

    This command includes the rmin and rmax parameters.

  14. Enter an Application Server Process and bind an SCTP association with it (ent-assoc).
  15. Associate a routing key to an association name (ent-as).

    An Application Server is a logical entity serving a specific routing key or set of routing keys. The first ent-as command entered creates the Application Server, and subsequent ent-as commands add additional associations to the existing Application Server.

  16. Set the network context for the message, either for the Signaling Gateway process (SGP) or application server process (ent-na).
  17. Allow card (alw-card).
  18. Activate signaling link (act-slk).