Enable And Configure File Person, configuration error is not activated

[Alex24]

When making the File Persona configuration, it is not done and the following errorer is sent. You will know why this happens

Could you tell me what you mean by this
Compliance WORM feature is not supported for selected system.

   it shows it in the attached file

General

    System appdiskmgmt
    Serial number
    ID 11
    Type User operation
    Start time 6/06/2018 10:34:45 AM MST
    End time 6/06/2018 11:34:53 AM MST
    Duration 1 hour 8 seconds
    Priority —
    Origin SSMC

Task Detail
6/06/2018 10:34:45 AM MST Created
6/06/2018 10:34:45 AM MST Start user operation
6/06/2018 10:34:45 AM MST Enable File Persona on (appdiskmgmt)
6/06/2018 10:34:45 AM MST Enable File Persona (appdiskmgmt) on ports (0:3:1,1:3:1)
6/06/2018 10:34:51 AM MST Waiting for array task to complete: 2591 managefsinstall
6/06/2018 11:34:53 AM MST Timed out
6/06/2018 11:34:53 AM MST Failed: One or more errors occurred while enabling File Persona

[Dennis Handly]

If you ignore that message, is File Persona enabled?

What does the CLI show for "showfs"?

And "showtask 2591".

[Lucas Banuelos]

I had exactly the same issue, and the task's result is:

# startfs -cpgname FILE_PERSONA 0:3:1 1:3:1

Id Type Name Status Phase Step -------StartTime------- ------FinishTime------- -Priority- -User--
6688 background_command managefsinstall failed --- --- 2018-10-24 11:26:26 CDT 2018-10-24 11:40:55 CDT n/a 3paradm

Detailed status:
2018-10-24 11:26:26 CDT Created task.
2018-10-24 11:26:26 CDT Updated Executing "managefsinstall -upgrade 0 -tasks 6686 6687 -cpg NL_FILEPERSONA -nsp 0:3:1 1:3:1" as 1:30236
2018-10-24 11:40:55 CDT Error Task 6686 failed: 2018-10-24 11:40:37 CDT Error
Error: Failed to bring up internal networking on virtual machine on node 0 after VM re-define
2018-10-24 11:40:55 CDT Error Task exited with status 1
2018-10-24 11:40:55 CDT Failed Could not complete task.

[Dennis Handly]

> Error: Failed to bring up internal networking on virtual machine on node 0 after VM re-define

Look like you'll need to contact HPE Support for help.

Are these valid ports: 0:3:1,1:3:1 ?

shownode -pci