Справочник Пользователя для Q-Logic 8200 SERIES
4 – Using the SANbox SSP
Using the SVM GUI to Manage Virtual Storage
4-10
SN0054628-00 A
Q
4. Assign permissions: R/W for read and write or Off (read only is not supported),
and then click Continue.
5. The new volume displays in the volume list.
6. Perform a hardware rescan on the system. Depending on the system, you may
also need to reboot the initiator to discover the new volume.
4.5.1
Failing Back
Failover to secondary paths on the back-side and front-side is automatic when you
are using an SVM appliance, while failback is manual. Failback causes I/O traffic
to resume using the primary paths. The system does not automatically fail back
once the primary back-side paths are restored. The administrator must perform an
operation on the primary paths to make them active. Until the primary paths are
also active, the system continues using the secondary paths.
are using an SVM appliance, while failback is manual. Failback causes I/O traffic
to resume using the primary paths. The system does not automatically fail back
once the primary back-side paths are restored. The administrator must perform an
operation on the primary paths to make them active. Until the primary paths are
also active, the system continues using the secondary paths.
On the back-side, if primary path failure has forced the activation of secondary
paths, the primary paths must be made available and active as soon as possible.
This requires both addressing the cause of the failure, and performing a manual
failback operation once the primary paths are made available. If you do not manually
fail back, and all secondary back-side paths fail, the system does not automatically
activate the primary paths on the back-side. Even if the primary paths are available,
the system does not automatically activate the primary paths.
paths, the primary paths must be made available and active as soon as possible.
This requires both addressing the cause of the failure, and performing a manual
failback operation once the primary paths are made available. If you do not manually
fail back, and all secondary back-side paths fail, the system does not automatically
activate the primary paths on the back-side. Even if the primary paths are available,
the system does not automatically activate the primary paths.
The failback behavior between front-side and back-side paths differs in the case
that all secondary paths fail. For both front-side and back-side paths, primary paths
are not automatically made active once they are available. On some systems,
however, host-based front-side multipathing software does activate the primary
paths if all secondary paths fail on the front-side. This reduces the urgency of
performing the failback operation on the front-side, since a path failure can still be
tolerated. The administrator must still address the failure on the front-side paths
and return the primary paths to an available state.
that all secondary paths fail. For both front-side and back-side paths, primary paths
are not automatically made active once they are available. On some systems,
however, host-based front-side multipathing software does activate the primary
paths if all secondary paths fail on the front-side. This reduces the urgency of
performing the failback operation on the front-side, since a path failure can still be
tolerated. The administrator must still address the failure on the front-side paths
and return the primary paths to an available state.
To fail back front-side traffic (to resume using primary paths ):
1. Open the SVM GUI, and open Volume Manager in the tree view.
2. Click Volume, select Manage under the host tree, and then click the Manage
button on the far right side of the host that you want to failback.
3. Click Fail Back.
The SVM GUI provides the name of the SANbox SSP that the selected host resumes
using.
using.