Activating the Origin-Based MTP Routing Feature

This procedure is used to enable and turn on the Origin-Based MTP Routing feature using the feature’s part number and a feature access key.

The feature access key for the Origin-Based MTP Routing feature is based on the feature’s part number and the serial number of the EAGLE, making the feature access key site-specific.

The enable-ctrl-feat command enables the feature by inputting the feature’s access key and the feature’s part number with these parameters:

Note:

As of Release 46.3, the fak parameter is no longer required. This parameter is only used for backward compatibility.

:fak – The feature access key provided by Oracle.

:partnum – The Oracle-issued part number of the Origin-Based MTP Routing feature, 893014201.

Once this feature is enabled, it is permanently enabled. This feature cannot be enabled with a temporary feature access key.

The enable-ctrl-feat command requires that the database contain a valid serial number for the EAGLE, and that this serial number is locked. This can be verified with the rtrv-serial-num command. The EAGLE is shipped with a serial number in the database, but the serial number is not locked. The serial number can be changed, if necessary, and locked once the EAGLE is on-site, with the ent-serial-num command. The ent-serial-num command uses these parameters.

:serial – The serial number assigned to the EAGLE. The serial number is not case sensitive.

:lock – Specifies whether or not the serial number is locked. This parameter has only one value, yes, which locks the serial number. Once the serial number is locked, it cannot be changed.

Note:

To enter and lock the EAGLE’s serial number, the ent-serial-num command must be entered twice, once to add the correct serial number to the database with the serial parameter, then again with the serial and the lock=yes parameters to lock the serial number. You should verify that the serial number in the database is correct before locking the serial number. The serial number can be found on a label affixed to the control shelf (shelf 1100).

The chg-ctrl-feat command uses these parameters:

:partnum – The Oracle-issued part number of the Origin-Based MTP Routing feature, 893014201.

:status=on – used to turn the Origin-Based MTP Routing feature on.

The status of the controlled features in the EAGLE is shown with the rtrv-ctrl-feat command.

To turn the Origin-Based MTP Routing feature on with the chg-ctrl-feat command, the STP option MTPLPRST must be set to yes. This can be verified by performing the rtrv-stpopts command. Perform the Configuring the Frequency of RST Messages on Low Priority Routes procedure to change the MTPLPRST option value, if necessary.

Once the Origin-Based MTP Routing feature is enabled and turned on, provisioning for the Origin-Based MTP Routing feature can be performed. Perform these procedures to provision the Origin-Based MTP Routing feature.

Origin-Based MTP Routing Feature

Origin-Based MTP Routing provides greater flexibility and control over the EAGLE routing mechanisms by enabling the user to selectively route traffic to the same destination through different networks depending on various classes of exception routes. The classes of exception routes are shown in the following list.

DPC and OPC - an exception route using the DPC (destination point code) and OPC (originating point code) in the message to determine how the message will be routed.
DPC and the originating linkset - an exception route using the DPC and the name of the linkset carrying incoming traffic to the EAGLE to determine how the message will be routed.
DPC and CIC - an exception route using the DPC and CIC (circuit identification code) in the message to determine how the message will be routed.
DPC and SI - an exception route using the DPC and SI (service indicator) value in the message to determine how the message will be routed.
DPC - an exception route using only the DPC in the message to determine how the message will be routed.

The DPC of a route coupled with an exception route class and exception route criteria creates a new destination for the route and also creates an additional entry in the EAGLE’s routing table. The number of entries in the EAGLE’s routing table is the number of DPCs provisioned with the ent-dstn command plus the number of exception route entries provisioned with the ent-rtx command.

The number of entries in the EAGLE’s routing table cannot exceed the number of DPCs allocated in the routing table, shown in the DESTINATION ENTRIES ALLOCATED: row of the rtrv-rtx and rtrv-dstn output. The EAGLE can contain a maximum of 10,000 entries in the routing table. The total number of entries provisioned in the routing table is shown in the TOTAL DPC(s): row of the rtrv-dstn or rtrv-rtx output.

