Adding a Cluster Point Code

This procedure is used to add a cluster point code for the Cluster Routing and Management Diversity (CRMD) feature, and nested cluster point codes for the nested cluster routing feature to the database, using the ent-dstn command.

To change the attributes of an existing cluster point code, go to the Changing the Attributes of a Cluster Point Code procedure.

Note:

Cluster entries can only be provisioned as ANSI destination point codes. Cluster entries cannot be provisioned for ITU international or ITU national destination point codes, and cannot be provisioned as a proxy point code. The ANSI alias point code for an ITU international or ITU national destination point code must be a full point code. An ANSI private point code must be a full point code.

To remove a cluster point code from the database, go to the Removing a Destination Point Code procedure.

The Cluster Routing and Management Diversity feature must be turned on.

The ent-dstn command uses these parameters:

:dpc/dpca – The destination point code being added to the database.

Note:

See Point Code Formats for a definition of the point code types that are used on the EAGLE.

Note:

Alias point codes (aliasi/aliasn/aliasn24) and secondary point codes (spc/spca) cannot be specified for a cluster point code.

:clli – The Common Language Location Identifier assigned to this point code.

:domain – The network in which the destination entity or node exists, SS7.

Note:

Specifying :domain=ss7 is the only valid entry for cluster destinations.

:bei – Broadcast exception indicator that indicates whether transfer-prohibited (TFP) messages will be broadcast from this node. The bei=yes parameter means TFPs will not be broadcast. The bei=no parameter means TFPs will be broadcast.

:ipgwapc– (ANSI networks only)IP Gateway Adjacent Point Code indicator. Specify ipgwapc=yes to provide SS7 linkset definition compatibility for gateway connections to IP-SCPs. The default is ipgwapc=no.

:elei – For cluster point codes only. Specifies whether or not the EAGLE maintains a dynamic status exception list for each cluster route that may be used to reach the member signaling points making up the cluster. The elei=yes parameter means the EAGLE does not maintain an exception list for the cluster point code specified by the dpc parameter. The elei=no parameter means the EAGLE does maintain an exception list for the cluster point code specified by the dpc parameter. The default value for the elei parameter is no.

:ncai – The nested-cluster-allowed indicator specifies whether or not the route to the cluster point code can be different from the route to a point code that is a member of the cluster point code. A point code is a member of a cluster point code if it has the same network identifier (NI) and network cluster (NC) values as the cluster point code. This parameter can be specified only for cluster point codes.

If the ncai parameter value is yes, the cluster point code is a nested cluster point code. Point codes that are members of this cluster point code can be assigned to routesets that are different from the routeset assigned to the cluster point code.

If the ncai parameter value is no, the cluster point code is not a nested cluster point code. Point codes that are members of this cluster point code must be assigned to the same routeset assigned to the cluster point code.

The default value for the ncai parameter is no.

See the Nested Cluster Routing section for more information on the nested cluster routing feature.

:nprst - NM bits reset. This parameter specifies whether the NM bits in an ITU IAM message should be set to 00. This parameter has two values.

• off - Do not set NM bits to 00 in an ITU IAM message if the nptype option value in the rtrv-tifopts output is nm.
• on - Set the NM bits to 00 in an ITU IAM message if the nptype option value in the rtrv-tifopts output is nm.

  The default value for this parameter is off.

:rcause - Release cause. This parameter specifies the condition that triggers the sending of a Release message. This parameter has these values.

• 0 - 127
• none - use the values specified for the rcausenp and rcausepfx parameters in the rtrv-tifopts output.

  The default value for this parameter is none.

  If the rlcopc parameter value in the rtrv-tipopts output is on and a value of 0-127 is specified for the rcause parameter, then the rcause parameter value overrides the values specified for the rcausenp and rcausepfx parameters in the rtrv-tifopts output.

:splitiam - This parameter specifies how and when to split an ITU IAM message into one IAM message and one SAM message. This parameter has these values.

• 15-31 - The maximum number of CdPN digits allowed in the IAM message before the splitting occurs. The remaining digits, up to a total of 32, are encoded in the SAM message.
• none - the value specified for the splitiam parameter in the rtrv-tifopts output is used to determine when to split the IAM message.

  The default value for this parameter is none.

To specify the nprst or rcause parameters, the TIF Number Portability feature, part number 893018901, must be enabled. To specify the splitiam parameter, at least one of these features must be enabled.

