I had a client that was trying to connect a CX700 to their AIX TSM system.
What they say is that the SANDISCOVER was causing problems and IBM suggested
they disable it in the DSMSERV.OPT. Been working ever since. I wasn't
involved in the issue, this is just what they told me they found out. But
you might want to give it a try.
Bill Boyer
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Jacques Van Den Berg
Sent: Monday, June 30, 2008 9:19 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Disk pools on EMC issue
Hi Rick,
1. EMC storage is Clariion CX700 and is online and available.
2. Using file systems which is mounted and available when starting up
the server.
3. I'm using Powerpath with one HBA seeing both SP's on EMC.
4. OS is AIX 5.3.
This is the current output of powermt display dev=all:
Pseudo name=hdiskpower1
CLARiiON ID=CK200043600082 [sapnim_SG]
Logical device ID=6006016049C711006CE3D762B8EFDA11 [LUN 18]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP A
========================================================================
======
---------------- Host --------------- - Stor - -- I/O Path - --
Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs
Errors
========================================================================
======
0 fscsi0 hdisk2 SP B0 active dead 0
1
0 fscsi0 hdisk6 SP A0 active alive 0
0
Pseudo name=hdiskpower2
CLARiiON ID=CK200043600082 [sapnim_SG]
Logical device ID=6006016049C71100C2965982B8EFDA11 [LUN 76]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP A
========================================================================
======
---------------- Host --------------- - Stor - -- I/O Path - --
Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs
Errors
========================================================================
======
0 fscsi0 hdisk3 SP B0 active dead 0
1
0 fscsi0 hdisk7 SP A0 active alive 0
0
Pseudo name=hdiskpower3
CLARiiON ID=CK200043600082 [sapnim_SG]
Logical device ID=6006016049C71100C4E0CBCDB8EFDA11 [LUN 78]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP A
========================================================================
======
---------------- Host --------------- - Stor - -- I/O Path - --
Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs
Errors
========================================================================
======
0 fscsi0 hdisk5 SP B0 active dead 0
1
0 fscsi0 hdisk9 SP A0 active alive 0
0
Pseudo name=hdiskpower0
CLARiiON ID=CK200043600082 [sapnim_SG]
Logical device ID=6006016049C71100E0128CBFB8EFDA11 [LUN 77]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP B, current=SP A
========================================================================
======
---------------- Host --------------- - Stor - -- I/O Path - --
Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs
Errors
========================================================================
======
0 fscsi0 hdisk4 SP B0 active dead 0
1
0 fscsi0 hdisk8 SP A0 active alive 0
0
Pseudo name=hdiskpower4
CLARiiON ID=CK200043600082 [sapnim_SG]
Logical device ID=6006016064C111003A6867CD733BDC11 [LUN 187]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP B, current=SP A
========================================================================
======
---------------- Host --------------- - Stor - -- I/O Path - --
Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs
Errors
========================================================================
======
0 fscsi0 hdisk10 SP B0 active dead 0
1
0 fscsi0 hdisk12 SP A0 active alive 0
0
Pseudo name=hdiskpower5
CLARiiON ID=CK200043600082 [sapnim_SG]
Logical device ID=6006016064C111006CDE5FA0733BDC11 [LUN 186]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP A
========================================================================
======
---------------- Host --------------- - Stor - -- I/O Path - --
Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs
Errors
========================================================================
======
0 fscsi0 hdisk11 SP B0 active dead 0
1
0 fscsi0 hdisk13 SP A0 active alive 0
0
Pseudo name=hdiskpower6
CLARiiON ID=CK200043600082 [sapnim_SG]
Logical device ID=6006016064C11100E0B90BC3BD4BDC11 [LUN 188]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP A
========================================================================
======
---------------- Host --------------- - Stor - -- I/O Path - --
Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs
Errors
========================================================================
======
0 fscsi0 hdisk14 SP B0 active dead 0
1
0 fscsi0 hdisk15 SP A0 active alive 0
0
Jacques van den Berg
TSM / Storage / SAP Basis Administrator
Pick 'n Pay IT
Email : jvandenberg AT pnp.co DOT za
Tel : +2721 - 658 1711
Fax : +2721 - 658 1676
Mobile : +2782 - 653 8164
Dis altyd lente in die hart van die mens wat God
en sy medemens liefhet (John Vianney).
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Rhodes
Sent: 30 June 2008 03:08 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM Disk pools on EMC issue
I think we need some more info.
We use EMC storage (DMX and Clariion) for all our TSM disk based
storage (db, log, disk storage pools, file device pools). It just works
-
really well.
Is your storage online and available before you start TSM?
Are you using filesystems or logical volumes?
Are you using PowerPath, or some other mpio driver?
What OS are you using for for your TSM server (we use AIX)?
Rick
Jacques Van Den
Berg
<jvandenberg@PNP.
To
CO.ZA> ADSM-L AT VM.MARIST DOT EDU
Sent by: "ADSM:
cc
Dist Stor
Manager"
Subject
<[email protected] TSM Disk pools on EMC issue
.EDU>
06/30/2008 08:47
AM
Please respond to
"ADSM: Dist Stor
Manager"
<[email protected]
.EDU>
Hello,
I have an interesting issue where when trying to startup TSM, the EMC
storage path's change status to dead.
Environment:
TSM sever using purely for IBM Commonstore for SAP archiving.
TSM database & log files on EMC Clarion Storage - mirrored across LUN'
on EMC.
2TB of disk pools spread across 4 X 500GB LUN's on EMC storage.
My question: Is there a way a can tell TSM not to "VARY-ON" my disk pool
volumes during startup so that I can vary-on them manually once TSM is
up? I think that TSM is trying so hard to vary-on these volumes that the
EMC path timeout.
Has anyone experienced something similar?
Regards,
Jacques van den Berg
TSM / Storage / SAP Basis Administrator
Pick 'n Pay IT
Email : jvandenberg AT pnp.co DOT za <mailto:jvandenberg AT pnp.co DOT za>
Tel : +2721 - 658 1711
Fax : +2721 - 658 1676
Mobile : +2782 - 653 8164
Dis altyd lente in die hart van die mens wat God
en sy medemens liefhet (John Vianney).
Read our disclaimer at:
http://www.picknpay.co.za/pnp/view/pnp/en/page5093?
If you don't have web access, the disclaimer can be mailed to you on
request.
Disclaimer requests to be sent to it-security AT pnp.co DOT za
-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.
Read our disclaimer at: http://www.picknpay.co.za/pnp/view/pnp/en/page5093?
If you don't have web access, the disclaimer can be mailed to you on
request.
Disclaimer requests to be sent to it-security AT pnp.co DOT za
|