This software can delete access paths set by it and access paths for Fibre Channel switches.
Delete an access path for which one-to-one WWPN zoning is set for a Fibre Channel switch between server nodes (HBAs) or between storages (CAs) according to the zoning information in Fibre Channel switch properties.
The access path cannot be deleted to change the zone status of the switch to non-zoning (No Security). All the zoning settings of the switch are deleted when a user request to delete an access path is processed, this software creates a dummy zone. Although the loss of zone security as a result of deleting zoning can lead to inadvertent accessing of disk areas during operation, the dummy zone created prevents data destruction.
When changing the zone status of the switch to non-zoning (No Security), manually change the zone status of the switch to No Security. Note that this dummy zone is not deleted even if access path addition processing is executed.
Notes
Only "System Administrator" account can delete access paths.
You cannot delete access paths defined during setup other than for setting one-to-one WWPN zoning such as port zoning, WWNN zoning, or multi-port WWPN zoning in a Fibre Channel switch. (Only the one-to-one WWPN zoning setting is valid in this software.) In such cases, delete a zone from the zone information of Fibre Channel switch properties, or log in directly to the Fibre Channel, and change the setup.
Verify that all Fibre Channel switches cascaded to the Fibre Channel switch associated with the access path setting can be 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 deleting an access path that is configured in the FC routing functionality LSAN zone in this software, manually delete the LSAN zone in the device in advance.
Server Node Setting
If Fujitsu multipath disk control mechanism or msdsm on the Windows server node, be sure to shut down the server node before deleting an access path. If an access path is deleted while the server node is in operation, a very long time is required to shut down the server node later because of the operation of Windows path detection logic.
To delete the access path of Fujitsu multipath disk control mechanism or msdsm on the same server node as the Management Server from this software, shut down the Management Server, disconnect the FC cable from the access path to be deleted, restart the admin server, and delete the access path.
For Unix, execute umount for the access path to be deleted.
Physical Removal (Only for Solaris environments)
When ETERNUS Multipath Driver 2.0.1 or higher is used and the access path to be deleted is physically connected to a Fibre Channel switch for which no zone is set, physically remove the access path in advance such as by disconnecting the cable for which access path deletion is to be executed.
Delete a set access path.
[Solaris (MPLB, MPHD environment)] Release the multipath setting.
Refer to the relevant driver's manual for information on the command and command parameters.
If MPLB 2.2 and higher, execute the following command:
# mplbconfig (arguments are required, -d option)
If MPLB 2.1 and former or MPHD, execute the following command:
# iompadm (arguments are required, destroy option)
MPLB2.1 or earlier and MPHD do not support the commands that add and remove paths. Delete the multipath instance by using the above command (iompadm destroy).
[Solaris (MPLB, MPHD, HDDV environment)] Release HDDV.
When the hot system expansion function of server node is disabled, execute the following commands:
# hddvadm -i
hddv.conf is moved to sd.conf, and the mphd.conf/mplb.conf file is saved.
[Windows] If Fujitsu multipath disk control mechanism or msdsm is set, shut down the Windows server node. If the Windows server node is active in this environment, this software suppresses access path deletion.
Using Web Console, execute the deletion of the target access path.
[ETERNUS Multipath Driver 2.0.1 or higher] Execute the grmpdautoconf command to implement path removal.
(Refer to the ETERNUS Multipath Driver User's Guide for details about the command specifications.)
[Solaris] Follow the procedure below so that the server node recognizes the storage unit.
In the hot system expansion (hddvadm -M) environment of ETERNUS Multipath Driver 2.0.1 or higher, MPLB, MPHD, or HDDV, execute the command shown below. After path removal, the server must be restarted to enable the Fibre Channel card definition of the server node.
# /usr/sbin/shutdown -y -i6 -g0 (restarts the server) # disks -C
In an environment using MPLB2.2 or later, MPHD, and HDDV with non-hot system expansion or normal specified (hddvadm -m), execute the following operations:
#touch /reconfigure
# /usr/sbin/shutdown -y -i5 -g0
Start it in single user mode.
# 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 (Instances for each driver (mplb/mphd/hddv) are configured when the definition file is restored.)
# disks -C
In an environment using MPLB2.1 or earlier
#touch /reconfigure
# /usr/sbin/shutdown -y -i5 -g0
Start it in single user mode.
# 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
# disks -C
Reconfigure the multipath by using the new #iompadm command.
In an environment where neither the hard disk driver (HDDV) nor multipath control (MPHD MPLB) is used
#touch /reconfigure
# /usr/sbin/shutdown -y -i6 -g0
# disks -C
Check the access path from this software.
[Windows] Restart the device.
[Linux] Restart the device.
[HP-UX] Restart the device.
[AIX] Restart the device.
[Other server nodes] Perform operations for device deletion recognition.
For VMware vSphere, perform the Reload Conf. operation for the target server node either after rebooting the VM host or after rescanning for the HBA in which the access path is set from VMware vCenter Server or VMware vSphere Client.
