Node created from API never gets polled

Hi,

Some details appear after rediscovery of the node. You can check the RediscoveryInterval (which is set to 30 minutes by default) and NextRediscovery to see when the rediscovery will happen. You can also trigger Rediscovery from GUI and see the details.

Also NextPoll will give you details on when is the next polling will happen (It has interval of 2 minutes by default).

Check and let me know if you still face issues.

I appear to be getting better results with this today.  Not sure if I had typos when I was testing last week or what.  The node did eventually start getting SNMP polled but it seemed to be hours after I created it (maybe during the Rediscovery process?).

In testing today, I can get the ICMP status just from creating the pollers and waiting a couple minutes.  If I then do a "Poll now" through the GUI, I am now getting all of the SNMP related info I'm looking for.  I can't seem to get the PollNow invoke verb to work though.  I'm issuing:

#Using hard coded NodeId again as an example

res = swis.invoke("Orion.Nodes", "PollNow", "N:100")

print res

Which returns "None", I assume that is fine to see in the return but the node never appears to get polled.  The "netObjectId(System.String)" is supposed to be the NodeId right?  And in "N:XXX" format?

Also, is there a way to invoke rediscovery via API?  I didn't see it in the SWIS schema under Orion.Nodes.

Hi,

The syntax for PollNow is correct. How do you confirm that the node is not getting polled?

Check the PollInterval, to see how what is the interval set for polling (by default it is 120 seconds, so every 2 minutes polling should happen.)

If you want to check if the pollNow via SDK  is working, increase the polling interval to say 5 minutes (300) and invoke pollNow, you should see the NextPoll is updated to 5 minutes from the time when invoke was called. (there may be delay of few seconds as it is a background process)

There is no verb for Rediscovery as of now.

Thanks

It looks like "Rediscovery" is the key here like you mentioned in your first reply.  I checked the "NextPoll" time as you suggested and it looks like invoking "PollNow" via API is working but its functionality doesn't seem to mirror the "Poll now" option in the GUI.  I noticed when I do a "Poll now" in the GUI, it updates the "NextRediscovery" time.  So, when I either "Poll now" or "Rediscover" via the GUI, I get all the node details, etc.

Do you have any suggestions for getting SNMP info back as quick to real time as possible?  For now, I guess I'll set RediscoveryInterval=1 and PollInterval=60 when I create the node, then issue an "Update" on the URI for that node to change it back to normal after I get the data I'm looking for.

On a side note, do you have any basic rundown of what common tasks are currently possible or impossible using the API?  I've dug through Thwack quite a bit looking for answers to things like whether you can add volumes, whether you can detect pollers automatically, etc.  I stumbled across something I think you may have posted including use of the "Discovery" verbs that had a bunch of strange looking XML attached to it.  I'm not sure if things have changed since these posts, just trying to get an idea of what the current state of things is.

Thanks.

I'm having the same issue but unfortunately it's not clearing up on its own like mlrabbitt‌'s issue. Here's the test code I'm using. It creates the node without issue but then sits there as Unknown and doesn't poll. I've let it sit for hours and there's no change.

https://gist.github.com/mrxinu/223c73c6f3636ff489a4

--

Steven Klassen

Developer Analyst @ Loop1 Systems, Inc.

http://www.loop1systems.com/

Have you tried doing a Rediscover through the GUI after creating the node?  In my case, my nodes didn't start polling correctly until the Rediscovery happened, which in my environment is 240 minutes (4 hours).

I did and that doesn't seem to make a difference. I went ahead and created the node in the GUI, took stock of all the pollers assigned to it (and their Enabled settings) and mimicked that exactly in the code. Same result.

https://gist.github.com/mrxinu/223c73c6f3636ff489a4/revisions

--

Steven Klassen

Developer Analyst @ Loop1 Systems, Inc.

http://www.loop1systems.com/

I ran the first script you included and it worked for me.  I'm not sure what's different about your environment.  Are you sure your IPAddress, Community, EngineID are all correct?

Here's an alternate (probably better) way of adding a node via API that might be worth trying: Perl SDK - Start Discovery - PluginConfigurations

Yes, The thwack post provided below provides details on answering your question.

How do we programmatically discover the non-interface properties [in Orion] and enable them

Well that's encouraging. =) I'll check out running this against another system.

--

Steven Klassen

Developer Analyst @ Loop1 Systems, Inc.

http://www.loop1systems.com/