AppSync: Mapowanie aplikacji nie powiodło się podczas znajdowania woluminów wirtualnych VPLEX

Summary: AppSync nie jest w stanie uzyskać informacji o woluminach wirtualnych za pomocą wwn: z VPLEX z powodu problemów z konsolą zarządzania 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.

Symptoms

Usługa AppSync nie może uzyskać informacji o woluminie wirtualnym za pomocą polecenia wwn:<wwn_id> z klastra VPLEX ze względu na problemy z konsolą zarządzania VPLEX.
Polecenie AppSync nie powiodło się:https://xxx.xx.xxx.xxx:443/vplex/export+storage-view+find HTTP/1.1
 
Podstawowy błąd znaleziony w dzienniku serwera to:
 

Niepowodzenie próby odświeżenia właściwości "storage-views" na\n Eksporcie.\nPrzyczyna:        Nieskończony lub NaN\n"
 

Szczegółowe informacje na temat tego błędu można znaleźć w dzienniku serwera, jak widać poniżej: 
 

<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

Ten problem jest związany z konsolą zarządzania VPLEX, która odrzuca prawidłowe polecenia przekazywane z AppSync za pośrednictwem interfejsu REST API. Jest to znany problem w VPLEX.

Obecnie uważa się, że przyczyną problemu z NaN jest to, że natywny kod CST JNI nie jest bezpieczny wątkowo i uszkadza rejestry FPU oraz zakłóca inne wątki java, które muszą używać FPU (na przykład w przypadku podwójnych liczb).

Resolution

Trwałe rozwiązanie:
Ten problem został rozwiązany w kodzie VPLEX GeoSynchrony w wersji 6.0 Service Pack 1 poprawki 4 lub nowszej.

Obejście:

  1. Uruchom ponownie konsolę zarządzania VPLEX.
  2. Uruchom ponownie plan usługi AppSync.

Więcej informacji na temat ponownego uruchamiania usługi VPLEX Management Console można znaleźć w artykule bazy wiedzy 000167777: Kontroler ViPR: Utworzenie rozproszonej jednostki LUN VPLEX kończy się niepowodzeniem ze stanem 524: Nieskończoność lub 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.