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!

[Ashutosh Munot1]

Yes that is fine.

[stuartgriffiths]

Hi, Ashutosh.

I've encountered this issue having upgraded from Orlando to Quebec on our Dev instance.

We run discovery from both Dev (on demand) & Prod (scheduled).

Same discovery configuration and same credentials.

Prod is running fine but since the upgrade in Dev discovery of network switches is now failing as per the OP.

The issue occurs during execution of the 'SNMP - Switch - Vlan' pattern called from the 'Network Switch' pattern and manifests like this (I've redacted some values with asterisks):

04/08/21 06:40:17 (967) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 DEBUG: (104)DefaultPatternExecutor - Starting step: [name='Handle FDB for Cisco', functor=IfClosure:IF:a5f1cc57-cfc5-483f-8334-d496ecc84907]
04/08/21 06:40:17 (970) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 DEBUG: (104)CommandsRunner - input: ; commands count: 1
04/08/21 06:40:17 (970) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 DEBUG: (104)SNMPProviderImpl - getting SNMP table 1.3.6.1.2.1.17.4.3.1 from 172.**.**.* (context:@1/vlan-1)
04/08/21 06:40:17 (972) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 DEBUG: (104)SNMPProviderImpl - EngineID previously fetched by SNMP4J: 80:00:00:09:03:00:00:1c:f6:a0:6c:81
04/08/21 06:40:17 (973) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 DEBUG: (104)SNMPProviderImpl - Adding local user *************** for engine ID 80 00 00 09 03 00 00 1c f6 a0 6c 81 
04/08/21 06:40:18 (071) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 DEBUG: (104)SNMPProviderImpl - After addUser user count is 1
04/08/21 06:40:18 (082) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 DEBUG: (104)SNMPProviderImpl - Error during table retrieval from host 172.**.**.*. TableEvent:16. Error Message: Authorization error
04/08/21 06:40:18 (086) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 (104)Step Failed - Handle FDB for Cisco - SNMP table query failed on host 172.**.**.*. Consider increasing the value of MID property mid.snmp.request.timeout. Current value is 10000 milliseconds

It goes on to a later step:
04/08/21 06:40:18 (098) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 DEBUG: (104)DefaultPatternExecutor - Starting step: [name='Handle bridge ports for Cisco', functor=IfClosure:IF:5ad414c1-35e2-4707-8144-699b5acf61a0]
04/08/21 06:40:18 (102) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 DEBUG: (104)CommandsRunner - input: ; commands count: 1
04/08/21 06:40:18 (102) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 DEBUG: (104)SNMPProviderImpl - getting SNMP table 1.3.6.1.2.1.17.1.4.1 from 172.**.**.* (context:@1/vlan-1)
04/08/21 06:40:18 (102) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 DEBUG: (104)SNMPProviderImpl - SNMP provider is not active. State: FAIL
04/08/21 06:40:18 (102) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 DEBUG: (104)CommandsRunner - all commands failed on host: 172.**.**.*. command type: SNMP_TABLE. command track:
SnmpTableCommand\(Relevant),; input: 
04/08/21 06:40:18 (105) Worker-Standard:HorizontalDiscoveryProbe-33b7490bdb57a0105be7d3ca4b9619e3 (104)Step failed - Handle bridge ports for Cisco - All command implementations (SNMP_TABLE) failed on host 172.**.**.*. Host might be down or unreachable. ()

Whlst the 'SNMP - Switch - Vlan' pattern has been updated as part of the upgrade, the updates look trivial to me. But I also tried reverting the pattern text back to the previous version but this made no difference to the result. Seems to be something underlying the pattern.

If you were able to resolve this, can you confirm what steps you took, please?

Thanks.
Stuart.

[SiD2]

Hi @Alexey,

This is a known issue and possibly will be fixed in upcoming Rome release, here is the PRB1378161.

This happens when the snmp query fails for some reason either cred or any other reason, in backend code there is an issue and further all snmp queries will fail, so only you got the error "all commands failed on...".

You can wait for the fix but till then you can fix your authorization error above and this scenario can be avoided.

Please mark Helpful / Accept Solution so that it helps others with similar questions.

[Fernando Dunn]

I'm having this problem after upgrading to Paris. All of my switches that were discovering fine haven't been discovered since the upgrade in December. I'm installing Paris Patch 6 now. Any suggestions otherwise?

[SiD2]

Hi Alexey,

The first step you can click on the Here and it will show you pattern log and which pattern step is failed, check in debug mode running that step and this will give some lead.

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