Error Message

SCSI error occurred on Path c9t21420002AC0203A5d214s2(243/650): opcode=0x5f reported illegal request (status=0x2, key=0x5, asc=0x26, ascq=0x0) invalid field in parameter list

Known limitation.

3Par arrays are A/A by default and will be claimed by our asl as A/A. However the array might be only A/A in particular configurations- for example as a single controller or two controller configuration where both storage controllers are configured as A/A.

If the array is configured as part of a Remote Copy, Peer Persistence or Peer Motion setup, it will act in ALUA mode.

When Remote Copy, Peer Persistence or Peer Motion is configured and one storage controller is configured as Active/Optimized (AO) and the other as Standby (in these configurations 3PAR secondary paths don’t support Active/Non-Optimized (ANO) state ), the standby paths will not be read-write and the SCSI PR registration cannot be done on those paths and so the above error message will be generated.

Due to these limitations with the standby paths not accepting i/o and impacting SCSI PR registrations, this configuration is unsupported.

For example:
If the 3Par array has been setup to have eight active paths across two controllers, dmp will report eight active paths for the disks and so it would be expected that there would be eight keys registered on the disks. The fact that it is  configured as part of a RemoteCopy configuration with another cluster/array, the eight paths are really a mix of active/optimized and standby and so only two fencing keys were seen on the disks. One key for a path on each controller. This is due to the SCSI PR registration not being successful down all the paths.

It should also be noted that the above messages will also be seen when activities such as device discovery, dmp path state check and diskgroup imports are done and this could lead to lots of events being triggered in OS logs such as Solaris FMA logs.