09-30-2010
Migrate from MPXIO to Powerpath
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 boot drive and powerpath control any other san drive connected.
Anyone else already try this?
Any tips or anything at all?!
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
LEARN ABOUT SUSE
tgt-admin
TGT-ADMIN(8) TGT Configuration Tool TGT-ADMIN(8)
NAME
tgt-admin - Linux SCSI Target Configuration Tool.
SYNOPSIS
tgt-admin -[OPTION]...
DESCRIPTION
tgt-admin is a utility which allows a persistent configuration of targets and luns.
It uses tgtadm commands to create, delete and show targets.
OPTIONS
-e, --execute
read /etc/tgt/targets.conf and execute tgtadm commands.
if target already exists it will be deleted and a new instance will be created with the new parameters instead.
-d, --delete
delete all the targets
-s, --show
show all the targets
-f, --force
don't exit on tgtadm errors
-p, --pretend
only print tgtadm options
-v, --verbose
increase verbosity (no effect in "pretend" mode)
-c, --conf <conf_file>
specify an alternative configuration file instead of /etc/tgt/target.conf, which is the default.
-h, --help
display a list of available options and exits
CONFIGURATION FILE SYNTAX
The defualt configuration file is: /etc/tgt/target.conf. It defines all the targets and their properties.
The configuration file is in XML format and uses tags. Configuration file contains several target blocks, where each block contains tar-
get's proerties such as storage devices, initator ACL and authorization information. You can include other config files using:
include /etc/tgt/xen/*.conf.
There are 2 types of storage devices:
backing-store - defines a virtual device on the target.
direct-store - defines a direct mapped device with the same properties as the physical device (such as VENDOR_ID , SERIAL_NUM, etc.)
initiator-address - allows connections only from the specify IP address. defaults to ALL if no "initiator-address" is specified
incominguser - define iscsi incoming authentication setting. if no "incominguser" is specified, it is not used.
outgoinguser - define iscsi outgoing authentication setting. if no "outgoinguser" is specified, it is not used.
example for a configuration file:
<target iqn.2007-04.com.example:san.monitoring>
backing-store /dev/san/monitoring
# if no "incominguser" is specified, it is not used
incominguser backup secretpass12
# defaults to ALL if no "initiator-address" is specified
initiator-address 192.168.1.2 </target>
<target iqn.2007-02.com.example:san.xen1>
backing-store /dev/san/xen1-disk1 # LUN1
direct-store /dev/san/xen1-disk2 # LUN2
initiator-address 192.168.1.2 # Allowed IP
initiator-address 192.168.5.6 # Allowed IP
incominguser user1 secretpass12
incominguser user2 secretpass23
outgoinguser userA secretpassA </target>
<target iqn.2007-02.com.example:san.xen2>
backing-store /dev/san/xen2 </target>
<target iqn.2007-06.com.example:san.vmware1>
backing-store /dev/san/vmware1 </target>
FILES
/etc/tgt/target.conf
Configuration file for tgt-admin.
SEE ALSO
tgtadm(8)
REPORTING BUGS
Report bugs to <stgt-devel@lists.berlios.de>
TGT Configuration Tool 2008-07-21 TGT-ADMIN(8)