Skip to content

Suggested Search Strategies

Jump to bottom
Jeremy edited this page Jun 23, 2025 · 5 revisions

Suggested Search Strategies

This guide provides practical search strategies for the Cisco Support MCP Server, based on real-world usage patterns and analysis. Use these examples to get the most effective results from the bug database.

🆕 NEW in v1.9.5: Version Parameter Support

The multi_severity_search tool now supports a version parameter for much more precise version-specific bug searches!

✅ PROVEN WORKING Example:

Tool: multi_severity_search
search_term: "Cisco Unified Communications Manager (CallManager)"
search_type: "keyword"
max_severity: 1
version: "12.5"

Benefits: More accurate results, fewer false positives, version-specific bug discovery!

🎯 Quick Start Strategies

High-Severity Bug Search

# For immediate incident response - Option 1: Technical ID with version
Tool: multi_severity_search
search_term: "ISR4431"
search_type: "keyword" 
max_severity: 3
version: "17.9.6"

# Alternative Option 2: Full product series name (broader coverage)
Tool: multi_severity_search
search_term: "Cisco 4000 Series Integrated Services Routers"
search_type: "product_series" 
max_severity: 3
version: "17.9.6"

# Alternative Option 3: Short model number (fastest search)
Tool: multi_severity_search
search_term: "4431"
search_type: "keyword" 
max_severity: 3
version: "17.9.6"

When to Use Each Option:

  • Option 1 (ISR4431): Best balance of specificity and coverage
  • Option 2 (Cisco 4000 Series...): Broadest coverage, finds cross-platform issues
  • Option 3 (4431): Fastest search, may include false positives from other product lines

Version-Specific Critical Bug Search (NEW v1.9.5+)

# ✅ PROVEN WORKING: Cisco Unified Communications Manager (CallManager)
Tool: multi_severity_search
search_term: "Cisco Unified Communications Manager (CallManager)"
search_type: "keyword"
max_severity: 1
version: "12.5"

# Alternative: Product series approach for comprehensive results
Tool: multi_severity_search
search_term: "Cisco Unified Communications Manager (CallManager)"
search_type: "product_series"
max_severity: 1
version: "12.5"

# ISR Router example with version
Tool: multi_severity_search
search_term: "ISR4431"
search_type: "keyword"
max_severity: 1
version: "17.9.6"

Product Series Search (Traditional Method)

# Example 1: Using full product series name with version (Cisco API format - no leading zeros)
Tool: search_bugs_by_product_series_affected
product_series: "Cisco 4000 Series Integrated Services Routers"
affected_releases: "17.9.6"

# Example 2: Cisco Unified Communications Manager
Tool: search_bugs_by_product_series_affected
product_series: "Cisco Unified Communications Manager (CallManager)"
affected_releases: "12.5"

Product-Specific Investigation

# When you have exact product model
Tool: progressive_bug_search
primary_search_term: "ISR4431/K9"
severity_range: "high"
status: "O"

Software Version Analysis

# For version-specific issues
Tool: comprehensive_analysis
product_identifier: "ISR4431"
software_version: "17.09.06"
analysis_focus: "comprehensive"

🔍 Search Strategy by Use Case

1. Incident Response

Scenario: Production system experiencing issues

# Step 1: Get search strategy
Tool: smart_search_strategy
query_description: "ISR4431 memory leak high CPU 17.09.06"
search_context: "incident"

# Step 2: Execute comprehensive search
Tool: comprehensive_analysis
product_identifier: "ISR4431"
software_version: "17.09.06"  
analysis_focus: "incident_response"

Expected Results:

  • Product resolved to "Cisco 4431 Integrated Services Router"
  • Multi-severity bug search results
  • Product series search with "Cisco 4000 Series Integrated Services Routers"
  • Web search queries for official Cisco documentation
  • Immediate action recommendations

2. Upgrade Planning

Scenario: Planning software upgrade from 17.09.06 to 17.12.1

# Step 1: Analyze current version
Tool: progressive_bug_search
primary_search_term: "17.09.06"
severity_range: "high"

# Step 2: Check target version  
Tool: multi_severity_search
search_term: "17.12.1"
search_type: "keyword"
max_severity: 3

# Step 3: Get lifecycle info
Tool: comprehensive_analysis
product_identifier: "ISR4431"
software_version: "17.09.06"
analysis_focus: "upgrade_planning"

