Go to primary content
Oracle® Communications EAGLE Commands Error Recovery Reference
Release 46.8
F11879 Revision 1
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

E2025 Cmd Rej: Invalid card location

For the act-lbp command, the value specified for the loc parameter must indicate an HC-MIM, E5-E1T1, or E5-E1T1-B card, provisioned with the LIMT1 card type, running the SS7ANSI or CCS7ITU application.

For the chg-db command, a value of 1113 or 1115 must be specified for the sloc parameter.

For the ent-card command, a type DSM card must be inserted into an odd-numbered card location. The n+1 slot next to the DSM card must be empty, where n is the odd-numbered location (for example, if the DSM is in location 1101, then the 1102 slot must be empty and not provisioned).

For the ent-trace command, values of 1113 - 1118 cannot be specified for the loc parameter.

For the rept-imt-lvl2 command, MUX card locations (xx09 and xx10), E5-TDM card slots 1114 and 1116, and E5-MDAL slots 1117 and 1118 cannot be specified as values for the loc, sloc, and eloc parameters.

For the rept-stat-gedti command, the value specified for the loc parameter must correspond to the location of an IPSM card that is configured as a GEDTI Hub.

For the rept-stat-j1 command, card location 1118 cannot be specified.

For the rept-stat-rtd command, the following card locations cannot be specified: 1114, 1116, 1117, 1118 (E5-TDM, E5-MDAL cards), and all xy09 and xy10 locations where x is the frame and y is the shelf (HMUX or HIPR MUX cards).

For the rtrv-data-rtdb command, the card location slot must be between 1 and 16 and not 9 or 10. The frame location must be 1xxx, 2xxx, 3xxx, 4xxx, 5xxx, or 6xxx. The shelf location must be 11xx, 12xx, 13xx, 21xx, 22xx, 23xx, 31xx, 32xx, 33xx, 41xx, 42xx, 43xx, 51xx, 52xx, 53xx, or 61xx.

For the tst-disk command, the card in the specified location must be an E5-TDM or an E5-MCAP card.

Recovery

Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.

Contact My Oracle Support if this error message appears again. See My Oracle Support (MOS).