• TIF Number Portability - part number 893018901
• TIF SCS Forwarding - part number 893022201
• TIF Simple Number Substitution - part number 893024001
• TIF Additional Subscriber Data - part number 893024501
• TIF Generic Routing Number - part number 893025501
• TIF Selective Screening - part number 893040201

The status of these features is shown in the rtrv-ctrl-feat output. Perform the procedures in TIF User's Guide to enable these features.

:sccpmsgcnv - The sccpmsgcnv parameter controls SCCP UDT(S)/XUDT(S) message conversion for the specified destination. This parameter can be specified only if the XUDT UDT Conversion feature is enabled and turned on. The rtrv-ctrl-feat output shows the status of the XUDT UDT Conversion feature. If the XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature. This parameter contains these values.

• none - SCCP UDT(S)/XUDT(S) message conversion is not required on messages for the destination. This value is the default value for this parameter.
• udt2xudt - All UDT(S) messages for the destination are converted to XUDT(S) messages.
• xudt2udt - All non-segmented XUDT(S) messages for the destination are converted to UDT(S) messages. Segmented XUDT(S) messages for the destination are not converted to UDT(S ) messages.
• sxudt2udt - All segmented and non-segmented XUDT(S) messages for the destination are converted to UDT(S) messages.

The ent-dstn command also contains the homescp and homesmsc parameters. The values for these parameters are yes and no. The value no is the default value for these parameters. The value yes for these parameters cannot be specified for a cluster point code. To specify the value yes for these parameters, perform the Adding a Destination Point Code or Changing a Destination Point Code procedures.

To add a cluster point code to the database, the Cluster Routing and Management Diversity feature must be on. The ncai parameter can be specified for the cluster point code only if both the Cluster Routing and Management Diversity and nested cluster routing features are on. This is shown by the entries CRMD = on (for the Cluster Routing and Management Diversity feature) and NCR = on (for the nested cluster routing feature) in the rtrv-feat command output.

The domain of the cluster point code must be SS7 (domain=ss7).

To enter an ANSI point code, an ANSI self ID for the EAGLE must be defined. This can be verified with the rtrv-sid command. The ANSI self ID is shown in the PCA field in the rtrv-sid command output. If no values are shown in the PCA field of the rtrv-sid command output, go to Changing the Self-Identification of the EAGLE procedure to add the ANSI Self ID of the EAGLE.

The actual number of destination point codes that can be configured in the database is set by the mtpdpcq parameter of the chg-stpopts command, and is shown in the MTPDPCQ field in the rtrv-stpopts command output. See 13.

If the 5000 Routes feature is not on, and 6000, 7000, 8000, or 10,000 routesets are not enabled, the sum of the mtpdpcq and mtpxlq parameters cannot exceed 2500. The range of values for the mtpdpcq and mtpxlq parameters is 500 to 2000.

If the 5000 Routes feature is on, and 6000, 7000, 8000, or 10,000 routesets are not enabled the sum of the mtpdpcq and mtpxlq parameters cannot exceed 5500. The range of values for the mtpdpcq and mtpxlq parameters is 500 to 5000.

If 6000 routesets are enabled, the sum of the mtpdpcq and mtpxlq parameters cannot exceed 6500. The range of values for the mtpdpcq and mtpxlq parameters is 500 to 6000.

If 7000 routesets are enabled, the sum of the mtpdpcq and mtpxlq parameters cannot exceed 7500. The range of values for the mtpdpcq parameter is 500 to 7000. The range of values for the mtpxlq parameter is 500 to 6000.

If 8000 routesets are enabled, the sum of the mtpdpcq and mtpxlq parameters cannot exceed 8500. The range of values for the mtpdpcq parameter is 500 to 8000. The range of values for the mtpxlq parameter is 500 to 6000.

If 10,000 routesets are enabled, the sum of the mtpdpcq and mtpxlq parameters cannot exceed 10500. The range of values for the mtpdpcq and mtpxlq parameters is 500 to 10,000.

Note:

For more information on the destination point code quantities, go to the Changing the DPC Quantity procedure.

If the ncai parameter value is yes, the EAGLE can have a maximum of 200 nested cluster point codes in the database.

