6 IPSG M2PA and M3UA Configuration Procedures
Chapter 6, IPSG M2PA and M3UA Configuration Procedures, describes the procedures necessary to configure the components necessary to establish IP connections using M2PA or M3UA associations on IPSG signaling links.
6.1 Adding IPSG Components
This section describes how to configure the components necessary to establish connections using IPSG M2PA associations on IPSG signaling links, and IPSG M3UA associations on IPSG signaling links.
The configuration of these connections consists of these items.
- Configure the IPSG card with the Adding an IPSG Card procedure.
- Configure the required destination point codes - see Chapter 2, “Configuring Destination Tables,” in Database Administration - SS7 User's Guide.
- Configure the required IPSG linksets - perform the Adding an IPSG M2PA Linkset or the Adding an IPSG M3UA Linkset procedures.
- IP addresses must be assigned to the IPSG card configured in step 1 by performing the Configuring an IP Link procedure. There are other IP link parameters that are assigned to the IPSG card when the IPSG card is configured. Default values are assigned to these parameters when the IPSG card is configured. These values can be displayed by the
rtrv-ip-lnkcommand. These values can be changed by performing the Configuring an IP Link procedure. - Local IP hosts, assigned to the IP addresses assigned to step 4, must be configured in the database by performing the Adding an IP Host procedure. Verify the hosts with the
rtrv-ip-hostcommand. This establishes a relationship between the IPSG card related information and the association related information. - When the IPSG cards are added to the database in step 1, there are IP parameters that control the IP stack that are assigned default values. These parameter values can be displayed by the
rtrv-ip-cardcommand. These values can be changed by performing the Configuring an IP Card procedure. - Static IP routes provide more flexibility in selecting the path to the remote destination and reduces the dependence on default routers. Static IP routes are provisioned by performing the Adding an IP Route procedure.
- IPSG Associations specify a connection between a local host/TCP port and a remote host/TCP port. Two types of IPSG associations can be provisioned: M2PA and M3UA. Associations that are assigned to IPSG M2PA signaling links must be IPSG M2PA associations. Associations that are assigned to IPSG M3UA signaling links must be IPSG M3UA associations. The IPSG M2PA association is configured by performing the Adding an IPSG M2PA Association procedure. The IPSG M3UA association is configured by performing the Adding an IPSG M3UA Association procedure. Associations can be assigned to IPLIMx or IPGWx signaling links also. These associations are configured by performing the Adding an M2PA Association or Adding an M3UA or SUA Associationprocedures. A number of fields in the association cannot be configured with the Adding an IPSG M2PA Association or Adding an IPSG M3UA Association procedures and are set to default values. The values of these fields can be displayed using the
rtrv-assoccommand after the Adding an IPSG M2PA Association or Adding an IPSG M3UA Association procedures are performed. These values can be changed by performing the Changing the Attributes of an IPSG Association procedure. - There are two versions of IPSG M2PA associations, RFC and Draft 6, that can be configured in the database. When an IPSG M2PA association is added to the database with the Adding an IPSG M2PA Association procedure, the association is configured as an RFCM2PA association. The RFC version of M2PA timer set 1 is also assigned to the association when the IPSG M2PA association is added to the database.
There are two different versions, RFC and Draft 6, of M2PA timer sets that can be assigned to IPSG M2PA associations. Each version of the M2PA timer sets contains 20 timer sets. The values of these timer sets can be changed with the Changing an M2PA Timer Set procedure.
The version of the IPSG M2PA association and the M2PA timer set assigned to the association can be changed with Changing the Attributes of an IPSG Association procedure. 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 IPSG 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 IPSG 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.
- When an IPSG M3UA association is added to the database, UA parameter set 10 is assigned to the association. There are 10 UA parameter sets that can be assigned to an association, but the UA parameter set assignment can be changed, using the Changing the Attributes of an IPSG Association procedure. The values assigned to each UA parameter set can be changed, except for UA parameter set 10, using the Changing a UA Parameter Set procedure.
- Configure the IPSG signaling links with either the Adding an IPSG M2PA Linkset or Adding an IPSG M3UA Signaling Link procedures. If the addition of these signaling links will exceed the current number of signaling links the EAGLE is allowed to have, the Enabling the Large System # Links Controlled Feature procedure will have to be performed to increase the quantity of signaling links.
- Configure the required routes - see Chapter 3, “SS7 Configuration,” in Database Administration - SS7 User's Guide.
- An internal point code can be provisioned to provide routing to an IP end office node. Configure the internal point codes by performing the Adding an End Node Internal Point Codeprocedure.
- The network appearance field identifies the SS7 network context for the message, for the purpose of logically separating the signaling traffic between the SGP (signaling gateway process) and the application server over a common SCTP (stream control transmission protocol) association. This field is contained in the DATA, DUNA, DAVA, DRST, DAUD, SCON, and DUPU messages. Network appearances are configured by performing the Adding a Network Appearance procedure.
- The EAGLE processes messages with a service information field (SIF) that is 272 bytes or smaller. The Large MSU Support for IP Signaling feature allows the EAGLE to process messages with a service indicator value of 6 to 15 and with a SIF that is larger than 272 bytes. Perform the Activating the Large MSU Support for IP Signaling Feature procedure to enable and turn on the Large MSU Support for IP Signaling feature.
6.2 Adding an IPSG Card
This procedure is used to add an
IPSG card to the
database using the
ent-card command. An IPSG card is an
E5-ENET-B or SLIC card that is running the IPSG application.
The
ent-card command uses these
parameters.
:loc – The location of
the card being added to the database.
:type – The type of
card being added to the database. For this procedure, the value of this
parameter is
enet for an E5-ENET card and
enetb for E5-ENET-B.
When provisioning the SLIC, the card type is
slic.
:appl – The application
software that is assigned to the card. For this procedure, the value of this
parameter is
ipsg.
:force – If the global
title translation feature is on, the
force=yes parameter allows the
IPSG card to be added to
the database even if the current
SCCP
transactions-per-second threshold is unable to support the additional
SCCP
transaction-per-second capacity created by adding the
IP card. This parameter
is obsolete and is no longer used.
Card Slot Selection
The E5-ENET card can be inserted into any card slot, except for card slots that must remain empty to accommodate dual-slot cards, slots 09 and 10 in each shelf, and slots 1113 through 1118.
To provision a E5-ENET card, the shelf containing the
E5-ENET card must have HIPR2 cards installed in slots 9 and 10 in that shelf.
If HIPR2 cards are not installed in the shelf that the E5-ENET card will
occupy, the E5-ENET card will be auto-inhibited when the E5-ENET card is
inserted into the shelf. Enter the
rept-stat-gpl:gpl=hipr2 command to
verify whether or not
HIPR2 cards are installed in the same shelf
as the E5-ENET card being provisioned in this procedure.
Figure 6-1 Adding an IPSG Card
6.3 Adding an IPSG M2PA Linkset
This procedure is used to configure IPSG M2PA linksets in the EAGLE using the ent-ls commands with these parameters.
: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.:lst – The linkset type of the specified linkset, a, b, c, d, e. The linkset type prx can also be specified for an IPSG M2PA linkset. For more information on using the prx linkset type, refer to the "Adding an SS7 Linkset" procedure in Database Administration - SS7 User's Guide.
:ipsg – This parameter specifies whether or not the linkset is an IPSG linkset. This parameter has two values, yes (if the linkset is an IPSG linkset) or no (if the linkset is not an IPSG linkset). For this procedure, the ipsg parameter value must be yes.
:maxslktps – The maximum number of transactions per second (TPS) for all signaling links that are assigned to the IPSG M2PA linkset. See Maximum Card Capacity for Different Card Types for MaxTPS values.
:rsvdslktps – The number of transactions per second (TPS) that is assigned to each IPSG signaling link that will be in the linkset. See Maximum Card Capacity for Different Card Types for MaxTPS values. The slktps parameter can be used in place of the rsvdslktps parameter.
:tpsalmtype – The TPS threshold that will generate alarms. This parameter has two values.
rsvdslktps- TheRSVDSLKTPSthreshold generates alarms.maxslktps- TheMAXSLKTPSthreshold generates alarms.
:lsusealm – The linkset’s TPS 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 TPS alarm threshold, from 10 to 100 percent of the signaling link’s fair share of the linkset’s TPS from 10 to 100 percent of the IPSG card’s capacity See Maximum Card Capacity for Different Card Types for MaxTPS values. 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 TPS or the percentage of the IPGWx card’s capacity.
A signaling link's fair share of linkset’s TPS is the linkset’s TPS divided by the number of in-service links in the linkset. For example, if the linkset TPS is 4000 and there are 4 signaling links in the linkset, all in-service, then the signaling link's fair-share would be 1000 TPS (4000/4=1000). Table 6-1 shows this calculation for a linkset with 1, 2, 3 and 4 in-service signaling links.
Table 6-1 Signaling Link Fair Share Example
| Number of In-Service Signaling Links | Linkset TPS | Signaling Link Fair Share of the Linkset TPS |
|---|---|---|
|
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 TPS alarm shows that the linkset TPS is set too low for the linkset or that the IPSG card's capacity has been exceeded. Setting the signaling link TPS alarm threshold lower than the linkset TPS alarm threshold can give the user an earlier indication that the linkset TPS is inadequate or that traffic is not balanced across the links in the linkset.
:adapter - This parameter specifies the adapter layer for the signaling links that will be assigned to the IPSG M2PA linkset. This parameter has two values, m2pa and m3ua. For an IPSG M2PA linkset, the adapter parameter value must be m2pa.
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.
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.
Adding the IPSG M2PA linkset cannot exceed the maximum total provisioned system TPS shown in the rtrv-tps output. An IPSG M2PA linkset uses from 100 to MaxTPS (see Maximum Card Capacity for Different Card Types for MaxTPS values, as provisioned by the maxslktps parameter.
- 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.
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.
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
F9function key on the keyboard at the terminal where thertrv-lsorrtrv-dstncommands were entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-lsorrtrv-dstncommands were entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-lsorrtrv-dstncommands were entered, from another terminal other that the terminal where thertrv-lsorrtrv-dstncommands 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-2 Adding an IPSG M2PA Linkset
6.4 Adding an IPSG M3UA Linkset
This procedure is used to configure IPSG M3UA linksets in the EAGLE using the ent-ls command with these parameters.
: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.:lst – The linkset type of the linkset. For an IPSG M3UA linkset, only one value can be specified, A.
:ipsg – This parameter specifies whether or not the linkset is an IPSG linkset. This parameter has two values, yes (if the linkset is an IPSG linkset) or no (if the linkset is not an IPSG linkset). For this procedure, the ipsg parameter value must be yes.
:maxslktps – The maximum number of transactions per second (TPS) for all signaling links that are assigned to the IPSG M3UA linkset. See Maximum Card Capacity for Different Card Types for MaxTPS values.
:rsvdslktps – The number of transactions per second (TPS) that is assigned to each IPSG signaling link that will be in the linkset. See Maximum Card Capacity for Different Card Types for MaxTPS values. The slktps parameter can be used in place of the rsvdslktps parameter.
:tpsalmtype – The TPS threshold that will generate alarms. This parameter has two values.
rsvdslktps- TheRSVDSLKTPSthreshold generates alarms.maxslktps- TheMAXSLKTPSthreshold generates alarms.
:lsusealm – The linkset’s TPS alarm threshold, from 10 to 100 percent of the linkset’s TPS. When this threshold is reached, a major alarm (UAM 0115) is generated. When the linkset’s TPS falls below this threshold, UAM 0115 is automatically cleared and UAM 0118 is generated.
:slkusealm – The signaling link TPS alarm threshold, from 10 to 100 percent of the signaling link’s fair share of the linkset’s TPS from 10 to 100 percent of the IPSG card’s capacity (5000 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 TPS or the percentage of the IPSG card’s capacity.
A signaling link's fair share of linkset’s TPS is the linkset’s TPS divided by the number of in-service links in the linkset. For example, if the linkset TPS is 4000 and there are 4 signaling links in the linkset, all in-service, then the signaling link's fair-share would be 1000 TPS (4000/4=1000). Table 6-2 shows this calculation for a linkset with 1, 2, 3 and 4 in-service signaling links.
Table 6-2 Signaling Link Fair Share Example
| Number of In-Service Signaling Links | Linkset TPS | Signaling Link Fair Share of the Linkset TPS |
|---|---|---|
|
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 TPS alarm shows that the linkset TPS is set too low for the linkset or that the IPSG card's capacity has been exceeded. Setting the signaling link TPS alarm threshold lower than the linkset TPS alarm threshold can give the user an earlier indication that the linkset TPS is inadequate or that traffic is not balanced across the links in the linkset.
:adapter - This parameter specifies the adapter layer for the signaling links that will be assigned to the IPSG M3UA linkset. This parameter has two values, m2pa and m3ua. For an IPSG M3UA linkset, the adapter parameter value must be m3ua.
:rcontext - This parameter specifies the routing context value that is assigned to the IPSG M3UA linkset. The value for this parameter is from 0 to 4294967295. The default value for this parameter is none, no value is specified.
:asnotif - This parameter specifies whether or not AS notifications will be sent for the IPSG M3UA linkset. This parameter has two values, yes, AS notifications will be sent for the linkset, and no, AS notifications will not be sent for the linkset. The default value for this parameter is yes.
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.
Adding the IPSG M3UA linkset cannot exceed the maximum total provisioned system TPS shown in the rtrv-tps output. An IPSG M3UA linkset uses from 100 to 5000 TPS, as provisioned by the maxslktps parameter.
- 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.
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 IPSG M3UA 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
F9function key on the keyboard at the terminal where thertrv-lsorrtrv-dstncommands were entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-lsorrtrv-dstncommands were entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-lsorrtrv-dstncommands were entered, from another terminal other that the terminal where thertrv-lsorrtrv-dstncommands 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-3 Adding an IPSG M3UA Linkset
6.5 Configuring an IP Link
This procedure is used to configure the link parameters for IP cards using the chg-ip-lnk command. These link parameters are used to configure the Ethernet hardware.
The chg-ip-lnk command uses the following parameters.
:loc – The card location of the IP card.
:port – The Ethernet interface on the IP card, A or B.
:ipaddr – IP address assigned to the Ethernet interface on the IP card. This is an IP address expressed in standard “dot notation.” IP addresses consist of the system’s network number and the machine’s unique host number.
:submask – The subnet mask of the IP interface. A subnet mask is an IP address with a restricted range of values. The bits in the mask must be a string of one’s followed by a string of zero’s. There must be at least two one’s in the mask, and the mask cannot be all one’s. See Table 6-3 to assign the correct parameter values.
:auto – Tells hardware whether to automatically detect the duplex and speed.
:duplex – This is the mode of operation of the interface.
:speed – This is the bandwidth in megabits per second of the interface.
:mactype – This is the Media Access Control Type of the interface.
:mcast – The multicast control flag. This parameter enables or disables multicast support for the interface.
The EAGLE can contain a maximum of 2048 IP links.
A zero ipaddr parameter value (0.0.0.0) indicates the IP card Ethernet interface to IP link association is disabled. The host to the original IP address must be removed before the ipaddr=0.0.0.0 can be specified.
If the defrouter parameter of the chg-ip-card command contains an IP address for the card specified in this procedure, the network portion of one of the IP addresses assigned to the card in this procedure must match the network portion of the IP address specified by the defrouter parameter of the chg-ip-card command.
The network portion of the IP address is based on the class of the IP address (shown in Table 6-3). If the IP address is a Class A IP address, the first field is the network portion of the IP address. If the IP address is a Class B IP address, the first two fields are the network portion of the IP address. If the IP address is a Class C IP address, the first three fields are the network portion of the IP address. For example, if the IP address is 193.5.207.150, a Class C IP address, the network portion of the IP address is 193.5.207.
If the auto=yes parameter is specified, then the duplex and speed parameters are not allowed.
The loc parameter value must be shown in the rtrv-ip-card output.
The IP card must be placed out of service.
If either the ipaddr or submask parameters are specified, then both parameters must be specified. If the ipaddr parameter value is zero (0.0.0.0), the submask parameter is not required.
The IP address and subnet mask values cannot be changed to an address representing a different network if:
- If the network interface specified by the
locandportparameters has a default router,dnsa, ordsnbparameter values assigned to it, as shown in thertrv-ip-cardoutput. - Any IP routes, shown in the
rtrv-ip-rteoutput, reference the IP address for the network interface specified by thelocandportparameters.
The IP link cannot be changed if open associations reference the IP link being changed.
The network portion of the IP addresses assigned to the IP links on an IP card must be unique. For example, if IP links are assigned to IP card 1103, the network portion of the IP address for Ethernet interface A (port=a) must be different from the IP address for Ethernet interface B (port=b).
The submask parameter value is based upon the ipadddr setting. See Table 6-3 for the valid input values for the submask and ipaddr parameter combinations.
Table 6-3 Valid Subnet Mask Parameter Values
| Network Class | IP Network Address Range | Valid Subnet Mask Values |
|---|---|---|
|
A |
1.0.0.0 to 127.0.0.0 |
255.0.0.0 (the default value for a class A IP address) 255.192.0.0 255.224.0.0 255.240.0.0 255.248.0.0 255.252.0.0 255.254.0.0 255.255.128.1 |
|
A+B |
128.0.0.0 to 191.255.0.0 |
255.255.0.0 (the default value for a class B IP address) 255.255.192.0 255.255.224.0 255.255.240.0 255.255.248.0 255.255.252.0 255.255.254.0 255.255.255.128 |
|
A+B+C |
192.0.0.0 to 223.255.255.0 |
255.255.255.0 (the default value for a class C IP address) 255.255.255.192 255.255.255.224 255.255.255.240 255.255.255.248 255.255.255.252 |
If a Class B IP address is specified for the ipaddr parameter of the chg-ip-lnk command, the subnet address that results from the ipaddr and submask parameter values cannot be the same as the subnet address that results from the pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values of the chg-netopts command. The pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values can be verified by entering the rtrv-netopts command. Choose ipaddr and submask parameter values for the IP link whose resulting subnet address is not be the same as the subnet address resulting from the pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values of the chg-netopts command.
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
F9function key on the keyboard at the terminal where thertrv-assoccommand was were entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-assoccommand was entered, from another terminal other that the terminal where thertrv-assoccommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-4 Configuring an IP Link
6.6 Adding an IP Host
This procedure associates hostnames with IP addresses using the ent-ip-host command.
The ent-ip-host command uses the following parameters.
:host– The host name to be associated with the IP address. This parameter identifies the logical name assigned to the device with the IP address indicated. The host name can contain up to 60 characters (using only these characters: a-z, A-Z, 0-9, -, .) and is not case sensitive. The host name must begin with a letter. Host names containing a dash (-) must be enclosed in double quotes.
:ipaddr – The IP address to be associated with the hostname. The node’s IP address. This is an IP address expressed in standard “dot notation.” IP addresses consist of the system’s network number and the machine’s unique host number.
:type – Specifies if the host resides on the IP card on the EAGLE 5 (type=local, the default value), or if the host resides on equipment that is not in the EAGLE 5 (type=remote). This parameter is optional.
The EAGLE 5 can contain a maximum of 4026 IP hosts.
The IP address for a local host must be shown in the rtrv-ip-lnk output.
The IP address for a remote host must not be shown in the rtrv-ip-lnk output.
Figure 6-5 Adding an IP Host
6.7 Configuring an IP Card
This procedure is used to change the IP stack parameters associated with an IP card in the database using the chg-ip-card command.
The chg-ip-card command uses the following parameters.
:loc – The card location of the IP card
:srchordr – Host Table Search Order
:dnsa – Domain name server A’s IP address. This is an IP address expressed in standard “dot notation.” IP addresses consist of the system’s network number and the machine’s unique host number.
:dnsb – Domain name server B’s IP address. This is an IP address expressed in standard “dot notation.” IP addresses consist of the system’s network number and the machine’s unique host number.
:domain – The domain name is used to construct a fully-qualified DNS name consisting of 120 characters or less. For example, a domain name can be tekelec.com, the hostname is john.doe. The fully-qualified DNS name would be john.doe@tekelec.com.
:defrouter – Default router IP address. This is an IP address expressed in standard “dot notation.” IP addresses consist of the system’s network number and the machine’s unique host number.
:rstdomain – Reset Domain name. The parameter is used to reset the domain to a NULL value.
:sctpcsum – The SCTP checksum algorithm that will be applied to the traffic on the IP card, either adler32 or crc32c. The sctpcsum parameter can be specified only if the SCTPCSUM value in the rtrv-sg-opts output is percard.
The chg-ip-card command contains other parameters that cannot be used in this procedure. Refer to Commands User's Guide for more information about these parameters.
The IP card must be placed out of service.
The rstdomain parameter cannot be specified if the domain parameter is specified.
There is only one default router (defrouter parameter) for each IP card. The default router is used as the primary route unless a static IP routes is defined for the destination IP address. Static IP routes are assigned using the ent-ip-rte command in the Adding an IP Route procedure.
The network portion of the IP address of the default router must match the network portion of one of the IP addresses assigned to the card.
The network portion of the IP address is based on the class of the IP address (shown in Table 6-3). If the IP address is a Class A IP address, the first field is the network portion of the IP address. If the IP address is a Class B IP address, the first two fields are the network portion of the IP address. If the IP address is a Class C IP address, the first three fields are the network portion of the IP address. For example, if the IP address is 193.5.207.150, a Class C IP address, the network portion of the IP address is 193.5.207.
The default router can be associated with only one IP address assigned to the card if the defrouter parameter is specified. For example, the dnsa value for card 1101 is 150.1.1.10. The dnsb value for card 1101 is 160.25.37.1. A default router is provisioned with the IP address 150.1.1.4. The default router is associated with the Ethernet A IP address (the dnsa parameter value), but not the Ethernet B IP address (the dnsb parameter value).
If the default router is associated with one of the IP card’s IP addresses, a second gateway router can be assigned to the other IP address on the IP card by provisioning a static IP route for the IP card using the ent-ip-rte command in the Adding an IP Route procedure. Static IP routes can provide gateway routers associated with the other IP address on the IP card. To provision the gateway router (the gtwy parameter of the ent-ip-rte command) for the other IP address assigned to the IP card, the network portion of the gateway router’s IP address must match the network portion of the other IP address assigned to the IP card.
Specifying the IP address 0.0.0.0 for the dnsa or dnsb parameters, removes the IP address for Ethernet A (dnsa) or Ethernet B (dnsb).
When an IP card is entered into the database with the ent-card command, the IP stack parameters associated with this card are initially set with these default values:
:srchordr– SRVR:dnsa– No DNSA IP address is specified:dnsb– No DNSB IP address is specified:domain– No domain name is specified:defrouter– No default router IP address is specified:rstdomain– No:sctpcsum– CRC32C
The value of any optional parameter not specified with the chg-ip-card command is not changed.
Figure 6-6 Configuring an IP Card
6.8 Adding an IP Route
This procedure is used to add an IP route to the database using the ent-ip-rte command.
The ent-ip-rte command uses these parameters.
:loc – The location of the IP card that the IP route will be assigned to.
:dest – The IP address of the remote host or network.
:submask – The subnet mask of the destination IP address.
:gtwy – The IP address of the gateway or router that will send the IP data to its final destination.
There can be a maximum of 64 IP routes assigned to an IP card.
The EAGLE can contain a maximum of 2048 IP routes.
Ethernet Interfaces A and B on the IP card specified by the loc parameter can be used.
The network portion of the IP address value of the gtwy parameter must be the same as the network portion of the IP addresses shown for either the A or B interfaces in the rtrv-ip-card output.
The value of the dest and gtwy parameters cannot be 127.x.x.x (the loopback address), 0.0.0.0, or the IP addresses of the A or B interfaces on the IP card, and cannot be assigned to another IP card.
If the dest parameter value represents a host IP address, the value for the submask parameter must be 255.255.255.255. Otherwise, the submask parameter value is identifies the network/host ID portions that must be entered when the dest parameter value represents a network address.
The submask is applied to the IP address which is being routed to see if it yields a route match. For example, if IP address 192.1.1.2 is being routed and the IP routing table contains these entries.
Table 6-4 Sample IP Routing Table
| IP address | Submask | Gateway |
|---|---|---|
|
191.1.0.0 |
255.255.0.0 |
192.168.110.250 |
|
192.0.0.0 |
255.0.0.0 |
192.168.110.251 |
IP routing occurs as follows:
-
The subnet mask of route 1 (255.255.0.0) is applied to the IP address being routed (192.1.1.2) with the resulting IP address of 192.1.0.0. IP address 192.1.0.0 does not match IP address 191.1.0.0 in the IP routing table, so the next route is chosen.
-
The subnet mask of route 2 (255.0.0.0) is applied to the IP address being routed (192.1.1.2) with the resulting IP address of 192.0.0.0 which matches the second route in the IP routing table, so this route is selected for routing this datagram.
See Table 6-5 for the valid input values for the submask and dest parameter combinations.
Table 6-5 Valid Subnet Mask Parameter Values
| Network Class | IP Network Address Range | Valid Subnet Mask Values |
|---|---|---|
|
A |
1.0.0.0 to 127.0.0.0 |
255.0.0.0 (the default value for a class A IP address) 255.192.0.0 255.224.0.0 255.240.0.0 255.248.0.0 255.252.0.0 255.254.0.0 255.255.128.1 |
|
A+B |
128.1.0.0 to 191.255.0.0 |
255.255.0.0 (the default value for a class B IP address) 255.255.192.0 255.255.224.0 255.255.240.0 255.255.248.0 255.255.252.0 255.255.254.0 255.255.255.128 |
|
A+B+C |
192.0.0.0 to 223.255.255.0 |
255.255.255.0 (the default value for a class C IP address) 255.255.255.192 255.255.255.224 255.255.255.240 255.255.255.248 255.255.255.252 |
If a Class B IP address is specified for the dest parameter of the ent-ip-rte command, the subnet address that results from the dest and submask parameter values cannot be the same as the subnet address that results from the pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values of the chg-netopts command. The pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values can be verified by entering the rtrv-netopts command. Choose dest and submask parameter values for the IP route whose resulting subnet address is not be the same as the subnet address resulting from the pvn and pvnmask, fcna and fcnamask, or fcnb and fcnbmask parameter values of the chg-netopts command.
Figure 6-7 Adding an IP Route
6.9 Adding an IPSG M2PA Association
This procedure is used to configure IPSG 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. IPSG M2PA associations are assigned to E5-ENET cards running the IPSG application (IPSG cards).
The ent-assoc command uses these parameters to add an IPSG M2PA association to the database.
: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.
: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 IPSG Association procedure.
These fields and their default values are shown in Table 6-6.
Table 6-6 IPSG M2PA Association Fields and Default Values
|
|
|
|
|
|
|
|
|
|
|
|
ver=rfc
|
bufsize=200
|
rtxthr=0
|
rhostval=relaxed
|
The link parameter cannot be specified for an IPSG M2PA association.
An IPSG 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 on this procedure by specifying the rhost parameter with the ent-assoc command. To provision an alternate remote host for an IPSG M2PA association, perform Changing the Attributes of an IPSG Association.
The size of the buffers on the IPSG cards is 3200 KB. The size of the buffers assigned to each association that is assigned to the IPSG card cannot exceed the maximum buffer size for the IPSG 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 IPSG card to exceed the maximum buffer size for that IPSG card, the ent-assoc command will be rejected. If the you wish to add the association and the maximum buffer size for the IPSG card will be exceeded, the buffer size of the other associations assigned to the IPSG card must be decreased by performing the Changing the Buffer Size of an IPSG Association procedure. The available size of the buffers on the IPSG card can be verified by entering this command.
rtrv-assoc:lhost=<local host name assigned to the association>
The alhost parameter can also be used with the rtrv-assoc command to display the available size of the buffers on the IPSG card.
The aname parameter can be used with the rtrv-assoc command to display the available size of the buffers on the IPSG 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).
A maximum of 32 IPSG M2PA associations can be assigned to an IPSG card.
The B Ethernet interface of the IPSG card can be used.
To activate the association after the association is assigned to a signaling link, the association must contain values for the lhost, lport, rhost, rport parameters.
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 IPSG 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 IPSG 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
F9function key on the keyboard at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-assoccommand was entered, from another terminal other that the terminal where thertrv-assoccommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-8 Adding an IPSG M2PA Association
6.10 Adding an IPSG M3UA Association
This procedure is used to configure IPSG M3UA associations using the ent-assoc command. The combination of a local host, local SCTP port, remote host and remote SCTP port defines an association. IPSG M3UA associations are assigned to E5-ENET cards running the IPSG application (IPSG cards).
The ent-assoc command uses these parameters to add an IPSG M3UA association to the database.
: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.
:adapter – The adapter layer for this association, m3ua. The adapter parameter is required for adding an IPSG M3UA association. The default value for the adapter parameter is m2pa.
:alhost – The alternate local host name.
The link parameter cannot be specified for an IPSG M3UA association.
The adapter=m2pa and m2patset parameters can be used only when configuring M2PA associations. Perform the Adding an M2PA Association or Adding an IPSG M2PA Association procedures to configure M2PA associations.
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 IPSG Association procedure.
These fields and their default values are shown in Table 6-7.
Table 6-7 IPSG M3UA Association Fields and Default Values
|
|
|
|
|
|
|
|
|
|
|
|
bufsize=200
|
rtxthr=0
|
rhostval=relaxed
|
An IPSG M3UA 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 on this procedure by specifying the rhost parameter with the ent-assoc command. To provision an alternate remote host for an IPSG M3UA association, perform Changing the Attributes of an IPSG Association.
The size of the buffers on the IPSG cards is 3200 KB. The size of the buffers assigned to each association that is assigned to the IPSG card cannot exceed the maximum buffer size for the IPSG 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 IPSG card to exceed the maximum buffer size for that IPSG card, the ent-assoc command will be rejected. If the you wish to add the association and the maximum buffer size for the IPSG card will be exceeded, the buffer size of the other associations assigned to the IPSG card must be decreased by performing the Changing the Buffer Size of an IPSG Association procedure. The available size of the buffers on the IPSG 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 M3UA association.
The EAGLE can contain a maximum of 4000 connections (association to application server assignments).
The B Ethernet interface of the IPSG card can be used.
To activate the association after the association is assigned to a signaling link, the association must contain values for the lhost, lport, rhost, rport parameters.
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 IPSG 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 IPSG card while the alhost parameter value represents an IP address corresponding to the other network interface of the same IPSG 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
F9function key on the keyboard at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-assoccommand was entered, from another terminal other that the terminal where thertrv-assoccommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-9 Adding an IPSG M3UA Association
6.11 Adding an IPSG M2PA Signaling Link
This procedure is used to add an IPSG M2PA signaling link to the database using the ent-slk command. An IPSG M2PA signaling link is a signaling link that is assigned to an IPSG card and that contains an IPSG linkset and IPSG association whose ADAPTER value is M2PA. The ent-slk command uses these parameters to add an IPSG M2PA signaling link.
:loc – The card location of the IPSG card that the IPSG M2PA signaling link will be assigned to. The cards specified by this parameter are E5-ENET cards running the IPSG application.
:link – The signaling link on the card specified in the loc parameter.
:lsn – The name of the linkset that will contain the signaling link.
:slc – The signaling link code. The SLC must be unique within the linkset. It must be the same at both the EAGLE location and the distant node.
:aname – The name of the IPSG M2PA association that will be assigned to the IPSG M2PA signaling link.
ent-slk command contains other optional parameters that are not used to configure an IPGWx signaling link. These parameters are discussed in more detail in Commands User's Guide or in these sections.
- These procedures in this manual:
- These procedures in Database Administration - SS7 User's Guide
- Adding an SS7 Signaling Link
- Adding an E1 Signaling Link
- Adding a T1 Signaling Link
- Adding an ATM High-Speed Signaling Link
These items must be configured in the database before an IPSG M2PA signaling link can be added:
- Shelf – perform the "Adding a Shelf" procedure in Database Administration - System Management User's Guide.
- IPSG Card – perform the Adding an IPSG Card procedure.
- Destination Point Code – perform the “Adding a Destination Point Code” procedure in Database Administration - SS7 User's Guide.
- IPSG M2PA Linkset – perform the Adding an IPSG M2PA Linkset procedure.
- IPSG M2PA Association - perform the Adding an IPSG M2PA Association procedure.
Verify that the link has been physically installed (all cable connections have been made).
To configure the EAGLE to perform circular routing detection test on the signaling links, “Configuring Circular Route Detection” procedure in Database Administration - SS7 User's Guide.
Note:
Circular route detection is not supported in ITU networks.To provision a EAGLE with more than 1200 signaling links, the EAGLE must have certain levels of hardware installed. See the EAGLE section for more information on these hardware requirements.
The EAGLE can contain a mixture of low-speed, E1, T1, ATM high-speed, and IP signaling links. The Determining the Number of High-Speed and Low-Speed Signaling Links section describes how to determine the quantities of the different types of signaling links the EAGLE can have.
RSVDSLKTPS value that is assigned to the linkset will be assigned to the signaling link. The sum of the TPS used by all the signaling links that are assigned to the IPSG card cannot exceed MaxTPS. See Maximum Card Capacity for Different Card Types for MaxTPS values. The TPS used by the IPSG card and the TPS used by each signaling link that is assigned to the IPSG card is shown by entering the rtrv-slk command with the location of the IPSG card. If the MaxTPS limit for the IPSG card will be exceeded by adding the IPSG M2PA signaling link, one of these actions must be performed.
- Another IPSG card must be used for the IPSG M2PA signaling link.
- The
RSVDSLKTPSvalues for the linksets shown in thertrv-slkoutput for the IPSG card must be reduced enough to allow the IPSG M2PA linkset to be added.
- 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.
Canceling the REPT-STAT-SLK, RTRV-LS, and RTRV-SLK Commands
Because the rept-stat-slk, rtrv-ls, and rtrv-slk commands used in this procedure can output information for a long period of time, the rept-stat-slk, rtrv-ls, and rtrv-slk commands can be canceled and the output to the terminal stopped. There are three ways that the rept-stat-slk, rtrv-ls, and rtrv-slk commands can be canceled.
- Press the
F9function key on the keyboard at the terminal where therept-stat-slk,rtrv-ls, orrtrv-slkcommands were entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where therept-stat-slk,rtrv-ls, orrtrv-slkcommands were entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where therept-stat-slk,rtrv-ls, orrtrv-slkcommands were entered, from another terminal other that the terminal where therept-stat-slk,rtrv-ls, orrtrv-slkcommands was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-10 Adding an IPSG M2PA Signaling Link
6.12 Adding an IPSG M3UA Signaling Link
This procedure is used to add an IPSG M3UA signaling link to the database using the ent-slk command. An IPSG M3UA signaling link is a signaling link that is assigned to an IPSG card and that contains an IPSG linkset and IPSG association whose ADAPTER value is M3UA. The ent-slk command uses these parameters to add an IPSG M3UA signaling link.
:loc – The card location of the IPSG card that the IPSG M3UA signaling link will be assigned to. The cards specified by this parameter are E5-ENETcards running the IPSG application.
:link – The signaling link on the card specified in the loc parameter.
:lsn – The name of the linkset that will contain the signaling link.
:slc – The signaling link code. The SLC must be unique within the linkset. It must be the same at both the EAGLE location and the distant node.
:aname – The name of the IPSG M3UA association that will be assigned to the IPSG M3UA signaling link.
ent-slk command contains other optional parameters that are not used to configure an IPGWx signaling link. These parameters are discussed in more detail in Commands User's Guide or in these sections.
- These procedures in this manual:
- These procedures in Database Administration - SS7 User's Guide
- Adding an SS7 Signaling Link
- Adding an E1 Signaling Link
- Adding a T1 Signaling Link
- Adding an ATM High-Speed Signaling Link
These items must be configured in the database before an IPSG M3UA signaling link can be added:
- Shelf – perform the "Adding a Shelf" procedure in Database Administration - System Management User's Guide.
- IPSG Card – perform the Adding an IPSG Card procedure.
- Destination Point Code – perform the “Adding a Destination Point Code” procedure in Database Administration - SS7 User's Guide.
- IPSG M3UA Linkset – perform the Adding an IPSG M3UA Linkset procedure.
- IPSG M3UA Association - perform the Adding an IPSG M3UA Association procedure.
Verify that the link has been physically installed (all cable connections have been made).
To configure the EAGLE to perform circular routing detection test on the signaling links, “Configuring Circular Route Detection” procedure in the Database Administration - SS7.
Note:
Circular route detection is not supported in ITU networks.To provision a EAGLE with more than 1200 signaling links, the EAGLE must have certain levels of hardware installed. See the Requirements for EAGLEs Containing more than 1200 Signaling Links section for more information on these hardware requirements.
The EAGLE can contain a mixture of low-speed, E1, T1, ATM high-speed, and IP signaling links. The Determining the Number of High-Speed and Low-Speed Signaling Links section describes how to determine the quantities of the different types of signaling links the EAGLE can have.
- HC-MIM
- E5-E1/T1
- E5-ATM
- E5-SM4G
- E5-ENET
- E5-based control cards
- E5-STC card for the EAGLE Integrated Monitoring Support feature
RSVDSLKTPS value that is assigned to the linkset will be assigned to the signaling link. The sum of the TPS used by all the signaling links that are assigned to the IPSG card cannot exceed the MaxTPS. See Maximum Card Capacity for Different Card Types for MaxTPS values. The TPS used by the IPSG card and the TPS used by each signaling link that is assigned to the IPSG card is shown by entering the rtrv-slk command with the location of the IPSG card. If the MaxTPS limit for the IPSG card will be exceeded by adding the IPSG M3UA signaling link, one of these actions must be performed.
- Another IPSG card must be used for the IPSG M3UA signaling link.
- The
RSVDSLKTPSvalues for the linksets shown in thertrv-slkoutput for the IPSG card must be reduced enough to allow the IPSG M3UA linkset to be added.
- 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.
Canceling the REPT-STAT-SLK, RTRV-LS, and RTRV-SLK Commands
Because the rept-stat-slk, rtrv-ls, and rtrv-slk commands used in this procedure can output information for a long period of time, the rept-stat-slk, rtrv-ls, and rtrv-slk commands can be canceled and the output to the terminal stopped. There are three ways that the rept-stat-slk, rtrv-ls, and rtrv-slk commands can be canceled.
- Press the
F9function key on the keyboard at the terminal where therept-stat-slk,rtrv-ls, orrtrv-slkcommands were entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where therept-stat-slk,rtrv-ls, orrtrv-slkcommands were entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where therept-stat-slk,rtrv-ls, orrtrv-slkcommands were entered, from another terminal other that the terminal where therept-stat-slk,rtrv-ls, orrtrv-slkcommands was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-11 Adding an IPSG M3UA Signaling Link
6.13 Adding a Network Appearance
The network appearance field identifies the SS7 network context for the message, for the purpose of logically separating the signaling traffic between the SGP (signaling gateway process) and the ASP (application server process) over a common SCTP (stream control transmission protocol) association. This field is contained in the DATA, DUNA, DAVA, DRST, DAUD, SCON, and DUPU messages.
The network appearance is provisioned in the database using the ent-na command with these parameters.
:na – the 32-bit value of the network appearance, from 0 to 4294967295.
:type – the network type of the network appearance, ansi (ANSI), itui (ITU-I), itun (14-bit ITU-N), itun24 (24-bit ITU-N), ituis (ITU-I Spare), ituns (14-bit ITU-N Spare).
:gc – the specific ITU-N group code associated with the network appearance.
The gc parameter can be specified only with the type=itun or type=ituns parameters.
The gc parameter must be specified with the type=itun or type=ituns parameters if the ITU Duplicate Point Code feature is on. If the ITU Duplicate Point Code feature is off, the gc parameter cannot be specified.
The gc parameter value must be shown in the rtrv-spc or rtrv-sid outputs.
The ituis or ituns parameters can be specified only if the ITU National and International Spare Point Code Support feature is enabled.
Figure 6-12 Adding a Network Appearance
6.14 Activating the Large MSU Support for IP Signaling Feature
This procedure is used to enable and turn on the Large MSU Support for IP Signaling feature using the feature’s part number and a feature access key.
The feature access key for the Large MSU Support for IP Signaling feature is based on the feature’s part number and the serial number of the EAGLE, making the feature access key site-specific.
The enable-ctrl-feat command enables the controlled feature by inputting the controlled feature’s access key and the controlled feature’s part number with these parameters:
Note:
As of Release 46.3, the fak parameter is no longer required. This parameter is only used for backward compatibility.:fak – The feature access key provided by Oracle. The feature access key contains 13 alphanumeric characters and is not case sensitive.
:partnum – The Oracle-issued part number of the Large MSU Support for IP Signaling feature, 893018401.
The enable-ctrl-feat command requires that the database contain a valid serial number for the EAGLE, and that this serial number is locked. This can be verified with the rtrv-serial-num command. The EAGLE is shipped with a serial number in the database, but the serial number is not locked. The serial number can be changed, if necessary, and locked once the EAGLE is on-site, by using the ent-serial-num command. The ent-serial-num command uses these parameters.
:serial – The serial number assigned to the EAGLE. The serial number is not case sensitive.
:lock – Specifies whether or not the serial number is locked. This parameter has only one value, yes, which locks the serial number. Once the serial number is locked, it cannot be changed.
Note:
To enter and lock the EAGLE’s serial number, theent-serial-num command must be entered twice, once to add the correct serial number to the database with the serial parameter, then again with the serial and the lock=yes parameters to lock the serial number. You should verify that the serial number in the database is correct before locking the serial number. The serial number can be found on a label affixed to the control shelf (shelf 1100).
This feature cannot be temporarily enabled (with the temporary feature access key).
Once this feature has been enabled, the feature must be turned on with the chg-ctrl-feat command. The chg-ctrl-feat command uses these parameters:
:partnum – The Oracle-issued part number of the Large MSU Support for IP Signaling feature, 893018401.
:status=on – used to turn the Large MSU Support for IP Signaling feature on.
Once the Large MSU Support for IP Signaling feature has been turned on, it be can be turned off. For more information about turning the Large MSU Support for IP Signaling feature off, go to the Turning Off the Large MSU Support for IP Signaling Feature procedure.
The status of the features in the EAGLE is shown with the rtrv-ctrl-feat command.
The Large MSU Support for IP Signaling feature allows the EAGLE to process messages with a service indicator value of 6 to 15 and with a service information field (SIF) that is larger than 272 bytes. The large messages are processed only on E5-ENET cards. There are certain software components that if enabled or provisioned, that will not process large messages even if the Large MSU Support for IP Signaling feature is enabled and turned on. UIMs are displayed when most of these circumstances occur. These UIMs are:
- UIM 1333 – Displayed when a large message is received on an M3UA association and the Large MSU Support for IP Signaling feature is not enabled or is enabled and turned off. The large message is discarded.
- UIM 1350 – Displayed when a M2PA IP connection receives message with an SIF greater than 272 bytes and the Large MSU Support for IP Signaling feature is not enabled or is enabled and turned off. The large message is discarded.
- UIM 1352 – Displayed when a message with an SIF greater than 272 bytes is received; the Large MSU Support for IP Signaling feature is enabled and turned on; there are routes available for the destination point code; but the selected outbound card does not support large messages.
- UIM 1353 – Displayed when a large message passes a gateway screening screenset that redirects messages for the Database Transport Access (DTA) feature. Large messages are not redirected for the DTA feature.
For more information on these UIMs, refer to Unsolicited Alarm and Information Messages Reference.
Note:
Large messages are not monitored by the EAGLE 5 Integrated Monitoring Support feature and are not sent to the IMF. A UIM is not generated.Figure 6-13 Activating the Large MSU Support for IP Signaling Feature
6.15 Removing IPSG Components
This section describes how to remove the following components from the database.
- An IPSG Card – Perform the Removing an IPSG Card procedure
- An IPSG Linkset – Perform the Removing an IPSG Linkset procedure
- An IP Host – Perform the Removing an IP Host Assigned to an IPSG Card procedure
- An IP Route – Perform the Removing an IP Route procedure
- An IPSG Association – Perform the Removing an IPSG Association procedure
- An IPSG M2PA Signaling Link – Perform the Removing an IPSG M2PA Signaling Link procedure
- An IPSG M2PA Signaling Link – Perform the Removing an IPSG M3UA Signaling Link procedure
6.16 Removing an IPSG Card
Use this procedure to remove an IPSG card, a card running the ipsg application, from the database using the dlt-card command.
The card cannot be removed if it does not exist in the database. Before removing the card from the database, the signaling links assigned to the card must be removed.
Caution:
If the IPGWx card is the last IP card in service, removing this card from the database will cause traffic to be lost.Figure 6-14 Removing an IPSG Card
6.17 Removing an IPSG Linkset
This procedure is used to remove a
IPSG linkset from the database using the
dlt-ls command. An IPSG linkset
is a linkset whose
ipsg parameter value is
yes.
The
dlt-ls command has only one
parameter,
lsn, which is the name of the
linkset to be removed from the database.
The linkset to be removed must exist in the database.
To remove a linkset, all links associated with the linkset must be removed.
The linkset to be removed cannot be referenced by a routeset.
If the Flexible Linkset Optional Based Routing feature is enabled and turned on, and the linkset is referenced by a GTT selector, the linkset cannot be removed.
A proxy linkset whose APC is assigned
to more than one proxy linkset cannot be removed if the linkset contains the
proxy point code (shown in the
PPCA/PPCI/PPCN/PPCN24 field in the
rtrv-ls:apc/apca/apci/apcn/apcn24=<APC of the
linkset> output) that is also assigned to the APC of the linkset.
The proxy point code assigned to the APC of the linkset is shown in the
rtrv-dstn:dpc/dpca/dpci/dpcn/dpcn24=<APC of
the linkset> output. The linksets that do not contain the proxy
point code that is assigned to the APC of the linkset must be removed before
the linkset containing proxy point code that is assigned to the APC of the
linkset can be removed.
Canceling the
RTRV-LS Command
Because the
rtrv-ls command used in this
procedure can output information for a long period of time, the
rtrv-ls command can be canceled
and the output to the terminal stopped. There are three ways that the
rtrv-ls command can be
canceled.
- Press the
F9function key on the keyboard at the terminal where thertrv-lscommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-lscommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-lscommand was entered, from another terminal other that the terminal where thertrv-lscommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the
canc-cmd command, go to
Commands User's Guide.
Figure 6-15 Removing an IPSG Linkset
6.18 Removing an IP Host Assigned to an IPSG Card
This procedure removes an IP host that is assigned to an IPSG card using the dlt-ip-host command.
The dlt-ip-host command uses the following parameter.
:host – Hostname. The hostname to be removed. This parameter identifies the logical name assigned to a device with an IP address.
No associations can reference the host name being removed in this procedure.
The associations referencing the host name can be removed by performing the Removing an IPSG Association procedure or the host name in these associations can be changed by performing the Changing the Host Values of an IPSG Association procedure. The host name assigned to associations is displayed in the rtrv-assoc outputs.
Figure 6-16 Removing an IP Host Assigned to an IPSG Card
6.19 Removing an IP Route
This procedure is used to remove an IP route from the database using the dlt-ip-rte command.
The dlt-ip-rte command uses these parameters.
:loc – The location of the IP card containing the IP route being removed.
:dest – The IP address of the remote host or network assigned to the IP route being removed.
:force – To remove the IP route, the IP card that the route is assigned to must be out of service, or the force=yes parameter must be specified with the dlt-ip-rte command. The force=yes parameter allows the IP route to be removed if the IP card is in service.
Caution:
Removing an IP route while the IP card is still in service can result in losing the ability to route outbound IP traffic on the IP card. This can cause both TCP and SCTP sessions on the IP card to be lost.Figure 6-17 Removing an IP Route
6.20 Removing an IPSG Association
This procedure is used to remove an IPSG association from the database using the dlt-assoc command. An IPSG association is an M2PA or M3UA association that is assigned to an IPSG card.
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 adapter value assigned to the association being removed in this procedure must be either m2pa or m3ua. The application assigned to the card that is hosting the association must be IPSG.
If the adapter value of the association is m2pa and the application assigned to the card is either IPLIM or IPLIMI (an IPLIMx card), perform the Removing an M2PA Association to remove an M2PA association assigned to an IPLIMx card.
If the adapter value of the association is m3ua and the application assigned to the card is either SS7IPGW or IPGWI (an IPGWx card), perform the Removing a M3UA or SUA Association to remove an M3UA association assigned to an IPGWx card.
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
F9function key on the keyboard at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-assoccommand was entered, from another terminal other that the terminal where thertrv-assoccommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-18 Removing an IPSG Association
6.21 Removing an IPSG M2PA Signaling Link
This procedure is used to remove an IPSG M2PA signaling link from the database using the dlt-slk command. The dlt-slk command uses these parameters.
:loc – The card location of the IPSG card that the IPSG M2PA signaling link is assigned to.
:link – The signaling link on the card specified in the loc parameter.
:force – This parameter must be used to remove the last link in a linkset without having to remove all of the routes that referenced the linkset.
The tfatcabmlq parameter (TFA/TCA Broadcast Minimum Link Quantity), assigned to linksets, shows the minimum number of links in the given linkset (or in the combined link set in which it resides) that must be available for traffic. When the number of signaling links in the specified linkset is equal to or greater than the value of the tfatcabmlq parameter, the status of the routes that use the specified linkset is set to allowed and can carry traffic. Otherwise, these routes are restricted. The value of the tfatcabmlq parameter cannot exceed the total number of signaling links contained in the linkset.
If the linkset type of the linkset that contains the signaling link that is being removed is either A, B, D, E, or PRX, the signaling link can be removed regardless of the tfatcabmlq parameter value of the linkset and regardless of the LSRESTRICT option value. When a signaling link in one of these types of linksets is removed, the tfatcabmlq parameter value of the linkset is decreased automatically.
- If the
LSRESTRICToption is off. TheLSRESTRICToption value is shown in thertrv-ss7optsoutput. - If the
LSRESTRICToption is on and the number of signaling links assigned to the linkset will be equal to or greater than the value of thetfatcabmlqparameter value of the linkset after the signaling link is removed.The
tfatcabmlqparameter value of the linkset is shown in theTFATCABMLQcolumn of thertrv-ls:lsn=<linkset name>output. Thetfatcabmlqparameter value can be a fixed value (1 to 16) or 0. If thetfatcabmlqparameter value of the linkset is a fixed value, the number of signaling links that are in the linkset after the signaling link is removed must be equal to or greater than thetfatcabmlqparameter value of the linkset.If the
tfatcabmlqparameter value is 0, the signaling link can be removed. When thetfatcabmlqparameter value is 0, the value displayed in theTFATCABMLQcolumn of thertrv-lsoutput is 1/2 of the number of signaling links contained in the linkset. If the number of signaling links in the linkset is an odd number, thetfatcabmlqparameter value is rounded up to the next whole number. As the signaling links are removed, thetfatcabmlqparameter value of the linkset is decreased automatically.
Canceling the RTRV-SLK Command
Because the rtrv-slk command used in this procedure can output information for a long period of time, the rtrv-slk command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-slk command can be canceled.
- Press the
F9function key on the keyboard at the terminal where thertrv-slkcommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-slkcommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-slkcommand was entered, from another terminal other that the terminal where thertrv-slkcommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-19 Removing an IPSG M2PA Signaling Link
6.22 Removing an IPSG M3UA Signaling Link
This procedure is used to remove an IPSG M3UA signaling link from the database using the dlt-slk command. The dlt-slk command uses these parameters.
:loc – The card location of the IPSG card that the IPSG M3UA signaling link is assigned to.
:link – The signaling link on the card specified in the loc parameter.
:force – This parameter must be used to remove the last link in a linkset without having to remove all of the routes that referenced the linkset.
NUMSLKALW, NUMSLKRSTR, or NUMSLKPROH values shown in the rtrv-ls output. The NUMSLKALW, NUMSLKRSTR, and NUMSLKPROH values are defined as follows.
NUMSLKALW- specifies the number of IS-NR (in-service normal) signaling links in the IPSG M3UA linkset required to change the state of the linkset from the Restricted or Prohibited state to the Allowed state.NUMSLKRSTR- specifies the number of signaling links in the IPSG M3UA linkset required to change the state of the linkset from the Allowed state to the Restricted state.NUMSLKPROH- specifies the number of signaling links in the IPSG M3UA linkset required to change the state of the linkset from the Allowed or Restricted state to the Prohibited state.
For more information about the NUMSLKALW, NUMSLKRSTR, and NUMSLKPROH values, refer to the Configuring IPSG M3UA Linkset Options procedure.
If the NUMSLKALW, NUMSLKRSTR, and NUMSLKPROH values are 1 or 0, then the IPSG M3UA signaling link can be removed. The value 0 is shown in the rtrv-ls output as a number with an asterisk (*), for example, 2*.
Canceling the RTRV-SLK Command
Because the rtrv-slk command used in this procedure can output information for a long period of time, the rtrv-slk command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-slk command can be canceled.
- Press the
F9function key on the keyboard at the terminal where thertrv-slkcommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-slkcommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-slkcommand was entered, from another terminal other that the terminal where thertrv-slkcommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-20 Removing an IPSG M3UA Signaling Link
6.23 Removing a Network Appearance
This procedure removes the network appearance from the database using the dlt-na command with these parameters.
:na – the 32-bit value of the network appearance, from 0 to 4294967295.
:type – the network type of the network appearance, ansi (ANSI), itui (ITU-I), itun (14-bit ITU-N), itun24 (24-bit ITU-N), ituis (ITU-I Spare), ituns (14-bit ITU-N Spare).
:gc – the specific ITU-N group code associated with the network appearance.
Specifying the gc parameter removes the specific network appearance containing the na and gc parameter values.
Specifying the type=itun or type=ituns parameter without the gc parameter removes all 14-bit ITU-N or 14-bit ITU-N spare network appearances containing the specified na parameter value.
Figure 6-21 Removing a Network Appearance
6.24 Changing IPSG Components
This section describes how to change the attributes of the following components in the database.
- Changing an IPLIMx card that contains IPLIMx M2PA signaling links to an IPSG card that contains IPSG M2PA signaling links – perform the Changing an IPLIMx Card to an IPSG Card procedure.
- IP options – perform the Configuring IP Options procedure.
- The options for an IPSG M3UA linkset – perform the Configuring IPSG M3UA Linkset Options procedure.
- An IPSG Linkset – Perform these procedures.
- An IPSG Association – Perform these procedures.
- The SCTP retransmission parameters – Perform the Configuring an IPSG Association for SCTP Retransmission Control procedure.
- The SCTP Checksum Algorithm – Perform these procedures.
- The M2PA timer set for an IPSG M2PA association – perform the Changing an M2PA Timer Set procedure.
- The UA parameter set for an IPSG M3UA association – perform the Changing a UA Parameter Set procedure.
- Turn off the Large MSU Support for IP Signaling feature – Perform the Turning Off the Large MSU Support for IP Signaling Feature procedure.
6.25 Changing an IPLIMx Card to an IPSG Card
This procedure is used to change an IPLIMx card to an IPSG card. The linksets, signaling links, and M2PA associations that are assigned to the IPLIMx card are changed to IPSG M2PA linksets, IPSG M2PA signaling links, and IPSG M2PA associations. To change an IPLIMx card to an IPSG card, the chg-card command is used with these parameters.
:loc – The card location of the IPLIMx card.
:nappl – The new application that is assigned to the card, ipsg.
The IPLIMx card must be an E5-ENET card that is running either the IPLIM or IPLIMI applications. IPLIMx signaling links must be assigned to the card. M2PA associations must be assigned to the signaling links. Before the chg-card command can be executed, the IPLIMx card and its signaling links must be taken out of service.
If adding the IPLIMx signaling link will exceed the maximum total provisioned system TPS, and the maximum total provisioned system TPS is 500,000, perform the "Activating the HIPR2 High Rate Mode" feature in Database Administration - System Management to enable and turn on the HIPR2 High Rate Mode feature. When the HIPR2 High Rate Mode feature is enabled and turned on, the maximum total provisioned system TPS is increased to 1,000,000 (1M). If the maximum total provisioned system TPS is 1M, or the maximum total provisioned system TPS is 500,000 and will not be increased, and adding the IPLIMx signaling link will exceed the maximum total provisioned system TPS, the IPLIMx signaling link cannot be added unless the amount of available TPS is reduced enough to allow the IPLIMx signaling link to be added. The available TPS can be reduced by performing one or more of these actions.
Figure 6-22 Changing IPLIMx Card to IPSG Card
6.26 Configuring IP Options
Use this procedure to change the IP options defined by these parameters: getcomm, setcomm, snmpcont, srkq, trapcomm, ipgwabate, and uameasusedftas.
chg-sg-opts command also contains the sctpcsum parameter. Perform the one of these procedures to change the sctpcsum parameter value.
:getcomm – The community name used to validate SNMP Get and GetNext requests. This value applies to each IP card SNMP agent.
:setcomm – The community name used to validate SNMP Set requests. This value applies to each IP card SNMP agent.
:snmpcont – The system contact information for each IP card SNMP agent, used to define the sysContact object in the SNMP MIB II System Group.
:srkq – The static routing key quantity used to specify the maximum number of static routing key entries in the Routing Key table of each ss7ipgw and ipgwi card.
:trapcomm – The community name used when sending SNMP traps. This value applies to each IP card SNMP agent.
:ipgwabate – enables (ipgwabate=yes) or disables (ipgwabate=no) SS7 congestion abatement procedures for IPGWx signaling links (signaling links assigned to cards running the ss7ipgw or ipgwi applications). The default value for this parameter is no.
:uameasusedftas - specifies whether UA measurements are pegged against the default application server or against the application server shown by the routing context. The values for this parameter are yes and no. The system default value for this parameter is yes.
yes- UA measurement registers are pegged against the default application server.no- UA measurements are pegged against the application server shown by the routing context.
The maximum value of the srkq parameter is 2500.
The value specified for the srkq parameter cannot be less than the current number of provisioned routing keys. The number of routing keys that are currently provisioned is shown in the rtrv-appl-rtkey or rtrv-tbl-capacity command outputs.
The values of the snmpcont, getcomm, setcomm, and trapcomm parameters are a string of up to 32 characters that is not case sensitive. If the character string contains characters other than alphanumeric characters, the character string must be enclosed in single quotes.
Figure 6-23 Configuring IP Options
6.27 Configuring IPSG M3UA Linkset Options
This procedure is used to configure the options for an
IPSG M3UA linkset with the
chg-lsopts command and these
parameters.
:lsn - The name of the
IPSG M3UA linkset.
:numslkalw - This
parameter specifies the number of
IS-NR (in-service normal) signaling links in
the IPSG M3UA linkset required to change the state of the linkset from the
Restricted or Prohibited state to the Allowed state. When the number of IS-NR
signaling links in the linkset changes from a value that is less than the
numslkalw parameter value to a value
that is equal or greater than the
numslkalw value, the state of the
linkset changes to the Allowed state. The value of this parameter is from 0 to
16. The value of this parameter cannot exceed the number of signaling links
that are assigned to the linkset. The value 0 represents half the number of
signaling links that are assigned to the linkset. If this parameter is not
specified, the current value of this parameter is not changed. The system
default value for this parameter is 1.
:numslkrstr - This
parameter specifies the number of signaling links in the IPSG M3UA linkset
required to change the state of the linkset from the Allowed state to the
Restricted state. When the number of IS-NR signaling links in the linkset
changes from a value that is equal to or greater than the
numslkrstr parameter value to a value
that is less than the
numslkrstr parameter value and greater
than the
numslkproh parameter value, the state
of the linkset changes from the Allowed state to the Restricted state. Changing
the state of the linkset from the Prohibited state to the Restricted state is
not supported. The value of this parameter is from 0 to 16. The value of this
parameter cannot exceed the number of signaling links that are assigned to the
linkset. The value 0 represents half the number of signaling links that are
assigned to the linkset. If this parameter is not specified, the current value
of this parameter is not changed. The system default value for this parameter
is 1.
:numslkproh - This
parameter specifies the number of signaling links in the IPSG M3UA linkset
required to change the state of the linkset from the Allowed or Restricted
state to the Prohibited state. When the number of IS-NR signaling links in the
linkset changes from a value that is equal to or greater than the
numslkproh parameter value to a value
that is less than the
numslkproh parameter value, the state
of the linkset changes from the Allowed or Restricted state to the Prohibited
state. The value of this parameter is from 0 to 16. The value of this parameter
cannot exceed the number of signaling links that are assigned to the linkset.
The value 0 represents half the number of signaling links that are assigned to
the linkset. If this parameter is not specified, the current value of this
parameter is not changed. The system default value for this parameter is 1.
An IPSG M3UA linkset is a linkset that contains these
values:
IPSG=yes,
ADAPTER=m3ua.
If the IPSG M3UA linkset contains no signaling links,
the value of the
numslkalw,
numslkrstr, or
numslkproh parameters can only be
changed to 0 or 1.
If 0 is specified as the value of the
numslkalw,
numslkrstr, or
numslkproh parameters, a number with
an asterisk (*) is shown as the value of the
numslkalw,
numslkrstr, or
numslkproh parameter.
Figure 6-24 Configuring IPSG M3UA Linkset Options
6.28 Changing an IPSG M2PA Linkset
This procedure is used to change an IPSG M2PA linkset, a linkset that contains the IPSG value yes and whose ADAPTER value is m2pa, in the EAGLE using the chg-ls commands with these parameters.
:lsn – The name of the linkset that will be changed, shown in the rtrv-ls output.
:ipsg – This parameter specifies whether or not the linkset is an IPSG linkset. This parameter has two values, yes (if the linkset is an IPSG linkset) or no (if the linkset is not an IPSG linkset). For this procedure, the ipsg parameter value must be yes.
:maxslktps – The maximum number of transactions per second (TPS) for all signaling links that are assigned to the IPSG M2PA linkset. See Maximum Card Capacity for Different Card Types for MaxTPS values.
:rsvdslktps – The number of transactions per second (TPS) that is assigned to each IPSG signaling link that will be in the linkset. See Maximum Card Capacity for Different Card Types for MaxTPS values. The slktps parameter can be used in place of the rsvdslktps parameter.
:tpsalmtype – The TPS threshold that will generate alarms. This parameter has two values.
rsvdslktps- TheRSVDSLKTPSthreshold generates alarms.maxslktps- TheMAXSLKTPSthreshold generates alarms.
:adapter - This parameter specifies the adapter layer for the signaling links that will be assigned to the IPSG M2PA linkset. This parameter has two values, m2pa and m3ua. For an IPSG M2PA linkset, the adapter parameter value must be m2pa.
:lsusealm – The linkset’s TPS alarm threshold, from 10 to 100 percent of the linkset’s TPS. When this threshold is reached, a major alarm (UAM 0115) is generated. When the linkset’s TPS falls below this threshold, UAM 0115 is automatically cleared and UAM 0118 is generated.
:slkusealm – The signaling link TPS alarm threshold, from 10 to 100 percent of the signaling link’s fair share of the linkset’s TPS or from 10 to 100 percent of the IPSG card’s capacity. See Maximum Card Capacity for Different Card Types for MaxTPS values. 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 TPS or the percentage of the IPSG card’s capacity.
A signaling link's fair share of linkset’s TPS is the linkset’s TPS divided by the number of in-service links in the linkset. For example, if the linkset TPS is 4000 and there are 4 signaling links in the linkset, all in-service, then the signaling link's fair-share would be 1000 TPS (4000/4=1000). Table 6-10 shows this calculation for a linkset with 1, 2, 3 and 4 in-service signaling links.
Table 6-10 Signaling Link Fair Share Example
| Number of In-Service Signaling Links | Linkset TPS | Signaling Link Fair Share of the Linkset TPS |
|---|---|---|
|
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 TPS alarm shows that the linkset TPS is set too low for the linkset or that the IPSG card's capacity has been exceeded. Setting the signaling link TPS alarm threshold lower than the linkset TPS alarm threshold can give the user an earlier indication that the linkset TPS is inadequate or that traffic is not balanced across the links in the linkset.
rtrv-tps output. If changing the IPSG M2PA linkset will exceed the maximum total provisioned system TPS, and the maximum total provisioned system TPS is 500,000, perform the "Activating the HIPR2 High Rate Mode" feature in Database Administration - System Management to enable and turn on the HIPR2 High Rate Mode feature. When the HIPR2 High Rate Mode feature is enabled and turned on, the maximum total provisioned system TPS is increased to 1,000,000 (1M). If the maximum total provisioned system TPS is 1M or the maximum total provisioned system TPS is 500,000 and will not be increased, and changing the MAXSLKTPS or RSVDSLKTPS values for the IPSG M2PA linkset will exceed the maximum total provisioned system TPS, the MAXSLKTPS or RSVDSLKTPS values for the IPSG M2PA linkset cannot be changed unless the amount of available TPS is reduced enough to allow the MAXSLKTPS or RSVDSLKTPS values for the IPSG M2PA linkset to be changed. The available TPS can be reduced by performing one or more of these actions.
- 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.
This procedure can also be used to change an IPSG M3UA linkset or a non-IPSG linkset to an IPSG M2PA linkset.
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.
Canceling the RTRV-LS Command
Because the rtrv-ls command used in this procedure can output information for a long period of time, the rtrv-ls command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-ls command can be canceled.
- Press the
F9function key on the keyboard at the terminal where thertrv-lscommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-lscommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-lscommand was entered, from another terminal other that the terminal where thertrv-lscommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-25 Changing an IPSG M2PA Linkset
6.29 Changing an IPSG M3UA Linkset
This procedure is used to change an IPSG M3UA linkset, a linkset that contains the IPSG value yes and whose ADAPTER value is m3ua, in the EAGLE using the chg-ls commands with these parameters.
:lsn – The name of the linkset that will be changed, shown in the rtrv-ls output.
:ipsg – This parameter specifies whether or not the linkset is an IPSG linkset. This parameter has two values, yes (if the linkset is an IPSG linkset) or no (if the linkset is not an IPSG linkset). For this procedure, the ipsg parameter value must be yes.
:maxslktps – The maximum number of transactions per second (TPS) for all signaling links that are assigned to the IPSG M3UA linkset. See Maximum Card Capacity for Different Card Types for MaxTPS values.
:rsvdslktps – The number of transactions per second (TPS) that is assigned to each IPSG signaling link that will be in the linkset. See Maximum Card Capacity for Different Card Types for MaxTPS values. The slktps parameter can be used in place of the rsvdslktps parameter.
:tpsalmtype – The TPS threshold that will generate alarms. This parameter has two values.
rsvdslktps- TheRSVDSLKTPSthreshold generates alarms.maxslktps- TheMAXSLKTPSthreshold generates alarms.
:adapter - This parameter specifies the adapter layer for the signaling links that will be assigned to the IPSG M3UA linkset. This parameter has two values, m2pa and m3ua. For an IPSG M3UA linkset, the adapter parameter value must be m3ua.
:rcontext - This parameter specifies the routing context value that is assigned to the IPSG M3UA linkset. The value for this parameter is from 0 to 4294967295. The default value for this parameter is none, no value is specified.
:action=delete - This parameter is used to remove an existing routing context (RCONTEXT) value from the IPSG M3UA linkset. If the rcontext value for the IPSG M3UA linkset is none, the linkset does not contain a routing context value.
:asnotif - This parameter specifies whether or not AS notifications will be sent for the IPSG M3UA linkset. This parameter has two values, yes, AS notifications will be sent for the linkset, and no, AS notifications will not be sent for the linkset. The default value for this parameter is yes.
:lsusealm – The linkset’s TPS alarm threshold, from 10 to 100 percent of the linkset’s TPS. When this threshold is reached, a major alarm (UAM 0115) is generated. When the linkset’s TPS falls below this threshold, UAM 0115 is automatically cleared and UAM 0118 is generated.
:slkusealm – The signaling link TPS alarm threshold, from 10 to 100 percent of the signaling link’s fair share of the linkset’s TPS or from 10 to 100 percent of the IPSG card’s capacity. See Maximum Card Capacity for Different Card Types for MaxTPS values. 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 TPS or the percentage of the IPSG card’s capacity.
A signaling link's fair share of linkset’s TPS is the linkset’s TPS divided by the number of in-service links in the linkset. For example, if the linkset TPS is 4000 and there are 4 signaling links in the linkset, all in-service, then the signaling link's fair-share would be 1000 TPS (4000/4=1000). Table 6-11 shows this calculation for a linkset with 1, 2, 3 and 4 in-service signaling links.
Table 6-11 Signaling Link Fair Share Example
| Number of In-Service Signaling Links | Linkset TPS | Signaling Link Fair Share of the Linkset TPS |
|---|---|---|
|
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 TPS alarm shows that the linkset TPS is set too low for the linkset or that the IPSG card's capacity has been exceeded. Setting the signaling link TPS alarm threshold lower than the linkset TPS alarm threshold can give the user an earlier indication that the linkset TPS is inadequate or that traffic is not balanced across the links in the linkset.
rtrv-tps output. If changing the IPSG M3UA linkset will exceed the maximum total provisioned system TPS, and the maximum total provisioned system TPS is 500,000, perform the "Activating the HIPR2 High Rate Mode" feature in Database Administration - System Management User's Guide to enable and turn on the HIPR2 High Rate Mode feature. When the HIPR2 High Rate Mode feature is enabled and turned on, the maximum total provisioned system TPS is increased to 1,000,000 (1M). If the maximum total provisioned system TPS is 1M or the maximum total provisioned system TPS is 500,000 and will not be increased, and changing the MAXSLKTPS or RSVDSLKTPS values for the IPSG M3UA linkset will exceed the maximum total provisioned system TPS, the MAXSLKTPS or RSVDSLKTPS values for the IPSG M3UA linkset cannot be changed unless the amount of available TPS is reduced enough to allow the MAXSLKTPS or RSVDSLKTPS values for the IPSG M3UA linkset to be changed. The available TPS can be reduced by performing one or more of these actions.
- 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.
This procedure can also be used to change an IPSG M2PA linkset or a non-IPSG linkset to an IPSG M3UA linkset.
Other Optional Parameters
- The Configuring IPSG M3UA Linkset Options procedure 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 the Database Administration - Features User's Guide.
Note:
Themtprse, spc/spca/spci/spcn/spcn24, sapci/sapcn/sapcn24, and ppc/ppca/ppci/ppcn/ppcn24 parameters cannot be specified for an IPSG M3UA linkset.
Canceling the RTRV-LS Command
Because the rtrv-ls command used in this procedure can output information for a long period of time, the rtrv-ls command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-ls command can be canceled.
- Press the
F9function key on the keyboard at the terminal where thertrv-lscommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-lscommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-lscommand was entered, from another terminal other that the terminal where thertrv-lscommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-26 Changing an IPSG M3UA Linkset
6.30 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.
lhostandalhost- 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 theadapter 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-assoccommand 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
F9function key on the keyboard at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-assoccommand was entered, from another terminal other that the terminal where thertrv-assoccommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-27 Changing the Attributes of an IPSG Association
6.31 Changing the Buffer Size of an IPSG Association
This procedure is used to change the buffer size of an IPSG association, assigned to E5-ENET cards that are running the IPSG application, IPSG cards, using the chg-assoc command.
If you wish to change the buffer size of M2PA associations assigned to cards that are running the IPLIM or IPLIMI applications, perform the Changing the Buffer Size of a M2PA Association procedure.
If you wish to change the buffer size of M3UA associations assigned to cards that are running the SS7IPGW or IPGWI applications, perform the Changing the Buffer Size of a M3UA or SUA 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.
: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.
:bufsize – The size, in kilobytes, of the buffer used by the association. The values for this parameter are 8 kilobytes to 400 kilobytes. The maximum size of the buffers on an IPSG card is 6400 KB.
The size of the buffers assigned to each association that is assigned to the IP card cannot exceed the maximum buffer size for that card. If the bufsize parameter value causes the total buffer size for all the associations on the IPSG card to exceed the maximum buffer size for that IPSG card, the chg-assoc command will be rejected. The available size of the buffers on the IPSG 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.
If you wish to increase the buffer size for this association to a value that is greater than available buffer size for the card, the buffer size of the other associations assigned to the card must be decreased.
The chg-assoc command contains other parameters that are not used in this procedure. To change these parameters, perform these procedures.
lhostandalhost- Changing the Host Values of an IPSG Association- Other attributes of the IPSG Association - Changing the Buffer Size of an IPSG Association
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
F9function key on the keyboard at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-assoccommand was entered, from another terminal other that the terminal where thertrv-assoccommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-28 Changing the Buffer Size of an IPSG Association
6.32 Changing the Host Values of an IPSG Association
This procedure is used to change the host values of an IPSG association, assigned to E5-ENET cards that are running the IPSG application, IPSG cards, using the chg-assoc command.
If you wish to change the host values of M2PA associations assigned to cards that are running the IPLIM or IPLIMI applications, perform the Changing the Host Values of a M2PA Association procedure.
If you wish to change the host values of M3UA associations assigned to cards that are running the SS7IPGW or IPGWI applications, perform the Changing the Host Values of a M3UA or SUA 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.
:alhost – The alternate local host name, shown in the rtrv-ip-host output.
:adapter – The adapter layer for this association, m2pa or m3ua.
: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.
: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.
The chg-assoc command contains other parameters that are not used in this procedure. To change these parameters, perform these procedures.
bufsize- Changing the Buffer Size of an IPSG Association- Other attributes of the IPSG association - Changing the Attributes of an IPSG Association
At least one optional parameter must be specified.
The command input is limited to 150 characters, including the hostnames.
The EAGLE can contain a maximum of 4000 connections.
A maximum of 32 associations can be assigned to an IPSG card running on an E5-ENET/E5--ENET-B card or DEIR card.
An IPSG application running on the SLIC card can contain a maximum of 128 associations.
- If the
ADAPTERvalue of the association is M2PA, perform the Removing an IPSG M2PA Signaling Link procedure. - If the
ADAPTERvalue of the association is M3UA, perform the Removing an IPSG M3UA Signaling Link procedure.
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 IPSG 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 IPSG card while the alhost parameter value represents an IPSG address corresponding to the other network interface of the same IPSG 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 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
F9function key on the keyboard at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-assoccommand was entered, from another terminal other that the terminal where thertrv-assoccommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-29 Changing the Host Values of an IPSG Association
6.33 Configuring an IPSG Association for SCTP Retransmission Control
This procedure is used to gather the information required to configure the retransmission parameters for M2PA or M3UA associations assigned to cards running the IPSG application. Perform the Configuring SCTP Retransmission Control for a M2PA Association procedure to configure the retransmission parameters for M2PA associations assigned to IPLIMx cards. Perform the Configuring SCTP Retransmission Control for a M3UA or SUA Association procedure to configure the retransmission parameters for M3UA associations assigned to IPLIMx cards. If any assistance is needed to configure the retransmission parameters for associations, contact unresolvable-reference.html#GUID-1825DD07-2A6B-4648-859A-1258A0F9AC40.
The retransmission parameters are configured using the rmode, rmin, rmax, rtimes, and cwmin parameters of the chg-assoc command.
:rmode – The retransmission mode 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 mode 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.
:rmax – The maximum value of the calculated retransmission timeout in milliseconds.
Note:
Thermin and rmax parameter values form a range of retransmission values. The value of the rmin parameter must be less than or equal to the rmax parameter value.
:rtimes – The number of times a data retransmission occurs before closing the association.
:cwmin – The minimum size in bytes of the association's congestion window and the initial size in bytes of the congestion window.
The Changing the Attributes of an IPSG Association procedure is used to change the values of these parameters. In addition to using the Changing the Attributes of an IPSG Association procedure, these pass commands are also used in this procedure.
ping– tests for the presence of hosts on the network.assocrtt– displays the SCTP round trip times for a specified association. Minimum, maximum, and average times are kept for each open association. The Retransmission Mode (RFC or LIN) and the configured Minimum and Maximum Retransmission Timeout limits are also displayed.sctp– provides a summary list of all SCTP instances.sctp -a <association name>– displays the measurements and information for a specific association.Note:
The values for the minimum and maximum retransmission times in the output from this command are shown in microseconds.
For more information on the pass commands, see Commands User's Guide.
The chg-assoc command contains other optional parameters that can be used to configure an association. These parameters are not shown here because they are not necessary for configuring the SCTP retransmission parameters. These parameters are explained in more detail in the Changing the Attributes of an IPSG Association procedure, or in the and chg-assoc command description in Commands User's Guide.
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
F9function key on the keyboard at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-assoccommand was entered, from another terminal other that the terminal where thertrv-assoccommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-30 Configuring an IPSG Association for SCTP Retransmission Control
6.34 Changing the SCTP Checksum Algorithm Option for IPSG M2PA Associations
sctpcsum parameter of the chg-sg-opts command is used to change this option. The Adler-32 and CRC-32c checksum algorithms specified in this procedure applies to all the M2PA associations that are assigned to all the IP cards running the IPSG application. This option is a system-wide option. To apply this option to associations assigned to cards running the IPLIM, IPLIMI, SS7IPGW, or IPGWI applications, or to IPSG M3UA associations, perform these procedures.
The sctpcsum parameter contains another value, percard, that allows either the Adler-32 or CRC-32c SCTP checksum algorithm to be specified for the all the associations assigned to a specific card. With this option specified, the Adler-32 checksum algorithm can be specified for the associations on one card and the CRC-32c checksum algorithm can be specified for the associations on another card. Setting the sctpcsum parameter to percard changes the SCTP checksum algorithm for the associations assigned to a card to the SCTP checksum algorithm value for that card. The checksum algorithm for individual cards is provisioned by performing the Configuring an IP Link procedure.
Once the SCTP checksum option has been changed, the associations on each IP card need to be reset by changing the open parameter value for each association to no, then back to yes. This ensures that the associations on the IP card are using the new SCTP checksum algorithm.
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
F9function key on the keyboard at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-assoccommand was entered, from another terminal other that the terminal where thertrv-assoccommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-31 Changing the SCTP Checksum Algorithm Option for IPSG M2PA Associations
6.35 Changing the SCTP Checksum Algorithm Option for IPSG M3UA Associations
sctpcsum parameter of the chg-sg-opts command is used to change this option. The Adler-32 and CRC-32c checksum algorithms specified in this procedure applies to all the M3UA associations that are assigned to all the IP cards running the IPSG application. This option is a system-wide option. To apply this option to associations assigned to cards running the IPLIM, IPLIMI, SS7IPGW, or IPGWI applications, or to IPSG M2PA associations, perform these procedures.
The sctpcsum parameter contains another value, percard, that allows either the Adler-32 or CRC-32c SCTP checksum algorithm to be specified for the all the associations assigned to a specific card. With this option specified, the Adler-32 checksum algorithm can be specified for the associations on one card and the CRC-32c checksum algorithm can be specified for the associations on another card. Setting the sctpcsum parameter to percard changes the SCTP checksum algorithm for the associations assigned to a card to the SCTP checksum algorithm value for that card. The checksum algorithm for individual cards is provisioned by performing the Configuring an IP Card procedure.
Once the SCTP checksum option has been changed, the associations on each IP card need to be reset by changing the open parameter value for each association to no, then back to yes. This ensures that the associations on the IP card are using the new SCTP checksum algorithm.
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
F9function key on the keyboard at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-assoccommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-assoccommand was entered, from another terminal other that the terminal where thertrv-assoccommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-32 Changing the SCTP Checksum Algorithm Option for IPSG M3UA Associations
6.36 Changing an M2PA Timer Set
This procedure is used to change the values of the M2PA timers in an M2PA timer set using the chg-m2pa-tset command. The M2PA timers are used to control the behavior of the signaling link assigned to an M2PA association (an association containing the M2PA adapter layer - adapter=m2pa) during signaling link alignment and proving, and during times of transmit congestion.
The EAGLE contains 20 M2PA timer sets. One of these timer sets is assigned to an M2PA association using the m2patset parameter of either the ent-assoc or chg-assoc command. If the m2patset parameter is not specified with the ent-assoc command, or with the chg-assoc command if the adapter layer for that association is being changed to M2PA, timer set 1 is automatically assigned to the association.
Caution:
Changing an M2PA timer set may affect the performance of any associations using the timer set being changed.The chg-m2pa-tset command uses these parameters.
:tset – The M2PA timer set being changed, 1 - 20.
:srctset – The timer values in an existing M2PA timer set can be copied to another M2PA timer set, specified by the tset parameter. The srctset parameter specifies the timer set that is to be copied. If the srctset parameter is specified, no other timer values can be specified, The srctset parameter value cannot be the timer set specified by the tset parameter.
:ver – The M2PA version, either Draft 6 (ver=d6) or RFC (ver=rfc).
Note:
The definitions of timers T1 and T3 for the Draft 6 version are different from the RFC version. The T2 timer applies only to the RFC version. The definitions of timers T4N, T4E, T5, T6, T7, T16, T17 and T18 for are the same for the Draft 6 version and the RFC version.The timer parameter descriptions and values are shown in Table 6-13.
Table 6-13 M2PA Timers
| Timer | Draft 6 Timer Name | RFC Timer Name | Definition | Value (in msecs) | DRAFT 6 System Default Value (in msecs) | RFC System Default Value (in msecs) |
|---|---|---|---|---|---|---|
|
|
N/A |
Ready Timer |
The amount of time after proving the M2PA adapter layer waits to receive a Link Status Ready message from the peer. |
1000 - 350000 |
N/A |
300000 |
|
|
Alignment Timer |
N/A |
The amount of time the M2PA adapter layer waits to receive a Link Status Alignment message from the peer. |
1000 - 350000 |
10000 |
N/A |
|
|
N/A |
Not Aligned Timer |
The the amount of time the M2PA adapter layer waits to receive a Link Status Alignment/Link Status Proving message after sending a Link Status Alignment message. Timer T2 is not used in M2PA Draft 6 timer sets. |
5000 - 150000 |
N/A |
20000 |
|
|
N/A |
Alignment Timer |
The amount of time the M2PA layer waits to receive a Link Status Alignment message from the peer. |
1000 - 60000 |
N/A |
2000 |
|
Ready Timer |
N/A |
The amount of time after proving the M2PA adapter layer waits to receive a Link Status Ready message from the peer. |
1000 - 60000 |
10000 |
N/A |
|
|
|
Proving Timer (Normal) |
The amount of time the M2PA adapter layer generates Link Status Proving messages during normal proving. |
1000 - 70000 |
10000 |
30000 |
|
|
|
Proving Timer (Emergency) |
The amount of time the M2PA adapter layer generates Link Status Proving messages during emergency proving. |
400 - 5000 |
500 |
500 |
|
|
|
Busy Rate Timer |
The amount of time between sending Link Status Busy messages while the link is in-service. |
80 - 10000 |
1000 |
100 |
|
|
|
Remote Congestion Timer |
The amount of time that a congested link will remain in service. |
1000 - 6000 |
3000 |
3000 |
|
|
|
Excess Delay in Acknowledgement Timer |
The maximum amount of time that may pass between when a user data message is transmitted and an acknowledgement for that message is received from the peer. If this timer expires, the link is taken out of service. |
200 - 2000 |
1200 |
1200 |
|
|
|
Proving Rate Timer |
The amount of time between sending Link Status Proving messages while the T4N or T4E timer is running. |
100 - 500000 ** |
200000 ** |
200000 ** |
|
|
|
Ready Rate Timer |
The amount of time between sending Link Status Ready messages while the T3 timer is running. |
100 - 500 |
250 |
250 |
|
|
|
Processor Outage Rate Timer |
The amount of time between sending Link Status Processor Outage messages while the link is in-service. |
100 - 10000 |
1000 |
1000 |
|
|
msecs - milliseconds * The T2 Timer can be specified only for the M2PA RFC version. ** The value of the T16 Timer is in microseconds. |
||||||
The value of any timer parameter not specified with the chg-m2pa-tset command is not changed.
Figure 6-33 Changing an M2PA Timer Set
6.37 Changing a UA Parameter Set
Use this procedure to change the values in a UA (user adapter) parameter set using the chg-uaps command. The chg-uaps command uses these parameters.
:set – the UA parameter set being changed, from 1 - 9
:scrset – the source UA parameter set used to copy the values from one UA parameter set to another, from 1 to 10.
:timer – the timer being changed, from 1 to 10. Currently, there are only three timers defined:
- Timer 2 – The False IP Connection Congestion Timer – the maximum amount of time (in milliseconds) that an association is allowed to remain congested before failing due to false connection congestion.
- Timer 3 – The UA Heartbeat Period Timer – The frequency, in milliseconds, that heartbeat messages are transmitted.
- Timer 4 – The UA Heartbeat Received Timer – The amount of time, in milliseconds, that the EAGLE waits for a response to the heartbeat message that was transmitted. If a response to the heartbeat message is not received in the amount of time defined by Timer 4, the association is torn down
:tvalue – The value of the timer specified by the timer parameter.
- The value of timer 2 is from 10 to 30,000 milliseconds. The system default value is 3,000 milliseconds.
- The value of timer 3 is from 100 to 60,000 milliseconds. The system default value is 10,000 milliseconds.
- The value of timer 4 is from 100 to 10,000 milliseconds. The system default value is 5,000 milliseconds.
:parm – the UA parameters, from 1 to 10. Currently, only four UA parameters are defined.
- 1 – Controlling ASPSNM Behavior
- 2 – Controlling ASP/Application Server State Notification Behavior
- 3 – UA Serviceability Options
- 4 – SCTP Payload Protocol Indicator Option
:pvalue – the value of the UA parameters, which is dependent on the parm parameter value. The value of the pvalue parameter is a bit-mapped value, requiring a 0 in the specific bit position to disable the item, or a 1 in the specific bit position to enabled the item. The value of the pvalue parameter is a 32-bit number. Any bits not specified in the following lists are not used.
- If the
parmvalue is 1, the bits used by thepvalueparameter are:- 0 – Broadcast – controls broadcast phase SNMTFPs, TFRs and TFAs that are sent when a destination's status changes. If this flag is set, SNMTFPs/TFRs/TFAs are replicated to all associations/sockets that meet the Multicast SNM Criteria and have this enabled. The default is to enable all broadcast phase messages.
- 1 – Response Method – controls the sending of an SNMTFC/UPU as a reply to a message received on an association/socket for an unavailable destination. The SNMTFC/UPU is replicated to all associations/sockets that have this capability and meet the Response SNM Criteria. The default is to allow the response to be sent.
- 6 – Broadcast Congestion Status Change – controls the sending of unsolicited congestion status changes by an ASP. Unsolicited congestion status messages (TFCs generated when a destination's congestion status changes) are replicated to all ASPs who have this capability and meet the Multicast SNM Criteria. The default is to generate no unsolicited congestion status changes.
Table 6-14 shows the values can be entered for the
pvalueparameter if theparmvalue is 1. Thepvalueparameter value can be entered as a hexadecimal or a decimal number.Table 6-14 Valid PVALUE Parameter Values if PARM=1
Bits Enabled Bits Disabled Hexadecimal Value Decimal Value None
Bit 0 - Broadcast
Bit 1 - Response Method
Bit 6 - Broadcast Congestion Status Change
h’0
0
Bit 0 - Broadcast
Bit 1 - Response Method
Bit 6 - Broadcast Congestion Status Change
h’1
1
Bit 1 - Response Method
Bit 0 - Broadcast
Bit 6 - Broadcast Congestion Status Change
h’2
2
Bit 0 - Broadcast
Bit 1 - Response Method
Bit 6 - Broadcast Congestion Status Change
h’3*
3*
Bit 6 - Broadcast Congestion Status Change
Bit 0 - Broadcast
Bit 1 - Response Method
h’40
64
Bit 6 - Broadcast Congestion Status Change
Bit 0 - Broadcast
Bit 1 - Response Method
h’41
65
Bit 6 - Broadcast Congestion Status Change
Bit 1 - Response Method
Bit 0 - Broadcast
h’42
66
Bit 0 - Broadcast
Bit 1 - Response Method
Bit 6 - Broadcast Congestion Status Change
None
h’43
67
* The system default value
- If the
parmvalue is 2, the bits used by thepvalueparameter are:- 0 – ASP Active Notifications – controls the sending of ASP-Active notifications. If this value is specified, an ASP-Default notification is sent when an ASP transitions to the ASP-ACTIVE state. The default is not to send ASP-Active notifications.
- 1 – ASP Inactive Notifications – controls the sending of ASP-Inactive notifications. If this value is specified, an ASP-Inactive notification is sent when an ASP transitions to the ASP-INACTIVE state. The default is not to send ASP-Inactive notifications.
Note:
To see the ASP activations and inactivations, bits 0 and 1 of the pvalue parameter value need to be enabled. See Table 6-15. - 2 – ASPAS State Query – controls the sending of ASP/AS State notifications on request by an ASP. If this value is specified, the EAGLE responds with ASP and AS state notifications if the remote ASP sends ASP-UP or ASP-INACTIVE, while the local ASP is in the ASP-INACTIVE state, or the remote ASP sends an ASP-ACTIVE notification while the local ASP is in the ASP-ACTIVE state. The default is not to send ASP/AS state notifications.
Table 6-15 shows the values can be entered for the
pvalueparameter if theparmvalue is 2. Thepvalueparameter value can be entered as a hexadecimal or a decimal number.Table 6-15 Valid PVALUE Parameter Values if PARM=2
Bits Enabled Bits Disabled Hexadecimal Value Decimal Value None
Bit 0 - ASP Activate Notifications
Bit 1 - ASP Inactivate Notifications
Bit 2 - ASP AS State Query
h’0*
0*
Bit 0 - ASP Activate Notifications
Bit 1 - ASP Inactivate Notifications
Bit 2 - ASP AS State Query
h’1
1
Bit 1 - ASP Inactivate Notifications
Bit 0 - ASP Activate Notifications
Bit 2 - ASP AS State Query
h’2
2
Bit 0 - ASP Activate Notifications
Bit 1 - ASP Inactivate Notifications
Bit 2 - ASP AS State Query
h’3
3
Bit 2 - ASP AS State Query
Bit 0 - ASP Activate Notifications
Bit 1 - ASP Inactivate Notifications
h’4
4
Bit 0 - ASP Activate Notifications
Bit 2 - ASP AS State Query
Bit 1 - ASP Inactivate Notifications
h’5
5
Bit 1 - ASP Inactivate Notifications
Bit 2 - ASP AS State Query
Bit 0 - ASP Activate Notifications
h’6
6
Bit 0 - ASP Activate Notifications
Bit 1 - ASP Inactivate Notifications
Bit 2 - ASP AS State Query
None
h’7
7
* The system default value
- If the
parmvalue is 3, the bits used by thepvalueparameter are:- 0 – UA Heartbeats – heartbeat messages are sent on connections from the EAGLE to the far-end node that are in the ASP-Down, ASP-Active, and ASP-Inactive states if the bit is enabled.
- 1 – UA Graceful Shutdown – enables the graceful shutdown of IPSG M3UA connections if the bit is enabled.
Table 6-16 shows the values can be entered for the
pvalueparameter if theparmvalue is 3. Thepvalueparameter value can be entered as a hexadecimal or a decimal number.Table 6-16 Valid PVALUE Parameter Values if PARM=3
Bits Enabled Bits Disabled Hexadecimal Value Decimal Value None
Bit 0 - UA Heartbeats
Bit 1 - UA Graceful Shutdown
h’0*
0*
Bit 0 - UA Heartbeats
Bit 1 - UA Graceful Shutdown
h’1
1
Bit 1 - UA Graceful Shutdown
Bit 0 - UA Heartbeats
h’2
2
Bit 0 - UA Heartbeats
Bit 1 - UA Graceful Shutdown
None
h’3
3
* The system default value
- If the
parmvalue is 4, the bit 0, the SCTP Payload Protocol Indicator byte order option, is used by thepvalueparameter. This bit indicates whether the SCTP Payload Protocol Indicator (PPI) in the received or transmitted message should be in the Big Endian and Little Endian byte format.Table 6-17 shows the values can be entered for the
pvalueparameter if theparmvalue is 4. Thepvalueparameter value can be entered as a hexadecimal or a decimal number.Table 6-17 Valid PVALUE Parameter Values if PARM=4
SCTP Payload Protocol Indicator Byte Order Option - Bit 0 Hexadecimal Value Decimal Value Big Endian Byte Format h’0*
0*
Little Endian Byte Format
h’1
1
* The system default value
UA parameter set 10 contains the default values for the UA parameter sets and cannot be changed.
The set and scrset parameter values cannot be the same.
If the scrset parameter is specified, no other optional parameter may be specified.
The timer and tvalue parameters must be specified together. If one is specified, the other must be specified.
The parm and pvalue parameters must be specified together. If one is specified, the other must be specified.
Canceling the RTRV-UAPS Command
Because the rtrv-uaps command used in this procedure can output information for a long period of time, the rtrv-uaps command can be canceled and the output to the terminal stopped. There are three ways that the rtrv-uaps command can be canceled.
- Press the
F9function key on the keyboard at the terminal where thertrv-uapscommand was entered. - Enter the
canc-cmdwithout thetrmparameter at the terminal where thertrv-uapscommand was entered. - Enter the
canc-cmd:trm=<xx>, where<xx>is the terminal where thertrv-uapscommand was entered, from another terminal other that the terminal where thertrv-uapscommand was 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-trmcommand. The user’s permissions can be verified with thertrv-userorrtrv-secu-usercommands.
For more information about the canc-cmd command, go to Commands User's Guide.
Figure 6-34 Changing a UA Parameter Set
6.38 Turning Off the Large MSU Support for IP Signaling Feature
This procedure is used to turn off the Large MSU Support for IP Signaling feature, using the chg-ctrl-feat command.
The chg-ctrl-feat command uses these parameters:
:partnum – The part number of the Large MSU Support for IP Signaling feature, 893018401.
:status=off – used to turn off the Large MSU Support for IP Signaling feature.
The status of the Large MSU Support for IP Signaling feature must be on and is shown with the rtrv-ctrl-feat command.
Caution:
If the Large MSU Support for IP Signaling feature is turned off, the EAGLE will not process messages with a signaling information field (SIF) that is larger than 272 bytes.Figure 6-35 Turning Off the Large MSU Support for IP Signaling Feature