Select Page

vCenter Operations Manager – Import custom MIBs for SNMP monitoring

vCenter Operations Manager – Import custom MIBs for SNMP monitoring

In order to property utilize the SNMP adapter within vCOps, it’s best to import manufacturer specific MIBs in order to pull proper information from the device. By default, vCOps includes many default, RFC compliant MIBs to utilize, however, they may not be as specific as you’d like. Most manaufacturers provide the ability to download MIBs for your device, therefore, that’s where we should start. For this example, we’ll be showing you how import MIBs for a Synology NAS appliance.

1) Download MIBs from manufacturer.






2) Using an application like WinSCP, connect to the Analytics VM using the local credentials (root/password). On the right (remote) section, browse to /usr/lib/vmware-vcops/user/plugins/inbound/snmp_adapter3/conf/mibs and copy the MIBs from your local machine to this folder. I also changed the rights and ownership to match the other MIB files within the same folder.

copy MIBs


3) Next you’ll need to connect to your Analytics VM via Putty. Again, use the local credentials (root/password). Now you’ll need to run the ‘’ script found in the “/usr/lib/vmware-vcops/user/plugins/inbound/snmp_adapter3/conf ” folder. This script will update the mib.imports.props file found in the same folder as the mib files. This file keeps track of all MIB file dependencies. To do so, type:


If you get the following Permission denied error, run the command “chmod u+x” to give your account executable permissions. Then try the command again.

-bash: /usr/lib/vmware-vcops/user/plugins/inbound/snmp_adapter3/conf/ Permission denied


4) Next we need to check the error log for any problems. The log file, mib-import.log, can be found in the same folder as the script we just ran. To view the log, type: “cat mib-import.log”. You can see that the file now includes the Synology MIBs that we copied into the MIB file in step 2. The end of the file also displays the location of the prop file in which it updated.

view log file


5) The next step is to modify the describe.xml file in a text editor and manually increase the version number. If the version number is, for example, “6”, we’ll need to change it to “7”. To open the file in a text editor, use the following command: vi describe.xml

Use the arrow keys to navagate to the 5. Press the ‘Insert’ button on the keyboard and modify the 5 from a 6. Press ESC to get out of Insert mode. To save the file, type “:w”. The quit the text editor, type “:q”. At this point you can verify the change by using “cat describe.xml” and viewing the file to ensure that the version number was successfully changed.

change to 6


6) The last step (finally) is to redescribe the SNMP adapter. This is done within the Custom UI under the Admin > Support page. Click the Info tab and click the Describe icon in the top right of Adapters Info section.



7) Verify that the Describe Version for the SNMP Adapter was incremented to the value you changed it to in step 5. It’ll take about 5 minutes and the Adapters Info page should update automatically. You should now be able to select the Synology MIB when creating a new resource within vCOps. Navagiate to Environments > Environment Overview. Click Add Resource and modify the fields as shown below (you may need to create a new adapter instance and credential if you haven’t yet). Finally, you should now see the Synology MIBs under the Resource Kind list.














About The Author

Bryan Krausen

Bryan Krausen is currently working as a Sr. Solutions Architect with experience in a vast number of platforms, specializing in AWS and HashiCorp tools.

Leave a reply

Your email address will not be published.