1. Database Administration - IP7 User's Guide
  2. IETF M2PA Configuration Procedures
  3. Adding an M2PA Association

Adding an M2PA Association

This procedure is used to configure M2PA associations using the ent-assoc command. The combination of a local host, local SCTP port, remote host and remote SCTP port defines an association. M2PA associations are assigned to cards running either the IPLIM or IPLIMI applications (IPLIMx cards).

The ent-assoc command uses these parameters:

:aname – The name assigned to the association. Valid association names can contain up to 15 alphanumeric characters where the first character is a letter and the remaining characters are alphanumeric characters. The aname parameter value is not case-sensitive.

:lhost – Local Hostname. The logical name assigned to the local host device.

:lport – The SCTP port number for the local host.

:rhost – Remote Hostname. The logical name assigned to the remote host device.

:rport – The SCTP port number for the remote host.

:link – The signaling link on the IP card. If a signaling link is not specified for a association when it is entered, the association defaults to signaling link A. If the card is an E5-ENET or E5-ENET-B card, the values for the link parameter can be a, a1, a2, a3, a4, a5, a6, a7, b, b1, b2, b3, b4, b5, b6, or b7.

Note:

The port parameter can be used in place of the link parameter to specify the signaling link on the card.

:adapter – The adapter layer for this association, m2pa. The adapter parameter is optional. The default value for the adapter parameter is m2pa.

:alhost – The alternate local host name.

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

Associations contain fields whose values are not assigned using the ent-assoc command. When an association is added to the database, these fields receive their default values. If a different value is desired, the chg-assoc command must be used. To change these values perform the Changing the Attributes of an M2PA Association procedure.

These fields and their default values are shown in Table 3-6.

Table 3-6 M2PA Association Fields and Default Values

open=no

rmax=800

cwmin=3000

alw=no

uaps=10

istrms=2

rmode=lin

rtimes=10

ostrms=2

rmin=120

ver=rfc bufsize=200 rtxthr=0 rhostval=relaxed

An M2PA association that is assigned to an IPLIMx signaling link can contain a UA parameter set value (the uaps parameter). The uaps parameter cannot be specified with the ent-assoc command. The default value for the uaps parameter is 10. While the uaps parameter value can be changed with the chg-assoc command, the uaps parameter value has no impact on the traffic carried by an M2PA association that is assigned to an IPLIMx signaling link.The uaps parameter value impacts M3UA or SUA associations that are assigned to IPGWx signaling links and M2PA and M3UA associations that are assigned to IPSG cards. The uaps parameter value is shown in the UAPS field in the rtrv-assoc output for an M2PA associations that is assigned to an IPLIMx signaling link.

An M2PA association can contain an alternate remote host. The alternate remote host is provisioned with the rhost and rhostype=alternate parameters of the chg-assoc command. A primary remote host can be provisioned in this procedure by specifying the rhost parameter with the ent-assoc command. To provision an alternate remote host for an M2PA association, perform Changing the Attributes of an M2PA Association.

The size of the buffers on the on the E5-ENET and E5-ENET-B cards are shown in the following list.

  • E5-ENET Card and E5-ENET-B - 3200 KB

The size of the buffers assigned to each association that is assigned to the IP card cannot exceed the maximum buffer size for the IP card. When a new association is added, the default buffer size for the association is assigned to the association. If adding the new association causes the total buffer size for all the associations on the IP card to exceed the maximum buffer size for that IP card, the ent-assoc command will be rejected. If the you wish to add the association and the maximum buffer size for the IP card will be exceeded, the buffer size of the other associations assigned to the IP card must be decreased by performing the Changing the Buffer Size of a M2PA Association procedure. The available size of the buffers on the IP card can be verified by entering this command.

rtrv-assoc:lhost=<local host name assigned to the association being changed>

The alhost parameter can also be used with the rtrv-assoc command to display the available size of the buffers on the IP card.

The aname parameter can be used with the rtrv-assoc command to display the available size of the buffers on the IP card and the size of the buffer assigned to the association.

The value of the lhost, rhost, or alhost parameters is a text string of up to 60 characters, with the first character being a letter. The command line on the terminal can contain up to 150 characters. If the host names are too long to fit on the ent-assoc command line, perform the chg-assoc command with the parameters and values necessary to complete the entry of the M2PA association.

The EAGLE can contain a maximum of 4000 connections (association to application server assignments).

IPLIMx cards can contain one association for each signaling link on the card. The E5-ENET card can contain a maximum of 16 signaling links, resulting in a maximum of 16 associations for this card.

