6.3.3 Access path setting

In a storage system where a Fibre Channel switch is between a server node and storage, this software automatically changes the security settings supported by each device and sets an access path, as shown in the figure below. If no security mechanism is provided on the device side, setting up security may not be possible. However, the security mechanisms of other devices create access paths. If none of the devices constituting these access paths is equipped with a security function, security cannot be set up but the access paths can be accessed from the server node. This software can set an access path only in the Fibre Channel switch environment.

Even if the access path state is "Config miss Match," you can create a correct access path by setting the access path properly. Select the access path whose state is "Config miss Match" in the Access Path window, and set the access path.

This function can set an access path not only between a server node (HBA) and storage (CA) but also between a server node (HBA) and a bridge port, between two server nodes (HBAs), and between storage systems (CAs).

Note

Each storage system has requirements, such as HBA types used, for guaranteeing operation according to the mutual connection verification status. Set each access path so that these requirements are satisfied. For more information about the requirements, contact the respective storage system distributor.

Table 6.7 Security information that this software sets in a device when setting an access path
Device type			Contents set by this software
Solaris OS server node	Agent available	PW008FC2A, PW008FC2-G, PW008FC3, GP7B8FC1A, GP7B8FC1-G, GP7B8FC1, SE0X7F11F, SE0X7F12F	Partner device is a disk (excluding a manually embedded disk) unit: Setting of sd.conf LUN / setting for associating fjpfca.conf TID with WWPN Partner device is a tape, library, bridge, or manually embedded disk: Setting for associating fjpfca.conf TID with WWPN Partner device is an HBA: No setting
		SN10-FC01, FC64-1063	Partner device is a disk (excluding a manually embedded disk): Setting for associating sd.conf TID and LUN with WWPN Partner device is a tape, library, or HBA: No setting
		LP-7000, 8000, 9000, 9002S, 9002L, 9802, 10000	Partner device is a disk (excluding a manually embedded disk): Setting for associating sd.conf/lpfc.conf or lpfs.conf TID and LUN with WWPN Partner device is a tape, library, bridge, or manually embedded disk: Setting for associating lpfc.conf or lpfs.conf TID and LUN with WWPN Partner device is an HBA: No setting
		QLA-2200	Partner device is a disk (excluding a manually embedded disk): Setting for associating sd.conf/qla2200.conf TID and LUN with WWPN Partner device is a tape, library, bridge, or manually embedded disk: Setting for associating qla2200.conf TID and LUN with WWPN Partner device is an HBA: No setting
		HBA (other than above cases)	No setting
	Agent unavailable		No setting
Windows server node	Agent available/unavailable		No setting
Linux server node	Agent available/unavailable		No setting
HP-UX server node	Agent available/unavailable		No setting
Other server nodes	Agent unavailable		No setting
Fibre Channel switch		With zoning setting	WWPN one-to-one zoning is set. (However, this zoning is not set if the Fibre Channel switch side already has sufficient port zoning.)
Fibre Channel switch		Without zoning setting	No setting (However, if "Operation for setting WWPN zoning" has been selected for the Fibre Channel switch, a dialog box is displayed allowing the user to select whether to execute the zone setting.)
ETERNUS8000, ETERNUS6000, ETERNUS4000, ETERNUS3000, ETERNUS2000, ETERNUS DX60/DX80, GR		With security setting	Setting of HBA WWPN for security
		Host affinity (zone) setting	Setting of HBA WWPN to the affinity group (zone)
		Without security setting	No setting
Other storage/tapes/bridges			No setting

6.3.3.1 Preparations

Notes

