This section explains how to create definition files.
When using a physical L-Server, the configuration of the definition file may be necessary.
When using SAN storage
For all storage
Refer to "B.1.1 Creating Definition Files Combining Ports of SAN Storage".
When using ETERNUS storage
Refer to "B.1.2 Format Selection for the Names of Virtual Storage Resources and Disk Resources Managed by ESC".
When configuring Thin Provisioning attributes on a storage pool
Refer to "20.2 Creating" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Refer to "G.1.1 Overcommit Definition Files", when migration is not executed using the configuration methods for overcommit functions after performing upgrade of the admin server from ROR V2.3.0 or V3.0.0.
When using configuration of priority for resource selection on Thin Provisioning and Automatic Storage Layering
Refer to "B.1.3 Configuration of Priority for Resource Selection on Thin Provisioning and Automatic Storage Layering".
When using dynamic LUN mirroring
Refer to "B.1.4 Creating Mirroring Definition Files for Dynamic LUN Mirroring".
When using EMC storage
For details, refer to "B.1.5 Definition File for EMC Storage".
When using Storage Server that operates FalconStor NSS
For details, refer to "B.1.11 Definition File for FalconStor NSS".
When the number of FCs fitted and their position differ depending on the physical server
Refer to "B.1.7 Setting the Number of FCs Fitted and their Position for Each Physical Server".
When creating a physical L-Server without specifying a model name in the L-Server template
When using alive monitoring
Refer to "B.1.8 Definition File for Alive Monitoring".
