pattern failed: section: discovery, error: All command implementations (SNMP_TABLE) failed on host

[Anshu_Anand_]

Dear Experts,

I am getting error on discovering my network switch.

Identification Engine: Discovery status is FAILURE, 
Identification sections in pattern failed: section: discovery, 
error: All command implementations (SNMP_TABLE) failed on host XX.XX.XX.XX
Host might be down or unreachable. ().

 The device is up and running in the datacenter.The credentials test pass .

The debug of pattern fetch the serial,model id,oid and other info.

But still it does not discover and pattern fail.

Could you please provide, what i am missing?

@Ashutosh Munot 

@Ankur Bawiskar @chuckm 

[ggarcia1]

Go to Pattern Designer, open Network Switch pattern, click Debug, select mid and enter IP of the problem switch.

Click the last step on the pattern and all the prior steps will trigger; it should point out which step fails; if not just click every couple of steps to find which step is failing.

It might be a specific mib/oid that is not supported on this device. You may have to consult with your network team to verify.

If that ends up being the case, you may have to copy the pattern and disable that step and any dependent steps (if your on paris, i'm not sure if other versions allow a single step to be disabled).

I don't think extending the pattern will work because I think extensions run after the main section, but in this case the main section is failing.

Debug and see where it leads.

[Aleksey Nazarov]

Debugger is not generating any errors. Any other ideas?

[ggarcia1]

When you expand the discovery sections with the red icons, which specific steps also have a red icon?

That error can return when any given SNMP command fails, so we'll want to try to find which one is failing and then investigate if that command/MIB is supported on the target device.

Then it might not be about the failure of that step so much as a precondition on another step for that value that didn't return, but first we gotta know what step.

Debugging and discovery don't always line up.