This section describes the maintenance procedure for the Storage Cluster environment.
This section, for the purpose of convenience, defines and explains the following names.
Defined Names Used in Explanation in This Section | Meaning of Defined Names |
|---|---|
ETERNUS-A | Primary Storage |
ETERNUS-B | Secondary Storage |
ETERNUS-C | ETERNUS Disk storage system prepares to restructure the Storage Cluster environment after the Primary Storage or the Secondary Storage is removed |
Point
The TFO group status is automatically updated. Re-check it after waiting for a while or manually updating the TFO group status by referring to "9.4.2.2 Updating TFO Group Status" when the status which is different from the procedure is displayed.
Refer to the ETERNUS Disk storage system manuals for the command name and the format of ETERNUS CLI used in the procedure.
For the Advanced Copy maintenance contents when operating AdvancedCopy Manager, refer to "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" and "Table 9.8 When Using AdvancedCopy Manager Replication Management Function".
When the AdvancedCopy Manager Copy Control Module function is in use, refer to "Command References" in the AdvancedCopy Manager Operation Guide for Copy Control Module for information on the commands.
When the AdvancedCopy Manager replication management function is in use, refer to "Command References" in the AdvancedCopy Manager Operation Guide for information on the commands.
Maintenance Contents | Type of Copy Being Executed | ||
|---|---|---|---|
OPC/QuickOPC | SnapOPC+ | EC/REC | |
(a) Stopping the copy session | Confirm the copy session with the acopc query command and stop the copy session with the acopc cancel command. | Confirm the copy session with the acsnap query command and stop the copy session with the acsnap cancel command. | Confirm the copy session with the acec query command and stop the copy session with the acec cancel command. |
(b) Stopping copy sessions when the TFO status is in "Standby" | With the accopy query command, confirm the copy session in the ETERNUS Disk storage system where the TFO status is in "Standby". After that, stop the copy session with the accopy fcancel command. | ||
(c) Deleting AdvancedCopy Manager environment settings | Delete copy pairs with the acpair remove command. | ||
(d) Configuring the AdvancedCopy Manager environment | Add copy pairs with the acpair add command. | ||
(e) Starting a copy session |
| Start the copy session with the acsnap start command. | Start the copy session with the acec start command.
|
(f) Checking the status of the copy session | Confirm the status of the copy session and recovery the copy session by referring to "When Recovering Storage Cluster Continuous Copy Function" in the AdvancedCopy Manager Operation Guide for Copy Control Module. | ||
(g) Stopping management service | Stop the management service with the acservice stop command. | ||
Maintenance Contents | Type of Copy Being Executed | ||
|---|---|---|---|
OPC/QuickOPC | SnapOPC+ | EC/REC | |
(a) Stopping the copy session | Confirm the copy session with the swsrpstat command and stop the copy session with the swsrpcancel command. | ||
(b) Stopping copy sessions when the TFO status is in "Standby" | In the Management Server, confirm the copy session with the accopy query command and stop the copy session with the accopy fcancel command. The replication management function commands cannot execute for the storage device where the TFO status is in "Standby". For this reason, use the AdvancedCopy Manager Copy Control function commands only when stopping the copy session in the storage device where the TFO status is in "Standby". | ||
(c) Deleting AdvancedCopy Manager environment settings | Delete the replication volume information with the swsrpdelvol command. When the copy session exists in the ETERNUS Disk storage system where the TFO status is in "Active", delete the replication volume information with the swsrpdelvol command by specifying the -e option. | ||
(d) Configuring the AdvancedCopy Manager environment | Configure the AdvancedCopy Manager environment with the swsrpsetvol command. | ||
(e) Starting a copy session |
| Start the copy session with the swsrpmake command by specifying the -C option or the -P option. | Start the copy session with the swsrpstartsync command.
|
(f) Checking the status of the copy session | Confirm the status of the copy session and recovery the copy session by referring to "When Recovering Storage Cluster Continuous Copy Function" in the AdvancedCopy Manager Operation Guide for Copy Control Module. | ||
When recovering, the initial copy takes place between the pair volumes. For an estimate of the initial copy required time, refer to "Table 9.6 Time Required for Initial Copy (Standard Value of 1 TB Physical Capacity Volume)".
In an environment that uses the following storage devices, if a failover/failback must be performed while the TFO group phase is "Maintenance", contact your maintenance engineer in advance.
ETERNUS DX S5 series, ETERNUS DX8900 S4, or ETERNUS AF S3 series that has firmware version V11L40-5000 or later
ETERNUS DX S4/S3 series (excluding the ETERNUS DX8900 S4), ETERNUS AF S2 series, AF series, or ETERNUS DX200F that has firmware version V10L90-1000 or later
This section describes the procedure for replacing the ETERNUS Disk storage system for each cabinet.
When Replacing Primary Storage
When ETERNUS-A fails during an operation with a TFO status of "Active", if the Failover mode is "Auto", Automatic Failover is performed. If the Failover mode is "Manual", perform a Manual Failover.
Remove the fiber channel cable connected to the CA port of ETERNUS-A. For iSCSI configurations, remove the LAN cable.
If ETERNUS-A is being operated using the AdvancedCopy Manager Copy Control Module function, stop the management service of AdvancedCopy Manger CCM.
Refer to "(g) Stopping management service" of "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" for the stop procedure of the management service.
Perform the procedure in "9.4.3.12 Temporarily Deleting the Storage Cluster Environment for Recovery" to delete all of the TFO groups.
For FC configurations, in order to take over the logical WWPN/WWNN set in ETERNUS-B, check the WWPN Handover checkbox and delete all of the TFO groups.
For iSCSI configurations, the WWPN Handover checkbox is displayed but grayed out.
Remove ETERNUS-A.
In ETERNUS-C, create the same business volume as ETERNUS-A that is in the process of being removed. At this time, do not hard wire the business server and ETERNUS-C.
Configure the Storage Cluster environment with ETERNUS-B as the Primary Storage and ETERNUS-C as the Secondary Storage.
For iSCSI configurations, be sure to configure the CA port of ETERNUS-C after configuring a TFO group.
Connect the fiber channel disconnected in Step 2 to the CA port of ETERNUS-C and hard wire the connection to the business server. For iSCSI configurations, connect the LAN cable and hard wire the connection to the business server.
After confirming that the phases of all of the TFO groups of ETERNUS-B are "Normal", perform a Manual Failover by selecting all of the TFO groups.
Remove the fiber channel cable connected to the CA port of ETERNUS-B. For iSCSI configurations, remove the LAN cable.
Perform the procedure in "9.4.3.12 Temporarily Deleting the Storage Cluster Environment for Recovery" to delete all of the TFO groups.
For FC configurations, in order to take over the logical WWPN/WWNN set in ETERNUS-C, check the WWPN Handover checkbox and delete all of the TFO groups.
For iSCSI configurations, the WWPN Handover checkbox is displayed but grayed out.
Configure the Storage Cluster environment with ETERNUS-B as the Secondary Storage and ETERNUS-C as the Primary Storage.
For iSCSI configurations, be sure to configure the CA port of ETERNUS-B after configuring a TFO group.
Reconnect the business server to ETERNUS-B which was disconnected in Step 10.
An initial copy from ETERNUS-C to ETERNUS-B is completed, and it returns to former state of the operation.
When operating AdvancedCopy Manager, configure the AdvancedCopy Manager environment.
Refer to "(d) Configuring the AdvancedCopy Manager environment" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the configuration procedure.
Note
Do not reconnect ETERNUS-A after deleting the TFO group set in ETERNUS-B in Step 4. For FC configurations, there is a possibility that data corruption may occur due to WWPN/WWNN duplication. For iSCSI configurations, there is a possibility that data corruption may occur due to duplication of the iSCSI IP address.
When Replacing Secondary Storage
Delete ETERNUS-B from the product and remove it so that it is not managed.
If ETERNUS-B is being operated using the AdvancedCopy Manager Copy Control Module function, stop the management service of AdvancedCopy Manger CCM.
Refer to "(g) Stopping management service" of "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" for the stop procedure of the management service.
Perform the procedure in "9.4.3.12 Temporarily Deleting the Storage Cluster Environment for Recovery" to delete all the TFO groups.
Register ETERNUS-C to the product as the new Secondary Storage.
Reconstruct the Storage Cluster environment by using ETERNUS-A and ETERNUS-C.
When operating AdvancedCopy Manager, configure the AdvancedCopy Manager environment.
Refer to "(d) Configuring the AdvancedCopy Manager environment" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the configuration procedure.
See
Execute Steps 4 and 5 in the Secondary Storage, referring to "When Adding Secondary Storage Where Only Primary Storage Is Used" in "9.3 Work Flow".
Check on the following conditions whether any RAID failure is occurring in the Primary Storage or the Secondary Storage:
The device status is not "Normal", and
The RAID group status is "Broken".
When RAID Failure of Primary Storage Occurred
When the RAID failure of ETERNUS-A occurs during an operation with a TFO status of "Active", if the Failover mode is "Auto", Automatic Failover is performed. If the Failover mode is "Manual", perform a Manual Failover.
This step is not necessary during an operation with a TFO status of "Standby".
If the Failback mode is operating in "Auto", as it is necessary to perform Failback after confirming the copy session status, change this to "Manual".
When operating AdvancedCopy Manager, stop the volume copy session belonging to the failed RAID.
Refer to "(a) Stopping the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Additionally, if the copy session in ETERNUS-A is not stopped as a result of checking the copy session status, stop only the copy session in ETERNUS-A. When using the Storage Cluster Continuous Copy function and when Automatic Failover has been performed, it is possible to just stop copy sessions on the volume of ETERNUS-A.
For the procedure for stopping the copy sessions of ETERNUS-A, refer to "(b) Stopping copy sessions when the TFO status is in "Standby" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.8 When Using AdvancedCopy Manager Replication Management Function".
For ETERNUS-A, perform the procedure in "9.4.3.8 Releasing TFO Pair" to release the TFO pair.
Maintain the RAID of ETERNUS-A.
For ETERNUS-A, perform the procedure in "9.4.3.9 Recovering TFO Pair" to recover the TFO pair.
Wait for the initial copy from ETERNUS-B to ETERNUS-A to complete.
After confirming that all the following conditions are satisfied, proceed to the next step.
On the Storage Cluster overview screen, the TFO group phase is "Failback Ready".
On the Storage Cluster TFO group details screen, the session status of the TFO pair is "Active" and the session phase is "Equivalent".
If the TFO group phase is "Maintenance" on the Storage Cluster overview screen, refer to "Meaning and Action Plan" for "Maintenance" in the "Phase" table of "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and perform the necessary corrective actions.
See
For details of the TFO group status, refer to "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and for details of the TFO pair session information, refer to "9.4.2.10 Confirming the Status on the TFO Group Details Screen".
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
Check that the copy session status matches between ETERNUS-A and ETERNUS-B.
Refer to "(f) Checking the status of the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Perform a Manual Failback.
If the Failback mode is changed to "Manual" in Step 2, change to "Auto".
When RAID Failure of Secondary Storage Occurred
If the RAID failure of ETERNUS-B occurs during an operation with a TFO status of "Active", perform a Manual Failback.
This step is not necessary during an operation with a TFO status of "Standby".
When operating AdvancedCopy Manager, stop the volume copy session belonging to the failed RAID.
Refer to "(a) Stopping the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Additionally, if the copy session in ETERNUS-B is not stopped as a result of checking the copy session status, stop only the copy session in ETERNUS-B. When using the Storage Cluster Continuous Copy function and when the Manual Failback has not been performed in Step 1, it is possible to just stop copy sessions on the volume of ETERNUS-B.
For the procedure for stopping the copy sessions of ETERNUS-B, refer to "(b) Stopping copy sessions when the TFO status is in "Standby" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.8 When Using AdvancedCopy Manager Replication Management Function".
For ETERNUS-B, perform the procedure in "9.4.3.8 Releasing TFO Pair" to release the TFO pair.
Maintain the RAID of ETERNUS-B.
For ETERNUS-B, perform the procedure in "9.4.3.9 Recovering TFO Pair" to recover the TFO pair.
Wait for the copy from ETERNUS-A to ETERNUS-B to complete.
After confirming that all the following conditions are satisfied, proceed to the next step.
On the Storage Cluster overview screen, the TFO group phase is "Normal".
On the Storage Cluster TFO group details screen, the session status of the TFO pair is "Active" and the session phase is "Equivalent".
If the TFO group phase is "Maintenance" on the Storage Cluster overview screen, refer to "Meaning and Action Plan" for "Maintenance" in the "Phase" table of "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and perform the necessary corrective actions.
See
For details of the TFO group status, refer to "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and for details of the TFO pair session information, refer to "9.4.2.10 Confirming the Status on the TFO Group Details Screen".
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
Check that the copy session status matches between ETERNUS-A and ETERNUS-B.
Refer to "(f) Checking the status of the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Check on the following conditions whether any RAID close is occurring in the Primary Storage or the Secondary Storage:
The device status is not "Normal", and
The RAID group status is "No Disk Path".
When RAID Close of Primary Storage Occurred
If the RAID close of ETERNUS-A occurs during an operation with a TFO status of "Active", Automatic Failover is performed if the Failover mode is "Auto", however, Automatic Failover is not performed if the Failover mode is "Manual". If the Failover mode is "Manual", perform a Manual Failover.
This step is not necessary during an operation with a TFO status of "Standby".
If the Failback mode is operating in "Auto", as it is necessary to perform Failback after confirming the copy session status, change this to "Manual".
When operating AdvancedCopy Manager, stop the copy sessions on the volume to which the closed RAID belongs.
Refer to "(a) Stopping the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Additionally, if the copy session in ETERNUS-A is not stopped as a result of checking the copy session status, stop only the copy session in ETERNUS-A. When using the Storage Cluster Continuous Copy function and when the fail over has not been performed in Step 1, it is possible to just stop copy sessions on the volume of ETERNUS-A.
For the procedure for stopping the copy sessions of ETERNUS-A, refer to "(b) Stopping copy sessions when the TFO status is in "Standby" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.8 When Using AdvancedCopy Manager Replication Management Function".
For ETERNUS-A, perform the procedure in "9.4.3.8 Releasing TFO Pair" to release the TFO pair.
Maintain the RAID of ETERNUS-A.
For ETERNUS-A, perform the procedure in "9.4.3.9 Recovering TFO Pair" to recover the TFO pair.
Wait for the copy from ETERNUS-B to ETERNUS-A to complete.
After confirming that all the following conditions are satisfied, proceed to the next step.
On the Storage Cluster overview screen, the TFO group phase is "Failback Ready".
On the Storage Cluster TFO group details screen, the session status of the TFO pair is "Active" and the session phase is "Equivalent".
If the TFO group phase is "Maintenance" on the Storage Cluster overview screen, refer to "Meaning and Action Plan" for "Maintenance" in the "Phase" table of "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and perform the necessary corrective actions.
See
For details of the TFO group status, refer to "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and for details of the TFO pair session information, refer to "9.4.2.10 Confirming the Status on the TFO Group Details Screen".
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
Check that the copy session status matches ETERNUS-A and ETERNUS-B.
Refer to "(f) Checking the status of the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Perform a Manual Failback.
If the Failback mode is changed to "Manual" in Step 2, change to "Auto".
When RAID Close of Secondary Storage Occurred
If the RAID close of ETERNUS-B occurs during an operation with a TFO status of "Active", perform a Manual Failback.
This step is not necessary during an operation with a TFO status of "Standby".
When operating AdvancedCopy Manager, stop the copy sessions on the volume to which the closed RAID belongs.
Refer to "(a) Stopping the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Additionally, if the copy session in ETERNUS-B is not stopped as a result of checking the copy session status, stop only the copy session in ETERNUS-B. When using the Storage Cluster Continuous Copy function and when the Manual Failback has not been performed in Step 1, it is possible to just stop copy sessions on the volume of ETERNUS-B.
For the procedure for stopping the copy sessions of ETERNUS-B, refer to "(b) Stopping copy sessions when the TFO status is in "Standby" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.8 When Using AdvancedCopy Manager Replication Management Function".
For ETERNUS-B, perform the procedure in "9.4.3.8 Releasing TFO Pair" to release the TFO pair.
Maintain the RAID of ETERNUS-B.
For ETERNUS-B, perform the procedure in "9.4.3.9 Recovering TFO Pair" to recover the TFO pair.
Wait for the copy from ETERNUS-A to ETERNUS-B to complete.
After confirming that all the following conditions are satisfied, proceed to the next step.
On the Storage Cluster overview screen, the TFO group phase is "Normal".
On the Storage Cluster TFO group details screen, the session status of the TFO pair is "Active" and the session phase is "Equivalent".
If the TFO group phase is "Maintenance" on the Storage Cluster overview screen, refer to "Meaning and Action Plan" for "Maintenance" in the "Phase" table of "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and perform the necessary corrective actions.
See
For details of the TFO group status, refer to "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and for details of the TFO pair session information, refer to "9.4.2.10 Confirming the Status on the TFO Group Details Screen".
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
Check that the copy session status matches ETERNUS-A and ETERNUS-B.
Refer to "(f) Checking the status of the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Check on the following conditions whether any failure is occurring in the CA ports belonging to the Primary TFO Group due to CA port failure or connection failure during an operation with a TFO status of is "Active":
The status of the port in the storage device is "Error", or
The SNMP Trap notifying that a CA port of the storage device to which Primary TFO Group belongs is linked down is displayed in the event log and the dashboard of Web Console.
When Using the Automatic Failover Function Triggered by CA Port Linkdown
If all the CA ports belonging to the Primary TFO Group are linked down during an operation with a TFO status of is "Active", Automatic Failover is performed. Recover the environment according to the following procedure:
From the Storage Cluster overview screen of Web Console, check that the TFO group phase is "Failback Ready".
Maintain the CA port to recover the CA Port.
Perform a Manual Failback.
Note
If you perform a Manual Failback without recovering a closed CA port, Automatic Failover may be performed and business I/O may be stopped. For this reason, after maintaining the CA port, perform a Manual Failback.
When Not Using the Automatic Failover Function Triggered by CA Port Linkdown
If all the CA ports belonging to the Primary TFO Group are linked down during an operation with a TFO status of is "Active", Automatic Failover is not performed. Recover the environment according to the following procedure:
If the Failback mode is operating in "Auto", as it is necessary to perform Failback after recovering the closed CA ports, change this to "Manual".
Perform a Manual Failover. Upon completion of the failover, from the Storage Cluster overview screen of Web Console, check that the TFO group phase is "Failback Ready".
Maintain the CA port to recover the CA Port.
Perform a Manual Failback.
If the Failback mode is changed to "Manual" in Step 1, change to "Auto".
Point
Refer to "Configuring TFO Group" in "9.4.1 Installation" for information on the Automatic Failover function triggered by CA port linkdown.
Check on the following conditions whether any bad sectors are occurring in the Primary Storage or the Secondary Storage:
The following message is displayed in Overview of the ETERNUS Web GUI:
Bad Sector has occurred. Please check the details by the volume navigation.
The bad sector areas are recovered from devices for which TFO status is "Active" to the Standby device.
If the Status column on Volume tab of the TFO group details screen is set to anything other than "Active", contact a Fujitsu customer engineer.
When Bad Sector Occurs in Primary Storage Copy Source
If a bad sector in ETERNUS-A occurs during an operation with a TFO status of "Active", perform a Manual Failover.
This step is not necessary during an operation with a TFO status of "Standby".
If the Failback mode is operating in "Auto", as it is necessary to perform Failback after confirming the copy session status, change this to "Manual".
When operating AdvancedCopy Manager, stop the copy session on volumes that have bad sectors.
Refer to "(a) Stopping the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Additionally, if the copy session in ETERNUS-A is not stopped as a result of checking the copy session status, stop only the copy session in ETERNUS-A. When using the Storage Cluster Continuous Copy function, it is possible to just stop copy sessions on the volume of ETERNUS-A.
For the procedure for stopping the copy sessions of ETERNUS-A, refer to "(b) Stopping copy sessions when the TFO status is in "Standby" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.8 When Using AdvancedCopy Manager Replication Management Function".
For ETERNUS-A, perform the procedure in "9.4.3.8 Releasing TFO Pair" to release the TFO pair.
For ETERNUS-A, perform the procedure in "9.4.3.9 Recovering TFO Pair" to recover the TFO pair.
Wait for the copy from ETERNUS-B to ETERNUS-A to complete.
After confirming that all the following conditions are satisfied, proceed to the next step.
On the Storage Cluster overview screen, the TFO group phase is "Failback Ready".
On the Storage Cluster TFO group details screen, the session status of the TFO pair is "Active" and the session phase is "Equivalent".
If the TFO group phase is "Maintenance" on the Storage Cluster overview screen, refer to "Meaning and Action Plan" for "Maintenance" in the "Phase" table of "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and perform the necessary corrective actions.
See
For details of the TFO group status, refer to "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and for details of the TFO pair session information, refer to "9.4.2.10 Confirming the Status on the TFO Group Details Screen".
Delete the bad sector information for the target LUN from the ETERNUS Web GUI.
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
Check that the copy session status matches ETERNUS-A and ETERNUS-B.
Refer to "(f) Checking the status of the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Perform a Manual Failback.
If the Failback mode is changed to "Manual" in Step 2, change to "Auto".
When Bad Sector Occurs in Secondary Storage Copy Source
If a bad sector in ETERNUS-B occurs during an operation with a TFO status of "Active", perform a Manual Failover.
This step is not necessary during an operation with a TFO status of "Standby".
When operating AdvancedCopy Manager, stop the copy session on volumes on which there are bad sectors.
Refer to "(a) Stopping the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Additionally, if the copy session in ETERNUS-B is not stopped as a result of checking the copy session status, stop only the copy session in ETERNUS-B. When using the Storage Cluster Continuous Copy function, it is possible to just stop copy sessions on the volume of ETERNUS-B.
For the procedure for stopping the copy sessions of ETERNUS-B, refer to "(b) Stopping copy sessions when the TFO status is in "Standby" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.8 When Using AdvancedCopy Manager Replication Management Function".
For ETERNUS-B, perform the procedure in "9.4.3.8 Releasing TFO Pair" to release the TFO pair.
For ETERNUS-B, perform the procedure in "9.4.3.9 Recovering TFO Pair" to recover the TFO pair.
Wait for the copy from ETERNUS-A to ETERNUS-B to complete.
After confirming that all the following conditions are satisfied, proceed to the next step.
On the Storage Cluster overview screen, the TFO group phase is "Normal".
On the Storage Cluster TFO group details screen, the session status of the TFO pair is "Active" and the session phase is "Equivalent".
If the TFO group phase is "Maintenance" on the Storage Cluster overview screen, refer to "Meaning and Action Plan" for "Maintenance" in the "Phase" table of "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and perform the necessary corrective actions.
See
For details of the TFO group status, refer to "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and for details of the TFO pair session information, refer to "9.4.2.10 Confirming the Status on the TFO Group Details Screen".
Delete the bad sector information for the target LUN from the ETERNUS Web GUI.
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
Check that the copy session status matches ETERNUS-A and ETERNUS-B.
Refer to "(f) Checking the status of the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
If an event other than a RAID failure, RAID close, CA port Linkdown, or bad sectors occurs and the session status of the TFO pair becomes "Error Suspend", perform a recovery with this procedure.
Check the following conditions to determine whether the session status of the TFO pair is "Error Suspend".
The TFO group phase is "Maintenance".
The volume session information is "Error Suspend" in the TFO pair session information.
See
For details of the TFO group status, refer to "9.4.2.9 Confirming the Status on the Storage Cluster Overview Screen" and for details of the TFO pair session information, refer to "9.4.2.10 Confirming the Status on the TFO Group Details Screen".
When the Session Status of the TFO Pair in the Primary Storage Becomes Error Suspend Due to an Event
When the session status of the TFO pair in ETERNUS-A is "Error Suspend" during an operation with a TFO status of "Active", if the Failover mode is "Auto", Automatic Failover is performed. If the Failover mode is "Manual", perform a Manual Failover because Automatic Failover is not performed.
This step is not necessary during an operation with a TFO status of "Standby".
If the Failback mode is operating in "Auto", as it is necessary to perform Failback after confirming the copy session status, change this to "Manual".
When operating AdvancedCopy Manager, stop the copy session of the volume whose TFO pair session becomes "Error Suspend".
Refer to "(a) Stopping the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Additionally, if the copy session in ETERNUS-A is not stopped as a result of checking the copy session status, stop only the copy session in ETERNUS-A. When using the Storage Cluster Continuous Copy function and when the fail over has not been performed in Step 1, it is possible to just stop copy sessions on the volume of ETERNUS-A.
For the procedure for stopping the copy sessions of ETERNUS-A, refer to "(b) Stopping copy sessions when the TFO status is in "Standby" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.8 When Using AdvancedCopy Manager Replication Management Function".
For ETERNUS-A, perform the procedure in "9.4.3.8 Releasing TFO Pair" to release the TFO pair.
Depending on the phenomenon, maintain ETERNUS-A.
For ETERNUS-A, perform the procedure in "9.4.3.9 Recovering TFO Pair" to recover the TFO pair.
Wait for the copy from ETERNUS-B to ETERNUS-A to complete.
After confirming that all the following conditions are satisfied, proceed to the next step.
On the Storage Cluster overview screen, the TFO group phase is "Failback Ready".
On the Storage Cluster TFO group details screen, the session status of the TFO pair is "Active" and the session phase is "Equivalent".
If the TFO group phase is "Maintenance" on the Storage Cluster overview screen, check the TFO pair session information and resolve the problem events of the TFO pair sessions that are not in the "Active" status.
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
Check that the copy session status matches between ETERNUS-A and ETERNUS-B.
Refer to "(f) Checking the status of the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Perform a Manual Failback.
If the Failback mode is changed to "Manual" in Step 2, change to "Auto".
When the Session Status of the TFO Pair in the Secondary Storage Becomes Error Suspend Due to an Event
When the session status of the TFO pair in ETERNUS-B is "Error Suspend" during an operation with a TFO status of "Active", perform a Manual Failback.
This step is not necessary during an operation with a TFO status of "Standby".
When operating AdvancedCopy Manager, stop the copy session of the volume whose TFO pair session becomes "Error Suspend".
Refer to "(a) Stopping the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Additionally, if the copy session in ETERNUS-B is not stopped as a result of checking the copy session status, stop only the copy session in ETERNUS-B. When using the Storage Cluster Continuous Copy function and when the Manual Failback has not been performed in Step 1, it is possible to just stop copy sessions on the volume of ETERNUS-B.
For the procedure for stopping the copy sessions of ETERNUS-B, refer to "(b) Stopping copy sessions when the TFO status is in "Standby" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or "Table 9.8 When Using AdvancedCopy Manager Replication Management Function".
For ETERNUS-B, perform the procedure in "9.4.3.8 Releasing TFO Pair" to release the TFO pair.
Depending on the phenomenon, maintain ETERNUS-B.
For ETERNUS-B, perform the procedure in "9.4.3.9 Recovering TFO Pair" to recover the TFO pair.
Wait for the copy from ETERNUS-A to ETERNUS-B to complete.
After confirming that all the following conditions are satisfied, proceed to the next step.
On the Storage Cluster overview screen, the TFO group phase is "Normal".
On the Storage Cluster TFO group details screen, the session status of the TFO pair is "Active" and the session phase is "Equivalent".
If the TFO group phase is "Maintenance" on the Storage Cluster overview screen, check the TFO pair session information and resolve the problem events of the TFO pair sessions that are not in the "Active" status.
When operating AdvancedCopy Manager, start the copy session.
Refer to "(e) Starting a copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
Check that the copy session status matches between ETERNUS-A and ETERNUS-B.
Refer to "(f) Checking the status of the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
This section describes the procedure when running temporarily with a single system, such as when updating the firmware version.
When Maintaining Primary Storage
Change to "Manual" when operating the Failback mode in "Auto".
When maintaining ETERNUS-A during an operation with a TFO status of "Active", perform a Manual Failover.
Maintain ETERNUS-A.
When stopping ETERNUS-A and when ETERNUS-A is being operated using the AdvancedCopy Manager Copy Control Module function, stop ETERNUS-A first and then stop the management service of AdvancedCopy Manager CCM.
Refer to "(g) Stopping management service" of "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" for the stop procedure of the management service.
Check that the TFO group operating status is "Failback Ready".
Check that the copy session status matches ETERNUS-A and ETERNUS-B.
Refer to "(f) Checking the status of the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
Perform a Manual Failback.
If the Failback mode is changed to "Manual" in Step 1, change to "Auto".
When Maintaining Secondary Storage
When maintaining ETERNUS-B during an operation with a TFO status of "Active", perform a Manual Failover.
Maintain ETERNUS-B.
When stopping ETERNUS-B and when ETERNUS-A is being operated using the AdvancedCopy Manager Copy Control Module function, stop ETERNUS-B first and then stop the management service of AdvancedCopy Manager CCM.
Refer to "(g) Stopping management service" of "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" for the stop procedure of the management service.
Check that the TFO group operating status is "Normal".
Check that the copy session status matches ETERNUS-A and ETERNUS-B.
Refer to "(f) Checking the status of the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
When Updating Firmware Version
Change to "Manual" when operating the Failback mode in "Auto".
Perform a Manual Failover for all of the Primary TFO Groups of ETERNUS-A.
Restart ETERNUS-A after applying the firmware to ETERNUS-A.
Perform a Manual Failback for all of the Secondary TFO Groups of ETERNUS-B.
Perform a Manual Failover for all of the Primary TFO Groups of ETERNUS-B.
Restart ETERNUS-B after applying the firmware to ETERNUS-B.
Perform a Manual Failback for all of the Secondary TFO Groups of ETERNUS-A.
If the Failback mode is changed to "Manual" in Step 1, change to "Auto".
The operation to release a TFO pair is used for maintenance work when a RAID failure, a RAID close, or a bad sector occurs, or when the session status of the TFO pair becomes "Error Suspend".
After releasing the TFO pair to stop synchronization between volumes, perform a maintenance.
The procedure to release a TFO pair is as follows. This operation can be performed from both the Primary Storage and the Secondary Storage.
Click Storage on the global navigation tab.
Registered ETERNUS Disk storage systems are displayed on the Main pane.
On the Main pane, click the Name of a target ETERNUS Disk storage system.
On the Category pane, click Storage Cluster.
Created TFO groups are displayed on the Main pane.
On the Main pane, click the Name of a target TFO group.
The TFO group details screen is displayed on the Main pane.
On the Main pane, click the Volume tab.
The information for pairs of local volume and remote volume is displayed.
After checking the target volume checkbox to be released the TFO pair, click Release Pair under TFOV on the Action pane.
The information confirmation screen is displayed.
After checking the displayed information, click Release.
As with the operation to release a TFO pair, the operation to recover a TFO pair is used for maintenance work when a RAID failure, a RAID close, or a bad sector occurs, or when the session status of the TFO pair becomes "Error Suspend".
After resolving the incident, recover the TFO pair to restart the synchronization of the volumes.
The procedure to recover a TFO pair is as follows. This operation can be performed from both the Primary Storage and the Secondary Storage.
Click Storage on the global navigation tab.
Registered ETERNUS Disk storage systems are displayed on the Main pane.
On the Main pane, click the Name of a target ETERNUS Disk storage system.
On the Category pane, click Storage Cluster.
Created TFO groups are displayed on the Main pane.
On the Main pane, click the Name of a target TFO group.
The TFO group details screen is displayed on the Main pane.
On the Main pane, click the Volume tab.
The information for pairs of local volume and remote volume is displayed.
After checking the target volume checkbox to be recovered the TFO pair, click Recover Pair under TFOV on the Action pane.
The information confirmation screen is displayed.
After checking the displayed information, click Recover.
Point
By recovering a TFO pair, a synchronization between the paired volumes are performed with the initial copy. Refer to "Table 9.6 Time Required for Initial Copy (Standard Value of 1 TB Physical Capacity Volume)" for the time required for an initial copy.
Note
Synchronization with initial copy are performed from volumes with a TFO status of "Active" to volumes with a TFO status of "Standby". Before performing the work in this section, confirm that the direction of the initial copy is correct.
To change the operation mode or port pair for the set TFO group, perform the following procedure.
To delete all the port pairs that are already set and add new port pairs, check the status of the TFO group whose settings are to be changed.
Confirm that the value of the Active/Standby column for the Primary Storage is "Active" and the value of the Active/Standby column of the Secondary Storage is "Standby".
Note
For the operation in the TFO group Configuration screen that is described in Step 8, if all the port pairs that are already set are deleted at the same time as adding new port pairs, this product reconfigures the TFO group after the TFO group settings are temporarily deleted. Temporarily deleting the TFO group interrupts the synchronization between the Primary/Secondary storage devices, and reconfiguring the TFO group starts an initial copy from the Primary Storage to the Secondary Storage.
When this initial copy is executed, the data of the Secondary Storage is rewritten to the data of the Primary Storage and if the work in this section is performed while the status of the TFO group in the Secondary Storage is "Active", data corruption of the Secondary Storage may occur.
When deleting all the port pairs that are already set and adding new port pairs and when operating AdvancedCopy Manager, stop the copy session of volumes that belong to the TFO group to be changed.
Refer to "(a) Stopping the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Click Storage on the global navigation tab.
Registered ETERNUS Disk storage systems are displayed on the Main pane.
On the Main pane, click the Name of a target ETERNUS Disk storage system.
On the Category pane, click Storage Cluster.
The items on the Category pane switch to those associated with Storage Cluster function. Additionally, created TFO groups are displayed on the Main pane.
After selecting a TFO group for which you want to change the setting on the Main pane, click Set under TFO Group on the Action pane.
The TFO Group Configuration Wizard screen is displayed.
The Selection screen for ETERNUS Disk storage systems and options is displayed.
Select Failover Mode and Failback Mode to change the mode for the selected TFO group.
On completion of input, click Next.
The TFO Group Configuration screen is displayed.
Select from a list of ports for the Primary Storage and the Secondary Storage, one port for each storage to be paired and click Add. When deleting, select an unnecessary pair from the Port Pair List table to click Delete.
When deleting all the port pairs that are already set and adding new port pairs, after the completion of the change operation, an initial copy is performed from the Primary Storage to the Secondary Storage.
On completion of required configuration, click Next.
The Setting Confirmation screen is displayed.
If the information is correct, click Set.
A warning dialog box is displayed.
When changing the TFO group settings, click OK.
TFO group changes are performed with the set content.
If an initial copy from the Primary Storage to the Secondary Storage is performed, wait until the initial copy is completed. For an estimate of the initial copy required time, refer to "Table 9.6 Time Required for Initial Copy (Standard Value of 1 TB Physical Capacity Volume)".
When deleting all the port pairs that are already set and adding new port pairs and when operating AdvancedCopy Manager, start a copy session.
Refer to "(e) Starting a copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session start procedure.
Check that the copy session status matches between the Primary Storage and the Secondary Storage.
Refer to "(f) Checking the status of the copy session" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session status confirmation procedure.
The procedure to change the iSCSI IP address when using Storage Cluster for iSCSI configurations varies depending on the target box and the status of the iSCSI IP address setting in both boxes before and after the change.
Box for Changing iSCSI IP Address | Status of iSCSI IP Address Both Boxes Before Change | Status of iSCSI IP Address Both Boxes After Change | Required Additional Work for Changing iSCSI IP Address |
|---|---|---|---|
Both boxes | Matched | Matches | Work 1 |
Does not match | Work 1 and Work 2 | ||
Mismatched | Matches | Work 1 | |
Does not match | Work 1 and Work 2 | ||
Primary Storage only | Matched | Does not match | Work 1 |
Mismatched | Matches | Work 1 | |
Does not match | Work 1 | ||
Secondary Storage only | Matched | Does not match | Work 2 |
Mismatched | Matches | None | |
Does not match | Work 2 |
Work 1 and Work 2 listed in the above table are as follows. When both are required, perform in the order of Work 1 and then Work 2.
Check whether the business server recognizes the post-change iSCSI IP address on the Primary Storage.
If it is not recognized, make the business server recognize the iSCSI IP address of the Primary Storage after the change.
Take the following steps:
Refer to "9.4.2.6 Manual Failover/Failback" to perform a Manual Failover.
Make the business server recognize the iSCSI IP address of the Secondary Storage after the change.
Refer to "9.4.2.6 Manual Failover/Failback" to perform a Manual Failback.
See
Refer to "Change FC/iSCSI/SAS Port Settings" in the Web Console Guide for information on how to change the iSCSI IP address of CA ports.
When temporarily deleting the Storage Cluster environment for maintenance work, delete the TFO groups.
Deleting TFO groups clears the Storage Cluster operation, clearing the synchronization of volumes, too.
For FC configurations and when removing the Primary Storage after failover to the Secondary Storage, the Storage Cluster operation must be canceled and the logical WWPN/WWNN set for the ports to the Secondary Storage must not be canceled but inherited. At that stage, specify WWPN Handover in Step 6.
Note
If the work in this section is performed, the WWPN/WWNN of the CA port in both the Primary Storage and the Secondary Storage has the same status. If the CA port of both devices become "Active" in that state, a conflict occurs with the WWPN/WWNN and a data corruption may occur. Because of that, observe the following for the work in this section.
Do not perform the work in this section while the Primary Storage is connected.
For iSCSI configurations, after confirming that one of the following conditions is satisfied, perform the work in this section.
The storage device in the standby side or the storage device to be replaced is not connected to SAN.
The iSCSI IP address of the iSCSI port is not a duplicate in the same network.
The procedure to temporarily delete TFO groups for recovery is as follows.
When operating AdvancedCopy Manager, stop the copy session and delete the AdvancedCopy Manager environment.
Refer to "(a) Stopping the copy session" and "(c) Deleting AdvancedCopy Manager environment settings" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Click Storage on the global navigation tab.
Registered ETERNUS Disk storage systems are displayed on the Main pane.
On the Main pane, click the Name of a target ETERNUS Disk storage system.
On the Category pane, click Storage Cluster.
Created TFO groups are displayed on the Main pane.
Select the target TFO groups on the Main pane and click Delete under TFO Group on the Action pane.
The TFO Group Deletion Wizard screen is displayed.
The Option Selection/Confirmation screen is displayed.
Check the WWPN Handover checkbox.
For iSCSI configurations, the WWPN Handover checkbox is displayed but grayed out.
Click Delete.
For FC configurations, on completion of deletion, make sure on the FC Port List screen that WWPN is inherited. The procedure is as follows:
For iSCSI configurations, the values set to the ports are kept as they are and no confirmation is required.
Click Storage on the global navigation tab.
Registered ETERNUS Disk storage systems are displayed on the Main pane.
On the Main pane, click the Name of the ETERNUS Disk storage system specified as the Secondary Storage for Storage Cluster.
On the Category pane, click Connectivity.
A list of port types is displayed on the Main pane.
On the Main pane, click No. of Ports whose type is FC.
A list of FC ports is displayed on the Main pane. When a value is displayed in the Logical WWPN column and the TFO Status column is "-" (hyphen), that port inherited the logical WWPN/WWNN when TFO group was deleted.
Note
If the work in this section is performed, the business server cannot connect to the storage and the business volume between the Primary Storage and Secondary Storage is out of sync. Perform the work after confirming that there are no problems with the completion of the operations that use the Storage Cluster function and that there are no problems even if the transactions for the business volume are stopped to perform the work.
To delete the Storage Cluster environment, perform the following procedure.
Deleting Access Path
For both the Primary Storage and the Secondary Storage, delete the access path using Web Console or the storageadm zone command.
Deleting Business Volumes from Storage Cluster Environment
Delete all the business volumes that are used by the Storage Cluster environment. Refer to "9.4.2.3 Adding and Deleting Business Volume" for information on how to delete them.
Deleting TFO Groups
After confirming that no TFO pair is registered in the TFO groups, use Web Console to delete all the TFO groups.
Note
Do not specify WWPN Handover in Step 6.
For iSCSI configurations, after confirming that one of the following conditions is satisfied, perform the procedure.
The storage device in the standby side is not connected to SAN.
The iSCSI IP address of the iSCSI port is not a duplicate in the same network.
The procedure for deleting TFO groups is as follows.
When operating AdvancedCopy Manager, stop the copy session and delete the AdvancedCopy Manager environment.
Refer to "(a) Stopping the copy session" and "(c) Deleting AdvancedCopy Manager environment settings" in "Table 9.7 When Using AdvancedCopy Manager Copy Control Module Function" or in "Table 9.8 When Using AdvancedCopy Manager Replication Management Function" for the copy session stop procedure.
Click Storage on the global navigation tab.
Registered ETERNUS Disk storage systems are displayed on the Main pane.
On the Main pane, click the Name of a target ETERNUS Disk storage system.
On the Category pane, click Storage Cluster.
Created TFO groups are displayed on the Main pane.
Select the target TFO groups on the Main pane and click Delete under TFO Group on the Action pane.
The TFO Group Deletion Wizard screen is displayed.
The Option Selection/Confirmation screen is displayed.
Do not check the WWPN Handover checkbox.
For iSCSI configurations, the WWPN Handover checkbox is displayed but grayed out.
Click Delete.
For FC configurations, on completion of deletion, make sure on the FC Port List screen that WWPN is inherited. The procedure is as follows:
For iSCSI configurations, the values set to the ports are kept as they are and no confirmation is required.
Click Storage on the global navigation tab.
Registered ETERNUS Disk storage systems are displayed on the Main pane.
On the Main pane, click the Name of the ETERNUS Disk storage system specified as the Secondary Storage for Storage Cluster.
On the Category pane, click Connectivity.
A list of port types is displayed on the Main pane.
On the Main pane, click No. of Ports whose type is FC.
A list of FC ports is displayed on the Main pane. When both the Logical WWPN column and the TFO Status column are "-" (hyphen), the logical WWPN/WWNN is not inherited by those ports when the TFO group is deleted.
Changing REC Path Configuration
If necessary, use Web Console to change the REC path configuration that is being used by the Storage Cluster environment.
Changing Port Configuration
If necessary, use Web Console to change the port (the port for connecting to the business server and the port for the REC path) configuration that is being used by the Storage Cluster environment.
