Removing a M3UA or SUA Association

This procedure is used to remove a SUA association from the database or to remove a M3UA association that is assigned to a card running either the SS7IPGW or IPGWI applications. Perform the Removing an IPSG Association procedure to remove a M3UA association that is assigned to a card running the IPSG application.

The dlt-assoc command uses one parameter, aname, the name of the association being removed from the database. The association being removed must be in the database.

The open parameter must be set to no before the association can be removed. Use the chg-assoc command to change the value of the open parameter.

The association being removed from the database cannot be assigned to an application server. This can be verified with the rtrv-as command. If the association is assigned to any application servers, go to the Removing an Association from an Application Server procedure and remove the association from the application servers.

Canceling the RTRV-ASSOC and RTRV-AS Commands

Because the rtrv-assoc and rtrv-as commands used in this procedure can output information for a long period of time, the rtrv-assoc and rtrv-as commands can be canceled and the output to the terminal stopped. There are three ways that the rtrv-assoc and rtrv-as commands can be canceled.

Press the F9 function key on the keyboard at the terminal where the rtrv-assoc or rtrv-as commands were entered.
Enter the canc-cmd without the trm parameter at the terminal where the rtrv-assoc or rtrv-as commands were entered.
Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-assoc or rtrv-as commands were entered, from another terminal other that the terminal where the rtrv-assoc or rtrv-as commands were entered. To enter the canc-cmd:trm=<xx> command, the terminal must allow Security Administration commands to be entered from it and the user must be allowed to enter Security Administration commands. The terminal’s permissions can be verified with the rtrv-secu-trm command. The user’s permissions can be verified with the rtrv-user or rtrv-secu-user commands.

For more information about the canc-cmd command, go to Commands User's Guide.

Display the 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          1203 A     A1   M2PA    2048  1030  NO   NO

If the association that is being removed in this procedure is an SUA association, continue the procedure with 3.

If the association that is being removed in this procedure is an M3UA association, continue the procedure with 2.

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

This is an example of possible output.
```
rlghncxa03w 08-03-06 15:17:20 EST EAGLE5 38.0.0
CARD   TYPE      APPL     LSET NAME   LINK SLC LSET NAME   LINK SLC
1201   DCM       SS7IPGW  lsn1        A    0
```
If the application assigned to the card is SS7IPGW or IPGWI, shown in the APPL column, continue the procedure with 3.

If the application assigned to the card is IPSG, perform the Removing an IPSG Association procedure.
Display the application servers referencing the association being removed from the database using the rtrv-as command with the name of the association being removed in this procedure.
For this example, enter this command.
rtrv-as:aname=swbel32

This is an example of possible output.
```
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

AS Name           Mode        Tr ms   Association Names
as1               LOADSHARE   2000    swbel32
as2               OVERRIDE    10      swbel32
AS Table is (2 of 250) 1% full
```
If the association is assigned to any application servers, go to the Removing an Association from an Application Server procedure and remove the association from the application servers.
Change the value of the open parameter to no by specifying the chg-assoc command with the open=no parameter.
Note:
If the value of theopen parameter for the association being removed from the database (shown in1) isno, continue this procedure with5.

For this example, enter this command.

chg-assoc:aname=swbel32:open=no

When this command has successfully completed, this message should appear.
```
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
CHG-ASSOC: MASP A - COMPLTD;
```
Remove the association from the database using the dlt-assoc command.
For this example, enter this command.

dlt-assoc:aname=swbel32

When this command has successfully completed, this message should appear.
```
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0
DLT-ASSOC:  MASP A - COMPLTD
```
Verify the changes using the rtrv-assoc command with the name of the association specified in 5.
For this example, enter this command.
rtrv-assoc:aname=swbel32

This is an example of possible output.
```
rlghncxa03w 06-10-28 09:12:36 GMT EAGLE5 36.0.0

No matching entries found

IP Appl Sock table is (3 of 4000) 1% full
```

Back up the new changes, using the chg-db:action=backup:dest=fixed command. These messages should appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first.


BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Figure 4-31 Removing a M3UA or SUA Association