Only the administration account whose authority level is "privileged administrator" can set access paths.
To change the HOST ID (Target ID) of a set access path, delete the path and then set it again with a new ID.
To change the specified AffinityGroup/zone name on the ETERNUS/GR side of a set access path, delete the path and then set it again with a new zone.
From the [View] menu, select [Refresh], and verify that all Fibre Channel switches cascaded to the Fibre Channel switch associated with the access path setting are correctly recognized in the current status. Once an access path is changed because a Fibre Channel switch is temporarily disconnected from the cascade connection, the old cascade connection cannot easily be recovered. (In this event, execute the cfgClear command to delete zoning information for the Fibre Channel temporarily disconnected from the cascade connection. This enables cascade reconnection.)
When an access path is set for an ETERNUS storage device, "Host response" must be set for the storage device according to the environment. For details, refer to the related ETERNUS disk array manual.
When setting an access path that is configured in the FC routing functionality LSAN zone in this software, manually set the LSAN zone in the device in advance.

Checking storage settings

Check the following settings on the storage side before setting an access path:

ETERNUS8000 series, ETERNUS6000 series, ETERNUS4000 series, ETERNUS3000 series, ETERNUS2000 series, ETERNUS DX60/DX80 and GR series
By setting up the zone (host affinity) function, you can use storage areas efficiently on a storage area network. To use this zone function, you must set up a zone on the storage side before setting an access path. Set up a Affinity Group/zone with ETERNUSmgr/GRmgr, or consult with your Fujitsu customer engineer.
ETERNUS DX60, ETERNUS DX80
If linked affinity groups are used, then the WWN settings of the server nodes to be used must be set in advance.
Use ETERNUSmgr to set the WWN settings. When updating settings, set the [Host Specific Mode] to [HP-UX Mode].

Connected state of the FC cable between devices

When setting an access path, an HBA and CA must be physically connected via a Fibre Channel switch.
When HBA and CA are connected via FC hub or in FC-AL one-to-one correspondence, the setting of the access paths is not supported. Set to the server node and storage manually.

Device status

Each HBA must be connected to a Fibre Channel switch and operate as the N port or NL public.
All of a Fibre Channel switch on the way of the access path setting, HBAs, server nodes, CAs and storages should be operating normally.

Using ETERNUS multipath driver 2.0.1 or later

The access path setting function of this software does not write access path setting information to /kernel/drv/sd.conf in an environment in which the ETERNUS multipath driver is installed. However, the setting information is written to /kernel/drv/fjpfca.conf or /kernel/drv/lpfc.conf.

Therefore, to use the access path setting function of this software to build a multipath, follow the procedure below.

Install the ETERNUS multipath driver (mpdpkgadd command).
After installation is completed, you are asked whether you want to configure the environment for the multipath driver. Enter "n" to exit.
```
Do you want to make a multipath configuration now? [y,n,?,q] n
```
Make access path settings by using this software.
Make access path settings to build a multipath configuration.
The access path setting information with these settings is written to fjpfca.conf or lpfc.conf.
Configure the environment for the multipath driver (grmpdautoconf command).
For details on interactive processing, see the ETERNUS multipath driver manual.
However, if you are asked whether you want to make ETERNUS and switch settings, enter "n" (No & skip).
```
Do you want to set Host affinity & set a switch zoning?

   Yes ---> hit the 'y' key.
   No & skip ---> hit the 'n' key.
   Quit ---> hit the 'q' key.

Please input [y,n,q]n
```

Note

Do not use this software to set any access path in a multipath configuration before installing the ETERNUS multipath driver (steps 1 and 2 cannot be reversed). If an access path is thus configured before the ETERNUS multipath driver is installed, the multipath driver has conflicting environmental conditions since setting information is written to sd.conf (an undefined target ID is used in sd.conf).

Using the hard disk driver (HDDV) and multipath disk control (GR Multipath Driver, MPLB, MPHD)

