Search <book_title>...

InfoScale™ 9.0 Storage Foundation and High Availability Configuration and Upgrade Guide - Solaris

Last Published: 2025-04-18

Product(s): InfoScale & Storage Foundation (9.0)

Platform: 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 9.0. 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 9.0, 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
  ...