Warning: 'Descoping Asset as respective agent status is unreachable' in CCS 12.x.x

ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Warning: 'Descoping Asset as respective agent status is unreachable' in CCS 12.x.x

book

Article ID: 195672

calendar_today

Updated On:

Products

Control Compliance Suite Standards Server Control Compliance Suite

Issue/Introduction

Control Compliance Suite (CCS)

When running a job in CCS, the warning 'Descoping Asset as respective agent status is unreachable' is being reported on some of the assets.

Cause

The message 'Descoping Asset as respective agent status is unreachable' is just a warning message indicating that a previous job run (a CCS ping, CER job, Data collection job, etc) had a problem with the agent and it has been 'descoped' from future scans, and the descoping message is saying that the asset was skipped because that agent has known problems and has been marked 'red' in the Agent view in the console. Once the issue is resolved on the agent and it is verified by a CCS Ping (in the CCS Console) or running an Agent Management Job and the agent is marked 'green' in the Console, then that asset will be included in the next scan.

Environment

Release :CCS 12.5.x, 12.6

Component : CCS Agent

Resolution

To see the actual error that is being reported when a scan is run on that agent, you can export a .csv file that will give details on what might be causing the issue.

First, check the 'available column' icon on the right hand side and enable all the columns:

After you enable all columns you click on the ellipse and select 'Export Agents to CSV'.

In the CSV, the 'Details' column will show the error that might help why the agent is not able to run scans or if it is not reachable, etc.

Using that information in the csv, you can also check to see if the following might not be causing the problem:

Has the agent hostname/FQDN changed since it was initially registered to CCS? (if yes, agent needs to be registered)
Has the recorded IP changed since it was initially registered to CCS? (if yes, agent needs to be reregistered)
Does the manager listed as 'Routed from CCS manager' have connectivity to that agent?

Additional Information

How to disable descoping of agents in data collection

Retaining unreachable agents in data collection job scope