Go to primary content
Oracle® Communications EAGLE Database Administration - GTT User's Guide
Release 46.7
E97332-02
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

Activating the EPAP Data Split and Dual ExAP Configuration Features

This procedure is used to enable and turn on the EPAP Data Split and Dual ExAP Configuration features using the feature part numbers.

Once the feature is turned ON, E5-SMxG card can be provisioned as either a DN card or IMSI card. On the DN card, DN, DN Block, ASD and Entity data is be loaded. On the IMSI card, IMSI, IMEI, IMEI Block and Entity data is loaded. The feature also provides the GTT data type. A maximum of 240 million of DN data is loaded on the DN cards and a maximum of 240 million of IMSI on IMSI cards. The total maximum capacity of 480 million data is supported system wide.

With the Dual ExAP Configuration feature, the EPAP-based features and ELAP-based features can be turned on (and process traffic) simultaneously on the same EAGLE. This feature is used to control the provisioning of E5-SMxG card to be EPAP, ELAP or GTT data types, and determine the table to download to the corresponding E5-SMxG. Another data type, GTT, is also assigned to E5-SMxG card if the corresponding E5-SMxG card does not download any tables from EPAP or ELAP.

Table 5-1 EAGLE Feature and EPAP DB Capacity Combinations

EPAP Split DB Feature STPOPTS: EPAP 240M Max Ind. DNs Max Ind. IMSIs Max Ind. DNs + Ind. IMSIs Max Ind. IMEIs SM Requires 64-bit GPLs? Max RTDB Size (DN+IMSI+IMEI) supported on Ind. SM8G-B Max RTDB Size (DN+IMSI+IMEI) supported on Ind. SLIC
OFF OFF 120M 120M 120M 32M No 120M 120M
ON OFF 120M 120M 240M 32M No 120M 120M
OFF ON 240M 240M 240M 48M Yes 240M 240M (240M DN + 240M IMSI)
ON ON 240M 240M 480M 48M Yes 240M 480M (420M DN + 240M IMSI)

Note:

*Use the AUTO=YES parameter with the chg-ip-lnk command to set ExAP Ports on SM (SMxG/SLIC) cards to auto negotiate the speed and duplex. Corresponding ports on EPAP LAN switches should be configured accordingly to achieve the required operational speed and duplex of 1Gbps and Full Duplex. Refer to ExAP Administration Guide for more information. Once the SM cards in service, the pass command pass:cmd="netstat -i":loc=<:SM card loc> can be used to verify the operational speed and duplex of ExAP ports on SM cards.

Table 5-2 Reload Times For Cards Connected to EPAP With Cold Restart and 240M DN + 240M IMSI

Data Rate between EPAP and card 1 card (before 46.4) Up to 32 cards (before 46.4) From 33 up to 40 cards (46.5 and later)
100 Mbps 120 minutes 180 minutes 180 minutes
1 Gpbs 15 minutes 20 minutes 20 minutes

Note:

The recommended data rate connection between EPAP and EAGLE is 1 Gpbs. A 100 Mbps data rate connection between EPAP and EAGLE card is not recommended if the EPAP database has more than 120 DN or 120 IMSI or more than 32 cards connected to the EPAP. If 100 Mbps connections are used, the RTDB download time will increase substantially and can increase the download time by an hour or more, depending on the number of entries in the RTDB.

EPAP Data Split

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

chg-stpopts:on=mfc if MFC has not been turned ON yet.

:fak – The feature access key provided. The feature access key contains 13 alphanumeric characters and is not case sensitive.

:partnum – The issued part number of the EPAP Data Split feature, 893039801.

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.

The initial status of this feature is "disabled and off." This feature cannot be temporarily enabled (with the temporary feature access key).

Once this feature has been enabled, the feature must be activated with the chg-ctrl-feat command. The chg-ctrl-feat command uses these parameters:

:partnum – The issued part number of the Dual ExAP Configuration feature, 893039801.

:status=on – used to turn the Dual ExAP Configuration feature on.