The B Ethernet interface of the IP card can be used on the E5-ENET card.

If the association is to be activated in this procedure, with the chg-assoc command, the association must contain values for the lhost, lport, rhost, rport parameters.

The ipliml2 parameter value of the signaling link assigned to the association must be m2pa. The adapter parameter value of the association must be m2pa.

The signaling link being assigned to the association must be out of service. This state is shown in the rept-stat-slk output with the entries OOS-MT in the PST field and Unavail in the SST field.

If the association is being opened in this procedure with the chg-assoc command and the open=yes parameter, the signaling link assigned to the association must be in the database and the ipliml2 parameter value of the signaling link assigned to the association must be m2pa.

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

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.

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.

  1. 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
assoc3          1203 A     A1   M2PA    2048  1030  NO   NO
    Perform one of these actions.
    • If the desired IP link (shown by the entries in the CARD LOC and IPLINK PORT columns for an association whose ADAPTER value is M2PA) is shown in the rtrv-assoc output, continue the procedure with 2.
    • If the desired IP link is not shown in the rtrv-assoc output, continue the procedure with 3.
  2. Display the signaling links assigned to the card that the new M2PA association will be assigned to by entering the rtrv-slk command with the card location displayed in 1. For this example, enter this command.

    rtrv-slk:loc=1203

    The following is an example of the possible output. 

    rlghncxa03w 08-04-06 10:07:25 GMT EAGLE5 38.0.0

LOC  LINK LSN         SLC TYPE     IPLIML2
1203 A    e5e6a       0   IPLIM    M2PA
1203 A1   m2pa1       0   IPLIM    M2PA

    If the value in the TYPE column is either IPLIM or IPLIMI, continue the procedure with 6.

    If the value in the TYPE column is IPSG, the links and host assigned to this card cannot be used in this procedure. If you wish to use this card to configure an M2PA association, perform the Adding an IPSG M2PA Association procedure.

    If you do not wish to use this card to configure an M2PA association, perform one of these actions.
    • Choose another card from the rtrv-assoc output in 1 and repeat this step.
    • Continue the procedure with 3 to choose another IPLIMx card and IP link for the new M2PA association.
  3. Display the IP links in the database by entering the rtrv-ip-lnk command. The following is an example of the possible output. 
    
rlghncxa03w 08-12-28 21:14:37 GMT EAGLE5 40.0.0
LOC   PORT IPADDR          SUBMASK         DUPLEX  SPEED MACTYPE AUTO MCAST
1201  A    192.1.1.10      255.255.255.128 HALF    10    802.3   NO   NO
1201  B    --------------- --------------- HALF    10    DIX     NO   NO
1203  A    192.1.1.12      255.255.255.0   ----    ---   DIX     YES  NO
1203  B    --------------- --------------- HALF    10    DIX     NO   NO
1205  A    192.1.1.14      255.255.255.0   FULL    100   DIX     NO   NO
1205  B    --------------- --------------- HALF    10    DIX     NO   NO
2101  A    192.1.1.20      255.255.255.0   FULL    100   DIX     NO   NO
2101  B    --------------- --------------- HALF    10    DIX     NO   NO
2103  A    192.1.1.22      255.255.255.0   FULL    100   DIX     NO   NO
2103  B    --------------- --------------- HALF    10    DIX     NO   NO
2105  A    192.1.1.24      255.255.255.0   FULL    100   DIX     NO   NO
2105  B    --------------- --------------- HALF    10    DIX     NO   NO
2205  A    192.1.1.30      255.255.255.0   FULL    100   DIX     NO   NO
2205  B    --------------- --------------- HALF    10    DIX     NO   NO
2207  A    192.1.1.32      255.255.255.0   FULL    100   DIX     NO   NO
2207  B    --------------- --------------- HALF    10    DIX     NO   NO
2213  A    192.1.1.50      255.255.255.0   FULL    100   DIX     NO   NO
2213  B    --------------- --------------- HALF    10    DIX     NO   NO
2301  A    192.1.1.52      255.255.255.0   FULL    100   DIX     NO   NO
2301  B    --------------- --------------- HALF    10    DIX     NO   NO

IP-LNK   table is (20 of 2048) 1% full.

    If the required IP link is not in the database, add the IP link using the Configuring an IP Link procedure.

  4. Verify that the local host name to be assigned to the association is in the database by using the rtrv-ip-host:display=all command. The following is an example of the possible output. 
    
rlghncxa03w 13-06-28 21:15:37 GMT EAGLE5 45.0.0

