Please enter search query.
Search <book_title>...
Storage Foundation 7.4.1 Configuration and Upgrade Guide - Solaris
Last Published:
2019-06-18
Product(s):
InfoScale & Storage Foundation (7.4.1)
Platform: Solaris
- Section I. Introduction and configuration of Storage Foundation
- Section II. Upgrade of Storage Foundation
- Planning to upgrade Storage Foundation
- About the upgrade
- Supported upgrade paths
- Preparing to upgrade SF
- Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
- Upgrading Storage Foundation
- Performing an automated SF upgrade using response files
- Upgrading SF using Boot Environment upgrade
- Performing post-upgrade tasks
- Optional configuration steps
- Recovering VVR if automatic upgrade fails
- Resetting DAS disk names to include host name in FSS environments
- Upgrading disk layout versions
- Upgrading VxVM disk group versions
- Updating variables
- Setting the default disk group
- Upgrading the Array Support Library
- Converting from QuickLog to Multi-Volume support
- Verifying the Storage Foundation upgrade
- Planning to upgrade Storage Foundation
- Section III. Post configuration tasks
- Section IV. Configuration and Upgrade reference
- Appendix A. Installation scripts
- Appendix B. Configuring the secure shell or the remote shell for communications
- About configuring secure shell or remote shell communication modes before installing products
- Manually configuring passwordless ssh
- Setting up ssh and rsh connection using the installer -comsetup command
- Setting up ssh and rsh connection using the pwdutil.pl utility
- Restarting the ssh session
- Enabling and disabling rsh for Solaris
Adding JBOD support for storage arrays for which there is not an ASL available
If an array is of type A/A-A, A/P or ALUA and a suitable ASL is not available, the array must be claimed as a JBOD of type A/P. This is to prevent path delays and I/O failures arising. As JBODs are assumed to be type A/A by default, you must create appropriate JBOD entries for such arrays.
To configure an A/A-A, A/P or ALUA array as a JBOD
- Stop all applications, such as databases, from accessing the VxVM volumes that are configured on the array, and unmount all VxFS file systems and Storage Checkpoints that are configured on the array.
- Add the array as a JBOD of type A/P:
# vxddladm addjbod vid=SUN pid=T300 policy=ap
- If you have not already done so, upgrade the Storage Foundation or VxVM software to 7.4.1. Device discovery is performed during the upgrade, and the array is claimed as a JBOD of appropriate type.
If you have already upgraded your system to 7.4.1, run the following command to perform device discovery:
# vxdctl enable
- Verify that the array has been added with the policy set to APdisk:
# vxddladm listjbod VID PID Opcode Page Code Page Offset SNO length Policy ============================================================ SUN T300 18 -1 36 12 APdisk
- Check that the correct devices are listed for the array:
# vxdisk list DEVICE TYPE DISK GROUP STATUS APdisk_0 auto:cdsdisk - - online invalid APdisk_1 auto:cdsdisk - - online invalid APdisk_2 auto:cdsdisk - - online invalid ...