AIX and TSM w/Sun StorageTek 6140

M

mikeatkc

ADSM.ORG Senior Member
Joined
Apr 24, 2007
Messages
450
Reaction score
5
Points
0
Location
United States
Anyone here using AIX 5.3 with Sun StorageTek 6140 for SAN? If so, are you using RDAC, if not are you using IBM driver with AIX_FO? All feedback is welcome on how you setup your TSM w/AIX and Sun SAN and the difficulties, etc.

AIX 5.3 / TSM 5.5.2.0 / Sun StorageTek 6140


Thanks.
 
I'm making some progress w/the SAN...however, attempts to create a new volume group returns the below. I removed all hdisk and re-ran cfgmgr but it still doesn't help. I'm using AIX_FO as host type on the SAN. Anything I can do in AIX to prevent duplicate PVIDs? (change PVIDs manually?)

Thank you for your input/s.

0516-1748 /usr/sbin/mkvg: Physical volumes hdisk2 and hdisk62 have identical PVIDs (0007da52c89e97c1).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk3 and hdisk15 have identical PVIDs (0007da52c89eb5a7).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk4 and hdisk16 have identical PVIDs (0007da52c89ed285).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk5 and hdisk17 have identical PVIDs (0007da52c89ef036).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk6 and hdisk18 have identical PVIDs (0007da52c89f0e85).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk8 and hdisk20 have identical PVIDs (0007da52b41d9242).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk9 and hdisk21 have identical PVIDs (0007da52b41d9347).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk10 and hdisk22 have identical PVIDs (0007da52b41d9429).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk11 and hdisk23 have identical PVIDs (0007da52b41d950d).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk12 and hdisk24 have identical PVIDs (0007da52b41d95e1).
 
When creating/expanding a volume group in AIX with multi-pathed devices, only use one of the devices or use a multi-path device driver. With AIX 5.3 and above, you can use the native MPIO but it lacks in some of the abilities of drivers like IBM's SDD and EMC's PowerPath.

I would create the VG with a single device, run cfgmgr to update the PVID on the other path to the same device and then add new disks one at a time with a cfgmgr between each one so that you don't try to add a device that is already a member of the VG but hasn't had it's PVID updated.

-Aaron
 
I hooked one FC onto the SAN (leaving three FCs unplugged) and AIX cfgmgr discovered the disks, etc. However, creating a new vg gave the same error. I removed the hdisks again and rebooted thinking the system might be cleaner and cfgmgr during boot discovers it differently but no luck. Why the heck does these hdisks get the same PVID? I'm on AIX 5.3 w/SP4 so the patch should be update.

I have 10 LUNs and 4 FCs, going over 2 fiber switches (2 FCs per switch) but currently hooking 1 FC to test and add disks at a later time.


0516-1748 /usr/sbin/mkvg: Physical volumes hdisk2 and hdisk14 have identical PVIDs (0007da52c89e97c1).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk3 and hdisk15 have identical PVIDs (0007da52c89eb5a7).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk4 and hdisk16 have identical PVIDs (0007da52c89ed285).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk5 and hdisk17 have identical PVIDs (0007da52c89ef036).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk6 and hdisk18 have identical PVIDs (0007da52c89f0e85).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk8 and hdisk20 have identical PVIDs (0007da52b41d9242).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk9 and hdisk21 have identical PVIDs (0007da52b41d9347).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk10 and hdisk22 have identical PVIDs (0007da52b41d9429).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk11 and hdisk23 have identical PVIDs (0007da52b41d950d).
0516-1748 /usr/sbin/mkvg: Physical volumes hdisk12 and hdisk24 have identical PVIDs (0007da52b41d95e1).
0516-1182 /usr/sbin/mkvg Open Failure on hdisk7.
0516-1182 /usr/sbin/mkvg Open Failure on hdisk19.
0516-862 /usr/sbin/mkvg: Unable to create volume group.
 
Whats the output from:

lsdev -Cc disk
lscfg -vl {hdisk}
 
Looks normal? w/the exception PVID is the same w/some of the hdisks (some hdisk displays below missing, 10000 characters max.)

