Changing the Attributes of an IPSG Association

This procedure is used to change the values of the attributes of an IPSG association, assigned to cards that are running the IPSG application, IPSG cards, using the chg-assoc command and the following parameters.

Table 6-12 Change IPSG Association Parameters

aname	lport	rhost	rport	open	alw
rmode	rmin	rmax	rtimes	cwmin	istrms
ostrms	m2patset	ver	rtxthr	uaps	rhosttype
rhostval

If you wish to change the attributes of M2PA associations assigned to cards that are running the IPLIM or IPLIMI applications, perform Changing the Attributes of an M2PA Association.

If you wish to change the attributes of M3UA associations assigned to cards that are running the SS7IPGW or IPGWI applications, perform Changing the Attributes of a M3UA or SUA Association.

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

lhost and alhost - Changing the Host Values of an IPSG Association.
bufsize - Changing the Buffer Size of an IPSG Association

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

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

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

Note:

If the adapter parameter value for the association is M3UA, the alw parameter cannot be specified.

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

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

: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 association must be assigned to a signaling link.

At least one optional parameter is required.

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

The value of the rmin parameter must be less than or equal to the rmax parameter value.

The m2patset and ver parameters can be specified only for IPSG M2PA associations.

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 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
assoc2          1205 A     A    M2PA    2048  2048  YES  YES
assoc3          1205 A     B2   M2PA    3000  3000  YES  YES
assoc5          1205 A     A3   M2PA    1500  3000  YES  YES

Enter the rtrv-card command with the location of the card that is hosting the M2PA or M3UA association that will be changed in this procedure. For this example, enter these commands.
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   ENET      IPSG     e5e6a       A    0   e5e6a       B2   1
                          e5e6a       A3   2
```
rtrv-card:loc=1201

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
1201   ENET      IPSG     ipsgm3ua1   A    0   
```
If the application assigned to the card is IPSG, shown in the APPL column, and the values of any of these parameters are being changed: lport, rhost, rport, rmode, rmin, rmax, rtimes, cwmin, istrms, ostrms, ver, m2patset, or uaps, continue the procedure by performing one of these steps.
- If the open parameter value for the association is yes, continue the procedure with 3.
- If the open parameter value for the association is no, continue the procedure with 4.
If the application assigned to the card is IPSG, 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 steps.

Note:
If the adapter parameter value for the association is M3UA, the alw parameter cannot be specified.
- 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 10.
- If the value of the rtxthr parameter is being changed, continue the procedure with 4.
- If the value of the open parameter value is being changed to yes, the association must be assigned to a signaling link. If the association is assigned to a signaling link, the signaling link value is shown in the LINK column in the rtrv-assoc output, in 1. If the association is not assigned to a signaling link, dashes are shown in the LINK column in the rtrv-assoc output. If association is assigned to a signaling link, perform one of these actions.
  - If only the alw parameter is being specified with the open=yes parameter, continue the procedure with 10.
  - If the value of the rtxthr parameter is being changed, continue the procedure with 4.
- If the value of the open parameter value is being changed to yes and the association is not assigned to a signaling link, perform one of these procedures.
  - If the ADAPTER value of the association is M2PA, perform Adding an IPSG M2PA Signaling Link.
  - If the ADAPTER value of the association is M3UA, perform Adding an IPSG M3UA Signaling Link.
- After the association has been assigned to a signaling link, perform one of these actions.
  - If only the alw parameter is being specified with the open=yes parameter, continue the procedure with 10.
  - If the value of the rtxthr parameter is being changed, continue the procedure with 4.
If the application assigned to the card is IPLIM or IPLIMI, perform Changing the Attributes of an M2PA Association.

If the application assigned to the card is SS7IPGW or IPGWI, perform Changing the Attributes of a M3UA or SUA Association.
Change the value of the open parameter to no by specifying the chg-assoc command with the open=no parameter.
For this example, enter these commands.

chg-assoc:aname=assoc2:open=no

chg-assoc:aname=assoc1:open=no

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

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

For this example, enter these commands.

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      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    remotehost1
       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 (7 of 4000) 1% full
Assoc Buffer Space Used (800 KB of 6400 KB) on LOC = 1205

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    m3ua1
      ALHOST   ---
      RHOST    remote1
      ARHOST   ---
      LPORT    2000          RPORT      1030
      ISTRMS   2             OSTRMS     2           BUFSIZE  200
      RMODE    LIN           RMIN       120         RMAX     800
      RTIMES   10            CWMIN      3000        UAPS     10
      OPEN     NO            ALW        NO          RTXTHR   0
      RHOSTVAL RELAXED

      LSN
      ipsgm3ua1

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

Continue the procedure by performing one of these actions.

