Re: problems while querying an HP blade enclosure

2011-11-02 Thread Daniel Sanabria
Guys, Thanks a million !!! Today's issue about not getting a reply after replacing the dashes was down to a network problem (access issues in a way). All your comments helped me with the troubleshooting. I might come back to this list when trying to use SET commands but once I played a bit more

Re: problems while querying an HP blade enclosure

2011-11-02 Thread Dave Shield
On 2 November 2011 09:33, Daniel Sanabria wrote: > What does it mean the fact that the enclosure is not replying when I'm > querying the enterprise OID? Typically access control. Is the enclosure configured to respond to this community string? What happens if you query the 'system' group with th

Re: problems while querying an HP blade enclosure

2011-11-02 Thread Daniel Sanabria
Thanks again, I certainly missed those dashes ... Now however, I get no response at all from the remote end (the Blade Enclosure OA). [root@admin ~]# snmpwalk -v1 -c ammeon -t 60 10.44.84.33 1.3.6.1.4.1.232.22 Timeout: No Response from 10.44.84.33 [root@admin ~]# I'm new to snmp and net-snmp so

Re: problems while querying an HP blade enclosure

2011-11-02 Thread anand anand
Hi, The problem is in the command "snmpwalk –v1 –c ammeon 10.44.84.33 1.3.6.1.4.1.232". I have marked them in red. It should be " snmpwalk -v1 -c ammeon 10.44.84.33 1.3.6.1.4.1.232". Not the Dashes before the version and community options. Thanks -anand On Wed, Nov 2, 2011 at 3:52 AM, Danie

Re: problems while querying an HP blade enclosure

2011-11-01 Thread Daniel Sanabria
Thanks for replying, I'm getting this when doing snmpwalk using the enterprise oid [root@admin ~]# snmpwalk –v1 –c ammeon 10.44.84.33 1.3.6.1.4.1.232 –c: Unknown Object Identifier (Sub-id not found: (top) -> –c) [root@admin ~]# Where is the problem? is it in the target (blade enclosure) or the h

RE: problems while querying an HP blade enclosure

2011-11-01 Thread Alexandre James
I believe if you don't pass an oid to snmp walk it will only want the mib-2 tree (1.3.6.1.2) where the CPQRACK-MIB is an enterprise mib so it's under the enterprise tree (1.3.6.1.4.1). More specifically, if do something link the following, you should only get the contents of the CPQRACK-MIB: sn