/# lsdev -Cc disk
hdisk0 Available 00-08-00 SAS Disk Drive
hdisk1 Available 00-08-00 SAS Disk Drive
hdisk2 Available 02-08-02 Other FC SCSI Disk Drive
hdisk3 Available 02-08-02 Other FC SCSI Disk Drive
hdisk4 Available 02-08-02 Other FC SCSI Disk Drive
hdisk5 Available 02-08-02 Other FC SCSI Disk Drive
hdisk6 Available 02-08-02 Other FC SCSI Disk Drive
hdisk7 Available 02-08-02 Other FC SCSI Disk Drive
hdisk8 Available 02-08-02 Other FC SCSI Disk Drive
hdisk9 Available 02-08-02 Other FC SCSI Disk Drive
hdisk10 Available 02-08-02 Other FC SCSI Disk Drive
hdisk11 Available 02-08-02 Other FC SCSI Disk Drive
hdisk12 Available 02-08-02 Other FC SCSI Disk Drive
hdisk13 Available 02-08-02 Other FC SCSI Disk Drive
hdisk14 Available 02-08-02 Other FC SCSI Disk Drive
hdisk15 Available 02-08-02 Other FC SCSI Disk Drive
hdisk16 Available 02-08-02 Other FC SCSI Disk Drive
hdisk17 Available 02-08-02 Other FC SCSI Disk Drive
hdisk18 Available 02-08-02 Other FC SCSI Disk Drive
hdisk19 Available 02-08-02 Other FC SCSI Disk Drive
hdisk20 Available 02-08-02 Other FC SCSI Disk Drive
hdisk21 Available 02-08-02 Other FC SCSI Disk Drive
hdisk22 Available 02-08-02 Other FC SCSI Disk Drive
hdisk23 Available 02-08-02 Other FC SCSI Disk Drive
hdisk24 Available 02-08-02 Other FC SCSI Disk Drive
hdisk25 Available 02-08-02 Other FC SCSI Disk Drive

hdisk2 U789C.001.DQDA160-P1-C4-T1-W202700A0B82681F2-L5000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245007032
Device Specific.(Z1)........

hdisk3 U789C.001.DQDA160-P1-C4-T1-W202700A0B82681F2-L6000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245004032
Device Specific.(Z1)........

hdisk4 U789C.001.DQDA160-P1-C4-T1-W202700A0B82681F2-L7000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245007032
Device Specific.(Z1)........

hdisk5 U789C.001.DQDA160-P1-C4-T1-W202700A0B82681F2-L8000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245004032
Device Specific.(Z1)........

hdisk6 U789C.001.DQDA160-P1-C4-T1-W202700A0B82681F2-L9000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245004032
Device Specific.(Z1)........

hdisk7 U789C.001.DQDA160-P1-C4-T1-W202700A0B82681F2-L1F000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......Universal Xport
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245007032
Device Specific.(Z1)........

hdisk8 U789C.001.DQDA160-P1-C4-T1-W202700A0B811C006-L0 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245004032
Device Specific.(Z1)........

hdisk9 U789C.001.DQDA160-P1-C4-T1-W202700A0B811C006-L1000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245007032
Device Specific.(Z1)........

hdisk10 U789C.001.DQDA160-P1-C4-T1-W202700A0B811C006-L2000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245004032
Device Specific.(Z1)........

hdisk11 U789C.001.DQDA160-P1-C4-T1-W202700A0B811C006-L3000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245007032
Device Specific.(Z1)........

hdisk12 U789C.001.DQDA160-P1-C4-T1-W202700A0B811C006-L4000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245004032
Device Specific.(Z1)........

hdisk13 U789C.001.DQDA160-P1-C4-T1-W202700A0B811C006-L1F000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......Universal Xport
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245007032
Device Specific.(Z1)........

hdisk14 U789C.001.DQDA160-P1-C4-T1-W202600A0B82681F2-L5000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245004032
Device Specific.(Z1)........

hdisk15 U789C.001.DQDA160-P1-C4-T1-W202600A0B82681F2-L6000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245007032
Device Specific.(Z1)........

hdisk16 U789C.001.DQDA160-P1-C4-T1-W202600A0B82681F2-L7000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245004032
Device Specific.(Z1)........

hdisk17 U789C.001.DQDA160-P1-C4-T1-W202600A0B82681F2-L8000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245007032
Device Specific.(Z1)........

hdisk18 U789C.001.DQDA160-P1-C4-T1-W202600A0B82681F2-L9000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245007032
Device Specific.(Z1)........

hdisk19 U789C.001.DQDA160-P1-C4-T1-W202600A0B82681F2-L1F000000000000 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......Universal Xport
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245007032
Device Specific.(Z1)........

hdisk20 U789C.001.DQDA160-P1-C4-T1-W202600A0B811C006-L0 Other FC SCSI Disk Drive

Manufacturer................SUN
Machine Type and Model......CSM200_R
ROS Level and ID............30363139
Serial Number...............
Device Specific.(Z0)........0000053245007032
Device Specific.(Z1)........
 
A quick search on SUN's site shows this. From that link, I came to this which you should be able to get the AIX driver for the 6140. Or just follow this link to get the actual download.

