Sponsored Content
Operating Systems HP-UX Getting multipath information Post 302974515 by anaigini45 on Tuesday 31st of May 2016 10:00:59 AM
Old 05-31-2016
Yes. If we have external storage devices attached to the server, like 3PAR, etc then for the device to be able to communicate with the server, and to configure the drives for mounting we need multipathing on the OS.
 

10 More Discussions You Might Find Interesting

1. Solaris

Software Multipath

Hello everybody... I have a Server conected to a Disk Array through 2 canals of FiberChannel... I've installed RedHat Advance Server 3 and of course i see two device files that refer the same disk: for example: /dev/sda and /dev/sdb are refered to the same Lun... This is the same case for a new... (2 Replies)
Discussion started by: lenux78
2 Replies

2. UNIX for Dummies Questions & Answers

Linux Multipath Enhancement

Hi.. when i delete a Lun from a Array on a SAN, and again when i create a Lun it shows that the newly created Lun has the ID of the Old deleted Lun which is leading to data corruption. All this is handled by the Multipath software. can anybody help. (0 Replies)
Discussion started by: Praveen13
0 Replies

3. Red Hat

how to combine nics for DM Multipath

I don't undestand how to combine 4 nics in order to use DM Multipath. Do I have to install each nic with its IP address? If yes, do I need a group IP address? This concept is not clear for me. The connection beetwen the server (DELL Poweredge T710) and the SAN through iscsi works well, I used... (1 Reply)
Discussion started by: gnupinux
1 Replies

4. Red Hat

Help with Multipath

Hi All, When I execute multipath -ll command that time display only 3 path (mpath1,mpath2 and mpath5), not display other 2 path (mpath3 and mpath4). I have configure 5 path in /etc/multipath.conf file. What is the reason behind it. Please help me. Please find below the output : ... (5 Replies)
Discussion started by: mnmonu
5 Replies

5. Red Hat

Help with Multipath

Hi All, When I execute "multipath -ll" command that time display only 3 path (orafra2,oradata2 and oradata1), not display other 2 path (orafra1 and data1). I have configure 5 path in "/etc/multipath.conf" file. What is the reason behind it. Please help me. Please find below some output for... (4 Replies)
Discussion started by: mnmonu
4 Replies

6. Ubuntu

Multipath-Tools

Hello, i have a problem with the multipath tools configuration. i can't remove the local disk paths. the multipath.conf archives configuration is: --------------------------------------------------------- $ cat /etc/multipath.conf blacklist{ devnode cciss devnode fd ... (0 Replies)
Discussion started by: FeeII
0 Replies

7. Red Hat

Question about multipath

hi, I've a question about multipath. One server uses this configuration: mpath02 (3600d000ff0d510cae5b8df4d01000000) dm-2 FSC,FibraCAT_SX \_ round-robin 0 \_ 0:0:3:2 sdq 8:64 \_ round-robin 0 \_ 1:0:2:2 sdw 8:160 \_ round-robin 0 \_ 1:0:5:2 sde 65:16 \_ round-robin... (0 Replies)
Discussion started by: davyp74
0 Replies

8. Red Hat

Multipath Query

Hi, I am running RHEL6 on a physical node (HP Proliant). If it normal for the root device to get listed in the "multipath -ll" output? (Listed below as dm-4, HP LOGICAL VOLUME). i.e. asm-data (360a98000424a414b453f443548503644) dm-3 NETAPP,LUN size=768G features='4 queue_if_no_path... (0 Replies)
Discussion started by: Duffs22
0 Replies

9. UNIX for Advanced & Expert Users

Different multipath softwares for RAC

Hi, I have a RAC installation on 2 solaris 11 nodes. (With ASM) Disks' mpath are managed by EMC Powerpath on both nodes. I want to migrate mpath software to Solaris multipath without downtime. My plan is first migrate node1 to solaris mpath, then after some days migrate node2 to sol.mpath. My... (5 Replies)
Discussion started by: vlkkck
5 Replies

10. Red Hat

Multipath configuration not being detected

Hi, In a RHEL 5 box, I have just added new multipath configurations in /etc/multipath.conf : blacklist_exceptions { wwid "360002ac0000000000000008e0001ee00" wwid "360002ac0000000000000008f0001ee00" wwid "360002ac000000000000000900001ee00" wwid... (0 Replies)
Discussion started by: anaigini45
0 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 05:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy