Changing a Route Exception Entry

This procedure is used to change the attributes of an exception route in the database using the chg-rtx command. The attributes of the exception route that can be changed are the linkset (lsn parameter) and the relative cost (rc parameter) of the exception route.

The chg-rtx command uses these parameters.

:dpc/dpca/dpci/dpcn/dpcn24 – The destination point code of the node that the traffic is being sent to.

:opc/opca/opci/opcn/opcn24 – The originating point code of the node sending traffic to the EAGLE 5 ISS.

:ilsn – The name of the linkset carrying incoming traffic to the EAGLE.

:lsn – The name of the linkset that carries the traffic to the node specified by the destination point code.

:si – The service indicator value assigned to the exception route.

:cic – The circuit identification code value assigned to an exception route containing a single CIC entry or the CIC value that begins a range of CICs assigned to the exception route.

:ecic – The circuit identification code value that ends the range of CICs assigned to the exception route.

:rc – The new relative cost value (priority) that will be assigned to the exception route. The value of the rc parameter is 0 to 99.

:nlsn – The name of the new linkset that will carry the traffic to the node specified by the destination point code.

:force – This parameter allows the exception route to be changed even if the ilsn parameter value is the same as the nlsn parameter value. This parameter has only one value, yes.

The values of all the parameters specified for the chg-rtx command, except the rc, nlsn, and force=yes parameters, must be shown in the rtrv-rtx output and must be assigned to the specified dpc/dpca/dpci/dpcn/dpcn24 value.

The combinations of these parameters that can be used with the chg-rtx command are shown in Table 3-29 .

The names of the linksets required specified for the nlsn parameter must be provisioned in the database. This can be verified by entering the rtrv-ls command. If the required linkset is not in the database, perform one of these procedures to add the linkset.

• Adding an SS7 Linkset
• “Adding an X.25 Linkset” procedure in Database Administration - Features User's Guide
• “Configuring an IPGWx Linkset,” "Adding an IPSG M2PA Linkset," or "Adding an IPSG M3UA Linkset" procedures in Database Administration - IP7 User's Guide.

The linkset must be added according to the rules shown in the "Adding Linksets for Exception Routes" section.

Adding Linksets for Exception Routes

The linkset must be added according to the following rules:

• If the dpc value of the exception route entry is an ANSI point code, the adjacent point code of the new linkset must be an ANSI point code.
• If the exception route is an OPC-based exception route, the opc parameter value cannot be the adjacent point code of the linkset that is specified by the lsn parameter value.
• If the dpc value of the exception route entry is an ITU-I point code, the adjacent point code of the new linkset must be an ITU-I point code. If the linkset contains an SAPC (secondary adjacent point code), the adjacent point code of the new linkset can be either an ITU-N or ITU-N24 point code if the sapc value is an ITU-I point code. If the adjacent point code of the nlsn value is an ITU-N point code with a group code, when the exception route is changed, the group code of the adjacent point code of the new linkset does not have to be the same as the group code of the opcn value. If an ITU-N linkset is specified for the ilsn parameter, the group code of the adjacent point code of the ilsn value does not have to match the group code of the adjacent point code of the nlsn value.
• If the adjacent point code of the nlsn value is an ITU-N point code with a group code, when the exception route is changed, the group code of the adjacent point code of the new linkset does not have to be the same as the group code of the opcn value. If an ITU-N linkset is specified for the ilsn parameter, the group code of the adjacent point code of the ilsn value does not have to match the group code of the adjacent point code of the nlsn value.
• If the dpc value of the exception route entry is an ITU-N point code, the adjacent point code of the nlsn value must be an ITU-N point code.
  • If the dpc value of the exception route entry is an ITU-N point code with no group code assigned to the ITU-N point code, the adjacent point code of the nlsn value or the adjacent point code of all the linksets in the routeset can be an ITU-I point code if the sapc (secondary adjacent point code) value is an ITU-N point code.
  • If the dpc value of the exception route entry is an ITU-N point code with a group code, the adjacent point code of the nlsn value can be an ITU-I point code if the sapc value is an ITU-N point code. When the exception route is changed, the group code of the adjacent point code of the nlsn value and the ilsn value must be the same. The group code of the dpcn value must be the same as the group code of either the adjacent point code of the nlsn value or the sapc (secondary adjacent point code) assigned to the nlsn value.
