Printer Discovery schedule

pranithadar
Kilo Contributor

yesterday

"I’m discovering printer devices using discovery schedules, When the SNMP version is set to 'ALL', the discovery fails. However, when I set the SNMP version to V1/V2, the same discovery schedules completes successfully. Could you help me understand why this is happening?"

0 Helpfuls
  • 754 Views
1 REPLY 1

Steven Coda
Tera Contributor

yesterday

Hi,  
This appears to be a challenging situation you are having,  I have not seen this myself and was thinking about this within my own PDI and our own instance,  I put together some thoughts and hope this may help you isolate what it could be.

I feel that when SNMP discovery works for version v1 or v2 but fails when set to ALL it might point to a configuration or credential mismatch rather than a problem with the Discovery schedule itself

Here are some steps I was thinking you may want to try to troubleshoot (not in order)

 

Confirm that the SNMP ALL option includes v1 v2c and v3:  Discovery will attempt each version based on credential matching so if the v3 credential is invalid or incomplete the entire SNMP probe may fail before falling back to v1 or v2

 

Check your SNMP credentials: Make sure you have valid entries for v1 v2c and v3 in the SNMP credentials table and that they are assigned to the correct MID Server or Discovery range (I feel you have this since v1 and v2c works)

 

Verify your MID Server configuration:  Review the MID Server properties to confirm the SNMP capability is enabled and that it is allowed to use all versions of SNMP (I feel you have this since v1 and v2c works, however, double-checking)

 

Test MID Server capabilities using this table:  /ecc_agent_capability_value_test.do - This can show whether your MID Server supports the SNMP ALL capability and is properly reporting it to the instance

 

Review the Discovery patterns and probes: Walking through the debug the SNMP pattern allow you to confirm which credential is being used, and where discovery is failing when SNMP ALL is selected


Sometimes the pattern logic or the credential matching rules may behave differently than expected

Run two test discoveries

  • One with SNMP v1v2
  • One with SNMP ALL

Collect both MID Server logs and ECC queue messages then compare them line by line

 

Compare the successful and failed runs: Look for which SNMP version was attempted first what credential ID was used and whether there were timeouts or authentication failures before the Discovery stopped

 

This comparison is often the key to seeing what is actually happening behind the scenes

 

Looking forward to your response when you find out how you resolved it.

0 Helpfuls