If the number of FCs fitted or their location differs from physical server to physical server, prepare an "FC connection pattern" and define the number of FCs and their location for each physical server.
This setting can be made when the storage units are the following:
EMC CLARiiON Storage or EMC VNX storage
EMC Symmetrix DMX Storage
EMC Symmetrix VMAX Storage
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data\fc_connection_pattern
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data/fc_connection_pattern
Make the file extension .rcxprop and then allocate a file with an arbitrary file name. Specify the file name using the following string:
The file name must start with an alphanumeric character, and can contain up to 64 alphanumeric characters, underscores ("_"), and hyphens ("-").
Create a different "FC pattern" file for each system that has a different pattern.
NUM_OF_FC=Number_of_FCs_used |
Specify the number of FCs to be used. 1, 2, and 4 can be specified for the number.
Specify the number of HBAs that are actually mounted on the server.
Allocate a sequential number to all of the ports, sorted in the expansion slot order.
By specifying the HBA numbers, up to two FC ports can be set as Boot paths.
The priority of HBA numbers is set based on the order in which they are listed.
Only numbers under the value specified in NUM_OF_FC can be specified.
NUM_OF_FC value | Valid Range of HBA Numbers |
|---|---|
4 | 0 - 3 |
2 | 0 - 1 |
1 | 0 |
Specify as many as there are connected storage chassis. However, the number in X must be a decimal between 0 and 99, starting from 0 and counting up.
Specify the storage chassis identification number.
Define the FCPort pairing on the server side, separating with a colon (:).
Define the FCPort pairing on the storage side, separating with a colon (:).
By specifying separate HBA numbers for each STORAGE_X, logical paths to two storage chassis can be set from each single physical server.
However, if the same storage chassis identification number is defined multiple times, only the one defined first will be valid.
Note
The file names of FC connection patterns cannot be changed after performing the following operations:
Import of the L-Server template specifying an FC connection pattern
Turning on of the physical L-Server with a definition specifying an FC connection pattern
Creation of a physical L-Server specifying an FC connection pattern
The details of FC connection pattern files can only be changed in the following cases:
When a physical L-Server with an FC connection pattern specified is in the defined state
Example
An example definition file is indicated below.
If 2 paths (1 boot path)
NUM_OF_FC = "2" |
If 2 paths (2 boot path)
NUM_OF_FC = "2" |
If 4 paths (1 chassis)
NUM_OF_FC = "4" |
If 4 paths (2 chassis)
NUM_OF_FC = "4" |
