Changing a Route

This procedure is used to change the relative cost of a route or the linkset assigned to a route in the database using the chg-rte command.

The chg-rte command uses these parameters.

:dpc/dpca/dpci/dpcn/dpcn24 – The destination point code of the node that the traffic is bound for.

Note:

See Point Code Formats 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.

:lsn – The name of the linkset that is currently assigned to the route.

:rc – The relative cost (priority) for this route.

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

The route to be changed must exist in the database. This can be verified in 1.

If the DPC of the route being changed is a private point code, or if the ipgwapc parameter of the linkset assigned to the route is yes, the route is an IPGWx route (a route that contains an IPGWx linkset). The IPGWx route can contain only one linkset. The DPC of an IPGWx route must either be the APC of the IPGWx linkset or the SAPC assigned to the IPGWx linkset. The DPC of the route cannot be changed. The SAPC can be assigned to only one linkset. As a result, the linkset assigned to the IPGWx route cannot be changed. Only the rc parameter value assigned to the route can be changed.

The examples in this procedure are used to change the relative cost assigned to the linkset ls01 for the route to DPC 003-003-003 in the database to change the name of linkset ls01 to lsa2.

Changing Routes Other than IPGWx Routes

If the 6-Way Loadsharing on Routesets feature is enabled and turned on, a maximum of six routes in the routeset can be assigned the same relative cost value. It is recommended that the routeset be provisioned with a group of four routes that have the same relative cost value and another group of two routes that have the same relative cost value. Three or five routes in the routeset that have the same relative cost value can be provisioned, but the odd number makes it more difficult to distribute the route traffic evenly. Six routes in the routeset that have the same relative cost value can be provisioned, but this does not allow for any backup routes and also offers the worst chance for congestion and queuing issues during network failures. If the 6-Way Loadsharing on Routesets feature is not enabled or not turned on, a maximum of two linksets can be assigned the same relative cost value. The relative cost value of the route is defined by the rc parameter of the chg-rte command and is shown in the RC field in the output of the rtrv-rte command.

The ANSI DPC (DPC/DPCA) of the route can use either a full point code, a cluster point code, or a network routing point code. ITU DPCs (DPCI and DPCN - 14-bit or 24-bit DPCNs) must use full point codes. For more information on full and cluster point codes, go to the Cluster Routing and Management Diversity (CRMD) section. For more information on network routing point codes, go to the Network Routing section.

The DPC of the route must be of the same format as the APC of the linkset being added to the route. That is, routes containing ANSI DPCs must have linksets with ANSI APCs; routes containing ITU-I DPCs must have linksets with ITU-I APCs; routes containing 14-bit ITU-N DPCs must have linksets with 14-bit ITU-N APCs; routes containing 24-bit ITU-N DPCs must have linksets with 24-bit ITU-N APCs. The DPC of the route must be defined as a true point code in the rtrv-dstn output. Alias point codes and secondary point codes cannot be used. True point codes are shown in the output of the rtrv-dstn command in the DPCA, DPCI, DPCN, or DPCN24 fields.

Either the nlsn or rc parameters, or both, must be specified with the chg-rte command. If neither of these parameters are specified, the command is rejected.

The linkset specified by the nlsn parameter must be in the database and must contain at least one signaling link. This can be verified with the rtrv-ls command and specifying the name of the linkset with the lsn parameter.

If the DPC of the route is a cluster point code or a network routing point code, only linksets, specified with either the lsn or nlsn parameters, whose linkset type is either B, C, or D can be assigned to the route. The linkset type is shown in the LST field of the rtrv-ls command output. If the linkset type of the desired linkset is either A, E, or PRX, one of three actions must be taken.

Choose another linkset with the linkset type B, C, or D.
Change the linkset type of an existing linkset – perform the Changing an SS7 Linkset procedure.
Add a new linkset to the database with the necessary signaling links and the linkset type B, C, or D.
1. Perform the Adding an SS7 Linkset procedure to add the linkset.
2. If the necessary signaling links are not in the database, go to the Adding an SS7 Signaling Link procedure and add the signaling links to the database.

If the DPC of the route is a member of a cluster point code, and the nested cluster allowed indicator (ncai parameter of either the ent-dstn or chg-dstn command) is set to no, then all destinations in the cluster have the same route as the cluster point code, with the same attributes as the route to the cluster point code. If the nested cluster allowed indicator is set to yes, then the routes to the members of the cluster point code, and the attributes of these routes, can be different from the route to the cluster point code. For more information, see the Nested Cluster Routing section.

