...
In the last column, the MIB name can be defined. The MIB name parts must be equal to the parts of the OID – the parts are separated by “.”. E.g. if there is an auto generated OID (OID is left empty), the MIB name is a single entry (e.g. sensor1). If the OID suffix is 1.10, the MIB name must contain two parts. E.g. device1.sensor1).
Note |
---|
Keep in mind that the MIB names must be consistent and unique. Check the server logs for warnings or errors after loading the configuration. |
The Core Server automatically generates an MIB file. This file can be give to the SNMP clients to show the correct names. The location of the MIB file is:
Code Block |
---|
<WorkspaceFolder>\LogFiles\NETx.mib |
An example
Consider the following SNMP mapping definitions:
...
The OID of the first data point is generated automatically. Assuming that the default base OID is used, the full OID of definition 1 is 1.3.6.1.4.1.58651.1. The MIB name is iso(1).identified-organization(3).dod(6).internet(1).private(4).enterprise(1).netxautomation(58651).sensor1(1).
The second data point uses a specific OID suffix. Assuming that the default base OID is used, the full OID of definition 2 is 1.3.6.1.4.1.58651.2.1 The MIB name is iso(1).identified-organization(3).dod(6).internet(1).private(4).enterprise(1).netxautomation(58651).device1(2).value1(1)
Note |
---|
Note that a suffix of 1.10 for definition is not valid. This would result in an OID of 1.3.6.1.4.1.58651.1.1 which is not allowed since the first definition already uses 1.3.6.1.4.1.58651.1. |
The result MIB file looks as follows:
Code Block |
---|
-- NETx MIB 1.00
--
NETX-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter64, Counter32, Gauge32, TimeTicks, IpAddress, enterprises FROM SNMPv2-SMI
OBJECT-GROUP FROM SNMPv2-CONF;
netx MODULE-IDENTITY
LAST-UPDATED "202207120101Z"
ORGANIZATION "NETxAutomation"
CONTACT-INFO
"www.netxautomation.com"
DESCRIPTION
"The MIB module for NETx BMS Platform / NETx MP Server"
::= { netxautomation 3 }
--
-- Node Definitions
--
netxautomation OBJECT IDENTIFIER ::= { enterprises 58651 }
netxGroup OBJECT-GROUP
OBJECTS { sensor1,value1 }
STATUS current
DESCRIPTION
"NETx Group"
::= { netxautomation 4 }
sensor1 OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Variable 1 (Numeric)"
::= { netxautomation 1 }
device1 OBJECT IDENTIFIER ::= { netxautomation 2 }
value1 OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Variable 2 (Numeric)"
::= { device1 10 }
END |