-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
alexslv
Jul 8, 2015 1:09 PM
yes, if your walk is working fine, you have same ports and same community string and your PING works from polling engine but SNMP test still would not work - you can do the following:
1. login to your customer portal
2. click on log a ticket
3. describe your problem
4. click submit
5. allow few hours... have a coffee
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
I'm willing to do it, but I was hoping to not have to.
-
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
The only times I have had issues with Test Failed is that the string was mistyped (it is case sensitive) or that I was using the wrong version of SNMP. The only other time that I have had Test Failed when the SNMP engine on the target was not responding.
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
d09h
Jul 8, 2015 1:25 PM
I have seen a few devices that don't respond with a system MIB. Testing via web always failed, but I could list resources and assign universal device pollers. Can you list resources successfully too?
I am also convinced that the test button does nothing after the initial key press and subsequent test. Believe you have to navigate away from the page and come back to re-test.
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
I've done some research and the MIB is already in the SolarWinds MIB database. I figured I'd try pull data for the vendor specific OID's and see what happens (from the universal device poller) but, as if on cue, the device is no longer pingable so I have to wait for it to come back up.
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
alexslv
Jul 9, 2015 4:29 AM
1 of 1 people found this helpfuljust for the record - you do not need to have MIB in database to be able to poll over SNMP
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
d09h
Jul 9, 2015 7:39 AM
1 of 1 people found this helpfulAgreed. I figured if he can list resources, troubleshooting steps would be different than they would be if he could not list resources.
tigger2, can you list resources? Have you created a Universal Device Poller yet? Any logs on the monitored device?
The IronMails I used to monitor would never successfully respond when the test button was used. I was able to poll them regardless, but the SNMP test never worked. Believe it was due to not responding with sysObjectOID as suggested by HolyGuacamole.
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
alexslv
Jul 9, 2015 9:47 AM
Really? I have tried to add device which does not respond to SNMP test - it would fail to add new node upon validation. How did you add new node with "Test" not working?
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
alexslv
Jul 9, 2015 9:50 AM
1 of 1 people found this helpfulAh, ok, I have managed to do this by adding device as ICMP only first and then by editing polling method of it.
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
d09h
Jul 9, 2015 10:20 AM
1 of 1 people found this helpfulI believe I did the same thing. Sometimes necessary. Luckily not too often.
I might have done via Sonar Discovery though, as I frequently add sixteen similar devices at a time. In either case, I add as ICMP or external (vs SNMP) and then jam SNMPv3 credentials in database. And change polling method in the database.
-
-
-
-
-
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
shuth
Jul 8, 2015 6:31 PM
One of the things I'd like is for the previous "Test Failed" message to disappear when you click on Test again. That way, it makes it easier to see the subsequent test has failed, if it's still trying, or hopefully succeeded.
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
d09h
Jul 9, 2015 10:31 AM
What he said.
-
-
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
It sounds like you may not have SNMP running on the target device. Have you verified that SNMP is enabled?
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
Yep. I can do a MIB walk against the device and it returns data.
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
Are UDP ports 161 and 162 open between the device and the poller?
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
I like to do my SNMP walks from the pollers for exactly this reason.
-
-
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
1 of 1 people found this helpfulSince you have verified a MIB walk, the SNMP agent is obviously running on the target machine and there are no access list limitations.
The only reason I have seen it fail under these circumstances is when you have specified the RO community string for both Read and ReadWrite text boxes in the Add Node wizard. You can leave RW community field blank, and it should work. Not sure if it is relevant in your case.
Does your UPS device respond to basic MIB2 OIDs (like sysObjectOID)? Your MIB walk should be able to tell
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
Thanks for all the input! It's been awhile since I've had to do anything too deep in SNMP so I'm a little rusty on... everything. I don't have any command line tools installed, etc other than the Engineers Toolset.
There's several questions above so I'll try to sum it all up so far:
- SNMP is enabled on the target device, ports are open, etc. and my snmp read string is working (I have not tried using any strings in any any read/write setting(s), just the read string) just not through Orion. I do not have any access to this device in any other fashion (I'm not an admin of those devices, I don't have a web page to access the device to check configuration or modify it or access logs on it)
- I have added the node via ICMP, and then have tried SNMPv1 and v2 trying both combinations of "use 64 bit counters". In all of these configurations: Test button does not work, listing resources does not work.Aaaand:
- I ran MIB walks for both "standard" and "private" and all I get back is 1.3.6.1.4.1.*. It appears that mib-2 is not installed on the target device so I cannot get to sysObjectOID
Note: I poked around and found that the MIB walk uses SNMPv2c. I switched to SNMPv1 and it doesn't respond.
Note: I added the node and changed it to use SNMP, then went into the Universal Device Poller and tested there (there is a "Test" button in this tool as well). The tests were fine as I walked down each OID branch until I got to mib-2, then it said 'the OID is not supported', which confirms it a second way.
The plan right now is: I'm going to talk to the device admin and see if I can get mib-2 installed on it as this seems to be required for Orion for "standard" device monitoring outside of the Universal Device Poller. I'm too lazy right now to search the docs to validate this
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
Update: It looks like the vendor does not have and is not is not going to add MIB-2 to their device. Their reasoning is "MIB-1 ought to be enough for anybody", which is all I received via a hand written, wax sealed folded scrap of parchment that was hand delivered by a messenger riding a horse. I'm pretty sure they're not joking.
Given this, since I can't use discovery or add it manually, is there any other way to add a MIB-1 only device to Orion (beyond ping only)? I have not used the Universal device poller in a long time, but if I can't add the node to Orion as SNMP to assign Universal pollers, how would I poll for the MIB values the device does allow?
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
RichardLetts
Aug 7, 2015 5:18 PM
1 of 1 people found this helpfulWow. a balst from the past -- a quarter of a century ago [MIB-1 was from 1990; back then SNMP management applications were something one wrote from scratch including your own ASN.1 parser ]
Also: name names. it's Friday afternoon and I need another laugh...
Using the API it's possible to add a device that is not currently UP. there are xamples in the Orion SDK, some of them are powershell, and to get the node in there it's a start.
I think you can also add a node as ICMP, and then convert it to SNMP and the UI does not complain as much about not being able to get information.
with 11.5.x you can define your own set of 'device' pollers (distinct from the UnDP pollers) to retrieve whatever crazy MIB variable you like for the node details.
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
Vendor: Eltek Device: Enexus
...however...I'm looking at their root MIB definition as well as the fact that the device responds to SNMPv2 and I found this little blurb on the net "SNMPv2 includes MIB-II and adds some new objects"...In their root MIB they have:
IMPORTS
MODULE-IDENTITY, enterprises
FROM SNMPv2-SMI;
Is it possible that: They actually have MIB-2 (have it loaded on the device), but are somehow blocking parts of it with ACL's or removed parts they "don't need" on their device....and the person who sent that tobacco stained letter by horse and messenger was just pulling my leg?
I'll give the API-adding a shot and see how well it goes. I think the last time I tried adding as ICMP then converting to SNMP in the UI it would not let me. We're still on 11.0.1 but I have upgrading on the list of things to do.
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
Update: I was able to add the device(s) as ICMP only, then change it to SNMP after it was added so I didn't need to use the API method... Then I created some device pollers and it's all working well....except...
The "packet loss" of the device(s) is at ~50% loss ( it fluctuates a little bit), causing Orion to flip from up to down, to yellow, etc.about every poll cycle. I did some pings of my own and it all looks ok. I'm wondering if Orion is trying to determine "up" from both ICMP ( it works) and then SNMP (it fails, because no MIB-2) independently.
The SNMP custom pollers are working rock solid.
Any ideas on how to get the "regular" polling to report "green" (e.g. turn off SNMP polling for "up" status and keep ICMP...assuming this is what's happening..., or some other means)? I've tried changing the node level status settings for packet loss and response time to very high numbers and it doesn't seem to have an effect, The nodes just keep flip-flopping red-green-yellow-red.
-
Re: Is there a way to troubleshoot why the the "test" button fails when adding a new node using via SNMP
Update: The "packet loss" issue in my post immediately above is "fixable" but apparently not part of a published workaround, patch, or Thwack post. I opened a ticket and after sending some screenshots, analysis, diagnostics, Wireshark dumps, etc. SolarWinds support was able to stop the flapping from happening. I'm not posting what was done to encourage anyone else who ends up here with this *hopefully uncommon* issue to open a support ticket, as the method to fix this may change over time.
-
-
-