• If the dpc value of the exception route entry is an ITU-N24 point code, the adjacent point code of the lsn value must be an ITU-N24 point code. If the linkset contains an SAPC (secondary adjacent point code), the adjacent point code of the lsn value can be an ITU-I point code if the sapc value is an ITU-N24 point code.

The SAPC values assigned to the linksets can be verified by entering the rtrv-ls:lsn=<linkset name> command.

1. Display the exception routes in the database by entering the rtrv-rtx command.

   This is an example of the possible output.

   rlghncxa03w 07-05-07 11:43:04 GMT  EAGLE5 37.0.0
      DPCA          RTX-CRITERIA              LSN        RC    APC
   
      003-003-003   OPCA
                    009-009-009               lsn1       3     002-002-002
                    010-010-010               lsn1       2     002-002-002
                    010-010-010               lsn2       10    002-002-003
   
                    ILSN
                    lsn3                      lsn2       2     002-002-003
                    lsn4                      lsn2       1     002-002-003
                    lsn4                      lsn1       10    002-002-002
   
                    CIC - ECIC
                    15    15                  lsn2       1     002-002-003
                    17    17                  lsn2       7     002-002-003
                    17    17                  lsn1       10    002-002-002
                    18    30                  lsn1       8     002-002-002
                    18    30                  lsn2       10    002-002-003
   
                    SI
                    3                         lsn2       5     002-002-003
                    3                         lsn1       10    002-002-002
                    5                         lsn2       5     002-002-003
      006-006-006   OPCA
                    125-150-175               lsn11      10    004-004-004
   
                    OPCI
                    2-103-1                   lsn11      20    004-004-004
   
                    ILSN
                    lsn12                     lsn11      11    004-004-004
   
                    lsn13                     lsn11      12    004-004-004
   
                    CIC - ECIC
                    250   250                 lsn12      15    005-005-005
                    300   500                 lsn12      25    005-005-005
   
                    SI
                    5                         lsn12      10    005-005-005
   
      DPCI          RTX-CRITERIA              LSN        RC    APC
      0-123-7       OPCI
                    1-222-3                   lsn3       10    1-234-5
                    1-222-4                   lsn3       11    1-234-5
                    1-222-5                   lsn4       11    2-145-6
   
      3-025-6       OPCA
                    135-102-089               lsn13      10    1-100-5
   
                    OPCI
                    4-054-0                   lsn13      15    1-100-5
   
                    OPCN
                    00503                     lsn11      15    1-100-5
   
                    ILSN
                    lsn2                      lsn14      45    4-139-4
                    lsn4                      lsn13      25    1-100-5
                    lsn16                     lsn16      50    12567
   
                    CIC - ECIC
                    100   100                 lsn14      35    4-139-4
                    50    75                  lsn13      40    1-100-5
   
                    SI
                    3                         lsn13      30    1-100-5
   
      DPCN          RTX-CRITERIA              LSN        RC    APC
      09852         OPCA
                    127-063-048               lsn15      10    11302
   
                    OPCI
                    3-037-1                   lsn16      15    12567
   
                    OPCN
                    00409                     lsn13      20    1-100-5
   
                    ILSN
                    lsn13                     lsn15      25    11302
                    lsn4                      lsn16      30    12567
   
                    CIC - ECIC
                    1000  1000                lsn16      40    12567
                    2000  3000                lsn15      45    11302
   
                    SI
                    4                         lsn15      35    11302
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   20
       EXCEPTION DPC(s):              41
       TOTAL DPC(s):                  61
       CAPACITY (% FULL):              3%
   ALIASES ALLOCATED:               12000
       ALIASES USED:                   0
       CAPACITY (% FULL):              0%
   

   The DPC of an exception route entry can contain only a maximum of two entries with the same RC value and with either the same OPC value, the same ILSN value, the same single CIC value, the same range of CIC values, or the same SI value. The LSN value for each entry must be different. The DPC of an exception route entry can contain only one entry with a single CIC value. Continue the procedure by performing one of these steps.

   • If no more than two entries in the exception route will contain the same exception route criteria, except for the linkset name, continue the procedure with 3.
   • If more than two entries in the exception route will contain the same exception route criteria, except for the linkset name, continue the procedure by performing one of these steps.
     • If more than two entries in an exception route that contain the same exception route criteria, except for the linkset name, are shown in this step, continue the procedure with 3.
     • If more than two entries in an exception route that contain the same exception route criteria, except for the linkset name, are not shown in this step, continue the procedure with 2.