When the hot system expansion function of a server node is disabled, the access path setting function writes access path information in /kernel/drv/sd.conf on the server node side. For this reason, when using the HDDV and GR Multipath Driver, MPLB, MPHD, set access paths according to the sd.conf rewrite timing specified for environment setup in the respective manuals.
To add a logical unit access path to the host being used with the HDDV or Multipath disk control (ETERNUS Multipath Driver, GR Multipath Driver, MPLB, MPHD), or to set an additional logical unit in the server node, configure with [Set Access Path] the required setting for ETERNUS Multipath Driver, GR Multipath Driver, MPLB, MPHD, HDDV.
If the HDDV version is 2.2 or higher and hot system expansion is enabled by in hddvadm -M, hot system expansion can be implemented for the logical unit in the Solaris 9 OS or in a special environment. Before hot system expansion, specify the hddv.conf editing method and hddvadm -M use method and set up the special environment manually according to the related HDDV manual. (When using hddvadm -M, this software does not edit files named hddv.conf and sd.conf. Edit these files manually to add definitions separately. It edits the file named fjpfca.conf automatically.)

Note

Do not supposed to execute the grmpdautoconf command of GR Multipath Driver (GR Multipath Driver is 1.0.4 or higher) in the environment that hot system expansion of hddvadm -M is unavailable in Solaris OS server node (Agent is available). The HDDV multipath environment can be automatically constructed as the number of sd.conf TID for Agent setting and the number of hddv.conf TID for GR Multipath Driver setting are doubly defined. If the access path setting is executed in the above environment of this software, execute HDDV driver multipath disk control construction by using the constructing procedure from sd driver (standard settings). If hot system expansion of hddvadm -M is available in an environment, the grmpdautoconf command can be executed because the definition setting for sd. conf is not performed in the access path setting of this software.

6.3.3.2 Setting

Set access paths for the Fibre Channel. You can set a new access path and clarify access path settings (correction in the event of an access path setting conflict), and also change settings of logical unit expansion in the access path.

Access path setting procedure

Configure the access path environment by installing additional storage and connecting a Fibre Channel cable, etc.
Preprocessing for the device driver definition file
- When ETERNUS Multipath Driver 2.0.1 or higher is used
  No preprocessing needs to be performed.
- Solaris 8 OS and Solaris 9 OS
  - This procedure changes the disk array control driver from sd to hddv when the grmpdautocon command is executed in the GR Multipath Driver environment (v1.0.4 or later) or when the hot system expansion function (hddvadmM) is enabled for setting a hard disk driver (hereinafter abbreviated as hddv).
    Check whether the hddv configuration information file (hddv.conf) has been created.
    # ls /kernel/drv/hddv.conf
    If the file is not found, execute the following command and create the hddv.conf file:
    # hddvadm -M
    When the file is found, check whether the file content is of class or parent type.
    (Example)
    Example of hddv.conf of the parent type
    name="hddv" parent="scsi" target=16 lun=0;
    Example of hddv.conf of the class type
    name="hddv" class="scsi" target=16 lun=0;
    The class type of file requires no preprocessing. (All hddv.conf files created by the hot system expansion command [hddvadm M] are of the class type.)
    For the parent type of file, follow the instructions below to initialize the non-hot system expansion environment and move into the hot system expansion environment. To directly use the non-hot system expansion environment, follow the procedure for setting non-hot system expansion (hddvamd m).
    1. Execute hddvadm -i.
    2. Confirm that /kernel/drv/hddv.conf is not present.
    3. Delete the entries made for recognizing the disk array device from the sd configuration information file (sd.conf).
    4. Execute the following command and create an hddv configuration information file (hddv.conf):
    # hddvadm -M
    Note
    Before setting the access path, do not execute the grmpdautoconf command without executing the hddvadm M command that enables the hot system expansion environment. Otherwise, the TargetID of sd.conf and TargetID of hddv.conf of the GR Multipath Driver setting may be defined twice. Consequently, a HDDV multi-path environment may be automatically created due to the duplicated TargetID definition.
    In a non-hot system expansion environment, sd.conf is described by "access-path setting". Therefore, the TargetID of sd.conf may match that of hddv.conf, which is edited later. This duplicated TargetID definition must be avoided. In a hot system expansion environment (hddvadm M), sd.conf is not described by "access-path setting". Therefore, the TargetID definition will not be duplicated.
  - In the MPLB2.0 or MPLB2.1 environment with non-hot system expansion specified (hddvadm -m), the commands for adding and removing paths are not supported. Accordingly, the multipath configuration must be canceled once. Execute the destroy command of #iompadm to cancel the multipath configuration.
  - In the multipath disk control (GR multipath driver, MPLB, MPHD, or HDDV) environment with non-hot system expansion is specified (hddvadm -m), execute the following command on the target server node:
    # hddvadm -i
    By executing this hddvadm -i command, hddv.conf file moves to sd.conf and mphd.conf/mplb.conf file is saved. However, in the hot system expansion environment or in the hddvadm -M execution environment, hot system expansion can be performed without executing the hddvadm -i command. Therefore, this command need not be set.