🔑 Key API Discovery

✅ Product Series Endpoint Works with Full Names

Working Example:

https://apix.cisco.com/bug/v2.0/bugs/product_series/Cisco 4000 Series Integrated Services Routers/affected_releases/17.9.6

This means you can use:

  • "Cisco 4000 Series Integrated Services Routers"
  • "Cisco Catalyst 9200 Series"
  • "Cisco ASR 1000 Series"
  • "Cisco Unified Communications Manager (CallManager)"

⚠️ CRITICAL: Version Format Requirements

✅ Correct Format (No Leading Zeros):

  • 17.9.6 ✅ WORKS
  • 15.1.4 ✅ WORKS
  • 16.12.5 ✅ WORKS

❌ Incorrect Format (With Leading Zeros):

  • 17.09.06 ❌ Returns no results
  • 15.01.04 ❌ Returns no results
  • 16.12.05 ❌ Returns no results

Auto-Conversion: The enhanced tools (v1.9.1+) now automatically convert 17.09.06 → 17.9.6 format.

❌ Product Name Endpoint Requires Technical IDs

The /bugs/products/product_name/ endpoint expects technical product identifiers, not full marketing names:

  • ✅ Use: "ISR4431", "WS-C2960-24TC-L"
  • ❌ Don't use: "Cisco 4431 Integrated Services Router"

📋 Search Patterns by Product Type

ISR (Integrated Services Routers)

Product Series: "Cisco 4000 Series Integrated Services Routers" Product Variations to Try: ISR4431/K9 → ISR4431 → ISR4400 → ISR

Effective Searches:

# Best approach - Product series with version
Tool: search_bugs_by_product_series_affected
product_series: "Cisco 4000 Series Integrated Services Routers"
affected_releases: "17.09.06"

# Alternative - Progressive search
Tool: progressive_bug_search
primary_search_term: "ISR4400 memory"
severity_range: "medium"

Catalyst Switches

Product Series: "Cisco Catalyst 9200 Series" Product Variations: WS-C2960-24TC-L → C2960 → Catalyst 2960

Effective Searches:

# Product series approach
Tool: search_bugs_by_product_series_affected
product_series: "Cisco Catalyst 9200 Series"
affected_releases: "16.12.05"

# Alternative keyword search
Tool: progressive_bug_search
primary_search_term: "Catalyst 2960 spanning tree"
severity_range: "high"

ASR (Aggregation Services Routers)

Product Series: "Cisco ASR 1000 Series" Product Variations: ASR1001-X → ASR1000 → ASR

Effective Searches:

# Product series with version
Tool: search_bugs_by_product_series_affected
product_series: "Cisco ASR 1000 Series"
affected_releases: "17.06.05"

Unified Communications Manager

Product Series: "Cisco Unified Communications Manager (CallManager)" Product Variations: CUCM → CallManager → Unified Communications Manager Common Versions: 15.0, 14.0, 12.5, 11.5, 10.5

✅ Recommended Searches (v1.9.5+):

# ✅ PROVEN: Multi-severity search with version (most effective)
Tool: multi_severity_search
search_term: "Cisco Unified Communications Manager (CallManager)"
search_type: "keyword"
max_severity: 1
version: "12.5"

# Alternative: Product series approach for comprehensive coverage
Tool: multi_severity_search
search_term: "Cisco Unified Communications Manager (CallManager)"
search_type: "product_series"
max_severity: 3
version: "12.5"

# Version comparison for upgrade planning
Tool: multi_severity_search
search_term: "CallManager"
search_type: "keyword"
max_severity: 2
version: "15.0"

Traditional Methods:

# Product series with version (traditional)
Tool: search_bugs_by_product_series_affected
product_series: "Cisco Unified Communications Manager (CallManager)"
affected_releases: "12.5"

# Keyword-based search for specific issues
Tool: progressive_bug_search
primary_search_term: "CallManager database replication"
severity_range: "high"

💡 CallManager Tips:

  • Use version parameter: Much more precise than generic searches
  • Version format: Use simple format (12.5, 14.0, 15.0) not full patch versions
  • Keyword vs Product Series: Keyword search works well for CallManager names
  • Common Issues: Database replication, cluster communication, phone registration

🚀 Enhanced Search Tools (v1.9.0)

