We are seeing trap conflicts in Spectrum MIB Tools.
In the above example, notice the event code for the cefcFanTrayStatusChange trap is 0x00210c29 for the 0x1000000 landscape but it is 0x04dc000f for all other landscapes.
How can we resolve this conflict.
From the above example, the event code for the cefcFanTrayStatusChange trap is 0x00210c29 for the 0x1000000 landscape which is the "out of the box" event code for this trap.
The 0x04dc000f event code is a custom event code for the same trap.
In this example, the customization was not done on the 0x1000000 landscape.
Release : Any
Component : Spectrum Events and Alarms
In this example, the customized 0x04dc000f event code needs to be duplicated on the 0x1000000 landscape.
The easiest way to accomplish this is to choose one landscape to be the "master" for customized traps and events. (Most likely the MLS system.)
When that is decided, copy the entire $SPECROOT/custom/Events directory from the "master" landscape to the $SPECROOT/custom/Events directory on ALL SpectroSERVER, OneClick and Spectrum Repot Manager (SRM) systems in the entire Spectrum environment.
Then, update the event configuration for all the primary SpectroSERVER systems by doing the following for each VNM model in the database:
1. Log into OneClick as an ADMIN user
2. Find a VNM model
3. Click on the Information tab in the Component Detail panel
4. Find and expand the SpectroSERVER Control subview
5. Click on the Update Event Configuration button
To update the OneClick and SRM systems, simply restart tomcat.
To update the secondary SpectroSERVER systems, run an online backup.
As a general rule of thumb, ALL SpectroSERVER, OneClick and SRM systems should contain the same information in the $SPECROOT/custom/Events directory to make it easier to administer and avoid these types of conflicts.