Table of Contents
Advertisement
Page 168 of 220 Maintenance
Handling Meridian Companion exceptions
Config warning: Recoverable inconsistency
553-3601-200 Standard 7.00 November 1998
OK
h. Press
. The display shows Code 2: . Enter the second code
number.
OK
i. Press
. The display shows Code 3: . Enter the third code number.
OK
j. Press
. This will restore the system to its previous SSN.
6.
If you have Companion Manager installed and have previously
performed a system backup, perform a restore operation. If not, proceed
with the following steps.
7.
Repeat steps 5e to 5i for each code recorded in Meridian Companion
Programming and Provisioning Record.
8.
Verify that the correct number of Portable Credits and Radio Credits is
available (see "Verifying Portable Credits" on page 122).
9.
Reenter all programming data.
10.
Reregister all portables.
An exception during system initialization or operation can disable the system,
except for the Administration Terminal, dropping all calls. As the system
enters a disabled state, the Administration Terminal displays an exception
message, preempting any existing alarm message.
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.
A recoverable inconsistency occurs only during system startup after system
cards have been relocated (moved as a group without changing relative card
Advertisement
Table of Contents
Troubleshooting
