10-22-2009
what do you expect to see? there are TWO path to the luns... but if mpxio works correct, you should only see the luns once in "format".
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I'm new to solaris and just installed solaris 10. For some reason I can't resolve stuff. I installed it with the option to use dns. My routing is correct. (I can ping stuff outside my subnet).
I have a resolv.conf which looks like this:
bash-3.00# more resolv.conf
10.32.2.12
10.32.2.11... (5 Replies)
Discussion started by: barabas
5 Replies
2. Solaris
Hi All,
I have one question.
I found out that my system setting for mpxio-disable=yes. Sun recommend to change it to mpxio-disable=no and run stmsboot -e command.
But no one can tell will it affect the system or not and the system is sol-10 and using veritas volume manager and attached... (3 Replies)
Discussion started by: mailbox80
3 Replies
3. Solaris
Hi,
I have a quick question.
How can I see MPXIO statistics (like errors, how many I/O|throuput per path, ....) on Solaris 10? Does maybe a ready dtrace script exist (I do not have the knowledge to write one myself)?
I would be happy if somebody knows some good documentation/links (with... (1 Reply)
Discussion started by: victorinox
1 Replies
4. Filesystems, Disks and Memory
:confused:
Last week I read that VxVM won't work with MPxIO (i don't recall the link) and that it should be unconfigured when installing VxVM. Today I read that VxVM works in "pass-thru" mode with MPxIO and DMP uses the devices presented by MPxIO.
If I create disks with MPxIO and use VxVM to... (1 Reply)
Discussion started by: bluescreen
1 Replies
5. Filesystems, Disks and Memory
Greetings Forumers!!
I was given a T2000 with one, dual port, HBA card. The card had one fiber connection to the SAN and the former admin enabled MPxIO.
Yesterday, I learned that the other port was connected to the same SAN. This system is in another city so I don't have physical access to... (1 Reply)
Discussion started by: bluescreen
1 Replies
6. Solaris
Hi Kudo,
I wanna to know that how can I do mpxio device name to os native name mapping without using stmsboot -L I tried everything still not able to got the solution till I able to get these o/p
here is native disk info as well physical wat is the logical OS name of the disk
... (1 Reply)
Discussion started by: tarunn.dubeyy
1 Replies
7. Solaris
Hello folks,
I have a newly installed Solaris 10 system running on a T6320 blade. I have set up LDM with the intent to move an ldom from another blade to this one. So far, so good.
I had the SAN folks make the LUNs belonging to the ldom visible to my new blade and I can see them, all 4 paths.... (4 Replies)
Discussion started by: Ranck
4 Replies
8. Solaris
Here is the issue:
I am building a database server using Solaris 10x86 U8.
The system is jumpstarted with mpxio enabled and booting from the san.
We need to have powerpath 5.3 installed and would like to have powerpath take control of the the boot san as well or have mpxio control the san... (2 Replies)
Discussion started by: nabru72
2 Replies
9. Solaris
Hi,
I have an Oracle/Sun T3-2 Server with a duel SAS controller Fujitsu DX60 array attached.
I have 2 x SAS HBA's in the T3-2. One HBA cabled to CM0 and one HBA cabled to CM1 of the array.
The array is setup with one RAID GROUP and one VOLUME and one LUN
In Solaris I can see one device... (4 Replies)
Discussion started by: general_lee
4 Replies
10. Solaris
Hi,
I believe this is an OS multipathing issue - Solaris 10
We have x2 Dual port 8GB Qlogic HBA's installed in our SOlaris 10 host.
HBA0 (IOU0) Port WWN's - 09f4 (pci@3,700000/SUNW,qlc@0)
09f5 (pci@3,700000/SUNW,qlc@0,1)
HBA1 (IOU1) Port WWN's... (2 Replies)
Discussion started by: jamba1
2 Replies
LEARN ABOUT SUSE
fc_remote_port_delete
FC_REMOTE_PORT_DELET(9) SCSI mid layer FC_REMOTE_PORT_DELET(9)
NAME
fc_remote_port_delete - notifies the fc transport that a remote port is no longer in existence.
SYNOPSIS
void fc_remote_port_delete(struct fc_rport * rport);
ARGUMENTS
rport
The remote port that no longer exists
DESCRIPTION
The LLDD calls this routine to notify the transport that a remote port is no longer part of the topology. Note: Although a port may no
longer be part of the topology, it may persist in the remote ports displayed by the fc_host. We do this under 2 conditions: 1) If the port
was a scsi target, we delay its deletion by "blocking" it. This allows the port to temporarily disappear, then reappear without disrupting
the SCSI device tree attached to it. During the "blocked" period the port will still exist. 2) If the port was a scsi target and disappears
for longer than we expect, we'll delete the port and the tear down the SCSI device tree attached to it. However, we want to semi-persist
the target id assigned to that port if it eventually does exist. The port structure will remain (although with minimal information) so that
the target id bindings remails.
If the remote port is not an FCP Target, it will be fully torn down and deallocated, including the fc_remote_port class device.
If the remote port is an FCP Target, the port will be placed in a temporary blocked state. From the LLDD's perspective, the rport no longer
exists. From the SCSI midlayer's perspective, the SCSI target exists, but all sdevs on it are blocked from further I/O. The following is
then expected.
If the remote port does not return (signaled by a LLDD call to fc_remote_port_add) within the dev_loss_tmo timeout, then the scsi target is
removed - killing all outstanding i/o and removing the scsi devices attached ot it. The port structure will be marked Not Present and be
partially cleared, leaving only enough information to recognize the remote port relative to the scsi target id binding if it later appears.
The port will remain as long as there is a valid binding (e.g. until the user changes the binding type or unloads the scsi host with the
binding).
If the remote port returns within the dev_loss_tmo value (and matches according to the target id binding type), the port structure will be
reused. If it is no longer a SCSI target, the target will be torn down. If it continues to be a SCSI target, then the target will be
unblocked (allowing i/o to be resumed), and a scan will be activated to ensure that all luns are detected.
Called from normal process context only - cannot be called from interrupt.
NOTES
This routine assumes no locks are held on entry.
AUTHORS
James Bottomley <James.Bottomley@hansenpartnership.com>
Author.
Rob Landley <rob@landley.net>
Author.
COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 FC_REMOTE_PORT_DELET(9)