LOCAL IPADDR    LOCAL HOST
192.1.1.10      IPNODE1-1201
192.1.1.12      IPNODE1-1203
192.1.1.14      IPNODE1-1205
192.1.1.20      IPNODE2-1201
192.1.1.22      IPNODE2-1203
192.1.1.24      IPNODE2-1205
192.1.1.30      KC-HLR1
192.1.1.32      KC-HLR2
192.1.1.50      DN-MSC1
192.1.1.52      DN-MSC2

REMOTE IPADDR   REMOTE HOST
150.1.1.5       NCDEPTECONOMIC_DEVELOPMENT. SOUTHEASTERN_COORIDOR_ASHVL. GOV

IP Host table is (11 of 4096) .26% full

    The IP address of the IP link should be assigned to the local host name that will be assigned to the association.

    The ipliml2 parameter value of the signaling link must be m2pa.

    The values of the lhost and alhost parameters must be in the LOCAL HOST column in the rtrv-ip-host output.

    If the required hostname is not in the database, add the IP host name using the Adding an IP Host procedure.

  5. Display the signaling links assigned to the card that the new M2PA association will be assigned to by entering the rtrv-slk command with the card location displayed in 3 or the card location of the IP link that was configured by performing the Configuring an IP Link procedure in 3. For this example, enter this command.

    rtrv-slk:loc=1203

    The following is an example of the possible output. 

    rlghncxa03w 08-04-06 10:07:25 GMT EAGLE5 38.0.0

LOC  LINK LSN         SLC TYPE     IPLIML2
1203 A    e5e6a       0   IPLIM    M2PA
1203 A1   m2pa1       0   IPLIM    M2PA

    If the signaling link that you wish to assign to the association is shown in the rtrv-slk output, continue the procedure with 6.

    If the signaling link that you wish to assign to the association is not shown in the rtrv-slk output, add the signaling link to the database with the ipliml2=m2pa parameter, and without activating the signaling link, by performing the Adding an IPLIMx Signaling Link procedure. After the signaling link has been added, continue the procedure with 9.

  6. Display the status of the signaling link shown in 5 using the rept-stat-slk command specifying the card location and signaling link. For example, enter this command.

    rept-stat-slk:loc=1203:link=a

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
SLK      LSN         CLLI        PST          SST       AST
1203,A   e5e6a       ----------- IS-NR        Avail     ----
Command Completed.

    If the primary state (PST) of the signaling link is OOS-MT and the secondary state (SST) is Unavail, continue the procedure with 9.

    If the primary state (PST) of the signaling link not is OOS-MT and the secondary state (SST) is not Unavail, continue the procedure with 7.

  7. Deactivate the signaling link from 6 using the dact-slk command. For example, enter this command.

    dact-slk:loc=1203:link=a

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 08-04-07 11:11:28 GMT EAGLE5 38.0.0
Deactivate Link message sent to card
  8. Verify the status of the signaling link using the rept-stat-slk command. For example, enter this command.

    rept-stat-slk:loc=1203:link=a

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
SLK      LSN         CLLI        PST          SST       AST
1203,A   e5e6a       ----------- OOS-MT       Unavail   ----
Command Completed.
  9. Verify the values of the M2PA timer set you wish to assign to the association by entering the rtrv-m2pa-tset command with the ver=rfc parameter.
    When an M2PA association is provisioned in this procedure, the RFC M2PA version is assigned to the M2PA association by default.

    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 RFCM2PA 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 you wish to assign the Draft 6 M2PA version to this association and use the Draft 6 M2PA timer sets, perform the Changing the Attributes of an M2PA Association procedure after this procedure is completed to change the M2PA version of this association.

    Note:

    If them2patset parameter will not be specified with theent-assoc command, theM2PA timer set 1 will be assigned to the association.

    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 08-04-28 21:16:37 GMT EAGLE5 38.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 08-04-28 21:16:37 GMT EAGLE5 38.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 08-04-28 21:16:37 GMT EAGLE5 38.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

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

    Caution:

    Changing an M2PA timer set may affect the performance of any associations using the timer set being changed.
  10. Verify the available buffer size for the IP card that will contain the association being added in this procedure by entering the rtrv-assoc command with the local host name assigned to the association being added. For this example, enter this command.

    rtrv-assoc:lhost="IPNODE2-1203"

    This is an example of the 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
