Generic FC Pools (Existing LUNs)

Use this page when you want to attach LUNs that already exist on your own Fibre Channel array to Karios VMs. Each LUN becomes a data disk of one VM. Your data stays on your array, and the array keeps its own masking.

If you want Karios to create the disks on a SAN array instead, use FC Pools on a Managed Array (COMSTAR). For shared concepts (ports, paths, readiness, health), see Fibre Channel Storage. The iSCSI counterpart is Generic iSCSI Pools (Existing LUNs).

UI path: Control Center -> Storage -> Instance Storage

When to Use

  • You have data on LUNs of an existing FC array and want a VM to use it as a disk.

  • You manage the array yourself, with any vendor’s software or appliance. Karios needs no login to it.

  • You want Karios to attach and detach LUNs, not to create or change them.

What Karios Does and Does Not Do

Karios does:

  • Read, on every host in the zone, which LUNs the array presents over the ports you pick, and list them with their identity, size, paths, and state.

  • Attach a LUN to one VM as a data disk, and detach it again.

  • Watch each LUN and tell you if it goes missing, is seen by another pool, or changes size. A LUN that grows on the array is delivered to the VM that holds it.

Karios never:

  • Creates, resizes, wipes, or deletes a LUN.

  • Changes the array’s masking or the switch’s zoning.

  • Reads, checks, or formats what is on a LUN. Whatever is on it becomes the VM’s disk.

  • Boots a VM from an existing LUN. A LUN is attached as a data disk only.

Before You Start

  • [ ] You are a platform administrator. Every generic FC task, including viewing the LUNs, is limited to the platform administrator.

  • [ ] The platform setting mount.disabled.storage.pool is true, as for generic iSCSI (see Task 1 in Generic iSCSI Pools).

  • [ ] Every host in the zone that should hold the LUNs has an FC HBA and is zoned to the array’s ports. A host without an HBA is listed as No FC HBA and never holds the pool.

  • [ ] The LUNs are masked on the array to each host’s initiator WWPN, on every port the pool watches. LUNs must use a 512-byte logical block size and an NAA identity.

  • [ ] The LUNs are not write-protected on the array.

  • [ ] No other pool lists the same LUNs. A LUN that another pool already holds as a volume is refused at create (see Task 2).

Note

No array is registered for this pool type. Karios keeps an internal record of the pool and its ports; the Array row on the pool card is blank.

Task 1: Mask the LUNs on the Array

When to Use: Do this on your array before you create the pool, and whenever you add a LUN.

Purpose: Let each host see the LUNs on the ports the pool will watch.

Steps:

  1. On the switch, zone each host’s initiator WWPN to the array’s target ports. The create form’s Hosts card shows every host’s WWPN and offers Show zoning commands.

  2. On the array, present the LUNs to each host’s WWPN on every port you will tick in the pool.

  3. On a host that already holds a SAN pool, nothing else is needed: the next scan finds the LUN. On a fresh host, the first scan runs when the pool is created.

Expected Outcome:

  • The Hosts card reads Ready for every host with its port count.

Task 2: Create the Pool

When to Use: Do this after Task 1, once per array (or per group of ports) you want to use.

Purpose: Make the zone’s hosts read the LUNs behind the picked ports.

Steps:

  1. Click Add Instance Storage. Set Protocol to fc and Driver to generic (maps existing LUNs). Scope is fixed to Zone.

  2. Enter a Name for the pool.

  3. Under Ports to watch for health, tick the array ports this pool reads through. The list shows the target ports your hosts report seeing, each with how many hosts see it. If no host has reported yet, type the WWPNs separated by commas, or leave the list blank to take every port the hosts see.

  4. Pick Minimum paths. Karios proposes a value from what the hosts see, capped at the ticked ports. With one port, or before any host has reported, it is 1; tick the single path acknowledgement when the form shows it.

  5. Storage tags shows the locked Reserved for existing LUNs chip. Karios adds it to keep ordinary disks off this pool.

  6. Click Add Instance Storage.

Expected Outcome:

  • The pool appears in the list with protocol FC and the badge Existing LUNs.

  • The pool’s LUNs tab lists the LUNs the hosts see behind the ticked ports.

If this fails:

