...
...
...
...
| Table of Contents |
|---|
1. Overview
In this tutorial, we will walk you through creating a new model for a device to be supported on NMIS 8 and to add new metric.
...
| Warning | ||||
|---|---|---|---|---|
| ||||
Opmantek VM has SNMPv2c enabled by default, the community used on this VM is: nmisGig8 This can be verified on the snmp configuration file that can be found in /etc/snmpd/snmpd.conf |
...
We will need to have all the necessary standard (IETF/IEEE) MIBs and the vendor specific MIBs for the device to be modelled, once we have the MIBs the best way to interpret the MIBs is to complete an SNMP WALK of the device, first verify that you can use SNMP to access the device see the following article: Testing SNMP Connectivity from the NMIS Server with snmpwalk.
This time we will be using the Opmantek VM to monitor the devices but also, for simplicity, it will be used in this tutorial as the device to be modelled, so it will be having 2 roles, by default the NMIS Server is monitored itself and can be found as the localhost device.
...
As you may have notice already, there are many devices that uses the same agents, in this example Linux Servers uses NET-SNMP, but Net-SNMP is available for many Unix and Unix-like operating systems and also for Microsoft Windows.
| Info |
|---|
Tip: Many devices now uses NET-SNMP as Agent, most of the time, it’s a good idea to copy an existing model and tailor it to our needs instead of creating a new one. |
...