| Bug #33621 | SNMPv2-SMI-v1 should be replaced with SNMPv2-SMI in MNMAS.MIB imports | ||
|---|---|---|---|
| Submitted: | 2 Jan 2008 11:41 | Modified: | 11 Jan 2008 2:14 |
| Reporter: | Domas Mituzas | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Server | Severity: | S3 (Non-critical) |
| Version: | 1.2.x | OS: | Any |
| Assigned to: | Sloan Childers | CPU Architecture: | Any |
[2 Jan 2008 22:43]
Sloan Childers
r8692 development-1.2.1
[11 Jan 2008 2:14]
Bill Weber
verified fixed in build 1.3.0.8671
Description: as SNMPv2-SMI-v1 MIB is not common (at least not on default linux net-snmp packages), it might be better to use generic SNMPv2-SMI MIB import: MYSQLTRAP-MIB DEFINITIONS ::= BEGIN IMPORTS enterprises FROM SNMPv2-SMI-v1; How to repeat: snmptrapd -M ... -m +MYSQLTRAP-MIB would yield 'unknown MIB' error for SNMPv2-SMI-v1, whereas it is happy with SNMPv2-SMI import Suggested fix: I might be wrong at this, so please correct me if it is so. :)