Eagle5 STP - E2667 Cmd Rej: Same Power Source Of E5APPB Cards Running Same Application

Asset ID:	1-72-2386711.1
Update Date:	2018-04-16
Keywords:

Solution Type Problem Resolution Sure

Solution 2386711.1 : Eagle5 STP - E2667 Cmd Rej: Same Power Source Of E5APPB Cards Running Same Application

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 46.3 and later
Tekelec

Symptoms

Customer has 2 E5-APP-B cards defined with EPAP application. Upon definition of the 3rd card the command is rejected with error:

ent-card:loc=1317:type=e5appb:appl=epap:srvname=gflex
Command entered at terminal #21.
;

tekelecstp 18-04-03 21:52:39 PST EAGLE 46.3.0.0.2-68.28.0
ENT-CARD: MASP A - Command Aborted
;
E2667 Cmd Rej: Same Power source of E5APPB cards running same application

Changes

Cause

When we use the ent-card command in the Eagle STP for provisioning, certain limitations apply. For E5-APP-B cards (part number 870-3096-01) used with EPAP as application type, the maximum number of cards allowed in the database is 2. This specific limitation caused the system to return an error upon declaration of the third card.

More information about the system configuration and limitations can be found in our documentation: https://docs.oracle.com/cd/E76234_01/docs.463/E72170_rev_1.pdf (page 3196).

Solution

Check with the customer the purpose of the 3rd E5-APP-B card.

If the extra card is a stand-a-lone PDB for GFLEX the command can be forced.

The command rejection can be by-passed by using "force=yes" when declaring new board. In this case we can treat the error as a notification, the Eagle's way of confirming that if you continue with the declaration of a 3rd or 4th E5-APP-B card, it will be stand-alone systems.

Please configure the new card using the command:

ent-card:loc=1317:type=e5appb:appl=epap:srvname=gflex:force=yes

Attachments

This solution has no attachment