When mapping customized MIBs, an error is thrown:
"The objects in this MIB cannot be mapped to consistent Attribute IDs across all SpectroSERVERs in your environment due to conflicts with existing attribute IDs."
When adding any new OID to Spectrum (using either Model Type Editor or MIBTools), this should be done on the MLS server. MIBTools can then synchronize across all landscapes in a DSS environment.
This error indicates that the modelling catalogs on the various SpectroSERVERs in the distributed environment are not in 100% synchronization, possibly due to custom OID/attribute additions being made on non-MLS landscapes. Consequently, when trying to compile the MIB in MIBTools, it is trying to create new attributes to associate to the new OIDs, but when MIBTools pushes out the new attributes to other SpectroSERVERs, these attribute IDs are already being used, hence the conflict and error thrown.
To resolve this, you need to manually bring the catalogs of all the landscapes back in sync. You can do this as follows:
Please reference "Master Catalog" solution discussed in knowledge article 121348 "How to propagate catalog changes in a Distributed SpectroSERVER environment" for more information.