The value of the clli parameter cannot be in the DPC table and cannot match the CLLI of the EAGLE. Verify this by entering the rtrv-dstn and the rtrv-sid commands, shown in 3 and 4. If the value of the clli parameter matches any CLLI values in either of these outputs, choose another value for the clli parameter that does not match any CLLIs shown in either of these command outputs.

If the PCTYPE field of the rtrv-sid command output contains the entry ANSI, and the network value of the destination point codes specified by the ent-dstn command, is from 0 to 5, the cluster value of that point code must be from 1 to 255. If the network value of that point code is from 6 to 255, the cluster value of that point code must be from 0 to 255.

To add a cluster point code to the database when the database contains point codes that are members of the cluster, the linkset type used by the routes to the member point codes must be either B, C, or D. For example, you wish to add the cluster point code 004-004-* and the database contains point codes 004-004-001 and 004-004-002. When cluster point code is added, point codes 004-004-001 and 004-004-002 would become members of the cluster point code 004-004-*. If point codes 004-004-001 or 004-004-002 are the destination point codes of routes, and the linkset type of these routes are either A or E, the cluster point code 004-004-* cannot be added to the database. The linkset type of these routes must be changed to either B, C, or D to add cluster point code 004-004-* to the database. To change the linkset type of a linkset, perform the Changing an SS7 Linkset procedure.

The examples in this procedure are used to enter the cluster point code 111-011-* and the nested cluster point code 030-045-*.

Canceling the RTRV-DSTN Command

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

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

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

1. Display the current destination point codes in the database, using the rtrv-dstn command.

   This is an example of the possible output.

   rlghncxa03w 10-12-10 11:43:04 GMT EAGLE5 43.0.0
   Extended Processing Time may be Required
   
      DPCA          CLLI        BEI ELEI   ALIASI           ALIASN/N24    DMN
      002-002-002   ----------- no  --- --------------   --------------   SS7
      020-002-045   rlghncbb100 no  --- --------------   --------------   SS7
      020-002-050   rlghncbb100 no  --- --------------   --------------   SS7
      030-045-001   ----------- yes --- --------------   --------------   SS7
      111-011-001   ----------- yes --- --------------   --------------   SS7
      240-012-005   rlghncbb002 yes ---    1-112-2          11112         SS7
      240-012-006   rlghncbb003 yes ---    1-112-3          11113         SS7
   
      DPCI          CLLI        BEI ELEI   ALIASA           ALIASN/N24    DMN
      2-131-1       rlghncbb023 no  ---    222-210-000      12001         SS7
      2-131-2       ----------- no  ---    222-211-001      12002         SS7
   
      DPCN          CLLI        BEI ELEI   ALIASA           ALIASI        DMN
      11211         rlghncbb013 no  ---    222-200-200      2-121-1       SS7
      11212         rlghncbb013 no  ---    222-200-201      2-121-2       SS7
   
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   11
       EXCEPTION DPC(s):               0
       NETWORK DPC(s):                 0
       CLUSTER DPC(s):                 0
       TOTAL DPC(s):                  11
       CAPACITY (% FULL):             1%
   ALIASES ALLOCATED:               8000
       ALIASES USED:                  12
       CAPACITY (% FULL):             1%
   X-LIST ENTRIES ALLOCATED:         500
   RTRV-DSTN: MASP A - COMPLTD
   

   If the addition of the cluster point code will not exceed the current DPC capacity shown in the rtrv-dstn output, continue the procedure with 2.

   If the addition of the cluster point code will exceed the current DPC capacity, and the current capacity is less than 10,000 (or 10,500 if the DESTINATION ENTRIES ALLOCATED and X-LIST ENTRIES ALLOCATED fields are shown in the rtrv-dstn output), perform the Changing the DPC Quantity procedure to change the DPC quantity. Continue the procedure with 2.

   If the addition of the cluster point code will exceed the current DPC capacity, and the current capacity is 10,000 (or 10,500 if the DESTINATION ENTRIES ALLOCATED and X-LIST ENTRIES ALLOCATED fields are shown in the rtrv-dstn output), perform the Removing a Destination Point Code procedure to remove a DPC or perform the Removing a Route Exception Entry procedure to remove an exception route. Continue the procedure with 2.

   Note:

   If thertrv-dstn output in1shows any cluster point codes, and nested cluster point codes are not being configured in this procedure, continue the procedure with3.

   Note:

   If cluster point codes are not shown in thertrv-dstn output in1, but ANSI point codes are shown in1, continue the procedure with3.
