[racktables-users] Re: snmpget problem occurred again
- From: Roy de Jager <roy.dejager@xxxxxxxx>
- To: racktables-users@xxxxxxxxxxxxx
- Date: Tue, 20 Jan 2009 12:42:26 +0100
It looks like i have the same problemen with SNMP.
Running racktables on windows xp machine with xampp installed.
With kind regards,
Roy
Killsystem
<killsystem@toolsec
tion.info> To
Sent by: racktables-users@xxxxxxxxxxxxx
racktables-users-bo cc
unce@xxxxxxxxxxxxx
Subject
[racktables-users] snmpget problem
20-01-2009 12:10 PM occurred again
Please respond to
racktables-users@fr
eelists.org
HI,
seems that this bug is again in the latest version 0.16.6
If this is intentionally than please let me know that I can change it in
the upgrade process myself.
gretz Killsystem
On Mon, 10 Nov 2008 17:25:07 +0100, Killsystem
<killsystem@xxxxxxxxxxxxxxxx> wrote:
> Hi today I found a bug with this patch of mine.
>
> If the switch does not support the OID you get an error message like this
> one:
>
> Warning: snmpget() [function.snmpget]: Error in packet: (noSuchName)
There
> is no such variable name in this MIB. in /var/www/racktables/inc/snmp.php
> on line 96
> Warning: snmpget() [function.snmpget]: This name does not exist:
> SNMPv2-SMI::enterprises.9.3.6.3.0 in /var/www/racktables/inc/snmp.php on
> line 96
> Warning: Cannot modify header information - headers already sent by
(output
> started at /var/www/racktables/inc/snmp.php:96) in
> /var/www/racktables/process.php on line 30
>
> Easy enough to fix
> Instead of using
> $sysChassi = snmpget ($endpoints[0], $community,
'1.3.6.1.4.1.9.3.6.3.0');
> just use
> $sysChassi = snmp2_get ($endpoints[0], $community,
> '1.3.6.1.4.1.9.3.6.3.0');
>
> Seems to be some problem with the snmpget function.
>
> gretz Killsystem
----------------------------------------------------------------
DISCLAIMER:
This e-mail and any attachments is intended solely for the use of the
individual addressee(s), and may not be passed on to, or made available for use
by any person. If you are not the intended recipient or reader, you are kindly
requested to notify the sender by replying to this message, and then delete it
from your system. Members of the Tauw-group are neither liable for the proper
and complete transmission of the information contained in this communication,
nor for any delay in its receipt. Any e-mail messages from members of the
Tauw-group shall not be binding nor be construed as constituting any obligation
on the part of members of the Tauw-group.
Other related posts: