Views:
What do I do if the agent connection state shows Disconnected(N) on Management Service CLI?
  1. Verify network connectivity — Ensure the Vscan server can reach the Management Service in the Containerized Scanner cluster
  2. Check agent logs — If network connectivity is stable, review the agent logs in Windows Event Log for additional troubleshooting information
  3. Disconnection during agent installation:
    1. Search the logs for Failed to connect using onboarding token and review the error message
    2. If the error indicates an expired token, issue a new onboarding token and reinstall the agent
  4. Disconnection after the agent has been running:
    1. Search the logs for Failed to connect using device token and review the error message
    2. If the error indicates an expired token, proceed with agent re-onboarding (see below)
How do I re-onboard an agent?
  1. Stop the ONTAP agent service (v1fs-ontap-agent) on Vscan server
  2. Re-onboard the agent and issue a new onboarding token via Management Service CLI:
    clish agent re-onboard --instance <agent-name>
  3. Modify the config.yaml file in the ONTAP agent installation folder (default: C:\Program Files\v1fs-ontap-agent\)
  4. Remove the device_token key and its value
  5. Add the onboarding_token key with the newly issued token:
    onboarding_token: eyJh......
  6. Start the ONTAP agent service (v1fs-ontap-agent)
  7. Verify the agent connection status using the Management Service CLI
  8. After the agent connects successfully, re-enter credentials using:
    clish agent credential modify --instance <agent-name>