ViPR-kontroller: Pålegg om å fjerne en NFS-fil Systemet mislykkes
Summary: Sletting av et ViPR Controller-administrert NFS-filsystem mislykkes.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Dette er en ny implementering av VNX File i ViPR Controller.
Brukeren kan ikke slette et NFS-filsystem på et VNX-array i ViPR-kontrolleren.
Feil ved ViPR-kontrollergrensesnittet:
Brukeren kan ikke slette et NFS-filsystem på et VNX-array i ViPR-kontrolleren.
Feil ved ViPR-kontrollergrensesnittet:
[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-kontrolleren spør VNX (CheckpointQueryParams XML API)-knappen for å se etter alle øyeblikksbilder på hele matrisen.
Hvis SnapSure ikke er aktivert eller lisensiert på VNX-arrayet, fører dette til at API-spørringen mislykkes. Eksempel:
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 er en forutsetning for ViPR-kontroller i VNX-filmiljøer. Se Krav og informasjonsveiledning for virtuelt datasenter for ViPR-kontroller for mer informasjon.
Resolution
Aktiver SnapSure på VNX-arrayet:
- I Unisphere UI velger du navnet på kontrollstasjonen.
- Her får du hele menyen for VNX-klyngen. Til venstre ser du lisensundermenyen.
- Bekreft at det er merket av for SnapSure. Hvis den er validert, må du kontrollere at den er validert, og hvis den ikke er det, validere den.
Additional Information
Før du sletter filsystemet, spør ViPR Controller VNX (CheckpointQueryParams XML API)-knappen for å se etter alle øyeblikksbilder på hele matrisen.
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
ViPR-kontrollerfeil med utdataene nedenfor:
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]"
I støttematerialloggene for VNX Arrayet viser det at det er et problem med SnapSure-lisensiering:
(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)
Products
VNX/VNXeArticle Properties
Article Number: 000056911
Article Type: Solution
Last Modified: 20 Oct 2025
Version: 5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.