08-16-2013
Actually that you see the same disk from different angles is not a bug, it is a feature. If one of these connections (and hence the related hdisk device) would be disconnected the whole system would still work.
This is what "multipath" drivers are all about: to create single devices back from the various device entries, which represent different views of the same hardware.
Not sure what your question is, but i hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. AIX
Hi All,
I have mirrored SAN volume on my B80 rootvg. Can I just remove the mirror and "Remove a P V from a V G" and it will be a diskless AIX?
Is that going to boot on SAN rootvg volume?
Thanks in advance,
itik (3 Replies)
Discussion started by: itik
3 Replies
2. AIX
Hello everyone
I got several aix boxes with aix 5.3
I got a ibm san ds4500
My question is
How can I do a match between my disks on aix and the san?
I try to do a match with the LUN but for example. In my san I got several 1 LUN and on one of my aix box I got this
If I type lscfg... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies
3. AIX
We are considering a DR strategy of booting AIX 5.3 and 5.3 logical partitions from EMC Symmetrix SAN disks, so that we can replicate via SRDF to a recovery site. Has anyone tried configuring AIX 5.x systems to boot from SAN disk? If so, can you provide any information on the pros and cons of... (6 Replies)
Discussion started by: jjgarrot
6 Replies
4. Solaris
hi all,
have a solaris 9 OS and a SAN disk which used to work fine is not getting picked up by my machine. can anyone point out things to check in order to troubleshoot this ??
thanks in advance. (3 Replies)
Discussion started by: cesarNZ
3 Replies
5. Filesystems, Disks and Memory
Scenario:
I've got 2 M5000's connected to a 9985 SAN storage array. I have configured the SAN disks with stmsboot, format and newfs. I can access the same SAN space from both systems. I have created files from both systems on the SAN space.
Question:
Why can't I see the file created... (3 Replies)
Discussion started by: bluescreen
3 Replies
6. UNIX for Dummies Questions & Answers
Hi all,
My main function is as a DBA. Another person manages the server and the SAN.
I just want to know if I should be worried about high disk I/O or is it irrelevant as the I/O "load balancing" will be "taken care" of by the SAN?
For example, I have hdisk1-5 and I can see that there are... (2 Replies)
Discussion started by: newbie_01
2 Replies
7. Solaris
Hi,
I have a production solaris 10 SPARC system (portal). Yesterday legato/Networker gave an I/O Error on one of the files on its SAN mounted disk.
I went to that particular file on the system, did an ls and it showed the file. However, ls -l did not work and it said IO error.
... (6 Replies)
Discussion started by: Mack1982
6 Replies
8. AIX
Hello All,
Our servers having emc clarion for the data disks. Is that possible to see those san disks raid level from AIX ?
Am having AIX 6.1 and EMC clarion 5.5.
Regards,
Gowtham.G (3 Replies)
Discussion started by: gowthamakanthan
3 Replies
9. AIX
Hi guys, :)
I'm a studient in IT field (AIX)
I'm trying to map a LUN from a SAN (DS3400) to an AIX server (5300-04-00)
I know there is no MPIO on this version of AIX, and i see double my LUN from the SAN
root@localhost # lscfg | grep hdisk
+ hdisk7 ... (13 Replies)
Discussion started by: Tharsan
13 Replies
10. UNIX for Beginners Questions & Answers
I am in the market looking to purchase a new E950 server and I am trying to decide between using local SSD drives or SSD based SAN. The application that will be running on this server is read-intensive so I am looking for the most optimal configuration to support this application. There are no... (2 Replies)
Discussion started by: ikx
2 Replies
pm(9P) Kernel Properties for Drivers pm(9P)
NAME
pm - Power Management properties
DESCRIPTION
The pm-hardware-state property can be used to influence the behavior of the Power Management framework. Its syntax and interpretation is
described below.
Note that this property is only interpreted by the system immediately after the device has successfully attached. Changes in the property
made by the driver after the driver has attached will not be recognized.
pm-hardware-state is a string-valued property. The existence of the pm-hardware-state property indicates that a device needs special han-
dling by the Power Management framework with regard to its hardware state.
If the value of this property is needs-suspend-resume, the device has a hardware state that cannot be deduced by the framework. The frame-
work definition of a device with hardware state is one with a reg property. Some drivers, such as SCSI disk and tape drivers, have no reg
property but manage devices with "remote" hardware. Such a device must have a pm-hardware-state property with a value of needs-suspend-
resume for the system to identify it as needing a call to its detach(9E) entry point with command DDI_SUSPEND when system is suspended, and
a call to attach(9E) with command DDI_RESUME when system is resumed. For devices using original Power Management interfaces (which are now
obsolete) detach(9E) is also called with DDI_PM_SUSPEND before power is removed from the device, and attach(9E) is called with
DDI_PM_RESUME after power is restored.
A value of no-suspend-resume indicates that, in spite of the existence of a reg property, a device has no hardware state that needs saving
and restoring. A device exporting this property will not have its detach() entry point called with command DDI_SUSPEND when system is sus-
pended, nor will its attach() entry point be called with command DDI_RESUME when system is resumed. For devices using the original (and now
obsolete) Power Management interfaces, detach(9E) will not be called with DDI_PM_SUSPEND command before power is removed from the device,
nor attach(9E) will be called with DDI_PM_RESUME command after power is restored to the device.
A value of parental-suspend-resume indicates that the device does not implement the detach(9E) DDI_SUSPEND semantics, nor the attach()
DDI_RESUME semantics, but that a call should be made up the device tree by the framework to effect the saving and/or restoring of hardware
state for this device. For devices using original Power Management interfaces (which are now obsolete), it also indicates that the device
does not implement the detach(9E) DDI_PM_SUSPEND semantics, nor the attach(9E) DDI_PM_RESUME semantics, but that a call should be made up
the device tree by the framework to effect the saving and/or restoring the hardware state for this device.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+--------------------------+--------------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+--------------------------+--------------------------------+
|Interface stability |Evolving |
+--------------------------+--------------------------------+
SEE ALSO
power.conf(4), pm(7D), attach(9E), detach(9E), pm_busy_component(9F), pm_idle_component(9F), pm-components(9P)
Writing Device Drivers
SunOS 5.10 20 Jan 2004 pm(9P)