Discovery incorrect classification orderIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Discovery incorrect classification order. Discovery not triggering classification probes according to port probes classification priority. Release All supported releases. Cause A system property called glide.discovery.ip_service_affinity allows Discovery to remember the last port of the IP address that was discovered. This property is set to false by default. When set to true, glide.discovery.ip_service_affinity = true, an entry for the ip address and ip service will be created on table ip_service_affinity. The next time this ip address is discovered, the ip service specified under ip_service_affinity will be attempted first regardless of classification priority. Resolution Delete the ip_service_affinity for the ip address having the issue.