Skip to main content
NetApp Console local deployment

Troubleshoot LLM integration in NetApp Console local deployment

Contributors netapp-tonias netapp-ml94669
PDFs

Use this quick triage flow to diagnose and resolve common LLM integration issues in NetApp Console local deployment.

Note This documentation regarding connecting an LLM to the Console assistant to enable AI features is provided as a technology preview. With this preview offering, NetApp reserves the right to modify offering details, contents, and timeline before General Availability.

If you have not completed setup, see Connect your LLM and enable the NetApp Console assistant.

Triage LLM integration issues quickly

  1. Validate AI Tools configuration in Administration > AI Tools.

    Confirm provider type, endpoint URL, API key, selected model, and outbound network access.

  2. Validate assistant availability on the dashboard.

    Confirm the Console assistant button appears for expected users and organizations.

  3. Validate runtime behavior.

    Run a simple read-only request and confirm provider endpoint reachability, model availability, and provider service health.

Troubleshoot by symptom

Symptom Likely cause What to check Next action

Save or test fails in AI Tools

Configuration or connectivity mismatch

Provider type, endpoint URL, API key format, selected model, and outbound access

Correct the value that fails validation and save again

Console assistant button is missing

Unhealthy integration status, org mismatch, or RBAC mismatch

Successful AI Tools save, integration status, current organization, and expected access role

Refresh the session and verify with a known-good admin account

Assistant opens but request fails

Provider or runtime path issue

Endpoint reachability, model availability on that endpoint, provider limits, and temporary provider status

Retry after fixing endpoint/model mismatch or provider-side limit issues

Assistant response is slow or inconsistent

Prompt size, endpoint performance, or network/proxy instability

Short prompt test, provider service health, and network/proxy stability

Use a shorter prompt, try another supported model, and stabilize network or proxy routing

Respond to LLM credential exposure or misuse

If you suspect API key exposure or unauthorized use:

  1. Revoke the existing API key in your provider system.

  2. Create a new API key.

  3. Update the key in Administration > AI Tools.

  4. Verify successful reconnection with a read-only assistant test.