veritas storage foundation + netapp filer + lun iscsi

Updated: 22 May 2010 | 5 comments

thesime

+1 1 Vote

This issue has been solved. See solution.

Hi to everybody,

I have a problem on my IBM AIX system :

root@ronobe: / =>oslevel -s
5300-08-04-0844
root@ronobe: / =>lslpp -l |grep -i VRTSvxvm
VRTSvxvm 5.0.1.0 APPLIED Veritas Volume Manager by
VRTSvxvm 5.0.1.0 APPLIED Veritas Volume Manager by

I've mapped one lun of my netapp filer to do some tests...the systems see it :

root@ronobe: / =>lscfg -vps -l hdisk56
hdisk56
Other iSCSI Disk Drive

        Manufacturer................NETAPP
        Machine Type and Model......LUN
        ROS Level and ID............302E3220
        Serial Number...............W-COk4OR
        Device Specific.(Z0)........0000043270001002
        Device Specific.(Z1)........ToME
        Device Specific.(Z2)........S316
        Device Specific.(Z3)........0
        Device Specific.(Z4)........
        Device Specific.(Z5)........ON

But veritas do not see it if I do simple a vxdisk list.Infact I see only the other storages:

DS6410_27    auto:cdsdisk    thorax2909   thoray29     online udid_mismatch
DS6410_28    auto:cdsdisk    thoray2907   thoray29     online udid_mismatch
DS6410_29    auto:cdsdisk    thorax2906   thoray29     online udid_mismatch
DS6410_30    auto:cdsdisk    thorax2908   thoray29     online udid_mismatch
DS6410_31    auto:cdsdisk    thoray2906   thoray29     online udid_mismatch
DS6410_32    auto:cdsdisk    thoray2905   thoray29     online udid_mismatch
DS6410_33    auto:cdsdisk    thoray2903   thoray29     online udid_mismatch
DS6410_34    auto:cdsdisk    thoray2902   thoray29     online udid_mismatch
DS6410_35    auto:cdsdisk    thoray2908   thoray29     online udid_mismatch
DS6410_36    auto:cdsdisk    thoray2904   thoray29     online udid_mismatch
DS6410_37    auto:cdsdisk    thoray2901   thoray29     online udid_mismatch
DS6410_38    auto:cdsdisk    thorax2911   thoray29     online udid_mismatch
DS6410_39    auto:cdsdisk    thoray2912   thoray29     online udid_mismatch
DS6410_40    auto:cdsdisk    thorax2903   thoray29     online udid_mismatch
DS6410_41    auto:cdsdisk    thorax2901   thoray29     online udid_mismatch
DS6410_42    auto:cdsdisk    thorax2902   thoray29     online udid_mismatch
DS6410_43    auto:cdsdisk    thoray2915   thoray29     online udid_mismatch
DS6410_44    auto:cdsdisk    thorax2905   thoray29     online udid_mismatch
DS6410_45    auto:cdsdisk    thoray2914   thoray29     online udid_mismatch
DS6410_46    auto:cdsdisk    thoray2911   thoray29     online udid_mismatch
DS6410_47    auto:cdsdisk    thoray2917   thoray29     online udid_mismatch
DS6410_48    auto:cdsdisk    thoray2910   thoray29     online udid_mismatch
DS6410_49    auto:cdsdisk    thoray2913   thoray29     online udid_mismatch
DS6410_50    auto:cdsdisk    thoray2909   thoray29     online udid_mismatch
DS6410_51    auto:cdsdisk    thorax2904   thoray29     online udid_mismatch
DS6410_52    auto:cdsdisk    thoray2916   thoray29     online udid_mismatch
DS6410_53    auto:cdsdisk    thorax2907   thoray29     online udid_mismatch
DS6410_82    auto:cdsdisk    thoray2918   thoray29     online udid_mismatch
DS6410_83    auto:cdsdisk    thoray2919   thoray29     online udid_mismatch
DS6410_84    auto:cdsdisk    thoray2920   thoray29     online udid_mismatch
DS6410_85    auto:cdsdisk    thoray2921   thoray29     online udid_mismatch
DS6410_86    auto:cdsdisk    thoray2922   thoray29     online udid_mismatch
DS6410_87    auto:cdsdisk    thoray2926   thoray29     online udid_mismatch
DS6410_88    auto:cdsdisk    thoray2927   thoray29     online udid_mismatch
DS6410_89    auto:cdsdisk    thoray2923   thoray29     online udid_mismatch
DS6410_90    auto:cdsdisk    thoray2925   thoray29     online udid_mismatch
DS6410_91    auto:cdsdisk    thoray2924   thoray29     online udid_mismatch
DS6410_96    auto:cdsdisk    thoray2928   thoray29     online udid_mismatch
DS6410_108   auto:cdsdisk    thoray0115   thoray01     online udid_mismatch
DS6410_109   auto:cdsdisk    thoray0122   thoray01     online udid_mismatch
DS6410_110   auto:cdsdisk    thoray0121   thoray01     online udid_mismatch
DS6410_111   auto:cdsdisk    thoray2929   thoray29     online udid_mismatch
DS8100_25    auto:LVM        -            -            LVM
DS8100_26    auto:LVM        -            -            LVM
DS8100_27    auto:LVM        -            -            LVM
DS8100_33    auto:cdsdisk    poste8       PTP          online
DS8100_34    auto:cdsdisk    poste5       PTP          online
DS8100_35    auto:cdsdisk    poste3       PTP          online
DS8100_36    auto:cdsdisk    poste4       PTP          online

What do I do wrong?maybe some packages are not installed?

thanks to everyone who can suggest me a solution!

discussion Filed Under:

Storage and Clustering, Storage Foundation, Configuring

Comments RSS Feed

Comments

Apr

2009

0 Votes 0

Gaurav Sangamnerkar

Trusted Advisor

Hello, After presenting the

Hello,

After presenting the Lun to OS & scanning it in the OS, was there any commands executed to scan disk in Veritas ? commands like

# vxdctl enable

# vxdisk scandisks

Also, can you paste following:

# lspv hdisk56

# lspv -l hdisk56

# lquerypv -h /dev/hdisk56

Point to to remember is, if the OS can read/write the disk fine, Veritas shouldn't have any issues....

Thanks

Gaurav

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.

Apr

2009

0 Votes 0

thesime

Hi there !, thanks for the

Hi there !,

thanks for the answer...

Well.. I've done both... vxdctl enable and vxdisk scandisks, but I've not so much lucky...veritas don't see the disk...
here the output of commands requested :

root@ronobe: / =>lspv hdisk56
PHYSICAL VOLUME:    hdisk56                  VOLUME GROUP:     TESTISCSI
PV IDENTIFIER:      00cb1e7b332cc76c VG IDENTIFIER     00cb1e7b00004c0000000120332d0cb2
PV STATE:           active
STALE PARTITIONS:   0                        ALLOCATABLE:      yes
PP SIZE:            16 megabyte(s)           LOGICAL VOLUMES: 0
TOTAL PPs:          639 (10224 megabytes)    VG DESCRIPTORS:   2
FREE PPs:           639 (10224 megabytes)    HOT SPARE:        no
USED PPs:           0 (0 megabytes)          MAX REQUEST:      256 kilobytes
FREE DISTRIBUTION: 128..128..127..128..128
USED DISTRIBUTION: 00..00..00..00..00
root@ronobe: / =>
root@ronobe: / =>
root@ronobe: / =>lspv -l hdisk56
root@ronobe: / =>
root@ronobe: / =>
root@ronobe: / =>lquerypv -h /dev/hdisk56
00000000   C9C2D4C1 00000000 00000000 00000000 |................|
00000010   00000000 00000000 00000000 00000000 |................|
00000020   00000000 00000000 00000000 00000000 |................|
00000030   00000000 00000000 00000000 00000000 |................|
00000040   00000000 00000000 00000000 00000000 |................|
00000050   00000000 00000000 00000000 00000000 |................|
00000060   00000000 00000000 00000000 00000000 |................|
00000070   00000000 00000000 00000000 00000000 |................|
00000080   00CB1E7B 332CC76C 00000000 00000000 |...{3,.l........|
00000090   00000000 00000000 00000000 00000000 |................|
000000A0   00000000 00000000 00000000 00000000 |................|
000000B0   00000000 00000000 00000000 00000000 |................|
000000C0   00000000 00000000 00000000 00000000 |................|
000000D0   00000000 00000000 00000000 00000000 |................|
000000E0   00000000 00000000 00000000 00000000 |................|
000000F0   00000000 00000000 00000000 00000000 |................|

I've utilized the disk now for a lvm dg test...but veritas should mark it like lvm disk as you see in other disks in the vxdisk list:

root@ronobe: / =>vxdisk list |grep -i lvm
DS8100_25    auto:LVM        -            -            LVM
DS8100_26    auto:LVM        -            -            LVM
DS8100_27    auto:LVM        -            -            LVM
DS8100_43    auto:LVM        -            -            LVM
DS8100_129   auto:LVM        -            -            LVM
DS8100_130   auto:LVM        -            -            LVM
DS8100_131   auto:LVM        -            -            LVM
DS8100_132   auto:LVM        -            -            LVM
DS8100_133   auto:LVM        -            -            LVM
DS8100_134   auto:LVM        -            -            LVM
DS8100_135   auto:LVM        -            -            LVM
DS8100_139   auto:LVM        -            -            LVM
DS8100_140   auto:LVM        -            -            LVM
DS8100_142   auto:LVM        -            -            LVM
DS8100_143   auto:LVM        -            -            LVM
DS8100_144   auto:LVM        -            -            LVM
DS8100_145   auto:LVM        -            -            LVM
Disk_14      auto:LVM        -            -            LVM
Disk_15      auto:LVM        -            -            LVM

Apr

2009

0 Votes 0

Gaurav Sangamnerkar

Trusted Advisor

Hi there, well seems to be

Hi there,

well seems to be really unlucky :-(

ok, is DMP able to see the controller & enclosure you have connected ?

# vxdmpadm listctlr all
# vxdmpadm listenclosure all

Lets say if you have connected the NetApp on c5, first command listed above should show something connected over c5.

Also, you can check if ASL is needed for this NetApp array or else you will need to add the array as a JBOD to show to DMP...

Gaurav

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.

Apr

2009

0 Votes 0

Gaurav Sangamnerkar

Trusted Advisor

Hello again, Well I missed a

Hello again,

Well I missed a point in the original description that Lun is a ISCSI lun,

VXVM DMP has started supporting ISCSI from 5.0MP3 onwards, I think that might be the issue....

Check the release notes of 5.0MP3 Storage Foundation... You might need to upgrade to MP3 to get this rolling..

Hope this helps

Gaurav

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.

SOLUTION

Apr

2009

0 Votes 0

thesime

DOW! :O(( this means I have

DOW! :O((

this means I have to reboot ronobe...hope I can do it in a days...my customer will kill me ahahah....have to find a good reason to tell him :O))) ...but I'll do and I'll let you know the result!

thanks a lot!

veritas storage foundation + netapp filer + lun iscsi

Comments

Hello, After presenting the

Hi there !, thanks for the

Hi there, well seems to be

Hello again, Well I missed a

DOW! :O(( this means I have

Would you like to reply?

Links

Technical Support

Symantec.com

Store

Community Stats