![Previous Topic: How to Edit empire.asn1 for ntRegPerf Variables](574.png)
![Next Topic: SystemEDGE AIMs](573.png)
CA SystemEDGE User Guide › Windows Registry and Performance MIB Objects › Using Windows Registry and Performance Variables with Your Management Software › How to Add a Separate MIB Specification for ntRegPerf Variables
How to Add a Separate MIB Specification for ntRegPerf Variables
You can put ntRegPerf variables in a separate MIB specification file to avoid directly manipulating the MIB file. You can save time and effort by making changes to a MIB specification file, which is much smaller than empire.asn1. This avoids recompiling and reloading the entire empire.asn1 file.
To add a separate MIB specifications for ntRegPerf variables, complete the following process:
- Edit your own MIB specification file (for example, ntregperf.asn1) to include the new ntRegPerf MIB variables that exist under the Systems Management Empire MIB ntregperfGroup.
- Perform a test compile of the ntregperf.asn1 file to make sure there are no syntax errors. This procedure is specific to your management system and its corresponding MIB compiler.
- Import the ntregperf.asn1 file to your management system software. This procedure is specific to your network management station and its corresponding MIB compiler.
Note: If you do not reimport the MIB file, your management system software will not be able to access the new MIB objects.
Copyright © 2013 CA.
All rights reserved.
![Previous Topic: How to Edit empire.asn1 for ntRegPerf Variables](574.png) ![Next Topic: SystemEDGE AIMs](573.png)
|
|