OLVM : Expanding Fiber Channel (FC) Support in OLVM Using a Data Domain Storage System

 

Intro

We are living in a data-driven era where AI is advancing rapidly, placing even greater demands on processing power and virtualized environments. While cloud adoption continues to grow—largely fueled by virtualization—many organizations still rely heavily on their on-premises virtual infrastructure alongside cloud technologies.

Oracle Linux Virtualization Manager (OLVM) is quickly emerging as a strong alternative, addressing key gaps left by other platforms like VMware. With Broadcom tightening its licensing policies, many organizations are now considering a move away from VMware. For those looking to transition, OLVM stands out as a reliable and cost-effective option, backed by Oracle’s 24/7 enterprise-grade support.

In this article, I’ll walk you through how to expand Fiber Channel (FC) support in OLVM using a Data Domain storage system.

Document Reference:

OLVM: Expanding the Size of a Storage Domain (FC/iSCSI) (Doc ID 2881013.1)

Steps to increase the FC data domain :

• Increase the Storage LUN at the SAN level.
• On all KVM hypervisors where the storage is mounted, execute the following command:/usr/bin/rescan-scsi-bus.sh
• Increase the size of the Data Domain from the OLVM storage side.

This is a sample output from executing /usr/bin/rescan-scsi-bus.sh.

Please ensure any issues are resolved before proceeding with the disk size increase from the OLVM side.

Sample output :

[root@kvm01 ~]# /usr/bin/rescan-scsi-bus.sh
Scanning SCSI subsystem for new devices
Scanning host 0 for  SCSI target IDs  0 1 2 3 4 5 6 7, all LUNs
 Scanning for device 0 0 0 0 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
      Vendor: Generic- Model: SD/MMC CRW       Rev: 1.00
      Type:   Direct-Access                    ANSI SCSI revision: 06
.Scanning host 1 for  all SCSI target IDs, all LUNs
 Scanning for device 1 0 0 0 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 00
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 0 1 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 01
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 0 2 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 02
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 0 3 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 03
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 0 5 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 05
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 0 9 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 09
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 0 10 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 10
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 0 11 ...
OLD: Host: scsi1 Channel: 00 Id: 00 Lun: 11
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 1 0 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 00
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 1 1 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 01
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 1 2 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 02
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 1 3 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 03
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 1 5 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 05
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 1 9 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 09
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 1 10 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 10
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 1 0 1 11 ...
OLD: Host: scsi1 Channel: 00 Id: 01 Lun: 11
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
Scanning host 2 for  SCSI target IDs  0 1 2 3 4 5 6 7, all LUNs
 Scanning for device 2 0 0 0 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00
      Vendor: HPE      Model: Smart Adapter    Rev: 3.53
      Type:   Enclosure                        ANSI SCSI revision: 05
 Scanning for device 2 1 0 0 ... 0 ...
OLD: Host: scsi2 Channel: 01 Id: 00 Lun: 00
      Vendor: HPE      Model: LOGICAL VOLUME   Rev: 3.53
      Type:   Direct-Access                    ANSI SCSI revision: 05
 Scanning for device 2 2 0 0 ... 0 ...
OLD: Host: scsi2 Channel: 02 Id: 00 Lun: 00
      Vendor: HPE      Model: P408i-a SR Gen10 Rev: 3.53
      Type:   RAID                             ANSI SCSI revision: 05
Scanning host 3 for  all SCSI target IDs, all LUNs
 Scanning for device 3 0 0 0 ...
OLD: Host: scsi3 Channel: 00 Id: 00 Lun: 00
      Vendor: DGC      Model: VRAID            Rev: 0532
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 3 0 0 1 ...
OLD: Host: scsi3 Channel: 00 Id: 00 Lun: 01
      Vendor: DGC      Model: VRAID            Rev: 0532
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 3 0 0 2 ...
OLD: Host: scsi3 Channel: 00 Id: 00 Lun: 02
      Vendor: DGC      Model: VRAID            Rev: 0532
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 3 0 1 0 ...
OLD: Host: scsi3 Channel: 00 Id: 01 Lun: 00
      Vendor: DGC      Model: VRAID            Rev: 0532
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 3 0 1 1 ...
OLD: Host: scsi3 Channel: 00 Id: 01 Lun: 01
      Vendor: DGC      Model: VRAID            Rev: 0532
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 3 0 1 2 ...
OLD: Host: scsi3 Channel: 00 Id: 01 Lun: 02
      Vendor: DGC      Model: VRAID            Rev: 0532
      Type:   Direct-Access                    ANSI SCSI revision: 04
