Activating the EPAPX DB Expansion Feature

When EPAP is running on release 16.3 with its full capacity, DN-based SLIC-SCCP cards are able to load 480M individual DN entries. IMSI-based SLIC-SCCP cards are be able to load 600M individual IMSI entries or 600M individual IMEI entries. This is applicable when the EPAP Split DB feature is ON. DB allocation to EAGLE EPAP-based cards are flexible, as per the configurations done on the EPAP side.

Note:

Once the STPOPTS:EPAPX feature is enabled, STPOPTS:EPAP240M cannot be enabled.

If the EPAP Split DB feature is OFF, then the DN & IMSI tables are loaded onto a single EPAP card. In this case the DN + IMSI entries must be less than 480M. The exact allowed combinations are listed in the following table:

Note:

Table 5-3 details the card configuration as in data=<dn/imsi/epap>.

Table 5-3 EAGLE Feature and EPAPX DB Capacity Combinations

EPAP Split DB Feature	STPOPTS: EPAPX	Max Ind. DNs	Max Ind. IMSIs	Max Ind. DNs + Ind. IMSIs	Max Ind. IMEIs	Max RTDB Size (DN+IMSI+IMEI) Supported on Ind. SLIC
OFF	OFF EPAP240M OFF	120M	120M	120M	48M	120M for DN card 135M for IMSI card
ON	OFF EPAP240M OFF	120M	120M	240M	48M	120M for DN card 135M for IMSI card
ON	OFF EPAP240M ON	240M	240M	480M	48M	240M for DN card 288M for IMSI card 528M for EPAP card
OFF	ON	480M	480M	480M	480M	480M (DN + IMSI + IMEI)
ON	ON	480M	600M	1080M	600M	480M for DN card 600M for IMSI card

To enable the 480M DN & 600M IMSI/600M IMEI capacity expansion on EAGLE, the epapx parameter is introduced in the STPOPTS table. The SLIC-SCCP cards on EAGLE are able to load 480M DN entries only when the STPOPTS: EPAPX parameter is ON. Similarly, SLIC-SCCP cards on EAGLE are able to load 600M IMSI or 600M IMEI entries only when the STPOPTS: EPAPX parameter is ON.

Note:

The STPOPTS:EPAPX feature can only be turned ON if all EPAP-based SCCP cards are SLIC cards running 64-bit GPLs, and all other types of EPAP-based SCCP cards, including SMxG cards and SLIC cards running 32-bit GPLs, are either inhibited or deleted from the EAGLE. Once turned ON, it is not possible to turn OFF the option manually.

Note:

Turning on the EPAPX DB Expansion feature allows the 480M data to be provisioned and the DN block capacity will be 400k.

Execute these steps to activate the EPAPX DB Expansion feature.

1. If EAGLE is currently configured with these parameters, then the SM cards need to be re-configured to use the EPAP Data Split feature with at least one SM card data=DN and at least one SM card data=IMSI by using the chg-card command.
   • EPAP Split DB Feature is ON, and
   • STPOPTS:EPAP240M is ON, and
   • SM cards are configured with data=EPAP, and
   • RTDB size is > 480M (calculated by summing the DN/IMSI/IMEI data counts in the RTDB:View RTDB Status from the EPAP's GUI)
2. If the EPAP is configured as a Mixed EPAP, then convert the EPAPs to a Standalone PDB EPAP and non-Provisioning EPAPs configuration. Refer to the Standalone PDB EPAP Configuration Procedure in the EPAP Administration Guide.
3. Back up the EAGLE database using the instructions found in the Database Administration – System Management User’s Guide.
4. Use the chg-stpopts:on=epapx command to turn ON the functionality for the EPAPX DB Expansion feature.
5. Use the rtrv-stpopts command to check the current status of the STPOPTS EPAPX option.
6. Change the EPAP’s database architecture to eXtreme. Refer to the EPAP Upgrade/Installation Guide for detailed instructions.
7. Boot EAGLE’s SM card to load the EPAP database using the new EPAPX schema.