2. Display the self-identification of the EAGLE using the rtrv-sid command. This is an example of the possible output..

   rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
   PCA              PCI             PCN           CLLI            PCTYPE
   010-020-030      0-123-1         12-0-14-1     rlghncxa03w     OTHER
   
   CPCA
   002-002-002       002-002-003       002-002-004      002-002-005
   002-002-006       002-002-007       002-002-008      002-002-009
   004-002-001       004-003-003       050-060-070
   
   CPCI
   1-001-1           1-001-2           1-001-3          1-001-4
   1-002-1           1-002-2           1-002-3          1-002-4
   2-001-1           7-222-7
   
   CPCN
   2-0-10-3          2-0-11-0          2-0-11-2          2-0-12-1
   2-2-3-3           2-2-4-0           10-14-10-1
   

   If the PCA field does not contain an entry, perform the Changing the Self-Identification of the EAGLE procedure and add an ANSI point code to the self identification of the EAGLE.

   Note:

   If theDESTINATION ENTRIES ALLOCATEDandX-LIST ENTRIES ALLOCATED fields are shown in thertrv-dstn output in1, and nested cluster point codes are not being configured in this procedure, continue the procedure with6.
3. Verify that the Cluster Routing and Management Diversity feature is turned on, by entering the rtrv-feat command. If nested cluster point codes are to be configured in the database, the nested cluster routing feature must be turned on. If the Cluster Routing and Management Diversity feature is turned on, the CRMD field should be set to on. If the nested cluster routing feature is turned on, the NCR field should be set to on. In this example, both features are off.

   Note:

   Thertrv-feat command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-feat command, see thertrv-feat command description in Commands User's Guide.
4. Turn the Cluster Routing and Management Diversity feature on by entering this command.

   chg-feat:crmd=on

   Note:

   If the Cluster Routing and Management Diversity feature is on, shown by theCRMD = on entry in thertrv-feat command output in3, continue the procedure with5.

   Note:

   Once the Cluster Routing and Management Diversity feature is turned on with thechg-feat command, it cannot be turned off.

   The Cluster Routing and Management Diversity feature must be purchased before you turn this feature on with the chg-feat command. If you are not sure if you have purchased the Cluster Routing and Management Diversity feature, contact your Sales Representative or Account Representative.

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

   rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
   CHG-FEAT: MASP A - COMPLTD
   

   If nested cluster point codes are being added to the database or the ncai parameter is be specified for the cluster point code and the nested cluster routing feature is on, shown by the NCR = on entry in the rtrv-feat command output in 3, and DPCs are shown in the rtrv-dstn output that are members of the cluster point code that is being added, continue the procedure with 6. If the rtrv-dstn output does not show any DPCs that are members of the cluster point code being added, continue the procedure with 9.

   If nested cluster point codes are being added to the database or the ncai parameter is be specified for the cluster point code and the nested cluster routing feature is off, continue the procedure with 5.

5. Turn the nested cluster routing feature on by entering this command.
   chg-feat:ncr=on

   Note:

   Once the nested cluster routing feature is turned on with thechg-feat command, it cannot be turned off.

   The nested cluster routing feature must be purchased before you turn this feature on with the chg-feat command. If you are not sure if you have purchased the nested cluster routing feature, contact your Sales Representative or Account Representative.

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

   rlghncxa03w 07-05-10 11:43:04 GMT EAGLE5 37.0.0
   CHG-FEAT: MASP A - COMPLTD
   

   Note:

   If thertrv-dstn output does not show any DPCs that are members of the cluster point code being added in this procedure, continue the procedure with 9 .
6. The cluster point code cannot be added to the database if the database contains member point codes assigned to routes that are assigned to linksets whose linkset type is either A or E.

   Enter the rtrv-rte command with one of the DPCs that is a member of the cluster point code being added in this procedure. For this example, enter these commands.

   rtrv-rte:dpca=111-011-001

   This is an example of the possible output.

   rlghncxa03w 07-05-17 15:35:05 GMT  EAGLE5 37.0.0
      DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
      111-011-001    -------    -----------   lsn2       10   111-011-001
                                                  RTX:No  CLLI=-----------
   

   rtrv-rte:dpca=030-045-001

   This is an example of the possible output.

   rlghncxa03w 07-05-17 15:35:05 GMT  EAGLE5 37.0.0
      DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
      030-045-001    -------    -----------   lsn3       10    030-045-001
                                                  RTX:No  CLLI=-----------
   

   If the DPC specified in this step is the DPC of a route, continue the procedure with 7.

   If the DPC specified in this step is not the DPC of a route, repeat this step for other DPCs, shown in the rtrv-dstn output, that are members of the cluster point code being added in this procedure.

   If all the DPCs that are members of the cluster point code being added have been displayed, and none of these DPCs are DPCs of routes, continue the procedure with 9.