2. For an exception route to have more than two entries with the same exception route criteria, except for the linkset name (the lsn parameter value), the 6-Way Loadsharing on Routesets feature must be enabled and turned on.

   To verify the status of the 6-Way Loadsharing on Routesets feature, enter this command.

   rtrv-ctrl-feat:partnum=893019801

   The following is an example of the possible output.

   rlghncxa03w 09-05-28 21:15:37 GMT EAGLE5 41.0.0
   The following features have been permanently enabled:
   
   Feature Name              Partnum    Status  Quantity
   6-Way LS on Routesets     893019801  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 6-Way Loadsharing on Routesets feature is not enabled or not turned on, perform Activating the 6-Way Loadsharing on Routesets Feature to enable and turn on the 6-Way Loadsharing on Routesets feature.

   After the 6-Way Loadsharing on Routesets feature has been enabled and turned on, or if the rtrv-ctrl-feat output shows that the 6-Way Loadsharing on Routesets feature is enabled and turned on, continue this procedure by performing one of these steps.

   • If only the relative cost of the exception route (rc parameter) is being changed, continue the procedure with 5.
   • If the name of the linkset that will be specified for the lsn parameter is shown in the rtrv-rtx output, continue the procedure with 4. If the name of the linkset is not shown in the rtrv-rtx output, continue the procedure with 3
3. Display the linksets in the database by entering the rtrv-ls command.

   This is an example of the possible output.

   rlghncxa03w 06-10-10 11:43:04 GMT EAGLE5 36.0.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn1          002-002-002   none 1   1   no  B   2    off off off no    off
   lsn2          002-002-003   none 1   1   no  B   3    off off off no    off
   lsn11         004-004-004   none 1   1   no  B   1    off off off no    off
   lsn12         005-005-005   none 1   1   no  B   4    off off off no    off
   
                                    L3T SLT              GWS GWS GWS
   
   LSN           APCI   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn3          1-234-5       none 1   2   no  B   2    off off off ---   off
   lsn4          2-145-6       none 1   2   no  B   2    off off off ---   off
   lsn13         1-100-5       none 1   2   no  B   1    off off off ---   off
   lsn14         4-139-4       none 1   2   no  B   1    off off off ---   off
   
                                    L3T SLT              GWS GWS GWS
   
   LSN           APCN   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn5          00002         none 1   2   no  B   2    off off off ---   off
   lsn6          00003         none 1   2   no  B   2    off off off ---   off
   lsn15         11302         none 1   2   no  B   2    off off off ---   off
   lsn16         12567         none 1   2   no  B   2    off off off ---   off
   
   Link set table is (12 of 1024) 1% full.
   

   If the required linkset is shown in the rtrv-ls output, continue the procedure with 4.

   If the required linkset is not in the database, (see the "Adding Linksets for Exception Routes" section), perform one of these procedures to add the linkset.

   1. Adding an SS7 Linkset
   2. “Adding an X.25 Linkset” procedure in Database Administration - Features User's Guide
   3. “Configuring an IPGWx Linkset,” "Adding an IPSG M2PA Linkset," or "Adding an IPSG M3UA Linkset" procedures in Database Administration - IP7 User's Guide.

   The linkset must be added according to the rules shown in the "Adding Linksets for Exception Routes" section. After the new linkset has been added, continue the procedure with 5.

   Note:

   If the DPC exception route entry is an ANSIDPC, the adjacent point code of the lsn value must be an ANSI point code. If the DPC exception route entry is an ANSIDPC, continue the procedure with 5.
4. Display the linkset that will be assigned to the exception route entry by entering the rtrv-ls command with the name of the linkset.

   For this example, enter these commands.

   rtrv-ls:lsn=lsn13

   This is an example of the possible output.

   rlghncxa03w 06-10-17 11:43:04 GMT  EAGLE5 36.0.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCI   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn13         1-100-5       none 1   2   no  B   1    off off off ---   off
   
              CLLI         TFATCABMLQ MTPRSE ASL8 SLSOCBIT SLSRSB MULTGC
              -----------  1          no     ---  none     7      no
   
              ITUTFR RANDSLS
              off    all
   
              IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
              no      ---------- ---   ---      ---       CdPA
   
             LOC   LINK SLC TYPE     IPLIML2
             1301  A    0   IPLIMI   M2PA
   
             SAPCN
             11211
   Link set table is (12 of 1024) 1% full.
   

   rtrv-ls:lsn=lsn16

   This is an example of the possible output.

   rlghncxa03w 06-10-17 11:43:04 GMT  EAGLE5 36.0.0
   
                                    L3T SLT              GWS GWS GWS
   LSN           APCI   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
   lsn16         12567         none 1   2   no  B   2    off off off ---   off
   
              CLLI         TFATCABMLQ MTPRSE ASL8 SLSOCBIT SLSRSB MULTGC
              -----------  1          no     ---  none     7      no
   
              ITUTFR RANDSLS
              off    all
   
              IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
              no      ---------- ---   ---      ---       CdPA
   
             LOC   LINK SLC TYPE     IPLIML2
             1301  A    0   IPLIMI   M2PA
   
             SAPCI
             5-067-1
   Link set table is (12 of 1024) 1% full.
   

   If the linkset does not meet the criteria shown in the "Adding Linksets for Exception Routes" section, either choose another linkset with an ITU-I, ITU-N, or ITU-N24 adjacent point code from the rtrv-ls output in 3 and repeat 4, or add a new linkset by performing one of these procedures:

   1. Adding an SS7 Linkset
   2. “Configuring an IPGWx Linkset,” "Adding an IPSG M2PA Linkset," or "Adding an IPSG M3UA Linkset" procedures in Database Administration - IP7 User's Guide.

   The linkset must be added according to the rules shown in the "Adding Linksets for Exception Routes" section.