This software automatically edits sd.conf (in the hot system expansion environment) and the configuration definition files (*.conf) of the target HBA when an access path is being set. Stop all programs affected by the editing of these files.
Steps 3 to 7 given below are a procedure for setting a new access path. If target storage is already displayed, start from step 6. To change the settings of an existing access path, select that path, and start from step 8.
Select the target server node, and open the "Server Node view".
From the [Operation] menu, select [View Device] - [Add] to display the Add View Device dialog. Select the access path target storage from "Available Devices" in this dialog, and move it to "Devices to Show" by clicking the <>> Add> button. After completing view device addition, click the <OK> button.
The selected storage is displayed in the window.
Click to select the HBA of the server node side on which an access path is to be created.
While holding down the Ctrl key, click to select the CA of the storage side on which an access path is to be created.
Select [Access Path] - [Connect] from the menu displayed by right-clicking.
You can also perform steps 6 to 8 simply by dragging & dropping the relevant port icons (e.g., by dragging the HBA port and dropping it on the CA port).
Note
After performing the above steps, move the mouse. (The drag & drop operations may not be accepted by the system).
[For the storage that is ETERNUS8000, ETERNUS6000, ETERNUS4000, ETERNUS3000, ETERNUS2000, ETERNUS DX60/DX80 or GR series] If Affinity Group (zone) is set on the storage side, select the Affinity Group (zone) used by the access path. For this task, you can use a function that can automatically fetch and select the Affinity Group (zone) set on the storage side.
Note
In ETERNUS6000 devices, the concatenated AffinityGroups can be selected only by dragging the access path to 4Gbps(transfer rate) FC-CA ports. The concatenated AffinityGroups should not be dragged and dropped to FC-CA ports others than 4Gbps(transfer rate) FC-CA ports.
[Solaris OS server node (Agent available)] Enter the Target ID (X of Solaris OS special file /dev/rdsk/c?tXd?s?) corresponding to the access path. (The "Target ID Configuration" dialog appears only in an HBA-device environment in which Target IDs can be specified. If the HBA is XSEFC401AF, XSEFC402AF, SG-XPCI1FC-QF2, SG-XPCI2FC-QF2, SG-XPCI1FC-QL2 or SG-XPCI2FC-QF2-Z, the "Target ID Configuration" dialog is not appeared.)
If a Fujitsu-made multipath disk control is used, specify 16 or a greater number for Target ID.
[Solaris OS server node (Agent available)] Enter the LUN used by the access path. (The "LUN Configuration" dialog appears only in an HBA-device environment in which LUNs can be specified.)
At this time, information for LUNs already accessible from the server node is registered at the currently set LUN information place. If a new access path is set, no value is registered at this place. The LUN set in the zone on the selected storage side is registered as the initial value of "Specify a LUN".
If a LUN is added in this step, the corresponding LUN is added to the /kernel/drv/sd.conf file on the server node. If a LUN is deleted, another path may be using the LUN. For this reason, this software does not automatically delete the LUN from the /kernel/drv/sd.conf file. To delete the definition, edit the /kernel/drv/sd.conf file on the server node side.
In a hot system expansion environment of ETERNUS Multipath Driver 2.0.1 or later, or the multipath disk control (GR Multipath Driver, MPLB, MPHD, HDDV 2.2 or higher), contents of the sd.conf file are not modified. Specify TIDs and LUNs in the hddv.conf file for the multipath disk control. For details, refer to the handbook for HDDV 2.2 or higher.
If the HBA is XSEFC401AF, XSEFC402AF, SG-XPCI1FC-QF2, SG-XPCI2FC-QF2, SG-XPCI1FC-QL2 or SG-XPCI2FC-QF2-Z, click the <OK> button without changing the initial value.
[For the Fibre Channel switch that is in no-zone status] If "Configure WWPN_Zoning on the switch when access paths are created." is selected when the Fibre Channel switch is registered with this software, a dialog opens to ask about whether to set zoning in the Fibre Channel switch. The security function of the Fibre Channel switch is used if zoning is set in a place without zoning. Note that operation of other active access paths is disabled by this security function. In such a configuration, it is recommended to stop operation of other access paths, and set the access paths again from this software. If "Do not configure WWPN_Zoning on the switch when access paths are created." is selected when the Fibre Channel switch is registered with it, the above dialog does not appear. To change "Do not configure WWPN_Zoning on the switch when access paths are created." to "Configure WWPN_Zoning on the switch when access paths are created.", change the setting according to the property zoning information about the Fibre Channel switch.
Check access path information when it is displayed. If the displayed information need not be modified, click <OK> button. This software sets an access path for the device.
Note
If a storage area used in this access path setting is defined in another HBA, an area collision warning message is output. (Only the ETERNUS8000, ETERNUS6000, ETERNUS4000, ETERNUS3000, ETERNUS2000 series, ETERNUS DX60/DX80 and the GR series provide this check mechanism on the storage side.) The access path setting is required if the storage area is defined from several HBAs in multipath disk control or on the cluster system. In other configurations, recheck the settings because data may have been corrupted.
The message showing the normal end of the access path is displayed. Check the contents, and click the <OK> button.
In Solaris OS server nodes, the status of this access path is normal (Blue). In other OS server nodes, the status of this access path is normal (Green) or normal (Blue). At this time, a momentary HBA error causes the HBA to go to "warning!" status. From [View], execute [Refresh] and then verify that the latest status is effective. When setting several access paths simultaneously, perform step 6 and after to add the access paths. When an access path is set in Windows2000 or Windows2003, devices are automatically recognized according to the number of the LUNs set in the access path, and a device addition message is displayed. Alternatively, the device addition message may be output to the event log as Removable Storage. However, a prerequisite is that the device support plug&play. (ETERNUS/GR supports this function.)
For ETERNUS storage devices, "Host response" related to [Host worldwide name] of the preset host affinity is "00" for the ETERNUS3000 or "Default" for the ETERNUS8000, ETERNUS6000, ETERNUS4000, ETERNUS2000 and ETERNUS DX60/DX80.
Change the "Host response" setting by ETERNUSmgr, if necessary. For details, refer to the related ETERNUS disk array manual.
[Setting an access path for a tape in Solaris OS] Write information such as a LUN number in a configuration definition file (e.g., st.conf) for the target tape driver. If the HBA is the SN10-FC01 or FC64-1063, however, WWPN binding information must also be written. After the access path has been set, the following tape driver can display LUN information: st,ftla,fsct,IBMtape,mt,lb,sg.
[GR720, GR730 (version V11L21 or earlier), GR740, GR820, GR840 (version V03L52P1939 or earlier)] Restart the GR device. The device must be restarted to reflect the GR settings defined from this software. However, unspecified versions and some of the GR740, GR820, GR840 P19 versions (for these versions, contact Fujitsu) need not be restarted because the ETERNUS8000, ETERNUS6000, ETERNUS4000, ETERNUS3000, ETERNUS2000 and ETERNUS DX60/DX80 series supports the hot system configuration setting reflection function.
[Under the hddvadm-M execution environment, where the hot system expansion function of multi-path disk control (ETERNUS Multipath Driver 2.0.1 or later, GR Multipath Driver 1.0.4 or later) has been set in the Solaris OS server node] Execute the command below on the target server node to enable the server node to recognize the storage device.
- When PW008FC2A, PW008FC2-G, PW008FC3, GP7B8FC1A, GP7B8FC1-G, GP7B8FC1, SE0X7F11F or SE0X7F12F is set as the access path for HBA, the driver validates the set information. Execute a command to change the hot system expansion properties of the driver. Execute the following FUJITSU PCI Fibre Channel driver command:
```
# /usr/sbin/FJSVpfca/fc_config -v
```
  Note that the server must be rebooted for a FUJITSU PCI Fibre Channel driver that does not support this command. Use the following command to reboot the server node:
