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.

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.

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.

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.

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.

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

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

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.
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;
```
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;
```
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.
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;
```

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