![]() |
|
|
|
#1
|
|||
|
|||
|
Irrelevant. Thanks for the help sight.
Last edited by MGCJerry; 01-16-2013 at 04:03 AM. |
|
#2
|
||||
|
||||
|
I'll bite, even though I've never done anything like this.
I've never had to deal too much with managed switches, or snmp for that matter, but I'll try to help. Most of the time when I have problems like this that google won't fix, it's something obvious.Network cable plugged in all the way on both ends? Unblocked the ports in both directions that SNMP uses in windows firewall? (UDP 161 and 162) Switch isn't dropping your SNMP requests/ SNMP disabled on switch? Might have to run apache as root (gasp!) if you're in windows and need an obscene amount of simultaneous connections No network hardware in between that's screwing with your packet headers? Using correct ip/subnet mask? Both manager and agent use same version of SNMP? (SNMPv2 will work with SNMPv1, but just to be absolutely certain this isn't your problem) |
|
#3
|
||||
|
||||
|
Jesus... Thats one Gordian Knot of a network.
![]() Are you sure the switch supports the variables you're trying to read? Are you querying too fast? Are you querying more than one variable at a time with different sessions? As for #4, its a limitation of the windows xp kernel iirc. Actually, running as root won't help either. If your number of connections is in the thousands, this may be your problem. Last edited by Sight Unseen; 02-05-2011 at 05:36 AM. |
|
#4
|
||||
|
||||
|
I think 2003 runs the xp kernel.
Also, make sure you're not making more than one read at a time. Like for instance calling the read method, then calling it immediately again before the switch has a chance to respond to the first request. I guess what I'm saying is make sure your code queries everything at once instead of sending a seperate query for each read request... or something. I'm just making a shot in the dark really.
Last edited by Sight Unseen; 02-06-2011 at 05:01 AM. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|