All other properties of a routeset apply to exception routesets with respect to provisioning (routes and route costs) and alarming with the exception of network management, which is discussed in the "Network Management and Exception Routes" section.

Exception Route Processing Order and Route Costs

The processing order of exception routes is pre-defined. The exception class list in the "Network Management and Exception Routes" section also shows the order that the classes of exception routes are processed.

If a particular route has two exception routes, a DPC and OPC and a DPC and CIC exception route, the DPC and OPC exception route is used first since it is processed before the DPC and CIC exception route.

To determine the priority of exception routes, a relative cost value is assigned to each exception route. The relative cost values are used only within an exception route class. The DPC of the exception route contains multiple entries exception route class value, for example multiple entries with the same DPC and OPC value. The relative cost value determines the order in which the exception routes with the same DPC and OPC values are used to route the messages.

For example, DPC A contains the following exception routes:

OPC = B: RC=20: LSN=LSB
OPC = B: RC=20: LSN=LSC
OPC = B: RC=30: LSN=LSD
SI = 3: RC=10: LSN=LS3

When an SCCP message is received from Node B, the exception route mechanism splits traffic matching exception routes OPC = B between the linksets LSB and LSC, treating it as a combined linkset, since both entries have the same relative cost value. When both linksets LSB and LSC are not available, traffic is switched to linkset LSD. Even through the SI=3 exception route has a lower relative cost value than the other exception routes for DPC A, the SI=3 exception route is used to route the messages only when the linksets LSB, LSC, and LSD are not available.

CIC Handling

Exception routes can be provisioned based on a single CIC value or a range of CIC values in an ISUP message. The only value used by this feature for all CIC triggers will be the CIC value placed after the routing label and not any CIC value placed within the mandatory fixed, variable or optional parts of the message. Figure 3-39 shows the location of this value within the message.

Figure 3-39 ISDN User Part Message Parts

Since this feature will not consider any CIC value placed within the mandatory fixed, variable or optional part, messages within ISUP that are applied over a range of circuits (GRS, CGB, CGU, etc.) may be mishandled. Because of this, the user must consider how maintenance is handled before CIC ranging is used in order to ensure that circuit maintenance is performed properly.

For example, if a GRS is sent where the CIC field is 5 and the range field is 10, this implies that circuits 5 to 15 should be reset. If an exception route is provisioned for CIC 5, it would take the path (if available) provisioned since the CIC value in the message matches the one that is provisioned. However, if the exception route provisioned is 6, the CGU will not take the path provisioned even though 6 is within the range specified by the GRS message.

Network Management and Exception Routes

The Origin-Based MTP Routing operates on an end-to-end scheme, and not a point-to-point scheme. As a result, adjacent point codes cannot have exception routes. Correct network handing is critical for the EAGLE and other routing mechanisms to operate properly. Imposing exception routes over adjacent point codes introduces a large element of risk since elements of the network may receive point code and link events late, impacting routing to those and other destinations.

When considering the impact that exception routing could have on the network, the following restrictions are in place to ensure network sanity:

Adjacent point codes cannot not have exception routes.
Exception routes do not factor into the status of a destination. A destination’s status is defined only by the standard routes entered.
If all the DPC-based routes to a destination are unavailable, then the status of the destination is listed as prohibited even if there are exception routes available.
Preventative and broadcast TFx or TCx are not sent based on the status of exception routes. If an exception route is unavailable, the next exception route is chosen ending with the standard provisioned routes.

Congestion Handling and Origin-Based Routing

Since the only identifying characteristic of a TFC message is the capability point code (CPC), the EAGLE is unable to determine if the node or the route used to reach that destination is congested. Normally, the EAGLE would list the destination as congested since there was only one routeset to that destination.

With the Origin-Based MTP Routing feature, there is no longer only one routeset to a destination, but many. However, due to the inexact nature of the TFC, the EAGLE is still unable to determine if an exception route, a normal route, or the node itself that is congested. Thus, once a TFC is received regarding a node within exception routes provisioned against it, the EAGLE lists all routesets to that destination as congested.