7. Enter the rtrv-ls command with the linkset name shown in the rtrv-rte output in 6.

   The linkset name is shown in the LSN column of the rtrv-rte output. For this example, enter these commands.

   rtrv-ls:lsn=lsn2

   This is an example of the possible output.

   rlghncxa03w 09-05-17 15:35:05 GMT  EAGLE5 41.0.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn2          111-011-001   none 1   1   no  B   2    off off off no    off
   
              CLLI         TFATCABMLQ MTPRSE ASL8
              -----------  1          ---    no
   
              RANDSLS
              off
   
              IPSG  IPGWAPC  GTTMODE           CGGTMOD
              no    no       CdPA                no
   
                                     L2T               PCR  PCR
              LOC  LINK SLC TYPE     SET  BPS    ECM   N1   N2
              1103 A     0  LIMDS0   1    56000  BASIC ---  -----
              1104 A     1  LIMDS0   1    56000  BASIC ---  -----
   
   Link set table is (6 of 1024) 1% full.
   

   rtrv-ls:lsn=lsn3

   This is an example of the possible output.

   rlghncxa03w 09-05-17 15:35:05 GMT  EAGLE5 41.0.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn3          030-045-001   none 1   1   no  B   2    off off off no    off
   
              CLLI         TFATCABMLQ MTPRSE ASL8
              -----------  1          ---    no
   
              RANDSLS
              off
   
              IPSG  IPGWAPC  GTTMODE           CGGTMOD
              no    no       CdPA                no
   
                                     L2T               PCR  PCR
              LOC  LINK SLC TYPE     SET  BPS    ECM   N1   N2
              1103 B     0  LIMDS0   1    56000  BASIC ---  -----
              1104 B     1  LIMDS0   1    56000  BASIC ---  -----
   
   Link set table is (6 of 1024) 1% full.
   

   If the linkset type of the linkset is either A or E, performChanging an SS7 Linkset to change the linkset type to B, C, or D.

   If all the DPCs that are members of the cluster point code being added have not been displayed in 6, repeat 6 and 7.

   After all the linksets whose APCs are members of the cluster point code that is being added, and the linkset type of these linksets shown in this step is B, C, or D, or the linkset type was changed, continue the procedure by performing one of these steps.

   • If the nprst, rcause, or splitiam parameters will not be specified for the cluster point code, continue the procedure with 9 .
   • If the nprst, rcause, or splitiam parameters will be specified for the cluster point code, continue the procedure with 8.
8. Display the features that are enabled by entering the rtrv-ctrl-feat command. This is an example of the possible output.

   rlghncxa03w 10-12-17 15:35:05 GMT  EAGLE5 43.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum   Status Quantity
   HC-MIM SLK Capacity       893012707 on     64
   TIF Number Portability    893018901 off    ----
   XUDT UDT Conversion       893035301 on     ----
   
   
   The following features have been temporarily enabled:
   
   Feature Name              Partnum   Status Quantity   Trial Period Left
   Zero entries found.
   
   
   The following features have expired temporary keys:
   
   Feature Name              Partnum
   Zero entries found.
   

   To specify the nprst or rcause parameters, the TIF Number Portability feature, part number 893018901, must be enabled. To specify the splitiam parameter, at least one of these features must be enabled.

   • TIF Number Portability - part number 893018901
   • TIF SCS Forwarding - part number 893022201
   • TIF Simple Number Substitution - part number 893024001
   • TIF Additional Subscriber Data - part number 893024501
   • TIF Generic Routing Number - part number 893025501

   Perform the procedures in TIF User's Guide to enable these features as required.

9. Continue the procedure by performing one of these steps.
   • Continue the procedure with 11 if any of these conditions are present.
     • The sccpmsgcnv parameter will not be specified for the cluster point code.
     • The sccpmsgcnv parameter will be specified for the cluster point code and the rtrv-ctrl-feat output in this step shows that the XUDT UDT Conversion feature is enabled and turned on. If the rtrv-ctrl-feat output in this step shows that the XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature.
   • Continue the procedure with 10 if the sccpmsgcnv parameter will be specified for the cluster point code and 8 was not performed.
