This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
tsm:tsm_tdpvmware_local_node [2021/01/01 21:25] 127.0.0.1 external edit |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== TDP for Virtual Environment pair nodes ====== | ||
- | https://www.ibm.com/support/knowledgecenter/SSERB6_8.1.0/ve.inst/t_ve_cfg_setmpnodeslnx.html | ||
- | |||
- | https://www.ibm.com/support/pages/configuration-mount-proxy-node-pair-fails-ans3144w-linux | ||
- | |||
- | https://www.ibm.com/support/pages/configuration-mount-proxy-node-pair-fails-ans3144w-windows | ||
- | |||
- | ===== Windows node config ===== | ||
- | |||
- | Configuration of Mount Proxy Node pair fails with ANS3144W - Windows | ||
- | |||
- | |||
- | Problem | ||
- | |||
- | The Tivoli Storage Manager for VMware UI is used to configure a Mount Proxy Node pair. The "Validate Selected Node" button is selected and the validation fails with the ANS3144W error for the Windows node | ||
- | Symptom | ||
- | |||
- | The following error is logged in the Status detail in the Tivoli Storage Manager for VMware UI : | ||
- | |||
- | ANS3144W The ISCSI service is not running. File level restore mount operations will not work. | ||
- | |||
- | The error is logged for the Windows node. | ||
- | Diagnosing The Problem | ||
- | |||
- | On the Windows machine that runs the Windows node, verify the status of the "Microsoft iSCSI Initiator" service in Windows. For example : | ||
- | |||
- | {{:tsm:windows_iscsi01.gif?650}} | ||
- | |||
- | In this example, it shows that the service is stopped. | ||
- | |||
- | You can also use the Microsoft "sc" command to verify the status of the service (MSiSCSI). For example : | ||
- | <cli prompt='>'> | ||
- | C:> sc query MSiSCSI | ||
- | SERVICE_NAME: MSiSCSI | ||
- | TYPE : 20 WIN32_SHARE_PROCESS | ||
- | STATE : 1 STOPPED | ||
- | WIN32_EXIT_CODE : 0 (0x0) | ||
- | SERVICE_EXIT_CODE : 0 (0x0) | ||
- | CHECKPOINT : 0x0 | ||
- | WAIT_HINT : 0x0 | ||
- | </cli> | ||
- | |||
- | In this example, it shows that the service is stopped. | ||
- | Resolving The Problem | ||
- | |||
- | On the Windows machine that runs the Windows node, start the "Microsoft iSCSI Initiator" service using the services panel or with the following Windows command : | ||
- | <cli prompt='>'> | ||
- | C:> sc start MSiSCSI | ||
- | </cli> | ||
- | |||
- | ===== Linux node config ===== | ||
- | |||
- | <cli prompt='>'> | ||
- | manu@manu-opensuse:~> systemctl list-unit-files | grep scsi | ||
- | iscsi.service enabled | ||
- | iscsid.service disabled | ||
- | iscsiuio.service disabled | ||
- | iscsid.socket enabled | ||
- | iscsiuio.socket disabled | ||
- | </cli> |