> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/deploy/connect-hosts/host-connectivity.md).

# Host Connectivity

Learn how hosts connect to Silk storage over iSCSI, access mapped volumes, and use multiple paths for redundancy.

A DataPod is ready for a workload when its hosts can reach the DataPod, see the volumes assigned to them, and maintain access if a storage path fails. Host connectivity brings those pieces together.&#x20;

Application and database hosts connect over iSCSI to targets on the DataPod's c.nodes. Volume mappings determine which volumes each host can see. With host-side multipathing, the operating system can continue accessing a mapped volume through another available path if one fails.&#x20;

## Plan the host network path

Connect hosts to the iSCSI data port (`dataport01`, which sits on the Data 1 subnet) on each c.node. Flex configures these ports for iSCSI during deployment and scale-out. In the SDP Management Console, go to **Connectivity > IP Data Ports** to find the target IP address. Replication traffic uses a separate data port (`dataport02`) and subnet (Data 2).&#x20;

Verify reachability in both directions:

{% columns %}
{% column %}
The **host** needs a route to the iSCSI target IPs.
{% endcolumn %}

{% column %}
The **DataPod** needs a return path to the host subnet through the iSCSI network.
{% endcolumn %}
{% endcolumns %}

Each c.node's default route uses its management interface, so the DataPod needs a static route to send iSCSI traffic back to the host network. Go to **Connectivity > Static Routes** and create a route with the following values:

* **Destination subnet address and mask:** The host network's subnet.&#x20;
* **Gateway IP address:** The gateway of the DataPod's `dataport01` network.

Apply the route to all c.nodes so every storage path can reach the host. If a host also needs to reach the DataPod's management UI or API, plan that access separately.&#x20;

## Register hosts and map volumes

Register each host in the SDP Management Console using its iSCSI Qualified Name (IQN). The IQN identifies the host's iSCSI initiator. If your environment uses Challenge-Handshake Authentication Protocol (CHAP), configure a CHAP profile in the DataPod and the corresponding credentials on the host. With one-way CHAP, the DataPod authenticates the host. With mutual CHAP, the host also authenticates the DataPod.&#x20;

Map each volume to the hosts that need access. You can select a volume group to map all of its volumes at once. For clustered workloads where multiple hosts need the same volumes, add the hosts to a host group and map the volumes to the group. **A host can belong to only one host group.**&#x20;

## Establish and verify redundant paths

Use the host configuration guidance for your operating system to configure multipathing and establish iSCSI sessions.&#x20;

{% tabs %}
{% tab title="Windows" %}
Use the `SilkiSCSI` PowerShell module, available on [Silk's GitHub](https://github.com/silk-us/Silk-iSCSI) and the [PowerShell Gallery](https://www.powershellgallery.com/packages/silkiscsi).
{% endtab %}

{% tab title="Linux" %}
Use `iscsiadm` with native multipathing.
{% endtab %}
{% endtabs %}

Distribute sessions across the c.nodes so the host has storage paths through multiple nodes. Rebalance sessions when c.nodes are added or removed.&#x20;

An active iSCSI session confirms that the host has connected to a c.node. Verify that the storage is usable:

{% columns %}
{% column %} <i class="fa-database">:database:</i>

**On the DataPod**, go to **Connectivity > iSCSI Sessions**. Check the active session count for the host across the c.nodes and compare it with the intended distribution.

For details on reading the session counts, see **iSCSI Sessions** in the [SDP Management Console User Guide](https://support.silk.us/sys/document/preview/Silk-Cloud-Platform-User-Guide-240223011600..pdf) (requires Silk Support Portal access).&#x20;
{% endcolumn %}

{% column %} <i class="fa-server">:server:</i>

**On the host**, verify that the expected mapped volumes are visible and that the operating system reports the expected paths for each volume.&#x20;

The console shows active sessions by host and c.node. The host shows which paths are available for each device.&#x20;
{% endcolumn %}
{% endcolumns %}

## Related resources

{% content-ref url="/pages/t3ez4YDccYYKuyPiGfgZ" %}
[Plan AWS Networking and Connectivity](/deploy/deploy-on-aws/plan-aws-networking-and-connectivity.md)
{% endcontent-ref %}

{% content-ref url="/pages/rjP9aCn6dC8QQtcPsR9y" %}
[Plan Azure Networking and Connectivity](/deploy/deploy-on-azure/plan-azure-networking-and-connectivity.md)
{% endcontent-ref %}

{% content-ref url="/spaces/jI1rjszhUJU6LG8J53d0/pages/yH4ng7yl0HUw4u0AuGya" %}
[Volumes and Volume Groups](/learn/data-management-concepts/volumes-and-volume-groups.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.silk.us/deploy/connect-hosts/host-connectivity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
