1. Database Administration - IP7 User's Guide
  2. IETF M3UA and SUA Configuration Procedures
  3. Adding a New Association to an Existing Application Server

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