Troubleshooting Page 179 of 206Meridian Companion Installation and Maintenance GuideUnderstanding event messagesEvent messages appear as items in the Administration log or the Event/Alarmlog. Most of these event messages appear during normal maintenance. Aninstaller may view the event messages to diagnose a problem in the system.Each event is assigned a severity number. An S preceding this number (forexample, S4), may appear in the event message. S1 has the lowest priority. Ifthe log is full, new event messages with a higher severity number replaceexisting event messages of a lower severity. For this reason, check eventmessages at regular intervals and deal with all messages.Table 42 : Event messages in the Event/Alarm logEvent code MeaningEVT221 The Event/Alarm log has been cleared.EVT222 The debugging facility has been accessed.EVT299 The system has been restarted after a power outage.EVT301-ccuux Radio ccuux cannot successfully receive the data image duringdownload.Both radios belonging to the Base Station will be disabled. This mayoccur if the flash EEPROM is faulty. The Base Station should bereplaced.EVT302-ccuux Radio ccuux cannot be written to during data transfer.Both radios belonging to the Base Station will be disabled. The BaseStation’s flash EEPROM is faulty. The Base Station should be replaced.EVT303-ccuux Radio ccuux cannot be synchronized with the other radios in thesystem.Both radios belonging to the Base Station will be disabled. The BaseStation hardware is faulty. The Base Station should be replaced. Twoevents are raised: one for the B1 channel radio and another for the B2channel radio. A corresponding alarm code 53 will occurEVT304-ccuux Radio ccuux cannot be synchronized with other radios because ofsystem overload.
