Custom MIB Setup

The option exists to configure the SNMP Agent MIB to produce an OEM MIB rather than the standard VTSCADA MIB. The primary setting to enable this is:

SNMPAgentOEMSetup

This is a string of the form "enterprise(PEN).product(number)". (For example: "acme(696).rocketApp(1)").

The enterprise and PEN must match what is defined in the enterprise MIB file. After this setting is specified you must include the following to generate a functional MIB file:

SNMPAgentOEMEnterpriseMIBModule

Enterprise MIB module name for exported MIB file (e.g. "ACME-MIB"). Must match the enterprise MIB file module declaration.

SNMPAgentOEMProductMIBModule

Product MIB module name for exported MIB file (e.g. "ROCKET-APP-MIB")

The MIB subsystem will create a custom MIB based on these settings. Note that the enterprise MIB file will have to be supplied to the end user in order for the custom product MIB to be of use. However, the VTScada SNMP Agent does not need the actual enterprise MIB module to function.

The header of the generated MIB file will contain the following fields. Definitions for these are optional.

SNMPAgentOEMOrganization

(string) Organization for exported MIB file

SNMPAgentOEMContactInfo

(string) Contact Information for exported MIB file

SNMPAgentOEMDescription

(string) Product description for exported MIB file

In order for the custom parameters to be SMIv2 compliant, the following rules must be observed,

  1. MIB Module names:
  • Must begin with UPPER case letter, followed by zero or more letters, digits, and hyphens
  • Hyphen cannot be last, and there cannot be two consecutive hyphens
  1. SNMPAgentOEMProduct setting names:
  • Must begin with LOWER case letter, followed by zero or more letters and digits
  • Have no hyphens