1. EAGLE Database Administration - IP7 User's Guide
  2. IETF M3UA and SUA Configuration Procedures

4 IETF M3UA and SUA Configuration Procedures

Chapter 4, IETF M3UA and SUA Configuration Procedures, describes the procedures necessary to configure the components necessary to establish IP connections using M3UA or SUA associations on IPGWx signaling links.

4.1 Adding IETF M3UA and SUA Components

This section describes how to configure the components necessary to establish IP connections using M3UA or SUA associations on IPGWx signaling links. IPGWx signaling links are signaling links assigned to cards running either the SS7IPGW or IPGWI applications. The SS7IPGW application supports point-to-multipoint connectivity for ANSI networks. The IPGWI application supports point-to-multipoint connectivity for ITU networks.

The configuration of these IP connections consists of these items.

  1. Configure the IPGWx card with the Adding an IPGWx Card procedure. Turn the ISUP-over-IP (ipisup) feature with the chg-feat command.

    Note:

    Before turning on the ISUP-over-IP feature (ipisup) feature, make sure you have purchased these features. If you are not sure whether you have purchased the ISUP-over-IP feature, contact your Oracle Sales Representative or Account Representative. Once a feature has been turned on with the chg-feat command, the feature cannot be turned off.
  2. Configure the required destination point codes - see Chapter 2, “Configuring Destination Tables,” in Database Administration - SS7 User's Guide.
  3. Configure the required IPGWx linksets with the Configuring an IPGWx Linkset procedure. If you wish to add a mate IPGWx linkset to another IPGWx linkset, perform the Adding a Mate IPGWx Linkset to another IPGWx Linkset procedure.
  4. Configure the IPGWx signaling links with the Adding an IPGWx Signaling Link procedure. 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 Database Administration - SS7 User's Guide.
  6. IP addresses must be assigned to the IPGWx card configured in step 1 by performing theConfiguring an IP Link procedure. There are other IP link parameters that are assigned to the IPGWx card when the IPGWx card is configured. Default values are assigned to these parameters when the IPGWx card is configured. These values can be displayed by the rtrv-ip-lnk command. These values can be changed by performing theConfiguring 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 theAdding 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 IPGWx signaling links must be either M3UA or SUA associations. The M3UA and SUA associations are configured by performing the Adding an M3UA or SUA Association procedure. M2PA associations that are assigned to IPLIMx signaling links are provisioned with the Adding an M2PA Association procedure inIETF M2PA Configuration Procedures. 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 M3UA or SUA Association procedure and are set to default values. The values of these fields can be displayed using the rtrv-assoc command after theAdding an M3UA or SUA Association procedure is performed. These values can be changed by performing these procedures: Changing the Attributes of a M3UA or SUA Association, Changing the Buffer Size of a M3UA or SUA Association. Only one signaling link can be assigned to an IPGWx card. A maximum of 50 IP connections can be assigned to an IPGWx card.
  11. When an M3UA or SUA association is added to the database, UA parameter set 10 is assigned to the association. There are 10 UA parameter sets that can be assigned to an association, but the UA parameter set assignment can be changed, using the Changing the Attributes of a M3UA or SUA Association procedure. The values assigned to each UA parameter set can be changed, except for UA parameter set 10, using the Changing a UA Parameter Set procedure.
  12. The application server contains a set of one to 16 associations, of which one or more is normally actively processing traffic. Application servers are configured by performing on of these procedures:

    If the associations assigned to application server are M3UA associations, and the open parameter value for these associations is yes, then the same UA parameter set must be assigned to all of the associations in the application server.

  13. Routing keys specify MSU filters for the IP connection. Configure the routing keys with theAdding a Routing Key Containing an Application Server procedure.
  14. An internal point code can be provisioned to provide routing to an IP end office node. Configure the internal point codes by performing the Adding an End Node Internal Point Codeprocedure.
  15. The network appearance field identifies the SS7 network context for the message, for the purpose of logically separating the signaling traffic between the SGP (signaling gateway process) and the application server over a common SCTP (stream control transmission protocol) association. This field is contained in the DATA, DUNA, DAVA, DRST, DAUD, SCON, and DUPU messages. Network appearances are configured by performing the Adding a Network Appearance procedure.
  16. 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.

4.2 Adding an IPGWx Card

This procedure is used to add an IPGWx card to the database using the ent-card command. An IPGWx card is a card that is running either the SS7IPGW or IPGWI applications. Table 4-1shows the cards that can be provisioned in this procedure.

Table 4-1 IPGWx 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 ss7ipgw for ANSI IP network connections or ipgwi 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.

If you have purchased the ISUP-over-IP (ipisup) feature, verify that the ISUP-over-IP feature is turned on (ipisup=on) using the rtrv-feat command. If the appropriate feature is off, turn it on with the chg-feat command. For more information on the ISUP-over-IP feature, refer to section Point-to-Multipoint Connectivity (SS7IPGW and IPGWI).

Note:

Before turning on the ISUP-over-IP feature (ipisup), make sure you have purchased this feature. If you are not sure whether you have purchased the ISUP-over-IP feature, contact your Oracle Sales Representative or Account Representative. Once a feature has been turned on with the chg-feat command, the feature cannot be turned off.

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.

  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-03-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

    If the required unprovisioned card slots (see the Card Slot Selection section) 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, this procedure cannot be performed. There are no available card slots for the new IPGWx 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 Card Slot Selection section). If the card has not been installed, insert the card into the desired card location following the rules described in the Card Slot Selection section.

    Caution:

    If the versions of the flash GPLs on the IP card do not match the flash GPL versions in the database when the IP 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 Unsolicited Alarm and Information Messages before proceeding with this procedure.

    If the ISUP-over-IP feature will be used, continue the procedure with 5.

    If the ISUP-over-IP feature will not be used, continue the procedure with one of these actions.
    • If the card being added in this procedure is not an E5-ENET card, continue the procedure with 12.
    • If the card being added in this procedure is an E5-ENET card, continue the procedure with 7.
  5. Verify the ISUP-over-IP feature is on by entering the rtrv-feat command.

    If the ISUP-over-IP feature is on, the ipisup field is set to on.

    Note:

    The rtrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-feat command, see the rtrv-feat command description in the Commands User's Guide.
    If the ISUP-over-IP feature is on, continue the procedure with one of these actions.
    • If the card being added in this procedure is not an E5-ENET card, continue the procedure with 12.
    • If the card being added in this procedure is an E5-ENET card, continue the procedure with 7.

    If the ISUP-over-IP feature is not on, continue the procedure with 6.

  6. Turn the ISUP-over-IP feature on by entering this command.

    To enable the ISUP-over-IP feature, enter this command.

    chg-feat:ipisup=on

    Note:

    Once the ISUP-over-IP feature is turned on with the chg-feat command, it cannot be turned off.

    Note:

    The ISUP-over-IP feature must be purchased before turning them on. If you are not sure whether you have purchased the ISUP-over-IP feature, contact your Sales Representative or Account Representative.

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

    rlghncxa03w 06-10-12 09:12:36 GMT EAGLE5 36.0.0
CHG-FEAT: MASP A - COMPLTD
    After the ISUP-over-IP feature is turned on, continue the procedure with one of these actions.
    • If the card being added in this procedure is not an E5-ENET card, continue the procedure with 12.
    • If the card being added in this procedure is an E5-ENET card, continue the procedure with 7.
  7. 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 12.

    If 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 12.

  8. 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 the 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 Configuring the MFC Option procedure in Database Administration - System Management User's Guide was performed in this step, continue the procedure with 9.

  9. The Fan feature must be turned on. If the rtrv-feat command in 5 was not performed, 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 6 If 13 was 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 on, continue the procedure with 11.

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

  10. 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
  11. 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 12.

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

  12. Add the card using the ent-card command.

    For this example, enter these commands.

    ent-card:loc=1315:type=dcm:appl=ss7ipgw

    ent-card:loc=1317:type=dcm:appl=ipgwi

    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
  13. Verify the changes using the rtrv-card command with the card location specified in 12.

    For this example, enter these commands.

    rtrv-card:loc=1315

    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
1315   DCM       SS7IPGW

    rtrv-card:loc=1317

    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
1317   DCM       IPGWI
  14. 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.
  15. If you wish to change the quantity of static routing keys in the database, perform the Changing IP Options procedure.

    Otherwise, this procedure is finished.

Figure 4-1 Add an IPGWx Card - Sheet 1 of 3



Note:

Before executing this procedure, make sure you have purchased the ISUP-over-IP feature. If you are not sure whether you have purchased the ISUP-over-IP feature, contact your Sales Representative or Account Representative.

Figure 4-2 Add an IPGWx Card - Sheet 2 of 3



Figure 4-3 Add an IPGWx Card - Sheet 3 of 3



4.3 Configuring an IPGWx Linkset

This procedure is used to configure IPGWx linksets in the EAGLE using the ent-ls or chg-ls commands with these parameters. An IPGWx linkset is a linkset that contains signaling links running either the SS7IPGW or IPGWI applications.

Note:

This procedure is not used to configure a mate IPGWx linkset, with the matelsn and action parameters. To configure a mate IPGWx linkset, perform procedure.

:lsn – The name of the linkset. The linkset name can contain up to 10 characters, with the first character being a letter. However, the SEAS interface supports only eight characters. If this linkset is displayed on the SEAS interface and the linkset name contains more than eight characters, only the first eight characters in the linkset name are shown. If this linkset name contains more than eight characters, and is specified with the linkset commands on the SEAS interface, only the first eight characters can be specified.

:apc/apca/apci/apcn/apcn24 – Adjacent point code – the point code identifying the node that is next to the EAGLE. The adjacent point code can be one of the following types of point codes:

:apc/apca – ANSI point code, ANSI private point code

:apci – ITU-I point code, ITU-I spare point code, ITU-I private point code, ITU-I private spare point code.

:apcn – 14-bit ITU-N point code, 14-bit ITU-N spare point code, 14-bit ITU-N private point code, 14-bit ITU-N private spare point code.

:apcn24 – 24-bit ITU-N point code, 24-bit ITU-N private point code.

Note:

See the “Point Code Formats” section in Database Administration - SS7 User's Guide for a definition of the point code types that are used on the EAGLE and for a definition of the different formats that can be used for ITU national point codes.

Note:

The apc/apca/apci/apcn/apcn24 parameter must be specified with the ent-ls command. Specifying this parameter with the chg-ls command is required only if the adjacent point code of the linkset is being changed.

:lst – The linkset type of the specified linkset - The lst parameter must be specified with the ent-ls command. Specifying this parameter with the chg-ls command is required only if the linkset type of the linkset is being changed.

:ipgwapc – IP Gateway Adjacent Point Code indicator. Specify the ipgwapc=yes parameter to provide SS7 linkset definition compatibility for gateway connections to IP-SCPs. This parameter can be specified only for, and must be specified for, linksets containing signaling links assigned to either the SS7IPGW or IPGWI applications. The default is ipgwapc=no.

Note:

The ipgwapc parameter can be specified only with the ent-ls command.

To provision ISUP-CIC routing keys, the ipgwapc=yes parameter and the IP Gateway ISUP routing feature must be turned on. Verify this with the rtrv-feat command. If the IP Gateway ISUP routing feature is turned on, the ipisup field should be set to on. If the IP Gateway ISUP routing feature is not turned on, enter the chg-feat:ipisup=on command.

Note:

Once the IP Gateway ISUP routing feature is turned on with the chg-feat command, it cannot be turned off.

Note:

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

:iptps – The quantity of IP TPS (transactions per second) that is assigned to the IPGWx linkset, from 100 to 32,000. The total amount of the IP TPS for all IPGWx linksets cannot exceed the total provisioned system TPS value in the rtrv-tps output..

:lsusealm – The linkset’s IPTPS alarm threshold, from 10 to 100 percent of the linkset’s IPTPS. When this threshold is reached, a major alarm (UAM 0115) is generated. When the linkset’s IPTPS falls below this threshold, UAM 0115 is automatically cleared and UAM 0118 is generated.

:slkusealm – The signaling link IPTPS alarm threshold, from 10 to 100 percent of the signaling link’s fair share of the linkset’s IPTPS or from 10 to 100 percent of the IPGWx card’s capacity (4000 TPS). This threshold is reached when the signaling link’s actual usage exceeds the percentage of the signaling link’s fair share of the linkset’s IPTPS or the percentage of the IPGWx card’s capacity.

A signaling link's fair share of linkset’s IPTPS is the linkset’s IPTPS divided by the number of in-service links in the linkset. For example, if the linkset IPTPS is 4000 and there are 4 signaling links in the linkset, all in-service, then the signaling link's fair-share would be 1000 IPTPS (4000/4=1000). Table 4-2 shows this calculation for a linkset with 1, 2, 3 and 4 in-service signaling links.

Table 4-2 Signaling Link Fair Share Example

Number of In-Service Signaling Links Linkset IPTPS Signaling Link Fair Share of the Linkset IPTPS

4

4000

1000

3

4000

1333

2

4000

2000

1

4000

4000

When this threshold is exceeded, a minor alarm (UAM 0116) is generated. When the amount of traffic on the signaling link falls below this threshold, UAM 0116 is automatically cleared and UAM 0119 is generated.

The signaling link IPTPS alarm shows that the linkset IPTPS is set too low for the linkset or that the IPGWx card's capacity has been exceeded. Setting the signaling link IPTPS alarm threshold lower than the linkset IPTPS alarm threshold can give the user an earlier indication that the linkset IPTPS is inadequate or that traffic is not balanced across the links in the linkset.

:multgc – specifies whether multiple group codes (for 14-bit ITU-N point codes) are supported for the linkset. When this parameter value is yes, secondary adjacent point codes whose group codes are different from the adjacent point code of the linkset can be assigned to the linkset. If the parameter value is no, the group code of the secondary adjacent point code must be the same as the group code of the linkset’s adjacent point code. For more information on secondary adjacent point codes, go to the “Configuring an ITU Linkset with a Secondary Adjacent Point Code (SAPC)” procedure in the Database Administration - SS7 User's Guide.

This parameter only applies to linksets whose adjacent point codes are either ITU international point codes or ITU national point codes. All the signaling links in this linkset must be assigned to cards running the IPGWI application. For more information on assigning signaling links to cards running the IPGWI application, go to the Adding an IPGWx Signaling Link procedure.

The ITU duplicate point code feature must be on before this parameter can be specified. Verify this with the rtrv-feat command. If the ITU duplicate point code feature is turned on, the ituduppc field should be set to on. If the ITU duplicate point code feature is not turned on, enter the chg-feat:ituduppc=on command.

Note:

Once the ITU duplicate point code feature is turned on with the chg-feat command, it cannot be turned off.

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

Adding the IPGWx linkset cannot exceed the maximum total provisioned system TPS shown in the rtrv-tps output. An IPGWx linkset uses 4000 TPS.

If adding the IPGWx linkset 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 IPGWx linkset will exceed the maximum total provisioned system TPS, the IPGWx linkset cannot be added unless the amount of available TPS is reduced enough to allow the IPGWx linkset 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.

The adjacent point code (APC) for the linkset must be defined in the database, must be in the SS7 domain and cannot match the point code or capability point code of the EAGLE. The domain of the point code is shown in the DMN field in the output of the rtrv-dstn command. The point code of the EAGLE is shown in the PCA, PCN, PCN24, or PCI fields and the capability point code of the EAGLE are shown in the CPCA, CPCN, CPCN24, or CPCI fields in the output of the rtrv-sid command. An ANSI adjacent point code must be a full point code and cannot be a cluster point code or a network routing point code. The adjacent point code of the linkset cannot be a proxy point code, cannot have a proxy point code assigned to it, and cannot be assigned to another linkset.

If the APC is not in the destination point code table, go to the “Adding a Destination Point Code” procedure in Database Administration - SS7 User's Guide and add the APC to the destination point code table.

For IPGWx linksets, more than one device may be attached to the LAN and have IP connections to the IP card running either the SS7IPGW or IPGWI application. Thus each IPGWx linkset is adjacent to all devices on the LAN (or adjacent to no device on the LAN, depending on your point of view). To provide a scheme allowing this point-to-multipoint connection and maintain consistent SS7 linkset definition rules, a virtual APC is required. This virtual APC is a real SS7 point code that is not used anywhere else in the SS7 network. Virtual APCs assigned to SS7IPGW linksets are ANSI point codes. Virtual APCs assigned to IPGWI linksets are either ITU-I or ITU-N point codes (either 14-bit or 24-bit ITU-N point codes). Virtual point codes can be reused on more than one switch. For example, a mated set of switches, each with two related links, could share two virtual point codes instead of requiring four. DPCs and linksets related to the virtual APC must be defined with the ipgwapc parameter set to yes.

For provisioning of ISUP-CIC routing keys, the ipgwapc=yes parameter and the IP Gateway ISUP routing feature must be turned on. Verify this with the rtrv-feat command. If the IP Gateway ISUP routing feature is turned on, the ipisup field should be set to on. If the IP Gateway ISUP routing feature is not turned on, enter the chg-feat:ipisup=on command.

Note:

Once the IP Gateway ISUP routing feature is turned on with the chg-feat command, it cannot be turned off.

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

Other Optional Parameters

There are other optional parameters that can be used to configure an IPGWx linkset. These parameters are not required for configuring an IPGWx linkset. These parameters are discussed in more detail in Commands User's Guide or in these sections.

Note:

The mtprse, spc/spca/spci/spcn/spcn24, and ppc/ppca/ppci/ppcn/ppcn24 parameters cannot be specified for an IPGWx linkset.

Canceling the RTRV-LS and RTRV-DSTN Commands

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-ls or rtrv-dstn commands were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-ls or rtrv-dstn commands were entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-ls or rtrv-dstn commands were entered, from another terminal other that the terminal where the rtrv-ls or rtrv-dstn 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 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.

    An IPGWx linkset uses 4000 TPS. If configuring the linkset will not exceed the maximum total provisioned system TPS, continue the procedure with 7.

    If configuring the IPGWx linkset will exceed the maximum total provisioned system TPS, continue the procedure by performing one of these actions.
    • If the maximum total provisioned system TPS is 500,000 and you wish to change and the maximum total provisioned system TPS to 1M, 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 1M. After the HIPR2 High Rate Mode feature has been enabled and turned on, continue the procedure with 7.
    • 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 IPGWx linkset will exceed the maximum total provisioned system TPS, the IPGWx linkset cannot be added unless the amount of available TPS is reduced enough to allow the IPGWx linkset 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 4.
      • 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 4.
      • Some ATM high-speed signaling links have to be removed. To perform this action, continue the procedure with 2.
      • An IPLIMx card that contains signaling links has to be removed. To perform this action, continue the procedure with 3.
  2. 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 IPGWx linkset to be added, the IPGWx linkset 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 4.
    • 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 4.
    • An IPLIMx card that contains signaling links has to be removed. To perform this action, continue the procedure with 3.

    If you do not wish to perform other actions to increase the available TPS and the available TPS will allow the IPGWx linkset to be added, continue the procedure with 7.

  3. 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 IPGWx linkset to be added, the IPGWx linkset 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 4.
    • 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 4.
    • Some ATM high-speed signaling links have to be removed. To perform this action, continue the procedure with 2.

    If you do not wish to perform other actions to increase the available TPS and the available TPS will allow the IPGWx linkset to be added, continue the procedure with 7.

  4. 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