1. Smart Search Strategy

Tool: smart_search_strategy
query_description: "ISR4431 17.09.06 memory issues production"
search_context: "incident"

Returns: Customized search recommendations and strategy

2. Progressive Bug Search

Tool: progressive_bug_search
primary_search_term: "ISR4431/K9"
version: "17.09.06"
severity_range: "high"

Features: Auto-broadening, version normalization, product ID variations

3. Multi-Severity Search

Tool: multi_severity_search
search_term: "memory leak repm"
search_type: "keyword"
max_severity: 3

Features: Parallel searches of severities 1, 2, 3 with combined results

4. Product Name Resolver

Tool: product_name_resolver
product_id: "ISR4431/K9"

Returns: Full product name + product series + web search strategies

5. Comprehensive Analysis

Tool: comprehensive_analysis
product_identifier: "ISR4431/K9"
software_version: "17.09.06"
analysis_focus: "incident_response"

Features: Product resolution + bug analysis + web guidance + recommendations

💡 Best Practices Summary

✅ Most Effective Approaches

  1. Use multi_severity_search with version parameter for version-specific issues (v1.9.5+)
  2. Use product series search for full product names
  3. Start with comprehensive analysis for unknown situations
  4. Use progressive search when exact searches fail
  5. Try multiple severity levels for critical issues
  6. Combine different search approaches

🆕 Version Parameter Benefits (v1.9.5+):

  • ✅ More Precise Results: Get bugs specific to your software version
  • ✅ Better Performance: Reduced false positives and irrelevant results
  • ✅ Proven Working: Successfully tested with CallManager 12.5, ISR 17.9.6
  • ✅ Multiple Search Types: Works with both keyword and product_series searches

🎯 Product Name vs. Product ID Best Practice

❌ Less Effective:

Tool: search_bugs_by_keyword
keyword: "ISR4431/K9 17.09.06"

✅ More Effective:

Tool: search_bugs_by_product_series_affected
product_series: "Cisco 4000 Series Integrated Services Routers"
affected_releases: "17.09.06"

🚀 Best - Automated:

Tool: comprehensive_analysis
product_identifier: "ISR4431/K9"
software_version: "17.09.06"

🔄 When to Use Each Tool

Scenario Recommended Tool Why
Have product series name + version search_bugs_by_product_series_affected Direct API support for full names
Have technical product ID progressive_bug_search Handles variations automatically
Unknown/complex situation comprehensive_analysis Combines multiple strategies
High-severity focus multi_severity_search Parallel severity searches
Need search guidance smart_search_strategy Provides customized recommendations

🌐 Web Search Integration

Product Resolution

Tool: product_name_resolver
product_id: "ISR4431/K9"

Returns:

  • Full Name: "Cisco 4431 Integrated Services Router"
  • Product Series: "Cisco 4000 Series Integrated Services Routers"
  • Official URL: https://www.cisco.com/c/en/us/support/routers/4431-integrated-services-router-isr/model.html

Lifecycle Research Queries

Auto-generated web search queries:

  • "ISR4431/K9" end of life site:cisco.com
  • "17.09.06" end of support site:cisco.com
  • "Cisco 4000 Series" replacement migration site:cisco.com

🎯 Real-World Example

Complete ISR4431 Investigation

# 1. Get strategy recommendations
Tool: smart_search_strategy
query_description: "ISR4431 17.09.06 memory constantly increasing"
search_context: "incident"

# 2. Execute comprehensive analysis (automatically does product resolution + multiple searches)
Tool: comprehensive_analysis
product_identifier: "ISR4431"
software_version: "17.09.06"
analysis_focus: "incident_response"
include_web_search_guidance: true

# 3. If needed, direct product series search
Tool: search_bugs_by_product_series_affected
product_series: "Cisco 4000 Series Integrated Services Routers"
affected_releases: "17.09.06"

Expected Results:

  • Bug CSCwp03948: Memory usage constantly increasing on repm process
  • Product: Cisco 4431 Integrated Services Router
  • Series: Cisco 4000 Series Integrated Services Routers
  • Status: Open, Severity 2
  • Web search queries for EoL status and migration
  • Comprehensive recommendations

This approach leverages all the enhanced search capabilities introduced in v1.9.0 for maximum effectiveness!

Clone this wiki locally