Sponsored Content
Full Discussion: Solaris multipathing
Operating Systems Solaris Solaris multipathing Post 302414107 by hergp on Monday 19th of April 2010 09:06:06 AM
Old 04-19-2010
On Solaris 10, multipathing is activated on fp controllers by default. You do not need to run stmsboot -e. There was/is a bug (6814757) where /kernel/drv./fp.conf was destroyed when you tried to run stmsboot -e (I hit that bug once).

Do you see any HBAs in the output of fcinfo hba-port?
 

10 More Discussions You Might Find Interesting

1. IP Networking

Quick Poll: Solaris IP Multipathing

I've setup Solaris IP Multipathing under Solaris whenever the hardware to do so was available. I find it amazing though that so few places I've worked at don't use it until I arrive. I wanted to find out if I'm running into all the exceptions, or is it really not being used? ... (3 Replies)
Discussion started by: kduffin
3 Replies

2. Solaris

solaris multipathing

I have solaris 10 sparc. I installed a Qlogic hba card. This card is connected on a brocade switch and the brocade is connected on 2 different controllers on a Hitachi disk bay. I formated 2 luns. On my solaris system, i have 4 disk. How to configure solaris 10 to fix the dual disk view. ... (4 Replies)
Discussion started by: simquest
4 Replies

3. Solaris

Solaris IP Multipathing (IPMP) Help