ipgwx1105     70%     ----    10000  TX:   3700   4000  10-07-19 09:49:19 
                                    RCV:   3650   4000  10-07-19 09:49:19
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 5.

    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 IPGWx linkset to be added, the IPGWx linkset 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 3.
    • Some ATM high-speed signaling links have to be removed. To perform this action, continue the procedure with 2.

    If you do not wish to perform other actions to increase the available TPS and the available TPS will allow the IPGWx linkset to be added, continue the procedure with 7.

  5. Display the attributes of the linksets shown in 4 by entering the rtrv-ls command with the name of the linkset shown in 4. If an existing IPGWx linkset is being changed in 20, that linkset does not need to be displayed in this step.

    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 (11 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 (11 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 (11 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 (11 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 (11 of 1024) 1% full.
    Perform one or both of these actions as necessary.
    • To change the IPTPS value for any linksets shown in the rtrv-ls output whose IPGWAPC value is yes, continue the procedure with 6.
    • To change the MAXSLKTPS value (and RSVDSLKTPS value if necessary) for any linksets shown in the rtrv-ls output, 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).
    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 3.
    • Some ATM high-speed signaling links have to be removed. To perform this action, continue the procedure with 2.

    If you do not wish to perform other actions to increase the available TPS and the available TPS will allow the IPGWx linkset to be added, continue the procedure with 7.

  6. Reduce the IPTPS values of some or all the IPGWx linksets by entering the chg-ls command with the name of each linkset being changed, shown in 5, and the new IPTPS value. For this example, enter these commands.

    chg-ls:lsn=ipgwx1:iptps=28000

    chg-ls:lsn=ipgwx3:iptps=28000

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

    
rlghncxa03w 10-07-17 16:23:21 GMT  EAGLE5 42.0.0
Link set table is ( 11 of 1024)  1% full
CHG-LS: MASP A - COMPLTD

    If no IPSG linksets are shown in 5, continue the procedure with 7.

    If IPSG linksets are shown in 5, continue the procedure with one of these steps.
    • To change the MAXSLKTPS value (and RSVDSLKTPS value if necessary) for any linksets shown in the rtrv-ls output, 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).
    • If you do not wish to change any IPSG linksets, continue the procedure by performing these actions as required.
      • To remove some IPLIMx cards that contains signaling links, continue the procedure with 3.
      • To remove some ATM high-speed signaling links, continue the procedure with 2.
      • If you do not wish to perform other actions to increase the available TPS and the available TPS will allow the IPGWx linkset to be added, continue the procedure with 7.
  7. Display the current linksets in the database 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
lsgw1105      009-002-003   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 (11 of 1024) 1% full.
    Continue the procedure by performing one of these steps.
    • If the multgc=yes parameter is not being specified for the linkset, continue the procedure by performing one of these steps.
      • If a new linkset is being added, continue the procedure with 12.
      • If an existing linkset is being changed and the APC of the linkset is being changed, continue the procedure with 12.
      • If an existing linkset is being changed and the APC of the linkset is not being changed, continue the procedure with 20.
    • If the multgc=yes parameter will be specified for the linkset and a new linkset is being added, continue the procedure by performing one of these steps. The multgc=yes parameter can be specified only for IPGWx linksets that contain signaling links that are assigned to cards that are running the IPGWI application.
      • If linksets containing ITU-N adjacent point codes with group codes are shown in the rtrv-ls output, continue the procedure with 12.
      • If linksets containing ITU-N adjacent point codes with group codes are not shown in the rtrv-ls output, continue the procedure with 8.
    • If the multgc parameter value for an existing linkset will be changed, continue the procedure by performing one of these steps.
      • If the multgc parameter value is being changed to no, continue the procedure with 10.
      • If the multgc parameter value is being changed to yes, continue the procedure with 8. The multgc=yes parameter can be specified only for IPGWx linksets that contain signaling links that are assigned to cards that are running the IPGWI application.
  8. To specify the multgc=yes parameter with the ent-ls or chg-ls commands, the ITU Duplicate Point Code feature must be on. For the ITU Duplicate Point Code feature to be on, the Multiple Point Code feature must be on. Enter the rtrv-feat command to verify that either of these features are on.

    The entry MPC = on in the rtrv-feat command output shows that the Multiple Point Code feature is on. The entry ITUDUPPC = on in the rtrv-feat command output shows that the ITU Duplicate Point Code feature is 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, see thertrv-feat command description inCommands User's Guide.
    Continue the procedure by performing one of these steps.
    • If the ITU Duplicate Point Code feature is on (ITUDUPPC = on), continue the procedure with 10.
    • If the ITU Duplicate Point Code feature is off (ITUDUPPC = off), continue the procedure with Oracle.
  9. Turn the ITU Duplicate Point Code feature on, and the Multiple Point Code feature if necessary, by entering one of these commands.

    To turn the ITU Duplicate Point Code feature on only.

    chg-feat:ituduppc=on

    To turn both the ITU Duplicate Point Code and Multiple Point Code features on.

    chg-feat:mpc=on:ituduppc=on

    Note:

    Once the ITU Duplicate Point Code and Multiple Point Code features are turned on with thechg-feat command, they cannot be turned off.

    The ITU Duplicate Point Code and Multiple Point Code features must be purchased before you turn either of these features on with the chg-feat command. If you are not sure if you have purchased these features, contact your Oracle Sales Representative or Account Representative.

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

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 37.5.0
CHG-FEAT: MASP A - COMPLTD
    Continue the procedure by performing one of these steps.
    • If a new linkset is being added, continue the procedure with 12.
    • If an existing linkset is being changed and the APC of the linkset is being changed, continue the procedure with 12.
    • If an existing linkset is being changed and the APC of the linkset is not being changed, continue the procedure with 20.
  10. If the multgc parameter value is changed to no, the linkset can contain only one secondary adjacent point code. An ITU international linkset can contain only one 14-bit ITU national secondary adjacent point code. If the ITU international linkset contains more than one 14-bit ITU national secondary adjacent point code, all but one of these 14-bit ITU national secondary adjacent point codes must be removed from the linkset. An ITU national linkset can contain only one ITU international secondary adjacent point code. All 14-bit ITU-N secondary adjacent point codes must be removed from the linkset. All routes to these secondary adjacent point codes must be removed from the database before the secondary adjacent point codes can be removed.

    Display the routes using the secondary adjacent point code being removed from the linkset with the rtrv-rte command, specifying the secondary adjacent point code being removed as the value of the dpc parameter.

    For this example, enter these commands.

    rtrv-rte:dpcn=11213-de

    This is an example of the possible output. 

    
rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 37.5.0
DPCN             ALIASA         ALIASI  LSN        RC    APC
11213-de      -------------- ---------- lsn3       10    11213-de
                                            RTX:No  CLLI=-----------

    rtrv-rte:dpcn=12114-fr

    This is an example of the possible output. 

    
rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 37.5.0
DPCN             ALIASA         ALIASI  LSN        RC    APC
12114-fr      -------------- ---------- lsn3       10    12114-fr
                                            RTX:No  CLLI=-----------

    rtrv-rte:dpcn=12115-uk

    This is an example of the possible output. 

    
rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 37.5.0
DPCN             ALIASA         ALIASI  LSN        RC    APC
12115-uk      -------------- ---------- lsn3       10    12115-uk
                                            RTX:No  CLLI=-----------

    If the secondary adjacent point code is assigned to a route, that route must be removed from the database. Perform the “Removing a Route” procedure in the Database Administration - SS7 User's Guide to remove the route from the database.

  11. Remove the secondary adjacent point codes specified in 10 from the linkset with the chg-ls command with the sapcn and the action=delete parameters. For this example, enter these commands.

    chg-ls:lsn=lsn3:sapcn=11213-de:action=delete

    chg-ls:lsn=lsn3:sapcn=12114-fr:action=delete

    chg-ls:lsn=lsn3:sapcn=12115-uk:action=delete

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

    
rlghncxa03w 06-10-17 16:23:21 GMT  EAGLE5 37.5.0
Link set table is ( 13 of 255)  5% full
CHG-LS: MASP A - COMPLTD
    Continue the procedure by performing one of these steps.
    • If a new linkset is being added, continue the procedure with 12.
    • If an existing linkset is being changed and the APC of the linkset is being changed, continue the procedure with 12.
    • If an existing linkset is being changed and the APC of the linkset is not being changed, continue the procedure with 20.
  12. Display the point code and capability point code of the EAGLE by using the rtrv-sid command.

    This is an example of the possible output. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 37.5.0
PCA              PCI             PCN           CLLI            PCTYPE
001-001-001      1-200-6         13482         rlghncxa03w     OTHER

CPCA
002-002-002       002-002-003       002-002-004      002-002-005
002-002-006       002-002-007       002-002-008      002-002-009
004-002-001       004-003-003       144-212-003

CPCA (LNP)
005-005-002       005-005-004       005-005-005

CPCI
1-001-1           1-001-2           1-001-3          1-001-4

CPCN
02091             02092             02094             02097
02191             02192             11177
  13. Display the destination point codes in the database by entering the rtrv-dstn command. This is an example of the possible output. 
    
rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
Extended Processing Time may be Required

   DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
   001-207-000   ----------- no  --- --------------   --------------   SS7
   001-001-001   ----------- no  --- --------------   --------------   SS7
   001-001-002   ----------- no  --- --------------   --------------   SS7
   001-005-000   ----------- no  --- --------------   --------------   SS7
   001-007-000   ----------- no  --- --------------   --------------   SS7
   008-012-003   ----------- no  --- --------------   --------------   SS7
   003-002-004   ----------- no  --- --------------   --------------   SS7
   009-002-003   ----------- no  --- --------------   --------------   SS7
   010-020-005   ----------- no  --- --------------   --------------   SS7

   DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
   1-207-0       ----------- no  --- --------------   --------------   SS7
   0-015-0       ----------- no  --- --------------   --------------   SS7
   0-017-0       ----------- no  --- --------------   --------------   SS7
   1-011-1       ----------- no  --- --------------   --------------   SS7
   1-011-2       ----------- no  --- --------------   --------------   SS7


Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
    If the new adjacent point code is not shown in the rtrv-dstn output, perform the "Adding a Destination Point Code" procedure in Database Administration - SS7 User's Guide to add the required point code. This point code cannot be a proxy point code (the prx=yes value assigned to the point code) and a proxy point code (a point code value is shown in the PPC column) cannot be assigned to the point code. After the point code has been added, continue the procedure by performing one of these steps.
    • If a new linkset is being added, continue the procedure by performing one of these steps.
      • If you do not wish to use the IP Gateway ISUP routing feature, continue the procedure with 19.
      • If you wish to use the IP Gateway ISUP routing feature, continue the procedure with 17.
    • If an existing linkset is being changed, continue the procedure with 20.

    If the new adjacent point code is shown in the rtrv-dstn output, continue the procedure with 14.

  14. Display the adjacent point code of the new linkset in the destination point code table by using the rtrv-dstn command and specifying the point code. For this example, enter this command.

    rtrv-dstn:dpca=010-020-005

    This is an example of the possible output. 

    
rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0

   DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
   010-020-005   ----------- no  --- --------------   --------------   SS7

   SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   -----------  ----         none   off   none     no     no    none

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full

    This point code cannot be a proxy point code (the prx=yes value assigned to the point code) and a proxy point code (a point code value is shown in the PPC column) cannot be assigned to the point code. If a proxy point code is shown in this step, or if the point code is a proxy point code, choose another point code and repeat this procedure from 12.

  15. The APC of the linkset cannot be the DPC of any exception route. Verify that the adjacent point code of the linkset is not the DPC of any exception route by entering the rtrv-rtx command with the dpc/dpca/dpci/dpcn/dpcn24 parameter. The dpc/dpca/dpci/dpcn/dpcn24 parameter value is the adjacent point code value that will be specified for the linkset.

    For this example, enter this command.

    rtrv-rtx:dpca=010-020-005

    This is an example of the possible output. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 37.5.0
    DPCA          RTX-CRITERIA              LSN        RC    APC

    010-020-005   OPCA
                  007-008-009               ls1305     20    001-005-000
                  008-008-008               ls1307     40    001-007-000

 DESTINATION ENTRIES ALLOCATED:   2000
     FULL DPC(s):                   13
     EXCEPTION DPC(s):               5
     NETWORK DPC(s):                 0
     CLUSTER DPC(s):                 1
     TOTAL DPC(s):                  19
     CAPACITY (% FULL):              1%
 ALIASES ALLOCATED:               12000
     ALIASES USED:                   0
     CAPACITY (% FULL):              0%
 X-LIST ENTRIES ALLOCATED:         500

    If the adjacent point code of the linkset is not the DPC of a route exception table entry, no entries are displayed in the rtrv-rtx output, but a summary of the point code quantities is displayed, as shown in the following output example. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 37.5.0

    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   15
        EXCEPTION DPC(s):               5
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 1
        TOTAL DPC(s):                  21
        CAPACITY (% FULL):              1%
    ALIASES ALLOCATED:               12000
        ALIASES USED:                   0
        CAPACITY (% FULL):              0%
    X-LIST ENTRIES ALLOCATED:         500

    If the point code specified in this step is shown in the DPCA/DPCI/DPCN/ DPCN24 columns in this step, the point code value cannot be used as an adjacent point code unless one of two actions are taken:

    • Choose another adjacent point code value and repeat 12 through 15.
    • Remove all the entries displayed in this step by performing the “Removing a Route Exception Entry” procedure in Database Administration - SS7 User's Guide.
  16. Display any entires in the route table whose DPC value is also the adjacent point code of the new linkset being added in this procedure, or the new adjacent point code of the existing linkset being changed in this procedure. Enter the rtrv-rte command with the dpc/dpca/dpci/dpcn/dpcn24 parameter. The dpc/dpca/dpci/dpcn/dpcn24 parameter value is the adjacent point code value that will be specified for the linkset. For this example, enter this command.

    rtrv-rte:dpca=010-020-005

    This is an example of the possible output. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 37.5.0

   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   010-020-005 ---------- --------------   lsn1       1     003-003-003
                                           lsn2       2     003-003-004
                                               RTX:No  CLLI=-----------

    If the adjacent point code of the linkset is not the DPC of a route, the point code entry is displayed in the rtrv-rte output, but the LSN, RC, and APC columns contain dashes, as shown in the following output example. 

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 37.5.0

   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   002-002-002 ---------- --------------   ---------- --    -----------
                                               RTX:No  CLLI=-----------

    If the point code specified in this step is shown in the DPCA/DPCI/DPCN/ DPCN24 columns in this step, the point code value cannot be used as an adjacent point code unless one of two actions are taken:

    • Choose another adjacent point code value and repeat 12 through 16.
    • Remove all the entries displayed in this step by performing the “Removing a Route” procedure in Database Administration - SS7 User's Guide.
    After this step has been performed, continue the procedure by performing one of these steps.
    • If a new linkset is being added, continue the procedure by performing one of these steps.
      • If you do not wish to use the IP Gateway ISUP routing feature, continue the procedure with 19.
      • If you wish to use the IP Gateway ISUP routing feature, continue the procedure with 17.
    • If an existing linkset is being changed, continue the procedure with 20.
  17. Verify that the IP Gateway ISUP routing feature is on by entering the rtrv-feat command. The entry IPISUP = on in the rtrv-feat command output shows that the IP Gateway ISUP routing feature is 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, see thertrv-feat command description inCommands User's Guide.
    • If the IP Gateway ISUP routing feature is on, continue the procedure with 19.
    • If the IP Gateway ISUP routing feature, continue the procedure with 18.
  18. Turn the IP Gateway ISUP routing feature on by entering this command.

    Note:

    If theIP GatewayISUP routing feature is on (IPISUP = on), continue the procedure with 19.

    chg-feat:ipisup=on

    Note:

    Once theIP GatewayISUP routing feature is turned on with thechg-feat command, it cannot be turned off.

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

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

    
rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 37.5.0
CHG-FEAT: MASP A - COMPLTD
  19. Add the new linkset to the database using the ent-ls command. The new linkset must meet these conditions.

    The name of this linkset , the lsn parameter value, cannot be used by another linkset – the linkset configuration is shown in the output of 7.

    The APC of the new linkset must be in the destination point code table, but cannot be either the EAGLE’s point code or the EAGLE’s capability point code – shown in the outputs of 12, 13, and 14. The adjacent point code can be one of the following types of point codes:

    :apc/apca – ANSI point code, ANSI private point code

    :apci – ITU-I point code, ITU-I spare point code, ITU-I private point code, ITU-I private spare point code.

    :apcn – 14-bit ITU-N point code, 14-bit ITU-N spare point code, 14-bit ITU-N private point code, 14-bit ITU-N private spare point code.

    :apcn24 – 24-bit ITU-N point code, 24-bit ITU-N private point code.

    These parameters and values must also be specified for the IPGWx linkset:

    • ipgwapc=yes
    • lst=<a,b,c,d,e>
    • iptps=<100-32000>

      Note:

      The iptps parameter value must be divisible by 10. The sum of all the linkset IP TPS values, including the value for this linkset, cannot exceed the maximum total provisioned system TPS value shown in thertrv-tps output in 1, or the increased value if the "Activating the HIPR2 High Rate Mode Feature" procedure was performed.
    • The optional parameters lsusealm (the linkset’s IP TPS alarm threshold) and slkusealm (the signaling link IP TPS alarm threshold) can be specified with the ent-ls command. The default value for the lsusealm parameter is 100%, and the default value for the slkusealm parameters is 80%.
    • The multgc=yes parameter can be specified only for IPGWx linksets that will contain signaling links that are assigned to cards that are running the IPGWI application.

    Note:

    There are other optional parameters that can be specified with the ent-ls command, but are not required for an IPGWx linkset.See the Other Optional Parameters section for the procedures that discuss these parameters and their usage.

    For this example, enter this command.

    ent-ls:lsn=lsgw1107:apca=010-020-005:lst=a:ipgwapc=yes:iptps=4000 :lsusealm=70:slkusealm=70

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

    
rlghncxa03w 06-10-17 16:23:21 GMT  EAGLE5 37.5.0
Link set table is ( 14 of 1024)  1% full
ENT-LS: MASP A - COMPLTD

    Continue the procedure with 21.

  20. Change the existing linkset by entering the chg-ls command.

    The name of the linkset that is being changed, specified with the lsn parameter, must be specified. The name of the linkset is shown in the rept-stat-iptps output in 4.

    One of these optional parameters must be specified.

    • The new adjacent point code of the linkset, specified with the apc/apca/apci/apcn/apcn24, if the current adjacent point code of the linkset is being changed.
    • iptps=<100-32000>

      Note:

      The iptps parameter value must be divisible by 10. The sum of all the linkset IP TPS values, including the value for this linkset, cannot exceed the maximum total provisioned system TPS value shown in thertrv-tps output in 1, or the increased value if the "Activating the HIPR2 High Rate Mode Feature" procedure was performed. .
    • The optional parameters lsusealm (the linkset’s IP TPS alarm threshold) and slkusealm (the signaling link IPTPS alarm threshold) can be specified with the chg-ls command.
    • The multgc=yes parameter can be specified only for IPGWx linksets that contain signaling links that are assigned to cards that are running the IPGWI application.

    Note:

    There are other optional parameters that can be specified with the ent-ls command, but are not required for an IPGWx linkset. See the Other Optional Parameters section for the procedures that discuss these parameters and their usage.

    For this example, enter this command.

    chg-ls:lsn=lsgw1105:iptps=14000:lsusealm=70:slkusealm=70

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

    
rlghncxa03w 06-10-17 16:23:21 GMT  EAGLE5 37.5.0
Link set table is ( 14 of 1024)  1% full
CHG-LS: MASP A - COMPLTD
  21. Verify the changes using the rtrv-ls command specifying the linkset name specified in either 19 or 20 with the lsn parameter. For this example, enter these commands.

    rtrv-ls:lsn=lsgw1105

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

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

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 14000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1105 A    0   SS7IPGW

Link set table is ( 14 of 1024)  1% full

    rtrv-ls:lsn=lsgw1107

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

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

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 4000  70     % 70      % CdPA

Link set table is ( 14 of 1024)  1% full
  22. 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 4-4 Configuring an IPGWx Linkset



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

4.4 Adding a Mate IPGWx Linkset to another IPGWx Linkset

This procedure is used to add a mate IPGWx linkset to an existing IPGWx linkset chg-ls command with these parameters.

:lsn – The name of the IPGWx linkset that will contain the mate IPGWx linkset that is being added shown in the rept-stat-iptps or rtrv-ls command outputs. is being added.

:matelsn – The name of the mate IPGWx linkset that is being added.

:action=add – adds the mate IPGWx linkset to the IPGWx linkset specified by the lsn parameter.

An IPGWx linkset is a linkset that contains signaling links assigned to IPGWx cards. IPGWx cards are cards running either the SS7IPGW or IPGWI applications.

The EAGLE allows an IPGWx linkset to contain up to 8 IPGWx signaling links, and as a result, 8 IPGWx cards. This increases the amount of traffic that can be delivered to a single IP node compared to the two-card combined IPGWx linkset deployments used in previous releases. An IPGWx linkset containing up to 8 IPGWx signaling links is the preferred method of configuring IPGWx linksets (see the Configuring an IPGWx Linkset procedure). This method is required if more than two IPGWx signaling links are to be used in the linkset.

To provide backward compatibility with pre-existing two-card combined IPGWx linkset deployments, the EAGLE also provides for a mate IPGWx linkset. A mate IPGWx linkset consists of one IPGWx linkset assigned to another IPGWx linkset using the matelsn parameter of the chg-ls command. To assign a mate IPGWx linkset to another IPGWx linkset, both linksets can contain no more than one signaling link. While mate IPGWx linksets can be configured using this procedure, the preferred method of configuring two-card IPGWx deployments is to configure a two-link non-mated linkset using the Configuring an IPGWx Linkset procedure.

Each linkset in the mated pair must either contain no mate linksets, or can reference the other linkset in the mated pair. For example, to assign linkset LSN2 to IPGWx linkset LSN1 as a mate linkset, linkset LSN1 cannot contain any mate linksets. Linkset LSN2 can have linkset LSN1 as a mate, otherwise linkset LSN2 cannot have any mate linksets assigned to it.

The mate linkset name is displayed in the rtrv-ls:lsn=<linkset name> command output. If either linkset contains more than one signaling link, all but one of the signaling links must be removed from these linksets or other linksets must be chosen. Perform the Removing an IPGWx Signaling Linkprocedure to remove any signaling links from the linkset. If new linksets must be configured for this procedure, perform the Configuring an IPGWx Linkset procedure.

Before a mate IPGWx linkset can be added to an IPGWx linkset, the card containing the IPGWx signaling link assigned to the linkset being changed, and the signaling link assigned to that card must be placed out of service.

The network type of the adjacent point code of the mate IPGWx linkset must be the same type as the linkset the mate is assigned to. For example, if a mate IPGWx linkset is assigned to an IPGWx linkset with an ITU-I adjacent point code, the mate IPGWx linkset must have an ITU-I adjacent point code.

Other Optional Parameters

There are other optional parameters that can be used to configure a linkset. These parameters are not required for configuring an IPGWx linkset. These parameters are discussed in more detail in Commands User's Guide or in these sections.
  1. Display the system-wide IP TPS usage report, and the IPGWx linksets, by entering the rept-stat-iptps command. 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
lsgw1101      80%     ----     6000  TX:   5100     5500  05-02-10 11:40:04
                                    RCV:   5100     5500  05-02-10 11:40:04
lsgw1103      80%     ----     6000  TX:   5200     5500  05-02-10 11:40:04
                                    RCV:   5200     5500  05-02-10 11:40:04
lsgw1105      80%     ----    14000  TX:   7300     7450  05-02-10 11:40:04
                                    RCV:   7300     7450  05-02-10 11:40:04
lsgw1107      70%      ----    4000  TX:   3200     3500  05-02-10 11:40:04
                                    RCV:   3200     3500  05-02-10 11:40:04 
--------------------------------------------------------------------------

Command Completed.

    If linksets are displayed in this step, continue the procedure 2.

    If no linksets are displayed in this step, perform the Configuring an IPGWx Linkset to create two IPGWx linksets. After the IPGWx linksets have been created, continue the procedure with 14.

  2. Display the linkset that is being changed by entering the rtrv-ls command with a linkset name shown in the rept-stat-iptps output in 1. For this example, enter this command.

    rtrv-ls:lsn=lsgw1103

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

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

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1103 A    0   SS7IPGW

Link set table is ( 14 of 1024)  1% full

    To assign a mate IPGWx linkset to this linkset, this linkset cannot contain more than one signaling link.

    If this linkset does not contain more than one signaling link, and the linkset that will be the mate IPGWx linkset is shown in the rept-stat-iptps output in 1, continue the procedure with 3.

    If this linkset does not contain more than one signaling link, and the linkset that will be the mate IPGWx linkset is not shown in the rept-stat-iptps output in 1, continue the procedure with 5.

    If this linkset contains more than one signaling link, and you wish to add the mate IPGWx linkset to this linkset, perform the Removing an IPGWx Signaling Link procedure to remove all but one of the signaling links in the linkset. After the signaling links have been removed, perform one of these actions.
    • If the linkset that will be the mate IPGWx linkset is shown in the rept-stat-iptps output in 1, continue the procedure with 3.
    • If the linkset that will be the mate IPGWx linkset is not shown in the rept-stat-iptps output in 1, perform the Configuring an IPGWx Linkset procedure to add the linkset that will be the mate IPGWx linkset. After the linkset has been added, continue the procedure with 5.
    If this linkset contains more than one signaling link, and you do not wish to add the mate IPGWx linkset to this linkset, perform one of these actions.
    • If wish to use another linkset shown in the rept-stat-iptps output in 1, repeat this step with a linkset shown in the rept-stat-iptps output in 1.
    • Perform the Configuring an IPGWx Linkset procedure to add the new IPGWx linkset that the mate IPGWx linkset will be assigned to. After the linkset has been added, if the linkset that will be the mate IPGWx linkset is shown in the rept-stat-iptps output in 1, continue the procedure with 3. If the linkset that will be the mate IPGWx linkset is not shown in the rept-stat-iptps output in 1, perform the Configuring an IPGWx Linkset procedure to add the new IPGWx linkset that will be the mate IPGWx linkset. After the mate IPGWx linkset has been added, continue the procedure with 14
  3. Display the mate linkset from the IPGWx linksets shown in the rept-stat-iptps output in 1.

    For this example, enter this command.

    rtrv-ls:lsn=lsgw1107

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

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

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1107 A    0   SS7IPGW

Link set table is ( 14 of 1024)  1% full
  4. To use the linkset shown in 3 as a mate, the network type of the adjacent point code of the linkset shown in 3 must be the same as the network type of the linkset shown in 2. The linkset shown in 3 must not have more than one signaling link assigned to it.

    If the linkset contains more than one signaling link, all but one of these signaling links must be removed from the linkset. Perform the Removing an IPGWx Signaling Link procedure to remove these signaling links.

    If you do not wish to change this linkset, or if the network type of the adjacent point codes of both linksets are not the same, either choose another linkset from the rept-stat-iptps output in 1, and repeat 3, and 4 if necessary, or perform the Configuring an IPGWx Linkset procedure and add a new linkset. Continue the procedure with 5.

    If the network types of the adjacent point codes of both linksets are the same, and the mate linkset contains no more than one signaling link, do not perform the actions in this step. Continue the procedure with 5.

  5. Display the status of the card containing the signaling link assigned to the linkset being changed by entering the rept-stat-card command with the card location shown in the LOC field in the rtrv-ls output in 2. For this example, enter this command.

    Note:

    If the linkset that the mate linkset is being added to has no signaling links (see thertrv-ls output in2), continue the procedure with14.

    rept-stat-card:loc=1103

    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
1103  114-000-000  DCM     SS7IPGW   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              lsgw1103      -----------
Command Completed.
  6. Display the status of the signaling link assigned to the card shown in 5 by entering the rept-stat-slk command with the card location used in 5 and the link=a parameter. For this example, enter this command.

    Note:

    If the status of the card shown inPST field in therept-stat-card output in5isOOS-MT-DSBLD, continue the procedure with14.

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

    This is an example of the possible output. 

    
rlghncxa03w 08-04-27 17:00:36 GMT EAGLE5 38.0.0
SLK      LSN         CLLI        PST          SST       AST
1103,A   lsgw1103    ----------- IS-NR        Avail     -----
  ALARM STATUS       = No Alarms.
  UNAVAIL REASON     = NA
Command Completed.

    If the status of the signaling link is out-of-service maintenance disabled (OOS-MT-DSBLD), continue the procedure with 14.

    If the status of the signaling link is not out-of-service maintenance disabled (OOS-MT-DSBLD), any in-service IP connections on the signaling link must be placed out of service. Continue the procedure by performing one of these steps.
    • The recommended method is to have the far end node place these IPconnections out of service. Have the far-end node for the signaling link shown in this step place the M3UA or SUA associations in either the ASP-INACTIVE or ASP-DOWN state. After the IP connections have been placed out of service, continue the procedure with 12.
    • If you do not wish to have the far end node place these IP connections out of service, continue the procedure with 7.
  7. Display the IP link associated with the card that the signaling link shown in 6 is assigned to by entering the rtrv-ip-lnk command with the card location shown in 6. For this example, enter this command.

    rtrv-ip-lnk:loc=1103

    The following is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:14:37 GMT EAGLE5 38.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
1103  A    192.1.1.10      255.255.255.128 HALF    10    802.3   NO   NO
1103  B    --------------- --------------- HALF    10    DIX     NO   NO
  8. Display the IP host information associated with the IP link by entering the rtrv-ip-host command with the IP address shown in 7. For this example, enter this command.

    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_1103

IP Host table is (11 of 4096) .26% full
  9. Display the association associated with the local host name shown in 8 by entering the rtrv-assoccommand.

    For this example, enter this command.

    rtrv-assoc:lhost=ipnode1_1103

    The following 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          1103 A     A    M3UA    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 = 1103
  10. Change the alw parameter values in the association shown in 9 using the chg-assoc command with the alw=no parameters, as necessary.

    Note:

    If theopen andalw parameter values of the association shown in9areno, continue the procedure with11.

    chg-assoc:aname=assoc2:alw=no

    Caution:

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

    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

    Repeat this step for all associations shown in 9.

  11. Change the open parameter values in the association shown in 9 using the chg-assoc command with the open=no parameters, as necessary.

    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

    Repeat this step for all associations shown in 9.

  12. Deactivate the signaling link assigned to the IP card using the dact-slk command. For example, enter this command.

    dact-slk:loc=1103: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 08-04-12 09:12:36 GMT EAGLE5 38.0.0
Deactivate Link message sent to card.
  13. Inhibit the IP card using the inh-card command. For example, enter this command.

    inh-card:loc=1103

    This message should appear. 

    
rlghncxa03w 08-04-28 21:18:37 GMT EAGLE5 38.0.0
Card has been inhibited.
  14. Change the linkset shown in 2 by entering the chg-ls command with the matelsn and action=add parameters.

    For this example, enter this command.

    chg-ls:lsn=lsgw1103:matelsn=lsgw1107:action=add

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

    
rlghncxa03w 08-04-17 16:23:21 GMT  EAGLE5 38.0.0
Link set table is ( 14 of 1024)  1% full
CHG-LS: MASP A - COMPLTD
  15. Verify the changes using the rtrv-ls command specifying the linkset name specified in 14 with the lsn parameter. For this example, enter this command.

    rtrv-ls:lsn=lsgw1103

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

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

           IPGWAPC  MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes      lsgw1107   10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1103 A    0   SS7IPGW

Link set table is ( 14 of 1024)  1% full

    If the linkset shown in this step does not have a signaling link assigned to it, or if the dact-slk command in 12 was not performed, continue the procedure with 20.

  16. Allow the IP card that was inhibited in 13 using the alw-card command. For example, enter this command.

    alw-card:loc=1103

    This message should appear. 

    rlghncxa03w 08-04-28 21:21:37 GMT EAGLE5 38.0.0
Card has been allowed.
  17. Activate the signaling link from 12 using the act-slk command. For example, enter this command.

    act-slk:loc=1103:link=a

    The output confirms the activation. 

    rlghncxa03w 08-04-07 11:11:28 GMT EAGLE5 38.0.0
Activate Link message sent to card

    If 10 and 11 were not performed, continue the procedure with 19.

  18. Change the open and alw parameter values for all the associations changed in 10 or 11 using the chg-assoc command with the open=yes and alw=yes parameters.

    chg-assoc:aname=assoc1:open=yes:alw=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
  19. Have the far-end node for the signaling link shown in 15 place the IP connections on the signaling link into service by placing the M3UAor SUA associations in the ASP-ACTIVE state.
  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.

Figure 4-5 Adding a Mate IPGWx Linkset to another IPGWx Linkset



Sheet 1 of 6



Sheet 2 of 6



Sheet 3 of 6



Sheet 4 of 6



Sheet 5 of 6



Sheet 6 of 6

4.5 Adding an IPGWx Signaling Link

This procedure is used to add an IPGWx signaling link to the database using the ent-slk command with 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 SS7IPGW or IPGWI 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.

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 – see "Adding a Shelf" in the Database Administration - System Management User's Guide.
  • Card – see Adding an IPGWx Card
  • Destination Point Code – see “Adding a Destination Point Code” in the Database Administration - SS7 User's Guide.
  • Linkset – see Configuring an IPGWx Linkset.

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 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 (        7 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 current signaling link configuration using the rtrv-slk command. 
    
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 B    lsa1         0  LIMDS0   1    56000  BASIC ---  -----
1203 B    lsa2         0  LIMDS0   1    56000  BASIC ---  -----
1207 A    lsn1207a     0  LIMDS0   1    56000  BASIC ---  -----
1207 B    lsn1207b     0  LIMDS0   1    56000  BASIC ---  -----

SLK table is (4 of 1200) 1% full.
  3. Display the current linkset configuration using the rtrv-ls command.

    This is an example of the possible output. 

    
rlghncxa03w 08-04-10 11:43:04 GMT EAGLE5 38.0.0

                                 L3T SLT              GWS GWS GWS
LSN          APCA   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
e1e2         001-207-000   none  1   1   no  B   6    off off off no    off
ls1305       000-005-000   none  1   1   no  A   1    off off off no    off
ls1307       000-007-000   none  1   1   no  A   1    off off off no    off
e1m1s1       001-001-001   none  1   1   no  A   7    off off off no    off
e1m1s2       001-001-002   none  1   1   no  A   7    off off off no    off

                                 L3T SLT              GWS GWS GWS
LSN          APCI   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
e1e2i        1-207-0       none  1   1   no  B   4    off off off ---   on
ls1315       0-015-0       none  1   1   no  A   1    off off off ---   off
ls1317       0-017-0       none  1   1   no  A   1    off off off ---   on
e1m2s1       1-011-1       none  1   1   no  A   7    off off off ---   off
e1m2s2       1-011-2       none  1   1   no  A   7    off off off ---   off

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

    If the required linkset is not in the database, perform the Configuring an IPGWx Linkset to add the linkset to the database.

    If you plan to use a linkset shown in this step, continue the procedure with 4.

    If a new linkset is being added in this step, continue the procedure with 5.

  4. 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=lsnipgw

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

           CLLI         TFATCABMLQ  MTPRSE  ASL8  SLSRSB  MULTGC  ITUTFR
           -----------  1           no      ---   1       yes     off

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1317 A     0  IPGWI

           SAPCI
           1-10-1

           SAPCN
           1234-aa
           1235-bb
           1200-zz

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

    Linksets containing IPGWx signaling links can contain only IPGWx signaling links.

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

    This is an example of the possible output. 

    
rlghncxa03w 09-10-28 09:12:36 GMT EAGLE5 41.0.0
CARD   TYPE      APPL      LSET NAME     LINK SLC LSET NAME     LINK SLC
1102   TSM       GLS        
1113   GSPM      EOAM
1114   TDM-A
1115   GSPM      EOAM
1116   TDM-B
1117   MDAL
1201   LIMDS0    SS7ANSI   lsa1          B    0
1202   LIMDS0    SS7ANSI   
1203   LIMDS0    SS7ANSI   lsa2          B    0
1204   LIMDS0    SS7ANSI   
1205   LIMDS0    SS7ANSI   lsa3          A    0   
1206   LIMDS0    SS7ANSI   
1207   LIMDS0    SS7ANSI   lsn1207a      A    0   lsn1207b      B    0
1208   LIMDS0    SS7ANSI   
1212   LIMDS0    SS7ANSI   
1213   LIMDS0    SS7ANSI   
1214   LIMDS0    SS7ANSI   lsn1214a      A    0   lsa3          B    1
1215   LIMDS0    SS7ANSI   
1301   LIMDS0    ATMANSI   
1302   LIMATM    ATMANSI   
1304   LIMDS0    SS7ANSI   
1305   LIMATM    ATMANSI   
1308   LIMDS0    SS7ANSI   
1311   LIMDS0    SS7ANSI   
1313   LIMDS0    SS7ANSI   
1318   LIMATM    ATMANSI

    If the required card is not in the database, perform the Adding an IPGWx Card procedure and add the IP 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 beIPGWI.

    Note:

    If theIPGWx linkset contains anyIPGWx signaling links, continue the procedure with7.
  6. If you wish to assign an IPGWx signaling link to a linkset contains no signaling links, but the IPGWAPC value is no, perform the “Removing a Linkset Containing SS7 Signaling Links” procedure in the Database Administration - SS7 User's Guide and remove the linkset, then perform the Configuring an IPGWx Linkset procedure and re-enter the new linkset with the ipgwapc=yes parameter. Continue the procedure with 10.
  7. If the desired linkset, shown in the rtrv-ls output in 4, has a mate IPGWx linkset assigned, or is the mate to another IPGWx linkset, the desired linkset can contain only one signaling link.

    If the desired linkset does not have a mate IPGWx linkset assigned, or is not the mate of another IPGWx linkset, the desired linkset can contain up to 8 IPGWx signaling links. No other signaling link types can be in an IPGWx linkset.

    If you wish to assign more than one IPGWx signaling link to an IPGWx linkset that has a mate linkset assigned, the mate to this linkset must be removed. Perform the Removing a Mate IPGWx Linkset from another IPGWx Linkset procedure and remove the mate linkset from the linkset you wish to assign the IPGWx signaling link to. If you do not wish to use this linkset, perform the Configuring an IPGWx Linkset procedure and add a new IPGWx linkset.

    If the desired IPGWx linkset does not have a mate assigned, continue the procedure with 9.

    If the desired linkset has a mate linkset assigned, and contains an IPGWx signaling link, perform the Configuring an IPGWx Linkset procedure and add a new IPGWx linkset. Continue the procedure with 10.

  8. If you wish to assign more than one IPGWx signaling link to an IPGWx linkset that is a mate to another IPGWx linkset, this linkset must be removed from the other linkset as a mate.

    To verify if the linkset you wish to use is the mate of another IPGWx linkset, enter the rept-stat-iptps command to display the names of all the IPGWx linksets. 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
lsgw1101      80%     ----     6000  TX:   5100     5500  05-02-10 11:40:04
                                    RCV:   5100     5500  05-02-10 11:40:04
lsgw1103      80%     ----     6000  TX:   5200     5500  05-02-10 11:40:04
                                    RCV:   5200     5500  05-02-10 11:40:04
lsgw1105      80%     ----    14000  TX:   7300     7450  05-02-10 11:40:04
                                    RCV:   7300     7450  05-02-10 11:40:04
lsgw1107      70%      ----    4000  TX:   3200     3500  05-02-10 11:40:04
                                    RCV:   3200     3500  05-02-10 11:40:04 
--------------------------------------------------------------------------

Command Completed.
  9. Enter the rtrv-ls:lsn=<IPGWx linkset name from the rept-stat-iptps output> to verify if the desired linkset is the mate of another IPGWx linkset.

    For this example, enter this command.

    rtrv-ls:lsn=lsgw1103

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

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

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     lsgw1107   10000 70     % 70      % CdPA

            LOC  LINK SLC TYPE
            1103 A    0   SS7IPGW

 Link set table is ( 14 of 1024)  1% full

    If the name of the linkset you wish to use is not shown in the MATELSN field of the rtrv-ls output, repeat this step until all the IPGWx linksets have been displayed, or until a linkset has been found that has the linkset you wish to use assigned as a mate. If the linkset you wish to use is not the mate of another IPGWx linkset, continue the procedure with 10.

    If the name of the linkset you wish to use is shown in the MATELSN field of the rtrv-ls output, perform the Removing a Mate IPGWx Linkset from another IPGWx Linkset procedure to remove this linkset from the other linkset as a mate. Then continue the procedure with 10.

    If the desired linkset is the mate of another IPGWx linkset, and you do not wish to use this linkset, perform the Configuring an IPGWx Linkset procedure and add a new IPGWx linkset. Then continue the procedure with 10.

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

    Table 4-3 IPGWx Signaling Link Parameter Combinations

    IPGWx Signaling Link
    :loc = location of the IP card with one of these applications: SS7IPGW or IPGWI; and the DCM card type. (See Note 6)
    :link = A
    :lsn = linkset name (See Notes 1, 2, 3, 4, and 5)
    :slc = 0 - 15 (See Notes 4 and 5)
    Notes:

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

    2. The ipgwapc=yes parameter must be assigned to the linkset.

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

    4. A linkset can contain only one signaling link assigned to the SS7IPGW or IPGWI applications if the linkset contains a mate IPGWx linkset, or is the mate of an IPGWx linkset.

    5. If the linkset does not have a mate IPGWx linkset assigned to it, or is not the mate of an IPGWx linkset, the linkset can contain up to 8 signaling links assigned to the SS7IPGW or IPGWI applications.

    For this example, enter these commands.

    ent-slk:loc=2207:link=a:lsn=lsnlp3:slc=0

    ent-slk:loc=2211:link=a:lsn=lsnlp4:slc=0

    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.
  11. Verify the changes using the rtrv-slk command with the card location and link parameter values specified in 10.

    rtrv-slk:loc=2207:link=a

    This is an example of the possible output. 

    
rlghncxa03w 07-05-19 21:17:04 GMT EAGLE5 37.0.0
LOC  LINK LSN          SLC TYPE
2207 A    lsnlp3        0  SS7IPGW

    rtrv-slk:loc=2211:link=a

    This is an example of the possible output. 

    
rlghncxa03w 07-05-19 21:17:04 GMT EAGLE5 37.0.0
LOC  LINK LSN          SLC TYPE
2211 A    lsnlp4        0  IPGWI
  12. If any cards contain the first signaling link on a card, those cards must be brought into service with the rst-card command, specifying the location of the card.
    For this example, enter these commands.

    rst-card:loc=2207

    rst-card:loc=2211

    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.
  13. 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=2207:link=a

    act-slk:loc=2211: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
  14. Check the status of the signaling links added in 10 using the rept-stat-slk command with the card location and link parameter values specified in 10. 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=2207: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
2207,A   lsnlp3    ----------- IS-NR        Avail     ----
  ALARM STATUS       = 
  UNAVAIL REASON     =

    rept-stat-slk:loc=2211: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
2211,A   lsnlp4    ----------- IS-NR        Avail     ----
  ALARM STATUS       = 
  UNAVAIL REASON     =
  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 4-6 Adding an IPGWx Signaling Link



Sheet 1 of 6



Sheet 2 of 6



Sheet 3 of 6



Sheet 4 of 6



Sheet 5 of 6



Sheet 6 of 6

4.6 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 4-4 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 4-4). 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 4-4 for the valid input values for the submask and ipaddr parameter combinations.

Table 4-4 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.

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) 1% 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 IPGWx 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
1201  A    nc001         0  SS7IPGW
  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     SS7IPGW   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     SS7IPGW   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 with 13 .

    For this example, enter this command.

    rtrv-ip-card:loc=1201

    This is an example of the possible output. 

    
rlghncxa03w 08-06-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 4-4) will be specified for theipaddr parameter in14, continue the procedure with 13 .

    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    M3UA    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     SS7IPGW   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 4-7 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

