Network Switch stuck at "Identifying" activity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2020 11:39 AM
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!
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2020 06:04 AM
Does this issue happen consistently with this device?
Network devices typically prioritize processing SNMP get requests at a low or lowest level. Or some will ignore SNMP gets on a large table due to processing constraints depending on CPU load. Its possible this device is at high load and ignoring the request.
In a past life, I was an embedded software developer on network switches and routers. SNMP gets were always prioritized at the lowest level below other management traffic.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2020 07:51 AM
Thanks for the input, Paul.
This is the consistent case on a number of switches, based on my understanding high load is not a case in the customer environment, we can double check that though.
I think there is something with creds, but don't know how to check that. Again, we can login to the switches with a given credential record, we have snmp queries that returns some info back, but at some point context info appended to queries and that fails. There is no context on the credential record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-04-2021 04:49 PM
Did you ever figure this out? I'm getting the same thing after going from New York to Paris.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2021 07:20 AM
The SNMP configuration on switches side were preventing discovery. Double check that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2021 07:52 AM
I see. So you were never discovering these devices before?