If the APC of the linkset assigned to the route and the DPC of the route are the same, the name of the linkset cannot be changed in this procedure if the linkset and the DPC of the route contain these attributes.

The DPC of the route contains a proxy point code.
The linkset type of the linkset is PRX (a proxy linkset) and the proxy point code that is assigned to the DPC of the route is also assigned to the linkset.

These attributes can be verified by entering the rtrv-dstn command with the DPC of the route and the rtrv-ls command with the linkset name assigned to the route. If these attributes are present and you wish to change the name of the linkset, perform the Removing a Route procedure to remove the linkset from the DPC of the route. To remove a proxy linkset from the DPC of the route, all the linksets assigned to the DPC must be removed. After the linksets have been removed from the DPC, Add the new linkset to the DPC of the route by performing the Adding a Route Containing an SS7 DPC procedure.

Canceling the RTRV-LS and RTRV-RTE Commands

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

Press the F9 function key on the keyboard at the terminal where the rtrv-ls or rtrv-rte commands were entered.
Enter the canc-cmd without the trm parameter at the terminal where the rtrv-ls or rtrv-rte commands were entered.
Enter the canc-cmd:trm=<xx>, where <xx> is the terminal where the rtrv-ls or rtrv-rte commands were entered, from another terminal other that the terminal where the rtrv-ls or rtrv-rte commands were 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, go to Commands User's Guide.

Display the current route configuration using the rtrv-rte 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           ALIASI     ALIASN/N24    LSN        RC    APCA
   001-002-003 --------- --------------    ls04       10    001-002-003
                                               RTX:No  CLLI=ls04clli
   002-002-100 --------- --------------    ls01       10    002-002-100
                                           ls02       20    004-004-004
                                           ls03       30    003-003-003
                                               RTX:No  CLLI=ls01clli
   002-007-008 --------- --------------    ls06       10    002-007-008
                                               RTX:No  CLLI=ls06clli
   002-009-003 ---------- --------------   ls05       10    002-009-003
                                               RTX:No  CLLI=-----------
   003-003-003 --------- --------------    ls03       10    003-003-003
                                           ls01       20    002-002-100
                                           ls02       30    004-004-004
                                               RTX:No  CLLI=ls03clli
   004-004-004 --------- --------------    ls02       10    004-004-004
                                           ls01       20    002-002-100
                                           ls03       30    003-003-003
                                               RTX:No  CLLI=ls02clli
   009-002-003 ---------- --------------   ls07       10    009-002-003
                                               RTX:No  CLLI=-----------
   140-012-004    1-111-1      11121       ls000001   10    240-012-002
                                           ls000002   10    240-012-002
                                           ls000003   20    240-012-002
                                           ls000004   30    240-012-002
                                           ls000005   40    240-012-002
                                           ls000006   50    240-012-002
                                               RTX:No  CLLI=dp1
   140-012-005 1-111-2       11122         ls000001   10    240-012-002
                                           ls000002   10    240-012-002
                                           ls000003   20    240-012-002
                                           ls000004   30    240-012-002
                                           ls000005   40    240-012-002
                                           ls000006   50    240-012-002
                                               RTX:No  CLLI=dp2
   179-100-087 ---------- --------------   atmansi0   10    179-100-087
                                               RTX:No  CLLI=-----------
   200-050-176 ---------- --------------   atmansi1   10    200-050-176
                                               RTX:No  CLLI=-----------
   DPCI       ALIASN/N24       ALIASA      LSN        RC    APC
   2-234-5    11-13-3-3       240-111-111  ls100001   10    1-234-5
                                           ls100002   10    1-234-6
                                           ls100003   20    1-234-7
                                           ls100004   30    1-234-1
                                           ls100005   40    1-234-2
                                           ls100006   50    1-234-3
                                               RTX:No  CLLI=idp1
   3-150-4 -------------   --------------  lsi7       10    3-150-4
                                               RTX:No  CLLI=lsi7clli
   DPCN             ALIASA         ALIASI  LSN        RC    APC
   10685      ------------- ---------      lsn5       10    10685
                                               RTX:No  CLLI=lsi5clli
   13111         011-222-111 0-001-1       ls200001   10    11111
                                           ls200002   10    11112
                                           ls200003   20    11113
                                           ls200004   30    11114
                                           ls200005   40    11115
                                           ls200006   50    11116
                                               RTX:No  CLLI=ndp1
   DPCN24           ALIASA         ALIASI  LSN        RC    APC

