Update Port Probe Priorities for SNMP to be higher than SSH Product Success Playbook Update Port Probe Priorities for SNMP to be higher than SSH A step-by-step guide to analyze and remediate issues with Discovery Table of Contents Summary Goal of this Playbook Audience Problem Overview Executive Summary How this playbook can help you achieve business goals How this playbook is structured Problem Analysis Upstream Causes Downstream Consequences Impact on Your Business Engagement Questions Remediation Plays Summary Play 1: Review your data Play 2: Fix Play Play 3: Fix Play Data Governance Summary Goal of this Playbook This playbook helps in analyzing and resolving outstanding discovery issues related to base port probe configuration Details about this playbook Author Bibu Elias Punnachalil Reviewer John(Johnny) Walker Date 09/01/2022 Addresses HSD # HSD0010803 Applicable ServiceNow Releases All Releases Prerequisites Time Required Approximately 4 to 16 hours (depending on your environment) Audience Discovery AdministratorConfiguration ManagerServiceNow AdministratorSystem Administrators Problem Overview It is customary practice that most network devices are discovered using SNMP. Many devices, however, have both SNMP & SSH protocols actively listening or accepting connections. In these cases, Discovery may log error messages such as the following (No Valid Credential Found for types [SSH Password, SSH Key] Note: These and similar messages can be resolved or avoided by adjusting the classification priority such that SNMP has higher priority than SSH. In this way, the configuration of your devices need not be changed, but Discovery can be configured to prefer the SNMP protocol over SSH when they are both available Executive Summary How this playbook can help you achieve business goals This playbook helps in improving the discovery health with less error messages and improve performance How this playbook is structured This Playbook will guide you through 4 plays. Play 1 (a review configuration play) helps you to check the current port probe priorityPlay 2 (a review error messages play) provides remediation steps required to change the priority for port probesPlay 3 (fix play) provides remediation steps remediation steps required to change the classification priority for port probesPlay 4 (a Data Governance play) lists the guidelines and processes for continuing to monitor the port probe priority related issues Problem Analysis Upstream Causes Base configuration change is not practiced, due to potential risksDiscovery error messages are not actively monitored Downstream Consequences Data Consequence If there is a large amount of noise in the Discovery logs, it may be difficult to notice that there are actionable errors that are impeding data collectionIf Discovery takes too long, it may not collect all your data within the allotted window for schedules Operation Consequence Operational teams may require spending additional effort in troubleshooting discovery issuesDiscovery takes longer time to complete than it needs to App Consequence More hardware & network resources are consumed due to unnecessary triggering of probesMissing or incomplete data in your CMDB can impact any of the other applications which rely on accurate and up to date information Impact on Your Business Discovery error messages related to probe priority does not serve any purpose and delays discovery troubleshooting Incident Reduction Reduced Discovery Error Messages Engagement Questions: Consider the answers to these questions: How much time does your team spend reviewing error messages from Discovery?Do you use Discovery for your network devices? Remediation Plays SummaryThe table below lists and summarizes each of the remediation plays in the playbook. Details are included later. Play Name Review your data What this play is about Review port probe priorities Required tasks List port probes and check priorities Review Error Messages : Review Classification Errors What this play is about Review discovery errors related to classification Required tasks Navigate to classification errors and verify Fix Play : Swap Probe Priorities What this play is about Swap port probe priorities Required tasks Update the port priority so that SNMP takes precedence over SSH Data Governance What this play is about Helps you establish monitoring process for checking the port priorities Required tasks Provides detailed advice, best practices and data audit instructions Play 1 - Review your data What this Play is about Review port probe priorities Required tasks Click on Navigator Discovery Definition Port probes.This will list all port probes configured for Discovery. Filter for snmp or ssh by using the condition builder: Field Operator Value Name Is one of snmp ssh Example: Check the classification priority Play 2 – Review error messages from Discovery Home What this Play is about This fix play provides steps to review error messages related to port probe priority Required tasks Navigate to Discovery Home Click on the tile “Errors” Click on “Configuration” tile in Errors by Category Click on “Unable to classify” tile in Errors by Category > Configuration List of IP address with active classification errors. Check which IP addresses were subsequently discovered successfully through SNMP protocol Play 3 – Fix Play : Change the classification priority What this Play is about This play will help with changing the classification priority Required tasks Perform the steps in play 1. Swap the priorities as shown below After the discovery schedules are run, review the errors in play 2 Data Governance What this Play is about This play provides an approach for monitoring and governing the port probe priorities Required tasks Regularly monitor discovery home for error messages (refer play 2)In case, classification errors, investigate if the errors are triggered due to trying of wrong protocolCheck if IP service affinity is enabled Congratulations You have completed this Product Success Playbook.