Configuring an IPGWx Linkset
This procedure is used to configure IPGWx linksets in the EAGLE using the ent-ls
or chg-ls
commands with these parameters. An IPGWx linkset is a linkset that contains signaling links running either the SS7IPGW or IPGWI applications.
Note:
This procedure is not used to configure a mate IPGWx linkset, with thematelsn
and action
parameters. To configure a mate IPGWx linkset, perform procedure.
:lsn
– The name of the linkset. The linkset name can contain up to 10 characters, with the first character being a letter. However, the SEAS interface supports only eight characters. If this linkset is displayed on the SEAS interface and the linkset name contains more than eight characters, only the first eight characters in the linkset name are shown. If this linkset name contains more than eight characters, and is specified with the linkset commands on the SEAS interface, only the first eight characters can be specified.
:apc/apca/apci/apcn/apcn24
– Adjacent point code – the point code identifying the node that is next to the EAGLE. The adjacent point code can be one of the following types of point codes:
:apc
/apca
– ANSI point code, ANSI private point code
:apci
– ITU-I point code, ITU-I spare point code, ITU-I private point code, ITU-I private spare point code.
:apcn
– 14-bit ITU-N point code, 14-bit ITU-N spare point code, 14-bit ITU-N private point code, 14-bit ITU-N private spare point code.
:apcn24
– 24-bit ITU-N point code, 24-bit ITU-N private point code.
Note:
See the “Point Code Formats” section in Database Administration - SS7 User's Guide for a definition of the point code types that are used on the EAGLE and for a definition of the different formats that can be used for ITU national point codes.Note:
Theapc/apca/apci/apcn/apcn24
parameter must be specified with the ent-ls
command. Specifying this parameter with the chg-ls
command is required only if the adjacent point code of the linkset is being changed.
:lst
– The linkset type of the specified linkset - The lst
parameter must be specified with the ent-ls
command. Specifying this parameter with the chg-ls
command is required only if the linkset type of the linkset is being changed.
:ipgwapc
– IP Gateway Adjacent Point Code indicator. Specify the ipgwapc=yes
parameter to provide SS7 linkset definition compatibility for gateway connections to IP-SCPs. This parameter can be specified only for, and must be specified for, linksets containing signaling links assigned to either the SS7IPGW or IPGWI applications. The default is ipgwapc=no
.
Note:
Theipgwapc
parameter can be specified only with the ent-ls
command.
To provision ISUP-CIC routing keys, the ipgwapc=yes
parameter and the IP Gateway ISUP routing feature must be turned on. Verify this with the rtrv-feat
command. If the IP Gateway ISUP routing feature is turned on, the ipisup
field should be set to on
. If the IP Gateway ISUP routing feature is not turned on, enter the chg-feat:ipisup=on
command.
Note:
Once the IP Gateway ISUP routing feature is turned on with thechg-feat
command, it cannot be turned off.
Note:
The IP Gateway ISUP routing feature must be purchased before you turn the feature on with thechg-feat
command. If you are not sure if you have purchased the IP Gateway ISUP routing feature, contact your Oracle Sales Representative or Account Representative.
:iptps
– The quantity of IP TPS (transactions per second) that is assigned to the IPGWx linkset, from 100 to 32,000. The total amount of the IP TPS for all IPGWx linksets cannot exceed the total provisioned system TPS value in the rtrv-tps
output..
:lsusealm
– The linkset’s IPTPS alarm threshold, from 10 to 100 percent of the linkset’s IPTPS. When this threshold is reached, a major alarm (UAM 0115) is generated. When the linkset’s IPTPS falls below this threshold, UAM 0115 is automatically cleared and UAM 0118 is generated.
:slkusealm
– The signaling link IPTPS alarm threshold, from 10 to 100 percent of the signaling link’s fair share of the linkset’s IPTPS or from 10 to 100 percent of the IPGWx card’s capacity (4000 TPS). This threshold is reached when the signaling link’s actual usage exceeds the percentage of the signaling link’s fair share of the linkset’s IPTPS or the percentage of the IPGWx card’s capacity.
A signaling link's fair share of linkset’s IPTPS is the linkset’s IPTPS divided by the number of in-service links in the linkset. For example, if the linkset IPTPS is 4000 and there are 4 signaling links in the linkset, all in-service, then the signaling link's fair-share would be 1000 IPTPS (4000/4=1000). Table 4-2 shows this calculation for a linkset with 1, 2, 3 and 4 in-service signaling links.
Table 4-2 Signaling Link Fair Share Example
Number of In-Service Signaling Links | Linkset IPTPS | Signaling Link Fair Share of the Linkset IPTPS |
---|---|---|
4 |
4000 |
1000 |
3 |
4000 |
1333 |
2 |
4000 |
2000 |
1 |
4000 |
4000 |
When this threshold is exceeded, a minor alarm (UAM 0116) is generated. When the amount of traffic on the signaling link falls below this threshold, UAM 0116 is automatically cleared and UAM 0119 is generated.
The signaling link IPTPS alarm shows that the linkset IPTPS is set too low for the linkset or that the IPGWx card's capacity has been exceeded. Setting the signaling link IPTPS alarm threshold lower than the linkset IPTPS alarm threshold can give the user an earlier indication that the linkset IPTPS is inadequate or that traffic is not balanced across the links in the linkset.
:multgc
– specifies whether multiple group codes (for 14-bit ITU-N point codes) are supported for the linkset. When this parameter value is yes
, secondary adjacent point codes whose group codes are different from the adjacent point code of the linkset can be assigned to the linkset. If the parameter value is no
, the group code of the secondary adjacent point code must be the same as the group code of the linkset’s adjacent point code. For more information on secondary adjacent point codes, go to the “Configuring an ITU Linkset with a Secondary Adjacent Point Code (SAPC)” procedure in the Database Administration - SS7 User's Guide.
This parameter only applies to linksets whose adjacent point codes are either ITU international point codes or ITU national point codes. All the signaling links in this linkset must be assigned to cards running the IPGWI application. For more information on assigning signaling links to cards running the IPGWI application, go to the Adding an IPGWx Signaling Link procedure.
The ITU duplicate point code feature must be on before this parameter can be specified. Verify this with the rtrv-feat
command. If the ITU duplicate point code feature is turned on, the ituduppc
field should be set to on
. If the ITU duplicate point code feature is not turned on, enter the chg-feat:ituduppc=on
command.
Note:
Once the ITU duplicate point code feature is turned on with thechg-feat
command, it cannot be turned off.
The ITU duplicate point code feature must be purchased before you turn the feature on with the chg-feat
command. If you are not sure if you have purchased the ITU duplicate point code feature, contact your Oracle Sales Representative or Account Representative.
Adding the IPGWx linkset cannot exceed the maximum total provisioned system TPS shown in the rtrv-tps
output. An IPGWx linkset uses 4000 TPS.
- The IP TPS values of some IPGWx linksets have to be changed.
- The MAXSLKTPS values of some IPSG linksets (and the RSVDSLKTPS values if necessary) have to be changed.
- Some ATM high-speed signaling links have to be removed.
- An IPLIMx card that contains signaling links has to be removed.
The adjacent point code (APC) for the linkset must be defined in the database, must be in the SS7 domain and cannot match the point code or capability point code of the EAGLE. The domain of the point code is shown in the DMN
field in the output of the rtrv-dstn
command. The point code of the EAGLE is shown in the PCA
, PCN
, PCN24
, or PCI
fields and the capability point code of the EAGLE are shown in the CPCA
, CPCN
, CPCN24
, or CPCI
fields in the output of the rtrv-sid
command. An ANSI adjacent point code must be a full point code and cannot be a cluster point code or a network routing point code. The adjacent point code of the linkset cannot be a proxy point code, cannot have a proxy point code assigned to it, and cannot be assigned to another linkset.
If the APC is not in the destination point code table, go to the “Adding a Destination Point Code” procedure in Database Administration - SS7 User's Guide and add the APC to the destination point code table.
For IPGWx linksets, more than one device may be attached to the LAN and have IP connections to the IP card running either the SS7IPGW or IPGWI application. Thus each IPGWx linkset is adjacent to all devices on the LAN (or adjacent to no device on the LAN, depending on your point of view). To provide a scheme allowing this point-to-multipoint connection and maintain consistent SS7 linkset definition rules, a virtual APC is required. This virtual APC is a real SS7 point code that is not used anywhere else in the SS7 network. Virtual APCs assigned to SS7IPGW linksets are ANSI point codes. Virtual APCs assigned to IPGWI linksets are either ITU-I or ITU-N point codes (either 14-bit or 24-bit ITU-N point codes). Virtual point codes can be reused on more than one switch. For example, a mated set of switches, each with two related links, could share two virtual point codes instead of requiring four. DPCs and linksets related to the virtual APC must be defined with the ipgwapc
parameter set to yes
.
For provisioning of ISUP-CIC routing keys, the ipgwapc=yes
parameter and the IP Gateway ISUP routing feature must be turned on. Verify this with the rtrv-feat
command. If the IP Gateway ISUP routing feature is turned on, the ipisup
field should be set to on
. If the IP Gateway ISUP routing feature is not turned on, enter the chg-feat:ipisup=on
command.
Note:
Once the IP Gateway ISUP routing feature is turned on with thechg-feat
command, it cannot be turned off.
The IP Gateway ISUP routing feature must be purchased before you turn the feature on with the chg-feat
command. If you are not sure if you have purchased the IP Gateway ISUP routing feature, contact your Oracle Sales Representative or Account Representative.
Other Optional Parameters
- These procedures in this manual:
- These procedures in Database Administration - SS7 User's Guide
- Adding an SS7 Linkset
- Changing an SS7 Linkset
- Configuring an ITU Linkset with a Secondary Adjacent Point Code (SAPC)
- The "Configuring a Linkset for the GSM MAP Screening Feature" procedure in Database Administration - Features User's Guide.
Note:
Themtprse
, spc/spca/spci/spcn/spcn24
, and ppc/ppca/ppci/ppcn/ppcn24
parameters cannot be specified for an IPGWx linkset.
Canceling the RTRV-LS
and RTRV-DSTN
Commands
Because the rtrv-ls
and rtrv-dstn
commands used in this procedure can output information for a long period of time, the rtrv-ls
and rtrv-dstn
commands can be canceled and the output to the terminal stopped. There are three ways that the rtrv-ls
and rtrv-dstn
commands can be canceled.
- Press the
F9
function key on the keyboard at the terminal where thertrv-ls
orrtrv-dstn
commands were entered. - Enter the
canc-cmd
without thetrm
parameter at the terminal where thertrv-ls
orrtrv-dstn
commands were entered. - Enter the
canc-cmd:trm=<xx>
, where<xx>
is the terminal where thertrv-ls
orrtrv-dstn
commands were entered, from another terminal other that the terminal where thertrv-ls
orrtrv-dstn
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-4 Configuring an IPGWx Linkset
Sheet 1 of 7
Sheet 2 of 7
Sheet 3 of 7
Sheet 4 of 7
Sheet 5 of 7
Sheet 6 of 7
Sheet 7 of 7