AppSync : Échec du mappage des applications lors de la recherche de volumes virtuels VPLEX

Summary: AppSync n’est pas en mesure d’obtenir les informations sur les volumes virtuels avec WWN : à partir de VPLEX en raison de problèmes de console de gestion VPLEX.

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

AppSync n’a pas pu obtenir les informations de volume virtuel avec wwn :<wwn_id> à partir du cluster VPLEX en raison de problèmes liés à la console de gestion VPLEX.
Échec de la commande AppSync :https://xxx.xx.xxx.xxx:443/vplex/export+storage-view+find HTTP/1.1
 
L’erreur principale détectée dans le journal du serveur est la suivante :
 

Échec de la tentative d’actualisation des propriétés 'storage-views' sur\n Exporter.\nCause :        Infini ou NaN\n"
 

Les détails concernant cette erreur se trouvent dans le journal du serveur, comme indiqué ici : 
 

<date>  10:07:20.697 INFO [Thread-404] [com.emc.archway.restclient.RESTClient] [xxxx] [] executeRequest: executing POST: POST https://xxx.xx.xxx.xxx:443/vplex/export+storage-view+find HTTP/1.1
<date>  10:07:20.822 INFO [Thread-404] [com.emc.archway.restclient.RESTClient] [xxxx] [] executeRequest: Response Status Line: HTTP/1.1 541
<date>  10:07:20.822 ERROR [Thread-404] [com.emc.archway.restclient.RESTClientRequest] [xxxx] [] Response is
<date>  10:07:20.822 ERROR [Thread-691 (HornetQ-client-global-threads-739147480)] [com.emc.archway.service.vplex.VPLEXClient] [xxxx] [] Exception Occurred: RESTClientUnexpectedResponseCodeException, Message: {    "response": {        "context": null,        "message": "export storage-view find -c /clusters/cluster-1 -v VPD83T3:<wwn_id> ",        "exception": "export        Evaluation of <<export storage-view find -c\nstorage-view  /clusters/cluster-1 -v\nfind:         VPD83T3:<wwn_id> >> failed.\ncause:        Command execution failed.\ncause:        com.emc.vplex.smsv2.business.BusinessException: Failure\n              attempting to refresh properties 'storage-views' on Export.\ncause:        Failure attempting to refresh properties 'storage-views' on\n              Export.\ncause:        Infinite or NaN\n",        "custom-data": null    }}
<date>  10:07:20.822 ERROR [Thread-691 (HornetQ-client-global-threads-739147480)] [com.emc.archway.service.vplex.VPLEXClient] [xxxx] [] +++The following stack trace is abbreviated.+++
<date>  10:07:20.822 ERROR [Thread-691 (HornetQ-client-global-threads-739147480)] [com.emc.archway.service.vplex.VPLEXServiceBean] [xxxx] [] Exception Occurred: VPLEXRequestFailedException, Message: {    "response": {        "context": null,        "message": "export storage-view find -c /clusters/cluster-1 -v VPD83T3:<wwn_id> ",        "exception": "export        Evaluation of <<export storage-view find -c\nstorage-view  /clusters/cluster-1 -v\nfind:         VPD83T3:<wwn_id> >> failed.\ncause:        Command execution failed.\ncause:        com.emc.vplex.smsv2.business.BusinessException: Failure\n              attempting to refresh properties 'storage-views' on Export.\ncause:        Failure attempting to refresh properties 'storage-views' on\n              Export.\ncause:        Infinite or NaN\n",        "custom-data": null    }}
<date>  10:07:20.869 ERROR [Thread-691 (HornetQ-client-global-threads-739147480)] [com.emc.archway.service.vplex.VPLEXServiceBean] [xxxx] [] com.emc.archway.service.vplex.VPLEXClient.sendSingleVplexRequest(VPLEXClient.java:206) [top 3 frames]
<date>  10:07:20.869 ERROR [Thread-691 (HornetQ-client-global-threads-739147480)] [com.emc.archway.service.vplex.VPLEXServiceBean] [xxxx] [] com.emc.archway.service.vplex.VPLEXServiceBean.executeCLICommand(VPLEXServiceBean.java:1161) [top 3 frames]
<date>  10:07:20.869 ERROR [Thread-691 (HornetQ-client-global-threads-739147480)] [com.emc.archway.service.vplex.VPLEXServiceBean] [xxxx] [] com.emc.archway.service.vplex.VPLEXServiceBean.getStorageViewsInfosContainingWwn(VPLEXServiceBean.java:1418) [top 3 frames]
<date>  10:07:20.869 ERROR [Thread-691 (HornetQ-client-global-threads-739147480)] [com.emc.archway.service.vplex.VPLEXServiceBean] [xxxx] [] com.emc.archway.service.vplex.VPLEXServiceBean.getVirtualVolumeIdFromWwn(VPLEXServiceBean.java:914)
<date>  10:07:21.088 INFO [Thread-691 (HornetQ-client-global-threads-739147480)] [com.emc.archway.service.vplex.VPLEXServiceBean] [xxxx] [] VPLEXRequestFailedException while finding virtual volume with wwn:<wwn_id>  in cluster:cluster-1 error:{    "response": {        "context": null,        "message": "export storage-view find -c /clusters/cluster-1 -v VPD83T3:<wwn_id> ",        "exception": "export        Evaluation of <<export storage-view find -c\nstorage-view  /clusters/cluster-1 -v\nfind:         VPD83T3:<wwn_id> >> failed.\ncause:        Command execution failed.\ncause:        com.emc.vplex.smsv2.business.BusinessException: Failure\n              attempting to refresh properties 'storage-views' on Export.\ncause:        Failure attempting to refresh properties 'storage-views' on\n              Export.\ncause:        Infinite or NaN\n",        "custom-data": null    }}
<date>  10:07:21.635 INFO [Thread-691 (HornetQ-client-global-threads-739147480)] [com.emc.archway.service.vplex.VPLEXServiceBean] [xxxx] [] VPLEXRequestFailedException while finding virtual volume with wwn:<wwn_id>  in cluster:cluster-1 error:{    "response": {        "context": null,        "message": "export storage-view find -c /clusters/cluster-1 -v VPD83T3:<wwn_id> ",        "exception": "export        Evaluation of <<export storage-view find -c\nstorage-view  /clusters/cluster-1 -v\nfind:         VPD83T3:<wwn_id> >> failed.\ncause:        Command execution failed.\ncause:        com.emc.vplex.smsv2.business.BusinessException: Failure\n              attempting to refresh properties 'storage-views' on Export.\ncause:        Failure attempting to refresh properties 'storage-views' on\n              Export.\ncause:        Infinite or NaN\n",        "custom-data": null    }}
<date>  10:07:21.807 INFO [Thread-691 (HornetQ-client-global-threads-739147480)] [com.emc.archway.service.eventservice.EventServiceBean] [xxxx] [] EVENT [VNX_000072]: 172.xx.xx.xx\E:\ were mapped to array CKM00xxxx. If the array is a VNX, XtremIO, VPLEX Cluster, VNXe or Unity array, register CKM00xxxxxx. If the array is a VMAX array, register EMC SMI-S Provider managing the VMAX Array.(METADATA: TYPE-INFO, TIME-2017-06-13 10:07:21.807+0100NATIVETIME-2017-06-13 10:07:21.807+0100, HOST-xxxx, PHASE-Application mapping, THREAD=Thread-691 (HornetQ-client-global-threads-739147480), USER-j.leslie, CATEGORY-GENERIC, SESSIONID-1yZV80s43ZbQGSyjn4RQ6zxO6fwKc1Y2UJD-d8aG)
<date>  10:07:21.872 INFO [Thread-691 (HornetQ-client-global-threads-739147480)] [com.emc.archway.service.eventservice.EventServiceBean] [xxxx] [] EVENT [GENL_000044]: The following application items could not be mapped to any configured storage system: xxxx-SQL-01:ReportServerTempDB.Register the required storage system in AppSync.(METADATA: TYPE-WARNING, TIME-2017-06-13 10:07:21.872+0100NATIVETIME-2017-06-13 10:07:21.872+0100, HOST-xxxx, PHASE-Application mapping, THREAD=Thread-691 (HornetQ-client-global-threads-739147480), USER-j.leslie, CATEGORY-GENERIC, SESSIONID-1yZV80s43ZbQGSyjn4RQ6zxO6fwKc1Y2UJD-d8aG)
<date>  10:07:21.888 INFO [Thread-691 (HornetQ-client-global-threads-739147480)] [com.emc.archway.service.eventservice.EventServiceBean] [xxxx] [] EVENT [SPP_000037]: Cannot determine the storage type where application xxxx-SQL-01:ReportServerTempDB resides. Verify if the application is located on a supported EMC storage that has been added to AppSync.(METADATA: TYPE-ERROR, TIME-2017-06-13 10:07:21.872+0100NATIVETIME-2017-06-13 10:07:21.872+0100, HOST-xxxx, PHASE-Application mapping, THREAD=Thread-691 (HornetQ-client-global-threads-739147480), USER-j.leslie, CATEGORY-GENERIC, SESSIONID-1yZV80s43ZbQGSyjn4RQ6zxO6fwKc1Y2UJD-d8aG)



Cause

Ce problème est lié au fait que la console de gestion VPLEX rejette les commandes valides transmises depuis AppSync via l’API REST. Il s’agit d’un problème connu dans VPLEX.

On pense actuellement que la raison du problème NaN est que le code natif CST JNI n’est pas thread-safe et corrompt les registres FPU et interfère avec d’autres threads Java qui ont besoin d’utiliser le FPU (par exemple pour les nombres doubles).

Resolution

Solution définitive :
Ce problème est résolu dans le code VPLEX GeoSynchrony version 6.0 Service Pack 1 correctif 4 et versions ultérieures.

Contournement:

  1. Redémarrez la console de gestion VPLEX.
  2. Exécutez à nouveau le plan de service AppSync.

Pour plus d’informations sur le redémarrage du service VPLEX Management Console, reportez-vous à l’article 000167777 de la base de connaissances : ViPR Controller : La création d’une LUN distribuée VPLEX échoue avec l’état 524 : Infini ou NaN 


Additional Information


 
 

Affected Products

AppSync

Products

AppSync, VPLEX Series
Article Properties
Article Number: 000057099
Article Type: Solution
Last Modified: 17 أبريل 2026
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.