SpectroSERVER is out of default event codes

Products

• Spectrum
• Network Observability

Issue/Introduction

We have been configuring custom events and we're using 0xfff0ffff for a special case.

However, this apparently caused the default event codes to be exhausted. 

We have since readjusted the codes and now have the 0xfff0f000 to 0xfff0ffff unused.

However, Spectrum is still complaining that it is out of the default event codes.

How can this be reset?

Environment

All supported DX NetOps Spectrum releases

Cause

The custom event codes are not in sync on all landscapes.

Some instances were due to custom event code work performed on one landscape without replication to others. This can cause events to be out of sync.

Resolution

To resolve this we need to modify all landscapes so they have the same events.

Best practice is to ensure $SPECROOT/custom/Events directories are the same on all SS, OC and SRM systems in the environment. This includes all possible AlertMap and EventDisp files under that directory.

The file copying can be done manually as changes are made, or through a custom internal sync script.

Even though OC and SRM do not use EventDisp and AlertMap files, it is easier to manage if all systems have the same files.
 
Once all systems have the same files use these two options to ensure everything is updated all around with the custom file configs.

1. Navigate to the VNM model in the OC web UI.
   
   1. In the Information tab for the VNM model expand the SpectroSERVER Control section.
   2. Select the Update Event Configuration option.
2. In the OC admin web site go to:
   
   1. Administration -> "Update Event and Alarm Files"
   2. Select the Reload button.