Network Switch stuck at "Identifying" activity

[Alexey7]

Hi everyone,

Looking for any guidance over the following errors from a Switch discovery. Currently it errors out with "Failed Exploring CI Pattern, Pattern name: Network Switch, To Check Pattern Log Press Here"

The following errors are from MID. Keep in mind the most of SNMP queries do return results back, however some of them do not, like this one:

getting SNMP table 1.3.6.1.2.1.17.2.15.1 from 10.10.10.10 (context:@1/vlan-1)

SNMP provider is not active. State: FAIL

Questions:

• How the error above affect the switch discovery? Is this something that caused discovery to fail?
• Some of queries have "context:null/null" and some like in the example above "context:@1/vlan-1", do you know where are these coming from? Most of queries if not all with "context:@1/vlan-1" are failing.

mid.snmp.request.timeout set to 15000; mid.snmp.session.timeout set to 60000. The docs do not say what's the limits for these parameters, so to know that would be something that will benefit me as well.

Thank you beforehand!

[Alexey7]

I got the following when i expand "discovery":

2020-11-13 12:51:55: Identification Engine: Discovery status is FAILURE, Identification sections in pattern failed: section: discovery, error: All command implementations (SNMP_TABLE) failed on host 10.10.10.10. Host might be down or unreachable. ().


And as i mentioned above not all snmp queries are failing, i can confirm that using Network Switch pattern debug mode. I see data is coming back and populates temporary vars and snow tables.

I'd appreciate further input. Thanks

[SiD2]

Hi Alexey,

If I get you correctly, you mean when you did pattern debug some snmp queries did get some results, but when you ran discovery you are getting above error.

If this is the case, I guess some issue with communication not consistent b/w snow instance and the switch. Can you check once restarting the mid server?

Also if you have multiple mid servers, are you sure same mid is used while running discovery and pattern debug?

Please mark the appropriate responses as Correct/Helpful so that this thread gets closed and helps others with the same question in the future.

[Alexey7]

You're correct.

And yes, something is not consistent... I did restart mids, we have a cluster assigned to a discovery schedule, but i ran a quick discovery from a single mid and got the same error.

[SiD2]

Hi Alexey,

I'm not much aware of these kind of issues on snmp, but as you checked discovery now with one specific mid server, can you try pattern debug with the same mid and see if you are getting any responses.

On the inconsistent behavior, i'm helpless, let's see what others will say.

@Ashutosh Munot  @doug.schulze any thoughts?

[Ashutosh Munot1]

Hi,

I am working on this issue as well. I was facing the same issue. If i have answer will get back.

Thanks,
Ashutosh