how to translate ssd instances to rdac cXtYdZ names when path_to_ inst is out of date?

From: Largent, Aaron (ALargent@concordefs.com)
Date: Mon Apr 28 2003 - 11:00:47 EDT


I'm working with a black box here, no physical access, and trying to
interpret iostat data and map each ssd device to the proper cXtYdZ
device in a spreadsheet.

this system has 20 LUNs from 5 A3500 modules, each dual-pathed.
I have a very thorough compilation of all devices and paths from the
information I have collected from prtconf, the most recent reboot,
/kernel/drv/rdriver.conf, and vxprint output. so my understanding of
the physical connections and paths right now is very good.

the problem is that since path_to_inst is not up to date, iostat -nx
still wont report anything but ssd instances. and since vxprint and others
refer to only the cXtYdZ name, I am stuck trying to decipher which
ssd data goes to which filesystem.

rdac is installed, so Veritas is using the pseudo devices in /dev/dsk
and not the ones reported on boot.

What piece am I missing here? I get the feeling I am overlooking
something very simple. is there an rm6 related command to report
which rdac pseudo devices are currently mapped to which ssd instances?
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:17 EDT