10. Enter this command to verify the status of the XUDT UDT Conversion feature.

    rtrv-ctrl-feat:partnum=893035301

    This is an example of the possible output.

    rlghncxa03w 10-12-17 15:35:05 GMT  EAGLE5 43.0.0
    The following features have been permanently enabled:
    
    Feature Name              Partnum   Status Quantity
    XUDT UDT Conversion       893035301 on     ----
    
    
    The following features have been temporarily enabled:
    
    Feature Name              Partnum   Status Quantity   Trial Period Left
    Zero entries found.
    
    
    The following features have expired temporary keys:
    
    Feature Name              Partnum
    Zero entries found.
    

    If the XUDT UDT Conversion feature is not enabled or turned on, perform the "Activating the XUDT UDT Conversion Feature" procedure in Database Administration - GTT User's Guide to enable and turn on the XUDT UDT Conversion feature.

    If the XUDT UDT Conversion feature is enabled and turned on, or the "Activating the XUDT UDT Conversion Feature" procedure was performed in this step, continue the procedure with 11.

11. Add the cluster point code to the database, by using the ent-dstn command.

    For this example, enter these commands.

    ent-dstn:dpca=111-011-*:clli=rlghncbb000:bei=yes:elei=yes:domain=ss7

    ent-dstn:dpca=030-045-*:clli=rlghncbb010:bei=yes:elei=yes :domain=ss7:ncai=yes

    ent-dstn:dpca=100-075-*:bei=yes:elei=yes:ncai=yes:nprst=on:rcause=15 :splitiam=10:sccpmsgcnv=udt2xudt

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

    rlghncxa03w 09-05-17 15:35:05 GMT  EAGLE5 41.0.0
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   12
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 3
        TOTAL DPC(s):                  15
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  12
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    ENT-DSTN: MASP A - COMPLTD
    

12. Verify the changes using the rtrv-dstn command and specifying the DPC that was entered in 11.

    For this example, enter these commands.

    rtrv-dstn:dpca=111-011-*

    This is an example of the possible output.

    rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0
    
       DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
       111-011-*     rlghncbb000 yes yes ----------      --------------   SS7
    
       SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       -----------  no           none   off   none     no     no    none 
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   12
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 3
        TOTAL DPC(s):                  15
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  12
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    RTRV-DSTN: MASP A - COMPLTD
    

    rtrv-dstn:dpca=030-045-*

    This is an example of the possible output.

    rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0
    
       DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
       030-045-*     rlghncbb010 yes yes ----------      --------------   SS7
    
       SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       -----------  no           none   off   none     no     no    none
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   12
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 3
        TOTAL DPC(s):                  15
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  12
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    RTRV-DSTN: MASP A - COMPLTD
    

    rtrv-dstn:dpca=100-075-*

    rlghncxa03w 10-12-28 21:16:37 GMT EAGLE5 43.0.0
    
       DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
       100-075-*     ----------- yes yes ----------      --------------   SS7
    
       SPCA         NCAI         RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
       -----------  yes          15     on      10     no     no    udt2xudt
    
    DESTINATION ENTRIES ALLOCATED:   2000
        FULL DPC(s):                   12
        EXCEPTION DPC(s):               0
        NETWORK DPC(s):                 0
        CLUSTER DPC(s):                 3
        TOTAL DPC(s):                  15
        CAPACITY (% FULL):             1%
    ALIASES ALLOCATED:               8000
        ALIASES USED:                  12
        CAPACITY (% FULL):             1%
    X-LIST ENTRIES ALLOCATED:         500
    RTRV-DSTN: MASP A - COMPLTD
    

    Note:

    If you do not wish to change the exception list parameters for the Cluster Routing and Management Diversity feature, continue the procedure with16.
