Discovery issue on PowerProtect Data Manager

Does your PowerStore have the optional Mezzanine bord which offer the 4x 10 or 25G GbE? on the controler module? The Ports 0+1 are hard configured as a LAG/LACP and IIRC this interface is named "bond".

Regards,

Joerg

We created  fsn with 2 ports on power store 500T and we are trying to run the discovery from Power protect manager but it fails with the above error. We cannot find any traffic on the firewall and we are do not know how the Power Protect Manager discovers the power store in order to solve the above issue.

The issue was that Power Protect Data Manager is compatible only with Link aggregation and does not work with FSN!!

Now we have the following issue

NAS vProxy Engine protengine.danaos.local is unable to perform SnapshotAndSlice operation for nasShare DMC_PG. 

Error Details:
 TaskId: 44b4720b-3248-4ea1-bf42-8c19a633af62, JobId 44b4720b-3248-4ea1-bf42-8c19a633af62 
 NAS agent error code 'ABNA0044'. Rest response code 422 for url : 
https://xxx.xxx.xxx.xxx/api/rest/smb_share/67bc6975-bdec-8692-2443-329f786fcc8c/set_acl, 
ERROR_CODE_PST : 0xE080101404E0, ERROR_SEVERITY : Error, ERROR_MESSAGE_L10N : 
The input User: xxxx\dcuser cannot be resolved to an SID.. 

Ah ok.

The new error looks like an authentification problem related to an external identity source? Is this an AD User or a local or hardcoded account? The term "SID" sound more like Microsoft Windows.

I only have experience with the PowerStore it self an because we are a VMware shop we only use "block" in most cases. But i have some units within unified mode as well.  

Yes the interface with the name "bond" is the default LAG/LACP on the mezz. card which is optional on the 500t and there is no need to setup any more. This was different on early version of the PowerStore OS/Firmware. There is was a fixed requirement.

Regards,

Joerg