5. Change the exception route entry by entering the chg-rtx command and specifying the parameter combinations shown in Table 3-29 for the exception route criteria being assigned to the exception route.

   Table 3-29 Change Exception Route Parameter Combinations

   Exception Route Criteria
   :dpc/dpca/ dpci/dpcn/ dpcn24 = DPC of the exception route being changed (See Note 1)	:dpc/dpca/ dpci/dpcn/ dpcn24 = DPC of the exception route being changed (See Note 1)	:dpc/dpca/ dpci/dpcn/ dpcn24 = DPC of the exception route being changed (See Note 1)	:dpc/dpca/ dpci/dpcn/ dpcn24 = DPC of the exception route being changed (See Note 1)	:dpc/dpca/ dpci/dpcn/ dpcn24 = DPC of the exception route being changed (See Note 1)
   :opc/opca/ opci/opcn/ opcn24 = OPC value of the exception route being changed. (See Note 3)	:ilsn = incoming linkset name of the exception route being changed (See Note 3)	:si = service indicator value of the exception route being changed	:cic = circuit identification code value of the exception route being changed	:cic = the circuit identification code value beginning a range of CICs of the exception route being changed
   :lsn = linkset name of the exception route being changed	:lsn = linkset name of the exception route being changed	:lsn = linkset name of the exception route being changed	:lsn = linkset name shown of the exception route being changed	:ecic = the circuit identification code value ending a range of CICs of the exception route being changed
   :nlsn = new linkset name shown in the rtrv-ls output (See Notes 2, 3, 4, and 6)	:nlsn = new linkset name shown in the rtrv-ls output (See Notes 2, 3, 4, and 6)	:nlsn = new linkset name shown in the rtrv-ls output (See Notes 2, 4, and 6)	:nlsn = new linkset name shown in the rtrv-ls output (See Notes 2, 4, and 6)	:lsn = linkset name shown of the exception route being changed
   :rc = new relative cost value, 0 - 99 (See Notes 4 and 5)	:rc = new relative cost value, 0 - 99 (See Notes 4 and 5)	:rc = new relative cost value, 0 - 99 (See Notes 4 and 5)	:rc = new relative cost value, 0 - 99 (See Notes 4 and 5)	:nlsn = new linkset name shown in the rtrv-ls output (See Notes 2, 4, and 6)
   :force=yes (See Note 3)	:force=yes (See Note 3)			:rc = new relative cost value, 0 - 99 (See Notes 4 and 5)
   Notes: 1. The DPC of an exception route entry can contain only a maximum of two entries with the same RC value and with either the same OPC value, the same ILSN value, the same SI value, the same CIC value, or range of CIC values if the 6-Way Loadsharing on Routesets feature is not enabled or turned on. If the 6-Way Loadsharing on Routesets feature is enabled and turned on, the DPC of an exception route entry can contain more than two entries with the same RC value and with either the same OPC value, the same ILSN value, the same SI value, the same CIC value, or range of CIC values, the LSN value for each entry must be different. 2. The new linkset specified in this step must meet the criteria shown in the "Adding Linksets for Exception Routes" section. 3. The force=yes parameter must be used if the LSN and ILSN values are the same, or if the OPC value is the same as the APC of the linkset specified by the lsn parameter. 4. The nlsn or rc parameters, or both parameters, must be specified with the chg-rtx command. 5. The new rc parameter value must be different from the current rc parameter value. 6. The nlsn parameter value cannot be currently assigned to the DPC of the exception route that is being changed.

   For this example, enter these commands.

   chg-rtx:dpca=003-003-003:opca=009-009-009:lsn=lsn1:nlsn=lsn2 :rc=20

   chg-rtx:dpci=0-123-7:ilsn=lsn4:lsn=13:nlsn=lsn16

   chg-rtx:dpci=0-123-7:cic=50:ecic=75:lsn=lsn13:rc=20

   chg-rtx:dpcn=09852:cic=1000:lsn=lsn16:rc=45

   chg-rtx:dpcn=09852:si=4:lsn=lsn15:nlsn=lsn16:rc=50

   chg-rtx:dpcn=09852:ilsn=lsn13:nlsn=lsn13:force=yes

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

   rlghncxa03w 06-10-07 08:28:30 GMT  EAGLE5 36.0.0
   CHG-RTX: MASP A - COMPLTD
   

   Note:

   If the linkset name was changed in 5, the lsn value for the rtrv-rtx command must be the nlsn value specified in 5.