assoc2          1203 A     A1   M2PA    2048  1030  NO   NO 

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

    If adding the new association causes the total buffer size for all the associations on the IP card to exceed the maximum buffer size for that IP card, the ent-assoc command will be rejected.

    The default buffer value for an IPLIMx association is 200.

    If the you wish to add the association and the maximum buffer size for the IP card will be exceeded, the buffer size of the other associations assigned to the IP card must be decreased by performing the Changing the Buffer Size of a M2PA Association procedure.

  11. Add the associations using the ent-assoc command. For this example, enter this command.

    ent-assoc:aname=assoc2:lhost=gw107.nc.tekelec.com:lport=2000: rhost=gw100.nc.tekelec.com:rport=1030:adapter=m2pa:link=a

    These are the rules that apply to adding M2PA associations that are assigned to IPLIMx signaling links.
    • The B Ethernet interface can be used with E5-ENET cards.
    • The EAGLE can contain a maximum of 4000 connections (association – application server assignments plus sockets).
    • The adapter parameter value for the association must be m2pa. The value of the ipliml2 parameter of the signaling link being assigned to this association must be m2pa. The default value for the adapter parameter is m2pa.
    • IPLIMx cards can have only one connection for each signaling link assigned to the card. If the card is an E5-ENET card, the card may contain a maximum of 16 connections.
    • The value of the lhost, rhost, or alhost parameters is a text string of up to 60 characters, with the first character being a letter. The command line on the terminal can contain up to 150 characters. If the host names are too long to fit on the ent-assoc command line, perform the chg-assoc command with the parameters and values necessary to complete the entry of the M2PA association.
    • If the new association is to be activated in this procedure with the chg-assoc command, the association must contain values for the lhost, rhost, lport, and rport parameters.
    • If the lhost and alhost parameters are specified, the lhost parameter value represents the IP address corresponding to one of the network interfaces (A or B) on the IP card while the alhost parameter value represents the IP address corresponding to the other network interface of the same IP card.
    • The m2patset parameter can be specified only with the adapter=m2pa parameter.
    • The m2patset parameter value defaults to M2PA timer set 1 (m2patset=1) if the m2patset parameter is not specified.
    • The port parameter can be used in place of the link parameter to specify the signaling link assigned to the association.
    • When the adapter=m2pa parameter is specified, the RFC M2PA version is assigned to the M2PA association by default. If you wish to assign the Draft 6 M2PA version to this association, perform the Changing the Attributes of an M2PA Associationprocedure after this procedure is completed to change the M2PA version of this association.

    When each of these commands have successfully completed, this message should appear. 

    
rlghncxa03w 08-04-28 09:12:36 GMT EAGLE5 38.0.0
ENT-ASSOC: MASP A - COMPLTD

    Note:

    If the association added in this step is not being activated in this procedure, continue the procedure with13.
  12. Activate the association added in 11 by entering the chg-assoc command with the association name specified in 11 and the open=yes and alw=yes parameters. For example, enter this command.

    chg-assoc:aname=assoc2:open=yes:alw=yes

    When this command have successfully completed, this message should appear. 

    
rlghncxa03w 08-04-28 21:15:37 GMT EAGLE5 38.0.0
CHG-ASSOC: MASP A - COMPLTD
  13. Verify the changes using the rtrv-assoc command specifying the association name specified in 11 and 12. For this example, enter this command.

    rtrv-assoc:aname=assoc2

    This is an example of possible output. 

    
rlghncxa03w 10-07-28 09:12:36 GMT EAGLE5 42.0.0
ANAME assoc2
      LOC      1203          IPLNK PORT  A          LINK  A
      ADAPTER  M2PA          VER         M2PA RFC
      LHOST    gw105.nc.tekelec.com
      ALHOST   ---
      RHOST    gw100.nc.tekelec.com
      ARHOST   ---
      LPORT    1030          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       M2PATSET    1

IP Appl Sock table is (5 of 4000) 1% full
Assoc Buffer Space Used (400 KB of 1600 KB) on LOC = 1203
  14. Activate the signaling link assigned to the association using the act-slk command.

    For example, enter this command.

    act-slk:loc=1203:link=a

    When this command has successfully completed, the following message should appear. 

    
rlghncxa03w 08-04-07 11:11:28 GMT EAGLE5 38.0.0
Activate Link message sent to card
  15. Verify the status of the signaling link using the rept-stat-slk command. For example, enter this command.

    rept-stat-slk:loc=1203:link=a

    This is an example of the possible output. 

    
rlghncxa03w 08-04-28 21:16:37 GMT EAGLE5 38.0.0
SLK      LSN         CLLI        PST          SST       AST
1203,A   e5e6a       ----------- IS-NR        Avail     ----
Command Completed.
  16. 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 3-7 Adding an M2PA Association



Sheet 1 of 3



Sheet 2 of 3



Sheet 3 of 3