If the DPC of the route being changed is a private point code, the route is an IPGWx route (a route that contains an IPGWx linkset). The DPC of an IPGWx route must either be the APC of the IPGWx linkset or the SAPC assigned to the IPGWx linkset. The DPC of the route cannot be changed. The SAPC can be assigned to only one linkset. As a result, the linkset assigned to the IPGWx route cannot be changed. Only the rc parameter value assigned to the route can be changed. If you wish to change the rc parameter value, continue the procedure with 9.

If you do not wish to change the rc parameter value, this procedure cannot be performed.

If the DPC of the route being changed is not a private point code, the route contains two or more linksets, and the rc parameter values of the routes are being changed, continue the procedure performing one of these steps.

If no more than two routes in the routeset will have the same relative cost value, continue the procedure by performing one of these steps.
- If the linkset name will not be changed, continue the procedure with 9.
- If the linkset name will be changed, continue the procedure by performing one of these steps.
  - if the APC of the linkset and the DPC of the route are the same. continue the procedure with 4.
  - If the APC of the linkset and the DPC of the route are not the same, continue the procedure with 6.
If more than two routes in the routeset will have the same relative cost value, continue the procedure by performing one of these steps.
- If routesets that contain more than two routes with the same relative cost value are shown in the rtrv-rte output, continue the procedure by performing one of these steps.
  - If the linkset name will not be changed, continue the procedure with 9.
  - If the linkset name will be changed, continue the procedure by performing one of these steps.
    - if the APC of the linkset and the DPC of the route are the same. continue the procedure with 4.
    - If the APC of the linkset and the DPC of the route are not the same, continue the procedure with 6.
- If routesets that contain more than two routes with the same relative cost value are not shown in the rtrv-rte output, continue the procedure with 3.

If the DPC of the route being changed is not a private point code, and the route contains only one linkset, continue the procedure with 2 to verify the ipgwapc value assigned to the linkset.

Display the linkset assigned to the route by entering the rtrv-ls command with the name of the linkset.
For this example, enter this command.

rtrv-ls:lsn=ls04

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           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
ls04          001-002-003   none 1   1   no  A   1    off off off ---   on

          CLLI         TFATCABMLQ MTPRSE ASL8
          ls04clli     1          no     ---

          IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
          yes     ---------- 100   100    % 80      % CdPA

          LOC  LINK SLC TYPE
          1303 A     0  SS7IPGW

