User`s guide

335
The second MIB is the “Monitor MIB” which is a standard MIB that gives access to various
Digi TransPort proprietary objects. The OIDs in this MIB do not change with every release
although it is possible for new objects to be added to it. This MIB is available from the
Technical Support team.
The standard MIBs supported are:
• SNMP MIB (RFC3418)
• Interfaces MIB (RFC2233)
*
• IP MIB (RFC2011)
• IP Forwarding Table MIB (RFC2096)
• TCP MIB (RFC2012)
• UDP MIB (RFC2013)
• VRRP MIB (RFC2787)
• SNMP MPD MIB (RFC3412)
• SNMP USM MIB (RFC3414)
**
* The following groups/tables in RFC2233 are not supported: ifXTable, ifStackTable,
ifRcvAddressTable.
** The following groups/tables in RFC3414 are not supported: usmUserTable.
Other MIBs may be available on request.
Enable SNMPv1
Ticking this checkbox enables support for version 1 of the protocol.
Enable SNMPv2c
Ticking this checkbox enables support for version 2c of the protocol.
Enable SNMPv3
Ticking this checkbox enables support for version 3 of the protocol.
Use UDP Port n
This is the UDP port number to use. The default is UDP port 161.
SNMPv3 Engine ID
This is required as part of the SNMP v3 protocol. This is a 24 hexadecimal character string;
any trailing zeroes in this string making the value up to 24 characters can be omitted. A
remote engine ID is required when a SNMP v3 Inform is configured. The remote engine ID is
used to compute the security digest for authenticating and encrypting packets sent to a user
on the remote host.
Related CLI Commands
Entity
Instance
Parameter
Values
Equivalent Web Parameter
snmp n v1enable 0,1
Enable SNMPv1
0 = Off
1 = On
snmp n v2cenable 0,1
Enable SNMPv2c
0 = Off
1 = On
snmp n v3enable 0,1
Enable SNMPv3
0 = Off