It looks to me like there is a pathing/zoning problem where one LUN on the 6140 is pathed/zoned to all the HBAs such that even with only 1 HBA on the host active, it sees multiple paths to the LUN and gets very confused. Installing the driver from Veritas should help with the multiple paths problem.

-Aaron
 
I got the same result/s and the Veritas DMP is outdated (I think). I'm using the Sun RDAC (which is supposed to be newer driver) which causes my system to hang. I have removed the Sun RDAC and attempts to use AIX MPIO. However, cfgmgr does not recognize my FCs as MPIO devices. I've also gone into smitty and attempted to add the FCs as MPIO devices but no luck.

I believed the reason for so many PVIDs overlapped was that the FCs were not recognized as MP/MPIO devices and no "meta devices" were created to handle the hdisks as MP. Hence, the LUNs appeared but really not ready for MP usage.

Anyhow, I think if I can get AIX to recognize the FCs as MPIO devices I can get the hdisks to function properly.

!!! LP11002 Fcode, Copyright (c) 2000-2006 Emulex !!! Version 1.50x1
!!! LP11002 Fcode, Copyright (c) 2000-2006 Emulex !!! Version 1.50x1
!!! LPe11002 Fcode, Copyright (c) 2000-2006 Emulex !!! Version 1.50x1
!!! LPe11002 Fcode, Copyright (c) 2000-2006 Emulex !!! Version 1.50x1
!!! LPe11002 Fcode, Copyright (c) 2000-2006 Emulex !!! Version 1.50x1
!!! LPe11002 Fcode, Copyright (c) 2000-2006 Emulex !!! Version 1.50x1
!!! LPe11002 Fcode, Copyright (c) 2000-2006 Emulex !!! Version 1.50x1
!!! LPe11002 Fcode, Copyright (c) 2000-2006 Emulex !!! Version 1.50x1
 
Are you using IBM FC adapters? I've never had a problem with having the FC adapters be recognized as MPIO devices. What level of 5.3 are you running? Do you have any broken filesets?
 
Four Emulex adapters, however, it is identified as IBM 5759 (1) and IBM 5754 (3) under lscfg -vl command. The hdisk0/hdisk1 of SAS controller, all of which identify as MPIO devices. And yes I thought the FCs would have been identify as MPIO by AIX drivers (which I added all for TSM, etc.).

# oslevel -r
5300-08

AIX 5.3 w/SP4

How do I determine broken filesets? (lppchk -v?)

lppchk -v returns nothing.
 
Last edited:
4 adapters? In post #8 at the bottom, you listed 8 boot inits. Are they dual port adapters?

If they're IBM FeatureCode adapters, then they should just work as MPIO adapters. No special configurations needed.

lppchk -vm3 but I doubt that'd show up any errors if you didn't get any with just the -v option.

I'd call up IBM and open a PMR at this point. The disks should work as MPIO devices if AIX sees them as multiple paths to the same LUN.
 
4 adapters dual-port. I'll be contacting IBM early tomorrow to see what they have to say.
 
My solution is to use Sun's RDAC driver for AIX 5.3 so that AIX can communicate with Sun's StorageTek 6140 properly. However, the server does not have standby failover for the HBA (ie. if one HBA failed, the server needs to be reboot in order for the other HBA to manage the LUNs). Additionally, no proper "balancing" for the LUNs. I have four HBAs but only one HBA can manage the LUNs the other three is for "failover" as described above (this is just wrong). Sun's RDAC does not provide adequate MPIO to AIX.

Furthermore, I have two SAN arrays (one with fiber disks, one with SATA disks) but I can only use one or the other and not both. With Sun's RDAC driver, using both arrays caused the system not to recognize all the LUNs. I figured spreading my storage layout between the two arrays to increase performance but it does not work out that way.

I thought about plugging two external 1TB USB hard-drives onto the server for storage and calling it the day :) Anyhow, after fiddling with the storage for a long duration, I just go with what's available. Now, if IBM decided to purchase Sun, maybe I'll get a decent RDAC driver for AIX? (not holding my breath)
 
You must log in or register to reply here.

Data Privacy Impact Assessment

Compliance Assurance in Every Byte: Discover the Impact of Our DPIA Services.

Sponsor ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

Navigation Menu

Forums
   IBM TSM
   EMC Backup and Recovery
   Symantec NetBackup  
   SAN  
   NAS
   Platforms / OS
Mailing List Archives
   ADSM-L
User Groups

NordVPN 3 Months FREE

Help Support ADSM.ORG and Get NordVPN with 64% Off and 3 Months FREE.

NordVPN with 64% off + 3 months FREE

Forum statistics

Threads
31,974
Messages
135,448
Members
21,953
Latest member
jrogers
Back
Top