Link set table is (10 of 1024) 1% full.
```
If the ipgwapc parameter value of the linkset is yes, the route is an IPGWx route (a route that contains an IPGWx linkset). The DPC of an IPGWx route must either be the APC of the IPGWx linkset or the SAPC assigned to the IPGWx linkset. The DPC of the route cannot be changed. The SAPC can be assigned to only one linkset. As a result, the linkset assigned to the IPGWx route cannot be changed. Only the rc parameter value assigned to the route can be changed. If you wish to change the rc parameter value, continue the procedure with 9.

If you do not wish to change the rc parameter value, this procedure cannot be performed.
If the ipgwapc parameter value of the linkset is no, continue the procedure by performing one of these step.
- If no more than two routes in the routeset will have the same relative cost value, continue the procedure by performing one of these steps.
  - If the linkset name will not be changed, continue the procedure with 9.
  - If the linkset name will be changed, continue the procedure by performing one of these steps.
    if the APC of the linkset and the DPC of the route are the same. continue the procedure with 4.
    
    If the APC of the linkset and the DPC of the route are not the same, continue the procedure with 6.
- If more than two routes in the routeset will have the same relative cost value, continue the procedure by performing one of these steps.
  - If routesets that contain more than two routes with the same relative cost value are shown in the rtrv-rte output, continue the procedure by performing one of these steps.
    If the linkset name will not be changed, continue the procedure with 9.
    
    If the linkset name will be changed, continue the procedure by performing one of these steps.
    if the APC of the linkset and the DPC of the route are the same. continue the procedure with 4.
    
    If the APC of the linkset and the DPC of the route are not the same, continue the procedure with 6.
  - If routesets that contain more than two routes with the same relative cost value are not shown in the rtrv-rte output, continue the procedure with 3.
For a routeset to have more than two routes with the same relative cost 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 the linkset name will not be changed, continue the procedure with 9.
- If the linkset name will be changed, continue the procedure by performing one of these steps.
  - if the APC of the linkset and the DPC of the route are the same. continue the procedure with 4.
  - If the APC of the linkset and the DPC of the route are not the same, continue the procedure with 6.

Display the attributes of the linkset whose DPC is the same as the DPC of the route by entering the rtrv-ls command with the name of the linkset. For this example, enter this command.

rtrv-ls:lsn=ls02

This is an example of the possible output.

rlghncxa03w 07-08-14 09:24:36 GMT  EAGLE5 37.0.0

                                 L3T SLT              GWS GWS GWS
LSN           APCA   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
ls02          004-004-004   none 1   1   no  PRX 1    off off off no    off

              PPCA          CLLI         TFATCABMLQ MTPRSE ASL8
              010-010-010   -----------  1          ---    no

           IPGWAPC MATELSN    IPTPS  LSUSEALM SLKUSEALM GTTMODE
           no      ---------- ----   ---      ---       CdPA

Link set table is (9 of 1024) 1% full.

If the linkset type is PRX, continue the procedure with 5.

If the linkset type is not PRX, continue the procedure with 6.

Display the DPC of the route by entering the rtrv-dstn command with the DPC of the route. For this example, enter this command.
rtrv-dstn:dpca=004-004-004

This is an example of the possible output.
```
rlghncxa03w 10-12-15 09:22:39 GMT  EAGLE5 43.0.0

   DPCA          CLLI        BEI ELEI   ALIASI          ALIASN/N24    DMN
   004-004-004   ----------- no  --- ----------      --------------   SS7

   PPCA         NCAI PRX     RCAUSE NPRST SPLITIAM HMSMSC HMSCP SCCPMSGCNV
   010-010-010  ---- no      none   off   none     no     no    none

Destination table is (14 of 2000) 1% full
Alias table is (0 of 12000) 0% full
PPC table is (2 of 10) 20% full
```
If the linkset shown in 4 does not contain the proxy point code shown in this step, continue the procedure with 6.

If the linkset shown in 4 contains the proxy point code shown in this step, the linkset name cannot be changed in this procedure. If you wish to change the linkset name, perform the Removing a Route procedure to remove the linkset from the DPC of the route. To remove a proxy linkset from the DPC of the route, all the linksets assigned to the DPC must be removed. After the linksets have been removed from the DPC, Add the new linkset to the DPC of the route by performing the Adding a Route Containing an SS7 DPC procedure. However, the RC value for this linkset can be changed. If you wish to change the RC value for this linkset, repeat this procedure from 3.

Display the linksets in the database with 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
e1e2          001-207-000   none 1   1   no  B   6    off off off no    off
ls1305        000-005-000   none 1   1   no  A   1    off off off no    off
ls1307        000-007-000   none 1   1   no  A   1    off off off no    off
e1m1s1        001-001-001   none 1   1   no  A   7    off off off no    off
e1m1s2        001-001-002   none 1   1   no  A   7    off off off no    off

                                 L3T SLT              GWS GWS GWS
LSN           APCI   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
e1e2i         1-207-0       none 1   1   no  B   4    off off off ---   on
ls1315        0-015-0       none 1   1   no  A   1    off off off ---   off
ls1317        0-017-0       none 1   1   no  A   1    off off off ---   on
e1m2s1        1-011-1       none 1   1   no  A   7    off off off ---   off
e1m2s2        1-011-2       none 1   1   no  A   7    off off off ---   off

Link set table is (10 of 1024) 1% full.

If the new linkset to be added to the route is not shown in the rtrv-ls output, and the DPC of the route is not an ANSI point code, add the new linkset by performing the Adding an SS7 Linkset procedure.

After the new linkset has been added, or if the new linkset is shown in the rtrv-ls output, continue the procedure by performing one of these steps.

If the DPC of the route is not a cluster point code, continue the procedure with 8.
If the DPC of the route is a cluster point code, continue the procedure with 7.

Display the ncai parameter value assigned to the cluster point code using the rtrv-dstn command and specifying the cluster point code.
If the ncai parameter value is no, then the route to the DPC must be the same as the route to the cluster point code. If the ncai parameter value is yes, the route to the member of the cluster does not have to be the same as the route to the cluster point code. The ncai value is shown in the NCAI field of the rtrv-dstn output. For this example, enter this command.

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
   -----------  ----         none   off   none     no     no    none

Destination table is (12 of 2000) 1% full
Alias table is (6 of 8000) 1% full
```
Note:
If the DPC of the route is not a cluster point code or a 14-bit ITU-N point code with group codes, continue the procedure with 9.

