If a NetFlow collector service is showing a “down” status, which two of the following...

When the NetFlow collector service is showing a " down " status, the SolarWinds documentation recommends the following troubleshooting steps:

Confirm the database connection is up and server has free resources.

Explanation: The NetFlow collector service relies on connectivity to the SolarWinds database. If the database connection is lost or the server is out of resources (such as CPU or RAM), the service may go down or fail to start. Ensuring that the database is reachable and that the server has enough resources is a primary troubleshooting step.

Start or restart SolarWinds’ NetFlow service from Orion Service Manager.

Explanation: The official troubleshooting guidance instructs administrators to use the Orion Service Manager to start or restart the NetFlow service. This is a direct method to recover the NetFlow collector from a " down " state and is one of the first actions recommended by SolarWinds support.

Options B and C are not recommended in the official documentation:

Deleting and re-adding the NetFlow collector service is not a documented troubleshooting step and may cause loss of configuration.

Starting or restarting the generic " collector service " is not specific to NetFlow; the correct service is the NetFlow service.

Exact Extract from Official Guide:

" If NetFlow collector service status is down:

Ensure the SolarWinds database is online and the server is not experiencing resource issues.

Use the Orion Service Manager to start or restart the NetFlow service.

If the issue persists, review the NetFlow logs for errors and consult the SolarWinds Success Center for advanced troubleshooting. " — (Network Performance Monitor Administrator Guide, Troubleshooting NetFlow and Service Issues)