Re: [Devmon] Issue with NetApp Filers.

[Buchan M. <bg...@st...>]

On Tuesday 12 February 2008 17:20:55 Lor...@pf... wrote:
> Guys,
>
> I'm running Devmon version 0.3.0-beta2 on an old RH 7.3 box with
> BigBrother 1.9c to monitor three routers and two NetApp filers (viking and
> gemini).
>
> Everything seems to be discovered fine:
>
> [bb@genesis devmon]$ ./devmon -vv -f --readbbhosts
> [08-02-12@15:00:32] SNMP querying all hosts in bb-hosts file, please
> wait...
> [08-02-12@15:00:33] Querying new hosts using cid 'xxxxxxxx' and snmp v2
> [08-02-12@15:00:43] ERROR: snmpget viking (no response received)
> [08-02-12@15:00:43] ERROR: snmpget gemini (no response received)
> [08-02-12@15:00:43] Discovered router1-a01 as a cisco 2800
> [08-02-12@15:00:43] Discovered router2-a02 as a cisco 2800
> [08-02-12@15:00:43] Discovered router3-int as a cisco 2600
> [08-02-12@15:00:43] Querying new hosts using cid 'private' and snmp v2
> [08-02-12@15:00:53] ERROR: snmpget gemini (no response received)
> [08-02-12@15:00:53] ERROR: snmpget viking (no response received)
> [08-02-12@15:00:53] Querying new hosts using cid 'xxxxxxxx' and snmp v1
> [08-02-12@15:00:53] Discovered gemini as a NetApp NetApp
> [08-02-12@15:00:53] Discovered viking as a NetApp NetApp
> [bb@genesis devmon]
>
> In the BB page though, the routers show up correctly, but the Filer tests
> from devmon all show the black dot.
>
> the devmon.log file shows the following:
>
> [08-02-12@15:14:17] Missing repeater data for ifDescr for if_load msg
> [08-02-12@15:15:16] No SNMP data found for qrVType on gemini

[...]

> [08-02-12@15:16:16] No SNMP data found for ifOutOctets on viking
> [08-02-12@15:16:16] No SNMP data found for ifDescr on viking
> [08-02-12@15:16:16] No SNMP data found for ifInOctets on viking
> [08-02-12@15:16:16] No SNMP data found for ifBps on viking
> [08-02-12@15:16:16] Missing repeater data for ifDescr for if_load msg

Are you able to walk the OIDs in question ? E.g.:

snmpwalk -v1 -c xxxxxx viking 1.3.6.1.2.1.2.2.1.2

If you can, you may want to try upgrading to the 0.3.0-rc1 release, a similar 
issue affecting Cisco ASA/PIXs was fixed by Francois.

Regards,
Buchan