09-30-2010
Thanks Bluescreen,
That would actually work unfortunately we don't have any internal drives which is causing me a lot of headaches.
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. Solaris
How to change the following values in power path from SP B to SP A ?
Owner: default=SP B, current=SP B
this is excerpt from powermt display dev=all (3 Replies)
Discussion started by: fugitive
3 Replies
4. AIX
Hi Guys,
I have a problem while trying to upgrade to more current EMC powerpath software on AIX 5.3 - respectively uninstalling the existing one.
I tried to deinstall the powerpath software with removed disks - was working perfectly fine on 12 servers - but number 13 is failing with errors:
... (4 Replies)
Discussion started by: zxmaus
4 Replies
5. Red Hat
Hi ,
I have a redhat 5.3 server which has 2 vg.. one is rootvg in local harddisk and another one is applicationvg in SAN.. When I reboot the server , EMC powerpath driver is not starting up automatically. Hence applicationvg is not mounting properly. Therefore I need to unmount it manually and... (4 Replies)
Discussion started by: Makri
4 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,
I have an issue with veritas volume manager version 5.0 in combination with EMC powerpath version 5.2.0 running on Solaris10(Sparc). This server is fiber connected to a EMC Clariion CX3-40 SAN.
This is the situation :
Server is a SUN Enterprise M5000
OS = Solaris10 Sparc
Veritas... (1 Reply)
Discussion started by: chipke2005
1 Replies
8. Linux
Hello guys, I'm going crazy over here with a problem with a LUN created on a EMC CX3.
I did sucessfully managed to create the LUN on the Storage (the LUN is named DBLNX25EC_TST), after doing the following process:
echo "1" > /sys/class/fc_host/host<n>/issue_lip
and
echo "- - -" >... (10 Replies)
Discussion started by: Zarnick
10 Replies
9. Solaris
Hi all
I am running the following hardware:
2 SUN Solaris 10 machines
They are connected to EMC clarion LUNs
We are running a Sun Cluster 3.2 managing both nodes
We are using Solaris Volume Manager to handle the shared storage for the cluster. It is using a number of named disk sets that is... (0 Replies)
Discussion started by: abohmeed
0 Replies
10. Solaris
It seems like I lost one path on my Solaris-11 box. But I want to make sure before going to Storage team, if issue is from OS side or Storage side. Storage team is able to see that only one wwwn is looged in their switch. I am not at server's physical location. What does below output says ? I... (0 Replies)
Discussion started by: solaris_1977
0 Replies
SBP(4) BSD Kernel Interfaces Manual SBP(4)
NAME
sbp -- Serial Bus Protocol 2 (SBP-2) Mass Storage Devices driver
SYNOPSIS
kldload firewire
kldload cam
kldload sbp
or
device sbp
device firewire
device scbus
device da
device cd
device pass
DESCRIPTION
The sbp driver provides support for SBP-2 devices that attach to the FireWire (IEEE 1394) port. It should work with SBP-2 devices which the
CAM layer supports, for example, HDDs, CDROM drives and DVD drives.
Some users familiar with umass(4) might wonder why the device is not detached at the CAM layer when the device is unplugged. It is detached
only if the device has not been plugged again during several bus resets. This is for preventing to detach an active file system even when
the device cannot be probed correctly for some reason after a bus reset or when the device is temporary disconnected because the user changes
the bus topology. If you want to force to detach the device, run ``fwcontrol -r'' several times or set hw.firewire.hold_count=0 by
sysctl(1).
Some (broken) HDDs do not work well with tagged queuing. If you have problems with such drives, try ``camcontrol [device id] tags -N 1'' to
disable tagged queuing.
SEE ALSO
cam(4), firewire(4), camcontrol(8), fwcontrol(8), kldload(8), sysctl(8)
AUTHORS
The sbp driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa.
This manual page was written by Katsushi Kobayashi.
BSD
May 20, 2002 BSD