1. EAGLE Database Administration - IP7 User's Guide
  2. IETF M2PA Configuration Procedures

3 IETF M2PA Configuration Procedures

Chapter 3, IETF M2PA Configuration Procedures, describes the procedures necessary to configure the components necessary to establish IP connections using M2PA associations on IPLIMx signaling links.

3.1 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.

3.2 Adding an IPLIMx Card

This procedure is used to add an IPLIMx card to the database using the ent-card command. An IPLIMx card runs either the IPLIM or IPLIMI applications. A maximum of 100 IPLIMx cards can be provisioned in the database. Table 3-1 shows the cards that can be provisioned in this procedure.

Table 3-1 IPLIMx Card Types

Card Type Part Number
E5-ENET 870-2212-xx
E5-ENET-B 870-2971-xx

The EAGLE can support a combination of E5-ENET and E5-ENET-B cards.

The ent-card command uses these parameters.

:loc – The location of the card being added to the database.

:type – The type of card being added to the database. For this procedure, the value of this parameter is dcm.

:appl – The application software that is assigned to the card. For this procedure, the value of this parameter is iplim for ANSI IP network connections or iplimi for ITU IP network connections.

:force – If the global title translation feature is on, the force=yes parameter allows the LIM to be added to the database even if the current SCCP transactions-per-second threshold is unable to support the additional SCCP transaction-per-second capacity created by adding the IP card. This parameter is obsolete and is no longer used.

Card Slot Selection

The E5-ENET card can be inserted into any card slot, except for card slots that must remain empty to accommodate dual-slot cards, slots 09 and 10 in each shelf, and slots 1113 through 1118.

To provision a E5-ENET card, the shelf containing the E5-ENET card must have HIPR2 cards installed in slots 9 and 10 in that shelf. If HIPR2 cards are not installed in the shelf that the E5-ENET card will occupy, the E5-ENET card will be auto-inhibited when the E5-ENET card is inserted into the shelf. Enter the rept-stat-gpl:gpl=hipr2 command to verify whether or not HIPR2 cards are installed in the same shelf as the E5-ENET card being provisioned in this procedure.

Before adding an IPLIMx card, the Eagle STP must have a fan unit, and the fan feature must be turned on. Also, the MFC STP option must be on.

  1. Display the cards in the database using the rtrv-card command.

    This is an example of the possible output. Cards should be distributed throughout the EAGLE for proper power distribution. Refer to Installation Guide for the shelf power distribution. 

    rlghncxa03w 09-05-05 08:12:53 GMT  41.0.0
CARD   TYPE      APPL      LSET NAME     LINK SLC LSET NAME     LINK SLC
1101   DSM       VSCCP     
1102   TSM       GLS       
1113   GSPM      EOAM
1114   TDM-A
1115   GSPM      EOAM
1116   TDM-B
1117   MDAL
1201   LIMDS0    SS7ANSI   sp2           A    0   sp1           B    0
1203   LIMDS0    SS7ANSI   sp3           A    0   
1204   LIMDS0    SS7ANSI   sp3           A    1   
1206   LIMDS0    SS7ANSI   nsp3          A    1   nsp4          B    1 
1301   LIMDS0    SS7ANSI   sp6           A    1   sp7           B    0
1302   LIMDS0    SS7ANSI   sp7           A    1   sp5           B    1
1303   DCM       IPLIM     ipnode1       A    0   ipnode3       B    1
1305   DCM       IPLIM     ipnode4       A    0   
2101   ENET      IPSG
2103   ENET      IPSG
2105   ENET      IPSG
2107   ENET      IPSG
2201   DCM       IPLIM
2203   DCM       IPLIM
2207   DCM       IPLIM
2211   DCM       SS7IPGW
2213   DCM       SS7IPGW
2215   DCM       IPGWI
2217   DCM       IPGWI
2301   DCM       SS7IPGW
2303   DCM       SS7IPGW
2305   DCM       IPGWI
2307   DCM       IPGWI
2311   DCM       IPLIMI
2313   DCM       IPLIMI
    Continue the procedure by performing one of these steps.
    • If the required unprovisioned card slots (see the section Card Slot Selection) are shown in the rtrv-card output, continue the procedure with 4.
    • If the required unprovisioned card slots are not shown in the rtrv-card output, 2 must be performed.
  2. Display the shelves in the database by entering the rtrv-shlf command. This is an example of the possible output. 
    rlghncxa03w 08-03-05 08:12:53 GMT  38.0.0
SHELF DISPLAY
FRAME SHELF        TYPE
  1     1       CONTROL
  1     2       EXTENSION
  1     3       EXTENSION
  2     1       EXTENSION
  2     2       EXTENSION
  2     3       EXTENSION

    If all the shelves are provisioned in the database, then the remainder of this procedure cannot be performed. There are no available card slots for the new IPLIMx card.

    If all the shelves have not been provisioned in the database, continue the procedure with 3.

  3. Add the required shelf using the ent-shlf command with the location of the shelf and the type=ext parameter. The shelf location values are 1200, 1300, 2100, 2200, 2300, 3100, 3200, 3300, 4100, 4200, 4300, 5100, 5200, 5300, and 6100. For this example, enter this command.

    ent-shlf:loc=3100:type=ext

    When this command has successfully completed, this message should appear. 

    rlghncxa03w 07-05-01 09:12:36 GMT  EAGLE5 37.0.0
ENT-SHLF: MASP A - COMPLTD
  4. Verify that the card to be entered has been physically installed into the proper location (see the section Card Slot Selection).

    Caution:

    If the versions of the flash GPLs on the IPSG card do not match the flash GPL versions in the database when the IPSG card is inserted into the card slot, UAM 0002 is generated indicating that these GPL versions do not match. If UAM 0002 has been generated, perform the alarm clearing procedure for UAM 0002 in Maintenance Guide before proceeding with this procedure.

    Note:

    If the card being added in this procedure is not an E5-ENET card, continue the procedure with 10.
  5. Verify that HIPR2 cards are installed in card locations 9 and 10 in the shelf containing the E5-ENET card being added in this procedure. Enter this command.

    rept-stat-gpl:gpl=hipr2

    This is an example of the possible output. 

    
rlghncxa03w 09-07-05 08:12:53 GMT  41.1.0
GPL        CARD      RUNNING            APPROVED      TRIAL
HIPR2      1109      132-002-000        132-002-000   132-003-000
HIPR2      1110      132-002-000        132-002-000   132-003-000
HIPR2      1209      132-002-000        132-002-000   132-003-000
HIPR2      1210      132-002-000        132-002-000   132-003-000
HIPR2      1309      132-002-000        132-002-000   132-003-000
HIPR2      1310      132-002-000        132-002-000   132-003-000
HIPR2      2109      132-002-000        132-002-000   132-003-000
HIPR2      2110      132-002-000        132-002-000   132-003-000
HIPR2      2209      132-002-000        132-002-000   132-003-000
HIPR2      2210      132-002-000        132-002-000   132-003-000
HIPR2      2309      132-002-000        132-002-000   132-003-000
HIPR2      2310      132-002-000        132-002-000   132-003-000
Command Completed

    If HIPR2 cards are installed in the shelf containing the E5-ENET card, continue the procedure with 10.

    If HIPR or HIPR2 cards are not installed on the shelf containing the E5-ENET card, go to Installation Guide and install the HIPR2 cards. Once the HIPR2 cards have been installed, continue the procedure with 10.

  6. Enter the rtrv-stpopts command to verify whether or not the MFC option is on.

    This is an example of the possible output. 

    

rlghncxa03w 11-10-17 16:02:05 GMT EAGLE5 44.0.0
STP OPTIONS         
---------------------------
MFC                     off

    The rtrv-stpopts command output contains other fields that are not used by this procedure. To see all fields displayed by the rtrv-stpopts command, see the rtrv-stpopts command description in Commands User's Guide.

    If the MFC option is off, perform the Configuring the MFC Option procedure in Database Administration - System Management User's Guide to turn on the MFC option.

    If the MFC option is on or the MFC Option procedure in Database Administration - System Management User's Guide was performed in this step, continue the procedure with 7.

    The Fan feature must be purchased before you turn this feature on with the chg-feat command. If you are not sure if you have purchased the Fan feature, contact your Sales Representative or Account Representative.

  7. Enter the rtrv-feat command to verify that the Fan feature is on.

    If the Fan feature is on, shown in either the rtrv-feat output in this step or in 7, continue this procedure with 9.

    If 7 was not performed, the FAN field should be set to on.

    The rtrv-feat command output contains other fields that are not used by this procedure. To see all fields displayed by the rtrv-feat command, see the rtrv-feat command description in Commands User's Guide.

    If the Fan feature is off, continue the procedure with 8.

  8. Turn the Fan feature on by entering this command.

    chg-feat:fan=on

    Note:

    Once the Fan feature is turned on with thechg-feat command, it cannot be turned off.

    When the chg-feat has successfully completed, this message appears. 

    
rlghncxa03w 11-10-28 11:43:04 GMT EAGLE5 44.0.0
CHG-FEAT: MASP A - COMPLTD
  9. The shelf containing the E5-ENET-B card that is being added in this procedure must have fans installed. Verify whether or not fans are installed on the shelf.

    If the fans are installed, continue the procedure with 10.

    If the fans are not installed on the shelf containing the E5-ENET-B card, go to Installation Guide and install the fans. After the fans have been installed and tested, continue the procedure with 10.

  10. Add the card using the ent-card command. For this example, enter these commands.

    ent-card:loc=1311:type=dcm:appl=iplim

    ent-card:loc=1313:type=dcm:appl=iplimi

    When each of these commands have successfully completed, this message should appear. 

    
rlghncxa03w 06-10-12 09:12:36 GMT EAGLE5 36.0.0
ENT-CARD: MASP A - COMPLTD
  11. Verify the changes using the rtrv-card command with the card location specified in 10. For this example, enter these commands.

    rtrv-card:loc=1311

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CARD   TYPE      APPL      LSET NAME     LINK SLC LSET NAME     LINK SLC
1311   DCM       IPLIM

    rtrv-card:loc=1313

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CARD   TYPE      APPL      LSET NAME     LINK SLC LSET NAME     LINK SLC
1313   DCM       IPLIMI
  12. Back up the new changes using the chg-db:action=backup:dest=fixed command. These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-1 Adding an IPLIMx Card



Sheet 1 of 3



Sheet 2 of 3



Sheet 3 of 3

3.3 Adding an IPLIMx Signaling Link

This procedure is used to add an IPLIMx signaling link to the database using the ent-slk command. The ent-slk command uses these parameters.

:loc – The card location of the IP card that the IP signaling link will be assigned to. The cards specified by this parameter are IP cards running the IPLIM or IPLIMI applications.

:link – The signaling link on the card specified in the loc parameter.

:lsn – The name of the linkset that will contain the signaling link.

:slc – The signaling link code. The SLC must be unique within the linkset. It must be the same at both the EAGLE location and the distant node.

:ipliml2 – The L2 protocol stack to be assigned to the IP signaling link, M2PA (the default value).

The ent-slk command contains other optional parameters that are not used to configure an IPGWx signaling link. These parameters are discussed in more detail in Commands User's Guide or in these sections.

These items must be configured in the database before an IP signaling link can be added:

  • Shelf – perform the "Adding a Shelf" procedure in Database Administration - System Management User's Guide
  • Card – perform the Adding an IPLIMx Card procedure
  • Destination Point Code – perform the “Adding a Destination Point Code” procedure in Database Administration - SS7 User's Guide.
  • Linkset – An IPLIMx signaling link can be assigned to any linkset that does not contain IPGWx signaling links . Perform one of these procedures to add the linkset.

Adding the IPLIMx signaling link to an IPLIMx card that does not contain any IPLIMx signaling links cannot exceed the maximum total provisioned system TPS shown in the rtrv-tps output. An IPLIMx card that contains IPLIMx signaling links uses 4000 TPS. If the IPLIMx signaling link is being added to an IPLIMx card that contains other signaling links, no additional TPS is used and the maximum total provisioned system TPS shown in the rtrv-tps output will not be exceeded.

If adding the IPLIMx signaling link will exceed the maximum total provisioned system TPS, and the maximum total provisioned system TPS is 500,000, perform the "Activating the HIPR2 High Rate Mode" feature in Database Administration - System Management User's Guide to enable and turn on the HIPR2 High Rate Mode feature. When the HIPR2 High Rate Mode feature is enabled and turned on, the maximum total provisioned system TPS is increased to 1,000,000 (1M). If the maximum total provisioned system TPS is 1M, or the maximum total provisioned system TPS is 500,000 and will not be increased, and adding the IPLIMx signaling link will exceed the maximum total provisioned system TPS, the IPLIMx signaling link cannot be added unless the amount of available TPS is reduced enough to allow the IPLIMx signaling link to be added. The available TPS can be reduced by performing one or more of these actions.
  • The IP TPS values of some IPGWx linksets have to be changed.
  • The MAXSLKTPS values of some IPSG linksets (and the RSVDSLKTPS values if necessary) have to be changed.
  • Some ATM high-speed signaling links have to be removed.
  • An IPLIMx card that contains signaling links has to be removed.

Verify that the link has been physically installed (all cable connections have been made).

To configure the EAGLE to perform circular routing detection test on the signaling links, “Configuring Circular Route Detection” procedure in the Database Administration - SS7 User's Guide.

Note:

Circular route detection is not supported in ITU networks.

To provision a EAGLE with more than 1200 signaling links, the EAGLE must have certain levels of hardware installed. See the Requirements for EAGLEs Containing more than 1200 Signaling Links section for more information on these hardware requirements.

The EAGLE can contain a mixture of low-speed, E1, T1, ATM high-speed, and IP signaling links. The Determining the Number of High-Speed and Low-Speed Signaling Links section describes how to determine the quantities of the different types of signaling links the EAGLE can have.

Canceling the REPT-STAT-SLK, RTRV-LS, and RTRV-SLK Commands

Because the rept-stat-slk, rtrv-ls, and rtrv-slk commands used in this procedure can output information for a long period of time, the rept-stat-slk, rtrv-ls, and rtrv-slk commands can be canceled and the output to the terminal stopped. There are three ways that the rept-stat-slk, rtrv-ls, and rtrv-slk commands can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rept-stat-slk, rtrv-ls, or rtrv-slk commands were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rept-stat-slk, rtrv-ls, or rtrv-slk commands were entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rept-stat-slk, rtrv-ls, or rtrv-slk commands were entered, from another terminal other that the terminal where the rept-stat-slk, rtrv-ls, or rtrv-slk commands was entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

  1. Display the maximum number of signaling links the EAGLE can have and the number of signaling links that are currently provisioned by entering the rtrv-tbl-capacity command.

    This is an example of the possible output. 

    
rlghncxa03w 09-07-19 21:16:37 GMT EAGLE5 41.1.0

SLK      table is (        4 of      1200)   1% full

    Note:

    Thertrv-tbl-capacity command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-tbl-capacity command, refer to thertrv-tbl-capacitycommand description inCommands User's Guide.

    If the addition of the new signaling link will not exceed the maximum number of signaling links the EAGLE can have, continue the procedure with 2.

    If the addition of the new signaling link will exceed the maximum number of signaling links the EAGLE can have, and the maximum number of signaling links is less than 2800, perform the Enabling the Large System # Links Controlled Feature procedure to enable the desired quantity of signaling links. After the new quantity of signaling links has been enabled, continue the procedure with 2.

    If the addition of the new signaling link will exceed the maximum number of signaling links the EAGLE can have (in this example, the maximum number of signaling links is 1200), and the maximum number of signaling links is 2800, this procedure cannot be performed. The EAGLE cannot contain more than 2800 signaling links.

  2. Display the total provisioned system TPS by entering the rtrv-tps command. This is an example of the possible output. 
    
rlghncxa03w 10-07-10 16:20:46 GMT  EAGLE 42.0.0

CARD     NUM    NUM      RSVD       MAX
TYPE   CARDS  LINKS       TPS       TPS
-----  -----  -----  --------  --------
IPGW      17     16     48000     80000
IPSG       3      7      4200      8000
IPLIM      2      4      8000      8000
ATM        2      2      3668      3668

Total provisioned System TPS (99668 of 500000) 20%

Command Completed.
  3. Display the cards in the database using the rtrv-card command.

    This is an example of the possible output. 

    
rlghncxa03w 13-06-28 09:12:36 GMT EAGLE5 45.0.0
CARD   TYPE      APPL     LSET NAME   LINK SLC LSET NAME   LINK SLC
1101   DCM       SS7IPGW  ipgwx1      A    0
1102   DCM       SS7IPGW  ipgwx1      A    1
1103   DCM       SS7IPGW  ipgwx1      A    2
1104   DCM       SS7IPGW  ipgwx1      A    3
1105   DCM       SS7IPGW  ipgwx1      A    4
1106   DCM       SS7IPGW  ipgwx1      A    5
1107   DCM       SS7IPGW  ipgwx1      A    6
1108   DCM       SS7IPGW  ipgwx1      A    7
1111   DCM       SS7IPGW  ipgwx2      A    0
1112   DCM       SS7IPGW  ipgwx2      A    1
1113   E5MCAP    OAMHC
1114   E5TDM-A
1115   E5MCAP    OAMHC
1116   E5TDM-B
1117   E5MDAL
1201   DCM       SS7IPGW  ipgwx2      A    2
1202   DCM       SS7IPGW  ipgwx2      A    3
1203   DCM       SS7IPGW  ipgwx2      A    4
1204   DCM       SS7IPGW  ipgwx2      A    5
1205   DCM       SS7IPGW  ipgwx2      A    6
1206   DCM       SS7IPGW  ipgwx2      A    7
1207   DSM       VSCCP    
1208   TSM       GLS     
1301   DCM       IPLIM    lsniplim    A    0   lsniplim    A1   1
                          lsniplim    B1   2
1302   LIMATM    ATMANSI
1303   ENET      IPSG     ipsglsn     A    0   ipsglsn     A1   1
                          ipsglsn     B1   2   ipsglsn     A2   3
                          ipsglsn     A3   4   ipsglsn2    B3   0
1304   LIMATM    ATMANSI
1305   LIMATM    ATMANSI  lsnds0      A    1
1306   LIME1ATM  ATMITU   lsnituatm   A    0
1307   ENET      IPSG     ipsglsn     A    5
1311   DCM       IPLIM
1312   LIMDS0    SS7ANSI  lsnds0      A    0
1317   DCM       IPLIMI   lsniplimi   A    0
1318   LIMATM    ATMANSI

    If the required card is not in the database, perform the Adding an IPLIMx Card procedure and add the IPLIMx card to the database.

    Note:

    If the linkset that the signaling link will be added to contains themultgc=yes parameter, the application assigned to the card must be IPLIMI.

    An IPLIMx card that contains signaling links uses 4000 TPS. If the card that the new IPLIMx signaling link will be assigned to has other signaling links assigned to it (shown in the LSET NAME, LINK, and SLC columns in the rtrv-card output), continue the procedure with 8.

    If the Adding an IPLIMx Card procedure was performed in this step, or if the new signaling link will be assigned to an existing IPLIMx card that contains no signaling links, continue the procedure by performing one of these actions.
    • If adding the new IPLIMx signaling link will not exceed the maximum total provisioned system TPS, shown in 2 , continue the procedure with 8.
    • If adding the new IPLIMx signaling link will exceed the maximum total provisioned system TPS, and the maximum total provisioned system TPS is 500,000 shown, perform the "Activating the HIPR2 High Rate Mode Feature" procedure in Database Administration - System Management User's Guide to enable and turn on the HIPR2 High Rate Mode feature. When the HIPR2 High Rate Mode feature is enabled and turned on, the maximum total provisioned system TPS is increased to 1M. After the HIPR2 High Rate Mode feature has been enabled and turned on, continue the procedure with 8.
    • If the maximum total provisioned system TPS is 1M, or the maximum total provisioned system TPS is 500,000 and will not be increased, and adding the IPLIMx signaling link will exceed the maximum total provisioned system TPS, the IPLIMx signaling link cannot be added unless the amount of available TPS is reduced enough to allow the IPLIMx signaling link to be added. The available TPS can be increased by performing one or more of these actions.
      • The IP TPS values of some IPGWx linksets have to be changed. To perform this action, continue the procedure with 6.
      • The MAXSLKTPS values of some IPSG linksets (and the RSVDSLKTPS values if necessary) have to be changed. To perform this action, continue the procedure with 6.
      • Some ATM high-speed signaling links have to be removed. To perform this action, continue the procedure with 4.
      • An IPLIMx card that contains signaling links has to be removed. To perform this action, continue the procedure with 5.
  4. Display the ATM high-speed signaling links by entering this command.

    rtrv-slk:type=saal

    This is an example of the possible output. 

    
rlghncxa03w 10-07-19 21:16:37 GMT EAGLE5 42.0.0

                                  LP         ATM
LOC  LINK LSN        SLC TYPE     SET BPS    TSEL     VCI   VPI  LL
1303 A    lsnds0     1   LIMATM   1   1.544M LINE     5     0    0

                                  LP         ATM                    E1ATM
LOC  LINK LSN        SLC TYPE     SET BPS    TSEL     VCI   VPI  CRC4 SI SN
1306 A    lsnituatm  0   LIME1ATM 21  2.048M LINE     5     0    ON   3  0

SLK table is (30 of 1200) 2% full.

    If ATM high-speed signaling links are shown in the rtrv-slk output, perform the "Removing an SS7 Signaling Link" procedure in Database Administration - SS7 User's Guide to remove some of the ATM high-speed signaling links.

    If ATM high-speed signaling links are not displayed in the rtrv-slk output, perform one or more of these actions to increase the available TPS.

    Note:

    If one or more of these actions are not performed to increase the available TPS and the available TPS will not allow the IPLIMX signaling link to be added, the IPLIMx signaling link cannot be added and the remainder of this procedure cannot be performed.
    • The IP TPS values of some IPGWx linksets have to be changed. To perform this action, continue the procedure with 6.
    • The MAXSLKTPS values of some IPSG linksets (and the RSVDSLKTPS values if necessary) have to be changed. To perform this action, continue the procedure with 6.
    • An IPLIMx card that contains signaling links has to be removed. To perform this action, continue the procedure with 5.

    If you do not wish to perform other actions to increase the available TPS and the available TPS will allow the IPLIMx signaling link to be added, continue the procedure with 8.

  5. Display the signaling links that are assigned to IPLIMx cards by entering this command.

    rtrv-slk:type=iplim

    This is an example of the possible output. 

    
rlghncxa03w 10-07-19 21:16:37 GMT EAGLE5 42.0.0

LOC  LINK LSN        SLC TYPE     ANAME           SLKTPS
1301 A    lsniplim   0   IPLIM    M2PA
1301 A1   lsniplim   1   IPLIM    M2PA
1301 B1   lsniplim   2   IPLIM    M2PA
1317 A    lsniplimi  0   IPLIMI   M2PA

SLK table is (30 of 1200) 2% full.

    If IPLIMx cards containing signaling links are shown in the rtrv-slk output, perform the Removing an IPLIMx Card procedure to remove an IPLIMx card and its associated signaling links.

    If IPLIMx cards containing signaling links are not displayed in the rtrv-slk output, perform one or more of these actions to increase the available TPS.

    Note:

    If one or more of these actions are not performed to increase the available TPS and the available TPS will not allow the IPLIMx signaling link to be added, the IPLIMx signaling link cannot be added and the remainder of this procedure cannot be performed.
    • The IP TPS values of some IPGWx linksets have to be changed. To perform this action, continue the procedure with 6.
    • The MAXSLKTPS values of some IPSG linksets (and the RSVDSLKTPS values if necessary) have to be changed. To perform this action, continue the procedure with 6.
    • Some ATM high-speed signaling links have to be removed. To perform this action, continue the procedure with 4.

    If you do not wish to perform other actions to increase the available TPS and the available TPS will allow the IPLIMx signaling link to be added, continue the procedure with 8.

  6. Display the IPGWx and IPSG linksets by entering this command.

    rept-stat-iptps

    This is an example of the possible output. 

    
rlghncxa03w 10-07-19 21:16:37 GMT EAGLE5 42.0.0
IP TPS USAGE REPORT

           THRESH  CONFIG/  CONFIG/         TPS   PEAK      PEAKTIMESTAMP
                      RSVD      MAX
-------------------------------------------------------------------------
LSN
ipgwx1       100%     ----    32000  TX:   3700   4000  10-07-19 09:49:19 
                                    RCV:   3650   4000  10-07-19 09:49:19
ipgwx2       100%     ----    16000  TX:   4800   5000  10-07-19 09:49:09 
                                    RCV:   4850   5000  10-07-19 09:49:09
ipgwx3       100%     ----    32000  TX:    427    550  10-07-19 09:49:19 
                                    RCV:    312    450  10-07-19 09:49:19
ipsglsn      100%      600    24000  TX:   4800   5000  10-07-19 09:49:19 
                                    RCV:   4800   5000  10-07-19 09:49:19    
ipsglsn2     100%      600     4000  TX:    427    550  10-07-19 09:49:19 
                                    RCV:    312    450  10-07-19 09:49:19   
-------------------------------------------------------------------------

Command Completed.

    If linksets are displayed in the rept-stat-iptps output, continue the procedure with 7.

    If linksets are not displayed in the rept-stat-iptps output, perform one or more of these actions to increase the available TPS.

    Note:

    If one or more of these actions are not performed to increase the available TPS and the available TPS will not allow the IPLIMx signaling link to be added, the IPLIMx signaling link cannot be added and the remainder of this procedure cannot be performed.
    • An IPLIMx card that contains signaling links has to be removed. To perform this action, continue the procedure with 5.
    • Some ATM high-speed signaling links have to be removed. To perform this action, continue the procedure with 4.

    If you do not wish to perform other actions to increase the available TPS and the available TPS will allow the IPLIMx signaling link to be added, continue the procedure with 8.

  7. Display the attributes of the linksets shown in 6 by entering the rtrv-ls command with the name of the linkset shown in 6.

    For this example enter these commands.

    rtrv-ls:lsn=ipgwx1

    This is an example of the possible output. 

    
rlghncxa03w 10-07-19 21:16:37 GMT EAGLE5 42.0.0

                                 L3T SLT              GWS GWS GWS
LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
ipgwx1        001-001-002   none 1   1   no  A   8    off off off no    off

              SPCA          CLLI         TFATCABMLQ MTPRSE ASL8
           ---------------- -----------  4          ---    no

           RANDSLS
           off

           IPSG  IPGWAPC  GTTMODE           CGGTMOD
           no    yes      CdPA                no

           MATELSN    IPTPS   LSUSEALM  SLKUSEALM
           ---------- 32000   100%      80%

           LOC  LINK SLC TYPE
           1101 A    0   SS7IPGW
           1102 A    1   SS7IPGW
           1103 A    2   SS7IPGW
           1104 A    3   SS7IPGW
           1105 A    4   SS7IPGW
           1106 A    5   SS7IPGW
           1107 A    6   SS7IPGW
           1108 A    7   SS7IPGW


Link set table is (8 of 1024) 1% full.

    rtrv-ls:lsn=ipgwx2

    This is an example of the possible output. 

    
rlghncxa03w 10-07-19 21:16:37 GMT EAGLE5 42.0.0

                                 L3T SLT              GWS GWS GWS
LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
ipgwx2        001-001-003   none 1   1   no  A   8    off off off no    off

              SPCA          CLLI         TFATCABMLQ MTPRSE ASL8
           ---------------- -----------  4          ---    no

           RANDSLS
           off

           IPSG  IPGWAPC  GTTMODE           CGGTMOD
           no    yes      CdPA                no

           MATELSN    IPTPS   LSUSEALM  SLKUSEALM
           ---------- 16000   100%      80%

           LOC  LINK SLC TYPE
           1111 A    0   SS7IPGW
           1112 A    1   SS7IPGW
           1201 A    2   SS7IPGW
           1202 A    3   SS7IPGW
           1203 A    4   SS7IPGW
           1204 A    5   SS7IPGW
           1205 A    6   SS7IPGW
           1206 A    7   SS7IPGW


Link set table is (8 of 1024) 1% full.

    rtrv-ls:lsn=ipgwx3

    This is an example of the possible output. 

    
rlghncxa03w 10-07-19 21:16:37 GMT EAGLE5 42.0.0

                                 L3T SLT              GWS GWS GWS
LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
ipgwx3        001-001-004   none 1   1   no  A   0    off off off no    off

              SPCA          CLLI         TFATCABMLQ MTPRSE ASL8
           ---------------- -----------  1          ---    no

           RANDSLS
           off

           IPSG  IPGWAPC  GTTMODE           CGGTMOD
           no    yes      CdPA                no

           MATELSN    IPTPS   LSUSEALM  SLKUSEALM
           ---------- 32000   100%      80%


Link set table is (8 of 1024) 1% full.

    rtrv-ls:lsn=ipsglsn

    This is an example of the possible output. 

    
rlghncxa03w 10-07-19 21:16:37 GMT EAGLE5 42.0.0

                                 L3T SLT              GWS GWS GWS
LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
ipsglsn       003-003-003   none 1   1   no  A   6    off off off no    off

              SPCA          CLLI         TFATCABMLQ MTPRSE ASL8
           ---------------- -----------  3          ---    no

           RANDSLS
           off

           IPSG  IPGWAPC  GTTMODE           CGGTMOD
           yes   no       CdPA               no

           ADAPTER    RSVDSLKTPS  MAXSLKTPS
           m2pa       600         4000

           TPSALM     LSUSEALM    SLKUSEALM
           rsvdslktps 100%         100%

           LOC  LINK SLC TYPE     ANAME
           1303 A    0   IPSG     ipsgm2pa1
           1303 A1   1   IPSG     ipsgm2pa2
           1303 B1   2   IPSG     ipsgm2pa3
           1303 A2   3   IPSG     ipsgm2pa4
           1303 A3   4   IPSG     ipsgm2pa5
           1307 A    5   IPSG     m2pa2


Link set table is (8 of 1024) 1% full.

    rtrv-ls:lsn=ipsglsn2

    This is an example of the possible output. 

    
rlghncxa03w 10-07-19 21:16:37 GMT EAGLE5 42.0.0

                                 L3T SLT              GWS GWS GWS
LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
ipsglsn2      005-005-005   none 1   1   no  A   1    off off off no    off

              SPCA          CLLI         TFATCABMLQ MTPRSE ASL8
           ---------------- -----------  1          ---    no

           RANDSLS
           off

           IPSG  IPGWAPC  GTTMODE           CGGTMOD
           yes   no       CdPA               no

           ADAPTER    RSVDSLKTPS  MAXSLKTPS
           m2pa       600         4000

           TPSALM     LSUSEALM    SLKUSEALM
           rsvdslktps 100%         100%

           LOC  LINK SLC TYPE     ANAME
           1303 B3   0   IPSG     ipsgm2pa6


Link set table is (8 of 1024) 1% full.
    Perform one or both of these actions as necessary.
    • Perform the Configuring an IPGWx Linkset procedure to change the IPTPS value for any linksets shown in the rtrv-ls output whose IPGWAPC value is yes.
    • Perform the Changing an IPSG M2PA Linkset procedure (for linkset whose IPSG value is yes and ADAPTER value is M2PA) or the Changing an IPSG M3UA Linkset procedure (for linkset whose IPSG value is yes and ADAPTER value is M3UA) to change the MAXSLKTPS value (and RSVDSLKTPS value if necessary) for any linksets shown in the rtrv-ls output.
    Perform one or both of these actions to increase the available TPS if needed.
    • An IPLIMx card that contains signaling links has to be removed. To perform this action, continue the procedure with 5.
    • Some ATM high-speed signaling links have to be removed. To perform this action, continue the procedure with 4.

    If you do not wish to perform other actions to increase the available TPS and the available TPS will allow the IPLIMx signaling link to be added, continue the procedure with 8.

  8. Display the current signaling link configuration using the rtrv-slk command.

    This is an example of the possible output. 

    
rlghncxa03w 10-07-19 21:16:37 GMT EAGLE5 42.0.0
                                  L2T               PCR  PCR
LOC  LINK LSN        SLC TYPE     SET  BPS    ECM   N1   N2
1312 A    lsnds0     0   LIMDS0   1    56000  BASIC ---- ------

                                  LP         ATM
LOC  LINK LSN        SLC TYPE     SET BPS    TSEL     VCI   VPI  LL
1305 A    lsnds0     1   LIMATM   1   1.544M LINE     5     0    0

                                  LP         ATM                    E1ATM
LOC  LINK LSN        SLC TYPE     SET BPS    TSEL     VCI   VPI  CRC4 SI SN
1306 A    lsnituatm  0   LIME1ATM 21  2.048M LINE     5     0    ON   3  0

LOC  LINK LSN        SLC TYPE     ANAME           SLKTPS
1303 A    ipsglsn    0   IPSG     ipsgm2pa1       600
1303 A1   ipsglsn    1   IPSG     ipsgm2pa2       600
1303 B1   ipsglsn    2   IPSG     ipsgm2pa3       600
1303 A2   ipsglsn    3   IPSG     ipsgm2pa4       600
1303 A3   ipsglsn    4   IPSG     ipsgm2pa5       600
1303 B3   ipsglsn2   0   IPSG     ipsgm2pa6       1000
1307 A    ipsglsn    5   IPSG     m2pa2           600

LOC  LINK LSN        SLC TYPE     IPLIML2
1301 A    lsniplim   0   IPLIM    M2PA
1301 A1   lsniplim   1   IPLIM    M2PA
1301 B1   lsniplim   2   IPLIM    M2PA
1317 A    lsniplimi  0   IPLIMI   M2PA

LOC  LINK LSN        SLC TYPE
1201 A    ipgwx2     2   SS7IPGW
1202 A    ipgwx2     3   SS7IPGW
1203 A    ipgwx2     4   SS7IPGW
1204 A    ipgwx2     5   SS7IPGW
1205 A    ipgwx2     6   SS7IPGW
1206 A    ipgwx2     7   SS7IPGW
1101 A    ipgwx1     0   SS7IPGW
1102 A    ipgwx1     1   SS7IPGW
1103 A    ipgwx1     2   SS7IPGW
1104 A    ipgwx1     3   SS7IPGW
1105 A    ipgwx1     4   SS7IPGW
1106 A    ipgwx1     5   SS7IPGW
1107 A    ipgwx1     6   SS7IPGW
1108 A    ipgwx1     7   SS7IPGW
1111 A    ipgwx2     0   SS7IPGW
1112 A    ipgwx2     1   SS7IPGW

SLK table is (30 of 1200) 2% full.
  9. Display the current linkset configuration using the rtrv-ls command.

    This is an example of the possible output. 

    
rlghncxa03w 10-07-10 11:43:04 GMT EAGLE5 42.0.0

                                 L3T SLT              GWS GWS GWS
LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
ipgwx1        001-001-002   none 1   1   no  A   8    off off off no    off
ipgwx2        001-001-003   none 1   1   no  A   8    off off off no    off
ipgwx3        001-001-004   none 1   1   no  A   0    off off off no    off
lsniplim      002-002-002   none 1   1   no  A   3    off off off no    off
ipsglsn       003-003-003   none 1   1   no  A   6    off off off no    off
ipsglsn2      005-005-005   none 1   1   no  A   1    off off off no    off
lsnds0        009-009-009   none 1   1   no  A   2    off off off no    off

                                 L3T SLT              GWS GWS GWS
LSN           APCI   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsnituatm     1-002-3       none 1   2   no  A   1    off off off no    off
atmitu1       3-111-3       none 1   1   no  A   0    off off off no    off

                                 L3T SLT              GWS GWS GWS
LSN           APCN   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsipgw        2968          none 1   2   no  A   1    off off off no    off

Link set table is (10 of 1024) 1% full.
    If the desired linkset is not in the database, perform one of these procedures to add the linkset to the database.

    After the new linkset has been added, continue the procedure with 11.

    If the signaling link will be assigned to the linkset shown in this step, continue the procedure with 10.

  10. Display the linkset that the signaling link is being assigned to using the rtrv-ls command, specifying the name of the linkset that the signaling link is being assigned to.
    For this example, enter this command.

    rtrv-ls:lsn=lsipgw

    This is an example of the possible output. 

    
rlghncxa03w 10-07-17 11:43:04 GMT EAGLE5 42.0.0

                                 L3T SLT              GWS GWS GWS
LSN           APCN   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsipgw        2968          none 1   2   no  A   1    off off off no    off

              SPCN          CLLI         TFATCABMLQ MTPRSE ASL8
           ---------------- -----------  1          ---    ---

           SLSOCBIT SLSRSB RANDSLS MULTGC ITUTFR
           none     1      off     no     off

           IPSG  IPGWAPC  GTTMODE           CGGTMOD
           no    no       CdPA                no

           LOC  LINK SLC TYPE     IPLIML2
           1317 A    0   IPLIMI   M2PA

           SAPCI
           1-10-1

           SAPCN
           1234-aa
           1235-bb
           1200-zz

Link set table is (10 of 1024) 1% full.

    The signaling link cannot be assigned to a linkset whose IPGWAPC value is yes. If the IPGWAPC value for the linkset is yes, repeat the procedure from 9 and choose another linkset.

    If the IPGWAPC value for the linkset is no, continue the procedure with 11.

  11. Add the signaling link to the database using the ent-slk command.
    Table 3-2 shows the parameters and values that can be specified with the ent-slk command.

    Table 3-2 M2PA IPLIMx Signaling Link Parameter Combinations

    M2PA IPLIMx Signaling Link
    Mandatory Parameters
    :loc = location of the IP card with one of these applications: IPLIM or IPLIMI; and the DCM card type. (See Note 1)
    :link = <see Note 2>
    :lsn = linkset name (See Note 3)
    :slc = 0 - 15 (See Note 4)
    Optional Parameter
    :ipliml2 = m2pa, default value = m2pa

    Notes:

    1. If the multgc=yes parameter is assigned to the linkset, the card’s application must be IPLIMI.

    2. The range of link parameter values is dependent on the type of IPLIMx card that is being provisioned.
    • Single-Slot EDCM - Link Parameter Values A - A3, B - B3
    • E5-ENET - Link Parameter Values A - A7, B - B7

    3. If the card’s application is IPLIMI, the linkset adjacent point code must be ITU. If the card’s application is IPLIM, the linkset adjacent point code must be ANSI. The domain of the linkset adjacent point code must be SS7.

    4. Signaling links provisioned in this procedure can be in a linkset that contains non-IPLIMx signaling links.

    For this example, enter these commands.

    ent-slk:loc=2204:link=b:lsn=lsnlp2:slc=0:ipliml2=m2pa

    ent-slk:loc=2205:link=a:lsn=lsnlp1:slc=1:ipliml2=m2pa

    ent-slk:loc=2213:link=a:lsn=lsnlp5:slc=1:ipliml2=m2pa

    When each of these commands have successfully completed, this message should appear. 

    
rlghncxa03w 06-10-07 08:29:03 GMT  EAGLE5 36.0.0
ENT-SLK: MASP A - COMPLTD

    Note:

    If adding the new signaling link will result in more than 700 signaling links in the database and the OAMHCMEAS value in thertrv-measopts output ison, the scheduled UI measurement reports will be disabled.
  12. Verify the changes using the rtrv-slk command with the card location and link parameter values specified in 11. For this example, enter these commands.

    rtrv-slk:loc=2204:link=b

    This is an example of the possible output. 

    
rlghncxa03w 06-10-19 21:16:37 GMT EAGLE5 36.0.0
LOC  LINK LSN         SLC TYPE     IPLIML2
2204 B    lsnlp2       0  IPLIM    M2PA

    rtrv-slk:loc=2205:link=a

    This is an example of the possible output. 

    
rlghncxa03w 06-10-19 21:16:37 GMT EAGLE5 36.0.0
LOC  LINK LSN         SLC TYPE     IPLIML2
2205 A    lsnlp1       1  IPLIM    M2PA

    rtrv-slk:loc=2213:link=a

    This is an example of the possible output. 

    
rlghncxa03w 06-10-19 21:16:37 GMT EAGLE5 36.0.0
LOC  LINK LSN         SLC TYPE     IPLIML2
2213 A    lsnlp5       0  IPLIM    M2PA
    Continue the procedure by performing one of these steps.
    • If a new signaling link is the first signaling link on the IPLIMx card, continue the procedure with 13.
    • If all the signaling links that were added in this procedure were added to IPLIMx cards that contained other signaling links, continue the procedure with14.
  13. Place the IPLIMx card containing the first signaling link on that card into service with the rst-card command, specifying the location of the card. For this example, enter these commands.

    rst-card:loc=2204

    rst-card:loc=2205

    rst-card:loc=2213

    When each of these commands have successfully completed, this message should appear. 

    
rlghncxa03w 06-10-23 13:05:05 GMT EAGLE5 36.0.0
Card has been allowed.
  14. Activate all signaling links on the cards using the act-slk command, specifying the card location and link parameter value of each signaling link. For this example, enter these commands.

    act-slk:loc=2204:link=b

    act-slk:loc=2205:link=a

    act-slk:loc=2213:link=a

    When each of these commands have successfully completed, this message should appear. 

    
rlghncxa03w 06-10-07 08:31:24 GMT  EAGLE5 36.0.0
Activate Link message sent to card
  15. Check the status of the signaling links added in 11 using the rept-stat-slk command with the card location and link parameter values specified in 11.The state of each signaling link should be in service normal (IS-NR) after the link has completed alignment (shown in the PST field). For this example, enter these commands.

    rept-stat-slk:loc=2204:link=b

    This is an example of the possible output. 

    
rlghncxa03w 07-05-23 13:06:25 GMT EAGLE5 37.0.0
SLK      LSN       CLLI        PST          SST       AST
2204,B   lsnlp2    ----------- IS-NR        Avail     ----
  ALARM STATUS       = 
  UNAVAIL REASON     =

    rept-stat-slk:loc=2205:link=a

    This is an example of the possible output. 

    
rlghncxa03w 07-05-23 13:06:25 GMT EAGLE5 37.0.0
SLK      LSN       CLLI        PST          SST       AST
2205,A   lsnlp1    ----------- IS-NR        Avail     ----
  ALARM STATUS       = 
  UNAVAIL REASON     =

    rept-stat-slk:loc=2213:link=a

    This is an example of the possible output. 

    
rlghncxa03w 07-05-23 13:06:25 GMT EAGLE5 37.0.0
SLK      LSN       CLLI        PST          SST       AST
2213,A   lsnlp5    ----------- IS-NR        Avail     ----
  ALARM STATUS       = 
  UNAVAIL REASON     =
  16. Back up the new changes using the chg-db:action=backup:dest=fixed command. These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-2 Adding an IPLIMx Signaling Link



Sheet 1 of 5



Sheet 2 of 5



Sheet 3 of 5



Sheet 4 of 5



Sheet 5 of 5

3.4 Configuring an IP Link

This procedure is used to configure the link parameters for IP cards using the chg-ip-lnk command. These link parameters are used to configure the Ethernet hardware.

The chg-ip-lnk command uses the following parameters.

:loc – The card location of the IP card.

:port – The Ethernet interface on the IP card, A or B.

:ipaddr – IP address assigned to the Ethernet interface on the IP card. This is an IP address expressed in standard “dot notation.” IP addresses consist of the system’s network number and the machine’s unique host number.

:submask – The subnet mask of the IP interface. A subnet mask is an IP address with a restricted range of values. The bits in the mask must be a string of one’s followed by a string of zero’s. There must be at least two one’s in the mask, and the mask cannot be all one’s. See Table 3-3 to assign the correct parameter values.

:auto – Tells hardware whether to automatically detect the duplex and speed.

:duplex – This is the mode of operation of the interface.

:speed – This is the bandwidth in megabits per second of the interface.

:mactype – This is the Media Access Control Type of the interface.

:mcast – The multicast control flag. This parameter enables or disables multicast support for the interface.

The EAGLE can contain a maximum of 2048 IP links.

A zero ipaddr parameter value (0.0.0.0) indicates the IP card Ethernet interface to IP link association is disabled. The host to the original IP address must be removed before the ipaddr=0.0.0.0 can be specified.

If the defrouter parameter of the chg-ip-card command contains an IP address for the card specified in this procedure, the network portion of one of the IP addresses assigned to the card in this procedure must match the network portion of the IP address specified by the defrouter parameter of the chg-ip-card command.

The network portion of the IP address is based on the class of the IP address (shown in Table 3-3). If the IP address is a Class A IP address, the first field is the network portion of the IP address. If the IP address is a Class B IP address, the first two fields are the network portion of the IP address. If the IP address is a Class C IP address, the first three fields are the network portion of the IP address. For example, if the IP address is 193.5.207.150, a Class C IP address, the network portion of the IP address is 193.5.207.

If the auto=yes parameter is specified, then the duplex and speed parameters are not allowed.

The loc parameter value must be shown in the rtrv-ip-card output.

The IP card must be placed out of service.

If either the ipaddr or submask parameters are specified, then both parameters must be specified. If the ipaddr parameter value is zero (0.0.0.0), the submask parameter is not required.

The IP address and subnet mask values cannot be changed to an address representing a different network if:

  • If the network interface specified by the loc and port parameters has a default router, dnsa, or dsnb parameter values assigned to it, as shown in the rtrv-ip-card output.
  • Any IP routes, shown in the rtrv-ip-rte output, reference the IP address for the network interface specified by the loc and port parameters.

The IP link cannot be changed if open associations reference the IP link being changed.

The network portion of the IP addresses assigned to the IP links on an IP card must be unique. For example, if IP links are assigned to IP card 1103, the network portion of the IP address for Ethernet interface A (port=a) must be different from the IP address for Ethernet interface B (port=b).

The submask parameter value is based upon the ipadddr setting. See Table 3-3 for the valid input values for the submask and ipaddr parameter combinations.

Table 3-3 Valid Subnet Mask Parameter Values

Network Class IP Network Address Range Valid Subnet Mask Values

A

1.0.0.0 to 127.0.0.0

255.0.0.0 (the default value for a class A IP address)

255.192.0.0

255.224.0.0

255.240.0.0

255.248.0.0

255.252.0.0

255.254.0.0

255.255.128.1

A+B

128.0.0.0 to 191.255.0.0

255.255.0.0 (the default value for a class B IP address)

255.255.192.0

255.255.224.0

255.255.240.0

255.255.248.0

255.255.252.0

255.255.254.0

255.255.255.128

A+B+C

192.0.0.0 to 223.255.255.0

255.255.255.0 (the default value for a class C IP address)

255.255.255.192

255.255.255.224

255.255.255.240

255.255.255.248

255.255.255.252

If a Class B IP address is specified for the ipaddr parameter of the chg-ip-lnk command, the subnet address that results from the ipaddr and submask parameter values cannot be the same as the subnet address that results from the pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values of the chg-netopts command. The pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values can be verified by entering the rtrv-netopts command. Choose ipaddr and submask parameter values for the IP link whose resulting subnet address is not be the same as the subnet address resulting from the pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values of the chg-netopts command.

The IP address for the IP link cannot be shown as the IPADDR value in the rtrv-ip-lnk, rtrv-ftp-serv, or rtrv-seas-config outputs, or the BPIPADDR value in the rtrv-ip-card output.

Canceling the RTRV-ASSOC Command

Because the rtrv-assoc command used in this procedure can output information for a long period of time, the rtrv-assoc command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-assoc command can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-assoc commandwas were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-assoc commandwas entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-assoc commandwas entered, from another terminal other that the terminal where the rtrv-assoc commandwas entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

  1. Display the current link parameters associated with the IP card in the database by entering the rtrv-ip-lnk command.

    The following is an example of the possible output. 

    
rlghncxa03w 08-12-28 21:14:37 GMT EAGLE5 40.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
1201  A    192.1.1.10      255.255.255.128 HALF    10    802.3   NO   NO
1201  B    --------------- --------------- HALF    10    DIX     NO   NO
1203  A    192.1.1.12      255.255.255.0   ----    ---   DIX     YES  NO
1203  B    --------------- --------------- HALF    10    DIX     NO   NO
1205  A    192.1.1.14      255.255.255.0   FULL    100   DIX     NO   NO
1205  B    --------------- --------------- HALF    10    DIX     NO   NO
2101  A    192.1.1.20      255.255.255.0   FULL    100   DIX     NO   NO
2101  B    --------------- --------------- HALF    10    DIX     NO   NO
2103  A    192.1.1.22      255.255.255.0   FULL    100   DIX     NO   NO
2103  B    --------------- --------------- HALF    10    DIX     NO   NO
2105  A    192.1.1.24      255.255.255.0   FULL    100   DIX     NO   NO
2105  B    --------------- --------------- HALF    10    DIX     NO   NO
2205  A    192.1.1.30      255.255.255.0   FULL    100   DIX     NO   NO
2205  B    --------------- --------------- HALF    10    DIX     NO   NO
2207  A    192.1.1.32      255.255.255.0   FULL    100   DIX     NO   NO
2207  B    --------------- --------------- HALF    10    DIX     NO   NO
2213  A    192.1.1.50      255.255.255.0   FULL    100   DIX     NO   NO
2213  B    --------------- --------------- HALF    10    DIX     NO   NO
2301  A    192.1.1.52      255.255.255.0   FULL    100   DIX     NO   NO
2301  B    --------------- --------------- HALF    10    DIX     NO   NO

IP-LNK   table is (20 of 2048) full.

    Note:

    If theipaddr=0.0.0.0 is not being specified in this procedure, continue the procedure with3.
  2. If IP address information is being added or changed (not deleted) in the link parameters, verify that the IP address is present in the IP host table by using the rtrv-ip-host:display=all command.

    The following is an example of the possible output. 

    
rlghncxa03w 13-06-28 21:15:37 GMT EAGLE5 45.0.0

LOCAL IPADDR    LOCAL HOST
192.1.1.10      IPNODE1-1201
192.1.1.12      IPNODE1-1203
192.1.1.14      IPNODE1-1205
192.1.1.20      IPNODE2-1201
192.1.1.22      IPNODE2-1203
192.1.1.24      IPNODE2-1205
192.1.1.30      KC-HLR1
192.1.1.32      KC-HLR2
192.1.1.50      DN-MSC1
192.1.1.52      DN-MSC2

REMOTE IPADDR   REMOTE HOST
150.1.1.5       NCDEPTECONOMIC_DEVELOPMENT. SOUTHEASTERN_COORIDOR_ASHVL. GOV

IP Host table is (11 of 4096) 0.26% full

    If the current IP address of the IP link is shown in the rtrv-ip-host output, remove the host assigned to the IP address by performing the Removing an IP Host Assigned to an IPLIMx Card procedure.

  3. To change IP link parameters, the signaling link to the IP card and the IP card have to be inhibited.
    Display the signaling link associated with the card shown in 1 using the rtrv-slk command specifying the card location.

    For this example, enter this command.

    rtrv-slk:loc=1201

    This is an example of the possible output. 

    
rlghncxa03w 06-10-19 21:17:04 GMT EAGLE5 36.0.0
LOC   LINK LSN          SLC TYPE    IPLIML2
1201  A    nc001         0  IPLIM   M2PA
  4. Retrieve the status of the signaling link assigned to the IP card to be changed using the rept-stat-slk command.

    For example, enter this command.

    rept-stat-slk:loc=1201:link=a

    The output lists the signaling link assigned to this card: 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
SLK      LSN         CLLI        PST          SST       AST
1201,A   nc001       ----------- IS-NR
Command Completed.

    If the signaling link is in service-normal (IS-NR), continue the procedure with 5 to deactivate the signaling link. If the signaling link is out-of-service-maintenance disabled (OOS-MT-DSBLD), continue the procedure with 7 to verify the IP card status.

  5. Deactivate the signaling link assigned to the IP card using the dact-slk command.

    For example, enter this command.

    dact-slk:loc=1201:link=a

    Caution:

    This command impacts network performance and should only be used during periods of low traffic.

    After this command has successfully completed, this message appears. 

    
rlghncxa03w 06-10-12 09:12:36 GMT EAGLE5 36.0.0
Deactivate Link message sent to card.
  6. Verify the new link status using the rept-stat-slk command.

    For example, enter this command.

    rept-stat-slk:loc=1201:link=a

    The output displays the link status as OOS-MT-DSBLD and gives off a minor alarm: 

    
rlghncxa03w 06-10-27 17:00:36 GMT EAGLE5 36.0.0
SLK      LSN         CLLI        PST          SST       AST
1201,A   nc001       ----------- OOS-MT-DSBLD AVAIL     ---
ALARM STATUS = * 0236 REPT-LKS:not aligned
UNAVAIL REASON = NA 
Command Completed.
  7. Verify the status of the IP card to be inhibited using the rept-stat-card command.

    For example, enter this command.

    rept-stat-card:loc=1201

    This is an example of the possible output. 

    
rlghncxa03w 06-10-27 17:00:36 GMT EAGLE5 36.0.0
CARD  VERSION      TYPE    GPL       PST           SST       AST
1201  114-000-000  DCM     IPLIM     IS-NR         Active    -----
  ALARM STATUS      = No Alarms.
  BPDCM GPL         = 002-102-000
  IMT BUS A         = Conn
  IMT BUS B         = Conn
  SIGNALING LINK STATUS
      SLK    PST                LS            CLLI
      A      IS-NR              nc001         -----------

Command Completed.

    If the IP card to be inhibited is in service-normal (IS-NR), continue the procedure with 8 to inhibit the card. If the IP card is out-of-service-maintenance disabled (OOS-MT-DSBLD), continue the procedure with 10 to change the IP link parameters.

  8. Inhibit the IP card using the inh-card command.

    For example, enter this command.

    inh-card:loc=1201

    This message should appear. 

    
rlghncxa03w 06-10-28 21:18:37 GMT EAGLE5 36.0.0
Card has been inhibited.
  9. Display the status of the IP card to verify that it is out-of-service maintenance-disabled (OOS-MT-DSBLD).

    Enter this command.

    rept-stat-card:loc=1201

    This is an example of the possible output. 

    
rlghncxa03w 06-10-27 17:00:36 GMT EAGLE5 36.0.0
CARD  VERSION      TYPE    GPL       PST           SST       AST
1201  114-000-000  DCM     IPLIM     IS-NR         Active    -----
  ALARM STATUS      = No Alarms.
  BPDCM GPL         = 002-102-000
  IMT BUS A         = Conn
  IMT BUS B         = Conn
  SIGNALING LINK STATUS
      SLK    PST                LS            CLLI
      A      IS-NR              nc001         -----------

Command Completed.
  10. Display the attributes of the IP card assigned to the IP link being changed by entering the rtrv-ip-card command and specifying the card location of the IP link.

    Note:

    If theipaddr orsubmask parameter values are not being changed, continue the procedure with13.

    For this example, enter this command.

    rtrv-ip-card:loc=1201

    This is an example of the possible output. 

    
rlghncxa03w 08-08-28 21:17:37 GMT EAGLE5 39.0.0
   LOC 1201
     SRCHORDR  LOCAL
     DNSA      150.1.1.1
     DNSB      ---------------
     DEFROUTER ---------------
     DOMAIN    ---------------
     SCTPCSUM  crc32c
     BPIPADDR  ---------------
     BPSUBMASK ---------------

    If the rtrv-ip-card output shows an IP address for the default router (DEFROUTER) whose network portion matches the network portion of the IP address being changed, go to the Configuring an IP Card procedure and change the IP address of the default router to 0.0.0.0.

  11. Display any IP routes referencing the IP link being changed by entering the rtrv-ip-rte command and specifying the card location of the IP link.

    For this example, enter this command.

    rtrv-ip-rte:loc=1201

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
LOC   DEST             SUBMASK          GTWY
1201  128.252.10.5     255.255.255.255  140.188.13.33
1201  128.252.0.0      255.255.0.0      140.188.13.34
1201  150.10.1.1       255.255.255.255  140.190.15.3

IP Route table is  (5 of 2048) 0.24% full

    If the rtrv-ip-rte output shows that the card has IP routes assigned to it, go to the Removing an IP Route procedure and remove the IP routes from the database.

  12. The subnet address that results from the ipaddr and submask parameter values of the chg-ip-lnk command cannot be the same as the subnet address that results from the pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values of the chg-netopts command.

    Note:

    If a Class A or CIP address (seeTable 3-3) will be specified for theipaddr parameter in14, continue the procedure with13.

    Display the pvn, pvnmask, fcna, fcnamask, fcnb, and fcnbmask parameter values of the chg-netopts command by entering the rtrv-netopts command.

    If error message E3967 Cmd Rej: E5IS must be on is displayed after the rtrv-netopts command is executed, the pvn, pvnmask, fcna, fcnamask, fcnb, and fcnbmask parameters are not configured. Continue the procedure with 13.

    This is an example of the possible output if the E5IS feature is on. 

    
rlghncxa03w 09-02-28 21:17:37 GMT EAGLE5 40.1.0
NETWORK OPTIONS
------------------
PVN        = 128.20.30.40
PVNMASK    = 255.255.192.0
FCNA       = 170.120.50.0
FCNAMASK   = 255.255.240.0
FCNB       = 170.121.50.0
FCNBMASK   = 255.255.254.0

    Choose ipaddr and submask parameter values for the IP link whose resulting subnet address is not be the same as the subnet address resulting from the pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values of the chg-netopts command. Continue the procedure with 13.

  13. Display the associations referencing the local host name that is associated with the IP link being changed by entering the rtrv-assoc command and specifying the local host name shown in the rtrv-ip-host output in 2.

    For this example, enter this command.

    rtrv-assoc:lhost="ipnode-1201"

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
swbel32         1201 A     A    M2PA    1030  2345  YES  YES

IP Appl Sock/Assoc table is (3 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 3200 KB) on LOC = 1201

    If no associations are displayed in this step, continue the procedure with 14.

    If the rtrv-assoc output shows that the open parameter for any associations is yes, perform one of these procedures to change the value of the open parameter the associations to no.

  14. Change the link parameters associated with the IP card in the database using the chg-ip-lnk command.

    For this example, enter this command.

    chg-ip-lnk:loc=1201:port=a:ipaddr=192.1.1.10:submask=255.255.255.0 :auto=yes:mactype=dix

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 06-10-28 21:18:37 GMT EAGLE5 36.0.0
CHG-IP-LNK: MASP A - COMPLTD
  15. Verify the new link parameters associated with the IP card that was changed in 14 by entering the rtrv-ip-lnk command with the card location specified in 14.

    For this example, enter this command.

    The following is an example of the possible output. 

    
rlghncxa03w 07-05-28 21:14:37 GMT EAGLE5 37.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
1201  A    192.1.1.10      255.255.255.128 HALF    10    DIX     YES  NO
1201  B    --------------- --------------- HALF    10    DIX     NO   NO
  16. Allow the IP card that was inhibited in 8 by using by using the alw-card command.

    Note:

    If8was not performed, continue the procedure with18.

    For example, enter this command.

    alw-card:loc=1201

    This message should appear. 

    
rlghncxa03w 06-10-28 21:20:37 GMT EAGLE5 36.0.0
Card has been allowed.
  17. Verify the in-service normal (IS-NR) status of the IP card using the rept-stat-card command.

    For example, enter this command.

    rept-stat-card:loc=1201

    This is an example of the possible output. 

    
rlghncxa03w 06-10-27 17:00:36 GMT EAGLE5 36.0.0
CARD  VERSION      TYPE    GPL       PST           SST       AST
1201  114-000-000  DCM     IPLIM     IS-NR         Active    -----
  ALARM STATUS      = No Alarms.
  BPDCM GPL         = 002-102-000
  IMT BUS A         = Conn
  IMT BUS B         = Conn
  SIGNALING LINK STATUS
      SLK    PST                LS            CLLI
      A      IS-NR              nc001         -----------

Command Completed.
  18. Activate the signaling link from 5 using the act-slk command.

    Note:

    If5was not performed, continue the procedure with20.

    For example, enter this command.

    act-slk:loc=1201:link=a

    The link changes its state from OOS-MT-DSBLD (out-of-service maintenance-disabled) to IS-NR (in-service normal).

    The output confirms the activation. 

    
rlghncxa03w 06-10-07 11:11:28 GMT EAGLE5 36.0.0
Activate Link message sent to card
  19. Verify the in-service normal (IS-NR) status of the signaling link using the rept-stat-slk command.

    For example, enter this command.

    rept-stat-slk:loc=1201:link=a

    This message should appear. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
SLK      LSN         CLLI        PST          SST       AST
1201,A   nc001       ----------- IS-NR
Command Completed.
  20. Perform the Configuring an IP Card procedure and change the IP address of the default router to a non-zero value, where the network portion of the default router IP address matches the network portion of the IP link’s new IP address.

    Note:

    If theipaddr orsubmask values were not changed, continue the procedure with22.

    Note:

    If theIP address of the default router was not changed to 0.0.0.0 in 10 , continue the procedure with21.
  21. Perform the Adding an IP Route procedure and add the IP routes back into the database.

    Note:

    IfIP routes were not removed in11, continue the procedure with22.
  22. Perform one of these procedures as necessary and change the value of the open parameter of the association to yes.

    Note:

    If theopen parameter value for an association was not changed in13, continue the procedure with23.
  23. Back up the new changes using the chg-db:action=backup:dest=fixed command.
    These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-3 Configuring an IP Link



Sheet 1 of 9



Sheet 2 of 9



Sheet 3 of 9



Sheet 4 of 9



Sheet 5 of 9



Sheet 6 of 9



Sheet 7 of 9



Sheet 8 of 9



Sheet 9 of 9

3.5 Adding an IP Host

This procedure associates hostnames with IP addresses using the ent-ip-host command.

The ent-ip-host command uses the following parameters.

:host– The host name to be associated with the IP address. This parameter identifies the logical name assigned to the device with the IP address indicated. The host name can contain up to 60 characters (using only these characters: a-z, A-Z, 0-9, -, .) and is not case sensitive. The host name must begin with a letter. Host names containing a dash (-) must be enclosed in double quotes.

:ipaddr – The IP address to be associated with the hostname. The node’s IP address. This is an IP address expressed in standard “dot notation.” IP addresses consist of the system’s network number and the machine’s unique host number.

:type – Specifies if the host resides on the IP card on the EAGLE 5 (type=local, the default value), or if the host resides on equipment that is not in the EAGLE 5 (type=remote). This parameter is optional.

The EAGLE 5 can contain a maximum of 4096 IP hosts.

The IP address for a local host must be shown in the rtrv-ip-lnk output.

The IP address for a remote host must not be shown in the rtrv-ip-lnk output.

  1. Display the current IP host information in the database by entering the rtrv-ip-host:display=all command.

    The following is an example of the possible output. 

    
rlghncxa03w 13-06-28 21:17:37 GMT EAGLE5 45.0.0
LOCAL IPADDR    LOCAL HOST
192.1.1.10      IPNODE1-1201
192.1.1.12      IPNODE1-1203
192.1.1.14      IPNODE1-1205
192.1.1.20      IPNODE2-1201
192.1.1.22      IPNODE2-1203
192.1.1.24      IPNODE2-1205
192.1.1.32      KC-HLR2
192.1.1.50      DN-MSC1
192.1.1.52      DN-MSC2

REMOTE IPADDR   REMOTE HOST
150.1.1.5       NCDEPTECONOMIC_DEVELOPMENT. SOUTHEASTERN_COORIDOR_ASHVL. GOV

IP Host table is (10 of 4096) .24% full
  2. Verify that the IP address assigned to the IP links by entering the rtrv-ip-lnk command.

    The following is an example of the possible output. 

    
rlghncxa03w 08-12-28 21:14:37 GMT EAGLE5 40.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
1201  A    192.1.1.10      255.255.255.128 HALF    10    802.3   NO   NO
1201  B    --------------- --------------- HALF    10    DIX     NO   NO
1203  A    192.1.1.12      255.255.255.0   ----    ---   DIX     YES  NO
1203  B    --------------- --------------- HALF    10    DIX     NO   NO
1205  A    192.1.1.14      255.255.255.0   FULL    100   DIX     NO   NO
1205  B    --------------- --------------- HALF    10    DIX     NO   NO
2101  A    192.1.1.20      255.255.255.0   FULL    100   DIX     NO   NO
2101  B    --------------- --------------- HALF    10    DIX     NO   NO
2103  A    192.1.1.22      255.255.255.0   FULL    100   DIX     NO   NO
2103  B    --------------- --------------- HALF    10    DIX     NO   NO
2105  A    192.1.1.24      255.255.255.0   FULL    100   DIX     NO   NO
2105  B    --------------- --------------- HALF    10    DIX     NO   NO
2207  A    192.1.1.32      255.255.255.0   FULL    100   DIX     NO   NO
2207  B    --------------- --------------- HALF    10    DIX     NO   NO
2213  A    192.1.1.50      255.255.255.0   FULL    100   DIX     NO   NO
2213  B    --------------- --------------- HALF    10    DIX     NO   NO
2301  A    192.1.1.52      255.255.255.0   FULL    100   DIX     NO   NO
2301  B    --------------- --------------- HALF    10    DIX     NO   NO

IP-LNK   table is (20 of 2048) 1% full.

    If a local host is being configured in this procedure, the IP address assigned to the local host must be shown in the rtrv-ip-lnk output. If the IP address is not shown in the rtrv-ip-lnk output, add the IP address by performing the Configuring an IP Link procedure.

    If a remote host is being configured in this procedure, the IP address assigned to the remote host cannot be shown in the rtrv-ip-lnk output.

  3. Add IP host information to the database by entering the ent-ip-host command.
    If a local host is being configured, enter the ent-ip-host command with the IP address from 2, and the type=local parameter or without the type parameter. If the type parameter is not specified with the ent-ip-host command, the type parameter value defaults to local.

    If a remote host is being configured, enter the ent-ip-host command with the IP address that is not shown in 2, and the type=remote parameter.

    For example, enter this command.

    ent-ip-host:host=”kc-hlr1”:ipaddr=192.1.1.30

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 06-10-28 21:18:37 GMT EAGLE5 36.0.0
ENT-IP-HOST: MASP A - COMPLTD
  4. Verify the new IP host information in the database by entering the rtrv-ip-host command with the host parameter value specified in 3.

    For this example, enter this command.

    rtrv-ip-host:host=”kc-hlr1”

    The following is an example of the possible output.

    
rlghncxa03w 13-06-28 21:19:37 GMT EAGLE5 45.0.0
LOCAL IPADDR    LOCAL HOST
192.1.1.30      KC-HLR1

IP Host table is (11 of 4096) .26% full
  5. Back up the new changes using the chg-db:action=backup:dest=fixed command.
    These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-4 Adding an IP Host



3.6 Configuring an IP Card

This procedure is used to change the IP stack parameters associated with an IP card in the database using the chg-ip-card command.

The chg-ip-card command uses the following parameters.

:loc – The card location of the IP card

:srchordr – Host Table Search Order

:dnsa – Domain name server A’s IP address. This is an IP address expressed in standard “dot notation.” IP addresses consist of the system’s network number and the machine’s unique host number.

:dnsb – Domain name server B’s IP address. This is an IP address expressed in standard “dot notation.” IP addresses consist of the system’s network number and the machine’s unique host number.

:domain – The domain name is used to construct a fully-qualified DNS name consisting of 120 characters or less. For example, a domain name can be tekelec.com, the hostname is john.doe. The fully-qualified DNS name would be john.doe@tekelec.com.

:defrouter – Default router IP address. This is an IP address expressed in standard “dot notation.” IP addresses consist of the system’s network number and the machine’s unique host number.

:rstdomain – Reset Domain name. The parameter is used to reset the domain to a NULL value.

:sctpcsum – The SCTP checksum algorithm that will be applied to the traffic on the IP card, either adler32 or crc32c. The sctpcsum parameter can be specified only if the SCTPCSUM value in the rtrv-sg-opts output is percard.

The chg-ip-card command contains other parameters that cannot be used in this procedure. Refer to Commands User's Guide for more information about these parameters.

The IP card must be placed out of service.

The rstdomain parameter cannot be specified if the domain parameter is specified.

There is only one default router (defrouter parameter) for each IP card. The default router is used as the primary route unless a static IP routes is defined for the destination IP address. Static IP routes are assigned using the ent-ip-rte command in the Adding an IP Route procedure.

The network portion of the IP address of the default router must match the network portion of one of the IP addresses assigned to the card.

The network portion of the IP address is based on the class of the IP address (shown in Table 3-3). If the IP address is a Class A IP address, the first field is the network portion of the IP address. If the IP address is a Class B IP address, the first two fields are the network portion of the IP address. If the IP address is a Class C IP address, the first three fields are the network portion of the IP address. For example, if the IP address is 193.5.207.150, a Class C IP address, the network portion of the IP address is 193.5.207.

The default router can be associated with only one IP address assigned to the card if the defrouter parameter is specified. For example, the dnsa value for card 1101 is 150.1.1.10. The dnsb value for card 1101 is 160.25.37.1. A default router is provisioned with the IP address 150.1.1.4. The default router is associated with the Ethernet A IP address (the dnsa parameter value), but not the Ethernet B IP address (the dnsb parameter value).

If the default router is associated with one of the IP card’s IP addresses, a second gateway router can be assigned to the other IP address on the IP card by provisioning a static IP route for the IP card using the ent-ip-rte command in the Adding an IP Route procedure. Static IP routes can provide gateway routers associated with the other IP address on the IP card. To provision the gateway router (the gtwy parameter of the ent-ip-rte command) for the other IP address assigned to the IP card, the network portion of the gateway router’s IP address must match the network portion of the other IP address assigned to the IP card.

Specifying the IP address 0.0.0.0 for the dnsa or dnsb parameters, removes the IP address for Ethernet A (dnsa) or Ethernet B (dnsb).

When an IP card is entered into the database with the ent-card command, the IP stack parameters associated with this card are initially set with these default values:

  • :srchordr – SRVR
  • :dnsa – No DNSA IP address is specified
  • :dnsb – No DNSB IP address is specified
  • :domain – No domain name is specified
  • :defrouter – No default router IP address is specified
  • :rstdomain – No
  • :sctpcsum – CRC32C

The value of any optional parameter not specified with the chg-ip-card command is not changed.

  1. Display the current IP parameters associated with card in the database by entering the rtrv-ip-card command.

    The following is an example of the possible output. 

    
rlghncxa03w 08-06-28 21:17:37 GMT EAGLE5 39.0.0
   LOC 1201
     SRCHORDR  SRVR
     DNSA      150.1.1.1
     DNSB      ---------------
     DEFROUTER ---------------
     DOMAIN    ---------------
     SCTPCSUM  crc32c
     BPIPADDR  ---------------
     BPSUBMASK ---------------
   LOC 1203
     SRCHORDR  LOCAL
     DNSA      192.1.1.40
     DNSB      ---------------
     DEFROUTER ---------------
     DOMAIN    NC. TEKELEC. COM
     SCTPCSUM  crc32c
     BPIPADDR  ---------------
     BPSUBMASK ---------------
   LOC 1205
     SRCHORDR  SRVRONLY
     DNSA      192.1.1.40
     DNSB      ---------------
     DEFROUTER ---------------
     DOMAIN    NC. TEKELEC. COM
     SCTPCSUM  crc32c
     BPIPADDR  ---------------
     BPSUBMASK ---------------

    To change the parameters of an IP card, the signaling link to the card and the card have to be inhibited.

  2. Display the signaling link associated with the card shown in 1 using the rtrv-slk command specifying the card location.

    For this example, enter this command.

    rtrv-slk:loc=1201

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
LOC   LINK LSN          SLC TYPE    IPLIML2
1201  A    nc001         0  IPLIM   M2PA
  3. Retrieve the status of the signaling link shown in 2 using the rept-stat-slk command specifying the card location and signaling link.

    For example, enter this command.

    rept-stat-slk:loc=1201:link=a

    The output lists the signaling link assigned to this card: 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
SLK      LSN         CLLI        PST          SST       AST
1201,A   nc001       -----------  IS-NR
        Avail     ----
Command Completed.

    If the signaling link is in service-normal (IS-NR), continue the procedure with 4 to deactivate the signaling link. If the signaling link is out-of-service-maintenance disabled (OOS-MT-DSBLD), continue the procedure with 6 to verify the card status.

  4. Deactivate the signaling link assigned to the IP card using the rept-stat-slk command.

    For example, enter this command.

    dact-slk:loc=1201:link=a

    Caution:

    This command impacts network performance and should only be used during periods of low traffic.

    After this command has successfully completed, this message appears. 

    
rlghncxa03w 06-10-12 09:12:36 GMT EAGLE5 36.0.0
Deactivate Link message sent to card.
  5. Verify the new link status using the rept-stat-slk command.

    For example, enter this command.

    rept-stat-slk:loc=1201:link=a

    The output displays the link status as OOS-MT-DSBLD and gives off a minor alarm: 

    
rlghncxa03w 06-10-27 17:00:36 GMT EAGLE5 36.0.0
SLK      LSN         CLLI        PST          SST       AST
1201,A   nc001       ----------- OOS-MT-DSBLD AVAIL     ---
ALARM STATUS = * 0236 REPT-LKS:not aligned
UNAVAIL REASON = NA 
Command Completed.
  6. Verify the status of the IP card to be inhibited using the rept-stat-card command.

    For example, enter this command.

    rept-stat-card:loc=1201

    This is an example of the possible output. 

    
rlghncxa03w 06-10-27 17:00:36 GMT EAGLE5 36.0.0
CARD  VERSION      TYPE    GPL       PST           SST       AST
1201  114-000-000  DCM     IPLIM     IS-NR         Active    -----
  ALARM STATUS      = No Alarms.
  BPDCM GPL         = 002-102-000
  IMT BUS A         = Conn
  IMT BUS B         = Conn
  SIGNALING LINK STATUS
      SLK    PST                LS            CLLI
      A      IS-NR              nc001         -----------

Command Completed.

    If the IP card to be inhibited is in service-normal (IS-NR), continue the procedure with 7 to inhibit the card. If the IP card is out-of-service-maintenance disabled (OOS-MT-DSBLD), continue the procedure with 9.

  7. Inhibit the IP card using the inh-card command.

    For example, enter this command.

    inh-card:loc=1201

    This message should appear. 

    
rlghncxa03w 06-10-28 21:18:37 GMT EAGLE5 36.0.0
Card has been inhibited.
  8. Display the status of the IP card to verify that it is out-of-service maintenance-disabled (OOS-MT-DSBLD).

    Enter this command.

    rept-stat-card:loc=1201

    This is an example of the possible output. 

    
rlghncxa03w 06-10-27 17:00:36 GMT EAGLE5 36.0.0
CARD  VERSION      TYPE    GPL       PST           SST       AST
1201  114-000-000  DCM     IPLIM     IS-NR         Active    -----
  ALARM STATUS      = No Alarms.
  BPDCM GPL         = 002-102-000
  IMT BUS A         = Conn
  IMT BUS B         = Conn
  SIGNALING LINK STATUS
      SLK    PST                LS            CLLI
      A      IS-NR              nc001         -----------

Command Completed.

    If the defrouter parameter will be specified in 11, continue the procedure with 11.

    If the defrouter parameter will not be specified in 11, continue the procedure by performing one of these steps.
    • If the sctpcsum parameter value for the card will not be changed, continue the procedure with 11.
    • If the sctpcsum parameter value for the card will be changed, continue the procedure with 10.
  9. Verify that the IP address of either Ethernet A or B (the address whose network portion matches the network portion of the defrouter parameter value to be used in 11) is in the IP link table by entering the rtrv-ip-lnk command with the card location specified in this procedure.

    For this example, enter this command.

    rtrv-ip-lnk:loc=1201

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
1201  A    192.1.1.10      255.255.255.0   ----    ---   DIX     YES  NO
1201  B    --------------- --------------- ----    ---   DIX     YES  NO

    If the network portion of the IP address specified by the defrouter value does not match the network portions of either IP address displayed in this step, perform one of these actions:

    • Choose another value for the defrouter parameter, making sure that the network portion of the new IP address matches the network portion of one of the IP addresses displayed in this step.
    • Perform the Configuring an IP Link procedure and change one of the IP addresses shown in this step so that the network portion of the new IP address changed in the Configuring an IP Link procedure matches the network portion of the IP address value for the defrouter parameter.
    After this step has been completed, continue the procedure by performing one of these steps.
    • If the sctpcsum parameter value for the card will not be changed, continue the procedure with 11.
    • If the sctpcsum parameter value for the card will be changed, continue the procedure with 10.
  10. To change the sctpcsum parameter value for the IP card, the sctpcsum parameter value in the rtrv-sg-opts output must be percard. Verify the sctpcsum parameter value by entering the rtrv-sg-opts command.

    The following is an example of the possible output. 

    
rlghncxa03w 08-04-13 09:19:43 GMT EAGLE5 38.0.0
SRKQ:           1500
SNMPCONT:       tekelec
GETCOMM:        public
SETCOMM:        private
TRAPCOMM:       public
SCTPCSUM:       adler32
IPGWABATE:      NO
UAMEASUSEDFTAS: NO

    If the sctpcsum parameter value in the rtrv-sg-opts output is percard, continue the procedure with 11.

    If the sctpcsum parameter value in the rtrv-sg-opts output is adler 32 or crc32c, perform the Changing the SCTP Checksum Algorithm Option for M2PA Associations procedure to change the sctpcsum parameter value to percard. After the Changing the SCTP Checksum Algorithm Option for M2PA Associations procedure has been performed, continue the procedure with 11.

  11. Change the IP stack parameters associated with an IP card in the database using the chg-ip-card command.

    For this example, enter this command.

    chg-ip-card:loc=1201:srchordr=local:dnsa=192.1.1.40:domain=nc.tekelec.com :sctpcsum=adler32

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 06-10-28 21:20:37 GMT EAGLE5 36.0.0
CHG-IP-CARD: MASP A - COMPLTD
  12. Verify the new IP parameters associated with the IP card that was changed in 11 by entering the rtrv-ip-card command with the card location specified in 11.

    For this example, enter this command.

    rtrv-ip-card:loc=1201

    The following is an example of the possible output. 

    
rlghncxa03w 08-06-28 21:17:37 GMT EAGLE5 39.0.0
   LOC 1201
     SRCHORDR  LOCAL
     DNSA      192.1.1.40
     DNSB      ---------------
     DEFROUTER ---------------
     DOMAIN    NC. TEKELEC. COM
     SCTPCSUM  adler32
     BPIPADDR  ---------------
     BPSUBMASK ---------------

    Note:

    If7was not performed, continue the procedure with15.
  13. Allow the IP card that was inhibited in 7 by using the alw-card command.

    For example, enter this command.

    alw-card:loc=1201

    This message should appear. 

    
rlghncxa03w 06-10-28 21:22:37 GMT EAGLE5 36.0.0
Card has been allowed.
  14. Verify the in-service normal (IS-NR) status of the IP card using the rept-stat-card command.

    For example, enter this command.

    rept-stat-card:loc=1201

    This is an example of the possible output. 

    
rlghncxa03w 06-10-27 17:00:36 GMT EAGLE5 36.0.0
CARD  VERSION      TYPE    GPL       PST           SST       AST
1201  114-000-000  DCM     IPLIM     IS-NR         Active    -----
  ALARM STATUS      = No Alarms.
  BPDCM GPL         = 002-102-000
  IMT BUS A         = Conn
  IMT BUS B         = Conn
  SIGNALING LINK STATUS
      SLK    PST                LS            CLLI
      A      IS-NR              nc001         -----------

Command Completed.
  15. Activate the signaling link from 4 using the act-slk command.

    Note:

    If4was not performed, continue the procedure with17.

    For example, enter this command.

    act-slk:loc=1201:link=a

    The link changes its state from OOS-MT-DSBLD (out-of-service maintenance-disabled) to IS-NR (in-service normal).

    The output confirms the activation. 

    
rlghncxa03w 06-10-07 11:11:28 GMT EAGLE5 36.0.0
Activate Link message sent to card
  16. Verify the in-service normal (IS-NR) status of the signaling link using the rept-stat-slk command.

    For example, enter this command.

    rept-stat-slk:loc=1201:link=a

    This message should appear. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
SLK      LSN         CLLI        PST          SST       AST
1201,A   nc001       -----------  IS-NR
        Avail     ----
Command Completed.
  17. Back up the new changes using the chg-db:action=backup:dest=fixed command.
    These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-5 Configuring an IP Card



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

3.7 Adding an IP Route

This procedure is used to add an IP route to the database using the ent-ip-rte command.

The ent-ip-rte command uses these parameters.

:loc – The location of the IP card that the IP route will be assigned to.

:dest – The IP address of the remote host or network.

:submask – The subnet mask of the destination IP address.

:gtwy – The IP address of the gateway or router that will send the IP data to its final destination.

There can be a maximum of 64 IP routes assigned to an IP card.

The EAGLE can contain a maximum of 1024 IP routes.

Ethernet Interfaces A and B on the IP card specified by the loc parameter can be used.

The network portion of the IP address value of the gtwy parameter must be the same as the network portion of the IP addresses shown for either the A or B interfaces in the rtrv-ip-card output.

The value of the dest and gtwy parameters cannot be 127.x.x.x (the loopback address), 0.0.0.0, or the IP addresses of the A or B interfaces on the IP card, and cannot be assigned to another IP card.

If the dest parameter value represents a host IP address, the value for the submask parameter must be 255.255.255.255. Otherwise, the submask parameter value is identifies the network/host ID portions that must be entered when the dest parameter value represents a network address.

The submask is applied to the IP address which is being routed to see if it yields a route match. For example, if IP address 192.1.1.2 is being routed and the IP routing table contains these entries.

Table 3-4 Sample IP Routing Table

IP address Submask Gateway

191.1.0.0

255.255.0.0

192.168.110.250

192.0.0.0

255.0.0.0

192.168.110.251

IP routing occurs as follows:

  1. The subnet mask of route 1 (255.255.0.0) is applied to the IP address being routed (192.1.1.2) with the resulting IP address of 192.1.0.0. IP address 192.1.0.0 does not match IP address 191.1.0.0 in the IP routing table, so the next route is chosen.

  2. The subnet mask of route 2 (255.0.0.0) is applied to the IP address being routed (192.1.1.2) with the resulting IP address of 192.0.0.0 which matches the second route in the IP routing table, so this route is selected for routing this datagram.

See Table 3-5 for the valid input values for the submask and dest parameter combinations.

Table 3-5 Valid Subnet Mask Parameter Values

Network Class IP Network Address Range Valid Subnet Mask Values

A

1.0.0.0 to 127.0.0.0

255.0.0.0 (the default value for a class A IP address)

255.192.0.0

255.224.0.0

255.240.0.0

255.248.0.0

255.252.0.0

255.254.0.0

255.255.128.1

A+B

128.1.0.0 to 191.255.0.0

255.255.0.0 (the default value for a class B IP address)

255.255.192.0

255.255.224.0

255.255.240.0

255.255.248.0

255.255.252.0

255.255.254.0

255.255.255.128

A+B+C

192.0.0.0 to 223.255.255.0

255.255.255.0 (the default value for a class C IP address)

255.255.255.192

255.255.255.224

255.255.255.240

255.255.255.248

255.255.255.252

If a Class B IP address is specified for the dest parameter of the ent-ip-rte command, the subnet address that results from the dest and submask parameter values cannot be the same as the subnet address that results from the pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values of the chg-netopts command. The pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values can be verified by entering the rtrv-netopts command. Choose dest and submask parameter values for the IP route whose resulting subnet address is not be the same as the subnet address resulting from the pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values of the chg-netopts command.

  1. Display the IP routes in the database with the rtrv-ip-rte command.

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
LOC   DEST             SUBMASK          GTWY
1301  128.252.10.5     255.255.255.255  140.188.13.33
1301  128.252.0.0      255.255.0.0      140.188.13.34
1301  150.10.1.1       255.255.255.255  140.190.15.3
1303  192.168.10.1     255.255.255.255  150.190.15.23
1303  192.168.0.0      255.255.255.0    150.190.15.24

IP Route table is  (5 of 2048) 0.24% full
  2. Display the IP cards in the database with the rtrv-ip-card command.

    This is an example of the possible output. 

    
rlghncxa03w 08-08-28 21:17:37 GMT EAGLE5 39.0.0
   LOC 1212
     SRCHORDR  LOCAL
     DNSA      150.1.1.1
     DNSB      ---------------
     DEFROUTER 150.1.1.100
     DOMAIN    NC. TEKELEC. COM
     SCTPCSUM  crc32c
     BPIPADDR  ---------------
     BPSUBMASK ---------------
   LOC 1301
     SRCHORDR  SRVRONLY
     DNSA      140.188.13.10
     DNSB      140.190.15.28
     DEFROUTER ---------------
     DOMAIN    NC. TEKELEC. COM
     SCTPCSUM  crc32c
     BPIPADDR  ---------------
     BPSUBMASK ---------------
   LOC 1303
     SRCHORDR  LOCAL
     DNSA      150.190.15.1
     DNSB      ---------------
     DEFROUTER 150.190.15.25
     DOMAIN    NC. TEKELEC. COM
     SCTPCSUM  crc32c
     BPIPADDR  ---------------
     BPSUBMASK ---------------

    If the required IP card is not shown in the rtrv-ip-card output, perform the Adding an IPLIMx Card procedure to add the card to the database.

    Perform the Configuring an IP Card procedure and make sure that the network portion of the IP addresses assigned for the A or B interfaces of the IP card is the same as the network portion of the IP address that will be assigned to the gtwy parameter of the IP route

    Note:

    If a Class A or CIP address (seeTable 3-5) will be specified for thedest parameter in4, continue the procedure with4.
  3. The subnet address that results from the dest and submask parameter values of the ent-ip-rte command cannot be the same as the subnet address that results from the pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values of the chg-netopts command.

    Display the pvn, pvnmask, fcna, fcnamask, fcnb, and fcnbmask parameter values of the chg-netopts command by entering the rtrv-netoptscommand.

    If error message E3967 Cmd Rej: E5IS must be on is displayed after the rtrv-netopts command is executed, the pvn, pvnmask, fcna, fcnamask, fcnb, and fcnbmask parameters are not configured. Continue the procedure with 4.

    This is an example of the possible output if the E5IS feature is on. 

    
rlghncxa03w 09-02-28 21:17:37 GMT EAGLE5 40.1.0
NETWORK OPTIONS
------------------
PVN        = 128.20.30.40
PVNMASK    = 255.255.192.0
FCNA       = 170.120.50.0
FCNAMASK   = 255.255.240.0
FCNB       = 170.121.50.0
FCNBMASK   = 255.255.254.0

    Choose dest and submask parameter values for the IP route whose resulting subnet address is not be the same as the subnet address resulting from the pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values of the chg-netopts command. Continue the procedure with 4.

  4. Add the IP route to the database using the ent-ip-rte command.

    For this example, enter this command.

    ent-ip-rte:loc=1212:dest=132.10.175.20:submask=255.255.255.255 :gtwy=150.1.1.50

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-12 09:12:36 GMT EAGLE5 36.0.0
ENT-IP-RTE: MASP A - COMPLTD
  5. Verify the changes using the rtrv-ip-rte command with the card location specified with the ent-ip-rte command in 4.

    For this example, enter these commands.

    rtrv-ip-rte:loc=1212

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
LOC   DEST             SUBMASK          GTWY
1212  132.10.175.20    255.255.255.255  150.1.1.50
IP Route table is  (6 of 2048) 0.29% full
  6. Back up the new changes using the chg-db:action=backup:dest=fixed command.
    These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-6 Adding an IP Route



Sheet 1 of 2



Sheet 2 of 2

3.8 Adding an M2PA Association

This procedure is used to configure M2PA associations using the ent-assoc command. The combination of a local host, local SCTP port, remote host and remote SCTP port defines an association. M2PA associations are assigned to cards running either the IPLIM or IPLIMI applications (IPLIMx cards).

The ent-assoc command uses these parameters:

:aname – The name assigned to the association. Valid association names can contain up to 15 alphanumeric characters where the first character is a letter and the remaining characters are alphanumeric characters. The aname parameter value is not case-sensitive.

:lhost – Local Hostname. The logical name assigned to the local host device.

:lport – The SCTP port number for the local host.

:rhost – Remote Hostname. The logical name assigned to the remote host device.

:rport – The SCTP port number for the remote host.

:link – The signaling link on the IP card. If a signaling link is not specified for a association when it is entered, the association defaults to signaling link A. If the card is an E5-ENET or E5-ENET-B card, the values for the link parameter can be a, a1, a2, a3, a4, a5, a6, a7, b, b1, b2, b3, b4, b5, b6, or b7.

Note:

The port parameter can be used in place of the link parameter to specify the signaling link on the card.

:adapter – The adapter layer for this association, m2pa. The adapter parameter is optional. The default value for the adapter parameter is m2pa.

:alhost – The alternate local host name.

:m2patset – The M2PA timer set assigned to the association. The m2patset parameter can be specified only with the adapter=m2pa parameter. If the adapter=m2pa parameter is specified, and the m2patset parameter is not specified with the ent-assoc command, the default value for the m2patset parameter (1 - M2PA timer set 1) is assigned to the association.

Associations contain fields whose values are not assigned using the ent-assoc command. When an association is added to the database, these fields receive their default values. If a different value is desired, the chg-assoc command must be used. To change these values perform the Changing the Attributes of an M2PA Association procedure.

These fields and their default values are shown in Table 3-6.

Table 3-6 M2PA Association Fields and Default Values

open=no

rmax=800

cwmin=3000

alw=no

uaps=10

istrms=2

rmode=lin

rtimes=10

ostrms=2

rmin=120

ver=rfc bufsize=200 rtxthr=0 rhostval=relaxed

An M2PA association that is assigned to an IPLIMx signaling link can contain a UA parameter set value (the uaps parameter). The uaps parameter cannot be specified with the ent-assoc command. The default value for the uaps parameter is 10. While the uaps parameter value can be changed with the chg-assoc command, the uaps parameter value has no impact on the traffic carried by an M2PA association that is assigned to an IPLIMx signaling link.The uaps parameter value impacts M3UA or SUA associations that are assigned to IPGWx signaling links and M2PA and M3UA associations that are assigned to IPSG cards. The uaps parameter value is shown in the UAPS field in the rtrv-assoc output for an M2PA associations that is assigned to an IPLIMx signaling link.

An M2PA association can contain an alternate remote host. The alternate remote host is provisioned with the rhost and rhostype=alternate parameters of the chg-assoc command. A primary remote host can be provisioned in this procedure by specifying the rhost parameter with the ent-assoc command. To provision an alternate remote host for an M2PA association, perform Changing the Attributes of an M2PA Association.

The size of the buffers on the on the E5-ENET and E5-ENET-B cards are shown in the following list.

  • E5-ENET Card and E5-ENET-B - 3200 KB

The size of the buffers assigned to each association that is assigned to the IP card cannot exceed the maximum buffer size for the IP card. When a new association is added, the default buffer size for the association is assigned to the association. If adding the new association causes the total buffer size for all the associations on the IP card to exceed the maximum buffer size for that IP card, the ent-assoc command will be rejected. If the you wish to add the association and the maximum buffer size for the IP card will be exceeded, the buffer size of the other associations assigned to the IP card must be decreased by performing the Changing the Buffer Size of a M2PA Association procedure. The available size of the buffers on the IP card can be verified by entering this command.

rtrv-assoc:lhost=<local host name assigned to the association being changed>

The alhost parameter can also be used with the rtrv-assoc command to display the available size of the buffers on the IP card.

The aname parameter can be used with the rtrv-assoc command to display the available size of the buffers on the IP card and the size of the buffer assigned to the association.

The value of the lhost, rhost, or alhost parameters is a text string of up to 60 characters, with the first character being a letter. The command line on the terminal can contain up to 150 characters. If the host names are too long to fit on the ent-assoc command line, perform the chg-assoc command with the parameters and values necessary to complete the entry of the M2PA association.

The EAGLE can contain a maximum of 4000 connections (association to application server assignments).

IPLIMx cards can contain one association for each signaling link on the card. The E5-ENET card can contain a maximum of 16 signaling links, resulting in a maximum of 16 associations for this card.

The B Ethernet interface of the IP card can be used on the E5-ENET card.

If the association is to be activated in this procedure, with the chg-assoc command, the association must contain values for the lhost, lport, rhost, rport parameters.

The ipliml2 parameter value of the signaling link assigned to the association must be m2pa. The adapter parameter value of the association must be m2pa.

The signaling link being assigned to the association must be out of service. This state is shown in the rept-stat-slk output with the entries OOS-MT in the PST field and Unavail in the SST field.

If the association is being opened in this procedure with the chg-assoc command and the open=yes parameter, the signaling link assigned to the association must be in the database and the ipliml2 parameter value of the signaling link assigned to the association must be m2pa.

Uni-homed endpoints are associations configured with the lhost parameter only. The lhost parameter value represents an IP address that corresponds to either the A or B network interface of the IP card. Multi-homed endpoints are associations configured with both the lhost and alhost parameters. The lhost parameter value represents an IP address corresponding to one of the network interfaces (A or B) of the IP card while the alhost parameter value represents an IP address corresponding to the other network interface of the same IP card.

An alternate remote host can be configured for multi-homed associations using the rhost and rhosttype parameters of the chg-assoc command. The rhost parameter value with the rhostype=primary parameter represents an IP address that corresponds to one of the network interfaces at the remote end while the rhost parameter value with the rhostype=alternate parameter represents an IP address that corresponds to the other network interface at the remote end.

Canceling the RTRV-ASSOC Command

Because the rtrv-assoc command used in this procedure can output information for a long period of time, the rtrv-assoc command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-assoc command can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-assoc command was entered.

  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-assoc command was entered.

  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-assoc command was entered, from another terminal other that the terminal where the rtrv-assoc command was entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

  1. Display the associations in the database using the rtrv-assoc command. This is an example of possible output. 
    
rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0
                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
swbel32         1201 A     A    M3UA    1030  2345  YES  YES
a2              1305 A     A    SUA     1030  2345  YES  YES
a3              1307 A     A    SUA     1030  2346  YES  YES
assoc3          1203 A     A1   M2PA    2048  1030  NO   NO
    Perform one of these actions.
    • If the desired IP link (shown by the entries in the CARD LOC and IPLINK PORT columns for an association whose ADAPTER value is M2PA) is shown in the rtrv-assoc output, continue the procedure with 2.
    • If the desired IP link is not shown in the rtrv-assoc output, continue the procedure with 3.
  2. Display the signaling links assigned to the card that the new M2PA association will be assigned to by entering the rtrv-slk command with the card location displayed in 1. For this example, enter this command.

    rtrv-slk:loc=1203

    The following is an example of the possible output. 

    rlghncxa03w 08-04-06 10:07:25 GMT EAGLE5 38.0.0

LOC  LINK LSN         SLC TYPE     IPLIML2
1203 A    e5e6a       0   IPLIM    M2PA
1203 A1   m2pa1       0   IPLIM    M2PA

    If the value in the TYPE column is either IPLIM or IPLIMI, continue the procedure with 6.

    If the value in the TYPE column is IPSG, the links and host assigned to this card cannot be used in this procedure. If you wish to use this card to configure an M2PA association, perform the Adding an IPSG M2PA Association procedure.

    If you do not wish to use this card to configure an M2PA association, perform one of these actions.
    • Choose another card from the rtrv-assoc output in 1 and repeat this step.
    • Continue the procedure with 3 to choose another IPLIMx card and IP link for the new M2PA association.
  3. Display the IP links in the database by entering the rtrv-ip-lnk command. The following is an example of the possible output. 
    
rlghncxa03w 08-12-28 21:14:37 GMT EAGLE5 40.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
1201  A    192.1.1.10      255.255.255.128 HALF    10    802.3   NO   NO
1201  B    --------------- --------------- HALF    10    DIX     NO   NO
1203  A    192.1.1.12      255.255.255.0   ----    ---   DIX     YES  NO
1203  B    --------------- --------------- HALF    10    DIX     NO   NO
1205  A    192.1.1.14      255.255.255.0   FULL    100   DIX     NO   NO
1205  B    --------------- --------------- HALF    10    DIX     NO   NO
2101  A    192.1.1.20      255.255.255.0   FULL    100   DIX     NO   NO
2101  B    --------------- --------------- HALF    10    DIX     NO   NO
2103  A    192.1.1.22      255.255.255.0   FULL    100   DIX     NO   NO
2103  B    --------------- --------------- HALF    10    DIX     NO   NO
2105  A    192.1.1.24      255.255.255.0   FULL    100   DIX     NO   NO
2105  B    --------------- --------------- HALF    10    DIX     NO   NO
2205  A    192.1.1.30      255.255.255.0   FULL    100   DIX     NO   NO
2205  B    --------------- --------------- HALF    10    DIX     NO   NO
2207  A    192.1.1.32      255.255.255.0   FULL    100   DIX     NO   NO
2207  B    --------------- --------------- HALF    10    DIX     NO   NO
2213  A    192.1.1.50      255.255.255.0   FULL    100   DIX     NO   NO
2213  B    --------------- --------------- HALF    10    DIX     NO   NO
2301  A    192.1.1.52      255.255.255.0   FULL    100   DIX     NO   NO
2301  B    --------------- --------------- HALF    10    DIX     NO   NO

IP-LNK   table is (20 of 2048) 1% full.

    If the required IP link is not in the database, add the IP link using the Configuring an IP Link procedure.

  4. Verify that the local host name to be assigned to the association is in the database by using the rtrv-ip-host:display=all command. The following is an example of the possible output. 
    
rlghncxa03w 13-06-28 21:15:37 GMT EAGLE5 45.0.0

LOCAL IPADDR    LOCAL HOST
192.1.1.10      IPNODE1-1201
192.1.1.12      IPNODE1-1203
192.1.1.14      IPNODE1-1205
192.1.1.20      IPNODE2-1201
192.1.1.22      IPNODE2-1203
192.1.1.24      IPNODE2-1205
192.1.1.30      KC-HLR1
192.1.1.32      KC-HLR2
192.1.1.50      DN-MSC1
192.1.1.52      DN-MSC2

REMOTE IPADDR   REMOTE HOST
150.1.1.5       NCDEPTECONOMIC_DEVELOPMENT. SOUTHEASTERN_COORIDOR_ASHVL. GOV

IP Host table is (11 of 4096) .26% full

    The IP address of the IP link should be assigned to the local host name that will be assigned to the association.

    The ipliml2 parameter value of the signaling link must be m2pa.

    The values of the lhost and alhost parameters must be in the LOCAL HOST column in the rtrv-ip-host output.

    If the required hostname is not in the database, add the IP host name using the Adding an IP Host procedure.

  5. Display the signaling links assigned to the card that the new M2PA association will be assigned to by entering the rtrv-slk command with the card location displayed in 3 or the card location of the IP link that was configured by performing the Configuring an IP Link procedure in 3. For this example, enter this command.

    rtrv-slk:loc=1203

    The following is an example of the possible output. 

    rlghncxa03w 08-04-06 10:07:25 GMT EAGLE5 38.0.0

LOC  LINK LSN         SLC TYPE     IPLIML2
1203 A    e5e6a       0   IPLIM    M2PA
1203 A1   m2pa1       0   IPLIM    M2PA

    If the signaling link that you wish to assign to the association is shown in the rtrv-slk output, continue the procedure with 6.

    If the signaling link that you wish to assign to the association is not shown in the rtrv-slk output, add the signaling link to the database with the ipliml2=m2pa parameter, and without activating the signaling link, by performing the Adding an IPLIMx Signaling Link procedure. After the signaling link has been added, continue the procedure with 9.

  6. Display the status of the signaling link shown in 5 using the rept-stat-slk command specifying the card location and signaling link. For example, enter this command.

    rept-stat-slk:loc=1203:link=a

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
SLK      LSN         CLLI        PST          SST       AST
1203,A   e5e6a       ----------- IS-NR        Avail     ----
Command Completed.

    If the primary state (PST) of the signaling link is OOS-MT and the secondary state (SST) is Unavail, continue the procedure with 9.

    If the primary state (PST) of the signaling link not is OOS-MT and the secondary state (SST) is not Unavail, continue the procedure with 7.

  7. Deactivate the signaling link from 6 using the dact-slk command. For example, enter this command.

    dact-slk:loc=1203:link=a

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 08-04-07 11:11:28 GMT EAGLE5 38.0.0
Deactivate Link message sent to card
  8. Verify the status of the signaling link using the rept-stat-slk command. For example, enter this command.

    rept-stat-slk:loc=1203:link=a

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
SLK      LSN         CLLI        PST          SST       AST
1203,A   e5e6a       ----------- OOS-MT       Unavail   ----
Command Completed.
  9. Verify the values of the M2PA timer set you wish to assign to the association by entering the rtrv-m2pa-tset command with the ver=rfc parameter.
    When an M2PA association is provisioned in this procedure, the RFC M2PA version is assigned to the M2PA association by default.

    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 RFCM2PA 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.

    If you wish to assign the Draft 6 M2PA version to this association and use the Draft 6 M2PA timer sets, perform the Changing the Attributes of an M2PA Association procedure after this procedure is completed to change the M2PA version of this association.

    Note:

    If them2patset parameter will not be specified with theent-assoc command, theM2PA timer set 1 will be assigned to the association.

    To display the M2PA Draft 6 timer values, enter this command.

    rtrv-m2pa-tset:ver=d6

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0

M2PA Draft 6 Timers (in msec, T16 in microsec)
TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16    T17  T18
1    6000   ------ 5000  20000 500  5000  4000 1000  100000 150  500
2    7500   ------ 1500  2000  500  9000  1250 300   150000 175  600
3    100000 ------ 2000  3000  500  4000  1500 500   170000 200  800
4    200000 ------ 20000 4000  500  6000  2000 700   480000 225  900
5    250000 ------ 30000 30000 500  100   2250 400   400000 400  8000
6    50000  ------ 50000 60000 500  500   4500 800   300000 300  7000
7    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
8    80000  ------ 1500  15000 500  8000  2750 1100  350000 350  5000
9    27500  ------ 3850  4859  450  5700  3750 1150  250    375  8750
10   90000  ------ 2500  50000 500  7500  5000 1750  440000 450  3000
11   20000  ------ 4500  5500  500  6500  5500 1600  250000 475  4500
12   30000  ------ 7500  7000  500  750   4250 1800  275000 275  3500
13   40000  ------ 35000 9000  500  1250  3500 1900  500    325  9000
14   70000  ------ 45000 11000 500  1500  1750 900   1000   125  6000
15   9000   ------ 25000 40000 500  2500  3250 600   5000   425  5500
16   75000  ------ 15000 25000 500  4500  1600 1400  6000   240  9500
17   350000 ------ 60000 70000 600  10000 6000 2000  500000 500  10000
18   150000 ------ 55000 35000 500  3500  5750 1500  125000 440  750
19   175000 ------ 12500 45000 500  1100  2600 1300  7000   340  850
20   1000   ------ 1000  1000  400  80    1000 200   100    100  100

    To display the M2PARFC values, enter this command.

    rtrv-m2pa-tset:ver=rfc

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0

M2PA RFC Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16    T17  T18
1    6000   75000  5000  20000 500  5000  4000 1000  100000 150  500
2    7500   8000   1500  2000  500  9000  1250 300   150000 175  600
3    100000 10000  2000  3000  500  4000  1500 500   170000 200  800
4    200000 6000   20000 4000  500  6000  2000 700   480000 225  900
5    250000 140000 30000 30000 500  100   2250 400   400000 400  8000
6    50000  100000 50000 60000 500  500   4500 800   300000 300  7000
7    300000 20000  2000  10000 500  1000  3000 1200  200000 250  1000
8    80000  130000 1500  15000 500  8000  2750 1100  350000 350  5000
9    27500  120000 3850  4859  450  5700  3750 1150  250    375  8750
10   90000  9000   2500  50000 500  7500  5000 1750  440000 450  3000
11   20000  60000  4500  5500  500  6500  5500 1600  250000 475  4500
12   30000  50000  7500  7000  500  750   4250 1800  275000 275  3500
13   40000  90000  35000 9000  500  1250  3500 1900  500    325  9000
14   70000  45000  45000 11000 500  1500  1750 900   1000   125  6000
15   9000   30000  25000 40000 500  2500  3250 600   5000   425  5500
16   75000  15000  15000 25000 500  4500  1600 1400  6000   240  9500
17   350000 150000 60000 70000 600  10000 6000 2000  500000 500  10000
18   150000 20000  55000 35000 500  3500  5750 1500  125000 440  750
19   175000 12500  12500 45000 500  1100  2600 1300  7000   340  850
20   1000   5000   1000  1000  400  80    1000 200   100    100  100

    If the ver parameter is not specified when entering the rtrv-m2pa-tset command, both the Draft 6 and RFC values are displayed. This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0

M2PA Draft 6 Timers (in msec, T16 in microsec)
TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16    T17  T18
1    6000   ------ 5000  20000 500  5000  4000 1000  100000 150  500
2    7500   ------ 1500  2000  500  9000  1250 300   150000 175  600
3    100000 ------ 2000  3000  500  4000  1500 500   170000 200  800
4    200000 ------ 20000 4000  500  6000  2000 700   480000 225  900
5    250000 ------ 30000 30000 500  100   2250 400   400000 400  8000
6    50000  ------ 50000 60000 500  500   4500 800   300000 300  7000
7    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
8    80000  ------ 1500  15000 500  8000  2750 1100  350000 350  5000
9    27500  ------ 3850  4859  450  5700  3750 1150  250    375  8750
10   90000  ------ 2500  50000 500  7500  5000 1750  440000 450  3000
11   20000  ------ 4500  5500  500  6500  5500 1600  250000 475  4500
12   30000  ------ 7500  7000  500  750   4250 1800  275000 275  3500
13   40000  ------ 35000 9000  500  1250  3500 1900  500    325  9000
14   70000  ------ 45000 11000 500  1500  1750 900   1000   125  6000
15   9000   ------ 25000 40000 500  2500  3250 600   5000   425  5500
16   75000  ------ 15000 25000 500  4500  1600 1400  6000   240  9500
17   350000 ------ 60000 70000 600  10000 6000 2000  500000 500  10000
18   150000 ------ 55000 35000 500  3500  5750 1500  125000 440  750
19   175000 ------ 12500 45000 500  1100  2600 1300  7000   340  850
20   1000   ------ 1000  1000  400  80    1000 200   100    100  100

M2PA RFC Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16    T17  T18
1    6000   75000  5000  20000 500  5000  4000 1000  100000 150  500
2    7500   8000   1500  2000  500  9000  1250 300   150000 175  600
3    100000 10000  2000  3000  500  4000  1500 500   170000 200  800
4    200000 6000   20000 4000  500  6000  2000 700   480000 225  900
5    250000 140000 30000 30000 500  100   2250 400   400000 400  8000
6    50000  100000 50000 60000 500  500   4500 800   300000 300  7000
7    300000 20000  2000  10000 500  1000  3000 1200  200000 250  1000
8    80000  130000 1500  15000 500  8000  2750 1100  350000 350  5000
9    27500  120000 3850  4859  450  5700  3750 1150  250    375  8750
10   90000  9000   2500  50000 500  7500  5000 1750  440000 450  3000
11   20000  60000  4500  5500  500  6500  5500 1600  250000 475  4500
12   30000  50000  7500  7000  500  750   4250 1800  275000 275  3500
13   40000  90000  35000 9000  500  1250  3500 1900  500    325  9000
14   70000  45000  45000 11000 500  1500  1750 900   1000   125  6000
15   9000   30000  25000 40000 500  2500  3250 600   5000   425  5500
16   75000  15000  15000 25000 500  4500  1600 1400  6000   240  9500
17   350000 150000 60000 70000 600  10000 6000 2000  500000 500  10000
18   150000 20000  55000 35000 500  3500  5750 1500  125000 440  750
19   175000 12500  12500 45000 500  1100  2600 1300  7000   340  850
20   1000   5000   1000  1000  400  80    1000 200   100    100  100

    If the M2PA timer set you wish to assign to the association does not contain the desired values, go to the Changing a M2PA Timer Set procedure and changed the desired timer values.

    Caution:

    Changing an M2PA timer set may affect the performance of any associations using the timer set being changed.
  10. Verify the available buffer size for the IP card that will contain the association being added in this procedure by entering the rtrv-assoc command with the local host name assigned to the association being added. For this example, enter this command.

    rtrv-assoc:lhost="IPNODE2-1203"

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0
                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
assoc2          1203 A     A1   M2PA    2048  1030  NO   NO 

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (200 KB of 1600 KB) on LOC = 1203

    If adding the new association causes the total buffer size for all the associations on the IP card to exceed the maximum buffer size for that IP card, the ent-assoc command will be rejected.

    The default buffer value for an IPLIMx association is 200.

    If the you wish to add the association and the maximum buffer size for the IP card will be exceeded, the buffer size of the other associations assigned to the IP card must be decreased by performing the Changing the Buffer Size of a M2PA Association procedure.

  11. Add the associations using the ent-assoc command. For this example, enter this command.

    ent-assoc:aname=assoc2:lhost=gw107.nc.tekelec.com:lport=2000: rhost=gw100.nc.tekelec.com:rport=1030:adapter=m2pa:link=a

    These are the rules that apply to adding M2PA associations that are assigned to IPLIMx signaling links.
    • The B Ethernet interface can be used with E5-ENET cards.
    • The EAGLE can contain a maximum of 4000 connections (association – application server assignments plus sockets).
    • The adapter parameter value for the association must be m2pa. The value of the ipliml2 parameter of the signaling link being assigned to this association must be m2pa. The default value for the adapter parameter is m2pa.
    • IPLIMx cards can have only one connection for each signaling link assigned to the card. If the card is an E5-ENET card, the card may contain a maximum of 16 connections.
    • The value of the lhost, rhost, or alhost parameters is a text string of up to 60 characters, with the first character being a letter. The command line on the terminal can contain up to 150 characters. If the host names are too long to fit on the ent-assoc command line, perform the chg-assoc command with the parameters and values necessary to complete the entry of the M2PA association.
    • If the new association is to be activated in this procedure with the chg-assoc command, the association must contain values for the lhost, rhost, lport, and rport parameters.
    • If the lhost and alhost parameters are specified, the lhost parameter value represents the IP address corresponding to one of the network interfaces (A or B) on the IP card while the alhost parameter value represents the IP address corresponding to the other network interface of the same IP card.
    • The m2patset parameter can be specified only with the adapter=m2pa parameter.
    • The m2patset parameter value defaults to M2PA timer set 1 (m2patset=1) if the m2patset parameter is not specified.
    • The port parameter can be used in place of the link parameter to specify the signaling link assigned to the association.
    • When the adapter=m2pa parameter is specified, the RFC M2PA version is assigned to the M2PA association by default. If you wish to assign the Draft 6 M2PA version to this association, perform the Changing the Attributes of an M2PA Associationprocedure after this procedure is completed to change the M2PA version of this association.

    When each of these commands have successfully completed, this message should appear. 

    
rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0
ENT-ASSOC: MASP A - COMPLTD

    Note:

    If the association added in this step is not being activated in this procedure, continue the procedure with13.
  12. Activate the association added in 11 by entering the chg-assoc command with the association name specified in 11 and the open=yes and alw=yes parameters. For example, enter this command.

    chg-assoc:aname=assoc2:open=yes:alw=yes

    When this command have successfully completed, this message should appear. 

    
rlghncxa03w 08-04-28 21:15:37 GMT EAGLE5 38.0.0
CHG-ASSOC: MASP A - COMPLTD
  13. Verify the changes using the rtrv-assoc command specifying the association name specified in 11 and 12. For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of possible output. 

    
rlghncxa03w 10-07-28 09:12:36 GMT EAGLE5 42.0.0
ANAME assoc2
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  M2PA          VER         M2PA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    1030          RPORT       1030
      ISTRMS   2             OSTRMS      2           BUFSIZE  200
      RMODE    LIN           RMIN        120         RMAX     800
      RTIMES   10            CWMIN       3000        UAPS     10
      OPEN     NO            ALW         NO          RTXTHR   0
      RHOSTVAL RELAXED       M2PATSET    1

IP Appl Sock table is (5 of 4000) 1% full
Assoc Buffer Space Used (400 KB of 1600 KB) on LOC = 1203
  14. Activate the signaling link assigned to the association using the act-slk command.

    For example, enter this command.

    act-slk:loc=1203:link=a

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 08-04-07 11:11:28 GMT EAGLE5 38.0.0
Activate Link message sent to card
  15. Verify the status of the signaling link using the rept-stat-slk command. For example, enter this command.

    rept-stat-slk:loc=1203:link=a

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
SLK      LSN         CLLI        PST          SST       AST
1203,A   e5e6a       ----------- IS-NR        Avail     ----
Command Completed.
  16. Back up the new changes, using the chg-db:action=backup:dest=fixed command. These messages should appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-7 Adding an M2PA Association



Sheet 1 of 3



Sheet 2 of 3



Sheet 3 of 3

3.9 Activating the Large MSU Support for IP Signaling Feature

This procedure is used to enable and turn on the Large MSU Support for IP Signaling feature using the feature’s part number and a feature access key.

The feature access key for the Large MSU Support for IP Signaling feature is based on the feature’s part number and the serial number of the EAGLE, making the feature access key site-specific.

The enable-ctrl-feat command enables the controlled feature by inputting the controlled feature’s access key and the controlled feature’s part number with these parameters:

Note:

As of Release 46.3, the fak parameter is no longer required. This parameter is only used for backward compatibility.

:fak – The feature access key provided by Oracle. The feature access key contains 13 alphanumeric characters and is not case sensitive.

:partnum – The Oracle-issued part number of the Large MSU Support for IP Signaling feature, 893018401.

The enable-ctrl-feat command requires that the database contain a valid serial number for the EAGLE, and that this serial number is locked. This can be verified with the rtrv-serial-num command. The EAGLE is shipped with a serial number in the database, but the serial number is not locked. The serial number can be changed, if necessary, and locked once the EAGLE is on-site, by using the ent-serial-num command. The ent-serial-num command uses these parameters.

:serial – The serial number assigned to the EAGLE. The serial number is not case sensitive.

:lock – Specifies whether or not the serial number is locked. This parameter has only one value, yes, which locks the serial number. Once the serial number is locked, it cannot be changed.

Note:

To enter and lock the EAGLE’s serial number, the ent-serial-num command must be entered twice, once to add the correct serial number to the database with the serial parameter, then again with the serial and the lock=yes parameters to lock the serial number. You should verify that the serial number in the database is correct before locking the serial number. The serial number can be found on a label affixed to the control shelf (shelf 1100).

This feature cannot be temporarily enabled (with the temporary feature access key).

Once this feature has been enabled, the feature must be turned on with the chg-ctrl-feat command. The chg-ctrl-feat command uses these parameters:

:partnum – The Oracle-issued part number of the Large MSU Support for IP Signaling feature, 893018401.

:status=on – used to turn the Large MSU Support for IP Signaling feature on.

Once the Large MSU Support for IP Signaling feature has been turned on, it be can be turned off. For more information about turning the Large MSU Support for IP Signaling feature off, go to the Turning Off the Large MSU Support for IP Signaling Feature procedure.

The status of the features in the EAGLE is shown with the rtrv-ctrl-feat command.

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 service information field (SIF) that is larger than 272 bytes. The large messages are processed only on E5-ENET cards. There are certain software components that if enabled or provisioned, that will not process large messages even if the Large MSU Support for IP Signaling feature is enabled and turned on. UIMs are displayed when most of these circumstances occur. These UIMs are:

  • UIM 1333 – Displayed when a large message is received on an M3UA association and the Large MSU Support for IP Signaling feature is not enabled or is enabled and turned off. The large message is discarded.
  • UIM 1350 – Displayed when a M2PA IP connection receives message with an SIF greater than 272 bytes and the Large MSU Support for IP Signaling feature is not enabled or is enabled and turned off. The large message is discarded.
  • UIM 1352 – Displayed when a message with an SIF greater than 272 bytes is received; the Large MSU Support for IP Signaling feature is enabled and turned on; there are routes available for the destination point code; but the selected outbound card does not support large messages.
  • UIM 1353 – Displayed when a large message passes a gateway screening screenset that redirects messages for the Database Transport Access (DTA) feature. Large messages are not redirected for the DTA feature.

For more information on these UIMs, refer to the Unsolicited Alarm and Information Messages Reference.

Note:

For STC style monitoring, large messages are not monitored by the EAGLE 5 Integrated Monitoring Support feature and are not sent to the IMF. A UIM is not generated. If Fast Copy is allowed, however, Fast Copy can copy large MSUs to IMF.
  1. Display the status of the controlled features by entering the rtrv-ctrl-feat command.

    The following is an example of the possible output. 

    rlghncxa03w 08-04-28 21:15:37 GMT EAGLE5 38.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Command Class Management  893005801  on      ----
LNP Short Message Service 893006601  on      ----
Intermed GTT Load Sharing 893006901  on      ----
XGTT Table Expansion      893006101  on      400000
XMAP Table Expansion      893007710  off     ----
Large System # Links      893005910  on      2000
Routesets                 893006401  on      6000
HC-MIM SLK Capacity       893012707  on      64

The following features have been temporarily enabled:

Feature Name              Partnum    Status  Quantity     Trial Period Left
Zero entries found.

The following features have expired temporary keys:

Feature Name              Partnum
Zero entries found.

    If the Large MSU Support for IP Signaling feature is enabled and turned on, no further action is necessary. This procedure does not need to be performed.

    If the Large MSU Support for IP Signaling feature is enabled and but not turned on, continue this procedure with 7.

    If the Large MSU Support for IP Signaling feature is not enabled, continue this procedure with 2.

    Note:

    If the rtrv-ctrl-feat output in 1shows any controlled features, continue this procedure with 6. If thertrv-ctrl-feat output shows only the HC-MIM SLK Capacity feature with a quantity of 64, 2 through 5 must be performed.
  2. Display the serial number in the database with the rtrv-serial-num command.

    This is an example of the possible output. 

    rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
System serial number = nt00001231

System serial number is not locked.

rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
Command Completed

    Note:

    If the serial number is correct and locked, continue the procedure with6. If the serial number is correct but not locked, continue the procedure with 5. If the serial number is not correct, but is locked, this feature cannot be enabled and the remainder of this procedure cannot be performed. Contact the Customer Care Center to get an incorrect and locked serial number changed. Refer to unresolvable-reference.html#GUID-1825DD07-2A6B-4648-859A-1258A0F9AC40 for the contact information. The serial number can be found on a label affixed to the control shelf (shelf 1100).
  3. Enter the correct serial number into the database using the ent-serial-num command with the serial parameter.

    For this example, enter this command.

    ent-serial-num:serial=<EAGLE’s correct serial number>

    When this command has successfully completed, the following message should appear. 

    rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
ENT-SERIAL-NUM:  MASP A - COMPLTD
  4. Verify that the serial number entered into ietf-m2pa-configuration-procedures1.html was entered correctly using the rtrv-serial-num command.

    This is an example of the possible output. 

    rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
System serial number = nt00001231

System serial number is not locked.

rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
Command Completed

    If the serial number was not entered correctly, repeat ietf-m2pa-configuration-procedures1.html and ietf-m2pa-configuration-procedures1.html and re-enter the correct serial number.

  5. Lock the serial number in the database by entering the ent-serial-num command with the serial number shown in ietf-m2pa-configuration-procedures1.html, if the serial number shown in ietf-m2pa-configuration-procedures1.html is correct, or with the serial number shown in ietf-m2pa-configuration-procedures1.html, if the serial number was changed in ietf-m2pa-configuration-procedures1.html, and with the lock=yes parameter.

    For this example, enter this command.

    ent-serial-num:serial=<EAGLE’s serial number>:lock=yes

    When this command has successfully completed, the following message should appear. 

    rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
ENT-SERIAL-NUM:  MASP A - COMPLTD
  6. Enable the Large MSU Support for IP Signaling feature with the enable-ctrl-feat command specifying the part number for the Large MSU Support for IP Signaling feature and the feature access key. Enter this command.

    enable-ctrl-feat:partnum=893018401:fak=<Large MSU Support for IP Signaling feature access key>

    Note:

    A temporary feature access key cannot be specified to enable this feature.

    Note:

    The values for the feature access key (the fak parameter) are provided by Oracle. If you do not have the feature access key for the feature you wish to enable, contact your Sales Representative or Account Representative.

    When the enable-crtl-feat command has successfully completed, this message should appear. 

    rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
ENABLE-CTRL-FEAT: MASP B - COMPLTD
  7. Turn the Large MSU Support for IP Signaling feature on with the chg-ctrl-feat command specifying the part number for the Large MSU Support for IP Signaling feature and the status=on parameter. Enter this command.

    chg-ctrl-feat:partnum=893018401:status=on

    When the chg-crtl-feat command has successfully completed, this message should appear. 

    rlghncxa03w 07-05-28 21:15:37 GMT EAGLE5 37.0.0
CHG-CTRL-FEAT: MASP B - COMPLTD
  8. Verify the changes by entering the rtrv-ctrl-featcommand with the Large MSU Support for IP Signaling feature part number. Enter this command.

    rtrv-ctrl-feat:partnum=893018401

    The following is an example of the possible output. 

    rlghncxa03w 10-04-28 21:15:37 GMT EAGLE5 42.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Large MSU for IP Sig      893018401  on      ----

The following features have been temporarily enabled:

Feature Name              Partnum    Status  Quantity     Trial Period Left
Zero entries found.

The following features have expired temporary keys:

Feature Name              Partnum
Zero entries found.
  9. Back up the new changes using the chg-db:action=backup:dest=fixed command. These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-8 Activate the Large MSU Support for IP Signaling Feature - Sheet 1 of 4

Figure 3-9 Activate the Large MSU Support for IP Signaling Feature - Sheet 2 of 4

Figure 3-10 Activate the Large MSU Support for IP Signaling Feature - Sheet 3 of 4

Figure 3-11 Activate the Large MSU Support for IP Signaling Feature - Sheet 4 of 4

3.10 Removing IETF M2PA Components

This section describes how to remove the following components from the database.

3.11 Removing an IPLIMx Card

Use this procedure to remove an IPLIMx card, a card running the iplim or iplimi applications from the database using the dlt-card command.

The card cannot be removed if it does not exist in the database. Prior to removing the card from the database, the signaling links assigned to the card must be removed.

Caution:

If the IPGWx card is the last IP card in service, removing this card from the database will cause traffic to be lost.
  1. Display the cards in the database using the rtrv-card command.

    This is an example of the possible output. 

    rlghncxa03w 13-06-15 16:34:56 GMT EAGLE5 45.0.0
CARD   TYPE      APPL      LSET NAME     LINK SLC LSET NAME     LINK SLC
1101   DSM       VSCCP     
1102   TSM       GLS          
1113   E5MCAP    OAMHC
1114   E5TDM-A
1115   E5MCAP    OAMHC
1116   E5TDM-B
1117   E5MDAL
1201   LIMDS0    SS7ANSI   lsn1          A    0   lsn2          B    1
1203   LIMDS0    SS7ANSI   lsn2          A    0   lsn1          B    1
1204   LIMATM    ATMANSI   atmgwy        A    0   
1205   DCM       IPLIM     ipnode1       A    0   ipnode3       B    1
1207   DCM       IPLIM     ipnode2       A    0   
1303   DCM       IPLIM     ipnode1       A    0   ipnode3       B    1
1305   DCM       IPLIM     ipnode4       A    0

    Select a card whose application is either IPLIM or IPLIMI.

    Perform the Removing an IPLIMx Signaling Link procedure in this chapter to remove all the signaling links assigned to the card, shown in the LINK column of the rtrv-card output.

    The card location is shown in the CARD field of the rtrv-card command output. No entries in the LSET NAME, LINK, and SLC columns mean that no signaling link is assigned to the card.

  2. Remove the card from the database using the dlt-card command.
    The dlt-card command has only one parameter, loc, which is the location of the card. For this example, enter these commands.

    dlt-card:loc=1205

    dlt-card:loc=1207

    When these commands have successfully completed, this message appears. 

    
rlghncxa03w 06-10-12 09:12:36 GMT EAGLE5 36.0.0
DLT-CARD: MASP A - COMPLTD
  3. Verify the changes using the rtrv-card command and specifying the card that was removed in 2.
    For this example, enter these commands.

    rtrv-card:loc=1205

    rtrv-card:loc=1207

    When these commands have successfully completed, this message appears. 

    
E2144 Cmd Rej: Location invalid for hardware configuration
  4. Back up the new changes using the chg-db:action=backup:dest=fixed command.
    These messages appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-12 Removing an IPLIMx Card



3.12 Removing an IPLIMx Signaling Link

This procedure is used to remove an IPLIMx signaling link from the database using the dlt-slk command. The dlt-slk command uses these parameters.

:loc – The card location of the IPLIMx card that the IP signaling link is assigned to.

:link – The signaling link on the card specified in the loc parameter.

:force – This parameter must be used to remove the last link in a linkset without having to remove all of the routes that referenced the linkset.

The tfatcabmlq parameter (TFA/TCA Broadcast Minimum Link Quantity), assigned to linksets, shows the minimum number of links in the given linkset (or in the combined link set in which it resides) that must be available for traffic. When the number of signaling links in the specified linkset is equal to or greater than the value of the tfatcabmlq parameter, the status of the routes that use the specified linkset is set to allowed and can carry traffic. Otherwise, these routes are restricted. The value of the tfatcabmlq parameter cannot exceed the total number of signaling links contained in the linkset.

If the linkset type of the linkset that contains the signaling link that is being removed is either A, B, D, E, or PRX, the signaling link can be removed regardless of the tfatcabmlq parameter value of the linkset and regardless of the LSRESTRICT option value. When a signaling link in one of these types of linksets is removed, the tfatcabmlq parameter value of the linkset is decreased automatically.

If the linkset type of the linkset that contains the signaling link that is being removed is C, the signaling link can be removed only:
  • If the LSRESTRICT option is off. The LSRESTRICT option value is shown in the rtrv-ss7opts output.
  • If the LSRESTRICT option is on and the number of signaling links assigned to the linkset will be equal to or greater than the value of the tfatcabmlq parameter value of the linkset after the signaling link is removed.

    The tfatcabmlq parameter value of the linkset is shown in the TFATCABMLQ column of the rtrv-ls:lsn=<linkset name> output. The tfatcabmlq parameter value can be a fixed value (1 to 16) or 0. If the tfatcabmlq parameter value of the linkset is a fixed value, the number of signaling links that are in the linkset after the signaling link is removed must be equal to or greater than the tfatcabmlq parameter value of the linkset.

    If the tfatcabmlq parameter value is 0, the signaling link can be removed. When the tfatcabmlq parameter value is 0, the value displayed in the TFATCABMLQ column of the rtrv-ls output is 1/2 of the number of signaling links contained in the linkset. If the number of signaling links in the linkset is an odd number, the tfatcabmlq parameter value is rounded up to the next whole number. As the signaling links are removed, the tfatcabmlq parameter value of the linkset is decreased automatically.

Canceling the RTRV-SLK Command

Because the rtrv-slk command used in this procedure can output information for a long period of time, the rtrv-slk command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-slk command can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-slk command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-slk command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-slk command was entered, from another terminal other that the terminal where the rtrv-slk command was entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

  1. Display the current link configuration using the rtrv-slk command.

    This is an example of the possible output. 

    
rlghncxa03w 09-07-19 21:16:37 GMT EAGLE5 41.1.0
                                    L2T              PCR  PCR
LOC   LINK LSN          SLC TYPE    SET BPS    ECM   N1   N2
1201  A    ls01          0  LIMDS0  1   56000  BASIC ---  -----
1201  B    lsa1          0  LIMDS0  1   56000  BASIC ---  -----
1203  A    ls03          0  LIMDS0  3   56000  BASIC ---  -----
1203  B    lsa2          0  LIMDS0  1   56000  BASIC ---  -----
1204  B    ls01          1  LIMDS0  1   56000  BASIC ---  -----
1207  A    lsn1207a      0  LIMDS0  1   56000  BASIC ---  -----
1207  B    lsn1207b      0  LIMDS0  1   56000  BASIC ---  -----
1208  B    ls03          1  LIMDS0  3   56000  BASIC ---  -----
1213  B    ls05          0  LIMDS0  5   56000  BASIC ---  -----
1215  A    ls05          1  LIMDS0  5   56000  BASIC ---  -----
1311  A    ls01          2  LIMDS0  1   56000  BASIC ---  -----
1311  A1   ls05          2  LIMDS0  5   56000  BASIC ---  -----
1311  B    ls03          2  LIMDS0  3   56000  BASIC ---  -----
1311  B1   ls07          1  LIMDS0  7   56000  BASIC ---  -----
1313  A    ls07          0  LIMDS0  7   56000  BASIC ---  -----

                                    LP           ATM
LOC   LINK LSN          SLC TYPE    SET BPS      TSEL      VCI  VPI   LL
1302  A    atmansi0      0  LIMATM  3   1544000  EXTERNAL  35   15    0
1305  A    atmansi1      0  LIMATM  4   1544000  INTERNAL  100  20    2
1318  A    atmansi0      1  LIMATM  9   1544000  LINE      150  25    4

                                   LP         ATM                    E1ATM
LOC  LINK LSN         SLC TYPE     SET BPS    TSEL     VCI   VPI  CRC4 SI SN
2101 A    atmitu1      0  LIME1ATM 5   2.048M LINE     150   2    ON   1  20
2105 A    atmitu1      1  LIME1ATM 5   2.048M LINE     35    15   ON   2  15

LOC  LINK LSN         SLC TYPE     IPLIML2
2202 A    lsnlp1       0  IPLIM    M2PA
2205 A    lsnip1       0  IPLIM    M2PA
2204 B    lsnlp2       0  IPLIM    M2PA
2213 A    lsnip5       0  IPLIMI   M2PA
2215 A    lsnlp2       1  IPLIM    M2PA

LOC  LINK LSN         SLC TYPE
2207  A    lsnlp3      0  SS7IPGW
2211  A    lsnlp4      0  IPGWI

SLK table is (27 of 1200) 2% full
  2. Display the linkset that contains the signaling link that is being removed by entering the rtrv-ls command with the name of the linkset shown in the LSN column of the rtrv-slk output.

    For this example, enter these commands.

    rtrv-ls:lsn=lsnip1

    This is an example of the possible output. 

    
rlghncxa03w 10-07-17 11:43:04 GMT EAGLE5 42.0.0

                                 L3T SLT              GWS GWS GWS
LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsnip1        002-009-003   scr2 1   1   no  a   1    on  off on  no    off

              SPCA          CLLI         TFATCABMLQ MTPRSE ASL8
           ---------------- -----------  1          no     no
       
           RANDSLS
           off

           ISLSRSB RSLS8
           1       no

           IPSG  IPGWAPC  GTTMODE           CGGTMOD
           no    no       CdPA               no

           LOC  LINK SLC TYPE     IPLIML2
           2205 A    0   IPLIM    M2PA

Link set table is ( 20 of 1024)  2% full

    rtrv-ls:lsn=lsnlp2

    This is an example of the possible output. 

    
rlghncxa03w 10-07-17 11:43:04 GMT EAGLE5 42.0.0

                                 L3T SLT              GWS GWS GWS
LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsnlp2        002-009-003   scr2 1   1   no  a   2    on  off on  no    off

              SPCA          CLLI         TFATCABMLQ MTPRSE ASL8
           ---------------- -----------  1          no     no
       
           RANDSLS
           off

           ISLSRSB RSLS8
           1       no

           IPSG  IPGWAPC  GTTMODE           CGGTMOD
           no    no       CdPA               no

           LOC  LINK SLC TYPE     IPLIML2
           2204 B    0   IPLIM    M2PA
           2215 A    1   IPLIM    M2PA

Link set table is ( 20 of 1024)  2% full

    If the linkset type of the linkset is A, B, D, E, or PRX, continue the procedure with 5.

    If the linkset type of the linkset is C, continue the procedure with 3.

  3. Display the LSRESTRICT option value by entering the rtrv-ss7opts command.

    This is an example of the possible output. 

    
rlghncxa03w 10-07-30 15:09:00 GMT  42.0.0

SS7 OPTIONS
-----------------------
LSRESTRICT     on

    Note:

    Thertrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-feat command, refer to the rtrv-feat command description in Commands User's Guide.

    The signaling link cannot be removed, if the LSRESTRICT option is on and the number of signaling links assigned to the linkset will be less than the value of the tfatcabmlq parameter value of the linkset if the signaling link is removed.

    If the LSRESTRICT option is on and the number of signaling links assigned to the linkset will be equal to or greater than the value of the tfatcabmlq parameter value of the linkset if the signaling link is removed, continue the procedure with 5.

    If the LSRESTRICT option is on and the number of signaling links assigned to the linkset will be less than the value of the tfatcabmlq parameter value of the linkset if the signaling link is removed, the signaling link cannot be removed unless the tfatcabmlq parameter value of the linkset is changed to 0. Continue the procedure with 4.

    If the LSRESTRICT value is off, continue the procedure with 5.

  4. Change the tfatcabmlq parameter value of the linkset to 0 by entering the chg-ls command with the name of the linkset that contains the signaling link that is being removed and the tfatcabmlq parameters. For this example, enter this command.

    chg-ls:lsn=ls17:tfatcabmlq=0

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 10-07-07 08:41:12 GMT  EAGLE5 42.0.0

Link set table is (20 of 1024) 2% full.

CHG-LS: MASP A - COMPLTD
  5. Display the IP link associated with the card that the signaling link being removed the database is assigned to.
    Enter the rtrv-ip-lnk command with the card location of the signaling link being removed shown in 1. For this example, enter these commands.

    rtrv-ip-lnk:loc=2205

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:14:37 GMT EAGLE5 36.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
2205  A    192.3.1.10      255.255.255.128 HALF    10    802.3   NO   NO
2205  B    --------------- --------------- HALF    10    DIX     NO   NO

    rtrv-ip-lnk:loc=2204

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:14:37 GMT EAGLE5 36.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
2204  A    192.1.1.10      255.255.255.128 HALF    10    802.3   NO   NO
2204  B    --------------- --------------- HALF    10    DIX     NO   NO
  6. Display the IP host information associated with the IP link by entering the rtrv-ip-host command with the IP address shown in 5.
    For this example, enter these commands.

    rtrv-ip-host:ipaddr=192.001.001.010

    The following is an example of the possible output. 

    
rlghncxa03w 08-12-28 21:17:37 GMT EAGLE5 40.0.0

LOCAL IPADDR    LOCAL HOST
192.1.1.10      IPNODE1_2204

IP Host table is (11 of 4096) .26% full

    rtrv-ip-host:ipaddr=192.003.001.010

    The following is an example of the possible output. 

    
rlghncxa03w 08-12-28 21:17:37 GMT EAGLE5 40.0.0

LOCAL IPADDR    LOCAL HOST
192.3.1.10      IPNODE1_2205

IP Host table is (11 of 4096) .26% full
  7. Display the association associated with the local host name shown in 6 by entering the rtrv-assoc command.
    For this example, enter this command.

    rtrv-assoc:lhost=ipnode1_2204

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
assoc1          2204 A     A    M2PA    1030  1030  YES  YES

IP Appl Sock/Assoc table is (4 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 3200 KB) on LOC = 2204

    rtrv-assoc:lhost=ipnode1_2205

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

IP Appl Sock/Assoc table is (4 of 4000) 1% full

    Note:

    If there are no associations assigned to the specified local host name, thertrv-assoc output shows no association information as shown above.
  8. Change the value of the open and alw parameters to no by specifying the chg-assoc command with the open=no and alw=no parameters, as necessary.

    Note:

    If there is no association shown in 7, or the open and alw parameter values of the association shown in7 are no, continue the procedure with 9.

    For this example, enter this command.

    chg-assoc:aname=assoc1:open=no:alw=no

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
  9. Deactivate the link to be removed using the dact-slk command, using the output from 1 to obtain the card location and link parameter value of the signaling link to be removed.
    For this example, enter these commands.

    dact-slk:loc=2205:link=a

    dact-slk:loc=2204:link=a

    When each of these command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-07 08:41:12 GMT  EAGLE5 36.0.0
Deactivate Link message sent to card
  10. Verify that the link is out of service - maintenance disabled (OOS-MT-DSBLD) using the rept-stat-slk command with the card location and link parameter values specified in 9.
    For this example, enter these commands.

    rept-stat-slk:loc=2205:link=a

    This is an example of the possible output. 

    
rlghncxa03w 06-10-23 13:06:25 GMT EAGLE5 36.0.0
SLK      LSN       CLLI        PST          SST       AST
2205,A   ls05      ls05clli    OOS-MT_DSBLD Unavail   ----
  ALARM STATUS       = *   0235 REPT-LNK-MGTINH: local inhibited
  UNAVAIL REASON     = LI

    rept-stat-slk:loc=2204:link=a

    This is an example of the possible output. 

    
rlghncxa03w 06-10-23 13:06:25 GMT EAGLE5 36.0.0
SLK      LSN       CLLI        PST          SST       AST
2204,A   ls04      ls04clli    OOS-MT       Unavail   ----
  ALARM STATUS       = *   0235 REPT-LNK-MGTINH: local inhibited
  UNAVAIL REASON     = LI
  11. If the signaling link to be removed is the last signaling link on a card, the card must be inhibited before the signaling link is removed.

    Note:

    If the signaling link being removed is not the last signaling link on the card, continue the procedure with 13.

    Before entering the dlt-slk command, enter the rmv-card command and specify the location of the card to be inhibited. The card location is shown in the output of rept-stat-slk command executed in 10.

    In the example used for this procedure, the signaling link is the last signaling link on the card and must be inhibited. Enter these commands.

    rmv-card:loc=2205

    rmv-card:loc=2204

    When each of these command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-07 08:41:12 GMT  EAGLE5 36.0.0
Card has been inhibited.
  12. Verify that the card has been inhibited by entering the rept-stat-card command with the card location specified in 11. For this example, enter these commands.

    rept-stat-card:loc=2205

    This is an example of the possible output. 

    rlghncxa03w 07-05-27 16:43:42 GMT EAGLE5 37.0.0
CARD   VERSION      TYPE      GPL        PST            SST        AST
2205   114-001-000  DCM       IPLIM      OOS-MT-DSBLD   Isolated   -----
  ALARM STATUS        = **  0013 Card is isolated from the system
  BPDCM GPL           = 002-102-000
  IMT BUS A           = Disc
  IMT BUS B           = Disc
  SIGNALING LINK STATUS
      SLK    PST                LS            CLLI          E5IS
      A      OOS-MT             lsnlp1        -----------   INACTIVE

Command Completed.

    rept-stat-card:loc=2204

    This is an example of the possible output. 

    rlghncxa03w 07-05-27 16:43:42 GMT EAGLE5 37.0.0
CARD   VERSION      TYPE      GPL        PST            SST        AST
2204   114-001-000  DCM       IPLIM      OOS-MT-DSBLD   Isolated   -----
  ALARM STATUS        = **  0013 Card is isolated from the system
  BPDCM GPL           = 002-102-000
  IMT BUS A           = Disc
  IMT BUS B           = Disc
  SIGNALING LINK STATUS
      SLK    PST                LS            CLLI          E5IS
      A      OOS-MT             lsnlp2        -----------   INACTIVE

Command Completed.
  13. Remove the signaling link from the EAGLE using the dlt-slk command.
    If there is only one signaling link in the linkset, the force=yes parameter must be specified to remove the signaling link.

    In the example used in this procedure, the signaling link is the last signaling link in the linkset. Enter these commands.

    dlt-slk:loc=2205:link=a:force=yes

    dlt-slk:loc=2204:link=a:force=yes

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-07 08:41:17 GMT  EAGLE5 36.0.0
DLT-SLK: MASP A - COMPLTD

    Note:

    If removing the signaling link will result in 700 or less signaling links in the database and the OAMHCMEAS value in the rtrv-measopts output is on, the scheduled UI measurement reports will be enabled.
  14. Verify the changes using the rtrv-slk command with the card location and link values specified in 13. For this example, enter these commands.

    rtrv-slk:loc=2205:link=a

    rtrv-slk:loc=2204:link=a

    When the rtrv-slk command has completed, the specified signaling link is not shown in the rtrv-slk output, as shown in this example. 

    
    rlghncxa03w 09-09-18 13:43:31 GMT EAGLE5 41.1.0
E2373 Cmd Rej: Link is unequipped in the database
  15. Back up the new changes using the chg-db:action=backup:dest=fixed command. These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-13 Removing an IPLIMx Signaling Link



Sheet 1 of 2



Sheet 2 of 2

3.13 Removing an IP Host Assigned to an IPLIMx Card

This procedure removes an IP host that is assigned to an IPLIMx card using the dlt-ip-host command.

The dlt-ip-host command uses the following parameter.

:host– Hostname. The hostname to be removed. This parameter identifies the logical name assigned to a device with an IP address.

No associations can reference the host name being removed in this procedure.

The associations referencing the host name can be removed by performing the Removing an M2PA Association procedure or the host name in these associations can be changed by performing the Changing the Host Values of a M2PA Association procedure. The host name assigned to associations is displayed in the rtrv-assoc outputs.

  1. Display the current IP host information in the database by entering the rtrv-ip-host:display=all command.

    The following is an example of the possible output. 

    
rlghncxa03w 08-12-28 21:17:37 GMT EAGLE5 40.0.0

LOCAL IPADDR    LOCAL HOST
192.1.1.10      IPNODE1-1201
192.1.1.12      IPNODE1-1203
192.1.1.14      IPNODE1-1205
192.1.1.20      IPNODE2-1201
192.1.1.22      IPNODE2-1203
192.1.1.24      IPNODE2-1205
192.1.1.30      KC-HLR1
192.1.1.32      KC-HLR2
192.1.1.50      DN-MSC1
192.1.1.52      DN-MSC2
192.3.3.33      GW100. NC. TEKELEC. COM

REMOTE IPADDR   REMOTE HOST
150.1.1.5       NCDEPTECONOMIC_DEVELOPMENT. SOUTHEASTERN_COORIDOR_ASHVL. GOV

IP Host table is (12 of 4096) .29% full

    If the IP host that is being removed is a remote host, continue the procedure with 5.

    If the IP host that is being removed is a local host, continue the procedure with 2.

  2. Display the current link parameters associated with the IP card in the database by entering the rtrv-ip-lnk command. The following is an example of the possible output.
    
rlghncxa03w 08-12-28 21:14:37 GMT EAGLE5 40.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
1303  A    192.1.1.10      255.255.255.128 HALF    10    802.3   NO   NO
1303  B    --------------- --------------- HALF    10    DIX     NO   NO
1305  A    192.1.1.12      255.255.255.0   ----    ---   DIX     YES  NO
1305  B    --------------- --------------- HALF    10    DIX     NO   NO
1313  A    192.1.1.14      255.255.255.0   FULL    100   DIX     NO   NO
1313  B    --------------- --------------- HALF    10    DIX     NO   NO
2101  A    192.1.1.20      255.255.255.0   FULL    100   DIX     NO   NO
2101  B    --------------- --------------- HALF    10    DIX     NO   NO
2103  A    192.1.1.22      255.255.255.0   FULL    100   DIX     NO   NO
2103  B    --------------- --------------- HALF    10    DIX     NO   NO
2105  A    192.1.1.24      255.255.255.0   FULL    100   DIX     NO   NO
2105  B    --------------- --------------- HALF    10    DIX     NO   NO
2205  A    192.1.1.30      255.255.255.0   FULL    100   DIX     NO   NO
2205  B    --------------- --------------- HALF    10    DIX     NO   NO
2207  A    192.1.1.32      255.255.255.0   FULL    100   DIX     NO   NO
2207  B    --------------- --------------- HALF    10    DIX     NO   NO
2213  A    192.1.1.50      255.255.255.0   FULL    100   DIX     NO   NO
2213  B    --------------- --------------- HALF    10    DIX     NO   NO
2301  A    192.1.1.52      255.255.255.0   FULL    100   DIX     NO   NO
2301  B    --------------- --------------- HALF    10    DIX     NO   NO
2305  A    192.3.3.33      255.255.255.0   FULL    100   DIX     NO   NO
2305  B    --------------- --------------- HALF    10    DIX     NO   NO

IP-LNK   table is (22 of 2048) 1% full.
  3. Display the cards in the database using the rtrv-card command. This is an example of the possible output.
    rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
CARD   TYPE      APPL      LSET NAME     LINK SLC LSET NAME     LINK SLC
1101   DSM       VSCCP     
1102   TSM       GLS       
1113   E5MCAP    EOAM
1114   E5TDM-A
1115   E5MCAP    EOAM
1116   E5TDM-B
1117   E5MDAL
1201   LIMDS0    SS7ANSI   sp2           A    0   sp1           B    0
1203   LIMDS0    SS7ANSI   sp3           A    0   
1204   LIMDS0    SS7ANSI   sp3           A    1   
1206   LIMDS0    SS7ANSI   nsp3          A    1   nsp4          B    1    
1301   LIMDS0    SS7ANSI   sp6           A    1   sp7           B    0
1302   LIMDS0    SS7ANSI   sp7           A    1   sp5           B    1
1303   DCM       IPLIM     ipnode1       A    0   ipnode3       B    1
1305   DCM       IPLIM     ipnode4       A    0       
1313   DCM       SS7IPGW   ipgtwy1       A    0   
2101   DCM       SS7IPGW   ipgtwy2       A    0   
2103   DCM       SS7IPGW   ipgtwy3       A    0   
2105   DCM       IPLIM     ipnode1       A1   1   ipnode5       B    2   
2205   DCM       IPLIM     ipnode3       A2   0   ipnode6       B1   2   
2207   DCM       IPLIM     ipnode5       A    0   ipnode4       B3   1   
2213   DCM       IPLIM     ipnode5       A3   1   ipnode3       B2   2   
2301   DCM       IPLIM     ipnode6       A    0   ipnode1       B    2   
2305   DCM       IPLIM     ipnode6       A1   1   ipnode1       B1   3

    Select an IP host whose IP address is assigned to a card running the IPLIM or IPLIMI application.

  4. Display the associations referencing the host name being removed in this procedure by entering the rtrv-assoc command with the local host name.

    For this example, enter this command.

    rtrv-assoc:lhost=gw100.nc.tekelec.com

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:14:37 GMT EAGLE5 36.0.0
                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
a2              2305 A     A    M2PA    7205  7001  NO   NO

IP Appl Sock/Assoc table is (4 of 4000) 1% full
Assoc Buffer Space Used (200 KB of 1600 KB) on LOC = 2305

    If no associations referencing the host name being removed in this procedure are shown in this step, continue the procedure with 5.

    Any associations referencing the host name must either be removed or the host name assigned to the association must be changed.

    To remove the associations, perform the Removing an M2PA Association procedure.

    Continue the procedure with 5 after the associations have been removed.

    To change the host name assigned to the associations, perform the Changing the Host Values of a M2PA Association procedure.

    Continue the procedure with 5 after the host name assigned to the associations have been changed.

  5. Delete IP host information from the database by entering the dlt-ip-host command.

    For example, enter this command.

    dlt-ip-host:host=gw100.nc.tekelec.com

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 06-10-28 21:19:37 GMT EAGLE5 36.0.0
DLT-IP-HOST: MASP A - COMPLTD
  6. Verify the changes by entering the rtrv-ip-host command with the host name specified in 5.

    For this example, enter this command.

    rtrv-ip-host:host=gw100.nc.tekelec.com

    The following is an example of the possible output. 

    
rlghncxa03w 09-07-28 21:20:37 GMT EAGLE5 41.1.0

No matching entries found.

IP Host table is (10 of 4096) .24% full
  7. Back up the new changes using the chg-db:action=backup:dest=fixed command.
    These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-14 Removing an IP Host Assigned to an IPLIMx Card



3.14 Removing an IP Route

This procedure is used to remove an IP route from the database using the dlt-ip-rte command.

The dlt-ip-rte command uses these parameters.

:loc – The location of the IP card containing the IP route being removed.

:dest – The IP address of the remote host or network assigned to the IP route being removed.

:force – To remove the IP route, the IP card that the route is assigned to must be out of service, or the force=yes parameter must be specified with the dlt-ip-rte command. The force=yes parameter allows the IP route to be removed if the IP card is in service.

Caution:

Removing an IP route while the IP card is still in service can result in losing the ability to route outbound IP traffic on the IP card. This can cause both TCP and SCTP sessions on the IP card to be lost.
  1. Display the IP routes in the database with the rtrv-ip-rte command.
    This is an example of the possible output. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
LOC   DEST             SUBMASK          GTWY
1212  132.10.175.20    255.255.0.0      150.1.1.50
1301  128.252.10.5     255.255.255.255  140.188.13.33
1301  128.252.0.0      255.255.0.0      140.188.13.34
1301  150.10.1.1       255.255.255.255  140.190.15.3
1303  192.168.10.1     255.255.255.255  150.190.15.23
1303  192.168.0.0      255.255.255.0    150.190.15.24

IP Route table is  (6 of 2048) 0.29% full
  2. Verify the state of the IP card containing the IP route being removed by entering the rept-stat-card command and specifying the card location of the IP card.
    The IP card should be in the out-of-service maintenance-disabled (OOS-MT-DSBLD) in order to remove the IP route. If the IP card’s state is out-of-service maintenance-disabled, the entry OOS-MT-DSBLD is shown in the PST column of the rept-stat-card output. For this example, enter this command.

    rept-stat-card:loc=1301

    This is an example of the possible output. 

    
rlghncxa03w 06-10-27 17:00:36 GMT EAGLE5 36.0.0
CARD  VERSION      TYPE    GPL       PST           SST       AST
1301  114-000-000  DCM     IPLIM     IS-NR         Active    -----
  ALARM STATUS      = No Alarms.
  BPDCM GPL         = 002-102-000
  IMT BUS A         = Conn
  IMT BUS B         = Conn
  SIGNALING LINK STATUS
      SLK    PST                LS            CLLI
      A      IS-NR              nc001         -----------

Command Completed.

    Note:

    If the output of 2 shows that the IP card’s state is not OOS-MT-DSBLD, and you do not wish to change the state of the IP card, continue the procedure with 4.
  3. Change the IP card’s state to OOS-MT-DSBLD using the inh-card command and specifying the card location of the IP card.
    For this example, enter these commands.

    inh-card:loc=1301

    When this command has successfully completed, this message appears. 

    
rlghncxa03w 06-10-12 09:12:36 GMT EAGLE5 36.0.0
Card has been inhibited.
  4. Remove the IP route from the database using the dlt-ip-rte command.
    If the state of the IP card is not OOS-MT-DSBLD, the force=yes parameter must be specified with the dlt-ip-rte command. For this example, enter this command.

    dlt-ip-rte:loc=1301:dest=128.252.0.0

    Caution:

    Removing an IP route while the IP card is still in service can result in losing the ability to route outbound IP traffic on the IP card. This can cause both TCP and SCTP sessions on the IP card to be lost.

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-12 09:12:36 GMT EAGLE5 36.0.0
DLT-IP-RTE: MASP A - COMPLTD
  5. Verify the changes using the rtrv-ip-rte command.
    This is an example of the possible output. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
LOC   DEST             SUBMASK          GTWY
1212  132.10.175.20    255.255.0.0      150.1.1.50
1301  128.252.10.5     255.255.255.255  140.188.13.33
1301  150.10.1.1       255.255.255.255  140.190.15.3
1303  192.168.10.1     255.255.255.255  150.190.15.23
1303  192.168.0.0      255.255.0.0      150.190.15.24

IP Route table is  (5 of 2048) 0.24% full
  6. Place the IP card back into service by using the alw-card command.

    Note:

    If the IP card containing the IP route that was removed from the database does not contain other IP routes, continue the procedure with 7.

    For example, enter this command.

    alw-card:loc=1301

    This message should appear. 

    
rlghncxa03w 06-10-28 21:22:37 GMT EAGLE5 36.0.0
Card has been allowed.
  7. Back up the new changes using the chg-db:action=backup:dest=fixed command.
    These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-15 Removing an IP Route



3.15 Removing an M2PA Association

This procedure is used to remove an association from the database using the dlt-assoc command.

The dlt-assoc command uses one parameter, aname, the name of the association being removed from the database. The association being removed must be in the database.

The open parameter must be set to no before the association can be removed. Use the chg-assoc command to change the value of the open parameter.

The adapter value assigned to the association being removed in this procedure must be m2pa.The application assigned to the card that is hosting the M2PA association must be either IPLIM or IPLIMI. Perform the Removing an IPSG Association procedure to remove an M2PA association assigned to an IPSG card.

Canceling the RTRV-ASSOC Command

Because the rtrv-assoc command used in this procedure can output information for a long period of time, the rtrv-assoc command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-assoc command can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-assoc command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-assoc command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-assoc command was entered, from another terminal other that the terminal where the rtrv-assoc command was entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

  1. Display the associations in the database using the rtrv-assoc command.

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
swbel32         1201 A     A    M3UA    1030  2345  YES  YES
a2              1305 A     A    SUA     1030  2345  YES  YES
a3              1307 A     A    SUA     1030  2346  YES  YES
assoc1          1203 A     A1   M2PA    2048  1030  NO   NO
  2. Enter the rtrv-card command with the location of the card that is hosting the M2PA association that will be removed in this procedure. For this example, enter this command.

    rtrv-card:loc=1203

    This is an example of possible output. 

    
rlghncxa03w 08-03-06 15:17:20 EST EAGLE5 38.0.0
CARD   TYPE      APPL     LSET NAME   LINK SLC LSET NAME   LINK SLC
1203   DCM       IPLIM    lsn1        A1   0

    If the application assigned to the card is IPLIM or IPLIMI, shown in the APPL column, continue the procedure with 3.

    If the application assigned to the card is IPSG, perform the Removing an IPSG Association procedure.

  3. Change the value of the open parameter to no by specifying the chg-assoc command with the open=no parameter.

    Note:

    If the value of theopen parameter for the association being removed from the database (shown in1) isno, continue this procedure with4.

    For this example, enter this command.

    chg-assoc:aname=assoc1:open=no

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
  4. Remove the association from the database using the dlt-assoc command.

    For this example, enter this command.

    dlt-assoc:aname=assoc1

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
DLT-ASSOC:  MASP A - COMPLTD
  5. Verify the changes using the rtrv-assoc command with the name of the association specified in 4.

    For this example, enter this command.

    rtrv-assoc:aname=assoc1

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

No matching entries found

IP Appl Sock table is (3 of 4000) 1% full
  6. Back up the new changes, using the chg-db:action=backup:dest=fixed command. These messages should appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-16 Removing an M2PA Association



3.16 Changing IETF M2PA Components

This section describes how to change the attributes of the following components in the database.

3.17 Changing the Attributes of an M2PA Association

This procedure is used to change the values of the attributes of an M2PA association, assigned to cards that are running the IPLIM or IPLIMI applications, using the chg-assoc command and the following parameters.

Table 3-7 Change M2PA Association Parameters

aname lport rhost rport open alw
rmode rmin rmax rtimes cwmin istrms
ostrms m2patset ver rtxthr rhosttype rhostval

An M2PA association that is assigned to an IPLIMx signaling link can contain a UA parameter set value (the uaps parameter). While the uaps parameter value can be changed with the chg-assoc command, the uaps parameter value has no impact on the traffic carried by an M2PA association that is assigned to an IPLIMx signaling link.The uaps parameter value impacts M3UA or SUA associations that are assigned to IPGWx signaling links and M2PA and M3UA associations that are assigned to IPSG cards. The uaps parameter value is shown in the UAPS field in the rtrv-assoc output for an M2PA associations that is assigned to an IPLIMx signaling link.

If you wish to change the attributes of M2PA associations assigned to cards that are running the IPSG application, perform Changing the Attributes of an IPSG Association.

The chg-assoc command contains other parameters that are not used in this procedure. To change these parameters, perform these procedures.

:aname – The name assigned to the association, shown in the rtrv-assoc output.

:lport – The SCTP port number for the local host.

:rhost – The host name for the remote host, rhost can be any string of characters starting with a letter and comprising these characters ['a'..'z', 'A'..'Z', '0'..'9', '-', '.']. Hostnames are not case-sensitive and can contain up to 60 characters. The default value of this optional parameter is empty (null string).

:rport – The SCTP port number for the remote host.

:open – The connection state for this association. Valid values are yes or no. When the open=yes parameter is specified, the connection manager opens the association if the association is operational. When the open=no parameter is specified, the connection manager will not open the association.

:alw – The connection state for this association. Valid values are yes or no. When the alw=yes parameter is specified, the connection manager allows the association to carry SS7 traffic. When the alw=no parameter is specified, the connection manager prohibits the association from carrying SS7 traffic.

:rmode – The retransmission policy used when packet loss is detected. The values are rfc or lin.

  • rfc – Standard RFC 2960 algorithm in the retransmission delay doubles after each retransmission. The RFC 2960 standard for congestion control is also used.
  • lin – Oracle's linear retransmission policy where each retransmission timeout value is the same as the initial transmission timeout and only the slow start algorithm is used for congestion control.

:rmin – The minimum value of the calculated retransmission timeout in milliseconds, from 10 - 1000.

:rmax – The maximum value of the calculated retransmission timeout in milliseconds, from 10 - 1000.

:rtimes – The number of times a data retransmission will occur before closing the association from 3 - 12.

:cwmin – The minimum size in bytes of the association's congestion window and the initial size in bytes of the congestion window, from 1500 - 409600. The cwmin parameter value must be less than or equal to the size of the buffer used by the association, shown by the bufsize parameter value. If the buffer size for the association needs to be changed, perform Changing the Buffer Size of a M2PA Association.

The rmode, rmin, rmax, rtimes, and cwmin parameters are used to configure the SCTP retransmission controls for an association, in addition to other commands. Perform Configuring SCTP Retransmission Control for a M2PA Association to configure the SCTP retransmission controls for an association.

:istrms – The number of inbound streams (1 or 2) advertised by the SCTP layer for the association.

:ostrms – The number of outbound streams (1 or 2) advertised by the SCTP layer for the association.

:m2patset – The M2PA timer set assigned to the association. The m2patset parameter can be specified only with the adapter=m2pa parameter, or if the association already has the adapter=m2pa parameter assigned and the adapter parameter value is not being changed. If the adapter parameter value is being changed to m2pa, and the m2patset parameter is not specified, the default value for the m2patset parameter (1 - M2PA timer set 1) is assigned to the association. If the adapter parameter value for the association is m2pa, is not being changed, and the m2patset parameter is not specified with the chg-assoc command, the m2patset parameter value is not changed.

:ver – The M2PA version assigned to the M2PA association, either the RFC version (ver=rfc), or the Draft 6 version (ver=d6). The ver parameter can be specified only if, when this procedure is completed, the adapter parameter value is m2pa. If the adapter parameter value is being changed to m2pa, and the ver parameter is not specified, the default M2PA version of RFC is assigned to the association. To change the ver parameter value, the open parameter value for the association must be no.

:rtxthr –The retransmission threshold for the association. The RTXTHR parameter value indicates the number of packet re-transmissions that can occur on the association (per monitoring time period of 2 seconds). Alarm "IP Connection Excess Retransmits" (UAM 536) will be raised if the number of packets re-transmitted is greater than the configured RTXTHR parameter value, during 5 such consecutive monitoring periods. Once alarm is raised, it may require up to 12 consecutive monitoring periods with the number of re-transmissions < RTXTHR to clear the alarm. The design allows the alarm to come on at low error rates, and not come for occasional errors.

The value of this parameter is 0 to 65,535. The value of this parameter is shown in the RTXTHR field of the rtrv-assoc:aname=<association name> output. The rtxthr parameter value can be changed if the open parameter value is either "yes" or "no". It is possible to configure the RTXTHR so that UAM 536 alarms if the error rate on association is above the recommended maximum packet loss of 0.025%. If the error rate is more than 0.025%, investigate to determine if this can be improved in the network.

:rhosttype – The type of remote host assigned to the association, primary or alternate. The primary remote host is shown in the RHOST field of the rtrv-assoc:aname=<association name> output. The alternate remote host is shown in the ARHOST field of the rtrv-assoc:aname=<association name> output.

An alternate remote host can be configured for multi-homed associations using the rhost and rhosttype parameters of the chg-assoc command. The rhost parameter value with the rhostype=primary parameter represents an IP address that corresponds to one of the network interfaces at the remote end while the rhost parameter value with the rhostype=alternate parameter represents an IP address that corresponds to the other network interface at the remote end.

:rhostval – The validation mode used for the association when an SCTP INIT/INIT-ACK message is received. The value of this parameter is shown in the RHOSTVAL field of the rtrv-assoc:aname=<association name> output. This parameter has two values.
  • relaxed - accept the message if the IP address for the primary or alternate remote host matches the IP address, source IP address, or the host name in the message.
  • match - accept the message if the message contains the primary remote host value and the alternate remote host value (if the alternate remote host is provisioned). If the alternate remote host is not provisioned, then accept the message if the message contains the primary remote host value. Reject the message if it contains any IP address other than that of the primary or alternate remote host.

    Refer to the chg-assoc command description in Commands User's Guide for more information about this parameter.

If the value of the open parameter is yes, only the value of the alw, and rtxthr parameters can be changed. To change the values of other parameters, the value of the open parameter must be no.

To set the open parameter value to yes, the association specified by the aname parameter must contain values for the lhost, lport, rhost, and rport parameters. The lhost parameter value must have a signaling link assigned to it.

At least one optional parameter is required.

The command input is limited to 150 characters, including the hostnames.

The value of the rmin parameter must be less than or equal to the rmax parameter value.

The ipliml2 parameter value of the signaling link assigned to the association must be m2pa. The adapter parameter value of the association must match the ipliml2 parameter value.

The signaling link being assigned to the association must be out of service. This state is shown in the rept-stat-slk output with the entries OOS-MT in the PST field and Unavail in the SST field.

If the association is being opened in this procedure with the chg-assoc command and the open=yes parameter, the signaling link assigned to the association must be in the database and the ipliml2 parameter value of the signaling link assigned to the association must be m2pa.

Canceling the RTRV-ASSOC Command

Because the rtrv-assoc command used in this procedure can output information for a long period of time, the rtrv-assoc command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-assoc command can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-assoc command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-assoc command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-assoc command was entered, from another terminal other that the terminal where the rtrv-assoc command was entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

  1. Display the associations in the database using the rtrv-assoc command.

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
swbel32         1201 A     A    M3UA    1030  2345  YES  YES
a2              1305 A     A    SUA     1030  2345  YES  YES
a3              1307 A     A    SUA     1030  2346  YES  YES
assoc1          1201 A     A    M3UA    2000  1030  YES  YES
assoc2          1205 A     A    M2PA    2048  2048  YES  YES
assoc3          1205 A     B2   M2PA    3000  3000  YES  YES
assoc5          1205 A     A3   M2PA    1500  3000  YES  YES
  2. Enter the rtrv-card command with the location of the card that is hosting the M2PA association that will be changed in this procedure. For this example, enter this command.

    rtrv-card:loc=1205

    This is an example of possible output. 

    
rlghncxa03w 08-04-06 15:17:20 EST EAGLE5 38.0.0
CARD   TYPE      APPL     LSET NAME   LINK SLC LSET NAME   LINK SLC
1205   DCM       IPLIM    e5e6a       A    0   e5e6a       B2   1
                          e5e6a       A3   2
    If the application assigned to the card is IPLIM or IPLIMI, shown in the APPL column, and the values of any of these parameters are being changed: lport, rhost, rport, rmode, rmin, rmax, rtimes, cwmin, istrms, ostrms, ver, or m2patset, continue the procedure by performing one of these steps.
    • If the open parameter value for the association is yes, continue the procedure with 3.
    • If the open parameter value for the association is no, continue the procedure with 4.
    If the application assigned to the card is IPLIM or IPLIMI, shown in the APPL column, and only the values of the alw, open, rtxthr parameters are being changed, continue the procedure by performing one of these steps.
    • If only the values of the alw parameter is being changed, or the open parameter value is being changed to no, continue the procedure with 9.
    • If the value of the rtxthr parameter is being changed, continue the procedure with 4.
    • If the value of the open parameter value is being changed to yes, a signaling link must be assigned to the card shown in this step. If a signaling links is assigned to the card, entries are shown in the LSET NAME and LINK columns of the rtrv-card output. If a signaling link is assigned to the card, perform one of these actions.
      • If only the alw parameter is being specified with the open=yes parameter, continue the procedure with 9.
      • If the value of the rtxthr parameter is being changed, continue the procedure with 4.
    • If the value of the open parameter value is being changed to yes and a signaling link is not assigned to the card, performAdding an IPLIMx Signaling Link to assign an IPLIMx signaling link to the card. After the signaling link has been added, perform one of these actions.
      • If only the alw parameter is being specified with the open=yes parameter, continue the procedure with 9.
      • If the value of the rtxthr parameter is being changed, continue the procedure with 4.

    If the application assigned to the card is IPSG, perform Changing the Attributes of an IPSG Association.

  3. Change the value of the open parameter to no by specifying the chg-assoc command with the open=no parameter.

    For this example, enter this command.

    chg-assoc:aname=assoc2:open=no

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
  4. Display the association being changed by entering the rtrv-assoc command with the aname parameter specified in 3 or selected in 1.

    For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of the possible output. 

    
rlghncxa03w 10-07-28 21:14:37 GMT EAGLE5 42.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    remotehost1
       ARHOST   ---
       LPORT    2048          RPORT       2048
       ISTRMS   2             OSTRMS      2           BUFSIZE  400
       RMODE    LIN           RMIN        120         RMAX     800
       RTIMES   10            CWMIN       3000        UAPS     10
       OPEN     NO            ALW         YES         RTXTHR   2000
       RHOSTVAL RELAXED       M2PATSET    1

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (1600 KB of 1600 KB) on LOC = 1205
    Continue the procedure by performing one of these actions.
    • If the cwmin and m2patset parameters will not be specified in this procedure, continue the procedure with 7 .
    • If the cwmin parameter will be be specified in this procedure, continue the procedure with 5.
    • If the m2patset parameter will be be specified in this procedure, but the cwmin parameter will not be specified in this procedure, continue the procedure with 6.
  5. To change the cwmin value, the new cwmin parameter value must be less than or equal to the bufsize parameter value.
    The cwmin parameter is the number if bytes specified for the association's congestion window. The bufsize is the number of kilobytes specified for the size of the association's buffer. To determine whether or not the cwmin value is less than or equal to the bufsize value, perform one of these actions.
    • Multiply the bufsize value by 1024.
    • Divide the cwmin value by 1024.
    Continue the procedure by performing one of these actions.
    • If the new cwmin value is less than or equal to the bufsize value, and the m2patset parameter will be specified in this procedure, continue the procedure with 6.
    • If the new cwmin value is less than or equal to the bufsize value, and the m2patset parameter will not be specified in this procedure, continue the procedure with 7 .
    • If the new cwmin value is not less than or equal to the bufsize value, either choose another value for the cwmin parameter that is less than or equal to the bufsize value, or perform to change the bufsize value so that the bufsize value is greater than or equal to the cwmin value. After the new cwmin value has been chosen or the bufsize value has been changed, continue the procedure by performing one of these actions.
      • If the m2patset parameter will be specified in this procedure, continue the procedure with 6.
      • If the m2patset parameter will not be specified in this procedure, continue the procedure with 7.
  6. Verify the values of the M2PA timer set you wish to assign to the association by entering the rtrv-m2pa-tset command with the M2PA version (either ver=rfc to display the RFCM2PA timer values or ver=d6 to display the Draft 6 M2PA timer values) of the timer set you wish to assign to the association.

    If the ver parameter is not specified with the rtrv-m2pa-tset command, both the RFC and Draft 6 timer values are displayed.

    To display the M2PA Draft 6 timer values, enter this command.

    rtrv-m2pa-tset:ver=d6

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0

M2PA Draft 6 Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16    T17  T18
1    6000   ------ 5000  20000 500  5000  4000 1000  100000 150  500
2    7500   ------ 1500  2000  500  9000  1250 300   150000 175  600
3    100000 ------ 2000  3000  500  4000  1500 500   170000 200  800
4    200000 ------ 20000 4000  500  6000  2000 700   480000 225  900
5    250000 ------ 30000 30000 500  100   2250 400   400000 400  8000
6    50000  ------ 50000 60000 500  500   4500 800   300000 300  7000
7    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
8    80000  ------ 1500  15000 500  8000  2750 1100  350000 350  5000
9    27500  ------ 3850  4859  450  5700  3750 1150  250    375  8750
10   90000  ------ 2500  50000 500  7500  5000 1750  440000 450  3000
11   20000  ------ 4500  5500  500  6500  5500 1600  250000 475  4500
12   30000  ------ 7500  7000  500  750   4250 1800  275000 275  3500
13   40000  ------ 35000 9000  500  1250  3500 1900  500    325  9000
14   70000  ------ 45000 11000 500  1500  1750 900   1000   125  6000
15   9000   ------ 25000 40000 500  2500  3250 600   5000   425  5500
16   75000  ------ 15000 25000 500  4500  1600 1400  6000   240  9500
17   350000 ------ 60000 70000 600  10000 6000 2000  500000 500  10000
18   150000 ------ 55000 35000 500  3500  5750 1500  125000 440  750
19   175000 ------ 12500 45000 500  1100  2600 1300  7000   340  850
20   1000   ------ 1000  1000  400  80    1000 200   100    100  100

    To display the M2PARFC values, enter this command.

    rtrv-m2pa-tset:ver=rfc

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0

M2PA RFC Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16    T17  T18
1    6000   75000  5000  20000 500  5000  4000 1000  100000 150  500
2    7500   8000   1500  2000  500  9000  1250 300   150000 175  600
3    100000 10000  2000  3000  500  4000  1500 500   170000 200  800
4    200000 6000   20000 4000  500  6000  2000 700   480000 225  900
5    250000 140000 30000 30000 500  100   2250 400   400000 400  8000
6    50000  100000 50000 60000 500  500   4500 800   300000 300  7000
7    300000 20000  2000  10000 500  1000  3000 1200  200000 250  1000
8    80000  130000 1500  15000 500  8000  2750 1100  350000 350  5000
9    27500  120000 3850  4859  450  5700  3750 1150  250    375  8750
10   90000  9000   2500  50000 500  7500  5000 1750  440000 450  3000
11   20000  60000  4500  5500  500  6500  5500 1600  250000 475  4500
12   30000  50000  7500  7000  500  750   4250 1800  275000 275  3500
13   40000  90000  35000 9000  500  1250  3500 1900  500    325  9000
14   70000  45000  45000 11000 500  1500  1750 900   1000   125  6000
15   9000   30000  25000 40000 500  2500  3250 600   5000   425  5500
16   75000  15000  15000 25000 500  4500  1600 1400  6000   240  9500
17   350000 150000 60000 70000 600  10000 6000 2000  500000 500  10000
18   150000 20000  55000 35000 500  3500  5750 1500  125000 440  750
19   175000 12500  12500 45000 500  1100  2600 1300  7000   340  850
20   1000   5000   1000  1000  400  80    1000 200   100    100  100

    If the ver parameter is not specified when entering the rtrv-m2pa-tset command, both the Draft 6 and RFC values are displayed. This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0

M2PA Draft 6 Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16    T17  T18
1    6000   ------ 5000  20000 500  5000  4000 1000  100000 150  500
2    7500   ------ 1500  2000  500  9000  1250 300   150000 175  600
3    100000 ------ 2000  3000  500  4000  1500 500   170000 200  800
4    200000 ------ 20000 4000  500  6000  2000 700   480000 225  900
5    250000 ------ 30000 30000 500  100   2250 400   400000 400  8000
6    50000  ------ 50000 60000 500  500   4500 800   300000 300  7000
7    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
8    80000  ------ 1500  15000 500  8000  2750 1100  350000 350  5000
9    27500  ------ 3850  4859  450  5700  3750 1150  250    375  8750
10   90000  ------ 2500  50000 500  7500  5000 1750  440000 450  3000
11   20000  ------ 4500  5500  500  6500  5500 1600  250000 475  4500
12   30000  ------ 7500  7000  500  750   4250 1800  275000 275  3500
13   40000  ------ 35000 9000  500  1250  3500 1900  500    325  9000
14   70000  ------ 45000 11000 500  1500  1750 900   1000   125  6000
15   9000   ------ 25000 40000 500  2500  3250 600   5000   425  5500
16   75000  ------ 15000 25000 500  4500  1600 1400  6000   240  9500
17   350000 ------ 60000 70000 600  10000 6000 2000  500000 500  10000
18   150000 ------ 55000 35000 500  3500  5750 1500  125000 440  750
19   175000 ------ 12500 45000 500  1100  2600 1300  7000   340  850
20   1000   ------ 1000  1000  400  80    1000 200   100    100  100

M2PA RFC Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16    T17  T18
1    6000   75000  5000  20000 500  5000  4000 1000  100000 150  500
2    7500   8000   1500  2000  500  9000  1250 300   150000 175  600
3    100000 10000  2000  3000  500  4000  1500 500   170000 200  800
4    200000 6000   20000 4000  500  6000  2000 700   480000 225  900
5    250000 140000 30000 30000 500  100   2250 400   400000 400  8000
6    50000  100000 50000 60000 500  500   4500 800   300000 300  7000
7    300000 20000  2000  10000 500  1000  3000 1200  200000 250  1000
8    80000  130000 1500  15000 500  8000  2750 1100  350000 350  5000
9    27500  120000 3850  4859  450  5700  3750 1150  250    375  8750
10   90000  9000   2500  50000 500  7500  5000 1750  440000 450  3000
11   20000  60000  4500  5500  500  6500  5500 1600  250000 475  4500
12   30000  50000  7500  7000  500  750   4250 1800  275000 275  3500
13   40000  90000  35000 9000  500  1250  3500 1900  500    325  9000
14   70000  45000  45000 11000 500  1500  1750 900   1000   125  6000
15   9000   30000  25000 40000 500  2500  3250 600   5000   425  5500
16   75000  15000  15000 25000 500  4500  1600 1400  6000   240  9500
17   350000 150000 60000 70000 600  10000 6000 2000  500000 500  10000
18   150000 20000  55000 35000 500  3500  5750 1500  125000 440  750
19   175000 12500  12500 45000 500  1100  2600 1300  7000   340  850
20   1000   5000   1000  1000  400  80    1000 200   100    100  100

    If the M2PA timer set you wish to assign to the association does not contain the desired values, performChanging a M2PA Timer Set to change the desired timer values.

    Caution:

    Changing anM2PA timer set may affect the performance of any associations using the timer set being changed.
  7. The remote hosts assigned to the association can be changed by specifying the rhost and rhosttype parameters with the chg-assoc command.

    If the primary and alternate remote hosts are not being changed in this procedure, or if only the primary remote host is being changed, continue the procedure with 9.

    To change the alternate remote host value for the association, the association must have a primary remote host assigned to it. If the association has a primary remote host, continue the procedure with 9. If the association does not have a primary remote host, continue the procedure with 8.

  8. Assign a primary remote host to the association by entering the chg-assoc command with the name of the association and the primary remote host name.

    For this example, enter this command.

    chg-assoc:aname=assoc2:rhost=”gw200.nc-Oracle.com”

    The rhosttype=primary parameter can be specified with the chg-assoc command, but is not necessary.

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
CHG-ASSOC: MASP A - COMPLTD;
  9. Change the association using the chg-assoc command.

    For this example, enter this command.

    chg-assoc:aname=assoc2:rhost=”gw200.nc-Oracle.com”:rport=3000 :rtxthr=10000:rhostval=match

    If an alternate remote host is being specified for the association, for this example enter this command.

    chg-assoc:aname=assoc2:rhost=”gw210.nc-Oracle.com”:rhosttype=alternate:rport=3000 :rtxthr=10000:rhostval=match

    If only the alw, open, or rtxthr parameter values are being changed in this step, for this example, enter this command.

    chg-assoc:aname=assoc2:alw=no:open=yes:rtxthr=10000

    These are the rules that apply to changing the attributes of M2PA associations that are assigned to IPLIMx signaling links.
    • If any optional parameters are not specified with the chg-assoc command, those values are not changed.
    • The value of the rhost parameter is a text string of up to 60 characters, with the first character being a letter. The command input is limited to 150 characters, including the hostname.
    • If the value of the open parameter is yes, only the values of the alw and rtxthr parameters can be changed. To change the values of the other parameters, the value of the open parameter must be no.
    • The value of the rmin parameter must be less than or equal to the rmax parameter value.
    • 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.

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;

    If the value of the open parameter was not changed in 3, continue the procedure with Oracle.

  10. Change the value of the open parameter to yes by specifying the chg-assoc command with the open=yes parameter.

    For this example, enter this command.

    chg-assoc:aname=assoc2:open=yes

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
  11. Verify the changes using the rtrv-assoc command specifying the association name specified in 9 and 10.

    For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of possible output. 

    
rlghncxa03w 10-07-28 21:14:37 GMT EAGLE5 42.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    gw200.nc-Oracle.com
       ARHOST   gw210.nc-Oracle.com
       LPORT    2048          RPORT       3000
       ISTRMS   2             OSTRMS      2           BUFSIZE  400
       RMODE    LIN           RMIN        120         RMAX     800
       RTIMES   10            CWMIN       3000        UAPS     10
       OPEN     YES           ALW         NO          RTXTHR   10000
       RHOSTVAL MATCH         M2PATSET    1

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (1600 KB of 1600 KB) on LOC = 1205
  12. Back up the new changes, using the chg-db:action=backup:dest=fixed command.

    These messages should appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first. 

    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.
    If you wish to change the lhost, alhost, bufsize, or link values of the M2PA association, perform one of these procedures.

    If you do not wish to change the lhost, alhost, bufsize, or link values of the M2PA association, this procedure is finished.

Figure 3-17 Changing the Attributes of an M2PA Association



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

3.18 Changing the Buffer Size of a M2PA Association

This procedure is used to change the buffer size of a M2PA association, assigned to cards that are running the IPLIM or IPLIMI applications, using the chg-assoc command. If you wish to change the buffer size of M2PA associations assigned to cards that are running the IPSG application, perform the Changing the Buffer Size of an IPSG Association procedure.

These parameters of the chg-assoc command are used in this procedure:

:aname – The name assigned to the association, shown in the rtrv-assoc output.

:open – The connection state for this association. Valid values are yes or no. When the open=yes parameter is specified, the connection manager opens the association if the association is operational. When the open=no parameter is specified, the connection manager will not open the association.

:bufsize – The size, in kilobytes, of the buffer used by the association. The values for this parameter are 8 kilobytes to 400 kilobytes. The maximum size of the buffers on the E5-ENET cards are shown in the following list.

  • E5-ENET Card - 3200 KB

The size of the buffers assigned to each association that is assigned to the IP card cannot exceed the maximum buffer size for that card. If the bufsize parameter value causes the total buffer size for all the associations on the IP card to exceed the maximum buffer size for that IP card, the chg-assoc command will be rejected. The available size of the buffers on the IP card can be verified by entering this command.

rtrv-assoc:lhost=<local host name assigned to the association being changed>

The alhost parameter can also be used with the rtrv-assoc command to display the available size of the buffers on the IP card.

The aname parameter can be used with the rtrv-assoc command to display the available size of the buffers on the IP card and the size of the buffer assigned to the association.

If you wish to increase the buffer size for this association to a value that is greater than available buffer size for the card, the buffer size of the other associations assigned to the card must be decreased.

The chg-assoc command contains other parameters that are not used this procedure. To change these parameters, perform these procedures.

Canceling the RTRV-ASSOC Command

Because the rtrv-assoc command used in this procedure can output information for a long period of time, the rtrv-assoc command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-assoc command can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-assoc command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-assoc command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-assoc command was entered, from another terminal other that the terminal where the rtrv-assoc command was entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

  1. Display the associations in the database using the rtrv-assoc command.

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
swbel32         1201 A     A    M3UA    1030  2345  YES  YES
a2              1305 A     A    SUA     1030  2345  YES  YES
a3              1307 A     A    SUA     1030  2346  YES  YES
assoc1          1201 A     A    M3UA    2000  1030  YES  YES
assoc2          1205 A     A    M2PA    2048  2048  YES  YES
assoc3          1205 A     B2   M2PA    3000  3000  YES  YES
assoc5          1205 A     A3   M2PA    1500  3000  YES  YES
  2. Enter the rtrv-card command with the location of the card that is hosting the M2PA association that will be changed in this procedure. For this example, enter this command.

    rtrv-card:loc=1205

    This is an example of possible output. 

    
rlghncxa03w 08-04-06 15:17:20 EST EAGLE5 38.0.0
CARD   TYPE      APPL     LSET NAME   LINK SLC LSET NAME   LINK SLC
1205   DCM       IPLIM    e5e6a       A    0   e5e6a       B2   1
                          e5e6a       A3   2
    If the application assigned to the card is IPLIM or IPLIMI, shown in the APPL column, continue the procedure by performing one of these steps.
    • If the open parameter value for the association being changed is yes, continue the procedure with 3.
    • If the open parameter value for the association being changed is no, continue the procedure with 4.

    If the application assigned to the card is IPSG, perform the Changing the Buffer Size of an IPSG Association procedure.

  3. Change the value of the open parameter to no by specifying the chg-assoc command with the open=no parameter.

    For this example, enter this command.

    chg-assoc:aname=assoc2:open=no

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
  4. Display the association being changed by entering the rtrv-assoc command with the aname parameter specified in 3 or the name of the association assigned to the card displayed in 1.

    For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of the possible output. 

    
rlghncxa03w 10-07-28 21:14:37 GMT EAGLE5 42.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    remotehost1
       ARHOST   ---
       LPORT    2048          RPORT       2048
       ISTRMS   2             OSTRMS      2           BUFSIZE  400
       RMODE    LIN           RMIN        120         RMAX     800
       RTIMES   10            CWMIN       3000        UAPS     10
       OPEN     NO            ALW         YES         RTXTHR   2000
       RHOSTVAL RELAXED       M2PATSET    1

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (1600 KB of 1600 KB) on LOC = 1205
  5. If the bufsize parameter value causes the total buffer size for all the associations on the IP card to exceed the maximum buffer size for that IP card, the chg-assoc command will be rejected.

    If you wish to increase the buffer size for this association to a value that is greater than available buffer size for the card, the buffer size of the other associations assigned to the card must be decreased. Perform this step and 6, 7, and 8.

    If the buffers on the other associations assigned to the card do not need to be changed, continue the procedure with 9.

    Display the associations assigned to the IP card (and its corresponding local host) by entering the rtrv-assoc command with the local host name assigned to the association being changed. For this example, enter this command.

    rtrv-assoc:lhost=IPNODE2-1205

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:14:37 GMT EAGLE5 36.0.0
                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
assoc2          1205 A     A    M2PA    2048  2048  YES  YES
assoc3          1205 A     B2   M2PA    3000  3000  YES  YES
assoc5          1205 A     A3   M2PA    1500  3000  YES  YES

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (1600 KB of 1600 KB) on LOC = 1205
  6. Display each association shown in 5 by entering the rtrv-assoc command with the name of each association shown in 5.

    For this example, enter these commands.

    rtrv-assoc:aname=assoc2

    This is an example of the possible output. 

    
rlghncxa03w 10-07-28 21:14:37 GMT EAGLE5 42.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    remotehost1
       ARHOST   ---
       LPORT    2048          RPORT       2048
       ISTRMS   2             OSTRMS      2           BUFSIZE  400
       RMODE    LIN           RMIN        120         RMAX     800
       RTIMES   10            CWMIN       3000        UAPS     10
       OPEN     NO            ALW         YES         RTXTHR   2000
       RHOSTVAL RELAXED       M2PATSET    1

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (1600 KB of 1600 KB) on LOC = 1205

    rtrv-assoc:aname=assoc3

    This is an example of the possible output. 

    
rlghncxa03w 10-07-28 21:14:37 GMT EAGLE5 42.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  B2
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    remotehost3
       ARHOST   ---
       LPORT    3000          RPORT       3000
       ISTRMS   2             OSTRMS      2           BUFSIZE  400
       RMODE    LIN           RMIN        120         RMAX     800
       RTIMES   10            CWMIN       3000        UAPS     10
       OPEN     YES           ALW         YES         RTXTHR   2000
       RHOSTVAL RELAXED       M2PATSET    1

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (1600 KB of 1600 KB) on LOC = 1205

    rtrv-assoc:aname=assoc5

    This is an example of the possible output. 

    
rlghncxa03w 10-07-28 21:14:37 GMT EAGLE5 42.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A3
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    remotehost3
       ARHOST   ---
       LPORT    1500          RPORT       3000
       ISTRMS   2             OSTRMS      2           BUFSIZE  400
       RMODE    LIN           RMIN        120         RMAX     800
       RTIMES   10            CWMIN       3000        UAPS     10
       OPEN     YES           ALW         YES         RTXTHR   2000
       RHOSTVAL RELAXED       M2PATSET    1

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (1600 KB of 1600 KB) on LOC = 1205
  7. To change the bufsize value for the associations shown in 6, the new bufsize parameter value must be greater than or equal to the cwmin parameter value.
    The cwmin parameter is the number if bytes specified for the association's congestion window. The bufsize is the number of kilobytes specified for the size of the association's buffer. To determine whether or not the cwmin value is less than or equal to the bufsize value, perform one of these actions.
    • Multiply the bufsize value by 1024.
    • Divide the cwmin value by 1024.
    Continue the procedure by performing one of these actions.
    • If the new bufsize value is greater than or equal to the cwmin value, continue the procedure with 8.
    • If the new bufsize value is not greater than or equal to the cwmin value, either choose another value for the bufsize parameter that is greater than or equal to the cwmin value, or perform the Changing the Attributes of an M2PA Association procedure to change the bufsize value so that the bufsize value is greater than or equal to the cwmin value. After the new bufsize value has been chosen or the cwmin value has been changed, continue the procedure with 8.
  8. Change the size of the buffers for one or more of the associations displayed in 6 to allow the buffer of the association displayed in 4 to be changed.

    Enter the chg-assoc command with the bufsize parameter. For this example, enter this command.

    chg-assoc:aname=assoc3:bufsize=400

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
  9. To change the bufsize value for the association shown in 4, the new bufsize parameter value must be greater than or equal to the cwmin parameter value.
    The cwmin parameter is the number if bytes specified for the association's congestion window. The bufsize is the number of kilobytes specified for the size of the association's buffer. To determine whether or not the cwmin value is less than or equal to the bufsize value, perform one of these actions.
    • Multiply the bufsize value by 1024.
    • Divide the cwmin value by 1024.
    Continue the procedure by performing one of these actions.
    • If the new bufsize value is greater than or equal to the cwmin value, continue the procedure with 10.
    • If the new bufsize value is not greater than or equal to the cwmin value, either choose another value for the bufsize parameter that is greater than or equal to the cwmin value, or perform the Changing the Attributes of an M2PA Association procedure to change the bufsize value so that the bufsize value is greater than or equal to the cwmin value. After the new bufsize value has been chosen or the cwmin value has been changed, continue the procedure with 10.
  10. Change the association using the chg-assoc command.

    For this example, enter this command.

    chg-assoc:aname=assoc2:bufsize=500

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;

    If the value of the open parameter was not changed in 3, continue the procedure with 12.

    If the value of the open parameter was changed in 3, continue the procedure with 11.

  11. Change the value of the open parameter to yes by specifying the chg-assoc command with the open=yes parameter.

    For this example, enter this command.

    chg-assoc:aname=assoc2:open=yes

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
  12. Verify the changes using the rtrv-assoc command specifying the association name specified in 10 and 11.

    For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of possible output. 

    
rlghncxa03w 10-07-28 21:14:37 GMT EAGLE5 42.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    remotehost1
       ARHOST   ---
       LPORT    2048          RPORT       2048
       ISTRMS   2             OSTRMS      2           BUFSIZE  500
       RMODE    LIN           RMIN        120         RMAX     800
       RTIMES   10            CWMIN       3000        UAPS     10
       OPEN     YES           ALW         YES         RTXTHR   2000
       RHOSTVAL RELAXED       M2PATSET    1

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (1600 KB of 1600 KB) on LOC = 1205
  13. Back up the new changes, using the chg-db:action=backup:dest=fixed command.

    These messages should appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first. 

    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.
    If you wish to change the other attributes of the M2PA association, perform one of these procedures.

    If you do not wish to change the other attributes of the M2PA association, this procedure is finished.

Figure 3-18 Changing the Buffer Size of a M2PA Association



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

3.19 Changing the Host Values of a M2PA Association

This procedure is used to change the host values of a M2PA association, assigned to cards that are running the IPLIM or IPLIMI applications, using the chg-assoc command. If you wish to change the attributes of M2PA associations assigned to cards that are running the IPSG application, perform the Changing the Host Values of an IPSG Association procedure.

These parameters of the chg-assoc command are used in this procedure:

:aname – The name assigned to the association, shown in the rtrv-assoc output.

:lhost – The host name for the local host, shown in the rtrv-ip-host output.

:lport – The SCTP port number for the local host.

:rhost – The host name for the remote host, rhost can be any string of characters starting with a letter and comprising these characters ['a'..'z', 'A'..'Z', '0'..'9', '-', '.']. Hostnames are not case-sensitive and can contain up to 60 characters. The default value of this optional parameter is empty (null string).

:rport – The SCTP port number for the remote host.

:alhost – The alternate local host name, shown in the rtrv-ip-host output.

:link – The signaling link on the IPLIMx card. If the card is a E5-ENET card, the values for the link parameter can be a, a1, a2, a3, a4, a5, a6, a7, b, b1, b2, b3, b4, b5, b6, or b7.

Note:

The port parameter can be used in place of the link parameter to specify the signaling link on the card.

:adapter – The adapter layer for this association, m2pa.

:open – The connection state for this association. Valid values are yes or no. When the open=yes parameter is specified, the connection manager opens the association if the association is operational. When the open=no parameter is specified, the connection manager will not open the association.

:m2patset – The M2PA timer set assigned to the association. The m2patset parameter can be specified only with the adapter=m2pa parameter, or if the association already has the adapter=m2pa parameter assigned and the adapter parameter value is not being changed. If the adapter parameter value is being changed to m2pa, and the m2patset parameter is not specified, the default value for the m2patset parameter (1 - M2PA timer set 1) is assigned to the association. If the adapter parameter value for the association is m2pa, is not being changed, and the m2patset parameter is not specified with the chg-assoc command, the m2patset parameter value is not changed.

:ver – The M2PA version assigned to the M2PA association, either the RFC version (ver=rfc), or the Draft 6 version (ver=d6). The ver parameter can be specified only if, when this procedure is completed, the adapter parameter value is m2pa. If the adapter parameter value is being changed to m2pa, and the ver parameter is not specified, the default M2PA version of RFC is assigned to the association. To change the ver parameter value, the open parameter value for the association must be no.

The chg-assoc command contains other parameters that are not used this procedure. To change these parameters, perform these procedures.

At least one optional parameter is required.

The command input is limited to 150 characters, including the hostnames.

The EAGLE can contain a maximum of 4000 connections (association to application server assignments).

IPLIMx cards can have one association for each signaling link on the card. The E5-ENET card can contain a maximum of 16 signaling links, resulting in a maximum of 16 associations for this card.

The B Ethernet interface of the IP card can be used on E5-ENET cards.

The ipliml2 parameter value of the signaling link assigned to the association must be m2pa. The adapter parameter value of the association must match the ipliml2 parameter value.

The signaling link being assigned to the association must be out of service. This state is shown in the rept-stat-slk output with the entries OOS-MT in the PST field and Unavail in the SST field.

Uni-homed endpoints are associations configured with the lhost parameter only. The lhost parameter value represents an IP address that corresponds to either the A or B network interface of the IP card. Multi-homed endpoints are associations configured with both the lhost and alhost parameters. The lhost parameter value represents an IP address corresponding to one of the network interfaces (A or B) of the IP card while the alhost parameter value represents an IP address corresponding to the other network interface of the same IP card.

The alhost=none parameter removes the alternate local host from the specified association, which also removes the multi-homed endpoint capability.

Canceling the RTRV-ASSOC and RTRV-AS Commands

Because the rtrv-assoc and rtrv-as commands used in this procedure can output information for a long period of time, the rtrv-assoc and rtrv-as commands can be canceled and the output to the terminal stopped. There are three ways that the rtrv-assoc and rtrv-as commands can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-assoc or rtrv-as commands were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-assoc or rtrv-as commands were entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-assoc or rtrv-as commands were entered, from another terminal other that the terminal where the rtrv-assoc or rtrv-as commands were entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

  1. Display the associations in the database using the rtrv-assoc command.

    This is an example of possible output. 

    
rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0

                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
swbel32         1201 A     A    M3UA    1030  2345  YES  YES
a2              1305 A     A    SUA     1030  2345  YES  YES
a3              1307 A     A    SUA     1030  2346  YES  YES
assoc1          1201 A     A    M3UA    2000  1030  YES  YES
assoc2          2105 A     A    M2PA    2048  2048  YES  YES
assoc3          2105 A     B2   M2PA    3000  3000  YES  YES
assoc5          2105 A     A3   M2PA    1500  3000  YES  YES
  2. Enter the rtrv-card command with the location of the card that is hosting the M2PA association that will be changed in this procedure. For this example, enter this command.

    rtrv-card:loc=2105

    This is an example of possible output. 

    
rlghncxa03w 08-04-06 15:17:20 EST EAGLE5 38.0.0
CARD   TYPE      APPL     LSET NAME   LINK SLC LSET NAME   LINK SLC
2105   DCM       IPLIM    e5e6a       A    0   e5e6a       B2   1
                          e5e6a       A3   2
    If the application assigned to the card is IPLIM or IPLIMI, shown in the APPL column, continue the procedure by performing one of these steps.
    • If the open parameter value for the association being changed is yes, continue the procedure with 3.
    • If the open parameter value for the association being changed is no, continue the procedure with 4.

    If the application assigned to the card is IPSG, perform the Changing the Host Values of an IPSG Association procedure.

  3. Change the value of the open parameter to no by specifying the chg-assoc command with the open=no parameter.

    For this example, enter this command.

    chg-assoc:aname=assoc2:open=no

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0
CHG-ASSOC: MASP A - COMPLTD;
  4. Display the association being changed by entering the rtrv-assoc command with the aname parameter specified in 3.

    For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of the possible output. 

    
rlghncxa03w 10-07-28 21:14:37 GMT EAGLE5 42.0.0
 ANAME assoc2
       LOC      2105          IPLNK PORT  A,B        LINK  A
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    IPNODE2-1205
       ALHOST   M2PA1
       RHOST    remotehost1
       ARHOST   ---
       LPORT    2048          RPORT       2048
       ISTRMS   2             OSTRMS      2           BUFSIZE  400
       RMODE    LIN           RMIN        120         RMAX     800
       RTIMES   10            CWMIN       3000        UAPS     10
       OPEN     NO            ALW         YES         RTXTHR   2000
       RHOSTVAL RELAXED       M2PATSET    1

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (1600 KB of 1600 KB) on LOC = 2105

    If the association shown in this step is not an M2PA association, continue the procedure with 5.

    If the association shown in this step is an M2PA association, perform one of these actions.
    • If the association does not have an ALHOST value, continue the procedure with 5.
    • If the association does have an ALHOST value, and the ALHOST value will be removed along with changing the LHOST value of the association, continue the procedure with 5.
    • If the association does have an ALHOST value, and the only action that will be performed in this procedure is to remove the ALHOST value from the association, continue the procedure with Oracle.
  5. Verify that the local host name to be assigned to the association is in the database by entering the rtrv-ip-host:display=all command.

    The following is an example of the possible output. 

    
rlghncxa03w 08-12-28 21:15:37 GMT EAGLE5 40.0.0

LOCAL IPADDR    LOCAL HOST
192.1.1.10      IPNODE1-1201
192.1.1.12      GW105. NC. Oracle. COM
192.1.1.14      IPNODE1-1205
192.1.1.20      IPNODE2-1201
192.1.1.22      IPNODE2-1203
192.1.1.24      IPNODE2-1205
192.1.1.30      KC-HLR1
192.1.1.32      KC-HLR2
192.1.1.50      DN-MSC1
192.1.1.52      DN-MSC2
192.1.1.54      M2PA1

REMOTE IPADDR   REMOTE HOST
150.1.1.5       NCDEPTECONOMIC_DEVELOPMENT. SOUTHEASTERN_COORIDOR_ASHVL. GOV

IP Host table is (12 of 4096) .29% full
  6. Display the IP links in the database by entering the rtrv-ip-lnk command.

    The following is an example of the possible output. 

    
rlghncxa03w 08-12-28 21:14:37 GMT EAGLE5 40.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
1303  A    192.1.1.10      255.255.255.128 HALF    10    802.3   NO   NO
1303  B    --------------- --------------- HALF    10    DIX     NO   NO
1305  A    192.1.1.12      255.255.255.0   ----    ---   DIX     YES  NO
1305  B    --------------- --------------- HALF    10    DIX     NO   NO
1313  A    192.1.1.14      255.255.255.0   FULL    100   DIX     NO   NO
1313  B    --------------- --------------- HALF    10    DIX     NO   NO
2101  A    192.1.1.20      255.255.255.0   FULL    100   DIX     NO   NO
2101  B    --------------- --------------- HALF    10    DIX     NO   NO
2103  A    192.1.1.22      255.255.255.0   FULL    100   DIX     NO   NO
2103  B    --------------- --------------- HALF    10    DIX     NO   NO
2105  A    192.1.1.24      255.255.255.0   FULL    100   DIX     NO   NO
2105  B    192.1.1.54      255.255.255.0   FULL    100   DIX     NO   NO
2205  A    192.1.1.30      255.255.255.0   FULL    100   DIX     NO   NO
2205  B    --------------- --------------- HALF    10    DIX     NO   NO
2207  A    192.1.1.32      255.255.255.0   FULL    100   DIX     NO   NO
2207  B    --------------- --------------- HALF    10    DIX     NO   NO
2213  A    192.1.1.50      255.255.255.0   FULL    100   DIX     NO   NO
2213  B    --------------- --------------- HALF    10    DIX     NO   NO
2301  A    192.1.1.52      255.255.255.0   FULL    100   DIX     NO   NO
2301  B    --------------- --------------- HALF    10    DIX     NO   NO

IP-LNK   table is (20 of 2048) 1% full.

    If the required IP link, one that contains the desired IP address, is not shown in the rtrv-ip-lnk output, add the IP link using the Configuring an IP Link procedure. After the IP link has been added, assign the IP address of the IP link to the IP host name using the Adding an IP Host procedure. Then continue the procedure with 11.

    If the required IP link is shown in the rtrv-ip-lnk output, but the IP host is not shown in the rtrv-ip-host output in 5, assign the IP address of the IP link to the IP host name using the Adding an IP Host procedure. Then continue the procedure with 11.

    If the required IP host was shown in 5, the required IP link is shown in the rtrv-ip-lnk output in this step. Perform 7 to verify the application running on the card whose IP address is assigned to the IP host.

    Note:

    Thertrv-ip-host output must contain a host name for the association’slhost parameter and a host name for the association’salhost parameter, if thealhost parameter will be specified for the association. The IP address of the IP link should be assigned to the host name, shown in thertrv-ip-host output, that will be used as the association’slhost parameter value. If thealhost parameter will be specified for the association, the IP address of the IP link must be assigned to the host name that will be used as thealhost parameter value. The IP links associated with the association’slhost andalhost values must be assigned to the same card.
  7. Display the application running on the IP card shown in 6 whose IP address is assigned to the IP host using the rept-stat-card command specifying the location of the IP card.

    For this example, enter this command.

    rept-stat-card:loc=1205

    This is an example of the possible output. 

    
rlghncxa03w 08-04-27 17:00:36 GMT EAGLE5 38.0.0
CARD  VERSION      TYPE    GPL       PST           SST       AST
1205  114-000-000  DCM     IPLIM     IS-NR         Active    -----
  ALARM STATUS      = No Alarms.
  BPDCM GPL         = 002-102-000
  IMT BUS A         = Conn
  IMT BUS B         = Conn
  SIGNALING LINK STATUS
      SLK    PST                LS            CLLI
      A      IS-NR              e5e6a         -----------
      A3     IS-NR              e5e6a         -----------
      B2     IS-NR              e5e6a         -----------

Command Completed.
  8. Display the signaling link associated with the association being changed using the rtrv-slk command and specifying the card location shown in 7, and the new link parameter value of the association for the link parameter value. The card location should reference the local host assigned to the association. The rtrv-ip-lnk output shows the card location associated with the IP address that is associated with the local host in 7. If the rtrv-ip-lnk command was not executed in 6, execute it now to get the card location and the IP address. To display the signaling link for this example, enter this command.

    Note:

    If thelink parameter value is not being changed, continue the procedure with9.

    rtrv-slk:loc=1205:link=a

    The following is an example of the possible output. 

    
rlghncxa03w 08-04-19 21:17:04 GMT EAGLE5 38.0.0
LOC   LINK LSN          SLC TYPE    IPLIML2
1205  A    e5e6a         0  IPLIM   M2PA

    If the required signaling link is not in the database, add the signaling link using the Adding an IPLIMx Signaling Link procedure without activating the signaling link. If the application of the card containing the signaling link is IPLIM or IPLIMI, the ipliml2=m2pa parameter must be specified for the signaling link and the adapter=m2pa parameter value must be specified for the association.

  9. Display the application servers referencing the association being changed using the rtrv-as command with the name of the association being changed in this procedure.

    Note:

    If theadapter parameter value is not being changed from M3UA or SUA to M2PA, continue the procedure with10.

    For this example, enter this command.

    rtrv-as:aname=assoc2

    This is an example of possible output. 

    
rlghncxa03w 08-04-28 21:14:37 GMT EAGLE5 38.0.0
AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   2000    assoc2

as4               LOADSHARE   2000    assoc2

as6               LOADSHARE   2000    assoc2

AS Table is (6 of 250) 1% full

    If the association is not assigned to any application servers, continue the procedure with 10

    If the association is assigned to any application servers, go to the Removing an Association from an Application Server procedure and remove the association from the application servers. After the association has been removed from the application servers, continue the procedure with 10

  10. Display the application running on the IP card shown in 6 using the rept-stat-card command specifying the location of the IP card.

    Note:

    If therept-stat-card command was performed in7, continue the procedure with11.

    For this example, enter this command.

    rept-stat-card:loc=2105

    This is an example of the possible output. 

    
rlghncxa03w 08-04-27 17:00:36 GMT EAGLE5 38.0.0
CARD  VERSION      TYPE    GPL       PST           SST       AST
2105  114-000-000  DCM     IPLIM     IS-NR         Active    -----
  ALARM STATUS      = No Alarms.
  BPDCM GPL         = 002-102-000
  IMT BUS A         = Conn
  IMT BUS B         = Conn
  SIGNALING LINK STATUS
      SLK    PST                LS            CLLI
      A      IS-NR              e5e6a         -----------
      A3     IS-NR              e5e6a         -----------
      B2     IS-NR              e5e6a         -----------

Command Completed.
  11. Display the signaling link that will be assigned to the association by entering the rtrv-slk command and specifying the card location and signaling link.

    Note:

    If a new signaling link was added in8, continue the procedure withOracle.

    For this example, enter this command.

    rtrv-slk:loc=1203:link=a

    This is an example of the possible output. 

    
rlghncxa03w 08-04-19 21:17:04 GMT EAGLE5 38.0.0
LOC   LINK LSN          SLC TYPE    IPLIML2
1203  A    e5e6a         1  IPLIM   M2PA

    When the IP card’s application is either IPLIM or IPLIMI, the ipliml2 parameter value for the signaling link assigned to the association must be m2pa. If the ipliml2 parameter is not m2pa, remove the signaling link using the Removing an IPLIMx Signaling Link procedure. Add the signaling link back into the database with the ipliml2=m2pa parameter, and without activating the signaling link, using the Adding an IPLIMx Signaling Link procedure.

  12. Display the status of the signaling link shown in 11 using the rept-stat-slk command specifying the card location and signaling link.

    Note:

    If theAdding an IPLIMx Signaling Linkprocedure was not performed in11, continue the procedure withOracle.

    For example, enter this command.

    rept-stat-slk:loc=1203:link=a

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
SLK      LSN         CLLI        PST          SST       AST
1203,A   e5e6a       ----------- IS-NR        Avail     ----
Command Completed.

    Note:

    If the primary state (PST) of the signaling link isOOS-MT and the secondary state (SST) isUnavail, continue the procedure withOracle.
  13. Deactivate the signaling link from 12 using the dact-slk command.

    For example, enter this command.

    dact-slk:loc=1203:link=a

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 08-04-07 11:11:28 GMT EAGLE5 38.0.0
Deactivate Link message sent to card
  14. Verify the status of the signaling link using the rept-stat-slk command.

    For example, enter this command.

    rept-stat-slk:loc=1203:link=a

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
SLK      LSN         CLLI        PST          SST       AST
1203,A   e5e6a       ----------- OOS-MT       Unavail   ----
Command Completed.
  15. Change the association using the chg-assoc command.

    For this example, enter this command.

    chg-assoc:aname=assoc2:lhost=m2pa2:alhost=m2pa3:rhost="gw200.nc-Oracle.com"

    These are the rules that apply to changing the host value of M2PA associations that are assigned to IPLIMx signaling links.
    • If any optional parameters are not specified with the chg-assoc command, those values are not changed.
    • The B Ethernet interface can be used with E5-ENET cards.
    • The EAGLE can contain a maximum of 4000 connections.
    • IPLIMx cards can have only one connection for each signaling link assigned to the card. If the card is an E5-ENET card, the card may contain a maximum of 16 connections.
    • The value of the lhost and rhost parameters is a text string of up to 60 characters, with the first character being a letter. The command input is limited to 150 characters, including the hostnames.
    • The adapter parameter value for the association must be m2pa and the ipliml2=m2pa parameter must be assigned to the signaling link on the iplim or iplimi card.
    • Specifying the lhost parameter only creates a uni-homed endpoint. The network portion of the endpoint's IP address must be the same as the network portion of the IP address assigned to either the A or B network interface of the IP card.
    • Specifying the lhost and alhost parameters creates a multi-homed endpoint. The network portion of the IP address associated with the lhost parameter must be the same as the network portion of the IP address assigned to one of the network interfaces (A or B) of the IP card, and the network portion of the IP address associated with the alhost parameter must be the same as the network portion of the IP address assigned to the other network interface on the IP card.
    • The alhost=none parameter removes the alternate local host from the specified association, which also removes the multi-homed endpoint capability.
    • If the mp2atset parameter is not specified with the chg-assoc command, and the adapter parameter value is being changed to m2pa, the m2patset parameter value defaults to M2PA timer set 1 (m2patset=1).
    • The port parameter can be used in place of the link parameter to specify the signaling link assigned to the association.
    • 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.
    • If the adapter parameter value of the association is changed to m2pa in this procedure and the ver parameter is not specified, the version of the association will be RFC. To make this association a M2PA Draft 6 association, the ver=d6 parameter must be specified for this association.

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0
CHG-ASSOC: MASP A - COMPLTD;

    Note:

    If the value of theopen parameter was not changed in3, continue the procedure withOracle.
  16. Change the value of the open parameter to yes by specifying the chg-assoc command with the open=yes parameter.

    For this example, enter this command.

    chg-assoc:aname=assoc2:open=yes

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0
CHG-ASSOC: MASP A - COMPLTD;
  17. Verify the changes using the rtrv-assoc command specifying the association name specified in Oracle and 16.

    For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of possible output. 

    
rlghncxa03w 10-07-28 21:14:37 GMT EAGLE5 42.0.0
 ANAME assoc2
       LOC      1203          IPLNK PORT  A,B        LINK  A
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    M2PA2
       ALHOST   M2PA3
       RHOST    gw200.nc-tekelec.com
       ARHOST   ---
       LPORT    2048          RPORT       3000
       ISTRMS   2             OSTRMS      2           BUFSIZE  500
       RMODE    LIN           RMIN        120         RMAX     800
       RTIMES   10            CWMIN       3000        UAPS     10
       OPEN     YES           ALW         YES         RTXTHR   10000
       RHOSTVAL RELAXED       M2PATSET    1

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (1300 KB of 1600 KB) on LOC = 1203
  18. Activate the signaling link assigned to the association using the act-slk command.

    For example, enter this command.

    act-slk:loc=1203:link=a

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 08-04-07 11:11:28 GMT EAGLE5 38.0.0
Activate Link message sent to card
  19. Verify the status of the signaling link using the rept-stat-slk command.

    For example, enter this command.

    rept-stat-slk:loc=1203:link=a

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
SLK      LSN         CLLI        PST          SST       AST
1203,A   e5e6a       ----------- IS-NR        Avail     ----
Command Completed.
  20. Back up the new changes, using the chg-db:action=backup:dest=fixed command.

    These messages should appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first. 

    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.
    If you wish to change the other attributes of the M2PA association, perform one of these procedures.

    If you do not wish to change the other attributes of the M2PA association, this procedure is finished.

Figure 3-19 Changing the Host Values of a M2PA Association



Sheet 1 of 7



Sheet 2 of 7



Sheet 3 of 7



Sheet 4 of 7



Sheet 5 of 7



Sheet 6 of 7



Sheet 7 of 7

3.20 Changing the Link Value of a M2PA Association to another Link Value on the Same IPLIMx Card

This procedure is used to change the link value of an M2PA association, assigned to cards that are running the IPLIM or IPLIMI applications (IPLIMx cards), to another link value that is assigned to the same IPLIMx card that is hosting the M2PA association. The chg-assoc command is used to change the link value for the association. If you wish to change the attributes of M2PA associations assigned to cards that are running the IPSG application, perform the Changing the Attributes of an IPSG Association procedure.

These parameters of the chg-assoc command are used in this procedure:

:aname – The name assigned to the association, shown in the rtrv-assoc output.

:link – The signaling link on the IPLIMx card. If the card is a single-slot EDCM, the values for the link parameter can be a, a1, a2, a3, b, b1, b2, or b3.

If the card is a E5-ENET card, the values for the link parameter can be a, a1, a2, a3, a4, a5, a6, a7, b, b1, b2, b3, b4, b5, b6, or b7.

Note:

The port parameter can be used in place of the link parameter to specify the signaling link on the card.

:open – The connection state for this association. Valid values are yes or no. When the open=yes parameter is specified, the connection manager opens the association if the association is operational. When the open=no parameter is specified, the connection manager will not open the association.

IPLIMx cards can have one association for each signaling link on the card. The single-slot EDCM can contain a maximum of eight signaling links, resulting in a maximum of eight associations for this card. The E5-ENET card can contain a maximum of 16 signaling links, resulting in a maximum of 16 associations for this card.

The signaling link being assigned to the association must be out of service. This state is shown in the rept-stat-slk output with the entries OOS-MT in the PST field and Unavail in the SST field.

If you wish to change the lhost, alhost, bufsize, or link values of the M2PA association, perform one of these procedures.

If you do not wish to change the lhost, alhost, bufsize, or link values of the M2PA association, this procedure is finished.

Canceling the RTRV-ASSOC Command

Because the rtrv-assoc command used in this procedure can output information for a long period of time, the rtrv-assoc command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-assoc command can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-assoc command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-assoc command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-assoc command was entered, from another terminal other that the terminal where the rtrv-assoc command was entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

  1. Display the associations in the database using the rtrv-assoc command.

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
swbel32         1201 A     A    M3UA    1030  2345  YES  YES
a2              1305 A     A    SUA     1030  2345  YES  YES
a3              1307 A     A    SUA     1030  2346  YES  YES
assoc1          1201 A     A    M3UA    2000  1030  YES  YES
assoc2          1205 A     A    M2PA    2048  2048  YES  YES
assoc3          1205 A     B2   M2PA    3000  3000  YES  YES
  2. Enter the rtrv-card command with the location of the card that is hosting the M2PA association that will be changed in this procedure. For this example, enter this command.

    rtrv-card:loc=1205

    This is an example of possible output. 

    
rlghncxa03w 08-04-06 15:17:20 EST EAGLE5 38.0.0
CARD   TYPE      APPL     LSET NAME   LINK SLC LSET NAME   LINK SLC
1205   DCM       IPLIM    e5e6a       A    0   e5e6a       B2   1
                          e5e6a       A3   2
    If the application assigned to the card is IPLIM or IPLIMI, shown in the APPL column, continue the procedure by performing one of these steps.
    • If the open parameter value for the association being changed is yes, continue the procedure with 3.
    • If the open parameter value for the association being changed is no, continue the procedure with 4.

    If the application assigned to the card is IPSG, perform the Changing the Attributes of an IPSG Association procedure.

  3. Change the value of the open parameter to no by specifying the chg-assoc command with the open=no parameter.

    For this example, enter this command.

    chg-assoc:aname=assoc2:open=no

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
  4. Perform one of these actions.
    • If the new link value is not shown in the rtrv-card output in 2, perform the Adding an IPLIMx Signaling Link procedure to provision the signaling link with the card location specified in 2 and the new link value. After the new signaling link has been provisioned, continue the procedure with 8.
    • If the new link value is shown in the rtrv-card output in 2 and in the rtrv-assoc output in 1, this link value cannot be used. Perform the Adding an IPLIMx Signaling Link procedure to provision the signaling link with the card location specified in 2 and the new link value. After the new signaling link has been provisioned, continue the procedure with 8.
    • If the new link value is shown in the rtrv-card output in 2 but not in the rtrv-assoc output in 1, continue the procedure with 5.
  5. Display the status of the signaling link that will be the new link value for the association shown in 2 (using the values in the LOC and LINK columns in the rtrv-card output) by entering the rept-stat-slk command specifying the card location and signaling link.

    For example, enter this command.

    rept-stat-slk:loc=1205:link=a3

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
SLK      LSN         CLLI        PST          SST       AST
1205,A3  e5e6a       ----------- IS-NR        Avail     ----
Command Completed.

    If the primary state (PST) of the signaling link not is OOS-MT and the secondary state (SST) is Unavail, continue the procedure with 6.

    If the primary state (PST) of the signaling link is OOS-MT and the secondary state (SST) is Unavail, continue the procedure with 8.

  6. Deactivate the signaling link shown in 5 using the dact-slk command.

    For example, enter this command.

    dact-slk:loc=1205:link=a3

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 06-10-07 11:11:28 GMT EAGLE5 36.0.0
Deactivate Link message sent to card
  7. Verify the status of the signaling link using the rept-stat-slk command.

    For example, enter this command.

    rept-stat-slk:loc=1205:link=a3

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
SLK      LSN         CLLI        PST          SST       AST
1205,A3  e5e6a       ----------- OOS-MT       Unavail   ----
Command Completed.
  8. Change the association using the chg-assoc command.

    For this example, enter this command.

    chg-assoc:aname=assoc2:link=a3

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;

    If the value of the open parameter was not changed in 3, continue the procedure with 10.

    If the value of the open parameter was changed in 3, continue the procedure with 9.

  9. Change the value of the open parameter to yes by specifying the chg-assoc command with the open=yes parameter.

    For this example, enter this command.

    chg-assoc:aname=assoc2:open=yes

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
  10. Verify the changes using the rtrv-assoc command specifying the association name specified in 8 and 9.

    For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of possible output. 

    
rlghncxa03w 10-07-28 21:14:37 GMT EAGLE5 42.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    gw200.nc-tekelec.com
       ARHOST   ---
       LPORT    2048          RPORT       3000
       ISTRMS   2             OSTRMS      2           BUFSIZE  500
       RMODE    LIN           RMIN        120         RMAX     800
       RTIMES   10            CWMIN       3000        UAPS     10
       OPEN     YES           ALW         NO          RTXTHR   10000
       RHOSTVAL MATCH         M2PATSET    1

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (1300 KB of 1600 KB) on LOC = 1205

    If the state of the signaling link was changed in 6, continue the procedure with 11.

    If the state of the signaling link was not changed in 6, continue the procedure with 13.

  11. Activate the signaling link assigned to the association using the act-slk command.

    For example, enter this command.

    act-slk:loc=1205:link=a3

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 06-10-07 11:11:28 GMT EAGLE5 36.0.0
Activate Link message sent to card
  12. Verify the status of the signaling link using the rept-stat-slk command.

    For example, enter this command.

    rept-stat-slk:loc=1205:link=a3

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
SLK      LSN         CLLI        PST          SST       AST
1205,A3  e5e6a       ----------- IS-NR        Avail     ----
Command Completed.
  13. Back up the new changes, using the chg-db:action=backup:dest=fixed command.

    These messages should appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first. 

    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.
    If you wish to change the other attributes of the M2PA association, perform one of these procedures.

    If you do not wish to change the other attributes of the M2PA association, this procedure is finished.

Figure 3-20 Changing the Link Value of a M2PA Association to another Link Value on the Same IPLIMx Card



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

3.21 Configuring SCTP Retransmission Control for a M2PA Association

This procedure is used to gather the information required to configure the retransmission parameters for M2PA associations assigned to cards running either the IPLIM or IPLIMI applications. Perform the Configuring an IPSG Association for SCTP Retransmission Control procedure to configure the retransmission parameters for M2PA associations assigned to IPSG cards. If any assistance is needed to configure the retransmission parameters for associations, contact unresolvable-reference.html#GUID-1825DD07-2A6B-4648-859A-1258A0F9AC40.

The retransmission parameters are configured using the rmode, rmin, rmax, rtimes, and cwmin parameters of the chg-assoc command.

:rmode – The retransmission mode used when packet loss is detected. The values are rfc or lin.

  • rfc – Standard RFC 2960 algorithm in the retransmission delay doubles after each retransmission. The RFC 2960 standard for congestion control is also used.
  • lin – Oracle's linear retransmission mode where each retransmission timeout value is the same as the initial transmission timeout and only the slow start algorithm is used for congestion control.

:rmin – The minimum value of the calculated retransmission timeout in milliseconds.

:rmax – The maximum value of the calculated retransmission timeout in milliseconds.

Note:

The rmin and rmax parameter values form a range of retransmission values. The value of the rmin parameter must be less than or equal to the rmax parameter value.

:rtimes – The number of times a data retransmission occurs before closing the association.

:cwmin – The minimum size in bytes of the association's congestion window and the initial size in bytes of the congestion window.

The Changing the Attributes of an M2PA Association procedure is used to change the values of these parameters. In addition to using the Changing the Attributes of an M2PA Association procedure, these pass commands are also used in this procedure.

  • ping – tests for the presence of hosts on the network.
  • assocrtt – displays the SCTP round trip times for a specified association. Minimum, maximum, and average times are kept for each open association. The Retransmission Mode (RFC or LIN) and the configured Minimum and Maximum Retransmission Timeout limits are also displayed.
  • sctp – provides a summary list of all SCTP instances.
  • sctp -a <association name> – displays the measurements and information for a specific association.

    Note:

    The values for the minimum and maximum retransmission times in the output from this command are shown in microseconds.

For more information on the pass commands, see Commands User's Guide.

The chg-assoc command contains other optional parameters that can be used to configure an association. These parameters are not shown here because they are not necessary for configuring the SCTP retransmission parameters. These parameters are explained in more detail in the Changing the Attributes of an M2PA Association procedure, or in the and chg-assoc command description in Commands User's Guide.

Canceling the RTRV-ASSOC Command

Because the rtrv-assoc command used in this procedure can output information for a long period of time, the rtrv-assoc command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-assoc command can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-assoc command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-assoc command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-assoc command was entered, from another terminal other that the terminal where the rtrv-assoc command was entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

  1. Display the associations in the database using the rtrv-assoc command.

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
swbel32         1201 A     A    M3UA    1030  2345  YES  YES
a2              1305 A     A    SUA     1030  2345  YES  YES
a3              1307 A     A    SUA     1030  2346  YES  YES
assoc1          1201 A     A    M2PA    2000  1030  YES  YES
  2. Enter the rtrv-card command with the location of the card that is hosting the M2PA association that will be changed in this procedure. For this example, enter this command.

    rtrv-card:loc=1201

    This is an example of possible output. 

    
rlghncxa03w 08-03-06 15:17:20 EST EAGLE5 38.0.0
CARD   TYPE      APPL     LSET NAME   LINK SLC LSET NAME   LINK SLC
1201   DCM       IPLIM    lsn1        A    0

    If the application assigned to the card is IPLIM or IPLIMI, shown in the APPL column, continue the procedure with 3.

    If the application assigned to the card is IPSG, perform the Configuring an IPSG Association for SCTP Retransmission Control procedure.

  3. Display the association that will be changed by entering the rtrv-assoc command with the name of the association. For this example, enter this command.

    rtrv-assoc:aname=assoc1

    This is an example of the possible output. 

    
rlghncxa03w 10-07-28 21:14:37 GMT EAGLE5 42.0.0
 ANAME assoc1
       LOC      1201          IPLNK PORT  A          LINK  A
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    gw100.nc-tekelec.com
       ARHOST   ---
       LPORT    2000          RPORT       1030
       ISTRMS   2             OSTRMS      2           BUFSIZE  400
       RMODE    LIN           RMIN        120         RMAX     800
       RTIMES   10            CWMIN       3000        UAPS     10
       OPEN     YES           ALW         NO          RTXTHR   2000
       RHOSTVAL MATCH         M2PATSET    1

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (1600 KB of 1600 KB) on LOC = 1201
  4. Enter the ping pass command specifying the card location of the local host, shown in 3 , and the name of the remote host assigned to the association being changed, shown in 3 .

    This command is entered several times to obtain the average round trip time. For this example, enter this command.

    pass:loc=1201:cmd=”ping gw100.nc.tekelec.com”

    The following is an example of the possible output 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
PASS: Command sent to card

rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
PING command in progress

rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
PING GW100. NC. TEKELEC. COM (192.1.1.30): 56 data bytes
64 bytes from tekral.nc.tekelec.com (192.1.1.30): icmp_seq=0. time=5. ms
64 bytes from tekral.nc.tekelec.com (192.1.1.30): icmp_seq=1. time=9. ms
64 bytes from tekral.nc.tekelec.com (192.1.1.30): icmp_seq=2. time=14. ms
----tekral PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 5/9/14

PING command complete

    If the SCTP retransmission parameters do not need to be changed, do not perform 5 through 8. This procedure is finished.

  5. Perform the Changing the Attributes of an M2PA Association procedure to change the retransmission parameters of the association based on the results of pinging the remote host.
  6. Enter the assocrtt pass command to display the round trip time data collected after an association is established when an SCTP INIT message is sent and an acknowledgment is received.

    The assocrtt command is entered with the card location from 4 (the card location assigned to the association being changed), and the name of the association being changed. This association must contain the host name used in 4. For this example, enter this command.

    pass:loc=1201:cmd=”assocrtt assoc1”

    The following is an example of the possible output 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
PASS: Command sent to card

rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0

ASSOCRTT: Association round-trip time report (in milliseconds)

Retransmission Configuration
    Retransmission Mode              : LIN
    Minimum RTO: 120
    Maximum RTO: 800

Traffic Round-Trip Times

    Minimum round-trip time          : 5
    Maximum round-trip time          : 120
    Weighted Average round-trip time : 10
    Last recorded round-trip time    : 10

Measured Congested Traffic Round-Trip Times

    Minimum round-trip time          : 0
    Maximum round-trip time          : 0
    Weighted Average round-trip time : 0
    Last recorded round-trip time    : 0
;
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
ASSOCRTT command complete
  7. Enter the sctp -a <association name> pass command to determine if retransmissions have occurred.

    The association name is the association name specified in 6. Specify the card location used in 6. For this example, enter this command.

    pass:loc=1201:cmd=”sctp -a assoc1"

    The following is an example of the possible output 

    
    rlghncxa03w 10-12-28 21:15:37 GMT EAGLE5 43.0.0

    Aname            Local           Local  Remote          Remote
                     IP Address      Port   Address         Port
    Assoc1           192.168.110.12  2222   192.168.112.4   5555
                     192.168.112.12  

             Configuration                         State
        Retransmission Mode = LIN        State = OPEN
Min. Retransmission Timeout = 10000      ULP association id = 18
Max. Retransmission Timeout = 800000     Number of nets = 2
     Max. Number of Retries = 10         Inbound Streams = 1
    Min. Congestion Window = 3000        Outbound Streams = 2
            Inbound Streams = 2
           Outbound Streams = 2
         Checksum Algorithm = crc32c
       Send/Rcv Buffer Size = 204800

                              Nets Data

         IP Address    192.168.112.4      State     Reachable
               Port     7777             Primary     YES
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

         IP Address     192.168.113.5      State     Reachable
               Port     7777             Primary     NO
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

                    Last Net Sent To = 192.168.112.4
                  Last Net Rcvd From = 192.168.112.4
                 Over All Eror Count = 0
                          Peers Rwnd = 13880
                             My Rwnd = 16384
                          Max Window = 16384
                  Initial Seq Number = 24130
             Next Sending Seq Number = 124686
               Last Acked Seq Number = 124669
         Maximum Outbound Char Count = 16384
         Current Outbound Char Count = 2112
            Number Unsent Char Count = 0
           Outbound Data Chunk Count = 16
                       Number Unsent = 0
                Number To Retransmit = 0
  
                  ip datagrams rcvd = 155402
 ip datagrams with data chunks rcvd = 120844
                   data chunks rcvd = 367908
                   data chunks read = 367900
                      dup tsns rcvd = 8
                         sacks rcvd = 38734
                gap ack blocks rcvd = 3
            heartbeat requests rcvd = 135
                heartbeat acks rcvd = 52
            heartbeat requests sent = 52
                  ip datagrams sent = 129254
 ip datagrams with data chunks sent = 73084
                   data chunks sent = 396330
        retransmit data chunks sent = 135
                         sacks sent = 64872
                        send failed = 0
             retransmit timer count = 0
    consecutive retransmit timeouts = 0
RTT between RMIN and RMAX inclusive = 6
              RTT greater than RMAX = 0
              fast retransmit count = 135
                   recv timer count = 0
              heartbeat timer count = 244
                   none left tosend = 0
                none left rwnd gate = 5
                none left cwnd gate = 8

;

    rlghncxa03w 10-12-28 21:15:37 GMT EAGLE5 43.0.0

    SCTP command complete

    
    rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0

    Aname            Local           Local  Remote          Remote
                     IP Address      Port   Address         Port
    Assoc1           192.168.110.12  2222   192.168.112.4   5555
                     192.168.112.12  

             Configuration                         State
        Retransmission Mode = LIN        State = OPEN
Min. Retransmission Timeout = 10         ULP association id = 18
Max. Retransmission Timeout = 800        Number of nets = 2
     Max. Number of Retries = 10         Inbound Streams = 1
    Min. Congestion Window = 3000        Outbound Streams = 2
            Inbound Streams = 2
           Outbound Streams = 2

                              Nets Data

         IP Address    192.168.112.4      State     Reachable
               Port     7777             Primary     YES
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

         IP Address     192.168.113.5      State     Reachable
               Port     7777             Primary     NO
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

                    Last Net Sent To = 192.168.112.4
                  Last Net Rcvd From = 192.168.112.4
                 Over All Eror Count = 0
                          Peers Rwnd = 13880
                             My Rwnd = 16384
                          Max Window = 16384
                  Initial Seq Number = 24130
             Next Sending Seq Number = 124686
               Last Acked Seq Number = 124669
         Maximum Outbound Char Count = 16384
         Current Outbound Char Count = 2112
            Number Unsent Char Count = 0
           Outbound Data Chunk Count = 16
                       Number Unsent = 0
                Number To Retransmit = 0
  
                  ip datagrams rcvd = 155402
 ip datagrams with data chunks rcvd = 120844
                   data chunks rcvd = 367908
                   data chunks read = 367900
                      dup tsns rcvd = 8
                         sacks rcvd = 38734
                gap ack blocks rcvd = 3
            heartbeat requests rcvd = 135
                heartbeat acks rcvd = 52
            heartbeat requests sent = 52
                  ip datagrams sent = 129254
 ip datagrams with data chunks sent = 73084
                   data chunks sent = 396330
        retransmit data chunks sent = 135
                         sacks sent = 64872
                        send failed = 0
             retransmit timer count = 0
    consecutive retransmit timeouts = 0
RTT between RMIN and RMAX inclusive = 6
              RTT greater than RMAX = 0
              fast retransmit count = 135
                   recv timer count = 0
              heartbeat timer count = 244
                   none left tosend = 0
                none left rwnd gate = 5
                none left cwnd gate = 8

    SCTP command complete
  8. Perform the Changing the Attributes of an M2PA Association procedure to change the retransmission parameters of the association based on the results of the outputs of 6 and 7.

    The Weighted Average round-trip time shown in the assocrtt pass command output in 6, and the data retransmission counts shown in the sctp -a pass command output in 7 are used as a guide to determine the appropriate values for the rmode, rmin, rmax, and rtimes parameters. If the retransmission parameters do not have to be adjusted, do not perform this step. This procedure is finished.

Figure 3-21 Configuring the SCTP Retransmission Control for a M2PA Association



3.22 Changing a M2PA Timer Set

This procedure is used to change the values of the M2PA timers in a M2PA timer set using the chg-m2pa-tset command. The M2PA timers are used to control the behavior of the signaling link assigned to an M2PA association (an association containing the M2PA adapter layer - adapter=m2pa) during signaling link alignment and proving, and during times of transmit congestion.

The EAGLE contains 20 M2PA timer sets. One of these timer sets is assigned to an M2PA association using the m2patset parameter of either the ent-assoc or chg-assoc command. If the m2patset parameter is not specified with the ent-assoc command, or with the chg-assoc command if the adapter layer for that association is being changed to M2PA, timer set 1 is automatically assigned to the association.

Caution:

Changing an M2PA timer set may affect the performance of any associations using the timer set being changed.

The chg-m2pa-tset command uses these parameters.

:tset – The M2PA timer set being changed, 1 - 20.

:srctset – The timer values in an existing M2PA timer set can be copied to another M2PA timer set, specified by the tset parameter. The srctset parameter specifies the timer set that is to be copied. If the srctset parameter is specified, no other timer values can be specified, The srctset parameter value cannot be the timer set specified by the tset parameter.

:ver – The M2PA version, either Draft 6 (ver=d6) or RFC (ver=rfc).

Note:

The definitions of timers T1 and T3 for the Draft 6 version are different from the RFC version. The T2 timer applies only to the RFC version. The definitions of timers T4N, T4E, T5, T6, T7, T16, T17 and T18 for are the same for the Draft 6 version and the RFC version.

The timer parameter descriptions and values are shown in Table 3-8.

Table 3-8 M2PA Timers

Timer Draft 6 Timer Name RFC Timer Name Definition Value (in msecs) DRAFT 6 System Default Value (in msecs) RFC System Default Value (in msecs)

:t1

N/A

Ready Timer

The amount of time after proving the M2PA adapter layer waits to receive a Link Status Ready message from the peer.

1000 -

350000

N/A

300000

:t1

Alignment Timer

N/A

The amount of time the M2PA adapter layer waits to receive a Link Status Alignment message from the peer.

1000 -

350000

10000

N/A

:t2 *

N/A

Not Aligned Timer

The the amount of time the M2PA adapter layer waits to receive a Link Status Alignment/Link Status Proving message after sending a Link Status Alignment message. Timer T2 is not used in M2PA Draft 6 timer sets.

5000 -

150000

N/A

20000

:t3

N/A

Alignment Timer

The amount of time the M2PA layer waits to receive a Link Status Alignment message from the peer.

1000 -

60000

N/A

2000

Ready Timer

N/A

The amount of time after proving the M2PA adapter layer waits to receive a Link Status Ready message from the peer.

1000 -

60000

10000

N/A

:t4n

Proving Timer (Normal)

The amount of time the M2PA adapter layer generates Link Status Proving messages during normal proving.

1000 -

70000

10000

30000

:t4e

Proving Timer (Emergency)

The amount of time the M2PA adapter layer generates Link Status Proving messages during emergency proving.

400 - 5000

500

500

:t5

Busy Rate Timer

The amount of time between sending Link Status Busy messages while the link is in-service.

80 - 10000

1000

100

:t6

Remote Congestion Timer

The amount of time that a congested link will remain in service.

1000 - 6000

3000

3000

:t7

Excess Delay in

Acknowledgement

Timer

The maximum amount of time that may pass between when a user data message is transmitted and an acknowledgement for that message is received from the peer. If this timer expires, the link is taken out of service.

200 - 2000

1200

1200

:t16

Proving Rate Timer

The amount of time between sending Link Status Proving messages while the T4N or T4E timer is running.

100 -

500000 **

200000 **

200000 **

:t17

Ready Rate Timer

The amount of time between sending Link Status Ready messages while the T3 timer is running.

100 - 500

250

250

:t18

Processor Outage Rate Timer

The amount of time between sending Link Status Processor Outage messages while the link is in-service.

100 - 10000

1000

1000

msecs - milliseconds

* The T2 Timer can be specified only for the M2PA RFC version.

** The value of the T16 Timer is in microseconds.

The value of any timer parameter not specified with the chg-m2pa-tset command is not changed.

  1. Display the M2PA timer sets in the database by entering the rtrv-m2pa-tset command with the version of the M2PA timer sets you wish to change with the ver parameter.
    To display the M2PA Draft 6 timer values, enter this command.

    rtrv-m2pa-tset:ver=d6

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0

M2PA Draft 6 Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16    T17  T18
1    6000   ------ 5000  20000 500  5000  3000 1000  200000 250  1000
2    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
3    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
4    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
5    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
6    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
7    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
8    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
9    27500  ------ 3850  4859  450  5700  3750 1150  250    375  8750
10   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
11   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
12   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
13   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
14   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
15   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
16   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
17   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
18   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
19   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
20   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000

    To display the M2PARFC timer values, enter this command.

    rtrv-m2pa-tset:ver=rfc

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0

M2PA RFC Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16    T17  T18
1    6000   20000  5000  20000 500  5000  3000 1000  200000 250  1000
1    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
2    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
3    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
4    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
5    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
6    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
7    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
8    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
9    27500  10000  3850  4859  450  5700  3750 1150  250    375  8750
10   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
11   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
12   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
13   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
14   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
15   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
16   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
17   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
18   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
19   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
20   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000

    If the ver parameter is not specified when entering the rtrv-m2pa-tset command, both the Draft 6 and RFC values are displayed. This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0

M2PA Draft 6 Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16    T17  T18
1    6000   ------ 5000  20000 500  5000  3000 1000  200000 250  1000
2    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
3    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
4    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
5    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
6    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
7    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
8    10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
9    27500  ------ 3850  4859  450  5700  3750 1150  250    375  8750
10   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
11   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
12   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
13   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
14   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
15   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
16   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
17   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
18   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
19   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000
20   10000  ------ 10000 10000 500  1000  3000 1200  200000 250  1000

M2PA RFC Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16    T17  T18
1    6000   20000  5000  20000 500  5000  3000 1000  200000 250  1000
2    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
3    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
4    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
5    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
6    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
7    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
8    300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
9    27500  10000  3850  4859  450  5700  3750 1150  250    375  8750
10   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
11   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
12   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
13   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
14   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
15   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
16   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
17   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
18   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
19   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
20   300000 20000  2000  30000 500  100   3000 1200  200000 250  1000
  2. Change the desired timer set with the chg-m2pa-tset command. To change a specific timer set, enter the chg-m2pa-tset command with the tset and ver parameters and the timer parameters you wish to change. For this example, to change the values of the RFC version of timer set 1, enter this command.

    chg-m2pa-tset:tset=1:t1=27500:t2=10000:t3=3850:t4e=450:t4n=45000:t5=5700 :t6=3750:t7=1150:t16=250000:t17=375:t18=8750:ver=rfc

    To change the values of the Draft 6 version of timer set 1, enter this command.

    chg-m2pa-tset:tset=1:t1=27500:t3=3850:t4e=450:t4n=45000:t5=5700 :t6=3750:t7=1150:t16=250000:t17=375:t18=8750:ver=d6

    Note:

    The values for theM2PA timers are shown in Table 3-8.

    To copy an M2PA timer set to another timer set, enter the chg-m2pa-tset command with the tset, ver, and srctset parameters. For this example, to copy the RFC version of timer set 9 to timer set 1, enter this command.

    chg-m2pa-tset:tset=1:srctset=9:ver=rfc

    To copy the Draft 6 version of timer set 9 to timer set 1, enter this command.

    chg-m2pa-tset:tset=1:srctset=9:ver=d6

    Note:

    Thever parameter is optional and does not have to be specified to change theM2PARFC timer values. The default value for thever parameter isrfc. If you wish to change theM2PA Draft 6 timer values, thever=d6 parameter must be specified with thechg-m2pa-tset command.

    When the chg-m2pa-tset command has successfully completed, the following message should appear. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
CHG-M2PA-TSET: MASP A - COMPLTD
  3. Verify the changes by entering the rtrv-m2pa-tset command specifying the timer set and version parameter values specified in 2. For this example, enter one of these commands.

    rtrv-m2pa-tset:tset=1:ver=rfc

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0

M2PA RFC Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16     T17  T18
1    27500  10000  3850  45000 450  5700  3750 1150  250000  375  8750

    rtrv-m2pa-tset:tset=1:ver=d6

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0

M2PA Draft 6 Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16     T17  T18
1    27500  ------ 3850  45000 450  5700  3750 1150  250000  375  8750

    rtrv-m2pa-tset:tset=9:ver=rfc

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0

M2PA RFC Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16     T17  T18
9    27500  10000  3850  45000 450  5700  3750 1150  250000  375  8750

    rtrv-m2pa-tset:tset=9:ver=d6

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0

M2PA Draft 6 Timers (in msec, T16 in microsec)

TSET T1     T2     T3    T4N   T4E  T5    T6   T7    T16     T17  T18
9    27500  ------ 3850  45000 450  5700  3750 1150  250000  375  8750
  4. Back up the new changes, using the chg-db:action=backup:dest=fixed command. These messages should appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-22 Changing an M2PA Timer Set



3.23 Changing the SCTP Checksum Algorithm Option for M2PA Associations

Use this procedure to change the SCTP checksum algorithm, either Adler-32 or CRC-32c, applied to traffic on SCTP associations. The sctpcsum parameter of the chg-sg-opts command is used to change this option. The Adler-32 and CRC-32c checksum algorithms specified in this procedure applies to all the associations that are assigned to all the IP cards running the IPLIM or IPLIMI applications. This option is a system-wide option. To apply this option to associations assigned to cards running the SS7IPGW, IPGWI, or IPSG applications, perform these procedures.

The sctpcsum parameter contains another value, percard, that allows either the Adler-32 or CRC-32c SCTP checksum algorithm to be specified for the all the associations assigned to a specific card. With this option specified, the Adler-32 checksum algorithm can be specified for the associations on one card and the CRC-32c checksum algorithm can be specified for the associations on another card. Setting the sctpcsum parameter to percard changes the SCTP checksum algorithm for the associations assigned to a card to the SCTP checksum algorithm value for that card. The checksum algorithm for individual cards is provisioned by performing the Configuring an IP Card procedure.

Once the SCTP checksum option has been changed, the associations on each IP card need to be reset by changing the open parameter value for each association to no, then back to yes. This ensures that the associations on the IP card are using the new SCTP checksum algorithm.

Canceling the RTRV-ASSOC Command

Because the rtrv-assoc command used in this procedure can output information for a long period of time, the rtrv-assoc command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-assoc command can be canceled.

  • Press the F9 function key on the keyboard at the terminal where the rtrv-assoc command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-assoc command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-assoc command was entered, from another terminal other that the terminal where the rtrv-assoc command was entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

  1. Display the current IP options in the database by entering the rtrv-sg-opts command. The following is an example of the possible output. 
    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
SCTPCSUM:       adler32

    The rtrv-sg-opts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-sg-opts command, see the rtrv-sg-opts command description in Commands User's Guide.

  2. Display the cards in the EAGLE by entering the rtrv-card command. This is an example of the possible output. 
    
rlghncxa03w 13-05-28 09:12:36 GMT EAGLE5 45.0.0
CARD   TYPE      APPL      LSET NAME     LINK SLC LSET NAME     LINK SLC
1101   DSM       VSCCP     
1102   TSM       GLS       
1113   E5MCAP    EOAM
1114   E5TDM-A
1115   E5MCAP    EOAM
1116   E5TDM-B
1117   E5MDAL
1201   LIMDS0    SS7ANSI   sp2           A    0   sp1           B    0
1203   LIMDS0    SS7ANSI   sp3           A    0   
1204   LIMDS0    SS7ANSI   sp3           A    1   
1206   LIMDS0    SS7ANSI   nsp3          A    1   nsp4          B    1    
1301   LIMDS0    SS7ANSI   sp6           A    1   sp7           B    0
1302   LIMDS0    SS7ANSI   sp7           A    1   sp5           B    1
1303   DCM       IPLIM     ipnode1       A    0   ipnode3       B    1
1305   DCM       IPLIM     ipnode4       A    0       
1313   DCM       SS7IPGW   ipgtwy1       A    0   
2101   DCM       SS7IPGW   ipgtwy2       A    0   
2103   DCM       SS7IPGW   ipgtwy3       A    0   
2105   DCM       IPLIM     ipnode1       A1   1   ipnode5       B    2   
2205   DCM       IPLIM     ipnode3       A2   0   ipnode6       B1   2   
2207   DCM       IPLIM     ipnode5       A    0   ipnode4       B3   1   
2213   DCM       IPLIM     ipnode5       A3   1   ipnode3       B2   2   
2301   DCM       IPLIM     ipnode6       A    0   ipnode1       B    2   
2305   DCM       IPLIM     ipnode6       A1   1   ipnode1       B1   3

    Record the card location, shown in the LOC column, and signaling link, shown in the LINK column, information for all cards running the IPLIM or IPLIMI applications.

  3. Change the SCTP checksum option in the database using the chg-sg-opts command. For this example, enter this command.

    chg-sg-opts:sctpcsum=crc32c

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 06-10-28 21:19:37 GMT EAGLE5 36.0.0
CHG-SG-OPTS: MASP A - COMPLTD
    Continue the procedure by performing one of these actions.
    • If the sctpcsum parameter value was changed to either adler32 or crc32c, continue the procedure with 4.
    • If the sctpcsum parameter value was changed to percard, perform the Configuring an IP Card procedure to assign an sctpcsum parameter value to all the cards running the IPLIM or IPLIMI applications. After the Configuring an IP Card procedure has been performed, continue the procedure with 5.
  4. Verify that the SCTP checksum algorithm was changed using the rtrv-sg-opts command. The SCTP checksum algorithm option value is shown in the SCTPCSUM parameter. The following is an example of the possible output. 
    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
SCTPCSUM:       crc32c

    The rtrv-sg-opts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-sg-opts command, see the rtrv-sg-opts command description in Commands User's Guide.

  5. Select one of the IP cards shown in the rtrv-card output in 2 running the IPLIM or IPLIMI applications. Place the signaling links on this card out of service using the dact-slk command. For this example, enter these commands.

    dact-slk:loc=1308:link=a1

    dact-slk:loc=1308:link=b

    dact-slk:loc=1308:link=b2

    When these commands have successfully completed, this message appears. 

    rlghncxa03w 06-10-12 09:12:36 GMT EAGLE5 36.0.0
Deactivate Link message sent to card
  6. Display the IP addresses of the IP links in the database by entering the rtrv-ip-lnk command. The following is an example of the possible output. 
    
rlghncxa03w 08-12-28 21:17:37 GMT EAGLE5 40.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
1202  A    192.1.1.10      255.255.255.0   HALF    10    DIX     NO   NO
1202  B    --------------- --------------- HALF    10    DIX     NO   NO
1205  A    192.1.1.12      255.255.255.0   HALF    10    DIX     NO   NO
1205  B    --------------- --------------- HALF    10    DIX     NO   NO
1207  A    192.1.1.14      255.255.255.0   HALF    10    DIX     NO   NO
1207  B    --------------- --------------- HALF    10    DIX     NO   NO
1303  A    192.1.1.20      255.255.255.0   HALF    10    DIX     NO   NO
1303  B    --------------- --------------- HALF    10    DIX     NO   NO
1305  A    192.1.1.22      255.255.255.0   HALF    10    DIX     NO   NO
1305  B    --------------- --------------- HALF    10    DIX     NO   NO
1308  A    192.1.1.24      255.255.255.0   HALF    10    DIX     NO   NO
1308  B    --------------- --------------- HALF    10    DIX     NO   NO
1315  A    192.1.1.50      255.255.255.0   HALF    10    DIX     NO   NO
1315  B    --------------- --------------- HALF    10    DIX     NO   NO
1317  A    192.1.1.52      255.255.255.0   HALF    10    DIX     NO   NO
1317  B    --------------- --------------- HALF    10    DIX     NO   NO

IP-LNK   table is (16 of 2048) 1% full.
  7. Display the current IP host information in the database by entering the rtrv-ip-host:display=all command. The following is an example of the possible output. 
    
rlghncxa03w 08-12-28 21:17:37 GMT EAGLE5 40.0.0

LOCAL IPADDR    LOCAL HOST
192.1.1.10      IPNODE1-1201
192.1.1.12      IPNODE1-1203
192.1.1.14      IPNODE1-1205
192.1.1.20      IPNODE2-1201
192.1.1.22      IPNODE2-1203
192.1.1.24      IPNODE2-1205
192.1.1.32      KC-HLR2
192.1.1.50      DN-MSC1
192.1.1.52      DN-MSC2

REMOTE IPADDR   REMOTE HOST
150.1.1.5       NCDEPTECONOMIC_DEVELOPMENT. SOUTHEASTERN_COORIDOR_ASHVL. GOV

IP Host table is (10 of 4096) .24% full
  8. Display the associations assigned to the IP card specified in 5, using the rtrv-assoc command with the local host name of the associations assigned to the IP card. To find the local host name of the association, the card location of the IP card is assigned to an IP address in the IP link table (rtrv-ip-lnk output). The IP address is assigned to a hostname in the IP host table (rtrv-ip-host output).

    For this example, the local host name of associations assigned to the IP card 1308 (the card specified in 5) is IPNODE2-1205. Enter this command.

    rtrv-assoc:lhost=ipnode2-1205

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
assoc2          1308 A     A1   M2PA    2187  1025  YES  YES
assoc4          1308 A     B    M2PA    3290  1025  YES  YES
assoc5          1308 A     B2   M2PA    1057  1025  YES  YES

IP Appl Sock/Assoc table is (9 of 4000) 1% full
Assoc Buffer Space Used (600 KB of 3200 KB) on LOC = 1308
  9. Change the value of the open parameter of the associations shown in 8 to no by specifying the chg-assoc command with the open=no parameter. For this example, enter this command.

    chg-assoc:aname=assoc2:open=no

    chg-assoc:aname=assoc4:open=no

    chg-assoc:aname=assoc5:open=no

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
  10. Change the value of the open parameter of the associations changed in 9 to yes by specifying the chg-assoc command with the open=yes parameter. For this example, enter this command.

    chg-assoc:aname=assoc2:open=yes

    chg-assoc:aname=assoc4:open=yes

    chg-assoc:aname=assoc5:open=yes

    When this command has successfully completed, this message should appear. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
  11. Verify the checksum algorithm that is assigned to the associations shown in 10 by entering the sctp -a pass command with the card location of the IP card specified in 5 and the name of the associations specified in 10. For this example, enter this command.

    pass:loc=1308:cmd=”sctp -a assoc2 ”

    The following is an example of the possible output. 

        rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0
    Aname            Local              Local   Primary        Remote
                     IP Address         Port    Address        Port
    assoc2           192.1.1.24         2187    192.168.112.4  1025
                     192.1.1.24  

               Configuration                            State
        Retransmission Mode = LIN          State = OPEN
Min. Retransmission Timeout = 10000        ULP association id = 18
Max. Retransmission Timeout = 800000       Number of nets = 2
     Max. Number of Retries = 10           Inbound Streams = 1
    Min. Congestion Window  = 3000         Outbound Streams = 2
            Inbound Streams = 2
           Outbound Streams = 2
         Checksum Algorithm = crc32c
       Send/Rcv Buffer Size = 204800


                                 Nets Data     

         IP Address     192.168.112.4      State     Reachable
               Port     1025             Primary     YES
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

         IP Address     192.168.112.5      State     Reachable
               Port     7777             Primary     NO
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

                    Last Net Sent To = 192.168.112.4      
                  Last Net Rcvd From = 192.168.112.4      
                 Over All Eror Count = 0
                          Peers Rwnd = 13880
                             My Rwnd = 16384
                          Max Window = 16384
                  Initial Seq Number = 24130
             Next Sending Seq Number = 124686
               Last Acked Seq Number = 124669
         Maximum Outbound Char Count = 16384
         Current Outbound Char Count = 2112
            Number Unsent Char Count = 0
           Outbound Data Chunk Count = 16
                       Number Unsent = 0
                Number To Retransmit = 0


                   ip datagrams rcvd = 155402
  ip datagrams with data chunks rcvd = 120844
                    data chunks rcvd = 367908
                    data chunks read = 367900
                       dup tsns rcvd = 8
                          sacks rcvd = 38734
                 gap ack blocks rcvd = 3
             heartbeat requests rcvd = 135
                 heartbeat acks rcvd = 52
             heartbeat requests sent = 52
                   ip datagrams sent = 129254
  ip datagrams with data chunks sent = 73084
                    data chunks sent = 396330
         retransmit data chunks sent = 135
                          sacks sent = 64872
                         send failed = 0
              retransmit timer count = 0
     consecutive retransmit timeouts = 0
 RTT between RMIN and RMAX inclusive = 6
               RTT greater than RMAX = 0
               fast retransmit count = 135
                    recv timer count = 0
               heartbeat timer count = 244
                    none left tosend = 0
                 none left rwnd gate = 5
                 none left cwnd gate = 8


;

    rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

    SCTP command complete

        rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
    Aname            Local              Local   Primary        Remote
                     IP Address         Port    Address        Port
    assoc2           192.1.1.24         2187    192.168.112.4  1025
                     192.1.1.24  

               Configuration                            State
        Retransmission Mode = LIN          State = OPEN
Min. Retransmission Timeout = 10           ULP association id = 18
Max. Retransmission Timeout = 800          Number of nets = 2
     Max. Number of Retries = 10           Inbound Streams = 1
    Min. Congestion Window  = 3000         Outbound Streams = 2
            Inbound Streams = 2
           Outbound Streams = 2
  Checksum Algorithm = crc32c


                                 Nets Data     

         IP Address     192.168.112.4      State     Reachable
               Port     1025             Primary     YES
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

         IP Address     192.168.112.5      State     Reachable
               Port     7777             Primary     NO
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

                    Last Net Sent To = 192.168.112.4      
                  Last Net Rcvd From = 192.168.112.4      
                 Over All Eror Count = 0
                          Peers Rwnd = 13880
                             My Rwnd = 16384
                          Max Window = 16384
                  Initial Seq Number = 24130
             Next Sending Seq Number = 124686
               Last Acked Seq Number = 124669
         Maximum Outbound Char Count = 16384
         Current Outbound Char Count = 2112
            Number Unsent Char Count = 0
           Outbound Data Chunk Count = 16
                       Number Unsent = 0
                Number To Retransmit = 0


                   ip datagrams rcvd = 155402
  ip datagrams with data chunks rcvd = 120844
                    data chunks rcvd = 367908
                    data chunks read = 367900
                       dup tsns rcvd = 8
                          sacks rcvd = 38734
                 gap ack blocks rcvd = 3
             heartbeat requests rcvd = 135
                 heartbeat acks rcvd = 52
             heartbeat requests sent = 52
                   ip datagrams sent = 129254
  ip datagrams with data chunks sent = 73084
                    data chunks sent = 396330
         retransmit data chunks sent = 135
                          sacks sent = 64872
                         send failed = 0
              retransmit timer count = 0
     consecutive retransmit timeouts = 0
 RTT between RMIN and RMAX inclusive = 6
               RTT greater than RMAX = 0
               fast retransmit count = 135
                    recv timer count = 0
               heartbeat timer count = 244
                    none left tosend = 0
                 none left rwnd gate = 5
                 none left cwnd gate = 8


;

    rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0

    SCTP command complete

    pass:loc=1308:cmd=”sctp -a assoc4 ”

    The following is an example of the possible output. 

        rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0
    Aname            Local              Local   Primary        Remote
                     IP Address         Port    Address        Port
    assoc4           192.1.1.24         3290    192.168.112.4  1025
                     192.1.1.24  

               Configuration                            State
        Retransmission Mode = LIN          State = OPEN
Min. Retransmission Timeout = 10000        ULP association id = 18
Max. Retransmission Timeout = 800000       Number of nets = 2
     Max. Number of Retries = 10           Inbound Streams = 1
    Min. Congestion Window  = 3000         Outbound Streams = 2
            Inbound Streams = 2
           Outbound Streams = 2
         Checksum Algorithm = crc32c
       Send/Rcv Buffer Size = 204800


                                 Nets Data     

         IP Address     192.168.112.4      State     Reachable
               Port     1025             Primary     YES
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

         IP Address     192.168.112.5      State     Reachable
               Port     7777             Primary     NO
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

                    Last Net Sent To = 192.168.112.4      
                  Last Net Rcvd From = 192.168.112.4      
                 Over All Eror Count = 0
                          Peers Rwnd = 13880
                             My Rwnd = 16384
                          Max Window = 16384
                  Initial Seq Number = 24130
             Next Sending Seq Number = 124686
               Last Acked Seq Number = 124669
         Maximum Outbound Char Count = 16384
         Current Outbound Char Count = 2112
            Number Unsent Char Count = 0
           Outbound Data Chunk Count = 16
                       Number Unsent = 0
                Number To Retransmit = 0


                   ip datagrams rcvd = 155402
  ip datagrams with data chunks rcvd = 120844
                    data chunks rcvd = 367908
                    data chunks read = 367900
                       dup tsns rcvd = 8
                          sacks rcvd = 38734
                 gap ack blocks rcvd = 3
             heartbeat requests rcvd = 135
                 heartbeat acks rcvd = 52
             heartbeat requests sent = 52
                   ip datagrams sent = 129254
  ip datagrams with data chunks sent = 73084
                    data chunks sent = 396330
         retransmit data chunks sent = 135
                          sacks sent = 64872
                         send failed = 0
              retransmit timer count = 0
     consecutive retransmit timeouts = 0
 RTT between RMIN and RMAX inclusive = 6
               RTT greater than RMAX = 0
               fast retransmit count = 135
                    recv timer count = 0
               heartbeat timer count = 244
                    none left tosend = 0
                 none left rwnd gate = 5
                 none left cwnd gate = 8


;

    rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

    SCTP command complete

        rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
    Aname            Local              Local   Primary        Remote
                     IP Address         Port    Address        Port
    assoc4           192.1.1.24         3290    192.168.112.4  1025
                     192.1.1.24  

               Configuration                            State
        Retransmission Mode = LIN          State = OPEN
Min. Retransmission Timeout = 10           ULP association id = 18
Max. Retransmission Timeout = 800          Number of nets = 2
     Max. Number of Retries = 10           Inbound Streams = 1
    Min. Congestion Window  = 3000         Outbound Streams = 2
            Inbound Streams = 2
           Outbound Streams = 2
  Checksum Algorithm = crc32c


                                 Nets Data     

         IP Address     192.168.112.4      State     Reachable
               Port     1025             Primary     YES
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

         IP Address     192.168.112.5      State     Reachable
               Port     7777             Primary     NO
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

                    Last Net Sent To = 192.168.112.4      
                  Last Net Rcvd From = 192.168.112.4      
                 Over All Eror Count = 0
                          Peers Rwnd = 13880
                             My Rwnd = 16384
                          Max Window = 16384
                  Initial Seq Number = 24130
             Next Sending Seq Number = 124686
               Last Acked Seq Number = 124669
         Maximum Outbound Char Count = 16384
         Current Outbound Char Count = 2112
            Number Unsent Char Count = 0
           Outbound Data Chunk Count = 16
                       Number Unsent = 0
                Number To Retransmit = 0


                   ip datagrams rcvd = 155402
  ip datagrams with data chunks rcvd = 120844
                    data chunks rcvd = 367908
                    data chunks read = 367900
                       dup tsns rcvd = 8
                          sacks rcvd = 38734
                 gap ack blocks rcvd = 3
             heartbeat requests rcvd = 135
                 heartbeat acks rcvd = 52
             heartbeat requests sent = 52
                   ip datagrams sent = 129254
  ip datagrams with data chunks sent = 73084
                    data chunks sent = 396330
         retransmit data chunks sent = 135
                          sacks sent = 64872
                         send failed = 0
              retransmit timer count = 0
     consecutive retransmit timeouts = 0
 RTT between RMIN and RMAX inclusive = 6
               RTT greater than RMAX = 0
               fast retransmit count = 135
                    recv timer count = 0
               heartbeat timer count = 244
                    none left tosend = 0
                 none left rwnd gate = 5
                 none left cwnd gate = 8


;

    rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0

    SCTP command complete

    pass:loc=1308:cmd=”sctp -a assoc5 ”

    The following is an example of the possible output. 

        rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0
    Aname            Local              Local   Primary        Remote
                     IP Address         Port    Address        Port
    assoc5           192.1.1.24         1057    192.168.112.4  1025
                     192.1.1.24  

               Configuration                            State
        Retransmission Mode = LIN          State = OPEN
Min. Retransmission Timeout = 10000        ULP association id = 18
Max. Retransmission Timeout = 800000       Number of nets = 2
     Max. Number of Retries = 10           Inbound Streams = 1
    Min. Congestion Window  = 3000         Outbound Streams = 2
            Inbound Streams = 2
           Outbound Streams = 2
         Checksum Algorithm = crc32c
       Send/Rcv Buffer Size = 204800


                                 Nets Data     

         IP Address     192.168.112.4      State     Reachable
               Port     1025             Primary     YES
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

         IP Address     192.168.112.5      State     Reachable
               Port     7777             Primary     NO
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

                    Last Net Sent To = 192.168.112.4      
                  Last Net Rcvd From = 192.168.112.4      
                 Over All Eror Count = 0
                          Peers Rwnd = 13880
                             My Rwnd = 16384
                          Max Window = 16384
                  Initial Seq Number = 24130
             Next Sending Seq Number = 124686
               Last Acked Seq Number = 124669
         Maximum Outbound Char Count = 16384
         Current Outbound Char Count = 2112
            Number Unsent Char Count = 0
           Outbound Data Chunk Count = 16
                       Number Unsent = 0
                Number To Retransmit = 0


                   ip datagrams rcvd = 155402
  ip datagrams with data chunks rcvd = 120844
                    data chunks rcvd = 367908
                    data chunks read = 367900
                       dup tsns rcvd = 8
                          sacks rcvd = 38734
                 gap ack blocks rcvd = 3
             heartbeat requests rcvd = 135
                 heartbeat acks rcvd = 52
             heartbeat requests sent = 52
                   ip datagrams sent = 129254
  ip datagrams with data chunks sent = 73084
                    data chunks sent = 396330
         retransmit data chunks sent = 135
                          sacks sent = 64872
                         send failed = 0
              retransmit timer count = 0
     consecutive retransmit timeouts = 0
 RTT between RMIN and RMAX inclusive = 6
               RTT greater than RMAX = 0
               fast retransmit count = 135
                    recv timer count = 0
               heartbeat timer count = 244
                    none left tosend = 0
                 none left rwnd gate = 5
                 none left cwnd gate = 8


;

    rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0

    SCTP command complete

        rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
    Aname            Local              Local   Primary        Remote
                     IP Address         Port    Address        Port
    assoc5           192.1.1.24         1057    192.168.112.4  1025
                     192.1.1.24  

               Configuration                            State
        Retransmission Mode = LIN          State = OPEN
Min. Retransmission Timeout = 10           ULP association id = 18
Max. Retransmission Timeout = 800          Number of nets = 2
     Max. Number of Retries = 10           Inbound Streams = 1
    Min. Congestion Window  = 3000         Outbound Streams = 2
            Inbound Streams = 2
           Outbound Streams = 2
  Checksum Algorithm = crc32c


                                 Nets Data     

         IP Address     192.168.112.4      State     Reachable
               Port     1025             Primary     YES
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

         IP Address     192.168.112.5      State     Reachable
               Port     7777             Primary     NO
                MTU     1500                cwnd     16384
           ssthresh     16384                RTO     120

                    Last Net Sent To = 192.168.112.4      
                  Last Net Rcvd From = 192.168.112.4      
                 Over All Eror Count = 0
                          Peers Rwnd = 13880
                             My Rwnd = 16384
                          Max Window = 16384
                  Initial Seq Number = 24130
             Next Sending Seq Number = 124686
               Last Acked Seq Number = 124669
         Maximum Outbound Char Count = 16384
         Current Outbound Char Count = 2112
            Number Unsent Char Count = 0
           Outbound Data Chunk Count = 16
                       Number Unsent = 0
                Number To Retransmit = 0


                   ip datagrams rcvd = 155402
  ip datagrams with data chunks rcvd = 120844
                    data chunks rcvd = 367908
                    data chunks read = 367900
                       dup tsns rcvd = 8
                          sacks rcvd = 38734
                 gap ack blocks rcvd = 3
             heartbeat requests rcvd = 135
                 heartbeat acks rcvd = 52
             heartbeat requests sent = 52
                   ip datagrams sent = 129254
  ip datagrams with data chunks sent = 73084
                    data chunks sent = 396330
         retransmit data chunks sent = 135
                          sacks sent = 64872
                         send failed = 0
              retransmit timer count = 0
     consecutive retransmit timeouts = 0
 RTT between RMIN and RMAX inclusive = 6
               RTT greater than RMAX = 0
               fast retransmit count = 135
                    recv timer count = 0
               heartbeat timer count = 244
                    none left tosend = 0
                 none left rwnd gate = 5
                 none left cwnd gate = 8


;

    rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0

    SCTP command complete

    If the checksum algorithm shown in any of the associations displayed in this step do not match the checksum algorithm specified in 3, contact the Customer Care Center. Refer to unresolvable-reference.html#GUID-1825DD07-2A6B-4648-859A-1258A0F9AC40 for the contact information.

    If the checksum algorithm shown in all of the associations displayed in this step match the checksum algorithm specified in ietf-m2pa-configuration-procedures1.html, continue the procedure with ietf-m2pa-configuration-procedures1.html.

  12. Put the signaling links that were placed out of service in ietf-m2pa-configuration-procedures1.html back into service using the act-slk command. For example, enter this command.

    act-slk:loc=1308:link=a1

    act-slk:loc=1308:link=b

    act-slk:loc=1308:link=b2

    When these commands have successfully completed, this message appears. 

    
rlghncxa03w 06-10-07 11:11:28 GMT EAGLE5 36.0.0
Activate Link message sent to card
  13. Verify the in-service normal (IS-NR) status of the signaling link by using the rept-stat-slk command and specifying the card location and link values specified in ietf-m2pa-configuration-procedures1.html.

    For example, enter these commands.

    rept-stat-slk:loc=1308:link=a1

    This message should appear. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
SLK      LSN         CLLI        PST          SST       AST
1308,A1  ipnode1     ----------- IS-NR        Avail     ----
Command Completed.

    rept-stat-slk:loc=1308:link=b

    This message should appear. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
SLK      LSN         CLLI        PST          SST       AST
1308,B   ipnode3     ----------- IS-NR        Avail     ----
Command Completed.

    rept-stat-slk:loc=1308:link=b2

    This message should appear. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
SLK      LSN         CLLI        PST          SST       AST
1308,B2  ipnode4     ----------- IS-NR        Avail     ----
Command Completed.
  14. Enter the netstat -p sctp pass command with the card location of the IP card to determine if any errors have occurred. For this example, enter this command.

    pass:loc=1308:cmd=”netstat -p sctp”

    The following is an example of the possible output. 

    rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
ip packets sent...................................... 1474882
        ip packets sent with data chunk.................. 306354
        control chunks (excluding retransmissions)....... 1172759
        ordered data chunks (excluding retransmissions).. 1534350
        unordered data chunks (excluding retransmissions) 0
        user messages fragmented due to MTU.............. 0
        retransmit data chunks sent...................... 4
        sacks sent....................................... 496302
        send failed...................................... 0
    ip packets received.................................. 1816035
        ip packets received with data chunk.............. 989957
        control chunks (excluding duplicates)............ 833141
        ordered data chunks (excluding duplicates)....... 989968
        unordered data chunks (excluding duplicates)..... 0
        user messages reassembled........................ 0
        data chunks read................................. 988601
        duplicate tsns received.......................... 0
        sacks received................................... 153763
        gap ack blocks received.......................... 0
        out of the blue.................................. 4
        with invalid checksum............................ 0
    connections established.............................. 2954
        by upper layer................................... 0
        by remote endpoint............................... 2958
    connections terminated............................... 4
        ungracefully..................................... 2952
        gracefully....................................... 0
    associations dropped due to retransmits.............. 0
    consecutive retransmit timeouts...................... 4
    retransmit timer count............................... 6
    fast retransmit count................................ 0
    heartbeat requests received.......................... 330275
    heartbeat acks received.............................. 340239
    heartbeat requests sent.............................. 340258
    associations supported............................... 50
    milliseconds cookie life at 4-way start-up handshake. 5000
    retransmission attempts allowed at start-up phase.... 8

;

    rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0

    NETSTAT command complete

    If errors are shown in the pass command output, contact the Customer Care Center. Refer to unresolvable-reference.html#GUID-1825DD07-2A6B-4648-859A-1258A0F9AC40 for the contact information.

  15. Repeat ietf-m2pa-configuration-procedures1.html through ietf-m2pa-configuration-procedures1.html to update the other IP cards in the EAGLE running the IPLIM and IPLIMI applications with the new SCTP checksum algorithm.

    If the rtrv-card output in ietf-m2pa-configuration-procedures1.html shows cards running the SS7IPGW, IPGWI, or IPSG applications, continue the procedure with ietf-m2pa-configuration-procedures1.html.

  16. Back up the database by entering the chg-db:action=backup:dest=fixed command. These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.
  17. If the rtrv-card output in ietf-m2pa-configuration-procedures1.html shows cards running the SS7IPGW or IPGWI applications, perform the Changing the SCTP Checksum Algorithm Option for M3UA and SUA Associations procedure.
    If the rtrv-card output in 2 shows cards running the IPSG application, perform these procedures.

    If the rtrv-card output in 2 shows that there are no cards running the SS7IPGW, IPGWI, or IPSG applications, this procedure is finished.

Figure 3-23 Changing the SCTP Checksum Algorithm Option for M2PA Associations



Sheet 1 of 3



Sheet 2 of 3



Sheet 3 of 3

3.24 Turning Off the Large MSU Support for IP Signaling Feature

This procedure is used to turn off the Large MSU Support for IP Signaling feature, using the chg-ctrl-feat command.

The chg-ctrl-feat command uses these parameters:

:partnum – The part number of the Large MSU Support for IP Signaling feature, 893018401.

:status=off – used to turn off the Large MSU Support for IP Signaling feature.

The status of the Large MSU Support for IP Signaling feature must be on and is shown with the rtrv-ctrl-feat command.

Caution:

If the Large MSU Support for IP Signaling feature is turned off, the EAGLE will not process messages with a signaling information field (SIF) that is larger than 272 bytes.
  1. Display the status of the Large MSU Support for IP Signaling feature by entering the rtrv-ctrl-feat:partnum=893018401 command. The following is an example of the possible output. 
    
rlghncxa03w 10-04-28 21:15:37 GMT EAGLE5 42.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Large MSU for IP Sig      893018401  on      ----

The following features have been temporarily enabled:

Feature Name              Partnum    Status  Quantity   Trial Period Left
Zero entries found.

The following features have expired temporary keys:

Feature Name              Partnum
Zero entries found.

    If the status of the Large MSU Support for IP Signaling feature is off, or if the Large MSU Support for IP Signaling feature is not enabled, this procedure cannot be performed.

  2. Turn off the Large MSU Support for IP Signaling feature by entering the chg-ctrl-feat command with the status=off parameter. For example, enter this command.

    chg-ctrl-feat:partnum=893018401:status=off

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
CHG-CTRL-FEAT: MASP B - COMPLTD
  3. Verify that the Large MSU Support for IP Signaling feature has been turned off by using the rtrv-ctrl-feat:partnum=893018401 command. The following is an example of the possible output. 
    
rlghncxa03w 10-04-28 21:15:37 GMT EAGLE5 42.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
Large MSU for IP Sig      893018401  off      ----

The following features have been temporarily enabled:

Feature Name              Partnum    Status  Quantity   Trial Period Left
Zero entries found.

The following features have expired temporary keys:

Feature Name              Partnum
Zero entries found.
  4. Back up the new changes using the chg-db:action=backup:dest=fixed command. These messages should appear, the active Maintenance and Administration Subsystem Processor (MASP) appears first. 
    
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 3-24 Turning Off the Large MSU Support for IP Signaling Feature