Use this Knowledge Script to add management information base (MIB) files, enabling you to convert trap object identifiers (OIDs) into object descriptive names (ODEs) to make monitored traps more readable with the SNMPTraps_TrapMonitor Knowledge Script. The MIB files should be ASN.1 text files with a .txt, .my, or .mib file extension, and not compiled MIB files.
Use this script to copy a MIB file from a location you specify to the MIB tree located in the netiq/AppManager/bin/MIBs folder. If you select Yes for the Reload MIB tree? parameter, you can also reload all MIBs in the tree without restarting the AppManager agent. A restart of the AppManager agent automatically reloads the MIB tree.
In This Scenario |
Set These Parameters |
---|---|
You want to add a MIB file to the MIB tree, but do not want the addition to take effect until after the next restart of the AppManager agent. |
Install additional MIB files?: Select Yes. Full path to MIB files and List of MIB files: Provide location and name of MIB file you want to add. Reload MIB tree?: Set to No (unselected). |
You manually copied a MIB file to the MIB directory and want to reload all MIBs in the directory. |
Install additional MIB files?: Set to No (unselected). Full path to MIB files and List of MIB files: Leave blank. Reload MIB tree?: Select Yes. MIB reload timeout: Set new timeout value or accept default of 10 seconds. |
Due to compiler errors, you edited some MIBs in the MIB directory. Now you want to reload the MIBs to ensure the errors have been fixed. |
Install additional MIB files?: Set to No (unselected). Full path to MIB files and List of MIB files: Leave blank. Reload MIB tree?: Select Yes. MIB reload timeout: Set new timeout value or accept default of 10 seconds. |
NT_MachineFolder
By default, this script runs once.
Set the Values tab parameters as needed.
Parameter |
How to Set It |
---|---|
General Settings |
|
Job Failure Notification |
|
Event severity if AddMIB job fails unexpectedly |
Set the event severity level, from 1 to 40, to reflect the importance when this script fails unexpectedly. The default is 5. |
Additional Settings |
|
Event Details |
|
Event detail format |
Select whether to view event details in an HTML table or in plain text. The default is HTML Table. |
Tracing (for advanced users only) |
Use the tracing settings in this section only with the help of NetIQ Technical Support. |
Raise event with job execution log? |
Select Yes to raise an event when the job execution log is created. The default is unselected. |
Logging level |
Select the logging level you want to monitor. The options are Off, Fatal, Error, Warn, Info, Debug, or All. Use these settings only with the help of Technical Support. The default is Warn. |
Derive event severity from most severe event log entry? |
Select Yes to calculate the event severity for the Raise event with job execution log parameter based on the most severe event log entry. The default is Yes. |
Event severity (if automatic severity computation not selected above) |
If you did not select Yes for the Derive event severity from most severe event log entry parameter, set the event severity level, from 1 to 40, to reflect the importance of the event raised with the creation of the job execution log. The default is 40. |
MIB Load Configuration Settings |
|
Raise event with the list of currently installed MIBs? |
Select Yes to raise an informational event that provides a list of all MIBs installed in the MIB tree. The default is Yes. |
Event severity for the list of currently installed MIBs |
Set the event severity level, from 1 to 40, to reflect the importance of an event that provides a list of all MIBs in the MIB tree. The default is 25. |
Install additional MIB files? |
Select Yes to install additional MIB files. The default is Yes. If you select Yes for this parameter, but do not enter any value for both the Full path to MIB files and the List of MIB files parameters, the script loads or reloads all MIB files in the NetIQ\AppManager\bin\MIBs folder. |
Raise event if installation of MIB files succeeds? |
Select Yes to raise an event if the installation of the MIB files succeeds. The default is Yes. |
Event severity when installation of MIB files succeeds |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the installation of the MIB files succeeds. The default is 25. |
Raise event if installation of MIB files fails? |
Select Yes to raise an event if the installation of the MIB files fails. The default is Yes. |
Event severity when installation of MIB files fails |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the installation of MIB files fails. The default is 10. |
Full path to MIB files |
Specify the full path to the folder that contains the MIB files you want to install. Place the file in a location that is accessible by the account under which the NetIQmc service is running on the agent. This script supports UNC shares if the agent’s parent account has authority to access the share. |
List of MIB files |
Provide a comma-separated list of the MIB files you want to install. The MIB files should not be compiled MIB files. The MIB files you specify must be located in the folder you identified in the Full path to MIB files parameter. |
Reload MIB tree? |
Select Yes to update the MIB tree. The default is Yes. |
Raise event if reloading of MIB tree succeeds? |
Select Yes to raise an event if the reloading of the MIB tree succeeds. The default is Yes. |
Event severity when reloading of MIB tree succeeds |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the reloading of the MIB tree succeeds. The default is 25. |
Raise event if reloading of MIB tree fails? |
Select Yes to raise an event if AppManager fails to reload the specified MIB files. The default is Yes. Failure scenarios include:
|
Event severity when reloading of MIB tree fails |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the reloading of the MIB tree fails. The default is 10. |
Raise event if reload MIB parser warnings received? |
Select Yes to raise an event if warning messages are received during the reload process. The default is Yes. A potential warning scenario could be if not all the specified MIB files were loaded to the MIB tree. |
Event severity when reload MIB parser warnings received |
Set the severity level, from 1 to 40, to indicate the importance of an event in which warning messages are received during the reload process. The default is 15. |
MIB reload timeout |
Specify the length of time AppManager should attempt to update the MIB tree before timing out and raising a failure event. The default is 10 seconds. |