Changing the Host Values of a M3UA or SUA Association
This procedure is used to change the host values of a M3UA or SUA association, assigned to cards that are running the SS7IPGW or IPGWI applications, using the chg-assoc
command. If you wish to change the attributes of M3UA associations assigned to cards that are running the IPSG application, perform the Changing the Host Values of an IPSG 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.
: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.
:link
– The signaling link on the IPGWx card. The value for the link
parameter for M3UA or SUA associations is A.
Note:
Theport
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, either m3ua
or sua
. The adapter
parameter is optional. The default value for the adapter
parameter in this procedure is m3ua
.
:alhost
– The alternate local host name, shown in the rtrv-ip-host
output.
: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.
:uaps
– The UA parameter set value being assigned to either an M3UA or SUA association.
At least one optional parameter is required.
The command input is limited to 150 characters, including the hostnames.
The maximum number SCTP association to application server assignments that can be hosted by an IPGWx card (referenced by the lhost
parameter of the association) is 50. For example, the IPGWx card currently contains 38 SCTP association to application server assignments. The SCTP association to application server assignments could be one SCTP association assigned to 38 application servers, two SCTP associations assigned to 19 application servers, or any combination of SCTP associations assigned to application servers that add up to 38. The SCTP association to application server assignments can be verified with the rtrv-assoc:lhost=<local host name>
and rtrv-as:aname=<association name>
commands.
Table 4-17 Examples of IPGWx Card Provisioning Limits
Number of Associations hosted by the IPGWx card | Number of Application Servers each Association is Assigned to * | Total Association - Application Server Assignments maintained by the IPGWx card |
---|---|---|
1 |
50 |
50 |
50 |
1 |
50 |
25 |
1 |
50 |
25 |
2 |
50 |
0 |
0 |
50 |
38 |
1 |
38 |
19 |
2 |
38 |
* The EAGLE can contain a maximum of 250 application servers. |
The EAGLE can contain a maximum of 4000 connections.
The B Ethernet interface of the IP card can be used on the E5-ENET cards.
If the card’s application is either SS7IPGW or IPGWI, the signaling link being assigned to the association must be in service. This state is shown in the rept-stat-slk
output with the entries IS-NR
in the PST
field and Avail
in the SST
field.
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.
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
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 thertrv-assoc
orrtrv-as
commands were entered. - Enter the
canc-cmd
without thetrm
parameter at the terminal where thertrv-assoc
orrtrv-as
commands were entered. - Enter the
canc-cmd:trm=<xx>
, where<xx>
is the terminal where thertrv-assoc
orrtrv-as
commands were entered, from another terminal other that the terminal where thertrv-assoc
orrtrv-as
commands were entered. To enter thecanc-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 thertrv-secu-trm
command. The user’s permissions can be verified with thertrv-user
orrtrv-secu-user
commands.
For more information about the canc-cmd
command, go to Commands User's Guide.
Figure 4-38 Changing the Host Values of a M3UA or SUA 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