My Oracle Support Banner

Solaris Cluster How to Verify and Troubleshoot Physical Device Paths, when "DID" Device Path is in Status "Fail" (Doc ID 1019917.1)

Last updated on MAY 11, 2018

Applies to:

Solaris Cluster - Version 3.0 to OSC 4.3 [Release 3.0 to 4.3]
Solaris Cluster Geographic Edition - Version 3.0x to OSC 4.3 [Release 3.0 to 4.3]
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86 (32-bit)
Oracle Solaris on x86-64 (64-bit)

Goal

This document explains how to determine if physical device paths to the storage are valid on Solaris Cluster node/system/server. It also troubleshoots the Solaris Cluster DID device layer when "cldev status" or "scdpm -p all" shows physical device paths to the storage path in Status "Fail"

This document shows example using Solaris Cluster 3.2 on new command line. Refer to <Document 1541888.1> for corresponding Solaris Cluster 3.0/3.1 command

 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 1) Introduction to the Solaris Cluster DID pseudo driver
 2) Checking DID device mapping
 3) Checking DID device state
 4) Verifing DID and physical device access state
 a) Checking the state for a particular device
 b) Checking the access of DID and physical device
  5) Reparing DID device
 a) Common DID repair steps following physical access issues
 6) Clearing mismatched "DevID" Kernel State of "DID" Device versus Cluster CCR State
 a) Verification of the stored DevID's
 b) DevID repair steps for mismatched DevID Kernel State without rebooting
 Community Discussions
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.