13. The parameters for the exception list for the Cluster Routing and Management Diversity feature can be changed from the default settings by using the chg-stpopts command. The parameters of the chg-stpopts command that control the exception point-code list are:

    mtpxlq = the maximum number of entries the exception list (x-list) can contain

    mtpxlet = the maximum amount of time the EAGLE will maintain an unreferenced exception list (x-list) entry, expressed in the format hhmm, where hh is the number of hours, and mm is the number of minutes.

    mtpxlot = the exception list (x-list) occupancy threshold (in terms of percentage of space available). If this threshold is exceeded, the EAGLE raises a minor alarm.

    mtpdpcq = the maximum number of destination point codes that can be configured on the EAGLE.

    Note:

    The sum of theMTPDPCQ andMTPXLQ value’s cannot exceed one of these totals depending on the features that are enabled or turned on:

    • 2500 – if the 5000 Routes feature is not on, and 6000, 7000, or 8000 routesets are not enabled. The range of values for the mtpdpcq and mtpxlq parameters is 500 to 2000.
    • 5500 – if the 5000 Routes feature is on, but 6000, 7000, or 8000 routesets are not enabled. The range of values for the mtpdpcq and mtpxlq parameters is 500 to 5000.
    • 6500 – if 6000 routesets are enabled. The range of values for the mtpdpcq and mtpxlq parameters is 500 to 6000.
    • 7500 – if 7000 routesets are enabled. The range of values for the mtpdpcq parameter is 500 to 7000. The range of values for the mtpxlq parameter is 500 to 6000.
    • 8500 – if 8000 routesets are enabled. The range of values for the mtpdpcq parameter is 500 to 8000. The range of values for the mtpxlq parameter is 500 to 6000.
    • 10,500 – if 10,000 routesets are enabled. The range of values for the mtpdpcq and mtpxlq parameters is 500 to 10,000.

    Display the existing values for the exception list parameters, by entering the rtrv-stpopts command. This is an example of the possible output.

    rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
    STP OPTIONS
    -----------------------
    MTPXLQ             500
    MTPXLET           0100
    MTPXLOT            90%
    MTPDPCQ           2000
    

    Note:

    Thertrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-stpopts command, see thertrv-stpopts command description in Commands User's Guide.

    Note:

    If the Cluster Routing and Management Diversity was turned on in this procedure, theMTPXLQ,MTPXLET, andMTPXLOT parameters are shown with these default values.

    • MTPXLQ – 500
    • MTPXLET – 0100
    • MTPXLOT – 90%

    The MTPDPCQ value is not changed when the Cluster Routing and Management Diversity is turned on.

14. If you wish to change the exception list parameters or the mtpdpcq value, enter the chg-stpopts command.

    Note:

    If the DPC quantity or the exception list quantity is being changed in this step, both the mtpdpcq andmtpxlq parameters do have to be specified in this step unless the resulting sum of themtpdpcq andmtpxlq parameters would exceed the totals shown in12. For example, the currentmtpdpcq value is 4000 and the currentmtpxlq value is 1500, resulting in a sum of 5500, and only the 5000 Routes feature is on. To change either value, both parameters must be specified and the sum of the new values cannot exceed 5500. If in this example, the currentmtpdpcq value is 3000 and the currentmtpxlq value is 1500, resulting in a sum of 4500, either parameter value can be changed without specifying the other parameter as long as the sum of the values does not exceed 5500.

    For this example, change the DPC quantity value to 1750, the exception list size to 750, the exception list timer to 1 hour and 30 minutes (90 minutes), and the exception list occupancy threshold to 75%. Enter this command.

    chg-stpopts:mtpdpcq=1750:mtpxlq=750:mtpxlet=0130:mtpxlot=75

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

    rlghncxa03w 07-05-17 15:35:05 GMT EAGLE5 37.0.0
    CHG-STPOPTS: MASP A - COMPLTD
    

15. Verify the changes using the rtrv-stpopts command.

    This is an example of the possible output.

    rlghncxa03w 07-05-17 16:02:05 GMT  EAGLE5 37.0.0
    STP OPTIONS
    -----------------------
    MTPXLQ             750
    MTPXLET           0130
    MTPXLOT            75%
    MTPDPCQ           1750
    

    Note:

    Thertrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by thertrv-stpopts command, see thertrv-stpopts command description in Commands User's Guide.
16. Back up the new changes, using the chg-db:action=backup:dest=fixed command.
    These messages should appear; the active Maintenance and Administration Subsystem Processor (MASP) appears first.

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

Figure 2-25 Adding a Cluster Point Code

Sheet 1 of 5

Sheet 2 of 5

Sheet 3 of 5

Sheet 4 of 5

Sheet 5 of 5