Discovery of NetApp Storage fails classifier "Data ONTAP Release"; OOTB default classifier specifies /api/cluster value = "NetApp Release"Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } NetApp Storage Cluster Mode – HTTP" pattern is not triggered in some cases and the Discovery run ends in classification with messages such as "Active, couldn't classify," "No classification probe," and/or "No results returned from probe," resulting in incomplete discovery and missing/inconsistent Cluster/Node/SVM relationships. Examples: 1. Successful 11.22.33.33/ MID Server - HTTP - Classified and triggered Pattern name: NetApp Storage Cluster-Mode - HTTP - DIS0021157 - https://__instance__.service-now.com/nav_to.do?uri=discovery_status.do?sys_id=823e6f780fd6fa94a19ce2f800d1b2e0 2. Unsuccessful /failed - 11.22.33.44/ MID Server - HTTP - Classify "Active, couldn't classify" "No results returned from probe." - DIS0021158 - https://__instance__.service-now.com/nav_to.do?uri=discovery_status.do?sys_id=6a8e67f80fd6fa94a19ce2f800d1b284 Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } If we look at the ECC Queue input HTTP classify for each example we see a difference.successful - "full": "NetApp Release 9.16.1P7: Thu Aug 21 10:29:10 UTC 2025"failed - "Data ONTAP Release 9.16.1P7: Thu Aug 21 10:29:10 UTC 2025 (Lenovo)" Facts<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Storage Team will tell you that the NetApp where discovery fails is Lenovo marked and this model with API responds with string “Data ONTAP Release 9.16.1P7: Thu Aug 21 10:29:10 UTC 2025 (Lenovo)” . This behaviour cannot be changed. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } NetApp Storage Release 9.16.1P7 Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Reviewing the HTTP classification probe behavior (HTTPClassyProbe) for working vs failing targets. Discovery is successful for some when the classifier specifies /api/cluster value = "NetApp Release" - For a working NetApp target, the MID Server receives a valid response from https://<target>:443/api/cluster that includes the expected NetApp signature (for example, "NetApp Release …"). This allows Discovery to classify the endpoint and proceed with NetApp discovery. Discovery of NetApp Storage fails classifier "Data ONTAP Release" - For one of the failing targets (11.22.33.44), the HTTP classification probe is generated and port 443 is detected as open, however the request to https://11.22.33.44:443/api/cluster returns HTTP 404. Because the expected NetApp signature is not returned, Discovery cannot classify the endpoint as NetApp and therefore the NetApp pattern does not get triggered for that target. If we look at the HTTP classifications for "NetApp HTTP" definition:- https://__instance__.service-now.com/nav_to.do?uri=discovery_classy_http.do?sys_id=a3472daa87f92110c78ec8809bbb35c9, we can see the match MUST contain the value "NetApp Release" and in the unsuccessful discovery the value contains the returned information "Data ONTAP"- https://__instance__.service-now.com/nav_to.do?uri=discovery_classy_http_match.do?sys_id=107230101b87211082d00fa7624bcb34 Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Add a new HTTP Classification Matches for this NetApp model On nonPROD add another HTTP Classification Match to HTTP Classification /api/cluster: HTTP Classification Match - https://__instance__.service-now.com/nav_to.do?uri=discovery_classy_http_match.do?sys_id=107230101b87211082d00fa7624bcb34 HTTP Classification /api/cluster - https://__instance__.service-now.com/nav_to.do?uri=discovery_classy_http.do?sys_id=a3472daa87f92110c78ec8809bbb35c9 - see attached "discovery_classy_http_match_5f62d4573b523ad08f1693c964e45ae3.xml" 1. go to HTTP Classification /api/cluster - https://__instance__.service-now.com/nav_to.do?uri=discovery_classy_http.do?sys_id=a3472daa87f92110c78ec8809bbb35c9 2. under HTTP Classification Matches click NEW- ORDER - 110- VALUE - Data ONTAP Release- PATTERN - NetApp Storage Cluster-Mode - HTTP 3. Save 4. Test by running discovery to see if this is successful for both scenarios