6. Verify the changes using the rtrv-rtx command, specifying these parameters depending on the exception route criteria specified in 5.
   1. If the opc/opca/opci/opcn/opcn24 parameter was specified in 5 - enter these parameters and values specified in 5 with the rtrv-rtx command – dpc/dpca/dpci/dpcn/dpcn24, opc/opca/opci/opcn/opcn24, and lsn.
   2. If the ilsn parameter was specified in 5 - enter these parameters and values specified in 5 with the rtrv-rtx command – dpc/dpca/dpci/dpcn/dpcn24, ilsn, and lsn.
   3. If the si parameter was specified in 5 - enter these parameters and values specified in 5 with the rtrv-rtx command – dpc/dpca/dpci/dpcn/dpcn24, si, and lsn.
   4. If only the cic parameter was specified in 5 - enter these parameters and values specified in 5 with the rtrv-rtx command – dpc/dpca/dpci/dpcn/dpcn24, cic, and lsn.
   5. If the cic and ecic parameters were specified in 5 - enter these parameters and values specified in 5 with the rtrv-rtx command – dpc/dpca/dpci/dpcn/dpcn24, cic, ecic, and lsn.

   For this example, enter these commands.

   rtrv-rtx:dpca=003-003-003:opca=009-009-009:lsn=lsn2

   rlghncxa03w 06-10-07 08:28:30 GMT  EAGLE5 36.0.0
   
      DPCA          RTX-CRITERIA              LSN        RC    APC
   
      003-003-003   OPCA
                    009-009-009               lsn2       20    002-002-003
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   20
       EXCEPTION DPC(s):              36
       TOTAL DPC(s):                  56
       CAPACITY (% FULL):              3%
   ALIASES ALLOCATED:               12000
       ALIASES USED:                   0
       CAPACITY (% FULL):              0%
   

   rtrv-rtx:dpci=3-025-6:ilsn=lsn4:lsn=lsn16

   rlghncxa03w 06-10-07 08:28:30 GMT  EAGLE5 36.0.0
   
      DPCI          RTX-CRITERIA              LSN        RC    APC
   
      3-025-6       ILSN
                    lsn4                      lsn16      25    12567
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   20
       EXCEPTION DPC(s):              36
       TOTAL DPC(s):                  56
       CAPACITY (% FULL):              3%
   ALIASES ALLOCATED:               12000
       ALIASES USED:                   0
       CAPACITY (% FULL):              0%
   

   rtrv-rtx:dpci=3-025-6:cic=50:ecic=75:lsn=lsn13

   rlghncxa03w 06-10-07 08:28:30 GMT  EAGLE5 36.0.0
   
      DPCI          RTX-CRITERIA              LSN        RC    APC
   
      3-025-6       CIC - ECIC
                    50    75                  lsn13      20    1-100-5
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   20
       EXCEPTION DPC(s):              36
       TOTAL DPC(s):                  56
       CAPACITY (% FULL):              3%
   ALIASES ALLOCATED:               12000
       ALIASES USED:                   0
       CAPACITY (% FULL):              0%
   

   rtrv-rtx:dpcn=09852:ilsn=lsn13:lsn=13

   rlghncxa03w 06-10-07 08:28:30 GMT  EAGLE5 36.0.0
   
      DPCN          RTX-CRITERIA              LSN        RC    APC
   
      09852         ILSN
                    lsn13                     lsn13      25    1-100-5
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   20
       EXCEPTION DPC(s):              36
       TOTAL DPC(s):                  56
       CAPACITY (% FULL):              3%
   ALIASES ALLOCATED:               12000
       ALIASES USED:                   0
       CAPACITY (% FULL):              0%
   

   rtrv-rtx:dpcn=09852:si=4:lsn=lsn16

   rlghncxa03w 06-10-07 08:28:30 GMT  EAGLE5 36.0.0
   
      DPCN          RTX-CRITERIA              LSN        RC    APC
   
      09852         SI
                    4                         lsn16      50    12567
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   20
       EXCEPTION DPC(s):              36
       TOTAL DPC(s):                  56
       CAPACITY (% FULL):              3%
   ALIASES ALLOCATED:               12000
       ALIASES USED:                   0
       CAPACITY (% FULL):              0%
   

   rtrv-rtx:dpcn=09852:cic=1000:lsn=lsn16

   rlghncxa03w 06-10-07 08:28:30 GMT  EAGLE5 36.0.0
   
      DPCN          RTX-CRITERIA              LSN        RC    APC
      09852         CIC - ECIC
                    1000                      lsn16      45    12567
   
   DESTINATION ENTRIES ALLOCATED:   2000
       FULL DPC(s):                   20
       EXCEPTION DPC(s):              36
       TOTAL DPC(s):                  56
       CAPACITY (% FULL):              3%
   ALIASES ALLOCATED:               12000
       ALIASES USED:                   0
       CAPACITY (% FULL):              0%
   

7. 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 3-44 Changing a Route Exception Entry

Sheet 1 of 8

Sheet 2 of 8

Sheet 3 of 8

Sheet 4 of 8

Sheet 5 of 8

Sheet 6 of 8

Sheet 7 of 8

Sheet 8 of 8