If the cwmin parameter will be be specified in this procedure, continue the procedure with 5.

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 by performing one of these actions.
  - If the m2patset parameter will be specified for an M2PA association, continue the procedure with 6.
  - If the uaps parameter will be specified for an M3UA association, continue the procedure with 7.
  - If the rhost parameter will be specified for the association, continue the procedure with 8.
  - If the m2patset, uaps, or rhost parameter will not be specified for the association, 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 perform Changing the Buffer Size of an IPSG 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 by performing one of these actions.
  - If the m2patset parameter will be specified for an M2PA association, continue the procedure with 6.
  - If the uaps parameter will be specified for an M3UA association, continue the procedure with 7.
  - If the rhost parameter will be specified for the association, continue the procedure with 8.
  - If the m2patset, uaps, or rhost parameter will not 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, perform the Changing an M2PA Timer Set procedure to change the desired timer values.

After the M2PA timer set values have been changed, or if you have decided not to change the M2PA timer set values, continue the procedure by performing one of these actions.

If the uaps parameter will be specified for an M3UA association, continue the procedure with 7.
If the rhost parameter will be specified for the association, continue the procedure with 8.
If the uaps or rhost parameter will not 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

Caution:

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

If the UA parameter set you wish to assign to the association does not contain the desired values, perform the Changing a UA Parameter Set procedure to change the desired parameter set values.

After the UA parameter set values have been changed, or if you have decided not to change the UA parameter set values, continue the procedure by performing one of these actions.

If the rhost parameter will be specified for the association, continue the procedure with 8.
If the uaps or rhost parameter will not be specified for the association, continue the procedure with 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 10.

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 10. If the association does not have a primary remote host, continue the procedure with 9.
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;
```
Change the association using the chg-assoc command.
For this example, enter these commands.

chg-assoc:aname=assoc2:rhost=”gw200.nc-Oracle.com” :rport=3000:rtxthr=10000:rhostval=match

chg-assoc:aname=assoc1:rport=3000:rtxthr=10000:uaps=3: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

Note:
Them2patset andver parameters can be specified only for M2PA associations.

If only the alw, open, rtxthr parameter values are being changed in this step, for this example, enter this command.

Note:
If theadapter parameter value for the association is M3UA, thealw parameter cannot be specified.

chg-assoc:aname=assoc2:alw=no:open=yes:rtxthr=10000
These are the rules that apply to changing the attributes of an IPSG association.
1. If any optional parameters are not specified with the chg-assoc command, those values are not changed.
2. 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.
3. 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 value must be no.
4. The value of the rmin parameter must be less than or equal to the rmax parameter value.
5. 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.
6. The m2patset and ver parameters can be specified only for IPSG M2PA associations.
7. If the adapter parameter value for the association is M3UA, the alw parameter cannot be specified.
When 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;
```
If the value of the open parameter was not changed in 3, continue the procedure with Oracle.
Change the value of the open parameter to yes by specifying the chg-assoc command with the open=yes parameter.
For this example, enter these commands.

chg-assoc:aname=assoc2:open=yes

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

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

For this example, enter these commands.

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      1205          IPLNK PORT  A          LINK  A
       ADAPTER  M2PA          VER         M2PA RFC
       LHOST    IPNODE2-1205
       ALHOST   ---
       RHOST    gw200.nc-Oracle.com
       ARHOST   gw210.nc-Oracle.com
       LPORT    2048          RPORT       2048
       ISTRMS   2             OSTRMS      2          BUFSIZE  400
       RMODE    LIN           RMIN        120        RMAX     800
       RTIMES   10            CWMIN       3000       UAPS     10
       OPEN     YES           ALW         NO         RTXTHR   10000
       RHOSTVAL MATCH         M2PATSET    1

       LSN
       e5e6a

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

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    m3ua1
      ALHOST   ---
      RHOST    remote1
      ARHOST   ---
      LPORT    2000          RPORT      3000
      ISTRMS   2             OSTRMS     2           BUFSIZE  200
      RMODE    LIN           RMIN       120         RMAX     800
      RTIMES   10            CWMIN      3000        UAPS     3
      OPEN     YES           ALW        NO          RTXTHR   10000
      RHOSTVAL MATCH
       
      LSN
      ipsgm3ua1

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

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 IPSG association, perform one of these procedures.
- lhost and alhost - Changing the Host Values of an IPSG Association
- bufsize - Changing the Buffer Size of an IPSG Association
If you do not wish to change the lhost, alhost, bufsize, or link values of the IPSG association, this procedure is finished.

Figure 6-27 Changing the Attributes of an IPSG Association

Sheet 1 of 5

Sheet 2 of 5

Sheet 3 of 5

Sheet 4 of 5

Sheet 5 of 5