Table of Contents
Advertisement
Page 190 of 220 Troubleshooting
Understanding event messages
Table 43 : Event messages in the Event/Alarm log
Event code
EVT221
EVT222
EVT299
EVT301-ccuux
EVT302-ccuux
EVT303-ccuux
EVT304-ccuux
553-3601-200 Standard 7.00 November 1998
Event messages appear as items in the Administration log or the Event/Alarm
log. Most of these event messages appear during normal maintenance. An
installer may view the event messages to diagnose a problem in the system.
Each event is assigned a severity number. An
S4
example,
), may appear in the event message.
the log is full, new event messages with a higher severity number replace
existing event messages of a lower severity. For this reason, check event
messages at regular intervals and deal with all messages.
The Event/Alarm log has been cleared.
The debugging facility has been accessed.
The system has been restarted after a power outage.
ccuux
Radio
cannot successfully receive the data image during
download.
Both radios belonging to the Base Station will be disabled. This may
occur if the flash EEPROM is faulty. The Base Station should be
replaced.
Radio ccuux cannot be written to during data transfer.
Both radios belonging to the Base Station will be disabled. The Base
Station's flash EEPROM is faulty. The Base Station should be replaced.
Radio ccuux cannot be synchronized with the other radios in the
system.
Both radios belonging to the Base Station will be disabled. The Base
Station hardware is faulty. The Base Station should be replaced. Two
events are raised: one for the B1 channel radio and another for the B2
channel radio. A corresponding alarm code 53 will occur
ccuux
Radio
cannot be synchronized with other radios because of
system overload.
S
preceding this number (for
S1
has the lowest priority. If
Meaning
Advertisement
Table of Contents
Troubleshooting
