InfoScale™ 9.0 Storage Foundation and High Availability Configuration and Upgrade Guide - Solaris
- Section I. Introduction to SFHA
- Section II. Configuration of SFHA
- Preparing to configure
- Preparing to configure SFHA clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring the CP server manually
- Configuring CP server using response files
- Configuring SFHA
- Configuring Storage Foundation High Availability using the installer
- Configuring a secure cluster node by node
- Verifying and updating licenses on the system
- Configuring Storage Foundation High Availability using the installer
- Configuring SFHA clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Manually configuring SFHA clusters for data integrity
- Setting up disk-based I/O fencing manually
- Setting up server-based I/O fencing manually
- Configuring server-based fencing on the SFHA cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Performing an automated SFHA configuration using response files
- Performing an automated I/O fencing configuration using response files
- Section III. Upgrade of SFHA
- Planning to upgrade SFHA
- Preparing to upgrade SFHA
- Upgrading Storage Foundation and High Availability
- Performing a rolling upgrade of SFHA
- Performing a phased upgrade of SFHA
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated SFHA upgrade using response files
- Upgrading SFHA using Boot Environment upgrade
- Performing post-upgrade tasks
- Post-upgrade tasks when VCS agents for VVR are configured
- Upgrading the Array Support Library
- About enabling LDAP authentication for clusters that run in secure mode
- Planning to upgrade SFHA
- Section IV. Post-installation tasks
- Section V. Adding and removing nodes
- Adding a node to SFHA clusters
- Adding the node to a cluster manually
- Adding a node using response files
- Configuring server-based fencing on the new node
- Removing a node from SFHA clusters
- Removing a node from a SFHA cluster
- Removing a node from a SFHA cluster
- Adding a node to SFHA clusters
- Section VI. Configuration and upgrade reference
- Appendix A. Installation scripts
- Appendix B. SFHA services and ports
- Appendix C. Configuration files
- Appendix D. Configuring the secure shell or the remote shell for communications
- Appendix E. Sample SFHA cluster setup diagrams for CP server-based I/O fencing
- Appendix F. Reconciling major/minor numbers for NFS shared disks
- Appendix G. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Using the UDP layer of IPv6 for LLT
- Manually configuring LLT over UDP using IPv6
Converting a defined disk to auto:simple
In VxVM 4.0, and particularly in prior releases, EMCpower disks could be defined by a persistent disk access record (darec), and identified as simple disks. If an EMCpower disk is defined with a persistent darec, it must be manually converted to auto:simple format before upgrading to VxVM 9.0.
If the defined disk is defined on a slice other than s2, you must copy the partition entry for that slice to that for s0 and change the tag. If the tag of the original slice is changed, the status of the disk is seen as online:aliased after the upgrade.
The following example is used to illustrate the procedure. The ls command shows the mapping of the EMC disks to persistent disk access records:
# ls -l /dev/vx/dmp/emcdisk1 lrwxrwxrwx 1 root other 36 Sep 24 17:59 /dev/vx/dmp/emcdisk1-> /dev/dsk/c6t0d11s5 # ls -l /dev/vx/rdmp/emcdisk1 lrwxrwxrwx 1 root other 40Sep 24 17:59 /dev/vx/rdmp/emcdisk1-> /dev/dsk/c6t0d11s5
Here the fifth partition of c6t0d11s5 is defined as the persistent disk access record emcdisk1.
The vxdisk list command can be used to display the EMCpower disks that are known to VxVM:
# vxdisk list DEVICE TYPE DISK GROUP STATUS c6t0d12s2 auto:sliced - - online emcdisk1 simple fdisk fdg online ...
The vxprint command is used to display information about the disk group, fdg:
# vxprint Disk group: fdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg fdg fdg - - - - - - dm fdisk emcdisk1 - 17673456 - - - - ...
To convert a disk with a persistent disk access record to auto:simple format
- Stop all the volumes in the disk group, and then deport it:
# vxvol -g fdg stopall # vxdg deport fdg
- Use the vxdisk rm command to remove the persistent record definitions:
# vxdisk rm emcdisk1
If you now run the vxdisk list command, the EMCpower disk is no longer displayed:
# vxdisk list DEVICE TYPE DISK GROUP STATUS c6t0d12s2 auto:sliced - - online ...
- Use the vxprtvtoc command to retrieve the partition table entry for the device:
# /etc/vx/bin/vxprtvtoc -f /tmp/hdisk /dev/rdsk/c6t0d11s2
- Use the vxedvtoc command to modify the partition tag and update the VTOC:
# /etc/vx/bin/vxedvtoc -f /tmp/hdisk /dev/rdsk/c6t0d11s2 # THE ORIGINAL PARTITIONING IS AS FOLLOWS: # SLICE TAG FLAGS START SIZE 4 0x0 0x200 0 0 5 0x0 0x200 3591000 2100375 6 0x0 0x200 0 0 # THE NEW PARTITIONING WILL BE AS FOLLOWS: # SLICE TAG FLAGS START SIZE 4 0x0 0x200 0 0 5 0xf 0x200 3591000 2100375 6 0x0 0x200 0 0 DO YOU WANT TO WRITE THIS TO THE DISK ? [Y/N] :Y WRITING THE NEW VTOC TO THE DISK #
- Upgrade to VxVM 9.0 using the appropriate upgrade procedure.
- After upgrading VxVM, use the vxdisk list command to validate the conversion to auto:simple format:
# vxdisk list DEVICE TYPE DISK GROUP STATUS c6t0d12s2 auto:sliced - - online emcpower10s2 auto:simple - - online:aliased ...
To display the physical device that is associated with the metadevice, emcpower10s2, enter the following command:
# vxdmpadm getsubpaths dmpnodename=emcpower10s2
- Import the disk group and start the volumes:
# vxdg import fdg # vxvol -g fdg startall
You can use the vxdisk list command to confirm that the disk status is displayed as online:simple:
# vxdisk list DEVICE TYPE DISK GROUP STATUS c6t0d12s2 auto:sliced - - online emcpower10s2 auto:simple fdisk fdg online:aliased
To allow DMP to receive correct enquiry data, the common Serial Number (C-bit) Symmetrix Director parameter must be set to enabled.