Changing the Host Values of an IPSG Association

This procedure is used to change the host values of an IPSG association, assigned to E5-ENET cards that are running the IPSG application, IPSG cards, using the chg-assoc command.

If you wish to change the host values of M2PA associations assigned to cards that are running the IPLIM or IPLIMI applications, perform the Changing the Host Values of a M2PA Association procedure.

If you wish to change the host values of M3UA associations assigned to cards that are running the SS7IPGW or IPGWI applications, perform the Changing the Host Values of a M3UA or SUA 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.

:alhost – The alternate local host name, shown in the rtrv-ip-host output.

:adapter – The adapter layer for this association, m2pa or 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. If the open=no parameter is specified for an established IPSG M3UA association, and the UA Graceful Shutdown option is enabled (refer to Changing a UA Parameter Set for more information), the IPSG M3UA connection will be gracefully shutdown.

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

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

:uaps – The UA parameter set value being assigned to an M2PA or an M3UA association.

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

bufsize - Changing the Buffer Size of an IPSG Association
Other attributes of the IPSG association - Changing the Attributes of an IPSG Association

At least one optional parameter must be specified.

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

The EAGLE can contain a maximum of 4000 connections.

A maximum of 32 associations can be assigned to an IPSG card running on an E5-ENET/E5--ENET-B card or DEIR card.

An IPSG application running on the SLIC card can contain a maximum of 128 associations.

Before the local host value of the IPSG association can be changed, the signaling link that the association is assigned to must be removed by performing one of these procedures.

If the ADAPTER value of the association is M2PA, perform the Removing an IPSG M2PA Signaling Link procedure.
If the ADAPTER value of the association is M3UA, perform the Removing an IPSG M3UA Signaling Link procedure.

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 IPSG 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 IPSG card while the alhost parameter value represents an IPSG address corresponding to the other network interface of the same IPSG 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 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.

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

This is an example of possible output.


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

                CARD IPLNK
ANAME           LOC  PORT  LINK ADAPTER LPORT RPORT OPEN ALW
swbel32         1201 A     A    M3UA    1030  2345  YES  YES
a2              1305 A     A    SUA     1030  2345  YES  YES
a3              1307 A     A    SUA     1030  2346  YES  YES
assoc1          1201 A     A    M3UA    2000  1030  YES  YES
assoc2          2105 A     A    M2PA    2048  2048  YES  YES
assoc3          2105 A     B2   M2PA    3000  3000  YES  YES
assoc5          2105 A     A3   M2PA    1500  3000  YES  YES

Enter the rtrv-card command with the location of the card that is hosting the IPSG association that will be changed in this procedure. For this example, enter this command.
rtrv-card:loc=2105

This is an example of possible output.
```
rlghncxa03w 08-04-06 15:17:20 EST EAGLE5 38.0.0
CARD   TYPE      APPL     LSET NAME   LINK SLC LSET NAME   LINK SLC
2105   ENET      IPSG     e5e6a       A    0   e5e6a       B2   1
                          e5e6a       A3   2
```
If the application assigned to the card is IPSG, 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 Oracle.
If the application assigned to the card is IPLIM or IPLIMI, perform the Changing the Host Values of a M2PA Association procedure.

