4.18 alw-card
Use this command to change the card from OOS-MT-DSBLD (Out-of-Service-Maintenance-Disabled) to IS-NR (In-Service-Normal) if the loading is successful.
Parameters
- code (optional)
-
The GPL type to be loaded.
Note:
In case code is provided along with sloc and eloc parameters in the command, then code parameter's value is applied to all the cards within sloc-eloc range, including sloc and eloc.Caution:
Do not enter the pktgen or inactiveprtn values for this parameter unless instructed to do so by Oracle personnel.- Range:
-
- appr
- Downloads the approved GPL
- inactiveprtn
- Downloads the MASP with associated GPL from the inactive partition of the TDM. This value should be specified only during a software upgrade.
- pktgen
- Downloads the PKTGEN GPL for the
appropriate hardware type. This GPL is to be used only for engineering test
purposes and must not be used in customer installations without engineering
oversight.
Note:
After the PKTGEN GPL is initially downloaded to a card by this command, the PKTGEN GPL will continue to be downloaded to the card until anotheralw-card
command is issued. - trial
- Downloads the trial GPL
- Default:
- appr
- data (optional)
- High memory refresh. This parameter causes data to
be reloaded to the specified card.
Note:
Various conditions in the system may prevent the persistence of the data on the cards. In case data parameter is provided along with sloc and eloc parameters in the command, then data parameter's value is applied to all the cards within sloc-eloc range, including sloc and eloc.- Range:
-
- persist
- Indicates that the database is not to be reloaded to the card. This parameter is used to request that the EAGLE perform a warm restart of the requested cards. The EAGLE performs various checks to ensure that all conditions necessary to initiate the warm restart are in place. During the card initialization and loading sequence, a warm restart is performed if the card meets the warm restart conditions, as described in the Notes section of this command.
- refresh
- Causes data to be reloaded to the specified card.
- Default:
- refresh
- loc (optional)
- The card location as stenciled on the shelf of the
system.
- Range:
- 1101 - 1108, 1111 - 1113, 1115, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
alw-card:loc=2301:code=trial
alw-card:loc=1101:data=persist
alw-card:loc=1106:data=persist:perdata=gtt
Dependencies
The shelf and card must be equipped.
No other action command can be in progress when this command is entered.
An EPAP-based feature or an LNP feature that is warm-restart capable must be enabled; SIP or DEIR must be enabled, or at least one ENUM or one GTT-enabled IPSG card must be present before this command can be entered with the data=persist parameter.
The data parameter is valid only for SCCP card locations or GPLs, or MPS database (VSCCP) card locations or GPLs, or GTT-enabled IPSG card locations or GPLs.
The card location (loc) must be within the allowed range.
A card that is the active MASP cannot be specified for the loc/sloc/eloc parameter.
- Card location equipped with an E5-APP-B card cannot be specified.
- Card location equipped with a Telco Switch cannot be specified.
If an OAM card is installed in the location specified by the loc parameter, then only a value of inactiveprtn is supported for the code parameter.
The S13 EIR feature must be activated before allowing a card running the DEIRHC GPL.
The PERDATA parameter is valid only with the DATA parameter.
The SIP NP feature must be activated before allowing a card running the SIPHC GPL.
Notes
Installation Guide provides an illustration of card locations.
The system previously supported the data parameter for reloading GTT data. The system does not support persistent GTT data loading, and the data parameter is now used in support of a warm restart feature.
A number of reasons exist for not being able to warm restart. If none of these conditions exists, a warm restart is possible and will be attempted following a Service Module card reset.
- The following conditions require a full data reload:
- AUDIT FAILED—Checksum comparisons of the LNP database failed during card initialization. Data on the card is determined to be corrupted after the reset (was not yet detected by normal auditing).
- AUDIT TIMEOUT—LNP initialization audit timed out (software failure)
- DB LEVEL—Database level is not supported, or the difference exceeds incremental loading capability. This condition is caused by the reset of OAMs or if the number of updates exceeds the incremental loading capability.
- DB STATUS—Database status of the card is incoherent at the time of a reset. This condition can be caused by a failed network card update or a reset during a database update to the card.
- DB VERSION—LNP Database
version has changed from the previous version. An import, or bulk downloads
(
chg-db
), or changes from release to release may alter the database version. - HW ERROR—Hardware error bit checks on the card failed during card initialization
- NO AUDIT—Unable to perform an LNP audit. The LNP audit is not on (for example, LNP options has audit=off). This condition can occur if the rate of LNP updates exceeds the ability of the LNP audit to compute checksums (excessive unknown checksums). This condition is more likely on a small database where there are fewer checksums. The percentage of known checksums must be 99% or more. The percentage is based on the number of checksums in use, which is smaller for small databases (such as two million TNs or fewer).
- POWER ON—A power on reset (the card is pulled and reinserted)
- UNKNOWN/OTHER—Unknown or other type of software failure.
- USER REQUEST—User-initiated
init-card
orinit-sys
command reload type=cold. The default restart type for these commands is a cold or full LNP data reload. The user must specify data=persist for a warm restart on command. - XILINX VERSION—The M256 Xilinx program version has changed from the previous version.
- The following conditions require a cold restart for
the MCPM card:
- DB STATUS—Database status of the card is incoherent at the time of a reset. This condition can be caused by a failed network card update or a reset during a database update to the card.
- MEAS DB–Measurements database initialization failure or corruption.
- POWER ON—A power on reset (card is pulled and reinserted).
- UNKNOWN/OTHER—Unknown or other type of software failure.
- XILINX VERSION—D1G Xilinx program version has changed from previous version.
- The following conditions require a cold restart for
the GTT-enabled IPSG card:
- GTT DB LEVEL— GTT Database level is incoherent at the time of reset. This condition is caused by the reset of OAMs.
- GTT DB STATUS— GTT Database status of the card is incoherent at the time of a reset. This condition can be caused by a failed network card update or a reset during a database update to the card.
- POWER ON— A power on reset (the card is pulled and reinserted)
- UNKNOWN/OTHER— Unknown or other type of software failure.
- USER REQUEST— User-initiated init-card or init-sys command reload type=cold. The default restart type for these commands is a cold or full GTT data reload. The user must specify data=persist for a warm restart on command.
- XILINX VERSION— The SLIC Xilinx program version has changed from the previous version.
Caution:
This command can be used to enable Measurements Platform measurements collection after the collection function has been disabled with theinh-card
command for ALL MCPM cards in
the system. To enable collection, at least 1 MCPM card must be allowed in the
system. Disabling collection by inhibiting all MCPM cards CAN RESULT IN LOSING
ALL PAST MEASUREMENT DATA ON THE CARDS.
When the OA&M IP Security feature is turned on, and an IPSM card is inserted and initialized for the first time or is removed, inserted, and initialized again, the "SSH Host Keys Regenerated" UIM is displayed. The UIM shows the generated SSH Host Key fingerprint that must be provided at the secure client in order for secure information transfer to occur. The SSH Host Key fingerprint is changed whenever power is lost and restored to an IPSM card.
rlghncxa03 03-07-11 07:05:00 EST EAGLE 30.2.0
0021.1493 CARD 1111 INFO SSH Host Keys Regenerated
84 7c 92 8b c 7c ds 19 1c 6 4b de 5c 8f c5 4d
Report Date:03-07-11 Time:22:27:36
;
When the OA&M IP Security feature is turned on, and an IPSM card is restarted with this command, the "SSH Host Keys Loaded" UIM is displayed. The UIM shows the current SSH Host Key fingerprint. The SSH Host Key fingerprint is not changed if the IPSM card does not lose power.
rlghncxa03 03-07-11 07:05:00 EST EAGLE 30.2.0
0021.1493 CARD 1111 INFO SSH Host Keys Regenerated
DSA Server Host Key FTRA-formatted Fingerprint=
84 7c 92 8b c 7c ds 19 1c 6 4b de 5c 8f c5 4d
Report Date:03-07-11 Time:22:27:36
;
If a location for an E5-E1T1-B (type LIME1 or LIMT1), or E5-ATM-B (type LIMATM or LIME1ATM) card is specified, then at least one signaling link must be provisioned for the card before it can be allowed.
When SLOC and ELOC are given in the
alw-card
command, along with DATA and
PERDATA parameters, instead of displaying an MTT, a list of card locations will
be displayed pointing out the cards on which data was persisted and the cards
on which it wasn't.
Output
alw-card:loc=2301:code=trial
rlghncxa03w 06-06-01 11:11:28 EST EAGLE 35.0.0
Card has been allowed.
;
alw-card:sloc=1103:eloc=1106:data=persist:perdata=all
tekelecstp 16-09-08 17:58:00 EST EAGLE 46.5.0.0.0-70.4.0
Card 1103 – 1106 have been allowed.
LOC 1103 : ALLOW OPERATION COMPLETED.
LOC 1104 : ALLOW OPERATION COMPLETED: Data not persisted.
LOC 1105 : ALLOW OPERATION COMPLETED.
LOC 1106 : ALLOW OPERATION COMPLETED.