ViPR Controller: Order to Remove an NFS file System Fails
Summary: Deletion of a ViPR Controller managed NFS file system fails.
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
This is a new implementation of VNX File within ViPR Controller.
The user is unable to delete an NFS file system on a VNX array in the ViPR Controller.
ViPR Controller UI errors:
The user is unable to delete an NFS file system on a VNX array in the ViPR Controller.
ViPR Controller UI errors:
[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 queries the VNX (CheckpointQueryParams XML API) to check for all snapshots on the entire array.
If SnapSure is not enabled or licensed on the VNX array, this causes the API query to fail. For example:
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 is a prerequisite for ViPR Controller in VNX file environments. See the ViPR Controller Virtual Data Center Requirements and Information Guide for more details.
Resolution
Enable SnapSure on the VNX Array:
- In the Unisphere UI, select the name of the Control Station.
- Here, you get the full menu for the VNX cluster. On the left, you see the license submenu.
- Verify if the SnapSure checkbox is checked. If it is, check that it is validated, and if it is not, validate it.
Additional Information
Before deleting the file system, ViPR Controller queries the VNX (CheckpointQueryParams XML API) to check for all snapshots on the entire 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
ViPR Controller errors with the output below:
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]"
In the VNX Array support materials logs, it shows that there is an issue with SnapSure licensing:
(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.