Windows Target Environment Discovery or Refresh Fails With IO Write Error (KBA1826)
KBA
KBA#1826Applicable Delphix Versions
|
Major Release |
Sub Releases |
| 5.3 | 5.3.0.0 |
| 5.2 | 5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1 |
|
5.1 |
5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0 |
|
5.0 |
5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1 ,5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4 |
|
4.3 |
4.3.1.0, 4.3.2.0, 4.3.2.1, 4.3.3.0, 4.3.4.0, 4.3.4.1, 4.3.5.0 |
|
4.2 |
4.2.0.0, 4.2.0.3, 4.2.1.0, 4.2.1.1, 4.2.2.0, 4.2.2.1, 4.2.3.0, 4.2.4.0 , 4.2.5.0, 4.2.5.1 |
|
4.1 |
4.1.0.0, 4.1.2.0, 4.1.3.0, 4.1.3.1, 4.1.3.2, 4.1.4.0, 4.1.5.0, 4.1.6.0 |
|
4.0 |
4.0.0.0, 4.0.0.1, 4.0.1.0, 4.0.2.0, 4.0.3.0, 4.0.4.0, 4.0.5.0, 4.0.6.0, 4.0.6.1 |
Issue
During a windows target host environment discovery and subsequent refresh, a failure occurs early in the workflow. The job will fail after this error occurs, involving an io write error during the first attempt to write scripts to the DelphixConnector location for the discovery:
java.net.SocketException: Connection timed out (Read failed)"] An IO error occurred while attempting to write a remote file on host "Windows_Host_Name"
The environment remains on the environments list. Attempts to delete it fail with a timeout and additional information:
java.net.SocketException: Connection timed out (Read failed)}"]
Attempt to remove persistent iSCSI target "iqn.2008-07.com.delphix:02:3122ea8c-49b0-eac1-d502-d456a63ac856" has failed on host "Windows_Host_Name" : exception.ccc.writefile.failed {Windows_Host_Name
java.net.SocketException: Connection timed out (Read failed)}
Troubleshooting
The errors are caused by something not configured properly. In this situation, an MTU mismatch was the cause of the issue.
The Delphix engine interface servicing the Windows host configured MTU as 9000 bytes, so called Jumbo frames.
The Windows host MTU configured for 1500.
This can be tested with the ping command from the Windows host to the Delphix engine:
ping Delphix_Engine_Ip_Address -f -l 8000
Example output:
Pinging Delphix_Engine_Ip_Address with 8000 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Ping statistics for Delphix_Engine_Ip_Address:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
It's a good indication the MTUs mismatch.
Resolution
Correct the situation so the MTUs will match. If Jumbo frames are desired, enable Jumbo frames on the Windows network adapter and all network hops between the host and the Delphix Engine.