JonH67,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit https://www.microfocus.com/support-and-services and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.microfocus.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.microfocus.com)
- You might consider hiring a local partner to assist you.
https://www.partnernetprogram.com/partnerfinder/find.html

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.microfocus.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Micro Focus Forums Team
http://forums.microfocus.com

JonH67 wrote:

>
> Does anyone know how to troubleshoot or configuration to scan OES2SP3
> cluster resources? I've set up 2.6.1 as the scan capability matrix
> implies that MFR3 does not support scanning OES2 even with a proxy. I
> can scan Netware, I can scan OES2 local volumes via the proxy agent
> with no issues, but as soon as I do a scan on a cluster volume it
> shows a 220 the edirectory tree or server name could not be resolved
> or invalid error.
> I can select the resource as a proxy assignment, I can see the cluster
> volume as NSS in storage resources, I can select it as a scan target
> and create a scan policy exactly the same way as Netware or OES2 local
> volumes and it fails. I have checked the proxy users rights to the
> Cluster node, the cluster server resource and the cluster volume and
> it has Supervisor to all of them.
>
> Any pointers on how to resolve this would be great
>
> Thanks

JonH67,
File Reporter should be able to scan any OES2 volume clustered or not.
Please check your DNS and SLP resolution, also verify that within the
linux mount point attribute is configured in the eDirectory volume
objects.

If you're still having difficulties after performing these checks, I
suggest opening and SR.

Thanks,
Rich Lagger
Product Specialist.

--