Note:

Once this feature has been turned on, it cannot be turned off.

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

For existing SMs, enter the following commands:
  • inh-card: loc=<SM location>
  • chg-card:loc=<SM location>:data={DN/IMSI/GTT}
  • alw-card:loc=<SM location>
  • chg-db:action=backup to backup the configuration

If GTTDIST=EPAP, the user must change GTTDIST to ALL, ELAP, DN or IMSI based on the availability of matching data type cards. If GTTDIST is to be changed directly to DN or IMSI from EPAP, then the change should be done when there are enough EPAP cards remaining to handle the GTT traffic load. There also needs to be sufficient DN or IMSI cards (in IS-NR state) to handle GTT traffic load or GTT traffic may be discarded.

To add new SMs, enter the following commands:
  • ent-card:loc=<SM location>:appl=vsccp:type=dsm:data={DN/IMSI/GTT}
  • chg-ip-lnk to configure the IP address to connect to the EPAP server
  • alw-card:loc=<SM location>
  • chg-db:action=backup to backup the configuration

Dual ExAP Configuration

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

chg-stpopts:on=mfc if MFC has not been turned ON yet.

:fak – The feature access key provided. The feature access key contains 13 alphanumeric characters and is not case sensitive.

:partnum – The issued part number of the Dual ExAP Configuration feature, 893040501.

This feature is enabled and turned ON with in one step with the enable-ctrl-feat command.

Note:

The EPAP data parameter is allowed when RTDB Split Feature is enabled.

The initial status of this feature is "disabled and off." This feature cannot be temporarily enabled (with the temporary feature access key).

Once this feature is enabled, all existing SM cards will be automatically reconfigured as either ELAP cards (if the LNP feature was ON before Dual ExAP Config is enabled), or EPAP cards (if EPAP based feature is ON before Dual ExAP Config is enabled).

Once this feature has been enabled, the feature must be activated with the chg-ctrl-feat command. The chg-ctrl-feat command uses these parameters:

:partnum – The issued part number of the Dual ExAP Configuration feature, 893040501.

:status=on – used to turn the Dual ExAP Configuration feature on.

Note:

Once this feature has been turned on, it cannot be turned off.

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

For existing SMs, enter the following commands:
  • inh-card: loc=<SM location>
  • chg-card:loc=<SM location>:data={EPAP/ELAP/GTT}
  • alw-card:loc=<SM location>
  • chg-db:action=backup to backup the configuration
To add new SMs, enter the following commands:
  • ent-card:loc=<SM location>:appl=vsccp:type=dsm:data={EPAP/ELAP/GTT}
  • chg-ip-lnk to configure the IP address to connect to the EPAP server
  • alw-card:loc=<SM location>
  • chg-db:action=backup to backup the configuration

Feature Activation At EPAP

By default the feature EPAP data split is OFF. The uiEdit tool is used to turn this ON. Execute following command to view the current value of configurable parameter: $ /usr/TKLC/epap/bin/uiEdit EPAP_DATA_SPLIT.

Execute following command to activate the feature: $ /usr/TKLC/epap/bin/uiEdit EPAP_DATA_SPLIT ON.

Note:

After the previous command has been performed, restart the PDBA and the EPAP application to complete feature activation.

Note:

Turning on the EPAP_DATA_SPLIT feature allows the 240M data to be provisioned and EIR_BLK_EXPANSION_100k will increase the provisioning capacity of EIR blocks from 50k to 100k.

EIR Block Expansion Feature

By default the feature EIR block expansion to 100K is OFF. The "uiEdit" tool is used to turn this ON. Execute following command to view the current value of configurable parameter: $ /usr/TKLC/epap/bin/uiEdit EIR_BLK_EXPANSION_100K.

Execute following command to activate the feature: $ /usr/TKLC/epap/bin/uiEdit EIR_BLK_EXPANSION_100K ON.

Note:

After the previous command has been performed, restart the PDBA or send SIGHUP signal to PDBA to complete feature activation.

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. The user 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).