![Previous Topic: How to Edit empire.asn1 for Extension Variables](574.png)
![Next Topic: Recommendations for Using Extensions](573.png)
CA SystemEDGE User Guide › Custom MIB Objects › Using Extension Variables with Your Management Software › How to Edit a Separate MIB Specification for Extension Variables
How to Edit a Separate MIB Specification for Extension Variables
You can put extension variables in a separate MIB specification file for ease of updating. You can save time and effort by making changes to a MIB specification file, which is much smaller than empire.asn1, thereby avoiding recompiling and reloading the entire empire.asn1 file.
To add your extension variables to a separate MIB specification file
- Create and debug the relevant extension scripts, and configure them in the agent's configuration file, sysedge.cf, to include them.
- Edit your own MIB specification file (for example, extensions.asn1) to include new extension MIB variables that exist under the Systems Management Extension group.
- Perform a test compile of extensions.asn1 to check that there are no syntax errors. This procedure is specific to your management system and MIB compiler.
- Import the extensions.asn1 file into your management software. This procedure is specific to your management system and MIB compiler.
Note: If you do not reimport the MIB file, your management system software will not be able to access the new extension MIB objects.
Copyright © 2013 CA.
All rights reserved.
![Previous Topic: How to Edit empire.asn1 for Extension Variables](574.png) ![Next Topic: Recommendations for Using Extensions](573.png)
|
|