AppSync: Mappatura delle applicazioni non riuscita durante la ricerca di volumi virtuali VPLEX

Oversigt: AppSync non è in grado di ottenere le informazioni sui volumi virtuali con wwn: da VPLEX a causa di problemi della console di gestione VPLEX.

Denne artikel gælder for Denne artikel gælder ikke for Denne artikel er ikke knyttet til et bestemt produkt. Det er ikke alle produktversioner, der er identificeret i denne artikel.

Symptomer

AppSync non è in grado di ottenere le informazioni sul volume virtuale con wwn:<wwn_id> dal cluster VPLEX a causa di problemi della console di gestione VPLEX.
Comando AppSync non riuscito:https://xxx.xx.xxx.xxx:443/vplex/export+storage-view+find HTTP/1.1
 
L'errore principale riscontrato nel registro del server è:
 

Errore nel tentativo di aggiornare le proprietà 'storage-views' su\n Esporta.\ncausa:        Infinito o NaN\n"
 

I dettagli relativi a questo errore sono disponibili nel registro del server, come illustrato di seguito: 
 

<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)



Årsag

Questo problema è correlato alla console di gestione VPLEX che rifiuta i comandi validi passati da AppSync tramite l'API REST. Si tratta di un problema noto in VPLEX.

Si ritiene attualmente che il motivo del problema NaN sia il codice nativo JNI CST che non è thread-safe e corrompe i registri FPU e interferisce con altri thread Java che devono utilizzare l'FPU (ad esempio per i numeri doppi).

Løsning

Risoluzione permanente:
Questo problema è stato risolto nel codice VPLEX GeoSynchrony versione 6.0, Service Pack 1, Patch 4 e versioni successive.

Soluzione:

  1. Riavviare la console di gestione VPLEX.
  2. Eseguire nuovamente il piano di servizio AppSync.

Per ulteriori informazioni su come riavviare il servizio della console di gestione VPLEX, consultare l'articolo 000167777 della Knowledge Base: Controller ViPR : La creazione di una LUN distribuita VPLEX ha esito negativo con stato 524: Infinito o NaN 


Flere oplysninger


 
 

Berørte produkter

AppSync

Produkter

AppSync, VPLEX Series
Artikelegenskaber
Artikelnummer: 000057099
Artikeltype: Solution
Senest ændret: 09 sep. 2025
Version:  4
Find svar på dine spørgsmål fra andre Dell-brugere
Supportservices
Kontrollér, om din enhed er dækket af supportservices.