Iscsi an Error Occurred Please Try Again

Configuring SQL Server Hosts to Connect to the Delphix Engine Over Some other Network (KBA1792)

Last updated
Relieve as PDF

Applicable Delphix Versions

Click hither to view the versions of the Delphix engine to which this commodity applies

Major Release	All Sub Releases
six.0	vi.0.0.0, six.0.1.0, half-dozen.0.1.i, 6.0.2.0, 6.0.2.i, 6.0.3.0, half dozen.0.3.1, 6.0.four.0, 6.0.4.i, 6.0.4.2, half dozen.0.5.0, 6.0.6.0, vi.0.vi.i, 6.0.seven.0
5.3	5.three.0.0, 5.iii.0.1, 5.3.0.2, five.iii.0.three, 5.3.i.0, 5.3.1.1, 5.3.1.two, five.3.2.0, five.3.3.0, v.3.3.1, 5.3.iv.0, v.three.five.0 5.iii.6.0, five.3.vii.0, 5.3.7.1, v.3.8.0, 5.3.viii.1, 5.iii.ix.0
v.2	5.2.2.0, 5.2.2.1, five.two.3.0, 5.2.4.0, 5.two.v.0, 5.ii.v.one, 5.2.6.0, 5.ii.6.1
5.1	5.1.0.0, 5.1.1.0, 5.1.two.0, five.1.3.0, v.ane.iv.0, 5.1.5.0, five.1.5.i, v.1.6.0, five.1.7.0, five.1.8.0, 5.1.8.i, 5.1.ix.0, 5.1.10.0
5.0	5.0.i.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.ii.3, five.0.three.0, 5.0.3.1, 5.0.four.0, 5.0.4.i ,5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.iii, 5.0.5.iv

Summary

Occasionally, information technology may be necessary to change the network that the Delphix Engine uses for advice with SQL Server target hosts. For example, the Delphix Engine may be configured with a second network interface to let communication over a storage network or dedicated switch.

This document describes the steps required to allow the use of the new network. This involves immigration the iSCSI configuration on the Target host, and reconfiguring the host using Delphix Engine'due south Management interface.

Delight note that it is not currently possible to "split" communication, so that iSCSI action takes place over 1 network while JDBC action occurs over another. All traffic betwixt the Delphix Engine and the Target host will flow through the new network.

Prerequisites

Before proceeding with the steps in this certificate:

The new network adapters must exist configured on the Target host, including having an IP address assigned
The new network adapter must exist added and configured on the Delphix Engine, using the Server Setup interface

Configuring Connectivity Over Another Network

1. Exam connectivity using new devices

In one case the network is configured, validate that the advisable connectivity is in place.

The Delphix Engine's Network Operation Tool (available in the CLI, or the GUI since 5.2) will allow you lot to exam that the target'southward new IP address is reachable
The Target should exist able to ping the Delphix Engine's new IP accost
The Target must be permitted to connect to the Delphix Engine's new IP accost using:
- TCP port 3260 (iSCSI)
- TCP port 50001 (optional, for network throughput testing)
The Delphix Engine must be permitted (both through the Network and by the Windows Firewall) to reach the Target'southward new IP address using:
- TCP Port 9100 (Delphix Connector communication)
- TCP Port 8415 (Delphix Session Protocol, or DSP)
- ICMP (for ping/traceroute)
- TCP Port 50001 (optional, for network throughput testing)

Storage network interfaces are likely to utilize the "Public" network profile in Windows, and existing Windows Firewall rules may demand to be modified to allow this communication.

Annotation that port 50001 is just in use while network throughput tests are running.

two. Disable all VDBs

To review all VDBs fastened to a target, use the Databases tab of the Manage → Environments screen:

Each Staging Database and VDB should be Disabled from the Manage → Datasets screen:

This step tin besides exist done using the CLI, Delphix Toolkit, or delphixpy.

3. Open the iSCSI Initiator control panel applet

Connect to the Target host (for example via Remote Desktop), and launch the iSCSI Initiator command panel applet from the Start Bill of fare or via iscsicpl.exe.

If there are multiple Delphix Engines or other iSCSI Devices connected to the host, take care when making any changes.

The Volumes and Devices, RADIUS and Configuration tabs can be left unmodified. The Volumes and Devices tab does non contain whatever data specific to IP address, and will likely be empty after the VDBs has been disabled.

four. Remove the Favorite Target

If there is only one Delphix Engine connected to this target, information technology tin be removed from the Favorite Targets tab past selecting it and clicking the Remove button.

If there are multiple targets listed, you can confirm the correct iSCSI target past selecting each and clicking Details. The target to be removed should friction match the Delphix Engine'southward current IP address.

If there are multiple devices, make a annotation of the Target proper name of the target y'all are removing, as it will be used in the adjacent step.

5. Disconnect the Target

Switch to the Targets tab and Disconnect from the Delphix Engine's iSCSI Target. The Name should match the Target Name that was removed from the Favorite Targets tab.

If prompted to disconnect from any agile sessions, select Yep:

6. Remove the Target Portal

Switch to the Discovery tab, and Remove the Target portal that matches the Delphix Engine's existing IP address:

This should complete without prompting, and will also remove the portal from the listing in the Targets tab.

7. Alter the Host Address in the Delphix Engine

Using the Delphix Engine'southward Direction Interface, open the Manage → Environments screen and select the Target host.

To modify the Host Accost for the surround, use the Edit (Pencil) icon adjacent to the Attributes panel:

Update the Host Address to reflect the new IP accost, so use the Relieve (Tick) icon to confirm the change:

This will automatically trigger an activeness to Refresh the Environment. The refresh process includes steps to configure the iSCSI Target, and verify that it is reachable.

8. Enable VDBs

From the Manage → Datasets screen, Enable each dSource and VDB that was Disabled in Pace 2.

9. Exam VDB Behavior

In one case the VDBs have been successfully enabled, ensure that they respond correctly to queries, and are providing the latency and throughput that you expect from the new network.

Troubleshooting Errors

The following warnings or errors may occur while attempting to reconfigure the Target Host or Delphix Engine.

Error: "Failed to add or update the iSCSI persistent login target"

When attempting to change the Host Accost of an Environment, yous may receive the error:

Failed to add together or update the iSCSI persistent login target on host "<HOSTNAME>".

This suggests that some configuration of the iSCSI Target is still present on the Target host. Ensure that all VDBs and dSources which use the Target are disabled, and attempt Step 3 again.

Error: "An IO error occurred while attempting to write a remote file on host <HOSTNAME>."

When attempting to alter the Host Address of an Surroundings, you may receive the fault:

An IO error occurred while attempting to write a remote file on host <HOSTNAME>.

This suggests that network configuration may be inconsistent betwixt the Delphix Engine and the Target host. Ensure that the Jumbo Frames configuration is consistent between the Delphix Engine, the Target host, and all intermediate network devices.

partlowablemody.blogspot.com

Source: https://support.delphix.com/Delphix_Virtualization_Engine/MSSQL_Server/Configuring_SQL_Server_Hosts_to_Connect_to_the_Delphix_Engine_Over_Another_Network_(KBA1792)