05-07-2014
Thank you very much.
Yes I can get downtime for cluster
---------- Post updated 05-07-14 at 08:31 AM ---------- Previous update was 05-06-14 at 02:01 PM ----------
Hi,
Thank you ver much.
Yes i can get a downtime for the cluster
10 More Discussions You Might Find Interesting
1. HP-UX
Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch.
Any... (0 Replies)
Discussion started by: Hils
0 Replies
2. Solaris
Hi everyone,
I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN?
At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies
3. AIX
Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage.
DS5020 mentions Enhanced Remote Mirror to multi-LUN applications
I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ? (1 Reply)
Discussion started by: filosophizer
1 Replies
4. HP-UX
Hello gurus,
I am a SAN Admin - not very familiar with the HPUX administration - so need help with the steps in regards to the migration I need to do at my client place.
Environment: Migrating from CX4 to VMAX - using OR/Hot Pull.
Here are the steps I have put together - HPUX gurus please... (5 Replies)
Discussion started by: jps460
5 Replies
5. Solaris
I am going to do a SAN Array migration and need the sequence of steps required on the Solaris cluster before moving the old array luns to new array luns.
Here are the steps and I need info on the bold points:( I might even be wrong on the sequence of steps please correct me if I am wrong)
1.... (0 Replies)
Discussion started by: sunshinedeepu
0 Replies
6. HP-UX
Hi,
I am very new to HP-UX, and we're going to be doing a SAN migration.
We're going to take down the machine, and zone it to the new SAN.
My question is, will the device names change and will that interfere with the LVM?
If the new disks come in with different device names, how would I... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
7. Red Hat
I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew... (4 Replies)
Discussion started by: rbatte1
4 Replies
8. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
9. Solaris
I am working on VM host and collecting data to identify the type of storage attached to the server which will be migrated to VNX.
it has one ldom created on it
luxadm probe output ---
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node... (7 Replies)
Discussion started by: kpatel786
7 Replies
10. Filesystems, Disks and Memory
hi! i got a rhel 6.3 host that already have an xfs filesystem mounted from a SAN (let's call it SAN-1) whose size is 9TB.
i will be receiving another SAN (let's call it SAN-2) storage of 15TB size. this new addition is physically on another SAN storage. SAN-1 is on a Pillar storage while the new... (6 Replies)
Discussion started by: rino19ny
6 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)