If the application assigned to the card is SS7IPGW or IPGWI, perform the Changing the Host Values of a M3UA or SUA Association procedure.
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;
```

Display the association being changed by entering the rtrv-assoc command with the aname parameter specified in 3.

For this example, enter this command.

rtrv-assoc:aname=assoc2

This is an example of the possible output.


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

       LSN
       e5e6a

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

Continue the procedure by performing 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 11.

Verify that the local host name to be assigned to the association is in the database by entering the rtrv-ip-host:display=all command.

The following is an example of the possible output.


rlghncxa03w 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. Oracle. COM
192.1.1.14      IPNODE1-1205
192.1.1.20      IPNODE2-1201
192.1.1.22      IPNODE2-1203
192.1.1.24      IPNODE2-1205
192.1.1.30      KC-HLR1
192.1.1.32      KC-HLR2
192.1.1.50      DN-MSC1
192.1.1.52      DN-MSC2
192.1.1.54      M2PA1

REMOTE IPADDR   REMOTE HOST
150.1.1.5       NCDEPTECONOMIC_DEVELOPMENT. SOUTHEASTERN_COORIDOR_ASHVL. GOV

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

If the required IP host is shown in the rtrv-ip-host output, continue the procedure with 7.

If the required IP host is not shown in the rtrv-ip-host output, continue the procedure with 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.20      255.255.255.0   FULL    100   DIX     NO   NO
1201  B    --------------- --------------- HALF    10    DIX     NO   NO
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
2103  A    192.1.1.22      255.255.255.0   FULL    100   DIX     NO   NO
2103  B    --------------- --------------- HALF    10    DIX     NO   NO
2105  A    192.1.1.24      255.255.255.0   FULL    100   DIX     NO   NO
2105  B    192.1.1.54      255.255.255.0   FULL    100   DIX     NO   NO
2205  A    192.1.1.30      255.255.255.0   FULL    100   DIX     NO   NO
2205  B    --------------- --------------- HALF    10    DIX     NO   NO
2207  A    192.1.1.32      255.255.255.0   FULL    100   DIX     NO   NO
2207  B    --------------- --------------- HALF    10    DIX     NO   NO
2213  A    192.1.1.50      255.255.255.0   FULL    100   DIX     NO   NO
2213  B    --------------- --------------- HALF    10    DIX     NO   NO
2301  A    192.1.1.52      255.255.255.0   FULL    100   DIX     NO   NO
2301  B    --------------- --------------- HALF    10    DIX     NO   NO

IP-LNK   table is (20 of 2048) 1% full.
```
If the required IP link, one that contains the desired IP address, is not shown in the rtrv-ip-lnk output, add the IP link using the Configuring an IP Link procedure. After the IP link has been added, assign the IP address of the IP link to the IP host name using the Adding an IP Host procedure.

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.

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.
After the new IP host has been added, continue the procedure by performing one of these steps.
- If the ADAPTER value of the association is not being changed, continue the procedure with 11.
- If the ADAPTER value of the association is being changed, continue the procedure by performing one of these steps.
  - If the ADAPTER value of the association is being changed to M2PA, perform one of these steps.
    
    If the m2patset, ver, and uaps parameters will not be specified for the association, continue the procedure with 11.
    
    If the m2patset and ver parameters will be specified for the association, continue the procedure with 9.
    
    If only the uaps parameter will be specified for the association, continue the procedure with 10.
  - If the ADAPTER value of the association is being changed to M3UA, perform one of these steps.
    
    If the uaps parameter will not be specified for the association, continue the procedure with 11.
    
    If the uaps parameter will be specified for the association, continue the procedure with 10.
Display the associations that are assigned to the new local host by entering the rtrv-assoc command with the name of the new local host. For this example, enter this command.
rtrv-assoc:lhost="IPNODE2-1201"

The following is an example of the possible output.
```
rlghncxa03w 08-04-19 21:17:04 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
assoc1          1201  A     A    M3UA    2000  1030  YES  YES

IP Appl Sock/Assoc table is (7 of 4000) 1% full
Assoc Buffer Space Used (400 KB of 6400 KB) on LOC = 1201
```
A maximum of 32 associations can be assigned to a local host. If 32 associations are shown in this steps, repeat this procedure from 5 and choose another local host.

If the number of associations shown in this step is less than 32, continue the procedure with 8.
Before the local host of the association can be changed, the association cannot be assigned to a signaling link.
If dashes are shown in the LINK column of the rtrv-assoc output in 1, the association is not assigned to a signaling link.
If the association is assigned to a signaling link, perform one of these procedures.
- If the ADAPTER value of the association is M2PA, perform the Removing an IPSG M2PA Signaling Link procedure.
- If the ADAPTER value of the association is M3UA, perform the Removing an IPSG M3UA Signaling Link procedure.
After the signaling link has been removed, or if the association is not assigned to a signaling link, continue the procedure by performing one of these steps.
- If the ADAPTER value of the association is not being changed, continue the procedure with 11.
- If the ADAPTER value of the association is being changed, continue the procedure by performing one of these steps.
  - If the ADAPTER value of the association is being changed to M2PA, perform one of these steps.
    
    If the m2patset, ver, and uaps parameters will not be specified for the association, continue the procedure with 11.
    
    If the m2patset and ver parameters will be specified for the association, continue the procedure with 9.
    
    If only the uaps parameter will be specified for the association, continue the procedure with 10.
  - If the ADAPTER value of the association is being changed to M3UA, perform one of these steps.
    
    If the uaps parameter will not be specified for the association, continue the procedure with 11.
    
    If the uaps parameter will be specified for the association, continue the procedure with 10.

Verify the values of the M2PA timer set you wish to assign to the association by entering the rtrv-m2pa-tset command with the M2PA version (either ver=rfc to display the RFCM2PA timer values or ver=d6 to display the Draft 6 M2PA timer values) of the timer set you wish to assign to the association.

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

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

rtrv-m2pa-tset:ver=d6

This is an example of the possible output.


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

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

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

To display the M2PARFC values, enter this command.

rtrv-m2pa-tset:ver=rfc

This is an example of the possible output.


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