A refused create leaves nothing behind. Fix the cause and create again.

  1. No host in scope reaches the array: zone at least one host to a ticked port.

  2. KF-4013: a host is logged in on fewer of the ticked ports than Minimum paths. Zone the host to the missing port, untick it, or lower Minimum paths.

  3. this pool lists LUNs another pool already holds as a volume: the message names each LUN and the pool that holds it. Creating this pool would put every one of them in conflict in both pools. Limit this pool to ports that do not carry them, or delete the pool that holds them first.

  4. A typed port is refused: WWPNs are 16 hex digits, with or without colons.

  5. KF-5022: no host answered the check. Retry.

Note

A pool whose ports carry no LUN for the hosts still creates, with zero LUNs. Mask the LUNs on the array; the next scan lists them.

Task 3: Review the LUNs Tab

When to Use: Use this after the create, and any time you change masking on the array.

Purpose: See what the hosts see on your array.

Steps:

  1. Open the pool, or in its row open Actions and choose View LUNs.

  2. Open the LUNs tab. The header shows the ports watched, Hosts n of m (hosts that reported, of hosts in the zone), and Last scan.

  3. Each host re-reads its HBAs on its own every 15 minutes, so a LUN you mask on the array appears within that time. The tab shows the latest pass; Refresh reloads the page data.

  4. Filter by state, or search by identity, vendor, or VM.

  5. Open a row to see its identity, vendor and model, volume, holding host, state reason, and the paths at the last scan, one per host and array port.

Expected Outcome:

  • Every masked LUN is listed. LUNs ready to use read Detached.

LUN States

State

Meaning

Detached

Every host sees the LUN on at least Minimum paths of the pool’s ports, and no VM has it. You can attach it.

Attached

The LUN is a data disk of the VM shown in Attached to.

Not ready

A host does not see the LUN, sees it on fewer than Minimum paths ports, or has no good scan yet. Or the array write-protects the LUN, its block size is not 512 bytes, or its identity is not an NAA identity. The State reason says which.

Missing

The LUN is attached, but no host has reported it for two scans in a row. A LUN that is not attached and disappears is simply dropped from the list.

Conflict

Another pool lists the same LUN, a host sees it at two LUN numbers, or a different LUN now sits where this one was. Fix the cause on the array or the other pool, then wait for the next scan.

Task 4: Attach a LUN to a VM

When to Use: Use this to give a VM one of the listed LUNs as a data disk.

Purpose: Attach the LUN without changing anything on the array.

Steps:

  • From the LUNs tab: click Attach on a Detached row, pick the VM, optionally name the volume, and confirm.

  • From the VM: open the VM, go to Volumes, click Add Disk, set Source to Existing LUN, pick the LUN, and click Attach.

  • When creating a VM: in Create VM, pick one or more LUNs in Existing LUNs. Karios attaches each LUN after the VM is created, and starts the VM once every LUN is attached. The root disk still comes from a template or boot image on another pool.

Rules:

  • The VM must be in the pool’s zone, on a host with an FC HBA.

  • If the VM is running, its host must see the LUN on at least Minimum paths of the pool’s ports right now. Karios checks the host’s live paths, not the last scan.

  • A LUN is attached to one VM at a time.

  • Each attached LUN becomes a volume of the reserved Karios LUN volume profile.

Warning

Karios does not read, check, or wipe the LUN. Whatever is on it becomes the VM’s disk. Make sure you attach the right LUN.

Expected Outcome:

  • The row reads Attaching..., then Attached with the VM name.

  • The VM’s disk list shows the disk with a LUN badge. A running VM sees the disk at once; a stopped VM gets it at its next start.

If this fails:

  1. KF-4018: the VM’s host cannot see the LUN, or the LUN is in conflict. The message names the host and its WWPN. Mask the LUN to that host on every watched port, or clear the conflict, then wait for the next scan.

  2. KF-4019: the LUN is not Detached, or the VM is in another zone. Wait for the LUN to read Detached, or pick a VM in the pool’s zone.

  3. KF-4013: the host sees the LUN on fewer paths than Minimum paths. Check the zoning and the port state, or lower Minimum paths.

  4. A failed attach puts the LUN back to Detached by itself in a few minutes.

