actually we are working with a customer on this issue. Same thing, same trouble.
In my case the problem is "TAG based assignment" from SVA-Manager to OSS Server. One problem is.
- If there is one TAG renamed, this is not changed in the SVA-Manager policy.
Afterwards the SVA manager is not able to assign a OSS scanner any more. Renaming the TAGs again has not solved the issue.
Are you using TAG based assignment rules?
hi Troja no we are using I.P. based assignment rules
we have also redeployed the SVA manager more than once and no luck
the same issue as we have. After there is one problem, reinstalling the SVA appliance does not solve the problem.
How about the logs on SVA manager. Are there any error messages?
i have done a tail -f /var/logs (not sure the correct location at the moment off the top of my head).
and have seen **dropped** in the logs if you have another location for actual SVA logs please can you share ?
we took a look at /opt/McAfee/movesvamanager/logs/svaManger.log.
First of all, change the LOG settings in EPO for the svamanger from Info to Debug.
In our problem scenario the log shows the following error.
xx-x-2015 15:26:21.331 [qtp900363672-25] DEBUG IpMappingFilter - IP mapping filter not valid for the client : MYSERVER
xx-xx-2015 15:26:21.331 [qtp900363672-25] DEBUG IpMappingFilter - returning empty oss list as filter is configured to Assign OSS if rule is not defined for client ]
xx-xx-2015 15:26:21.331 [qtp900363672-25] INFO ClientAssignmentEngineImpl - No OSS found for client : 192.168.xx.xx for filter : ipMappingFilter
xx-xx-2015 15:26:21.331 [qtp900363672-25] DEBUG ClientAssignmentEngineImpl - No suitable OSS found for client : 192.168.xx.xx returning null
xx-xx-2015 15:26:21.331 [qtp900363672-25] WARN AssignOssHandler - Unable to assign OSS for client: ClientInfoVo
Perhaps you can find a useful information what is going on on svamanager.
tx will have a look