Display each linkset being assigned to the route to verify the multgc parameter value with the rtrv-ls command, specifying the name of the linkset that will be assigned to the route.

If the multgc linkset parameter value is yes, then 14-bit ITU National DPCs with group codes that are different from the linkset APC group code can be assigned to the route. If the multgc value is set to no, then only 14-bit ITU National DPCs with group codes that are the same as the linkset APC group code can be assigned to the route. The multgc value is shown in the MULTGC field of the rtrv-ls output.

For this example, enter the following command.

rtrv-ls:lsn=e1e2i

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           APCI   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
e1e2i         1-202-0       none 1   1   no  B   10   off off off ---   on

          CLLI         TFATCABMLQ MTPRSE ASL8 SLSOCBIT SLSRSB MULTGC
          -----------  5          no     ---  none     1      no

          ITUTFR
          off

          IPGWAPC MATELSN    IPTPS LSUSEALM SLKUSEALM GTTMODE
          no      ---------- ---   ---      ---       CdPA

          LOC  LINK SLC TYPE     IPLIML2
          1311 A     0  IPLIMI   M2PA
          1313 A     1  IPLIMI   M2PA
          1311 B     2  IPLIMI   M2PA
          1313 B     3  IPLIMI   M2PA

          SAPCN
          03664

Link set table is (10 of 1024) 1% full.

Change the route configuration in the database using the chg-rte command.
For this example, enter this command.

chg-rte:dpca=003-003-003:lsn=ls01:rc=50:nlsn=lsa2
These are the rules that apply to adding a route.
- An IPGWx route can contain only one linkset, and only the rc parameter value for an IPGWx route can be changed. For an SS7 route other than an IPGWx route, a maximum of two linksets can be assigned the same rc parameter value, 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, a maximum of six linksets in the route can have the same rc parameter value.
- If the DPC of the route is a cluster point code or a network routing point code, the link set type of the linkset assigned to the route must be either B, C, or D.
- If the DPC of the route is a member of a cluster point code, and the nested cluster allowed indicator (ncai parameter of either the ent-dstn or chg-dstn command) is set to no, then the route to the DPC must be the same as the route to the cluster point code. If the nested cluster allowed indicator is set to yes, the route to the member of the cluster does not have to be the same as the route to the cluster point code.
- For routes containing 14-bit ITU National DPCs with group codes, if the linkset assigned to the route has the MULTGC value set to yes, then the group code of the linkset's APC can be different from the group code of the route's DPC. If the MULTGC value is set to no, then the group code of the linkset's APC must be the same as the group code of the route's DPC.
- If the DPC of the route is a cluster point code, the linksets that will be assigned to the route, with the nlsn parameter, cannot specify the ipgwapc=yes parameter.
- The DPC of the route must be of the same format as the APC of the linkset being added to the route. That is, routes containing ANSI DPCs must have linksets with ANSI APCs; routes containing ITU-I DPCs must have linksets with ITU-I APCs; routes containing 14-bit ITU-N DPCs must have linksets with 14-bit ITU-N APCs; routes containing 24-bit ITU-N DPCs must have linksets with 24-bit ITU-N APCs.
When this command has successfully completed, this message should appear.
```
rlghncxa03w 06-10-07 08:45:54 GMT  EAGLE5 36.0.0
CHG-RTE: MASP A - COMPLTD
```

Verify the changes using the rtrv-rte command, specifying the destination point code of the route or the name of the routeset assigned to the route.

For this example, enter this command.

rtrv-rte:dpca=003-003-003

This is an example of the possible output.

rlghncxa03w 06-10-07 11:43:04 GMT  EAGLE5 36.0.0
   DPCA           ALIASI     ALIASN/N24    LSN        RC    APCA
   003-003-003 ---------- --------------   ls03       10    003-003-003
                                           ls01       20    002-002-100
                                           ls02       30    004-004-004
                                               RTX:No  CLLI=ls03clli

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-22 Changing a Route

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