Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > IP Address Manager (IPAM) > IPAM - Knowledgebase Articles > IPAM scans not running

IPAM scans not running

 Updated June 23rd, 2017

Issue

When users view a Scan Job Status (IPAM Settings > Scan Job Status), all jobs display the following status:
    Status "Next Scan: ASAP", Last Discovery: {Past Date}

If you receive the above Scan Job Status, verify the following:

  • All services are running in the Servers Manager.
  • There are no reported IPAM errors in the SolarWinds.Net Event Log under the Windows Applications and Services Logs.

If neither of these are not the issue continue to the resolution below.

Resolution

Try the following resolutions to restart IPAM scanning:

  • Replace the job engine v2 and collector. In general, IPAM scans are stuck due to a stalled job engine. SolarWinds recommends replacing the job engine to flush the IPAM jobs out and then allow them to restart.
  • Review your subnets. If you have added an excessively large subnet, either manually or from a scope, scanning may stall.
  • Verify your zones. If IPAM is conducting a DNS zone transfer and a DNS is being monitored this can corrupt the zone. Verify all zones are correct and not corrupted.

Replace Job Engine v2

  1. Stop all Orion services from Orion Service Manager.
  2. Go to C:\ProgramData\SolarWinds\JobEngineV2\Data\JobEngine35.sdf file and rename it to JobEngine35_OLD.sdf.
  3. Create a copy of C:\ProgramData\SolarWinds\JobEngineV2\Data\JobEngine35 - Blank.sdf one and rename it to JobEngine35.sdf.

    This way you have the old one to revert back to and you always have a blank copy in case an issue reoccurs.

     

  4. Right-click the properties of the JobEngine35.sdf you created and clear the read only box. Click OK.

Replace Collector (Polling Controller)

  1. Stop all Orion services from Orion Service Manager.
  2. Go to C:\ProgramData\SolarWinds\Collector\Data\PollingController.sdf file and rename it to PollingController_OLD.sdf 
  3. Create a copy of C:\ProgramData\SolarWinds\Collector\Data\PollingController - Blank.sdf and rename it to PollingController.sdf. 

    This way you have the old one to revert back to and you always have a blank copy in case issue reoccurs.

  4. Right click on properties of the PollingController.sdf you have created, clear the read-only box and click OK.
  5. Restart all Orion Services

 

This issue can also mask a separate issue with the same symptoms documented here

Last modified

Tags

Classifications

Public