Value in parent OID

2013-04-17 Thread Fredrik Björk
Hi! Is it "legal" to have a value assigned to an OID that has a child like this: .1.3.6.1.3.123.1 = Integer 1 .1.3.6.1.3.123.1.2 = Integer 1 or is there a rule saying that a parent (.1.3.6.1.3.123.1 in this case) cannot have a value? We base an extension on this, but another piece of softwar

disable MIB parsing

2013-04-17 Thread Stuart Kendrick
Is there a CLI way to disable MIB parsing? Most of them time, I want 'snmpget' to load my MIB file collection because I'm handing it Object Values ... but occasionally, I don't ... I just want it to take the OID I'm handing it and issue the GET: snmpget -c public sample-host .1.3.6.1.4.1.9.9.9

SNMPv3 installation - need to also allow SNMPv1 readers

2013-04-17 Thread Chris Bartram
I have a working SNMPv3 installation (NET-SNMP version 5.3.2.2 on RHEL5:) but find we must also allow SNMPv1 gets from another tool (Dell OpenManage Essentials) which doesn't support SNMPv3. Below is what Dell recommends using in the standard snmpd.conf file; I tried adding this to my existin

Re: disable MIB parsing

2013-04-17 Thread Fredrik Björk
Hi! Of course it is possible... snmpbulkwalk -v 2c -c public 172.19.13.13 -m "" -m tells the snmp command where to look for MIB files and -m "" tells it to look nowhere! /Fredrik On 2013-04-18 00:30, Stuart Kendrick wrote: > Is there a CLI way to disable MIB parsing? > > Most of them time, I

Re: SNMPv3 installation - need to also allow SNMPv1 readers

2013-04-17 Thread Fredrik Björk
Hi! First of all the obvious: is the manager REALLY coming from IP 192.168.1.50 when the packets hit the RHEL box? No NAT in between? No dual NICs or IPs? Just to make sure: tcpdump -nnvv -c 10 port 161 Then try to access the RHEL box with SNMP from the manager. If source IP is really 192.1