Controller ViPR: L'ordine di rimozione di un file system NFS non riesce
Summary: L'eliminazione di un file system NFS gestito dal controller ViPR non riesce.
Symptoms
L'utente non è in grado di eliminare un file system NFS su un array VNX nel controller ViPR.
Errori UI del controller ViPR:
[ERROR] Fri Jun 22 08:58:20 UTC 2018 Error 12000: Message: Operation failed due to the following error: Failure Description: Check File System dependencies: NFS and CIFS exports and snapshots
Cause
ViPR Controller esegue query su VNX (CheckpointQueryParams XML API) per verificare la presenza di tutte le istantanee sull'intero array.
Se SnapSure non è abilitato o concesso in licenza sull'array VNX, la query API avrà esito negativo. Ad esempio:
Time on CS: Mon Jun 18 18:12:50 CEST 2018 Output from: /nas/bin/nas_license -list key status value site_key online 57 93 7c 7a cifs online nfs online replicatorV2 online
SnapSure è un prerequisito per ViPR Controller negli ambienti di file VNX. Per ulteriori dettagli, consultare la Guida ai requisiti e alle informazioni del data center virtuale del controller ViPR.
Resolution
- Nell'interfaccia utente di Unisphere, selezionare il nome della control station.
- Qui viene visualizzato il menu completo per il cluster VNX. A sinistra viene visualizzato il sottomenu delle licenze.
- Verificare che la casella di controllo SnapSure sia selezionata. In caso affermativo, verificare che sia convalidato e, in caso contrario, convalidarlo.
Additional Information
Prima di eliminare il file system, ViPR Controller esegue una query su VNX (CheckpointQueryParams XML API) per verificare la presenza di tutte le istantanee sull'intero array.
vipr3 vipr3 controllersvc 2018-06-22 08:58:08,844 [199|checkFileSystemDependenciesInStorage|1246f9af-6340-4754-b2d6-ecb570f544f144f2570a-0c48-4a39-ac03-bd068a13fd4b] DEBUG Wire.java (line 84) >> "<?xml version="1.0" encoding="UTF-8" standalone="yes"?><RequestPacket xmlns="http://www.emc.com/schemas/celerra/xml_api"><Request><Query><CheckpointQueryParams/></Query></Request></RequestPacket>"
vipr3 vipr3 controllersvc 2018-06-22 08:58:08,844 [199|checkFileSystemDependenciesInStorage|1246f9af-6340-4754-b2d6-ecb570f544f144f2570a-0c48-4a39-ac03-bd068a13fd4b] DEBUG EntityEnclosingMethod.java (line 508) Request body sent
Errori del controller ViPR con l'output riportato di seguito:
vipr3 vipr3 controllersvc 2018-06-22 08:58:10,768 [199|checkFileSystemDependenciesInStorage|1246f9af-6340-4754-b2d6-ecb570f544f144f2570a-0c48-4a39-ac03-bd068a13fd4b] DEBUG Wire.java (line 70) << "<ResponsePacket xmlns="http://www.emc.com/schemas/celerra/xml_api">[\n]"
vipr3 vipr3 controllersvc 2018-06-22 08:58:10,768 [199|checkFileSystemDependenciesInStorage|1246f9af-6340-4754-b2d6-ecb570f544f144f2570a-0c48-4a39-ac03-bd068a13fd4b] DEBUG Wire.java (line 70) << " <Response>[\n]"
vipr3 vipr3 controllersvc 2018-06-22 08:58:10,768 [199|checkFileSystemDependenciesInStorage|1246f9af-6340-4754-b2d6-ecb570f544f144f2570a-0c48-4a39-ac03-bd068a13fd4b] DEBUG Wire.java (line 70) << " <Fault maxSeverity="error">[\n]"
vipr3 vipr3 controllersvc 2018-06-22 08:58:10,768 [199|checkFileSystemDependenciesInStorage|1246f9af-6340-4754-b2d6-ecb570f544f144f2570a-0c48-4a39-ac03-bd068a13fd4b] DEBUG Wire.java (line 70) << " <Problem messageCode="14227210241" facility="APL" component="API" message="APL subsystem query failed." severity="error">[\n]"
vipr3 vipr3 controllersvc 2018-06-22 08:58:10,768 [199|checkFileSystemDependenciesInStorage|1246f9af-6340-4754-b2d6-ecb570f544f144f2570a-0c48-4a39-ac03-bd068a13fd4b] DEBUG Wire.java (line 70) << " <Description>Appliance Layer (APL) subsystem that the XML API server talks to failed to execute a query. This indicates a problem with the APL subsystem in Control Station software.</Description>[\n]"
vipr3 vipr3 controllersvc 2018-06-22 08:58:10,769 [199|checkFileSystemDependenciesInStorage|1246f9af-6340-4754-b2d6-ecb570f544f144f2570a-0c48-4a39-ac03-bd068a13fd4b] DEBUG Wire.java (line 70) << " <Action>If the problem persists, collect support materials by running the /nas/tools/collect_support_materials script or the newer /nas/tools/automaticcollection script. Note any symptoms. If you require more information on the materials collection process, refer to the Problem Resolution Roadmap for Celerra, available on EMC Powerlink, or EMC Knowledgebase Support Solution number emc135846. For more information on this message, use the text from the error message's brief description or the message's ID to search the Knowledgebase on Powerlink. After logging in to Powerlink, go to Support > Knowledgebase Search > Support Solutions Search.</Action>[\n]"
Nei registri dei materiali di supporto dell'array VNX, si segnala che si è verificato un problema con le licenze SnapSure:
(cel_api.log) Jun 22, 15:12:24 APL reply is: < ?xml version="1.0" encoding="UTF-8" standalone="no" ?> < APLTask complete="true" description="Query checkpoints" failed="true" originator="username@localhost" xmlns="http://www.emc.com/schemas/celerra/apl_1.0"> <Statuses> <Status creationTime="1530623544" id="13422428162"> <MessageArgList> <MessageArg argName="license" argType="8"> <string>snapsure</string> </MessageArg> </MessageArgList> </Status> </Statuses> < /APLTask> Jun 22, 15:12:25 Creating API status --------------> Jun 22, 15:12:25 Diagnostics tag: 1646045cef9 com.emc.celerra.api.RequestException: com.emc.nas.ccmd.common.MessageInstanceImpl@50020001 at com.emc.celerra.api.apl.AbstractQuery.makeAplListCall(AbstractQuery.java:144)