> For the complete documentation index, see [llms.txt](https://docs.vergeos-demo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vergeos-demo.com/run-the-platform/storage/fibre-channel.md).

# Using Fibre Channel Storage with vSAN

## Overview

VergeOS vSAN supports the use of Fibre Channel (FC) LUNs as storage devices within its tiered architecture. This enables seamless integration with your existing SAN infrastructure while benefiting from vSAN's native performance, redundancy, and efficiency.

{% hint style="info" %}
**Physical Disks vs. Fibre Channel LUNs**

While VergeOS vSAN supports Fibre Channel LUNs, **Verge.io recommends using physical disks directly attached to nodes** for optimal performance and simplicity. Physical disks provide:

* **Simpler configuration** - No FC zoning, HBA management, or SAN coordination required
* **Better performance** - Direct access without SAN overhead and network bottlenecks
* **Lower complexity** - Fewer failure points and easier troubleshooting
* **Cost efficiency** - No need for FC infrastructure, HBAs, or SAN licensing

Consider FC LUNs primarily when you have existing SAN investments or specific compliance requirements.
{% endhint %}

## Implementation Requirements

### Hardware

* Physical disks in VergeOS Systems vSAN [**Tier 0**](/run-the-platform/storage/storage-tiers.md#tier-0-metadata-tier)
* FC Host Bus Adapters (HBAs) in at least two cluster nodes
* Compatible FC switches (8/16/32 Gb)
* Redundant FC fabric highly recommended
* FC storage array with available LUNs

  <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p><strong>Unique LUNs Per Node</strong></p><p>Unlike traditional shared-storage clustering, VergeOS vSAN expects <strong>each node to be presented with its own unique LUN(s)</strong>. Do <strong>NOT</strong> present the same LUNs to multiple nodes. <strong>VergeOS treats Fibre Channel LUNs no different than physical disks.</strong></p></div>

### Fabric Configuration

* WWPN-based zoning configured
* Each node is assigned **dedicated** LUNs (They are treated like they are physical disks)
* Redundant physical paths per node

{% hint style="success" %}
**One LUN Per Physical Disk**

For maximum efficiency and to avoid duplicate redundancy, we recommend **mapping each FC LUN to a dedicated physical disk**.
{% endhint %}

{% hint style="success" %}
**Deduplication**

VergeOS vSAN handles data deduplication natively at the block level. When using external storage with vSAN, you should disable deduplication on your SAN if it does not support cross-LUN deduplication. If your SAN supports global deduplication, we recommend leaving it enabled to reduce overall storage consumption. VergeOS replicates data across FC LUNs according to the system's configured [vSAN redundancy level](/run-the-platform/storage/vsan-redundancy-levels.md) (N+1 stores 2 copies; N+2 stores 3 copies).
{% endhint %}

{% hint style="warning" %}
**Turn Off Storage Redundancy**

VergeOS vSAN handles data redundancy natively. You should **disable RAID and automatic tiering features** on the SAN for LUNs used by VergeOS.
{% endhint %}

## Path Management

### Multipath Configuration

By default, VergeOS manages multiple paths to each LUN in an active/passive configuration:

* **Primary Path** – Used for I/O
* **Secondary Paths** – Automatically activated on failure
* **Failover Timeout** – 7-second delay before switching
* **Path Recovery** – Alternate path remains active until manually overridden

{% hint style="info" %}
**VergeOS Path Optimization**

VergeOS automatically selects the best path for each LUN based on internal algorithms. It's normal to see multiple disks with identical serial numbers in the UI—this does **not** indicate a problem.
{% endhint %}

## Configuration Steps

1. **Prepare the FC Environment**:
   * Set up WWPN zoning on the FC switch
   * Present unique LUNs to each node - **Reminder, they are treated like they are physical disks**
   * Confirm multipath availability per node
2. **Add Storage to vSAN**:
   * Open the **Storage Tiers** section in the VergeOS UI
   * Select the tier where FC LUNs will be added
   * Apply the configuration
   * Confirm that drives appear in the desired tier

{% hint style="warning" %}
**Always Scale-Up**

We recommend adding all Fibre Channel LUNs via [**Scaling Up a vSAN**](/knowledge-base/storage-vsan/scaling-up-a-vsan.md) procedure.
{% endhint %}

{% hint style="warning" %}
**Use Maintenance Mode**

Always enter [**Maintenance Mode**](/run-the-platform/operations/maintenance-mode.md) before modifying storage configurations.
{% endhint %}

## Best Practices

### Path Management

* Use redundant physical connections per node
* Test failover functionality regularly
* Keep HBA firmware updated
* Monitor path health proactively

### Performance Optimization

* Distribute LUNs evenly across paths
* Monitor queue depth and I/O throughput
* Adjust HBA settings if needed
* Avoid oversubscribing a single LUN with multiple VMs

{% hint style="info" %}
**Core Network Bandwidth Consideration**

VergeOS vSAN uses the core network when reading/writing data. This means that during a write operation, the system sends the data to two nodes simultaneously over the core network. If your Fibre Channel SAN supports 32 Gb speeds but your core network is 25 Gb, the maximum write throughput will be constrained by the core network, not the SAN. To maximize performance, ensure the core network is greater than the FC SAN bandwidth, especially for write-intensive workloads.
{% endhint %}

## Monitoring and Maintenance

## Troubleshooting

### Path Failures

* Check physical connections
* Confirm FC switch zoning
* Review HBA logs and driver status
* Validate storage array health

### Performance Bottlenecks

* Check queue depths and path load
* Confirm proper multipath usage
* Identify oversubscription of specific LUNs

## Related Documentation

* [Storage Tiers](/run-the-platform/storage/storage-tiers.md)
* [vSAN Architecture](/run-the-platform/storage/vsan-architecture.md)
* [Maintenance Mode](/run-the-platform/operations/maintenance-mode.md)
* [System Monitoring](/run-the-platform/system-administration/subscriptions-overview.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vergeos-demo.com/run-the-platform/storage/fibre-channel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.