This is a tech doc describing how MIBs are added in a Distributed SpectroSERVER (DSS) environment and how the changes are propagated in that environment.
Adding MIBs to a SpectroSERVER can be considered a 2 step process:
1. Compiling and adding the MIB to the MIB Tools database.
2. Mapping MIB objects to an attribute with attributes stored in the SpectroSERVER database.
Therefore as a result the answer to this question will first define the 2 sections of this process and then describe how this is achieved in a DSS environment..
Release: Any version of Spectrum
Where and how are new MIBs added in Spectrum in a Distributed SpectroSERVER environment
Compiling and adding the MIB to the MIB Tools database:
When adding new MIBs using MIB tools utility the new MIBs are added to the MIB database not to the SpectroSERVER database.
The MIB database is maintained always on the same system where there is the corresponding OneClick server.
Mapping MIB objects to an attribute with attributes stored in the SSdb database:
After you have compiled and added MIBs to the MIB Tools database to add support for specific MIB objects the second part is to map these to attributes which is then stored in the SSdb database.
Adding support for new MIBs in a DSS environment:
In a DSS environment when adding support for MIB objects information is written to each SpectroSERVER in the DSS env.
However the information required by OneClick to support the traps and attributes is written only on the OneClick server on which you are working so if you have multiple OneClicks running in the DSS environment you need will need to ensure that these are kept in sync.
For further information on maintaining MIB tools and MIBs in sync across your DSS environment please refer to section:
MIB Tools Support for Multiple SpectroSERVERs
MIB Tools Synchronization in a DSS Environment
Create Consistent Support Across a DSS Environment
Synchronize and Update MIB Databases and Support Files on Multiple OneClick Servers