To ensure that the EAGLE has the correct congestion status of the destination, the EAGLE sends an RCT regarding that destination over each impacted route and not just the normal route. This ensures that the destination does not “bounce” in and out of congestion. The EAGLE starts level 3 timer T15 at the beginning of the broadcast and level 3 timer T16 at the completion.

If the EAGLE receives a TFC regarding that destination in response to the poll, the EAGLE maintains the congestion level against it, even if it was received over a linkset which is part of an exception routeset and not the normal routeset. This is because the EAGLE can not rely on the incoming linkset of the TFC to identify the route that is congested since the adjacent nodes routing provisioning may be different the EAGLE.

Circular Route Detection and Origin-Based Routing

Normally, if the EAGLE detects that traffic originated from a route is to be sent back over the same route, it changes the status of the DPC to prohibited so that the linkset does not enter into congestion and potentially impact other valid routes. However, with Origin-Based MTP Routing, this can occur since there are some situations where this is the desired action. In order to reduce the impact to the true route of the DPC, the EAGLE prohibits only the impacted route to a destination, and not the destination itself.

This ensures that only the exception route provisioned in this manner is impacted if circular routing is detected and allow all other remaining traffic to reach the DPC.

However, since this is an abnormal routing condition, the EAGLE requires the use of the force=yes parameter when entering an exception route where the ILSN and the LSN parameters values are the same

If circular routing is detected on an exception route, enter the rst-dstn command to clear this condition.

Gateway Nodes and Exception Routes

Exception routes can be provisioned across networks, where the OPC and DPC do not exist within the same network type (ANSI, ITU-I or ITU-N). However, exception routes can be provisioned only through using full point code values, not alias or cluster point code values. This allows the user to understand which exception routes apply without trying to remember what aliases are provisioned for specific point codes.

Because of MTP conversion restrictions it is necessary that each OPC that is used within a gateway exception routeset must have an alias point code entry in the destination table for the network that the DPC of the exception route resides in. If the alias point code is not present, then the EAGLE is not able to route messages across networks.

SCCP Handling

With SCCP messaging, there are three possible OPC values that may be used; the OPC originally in the routing header, the EAGLE true point code, and the CGPA OPC (determined by whether the CGPA portion of the message is route-on-dpcssn or route-on-gt). To provide the option on which criteria to use, Origin-Based MTP Routing provides an SCCP option (MOBRSCCPOPC) which has three values:

mtp – The original OPC in the message is used as the OPC value to use for routing the SCCP message.
sccp – If the CGPA portion of the message is route-on-dpcssn, the point code in the CGPA portion of the message, if the CGPA portion of the message is route-on-dpcssn, is used as the OPC value to use for routing the SCCP message. If the CGPA portion of the message is route-on-gt, the MTP option, the original OPC in the message, is used as the OPC value to use for routing the SCCP message.
tpc – The EAGLE’s true point code is used as the OPC value to use for routing the SCCP message.

The MOBRSCCPOPC option is provisioned with the chg-sccpopts command.

If traffic truly originates from the EAGLE (for example, a UDTS), then the ilsn parameter of an exception route is not used in evaluating which exception route to use, if any. This is because the traffic was generated by the EAGLE and did not enter through any linkset.

UDTS/XUDTS messages generated by the EAGLE and messages undergoing global title translation are routed over OPC exception routes. However, other messages originated by the EAGLE, for example, response messages generated by the EAGLE SCCP services/subsystems, do not use OPC exception routes. These messages are routed using other exception criteria, for example, SI based exception routes, if these exception routes are defined. If these exception routes are not defined, normal routing is applied to these messages.

Display the controlled features in the database by entering the rtrv-ctrl-feat command.
This is an example of the possible output.
```
rlghncxa03w 06-10-28 11:43:04 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum    Status  Quantity
SCCP Conversion           893012001  on      ----
EIR                       893012301  on      ----
GSM Map Screening (GMS)   893013201  on      ----
HC-MIM SLK Capacity       893012707  on      64

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 Origin-Based MTP Routing feature is enabled, the entry MTP Origin-Based Routing is shown in the permanently enabled section of the rtrv-ctrl-feat output. If the status of the Origin-Based MTP Routing feature is on, no further action can be performed.

If the Origin-Based MTP Routing feature is not enabled, continue the procedure with 2.

If the rtrv-ctrl-feat output in 1 shows any controlled features, continue the procedure with Oracle. If the rtrv-ctrl-feat output shows only the HC-MIM SLK Capacity feature with a quantity of 64, 2 through 5 must be performed.

If the Origin-Based MTP Routing feature is enabled but not turned on, continue the procedure with 7.
Display the serial number in the database with the rtrv-serial-num command.
This is an example of the possible output.
```
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
System serial number = nt00001231

