"No event format file exists" seen in the Spectrum OneClick Events tab

Products

• Spectrum
• Network Observability

Issue/Introduction

The following is seen in the Events tab of the OneClick console:

An event occurred for model 'modelname' of type 'modeltype' for which no event format file exists. (event [0xffffffff])

No Associated Text

Cause

As the event states, Spectrum cannot find an Event Format file for the event specified. In the above example, the event is 0xffffffff.

This is most commonly seen when creating custom events in the Event Configuration editor and there are multiple OneClick servers in the Spectrum environment.

When the event is created and saved in the OneClick Event Configuration editor, a copy of the Event Format file will be placed in the $SPECROOT/custom/Events/CsEvFormat directory on the OneClick system where the OneClick console is launched. However, if there are other OneClick systems in the Spectrum environment, this event will NOT be copied to the $SPECROOT/custom/Events/CsEvFormat directory on those OneClick systems.

Resolution

Manually copy the associated Event Format file from the $SPECROOT/custom/Events/CsEvFormat directory of the OneClick server that you used to create the events (in the Event Configuration Manager) to the $SPECROOT/custom/Events/CsEvFormat directory on the server missing the files.  You can use any file transfer utility such as SCP or rsync.  Make sure the copied files (on the host you copied to) have the correct permissions as file ownership could change.

Once the files have  update the event configuration in OneClick:

1. Log into the OneClick web pages as an ADMIN user

2. Click on the Administration link

3. Click on the Update Event and Alarm Files link

4. Click on the Reload button

Then log out of the OneClick console and log back in.

Additional Information

You may also need to copy the alarm files in the $SPECROOT/custom/Events/CsPCause directory to the other OneClick host.

When using the Event Configuration Editor the files are copied to all SpectroSERVERs no matter which OneClick you create them on.  Ideally the MLS would have all events needed so you can copy the CsEvFormat and CsPCAuse files from the MLS to all OneClicks.

This message can also be seen on a Spectrum system running an AlarmNotifier process. As in the OneClick system, copy the associated Event Format file from the $SPECROOT/custom/Events/CsEvFormat directory of the OneClick server in the environment to the $SPECROOT/custom/Events/CsEvFormat directory on the server missing the file.

 

It is a good practice to manage your events from a dedicated MLS server in order to reduce the risk for lost events during synchronization from copying the events from other OneClick servers.  It is recommended to run the getSpectrumInfo.sh script before making any changes.