Task 5: Detach a LUN

When to Use: Use this to take a LUN away from a VM. The LUN keeps its data.

Steps:

  1. Stop the VM that holds the LUN. Karios never unplugs a LUN from a running VM.

  2. On the LUNs tab, click Detach on the row. Or use Detach LUN on the disk in Block Storage or on the VM’s Volumes tab.

  3. Type the volume name to confirm, and click Detach.

Expected Outcome:

  • The row reads Detaching... until the host confirms, then Detached. The host drops the LUN’s paths; the array’s masking is untouched.

If this fails:

  1. KF-4019 with stop VM <name> first: stop the VM, then detach again.

  2. If the LUN was deleted on the array while attached, the row reads Missing. One Detach still finishes: Karios releases the stale paths on the host and removes the volume.

Task 6: Grow a LUN

When to Use: Use this when a VM needs more space on an attached LUN.

Steps:

  1. Grow the LUN on your array. The VM can stay running.

  2. Wait for the next scan (up to 15 minutes). Karios records the new size, the host re-reads the paths, and the running VM sees the larger disk.

Expected Outcome:

  • The LUNs tab and the guest both show the new size.

Note

Karios refuses to resize a LUN disk itself (KF-4017). Always grow it on the array. A LUN that shrinks is flagged; Karios never shrinks a disk under a VM.

Task 7: Delete the Pool

When to Use: Use this to stop using the array’s LUNs through Karios. The LUNs and their data stay on the array.

Steps:

  1. Detach every LUN (Task 5).

  2. In the pool row, open Actions and choose Delete. Type the pool name and confirm. Karios enables the pool, puts it in maintenance, and removes it from the platform for you.

Expected Outcome:

  • The pool is gone from the list. The hosts drop the LUN paths they held for it. Nothing on the array changes.

If this fails:

  1. The pool still has attached LUNs: detach them first.

Limits

  • Data disks only. A VM cannot boot from an existing LUN.

  • Zone scope only.

  • No volume snapshots and no Storage QoS (KF-4016).

  • Karios never creates, resizes, or deletes a LUN (KF-4017).

  • One LUN belongs to one pool. Two pools whose ports carry the same LUN put it in Conflict in both.

  • A LUN that is only on an unticked port is not listed. Tick the port, or mask the LUN on a ticked one.

Troubleshooting

Code or message

What it means

What to do

Unknown on a host

The host has not reported yet, or not for three minutes. A host reports once at start and every minute while it holds a pool.

Wait a minute, or restart the Karios host service on it.

Not zoned

The host’s HBA sees none of the array’s ports.

Zone the host’s WWPN to the ports on the switch, then Re-check.

No FC HBA

The host has no FC adapter. It never holds the pool.

Place VMs that need the LUNs on hosts with an HBA.

KF-4013

A host sees fewer of the pool’s ports than Minimum paths.

Zone the host to the missing port, bring the port back, or lower the floor.

KF-4017

Create, resize, clone, or template asked on this pool.

Attach LUNs from the LUNs tab. To grow a LUN, follow Task 6.

KF-4018

The host cannot see the LUN, or the LUN is in conflict with another pool.

Mask it to the host on every watched port, or remove it from the other pool, then wait for the next scan.

KF-4019

The LUN is not in the state the action needs.

Stop the VM before detach, wait for attach to finish, or clear a conflict.

another pool already holds as a volume

The create would list a LUN that is attached through another pool.

Untick the ports that carry it, or delete the other pool first.

Unable to create a deployment on VM start

The platform could not place the VM. With a LUN in Conflict or a host short of paths, Karios refused the attach on that host.

Read the LUN’s State reason and the host’s row; the management log carries the KF- cause. Clear the conflict and start the VM again.

Placement: Disabled by the fabric

No host could reach the pool for about five minutes.

Fix the fabric or the array. Placement comes back by itself.

Done Criteria

  • [ ] mount.disabled.storage.pool is true.

  • [ ] The pool shows Hosts n of n on the LUNs tab and every host reads Ready.

  • [ ] The LUNs you need read Detached or Attached.

  • [ ] A test VM sees its attached LUN, sees a grow done on the array, and keeps its data after detach and attach.