4.7 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 4-8 Adding an IP Host



4.8 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 4-4). 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
1201  A    nc001         0  SS7IPGW
  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), go to 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     SS7IPGW   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), go to 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     SS7IPGW   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 M3UA and SUA Associations procedure to change the sctpcsum parameter value to percard. After the Changing the SCTP Checksum Algorithm Option for M3UA and SUA 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     SS7IPGW   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 4-9 Configuring an IP Card



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

4.9 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 2048 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 4-5 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 4-6 for the valid input values for the submask and dest parameter combinations.

Table 4-6 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 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 IPGWx Card to add the card to the database.

    Perform the Configuring an IP Card 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 4-6) 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-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 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 4-10 Adding an IP Route



Sheet 1 of 2



Sheet 2 of 2

4.10 Adding an M3UA or SUA Association

This procedure is used to configure M3UA or SUA associations using the ent-assoc command. The combination of a local host, local SCTP port, remote host and remote SCTP port defines an association. M3UA and SUA associations are assigned to cards running either the SS7IPGW or IPGWI applications (IPGWx 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. The value for the link parameter for M3UA or SUA associations is A.

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, either m3ua or sua. The adapter parameter is optional. The default value for the adapter parameter is m3ua.

:alhost – The alternate local host name.

The adapter=m2pa and m2patset parameters can be used only when configuring M2PA associations. Perform the Adding an M2PA Association or Adding an IPSG M2PA Association procedures to configure M2PA associations.

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 a M3UA or SUA Association procedure.

These fields and their default values are shown in Table 4-7.

Table 4-7 M3UA and SUA 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

bufsize=16 rtxthr=0 rhostval=relaxed  

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

The size of the buffers on the E5-ENET card is 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 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 M3UA or SUA 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 M3UA or SUA association.

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

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 signaling link being assigned to the association must be in service. This state is shown in the rept-stat-slk output with the entries IS-NR in the PST field and Avail 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.

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 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
assoc3          1203 A     A1   M2PA    2048  1030  NO   NO
    Perform one of these actions.
    • If SUA associations are assigned to the desired IP link (shown by the entries in the CARD LOC and IPLNK PORT columns for an association whose ADAPTER value is SUA in the rtrv-assoc output), continue the procedure with 5.
    • If M3UA associations are assigned to the desired IP link (shown by the entries in the CARD LOC and IPLNK PORT columns for an association whose ADAPTER value is M3UA 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 M3UA 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=1201

    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
1201 A    lsn1        0   SS7IPGW

    If the value in the TYPE column is either SS7IPGW or IPGWI, continue the procedure with 5.

    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 M3UA association, perform the Adding an IPSG M3UA Association procedure.

    If you do not wish to use this card to configure an M3UA 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 IPGWx card and IP link for the new 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 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. 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.

    Note:

    If a newIP host was added in 4, continue the procedure with6.

    rtrv-assoc:lhost="IPNODE2-1305"

    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
a2              1305 A     A    SUA     1030  2345  YES  YES 

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1305

    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 M3UA or SUA association is 16.

    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 M3UA or SUA Association procedure.

  6. Add the associations using the ent-assoc command. For this example, enter these commands.

    ent-assoc:aname=assoc1:lhost=gw105.nc.tekelec.com:lport=1030: rhost=gw100.nc.tekelec.com:rport=1030:adapter=m3ua:link=a

    These are the rules that apply to adding M3UA or SUA associations that are assigned to IPGWx signaling links.
    • The B Ethernet interface can be used with E5-ENET cards.
    • Each local host on an IPGWx card can contain a maximum of 50 connections (association – application server assignments).
    • The EAGLE can contain a maximum of 4000 connections (association – application server assignments).
    • 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 M3UA or SUA 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 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 default value for the adapter parameter is m3ua.
    • The port parameter can be used in place of the link parameter to specify the signaling link assigned to the association.

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

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

    Note:

    If the association added in step 6 is not being activated in this procedure, skip step 7 and go to step 8.
  7. Activate the association added in 6 by entering the chg-assoc command with the association name specified in 6 and the open=yes and alw=yes parameters. For example, enter this command.

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

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

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD
  8. Verify the changes using the rtrv-assoc command specifying the association name specified in 6 and 7. For this example, enter these commands.

    rtrv-assoc:aname=assoc1

    This is an example of possible output. 

    
rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc1
      LOC      1305          IPLNK PORT  A          LINK  A
      ADAPTER  M3UA          VER         M3UA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    1030          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   0
      RHOSTVAL RELAXED

IP Appl Sock table is (5 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1305
  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 4-11 Adding an IPGWx M3UA or SUA Association



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

4.11 Adding a New Association to a New Application Server

This procedure is used create a new application server and assign a new association to the application server using the ent-as command.

The ent-as command uses these parameters:

:asname – The name of the new application server. The name of the application server can contain up to 15 alphanumeric characters, with the first character being an alphabetic character. Application server names are not case sensitive.

:aname – The name of the association being assigned to the application server.

The maximum number SCTP association to application server assignments that can be hosted by an IPGWx card (referenced by the lhost parameter of the association) is 50. For example, the IPGWx card currently contains 38 SCTP association to application server assignments. The SCTP association to application server assignments could be one SCTP association assigned to 38 application servers, two SCTP associations assigned to 19 application servers, or any combination of SCTP associations assigned to application servers that add up to 38. The SCTP association to application server assignments can be verified with the rtrv-assoc:lhost=<local host name> and rtrv-as:aname=<association name> commands.

Table 4-8 Examples of IPGWx Card Provisioning Limits

Number of Associations hosted by the IPGWx card Number of Application Servers each Association is Assigned to * Total Association - Application Server Assignments maintained by the IPGWx card

1

50

50

50

1

50

25

1

50

25

2

50

0

0

50

38

1

38

19

2

38

* The EAGLE can contain a maximum of 250 application servers.

The open parameter of the association must be set to no before the association can be assigned to the application server. This can be verified with the rtrv-assoc command.

M2PA associations (adapter=m2pa) cannot be assigned to application servers. Only M3UA (adapter=m3ua) and SUA (adapter=sua) associations can be assigned to application servers. This can be verified in the ADAPTER field in the rtrv-assoc output.

The application server recovery timer (the tr parameter of the chg-as command) for the application server is set by default to 10 milliseconds when an application server is added. The traffic mode (the mode parameter of the chg-as command) for the application server is set by default to LOADSHARE when an application server is added. Perform the Changing an Application Server procedure to change these parameter values.

Canceling the RTRV-AS and RTRV-ASSOC Commands

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-as or rtrv-assoc commands were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-as or rtrv-assoc commands were entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-as or rtrv-assoc commands were entered, from another terminal other that the terminal where the rtrv-as or rtrv-assoc 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 application servers in the database using the rtrv-as command. This is an example of possible output. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   10      a2
                                      a3
                                      assoc1

as2               OVERRIDE    10      assoc7
as3               OVERRIDE    10      swbel32

AS table is (3 of 250) 1% full.
  2. 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     2000  2345  YES  YES
a3              1307 A     A    SUA     3000  3000  YES  YES
assoc1          1305 A     A    SUA     4000  1030  YES  YES
assoc7          1311 A     A    SUA     2500  2000  YES  YES
  3. Display the IP host names 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      GW105. NC. TEKELEC. 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

REMOTE IPADDR   REMOTE HOST
150.1.1.5       NCDEPTECONOMIC_DEVELOPMENT. SOUTHEASTERN_COORIDOR_ASHVL. GOV

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

    If the IP host name for the new association is not shown in the LOCAL HOST column of the rtrv-ip-host output, add the IP host name by performing the Adding an IP Host procedure. After the IP host has been added, continue the procedure with 7.

    If the IP host name for the new association is shown in the LOCAL HOST column of the rtrv-ip-host output, continue the procedure with 4.

  4. 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.
  5. Enter the rtrv-card command with the location of the card, from the rtrv-ip-lnk output in 4, that will host the association that will be assigned to the application server. For this example, enter this command.

    rtrv-card:loc=1205

    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
1205   DCM       SS7IPGW  lsn1        A    0

    If the application assigned to the card is SS7IPGW or IPGWI, shown in the APPL column, continue the procedure with 6.

    If the application assigned to the card is IPSG, the host assigned to this card cannot be used for the association that will be assigned to the application server. Repeat this procedure from 3 and choose another IP host.

  6. Display the associations assigned to the local host value that will be assigned to the association being configured in this procedure by entering the rtrv-assoc command with the lhost parameter. 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
a2              1205 A     A    SUA     2000  2048  YES  YES
a3              1205 A     A    SUA     3000  3000  YES  YES

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (32 KB of 3200 KB) on LOC = 1205
  7. Display the application servers that the associations shown in 6 are assigned to by entering rtrv-as command with the names of the associations shown in 6. For this example, enter these commands.

    rtrv-as:aname=a2

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:14:37 GMT EAGLE5 36.0.0
AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   2000    a2
AS Table is (3 of 250) 1% full

    rtrv-as:aname=a3

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:14:37 GMT EAGLE5 36.0.0
AS Name           Mode        Tr ms   Association Names
as2               LOADSHARE   2000    a3
AS Table is (3 of 250) 2% full

    The maximum number of SCTP association to application server assignments that can be hosted by an IPGWx card (referenced by the lhost parameter of the association) is 50.

    If the number of SCTP association to application server assignments is less than 50, continue the procedure with 8.

    If the number of SCTP association to application server assignments is 50, the local host value cannot be used in this procedure.

    Repeat this procedure from 3 and select another local IP host from the rtrv-ip-host output or perform the Adding an IP Host procedure to add a new local IP host. After the new local IP host name as been added, continue the procedure with 8.

  8. Add the new association by performing the Adding an M3UA or SUA Association procedure.

    The open parameter value for this association must be set to no.

    These are the rules that apply to the association and the application server.
    1. M2PA associations cannot be assigned to an application server.
    2. If the application server is being added in this procedure will be assigned to a routing key containing an rcontext parameter value, the adapter parameter value for the association assigned to this application server can be either M3UA or SUA.
    3. If the application server is being added in this procedure will be assigned to a routing key that does not contain an rcontext parameter value, the adapter parameter value for the association assigned to this application server must be M3UA.
    4. SUA associations and their corresponding application server, can be assigned to only these types of routing keys.
      • Full routing key – DPC/SI=3/SSN
      • Partial routing key – DPC/SI=3
      • Partial routing key – DPC only
      • Partial routing key – SI=3 only
      • Default routing key.
      • The routing key containing the application server with the SUA associations must have an rcontext value assigned to it. If the new application server will not be assigned to one of these types of routing keys, the adapter parameter value of the associations assigned to the application server must be M3UA.
    5. 5. The application of the card containing the signaling link assigned to the association is either SS7IPGW or IPGWI.
  9. Assign the new association to the new application server and add the new application server to the database using the ent-as command. For this example, enter this command

    ent-as:asname=as4:aname=assoc10

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

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ENT-AS:  MASP A - COMPLTD;
  10. Verify the changes using the rtrv-as command with the application server name and association name specified in 9. For this example, enter this command.

    rtrv-as:asname=as4:aname=assoc10

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
AS Name           Mode        Tr ms   Association Names
as4               LOADSHARE   10      assoc10

AS table is (4 of 250) 1% full.

    Note:

    If you do not wish to change theopen parameter value of the association specified in9, continue the procedure with12.
  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=assoc10: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. 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 4-12 Adding a New Association to a New Application Server



Sheet 1 of 3



Sheet 2 of 3



Sheet 3 of 3

4.12 Adding an Existing Association to a New Application Server

This procedure is used create a new application server and assign an existing association to the application server using the ent-as command.

The ent-as command uses these parameters:

:asname – The name of the new application server. The name of the application server can contain up to 15 alphanumeric characters, with the first character being an alphabetic character. Application server names are not case sensitive.

:aname – The name of the association being assigned to the application server.

The maximum number SCTP association to application server assignments that can be hosted by an IPGWx card (referenced by the lhost parameter of the association) is 50. For example, the IPGWx card currently contains 38 SCTP association to application server assignments. The SCTP association to application server assignments could be one SCTP association assigned to 38 application servers, two SCTP associations assigned to 19 application servers, or any combination of SCTP associations assigned to application servers that add up to 38. The SCTP association to application server assignments can be verified with the rtrv-assoc:lhost=<local host name> and rtrv-as:aname=<association name> commands.

Table 4-9 Examples of IPGWx Card Provisioning Limits

Number of Associations hosted by the IPGWx card Number of Application Servers each Association is Assigned to * Total Association - Application Server Assignments maintained by the IPGWx card
1 50 50
50 1 50
25 1 50
25 2 50
0 0 50
38 1 38
19 2 38
* The EAGLE can contain a maximum of 250 application servers.

The open parameter of the association must be set to no before the association can be assigned to the application server. This can be verified with the rtrv-assoc command.

M2PA associations (adapter=m2pa) cannot be assigned to application servers. Only M3UA (adapter=m3ua) and SUA (adapter=sua) associations can be assigned to application servers. This can be verified in the ADAPTER field in the rtrv-assoc output.

The application server recovery timer (the tr parameter of the chg-as command) for the application server is set by default to 10 milliseconds when an application server is added. The traffic mode (the mode parameter of the chg-as command) for the application server is set by default to LOADSHARE when an application server is added. Perform the Changing an Application Server procedure to change these parameter values.

Canceling the RTRV-AS and RTRV-ASSOC Commands

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-as or rtrv-assoc commands were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-as or rtrv-assoc commands were entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-as or rtrv-assoc commands were entered, from another terminal other that the terminal where the rtrv-as or rtrv-assoc 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 application servers in the database using the rtrv-as command.

    This is an example of possible output. 

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

AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   10      a2
                                      a3
                                      assoc1

as2               OVERRIDE    10      assoc7
as3               OVERRIDE    10      swbel32

AS table is (3 of 250) 1% full.

    Note:

    If the association being added to the application server is not shown in the rtrv-as output in 1, continue the procedure with 3.
  2. Display the associations in the database using the rtrv-assoc command and specifying the association name shown in the rtrv-as output in 1.

    For this example, enter this command.

    rtrv-assoc:aname=assoc1

    This is an example of possible output. 

    rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc1
      LOC      1305          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw102.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    4000          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as1

IP Appl Sock table is (6 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1305

    If the association does not meet the requirements shown in 8, repeat this step with another association shown in 1, or continue the procedure with 3.

    If the association does meet the requirements shown in 8, continue the procedure with 5.

  3. Display the associations in the database using the rtrv-assoc command with the display=all parameter.

    This is an example of possible output. 

    rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0

ANAME swbel32
      LOC      1201          IPLNK PORT  A          LINK  A
      ADAPTER  M3UA          VER         M3UA RFC
      LHOST    gw101.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.ncd-economic-development.southeastern-corridor-ash.gov
      ARHOST   ---
      LPORT    1030          RPORT       2345
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as3

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

ANAME a2
      LOC      1305          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw102.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    2000          RPORT       2345
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as1

IP Appl Sock table is (6 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1305

ANAME a3
      LOC      1307          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw103.nc.tekelec.com
      ALHOST   ---
      RHOST    gw106.nc.tekelec.com
      ARHOST   ---
      LPORT    3000          RPORT       2346
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES

      as1

IP Appl Sock table is (6 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1307

ANAME assoc1
      LOC      1305          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw102.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    4000          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as1

IP Appl Sock table is (6 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1305

ANAME assoc7
      LOC      1311          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    2500          RPORT       2000
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as2

IP Appl Sock table is (6 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1311

    If the desired association is shown in the rtrv-assoc output, see 8 for the rules that apply to the association and the new application server, continue the procedure with 4.

    If the desired association is not shown in the rtrv-assoc output, perform the Adding a New Association to a New Application Server procedure to add a new association to a new application server.

  4. Enter the rtrv-card command with the location of the card, from the rtrv-assoc output in 3, that contains the association that will be assigned to the application server. 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       SS7IPGW  lsn1        A    0

    If the application assigned to the card is SS7IPGW or IPGWI, shown in the APPL column, continue the procedure with 5.

    If the application assigned to the card is IPSG, the association assigned to this card cannot be assigned to the application server. Repeat this procedure from 3 and choose another association.

  5. Display the associations assigned to the local IP host value specified in 2 or 3 by entering the rtrv-assoc command with the lhost parameter.

    For this example, enter this command.

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

    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
assoc1          1305 A     A    SUA     4000  1030  YES  YES

IP Appl Sock/Assoc table is (5 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 3200 KB) on LOC = 1305
  6. Display the application servers that the associations shown in 5 are assigned to by entering rtrv-as command with the names of the associations shown in 5.

    For this example, enter this command.

    rtrv-as:aname=assoc1

    This is an example of the possible output. 

    rlghncxa03w 06-10-28 21:14:37 GMT EAGLE5 36.0.0
AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE    10     assoc1
AS Table is (3 of 250) 1% full

    The maximum number of SCTP association to application server assignments that can be hosted by an IPGWx card (referenced by the lhost parameter of the association) is 50.

    If the number of SCTP association to application server assignments is less than 50, continue the procedure with 7.

    If the number of SCTP association to application server assignments is 50, the association shown in either 2 or 3 cannot be used in this procedure. Go back to 1 and choose another association to assign to the new application server.

    Note:

    If the value of theopen parameter of the association being assigned to the application server in5 isno, continue the procedure with8.
  7. 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=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;
  8. Add the application server to the database with the name of the association shown in either 2 or 3 using the ent-as command.
    These are the rules that apply to the association and the application server.
    • M2PA associations cannot be assigned to an application server.
    • If the application server is being added in this procedure will be assigned to a routing key containing an rcontext parameter value, the adapter parameter value for the association assigned to this application server can be either M3UA or SUA.
    • If the application server is being added in this procedure will be assigned to a routing key that does not contain an rcontext parameter value, the adapter parameter value for the association assigned to this application server must be M3UA.
    • SUA associations and their corresponding application server, can be assigned to only these types of routing keys.
      • Full routing key – DPC/SI=3/SSN
      • Partial routing key – DPC/SI=3
      • Partial routing key – DPC only
      • Partial routing key – SI=3 only
      • Default routing key.
      • The routing key containing the application server with the SUA associations must have an rcontext value assigned to it. If the new application server will not be assigned to one of these types of routing keys, the adapter parameter value of the associations assigned to the application server must be M3UA.

    For this example, enter this command.

    ent-as:asname=as4:aname=assoc1

    This is an example of the possible outputs. 

    rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ENT-AS:  MASP A - COMPLTD;
  9. Verify the changes using the rtrv-as command with the application server name specified in 8.

    For this example, enter this command.

    rtrv-as:asname=as4

    This is an example of the possible output. 

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

AS Name           Mode        Tr ms   Association Names
as4               LOADSHARE   10      assoc1

AS table is (4 of 250) 1% full.

    Note:

    If you do not wish to change the open parameter value of the association specified in 8, continue the procedure with 11.
  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=assoc1: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. 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 4-13 Add an Existing Association to a New Application Server - Sheet 1 of 4



Figure 4-14 Add an Existing Association to a New Application Server - Sheet 2 of 4



Figure 4-15 Add an Existing Association to a New Application Server - Sheet 3 of 4



Figure 4-16 Add an Existing Association to a New Application Server - Sheet 4 of 4



4.13 Adding a New Association to an Existing Application Server

This procedure is used assign a new association to an existing application server using the ent-as command.

The ent-as command uses these parameters:

:asname – The name of the new application server.

:aname – The name of the association being assigned to the application server.

The maximum number SCTP association to application server assignments that can be hosted by an IPGWx card (referenced by the lhost parameter of the association) is 50. For example, the IPGWx card currently contains 38 SCTP association to application server assignments. The SCTP association to application server assignments could be one SCTP association assigned to 38 application servers, two SCTP associations assigned to 19 application servers, or any combination of SCTP associations assigned to application servers that add up to 38. The SCTP association to application server assignments can be verified with the rtrv-assoc:lhost=<local host name> and rtrv-as:aname=<association name> commands.

Table 4-10 Examples of IPGWx Card Provisioning Limits

Number of Associations hosted by the IPGWx card Number of Application Servers each Association is Assigned to * Total Association - Application Server Assignments maintained by the IPGWx card

1

50

50

50

1

50

25

1

50

25

2

50

0

0

50

38

1

38

19

2

38

* The EAGLE can contain a maximum of 250 application servers.

A maximum of 16 associations can be assigned to an application server.

The open parameter of the association must be set to no before the association can be assigned to the application server. This can be verified with the rtrv-assoc command.

M2PA associations (adapter=m2pa) cannot be assigned to application servers. Only M3UA (adapter=m3ua) and SUA (adapter=sua) associations can be assigned to application servers. This can be verified in the ADAPTER field in the rtrv-assoc output.

The application running on the card hosting the association that will be assigned to the application server must be the same as the application running on the cards hosting the other associations assigned to the application server.

Canceling the RTRV-AS and RTRV-ASSOC Commands

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-as or rtrv-assoc commands were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-as or rtrv-assoc commands were entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-as or rtrv-assoc commands were entered, from another terminal other that the terminal where the rtrv-as or rtrv-assoc 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 application servers in the database using the rtrv-as command.
    This is an example of possible output. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   10      assoc1
                                      assoc2
                                      assoc3
                                      assoc5
                                      assoc6

as2               OVERRIDE    10      assoc7

AS table is (2 of 250) 1% full.
  2. Display the application server that the new association will be added to by entering the rtrv-as command with the name of the application server.
    For this example, enter this command.

    rtrv-as:asname=as2

    This is an example of possible output. 

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

AS Name           Mode        Tr ms   Association Names
as2               OVERRIDE    10      assoc7

AS table is (2 of 250) 1% full.

    A maximum of 16 associations can be assigned to an application server. If the application server displayed in this step contains less than 16 associations, continue the procedure with 3.

    If the application server displayed in this step contains 16 associations, either select another application server to use in this procedure and repeat this step, or perform the Adding a New Association to a New Application Server procedure to add the new association to a new application server.

  3. Display the one of the associations assigned to the application server shown in 2 using the rtrv-assoc command and specifying the association name shown in the rtrv-as output from 2. For this example, enter this command.

    rtrv-assoc:aname=assoc7

    This is an example of possible output. 

    
rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc7
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    1030          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED
      
      ASNAMES
      as2

IP Appl Sock table is (7 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1203

    The adapter parameter value of all the associations assigned to an application server must be the same. This step identifies the adapter value of the associations assigned to the application server. The application running on the card hosting the new association must be the same as the application on the cards hosting the associations assigned to the application server.

  4. Display the signaling link assigned to the card, shown in 3 by entering the rtrv-slk command with the card location of the signaling link shown in 3. For this example, enter this command.

    rtrv-slk:loc=1203

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:19:37 GMT EAGLE5 36.0.0
LOC  LINK LSN         SLC TYPE
1203 A    lsn5         1  SS7IPGW

    The application running on the card is shown in the TYPE column of the rtrv-slk output.

    For this example, the new association must be assigned to a card running the SS7IPGW application.

    If the local host value shown in 3 will be assigned to the new association, continue the procedure with 8.

    If another local host value will be assigned to the new association, perform 5.

  5. Display the IP host names 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 44.0.0

LOCAL IPADDR    LOCAL HOST
192.1.1.10      IPNODE1-1201
192.1.1.12      GW105. NC. TEKELEC. 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

REMOTE IPADDR   REMOTE HOST
150.1.1.5       NCDEPTECONOMIC_DEVELOPMENT. SOUTHEASTERN_COORIDOR_ASHVL. GOV

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

    If the local IP host name for the new association is not shown in the LOCAL HOST column of the rtrv-ip-host output, add the new IP host name by performing the Adding an IP Host procedure. The new local IP host must be assigned to a card running the application shown in 4.

    After the new local IP host has been added, continue the procedure with 9.

    If the local IP host name for the new association is shown in the LOCAL HOST column of the rtrv-ip-host output, continue the procedure with 8.

  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
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.
  7. Display the signaling link assigned to the card, shown in 6, whose IP address is assigned to the local host shown in 5 by entering the rtrv-slk command with the card location of the signaling link. For this example, enter this command.

    rtrv-slk:loc=1205

    The following is an example of the possible output. 

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

LOC  LINK LSN         SLC TYPE
1205 A    lsn5         1  SS7IPGW

    The application running on the card is shown in the TYPE column of the rtrv-slk output.

    For this example, the new association must be assigned to a card running the SS7IPGW application.

    If the card’s application shown in this step and in 4 are the same, continue the procedure with 8.

    If the card’s application shown in this step and in 4 are not the same, either repeat this procedure from 5 with another local IP host, or add the new local IP host name by performing the Adding an IP Host procedure. The new local IP host must be assigned to a card running the application shown in 4. After the new local IP host has been added, continue the procedure with 9.

  8. Display the associations assigned to the local IP host value specified in 3 or 5 by entering the rtrv-assoc command with the lhost parameter. For this example, enter this command.

    rtrv-assoc:lhost="IPNODE-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
assoc1          1205 A     A    M3UA    1030  1030  YES  YES

IP Appl Sock/Assoc table is (7 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 3200 KB) on LOC = 1205
  9. Display the application servers that the associations shown in 8 are assigned to by entering rtrv-as command with the names of the associations shown in 8. For this example, enter this command.

    rtrv-as:aname=assoc1

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:14:37 GMT EAGLE5 36.0.0
AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   10      assoc1
AS Table is (2 of 250) 1% full

    The maximum number of SCTP association to application server assignments that can be hosted by an IPGWx card (referenced by the lhost parameter of the association) is 50.

    If the number of SCTP association to application server assignments is less than 50, continue the procedure with 10.

    If the number of SCTP association to application server assignments is 50, either repeat this procedure from 5 with another local IP host, or add the new local IP host name by performing the Adding an IP Host procedure. The new local IP host must be assigned to a card running the application shown in 4 and 7. After the new local IP host has been added, continue the procedure with10.

  10. Add the new association by performing the Adding an M3UA or SUA Association procedure.

    The open parameter value for this association must be set to no. The adapter value for this association must be the same as the adapter value shown in 3.

    These are the rules that apply to the association and the application server.
    • M2PA associations cannot be assigned to an application server.
    • If the application server is being added in this procedure will be assigned to a routing key containing an rcontext parameter value, the adapter parameter value for the association assigned to this application server can be either M3UA or SUA.
    • If the application server is being added in this procedure will be assigned to a routing key that does not contain an rcontext parameter value, the adapter parameter value for the association assigned to this application server must be M3UA.
    • SUA associations and their corresponding application server, can be assigned to only these types of routing keys.
      • Full routing key – DPC/SI=3/SSN
      • Partial routing key – DPC/SI=3
      • Partial routing key – DPC only
      • Partial routing key – SI=3 only
      • Default routing key.
      • The routing key containing the application server with the SUA associations must have an rcontext value assigned to it. If the new application server will not be assigned to one of these types of routing keys, the adapter parameter value of the associations assigned to the application server must be M3UA.
    • The application of the card containing the signaling link assigned to the association is either SS7IPGW or IPGWI.
  11. Add the association to the application server using the ent-as command with the name of the application server specified in 2 and the name of the new association. For this example, enter this command.

    ent-as:asname=as2:aname=assoc10

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ENT-AS:  MASP A - COMPLTD;
  12. Verify the changes using the rtrv-as command with the name of the application server specified in 11. For this example, enter this command.

    rtrv-as:asname=as2

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
AS Name           Mode        Tr ms   Association Names
as2               OVERRIDE    10      assoc7
                                      assoc10

AS table is (2 of 250) 1% full.

    Note:

    If you do not wish to change theopen parameter value of the association specified in11, continue the procedure with14.
  13. 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=assoc10: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;
  14. 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 4-17 Adding a New Association to an Existing Application Server



Sheet 1 of 5



Sheet 2 of 5



Sheet 3 of 5



Sheet 4 of 5



Sheet 5 of 5

4.14 Adding an Existing Association to an Existing Application Server

This procedure is used assign an existing association to an existing application server using the ent-as command.

The ent-as command uses these parameters:

:asname – The name of the application server.

:aname – The name of the association being assigned to the application server.

The maximum number SCTP association to application server assignments that can be hosted by an IPGWx card (referenced by the lhost parameter of the association) is 50. For example, the IPGWx card currently contains 38 SCTP association to application server assignments. The SCTP association to application server assignments could be one SCTP association assigned to 38 application servers, two SCTP associations assigned to 19 application servers, or any combination of SCTP associations assigned to application servers that add up to 38. The SCTP association to application server assignments can be verified with the rtrv-assoc:lhost=<local host name> and rtrv-as:aname=<association name> commands.

Table 4-11 Examples of IPGWx Card Provisioning Limits

Number of Associations hosted by the IPGWx card Number of Application Servers each Association is Assigned to * Total Association - Application Server Assignments maintained by the IPGWx card
1 50 50
50 1 50
25 1 50
25 2 50
0 0 50
38 1 38
19 2 38
* The EAGLE can contain a maximum of 250 application servers.

A maximum of 16 associations can be assigned to an application server.

The open parameter of the association must be set to no before the association can be assigned to the application server. This can be verified with the rtrv-assoc command.

M2PA associations (adapter=m2pa) cannot be assigned to application servers. Only M3UA (adapter=m3ua) and SUA (adapter=sua) associations can be assigned to application servers. This can be verified in the ADAPTER field in the rtrv-assoc output.

The application running on the card hosting the association that will be assigned to the application server must be the same as the application running on the cards hosting the other associations assigned to the application server.

Canceling the RTRV-AS and RTRV-ASSOC Commands

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-as or rtrv-assoc commands were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-as or rtrv-assoc commands were entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-as or rtrv-assoc commands were entered, from another terminal other that the terminal where the rtrv-as or rtrv-assoc 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 application servers in the database using the rtrv-as command.
    This is an example of possible output. 
    rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   10      a2
                                      a3
                                      assoc1

as2               OVERRIDE    10      assoc7
as3               OVERRIDE    10      swbel32

AS table is (3 of 250) 1% full.
  2. Display the application server that the new association will be added to by entering the rtrv-as command with the name of the application server.
    For this example, enter this command.

    rtrv-as:asname=as2

    This is an example of possible output. 

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

AS Name           Mode        Tr ms   Association Names
as2               OVERRIDE    10      assoc7

AS table is (3 of 250) 1% full.

    A maximum of 16 associations can be assigned to an application server. If the application server displayed in this step contains less than 16 associations, continue the procedure with 3.

    If the application server displayed in this step contains 16 associations, either select another application server to use in this procedure and repeat this step, or perform the Adding an Existing Association to a New Application Server procedure to add the association to a new application server.

    Note:

    If the association being added to the application server is shown in the rtrv-as output in 1, continue the procedure with 4.
  3. 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     2000  2345  YES  YES
a3              1307 A     A    SUA     3000  2346  YES  YES
assoc1          1305 A     A    SUA     4000  1030  YES  YES
assoc7          1305 A     A    SUA     4500  1030  YES  YES

    If the association being added to the application server is shown in this step, continue the procedure with 4.

    If the association being added to the application server is not shown in this step, perform the Adding a New Association to an Existing Application Server procedure to add a new association to the application server.

  4. Display one of the associations assigned to the application server shown in 2 using the rtrv-assoc command and specifying the association name shown in the rtrv-as output from 2 or in the rtrv-assoc output in 3.

    For this example, enter this command.

    rtrv-assoc:aname=assoc7

    This is an example of possible output. 

    rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc7
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    4500          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as2

IP Appl Sock table is (6 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1203

    The adapter parameter value of all the associations assigned to an application server must be the same. This step identifies the adapter value of the associations assigned to the application server.

    The application running on the card hosting the new association must be the same as the application on the cards hosting the associations assigned to the application server.

  5. Display the signaling link assigned to the card, shown in 4 by entering the rtrv-slk command with the card location of the signaling link.
    For this example, enter this command.

    rtrv-slk:loc=1205

    The following is an example of the possible output. 

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

LOC  LINK LSN         SLC TYPE
1205 A    lsn5         1  SS7IPGW

    The application running on the card is shown in the TYPE column of the rtrv-slk output.

    For this example, the new association must be assigned to a card running the SS7IPGW application.

  6. Display the association being added to the application server using the rtrv-assoc command and specifying the name of the association being added.
    For this example, enter this command.

    rtrv-assoc:aname=assoc1

    This is an example of possible output. 

    rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc1
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw101.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    4000          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as1

IP Appl Sock table is (6 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1203

    If the local host and adapter values shown in this step are the same as the local host and adapter values shown in 4, continue the procedure with 8.

    If the adapter value shown in this step is not the same as the adapter value shown in 4, repeat this procedure from 3.

    If the local host value shown in this step is not the same as the local host value shown in 4, but the adapter value shown in this step is the same as the adapter values shown in 4, continue the procedure with 7.

  7. Display the signaling link assigned to the card, shown in 6 by entering the rtrv-slk command with the card location of the signaling link.
    For this example, enter this command.

    rtrv-slk:loc=1201

    The following is an example of the possible output. 

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

LOC  LINK LSN         SLC TYPE
1201 A    lsn1         0  SS7IPGW

    The application running on the card is shown in the TYPE column of the rtrv-slk output.

    For this example, the association being added to the application server must be assigned to a card running the SS7IPGW application.

    If the card applications shown in this step and in 5 are the same, continue the procedure with 8.

    If the card applications shown in this step and in 5 are not the same, repeat this procedure from 3.

  8. Display the associations assigned to the local IP host value specified in by entering the rtrv-assoc command with the lhost parameter.
    For this example, enter this command.

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

    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
assoc1          1203 A     A    SUA     4000  1030  YES  YES

IP Appl Sock/Assoc table is (6 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 3200 KB) on LOC = 1203
  9. Display the application servers that the associations shown in 8 are assigned to by entering rtrv-as command with the names of the associations shown in 8.
    For this example, enter this command.

    rtrv-as:aname=assoc1

    This is an example of the possible output. 

    rlghncxa03w 06-10-28 21:14:37 GMT EAGLE5 36.0.0
AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE    10     assoc1
AS Table is (3 of 250) 1% full

    The maximum number of SCTP association to application server assignments that can be hosted by an IPGWx card (referenced by the lhost parameter of the association) is 50.

    If the number of SCTP association to application server assignments is less than 50, continue the procedure with 10.

    If the number of SCTP association to application server assignments is 50, either repeat this procedure from 3, or perform the Adding a New Association to an Existing Application Server procedure to add a new association to this application server.

    Note:

    If the value of the open parameter shown in 6 is no, continue the procedure with 11.
  10. 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=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;
  11. Add the association to the application server using the ent-as command.
    For this example, enter this command

    ent-as:asname=as2:aname=assoc1

    This is an example of possible output. 

    rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ENT-AS:  MASP A - COMPLTD;
  12. Verify the changes using the rtrv-as command with the application server name specified in 11.
    For this example, enter this command.

    rtrv-as:asname=as2

    This is an example of possible output. 

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

AS Name           Mode        Tr ms   Association Names
as2               OVERRIDE    10      assoc1
                                      assoc7
AS table is (3 of 250) 1% full.

    Note:

    If you do not wish to change theopen parameter value of the association specified in11, continue the procedure with14.
  13. 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=assoc1: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;
  14. 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 4-18 Add an Existing Application to an Existing Application Server - Sheet 1 of 5



Figure 4-19 Add an Existing Application to an Existing Application Server - Sheet 2 of 5



Figure 4-20 Add an Existing Application to an Existing Application Server - Sheet 3 of 5



Figure 4-21 Add an Existing Application to an Existing Application Server - Sheet 4 of 5



Figure 4-22 Add an Existing Application to an Existing Application Server - Sheet 5 of 5



4.15 Adding a Routing Key Containing an Application Server

This procedure is used to add a routing key containing an application server to the database using the ent-appl-rtkey command.

A routing key defines a filter that checks the specified values in an incoming SS7 MSU to determine which, if any, association receives the MSU. For more information about static routing keys, see Understanding Routing for SS7IPGW and IPGWI Applications.

The ent-appl-rtkey command uses these parameters.

:dpc/dpca/dpci/dpcn/dpcn24 – The destination point code value that is used to filter incoming MSUs. This parameter must not specify a cluster route. The destination point code of the routing key cannot be the APC of an IPGWx linkset or the SAPC assigned to an IPGWx linkset.

:opc/opca/opci/opcn/opcn24 – The originating point code value that is used to filter incoming MSUs. This parameter must not specify a cluster route. This parameter is valid only when the si parameter value is set to 4, 5, or 13. This parameter is required if si=4, 5, or 13 and type=full.

Note:

See the “Point Code Formats” section in Database Administration - SS7 User's Guide for a definition of the point code types that are used on the EAGLE and for a definition of the different formats that can be used for ITU national point codes.

:si – The service indicator value that is used to filter incoming MSUs. The range of values for the service indicator parameter (si) can be a numerical value from 0 to 15, or for selected service indicator values, a text string can be used instead of numbers. Table 4-12 shows the text strings that can be used in place of numbers for the service indicator values.

Table 4-12 Service Indicator Text String Values

Service Indicator Value Text String

0

snm

1

regtest

2

spltst

3

sccp

4

tup

5

isup

13

qbicc

:ssn – The subsystem value that is used to filter incoming MSUs. The ssn parameter is only valid when the si parameter value is set to 3 or sccp.

:cics – The starting circuit identification code that is used to filter incoming MSUs. When specified with cice, cics identifies the start of the range of circuit identification codes. The cics parameter is valid only when the si parameter value is set to 4, 5, or 13. The cics is required if si=4, 5, or 13 and type=full.

:cice – The ending circuit identification code that is used to filter incoming MSUs. When specified with cics, cice identifies the end of the range of circuit identification codes. The cice parameter is valid only when the si parameter value is set to 4, 5, or 13. The cice is required if si=4, 5, or 13 and type=full.

:type – The routing key type – Identifies the type of routing key that is being entered and used to route message signaling units (MSUs). One of three values, full/partial/default, can be specified for the type parameter (see Table 4-13). If type is not explicitly specified, type=full is assumed.

:asname – Application server (AS) name.

:rcontext – The routing context parameter, which has two functions:

  • Provides an index of the application server traffic that the sending application server is configured or registered to receive.
  • Identifies the SS7 network context for the message. The routing context parameter implicitly defines the SS7 point code format used, the SS7 network indicator value, and the SCCP protocol type/variant/version used.

Application server names are shown in the rtrv-as output.

Only one application server can be assigned to a routing key. There is a maximum of 2500 routing keys allowed per EAGLE. The application server names in each routing key must be unique.

The number of static routing keys is limited by the srkq parameter that was specified on the chg-sg-opts command.

Routing keys are associated only with the ss7ipgw or ipgwi application.

Group codes are required for 14-bit ITU-N point codes (DPCN/OPCN) when the Duplicate Point Code feature is enabled.

The starting circuit identification code must be less than or equal to the ending circuit identification code.

The ISUP routing over IP feature must be on in order to enter a routing key with these parameters: dpc, si, opc, cics, and cice. The IPISUP field in the rtrv-feat command output shows whether or not this feature is on.

The parameter combinations used by the ent-appl-rtkey command are based on the type of routing key and the service indicator value in the routing key. The parameter combinations are shown in Table 4-13.

Table 4-13 Routing Key Parameter Combinations for Adding a Routing Key Containing an Application Server

Full Routing Key - SI = 3 (SCCP) Partial Routing Key - SI = 3 (SCCP) Full Routing Key - SI=4 (TUP), 5 (ISUP), 13 (QBICC) Partial Routing Key - SI=4 (TUP), 5 (ISUP), 13 (QBICC) Full Routing Key - Other SI Values Partial Routing Key - Other SI Values Default Routing Key

dpc (See Notes 1, 2, and 11)

type=partial

dpc (See Notes 1 and 2)

type=partial

dpc (See Notes 1 and 2)

type=partial

type=default

si=3 (See Notes 4 and 11)

dpc (See Notes 1, 2, and 3)

si=4, 5, 13 (See Note 4)

dpc (See Notes 1, 2, and 3)

si=value other than 3, 4, 5, 13 (See Note 4)

dpc (See Notes 1, 2, and 3)

asname (See Note 10)

ssn (See Note 11)

si=3 (See Notes 3 and 4)

opc (See Notes 1 and 2)

si=4, 5, 13 (See Notes 3, 4, and 10)

type=full

si=value other than 3, 4, 5,

13 (See Notes 3, 4, and 10)

rcontext (See Note 10)

type=full

asname (See Note 10)

cics (See Notes 5, 6, 7, 8, and 9)

opc (See Notes 1, 2, and 3)

asname (See Note 10)

asname (See Note 10)

 

asname (See Note 10)

rcontext (See Note 10)

cice (See Notes 5, 6, 7, 8, and 9)

asname (See Note 10)

rcontext (See Note 10)

rcontext (See Note 10)

 

rcontext (See Note 10)

 

type=full

rcontext (See Note 10)

     
   

asname (See Note 10)

       
   

rcontext (See Note 10)

       

Notes:

1. The dpc and opc parameters can be either an ANSI point code (dpca, opca), ITU-I point code or ITU-I spare point code (dpci, opci), 14-bit ITU-N point code or 14-bit ITU-N spare point code (dpcn, opcn), or 24-bit ITU-N point code (dpcn24, opcn24). If the dpc and opc parameters are specified, the dpc and opc must be the same type of point code. For example, if the dpca parameter is specified, the OPC is specified with the opca parameter. If either point code value is a spare point code, the other point code value must be a spare point code on the same type. For example, if the dpc value is an ITU-I spare point code, the opc value must be an ITU-I spare point code.

2. If the ITU National Duplicate Point Code feature is on, the values for the dpcn and opcn parameters must have group codes assigned to them. The field ITUDUPPC in the rtrv-feat command output shows whether or not the ITU National Duplicate Point Code feature is on. If group codes are specified for ITU-N DPC and OPC, the groups codes must be the same.

3. These parameters are optional for partial routing keys, but at least one these parameters must be specified with the ent-appl-rtkey command.

4. Text strings can be used in place of some numerical service indicator values. See Table 4-12 for a list of these text strings.

5. When the service indicator parameter value equals 4 and an ANSI dpc is specified, the opc, cics, and cice parameters cannot be used. If the service indicator parameter value equals 4 and an ITU dpc is specified, the opc, cics, and cice parameters are required.

6. If the service indicator parameter (si) value is 4, the values of the cics and cice parameters is from 0 to 4095.

7. If the service indicator parameter (si) value is 5 and the point code in the routing key is either an ITU-I, 14-bit ITU-N, or 24-bit ITU-N point code, the values of the cics and cice parameters is from 0 to 4095. If the point code in the routing key is an ANSI point code, the values of the cics and cice parameters is from 0 to 16383.

8. If the service indicator parameter value is 13, the values of the cics and cice parameters is from 0 to 4294967295.

9. The CIC range, defined by the cics and cice parameters, cannot overlap the CIC range in an existing routing key.

10. The following rules apply to using the rcontext parameter.

  • The value of the rcontext parameter is from 0 to 4294967295.

  • The rcontext parameter is required for a routing key containing an SUA application server.
  • The rcontext parameter is optional for a routing key containing an M3UA application server.
  • The rcontext parameter value must be unique in the database. Multiple routing keys cannot have the same rcontext value assigned.
  • An application server can be assigned to only one routing key containing a routing context value.
  • If the application server being assigned to the new routing key is assigned to other routing keys that do not contain rcontext parameter values, the rcontext parameter cannot be specified for the new routing key.
  • An application server can be assigned to multiple routing keys if those routing keys do not contain a routing context value.
  • An application server can be assigned to either a routing key containing a routing context value, or to routing keys that do not contain a routing context value, but the application server cannot be assigned to both types of routing keys.
  • In order for an M3UA or SUA association to be assigned to multiple routing keys with a routing context value, the M3UA or SUA association must be assigned to multiple application servers and then each application server must be assigned to a routing key containing a routing context value.

11. To communicate the status changes of remote IP subsystems (defined by the DPC and SSN specified in a full SCCP routing key), the DPC and SSN specified for a full SCCP routing key must be provisioned in the mated application table. Perform one of the mated application procedures in Database Administration - GTT User's Guide to provision a mated application with the DPC and SSN specified for a full SCCP routing key.

Canceling the RTRV-AS and RTRV-APPL-RTKEY Commands

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-as or rtrv-appl-rtkey commands were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-as or rtrv-appl-rtkey commands were entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-as and rtrv-appl-rtkey commands were entered, from another terminal other that the terminal where the rtrv-as or rtrv-appl-rtkey 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 current routing key information in the database by entering the rtrv-appl-rtkey command.

    The following is an example of the possible output. 

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

RCONTEXT    DPC          SI  ADPTR  ASNAME           TYPE
----------  123-234-123   5  M3UA   as12             FULL
----------  005-005-001   5  M3UA   as9              FULL
----------  005-005-001   5  M3UA   as9              FULL
2500        006-006-001   5  SUA    as10             FULL

RCONTEXT    DPCI         SI  ADPTR  ASNAME           TYPE
----------    2-100-7     6  M3UA   as4              FULL
100           3-137-6     6  SUA    as1              FULL
225           4-035-7     5  SUA    as7              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-7     5  M3UA   as8              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-8     3  M3UA   as3              FULL
----------    6-006-8     5  M3UA   as5              FULL
----------    6-024-7     5  M3UA   as4              FULL
----------    6-024-7     5  M3UA   as4              FULL
300           7-008-7     6  SUA    as6              FULL

RCONTEXT    DPC          SI  ADPTR  ASNAME           TYPE
----------  ***********  **  M3UA   as11             DEFAULT

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full

    The database can contain only one default routing key. If the rtrv-appl-rtkey output contains a default routing key, a default routing key cannot be added in this procedure. Continue the procedure with 2 to add either a full or partial routing key with the desired application server.

  2. Display the current application server information in the database by entering the rtrv-as command.

    The following is an example of the possible output. 

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

AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   10      assoc1
                                      assoc2
                                      assoc3
                                      assoc5
                                      assoc6

as2               OVERRIDE    10      assoc7

as3               LOADSHARE   10      assoc8
                                      assoc9

as4               LOADSHARE   10      assoc10
                                      assoc11

as5               LOADSHARE   10      assoc12
                                      assoc13

as6               LOADSHARE   10      assoc14
                                      assoc15

as7               LOADSHARE   10      assoc16
                                      assoc17

as8               LOADSHARE   10      assoc18
                                      assoc19

as9               LOADSHARE   10      assoc20
                                      assoc21

as10              LOADSHARE   10      assoc22
                                      assoc23

as12              LOADSHARE   10      assoc24
                                      assoc25
AS Table is (11 of 250) 4% full

    If the required application server is not in the database, perform one of these procedures to add the application server:

    If the rcontext parameter will not be specified for the routing key, make sure that the adapter parameter value for the associations assigned to the new application server is M3UA.

    If the rcontext parameter will be specified for the routing key, make sure that the open parameter value of the associations is set to no. The adapter parameter value of these associations can be either SUA or M3UA.

    SUA associations, and their corresponding application server, can be assigned to only these types of routing keys:

    • Full routing key – DPC/SI=3/SSN
    • Partial routing key – DPC/SI=3
    • Partial routing key – DPC only
    • Partial routing key – SI=3 only
    • Default routing key.

    After the new application server is added to the database, continue the procedure with 4.

  3. Display the routing keys containing the application server being used in this procedure by entering the rtrv-appl-rtkey command with the application server name and the display=all parameter.
    For this example, enter these commands.

    rtrv-appl-rtkey:asname=as4:display=all

    The following is an example of the possible output. 

    
rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
----------   6-024-7      5 ---   1-057-4      150        175

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as4    
                                         
    ANAMES
    assoc11          assoc12

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE       LOC
----------   2-100-7      6 --- -----------    ---------- ---------- ----

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as4    
                                         
    ANAMES
    assoc11          assoc12

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full

    rtrv-appl-rtkey:asname=as5:display=all

    The following is an example of the possible output. 

    
rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
225          4-035-7      5 ---   3-200-4      200        300

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as5    
                                         
    ANAMES
    assoc15          assoc16


STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full

    If the application server is not assigned to any routing keys, the rcontext parameter can be specified for the new routing key using this application server. Continue the procedure with 4.

    An application server can be assigned to only one routing key containing a routing context value. If the application server is assigned to other routing keys, the rcontext parameter cannot be specified for the new routing key being added in this procedure. If you wish to use the rcontext parameter for the new routing key, perform one of these procedures to add the application server:

    After the new application server is added, continue the procedure with 6.

    If the application server is assigned to other routing keys, and these routing keys do not contain rcontext parameter values, the application server can be assigned to the new routing key in this procedure, but the rcontext parameter cannot be specified for the new routing key.

    If you do not wish to use the rcontext parameter for the new routing key, continue the procedure with 6.

  4. Display the associations assigned to the application server displayed in 3, to verify the open parameter value of the association, using the rtrv-assoc command with the association names shown in 2.
    For this example, enter these commands.

    rtrv-assoc:aname=assoc11

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ANAME assoc11
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  M3UA          VER         M3UA RFC
      LHOST    gw110.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      LPORT    1030          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      
      ASNAMES
      as4

IP Appl Sock table is (10 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1203

    rtrv-assoc:aname=assoc12

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ANAME assoc12
      LOC      1204          IPLNK PORT  A          LINK  A
      ADAPTER  M3UA          VER         M3UA RFC
      LHOST    gw200.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      LPORT    2564          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      
      ASNAMES
      as4

IP Appl Sock table is (10 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1204

    rtrv-assoc:aname=assoc15

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ANAME assoc15
      LOC      1207          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw150.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      LPORT    1500          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      
      ASNAMES
      as5

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

    rtrv-assoc:aname=assoc16

    This is an example of possible output. 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ANAME assoc16
      LOC      1211          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw160.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      LPORT    3571          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      
      ASNAMES
      as5

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

    Repeat this step for each association name displayed in 3 to verify the open parameter of each association assigned to the application server.

    If a new application server was added in 2, continue the procedure with 6.

    If the rcontext parameter is not being specified in this procedure, continue the procedure with 6.

    If the open parameter value for all the associations assigned to the application server is no (shown in this step), continue the procedure with 6.

  5. 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=assoc11:open=no

    chg-assoc:aname=assoc12:open=no

    chg-assoc:aname=assoc15:open=no

    chg-assoc:aname=assoc16:open=no

    chg-assoc:aname=assoc20:open=no

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

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

    Caution:

    TheIP connections using the associations specified in this step will not be able to carry any traffic when theopen parameter is changed tono.

    Repeat this step for all the associations assigned to the application server that have the open=yes parameter value.

    If a default routing key with an application server name is being added in this procedure, continue the procedure with 11.

    If ITU-I or 14-bit ITU-N spare point codes are not being assigned to the routing key, or if ITU-I or 14-bit ITU-N spare point codes are shown in any routing keys shown in the rtrv-app-rtkey output in 1, continue the procedure with 7.

  6. Display the status of the ITU National and International Spare Point Code Support feature by entering the rtrv-ctrl-feat command with the ITU National and International Spare Point Code Support feature part number.
    Enter this command.

    rtrv-ctrl-feat:partnum=893013601

    The following is an example of the possible output. 

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

Feature Name              Partnum    Status  Quantity
Spare Point Code Support  893013601  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 ITU National and International Spare Point Code Support feature is not enabled, perform the “Activating the ITU National and International Spare Point Code Support feature” procedure in Database Administration - SS7 User's Guide and enable and turn on the ITU National and International Spare Point Code Support feature.

  7. The DPC of the routing key cannot be the APC of an IPGWx linkset or an SAPC assigned to an IPGWx linkset.

    Display the names of the IPGWx linksets by entering the rept-stat-iptps command. 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
lsgw1201      80%     ----    10000  TX:   7200     7600  05-02-10 11:40:04
                                    RCV:   7200     7600  05-02-10 11:40:04
lsgw1204      80%     ----    10000  TX:   6700     7600  05-02-10 11:40:04
                                    RCV:   6500     7600  05-02-10 11:40:04
lsgw1207      80%     ----    10000  TX:   7300     7450  05-02-10 11:40:04
                                    RCV:   7300     7450  05-02-10 11:40:04
lsgw1211      80%      ----   10000  TX:   7400     7450  05-02-10 11:40:04
                                    RCV:   7400     7450  05-02-10 11:40:04 
---------------------------------------------------------------------------

Command Completed.
  8. Display the IPGWx linksets shown in the rept-stat-iptps output in 7 using the rtrv-ls command and specifying the name of the linkset shown in 7.

    For this example, enter these commands.

    rtrv-ls:lsn=lsgw1201

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 16:31:35 GMT EAGLE5 38.0.0

                                 L3T SLT              GWS GWS GWS
LSN          APCA   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsgw1201     240-020-000   scr1  1   1   yes A   1    off off off yes   off

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE     IPLIML2

           LOC  LINK SLC TYPE
           1201 A    0   SS7IPGW

Link set table is (14 of 1024)  1% full

    rtrv-ls:lsn=lsgw1204

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

           CLLI         TFATCABMLQ  MTPRSE  ASL8  SLSRSB  MULTGC  ITUTFR
           -----------  1           ---     ---   1       no      off

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1204 A    0   IPGWI

           SAPCI
           1-010-1

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

    rtrv-ls:lsn=lsgw1207

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

                                 L3T SLT              GWS GWS GWS
LSN          APCI   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsgw1207     2-154-0       none  1   1   no  A   1    off off off ---   off

           CLLI         TFATCABMLQ  MTPRSE  ASL8  SLSRSB  MULTGC  ITUTFR
           -----------  1           ---     ---   1       no      off

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1207 A    0   IPGWI

           SAPCN
           5823

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

    rtrv-ls:lsn=lsgw1211

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 16:31:35 GMT EAGLE5 38.0.0
                                 L3T SLT              GWS GWS GWS
LSN          APCA   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsgw1211     010-130-057   scr1  1   1   yes A   1    off off off yes   off

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1211 A    0   SS7IPGW

Link set table is (14 of 1024)  1% full

    If the DPC of the routing key is shown in the rtrv-ls outputs in this step, choose another DPC value for the routing key that is not shown in the rtrv-ls outputs in this step.

    Note:

    If theSI value of the routing key being added is a value other than 4, 5, or 13, continue the procedure with11.
  9. Verify that the ISUP Routing over IP feature is on, by entering the rtrv-feat command.
    If the ISUP Routing over IP feature is on, the IPISUP field should be set to on. For this example, the ISUP Routing over IP feature is off.

    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, see thertrv-feat command description in theCommands Manual.

    If the ISUP Routing over IP feature is on, continue the procedure with 11.

  10. Turn the ISUP Routing over IP feature on by entering this command.

    chg-feat:ipisup=on

    Note:

    Once theISUP Routing overIP feature is turned on with thechg-feat command, it cannot be turned off.

    The ISUP Routing over IP 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 ISUP Routing over IP feature, contact your Oracle Sales Representative or Account Representative.

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

    
rlghncxa03w 06-10-28 11:43:04 GMT EAGLE5 36.0.0
CHG-FEAT: MASP A - COMPLTD
  11. Add a routing key entry to the database by entering the ent-appl-rtkey command.
    The parameters required for the ent-appl-rtkey command are determined by the type of routing key being added and the service indicator value in the routing key. See Table 4-13 for the parameter combinations that can be used for the type of routing key being added to the database. For this example, enter these commands.

    ent-appl-rtkey:dpci=3-009-3:si=5:opci=4-100-3:cics=100 :cice=500:asname=as3:type=full

    ent-appl-rtkey:dpci=1-050-2:si=5:opci=6-077-7:cics=200 :cice=300:asname=as20:type=full:rcontext=2000

    Note:

    A routing key cannot be added with the application serveras4, displayed in3, because application serveras4 is assigned to a routing key containing a routing context value. Only one application server can be assigned to a routing key containing a routing context value.

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

    
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
ENT-APPL-RTKEY: MASP A - COMPLTD
  12. Verify the new routing key information in the database by entering the rtrv-appl-rtkey command with the routing key parameters specified in 11 (dpc, si, opc, cics, cice, ssn, asname, type, and rcontext, as applicable) with the display=all parameter.
    For this example, enter these commands.

    rtrv-appl-rtkey:dpci=3-009-3:si=5:opci=4-100-3:cics=100 :cice=500:asname=as3:type=full:display=all

    The following is an example of the possible output. 

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

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
----------   3-009-3      5 ---   4-100-3      100        500

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as3    
                                         
    ANAMES
    assoc11          assoc12

STATIC Route Key table is (19 of 2000) 1% full
STATIC Route Key Socket Association table is (19 of 32000) 1% full

    rtrv-appl-rtkey:dpci=1-050-2:si=5:opci=6-077-7:cics=200 :cice=300:asname=as20:type=full:rcontext=2000:display=all

    The following is an example of the possible output. 

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

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
2000         1-050-2      5 ---   6-077-7      200        300

    ADPTR  TYPE      ASNAME             
    SUA    FULL      as20   
                                         
    ANAMES
    assoc20

STATIC Route Key table is (19 of 2000) 1% full
STATIC Route Key Socket Association table is (19 of 32000) 1% full

    Note:

    If theopen parameter value of the associations assigned to the routing key added in this procedure was not changed (5was not performed), continue the procedure with14.
  13. Change the value of the open parameter of the associations that were changed in 5 to yes by specifying the chg-assoc command with the open=yes parameter.
    For this example, enter these commands.

    chg-assoc:aname=assoc11:open=yes

    chg-assoc:aname=assoc12:open=yes

    chg-assoc:aname=assoc15:open=yes

    chg-assoc:aname=assoc16:open=yes

    chg-assoc:aname=assoc20:open=yes

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

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

    Repeat this step for all the associations that were changed in 5.

  14. 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 4-23 Adding a Routing Key Containing an Application Server



Sheet 1 of 5



Sheet 2 of 5



Sheet 3 of 5



Sheet 4 of 5



Sheet 5 of 5

4.16 Adding a Network Appearance

The network appearance field identifies the SS7 network context for the message, for the purpose of logically separating the signaling traffic between the SGP (signaling gateway process) and the ASP (application server process) over a common SCTP (stream control transmission protocol) association. This field is contained in the DATA, DUNA, DAVA, DRST, DAUD, SCON, and DUPU messages.

The network appearance is provisioned in the database using the ent-na command with these parameters.

:na – the 32-bit value of the network appearance, from 0 to 4294967295.

:type – the network type of the network appearance, ansi (ANSI), itui (ITU-I), itun (14-bit ITU-N), itun24 (24-bit ITU-N), ituis (ITU-I Spare), ituns (14-bit ITU-N Spare).

:gc – the specific ITU-N group code associated with the network appearance.

The gc parameter can be specified only with the type=itun or type=ituns parameters.

The gc parameter must be specified with the type=itun or type=ituns parameters if the ITU Duplicate Point Code feature is on. If the ITU Duplicate Point Code feature is off, the gc parameter cannot be specified.

The gc parameter value must be shown in the rtrv-spc or rtrv-sid outputs.

The ituis or ituns parameters can be specified only if the ITU National and International Spare Point Code Support feature is enabled.

  1. Display the network appearances in the database with the rtrv-na command. This is an example of the possible output. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
TYPE  GC           NA
ANSI  --          100
ITUN  FR   4000000000
ITUN  GE   1000000000

    Note:

    If thegc parameter is not being specified in this procedure, continue the procedure with4.
  2. Display the self-identification of the EAGLE using the rtrv-sid command. This is an example of the possible output. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
PCA              PCI             PCN           CLLI            PCTYPE
001-001-001      1-200-6         13482         rlghncxa03w     OTHER

CPCA
002-002-002       002-002-003       002-002-004      002-002-005
002-002-006       002-002-007       002-002-008      002-002-009
004-002-001       004-003-003       144-212-003

CPCA (LNP)
005-005-002      005-005-004      005-005-005

CPCI
1-001-1           1-001-2           1-001-3          1-001-4

CPCN
02091             02092             02094             02097
02191             02192             11177

    If the desired group code is shown in the rtrv-sid output, continue the procedure with 4.

  3. Display the secondary point codes in the database with the rtrv-spc command. This is an example of the possible output. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
SPC (Secondary Point Codes)

SPCA
001-010-010
002-010-010
003-010-010

SPC-I
1-253-5
2-254-6
3-255-7

SPC-N
10-01-11-1-fr
13-02-12-0-ge
13-02-12-0-uk

SPC-N24
none

Secondary Point Code table is (9 of 40) 23% full

    If the desired group code is not shown in the rtrv-spc or rtrv-sid outputs, go to the “Adding a Secondary Point Code” procedure in Database Administration - SS7 User's Guide to turn the ITU Duplicate Point Code feature on, and add a secondary point code to the database with the desired group code value.

    If the ituis or ituns parameters will not be specified in this procedure, continue the procedure with 5.

    If the ituis or ituns parameters will be specified in this procedure, and ITU-I spare or 14-bit ITU-N spare network appearances are shown in the rtrv-na output in 1, or ITU-I spare or 14-bit ITU-N spare point codes are shown in the rtrv-sid output in 2, continue the procedure with 5.

  4. Display the status of the ITU National and International Spare Point Code Support feature by entering the rtrv-ctrl-feat command with the ITU National and International Spare Point Code Support feature part number. Enter this command.

    rtrv-ctrl-feat:partnum=893013601

    The following is an example of the possible output. 

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

Feature Name              Partnum    Status  Quantity
Spare Point Code Support  893013601  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 ITU National and International Spare Point Code Support feature is not enabled, perform the “Activating the ITU National and International Spare Point Code Support feature” procedure in Database Administration - SS7 User's Guide and enable and turn on the ITU National and International Spare Point Code Support feature.

  5. Add the network appearance to the database with the ent-na command.

    If the gc parameter is specified with the ent-na command, the gc parameter value must be shown in the rtrv-sid output in 2, or assigned to an ITU-N point code (SPC-N) shown in the rtrv-spc output in 3. For this example, enter these commands.

    ent-na:na=1000:type=itui

    ent-na:na=3:type=itun24

    ent-na:na=150000:type=itun:gc=uk

    ent-na:na=2000:type=ituis

    ent-na:na=5000:type=ituns:gc=sp

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

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
ENT-NA:  MASP A - COMPLTD
  6. Verify the changes using the rtrv-na command. This is an example of the possible output. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
TYPE    GC           NA
ANSI    --          100
ITUI    --         1000
ITUN    uk       150000
ITUN    fr   4000000000
ITUN    ge   1000000000
ITUN24  --            3
ITUIS   --         2000
ITUNS   sp         5000
  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 4-24 Adding a Network Appearance



Sheet 1 of 3



Sheet 2 of 3



Sheet 3 of 3

4.17 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:

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.
  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 the procedure with 7.

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

    Note:

    If thertrv-ctrl-feat output in1shows any controlled features, continue this procedure with6. If thertrv-ctrl-feat output shows only the HC-MIM SLK Capacity feature with a quantity of 64,2through5must 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 with5. 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 tounresolvable-reference.html#GUID-1825DD07-2A6B-4648-859A-1258A0F9AC40for 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-m3ua-and-sua-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-m3ua-and-sua-configuration-procedures1.html and ietf-m3ua-and-sua-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-m3ua-and-sua-configuration-procedures1.html, if the serial number shown in ietf-m3ua-and-sua-configuration-procedures1.html is correct, or with the serial number shown in ietf-m3ua-and-sua-configuration-procedures1.html, if the serial number was changed in ietf-m3ua-and-sua-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 (thefak 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 4-25 Activating the Large MSU Support for IP Signaling Feature



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

4.18 Removing IETF M3UA and SUA Components

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

4.19 Removing an IPGWx Card

Use this procedure to remove an IP card, a card running one of these applications: ss7ipgw or ipgwi, 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 09-10-15 16:34:56 GMT EAGLE5 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   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 SS7IPGW or IPGWI.

    Perform the Removing an IPGWx Signaling Link procedure 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 4-26 Removing an IPGWx Card



4.20 Removing an IPGWx Signaling Link

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

:loc – The card location of the IP 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    SAALTALI
2205 A    lsnip1       1  IPLIM    M2PA
2204 B    lsnlp2       0  IPLIM    M2PA
2213 A    lsnip5       0  IPLIMI   M2PA
2215 A    lsnlp2       1  IPLIM    SAALTALI

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=lsnlp3

    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
lsnlp3        002-009-003   scr2 1   1   no  a   1    on  off on  no    off

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

           IPSG  IPGWAPC  GTTMODE           CGGTMOD
           no    yes      CdPA                no

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

           LOC  LINK SLC TYPE
           1201 A    0   SS7IPGW

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 inCommands 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. Any in-service IP connections on the signaling link being removed in this procedure must be placed out of service.

    Have the far-end node for the signaling link being removed place the M3UA or SUA associations in either the ASP-INACTIVE or ASP-DOWN state.

  6. 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 this command.

    rtrv-ip-lnk:loc=2207

    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
2207  A    192.1.1.10      255.255.255.128 HALF    10    802.3   NO   NO
2207  B    --------------- --------------- HALF    10    DIX     NO   NO
  7. Display the IP host information associated with the IP link by entering the rtrv-ip-host command with the IP address shown in 6. 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_2207

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

    rtrv-assoc:lhost=ipnode1_2207

    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          2207 A     A    M3UA    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 = 2207
  9. 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. For this example, enter this command.

    Note:

    If there is no association shown in7, or theopen andalw parameter values of the association shown in7areno, continue the procedure with10.

    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;
  10. 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=2207: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
  11. 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 10. For this example, enter these commands.

    rept-stat-slk:loc=2207: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
2207,A   ls04      ls04clli    OOS-MT       Unavail   ----
  ALARM STATUS       = *   0235 REPT-LNK-MGTINH: local inhibited
  UNAVAIL REASON     = LI
  12. Place the card that contains the signaling link shown in 11 out of service by entering the rmv-card command specifying the card location shown in 11. For this example, enter this command.

    rmv-card:loc=2207

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

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

    rept-stat-card:loc=2207

    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
2207   114-001-000  DCM       SS7IPGW    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.
  14. 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 this command.

    dlt-slk:loc=2207: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 theOAMHCMEAS value in thertrv-measopts output is on, the scheduled UI measurement reports will be enabled.
  15. Verify the changes using the rtrv-slk command, with the card location and link values specified in 14. For this example, enter this command.

    rtrv-slk:loc=2207:link=a

    When the rtrv-slk command has completed, no entry is displayed showing that the signaling link has been removed. 

    
    rlghncxa03w 09-09-18 13:43:31 GMT EAGLE5 41.1.0
E2373 Cmd Rej: Link is unequipped in the database
  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 4-27 Removing an IPGWx Signaling Link



Sheet 1 of 2



Sheet 2 of 2

4.21 Removing a Mate IPGWx Linkset from another IPGWx Linkset

This procedure is used to remove a mate IPGWx linkset from an existing IPGWx linkset chg-ls command with these parameters.

:lsn – The name of the IPGWx linkset that contains the mate IPGWx Linkset that is being removed, shown in the rept-stat-iptps or rtrv-ls command outputs.

:matelsn – The name of the mate IPGWx linkset that is being removed.

:action=delete – removes the mate IPGWx linkset from the IPGWx linkset specified by the lsn parameter.

An IPGWx linkset is a linkset that contains signaling links assigned to IPGWx cards. IPGWx cards are cards running either the SS7IPGW or IPGWI applications.

The mate linkset name is displayed in the rtrv-ls:lsn=<linkset name> command output.

Before a mate IPGWx linkset can be removed from an IPGWx linkset, the card containing the IPGWx signaling link assigned to the mate linkset, and the signaling link assigned to that card must be placed out of service.

Other Optional Parameters

There are other optional parameters that can be used to configure a linkset. These parameters are not required for configuring an IPGWx linkset. These parameters are discussed in more detail in Commands User's Guide or in these sections.
  1. Display the system-wide IP TPS usage report, and the IPGWx linksets, by entering the rept-stat-iptps command. 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
lsgw1101      80%     ----     6000  TX:   5100     5500  05-02-10 11:40:04
                                    RCV:   5100     5500  05-02-10 11:40:04
lsgw1103      80%     ----     6000  TX:   5200     5500  05-02-10 11:40:04
                                    RCV:   5200     5500  05-02-10 11:40:04
lsgw1105      80%     ----    14000  TX:   7300     7450  05-02-10 11:40:04
                                    RCV:   7300     7450  05-02-10 11:40:04
lsgw1107      70%      ----    4000  TX:   3200     3500  05-02-10 11:40:04
                                    RCV:   3200     3500  05-02-10 11:40:04 
--------------------------------------------------------------------------

Command Completed.

    If no entries are displayed in the rept-stat-iptps output, there are no IPGWx linksets in the database. This procedure cannot be performed.

    If entries are displayed in the rept-stat-iptps output, continue the procedure with 2.

  2. Display the attributes of all the linksets shown in the rept-stat-iptps output in 1 by entering the rtrv-ls command with the name of each linkset shown in the rept-stat-iptps output in 1. For this example, enter these commands.

    rtrv-ls:lsn=lsgw1101

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

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

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1101 A    0   SS7IPGW

Link set table is ( 14 of 1024)  1% full

    rtrv-ls:lsn=lsgw1103

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

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

           IPGWAPC  MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes      lsgw1107   10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1103 A    0   SS7IPGW

Link set table is ( 14 of 1024)  1% full

    rtrv-ls:lsn=lsgw1105

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

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

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1105 A    0   SS7IPGW

Link set table is ( 14 of 1024)  1% full

    rtrv-ls:lsn=lsgw1107

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

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

           IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes     ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1107 A    0   SS7IPGW

Link set table is ( 14 of 1024)  1% full

    If none of the linksets displayed in this step contain a mate IPGWx linkset, shown in the MATELSN column, this procedure cannot be performed.

    If any of the linksets displayed in this step contain a mate IPGWx linkset, shown in the MATELSN column, continue this procedure with one of these steps.
    • If a signaling link is assigned to the mate linkset, continue the procedure with 3.
    • If a signaling link is not assigned to the mate linkset, continue the procedure with 12.
  3. Display the status of the card containing the signaling link that is assigned to the mate IPGWx linkset that is being removed by entering the rept-stat-card command with the card location shown in the LOCcolumn for the mate IPGWx linkset shown in 2. For this example, enter this command.

    rept-stat-card:loc=1107

    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
1107  114-000-000  EDCM    SS7IPGW   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              lsgw1107      -----------
Command Completed.

    If the status of the card is out-of-service maintenance disabled (OOS-MT-DSBLD), continue the procedure with 12.

    If the status of the card is not out-of-service maintenance disabled (OOS-MT-DSBLD), continue the procedure with 4.

  4. Display the status of the signaling link assigned to the card shown in 3 by entering the rept-stat-slk command with the card location used in 3 and the link=a parameter. For this example, enter this command.

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

    This is an example of the possible output. 

    
rlghncxa03w 08-04-27 17:00:36 GMT EAGLE5 38.0.0
SLK      LSN         CLLI        PST          SST       AST
1107,A   lsgw1107    ----------- IS-NR        Avail     -----
  ALARM STATUS       = No Alarms.
  UNAVAIL REASON     = NA
Command Completed.

    If the status of the signaling link is out-of-service maintenance disabled (OOS-MT-DSBLD), continue the procedure with 12.

    If the status of the signaling link is not out-of-service maintenance disabled (OOS-MT-DSBLD), any in-service IP connections on the signaling link must be placed out of service. Continue the procedure by performing one of these steps.
    • The recommended method is to have the far end node place these IPconnections out of service. Have the far-end node for the signaling link shown in 4 place the M3UA or SUA associations in either the ASP-INACTIVE or ASP-DOWN state. After the IP connections have been placed out of service, continue the procedure with 10.
    • If you do not wish to have the far end node place these IPconnections out of service, continue the procedure with 5.
  5. Display the IP link associated with the card that the signaling link shown in 4 is assigned to by entering the rtrv-ip-lnk command with the card location shown in 4. For this example, enter this command.

    rtrv-ip-lnk:loc=1107

    The following is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:14:37 GMT EAGLE5 38.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
1107  A    192.3.1.10      255.255.255.128 HALF    10    802.3   NO   NO
1107  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 this command.

    rtrv-ip-host:ipaddr=192.003.001.010

    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.3.1.10      IPNODE1_1107

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

    For this example, enter this command.

    rtrv-assoc:lhost=ipnode1_1107

    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
assoc1          1107 A     A    M3UA    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 = 1107
  8. Change the alw parameter values in the association shown in 7 using the chg-assoc command with the alw=no parameters, as necessary.

    Note:

    If theopen andalw parameter values of the association shown in7areno, continue the procedure with10.

    chg-assoc:aname=assoc1:alw=no

    Caution:

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

    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

    Repeat this step for all associations shown in 7.

  9. Change the open parameter values in the association shown in 7 using the chg-assoc command with the open=no parameters, as necessary.

    chg-assoc:aname=assoc1: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
    Repeat this step for all associations shown in 7.
  10. Deactivate the signaling link assigned to the IP card using the dact-slk command. For example, enter this command.

    dact-slk:loc=1107:link=a (for the removing a mate linkset example)

    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 08-04-12 09:12:36 GMT EAGLE5 38.0.0
Deactivate Link message sent to card.
  11. Inhibit the IP card using the inh-card command. For example, enter this command.

    inh-card:loc=1107 (for the removing a mate linkset example)

    This message should appear. 

    
rlghncxa03w 08-04-28 21:18:37 GMT EAGLE5 38.0.0
Card has been inhibited.
  12. Change the linkset shown in 2 by entering the chg-ls command with the matelsn and action=delete parameter.

    For this example, enter this command.

    chg-ls:lsn=lsgw1103:matelsn=lsgw1107:action=delete

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

    
rlghncxa03w 08-04-17 16:23:21 GMT  EAGLE5 38.0.0
Link set table is ( 14 of 1024)  1% full
CHG-LS: MASP A - COMPLTD
  13. Verify the changes using the rtrv-ls command specifying the linkset name specified in 12 with the lsn parameter. For this example, enter this command.

    rtrv-ls:lsn=lsgw1103

    This is an example of the possible output. 

    
rlghncxa03w 08-04-17 11:43:04 GMT EAGLE5 38.0.0

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

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

           IPGWAPC  MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
           yes      ---------- 10000 70     % 70      % CdPA

           LOC  LINK SLC TYPE
           1103 A    0   SS7IPGW

Link set table is ( 14 of 1024)  1% full

    If the linkset shown in this step does not have a signaling link assigned to it, continue the procedure with 18.

    If the linkset shown in this step has a signaling link assigned to it, continue the procedure with 14.

  14. Allow the IP card that was inhibited in 11 using the alw-card command. For example, enter this command.

    alw-card:loc=1107

    This message should appear. 

    rlghncxa03w 08-04-28 21:21:37 GMT EAGLE5 38.0.0
Card has been allowed.
  15. Activate the signaling link from 10 using the act-slk command. For example, enter one of these commands.

    act-slk:loc=1107:link=a

    The output confirms the activation. 

    rlghncxa03w 08-04-07 11:11:28 GMT EAGLE5 38.0.0
Activate Link message sent to card
  16. Change the open and alw parameter values for all the associations changed in 8 or 9 using the chg-assoc command with the open=yes and alw=yes parameters.

    Note:

    If8and9were not performed, continue the procedure with17.

    chg-assoc:aname=assoc1:open=yes:alw=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. Have the far-end node for the signaling link shown in 13 place the M3UAor SUAassociations in the ASP-ACTIVEstate to place the IP connections on the signaling link into service.
  18. 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 4-28 Removing a Mate IPGWx Linkset from another IPGWx Linkset



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

4.22 Removing an IP Host Assigned to an IPGWx Card

This procedure removes an IP host that is assigned to an IPGWx 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 a M3UA or SUA Association procedure or the host name in these associations can be changed by performing theChanging the Host Values of a M3UA or SUA 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) 0.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 SS7IPGW or IPGWI 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=”IPNODE1-1205”

    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              1313 A     A    M3UA    7205  7001  NO   NO

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

    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 a M3UA or SUA 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 M3UA or SUA 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=”IPNODE1-1205”

    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=”IPNODE1-1205”

    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) 0.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 4-29 Removing an IP Host Assigned to an IPGWx Card



4.23 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     SS7IPGW   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 4-30 Removing an IP Route



4.24 Removing a M3UA or SUA Association

This procedure is used to remove a SUA association from the database or to remove a M3UA association that is assigned to a card running either the SS7IPGW or IPGWI applications. Perform the Removing an IPSG Association procedure to remove a M3UA association that is assigned to a card running the IPSG application.

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 association being removed from the database cannot be assigned to an application server. This can be verified with the rtrv-as command. 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.

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

    If the association that is being removed in this procedure is an SUA association, continue the procedure with 3.

    If the association that is being removed in this procedure is an M3UA association, continue the procedure with 2.

  2. Enter the rtrv-card command with the location of the card that is hosting the M3UA association that will be removed 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       SS7IPGW  lsn1        A    0

    If the application assigned to the card is SS7IPGW or IPGWI, 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. Display the application servers referencing the association being removed from the database using the rtrv-as command with the name of the association being removed in this procedure.
    For this example, enter this command.

    rtrv-as:aname=swbel32

    This is an example of possible output. 

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

AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   2000    swbel32
as2               OVERRIDE    10      swbel32
AS Table is (2 of 250) 1% full

    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.

  4. 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 with5.

    For this example, enter this command.

    chg-assoc:aname=swbel32: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;
  5. Remove the association from the database using the dlt-assoc command.

    For this example, enter this command.

    dlt-assoc:aname=swbel32

    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
  6. Verify the changes using the rtrv-assoc command with the name of the association specified in 5.
    For this example, enter this command.

    rtrv-assoc:aname=swbel32

    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
  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 4-31 Removing a M3UA or SUA Association



4.25 Removing an Association from an Application Server

This procedure is used remove an association from an application server using the dlt-as command.

The dlt-as command uses these parameters:

:asname – The application server name containing the association being removed in this procedure.

:aname – The name of the association being removed from the application server.

The association name and application server name combination must be in the database.

The open parameter value in the association assigned to the application server specified in the dlt-as command must be no. This can be verified with the rtrv-assoc command. Use the chg-assoc command to change the value of the open parameter.

If the association is the only association assigned to the application server, the application server is removed from the database. The application server cannot be removed from the database if it is assigned to a routing key. This can be verified with the rtrv-appl-rtkey command.

Canceling the RTRV-AS, RTRV-ASSOC, and RTRV-APPL-RTKEY Commands

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-as, rtrv-assoc, or rtrv-appl-rtkey commands were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-as, rtrv-assoc, or rtrv-appl-rtkey commands were entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-as, rtrv-assoc, or rtrv-appl-rtkey commands were entered, from another terminal other that the terminal where the rtrv-as, rtrv-assoc, or rtrv-appl-rtkey 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 Manual User's Guide.

  1. Display the application servers in the database using the rtrv-as command.
    This is an example of possible output. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   10      assoc1
                                      assoc2
                                      assoc3
                                      assoc5
                                      assoc6

as2               OVERRIDE    10      assoc7
as3               LOADSHARE   10      assoc4

AS table is (3 of 250) 1% full.
  2. Display the associations to be removed from the application server using the rtrv-assoc command and specifying the association name shown in the rtrv-as output in 1.
    For this example, enter this command.

    rtrv-assoc:aname=assoc1

    This is an example of possible output. 

    
rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc1
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  M3UA          VER         M3UA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    1030          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as1

IP Appl Sock table is (4 of 4000) 1% full
Assoc Buffer Space Used (16 KB of 800 KB) on LOC = 1203
  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 shown in2isno, continue the 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. If the association is the only association assigned to the application server, the application server is removed from the database.

    Note:

    If the application server specified in this procedure contains more than one association, continue this procedure with 5.

    The application server cannot be removed from the database if it is assigned to a routing key. Verify the routing keys that the application server is assigned to by entering the rtrv-appl-rtkey command with the application server name that will be specified in 5 and the display=all parameter. For this example, enter this command.

    rtrv-appl-rtkey:asname=as1:display=all

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

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE       LOC
----------   6-024-7      5 ---   1-057-4      150        175        STATIC

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as1    
                                         
        ANAMES
        assoc1           assoc2           assoc3           assoc5
        assoc6

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE       LOC
----------   2-100-7      6 --- -----------    ---------- ---------- STATIC

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as1    
                                         
        ANAMES
        assoc1           assoc2           assoc3           assoc5
        assoc6

STATIC Route Key table is (7 of 2000) 1% full
STATIC Route Key Socket Association table is (7 of 32000) 1% full

    If the application server is assigned to any routing keys, remove the routing keys referencing the application server by performing the Removing a Routing Key Containing an Application Server procedure.

  5. Remove the association from the application server from the database using the dlt-as command.

    For this example, enter this command.

    dlt-as:asname=as1:aname=assoc1

    Note:

    If the association being removed from the application server is the only association assigned to the application server, the application server is removed from the database.
    This is an example of possible inputs and outputs: 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
DLT-AS:  MASP A - COMPLTD;
  6. Verify the changes using the rtrv-as command with the application server name specified in 5.

    For this example, enter this command.

    rtrv-as:asname=as1

    This is an example of possible output. 

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

AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   10      assoc2
                                      assoc3
                                      assoc5
                                      assoc6

AS table is (3 of 250) 1% full.
  7. Change the value of the open parameter to yes by specifying the chg-assoc command with the open=yes parameter.

    Note:

    If the value of the open parameter was not changed in3, continue this procedure with8.

    For this example, enter this command.

    chg-assoc:aname=assoc1: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;
  8. 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 4-32 Removing an Association from an Application Server



Sheet 1 of 2



Sheet 2 of 2

4.26 Removing a Routing Key Containing an Application Server

This procedure is used remove a static key from the database using the dlt-appl-rtkey command. For more information about static and dynamic routing keys, see Understanding Routing for SS7IPGW and IPGWI Applications.

The dlt-appl-rtkey command uses these parameters.

:dpc/dpca/dpci/dpcn/dpca24 – The destination point code value that is used to filter incoming MSUs.

:opc/opca/opci/opcn/opcn24 - The originating point code value that is used to filter incoming MSUs. This parameter must not specify a cluster route. This parameter must not specify a cluster route. This parameter is only valid when the si parameter value is set to 4, 5, or 13. This parameter is required if si=4, 5, or 13 and type=full.

Note:

See the “Point Code Formats” section in Database Administration - SS7 User's Guide for a definition of the point code types that are used on the EAGLE and for a definition of the different formats that can be used for ITU national point codes.

:si – The service indicator value that is used to filter incoming MSUs. The range of values for the service indicator parameter (si) can be a numerical value from 0 to 15, or for selected service indicator values, a text string can be used instead of numbers. Table 4-14 shows the text strings that can be used in place of numbers for the service indicator values.

Table 4-14 Service Indicator Text String Values

Service Indicator Value Text String Service Indicator Value Text String
0 snm 4 tup
1 regtest 5 isup
2 spltst 13 qbicc
3 sccp    

:ssn – The subsystem value that is used to filter incoming MSUs. The ssn parameter is only valid when the si parameter value is set to 3 or sccp.

:cics - The starting circuit identification code that is used to filter incoming MSUs. Specify with cice to delete routing keys with the circuit identification code or range of circuit identification codes. The cics parameter is only valid when the si parameter value is set to 4, 5, or 13. The cics is required if si=4, 5, or 13 and type=full.

:cice - The ending circuit identification code that is used to filter incoming MSUs. Specify with cics to delete routing keys with the circuit identification code or range of circuit identification codes. The cice parameter is only valid when the si parameter value is set to 4, 5, or 13. The cics is required if si=4, 5, or 13 and type=full.

:type - Identifies the type of routing key that is being deleted. One of three values, type = full/partial/default. If type is not explicitly specified, type = full is assumed.

:asname - Application server (AS) name.

:rcontext – The routing context parameter value assigned to the routing key.

The parameter combinations used by the dlt-appl-rtkey command are based on the type of routing key and the service indicator value in the routing key. The parameter combinations are shown in Table 4-15 .

Table 4-15 Routing Key Parameter Combinations for Removing Routing Keys

Full Routing Key SI=3 (SCCP) (See Notes 1, 3, and 4) Partial Routing Key SI=3 (SCCP) (See Notes 1, 3, and 4) Full Routing Key SI=4 (TUP), 5 (ISUP), 13 (QBICC) (See Notes 1, 3, and 4) Partial Routing Key SI=4 (TUP), 5 (ISUP), 13 (QBICC) (See Notes 1, 3, and 4) Full Routing Key Other SI Values (See Notes 1, 3, and 4) Partial Routing Key Other SI Values (See Notes 1, 3, and 4) Default Routing Key (See Notes 1, 3, and 4)

dpc

type=partial

dpc

type=partial

dpc

type=partial

type=default

si=3 (See Note 1)

dpc (See Note 2)

si=4, 5, 13 (See Note 1)

dpc (See Note 2)

si=value other than 3, 4, 5, 13 (See Note 1)

dpc (See Note 2)

asname

ssn

si=3 (See Notes 1 and 2)

opc

si=4, 5, 13 (See Notes 1 and 2)

type=full

si=value other than 3, 4, 5, 13 (See Notes 1 and 2)

rcontext (See Notes 3 and 4)

type=full

asname

cics

opc (See Note 2)

asname

asname

 
asname rcontext (See Notes 3 and 4)

cice

asname

rcontext (See Notes 3 and 4) rcontext (See Notes 3 and 4)  
rcontext (See Notes 3 and 4)  

type=full

rcontext (See Notes 3 and 4)      
   

asname

       
    rcontext (See Notes 3 and 4)        

Notes:

1. The values for these parameters must be entered exactly as shown in the rtrv-appl-rtkey command output for the routing key being removed. However, text strings can be used in place of some numerical service indicator values. See Table 4-14 for a list of these text strings.

2. These parameters are optional for partial routing keys, but at least one these parameters must be specified with the dlt-appl-rtkey command.

3. If the routing key contains a numerical value in the RCONTEXT column in the rtrv-appl-rtkey output, the dlt-appl-rtkey command can be specified with only the rcontext parameter and value instead of the dpc, si, ssn, opc, cics, cice, or type parameters and values to remove the routing key.

4. If the routing key contains dashes in the RCONTEXT column in the rtrv-appl-rtkey output, the dpc, si, ssn, opc, cics, cice, or type parameters and values must be used with the dlt-appl-rtkey command to remove the routing key.

Canceling the RTRV-APPL-RTKEY Command

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-appl-rtkey command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-appl-rtkey command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-appl-rtkey commands were entered, from another terminal other that the terminal where the rtrv-appl-rtkey 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 routing key information in the database by entering the rtrv-appl-rtkey command.

    The following is an example of the possible output. 

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

RCONTEXT    DPC          SI  ADPTR  ASNAME           TYPE
----------  123-234-123   5  M3UA   as9              FULL
----------  123-234-123   5  M3UA   as9              FULL
1000        005-005-001   5  SUA    as10             FULL
2000        005-005-001   5  SUA    as10             FULL
----------  006-006-001   5  M3UA   as11             FULL
----------  006-006-001   5  M3UA   as11             FULL

RCONTEXT    DPCI         SI  ADPTR  ASNAME           TYPE
----------    2-100-7     6  M3UA   as4              FULL
100           3-137-6     6  SUA    as1              FULL
225           4-035-7     5  M3UA   as7              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-7     5  M3UA   as8              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-8     3  M3UA   as3              FULL
----------    6-006-8     5  M3UA   as5              FULL
----------    6-024-7     5  M3UA   as4              FULL
----------    6-024-7     5  M3UA   as4              FULL
300           7-008-7     6  SUA    as6              FULL

RCONTEXT    DPC          SI  ADPTR  ASNAME           TYPE
----------  ***********  **  M3UA   as123            DEFAULT

STATIC Route Key table is (15 of 2000) 1% full
STATIC Route Key Socket Association table is (15 of 32000) 1% full

    If a routing context value is not assigned to the the routing key being removed in this procedure, continue the procedure with 3.

  2. Display the specific routing key information for the routing key being removed from the database by entering the rtrv-appl-rtkey command with the display=all parameter and the RCONTEXT values shown in the rtrv-appl-rtkey output in 1 for the routing key being removed.
    For this example, enter this command.

    rtrv-appl-rtkey:rcontext=225

    This is an example of the possible output. 

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

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
225          4-035-7      5 ---   2-007-3      2000       3000

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as7    
                                         
    ANAMES
    assoc15

STATIC Route Key table is (15 of 2000) 1% full
STATIC Route Key Socket Association table is (15 of 32000) 1% full

    After this step is performed, continue the procedure with 4.

  3. Display the specific routing key information for the routing key being removed from the database by entering the rtrv-appl-rtkey command with the display=all parameter and the DPC, SI, andTYPE values shown in the rtrv-appl-rtkey output in 1 for the routing key being removed. For this example, enter this command.

    rtrv-appl-rtkey:dpci=6-006-6:si=3:display=all:type=full

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
----------   6-006-6      3 170 -----------    ---------- ----------

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as2    
                                         
    ANAMES
    assoc1

STATIC Route Key table is (15 of 2000) 1% full
STATIC Route Key Socket Association table is (15 of 32000) 1% full
  4. Display the associations assigned to the routing key by entering the rtrv-assoc parameter with the association name shown in either 2 or 3. For this example, enter these commands.

    rtrv-assoc:aname=assoc1

    This is an example of possible output. 

    
rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc1
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  M3UA          VER         M3UA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    1030          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as2

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

    rtrv-assoc:aname=assoc15

    This is an example of possible output. 

    
rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc15
      LOC      1205          IPLNK PORT  A          LINK  A
      ADAPTER  M3UA          VER         M3UA RFC
      LHOST    gw115.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    2000          RPORT       2000
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as7

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

    Repeat this step for all the associations shown in 2 or 3.

  5. Change the open parameter value of the association to no by using the chg-assoc command.

    Note:

    If theopen parameter value of all the associations shown in4isno, continue the procedure with6.

    For example, enter these commands.

    chg-assoc:aname=assoc1:open=no

    chg-assoc:aname=assoc15:open=no

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

    
rlghncxa03w 06-10-28 21:18:37 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD

    Caution:

    TheIP connections using the associations specified in this step will not be able to carry any traffic when theopen parameter is changed tono.

    Repeat this step for all the associations shown in 4 that contain the open=yes parameter value.

  6. Remove the routing key information from the database by entering the dlt-appl-rtkey command.
    The parameters required for the dlt-appl-rtkey command are determined by the type of routing key being added and the service indicator value in the routing key. See Table 4-15 for the parameter combinations that can be used for the type of routing key being added to the database. For example, enter these commands.

    dlt-appl-rtkey:dpci=6-006-6:si=3:ssn=170:asname=as2

    dlt-appl-rtkey:rcontext=225

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

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
DLT-APPL-RTKEY: MASP A - COMPLTD
  7. Verify the changes by entering the rtrv-appl-rtkey command with the routing key parameters specified in 6 (dpc, si, opc, cics, cice, ssn, asname, and type, and loc, as applicable). For this example, enter these commands.

    rtrv-appl-rtkey:dpci=6-006-6:si=3:ssn=170:asname=as2

    The following is an example of the possible output. 

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

No matching entries found

STATIC Route Key table is (12 of 2000) 1% full
STATIC Route Key Socket Association table is (6 of 32000) 1% full

    rtrv-appl-rtkey:rcontext=225

    The following is an example of the possible output. 

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

No matching entries found

STATIC Route Key table is (12 of 2000) 1% full
STATIC Route Key Socket Association table is (6 of 32000) 1% full

    Note:

    If5was not performed, continue the procedure with9.
  8. Change the open parameter value of the associations that were changed in 5 to yes by using the chg-assoc command.
    For example, enter these commands.

    chg-assoc:aname=assoc1:open=yes

    chg-assoc:aname=assoc15:open=yes

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

    
rlghncxa03w 06-10-28 21:18:37 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD

    Repeat this step for all the associations that were changed in 9.

  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 4-33 Removing a Routing Key Containing an Application Server



Sheet 1 of 2



Sheet 2 of 2

4.27 Removing a Network Appearance

This procedure removes the network appearance from the database using the dlt-na command with these parameters.

:na – the 32-bit value of the network appearance, from 0 to 4294967295.

:type – the network type of the network appearance, ansi (ANSI), itui (ITU-I), itun (14-bit ITU-N), itun24 (24-bit ITU-N), ituis (ITU-I Spare), ituns (14-bit ITU-N Spare).

:gc – the specific ITU-N group code associated with the network appearance.

Specifying the gc parameter removes the specific network appearance containing the na and gc parameter values.

Specifying the type=itun or type=ituns parameter without the gc parameter removes all 14-bit ITU-N or 14-bit ITU-N spare network appearances containing the specified na parameter value.

  1. Display the network appearances in the database with the rtrv-na command.
    This is an example of the possible output. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
TYPE    GC           NA
ANSI    --          100
ITUI    --         1000
ITUN    uk       150000
ITUN    fr   4000000000
ITUN    ge   1000000000
ITUN24  --            3
ITUIS   --         2000
ITUNS   sp         5000
  2. Remove the network appearance from the database with the dlt-na command.
    For this example, enter these commands.

    dlt-na:na=100:type=ansi

    dlt-na:na=4000000000:type=itun:gc=fr

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

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
DLT-NA:  MASP A - COMPLTD
  3. Verify the changes using the rtrv-na command.
    This is an example of possible output. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
TYPE    GC           NA
ITUI    --         1000
ITUN    uk       150000
ITUN    ge   1000000000
ITUN24  --            3
ITUIS   --         2000
ITUNS   sp         5000
  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 4-34 Removing a Network Appearance



4.28 Changing IETF M3UA and SUA Components

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

4.29 Changing IP Options

Use this procedure to change the IP options defined by these parameters: getcomm, setcomm, snmpcont, srkq, trapcomm, ipgwabate, and uameasusedftas.

The chg-sg-opts command also contains the sctpcsum parameter. Perform the one of these procedures to change the sctpcsum parameter value.

:getcomm – The community name used to validate SNMP Get and GetNext requests. This value applies to each IP card SNMP agent.

:setcomm – The community name used to validate SNMP Set requests. This value applies to each IP card SNMP agent.

:snmpcont – The system contact information for each IP card SNMP agent, used to define the sysContact object in the SNMP MIB II System Group.

:srkq – The static routing key quantity used to specify the maximum number of static routing key entries in the Routing Key table of each ss7ipgw and ipgwi card.

:trapcomm – The community name used when sending SNMP traps. This value applies to each IP card SNMP agent.

:ipgwabate – enables (ipgwabate=yes) or disables (ipgwabate=no) SS7 congestion abatement procedures for IPGWx signaling links (signaling links assigned to cards running the ss7ipgw or ipgwi applications). The default value for this parameter is no.

:uameasusedftas - specifies whether UA measurements are pegged against the default application server or against the application server shown by the routing context. The values for this parameter are yes and no. The system default value for this parameter is yes.
  • yes - UA measurement registers are pegged against the default application server.
  • no - UA measurements are pegged against the application server shown by the routing context.

The maximum value of the srkq parameter is 2500.

The value specified for the srkq parameter cannot be less than the current number of provisioned routing keys. The number of routing keys that are currently provisioned is shown in the rtrv-appl-rtkey or rtrv-tbl-capacity command outputs.

The values of the snmpcont, getcomm, setcomm, and trapcomm parameters are a string of up to 32 characters that is not case sensitive. If the character string contains characters other than alphanumeric characters, the character string must be enclosed in single quotes.

  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 08-04-28 21:17:37 GMT EAGLE5 38.0.0
SRKQ:           250
SNMPCONT:       john doe 555-123-4567
GETCOMM:        public
SETCOMM:        private
TRAPCOMM:       public
SCTPCSUM:       crc32c
IPGWABATE:      NO
UAMEASUSEDFTAS  YES

    If the srkq parameter value will not be changed, continue the procedure with 3.

    If the srkq parameter value will be changed, verify the number of routing keys that are currently provisioned by performing 2.

  2. Enter the rtrv-tbl-capacity command to verify the number of routing keys that are currently provisioned.

    The following is an example of the possible output. 

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

RTEKEY   table is (       53 of      2500)   2% 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, see thertrv-tbl-capacity command description inCommands User's Guide.

    The number of routing keys that are currently provisioned is shown in the RTEKEY row of the rtrv-tbl-capacity output. In this example, there are 53 routing keys provisioned in the database. The new srkq parameter value cannot be less than 53.

  3. Change the IP options in the database using the chg-sg-opts command.

    For this example, enter this command.

    chg-sg-opts:srkq=200:ipgwabate=yes:uameasusedftas=no

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

    
rlghncxa03w 08-04-28 21:18:37 GMT EAGLE5 38.0.0
CHG-SG-OPTS: MASP A - COMPLTD
  4. Verify the new IP options in the database by entering the rtrv-sg-opts command.

    The following is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:19:37 GMT EAGLE5 38.0.0
SRKQ:           200
SNMPCONT:       john doe 555-123-4567
GETCOMM:        public
SETCOMM:        private
TRAPCOMM:       public
SCTPCSUM:       crc32c
IPGWABATE:      YES
UAMEASUSEDFTAS  NO
  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 4-35 Changing IP Options



4.30 Changing the Attributes of a M3UA or SUA Association

This procedure is used to change the values of the attributes of a M3UA or SUA association, assigned to cards that are running the SS7IPGW or IPGWI applications, using the chg-assoc command and the following parameters.

Table 4-16 Change M3UA and SUA Association Parameters

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

If you wish to change the attributes of M3UA associations assigned to cards that are running the IPSG application, perform.

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.

:adapter – The adapter layer for this association, either m3ua or sua. The adapter parameter is optional. The default value for the adapter parameter in this procedure is m3ua.

: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 M3UA or SUA 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 M3UA or SUA 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.

:uaps – The UA parameter set value being assigned to either an M3UA or SUA association.

:rtxthr – The retransmission threshold for the association. The rtxthr parameter value indicates the number of retransmissions that can occur on the association that when exceeded will generate UAM 0537, Ethernet Error Threshold Exceeded. 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.

: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 adapter parameter value cannot be changed if the association is assigned to an application server. This can be verified with the rtrv-as command. If the association is assigned to any application servers, perform Removing an Association from an Application Server to remove the association from the application servers.

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

If the card’s application is either SS7IPGW or IPGWI, the signaling link being assigned to the association must be in service. This state is shown in the rept-stat-slk output with the entries IS-NR in the PST field and Avail in the SST field.

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          1205 A     A    M3UA    2048  2048  YES  YES
assoc3          1205 A     A    M3UA    3000  3000  YES  YES
assoc5          1205 A     A    M3UA    1500  3000  YES  YES

    Select an association whose adapter value is M3UA or SUA. If the card shown in the CARD LOC column contains any SUA associations, continue the procedure with 3. If the card contains only M3UA associations, continue the procedure with 2.

  2. Enter the rtrv-card command with the location of the card that is hosting the M3UA 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       SS7IPGW  e5e6a       A    0

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

    If the application assigned to the card is SS7IPGW or IPGWI, continue the procedure with 3.

  3. Continue the procedure by performing one of these actions.
    If the application assigned to the card is SS7IPGW or IPGWI, shown in the APPL column, and the values of any of these parameters are being changed: lport, rhost, rport, adapter, rmode, rmin, rmax, rtimes, cwmin, istrms, ostrms, or uaps, continue the procedure by performing one of these actions.
    • If the open parameter value for the association is yes, continue the procedure with 5.
    • If the open parameter value for the association is no, continue the procedure with 6.
    If the application assigned to the card is SS7IPGW or IPGWI, shown in the APPL column, and only the values of the alw, open, or rtxthr parameters are being changed, continue the procedure by performing one of these actions.
    • 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 12.
    • If the value of the rtxthr parameter is being changed, continue the procedure with 6.
    • 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 2 was performed, perform one of these actions.
      • If a signaling links is assigned to the card, entries area shown in the LSET NAME and LINK columns of the rtrv-card output in 2. 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 12.
        • If the value of the rtxthr parameter is being changed, continue the procedure with 6.
      • 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 IPGWx Signaling Link to assign an IPGWx 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 12.
        • If the value of the rtxthr parameter is being changed, continue the procedure with 6.
    • If the value of the open parameter value is being changed to yes, and 2 was not performed, continue the procedure with 4.
  4. Display the signaling link that is assigned to the card containing the association that is being changed by entering the rtrv-slk command with the location of the card. For this example, enter this command.

    rtrv-slk:loc=1205

    This is an example of possible output. 

    rlghncxa03w 08-04-25 14:02:39 EST  38.0.0
rtrv-slk:loc=1101
Command entered at terminal #4.

LOC  LINK LSN         SLC TYPE
1205 A    e5e6a       0   SS7IPGW

    If a signaling link is shown in this step, perform one of these actions.

    • If only the alw parameter is being specified with the open=yes parameter, continue the procedure with 12.
    • If the value of the rtxthr parameter is being changed, continue the procedure with 6.
    If a signaling link is not shown in this step, perform Adding an IPGWx Signaling Link to assign an IPGWx 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 12.
    • If the value of the rtxthr parameter is being changed, continue the procedure with 6.
  5. 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;
  6. Display the association being changed by entering the rtrv-assoc command with the aname parameter specified in 5 or selected in 1.
    For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of the possible output. 

    
rlghncxa03w 09-05-28 21:14:37 GMT EAGLE5 41.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M3UA          VER         M3UA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    remotehost1
       ARHOST   ---
       LPORT    2048          RPORT       2048
       ISTRMS   2             OSTRMS      2          BUFSIZE  200
       RMODE    LIN           RMIN        120        RMAX     800
       RTIMES   10            CWMIN       3000       UAPS     10
       OPEN     No            ALW         YES        RTXTHR   2000
       RHOSTVAL RELAXED

      ASNAMES
      as1              as4              as6

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (800 KB of 800 KB) on LOC = 1205
    Continue the procedure by performing one of these steps.
    • If only the rtxthr parameter value is being changed, continue the procedure with 12.
    • If the adapter, uaps, or cwmin parameter values are not being changed, continue the procedure with 10 .
    • If the adapter parameter value is being changed, continue the procedure with 7.
    • If the uaps parameter value is being changed, but the adapter parameter value is not being changed, continue the procedure with 8.
    • If the cwmin parameter value is being changed, but the adapter and uaps parameter values are not being changed, continue the procedure with 9.
  7. 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.

    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 assigned to any application servers, performRemoving an Association from an Application Server to remove the association from the application servers.

    Continue the procedure by performing one of these steps.
    • If the uaps or cwmin parameter values are not being changed, continue the procedure with 10 .
    • If the uaps parameter value is being changed, continue the procedure with 8.
    • If the cwmin parameter value is being changed, but the uaps parameter value is not being changed, continue the procedure with 9.
  8. Verify the values of the UA parameter set you wish to assign to the association by entering the rtrv-uaps command with the desired parameter set.

    Note:

    If theuaps parameter will not be specified with thechg-assoc command, and the adapter parameter value is being changed to eitherm3ua orsua, theUA parameter set 10 will be assigned to the association.

    For this example, enter this command.

    rtrv-uaps:set=3

    This is an example of possible output. 

    
rlghncxa03w 10-07-28 09:12:36 GMT EAGLE5 42.0.0
SET  TIMER      TVALUE  PARM      PVALUE
 3       1          10     1           3
 3       2        3000     2           0
 3       3       10000     3           1
 3       4        5000     4           0
 3       5           0     5           0
 3       6           0     6           0
 3       7           0     7           0
 3       8           0     8           0
 3       9           0     9           0
 3      10           0    10           0

TIMER 2: False IP Connection Congestion Timer, max time an
         association can be congested before failing due to false
         congestion. SS7IPGW and IPGWI applications enforce
         0-30000(ms). Not supported on IPSG application.
TVALUE : Valid range = 32-bits

TIMER 3: UA HeartBeat Period Timer T(beat), time (ms) between sending
         of BEAT msgs by NE. IPSG, SS7IPGW and IPGWI applications
         enforce 100(ms)-60000(ms).
TVALUE : Valid range = 32-bits

TIMER 4: UA HeartBeat Received Timer T(beat ack), timeout period for
         response BEAT ACK msgs by NE. IPSG, SS7IPGW and IPGWI
         applications enforce 100(ms)-10000(ms).
TVALUE : Valid range = 32-bits

PARM  1: ASP SNM options.  Each bit is used as an enabled/disabled
         flag for a particular ASP SNM option. Not supported on IPSG
         application.
PVALUE : Valid range = 32-bits
         BIT                                  BIT VALUE
         0=Broadcast                          0=Disabled , 1=Enabled
         1=Response Method                    0=Disabled , 1=Enabled
         2-5=Reserved
         6=Broadcast Congestion Status Change 0=Disabled , 1=Enabled
         7-31=Reserved

PARM  2: ASP/AS Notification options.  Each bit is used as an
         enabled/disabled flag for a particular ASP/AS
         Notification option.  Not supported on IPSG application.
PVALUE : Valid range = 32-bits
         BIT                                  BIT VALUE
         0=ASP Active Notifications           0=Disabled , 1=Enabled
         1=ASP Inactive Notifications         0=Disabled , 1=Enabled
         2=ASP AS State Query                 0=Disabled , 1=Enabled
         3-31=Reserved

PARM  3: UA Serviceability Options.  Each bit is used as an
         enabled/disabled flag for a particular UA Serviceability
         option. Supported on IPSG, SS7IPGW, and IPGWI applications.
         UA Graceful Shutdown supported on IPSG for M3UA only.
PVALUE : Valid range = 32-bits
         BIT                                  BIT VALUE
         0=UA Heartbeats                      0=Disabled , 1=Enabled
         1=UA Graceful Shutdown               0=Disabled , 1=Enabled 
         2-31=Reserved

PARM  4: SCTP Payload Protocol Indicator byte order option. Bit indicates 
         PPI value is RCV/TX in Big Endian or Little Endian byte format.  
         Supported on IPSG-M2PA associations only.
PVALUE : Valid range = 32-bits
         BIT                               BIT VALUE
         0=Payload Protocol Indicator      0=Big Endian , 1=Little Endian
         1-31=Reserved

    If the UA parameter set you wish to assign to the association does not contain the desired values, performChanging a UA Parameter Set to change the desired parameter set values.

    Caution:

    Changing aUA parameter set may affect the performance of any associations using the parameter set being changed.
    Continue the procedure by performing one of these steps.
    • If the cwmin parameter value is not being changed, continue the procedure with 10 .
    • If the cwmin parameter value is being changed, continue the procedure with 9.
  9. 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, continue the procedure with 10 .
    • 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 performChanging the Buffer Size of a M3UA or SUA Association 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 with 10 .
  10. 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 12.

    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 12. If the association does not have a primary remote host, continue the procedure with 10.

  11. 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;
  12. 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 the chg-assoc command.
    1. If any optional parameters are not specified with the chg-assoc command, those values are not changed.
    2. The value of the rmin parameter must be less than or equal to the rmax parameter value.
    3. 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.
    4. 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.

    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 with14.
  13. 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;
  14. Verify the changes using the rtrv-assoc command specifying the association name specified in 12 and 13.
    For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of possible output.

    Note:

    If theRemoving an Association from an Application Serverprocedure in7was not performed, continue the procedure with16.
  15. Assign the association changed in 12 to all applicable application servers by performing one of these procedures:
  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.
    If you wish to change the lhost, alhost, or bufsize values of the M3UA or SUA association, perform one of these procedures.

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

Figure 4-36 Changing the Attributes of a M3UA or SUA Association



Sheet 1 of 8



Sheet 2 of 8



Sheet 3 of 8



Sheet 4 of 8



Sheet 5 of 8



Sheet 6 of 8



Sheet 7 of 8



Sheet 8 of 8

4.31 Changing the Buffer Size of a M3UA or SUA Association

This procedure is used to change the buffer size of a M3UA or a SUA association, assigned to cards that are running the SS7IPGW or IPGWI applications, using the chg-assoc command. If you wish to change the attributes of M3UA 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 IP 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 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          1205 A     A    M3UA    2048  2048  YES  YES
assoc3          1205 A     A    M3UA    3000  3000  YES  YES
assoc5          1205 A     A    M3UA    1500  3000  YES  YES

    Select an association whose adapter value is M3UA or SUA. If the card shown in the CARD LOC column contains any SUA associations, and the open parameter value of the association is no, continue the procedure with 4. If the open parameter value of the association is yes, continue the procedure with 3

    If the card contains only M3UA associations, continue the procedure with 2.

  2. Enter the rtrv-card command with the location of the card that is hosting the M3UA 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       SS7IPGW  e5e6a       A    0
    If the application assigned to the card is SS7IPGW or IPGWI, 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 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 or the association selected in 1.
    For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of the possible output. 

    
rlghncxa03w 09-05-28 21:14:37 GMT EAGLE5 41.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M3UA          VER         M3UA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    remotehost1
       ARHOST   ---
       LPORT    2048          RPORT       2048
       ISTRMS   2             OSTRMS      2          BUFSIZE  200
       RMODE    LIN           RMIN        120        RMAX     800
       RTIMES   10            CWMIN       3000       UAPS     10
       OPEN     No            ALW         YES        RTXTHR   2000
       RHOSTVAL RELAXED

      ASNAMES
      as1              as4              as6

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (800 KB of 800 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 08-04-28 21:14:37 GMT EAGLE5 38.0.0
                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
assoc2          1205 A     A    M3UA    2048  2048  YES  YES
assoc3          1205 A     A    M3UA    3000  3000  YES  YES
assoc5          1205 A     A    M3UA    1500  3000  YES  YES

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (800 KB of 3200 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. 

    
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M3UA          VER         M3UA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    remotehost1
       ARHOST   ---
       LPORT    2048          RPORT       2048
       ISTRMS   2             OSTRMS      2          BUFSIZE  200
       RMODE    LIN           RMIN        120        RMAX     800
       RTIMES   10            CWMIN       3000       UAPS     10
       OPEN     YES           ALW         YES        RTXTHR   2000
       RHOSTVAL RELAXED

      ASNAMES
      as1              as4              as6

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

    rtrv-assoc:aname=assoc3

    This is an example of the possible output. 

    
 ANAME assoc3
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M3UA          VER         M3UA 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   10000
       RHOSTVAL RELAXED

      ASNAMES
      as2              as3              as5

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

    rtrv-assoc:aname=assoc5

    This is an example of the possible output. 

    
 ANAME assoc5
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M3UA          VER         M3UA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    remotehost3
       ARHOST   ---
       LPORT    1500          RPORT    3000
       ISTRMS   2             OSTRMS   2             BUFSIZE  200
       RMODE    LIN           RMIN     120           RMAX     800
       RTIMES   10            CWMIN    3000          UAPS     10
       OPEN     YES           ALW      YES           RTXTHR   10000
       RHOSTVAL RELAXED

      ASNAMES
      as2              as3              as5

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (800 KB of 800 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 a M3UA or SUA 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=200

    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;
  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 a M3UA or SUA 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=250

    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;

    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 08-04-28 09:12:36 GMT EAGLE5 38.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 09-05-28 09:12:36 GMT EAGLE5 41.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M3UA          VER         M3UA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    gw200.nc-tekelec.com
       ARHOST   ---
       LPORT    2048          RPORT       3000
       ISTRMS   2             OSTRMS      2          BUFSIZE  250
       RMODE    LIN           RMIN        120        RMAX     800
       RTIMES   10            CWMIN       3000       UAPS     10
       OPEN     YES           ALW         YES        RTXTHR   10000
       RHOSTVAL RELAXED

      ASNAMES
      as1              as4              as6

IP Appl Sock table is (8 of 4000) 1% full
Assoc Buffer Space Used (650 KB of 800 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 other attributes of the M3UA or SUA association, perform one of these procedures.

    If you do not wish to change other attributes of the M3UA or SUA association, this procedure is finished.

Figure 4-37 Changing the Buffer Size of an M3UA or SUA Association



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

4.32 Changing the Host Values of a M3UA or SUA Association

This procedure is used to change the host values of a M3UA or SUA association, assigned to cards that are running the SS7IPGW or IPGWI applications, using the chg-assoc command. If you wish to change the attributes of M3UA 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.

:link – The signaling link on the IPGWx card. The value for the link parameter for M3UA or SUA associations is A.

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, either m3ua or sua. The adapter parameter is optional. The default value for the adapter parameter in this procedure is m3ua.

:alhost – The alternate local host name, shown in the rtrv-ip-host 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.

:uaps – The UA parameter set value being assigned to either an M3UA or SUA association.

At least one optional parameter is required.

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

The maximum number SCTP association to application server assignments that can be hosted by an IPGWx card (referenced by the lhost parameter of the association) is 50. For example, the IPGWx card currently contains 38 SCTP association to application server assignments. The SCTP association to application server assignments could be one SCTP association assigned to 38 application servers, two SCTP associations assigned to 19 application servers, or any combination of SCTP associations assigned to application servers that add up to 38. The SCTP association to application server assignments can be verified with the rtrv-assoc:lhost=<local host name> and rtrv-as:aname=<association name> commands.

Table 4-17 Examples of IPGWx Card Provisioning Limits

Number of Associations hosted by the IPGWx card Number of Application Servers each Association is Assigned to * Total Association - Application Server Assignments maintained by the IPGWx card

1

50

50

50

1

50

25

1

50

25

2

50

0

0

50

38

1

38

19

2

38

* The EAGLE can contain a maximum of 250 application servers.

The EAGLE can contain a maximum of 4000 connections.

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

If the card’s application is either SS7IPGW or IPGWI, the signaling link being assigned to the association must be in service. This state is shown in the rept-stat-slk output with the entries IS-NR in the PST field and Avail 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          1205 A     A    M3UA    2048  2048  YES  YES
assoc3          1205 A     A    M3UA    3000  3000  YES  YES
assoc5          1205 A     A    M3UA    1500  3000  YES  YES
    Select an association whose adapter value is M3UA or SUA. If the card shown in the CARD LOC column contains any SUA associations, 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 card contains only M3UA associations, continue the procedure with 2.

  2. Enter the rtrv-card command with the location of the card that is hosting the M3UA 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       SS7IPGW  e5e6a       A    0

    If the application assigned to the card is IPSG, perform the Changing the Host Values of an IPSG Association procedure.

    If the application assigned to the card is SS7IPGW or IPGWI, 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.
  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 or the association selected in 1.

    For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of the possible output. 

    
rlghncxa03w 09-05-28 21:14:37 GMT EAGLE5 41.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M3UA          VER         M3UA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    remotehost1
       ARHOST   ---
       LPORT    2048          RPORT       2048
       ISTRMS   2             OSTRMS      2          BUFSIZE  200
       RMODE    LIN           RMIN        120        RMAX     800
       RTIMES   10            CWMIN       3000       UAPS     10
       OPEN     No            ALW         YES        RTXTHR   2000
       RHOSTVAL RELAXED

      ASNAMES
      as1              as4              as6

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

    If the association shown in this step is an M2PA association, continue the procedure with 5.

    If the association shown in this step is an M3UA or SUA 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 using 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

REMOTE IPADDR   REMOTE HOST
150.1.1.5       NCDEPTECONOMIC_DEVELOPMENT. SOUTHEASTERN_COORIDOR_ASHVL. GOV

IP Host table is (11 of 4096) .26% 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 07-05-28 21:14:37 GMT EAGLE5 37.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.

    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     SS7IPGW   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.
  8. Display the associations assigned to the local host that will be assigned to the association being configured in this procedure by entering the rtrv-assoc command with the lhost parameter.
    For this example, enter this command.

    rtrv-assoc:lhost="IPNODE2-1205"

    This is an example of the possible output. 

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

                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
assoc2          1205 A     A    M3UA    2048  2048  YES  YES
assoc3          1205 A     A    M3UA    3000  3000  YES  YES
assoc5          1205 A     A    M3UA    1500  3000  YES  YES

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (600 KB of 3200 KB) on LOC = 1205
  9. Display the application servers that the associations shown in 8 are assigned to by entering rtrv-as command with the names of the associations shown in 8.

    For this example, enter these commands.

    rtrv-as:aname=assoc2

    This is an example of the 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

    rtrv-as:aname=assoc3

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:14:37 GMT EAGLE5 38.0.0
AS Name           Mode        Tr ms   Association Names
as2               LOADSHARE   2000    assoc3

as3               LOADSHARE   2000    assoc3

as5               LOADSHARE   2000    assoc3

AS Table is (6 of 250) 2% full

    rtrv-as:aname=assoc5

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:14:37 GMT EAGLE5 38.0.0
AS Name           Mode        Tr ms   Association Names
as2               LOADSHARE   2000    assoc5

as3               LOADSHARE   2000    assoc5

as5               LOADSHARE   2000    assoc5

AS Table is (6 of 250) 2% full

    The maximum number of SCTP association to application server assignments that can be hosted by an IPGWx card (referenced by the lhost parameter of the association) is 50.

    If the number of SCTP association to application server assignments (shown in this step) is less than 50, continue the procedure by performing one of these steps.
    • If the rept-stat-card command was not performed in 7, continue the procedure with 10.
    • If the rept-stat-card command was performed in 7, and the link value will not be changed, continue the procedure with Oracle.
    • If the rept-stat-card command was performed in 7, and the link value will be changed, continue the procedure with 11.

    If the number of SCTP association to application server assignments (shown in this step) is 50, the local host value cannot be used in this procedure. Repeat 5 and 6 and select another IP link and IP.

  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.

    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     SS7IPGW   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 link value will not be changed, continue the procedure with Oracle.
    • If the link value will be changed, continue the procedure with 11.
  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.

    For this example, enter this command.

    rtrv-slk:loc=1203

    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
1203  A    e5e6a         1  SS7IPGW

    If the required IPGWx signaling is shown in this step, continue the procedure with Oracle.

    If the required IPGWx signaling is not shown in this step, perform the Adding an IPGWx Signaling Link to add the required IPGWx signaling link. After the signaling link has been added, continue the procedure with Oracle.

  12. Change the association using the chg-assoc command.

    For this example, enter this command.

    chg-assoc:aname=assoc2:lhost=m3ua1:alhost=m3ua2:rhost=”gw200.nc-Oracle.com”

    These are the rules that apply to the chg-assoc command.
    • If any optional parameters are not specified with the chg-assoc command, those values are not changed.
    • E5-ENET cards can use the B Ethernet interface.
    • The number of association – application server assignments on an IPGWx card cannot exceed 50.
    • The EAGLE can contain a maximum of 4000 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.
    • 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 uaps parameter is not specified with the chg-assoc command, and the adapter parameter value is being changed to either m3ua or sua, the uaps parameter value defaults to UA parameter set 10 (uaps=10).
    • The port parameter can be used in place of the link parameter to specify the signaling link assigned to the 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.
  13. 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;
  14. Verify the changes using the rtrv-assoc command specifying the association name specified in Oracle and 13.

    For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of possible output. 

    
rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
 ANAME assoc2
       LOC      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M3UA          VER         M3UA RFC
       LHOST    m3ua1
       ALHOST   m3ua2
       RHOST    gw200.nc-tekelec.com
       ARHOST   ---
       LPORT    2048          RPORT       3000
       ISTRMS   2             OSTRMS      2          BUFSIZE  250
       RMODE    LIN           RMIN        120        RMAX     800
       RTIMES   10            CWMIN       3000       UAPS     10
       OPEN     YES           ALW         YES        RTXTHR   10000
       RHOSTVAL RELAXED

      ASNAMES
      as1              as4              as6

IP Appl Sock table is (8 of 4000) 1% full
Assoc Buffer Space Used (650 KB of 800 KB) on LOC = 1205
  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.
    If you wish to change other attributes the of the M3UA or SUA association, perform one of these procedures.

    If you do not wish to change the other attributes of the M3UA or SUA association, this procedure is finished.

Figure 4-38 Changing the Host Values of a M3UA or SUA Association



Sheet 1 of 6



Sheet 2 of 6



Sheet 3 of 6



Sheet 4 of 6



Sheet 5 of 6



Sheet 6 of 6

4.33 Configuring SCTP Retransmission Control for a M3UA or SUA Association

This procedure is used to gather the information required to configure the retransmission parameters for SUA associations and M3UA associations that are assigned to cards running either the SS7IPGW or IPGWI applications. Perform the Configuring an IPSG Association for SCTP Retransmission Control procedure to configure the retransmission parameters for M3UA associations assigned to IPSG cards. If any assistance is needed to configure the retransmission parameters for associations, contact the Customer Care Center. Refer to unresolvable-reference.html#GUID-1825DD07-2A6B-4648-859A-1258A0F9AC40 for the contact information.

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.

For associations assigned to the ss7ipgw or ipgwi applications, the value of the cwmin parameter must be less than or equal to 16384.

The Changing the Attributes of a M3UA or SUA Association procedure is used to change the values of these parameters. In addition to using the Changing the Attributes of a M3UA or SUA 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 a M3UA or SUA 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    M3UA    2000  1030  YES  YES

    If the association that is being removed in this procedure is an SUA association, continue the procedure with 3.

    If the association that is being removed in this procedure is an M3UA association, continue the procedure with 2.

  2. Enter the rtrv-card command with the location of the card that is hosting the M3UA 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       SS7IPGW  lsn1        A    0

    If the application assigned to the card is SS7IPGW or IPGWI, 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 09-05-28 21:14:37 GMT EAGLE5 41.0.0
 ANAME assoc1
       LOC      1201          IPLNK PORT  A          LINK  A
       ADAPTER  M3UA          VER         M3UA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    gw100.nc.tekelec.com
       ARHOST   ---
       LPORT    2000          RPORT       1030
       ISTRMS   2             OSTRMS      2          BUFSIZE  200
       RMODE    LIN           RMIN        120        RMAX     800
       RTIMES   10            CWMIN       3000       UAPS     10
       OPEN     YES           ALW         YES        RTXTHR   2000
       RHOSTVAL RELAXED

      ASNAMES
      as1              as4              as6

IP Appl Sock/Assoc table is (8 of 4000) 1% full
Assoc Buffer Space Used (800 KB of 800 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 are not to be changed, do not perform 5 through 8. This procedure is finished.

  5. Perform the Changing the Attributes of a M3UA or SUA 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 local 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 a M3UA or SUA 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 5, and the data retransmission counts shown in the sctp -a pass command output in 6 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 4-39 Configuring SCTP Retransmission Control for a M3UA or SUA Association



Sheet 1 of 2



Sheet 2 of 2

4.34 Changing an Application Server

This procedure is used change the characteristics of an existing application server using the chg-as command.

The chg-as command uses these parameters:

:asname – The name of the application server being changed.

:mode – The traffic mode assigned to the application server, either loadshare or override.

:tr – The application server recovery timer, 10 - 2000 milliseconds.

The mode parameter value cannot be changed unless the open parameter value of the all the associations assigned to the application server is set to no. This can be verified with the rtrv-assoc command.

The association assignments for an application server cannot be changed with this procedure. To change an association assignment for an application server, go to the Removing an Association from an Application Server procedure and remove the association from the application server, then perform one of these procedures to add another association to the application server:

Canceling the RTRV-AS and RTRV-ASSOC Commands

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-as or rtrv-assoc commands were entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-as or rtrv-assoc commands were entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-as or rtrv-assoc commands were entered, from another terminal other that the terminal where the rtrv-as or rtrv-assoc 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 application servers in the database using the rtrv-as command.

    This is an example of possible output. 

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

AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   10      assoc1
                                      assoc2
                                      assoc3
                                      assoc5
                                      assoc6

as2               OVERRIDE    10      assoc7
as3               LOADSHARE   10      assoc4

AS table is (2 of 250) 1% full.

    Note:

    If themode parameter will not be specified with thechg-as command in5, continue the procedure with5.
  2. Display one of the associations assigned to the application server shown in 1 using the rtrv-assoc command and specifying the association name shown in the rtrv-as output in 1.

    For this example, enter this command.

    rtrv-assoc:aname=assoc1

    This is an example of possible output. 

    
rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc1
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  M3UA          VER         M3UA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.ncd-economic-development.southeastern-corridor-ash.gov
      ARHOST   ---
      LPORT    1030          RPORT       2345
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as1

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

    Note:

    If the value of theopen parameter shown in this step isno, continue the procedure with5.
  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=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

    Note:

    If all the associations assigned to the application server been displayed, continue the procedure with5.
  4. Repeat 2 and 3 for all associations assigned to the application server being changed.
  5. Change the application server in the database using the chg-as command.
    For this example, enter this command

    chg-as:asname=as1:mode=override:tr=1000

    This is an example of possible inputs and outputs: 

    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-AS:  MASP A - COMPLTD;
  6. Verify the changes using the rtrv-as command.
    This is an example of possible output. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

AS Name           Mode        Tr ms   Association Names
as1               OVERRIDE    1000    assoc1
                                      assoc2
                                      assoc3
                                      assoc5
                                      assoc6

as2               OVERRIDE    10      assoc7
as3               LOADSHARE   10      assoc4

AS table is (2 of 250) 1% full

    Note:

    If the value of theopen parameter was not changed in3, continue the procedure with8.
  7. 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=assoc1: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

    Repeat this step for all associations that were changed in 3.

  8. 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 4-40 Changing an Application Server



Sheet 1 of 2



Sheet 2 of 2

4.35 Changing the CIC Values in an Existing Routing Key Containing an Application Server

This procedure is used to change the CIC values in an existing routing key using the chg-appl-rtkey command. These parameters are used in this procedure.

:dpc/dpca/dpci/dpcn/dpcn24 – Destination point code value that is used to filter incoming MSUs.

:opc/opca/opci/opcn/opcn24 - The originating point code value that is used to filter incoming MSUs. This value must not specify a cluster route.

Note:

See the “Point Code Formats” section in the Database Administration - SS7 User's Guide for a definition of the point code types that are used on the EAGLE and for a definition of the different formats that can be used for ITU national point codes.

:si – The service indicator value that is used to filter incoming MSUs. The range of values for the service indicator parameter (si) can be a numerical value either 4, 5, or 13, or for selected service indicator values, a text string can be used instead of numbers. Table 4-18 shows the text strings that can be used in place of numbers for the service indicator values.

Table 4-18 Service Indicator Text String Values

Service Indicator Value Text String

4

tup

5

isup

13

qbicc

:cics - Starting circuit identification code that is used to filter incoming MSUs. Specify with cice to identify the routing key to be changed.

:cice - Ending circuit identification code that is used to filter incoming MSUs. Specify with cics to identify the routing key to be changed.

:ncics - New starting circuit identification code that is used to filter incoming MSUs. Specify the ncics parameter and/or the ncice parameter to change the range of circuit identification codes assigned to the routing key.

:ncice - New ending circuit identification code that is used to filter incoming MSUs. Specify the ncice parameter and/or the ncics parameter to change the range of circuit identification codes assigned to the routing key.

:split - The circuit identification code value where the specified range of CIC values for the routing key specified by the cics and cice values is to be split into two routing keys. The CIC values in one routing key ranges from the cics value of the original routing key to a value equal to one less than the split value. The CIC values in the other routing key ranges from the split value to the cice value of the original routing key. All other parameters in both routing keys remain the same as in the original routing key. The range of CIC values cannot be split if the routing key contains a routing context parameter value.

:type - Key type. Identifies the type of routing key that will be changed. One of three values, type=full/partial/default. If type is not explicitly specified, type=full is assumed. Only the type=full parameter can be used in this procedure.

:rcontext – The routing context parameter value assigned to the routing key.

The chg-appl-rtkey command contains other parameters that are not used in this procedure.

:ssn – The subsystem number value that is used to filter incoming MSUs. See the Adding a Routing Key Containing an Application Server procedure for more information on using the ssn parameter with a routing key.

:nrcontext – The new routing context parameter value.

See the Changing the Routing Context Value in an Existing Routing Key procedure for changing the routing context parameter value in an existing routing key.

Rules for Changing the Range of CIC Values in an Existing Routing Key

The parameter combinations used by the chg-appl-rtkey command to change the range of CIC values in the routing key are shown in Table 4-19.

Table 4-19 Routing Key Parameter Combinations for Changing the Range of CIC Values in an Existing Routing Key

SI=4 (TUP) SI=5 (ISUP) SI=13 (QBICC)

dpci/dpcn/dpcn24=<the DPC assigned to the routing key> (See Note 1)

dpc/dpca=<the DPC assigned to the routing key> (See Note 1)

dpci/dpcn/dpcn24=<the DPC assigned to the routing key> (See Note 1)

dpc/dpca/dpci/

dpcn/dpcn24=<the DPC assigned to the routing key> (See Note 1)

si=4 (See Note 1)

si=5 (See Note 1)

si=5 (See Note 1)

si=13 (See Note 1)

opci/opcn/opcn24=<the OPC assigned to the routing key> (See Note 1)

opc/opca=<the OPC assigned to the routing key> (See Note 1)

opci/opcn/opcn24=<the OPC assigned to the routing key> (See Note 1)

opc/opca/opci/

opcn/opcn24=<the OPC assigned to the routing key> (See Note 1)

cics=<the CICS value assigned to the routing key> (See Notes 1 and 2)

cics=<the CICS value assigned to the routing key>1, 2

cics=<the CICS value assigned to the routing key> (See Notes 1 and 2)

cics=<the CICS value assigned to the routing key> (See Notes 1 and 2)

cice=<the CICE value assigned to the routing key> (See Notes 1 and 2)

cice=<the CICE value assigned to the routing key> (See Notes 1 and 2)

cice=<the CICE value assigned to the routing key> (See Notes 1 and 2)

cice=<the CICE value assigned to the routing key> (See Notes 1 and 2)

type=full

type=full

type=full

type=full

ncics=<0 to 4095> (See Notes 2 and 3)

ncics=<0 to 16383> (See Notes 2 and 3)

ncics=<0 to 4095> (See Notes 2 and 3)

ncics=<0 to 4294967295> (See Notes 2 and 3)

ncice=<0 to 4095> (See Notes 2 and 3)

ncice=<0 to 16383> (See Notes 2 and 3)

ncice=<0 to 4095> (See Notes 2 and 3)

ncice=<0 to 4294967295> (See Notes 2 and 3)

rcontext=<the current routing context value assigned to the routing key> (See Notes 4 and 5)

rcontext=<the current routing context value assigned to the routing key> (See Notes 4 and 5)

rcontext=<the current routing context value assigned to the routing key> (See Notes 4 and 5)

rcontext=<the current routing context value assigned to the routing key> (See Notes 4 and 5)

1. The values for these parameters must be entered exactly as shown in the rtrv-appl-rtkey command output for the routing key being changed. However, text strings can be used in place of some numerical service indicator values. See Table 4-18 for a list of these text strings. The text string must correspond to the numerical value shown in the routing key being changed.

2. The cics and cice parameters must be specified and either the ncics or ncice parameters, or both, must be specified. If both the ncics and ncice parameters are specified, the value of the ncics parameter must be less than the value of the ncice parameter. If the ncics parameter is not specified, the value of the ncice parameter must be greater than or equal to the cics parameter value. If the ncice parameter is not specified, the value of the ncics parameter must be less than or equal to the cice parameter value.

3. The new CIC range cannot overlap the CIC range in an existing routing key.

4. If the routing key contains a numerical value in the RCONTEXT column in the rtrv-appl-rtkey output, the rcontext parameter and value can be used in place of the dpc, si, opc, cics, cice, or type=full parameters and values to identify the routing that is being changed with the chg-appl-rtkey command. However, if only the rcontext parameter is used to identify the routing key being changed, only one of these parameters, ncics or ncice can be specified with the chg-appl-rtkey parameter. If you wish to specify the ncics and ncice parameters with the chg-appl-rtkey parameter, the dpc, si, opc, cics, cice, or type=full parameters and values must be specified with the chg-appl-rtkey command.

5. If the routing key contains dashes in the RCONTEXT column in the rtrv-appl-rtkey output, the dpc, si, opc, cics, cice, or type parameters and values must be used with the chg-appl-rtkey command to identify the routing key being changed.

Rules for Splitting the Range of CIC Values in an Existing Routing Key

The parameter combinations used by the chg-appl-rtkey command to split the range of CIC values in the routing key are shown in Table 4-20.

Splitting the range of CIC values creates two routing keys. The CIC values in one routing key ranges from the cics value of the original routing key to a value equal to one less than the split value. The CIC values in the other routing key ranges from the split value to the cice value of the original routing key. All other parameters in both routing keys remain the same as in the original routing key. The range of CIC values cannot be split if the routing key contains a routing context parameter value.

Table 4-20 Routing Key Parameter Combinations for Splitting the Range of CIC Values in an Existing Routing Key

SI=4 (TUP) SI=5 (ISUP) SI=13 (QBICC)

dpci/dpcn/dpcn24=<the DPC assigned to the routing key> (See Note 1)

dpc/dpca=<the DPC assigned to the routing key> (See Note 1)

dpci/dpcn/dpcn24=<the DPC assigned to the routing key> (See Note 1)

dpc/dpca/dpci/

dpcn/dpcn24=<the DPC assigned to the routing key> (See Note 1)

si=4 (See Note 1)

si=5 (See Note 1)

si=5 (See Note 1)

si=13 (See Note 1)

opci/opcn/opcn24=<the OPC assigned to the routing key> (See Note 1)

opc/opca=<the OPC assigned to the routing key> (See Note 1)

opci/opcn/opcn24=<the OPC assigned to the routing key> (See Note 1)

opc/opca/opci/

opcn/opcn24=<the OPC assigned to the routing key> (See Note 1)

cics=<the CICS value assigned to the routing key> (See Note 1)

cics=<the CICS value assigned to the routing key> (See Note 1)

cics=<the CICS value assigned to the routing key> (See Note 1)

cics=<the CICS value assigned to the routing key> (See Note 1)

cice=<the CICE value assigned to the routing key> (See Note 1)

cice=<the CICE value assigned to the routing key> (See Note 1)

cice=<the CICE value assigned to the routing key> (See Note 1)

cice=<the CICE value assigned to the routing key> (See Note 1)

type=full

type=full

type=full

type=full

split=<0 to 4095> (See Note 2)

split=<0 to 16383> (See Note 2)

split=<0 to 4095> (See Note 2)

split=<0 to 4294967295> (See Note 2)

1. The values for these parameters must be entered exactly as shown in the rtrv-appl-rtkey command output for the routing key being changed. However, text strings can be used in place of some numerical service indicator values. See Table 4-18 for a list of these text strings. The text string must correspond to the numerical value shown in the routing key being changed.

2. The split parameter value must be greater than the cics parameter value and less than the cice parameter value.

Canceling the RTRV-APPL-RTKEY Command

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-appl-rtkey command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-appl-rtkey command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-appl-rtkey command was entered, from another terminal other that the terminal where the rtrv-appl-rtkey 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 routing key information in the database by entering the rtrv-appl-rtkey command.

    The following is an example of the possible output. 

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

RCONTEXT    DPC          SI  ADPTR  ASNAME           TYPE
----------  123-234-123   5  M3UA   as12             FULL
----------  005-005-001   5  M3UA   as9              FULL
----------  005-005-001   5  M3UA   as9              FULL
2500        006-006-001   5  SUA    as10             FULL

RCONTEXT    DPCI         SI  ADPTR  ASNAME           TYPE
----------    2-100-7     6  M3UA   as4              FULL
100           3-137-6     6  SUA    as1              FULL
225           4-035-7     5  SUA    as7              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-7     5  M3UA   as8              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-6     5  M3UA   as2              FULL
----------    6-006-8     3  M3UA   as3              FULL
----------    6-006-8     5  M3UA   as5              FULL
----------    6-024-7     5  M3UA   as4              FULL
----------    6-024-7     5  M3UA   as4              FULL
300           7-008-7     6  SUA    as6              FULL

RCONTEXT    DPC          SI  ADPTR  ASNAME           TYPE
----------  ***********  **  M3UA   as11             DEFAULT

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full
  2. Display the specific routing key information for the routing key being changed by entering the rtrv-appl-rtkey command with the display=all parameter.

    If the routing key being changed contains a routing context value, specify the rcontext parameter and value shown in the rtrv-appl-rtkey output in 1 for the routing key being changed.

    If the routing key being changed does not contain a routing context value, specify the DPC, SI, and TYPE values shown in the rtrv-appl-rtkey output in 1 for the routing key being changed. The service indicator value for the routing key to be used in this procedure is either 4, 5, or 13.

    For this example, enter these commands.

    rtrv-appl-rtkey:dpc=123-234-123:si=5:type=full:display=all

    This is an example of the possible output. 

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

RCONTEXT   DPC           SI SSN OPC            CICS       CICE
---------  123-234-123    5 --- 122-124-125    1          1000

    ADPTR  TYPE      ASNAME 
    M3UA   FULL      as12

    ANAMES
    assoc20

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full

    rtrv-appl-rtkey:rcontext=225:display=all

    This is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
225          4-035-7      5 ---   2-007-3      2000       3000

    ADPTR  TYPE      ASNAME             
    M3UA   FULL      as7    
                                         
    ANAMES
    assoc15

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full
  3. Change the CIC values of the routing key by entering the chg-appl-rtkey command.
    The parameters required for the chg-appl-rtkey command are determined by the type of change being made to the routing key. Go to one of these sections to determine the required parameter combination.

    To change the range of CIC values for this example, enter these commands.

    chg-appl-rtkey:dpca=123-234-123:si=5:opca=122-124-125:cics=1:cice=1000:ncice=2000

    chg-appl-rtkey:dpci=4-035-7:si=5:opci=2-007-3:cics=2000:cice=3000:ncice=4000

    If a routing context value is assigned to the routing key, the rcontext parameter and value assigned to the routing key can be used to identify the routing key being changed instead of the dpc, si, opc, cics, and cice parameters. If the rcontext parameter is specified only one of these parameters, ncics or ncice, can be specified with the chg-appl-rtkey parameter.

    For this example, enter this command.

    chg-appl-rtkey:rcontext=225:ncice=4000

    To split the range of CIC values for this example, enter this command.

    chg-appl-rtkey:dpca=123-234-123:si=5:opca=122-124-125:cics=1:cice=1000:split=500

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

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
CHG-APPL-RTKEY: MASP A - COMPLTD
  4. Display the new routing key information in the database by entering the rtrv-appl-rtkey command with the display=all parameter.

    If the routing key being changed contains a routing context value, specify the rcontext parameter and value specified in the chg-appl-rtkey command in 3. The DPC, SI, CICS, and CICE parameters and values used in 3 can be specified in the rtrv-appl-rtkey command for routing keys containing routing context values.

    If the routing key being changed does not contain a routing context value, specify the DPC, SI, CICS, and CICE parameters and values specified in the chg-appl-rtkey command in 3. If the ncics or ncice parameters were specified in 3, the NCICS or NCICE values specified in 3 must be specified for the cics or cice parameters in this step.

    For this example, enter these commands.

    rtrv-appl-rtkey:dpca=123-234-123:si=5:cics=1:cice=2000:display=all 

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

RCONTEXT   DPC           SI SSN OPC            CICS       CICE
---------  123-234-123    5 --- 122-124-125    1          2000

    ADPTR  TYPE      ASNAME 
    M3UA   FULL      as12

    ANAMES
    assoc20

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full

    rtrv-appl-rtkey:dpci=4-035-7:si=5:cics=2000:cice=4000 :display=all

    or

    rtrv-appl-rtkey:rcontext=225:display=all

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
225          4-035-7      5 ---   2-007-3      2000       4000

    ADPTR  TYPE      ASNAME             
    SUA    FULL      as7    
                                         
    ANAMES
    assoc15

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full

    rtrv-appl-rtkey:dpca=123-234-123:si=5:cics=1:cice=1000 :display=all

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
RCONTEXT   DPC           SI SSN OPC            CICS       CICE
---------- 123-234-123    5 --- 100-100-100    1          499

    ADPTR  TYPE      ASNAME 
    M3UA   FULL      as12

    ANAMES
    assoc20

RCONTEXT   DPC           SI SSN OPC            CICS       CICE
---------- 123-234-123    5 --- 122-124-125    500        1000

    ADPTR  TYPE      ASNAME 
    M3UA   FULL      as12

    ANAMES
    assoc20

STATIC Route Key table is (18 of 2000) 1% full
STATIC Route Key Socket Association table is (18 of 32000) 1% 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 4-41 Changing the CIC Values in an Existing Routing Key Containing an Application Server



Sheet 1 of 2



Sheet 2 of 2

4.36 Changing the Routing Context Value in an Existing Routing Key

This procedure is used to change the routing context value in an existing routing key using the chg-appl-rtkey command.

The routing key being changed in this procedure must contain a number for the routing context value. If the routing context value shown for the routing key contains dashes (-), this routing key cannot be used in this procedure. The dashes shows that the routing key does not have a routing context assigned to it.

To assign a routing context value to an existing M3UA routing key, the routing key must be removed by performing the Removing a Routing Key Containing an Application Server procedure, then re-enter the routing key with the routing context value by performing the Adding a Routing Key Containing an Application Server procedure. A routing context value must always be assigned to an SUA routing key.

These parameters are used in this procedure.

:rcontext – The current routing context parameter value, which has two functions:

  • Provides an index of the application server traffic that the sending ASP is configured or registered to receive.
  • Identifies the SS7 network context for the message. The routing context parameter implicitly defines the SS7 point code format used, the SS7 network indicator value, and the SCCP protocol type/variant/version used.

:nrcontext – The new routing context parameter value, from 0 to 4294967295. The new routing context value cannot be assigned to other routing keys.

The chg-appl-rtkey command contains other parameters that are not used in this procedure.

:dpc/dpca/dpci/dpcn/dpcn24 – Destination point code value that is used to filter incoming MSUs.

:opc/opca/opci/opcn/opcn24 - The originating point code value that is used to filter incoming MSUs. This value must not specify a cluster route.

:si – The service indicator value that is used to filter incoming MSUs. The range of values for the service indicator parameter (si) can be a numerical value from 0 to 15, or for selected service indicator values, a text string can be used instead of numbers. Table 4-21 shows the text strings that can be used in place of numbers for the service indicator values.

Table 4-21 Service Indicator Text String Values

Service Indicator Value Text String Service Indicator Value Text String

0

snm

4

tup

1

regtest

5

isup

2

spltst

13

qbicc

3

sccp

   

:ssn – The subsystem number value that is used to filter incoming MSUs.

:cics - Starting circuit identification code that is used to filter incoming MSUs.

:cice - Ending circuit identification code that is used to filter incoming MSUs.

:type - Key type. Identifies the type of routing key that will be changed. One of three values, type =full/partial/default. If type is not explicitly specified, type = full is assumed.

:ncics - New starting circuit identification code that is used to filter incoming MSUs.

:ncice - New ending circuit identification code that is used to filter incoming MSUs.

:split - The circuit identification code value where the specified range of the routing key specified by the cics and cice values is to be split into two entries.

See the Changing the CIC Values in an Existing Routing Key Containing an Application Server procedure for changing a routing key using the ncics, ncice, and split parameters.

Canceling the RTRV-APPL-RTKEY Command

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-appl-rtkey command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-appl-rtkey command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-appl-rtkey command was entered, from another terminal other that the terminal where the rtrv-appl-rtkey 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 routing key information in the database by entering the rtrv-appl-rtkey command. The following is an example of the possible output. 
    
rlghncxa03w 08-04-28 21:15:37 GMT EAGLE5 38.0.0

RCONTEXT    DPC          SI  ADPTR  ASNAME           TYPE
----------  123-234-123   5  M3UA   as12             FULL
----------  005-005-001   5  M3UA   as9              FULL
----------  005-005-001   5  M3UA   as9              FULL
2500        006-006-001   5  SUA    as10             FULL

RCONTEXT    DPCI         SI  ADPTR  ASNAME           TYPE
----------    2-100-7     6  M3UA   as4              FULL
100           3-137-6     6  SUA    as1              FULL
225           4-035-7     5  M3UA   as7              FULL
310           6-006-6     5  SUA    as2              FULL
----------    6-006-7     5  M3UA   as8              FULL
1000          6-006-6     5  SUA    as2              FULL
500           6-006-6     5  SUA    as2              FULL
----------    6-006-8     3  M3UA   as3              FULL
----------    6-006-8     5  M3UA   as5              FULL
----------    6-024-7     5  M3UA   as4              FULL
----------    6-024-7     5  M3UA   as4              FULL
300           7-008-7     6  SUA    as6              FULL

RCONTEXT    DPC          SI  ADPTR  ASNAME           TYPE
----------  ***********  **  M3UA   as11             DEFAULT

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full
  2. Display the specific routing key information for the routing key being changed by entering the rtrv-appl-rtkey command with the display=all parameter and the RCONTEXT value shown in the rtrv-appl-rtkey output in 1 for the routing key being changed. For this example, enter this command.

    rtrv-appl-rtkey:rcontext=310:display=all

    This is an example of the possible output. 

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

RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
310          6-006-6      5 ---   1-002-3      75         100
    ADPTR  TYPE      ASNAME             
    SUA    FULL      as2    
                                         
    ANAMES
    assoc1

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full

    If the routing context value shown for the routing key is dashes (-), this routing key cannot be used in this procedure. The dashes show that the routing key does not have a routing context assigned to it.

    To assign a routing context value to a M3UA routing key that does not have a routing context value, the routing key must be removed by performing the Removing a Routing Key Containing an Application Server procedure. Re-enter the routing key with the routing context value by performing the Adding a Routing Key Containing an Application Server procedure. If you do not wish to assign a routing context value to this routing key, but you wish to change the routing context value in another routing key, repeat this step with another routing key shown in 1. If you do not wish to assign a routing context value to this routing key, and do not wish to change the routing context value in another routing key, this procedure cannot be performed.

    If the routing key contains a routing context value, continue the procedure with 3.

  3. Display the association displayed in the rtrv-appl-rtkey output in 2, using the rtrv-assoc command with the association name shown in 2.

    rtrv-assoc:aname=assoc1

    This is an example of possible output. 

    
rlghncxa03w 09-05-28 09:12:36 GMT EAGLE5 41.0.0
ANAME assoc1
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  SUA           VER         SUA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    1030          RPORT       1030
      ISTRMS   2             OSTRMS      2          BUFSIZE  16
      RMODE    LIN           RMIN        120        RMAX     800
      RTIMES   10            CWMIN       3000       UAPS     10
      OPEN     YES           ALW         YES        RTXTHR   10000
      RHOSTVAL RELAXED

      ASNAMES
      as2

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

    Repeat this step for each association name displayed in 2.

    Note:

    If theopen parameter value for all the associations assigned to the application server isno (shown in3), continue the procedure with5.
  4. 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=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;

    Caution:

    TheIP connections using the associations specified in this step will not be able to carry any traffic when theopen parameter is changed tono.

    Repeat this step for all the associations assigned to the application server that have the open=yes parameter value.

  5. Change the routing key information to the database by entering the chg-appl-rtkey command with the current and new routing context values. For this example, enter this command.

    chg-appl-rtkey:nrcontext=5280:rcontext=310

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

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
CHG-APPL-RTKEY: MASP A - COMPLTD
  6. Display the new routing key information in the database by entering the rtrv-appl-rtkey command with the new routing context value specified in 5 and the display=all parameter. For this example, enter this command.

    rtrv-appl-rtkey:rcontext=5280:display=all

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:15:37 GMT EAGLE5 38.0.0
RCONTEXT   DPCI          SI SSN OPCI           CICS       CICE
5280         6-006-6      5 ---   1-002-3      75         100
    ADPTR  TYPE      ASNAME             
    SUA    FULL      as2    
                                         
    ANAMES
    assoc1

STATIC Route Key table is (17 of 2000) 1% full
STATIC Route Key Socket Association table is (17 of 32000) 1% full

    Note:

    If4was not performed in this procedure, continue the procedure with8.
  7. Change the value of the open parameter of the associations that were changed in 4 to yes by specifying the chg-assoc command with the open=yes parameter. For this example, enter this command.

    chg-assoc:aname=assoc1: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;

    Repeat this step for all the associations that were changed in 4.

  8. 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 4-42 Changing the Routing Context Value in an Existing Routing Key



Sheet 1 of 2



Sheet 2 of 2

4.37 Changing the SCTP Checksum Algorithm Option for M3UA and SUA 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 SS7IPGW or IPGWI applications. This option is a system-wide option. To apply this option to associations assigned to cards running the IPLIM, IPLIMI, 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-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    EOAM
1114   E5TDM-A
1115   E5MCAP    EOAM
1116   E5TDM-B
1117   E5MDAL
1201   LIMDS0    SS7ANSI   lsn1          A    0    lsn2          B    1
1202   DCM       IPLIM     ipnode2       A    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     ipnode3       A    0    ipnode1       B    1
1305   DCM       IPLIM     ipnode4       A    0    
1308   DCM       IPLIM     ipnode3       B    2
                           ipnode1       A1   2    ipnode4       B2   1
1315   DCM       SS7IPGW   ipgtwy1       A    
1317   DCM       IPGWI     ipgtwy2       A

    Record the card location, shown in the LOC column, and signaling link, shown in the LINK column, information for all cards running the SS7IPGW and IPGWI applications.

  3. At the IP near end node, stop all traffic to one of the IP cards running the SS7IPGW or IPGWI applications on the EAGLE.
  4. At the EAGLE, enter the msucount -l pass command with the card location of the IP card selected in 3. For this example, enter this command.

    pass:loc=1315:cmd=”msucount -l”

    The following is an example of the possible output. 

    rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
PASS: Command sent to card

rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
MSUCOUNT: Command In Progress

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

MSUCOUNT: MSU Count Report

--------------------------
Link Measurements (Link A)
--------------------------
Transmit Counts                      Receive Counts
----------------------------------   -----------------------------
rate   msus        bytes             rate   msus        bytes
-----  ----------  ---------------   -----  ----------  ----------
2000   4294967295  4294967295        2000   4294967295  4294967295
MTP Primitive (MTPP) counts          Reroute Counts
----------------------------------   ----------------------
sent pdus   rcvd pdus   dscrd pdus   sent msus   rcvd msus
----------  ----------  ----------   ----------  ----------     
4294967295  4294967295  4294967295   4294967295  4294967295 
    
END of Report
  5. 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.
  6. 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
  7. Display the associations assigned to the IP card specified in 4, 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 1315 (the card specified in 4) is DN-MSC1. Enter this command.

    rtrv-assoc:lhost=dn-msc1

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
assoc3          1315 A     A    SUA     2345  1025  YES  YES
assoc6          1315 A     A    SUA     4156  1025  YES  YES

IP Appl Sock/Assoc table is (9 of 4000) 1% full
Assoc Buffer Space Used (32 KB of 3200 KB) on LOC = 1315
  8. At the EAGLE, enter the msucount -a pass command with the card location specified in 4 and the association names shown in 7. For this example, enter this command.

    pass:loc=1315:cmd=”msucount -a assoc3”

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
PASS: Command sent to card

rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
MSUCOUNT: Command In Progress

rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
MSUCOUNT: MSU Count Report

--------------------------
IP Connection Measurements
--------------------------
Receive Counts                     Transmit Counts
--------------------------------   -----------------------------
msus            bytes              msus             bytes
----------      ----------------   ----------       ----------
4294967295      4294967295         4294967295       4294967295
Receive Discard Counts             Transmit Discard Counts
--------------------------------   ---------------------------------
reason                count       reason                 count
--------------------- ---------   ---------------------- ----------
link state            4294967295   sccp msg type          4294967295
sccp msg type         4294967295   sccp class             4294967295
sccp class            4294967295   normalization error    4294967295
sccp called party     4294967295   invalid traffic type   4294967295
sccp calling party    4294967295   M3UA conversion error  4294967295
isup sio              4294967295   SUA conversion error   4294967295
normalization error   4294967295
error in XSRV packet  4294967295
M3UA PDU error        4294967295
SUA PDU error         4294967295
invalid rcontext      4294967295
Stored Transmit Discard Data
----------------------------
no stored transmit discard data
Stored Receive Discard Data
---------------------------
53 41 53 49 69 73 6f 74 11 00 87 0a 01 03 01 05
05 00 01 02 03 04 05 06 07 08 09 00 00 00 00 00

END of Report

    pass:loc=1315:cmd=”msucount -a assoc6”

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
PASS: Command sent to card

rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
MSUCOUNT: Command In Progress

rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
MSUCOUNT: MSU Count Report

--------------------------
IP Connection Measurements
--------------------------
Receive Counts                     Transmit Counts
--------------------------------   -----------------------------
msus            bytes              msus             bytes
----------      ----------------   ----------       ----------
4294967295      4294967295         4294967295       4294967295
Receive Discard Counts             Transmit Discard Counts
--------------------------------   ---------------------------------
reason                count       reason                 count
--------------------- ---------   ---------------------- ----------
link state            4294967295   sccp msg type          4294967295
sccp msg type         4294967295   sccp class             4294967295
sccp class            4294967295   normalization error    4294967295
sccp called party     4294967295   invalid traffic type   4294967295
sccp calling party    4294967295   M3UA conversion error  4294967295
isup sio              4294967295   SUA conversion error   4294967295
normalization error   4294967295
error in XSRV packet  4294967295
M3UA PDU error        4294967295
SUA PDU error         4294967295
invalid rcontext      4294967295
Stored Transmit Discard Data
----------------------------
no stored transmit discard data
Stored Receive Discard Data
---------------------------
53 41 53 49 69 73 6f 74 11 00 87 0a 01 03 01 05
05 00 01 02 03 04 05 06 07 08 09 00 00 00 00 00

END of Report
  9. At the IP near end node, disconnect all the associations attached to the IP card specified in 8.
  10. At the EAGLE, place the signaling link on this IP card out of service using the dact-slk command. For this example, enter this command.

    dact-slk:loc=1315:link=a

    When 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
  11. 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 12.
    • 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 13.
  12. 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.

  13. Change the value of the open parameter of the associations shown in 7 to no by specifying the chg-assoc command with the open=no parameter. For this example, enter this command.

    chg-assoc:aname=assoc3:open=no

    chg-assoc:aname=assoc6: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;
  14. Change the value of the open parameter of the associations changed in 13 to yes by specifying the chg-assoc command with the open=yes parameter. For this example, enter this command.

    chg-assoc:aname=assoc3:open=yes

    chg-assoc:aname=assoc6: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;
  15. Verify the checksum algorithm that is assigned to the associations shown in 14 by entering the sctp -a pass command with the card location of the IP card specified in 10 and the name of the associations specified in 14. For this example, enter this command.

    pass:loc=1315:cmd=”sctp -a assoc3 ”

    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
    assoc3           192.1.1.50         2345    192.168.112.4  1025
                     192.1.1.50  

               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
    assoc3           192.1.1.50         2345    192.168.112.4  1025
                     192.1.1.50  

               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=1315:cmd=”sctp -a assoc6 ”

    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
    assoc6           192.1.1.50         4156    192.168.112.4  1025
                     192.1.1.50  

               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
    assoc6           192.1.1.50         4156    192.168.112.4  1025
                     192.1.1.50  

               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 11, 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-m3ua-and-sua-configuration-procedures1.html, continue the procedure with ietf-m3ua-and-sua-configuration-procedures1.html.

  16. At the IP near end node, configure all the associations attached to the IP card specified in ietf-m3ua-and-sua-configuration-procedures1.html to use the SCTP checksum algorithm.
  17. Put the signaling link that was placed out of service in ietf-m3ua-and-sua-configuration-procedures1.html back into service using the act-slk command. For example, enter this command.

    act-slk:loc=1315:link=a

    When this command has successfully completed, this message appears. 

    
rlghncxa03w 06-10-07 11:11:28 GMT EAGLE5 36.0.0
Activate Link message sent to card
  18. 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 value specified in ietf-m3ua-and-sua-configuration-procedures1.html. For example, enter this command.

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

    The following 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
1315,A   ipgtwy1     ----------- IS-NR        Avail     ----
Command Completed.
  19. At the IP near end node, connect one of the associations attached to the IP card specified in ietf-m3ua-and-sua-configuration-procedures1.html.
  20. At the EAGLE, enter the rept-stat-assoc command specifying the association names specified with the chg-assoc command in ietf-m3ua-and-sua-configuration-procedures1.html and ietf-m3ua-and-sua-configuration-procedures1.html to verify that the association is established with the IP near end node. For this example, enter this command.

    rept-stat-assoc:aname=assoc3

    The following is an example of the possible output. 

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

                     CARD  IPLNK
ANAME           LOC  PORT  LINK  PST          SST         ASPID     
as1             1315 A     A     IS-NR        ESTABLISHED 4294967295

ASNAME            ANAME             ASP-STATE
assoc3            as1               ASP-ACTIVE

Command Completed.
    rept-stat-assoc:aname=assoc6

    The following is an example of the possible output. 

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

                     CARD IPLNK
ANAME           LOC  PORT  LINK  PST          SST         ASPID     
as6             1315 A     A     IS-NR        ESTABLISHED 4294967295

ASNAME            ANAME             ASP-STATE
assoc6            as6               ASP-ACTIVE

Command Completed.
  21. 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. For this example, enter this command.

    pass:loc=1315: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.
  22. At the IP near end node, connect all the other associations attached to the IP card specified in ietf-m3ua-and-sua-configuration-procedures1.html.
  23. At the IP near end node, activate one of the associations attached to the IP card specified in ietf-m3ua-and-sua-configuration-procedures1.html.
  24. At the EAGLE, enter the msucount -l pass command with the card location of the IP card specified in ietf-m3ua-and-sua-configuration-procedures1.html. For this example, enter this command.

    pass:loc=1315:cmd=”msucount -l”

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
PASS: Command sent to card

rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
MSUCOUNT: Command In Progress

rlghncxa03w 06-10-28 21:16:37 GMT EAGLE5 36.0.0
MSUCOUNT: MSU Count Report

--------------------------
Link Measurements (Link A)
--------------------------

Transmit Counts                      Receive Counts
----------------------------------   -----------------------------
rate   msus        bytes             rate   msus        bytes
-----  ----------  ---------------   -----  ----------  ----------
2000   4294967295  4294967295        2000   4294967295  4294967295

MTP Primitive (MTPP) counts          Reroute Counts
----------------------------------   ----------------------
sent pdus   rcvd pdus   dscrd pdus   sent msus   rcvd msus
----------  ----------  ----------   ----------  ----------     
4294967295  4294967295  4294967295   4294967295  4294967295     

END of Report
  25. At the EAGLE, enter the msucount -a pass command with the card location specified in ietf-m3ua-and-sua-configuration-procedures1.html and the association names specified in ietf-m3ua-and-sua-configuration-procedures1.html. For this example, enter this command.

    pass:loc=1315:cmd=”msucount -a assoc3”

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
PASS: Command sent to card

rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
MSUCOUNT: Command In Progress

rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
MSUCOUNT: MSU Count Report

--------------------------
IP Connection Measurements
--------------------------

Receive Counts                     Transmit Counts
--------------------------------   -----------------------------
msus            bytes              msus             bytes
----------      ----------------   ----------       ----------
4294967295      4294967295         4294967295       4294967295
Receive Discard Counts             Transmit Discard Counts
--------------------------------   ---------------------------------
reason                count       reason                 count
--------------------- ---------   ---------------------- ----------
link state            4294967295   sccp msg type          4294967295
sccp msg type         4294967295   sccp class             4294967295
sccp class            4294967295   normalization error    4294967295
sccp called party     4294967295   invalid traffic type   4294967295
sccp calling party    4294967295   M3UA conversion error  4294967295
isup sio              4294967295   SUA conversion error   4294967295
normalization error   4294967295
error in XSRV packet  4294967295
M3UA PDU error        4294967295
SUA PDU error         4294967295
invalid rcontext      4294967295

Stored Transmit Discard Data
----------------------------
no stored transmit discard data
Stored Receive Discard Data
---------------------------
53 41 53 49 69 73 6f 74 11 00 87 0a 01 03 01 05
05 00 01 02 03 04 05 06 07 08 09 00 00 00 00 00

END of Report

    pass:loc=1315:cmd=”msucount -a assoc6”

    The following is an example of the possible output. 

    
rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
PASS: Command sent to card

rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
MSUCOUNT: Command In Progress

rlghncxa03w 06-10-28 21:17:37 GMT EAGLE5 36.0.0
MSUCOUNT: MSU Count Report

--------------------------
IP Connection Measurements
--------------------------
Receive Counts                     Transmit Counts
--------------------------------   -----------------------------
msus            bytes              msus             bytes
----------      ----------------   ----------       ----------
4294967295      4294967295         4294967295       4294967295
Receive Discard Counts             Transmit Discard Counts
--------------------------------   ---------------------------------
reason                count       reason                 count
--------------------- ---------   ---------------------- ----------
link state            4294967295   sccp msg type          4294967295
sccp msg type         4294967295   sccp class             4294967295
sccp class            4294967295   normalization error    4294967295
sccp called party     4294967295   invalid traffic type   4294967295
sccp calling party    4294967295   M3UA conversion error  4294967295
isup sio              4294967295   SUA conversion error   4294967295
normalization error   4294967295
error in XSRV packet  4294967295
M3UA PDU error        4294967295
SUA PDU error         4294967295
invalid rcontext      4294967295
Stored Transmit Discard Data
----------------------------
no stored transmit discard data
Stored Receive Discard Data
---------------------------
53 41 53 49 69 73 6f 74 11 00 87 0a 01 03 01 05
05 00 01 02 03 04 05 06 07 08 09 00 00 00 00 00

END of Report

    If the outputs of the pass commands in ietf-m3ua-and-sua-configuration-procedures1.html and ietf-m3ua-and-sua-configuration-procedures1.html show that traffic is not flowing over the association, contact the Customer Care Center. Refer to unresolvable-reference.html#GUID-1825DD07-2A6B-4648-859A-1258A0F9AC40 for the contact information.

  26. At the IP near end node, activate all the other associations attached to the IP card specified in ietf-m3ua-and-sua-configuration-procedures1.html.
  27. Repeat ietf-m3ua-and-sua-configuration-procedures1.html through ietf-m3ua-and-sua-configuration-procedures1.html to update the other IP cards in the EAGLE running the SS7IPGW and IPGWI applications with the new SCTP checksum algorithm.
  28. 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.
  29. If the rtrv-card output in ietf-m3ua-and-sua-configuration-procedures1.html shows cards running the IPLIM or IPLIMI applications, perform the Changing the SCTP Checksum Algorithm Option for M2PA 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 IPLIM, IPLIMI, or IPSG applications, this procedure is finished.

Figure 4-43 Changing the SCTP Checksum Algorithm Option for M3UA and SUA Associations



Sheet 1 of 4



Sheet 2 of 4



Sheet 3 of 4



Sheet 4 of 4

4.38 Changing a UA Parameter Set

Use this procedure to change the values in a UA (user adapter) parameter set using the chg-uaps command. The chg-uaps command uses these parameters.

:set – the UA parameter set being changed, from 1 - 9

:scrset – the source UA parameter set used to copy the values from one UA parameter set to another, from 1 to 10.

:timer – the timer being changed, from 1 to 10. Currently, there are only three timers defined:

  • Timer 2 – The False IP Connection Congestion Timer – the maximum amount of time (in milliseconds) that an association is allowed to remain congested before failing due to false connection congestion.
  • Timer 3 – The UA Heartbeat Period Timer – The frequency, in milliseconds, that heartbeat messages are transmitted.
  • Timer 4 – The UA Heartbeat Received Timer – The amount of time, in milliseconds, that the EAGLE waits for a response to the heartbeat message that was transmitted. If a response to the heartbeat message is not received in the amount of time defined by Timer 4, the association is torn down

:tvalue – The value of the timer specified by the timer parameter.

  • The value of timer 2 is from 10 to 30,000 milliseconds. The system default value is 3,000 milliseconds.
  • The value of timer 3 is from 100 to 60,000 milliseconds. The system default value is 10,000 milliseconds.
  • The value of timer 4 is from 100 to 10,000 milliseconds. The system default value is 5,000 milliseconds.

:parm – the UA parameters, from 1 to 10. Currently, only four UA parameters are defined.

  • 1 – Controlling ASPSNM Behavior
  • 2 – Controlling ASP/Application Server State Notification Behavior
  • 3 – UA Serviceability Options
  • 4 – SCTP Payload Protocol Indicator Option

:pvalue – the value of the UA parameters, which is dependent on the parm parameter value. The value of the pvalue parameter is a bit-mapped value, requiring a 0 in the specific bit position to disable the item, or a 1 in the specific bit position to enabled the item. The value of the pvalue parameter is a 32-bit number. Any bits not specified in the following lists are not used.

  • If the parm value is 1, the bits used by the pvalue parameter are:
    • 1 – Response Method – controls the sending of an SNM TFC/UPU as a reply to a message received on an association for an unavailable destination. The SNM TFC/UPU is replicated to all associations that have this capability and meet the Response SNM Criteria. The default is to allow the response to be sent.
    • 1 – Response Method – controls the sending of an SNM TFC/UPU as a reply to a message received on an association for an unavailable destination. The SNM TFC/UPU is replicated to all associations that have this capability and meet the Response SNM Criteria. The default is to allow the response to be sent.
    • 6 – Broadcast Congestion Status Change – controls the sending of unsolicited congestion status changes by an ASP. Unsolicited congestion status messages (TFCs generated when a destination's congestion status changes) are replicated to all ASPs who have this capability and meet the Multicast SNM Criteria. The default is to generate no unsolicited congestion status changes.

    Table 4-22 shows the values can be entered for the pvalue parameter if the parm value is 1. The pvalue parameter value can be entered as a hexadecimal or a decimal number.

    Table 4-22 Valid PVALUE Parameter Values if PARM=1

    Bits Enabled Bits Disabled Hexadecimal Value Decimal Value

    None

    Bit 0 - Broadcast

    Bit 1 - Response Method

    Bit 6 - Broadcast Congestion Status Change

    h’0

    0

    Bit 0 - Broadcast

    Bit 1 - Response Method

    Bit 6 - Broadcast Congestion Status Change

    h’1

    1

    Bit 1 - Response Method

    Bit 0 - Broadcast

    Bit 6 - Broadcast Congestion Status Change

    h’2

    2

    Bit 0 - Broadcast

    Bit 1 - Response Method

    Bit 6 - Broadcast Congestion Status Change

    h’3*

    3*

    Bit 6 - Broadcast Congestion Status Change

    Bit 0 - Broadcast

    Bit 1 - Response Method

    h’40

    64

    Bit 6 - Broadcast Congestion Status Change

    Bit 0 - Broadcast

    Bit 1 - Response Method

    h’41

    65

    Bit 6 - Broadcast Congestion Status Change

    Bit 1 - Response Method

    Bit 0 - Broadcast

    h’42

    66

    Bit 0 - Broadcast

    Bit 1 - Response Method

    Bit 6 - Broadcast Congestion Status Change

    None

    h’43

    67

    * The system default value

  • If the parm value is 2, the bits used by the pvalue parameter are:
    • 0 – ASP Active Notifications – controls the sending of ASP-Active notifications. If this value is specified, an ASP-Default notification is sent when an ASP transitions to the ASP-ACTIVE state. The default is not to send ASP-Active notifications.
    • 1 – ASP Inactive Notifications – controls the sending of ASP-Inactive notifications. If this value is specified, an ASP-Inactive notification is sent when an ASP transitions to the ASP-INACTIVE state. The default is not to send ASP-Inactive notifications.

      Note:

      To see the ASP activations and inactivations, bits 0 and 1 of the pvalue parameter value need to be enabled. See Table 4-23.
    • 2 – ASPAS State Query – controls the sending of ASP/AS State notifications on request by an ASP. If this value is specified, the EAGLE responds with ASP and AS state notifications if the remote ASP sends ASP-UP or ASP-INACTIVE, while the local ASP is in the ASP-INACTIVE state, or the remote ASP sends an ASP-ACTIVE notification while the local ASP is in the ASP-ACTIVE state. The default is not to send ASP/AS state notifications.

    Table 4-23 shows the values can be entered for the pvalue parameter if the parm value is 2. The pvalue parameter value can be entered as a hexadecimal or a decimal number.

    Table 4-23 Valid PVALUE Parameter Values if PARM=2

    Bits Enabled Bits Disabled Hexadecimal Value Decimal Value

    None

    Bit 0 - ASP Activate Notifications

    Bit 1 - ASP Inactivate Notifications

    Bit 2 - ASP AS State Query

    h’0*

    0*

    Bit 0 - ASP Activate Notifications

    Bit 1 - ASP Inactivate Notifications

    Bit 2 - ASP AS State Query

    h’1

    1

    Bit 1 - ASP Inactivate Notifications

    Bit 0 - ASP Activate Notifications

    Bit 2 - ASP AS State Query

    h’2

    2

    Bit 0 - ASP Activate Notifications

    Bit 1 - ASP Inactivate Notifications

    Bit 2 - ASP AS State Query

    h’3

    3

    Bit 2 - ASP AS State Query

    Bit 0 - ASP Activate Notifications

    Bit 1 - ASP Inactivate Notifications

    h’4

    4

    Bit 0 - ASP Activate Notifications

    Bit 2 - ASP AS State Query

    Bit 1 - ASP Inactivate Notifications

    h’5

    5

    Bit 1 - ASP Inactivate Notifications

    Bit 2 - ASP AS State Query

    Bit 0 - ASP Activate Notifications

    h’6

    6

    Bit 0 - ASP Activate Notifications

    Bit 1 - ASP Inactivate Notifications

    Bit 2 - ASP AS State Query

    None

    h’7

    7

    * The system default value

  • If the parm value is 3, the bits used by the pvalue parameter are:
    • 0 – UA Heartbeats – heartbeat messages are sent on connections from the EAGLE to the far-end node that are in the ASP-Down, ASP-Active, and ASP-Inactive states if the bit is enabled.
    • 1 – UA Graceful Shutdown – enables the graceful shutdown of IPSG M3UA connections if the bit is enabled.

    Table 4-24 shows the values can be entered for the pvalue parameter if the parm value is 3. The pvalue parameter value can be entered as a hexadecimal or a decimal number.

    Table 4-24 Valid PVALUE Parameter Values if PARM=3

    Bits Enabled Bits Disabled Hexadecimal Value Decimal Value

    None

    Bit 0 - UA Heartbeats

    Bit 1 - UA Graceful Shutdown

    h’0*

    0*

    Bit 0 - UA Heartbeats

    Bit 1 - UA Graceful Shutdown

    h’1

    1

    Bit 1 - UA Graceful Shutdown

    Bit 0 - UA Heartbeats

    h’2

    2

    Bit 0 - UA Heartbeats

    Bit 1 - UA Graceful Shutdown

    None

    h’3

    3

    * The system default value

  • If the parm value is 4, the bit 0, the SCTP Payload Protocol Indicator byte order option, is used by the pvalue parameter. This bit indicates whether the SCTP Payload Protocol Indicator (PPI) in the received or transmitted message should be in the Big Endian and Little Endian byte format.

    Table 4-25 shows the values can be entered for the pvalue parameter if the parm value is 4. The pvalue parameter value can be entered as a hexadecimal or a decimal number.

    Table 4-25 Valid PVALUE Parameter Values if PARM=4

    SCTP Payload Protocol Indicator Byte Order Option - Bit 0 Hexadecimal Value Decimal Value
    Big Endian Byte Format

    h’0*

    0*

    Little Endian Byte Format

    h’1

    1

    * The system default value

UA parameter set 10 contains the default values for the UA parameter sets and cannot be changed.

The set and scrset parameter values cannot be the same.

If the scrset parameter is specified, no other optional parameter may be specified.

The timer and tvalue parameters must be specified together. If one is specified, the other must be specified.

The parm and pvalue parameters must be specified together. If one is specified, the other must be specified.

Canceling the RTRV-UAPS Command

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

  • Press the F9 function key on the keyboard at the terminal where the rtrv-uaps command was entered.
  • Enter the canc-cmd without the trm parameter at the terminal where the rtrv-uaps command was entered.
  • Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-uaps command was entered, from another terminal other that the terminal where the rtrv-uaps 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 values in the UA parameter set being changed by entering the rtrv-uaps command and specifying the desired UA parameter set number, from 1 to 9. For this example, enter this command.

    rtrv-uaps:set=3

    This is an example of possible output. 

    
rlghncxa03w 10-07-28 09:12:36 GMT EAGLE5 42.0.0
    SET  TIMER      TVALUE  PARM      PVALUE
      3      1           0     1           3
      3      2        3000     2           0
      3      3       10000     3           0
      3      4        5000     4           0
      3      5           0     5           0
      3      6           0     6           0
      3      7           0     7           0
      3      8           0     8           0
      3      9           0     9           0
      3     10           0    10           0

    TIMER 2: False IP Connection Congestion Timer, max time an
             association can be congested before failing due to false
             congestion. SS7IPGW and IPGWI applications enforce
             0-30000(ms). Not supported on IPSG application.
    TVALUE : Valid range = 32-bits

    TIMER 3: UA HeartBeat Period Timer T(beat), time (ms) between sending
             of BEAT msgs by NE. IPSG, SS7IPGW and IPGWI applications
             enforce 100(ms)-60000(ms).
    TVALUE : Valid range = 32-bits

    TIMER 4: UA HeartBeat Received Timer T(beat ack), timeout period for
             response BEAT ACK msgs by NE. IPSG, SS7IPGW and IPGWI
             applications enforce 100(ms)-10000(ms).
    TVALUE : Valid range = 32-bits

    PARM  1: ASP SNM options.  Each bit is used as an enabled/disabled
             flag for a particular ASP SNM option. Not supported on IPSG
             application.
    PVALUE : Valid range = 32-bits
             BIT                                  BIT VALUE
             0=Broadcast                          0=Disabled , 1=Enabled
             1=Response Method                    0=Disabled , 1=Enabled
             2-5=Reserved
             6=Broadcast Congestion Status Change 0=Disabled , 1=Enabled
             7-31=Reserved

    PARM  2: ASP/AS Notification options.  Each bit is used as an
             enabled/disabled flag for a particular ASP/AS
             Notification option.  Not supported on IPSG application.
    PVALUE : Valid range = 32-bits
             BIT                                  BIT VALUE
             0=ASP Active Notifications           0=Disabled , 1=Enabled
             1=ASP Inactive Notifications         0=Disabled , 1=Enabled
             2=ASP AS State Query                 0=Disabled , 1=Enabled
             3-31=Reserved

    PARM  3: UA Serviceability Options.  Each bit is used as an
             enabled/disabled flag for a particular UA Serviceability
             option. Supported on IPSG, SS7IPGW, and IPGWI applications.
             UA Graceful Shutdown supported on IPSG for M3UA only.
    PVALUE : Valid range = 32-bits
             BIT                                  BIT VALUE
             0=UA Heartbeats                      0=Disabled , 1=Enabled
             1=UA Graceful Shutdown               0=Disabled , 1=Enabled 
             2-31=Reserved

    PARM  4: SCTP Payload Protocol Indicator byte order option. Bit indicates 
             PPI value is RCV/TX in Big Endian or Little Endian byte format.  
             Supported on IPSG-M2PA associations only.
    PVALUE : Valid range = 32-bits
             BIT                               BIT VALUE
             0=Payload Protocol Indicator      0=Big Endian , 1=Little Endian
             1-31=Reserved

    If the new values of the UA parameter set are being copied from another UA parameter set, continue the procedure with 2.

    If the new values of the UA parameter set are not being copied from another UA parameter set, continue the procedure with 3.

  2. Display the values in the UA parameter set that will be copied to the UA parameter set displayed in 1 by entering the rtrv-uaps command and specifying the desired UA parameter set number, from 1 to 10. For this example, enter this command.

    rtrv-uaps:set=10

    This is an example of possible output. 

    
rlghncxa03w 10-07-28 09:12:36 GMT EAGLE5 42.0.0
    SET  TIMER      TVALUE  PARM      PVALUE
     10      1           0     1           3
     10      2        3000     2           0
     10      3       10000     3           0
     10      4        5000     4           0
     10      5           0     5           0
     10      6           0     6           0
     10      7           0     7           0
     10      8           0     8           0
     10      9           0     9           0
     10     10           0    10           0

    TIMER 2: False IP Connection Congestion Timer, max time an
             association can be congested before failing due to false
             congestion. SS7IPGW and IPGWI applications enforce
             0-30000(ms). Not supported on IPSG application.
    TVALUE : Valid range = 32-bits

    TIMER 3: UA HeartBeat Period Timer T(beat), time (ms) between sending
             of BEAT msgs by NE. IPSG, SS7IPGW and IPGWI applications
             enforce 100(ms)-60000(ms).
    TVALUE : Valid range = 32-bits

    TIMER 4: UA HeartBeat Received Timer T(beat ack), timeout period for
             response BEAT ACK msgs by NE. IPSG, SS7IPGW and IPGWI
             applications enforce 100(ms)-10000(ms).
    TVALUE : Valid range = 32-bits

    PARM  1: ASP SNM options.  Each bit is used as an enabled/disabled
             flag for a particular ASP SNM option. Not supported on IPSG
             application.
    PVALUE : Valid range = 32-bits
             BIT                                  BIT VALUE
             0=Broadcast                          0=Disabled , 1=Enabled
             1=Response Method                    0=Disabled , 1=Enabled
             2-5=Reserved
             6=Broadcast Congestion Status Change 0=Disabled , 1=Enabled
             7-31=Reserved

    PARM  2: ASP/AS Notification options.  Each bit is used as an
             enabled/disabled flag for a particular ASP/AS
             Notification option.  Not supported on IPSG application.
    PVALUE : Valid range = 32-bits
             BIT                                  BIT VALUE
             0=ASP Active Notifications           0=Disabled , 1=Enabled
             1=ASP Inactive Notifications         0=Disabled , 1=Enabled
             2=ASP AS State Query                 0=Disabled , 1=Enabled
             3-31=Reserved

    PARM  3: UA Serviceability Options.  Each bit is used as an
             enabled/disabled flag for a particular UA Serviceability
             option. Supported on IPSG, SS7IPGW, and IPGWI applications.
             UA Graceful Shutdown supported on IPSG for M3UA only.
    PVALUE : Valid range = 32-bits
             BIT                                  BIT VALUE
             0=UA Heartbeats                      0=Disabled , 1=Enabled
             1=UA Graceful Shutdown               0=Disabled , 1=Enabled 
             2-31=Reserved

    PARM  4: SCTP Payload Protocol Indicator byte order option. Bit indicates 
             PPI value is RCV/TX in Big Endian or Little Endian byte format.  
             Supported on IPSG-M2PA associations only.
    PVALUE : Valid range = 32-bits
             BIT                               BIT VALUE
             0=Payload Protocol Indicator      0=Big Endian , 1=Little Endian
             1-31=Reserved
  3. Change the UA parameter set values using the chg-uaps command with the UA parameter set value used in 1. If the parm and pvalue parameters are being specified, see these tables for the valid values of the pvalue parameter.

    For this example, enter this command.

    chg-uaps:set=3:timer=2:tvalue=2000:parm=2:pvalue=1:parm=3:pvalue=3

    The value of the pvalue parameter can be entered as either a decimal value or a hexadecimal value. This example shows the pvalue parameter value of the chg-uaps command being entered as a decimal value. If the decimal value of the pvalue parameter is 3, specify the pvalue=h’3 parameter to specify the hexadecimal value for the pvalue parameter.

    chg-uaps:set=3:timer=2:tvalue=2000:parm=2:pvalue=h’1:parm=3:pvalue=h’3

    If the values from one UA parameter set are being copied to another UA parameter set, only the set and scrset parameters can be specified with the chg-uaps command. For example, to copy the values from UA parameter set 10 to UA parameter set 5, enter this command.

    chg-uaps:set=5:scrset=10

    When this command has successfully completed, this message should appear. 
    
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-UAPS:  MASP A - COMPLTD
  4. Verify the changes using the rtrv-uaps command with the UA parameter set name used in 3. For this example, enter this command.

    rtrv-uaps:set=3

    This is an example of possible output. 

    
rlghncxa03w 10-07-28 09:12:36 GMT EAGLE5 42.0.0
    SET  TIMER      TVALUE  PARM      PVALUE
     3       1           0     1           3
     3       2        2000     2           1
     3       3       10000     3           3
     3       4        5000     4           0
     3       5           0     5           0
     3       6           0     6           0
     3       7           0     7           0
     3       8           0     8           0
     3       9           0     9           0
     3      10           0    10           0

    TIMER 2: False IP Connection Congestion Timer, max time an
             association can be congested before failing due to false
             congestion. SS7IPGW and IPGWI applications enforce
             0-30000(ms). Not supported on IPSG application.
    TVALUE : Valid range = 32-bits

    TIMER 3: UA HeartBeat Period Timer T(beat), time (ms) between sending
             of BEAT msgs by NE. IPSG, SS7IPGW and IPGWI applications
             enforce 100(ms)-60000(ms).
    TVALUE : Valid range = 32-bits

    TIMER 4: UA HeartBeat Received Timer T(beat ack), timeout period for
             response BEAT ACK msgs by NE. IPSG, SS7IPGW and IPGWI
             applications enforce 100(ms)-10000(ms).
    TVALUE : Valid range = 32-bits

    PARM  1: ASP SNM options.  Each bit is used as an enabled/disabled
             flag for a particular ASP SNM option. Not supported on IPSG
             application.
    PVALUE : Valid range = 32-bits
             BIT                                  BIT VALUE
             0=Broadcast                          0=Disabled , 1=Enabled
             1=Response Method                    0=Disabled , 1=Enabled
             2-5=Reserved
             6=Broadcast Congestion Status Change 0=Disabled , 1=Enabled
             7-31=Reserved

    PARM  2: ASP/AS Notification options.  Each bit is used as an
             enabled/disabled flag for a particular ASP/AS
             Notification option.  Not supported on IPSG application.
    PVALUE : Valid range = 32-bits
             BIT                                  BIT VALUE
             0=ASP Active Notifications           0=Disabled , 1=Enabled
             1=ASP Inactive Notifications         0=Disabled , 1=Enabled
             2=ASP AS State Query                 0=Disabled , 1=Enabled
             3-31=Reserved

    PARM  3: UA Serviceability Options.  Each bit is used as an
             enabled/disabled flag for a particular UA Serviceability
             option. Supported on IPSG, SS7IPGW, and IPGWI applications.
             UA Graceful Shutdown supported on IPSG for M3UA only.
    PVALUE : Valid range = 32-bits
             BIT                                  BIT VALUE
             0=UA Heartbeats                      0=Disabled , 1=Enabled
             1=UA Graceful Shutdown               0=Disabled , 1=Enabled 
             2-31=Reserved

    PARM  4: SCTP Payload Protocol Indicator byte order option. Bit indicates 
             PPI value is RCV/TX in Big Endian or Little Endian byte format.  
             Supported on IPSG-M2PA associations only.
    PVALUE : Valid range = 32-bits
             BIT                               BIT VALUE
             0=Payload Protocol Indicator      0=Big Endian , 1=Little Endian
             1-31=Reserved

    If 2 was performed, for this example, enter this command.

    rtrv-uaps:set=5

    This is an example of possible output. 

    
rlghncxa03w 10-07-28 09:12:36 GMT EAGLE5 42.0.0
    SET  TIMER      TVALUE  PARM      PVALUE
      5      1           0     1           3
      5      2        3000     2           0
      5      3       10000     3           0
      5      4        5000     4           0
      5      5           0     5           0
      5      6           0     6           0
      5      7           0     7           0
      5      8           0     8           0
      5      9           0     9           0
      5     10           0    10           0

    TIMER 2: False IP Connection Congestion Timer, max time an
             association can be congested before failing due to false
             congestion. SS7IPGW and IPGWI applications enforce
             0-30000(ms). Not supported on IPSG application.
    TVALUE : Valid range = 32-bits

    TIMER 3: UA HeartBeat Period Timer T(beat), time (ms) between sending
             of BEAT msgs by NE. IPSG, SS7IPGW and IPGWI applications
             enforce 100(ms)-60000(ms).
    TVALUE : Valid range = 32-bits

    TIMER 4: UA HeartBeat Received Timer T(beat ack), timeout period for
             response BEAT ACK msgs by NE. IPSG, SS7IPGW and IPGWI
             applications enforce 100(ms)-10000(ms).
    TVALUE : Valid range = 32-bits

    PARM  1: ASP SNM options.  Each bit is used as an enabled/disabled
             flag for a particular ASP SNM option. Not supported on IPSG
             application.
    PVALUE : Valid range = 32-bits
             BIT                                  BIT VALUE
             0=Broadcast                          0=Disabled , 1=Enabled
             1=Response Method                    0=Disabled , 1=Enabled
             2-5=Reserved
             6=Broadcast Congestion Status Change 0=Disabled , 1=Enabled
             7-31=Reserved

    PARM  2: ASP/AS Notification options.  Each bit is used as an
             enabled/disabled flag for a particular ASP/AS
             Notification option.  Not supported on IPSG application.
    PVALUE : Valid range = 32-bits
             BIT                                  BIT VALUE
             0=ASP Active Notifications           0=Disabled , 1=Enabled
             1=ASP Inactive Notifications         0=Disabled , 1=Enabled
             2=ASP AS State Query                 0=Disabled , 1=Enabled
             3-31=Reserved

    PARM  3: UA Serviceability Options.  Each bit is used as an
             enabled/disabled flag for a particular UA Serviceability
             option. Supported on IPSG, SS7IPGW, and IPGWI applications.
             UA Graceful Shutdown supported on IPSG for M3UA only.
    PVALUE : Valid range = 32-bits
             BIT                                  BIT VALUE
             0=UA Heartbeats                      0=Disabled , 1=Enabled
             1=UA Graceful Shutdown               0=Disabled , 1=Enabled 
             2-31=Reserved

    PARM  4: SCTP Payload Protocol Indicator byte order option. Bit indicates 
             PPI value is RCV/TX in Big Endian or Little Endian byte format.  
             Supported on IPSG-M2PA associations only.
    PVALUE : Valid range = 32-bits
             BIT                               BIT VALUE
             0=Payload Protocol Indicator      0=Big Endian , 1=Little Endian
             1-31=Reserved
  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 4-44 Changing a UA Parameter Set



4.39 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 4-45 Turning the Large MSU Support for IP Signaling Feature Off