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.

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.

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.

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.

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.

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

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