```
# /usr/sbin/shutdown -y -i6 -g0
```
- To automatically build a multipath device, execute the grmpdautoconf command. For details on the command, see the driver manual.
```
# /usr/sbin/grmpdautoconf
```
  To automatically build a multipath device that uses the ETERNUS multipath driver and has a path passing through multiple Fibre Channel switches, execute the command after confirming path redundancy and specifying the "-X" option (because the grmpdautoconf command cannot check whether the redundancy of a path passing through multiple Fibre Channel switches is guaranteed).
```
# /usr/sbin/grmpdautoconf -X
```
[On a Solaris OS server node with multipath disk control (GR multipath driver 1.0.3 or earlier, MPLB, MPHD, HDDV2.2 or later) and hot system expansion specified (hddvadm -M execution environment)] Execute the following command on the target server node so that the target server node recognizes the storage unit.
- When PW008FC2A, PW008FC2-G, PW008FC3, GP7B8FC1A, GP7B8FC1-G, GP7B8FC1, SE0X7F11F or SE0X7F12F is set as the access path for HBA, the driver validates the set information. Execute a command to change the hot system expansion properties of the driver. Execute the following FUJITSU PCI Fibre Channel driver command:
```
# /usr/sbin/FJSVpfca/fc_config -v
```
  Note that the server must be rebooted for a FUJITSU PCI Fibre Channel driver that does not support this command. Use the following command to reboot the server node:
