Installation guide

Maintenance Page 161 of 206
Meridian Companion Installation and Maintenance Guide
The three defined Meridian Companion abnormalities, listed below, relate to
configuration inconsistencies and are described in the sections that follow.
• Config warning: Recoverable inconsistency
• Config failure: Nonrecoverable inconsistency
• Config ambiguous
During a Meridian Companion exception, the feature key is disabled,
preventing you from entering a feature session. The only available actions are
RESET
and RESUME , as shown by the softkeys. They are described below.
Config warning: Recoverable inconsistency
A recoverable inconsistency occurs only during system startup after system
cards have been relocated (moved as a group without changing relative card
positions; see “Relocating the system” on page 151). It serves to remind the
installer that all WTNs must be reprogrammed from the Meridian 1 system
and that MDF cabling must be consistent with the new card locations.
The message Config Warning displays after initialization. If the
reprogramming and cabling have been performed correctly, you can press
RESUME
to tell the system to overwrite the old position information and
reactivate the system.
Otherwise, you must press
RESET . This triggers the installation procedure. A
warning message informs you that all data will be erased.
Config failure: Nonrecoverable inconsistency
A nonrecoverable inconsistency can occur during startup or during operation
when the system determines that the cards are in a different order from the
configuration stored in memory. Card type order has not been preserved,
making portable telephone registration data and system configuration data
invalid. This can occur if a previously programmed CMCC has been moved to
another Meridian 1 system with a different expansion card configuration, or if
an installer has replaced an existing CMLC with a CMRC to add Base Station
capacity.
The message Config Failure displays. There are two possible actions.
Note: If you press RESUME
without correcting the problem that triggered the
Config Failure (by returning cards to their old positions), the system