System serial number is not locked, yet.
```
Note:
If the serial number is correct and locked, continue the procedure with Oracle. If the serial number is correct but not locked, continue the procedure with 5. If the serial number is not correct, but is locked, this feature cannot be enabled and the remainder of this procedure cannot be performed. Contact the Customer Care Center to get an incorrect and locked serial number changed. Refer to My Oracle Support (MOS) for the contact information. The serial number can be found on a label affixed to the control shelf (shelf 1100).
Enter the correct serial number into the database using the ent-serial-num command with the serial parameter.
For this example, enter this command.

ent-serial-num:serial=<EAGLE’s correct serial number>

When this command has successfully completed, the following message should appear.
```
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
ENT-SERIAL-NUM:  MASP A - COMPLTD
```
Verify that the serial number entered into 3 was entered correctly using the rtrv-serial-num command.
This is an example of the possible output.
```
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
System serial number = nt00001231

System serial number is not locked, yet.
```
If the serial number was not entered correctly, repeat 2 and 3 and re-enter the correct serial number.
Lock the serial number in the database by entering the ent-serial-num command with the serial number shown in 2 , if the serial number shown in 2 is correct, or with the serial number shown in 4 , if the serial number was changed in 3 , and with the lock=yes parameter.
For this example, enter this command.

ent-serial-num:serial=<EAGLE’s serial number>:lock=yes

When this command has successfully completed, the following message should appear.
```
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
ENT-SERIAL-NUM:  MASP A - COMPLTD
```
Enable the Origin-Based MTP Routing feature by entering the enable-ctrl-feat command.
For this example, enter this command.

enable-ctrl-feat:partnum=893014201:fak=<Origin-Based MTP Routing feature access key>

Note:
The values for the feature access key (the fak parameter) are provided by Oracle. If you do not have the feature access key for the Origin-Based MTP Routing feature, contact your Oracle Sales Representative or Account Representative.

When the enable-crtl-feat command has successfully completed, this message should appear.
```
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
ENABLE-CTRL-FEAT: MASP A - COMPLTD
```
Display the existing value for the mtplprst parameter by entering the rtrv-stpopts command. The value for the mtplprst parameter is shown in the MTPLPRST field.
This is an example of the possible output.
```
rlghncxa03w 06-10-17 16:02:05 GMT  EAGLE5 36.0.0
STP OPTIONS
-----------------------
MTPLPRST            no
```
Note:
The rtrv-stpopts command output contains other fields that are not used by this procedure. If you wish to see all the fields displayed by the rtrv-stpopts command, see the rtrv-stpopts command description in Commands User's Guide.
Turn the Origin-Based MTP Routing feature on by entering the chg-ctrl-feat command with the part number used in Oracle and the status=on parameter.
Caution:
Once the Origin-Based MTP Routing feature is turned on, it cannot be turned off.

For this example, enter this command.

chg-ctrl-feat:partnum=893014201:status=on

When this command has successfully completed, the following message should appear.
```
rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
CHG-CTRL-FEAT: MASP A - COMPLTD
```

Verify the changes by entering this command.

rtrv-ctrl-feat:partnum=893014201

This is an example of the possible output.

rlghncxa03w 06-10-28 21:15:37 GMT EAGLE5 36.0.0
The following features have been permanently enabled:

Feature Name              Partnum   Status Quantity
MTP Origin-Based Routing  893014201 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.

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-40 Activating the Origin-Based MTP Routing Feature

Sheet 1 of 4

Sheet 2 of 4

Sheet 3 of 4

Sheet 4 of 4