Re: net-snmp compilation problem still unresolved

Group <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
Hi Bart,

Thanks for the command. I could see the debug messages now.
I have added a new MIB. To add those objects to snmpd.
Do i need to do configure again?. Is there any other way to do this.
Please let me know.

On Sun, May 9, 2010 at 7:11 AM, Bart Van Assche <[email protected]> wrote:

> On Sat, May 8, 2010 at 10:25 PM, Group <[email protected]> wrote:
>
>> My Configuration:
>>
>> net-snmp version: net-snmp-5.4.2.1
>> environment: cygwin
>> operating system: windows XP
>>
>>
>> Now i would like to run the snmp agent on windows.
>>
>> I created a snmpd.conf file in /usr/local/share/snmp
>> with following entry:
>>
>> rocommunity  private
>>
>> When i tried to do a snmpget i'm getting the following error.
>> $ snmpget -c private localhost sysUpTime
>> Timeout: No Response from localhost.
>>
>
> I assume that sysUpTime should have been sysUpTime.0 ? Anyway, the timeout
> error message means that there is either a network problem, a problem with
> the configuration of snmpd or that snmpd was not running.
>
>
>> and when i do a snmpget for netSnmpExampleInteger, i'm getting the
>> following error: (i have compiled this by
>> including in ./configure ... -with-mib-modules"examples/
>> static_int")
>> $ snmpget -c private localhost netSnmpExampleInteger.0
>> netSnmpExampleInteger.0: Unknown Object Identifier (Sub-id not found:
>> (top) -> netSnmpExampleInteger
>> )
>>
>> I'm not sure whether snmp agent is running or not. How can i check this.
>> I make sure that snmp port is not blocked (I allowed UDP port 161 in
>> firewall settings).
>>
>
> You can debug the access control setup of snmpd together with the network
> setup as follows:
> * Start snmpd with packet tracing enabled, e.g. as follows:
>     agent/snmpd -Mmibs -f -d -Lo
> * Run snmpgetnext in another shell, e.g. as follows:
>     apps/snmpgetnext -Mmibs -cprivate localhost .1
> * Inspect the snmpd output. If no output is printed, this means that the
> UDP packets sent by snmpgetnext do not arrive at snmpd and hence that the
> network setup should be inspected. If snmpd reports that it received the
> packets sent by snmpgetnext but did not send any packets back, then there is
> a mismatch between the access control information passed to snmpgetnext and
> the access control information in snmpd.conf. If snmpd reports that it
> received and sent packets, then this means that the access control
> information passed to snmpgetnext and snmpd did match.
>
> An example of how the snmpd output should look like (on a Linux system):
>
> [ ... ]
>
> Received 37 byte packet from UDP: [127.0.0.1]:60541->[127.0.0.1]
> 0000: 30 23 02 01  01 04 07 70  72 69 76 61  74 65 A1 15
> 0#.....private..
> 0016: 02 04 46 52  36 BF 02 01  00 02 01 00  30 07 30 05
> ..FR6.......0.0.
> 0032: 06 01 01 05  00                                       .....
>
> Received SNMP packet(s) from UDP: [127.0.0.1]:60541->[127.0.0.1]
>   GETNEXT message
>     -- ccitt.1
>
> Sending 119 bytes to UDP: [127.0.0.1]:60541->[127.0.0.1]
> 0000: 30 75 02 01  01 04 07 70  72 69 76 61  74 65 A2 67
> 0u.....private.g
> 0016: 02 04 46 52  36 BF 02 01  00 02 01 00  30 59 30 57
> ..FR6.......0Y0W
> 0032: 06 08 2B 06  01 02 01 01  01 00 04 4B  4C 69 6E 75
> ..+........KLinu
> 0048: 78 20 61 73  75 73 20 32  2E 36 2E 33  33 2E 32 2D    x asus
> 2.6.33.2-
> 0064: 73 63 73 74  20 23 31 20  53 4D 50 20  50 52 45 45    scst #1 SMP
> PREE
> 0080: 4D 50 54 20  53 61 74 20  41 70 72 20  33 20 32 31    MPT Sat Apr 3
> 21
> 0096: 3A 31 30 3A  35 38 20 43  45 53 54 20  32 30 31 30    :10:58 CEST
> 2010
> 0112: 20 78 38 36  5F 36 34                                  x86_64
>
> [ ... ]
>
> Bart.
>
>
>

------------------------------------------------------------------------------

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.