AppSync: El mapeo de aplicaciones falló durante la búsqueda de volúmenes virtuales de VPLEX

Summary: AppSync no puede obtener la información de los volúmenes virtuales con wwn: de VPLEX debido a problemas en la consola de administración de 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 no puede obtener la información del volumen virtual con wwn:<wwn_id> desde el clúster de VPLEX debido a problemas en la consola de administración de VPLEX.
El comando AppSync falló:https://xxx.xx.xxx.xxx:443/vplex/export+storage-view+find HTTP/1.1
 
El error principal que se encuentra en el registro del servidor es:
 

Error al intentar actualizar las propiedades 'storage-views' en\n la exportación.\ncausa:        Infinito o NaN\n"
 

Los detalles relacionados con este error se encuentran en el registro del servidor, como se muestra aquí: 
 

<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

Este problema se relaciona con la consola de administración de VPLEX, la cual rechaza comandos válidos pasados desde AppSync a través de la API REST. Este es un problema conocido en VPLEX.

Actualmente se cree que el motivo del problema de NaN es que el código nativo de CST JNI no es seguro para subprocesos y corrompe los registros de FPU e interfiere con otros subprocesos de Java que necesitan usar la FPU (como para números dobles).

Resolution

Resolución permanente:
Este problema se resolvió en el código de VPLEX GeoSynchrony versión 6.0 Service Pack 1 parche 4 y versiones posteriores.

Solución alternativa:

  1. Reinicie la consola de administración de VPLEX.
  2. Vuelva a ejecutar el plan de servicio de AppSync.

Para obtener más detalles sobre cómo reiniciar el servicio de la consola de administración de VPLEX, consulte el artículo 000167777 de la base de conocimientos: Controlador ViPR : La creación de un LUN distribuido de VPLEX falla con el estado 524: Infinito o 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.