```
# /usr/sbin/shutdown -y -i6 -g0
```
- In Solaris 9 OS, hddv.conf is edited if needed (see the multipath disk control (GR Multipath Driver, MPLB, MPHD, HDDV) various driver manuals). The following command is executed on the server node to fetch a storage device.
```
# update_drv -f hddv
```
- If the Solaris OS version is other than the Solaris 8 OS and Target ID which is specified at this software access path setting is already defined (reserved) in hddv.conf file, execute the command below on the target host to fetch device information.
```
# /usr/sbin/hddvadmdr
```
- If the Solaris OS version is other than the Solaris 8 OS and Target ID which is specified at this software access path setting is not defined (not reserved) in hddv.conf file, write the target ID into hddv.conf and execute the command below on the target host to fetch device information.
  To reserve space for future expansion, during hddv.conf editing, remove the comment characters on the lines for the Target ID and LUN involved. Then, after the next reboot, hot system expansion is enabled without another reboot. If the Fibre Channel interface is used to reserve this space, specify 16 or a higher number for the Target ID. Make sure that the Target ID number is not the same as that in sd.conf.
```
# touch /reconfigure
# /usr/sbin/shutdown -y -i6 -g0
```
With the above setting, the hddv driver can recognize the logical storage unit. If necessary, execute the command that builds an extension path to the multipath instance or the command that configures the multipath instance. For information about the commands, refer to the applicable driver manual (mplbconfig/iompadm add/iompadm new). After executing this driver command, click the multipath instance in the Server view. The extension path in addition to the existing path is highlighted. This indicates a correctly incorporated path.
[Under the hddadm-m execution environment, where the non-hot system expansion function of multi-path disk control (GR Multipath Driver, MPLB, MPHD, or HDDV) has been set in the Solaris OS server node or under the environment that does not use the multi-path disk control] Execute the following command on the target server node to enable the server node to recognize the device:
If the HBA is XSEFC401AF, XSEFC402AF, SG-XPCI1FC-QF2, SG-XPCI2FC-QF2, SG-XPCI1FC-QL2 or SG-XPCI2FC-QF2-Z
- Check the storage Ap_id using the cfgadm -al command, and make the OS recognize the LUN using the cfgadm -c configure Ap_id command. For details about the commands, check the man command.
- Non-GR Multipath Driver, MPLB, MPHD, or HDDV environment (including the tape environment)
```
# touch /reconfigure
# /usr/sbin/shutdown -y -i6 -g0
```
- GR Multipath Driver, MPLB, MPHD, or HDDV environment
```
# touch /reconfigure
# /usr/sbin/shutdown -y -i6 -g0
# hddvadm -m (The required part of sd.conf is moved to hddv.conf, and the saved mphd.conf/mplb.conf file is restored.)
# touch /reconfigure
# /usr/sbin/shutdown -y -i6 -g0 (mphc.conf/mplb.conf is restored. The existing instances of various drivers (mplb/mphd/hddv) are built.)
```
According to the environment, execute the command that builds an extension path to the multipath instance or the command that configures the multipath instance. For information about the commands, refer to the applicable driver manual (mplbconfig/iompadm add/iompadm new). After executing this driver command, click the multipath instance in the Server view. The extension path in addition to the existing path is highlighted. This indicates a correctly incorporated path.
[Solaris OS server node] Arrange the files in /dev/rdsk with # disks -C command.
[Windows] Restart the unit so that the device is recognized. Even if the device is automatically r ecognized by Windows 2000 or Windows 2003, Fujitsu recommends restarting the unit so that the device is recognized again.
[Linux server node] Restart the unit so that the device is recognized.
[HP-UX server node] Restart the unit to execute device recognition. After restart, check the connection of the device and search for the device file (for example, /dev/dsk/c5t1d0) with #ioscan -funC disk command. If the device file does not exist, create the device file by executing #insf-H <H/W pathname > -e command for H/W path in which the device file is not detected.
[Other server nodes] Perform operations for device recognition.
When the operating system is VMware Infrastructure 3 Version 3.5 (or later) or VMware ESXi 3.5 (or later), reboot the VM host or execute "Rescan" for the HBA that the access path has been set by using VMware Infrastructure Client. For the using method of VMware Infrastructure Client, refer to "Access path management" of "Configuration management" in "4.1.7.2 VMware Infrastructure 3 Version 3.5 (or later) or VMware ESXi 3.5 (or later)".
Check the access path from this software.
[For Solaris OS server node] /dev/rdisk/cXtXdX is created on the server node side. Note that executing [Refresh] from this software displays the access path. If it is possible to check that the LUN was recognized by the OS, the access path will change to normal (Green).
(If the HBA is XSEFC401AF, XSEFC402AF, SG-XPCI1FC-QF2, SG-XPCI2FC-QF2, SG-XPCI1FC-QL2 or SG-XPCI2FC-QF2-Z, it is not possible to check whether LUN is recognized by the OS. For this reason, the access path remains as Normal (Blue) and does not change.)
[Windows server node] A device is generated on the server node side. Using the same method, you can also set access path specification by selecting the server node from storage.
[Linux server node] A device is generated on the server node side. Using the same method, you can also set an access path by selecting the server node from storage.
[HP-UX server node] A device is generated on the server node side. Using the same method, you can also set an access path by selecting the server node from storage.

Note

You can set an access path between server nodes (HBAs) and between storage systems (CAs) by performing drag&drop operations between ports in the Server node view. In such cases, the only action necessary is to set one-to-one WWPN zoning on the Fibre Channel switch. Therefore, one requirement is that WWPN zoning of the Fibre Channel switch can be set. The GUI window cannot display access paths between server nodes(HBAs) and between storage systems (CAs) in a diagram. Check the zoning information in Fibre Channel switch properties. Also, delete an access path according to this zoning information.

To define the GR740 configuration after setting an access path, read existing GR740 configuration definition information from the device, edit it, and transfer it to the GR side. If the existing information is not used on the GR740 side, security settings defined by this software may be overwritten.