M2PA RFC Timers (in msec, T16 in microsec)

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

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


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

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

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

M2PA RFC Timers (in msec, T16 in microsec)

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

Caution:

Changing anM2PA timer set may affect the performance of any associations using the timer set being changed.

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

After the M2PA timer set values have been changed, of if you do not wish to change any of the M2PA timer set values, continue the procedure by performing one of these steps.

If the uaps parameter will not be specified for the association, continue the procedure with 11.
If the uaps parameter will be specified for the association, continue the procedure with 10.

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.

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 you do not wish to change the UA parameter set values, continue the procedure with 11.

If the UA parameter set you wish to assign to the association does not contain the desired values, go to the Changing a UA Parameter Set procedure and change the desired parameter set values. After the UA parameter set values have been changed, continue the procedure with 11.

Caution:

Changing aUA parameter set may affect the performance of any associations using the parameter set being changed.

Change the association using the chg-assoc command.
For this example, enter this command.

chg-assoc:aname=assoc2:lhost=m2pa2:alhost=m2pa3

Note:
See (Sheet 7) for the rules that apply to thechg-assoc command.
These are the rules that apply to changing the host values of an IPSG association.
- If any optional parameters are not specified with the chg-assoc command, those values are not changed.
- The EAGLE can contain a maximum of 4000 connections.
- The host of an IPSG association can contains a maximum of 32 IPSG associations.
- The value of the lhost 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.
- The m2patset and ver parameters can be specified only for IPSG M2PA associations.
- If the mp2atset parameter is not specified with the chg-assoc command, and the adapter parameter value is being changed to m2pa, the m2patset parameter value defaults to M2PA timer set 1 (m2patset=1).
- The M2PA version of the association determines the version of the M2PA timer set that is assigned to the association. For example, if M2PA timer set 3 is assigned to the M2PA association, and the association is an RFC M2PA association, the RFC version of M2PA timer set 3 is used with the association. If M2PA timer set 7 is assigned to the M2PA association, and the association is a Draft 6 M2PA association, the Draft 6 version of M2PA timer set 7 is used with the association.
- If the adapter parameter value of the association is changed to m2pa in this procedure and the ver parameter is not specified, the version of the association will be RFC. To make this association a M2PA Draft 6 association, the ver=d6 parameter must be specified for this association.
When this command has successfully completed, this message should appear.
```
rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0
CHG-ASSOC: MASP A - COMPLTD;
```
Continue the procedure by performing one of these steps.
- If the association was not assigned to a signaling link when this procedure was started, and the open parameter value was not changed in 3, continue the procedure with Oracle.
- If the association was not assigned to a signaling link when this procedure was started, and the open parameter value was changed in 3, continue the procedure with 12.
- If the association was assigned to a signaling link when this procedure was started, continue the procedure with 12.
Assign the association to a signaling link by performing one of these procedures.
If the ADAPTER value of the association is M2PA, perform the Adding an IPSG M2PA Signaling Link procedure.

If the ADAPTER value of the association is M3UA, perform the Adding an IPSG M3UA Signaling Link procedure.
After the association has been assigned to a signaling link, continue the procedure with one of these steps.
- If the open parameter value was not changed in 3, continue the procedure with Oracle.
- If the open parameter value was changed in 3, continue the procedure with 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;
```

Verify the changes using the rtrv-assoc command specifying the association name specified in 11 and 13.

For this example, enter this command.

rtrv-assoc:aname=assoc2

This is an example of possible output.


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

       LSN
       e5e6a

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


rlghncxa03w 09-05-28 21:14:37 GMT EAGLE5 41.0.0
 ANAME assoc2
       LOC      2107          IPLNK PORT  A,B        LINK  --
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    M2PA2
       ALHOST   M2PA3
       RHOST    gw200.nc-tekelec.com
       ARHOST   ---
       LPORT    2048          RPORT       2048
       ISTRMS   2             OSTRMS      2          BUFSIZE  400
       RMODE    LIN           RMIN        120        RMAX     800
       RTIMES   10            CWMIN       3000       M2PATSET 1
       OPEN     NO            ALW         YES        RTXTHR   2000
       RHOSTVAL RELAXED

       LSN
       e5e6a

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

Back up the new changes, using the chg-db:action=backup:dest=fixed command.
These messages should appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first.
```
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.
```
If you wish to change the other attributes of the IPSG association, perform one of these procedures.
- bufsize - Changing the Buffer Size of an IPSG Association
- Other attributes of the IPSG Association - Changing the Attributes of an IPSG Association
If you do not wish to change the other attributes of the IPSG association, this procedure is finished.

Figure 6-29 Changing the Host Values of an IPSG 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