Hello All, I work for a Health care company at a local trauma hospital. I maintain a Picture Archiving and Communication System (PAC's). Basically, any medical images (X-Ray, CT, MRI, Mammo, etc) are stored digitally on the servers for viewing and dictation from diagnostic stations. I took over... (10 Replies)
Discussion started by: mainegeek
10 Replies

4. Solaris

Solaris IP Multipathing

Hi, I saw your post on the forums about how to setup IP multipathing. I wanted your help on the below situation . I have 2 servers A and B . Now they should be connected to 2 network switches . S1 and S2. Now is it possible to have IP Multipathing on each of the servers as follows ? ... (0 Replies)
Discussion started by: maadhuu
0 Replies

5. Solaris

Disable Inbuilt multipathing software of Solaris 10

Dear UNIX Gurus I need to know how to disable MPXIO feature (Inbuilt multipathing software of Solaris 10) as we are going to implemented iSCSI EMC based SAN. I am bit new to this feature so kindly suggest how to disable it Regards (4 Replies)
Discussion started by: girish.batra
4 Replies

6. Solaris

Multipathing - problem

Hello, I turned on the server multipathing: # uname -a SunOS caiman 5.10 Generic_141444-09 sun4v sparc SUNW,T5140 stmsboot -D fp -e And after a reboot the server, multipathing is not enable: # stmsboot -L stmsboot: MPxIO is not enabled stmsboot: MPxIO disabled # ls /dev/dsk... (4 Replies)
Discussion started by: bieszczaders
4 Replies

7. Red Hat

How to Cleanup Multipathing

I have a server running redhat 5.5 and it has one SAN device presented to it as LUN9. How can I clean up the remaining entries. I cannot afford to interupt the service. Please assist. # multipath -l mpath0 (36000097000019260298953666633436) dm-11 EMC,SYMMETRIX \_ round-robin 0 \_ 2:0:0:9 ... (2 Replies)
Discussion started by: Tirmazi
2 Replies

8. AIX

Multipathing in AIX

Hi, I know the concept of multipathing, but would like to know how to configure multipathing in AIX. or software/driver is by default present in AIX?????? How to find out wheather multipathing is configured in AIX????? Regards, Manu (4 Replies)
Discussion started by: manoj.solaris
4 Replies

9. Solaris

ZeusIOPS multipathing failed Solaris 11

hi, just installed solaris 11.1 (11.1.9.5.1) on a sun7410 ZFSSA (x4440 + j4400), but when I enable multipathing with "stmsboot -e", only the 1TB SATA drives inside the j4400 are configured as multipathed vhci / mpxio devices, but the logzillas / ZeusIOPS drives are skipped. the server is... (0 Replies)
Discussion started by: pressy
0 Replies

10. Red Hat

Verify multipathing

I have a couple of questions regarding multipath. If I do vgdisplay vg01, I see it is using 1 PV: /dev/dm-13 If I type multipath -ll I see dm-9, dm-10, dm-11, dm-12, but do not see dm-13. Is my vg01 multipathed? How can I actually know for sure? Secondly, let's say this time vg01 says... (1 Reply)
Discussion started by: keelba
1 Replies
stmsboot(1M)															      stmsboot(1M)

NAME
stmsboot - administration program for the Solaris I/O multipathing feature SYNOPSIS
/usr/sbin/stmsboot [-d | -e | -u | -L | -l controller_number] The Solaris I/O multipathing feature is a multipathing solution for storage devices that is part of the Solaris operating environment. This feature was formerly known as Sun StorEdge Traffic Manager (STMS) or MPxIO. The stmsboot program is an administrative command to manage enumeration of fibre channel devices under Solaris I/O multipathing. Solaris I/O multipathing-enabled devices are enumerated under scsi_vhci(7D), providing multipathing capabilities. Solaris I/O multipathing-disabled devices are enumerated under the physical controller. In the /dev and /devices trees, Solaris I/O multipathing-enabled devices receive new names that indicate that they are under Solaris I/O multipathing control. This means a device will have a different name from its original name (following installation) when it is under Solaris I/O multipathing control. The stmsboot command automatically updates /etc/vfstab and dump configuration to reflect the device names changes when enabling or disabling Solaris I/O multipathing. A reboot is required for changes to take effect. The following options are supported: -e Enables Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports. Following this enabling, you are prompted to reboot. During the reboot, vfstab and the dump configuration will be updated to reflect the device name changes. -d Disables Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports. Following this disabling, you are prompted to reboot. During the reboot, vfstab and the dump configuration will be updated to reflect the device name changes. -u Updates vfstab and the dump configuration after you have manually modified the configuration to have Solaris I/O multipathing enabled or disabled on specific fp(7D) controller ports. This option prompts you to reboot. During the reboot, vfstab and the dump configura- tion will be updated to reflect the device name changes. -L Display the device name changes from non-Solaris I/O multipathing device names to Solaris I/O multipathing device names. -l controller_number Display the device name changes from non-Solaris I/O multipathing device names to Solaris I/O multipathing device names for the speci- fied controller. Along with its primary function of enabling or disabling Solaris I/O multipathing, the stmsboot command is used to update vfstab and the dump configuration to reflect device name changes. For a system to function properly, you must configure the applications that consume the devices by old names to use the new names. The -L and -l options display the mapping between the old and new device names. These options work after the changes made to the Solaris I/O multipathing configuration have taken effect. For example, you can use these options following the reboot after invoking stmsboot -e. The old device names must exist in order to display the mappings. Example 1: Enabling Solaris I/O Multipathing Following OS Upgrade To enable Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports run: # stmsboot -e Example 2: Disabling Solaris I/O Multipathing To disable Solaris I/O multipathing on all fibre channel (fp(7D)) controller ports, run: # stmsboot -d Example 3: Enabling Solaris I/O Multipathing on Selected Ports You want to enable Solaris I/O multipathing on some fibre channel controller ports and disable the feature on the rest. You edit the fp.conf file (see fp(7D)) to enable or disable Solaris I/O multipathing on specific controller ports. You then run the following command to have vfstab and the dump configuration updated to reflect the new device names: # stmsboot -u See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ |Availability |SUNWcsu, SUNWcslr | +-----------------------------+-----------------------------+ |Interface Stability |Obsolete | +-----------------------------+-----------------------------+ SEE ALSO
dumpadm(1M), ufsdump(1M), dumpdates(4), vfstab(4), fcp(7D), fctl(7D), fp(7D), qlc(7D), scsi_vhci(7D) Consult the Sun StorEdge Disk Tray [or Subsystem] Administrator's Guide for the T3, 3910, 3960, 6120, and 6320 storage subsystems. Sun StorEdge Traffic Manager Installation and Configuration Guide Solaris I/O multipathing is not supported on all devices. After enabling Solaris I/O multipathing, only those devices that Solaris I/O mul- tipathing supports are placed under Solaris I/O multipathing control. Non-supported devices remain as before. For Solaris releases prior to the current release, the -e and -d options remove the mpxio-disable property entries from fp.conf file (see fp(7D)) and add a global mpxio-disable entry to fp.conf. The current release of the Solaris operating system does not support the mpxio-disable property. Solaris I/O multipathing is always enabled. If you want to disable multipathing, you must use the mechanisms provided by the HBA drivers. See fp(7D). Enabling Solaris I/O Multipathing on a Sun StorEdge Disk Array The following applies to Sun StoreEdge T3, 3910, 3960, 6120, and 6320 storage subsystems. To place your Sun StorEdge disk subsystem under Solaris I/O multipathing control, in addition to enabling Solaris I/O multipathing, the mp_support of the subsystem must be set to mpxio mode. The preferred sequence is to change the subsystem's mp_support to mpxio mode, then run stmsboot -e. If Solaris I/O multipathing is already enabled but the subsystem's mp_support is not in mpxio mode, then change the mp_support to mpxio mode and run stmsboot -u. Refer to the Sun StorEdge Administrator's Guide for your subsystem for more details. ufsdump Users The ufsdump command keeps records of the filesystem dumps in /etc/dumpdates (see dumpdates(4)). Among other items, the records contain device names. An effect of the "active" stmsboot options (-e, -d, and -u) is to change the device name of a storage device. The stmsboot command does not modify the dumpdates file. Because of this, the dumpdates records will refer to the old device names, that is, the device names that were in effect before you ran stmsboot. The effect of this device name-dumpdates disagreement is that, following use of stms- boot, ufsdump will be processed as if no previous dump had ever been made, thus dumping the entire filesystem (effectively, a level 0 dump). Procedure to Use stmsboot in Sun Cluster Environment If possible, use stmsboot -e before you start installing Sun Cluster software. After you run stmsboot, you install Sun Cluster software as you normally would. If you install Sun Cluster software before running stmsboot, you must use the following procedure. On each machine in the cluster on which you want to enable the Solaris multipathing feature, enter: # stmsboot -e ...and allow the system to reboot. When the system comes up, enter the following two commands: 1. # /usr/cluster/bin/scdidadm -C 2. # /usr/cluster/bin/scdidadm -r The preceding commands update did mappings with new device names while preserving did instance numbers for disks that are connected to multiple cluster nodes. did instance numbers of the local disks might not be preserved. For this reason, the did disk names for local disks might change. 3. Update /etc/vfstab to reflect any new did disk names for your local disks. 4. Reboot the system. To disable the Solaris multipathing feature, use stmsboot -d (instead of stmsboot -e), then follow the procedure above. To view mappings between the old and new device names, run stmsboot -L. To view did device name mappings, run /usr/cluster/bin/scdidadm -L. 3 Mar 2005 stmsboot(1M)
All times are GMT -4. The time now is 02:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy