Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: IBM AIX - SAN Storage DS4300 issue
Operating Systems AIX IBM AIX - SAN Storage DS4300 issue Post 302849517 by filosophizer on Monday 2nd of September 2013 03:53:49 AM
Old 09-02-2013
okay, few things,

first remember, I was unable to see the HBAs when I connected directly to the SAN Storage.
That is: PORT 0 of DUAL PORT HBA connected to Controller A
PORT 1 of DUAL PORT HBA connected to Controller B
in my DS SAN Storage Client Manager I was unable to see the HBA

What I did was, in my AIX machine
Code:
rmdev -Rdl fcs0
rmdev -Rdl fcs1
cfgmgr -v

Refresh in Storage Client Manager and I was able to see the HBAs

Next thing,
I connected after that I connected my single fiber adapter card which is Dual Port HBA as such
HBA Port 0 ---- Controller A
HBA Port 1 ---- Controller B

Did refresh on the SAN Storage Client Software and I was able to see both Ports
Port 0 : 20:00:00:00:c9:61:2e:fa
Port 1 : 20:00:00:00:c9:61:2e:f9

I tried creating only one zone
Cabling as such:
Port 0 of the Dual Port HBA is connected to SAN Switch Port 0
SAN Switch Port 8 is connected to Controller A of the SAN Storage
Now details about the ports
SAN SWITCH PORT 0: Port WWN 20:00:00:05:1e:34:47:37
HBA Port 0 : Device Port WWN [10:00:00:00:c9:61:2e:f9]
Device Node WWN [20:00:00:00:c9:61:2e:f9]



SAN Switch Port #8: Port WWN 20:08:00:05:1e:34:47:37

Devices
Device Port WWN [20:0a:00:a0:b8:12:3b:3e]
Device Node WWN [20:0a:00:a0:b8:12:3b:3d]

Currently effective configuration on the Fabric: test_zc

Zone DB Max size for the fabric - 1048576 bytes

Zone DB to be committed - 0 bytes

You have defined the following zoning database:

Aliases:
test:
Emulex Corporation 20:00:00:00:c9:61:2e:f9 Symbios Logic Inc. 20:0a:00:a0:b8:12:3b:3d

Zones:
test_z:
test

Configurations:
test_zc:
test_z


The Effective Configuration is: test_zc

The Member(s) of the Effective Configuration is (are):

Zone: test_z 20:00:00:00:c9:61:2e:f9
20:0a:00:a0:b8:12:3b:3d

Code:
# cfgmgr
Method error (/usr/lib/methods/cfgefscsi -l fscsi1 ):
        0514-061 Cannot find a child device.

unable to see the disk added from SAN storage

I am wondering if I have done it properly ?
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

AIX 5.2 and DS4300 Storage

Hello, We're setting up a solution for a group of customers with 2 p520 servers and 1 DS4300 unit with 9 disks (at this stage). The meaning is to create two arrays on the DS4300. Both servers will be connected to the DS4300 unit and to both controllers (e.g. Controller 1 connected to server 1... (0 Replies)
Discussion started by: EricBE
0 Replies

2. Filesystems, Disks and Memory

AIX and DS4300 Storage Unit

Hello, We're setting up a solution for a group of customers with 2 p520 servers and 1 DS4300 unit with 9 disks (at this stage). The meaning is to create two arrays on the DS4300. Both servers will be connected to the DS4300 unit and to both controllers (e.g. Controller 1 connected to server 1... (0 Replies)
Discussion started by: EricBE
0 Replies

3. AIX

ibm san cache battery with aix

Hi All, I would like to share this incident that happened the other day. I have a question with this, https://www.unix.com/aix/64921-create-new-vg-san-rename-fs.html And I thought it's related to the above link but the problem was the ibm san 4300 cache battery was dead and I need to click... (2 Replies)
Discussion started by: itik
2 Replies

4. AIX

IBM FastT600 SAN - RAID 5 Storage Manager Client v08.33.G5.03 - Recovery?

To summarize the problem: The "IBM FastT Storage Manager Client v8" shows that our Disk Farm is arranged into 6 logical drives each in a RAID 5 configuration. This software also shows that 5 of the 6 logical drives (from Disk Farm) are in a error state: "Failed Logical Drive - Drive Failure".... (1 Reply)
Discussion started by: aix-olympics
1 Replies

5. AIX

IBM SAN Storage DS4700 - Copy Mirror Flashcopy

Hello, Does anyone know how to copy SAN Storage logical disks from IBM TotalStorage Software. I have a SAN Logical Disk of 200GB mounted on my AIX LPAR_1 via fibre channel fcs0 I would like to make an exact copy of the SAN Logical Disk from IBM totalStorage and mount it on AIX LPAR_2 ... (4 Replies)
Discussion started by: filosophizer
4 Replies

6. AIX

MPIO RDAC IBM SAN STORAGE DS4700 ?

Hello, I have AIX 6.1 with TL 4 and it is connected to IBM SAN STORAGE DS4700 After assigning some disks from SAN to AIX, I can see the disks in my AIX as hdisk2 Available 05-00-02 MPIO Other DS4K Array Disk hdisk3 Available 05-00-02 MPIO Other DS4K Array Disk But it should... (0 Replies)
Discussion started by: filosophizer
0 Replies

7. Solaris

Cannot see the IBM SAN storage

HI all, I had recently change the Server storage from EMC to the IBM SAN. but after the configuration, the IBM success to see the server HBA port and successfully assign a LUN for the server. When i go to the server, and restarted it. i use the "format" command to check, but din see any... (1 Reply)
Discussion started by: SmartAntz
1 Replies

8. AIX

IBM SAN storage -- cache battery

Hello, I have IBM SAN STORAGE DS4100 and one of the cache battery for the controller is dead. Suddenly the performance has been degraded and access to SAN disks ( reading and writing ) became very slow ? My query: Replacing the battery will take 6 days, so in the mean time what are the ways... (1 Reply)
Discussion started by: filosophizer
1 Replies

9. AIX

IBM SAN STORAGE HOT SPARE DISK

Hello, I have DS4000 IBM SAN Storage ( aka FastT Storage ) One of my disks has failed and I had a hot spare disk covering all the arrays. As the disk failed, immediately the hotspare disk took over the failed disk ( see the JPEG in the attachment ) My Question: How can I make the hotspare... (1 Reply)
Discussion started by: filosophizer
1 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)
All times are GMT -4. The time now is 02:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy