Controlador do ViPR: O pedido para remover um file system NFS falha

Summary: Falha na exclusão de um file system NFS gerenciado pelo ViPR Controller.

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.
Check out other resources

Symptoms

Esta é uma nova implementação do VNX File no ViPR Controller.

O usuário não consegue excluir um file system NFS em um array VNX no ViPR Controller.

Erros da interface do usuário do ViPR Controller: 
[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

O ViPR Controller consulta o VNX (CheckpointQueryParams XML API) para verificar todos os snapshots em todo o array.

Se o SnapSure não estiver habilitado ou licenciado no array VNX, isso causará falha na consulta à API. Por exemplo:

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

O SnapSure é um pré-requisito para o ViPR Controller em ambientes de arquivos VNX. Consulte o Guia de requisitos e informações do data center virtual do ViPR Controller para obter mais detalhes. 

 

Resolution

Habilite o SnapSure no array VNX:
  1. Na interface do usuário do Unisphere, selecione o nome da Control Station.
  2. Aqui, você obtém o menu completo do cluster do VNX. À esquerda, você verá o submenu licença.
  3. Verifique se a caixa de seleção SnapSure está marcada. Se estiver, verifique se ele está validado e, se não estiver, valide-o.

Additional Information

Antes de excluir o file system, o ViPR Controller consulta o VNX (CheckpointQueryParams XML API) para verificar todos os snapshots em todo o 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

Erros do ViPR Controller com o resultado abaixo:

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]"

Nos registros do material de suporte do array VNX, ele mostra que há um problema com o licenciamento do 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)

Products

VNX/VNXe
Article 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.