Scanning host 4 for  all SCSI target IDs, all LUNs
 Scanning for device 4 0 0 0 ...
OLD: Host: scsi4 Channel: 00 Id: 00 Lun: 00
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 0 1 ...
OLD: Host: scsi4 Channel: 00 Id: 00 Lun: 01
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 0 2 ...
OLD: Host: scsi4 Channel: 00 Id: 00 Lun: 02
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 0 3 ...
OLD: Host: scsi4 Channel: 00 Id: 00 Lun: 03
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 0 5 ...
OLD: Host: scsi4 Channel: 00 Id: 00 Lun: 05
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 0 9 ...
OLD: Host: scsi4 Channel: 00 Id: 00 Lun: 09
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 0 10 ...
OLD: Host: scsi4 Channel: 00 Id: 00 Lun: 10
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 0 11 ...
OLD: Host: scsi4 Channel: 00 Id: 00 Lun: 11
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 1 0 ...
OLD: Host: scsi4 Channel: 00 Id: 01 Lun: 00
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 1 1 ...
OLD: Host: scsi4 Channel: 00 Id: 01 Lun: 01
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 1 2 ...
OLD: Host: scsi4 Channel: 00 Id: 01 Lun: 02
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 1 3 ...
OLD: Host: scsi4 Channel: 00 Id: 01 Lun: 03
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 1 5 ...
OLD: Host: scsi4 Channel: 00 Id: 01 Lun: 05
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 1 9 ...
OLD: Host: scsi4 Channel: 00 Id: 01 Lun: 09
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 1 10 ...
OLD: Host: scsi4 Channel: 00 Id: 01 Lun: 10
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
 Scanning for device 4 0 1 11 ...
OLD: Host: scsi4 Channel: 00 Id: 01 Lun: 11
      Vendor: DGC      Model: VRAID            Rev: 0430
      Type:   Direct-Access                    ANSI SCSI revision: 04
Scanning host 5 for  all SCSI target IDs, all LUNs
0 new or changed device(s) found.
0 remapped or resized device(s) found.
0 device(s) removed.

Once the rescan is completed on all KVM hosts, the next step is to increase the Data Domain from the storage side.

Keep in mind that even if you extend the LUN at the SAN level, the change will not automatically reflect in the Data Domain.

From OLVM : Navigate to Storage >  Storage Domain > (Select respective data domain) > Select Manage domain as higlighted below.

                                                       

                                                    Figure 1 : Select Manage Domain

The Manage Windows interface will display the updated size, allowing you to increase it as needed.

                                               Figure 2 : Manage window

Now, select the desired size and click OK to apply the increase.

                                               Figure 3: Increase in size.

Now Data Domain will reflect the new size.

Figure: Data domain after an increase in size. 

Conclusion 

In today's evolving IT landscape, organizations are under increasing pressure to modernize infrastructure while maintaining flexibility, control, and cost-efficiency. As AI and data workloads grow, the need for robust, scalable virtualization solutions becomes even more critical.

With Broadcom’s licensing changes pushing many to reconsider their reliance on VMware, OLVM offers a compelling path forward. It not only fills the functionality gaps but also provides enterprise-grade reliability, backed by Oracle’s 24/7 support.

Whether you're planning a full migration or building out a hybrid environment, OLVM is well-positioned to meet the demands of modern workloads. In this article, we explored how to extend Fiber Channel (FC) capabilities in OLVM using Data Domain, helping organizations take a step forward in building a resilient and future-ready virtual infrastructure.