Loading...
Loading...
The SyncOnce operation from CMware SRM is not communicating with XtremIO XMS. VMware SRM logs show RestAPI commands failing with the following error: Object reference not set to an instance of an object The rest.log file on XMS shows HTTP code 200, which indicates that communication is functioning correctly. The following entries are from the VMware SRA logs: 2020-05-21 17:01:07.481: [error] 'xsra.RestApi.restGet' /home/srm/sra-linux/QueryCommonRequest.cs 441 sra-linux (Process id=2560) (Thread id=8)]: Resource temporarily unavailable 2020-05-21 17:01:07.486: [info] 'xsra.QueryCommonRequest.QueryCommonErrorResponse' /home/srm/sra-linux/QueryCommonRequest.cs 457 sra-linux (Process id=2560) (Thread id=8)]: Commence: construct common error response xml operation. 2020-05-21 17:01:07.490: [info] 'xsra.QueryCommonRequest.ConstructErrorElement' /home/srm/sra-linux/QueryCommonRequest.cs 566 sra-linux (Process id=2560) (Thread id=8)]: Commence: ConstructErrorElement. 2020-05-21 17:01:07.619: [error] 'xsra.SyncOnce.ConstructOutputXml' /home/srm/sra-linux/QueryCommonRequest.cs 441 sra-linux (Process id=2560) (Thread id=1)]: Object reference not set to an instance of an object. The following entries are from the XtremIO_SR_syncOnce__#.log file and show a connectivity failure: [2020-05-22 15:47:28.497: [error] 'xsra.RestApi.restGet' /home/srm/sra-linux/QueryCommonRequest.cs 441 sra-linux (Process id=328) (Thread id=10)]: Resource temporarily unavailable [2020-05-22 15:47:28.592: [warning] 'xsra.RestApi.restGet' /home/srm/sra-linux/QueryCommonRequest.cs 441 sra-linux (Process id=328) (Thread id=10)]: host 'https://xms-xms-its-02/api/json/v3/types/snapshot-sets/?full=1' doesn't response and SRA cannot ping that address, need to check network parameters, firewall and other settings related to networking, maybe host is down The following entries are from rest.log dile on XMS and show HTTP code 200, which indicates successful communication: 2020-05-21 12:19:38,292 - RestLogger[2564:ca53::RST27e22d] - INFO - rest_server::log_request:122 - REST call: <Request at 0x7fd2217d67a0 method=GET uri=/json/v2/types/clusters?name=xms-xio-984 clientproto=HTTP/1.1> with args {'name': ['aus-xio-983']} and content from user LogicMonitor @ 10.127.124.80 2020-05-21 12:19:38,543 - RestLogger[2564:ca53::RST27e22d] - INFO - rest_server::log_response:136 - REST <Request at 0x7fd2217d67a0 method=GET uri=/json/v2/types/clusters?name=xms-xio-984 clientproto=HTTP/1.1> respond with code 200 2020-05-21 12:20:38,292 - RestLogger[2564:ca53::RST90389f] - INFO - rest_server::log_request:122 - REST call: <Request at 0x7fd221e60bd8 method=GET uri=/json/v2/types/clusters?name=xms-xio-984 clientproto=HTTP/1.1> with args {'name': ['aus-xio-983']} and content from user LogicMonitor @ 10.127.124.80 2020-05-21 12:20:38,559 - RestLogger[2564:ca53::RST90389f] - INFO - rest_server::log_response:136 - REST <Request at 0x7fd221e60bd8 method=GET uri=/json/v2/types/clusters?name=xms-xio-984 clientproto=HTTP/1.1> respond with code 200
The XMS replication settings may be configured with the XMS-Alias instead of the fully qualified domain name (FQDN). Check the peer protection XMS from each cluster to ensure that the settings are correct. In the following example, the XMS-Alias is not set to the FQDN: xmcli (admin)> show-remote-protection-peer-xms XMS-Alias Index SW-Version IP-Address XMS-Connectivity-State xms-source-bot-02 0 6.2.1-36 172.31.5.230 connected xms_target-bot-02 1 6.2.1-36 172.31.3.230 connected The XMS-Alias must be configured with the FQDN, as shown in the following example: xmcli (admin)> show-remote-protection-peer-xms XMS-Alias Index SW-Version IP-Address XMS-Connectivity-State xms-source-bot-02.q2ac.xiolab.lab.emc.com 0 6.2.1-36 172.31.5.230 connected xms_target-bot-02.q2ac.xiolab.lab.emc.com 1 6.2.1-36 172.31.3.230 connected
Modify the XMS-Alias to use the FQDN. The following is an example of the command: xmcli (tech)> modify-remote-protection-peer-xms xms-alias-name="xms-source-bot-02" new-xms-alias-name="xms-source-bot-02.xiolab.lab.emc.com" To register from the peer XMS using the UI, perform the following steps: From the top menu bar, select System Settings > Remote Protection Settings to open the Remote Protection Settings Window. From the Remote Protection Settings menu, select the XMS Peers option. In the XMS Peers Table menu, click New to open the Register XMS dialog. Provide the XMS name, IP address, and credentials. Click Register XMS .
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.