1. Database Administration - IP7 User's Guide
  2. IETF M2PA Configuration Procedures
  3. Adding IETF IPLIMx Components

Adding IETF IPLIMx Components

This section describes how to configure the components necessary to establish IP connections using M2PA associations on IPLIMx signaling links. IPLIMx signaling links are signaling links assigned to cards running either the IPLIM or IPLIMI applications. The IPLIM application supports point-to-point connectivity for ANSI networks. The IPLIMI application supports point-to-point connectivity for ITU networks.

The configuration of these IP connections consists of these items.

  1. Configure the IPLIMx card with the Adding an IPLIMx Card procedure.
  2. Configure the required destination point codes - see Chapter 2, “Configuring Destination Tables,” in Database Administration - SS7 User's Guide.
  3. Configure the required IPLIMx linksets - see Chapter 3, “SS7 Configuration,” in Database Administration - SS7 User's Guide.
  4. Configure the IPLIMx signaling links with the Adding an IPLIMx Signaling Link procedure. The ipliml2=m2pa parameter of the ent-slk command must be specified for these signaling links. If the addition of these signaling links will exceed the current number of signaling links the EAGLE is allowed to have, the Enabling the Large System # Links Controlled Feature procedure will have to be performed to increase the quantity of signaling links.
  5. Configure the required routes - see Chapter 3, “SS7 Configuration,” in the Database Administration - SS7 User's Guide.
  6. IP addresses must be assigned to the IPLIMx card configured in step 1 by performing the Configuring an IP Link procedure. There are other IP link parameters that are assigned to the IPLIMx card when the IPLIMx card is configured. Default values are assigned to these parameters when the IPLIMx card is configured. These values can be displayed by the rtrv-ip-lnk command. These values can be changed by performing the Configuring an IP Link procedure.
  7. Local IP hosts, assigned to the IP addresses assigned to step 6, must be configured in the database by performing the Adding an IP Host procedure. Verify the hosts with the rtrv-ip-host command. This establishes a relationship between the IP card related information and the connection related information.
  8. When the IP cards are added to the database in step 1, there are IP parameters that control the IP stack that are assigned default values. These parameter values can be displayed by the rtrv-ip-card command. These values can be changed by performing the Configuring an IP Card procedure.
  9. Static IP routes provide more flexibility in selecting the path to the remote destination and reduces the dependence on default routers. Static IP routes are provisioned by performing the Adding an IP Route procedure.
  10. Associations specify a connection between a local host/TCP port and a remote host/TCP port. Three types of associations can be provisioned: M2PA, M3UA, and SUA. Associations that are assigned to IPLIMx signaling links must be M2PA associations. The ipliml2=m2pa parameter must be assigned to the signaling link that is assigned to an M2PA association. The M2PA association is configured by performing the Adding an M2PA Association procedure. M3UA and SUA associations are provisioned with the Adding an M3UA or SUA Association procedure. Associations can be assigned to IPSG signaling links also. These associations are configured by performing the Adding an IPSG M2PA Association or Adding an IPSG M3UA Association procedures. A number of fields in the association cannot be configured with the Adding an M2PA Association procedure and are set to default values. The values of these fields can be displayed using the rtrv-assoc command after the Adding an M2PA Association procedure is performed. These values can be changed by performing the Adding an M2PA Association procedure. An IPLIMx card can have one association for each signaling link assigned to the card.

  11. There are two versions of M2PA associations, RFC and Draft 6, that can be configured in the database. When an M2PA association is added to the database with Adding an M2PA Association procedure, the association is configured as an RFC M2PA association. The RFC version of M2PA timer set 1 is also assigned to the association when the M2PA association is added to the database.

    There are two different versions, RFC and Draft 6, of M2PA timer sets that can be assigned to M2PA associations. Each version of the M2PA timer sets contains 20 timer sets. The values of these timer sets can be changed with the Changing a M2PA Timer Set procedure.

    The version of the M2PA association and the M2PA timer set assigned to the association can be changed with Adding an M2PA Association procedure. The M2PA version of the association determines the version of the M2PA timer set that is assigned to the association. For example, if M2PA timer set 3 is assigned to the M2PA association, and the association is an RFC M2PA association, the RFC version of M2PA timer set 3 is used with the association. If M2PA timer set 7 is assigned to the M2PA association, and the association is a Draft 6 M2PA association, the Draft 6 version of M2PA timer set 7 is used with the association.

  12. The EAGLE processes messages with a service information field (SIF) that is 272 bytes or smaller. The Large MSU Support for IP Signaling feature allows the EAGLE to process messages with a service indicator value of 6 to 15 and with a SIF that is larger than 272 bytes. Perform the Activating the Large MSU Support for IP Signaling Feature procedure to enable and turn on the Large MSU Support for IP Signaling feature.